 
















                VAX TEAMDATA
                Installation Guide

                Order Number: AA-FX80D-TE






                ________________________________________________________________



                July 1988



                This manual contains information on installing VAX
                TEAMDATA




                OPERATING SYSTEM:            VMS
                                             MicroVMS

                SOFTWARE VERSION:            VAX TEAMDATA V1.3


                digital equipment corporation, maynard, massachusetts

 








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

   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 soft-
   ware on equipment that is not supplied by Digital Equipment
   Corporation or its affiliated companies.



   Copyright (c)1986, 1987, 1988 by Digital Equipment Corporation. All
   rights reserved.



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



   The following are trademarks of Digital Equipment Corporation:


   ACMS            Rdb/ELN       VAX Information Architecture
   DATATRIEVE      Rdb/VMS       VIDA
   DEC             ReGIS         VMS
   DECnet          TDMS          VT
   DECreporter     TEAMDATA
   DECUS           UNIBUS
   MicroVAX        VAX
   PDP             VAXcluster
   RALLY           VAXinfo       DIGITAL


   Lotus 1-2-3, WKS, VisiCalc, Symphony and DIF are trademarks of
   Lotus Development Corporation.
   dBase III is a trademark of Ashton-Tate.
   R:base 5000 is a trademark of Microrim.
   Multiplan and SYLK are trademarks of Microsoft Corp.
   SUPERCOMP-TWENTY and 20/20 are trademarks of Access Technology
   Inc.
   IBM is a trademark of International Business Machines, Inc.
   IDMS/R is a trademark of Cullinet Corporation.

 








                                                             Contents

                                                                 Page
Preface                                                           vii

1    Planning for Installation

     1.1  Overview of This Chapter .............................  1-1
     1.2  Prerequisite Hardware ................................  1-2
     1.3  TEAMDATA Support of License Management Facility
          (LMF) ................................................  1-3
     1.4  Prerequisite Software ................................  1-3
          1.4.1  TEAMDATA and VAX Rdb/VMS ......................  1-4
     1.5  Optional Software ....................................  1-5
          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-6
     1.6  Preparing Your System and the Installing Account .....  1-6
          1.6.1  Checking Privileges of the Installing Account..  1-7
          1.6.2  Checking and Setting User Process Quotas ......  1-9
          1.6.3  Checking and Setting System Parameters ........  1-11
          1.6.4  Changing System Parameters ....................  1-15
     1.7  Performance Considerations ...........................  1-16
          1.7.1  Memory Management .............................  1-17
          1.7.2  Paging and Swapping Files .....................  1-18
     1.8  System Parameters ....................................  1-18

2    Installing VAX TEAMDATA

     2.1  Using the VMSINSTAL Command Procedure ................  2-2
     2.2  Running the TEAMDATA IVP .............................  2-14
          2.2.1  The IVP for TEAMDATA ..........................  2-14
          2.2.2  The IVP for TEAMDATA and DATATRIEVE ...........  2-16





                                                                  iii

 







3    Post-Installation Procedure

     3.1  Moving TEAM$LIBRARY ..................................  3-2
     3.2  Editing SYSTARTUP.COM ................................  3-2
     3.3  DATATRIEVE Versions ..................................  3-3
     3.4  Granting Required User Privileges ....................  3-3
     3.5  Authorizing User Quotas ..............................  3-4
     3.6  Managing Run Unit Journal Files ......................  3-4
     3.7  Granting Database Access to Users on Other Systems ...  3-5
     3.8  Loading Your TEAMDATA License on Each Node in a VAX
          Cluster ..............................................  3-6
     3.9  TEAMDATA Shutdown Procedure ..........................  3-6
     3.10 Installing TEAMDATA on a MicroVAX ....................  3-7

4    Maintaining VAX TEAMDATA

     4.1  Server Process Problems ..............................  4-2
     4.2  Reading a Bugcheck Dump File .........................  4-3
     4.3  Insufficient Parameter Values ........................  4-5
     4.4  Reporting Problems to DIGITAL ........................  4-6

5    Installing TEAMDATA in ALL-IN-1 Menus

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

A    Files, Images and Logical Names










iv

 







B    A Sample Installation

Index

Tables

     1-1  Disk Requirements ....................................  1-2
     1-2  Required Installer Privileges ........................  1-8
     1-3  Required User Process Quotas .........................  1-10
     1-4  Required System Parameters ...........................  1-12






























                                                                    v

 

















                                                              Preface





   This manual tells you how to install the VAX TEAMDATA software,
   also referred to as TEAMDATA.

Who Should Use This Manual

   Read this manual if you are responsible for:

   o  Planning the installation of TEAMDATA and preparing your system

   o  Registering your TEAMDATA license

   o  Installing TEAMDATA

   o  Changing your system by adjusting parameters, startup and
      shutdown files, and privileges required for running TEAMDATA

   o  Installing TEAMDATA in an ALL-IN-1 menu

   To install the software, you must:

   o  Have all the information you need to register TEAMDATA through
      the License Management Facilty (LMF).






                                                                  vii

 







   o  Be familiar with VMSINSTAL, the command procedure used to
      install software products in the VMS environment. To locate the
      description of VMSINSTAL, see the master index of the VAX/VMS
      documentation set.

   o  Have access to the SYSTEM account on your machine or to an
      account with the user privilege SETPRV.

   If you are responsible for installing TEAMDATA on your system,
   read this entire manual before you begin the installation. This
   manual helps you make the required decisions and guides you
   through the correct sequence of actions.

Operating System Information

   Information about the versions of the operating system and related
   software that are compatible with this version of VAX TEAMDATA is
   included in Chapter 1 of this Installation Guide.

   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 TEAMDATA
   System Support Addendum, SSA 27.02.03-A, which will verify which
   versions of your operating system are compatible with this version
   of TEAMDATA.

















viii

 








Structure of This Manual

   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 VAX/VMS system by ad-
                 justing the required characteristics for running VAX
                 TEAMDATA.

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

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

   Appendix A    Lists the files included in the VAX TEAMDATA kit.

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

Conventions

   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.

   This manual uses the following conventions:

   o  Italic text in examples

      Identifies commands you type or sample responses to prompts.

   o  Gold-H




                                                                   ix

 







      Means press and release the Gold key, labeled PF1 on some
      keyboards, and then press another key. For example, press
      Gold-H to get Help.

   o  CTRL/W

      Means press the CTRL (control) key and another key at the same
      time. For example, press CTRL/W to refresh your screen.

   o  SELECT

      Identifies a labeled key on your keyboard, in this example the
      SELECT key.

   o  HELP (Gold-H)

      Identifies two keys or key combinations do the same thing.
      The first key notation refers to a key used on a VT200 series
      terminal. The key notation in parentheses refers to a key used
      on a VT100 series terminal. For example, a VT125 does not have
      a labeled HELP key, so you must press Gold-H.

      The keys in parentheses will work on any keyboard, including
      the VT200 series.

For More Information

   You can find further information on the topics covered in this
   manual in the VAX/VMS documentation set and in the ALL-IN-1 docu-
   mentation set. See especially:

   o  Guide to VAX/VMS Software Installation

   o  VAX/VMS Utilities Reference Manual

   o  Guide to VAX/VMS System Management and Daily Operations

   o  Guide to Networking on VAX/VMS

   o  ALL-IN-1 Office Menu System Manager's Guide






