Storage_Library_System_for_OpenVMS__________________ Installation and Configuration Guide Order Number: AA-KY16R-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-KY16Q-TE). Software Version: Storage Library System For OpenVMS Version 2.9C ________________________________________________________________ March 1999 Possession, use, or copying of the software described in this documentation is authorized only pursuant to a valid written license from COMPAQ, an authorized sublicenser, or the identified licenser. While COMPAQ believes the information included in this publication is correct as of the date of publication, it is subject to change without notice. Compaq Computer 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 Compaq Computer Corporation 1997, 1998, 1999. All Rights Reserved. All Rights Reserved. Printed in the United States of America. COMPAQ, DIGITAL, DIGITAL UNIX, and the COMPAQ and DIGITAL logos Registered in U.S. Patent and Trademark Office. DECconnect, HSZ, StorageWorks, VMS, and OpenVMS are trademarks of Compaq Computer 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. 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. All other trademarks and registered trademarks are the property of their respective holders. This document was prepared using VAX DOCUMENT Version 2.1. _________________________________________________________________ Contents Preface................................................... vii 1 Introduction to the Storage Library System for OpenVMS 1.1 What is SLS?.................................. 1-1 1.1.1 SLS Product Functions..................... 1-2 1.1.2 SLS Product Features...................... 1-2 1.1.3 SLS Device Support........................ 1-4 1.2 Mixed Architecture Environments............... 1-4 1.2.1 Mixed Architecture Environments........... 1-5 1.2.2 Principles Guiding Mixed Architecture Configuration............................. 1-5 1.2.3 Configuring Applications in a Mixed Architecture OpenVMS Cluster.............. 1-6 1.2.3.1 Separate Disk Configuration............. 1-6 1.2.3.2 Separate Root Configuration............. 1-7 1.2.3.3 Separate Subdirectory Configuration..... 1-7 1.2.4 Implementation Specific Approach.......... 1-8 2 Before Installing SLS 2.1 Preinstallation Process....................... 2-1 2.2 Configuring Your Hardware..................... 2-2 2.2.1 Hardware Configuration For an Automated Media Library............................. 2-3 2.2.1.1 Hardware Installation................... 2-3 2.2.1.2 Test the Hardware....................... 2-3 2.2.2 Hardware Configuration for a Media Loader.................................... 2-4 2.2.2.1 Hardware Installation................... 2-5 2.2.2.2 Test the Hardware....................... 2-5 iii 2.2.3 Hardware Configuration for an Operator Attended Drive............................ 2-6 2.2.3.1 Hardware Installation................... 2-6 2.2.3.2 Test the Hardware....................... 2-7 2.3 Quotas and OpenVMS Operating System Classes... 2-7 2.3.1 Required Quotas........................... 2-8 2.3.2 Required OpenVMS Operating System Classes................................... 2-8 2.4 Hardware Requirements......................... 2-8 2.5 Client and Server Definitions................. 2-11 2.5.1 Server Software .......................... 2-11 2.5.2 Client Software .......................... 2-12 2.6 Software Requirements......................... 2-12 2.6.1 Prerequiste for Installing on Open VMS Version 7.2............................... 2-13 2.6.2 Server Software Requirements.............. 2-14 2.6.3 Client Software Requirements.............. 2-15 2.6.4 Optional Software......................... 2-15 2.7 Shutting Down the Previous Version of SLS Software...................................... 2-16 2.8 Registering the SLS Software License.......... 2-16 2.8.1 License and Kit Names..................... 2-17 2.8.2 Unloading the Current SLS License......... 2-17 2.8.3 Registering Your New SLS License.......... 2-19 3 Installing the SLS Software 3.1 Before You Begin-Questions and Answers........ 3-1 3.2 Installing the SLS Software................... 3-2 3.3 Configuring SLS in a Mixed Architecture Environment................................... 3-10 3.3.1 How to Configure for a Mixed-Architecure Environment............................... 3-11 4 After Installing SLS 4.1 Verifying the Installation.................... 4-1 4.2 Editing the Systemwide Command Files.......... 4-2 4.2.1 Automatically Starting SLS................ 4-2 4.2.2 Defining Global Symbols for SLS Users..... 4-2 4.3 Preparing SLS Server Software................. 4-2 4.3.1 Defining a DECnet Network Object on an OpenVMScluster System..................... 4-3 iv 4.3.2 Defining the DECnet Phase V Network Object for SLS................................... 4-5 4.3.2.1 Issue the Commands on Currently Running Nodes................................... 4-5 4.3.2.2 Defining the SLS$DBX network object in the NET$APPLICATION_STARTUP.NCL File.... 4-5 4.3.3 Authorizing SLS Volume Database and Pool Access.................................... 4-8 4.4 Configuring SLS to Work With Specific VMS Versions...................................... 4-9 4.4.1 Version-Specific Files.................... 4-10 4.4.2 Upgrading OpenVMS Versions after Installing SLS............................ 4-11 4.5 Upgrading from a Previous Version............. 4-12 4.5.1 Reviewing Outdated Files from SLS$CUSTOM................................ 4-12 4.5.2 Updating the Command File TAPESTART.COM... 4-13 4.6 Configuring Media and Device Support.......... 4-14 4.6.1 Configuring MDMS for an Automated Tape Library System............................ 4-14 4.6.1.1 Configure MDMS for an ATL............... 4-15 4.6.1.2 Test the MDMS ATL Configuration......... 4-16 4.6.2 Configuring MDMS for a Media Loader....... 4-18 4.6.2.1 Configure MDMS for a Media Loader....... 4-18 4.6.2.2 Test the MDMS Media Loader Configuration........................... 4-20 4.6.3 Configuring for an Operator Attended Drive..................................... 4-22 4.6.3.1 Configure MDMS for an Operator Attended Device.................................. 4-22 4.6.3.2 Test the MDMS Configuration............. 4-23 4.6.4 Configuring Remote Tape or Optical Drives.................................... 4-24 4.6.4.1 On The System Where the Tape or Optical Drive Resides........................... 4-24 4.6.4.2 On The System Where the Data Resides.... 4-26 4.7 Configuring Remote Device Facility Support.... 4-26 4.7.1 Adding RDF Client Support................. 4-26 4.7.2 Adding RDF Server Support................. 4-27 v A SLS Server Installation Example Log File A.1 SLS Server Installation Log-Part 1............ A-1 A.2 SLS Server Installation Log-Part 2............ A-4 B Files and Logical Names B.1 Files......................................... B-1 B.2 Logical Names................................. B-23 C SLS Account User Authorization Data C.1 Authorization Data............................ C-1 Index Examples B-1 Sample List of LNM$SLS$VALUES Entries..... B-26 Tables 2-1 Preinstallation Tasks..................... 2-1 2-2 Verifying Disk Space Requirements......... 2-9 2-3 How to Start DECnet and OpenVMS Queue Manager................................... 2-15 2-4 Software License Names.................... 2-17 2-5 How to Unload the Server or Client Software License.......................... 2-17 2-6 How to Register Your SLS Server or Client License................................... 2-19 3-1 Installation Questions and Answers........ 3-2 3-2 How to Install the SLS Server or Client Software.................................. 3-2 3-3 How to Configure SLS in a Mixed Architecture OpenVMS Cluster System....... 3-11 3-4 Comparing Logical Definitions Between VAX and Alpha Systems......................... 3-13 4-1 How to Define the SLS$DBX NCP Object...... 4-3 4-2 How to Enable Client Node Access to the SLS Volume Database....................... 4-9 vi 4-3 SLS Files for Specific OpenVMS Versions... 4-11 4-4 How to Update the Command File TAPESTART.COM............................. 4-13 4-5 Enabling Remote Drive Selection........... 4-24 B-1 Files Installed on Server Nodes........... B-1 B-2 Files Installed on Client Nodes .......... B-14 B-3 Logical Name Table Entries................ B-24 B-4 Unload Drive Logicals..................... B-32 C-1 SLS Account User Authorization Data....... C-1 vii _________________________________________________________________ Preface Purpose 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:SLS029C.RELEASE_NOTES Intended 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. Document 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. vii Appendix D Lists SLS quota and account information. Related Documents The following documents are related to this documentation set or are mentioned in this manual: o Storage Library System for OpenVMS Command Reference Guide 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 Conventions 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. viii ___________________________________________________________ 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.____ Related Products The following related products are mentioned in this document: ___________________________________________________________ Product_______Description__________________________________ ABS ABS refers to Archive/Backup System for OpenVMS[TM] software. ix ___________________________________________________________ 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.____________________________ Determining 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. x 1 _________________________________________________________________ Introduction to the Storage Library System for OpenVMS This chapter defines the role of Digital's Storage Library System for OpenVMS (SLS) software product in storage management. 1.1 What is SLS? Storage Library System for OpenVMS (SLS) is a layered software product that provides support for saving copies of data and restoring those copies as necessary. _______________________ Warning _______________________ Due to changes in functionality and database structure, SLS software versions 2.5B and later are incompatible with SLS software version 2.4A and 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. ______________________________________________________ Storage administrators face three primary storage management problems that SLS software helps to solve: o Ensuring data is available in the event of a disaster o Maintaining data in some form for regulatory and legal purposes o Providing sufficient online storage space to meet users' needs Introduction to the Storage Library System for OpenVMS 1-1 Introduction to the Storage Library System for OpenVMS 1.1 What is SLS? 1.1.1 SLS Product Functions SLS allows you to do the following things: o Backup (save copies of) data files on an as-needed basis o Backup groups of files or entire disks on a scheduled basis for maintenance purposes o Restore previously-saved files or disks after a disaster occurs o Move data from online storage to offsite storage (archive) when files no longer need to be available for frequent use o Generate reports about saved data 1.1.2 SLS Product Features Backup and Restore Features SLS provides the following backup and restore features: o Automatic, flexible scheduling for backup operations o Support through the Remote Device Facility (RDF) for remote backup and archiving operations between devices located on different systems within a DECnet network, provided all are running SLS o Online catalog containing information about backed up data o Ability to restore data through the catalog without the user having to search for where the data is stored o Integration with RMU/BACKUP and RMU/RESTORE for backing up and restoring Oracle Rdb databases o DCL commands and menu interfaces o Customization features to meet a variety of site- specific and operational storage needs o Support for user-initiated as well as system-initiated backup operations 1-2 Introduction to the Storage Library System for OpenVMS Introduction to the Storage Library System for OpenVMS 1.1 What is SLS? Media and Device Management Features SLS provides the following media and device management features: o Volume database containing information about volumes that SLS can use o Magazine database relating individual volumes to multi- volume magazines and magazine-loader jukebox devices o Media life cycle control, including maintenance of volume retention periods, availability status, location, and scheduling of dates for volumes to move offsite and return o Volume counters noting the number of times the volume has been mounted and the number of errors associated with the volume; these counters are used to schedule volume cleaning o Volume access control based on user-defined volume pools o Media and device configurations using TAPESTART.COM to define devices available for use and the media they support o Support for a variety of media and devices, ranging from single-drive TK50 devices to robotically-controlled StorageTek silos and automated tape library systems Introduction to the Storage Library System for OpenVMS 1-3 Introduction to the Storage Library System for OpenVMS 1.1 What is SLS? 1.1.3 SLS Device Support SLS supports a large array of storage devices, ranging from single-tape drives to automated optical and tape jukeboxes. See the SLS SPD for a complete list of supported devices. 1.2 Mixed Architecture Environments _ Before You Install your Storage Management Software _ If you are planning to install SLS software in a mixed architecture OpenVMS Cluster, you should understand the configuration issues explained in this section. If you do not consider these configuration issues, you could spend considerable time deleting and editing files, and reinstalling the software. ______________________________________________________ This section addresses the characteristics of a mixed architecture environment and describes some fundamental approaches to installing and configuring your software to run in it. The following list identifies the topics and their purposes o Section 1.2.1 defines the mixed architecture environment and discusses ways in which they can come about, change, then disappear. Each of these occurrences requires some consideration about how to configure your software. o Section 1.2.2 lists the guiding principles that require you to make special considerations for mixed architecture implementation, and what these principles mean to you. o Section 1.2.3 describes three possible approaches to implementing a mixed architecture environment. o Section 1.2.4 explains why the documentation includes procedures for a specific approach. If you cannot use the documented procedures, you should decide on an approach before you begin installation. 1-4 Introduction to the Storage Library System for OpenVMS Introduction to the Storage Library System for OpenVMS 1.2 Mixed Architecture Environments 1.2.1 Mixed Architecture Environments A mixed architecture OpenVMS Cluster includes at least one VAX system and at least one Alpha system. Creating_a_Mixed_Architecture_Configuration: If you add an Alpha system to a homogenous VAX OpenVMS Cluster, or if you are currently running a homogenous Alpha OpenVMS Cluster and inherit a VAX system, you will have a mixed architecture environment. Before you integrate the Alpha or VAX node into the system, you should decide an approach to take for handling mixed architecture issues. Operating_a_Mixed_Architecture_Configuration: If you are currently operating a mixed architecture environment, and you want to add a VAX system or an Alpha system you must integrate it into your current configuration consistently with your other applications. You should understand the particular requirements of any new application you introduce into a mixed architecture OpenVMS Cluster. Dissolving_a_Mixed_Architecture_Configuration: If you remove the last VAX or Alpha system, leaving a homogenous OpenVMS Cluster, you should remove any aspects of configuration that accounted for the heterogenous nature of the mixed architecture system. This includes (but is not limited to) removing startup files, duplicate directory structures, and logical tables. 1.2.2 Principles Guiding Mixed Architecture Configuration Limitations: VAX systems cannot execute image files compiled on an Alpha system, and Alpha systems cannot execute image files compiled on a VAX system. Other types of files cannot be shared, including object code files (.OBJ), and user interface description files (.UID). You must place files that cannot be shared in different locations: VAX files accessible only to VAX OpenVMS Cluster nodes, and Alpha files accessible only to Alpha OpenVMS Cluster nodes. Introduction to the Storage Library System for OpenVMS 1-5 Introduction to the Storage Library System for OpenVMS 1.2 Mixed Architecture Environments Data files, in most cases, must be shared between OpenVMS Cluster nodes. You should place all shared files in directories accessible by both VAX and Alpha OpenVMS Cluster nodes. Logical names, that reference files which cannot be shared, or the directories in which they reside, must be defined differently on VAX and Alpha systems. Files that assign logical name values must therefore be architecture specific. Such files may either reside on node-specific disks or shared only among OpenVMS Cluster nodes of the same hardware architecture. 1.2.3 Configuring Applications in a Mixed Architecture OpenVMS Cluster This section describes three approaches to configuring applications to run in a mixed architecture OpenVMS Cluster. The one you choose depends on your existing configuration, and the needs of the particular application you are installing. These approaches are given as examples only. You should decide which you want to implement based on your own situation and style of system management. All of these approaches have two aspects in common: o All shared files reside in one location o All files that cannot be shared reside in separate locations 1.2.3.1 Separate Disk Configuration These characteristics describe the separate disk configuration: o Product directories are installed on two separate disks. o One of the product directories is a complete installation containing all data (and other shared) files, and all executable (and other nonshared) files for either VAX or Alpha systems. o The other of the product directories is a partial product installation, with only those directories that contain either Alpha or VAX system executables and other nonshared files. 1-6 Introduction to the Storage Library System for OpenVMS Introduction to the Storage Library System for OpenVMS 1.2 Mixed Architecture Environments o The systems using the disk with the complete installation uses logicals that normally reference the product executables and shared files. o The systems using the disk with only the nonshared files use normal product logical definitions to point to shared files and directories. System logicals that point to nonshared files are assigned to the specific device, directory and/or file names. 1.2.3.2 Separate Root Configuration These characteristics describe the separate root configuration: o Product directories are installed on the same disk, but at different root locations. o One of the product directories is a complete installation containing all data (and other shared files), and all executable (and other nonshared) files for either VAX or Alpha systems. o The other of the product directories is a partial product installation, with only those subdirectories that contain either Alpha or VAX system executables and other nonshared files. o The systems using the directory with the complete installation uses logicals that normally reference the product executables and shared files. o The systems using the directory with only the nonshared files use normal product logical definitions to point to shared files and directories. System logicals that point to nonshared files are assigned to the specific device, directory and/or file names. 1.2.3.3 Separate Subdirectory Configuration These characteristics describe the separate directory configuration: o Product directories are installed on the same disk, and under the same root. o Any directory which would normally contain the nonshared files (under a single architecture installation) has two subdirectories: one for VAX system nonshared files, and one for Alpha system nonshared files. Introduction to the Storage Library System for OpenVMS 1-7 Introduction to the Storage Library System for OpenVMS 1.2 Mixed Architecture Environments o Logicals that reference nonshared files are assigned search list values that point to the directories which holds shared files, and to the architecture specific subdirectories holding nonshared files. 1.2.4 Implementation Specific Approach This document includes specific procedures for a recommended approach based on current product configuration and the behavior of the installation software with respect to its use of logical definitions during upgrades. If the recommended approach is inconsistent with the way you currently manage your system, you should decide on a different approach before you begin your installation procedures. 1-8 Introduction to the Storage Library System for OpenVMS 2 _________________________________________________________________ Before Installing SLS This chapter explains preinstallation requirements for SLS. 2.1 Preinstallation Process This section describes what you need to do before you run the SLS, Version 2.9C installation procedure. Table 2-1 identifies actions you need to take to prepare for installing the SLS, Version 2.9C 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. ___________ Important - during Installation ___________ Installing SLS Version 2.9C requires DECnet to be enabled throughout the process. Before you begin installing make sure DECnet is enabled. ______________________________________________________ Table_2-1_Preinstallation_Tasks____________________________ Stage_Action_______________________________________________ 1 Configure and Verify Hardware Connections ___________________________________________________________ 2 Verify required quotas and OpenVMS operating system classes. (continued on next page) Before Installing SLS 2-1 Before Installing SLS 2.1 Preinstallation Process Table_2-1_(Cont.)_Preinstallation_Tasks____________________ Stage_Action_______________________________________________ ___________________________________________________________ 3 Check that the system on which you intend to install SLS meets hardware and software requirements. ___________________________________________________________ 4 Shut down previous versions of SLS software on all nodes of the cluster on which SLS software will be installed. ___________________________________________________________ 5 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. ___________________________________________________________ 6_____Register_the_SLS_license.____________________________ 2.2 Configuring Your Hardware ________________ MDMS Component of SLS ________________ The hardware configuration activities described in these sections refer to MDMS, which is an integral component of SLS. ______________________________________________________ This section describes how to configure automated media libraries, media loaders, and operator attended drives to enable MDMS to provide a managed media environment. This means installing, connecting, and testing the tape drives. Each procedure depends on the kind of tape drive that you plan to use. Use the procedures appropriate for the tape drives you plan to include in the managed media environment: o For an automated media library, refer to Section 2.2.1. o For a media loader, refer to Section 2.2.2. o For an operator attended drvie, refer to Section 2.2.3. 2-2 Before Installing SLS Before Installing SLS 2.2 Configuring Your Hardware 2.2.1 Hardware Configuration For an Automated Media Library The following procedure applies to the installation and testing of an automated media library. Configuration and testing of MDMS to manage an automated media library is described in Chapter 4. 2.2.1.1 Hardware Installation During this procedure, refer to the drive-specific hardware installation procedure information for details. The following procedure provides only the basic steps necessary to later configure MDMS against the drive: 1. Install and connect the hardware. Apply power to the drives. 2. If you are using an HSx controller, configure it to allow the OpenVMS system to communicate with the drives. 3. Make note of the drive name after you complete your connection procedure. You will need this, especially if you are going to use the Media Robot Utility software. 2.2.1.2 Test the Hardware With an automated media library, use a utility such as the Media Robot Utility (MRU) or use the front panel of the drive and the OpenVMS system to test the connection between the host and drive. Use the following procedure to test the hardware connection between the automated tape library and the OpenVMS system: 1. Verify the robot device name and the drive names located in the automatic tape library. Issue the DCL SHOW DEVICE command and/or the ROBOT SHOW ROBOT command. If there is a problem with drive name or the connection, it becomes apparent here. $ SHOW DEVICE [drive-name[:]] The following is the StorageWorks Media Robot Utility command for examining the robot: $ ROBOT SHOW ROBOT [robot_name] If you have problems with the drive name, refer to the OpenVMS system and drive-specific hardware documentation for remedial action. Before Installing SLS 2-3 Before Installing SLS 2.2 Configuring Your Hardware 2. Place a volume in the robot. 3. Inject the volume through a port on the robot by using the front panel controls or, if you are using StorageWorks Media Robot Utility, by issuing the ROBOT INJECT command: $ ROBOT INJECT [PORT port_number] SLOT slot_number [ROBOT robot_name] Alternately, you can expose the internal storage slots and place the volume directly into the robot. You also should consider placing one or more cleaning volumes into the robot at this time. 4. Load the volume into the drive by using the front panel controls or, if you are using MRU, by issuing the ROBOT SHOW and ROBOT LOAD command: $ ROBOT SHOW SLOT 0-n [ROBOT robot_name] $ ROBOT LOAD SLOT slot_num [ROBOT robot_name] 5. After loading the volume, check the OpenVMS system connection to the drive by mounting and dismounting the volume. Mount the volume foreign: $ MOUNT/FOREIGN/NOASSIST drive_name[:] Dismount the volume: $ DISMOUNT drive_name[:] 6. Remove the volume from the drive by using the front panel controls or, if you are using MRU, by issuing the ROBOT UNLOAD command: $ ROBOT UNLOAD SLOT slot_number [ROBOT robot_name] After having completed this procedure, the volume remains in the robot but is not loaded in the drive. 2.2.2 Hardware Configuration for a Media Loader The following procedure applies to the installation and testing of a media loader. Configuration and testing of MDMS to manage a media loader is described in Chapter 4. 2-4 Before Installing SLS Before Installing SLS 2.2 Configuring Your Hardware 2.2.2.1 Hardware Installation During this procedure, refer to the drive-specific hardware installation information for details. This procedure provides only the basic steps necessary to later configure MDMS against the drive: 1. Install and connect the hardware. Apply power to the drives. 2. If you are using an HSx controller, configure it to allow the OpenVMS system to communicate with the drives. 3. Make note of the drive name after you complete your connection procedure. You will need this, especially if you are going to use the Media Robot Utility software. 2.2.2.2 Test the Hardware With a media loader, use a utility such as the Media Robot Utility (MRU) or use the front panel of the drive and the OpenVMS system to test the connection between the OpenVMS system and drive. ________________________ Note ________________________ Before you perform this procedure, you must have a compatible, initialized volume in the robot. Use this initialized volume to perform this test. ______________________________________________________ Use the following procedure to test the hardware connection between the tape loader and the OpenVMS system: 1. Verify the changer device name and the drive names. Issue the DCL SHOW DEVICE command and/or the ROBOT SHOW ROBOT command. If there is a problem with drive name or the connection, it becomes apparent here: $ SHOW DEVICE [drive-name[:]] The following is the MRU command for examining the robot: $ ROBOT SHOW ROBOT [robot_name] If you have problems with the drive name, refer to the drive-specific hardware documentation for remedial action. Before Installing SLS 2-5 Before Installing SLS 2.2 Configuring Your Hardware 2. Place a volume in a magazine; place the magazine into the drive. 3. Load a volume into the robot by using the front panel controls or, if you are using MRU, by issuing the ROBOT SHOW and ROBOT LOAD command: $ ROBOT SHOW SLOT 0-n [ROBOT robot_name] $ ROBOT LOAD SLOT slot_num [ROBOT robot_name] 4. After loading the volume, check the OpenVMS system connection to the drive by mounting and dismounting the volume. Mount the volume with the OpenVMS MOUNT/FOREIGN command: $ MOUNT/FOREIGN/NOASSIST drive_name[:] Dismount the volume with the OpenVMS DISMOUNT command. Be sure to include the /NOUNLOAD qualifier: $ DISMOUNT/NOUNLOAD drive_name[:] 5. Remove the volume from the drive by using the front panel controls or, if you are using MRU, by issuing the ROBOT UNLOAD command. $ ROBOT UNLOAD SLOT slot_number [ROBOT robot_name] After having completed this procedure, the magazine with the volume remains in the media loader, but it is not loaded in the drive. 2.2.3 Hardware Configuration for an Operator Attended Drive This procedure applies to the installation and testing of an operator attended drive. The configuration and testing of MDMS to manage the operator attended drive is described in Chapter 4. 2.2.3.1 Hardware Installation During this procedure, refer to the drive-specific hardware installation information for details. This procedure provides only basic steps necessary to later configure MDMS against the drive: 1. Install and connect the hardware. Apply power to the drive. 2-6 Before Installing SLS Before Installing SLS 2.2 Configuring Your Hardware 2. If you are using an HSx controller, configure it to allow the OpenVMS system to communicate with the drive. 3. Make note of the drive name after you complete your connection procedure. 2.2.3.2 Test the Hardware Use the following procedure to test the hardware installation and connection with the OpenVMS system: 1. Verify the drive names. Issue the DCL SHOW DEVICE command. If there is a problem with drive name or the connection, it becomes apparent here. $ SHOW DEVICE [drive-name[:]] If you have problems with the drive name, refer to the drive-specific hardware documentation for remedial action. 2. Load a volume into the drive. 3. After loading the volume, check the OpenVMS system connection to the drive by mounting and dismounting the volume. Mount the volume with the OpenVMS MOUNT/FOREIGN command. $ MOUNT/FOREIGN/NOASSIST drive_name[:] Dismount the volume with the OpenVMS DISMOUNT command. $ DISMOUNT drive_name[:] 4. Remove the volume from the drive. 2.3 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. Before Installing SLS 2-7 Before Installing SLS 2.3 Quotas and OpenVMS Operating System Classes 2.3.1 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. 2.3.2 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: For information about verifying these classes, refer to the Guide to Setting Up an OpenVMS System. 2.4 Hardware Requirements For a detailed list of supported hardware for the SLS, Version 2.9C 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.9C software: o A VAX[TM], MicroVAX[TM], VAXstation[TM], or Alpha[TM] system o Four megabytes of memory for VAX, or sixteen megabytes of memory for Alpha o One or more tape devices or optical disks, for stand- alone systems 2-8 Before Installing SLS Before Installing SLS 2.4 Hardware Requirements o One disk, such as a Digital RD-[TM] or RA-[TM] series disk o Disk space: Use the steps in Table 2-2 to ensure there is enough disk space to install SLS server or client software. Table_2-2_Verifying_Disk_Space_Requirements________________ Step__Action_______________________________________________ (continued on next page) Before Installing SLS 2-9 Before Installing SLS 2.4 Hardware Requirements Table_2-2_(Cont.)_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: 2-10 Before Installing SLS Before Installing SLS 2.4 Hardware Requirements $ SHOW AUDIT/ALL 2.5 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. 2.5.1 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 2-11 Before Installing SLS 2.5 Client and Server Definitions 2.5.2 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. 2.6 Software Requirements The following software is required to install either SLS, Version 2.9C server or client software: o OpenVMS VAX operating system, Version 5.5-2, 6.2, 7.1 or 7.2 or OpenVMS Alpha operating system, Version 6.2, 7.1 or 7.2. ________________________ Note ________________________ Storage Library System for OpenVMS, Version 2.9C software is not supported on systems running OpenVMS, Version 7.0 operating system software. ______________________________________________________ 2-12 Before Installing SLS Before Installing SLS 2.6 Software Requirements o DECnet[TM] communications software, Version 5.4 or later 2.6.1 Prerequiste for Installing on Open VMS Version 7.2 On Alpha Systems For OPENVMS V7.2 on Alpha systems the following patch must be installed before using SLS. Kit name: AXPVMS-VMS72_PTHREAD-V0100 Platform: ALPHA Facility: PTHREAD ECO Number: 01 Minimum Version: V7.2 Maximum Version: V7.2 Installation Rating: 3 Engineer's Name: Mary Sullivan Problem Manager's Name:Mary Sullivan Actual/Target Version: A-RAVEN_PLUS SCT entry: CLDNOTES 1710 Dependencies: N Supersedes: N Reboot: N Number of Images: [2] [FACILITY]IMAGES - BUILD CLASS / MIN-MAX VERSION -------------------------------------------------- [PTHREAD]PTHREAD$RTL.EXE - V72R01 / V7.2 / V7.2 [PTHREAD]PTHREAD$DBGSHR.EXE - V72R01 / V7.2 / V7.2 On VAX Systems For OPENVMS V7.2 on VAX systems the following patch must be installed before using SLS. Before Installing SLS 2-13 Before Installing SLS 2.6 Software Requirements Kit name: VAXPTHR01_072 Platform: VAX Facility: PTHREAD ECO Number: 01 Minimum Version: V7.2 Maximum Version: V7.2 Installation Rating: 3 Engineer's Name: Mary Sullivan Problem Manager's Name: Mary Sullivan Actual/Target Version: SCT entry: Dependencies: N Supersedes: N Reboot: N Number of Images: [2] [FACILITY]IMAGES - BUILD CLASS / MIN-MAX VERSION -------------------------------------------------- [PTHREAD]PTHREAD$RTL.EXE - V72R / V7.2 / V7.2 [PTHREAD]PTHREAD$DBGSHR.EXE - V72R / V7.2 / V7.2 This patch must be installed to help SLS flag the actual status-at-exit of any storage command, and make a graceful exit from the command upon its completion. Without this patch all error messages issued by SLS will be masked and the exit status will always be 'Normal Successful Completion'. This will cause all the SLS command procedures that check for 'status after a storage command' to malfunction because of the pseudo 'success status' even in case of a failure. 2.6.2 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 2-3 to start them. 2-14 Before Installing SLS Before Installing SLS 2.6 Software Requirements Table_2-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________________________________ 2.6.3 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 4.3.3. 2.6.4 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.9C 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 2-15 Before Installing SLS 2.7 Shutting Down the Previous Version of SLS Software 2.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. 2.8 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 2-16 Before Installing SLS Before Installing SLS 2.8 Registering the SLS Software License 2.8.1 License and Kit Names Refer to Table 2-4 for the license and kit names for the server or client software. Table_2-4_Software_License_Names___________________________ Software Type________License_Name_____Software_Kit_Name_____________ Server SLS SLS29 Client SLS-REMOTE SLSCLIENT29 ACS SLS-ACS None. Although you load the ACS license separately, SLS support for ACS installs as part of the standard _____________________________installation_process._________ 2.8.2 Unloading the Current SLS License If your existing SLS license has a termination date, follow the steps in Table 2-5 to unload the current SLS software license. After completing this procedure, you may register the new SLS server or client software license. Table_2-5_How_to_Unload_the_Server_or_Client_Software_License____ Enter the command for the appropriate Step_Action________________software_type:________________________ 1 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 2-17 Before Installing SLS 2.8 Registering the SLS Software License Table 2-5 (Cont.) How to Unload the Server or Client Software __________________License________________________________________ Enter the command for the appropriate Step_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. _________________________________________________________________ 2 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 _________________________________________________________________ 3 Disable the previous Server: SLS software $ LICENSE DISABLE SLS/AUTHORIZATION=key_value license. Client: $ LICENSE DISABLE SLS- REMOTE/AUTHORIZATION=key_value _________________________________________________________________ 4 Unload the previous Server: SLS software $ LICENSE UNLOAD SLS license. (continued on next page) 2-18 Before Installing SLS Before Installing SLS 2.8 Registering the SLS Software License Table 2-5 (Cont.) How to Unload the Server or Client Software __________________License________________________________________ Enter the command for the appropriate Step_Action________________software_type:________________________ Client: ___________________________$_LICENSE_UNLOAD_SLS-REMOTE___________ 2.8.3 Registering Your New SLS License If you need to register the new SLS license, follow the steps in Table 2-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_2-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 2-19 Before Installing SLS 2.8 Registering the SLS Software License Table 2-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) 2-20 Before Installing SLS Before Installing SLS 2.8 Registering the SLS Software License Table 2-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__ _________ Error messages during installation _________ Users may need to refer to the MDMS Version 2.9C Installation Guide for trouble shooting during the SLS 2.9C installation. ______________________________________________________ Before Installing SLS 2-21 3 _________________________________________________________________ Installing the SLS Software This chapter describes how to install SLS, Version 2.9C software. For an example server installation, see Appendix A. ___________________ 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. ______________________________________________________ _____________ Note: Version Compatibility _____________ SLS Version 2.9C 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. ______________________________________________________ 3.1 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 3-1 Installing the SLS Software 3.1 Before You Begin-Questions and Answers Table_3-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 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. 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.____________________ 3.2 Installing the SLS Software Follow the steps in Table 3-2 to install SLS server or client software. Table_3-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) 3-2 Installing the SLS Software Installing the SLS Software 3.2 Installing the SLS Software Table 3-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 SLSC029 location: OPTIONS N Client software $@SYS$UPDATE:VMSINSTAL SLSCLIENTC029 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 3-3 Installing the SLS Software 3.2 Installing the SLS Software Table 3-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) 3-4 Installing the SLS Software Installing the SLS Software 3.2 Installing the SLS Software Table 3-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.9C (client and server) is not compatible with any previous * * versions of SLS prior to V2.5. If any node in a client-server * * configuration is running a version later than V2.5, then all * * nodes in the configuration must be running that same version or * * higher. An exception can be made if none of the SLS nodes * * serve a SLS$MAGAZINE_MASTER_FILE.DAT database. * * * ************************************************************************ * Do you want to continue with this installation [No]? Y System nodes running SLS Version 2.9C 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.9C 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 3-5 Installing the SLS Software 3.2 Installing the SLS Software Table 3-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 2.8, 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 4.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) 3-6 Installing the SLS Software Installing the SLS Software 3.2 Installing the SLS Software Table 3-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 2.4 and press . ___________________________________________________________ (continued on next page) Installing the SLS Software 3-7 Installing the SLS Software 3.2 Installing the SLS Software Table 3-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) 3-8 Installing the SLS Software Installing the SLS Software 3.2 Installing the SLS Software Table 3-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 3-9 Installing the SLS Software 3.2 Installing the SLS Software Table 3-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 C 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.________________________ 3.3 Configuring SLS in a Mixed Architecture Environment DIGITAL recommends configuring SLS according to the approach outlined in Section 1.2.3.2. The steps outlined in Table 3-3 implement that approach. 3-10 Installing the SLS Software Installing the SLS Software 3.3 Configuring SLS in a Mixed Architecture Environment This configuration assumes two installations: a primary installation for which all files and directories will be used, and a secondary installation for which only architecture-compatible executables or other nonshared files are located. With this installation, systems with logicals that point to shared locations must be defined to point to the primary installation file locations. This procedure describes how to change key logical definitions to point the primary installation files. 3.3.1 How to Configure for a Mixed-Architecure Environment Table 3-3 shows the steps for configuring SLS in a mixed architecture OpenVMS Cluster system. Table 3-3 How to Configure SLS in a Mixed Architecture __________OpenVMS_Cluster_System.__________________________ Step__Action_______________________________________________ 1 Edit the SYS$MANAGER:TAPESTART.COM file logical definitions on the secondary system so they point to the primary installation files for o The SLS master database location PRIMAST o System backup files SLS$SYSBAK_LOGS SLS$MAINTENANCE_LOGS SLS$SUMMARY_FILES SLS$TEMP_HISTORY o SLS history files HISDIR_n 2 Edit SLS$SYSTEM:LOADER.COM on the secondary system to change the definition of the logical that points to the Pool Authorization and user history update parameters SLS$PARAMS 3 Shutdown and restart SLS on the secondary system so ______the_new_logical_definitions_can_take_effect._________ Installing the SLS Software 3-11 Installing the SLS Software 3.3 Configuring SLS in a Mixed Architecture Environment Table 3-4 shows SLS logical definitions on both VAX and Alpha systems in a mixed architecture OpenVMS Cluster. In this particular configuration, the VAX system installation is the primary, the Alpha the secondary. The logicals on the Alpha system point to shared files in the VAX system directory. 3-12 Installing the SLS Software Installing the SLS Software 3.3 Configuring SLS in a Mixed Architecture Environment Table 3-4 Comparing Logical Definitions Between VAX and Alpha __________Systems________________________________________________ VAX System Logical Definitions___________________Alpha_System_Logical_Definitions___ VAXSYS>SHOW LOGICAL SLS$* ALPHASYS> SHOW LOGICAL SLS$* SLS$CUSTOM = SLS$ROOT:[CUSTOM]SLS$CUSTOM = SLS$ROOT:[CUSTOM] SLS$DATA = SLS$ROOT:[DATA.ALPHASYS] SLS$DATA = SLS$ROOT:[DATA.VAXSSLS$DATAC = SLS$ROOT:[DATA] SLS$DEFSBACLASS = SLS$DATAC = SLS$ROOT:[DATA] FOREVER <- insert archive class here SLS$DEFSBACLASS = FOREVER <- insert archive clSLS$HIST_$ALL$ = GENERIC = GENERIC_RMU_HISTORY SLS$HIST_$ALL$ = GENERIC = GENERIC_RMU_HSLS$HIST_$BACKUP$ = GENERIC SLS$HIST_$RMUBACKUP$ = SLS$HIST_$BACKUP$ = GENERIC GENERIC_RMU_HISTORY SLS$HIST_$RMUBACKUP$ = SLS$HIST_GENERIC = GENERIC_RMU_HISTORY $1$DUA3:[VAX.SLS$FILES.HIST] SLS$HIST_GENERIC = SLS$HIST_GENERIC_RMU_HISTORY = SLS$ROOT:[HIST] $1$DUA3:[VAX.SLS$FILES.HIST.DATABASE_HISTORY] SLS$HIST_GENERIC_RMU_HISTORY = SLS$LABEL = _NL: SLS$ROOT:[HIST.DATABASE_HISTSLS$LABEL_TEMPLATE = SLS$SYSTEM:PRINTED_LABEL_V21.TEMPLATE SLS$LABEL = _NL: SLS$LABEL_TEMPLATE = SLS$MAILBOX = MBA36: SLS$SYSTEM:PRINTED_LABEL_V21SLS$MAINTENANCE_LOGS = $1$DUA3:[VAX.SLS$FILES.SYSBAK.MAINTENANCE_LOGS] SLS$MAILBOX = MBA71: SLS$MAINTENANCE_LOGS = SLS$MASTER = SLS$ROOT:[SYSBAK.MAINTENANCE_LOGS]UA3:[VAX.SLS$FILES.PRIMAST] SLS$OFFSITE_DATE = 0 SLS$MASTER = SLS$ONSITE_DATE = 0 SLS$ROOT:[PRIMAST] SLS$PARAMS = SLS$OFFSITE_DATE = 0 $1$DUA3:[VAX.SLS$FILES.PARAMS] SLS$ONSITE_DATE = 0 SLS$ROOT = SLS$PARAMS = $1$DUA3:[ALPHA.SLS$FILES.] SLS$ROOT:[PARAMS] SLS$STARTUP_P1 = REBOOT SLS$ROOT = SLS$SUMMARY_FILES = $1$DUA3:[VAX.SLS$FILES.] $1$DUA3:[VAX.SLS$FILES.SYSBAK.SUMMARY_FILES] SLS$STARTUP_P1 = REBOOT SLS$SUMMARY_FILES = SLS$SYSBAK = SLS$ROOT:[SYSBAK] SLS$ROOT:[SYSBAK.SUMMARY_FILSLS$SYSBAK_LOGSh= SLS Software 3-13 $1$DUA3:[VAX.SLS$FILES.SYSBAK.SYSBAK_LOGS] SLS$SYSBAK = SLS$ROOT:[SYSBAK] SLS$SYSTEM = SLS$ROOT:[CUSTOM] SLS$SYSBAK_LOGS = = SLS$ROOT:[SYSTEM] SLS$ROOT:[SYSBAK.SYSBAK_LOGSSLS$TEMP_HISTORY = $1$DUA3:[VAX.SLS$FILES.SYSBAK.TEMP_HISTORY] SLS$SYSTEM = SLS$ROOT:[CUSTOM] SLS$VAULT = DPS = SLS$ROOT:[SYSTEM] SLS$TEMP_HISTORY = SLS$ROOT:[SYSBAK.TEMP_HISTORY] SLS$VAULT_=_DPS__________________________________________________ 4 _________________________________________________________________ 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 4.1 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 4-1 After Installing SLS 4.2 Editing the Systemwide Command Files 4.2 Editing the Systemwide Command Files To ensure SLS functions properly, you need to edit the system startup procedure and the system login file. 4.2.1 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 based on the OpenVMS Version. 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. 4.2.2 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. 4.3 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. 4-2 After Installing SLS After Installing SLS 4.3 Preparing SLS Server Software 4.3.1 Defining a DECnet Network Object on an OpenVMScluster System Follow the steps in Table 4-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_4-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-1997 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. ___________________________________________________________ (continued on next page) After Installing SLS 4-3 After Installing SLS 4.3 Preparing SLS Server Software Table_4-1_(Cont.)_How_to_Define_the_SLS$DBX_NCP_Object_____ Step_Action________________________________________________ 3 Exit the NCP utility: NCP> EXIT ___________________________________________________________ 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) 4-4 After Installing SLS After Installing SLS 4.3 Preparing SLS Server Software Table_4-1_(Cont.)_How_to_Define_the_SLS$DBX_NCP_Object_____ Step_Action________________________________________________ ___________________________________________________________ 8 Exit the SYSMAN utility: _____SYSMAN>_EXIT__________________________________________ 4.3.2 Defining the DECnet Phase V Network Object for SLS This section lists the commands that register the SLS$DBX object on nodes running DECnet, Phase V. You can use SYSMAN if all nodes in a OpenVMS Cluster to issue these commands at first. If only some of the nodes run DECnet, Phase V, you must issue these commands on those nodes individually. 4.3.2.1 Issue the Commands on Currently Running Nodes Once you have installed SLS, you need to register the SLS$DBX object on the node. Issue the commands shown: RUN SYS$SYSTEM:NCL NCL> CREATE NODE 0 SESSION CONTROL APPLICATION SLS$DBX NCL> SET NODE 0 SESSION CONTROL APPLICATION SLS$DBX NODE SYNONYM TRUE NCL> SET NODE 0 SESSION CONTROL APPLICATION SLS$DBX ADDRESSES = {NAME = SLS$DBX}, - NCL> IMAGE NAME = "SYS$SYSTEM:SLS$FIND_DB_NODE.EXE", USER NAME = "SLS" 4.3.2.2 Defining the SLS$DBX network object in the NET$APPLICATION_STARTUP.NCL File To define the SLS$DBX network object using DECnet-Plus (Phase V), first ensure that you are logged into the SYSTEM account. Then, execute the following command procedure to define the network object. $ @SYS$STARTUP:NET$CONFIGURE ADVANCED Copyright (c) Digital Equipment Corporation 1996. All rights reserved. DECnet-Plus for OpenVMS ADVANCED network configuration procedure This procedure will help you create or modify the management scripts needed to operate DECnet on this machine. You may receive help about most questions by answering with a question mark '?'. After Installing SLS 4-5 After Installing SLS 4.3 Preparing SLS Server Software You have chosen the ADVANCED configuration option. This option enables you to do some specific tailoring of your system's network configuration by answering some specific questions. If you do not want to do specific tailoring of your system's network configuration but instead want to quickly configure your system using most of the default answers, you should invoke NET$CONFIGURE.COM with the BASIC configuration option, ie: @SYS$MANAGER:NET$CONFIGURE BASIC * Do you want to continue? [YES] : Configuration last run by SYSTEM on 20-MAY-1998 22:35:21.23 The following NCL script files have been modified since being created by this procedure: SYS$SPECIFIC:[SYSMGR]NET$APPLICATION_STARTUP.NCL; SYS$SPECIFIC:[SYSMGR]NET$MOP_CLIENT_STARTUP.NCL; This procedure may create a new version of these scripts or modify information contained within them. In all cases, any previously created NCL scripts are renamed to "file.NCL-OLD", so that you may review any of your previous changes. Configuration Options for Node NODENM [0] Exit this procedure [1] Perform an entire configuration [2] Change naming information [3] Configure Devices on this machine [4] Configure Transports [5] Configure Timezone Differential Factor [6] Configure Event Dispatcher [7] Configure Application database [8] Configure MOP Client database [9] Configure Cluster Alias [10] Replace MOP Client configuration 4-6 After Installing SLS After Installing SLS 4.3 Preparing SLS Server Software * Which configuration option to perform? [1]: 7 * Do you want to ADD or DELETE an Application? [ADD]: * What is the name of the Application?: SLS$DBX * What is the destination type for 'SLS$DBX'? [NAME]: * What is the destination name for 'SLS$DBX'?: SLS$DBX * Do you want to specify another application address?[NO] : * What is the name of the Client for 'SLS$DBX'? : * What is the Image name for 'SLS$DBX'? : SYS$SYSTEM:SLS$FIND_DB_NODE.EXE * Incoming Alias for 'SLS$DBX' enabled?[TRUE]: * Incoming Proxy for 'SLS$DBX' enabled?[TRUE]: * Outgoing Alias for 'SLS$DBX' enabled?[FALSE]: * Outgoing Proxy for 'SLS$DBX' enabled?[TRUE]: * Require node synonym for 'SLS$DBX' enabled?[TRUE]: * What is the Incoming OSI TSEL for 'SLS$DBX'?: * What is the User Name for 'SLS$DBX'?[SLS$D$SERVER]: SLS * What UIC should 'SLS$DBX' use?[[200,200]]: [1,20] * Rights identifiers for 'SLS'?: %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account SLS * Do you want to generate NCL configuration scripts?[YES] : %NET$CONFIGURE-I-MODCHECKSUM, checksumming NCL management scripts modified by NET$CONFIGURE %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration completed Configuration Options for Node NODENM [0] Exit this procedure [1] Perform an entire configuration [2] Change naming information [3] Configure Devices on this machine [4] Configure Transports [5] Configure Timezone Differential Factor [6] Configure Event Dispatcher [7] Configure Application database [8] Configure MOP Client database [9] Configure Cluster Alias [10] Replace MOP Client configuration * Which configuration option to perform?[0] : 0 The above procedure adds the network object SLS$DBX to the file SYS$MANAGER:NET$APPLICATION_STARTUP.NCL. In order for the object to be defined on the running system without rebooting, issue the following command: After Installing SLS 4-7 After Installing SLS 4.3 Preparing SLS Server Software $ MCR NCL DO SYS$STARTUP:NET$APPLICATION_STARTUP A correctly defined DECnet-Plus object will look similar to the following: Node 0 Session Control Application SLS$DBX at 1998-10-19-18:37:44.876-04:00Iinf Characteristics Client = Addresses = { name = SLS$DBX } Outgoing Proxy = True Incoming Proxy = True Outgoing Alias = False Incoming Alias = True Node Synonym = True Image Name = SYS$SYSTEM:SLS$FIND_DB_NODE.EXE User Name = "SLS" Incoming OSI TSEL = OutgoingAlias Name= Network Priority = 0 4.3.3 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 4-2 to enable client node access to the SLS volume database. 4-8 After Installing SLS After Installing SLS 4.3 Preparing SLS Server Software Table 4-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 . ___________________________________________________________ 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. 4.4 Configuring SLS to Work With Specific VMS Versions ________________________ Note ________________________ Storage Library System for OpenVMS, Version 2.9C software is not supported on systems running OpenVMS, Version 7.0 operating system software. ______________________________________________________ After Installing SLS 4-9 After Installing SLS 4.4 Configuring SLS to Work With Specific VMS Versions SLS, Version 2.9C operates on systems running OpenVMS VAX Versions 5.5-2, 6.2, 7.1 and 7.2; and OpenVMS Alpha Versions 6.2, 7.1 and 7.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 Alpha. If you are running SLS, Version 2.9C on an Alpha system, you can skip this section. ______________________________________________________ 4.4.1 Version-Specific Files When SLS, Version 2.9C is installed on your system, the installation procedure copies all files shown in Table 4-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. 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. 4-10 After Installing SLS After Installing SLS 4.4 Configuring SLS to Work With Specific VMS Versions Table_4-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.2 SLS$SYSTEM:BACKUPCMD-V62.CLD SLS$SYSTEM:VMSBUXX-V62.EXE SYS$MESSAGE:SLS$BACKUPMSG-V62.EXE OpenVMS 7.1 SLS$SYSTEM:BACKUPCMD-V71.CLD OpenVMS 7.2 SLS$SYSTEM:BACKUPCMD-V72.CLD ___________________________________________________________ 4.4.2 Upgrading OpenVMS Versions after Installing SLS If you install SLS, and then later upgrade your OpenVMS software version, you must copy the three SLS version dependent files to cause them to be used. A command procedure has been supplied for this purpose. Example: Assume you had installed SLS on a system running VMS Version 6.2. You later upgrade to OpenVMS Version 7.1. You must now execute the following command so that SLS will use the correct OpenVMS Version 7.1 version dependent files: $ @SLS$SYSTEM:SLS$VERSION_CHECK_AND_COPY.COM If you install a version of OpenVMS that is unknown to SLS, this command procedure displays an appropriate error of the following form: %SLS-E-NOVERMATCH, No version specific SLS files exist for OpenVMS Vn.n No files will be copied. After Installing SLS 4-11 After Installing SLS 4.5 Upgrading from a Previous Version 4.5 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. 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.9C 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 through Version 2.9C 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. ______________________________________________________ 4.5.1 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.9C 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 ha