EDCS_II_______________________________________ Installation Guide Part Number: AA-EY16H-TE January 1997 This guide contains the installation procedure for EDCS II (Electronic Data Control System II). Revision/Update Information: This guide super- sedes the EDCS II Installation Guide, Version 2.4. Operating System and Version: OpenVMS VAX Version 6.1 or higher, OpenVMS Alpha Version 6.1 or higher, and MS-DOS Version 6.0 Software Version: EDCS II Version 2.4A Digital Equipment Corporation Maynard, Massachusetts The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. 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 1997. All rights reserved. Printed in U.S.A. The following are trademarks of Digital Equipment Corporation: DECnet, EDCS II, PATHWORKS, VAX, VAX DOCUMENT, OpenVMS, VT, and the DIGITAL logo. The following are third-party trademarks: MS-DOS is a trademark of Microsoft Inc.; PostScript is a trademark of Adobe Systems, Inc.; Oracle Rdb is a trademark of Oracle Corporation. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company, Limited. All other trademarks and registered trademarks are the property of their respective holders. This document is available on CD-ROM. This document was prepared using VAX DOCUMENT Version 2.1. ________________________________________________________________ Contents Preface.................................................. vii New and Changed Features................................. xiii 1 Preparing for Installation 1.1 Installation Procedure Requirements.......... 1-2 1.1.1 Software Required........................ 1-2 1.1.2 Time Required............................ 1-3 1.1.3 Privileges Required...................... 1-3 1.1.4 Disk Space Required to Install EDCS II... 1-4 1.1.5 Disk Space Required to Operate EDCS II... 1-5 1.2 System Parameter Values...................... 1-5 1.2.1 Minimum System Parameter Values.......... 1-6 1.2.2 System Parameter Recommendations for Larger Systems with Heavy Usage.......... 1-6 1.2.3 Checking System Parameter Values......... 1-7 1.2.4 Changing System Parameter Values......... 1-8 1.3 Process Quotas............................... 1-8 1.3.1 VMSINSTAL Notification of Requirements... 1-9 1.4 Shutting Down Previous EDCS Versions......... 1-10 1.5 Backing Up Your System Disk.................. 1-11 1.6 Registering Your Software License............ 1-11 1.7 Before Installing EDCS II.................... 1-12 1.7.1 Information Needed for All Installations............................ 1-13 1.7.2 Information Needed for Installing EDCS II as Both Client and Server................ 1-15 1.7.3 Information Needed for Installing EDCS II as a Server Only......................... 1-16 iii 1.7.4 Information Needed for Installing EDCS II as a Client Only......................... 1-17 2 Installing the MS-DOS Client 2.1 Before Installing the MS-DOS Client.......... 2-1 2.2 Disk Space Required for the MS-DOS Client.... 2-1 2.3 Installing the MS-DOS Client................. 2-2 2.4 Aborting the Installation.................... 2-2 3 Installing the OpenVMS Client and Server 3.1 Installing the OpenVMS Client and Server..... 3-1 3.1.1 Reading the Release Notes................ 3-2 3.1.2 Aborting the OpenVMS Installation........ 3-2 3.1.3 Recovering from OpenVMS Errors........... 3-2 3.2 After the OpenVMS Installation............... 3-3 3.2.1 Running the IVP After the Installation... 3-3 3.2.2 Editing Parameter Files.................. 3-5 3.2.3 Starting Up EDCS II...................... 3-6 A Sample Installation for an OpenVMS Server and Client B Sample Installation for an OpenVMS Server C Sample Installation for an OpenVMS Client D Sample Installation of a MS-DOS Client E Files and Logical Names Added or Modified by the Installation E.1 Files Added.................................. E-1 E.2 Files Deleted................................ E-3 E.3 Files Modified............................... E-3 E.4 Files Accessed............................... E-3 iv Tables 1 Document Conventions..................... x 1-1 Software Requirements for OpenVMS Installation ............................ 1-2 1-2 Disk Space Required to Install EDCS II... 1-4 1-3 Minimum Required System Parameters for EDCSII................................... 1-6 1-4 Recommended System Parameters for Larger Systems with Heavy Usage................. 1-7 1-5 Minimum Process Quotas for EDCS II....... 1-8 v ________________________________________________________________ Preface This guide describes how to install EDCS II (Electronic Data Control System II) Version 2.4A. EDCS II is a data management system designed to control files electronically in a distributed environment. Intended Audience This guide is for system managers or anyone responsible for installing the EDCS II software. Document Structure This document consists of three chapters and five appendixes: o Chapter 1 describes how to prepare for EDCS II installations. o Chapter 2 describes the installation procedure for a MS-DOS client. o Chapter 3 describes the installation procedure, postinstallation considerations, and procedures for the OpenVMS client and server. o Appendix A shows a sample installation of EDCS II as an OpenVMS client and server. o Appendix B shows a sample installation of EDCS II as an OpenVMS server. o Appendix C shows a sample installation of EDCS II as an OpenVMS client. o Appendix D shows a sample installation of EDCS II as a MS-DOS client. vii o Appendix E contains a listing of all the files and logical names that have been added or modified by the installation. Associated Documents This guide is part of the EDCS II documentation set, which contains six other documents: o EDCS II Administrator's Guide This guide describes how to configure, run, and maintain EDCS II. Because the EDCS II server is only OpenVMS, this guide mainly pertains to OpenVMS administrators. However, sections of this guide are for MS-DOS administrators. o EDCS II Quick Reference Guide The guide describes how to enter EDCS II commands and summarizes commands, parameters, qualifiers, and restrictions on OpenVMS and MS-DOS systems. o EDCS II Programmer's Guide This guide discusses how to use the EDCS II callable interface on OpenVMS and MS-DOS systems, and contains an appendix of diagnostic messages. It also explains how to create customized queries on OpenVMS systems regarding data stored in the Oracle Rdb[TM] database. This guide is for programmers and system developers. o EDCS II Reference Guide This document describes each EDCS II command for OpenVMS systems in alphabetical order. It also discusses command concepts and syntax. This document is for all EDCS II OpenVMS users. For MS-DOS users, online help and the EDCS II Quick Reference Guide provide information about EDCS II commands. o EDCS II Release Notes (online only) The release notes describe new and changed features and known restrictions in EDCS II Version 2.4A. The release notes are for all users. o EDCS II User's Guide viii 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 DECwindows and command line interfaces. The guide is for new users of the EDCS II system. The guide specifies OpenVMS command syntax only; however, any user of EDCS II will find the guide useful. The EDCS II documentation set (excluding the EDCS II Release Notes) is available on CD-ROM for users who have DECwindows software. Related Documents You may want to refer to the following documentation for more information: o Oracle Rdb Installation and Configuration Guide o UCX Installation Guide o OpenVMS System Management Volume 2 Maintenance o OpenVMS System Management Volume 1A Setup o OpenVMS System Management Volume 3 Security o OpenVMS System Management Volume 1B Setup o OpenVMS System Management Volume 1A Setup ix Document Conventions The following conventions are used in this guide: Table_1_Document_Conventions______________________________ 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 Ctrl/x indicates that you hold down the Ctrl key while you press another key or mouse button (indicated here by 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. lowercase text A lowercase italic x indicates the generic use of a letter. For example, xxx indicates any combination of alphabetic characters. UPPERCASE Uppercase letters in a command line indicate the keywords that you must enter. You can enter them in either uppercase or lowercase. You can use the first 3 characters to abbreviate command keywords, or you can use the minimum unique abbreviation. (continued on next page) x Table_1_(Cont.)_Document_Conventions______________________ Convention_______Meaning__________________________________ italic type Italic type emphasizes important information, indicates variable, and indicates complete titles of manuals. [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.________________________ xi Note Your comments and suggestions help us to improve the quality of our publications. Please send your comments to the following electronic mail address: comments@ilo.dec.com Thank you for your assistance. xii ________________________________________________________________ New and Changed Features EDCS II Version 2.4A has several changes for the installer. The following is a list of changes: o Version 2.4A now supports MS-DOS clients. This guide provides new information about how to install a MS-DOS client. o The OpenVMS server has new layered product and disk space requirements for running a MS-DOS client. o Version 2.4A has new licenses. xiii 1 ________________________________________________________________ Preparing for Installation This chapter discusses the preparations and requirements necessary for installing the EDCS II software. EDCS II is a data management system that controls files in a distributed environment. The EDCS II database is connected 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. EDCS II Version 2.4A has added new client installations for the MS-DOS (PC) platform. The MS-DOS client installa- tions attach directly to the server. They do not use the central process called the EDCS-ROUTER to access EDCS II as in Version 2.2. The client node contains the user interface. One or more client nodes can connect to the server node using UCX (TCP /IP). UCX must run on the OpenVMS system that contains the EDCS Server for any client access. You can have one node function as both a server and a client or you can have separate server nodes and client nodes. The installation procedure asks if you want to install: o An OpenVMS server node only o An OpenVMS client node only o Both an OpenVMS server and client The installation procedure varies depending on your answer. Preparing for Installation 1-1 This guide has appendixes that contain sample logs of the following types of installations: o OpenVMS client and server (Appendix A) o OpenVMS server only (Appendix B) o OpenVMS client only (Appendix C) o MS-DOS client on a PC (Appendix D) 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 that your kit is damaged or parts are missing, contact your Digital representative. For additional information about EDCS II and config- uring your system, see the EDCS II Administrator's Guide 1.1 Installation Procedure Requirements The following sections discuss various requirements for installing EDCS II. 1.1.1 Software Required Table 1-1 shows the software requirements for installing EDCS II Version 2.4A. Table_1-1_Software_Requirements_for_OpenVMS_Installation__ OpenVMS_Installation__Software_Requirements_______________ OpenVMS client or OpenVMS VAX Version 6.1 or higher or server OpenVMS Alpha Version 6.1 or higher. Oracle Rdb Version 6.1. Please note that only a run-time license for Oracle Rdb is required. UCX Version 3.3 (must be installed on the OpenVMS node on which the EDCS Server is installed.) (continued on next page) 1-2 Preparing for Installation Table 1-1 (Cont.) Software Requirements for OpenVMS __________________Installation____________________________ OpenVMS_Installation__Software_Requirements_______________ PATHWORKS Version 5.0A (installed on either OpenVMS EDCS server.) __________________________________________________________ PC_Client_InstallationSoftware_Requirements_______________ MS-DOS client MS-DOS Version 6.2 ______________________PATHWORKS_FOR_DOS_Version_5.0A______ 1.1.2 Time Required The time required to install EDCS II varies depending on the processor type, the disk space available, and whether you are installing a client, a server, or both. The average time required for an EDCS II installation is half hour, but this time varies from 15 minutes to 45 minutes. 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: CMKRNL EXQUOTA SYSLCK SYSPRV WORLD EDCS II uses VMSINSTAL, the standard VMS installation procedure for installation. Note that VMSINSTAL turns off BYPASS privilege at the start of the installation. See the OpenVMS 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. Preparing for Installation 1-3 1.1.4 Disk Space Required to Install EDCS II Table 1-2 can help you determine if you have enough memory for your specific installation. Table_1-2_Disk_Space_Required_to_Install_EDCS_II__________ Blocks - Peak Type_of_Installation__Utilization______AWD_[1]_-_Net______ OpenVMS client 13,000 3,800[2] OpenVMS server 30,000 8,000[1] OpenVMS client & 36,000 36,000[1] Server [1]If_database_is_installed_on_system_disk,_add_10,800____ blocks to this number. [2]If client disk is installed on system disk, add 700 blocks to this number. __________________________________________________________ In addition to the disk space shown in Table 1-2, if you plan to print the EDCS II Reference Manual in PostScript format at your site, add 3,600 blocks of required disk space. If you plan to print the EDCS II Reference Manual in text format, add 1,700 blocks of required disk space. See Associated Documents 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 disk space available on your system disk and you have another disk (for example, USER$DISK1) available on your system, you can invoke VMSINSTAL in Alternate Working Directory (AWD) mode. For example: $ @SYS$UPDATE:VMSINSTAL EDCS024 MUA0: OPTIONS AWD=USER$DISK1: If you have a minimum of 8,500 blocks available on your system disk and a minimum of 36,000 blocks available on your USER$DISK1, you can successfully install an EDCS II client and server. 1-4 Preparing for Installation 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. 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 reduces 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.1.5 Disk Space Required to Operate EDCS II After an OpenVMS client installation, the disk space required to operate EDCS II is 6 megabytes. This size is approximate. The actual size may vary depending on your system environment, configuration, and software options selected. For better performance, Digital recommends that you do not install your database on your system disk. ________________________Note ________________________ For 20 or more concurrent users connected to the server, at least 64 megabytes is recommended. For 10 or more concurrent users on any one client, a minimum of 32 megabytes is recommended. _____________________________________________________ 1.2 System Parameter Values The following sections describe: o Minimum system parameter values required for EDCS II o System parameters recommended for larger systems with heavy usage o How to check system parameter values Preparing for Installation 1-5 o How to calculate the GBLPAGES and GBLSECTIONS system parameter values o How to change system parameter values 1.2.1 Minimum System Parameter Values Table 1-3 lists the minimum required system parameter values for the installation. Depending on the programs and applications running at your site, you may need higher values for some settings. Table_1-3_Minimum_Required_System_Parameters_for_EDCSII___ System_Parameter______Client______Server______Both________ BALSETCNT[1] n+2 n+4 n+6 CTLPAGES 50 50 50 MAXPROCESSCNT[1] n+2 n+4 n+6 PROCSECTCNT N/A 48 48 WSMAX 3,000 8,000 8,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. __________________________________________________________ 1.2.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 64 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. 1-6 Preparing for Installation See the EDCS II Administrator's Guide for more information about the 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 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]Digital recommends these values 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 about calculating these settings. 1.2.3 Checking System Parameter Values You can check the values for the system parameters by invoking the SYSGEN Utility. To invoke the SYSGEN Utility, enter 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. Preparing for Installation 1-7 You can also directly check the value of the PROCSECTCNT parameter using the SYSGEN Utility. To change the current values of system parameters, see Section 1.2.4. After you have finished checking the parameters with the SHOW command, enter the EXIT command at the SYSGEN> prompt to return to the DCL level. For more information about the SYSGEN Utility, see the OpenVMS System Management Volume 1B Setup manual. 1.2.4 Changing System Parameter Values You can use either the SYSGEN Utility or the AUTOGEN command procedure to change system parameters. However, the option that you use depends on how the system administrator generally handles system settings at your site. Using the wrong method could adversely affect your system setup. For more information about the SYSGEN Utility, see the OpenVMS System Management Volume 1B Setup manual. For more information about the AUTOGEN command procedure, see the OpenVMS System Management Volume 1A Setup manual. 1.3 Process Quotas The account you use to install EDCS II must have suffi- cient quotas to enable you to perform the installation. Table 1-5 summarizes the process quotas required to perform the installation. Table_1-5_Minimum_Process_Quotas_for_EDCS_II______________ Minimum_Quota____Value____________________________________ ENQLM 2000 FILLM____________50_______________________________________ The SYSUAF> .DAT file stores user account quotas. Use the OpenVMS Authorize Utility to verify and change user account quotas. Set your directory to SYS$SYSTEM, then run the Authorize Utility: 1-8 Preparing for Installation $ 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 OpenVMS 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. For more information about modifying account quotas, see the OpenVMS System Management Volume 3 Security manual. 1.3.1 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 installa- tion 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 continue 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. Preparing for Installation 1-9 See the OpenVMS Installation Guide for more information about the VMSINSTAL procedure. 1.4 Shutting Down Previous EDCS Versions To shut down previous EDCS versions, log in to the SYSTEM account. If you have EDCS II Version 2.1 or Version 2.2 installed and running, shut down EDCS II. To do this, enter the following command at the system prompt: $ @SYS$STARTUP:EDCS$SHUTDOWN 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 If entered on a server, this command shuts down EDCS II on that server. If entered on a client, the command shuts down EDCS II 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. 1-10 Preparing for Installation 1.5 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 OpenVMS System Management Volume 2 Maintenance manual. 1.6 Registering Your Software License Before you install EDCS II, register your EDCS II licenses. 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 licenses - Product Authorization Keys (PAKs) which are shipped with your software. The PAK contains the LMF Product Name. Refer to the OpenVMS License Management Utility Manual for more information about PAKs. During the installation, you are asked if you have registered and loaded the PAKs. 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. There are two LMF PAKs associated with EDCS II Version 2.4A: o EDCS II SERVER Use this license to run an EDCS server on an OpenVMS node. The LMF product name is EDCS-SERVER. It supports unlimited use. EDCS II checks for server license only during the EDCS startup procedure. o EDCS II CLIENT Preparing for Installation 1-11 Use this license to run an OpenVMS client on an OpenVMS node. This license has the following types: - Capacity License (the LMF product name is EDCS- CLIENT) This license allows an unlimited number of users to use the client. - Concurrent Use License (the LMF product name is EDCS- CLIENT-USER) This license allows a limited number of users to use the client. - Personal License (the LMF product name is EDCS- CLIENT) This license allows only specified users to use the client. It is a restricted capacity license that allows system managers or privileged users to attach a list of names to the product license. This license is supported only in LMF Version 1.1, which is bundled with OpenVMS Version 5.5. Unlike previous versions of EDCS II, EDCS II Version 2.4A does not check the client license during the EDCS startup procedure. Instead, the license is checked at run time during EDCS image activation. 1.7 Before Installing EDCS II The following sections provide 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 1-12 Preparing for Installation 1.7.1 Information Needed for All Installations Check the following list before you start to install EDCS II. Ensure that: 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. The installer's account, or any account used for the installation, should not have /FLAG=LOCKPWD. If this setting exists, the installation will fail during password generation for the OpenVMS accounts. To check your account settings, enter: $ RUN AUTHORIZE UAF> SHOW (account) o You have OpenVMS VAX Version 6.1 or higher or OpenVMS Alpha Version 6.2 or higher installed on the target system. o You have UCX Version 3.3 installed and running. o You have PATHWORKS for OpenVMS (refer to Table 1-1) installed, if you plan to install the MS-DOS client. o You have Oracle Rdb Version 6.0 or higher installed on the target system, if you are installing both a server and a client or only a server. To check that Oracle Rdb is up and running, invoke RDO; then enter SHOW VERSION. $ RUN SYS$SYSTEM:RDO RDO> SHOW VERSION Current version of RDO is: Oracle Rdb 6.1 RDO> EXIT o You have made a backup copy of your system disk and any previously installed data files before you install EDCS II. o Your system has enough free blocks on the system disk. See Table 1-2 for more information about disk space requirements. If you are creating a new database, make sure that there is enough space on the disk for the database files. Preparing for Installation 1-13 o Your system parameter value settings are adequate for your installation. See Table 1-3 for more information. o Your network parameter value setting are adequate for your installation. o The ENQLM limit is set to at least 2000 and the FILLM limit is set to at least 50. o You know the name of the device on which the distribu- tion kit will be mounted, in other words, the physical location of the EDCS II savesets EDCSAV024.A through EDCSAV024.D. 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 multiple definitions. Do not use process-rooted (concealed) logical names in the naming of devices, directories, or processes. Process-rooted 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. During installation, when prompted for the database name, make sure there is no system logical defined on the system with the same name. For example, on a system where DEMO is the default database name and a logical that defines a system disk DUA1 is also named DEMO, the following error message is displayed when the user tries to log in to EDCS after installation: %EDCS-E-NODATABASE, Database DUA1:does not exist o During installation, you will be asked for your EDCS account password. During installation, the system generates a password for the following EDCS accounts: - Administrator - Operator During installation, you will be prompted for the EDCS account password. 1-14 Preparing for Installation 1.7.2 Information Needed for Installing EDCS II as Both Client and Server Ensure that you have assembled the following information before you begin the installation. You will be asked: o Whether or not you are installing a client, a server, or both client and server. o Whether or not you have registered and loaded the applicable PAKs for client, and/or server. o Whether or not you want to purge files replaced by this installation. o The name of the EDCS II database. 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 The name of the disk that the client will use for its temporary scratch area. o Whether or not you want to create a new database. o If you choose to create a database during the installation, 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 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. You can, however, use the default locations for the files if you wish. o The password for the Administrator and the Operator EDCS accounts. Preparing for Installation 1-15 1.7.3 Information Needed for Installing EDCS II as a Server Only Ensure that you have assembled the following information before you begin the installation. You will be asked: o Whether or not you are installing a client, a server, or both a client and a server. o Whether or not you have registered and loaded the PAK for the server. o Whether or not you want to purge files replaced by this installation. o The name of the client node. o The name of the EDCS II database. 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 installation, 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 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. You can, however, use the default locations for the files if you wish. o The password for the Administrator and the Operator EDCS accounts. 1-16 Preparing for Installation 1.7.4 Information Needed for Installing EDCS II as a Client Only Ensure that you have assembled the following information before you begin the installation. You will be asked: o Whether or not you are installing a client, a server, or both a client and a server. o Whether or not you have registered and loaded the applicable PAK for the client. o Whether or not you want to purge files replaced by this installation. o The name of the EDCS II database. o The name of the disk that the client will use. o The name of the disk where the EDCS II database will reside. Preparing for Installation 1-17 2 ________________________________________________________________ Installing the MS-DOS Client This chapter describes how to install the MS-DOS client. It also describes how to establish the communication link between the MS-DOS client and the OpenVMS server. The time required to install the MS-DOS client is approximately 1 minute. A sample installation log is shown in Appendix D. 2.1 Before Installing the MS-DOS Client For a list of software requirements, refer to Section 1.1.1. Before you start the installation, do the following: o Modify your AUTOEXEC.BAT file to include the following environment variables: - EDCSHOST=VMS_node_name o Modify your environment variable PATH to include the \EDCS directory path. 2.2 Disk Space Required for the MS-DOS Client To successfully install the MS-DOS client, you need approximately 1.26 megabytes of free disk space available on your PC system. To run the MS-DOS client, you need 4 megabytes of memory. Installing the MS-DOS Client 2-1 2.3 Installing the MS-DOS Client The MS-DOS client uses a batch file called LOADEDCS.BAT to load the following files into appropriate directories on your PC hard disk (drive C): EDCS.LIB EDCSDEFS.H EDCSMSG.H EDCS.EXE EDCSHELP.HLB CLIENT.INI Note that the installation does not compile or link any modules. During an initial installation, the batch file creates directories and copies files into these directories. After the initial installation, the files are updated. If you are installing from a 3.5-inch floppy disk that contains 2.0 megabytes of data, do the following: 1. Insert floppy disk 1 in drive A. 2. At the MS-DOS prompt, enter the following command: A:\INSTALL d where d is the letter that identifies the disk drive to install EDCS on. 2.4 Aborting the Installation To abort the installation, press Ctrl/E at the continua- tion prompt. If you press Ctrl/E while files are copying, delete the files copied on your system by the installation before restarting the installation. 2-2 Installing the MS-DOS Client 3 ________________________________________________________________ Installing the OpenVMS Client and Server This chapter describes how to install the OpenVMS client and server. Sample installation logs are contained in the following appendixes. o Appendix A - Installation of OpenVMS client and server o Appendix B - Installation of OpenVMS server only o Appendix C - Installation of OpenVMS client only 3.1 Installing the OpenVMS Client and Server Log in to the SYSTEM account. The following procedure installs EDCS II. The defaults to all questions are in brackets []. Press Return to accept the default. $ @SYS$UPDATE:VMSINSTAL EDCS024 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 3.1.1. The first part of the installation procedure describes preliminary requirements and considerations. Chapter 1 describes these preliminary requirements in more detail. See Appendix A for a sample installation of both OpenVMS client and server. Installing the OpenVMS Client and Server 3-1 3.1.1 Reading the 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 special installation considerations or 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 installation 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:EDCS024.RELEASE_NOTES. 3.1.2 Aborting the OpenVMS 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. 3.1.3 Recovering from OpenVMS Errors 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.2.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. 3-2 Installing the OpenVMS Client and Server Errors can occur during the installation if any of the following conditions exist: o The prerequisite software version is incorrect. o Quotas necessary for successful installation are insufficient. o System parameter values for successful installation are insufficient. o Disk space is insufficient. o The OpenVMS help library is currently in use. o The product is not properly licensed. If you receive a message about any of the preceding conditions, take action to resolve the problem. It is possible you will need to change a system parameter or increase an authorized quota value. See Section 1.2 for more information about parameters or Section 1.3 for more information about quota values. Log out of OpenVMS, then log back in and perform the installation procedure again. This helps to ensure the correct environment for VMSINSTAL. 3.2 After the OpenVMS Installation The following sections describe procedures you can perform after EDCS II is installed. 3.2.1 Running the IVP After the Installation The Installation Verification Procedure (IVP) verifies that software has been installed correctly on the designated 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 privileges required to start EDCS II are also required to run the IVP. These privileges are: CMKRNL SYSNAM Installing the OpenVMS Client and Server 3-3 DETACH SETPRV TMPMBX WORLD OPER EXQUOTA NETMBX PRMGBL SYSGBL SYSPRV SYSLCK See the EDCS II Administrator's Guide for more information about privileges. You can run the EDCS II IVP during or after the in- stallation. 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 installation, you must do one of the following: 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. Section 1.2 provides this parameter information. Then use one of the following commands: - For both the client and server, enter the following command: $ @SYS$TEST:EDCS$IVP_BOTH.COM - For the server only, enter the following command: $ @SYS$TEST:EDCS$IVP_SERVER.COM - For the client only, enter the following command: $ @SYS$TEST:EDCS$IVP_CLIENT.COM 3-4 Installing the OpenVMS Client and Server The IVP runs tests and displays success and error messages to indicate whether the installation was successful. The following log shows a successful IVP run on an OpenVMS client and server system with the EDCS-ROUTER installed. To be supplied After you run the IVP, restart EDCS II. See Section 3.2.3 for more information. 3.2.2 Editing Parameter Files When you start up EDCS II, it reads parameter files that contain parameters that you can tune to fit the needs of your site. 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. 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 the EDCS II Administrator's Guide for more information about editing the parameter files. Installing the OpenVMS Client and Server 3-5 3.2.3 Starting Up EDCS II You can set things up so that EDCS II starts up automat- ically whenever OpenVMS starts up. You can also start up EDCS II individually without having to start up OpenVMS, if OpenVMS is already running. The EDCS II Administrator's Guide describes how to accomplish both forms of EDCS II startup. 3-6 Installing the OpenVMS Client and Server A ________________________________________________________________ Sample Installation for an OpenVMS Server and Client This appendix shows an example of an OpenVMS server and client installation. $ @vmsinstal edcsvv024 $1$DKB100:[EDCS_DEV] options s OpenVMS VAX Software Product Installation Procedure V6.1 It is 25-JUL-1995 at 20:14. 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: EDCSVV V2.4A Beginning installation of EDCSVV V2.4A at 20:15 (Waiting for demon to record initial state... ...done) %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. Installing EDCS server for OpenVMS VAX/Alpha. Copyright Digital Equipment Corporation 1993,1994, 1995. All rights reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. Sample Installation for an OpenVMS Server and Client A-1 This installation supports ALPHA/VMS and VAX/VMS EDCSV2.4A servers and ALPHA/VMS, VAX/VMS and PC clients. Required inputs are: 1. Type of configuration (Client/Server/Both). 2. Disk name to install EDCS disk structure for server. 3. Disk name to install EDCS disk structure for client. 4. Name of database (if creating) 5. Device where database will be stored (if creating) The installation procedure requires 50,000 blocks of disk space on the system disk for the installation. For PC clients, a directory [EDCS.PC] will be created on the client disk with the required files for a PC installation. Post installation actions will include modifying EDCS$SERVER.INI and EDCS$CLIENT.INI files for system configuration. This installation does NOT modify the current INI files. Also, modify the EDCS$SCRATCH logical in EDCS$STARTUP24.COM to point to the server disk. To start the system type: @SYS$STARTUP:EDCS$STARTUP24 * Will you ever use the EDCS PC client with this server? [YES]? y * Enter type of configuration ([CLIENT],SERVER,BOTH): [SERVER]: both Installing EDCSV2.4A Client/Server * Specify the device for the EDCS Client: [SYS$SYSDEVICE:]: SYS$SYSDEVICE: %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[ EDCS]. SYS$SYSDEVICE: %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[ edcs.pc]. * Specify the device for the EDCS Server: [SYS$SYSDEVICE:]: * Do you want to create a new EDCSV2.4A database (Y,N)? [N]? n Installing EDCSV2.4A Client A-2 Sample Installation for an OpenVMS Server and Client %VMSINSTAL-I-RESTORE, Restoring product save set B ... Linking EDCS24.EXE and EMU24.EXE... Copying Client files... %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[EDCS.PC]. %CREATE-I-EXISTS, SYS$SYSDEVICE:[EDCS.PC] already exists %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... %VMSINSTAL-I-RESTORE, Restoring product save set B ... %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[EDCS.PC]. %CREATE-I-EXISTS, SYS$SYSDEVICE:[EDCS.PC] already exists Installing EDCSV2.4A Server %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[ EDCS.FTX]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[ EDCS.NOTIFICATION]. %VMSINSTAL-I-RESTORE, Restoring product save set C ... %VMSINSTAL-I-RESTORE, Restoring product save set D ... Linking server executables... Linking EDCS$NET.EXE Linking EDCS$CMD.EXE Linking EDCS$FILE.EXE Linking EDCS$FTX.EXE Linking EDCS$MTX.EXE Linking EDCS$SHUTDOWN.EXE Linking EDCS$CONVERT_PASS.EXE Linking EDCS$EDCS$SEED_DB.EXE Copying Server files... %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Installation of EDCSVV V2.4A completed at 20:28 VMSINSTAL procedure done at 20:43 SYSTEM logged out at 25-JUL-1995 20:58:44.67 Sample Installation for an OpenVMS Server and Client A-3 B ________________________________________________________________ Sample Installation for an OpenVMS Server This appendix shows an example of an OpenVMS server installation. $ @vmsinstal edcsvv024 $1$DKB100:[EDCS_DEV] OpenVMS VAX Software Product Installation Procedure V6.1 It is 25-JUL-1995 at 01:19. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? The following products will be processed: EDCSVV V2.4A Beginning installation of EDCSVV V2.4A at 01:19 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. Installing EDCS server for OpenVMS VAX/Alpha. Copyright Digital Equipment Corporation 1993,1994, 1995. All rights reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. This installation supports ALPHA/VMS and VAX/VMS EDCSV2.4A servers and ALPHA/VMS, VAX/VMS and PC clients. Required inputs are: Sample Installation for an OpenVMS Server B-1 1. Type of configuration (Client/Server/Both). 2. Disk name to install EDCS disk structure for server. 3. Disk name to install EDCS disk structure for client. 4. Name of database (if creating) 5. Device where database will be stored (if creating) The installation procedure requires 50,000 blocks of disk space on the system disk for the installation. For PC clients, a directory [EDCS.PC] will be created on the client disk with the required files for a PC installation. Post installation actions will include modifying EDCS$SERVER.INI and EDCS$CLIENT.INI files for system configuration. This installation does NOT modify the current INI files. Also, modify the EDCS$SCRATCH logical in EDCS$STARTUP24.COM to point to the server disk. To start the system type: @SYS$STARTUP:EDCS$STARTUP24 * Will you ever use the EDCS PC client with this server? [YES]? * Enter type of configuration ([CLIENT],SERVER,BOTH): [SERVER]: server * Specify the device for the EDCS Server: [SYS$SYSDEVICE:]: %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[ EDCS]. * Do you want to create a new EDCSV2.4A database (Y,N)? [N]? n Installing EDCSV2.4A Server B-2 Sample Installation for an OpenVMS Server %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[ EDCS.FTX]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[ EDCS.NOTIFICATION]. %VMSINSTAL-I-RESTORE, Restoring product save set C ... %VMSINSTAL-I-RESTORE, Restoring product save set D ... Linking server executables... Linking EDCS$NET.EXE Linking EDCS$CMD.EXE Linking EDCS$FILE.EXE Linking EDCS$FTX.EXE Linking EDCS$MTX.EXE Linking EDCS$SHUTDOWN.EXE Linking EDCS$CONVERT_PASS.EXE Linking EDCS$EDCS$SEED_DB.EXE Copying Server files... %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Installation of EDCSVV V2.4A completed at 01:25 VMSINSTAL procedure done at 01:25 Sample Installation for an OpenVMS Server B-3 C ________________________________________________________________ Sample Installation for an OpenVMS Client This appendix shows an example of an OpenVMS client installation. $ @vmsinstal edcsvv024 $1$DKB100:[EDCS_DEV] OpenVMS VAX Software Product Installation Procedure V6.1 It is 25-JUL-1995 at 01:26. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? The following products will be processed: EDCSVV V2.4A Beginning installation of EDCSVV V2.4A at 01:26 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. Installing EDCS server for OpenVMS VAX/Alpha. Copyright Digital Equipment Corporation 1993,1994, 1995. All rights reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. Sample Installation for an OpenVMS Client C-1 This installation supports ALPHA/VMS and VAX/VMS EDCSV2.4A servers and ALPHA/VMS, VAX/VMS and PC clients. Required inputs are: 1. Type of configuration (Client/Server/Both). 2. Disk name to install EDCS disk structure for server. 3. Disk name to install EDCS disk structure for client. 4. Name of database (if creating) 5. Device where database will be stored (if creating) The installation procedure requires 50,000 blocks of disk space on the system disk for the installation. For PC clients, a directory [EDCS.PC] will be created on the client disk with the required files for a PC installation. Post installation actions will include modifying EDCS$SERVER.INI and EDCS$CLIENT.INI files for system configuration. This installation does NOT modify the current INI files. Also, modify the EDCS$SCRATCH logical in EDCS$STARTUP24.COM to point to the server disk. To start the system type: @SYS$STARTUP:EDCS$STARTUP24 * Will you ever use the EDCS PC client with this server? [YES]? y * Enter type of configuration ([CLIENT],SERVER,BOTH): [SERVER]: client Installing EDCSV2.4A CLIENT * Specify the device for the EDCS Client: [SYS$SYSDEVICE:]: SYS$SYSDEVICE: %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[ EDCS]. SYS$SYSDEVICE: %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[ edcs.pc]. Installing EDCSV2.4A Client C-2 Sample Installation for an OpenVMS Client %VMSINSTAL-I-RESTORE, Restoring product save set B ... Linking EDCS24.EXE and EMU24.EXE... Copying Client files... %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[ EDCS.PC]. %CREATE-I-EXISTS, SYS$SYSDEVICE:[EDCS.PC] already exists %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Installation of EDCSVV V2.4A completed at 01:28 VMSINSTAL procedure done at 01:29 Sample Installation for an OpenVMS Client C-3 D ________________________________________________________________ Sample Installation of a MS-DOS Client This appendix shows an example of a MS-DOS client installation. Digital Equipment Corporation. 1995. All Rights Reserved. ======================================================================== EDCS II V2.4A MS-DOS Client installation ======================================================================== In order to start installation of EDCS II Version 2.4A MS-DOS client you need to have the following: o A total of 1.26 Mbytes disk space available on your system In order to successfully run the MS-DOS client, you need to have the following: o PATHWORKS for DOS Version 5.0A o PATHWORKS for DOS TCP/IP Version 1.3 o PATHWORKS for VMS Version 5.0A on your VMS server node. o A total of 4 Mbytes memory available on your PC o Your AUTOEXEC.BAT file to include the following environment variables: - Modify your PATH to include \EDCS directory - Set EDCSHOST=VMS_CLIENT_NODE_NAME - Set EDCSPORT=1300 The installation will create and copy the following files and directories. C:\c600\include\edcs\edcsdefs.h C:\c600\include\edcs\edcsmsg.h C:\edcs\example\unixpcex.c C:\edcs\example\nmakefile.ex C:\edcs\edcs.exe C:\edcs\edcshelp.hlb C:\c600\lib\edcs.lib Sample Installation of a MS-DOS Client D-1 To terminate the installation enter CTRL/C [[ Creating file C:\c600\include\edcs\edcsdefs.h... ]] Does EDCSDEFS.H specify a file name or directory name on the target (F = file, D = dirctory)? F Reading source file(s)... A:\EDCSDEFS.H 1 File(s) copied [[ Creating file C:\c600\include\edcs\edcsmsg.h... ]] 1 file(s) copied [[ Creating file C:\edcs\example\unixpcex.c... ]] Does UNIXPCEX.C specify a file name or directory name on the target (F = file, D = dirctory)? F Reading source file(s)... A:\UNIXPCEX.C 1 File(s) copied [[ Creating file C:\edcs\example\nmakefile.ex... ]] 1 file(s) copied [[ Creating file C:\edcs\edcs.exe... ]] 1 file(s) copied [[ Creating file C:\edcs\edcshelp.hlb... ]] 1 file(s) copied [[ Creating file C:\c600\lib\edcs.lib... ]] Does EDCS.LIB specify a file name or directory name on the target (F = file, D = dirctory)? F Reading source file(s)... A:\EDCS.LIB 1 File(s) copied Cleaning up... ****************************************** Installation of EDCS II V2.4A MS-DOS Client Completed Successfully ****************************************** D-2 Sample Installation of a MS-DOS Client E ________________________________________________________________ Files and Logical Names Added or Modified by the Installation This appendix lists the files and logical names added or modified during the installation. E.1 Files Added The following is a list of files added during the installation. [EDCS]EDCS$CREATE_DIRECTORIES.COM [EDCS]EDCS$IMPORT_DATABASE.COM [EDCS]EDCS$INQUIRE_DATABASE.COM [EDCS]EDCS$TUNE_DATABASE.COM [EDCS]EDCS.RBR [EDCS]FTX.DIR [EDCS]NOTIFICATION.DIR [EDCS]PC.DIR [EDCS.PC]CLIENT.INI [EDCS.PC]CLNT_DLL.INI [EDCS.PC]EDCS.EXE [EDCS.PC]EDCSDATA.H [EDCS.PC]EDCSDEFS.H [EDCS.PC]EDCSHELP.HLB [EDCS.PC]EDCSPRTO.H [EDCS.PC]EDCSWIN.DLL [EDCS.PC]EDCSWIN.LIB [EDCS.PC]EDCS_DOS.LIB [EDCS.PC]EDCS_WIN.LIB [EDCS.PC]EMU.EXE [EDCS.PC]INSTALL.BAT [EDCS.PC]NOTICE SYS$STARTUP:EDCS$START_CLIENT24.COM SYS$STARTUP:EDCS$RUN_CMD.COM SYS$STARTUP:EDCS$RUN_FILE.COM SYS$STARTUP:EDCS$RUN_FTX.COM SYS$STARTUP:EDCS$RUN_MTX.COM Files and Logical Names Added or Modified by the Installation E-1 SYS$STARTUP:EDCS$RUN_NET.COM SYS$STARTUP:EDCS$SHUTDOWN24.COM SYS$STARTUP:EDCS$START_FILE.COM SYS$STARTUP:EDCS$START_NET.COM SYS$SYSTEM:EDCS$CMD.EXE SYS$SYSTEM:EDCS$CONVERT_PASS.EXE SYS$SYSTEM:EDCS$FILE.EXE SYS$SYSTEM:EDCS$FTX.EXE SYS$SYSTEM:EDCS$MTX.EXE SYS$SYSTEM:EDCS$NET.EXE SYS$SYSTEM:EDCS$SEED_DB.EXE SYS$SYSTEM:EDCS$SHUTDOWN.EXE SYS$SYSTEM:EDCS24.EXE SYS$SYSTEM:EMU24.EXE SYS$HELP:EDCS024.RELEASE_NOTES SYS$LIBRARY:EDCSDEFS.H SYS$LIBRARY:EDCSPRTO.H SYS$LIBRARY:EDCS_LIBRARY.OLB SYS$MANAGER:EDCS$SERVER.INI SYS$HELP:EDCS$HELP.HLB SYS$HELP:EDCS024.RELEASE_NOTES SYS$LIBRARY:EDCSDATA.H SYS$MANAGER:EDCS$CLIENT.INI SYS$MANAGER:EDCS$NOTICE.INI SYS$STARTUP:EDCS$RUN_CMD.COM SYS$STARTUP:EDCS$RUN_FILE.COM SYS$STARTUP:EDCS$RUN_FTX.COM SYS$STARTUP:EDCS$RUN_MTX.COM SYS$STARTUP:EDCS$RUN_NET.COM SYS$STARTUP:EDCS$SHUTDOWN24.COM SYS$STARTUP:EDCS$START_FILE.COM SYS$STARTUP:EDCS$START_NET.COM SYS$SYSTEM:EDCS$CMD.EXE SYS$SYSTEM:EDCS$CONVERT_PASS.EXE SYS$SYSTEM:EDCS$FILE.EXE SYS$SYSTEM:EDCS$FTX.EXE SYS$SYSTEM:EDCS$MTX.EXE SYS$SYSTEM:EDCS$NET.EXE SYS$SYSTEM:EDCS$SEED_DB.EXE SYS$SYSTEM:EDCS$SHUTDOWN.EXE SYS$SYSTEM:EDCS24.EXE SYS$SYSTEM:EMU24.EXE E-2 Files and Logical Names Added or Modified by the Installation E.2 Files Deleted The following is a list of files deleted during the installation. SYS$LIBRARY:DCLTABLES.EXE SYS$LIBRARY:EDCS_LIBRARY.OLB SYS$HELP:EDCS$HELP.HLB E.3 Files Modified The following file is modified during the installation. [SYS0.SYSCOMMON.SYSMGR]EDCS$SERVER.INI E.4 Files Accessed The following is a list of files accessed during the installation (except installed images). [EDCS]EDCS$CREATE_DIRECTORIES.COM [EDCS]EDCS$IMPORT_DATABASE.COM [EDCS]EDCS$INQUIRE_DATABASE.COM [EDCS]EDCS$TUNE_DATABASE.COM [EDCS]EDCS.RBR [EDCS]NOTIFICATION.DIR [EDCS.PC]CLIENT.INI [EDCS.PC]CLNT_DLL.INI [EDCS.PC]EDCS.EXE [EDCS.PC]EDCSDATA.H [EDCS.PC]EDCSDEFS.H [EDCS.PC]EDCSHELP.HLB [EDCS.PC]EDCSPRTO.H [EDCS.PC]EDCSWIN.DLL [EDCS.PC]EDCSWIN.LIB [EDCS.PC]EDCS_DOS.LIB [EDCS.PC]EDCS_WIN.LIB [EDCS.PC]EMU.EXE [EDCS.PC]INSTALL.BAT [EDCS.PC]NOTICE. SYS$STARTUP:EDCS$START_CLIENT24.COM SYS$STARTUP:EDCS$RUN_CMD.COM SYS$STARTUP:EDCS$RUN_FILE.COM SYS$STARTUP:EDCS$RUN_FTX.COM SYS$STARTUP:EDCS$RUN_MTX.COM Files and Logical Names Added or Modified by the Installation E-3 SYS$STARTUP:EDCS$RUN_NET.COM SYS$STARTUP:EDCS$SHUTDOWN24.COM SYS$STARTUP:EDCS$START_FILE.COM SYS$STARTUP:EDCS$START_NET.COM SYS$SYSTEM:BACKUP.EXE SYS$SYSTEM:CREATE.EXE SYS$SYSTEM:EDCS$CMD.EXE SYS$SYSTEM:EDCS$CONVERT_PASS.EXE SYS$SYSTEM:EDCS$FILE.EXE SYS$SYSTEM:EDCS$FTX.EXE SYS$SYSTEM:EDCS$MTX.EXE SYS$SYSTEM:EDCS$NET.EXE SYS$SYSTEM:EDCS$SEED_DB.EXE SYS$SYSTEM:EDCS$SHUTDOWN.EXE SYS$SYSTEM:EDCS24.EXE SYS$SYSTEM:EMU24.EXE SYS$SYSTEM:INSTALL.EXE SYS$SYSTEM:LIBRARIAN.EXE SYS$SYSTEM:RIGHTSLIST.DAT SYS$HELP:EDCS024.RELEASE_NOTES SYS$LIBRARY:DCLTABLES.EXE SYS$LIBRARY:DECC$SHR.EXE SYS$LIBRARY:EDCSDEFS.H SYS$LIBRARY:EDCSPRTO.H SYS$LIBRARY:EDCS_LIBRARY.OLB SYS$LIBRARY:RDBSHR.EXE SYS$LIBRARY:SQL$SHR.EXE SYS$LIBRARY:SQL$USER.OLB SYS$MANAGER:EDCS$SERVER.INI SYS$MANAGER:SYSTARTUP_V5.COM SYS$HELP:EDCS$HELP.HLB SYS$LIBRARY:EDCSDATA.H SYS$LIBRARY:UCX$IPC.OLB SYS$MANAGER:EDCS$CLIENT.INI SYS$MANAGER:EDCS$NOTICE.INI E-4 Files and Logical Names Added or Modified by the Installation