x

 







   For more information on TEAMDATA, refer to:

   o  The Introduction to VAX TEAMDATA

   o  Using VAX TEAMDATA

   o  The VAX TEAMDATA Command Summary

   o  The VAX TEAMDATA Quick Reference Guide

   o  The VAX TEAMDATA Update Manual

   For information on running RALLY applications from TEAMDATA, refer
   to the 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 Guide to VIDA
   Operations. VIDA is used in the TRANSFER MAKE_KNOWN TABLE command
   when accessing IBM databases.

   For more information on management of Rdb/VMS databases and use
   of the RDO utility, refer to the VAX Rdb/VMS Guide to Database
   Administration and Maintenance.


















                                                                   xi

 


















                                         Planning for Installation  1




   If you are responsible for installing VAX TEAMDATA on your system,
   read all of this manual before you begin to install the software.
   This manual helps you make the required decisions and guides you
   through the correct sequence of actions.

1.1  Overview of This Chapter

   To plan and prepare your system for installing TEAMDATA, you must:

   o  Read the VAX TEAMDATA Release Notes.

   o  Check that your system has enough memory and available disk
      space to install and run TEAMDATA.

   o  Check that your system has the required software.

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

   o  Decide what values your VMS system parameters should have.

   o  Determine if you must register TEAMDATA through the online
      License Management Facility (LMF).




                                       Planning for Installation  1-1

 







   This manual tells you what actions to take at each step.

1.2  Prerequisite Hardware

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

   Hardware re-       TEAMDATA runs on all VAX systems, except the
   quired:            MicroVAX I and the VAX-11/725. For a complete
                      list of processors, see the VAX TEAMDATA System
                      Support Addendum.

   Memory required:   4 megabytes.

   Disk space re-     See Table 1-1.
   quired:

   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-1 summarizes these options.

   Table 1-1: Disk Requirements
   __________________________________________________________________

                                   
                          Blocks on 
                          System        Blocks on
                          Disk (To      System Disk
   Installation Option    Install)      (To Run)                         
   __________________________________________________________________

   TEAMDATA entirely on   12,500        9,800
   system disk

   TEAMDATA directory     8,100         5,400
   on another disk
   __________________________________________________________________



1-2  Planning for Installation

 







1.3  TEAMDATA Support of License Management Facility (LMF)

   TEAMDATA V1.3 supports the VMS License Management Facility (LMF)
   for installation on a system with VAX/VMS Version 5.0. Systems
   running VAX/VMS Version 4.7 do not support the LMF. If you need
   to register TEAMDATA through the LMF, your kit includes a Product
   Authorization Key (PAK) containing the information you need for
   registration.

   To register your PAK, use the command procedure SYS$UPDATE:VMSLICENSE.
   COM. For more information on this command procedure and the LMF,
   refer to VMS License Management Utility Reference Manual.

   TEAMDATA asks you early in the installation procedure if you
   have an authorization key registered and loaded. You can install
   TEAMDATA V1.3 without the authorization information, but you will
   not be able to run TEAMDATA or the IVP (Installation Verification
   Procedure).

1.4  Prerequisite Software

   To install TEAMDATA V1.3, you need the following software in-
   stalled on your system:

   o  VMS V4.7 or later

   o  Rdb/VMS V2.2 or later (development or run-time kit)

   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 TEAMDATA
   System Support Addendum, SSA 27.02.03-A, which will verify which
   versions of your operating system are compatible with this version
   of TEAMDATA.








                                       Planning for Installation  1-3

 







1.4.1  TEAMDATA and VAX Rdb/VMS

   VAX Rdb/VMS is a prerequisite for VAX TEAMDATA. You must have
   either the full development license 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 V2.2-0
     RDO> EXIT

   Check that the file SYS$SHARE:RDBSHR.EXE is installed on your
   system. If you have recently upgraded to a more recent version
   of Rdb/VMS, RDBSHR.EXE may have been deinstalled by the upgrade.
   Without it properly installed, TEAMDATA will not be accessible on
   your system.

   If this occurs, rerun SYS$MANAGER:TDA_STARTUP.COM, which will
   properly install RDBSHR.EXE.












1-4  Planning for Installation

 







1.5  Optional Software

   The following software can be used with VAX TEAMDATA V1.3:

   o  ALL-IN-1 V2.1 or later

   o  VAX RALLY V1.1 or later

   o  VAX DATATRIEVE V4.0 or later

   o  Common Data Dictionary/Plus V4.0

   o  VAX DBMS V3.0 or later

   o  VAX Xway V1.1

   o  VIDA with IDMS/R TM V2.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.5.1  TEAMDATA and VAX DATATRIEVE

   If you want to use DATATRIEVE domains through TEAMDATA, you must
   have DATATRIEVE V4.0 or later installed on your system. DATATRIEVE
   requires the VAX Common Data Dictionary (CDD) Version 3.4 or
   later.

1.5.2  TEAMDATA and VAX RALLY

   If you want to run VAX RALLY applications from TEAMDATA, you must
   have RALLY V1.1 or later installed on your system.

1.5.3  TEAMDATA and VAX Xway

   If you want to use the TRANSFER IMPORT and TRANSFER EXPORT com-
   mands in TEAMDATA, you must have V1.1 of VAX Xway installed on
   your system.




                                       Planning for Installation  1-5

 







1.5.4  TEAMDATA and VIDA

   If you want to use TEAMDATA to access information stored in IBM
   databases, you must have VIDA V1.0 installed on your system.

1.6  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:

   o  Process privileges

   o  Process quotas

   o  System parameters

   You must change, define, or redefine those characteristics of your
   system and account that do not match the values or definitions
   required for the installation and running of TEAMDATA.

   Before you finish changing system parameters, consult the perfor-
   mance recommendations section of this chapter.

      ___________________________ Note ___________________________

      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 Administration and
      Maintenance.

      ___________________________________________________________










1-6  Planning for Installation

 







1.6.1  Checking Privileges of the Installing Account

   The account you use to install TEAMDATA must have the user priv-
   ilege 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 ex-
   ample, you might have to run SYSGEN or AUTHORIZE. Some of these
   preparations require that your account have specific user priv-
   ileges, which might not be among default privileges assigned to
   your account.

   Table 1-2 shows you what privileges you need for various installa-
   tion tasks.




















                                       Planning for Installation  1-7

 







   Table 1-2: 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 not have
   the privileges listed in Table 1-2, use AUTHORIZE to grant them
   permanently or SET PROCESS/PRIVILEGES to grant them for this
   installation.











1-8  Planning for Installation

 







1.6.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-3.




































                                       Planning for Installation  1-9







   Table 1-3: Required User Process Quotas
   __________________________________________________________________

   Process      Recommended Controlling
   Quotas       Minimum     Qualifier   Defining Utility                
   __________________________________________________________________

   Buffered     10,336      BYTLM       AUTHORIZE
   I/O byte
   count quota

   Enqueue      600         ENQLM       AUTHORIZE
   quota

   Open file    60          FILLM       AUTHORIZE
   quota

   Maximum      2[1]        MAXDETACH   AUTHORIZE
   number of
   detached
   processes

   Maximum      3[1]        MAXJOBS     AUTHORIZE
   number of
   jobs

   Subprocess   1           PRCLM       AUTHORIZE
   quota

   Working      1024        WSEXTENT    AUTHORIZE
   set/Extent

   Working      512         WSQUOTA     AUTHORIZE
   set/Quota

   Page file    15,000      PGFLQUO     AUTHORIZE
   quota
   __________________________________________________________________

   [1]A value of zero for these parameters indicates no limit

   __________________________________________________________________

