DEC Storage Monitor Installation Guide for VMS Order Number: AA-PSHWA-TE October 1992 This document contains instructions for installing DEC Storage Monitor[TM] on the VMS operating system. This manual also explains how to read the online release notes before or after installing the product. Revision/Update Information: This is a new manual. Operating System and Version: VMS 5.4 or higher Software Version: DEC Storage Monitor Version 1.0 (Digital Equipment Corporation\Maynard, Massachusetts\) ________________________ First printing: October 1992 __________ Copyright ©1992 Digital Equipment Corporation All Rights Reserved. Printed in the U.S.A. The postpaid READER'S COMMENTS form on the last page of this document requests the user's critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: CDA, DEC, DEC Distributed Server Library, DECnet, DECnet-DOS, DECserver, DECstation, DEC Storage Monitor, DECwindows, PATHWORKS, PATHWORKS for DOS, VAX, VAX Ada, VAX BASIC, VAX BLISS, VAX C, VAXcluster, VAX DOCUMENT, VAX FORTRAN, VAX MACRO, VAX NCP Utility, VAX Pascal, VAX PL/1, VAX Rdb/VMS, VAXstation, VMS running on a VAX system, VT, ULTRIX, and the DIGITAL logo. The following are third-party trademarks: EOS/D3, JVPM, and VOS/T are registered trademarks of U.S. Design. Kodak is a registered trademark of Eastman Kodak Company. LaserStar, LaserWare, and WORMS-11 are trademarks of Perceptics Corporation. MS-DOS, Microsoft C, and Microsoft are registered trademarks of Microsoft Corporation. Windows is a trademark of Microsoft Corporation. OptiFileII is a trademark of KOM, Inc. Perceptics is a registered trademark of Perceptics Corporation. X Window System is a trademark of the Massachusetts Institute of Technology. __________________________________________________________________ Contents ____________________________________________________________ PREFACE vii __________________________________________________________________ CHAPTER 1 PREPARING FOR INSTALLATION 1-1 ____________________________________________________________ 1.1 DEFINITIONS 1-1 ____________________________________________________________ 1.2 PREREQUISITE HARDWARE 1-1 ____________________________________________________________ 1.3 PREREQUISITE SOFTWARE 1-2 ____________________________________________________________ 1.4 LICENSE REGISTRATION 1-2 ____________________________________________________________ 1.5 INSTALLATION PROCEDURE REQUIREMENTS 1-3 1.5.1 Privileges and Disk Space ______________ 1-3 1.5.2 System Parameters ______________________ 1-5 1.5.2.1 Checking System Parameter Values o 1-6 1.5.2.2 Calculating the Values for GBLPAGES and GBLSECTIONS o 1-6 1.5.2.3 Changing System Parameter Values with AUTOGEN o 1-7 1.5.3 Process Account Quotas _________________ 1-8 1.5.4 VMSINSTAL Requirements _________________ 1-9 1.5.5 Backing Up Your System Disk ____________ 1-10 __________________________________________________________________ CHAPTER 2 INSTALLING THE STORAGE MONITOR 2-1 ____________________________________________________________ 2.1 THE INSTALLATION PROCEDURE 2-1 ____________________________________________________________ 2.2 ERROR RECOVERY 2-5 iii Contents __________________________________________________________________ CHAPTER 3 AFTER INSTALLING THE STORAGE MONITOR 3-1 ____________________________________________________________ 3.1 RUNNING THE INSTALLATION VERIFICATION PROCEDURE SEPARATELY 3-1 ____________________________________________________________ 3.2 EDITING THE SYSTEM FILES 3-1 ____________________________________________________________ 3.3 VAXCLUSTER CONSIDERATIONS 3-2 ____________________________________________________________ 3.4 PRIVILEGES 3-2 ____________________________________________________________ 3.5 ACCOUNT QUOTAS 3-3 ____________________________________________________________ 3.6 ENHANCING THE STORAGE MONITOR PERFORMANCE 3-3 ____________________________________________________________ 3.7 DETERMINING AND REPORTING PROBLEMS 3-3 __________________________________________________________________ APPENDIX A SAMPLE INSTALLATION PROCEDURES A-1 ____________________________________________________________ A.1 INSTALLATION FOR THE STORAGE MONITOR CLIENT A-1 ____________________________________________________________ A.2 INSTALLATION FOR THE STORAGE MONITOR SERVER A-5 __________________________________________________________________ APPENDIX B FILES RESULTING FROM THE INSTALLATION B-1 ____________________________________________________________ B.1 FILES CREATED BY THE STORAGE MONITOR INSTALLATION B-1 ____________________________________________________________ B.2 FILES CONTAINED IN THE STORAGE MONITOR SAVESETS B-4 iv Contents __________________________________________________________________ APPENDIX C VAX RDB/VMS UPDATE INFORMATION C-1 ____________________________________________________________ C.1 EDITING THE SQL$STARTUP.COM FILE C-1 __________________________________________________________________ APPENDIX D STORAGE MONITOR INSTALLATION MESSAGES D-1 __________________________________________________________________ INDEX __________________________________________________________________ EXAMPLES A-1 Sample Storage Monitor Installation Procedure for the Client Software ______________________ A-1 A-2 Sample Storage Monitor Installation Procedure for the Server Software ______________________ A-5 C-1 SQL$STARTUP.COM File Edits ___________________ C-1 __________________________________________________________________ TABLES 1-1 Disk Space Requirements ______________________ 1-3 1-2 Minimum Required System Parameter Values _____ 1-5 1-3 Process Account Quotas for the Installing Account ______________________________________ 1-8 B-1 Storage Monitor Client Installed Files _______ B-1 B-2 Storage Monitor Server Installed Files _______ B-2 v __________________________________________________________________ Preface This guide provides a description of how to perform the installation of the DEC Storage Monitor[TM] on the VMS operating system. __________________________________________________________________ Purpose This guide describes the preparation for installation, the installation of the software, and post-installation procedures. __________________________________________________________________ Intended Audience This guide is intended for the person responsible for installing the Storage Monitor software. That individual is assumed to have VMS system management experience. __________________________________________________________________ Manuals in the Storage Monitor Documentation Set In addition to this guide, the Storage Monitor documentation set includes the following books: o DEC Storage Monitor Operations and Management Guide o DEC Storage Monitor Programmer's Reference Manual o DEC Storage Monitor Installation Guide for Windows o DEC Storage Monitor Release Notes (available online) __________________________________________________________________ Document Structure This guide is organized as follows: o Chapter 1, Preparing for Installation, describes the operating system and hardware requirements for the Storage Monitor installation and related procedures that you complete before installing the Storage Monitor and includes a list of prerequisite hardware, software and storage requirements. o Chapter 2, Installing the Storage Monitor, contains instructions for installing the Storage Monitor on VMS systems. vii Preface o Chapter 3, After Installing the Storage Monitor, describes actions that you perform after installation. o Appendix A, Sample Installation Procedures, contains samples of installations for Storage Monitor. o Appendix B, Files Resulting from the Installation, contains a list of savesets for installation and files contained in the savesets. o Appendix C, VAX Rdb/VMS Update Information, contains information regarding the mandatory update to VAX Rdb/VMS and editing the SQL$STARTUP.COM file. o Appendix D, Storage Monitor Installation Messages, contains a list of messages which result from using the installation procedure and explanations of those messages. __________________________________________________________________ Conventions This document uses the following conventions: __________________________________________________________________ Ellipses Conventions Conventions______Meaning__________________________________________ . . . Horizontal ellipsis in examples indicates one of the following: o Additional optional arguments in a statement have been omitted o Preceding item or items can be repeated one or more times o Additional parameters, values, or other information can be entered In DECwindows screens, horizontal ellipsis indicate a dialog menu item. If you select a menu item that is followed by a horizontal ellipsis, the system displays another window. . Vertical ellipsis indicate the omission of . information from an example or program. The . information is omitted because it is not important to the topic being discussed. viii Preface __________________________________________________________________ Keyboard Conventions Conventions______Meaning__________________________________________ Text within a box identifies a key, such as the key. A sequence such as indicates that you must hold down the Ctrl key while you press another key or a pointing device button. This term means to type the information into a field or box and press the key. __________________________________________________________________ Naming Conventions Conventions______Meaning__________________________________________ Storage Monitor Refers to the DEC Storage Monitor VMS Read VMS to be OpenVMS throughout this document. __________________________________________________________________ Programming Conventions Conventions______Meaning__________________________________________ * The asterisk (*) character is the wildcard character in commands. [ ] Brackets enclose optional elements in commands. (Brackets are not optional, however, in the syntax of a directory name in a VMS file _________________specification.)__________________________________ __________________________________________________________________ Typographic Conventions Conventions______Meaning__________________________________________ Bold text This typeface identifies user input. Used in examples and system displays. Words may also be boldfaced for emphasis. Italics Italic text is used to introduce new terms and to emphasize important information. New terms are defined in the Glossary. lowercase In command descriptions, lowercase letters indicate command parameters that are to be monospace supplied by the user. System output and user input are displayed using this font. User input is displayed in monospaced bold font. UPPERCASE All commands, file specifications, and logical names, and most messages and system prompts are presented in uppercase letters. ix Preface __________________________________________________________________ Screen Prompt Conventions __________________________________________________________________ Screen Prompt Conventions Conventions______Meaning__________________________________________ $ The dollar sign is the default VMS operating system prompt. SM$DB> The default prompt used by the DEC Storage Monitors Database Editor command line interface. SM$OP> The DEC Storage Monitor's Operator command line _________________prompt.__________________________________________ x __________________________________________________________________ 1 Preparing for Installation This guide applies to Version 1.0 of the DEC Storage Monitor[TM] and all subsequent maintenance releases up to the next major product release. This chapter discusses the preparations and requirements necessary for installing the Storage Monitor (both client and server software). The Storage Monitor provides online release notes. It is strongly recommended 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 Definitions Client/Server In the context of a client/server application (like the Storage Monitor), there is one server program that provides a service, such as access to a shared database. There can be multiple client programs that use the service by accessing the server program. These clients all share the server. __________________________________________________________________ 1.2 Prerequisite Hardware This section lists the resources that are required to use the Storage Monitor. The Client application programming interface (API) portion of the Storage Monitor runs on all Digital VAX hardware systems unless otherwise specified. A jukebox is optional for the Storage Monitor configuration. If you intend to use a jukebox for optical storage, you must use one of the supported jukeboxes listed in the DEC Storage Monitor Software Product Description. 1-1 Preparing for Installation __________________________________________________________________ 1.3 Prerequisite Software This section lists the software required for the Storage Monitor. The Storage Monitor running on VMS requires that the following software products be installed: o VMS Version 5.4 or higher o DECnet-VAX Phase IV o VAX Rdb/VMS Version 4.0-2 or higher[1] Note: See Appendix C for information regarding the mandatory update to VAX Rdb/VMS and editing the SQL$STARTUP.COM file. __________________________________________________________________ 1.4 License Registration For V1.0 of Storage Monitor, you must register and load a license for the Storage Monitor. The Storage Monitor uses the License Management Facility (LMF). In order to run the Installation Verification Procedure (IVP) and use the software, you must register and load your license for the Storage Monitor before you start the installation. 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 the Storage Monitor 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.3. For complete information on using LMF, see the VMS License Management Utility Manual. ____________________ [1] Version 4.0 is required. It has known bugs. Version 4.0- 2 corrects the known bugs and is recommended by both the VAX Rdb/VMS and the DEC Storage Monitor Development Groups. 1-2 Preparing for Installation __________________________________________________________________ 1.5 Installation Procedure Requirements This section and those that follow discuss various requirements for installing the Storage Monitor. The installation takes approximately 15 to 45 minutes, depending on your media type and your system configuration. ___________________________ 1.5.1 Privileges and Disk Space To install the Storage Monitor, you must be logged in to an account that has SETPRV or at least one of the following privileges: o CMKRNL o WORLD o SYSPRV Note that VMSINSTAL turns off BYPASS privilege at the start of the installation. The Storage Monitor's requirements for free disk storage space are different during installation and after installation. Table 1-1 summarizes the storage requirements. Table_1-1_Disk_Space_Requirements_________________ Blocks Blocks After During Installa- Kit_(1.0)_________________Installation___tion_____ Storage Monitor Client 1,200 400 software (including the API) 1-3 Preparing for Installation Table_1-1_(Cont.)_Disk_Space_Requirements_________ Blocks Blocks After During Installa- Kit_(1.0)_________________Installation___tion_____ Storage Monitor Server 4,800 3,300[1] software (including the Storage Manager Server, Database Server, Cache Server, and Jukebox Server) Storage Monitor Cache 1,200 400 Manager Optical Disk Jukebox 30,000 30,000[2] Control Libraries __________________________________________________ [1]Note: The number of caches created depends upon the installer's requirements. The Storage Monitor servers use an Input Cache and Retrieval Cache by default. Allow 2,400 blocks for each cache created during installation (for example, multiply the number of caches by 2,400 blocks). Physical disk space used for caches should be sized according to operational and user requirements, based upon an average operational file size and the anticipated volume of file input and activity at the installation site. The following formula may be useful for planning disk space: 50,000 bytes average/image X 1,000,000 images = planned storage [2]This applies to configurations with a U.S. Design Jukebox Controller. Each control library (the volatile directory information per platter side) requires 30,000 blocks. Contiguous magnetic disk space must be planned for this at platter initialization time. __________________________________________________ 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-4 Preparing for Installation ___________________________ 1.5.2 System Parameters Installing the Storage Monitor requires certain system parameter settings. Table 1-2 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-2 Minimum Required System Parameter __________Values__________________________________ System Parameter Minimum Value _________Storage_Monitor_Client_Software__________ GBLPAGES[1] n + 750[2] GBLSECTIONS[1] n + 15[2] __________________________________________________ _________Storage_Monitor_Server_Software__________ GBLPAGES[1] n + 200[2] GBLSECTIONS[1] n + 10[2] __________________________________________________ [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. [2]This number represents an approximation of the number of global pages and global sections required for installation. To get a closer approximation of the number of global pages and global sections, use the DIR/SIZE SYS$LIBRARY:DCLTABLES.EXE command. Use the preliminary approximations and run the system. Then use the SYS$UPDATE:AUTOGEN.COM command procedure with the feedback option and add 10% to the values for global pages and global sections. __________________________________________________ The following sections show you how to: o Check system parameter values o Calculate values for the GBLPAGES and GBLSECTIONS system parameters o Change parameter values with the VMS AUTOGEN command procedure 1-5 Preparing for Installation _____________________ 1.5.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 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-2. 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.5.2.2 Calculating the Values for GBLPAGES and GBLSECTIONS To install and run the Storage Monitor, 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. If you need to change these values, then use AUTOGEN to increase the GLBPAGES and GBLSECTIONS system parameters. The n + 200 value for GBLPAGES and the n + 10 value for GBLSECTIONS in Table 1-2 indicate that you must have at least 200 unused global pages and 10 unused global sections available on your system for the installation to process successfully. If you are installing the Storage Monitor on a system running VMS Version 5.4 (or later), 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-2, 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-2, you must increase the system parameter setting. 1-6 Preparing for Installation Section 1.5.2.3 describes the procedures for increasing these values. _____________________ 1.5.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 = 1024 To modify incremental parameters such as GBLPAGES and GBLSECTS, use ADD_. The following example increases the global page setting by 2000: ADD_GBLPAGES = 2000 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 resources consumed 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-7 Preparing for Installation ___________________________ 1.5.3 Process Account Quotas The account you use to install the Storage Monitor must have sufficient quotas to enable you to perform the installation. Table 1-3 summarizes the process quotas required for the Storage Monitor installation account. Table 1-3 Process Account Quotas for the __________Installing_Account______________________ Storage Monitor Client Software Account __________Quota__________Value____________________ ASTLM 100 BIOLM 18 BYTLM 40000 DIOLM 18 ENQLM 600 FILLM 100 TQELM 50 __________________________________________________ Storage Monitor Server Software Account __________Quota__________Value____________________ ASTLM 100 BIOLM 18 BYTLM 40000 DIOLM 18 ENQLM 600 FILLM 100 __________TQELM__________50_______________________ 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 UAF> At the UAF> prompt, enter the SHOW command with an account name to check a particular account. For example: UAF> SHOW SMITH 1-8 Preparing for Installation 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=100 UAF> EXIT After you exit from UAF, 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.5.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 = 100 BIOLM = 18 BYTLM = 40000 DIOLM = 18 ENQLM = 600 FILLM = 100 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 the Return key. Then correct the problem and restart the installation. 1-9 Preparing for Installation ___________________________ 1.5.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. 1-10 __________________________________________________________________ 2 Installing the Storage Monitor This chapter explains how to install the Storage Monitor. Section 2.1 contains a step-by-step description of the installation procedure. __________________________________________________________________ 2.1 The Installation Procedure The Storage Monitor 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. 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. 1 Invoke VMSINSTAL. @SYS$UPDATE:VMSINSTAL saveset-name device-name The following list defines the elements of the VMSINSTAL command procedure: saveset-names The installation name for the component. For the Storage Monitor, use the following installation names: SEP_SMC V1.0 for the Storage Monitor Client software and SEP_SMS V1.0 for the Storage Monitor Server software device-name The name of the device on which you plan to mount the media. For example, MTA0: 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 drive, you should replace any media you removed once the installation is complete. 2-1 Installing the Storage Monitor 2 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 the Return key. Otherwise, enter NO to discontinue the installation. After you back up your system disk, you can restart the installation. 3 Mount the media. If you are not installing the Storage Monitor Client software from disk or over the network, do the following: Please mount the first volume of the set on MTA0:. * Are you ready? YES %MOUNT-I-MOUNTED, SMCLIENT MOUNTED ON _$$MTA0: (NODE 1) The following products will be processed: SEP_SMC V1.0 Beginning installation of SEP_SMC V1.0 at 17:01 %VMSINSTAL-I-RESTORE, Restoring product saveset A... If you are not installing the Storage Monitor Server software from disk or over the network, do the following: Please mount the first volume of the set on MTA0:. * Are you ready? YES %MOUNT-I-MOUNTED, SMS V1.0 MOUNTED ON _$$MTA0: (NODE 1) The following products will be processed: SEP_SMS V1.0 Beginning installation of SEP_SMS V1.0 at 17:01 %VMSINSTAL-I-RESTORE, Restoring product saveset A... 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 the Storage Monitor has been mounted on the specified device and that the installation has begun. 2-2 Installing the Storage Monitor 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. 4 Mount additional media volumes. If you are not installing from disk or over the network, do the following: %BACKUP-I-READYREAD, mount volume 2 on _MTA0: 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. 5 Review release notes. Note that hardcopy release notes are included with the documentation set for the Storage Monitor. VMSINSTAL displays the following: %VMSINSTAL-I-RELMOVED, The product's release notes have been successfully moved to SYS$HELP. 6 Purge files. * Do you want to purge files replaced by this installation [YES]? You have the option to purge files from previous versions of the Storage Monitor 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. 7 Choose the Installation Verification Procedure (IVP) option. * 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 the Storage Monitor checks to be sure that the installation is successful. It is recommended that you run the IVP. After the Storage Monitor is installed, you can run the IVP independently 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 the Storage Monitor. 2-3 Installing the Storage Monitor To run the IVP independently, use the following command: $ @SYS$TEST:SM$IVP.COM Note: The following question appears only in the Storage Monitor Server software installation procedure. 8 Respond to license registration queries. Product: SEP-SM-SERVER Producer: DEC Version: 1.0 Release Date: 08-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 Read informational messages. At this point, the installation procedure displays a number of informational messages that report on the progress of the installation. The system prompts you with further questions that are included in the example in Appendix A, Sample Installation Procedures. For the input required for these questions, refer to the Getting Started chapter of the DEC Storage Monitor Operations and Management Guide. 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. The following messages are displayed: %VMSINSTAL-I-MOVEFILES, files will now be moved to their target directories... 10 Observe the installation Verification Procedure (IVP). 2-4 Installing the Storage Monitor If you chose to run the IVP, VMSINSTAL runs it now. When the IVP runs successfully, you see the following display: 11 End the installation procedure. For the Storage Monitor Client software: Installation of SEP_SMC V1.0 completed at 11:10 VMSINSTAL procedure done at 11:10 For the Storage Monitor Server software: Installation of SEP_SMS V1.0 completed at 11:10 VMSINSTAL procedure done at 11:10 These messages indicate that the entire installation procedure is complete. You can now log out of the privileged account, type the following: $ LOGOUT SYSTEM logged out at 10-MAY-1992 11:10:20.00 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, for the Storage Monitor Client software you see the following message: %VMSINSTAL-E-INSFAIL, The installation of SEP_SMC V1.0 has failed. If the IVP fails, you see these messages: The SEP_SMC V1.0 Installation Verification Procedure failed. %VMSINSTAL-E-IVPFAIL, The IVP for SEP_SMC V1.0 has failed. If the installation fails for the Storage Monitor Server software, you see the following message: %VMSINSTAL-E-INSFAIL, The installation of SEP_SMS V1.0 has failed. If the IVP fails, you see these messages: The SEP_SMS V1.0 Installation Verification Procedure failed. %VMSINSTAL-E-IVPFAIL, The IVP for SEP_SMS V1.0 has failed. 2-5 Installing the Storage Monitor Errors can occur during the installation if any of the following conditions exist: o The operating system version is incorrect. o A prerequisite software 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. 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, Preparing for Installation. 2-6 __________________________________________________________________ 3 After Installing the Storage Monitor After you install the Storage Monitor, you need to perform the following tasks: o Run the Installation Verification Procedure separately. o Edit the system startup and shutdown files. o Modify the system parameter settings. o Make the product usable on a VAXcluster. o Set the account quotas. o Tailor your system. o Enhance performance. o Report problems. __________________________________________________________________ 3.1 Running the Installation Verification Procedure Separately You usually run the Installation Verification Procedure (IVP) during installation. If you want to run the IVP separately to ensure the integrity of installed files should system problems occur, execute the following command procedure: $ @SYS$TEST:SM$IVP.COM __________________________________________________________________ 3.2 Editing the System Files You must edit the system startup and shutdown files to provide for automatic startup and shutdown of the Storage Monitor when your system is rebooted. Add the command line that starts the Storage Monitor to the system startup file, SYS$MANAGER:SYSTARTUP_V5.COM. The Storage Monitor cannot start until after the network has started. You must position this new command line after the line that invokes the network startup command procedure. The following example shows the network startup command line followed by the Storage Monitor startup command line: 3-1 After Installing the Storage Monitor $ @SYS$MANAGER:STARTNET.COM . . . $ @SYS$STARTUP:SEP$STARTUP.COM The file SYS$STARTUP:SEP$STARTUP.COM has been provided to help with site specific customizations. __________________________________________________________________ 3.3 VAXcluster Considerations If you are on a cluster, you should execute the following commands: $ RUN SYS$SYSTEM:SYSMAN SYSMAN> SET ENVIRONMENT/CLUSTER SYSMAN> SET PROFILE/PRIVILEGE=(CMKRNL,SYSPRV,CMEXEC) - _/DEFAULT=SYS$COMMON: SYSMAN> DO @SYS$STARTUP:SM$STARTUP.COM SYSMAN> DO INSTALL REPLACE SYS$SHARE:DCLTABLES.EXE SYSMAN> EXIT This ensures that the installed components are available to all nodes of the cluster before the next system boot. Users who are currently logged in have to log out and then log back in to use the new DCL command tables. __________________________________________________________________ 3.4 Privileges To use the Storage Monitor each account must have at least the following VMS user account privileges: o TMPMBX o NETBMX Use the VMS Authorize Utility to determine whether users have the privileges they require. For the Storage Monitor, you should install the software from the system account. SM$SERVER.EXE is put on the known file list (through the VMS Install Utility, $INSTALL) with SYSNAM and SYSLCK privileges. 3-2 After Installing the Storage Monitor __________________________________________________________________ 3.5 Account Quotas User account process quotas for the Storage Monitor vary widely depending upon the size of the specific client programs developed by your users. Therefore, adjust the process quotas as needed. See Section 1.5.3 for a description of how to verify and change account quotas. __________________________________________________________________ 3.6 Enhancing the Storage Monitor Performance After you install the Storage Monitor, you might want to adjust your system to enhance performance or lower the use of some system resources. Information about tuning your system is included in the Guide to VMS Performance Management, AA- LA43A-TE manual (applicable to either the Client or the Server) and the VAX Rdb/VMS Guide to Database Maintenance and Performance, AA-N035D-TE (applicable to the Server only). __________________________________________________________________ 3.7 Determining and Reporting Problems If you encounter a problem while using the Storage Monitor software, report it to your Digital representative. Depending upon 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 Storage Monitor 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 your warranty. If you encounter a problem during the warranty period, report the problem as indicated above or follow alternate instructions provided by Digital for reporting SPD nonconformance problems. (See the DEC Storage Monitor Release Notes (online) for information on how to submit an SPR.) 3-3 __________________________________________________________________ A Sample Installation Procedures This appendix contains sample installations of the Storage Monitor. There is an example of the Storage Monitor Client software and an example of the Storage Monitor Server software. These sample installations were run on a system that had no previous version of the Storage Monitor installed. It is assumed that DECnet is shut down, that no users are logged on to your system, and that OPTIONS N is specified to print the release notes. The Installation Verification Procedure (IVP) runs at the end of the installation. __________________________________________________________________ A.1 Installation for the Storage Monitor Client Example A-1 contains a sample installation for the Storage Monitor Client software. Example A-1 Sample Storage Monitor Installation Procedure for the Client Software __________________________________________________________________ $ @SYS$UPDATE:VMSINSTAL VAX/VMS Software Product Installation Procedure V5.4-2 It is 5-JUN-1992 at 16:26. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? * Where will the distribution volumes be mounted: DISK$2:[SMITH] Enter the products to be processed from the first distribution volume set. * Products: SEP_SMC * Enter installation options you wish to use (none): The following products will be processed: SEP_SMC V1.0 __________________________________________________________________ Example A-1 (continued on next page) A-1 Sample Installation Procedures Example A-1 (Cont.) Sample Storage Monitor Installation Procedure for the Client Software __________________________________________________________________ Beginning installation of SEP_SMC V1.0 at 16:28 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. ***************************************************************************** * * * DEC Storage Monitor(TM) * * Copyright © Digital Equipment Corporation. 1992. All rights reserved. * * * ***************************************************************************** **** QUESTIONS FOR THE USER **** * Do you want to purge files replaced by this installation [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]? **** ALL QUESTIONS HAVE NOW BEEN ASKED **** 5 to 10 minutes is required to complete the DEC Storage Monitor Client software installation. %VMSINSTAL-I-RESTORE, Restoring product save set B ... +---------------------------------------------------+ | De-Installing DEC Storage Monitor images (if any) | | Please ignore any error messages. | +---------------------------------------------------+ +----------------------------------------------------+ | Linking DSLAPISHR.EXE, SMCMNSHR.EXE, SEPCMNSHR | +----------------------------------------------------+ %VMSINSTAL-I-RESTORE, Restoring product save set C ... +-----------------------+ | Linking SMAPISHR.EXE | +-----------------------+ +----------------------------------------------+ | Installing the Last of Storage Monitor Files | +----------------------------------------------+ ...cleaning up and closing files... __________________________________________________________________ Example A-1 (continued on next page) A-2 Sample Installation Procedures Example A-1 (Cont.) Sample Storage Monitor Installation Procedure for the Client Software __________________________________________________________________ +-------------------------------------------------------------------------+ | The following files were added to your system by this kit installation: | +-------------------------------------------------------------------------+ SMAPI.H SMAPI.OPT SMAPIENT.H SMAPISHR.EXE DSLAPISHR.EXE SEPCMNSHR.EXE SMCMNSHR.EXE SEP$STARTUP.COM SM$IVP.COM SM$SHUTDOWN.COM SM$STARTUP.COM +-------------------------------------------------------+ | To complete the DEC Storage Monitor installation, | | you must perform several additional steps: | | | | Add the command: $ @SYS$STARTUP:SEP$STARTUP | | to the file SYS$MANAGER:SYSTARTUP_V5.COM. | | | | Add the command: $ @SYS$MANAGER:SM$SHUTDOWN | | to the file SYS$MANAGER:SYSHUTDWN.COM. | | | +-------------------------------------------------------+ %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Executing SEP startup procedure ... Defining SEP logical names ... Starting Storage Monitor ... Installing Storage Monitor sharable images ... Defining Storage Monitor logical names ... Defining Storage Monitor caches CACHE DEFINITION LOGICALS ARE MISSING -- SERVERS WILL NOT BE STARTED. ... Providing Storage Monitor cache reference names CACHE REFERENCE LOGICALS ARE MISSING -- SERVERS WILL NOT BE STARTED. ... Starting Storage Monitor servers ***************************************************************** ** DEC Storage Monitor Installation Verification Procedure ** ***************************************************************** (LNM$SYSTEM_TABLE) "SEP$SYSTEM" = "SYS$COMMON:[SEP]" "SM$DATABASE" = "SM$DB_DIR:SM$DATABASE" "SM$DB_DIR" = "SEP$SYSTEM" __________________________________________________________________ Example A-1 (continued on next page) A-3 Sample Installation Procedures Example A-1 (Cont.) Sample Storage Monitor Installation Procedure for the Client Software __________________________________________________________________ ***************************************************************** ** DEC Storage Monitor Installation Successfully Verified. ** ***************************************************************** Installation of SEP_SMC V1.0 completed at 16:34 Enter the products to be processed from the next distribution volume set. * Products: VMSINSTAL procedure done at 16:34 $ __________________________________________________________________ A-4 Sample Installation Procedures __________________________________________________________________ A.2 Installation for the Storage Monitor Server Example A-2 contains a sample installation for the Storage Monitor Server software. Example A-2 Sample Storage Monitor Installation Procedure for the Server Software __________________________________________________________________ $ @SYS$UPDATE:VMSINSTAL VAX/VMS Software Product Installation Procedure V5.4-2 It is 5-JUN-1992 at 16:26. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? * Where will the distribution volumes be mounted: DISK$2:[SMITH] Enter the products to be processed from the first distribution volume set. * Products: SEP_SMS The following products will be processed: SEP_SMS V1.0 Beginning installation of SEP_SMS V1.0 at 16:40 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. ***************************************************************************** * * * DEC Storage Monitor(TM) * * Copyright © Digital Equipment Corporation. 1992. All rights reserved. * * * ***************************************************************************** **** QUESTIONS FOR THE USER **** * Do you want to purge files replaced by this installation [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]? You now have 2 choices. You are asked to specify which components of the DEC Storage Monitor should be installed. You may choose to install either one or the other of the following: __________________________________________________________________ Example A-2 (continued on next page) A-5 Sample Installation Procedures Example A-2 (Cont.) Sample Storage Monitor Installation Procedure for the Server Software __________________________________________________________________ All Servers Components (3350 Blocks) Storage Manager Server Storage Manager Database Server - controls Client access Cache Server - assists local and remote cache managers Cache Manager - manages the Central Input and Retreival caches Jukebox Server - (optional) manages optical disk drives Cache Manager Only (750 Blocks) * Do you want to install All Server Components [YES]? You have chosen to install All Server Components. * Is this correct [YES]? Product: SEP-SM-SERVER Producer: DEC Version: 1.0 Release Date: 08-SEP-1992 * Does this product have an authorization key registered and loaded?Y *************************************************************** This installation requires the creation of the SEP$SERVER account. You MUST enter a valid User Identification Code (UIC) for the server account. *************************************************************** * Enter UIC to be used for SEP$SERVER account (e.g. [300,2]): [123,456] Please specify a device and directory where the Storage Monitor files will be stored. * DEC Storage Monitor files directory [SYS$COMMON:[SEP]]: * Directory SYS$COMMON:[SEP] does not exist. Should it be created [YES]? A PREFIX is used to create the three cache REFERENCE (CRF) logicals: SM$CRF__INPUT_CACHE, SM$CRF__RETRIEVAL_CACHE, and SM$CRF__LOCAL_CACHE. The REFERENCE logicals point to the DEFINITION logicals. Example: SM$CRF_CENTRAL_INPUT_CACHE = SM$CDF_INPUT = 3, DISK1:[ROOT1], DISK2:[ROOT2], DISK3:[ROOT3] __________________________________________________________________ Example A-2 (continued on next page) A-6 Sample Installation Procedures Example A-2 (Cont.) Sample Storage Monitor Installation Procedure for the Server Software __________________________________________________________________ There is one PREFIX for each set of Storage Monitor components. The PREFIX is passed into the Storage Manager Server in its startup command line. The PREFIX is also part of the client connect handshake to ensure that Client and Server will use the same magnetic caches. * Specify the Storage Monitor PREFIX for this installation [CENTRAL]: PREFIX: CENTRAL * Is this correct [YES]? Magnetic Cache Definitions: The next series of questions allow you to define the magnetic caches used by Storage Monitor components you have chosen to install. If this is a reinstallation or software update, these caches may already be defined, in which case you may wish to skip the questions regarding magnetic caches. Please reference the DEC Storage Monitor Operations and Management Guide. * Do you wish to supply Cache Definitions now [YES]? CENTRAL CACHE DEFINITIONS: You will now be asked to define the INPUT and RETRIEVAL caches. You have specified a PREFIX which is used to create the cache REFERENCE (CRF) logicals: SM$CRF__INPUT_CACHE, SM$CRF__RETRIEVAL_CACHE, and SM$CRF__LOCAL_CACHE. You will be asked a series of questions for each cache beginning with the cache NAME used to create the cache DEFINITION (CDF) logical: SM$CDF_. Then you will be asked to specify the devices and root directories for the cache. The result is a two level set of logicals defining the caches. In the following example, has the default value of "CENTRAL", and the default for an INPUT cache is "INPUT". SM$CRF_CENTRAL_INPUT_CACHE = SM$CDF_INPUT = 3, DISK1:[ROOT1], DISK2:[ROOT2], DISK3:[ROOT3] * What is the NAME of your INPUT cache [INPUT]: INPUT cache NAME you chose is: INPUT. * Is this correct [YES]? * Number of root directories (volumes) in the INPUT cache [1]: * Device and Directory for root 1: DUA1:[CACHE1] The device and directory you entered is: DUA1:[CACHE1]. * Is this correct [YES]? A Cache Manager monitors available blocks on each cache volume. A "Free Space Desired Goal" and a "Free Space Warning Limit" must be supplied, as well as an "Interval" in minutes, between caches. __________________________________________________________________ Example A-2 (continued on next page) A-7 Sample Installation Procedures Example A-2 (Cont.) Sample Storage Monitor Installation Procedure for the Server Software __________________________________________________________________ * Free space desired goal (# blocks) per cache volume? [500000]: * Free space warning limit (# blocks) per cache volume? [100000]: * Time between Cache Manager purges (in minutes)? [120]: * What is the NAME of your RETRIEVAL cache [RETRIEVAL]: RETRIEVAL cache NAME you chose is: RETRIEVAL. * Is this correct [YES]? * Number of root directories (volumes) in the RETRIEVAL cache [1]: * Device and Directory for root 1: DUA1:[CACHE2] The device and directory you entered is: DUA1:[CACHE2]. * Is this correct [YES]? A Cache Manager monitors available blocks on each cache volume. A "Free Space Desired Goal" and a "Free Space Warning Limit" must be supplied, as well as an "Interval" in minutes, between caches. * Free space desired goal (# blocks) per cache volume? [500000]: * Free space warning limit (# blocks) per cache volume? [100000]: * Time between Cache Manager purges (in minutes)? [120]: * What is the NAME of your LOCAL cache (example: LOCAL): LOCAL LOCAL cache NAME you chose is: LOCAL. * Is this correct [YES]? * Number of root directories (volumes) in the LOCAL cache [1]: * Device and Directory for root 1: DUA1:[CACHE3] The device and directory you entered is: DUA1:[CACHE3]. * Is this correct [YES]? A Cache Manager monitors available blocks on each cache volume. A "Free Space Desired Goal" and a "Free Space Warning Limit" must be supplied, as well as an "Interval" in minutes, between caches. * Free space desired goal (# blocks) per cache volume? [500000]: * Free space warning limit (# blocks) per cache volume? [100000]: * Time between Cache Manager purges (in minutes)? [120]: Optical Disc Device Definitions: The next series of questions allow you to define the optical disk devices (or jukeboxes) used by Storage Monitor components you have chosen to install. If this is a reinstallation or software update, these optical disk devices may already be defined, in which case you may wish to skip the questions regarding optical disk devices. Please reference the Storage Monitor Operations and Management Guide. * Do you wish to define optical disk devices now [YES]? You will now be asked about each JUKEBOX to be served. * Name to assign to the first JUKEBOX: JB1 __________________________________________________________________ Example A-2 (continued on next page) A-8 Sample Installation Procedures Example A-2 (Cont.) Sample Storage Monitor Installation Procedure for the Server Software __________________________________________________________________ The following question applies to jukeboxes that use U.S. Design device driver software, but not those that use Perceptics software. * Configuration File for jukebox JB1 [None]: * Jukebox type for JB1 jukebox (examples: KODAK6800, CYGNET): CYGNET * First device name on jukebox JB1 (examples: ODA0, JBA0):JBA0 If a jukebox holds 50 platters, and there are 2 volumes or devices per platter, then it has a total of 100 volumes or devices. * Total number of volumes or devices on jukebox JB1 [0]: 100 * Number of physical read/write drives in jukebox JB1 [1]: 2 * Accessible platter sides when inserted in jukebox JB1 [2]: 2 The following jukebox data were defined: Jukebox: JB1 Jukebox Type: CYGNET Jukebox Config File: Jukebox Devices: JBA0 - JBA99 Jukebox Drives: 2 Jukebox Access Sides: 2 * Is this correct? [Y/N]? Y * Name to assign to next JUKEBOX [Done]: **** ALL QUESTIONS HAVE NOW BEEN ASKED **** 10 to 20 minutes is required to complete the DEC Storage Monitor Server software installation. If caches are created as part of this installation, a batch procedure, SM$INSTALL_CACHES.COM, will be submitted to SYS$BATCH. This procedure will require 15 to 30 minutes to create each cache root. +-------------------------------------------------------------+ | Creating a user account for the DEC Storage Monitor servers | +-------------------------------------------------------------+ %SEP-I-ACCOUNT, This installation creates an account named SEP$SERVER. %UAF-I-ADDMSG, user record successfully added %UAF-I-RDBADDMSGU, identifier SEP$SERVER value: [000123,000456] added to rights data base %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named SEP$SERVER. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named SEP$SERVER. %UAF-I-MDFYMSG, user record(s) updated __________________________________________________________________ Example A-2 (continued on next page) A-9 Sample Installation Procedures Example A-2 (Cont.) Sample Storage Monitor Installation Procedure for the Server Software __________________________________________________________________ +---------------------------------------------------------------------+ | Creating the SEP$SYSTEM directory for the DEC Storage Monitor files | +---------------------------------------------------------------------+ %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$COMMON:[SEP]. %VMSINSTAL-I-RESTORE, Restoring product save set B ... +------------------------------------------------------+ | Creating the DEC Storage Monitor startup procedures. | +------------------------------------------------------+ +---------------------------------------------------+ | De-Installing DEC Storage Monitor images (if any) | | Please ignore any error messages. | +---------------------------------------------------+ +----------------------------------------------------+ | Linking DSLAPISHR.EXE, SMCMNSHR.EXE, SEPCMNSHR | +----------------------------------------------------+ %VMSINSTAL-I-RESTORE, Restoring product save set C ... %VMSINSTAL-I-RESTORE, Restoring product save set D ... +-----------------+ | Linking Servers | +-----------------+ +-----------------------------------+ | Creating Storage Monitor Database | | This may take 5 to 10 minutes. | +-----------------------------------+ +----------------------------------------------+ | Installing the Last of Storage Monitor Files | +----------------------------------------------+ ...cleaning up and closing files... +-------------------------------------------------------------------------+ | The following files were added to your system by this kit installation: | +-------------------------------------------------------------------------+ __________________________________________________________________ Example A-2 (continued on next page) A-10 Sample Installation Procedures Example A-2 (Cont.) Sample Storage Monitor Installation Procedure for the Server Software __________________________________________________________________ SM$CM_MAIN.EXE SM$CS_MAIN.EXE SM$DB_MAIN.EXE SM$DBE_MAIN.EXE SM$JB_MAIN.EXE SM$SM_MAIN.EXE SM$OP_MAIN.EXE SM$DBE_HELP.HLB SM$OP_HELP.HLB SM$DATABASE.RDB SM$DATABASE.SNP SM$DB_INITIALIZE.SM$DB SM$DB_INSTALL.LOG SM$DB_INSTALL.SM$DB SM$DB_SAMPLE.SM$DB DSLAPISHR.EXE SEPCMNSHR.EXE SMCMNSHR.EXE SEP$STARTUP.COM SM$IVP.COM SM$SHUTDOWN.COM SM$STARTUP.COM SM$DCL.CLD SM$DCL.HLP SM$MAKE_CACHE_ROOT.COM SM$MAKE_CACHE_ROOT_NOACL.COM SM$SERVER_STARTUP.COM SM$JB_SUB.COM SM$INSTALL_CACHES.COM SM$DEFINE_CACHES.COM SM$REFERENCE_CACHES.COM SM$CMSRVR_001.INP SM$CSSRVR_001.INP SM$DBSRVR_001.INP SM$SMSRVR_001.INP SM$JBSRVR_001.INP __________________________________________________________________ Example A-2 (continued on next page) A-11 Sample Installation Procedures Example A-2 (Cont.) Sample Storage Monitor Installation Procedure for the Server Software __________________________________________________________________ +-------------------------------------------------------+ | To complete the DEC Storage Monitor installation, | | you must perform several additional steps: | | | | Add the command: $ @SYS$STARTUP:SEP$STARTUP | | to the file SYS$MANAGER:SYSTARTUP_V5.COM. | | | | Add the command: $ @SYS$MANAGER:SM$SHUTDOWN | | to the file SYS$MANAGER:SYSHUTDWN.COM. | | | +-------------------------------------------------------+ %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... +--------------------------+ | Creating the Cache roots | +--------------------------+ %SEP_SMS-I-CRECACHE, SM$INSTALL_CACHES.COM to create the caches has been submitted. Executing SEP startup procedure ... Defining SEP logical names %DCL-I-SUPERSEDE, previous value of SEP$SYSTEM has been superseded ... Starting Storage Monitor ... Installing Storage Monitor sharable images ... Defining Storage Monitor logical names %DCL-I-SUPERSEDE, previous value of SM$DB_DIR has been superseded %DCL-I-SUPERSEDE, previous value of SM$DATABASE has been superseded ... Defining Storage Monitor caches ... Providing Storage Monitor cache reference names ... Starting Storage Monitor servers %RUN-S-PROC_ID, identification of created process is 00000098 %RUN-S-PROC_ID, identification of created process is 00000099 %RUN-S-PROC_ID, identification of created process is 0000009A %RUN-S-PROC_ID, identification of created process is 0000009B %RUN-S-PROC_ID, identification of created process is 0000009D ***************************************************************** ** DEC Storage Monitor Installation Verification Procedure ** ***************************************************************** (LNM$SYSTEM_TABLE) __________________________________________________________________ Example A-2 (continued on next page) A-12 Sample Installation Procedures Example A-2 (Cont.) Sample Storage Monitor Installation Procedure for the Server Software __________________________________________________________________ "SEP$SYSTEM" = "SYS$COMMON:[SEP]" "SM$CDF_INPUT" = "1" = "DUA1:[CACHE1]" "SM$CDF_LOCAL" = "1" = "DUA1:[CACHE3]" "SM$CDF_RETRIEVAL" = "1" = "DUA1:[CACHE2]" "SM$CRF_CENTRAL_INPUT_CACHE" = "SM$CDF_INPUT" "SM$CRF_CENTRAL_LOCAL_CACHE" = "SM$CDF_LOCAL" "SM$CRF_CENTRAL_RETRIEVAL_CACHE" = "SM$CDF_RETRIEVAL" "SM$DATABASE" = "SM$DB_DIR:SM$DATABASE" "SM$DB_DIR" = "SEP$SYSTEM" ***************************************************************** ** DEC Storage Monitor Installation Successfully Verified. ** ***************************************************************** Installation of SEP_SMS V1.0 completed at 17:07 Enter the products to be processed from the next distribution volume set. * Products: $ __________________________________________________________________ A-13 __________________________________________________________________ B Files Resulting from the Installation This appendix contains the names of the files that result from the installation of the DEC Storage Monitor on a VMS system and the files contained in the savesets. __________________________________________________________________ B.1 Files Created by the Storage Monitor Installation Table B-1 lists the files that are created as a result of the Storage Monitor Client installation on a VMS system. Table_B-1_Storage_Monitor_Client_Installed_Files__ File_Name______________Description________________ SMAPI.H Contains the Client and Operator API C language programming definitions. SMAPI.OPT Contains the linker opeions file for the API. SMAPIENT.H Contains the Client and Operator API C language function prototypes. DSLAPISHR.EXE Contains the DEC Distributed Server Library shareable executable image. SEPCMNSHR.EXE Contains the SEP common routine shareable executable image. SMCMNSHR.EXE Contains the Storage Monitor common routine shareable executable image. SMAPISHR.EXE Contains the Storage Monitor API sharable _______________________image._____________________ Table B-2 lists the files that are created as a result of the Storage Monitor Server installation on a VMS system. B-1 Files Resulting from the Installation Table_B-2_Storage_Monitor_Server_Installed_Files__ File_Name______________Description________________ SM$CM_MAIN.EXE Contains the Cache Manager executable image. SM$CS_MAIN.EXE Contains the Cache Server executable image. SM$DB_MAIN.EXE Contains the Database Server main executable. SM$DBE_MAIN.EXE Contains the Database Server Editor main executable. SM$JB_MAIN.EXE Contains the Jukebox Server executable image. SM$SM_MAIN.EXE Contains the Storage Manager executable image. SM$OP_MAIN.EXE Contains the Operator Interface main executable. SM$DBE_HELP.HLB Contains the Database Server DCL Help files. SM$OP_HELP.HLB Contains the Operator Interface DCL Help files. SM$DATABASE.RDB Contains the VAX Rdb/VMS file. SM$DATABASE.SNP Contains the VAX Rdb/VMS snapshot file. SM$DB_ Loads mandatory data to INITIALIZE.SM$DB the Database Server. SM$DB_INSTALL.LOG Contains a log of the initialization of the Database Server. SM$DB_INSTALL.SM$DB Contains database additions regarding the caches. SM$DB_SAMPLE.SM$DB Contains a sample Database Editor file. DSLAPISHR.EXE Contains the DEC Distributed Server Library shareable executable image. SEPCMNSHR.EXE Contains the SEP common routine shareable executable image. B-2 Files Resulting from the Installation Table B-2 (Cont.) Storage Monitor Server __________________Installed_Files_________________ File_Name______________Description________________ SMCMNSHR.EXE Contains the Storage Monitor common routine shareable executable image. SEP$STARTUP.COM Starts the Storage Monitor environment. SM$IVP.COM Runs the Installation Verification Procedure (IVP). SM$SHUTDOWN.COM Shuts down the Storage Monitor environment. SM$STARTUP.COM Installs the server images as shared images. SM$DCL.CLD Contains the Storage Monitor DCL directories. SM$DCL.HLP Contains DCL Help files. SM$MAKE_CACHE_ Constructs defined caches. ROOT.COM SM$MAKE_CACHE_ROOT_ Constructs defined caches. NOACL.COM SM$SERVER_STARTUP.COM Starts the server processes. SM$JB_SUB.COM Starts the jukebox server subprocesses. SM$INSTALL_CACHES.COM Creates the caches specified during installation. SM$DEFINE_CACHES.COM Defines the cache definition logicals (CDFs). SM$REFERENCE_ Defines the cache CACHES.COM reference logicals (CRFs). SM$CMSRVR_001.INP Contains the Cache Manager startup command. SM$CSSRVR_001.INP Contains the Cache Server startup command. SM$DBSRVR_001.INP Contains the Storage Monitor Database Server startup command. SM$SMSRVR_001.INP Contains the Storage Manager Server startup command. B-3 Files Resulting from the Installation Table B-2 (Cont.) Storage Monitor Server __________________Installed_Files_________________ File_Name______________Description________________ SM$JBSRVR_001.INP Contains the Jukebox _______________________Server_startup_command.____ __________________________________________________________________ B.2 Files Contained in the Storage Monitor Savesets There are four savesets files for the Storage Monitor on a VMS system. They contain the following files. o SEP_SMS010.A includes the following files: SEP_SM010.RELEASE_NOTES KITINSTAL.COM SM$SERVER_KITINSTAL.COM or SM$CLIENT_KITINSTAL.COM SMAPI.H SMAPIENT.H o SEP_SM010.B includes the following files: SEP$STARTUP.COM SM$STARTUP.COM SM$SHUTDOWN.COM SM$DCL.CLD SM$DCL.HLP SM$MAKE_CACHE_ROOT.COM SM$MAKE_CACHE_ROOT_NOACL.COM SM$JB_SUB.COM SM$IVP.COM DSLAPI.OLB DSLAPISHR.OPT SMCMN.OLB SMCMNSHR.OPT SM$CO_LIBR.OPT SM$CO_SHARE.OPT SM$DSL_LIBR.OPT SM$DSL_SHARE.OPT o SEP_SM010.C includes the following files: SMAPI.OPT SMAPI.OLB SMAPISHR.OPT o SEP_SM010.D includes the following files: SM$SERVER.OLB SM$DB_MAIN.OPT SM$JB_MAIN.OPT SM$SM_MAIN.OPT SM$CS_MAIN.OPT B-4 Files Resulting from the Installation SM$CM_MAIN.OPT SM$DBE_MAIN.OPT SM$DB_INITIALIZE.SM$DB SM$DB_SAMPLE.SM$DB SM$DB_SETACLS.RDO SM$DBE_HELP.HLB SM$OP_MAIN.OPT SM$OP_HELP.HLB B-5 __________________________________________________________________ C VAX Rdb/VMS Update Information This appendix contains information regarding the mandatory system upgrade to VAX Rdb/VMS 4.0-2. When upgrading the system, the SQL$STARTUP.COM file must be edited. __________________________________________________________________ C.1 Editing the SQL$STARTUP.COM File When upgrading to VAX Rdb/VMS 4.0-2, the following edits described in Example C-1 must be made to SQL$STARTUP.COM to ensure that the SQL$INT.EXE file is installed on system startup. Example C-1 SQL$STARTUP.COM File Edits __________________________________________________ $! $! This command procedure can deinstall all of the SQL images. If you $! have enabled installing the images in your startup, you should add $! the line $! $! $@sys$startup:sql$startup stop 1 $! $! to your system shutdown file and remove the GOTO EXIT_PROC command $! immediately following this comment. This procedure will then deinstall $! SQL images. $! $!!!!!! goto exit_proc 2 $ say "SQL: Removing SQL images" $ goto image_loop $! $ins_images: $! $! $! This command procedure can install all of the images used by SQL. $! Installing the SQL images will require 23 global sections $! and approximately 3084 global pages. To have this command procedure $! install the SQL images, remove the GOTO EXIT_PROC which follows $! this comment. $! $!!!!!! goto exit_proc 2 $ say "SQL: Installing SQL images" $! $image_loop: $! __________________________________________________ Example C-1 (continued on next page) C-1 VAX Rdb/VMS Update Information Example C-1 (Cont.) SQL$STARTUP.COM File Edits __________________________________________________ $ install :== $install/command $! $!_De-install_any_old_versions_of_SQL_____________ When you have edited the SQL$STARTUP.COM file, it should look like this example. 1 Add this line of code to the SYSHUTDOWN.COM file. 2 This line of code should be commented out as shown. C-2 __________________________________________________________________ D Storage Monitor Installation Messages The Storage Monitor sends messages to the system managers/operators during the installation procedure. This appendix contains all the Storage Monitor Installation Messages. ABTCACHEDEF, Aborting the definition of this cache Severity: Informational Explanation: This message indicates that you typed when asked about a cache. As a result of this action, the definition of this cache is aborted. User Action: If you typed in error, redefine the cache. BADNUMCACHE, The number of roots per cache must be from 1 to 126 Severity: Warning Explanation: This message indicates that the number of roots supplied did not fall within the range of numbers between 1 and 126. User Action: Supply a number for the roots that is within the range of 1 to 126. BADVMS, Storage Monitor requires VMS Version 5.4 or a higher version. Severity: Error Explanation: This message indicates you are attempting to install the Storage Monitor on an outdated version of the VMS operating system that is not supported by the Storage Monitor. User Action: Upgrade the VMS operating system to Version 5.4 or higher and then install the Storage Monitor. CMSRVRINS, The Cache Manager will also be installed. Severity: Informational Explanation: This message indicates that whenever you install the central servers, you always get the Cache Manager. User Action: None. D-1 Storage Monitor Installation Messages CRECACHE, The caches have all been created. Severity: Informational Explanation: This message indicates that cache creation is completed. User Action: None. DUPCACHE, Cache was already selected for management Severity: Error Explanation: This message indicates that you are telling the Cache Manager to manage a cache that was previously specified. User Action: Do not specify the same cache twice. DUPRIGHTID, [] was already specified for this cache it is not being added again to the cache ACL Severity: Error Explanation: This message indicates that the rights identifier specified for this cache is duplicated. User Action: Do not specify the same rights identifier twice. JBNAMTOOLONG, Jukebox names are restricted to 31 characters or less Severity: Error Explanation: This message indicates that the specified name for the jukebox is too long (exceeds 31 characters). User Action: Specify a name for the jukebox that is no longer than 31 characters. MISRIGHTID, [SEP$SERVER] is an unknown rights identifier - Caches cannot be created Severity: Warning Explanation: This message indicates the [SEP$SERVER] identifier used by the Storage Monitor Central Servers does not exist. User Action: Create the [SEP$SERVER] identifier and then create the caches. D-2 Storage Monitor Installation Messages MNGCACHE, Selecting cache: to be managed Severity: Informational Explanation: This message indicates that the named cache will be managed by the Cache Manager. User Action: None. MUSTSELCACHE, You must select some cache(s) to be managed Severity: Error Explanation: This message indicates that you must specify at least one cache to be managed by the Cache Manager. User Action: Specify at least one cache to be managed by the Cache Manager. NOJBCONFIG, The file does not exist, it should be created. Severity: Warning Explanation: This message indicates that the configuration file name does not exist. User Action: Create the file. NONEXCACHE, Root does not exist Severity: Informational Explanation: This message indicates that the cache root does not exist. User Action: Create the cache root. NOTCLUMBR, is not a member of this VAXcluster Severity: Error Explanation: This message indicates that the node name specified to run the server is not currently in the cluster. User Action: Choose a node to run the server that is currently running in the cluster. D-3 Storage Monitor Installation Messages NOTNETNODE, Node not found in network node list Severity: Error Explanation: This message indicates that the node name specified is not on the network's known node list. User Action: Add the node to the known node list using NCP. RDBREQ, SEP_SM Central Servers require RDB. You may abort the installation or respecify which components to install. Severity: Error Explanation: This message indicates that if you intend to run the Storage Monitor central servers, you must first install VAX Rdb/VMS. User Action: If you want to install the central servers, you must install VAX Rdb/VMS, and then install the servers. SYSUIC, You have selected a SYSTEM UIC for the SEP$SERVER account. Severity: Warning Explanation: This message indicates that you must choose a different UIC for the central servers and the Cache Manager. User Action: Choose a UIC group greater than MAXSYSGROUP. UNKCACHE, No cache called was defined. Change this cache reference Severity: Warning Explanation: This message indicates that the cache name specified was never defined. User Action: Select a cache name that was already defined. UNKRIGHTID, [Identifier] is an unknown rights identifier it is not being added to the cache ACL Severity: Error Explanation: This message indicates that an unknown rights identifier was specified. The D-4 Storage Monitor Installation Messages rights identifier is being ignored. User Action: Specify only existing rights identifiers. D-5 _________________________________________________________________ Index _______________________________ A FilenamesoB-1 _______________________________ Files Account created by the Storage privilegeso3-2 Monitor installationo process quotaso1-8 B-1 AUTOGENo1-7 editing the system fileso3-1 _______________________________ _______________________________ B G _______________________________ _______________________________ Backup GBLPAGESo1-6 system disko1-10 GBLSECTIONSo1-6 _______________________________ _______________________________ C H _______________________________ _______________________________ Calculating Hardware values for GBLPAGES and requirementso1-1 GBLSECTIONSo1-6 _______________________________ Changing I values for system parameters _______________________________ with AUTOGENo1-7 Installation Checking system parameter descriptiono2-1 valueso1-6 filesoB-1 Client minimum required system definitiono1-1 parameter valueso1-5 _______________________________ preparationo1-1 D procedureo1-3, 2-1, A-1 _______________________________ procedure for the Storage Definition Monitor clientoA-1 cliento1-1 procedure for the Storage servero1-1 Monitor serveroA-5 Disk spaceo1-3 requirementso1-3 requirementso1-3 savesetsoB-4 verificationo3-1 _______________________________ VMSINSTALo2-1 E Installation messagesoD-1 _______________________________ IVP Editing for Storage Monitoro3-1 system fileso3-1 running the procedureo3-1 Error Recoveryo2-5 _______________________________ _______________________________ M F _______________________________ _______________________________ Messages installationoD-1 Index-1 Index _______________________________ P Sample (cont'd) _______________________________ installation procedure for Parameters the Storage Monitor server checking valueso1-6 oA-5 Performanceo3-3 Saveset Prerequisite for the Storage Monitoro2-1 hardwareo1-1 Server softwareo1-2 definitiono1-1 Privilegeso1-3 Software accounto3-2 prerequisiteso1-2 Problems requirementso1-2 reportingo3-3 SQL$STARTUP.COM Procedure editingoC-1 installationoA-1 Storage Monitor installation for the Storage account privilegeso3-2 Monitor clientoA-1 audienceovii installation for the Storage installingo2-1 Monitor serveroA-5 IVPo3-1 IVPo3-1 license registrationo1-2 IVP for Storage Monitoro3-1 manualsovii Process post-installationo3-1 quotaso1-8, 3-3 savesetsoB-4 Storage Monitor client _______________________________ sample installationoA-1 Q Storage Monitor filesoB-1 _______________________________ Storage Monitor server Quotas sample installationoA-5 for process accounto1-8 System processo3-3 editing fileso3-1 tuningo3-3 _______________________________ System disk R backupo1-10 _______________________________ System parameterso1-5 Reporting checking valueso1-6 problemso3-3 setting valueso1-7 Requirements System parameter valueso1-5 disk spaceo1-3 _______________________________ for VMSINSTALo1-9 hardwareo1-1 T softwareo1-2 _______________________________ systemo1-1 Tuning the systemo3-3 _______________________________ S _______________________________ _______________________________ V Sample _______________________________ installation procedureoA-1 Values installation procedure for calculating GBLPAGES and the Storage Monitor client GBLSECTIONSo1-6 oA-1 changing system parameters with AUTOGENo1-7 Index-2 Index Values (cont'd) checking system parameterso 1-6 VAXclustero3-2 Verify the installation procedureo 3-1 VMSINSTAL installationo2-1 requirementso1-9 Index-3