Storage_Library_System_for_OpenVMS__________________ Installation Guide Order Number: AA-KY16M-TE Abstract This document contains information for installing the Storage Library System for OpenVMS (SLS) software. Revision/Update Information: This revised document supersedes the previous release of this document (Order Number AA-KY16L-TE). Software Version: Storage Library System For OpenVMS Version 2.8A ________________________________________________________________ January 1997 Possession, use, or copying of the software described in this documentation is authorized only pursuant to a valid written license from Digital, an authorized sublicenser, or the identified licenser. While Digital believes the information included in this publication is correct as of the date of publication, it is subject to change without notice. Digital Equipment Corporation makes no representations that the interconnection of its products in the manner described in this document will not infringe existing or future patent rights, nor do the descriptions contained in this document imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. © Digital Equipment Corporation 1995, 1996, 1997. All Rights Reserved. Printed in the United States of America. Alpha, DCL, DECnet, Digital UNIX, eXcursion, OpenVMS, OpenVMS Cluster, StorageWorks, VAXTPU, VAX, VMS, and the DIGITAL logo are all trademarks of Digital Equipment Corporation. AIX is registered trademark of International Business Machines Corporation. FTP Software is a trademark of FTP SOFTWARE, INC. HP is a registered trademark of Hewlett-Packard Company. Motif is a registered trademark of the Open Software Foundation, Inc. NT is a trademark of Microsoft Corporation. Oracle, Oracle Rdb, and Oracle RMU are all registered trademarks of Oracle Corporation. PostScript is a registered trademark of Adobe Systems, Inc. RDF is a trademark of Touch Technologies, Inc. SGI is a registered trademark of Chemical Bank. Solaris is a registered trademark of Sun Microsystems, Inc. StorageTek is a registered trademark of Storage Technology Corporation. SunOS is a trademark of Sun Microsystems, Inc. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Ltd. Windows and Windows NT are both trademarks of Microsoft Corporation. X Window System is a trademark of Massachusetts Institute of Technology. All other trademarks and registered trademarks are the property of their respective holders. This document was prepared using VAX DOCUMENT, Version 2.1. ___________________________________________________________ Contents ................................................... v Installing SLS Preinstallation Process.......................... 1-1 Quotas and OpenVMS Operating System Classes...... 1-2 Required Quotas ............................... 1-2 Required OpenVMS Operating System Classes ..... 1-2 Hardware Requirements............................ 1-3 Client and Server Definitions.................... 1-5 Server Software .............................. 1-5 Client Software .............................. 1-6 Software Requirements............................ 1-6 Server Software Requirements .................. 1-7 Client Software Requirements .................. 1-7 Optional Software ............................. 1-7 Shutting Down the Previous Version of SLS Software......................................... 1-8 Registering the SLS Software License............. 1-8 License and Kit Names ......................... 1-9 Unloading the Current SLS License ............. 1-9 Registering Your New SLS License .............. 1-11 the SLS Software Before You Begin-Questions and Answers........... 2-1 Installing the SLS Software...................... 2-2 iii After Installing SLS 3.1 Verifying the Installation....................... 3-1 3.2 Editing the Systemwide Command Files............. 3-2 3.2.1 Automatically Starting SLS .................... 3-2 3.2.2 Defining Global Symbols for SLS Users ......... 3-2 3.3 Preparing SLS Server Software.................... 3-2 3.3.1 Defining a Network Object on an OpenVMScluster System......................................... 3-3 3.3.2 Authorizing SLS Volume Database and Pool Access......................................... 3-5 3.4 Configuring SLS to Work With Specific VMS Versions......................................... 3-6 3.4.1 Version-Specific Files ........................ 3-6 3.5 Upgrading from a Previous Version................ 3-7 3.5.1 Reviewing Outdated Files from SLS$CUSTOM ...... 3-8 3.5.2 Updating the Command File TAPESTART.COM ....... 3-9 3.6 Configuring Media and Device Support............. 3-10 3.7 Configuring Remote Device Facility Support....... 3-10 3.7.1 Adding RDF Client Support ..................... 3-11 3.7.2 Adding RDF Server Support ..................... 3-11 SLS Server Installation Example Log File SLS Client Installation Example Log File Files and Logical Names C.1 Files............................................ C-1 C.2 Logical Names.................................... C-23 SLS Account User Authorization Data D.1 Authorization Data............................... D-1 A-1 SLS Server Installation Log-Part 1 ............ A-1 A-2 SLS Server Installation Log-Part 2 ............ A-4 C-1 Sample List of LNM$SLS$VALUES Entries ......... C-26 1-1 Preinstallation Tasks ......................... 1-1 1-2 Verifying Disk Space Requirements ............. 1-4 1-3 How to Start DECnet and OpenVMS Queue Manager........................................ 1-7 1-4 Software License Names ........................ 1-9 1-5 How to Unload the Server or Client Software License........................................ 1-9 1-6 How to Register Your SLS Server or Client License........................................ 1-11 2-1 Installation Questions and Answers ............ 2-2 2-2 How to Install the SLS Server or Client Software....................................... 2-2 3-1 How to Define the SLS$DBX NCP Object .......... 3-3 3-2 How to Enable Client Node Access to the SLS Volume Database................................ 3-5 3-3 SLS Files for Specific OpenVMS Versions ....... 3-7 3-4 How to Update the Command File TAPESTART.COM .. 3-9 C-1 Files Installed on Server Nodes ............... C-1 C-2 Files Installed on Client Nodes .............. C-14 C-3 Logical Name Table Entries .................... C-24 C-4 Unload Drive Logicals ......................... C-32 D-1 SLS Account User Authorization Data ........... D-1 v ______________________________________________________________ Preface of This Document This document contains information about installing Storage Library System for OpenVMS[TM] software. You can read the online release notes after completing the installation procedure by entering the following command: $ TYPE SYS$HELP:SLS028A.RELEASE_NOTES Audience This manual is intended for experienced OpenVMS[TM] system managers and storage administrators. It should be used with the System Management Subkit of the OpenVMS documentation set. Structure This document is organized in the following manner and includes the following information: Chapter 1 Identifies required software and hardware and explains tasks you need to perform before you install the SLS software. Chapter 2 Contains detailed instructions for installing SMF software. Chapter 3 Explains tasks you need to perform after you install the SLS software. Appendix A Shows a sample SLS server installation. Appendix B Shows a sample SLS client installation. Appendix C Lists SLS files and logical names. v Appendix D Lists SLS quota and account information. Documents The following documents are related to this documentation set or are mentioned in this manual: o Media and Device Management Services for OpenVMS Guide to Operations o Storage Library System for OpenVMS Guide to Backup and Restore Operations o OpenVMS System Management Utilities Reference Manual: A-L o OpenVMS DCL Dictionary: A-M o OpenVMS DCL Dictionary: N-Z o OpenVMS License Management Utility Manual o OpenVMS User's Manual The following conventions are used in this guide: ___________________________________________________________ Convention__Description____________________________________ { } In format command descriptions, braces indicate required elements. You must include one of the elements. [ ] Square brackets show optional elements in command syntax. You can omit these elements if you wish to use the default response. . . . Horizontal ellipsis points indicate the omission of information from a sentence or paragraph that is not important to the topic being discussed. ___________________________________________________________ Convention__Description____________________________________ Vertical ellipsis points indicate the omission . of information from an example or command . format. The information has been omitted . because it is not important to the topic being discussed. boldface Boldface type in text indicates the first type instance of terms defined in the Glossary or in text. italic Italic type emphasizes important information, type indicates variables, indicates complete titles of manuals, and indicates parameters for system information. Starting This type font denotes system response, user test . . . input, and examples. Ctrl/x Hold down the key labeled Ctrl (Control) and the specified key simultaneously (such as Ctrl /Z). PF1 x The key sequence PF1 x indicates that you press and release the PF1 key, and then you press and release another key (indicated here by x). n A lowercase italic n indicates the generic use of a number. For example, 19nn indicates a four-digit number in which the last two digits are unknown. x A lowercase italic x indicates the generic use of a letter. For example, xxx indicates any ____________combination_of_three_alphabetic_characters.____ Products The following related products are mentioned in this document: ___________________________________________________________ Product_______Description__________________________________ ABS ABS refers to Archive/Backup System for OpenVMS[TM] software. vii ___________________________________________________________ Product_______Description__________________________________ ABS OMT ABS OMT refers to Archive/Backup System for OpenVMS Management Tools[TM] software. HSM HSM refers to HSM for OpenVMS software. MDMS MDMS refers to Media and Device Management Services for OpenVMS software. OpenVMS Refers to the OpenVMS operating system. SMF SMF refers to Sequential Media Filesystem for OpenVMS software. SLS SLS refers to Storage Library System for ______________OpenVMS_software.____________________________ and Reporting Problems If you encounter a problem while using SLS, report it to Digital through your usual support channels. 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. 1 ______________________________________________________________ Before Installing SLS This chapter lists hardware and software requirements and explains how to register the SLS license. Preinstallation Process This section describes what you need to do before you run the SLS, Version 2.8A installation procedure. Table 1-1 identifies actions you need to take to prepare for installing the SLS, Version 2.8A server software (which provides all SLS functionality) or client software (which provides most SLS functionality, except for the media databases). Later sections of this chapter provide details. Table_1-1__Preinstallation_Tasks___________________________ Stage_Action_______________________________________________ 1 Verify required quotas and OpenVMS operating system classes. ___________________________________________________________ 2 Check that the system on which you intend to install SLS meets hardware and software requirements. ___________________________________________________________ 3 Shut down previous versions of SLS software on all nodes of the cluster on which SLS software will be installed. ___________________________________________________________ (continued on next page) Before Installing SLS 1-1 Table_1-1_(Cont.)__Preinstallation_Tasks___________________ Stage_Action_______________________________________________ 4 Delete all existing SLS jobs from batch queues. If you do not, the jobs will try to run using the old SYSBAK.COM and will fail. ___________________________________________________________ 5_____Register_the_SLS_license.____________________________ Quotas and OpenVMS Operating System Classes Before beginning the installation process: 1. Log in to the SYSTEM account. 2. Enable all privileges. 3. Verify that the required quotas and OpenVMS classes are present. Required Quotas If your SYSTEM account quotas are the same as or higher than the default values provided with the OpenVMS operating system, then these values should be sufficient to install SLS software. More_information: Refer to the OpenVMS Upgrade and Installation Procedures manual for further information. Required OpenVMS Operating System Classes Verify that the following OpenVMS operating system classes are resident on the system disk: o Network support o Programming support o Secure user's environment o System programming environment o Utilities o OpenVMS required save set How_to_verify: Before Installing SLS For information about verifying these classes, refer to the Guide to Setting Up an OpenVMS System. Hardware Requirements For a detailed list of supported hardware for the SLS, Version 2.8A product, see the Storage Library System for OpenVMS Software Product Description/Software Support Addendum. The following are the minimum hardware requirements for installing SLS, Version 2.8A software: o A VAX[TM], MicroVAX[TM], VAXstation[TM], or Alpha AXP[TM] system o Four megabytes of memory for VAX, or sixteen megabytes of memory for Alpha AXP o One or more tape devices or optical disks, for stand- alone systems o One disk, such as a Digital RD-[TM] or RA-[TM] series disk o Disk space: Use the steps in Table 1-2 to ensure there is enough disk space to install SLS server or client software. Before Installing SLS 1-3 Table_1-2__Verifying_Disk_Space_Requirements_______________ Step__Action_______________________________________________ 1 Verify that there are enough free blocks on the disk where you are installing SLS software by entering the command: $ SHOW DEVICE SYS$SYSDEVICE _____________________________________________________ IF you are in- stalling . . . ______________RDF__THEN_you_need_._._._______________ Server Yes 10,800 peak blocks during software installation 8,400 net blocks after installation (permanent) No 10,200 peak blocks during installation 7,800 net blocks after installation (permanent) _____________________________________________________ Client Yes 10,800 peak blocks during software installation 8,400 net blocks after installation (permanent) No 10,200 peak blocks during installation 7,800 net blocks after ___________________installation_(permanent)__________ ___________________________________________________________ 2_____Note_the_disk_name_where_SLS_will_be_installed.______ Warning: If your system is monitored by the Audit facility, then you must consider the system disk free block requirements. To determine this requirement, enter the command: Before Installing SLS $ SHOW AUDIT/ALL Client and Server Definitions This section introduces SLS's concepts of client software and server software. You need to understand these distinctions before you install the SLS software on your system. Server Software SLS server software gives users access to the full functionality of SLS software. SLS provides this access at the node or OpenVMScluster system where the SLS software is executing. You install SLS server software on the server node. SLS server software manages the: o Media database-A set of RMS files that describe all removable storage media known to SLS software. These files are part of the Media and Device Management Services for OpenVMS (MDMS) portion of the SLS product. For detailed information about the MDMS databases, see the Media and Device Management Services for OpenVMS Guide to Operations. A node or OpenVMScluster system executing SLS server software provides media management services both for itself and for any client nodes connected to it. The media database contains information about volume names, locations, magazines, tape jukeboxes, and pool access authorization. o SLS history files-Information is recorded at the local node about user files backed up or archived under SLS control. Requirement: To use the SLS product, you must have at least one SLS server license in the network. Before Installing SLS 1-5 Client Software SLS client software: o Provides backup scheduling and archiving services for the node or OpenVMScluster system on which it is executing o Acts as a client of another node executing SLS server software when it requires media management services o Provides users with full functionality when a node or OpenVMScluster system executing SLS client software is communicating with another node or OpenVMScluster system executing SLS server software Similar to the SLS server software, SLS client software also maintains history files in which it records information about user files backed up or archived locally under its control. The node executing SLS client software communicates using DECnet software to a server node running SLS server software. The server node maintains the media database. Requirement: To use media management services, each SLS client node must be connected to a server node executing SLS server software. Any number of SLS client nodes may be connected to a single SLS server node. Software Requirements The following software is required to install either SLS, Version 2.8A server or client software: o OpenVMS VAX operating system, Version 5.5-2 through 6.2, or OpenVMS AXP operating system, Version 6.1 through 6.2. o DECnet[TM] communications software, Version 5.4 or later Before Installing SLS Server Software Requirements Before you install the server software, check to see that the DECnet software and the OpenVMS Queue Manager are running. If they are not running, follow the steps in Table 1-3 to start them. Table_1-3__How_to_Start_DECnet_and_OpenVMS_Queue_Manager___ Step__Action_______________________________________________ 1 Start the DECnet software. Enter the following command at the DCL prompt: $ @SYS$MANAGER:STARTNET ___________________________________________________________ 2 Start the OpenVMS Queue Manager. Enter the following command at the DCL prompt: ______$_START/QUEUE/MANAGER________________________________ Client Software Requirements Before you install client software, the node on which you intend to install the SLS client software must be registered on the SLS server node. If it is not, the IVP fails. For more information, see Section 3.3.2. Optional Software o DCSC (Digital Cartridge Server Component) If you have a StorageTek Automated Cartridge Server (ACS[TM]), you must install the DCSC software and load the SLS-ACS license to use the ACS with SLS software. License_name: SLS-ACS o RDF (Remote Device Facility) SLS, Version 2.8A software provides optional installation of Remote Device Facility (RDF) software. During installation of the SLS software, you are asked if you want to access tape devices on a remote system or if you want to allow remote backups to tape devices on this system. RDF software is installed automatically if you answer YES to either question. Before Installing SLS 1-7 Shutting Down the Previous Version of SLS Software If you are running a previous version of SLS, then shut down SLS on all nodes in the cluster before installing the new version of SLS server or client software. Shut down the SLS software with the following command: $ @SLS$SYSTEM:SLS$SHUTDOWN ________________________ Note ________________________ Due to changes in functionality and database structure, SLS software versions 2.5B and 2.6 are incompatible with SLS software version 2.4A or earlier. If you are an existing SLS customer, and upgrade SLS on your server node to version 2.5 or higher, then you must also upgrade each of your client nodes to version 2.5 or higher. This requirement results from a change in the format of the common magazine database in SLS software version V2.5B. ______________________________________________________ You might also need to check the batch queues to see if any SLS jobs exist. If so, you need to delete the existing SLS jobs from the batch queues. Registering the SLS Software License If you are installing SLS server or client software for the first time, you must register the SLS software license. The following sections describe: o License and kit names o How to unload a previous license o How to register the server or client software license Before Installing SLS License and Kit Names Refer to Table 1-4 for the license and kit names for the server or client software. Table_1-4__Software_License_Names__________________________ Software Type________License_Name_____Software_Kit_Name_____________ Server SLS SLSA028 Client SLS-REMOTE SLSCLIENTA028 ACS SLS-ACS None. Although you load the ACS license separately, SLS support for ACS installs as part of the standard _____________________________installation_process._________ Unloading the Current SLS License If your existing SLS license has a termination date, follow the steps in Table 1-5 to unload the current SLS software license. After completing this procedure, you may register the new SLS server or client software license. 1-5 How to Unload the Server or Client Software License______________________________________________________________ Enter the command for the appropriate Action software type:______________________________________________________________ Obtain the Server: authorization $ LICENSE LIST SLS/FULL key value for the previous SLS software license. Client: $ LICENSE LIST SLS-REMOTE/FULL (continued on next page) Before Installing SLS 1-9 1-5 (Cont.) How to Unload the Server or Client Software License______________________________________________________________ Enter the command for the appropriate Action software type:______________________________________________________________ Examine the display for a license with a status of "Active" and write down the value associated with the key authorization field. ______________________________________________________________ Cancel the previous Server: SLS software $ LICENSE CANCEL SLS/AUTHORIZATION=key_value - license. /TERMINATION=YESTERDAY Client: $ LICENSE CANCEL SLS- REMOTE/AUTHORIZATION=key_value - /TERMINATION=YESTERDAY ______________________________________________________________ Disable the previous_Server: SLS software $ LICENSE DISABLE SLS/AUTHORIZATION=key_value license. Client: $ LICENSE DISABLE SLS- REMOTE/AUTHORIZATION=key_value ______________________________________________________________ Unload the previous Server: SLS software $ LICENSE UNLOAD SLS license. (continued on next page) Before Installing SLS 1-5 (Cont.) How to Unload the Server or Client Software License______________________________________________________________ Enter the command for the appropriate Action software type:______________________________________________________________ Client: $ LICENSE UNLOAD SLS-REMOTE______________________________________________________________ Registering Your New SLS License If you need to register the new SLS license, follow the steps in Table 1-6 to register your new SLS license. Where_to_find_registration_information: The license registration information is contained in the Product Authorization Key (PAK). The PAK is a certificate shipped with the SLS package. Table_1-6__How_to_Register_Your_SLS_Server_or_Client_License Enter the command for the Step_Action_____________________appropriate_software_type:_ 1 Enter the LICENSE Server: REGISTER command with $ LICENSE REGISTER SLS - the product name and a dash. Important: Client: Enter a dash at the end $ LICENSE REGISTER SLS- of each command in steps REMOTE - 1 through 8. Remember: To use SLS with a StorageTek ACS, you must also register the SLS-ACS license. ___________________________________________________________ (continued on next page) Before Installing SLS 1-11 Table 1-6 (Cont.) How to Register Your SLS Server or Client ___________________License_________________________________ Enter the command for the Step_Action_____________________appropriate_software_type:_ 2 Enter the /ISSUER Server_or_Client: qualifier information, _$ /ISSUER="DEC" - assigning the value DEC between quotation marks. ___________________________________________________________ 3 Enter the /AUTHORIZATION Server_or_Client: qualifier information, _$ /AUTHORIZATION=xxxxxxx - assigning it the value from the AUTHORIZATION NUMBER entry of the PAK. ___________________________________________________________ 4 Enter the /PRODUCER Server_or_Client: qualifier information, _$ /PRODUCER="DEC" - assigning the value DEC in quotes. ___________________________________________________________ 5 Enter the /UNITS Server_or_Client: qualifier information, _$ /UNITS=nn - assigning the value from the UNITS entry of the PAK. ___________________________________________________________ 6 Enter the /DATE Server_or_Client: qualifiers information, _$ /DATE=dd-mmm-yyyy - assigning the product's release date value from the PRODUCT RELEASE DATE entry of the PAK. ___________________________________________________________ (continued on next page) Before Installing SLS Table 1-6 (Cont.) How to Register Your SLS Server or Client ___________________License_________________________________ Enter the command for the Step_Action_____________________appropriate_software_type:_ 7 Enter the /AVAILABILITY Server_or_Client: qualifier information, _$ /AVAILABILITY=x - assigning the value from the AVAILABILITY TABLE CODE entry of the PAK. ___________________________________________________________ 8 Enter the /OPTIONS Server_or_Client: qualifier information, _$ /OPTIONS=xxxxxx - assigning the value from the KEY OPTIONS entry of the PAK. ___________________________________________________________ 9 Enter the /CHECKSUM Server_or_Client: qualifier information, _$ /CHECKSUM=1-xxxx-xxxx- assigning the value from xxxx-xxxx the CH entry of the PAK. Important: Do NOT end the entry with a dash. ___________________________________________________________ 10 Invoke the LICENSE LOAD Server: command with the product $ LICENSE LOAD SLS name. Client: ________________________________$_LICENSE_LOAD_SLS-REMOTE__ Before Installing SLS 1-13 2 ______________________________________________________________ Installing the SLS Software This chapter describes how to install SLS, Version 2.8A software. For an example server installation, see Appendix A. For an example client installation, see Appendix B. ___________________ Recommendation ___________________ We recommend you perform a backup of your system disk before you install SLS software. Refer to the OpenVMS Backup Utility Manual for more details. ______________________________________________________ _________________ Existing SLS Users _________________ SLS Version 2.8A software (client and server) is not compatible with any previous versions of SLS prior to version 2.5. If any node in a client-server configuration is running a version later than 2.5, then all nodes in the configuration must be running the same version or higher. An exception can be made if none of the SLS nodes serve a SLS$MAGAZINE_MASTER_ FILE.DAT datbase. ______________________________________________________ Before You Begin-Questions and Answers Before beginning the installation procedure, you may want to go over the following questions and answers: Installing the SLS Software 2-1 Table_2-1__Installation_Questions_and_Answers______________ Q: How long will the installation procedure take? A: The installation procedure will take 15-30 minutes on a VAX system and 5-10 minutes on an Alpha AXP system. Q: How can I get help? A: VMSINSTAL provides additional information about the decisions required to respond to the installation prompts. To get help at any installation prompt, enter < ? > and press . Q: Where can I find an example of the installation procedure? A: Appendix A contains an example of an installation procedure for the server software. Appendix B contains an example of an installation procedure for the client software. Q: How can I abort the installation procedure? A: Enter . Note: If you abort the VMSINSTAL procedure, you must restart ___the_installation_from_the_beginning.____________________ Installing the SLS Software Follow the steps in Table 2-2 to install SLS server or client software. Table_2-2__How_to_Install_the_SLS_Server_or_Client_Software Step_Action________________________________________________ 1 Load and mount the media that contains the software kit. ___________________________________________________________ (continued on next page) Installing the SLS Software Table 2-2 (Cont.) How to Install the SLS Server or Client ___________________Software________________________________ Step_Action________________________________________________ 2 Invoke the VMSINSTAL procedure. Depending upon the type software you are installing, enter the one of the following commands: ______________________________________________________ IF you are installing the_._._.___THEN_enter_the_command:___________________ Server software $@SYS$UPDATE:VMSINSTAL SLSA028 location: OPTIONS N Client software $@SYS$UPDATE:VMSINSTAL SLSCLIENTA028 location: OPTIONS N Where: location is the tape device (or directory) that contains the software kit save set. OPTIONS N is an optional parameter that tells SLS to ask you to choose Release Notes options. The default behavior is to ____________move_the_Release_Notes_to_SYS$HELP._______ ___________________________________________________________ 3 If you see the following messages: %VMSINSTAL-W- ACTIVE, The following processes are still active . . . * Do you want to continue anyway [NO]? Enter Y and press . ___________________________________________________________ (continued on next page) Installing the SLS Software 2-3 Table 2-2 (Cont.) How to Install the SLS Server or Client ___________________Software________________________________ Step_Action________________________________________________ 4 Confirm the state of the system backup. * Are you satisfied with the backup of your system disk [YES]? Press . Digital recommends you perform a full backup of your system disk before installing any software product. ___________________________________________________________ 5 If you did not include the location for the software to be mounted in the VMSINSTAL command line, identify the location for the software to be mounted. * Where will the distribution volumes be mounted: SLS$KITS: You may specify a tape drive, a local disk, or a remote disk. Enter the appropriate information and press . ___________________________________________________________ 6 Respond to the 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]: Enter the number of the desired option and press . ___________________________________________________________ 7 Continue the installation. * Do you want to continue the installation [NO]? Enter Y and press . ___________________________________________________________ (continued on next page) Installing the SLS Software Table 2-2 (Cont.) How to Install the SLS Server or Client ___________________Software________________________________ Step_Action________________________________________________ 8 If SLS is already installed on this system, verify that you want to install this version of SLS software. The installation procedure displays the following message: ************************************************************************ * WARNING * ************************************************************************ * * * SLS V2.8A (client and server) is not compatible with any previous * * versions of SLS prior to V2.5. All nodes running SLS which interact* * with each other should also be upgraded to V2.5 or above. * * * ************************************************************************ * Do you want to continue with this installation [No]? System nodes running SLS Version 2.8A software can interact with nodes running SLS Version 2.5 software. Enter Y and press if you are upgrading all nodes to SLS Version 2.8A or if some nodes are running SLS Version 2.5. If your configuration involves nodes running SLS Version 2.4 software or earlier, press to terminate the installation. ___________________________________________________________ (continued on next page) Installing the SLS Software 2-5 Table 2-2 (Cont.) How to Install the SLS Server or Client ___________________Software________________________________ Step_Action________________________________________________ 9 Select to run the Installation Verification Procedure (IVP). * Do you want to run the IVP after the installation [YES]? Press to run the IVP, else enter No and press . Recommendation: Running the IVP procedure is recommended. ___________________________________________________________ 10 Confirm the PAK registration. * Does this product have an authorization key registered and loaded? Enter Y and press . If you did not register and load the license, as explained in Section 1.7, abort the installation and do so before continuing. ___________________________________________________________ 11 Purge old SLS software files if you want to recover storage space on your disk. Custom_files: If you are upgrading from a previous version of SLS software and you have files in the SLS$ROOT:[CUSTOM] directory, these files will be placed in a directory created by the VMSINSTAL procedure. Refer to Section 3.5.1. * Do you want to purge files replaced by this installation [YES]? Press to purge old files, else enter No and press . ___________________________________________________________ (continued on next page) Installing the SLS Software Table 2-2 (Cont.) How to Install the SLS Server or Client ___________________Software________________________________ Step_Action________________________________________________ 12 Client_software_only: You need to know the name of the SLS server node or the OpenVMScluster system alias name. * Are you ready to proceed? [YES]? * What is the name or VMScluster system alias of the SLS server node: Enter the name or OpenVMScluster system alias name of the SLS server node. ___________________________________________________________ 13 RDF_(Remote_Device_Facility)_software: If you want to use the RDF software, then respond Yes to the following queries: * Do you want to backup disks on this system to a drive on a remote system? Enter Yes to use RDF client functionality, else enter No. _________________________________________________ * Do you want to allow remote backups access to the tape drives on this system? Enter Yes to use RDF server functionality, else enter No. ___________________________________________________________ 14 Specify the disk device name where SLS software will reside. * Enter the name of the disk device the SLS software will use [DUA0:]: Enter the name of the device you noted in Section 1.3 and press . ___________________________________________________________ (continued on next page) Installing the SLS Software 2-7 Table 2-2 (Cont.) How to Install the SLS Server or Client ___________________Software________________________________ Step_Action________________________________________________ 15 Enter the directory name where SLS software will reside: * Enter the name of the directory the SLS software will use [SLS$FILES]: Enter the directory name and press . ___________________________________________________________ 16 Specify the directory names where the summary and log files will reside. * Where to place summary files from system backups [SLS$ROOT:[SYSBAK.SUMMARY_FILES]]: * Where to place intermediate history files [SLS$ROOT:[SYSBAK.TEMP_HISTORY]]: * Where to place maintenance log files [SLS$ROOT:[SYSBAK.MAINTENANCE_LOGS]]: * Where to place system backup log files [SLS$ROOT:[SYSBAK.SYSBAK_LOGS]]: Choose one of the following options in response to the above queries: o Press to choose the default directory location []. o Enter SLS$ROOT:[SYSBAK] to retain the location of SLS Version 2.1 or earlier. o Enter the directory location of your choice. If you choose to provide a different directory location, the SLS installation will take somewhat longer than usual because it will need to move the files. ___________________________________________________________ (continued on next page) Installing the SLS Software Table 2-2 (Cont.) How to Install the SLS Server or Client ___________________Software________________________________ Step_Action________________________________________________ 17 Select to automatically move existing log and summary files. If you have been using earlier versions of SLS software, there will be log files and summary files resident in SLS$SYSBAK from previous system backups. This installation procedure has the ability to automatically distribute these old files into the directories you have specified. * Do you want to automatically move these old files? [Y]? Press to move the files, else enter No to retain the files in SLS$SYSBAK. ___________________________________________________________ 18 Identify the SLS manager account UIC. If you see the following message: * Enter the UIC for the SLS manager account. [[1,21]] Press , else, continue. ___________________________________________________________ 19 Enter and verify the SLS account password. Restriction: The password must be at least 15 and no more than 31 characters. * Password: * Verify password: ___________________________________________________________ (continued on next page) Installing the SLS Software 2-9 Table 2-2 (Cont.) How to Install the SLS Server or Client ___________________Software________________________________ Step_Action________________________________________________ 20 Update quotas and flags for the SLS account. 1. The installation procedure automatically updates the SLS account process quotas if the SLS account already exists. (See Appendix D for detailed information about quotas.) When you see the following message: * Do you wish to update these quotas now [YES]? Updating quotas is recommended. Enter the quota values and press . Result: Updating the SLS process account quotas causes the Authorize utility to run. ______________________________________________________ 2. Update flags for the SLS account. Recommendation: When you see the following message: * Do you wish to update these flags now [YES]? Updating flags is recommended. Enter the flag values and press . Result: Choosing to update the flags causes the Authorize utility to run. ___________________________________________________________ 21 At this point, the installation proceeds without _____further_operator_intervention.________________________ Installing the SLS Software 3 ______________________________________________________________ After Installing SLS After installing the SLS server or client software, you must prepare it for configuration. This chapter explains how to do the following post installation activities: o Verifying the installation o Making the SLS software available on a systemwide basis o Defining a network object on an OpenVMScluster system (server software only) o Upgrading SLS to comply with changes to OpenVMS version o Upgrading from a previous version of SLS software o Configuring media and device support for SLS o Configuring SLS for Remote Device Facility (RDF) support Verifying the Installation The Installation Verification Procedure (IVP) may be executed as part of the installation procedure by responding YES to the question * Do you want to run the IVP after the installation [YES]? If you did not execute the IVP during the installation procedure, then execute it immediately after installing the SLS software by entering the command: $ @SYS$TEST:SLS$IVP Requirements: o The SLS software must be running on the system where the IVP is executed. o When executing the IVP on a SLS client node, the client node must have access to the SLS server node. After Installing SLS 3-1 Editing the Systemwide Command Files To ensure SLS functions properly, you need to edit the system startup procedure and the system login file. Automatically Starting SLS To ensure the SLS software starts up each time the system is booted, edit the system startup procedure, SYS$MANAGER:SYSTARTUP_V5.COM or SYS$MANAGER:SYSTARTUP_VMS.COM for OpenVMS Version 6.0. Add the following line: $ @SYS$STARTUP:SLS$STARTUP Note: Include the startup line after the STARTNET command in the SYSTARTUP_x.COM file. If you are using DECnet-Plus, make sure the SLS$STARTUP command entry appears before the call @SYS$MANAGER:NET$NCP_APPLICATIONS.COM. Defining Global Symbols for SLS Users To define symbols for SLS software users, edit the system login file, SYS$MANAGER:SYLOGIN.COM. Add the following line: $ @SYS$MANAGER:SLS$TAPSYMBOL Note: Include the symbol line in a section of the SYLOGIN.COM file that is executed by all accounts. If SLS$TAPSYMBOL.COM is not run, users will be unable to access the SLS menus. Preparing SLS Server Software If you have installed SLS server software for the first time, then you must: o Define a network object on your OpenVMScluster system nodes. o Authorize SLS volume database and pool access. After Installing SLS Defining a Network Object on an OpenVMScluster System Follow the steps in Table 3-1 to define the SLS$DBX NCP object. Requirement: If you intend to implement the high-availability features of SLS software, all nodes that participate in the OpenVMScluster system alias must have the SLS$DBX NCP object defined. Table_3-1__How_to_Define_the_SLS$DBX_NCP_Object____________ Step_Action________________________________________________ 1 From an account with BYPASS privilege, on the node on which SLS software was just installed, invoke the Network Control Program (NCP) utility by entering the command: $ RUN SYS$SYSTEM:NCP ___________________________________________________________ 2 Obtain the password for the SLS account: NCP> SHOW OBJECT SLS$DBX CHARACTERISTICS Result: Object Volatile Characteristics as of 2-MAY-1996 13:08:15 Object = SLS$DBX Number = 0 File id = SYS$SYSTEM:SLS$FIND_DB_NODE.EXE User id = SLS Password = password Note: The password is displayed only when the BYPASS privilege is enabled. ___________________________________________________________ 3 Exit the NCP utility: NCP> EXIT (continued on next page) After Installing SLS 3-3 Table_3-1_(Cont.)__How_to_Define_the_SLS$DBX_NCP_Object____ Step_Action________________________________________________ ___________________________________________________________ 4 Invoke the SYSMAN utility: $RUN SYS$SYSTEM:SYSMAN ___________________________________________________________ 5 Set the SYSMAN environment to include the OpenVMScluster system nodes that participate in the DECnet OpenVMScluster system alias. Participating_nodes: The participating nodes in an OpenVMScluster can be all of the nodes or only some of the nodes. To identify the participating nodes, use one of the following commands: o To identify all nodes . . . SYSMAN> SET ENVIRONMENT /CLUSTER o To identify some specific nodes . . . SYSMAN> SET ENVIRONMENT /NODE=(node_1,node_2,...node_n) ___________________________________________________________ 6 Define the SLS$DBX object with this command: SYSMAN>DO MCR NCP DEFINE OBJECT SLS$DBX NUMBER 0 USER SLS - _SYSMAN> FILE SYS$SYSTEM:SLS$FIND_DB_NODE.EXE PASSWORD password Rule: The password entered with this command must be the same as the password used for the SLS account during installation. ___________________________________________________________ 7 Read the SLS$DBX object on the node: SYSMAN> DO MCR NCP SET KNOWN OBJECT ALL ___________________________________________________________ (continued on next page) After Installing SLS Table_3-1_(Cont.)__How_to_Define_the_SLS$DBX_NCP_Object____ Step_Action________________________________________________ 8 Exit the SYSMAN utility: _____SYSMAN>_EXIT__________________________________________ Authorizing SLS Volume Database and Pool Access You need to run SLS$SYSTEM:SLS$SLSMGR.EXE to authorize access to: o SLS server database for SLS client nodes o SLS pools for SLS users Follow the steps in Table 3-2 to enable client node access to the SLS volume database. Table 3-2 How to Enable Client Node Access to the SLS ___________Volume_Database_________________________________ Step_Action________________________________________________ 1 On the SLS server node, access the SLS Storage Administrator Menu with the following DCL command: $ RUN SLS$SYSTEM:SLS$SLSMGR ___________________________________________________________ 2 Select the Database Access Authorization option from the numeric keypad: Enter < 3 > and press . ___________________________________________________________ 3 Invoke the record insertion feature from the numeric keypad. Press keypad < 8 > or Press . ___________________________________________________________ (continued on next page) After Installing SLS 3-5 Table 3-2 (Cont.) How to Enable Client Node Access to the ___________________SLS_Volume_Database_____________________ Step_Action________________________________________________ 4 Enter the name of the client node(s) in the Node field and press . Result: The list of client nodes is displayed with the new entry or entries. ___________________________________________________________ 5 Save the changes to the database: Enter Y and press _____._____________________________________________ For more information, see Chapter 6 of the Media and Device Management Services for OpenVMS Guide to Operations. Configuring SLS to Work With Specific VMS Versions SLS, Version 2.8A operates on systems running OpenVMS VAX Versions 5.5-2 through 6.2 and OpenVMS AXP Versions 6.1 through 6.2. Three SLS files are dependent on the OpenVMS VAX version running on the system. When SLS is installed, the OpenVMS VAX version is checked, and the correct version of these files is set up for subsequent use. If you upgrade your OpenVMS VAX version after you install SLS, you need to make sure you have the correct version-specific files to match the OpenVMS VAX version. ________________________ Note ________________________ There are no version-specific files for OpenVMS AXP. If you are running SLS, Version 2.8A on an Alpha AXP system, you can skip this section. ______________________________________________________ Version-Specific Files When SLS, Version 2.8A is installed on your system, the installation procedure copies all files shown in Table 3-3 into the indicated directories. The procedure then copies the three files appropriate for your OpenVMS version to the same name, except that the version number is removed from the file name. After Installing SLS Example: If you are running VMS Version 5.5-2, then SLS$SYSTEM:BACKUPCMD-V55.CLD is copied to SLS$SYSTEM:BACKUPCMD.CLD. A similar copy is performed for the other two files. Table_3-3__SLS_Files_for_Specific_OpenVMS_Versions_________ Operating System______Files__________________________________________ VMS 5.5 SLS$SYSTEM:BACKUPCMD-V55.CLD SLS$SYSTEM:VMSBUXX-V55.EXE SYS$MESSAGE:SLS$BACKUPMSG-V55.EXE OpenVMS 6.0 SLS$SYSTEM:BACKUPCMD-V60.CLD SLS$SYSTEM:VMSBUXX-V60.EXE SYS$MESSAGE:SLS$BACKUPMSG-V60.EXE OpenVMS 6.1 SLS$SYSTEM:BACKUPCMD-V61.CLD SLS$SYSTEM:VMSBUXX-V61.EXE SYS$MESSAGE:SLS$BACKUPMSG-V61.EXE OpenVMS 6.2 SLS$SYSTEM:BACKUPCMD-V62.CLD SLS$SYSTEM:VMSBUXX-V62.EXE SYS$MESSAGE:SLS$BACKUPMSG-V62.EXE ___________________________________________________________ Upgrading from a Previous Version If you upgrade SLS software from a previous version, then: o You need to review the applicability of customized files. o If you upgrade from SLS Version 2.0 software, you need to retain previous applicable SYS$MANAGER:TAPESTART.COM file symbol assignments. After Installing SLS 3-7 o If you upgrade from SLS Version 2.1 software, the installation procedure modifies your current SYS$MANAGER:TAPESTART.COM file. ________________________ Note ________________________ SLS Version 2.8A software is incompatible with versions prior to SLS Version 2.5 software. This consideration applies to systems currently running SLS Version 2.4 software or earlier. When installed, SLS Version 2.5 and Version 2.8A software converts the previous volume and magazine databases to a new format. All information is maintained in the databases, except that all magazines initially appear as "not imported" in a jukebox. ______________________________________________________ Reviewing Outdated Files from SLS$CUSTOM Files placed in SLS$CUSTOM from a previous installation of SLS software may not be compatible with SLS, Version 2.8A software. These files could include patched images or modified command procedures. You need to determine if these files should be removed from SLS$CUSTOM. Where_to_find_old_custom_files: If, during installation, files are found in SLS$CUSTOM, then the installation procedure: 1. Creates a new directory, [SLS$FILES.OLDCUSTOM_n] Each time an installation is performed, the value of n increases. This indicates a new directory has been created for the files in [SLS$FILES.CUSTOM] from the previous installation. 2. Renames and copies all the files in SLS$CUSTOM to the new directory Recommendation: Review the files in [SLS$FILES.OLDCUSTOM_n] before placing them in [SLS$CUSTOM]. Files that predictably executed in a previous version of SLS software may be unpredictable with SLS, Version 2.8A software. After Installing SLS Updating the Command File TAPESTART.COM Follow the steps in Table 3-4 update the new version of command file TAPESTART.COM. For information about media and device management symbols in TAPESTART.COM, see the Media and Device Management Services for OpenVMS Guide to Operations. Note: This procedure is required only if you upgraded from SLS Version 2.0 software. Table_3-4__How_to_Update_the_Command_File_TAPESTART.COM____ Step_Action________________________________________________ 1 Set default to the directory that contains the file TAPESTART.COM. $ SET DEFAULT SYS$MANAGER ___________________________________________________________ 2 Ensure you have your old and new versions of TAPESTART.COM by entering the command: $ DIRECTORY TAPESTART.* Note: The previous version of the file TAPESTART.COM is named TAPESTART.OLD by the VMSINSTAL procedure. The new installed version is properly named TAPESTART.COM. ___________________________________________________________ 3 Edit the new TAPESTART.COM file to include the symbol assignments from the TAPESTART.OLD file. For information about configuring media and devices for SLS, see the Media and Device Management Services for OpenVMS Guide to Operations. ___________________________________________________________ (continued on next page) After Installing SLS 3-9 Table 3-4 (Cont.) How to Update the Command File ___________________TAPESTART.COM___________________________ Step_Action________________________________________________ 4 IF you have an OpenVMScluster node with unique requirements (such as a node with singular access to a tape device): 1. Place a copy of the TAPESTART.COM file in that node's SYS$SPECIFIC:[SYSMGR] directory. 2. Set the protection by entering the command: $ SET PROTECTION=W:RE TAPESTART.COM 3. Make the node-specific changes. ___________________________________________________________ 5 Start SLS software by entering the command: _____$_@SYS$STARTUP:SLS$STARTUP____________________________ Configuring Media and Device Support Once SLS is installed, you need to configure it to use the appropriate media and device support before you can actually save and restore data. This includes determining what physical devices exist for your system and defining appropriate symbols in SYS$MANAGER:TAPESTART.COM to identify them to SLS. For more information on configuring media and device support, see the Media and Device Management Services for OpenVMS Guide to Operations. Configuring Remote Device Facility Support If you requested support for the Remote Device Facility (RDF) during installation, then you need to identify server and client controls. After Installing SLS Adding RDF Client Support In the SYS$MANAGER:TAPESTART.COM file, add one or more media triplets that describe the remote tape device names. Important: It is important to add the remote node name to each device name. For_more_information: Refer to the Media and Device Management Services for OpenVMS Guide to Operations for detailed instructions about modifying the SYS$MANAGER:TAPESTART.COM file to allow access to remote devices. Adding RDF Server Support The configuration file SLS$ROOT:[TTI_RDEV]CONFIG_ nodename.DAT is created during the installation procedure. Include the tape devices you wish to serve in this file. For_more_information: Refer to the Media and Device Management Services for OpenVMS Guide to Operations for detailed instructions about modifying the SLS$ROOT:[TTI_RDEV]CONFIG_nodename.DAT file for remote tape devices. After Installing SLS 3-11 A ______________________________________________________________ SLS Server Installation Example Log File The following example shows an installation of the SLS server software on a VAX system running OpenVMS Version 6.2. A-1 SLS Server Installation Log-Part 1 SLS028A SYS$SYSDEVICE:[SLSKIT] OPTIONS N OpenVMS VAX Software Product Installation Procedure V6.2 is 28-JAN-1997 at 15:44. a question mark (?) at any time for help. The following processes are still active: DECW$SERVER_0 USER_BOB DECW$MWM DECW$TE_0150 _FTA8: _FTA9: you want to continue anyway [NO]? y you satisfied with the backup of your system disk [YES]? following products will be processed: V2.8A Beginning installation of SLS V2.8A at 15:45 Restoring product save set A ... Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: (continued on next page) SLS Server Installation Example Log File A-1 A-1 (Cont.) SLS Server Installation Log-Part 1 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above option [2]: 4 you want to continue the installation [NO]? y Product's release notes have been moved to SYS$HELP. WARNING * * SLS V2.8A (client and server) is not compatible with any previous * versions of SLS prior to V2.5. All nodes running SLS which interact* with each other should also be upgraded to V2.5 or above. * * you want to continue with this installation [No]? y you want to run the IVP after the installation [YES]? Product: SLS Producer: DEC Version: 2.8A Release Date: 22-JAN-1997 this product have an authorization key registered and loaded? y you want to purge files replaced by this installation [YES]? SLS provides support for remote backups. This function allows you to backup disks on this system to a tape drive located on some other system with SLS installed, or to allow other systems to backup their disks to the tape drives on this system. (continued on next page) SLS Server Installation Example Log File A-1 (Cont.) SLS Server Installation Log-Part 1 you want to backup disks on this system to a drive on a remote system? y Remote Device Facility Client support will be provided. you want to allow remote backups access to the tape drives on this system? y Remote Device Facility Server support will be provided. the name of the disk device the SLS software will use [$1$DKB0:]: the name of the directory the SLS software will use [SLS$FILES]: to place summary files from system backups [SLS$ROOT:[SYSBAK.SUMMARY_FILES]]: to place intermediate history files [SLS$ROOT:[SYSBAK.TEMP_HISTORY]]: to place maintenance log files [SLS$ROOT:[SYSBAK.MAINTENANCE_LOGS]]: to place system backup log files [SLS$ROOT:[SYSBAK.SYSBAK_LOGS]]: If you have been using earlier versions of SLS software, there will be log files and summary files resident in SLS$SYSBAK from previous system backups. This installation procedure has the ability to automatically distribute these old files into the directories you have specified. you want to automatically move these old files? [Y]? In order for the SLS software to perform system management tasks, a privileged account called SLS is created. You must specify a unique UIC for this account so that it will not conflict with other accounts on your system. the identifier SLS already exists with UIC [1,21] procedure will assume the SLS account also exists. Please enter a password for the SLS account. The password you specify must contain at least 15 and no more than 31 characters and may not refer to the account/product name, or your system node or cluster name. Valid characters include A through Z, 0 through 9, $ (dollar sign) and _ (underscore). As with the DCL SET PASSWORD command, your input will not echo on the terminal and you will be asked to verify the password. password: (continued on next page) SLS Server Installation Example Log File A-3 A-1 (Cont.) SLS Server Installation Log-Part 1 Updating account SLS with specified password This installation updates an ACCOUNT named SLS. user record(s) updated Updating account SLS for client network access This installation updates an ACCOUNT named SLS. user record(s) updated Updating account SLS privileges and login directory This installation updates an ACCOUNT named SLS. user record(s) updated This installation updates an ACCOUNT named SLS. user record(s) updated Refer to Example A-2 for Part 2 of a sample installation of the SLS server software on a VAX system running OpenVMS Version 6.2. A-2 SLS Server Installation Log-Part 2 The SLS account is used to establish quotas for the processes in which Backups are run. The quota values should be updated in accordance with the recommendations set forth in the `VMS Backup Utility Reference Manual'. If you wish, this installation procedure will automatically update these quotas now. you wish to update these quotas now [YES]? The following quotas will be set for the SLS account: Maxjobs: 0 Fillm: 500 Bytlm: 128000 Maxacctjobs: 0 Shrfillm: 0 Pbytlm: 0 Maxdetach: 0 BIOlm: 128 JTquota: 1024 Prclm: 10 DIOlm: 4096 WSdef: 1024 Prio: 4 ASTlm: 4096 WSquo: 16384 Queprio: 4 TQElm: 32 WSextent: 16384 CPU: (none) Enqlm: 2500 Pgflquo: 100000 (continued on next page) SLS Server Installation Example Log File A-2 (Cont.) SLS Server Installation Log-Part 2 Updating quotas for account SLS... This installation updates an ACCOUNT named SLS. user record(s) updated This installation updates an ACCOUNT named SLS. user record(s) updated This installation updates an ACCOUNT named SLS. user record(s) updated Digital recommends that the SLS account be used only by the SLS software and not as an interactive account. It is recommended that the Storage Administrator and Operators use other accounts to perform SLS functions. If you wish, this installation procedure will automatically set the appropriate flags to disallow interactive access to this account. you wish to update these flags now [YES]? The following fields will be set for the SLS account: /FLAGS= NoAudit DisMail NoDisReport DefCLI DisNewMail NoDisUser NoDisCtlY DisReconnect NoGenPwd /BATCH /NOINTERACTIVE /NOLOCAL /NODIALUP /NOREMOTE /NOEXPIRATION /PWDEXPIRED /NETWORK Updating flags for account SLS... This installation updates an ACCOUNT named SLS. user record(s) updated This installation updates an ACCOUNT named SLS. user record(s) updated This installation updates an ACCOUNT named SLS. user record(s) updated Checking for DISKQUOTAs on the SLS server device ... There will be no further questions asked. The installation of Storage Library System will take an average of 30 minutes more to complete. It may take longer if the log files and summary files from previous system backups are going to be automatically distributed into the system backup directories you have specified. (continued on next page) SLS Server Installation Example Log File A-5 A-2 (Cont.) SLS Server Installation Log-Part 2 Restoring product save set B ... Proceeding with saveset B Linking privileged shareable image The definitions of SLS$SYSBAK_LOGS, SLS$MAINTENANCE_LOGS, SLS$SUMMARY_FILES and SLS$TEMP_HISTORY are being replaced in your TAPESTART.COM file with the values you specified earlier in this installation. If you have changed the location of any of these logicals, you must ensure that appropriate files are copied from the old location to the new location. Creating SLS subdirectories... This product creates system disk directory $1$DKB0:[SLS$FILES]. $1$DKB0:[SLS$FILES] already exists This product creates system disk directory $1$DKB0:[SLS$FILES.AUDIT]. $1$DKB0:[SLS$FILES.AUDIT] already exists This product creates system disk directory $1$DKB0:[SLS$FILES.CUSTOM]. $1$DKB0:[SLS$FILES.CUSTOM] already exists This product creates system disk directory $1$DKB0:[SLS$FILES.DATA]. $1$DKB0:[SLS$FILES.DATA] already exists This product creates system disk directory $1$DKB0:[SLS$FILES.HIST]. $1$DKB0:[SLS$FILES.HIST] already exists This product creates system disk directory $1$DKB0:[SLS$FILES.PARAMS]. $1$DKB0:[SLS$FILES.PARAMS] already exists This product creates system disk directory $1$DKB0:[SLS$FILES.PRIMAST]. $1$DKB0:[SLS$FILES.PRIMAST] already exists This product creates system disk directory $1$DKB0:[SLS$FILES.SYSBAK]. $1$DKB0:[SLS$FILES.SYSBAK] already exists This product creates system disk directory $1$DKB0:[SLS$FILES.SYSTEM]. $1$DKB0:[SLS$FILES.SYSTEM] already exists This product creates system disk directory $1$DKB0:[SLS$FILES.USRBAK]. $1$DKB0:[SLS$FILES.USRBAK] already exists This product creates system disk directory SLS$ROOT:[SYSBAK.SUMMARY_FILES]. SLS$ROOT:[SYSBAK.SUMMARY_FILES] already exists This product creates system disk directory SLS$ROOT:[SYSBAK.TEMP_HISTORY]. SLS$ROOT:[SYSBAK.TEMP_HISTORY] already exists This product creates system disk directory SLS$ROOT:[SYSBAK.MAINTENANCE_LOGS]. SLS$ROOT:[SYSBAK.MAINTENANCE_LOGS] already exists This product creates system disk directory SLS$ROOT:[SYSBAK.SYSBAK_LOGS]. SLS$ROOT:[SYSBAK.SYSBAK_LOGS] already exists (continued on next page) SLS Server Installation Example Log File A-2 (Cont.) SLS Server Installation Log-Part 2 Defining files that need to be moved Providing Remote Device Facility Support Restoring product save set C ... This product creates system disk directory SLS$ROOT:[TTI_RDEV]. SLS$ROOT:[TTI_RDEV] already exists Moving old log files and summary files as requested. Finished moving old log files and summary files. The following post-installation steps are necessary. Refer to the Installation Guide for details. 1. Edit the system startup procedure to start the SLS software on this client. Add $ @SYS$STARTUP:SLS$STARTUP 2. Edit the system wide login file. Add $ @SYS$MANAGER:SLS$TAPSYMBOL 3. Run SLS$SYSTEM:SLS$SLSMGR.EXE to perform the following functions: a. Authorize access to the SLS server database for SLS client nodes. b. Authorize access to SLS pools for SLS users. 4. Customize SYS$MANAGER:TAPESTART.COM to reflect SLS environment parameters. 5. Check that SLS$DBX object is defined on all nodes participating in the VMScluster System alias. 6. For Remote Device Facility client support, you should add one or more media-type triplets (MTYPE_x, DENS_x, DRIVES_x) to your TAPESTART.COM to describe the remote tape drives. Be sure to include the remote nodename in each drive name. 7. For Remote Device Facility server support, you should check the file SLS$ROOT:[TTI_RDEV]CONFIG_NODE1.DAT to ensure that the tape devices you wish to serve are included in this RDF configuration file. This file will be created initially when SLS is started after this installation. (continued on next page) SLS Server Installation Example Log File A-7 A-2 (Cont.) SLS Server Installation Log-Part 2 Files will now be moved to their target directories... Starting SLS identification of created process is 00000154 Waiting for the SLS software to start Beginning SLS Version V2.8A Installation Verification Procedure (IVP) Installation verification begun at 28-JAN-1997 16:06:01.86 Checking for correct version of VMS. Checking for presence of DECnet. Checking for SLS executable images. Checking system-wide logical names. Checking for SLS database files. Checking for SLS client process. Checking for SLS server process. Checking for FMS executable images. Checking for correct version of SLS. Waiting for subprocess SLS$IVP to complete. %SLS-I-VERSION, Storage Library System for OpenVMS, version V2.8A Doing a STORAGE ADD VOLUME. Waiting for subprocess SLS$IVP to complete. Waiting for subprocess SLS$IVP to complete. Doing a STORAGE ALLOCATE. (continued on next page) SLS Server Installation Example Log File A-2 (Cont.) SLS Server Installation Log-Part 2 Doing a STORAGE SHOW VOLUME. XYZZY9 Owner: NODE1::SLS BACKUP Brand: 28-JAN-1997 16:06 Scratch: 27-MAR-1998 16:06 28-JAN-1997 16:06 Cleaned: 28-JAN-1997 16:06 type: TK86K Length: 0 0 UIC: [SLS] HEADQUARTERS Protection: S:RW,O:RW,G:R,W: Onsite: Errors: 0 Flag: ALLOCATED volume: *none* Previous: *none* Rec len: 0 Block factor: 0 28-JAN-1997 16:06 Density: number: Other side: / slot: / is not in a jukebox. is not in a magazine. Doing a STORAGE DEALLOCATE. Doing a STORAGE REMOVE VOLUME. Doing a STORAGE SHOW VOLUME; there should be no such volume. no such volume(s) * * * All tests have completed sucessfully. * * * Installation verification finished at 28-JAN-1997 16:06:33.18 Successful Installation Verification of SLS Version V2.8A Installation of SLS V2.8A completed at 16:06 VMSINSTAL procedure done at 16:06 SLS Server Installation Example Log File A-9 B ______________________________________________________________ SLS Client Installation Example Log File The following example shows an installation of the SLS client software on a VAX system running OpenVMS Version 6.2. This example also installs support for the RDF client and does not run an IVP. SLSCLIENTA028 SYS$SYSDEVICE:[SLSKIT] OPTIONS N OpenVMS VAX Software Product Installation Procedure V6.2 is 29-JAN-1997 at 08:45. a question mark (?) at any time for help. The following processes are still active: SYSTEM you want to continue anyway [NO]? Y you satisfied with the backup of your system disk [YES]? Y following products will be processed: V2.8A Beginning installation of SLSCLIENT V2.8A at 08:46 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 option [2]: 4 you want to continue the installation [NO]? Y Product's release notes have been moved to SYS$HELP. SLS Client Installation Example Log File B-1 WARNING * * SLS V2.8A (client and server) is not compatible with any previous * versions of SLS prior to V2.5. All nodes running SLS which interact* with each other should also be upgraded to V2.5 or above. * * you want to continue with this installation [No]? Y you want to run the IVP after the installation [YES]? Y Product: SLS-REMOTE Producer: DEC Version: 2.8A Release Date: 22-JAN-1997 this product have an authorization key registered and loaded? Y you want to purge files replaced by this installation [YES]? N Before proceeding with the installation of the SLS software, you should have read the SLS Installation Guide discussion about the use of the SLS server node or VMScluster System alias. You will need the name of the SLS server node or VMScluster System alias. you ready to proceed [YES]? Y is the name or VMScluster System alias of the SLS server node: NODE2 SLS provides support for remote backups. This function allows you to backup disks on this system to a tape drive located on some other system with SLS installed, or to allow other systems to backup their disks to the tape drives on this system. you want to backup disks on this system to a drive on a remote system? Y Remote Device Facility Client support will be provided. you want to allow remote backups access to the tape drives on this system? Y Remote Device Facility Server support will be provided. the name of the disk device the SLS software will use [$1$DKB0:]: the name of the directory the SLS software will use [SLS$FILES]: to place summary files from system backups [SLS$ROOT:[SYSBAK.SUMMARY_FILES]]: to place intermediate history files [SLS$ROOT:[SYSBAK.TEMP_HISTORY]]: to place maintenance log files [SLS$ROOT:[SYSBAK.MAINTENANCE_LOGS]]: to place system backup log files [SLS$ROOT:[SYSBAK.SYSBAK_LOGS]]: SLS Client Installation Example Log File If you have been using earlier versions of SLS software, there will be log files and summary files resident in SLS$SYSBAK from previous system backups. This installation procedure has the ability to automatically distribute these old files into the directories you have specified. you want to automatically move these old files? [Y]? In order for the SLS software to perform system management tasks, a privileged account called SLS is created. You must specify a unique UIC for this account so that it will not conflict with other accounts on your system. the identifier SLS already exists with UIC [1,21] procedure will assume the SLS account also exists. Please enter a password for the SLS account. The password you specify must contain at least 15 and no more than 31 characters and may not refer to the account/product name, or your system node or cluster name. Valid characters include A through Z, 0 through 9, $ (dollar sign) and _ (underscore). As with the DCL SET PASSWORD command, your input will not echo on the terminal and you will be asked to verify the password. password: Updating account SLS with specified password This installation updates an ACCOUNT named SLS. user record(s) updated Updating account SLS privileges and login directory This installation updates an ACCOUNT named SLS. user record(s) updated This installation updates an ACCOUNT named SLS. user record(s) updated The SLS account is used to establish quotas for the processes in which Backups are run. The quota values should be updated in accordance with the recommendations set forth in the `VMS Backup Utility Reference Manual'. If you wish, this installation procedure will automatically update these quotas now. you wish to update these quotas now [YES]? Y SLS Client Installation Example Log File B-3 The following quotas will be set for the SLS account: Maxjobs: 0 Fillm: 500 Bytlm: 128000 Maxacctjobs: 0 Shrfillm: 0 Pbytlm: 0 Maxdetach: 0 BIOlm: 128 JTquota: 1024 Prclm: 10 DIOlm: 4096 WSdef: 1024 Prio: 4 ASTlm: 4096 WSquo: 16384 Queprio: 4 TQElm: 32 WSextent: 16384 CPU: (none) Enqlm: 2500 Pgflquo: 100000 Updating quotas for account SLS... This installation updates an ACCOUNT named SLS. user record(s) updated This installation updates an ACCOUNT named SLS. user record(s) updated This installation updates an ACCOUNT named SLS. user record(s) updated Digital recommends that the SLS account be used only by the SLS software and not as an interactive account. It is recommended that the Storage Administrator and Operators use other accounts to perform SLS functions. If you wish, this installation procedure will automatically set the appropriate flags to disallow interactive access to this account. you wish to update these flags now [YES]? Y The following fields will be set for the SLS account: /FLAGS= NoAudit DisMail NoDisReport DefCLI DisNewMail NoDisUser NoDisCtlY DisReconnect NoGenPwd /BATCH /NOINTERACTIVE /NOLOCAL /NODIALUP /NOREMOTE /NOEXPIRATION /PWDEXPIRED /NONETWORK Updating flags for account SLS... This installation updates an ACCOUNT named SLS. user record(s) updated This installation updates an ACCOUNT named SLS. user record(s) updated This installation updates an ACCOUNT named SLS. user record(s) updated Checking for DISKQUOTAs on the SLS device ... SLS Client Installation Example Log File There will be no further questions asked. The installation of Storage Library System will take an average of 30 minutes more to complete. It may take longer if the log files and summary files from previous system backups are going to be automatically distributed into the system backup directories you have specified. Restoring product save set B ... Proceeding with saveset B Linking privileged shareable image The definitions of SLS$SYSBAK_LOGS, SLS$MAINTENANCE_LOGS, SLS$SUMMARY_FILES and SLS$TEMP_HISTORY are being replaced in your TAPESTART.COM file with the values you specified earlier in this installation. If you have changed the location of any of these logicals, you must ensure that appropriate files are copied from the old location to the new location. Creating SLS subdirectories... This product creates system disk directory $1$DKB0:[SLS$FILES]. $1$DKB0:[SLS$FILES] already exists This product creates system disk directory $1$DKB0:[SLS$FILES.AUDIT]. $1$DKB0:[SLS$FILES.AUDIT] already exists This product creates system disk directory $1$DKB0:[SLS$FILES.CUSTOM]. $1$DKB0:[SLS$FILES.CUSTOM] already exists This product creates system disk directory $1$DKB0:[SLS$FILES.DATA]. $1$DKB0:[SLS$FILES.DATA] already exists This product creates system disk directory $1$DKB0:[SLS$FILES.HIST]. $1$DKB0:[SLS$FILES.HIST] already exists This product creates system disk directory $1$DKB0:[SLS$FILES.PARAMS]. $1$DKB0:[SLS$FILES.PARAMS] already exists This product creates system disk directory $1$DKB0:[SLS$FILES.SYSBAK]. $1$DKB0:[SLS$FILES.SYSBAK] already exists This product creates system disk directory $1$DKB0:[SLS$FILES.SYSTEM]. $1$DKB0:[SLS$FILES.SYSTEM] already exists This product creates system disk directory $1$DKB0:[SLS$FILES.USRBAK]. $1$DKB0:[SLS$FILES.USRBAK] already exists This product creates system disk directory SLS$ROOT:[SYSBAK.SUMMARY_FILES]. SLS$ROOT:[SYSBAK.SUMMARY_FILES] already exists This product creates system disk directory SLS$ROOT:[SYSBAK.TEMP_HISTORY]. SLS$ROOT:[SYSBAK.TEMP_HISTORY] already exists This product creates system disk directory SLS$ROOT:[SYSBAK.MAINTENANCE_LOGS]. SLS$ROOT:[SYSBAK.MAINTENANCE_LOGS] already exists This product creates system disk directory SLS$ROOT:[SYSBAK.SYSBAK_LOGS]. SLS$ROOT:[SYSBAK.SYSBAK_LOGS] already exists SLS Client Installation Example Log File B-5 Defining files that need to be moved Providing Remote Device Facility Support Restoring product save set C ... This product creates system disk directory SLS$ROOT:[TTI_RDEV]. SLS$ROOT:[TTI_RDEV] already exists Moving old log files and summary files as requested. Finished moving old log files and summary files. The following post-installation steps are necessary. Refer to the Installation Guide for details. 1. Edit the system startup procedure to start the SLS software on this client. Add $ @SYS$STARTUP:SLS$STARTUP 2. Edit the system wide login file. Add $ @SYS$MANAGER:SLS$TAPSYMBOL 3. Customize SYS$MANAGER:TAPESTART.COM to reflect SLS environment parameters. 4. For Remote Device Facility client support, you should add one or more media-type triplets (MTYPE_x, DENS_x, DRIVES_x) to your TAPESTART.COM to describe the remote tape drives. Be sure to include the remote nodename in each drive name. 5. For Remote Device Facility server support, you should check the file SLS$ROOT:[TTI_RDEV]CONFIG_NODE2.DAT to ensure that the tape devices you wish to serve are included in this RDF configuration file. This file will be created initially when SLS is started after this installation. Files will now be moved to their target directories... Starting SLS identification of created process is 00000165 Waiting for the SLS software to start Beginning SLS Version V2.8A Installation Verification Procedure (IVP) Installation verification begun at 29-JAN-1997 09:01:17.91 Checking for correct version of VMS. SLS Client Installation Example Log File Checking for presence of DECnet. Checking for SLS executable images. Checking system-wide logical names. Checking for SLS database files. Checking for SLS client process. Checking for SLS server process. Checking for FMS executable images. Checking for correct version of SLS. Waiting for subprocess SLS$IVP to complete. Storage Library System for OpenVMS, version V2.8A Doing a STORAGE ADD VOLUME. Waiting for subprocess SLS$IVP to complete. Could not do a STORAGE ADD VOLUME! failed to connect to network task !AS at !%D Installation verification finished at 29-JAN-1997 09:01:36.62 Failed Installation Verification of SLS Version V2.8A Installation of SLSCLIENT V2.8A completed at 09:01 VMSINSTAL procedure done at 09:01 SLS Client Installation Example Log File B-7 C ______________________________________________________________ Files and Logical Names Files The Storage Library System (SLS) installation procedure creates a number of files on your system and defines logical names. o Table C-1 lists and describes the files installed on server nodes. o Table C-2 lists and describes the files installed on client nodes. o Table C-3 lists logical name table entries. o Table C-4 lists unload drive logicals. C-1 Files Installed on Server Nodes______________________________________________________________ Name Description______________________________________________________________ directory______________________________________________________________ SLS shareable image; contains application interface routines for history file access ______________________________________________________________ directory______________________________________________________________ Normal user login symbol definitions Contains all SLS software's tailoring parameters Template file for TAPESTART.COM (continued on next page) Files and Logical Names C-1 C-1 (Cont.) Files Installed on Server Nodes______________________________________________________________ Name Description______________________________________________________________ directory______________________________________________________________ Contains information for backup messages; copied from the appropriate SLS$BACKUPMSG-Vnn.EXE file for the version of OpenVMS running on your system Contains OpenVMS version-specific information for backup messages Contains text of SLS messages ______________________________________________________________ directory______________________________________________________________ Startup command file ______________________________________________________________ directory______________________________________________________________ Installation verification procedure ______________________________________________________________ directory______________________________________________________________ System backup history attribute template file ______________________________________________________________ directory______________________________________________________________ Pool authorization file Slot master file Slot master file definition Volume database FDL for TAPEMAST.DAT Magazine database (continued on next page) Files and Logical Names C-1 (Cont.) Files Installed on Server Nodes______________________________________________________________ Name Description______________________________________________________________ directory______________________________________________________________ __ files in SLS$PARAMS: are not replaced by the installation if SLS software was previously installed on your Defines location of user history files Distribution copy of B1C.TEMPLATE Note: The template version of this file is in SLS$SYSTEM:B1C.TEMPLATE. Use the updated version in SLS$PARAMS:. Defines dates of holidays for system backups FDL for POOLAUTH.DAT File containing name of default Standby Archiving class ______________________________________________________________ directory______________________________________________________________ Template parameter file for archive system backups Template system backup file ______________________________________________________________ directory______________________________________________________________ Accesses LNM$SLS logical name table Announces processing location Allocated Tapes report definition file Allocation Order report definition file Allocates a tape drive (continued on next page) Files and Logical Names C-3 C-1 (Cont.) Files Installed on Server Nodes______________________________________________________________ Name Description______________________________________________________________ directory______________________________________________________________ ASNUSRBAK.COM distribution copy Command Language Definition file for specific VMS versions, ranging from V5.4 through V6.2; for example, BACKUPCMD-V62.CLD Command Language Definition file for backup; copied from BACKUPCMD-Vnn, where nn is the current VMS version level Batch job to do a backup job Batch job for ASCII backup job Batch job for VMS BACKUP backup job Batch job for EBCDIC backup job Template for archiving classes Automatic scheduling day checker Early morning cleanup batch job Cleanable tapes report definition file Coming onsite report definition file Creates a symbol definition file (in [.DATA]) Creates a SYSBAK history FILES file Installs DATATRIEVE information Prints a list of down tapes control file Creates a *_SBK.COM system backup definition file Defines a LNM$SLS_VALUE logical name (continued on next page) Files and Logical Names C-1 (Cont.) Files Installed on Server Nodes______________________________________________________________ Name Description______________________________________________________________ directory______________________________________________________________ Finds a file in SYS$SYSTEM Free tapes report definition file Gets the earliest created file Going offsite report definition file Places an exclusive lock on a system backup history set Operator initialize tapes utility Sends mail message for backups and restores SLS system bootstrap loader SLS manager account login file Procedure to run MAIL_ADVANCE Displays scratchable tape Creates archive class authorizations Miscellaneous operator menu Mounts and validates a reel on a drive Moves USRBAK files to their owner Master report batch job Master report template definition file Operator login symbol definitions Operator startup processing job Template file for printed labels Template file for printed labels Quantity report batch job System startup command file Releases several tapes that are in transition (continued on next page) Files and Logical Names C-5 C-1 (Cont.) Files Installed on Server Nodes______________________________________________________________ Name Description______________________________________________________________ directory______________________________________________________________ Normal main restore batch job Restores an ASCII format tape Normal subrestore batch job Restores an EBCDIC format tape Restores an RMU backup tape Queues system backups for today Removes old system backup summary files Updates a system backup history batch job RMS definition file to convert a system history file to a sequential file Sets protection of SLS files Sets up SLS$USRBAK logical name for a user Sets up onsite and offsite dates Compresses system history files Contains all VAX FMS forms for SLS software Screens for SLSMGR.EXE Utility to abort a process Allocates a local or remote tape device Builds a user backup request FDL file for *_B1C.DAT Checks tape drives for data compaction capability Accounting period data collector (continued on next page) Files and Logical Names C-1 (Cont.) Files Installed on Server Nodes______________________________________________________________ Name Description______________________________________________________________ directory______________________________________________________________ Creates the LNM$JOB table with W:RE protection Creates a permanent mailbox for DCL use System backup executable for RMU database backup operations Command file to control spawned database backup process Operator Export Volume function for the ACS Operator Import Volume function for the ACS Operator Initialize Volume Series function for the ACS Operator Inventory Range of Volumes function for the ACS Operator Load Volume Onto Drive function for the ACS Operator SLS-ACS Management Menu Operator Unload Drive function for the ACS Operator Unload Volume function for the ACS Executable to release a drive allocated to DCSC Deallocates a local or remote tape device Deletes a permanent mailbox that CREMBX made Executes a FORCEX system service call (continued on next page) Files and Logical Names C-7 C-1 (Cont.) Files Installed on Server Nodes______________________________________________________________ Name Description______________________________________________________________ directory______________________________________________________________ Reads from a permanent mailbox from DCL Gets information from SYSUAF.DAT DCL STORAGE command help file IBM [TM] nonlabeled tape reading utility IBM [TM] nonlabeled tape writing utility For SLS-ACS support, determines whether DCSC (Digital Cartridge Server Component) software accesses a device Determines whether a drive is set to be nounload Reads key attributes into symbols Loads user address space with known exit status value Reads process rights identifiers Finds tapes that need to have advance mail sent Maintenance screen executable Master report executable Image for SLS$OPCOM process; sends and receives remote OPCOM messages and device control requests Writes to a permanent mailbox from DCL Quantity report executable Command procedure to determine version of RMU software DCL request that can define a symbol (continued on next page) Files and Logical Names C-1 (Cont.) Files Installed on Server Nodes______________________________________________________________ Name Description______________________________________________________________ directory______________________________________________________________ Normal restore screen request generator Loads system history definitions utility Polls for system backup subprocess complete Updates a system backup history executable Sets owner UIC of a device Sets process privileges given a hexadecimal mask Sets process username Allows SLS command procedures to print text of SLS system messages Shuts down SLS software SLS manager's authorization menu Prints a slot report Starts SLS$OPCOM process Starts Remote Device Facility (RDF) process DCL STORAGE command definition System backup executable Command procedure to control spawned system backup process System backup history cleanup executable System backup history reel free executable (continued on next page) Files and Logical Names C-9 C-1 (Cont.) Files Installed on Server Nodes______________________________________________________________ Name Description______________________________________________________________ directory______________________________________________________________ Generates reports of system backup histories DCL TAPE command executable Purges scratchable tape's executable Generate tape usage report executable DB manager executable RQ manager executable Moves volumes to vault User history load utility User backup executable User backup history tape free processor User backup history report generator Vault profile report executable Command procedure to verify your OpenVMS software version against the versions of BACKUPCMD.CLD and VMSBUXX.EXE; you use this procedure if you upgrade OpenVMS after you have installed SLS Maintenance program for volumes in StorageTek ACS robots Allocates tapes for a standalone backup Standby archiving batch job Standby archiving control menu SLS startup command file Used in label printing (continued on next page) Files and Logical Names C-1 (Cont.) Files Installed on Server Nodes______________________________________________________________ Name Description______________________________________________________________ directory______________________________________________________________ System backup batch job Template file to run system backups Intercepts SYSBAK subprocess RMS definition file for system backup history .FILES files RMS definition file for system backup history .SETS files System backup history cleanup batch job Converts system history files as a Batch process System backup history cleanup control menu Reads old system backup tape and updates system history file Reads backup listing and creates system history file Defines entire disk restore job Restores an entire disk batch job Help file for TUSERMENU.COM Purges scratchable tape's subprocess Purges scratchable tape's mail message Distribution version of TAPESTART.COM Tapes offsite report definition file Generates tape usage report batch job DB manager shutdown command file DB manager startup command file DB manager detached process command file (continued on next page) Files and Logical Names C-11 C-1 (Cont.) Files Installed on Server Nodes______________________________________________________________ Name Description______________________________________________________________ directory______________________________________________________________ RQ manager startup command file RQ manager detached process command file Starts TAPMGRDB and TAPMGRRQ command files Utility manager detached process command file Free tape utility processor Midnight utility processor TOPER menu command file Defines volume report for volumes in transition (continued on next page) Files and Logical Names C-1 (Cont.) Files Installed on Server Nodes______________________________________________________________ Name Description______________________________________________________________ directory______________________________________________________________ Another user menu Intercepts USRBAK subprocess FDL for DOCDB_4R2 files FDL for normal user history file Deletes user history entries Generates SLS$USRBAK logical name for USRRPT.EXE Sets location of volumes in or out of vault Vault menu command file Onsite and offsite dates for SET_ VAULT_DATES Vault profile report batch job Patched version of VMS BACKUP for specific VMS versions ranging from V5.4 through V6.2; for example, VMSBUXX-V62.EXE Patched version of VMS BACKUP; copied from whichever VMSBUXX-Vnn.EXE is appropriate for the version of VMS software______________________________________________________________ Files and Logical Names C-13 C-2 Files Installed on Client Nodes______________________________________________________________ Name Description______________________________________________________________ directory______________________________________________________________ Nonfunctional JCS shareable image; installed only if JCS software is not present SLS shareable image; contains application interface routines for history file access ______________________________________________________________ directory______________________________________________________________ Normal user login symbol definitions Contains all SLS software's customization parameters Template file for TAPESTART.COM ______________________________________________________________ directory______________________________________________________________ Contains text of SLS messages ______________________________________________________________ directory______________________________________________________________ Startup command file ______________________________________________________________ directory______________________________________________________________ Installation verification procedure ______________________________________________________________ directory______________________________________________________________ System backup history attribute template file (continued on next page) Files and Logical Names C-2 (Cont.) Files Installed on Client Nodes______________________________________________________________ ______________________________________________________________ directory______________________________________________________________ Defines location of user history files Distribution copy of B1C.TEMPLATE Defines dates of holidays for system backups Default standby archiving authorization file ______________________________________________________________ directory______________________________________________________________ Template parameter file for archive system backups Template system backup file ______________________________________________________________ directory______________________________________________________________ Accesses LNM$SLS logical name table Announces processing location Allocated tapes report definition file Allocation order report definition file Allocates a tape drive ASNUSRBAK.COM distribution copy Batch job to run a backup job Batch job for ASCII backup job Batch job for VMS BACKUP backup job Batch job for EBCDIC backup job Batch job for UASCII backup job Automatic scheduling day checker Early morning cleanup batch job (continued on next page) Files and Logical Names C-15 C-2 (Cont.) Files Installed on Client Nodes______________________________________________________________ Name Description______________________________________________________________ directory______________________________________________________________ Cleanable tapes report definition file Coming onsite report definition file Creates a symbol definition file (in [.DATA]) Creates a SYSBAK history FILES file Installs DATATRIEVE information Prints a list of down tapes control file Creates an *_SBK.COM system backup definition file Defines a LNM$SLS_VALUE logical name Finds a file in SYS$SYSTEM Free tapes report definition file Gets the earliest created file Going offsite report definition file Places an exclusive lock on a system backup history set Operator initialize tapes utility Sends mail message for backups and restores SLS system bootstrap loader SLS manager account login file Procedure to run MAIL_ADVANCE Displays scratchable tape Creates archive class authorizations Miscellaneous operator menu Mounts and validates a reel on a drive Master report batch job Master report template definition file (continued on next page) Files and Logical Names C-2 (Cont.) Files Installed on Client Nodes______________________________________________________________ Name Description______________________________________________________________ directory______________________________________________________________ Operator login symbol definitions Operator startup processing job Template file for printed labels Template file for printed labels Quantity report batch job System startup command file Releases several tapes that are in transition Normal main restore batch job Restores an ASCII format tape Normal subrestore batch job Restores an EBCDIC format tape (continued on next page) Files and Logical Names C-17 C-2 (Cont.) Files Installed on Client Nodes______________________________________________________________ Name Description______________________________________________________________ directory______________________________________________________________ Queues system backups for today Removes old system backup summary files Updates a system backup history batch job Creates a sequential file Sets up SLS$USRBAK logical name for a user Sets up onsite and offsite dates Compresses system history files Contains all VAX FMS forms for SLS software Utility to abort a process Allocates a local or remote tape device Builds a normal backup request FDL file for *_B1C.DAT Accounting period data collector Creates the LNM$JOB table with W:RE protection Creates a permanent mailbox for DCL use Operator Export Volume function for the ACS Operator Import Volume function for the ACS Operator Initialize Volume Series function for the ACS Operator Inventory Range of Volumes function for the ACS (continued on next page) Files and Logical Names C-2 (Cont.) Files Installed on Client Nodes______________________________________________________________ Name Description______________________________________________________________ directory______________________________________________________________ Operator Load Volume Onto Drive function for the ACS Operator SLS-ACS Management Menu Operator Unload Drive function for the ACS Operator Unload Volume function for the ACS Deallocates a local or remote tape device Deletes a permanent mailbox that CREMBX made Executes a FORCEX system service call Reads from a permanent mailbox from DCL Gets information from SYSUAF.DAT DCL STORAGE command help file IBM [TM] nonlabeled tape reading utility IBM [TM] nonlabeled tape writing utility For SLS-ACS support, determines whether DCSC (Digital Cartridge Server Component) software accesses a device Reads key attributes into symbols Reads process rights identifiers Finds tapes that need to have advance mail sent Maintenance screen executable Master report executable (continued on next page) Files and Logical Names C-19 C-2 (Cont.) Files Installed on Client Nodes______________________________________________________________ Name Description______________________________________________________________ directory______________________________________________________________ Image for SLS$OPCOM process; sends and receives remote OPCOM messages and device control requests Writes to a permanent mailbox from DCL Quantity report executable DCL request that can define a symbol Normal restore screen request generator Loads system history definitions utility Polls for system backup subprocess complete Updates a system backup history executable Sets owner UIC of a device Allows SLS command procedures to print text of SLS system messages Sets process privileges given a hexadecimal mask Sets process username Shuts down SLS software Prints a slot report Starts SLS$OPCOM process DCL STORAGE command definition System backup executable System backup history cleanup executable System backup history reel free executable (continued on next page) Files and Logical Names C-2 (Cont.) Files Installed on Client Nodes______________________________________________________________ Name Description______________________________________________________________ directory______________________________________________________________ Generates reports of system backup histories DCL TAPE command executable Purges scratchable tape's executable Generates tape usage report executable RQ manager executable Moves volumes to vault User history load utility User backup executable User backup history tape free processor User backup history report generator Vault profile report executable Allocates tapes for a standalone backup Standby archiving batch job Standby archiving control menu SLS startup command file (continued on next page) Files and Logical Names C-21 C-2 (Cont.) Files Installed on Client Nodes______________________________________________________________ Name Description______________________________________________________________ directory______________________________________________________________ System backup batch job Template file to run system backups Intercepts SYSBAK subprocess Template for system backup history .FILES files Template for system backup history .SETS files System backup history cleanup batch job Converts system history files as a Batch process System backup history cleanup control menu Reads old system backup tape into history Reads backup listing and creates system history file Defines entire disk restore job Restores an entire disk batch job Help file for TAPEMENU.COM Purges scratchable tape's subprocess Purges scratchable tape's mail message Distribution version of TAPESTART.COM Tapes offsite report definition file Generates tape usage report batch job RQ manager startup command file RQ manager detached process command file (continued on next page) Files and Logical Names C-2 (Cont.) Files Installed on Client Nodes______________________________________________________________ Name Description______________________________________________________________ directory______________________________________________________________ Starts TAPMGRDB and TAPMGRRQ command files Utility manager detached process command file Free volume utility processor Midnight utility processor TOPER menu command file Defines volume report for volumes in transition Another user menu Intercepts USRBAK subprocess FDL for normal user history file Deletes user history entries Generates an SLS$USRBAK logical name for USRRPT.EXE Sets location of volumes in or out of vault Vault menu command file Onsite and offsite dates for SET_ VAULT_DATES Vault profile report batch job Patched version of VMS BACKUP______________________________________________________________ Logical Names Table C-3 lists the logical names entered into the logical name tables LNM$SYSTEM_TABLE and LNM$SLS$TABLE when SLS software is installed. These names are defined by the product's startup file. They are automatically entered into these logical name tables whenever the system reboots or whenever the software is invoked. Files and Logical Names C-23 The LNM$JOB table also contains logical names that are defined when a user logs in to a system running SLS software. C-3 Logical Name Table Entries______________________________________________________________ Name Definition and Description______________________________________________________________ ______________________________________________________________ SLS$ROOT:[CUSTOM] This directory contains customized SLS files for your site. SLS$ROOT:[DATA.nodename] This directory stores all the log files for your current SLS system. SLS$ROOT:[DATA] This is the top level directory for log file storage. JCS$DEFAULT_JUKEBOX The default jukebox used by SLS software. FOREVER <- insert archive class here This logical points to the default archive class. Refer to the Storage Library System for OpenVMS Storage Administrator's Guide for information on defining standby archiving classes. GENERIC The default system backup history set. SLS$ROOT:[HIST] The location of the GENERIC history set. filespec or _NL: or device: (continued on next page) Files and Logical Names C-3 (Cont.) Logical Name Table Entries______________________________________________________________ Name Definition and Description______________________________________________________________ ______________________________________________________________ This logical points to the current label file or printer where labels are printed. mbx_id The mailbox used for communication to the SLS$TAPMGRRQ process. SLS$ROOT:[PRIMAST] This directory points to the node's database, whether this is your current node or a node remote to you. SLS$ROOT:[PARAMS] This directory contains the system dependent parameter files for SLS software. device:[SLS$FILES.] This directory points to the top level directory for SLS files. REBOOT Used internally during startup. SLS$ROOT:[SYSBAK] This directory contains the *_SBK.COM history files. SLS$ROOT:[CUSTOM] SLS$ROOT:[SYSTEM] This directory contains all the files for running SLS software. DPS The location for volumes sent offsite. (continued on next page) Files and Logical Names C-25 C-3 (Cont.) Logical Name Table Entries______________________________________________________________ Name Definition and Description______________________________________________________________ Entries______________________________________________________________ nodename Name of node where primary volume database resides. proc_id Points to the process ID of the database manager process. proc_id Points to the process ID of the request manager process. ______________________________________________________________ Entries______________________________________________________________ SLS$PARAMS:SLS$DEFAULT_B1C.DAT Location of default standby archiving authorization file. SLS$ROOT:[USRBAK]username This points to the SLS backup procedure that uses the VMS BACKUP utility to back up user files. id_MBX mbx_id Network mailbox used by SLS software for user. One or more may be listed.______________________________________________________________ More logical names for SLS software can be found in the logical name table LNM$SLS$VALUES. These logicals are defined whenever TAPESTART.COM executes. Sample output from the DCL command SHOW LOGICAL/TABLE=LNM$SLS$VALUES is shown in Example C-1. Example C-1 Sample List of LNM$SLS$VALUES Entries (continued on next page) Files and Logical Names Example C-1 (Cont.) Sample List of LNM$SLS$VALUES Entries $ SHOW LOGICAL/TABLE=LNM$SLS$VALUES (LNM$SLS$VALUES) "BACKUP_DEFAULT_REEL" = " " "BACKUP_FINISH" = "MAIL" "BACKUP_QUEUE" = "SLS$THUNDR/NOSPOOL" "CLEANUP_Q" = "SLS$THUNDR/AFTER=03:00" "DEFAULT_ALLDEV" = "THUNDR$MUB0,THUNDR$MUC0,THUNDR$MUC2,THUNDR$MUA3,THUNDR$MUA1 " "DEFAULT_ALLOCSCRATCH" = "365 0:0:0" "DEFAULT_ALLOCSIZE" = "0" "DEFAULT_ALLTIM" = "0 0:0:30" "DEFAULT_BACKUPSCRATCH" = "365 0:0:0" "DEFAULT_BACKUPSIZE" = "0" "DEFAULT_BAKFMT" = "BACKUP" "DEFAULT_BAKOPT" = "YYYYYY" "DEFAULT_BAKUIC" = "0" "DEFAULT_BATCHQUEUE" = "SLS$THUNDR" "DEFAULT_DENS_1" = "6250" "DEFAULT_DENS_10" = " " "DEFAULT_DENS_11" = " " "DEFAULT_DENS_12" = " " "DEFAULT_DENS_13" = " " "DEFAULT_DENS_14" = " " "DEFAULT_DENS_15" = " " "DEFAULT_DENS_16" = " " "DEFAULT_DENS_17" = " " "DEFAULT_DENS_18" = " " "DEFAULT_DENS_19" = " " "DEFAULT_DENS_2" = "1600" "DEFAULT_DENS_20" = " " "DEFAULT_DENS_21" = " " "DEFAULT_DENS_22" = " " "DEFAULT_DENS_23" = " " "DEFAULT_DENS_24" = " " "DEFAULT_DENS_25" = " " "DEFAULT_DENS_26" = " " "DEFAULT_DENS_27" = " " "DEFAULT_DENS_28" = " " "DEFAULT_DENS_29" = " " "DEFAULT_DENS_3" = "800" (continued on next page) Files and Logical Names C-27 Example C-1 (Cont.) Sample List of LNM$SLS$VALUES Entries "DEFAULT_DENS_30" = " " "DEFAULT_DENS_31" = " " "DEFAULT_DENS_32" = " " "DEFAULT_DENS_4" = "COMP" "DEFAULT_DENS_5" = "NOCOMP" "DEFAULT_DENS_6" = " " "DEFAULT_DENS_7" = " " "DEFAULT_DENS_8" = " " "DEFAULT_DENS_9" = " " "DEFAULT_DRIVES_1" = "THUNDR$MUB0" "DEFAULT_DRIVES_10" = " " "DEFAULT_DRIVES_11" = " " "DEFAULT_DRIVES_12" = " " "DEFAULT_DRIVES_13" = " " "DEFAULT_DRIVES_14" = " " "DEFAULT_DRIVES_15" = " " "DEFAULT_DRIVES_16" = " " "DEFAULT_DRIVES_17" = " " "DEFAULT_DRIVES_18" = " " "DEFAULT_DRIVES_19" = " " "DEFAULT_DRIVES_2" = "THUNDR$MUB0" "DEFAULT_DRIVES_20" = " " "DEFAULT_DRIVES_21" = " " "DEFAULT_DRIVES_22" = " " "DEFAULT_DRIVES_23" = " " "DEFAULT_DRIVES_24" = " " "DEFAULT_DRIVES_25" = " " "DEFAULT_DRIVES_26" = " " "DEFAULT_DRIVES_27" = " " "DEFAULT_DRIVES_28" = " " "DEFAULT_DRIVES_29" = " " "DEFAULT_DRIVES_3" = " " "DEFAULT_DRIVES_30" = " " "DEFAULT_DRIVES_31" = " " "DEFAULT_DRIVES_32" = " " "DEFAULT_DRIVES_4" = "THUNDR$MUA4 " "DEFAULT_DRIVES_5" = "THUNDR$MUA3" "DEFAULT_DRIVES_6" = "THUNDR$MUC0,THUNDR$MUC2,THUNDR$MUA1" "DEFAULT_DRIVES_7" = " " (continued on next page) Files and Logical Names Example C-1 (Cont.) Sample List of LNM$SLS$VALUES Entries "DEFAULT_DRIVES_8" = " " "DEFAULT_DRIVES_9" = " " "DEFAULT_FRESTA" = "2" "DEFAULT_MAXSCRATCH" = "31-DEC-9999 23:59:59.99" "DEFAULT_MTYPE_1" = "9TRACK" "DEFAULT_MTYPE_10" = " " "DEFAULT_MTYPE_11" = " " "DEFAULT_MTYPE_12" = " " "DEFAULT_MTYPE_13" = " " "DEFAULT_MTYPE_14" = " " "DEFAULT_MTYPE_15" = " " "DEFAULT_MTYPE_16" = " " "DEFAULT_MTYPE_17" = " " "DEFAULT_MTYPE_18" = " " "DEFAULT_MTYPE_19" = " " "DEFAULT_MTYPE_2" = "9TRACK" "DEFAULT_MTYPE_20" = " " "DEFAULT_MTYPE_21" = " " "DEFAULT_MTYPE_22" = " " "DEFAULT_MTYPE_23" = " " "DEFAULT_MTYPE_24" = " " "DEFAULT_MTYPE_25" = " " "DEFAULT_MTYPE_26" = " " "DEFAULT_MTYPE_27" = " " "DEFAULT_MTYPE_28" = " " "DEFAULT_MTYPE_29" = " " "DEFAULT_MTYPE_3" = "9TRACK" "DEFAULT_MTYPE_30" = " " "DEFAULT_MTYPE_31" = " " "DEFAULT_MTYPE_32" = " " "DEFAULT_MTYPE_4" = "TA90E" "DEFAULT_MTYPE_5" = "TA90E" "DEFAULT_MTYPE_6" = "RV02K" "DEFAULT_MTYPE_7" = " " "DEFAULT_MTYPE_8" = " " "DEFAULT_MTYPE_9" = " " "DEFAULT_PROTECTION" = "307" "DEFAULT_RESOPT" = " Y NY" "DEFAULT_SELDEV" = "THUNDR$MUB0,THUNDR$MUC0,THUNDR$MUC2,THUNDR$MUA3,THUNDR$MUA1 " (continued on next page) Files and Logical Names C-29 Example C-1 (Cont.) Sample List of LNM$SLS$VALUES Entries "DEFAULT_USRRSS" = "128" "DEFAULT_VERBOSE" = "1" "ESC_ALLOC_BOLD" = ". .[1m" "ESC_ALLOC_NORM" = ". .[m" "ESC_LOAD_BLNK" = ".[5m.[7w" "ESC_LOAD_BOLD" = ".[1m.[7w" "ESC_LOAD_NORM" = ".[m.[w" "ESC_MOUNT_BOLD" = ". .[1m" "ESC_MOUNT_NORM" = ". .[m" "ESC_MOUNT_OPER" = "...[1m.#6 OPERATOR:" "LOCATION" = "HEADQUARTERS" "MGRPRI" = "8" "NET_REQUEST_TIMEOUT" = "15" "NODENAME" = "THUNDR" "PRIV_CLEAN" = "OPER" "PRIV_LABEL" = "OPER" "PRIV_MAXSCR" = "OPER" "PRIV_MODANY" = "OPER" "PRIV_MODOWN" = "TMPMBX" "PRIV_SEEANY" = "OPER" "PRIV_V_CLEAN" = "18" "PRIV_V_LABEL" = "18" "PRIV_V_MAXSCR" = "18" "PRIV_V_MODANY" = "18" "PRIV_V_MODOWN" = "15" "PRIV_V_SEEANY" = "18" "QUICKLOAD" = "1" "QUICKLOAD_RETRIES" = "80" "REMOTE_RETRIES" = "5" "RESTORE_FINISH" = "MAIL" "RESTOR_QUEUE" = "SLS$THUNDR/NOSPOOL" "SLS$UNATTENDED_BACKUPS" = "0" "STANDBY_ARCHIVE_INT" = "00:00:30" "STANDBY_ARCHIVE_LOG" = "SBARLOG" "STANDBY_ARCHIVE_START" = "0" "SYSCLN_RUN" = "WED=03,FRI=03,SAT=51 " "TAPEPURGE_MAIL" = "SYSTEM " "TAPEPURGE_WORK" = "MAIL " "TOPERMASK" = "1024" (continued on next page) Files and Logical Names Example C-1 (Cont.) Sample List of LNM$SLS$VALUES Entries "TOPERSTRING" = "TAPES" "TRANS_AGE" = "14 0:0:0" "USERBACK_FIRSTLINE" = "$!" "USERNAME" = "SLS" "VERSION" = "V2.8A" "VMSBU" = "VMSBUXX" "VMSV5" = "1" Table C-4 lists logical names that control whether or not SLS software unloads a drive when it dismounts a volume. In some cases, you may not want the drive to unload. These logical names are defined in the logical name table LNM$SLS$VALUES. Files and Logical Names C-31 There are two options: o To have the drive unload, define the logical as /UNLOAD. o To have the drive not unload, define the logical as /NOUNLOAD. Table_C-4__Unload_Drive_Logicals___________________________ Logical in LNM$SLS$VALUES_Table__Description__________________________ ARCHIVE_DISM_QUALS For standby archiving operations executed with the STORAGE SAVE command BACKUPXEQ_DISM_QUALS For user backup operations executed with the STORAGE SAVE command RESTORXEQ_DISM_QUALS For user restore operations executed with the STORAGE RESTORE command SYSBAK_DISM_QUALS For system backup operations SYSRES_DISM_QUALS_____For_system_restore_operations________ Files and Logical Names D ______________________________________________________________ SLS Account User Authorization Data Authorization Data Table D-1 lists AUTHORIZE qualifiers used to update the SLS account with values recommended for SLS software. They are also used when the account is being created. Table_D-1__SLS_Account_User_Authorization_Data_____________ Authorization field and_value_____________Description__________________________ /MAXJOBS=0 Maximum number of interactive, batch, and detached processes that can be active at one time with this user name is unlimited. ___________________________________________________________ /MAXACCTJOBS=0 Maximum number of interactive, batch, and detached processes on the same account that can be active at one time is unlimited. ___________________________________________________________ /MAXDETACH=0 Maximum number of detached processes with this user name that may be active at one time is unlimited. ___________________________________________________________ /PRCLM=10 Total number of subprocesses that may be active at one time. ___________________________________________________________ (continued on next page) SLS Account User Authorization Data D-1 Table_D-1_(Cont.)__SLS_Account_User_Authorization_Data_____ Authorization field and_value_____________Description__________________________ /PRIORITY=4 Default base priority. ___________________________________________________________ /QUEPRIO=4 Default queue priority. ___________________________________________________________ /CPU=(none) Maximum amount of CPU time is unlimited. ___________________________________________________________ /FILLM=500 Total number of files and network logical links that may be active at one time. ___________________________________________________________ /SHRFILLM=0 Maximum number of shared files that may be open at one time is unlimited. ___________________________________________________________ /BIOLM=128 Maximum number of buffered I/O operations that may be active at one time. ___________________________________________________________ /DIOLM=4096 Maximum number of direct I/O operations that may be active at one time. ___________________________________________________________ /ASTLM=4096 Maximum number of pending AST requests that may be queued for the user 0. ___________________________________________________________ (continued on next page) SLS Account User Authorization Data Table_D-1_(Cont.)__SLS_Account_User_Authorization_Data_____ Authorization field and_value_____________Description__________________________ /ENQLM=1000 Total number of lock requests that may be outstanding at the same time. ___________________________________________________________ /BYTLM=128000 Total number of bytes that may be specified for a buffered I/O operation. ___________________________________________________________ /PBYTLM=0 Paged pool byte count limit (unlimited). ___________________________________________________________ /JTQUOTA=1024 Byte count quota of the job-wide logical name table. ___________________________________________________________ /WSDEF=1024 Initial limit of a working set for the user process. ___________________________________________________________ /WSQUO=16384 Maximum to which the user's process may raise the working set limit when system memory is in demand. ___________________________________________________________ /WSEXTENT=16384 Maximum to which the user's process may raise its working set limit when there is free memory available. ___________________________________________________________ /PGFLQUO=100000 Total pages that this process can use in the system paging file. ___________________________________________________________ (continued on next page) SLS Account User Authorization Data D-3 Table_D-1_(Cont.)__SLS_Account_User_Authorization_Data_____ Authorization field and_value_____________Description__________________________ /BATCH Allows unrestricted access hours for batch jobs for this user name. ___________________________________________________________ /NOINTER Disallows interactive logins for this user name. ___________________________________________________________ /NOLOCAL Disallows interactive logins for this user name through a local terminal. ___________________________________________________________ /NODIAL Disallows interactive logins for this user name through dialup terminals. ___________________________________________________________ /NOREM Disallows interactive logins for this user name through network remote terminals. ___________________________________________________________ /NOEXPIRATION Account is not expired. ___________________________________________________________ /PWDEXPIRED Password is expired. ___________________________________________________________ (continued on next page) SLS Account User Authorization Data Table_D-1_(Cont.)__SLS_Account_User_Authorization_Data_____ Authorization field and_value_____________Description__________________________ /FLAGS= NODISUSER-Does not disable account completely. NOAUDIT-Does not audit all security relevant actions. DEFCLI-Prevents user from changing default CLI or CLI tables. NODISCTLY-Allows Ctrl/Y interrupts. DISMAIL-Prevents mail delivery to this user. DISNEWMAIL-Suppresses "New Mail..." announcements. DISRECONNECT-Disables automated reconnections. NODISREPORT-Disables time of last login and other security reports. NOGENPWD-Does not require user to use generated passwords. Note: These should be enclosed in parentheses and, if more than one is specified, separated by commas. ___________________________________________________________ /UIC= UIC as specified by the installer. ___________________________________________________________ /OWNER="SLS_MANAGER"__Name_of_the_account_owner.___________ SLS Account User Authorization Data D-5 ___________________________________________________________ Index How to _________________________ register (cont'd) files, 3-8 PAK, 1-11 SLS license, 1-11 shutdown SLS software, 1-8_________________________ unload the SLS license, 1-9 the I___________________________the systemwide 3-2 Installation before you begin, 2-1 requirements, 1-1_________________________ L______________________________ node, C-14tbl Licensing client software, 1-8 to determine, 1-4 how to register, 1-11 server software, 1-8 unloading, 1-9_________________________ where to find information, 1-11 1-3 LNM$JOB entries, C-26tbl LNM$SLS$TABLE entries, C-26tbl free LNM$SLS$VALUES entries systemwide for drive dismounts, C-31tbl 3-2 sample, C-26fig the LNM$SYSTEM_TABLE entries, C-24tbl client Logical names, C-24tbl LNM$JOB, C-24 LNM$SLS$TABLE, C-23 software, LNM$SLS$VALUES, C-26 software, LNM$SYSTEM_TABLE, C-23 Index-1 installation, 1-1, 1-2 client software, 1-6____________________________ server software, 1-5 operating classes OpenVMS operating system classes, 1-2 1-2 quotas, 1-2 software, 1-6 ____________________________ client, 1-7 server, 1-7 Product Authorization Key S______________________________ systemwide command SLS$CUSTOM, 3-8 files, 3-2 Software the system login client, 1-6 file, 3-2 how to install, 2-2 Authorization Key, how to install, 2-2 1-11 kit name, 1-9 1-11 license name, 1-9 optional, 1-7 requirements, 1-6____________________________ client, 1-7 server, 1-7 Remote server, 1-5 Device defining a network object, support, 3-3 3-10 how to install, 2-2 support, shutting down SLS, 1-8 System startup procedure, 3-2 space, 1-3