1-10  Planning for Installation

 







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

   o  If many users on your system are doing many database opera-
      tions at the same time, you might need to increase the ENQLM
      parameter.

   o  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 at least 15000.

   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.6.3  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.








                                      Planning for Installation  1-11

 







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

   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.
   __________________________________________________________________





1-12  Planning 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. To check the parameters listed in Table 1-4, except for
   GBLSECTIONS and GBLPAGES, log in to the SYSTEM account, and com-
   pare 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. Detailed instructions follow.

   To check the number of global sections available, use the SHOW
   command in the SYSGEN utility, as you did with LOCKIDTBL. The
   number of available global sections is the first number on the
   left:






                                      Planning for Installation  1-13

 







     $ RUN SYS$SYSTEM:SYSGEN
     SYSGEN> USE CURRENT
     SYSGEN> SHOW GBLSECTIONS
     Parameter Name    Current   Default   Minimum   Maximum Unit  Dynamic
     --------------    -------   -------   -------   ------- ----  -------
     GBLSECTIONS           512       220        20        -1 Sections
     SYSGEN> EXIT
     $

   To check the number of global sections currently in use, and
   to check the number of used and unused global pages, use the
   LIST/GLOBAL command of the INSTALL utility.

   For VMS Version 4.7, use the following example (for VMS Version
   5.0 the following example is the default and you enter only
   INSTALL). For example:

     $ INSTALL :== "$INSTALL/COMMAND_MODE"
     $ INSTALL LIST/GLOBAL/SUMMARY

            Summary of Local Memory Global Sections

       443 Global Sections Used,  20364/12636 Global Pages Used/Unused
     $

   To calculate the current number of unused global sections, sub-
   tract global sections used from the number available:

     512 - 443 = 69 unused sections

   Compare this number to the number of additional global sections
   required to install TEAMDATA, in Table 1-4. For example, if the
   table says you need 53 global sections to install TEAMDATA, the
   current number is sufficient:

     69 - 53 = 16 remaining global sections






1-14  Planning for Installation

 







   If the number of remaining global sections is small, you will
   have very little cushion left for any additional memory usage.
   Therefore, if the number of remaining sections is small, it is a
   good idea to increase the global sections available.

   Perform the same calculations to obtain the required additional
   global pages. For example, Table 1-4 lists the required number of
   global pages as 5800:

     12,636 - 5800 = 6836

   In this case, you have sufficient global pages for installation,
   and a sufficient cushion for future installations.

   See Section 4-3 for more information on the global sections and
   global pages parameters.

1.6.4  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 line, or change the existing line as follows:

     ADD_GBLSECTIONS=53

     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:





                                      Planning for Installation  1-15

 







   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 bringing
   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

   For more information, refer to documentation for the VMS Operating
   System.

1.7  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 can be modified by the system
   manager to improve performance. The following topics are included:

   o  Memory management

   o  Paging and swapping files



1-16  Planning for Installation

 







   o  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 VMS
   Performance Management Guide.

1.7.1  Memory Management

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

   o  WSDEFAULT 256

   o  WSQUOTA 512

   o  WSEXTENT 1024-1536

   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.













                                      Planning for Installation  1-17

 







1.7.2  Paging and Swapping Files

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

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

   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.8  System Parameters

   Table 1-4 lists the minimum system parameter values required to
   install VAX 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, some system parameters
   need to be adjusted to obtain better performance. The recommended
   values for these system parameters are listed here. These parame-
   ters can be adjusted independently through the use of the SYSGEN
   facility:

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

      Suggested setting: 2048

   o  RESHASHTBL - Defines the number of entries in the lock man-
      agement resource name hash table. This value should be set to
      one-quarter the value of LOCKIDTBL, rounded up to the closest
      power of 2.




1-18  Planning for Installation

 







      Suggested setting: 512

   o  SRPCOUNT, SRPCOUNTV - These parameters control the number of
      small request packets. It is recommended that you monitor the
      use of SRPs on the system using the DCL command SHOW MEMORY.
      If the total size of the SRP list is greater than the value
      of SRPCOUNT, 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.

   o  IRPCOUNT, IRPCOUNTV - These parameters control the number of
      I/O request packets. It is recommended that you use the DCL
      command SHOW MEMORY to monitor the use of IRPs on the system.
      If the total size of the IRP list is greater than the value
      of IRPCOUNT, then you should set the value of IRPCOUNT to this
      new value. 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.

   o  NPAGEDYN, NPAGEVIR - NPAGEDYN sets the size of the nonpaged
      dynamic pool in bytes. This pool can grow dynamically to the
      limit set by NPAGEVIR. It is recommended that you use the DCL
      command SHOW MEMORY to monitor the size of nonpaged pool on the
      system. If the total size of nonpaged pool 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.




                                      Planning for Installation  1-19

 


















                                           Installing VAX TEAMDATA  2




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

   Plan to finish this procedure in one session.

   The estimated time required for the installation is 50 minutes.
   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.

   All you need to install TEAMDATA are this manual and the distri-
   bution media. Before you begin the installation, check the part
   numbers of the media against those on the bill of materials in
   the distribution kit. Also make sure you have the right number of
   media.

      ___________________________ Note ___________________________

      If you already have another version of TEAMDATA installed
      on your system, and you want to change the location of





                                         Installing VAX TEAMDATA  2-1

 







      TEAM$LIBRARY, make the change before you begin the instal-
      lation.

      ___________________________________________________________

2.1  Using the VMSINSTAL Command Procedure

   This section guides you step by step through the installation
   of TEAMDATA. It includes instructions on how to prepare your
   system for running the VMSINSTAL command procedure as well as
   instructions for running VMSINSTAL. VMSINSTAL moves the software
   from the distribution media to your system disk.

   Step 1: Back up your system disk.

   This precaution protects your system software. A system failure
   at a critical point in the installation procedure could leave
   unusable files. This also protects your existing version of the
   product, which can, if you request, be deleted during the instal-
   lation.

   If your backup disk is the same type as your system disk, use the
   backup copy for the installation. However, if you switch to the
   backup copy of the system disk, you must run SHUTDOWN.COM to shut
   down the system, and you must reboot the system manually (see step
   4).

   Step 2: Log in to the SYSTEM account and check its process quotas
   and privileges.

   Step 3: Check the VMS system parameters and make any required
   changes.

   Use the SYSGEN utility to compare current system parameters with
   the required ones listed in Table 1-4 and explained in Section
   1.6.3.

   If the parameters you must change are dynamic, make the necessary
   changes to the ACTIVE system parameters with the SYSGEN commands
   USE, SET, and WRITE.



