Order Number: AA-EY16D-TE April 1991 This guide contains the installation procedure for the Electronic Data Control System (EDCS II). Revision/Update Information: This manual supersedes the EDCS II Installation Guide, AA-EY16C-TE. Operating System and Version: VMS Version 5.3-2 or higher Software Version: EDCS II Version 2.1 digital equipment corporation maynard, massachusetts ___________________________________________________ First printing, April 1986 Revised, December 1986 Revised, October 1989 Revised, April 1991 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. Any 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 or equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. © Digital Equipment Corporation 1986, 1989, 1991. All rights reserved. Printed in U.S.A. The Reader's Comments form at the end of this document re- quests your critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: Bookreader, DECforms, DECnet, DECwindows, EDCS II, VAX, VAXcluster, VAX DOCUMENT, VAX Rdb/VMS, VMS, VT, and the DIGITAL logo. ThisSdocument isravailable onaCDROM. of Adobe Systems, Inc. This document was prepared with VAX DOCUMENT, Version 1.2. S1175 Contents ________________________________________________________________ Preface ......................................................... vii ________________________________________________________________ Chapter 1 Preparing for Installation 1.1 Installation Procedure Requirements............. 1-3 1.1.1 Software Required.......................... 1-3 1.1.2 Time Required .............................. 1-4 1.1.3 Privileges Required ....................... 1-4 1.1.4 Disk Space Required to Install EDCS II ........................................... 1-4 1.1.5 Disk Space Required to Operate EDCS II ........................................... 1-7 1.1.6 System Parameter Values................... 1-7 1.1.6.1Minimum System Parameter Values Required ............................ 1-8 1.1.6.2System Parameter Recommendations for Larger Systems with Heavy Usage................................ 1-9 1.1.6.3Checking System Parameter Values............................... 1-10 1.1.6.4Calculating the GBLPAGES and GBLSECTIONS System Parameter Values............................... 1-11 1.1.6.5Changing System Parameter Values............................... 1-12 iii 1.1.7 Network Parameter Values Required....... 1-12 1.1.7.1Checking Network Parameter Values............................... 1-13 1.1.7.2Calculating the Maximum Links Network Parameter Values.......... 1-15 1.1.7.3Changing Network Parameters...... 1-15 1.1.8 Minimum Process Quotas Required ......... 1-16 1.1.9 VMSINSTAL Notification of Requirements................................ 1-17 1.2 Shutting Down Previous EDCS Versions............ 1-17 1.3 Backing Up Your System Disk...................... 1-18 1.4 Registering Your Software License............... 1-19 1.5 Procedure for Converting a VAX EDCS Database .. 1-19 1.6 Gathering Information Before You Install....... 1-19 1.6.1 Information Needed for All Installations .............................. 1-20 1.6.2 Information Needed for Installing EDCS II as Both Client and Server............. 1-21 1.6.3 Information Needed for Installing EDCS II as a Server Only ....................... 1-22 1.6.4 Information Needed for Installing EDCS II as a Client Only ....................... 1-23 ________________________________________________________________ Chapter 2 Installing EDCS II 2.1 Installation Procedure............................ 2-1 2.2 Reading the Online Release Notes ................ 2-2 2.3 Aborting the Installation ........................ 2-3 iv 2.4 Error Recovery ..................................... 2-3 ________________________________________________________________ Chapter 3 After the Installation 3.1 Running the IVP After the Installation ......... 3-1 3.2 Editing Parameter Files........................... 3-4 3.3 Running EDCS II on a VAXcluster ................. 3-4 3.4 Starting Up EDCS II ............................... 3-5 3.5 Running Verify and Repair ........................ 3-5 ________________________________________________________________ Appendix A Sample Installation of EDCS II as Both a Server and Client ________________________________________________________________ Appendix B Sample Installation of EDCS II as a Server ________________________________________________________________ Appendix C Sample Installation of EDCS II as a Client ________________________________________________________________ Appendix D Solving Installation Errors v ________________________________________________________________ Index ________________________________________________________________ Tables 1-1 Disk Space Required to Install EDCS II ......... 1-5 1-2 Disk Space Required to Operate EDCS II ......... 1-7 1-3 Minimum Required System Parameters for EDCS II ................................................... 1-8 1-4 Recommended System Parameters for Larger Systems with Heavy Usage.......................... 1-9 1-5 Number of Links Required.......................... 1-15 1-6 Minimum Process Quotas for EDCS II.............. 1-16 2-1 Sample Installation Logs.......................... 2-2 vi Preface ________________________________________________________________ This guide describes how to install the Electronic Data Control System (EDCS II) Version 2.1. ____________________________________________________________ Intended Audience This guide is for a system manager or anyone responsible for the installation of EDCS II. ____________________________________________________________ Document Structure This manual consists of three chapters and four appendixes: o Chapter 1 describes how to prepare for EDCS II installa- tions. o Chapter 2 describes the installation procedure. o Chapter 3 describes postinstallation considerations and procedures. o Appendix A is an example of an installation of EDCS II as both a client and server. o Appendix B is an example of an installation of EDCS II as a server. vii o Appendix C is an example of an installation of EDCS II as a client. The installation of the DECwindows and DECforms menu interfaces is also shown. o Appendix D describes potential errors and recovery proce- dures. ____________________________________________________________ Associated Documents The EDCS II documentation set consists of four other books, a pocket guide, and release notes, as follows: o EDCS II User's Guide This guide describes the EDCS II tasks that allow users to create, access, revise, and review any type of data file. It also describes the DECforms and DECwindows menu interfaces, and the command line interface. This guide is for new users of the EDCS II system. o EDCS II Reference Manual This manual provides a detailed description of EDCS II commands, parameters, and qualifiers, and discusses basic EDCS II concepts. It is for all EDCS II users. It is provided in your installation kit in PostScript (.ps) and ASCII (.txt) formats so that you can print it at your location. To print this manual on a PostScript printer, specify this file name: SYS$HELP:EDCS021_REFERENCE_MANUAL.PS To print this manual on a non-PostScript printer, specify this file name: SYS$HELP:EDCS021_REFERENCE_MANUAL.TXT o EDCS II Administrator's Guide viii This guide describes how to configure, run, and maintain EDCS II. This guide is for EDCS II account managers and administrators. o EDCS II Programmer's Guide This guide discusses how to use the EDCS II callable interface and contains an appendix of diagnostic messages. It also explains how to create customized queries on data stored in the VAX Rdb/VMS database. This guide is for programmers and developers. o EDCS II Pocket Guide This guide describes how to enter EDCS II commands and summarizes commands, parameters, and qualifiers. o EDCS II Release Notes The release notes contain information about added features or known problems not included in the documentation. The release notes are for all users and can be printed during the installation. The EDCS II documentation set, excluding the EDCS II Pocket Guide, is available on CDROM for users who have DECwindows and Bookreader software. ____________________________________________________________ Related Documents You may want to refer to the following documentation for more information: o The VAX Rdb/VMS Installation Guide o The "Backup" section in the VMS System Management Volume 2 Maintenance manual o The "Introduction to System Management" section in the VMS System Management Volume 1A Setup manual ix o The "Authorize" section in the VMS System Management Volume 3 Security manual o The "SYSGEN Utility" section in the VMS System Management Volume 1B Setup manual o The "Guide to Setting up a VMS System" section in the VMS System Management Volume 1A Setup manual o The VMS Network Control Program manual x ____________________________________________________________ Conventions The following conventions are used in this guide: xi xii _____________________________________________________________ Convention_________Meaning___________________________________ In examples, a key name shown within a box indicates that you press a key on the keyboard; in text, a key name is not enclosed in a box. In this example, the key is the Return key. Note that the Return key is not usually shown in syntax statements or in all examples; however, assume that you must press Return after entering a command or responding to a prompt. Ctrl/x In examples, a key combination is enclosed in a box; in text, a key combination is not enclosed in a box. A key combination, with a slash separating two key names, indicates that you hold down the first key while you press the second key. For exam- ple, the key combination Ctrl/x indicates that you hold down the key labeled Ctrl while you press the key labeled x. PF1 W In examples, a key sequence is enclosed in a box; in text, a key sequence is not enclosed in a box. For example, the key sequence PF1 W indicates that you must first press and release the key labeled PF1, then press and release the key labeled W. UPPERCASE Uppercase letters in a command line indi- cate the keywords that you must enter. You can enter them in either uppercase or low- ercase. You can use the first 3 characters to abbreviate command keywords, or you can use the minimum unique abbreviation. lowercase italics Lowercase italics indicate variables for which you supply a value. xiii [qualifier] Brackets indicate that the enclosed item is optional. (Brackets are not, however, optional in the syntax of a directory name in a file specification or in the syntax of a substring specification in an assignment statement.) { ALL } Braces enclosing two or more items in { CURRENT } commands indicate that you must specify { } ___________________one_of_the_items._________________________ Chapter 1 Preparing for Installation ________________________________________________________________ This chapter discusses the preparations and requirements necessary for installing EDCS II. EDCS II is a data management system that controls files in a distributed environment. The EDCS II database is con- nected directly to the server node. The server interfaces with the database to process user commands. One server node cannot have more than one database. You can use multiple server nodes (one server for each node) to create a multiple database (one database for each node) configuration. NOTE When installing EDCS II, be sure to fully upgrade your system. EDCS II Version 2.1 is incompatible with Version 2.0. Therefore, you cannot run Version 2.0 on a client and Version 2.1 on a server, or vice versa. The client node contains the user interface. One or more client nodes can connect to the server node by the DECnet network. You can have one node function as both a server and a client or you can have separate server nodes and client nodes. When you install EDCS II in a VAXcluster, whether the VAXcluster uses a cluster alias for EDCS II or not, Preparing for Installation 1-1 you must install both a client and a server. For additional information about EDCS II configurations, see the EDCS II Administrator's Guide. Because you can have separate server and client nodes as well as two different user interfaces, there are several possible EDCS II installations. (install_figure) shows all the possible EDCS II combinations. For example, 5. shows a client node only, with a DECforms interface. Note that for 10., 11. and 12., the assumption is that a client node has already been installed. 1-2 Preparing for Installation The installation procedure asks if you want to install a client node only, a server node only, both, or just a user interface (DECwindows or DECforms). The installation proce- dure will then vary depending on your answer. This guide has appendixes that contain sample logs of the following types of installations: o Both client and server (Appendix A) o Server only (Appendix B) o Client only, including the DECwindows and DECforms menu interfaces (Appendix C) Your bill of materials (BOM) and indented bills report (BIL) specify the number and contents of your media. Be sure to verify the contents of your kit with this information. If you find your kit is damaged or if you find that parts of it are missing, contact your Digital representative. ____________________________________________________________ 1.1 Installation Procedure Requirements The following sections discuss various requirements for installing EDCS II. ____________________________________________________________ 1.1.1 Software Required Your system must have the following software installed before you install EDCS II Version 2.1: 1. VMS Version 5.3-2 or higher. 2. DECwindows (same version as VMS), if you want a DECwindows interface. 3. DECforms Version 1.2-26, if you want a DECforms interface. 4. DECnet (same version as VMS). 5. VAX Rdb/VMS Version 3.1B or higher (required for a server installation only). Please note that only the run-time license of VAX Rdb/VMS is required. If you have questions about the required software, see the System Software Addendum (SSA). Preparing for Installation 1-3 ____________________________________________________________ 1.1.2 Time Required The time required to install EDCS II varies depending on the processor type, the disk space you have, and whether you are installing a client, a server, or both. The average time required for an EDCS II installation is 1 hour, but this time varies from 40 minutes to 2 hours. If you run the Installation Verification Procedure (IVP), the installation requires an additional 5 minutes. ____________________________________________________________ 1.1.3 Privileges Required To install EDCS II, log in to an account that has SETPRV or the following privileges: o CMKRNL o EXQUOTA o SYSLCK o SYSPRV o WORLD To run the IVP, you will need additional privileges. See Chapter 3 for more information. EDCS II uses VMSINSTAL, the standard VMS installation proce- dure, for installation. Note that VMSINSTAL turns off BYPASS privilege at the start of the installation. See the VMS Installation Guide for more information about VMSINSTAL. Digital recommends that you install EDCS II on a SYSTEM account with a SYSTEM UIC. If a SYSTEM account does not exist on the target system, create one using the Authorize utility. ____________________________________________________________ 1.1.4 Disk Space Required to Install EDCS II Table 1-1 can help you determine if you have enough memory for your specific installation. 1-4 Preparing for Installation Table 1-1: Disk Space Required to Install EDCS II _____________________________________________________________ Type_of_Installation______Blocks_____Assumption______________ Client 13,000 No menu interface Server 30,000 Client and Server 36,000 No menu interface Client and DECwindows 24,000 Client and DECforms 33,000 DECwindows 19,000 Client previously in- stalled DECforms 28,000 Client previously in- stalled Client/Server/DECforms 65,000 /DECwindows__________________________________________________ In addition to the disk space shown in Table 1-1, if you plan to print the EDCS II Reference Manual in PostScript format at your site, add 5,000 blocks of required disk space. If you plan to print the EDCS II Reference Manual in text format, add 3,000 blocks required disk space. See the Associated Documents section for more information. To determine the number of free disk blocks on the current system disk, enter the following command: $ SHOW DEVICE SYS$SYSDEVICE If you do not have enough free blocks of space to do a full installation (for example, server, client, and both menu interfaces or client and both menu interfaces), you can install EDCS II without a menu interface, then install the menu interface separately later. You can install the menu interface later because running EDCS II does not take as many blocks of space as installing it does. Preparing for Installation 1-5 VMSINSTAL operates in safety mode if enough free blocks are available. If a system failure occurs during installation, the system is still recoverable. If you do not have enough blocks, VMSINSTAL operates in an alternative mode that re- duces peak use. If a system failure occurs in the alternative mode, files on the system disk can be corrupted, and the system disk may not be recoverable. 1-6 Preparing for Installation ____________________________________________________________ 1.1.5 Disk Space Required to Operate EDCS II After the installation, the disk space shown in Table 1-2 is required to operate EDCS II. These sizes are approxi- mate; actual sizes may vary depending on the user's system environment, configuration, and software options selected. NOTE The database should not be installed on the system disk. Table 1-2: Disk Space Required to Operate EDCS II _____________________________________________________________ Type_of_Installation_________________Mbytes__________________ Client only 6 DECforms only 8 DECwindows only 12 Client and Server with DECforms and 16 DECwindows___________________________________________________ NOTE For 20 or more concurrent users connected to the server, at least 32 Mbytes is recommended. For 10 or more concurrent users on any one client, a minimum of 16 Mbytes is recommended. ____________________________________________________________ 1.1.6 System Parameter Values The following sections describe: o Minimum system parameter values required for EDCS II o System parameter recommendations for larger systems with heavy usage o Checking system parameter values Preparing for Installation 1-7 o Calculating the GBLPAGES and GBLSECTIONS system parameter values o Changing system parameter values ____________________________________________________________ 1.1.6.1 Minimum System Parameter Values Required Table 1-3 lists the minimum required system parameter values for the installation. Depending on the programs and applica- tions running at your site, you may need higher values for some settings. Table 1-3: Minimum Required System Parameters for EDCS II _____________________________________________________________ System Parameter______Client____Server____Both______________________ BALSETCNT[1] n + 2 n + 3 + n + 5 [3] CHANNELCNT[2] 2,000 N/A 2,000 GBLPAGES[1] n + n + n + 6,200 3,500 3,900 GBLPAGFIL[1] n + n + n + 6,200 3,500 3,900 GBLSECTIONS[1] n + 23 n + 15 n + 30 MAXPROCCNT[1] n + 2 n + 3 + n + 5 [3] PROCSECTCNT N/A 48 48 WSMAX 1,000 2,000 2,000 [1]The_n_variable_refers_to_the_system_parameter_values_that_ are currently in use on your system. To install EDCS II, you must raise those values by the number indicated. [2]Kitinstal does not check for this value, however this setting has been strongly recommended. [3]The number of command processors in your system. _____________________________________________________________ 1-8 Preparing for Installation ____________________________________________________________ 1.1.6.2 System Parameter Recommendations for Larger Systems with Heavy Usage Table 1-4 lists the recommended system parameter values for larger systems with heavy usage, depending on the programs and applications running at your site. You should consider increasing these values if: o Your system has 32 or more megabytes of main memory. o The EDCS II users on your system will be using the /DELIVER qualifier (an I/O intensive activity). o Your system has adequate memory to support the higher values. See the EDCS II Administrator's Guide for more information about effective use of EDCS II on larger systems with heavy usage. Table 1-4: Recommended System Parameters for Larger Systems with Heavy Usage _____________________________________________________________ System Parameter______Client____Server____Both______________________ WSMAX[1] 8,000 16,000 16,000 CHANNELCNT 2,000 N/A 2,000 LOCKIDTBL N/A 10,000 10,000 PIOPAGES[2] 2,000 2,000 2,000 [1]For_systems_with_128_megabytes_of_main_memory_or_more,____ these values can be higher. [2]These values are recommended to avoid the "Dynamic Memory Exhausted" error. _____________________________________________________________ The GBLPAGES and GBLPAGFIL setting may be increased according to specific usage needs. See the EDCS II Administrator's Guide for more information on calculating these settings. Preparing for Installation 1-9 ____________________________________________________________ 1.1.6.3 Checking System Parameter Values You can check the values for the system parameters by invok- ing the SYSGEN utility. However, for the system parameters GBLPAGES and GBLSECTIONS, you must perform other calculations as well, to assure correct minimum values. Section 1.1.6.4 contains information about these calculations. To check the values of your system parameters, invoke the SYSGEN utility by entering the following command at the DCL prompt: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> At the SYSGEN> prompt, enter the SHOW command to display the values of each system parameter. The following command displays the values for the WSMAX system parameter: SYSGEN> SHOW WSMAX Parameter Name Current Default Minimum Maximum Unit Dynamic -------------- ------- ------- ------- ------- ---- ------- WSMAX 8192 1024 60 100000 Pages This shows you the "Current" (Current Allocated Maximum) value of the parameter. This current value should equal or exceed the value indicated in Table 1-3 for WSMAX. You can also directly check the value of the PROCSECTCNT parameter using the SYSGEN utility. For the GBLPAGFIL parameter you should increase the cur- rent value by the amounts indicated in Table 1-3 (depend- ing on the type of installation you are doing), because you cannot check how many units of the GBLPAGFIL parame- ter are in use. However, you can check how many units of the GBLPAGES and GBLSECTIONS parameters are in use, as explained in Section 1.1.6.4. To change the current values of system parameters, see Section 1.1.6.5. After you finish checking the parameters with the SHOW com- mand, enter the EXIT command at the SYSGEN> prompt to return to the DCL level. 1-10 Preparing for Installation For more information about the SYSGEN utility, see the VMS System Management Volume 1B Setup manual. ____________________________________________________________ 1.1.6.4 Calculating the GBLPAGES and GBLSECTIONS System Parameter Values To set the correct values for the GBLPAGES and GBLSECTIONS parameters, you must know: o The current value that is set for these parameters (this value can be changed) o The number of parameter units already used on your system o The number of parameter units required for the EDCS II installation To calculate the correct values for these parameters, perform the following steps: 1. Run the VMS Install utility (INSTALL) by using the follow- ing DCL command: $ INSTALL LIST/GLOBAL/SUMMARY The INSTALL utility displays a summary of global sections used by your system, and the current number of unused global pages. For example: Summary of Local Memory Global Sections 258 Global Sections Used, 22580/3420 Global Pages Used/Unused 2. Check the global pages. Determine if the number of unused global pages is equal to or greater than the number spec- ified in Table 1-3. If the number of unused pages is less than the number listed in the table, you must increase the value for GBLPAGES. To do this, see Section 1.1.6.5. Preparing for Installation 1-11 3. Note the amount shown for "Global Sections Used". Now, check the current maximum value of the GBLSECTIONS parame- ter by running the SYSGEN utility. $ RUN SYS$SYSTEM:SYSGEN SYSGEN> SHOW GBLSECTIONS Parameter Name Current Default Minimum Maximum Unit Dynamic -------------- ------- ------- ------- ------- ---- ------- GBLSECTIONS 512 250 20 4095 Sections 4. Subtract the number of sections used (258) from the cur- rent amount allocated (512). If the difference is less than the number required in Table 1-3, you need to in- crease the value of the GBLSECTIONS parameter by at least the difference between the unused sections and the value as specified in Table 1-3. To do this, see Section 1.1.6.5. ____________________________________________________________ 1.1.6.5 Changing System Parameter Values You can use either the SYSGEN utility or the AUTOGEN command procedure to change system parameters. However, the option used depends on how the system administrator generally han- dles system settings at your site. Using the wrong method could adversely affect your system setup. For more information about the SYSGEN utility, see the VMS System Management Volume 1B Setup manual. For more infor- mation about the AUTOGEN command procedure, see the section entitled "Guide to Setting up a VMS System" in the VMS System Management Volume 1A Setup manual. ____________________________________________________________ 1.1.7 Network Parameter Values Required The following sections describe how to check your network pa- rameter values, and how to calculate and change your Maximum Links value. 1-12 Preparing for Installation ____________________________________________________________ 1.1.7.1 Checking Network Parameter Values You can check the values for the network parameters by invok- ing the NCP utility. To invoke the NCP utility, enter the following command: $ RUN SYS$SYSTEM:NCP NCP> Preparing for Installation 1-13 Then, to display the values of the network parameters, enter the following command: NCP>SHOW EXECUTOR CHARACTERISTICS Node Volatile Characteristics as of 11-JUL-1989 12:19:29 Executor node = 21.125 (VOLTA) Identification = DECnet-VAX V5.4, VMS T5.4-4FK Management version = V4.0.0 Incoming timer = 45 Outgoing timer = 60 Incoming Proxy = Enabled Outgoing Proxy = Enabled NSP version = V4.1.0 Maximum links = 32 Delay factor = 80 Delay weight = 5 Inactivity timer = 60 Retransmit factor = 10 Routing version = V2.0.0 Type = nonrouting IV Routing timer = 600 Broadcast routing timer = 180 Maximum address = 1023 Maximum circuits = 16 Maximum cost = 1022 Maximum hops = 30 Maximum visits = 63 Maximum area = 63 Max broadcast nonrouters = 64 Max broadcast routers = 32 Maximum path splits = 1 Area maximum cost = 1022 Area maximum hops = 30 Maximum buffers = 100 Buffer size = 576 Default access = incoming and outgoing Pipeline quota = 10000 Alias maximum links = 32 Path split policy = Normal Maximum Declared Objects = 31 Notice that the Maximum links value in this example is 32. 1-14 Preparing for Installation ____________________________________________________________ 1.1.7.2 Calculating the Maximum Links Network Parameter Values Table 1-5 shows how to calculate the number of links re- quired. Table 1-5: Number of Links Required _____________________________________________________________ Links_Required_________Calculation___________________________ To a server Each client requires two links to a server, plus the number of logged in users. To a client Client links must equal at least two, plus the number of logged in users, multiplied by the number of servers that the client connects to. Commands which trans- One additional link while the transfer fer_files______________is_in_progress._______________________ For Version 2.1, it is likely that the server will need to increase Maximum Links. For the client, it depends on how many logged in users there will be at any one time. The above is true even on configurations where the client and server are on the same node. The maximum value for Maximum Links is 960. The default value of Maximum Links is 32. For more information about network parameters, see the VMS Network Control Program Manual. ____________________________________________________________ 1.1.7.3 Changing Network Parameters The following command changes network parameters for Maximum Links to 64: NCP> SET EXECUTOR MAXIMUM LINKS 64 To return to the DCL level, enter the following command: NCP> EXIT Preparing for Installation 1-15 ____________________________________________________________ 1.1.8 Minimum Process Quotas Required The account you use to install EDCS II must have sufficient quotas to enable you to perform the installation. Table 1-6 summarizes the process quotas required to perform the instal- lation. Table 1-6: Minimum Process Quotas for EDCS II _____________________________________________________________ Minimum_Quota____Value_______________________________________ ENQLM 2000 FILLM____________50__________________________________________ The SYSUAF.DAT file stores user account quotas. You use the VMS Authorize utility to verify and change user account quo- tas. Set your directory to SYS$SYSTEM, then run the Authorize utility: $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> At the UAF> prompt, use the SHOW command with an account name to check a particular account. For example: UAF> SHOW SMITH To change a quota, use the MODIFY command at the UAF> prompt. MODIFY has the following format: UAF> MODIFY account-name /quota-name=nnnn The following example changes the FILLM quota for the SMITH account, then exits from the Authorize utility: UAF> MODIFY SMITH /FILLM=50 UAF> EXIT After you exit from the utility, the VMS system displays messages indicating whether or not changes were made. Once the changes have been made, you must log in again for the new quotas to take effect. 1-16 Preparing for Installation For more information about modifying account quotas, see the "Authorize" section in the VMS System Management Volume 3 Security manual. ____________________________________________________________ 1.1.9 VMSINSTAL Notification of Requirements When you invoke VMSINSTAL, it checks the following: o Whether you have logged in to a privileged account o Whether you have adequate SYSGEN quotas for installation o Whether DECnet is up and running o Whether any users have logged in to the system If VMSINSTAL detects any problems during the installation, it notifies you of the problem and asks if you want to con- tinue the installation. In some instances, you can enter YES to continue. To stop the installation process and correct the situation, enter NO or press Return. Then, correct the problem and restart the installation. See the VMS Installation Guide for more information regarding the VMSINSTAL procedure. ____________________________________________________________ 1.2 Shutting Down Previous EDCS Versions Log in to the SYSTEM account. If you have VAX EDCS Version 1.2 installed and running, shut down VAX EDCS. To do this, invoke the Utility Main Menu and select the Manage VAX EDCS menu. From this menu, shut down VAX EDCS and delete global sections. The VAX EDCS Administrator's Guide describes this further. If you have EDCS II Version 2.0 installed and running, shut down EDCS II. To do this, enter the EDCS Management Utility (EMU) and use the Shutdown System command for the Server: $ EMU EDCS Utility> SHUTDOWN SYSTEM/SERVER EDCS Utility> EXIT Preparing for Installation 1-17 If entered on a server, this command shuts down VAX EDCS on that server. If entered on a client, the command shuts down VAX EDCS on that client. If both the server and client are on the same node, then you must enter this command twice, once for the client and once for the server, as follows: $ EMU EDCS Utility> SHUTDOWN SYSTEM/SERVER EDCS Utility> SHUTDOWN SYSTEM/CLIENT EDCS Utility> EXIT You should also delete the global sections. In EMU, enter the following command: $ EMU EDCS Utility> DELETE SECTIONS EDCS Utility> EXIT See the EDCS II Administrator's Guide for information about these commands. If you have a field test version of EDCS II Version 2.1 installed and running, shut down EDCS II. To do this, run the command procedure SYS$STARTUP:EDCS$SHUTDOWN.COM. This shuts down both the client and server software and automatically deletes all global sections. For more information, see the EDCS II Administrator's Guide. ____________________________________________________________ 1.3 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 on top of the operating system. Use the backup procedures that have been established at your site. For details about performing a system disk backup, see the "Backup" section in the VMS System Management Volume 2 Maintenance manual. 1-18 Preparing for Installation ____________________________________________________________ 1.4 Registering Your Software License Before you install EDCS II, register your EDCS II software license. To do this, you must run the License Management Utility, which is a part of the License Management Facility (LMF). This utility prompts you for information about your license that you can find on the piece of paper entitled the Product Authorization Key (PAK). The PAK is shipped with the EDCS II product. Refer to the VMS License Management Utility Manual for more information. During the installation, you are asked if you have registered and loaded the authorization key. If you have successfully run the License Management Utility, answer YES. If you have not, you can still complete the installation; however, you will not be able to run either the EDCS II software or the Installation Verification Procedure (IVP) until you run the License Management Utility. ____________________________________________________________ 1.5 Procedure for Converting a VAX EDCS Database If you are converting to EDCS II from VAX EDCS, you must run a command procedure that converts a Version 1.1A or Version 1.2 database to a Version 2.1 database. You must convert your database because of differences in the EDCS II database relations, entity names, lists, attributes, and so forth. See Appendix B of the EDCS II Administrator's Guide for more information about database conversion. ____________________________________________________________ 1.6 Gathering Information Before You Install The following sections list information necessary for: o All EDCS II installations o Installing EDCS II as both server and client o Installing EDCS II as a server only o Installing EDCS II as a client only Preparing for Installation 1-19 ____________________________________________________________ 1.6.1 Information Needed for All Installations Check the following list before you start to install EDCS II. Make sure: o You have a SYSTEM account with a SYSTEM UIC on the target system. If the SYSTEM account does not exist, create one with the Authorize utility. o DECnet is up and running. Enter the following command: $ SHOW NETWORK VMS displays available network nodes if the network is up, or displays a message if the network is down. o You have VMS Version 5.3-2 or higher installed on the target system. o You have VAX Rdb/VMS Version 3.1B or higher installed on the target system if you are installing both a server and a client or only a server. To check that VAX Rdb/VMS is up and running, invoke RDO; then enter SHOW VERSION. $ RUN SYS$SYSTEM:RDO RDO> SHOW VERSION Current version of RDO is: Rdb/VMS 3.1B-0 RDO> EXIT o You have made a backup copy of your system disk and any previously installed VAX EDCS data files before you in- stall EDCS II. o Your system has enough free blocks on the system disk. See Section 1.1.4 for more information about disk space re- quirements. If you are creating a new database, make sure that there is enough space on the disk for the database files. o Your system parameter value settings are adequate for your installation. See Section 1.1.6.1 for more information. o Your network parameter value settings are adequate for your installation. See Section 1.1.7 for more information. o The ENQLM limit is set to at least 2000 and the FILLM limit is set to at least 50. 1-20 Preparing for Installation o You know the name of the device on which the distribution kit will be mounted, in other words, the physical location of the EDCS II savesets EDCS021.A through EDCS021.H. o You know the device on which the EDCS II database will reside. Make sure that the disk name for the server files is a device name or a logical name that does not have mul- tiple definitions. Do not use process-rooted (concealed) logical names in the naming of devices, directories, or processes. Process-rooted (concealed) logicals do not work because EDCS II runs multiple processes as part of its system. Disk logical names can be no longer than 15 characters. ____________________________________________________________ 1.6.2 Information Needed for Installing EDCS II as Both Client and Server Make sure that you have assembled the following information before you begin the installation. You will be asked: o Whether you want to view the preinstallation text. This text contains important information condensed from the EDCS II Installation Guide for the first-time installer. You may bypass this information, however it is recommended for the first-time installer. o Whether you want to copy the EDCS II Reference Manual to the SYS$HELP directory so you can print it after the installation. o Whether you are installing a client, a server, or both. o Whether you want to install the DECwindows interface. o Whether you want to install the DECforms interface. o The name of the EDCS II database. o The number (X.Y) of the database. This number (both the first and second part) is currently arbitrary. The two parts can be whatever the user likes. o The name of the disk used by the Notification Manager. o The name of the disk where you want the EDCS II database to reside. Preparing for Installation 1-21 o The name of the disk where you want to install the data files. o The name of the disk that the client will use for its temporary scratch area. o Whether you want to create a new database. o If you choose to create a database during the installa- tion, you are also asked if you want to use the default locations for the database area and snapshot files. These files contain the actual data for the database files. They do not have to be on the same disk or in the same direc- tory as the database root file, or as each other. You can achieve the best performance by spreading the files over the largest number of disks. You can, however, use the default locations for the files if you wish. o The password for the Administrator and the Operator ac- counts. o When EDCS II is installed the first time, you will be prompted for the User Identification Codes (UIC) for the EDCS II network (EDCSNET) and mail (EDCSMAIL) accounts, and the password for the EDCSMAIL account. ____________________________________________________________ 1.6.3 Information Needed for Installing EDCS II as a Server Only Make sure that you have assembled the following information before you begin the installation. You will be asked: o Whether you want to view the preinstallation text. This text contains important information condensed from the EDCS II Installation Guide for the first-time installer. You may bypass this information, however it is recommended for the first-time installer. o Whether you want to copy the EDCS II Reference Manual to the SYS$HELP directory so you can print it after the installation. o Whether you are installing a client, a server, or both. o The name of the client node. o The name of the EDCS II database. 1-22 Preparing for Installation o The number (X.Y) of the database. This number (both the first and second part) is currently arbitrary. The two parts can be whatever the user likes. o The name of the disk used by the Notification Manager. o The name of the disk where you want the EDCS II database to reside. o The name of the disk where you want to install the data files. o Whether you want to create a new database. o If you choose to create a database during the installa- tion, you are also asked if you want to use the default locations for the database area and snapshot files. These files contain the actual data for the database files. They do not have to be on the same disk or in the same direc- tory as the database root file, or as each other. You can achieve the best performance by spreading the files over the largest number of disks. You can, however, use the default locations for the files if you wish. o The password for the Administrator and the Operator ac- counts. o When EDCS II is installed the first time, you will be prompted for the User Identification Codes (UIC) for the EDCS II network (EDCSNET) and mail (EDCSMAIL) accounts, and the password for the EDCSMAIL account. ____________________________________________________________ 1.6.4 Information Needed for Installing EDCS II as a Client Only Make sure that you have assembled the following information before you begin the installation. You will be asked: o Whether you want to view the preinstallation text. This text contains important information condensed from the EDCS II Installation Guide for the first-time installer. You may bypass this information, however it is recommended for the first-time installer. o Whether you want to copy the EDCS II Reference Manual to the SYS$HELP directory so you can print it after the installation. Preparing for Installation 1-23 o Whether you are installing a client, a server, or both. o Whether you want to install the DECwindows interface. o Whether you want to install the DECforms interface. o The name of the server node. o The name of the EDCS II database. o The number (X.Y) of the database. This number (both the first and second part) is currently arbitrary. The two parts can be whatever the user likes. o The name of the disk that the client will use. o The name of the disk where the EDCS II database will reside. 1-24 Preparing for Installation Chapter 2 Installing EDCS II ________________________________________________________________ This chapter describes the installation procedure. ____________________________________________________________ 2.1 Installation Procedure Log in to the SYSTEM account. DECnet must be up and running during installation, so that the EDCS II startup procedure will work correctly. The following procedure installs EDCS II. The defaults to all questions are in brackets []. Press Return to accept the default. $@SYS$UPDATE:VMSINSTAL EDCS021 SYS$UPDATE OPTIONS N In the preceding example, the EDCS II software kit is located in the SYS$UPDATE directory. Substitute your own location, if different, for the one shown. The release notes option (OPTIONS N) has been included in the command line. For more information about reading the release notes, see Section 2.2. The first part of the installation procedure describes pre- liminary requirements and considerations. Chapter 1 describes these preliminary requirements in more detail. Installing EDCS II 2-1 The appendixes shown in Table 2-1 contain sample installa- tions. Table 2-1: Sample Installation Logs _____________________________________________________________ Appendix Installation of both client and server, including A DECwindows and DECforms user interfaces Appendix Installation of server only B Appendix Installation of client only C____________________________________________________________ ____________________________________________________________ 2.2 Reading the Online Release Notes EDCS II provides online release notes. Digital recommends that you read the release notes before installing EDCS II to see if there are: o Special installation considerations o Omissions or errors in the documentation To display, print, or copy the online release notes to the SYS$HELP directory, enter the OPTIONS N parameter on the in- stallation command line. The installation procedure contains four release notes options, as follows. Choose one of these options; the default option is 2. Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: After EDCS II has been installed, the release notes are located in the file SYS$HELP:EDCS021.RELEASE_NOTES. 2-2 Installing EDCS II Online HELP also directs you to the release notes file. After the installation, you can enter the following command to review the release notes: $HELP EDCS RELEASE_NOTES ____________________________________________________________ 2.3 Aborting the Installation To abort the installation procedure at any time, press Ctrl /y. When you press Ctrl/y, the installation procedure deletes all files it has created up to that point and exits. You can then restart the installation. ____________________________________________________________ 2.4 Error Recovery If errors occur during the installation itself or when the Installation Verification Procedure (IVP) is running, VMSINSTAL displays failure messages. For more information about the IVP, see Section 3.1. If the installation fails, the following message is displayed: %VMSINSTAL-E-INSFAIL, The installation of EDCS II has failed. If the IVP fails, the following messages are displayed: The EDCS II Installation Verification Procedure failed. %VMSINSTAL-E-IVPFAIL, The IVP for EDCS II has failed. Errors can occur during the installation if any of the fol- lowing conditions exist: o The prerequisite software version is incorrect. o Quotas necessary for successful installation are insuffi- cient. o System parameter values for successful installation are insufficient. o Disk space is insufficient. o The VMS HELP library is currently in use. Installing EDCS II 2-3 o The product is not properly licensed. If you receive a message about any of the preceding condi- tions, take action to resolve the problem. It is possible you will need to change a system parameter or increase an autho- rized quota value. See Section 1.1.6.1 for more information about parameters or Section 1.1.8 for more information about quota values. Log out of VMS, then log back in and perform the installation procedure again. This helps to ensure a proper environment for VMSINSTAL. Appendix D contains common VMSINSTAL errors and their solu- tions. 2-4 Installing EDCS II Chapter 3 After the Installation ________________________________________________________________ This chapter describes procedures you can perform after EDCS II is installed. ____________________________________________________________ 3.1 Running the IVP After the Installation The Installation Verification Procedure (IVP) verifies that software has been installed correctly on the desig- nated system. The command procedure EDCS$IVP_CLIENT.COM (for the client), EDCS$IVP_SERVER.COM (for the server), or EDCS$IVP_BOTH.COM (for both the client and the server) is placed in the SYS$TEST directory during installation. Because the EDCS II IVP involves starting EDCS II, the privi- leges required to start EDCS II are also required to run the IVP. These privileges are: o CMKRNL o SYSNAM o DETACH o SETPRV o TMPMBX o WORLD o OPER o EXQUOTA o NETMBX o PRMGBL After the Installation 3-1 o SYSGBL o SYSPRV o SYSLCK See the EDCS II Administrator's Guide for more information about privileges. The EDCS II IVP can be run during or after the installation. If you request that the IVP be run during installation time, VMSINSTAL invokes the IVP after the EDCS II components have been moved to their target directories. To run the IVP at any time other than during the installa- tion, you must do one of the following two things: o Shut down EDCS II, ensuring that all EDCS II processes exit successfully. o Make sure that at least twice the number of the system parameters GBLPAGES (global pages) and GBLSECTIONS (global sections) are available compared to the number normally required for an EDCS II installation. Table 1-3 provides this parameter information. Then use one of the following commands: o For both the client and server, enter the following com- mand: $ @SYS$TEST:EDCS$IVP_BOTH.COM o For the server only, enter the following command: $ @SYS$TEST:EDCS$IVP_SERVER.COM o For the client only, enter the following command: $ @SYS$TEST:EDCS$IVP_CLIENT.COM The IVP runs tests and displays success and error messages to indicate whether the installation was successful. The following example shows successful output of the IVP run on a client and server system. 3-2 After the Installation $ @SYS$TEST:SYS$TEST:EDCS$IVP_BOTH.COM -------------------------------------------------------------------------------- - - - THE EDCS II IVP - - Checking the RDMS_MONITOR - - - -------------------------------------------------------------------------------- Rdb/VMS (RDMS_MONITOR) has been previously started -------------------------------------------------------------------------------- - - - THE EDCS II IVP - - Starting EDCS II - - - -------------------------------------------------------------------------------- %DCL-I-SUPERSEDE, previous value of EDCS$LIBRARY has been superseded ------------------------------------------------------------------------------- - - - THE EDCS II IVP - - Checking to see if EDCS II is running - - - -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- - - - THE EDCS II IVP - - Shutting down EDCS II. - - - -------------------------------------------------------------------------------- Processing CLIENT... %EDCS-S-FASTSHUTDOWN, EDCS II is being shut down -- all outstanding requests are canceled %EDCS-S-GBLDELETED, The global sections have been deleted Processing SERVER... %EDCS-S-FASTSHUTDOWN, EDCS II is being shut down -- all outstanding requests are canceled %EDCS-S-GBLDELETED, The global sections have been deleted Deinstalling images... Deinstallation done. -------------------------------------------------------------------------------- - - - The EDCS II IVP HAS COMPLETED SUCCESSFULLY. - - All of the required processes are present. - - - -------------------------------------------------------------------------------- After the Installation 3-3 After you run the IVP, restart EDCS II. See Section 3.4 for more information. ____________________________________________________________ 3.2 Editing Parameter Files When you start up EDCS II, it reads parameter files that contain parameters that you can tune to fit your individual site's needs. A server parameter file exists for every EDCS II server. Likewise, a client parameter file exists for every EDCS II client. Before you start up EDCS II, review the server and client parameter files and make sure that they contain accurate and complete information regarding your EDCS II configuration. You should review these files before you start up EDCS II, because any changes you make to the files do not take effect until the next startup of EDCS II. However, you can make changes to the parameter files at any time. EDCS II enters information in the server and client parameter files according to data you provide during the installation procedure. When you install a server, information regarding one client that can access the server and its database is entered in the server parameter file. When you install a client, you enter information regarding one database that the client can access in the client parameter file. If your configuration contains more than one database that the client can access, you must enter this additional database information in the client parameter file. Likewise, if your configuration has more than one client that can access the server and its database, you must enter this additional client information in the server parameter file. See Chapter 3 of the EDCS II Administrator's Guide for more information about editing the parameter files. ____________________________________________________________ 3.3 Running EDCS II on a VAXcluster When you install EDCS II in a VAXcluster, whether the VAXcluster uses a cluster alias for EDCS II or not, you must install both a client and a server. 3-4 After the Installation For a VAXcluster that uses a cluster alias, this assumes that every node in the VAXcluster will be running EDCS II server and client software. For a VAXcluster that does not use a cluster alias, this assumes that at least one node in the VAXcluster will be running EDCS II server and client software. For more information, see the EDCS II Administrator's Guide. ____________________________________________________________ 3.4 Starting Up EDCS II You can set things up so that EDCS II starts up automatically whenever VMS starts up. You can also start up EDCS II indi- vidually without having to start up VMS, if VMS is already running. Chapter 3 of the EDCS II Administrator's Guide describes how to accomplish both forms of EDCS II startup. ____________________________________________________________ 3.5 Running Verify and Repair If you have database files from a previous version of VAX EDCS, you should run the Verify Files, Verify Element, and Repair Element utilities after the EDCS II installation. This will ensure that database information is complete and consistent after the conversion from VAX EDCS to EDCS II. See the EDCS II Administrator's Guide for information about how to run the Verify and Repair utilities. Appendix B of the EDCS II Administrator's Guide describes how to convert a VAX EDCS database to an EDCS II database. After the Installation 3-5 Appendix A Sample Installation of EDCS II as Both a Server and Client ________________________________________________________________ $ @SYS$UPDATE:VMSINSTAL EDCS021 MUA0 OPTIONS n VAX/VMS Software Product Installation Procedure V5.3-2 It is 13-MAR-1991 at 14:30. Enter a question mark (?) at any time for help. %VMSINSTAL-W-ACTIVE, The following processes are still active: JONES SMITH JOHNSON * Do you want to continue anyway [NO]? yes * Are you satisfied with the backup of your system disk [YES]? The following products will be processed: EDCS V2.1 Beginning installation of EDCS V2.1 at 14:30 %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]: 4 * Do you want to continue the installation [NO]? yes %VMSINSTAL-I-RELMOVED , The product's release notes have been successfully moved to SYS$HELP. * Do you want to view preinstallation text guide [YES]? yes Sample Installation of EDCS II as Both a Server and Client A-1 ******************************************************************************** Before you continue with your installation of EDCS II Version 2.1, please read the following preinstallation information. This will help you install EDCS II successfully. ******************************************************************************** PREINSTALLATION INFORMATION Before you install EDCS II Version 2.1, shut down previous versions of EDCS, and back up your system. SHUTTING DOWN PREVIOUS VERSIONS OF EDCS ======================================= If you have VAX EDCS Version 1.2 installed and running, shut down VAX EDCS. To do this, invoke the Utility Main Menu and select the Manage VAX EDCS menu. From this menu, select Shut Down VAX EDCS and Delete Global Sections. If you have EDCS II Version 2.0 or Version 2.1 installed and running, shut down EDCS II. To do this, run the SYS$STARTUP:EDCS$SHUTDOWN.COM command procedure. This shuts down both the client and server software, automatically deletes all global sections, and deinstalls the EDCS related images. BACKING UP SYSTEM ================= At the beginning of the installation, VMSINSTAL asks if you have backed up your system disk. Digital recommends that you back up your system disk before installing any software on top of the operating system. Use the backup procedures that have been established at your site. For details about performing a system disk backup, see the Backup section in the VMS System Management Volume 2 Maintenance manual. ABORTING THE INSTALLATION ========================== To abort the installation procedure at any time, press Ctrl/y. When you press Ctrl/y, the installation procedure deletes all files it has created up to that point and exits. You can then restart the installation. FULLY UPGRADING YOUR SYSTEM =========================== When installing EDCS II Version 2.1, be sure to fully upgrade your system. EDCS II Version 2.1 is incompatible with Version 2.0. Therefore, you can not run Version 2.0 on a client and Version 2.1 on a server, or vice versa. A-2 Sample Installation of EDCS II as Both a Server and Client CONVERTING VAX EDCS VERSION 1.2 TO EDCS II VERSION 2.1 ====================================================== If you are converting to EDCS II Version 2.1 from VAX EDCS, you must run a command procedure that converts a Version 1.1A or Version 1.2 database to a Version 2.1 database. You must convert your database because of differences in the EDCS II database relations, entity names, lists, attributes, and so forth. If you are currently running Version 2.0, you do not have to convert your database. See Appendix B of the EDCS Administrator's Guide for the procedure on database conversion. SOFTWARE REQUIRED ================= The following software must be installed on your system before you install EDCS II Version 2.1: 1. VMS Version 5.3-2 or higher. 2. DECwindows Version (same version as VMS), if you want a DECwindows interface. 3. DECforms Version 1.2-26, if you want a DECforms interface. 4. DECnet (same Version as VMS). 5. VAX Rdb/VMS Version 3.1B or higher (required for a server installation only). Please note that only the run-time license of VAX Rdb/VMS is required. SYSTEM ACCOUNT RECOMMENDED FOR INSTALLATION ============================================ Digital recommends that you install EDCS II with a SYSTEM account and a SYSTEM UIC on the target system. If the SYSTEM account does not exist, create one with the Authorize Utility. TIME REQUIRED FOR INSTALLATION ============================== Installation takes from 40 minutes to 2 hours. PRIVILEGES REQUIRED TO INSTALL EDCS II ====================================== To install EDCS II, you must be logged in to an account that has SETPRV or the 5 following VMS privileges: Sample Installation of EDCS II as Both a Server and Client A-3 CMKRNL EXQUOTA SYSLCK SYSPRV WORLD DISK SPACE REQUIRED TO INSTALL EDCS II ====================================== Check your disk space before installing EDCS II. To determine the number of free disk blocks on your system, enter the following: $ SHOW DEVICE SYS$SYSDEVICE The following table can help you determine if you have enough memory for your specific installation: ________________________________________________________________ | Type of Installation Blocks Assumption | |----------------------------------------------------------------| | Client 13,000 No menu interface | | Server 30,000 | | Server and Client 36,000 No menu interface | | Client and DECwindows 24,000 | | Client and DECforms 33,000 | | DECwindows 19,000 Client previously installed | | DECforms 28,000 Client previously installed | | Client/Server/DECforms/ | | DECwindows 65,000 | |________________________________________________________________| In addition to the disk space shown in the preceding table, if you plan to print the EDCS II Reference Manual in PostScript format at your site, add 5,000 blocks to the required disk space. If you plan to print the EDCS II Reference Manual in text format, add 3,000 blocks to the required disk space. For more information, see the EDCS II Installation Guide. DISK SPACE REQUIRED TO OPERATE EDCS II ====================================== The following table shows recommended disk space to operate EDCS II after installation. Type of installation Mbytes -------------------- ------ Client only 6 DECforms 8 DECwindows 12 Server with Client and DECform and DECwindows 16 A-4 Sample Installation of EDCS II as Both a Server and Client For more information, see the EDCS II Installation Guide. SYSTEM AND NETWORK PARAMETER SETTINGS ===================================== System and network parameters must be set for your type of installation. Depending on the programs and applications running at your site, you may need higher values for some settings. For more information, see the EDCS II Installation Guide. PROCESS QUOTAS REQUIRED ======================= The account you use to install EDCS II must have enough process quotas to let you install the product. The following table shows the minimum process quotas required: Minimum Quota Value ------------- ----- ENQLM 2000 FILLM 50 For more information, see the EDCS II Installation Guide. REGISTERING YOUR SOFTWARE LICENSE ================================= Before you install EDCS II, you should register your EDCS II software license. To do this, you must run the License Management Utility, which is a part of the License Management Facility (LMF). This utility prompts you for information about your license that you can find on the piece of paper entitled the Product Authorization Key (PAK). The PAK is shipped with the EDCS II product. During the installation, you are asked if you have registered and loaded the PAK. If you have successfully run the LMF, answer YES. If you have not already done so, you can still complete the installation; however, you will not be able to run either the EDCS II software or the Installation Verification Procedure (IVP) until you run the License Management Utility. CONFIGURING EDCS II TO ACHIEVE MAXIMUM PERFORMANCE ================================================== Digital recommends that you create your database on a disk other than the system disk. Digital also recommends that you spread your files over the largest number of disks possible. Sample Installation of EDCS II as Both a Server and Client A-5 The EDCS II database is connected directly to the server node. The server interfaces with the database to process user commands. Each server node can have only one database. You may use multiple server nodes (one server for each node) to create a multiple database (one database for each node) configuration. See the EDCS II Administrator's Guide for more information about configuring EDCS II to maximize performance. INSTALLATION VERIFICATION PROCEDURE (IVP) ========================================= After you install EDCS II, it is recommended that you run IVP, which takes an additional 10 minutes. You need the same privileges to run the IVP as to start EDCS$START processes, as follows: CMKRNL OPER SYSNAM EXQUOTA DETACH NETMBX SETPRV PRMGBL TMPMBX SYSGBL SYSPRV WORLD SYSLCK VIEWING AND PRINTING THE EDCS II REFERENCE MANUAL ================================================= The EDCS II Reference Manual is provided in your installation kit in PostScript (.ps) and ASCII (.txt) formats so that you can print it at your location. To print the Reference Manual if you have a PostScript printer, specify this file: SYS$HELP:EDCS021_REFERENCE_MANUAL.PS To print the Reference Manual if you have a non-PostScript printer, specify this file: SYS$HELP:EDCS021_REFERENCE_MANUAL.TXT The rest of the EDCS II books are available in hardcopy. The EDCS II documentation set, excluding the EDCS II Pocket Guide, is available on CDROM for users who have DECwindows and Bookreader. READING THE RELEASE NOTES ========================= EDCS II provides online release notes. To display, print, or copy the online release notes to the SYS$HELP directory, enter the OPTIONS N parameter on the installation command line. In the following example, the EDCS II software kit is located in SYS$UPDATE. Substitute your own location, if different, for the one shown. A-6 Sample Installation of EDCS II as Both a Server and Client $ SYS$UPDATE:VMSINSTAL EDCS021 SYS$UPDATE OPTIONS N Soon after the installation begins, you are presented with four options so you can choose to display, print, or copy the release notes to a file. After EDCS II has been installed, the release notes are located in the file SYS$HELP:EDCS021.RELEASE_NOTES. Online HELP also directs you to the release notes file. After the installation, to review the release notes, enter the following: $ HELP EDCS RELEASE_NOTES ************************************ - - - The Reference Manual is included with this kit in PostScript (.ps) and - - ASCII (.txt) formats. You can copy one or both to SYS$HELP and print it - - after the installation is completed. - Copy Options: 1. EDCS021_REFERENCE_MANUAL.PS (Requires additional 5,000 blocks) 2. EDCS021_REFERENCE_MANUAL.TXT (Requires additional 3,000 blocks) 3. Both 1 and 2 (Requires additional 8,000 blocks) 4. None of the above * Select option [4]: 1 * Do You want to continue with the installation [no]? yes - - - Digital Equipment Corporation. 1991. All Rights Reserved - - - You are next asked if you want to install a client node, a server node, both, or just a user interface (DECwindows or DECforms). You are then notified of the different user interfaces that are available for use with EDCS. You are also notified which of the user interfaces you have the necessary software to install during this installation. The DCL command line interface will be installed, regardless of additional interfaces chosen at installation time. You are then asked if you want to install the DECwindows interface, which is a menu interface that runs on workstations running DECwindows. You are also asked if you want to install the DECforms interface, which is a menu interface that runs on character cell (VT style) terminals. Sample Installation of EDCS II as Both a Server and Client A-7 Note that in order to install the DECwindows menu interface for EDCS II, the DECwindows software must already be installed. Likewise, in order to install the DECforms menu interface for EDCS II, the DECforms software must already be installed. -------------------------------------------------------------------------------- - - - EDCS II may be installed on your VAX as a CLIENT node only (CLIENT), or - - as a SERVER node only (SERVER), or as both a SERVER and a CLIENT node - - (BOTH) on the same VAX. - - - -------------------------------------------------------------------------------- * Do you want to install EDCS II as a CLIENT node, SERVER node, BOTH, or just an INTERFACE [CLIENT]: both - EDCS II has three different user interfaces - - 1. DCL command line (default interface) - 2. DECwindows Menu interface for DECwindows devices - 3. DECforms Menu interface for VT style devices - Of these you have the necessary software to install: - 1. DCL command line (default interface) - 2. DECwindows Menu interface for DECwindows devices - 3. DECforms Menu interface for VT style devices * Do you want to install the DECwindows Interface [NO]? yes * Do you want to install the DECforms Interface [NO]? yes Installing an EDCS II SERVER node Installing an EDCS II CLIENT node - - Next you are asked if you have registered your EDCS II software license. If you have successfully run the License Management Utility and registered and loaded your Product Authorization Key (PAK), answer YES. If you have not already done so, you can still complete the installation; however, you will not be able to run either the EDCS II software or the Installation Verification Procedure (IVP) until you run the License Management Utility. Product: EDCS-SERVER Producer: DEC Version: 2.1 Release Date: 01-JUL-1990 * Does this product have an authorization key registered and loaded? yes Product: EDCS-CLIENT Producer: DEC Version: 2.1 Release Date: 01-JUL-1990 * Does this product have an authorization key registered and loaded? yes A-8 Sample Installation of EDCS II as Both a Server and Client You are asked if you want to purge files created by previous installations of EDCS II. The installation keeps the database but removes all executable images if they are located on the same disks on which this installation would place them. * Do you want to purge files replaced by this installation [YES]? yes - - - The following questions must be answered regardless of the type of EDCS II - - node being installed (i.e., CLIENT, SERVER, BOTH). The answers supplied will - - be used to create the initialization file for either a CLIENT or SERVER. - - This file can be modified at any time after the installation. - - - You are next asked the name of the EDCS II database (any name up to 15 characters). * Enter the name of the EDCS II database [DEMO]: test You are now asked for the number of the database (X.Y). This number (both the first and second part) is arbitrary. The two parts can be whatever the user wants. The default response is 1.1. * Enter the number of the EDCS II database [1.1]: You are next asked for the name of the disk that the Notification Manager process will use. This disk can be located on any system; the default is SYS$SYSDEVICE. You are also asked for the name of the disk where you want the EDCS II data base to reside and the name of the disk where you want the datafiles to reside. The default response to all of these questions is SYS$SYSDEVICE. * Enter the disk that will be used by the EDCS II Notification Manager [SYS$SYSDEVICE]: * What disk do you want to install the EDCS II database on [SYS$SYSDEVICE:]: * What disk do you want the EDCS II datafiles on [SYS$SYSDEVICE:]: You are next asked the name of the disk that the client will use for its temporary scratch area, which does not take up much disk space. This disk can be located on any system; the default is SYS$SYSDEVICE. * Enter the disk that will be used by the CLIENT [SYS$SYSDEVICE]: Sample Installation of EDCS II as Both a Server and Client A-9 You are asked if you want to create a database at this time. Digital recommends that you create the database at this time. This merely sets up the database structures for you but does not fill the database with any data. If you answer YES or press Return, you are asked if you want to use the default locations for the database area and snapshot files. The database area and snapshot files contain the actual data for the database files. They do not have to be on the same disk or in the same directory as the database root file, or as each other. You can achieve the best performance by spreading the files over the largest number of disks. If you answer NO to this question, you will be prompted for the device for each of these files. You can, however, use the default locations for the files if you wish. * Do you want to create an EDCS II database [YES]? yes You will be asked for the locations of the database area files and the database snapshot files. These files contain the actual data for the database files. They do not have to be in the same directory or on the same disk as either the database root files, or the other area and snapshot files. The best performance can be achieved by spreading the files over the largest number of disks. Press Carriage Return to default to the EDCS$DATABASE area. This command file will prompt you for locations for each of the following areas: ACCOUNT DEFAULT ENTITY GENERATION HISTORY RELATIONSHIPS REVIEW The EDCS II database root file will be stored in SYS$SYSDEVICE:[EDCS.TEST.DATABASE]. * Do you want to use the default for all of the database areas [YES]? A-10 Sample Installation of EDCS II as Both a Server and Client ------------------------------------------------------------------------------- - You are next prompted to enter passwords which must contain 6 to 12 - - characters and cannot contain hyphens, spaces, or special characters. - - Note that the passwords that you enter do not echo on the terminal - - screen. - - Then you are asked if you want to run the IVP after the installation. - - Digital recommends that you run the IVP. - - - - You are next asked for the User Identification Codes (UIC) for the EDCS - - II network (EDCSNET), mail (EDCSMAIL) accounts, and password for EDCSMAIL- - account unless you have already established these accounts in a previous - - EDCS installation. The UIC numbers must be any valid unused, nonsystem - - UICs, in brackets and separated by a comma. If the UIC numbers that you - - enter are already assigned to someone else, you will be given the name - - they are assigned to and you will be prompted for different numbers. - - The password for EDCSMAIL account must contain 8 to 15 characters. - ------------------------------------------------------------------------------- * What is the password you want to use for the administrator's account: edcs$admin * Please reenter the administrator's account password for verification: edcs$admin * What is the password you want to use for the operator's account: edcs$oper * Please reenter the operator's account password for verification: edcs$oper * Do you want to run the IVP after the installation [YES]? yes * Enter the UIC (Octal) for the EDCSNET account: [100,330] %EDCS-I-CHECK, Checking UAF... UIC [100,330] is already assigned to user WALSH, please try again. * Enter the UIC (Octal) for the EDCSNET account: [600,100] %EDCS-I-CHECK, Checking UAF... * Enter the UIC (Octal) for the EDCSMAIL account: [600,101] %EDCS-I-CHECK, Checking UAF... * What is the password you want to use for the EDCSMAIL account: edcs$mail * Please reenter the EDCSMAIL account password for verification: edcs$mail %EDCS-I-NOMORQUES, You have answered all required questions. Sample Installation of EDCS II as Both a Server and Client A-11 You will next see that savesets B, C, D (if installing DECwindows), E (if installing DECforms), F, G and H (if you have selected COPY OPTIONS 1, 2, or 3 to copy the Reference Manual at your site) have been restored. Saveset A was restored earlier in the installation. ------------------------------------------------------------------------------- %VMSINSTAL-I-RESTORE, Restoring product save set B ... %VMSINSTAL-I-RESTORE, Restoring product save set C ... %VMSINSTAL-I-RESTORE, Restoring product save set D ... %VMSINSTAL-I-RESTORE, Restoring product save set E ... %VMSINSTAL-I-RESTORE, Restoring product save set F ... %VMSINSTAL-I-RESTORE, Restoring product save set G ... %VMSINSTAL-I-RESTORE, Restoring product save set H ... The EDCS II installation creates several permanent directories and files. - - - This installation creates the directory structure for EDCS II. - - - %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named EDCSNET. %UAF-I-ADDMSG, user record successfully added %UAF-I-RDBADDMSGU, identifier EDCSNET value: [000600,000100] added to rights data base %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named EDCSMAIL. %UAF-I-ADDMSG, user record successfully added %UAF-I-RDBADDMSGU, identifier EDCSMAIL value: [000600,000101] added to rights data base Creating the EDCS II Server directory structure on disk SYS$SYSDEVICE:. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[EDCS]. Creating Notification directory SYS$SYSDEVICE:[EDCS]NOTIFICATION.DIR A-12 Sample Installation of EDCS II as Both a Server and Client %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[EDCS.NOTIFICATION]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[EDCS.DEMO]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[EDCS.DEMO.DATABASE]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[EDCS.DEMO.DATAFILE]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[EDCS.DEMO.SCRATCH]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[EDCS.DEMO.ARCHIVE]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[EDCS.DEMO.VERIFY]. Creating the EDCS II Client directory structure on disk SYS$SYSDEVICE:. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[EDCS.SCRATCH]. Linking EDCS$MESSAGE (EDCS Message File)... Linking EDCS$RTL_COMMON (Common RTL)... Linking EDCS$RTL_CLIENT (Client RTL)... Linking EDCS$RTL_DML (DML RTL)... Linking EDCS$RTL_SERVER (Server RTL)... Linking EDCS$RTL_UTIL (Server Utility RTL)... Linking EDCS (User interface - Command Line)... Linking EDCS$FTM (File Transfer Manager)... Linking EDCS$CTRL (Client Controller)... Linking EDCS$CMDPROC (Server Command Processor)... Linking EDCS$MAIL (Mail Notification)... Linking EDCS$NETDISP (Network Dispatcher)... Linking EDCS$UTIL (Server EDCS Utility)... Linking EDCS$CONVERT (V1.1 to V2.0 Conversion Utility)... Linking EDCS$SEED_DB (Database Seed Utility)... Linking EDCS$LOAD (EDCS Initializer)... Linking FT CONVERT... Linking EDCS$BATCHLOAD Utility... Linking EDCS$SHOWFILE ... Linking EDCS$DELETE_SECTIONS ... - - - This installation will now create the DATABASE for EDCS II. - - - importing :edcs.rbr' *** Digital Internal Use Only *** Exported by Rdb/VMS V3.1B-0 Export/Import utility A component of Rdb/VMS V3.1B-0 Sample Installation of EDCS II as Both a Server and Client A-13 Previous name was EDCS$DATABASE_DIR:EDCS.RDB It was logically exported on 12-MAR-1991 21:39:28.27 Database NUMBER OF USERS is 50 Database NUMBER OF VAXCLUSTER NODES is 16 Database NUMBER OF DBR BUFFERS is 20 Database SNAPSHOT is ENABLED Database SNAPSHOT is DEFERRED Database BUFFER SIZE is 12 blocks Database NUMBER OF BUFFERS is 20 Definition of STORAGE AREA RDB$SYSTEM overridden Definition of STORAGE AREA ACCOUNT overridden Definition of STORAGE AREA ENTITY overridden Definition of STORAGE AREA GENERATION overridden Definition of STORAGE AREA HISTORY overridden Definition of STORAGE AREA RELATIONSHIPS overridden Definition of STORAGE AREA REVIEW overridden IMPORTing relation ACCOUNT IMPORTing relation ATTRIBUTE IMPORTing relation ATTRIBUTE_ASSOCIATION IMPORTing relation COMMANDS IMPORTing relation DEPENDENCY IMPORTing relation ENTITY IMPORTing relation GENERATION IMPORTing relation GENERATION_REVIEW IMPORTing relation HIERARCHY IMPORTing relation HISTORY IMPORTing relation HISTORY_QUAL IMPORTing relation LIST_ASSOCIATION IMPORTing relation LIST_ENTRY A-14 Sample Installation of EDCS II as Both a Server and Client IMPORTing relation LIST_HEADER IMPORTing relation LOGIN IMPORTing relation PATH IMPORTing relation RESERVATIONS IMPORTing relation REVIEW IMPORTing relation SUBSTITUTE IMPORTing relation SYSTEM IMPORTing relation TEAM IMPORTing view EDCS$SHOW_ENTITY_LIST_ENTRY IMPORTing view EDCS$SHOW_ENTITY_LIST_HEAD IMPORTing view EDCS$SHOW_LIST_HEAD IMPORTing view EDCS$SHOW_LIST_ID IMPORTing view EDCS$ACCOUNT IMPORTing view EDCS$TEAM IMPORTing view EDCS$SYSTEM IMPORTing view EDCS$SUBSTITUTE IMPORTing view EDCS$GROUP_REVIEW IMPORTing view EDCS$ELEMENT_REVIEW IMPORTing view EDCS$PATH IMPORTing view EDCS$GROUP_MAIL_LIST IMPORTing view EDCS$ELEMENT_MAIL_LIST IMPORTing view EDCS$GROUP_ACCESS_LIST IMPORTing view EDCS$ELEMENT_ACCESS_LIST IMPORTing view EDCS$ACCOUNT_HISTORY IMPORTing view EDCS$GROUP_HISTORY IMPORTing view EDCS$ELEMENT_HISTORY IMPORTing view EDCS$GROUP_CONTENTS IMPORTing view EDCS$ENTITY_REVISION_ATTRIBUTES IMPORTing view EDCS$ENTITY_REVISION IMPORTing view EDCS$ENTITY_GENERATION IMPORTing view EDCS$ENTITY_ATTRIBUTES IMPORTing view EDCS$ENTITY IMPORTing view EDCS$GROUP_DEPENDENCY IMPORTing view EDCS$ELEMENT_DEPENDENCY IMPORTing view EDCS$ARCHIVE IMPORTing view EDCS$MAIL_LIST IMPORTing view EDCS$ACCESS_LIST IMPORTing view EDCS_VIEW IMPORTing view HISTORY_USER_VIEW IMPORTing view HISTORY_ELEMENT_VIEW IMPORTing view HISTORY_PROJECT_VIEW IMPORTing view EDCS_AUTHORIZATION_VIEW IMPORTing view MAIL_USER_VIEW IMPORTing view ELEMENT_APPROVAL_VIEW Sample Installation of EDCS II as Both a Server and Client A-15 IMPORTing view PROJECT_APPROVAL_VIEW IMPORTing view ELEMENT_NOTIFY_VIEW IMPORTing view PROJECT_NOTIFY_VIEW IMPORTing view ELEMENT_ACCESS_VIEW IMPORTing view PROJECT_ACCESS_VIEW IMPORTing view GENERATION_VIEW IMPORTing view ELEMENT_VIEW IMPORTing view PROJECT_ELEMENT_VIEW IMPORTing view PROJECT_INFO_VIEW IMPORTing view EDCS_INFO_VIEW IMPORTing view ARCHIVE_VIEW *** Digital Internal Use Only *** *** Digital Internal Use Only *** Seeding the database with default values ... E D C S E D C S E D C S E D C S E D C S E D C S E D C S E D C S E D C S E D C S E D C S E D C S E D C S E D C S E D C S E D C S E D C S E D C S E D C S E D C S E D C S E D C S E D C S Database creation is complete. E D C S E D C S E D C S E D C S E D C S E D C S E D C S E D C S E D C S E D C S E D C S E D C S E D C S E D C S E D C S E D C S E D C S E D C S E D C S E D C S E D C S E D C S E D C S %EDCS-I-DELETE, Deleting EDCS global sections... %EDCS-I-DONE, Global Sections Deleted. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... A-16 Sample Installation of EDCS II as Both a Server and Client Beginning the EDCS II Installation Verification Procedure. - - - - - At the conclusion of the IVP the command procedure is placed into - - SYS$TEST. You can run the IVP command procedure at any time. - - - - - -------------------------------------------------------------------------------- - - - THE EDCS II IVP - - Checking the RDMS_MONITOR - - - -------------------------------------------------------------------------------- Rdb/VMS (RDMS_MONITOR) has been previously started -------------------------------------------------------------------------------- - - - THE EDCS II IVP - - Starting EDCS II - - - -------------------------------------------------------------------------------- %DCL-I-SUPERSEDE, previous value of EDCS$LIBRARY has been superseded %DCL-I-SUPERSEDE, previous value of EDCS$CONFIG has been superseded %DCL-I-SUPERSEDE, previous value of EDCS$RESTART has been superseded %RUN-S-PROC_ID, identification of created process is 000001E8 %RUN-S-PROC_ID, identification of created process is 000004EA %RUN-S-PROC_ID, identification of created process is 000004EB %RUN-S-PROC_ID, identification of created process is 000004ED %RUN-S-PROC_ID, identification of created process is 000002C2 %DCL-I-SUPERSEDE, previous value of EDCS$RESTART has been superseded ------------------------------------------------------------------------------- - - - THE EDCS II IVP - - Checking to see if EDCS II is running - - - -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- - - - THE EDCS II IVP - - Shutting down EDCS II. - - - -------------------------------------------------------------------------------- Processing CLIENT... %EDCS-S-FASTSHUTDOWN, EDCS II is being shut down -- all outstanding requests are canceled Sample Installation of EDCS II as Both a Server and Client A-17 %EDCS-S-GBLDELETED, The global sections have been deleted Processing SERVER... %EDCS-S-FASTSHUTDOWN, EDCS II is being shut down -- all outstanding requests are canceled %EDCS-S-GBLDELETED, The global sections have been deleted Deinstalling images... Deinstallation done. -------------------------------------------------------------------------------- - - - The EDCS II IVP HAS COMPLETED SUCCESSFULLY. - - All of the required processes are present. - - - -------------------------------------------------------------------------------- A-18 Sample Installation of EDCS II as Both a Server and Client Appendix B Sample Installation of EDCS II as a Server ________________________________________________________________ $ @SYS$UPDATE:VMSINSTAL EDCS021 MUA0: OPTIONS N VAX/VMS Software Product Installation Procedure V5.3-2 It is 15-MAR-1991 at 14:05. Enter a question mark (?) at any time for help. %VMSINSTAL-W-ACTIVE, The following processes are still active: JONES JOHNSON * 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: EDCS V2.1 Beginning installation of EDCS V2.1 at 14:06 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED , The product's release notes have been successfully moved to SYS$HELP. * Do you want to view preinstallation text guide [YES]? n - - - The Reference Manual is included with this kit in PostScript (.ps) and - - ASCII (.txt) formats. You can copy one or both to SYS$HELP and print it - - after the installation is completed. - Copy Options: Sample Installation of EDCS II as a Server B-1 1. EDCS021_REFERENCE_MANUAL.PS (Requires additional 5,000 blocks) 2. EDCS021_REFERENCE_MANUAL.TXT (Requires additional 3,000 blocks) 3. Both 1 and 2 (Requires additional 8,000 blocks) 4. None of the above * Select option [4]: 1 * Do You want to continue with the installation [no]? y - - - Digital Equipment Corporation. 1991. All Rights Reserved - - - You are next asked if you want to install a client node, a server node, both, or just a user interface (DECwindows or DECforms). You are then notified of the different user interfaces that are available for use with EDCS. You are also notified which of the user interfaces you have the necessary software to install during this installation. The DCL command line interface will be installed, regardless of additional interfaces chosen at installation time. You are then asked if you want to install the DECwindows interface, which is a menu interface that runs on workstations running DECwindows. You are also asked if you want to install the DECforms interface, which is a menu interface that runs on character cell (VT style) terminals. Note that in order to install the DECwindows menu interface for EDCS II, the DECwindows software must already be installed. Likewise, in order to install the DECforms menu interface for EDCS II, the DECforms software must already be installed. -------------------------------------------------------------------------------- - - - EDCS II may be installed on your VAX as a CLIENT node only (CLIENT), or - - as a SERVER node only (SERVER), or as both a SERVER and a CLIENT node - - (BOTH) on the same VAX. - - - -------------------------------------------------------------------------------- * Do you want to install EDCS II as a CLIENT node, SERVER node, BOTH, or just an INTERFACE [CLIENT]: server Installing an EDCS II SERVER node B-2 Sample Installation of EDCS II as a Server - - Next you are asked if you have registered your EDCS II software license. If you have successfully run the License Management Utility and registered and loaded your Product Authorization Key (PAK), answer YES. If you have not already done so, you can still complete the installation; however, you will not be able to run either the EDCS II software or the Installation Verification Procedure (IVP) until you run the License Management Utility. Product: EDCS-SERVER Producer: DEC Version: 2.1 Release Date: 01-JUL-1990 * Does this product have an authorization key registered and loaded? yes You are asked if you want to purge files created by previous installations of EDCS II. The installation keeps the database but removes all executable images if they are located on the same disks on which this installation would place them. * Do you want to purge files replaced by this installation [YES]? - - - The following questions must be answered regardless of the type of EDCS II - - node being installed (i.e., CLIENT, SERVER, BOTH). The answers supplied will - - be used to create the initialization file for either a CLIENT or SERVER. - - This file can be modified at any time after the installation. - - - You are next asked the names of the EDCS II client node and database that the server will interface with. At this time you can only specify one client You can later modify the server parameter file to specify other clients. The default for the client node is the same as the node on which you are installing other servers and databases. The default for the server node is the same as the node on which you are installing. * Enter the name of the EDCS II CLIENT node [IE0030]: ie0084 You are next asked the name of the EDCS II database (any name up to 15 characters). * Enter the name of the EDCS II database [DEMO]: example You are now asked for the number of the database (X.Y). This number is arbitrary. The first and second parts can be assigned to whatever the user wants. The default response is 1.1. * Enter the number of the EDCS II database [1.1]: Sample Installation of EDCS II as a Server B-3 You are next asked for the name of the disk that the Notification Manager process will use. This disk can be located on any system; the default is SYS$SYSDEVICE. You are also asked for the name of the disk where you want the EDCS II data base to reside and the name of the disk where you want the datafiles to reside. The default response to all of these questions is SYS$SYSDEVICE. * Enter the disk that will be used by the EDCS II Notification Manager [SYS$SYSDEVICE]: dua9 No such device as DUA9: Please reenter with a valid device You are next asked for the name of the disk that the Notification Manager process will use. This disk can be located on any system; the default is SYS$SYSDEVICE. You are also asked for the name of the disk where you want the EDCS II data base to reside and the name of the disk where you want the datafiles to reside. The default response to all of these questions is SYS$SYSDEVICE. * Enter the disk that will be used by the EDCS II Notification Manager [SYS$SYSDEVICE]: dua0 * What disk do you want to install the EDCS II database on [DUA0:]: * What disk do you want the EDCS II datafiles on [DUA0:]: You are asked if you want to create a database at this time. Digital recommends that you create the database at this time. This merely sets up the database structures for you but does not fill the database with any data. If you answer YES or press Return, you are asked if you want to use the default locations for the database area and snapshot files. The database area and snapshot files contain the actual data for the database files. They do not have to be on the same disk or in the same directory as the database root file, or as each other. You can achieve the best performance by spreading the files over the largest number of disks. If you answer NO to this question, you will be prompted for the device for each of these files. You can, however, use the default locations for the files if you wish. * Do you want to create an EDCS II database [YES]? no %EDCS-I-NODBFOUND, After installation, you must create database using EDCS$INQUIRE_DATABASE Utility. The device and database name you assign must match DUA0:[EDCS.EXAMPLE] B-4 Sample Installation of EDCS II as a Server Account EDCSNET with UIC [400,400] already exists Account EDCSMAIL with UIC [400,401] already exists %EDCS-I-NOMORQUES, You have answered all required questions. You will next see that savesets B, D (if installing DECwindows), E (if installing DECforms), F, G, and H (if you have selected COPY OPTIONS 1, 2, or 3 to copy the Reference Manual at your site) have been restored. Saveset A was restored earlier in the installation, and saveset C is not restored during this procedure because it corresponds to a client installation. %VMSINSTAL-I-RESTORE, Restoring product save set B ... %VMSINSTAL-I-RESTORE, Restoring product save set F ... %VMSINSTAL-I-RESTORE, Restoring product save set G ... %VMSINSTAL-I-RESTORE, Restoring product save set H ... The EDCS II installation creates several permanent directories and files. - - - This installation creates the directory structure for EDCS II. - - - %UAF-I-MDFYMSG, user record(s) updated %UAF-I-MDFYMSG, user record(s) updated Creating the EDCS II Server directory structure on disk DUA0:. Sample Installation of EDCS II as a Server B-5 %VMSINSTAL-I-SYSDIR, This product creates system disk directory DUA0:[EDCS.EXAMPLE]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DUA0:[EDCS.EXAMPLE.DATABASE]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DUA0:[EDCS.EXAMPLE.DATAFILE]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DUA0:[EDCS.EXAMPLE.SCRATCH]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DUA0:[EDCS.EXAMPLE.ARCHIVE]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DUA0:[EDCS.EXAMPLE.VERIFY]. Linking EDCS$MESSAGE (EDCS Message File)... Linking EDCS$RTL_COMMON (Common RTL)... Linking EDCS$RTL_DML (DML RTL)... Linking EDCS$RTL_SERVER (Server RTL)... Linking EDCS$RTL_UTIL (Server Utility RTL)... Linking EDCS$CMDPROC (Server Command Processor)... Linking EDCS$MAIL (Mail Notification)... Linking EDCS$NETDISP (Network Dispatcher)... Linking EDCS$UTIL (Server EDCS Utility)... Linking EDCS$CONVERT (V1.1 to V2.0 Conversion Utility)... Linking EDCS$SEED_DB (Database Seed Utility)... Linking EDCS$LOAD (EDCS Initializer)... Linking FT CONVERT... Linking EDCS$BATCHLOAD Utility... Linking EDCS$SHOWFILE ... Linking EDCS$DELETE_SECTIONS ... - - - An EDCS II database will not be created during this installation. - - If you currently have a database that you want to save, there will be a - - command file provided on the server disk([EDCS]EDCS$CONVERT.COM). This - - command file will convert your VAX EDCS V1.1 database to an EDCS II - - database - - - %EDCS-I-DELETE, Deleting EDCS global sections... %EDCS-I-DONE, Global Sections Deleted. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Installation of EDCS V2.1 completed at 14:27 VMSINSTAL procedure done at 14:27 B-6 Sample Installation of EDCS II as a Server Appendix C Sample Installation of EDCS II as a Client ________________________________________________________________ $ @SYS$UPDATE:VMSINSTAL EDCS021 MUA0: OPTIONS S VAX/VMS Software Product Installation Procedure V5.3-2 It is 15-MAR-1991 at 13:31. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? y The following products will be processed: EDCS V2.1 Beginning installation of EDCS V2.1 at 13:32 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. * Do you want to view preinstallation text guide [YES]? n - - - The Reference Manual is included with this kit in PostScript (.ps) and - - ASCII (.txt) formats. You can copy one or both to SYS$HELP and print it - - after the installation is completed. - Copy Options: 1. EDCS021_REFERENCE_MANUAL.PS (Requires additional 5,000 blocks) 2. EDCS021_REFERENCE_MANUAL.TXT (Requires additional 3,000 blocks) 3. Both 1 and 2 (Requires additional 8,000 blocks) 4. None of the above * Select option [4]: 2 * Do You want to continue with the installation [no]? y - - - Digital Equipment Corporation. 1991. All Rights Reserved - - - Sample Installation of EDCS II as a Client C-1 You are next asked if you want to install a client node, a server node, both, or just a user interface (DECwindows or DECforms). You are then notified of the different user interfaces that are available for use with EDCS. You are also notified which of the user interfaces you have the necessary software to install during this installation. The DCL command line interface will be installed, regardless of additional interfaces chosen at installation time. You are then asked if you want to install the DECwindows interface, which is a menu interface that runs on workstations running DECwindows. You are also asked if you want to install the DECforms interface, which is a menu interface that runs on character cell (VT style) terminals. Note that in order to install the DECwindows menu interface for EDCS II, the DECwindows software must already be installed. Likewise, in order to install the DECforms menu interface for EDCS II, the DECforms software must already be installed. -------------------------------------------------------------------------------- - - - EDCS II may be installed on your VAX as a CLIENT node only (CLIENT), or - - as a SERVER node only (SERVER), or as both a SERVER and a CLIENT node - - (BOTH) on the same VAX. - - - -------------------------------------------------------------------------------- * Do you want to install EDCS II as a CLIENT node, SERVER node, BOTH, or just an INTERFACE [CLIENT]: client - EDCS II has three different user interfaces - - 1. DCL command line (default interface) - 2. DECwindows Menu interface for DECwindows devices - 3. DECforms Menu interface for VT style devices - Of these you have the necessary software to install: - 1. DCL command line (default interface) - 2. DECwindows Menu interface for DECwindows devices - 3. DECforms Menu interface for VT style devices * Do you want to install the DECwindows Interface [NO]? no * Do you want to install the DECforms Interface [NO]? yes Installing an EDCS II CLIENT node C-2 Sample Installation of EDCS II as a Client - - Next you are asked if you have registered your EDCS II software license. If you have successfully run the License Management Utility and registered and loaded your Product Authorization Key (PAK), answer YES. If you have not already done so, you can still complete the installation; however, you will not be able to run either the EDCS II software or the Installation Verification Procedure (IVP) until you run the License Management Utility. Product: EDCS-CLIENT Producer: DEC Version: 2.1 Release Date: 01-JUL-1990 * Does this product have an authorization key registered and loaded? yes You are asked if you want to purge files created by previous installations of EDCS II. The installation keeps the database but removes all executable images if they are located on the same disks on which this installation would place them. * Do you want to purge files replaced by this installation [YES]? - - - The following questions must be answered regardless of the type of EDCS II - - node being installed (i.e., CLIENT, SERVER, BOTH). The answers supplied will - - be used to create the initialization file for either a CLIENT or SERVER. - - This file can be modified at any time after the installation. - - - You are next asked the names of the EDCS II server node and database that the client will access. At this time you can only specify one server and one database. You can later modify the client parameter file to specify other servers and databases. The default for the server node is the same as the node on which you are installing. * Enter the name of the EDCS II Server node [IE0086]: ie0084 You are next asked the name of the EDCS II database (any name up to 15 characters). * Enter the name of the EDCS II database [DEMO]: You are now asked for the number of the database (X.Y). This number is arbitrary. The first and second parts can be assigned to whatever the user wants. The default response is 1.1. You are also asked for the name of the disk that the client will use for its temporary scratch area, which does not take up much disk space. This disk can be located on any system; the default is SYS$SYSDEVICE. Sample Installation of EDCS II as a Client C-3 You are also asked for the name of the disk where you want the EDCS II database to reside. The default response is SYS$SYSDEVICE. * Enter the number of the EDCS II database [1.1]: * Enter the disk that will be used by the CLIENT [SYS$SYSDEVICE]: dua1 - - - You will now be asked for the name of disk that the EDCS II database - - will reside on. Since this disk can be on another system, its - - existence is not verified at this time. - - - * What disk does the EDCS II database reside on [SYS$SYSDEVICE]: dua3 %EDCS-I-NOMORQUES, You have answered all required questions. You will next see that savesets C, D (if installing DECwindows), E (if installing DECforms), F, G, and H (if you have selected COPY OPTIONS 1, 2, or 3 to copy the Reference Manual at your site) have been restored. Saveset A was restored earlier in the installation, and saveset B is not restored during this procedure because it corresponds to a server installation. %VMSINSTAL-I-RESTORE, Restoring product save set C ... %VMSINSTAL-I-RESTORE, Restoring product save set E ... %VMSINSTAL-I-RESTORE, Restoring product save set F ... %VMSINSTAL-I-RESTORE, Restoring product save set G ... %VMSINSTAL-I-RESTORE, Restoring product save set H ... The EDCS II installation creates several permanent directories and files. - - - This installation creates the directory structure for EDCS II. - - - Creating the EDCS II Client directory structure on disk DUA1:. Linking EDCS$MESSAGE (EDCS Message File)... Linking EDCS$RTL_COMMON (Common RTL)... Linking EDCS$RTL_CLIENT (Client RTL)... Linking EDCS$RTL_UTIL (Client Utility RTL)... Linking EDCS (User interface - Command Line)... Linking EDCS$FTM (File Transfer Manager)... Linking EDCS$CTRL (Client Controller)... Linking EDCS$UTIL (Client EDCS Utility)... Linking EDCS$LOAD (EDCS Initializer)... Linking EDCS$DELETE_SECTIONS ... Linking EDCS (User interface - DECforms)... Linking Forms Label Convert... Linking Shareable Forms Files... C-4 Sample Installation of EDCS II as a Client %EDCS-I-DELETE, Deleting EDCS global sections... %EDCS-I-DONE, Global Sections Deleted. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Installation of EDCS V2.1 completed at 14:22 VMSINSTAL procedure done at 14:52 Sample Installation of EDCS II as a Client C-5 Appendix D Solving Installation Errors ________________________________________________________________ This appendix describes installation error messages and contains suggestions for handling problems. If your intervention in correcting errors is not successful, or if the message so specifies, you should submit a Software Performance Report (SPR) to Digital Equipment Corporation. Please include as much detail as possible with the SPR, including the following: o A complete description of the problem, including the software version number. o The EDCS II log files: SYS$ERRORLOG:EDCS$CLIENT.LOG and SYS$ERRORLOG:EDCS$SERVER.LOG. o The SYS$MANAGER:EDCS$PARAMETER_CLIENT.INI and SYS$MANAGER:EDCS$PARAMETER_ SERVER.INI parameter files. o If changes were made to the VAX Rdb/VMS database, please submit a list of the changes and a listing of the rela- tions/views, indexes, and fields. Also, submit a display dump of the VAX Rdb/VMS header. o The type and configuration of the environment. o Any relevant listings of command files, linker maps, or data files. If you find an error in the EDCS II documentation, fill out and submit the Reader's Comments form at the back of the document in which the error was found. Include the section and page number of the error. Solving Installation Errors D-1 The following are common VMSINSTAL errors that you can cor- rect: ERROR This kit requires VMS Version 5.3-2 or subsequent version of VMS. SOLUTION Install VMS Version 5.3-2 before installing EDCS II. WARNING You do not have VAX Rdb/VMS Version 3.1B or later installed on your system. SOLUTION Install VAX Rdb/VMS Version 3.1B or later. ERROR System disk does not contain enough free space to install EDCS II. SOLUTION Make sure you have sufficient disk space on the system disk. Consult Section 1.1.4 for more infor- mation. ERROR Insufficient global pages/sections SOLUTION See Chapter 1 for instructions on how to increase global pages and sections. D-2 Solving Installation Errors Index ________________________________________________________________ A___________________________ Client node, 1-1 Account quotas installing, 1-1 modifying, 1-16 Client parameter files Authorize utility editing, 3-4 checking process quotas CMKRNL privilege, 1-4 with, 1-16 Concealed logicals using to create SYSTEM See also process-rooted account, 1-4 logicals, 1-21 AUTOGEN Concurrent users changing parameters with, memory recommendation, 1-7 1-12 Configuration, 1-1 Conversion B database, 1-19 ____________________________ Corruption Backing up system disk, 1-18 system disk, 1-6 BALSETCNT parameter, 1-8 BYPASS privilege, 1-4 D___________________________ C Database ____________________________ area and snapshot files, CHANNELCNT parameter, 1-8, 1-22, 1-23 1-9 conversion before Client installation, 1-19 sample installation, C-1 creating during installa- to C-5 tion, 1-22, 1-23 Client and server number, 1-21, 1-22, 1-24 memory required to operate requirements before , 1-7 installation, 1-19 Index-1 Database (Cont.) EDCS II Version 2.0 (Cont.) verifying and repairing shutting down before after VAX EDCS installation, 1-17 conversion, 3-5 EDCS II Version 2.1 DECforms incompatibility with memory required to operate Version 2.0, 1-1 , 1-7 shutting down before sample installation, A-1 installation, 1-18 to A-18 EDCSMAIL account, 1-22, 1-23 DECforms interface EDCSNET account, 1-22, 1-23 installing, 1-1 ENQLM process quota, 1-16 version required, 1-3 Error messages, D-1 to D-2 DECnet Errors version required, 1-3 recovering from, 2-3 DECnet network, 1-1 solving installation, D-1 DECwindows EXQUOTA privilege, 1-4 memory required to operate F , 1-7 ____________________________ sample installation, A-1 FILLM process quota, 1-16 to A-18 DECwindows interface G___________________________ installing, 1-1 GBLPAGES parameter, 1-8 version required, 1-3 GBLPAGFIL parameter, 1-8 Definitions GBLSECTIONS parameter, 1-8 multiple in logicals, 1-21 Global pages Device name, 1-21 See also GBLPAGES, 1-11 Disk logical names Global sections length, 1-21 deleting before installa- Disk space tion, 1-18 error showing insufficient See also GBLSECTIONS, 1-11 , 2-3 required for installation, I 1-4 ____________________________ required to operate EDCS INSTALL (VMS Install II, 1-7 utility), 1-11 Installation E___________________________ aborting, 2-3 EDCS II checklist for, 1-19 definition, 1-1 database requirements, EDCS II Version 2.0 1-19 Index-2 Installation (Cont.) M___________________________ disk space required for, Maximum Links 1-4 calculation, 1-12, 1-15 error recovery, 2-3 MAXPROCCNT parameter, 1-8 privileges required for, Memory 1-4 required for installation, procedure, 2-1 to 2-2 1-4 required software for, 1-3 required to operate EDCS sample of both server and II, 1-7 client, A-1 to A-18 Memory recommendation sample of client, C-1 to concurrent users, 1-7 C-5 Messages, D-2 sample of server, B-1 to Multiple database B-6 configuration, 1-1 system disk backup, 1-18 Multiple definitions time required for, 1-4 of logicals, 1-21 Installation Verification Multiple server nodes, 1-1 Procedure (IVP) N___________________________ example, 3-2 Network links running after installation calculation, 1-15 , 3-1 Network parameter values time required for, 1-4 how to change, 1-15 IVP how to check, 1-13 See Installation Number of users Verification Procedure memory recommendation, 1-7 IVP privileges, 3-1 P___________________________ L___________________________ PAK License See Product Authorization error showing lack of, 2-4 Key (PAK) registering software, 1-19 Parameter files License Management Utility editing, 3-4 registering your license, Parameter values 1-19 how to calculate, 1-11 Links how to change, 1-12 calculation, 1-15 how to check, 1-10 LMF (License Management network, 1-12 Facility), 1-19 required for installation, LOCKIDTBL parameter, 1-9 1-8 Logicals PIOPAGES parameter, 1-9 concealed, 1-21 Index-3 Previous versions Server and client shutting down, 1-17 sample installation, A-1 Privileges to A-18 required for installation, Server node, 1-1 1-4 installing, 1-1 required to run IVP, 3-1 Server parameter files Process Quotas editing, 3-4 minimum required, 1-16 SETPRV privilege, 1-4 Process-rooted logicals Shutting down EDCS II caution about use in Version 2.0 naming, 1-21 before installation, 1-17 PROCSECTCNT parameter, 1-8 Shutting down EDCS II Product Authorization Key, Version 2.1 1-19 before installation, 1-18 Product Authorization Key Shutting down VAX EDCS (PAK) before installation, 1-17 obtaining license Software information, 1-19 error showing incorrect version, 2-3 Q___________________________ required to install, 1-3 Quotas Software license error showing insufficient registering, 1-19 Software Performance Report , 2-3 (SPR), D-1 process, 1-16 Start EDCS II privileges, R 3-1 ____________________________ Starting up EDCS II, 3-5 Release notes SYSGEN parameters reading and printing, 2-2 setting, 1-8 Repair Element utility SYSGEN utility running after VAX EDCS changing parameters with, conversion, 3-5 1-12 Required software checking parameters with, to install, 1-3 1-10 Run-time license SYSLCK privilege, 1-4 VAX Rdb/VMS, 1-3 SYSPRV privilege, 1-4 S SYSTEM account, 1-4 ____________________________ System disk Server backing up, 1-18 sample installation, B-1 System disk corruption, 1-6 to B-6 System parameters Index-4 System parameters (Cont.) Verify Files utility (Cont.) error showing insufficient running after VAX EDCS , 2-3 conversion, 3-5 System parameter values VMS how to calculate, 1-11 version required, 1-3 how to change, 1-12 VMS HELP library how to check, 1-10 error showing in use, 2-3 required for installation, VMSINSTAL 1-8 notification of require- ments, 1-17 T___________________________ safety mode, 1-6 Time VMS Install utility required for installation, (INSTALL), 1-11 1-4 VMSINSTAL procedure, 1-4 U W___________________________ ____________________________ WORLD privilege, 1-4 UIC, 1-4, 1-22, 1-23 WSMAX parameter, 1-8, 1-9 Upgrading to Version 2.1 caution about compatibil- ity, 1-1 User account quotas, 1-16 User interface, 1-1 Users concurrent, 1-7 V___________________________ VAXcluster running EDCS II on, 3-4 VAX EDCS shutting down before installation, 1-17 VAX EDCS database special requirements, 1-19 VAX Rdb/VMS version required, 1-3 VAX Rdb/VMS database special requirements, 1-19 Verify Element utility running after VAX EDCS conversion, 3-5 Verify Files utility Index-5