DECview3D_CVE_for_VMS_________________________ Installation Guide Part Number: AA-PK4JB-TE July 1992 This document describes how to install the DECview3D for VMS Concurrent View and Edit (CVE) Module to view and edit graphics files. Revision/Update Information: This revised manual supersedes the DECview3D CVE for VMS Installation Guide, Version 2.1 (Part Number AA-PK4JA-TE). Operating System and VMS Version 5.4 or Version: higher Software Version: DECview3D CVE for VMS Version 2.2 Digital Equipment Corporation Maynard, Massachusetts __________________________________________________________ First Printing, November 1991 Revised, July 1992 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. © Digital Equipment Corporation 1992. The postpaid Reader's Comments forms at the end of this document request your critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: DECnet, DECview3D, DECwindows, VAX, VAX DOCUMENT, VMS, VAXcluster, VAXstation, VT, and the DIGITAL logo. PostScript is a trademark of Adobe Systems, Incorporated. This document was prepared using VAX DOCUMENT, Version 2.0. ________________________________________________________________ Contents Preface.................................................. v 1 Preparing to Install CVE 1.1 Required Operating System Components............ 1-1 1.2 Prerequisite Hardware........................... 1-2 1.3 Prerequisite Software........................... 1-2 1.4 License Registration............................ 1-3 1.5 Special Requirements for Installing CVE......... 1-4 1.6 Installation Procedure Requirements............. 1-4 1.6.1 Privileges and Disk Space .................... 1-4 1.6.2 System Parameters ............................ 1-5 1.6.2.1 Checking System Parameter Values........... 1-6 1.6.2.2 Calculating the Values for GBLPAGES and GBLSECTIONS................................ 1-6 1.6.2.3 Changing System Parameter Values with AUTOGEN.................................... 1-7 1.6.3 Process Account Quotas ....................... 1-8 1.6.4 VMSINSTAL Requirements ....................... 1-10 1.6.5 Backing Up Your System Disk .................. 1-11 2 Installing CVE 2.1 The Installation Procedure...................... 2-1 2.2 Error Recovery.................................. 2-12 iii 3 After Installing CVE 3.1 Editing the System Files........................ 3-1 3.2 VAXcluster Considerations....................... 3-1 3.3 Server Account Disk Quota....................... 3-2 3.4 User Account Requirements....................... 3-3 3.4.1 Privileges ................................... 3-3 3.4.2 Disk Quotas .................................. 3-3 3.4.3 User Account Quotas .......................... 3-3 3.4.4 Setting Up User Accounts ..................... 3-4 3.5 Determining and Reporting Problems.............. 3-5 4 Installation Verification Procedure 4.1 Invoking the IVP................................ 4-1 4.2 Interacting with the IVP........................ 4-1 4.3 Exiting the IVP................................. 4-2 A Sample Installation B Files and Logical Names Installed on Your System B.1 File Names...................................... B-1 B.2 Logical Names................................... B-2 Tables 1-1 Hardware Requirements for Installing CVE ..... 1-2 1-2 Prerequisite and Optional Software ........... 1-2 1-3 Disk Space Requirements ...................... 1-5 1-4 Minimum Required System Parameter Values ..... 1-5 1-5 Process Account Quotas for the Installing Account....................................... 1-8 3-1 User Account Quotas for Using CVE ............ 3-4 iv ________________________________________________________________ Preface The DECview3D CVE for VMS (CVE) application provides a means for two users in different locations to concurrently run DECview3D in such a way that the results of commands and actions issued by either user display simultaneously on both users' screens. This application lets users view, edit, and annotate graphic data concurrently during a CVE session. CVE helps users who are discussing a drawing on the telephone to visualize the details and record annotations to the drawing made by either party in the discussion. Purpose of This Guide This guide gives requirements and provides instructions for installing CVE for VMS. Intended Audience This document is intended for system managers or users who install the CVE software. You should be familiar with system management procedures. Structure of This Guide This guide contains the following: o Chapter 1, Preparing to Install CVE, describes the prerequisites for installing the Concurrent Viewing and Editing software. o Chapter 2, Installing CVE, gives a step-by-step description of the process of installing the software. v o Chapter 3, After Installing CVE, gives instructions for including the CVE software in system management procedures and for preparing users' accounts. o Chapter 4, Installation Verification Procedure, describes how to invoke, interact, and exit from the IVP. o Appendix A, Sample Installation, is a log of an installation. o Appendix B, Files and Logical Names Installed on Your System, is a list of files that are created during an installation and a list of all logical names that are defined. Related Documentation For more information, see the following documents: o DECview3D User's Guide provides instructions on how to use the DECview3D software. o DECview3D Reference Manual describes all DECview3D operations. o DECview3D Integration Guide instructs you on how to use the DECview3D software with the DECwrite document- processing software. o DECview3D CVE for VMS User's Guide instructs you on how to use the CVE software. Conventions This document uses the following documentation conven- tions: vi __________________________________________________________ Convention_______Meaning__________________________________ Ctrl/x Ctrl/x indicates that you hold down the Ctrl key while you press another key (indicated here by x). UPPERCASE Words in uppercase indicate a command, the name of a file, the name of a file protection code, or an abbreviation for a system privilege. Enter The word enter means to type information at your keyboard, and then press the Return key. $ SHOW TIME Command examples are in monospaced type, 16-NOV-92 and show all user-entered commands in 11:55:22 bold letters. Displays or output lines of prompting characters that the system prints are shown in regular type. lowercase Lowercase words in examples indicate that you supply an input value for the word. For example, PRINT filespec tells you to specify a file name. Italic type Italic type indicates complete titles of manuals. CVE Used throughout this guide to refer to DECview3D Concurrent View and Edit Module _________________for_VMS._________________________________ vii 1 ________________________________________________________________ Preparing to Install CVE This chapter discusses the preparations and requirements necessary for installing CVE. This manual applies to Version 2.2 of CVE and all subsequent maintenance releases up to the next major product release. 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 your kit is damaged or if you find that parts of it are missing, contact your Digital representative. CVE provides online release notes. Digital strongly recommends that you read the release notes before proceeding with the installation. For information on accessing the online release notes, see Section 2.1. 1.1 Required Operating System Components The VMS operating system comes with a variety of support options, or classes. Classes include such features as networking and RMS journaling. To use CVE, your system should be running a version of VMS that includes at least the following classes: o VMS Required Saveset o Network Support o Secure User's Environment o Utilities o VMS Workstation Support Preparing to Install CVE 1-1 For a complete list of the required classes, see the Software Support Addendum (SSA), which comes with the Software Product Description (SPD). 1.2 Prerequisite Hardware Table 1-1 describes the hardware items needed to install CVE. Table_1-1_Hardware_Requirements_for_Installing_CVE________ Item________________Purpose_______________________________ DECwindows A VAXstation running DECwindows is VAXstation required to run the Installation ____________________Verification_Procedure_(IVP)._________ 1.3 Prerequisite Software Table 1-2 provides information on the software you must have installed on your system before installing CVE. The System Software Addendum (SSA) contains a complete list of prerequisite and optional software and their required version numbers. Table_1-2_Prerequisite_and_Optional_Software______________ Prerequisite Products____________Comments______________________________ VMS Version 5.4 VMS Version 5.4 or higher must be installed before you can install CVE. DECwindows Version You must install CVE from a VAXstation 2.0 running DECwindows Version 2.0 or higher. DECnet Phase IV DECnet must be running before you install CVE if you plan to run the IVP. (continued on next page) 1-2 Preparing to Install CVE Table_1-2_(Cont.)_Prerequisite_and_Optional_Software______ Prerequisite Products____________Comments______________________________ DECview3D Version DECview3D must be installed before 2.2 you install CVE if you plan to run the IVP.[1] [1]Note_that_DECview3D_for_VMS_V2.2_requires_VMS_V5.3,____ while CVE for VMS V2.2 requires VMS V5.4. __________________________________________________________ 1.4 License Registration Before you install and run CVE Version 2.2 on a newly licensed node or cluster, you must first register a License Product Authorization Key (License PAK) using the License Management Facility (LMF). The License PAK may be shipped along with the kit if you ordered the license and media together; otherwise, it is shipped separately to a location based on your license order. If you are installing CVE as an update on a node or cluster already licensed for this software, you have already completed the License PAK registration requirements. You must register and load your license for DECview3D CVE for VMS before you start the installation in order to run the IVP and use the software. To register a license under VMS, first log in to the system manager's account, SYSTEM. You then have a choice of two ways to perform the registration: o Invoke the SYS$UPDATE:VMSLICENSE.COM procedure. When it prompts you for information, respond with data from your License PAK. o At the DCL prompt, enter the LICENSE REGISTER command with the appropriate qualifiers that correspond to License PAK information. If you plan to use DECview3D CVE for VMS on more than one node in a VAXcluster, you will need to perform a license load on the other nodes after you complete this installation. See Section 3.2. Preparing to Install CVE 1-3 For complete information on using LMF, see the VMS License Management Utility Manual. 1.5 Special Requirements for Installing CVE If you plan to run the IVP, several conditions must first be met: o DECnet must be running. o DECview3D Version 2.2 must be installed and its license registered. o You must be installing CVE from a VAXstation running DECwindows, since the IVP uses a DECwindows interface. o You must Customize the Security settings in your DECwindows Session Manager to authorize the CVE$SERVER account on node 0 (your local node) with LOCAL transport. 1.6 Installation Procedure Requirements This section and those that follow discuss various requirements for installing CVE. The installation takes approximately 5 to 15 minutes, depending on your type of media and your system configura- tion. Installing CVE and running the IVP on a standalone VAXstation II/GPX system takes 5 minutes when installed from a saveset located on the disk. 1.6.1 Privileges and Disk Space To install CVE, you must be logged in to an account that has SETPRV or at least the following privileges: o CMKRNL o WORLD o SYSPRV o CMKRNL o OPER 1-4 Preparing to Install CVE Note that VMSINSTAL turns off BYPASS privilege at the start of the installation. CVE's requirements for free disk storage space are different during installation and after installation. Table 1-3 summarizes the storage requirements. Table_1-3_Disk_Space_Requirements_________________________ Blocks During Blocks After Kit______________Installation__________Installation_______ CVE_Version_2.2__900___________________450________________ To determine the number of free disk blocks on the current system disk, enter the following command at the DCL prompt: $ SHOW DEVICE SYS$SYSDEVICE 1.6.2 System Parameters Installing CVE requires certain system parameter settings. Table 1-4 lists the minimum required system parameter values for the installation. Depending on the kinds of programs and applications running at your site, you might need higher values for some settings. Table_1-4_Minimum_Required_System_Parameter_Values________ System Parameter________Minimum_Value____________________________ GBLPAGES[1] n + 3 + size in blocks of SYS$LIBRARY:DCLTABLES.EXE GBLSECTIONS[1] n + 3 WSMAX 6144 [1]The_values_listed_for_these_system_parameters_represent the number of free global pages and global sections required for the installation, not the total number you need to run your system and other software. __________________________________________________________ The following sections show you how to: o Check system parameter values Preparing to Install CVE 1-5 o Calculate values for the GBLPAGES and GBLSECTIONS system parameters o Change parameter values with the VMS AUTOGEN command procedure 1.6.2.1 Checking System Parameter Values To check the values of your system parameters, enter the following command at the DCL prompt to invoke the System Generation Utility (SYSGEN): $ RUN SYS$SYSTEM:SYSGEN At the SYSGEN> prompt, enter the SHOW command to display the value of a system parameter. The values displayed should equal or exceed the value of each system parameter listed in Table 1-4. The following example displays the value for the WSMAX system parameter: SYSGEN> SHOW WSMAX After checking the parameters with the SHOW command, enter the EXIT command at the SYSGEN> prompt to return to DCL level. 1.6.2.2 Calculating the Values for GBLPAGES and GBLSECTIONS To install and run CVE, you must have sufficient free global pages and global sections. You must first find out how many free global pages and sections you have on your system. Then use AUTOGEN if you need to increase the GLBPAGES and GBLSECTIONS system parameters. 1-6 Preparing to Install CVE If you are installing CVE on a VMS Version 5.4 system or higher, you can use the WRITE command with the F$GETSYI lexical function to find the number of free global pages and global sections. The following example shows how to get this information at your terminal (the default for SYS$OUTPUT): $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES") 15848 $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS") 24 If the values displayed by the system are greater than the values in Table 1-4, you do not need to increase the values for these parameters. If the value of free global pages or global sections is less than the value in Table 1-4, you must increase the system parameter setting. Section 1.6.2.3 describes the procedures for increasing these values using AUTOGEN. 1.6.2.3 Changing System Parameter Values with AUTOGEN Use the AUTOGEN command procedure to change system parameters. AUTOGEN automatically adjusts values for parameters that are associated with the values you reset manually. To change system parameters with AUTOGEN, edit the following file: SYS$SYSTEM:MODPARAMS.DAT Use an editor to access the file. To change a parameter value listed in this file, delete the current value associated with that parameter and enter the new value. To add a new parameter, add a line to the file that includes both the name of the parameter and its value. For example: WSMAX = 6144 To modify incremental parameters such as GBLPAGES and GBLSECTS, use ADD_. The following example increases the global page setting by 2000: ADD_GBLPAGES = 2000 Preparing to Install CVE 1-7 Note that when you set the page file quota, do not use a value that exceeds the amount of page file space available on the system. After you make all your changes, exit from the editor and execute the AUTOGEN procedure to recalculate your system parameters. Enter the following command at the DCL prompt: $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT When you specify REBOOT, AUTOGEN performs an automatic system shutdown and then reboots the system. Any users logged on to the system are immediately disconnected during the shutdown. The automatic reboot puts the new parameter values into effect. The AUTOGEN Utility automatically adjusts some of the SYSGEN parameters based on the consumption of resources since the last reboot. If you do not want to take advantage of this automatic adjustment, include the NOFEEDBACK qualifier on the AUTOGEN command line. For more information about using AUTOGEN, see the VMS System Management Subkit. 1.6.3 Process Account Quotas The account you use to install CVE must have sufficient quotas to enable you to perform the installation and run the Installation Verification Procedure. Table 1-5 summarizes the process quotas required for the installation account. If you do not plan to run the IVP from the installation account, you can disregard the requirements in this table. Table 1-5 Process Account Quotas for the Installing __________Account_________________________________________ Account_Quota____Value____________________________________ ASTLM 100 BIOLM 40 (continued on next page) 1-8 Preparing to Install CVE Table 1-5 (Cont.) Process Account Quotas for the __________________Installing_Account______________________ Account_Quota____Value____________________________________ BYTLM 60,000 DIOLM 40 ENQLM 100 FILLM 50 PFGLQUO 50,000 WSDEF 1024[1] WSQUO 3072[1] WSEXT 6144[1] [1]The_values_for_WSEXT_must_be_greater_than_or_equal_to__ the value for WSQUO, which must be equal to or greater than the WSDEF value. __________________________________________________________ Preparing to Install CVE 1-9 User account quotas are stored in the file SYSUAF.DAT. Use the VMS Authorize Utility (AUTHORIZE) to verify and change user account quotas. First set your directory to SYS$SYSTEM and then run AUTHORIZE: $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE At the UAF> prompt, enter the SHOW command with an account name to check a particular account. For example: UAF> SHOW SMITH To change a quota, enter the MODIFY command. The following example changes the FILLM quota for the SMITH account and then exits from the utility: UAF> MODIFY SMITH /FILLM=50 UAF> EXIT After you exit from the utility, the system displays messages indicating whether or not changes were made. Once the changes have been made, you must log out and log in again for the new quotas to take effect. For more information on modifying account quotas, see the description of the Authorize Utility in the VMS System Management Subkit. 1.6.4 VMSINSTAL Requirements When you invoke VMSINSTAL, it checks the following: o Whether you have set your default device and directory to SYS$UPDATE o Whether you are logged in to a privileged account o Whether you have adequate quotas for installation o Whether DECnet is running o Whether any users are logged in to the system Note that the VMSINSTAL requires that the installation account have a minimum of the following quotas: ASTLM = 24 BIOLM = 18 BYTLM = 18,000 DIOLM = 18 1-10 Preparing to Install CVE ENQLM = 30 FILLM = 20 If VMSINSTAL detects any problems during the installation, it notifies you 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. 1.6.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. Use the backup procedures that are established at your site. For details on performing a system disk backup, see the section on the "Backup Utility" in the VMS System Management Subkit. Preparing to Install CVE 1-11 2 ________________________________________________________________ Installing CVE This chapter explains how to install CVE. Section 2.1 contains a step-by-step description of the installation procedure. 2.1 The Installation Procedure The CVE installation procedure consists of a series of questions and informational messages. See Appendix A for a sample 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 start the installation again. 1. Invoke VMSINSTAL. $ @SYS$UPDATE:VMSINSTAL saveset-name device-name OPTIONS N To start the installation, invoke the VMSINSTAL command procedure from a privileged account, such as the SYSTEM account. VMSINSTAL is in the SYS$UPDATE directory. The following list defines the elements of the VMSINSTAL command procedure: saveset-name The installation name for the component. For CVE, use the following installation name: CVE022 device-name The name of the device on which you plan to mount the media. For example, MUA0: is the device name for a tape drive. It is not necessary to use the console drive for this installation. However, if you do use the console Installing CVE 2-1 drive, you should replace any media you removed once the installation is complete. OPTIONS N An optional parameter that indicates you want to see the question on release notes. If you do not include the OPTIONS N parameter, VMSINSTAL does not ask you about the release notes. You should review the release notes before proceeding with the installation in case they contain additional information about the installation. If you are restarting the installation and have already reviewed the release notes, you do not need to specify OPTIONS N. Note that there are several other options you can select when you invoke VMSINSTAL. o Auto_answer option (A): Initially creates a file that contains your answers to VMSINSTALL questions and prompts. You can then use the option (and the answer file) to save time during a reinstallation (typically after upgrading your system). o Get saveset option (G): Lets you store product savesets temporarily on a magnetic tape or in a disk directory. o File log option (L): Logs all activity to the terminal during installation. o Alternate root option (R): Lets you install the product to a system root other than that of the running system. See the VMS documentation on software installation in the VMS System Management Subkit for detailed information on these options. If you specify more than one option, separate the options with commas (OPTIONS A,N). The following example invokes VMSINSTAL to install CVE from tape drive MUA0: and shows the system response. This example uses the OPTIONS N release note parameter. 2-2 Installing CVE $ @SYS$UPDATE:VMSINSTAL CVE021 MUA0: OPTIONS N VAX/VMS Software Product Installation Procedure V5.4 It is 16-NOV-1992 at 19:56. Enter a question mark (?) at any time for help. If you do not supply either the product name or the device name, VMSINSTAL prompts you for this information later in the installation procedure. VMSINSTAL does not prompt you for any options, so be sure to include OPTIONS N on the VMSINSTAL command line to access the release notes during the installation. Installing CVE 2-3 2. Confirm system status. VMSINSTAL displays a list of all active user processes (other than the installing process) and asks if you want to continue the installation. You can safely continue the installation with other processes running on your system. Although NO is the default response to the question, you should answer YES to continue the installation. 3. Confirm system backup. * Are you satisfied with the backup of your system disk [YES]? VMSINSTAL asks if you are satisfied with your system backup. You should always back up your system disk before performing an installation. If you are satisfied with the backup of your system disk, press RETURN. Otherwise, enter NO to discontinue the installation. After you back up your system disk, you can restart the installation. 4. Mount the media. Please mount the first volume of the set on MUA0:. * Are you ready? YES %MOUNT-I-MOUNTED, CVE MOUNTED ON _$$MUA0: (NODE 1) The following products will be processed: CVE V2.2 Beginning installation of CVE V2.2 at 19:56 %VMSINSTAL-I-RESTORE, Restoring product saveset A . . . You should now mount the first distribution volume on the device you specified when you invoked VMSINSTAL. The device name appears in the line preceding the question. VMSINSTAL then asks you if you are ready to continue with the installation. If you respond YES to indicate that you are ready, VMSINSTAL displays a message that the media containing CVE has been mounted on the specified device and that the installation has begun. 2-4 Installing CVE If you entered the wrong device name when you invoked VMSINSTAL and need to restart the installation, enter NO in response to the "Are you ready?" question. To abort the installation for other reasons, press Ctrl/Y. 5. Mount additional media volumes. %BACKUP-I-READYREAD, mount volume 2 on _MUA0: for reading Enter "YES" when ready: If your installation kit contains more than one volume, VMSINSTAL prompts you to mount the additional volumes and then asks you to indicate that you are ready for the installation to proceed. 6. Select a release notes option. 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]: If you specified OPTIONS N when you invoked VMSINSTAL, you are now asked to choose one of the four options for reviewing the release notes. If you select option 1, VMSINSTAL displays the release notes immediately on the console terminal. You can terminate the display at any time by pressing Ctrl/C. If you select option 2, VMSINSTAL prompts you for the name of the print queue that you want to use: * Queue name [SYS$PRINT]: You can press RETURN to send the file to the default output print device or you can enter another queue name. If you select option 3, VMSINSTAL displays the release notes immediately on the console terminal and then prompts you for a queue name for the printed version. Installing CVE 2-5 Select option 4 if you have already reviewed the release notes and are restarting the installation. Next, VMSINSTAL displays the following question: * Do you want to continue the installation [N]?:YES %VMSINSTAL-I-RELMOVED, The product's release notes have been successfully moved to SYS$HELP. To continue the installation, enter YES. Otherwise, press RETURN. In either case, the release notes are copied to a file in the SYS$HELP directory: SYS$HELP:CVE022.RELEASE_NOTES 2-6 Installing CVE After the installation, you can enter the following command to review the release notes through the Help facility: $ HELP CVE RELEASE_NOTES ________________________Note ________________________ The name of the release notes file installed by VMSINSTAL consists of the current product name and version number. Do not delete release notes for previous versions of CVE. _____________________________________________________ 7. Purge files. * Do you want to purge files replaced by this installation [YES]? You have the option to purge files from previous ver- sions of CVE that are superseded by this installation. Purging is recommended; however, if you need to keep files from the previous version, enter NO in response to the question. 8. Respond to license registration queries. Product: CVE, CVE-USER, or CVE-G Producer: DEC Version: 2.2 Release Date: 01-SEP-1992 * Does this product have an authorization key registered and loaded? The installation procedure displays license information about your product and then asks if you have registered and loaded your Product Authorization Key (PAK). If you have not registered and loaded your PAK, you must answer NO to this question. You have to register and load your PAK to successfully complete the installation. If you have not done so, you should stop the installation, register and load your PAK, and then restart the installation. 9. Choose the Installation Verification Procedure (IVP) option. Installing CVE 2-7 If DECnet is running on your system, and you have installed DECview3D V2.2 and its license, and you are on a DECwindows workstation, and you have registered and loaded the CVE license, you are now asked whether or not to run the IVP. If any of these conditions is not met, you cannot run the IVP as part of the installation procedure. * Do you want to run the IVP after the installation [YES]? The installation procedure now asks if you want to run the IVP. The IVP for CVE checks to be sure that the installation is successful. It is recommended that you run the IVP. After CVE is installed, you can run the IVP indepen- dently to verify that the software is available on your system. You might need to run the IVP after a system failure to make sure that users can access CVE. For instructions on running the IVP during or after the installation, please refer to Chapter 4. 10.Create an account. If this is the first time you are installing CVE on this system, the installation procedure creates the CVE$SERVER network object and a corresponding CVE$SERVER account. The installation procedure prompts you for a UIC for this account. The default UIC the prompt presents is an unused UIC in the DECNET group. It is recommended that you accept the default UIC. In order to make sure that the CVE server runs correctly, this installation procedure will create an account for the server. This CVE$SERVER account has no special privileges and is set up only for the operation of the CVE server. * Enter UIC for server account (include brackets) [[376,2]]? Press RETURN to accept the default, or enter a different UIC. Make sure that if you enter a UIC, you include the brackets. If the UIC you enter already exists or is invalid, the installation procedure informs you of this and prompts for a new UIC. 2-8 Installing CVE Once you have entered a UIC, you must enter a password for the account. Since this account will be used by a DECnet object and not by humans, the password should be long and complicated. The password must be between 8 and 31 characters in length and may not be the same as the account name. You must choose a password for the CVE$SERVER account. Since this account will never be accessed by a human, the password should be long and complicated. It must be between 8 and 31 characters long and cannot be the same as the account name. You will be asked to type a password and then to retype it for verification. The passwords you type will not be echoed to the screen. If you do not enter a password but instead press RETURN at the prompt, the installation procedure will generate a long, unique password for you. * Enter a password: * Verification: When you are prompted for the password, the password is not echoed to the screen as you type it. For this reason, you are asked to verify the password to eliminate the chances of mistyping it. If you want the installation procedure to generate a long and unique password, press RETURN when you are prompted for the password. 11.Create an application directory. If this is the first time you are installing CVE on this system, the installation procedure creates a directory where CVE places temporary files copied to this node by the software. Users may also place files to be accessed by the software in this directory. The name of this directory is [CVE$FILES]. The installation procedure prompts you for a device on which this directory is to be created. Installing CVE 2-9 The CVE server must have a directory where it can copy files passed to it or where authorized users can copy files to be accessed by the CVE server. Please specify a device where the [CVE$FILES] directory will be located. If the directory does not exist on the specified device, this procedure will create it. * What device should the [CVE$FILES] directory be on [DUA0:]? The default device presented by the prompt is the translation of SYS$SYSDEVICE or the device specified by the logical name CVE$FILES if such a logical name is defined. Enter a device name or press RETURN to accept the default. The installation procedure will check whether the device exists. If it does not, the procedure will inform you of this and prompt for a new device name. 2-10 Installing CVE 12.Read informational messages. At this point, the installation procedure displays a number of informational messages that report on the progress of the installation. There are no further questions. If the installation procedure has been successful up to this point, VMSINSTAL moves the new or modified files to their target directories, updates help files, and updates DCL tables, if necessary. If you chose to have files purged, that work is done now. Some of the messages that appear the first time you install CVE on this system will not appear during subsequent installations because some of the actions taken by the installation procedure need only be performed once on a system. The types of informational messages that appear refer to the following subjects: o Creating and updating an account. o Defining a network object. o Creating a directory. o Moving files to their target directories. o Listing of files installed. For the messages that appear during the initial installation of CVE, please see the sample installation procedure in Appendix A. 13.Observe the Installation Verification Procedure (IVP). If you chose to run the IVP, VMSINSTAL runs it now. The IVP is interactive. See Chapter 4 for instructions on how to interact with the IVP. CVE V2.2 Installation Verification Procedure When both DECview3D sessions have appeared, pull down the File menu from the CVE control box and select Quit. When the IVP has completed, you see the following display: Log file from CVE IVP session: . . . CVE IVP completed Installing CVE 2-11 14.End the installation procedure. Installation of CVE V2.2 completed at 20:02 VMSINSTAL procedure done at 20:02 The previous messages indicate that the entire installation procedure is complete. You can now log out of the privileged account: $ LOGOUT SYSTEM logged out at 16-NOV-1992 20:03:19.50 Note that VMSINSTAL deletes or changes entries in the process symbol tables during the installation. Therefore, if you are going to continue using the system manager's account and you want to restore these symbols, you should log out and log in again. 2.2 Error Recovery If errors occur during the installation itself or when the Installation Verification Procedure (IVP) is running, VMSINSTAL displays failure messages. If the installation fails, you see the following message: %VMSINSTAL-E-INSFAIL, The installation of CVE V2.2 has failed. If the IVP fails, you see these messages: The CVE V2.2 Installation Verification Procedure failed. %VMSINSTAL-E-IVPFAIL, The IVP for CVE V2.2 has failed. Errors can occur during the installation if any of the following conditions exist: o The operating system version is incorrect. o Quotas necessary for successful installation are insufficient. o System parameter values for successful installation are insufficient. o The VMS help library is currently in use. o The installing account does not have the necessary privileges. 2-12 Installing CVE For descriptions of the error messages generated by these conditions, see the VMS documentation on system messages, recovery procedures, and VMS software installation. If you are notified that any of these conditions exist, you should take the appropriate action as described in the message. For information on installation requirements, see Chapter 1. Installing CVE 2-13 3 ________________________________________________________________ After Installing CVE The following tasks take place after installing CVE: o Editing the system startup and shutdown files o Making the product usable on a VAXcluster o Setting the server account's disk quota o Setting user account quotas 3.1 Editing the System Files You must edit the system startup file to provide for automatic startup of CVE when your system is rebooted. Add the command line that starts CVE to the system startup file. The following example shows the CVE startup command line: $ @SYS$STARTUP:CVE$STARTUP.COM 3.2 VAXcluster Considerations If you are installing CVE on a VAXcluster and you want it to run on the other nodes of the cluster, you must perform four steps on each of the other cluster nodes on which you want CVE to run. You must perform these steps from the system account or from an account that has at least the privileges listed in Section 1.6.1. o Run the startup command procedure. $ @SYS$STARTUP:CVE$STARTUP.COM o Update the DCL tables. $ INSTALL REPLACE SYS$COMMON:[SYSLIB]DCLTABLES.EXE After Installing CVE 3-1 o Set the CVE$SERVER network object. $ MCR NCP SET KNOWN OBJECTS ALL o Load the license you registered on the installing node prior to the installation. $ LICENSE LOAD CVE or $ LICENSE LOAD CVE-USER or $ LICENSE LOAD CVE-G 3.3 Server Account Disk Quota If your system has disk quotas enabled, you must provide the CVE$SERVER account with disk quota on the disk that holds the CVE$FILES directory. If your system has quotas on the system disk, you must also provide the CVE$SERVER account with disk quota on that disk. The CVE$SERVER account writes the files it creates, such as layout files or snapshot files saved by the Concurrent User, to the CVE$FILES directory. The CVE$SERVER account must have sufficient disk quota to do so; otherwise, some DECview3D commands will not operate properly on the Concurrent User's system. Use the CVE$FILES logical name to determine which disk holds the CVE$FILES directory. Then use the SYSMAN utility to give the CVE$SERVER account quota on that disk. Since some files stored on the disk by CVE can be quite large, it is recommended that the CVE$SERVER account have a large (50,000 blocks or more) quota on that disk, especially if more than one CVE user will use the system. If Concurrent Users receive error messages indicating that a layout or snapshot file cannot be saved, check that the CVE$SERVER account has not exceeded its disk quota on the disk holding the CVE$FILES directory, and increase the quota if necessary. 3-2 After Installing CVE If your system has quotas enabled on the system disk, you must provide the CVE$SERVER account with disk quota on that disk so that NETSERVER.LOG and .VIEW_JOURNAL files can be placed in the CVE$SERVER's login directory. The disk quota required for this purpose is not great. Unless the CVE$FILES directory is also on the system disk, 1000 to 2000 blocks is sufficient. 3.4 User Account Requirements To work with CVE, user accounts on your system must have certain privileges and quotas. The next two sections contain information on these requirements. The third section discusses how to set up user accounts. 3.4.1 Privileges To use CVE, each account must have at least the TMPMBX and NETMBX privileges. Use the VMS Authorize Utility to determine whether users have the privileges they require. 3.4.2 Disk Quotas If your system has disk quotas enabled, you must give each user enough disk quota so that he or she can copy layout files and any other necessary files to the CVE$FILES directory. Use the CVE$FILES logical name to determine which disk holds the CVE$FILES directory. Then use the SYSMAN utility to give each user at least enough disk quota on that disk to hold all the files the user expects to keep in that directory at any one time. 3.4.3 User Account Quotas You must make sure that the appropriate user accounts have sufficient quotas to be able to use CVE. Table 3-1 summarizes the required user account quotas. After Installing CVE 3-3 Table_3-1_User_Account_Quotas_for_Using_CVE_______________ Account_Quota____Value____________________________________ ASTLM 100 BIOLM 40 BYTLM 60,000 DIOLM 40 ENQLM 100 FILLM 50 PGFLQUO 50,000 WSDEF 1024[1] WSQUO 3072[1] WSEXT 6144[1] [1]The_values_for_WSEXT_must_be_greater_than_or_equal_to__ the value for WSQUO, which must be equal to or greater than the WSDEF value. __________________________________________________________ See Section 1.6.3 for a description of how to verify and change account quotas. 3.4.4 Setting Up User Accounts User accounts should have the CVE$FILE rights identifier, which enables them to copy files to the CVE$FILES directory. The CVE$FILE rights identifier is automatically created by the installation procedure. You must grant the rights identifier from an account that has at least SYSPRV or BYPASS privilege. To grant the CVE$FILE rights identifier to a user, execute the following command: $ @SYS$MANAGER:CVE$GRANT_ID username 3-4 After Installing CVE 3.5 Determining and Reporting Problems If you encounter a problem while using CVE, report it to Digital. Depending on the nature of the problem and the type of support you have, you can take one of the following actions: o Call Digital if your software contract or warranty agreement entitles you to telephone support. o Submit a Software Performance Report (SPR). o Fill out and submit a Reader's Comments form if the problem has to do with the CVE documentation. There are Reader's Comments forms at the back of each manual. Use the form from the manual in which you found the error. Include the section and page number. Review the Software Product Description (SPD) and Warranty Addendum for an explanation of warranty. If you encounter a problem during the warranty period, report the problem as indicated above or follow alternate instructions provided by Digital for reporting SPD nonconformance problems. See the release notes for CVE for information on how to submit an SPR. After Installing CVE 3-5 4 ________________________________________________________________ Installation Verification Procedure This chapter describes the procedure for running the IVP from the installation procedure, or after completing the installation. 4.1 Invoking the IVP To run the IVP separately from the installation, log in to the SYSTEM account or into an account that has either SYSPRV, BYPASS, or READALL privilege so that you have access to the test files. The account that you run the IVP from must be logged in to a DECwindows VAXstation. Also, you must use the Session Manager's Customize Security dialog box to authorize access from node 0 (your local node), username CVE$SERVER, with LOCAL transport. Enter the following command: $ @SYS$TEST:CVE$IVP 4.2 Interacting with the IVP After you invoke the IVP, or after the installation procedure has invoked the IVP, you will see two dialog boxes entitled "Concurrent View and Edit V2.2." These overlap one another on your screen. After a short time, two DECview3D sessions display on your screen. These also overlap one another. Installation Verification Procedure 4-1 4.3 Exiting the IVP To exit the IVP, pull down the "File" menu from either CVE dialog box and choose "Quit". Both dialog boxes and both DECview3D sessions disappear from the screen. The IVP then types the contents of the CVE log file to the screen. At this point, the IVP is complete. For an example of the messages that appear when the IVP is run, see Appendix A. 4-2 Installation Verification Procedure A ________________________________________________________________ Sample Installation This appendix contains a sample installation of CVE. This sample was run on a system that had no previous version of CVE installed. The sample installation assumes that no other users are logged on to your system, and that OPTIONS N is specified to print the release notes. Note that in an actual installation, the password for the CVE$SERVER account is not echoed to the screen. Welcome to VAX/VMS V5.4 Username: SYSTEM Password: *********************************************************************** Welcome to node NODE01 VMS 5.4 *********************************************************************** Last interactive login on Thursday, 28-FEB-1992 16:09 Last non-interactive login on Thursday, 28-FEB-1992 00:00 $ @sys$update:vmsinstal cve022 kit$dir options N VAX/VMS Software Product Installation Procedure V5.4 It is 28-FEB-1992 at 19:50. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? yes The following products will be processed: CVE V2.2 Sample Installation A-1 Beginning installation of CVE V2.2 at 19:50 %VMSINSTAL-I-RESTORE, Restoring product save set A ... Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: 2 * Queue name [SYS$PRINT]: sys$print Job CVE022 (queue NODE01$LPS, entry 630) started on NODE01$LPS * Do you want to continue the installation [NO]? yes %VMSINSTAL-I-RELMOVED , The product's release notes have been successfully moved to SYS$HELP. © Digital Equipment Corporation, 1992. All Rights Reserved Installation procedure for DECview3D Concurrent View and Edit Module for VMS. During this installation, new files will be provided to replace existing versions. You may purge these older versions to save disk space, or keep them if you feel they may be of use. Purging is recommended. * Do you want to purge files replaced by this installation [YES]? yes Product: CVE, CVE-USER, or CVE-G Producer: DEC Version: 2.2 Release Date: 01-SEP-1992 * Does this product have an authorization key registered and loaded? yes Most products provide an Installation Verification Procedure (IVP) which verifies the completeness and accuracy of the installation. You may wish to run the IVP immediately after installation. * Do you want to run the IVP after the installation [YES]? yes In order to make sure that the CVE server runs correctly, this installation procedure will create an account for the server. This CVE$SERVER account has no special privileges and is set up only for the operation of the CVE server. * Enter UIC for server account (include brackets) [[376,001]]: A-2 Sample Installation You must choose a password for the CVE$SERVER account. Since this account will never be accessed by a human, the password should be long and complicated. It must be between 8 and 31 characters long and cannot be the same as the account name. You will be asked to type a password and then to retype it for verification. The passwords you type will not be echoed to the screen. If you do not enter a password but instead press RETURN at the prompt, the installation procedure will generate a long, unique password for you. * Enter a password: ABCDEFGHIJKLMNOP * Verification: ABCDEFGHIJKLMNOP The CVE server must have a directory where it can copy files passed to it or where authorized users can copy files to be accessed by the CVE server. Please specify a device where the [CVE$FILES] directory will be located. If the directory does not exist on the specified device, this procedure will create it. * What device should the [CVE$FILES] directory be on [SYS$SYSDEVICE:]: dua2: All questions required for installation of CVE have been answered. Installation will take approximately 5 to 10 minutes. Sample Installation A-3 %CVE-I-ADDID, Adding rights identifier CVE$FILE to rights list %VMSINSTAL-I-ACCOUNT, This installation adds an identifier named CVE$FILE. %UAF-I-RDBADDMSG, identifier CVE$FILE value: %X80010008 added to rights data base %CVE-I-CREACC, creating account CVE$SERVER for the CVE server %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named CVE$SERVER. %UAF-I-ADDMSG, user record successfully added %UAF-I-RDBADDMSGU, identifier CVE$SERVER value: [000376,000001] added to rights data base %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named CVE$SERVER. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named CVE$SERVER. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named CVE$SERVER. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named CVE$SERVER. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named CVE$SERVER. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[CVE$SERVER]. %CVE-I-OBJECT, defining new network object for your system %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named CVE$SERVER. %UAF-I-MDFYMSG, user record(s) updated Your VMS system will now be updated to include the following new and modified files: SYS$STARTUP:CVE$STARTUP.COM [new] SYS$SYSTEM:CVE$SERVER.COM [new] SYS$MANAGER:CVE$GRANT_ID.COM [new] SYS$SYSTEM:CVE$MAIN.EXE [new] SYS$HELP:CVE$HELP.HLB [new] DECW$SYSTEM_DEFAULTS:CVE$MAIN.UID [new] DECW$SYSTEM_DEFAULTS:CVE.DAT [new] SYS$COMMON:[SYSTEST]CVE$IVP.COM [new] SYS$COMMON:[SYSTEST.CVE]CVE$IVP.LAYOUT [new] SYS$LIBRARY:DCLTABLES.EXE [modified] SYS$HELP:HELPLIB.HLB [modified] You must add the following line to your system startup file (SYS$MANAGER:SYSTARTUP_V5.COM): $ @SYS$STARTUP:CVE$STARTUP A-4 Sample Installation The CVE Installation Verification Procedure (IVP) has been provided in SYS$COMMON:[SYSTEST]. The CVE IVP can be invoked at any time by using the following commands: $ SET DEFAULT SYS$COMMON:[SYSTEST] $ @CVE$IVP %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... %CVE-I-GRANTID, Granting rights identifier CVE$FILE to the CVE$SERVER account %UAF-I-GRANTMSG, identifier CVE$FILE granted to CVE$SERVER Beginning the CVE V2.2 Installation Verification Procedure When both DECview3D sessions have appeared, pull down the File menu from the CVE control box and select Quit. Log file from CVE IVP session: CVE V2.2 Thu Feb 28 19:54:41 1992 =======> User: NODE01::SYSTEM (Originator) =======> File on NODE01:: : SYS$COMMON:[SYSTEST.CVE]CVE$IVP.LAYOUT; =======> User: 0::SYSTEM Session ended Thu Feb 28 19:56:34 1992 The CVE V2.2 IVP has completed successfully Installation of CVE V2.2 completed at 19:56 VMSINSTAL procedure done at 19:56 $ logout SYSTEM logged out at 28-FEB-1992 19:57:25.04 Sample Installation A-5 B ________________________________________________________________ Files and Logical Names Installed on Your System The CVE installation procedure installs a number of files on your system and defines one logical name. Section B.1 lists the files installed. Section B.2 lists the logical name that is added to the system logical name table. B.1 File Names The following list contains the names of all files created on your system when CVE is installed. o SYS$STARTUP:CVE$STARTUP.COM o SYS$SYSTEM:CVE$SERVER.COM o SYS$MANAGER:CVE$GRANT_ID.COM o SYS$SYSTEM:CVE$MAIN.EXE o SYS$HELP:CVE$HELP.HLB o DECW$SYSTEM_DEFAULTS:CVE$MAIN.UID o DECW$SYSTEM_DEFAULTS:CVE.DAT o SYS$COMMON:[SYSTEST]CVE$IVP.COM o SYS$COMMON:[SYSTEST.CVE]CVE$IVP.LAYOUT Files and Logical Names Installed on Your System B-1 B.2 Logical Names The following logical name is entered into the system logical name table when CVE is installed. This name is stored in the product's startup file. It is automatically entered into the system logical name table whenever the system reboots or whenever the software is invoked. CVE$FILES This logical name points to a directory created during the installation process. This directory is used by CVE to temporarily store files copied to this node by the software. Files to be accessed by the software can also be copied to this directory by the user. B-2 Files and Logical Names Installed on Your System