2-2  Installing VAX TEAMDATA

 







   If any parameter you change is not a dynamic parameter, use
   AUTOGEN to change the parameter. Make the necessary changes in
   the data file MODPARAMS.DAT, as explained in Section 1.6.4.

   Step 4: Shut down the system.

   If you want to shut down the system and reboot it to change system
   parameters or change the system disk, run the command procedure
   SYS$SYSTEM:SHUTDOWN.COM.

   You can ask for an automatic reboot if you need to change only the
   system parameters. To change the system disk, however, you must
   halt the system manually, change the disks, and reboot the system
   manually (see step 5).

   Step 5: Restore the backed-up system disk.

   If you want to use the backup system disk for the installation,
   you must follow these steps:

   o  Shut down the system (see step 4).

   o  Halt the CPU manually.

   o  Stop the system disk drive.

   o  Change the disk packs.

   o  Start the system disk drive.

   o  Ensure that all required disk drives are mounted and spinning.

   o  Reboot the system.

   When the system starts up, log in to the SYSTEM account and con-
   tinue with the rest of the installation procedure.

   Prevent interactive users from gaining access to the system.

   Keep interactive users off the system during the installation pro-
   cess. For example, if anyone has opened the system help library,
   the installation will fail. Use the DCL REPLY command to inform





                                         Installing VAX TEAMDATA  2-3

 







   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

   Step 7: Check all batch and device queues to ensure that all batch
   and print jobs are finished.

   Step 8: 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 mon-
   itor is running, this command has no effect; the monitor continues
   to run.

   The installation cannot proceed until the Rdb/VMS monitor is
   running.

   Step 9: Invoke VMSINSTAL.COM and print the Release Notes

   Most of the installation procedure prompts include a default
   answer following the prompt. The default answer is enclosed by
   square brackets [ ]. For example:

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

   To accept the default answer, press RETURN. To record a yes an-
   swer, enter Y or YES; for a no answer, enter N or NO.

   Once you have ensured that the system disk has enough free disk
   space, invoke the VMSINSTAL command procedure at DCL command
   level. After you enter the file specification of the procedure,
   enter the product identifier TDA013, the name of the device on



2-4  Installing VAX TEAMDATA

 







   which you intend to mount the distribution media, and the option N
   to print or view the Release Notes. If you prefer, you can enter
   only the file specification and let VMSINSTAL prompt you for the
   rest of the installation.

   The following example includes all necessary information on the
   same command line and names the disk drive DMA0: as the device for
   mounting the distribution medium.

      $ SET DEFAULT SYS$UPDATE
      $ @VMSINSTAL TDA013 DMA0: OPTIONS N

   Option N displays a menu that asks if you want to view the Release
   Notes, print them, or both. The system also prompts you for the
   printer queue name and asks if you want to continue with the
   installation.

   Note that whether or not you choose option N, VMSINSTAL copies the
   Release Notes to SYS$HELP:TDA013.RELEASE_NOTES. DIGITAL recommends
   that you do not delete the Release Notes for previous versions of
   TEAMDATA (or any other product).

   Step 10: VMSINSTAL asks you 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 con-
   tinue with the installation until you do so. If you need to back
   up the system disk, type N. VMSINSTAL exits and returns you to
   the DCL prompt. Back up your system disk, and then start VMSINSTAL
   again at step 9.

   If you have already backed up the system disk, type Y and press
   the RETURN key or just press the RETURN key.







                                         Installing VAX TEAMDATA  2-5

 







   See the appropriate VAX/VMS software installation guide in the
   VAX/VMS documentation set for more information on backups before
   installations. For general information on backups, see the VAX/VMS
   Utilities Reference Manual.

   Step 11: Mount the first distribution medium.

   VMSINSTAL asks you to mount the first distribution medium on the
   device you named in step 9. For example:

     Please mount the first volume of the set on DMA0:.

   Take the distribution medium, physically mount it on the appropri-
   ate tape drive, and ready the drive.

   A prompt asks if you are ready to continue the installation. When
   you are ready, respond by entering Y. For example:

     * Are you ready? Y

   VMSINSTAL tries to execute the DCL MOUNT command using the device
   name you supplied in step 9. If it succeeds, it displays the MOUNT
   command success message on your terminal. For example:

     %MOUNT-I-MOUNTED, TDA013          mounted on _DMA0:

   If VMSINSTAL cannot execute the mount command, check the status
   of the device with a DCL SHOW DEVICE command. If the device is on
   line, you might have a problem with the installation kit or the
   device. Contact your DIGITAL representative.

   Step 12: Check the installation identification message.

   After mounting the device successfully, VMSINSTAL displays a
   message that tells you which version of the product is on the
   distribution medium and that it is ready for installation. For
   example:





2-6  Installing VAX TEAMDATA

 







     The following products will be processed:

       TDA V1.3

             Beginning installation of TDA V1.3 at 10:00

   The message after the product identification shows the next step
   VMSINSTAL takes automatically:

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

         ***************************************************************
         *                                                             *
         *                 TEAMDATA version: V1.3                      *
         *                                                             *
         *                 Installation Procedure                      *
         *                     on Node: OPUS                           *
         *               on 19-AUG-1988 10:00:24.71                    *
         *                                                             *
         *     Copyright (c) 1988 by Digital Equipment Corporation     *
         *                                                             *
         ***************************************************************

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

   If you are installing TEAMDATA Version 1.3 on a system that is
   running VMS V5.0 you are now asked if a TEAMDATA authorization key
   has been registered through the License Management Facility (LMF).


             Product:      TEAMDATA
             Producer:     DEC
             Version:      V1.3
             Release Date: 19-AUG-1988

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




                                         Installing VAX TEAMDATA  2-7

 







   At this point in the installation, you must answer YES or NO. If
   you answer YES, the installation then proceeds in the usual man-
   ner. 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 is halted.

   Step 13: Purge files replaced by the installation.

   VMSINSTAL asks if you want to purge the files replaced by this
   installation.

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

   Step 14: Check any system requirements error messages.

   At this point, VMSINSTAL displays the following message:

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






2-8  Installing VAX TEAMDATA

 







   The installation procedure checks several system characteristics,
   including:

   o  The number of blocks available on your system disk

   o  The VAX/VMS version your system is running

   o  The current value of process quotas

   o  The current value of system parameters

   If any system characteristic does not meet the minimum required
   value, the installation displays an error message and might 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.                                                *
     *                                                                       *
     *************************************************************************

   You should correct any problems before continuing the installation
   procedure or before you run TEAMDATA.

   For example:








                                         Installing VAX TEAMDATA  2-9

 







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

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

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

   Step 15: Choose the location of TEAM$LIBRARY.

   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 disk space is low,
   you have the option of placing this library on another disk:

     **************************************************************************
     *                                                                        *
     *   TEAMDATA creates a directory to put product specific files in.       *
     *      The logical TEAM$LIBRARY will point to this directory.            *
     *      These files amount to about 4400 disk blocks.                     *
     *      The default is recommended.                                       *
     *                                                                        *
     *      This directory already exists in: SYS$COMMON:[TEAMDATA]           *
     *                                                                        *
     **************************************************************************

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

      ___________________________ Note ___________________________

      DIGITAL recommends that you select the default location
      for TEAM$LIBRARY. If you decide to place TEAM$LIBRARY else-
      where, you must modify your SYSTARTUP.COM file. See Section
      3.2 for instructions. Note that for VMS Version 4.7 you




