DECdecision Installation and System Management Guide DECdecision is a decision-support environment with database, spreadsheet, and charting components, and an application tape recorder. This guide describes how to install and maintain DECdecision on a VMS system. Operating System and Version: OpenVMS Version 5.4 or higher Software Version: DECdecision Version 2.0 NOTICE The information in this document is subject to change without notice and should not be construed as a commitment by Touch Technologies, Inc. Touch Technologies, Inc. assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. __________ Copyright ©1995 Touch Technologies, Inc. All Rights Reserved The following are trademarks of Touch Technologies, Inc., and may be used only to describe products of Touch Technologies, Inc.: DYNAMIC TAPE ACCELERATOR INTOUCH DYNAMIC LOAD BALANCER CleanDisk PLUS REMOTE DEVICE FACILITY The following are trademarks of Digital Equipment Corporation: CDA, DATATRIEVE, DDIF, DECalc, DECchart, DECdecision, DECpresent, DECquery, DECwindows, DECwrite, DTIF, DX, LiveLink, RdbAccess for VAX RMS, Rdb/VMS, TEAMDATA, ULTRIX, VAX, VAX RMS, VIDA, OpenVMS, and the DIGITAL logo. ________________________ December 1995 __________________________________________________________________ Contents ____________________________________________________________ PREFACE vii __________________________________________________________________ CHAPTER 1 PREPARING FOR INSTALLATION 1-1 ____________________________________________________________ 1.1 CHECKING THE DISTRIBUTION KIT 1-2 ____________________________________________________________ 1.2 PREREQUISITE HARDWARE 1-2 ____________________________________________________________ 1.3 PREREQUISITE SOFTWARE 1-2 ____________________________________________________________ 1.4 REQUIRED OPERATING SYSTEM COMPONENTS 1-3 ____________________________________________________________ 1.5 REGISTERING YOUR LICENSE 1-3 ____________________________________________________________ 1.6 DECDECISION DIRECTORIES 1-4 ____________________________________________________________ 1.7 VAXCLUSTER CONSIDERATIONS 1-5 ____________________________________________________________ 1.8 PREPARING YOUR SYSTEM AND THE INSTALLING ACCOUNT 1-5 1.8.1 Checking Privileges of the Installing Account ________________________________ 1-5 1.8.2 Checking Quotas of the Installing Account ________________________________ 1-6 1.8.3 System Disk Space Requirements _________ 1-7 1.8.4 User Disk Space Requirements ___________ 1-7 1.8.5 System Parameter Values ________________ 1-8 1.8.5.1 Checking Parameter Values o 1-9 1.8.5.2 Calculating GBLPAGES and GBLSECTIONS Parameter Values o 1-9 1.8.5.3 Changing Parameter Values with AUTOGEN o 1-10 ____________________________________________________________ 1.9 MAKE SURE RDB/VMS IS RUNNING 1-11 iii Contents ____________________________________________________________ 1.10 BACKING UP YOUR SYSTEM DISK 1-11 ____________________________________________________________ 1.11 DETERMINING AND REPORTING PROBLEMS 1-11 ____________________________________________________________ 1.12 PRE-INSTALLATION CHECK LIST 1-12 __________________________________________________________________ CHAPTER 2 INSTALLING DECDECISION 2-1 ____________________________________________________________ 2.1 INSTALLATION OVERVIEW 2-1 ____________________________________________________________ 2.2 RUNNING THE VMSINSTAL COMMAND PROCEDURE 2-2 __________________________________________________________________ CHAPTER 3 POST-INSTALLATION PROCEDURES 3-1 ____________________________________________________________ 3.1 EDITING SYSTEM STARTUP AND SHUTDOWN FILES 3-1 ____________________________________________________________ 3.2 ACTIVATING DECDECISION ON A VAXCLUSTER 3-2 ____________________________________________________________ 3.3 USER ACCOUNT REQUIREMENTS 3-2 3.3.1 User Account Privileges ________________ 3-2 3.3.2 User Account Quotas ____________________ 3-3 ____________________________________________________________ 3.4 REBOOTING THE SYSTEM 3-4 ____________________________________________________________ 3.5 RUNNING THE INSTALLATION VERIFICATION PROCEDURE SEPARATELY 3-4 ____________________________________________________________ 3.6 RUNNING DECDECISION 3-4 ____________________________________________________________ 3.7 EXTENSION CHANGE FOR QUERY MACROS 3-5 ____________________________________________________________ 3.8 POST-INSTALLATION CHECK LIST 3-6 iv Contents __________________________________________________________________ CHAPTER 4 MANAGING YOUR DECDECISION ENVIRONMENT 4-1 ____________________________________________________________ 4.1 PERFORMANCE CONSIDERATIONS 4-1 4.1.1 Working Set Values _____________________ 4-1 4.1.2 Global Pages and Global Sections _______ 4-2 ____________________________________________________________ 4.2 MANAGING QUERY FILES AND DATABASES 4-3 4.2.1 Using DECdecision with DATATRIEVE Domains ________________________________ 4-3 4.2.2 Granting Database Access to Users on Other Systems __________________________ 4-4 ____________________________________________________________ 4.3 DECDECISION FATAL ERRORS 4-4 ____________________________________________________________ 4.4 USING LOGICAL NAMES WITH DECDECISION 4-5 __________________________________________________________________ APPENDIX A SAMPLE DECDECISION INSTALLATION A-1 __________________________________________________________________ APPENDIX B SAMPLE DECDECISION UPGRADE FROM A PREVIOUS VERSION B-1 __________________________________________________________________ APPENDIX C DECDECISION FILES C-1 __________________________________________________________________ INDEX __________________________________________________________________ EXAMPLES 3-1 Changing Macro Names _________________________ 3-5 v Contents __________________________________________________________________ TABLES 1-1 DECdecision Directories ______________________ 1-4 1-2 Minimum Installing Account Quotas ____________ 1-6 1-3 Disk Requirements ____________________________ 1-7 1-4 Required Minimum System Parameter Values _____ 1-8 1-5 Pre-Installation Check List __________________ 1-12 2-1 DECchart Component Installation ______________ 2-1 2-2 DECdecision Save Set Contents ________________ 2-2 3-1 Minimum User Account Quotas __________________ 3-3 3-2 Post-Installation Check List _________________ 3-6 vi __________________________________________________________________ Preface DECdecision is a decision-support environment with database, spreadsheet, and charting components, and an application tape recorder. Purpose of This Guide This guide describes how to install and maintain DECdecision on the VMS operating system. You should review the entire guide before you start the installation. Who Should Use This Guide This guide is for VMS system managers or others responsible for installing system software. To install the DECdecision software, you must have access to a privileged account such as the SYSTEM account, and you must be familiar with the VMS installation procedure, VMSINSTAL.COM. Structure of This Guide The guide has four chapters and three appendixes. Chapter 1 describes installation prerequisites and pre-installation procedures. Chapter 2 describes the installation procedure. Chapter 3 describes required post-installation procedures. Chapter 4 provides information about managing your DECdecision environment. Appendix A shows a sample printout of a first-time installation. Appendix B shows a sample printout of an upgrade from DECdecision Version 1.5 to Version 2.0. Appendix C shows the files that are transferred to your system when you install DECdecision. For More Information Refer to the following documentation for more information about DECdecision: o DECdecision Overview-provides a tutorial and general information on using DECdecision o Component online help-provides a full set of information about using a component o DECdecision Calc Macro Guide-describes how to use the Calc Macro Language vii Preface o DECdecision Release Notes-describes problems and workarounds for this version of DECdecision For more information about DECwindows, see the VMS DECwindows User's Guide. For more information about the VMSINSTAL command procedure, see one of the following manuals: o VMS System Manager's Manual, in the VMS base documentation set o Guide to Setting Up a VMS System, in the VMS system management kit. Conventions The following conventions are used in this guide: In procedures, key names are shown enclosed to indicate that you press a key on the keyboard. A sequence such as indicates that you must hold down the key labeled Ctrl while you press another key or a pointing device button. () In format descriptions, parentheses indicate that, if you choose more than one option, you must enclose the choices in parentheses. [] In format descriptions, brackets indicate that whatever is enclosed is optional; you can select none, one, or all of the choices. {} In format descriptions, braces surround a required choice of options; you must choose one of the options listed. user input In the Bookreader, information you must enter from the keyboard is indicated by boldface text. italic text Italic text represents information that can vary in system messages (for example, Internal error number). UPPERCASE Uppercase letters indicate that you must enter TEXT a command (for example, enter OPEN/READ). Uppercase letters also indicate the name of a routine, the name of a file, the name of a file protection code, or the abbreviation of a system privilege. DECdecision The term DECdecision refers to the DECdecision[TM] software. DECchart The term DECchart refers to the DECchart[TM] software. viii Preface Query The term Query refers to the Query[TM] software. ix __________________________________________________________________ 1 Preparing for Installation This chapter describes tasks that you must complete before installing DECdecision. Installing DECdecision is similar to installing other VMS layered products. You must do the following: o Take an inventory of the software distribution kit. o Make sure that your system has the prerequisite hardware, and that it has enough memory and available disk space to install and run DECdecision. o Make sure that your system has the required VMS operating system components and the prerequisite software. o If you are installing on a VAXcluster, decide how best to install DECdecision, depending on your configuration. o Register and load your DECdecision license. 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 Back up your system disk. o Advise your users when the installation will take place and how long it will take. The full installation takes approximately 45 minutes on a VAX 3900 system. Your time may vary depending on your system configuration and the type of installation media. Once you have prepared your system, you can then perform the installation procedure as described in Chapter 2, and any necessary post-installation procedures as described in Chapter 3. 1-1 Preparing for Installation __________________________________________________________________ 1.1 Checking the Distribution Kit Each DECdecision distribution kit contains: o A bill of materials (BOM) and indented bills report (BIL) o The distribution medium for the DECdecision software o Documentation for the product Media Only kits include just the installation guide. o The software license If you are upgrading from a previous version of DECdecision, you do not receive a new license. Your current license is still valid. To ensure that you have a complete kit, check the kit contents against the bill of materials and the indented bills report. Check also that you received the correct distribution medium, labeled as DECdecision Version 2.0. If your kit is damaged or parts of it are missing, contact your Digital representative. __________________________________________________________________ 1.2 Prerequisite Hardware DECdecision runs on all hardware configurations supported by VMS DECwindows Motif Version 1.1 with 8 MB or greater of memory. For more information, refer to your Software Product Description and your System Support Addendum. __________________________________________________________________ 1.3 Prerequisite Software To install DECdecision, you must have: 1 A valid VMS operating system configuration running OpenVMS Version 5.4 or higher and VMS DECwindows Motif Version 1.1 or higher. 2 Your DECdecision software license registered. See Section 1.5 for more information. 3 One of the following Rdb/VMS kits: - Rdb/VMS Full Development Kit Version 4.1 or higher - Rdb/VMS Interactive Kit Version 4.1 or higher - Rdb/VMS Run-Time Kit Version 4.1 or higher 1-2 Preparing for Installation - Oracle Rdb for OpenVMS VAX 6.1 or higher ____________________ Note ____________________ Previous versions of DECdecision also included the Rdb/VMS Run-Time Kit. This is no longer true for DECdecision V2.0. Before installing DECdecision, you must install the prerequisite version of Rdb/VMS. ____________________ Note ____________________ RDB is NOT required for installation of DECdecision V2.0. However, if RDB has not been installed prior to installing DECdecision V2.0, the Query component will not be installed. The Query component requires RDB to be present. For more information, refer to your Software Product Description and your System Support Addendum. __________________________________________________________________ 1.4 Required Operating System Components DECdecision requires the following OpenVMS Version 5.4 or higher components: o VMS required files (BASE) o Network support (NETWORK) o Programming support (PROG) o Secure user's environment (USER) o Utilities (UTIL) If your system does not meet these requirements, the installation will fail. You must install the required software using VMSTAILOR before performing the DECdecision installation. __________________________________________________________________ 1.5 Registering Your License You must register and load your DECdecision software license. The information you need is in the Product Authorization Key (PAK) shipped with the product. The PAK is a paper certificate that contains data about your license. You should register the license before you install DECdecision. If you do not, the Installation Verification Procedure (IVP) will fail. To register the license for the initial installation, first log in to a privileged account such as the system manager's account, SYSTEM. Then use the License Management Facility 1-3 Preparing for Installation to perform the registration, choosing one of the following procedures (the second method is faster for experienced users): o Invoke the SYS$UPDATE:VMSLICENSE.COM procedure. When prompted for information, respond with data from your Product Authorization Key (PAK). o Issue the DCL command LICENSE REGISTER with the appropriate qualifiers that correspond to information on the PAK. If you plan to use DECdecision on more than one node in a VAXcluster, you must perform a LICENSE LOAD on the other nodes after you complete this installation. See Section 3.2 for more information. For complete information on using the License Management Facility, see your VMS documentation set. __________________________________________________________________ 1.6 DECdecision Directories During the installation, DECdecision creates the default root directory SYS$COMMON:[DECISION], plus a subdirectory for each component. Table 1-1 lists the directories and their logical names. Table_1-1_DECdecision_Directories______________________________ Component___Directory___________________Logical_Name___________ DECdecision SYS$COMMON:[DECISION] DECISION$LIBRARY Query SYS$COMMON:[DECISION.QUERY] DECISION$QUERY_LIBRARY Builder SYS$COMMON:[DECISION.BUILDERDECISION$BUILDER_ LIBRARY Calc SYS$COMMON:[DECISION.ECALC] DECISION$ECALC_LIBRARY DECchart SYS$COMMON: CHART$EXAMPLES ____________[SYSHLP.EXAMPLES.DECCHART]_________________________ ____________________ Note ____________________ If you are upgrading from DECquery to DECdecision V2.0, the DECdecision installation will continue to use your DECquery databases in DECquery-library and also your users' DECquery databases. 1-4 Preparing for Installation __________________________________________________________________ 1.7 VAXcluster Considerations You can install DECdecision on a VAXcluster. In a common-environment VAXcluster, you can install DECdecision on the VAXcluster boot node. This allows more than one VAX processor to share the same DECdecision software. In a multiple-system VAXcluster, you can install DECdecision on each system disk in the cluster. You must make sure that each node where you plan to install or run DECdecision meets the minimum system parameter value requirements. See Section 1.8.5 for a list of required system parameter values. After you install DECdecision, you must run the DECdecision startup command procedure (SYS$STARTUP:DECISION$STARTUP.COM) and load the software license on every cluster node where you want to run DECdecision. See Section 3.1 and Section 3.2 for more information. __________________________________________________________________ 1.8 Preparing Your System and the Installing Account This section tells you which characteristics of your system and installing account you need to check before you install DECdecision. These characteristics include: o Account privileges o Account quotas o Disk space requirements o System parameters You must adjust those characteristics that do not match the minimum values required for installing and running DECdecision. ___________________________ 1.8.1 Checking Privileges of the Installing Account The account you use to install DECdecision must have the user privilege SETPRV. As one of the first actions, the VMSINSTAL command procedure grants all privileges (except BYPASS) to the process that invokes it. This command succeeds only if the account has SETPRV. On most systems, the SYSTEM account has SETPRV and is used to install software. The procedures described in this installation guide refer to the SYSTEM account, but they are the same for any account with SETPRV. 1-5 Preparing for Installation ___________________________ 1.8.2 Checking Quotas of the Installing Account The installing account must have sufficient quotas to perform the installation and run the Installation Verification Procedure (IVP). Table 1-2 summarizes the minimum account quotas required. Table_1-2_Minimum_Installing_Account_Quotas____________________ Account Quota__________Value_____Description___________________________ ASTLM 100 AST queue limit BYTLM 30,000 Buffered I/O byte count limit ENQLM 2000 Lock queue limit FILLM 100 Open file limit MAXDETACH 0 Maximum number of detached processes PGFLQUO 20,000 Paging file limit PRCLM 1 Subprocess creation limit WSEXTENT 2048 Working set extent WSQUO__________512_______Working_set_quota_____________________ Account quotas are stored in the file SYSUAF.DAT. Use the VMS Authorize Utility to verify and change user account quotas. Follow these steps: 1 Set your directory to SYS$SYSTEM and then run AUTHORIZE as follows: $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> 2 At the AUTHORIZE prompt (UAF>), use the SHOW command with an account name to check your account. For example: UAF> SHOW SMITH 3 To change a quota, use the MODIFY command at the UAF> prompt. The MODIFY command uses the following format: MODIFY account-name /quota-name=nnnn For example, to change the FILLM quota to 100 for the SMITH account, then exit from the Authorize Utility, you would enter the following: 1-6 Preparing for Installation UAF> MODIFY SMITH /FILLM=100 UAF> EXIT After you exit from the utility, the VMS system displays messages indicating whether changes were made. Once the changes have been made, you must log out and log in again for the new quotas to take effect. For more information on modifying account quotas, see the description of the AUTHORIZE utility in the Guide to Setting Up a VMS System. ___________________________ 1.8.3 System Disk Space Requirements Your system must have sufficient disk storage space to accommodate the installation. Table 1-3 lists the required free disk blocks. Table_1-3_Disk_Requirements____________________________________ Free Blocks Required During Blocks Used After Installation_______Installation________________________________ 48,000_____________29,000______________________________________ Use the DCL command SHOW DEVICE to determine the number of free blocks that are available on the system disk, as follows: $ SHOW DEVICE SYS$SYSDEVICE If the disk does not have enough free blocks, delete unnecessary files to provide the space required. ___________________________ 1.8.4 User Disk Space Requirements When a user runs the Query component for the first time, Query creates a default user database. The two files, named DECISION$QUERY_DB.RDB and DECISION$QUERY_DB.SNP, require a total of 1705 free disk blocks. Over time, more disk space will be required as the user adds new tables to the database or creates new databases. 1-7 Preparing for Installation ___________________________ 1.8.5 System Parameter Values Table 1-4 lists the minimum system parameter values required for DECdecision installation and use. If your parameters are higher, do not lower them. Other applications on your system may require higher values than these minimum values. On a VAXcluster, you must adjust not only the system parameters of nodes on which you install DECdecision, but also the nodes on which you intend to run DECdecision. Table_1-4_Required_Minimum_System_Parameter_Values_____________ System Parameter______Minimum_Value__________Type_____________________ CHANNELCNT A number larger than the largest FILLM used on the system. DECdecision requires a minimum FILLM of 100. See Table 3-1. CLISYMTBL[1] 500 Dynamic GBLPAGES 6,500 (unused global pages) GBLPAGFIL 2048 GBLSECTIONS 25 (unused global sections) LOCKIDTBL 256 LOCKIDTBL_ 2048 Dynamic MAX MAXBUF 1584 Dynamic PQL_DBYTLM 20,000 Dynamic PROCSECTCNT 64 RESHASHTBL 512 SRPCOUNT 1024 SRPCOUNTV 2048 VIRTUALPAGECNT 20,000 _______________________________________________________________ [1]Required only for installation _______________________________________________________________ 1-8 Preparing for Installation _____________________ 1.8.5.1 Checking Parameter Values To check the value of a system parameter, enter the following command at the DCL prompt: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> At the SYSGEN> prompt, use the SHOW command to display the value of each system parameter. The value displayed in the Current column should equal or exceed the value of each parameter listed in Table 1-4. For example, the following command displays the value for the MAXBUF system parameter: SYSGEN> SHOW MAXBUF After you finish checking parameter values, use the EXIT command to return to DCL level. _____________________ 1.8.5.2 Calculating GBLPAGES and GBLSECTIONS Parameter Values The values for GBLPAGES and GBLSECTIONS in Table 1-4 indicate that you must have at least 6,500 unused global pages and 25 unused global sections available for the installation. To calculate the number of unused global pages and global sections on your system, perform these steps: 1 Use the DCL F$GETSYI lexical function to determine the number of free global pages and global sections: $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES") $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS") 2 If the number of unused global pages or global sections is less than the number specified in Table 1-4, you must increase the value using the AUTOGEN command procedure, as shown in Section 1.8.5.3. 1-9 Preparing for Installation _____________________ 1.8.5.3 Changing Parameter Values with AUTOGEN Use the AUTOGEN command procedure to change system parameters. To change system parameters with AUTOGEN: 1 Edit the following file: SYS$SYSTEM:MODPARAMS.DAT For example, to increase the setting for the GBLPAGES system parameter by 2000, add this line to the file: ADD_GBLPAGES = 2000 2 Run the AUTOGEN procedure to recalculate your system parameters and reboot the system. Enter the following command at the DCL prompt: $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT When you specify REBOOT, AUTOGEN performs an automatic system shutdown and reboot. Any users logged on to the system are immediately disconnected during the shutdown. The automatic reboot puts the new parameter values into effect. AUTOGEN automatically adjusts some of the SYSGEN parameters based on the consumption of resources since the last reboot. If you do not want to take advantage of this automatic adjustment, include the NOFEEDBACK parameter on the AUTOGEN command line as well. For example: $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT NOFEEDBACK For more information about using AUTOGEN, see the instructions on modifying system parameters in the Guide to Setting Up a VMS System. 1-10 Preparing for Installation __________________________________________________________________ 1.9 Make Sure Rdb/VMS is Running Make sure Rdb/VMS is running before installing DECdecision. If Rdb/VMS is not running, the installation procedure cannot restore the DECdecision sample databases. To start Rdb/VMS, use the following DCL command: $ @SYS$MANAGER:RMONSTART.COM ____________________ Note ____________________ RDB is not required with DECdecision V2.0. However, if it is not installed and started prior to the installation of DECdecision V2.0, the Query component will not be installed. __________________________________________________________________ 1.10 Backing Up Your System Disk At the beginning of the installation, VMSINSTAL asks if you have backed up your system disk. Digital recommends that you do a system disk backup before installing any software. If a system failure occurs at a critical point during the installation, some of the files could be corrupted. Therefore, you should back up your system disk before attempting any software installation. For more information on backing up your system disk, see the section on the Backup Utility in the Guide to Maintaining a VMS System. __________________________________________________________________ 1.11 Determining and Reporting Problems If you encounter a problem while using DECdecision, report it to Digital. Depending on the nature of the problem and the type of support you have, you can take one of the following actions: o Call Digital if your software contract or warranty agreement entitles you to telephone support. o Submit a Software Performance Report (SPR). o Fill out and submit a Reader's Comments form if the problem has to do with the DECdecision documentation. There are Reader's Comments forms at the back of each manual. Use the form from the manual in which you found the error. Include the section number and page number. 1-11 Preparing for Installation Review the Software Product Description (SPD) and Warranty Addendum for an explanation of your warranty. If you encounter a problem during the warranty period, report the problem as indicated above or follow alternate instructions provided by Digital for reporting SPD nonconformance problems. __________________________________________________________________ 1.12 Pre-Installation Check List Table 1-5 summarizes the tasks you must perform before installing DECdecision. Check to make sure that you have performed all these tasks before proceeding with the installation. Table_1-5_Pre-Installation_Check_List__________________________ Task________________________For_More_Information_______________ Check that you have the See Section 1.2 and Section 1.3 prerequisite hardware and software Register and load your See Section 1.5 license Check privileges and See Section 1.8.1 and Section 1.8.2 quotas of the installing account Check that you have See Section 1.8.3 enough disk space Check system parameters See Section 1.8.5 Make sure Rdb/VMS is See Section 1.9 running if Query is to be installed Back_up_your_system_disk____See_Section_1.10___________________ 1-12 __________________________________________________________________ 2 Installing DECdecision This chapter describes the procedure for installing DECdecision and running the Installation Verification Procedure (IVP). Before you begin installing DECdecision, make sure that your system meets the requirements outlined in Chapter 1. The full installation takes approximately 45 minutes on a VAX 3900 system. Your time may vary depending on the configuration of your system, the choices you make during the installation, and the type of media you use. __________________________________________________________________ 2.1 Installation Overview There are two varieties of DECdecision installation: o Installing DECdecision for the first time Appendix A shows a first-time installation. o Upgrading from a previous version of DECdecision Appendix B shows an installation upgrade from DECdecision Version 1.5 to Version 2.0. During each installation, DECdecision checks to see if your system has the correct version of the DECchart component. If the DECchart component is out of date or missing, then DECdecision installs the correct version. If the correct version of DECchart is already on the system, DECdecision does not replace it. Table 2-1 explains how the DECdecision installation deals with different versions of the DECchart component. Table 2-2 shows which save sets contain the files for the DECdecision and DECchart components. Table_2-1_DECchart_Component_Installation______________________ Current DECchart Version____________DECdecision_Installation_Action_____________ None Installs DECchart Version 2.0. DECchart Version Prints a message and asks if you want to 1.0 or 1.1 proceed. If you answer YES, it installs or 1.5 DECchart Version 2.0. 2-1 Installing DECdecision Table_2-1_(Cont.)_DECchart_Component_Installation______________ Current DECchart Version____________DECdecision_Installation_Action_____________ DECchart Version Prints a message and asks if you want 2.0 to re-install DECchart Version 2.0. For versions greater than V2.0, DECdecision will always install the higher version if it is not already installed. The current ___________________version_is_V2.0C.___________________________ Table_2-2_DECdecision_Save_Set_Contents________________________ Component__Save_Sets___________________________________________ DECdecisionA,D,F DECchart___B,C,E_______________________________________________ __________________________________________________________________ 2.2 Running the VMSINSTAL Command Procedure Use the VMSINSTAL command procedure to install DECdecision. For more information about VMSINSTAL, refer to the following books in your VMS documentation set: o VMS System Manager's Manual, in the VMS base documentation set o Guide to Setting Up a VMS System, in the VMS system management subkit. If VMSINSTAL detects a problem during the installation procedure, it notifies you and asks if you want to continue. To stop the installation and correct the problem, enter NO or press RETURN. After you have made the correction, you can restart the installation. To stop the installation procedure at any time, press Ctrl/Y. The installation procedure deletes all the files it has created up to that point and exits. You can then restart the installation. Follow these steps to install DECdecision: 1 Log in to the SYSTEM account. Log in at the operator's console terminal under the system manager's account, SYSTEM. 2 Notify the users. Send a message requesting that all users log out. Use the DCL REPLY command to inform users of the schedule for the installation. Use the SET LOGINS command to prevent others from logging in: 2-2 Installing DECdecision $ REPLY/USER "Installation starting in 5 minutes. Please log out." $ SET LOGINS/INTERACTIVE=0 3 Invoke VMSINSTAL. Enter the following command line to run VMSINSTAL.COM: $ @SYS$UPDATE:VMSINSTAL DECISION020 ddcu: OPTIONS N where: o @SYS$UPDATE:VMSINSTAL invokes VMSINSTAL o DECISION020 is the save set name for the DECdecision software o ddcu: is the device specification for the distribution medium, for example, MUA0:. o OPTIONS N is an optional parameter indicating that you want to see the Release Notes question. If you do not include the OPTIONS N parameter, VMSINSTAL does not ask you about the Release Notes. Digital recommends that you review the Release Notes before proceeding with the installation. After you invoke VMSINSTAL, you see the following message: VAX/VMS Software Product Installation Procedure V5.4 It is 20-JUL-1995 at 09:17 Enter a question mark (?) at any time for help. 4 Answer the backup question. The installation procedure asks if you have backed up your system disk: * Are you satisfied with the backup of your system disk [YES]? If you have not backed up your system disk, you should not continue with the installation until you do so. If you need to back up the system disk, enter NO. VMSINSTAL exits and returns you to the DCL prompt. Back up your system disk, and then start VMSINSTAL again. If you have already backed up the system disk, press RETURN to continue. 5 Mount the media. You receive instructions to mount the distribution medium on the device you specified when you invoked VMSINSTAL (MUA0: in this example): 2-3 Installing DECdecision Please mount the first volume of the set on MUA0:. * Are you ready? Mount the distribution medium and enter YES to indicate that you are ready to continue. The following messages appear on your terminal: %MOUNT-I-MOUNTED, DECIS mounted on _MUA0: The following products will be processed: DECISION V2.0 Beginning installation of DECISION V2.0 at 09:17 %VMSINSTAL-I-RESTORE, Restoring product save set A... 6 Print and read the Release Notes. If you specified OPTIONS N when you invoked VMSINSTAL, you are now asked to choose one of the four options for reviewing the Release Notes: Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: Review the Release Notes in case they contain any information about changes in the installation procedures. Selecting option 2 prints a copy of the Release Notes. You are prompted for a print queue: * Queue name [SYS$PRINT]: Press RETURN to print the Release Notes on SYS$PRINT, or type a different queue name and press RETURN. You receive a message similar to the following: Job 810 (queue SYS$PRINT, entry 1295) started on SYS$PRINT If you selected options 1 or 3, the Release Notes are displayed. 7 Decide whether or not to continue. 2-4 Installing DECdecision The installation procedure asks if you want to continue: * Do you want to continue the installation? [NO]? %VMSINSTAL-I-RELMOVED, The product's release notes have been moved to SYS$HELP. Enter YES to continue. Otherwise, press RETURN. In either case, the Release Notes are moved to the SYS$HELP directory. The Release Notes are contained in the following file, which you may read or print later: SYS$HELP:DECISION020.RELEASE_NOTES. You then see the following message: ************************************************************ * * * DECdecision V2.0 * * Integrated Decision Support Package * * * * Installation Procedure * * * ************************************************************ At this point, the installation procedure checks to make sure your system is running the minimum required version of VMS. If your system does not meet the minimum requirements, the installation procedure issues an error message and then exits. 8 Answer the license registration question. The installation procedure asks if you have registered a DECdecision product authorization key, using the License Management Facility (LMF): Product: DECDECISION-USER Producer: DEC or TTI Version: 2.0 Release Date: 15-JUL-1995 * Does this product have an authorization key registered and loaded? You must have registered and loaded the product authorization key or the Installation Verification Procedure (IVP) will fail. Enter YES if your PAK is registered and loaded. If you enter NO, the installation procedure warns you that the IVP will fail. The installation then proceeds. See Section 1.5 for information about registering your product authorization key. 2-5 Installing DECdecision 9 Read messages. The following messages display: Checking user parameters Checking system parameters Testing dependent product versions %VMSINSTAL-I-RESTORE, Restoring product save set B ... At this point, the installation procedure checks to make sure your system is running the minimum required version of VMS DECwindows Motif. If your system does not meet the minimum requirements, the installation procedure issues the following error message and then exits: %VMSINSTAL-E-BADDW, This kit requires VMS DECwindows Motif V1.1 or later to install 10 Answer the DECchart upgrade question. DECdecision installs DECchart Version 2.0. The following messages display if your system has an earlier version of DECchart: This kit requires DECchart V2.0 or later ********************************************************** DECchart V2.0 will be installed since an earlier version exists on your system. ********************************************************** * Do you want to proceed [YES]? Press RETURN to continue the installation. Your message may vary depending on whether you have DECchart installed and what version it is. If you have no version of DECchart currently installed on your system, you see the following message: This kit requires DECchart V2.0 or later ********************************************************** DECchart V2.0 will be installed since it does not exist on your system. ********************************************************** See Table 2-1 for a description of the ways DECdecision handles the DECchart installation. 2-6 Installing DECdecision 11 Create the library directories. This question differs depending on whether you are installing DECdecision for the first time or upgrading from a previous version of DECdecision. The installation procedure asks where you would like to place the library root directories. o First time installation: The DECdecision product creates a tree of library directories. A subdirectory is created for each component. * Where would you like to place the DECISION V2.0 library root [SYS$COMMON:[DECISION]]: Press RETURN to create the default library, or you can specify another directory. The following messages display: %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[DECISION]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[DECISION.BUILDER]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[DECISION.ECALC]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[DECISION.QUERY]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSTEST.DECISION$IVP]. o Upgrade or re-installation: The directory DECISION$LIBRARY currently exists on your system. * Would you like to place the DECISION V2.0 library root there [YES]? Press RETURN to use the default library, or you can specify another directory. The following messages display: %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSTEST.DECISION$IVP]. %CREATE-I-EXISTS, VMI$ROOT:[SYSTEST.DECISION$IVP] already exists 12 Decide whether or not to upgrade the default user database. You see this question only if you are upgrading or reinstalling DECdecision. The installation procedure asks if you want to replace the default user database: 2-7 Installing DECdecision DECdecision has a default database. This is copied to new user's accounts when they first use DECdecision. This database is installed in DECISION$QUERY_LIBRARY Your system already has a default user database. * Do you want to replace it [NO]? ____________________ Note ____________________ If you are upgrading from DECquery, this message will be referring to your database in your DECQUERY-library. If you have never modified your default user database, enter YES to replace it. If you have made modifications, press RETURN. 13 Decide whether or not to run the IVP. The installation procedure asks if you want to run the Installation Verification Procedure (IVP): * Do you want to run the IVP after the installation [YES]? The DECdecision IVP checks to be sure the installation is successful. Digital recommends that you run the IVP. Press RETURN. 14 Specify an IVP display device. You must specify a workstation on which to display the IVP: The DECdecision IVP requires that a display device be defined (using the SET DISPLAY command). Please enter the node name of the workstation on which to display the IVP. * Enter node name (or Return to not run IVP): You must specify the node name of a workstation on which security is set up to allow display of the IVP. To ensure that your display is set up correctly, go to the Session Manager Options menu and select the Security option. When the list of authorized users displays, add the Node and Username of the system on which you are installing DECdecision. 2-8 Installing DECdecision For example, if you are installing DECdecision from the SYSTEM account on workstation node MYNODE, then you must add MYNODE::SYSTEM to the security database. If you have SET HOST 0 from your own account to use the SYSTEM account, then you must add 0::SYSTEM to the security database. See the DECwindows User's Guide for details on the Session Manager's security database. If you do not have a workstation available, you may press RETURN and the IVP will not be run. See Chapter 3 for directions on running the IVP after the installation. 15 Decide whether or not to purge files. The installation procedure asks if you want to purge (delete) old versions of files replaced by this installation: * Do you want to purge files replaced by this installation [YES]? Purging is recommended. Press RETURN to purge the old files. However, if you need to keep files from the previous version, enter NO. 16 Decide whether or not to continue. The installation procedure displays a time estimate and then asks if you want to continue: To complete the installation on a standalone VAX 11/780 will take approximately: 30 minutes to install 11 minutes to run the IVP All required questions have been asked. You can terminate the installation procedure at this time. * Do you want to continue the installation [YES]? Press RETURN to continue the installation. 17 Check informational messages. The installation procedure displays a series of messages as it performs the following installation tasks: o Restores files o Reminds you to edit SYSTARTUP_V5.COM or SYSTARTUP_VMS.COM for 6.0 or higher o Creates the DECchart directories 2-9 Installing DECdecision o Transfers files to their directories o Installs the Query databases %VMSINSTAL-I-RESTORE, Restoring product save set C ... %VMSINSTAL-I-RESTORE, Restoring product save set D ... %VMSINSTAL-I-RESTORE, Restoring product save set E ... %VMSINSTAL-I-RESTORE, Restoring product save set F ... ************************************************************* SYSTEM MANAGER: The following command line MUST be added to the system startup command file SYS$MANAGER:SYSTARTUP_V5.COM or SYS$MANAGER:SYSTARTUP_VMS.COM for all nodes that will be running DECdecision $ @SYS$STARTUP:DECISION$STARTUP.COM The following command line should be added to the system shutdown command file SYS$MANAGER:SYSHUTDWN.COM for all nodes that will be running DECdecision $ @SYS$MANAGER:DECISION$SHUTDOWN.COM ************************************************************* %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSTEST.CHART$IVP]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSHLP.EXAMPLES.DECCHART]. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories. ****************************************************************** * * * Installing Sample Database... * * * ****************************************************************** * * * Installing Default User Database... * * * ****************************************************************** * * * Installing Public Folder Database... * * * ****************************************************************** 18 Run the DECdecision IVP. The installation procedure runs the DECdecision Installation Verification Procedure: 2-10 Installing DECdecision Executing IVP for: DECdecision V2.0 The IVP runs a Builder BLUEPRINT which will run each component and produce intermediate reports and a final chart of the results. The reports and chart are compared with the expected values to determine if the IVP has completed successfully. Starting DECdecision... Comparing the results of the BLUEPRINT with the expected results ******************************** DECdecision V2.0 IVP COMPLETED SUCCESSFULLY ******************************** IVP completed for: DECdecision V2.0 19 End the installation procedure. The installation procedure ends automatically with the following messages: Installation of DECISION V2.0 completed at 10:30 VMSINSTAL procedure done at 10:30 20 Make the system available to users. After the installation completes successfully, you should reset system logins to your system default (64 in this example). Then send a message to all users stating that the system is again available. Use the following DCL commands: $ SET LOGINS/INTERACTIVE=64 $ REPLY/USER "Installation complete. System is ready for use." 2-11 __________________________________________________________________ 3 Post-Installation Procedures This chapter describes tasks that you must complete after DECdecision is installed. __________________________________________________________________ 3.1 Editing System Startup and Shutdown Files After the installation is complete, you must edit the system startup and shutdown files for all nodes that will be running DECdecision. Add the following line to your system startup file, SYS$MANAGER:SYSTARTUP_V5.COM, after the line that invokes the network startup command procedure: $ @SYS$STARTUP:DECISION$STARTUP.COM DECISION$STARTUP.COM also contains the commands to start Rdb/VMS. It runs the command procedures SYS$STARTUP:RMONSTART.COM and SYS$STARTUP:SQL$STARTUP.COM. ____________________ Note ____________________ RDB is not required for DECdecision V2.0 and higher. If RDB is not present, the call to RMONSTART.COM will not be in the startup file. ____________________ Note ____________________ If your network startup command procedure runs in batch mode, you may experience a problem starting the SQL portion of Rdb/VMS. SQL$STARTUP.COM contains commands that run the Network Control Program (NCP). If NCP is not yet available when SQL$STARTUP.COM runs, the SQL startup will fail. You can fix the problem by inserting a DCL WAIT command (for example, $ WAIT 00:01 inserts a 1 minute pause) into SYSTARTUP_V5.COM immediately before the line that invokes DECISION$STARTUP.COM. Add the following line to your system shutdown file, SYS$MANAGER:SYSHUTDWN.COM: 3-1 Post-Installation Procedures $ @SYS$MANAGER:DECISION$SHUTDOWN.COM This file also contains the commands to shut down your Rdb/VMS monitor. __________________________________________________________________ 3.2 Activating DECdecision on a VAXcluster To activate DECdecision on any type of VAXcluster, you must first install DECdecision on each system disk that is commonly shared among nodes in the cluster. Then you must perform the following procedure to start DECdecision, replace the DCL tables, and load the license on all other nodes in the cluster: $ RUN SYS$SYSTEM:SYSMAN SYSMAN> SET ENVIRONMENT/CLUSTER/USER=SYSTEM Remote Password: supply SYSTEM password here SYSMAN> DO LICENSE LOAD DECDECISION-USER SYSMAN> DO INSTALL REPLACE SYS$LIBRARY:DCLTABLES.EXE SYSMAN> DO @SYS$STARTUP:DECISION$STARTUP SYSMAN> EXIT ____________________ Note ____________________ If you are upgrading from a previous version of DECdecision, you do not need to load your license. Your current license is still loaded. __________________________________________________________________ 3.3 User Account Requirements DECdecision users must have certain account privileges and quotas. The following two sections contain information about these requirements. ___________________________ 3.3.1 User Account Privileges To use DECdecision, an account must have at least the TMPMBX and NETMBX privileges. Use the VMS Authorize Utility to determine if users have the privileges they require. See Section 1.8.2 for more information. 3-2 Post-Installation Procedures ___________________________ 3.3.2 User Account Quotas To use DECdecision, an account must have sufficient quotas. Table 3-1 summarizes the minimum required user account quotas. Table_3-1_Minimum_User_Account_Quotas__________________________ Account Quota__________Value_____Description___________________________ ASTLM 100 AST queue limit BIOLM 10 Buffered I/O limit BYTLM[1] 30,000 Buffered I/O byte count limit DIOLM 10 Direct I/O limit ENQLM 2000 Lock queue limit FILLM 100 Open file limit MAXDETACH[2] 0 Maximum number of detached processes PGFLQUO 20,000 Paging file limit PRCLM 1 Subprocess creation limit WSEXTENT 2048 Working set extent WSQUO 512 Working set quota _______________________________________________________________ [1]Each DECdecision component run simultaneously uses 3000 of the total BYTLM. Setting BYTLM to 30,000 allows a user to run eight components at one time, with the remaining BYTLYM available for other processes. If a user wants to run more components at one time, increase BYTLM accordingly. [2]Each DECdecision component runs as a detached process. A MAXDETACH of n allows n components to be run, or you can set it to 0 for an unlimited number. _______________________________________________________________ To avoid running out of processes, you should maintain the default MAXDETACH process quota of 0 (that is, infinite). Because DECdecision retains application processes for re-use you could run out of processes unless an infinite number are available. Use the VMS Authorize Utility to verify and change user account quotas. See Section 1.8.2 for more information. 3-3 Post-Installation Procedures __________________________________________________________________ 3.4 Rebooting the System You are not required to reboot the system to activate DECdecision. However, you may choose to reboot your system after you have installed DECdecision, edited the system startup and shutdown files, and reset the system parameters (if necessary). A system reboot establishes any new parameter settings and verifies that DECdecision is ready for use and that the edits to the system startup command file are correct. __________________________________________________________________ 3.5 Running the Installation Verification Procedure Separately If you answered YES to the IVP question during the DECdecision installation, the Installation Verification Procedure ran automatically at the end of the installation. You received a message indicating whether the IVP succeeded or failed. You can also run the IVP separately. The account from which you run the IVP must have the same privileges and account quotas required to install DECdecision. See Section 1.8 for more information. To run the IVP, use the following DCL command: $ @SYS$TEST:DECISION$IVP __________________________________________________________________ 3.6 Running DECdecision As part of the installation, DECdecision adds its name to the Session Manager and FileView Applications menus. You should inform all users after the installation that DECdecision is now available as an option on these menus. ____________________ Note ____________________ On clusters with a multiple system disk environment, the Applications menu is customized only for the disk or disks on which DECdecision is installed. Users may also enter the following commands at the DCL prompt to use DECdecision and its components: o INFORM/QUERY or INFORM/ACCESS o INFORM/CALC o INFORM/CHART o INFORM/BUILDER For a full list of the DECdecision DCL commands and qualifiers, see the DECdecision Overview, or enter the following DCL command: 3-4 Post-Installation Procedures $ HELP DECdecision __________________________________________________________________ 3.7 Extension Change for Query Macros The default extension for macros used by the Query engine has changed with this version of DECdecision. The following table illustrates the macro names: _______________________________________________________________ _____Query_Engine____Old_Extension___New_Extension_____________ DECISION$ACCESS .ACCESS$MACRO DECquery .QUERY_MACRO _____DECISION$QUERY__________________.QUERY$MACRO______________ The contents of the Query macros do not need to change. However, if you do not change the names, you will need to change the default file filter each time you want to select a macro using the Playback screen from the OPTIONS menu. A command file has been provided that will copy existing Query macros to the new extension. The command file is: DECISION$QUERY_LIBRARY:CHANGE_MACRO_NAMES.COM CHANGE_MACRO_NAMES.COM will ask the user for a disk and directory. It will then copy both *.QUERY_MACRO and *.ACCESS$MACRO to *.QUERY$MACRO. As a precaution, the old macro files are saved. Once you have determined that the macros were successfully copied, you can delete the old macro files. Example 3-1 Changing Macro Names _______________________________________________________________ $ @change_macro_names Please enter the disk and directory to use [USER:[QUERY]]: USER:[QUERY...] Copying USER:[QUERY]10822.QUERY_MACRO;3 to USER:[QUERY]10822.QUERY$MACRO; Copying USER:[QUERY]11316.QUERY_MACRO;1 to USER:[QUERY]11316.QUERY$MACRO; Copying USER:[QUERY]QUERY.QUERY_MACRO;1 to USER:[QUERY]QUERY.QUERY$MACRO; Copying USER:[QUERY.TEST]TEST.ACCESS$MACRO;1 to USER:[QUERY.TEST]TEST.QUERY$MACRO; _______________________________________________________________ 3-5 Post-Installation Procedures __________________________________________________________________ 3.8 Post-Installation Check List Table 3-2 summarizes the tasks you must perform after installing DECdecision. Check to make sure that you have performed all these tasks before making DECdecision available to users. Table_3-2_Post-Installation_Check_List_________________________ Task________________________For_More_Information_______________ Edit system startup and See Section 3.1 shutdown files Activate DECdecision on a See Section 3.2 VAXcluster Check privileges and See Section 3.3 quotas of the user accounts Run CHANGE_MACRO_ See Section 3.7 NAMES.COM to change the Query macros default extension______________________________________________________ 3-6 __________________________________________________________________ 4 Managing Your DECdecision Environment This chapter gives suggestions for ways to best manage your DECdecision environment. __________________________________________________________________ 4.1 Performance Considerations The major factors to consider when supporting many DECdecision users are physical memory size and system parameter settings. Several process and system parameters can affect DECdecision performance. This section describes parameters that you can modify to improve performance. The following sections discuss these performance topics: o Working set values o Global pages and global sections ____________________ Note ____________________ The quotas suggested in the following sections are minimum values. If you frequently perform operations such as accessing large tables, joining large tables, or importing and exporting large amounts of data, larger quotas might be necessary to enhance performance. For additional information on VMS performance, see the Guide to VMS Performance Management. For information on the parameters and quotas required to run VAX Rdb/VMS and for information on tuning your Rdb/VMS database system, see the VAX Rdb/VMS Installation Guide and the VAX Rdb/VMS Guide to Database Maintenance and Performance. ___________________________ 4.1.1 Working Set Values DECdecision requires large user working sets to run optimally. As a result, you should consider setting the following process account parameters to the indicated values: o WSDEFAULT = 512 o WSQUOTA = 1024 o WSEXTENT = 2048 to 8192 4-1 Managing Your DECdecision Environment 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. ___________________________ 4.1.2 Global Pages and Global Sections When run locally (for example, as a standalone workstation or as a satellite node on a VAXcluster), each invocation of a DECdecision component requires 300 additional global pages and 1 global section. You should have sufficient unused global pages and global sections to allow for this. In addition, Query requires additional global pages and global sections at run time. This is due to the fact that Rdb/VMS allocates a certain amount of memory for each open database. The number of additional global pages and global sections required depends on the number of Query users. To estimate the total number of unused global pages needed, calculate the sum of the following values: 1 The number of Query users, multiplied by 100 2 The number of unused global pages required to install DECdecision: 6,500 3 If you are running DECdecision locally, the maximum number of components that will be running simultaneously, multiplied by 300 To estimate the total number of unused global sections needed, calculate the sum of the following values: 1 The number of Query users, multiplied by 2 2 The number of unused global sections required to install DECdecision: 25 3 If you are running DECdecision locally, the maximum number of components that will be running simultaneously, multiplied by 1 For example, assume your workstation is a satellite node on a Local Area VAXcluster. DECdecision is installed on the boot node. You typically run the Query, Calc, and Chart components at the same time. Your workstation requires these minimum unused global page and global section values: o Global pages - 1 Query user multiplied by 100 = 100 - 6,500 - 3 components running simultaneously multiplied by 300 = 900 Total: 100 + 6,500 + 900 = 7,500 4-2 Managing Your DECdecision Environment o Global sections - 1 Query user multiplied by 2 = 2 - 25 - 3 components running simultaneously multiplied by 1 = 3 Total: 2 + 25 + 3 = 30 See Section 1.8.5 for information on the minimum parameter values required to run DECdecision. __________________________________________________________________ 4.2 Managing Query Files and Databases Query is built on Rdb/VMS, Digital's relational database management system. The next three sections provide specific information on the following Query database management topics: o Using DECdecision with DATATRIEVE domains o Granting database access to users on other systems See the Query online help for valuable Query database management information in these areas: o Query objects and logical names o Migrating a Query database to another system o Accessing large Rdb/VMS relations from within Query o Giving users access to information o Giving users access to data stored in IBM systems o Protecting data For more information about Rdb/VMS, see the Rdb/VMS Guide to Database Administration. ___________________________ 4.2.1 Using DECdecision with DATATRIEVE Domains To work with DATATRIEVE domains, Query requires that either the file SYS$SHARE:DTRSHR.EXE exist on the system or that a logical name be defined to point to the appropriate DTR shareable image. 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, you should place the following line in SYSTARTUP_V5.COM to make this choice permanent: 4-3 Managing Your DECdecision Environment $ DEFINE/SYSTEM/EXEC DTRSHR SYS$SHARE:DTRSHRV4.EXE If you change SYSTARTUP_V5.COM to include this line, DECdecision uses DTRSHRV4.EXE when Query users work with DATATRIEVE domains. ___________________________ 4.2.2 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 have at least the minimum quotas recommended for DECdecision user accounts. These quotas are listed in Table 3-1. To find out which account is associated with RDBSERVER, log in to a privileged account such as SYSTEM, and enter the following commands: $ RUN SYS$SYSTEM:NCP NCP> SHOW OBJECT RDBSERVER NCP displays information about the account associated with RDBSERVER. If NCP does not display the information, then the DECnet account is the account used for remote access requests. In this case, the DECnet account should have the quotas listed in Table 3-1. Enter EXIT to leave NCP. __________________________________________________________________ 4.3 DECdecision Fatal Errors If a DECdecision component encounters an unexpected problem or an internal fatal error, your session terminates. When this occurs, each of the components acts in the following manner: o Query displays an error message and creates the dump file DECISION$QUERY_BUGCHK.DMP. o Calc creates the dump file DECISION$CALC_ BUGCHK.DMP. o DECchart displays an error message and creates the dump file DECCHART.DMP. o Builder displays an error message and creates the dump file DECISION$BUILDER_BUGCHK.DMP. o The Control Component creates the dump file DECISION$CTL_BUGCHK.DMP The bugcheck dump file is placed in your SYS$SCRATCH directory. If a bugcheck occurs, please submit to Digital a description of the problem, instructions on how to reproduce it, the associated data files (databases, spreadsheets, blueprints, and so on), and a copy of the bugcheck dump file. 4-4 Managing Your DECdecision Environment __________________________________________________________________ 4.4 Using Logical Names with DECdecision For all components running under DECdecision, you should define any logical names you need as JOB logicals (or GROUP or SYSTEM logicals). You will lose all your JOB logicals if the process that has started DECdecision is terminated. The JOB logicals lost include SYS$LOGIN and SYS$SCRATCH. Without SYS$SCRATCH, you cannot open a Builder blueprint, record a private macro, import, export, perform Copy Selection operations, or use the Draw Chart command within Query. Deassigning the logical name DECW$USER_DEFAULTS may cause unexpected results in DECdecision. Do not deassign DECW$USER_ DEFAULTS. 4-5 __________________________________________________________________ A Sample DECdecision Installation This appendix shows a typical installation of DECdecision on a VMS Version 5.4 system. In the example, DECdecision also installs DECchart Version 2.0. Table 1-5 summarizes the tasks you must perform before installing DECdecision. Check to make sure that you have completed all these tasks before proceeding with the installation. Welcome to node MYNODE Username: SYSTEM Password: Welcome to VAX/VMS Version 5.4 on node MYNODE Last interactive login on Wednesday, 20-JUL-1995 08:32 Last non-interactive login on Wednesday, 20-JUL-1995 01:00 $ REPLY/USER "Installation starting in 5 minutes. Please log out." $ SET LOGINS/INTERACTIVE=0 $ @SYS$UPDATE:VMSINSTAL DECISION020 MUA0: OPTIONS N VAX/VMS Software Product Installation Procedure V5.4 It is 20-JUL-1995 at 09:17. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? Please mount the first volume of the set on MUA0:. * Are you ready? YES %MOUNT-I-MOUNTED, DECIS mounted on _MUA0: The following products will be processed: DECISION V2.0 Beginning installation of DECISION V2.0 at 09:17 %VMSINSTAL-I-RESTORE, Restoring product save set A ... Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: 2 A-1 Sample DECdecision Installation * Queue name [SYS$PRINT]: Job 810 (queue SYS$PRINT, entry 1295) started on SYS$PRINT * Do you want to continue the installation [NO]? YES %VMSINSTAL-I-RELMOVED , The product's release notes have been moved to SYS$HELP. ************************************************************ * * * DECdecision V2.0 * * Integrated Decision Support Package * * * * Installation Procedure * * * ************************************************************ Product: DECDECISION-USER Producer: DEC or TTI Version: 2.0 Release Date: 15-JUL-1995 * Does this product have an authorization key registered and loaded? YES Checking user parameters Checking system parameters Testing dependent product versions %VMSINSTAL-I-RESTORE, Restoring product save set B ... This kit requires DECchart V2.0 or later ********************************************************** DECchart V2.0 will be installed since an earlier version exists on your system. ********************************************************** The DECdecision product creates a tree of library directories. A subdirectory is created for each component. * Where would you like to place the DECISION V2.0 library root [SYS$SYSCOMMON:[DECISION]]: %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[DECISION]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[DECISION.BUILDER]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[DECISION.ECALC]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[DECISION.QUERY]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSTEST.DECISION$IVP]. * Do you want to run the IVP after the installation [YES]? A-2 Sample DECdecision Installation The DECdecision IVP requires that a display device be defined (using the SET DISPLAY command). Please enter the node name of the workstation on which to display the IVP. * Enter node name (or Return to not run IVP): MYNODE * Do you want to purge files replaced by this installation [YES]? To complete the installation on a standalone VAX 11/780 will take approximately: 30 minutes to install 11 minutes to run the IVP All required questions have been asked. You can terminate the installation procedure at this time. * Do you want to continue the installation [YES]? %VMSINSTAL-I-RESTORE, Restoring product save set C ... %VMSINSTAL-I-RESTORE, Restoring product save set D ... %VMSINSTAL-I-RESTORE, Restoring product save set E ... %VMSINSTAL-I-RESTORE, Restoring product save set F ... *************************************************************************** SYSTEM MANAGER The following command lines MUST be added to the system startup command file SYS$MANAGER:SYSTARTUP_V5.COM for all nodes that will be running DECdecision $ @SYS$STARTUP:DECISION$STARTUP.COM The following command lines should be added to the system shutdown command file SYS$MANAGER:SYSHUTDWN.COM for all nodes that will be running DECdecision $ @SYS$MANAGER:DECISION$SHUTDOWN.COM *************************************************************************** %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSTEST.CHART$IVP]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSHLP.EXAMPLES.DECCHART]. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories. Executing IVP for: DECISION V2.0 A-3 Sample DECdecision Installation ********************************************************************* * * * Installing Sample Database... * * * ********************************************************************* * * * Installing Default User Database... * * * ********************************************************************* * * * Installing Public Folder Database... * * * ********************************************************************* Executing IVP for: DECdecision V2.0 The IVP runs a Builder BLUEPRINT which will run each component and produce intermediate reports and a final chart of the results. The reports and chart are compared with the expected values to determine if the IVP has completed successfully. Starting DECdecision... Comparing the results of the BLUEPRINT with the expected results ******************************** DECdecision V2.0 IVP COMPLETED SUCCESSFULLY ******************************** IVP completed for: DECdecision V2.0 Installation of DECISION V2.0 completed at 10:30 VMSINSTAL procedure done at 10:30 $ SET LOGINS/INTERACTIVE=64 $ REPLY/USER "Installation complete. System is ready for use." Table 3-2 summarizes the tasks you must perform after installing DECdecision. Check to make sure that you have completed all these tasks before making DECdecision available to users. A-4 __________________________________________________________________ B Sample DECdecision Upgrade from a Previous Version This appendix shows a typical upgrade of DECdecision from Version 1.5 to Version 2.0 on a VMS Version 5.4 system. In this example, DECdecision also upgrades to DECchart Version 2.0. Table 1-5 summarizes the tasks you must perform before installing DECdecision. Check to make sure that you have completed all these tasks before proceeding with the installation. Welcome to node MYNODE Username: SYSTEM Password: Welcome to VAX/VMS Version 5.4 on node MYNODE Last interactive login on Wednesday, 20-JUL-1995 08:32 Last non-interactive login on Wednesday, 20-JUL-1995 01:00 $ REPLY/USER "Installation starting in 5 minutes. Please log out." $ SET LOGINS/INTERACTIVE=0 $ @SYS$UPDATE:VMSINSTAL DECISION020 MUA0: OPTIONS N VAX/VMS Software Product Installation Procedure V5.4 It is 20-JUL-1995 at 09:17. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? Please mount the first volume of the set on MUA0:. * Are you ready? YES %MOUNT-I-MOUNTED, DECIS mounted on _MUA0: The following products will be processed: DECISION V2.0 Beginning installation of DECISION V2.0 at 09:17 %VMSINSTAL-I-RESTORE, Restoring product save set A ... Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above B-1 Sample DECdecision Upgrade from a Previous Version * Select option [2]: 2 * Queue name [SYS$PRINT]: Job 810 (queue SYS$PRINT, entry 1295) started on SYS$PRINT * Do you want to continue the installation [NO]? YES %VMSINSTAL-I-RELMOVED , The product's release notes have been moved to SYS$HELP. ************************************************************ * * * DECdecision V2.0 * * Integrated Decision Support Package * * * * Installation Procedure * * * ************************************************************ Product: DECDECISION-USER Producer: DEC or TTI Version: 2.0 Release Date: 15-JUL-1995 * Does this product have an authorization key registered and loaded? YES Checking user parameters Checking system parameters Testing dependent product versions %VMSINSTAL-I-RESTORE, Restoring product save set B ... This kit requires DECchart V2.0 or later ************************************************************ DECchart V2.0 will be installed since an earlier version exists on your system. ************************************************************ * Do you want to proceed [YES]? The directory DECISION$LIBRARY currently exists on your system. * Would you like to place the DECISION V2.0 library root there [YES]? %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSTEST.DECISION$IVP]. %CREATE-I-EXISTS, VMI$ROOT:[SYSTEST.DECISION$IVP] already exists ************************************************************* DECdecision has a default database. This is copied to new user's accounts when they first use DECdecision. This database is installed in DECISION$QUERY_LIBRARY ************************************************************* B-2 Sample DECdecision Upgrade from a Previous Version Your system has a default user database. * Do you want to replace it [NO]? * Do you want to run the IVP after the installation [YES]? The DECdecision IVP requires that a display device be defined (using the SET DISPLAY command). Please enter the node name of the workstation on which to display the IVP. * Enter node name (or Return to not run IVP): MYNODE * Do you want to purge files replaced by this installation [YES]? To complete the installation on a standalone VAX 11/780 will take approximately: 30 minutes to install 11 minutes to run the IVP All required questions have been asked. You can terminate the installation procedure at this time. * Do you want to continue the installation [YES]? %VMSINSTAL-I-RESTORE, Restoring product save set C ... %VMSINSTAL-I-RESTORE, Restoring product save set D ... %VMSINSTAL-I-RESTORE, Restoring product save set E ... %VMSINSTAL-I-RESTORE, Restoring product save set F ... *************************************************************************** SYSTEM MANAGER The following command lines MUST be added to the system startup command file SYS$MANAGER:SYSTARTUP_V5.COM for all nodes that will be running DECdecision $ @SYS$STARTUP:DECISION$STARTUP.COM The following command lines should be added to the system shutdown command file SYS$MANAGER:SYSHUTDWN.COM for all nodes that will be running DECdecision $ @SYS$MANAGER:DECISION$SHUTDOWN.COM ************************************************************************* %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSTEST.CHART$IVP]. %CREATE-I-EXISTS, VMI$ROOT:[SYSTEST.CHART$IVP] already exists %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSHLP.EXAMPLES.DECCHART]. %CREATE-I-EXISTS, VMI$ROOT:[SYSTEST.EXAMPLES.DECCHART] already exists Deleting obsolete files %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories. B-3 Sample DECdecision Upgrade from a Previous Version ********************************************************************* * * * Installing Sample Database... * * * ********************************************************************* Executing IVP for: DECdecision V2.0 The IVP runs a Builder BLUEPRINT which will run each component and produce intermediate reports and a final chart of the results. The reports and chart are compared with the expected values to determine if the IVP has completed successfully. Starting DECdecision... Comparing the results of the BLUEPRINT with the expected results ******************************** DECdecision V2.0 IVP COMPLETED SUCCESSFULLY ******************************** IVP completed for: DECdecision V2.0 Installation of DECISION V2.0 completed at 10:30 VMSINSTAL procedure done at 10:30 $ SET LOGINS/INTERACTIVE=64 $ REPLY/USER "Installation complete. System is ready for use." Table 3-2 summarizes the tasks you must perform after installing DECdecision. Check to make sure that you have completed all these tasks before making DECdecision available to users. B-4 __________________________________________________________________ C DECdecision Files This appendix lists all the files that are transferred to your system during a first time DECdecision installation in which DECchart Version 2.0 is installed. The files are listed by directory. In DECW$SYSTEM_DEFAULTS: DECCHART$MOTIF_UID.UID DECISION$QUERY_DEFAULTS.DAT DECISION$QUERY_UID.UID DECISION$BUILDER_UID.UID DECISION$CT_UID.UID DECISION$DEFAULTS.DAT DECISION$ECALC.DAT DECISION$ESP_UID.UID DECISION$EVE_UID.UID In SYS$STARTUP: CHART$STARTUP.COM DECISION$STARTUP.COM In SYS$SYSTEM: DECCHART$MOTIF.EXE DECISION$QUERY.EXE DECISION$BUILDER.EXE DECISION$CT.EXE DECISION$ECALC.EXE In SYS$HELP: DECISION$QUERY_HELP.DECW$BOOK DECISION$BUILDER_HELP.DECW$BOOK DECISION$CHART.HLB DECISION$CT_HELP.DECW$BOOK DECISION$ECALC.DECW$BOOK DECISION020.RELEASE_NOTES TCV_CONVERT_MESSAGES.TXT C-1 DECdecision Files In SYS$COMMON:[SYSHLP.EXAMPLES.DECCHART]: CHART$SAMPLE.CHART CHART$SAMPLE.CHART_STYLE CHART$SAMPLE.TABLE In SYS$LIBRARY: DECISION$BUILDER_SHR.EXE DECISION$DTIF_TO_DDIF.EXE DECISION$ESP_SECTION.TPU$SECTION DECISION$TABLEWGT_SHR.EXE DTIF$READ_ASCII_FIELD.EXE DTIF$READ_ASCII_TABULAR.EXE DTIF$READ_CALCGRD.EXE DTIF$READ_DIF.EXE DTIF$READ_WK1.EXE DTIF$READ_WK3.EXE DTIF$WRITE_ASCII_TABULAR.EXE DTIF$WRITE_WK1.EXE DTIF$WRITE_WK3.EXE ECALC$GRID_SHR.EXE ECALC$TPU_SHR.EXE TCV$SHR.EXE TPU$EXT_TABLEWGT.EXE In SYS$MANAGER: DECISION$SHUTDOWN.COM In SYS$MESSAGE: DTIF$READ_ASCII_FIELD_MESSAGES.EXE DTIF$READ_ASCII_TABULAR_MESSAGES.EXE DTIF$READ_CACLGRD_MESSAGES.EXE DTIF$READ_DIF_MESSAGES.EXE DTIF$READ_WK1_MESSAGES.EXE DTIF$READ_WK3_MESSAGES.EXE DTIF$WRITE_ASCII_TABULAR_MESSAGES.EXE DTIF$WRITE_WK1_MESSAGES.EXE DTIF$WRITE_WK3_MESSAGES.EXE ECALC$MESSAGES.EXE TCV$MSG.EXE In CDA$LIBRARY: CH_AREA100.CHART_STYLE CH_AREAGRID.CHART_STYLE CH_AREASIMPLE.CHART_STYLE CH_AREA_COL.CHART_STYLE CH_BAR100.CHART_STYLE C-2 DECdecision Files CH_BARCLUSTER.CHART_STYLE CH_BARCLUSTERGRID.CHART_STYLE CH_BARCLUSTERVALUE.CHART_STYLE CH_BAROVERLAP.CHART_STYLE CH_BARSTACK.CHART_STYLE CH_COL100.CHART_STYLE CH_COLCLUSTER.CHART_STYLE CH_COLCLUSTERGRID.CHART_STYLE CH_COLCLUSTERVALUE.CHART_STYLE CH_COLOVERLAP.CHART_STYLE CH_COLSTACK.CHART_STYLE CH_COL_HILO.CHART_STYLE CH_COL_LINE.CHART_STYLE CH_COL_SCAT.CHART_STYLE CH_HILO.CHART_STYLE CH_HILOCLOSE.CHART_STYLE CH_HILOOPCL.CHART_STYLE CH_HILOOPEN.CHART_STYLE CH_HILO_LINE.CHART_STYLE CH_HISTO.CHART_STYLE CH_HISTOHGRID.CHART_STYLE CH_HISTOHVGRID.CHART_STYLE CH_HISTOVALUE.CHART_STYLE CH_LINE.CHART_STYLE CH_LINEHGRID.CHART_STYLE CH_LINEHVGRID.CHART_STYLE CH_LINELOG.CHART_STYLE CH_LINEMARKERS.CHART_STYLE CH_LINE_LINE.CHART_STYLE CH_LINE_SCAT.CHART_STYLE CH_PIE.CHART_STYLE CH_PIEALLEXP.CHART_STYLE CH_PIEONEEXP.CHART_STYLE CH_PIEVALUE.CHART_STYLE CH_SCATTER.CHART_STYLE CH_SCATTERDEPLOG.CHART_STYLE CH_SCATTERHVGRID.CHART_STYLE CH_SCATTERLINES.CHART_STYLE CH_SCATTERXYLOG.CHART_STYLE In DECISION$LIBRARY: QUERY.DIR BUILDER.DIR ECALC.DIR QUERY.DIR C-3 DECdecision Files In DECISION$QUERY_LIBRARY: DECISION$QUERY_CREDB.COM DECISION$ACCESS_DEFDB.RBR DECISION$ACCESS_DEFDB.RDB DECISION$ACCESS_DEFDB.SNP DECISION$QUERY_PUBLISH.ACCESS$MACRO DECISION$QUERY_PUBLISH.COM DECISION$ACCESS_SAMPLE.RBR DECISION$ACCESS_SAMPLE.RDB DECISION$ACCESS_SAMPLE.SNP DECISION$ACCESS_SYSDB.RDB DECISION$ACCESS_SYSDB.SNP DECISION$ACCESS_SYSDB.RBR In DECISION$BUILDER_LIBRARY: DECISION$APPEND.COM DECISION$BIG_DISCOUNT.DOC DECISION$BUILDER_SYSTBX.DAT DECISION$DECISION.BLUEPRINT DECISION$DECISION.DOC DECISION$DECISION_MORE.DOC DECISION$DECWRITE.BLUEPRINT DECISION$DECWRITE_GUIDE.DOC DECISION$EXTERNAL.BLUEPRINT DECISION$EXTERNAL.DOC DECISION$LIVELINK.DOC DECISION$LOOP.BLUEPRINT DECISION$LOOP.DOC DECISION$LOOP_MORE.DOC DECISION$REVENUE_BY_DIVISION.TABLE DECISION$SMALL_DISCOUNT.DOC DECISION$TUTORIAL.BLUEPRINT DECISION$TUTORIAL.DOC DECISION$TUTORIAL_MORE.DOC DECISION$USER_TOOL.BLUEPRINT DECISION$USER_TOOL.DOC DECISION$USER_TOOL_MORE.DOC DECISION$VARIABLES.BLUEPRINT DECISION$VARIABLES.DOC DECISION$VARIABLES_MORE.DOC DECISION$YEARLY_REVENUE.TABLE In DECISION$ECALC_LIBRARY: DECISION$INTEREST_TABLE.TABLE DECISION$MACRO_EXAMPLE.TPU DECISION$YEARLY_REV.TABLE C-4 DECdecision Files In SYS$TEST: CHART.DIR DECISION$IVP.COM DECISION$IVP.DIR In SYS$COMMON:[SYSTEST.DECISION$IVP]: DECISION$QUERY_REPORT.DDIF DECISION$CALC_REPORT.DDIF DECISION$CHART_RESULTS.CHART DECISION$COMPARE_FILES.COM DECISION$IVP.BLUEPRINT In SYS$COMMON:[VUE$LIBRARY.USER]: CHART$VUE.COM CHART$VUE_PROFILE.VUE$DAT DECISION$VUE.COM DECISION$VUE_PROFILE.VUE$DAT C-5 _________________________________________________________________ Index _______________________________ A DECchart _______________________________ installingo2-1 Access upgradingo2-1, 2-6 granting remoteo4-4 DECdecision Account privilegeso3-2 activating on VAXclustero3-2 Account quotaso3-3 DCL commands for runningo3-4 checkingo1-6 directorieso1-4 modifyingo1-6 filesoC-1 to C-5 handling fatal errorso4-4 _______________________________ logical nameso1-4 B registering licenseo1-3 _______________________________ runningo3-4 Backing up system disko1-11, user account privilegeso3-2 2-3 user account quotaso3-3 using with DATATRIEVEo4-3 _______________________________ using with remote databaseso C 4-4 _______________________________ Disk blocks CHANGE_MACRO_NAMES.COMo3-5 displaying number of unusedo Checking the distribution kito 1-7 1-2 requiredo1-7 Cluster Distribution kit activating DECdecision ono contents ofo1-2 3-2 list of files onoC-1 installing ono1-5 Dump fileso4-4 Components required _______________________________ VMSo1-3 E _______________________________ _______________________________ D Editing _______________________________ SYSHUTDWN.COMo3-1 Databases SYSTARTUP_V5.COMo3-1 accessing IBMo4-3 Errors accessing remoteo4-4 handling fatalo4-4 managing Queryo4-3 _______________________________ migrating to another systemo F 4-3 _______________________________ upgrading default usero2-7 Fatal errorso4-4 DATATRIEVE Files and DECdecisiono4-3 DECdecisionoC-1 to C-5 DCL command dumpo4-4 for starting Rdb monitoro managing Queryo4-3 1-11 purging old versionso2-9 DCL commands for checking disk spaceo1-7 _______________________________ for running DECdecisiono3-4 G for running the IVPo3-4 _______________________________ for running VMSINSTALo2-2 Index-1 Index _______________________________ Global pages L adjusting for run-time useo _______________________________ 4-2 Labels checkingo1-9 on distribution mediao1-2 required valueso1-8 Library directorieso2-7 Global sections License adjusting for run-time useo loading on VAXclustero3-2 4-2 registeringo1-3, 2-5 checkingo1-9 License Management Facilityo required valueso1-8 1-3 Granting remote database Logical nameso1-4, 4-5 accesso4-4 _______________________________ _______________________________ H M _______________________________ _______________________________ Hardware Macros - extension changeo3-5 prerequisiteo1-2 Media labelso1-2 _______________________________ mountingo2-3 I _______________________________ _______________________________ O Improving performanceo4-1 _______________________________ Installation Operating system exampleoA-1 to A-4 required componentso1-3 files installedoC-1 to C-5 first timeo2-1 _______________________________ kito1-2 P overviewo2-1 _______________________________ preparing foro1-1 PAK startingo2-2 loading on VAXclustero3-2 stoppingo2-2 registeringo1-3, 2-5 time neededo2-1 Parameters upgradingo2-1, B-1 to B-4 adjusting for run-time useo Installation Verification 4-2 Procedure changingo1-10 DECdecisiono2-10 checkingo1-9 running after installationo systemo1-8 3-4 Performance considerationso4-1 running during installationo global pageso4-2 2-8 global sectionso4-2 Installing account require- working seto4-1 mentso1-5 Post-installation privilegeso1-5 check listo3-6 quotaso1-6 Preparing for installationo1-1 IVP check listo1-12 DECdecisiono2-10 Prerequisite hardwareo1-2 running after installationo Prerequisite softwareo1-2 3-4 Privileges running during installationo required for installingo1-5 2-8 required for usingo3-2 Index-2 Index Problems SYSGEN reportingo1-11 changing parameterso1-10 Product Authorization Key checking valueso1-9 loading on VAXclustero3-2 minimum valueso1-8 registeringo1-3 SYSHUTDWN.COM _______________________________ editingo3-1 SYSTARTUP_V5.COM Q editingo3-1 _______________________________ System Query macros - extension editing shutdown fileo3-1 changeo3-5 editing startup fileo3-1 Quotas rebootingo3-4 installation accounto1-6 tuningo4-1 user accounto3-3 System disk _______________________________ backing upo1-11, 2-3 R System parameters _______________________________ adjusting for run-time useo Rdb/VMS 4-2 starting before installation changingo1-10 o1-11 minimum valueso1-8 Rebooting systemo3-4 on VAXclusterso1-5 Release noteso2-4 _______________________________ Remote access T grantingo4-4 _______________________________ Reporting problemso1-11 Time needed to installo2-1 Required disk space Tuning systemo4-1 systemo1-7 usero1-7 _______________________________ Required hardwareo1-2 U Required operating system _______________________________ componentso1-3 Upgrade procedureo2-1 Required privilegeso1-5 exampleoB-1 to B-4 Required softwareo1-2 User account Running DECdecisiono3-4 privilegeso3-2 _______________________________ quotaso3-3 S _______________________________ _______________________________ V Sample fileso1-4 _______________________________ Sample installationoA-1 to A-4 VAXcluster Sample upgradeoB-1 to B-4 activating DECdecisiono3-2 Shutdown file installing ono1-5 editing systemo3-1 loading license ono3-2 Software VMS components requiredo1-3 prerequisiteo1-2 VMSINSTAL procedureo2-3 to Starting the installationo2-2 2-11 Startup file command lineo2-3 editing systemo3-1 problem detectiono2-2 Stopping the installationo2-2 starting the installationo 2-2 Index-3 Index VMSINSTAL procedure (cont'd) stopping the installationo 2-2 time needed to installo2-1 _______________________________ W _______________________________ Working seto4-1 WSDEFAULT valueo4-1 WSEXTENT valueo4-1 WSMAX valueo4-1 WSQUOTA valueo4-1 Index-4