Archive/Backup System for OpenVMS Installation Guide Order Number: AA-QHD2G-TE Software Version Archive/Backup System for OpenVMS Version 3.0 Required Operating System OpenVMS Version 6.2, 7.1, and 7.2 Required Software Media and Device Management Services for OpenVMS Version 2.9C or Version 3.0 Optional Software DECnet (Phase IV) or DECnet-Plus(Phase V) TCP/IP Services for OpenVMS October 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. Copyright 1999 Compaq Computer Corporation. All rights reserved. Printed in the United States of America. TM DEC, DIGITAL, MSCP, OpenVMS, StorageWorks, TK, VAX VMSCluster and the DIGITAL Logos are registered in the United States Patent and Trademark Office. Compaq and the Compaq Logo are registered in the United States 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. Version 2.1. 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. Contents Preface 1 Welcome To ABS 1.1 What Do All Storage Environments Have In Common? 1.2 What Makes a Storage Environment Unique? 1.3 Mixed Architecture Environments 1.3.1 Mixed Architecture Environments 1.3.1.1 Creating a Mixed Architecture Configuration 1.3.1.2 Operating a Mixed Architecture Configuration 1.3.1.3 Dissolving a Mixed Architecture Configuration 1.3.2 Principles Guiding Mixed Architecture Configuration 1.3.3 Configuring Applications in a Mixed Architecture OpenVMS Cluster 1.3.3.1 Separate Disk Configuration 1.3.3.2 Separate Root Configuration 1.3.3.3 Separate Subdirectory Configuration 1.3.4 Implementation Specific Approach 1.4 What Is The Purpose of a Managed Media and Device Environment? 2 Meeting Installation Requirements 2.1 Recommended Installation 2.2 Deciding Where to Install ABS Server Software 2.3 Deciding Where To Install ABS Client Software 2.4 Deciding Where to Install MDMS Software 2.5 Using the Installation Worksheets 2.6 Required Privileges 2.7 Required OpenVMS Operating System Subclasses 2.8 Hardware, Software, and System Requirements 2.8.1 Required Hardware 2.8.2 Required Software 2.8.3 Optional Software 2.8.4 Required System Parameters 2.8.5 Required Process Account Quotas 2.8.6 Required Processes 2.9 Overview of Hardware Installation 2.9.1 Jukebox or Drive Hardware Installation 2.9.2 Test the Jukebox 2.9.3 Test the Drive 2.10 Registering ABS Licenses 2.11 Steps to Convert to a New Scheduling Option 3 Installing MDMS Software 3.1 MDMS Pre-installation Tasks 3.1.1 Hardware and Software Requirements 3.1.2 Meet Patch Requirements 3.1.3 Install CMA Shareable Images 3.1.4 Shutdown Previous Version of MDMS 3.1.5 Register the MDMS License 3.1.6 Verify the Node is in the MDMS Database 3.1.7 Consider RDF Configuration 3.2 Installing the MDMS Software 3.3 MDMS Post-installation Tasks 3.3.1 Create a Node Object 3.3.2 Provide Automatic Start Up and Shut Down 3.3.3 Remove SLS/MDMS V2.x Automatic Startup 3.3.4 Configure MDMS 3.3.5 Configure Remote Tape Drives 3.3.6 Grant MDMS Rights to Users 3.3.7 Installing the DCL tables on Nodes 3.4 Graphical User Interface(GUI) Installation 3.4.1 Requirements 3.4.2 Installation on OpenVMS Alpha V7.1 and V7.2 3.4.3 Installation on Intel Windows NT/95/98 3.4.4 Installation on Alpha Windows NT 3.5 Running the GUI 3.5.1 Running the GUI on OpenVMS Alpha 3.5.2 Running the GUI on Intel Windows NT/95/98 3.5.3 Running the GUI on Alpha Windows NT 4 Installing ABS Software 4.1 Installing Archive/Backup System for OpenVMS Software 4.1.1 Installing ABS Server Software 4.1.2 Installing ABS in a Mixed-Architecture OpenVMS Cluster 4.1.3 Installing ABS OpenVMS Client Software 4.1.4 Installing and Configuring ABS NT Clients 4.1.5 Configuring ABS UNIX Clients 4.1.5.1 Modifying the Appropriate UNIX Files 4.1.5.2 Transferring the UNIX Backup Agent Sources 4.1.5.3 Building the UNIX Executables 4.1.6 Authorizing NT and UNIX Clients 5 Performing Postinstallation Tasks 5.1 Installing ABS for the First Time 5.2 Verifying ABS Installation 5.3 Providing Automatic Start Up and Shut Down 5.4 Meeting OpenVMS Cluster Requirements 5.5 Granting the Appropriate ABS Access Right Identifiers 5.5.1 Enabling an Access Rights Identifier 5.5.2 Revoking An Access Rights Identifier 5.6 Modifying The ABS Default Policy Objects 5.6.1 Default Policy Object Attributes 5.6.2 Modifying Default Policy Objects 5.7 Performing a Save, Lookup, and Restore Operation 5.8 Verifying NT and UNIX Client Quotas 5.9 Adding NT Parameter 5.10 Allowing ABS Access to All Files on the NT Systems A Examples of Authorizing NT and UNIX Clients A.1 Adding Client Licenses A.2 Modifying Client Licenses A.3 Showing Client Licenses A.4 Removing Client Licenses B File and Logical Names B.1 ABS File Names B.2 ABS Logical Names C MDMS Files and Logical Names C.1 MDMS File Names C.2 MDMS Logical Names D MDMS V3.0 Rights and Privileges D.1 MDMS Rights - Types D.1.1 High Level Rights D.1.2 Low-level rights D.1.3 ABS Rights D.2 Default High-Level to Low-Level Mapping D.2.1 MDMS_USER: D.2.2 MDMS_OPERATOR Rights: D.2.2.1 Domain Commands for Mapping Privileges E Sample Configuration of MDMS E.1 Configuration Order E.1.1 Configuration Step 1 Example - Defining Locations E.1.2 Configuration Step 2 Example - Defining Media Type E.1.3 Configuration Step 3 Example - Defining Domain Attributes E.1.4 Configuration Step 4 Example - Defining MDMS Database Nodes E.1.5 Configuration Step 5 Example - Defining a Client Node E.1.6 Configuration Step 6 Example - Creating a Jukebox E.1.7 Configuration Step 7 Example - Defining a Drive E.1.8 Configuration Step 8 Example - Defining Pools E.1.9 Configuration Step 9 Example- Defining Volumes using the /VISION qualifier F Upgrading From ABS-OMT To ABS Preface Intended Audience This document is intended for storage administrators who are experienced OpenVMS system managers. This document should be used in conjunction with the Introduction to OpenVMS System Management manual. Conventions The following conventions are used in this document: Convention Description {} In format command descriptions, braces indicate required elements. [ ] In format command descriptions, square brackets indicate optional elements of the command syntax. You can omit these elements if you wish to use the default responses. boldface type Boldface type in text indicates the first instance of a term defined in the Glossary or defined in text. italic type Italic type emphasizes important information, indicates variables, indicates complete titles of manuals, and indicates parameters for system information. Starting test ... This type font denotes system response, user input, and examples. Ctrl/x Hold down the key labels Ctrl (Control) and the specified key simultaneously (such as Ctrl/Z). PF1 x The key sequence PF1 x instructs you to press and release the PF1 key, and then press and release another key (indicated here by x). n A lowercase italic n denotes 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 x denotes the generic use of a letter. For example, xxx indicates any combination of three alphabetic characters. Related Products The following related products may be mentioned in this document: Product Description ABS OMTABS OMT refers to Archive/Backup System for OpenVMS Management Tools[tm] software. HSM HSM refers to Hierarchical Storage Management for OpenVMS software. MDMS MDMS refers to Media and Device Management Services for OpenVMS software. OpenVMS OpenVMS refers to OpenVMS operating system. SMF SMF refers to Sequential Media Filesystem for OpenVMS software. SLS SLS refers to Storage Library System for OpenVMS software. Associate Documents The following documents are part of Archive/Backup System for OpenVMS documentation set: * Archive/Backup System for OpenVMS Installation Guide * Archive/Backup System for OpenVMS Guide to Operations * Archive/Backup System for OpenVMS Command Reference Guide 1 Welcome To ABS If you are installing for the first time, it is essential that you review the information presented in this chapter. If you are a current ABS customer and are upgrading, you may skip to See Meeting Installation Requirements. Welcome to Archive/Backup System for OpenVMS (ABS) Version 3.0. Because you have selected ABS to help you manage your data safety needs (archive and backup operations), you have a hardware and software environment (subsequently referred to as a storage environment) that contains a set of common elements. Your storage environment also contains very specific or unique elements. The information presented in this chapter is intended to give you an "overall picture" of a typical storage environment, and to explain how ABS compliments that environment. 1.1 What Do All Storage Environments Have In Common? All storage environments that plan to implement ABS have the following common hardware and software: * OpenVMS[tm] VAX[tm] or Alpha systems * OpenVMS software Version 6.2, 7.1, or 7.2 for VAX or Alpha systems * Disk devices for online storage/transactions * DECnet[tm] Phase IV or DECnet-Plus[tm] for VAX or Alpha systems * Tape drives * Removable media that is compatible with the tape drives for storing saved data 1.2 What Makes a Storage Environment Unique? Storage environments have some or all of the following characteristics that make them unique: * Mixed-architecture, OpenVMS Cluster (combination of OpenVMS VAX and Alpha systems). See Mixed Architecture Environments for details. * Heterogeneous client systems (OpenVMS, NT, UNIX) * Types of tape drives (TLZ06, TZ877, and so forth) * Types of robotic devices (jukeboxes or gravity-fed loaders) * Types of tape drive connections (direct-connect SCSI or controller-connected) * Location of tape drives (remote or local) * Number of disks * Number of tape drives 1.3 Mixed Architecture Environments If you are planning to install ABS software in a mixed-architecture OpenVMS Cluster, you should understand the configuration issues explained in the following sections. If you do not consider these configuration issues, you may 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 install and configure your software to run in. The following list identifies the topics and their purposes * See Mixed Architecture Environments 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. * See Principles Guiding Mixed Architecture Configuration lists the guiding principles that require you to make special considerations for mixed architecture implementation, and what these principles mean to you. * See Configuring Applications in a Mixed Architecture OpenVMS Cluster describes three possible approaches to implementing a mixed architecture environment. * See Implementation Specific Approach 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.3.1 Mixed Architecture Environments A mixed architecture OpenVMS Cluster includes at least one VAX system and at least one Alpha system. 1.3.1.1 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 Alpha or VAX node into the system, you should decide an approach to take for handling mixed architecture issues. 1.3.1.2 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. 1.3.1.3 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 heterogeneous nature of the mixed architecture system. This includes (but is not limited to) removing startup files, duplicate directory structures, and logical tables. 1.3.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 that cannot be shared, includes 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. 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.3.3 Configuring Applications in a Mixed Architecture OpenVMS Cluster The following sections describes three approaches to configure 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 the following aspects in common: * All shared files reside in one location. * All files that cannot be shared reside in separate locations 1.3.3.1 Separate Disk Configuration The following are characteristics of a separate disk configuration: * Product directories are installed on two separate disks. * One of the product directories is a complete installation containing all data files (and other shared files), and all executable files (and other nonshared files) for either VAX or Alpha systems. * The other product directories contain only a partial product installation, with only those directories that contain Alpha or VAX system executables and other nonshared files. * The systems using the disk with the complete installation uses logicals that normally reference the product executables and shared files. * 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.3.3.2 Separate Root Configuration The following are characteristics of a separate root configuration: * Product directories are installed on the same disk, but at different root locations. * One of the product directories is a complete installation containing all data files (and other shared files), and all executable files (and other nonshared files) for either VAX or Alpha systems. * The other product directories contain only a partial product installation, with only those subdirectories that contain either Alpha or VAX system executables and other nonshared files. * The systems using the directory with the complete installation uses logicals that normally reference the product executables and shared files. * 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.3.3.3 Separate Subdirectory Configuration The following are characteristics of a separate directory configuration: * Product directories are installed on the same disk, and under the same root directory. * Any directory which would normally contain the nonshared files (under a single architecture installation) has two subdirectories: one for VAX system nonshared files, one for Alpha system nonshared files. * 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.3.4 Implementation Specific Approach In this document, specific procedures are provided for a recommended approach based on the current configuration of 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 the installation procedure. 1.4 What Is The Purpose of a Managed Media and Device Environment? The purpose of a managed media and device environment is to maintain a logical view of the physical elements of your storage environment to serve your nearline and offline data storage needs. A managed media and device environment defines the media and defines the drives that can use the media. It also defines the locations where media is stored, the locations of the drives that are compatible with the media, and the policy that governs the use of media. The following list summarizes the characteristics of the managed media and device environment: * Volumes are defined as media types in MDMS. Media type definitions are stored in the MDMS volume configuration database. All managed media are known in terms of type, location, capability, availability, and authorization (who can use that media). Before you can use media in your managed storage environment, you must add the media to the MDMS volume configuration database, and initialize the media for use. Once this is done, the media is known as a "volume". ABS recognizes these media type definitions, and depending upon which media type your storage policy uses, performs the backup operation using the appropriate media type and tape drives. * Tape drive definitions also are stored in MDMS. Tape drives are used to serve the volumes known to MDMS. The MDMS software maintains a logical link between the volumes and the compatible tape drives, both in terms of physical and logical boundaries. Volumes and tape drives can be managed logically from locations miles away from where they are physically located. ABS depends upon MDMS to select the appropriate tape drives determined by the media type. ABS storage policies associate these logical connections. * The MDMS software enables you to set the default criteria for moving and recycling volumes. This criteria includes rotation between onsite and offsite locations for safekeeping of the volumes, and the schedule that moves the volume through its lifecycle (retention, use, and reuse). ABS enables you to set the retention criteria for data saved on volumes, while MDMS enables you to define when to move or recycle volumes. 2 Meeting Installation Requirements To ready your OpenVMS system for either ABS server or client software installation procedure, you must perform certain tasks and requirements: * If you are installing ABS for the first time, See Preinstallation Tasks For a New ABS Installation describes the tasks you must perform before installing ABS. * If you are upgrading your version of ABS, refer to See Preinstallation Tasks For an Upgrade ABS Installation. Preinstallation Tasks For a New ABS Installation Step Action 1. Decide on which system and disk to install ABS and MDMS OpenVMS server software. You must make this decision before you can perform the remaining preinstallation tasks. Refer to See Deciding Where to Install ABS Server Software and See Deciding Where to Install MDMS Software for information about ABS and MDMS server software. Use the worksheet provided in See Example Installation Worksheet to record your configuration. 2. Decide on which systems and disks to install ABS OpenVMS client software. Refer to See Deciding Where To Install ABS Client Software for information about ABS OpenVMS client software. Use the worksheet provided in See Using the Installation Worksheets to record your configuration. 3. Log in to the SYSTEM account and enable all privileges. Most system managers install software from the system account. See Required Privileges for the privileges required to install ABS Version 3.0. 4. Perform a system backup operation. COMPAQ recommends that you perform a backup operation on the system disk before installing any software. For details about performing a backup operation on a system disk, see OpenVMS System Manager's Manual. 5. Verify the OpenVMS operating system subclasses. Subclasses are provided in the OpenVMS save set that contains support for the OpenVMS operating system. See Required OpenVMS Operating System Subclasses lists the OpenVMS operating system subclasses required to install ABS Version 3.0 6. See Hardware, Software, and System Requirements to verify the following requirements: * Hardware and software requirements * System parameters * Account process quotas * System processes 7. Configure your hardware. Before you can use ABS software, you must first install and test your hardware configuration. It is recommended that you do this prior to installing ABS and MDMS software. These tasks are described in See Overview of Hardware Installation . Note: The Media Robot Utility (MRU) software provides you with the ability to control the operation of an automated library system or a media loader system without having to access front panel controls on the system. MRU is especially useful for installing, configuring, and testing the operation of these types of system. 8. COMPAQ distributes MRU software with its newest libraries and loaders. If you have recently purchased MRU software and installed it, you will have the MRU software with its newest libraries and loaders. If you are using an earlier COMPAQ library or loader and would like to use MRU software, contact your COMPAQ sales representative. Register ABS licenses as described in See Registering ABS Licenses . See Preinstallation Tasks For an Upgrade ABS Installation describes the preinstallation tasks to upgrade an existing ABS installation. Preinstallation Tasks For an Upgrade ABS Installation Step Action If you have new tape drives that you want to add to your 1. current storage environment, follow the instructions provided in See Overview of Hardware Installation . It is recommended that you do this prior to upgrading ABS or MDMS software. 2. Log in to the SYSTEM account and enable all privileges. Most system managers install software from the system account. See See Required Privileges for the privileges required to install ABS Version 3.0. 3. Perform a system backup operation. COMPAQ recommends that you perform a backup operation on the system disk before installing any software. For details about performing a backup operation on a system disk, see OpenVMS System Manager's Manual . Shutdown ABS. 4. If you are upgrading ABS and it is currently running, shut down ABS by entering the following commands on all nodes in the OpenVMS Cluster running ABS: $ @SYS$MANAGER:ABS$SHUTDOWN.COM 5. Verify the OpenVMS operating system subclasses. Subclasses are provided in the OpenVMS save set that contains support for the OpenVMS operating system. See Required OpenVMS Operating System Subclasses lists the OpenVMS operating system subclasses required to install ABS Version 3.0. 6. See Hardware, Software, and System Requirements to verify the following requirements: * Hardware and software requirements * System parameters * Account process quotas * System processes 7. See Steps to Convert to a New Scheduling Option to follow steps for converting to another scheduling option. 2.1 Recommended Installation In the event of a disaster situation it is essential to know where to install ABS and its dependent products so that you can recover the affected system as quickly as possible. To ease the recovery process in the event of a disaster situation, review this information to understand the most efficient way to install ABS, MDMS, and any dependent layered products. The information provided is only for OpenVMS VAX or Alpha systems. If you have other types of systems to consider, see the platform specific documentation for recovery information. Consider the following important guidelines: * You should install ABS server software and MDMS software on the same disk in a system. This disk could be the system disk, or another disk dedicated to ABS and its dependent layered products. The advantage of placing ABS and its dependent layered products on the system disk is that a less complicated restore process is enabled. However, the system disk then requires more space for ABS catalogs, MDMS database, and so forth. * This disk should be dedicated to ABS and its dependent layered products, not shared with other interactive processes that could impede the performance of ABS. * The system that contains this disk must have access to a tape drive compatible with the media that will contain ABS save sets for this disk. Before you begin the installation procedure, use the worksheets provided in See Installation Worksheet to identify which OpenVMS system and disk will contain ABS server software, MDMS software. 2.2 Deciding Where to Install ABS Server Software ABS is designed upon a client server technology. Before installing ABS software, decide which OpenVMS node or which nodes in an OpenVMS Cluster will run an ABS server. ABS server software is installed on an OpenVMS node or OpenVMS Cluster system and provides the policy database for itself and for any ABS client nodes connected to it. ABS server software makes the policy database available to all ABS clients. Requirement: You must install ABS server software on at least one OpenVMS node or OpenVMS Cluster system. Although the installation procedure does not have separate kits for the client and server software, ABS server is determined by the placement of ABS policy engine. During the installation procedure, you will be prompted to supply an OpenVMS node name (or node names in an OpenVMS Cluster) where you want the ABS server called the policy engine to reside. This node (or nodes in a cluster) becomes the ABS server nodes. You cannot specify a cluster alias name in the node name list. If your system configuration changes at some point after running the installation procedure, you can change the server node name(s) by modifying the ABS$SYSTEM:ABS$POLICY_CONFIG.DAT file and restarting the server software. 2.3 Deciding Where To Install ABS Client Software OpenVMS Clients Install ABS OpenVMS client software on any node that can communicate with ABS server and for which you want to create ABS save requests. ABS OpenVMS client node can communicate with an ABS server node using the DECnet software. When an ABS client node needs to perform an ABS operation, ABS client node communicates with ABS server, retrieves policy information, updates ABS policy database, and then relinquishes its communications with ABS server when the operation has completed. NT Clients For NT clients you must install ABS NT client software provided in ABS software kit. You must also authorize access for NT clients on ABS server node. Instructions for these tasks are described in See Installing and Configuring ABS NT Clients UNIX Clients UNIX clients do not require a separate client installation. However, you must transfer the GNU tar files provided by ABS software to the UNIX client system, and then you must build the executable files on the UNIX client system. Also, you must authorize access for UNIX clients on ABS server node. Instructions for these tasks are described in See Configuring ABS UNIX Clients Both NT and UNIX clients have their backup operations occur on ABS server node, and ABS server communicates with the NT or UNIX client system for data transfer and control. Given you have the appropriate amount of licenses and adequate resources available, any number of ABS client nodes may be connected to a single ABS server node. 2.4 Deciding Where to Install MDMS Software You must install Media and Device Management Services for OpenVMS (MDMS) software before you install ABS software. If you plan to use tape drives or robotic devices for your ABS save operations, MDMS supports ABS by enabling you to configure your tape drives and robotic devices, both local and remote, so that ABS can use them for its save and restore requests. Install MDMS software on the same OpenVMS node or OpenVMS Cluster system where you will be installing ABS server software (typically the same disk as ABS server software). MDMS provides media management services for itself and for any MDMS client nodes connected to it. MDMS software provides MDMS volume and magazine databases. The volume database contains definitions of all removable media known to MDMS software, and the associated tape drive definitions, such as if the tape drive is local or remote to MDMS. It also contains information about volume locations and volume pool authorization. MDMS software updates all MDMS databases when any transactions are performed against the volumes. Requirement: You must install MDMS software on at least one OpenVMS node or OpenVMS Cluster system in the network. 2.5 Using the Installation Worksheets To help you with the installation procedure the worksheet in See Installation Worksheet provides a work area to help you previously identify where you are installing ABS OpenVMS server, client software, and MDMS software. See Example Installation Worksheet provides an example of how to use the worksheets provided in See Installation Worksheet. Example Installation Worksheet Node Name or Support a Support a Remote Server/Client OpenVMS Disk Name Remote Tape Backup Cluster Name Device? Operation? ABS Server Software NODESV DISK$USER1: N/A N/A MDMS Software NODESV DISK$USER1: No Yes ABS OpenVMS Client and MDMS NODECA DISK$USER2: Yes No ABS OpenVMS Client and MDMS NODECB DISK$USER3: Yes No See Installation Worksheet provides the worksheet for your ABS/MDMS configuration. It is recommended that you make a copy of the worksheet and save the original for future use. Installation Worksheet Node Name or Support a Server/Client OpenVMS Disk Remote Tape Support a Remote Cluster Name Name Device? Backup Operation? ABS Server Software MDMS Software ABS OpenVMS Client and MDMS ABS OpenVMS Client and MDMS ABS NT Client N/A N/A N/A N/A N/A N/A N/A N/A ABS UNIX Client N/A N/A N/A N/A N/A N/A N/A N/A 2.6 Required Privileges To install ABS Version 3.0, log on to the SYSTEM account or to an account that has SETPRV or, at a minimum, has the following privileges enabled: * CMKRNL * WORLD * SYSPRV * TMPMBX * NETMBX Note that VMSINSTAL turns off the BYPASS privilege at the start of the installation procedure. 2.7 Required OpenVMS Operating System Subclasses OpenVMS operating system comes with a variety of support options, or subclasses. Subclasses include such features as networking and RMS journaling. To use ABS, your system should have the following subclasses resident: * Programming support * Utilities * System programming environment * Secure user's environment * Network support How to verify: For information about verifying these components, refer to either OpenVMS VAX Installation Procedures or OpenVMS Alpha Installation Procedures. 2.8 Hardware, Software, and System Requirements To make sure that your system is ready for the installation, verify that your system meets the following requirements: * Hardware * Software * System parameters * Process account quotas * Processes 2.8.1 Required Hardware To install ABS Version 3.0 software, you must meet the following minimum hardware requirements: * A VAX[tm] system, a MicroVAX[tm] system, a VAXstation[tm], or an Alpha system. * Four megabytes of memory for VAX systems, or 16 megabytes of memory for Alpha systems. * One or more tape drives if you plan to back up your data to removable media. Refer to See Required Privileges for instructions about configuring your hardware. * One disk, such as a COMPAQ RD[tm] or RZ[tm] series disk. * Adequate disk space. Refer to See Required Disk Space to make sure there is adequate disk space to install ABS Version 3.0. Verify that there are enough free blocks on the disk where you are installing the software. If you are providing remote drive support, you must answer yes to the remote drive question during MDMS installation procedure. This requires additional free disk space. Enter the following command to show the amount of used disk space on your disk: $ SHOW DEVICE disk-name See Required Disk Space lists the amount of disk spaced required to perform ABS Version 3.0 installation. Required Disk Space IF you are Supporting remote installing... drives? THEN you need... 140,000 peak blocks during MDMS Yes installation software No 140,000 peak blocks during installation 50,000 blocks during installation ABS Server 50, 000 blocks after installation software N/A plus additional blocks for the catalog size requirements 50,000 blocks during installation ABS Client software N/A 50, 000 blocks after installation plus additional blocks for the catalog size requirements 2.8.2 Required Software See Required Software lists the software you must have installed on your system before you can install ABS Version 3.0. Required Software Software Purpose System ABS OpenVMS DECnet Phase IV or Provides network support Server DECnet Plus for Note: OpenVMS ABS OpenVMS This software must be up and running Client before you start the installation procedure ABS OpenVMS Media and Device Provides media and device managment Server Management services for all OpenVMS media and Services1 tape drives. ABS OpenVMS Client ABS OpenVMS OpenVMS Operating Server Systema Provides OpenVMS and DCL capabilities. ABS OpenVMS Client 2.8.3 Optional Software See Optional Software describes the optional software you can use with ABS Version 3.0 software. Optional Software Software Purpose System Provides the ability to save data from Windows NT ABS NT Client systems to ABS OpenVMS server system using ABS NT Client Software software (provided with ABS, not purchased separately). Provides the ability to C Compiler build the executable files UNIX Client on UNIX clients DCSC2(Digital If you have a StorageTek Cartridge Server Automated Cartridge Server The system where the Component) (ACS), you must install the StorageTek silo resides. DCSC software. TCP/IP Services for Provides network support OpenVMS for NT and UNIX clients. ABS OpenVMS Server Provides the ability to eXcursion display the graphical user NT client system interface (GUI) on NT client systems. Media Robot Utility Provides library and loader The OpenVMS system where (MRU) testing, diagnostics, and the robotic device is control. physically connected Motif for X-Windows Provides graphical user ABS OpenVMS server interface capabilities ABS OpenVMS client Oracle Rdb a for VAX Provides distributed and or Alpha systems multi streaming ABS OpenVMS Server capabilities. Requirements: If you install Oracle Rdb for ABS policy database, the version of Oracle Rdb that you select must be up and running before you install ABS Version 3.0. Also, the file SYS$LIBRARY:SQL$USER.OLB or SYS$LIBRARY:SQL$USER_ n.OLB (where n is version specific) must pre exist on your system. If you have Oracle Rdb Version 6.0, you must apply engineering change order (ECO) number 5. 2.8.4 Required System Parameters To install ABS Version 3.0, the system parameters must be set to the minimum value or higher. See System Parameters - Minimum Values lists the minimum system parameter values required for the installation procedure to run successfully. Depending on the kinds of programs and applications running at your site, you may need higher values. System Parameters - Minimum Values System Parameter Minimum Value Dynamic PQL_DENQLM 300 Y GBLPAGES3 2000 N GBLSECTIONS 4 N LOCKIDTBL 45000 N PQL_MENQLM 300 Y PQL_MPGFLQUOTA 10000 Y PROCSECTCNT 100 N PQL_MTQELM 200 Y To see the current system parameter values on your system, enter the following command: $ MCR SYSGEN SYSGEN > SHOW/GEN Result: Shows the current values of all the system parameters. If you need to modify one or more of the system parameters, see the following example: $ MCR SYSGEN SYSGEN > SET GLBPAGES 2000 SYSGEN > WRITE CURRENT SYSGEN > EXIT The changed parameters should be added to SYS$SYSTEM:MODPARAMS.DAT for future changes made with AUTOGEN. You must then reboot the system so the non dynamic parameter values are recognized. More information: Refer to OpenVMS System Manager's Manual: Managing System Parameters for detailed information about required system parameters. 2.8.5 Required Process Account Quotas The account you use to install ABS (typically the SYSTEM account) must have sufficient quotas to enable you to perform the installation. 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 the software. See Required Installing Account Process Quotas summarizes the process quotas and the quotas that VMSINSTAL requires to perform the installation. Required Installing Account Process Quotas Account QuotaMinimum Value ASTLM 200 BIOLM 10000 BYTLM 18000 DIOLM 200 ENQLM 2048 FILLM 300 PGFLQUO 10000 TQELM 200 To see your current process quotas, see the following example: $ MCR AUTHORIZE UAF > SHOW SMITH Result: This command shows all your process quotas. If you need to increase your process account quotas, see the following example: $ MCR SYS$SYTEM:AUTHORIZE UAF> MODIFY SMITH/ENQLM 2048 UAF> EXIT If you are supporting NT or UNIX clients, to ensure successful save and restore operations, set the quotas to the following values from ABS OpenVMS server node: UCX> SET PROTOCOL TCP/QUOTA=(SEND:50000,RECEIVE:50000) If you have to reboot the machine, make sure that you reset these values after rebooting. More information: For detailed instructions about modifying account quotas, see the description of Authorize Utility in OpenVMS System Management Subkit . 2.8.6 Required Processes Before beginning the installation procedure, check to see that DECnet Phase IV or DECnet Plus and the OpenVMS Queue Manager are running. To see if these processes are active on your system, enter the following command: $ SHOW SYSTEM The following information is displayed for DECnet Phase IV: OpenVMS V7.1 on node NODE1 8-AUG-1997 13:39:28.23Uptime 0 23:36:26 Pid Process Name State Pri I/O CPU Page flts Page . . . 20A0022C QUEUE_MANAGER HIB 8 72 0 00:00:00.83 751 1210 . . . 20A00212 NETACP HIB 10 285 0 00:00:02.84 338 666 The following information is displayed for DECnet Plus: 37C00215 NET$ACP HIB 4 629 0 00:27:23.22 1894 2465 . . . 37C0024A QUEUE_MANAGER HIB 8 3333 0 00:07:45.24 1246 1766 If these processes are not active, follow the steps in See How to Start DECnet and the OpenVMS Queue Manager. How to Start DECnet and the OpenVMS Queue Manager Step Action 1. Start DECnet software. For DECnet Phase IV, enter the following command at DCL prompt: $ @SYS$MANAGER:STARTNET.COM For DECnet Plus, enter the following command at DCL prompt: $ @SYS$STARTUP:NET$STARTUP.COM 2. Start OpenVMS Queue Manager. Enter the following command at DCL prompt: $ START/QUEUE/MANAGER 2.9 Overview of Hardware Installation For your storage application to work, the hardware it depends on must be installed, connected, and configured to function with the operating system. This section provides a sequence of actions that you can use to verify that storage devices are connected and operating before you install MDMS and other application. This procedure applies to the installation of a jukebox with drives or a standalone drive. Use an initialized volume to perform this test. To initialize a volume, consult Open VMS documentation or enter HELP INITIALIZE at an OpenVMS terminal. 2.9.1 Jukebox or Drive Hardware Installation During this procedure, refer to the device specific hardware installation information for details. This procedure provides only the basic steps necessary to configure MDMS later against the jukebox and/or drives: 1. Following manufacturer's documentation, 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. Some controllers require you to configure pass through devices for drives and jukeboxes. 3. Make note of the device names after you complete connection procedures. If you are going to use Media Robot Utility software, define the logical MRU_ROBOT with the name of the jukebox device. 2.9.2 Test the Jukebox If possible, use a utility such as Media Robot Utility (MRU) for this procedure. Otherwise, use the front panel of the drive and OpenVMS system software to test the connection between the OpenVMS system and jukebox. Testing the Jukebox Connection Step Action 1. Verify the changer device name and the drive names. Enter 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. Use the OpenVMS SHOW DEVICE command: $ SHOW DEVICE [device_name[:]] Use the following MRU command for examining the robot: $ ROBOT SHOW ROBOT If either of these commands returns an error, make sure the device name is correct. If the device name is correct, then refer to the hardware documentation for remedial action. Place an initialized volume in the jukebox. * If your jukebox uses a magazine, place the volume in the magazine and then insert the magazine into the jukebox. * If your jukebox uses ports, place the volume into the port and then move the volume to an available slot in the jukebox. If you are using MRU, enter the following commands to accomplish this: $ ROBOT INJECT PORT port_number SLOT slot_number 2.9.3 Test the Drive This test involves loading a volume and then mounting it on the drive. For jukeboxes with multiple drives, perform this procedure with each drive. Following the successful completion of this test, you will be ready to install and test MDMS. Testing the Drive Connection Step Action 1. Load the volume into the drive. If you are using MRU, enter the following command: $ ROBOT LOAD SLOT slot_num DRIVE drive_num Mount volume with the OpenVMS MOUNT/FOREIGN command: $ MOUNT/FOREIGN/NOASSIST drive_name Dismount the volume with the OpenVMS DISMOUNT command. * If you are using a stand alone drive or a tape library then enter the command with /UNLOAD qualifier: $ DISMOUNT/UNLOAD drive_name * If you are using a loader, include the /NOUNLOAD qualifier: $ DISMOUNT/NOUNLOAD drive_name * If you are using a jukebox, unload the volume from the drive. Use the front panel controls, or if you are using MRU, enter the following command: $ ROBOT UNLOAD DRIVE drive_num SLOT slot_num * If you are using a jukebox, remove the volume. Use the front panel controls, or if you are using MRU, enter the following command: $ ROBOT EJECT PORT port_number 2.10 Registering ABS Licenses To use ABS Version 3.0 software, you must register and load the licenses before you begin the installation procedure. This information is supplied in the License PAK document which is packaged along with Archive/Backup System for OpenVMS Cover Letter . To register a license under OpenVMS, use the following procedure: 1. Log in to the system where you will be installing the software. Log in under SYSTEM account, or enable your account with the privileges described in See Required Privileges. 2. Select one of the following methods to register the licenses: 3. At DCL prompt, enter the LICENSE REGISTER command with appropriate qualifiers that correspond to License PAK information. See How to Register Your ABS Licenses Using the LICENSE REGISTER Command. 4. Invoke SYS$UPDATE:VMSLICENSE.COM procedure. When it prompts you for information, respond with data from your License PAK. See How to Register Your ABS Licenses Using VMSLICENSE.COM. If you plan to use ABS on more than one node in an OpenVMS Cluster, you must load the licenses on other nodes after you install ABS. See How to Register Your ABS Licenses Using the LICENSE REGISTER Command, Step 10 for instructions. How to Register Your ABS Licenses Using the LICENSE REGISTER Command Step Action 1. Enter the LICENSE REGISTER command with the product name followed by a dash (-): $ LICENSE REGISTER ABS-SERVER-VAX - ! Register this license on the ABS VAX server node $ LICENSE REGISTER ABS-SERVER-ALPHA - ! Register this license on the ABS Alpha server node $ LICENSE REGISTER ABS-CLIENT-VAX - ! Register this license on all ABS VAX client nodes $ LICENSE REGISTER ABS-CLIENT-ALPHA - ! Register this license on all ABS VAX Alpha nodes $ LICENSE REGISTER ABS-NT-CLIENT-USER - ! Register this license on the ABS server node where you plan to support NT clients. $ LICENSE REGISTER ABS-UNIX-CLIENT-USER - ! Register this license on the ABS server node where you plan to support UNIX clients. $ LICENSE REGISTER ABS-OMT - ! Register this license on all ABS VAX server nodes where you want to install the ABS OMT software $ LICENSE REGISTER ABS-OMT-UPG - ! Register this license on all ABS VAX server nodes where you want to upgrade the ABS OMT software to the full ABS product Important: Enter a dash (-) at the end of each command from Steps 1 through 8. 2. Enter the /ISSUER qualifier information, assigning the value DEC between quotation marks. _$ /ISSUER="DEC" - 3. Enter the /AUTHORIZATION qualifier information, assigning it the value from the AUTHORIZATION NUMBER4 entry of the PAK: _ $ /AUTHORIZATION=xxxxxx - Enter the /PRODUCER qualifier information, assigning the value DEC in quotes: _$ /PRODUCER="DEC" - Enter the /UNITS qualifier information, assigning it the value from the UNITS a entry of the PAK _$ /UNITS=nn - Enter the /DATE qualifier information, assigning the product's release date value from the PRODUCT RELEASE DATE a entry of the PAK: _$ /DATE=dd-mmm-yyyy - Enter the /AVAILABILITY qualifier information, assigning the value from the AVAILABILITY TABLE CODE a entry of the PAK: _$ /AVAILABILITY=x - Enter the /OPTIONS qualifier information, assigning the value from the KEY OPTIONS a entry of the PAK: _$ /OPTIONS=xxxxxx - Enter the /CHECKSUM qualifier information, assigning the value from the CH a entry of the PAK: _$ /CHECKSUM=1-xxxx-xxxx-xxxx-xxxx Important: Do NOT end the entry with a dash. Invoke the LICENSE LOAD command with the product name: $ LICENSE LOAD product_name See How to Register Your ABS Licenses Using VMSLICENSE.COM describes how to register your license using the command procedure. How to Register Your ABS Licenses Using VMSLICENSE.COM Step Action 1. From the system prompt, enter the following command: $ @SYS$UPDATE:VMSLICENSE.COM Select Option 1. "REGISTER a Product Authorization Key" Answer the questions according to the information supplied in the LICENSE PAK document (provided with the software kit). The following is only an example. Supply the information provided in the PAK to the prompts: Type ? at any prompt for a description of the information requested. Press Ctrl/Z at any prompt to return to the main menu. Issuer [DEC] Authorization Number []: Authorization Number []: ALS-NQ-1996JUN10-181 Product Name []: ABS-SERVER Producer [DEC]: Number of Units []: 1050 Version []: Product Release Date []: Key Termination Date []: Availability Table Code []: H Activity Table Code []: Key Options []: MOD_UNITS,ALPHA Product Token []: Hardware-Id []: Checksum []: 2-PIBA-KIPP=BIGE-DDHC 2. Verify the information that you entered is correct. Enter Yes. 3. To exit the command procedure, select Option 99. For complete information about using LMF, see OpenVMS License Management Utility Manual . 2.11 Steps to Convert to a New Scheduling Option If you are converting from DECSCHEDULER (default for V2.2n) to INT_QUEUE_MANAGER or EXT_QUEUE_MANAGER, you need to review your save requests before installing ABS V3.0. Before updating ABS to V3.0, do an ABS SHOW SAVE * command. 1. If a save has a start time in the past, you may want to set the save request to the desired start time, or to NEVER using: ABS SET SAVE request /START_TIME="time" or ABS SET SAVE request /START_TIME = NEVER or ABS SET SAVE request /NOSTART_TIME 2. Save requests which have an explicit time, NOW or NEVER will NOT be scheduled. 3. During ABS V3.0 installation, if you choose to use the INT_QUEUE_MANAGER or EXT_QUEUE_MANAGER scheduling option, all of the ABS jobs in the POLYCENTER Scheduler are placed on hold. You may wish to delete the POLYCENTER Scheduler job using SCHEDULER DELETE request/USER=ABS. After updating to ABS V3.0, ABS will begin scheduling the save requests at their new start time. If you did not set the start time of old requests to a time in the future, ABS will reset the start time of very old save requests to the next due time, based on the start time in the save request. It will not run the very old saves until the next due time calculated. If the start time was within one scheduling interval (for example, within a week for a weekly interval), then ABS will execute the save request when ABS is started after the upgrade, then it will reset the start time for the next due time. To make sure ABS executes your saves exactly when you want them to execute, modify the start time as mentioned in Step 1. Information about the ABS scheduling activities is logged to the ABS$LOG:ABS$POLICY_.LOG file. To receive additional information about scheduling in the log file, you may define a logical name: $ DEFINE/SYSTEM ABS_SCHEDULER_LOGGING TRUE An opcom message will automatically be sent to the TAPE operator if ABS fails to schedule a request. 3 Installing MDMS Software This chapter explains how to install the Media and Device Management Services (MDMS) Version 3.0 software. The sections in this chapter cover the 3 procedures involved in installing the software, namely: * pre-installation tasks * installation * post-installation tasks If this is the initial installation of MDMS V3.0 you should install MDMS on a node that is going to be one of your MDMS server nodes. You may want to read the MDMS configuration chapters in the guide to operations to make better decisions when installing MDMS. This version of MDMS installs the system executable files into system specific directories. Because of this, there is no special consideration for mixed architecture OpenVMS cluster system installations. At a minimum, you will install MDMS twice in a mixed architecture OpenVMS Cluster system: * the first time for the Open VMS VAX nodes * a second time for the OpenVMS Alpha nodes. 3.1 MDMS Pre-installation Tasks The following table lists out exactly which section describes the particular pre-installation task, to help you ensure that the installation takes place correctly. Action Section Meet hardware and software Section See Hardware and Software requirements Requirements Meet prerequisite patches requirements Section See Meet Patch Requirements Install CMA shareable images Section See Install CMA Shareable Images Shutdown previous version of MDMS Section See Shutdown Previous Version of MDMS Register the MDMS License Section See Register the MDMS License Verify the Node is in the MDMS Section See Verify the Node is in the Database MDMS Database Consider RDF Configuration Section See Consider RDF Configuration 3.1.1 Hardware and Software Requirements MDMS V3.0's free disk space requirements differ during installation (peak utilization) and after installation (net utilization). As a pre-installation step please make sure that the required space is available during and post-installation respectively. Table See Disk Space Requirements shows the different space requirements. Disk Space Requirements If you are Complete Installing the Kit You will need 131,560 peak blocks during installation MDMS V3.0 Yes 98,964 net blocks after installation(permanent) 4,716 peak blocks during installation No 1,156 net blocks after installation(permanent) The two installation variants are organized, and require disk space as follows: Variant Peak Net Utilization Utilization Complete kit with all options selected: * OpenVMS MDMS 131560 98964 * OpenVMS GUI * Alpha NT GUI * Windows GUI Minimal kit 4716 1156 The files for MDMS are placed in two locations: * system disk: for executables * MDMS$ROOT: for * Command procedures * Log files * Database files * GUI files for all three platforms If disk space is an issue, it is advisable to place MDMS$ROOT: on a disk other than your system disk because MDMS creates log files that can grow quite large. OpenVMS V6.2 is the minimum version of software necessary to run MDMS. OpenVMS V7.1 Alpha is the minimum version of software to run the GUI on. 3.1.2 Meet Patch Requirements Table describes the patch requirements for MDMS: Prerequisite Patches Component Operating System Version Patch MDMS$SERVER OpenVMS Alpha V6.2 ALPY2K_062 OpenVMS VAX V6.2 VAXLIBR06_070 GUI OpenVMS Alpha V7.1 to V7.1-H2 ALPBASE02_071 V7.1 to V7.1-H2 ALPACRT06_071 V7.1 to V7.1-H2 ALPDCL01_071 V7.1 to V7.1-H2 ALPSYSA01_071 V7.1 to V7.1-H2 ALPSYSB02_071 V7.1 to V7.1-H2 ALPTHREADS_03071 V7.1-2 ONLY VMS712_PTHREADS If the server patches are not installed, you will see the following error while trying to start the server: 09-Mar-1999 10:38:16 %MDMS-I-TEXT, "10k Day" patch not installed! You can obtain these patches or the latest revision by contacting your Compaq representative. If the patches for the MDMS$SERVER are not installed, the server will not start but you can successfully install MDMS, then install the patches and start the server. 3.1.3 Install CMA Shareable Images If you are installing MDMS on an OpenVMS V6.2 VAX system, you have to install the following three files: * SYS$COMMON:[SYSLIB]CMA$RTL * SYS$COMMON:[SYSLIB]CMA$OPEN_RTL * SYS$COMMON:[SYSLIB]CMA$LIB_SHR If these images are not installed by default, include the following lines in the SYS$STARTUP:SYSTARTUP_VMS.COM: $! $! Install CMA stuff for MDMS $! $ INSTALL = "$INSTALL/COMMAND_MODE" $ IF .NOT. F$FILE_ATTRIBUTES("SYS$COMMON:[SYSLIB]CMA$RTL.EXE", "KNOWN") $ THEN - $ INSTALL ADD SYS$COMMON:[SYSLIB]CMA$RTL $ ENDIF $ IF .NOT. F$FILE_ATTRIBUTES("SYS$COMMON:[SYSLIB]CMA$OPEN_RTL.EXE", "KNOWN") $ THEN $ INSTALL ADD SYS$COMMON:[SYSLIB]CMA$OPEN_RTL $ ENDIF $ IF .NOT. F$FILE_ATTRIBUTES("SYS$COMMON:[SYSLIB]CMA$LIB_SHR.EXE", "KNOWN") $ THEN $ INSTALL ADD SYS$COMMON:[SYSLIB]CMA$LIB_SHR $ ENDIF 3.1.4 Shutdown Previous Version of MDMS If you have been running a version of MDMS prior to Version 3.0, you must shut it down using the following command: $ @SLS$SYSTEM:SLS$SHUTDOWN If you are using MDMS V3.0, use the following command to shutdown MDMS: $ @SYS$STARTUP:MDMS$SHUTDOWN 3.1.5 Register the MDMS License As MDMS V 3.0 does not have a separate license, you need one of the following licenses to run MDMS: * ABS-CLIENT-ALPHA * ABS-CLIENT-VAX * ABS-OMT * ABS-OMT-UPG * ABS-SERVER-ALPHA * ABS-SERVER-VAX * HSM-SERVER * SLS * SLS-MGR * SLS-REMOTE * SLS-REMOTE-MGR If you do not have one of these licenses registered, please refer to the section on registering the license for ABS or HSM whichever you are installing. 3.1.6 Verify the Node is in the MDMS Database If this installation is not the initial installation of MDMS V3.0, you need to verify that the node you are installing MDMS on is in the MDMS database. Enter the following command on a node that has MDMS already installed on it and verify that the node you are installing MDMS on is in the database: $ MDMS SHOW NODE node_name_you_are_installing_on %MDMS-E-NOSUCHOBJECT, specified object does not exist If the node is not in the database, you receive the %MDMS-E-NOSUCHOBJECT error message and you should create the node. See the command reference guide for the qualifiers to use. If the node you are adding is an MDMS server node, be sure to use the /DATABASE qualifier. If the node you are creating is to be a database server node, you need to edit all SYS$STARTUP:MDMS$SYSTARTUP.COM files in your domain and add this node to the definition of MDMS$DATABASE_SERVERS. If the node is in the database, proceed with preinstallation tasks. The node may have been created when you converted from SLS/MDMS V2.x. If this the initial installation, you cannot create a node in the database. You will create the node during the post-installation. 3.1.7 Consider RDF Configuration MDMS provides RDF software to facilitate operations that require access to remote, network connected tape drives. This allows you to copy data from a local site to a remote site, or copy data from a remote site to a local site. During the installation you will be asked questions on whether you want to install on this node, the software that will allow it to act as a server and/or client for the RDF software. You need to decide if you want the server and/or client installed on the node. * Install the RDF Server software on all nodes that are connected to the tape drives used for remote operations. * Install the RDF Client software on all nodes that initiate remote operations to tape drives on the RDF Server node. After installing RDF you may have to reboot your system. A new driver is included with this kit. If you have never installed RDF before a reboot is not needed. If you already have RDF installed, you do not need to reboot unless you need the new driver installed. It will be installed on the next reboot. 3.2 Installing the MDMS Software The MDMS installation procedure consists of a series of questions and informational messages. Once you start the installation procedure, it presents you with a variety of questions that will change depending on whether the installation is the first or a subsequent installation. The installation procedure provides detailed information about the decisions you will make. If for any reason you need to abort the installation procedure at any time, you can press CTRL/Y and the installation procedure deletes all files it has created up to that point and exits. Note that you can restart the installation procedure from this point, at any time. Be sure to read Section 3.4 for information on selecting GUI kits to be extracted from the saveset during this installation. To install MDMS: 1. load the distribution medium into a suitable device, and mount the volume 2. invoke the VMSINSTAL procedure using the following command: $ @SYS$UPDATE:VMSINSTAL MDMS030 location: OPTIONS N Where: location: is the device and directory that contains the software kit save set. OPTIONS: N is an optional parameter that indicates you want to seen the question on Release Notes. If you do not include the OPTIONS:N parameter, VMSINSTAL does not ask you about the Release Notes. You should review the Release Notes before proceeding with the installation in case they contain additional information about the installation procedure. Follow the instructions as you are prompted to complete the installation. Each question you are asked is provided with alternatives for the decision you can take and an explanation for the related decision. Questions and decisions offered by the installation procedure vary. Subsequent installations will not prompt you for information you provided during the first installation. 3.3 MDMS Post-installation Tasks The following sections describe the post-installation tasks needed after installing the MDMS: Action Section Create a Node Object Section See Create a Node Object Provide Automatic Start Up and Section See Provide Automatic Start Up Shut Down and Shut Down Remove SLS/MDMS V2.x Automatic Section See Remove SLS/MDMS V2.x Startup Automatic Startup Configure MDMS Section See Configure MDMS Configure remote tape drives Section See Configure Remote Tape Drives Grant MDMS Rights to Users Section See Grant MDMS Rights to Users Installing the DCL tables on Section See Installing the DCL tables on Nodes Nodes 3.3.1 Create a Node Object If this is the initial installation of MDMS, you need to create the node object in the MDMS node database for this node. Use the MDMS CREATE NODE command to create this initial database node. Refer to the command reference guide for the qualifiers for this command. The following is an example: $ MDMS CREATE NODE NABORS - ! NABORS is the DECnet Phase IV node name or a ! name you make up if you do not use DECnet ! Phase IV in your network /DATABASE_SERVER - ! a potential database node ! must also be defined in ! in SYS$STARTUP:MDMS$SYSTARTUP.COM /TCPIP_FULLNAME=NABORS.SITE.INC.COM - ! the TCP/IP full node name if you ! are using TCP/IP you need this if ! you are using the GUI /DECNET_FULLNAME=INC:.SITE.NABORS - ! this is the full DECnet Phase V node name ! do not define if you do not have DECnet Phase V on this node ! be sure to define if you have DECnet Phase V installed on this node /TRANSPORT=(DECNET,TCPIP) ! describes the transports that listeners are ! started up on 3.3.2 Provide Automatic Start Up and Shut Down To automatically start MDMS when you initiate a system start up, at a location after the DECnet or TCP/IP start up command, add the following line in the system's start up file, SYS$MANAGER:SYSTARTUP_VMS.COM: $ @SYS$STARTUP:MDMS$STARTUP To automatically stop MDMS when you initiate a system shut down, enter the following into the system's shut down file: $ @SYS$STARTUP:MDMS$SHUTDOWN While using MDMS V3.0 with ABS, make sure that MDMS startup is executed prior to ABS startup. ABS needs a logical name that is defined by the MDMS startup. 3.3.3 Remove SLS/MDMS V2.x Automatic Startup If you have been using SLS/MDMS V2.x before and all your nodes running ABS and/or HSM version now support the new MDMS V3.0 make sure you remove this line from your system's start up file: $ @SYS$STARTUP:SLS$STARTUP If this node still needs to support clients that use SLS/MDMS V2.x refer to the Appendix SLS/MDMS V2.x Compatibility in the guide to operations. Until you have made all of the changes described in this appendix, you should not start up SLS/MDMS V2.x. You must have performed the conversion procedure as described in Section See Configure MDMS before editing the TAPESTART.COM file. 3.3.4 Configure MDMS Now that you have installed MDMS you need to configure MDMS by creating the following objects: * Media types * Locations * Nodes * Groups * Jukeboxes * Tape Drives * Magazines * Pools * Volumes Please refer to the MDMS section in the guide to operations for more information on configuration and operation. If you upgrading from SLS/MDMS V2.x you can convert the SLS/MDMS V2.x symbols and database to the MDMS V3.0 database. Use the procedure described in the appendix of the guide to operations. Once MDMS V3.0 is installed, and any conversions are performed, you may wish to adjust your configuration prior to performing MDMS operations 3.3.5 Configure Remote Tape Drives If you installed the RDF software, you need to configure the remote tape drives. For each tape drive served with RDF Server software, make sure there is a drive object record in the MDMS database that describes it. Refer to the chapters on MDMS configuration in the guide to operations and the MDMS CREATE DRIVE command in the command reference guide. For each node connected to the tape drive, edit the file TTI_RDEV:CONFIG_node.DAT and make sure that all tape drives are represented in the file. The syntax for representing tape drives is given in the file. During startup of MDMS, the RDF client and server are also started. The RDF images are linked on your system. If you see the following link errors on Alpha V6.2, this is not an RDF bug. The problem is caused by installed VMS patches ALPCOMPAT_062 and ALPCLUSIO01_062. %LINK-I-DATMISMCH, creation date of 11-FEB-1997 15:16 in shareable image SYS$COMMON:[SYSLIB]DISMNTSHR.EXE;3 differs from date of 4-MAY-1995 22:33 in shareable image library SYS$COMMON:[SYSLIB]IMAGELIB.OLB;1 . . . This is a known problem and is documented in TIMA. To correct the problem, issue the following DCL commands: $ LIBRARY/REPLACE/SHARE SYS$LIBRARY:IMAGELIB.OLB SYS$SHARE:DISMNTSHR.EXE $ LIBRARY/REPLACE/SHARE SYS$LIBRARY:IMAGELIB.OLB SYS$SHARE:INIT$SHR.EXE $ LIBRARY/REPLACE/SHARE SYS$LIBRARY:IMAGELIB.OLB SYS$SHARE:MOUNTSHR.EXE 3.3.6 Grant MDMS Rights to Users Before any user can use MDMS, you must grant MDMS rights to those users. Refer to the MDMS Rights and Privileges Appendix in the Archive/Backup System for OpenVMS Command Reference Guide for explanation of MDMS rights and how to assign them. 3.3.7 Installing the DCL tables on Nodes To make MDMS commands available on all nodes of the cluster, you should ensure that all nodes have the latest version of DCLTABLES.EXE installed. You can do this by using SYSMAN or by logging into each node in the cluster and enter the following command: $ INSTALL REPLACE SYS$COMMON:[SYSLIB]DCLTABLES.EXE 3.4 Graphical User Interface(GUI) Installation This section describes how to install and run the Graphical User Interface (GUI) on various platforms. As the GUI is based on Java, you must have the Java virtual machine installed on the system you run the MDMS GUI on. If you do not have Java installed on your system, these sections describe what is needed and where to get it. This installation procedure extracts files from the MDMS kit and places them in MDMS$ROOT:[GUI...]. You can then move the files to your Windows system and install them. For the GUI to communicate with the MDMS server, you must have TCP/IP services on the node where you have the MDMS server running. After installation be sure to refer to section 3.5 to run the GUI. 3.4.1 Requirements The GUI requires the following in order to run: Virtual Machine Since the MDMS GUI is a Java application, it requires the platform specific Java Virtual Machine. The availability of each Java Virtual Machine is described in the following sections. The best way of getting a Java Virtual Machine is to down load the platform-specific kit from the given URLs. If this is not possible, the MDMS package also contains a copy for your convenience. Issues concerning availability and installation of the Java Virtual Machine can be directed to: http://www.sun.com/java/products for Windows NT and http://www.digital.com/java/download/jdk_ovms/1.1.8/index.html for OpenVMS A Java Virtual Machine is included in this MDMS kit for the purpose of completeness. MDMS provides both the pointers (URLs) of downloading a Java Virtual Machine and the actual files of the Java Virtual Machine in the release package. However, the downloading approach is encouraged. Memory - The hard drive space requirement is 6 MB for Java Virtual Machine and 2 MB for MDMS GUI. The main memory space requirement for running MDMS GUI is 10 MB. 3.4.2 Installation on OpenVMS Alpha V7.1 and V7.2 The following steps describe how to install and run the MDMS GUI on OpenVMS Alpha: 1. If you are installing the GUI on OpenVMS Alpha V7.1, then the following patches (or their latest equivalent) need to be installed on the system. Please contact your Compaq representative for obtaining these patches. Patches Required for OpenVMS V7.1 for JAVA Patch Required For OpenVMS Fix Description Version Fixes needed to enable ALPBASE02_071 V7.1 to V7.1-H2 ALPACRT06_071 and ALPSYSA01_071. Must be installed first. ALPACRT06_071 V7.1 to V7.1-H2 DECC fixes-fork, exec ALPDCL01_071 V7.1 to V7.1-H2 Fixes for multiple kernel threading Problem ALPSYSA01_071 V7.1 to V7.1-H2 Higher-priority thread blocking ALPSYSB02_071 V7.1 to V7.1-H2 IEEE arithmetic ALPTHREADS_03071 V7.1 to V7.1-H2 DECthreads; support for Java, selected fixes VMS712_PTHREADS V7.1-2 ONLY DECthreads; support for Java, selected fixes These patches are not required for installation on OpenVMS Alpha V7.2. 1. Extract the files for the OpenVMS Java Virtual Machine. You may use the Java kit provided with the MDMS kit or download files from the Web. If you want to install from the MDMS kit, answer YES to the following question: Do you want the OpenVMS Java kit extracted [NO]? If you install from the MDMS kit, a file called: MDMS$ROOT:[GUI.VMS]DEC-AXPVMS-JAVA-V0101-81-1.PCSI_DCX_AXPEXE is created. Use this file to install Java as in step 4. 1. In the MDMS installation, the following question is asked. Do you want the MDMS GUI installed on Alpha OpenVMS [YES]? Reply `Yes' to the question if you want to install the GUI on OpenVMS. Files will be moved to MDMS$ROOT:[GUI.VMS] and the GUI installation will be completed. 1. Following the MDMS installation, you should install Java by first extracting the PCSI file for the Java installation using the following commands: $ SET DEFAULT MDMS$ROOT:[GUI.VMS] $ RUN DEC-AXPVMS-JAVA-V0101-81-1.PCSI_DCX_AXPEXE Extract and read the Release Notes for additional information on how to use this product in an OpenVMS environment: $ PRODUCT EXTRACT RELEASE_NOTES JAVA- /SOURCE=[directory_where_you_put_the_PCSI_file]- /FILE=[directory_where_you_want_it]JDK118_VMS_RELEASE_NOTES.HTML- /BASE_SYSTEM=AXPVMS Install the JDK1.1.8 from the .PCSI file obtained: $ PRODUCT INSTALL JAVA- /SOURCE=[directory_where_you_put_the_PCSI_file]/BASE_SYSTEM=AXPVMS The following files are installed by PCSI (POLYCENTER Software Installation utility) with file attribute of ARCHIVE: SYS$MANAGER:JAVA$SETUP.COM SYS$MANAGER:JAVA$STARTUP.COM SYS$SYSROOT:[JAVA.LIB]FONT.PROPERTIES SYS$SYSROOT:[JAVA.LIB]FONT_PROPERTIES.JA If a file having any of these names already exists on the system, the installation process renames it to a new name with the file type ending `_OLD', before loading the new copy from the kit. Only the latest version of the existing file is preserved (by being renamed to file.type_old) before PCSI deletes all remaining versions. For example, an existing SYS$MANAGER:JAVA$SETUP.COM is renamed to SYS$MANAGER:JAVA$SETUP.COM_OLD before the new copy is copied from the kit. If you have previously personalized any of these files, you might need to merge your personalizations with the new copy. The JDK documentation is installed on your system at the following location: SYS$COMMON:[SYSHLP.JAVA]INDEX.HTML 1. After installation you must do the following: $ EDIT SYS$STARTUP:JAVA$SETUP.COM and include the following logical name definition at the end of the file: $ DEFINE JAVA$CLASSPATH - MDMS$ROOT:[GUI.VMS]MDMS.ZIP,- MDMS$ROOT:[GUI.VMS]SYMANTEC.ZIP, - MDMS$ROOT:[GUI.VMS]SWINGALL.JAR, - SYS$COMMON:[JAVA.LIB]JDK118_CLASSES.ZIP 1. Run JAVA$SETUP.COM to establish defaults for the logical names CLASSPATH and JAVA$FILENAME_CONTROLS, and to define symbols that determine whether Java will interpret commands as either foreign commands or DCL commands: $ @SYS$MANAGER:JAVA$SETUP.COM Add the above command line to SYS$COMMON:[SYSMGR]SYLOGIN.COM so that when users login, they will have the Java definitions. Make sure that the logical JAVA$USE_DCL is not defined or the GUI will not work. 1. The JAVA$SETUP.COM procedure calls: SYS$SYSROOT:[SYSHLP.JAVA]JAVA$FILENAME_CONTROLS.COM to establish the JAVA$FILENAME_CONTROLS default values. You can edit this file to see what defaults are being used and how to change them. (This information is also in the "UNIX Style Filenames on an OpenVMS System" section of the JDK release notes.) 1. Rename the file SYS$COMMON:[JAVA.LIB]FONT.PROPERTIES to another name. This file remaps the fonts and makes the MDMS GUI appear incorrect. Renaming the file to another name will cause Java to use the default fonts, which are necessary to run the MDMS GUI. 2. If you are running the GUI using a non-PC keyboard, for example an OpenVMS keyboard, issue the following command on the system running the GUI: $mcr decw$utils:xmodmap -e "keysym Delete = BackSpace Delete" 3.4.3 Installation on Intel Windows NT/95/98 The following describes how to install the MDMS GUI on Intel platforms running Windows NT/95/98: 1. In the MDMS installation, the following question is asked. Do you want files extracted for Microsoft Windows NT/95/98 on Intel [YES]? Reply YES if you want to install the GUI on Intel Windows NT/95/98. 1. Install the Java Virtual Machine - If Java Virtual Machine is not already installed on your PC, down load JRE 1.1.8 from: http://www.javasoft.com/products/jdk/1.1/jre or http://www.sun.com/developers/developers.html and follow the instructions to perform a default installation. You may use other versions of JRE, preferably 1.1.8 or later. If a Java Virtual Machine is not available, you may use MDMS$ROOT:[GUI.INTEL]JRE117WINTEL.EXE. Simply double-click on this file to install Java, and follow the setup instructions. 1. Install the MDMS GUI: Make MDMS$ROOT:[GUI.INTEL]SETUP_INTEL.EXE available to the target machine (Intel PC running Windows NT/95/98) Run SETUP_INTEL.EXE on the target machine. 3.4.4 Installation on Alpha Windows NT The following describes how to install the MDMS GUI on an Alpha platform running Windows NT: 1. In the MDMS installation, the following question is asked. Reply YES if you want to install the GUI on Alpha NT. Do you want the MDMS GUI files extracted for Alpha NT [YES] ? 2. Install the Java Virtual Machine - If Java Virtual Machine is not already installed on your Alpha, down load JRE 1.1.8 from: http://www.digital.com/java/download/jre_nt/1.1.8/jre118_down.html and follow the instruction to perform a default installation. If a Java Virtual Machine is not available, you may use: MDMS$ROOT:[GUI.ALPHA_NT]JRE118ALPHANT.EXE. 4. Install FX!32 if not installed and make sure FX!32 is enabled. 5. Install the MDMS GUI: 6. Make MDMS$ROOT:[GUI.ALPHA_NT]SETUP_ALPHA_NT.EXE available to the target machine (Alpha PC running Windows NT) 7. Run SETUP_ALPHA_NT.EXE on the target machine. 8. If the 'Unzip To' folder has been modified to anything other than default directory, remember to modify the MDMS_GUI.BAT. 3.5 Running the GUI Now that you have installed the GUI, you have to make sure the server node is configured to accept communications from the GUI. The server node for the GUI must have: * TCP/IP enabled and * the MDMS rights enabled in the SYSUAF record for the user To enable TCP/IP communications on the server, you have to set the TCP/IP Fullname attribute and enable the TCPIP transport. See the command reference guide for information about setting these attributes in a node. MDMS rights for the user must be enabled in the SYSUAF record to log into the server using the GUI. Refer to the command reference guide for information about MDMS rights. The following sections describe how to run the GUI on various platforms. 3.5.1 Running the GUI on OpenVMS Alpha To use the MDMS GUI on OpenVMS Alpha systems, use the following commands: $ @SYS$STARTUP:JAVA$SETUP.COM $ SET DISPLAY/CREATE/NODE=node_name/TRANSPORT=transport $ MDMS/INTERFACE=GUI For the SET DISPLAY command, the node_name is the name of the node on which the monitor screen exists. This allows you to use the GUI on systems other than those running OpenVMS Alpha V7.1 or higher. The transport must be a keyword of: * LOCAL - if you are running the GUI on the same node as the monitor * DECNET - if you are running the GUI on a monitor connected to another node and you wish to use DECnet protocol between the monitor node and the GUI Java node. * TCPIP - if you are running the GUI on a monitor connected to another node and you wish to use TCPIP protocol between the monitor node and the GUI Java node. 3.5.2 Running the GUI on Intel Windows NT/95/98 To use the MDMS GUI on Intel Windows NT/95/98 platforms, double click MDMS_GUI\MDMS_GUI.BAT. 3.5.3 Running the GUI on Alpha Windows NT To use the MDMS GUI on Alpha Windows NT, do one the following: 1. If both the Java Virtual Machine and the MDMS GUI were installed with default selection, then double click MDMS_GUI\MDMS_GUI.BAT 2. Otherwise in MDMS_GUI\MDMS_GUI.bat, replace the Java Virtual Machine directory and MDMS_GUI directory as necessary, double click MDMS_GUI\MDMS_GUI.BAT. 4 Installing ABS Software This chapter contains instructions for installing Archive/Backup System for OpenVMS Version 3.0 software. Before proceeding with the installation procedure, make sure you have completed all of the following preinstallation tasks: * Did you decide where to install ABS server and client software? * Did you set your default directory to SYS$UPDATE? * Did you log into an account with the proper quotas and privileges? * Did you perform a system backup operation? * If you are doing an upgrade installation, did you shutdown ABS? * Did you verify the hardware and disk space requirements? * Did you verify the software requirements? * Did you check to see if DECnet (Phase IV) or DECnet-Plus and the QueueManager are running? * Did you register the appropriate licenses? * Did you install MDMS, or is it already installed? * Did you follow the steps required for converting to a new scheduling option? 4.1 Installing Archive/Backup System for OpenVMS Software Now that you have successfully installed and configured MDMS software, see See Stages of Installing ABS Software for the stages of installing and configuring ABS Version 3.0 software. Before installing ABS in a real time, storage management environment, COMPAQ recommends that you first install and configure ABS in a test environment. If you are not satisfied with the test installation, delete ABS and reinstall it. How To Delete ABS From Your System To delete ABS software from your system, shut down ABS and delete it from the system: $ @SYS$MANAGER:ABS$SHUTDOWN $ @ABS$SYSTEM:DELETE_ABS Stages of Installing ABS Software Stage Action 1. Install ABS server software as described in See Installing ABS Server Software. Note: If you are installing ABS in a mixed architecture environment (VAX and Alpha systems resident in a single OpenVMS Cluster), follow the installation instructions in See Installing ABS in a 2. Mixed-Architecture OpenVMS Cluster. Install ABS OpenVMS client software as described in See 3. Installing ABS OpenVMS Client Software. 4. Install ABS NT client software as described in See Installing and Configuring ABS NT Clients. 5. Install ABS UNIX clients as described in See Configuring ABS UNIX Clients. 6. Authorize NT and UNIX clients as described in See Authorizing NT and UNIX Clients. 7. Edit the system startup and shutdown files as described in See Verifying ABS Installation. 8. Verify for all OpenVMS Cluster requirements have been met as described in See Providing Automatic Start Up and Shut Down. 9. Verify ABS installation procedure as described in See Installing ABS for the First Time. 10. Verify that all default policy objects are resident on ABS server node as described in See Granting the Appropriate ABS 11. Access Right Identifiers. 12. Modify the default policy objects as described in See Revoking 13. An Access Rights Identifier. 14. Verify the tape drive connections as described in See Modifying The ABS Default Policy Objects. 4.1.1 Installing ABS Server Software ABS installation procedure consists of a series of questions and informational messages. See provides a sample installation log file. If for any reason you need to abort the installation procedure, at any time you can press CTRL/Y and the installation procedure deletes all files it has created up to that point and then exits. From this point, you can restart the installation procedure again. Follow the steps in See How to Install ABS Software to install ABS Version 3.0 software. How to Install ABS Software Step Action 1. Invoke VMSINSTAL: $ @SYS$UPDATE:VMSINSTAL saveset-name drive-name OPTIONS N To start the installation, invoke the VMSINSTAL command procedure from a privileged account, such as the SYSTEM account. VMSINSTAL is in the SYS$UPDATE directory. The following list defines the elements of the VMSINSTAL command procedure: save set name The installation name for the component. ABS030 drive-name The name of the drive where the media that contains the kit is located. For example, MTA0: is the device name for a tape drive or device:[directory] can be the CD-ROM drive name. It is not necessary to use the console drive for this installation. However, if you do use the console drive, you should replace any media you removed once the installation is complete. OPTIONS N An optional parameter that indicates you want to see the question on release notes. If you do not include the OPTIONS N parameter, VMSINSTAL does not ask you about the release notes. You should review the release notes before proceeding with the installation in case they contain additional information about the installation. Note: If you are restarting the installation and have already reviewed the release notes, you do not need to specify OPTIONS N. If you specify more than one option, separate them with commas (OPTIONS A,N). The following examples invoke VMSINSTAL to install ABS from the tape drive MTA0: and shows the responses. This example uses the OPTIONS N release note parameter. $ @SYS$UPDATE:VMSINSTAL ABS030 MTA0: OPTIONS N OpenVMS VAX Software Product Installation Procedure V6.1 It is 21-JUL-1996 at 10:00 Enter a question mark (?) at any time for help. If you do not supply either the product name or the drive name, VMSINSTAL prompts you for this information later in the installation procedure. Note: VMSINSTAL does not prompt you for any options, so be sure to include OPTIONS N on the VMSINSTAL command line to access the release notes during the installation procedure. See OpenVMS documentation located in the OpenVMS System Management Subkit for detailed information on these options. 2. Confirm system backup: * Are you satisfied with the backup of your system disk [YES]? VMSINSTAL asks if you are satisfied with your system backup. You should always back up your system disk before performing an installation. If you are satisfied with the backup of your system disk, press RETURN. Otherwise, enter NO to abort the installation. After you back up your system disk, you can restart the installation. Select the Release Notes Options: If you specified OPTIONS N when you invoked VMSINSTAL, you are now asked to choose one of the following options for reviewing the release notes. Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: IF you select . . . Option 1- VMSINSTAL displays the release notes immediately on the console terminal. You can terminate the display at any time by pressing CTRL/C. Option 2-VMSINSTAL prompts you for the name of the print queue that you want to print the release notes on: * Queue name [SYS$PRINT]: Press RETURN to send the file to SYS$PRINT or enter another queue name. Option 3-VMSINSTAL displays the release notes immediately on the console terminal and then prompts you for a queue name as described in Option 2. Option 4-The release notes are not displayed or printed. Next, VMSINSTAL displays the following question: * Do you want to continue the installation [N]?: YES %VMSINSTAL-I-RELMOVED, The product's release notes have been successfully moved to SYS$HELP. To continue the installation, enter YES. Otherwise, press RETURN. In either case, the release notes are copied to the following directory and file specification: SYS$HELP::ABS030.RELEASE_NOTES The name of the release notes file installed by VMSINSTAL consists of the current product name and version number. Do not delete release notes for previous versions of ABS. Release notes are always placed in the SYS$HELP directory. Purge files: 3. * Do you want to purge files replaced by this installation [YES]? You may purge files from previous versions of ABS. Those files are superseded by this installation. Purging is recommended. However, if you need to keep files from the previous version, enter NO in response to this question. Note: We recommend you to save the customized files of previous version of ABS in a separate directory before you answer YES and proceed with purging. Choose the Installation Verification Procedure (IVP) option: * Do you want to run the IVP after the installation [YES]? The installation procedure now asks if you want to run the IVP. The IVP checks to be sure that the installation is successful. It is recommended that you answer Yes to this prompt. If errors occur during the installation procedure, VMSINSTAL displays the following message: %VMSINSTAL-E-INSFAIL, The installation of ABS Version 3.0 has failed. Note: If you answered No to this prompt, after ABS is installed, independently run the IVP to verify that the software is available on your system. You may also need to run the IVP after a system failure to make sure that users can access ABS. See Verifying ABS Installation describes how to independently run the IVP. Respond to license registration queries. ABS-SERVER-VAX or ABS-SERVER-ALPHA ABS-CLIENT-VAX or ABS-CLIENT-ALPHA ABS-OMT with ABS-OMT-UPG License SLS SLS-ACS SLS-MGR SLS-REMOTE SLS-REMOTE-MGR 4. * Does this product have an authorization key registered and loaded? The installation procedure displays license information about your product and then asks if you have registered and loaded your Product Authorization Key (PAK). Note: If you have not registered and loaded your PAK, you must answer NO to this question. You must register and load the PAK to successfully complete the installation. If you have not done so, stop the installation, register and load the PAK, and restart the installation. Instructions for loading and registering your PAK is described in See Registering ABS Licenses. 5. Choose the ABS$ROOT disk device: * Enter the disk device name to use for ABS files [SYS$COMMON]: This disk device will contain ABS images, databases, and log files. Enter the name of the disk that will be ABS server. Use your information your recorded in See Installation Worksheet. Requirement: This disk device must have at least 40,000 free blocks and be available to all nodes in the OpenVMS Cluster that will be running ABS. 6. Enter the ABS account UIC: * Enter the UIC to be used for ABS account [[311,311]]: ABS account is not an interactive account and is used only for ABS processes. The password for ABS account is automatically generated by the installation procedure. If you choose to change the default UIC assignment, it must be unique and it cannot be a member of a SYSTEM UIC group. Choose the policy engine node or OpenVMS Cluster nodes (ABS Server): * Node name list for ABS Policy Engine [SVNODE::]: SVNODE 7. Enter the OpenVMS Cluster nodes or OpenVMS node name that you have designated for serving the ABS policy engine database. This node (or list of OpenVMS Cluster nodes) becomes ABS server nodes, sometimes referred to as the central security domain (CSD). Do not specify an OpenVMS Cluster alias name in the list. Note: The policy engine node information resides in the following directory and file name: ABS$SYSTEM:ABS$POLICY_CONFIG.DAT. If at some point in time you want to change the ABS server node name list, you can edit this file to change the policy engine (server) node(s) without having to reinstall ABS. For example, locate the last line in the file and change the following node information: ABS$POLICY_ENGINE_LOCATION = NODESV:: 8. Do not change any other information in this file. Choose the scheduling option: ABS allows the following scheduling options: * NONE * DECSCHEDULER * EXT_SCHEDULER * INT_QUEUE_MANAGER * EXT_QUEUE_MANAGER * Choose the Scheduling Option [INT_QUEUE_MANAGER]: 9. Enter the scheduling option you wish to use. The default is INT_QUEUE_MANAGER. See the ABS Release Notes for an explanation of these options Read the informational messages. At this point, the installation procedure displays a number of informational messages that report on the progress of the installation. There are no further questions. If the installation procedure has been successful up to this point, VMSINSTAL moves the new or modified files to their target directories, updates helpfiles, and updates DCL tables, if necessary. If you chose to have files purged, that work is done now. The installation procedure displays the following messages: %VMSINSTAL-I-MOVEFILES, files will now be moved to their target directories... 10. Observe the Installation Verification Procedure (IVP): If you selected to run the IVP in Step 7, VMSINSTAL runs it now. When the IVP runs successfully, the following is displayed: The IVP for Archive/Backup V3.0 was successful. End the installation procedure: Installation of ABS Version 3.0 completed at 12:46 VMSINSTAL procedure done at 12:47 11. The previous messages indicate that the entire installation procedure is complete. You can now log out of the privileged account: $ LOGOUT $ SYSTEM logged out at 21-JUL-1996 12:50:00:00 Note: VMSINSTAL deletes or changes entries in the process symbol tables during the installation. Therefore, if you are going to continue using the system manager's account and you want to restore these symbols, log off and log on again. 4.1.2 Installing ABS in a Mixed-Architecture OpenVMS Cluster If you are installing ABS on an OpenVMS Cluster system (contains both VAX and Alpha systems), you must meet the following requirements and install ABS as described in See Installing ABS in a Mixed-Architecture OpenVMS Cluster. Requirements: * The version of ABS must be the same on the OpenVMS VAX and the OpenVMS Alpha system(s). * If you are using Oracle Rdb for the policy database, the versions of Oracle Rdb installed on the OpenVMS VAX and OpenVMS Alpha system(s) must be compatible. For example, you cannot have Oracle Rdb Version 6.0 on the OpenVMS Alpha system and Oracle Rdb Version 5.1 on the OpenVMS VAX system. Those two versions of Oracle Rdb are not compatible. To ensure ABS functions correctly, each architecture must have its own set of .EXE and .UID files, but all other files required by ABS can be shared by both the VAX and Alpha system(s) on a common disk. See Installing ABS in a Mixed-Architecture OpenVMS Cluster describes how to configure ABS files on both types of systems. Installing ABS in a Mixed-Architecture OpenVMS Cluster Step Action 1. Install ABS on the VAX system in the OpenVMS Cluster as instructed in See Installing ABS Server Software. When the installation procedure prompts for the disk name to use for ABS files (Step 9 in See How to Install ABS Software), enter the disk name that can be accessed by both the VAX and Alpha system in the OpenVMS Cluster. For example, assume that the VAX system has a disk named DISK$SYSTEM_1 that is common to both the VAX and Alpha nodes in the OpenVMS Cluster (see Figure 1). Result: The installation procedure creates a directory named DISK$SYSTEM_1:[ABS] (which translates to ABS$ROOT) on the VAX system and also creates all of its subdirectories. Create two new directories on the common disk that will contain the .EXE and .UID files for the VAX and Alpha systems: $ CREATE/DIRECTORY ABS$ROOT:[SYSTEM.VAX] $ CREATE/DIRECTORY ABS$ROOT:[SYSTEM.ALPHA] Move the .EXE and .UID files from the VAX installation to the VAX directory: $ SET DEFAULT ABS$ROOT:[SYSTEM] $ RENAME *.EXE,*.UID [.VAX] Install ABS on the OpenVMS Alpha system in the OpenVMS Cluster as instructed in See Installing ABS Server Software . 2. When the installation procedure prompts for a disk name to use for ABS files, enter one the Alpha disks. For example, assume that the Alpha system has a disk named DISK$ALPHA. Result: The installation procedure creates a directory named DISK$ALPHA:[ABS] (which translates to ABS$ROOT) on the Alpha system and also creates all of its subdirectories (see Figure 1). 3. Copy the .EXE and .UID files from the Alpha installation to the appropriate directory on the common disk located on the VAX system: $ SET DEFAULT ABS$ROOT:[SYSTEM] $ COPY *.EXE,*.UID DISK$SYSTEM_1:[ABS.SYSTEM.ALPHA] 4. Edit the file SYS$STARTUP:ABS$ALTERNATE_ROOT.COM on both the VAX and Alpha systems. Define the logical ABS$ROOT to point to the common disk on the VAX system: ..$ Define/System/Exec/Trans=Conc ABS$ROOT DISK$SYSTEM_1:[ABS.] $ Exit 5. Edit the file SYS$STARTUP:ABS$STARTUP.COM on both the VAX and the Alpha system. Define the logical ABS$SYSTEM to be a search list: VAX System: . . . $! $ SysDefine ABS_SYSTEM ABS$ROOT:[SYSTEM],ABS$ROOT:[SYSTEM.VAX] $ SysDefine ABS$SYSTEM ABS$ROOT:[SYSTEM],ABS$ROOT:[SYSTEM.VAX] . . . Alpha System: . . . $! $ SysDefine ABS_SYSTEM ABS$ROOT:[SYSTEM],ABS$ROOT:[SYSTEM.ALPHA] $ SysDefine ABS$SYSTEM ABS$ROOT:[SYSTEM],ABS$ROOT:[SYSTEM.ALPHA] . . . 6. Edit the file ABS$SYSTEM:ABS$POLICY_CONFIG.DAT on the common disk to include both the VAX and Alpha node names: $ ABS$POLICY_ENGINE_LOCATION = NODE_V:: $ ABS$POLICY_ENGINE_LOCATION = NODE_A:: 7. Shutdown and restart ABS on both the VAX and Alpha systems by entering the following command at the system prompt on each system: $ @SYS$MANAGER:ABS$SHUTDOWN $ @SYS$STARTUP:ABS$STARTUP To increase disk space, once you have copied the .EXE and .UID files to the common disk, you can delete the extra ABS files on the Alpha system: $ SET DEFAULT ALPHA$DISK:[ABS] $ DELETE *.*;* You may have to set protections on directories to delete those files. 4.1.3 Installing ABS OpenVMS Client Software When installing ABS software, notice that ABS does not provide two separate software kits. Instead, installation of ABS OpenVMS server or client software is determined by the OpenVMS Cluster alias name or OpenVMS node name that you enter during the installation procedure. If you select to use the INT_QUEUE_MANAGER or EXT_QUEUE_MANAGER scheduling options, you must have ABS V3.0 installed on all of your ABS servers and ABS OpenVMS Clients. If you are using any other scheduling option, you may do a rolling upgrade of your clients. In those cases, ABS V2.2x may be running on the clients with ABS V3.0 running on the server. See Installing ABS OpenVMS Client Software describes how to install and configure an ABS OpenVMS client. In See Installing ABS OpenVMS Client Software, ABS server node is referred to as SVNODE::, and ABS client node is referred to as CLNODE:: Installing ABS OpenVMS Client Software Step Action 1. Install ABS software on the OpenVMS client node as described in See How to Install ABS Software except replace Step 11 with the following information: When the installation procedure prompts for the node name where ABS policy engine resides (ABS OpenVMS server node), do not accept the default node name (client node name). Instead, enter OpenVMS Cluster alias or OpenVMS node name that you entered when you installed ABS OpenVMS server software: * cluster or node list for ABS policy engine [CLNODE::] : SVNODE Result: ABS installs only the client portion of ABS software on the node named CLNODE::. 2. After installing ABS software on the OpenVMS client node, create a proxy account for ABS OpenVMS server node on ABS OpenVMS client node. On ABS OpenVMS client node (CLNODE::), enter the following set of DCL commands: $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> ADD/PROXY SVNODE::ABS ABS/DEFAULT UAF> EXIT Result: These commands allow CLNODE:: to submit a save or restore request from the client node. 3. Create save and restore requests for OpenVMS clients as described in Archive/Backup System for OpenVMS Guide to Operations . 4. Create (or modify) storage and environment policies. Archive/Backup System for OpenVMS Guide to Operations describes how to create those policies. 5. Create system and user backup operations using the correct storage and environment policies. Archive/Backup System for OpenVMS Guide to Operations , provides instructions for these tasks. 4.1.4 Installing and Configuring ABS NT Clients Requirements: * You must have eXcursion software installed on the NT client system if you want to use the graphical user interface (GUI) on the NT client system. * If you use FTP to copy the setup files to the NT System, be sure to copy the files in binary mode. See Stages of Installing an ABS NT Client describes the stages of installing and configuring an ABS NT client node. Stages of Installing an ABS NT Client Stage Action 1. Register ABS NT license on ABS OpenVMS server node. See Registering ABS Licenses for instructions. Install ABS NT client software on NT client system as described in See Installing and Configuring an ABS NT Client. Note: You must perform a separate installation on each NT client node that you want ABS to back up. 2. Authorize the NT client systems that you plan to back up using ABS (described in See Authorizing NT and UNIX Clients). 3. Create save and restore requests for the NT client system by using the GUI on the NT client system, or by using the GUI or DCL on ABS OpenVMS server node. See Archive/Backup System for OpenVMS Guide to Operations and Archive/Backup System for OpenVMS Command Reference Guide for instructions about creating save and restore requests for NT clients. To install and configure the NT client software, use the procedure in See Installing and Configuring an ABS NT Client. Installing and Configuring an ABS NT Client Step Action 1. Copy all files from one of the following directories located on ABS OpenVMS server node to the NT client system where you plan to install the NT client software, or to a location accessible by the NT client system. The NT client software is provided during ABS server installation procedure. ABS creates the appropriate directories and places the NT client software kits for Alpha and Intel systems in the following directories: ABS$ROOT:[CLIENTS.NT.ALPHA] ABS$ROOT:[CLIENTS.NT.INTEL] Run SETUP.EXE from this location to install ABS NT client software. Result: ABS NT client installation procedure prompts for information about the ABS server and the local host port number. 2. Answer the prompts exactly as you answered them during ABS server installation procedure: * ABS server node-Enter the node on which ABS server software has been installed and will be providing ABS services for the NT client backup operations. This node also verifies connection requests. * Local host port number-The NT client system uses a TCP/IP port to communicate with ABS server to initiate save and restore requests. The default port number is 1800. If you decide to change the port number, it is limited to a range between 1024 and 65535. This port number is arbitrary, but it must match the port number you use when you authorize NT clients. To test to see if port number 1800 is already in use, enter the following command from ABS OpenVMS server system prompt: $ TELNET node 1800 Where: node is the node name of the OpenVMS server node Note: Make sure that the number you provide does not conflict with a previously installed software application. 3. Authorize the NT clients you plan to back up using ABS as described in See Authorizing NT and UNIX Clients and See . 4.1.5 Configuring ABS UNIX Clients To allow ABS to perform backup and restore operations for UNIX clients, you must configure access between the OpenVMS systems that run ABS server software and the UNIX client systems that contain the files to be backed up. The stages of installing and configuring a UNIX client is described in See Stages of Installing and Configuring an ABS UNIX Client. There is no extra software kit provided for UNIX clients. Stages of Installing and Configuring an ABS UNIX Client Stage Action 1. Register ABS UNIX license on ABS OpenVMS server node. See Registering ABS Licenses for instructions. 2. Modify the appropriate files on the UNIX client system as described in the See Modifying the Appropriate UNIX Files. 3. Transfer the gtar and gzip sources from ABS OpenVMS server node to each UNIX client system that you intend to back up using ABS. See Transferring the UNIX Backup Agent Sources. 4. Build the executables on each UNIX client system that you plan to back up using ABS as described in See Building the UNIX Executables. 5. Authorize the UNIX clients as described in See Authorizing NT and UNIX Clients and See . 6. Create save and restore requests for the UNIX client from the OpenVMS server node. See Archive/Backup System for OpenVMS Guide to Operations and Archive/Backup System for OpenVMS Command Reference Guide for instructions about creating save and restore requests for UNIX clients. 4.1.5.1 Modifying the Appropriate UNIX Files See Modifying the Appropriate UNIX Files lists the files that you need to modify on each UNIX client system that ABS is going to back up, and it describes the modifications to make for those specific files. UNIX is a case sensitive system. Be sure to enter the commands on the UNIX client system exactly as they are shown in See Modifying the Appropriate UNIX Files and See Transferring the Backup Agent Sources. Modifying the Appropriate UNIX Files File Modification Replace the ASCII readable internet address with ABS OpenVMS server nodes. The file format is: # readable ip address account node01.vms.real.node ABS #ABS on node NODE01 In this example, replace node01.vms.real.node with ABS OpenVMS server node names. The account name must stay the same (ABS), and it must be specified in capital letters. /.rhosts 5 Example of /.rhosts: node01.vms.real.node ABS node02.vms.real.node ABS Requirement: You must always modify the /.rhosts file. If the file does not exist, then you must create it. Be sure that the /.rhosts file is located in the root directory and that is owned by the root account because ABS uses this directory during the backup operation. List the numeric internet address and the ASCII readable internet address of ABS OpenVMS server nodes. The file format is: # Internet Address Hostname # Comments nn.nn.nn.nn node01.vms.real.node # example entry for hosts fil e Where: /etc/hosts a * nn.nn.nn.nn is the numeric internet address of ABS node that executes save and restore requests. * node01.vms.real.node is the ASCII readable internet address of nn.nn.nn.nn. You must enter every node name on which ABS may execute. Example of /etc/hosts: 01.02.03.04 node01.vms.real.node # node01 running ABS 01.02.01.04 node02.vms.real.node # node02 running ABS Note: If ABS OpenVMS server nodes are already listed in the file /etc/hosts, you do not need to add them again. 4.1.5.2 Transferring the UNIX Backup Agent Sources During the installation of ABS server software, the installation procedure creates a directory named ABS$ROOT:[CLIENTS.UNIX] on ABS server node. This directory contains the following two uncompressed sources that make up the UNIX backup agent: * ABS$ROOT:[CLIENTS.UNIX]TAR-1_12.TAR * ABS$ROOT:[CLIENTS.UNIX]GZIP-1_2_4.TAR To configure a UNIX client, you must transfer the gtar and gzip sources to each UNIX client system that ABS is going to back up, build the executables, and place them in /usr/bin. Refer to See Transferring the Backup Agent Sources (shown from a Digital UNIX system) to transfer the gtar and gzip sources from ABS server node to the UNIX client system. Transferring the Backup Agent Sources u_node> ftp node01 # Connect to the ABS OpenVMS Server Node Connected to node01.vms.dec.com. 220 node01 FTP Server (Version 3.3) Ready. Name (node01:user1) : user1 331 Username USER1 requires a Password. Password : 230 User logged in. Remote system type is VMS. ftp> cd abs$root:[clients.unix] # Change to the directory that contains the files 250 CWD command successful. ftp > pwd 257 "ABS$ROOT:[CLIENTS.UNIX]" is current directory. ftp > ls # List the files in this directory 200 PORT command successful. 150 Opening data connection for (16.82.16.75,1174) gnu_general_public_license.txt;4 gnu_readme_where_to_get.txt;4 gzip-1_2_4.tar;4 tar-1_11_8.tar;4 226 NLST Directory transfer complete. ftp > bin # set the file transfer mode to binary 200 TYPE set to IMAGE. ftp > get # Get the sources (remote-file) tar-1_11_8.tar (local-file) tar-1_11_8.tar 200 PORT command successful. 150 Opening data connection for tar-1_11_8.tar (16.82.16.75,1178) 226 Transfer complete. 2662400 bytes received in 5.7 seconds (4.6e+02 Kbytes/s) ftp > get # Get the sources (remote-file) gzip-1_2_4.tar (local-file) gzip-1_2_4.tar 200 PORT command successful. 150 Opening data connection for gzip-1_2_4.tar (16.82.16.75,1494) 226 Transfer complete. 798720 bytes received in 1.8 seconds (4.3e+02 Kbytes/s) ftp > quit 221 Goodbye 4.1.5.3 Building the UNIX Executables After you have transferred the gtar and gzip sources, you are required to build the executables on the UNIX client system. The following sections describe how to build the tar and gzip executables. Building the tar Executable Use the following procedure to build the tar executable: 1. Use native tar to expand the tar file 2. Change directory to the tar directory 3. Enter the command ./configure --disable-nls 4. Enter the command make to build the tar image 5. Verify the tar image was created 6. Change directory to src 7. Verify that it is an executable image 8. Change to super user 9. Copy the executable from src/tar to usr/bin/ABSgtar 10. Change the protection on the image 11. Display the complete directory 12. Exit super user 13. Perform a cleanup operation Example of tar u_node > tar -xvf tar-1_12.tar 1 tar-1.12/README tar-1.12/AUTHORS . . . tar-1.12/po/sv.gmo u_node > cd tar-1.12 2 u_node > configure --disable-nls 3 creating cache ./config.cache checking host system type... alpha-dec-osf3.2 . . . creating config.h u_node > make 4 for subdir in doc lib intl src scripts po; do \ echo making all in $subdir; \ (cd $subdir && make CC='gcc' CFLAGS='-g -O' LDFLAGS='' LIBS='' prefix='/usr/local' exec_prefix='/usr/local' bindir='/usr/local/bin' libexecdir='/usr/local/libexec' infodir='/usr/local/info' infodir='/usr/local/info' libexecdir='/usr/local/libexec' all) || exit 1; \ done making all in doc . . . make[1]: Leaving directory `/usr/users/user1/tar-1.11.8/po' u_node > ls src 5 Makefile checktar.sh extract.o list.c open3.h rmt.o tar.h . . . buffer.c diffarch.o gnu.c names.c rmt.c tar 5 u_node > cd src 6 u-node > file tar 7 tar: COFF format alpha dynamically linked, demand paged executable or object module not stripped - version 3.11-8 u-node > su 8 Password : # cp tar /usr/bin/ABSgtar 9 # chmod ugo+x /usr/bin/ABSgtar 10 # ls -l /usr/bin/ABSgtar 11 -rwxr-xr-x 1 root system 655794 Jan 24 11:07 ABSgtar # exit 12 u-node > cd .. 13 u-node > rm -rf tar-1_12 13 %rm -f tar-1_12.tar 13 Building the gzip Executable Use the following procedure to build the gzip executable: 1. Use the native tar to expand the gzip-1_2_4.tar image 2. Change directory to gzip-1.2.4 3. Enter the command ./configure 4. Enter the command make 5. Verify that the gzip file is there 6. Make sure it is an executable 7. Change to super user 8. Copy gzip file to /usr/bin/ABSgzip 9. Change the protection on the image 10. Exit super user 11. Perform a cleanup operation Example of gzip u_node > tar -xvf gzip-1_2_4.tar 1 gzip-1.2.4/README . . . gzip-1.2.4/primos/include/sysTypes.h u_node > cd gzip-1.2.4 2 u_node > ./configure 3 checking for gcc . . . checking for gzip to derive installation directory prefix chose installation directory prefix /usr/local creating config.status creating Makefile u_node > make 4 gcc -c -DSTDC_HEADERS=1 -DHAVE_UNISTD_H=1 -DDIRENT=1 -O gzip.c . . . gcc -O -o gzip gzip.o zip.o deflate.o trees.o bits.o unzip.o inflate.o util.o crypt.o lzw.o unlzw.o unpack.o unlzh.o getopt.o /usr/ucb/ld: Warning: Linking some objects which contain exception information sections and some which do not. This may cause fatal runtime exception handling problems (last obj encountered without exceptions was crypt.o). rm -f gunzip zcat ln gzip gunzip ln gzip zcat u_node > ls gzip 5 gzip u_node > file gzip 6 gzip: COFF format alpha dynamically linked, demand paged executable or object module not stripped - version 3.11-8 u-node > su 7 Password : # cp gzip /usr/bin/ABSgzip 8 # chmod ugo+x /usr/bin/ABSgzip 9 # ls -l /usr/bin/ABSgzip -rwxr-xr-x 1 root system 654785 Jan 24 11:08 ABSgzip # ln -s /usr/bin/ABSgzip /usr/bin/gzip # exit 10 u-node > cd .. 11 u-node > rm -rf gzip-1.2.4 11 u-node > rm -f gzip-1_2_4.tar 11 If you have problems transferring or building the tar or gzip files, see your UNIX system manager. 4.1.6 Authorizing NT and UNIX Clients After you have registered and loaded the NT or UNIX client license on ABS server node, run the authorization executable file to authorize the NT or UNIX client node names that you intend to back up using ABS. You must authorize access on the ABS OpenVMS server system for each UNIX and NT system that you are going to back up using ABS. See Authorizing NT and UNIX Client Nodes describes how to authorize NT and UNIX client nodes. ABS NT and UNIX client licenses are sold in units according to the number of nodes that you want to support: 1, 5, 10, 25, 50, or 100. ABS calculates the number of nodes authorized versus the number of units the license allows. You cannot authorize more NT or UNIX clients than the number of units allowed by the NT or UNIX client license that you have purchased. Authorizing NT and UNIX Client Nodes Step Action 1. Enter the following command from ABS server: $ RUN ABS$SYSTEM:ABS_CLIENT_LICENSE.EXE Add the node names of the UNIX or NT client nodes. When prompted, specify an NT or UNIX client: Would you like to Add/Modify/Remove/Show the Client License?: ADD 2. Enter Node Name: CLIENT_NODE_NAME Client Node Type (UNIX or NT) [UNIX]: NT Enter TCPIP Port Number [1800]: Note: The port number is arbitrary, but it must match the port number you use when you authorize NT clients, described in See Authorizing NT and UNIX Clients. 3. If the client node is an NT client, enter the port number. The default is 1800. 4. Make sure that the logical named ABS$CLIENT_DB is defined as /SYSTEM/EXEC and that it translates to ABS$ROOT:[DATABASE]CLIENT_DB.DAT. This logical name should be defined during the startup procedure. You can verify that the logical name is defined correctly by entering the following command: $ SHOW LOGICAL/FULL ABS$CLIENT_DB More Information: For an example of adding, modifying, removing and showing NT or UNIX Clients. 5 Performing Postinstallation Tasks Complete ABS postinstallation tasks described in this chapter after you have successfully installed ABS OpenVMS server or client software: * See Verifying ABS Installation describes how to verify the installation was successful. * See Providing Automatic Start Up and Shut Down explains how to edit the startup and shutdown files. * See Meeting OpenVMS Cluster Requirements describes the requirements for an OpenVMS Cluster installation. * See Granting the Appropriate ABS Access Right Identifiers explains how to set up access right identifiers. * See Modifying The ABS Default Policy Objects describes how to modify ABS default policy objects. * See Performing a Save, Lookup, and Restore Operation explains how to test ABS installation to perform save and restore requests. * See Verifying NT and UNIX Client Quotas explains how to set the quotas if you are supporting UNIX and NT clients. * See Adding NT Parameter describes the need of adding NT parameter, before issuing multivolume SAVE requests. 5.1 Installing ABS for the First Time If you are installing ABS as a new installation, database initialization programs may fail to run. This results in IVP failure with errors showing the storage classes and execution environments. To initialize the database with the default storage classes and execution environments, run ABS$SYSTEM:EPCOT_DB_INIT.EXE after installing ABS. 5.2 Verifying ABS Installation If you did not execute the IVP during the installation procedure, you can execute it immediately after installing ABS software. Enter the following command at the DCL system prompt: $ @SYS$TEST:ABS$IVP.COM If an error occurs during the IVP, the following message is displayed: ABS Version 3.0 Installation Verification Procedure failed. %VMSINSTAL-E-IVPFAIL, The IVP for ABS Version 3.0 has failed. Errors can occur during the installation if any of the following conditions exist: * ABS is currently running * The operating system version is incorrect * A prerequisite software version is incorrect * Quotas necessary for successful installation are insufficient * System parameter values for successful installation are insufficient * The OpenVMS help library is currently in use * The product license has not been registered and loaded For descriptions of the error messages generated by these conditions, see the OpenVMS documentation on system messages, recovery procedures, and OpenVMS software installation. If you are notified that any of these conditions exist, you should take the appropriate action as described in the message. 5.3 Providing Automatic Start Up and Shut Down You must edit the startup and shutdown files to provide automatic startup and shutdown of ABS software. To make sure that ABS automatically starts up and shuts down, follow these steps: 1. Add the following command line to the system startup file named SYS$MANAGER:SYSTARTUP_ VMS.COM: $ @SYS$STARTUP:ABS$STARTUP Add the following line to the system shutdown file named SYS$MANAGER:SYSHUTDOWN.COM: $ @SYS$MANAGER:ABS$SHUTDOWN When using MDMS V3.0