2-10  Installing VAX TEAMDATA

 







      use SYSTARTUP.COM. For VMS Version 5.0 you use SYSTARTUP_
      V5.COM.

      ___________________________________________________________

   Step 16: 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
   the message shown below is not displayed.

   If you have modified TDADEFDB, you might 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.

     ****************************************************************
     *                                                              *
     *   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]?

   Step 17: Check informational messages.





                                        Installing VAX TEAMDATA  2-11

 







   VMSINSTAL displays a message that reminds you to edit the
   SYSTARTUP.COM files to add commands that invoke TDA_STARTUP. Note
   that for VMS Version 4.7 you use SYSTARTUP.COM. For VMS Version
   5.0 you use SYSTARTUP_V5.COM. You must edit SYSTARTUP.COM on all
   nodes that run TEAMDATA. Be sure to run the version that matches
   the version of VMS you use. If you do not do this, TEAMDATA will
   not be available when the system is rebooted:

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

   Step 18: Check file transfer messages.

   The installation procedure displays messages telling you what
   it is doing as it continues. Look for the messages that tell you
   when it begins and finishes installing the software options you
   select. The procedure displays these messages when the files for
   the product are transferred from the distribution medium to your
   system.

   The following example illustrates an installation:

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



2-12  Installing VAX TEAMDATA

 







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

        *****************************************************************
        *                                                               *
        *  Installing sample Database...                                *
        *                                                               *
        *****************************************************************

      %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target
      directories...
      VAX TEAMDATA: Installing TEAMDATA images
      VAX TEAMDATA: Starting System Interconnect
      %RUN-S-PROC_ID, identification of created process is 00000077

              Installation of TDA V1.3 completed at 10:48

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

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

   Use SYSGEN to change this parameter and restart the installa-
   tion at step 9. See Section 1.6.3 for more information about the
   CLISYMTBL parameter.

   Step 19: End the installation procedure.

   The installation procedure ends automatically with the following
   message:

             Installation of TDA V1.3 completed at 10:50
             VMSINSTAL procedure done at 11:32

   At the end of an installation, VMSINSTAL returns you to DCL com-
   mand level.



                                        Installing VAX TEAMDATA  2-13

 







2.2  Running the TEAMDATA IVP

   This section shows you how to run an Installation Verification
   Procedure (IVP) for TEAMDATA. Section 2.2.1 shows how to run an
   IVP that tests TEAMDATA itself. Section 2.2.2 shows how to test
   TEAMDATA access to DATATRIEVE domains.

2.2.1  The IVP for TEAMDATA

   The TEAMDATA IVP consists of a set of command procedures that
   test the TEAMDATA components. Run the TEAMDATA IVP from the system
   manager's account, following these steps:

   1. In the system manager's account, run TEAMDATA:

        $ TEAMDATA

      TEAMDATA displays a message and creates a new database. When
      this is complete, TEAMDATA displays the Main Folder.

   2. At this point, if you have DATATRIEVE installed, you can run
      the TEAMDATA/DATATRIEVE IVP (see Section 2.2.2). When that
      procedure returns you to the Main Folder, continue with this
      procedure.

   3. Press Gold-H. The Help window appears with Help on OPEN.

   4. Press the Right Arrow key twice to choose Training, then press
      RETURN. The menu of Training lessons appears.

   5. Press Gold-X to exit from Help.

   6. Press Gold-U. TEAMDATA prompts for the name of a command proce-
      dure.

   7. Enter the following:

        TEAM$LIBRARY:TDA_IVP_MAIN

      Press RETURN.



2-14  Installing VAX TEAMDATA

 







      The command procedure takes over and opens the table called
      IVP_TABLE. Wait until an empty table appears (the center of the
      screen will be empty), and the top line of the screen contains
      the following label:

        Table:  IVP_TABLE

   8. Press Gold-U. TEAMDATA prompts for the name of a command proce-
      dure.

   9. If you have a terminal that does not support ReGIS graphics
      (VT100 series, VT220), enter the following name and press
      RETURN:

        TEAM$LIBRARY:TDA_IVP_TABLE

      If your terminal supports graphics (VT125, VT240, VT241), enter
      the following name:

        TEAM$LIBRARY:TDA_IVP_TABLE_GRAPH

      The command procedure takes over, performs test operations,
      and exits from the table. Then, the previous command procedure
      takes over and opens a TEAMDATA spreadsheet.

   10.Wait until you see the following label at the top of the
      screen:

        Sheet:  IVP_SHEET

   11.Press Gold-U and enter the name of the next command procedure:

        TEAM$LIBRARY:TDA_IVP_SHEET

   12.This command procedure tests the sheet component and exits.
      Then, the previous command procedure exits from TEAMDATA.





                                        Installing VAX TEAMDATA  2-15

 







   13.When you return to DCL, you can delete the sample database you
      have created, if it is no longer needed:

        $ DELETE TEAMDB.*;

2.2.2  The IVP for TEAMDATA and DATATRIEVE

   The TEAMDATA/DATATRIEVE IVP consists of a command procedure that
   tests TEAMDATA's ability to access a DATATRIEVE domain. Make
   sure you have DATATRIEVE installed on your system. Then run this
   IVP from the system manager's account. If you have not yet run
   TEAMDATA, do so now:

     $ TEAMDATA

   Then, follow these steps:

   1. When the TEAMDATA Main Folder is displayed, press Gold-U.
      TEAMDATA prompts you for the name of a command procedure.

   2. Enter the following name:

        TEAM$LIBRARY:TDA_IVP_DTR

      This procedure will make a TEAMDATA entry for the DATATRIEVE
      domain called YACHTS_SEQUENTIAL. YACHTS_SEQ should appear in
      the NAME column of the TEAMDATA Main Folder. The procedure
      then opens the YACHTS_SEQ entry and displays the yachts data in
      table format. The system displays a message reminding you that
      no updates are allowed to the data. Press CTRL/Z to continue.

   3. At this point, you can try some TEAMDATA commands. When you are
      finished, choose or type the following command:

        EXIT QUIT

      The command procedure resumes control and deletes the YACHTS_
      SEQ entry from your folder.



2-16  Installing VAX TEAMDATA

 







   4. The DATATRIEVE IVP is completed. Type the following:

        EXIT SYSTEM

      TEAMDATA then returns you to DCL.

   The following problems can occur with the TEAMDATA/DATATRIEVE IVP:

   o  The following message might appear:

        DATATRIEVE system not available

      This message results for one of these reasons:

      _  DATATRIEVE is not installed on your system.

      _  The sample data file DTR$LIBRARY:YACHT.SEQ is missing.

      _  Your version of SYS$SHARE:DTRSHR has been given an alternate
         name (which is allowed in order to have multiple versions of
         DATATRIEVE on your system). If you have multiple versions of
         DATATRIEVE on your system, and, if the logical name DTRSHR
         refers to a DATATRIEVE shareable image that is incompatible
         with TEAMDATA, you will get this error. If possible, rede-
         fine DTRSHR to refer to a version of DATATRIEVE that runs
         with TEAMDATA. See Section 3.3 for more information.

      _  The VAX Common Data Dictionary (CDD) is not installed on
         your system.

   o  If the DATATRIEVE domain YACHTS_SEQUENTIAL or YACHT record
      is not found in CDD$TOP.DTR$LIB.DEMO, the message "Table not
      found" will appear on the screen. This can also happen if the
      domain definition contains a process logical name as part of a
      CDD path name.

      ___________________________ Note ___________________________

      TEAMDATA cannot use process logical names that you have
      defined in domain definitions. Therefore, if your do-




                                        Installing VAX TEAMDATA  2-17

 







      main definition includes process logical names, TEAMDATA
      will not open your DATATRIEVE domain correctly. For ex-
      ample, assume that CDD$ME is a process logical referring
      to CDD$TOP.FORESTER, and assume that MY_DISK is a process
      logical referring to DISK$1. TEAMDATA will not be able to
      use the domain defined as follows:

        DTR> SHOW ACCT
        DOMAIN CDD$ME.ACCT USING CDD$ME.ACCT_REC
           ON MY_DISK:[FORESTER.MONEY]ACCT.DAT;

      Use the DATATRIEVE EDIT command to change this domain defi-
      nition as follows:

        REDEFINE DOMAIN CDD$TOP.FORESTER.ACCT
           USING CDD$TOP.FORESTER.ACCT_REC
           ON DISK$1:[FORESTER.MONEY]ACCT.DAT;

      Or, define CDD$ME and MY_DISK as job logical names.

      ___________________________________________________________




















2-18  Installing VAX TEAMDATA

 


















                                       Post-Installation Procedure  3




   This chapter guides you step-by-step through the procedure to
   follow after you finish installing VAX TEAMDATA. These steps are:

   1. Deciding where to put TEAM$LIBRARY

   2. Editing the SYSTARTUP.COM file.

   3. Granting required user privileges to TEAMDATA users.

   4. Granting required quotas to TEAMDATA users.

   5. Setting the limit on Run Unit Journal files.

   6. Granting users on other systems access to your TEAMDATA
      databases

   7. Loading your TEAMDATA license on each node in a VAX cluster

   This chapter also provides information about the TEAMDATA shut-
   down procedure, and information about installing TEAMDATA on a
   MicroVAX.







                                     Post-Installation Procedure  3-1

 







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 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 direc-
   tory to USER$DISK, use these commands:

     $ CREATE/DIRECTORY USER$DISK:[BIZ_PRODS.TEAMDATA]
     $ COPY 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.COM

   In order to have VAX TEAMDATA V1.3 started automatically when your
   system is booted, edit the appropriate site-specific startup file:

   o  For VMS V4.7 the file is SYS$MANAGER:SYSTARTUP.COM.

   o  For VMS V5.0 the file is SYS$MANAGER:SYSTARTUP_V5.COM.

   Add the following line to the appropriate file:

     $ @SYS$MANAGER:TDA_STARTUP

   If you redefined TEAM$LIBRARY to refer to a disk other than the
   system disk, you must add the definition to the site-specific
   startup file.

   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 the site-specific
   startup file:




3-2  Post-Installation Procedure

 







     $ @SYS$MANAGER: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  DATATRIEVE Versions

   The installation procedure warns you if you have DATATRIEVE in-
   stalled, 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 cho-
   sen. To make this choice permanent, you must place the following
   line in the site-specific startup file:

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

   If you change the site-specific startup file to include this
   line, TEAMDATA uses DTRSHRV4.EXE when TEAMDATA users work with
   DATATRIEVE domains.

3.4  Granting Required User Privileges

   VAX 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.








                                     Post-Installation Procedure  3-3

 







   For example:

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



3.5  Authorizing User Quotas

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

3.6  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 main-
   tain 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. This problem can be solved in one of
   two ways.

   The first solution is to 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 can be
   opened 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, the file version limit should be set to at least six.




3-4  Post-Installation Procedure

 







   The version limit of a directory file can be changed with the SET
   FILE command, as in the following example:

     $ SET FILE USER$DISK:[000000]BINKLEY.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:[BINKLEY.RUJ]

   For more information on the TEAM$MAX_SERVERS logical, see Using
   VAX TEAMDATA.

3.7  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 con-
   tain at least the minimum quotas recommended for TEAMDATA user
   accounts. These quotas are listed in Table 1-3.

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

     $ MCR NCP
     NCP> SHOW OBJECT RDBSERVER

   Information about the account associated with RDBSERVER is dis-
   played. If no information is displayed, then the DECnet account
   is the account used for remote access requests. In this case, the
   DECnet account should contain the quotas listed in Table 1-3.





                                     Post-Installation Procedure  3-5

 







3.8  Loading Your TEAMDATA License on Each Node in a VAX Cluster

   Read this section only if you are installing TEAMDATA Version 1.3
   on a system running VMS Version 5.0.

   To run TEAMDATA on each node in a cluster, make sure the license
   is loaded on each node in the cluster. The VMS license command
   procedure described in Chapter 1 puts the license information in
   the cluster license database. The license still must be loaded
   into memory for each node of the cluster.

   Refer to the product name on your PAK to determine whether your
   license is for TEAMDATA or TEAMDATA-USER. Then enter the appropri-
   ate version of this command to load the license to each node of
   your cluster:

     $ LICENSE LOAD TEAMDATA

     $ LICENSE LOAD TEAMDATA-USER



3.9  TEAMDATA Shutdown Procedure

   TEAMDATA provides a shutdown procedure, TDA_STOP.COM. The instal-
   lation procedure copies this file to SYS$MANAGER. You do not need
   to run TDA_STOP.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 it if you need to reinstall the TEAMDATA kit.













3-6  Post-Installation Procedure

 







3.10  Installing TEAMDATA on a MicroVAX

   This section describes a problem that might occur on some MicroVMS
   systems. If you are not installing TEAMDATA on a MicroVAX, you can
   ignore this information.

   After you install TEAMDATA on your MicroVAX and run TEAMDATA, you
   might get an error message similar to the following:

     %DCL-W-ACTIMAGE, error activating image LIBRTL
     -CLI-E-IMGNAME, image file DAB1:[SYS0.][SYSLIB]LIBRTL.EXE;3
     -SYSTEM-F-PRIVINSTALL, shareable images must be installed to run
                            privileged image

   If this happens, you must install the image listed in the message.
   You must also modify the site-specific startup file to install
   the image. When you edit the site-specific startup file, the
   commands that install images such as this already exist, but are
   commented out. To activate the commands, remove the comment flags.
   You should install these images using the /SHARE qualifier.

   VMS returns the message once, for the first uninstalled image it
   encounters. Therefore, you might have to run TEAMDATA repeatedly
   to discover all the images that need to be installed.

   Enter these commands to install these images:

     $ INSTALL:==$INSTALL/COMMAND_MODE
     $ INSTALL ADD SYS$SHARE:LIBRTL/OPEN/HEADER/SHARE













                                     Post-Installation Procedure  3-7

 


















                                          Maintaining VAX TEAMDATA  4




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

   o  Handle server process problems

   o  Read a bugcheck dump file

   o  Handle a problem of insufficient global pages

   o  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.












                                        Maintaining VAX TEAMDATA  4-1

 







4.1  Server Process Problems

   TEAMDATA sometimes might not be able to create a server process
   to open a data table or spreadsheet. This might be due to certain
   system limitations or quota problems. In these cases, TEAMDATA
   might respond with the following error message:

                           CANNOT OPEN ENTRY
                           -----------------
        The entry you have selected cannot be opened for a reason unknown
        to TEAMDATA. Below is the error message returned by the system.
        Make a note of it and consult your system manager for further
        assistance.

        %SYSTEM-W-NONEXPR, nonexistent process

   In most cases, the last line of the message will give the reason
   for the failure. It might say "nonexistent process" as in the
   example above. This indicates that the server process was created
   sucessfully, but exited before it could open the table or sheet.
   In this case, the system accounting log can be used to determine
   the actual cause of the failure.

   Follow these steps:

   1. Log into a privileged account.

   2. Note the exact time. Enter:

        $ SHOW TIME

   3. Let the user reproduce the error message

   4. Enter the following command from the privileged account:

        $ ACCOUNTING/FULL/SINCE=<TIME>/USER=<USERNAME>







4-2  Maintaining VAX TEAMDATA

 







   In the example above, TIME is the time previously noted with the
   SHOW TIME command, and USERNAME is the name of the user experienc-
   ing the problem. For example:

     $ ACCOUNTING/FULL/SINCE=13:52/USER=JRAMONE

   The output gives the final status text of the server process. This
   status is an indication of what went wrong. Your system manager
   then can take the appropriate action to correct the problem.

4.2  Reading a Bugcheck Dump File

   Occasionally, a TEAMDATA 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.

   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




                                        Maintaining VAX TEAMDATA  4-3

 







   You can use this information in three ways:

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

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

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

   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 (%).

   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-4  Maintaining VAX TEAMDATA

 







4.3  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









                                        Maintaining VAX TEAMDATA  4-5

 







   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.

      ___________________________ 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.4  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.




4-6  Maintaining VAX TEAMDATA

 







   The following list of questions helps you collect supporting
   data that is often overlooked, but is essential to understanding
   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:

      o  Installing new prerequisite or optional software

      o  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 VAX TEAMDATA  4-7

 


















                             Installing TEAMDATA in ALL-IN-1 Menus  5




   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 in-
      stallation, your own configuration might be different from
      the one assumed here. If your installation is substantially
      different, you might need to contact your DIGITAL Software
      Services representative for assistance.

      ___________________________________________________________




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







5.1  Copying 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.

      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


   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.





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







   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 sub-
      menus. 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:

      o  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.

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

            TD   TEAMDATA

      o  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





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







      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 successfully
      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.














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







5.3  Recompiling 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 informa-
      tion about it, see the ALL-IN-1 System Manager's Guide.

   2. Remove and reinstall the newly compiled forms library:

        <OA$FBT_REMOVE_LIBRARY OA$LIB:OAFORM
        <OA$FBT_INSTALL_LIBRARY 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.














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







5.4  Running TEAMDATA from the ALL-IN-1 Menu

   Now, you can run TEAMDATA from the ALL-IN-1 menu. To do so:

   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 envi-
      ronment. The only differences between using TEAMDATA through
      ALL-IN-1 and using TEAMDATA from DCL are:

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

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

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

   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.




















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


















                                   Files, Images and Logical Names  A




   This appendix lists the logical names for the directories created
   or used by the TEAMDATA installation and the files transferred
   from the installation kit to those directories.

     SYS$HELP:     RPC$SWLUP.HLB              System Interconnect
     SYS$HELP:     TDA013.RELEASE_NOTES       TEAMDATA Release Notes
     SYS$HELP:     TDA$HELP.HLB               Main Help library
     SYS$HELP:     TDA$TRAIN.HLB              Training library

     SYS$MANAGER:  RPC$STARTUP.COM            System Interconnect
     SYS$MANAGER:  TDA_STARTUP.COM            TEAMDATA startup command file
     SYS$MANAGER:  TDA_STOP.COM               TEAMDATA stop command file

     SYS$MESSAGE   RPC$SWLMSG.EXE             System Interconnect
     SYS$MESSAGE   RPC$MSG.EXE                System Interconnect
     SYS$MESSAGE:  TDA$MSGSHR.EXE             Message shareable image










                                 Files, Images and Logical Names  A-1

 







     SYS$SHARE:    RPC$SHR.EXE                System Interconnect
     SYS$SHARE:    TDA$PRVSHR.EXE             Terminal control
     SYS$SHARE:    TDA$GRFSHR.EXE             Graph shareable image
     SYS$SHARE:    TDA$MENSHR.EXE             Menu definitions
     SYS$SHARE:    TDA$SHR.EXE                Main shareable image
     SYS$SHARE:    TDA$SRVDTE.EXE             Table server
     SYS$SHARE:    TDA$SRVFTE.EXE             Spreadsheet server
     SYS$SHARE:    TDA$SRVRGA.EXE             RALLY server

     SYS$SYSTEM:   TEAMDATA.EXE               Main TEAMDATA image


     TEAM$LIBRARY: TDAA1.COM                  ALL-IN-1 control
     TEAM$LIBRARY: TDACREDB.COM               Create new user database
     TEAM$LIBRARY: TDADCL.COM                 DCL subprocess control
     TEAM$LIBRARY: TDADEFDB.RBR               Default database
     TEAM$LIBRARY: TDADEFDB.RDB               Default database
     TEAM$LIBRARY: TDADEFDB.SNP               Default database
     TEAM$LIBRARY: TDASAMPLE.RBR              Sample database
     TEAM$LIBRARY: TDASAMPLE.RDB              Sample database
     TEAM$LIBRARY: TDASAMPLE.SNP              Sample database
     TEAM$LIBRARY: TDASYSDB.RDB               Public folder database
     TEAM$LIBRARY: TDASYSDB.SNP               Public folder database
     TEAM$LIBRARY: TDASYSDB_NEW.RBR           Public folder database
                                               (original)
     TEAM$LIBRARY: TDATSKCTL.COM              DCL subprocess control
     TEAM$LIBRARY: TDAWPSXAL.COM              WPS+ XAL control
     TEAM$LIBRARY: TDA_CLUST.GRG              Graph control file
     TEAM$LIBRARY: TDA_HISTO.GRG              Graph control file
     TEAM$LIBRARY: TDA_IVP_DTR.TDA            DATATRIEVE IVP
     TEAM$LIBRARY: TDA_IVP_MAIN.TDA           MAIN IVP
     TEAM$LIBRARY: TDA_IVP_SHEET.TDA          SHEET IVP
     TEAM$LIBRARY: TDA_IVP_TABLE.TDA          TABLE IVP (no graphics)
     TEAM$LIBRARY: TDA_IVP_TABLE_GRAPH.TDA    TABLE IVP for ReGIS
     TEAM$LIBRARY: TDA_LINE.GRG               Graph control file
     TEAM$LIBRARY: TDA_PIE.GRG                Graph control file
     TEAM$LIBRARY: TDA_SCAT.GRG               Graph control file
     TEAM$LIBRARY: TDA_SHOW_PROC.TDA          Show procedures UDP
     TEAM$LIBRARY: TDA_STACK.GRG              Graph control file



A-2  Files, Images and Logical Names

 


















                                             A Sample Installation  B




   This appendix illustrates a sample installation of VAX TEAMDATA
   on VMS V5.0. Your own installation might differ from this one,
   because you can make different choices during the procedure.

     $ @sys$update:vmsinstal tda013 sys$update

      VAX/VMS Software Product Installation Procedure V5.0

     It is 23-AUG-1988 at 14:24.
     Enter a question mark (?) at any time for help.

     %VMSINSTAL-W-DECNET, Your DECnet network is up and running.
     * Do you want to continue anyway [NO]? Y
     * Are you satisfied with the backup of your system disk [YES]?

     The following products will be processed:

       TDA V1.3

      Beginning installation of TDA V1.3 at 14:24






                                           A Sample Installation  B-1

 







     %VMSINSTAL-I-RESTORE, Restoring product saveset  A...
     %VMSINSTAL-I-RELMOVED , The product's release notes have been
      successfully moved to SYS$HELP.

         ***************************************************************
         *                                                             *
         *                   TEAMDATA version: V1.3                    *
         *                                                             *
         *                   Installation Procedure                    *
         *                       on Node: BIGVAX                       *
         *                 on 23-AUG-1988 14:25:00.24                  *
         *                                                             *
         *     Copyright (c) 1988 by Digital Equipment Corporation     *
         *                                                             *
         ***************************************************************

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

             Product:      TEAMDATA
             Producer:     DEC
             Version:      1.3
             Release Date: 19-AUG-1988

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

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

          *******************************************************************
          *                                                                 *
          *  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.          *
          *                                                                 *
          *******************************************************************

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








B-2  A Sample Installation

 







         *********************************************************************
         *                                                                   *
         *   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 4400 disk blocks.                *
         *      The default is recommended.                                  *
         *                                                                   *
         *      This directory already exists in: SYS$COMMON:[TEAMDATA]      *
         *                                                                   *
         *********************************************************************

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

         ****************************************************************
         *                                                              *
         *   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]?










                                           A Sample Installation  B-3

 







         *********************************************************************
         *                                                                   *
         *   SYSTEM MANAGER:                                                 *
         *                                                                   *
         *   Add to the system startup file: SYS$MANAGER:SYSTARTUP_V5.COM:   *
         *                                                                   *
         *            $ @SYS$MANAGER: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 saveset  B...
     %VMSINSTAL-I-RESTORE, Restoring product saveset  C...
     %VMSINSTAL-I-RESTORE, Restoring product saveset  D...
     %VMSINSTAL-I-RESTORE, Restoring product saveset  E...

         *********************************************************************
         *                                                                   *
         *   Installing Sample Database...                                   *
         *                                                                   *
         *********************************************************************

     %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories
     VAX TEAMDATA: Installing TEAMDATA images
     VAX TEAMDATA: Starting System Interconnect
     %RUN-S-PROC_ID, identification of created process is 00000077

      Installation of TDA V1.3 completed at 14:58

      VMSINSTAL procedure done at 14:58




B-4  A Sample Installation

 


















                                                  Index





  This index uses the following symbols:

  t      Entry occurrence in a table
  f      Entry occurrence in a figure
  e      Entry occurrence in an example


A                            AUTOGEN (cont'd.)
Access                         setting system
 granting remote  3-5            parameters  1-15
Accessing IBM databases      B
   1-6
ALL-IN-1  1-11               BUGCHECK dump file  4-3
  Installing TEAMDATA
    under  5-1 to  5-6       C
AUTHORIZE Utility  1-11      CDD
Authorizing quotas             and TEAMDATA  1-5
  user  3-4                  Changing system
AUTOGEN                         parameters  1-15
                             Checking privileges  1-7




                                                              Index-1

 







Checking process quotas      GBLPAGES parameter
   1-9                          (cont'd.)
Checking system                checking and setting
   parameters  1-11               1-13
CLISYMTBL                      insufficient  4-5
  SYSGEN parameter  2-13     GBLSECTIONS parameter
Conventions                    checking and setting
  keys  viii                      1-13
CSC                          Granting remote access
  See Customer Support          3-5
    Center                   Granting user privileges
Customer Support Center         3-3
   4-6
                             H
D
                             Hardware
Databases                      required  1-2
  sample  4-1
DATATRIEVE                   I
  and TEAMDATA  1-5, 3-3     IBM databases
Directories                    accessing  1-6
  logical names  A-1         Improving performance
Disk requirements  1-2          1-16
Dump file  4-3               Installation Verification
E                               Procedure
                               for TEAMDATA  2-14
Editing STARTUP.COM  3-2       for TEAMDATA and
F                                DATATRIEVE  2-16
                             Installer privileges  1-7
Files                        Installing TEAMDATA
  RDMMON.LOG  4-4              on a MicroVAX  3-7
  Run unit journal  3-4        under ALL-IN-1  5-1
  TDABUGCHK.DMP  4-3         IVP
  transferred from kit         See Installation
    A-1                          Verification
                                 Procedure
G
                             K
GBLPAGES parameter
                             Key conventions  viii




2-Index

 







L                            Parameters (cont'd.)
License Management             system  1-12
   Facility  1-3,  2-7            checking  1-11
Log files                    Performance considera-
  RDMMON.LOG  4-4               tions  1-16
Logical names                  memory management  1-17
  files transferred from       paging and swapping
    kit  A-1                     files  1-18
  TEAM$LIBRARY  2-10           system parameters  1-18
                             PGFLQUO  1-11
M                            Preparing account  1-6
                             Prerequisite hardware
MAXDETACH quota  1-11           1-2
MAXJOBS quota  1-11          Prerequisite software
Memory management  1-17         1-3
  WSDEFAULT value  1-17      Privileges
  WSEXTENT value  1-17         checking installing  1-7
  WSMAX value  1-17            granting to users  3-3
  WSQUOTA value  1-17          installer  1-7
MicroVAX                     Problems
  installing on  3-7           reporting  4-6
                             Process quotas  1-9
N                              checking  1-9

NETMBX privilege  3-3        Q
O                            Quotas
Optional software  1-5         MAXDETACH  1-11
  CDD  1-5                     MAXJOBS  1-11
  DATATRIEVE  1-5, 3-3         process
  RALLY  1-5                      checking  1-9
  VIDA  1-6                    user  3-4
  Xway  1-5                  R
P                            RALLY
Page file Quota  1-11          and TEAMDATA  1-5
Paging and swapping files    Rdb/VMS
   1-18                        and TEAMDATA  1-4
Parameters




                                                              Index-3

 







Rdb/VMS (cont'd.)            SYSGEN parameters
  SYS$SHARE:RDBSHR.EXE          (cont'd.)
    1-4                        CLISYMTBL  2-13
RDMMON.LOG file  4-4         SYSTARTUP.COM
Reading BUGCHECK dump          editing  3-2
   file  4-3                  System disk
Remote access                  backing up  2-2
  granting  3-5                restoring  2-3
Reporting problems  4-6      System parameters  1-12,
Required disk space  1-2        1-18
Required hardware  1-2         changing  1-15
Required software  1-3         checking  1-11, 2-2
  Rdb/VMS  1-4
Restoring system disk        T
   2-3                        TDABUGCHK.DMP
Restoring the sample           bugcheck dump file  4-3
   database  4-1              TDADEFDB.RDB  4-1
RUJ files  3-4               TDASAMPLE.RDB  4-1
Run unit journal files       TDASYSDBNEW.RDB  4-1
   3-4                        TEAM$LIBRARY logical
S                               name  2-10
                               moving  3-2
Sample database  4-1         TMPMBX privilege  3-3
Sample installation  B-1
Shutdown procedure  3-6      U
Software                     User quotas
  optional  1-5                authorizing  3-4
     CDD  1-5
     DATATRIEVE  1-5, 3-3    V
     RALLY  1-5
     VIDA  1-6               VAX DATATRIEVE
     Xway  1-5                 See DATATRIEVE
  required  1-3              VAX RALLY
     Rdb/VMS  1-4              See RALLY
Startup procedure            VAX Rdb/VMS
  editing STARTUP.COM  3-2     See Rdb/VMS
Symbol definitions           VAX Xway
  overflow error  2-13
SYSGEN parameters              See Xway





4-Index

 







VIDA                         W
  and TEAMDATA  1-6
VMSINSTAL                    WSDEFAULT value  1-17
  preparing to run  2-2      WSEXTENT value  1-17
VMSINSTAL Command            WSMAX value  1-17
   Procedure  2-4 to  2-13    WSQUOTA value  1-17

                             X

                             Xway
                               and TEAMDATA  1-5































                                                              Index-5
