                                               H                     Save_Set_Manager_for_OpenVMS________________________/                     User and Installation Guide   -                     Order Number: AA-QDKQG-TE     >                     This manual contains installation and userB                     information for the Save Set Manager software.              F                     Operating Systems:            OpenVMS VAX VersionsG                                                   5.5-2, 6.2, 7.1 & 7.2 H                                                   and OpenVMS Alpha 6.2,;                                                   7.1 & 7.2   B                     Software Version:             Save Set Manager=                                                   Version 1.4           /                     Compaq Computer Corporation "                     Houston, Texas                 N               ________________________________________________________________               July 1999   F               Possession, use, or copying of the software described inG               this documentation is authorized only pursuant to a valid H               written license from COMPAQ, an authorized sublicenser, or&               the identified licenser.  D               While COMPAQ believes the information included in thisI               publication is correct as of the date of publication, it is /               subject to change without notice.   B               Compaq Computer Corporation makes no representationsD               that the interconnection of its products in the mannerF               described in this document will not infringe existing orE               future patent rights, nor do the descriptions contained F               in this document imply the granting of licenses to make,G               use, or sell equipment or software in accordance with the                description.  9               Copyright 1999 Compaq Computer Corporation. "               All Rights Reserved.6               Printed in the United States of America.  A               DEC, DIGITAL, MSCP, OpenVMS, StorageWorks, TK, VAX, C               VMScluster and the DIGITAL Logo are registered in the 8               United States Patent and Trademark Office.  E               Compaq and the Compaq Logo are registered in the United 1               States Patent and Trademark Office.   A               DECconnect, HSZ, StorageWorks, VMS, and OpenVMS are 8               trademarks of Compaq Computer Corporation.  C               AIX is registered trademark of International Business #               Machines Corporation.   ?               FTP Software is a trademark of FTP SOFTWARE, INC.   F               HP is a registered trademark of Hewlett-Packard Company.  9               NT is a trademark of Microsoft Corporation.   C               Oracle, Oracle Rdb, and Oracle RMU are all registered /               trademarks of Oracle Corporation.   I               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.   I               Solaris is a registered trademark of Sun Microsystems, Inc.   H               StorageTek is a registered trademark of Storage Technology               Corporation.  <               SunOS is a trademark of Sun Microsystems, Inc.  E               UNIX is a registered trademark in the United States and B               other countries, licensed exclusively through X/Open               Company Ltd.  E               Windows and Windows NT are both trademarks of Microsoft                Corporation.  D               All other trademarks and registered trademarks are the3               property of their respective holders.   I               This document was prepared using VAX DOCUMENT, Version 2.1.                                  F      _________________________________________________________________  F                                                               Contents      F      Preface...................................................    vii        1  Introduction  F          1.1  Advantages of SSMgr..............................    1-1F          1.2  SSMgr Functions..................................    1-2F          1.3  How SSMgr Changes Save Set Management Policy.....    1-3F          1.4  OpenVMS Compatibility............................    1-6F          1.4.1  ODS and Extended File Specification Support ...    1-6F          1.4.1.1   Disk Concepts...............................    1-6F          1.4.2  OpenVMS BACKUP Utility ........................    1-9F          1.4.3  VMScluster Support ............................   1-10F          1.4.4  OpenVMS License Management Facility ...........   1-10F          1.4.5  Privileges ....................................   1-10F          1.4.6  Internationalization of Messages ..............   1-10F          1.4.7  OpenVMS HELP Utility ..........................   1-10        2  Installation Procedure  F          2.1  Preinstallation Requirements and Preparations....    2-1F          2.2  License Registration.............................    2-1F          2.2.1  Privileges and Disk Space .....................    2-1F          2.2.2  Process Account Quotas ........................    2-2F          2.2.3  User Account Quotas ...........................    2-2F          2.2.4  VMSINSTAL Requirements ........................    2-3F          2.2.5  Backing Up Your System Disk ...................    2-4F          2.3  Installing the SSMgr Software....................    2-4F          2.3.1  The Installation Procedure ....................    2-4F          2.3.2  Error Recovery ................................    2-7F          2.3.3  Installation on V5.5-2 Systems ................    2-8F          2.4  SSMgr Sample Installation........................    2-9F          2.5  Reporting Product Problems.......................   2-12    F                                                                    iii                            3  Using SSMgr  I            3.1  Input and Output Save Set Specifiers.............     3-1 I            3.1.1   Input Save Sets ...............................    3-1 I            3.1.1.1   Input Save Sets on Disk.....................     3-2 I            3.1.1.2   Input Save Sets on Tape.....................     3-2 I            3.1.1.3   Input Save Sets on Multivolume Tape Sets....     3-3 I            3.1.2   Output Save Sets ..............................    3-5 I            3.1.2.1   Output Save Sets on Disk....................     3-5 I            3.1.2.2   Output Save Sets on Tape....................     3-5 I            3.1.2.3   Output Save Sets on Multivolume Tape Sets...     3-6 I            3.1.3   Files-11 Mount Example ........................    3-8 I            3.1.4   Multiple Output Save Sets .....................    3-9 6            3.2  Wildcards in Save Set and Journal FileI                 Specifiers.......................................    3-12 I            3.2.1   Wildcard Constraints on Input Save Sets .......   3-12 I            3.2.2   Wildcard Constraints on Output Save Sets ......   3-12 I            3.2.3   Wildcard Constraints on Journal File Names ....   3-13 I            3.3  SSMgr Command Language Interface.................    3-14   I                 COPY.............................................    3-15   I                 MERGE............................................    3-37   I                 VALIDATE.........................................    3-57   %         4  Interpreting SSMgr Reports   I            4.1  Monitoring the Progress of SSMgr Operations......     4-1 I            4.2  Completion Reporting.............................     4-2 I            4.2.1   Normal Successful Completion ..................    4-2 @            4.2.2   Successful Completion with Save Set ConditionI                    Report.........................................    4-2 I            4.2.3   Error Reporting ...............................    4-7 I            4.2.4   Log File ......................................    4-8            5  SSMgr Messages   I            5.1  SSMgr INFORMATIONAL Level Messages...............     5-1 I            5.2  SSMgr ERROR Level Messages.......................     5-1 I            5.3  SSMgr FATAL Level Error Messages.................     5-2 I            5.4  SSMgr WARNING level Error Mesages................     5-7 I            5.5  Terminal Messages................................     5-7 I            5.5.1   ERRORS Option Terminal Messages ...............    5-7 I            5.5.2   EVENTS Option Terminal Messages ...............    5-9 I            5.5.3   LOG Option Terminal Messages ..................   5-10   
         iv                   I            5.6  Process Quota Exceeded (System Message)..........    5-11   
         Index              Examples  I            3-1     A Files-11 Mount ..............................    3-8   I            3-2     COPY Command ..................................   3-27   I            3-3     COPY Command with Multiple Output Save Sets ...   3-27   ;            3-4     COPY Command with IDENTICAL and OVERRIDE I                    Qualifiers on Save Set with Errors.............   3-29   <            3-5     COPY with Wildcarding, Journaling, and NoI                    Logfile........................................   3-30   I            3-6     COPY with /JOURNAL and /TERMINAL Qualifiers ...   3-33   @            3-7     COPY with /BLOCK_SIZE, /GROUP_SIZE, and /FULLI                    Qualifiers.....................................   3-34   I            3-8     MERGE Command .................................   3-47   @            3-9     MERGE Command with /FULL, /LOG, and /TERMINALI                    Qualifiers.....................................   3-48   @            3-10    MERGE Command with /FULL, /TERMINAL, /CHECKS,I                    and CRC Qualifiers.............................   3-52   <            3-11    MERGE Command with Journaling on All SaveI                    Sets...........................................   3-56   I            3-12    VALIDATE Command ..............................   3-63   I            3-13    VALIDATE with /Full Qualifier .................   3-63   I            3-14    VALIDATE All Save Sets in Directory ...........   3-65   I            3-15    VALIDATE with Journal Qualifier ...............   3-67   I            3-16    VALIDATE with Terminal Classes Enabled ........   3-68   I            4-1     Ctrl/T Report Example .........................    4-1   I            4-2     Normal Successful Completion Report ...........    4-3   I            4-3     Save Set Condition Report .....................    4-5   I            4-4     Error Report ..................................    4-7   I            4-5     Log File ......................................    4-9   I                                                                         v                             Tables  5            1-1     OpenVMS File Structure Options - A I                    Comparison.....................................    1-7   <            2-1     Process Account Quotas for the InstallingI                    Account........................................    2-2   I            3-1     SSMgr Commands and Qualifiers .................   3-14                                                                         
         vi                             I         _________________________________________________________________   I                                                                   Preface         H               The Save Set Manager User and Installation Guide describesG               the procedures for configuring, installing, and operating 4               the Save Set Manager (SSMgr) software.           Intended Audience   A               This manual is intended primarily for use by system 9               managers, operators, and workstation users.            Structure   2               This manual is organized as follows:  ;               Chapter 1   Provides an overview of the SSMgr   ;               Chapter 2   Explains how to install the SSMgr   I               Chapter 3   Describes the command language interface of the                            SSMgr   1               Chapter 4   Describes SSMgr reports   I               Chapter 5   Lists the error messages generated by the SSMgr            Related Documents   >               The following table lists documents that contain2               information related to this product:  I               ___________________________________________________________ I               Document_Title____________________________Order_Number_____   C               The Save Set Manager for OpenVMS User     AA-QDKQx-TE $               and Installation Guide  I                                                                       vii                  I               ___________________________________________________________ I               Document_Title____________________________Order_Number_____   C               OpenVMS System Management Utilities       AA-PV5Px-TK #               Reference Manual: A-L   C               OpenVMS License Management Utility        AA-PVXUx-TK I               Manual_____________________________________________________   !         Documentation Conventions   @               The following conventions are used in this manual:  G               boldface    Boldface type indicates the first instance of G               type        terms being defined in text, in the glossary, "                           or both.  E               italic      Italic type indicates emphasis and complete H               type        manual titles. In the glossary, italic type isA                           also used to indicate cross-references.                                                              viii                         I                                                                         1 I         _________________________________________________________________   I                                                              Introduction     ?               The Save Set Manager for OpenVMS[TM] (SSMgr) is a D               layered software product that reduces the time used toF               create OpenVMS BACKUP save sets, while providing greater1               flexibility in save set management.   E               OpenVMS BACKUP users have had a rich set of options and E               a high level of data integrity available at the cost of <               greater down time during the backup operation.  D               SSMgr runs as a post-processor on save sets created byH               BACKUP, or other storage management software that conformsH               to the BACKUP save set structure. It allows some functionsA               that are currently done online with BACKUP, such as I               checking the integrity of save sets, making multiple copies I               of a save set, and XOR or cyclic redundancy checking (CRC), D               to be done offline using SSMgr. SSMgr does not replaceA               OpenVMS BACKUP for creating or restoring save sets.   I               SSMgr is supported for OpenVMS VAX[TM] Versions 5.5-2, 6.2, E               7.1 & 7.2 and for OpenVMS Alpha[TM] Versions 6.2, 7.1 & G               7.2. SSMgr supports a DCL interface and all disk and tape 8               technologies supported by OpenVMS systems.           1.1 Advantages of SSMgr   I               Using SSMgr to manage your save sets provides the following                benefits:   E               o  You can run OpenVMS BACKUP with fewer time-consuming E                  data integrity options, such as /VERIFY, to complete H                  the operation with minimal down time. Once you have theI                  backup save set, you perform the validation and addition @                  of data integrity features offline using SSMgr.  I               o  You can reduce the number of full backups in your backup H                  cycle by substituting incremental backups and using the5                  save set merge feature of the SSMgr.   I                                                          Introduction 1-1S M  g               Introduction         1.1 Advantages of SSMgrs    E               o  Restore time is greatly reduced, because you can use H                  SSMgr to merge incremental backups into image save setsH                  to maintain a current image save set at all times. ThisF                  process replaces the practice of using OpenVMS BACKUPH                  to restore an image save set plus many incremental save                  sets.  I               o  SSMgr does not require access to any data outside of its H                  input save sets to run, so it can be run on any OpenVMSF                  system that can directly access those save sets or to)                  which they can be moved.   F               o  You can transfer save sets between tape technologies.  G               o  The data integrity of SSMgr save sets is comparable to_E                  save sets created with other OpenVMS utilities usingo$                  full data checking.  F               o  You gain additional flexibility in managing your saveC                  set files by using the SSMgr commands for save setr7                  validation, copy, and merge functions.e  G               o  You can monitor the integrity of archived save sets to F                  determine how badly the media has degraded over time,E                  and you can use SSMgr to reconstruct and restore theo*                  save sets to fresh media.  G               o  You can create OpenVMS BACKUP Journal Files (.BJL) forr.                  previously created save sets.  ?               o  You can create up to five copies of a save seto                   simultaneously.  F               SSMgr performs its operations on save sets that strictlyG               conform to the OpenVMS BACKUP save set format for disk or H               tape devices. You can use save sets and journal files thatD               have been created by SSMgr as input to OpenVMS BACKUP.           1.2 SSMgr Functions   5               SSMgr performs the following functions:,  D               o  VALIDATE-Validates that all data blocks in the saveG                  set can be read without error. Validation includes the E                  verification that any CRC or XOR protection recorded E                  in the save set is consistent with the data they areeG                  protecting. This command may eliminate your need for a :                  /VERIFY pass when you run OpenVMS BACKUP.           1-2 Introduction B  n      I                                                              IntroductiondI                                                       1.2 SSMgr Functionso    I                  Tapes degrade over time, and the VALIDATE command allowsoE                  you to monitor the degradation of your archived savegD                  sets so that you can detect that degradation early,H                  thus minimizing data loss. If the save sets contain XORI                  redundancy protection and degradation is detected early,G8                  you may avoid any consequent data loss.  G               o  COPY-Used to make a copy of a save set, to reconstruct H                  data that has been found to be degenerated by VALIDATE,?                  or to transfer a save set to a different media C                  technology. You also can change the format of save F                  sets, such as block or group size, and you can insertB                  or remove XOR and CRC protection in the save set.  G                  Using OpenVMS BACKUP, if you wished to create multipletG                  copies of a save set, such as a local copy and a vaulttF                  copy, you had to perform your online backup operationD                  multiple times. With SSMgr, you need to perform theD                  OpenVMS BACKUP operation only once, after which youF                  can produce up to 5 copies offline with a single COPY                  operation.n  @               o  MERGE-Allows for a more flexible backup policy,H                  including merging incremental save sets into image saveG                  sets to create a fully restorable save set, or merging.I                  incremental save sets into each other. The MERGE commandtF                  can be used to reduce the frequency of image save setG                  operations (also called full backup) done with OpenVMSc                  BACKUP.  I               Both COPY and MERGE commands include the option to validate F               their input save sets while performing their operations.  8         1.3 How SSMgr Changes Save Set Management Policy  I               A common BACKUP policy is to perform an image backup once a-G               week and incremental backups all other days. In the worst0E               case scenario, a disk could be lost on the seventh day,0F               after the last incremental backup had been performed andD               before the next image backup. To restore the disk, theD               image save set must first be restored and then the sixH               incremental save sets applied in sequence. The time neededI               to restore the data is longer if the period of time betweent&               image backups is longer.  I                                                          Introduction 1-32 4  M               Introduction8         1.3 How SSMgr Changes Save Set Management Policy                   Backup Strategies4  D               SSMgr allows you to select alternative policies as theG               best backup strategy for your installation. The following H               two different policies using the SSMgr MERGE command couldF               dramatically reduce the time needed to restore the disk:  H               o  Perform an image backup on day one. Each following day,H                  perform an incremental backup and merge the incrementalE                  save set for the day with the image backup save set, G                  creating a new image save set. Repeat this process forpD                  each subsequent day, merging that day's incrementalI                  save set with the image save set created by the previouspE                  day's merge operation until you wish to perform your #                  next image backup..  D                  This strategy results in a single large save set to3                  restore in the event of data loss.S  F               o  Perform an image backup on day one and an incremental?                  backup on day two. Perform another incremental @                  backup on day three and merge its save set withC                  the incremental save set from day two to produce a A                  cumulative incremental save set. Repeat for each-D                  subsequent day, merging that day's incremental saveE                  set with the cumulative incremental save set created H                  by the previous day's merge operation until you wish to0                  perform your next image backup.  D                  This strategy results in one image save set and oneE                  incremental save set to restore in the event of datau                  loss.  D               Merging an incremental save set with an image save setA               requires two SSMgr passes over the incremental save.C               set and one pass over the image save set. Merging two.D               incremental save sets requires one pass over each saveE               set. Therefore, depending upon the relative size of theoH               image and incremental save sets, you may prefer to use the7               second strategy instead of the first one..                   1-4 Introduction 4  1      I                                                              IntroductioncI                          1.3 How SSMgr Changes Save Set Management Policy.    4               Controlling Image Backup Save Set Size  E               Image save sets created by SSMgr merge operations of an4F               image save set and one or more incremental save sets canH               grow to be larger than the backed-up disk's capacity. NoteG               that this same condition occurs when using OpenVMS BACKUP.I               to restore an image save set and all subsequent incrementals               save sets.  I               The increase in size in both cases is due to directories or I               files on the volume that were deleted or renamed subsequent F               to the original image backup. Both BACKUP and SSMgr takeB               a conservative approach to the files that used to beI               contained in those deleted or renamed directories and their.E               subdirectories; BACKUP does not delete these files when H               restoring an incremental save set that shows the directoryI               deleted, and SSMgr retains these files when merging in such.&               an incremental save set.  D               Therefore, SSMgr MERGE operations do not eliminate theI               need for periodic image backups, but by using MERGE you can D               generally increase the interval between image backups.  F               Other Ways to Reduce the Time Spent on BACKUP Operations  B               Time spent on online OpenVMS BACKUP operations couldC               be further reduced by omitting the calculation of CRC6F               protection in BACKUP, and adding in such protection in aF               COPY or MERGE operation in SSMgr. CRC protection and XORH               redundancy were originally put into BACKUP as a protectiveF               mechanism against the relatively poor quality tapes (andG               tape drives) of previous storage technologies; their main D               use on modern tape systems is to protect against long-B               term degradation of tape media. CRC calculations areC               compute intensive and can reduce BACKUP throughput on H               less powerful VAX systems. XOR redundancy blocks can limitG               BACKUP throughput on slower tape technologies such as QIC                or RDAT.  F               Omitting these protections in BACKUP save set operationsH               results in greater throughput during the backup operation.H               These protections can then be inserted during a subsequentD               SSMgr COPY or MERGE operation. In the event that SSMgrG               detects an error on a recently produced save set, you can '               run OpenVMS BACKUP again..  I                                                          Introduction 1-5  o  .               Introduction!         1.4 OpenVMS Compatibilityo    !         1.4 OpenVMS Compatibility   F               The following general comments apply to using SSMgr with               OpenVMS systems.  9         1.4.1 ODS and Extended File Specification Support   H               SSMgr V1.4 supports all operations on ODS-5 disks on AlphaE               Systems running OpenVMS V7.2. This includes support forn               EFS.  H               The following information is useful in understanding how aH               disk may be configured to enhance data access for improved               performance.           1.4.1.1 Disk Concepts   A               Disk structures may be defined as either logical or I               physical and the two types interact with each other to some H               degree. That is, you cannot manipulate a logical structureH               without considering the effect on a corresponding physical               structure.  A               Note that RMS disk files reside on Files-11 On-DisknD               Structure (ODS) disks. Files-11 is the name applied toD               the disk structures supported by the operating system.  C               Files-11 disk structures are further characterized asmB               being either on-disk structures or CD-ROM volume andG               file structures. The Files-11 structure is a hierarchical D               organization of files, their data, and the directories,               needed to gain access to them.  E               The OpenVMS file system implements the Files-11 on-diskpG               structure and provides random access to the files located E               on the disk or CD-ROM. Users can read from and write to 5               disks; they can only read from CD-ROMs.n  D               On-disk structures include Levels 1, 2, and 5. (LevelsC               3 and 4 are internal names for ISO and High Sierra CDoF               formats.) ODS-1 and ODS-2 structures have been available/               on OpenVMS systems for some time.o  G               Beginning with OpenVMS Version 7.2-EFT2 on Alpha systems, 9               you can also specify ODS-5 to format disks.   I               Table 1-1 compares the specific characteristics of Files-11 9               On-Disk Structure (ODS) Levels 1, 2, and 5.            1-6 Introduction _  _      I                                                              Introduction_I                                                 1.4 OpenVMS Compatibilityt        I               Table_1-1_OpenVMS_File_Structure_Options_-_A_Comparison____M  #                           ODS-1(VAXPI               Characteristonly)_________ODS-2_________ODS-5_______________  @               File names  9.3           39.39         238 bytes,H                                                       including the dot.G                                                       For Unicode, that G                                                       is 119 characters H                                                       including the dot.  B               Character   Uppercase     Uppercase     ISO Latin-1,=               set         alphanumeric  alphanumeric  Unicode 3                                         plus hyphen 3                                         (-), dollar ,                                         sign0                                         ($), and2                                         underscore+                                         (_)   C               File        32,767        32,767        32,767 limit;tD               versions    limit;        limit;        version limitsD                           version       version       are supported.2                           limits        limits are1                           are not       supported #                           supported   E               Directories No            Alpha:        Alpha: 255 VAX:aD                           hierarchies   255[2] VAX:   8 (with rootedB                           of            8 (with       logical, 16).                           directories   rooted0                           and subdi-    logical,+                           rectories;    16)t#                           directory %                           entries areK%                           not orderede                           [1]   I               [1]RSX-11M,_RSX-11D,_RSX-11M-PLUS,_and_IAS_systems_do_not__h  H               support subdirectories and alphabetical directory entries.D               [2]Prior to OpenVMS Version 7.2, RMS limited directory                levels to 8 or 16.  I                                                  (continued on next page)n  I                                                          Introduction 1-7t                    Introduction!         1.4 OpenVMS Compatibilityp    B               Table 1-1 (Cont.) OpenVMS File Structure Options - AI               __________________Comparison_______________________________   #                           ODS-1(VAXYI               Characteristonly)_________ODS-2_________ODS-5______________   B               OpenVMS     Local access  Files can     Files can beE               Cluster     only; files   be shared     shared across abG               Access      cannot be     across a      cluster. However, D                           shared        cluster       only computersE                           across a                    running OpenVMS F                           cluster                     Version 7.2-EFT1H                                                       or later can mountF                                                       ODS-5 disks. VAXG                                                       computers runningeI                                                       Version 7.2-EFT1 oreH                                                       later can see onlyF                                                       files with ODS-2B                                                       style names.  G               Disk        Unprotected   Protected     Protected objects /                           objects       objectst  ?               Disk        Not           Supported     Supported,#               quotas      supported   ?               Multivolume Not           Supported     Supported #               files and   supportedv               volume               sets  ?               Placement   Not           Supported     Supportedn#               control     supportedb  E               Caches      No caching    Caching of    Caching of filesD                           of file       file header   header blocks,I                           header        blocks, file  file identificationbF                           blocks, file  identifica-   slots, or extent=                           identifica-   tion slots,   entriest1                           tion slots,   or extent /                           or extent     entriesv!                           entriesc  ?               Clustered   Not           Supported     Supported #               Allocation  supported   I                                                  (continued on next page)p           1-8 Introduction           I                                                              IntroductionmI                                                 1.4 OpenVMS Compatibilitya    B               Table 1-1 (Cont.) OpenVMS File Structure Options - AI               __________________Comparison_______________________________   #                           ODS-1(VAXaI               Characteristonly)_________ODS-2_________ODS-5______________   ?               Backup      Not           Supported     Supported #               Home Block  supportedt  F               Protection  E means       E means       E means "execute=               code E      "extend" for  "execute      access"C/                           the RSX-11M   access" #                           operatinga$                           system but$                           is ignored#                           by systemp                            but is!                           ignored $                           by OpenVMS  I               Enhanced    Not           Enhanced      Enhanced protection H               protection  supported     protection    features supported0               features                  features1               (for                      supportedu               example,               access               controle               lists)  ?               RMS         Not           Supported     SupportedRI               journaling__supported______________________________________G  H               For details please read Chapter 1 Introduction of Guide to(               OpenVMS File Applications.  $         1.4.2 OpenVMS BACKUP Utility  G               Save sets created by any version of OpenVMS BACKUP, up totG               and including V7.0, are accepted by SSMgr. Also, all saveuG               sets created by SSMgr are valid inputs to all versions ofkE               OpenVMS BACKUP. All save sets created by any version ofCG               SSMgr are accepted by SSMgr, but not all SSMgr operationsiF               are valid for all types of save sets. For example, whileD               SSMgr can copy physical save sets, it cannot merge two!               physical save sets.n  I                                                          Introduction 1-9                     Introduction!         1.4 OpenVMS Compatibility     D               Unlike OpenVMS BACKUP, output tapes used by SSMgr mustE               be initialized before use and all tapes must be mounted -               without the /FOREIGN qualifier.i            1.4.3 VMScluster Support  H               SSMgr runs as a single image on a single node and does not:               include any explicit VMScluster[TM] support.  1         1.4.4 OpenVMS License Management Facilitye  I               SSMgr uses the OpenVMS License Management Facility (LMF) todD               determine if a node is authorized to use the software.           1.4.5 Privileges  G               SSMgr requires no privileges other than TMPMBX and NETMBX 0               in order to perform its functions.  .         1.4.6 Internationalization of Messages  F               The OpenVMS MESSAGE utility is used by the SSMgr CommandG               Language Interface (CLI) to allow internationalization of (               error and status messages.  "         1.4.7 OpenVMS HELP Utility  D               An OpenVMS HELP utility file that describes the CLI isG               provided on the SSMgr distribution media and is installed G               with the software. Use the HELP SAVESET command to accessn/               this feature from the DCL prompt.                                      1-10 Introductiont p  o                    I                                                                         2 I         _________________________________________________________________n  I                                                    Installation Procedure     9         2.1 Preinstallation Requirements and Preparationsa  @               This section discusses the system requirements andG               preparations necessary for installing the SSMgr software.i  @               The SSMgr kit includes online and hardcopy releaseB               notes. Digital strongly recommends that you read theD               release notes before proceeding with the installation.?               The release notes for printing to hardcopy are in @               a file named SYS$HELP:SAVESET014_RELEASE_NOTES.PS.:               The online release notes are in a file named0               SYS$HELP:SAVESET014.RELEASE_NOTES.  G               SSMgr requires that your system to be running OpenVMS VAXrH               Versions 5.5-2, 6.2, 7.1 and 7.2 or OpenVMX Alpha 6.2, 7.1G               and 7.2. Installation may only be completed on a per-node                basis.            2.2 License Registration  F               Before you install and run SSMgr on a new node, you mustI               first register a License Product Authorization Key (Licenseu?               PAK) using the License Management Facility (LMF).u  D               For complete information on using LMF, see the OpenVMS0               License Management Utility Manual.  '         2.2.1 Privileges and Disk Spacee  G               To install the SSMgr software, you must be logged into annB               account that has either of the following privileges:                 o  SETPRV   *               o  CMKRNL, WORLD, and SYSPRV  I                                                Installation Procedure 2-1     i               Installation Procedure          2.2 License Registration    E               SSMgr requires 3500 free disk blocks on the system disk H               to install. To determine the number of free disk blocks onF               your system disk, enter the following command at the DCL               prompt:o  )               $ SHOW DEVICE SYS$SYSDEVICE   $         2.2.2 Process Account Quotas  G               The account you use to install SSMgr must have sufficienttI               quotas to enable you to perform the installation. Table 2-1eI               summarizes the process quotas required for the installation E               account. Unless you are installing SSMgr in your system I               account, these process quotas are in addition to the normal I               process quotas and are necessary to ensure the proper levelo+               of resources for your system.   I               Table_2-1_Process_Account_Quotas_for_the_Installing_Accountm  I               Process_Account__Quota_____________________________________   !               ASTLM            10a  !               BIOLM            10   #               BYTLM            4000S  !               DIOLM            10   !               ENQLM            20r  "               FILLM            300                  PRCLM            2  !               TQLM             10   I               PGFLQUOTA________10000_____________________________________   !         2.2.3 User Account Quotasa  H               User account quotas are stored in the SYSUAF.DAT file. UseE               the OpenVMS AUTHORIZE utility to verify and change usereH               account quotas. First set your directory to SYS$SYSTEM andD               then run AUTHORIZE, as shown in the following example:  &               $ SET DEFAULT SYS$SYSTEM               $ RUN AUTHORIZEt               UAF>  "         2-2 Installation Procedure l  v      I                                                    Installation Procedure I                                                  2.2 License Registration     H               At the UAF> prompt, enter the SHOW command with an account>               name to check a particular account. For example:                 UAF> SHOW SMITHi  H               To change a quota, enter the MODIFY command. The followingG               example changes the FILLM quota for the SMITH account andi*               then exits from the utility:  )               UAF> MODIFY SMITH /FILLM=50n               UAF> EXITe  D               Any account from which SSMgr is to be run must have atE               least the TMPMBX and NETMBX privileges. Use the OpenVMS G               AUTHORIZE utility to determine whether users who will run 5               SSMgr have the privileges they require.   C               After you exit from the AUTHORIZE utility, the system F               displays messages indicating whether or not changes wereI               made. Once the changes have been made, you must log out and =               log in again for the new quotas to take effect.   G               For more information on modifying account quotas, see theKH               description of the AUTHORIZE utility in the OpenVMS System9               Management Utilities Reference Manual: A-L.   $         2.2.4 VMSINSTAL Requirements  G               When invoked, VMSINSTAL first verifies that the following /               actions have already taken place:e  B               o  You have set your default device and directory to                  SYS$UPDATE.  :               o  You are logged into a privileged account.  ;               o  You have adequate quotas for installation.p  0               o  DECnet[TM] software is running.  F               o  You have determined if any users are logged in to the                  system.  H               If VMSINSTAL detects any problems during the installation,E               it notifies you and prompts you to continue or stop thenC               installation. In some instances, you can enter YES to E               continue. Enter NO if you need to stop the installation $               and correct a problem.  I                                                Installation Procedure 2-3k n  t               Installation Procedure          2.2 License Registration    )         2.2.5 Backing Up Your System Diskr  G               At the beginning of the installation procedure, VMSINSTALiG               prompts you about the backup of your system disk. DigitaloA               recommends that you back up your system disk before &               installing any software.  D               Use the backup procedures that are established at yourG               site. For details on performing a system disk backup, seegE               the section on the BACKUP utility in the OpenVMS Systemr8               Management Utilities Reference Manual: A-L  )         2.3 Installing the SSMgr Softwareu  E               This section contains a step-by-step description of then%               installation procedure.i  (         2.3.1 The Installation Procedure  F               The SSMgr installation procedure consists of a series ofI               questions and informational messages. See Section 2.4 for ae"               sample installation.  E               To start the installation, invoke the VMSINSTAL commandyE               procedure from a privileged account, such as the SYSTEM @               account. VMSINSTAL is in the SYS$UPDATE directory.  D               To abort the installation procedure at any time, enterG               Ctrl/Y. When you enter Ctrl/Y, the installation procedureoC               deletes all files it has created up to that point ands?               exits. You can then start the installation again.   "               1. Invoke VMSINSTAL.  I                  @SYS$UPDATE:VMSINSTAL saveset-name device-name OPTIONS NS                    Where:   I                  o  saveset-name-The installation name for the component. H                     Use the installation name SAVESET014 when installing                     SSMgr.  H                  o  device-name-The name of the device on which you planH                     to mount the media. For example, MUA0: is the deviceE                     name for a tape drive. It is not necessary to use H                     the console drive for this installation. However, ifH                     you do use the console drive, you should replace anyH                     media you removed once the installation is complete.  "         2-4 Installation Procedure 9  a      I                                                    Installation Procedure.I                                         2.3 Installing the SSMgr Software     @                  o  OPTIONS N-This is an optional parameter thatC                     indicates you want to be prompted to review the F                     release notes. If you do not include the OPTIONS ND                     parameter, VMSINSTAL does not issue this prompt.  I                     You should review the release notes before proceeding I                     with the installation in case they contain additional B                     information about the installation. If you areI                     restarting the installation and have already reviewed I                     the release notes, you do not need to specify OPTIONS                      N.  I                  The following example invokes VMSINSTAL to install SSMgr E                  from tape drive MUA0: and shows the system response. H                  This example uses the OPTIONS N release note parameter.  C                  $ @SYS$UPDATE:VMSINSTAL SAVESET014 MUA0: OPTIONS N   K                        VAX/VMS Software Product Installation Procedure V7.0t  ,                  It is 17-JUN-1999 at 07:03.  @                  Enter a question mark (?) at any time for help.  D                  If you do not supply either the product name or theH                  device name, VMSINSTAL prompts you for this informationD                  later in the installation procedure. VMSINSTAL doesF                  not prompt you for any options, so be sure to includeF                  OPTIONS N on the VMSINSTAL command line to access the7                  release notes during the installation.   '               2. Confirm system backup.t  O                  * Are you satisfied with the backup of your system disk [YES]?   B                  You should always back up your system disk beforeF                  performing an installation. If you are satisfied withF                  the backup of your system disk, press the Return key.E                  Otherwise, enter NO to discontinue the installation.aH                  After you back up your system disk, you can restart the                  installation.  /               3. Select a release notes option.a  '                  Release Notes Options:   +                   1.  Display release notese)                   2.  Print release notes "                   3.  Both 1 and 2'                   4.  None of the above   I                                                Installation Procedure 2-5  r  t               Installation Procedure)         2.3 Installing the SSMgr SoftwareV    %                  * Select option [2]:   G                  If you specified OPTIONS N when you invoked VMSINSTAL, H                  you are now asked to choose one of the four options for-                  reviewing the release notes.   G                  If you select option 1, VMSINSTAL displays the release C                  notes immediately on the console terminal. You cankF                  terminate the display at any time by entering Ctrl/C.  F                  If you select option 2, VMSINSTAL prompts you for the>                  name of the print queue that you want to use:  *                  * Queue name [SYS$PRINT]:  E                  You can press the Return key to send the file to the E                  default output print device or you can enter another                   queue name.  G                  If you select option 3, VMSINSTAL displays the release C                  notes immediately on the console terminal and then F                  prompts you for a queue name for the printed version.  I                  Select option 4 if you have already reviewed the released;                  notes and are restarting the installation.i  A                  Next, VMSINSTAL displays the following question:   E                  * Do you want to continue the installation [N]?: YES m                  %VMSINSTAL-I-RELMOVED, The product's release notes have been successfully moved to SYS$HELP.o  I                  Enter YES to continue the installation. Otherwise, pressnF                  the Return key. In either case, the release notes are<                  copied to a file in the SYS$HELP directory.                 4. Purge files.   R                  * Do you want to purge files replaced by this installation [YES]?  A                  You have the option to purge files from previousr>                  versions of SSMgr that are superseded by thisF                  installation. Purging is recommended; however, if youG                  need to keep files from the previous version, enter NO -                  in response to the question.t  E               5. Choose the Installation Verification Procedure (IVP)e                  option.  K                  * Do you want to run the IVP after the installation [YES]?   =                  The IVP for SSMgr checks to be sure that the G                  installation is successful. It is recommended that you                   run the IVP.   "         2-6 Installation Procedure           I                                                    Installation ProcedureoI                                         2.3 Installing the SSMgr Softwareu    >                  After SSMgr is installed, you can run the IVPG                  independently to verify that the software is availablerD                  on your system. You might need to run the IVP afterD                  a system failure to make sure that users can accessD                  SSMgr. You can run the IVP independently by running*                  SYS$TEST:SAVESET$IVP.COM.  3               6. Answer Authorization Key Question.u  Y                  * Does this product have an authorization key registered and loaded? YES   D                  If you do not have a license registered and loaded,F                  answer NO and the installation will continue, but theC                  IVP will not run, regardless of how you answer thesE                  previous IVP question. After registering and loadingnI                  the authorization key, you can run the IVP independentlyn1                  by how you answer the questions.e  /               7. End of installation procedure.y  L                     Installation of Save Set Manager V1.4 completed at 14:52  5                     VMSINSTAL procedure done at 14:52I  G                  These lines are displayed when the entire installationo'                  procedure is complete.e  D                  You now can log out of the privileged account. NoteI                  that VMSINSTAL deletes or changes entries in the processRI                  symbol tables during the installation. Therefore, if you I                  are going to continue using the system manager's account F                  and you want to restore these symbols, you should log&                  out and log in again.           2.3.2 Error Recovery  @               If errors occur during the installation procedure,F               VMSINSTAL displays failure messages. If the installation8               fails, you will see the following message:  Y               %VMSINSTAL-E-INSFAIL, The installation of Save Set Manager V1.4 has failed.e  <               If the IVP fails, you will see these messages:  S               The Save Set Manager V1.4 Installation Verification Procedure failed.o  Q               %VMSINSTAL-E-IVPFAIL, The IVP for Save Set Manager V1.4 has failed.   D               Errors can occur during the installation if any of the)               following conditions exist:i  ;               o  The operating system version is incorrect.e  I                                                Installation Procedure 2-7  m                  Installation Procedure)         2.3 Installing the SSMgr Software     A               o  Quotas necessary for successful installation are                   insufficient.  H               o  System parameter values for successful installation are                  insufficient.  I               o  An image mismatch error is issued while running the IVP.a  ,         2.3.3 Installation on V5.5-2 Systems  H               OpenVMS images created using DEC C, such as SSMgr, requireC               the existence of compatible run time libraries on thenD               system on which they are installed. If you do not haveF               the DEC C components kit installed, or you have an olderE               DEC C components kit installed, attempting to run SSMgrd9               will result in one of the following errors:4  B               1)  %DCL-W-ACTIMAGE, error activating image DECC$SHR7                   -CLI-E-IMAGEFNF, image file not found.A                   $1$DIA0:[SYS14.SYSCOMMON.][SYSLIB]DECC$SHR.EXE;n  E               2)  %DCL-W-ACTIMAGE, error activating image CMA$TIS_SHR -                    -CLI-E-IMGNAME, image fileaE                   $3$DUA0:[SYS9.SYSCOMMON.][SYSLIB]CMA$TIS_SHR.EXE;2- L                    SYSTEM-F-SHRIDMISMAT, ident mismatch with shareable image  F               If your system is running OpenVMS Version 5.5-2, you mayF               see one of these mismatch errors. You must install AACRTE               from the SSMgr installation kit to clear this error, ore4               upgrade to a later version of OpenVMS.  G                 _______________________ Caution _______________________s  @                 Be sure that you carefully read the installationE                 information for AACRT before installing the software; ?                 you may choose to not install SSMgr until after ?                 upgrading to later version of OpenVMS software.   F                 ______________________________________________________  G               For descriptions of the error messages generated by thesemA               conditions, see the OpenVMS documentation on systemiA               messages, recovery procedures, and OpenVMS softwareoA               installation. If you are notified that any of theseVI               conditions exist, you should take the appropriate action as G               described in the message. For information on installation ,               requirements, see Section 2.1.  "         2-8 Installation Procedure t  p      I                                                    Installation ProcedurerI                                             2.4 SSMgr Sample Installationo    %         2.4 SSMgr Sample Installation   G               This section contains a sample installation of SSMgr. The C               sample shows an installation for a system that had nosE               previous version of the SSMgr software installed. AftercI               installation, a sample run of the Installation Verification '               Procedure (IVP) is shown.   B               $ @sys$update:vmsinstal saveset014 disk$user:[ELVIS]  F               OpenVMS VAX Software Product Installation Procedure V7.0  )               It is 10-JUN-1999 at 10:14.   =               Enter a question mark (?) at any time for help.G  R               %VMSINSTAL-W-NOTSYSTEM, You are not logged in to the SYSTEM account.L               %VMSINSTAL-W-ACTIVE, The following processes are still active:                  UCX$NTPD                 DECW$SERVER_0                UCX$TFTP_BG8                 DECW$MWMi                VUE$ELVIS_2                VUE$ELVIS_3                VUE$ELVIS_4                VUE$ELVIS_5                DECW$TE_0068                 ELVIS6               * Do you want to continue anyway [NO]? yN               * Are you satisfied with the backup of your system disk [YES]? y  7               The following products will be processed:                    SAVESET V1.4  =               Beginning installation of SAVESET V1.4 at 10:15   D               %VMSINSTAL-I-RESTORE, Restoring product save set A ...Y               %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.e  N                Copyright Digital Equipment Corporation 1994, 1995.  All rights               reserved.   O               %SAVESET-I-VMSOK, Installing SAVESET V1.4 on OpenVMS Version V7.0 Q               * Do you want to purge files replaced by this installation [YES]? yiJ               * Do you want to run the IVP after the installation [YES]? y  I                                                Installation Procedure 2-9e w  w               Installation Procedure%         2.4 SSMgr Sample Installation     4                       Product:      SAVE-SET-MANAGER'                       Producer:     DECi'                       Version:      1.3 /                       Release Date: 14-JUN-1999s  T               * Does this product have an authorization key registered and loaded? yD               %VMSINSTAL-I-RESTORE, Restoring product save set B ...  :                The Save Set Manager for OpenVMS User Guide@                has been moved to SYS$HELP:SAVESET_USER_GUIDE.PS.  \               %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...  8               This is the SAVESET IVP command procedure.  )               $ saveset validate blue.bck ,               ERRORS terminal option enabled,               EVENTS terminal option enabled[               Primary input save set ELVIS$DKB300:[SYS0.SYSUPD.SAVESET014]BLUE.BCK;1 openedaD                 Save Set Manager V1.4  Time: 10-JUN-1999 10:16:50.03  ,                   SAVESET function: VALIDATEY                   Primary input save set: ELVIS$DKB300:[SYS0.SYSUPD.SAVESET014]BLUE.BCK;1 #                     No journal file 0                   Final status of each save set:S                     Save set name:  ELVIS$DKB300:[SYS0.SYSUPD.SAVESET014]BLUE.BCK;1 !                No errors detectede  +               $ saveset validate yellow.bck ,               ERRORS terminal option enabled,               EVENTS terminal option enabled]               Primary input save set ELVIS$DKB300:[SYS0.SYSUPD.SAVESET014]YELLOW.BCK;1 opened C                 Save Set Manager V1.4 Time: 10-JUN-1999 10:16:51.80g  ,                   SAVESET function: VALIDATE[                   Primary input save set: ELVIS$DKB300:[SYS0.SYSUPD.SAVESET014]YELLOW.BCK;1s#                     No journal filef0                   Final status of each save set:U                     Save set name:  ELVIS$DKB300:[SYS0.SYSUPD.SAVESET014]YELLOW.BCK;1 !                No errors detectedd  -               $ saveset copy blue.bck red.bcke,               ERRORS terminal option enabled,               EVENTS terminal option enabled[               Primary input save set ELVIS$DKB300:[SYS0.SYSUPD.SAVESET014]BLUE.BCK;1 openedtR               Output save set ELVIS$DKB300:[SYS0.SYSUPD.SAVESET014]RED.BCK; openedA               Save Set Manager V1.4 Time: 10-JUN-1999 10:16:53.88i  #         2-10 Installation Procedure            I                                                    Installation ProcedureaI                                             2.4 SSMgr Sample InstallationM    (                   SAVESET function: COPYY                   Primary input save set: ELVIS$DKB300:[SYS0.SYSUPD.SAVESET014]BLUE.BCK;1U#                     No journal fileaP                   Output save set: ELVIS$DKB300:[SYS0.SYSUPD.SAVESET014]RED.BCK;#                     No journal filed0                   Final status of each save set:S                     Save set name:  ELVIS$DKB300:[SYS0.SYSUPD.SAVESET014]BLUE.BCK;1a!                No errors detectedIQ                     Save set name:  ELVIS$DKB300:[SYS0.SYSUPD.SAVESET014]RED.BCK;S!                No errors detected   ;               $ saveset merge blue.bck yellow.bck green.bcko,               ERRORS terminal option enabled,               EVENTS terminal option enabled[               Primary input save set ELVIS$DKB300:[SYS0.SYSUPD.SAVESET014]BLUE.BCK;1 opened X               Secondary input save set ELVIS$DKB300:[SYS0.SYSUPD.SAVESET014]YELLOW.BCK;1               openedT               Output save set ELVIS$DKB300:[SYS0.SYSUPD.SAVESET014]GREEN.BCK; openedA               Save Set Manager V1.4 Time: 10-JUN-1999 10:16:56.18i  )                   SAVESET function: MERGE Y                   Primary input save set: ELVIS$DKB300:[SYS0.SYSUPD.SAVESET014]BLUE.BCK;1e#                     No journal file \                   Secondary input save set:ELVIS$DKB300:[SYS0.SYSUPD.SAVESET014]YELLOW.BCK;1#                     No journal file S                   Output save set: ELVBIS$DKB300:[SYS0.SYSUPD.SAVESET014]GREEN.BCK; #                     No journal fileo0                   Final status of each save set:S                     Save set name:  ELVIS$DKB300:[SYS0.SYSUPD.SAVESET014]BLUE.BCK;1 !                No errors detected U                     Save set name:  ELVIS$DKB300:[SYS0.SYSUPD.SAVESET014]YELLOW.BCK;1t!                No errors detectednS                     Save set name:  ELVIS$DKB300:[SYS0.SYSUPD.SAVESET014]GREEN.BCK; !                No errors detecteda  K               The SAVESET IVP command procedure has successfully completed.d>                Installation of SAVESET V1.4 completed at 10:16  0                VMSINSTAL procedure done at 10:17            I                                               Installation Procedure 2-11                     Installation Procedure&         2.5 Reporting Product Problems    &         2.5 Reporting Product Problems  C               If you encounter a problem while using this software,tE               report it to Digital Customer Services in the U.S.A. 1-.F               800-354-9000. In other countries, report it through your%               usual support channels.i                                                                              #         2-12 Installation Procedure     t                    I                                                                         3nI         _________________________________________________________________n  I                                                               Using SSMgr     E               This chapter describes how to use SSMgr, from preparings@               save sets to using the command language interface.  0         3.1 Input and Output Save Set Specifiers  C               SSMgr operates on save sets. Each SSMgr command takes D               at least one input save set as a parameter. Some SSMgrI               commands create output save sets. Input save sets may be onnI               disk or tape, and SSMgr can create output save sets on diskeG               or tape. OpenVMS BACKUP defines several modes under whicheI               save sets may be created. Three of those save set types are 1               fully supported by SSMgr. They are:r  H               o  Image save set-This also is called a full backup. It isF                  a functionally equivalent copy of an entire volume or                  volume set.  G               o  Incremental save set-This save set contains files thatrH                  were created or modified since the last save operation.  H               o  Selective-This also is called a file-oriented save set.F                  It is a collection of files saved for some particular                  reason.  I               Physical save sets (copies of entire volumes) are supportedsD               by SSMgr for VALIDATE and COPY operations, but not for               MERGE operations.e           3.1.1 Input Save SetsC  F               Input save sets may have been created by OpenVMS BACKUP,C               by SSMgr, or by some other entity that creates valid,:F               OpenVMS save sets. For SSMgr to operate on an input saveD               set, the device on which that save set resides must beG               mounted Files-11 (that is, not mounted /FOREIGN), must beeG               accessible by the process performing the SSMgr operation, 2               and must not require network access.  I                                                           Using SSMgr 3-1     n               Using SSMgr 0         3.1 Input and Output Save Set Specifiers    E               A save set is contained in a file whose contents have a E               well-defined structure. A save set file may reside on a G               disk, a bound volume set, a single tape, or a multivolume F               tape set. SSMgr does not validate, copy, or merge disks,G               tapes, or files. The units of operation are save sets. IntF               order for SSMgr to operate on these save sets, the filesC               containing them must be accessible in the appropriateaH               manner. The following sections describe how to ensure thatG               SSMgr can appropriately access input and output save setsY;               that are contained in files on various media.r  '         3.1.1.1 Input Save Sets on DiskS  B               SSMgr can read save sets on any disk that is locallyI               connected and mounted Files-11. The process wishing to readmF               those files must be suitably privileged for read access.I               The disk may be a single disk volume or a bound volume set.   H               Standard OpenVMS defaults apply in specifying the pathnameG               of the file containing the save set. That is, the defaultrA               directory specification is assumed unless otherwiseeA               specified. If more than one input save set is being C               specified (such as the primary input save set and the F               secondary input save set in a MERGE operation), the saveE               sets may be on the same or different devices, or in the ,               same or different directories.  C               For the use of wildcards in specifying pathnames, seei               Section 3.2   '         3.1.1.2 Input Save Sets on Tapee  D               Input save sets may be located on magnetic tape. SSMgrF               can read save sets on any tape that is locally connectedH               and mounted Files-11. SSMgr will always open any tape fileH               containing a save set read only. It does not matter if theG               tape is write-locked or not. In mounting a tape Files-11,IC               the tape label must be specified, or the /OVERRIDE=IDa3               qualifier used on the $MOUNT command.   I               Tape are sequential devices. SSMgr will begin searching for G               specified file at the current position on the tape unless H               the /REWIND qualifier is specified on the $SAVESET commandG               line. If /REWIND is specified, SSMgr will first rewind tot9               BOT and then search for the specified file.            3-2 Using SSMgre    1      I                                                               Using SSMgr I                                  3.1 Input and Output Save Set Specifiersp    G               If there is more than one input save set on tape (such asgI               the primary input save set and the secondary input save setsG               in a MERGE operation), each must be on a different volume 4               and mounted in a different tape drive.  8         3.1.1.3 Input Save Sets on Multivolume Tape Sets  >               A file containing a save set may span tapes in aF               multivolume tape set. If that is so, the tapes must haveF               been mounted in a manner that allows continuation to theG               next tape in the set. There are several factors that needl               to be considered.s  H               Tape switching of Files-11-mounted tapes is handled by theG               OpenVMS magnetic tape ancillary control process (MTAACP),eG               which is part of the OpenVMS operating system, not SSMgr.fH               The MTAACP performs a number of checks on the continuationI               volume that is loaded into the tape drive, be it by a humanrH               or by a mechanical loader. Two checks that are significantG               for input save sets that span tapes are the label (volume C               identifier) check and the set id (fileset identifier)-               check.  F               Multivolume tape sets that are created by OpenVMS BACKUPC               or by other OpenVMS utilities follow a canonical tape D               labeling scheme if the creator of the multivolume tapeH               set does not explicitly specify the tape labels to be used%               for continuation tapes.i  C               Labels generated for continuation tapes fill the six-2C               character volume identification field. The first four G               characters of the field contain the first four charactersiH               of the previous volume in the volume set. (If the label isG               less than four characters, the volume identifier field isoF               padded with underscores.) The fifth and sixth charactersA               contain the relative volume number for that reel or D               cartridge in the volume set. For example, if the firstG               tape has a label of ABCDEF, the second and third would be F               labeled ABCD02 and ABCD03. If the first tape has a labelE               of AB, the second and third would be labeled AB__02 and-               AB__03.l  F               If SSMgr will be processing an input save set that spansA               tapes (whether it is an operation on a single largeeD               save set or an operation that processes many save setsC               through the use of wildcards and the /ALL qualifier),u  I                                                           Using SSMgr 3-3  o  o               Using SSMgro0         3.1 Input and Output Save Set Specifiers    C               the multivolume set must be appropriately mounted for F               continuation. If the labeling of the continuation volumeG               does not fit the labeling scheme recognized by MTAACP, it H               will not mount and make available that volume for reading.H               If the multivolume tape set follows the canonical labelingF               scheme described above, it will mount and make availableH               that volume for continued processing. If not, the tape setI               must be mounted specifying the names of each tape volume in,#               the set. For example:   =                   $ MOUNT MUA0: BEATLE,JOHN,PAUL,GEORGE,RINGO   I               The use of the /OVERRIDE=ID qualifier on the $MOUNT command H               will override the label check on the first volume only. ItH               does not carry over to continuation volumes. Therefore, ifG               the labels are like the ones in the previous example, the '               following $MOUNT command:   +                   $ MOUNT/OVERRIDE=ID MUA0:   A               would result in the volume BEATLE being mounted andnF               processed, but when the tape switch occurred, the MTAACPE               would send OPCOM messages asking for relative volume 2,rH               BEAT02, to be mounted. At this point, the operation cannotI               continue, because the MTAACP will accept nothing other thanP$               a tape labeled BEAT02.  >               A second check made by the MTAACP is the filesetF               identifier. In some instances, continuation volumes thatH               are initialized by OpenVMS BACKUP may not be recognized byG               the MTAACP as the correct next volume, even though it is.oI               In that case, an OPCOM message is issued that says that theo.               tape is not the next in the set.  F               SSMgr does its own checking to ensure that what it findsI               on the next tape is indeed the continuation of the save setVG               it had been processing. Therefore, this check made by the F               MTAACP can be safely overridden with the /OVERRIDE=SETID;               qualifier on the $MOUNT command. For example,h  M                   $ MOUNT/OVERRIDE=SETID MUA0:  BEATLE,JOHN,PAUL,GEORGE,RINGOw                 3-4 Using SSMgr     E      I                                                               Using SSMgr I                                  3.1 Input and Output Save Set Specifiers              3.1.2 Output Save Sets  I               Output save sets may be created by SSMgr on any nonnetwork-tF               accessed disk, bound volume set, or tape device. As withD               input save sets, that device must be mounted Files-11.  (         3.1.2.1 Output Save Sets on Disk  I               SSMgr can create and write to save sets on any disk that isyI               locally connected and mounted Files-11. The process wishing I               to create and write those files must be suitably privileged H               for create and write access. The disk may be a single disk+               volume or a bound volume set.N  I               Standard OpenVMS defaults apply in specifying the pathnames:I               of the files containing the save sets. That is, the default A               directory specification is assumed unless otherwiseeE               specified. See Section 3.1.4 for special considerations.?               around the creation of multiple output save sets.   C               For the use of wildcards in specifying pathnames, see                Section 3.2.  (         3.1.2.2 Output Save Sets on Tape  E               Output save sets may be created on magnetic tape. SSMgrrE               can create save sets on any tape device that is locallytB               connected and mounted Files-11. In mounting a singleE               tape Files-11, the tape label must be specified, or theTI               /OVERRIDE=ID qualifier used on the $MOUNT command. Further,-H               the tape must have been initialized ($INITIALIZE) prior to(               mounting for use by SSMgr.  A               Tapes are sequential devices. SSMgr will create thenE               specified save set file after the last file on the tape G               unless the /REWIND qualifier is specified on the $SAVESET E               command line. If /REWIND is specified, SSMgr will firstyH               rewind to BOT and then create the specified save set file,=               overwriting whatever may have been on the tape.s  E               See Section 3.1.4 for special considerations around the 4               creation of multiple output save sets.  C               For the use of wildcards in specifying pathnames, seer               Section 3.2.  I                                                           Using SSMgr 3-5f f                  Using SSMgrs0         3.1 Input and Output Save Set Specifiers    9         3.1.2.3 Output Save Sets on Multivolume Tape Sets   I               A save set created by SSMgr may span tapes in a multivolumee?               tape set. If that will be so, the tapes must haveNB               been initialized and mounted in a manner that allowsI               continuation to the next tape in the set. There are severals1               factors that need to be considered.K  H               Tape switching of Files-11-mounted tapes is handled by theG               OpenVMS magnetic tape ancillary control process (MTAACP), G               which is part of the OpenVMS operating system, not SSMgr. C               The MTAACP has certain expectations of a continuation E               tape that is loaded into the drive, be it by a human oreD               a mechanical loader. Those expectations are set by theB               parameters and qualifiers that had been specified inC               the $MOUNT command for that device. There are severalfC               different ways in which a multivolume tape set can be F               mounted Files-11 for use by SSMgr to create and write to               output save sets:I  =                   $ MOUNT MUA0: BEATLE,JOHN,PAUL,GEORGE,RINGOA  D               In this example, five tapes have been initialized withD               the tape labels BEATLE, JOHN, PAUL, GEORGE, and RINGO.E               The tape that had been initialized as BEATLE is loaded, H               and the $MOUNT command issued. When that tape is full, theH               MTAACP expects a tape that had been initialized as PAUL toG               be loaded next. If a mechanical loader is being used, andpI               the next tape in the loader has that label, operations will H               proceed. If a tape is not automatically loaded, the MTAACPE               issues an OPCOM message requesting that relative volumetH               2, JOHN, be mounted. If a tape initialized with label JOHNH               is loaded into the drive, operations will continue on thatG               tape. If, however, an uninitialized tape or a tape with a H               label other than JOHN is loaded into the drive, the MTAACPG               will reject that tape and continue sending OPCOM messages 1               requesting relative volume 2, JOHN.s  &                   $ MOUNT MUA0: BEATLE  B               In this example, only the label of the first tape isD               specified on $MOUNT command line. A tape that had beenD               initialized as BEATLE is loaded and the $MOUNT commandB               issued. When that tape is full, the MTAACP expects aE               tape that been initialized as BEAT02 to be loaded next. D               See Section 3.1.1.3 for a description of the canonicalG               continuation tape labeling algorithm for a description of7           3-6 Using SSMgr            I                                                               Using SSMgrlI                                  3.1 Input and Output Save Set Specifierse    H               what labels are expected when continuation tape labels are;               not explicitly specified on the command line.e  >                   $ MOUNT/INITIALIZE=CONTINUATION MUA0: BEATLE  B               In this example, only the label of the first tape isE               specified on the $MOUNT command line. When continuation D               tapes are loaded, either by a human or by a mechanicalB               loader, the MTAACP will change the tape label of theE               next tape that is loaded, using the algorithm described_C               above. That is, the label of the second tape would be @               reinitialized to BEAT02, the third to BEAT03, etc.  ?               In each of the examples above, the MTAACP expectsiE               continuation tapes to have been initialized. It is also B               possible to use uninitialized (unformatted) tapes asE               continuation tapes. This requires responding to MTAACP-mF               generated OPCOM messages with the /BLANK_TAPE qualifier.               For example:  J                   %%%%%%%%%%%  OPCOM, 10-MAY-1999 15:23:31.78  %%%%%%%%%%%-                   request 3, from user SNYDERo?                   MOUNT new relative volume 2 (BEAT02) on MUA0:f  B               With OPER and VOLPRO privileges, the following replyG               will result in the uninitialized tape being formatted andc7               labeled, allowing operations to continue:p  /                   $ REPLY/BLANK_TAPE=3 "BEAT02"e  B               The tape will be formatted and labeled as BEAT02 (orF               whatever you specify as the label you want), and mounted2               in the drive, allowing continuation.  G               If a continuation tape is loaded that has been formatted,fF               but the tape has a label that is not the one expected byE               the MTAACP, the following reply will result in the tape ?               being relabeled, allowing operations to continue:   +                   $ REPLY/INITIALIZE_TAPE=3n  G               The tape will be relabeled as BEAT02, and operations wille*               continue. An alternative is:  2                   $ REPLY/INITIALIZE_TAPE=3 "JOHN"  C               In this case, the tape will be relabeled as JOHN, and '               operations will continue.s  I                                                           Using SSMgr 3-7  t  e               Using SSMgrb0         3.1 Input and Output Save Set Specifiers    $         3.1.3 Files-11 Mount Example  D               Example 3-1 shows a session in which an image save setE               on tape is merged with an incremental save set on disk. D               The resulting "virtual" image save set is written to a               multivolume tape.   *               Example 3-1 A Files-11 Mount  +               $ INITIALIZE MKB200: MERGE0 1 +               $ INITIALIZE MKB200: MERGE1 2l%               $ MOUNT MKB100: IMAGE 3s8               %MOUNT-I-MOUNTED, IMAGE mounted on MKB100:-               $ MOUNT MKB200: MERGE0,MERGE1 4.9               %MOUNT-I-MOUNTED, MERGE0 mounted on MKB200:e  I               $ saveset merge mkb100:full.bck incr.bck mkb200:merge.bck 5r,               ERRORS terminal option enabled,               EVENTS terminal option enabled.               Opening file MKB100:[]FULL.BCK;1?               Primary input save set MKB100:[]FULL.BCK;1 openedrI               Secondary input save set DISK$USER:[ELVIS]INCR.BCK;1 openedS.               Opening file MKB200:[]MERGE.BCK;8               Output save set MKB200:[]MERGE.BCK; opened  B                Save Set Manager V1.4 Time: 10-JUN-1999 13:29:09.58  )                   SAVESET function: MERGEk=                   Primary input save set: MKB100:[]FULL.BCK;1 #                     No journal file G                   Secondary input save set: DISK$USER:[ELVIS]INCR.BCK;1 #                     No journal file 6                   Output save set: MKB200:[]MERGE.BCK;#                     No journal filea  0                   Final status of each save set:  7                     Save set name:  MKB100:[]FULL.BCK;1 (                       No errors detected  ?                     Save set name:  DISK$USER:[ELVIS]INCR.BCK;1e(                       No errors detected  I                                                  (continued on next page)f           3-8 Using SSMgr            I                                                               Using SSMgraI                                  3.1 Input and Output Save Set Specifiers     2               Example 3-1 (Cont.) A Files-11 Mount  7                     Save set name:  MKB200:[]MERGE.BCK;e(                       No errors detected  "               $ DISMOUNT MKB100: 6"               $ DISMOUNT MKB200: 7  I               1  The output save set will span two volumes. In this line,iE                  the first tape is initialized with the label merge0.m  E               2  The first tape is removed from mkb200 and the secondrE                  tape is loaded. This second tape is then initialized E                  with the label merge1. After initializing that tape,SF                  it is removed and the first tape is reloaded into the                  drive.   D               3  The device containing the primary input save set is"                  mounted Files-11.  I               4  The device to which the "virtual" image save set will be G                  written also is mounted Files-11 as a multivolume save                   set.a  E               5  The SAVESET MERGE operation is performed. The secondaG                  output tape is loaded either manually or with a loaderi8                  when the first output tape reaches EOT.  0               6  The input device is dismounted.  F               7  The output device is dismounted, completing the merge                  operation.e  '         3.1.4 Multiple Output Save Sets   F               SSMgr provides the ability to make up to 5 copies of anyI               output save set simultaneously. These copies may be written I               to disk or tape. Each output save set pathname is specified G               as a separate parameter on the $SAVESET command line. For                example,  V                   $ SAVESET COPY MUA0:SS.BCK *.* [-]*.* MKA100:*.* MUA1:SS_ARCHIVE.BCK  E               In this example, the save set named SS.BCK is on a tapehF               mounted on tape drive MUA0:. Four copies are being made.H               Two of the copies are being written to disk, and two otherD               are being written to tape. The copies being written toD               disk are being written to the default directory and to  I                                                           Using SSMgr 3-9v m  a               Using SSMgr 0         3.1 Input and Output Save Set Specifiers    H               the parent directory, and in each case, the name SS.BCK isI               preserved. One tape copy is being written to a tape mountedhF               on MKA100: and the file name is again the same. The lastE               copy is being written to a tape mounted on MUA1: and is (               being name SS_ARCHIVE.BCK.  G               With the /ALL qualifier, SSMgr may be processing multiplesD               input save sets. With one exception, in the event of aG               failure to open or to write to any output save set, SSMgrmG               will attempt to continue operation to as many output save E               sets as it can, from as many input save sets as it can.f  F               If there is a failure to open any one of the output saveI               sets for the second or subsequent input save sets, an errordH               will be reported and operation will continue to all outputI               save sets that could be opened. If none could be opened, an I               error will be reported and operation will continue with then*               next input save set, if any.  F               If SSMgr cannot successfully write to an output save setG               once it has been opened, that output file will be closed, I               an error reported, and operation will continue to all other E               output save sets. If SSMgr encounters a condition wherenH               it can write to none of the output save sets, it will moveH               to the next input save set, if any, and continue operation               from there.n  I               The one exception to the continue-if-possible philosophy isrG               if there is a problem opening any output save set for the G               first (or only) input save set for a given SSMgr command.wH               In that case, the command execution is terminated to allow6               the offending condition to be corrected.  H               There are several performance and resource implications to2               producing multiple output save sets:  I               o  Multiple copies can be written to the same disk, but forLG                  each tape copy desired, there must be a dedicated tapet                  drive.   C               o  A SSMgr operation to multiple output save sets can B                  proceed only as fast as the slowest output deviceF                  permits. If one device is involved in error recovery,:                  all others must wait until it's complete.           3-10 Using SSMgr           I                                                               Using SSMgr I                                  3.1 Input and Output Save Set Specifiersl    G               o  A set of I/O buffers is allocated for each output saveoG                  set, with a maximum of four 64KB buffers allocated for                   each.  G               o  XOR and CRC calculations are performed for each output G                  save set, thereby significantly increasing the computen'                  load of the operation.o  F               o  For $ SAVESET COPY/IDENTICAL operation, there will beI                  significant slowdown with multiple output save sets. ThehH                  operation is optimized for a single output save set, anG                  optimization that does not transfer to multiple output %                  save set operations.                                                                 I                                                          Using SSMgr 3-11f ,  i               Using SSMgr =         3.2 Wildcards in Save Set and Journal File SpecifiersD    =         3.2 Wildcards in Save Set and Journal File Specifiers   F               SSMgr supports standard OpenVMS wildcarding of input andF               output save set specifiers, as well as journal file nameD               specifiers. However, because of the semantics of SSMgr3               commands, there are some constraints.i  5         3.2.1 Wildcard Constraints on Input Save Sets   G               By default, if a wildcard is used in the name of an input B               save set, only the first matching file found will beC               used. This is true for VALIDATE, COPY, and MERGE. For F               VALIDATE and COPY, you can elect to operate on all filesG               that match the wildcarded save set specifier by using the G               /ALL qualifier. Because the MERGE command takes two inputrH               save set specifiers and one output save set specifier, theE               possible combinations of names of input and output save C               sets all using wildcards presents a dizzying semanticnA               matrix of resultant operations. Therefore, the /ALLh?               qualifier is not supported for the MERGE command.f  F               As it is, use of /ALL with the COPY command has semantic(               implications. For example:  2                   $ SAVESET COPY *.BCK FOO.BCK/ALL  F               If there are 10 files that match the wildcarded save setD               specifier, *.BCK, there will be 10 versions of foo.bckC               created. That is, the output save set for each of theeF               10 COPY operations will have the same name, FOO.BCK, butE               a different version number. If there is a version limitiH               placed on the directory, the first several copies could be7               deleted on creation of subsequent copies.N  6         3.2.2 Wildcard Constraints on Output Save Sets  E               Wildcarding of output save set specifiers is permitted.SE               Resolution of the actual name of the output save set ishG               based on the location of the wildcard or wildcards in the (               output save set specifier.  C               The components of a save set specifier are the deviceDA               name, the directory string, the file name, the filehF               type, and the version number. For example, the specifier1               dua1:[foo]bar.baz;3 breaks down as:            3-12 Using SSMgr d  t      I                                                               Using SSMgr I                     3.2 Wildcards in Save Set and Journal File Specifiers     #                   device:     dua1: #                   directory:  [foo] !                   file name:  bars"                   file type:  .baz                    version:    ;3  E               Only the file name and file type components may contain F               wildcards. The only legal wildcard character is * and itF               must be the only character in that component of the fileE               specification. When the component contains the wildcardaE               character, the corresponding component from the primarytC               input file specification is used. If the component isiE               missing altogether, it is treated the same as if * weret               used.   E                   $ SAVESET COPY DUA0:[FOO]BAR.BAZ;3 DUA1:[MUMBLE]*;6s  8               In this case, the output save set would beD               DUA1:[MUMBLE]BAR.BAZ;6 because the file name componentB               contains the wildcard and the file type component isD               missing. Therefore, both of those components mimic theE               corresponding component from the primary input save seta               specification.  8         3.2.3 Wildcard Constraints on Journal File Names  C               As with output save set specifiers, journal file name F               specifiers may contain wildcard characters. If the "fileF               name" component of the journal file specifier contains aD               wild card, the "file name" component of the associatedD               save set will be used. If the "file type" component ofG               the journal file specifier contains a wild card, then thea<               default journal file type (.BJL) will be used.  P                   Example 1:  SAVESET VALIDATE DUA0:[FOO]BAR.BAZ;3/JOURNAL=*.JOU  S                   In this case, the journal file would be written to BAR.JOU in the $                   default directory.  R                   Example 2: SAVESET VALIDATE DUA0:[FOO]BAR.BAZ;3/JOURNAL=FOOBAR.*  S                   In this case, the journal file would be written to BAR.JOU in theI$                   default directory.  M                   Example 3: SAVESET VALIDATE DUA0:[FOO]BAR.BAZ;3/JOURNAL=*.*   S                   In this case, the journal file would be written to BAR.JOU in thet$                   default directory.  I                                                          Using SSMgr 3-13m a                  Using SSMgrr,         3.3 SSMgr Command Language Interface    ,         3.3 SSMgr Command Language Interface  D               This section describes the valid commands for SSMgr. AF               matrix of commands and qualifiers is shown in Table 3-1.  I               Table_3-1_SSMgr_Commands_and_Qualifiers____________________   I               Command          _____________SAVESET_Command______________2  I               Qualifier________VALIDATE__COPY______MERGE_________________t  5               /ALL             Yes       Yes       Nog  6               /BLOCK_SIZE      No        Yes       Yes  6               /BRIEF           Yes       Yes       Yes  6               /CHECKS          Yes       Yes       Yes  6               /COMMENT         No        Yes       Yes  6               /CRC             No        Yes       Yes  6               /FULL            Yes       Yes       Yes  6               /GROUP_SIZE      No        Yes       Yes  5               /IDENTICAL       No        Yes       Noo  6               /JOURNAL         Yes       Yes       Yes  6               /LOG_FILE        Yes       Yes       Yes  5               /OVERRIDE        No        Yes       Noc  6               /REWIND          Yes       Yes       Yes  I               /TERMINAL________Yes_______Yes_______Yes___________________c                       3-14 Using SSMgr a         I                                                                      COPY       I         _________________________________________________________________            COPY                  Copies a save set.           Format  >               COPY  input-ss output-ss [output-ss] [output-ss]+                     [output-ss] [output-ss]q           Parameters                 input-ss5               OpenVMS file name of an input save set.                  output-ss C               OpenVMS file name(s) of the output save set(s). Up to%C               5 output save sets may be specified. Unless otherwise G               specified by command qualifiers, the output save set willEF               have the same attributes for XOR group size, block size,H               CRC, and other attributes as the input save set. Different@               qualifiers may be applied to each output save set.           Description   I               The COPY command reads an OpenVMS BACKUP save set, verifies D               that it is readable and consistent, and creates 1 to 5G               copies of that save set. Any rewritten (redundant) blocks I               in the input save set are eliminated in the COPY operation.lG               For an explanation of rewritten blocks, see Section 4.2.2wG               for Successful Completion with Save Set Condition Report.n  H               You can optionally specify software CRC and XOR protectionH               to be present, absent, or the same as the source save set.H               The default is to make the output save set the same as theG               input save set. The desired block size of the output saverH               set can also be specified as different from the input saveD               set. The COPY command regenerates any bad blocks found#               during the operation.   F                 ________________________ Note ________________________  C                 The size of the save set after a COPY operation may E                 be slightly smaller than the original save set due toeD                 the way the OpenVMS BACKUP utility formats the data.  I                                                          Using SSMgr 3-15  i  -               COPY      C                 SSMgr repacks its data records during processing toRC                 reduce the space required; there is no loss of dataID                 from the OpenVMS input save set, and the output save6                 set is compatible with OpenVMS BACKUP.  F                 ______________________________________________________                                                                                       3-16 Using SSMgr a  d      I                                                                      COPYe                   Qualifiers                 /ALL                /[NO]ALL (default)                 Command qualifier   G               This qualifier specifies the behavior of Save Set ManagerM4               when save set names contain wildcards.  B               If ALL is specified, then all save sets matching theI               wildcarded input save set file specification are processed.   B               If NOALL is specified, then only the first file nameE               found that matches the wildcarded file specification isf               processed.  C               The qualifier is valid only for the VALIDATE and COPYa               functions.  $               The default is /NOALL.                 /BLOCK_SIZE=n0  '               Output save set qualifierr  D               This qualifier specifies the desired block size of theF               output save set. Valid values for n are between 2048 andG               65024, and are rounded up to the nearest multiple of 512.sH               The block size of the input save set is used if the BLOCK_.               SIZE qualifier is not specified.  E               As required by OpenVMS BACKUP, the upper limit for save I               sets on disk is 32256. If a larger block size is specified, 0               SSMgr will round it down to 32256.  @               This qualifier may not be used with the /IDENTICAL               qualifier.  B               The default is the block size of the input save set.                 /BRIEF (default)  I                                                          Using SSMgr 3-17r v  f               COPY                     Command qualifier.  H               This qualifier specifies that a minimum level of detail isI               to be echoed. The SAVESET function and save set name(s) arefH               echoed; any error information is displayed; and the resultE               of the SAVESET operation is reported. See /FULL for the 2               complete list of output information.  $               The default is /BRIEF.                                                                                 3-18 Using SSMgr a         I                                                                      COPY       (               /CHECKS=([NO]CRC, [NO]XOR)  &               Input save set qualifier  F               This qualifier specifies the optional consistency checksG               that will be performed on the input save set; the defaultt               is CRC, XOR.  F               You must specify the /CHECKS qualifier immediately afterF               the file name of each input save set when specifying theC               input save set. Example 3-12 also shows that when you D               specify both CRC and XOR checks, you must list them in7               parentheses with a comma separating them.   D               If CRC checking is specified and the input save set isG               written with CRC, then the CRC is computed for each blocktI               in the input save set. The computed CRC is compared against 1               the CRC stored in the block header.   E               If XOR checking is specified and the input save set was I               written with XOR redundancy, then a running XOR is computed F               across each XOR group of blocks. The running XOR is then(               compared to the XOR block.  B               Each of these options requires additional processingF               time and may impact the performance of SSMgr. Any CRC orD               XOR inconsistencies are written to the log file and anI               informational message is returned to the calling program or0-               user when processing completes.t                 /COMMENT=stringt  '               Output save set qualifier   F               This qualifier inserts a comment in the output save set.D               The comment string can be up to 252 characters. If theF               comment string is longer than one word or if it containsA               non-alphanumeric characters, it must be enclosed intE               quotation marks ("). The comment from the primary inputt<               save set is not copied to the output save set.  I               The default is no comment string written to the output saves               set.    I                                                          Using SSMgr 3-19i w                  COPY                     /CRC               /NOCRC  '               Output save set qualifier   G               Specifying /CRC causes the CRC to be computed across each I               block of the output save set and stored in the block headeryE               of each block of the output save set. Specifying /NOCRCaB               causes CRC computation to be inhibited on the outputF               save set. If this qualifier is not specified, the CRC isG               computed and stored in the output save set only if it wase,               present in the input save set.  @               This qualifier may not be used with the /IDENTICAL               qualifier.  C               The default is /CRC if the primary input save set waspG               written with CRC and /NOCRC if the primary input save seto&               was written without CRC.                                                             3-20 Using SSMgr    c      I                                                                      COPYe                     /FULLr                 Command qualifieri  H               This qualifier specifies that more detail is to be echoed.B               In addition to information displayed with the /BRIEFD               qualifier, the following information for each save set               is displayed:                     Save set name$                  Save set group size$                  Save set block size-                  Number of blocks in save set 4                  Nondirectory user files in save set1                  Directory user files in save setc5                  Alias nondirectory files in save set 2                  Alias directory files in save set)                  Unrecoverable CRC errors '                  Recoverable CRC errorse,                  Recoverable checksum errors.                  Unrecoverable checksum errors                  XOR errorsm                  Read errors                  Write errors                   Record errors-                  Unrecoverable missing blocks +                  Recoverable missing blocksi!                  Rewritten blocks   $               The default is /BRIEF.                 /GROUP_SIZE=nN  '               Output save set qualifier   G               This qualifier specifies the XOR group size in the output I               save set. Valid values for n are between 0 and 100. A value <               of 0 specifies that no XOR should be computed.  G               If this qualifier is not specified, the group size of the H               input save set is used for the output save set group size.)               This is the default action.   @               This qualifier may not be used with the /IDENTICAL               qualifier.  I                                                          Using SSMgr 3-21g u  r               COPY                         /IDENTICAL                 Command qualifierw  D               This qualifier does a fast copy of the input save set.E               A fast copy operation copies the contents of each inputnF               save set block to the output save set without validationE               of the block's internal record structure. If errors are F               encountered during this operation, restart the operationG               and include the /OVERRIDE qualifier to continue operation F               even in spite of the errors. See the /OVERRIDE qualifier                description below.  H               Each save set is stored with information that reflects theG               environment in which it was created. In a normal save settG               copy, the information in the output save set reflects the H               environment in which the output save set was created. WithE               the /IDENTICAL qualifier, this information reflects thefB               environment in which the input save set was created.  G               The /IDENTICAL qualifier is not supported for multivolumeaF               output save sets, because you may not be able to restore               such a save set.  G               You may not use /GROUP_SIZE, /BLOCK_SIZE, /CRC, /COMMENT,tG               or /JOURNAL qualifiers with the /IDENTICAL qualifier. You I               may not use the /TERMINAL=LOG qualifier with the /IDENTICAL                qualifier.  *               /JOURNAL[=journal-file-name]                  Save set qualifier  B               This qualifier specifies whether SSMgr will create aC               journal file for the save set. The journal file is ansD               OpenVMS BACKUP journal file with an OpenVMS file name.I               If no journal file name is specified, the journal file willtE               be written to <saveset_name>.BJL in the current defaultt               directory.  F               If a journal file with the same name already exists, theI               new journal file is appended. If it does not already exist,r,               a new journal file is created.           3-22 Using SSMgr e  l      I                                                                      COPY       E               Journal files created by SSMgr will not list the labels E               of follow-on volumes in multivolume tape sets. Also, if D               COPY/IDENTICAL is used to copy a multivolume tape to aH               single volume tape, the journal file will still list it as%               a multivolume tape set.   I               These differences from Backup created journal files are dueeI               to a limitation in VMS that does not allow a non-privilegedaG               process to obtain the volume labels of a multivolume tape                set.  H               You must specify this qualifier immediately after the save:               set file name specifier on the command line.  @               This qualifier is valid for all save set file nameA               specifiers, input or output, on all SSMgr commands.i  D               This qualifier may not be combined with the /IDENTICAL               qualifier.  G               Journal files will be created for each save set specified B               on the command line that is followed by the /JOURNALH               qualifier. If more than one journal file is being created,4               each journal file name must be unique.  C               For example, SAVESET COPY FILES.BCK/JOURNAL FILES.SAV E               /JOURNAL is illegal, because the resulting journal file 9               names would each be, by default, FILES.BJL.a  (               The default is /NOJOURNAL.                              I                                                          Using SSMgr 3-23r e                  COPY      0               /LOG_FILE[=logfile-name] (default)               /NOLOG_FILEd                 Command qualifier   B               This qualifier causes SSMgr to write events to a logD               file specified by logfile-name. The logfile-name is anE               ASCII file with an OpenVMS file name. If not specified, E               the default log file name is SAVESET.LOG in the currentRH               default directory. You can suppress creating a default logH               file by using /NOLOG_FILE or by including /LOG_FILE=NL: onG               the command line. The following events are written to theA               SAVESET.LOG file:n  )               o  Each invocation of SSMgr   C               o  All output returned to the user or calling program   D               o  Any errors or warnings encountered while processing*                  input or output save sets  "               o  Operator requests  G               Wildcards may not be used in the specification of logfile                names.                 /OVERRIDE #               /NOOVERRIDE (default).                 Command qualifier   D               This qualifier allows you to override certain internalD               consistency checks to allow execution to continue withG               unreadable or unrecoverable blocks in the input save set._H               This qualifier allows you to make a complete and identical)               copy of a damaged save set._  G               You must use the /IDENTICAL qualifier when specifying the_F               /OVERRIDE qualifier to allow continued processing of theF               save set after encountering unrecoverable input save setE               errors. The /IDENTICAL and /OVERRIDE qualifiers must be E               specified in that order on the command line as shown in                Example 3-4.             3-24 Using SSMgr    s      I                                                                      COPY                      /REWIND !               /NOREWIND (default)E  0               Input or output save set qualifier  E               For magnetic tape volumes only, REWIND directs SSMgr to E               rewind the magnetic tape to the beginning-of-tape (BOT)YF               marker before reading or writing the volume. If /ALL wasF               specified, the rewind only happens once before the first                SAVESET operation.  C               You must specify this qualifier immediately after the C               applicable file name on the command line, as shown in_               Example 3-12._  E               The following consequences result when using the REWIND                qualifier:  H               o  If specified with an input save set, SSMgr searches forF                  the specified file starting at the BOT position. ThisF                  allows SSMgr to find files located before the current&                  position of the tape.  G               o  If specified with an output save set, SSMgr overwrites H                  the tape starting at the BOT position. All files on the.                  tape are therefore destroyed.  D               The default for this qualifier is /NOREWIND. On input,D               the tape will be searched starting at the current tapeI               position. On output, the new file will be opened at end-of-                data.O  9               /TERMINAL=([NO]ERRORS, [NO]EVENTS, [NO]LOG)                  Command qualifiers  D               This qualifier specifies what class(es) of informationI               should be displayed on the user's terminal during executionn%               of the SAVESET command.   I               If ERRORS is specified, then all error conditions occurring G               during execution are displayed as they occur, in addition I               to being included in the final report at the end of command ,               execution and in the log file.  H               If EVENTS is specified, then all nonerror event conditionsB               occurring during execution (e.g., tape switches) are&               displayed as they occur.  I                                                          Using SSMgr 3-25P o  n               COPY      D               If LOG is specified, then the names of all output userB               files (for COPY and MERGE) are displayed as they areH               written to the output save set. For VALIDATE, the names ofG               all input user files are displayed as they are processed. B               The /TERMINAL=LOG qualifier may not be used with the#               /IDENTICAL qualifier.     F                 ________________________ Note ________________________  D                 When a multivolume save set is copied using the COPYB                 /IDENTICAL command, volume switch information fromD                 the original input save set will be preserved in theA                 single volume copy, and it will be reported as an_                 EVENT.  F                 ______________________________________________________  =               The default is /TERMINAL=(ERRORS,EVENTS,NOLOG).                                                              3-26 Using SSMgr           I                                                                      COPY                  Examples    &               Example 3-2 COPY Command  R               $ saveset copy mkb200:savesetua013.B/rewind disk$user:[kits]copy.sav,               ERRORS terminal option enabled,               EVENTS terminal option enabled6               Rewinding MKB200: to beginning of volume(               Rewind of MKB200: complete2               Opening file MKB200:[]SAVESET014.B;1C               Primary input save set MKB200:[]SAVESET014.B;1 opened.>               Output save set DISK$USER:[KITS]COPY.SAV; opened  A               Save Set Manager V1.4 Time: 10-JUN-1999 13:45:05.49O  (                   SAVESET function: COPYA                   Primary input save set: MKB200:[]SAVESET014.B;1r#                     No journal filet<                   Output save set: DISK$USER:[KITS]COPY.SAV;#                     No journal filed  0                   Final status of each save set:  ;                     Save set name:  MKB200:[]SAVESET014.B;1 (                       No errors detected  =                     Save set name:  DISK$USER:[KITS]COPY.SAV;u(                       No errors detected  F                  In Example 3-2, the tape mounted on mkb200 is rewoundI                  and then the save set, SAVESET014.B, is copied from thatsI                  tape to a file called copy.sav on disk$user:[kits], withl8                  all save set characteristics preserved.  E               Example 3-3 COPY Command with Multiple Output Save Sets   I                                                  (continued on next page)n            I                                                          Using SSMgr 3-27s                    COPY      H               Example 3-3 (Cont.) COPY Command with Multiple Output Save&                                   Sets  D               $ saveset copy full.bck mkb200:image.bck/block=32768 -(               mkb500:full20.bck/group=20,               ERRORS terminal option enabled,               EVENTS terminal option enabledJ               Primary input save set DISK$USER:[NDIAMOND]FULL.BCK;1 opened.               Opening file MKB200:[]IMAGE.BCK;8               Output save set MKB200:[]IMAGE.BCK; opened/               Opening file MKB500:[]FULL20.BCK;a9               Output save set MKB500:[]FULL20.BCK; openeda  A               Save Set Manager V1.4 Time: 10-JUN-1999 13:56:01.74u  (                   SAVESET function: COPYH                   Primary input save set: DISK$USER:[NDIAMOND]FULL.BCK;1#                     No journal file 6                   Output save set: MKB200:[]IMAGE.BCK;#                     No journal fileh7                   Output save set: MKB500:[]FULL20.BCK;R#                     No journal file   0                   Final status of each save set:  B                     Save set name:  DISK$USER:[NDIAMOND]FULL.BCK;1(                       No errors detected  7                     Save set name:  MKB200:[]IMAGE.BCK;t(                       No errors detected  8                     Save set name:  MKB500:[]FULL20.BCK;(                       No errors detected  ;                  In Example 3-3, two tape drives and a diskr?                  drive are being used. The input save set is oneG                  DISK$USER:[NDIAMOND] and is named FULL.BCK. Two copiestC                  of this save set are being made. One copy is beingtE                  written to the tape mounted on MKB200, with the sameSF                  name and other characteristics as the input save set,G                  except that the block size on the output tape is beinglF                  explicitly set to 32768, regardless of the block sizeI                  on the input save set. A second copy is being written to G                  the tape mounted on MKB500. For this copy, the name of I                  the save set is changed to FULL20.BCK, the group size is   I                                                  (continued on next page)o           3-28 Using SSMgr u  b      I                                                                      COPYn      H               Example 3-3 (Cont.) COPY Command with Multiple Output Save&                                   SetsH                  being explicitly set to 20, and all other characterists5                  of the input save set are preserved.       B               Example 3-4 COPY Command with IDENTICAL and OVERRIDE<                           Qualifiers on Save Set with Errors  O               $ saveset copy/identical/override star.sav mkb200:rock.bck/rewindo,               ERRORS terminal option enabled,               EVENTS terminal option enabled6               Rewinding MKB200: to beginning of volume(               Rewind of MKB200: completeE               Primary input save set DISK$USER:[GRD]STAR.SAV;1 opened -               Opening file MKB200:[]ROCK.BCK;a7               Output save set MKB200:[]ROCK.BCK; openedtN               CRC error: block number 33 in save set DISK$USER:[GRD]STAR.SAV;1M               Error recovery successful in save set DISK$USER:[GRD]STAR.SAV;1pS               %SAVESET-I-MISSINGBLK, Missing block could not be regenerated in file *               DISK$USER:[GRDEAD]STAR.SAV;1N               CRC error: block number 35 in save set DISK$USER:[GRD]STAR.SAV;1I               Recovery unsuccessful in save set DISK$USER:[GRD]STAR.SAV;1 Q               %SAVESET-I-BADCRC, Data CRC error in file DISK$USER:[GRD]STAR.SAV;1 N               CRC error: block number 42 in save set DISK$USER:[GRD]STAR.SAV;1L               Block recovered from XOR in save set DISK$USER:[GRD]STAR.SAV;1N               CRC error: block number 48 in save set DISK$USER:[GRD]STAR.SAV;1I               Recovery unsuccessful in save set DISK$USER:[GRD]STAR.SAV;1 Q               %SAVESET-I-BADCRC, Data CRC error in file DISK$USER:[GRD]STAR.SAV;1 I               XOR error at block 55 in save set DISK$USER:[GRD]STAR.SAV;1oN               CRC error: block number 60 in save set DISK$USER:[GRD]STAR.SAV;1I               Recovery unsuccessful in save set DISK$USER:[GRD]STAR.SAV;1rQ               %SAVESET-I-BADCRC, Data CRC error in file DISK$USER:[GRD]STAR.SAV;1RI               XOR error at block 66 in save set DISK$USER:[GRD]STAR.SAV;1   B               Save Set Manager V1.4  Time: 10-JUN-1999 14:38:49.31  I                                                  (continued on next page)v            I                                                          Using SSMgr 3-29R i  n               COPY      A               Example 3-4 (Cont.) COPY Command with IDENTICAL and F                                   OVERRIDE Qualifiers on Save Set with(                                   Errors  (                   SAVESET function: COPYF                   Primary input save set: DISK$USER:[GRDEAD]STAR.SAV;1#                     No journal filei5                   Output save set: MKB200:[]ROCK.BCK; #                     No journal filer  0                   Final status of each save set:  @                     Save set name:  DISK$USER:[GRDEAD]STAR.SAV;1;                     Unrecoverable CRC errors:             3 ;                     Recoverable CRC errors:               23;                     XOR errors:                           2E  6                     Save set name:  MKB200:[]ROCK.BCK;(                       No errors detected  B                  In Example 3-4, a copy of the save set, STAR.SAV,G                  located in the default disk directory, is being copiedhE                  to a tape mounted on tape device MKB200. The tape is E                  rewound before the copy is initiated. An "identical"tG                  copy is being made; i.e., no internal record structureiF                  validation is being done and the save set informationC                  stored within the output save set will reflect thehE                  environment in which the input save set was created,nE                  rather than the environment in which the output save G                  set is being created. Further, the /OVERRIDE qualifier C                  results in continued operation even in the face of D                  errors, accepting the fact that the output save set-                  may not be fully restorable.a  C               Example 3-5 COPY with Wildcarding, Journaling, and Noo!                           Logfilet  I                                                  (continued on next page)                        3-30 Using SSMgr P  Z      I                                                                      COPYI      H               Example 3-5 (Cont.) COPY with Wildcarding, Journaling, and,                                   No Logfile  &               $ saveset copy/all/nologH               _Input Save Set: dka400:[dcsc030.kit]*.*/checks=(crc,xor)-               _/journal=*.bjlaB               _Output Save Set: mkb200:*.*/crc/comment="DCSC Copy"!               _Output Save Set 2:P,               ERRORS terminal option enabled,               EVENTS terminal option enabledK               Primary input save set DKA400:[DCSC030.KIT]DCSC030.A;1 openedh.               Opening file MKB200:[]DCSC030.A;8               Output save set MKB200:[]DCSC030.A; opened  A               Save Set Manager V1.4 Time: 10-JUN-1999 14:53:20.21n  (                   SAVESET function: COPYI                   Primary input save set: DKA400:[DCSC030.KIT]DCSC030.A;1 @                     Journal file: DISK$GREEN:[DRAGON]DCSC030.BJL6                   Output save set: MKB200:[]DCSC030.A;#                     No journal filef  0                   Final status of each save set:  C                     Save set name:  DKA400:[DCSC030.KIT]DCSC030.A;1 (                       No errors detected  7                     Save set name:  MKB200:[]DCSC030.A; (                       No errors detected  K               Primary input save set DKA400:[DCSC030.KIT]DCSC030.B;1 openedn.               Opening file MKB200:[]DCSC030.B;8               Output save set MKB200:[]DCSC030.B; opened  A               Save Set Manager V1.4 Time: 10-JUN-1999 14:56:45.83   (                   SAVESET function: COPYI                   Primary input save set: DKA400:[DCSC030.KIT]DCSC030.B;1q@                     Journal file: DISK$GREEN:[DRAGON]DCSC030.BJL6                   Output save set: MKB200:[]DCSC030.B;#                     No journal fileb  0                   Final status of each save set:  I                                                  (continued on next page)   I                                                          Using SSMgr 3-31  u  f               COPY      H               Example 3-5 (Cont.) COPY with Wildcarding, Journaling, and,                                   No Logfile  C                     Save set name:  DKA400:[DCSC030.KIT]DCSC030.B;1c(                       No errors detected  7                     Save set name:  MKB200:[]DCSC030.B; (                       No errors detected  K               Primary input save set DKA400:[DCSC030.KIT]DCSC030.C;1 opened .               Opening file MKB200:[]DCSC030.C;8               Output save set MKB200:[]DCSC030.C; opened  A               Save Set Manager V1.4 Time: 10-JUN-1999 15:02:50.30   (                   SAVESET function: COPYI                   Primary input save set: DKA400:[DCSC030.KIT]DCSC030.C;1-@                     Journal file: DISK$GREEN:[DRAGON]DCSC030.BJL6                   Output save set: MKB200:[]DCSC030.C;#                     No journal file   0                   Final status of each save set:  C                     Save set name:  DKA400:[DCSC030.KIT]DCSC030.C;1n(                       No errors detected  7                     Save set name:  MKB200:[]DCSC030.C; (                       No errors detected  *                 Summary of COPY operations  <                   Total operations attempted:              3<                   Operations completing successfully:      3               $   5                  In Example 3-5, all the save sets ineG                  dka400:[dcsc030.kit] are copied to the tape mounted on H                  mkb200. No log file will be generated. CRC checking andG                  XOR checking will be performed on all the save sets as I                  they are being copied. A journal of the files is createdsF                  for each save set and given the name of each save setG                  with the .bjl extension. CRC is computed for each saveqI                  set on the tape, and the comment, "DCSC copy" is entered I                  into the save set comment field because the journal file E                  name is the same for all three save sets copied. TheuE                  second and third save sets' journal file entries aree  I                                                  (continued on next page)i           3-32 Using SSMgr p  f      I                                                                      COPY       H               Example 3-5 (Cont.) COPY with Wildcarding, Journaling, and,                                   No LogfileH                  appended to the journal file created for the first save                  set.t      E               Example 3-6 COPY with /JOURNAL and /TERMINAL QualifiersM  9               $ saveset copy/terminal=(errors,events,log)n:               _Input Save Set: mkb200:SAVESET014.B/journal,               _Output Save Set: saveset014.b!               _Output Save Set 2:c)               LOG terminal option enabledp,               ERRORS terminal option enabled,               EVENTS terminal option enabled2               Opening file MKB200:[]SAVESET014.B;1C               Primary input save set MKB200:[]SAVESET014.B;1 openedoF               Output save set DISK$USER:[SOFTWARE]SAVESET014.B; openedI               Processing user file: [SOFTWARE.SAVESET014]KITINSTAL.COM;29 K               Processing user file: [SOFTWARE.SAVESET014]SAVESET$IVP.COM;14 F               Processing user file: [SOFTWARE.SAVESET014]SAVESET.CLD;4F               Processing user file: [SOFTWARE.SAVESET014]SAVESET.HLP;49               Processing user file: [SOFTWARE.SAVESET014] )                SAVESET014.RELEASE_NOTES;3t9               Processing user file: [SOFTWARE.SAVESET014] ,                SAVESET014_RELEASE_NOTES.PS;59               Processing user file: [SOFTWARE.SAVESET014]t(                SAVESET_COVER_LETTER.PS;69               Processing user file: [SOFTWARE.SAVESET014] '                SAVESET_USER_GUIDE.PS;17T9               Processing user file: [SOFTWARE.SAVESET014] '                SAVESET_USER_GUIDE.TXT;8q  A               Save Set Manager V1.4 Time: 10-JUN-1999 15:31:56.90d  I                                                  (continued on next page)S                I                                                          Using SSMgr 3-33n                    COPY      B               Example 3-6 (Cont.) COPY with /JOURNAL and /TERMINAL,                                   Qualifiers  (                   SAVESET function: COPYA                   Primary input save set: MKB200:[]SAVESET014.B;1v1                     Journal file: SAVESET014.BJL;uD                   Output save set: DISK$USER:[SOFTWARE]SAVESET014.B;#                     No journal file   0                   Final status of each save set:  ;                     Save set name:  MKB200:[]SAVESET014.B;1 (                       No errors detected  E                     Save set name:  DISK$USER:[SOFTWARE]SAVESET014.B;t(                       No errors detected  ?                  Example 3-6 shows how to enable all classes ofhG                  information that can be displayed to a terminal duringuG                  a copy operation that copies the save set SAVESET014.B_F                  from the tape mounted on MKB200 to the directory fromI                  which the command is issued. Note the prompt for anotherTE                  output save set, should you decide to create anothernB                  copy during the same operation. If you don't wantH                  another copy, hit <return>. A journal file of the name,C                  SAVESET014.BJL, is created in that same directory.   G               Example 3-7 COPY with /BLOCK_SIZE, /GROUP_SIZE, and /FULL $                           Qualifiers  5               $ saveset copy/full mkb200:SAVESET014.b F               _Output Save Set: copy.sav/block_size=3072/group_size=20!               _Output Save Set 2:m,               ERRORS terminal option enabled,               EVENTS terminal option enabled2               Opening file MKB200:[]SAVESET014.B;1C               Primary input save set MKB200:[]SAVESET014.B;1 opened B               Output save set DISK$USER:[SOFTWARE]COPY.SAV; opened  B               Save Set Manager V1.4  Time: 10-JUN-1999 15:42:28.56  I                                                  (continued on next page)                3-34 Using SSMgr ]  Y      I                                                                      COPYO      I               Example 3-7 (Cont.) COPY with /BLOCK_SIZE, /GROUP_SIZE, ande2                                   /FULL Qualifiers  (                   SAVESET function: COPYA                   Primary input save set: MKB200:[]SAVESET014.B;1f#                     No journal files@                   Output save set: DISK$USER:[SOFTWARE]COPY.SAV;#                     No journal file   0                   Final status of each save set:  ;                     Save set name:  MKB200:[]SAVESET014.B;1r<                     Save set group size:                  25>                     Save set block size:                  9216=                     Blocks in save set:                   106a;                     Nondirectory files in save set:       9 ;                     Directory files in save set:          0 ;                     Alias nondirectory files in save set: 0 ;                     Alias directories in save set:        0n;                     Unrecoverable CRC errors:             0 ;                     Recoverable CRC errors:               0O;                     Unrecoverable checksum errors:        0 ;                     Recoverable checksum errors:          0 ;                     XOR errors:                           0k;                     Read errors:                          0 ;                     Write errors:                         0i;                     Record errors:                        0$;                     Unrecoverable missing blocks:         0M;                     Recoverable missing blocks:           0A;                     Rewritten blocks:                     0K(                       No errors detected  I                                                  (continued on next page)                         I                                                          Using SSMgr 3-35  K  E               COPY      I               Example 3-7 (Cont.) COPY with /BLOCK_SIZE, /GROUP_SIZE, and02                                   /FULL Qualifiers  A                     Save set name:  DISK$USER:[SOFTWARE]COPY.SAV; <                     Save set group size:                  20>                     Save set block size:                  3072=                     Blocks in save set:                   361d;                     Nondirectory files in save set:       9 ;                     Directory files in save set:          0 ;                     Alias nondirectory files in save set: 0 ;                     Alias directories in save set:        0p;                     Unrecoverable CRC errors:             0T;                     Recoverable CRC errors:               0D;                     Unrecoverable checksum errors:        0s;                     Recoverable checksum errors:          0 ;                     XOR errors:                           0 ;                     Read errors:                          0e;                     Write errors:                         0 ;                     Record errors:                        0a;                     Unrecoverable missing blocks:         0s;                     Recoverable missing blocks:           0t;                     Rewritten blocks:                     0 (                       No errors detected  <                  In Example 3-7, the save set, SAVESET014.B,=                  is copied from the tape mounted on MKB200 torE                  DISK$USER:[SOFTWARE]COPY.SAV. The block size will be H                  3072 and the group size = 20 in the save set, COPY.SAV.I                  Note the prompt for an additional output save set if all F                  the information is not entered on the initial commandI                  line. A full report will be generated upon completion of $                  the copy operation.                                   3-36 Using SSMgr t  t      I                                                                     MERGEb      I         _________________________________________________________________r  
         MERGEl  )               Merges two input save sets.i           Format  B               MERGE  primary-input-ss secondary-input-ss output-ssD                      [output-ss] [output-ss] [output-ss] [output-ss]           Parameters                 primary-input-ssF               OpenVMS file name of an input save set. The primary saveE               set can be an image, incremental, or file-oriented saves               set.                  secondary-input-ssB               OpenVMS file name of a secondary input save set. TheI               secondary input save set is an incremental or file-orientedmH               save set that covers a period of time starting at the time/               the primary save set was created.                  output-ssRC               OpenVMS file name(s) of the output save set(s). Up toRF               five output save sets may be specified. Unless otherwiseG               specified by command qualifiers, the output save set will F               have the same attributes for XOR group size, block size,F               CRC, and other attributes as the primary input save set.E               Different qualifiers may be applied to each output saveE               set.           Description   H               The MERGE operation takes two OpenVMS BACKUP save sets andE               produces 1 to 5 output save sets. Acceptable input saveeH               sets include image backups, incremental backups, and file-E               oriented save sets. The following combinations of input I               primary and secondary save sets result in the listed output                save sets:        I                                                          Using SSMgr 3-37            
         MERGEa    I               ___________________________________________________________g/               Primary Input     Secondary Input I               Save_Set__________Save_Set__________Output_Save_Set________   7               Image             Incremental       Imageh  =               Incremental       Incremental       IncrementalA  ?               Incremental       File-oriented     File-orientedK  ?               File-oriented     Incremental       File-oriented   I               File-oriented_____File-oriented_____File-oriented__________u  ;               No other combinations of save sets are legal.   E               The output save set contains the merge of the two input E               save sets. If the primary save set was an image backup, D               the output saves set contain an image backup up to theD               time that the secondary input save set was created. IfD               the primary and secondary save sets were incrementals,B               the output save set will contain an incremental saveE               set that spans the combined time frame of the two inputh               incrementals.m  B               The output save sets' CRC and XOR protections can beC               independently specified to be present, absent, or thesD               same as the primary save set. If detected by SSMgr, anG               attempt to merge a primary save set with an inappropriatee@               incremental save set, such as from another disk orD               noncontiguous time period, will result in a diagnosticE               message and an aborted operation. However, SSMgr cannot G               detect all such inappropriate combinations; the result of G               such an inappropriate merge will be a legal save set, butr1               its contents may not be meaningful.   E               The MERGE operation does not accept physical save sets.            Qualifiers                 /BLOCK_SIZE=n                    3-38 Using SSMgr           I                                                                     MERGE       '               Output save set qualifier   D               This qualifier specifies the desired block size of theF               output save set. Valid values for n are between 2048 andG               65024, and are rounded up to the nearest multiple of 512.aI               The block size of the primary input save set is used if thec4               BLOCK_SIZE qualifier is not specified.  @               As required by OpenVMS BACKUP, the upper limit forD               save sets on disks is 32256. If a larger block size is;               specified, SSMgr will round it down to 32256.m                 /BRIEF (default)                 Command qualifier   E               This qualifier specifies that a minimum level of detail0H               is to be echoed. The SAVESET function and save set name(s)E               are echoed; any error information is displayed; and the H               result of the SAVESET operation is reported. See /FULL for4               a complete list of output information.    '               /CHECKS=([NO]CRC,[NO]XOR):  &               Input save set qualifier  F               This qualifier specifies the optional consistency checksG               that will be performed on the input save set; the default                is CRC, XOR.  C               You must specify this qualifier immediately after the E               file name of the save set on the command line, as shownAG               in Example 3-10. Example 3-12 shows that when you specify]H               both CRC and XOR checks, you must list them in parentheses+               with a comma separating them.N  D               If CRC checking is specified and the input save set isG               written with CRC, then the CRC is computed for each block H               in the input save set. The CRC is compared against the CRC)               stored in the block header.         I                                                          Using SSMgr 3-39e           
         MERGE       A               If XOR checking is specified and the input save set D               was written with XOR redundancy, then a running XOR isG               computed across each XOR group of blocks. The running XORn+               is compared to the XOR block.   B               Each of these options requires additional processingF               time and may impact the performance of SSMgr. Any CRC orD               XOR inconsistencies are written to the log file and anI               informational message is returned to the calling program or0.               user when the command completes.                                                                               3-40 Using SSMgr    a      I                                                                     MERGEu                         /COMMENT=stringn                 Command qualifierC  F               This qualifier inserts a comment in the output save set.D               The string can be up to 252 characters. If the commentC               string is longer than one word or if it contains non-sG               alphanumeric characters, it must be enclosed in quotation3G               marks ("). If not specified, no comment is written to thea               output save set.                   /CRC               /NOCRC  '               Output save set qualifiers  G               Specifying /CRC causes the CRC to be computed across each I               block of the output save set and stored in the block header E               of each block of the output save set. Specifying /NOCRCaB               causes CRC computation to be inhibited on the outputF               save set. If this qualifier is not specified, the CRC isG               computed and stored in the output save set only if it was 4               present in the primary input save set.                   /FULL                  Command qualifierm  H               This qualifier specifies that more detail is to be echoed.B               In addition to information displayed with the /BRIEFD               qualifier, the following information for each save set               is displayed:                     Save set name$                  Save set group size$                  Save set block size-                  Number of blocks in save set 4                  Nondirectory user files in save set1                  Directory user files in save set 5                  Alias nondirectory files in save set   I                                                          Using SSMgr 3-41a n  J      
         MERGE       2                  Alias directory files in save set)                  Unrecoverable CRC errors '                  Recoverable CRC errors ,                  Recoverable checksum errors.                  Unrecoverable checksum errors                  XOR errorsn                  Read errors                  Write errorsj                  Record errors-                  Unrecoverable missing blockse+                  Recoverable missing blocksn!                  Rewritten blocksa                                                                           3-42 Using SSMgr 0  ]      I                                                                     MERGEe                         /GROUP_SIZE=nU  '               Output save set qualifier   G               This qualifier specifies the XOR group size in the output I               save set. Valid values for n are between 0 and 100. A value D               of 0 specifies that no XOR should be computed. If thisG               qualifier is not specified, the group size of the primary %               input save set is used..    *               /JOURNAL[=journal-file-name]                  Save set qualifier  B               This qualifier specifies whether SSMgr will create aC               journal file for the save set. The journal file is an D               OpenVMS BACKUP journal file with an OpenVMS file name.I               If no journal file name is specified, the journal file will E               be written to <saveset_name>.BJL in the current default                directory.  F               If a journal file with the same name already exists, theI               new journal file is appended. If it does not already exist, ,               a new journal file is created.  E               Journal files created by SSMgr will not list the labels E               of follow-on volumes in multivolume tape sets. Also, ifLD               COPY/IDENTICAL is used to copy a multivolume tape to aH               single volume tape, the journal file will still list it as%               a multivolume tape set.r  I               These differences from Backup created journal files are dueTI               to a limitation in VMS that does not allow a non-privileged G               process to obtain the volume labels of a multivolume tapeK               set.  H               You must specify this qualifier immediately after the save:               set file name specifier on the command line.  @               This qualifier is valid for all save set file nameA               specifiers, input or output, on all SSMgr commands.d  I                                                          Using SSMgr 3-43     e      
         MERGE       G               Journal files will be created for each save set specified B               on the command line that is followed by the /JOURNALH               qualifier. If more than one journal file is being created,I               each journal file name must be unique. For example, SAVESET I               MERGE FULL.BCK/JOURNAL INCR.BCK/JOURNAL FULL.BCK/JOURNAL is H               illegal, because the resulting journal file names would be/               FULL.BJL, INCR.BJL, and FULL.BJL.   (               The default is /NOJOURNAL.                                                                                 3-44 Using SSMgr b  k      I                                                                     MERGES      0               /LOG_FILE[=logfile-name] (default)               /NOLOG_FILE                  Command qualifierB  G               This qualifier causes SSMgr to write events to a log file E               specified by logfile-name. The logfile-name is an ASCII F               file with an OpenVMS file name. By default, a logfile isE               created for every execution of an SSMgr command. If not H               specified, the default log file name is SAVESET.LOG in theF               current default directory. You can suppress the creationH               of a default log file by using /NOLOG_FILE or bu includingI               /LOG_FILE=NL: on the command line. The following events areY.               written to the SAVESET.LOG file:  )               o  Each invocation of SSMgrj  C               o  All output returned to the user or calling programP  D               o  Any errors or warnings encountered while processing                   input save sets  "               o  Operator requests  G               Wildcards may not be used in the specification of logfile                names.                 /REWIND !               /NOREWIND (default)   0               Input or output save set qualifier  E               For magnetic tape volumes only, REWIND directs SSMgr to E               rewind the magnetic tape to the beginning-of-tape (BOT) /               marker before reading the volume.   C               You must specify this qualifier immediately after theeC               applicable file name on the command line, as shown in 5               Example 3-12 for the /CHECKS qualifier.o  E               The following consequences result when using the REWINDs               qualifier:  H               o  If specified with an input save set, SSMgr searches forF                  the specified file starting at the BOT position. ThisF                  allows SSMgr to find files located before the current&                  position of the tape.  I                                                          Using SSMgr 3-45l i  n      
         MERGEA      G               o  If specified with an output save set, SSMgr overwrites D                  the tape starting at BOT. All files on the tape are%                  therefore destroyed.   G               The default for this qualifier is /NOREWIND, which causesUA               SSMgr to start processing the tape from the currentx               position.t    9               /TERMINAL=([NO]ERRORS, [NO]EVENTS, [NO]LOG)                  Command qualifier   D               This qualifier specifies what class(es) of informationI               should be displayed on the user's terminal during executionb%               of the SAVESET command.   I               If ERRORS is specified, then all error conditions occurring G               during execution are displayed as they occur, in additioniI               to being included in the final report at the end of commandi,               execution and in the log file.  H               If EVENTS is specified, then all nonerror event conditionsB               occurring during execution (e.g., tape switches) are&               displayed as they occur.  D               If LOG is specified, then the names of all output userB               files (for COPY and MERGE) are displayed as they areH               written to the output save set. For VALIDATE, the names ofG               all input user files are displayed as they are processed.   =               The default is /TERMINAL=(ERRORS,EVENTS,NOLOG).            Examples  F                  In Example 3-8, an image save set, full.bck, is beingF                  merged with an incremental save set, incr.bck, in theD                  default disk directory. Two copies of the resultantE                  virtual image save set are being created, one in thedB                  current default directory and another on the tapeI                  mounted on device mbk500:. Each output save set is namedu                  merge.bck.C               3-46 Using SSMgr    m      I                                                                     MERGE       '               Example 3-8 MERGE Command   J               $ saveset merge full.bck incr.bck merge.bck mkb500:merge.bck,               ERRORS terminal option enabled,               EVENTS terminal option enabledI               Primary input save set DISK$MUSIC:[MOZART]FULL.BCK;1 opened K               Secondary input save set DISK$MUSIC:[MOZART]INCR.BCK;1 openedrB               Output save set DISK$MUSIC:[MOZART]MERGE.BCK; opened.               Opening file MKB500:[]MERGE.BCK;8               Output save set MKB500:[]MERGE.BCK; opened  A               Save Set Manager V1.4 Time: 10-JUN-1999 16:03:43.18s  )                   SAVESET function: MERGE G                   Primary input save set: DISK$MUSIC:[MOZART]FULL.BCK;1 #                     No journal filerI                   Secondary input save set: DISK$MUSIC:[MOZART]INCR.BCK;1s#                     No journal filea@                   Output save set: DISK$MUSIC:[MOZART]MERGE.BCK;#                     No journal filee6                   Output save set: MKB500:[]MERGE.BCK;#                     No journal fileh  0                   Final status of each save set:  A                     Save set name:  DISK$MUSIC:[MOZART]FULL.BCK;1)(                       No errors detected  A                     Save set name:  DISK$MUSIC:[MOZART]INCR.BCK;1m(                       No errors detected  A                     Save set name:  DISK$MUSIC:[MOZART]MERGE.BCK;z(                       No errors detected7                     Save set name:  MKB500:[]MERGE.BCK; (                       No errors detected                    I                                                          Using SSMgr 3-47  n         
         MERGE           G               Example 3-9 MERGE Command with /FULL, /LOG, and /TERMINAL $                           Qualifiers  I               $ saveset merge/full/log=merge.log/terminal=error incr2.bckn,               _Secondary Save Set: incr3.bckG               _Output Save Set: incr4.bck/group_size=0/block_size=32256 !               _Output Save Set 2: ,               ERRORS terminal option enabled,               EVENTS terminal option enabledJ               Primary input save set DISK$MUSIC:[EAGLES]INCR2.BCK;1 openedL               Secondary input save set DISK$MUSIC:[EAGLES]INCR3.BCK;1 openedB               Output save set DISK$MUSIC:[EAGLES]INCR4.BCK; opened  A               Save Set Manager V1.4 Time: 10-JUN-1999 16:11:55.01m  )                   SAVESET function: MERGErH                   Primary input save set: DISK$MUSIC:[EAGLES]INCR2.BCK;1#                     No journal fileeJ                   Secondary input save set: DISK$MUSIC:[EAGLES]INCR3.BCK;1#                     No journal filea@                   Output save set: DISK$MUSIC:[EAGLES]INCR4.BCK;#                     No journal file   0                   Final status of each save set:  I                                                  (continued on next page)k                                           3-48 Using SSMgr s  w      I                                                                     MERGEl      E               Example 3-9 (Cont.) MERGE Command with /FULL, /LOG, and 6                                   /TERMINAL Qualifiers  B                     Save set name:  DISK$MUSIC:[EAGLES]INCR2.BCK;1<                     Save set group size:                  10?                     Save set block size:                  32256e=                     Blocks in save set:                   146 =                     Nondirectory files in save set:       140 <                     Directory files in save set:          17;                     Alias nondirectory files in save set: 0i;                     Alias directories in save set:        0e;                     Files removed by merge:               0t;                     Unrecoverable CRC errors:             0p;                     Recoverable CRC errors:               0 ;                     Unrecoverable checksum errors:        0p;                     Recoverable checksum errors:          0f;                     XOR errors:                           0U;                     Read errors:                          0 ;                     Write errors:                         0u;                     Record errors:                        0i;                     Unrecoverable missing blocks:         0 ;                     Recoverable missing blocks:           05;                     Rewritten blocks:                     0 (                       No errors detected  I                                                  (continued on next page)f                                      I                                                          Using SSMgr 3-495 I         
         MERGE       E               Example 3-9 (Cont.) MERGE Command with /FULL, /LOG, and 6                                   /TERMINAL Qualifiers  B                     Save set name:  DISK$MUSIC:[EAGLES]INCR3.BCK;1<                     Save set group size:                  10?                     Save set block size:                  32256d=                     Blocks in save set:                   234o;                     Nondirectory files in save set:       4f<                     Directory files in save set:          17;                     Alias nondirectory files in save set: 0 ;                     Alias directories in save set:        0 ;                     Files removed by merge:               0 ;                     Unrecoverable CRC errors:             0t;                     Recoverable CRC errors:               0 ;                     Unrecoverable checksum errors:        0 ;                     Recoverable checksum errors:          0p;                     XOR errors:                           0t;                     Read errors:                          0m;                     Write errors:                         0t;                     Record errors:                        0 ;                     Unrecoverable missing blocks:         0.;                     Recoverable missing blocks:           0 ;                     Rewritten blocks:                     0 (                       No errors detected  I                                                  (continued on next page)d                                               3-50 Using SSMgr a  ,      I                                                                     MERGEh      E               Example 3-9 (Cont.) MERGE Command with /FULL, /LOG, and 6                                   /TERMINAL Qualifiers  A                     Save set name:  DISK$MUSIC:[EAGLES]INCR4.BCK; ;                     Save set group size:                  0 ?                     Save set block size:                  32256l=                     Blocks in save set:                   326.=                     Nondirectory files in save set:       144 <                     Directory files in save set:          17;                     Alias nondirectory files in save set: 0 ;                     Alias directories in save set:        0m;                     Files removed by merge:               0e;                     Unrecoverable CRC errors:             0p;                     Recoverable CRC errors:               0o;                     Unrecoverable checksum errors:        0h;                     Recoverable checksum errors:          0 ;                     XOR errors:                           0 ;                     Read errors:                          0 ;                     Write errors:                         0e;                     Record errors:                        0u;                     Unrecoverable missing blocks:         0a;                     Recoverable missing blocks:           0f;                     Rewritten blocks:                     0s(                       No errors detected  G                  Example 3-9 shows an incremental save set in the file,sI                  incr2.bck being merged with a later incremental save set H                  in the file, incr3.bck, and being written to a save setH                  in the file, incr4.bck. A full report is generated uponH                  completion of the merge operation. All errors, if thereG                  are any, are displayed to the terminal. The group sizeiG                  is set to 0, and the block size is set to 32256 in the ,                  merged save set, incr4.bck.                        I                                                          Using SSMgr 3-51            
         MERGEr          H               Example 3-10 MERGE Command with /FULL, /TERMINAL, /CHECKS,-                            and CRC Qualifiers   1               $ saveset merge/full/terminal=event ;               _Primary Save Set: incr2.bck/checks=(crc,xor) =               _Secondary Save Set: incr3.bck/checks=(crc,xor) -               _Output Save Set: incr4.bck/crc !               _Output Save Set 2: ,               ERRORS terminal option enabled,               EVENTS terminal option enabledJ               Primary input save set DISK$BIRD:[HUMMING]INCR2.BCK;1 openedL               Secondary input save set DISK$BIRD:[HUMMING]INCR3.BCK;1 openedB               Output save set DISK$BIRD:[HUMMING]INCR4.BCK; opened  A               Save Set Manager V1.4 Time: 10-JUN-1999 16:30:30.88   )                   SAVESET function: MERGE H                   Primary input save set: DISK$BIRD:[HUMMING]INCR2.BCK;1#                     No journal file J                   Secondary input save set: DISK$BIRD:[HUMMING]INCR3.BCK;1#                     No journal fileo@                   Output save set: DISK$BIRD:[HUMMING]INCR4.BCK;#                     No journal file   0                   Final status of each save set:  I                                                  (continued on next page)                                          3-52 Using SSMgr           I                                                                     MERGE       G               Example 3-10 (Cont.) MERGE Command with /FULL, /TERMINAL,i>                                    /CHECKS, and CRC Qualifiers  B                     Save set name:  DISK$BIRD:[HUMMING]INCR2.BCK;1<                     Save set group size:                  10?                     Save set block size:                  32256 =                     Blocks in save set:                   146i=                     Nondirectory files in save set:       140 <                     Directory files in save set:          17;                     Alias nondirectory files in save set: 0e;                     Alias directories in save set:        0f;                     Files removed by merge:               0 ;                     Unrecoverable CRC errors:             0a;                     Recoverable CRC errors:               0l;                     Unrecoverable checksum errors:        0 ;                     Recoverable checksum errors:          0r;                     XOR errors:                           0l;                     Read errors:                          0u;                     Write errors:                         0 ;                     Record errors:                        0 ;                     Unrecoverable missing blocks:         0n;                     Recoverable missing blocks:           0f;                     Rewritten blocks:                     0S(                       No errors detected  I                                                  (continued on next page)G                                      I                                                          Using SSMgr 3-53l    t      
         MERGEJ      G               Example 3-10 (Cont.) MERGE Command with /FULL, /TERMINAL,,>                                    /CHECKS, and CRC Qualifiers  B                     Save set name:  DISK$BIRD:[HUMMING]INCR3.BCK;1<                     Save set group size:                  10?                     Save set block size:                  32256 =                     Blocks in save set:                   234 ;                     Nondirectory files in save set:       4 <                     Directory files in save set:          17;                     Alias nondirectory files in save set: 0 ;                     Alias directories in save set:        0 ;                     Files removed by merge:               0 ;                     Unrecoverable CRC errors:             0g;                     Recoverable CRC errors:               0n;                     Unrecoverable checksum errors:        0e;                     Recoverable checksum errors:          0x;                     XOR errors:                           0,;                     Read errors:                          0 ;                     Write errors:                         0 ;                     Record errors:                        0i;                     Unrecoverable missing blocks:         0e;                     Recoverable missing blocks:           0L;                     Rewritten blocks:                     0 (                       No errors detected  I                                                  (continued on next page)                                                3-54 Using SSMgr    O      I                                                                     MERGEo      G               Example 3-10 (Cont.) MERGE Command with /FULL, /TERMINAL,W>                                    /CHECKS, and CRC Qualifiers  A                     Save set name:  DISK$BIRD:[HUMMING]INCR4.BCK;M<                     Save set group size:                  10?                     Save set block size:                  32256 =                     Blocks in save set:                   359f=                     Nondirectory files in save set:       144e<                     Directory files in save set:          17;                     Alias nondirectory files in save set: 0h;                     Alias directories in save set:        0 ;                     Files removed by merge:               0 ;                     Unrecoverable CRC errors:             0i;                     Recoverable CRC errors:               0 ;                     Unrecoverable checksum errors:        0 ;                     Recoverable checksum errors:          0g;                     XOR errors:                           0 ;                     Read errors:                          0 ;                     Write errors:                         0a;                     Record errors:                        0 ;                     Unrecoverable missing blocks:         0 ;                     Recoverable missing blocks:           0r;                     Rewritten blocks:                     0[(                       No errors detected  E                  Example 3-10 shows the merge of two incremental save B                  sets, incr2.bck and incr3.bck, into the save set,F                  incr4.bck. A full report is generated upon completionH                  of the merge operation. All events are displayed to theG                  terminal. CRC and XOR checking is performed on both oftF                  the input save sets, incr2.bck, and incr3.bck. CRC is9                  added to the merged save set, incr4.bck.                           I                                                          Using SSMgr 3-55g e  i      
         MERGEe          I               Example 3-11 MERGE Command with Journaling on All Save Setst  9               $ saveset merge incr2.bck/journal=incr2.bjlP>               _Secondary Save Set: incr3.bck/journal=incr3.bjl;               _Output Save Set: incr4.bck/journal=incr4.bjl !               _Output Save Set 2:d,               ERRORS terminal option enabled,               EVENTS terminal option enabledH               Primary input save set DISK$BEE:[BONNET]INCR2.BCK;1 openedJ               Secondary input save set DISK$BEE:[BONNET]INCR3.BCK;1 opened@               Output save set DISK$BEE:[BONNET]INCR4.BCK; opened  A               Save Set Manager V1.4 Time: 10-JUN-1999 16:40:04.67   )                   SAVESET function: MERGEtF                   Primary input save set: DISK$BEE:[BONNET]INCR2.BCK;1+                     Journal file: INCR2.BJLuH                   Secondary input save set: DISK$BEE:[BONNET]INCR3.BCK;1+                     Journal file: INCR3.BJL >                   Output save set: DISK$BEE:[BONNET]INCR4.BCK;+                     Journal file: INCR4.BJLe  0                   Final status of each save set:  @                     Save set name:  DISK$BEE:[BONNET]INCR2.BCK;1(                       No errors detected  @                     Save set name:  DISK$BEE:[BONNET]INCR3.BCK;1(                       No errors detected  ?                     Save set name:  DISK$BEE:[BONNET]INCR4.BCK;O(                       No errors detected  E                  Example 3-11 shows the merge of two incremental saveEA                  set, incr2.bck and incr3.bck, into the save set,9H                  incr4.bck. A journal file is created for each save set.                       3-56 Using SSMgr O  T      I                                                                  VALIDATEn      I         _________________________________________________________________a           VALIDATE  E               Validates the internal consistency and readability of au               save set.            Format                  VALIDATE  input-ss           Parameters                 input-ss6               OpenVMS file name of the input save set.           Description[  I               The SSMgr VALIDATE command reads an OpenVMS BACKUP save set F               and verifies that at least one copy of each block of theG               specified save set is readable or can be regenerated with[@               OpenVMS BACKUP or by using the SSMgr COPY command.  I               The VALIDATE command differs from the OpenVMS BACKUP/VERIFYoI               operation in that it does not compare the save set contents F               with the data on disk. It only verifies that the data inA               the save set is readable and internally consistent.   C               Any data integrity problems found during the VALIDATEe?               operation, including unreadable data, CRC and XOR F               consistency errors, and regenerated blocks, are reported               to the user.           Qualifiers                 /ALL                /[NO]ALL (default)                 Command qualifiert  G               This qualifier specifies the behavior of Save Set ManagerG4               when save set names contain wildcards.  B               If ALL is specified, then all save sets matching the:               wildcarded file specification are processed.  I                                                          Using SSMgr 3-57A E  u               VALIDATE      B               If NOALL is specified, then only the first file nameE               found that matches the wildcarded file specification ist               processed.  C               The qualifier is valid only for the VALIDATE and COPYs               functions.  $               The default is /NOALL.                 /BRIEF (default)                 Command qualifier   E               This qualifier specifies that a minimum level of detail H               is to be echoed. The SAVESET function and save set name(s)E               are echoed; any error information is displayed; and thelH               result of the SAVESET operation is reported. See /FULL for4               a complete list of output information.  $               The default is /BRIEF.  '               /CHECKS=([NO]CRC,[NO]XOR)   &               Input save set qualifier  F               This qualifier specifies the optional consistency checks;               that will be performed on the input save set.   C               You must specify this qualifier immediately after the H               file name of the save set on the command line, as shown inI               Example 3-12. Example 3-12 also shows that when you specify H               both CRC and XOR checks, you must list them in parentheses+               with a comma separating them.n  D               If CRC checking is specified and the input save set isG               written with CRC, then the CRC is computed for each blockeH               in the input save set. The CRC is compared against the CRCG               stored in the block header. If the input save set was not ?               written with CRC, then this qualifier is ignored.   A               If XOR checking is specified and the input save set D               was written with XOR redundancy, then a running XOR isG               computed across each XOR group of blocks. The running XORnE               is compared to the XOR block. If the input save set was E               not written with XOR redundancy, then this qualifier is                ignored.           3-58 Using SSMgr a  f      I                                                                  VALIDATE       B               Each of these options requires additional processingC               time and may impact the performance of SSMgr. Any CRC F               or XOR inconsistencies are written to the log file and aF               diagnostic message is returned to the calling program or-               user when processing completes.   /               The default is /CHECKS=(CRC,XOR).                    /FULL                  Command qualifier   H               This qualifier specifies that more detail is to be echoed.B               In addition to information displayed with the /BRIEFD               qualifier, the following information for each save set               is displayed:e                    Save set name$                  Save set group size$                  Save set block size-                  Number of blocks in save set 4                  Nondirectory user files in save set1                  Directory user files in save set 5                  Alias nondirectory files in save set 2                  Alias directory files in save set)                  Unrecoverable CRC errorsr'                  Recoverable CRC errors ,                  Recoverable checksum errors.                  Unrecoverable checksum errors                  XOR errors                   Read errors                  Write errors                   Record errors-                  Unrecoverable missing blockse+                  Recoverable missing blocks !                  Rewritten blocks   $               The default is /BRIEF.  *               /JOURNAL[=journal-file-name]        I                                                          Using SSMgr 3-59                     VALIDATE                      Save set qualifier  B               This qualifier specifies whether SSMgr will create aC               journal file for the save set. The journal file is an D               OpenVMS BACKUP journal file with an OpenVMS file name.I               If no journal file name is specified, the journal file willsE               be written to <saveset_name>.BJL in the current default                directory.  F               If a journal file with the same name already exists, theI               new journal file is appended. If it does not already exist,o,               a new journal file is created.  E               Journal files created by SSMgr will not list the labelseE               of follow-on volumes in multivolume tape sets. Also, if D               COPY/IDENTICAL is used to copy a multivolume tape to aH               single volume tape, the journal file will still list it as%               a multivolume tape set.   I               These differences from BACKUP created journal files are due I               to a limitation in VMS that does not allow a non-privileged G               process to obtain the volume labels of a multivolume tape                set.  H               You must specify this qualifier immediately after the save:               set file name specifier on the command line.  @               This qualifier is valid for all save set file nameA               specifiers, input or output, on all SSMgr commands.   (               The default is /NOJOURNAL.  0               /LOG_FILE[=logfile-name] (default)               /NOLOG_FILEt                 Command qualifierh  G               This qualifier causes SSMgr to write events to a log file E               specified by logfile-name. The logfile-name is an ASCIIlF               file with an OpenVMS file name. By default, a logfile isE               created for every execution of an SSMgr command. If notiH               specified, the default log file name is SAVESET.LOG in theF               current default directory. You can suppress the creationH               of a default log file by using /NOLOG_FILE or by includingI               /LOG_FILE=NL: on the command line. The following events are/.               written to the SAVESET.LOG file:           3-60 Using SSMgr           I                                                                  VALIDATEc      )               o  Each invocation of SSMgre  C               o  All output returned to the user or calling programc  D               o  Any errors or warnings encountered while processing                   input save sets  "               o  Operator requests  G               Wildcards may not be used in the specification of logfile                names.  3               The default is /LOG_FILE=SAVESET.LOG.                                                                 I                                                          Using SSMgr 3-61                     VALIDATE                     /REWIND !               /NOREWIND (default)I  &               Input save set qualifier  E               For magnetic tape volumes only, REWIND directs SSMgr toCE               rewind the magnetic tape to the beginning-of-tape (BOT)tE               marker before reading the volume. This qualifier allowslI               SSMgr to find save sets that are located before the current                tape position.  C               You must specify this qualifier immediately after the G               applicable file name of the save set on the command line, '               as shown in Example 3-12.   G               The default for this qualifier is /NOREWIND, which causes A               SSMgr to start processing the tape from the current E               position. Any input save set that is located before the =               current position of the tape will not be found.   9               /TERMINAL=([NO]ERRORS, [NO]EVENTS, [NO]LOG)                  Command qualifier   D               This qualifier specifies what class(es) of informationI               should be displayed on the user's terminal during execution %               of the SAVESET command.l  I               If ERRORS is specified, then all error conditions occurring G               during execution are displayed as they occur, in addition I               to being included in the final report at the end of commande,               execution and in the log file.  H               If EVENTS is specified, then all nonerror event conditionsB               occurring during execution (e.g., tape switches) are&               displayed as they occur.  D               If LOG is specified, then the names of all output userB               files (for COPY and MERGE) are displayed as they areH               written to the output save set. For VALIDATE, the names ofG               all input user files are displayed as they are processed.c  =               The default is /TERMINAL=(ERRORS,EVENTS,NOLOG).              3-62 Using SSMgr    o      I                                                                  VALIDATEn                 Examples    +               Example 3-12 VALIDATE Command   H               $ saveset validate mkb200:rock.bck/checks=(crc,xor)/rewind,               ERRORS terminal option enabled,               EVENTS terminal option enabled6               Rewinding MKB200: to beginning of volume(               Rewind of MKB200: complete.               Opening file MKB200:[]ROCK.BCK;1?               Primary input save set MKB200:[]ROCK.BCK;1 openeda  A               Save Set Manager V1.4 Time: 10-JUN-1999 19:17:42.17s  ,                   SAVESET function: VALIDATE=                   Primary input save set: MKB200:[]ROCK.BCK;1 #                     No journal file 0                   Final status of each save set:  7                     Save set name:  MKB200:[]ROCK.BCK;1e(                       No errors detected  E                  In Example 3-12, a save set named ROCK.BCK on MKB200eG                  is validated with CRC checking and XORing. The tape isoH                  rewound before the validation begins. A brief report is:                  generated upon completion of the command.  8               Example 3-13 VALIDATE with /Full Qualifier  Q               $ saveset validate mkb200:rock.bck/full/rewind/checks=(nocrc,noxor) ,               ERRORS terminal option enabled,               EVENTS terminal option enabled6               Rewinding MKB200: to beginning of volume(               Rewind of MKB200: complete.               Opening file MKB200:[]ROCK.BCK;1?               Primary input save set MKB200:[]ROCK.BCK;1 opened   A               Save Set Manager V1.4 Time: 10-JUN-1999 19:21:33.48   I                                                  (continued on next page)       I                                                          Using SSMgr 3-63                     VALIDATE      @               Example 3-13 (Cont.) VALIDATE with /Full Qualifier  ,                   SAVESET function: VALIDATE=                   Primary input save set: MKB200:[]ROCK.BCK;1n#                     No journal file 0                   Final status of each save set:  7                     Save set name:  MKB200:[]ROCK.BCK;1 <                     Save set group size:                  10?                     Save set block size:                  32256e=                     Blocks in save set:                   146e=                     Nondirectory files in save set:       140 <                     Directory files in save set:          17;                     Alias nondirectory files in save set: 0 ;                     Alias directories in save set:        0 ;                     Unrecoverable CRC errors:             0 ;                     Recoverable CRC errors:               0r;                     Unrecoverable checksum errors:        0:;                     Recoverable checksum errors:          0 ;                     XOR errors:                           0 ;                     Read errors:                          0 ;                     Write errors:                         0 ;                     Record errors:                        0s;                     Unrecoverable missing blocks:         0 ;                     Recoverable missing blocks:           0 ;                     Rewritten blocks:                     0 (                       No errors detected  D                  Example 3-13 shows usage of the VALIDATE command toD                  validate ROCK.BCK with full details provided in theE                  report, without the optional CRC and XOR consistencyeD                  checking, without a journal file, without rewindingF                  the tape, and with ERRORS and EVENTS terminal classes                  enabled.s                               3-64 Using SSMgr c  b      I                                                                  VALIDATE           >               Example 3-14 VALIDATE All Save Sets in Directory  :               $ saveset validate/all playoffs.*/checks=crc,               ERRORS terminal option enabled,               EVENTS terminal option enabledN               Primary input save set DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.96;1                opened   A               Save Set Manager V1.4 Time: 10-JUN-1999 19:31:19.04n  ,                   SAVESET function: VALIDATES                   Primary input save set: DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.96;1 #                     No journal fileS  0                   Final status of each save set:M                     Save set name:  DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.96;1r(                       No errors detected  N               Primary input save set DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.97;1                opened2  A               Save Set Manager V1.4 Time: 10-JUN-1999 19:31:22.25   ,                   SAVESET function: VALIDATES                   Primary input save set: DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.97;1 #                     No journal file   0                   Final status of each save set:  M                     Save set name:  DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.97;1I(                       No errors detected  N               Primary input save set DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.98;1                opened   A               Save Set Manager V1.4 Time: 10-JUN-1999 19:31:23.24   ,                   SAVESET function: VALIDATES                   Primary input save set: DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.98;1e#                     No journal filer  0                   Final status of each save set:  I                                                  (continued on next page)   I                                                          Using SSMgr 3-65                     VALIDATE      F               Example 3-14 (Cont.) VALIDATE All Save Sets in Directory  M                     Save set name:  DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.98;1a(                       No errors detected  N               Primary input save set DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.99;1                openeds  A               Save Set Manager V1.4 Time: 10-JUN-1999 19:31:25.02e  ,                   SAVESET function: VALIDATES                   Primary input save set: DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.99;1e#                     No journal file   0                   Final status of each save set:  M                     Save set name:  DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.99;1 (                       No errors detected  .                 Summary of VALIDATE operations  <                   Total operations attempted:              4<                   Operations completing successfully:      4  E                  Example 3-14 shows the validation of all of the save G                  sets in the DISK$AVALANCE:[STANLEY_CUP] directory. CRC D                  checking is performed on each save set, and a briefE                  report is generated upon the completion of each save I                  set, followed by a summary report of all the operations.                                          3-66 Using SSMgr           I                                                                  VALIDATE       :               Example 3-15 VALIDATE with Journal Qualifier  I               $ saveset validate mkb500:SAVESET014.b/journal=kit.contentsc,               ERRORS terminal option enabled,               EVENTS terminal option enabled2               Opening file MKB500:[]SAVESET014.B;1C               Primary input save set MKB500:[]SAVESET014.B;1 opened   A               Save Set Manager V1.4 Time: 10-JUN-1999 19:43:31.09   ,                   SAVESET function: VALIDATEA                   Primary input save set: MKB500:[]SAVESET014.B;1i.                     Journal file: KIT.CONTENTS  0                   Final status of each save set:;                     Save set name:  MKB500:[]SAVESET014.B;1 (                       No errors detected  0               $ backup/journal=kit.contents/list'               Listing of BACKUP journaloI               Journal file DISK$PEAK:[PIKES]KIT.CONTENTS;1 on 10-JUN-1999p                19:44:23.45  F               Save set SAVESET014.B created on 10-JUN-1999 19:40:01.662               Volume number 1, volume label MERGE07                   [SOFTWARE.SAVESET014]KITINSTAL.COM;29i9                   [SOFTWARE.SAVESET014]SAVESET$IVP.COM;14o4                   [SOFTWARE.SAVESET014]SAVESET.CLD;44                   [SOFTWARE.SAVESET014]SAVESET.HLP;4A                   [SOFTWARE.SAVESET014]SAVESET014.RELEASE_NOTES;3 D                   [SOFTWARE.SAVESET014]SAVESET014_RELEASE_NOTES.PS;5@                   [SOFTWARE.SAVESET014]SAVESET_COVER_LETTER.PS;6?                   [SOFTWARE.SAVESET014]SAVESET_USER_GUIDE.PS;17 ?                   [SOFTWARE.SAVESET014]SAVESET_USER_GUIDE.TXT;8C  #               End of BACKUP journalv  C                  Example 3-15 shows the validation of the save set,eD                  SAVESET014.B, on the tape device, MKB500, that alsoH                  creates a journal file named, KIT.CONTENTS, showing theH                  files in the save set. Note that to see the contents ofD                  the resultant journal file, BACKUP must be invoked.      I                                                          Using SSMgr 3-67                     VALIDATE      A               Example 3-16 VALIDATE with Terminal Classes EnabledR  ?               $ saveset validate/terminal=(errors,events,log) -X(               mkb500:SAVESET014.b/rewind)               LOG terminal option enabledS,               ERRORS terminal option enabled,               EVENTS terminal option enabled6               Rewinding MKB500: to beginning of volume(               Rewind of MKB500: complete2               Opening file MKB500:[]SAVESET014.B;1C               Primary input save set MKB500:[]SAVESET014.B;1 opened I               Processing user file: [SOFTWARE.SAVESET014]KITINSTAL.COM;29 K               Processing user file: [SOFTWARE.SAVESET014]SAVESET$IVP.COM;14HF               Processing user file: [SOFTWARE.SAVESET014]SAVESET.CLD;4F               Processing user file: [SOFTWARE.SAVESET014]SAVESET.HLP;49               Processing user file: [SOFTWARE.SAVESET014]y)                SAVESET014.RELEASE_NOTES;3,9               Processing user file: [SOFTWARE.SAVESET014] ,                SAVESET014_RELEASE_NOTES.PS;59               Processing user file: [SOFTWARE.SAVESET014]S(                SAVESET_COVER_LETTER.PS;69               Processing user file: [SOFTWARE.SAVESET014]r'                SAVESET_USER_GUIDE.PS;17c9               Processing user file: [SOFTWARE.SAVESET014]e'                SAVESET_USER_GUIDE.TXT;8   A               Save Set Manager V1.4 Time: 10-JUN-1999 19:51:55.14C  ,                   SAVESET function: VALIDATEA                   Primary input save set: MKB500:[]SAVESET014.B;1U#                     No journal file   0                   Final status of each save set:  ;                     Save set name:  MKB500:[]SAVESET014.B;1 (                       No errors detected  C                  Example 3-16 shows the validation of the save set,wC                  SAVESET014.B, on the tape device, MKB500, with all F                  classes of information: errors, events, and log beingF                  displayed to the terminal. The tape is rewound before1                  the validation operation begins.                3-68 Using SSMgr e  r                    I                                                                         4 I         _________________________________________________________________   I                                                Interpreting SSMgr Reports     G               This chapter describes the completion and interim reportse!               generated by SSMgr.l  7         4.1 Monitoring the Progress of SSMgr Operations   C               While SSMgr is running, you can use Ctrl/T to monitor F               the progress of the SSMgr operation. Each time you enterB               Ctrl/T, SSMgr displays a progress report as shown in               Example 4-1.  /               Example 4-1 Ctrl/T Report Examplet  Z               1 JOE::SMITH 15:44:09 SAVESET$S CPU=00:19:00.12 PF=392532 IO=292279 MEM=1131=               2  Current input file:    [SMITH]WS_LOGIN.COM;1 J               3  Input save set blocks:         5      Input files:     28J               4  Output save set blocks:        4      Output files:    24  F               1  The first line is the standard OpenVMS Ctrl/T output.  E               2  Name of last user file read from the input save set.e  I               3  Total number of save set blocks and user files that have ;                  been read from the primary input save set.   G               4  Total number of save set blocks and user files written G                  to the output save set. This is not displayed during am$                  VALIDATE operation.  E               Entering Ctrl/T before SSMgr has read the first file ofuE               the input save set will cause "None" to be displayed asgF               the current input file. On MERGE operations involving anH               image save set and an incremental save set, SSMgr displaysG               "None" in this field throughout the initial pass over theu#               incremental save set.e    I                                            Interpreting SSMgr Reports 4-1            "         Interpreting SSMgr Reports          4.2 Completion Reporting              4.2 Completion Reporting  G               When an SSMgr command terminates, the final status and/or E               a summary report is written to standard output. In most D               cases, this information also is written to a log file.  *         4.2.1 Normal Successful Completion  F               Every SSMgr operation that completes successfully issuesF               a completion report that details any errors or anomaliesH               found in the save sets. Refer to Example 4-2. If no errorsA               were detected, the report has the following format:   B         4.2.2 Successful Completion with Save Set Condition Report  G               If SSMgr found errors or anomalies in the input save set, G               but was still able to successfully complete the requestedAF               operation, then a save set condition report is produced.B               This report breaks out the number and type of errorsD               detected, as well as a list of user files affected. AnH               error can be either recoverable or unrecoverable. An errorD               is recoverable if the save set was created with an XORF               group size greater than zero, and there was no more thanF               one error in an XOR group. The following types of errorsC               and anomalies are broken out for each input save set:h  6               o  recoverable/unrecoverable CRC errors.  H               o  recoverable/unrecoverable block header checksum errors.  :               o  recoverable/unrecoverable missing blocks.  C               o  XOR mismatch errors. The XOR block at the end of arH                  group does not contain the XOR of all the blocks in theI                  group. Note that XOR mismatch errors are only considered I                  recoverable if CRC protection is present in the save set F                  and all data blocks in the XOR group had correct CRC.                 o  Read errors.   H               o  Record header errors. A record header within a save setH                  block contains an invalid record type or invalid record                  length.    &         4-2 Interpreting SSMgr Reports r  r      I                                                Interpreting SSMgr Reports I                                                  4.2 Completion Reporting     =               Example 4-2 Normal Successful Completion Report   M               1  $ saveset copy mkb200:rock.bck stones.sav/identical/override /               2  ERRORS terminal option enabled 0                   EVENTS terminal option enabled1               3  Opening file MKB200:[]ROCK.BCK;1 C                   Primary input save set MKB200:[]ROCK.BCK;1 openedeF                   Output save set DISK$MUSIC:[WAVES]STONES.SAV; opened  D               4  Save Set Manager V1.4 Time: 10-JUN-1999 20:04:29.93  )               5    SAVESET function: COPYV?                     Primary input save set: MKB200:[]ROCK.BCK;12%                       No journal fileaB                     Output save set: DISK$MUSIC:[WAVES]STONES.SAV;%                       No journal file   1               6    Final status of each save set:   7                     Save set name:  MKB200:[]ROCK.BCK;1i%               7    No errors detectedp  A                     Save set name:  DISK$MUSIC:[WAVES]STONES.SAV;M(                       No errors detected  0               1  Command as entered by the user.  5               2  Selected terminal options displayed.   C               3  Information about progress of command and save set                   names.                  4  Report header.h  A               5  Echo of the SSMgr command issued, separated intoeE                  function, input save set, output save set and statusl!                  of journal file.n  H               6  Status of each save set processed, including the statusE                  of multiple output save sets, if any were requested.r  >               7  No errors or anomalies, either recoverable or.                  unrecoverable, were detected.  D               o  Rewritten blocks. This is not an error, but a countD                  of the number of blocks which were rewritten due toC                  conditions such as bad spots on the media. If thisiI                  number is large, you may be able to significantly reducee  I                                            Interpreting SSMgr Reports 4-3u a  s      "         Interpreting SSMgr Reports          4.2 Completion Reporting    G                  the size of your save set by using SSMgr to copy it to(                  better media.  H               If recoverable errors were detected in the input save set,E               SSMgr also lists all files in the groups containing the)G               errors. These files are still readable, but are no longerID               protected by XOR redundancy. If a second error were toH               develop within the same XOR group, user file data could be               lost.   C               If your save set contains recoverable errors, Digital @               recommends that you use the SSMgr COPY function toB               regenerate the XOR redundancy protection. If you areE               dealing with save sets on media that is very old or hasfF               been improperly stored, Digital recommends that you copyA               the save set with the SAVESET COPY command with the H               /IDENTICAL and /OVERRIDE qualifers to another medium, thenG               SAVESET COPY the save set to a final medium with the /CRC I               and /GROUP qualifiers. This procedure accomplishes the copyeF               operation without the risk of running a second pass over                the suspect media.                                                &         4-4 Interpreting SSMgr Reports           I                                                Interpreting SSMgr Reports I                                                  4.2 Completion Reporting     3               Example 4-3 Save Set Condition Report   9               $ saveset merge zap4.sav zapcrc.sav foo.sav .                 ERRORS terminal option enabled.                 EVENTS terminal option enabled8                 Opening file DKB200:[ENGINEER]ZAP4.SAV;2I                 Primary input save set DKB200:[ENGINEER]ZAP4.SAV;2 opened <                 Opening file DISK$100:[ENGINEER]ZAPCRC.SAV;1O                 Secondary input save set DISK$100:[ENGINEER]ZAPCRC.SAV;1 openedn8                 Opening file DISK$100:[ENGINEER]FOO.SAV;B                 Output save set DISK$100:[ENGINEER]FOO.SAV; openedN                 Resetting to beginning of file DISK$100:[ENGINEER]ZAPCRC.SAV;1X                 File DISK$100:[ENGINEER]ZAPCRC.SAV;1 has been reset to beginning of fileC                 Save Set Manager V1.4 Time: 10-JUN-1999 20:38:36.57.  )                   SAVESET function: MERGEp2                   Primary input save set: ZAP4.SAV6                   Secondary input save set: ZAPCRC.SAV*                   Output save set: FOO.SAV  G               1Save set name:  DISK$100:[ENGINEER.SSM.SRC.TMP]ZAP4.SAV;9  8               2  Recoverable checksum errors:          1  /               3User files affected by error(s):[F                       [ENGINEER.SSM.VAXV60.OBJ]CONDITION_HANDLER.OBJ;3F                       [ENGINEER.SSM.VAXV60.OBJ]CONDITION_HANDLER.OBJ;2F                       [ENGINEER.SSM.VAXV60.OBJ]CONDITION_HANDLER.OBJ;1:                       [ENGINEER.SSM.VAXV60.OBJ]COPY.OBJ;25  I               4Save set name:  DISK$100:[ENGINEER.SSM.SRC.TMP]ZAPCRC.SAV;   8               5  Recoverable CRC errors:               1  I                                                  (continued on next page)n                    I                                            Interpreting SSMgr Reports 4-5            "         Interpreting SSMgr Reports          4.2 Completion Reporting    ;               Example 4-3 (Cont.) Save Set Condition Report   /               6User files affected by error(s):n,                       [ENGINEER]BATCH.COM;26/                       [ENGINEER]BL_SETUP.COM;15 /                       [ENGINEER]BL_SETUP.COM;142/                       [ENGINEER]BL_SETUP.COM;13E)                       [ENGINEER]BYE.COM;2 -                       [ENGINEER]EVEPLUS.COM;6 *                       [ENGINEER]FRED.COM;1.                       [ENGINEER]INIT$LSE.COM;3.                       [ENGINEER]INIT$LSE.COM;2.                       [ENGINEER]INIT$LSE.COM;1*                       [ENGINEER]LN03.COM;4+                       [ENGINEER]LOGIN.COM;6 +                       [ENGINEER]LOGIN.COM;5 +                       [ENGINEER]LOGIN.COM;4 +                       [ENGINEER]MEDIA.COM;1U,                       [ENGINEER]NEWEVE.COM;50                       [ENGINEER]NOTES$EDIT.COM;2+                       [ENGINEER]NOTUP.COM;2 0                       [ENGINEER]PAGE_COUNT.COM;9/                       [ENGINEER]PDC_ORDER.COM;3 6                       [ENGINEER]RAIDEV_GKSTARTUP.COM;10                       [ENGINEER]READ_DEMO.COM;13,                       [ENGINEER]SETDEF.COM;3+                       [ENGINEER]STOCK.COM;2s*                       [ENGINEER]TEMP.COM;2*                       [ENGINEER]UUCP.COM;1/                       [ENGINEER]WAS_LOGIN.COM;2e.                       [ENGINEER]WS_LOGIN.COM;1  ?               1  Name of first input save set containing errors                   /anomalies.  ;               2  Summary of errors found in first save set.3  G               3  List of user files in first input save set that are noD4                  longer protected by XOR redundancy.  @               4  Name of second input save set containing errors                  /anomalies.  I                                                  (continued on next page)   &         4-6 Interpreting SSMgr Reports           I                                                Interpreting SSMgr Reports I                                                  4.2 Completion Reporting     ;               Example 4-3 (Cont.) Save Set Condition Reporta  B               5  Summary of errors found in second input save set.  H               6  List of user files in second input save set that are no4                  longer protected by XOR redundancy.           4.2.3 Error ReportingB  E               In the case of an SSMgr MERGE or COPY operation (except C               COPY/IDENTICAL/OVERRIDE), SSMgr cannot continue afterAE               detecting an unrecoverable error. If this occurs, SSMgr G               terminates with an error message as shown in Example 4-4.   &               Example 4-4 Error Report  /               $ saveset copy zap2.bck zcopy.bck ,               ERRORS terminal option enabled,               EVENTS terminal option enabledJ               Primary input save set DISK$USER:[SOFTWARE]ZAP2.BCK;1 openedC               Output save set DISK$USER:[SOFTWARE]ZCOPY.BCK; opened S               CRC error: block number 50 in save set DISK$USER:[SOFTWARE]ZAP2.BCK;1oQ               Block recovered from XOR in save set DISK$USER:[SOFTWARE]ZAP2.BCK;1L  C                 Save Set Manager V1.4 Time: 10-JUN-1999 20:16:28.18   (                   SAVESET function: COPYH                   Primary input save set: DISK$USER:[SOFTWARE]ZAP2.BCK;1#                     No journal file.A                   Output save set: DISK$USER:[SOFTWARE]ZCOPY.BCK;_#                     No journal file   0                   Final status of each save set:  B                     Save set name:  DISK$USER:[SOFTWARE]ZAP2.BCK;1;                     Recoverable CRC errors:               1   4                     User files affected by error(s):C                       [SOFTWARE.SAVESET014]SAVESET_USER_GUIDE.PS;17S  B                     Save set name:  DISK$USER:[SOFTWARE]ZCOPY.BCK;(                       No errors detected      I                                            Interpreting SSMgr Reports 4-7t f         "         Interpreting SSMgr Reports          4.2 Completion Reporting             4.2.4 Log File  H               In addition to standard output, SSMgr messages and reportsG               also are sent to a log file as shown in Example 4-5. EachRF               log file begins with a diagnostic message containing theH               time the SSMgr command was issued, followed by a report orF               error message identical to that sent to standard output.F               The default log file name is SAVESET.LOG, written to theF               user's default directory. See the /LOGFILE= qualifier toH               change the log file name or supress creating the log file.  E               A new log file is created for each invocation of SSMgr.W                                                                  &         4-8 Interpreting SSMgr Reports H         I                                                Interpreting SSMgr Reports I                                                  4.2 Completion Reportingr    "               Example 4-5 Log File  @               $ saveset copy ssm.bck copy.sav/identical/override                 Log file:A  ,               ERRORS terminal option enabled,               EVENTS terminal option enabledM               Primary input save set DISK$ENGINEER:[SOFTWARE]SSM.BCK;1 opened F               Output save set DISK$ENGINEER:[SOFTWARE]COPY.SAV; openedV               CRC error: block number 15 in save set DISK$ENGINEER:[SOFTWARE]SSM.BCK;1Q               Recovery unsuccessful in save set DISK$ENGINEER:[SOFTWARE]SSM.BCK;19Y               %SAVESET-I-BADCRC, Data CRC error in file DISK$ENGINEER:[SOFTWARE]SSM.BCK;1nQ               XOR error at block 26 in save set DISK$ENGINEER:[SOFTWARE]SSM.BCK;1 V               CRC error: block number 45 in save set DISK$ENGINEER:[SOFTWARE]SSM.BCK;1Q               Recovery unsuccessful in save set DISK$ENGINEER:[SOFTWARE]SSM.BCK;1EY               %SAVESET-I-BADCRC, Data CRC error in file DISK$ENGINEER:[SOFTWARE]SSM.BCK;1aQ               XOR error at block 52 in save set DISK$ENGINEER:[SOFTWARE]SSM.BCK;1tV               CRC error: block number 68 in save set DISK$ENGINEER:[SOFTWARE]SSM.BCK;1Q               Recovery unsuccessful in save set DISK$ENGINEER:[SOFTWARE]SSM.BCK;1rY               %SAVESET-I-BADCRC, Data CRC error in file DISK$ENGINEER:[SOFTWARE]SSM.BCK;1 Q               XOR error at block 78 in save set DISK$ENGINEER:[SOFTWARE]SSM.BCK;1_  C                 Save Set Manager V1.4 Time: 10-JUN-1999 20:22:12.74g  (                   SAVESET function: COPYK                   Primary input save set: DISK$ENGINEER:[SOFTWARE]SSM.BCK;1r#                     No journal filerD                   Output save set: DISK$ENGINEER:[SOFTWARE]COPY.SAV;#                     No journal file   0                   Final status of each save set:  E                     Save set name:  DISK$ENGINEER:[SOFTWARE]SSM.BCK;1 ;                     Unrecoverable CRC errors:             3t;                     XOR errors:                           3A  E                     Save set name:  DISK$ENGINEER:[SOFTWARE]COPY.SAV;r(                       No errors detected            I                                            Interpreting SSMgr Reports 4-9     O                    I                                                                         5tI         _________________________________________________________________l  I                                                            SSMgr Messages     E               This section contains descriptions and user actions forr'               messages issued by SSMgr.t    .         5.1 SSMgr INFORMATIONAL Level Messages  D          NOLOGFILE, Unable to create log file. Continuing operation.  F             Explanation: Attempt to create log file failed. The reasonE             for the failure follows this message. Operation continuess             without logfile.  C             Action: Correct problem indicated by secondary message.n  H          NOLOGFILEWRITE, Unable to write log file. Continuing operation.  E             Explanation: Attempt to write to the log file failed. TheoB             reason for the failure follows this message. Operation&             continues without logfile.  C             Action: Correct problem indicated by secondary message.   &         5.2 SSMgr ERROR Level Messages  B          BADCHECKSUM, Block header checksum error in file filename  C             Explanation: An unrecoverable error was found in a savetD             set block header. The data contained in the block is not             reliable.l  A             Action: Use OpenVMS BACKUP to restore the recoverable $             portion of the save set.  0          BADCRC, Data CRC error in file filename  G             Explanation: An unrecoverable error was found in a save seteG             block CRC. The data contained in the block is not reliable.r  A             Action: Use OpenVMS BACKUP to restore the recoverableo$             portion of the save set.  I                                                        SSMgr Messages 5-1                     SSMgr Messages&         5.2 SSMgr ERROR Level Messages    +          BADXOR, XOR error in file filenames  F             Explanation: The XOR block of a save set group in save setF             filename does not contain the valid XOR of the data blocksH             in that group and CRC protection is not present. The data in+             the entire group is unreliable.s  A             Action: Use OpenVMS BACKUP to restore the recoverableo$             portion of the save set.  4          INVSAVESET, filename is not a valid saveset  F             Explanation: Save set filename is not a valid OpenVMS save             set.               Action: None.e  C          MISSINGBLK, Missing block could not be regenerated in file              filename  D             Explanation: There was an unrecoverable missing block inD             save set filename and there was insufficient metadata to,             reproduce the data in the block.  @             Action: None. The data in the missing block is lost.  ,         5.3 SSMgr FATAL Level Error Messages  A          BUG, A software bug was detected at line line, file filea  8             Explanation: SSMgr detected an internal bug.  G             Action: Please submit an SPR and copies of the log file andrF             the input save sets. If this bug prevents you from copyingD             the input save sets, submit the output of BACKUP/LIST on$             those save sets instead.  3          DEVACCESS, Cannot access device devicenamet  @             Explanation: Attempts to access a save set on device#             devicename have failed.   G             Action: Verify that the path name given by the command line E             is correct, that the device is mounted, and that you have ,             privileges to access the device.  9          DUPJNLFIL, Duplicate journal file name: filename   F             Explanation: For any single SAVESET command with more thanG             one journal file being created, each journal file name mustI             be unique.  H             Action: Verify that the save set file names used are unique.           5-2 SSMgr Messages S  f      I                                                            SSMgr Messages I                                      5.3 SSMgr FATAL Level Error Messages:    4          FAILURE, SAVESET operation was unsuccessful  B             Explanation: The SAVESET operation could not complete.C             Additional messages follow indicating the nature of the              failure.  A             Action: Base user action on the immediately followingS             messages.   1          FILECLOSE, could not close file filename   @             Explanation: SSMgr could not close the save set withD             filename. The reason for the failure appears immediately             after this message.m  8             Action: Dependent on the reason for failure.  /          FILEOPEN, could not open file filename   E             Explanation: SSMgr could not open the file with filename. E             The reason for the failure appears immediately after thise             message.  8             Action: Dependent on the reason for failure.  .          FILEREAD, error reading file filename  A             Explanation: SSMgr encountered and error reading filerD             filename. The reason for the failure appears immediately             after this message.   8             Action: Dependent on the reason for failure.  A          FILERESET, could not reset to beginning of file filename   B             Explanation: SSMgr could not reset to the beginning ofA             the file filename. The reason for the failure appearsg+             immediately after this message.e  8             Action: Dependent on the reason for failure.  /          FILEWRITE, error writing file filenameS  @             Explanation: SSMgr encountered an error writing fileD             filename. The reason for the failure appears immediately             after this message.   8             Action: Dependent on the reason for failure.  I                                                        SSMgr Messages 5-3n c  I               SSMgr Messages,         5.3 SSMgr FATAL Level Error Messages    9          IDENTCOPYFAIL, Identical copy of filename failedf  E             Explanation: The user specified /IDENTICAL on the SAVESETmG             COPY command line, and the operation failed. The reason fore?             the failure appears immediately after this message.h  8             Action: Dependent on the reason for failure.  D          INSUFSPACE, Insufficient space for filename to be allocated  B             Explanation: There is insufficient space on the targetE             output disk device to allow allocation of a file the size &             required by the operation.  F             Action: Specify a device that has sufficient space to hold             the output file.  C          INVADDRESS, Invalid address in save set record in save set              filename  E             Explanation: There is a nonzero value in address field ofiG             record header in non-LBN/VBN record. The associated data is              therefore suspect.  H             Action: Use OpenVMS BACKUP to restore the save set and check              for data corruption.  @          INVBLKSIZE, Invalid block size. Valid range: 2048-65535  D             Explanation: Save set blocks may be no smaller than 20481             bytes and no larger than 65535 bytes.   E             Action: Reenter the SAVESET command and specify a /BLOCK_ ;             SIZE value in the range of 2048 to 65535 bytes.   G          INVDEVCLASS, Could not open devicename. Device must be disk orr             tape  F             Explanation: SSMgr operates on disk and tape devices only.E             The device specified by devicename was not a disk or tapeE             device.                Action: None.g  C          INVFILATTR, Invalid file attribute in save set file recordS  F             Explanation: An invalid file attribute is stored in a saveF             set file record, indicating a corrupt or otherwise invalid             save set record.  C             Action: Re-enter the SAVESET command with a /GROUP_SIZE '             value in the range 0 - 100.            5-4 SSMgr Messages :  O      I                                                            SSMgr Messages I                                      5.3 SSMgr FATAL Level Error Messages     ;          INVGRPSIZE, Invalid group size. Valid range: 0-100E  G             Explanation: Save set XOR groups may be no larger than 100.SE             A value of zero indicates no XOR should be written to theS             save set.H  G             Action: Reenter the SAVESET command with a GROUP_SIZE value "             in the range 0 to 100.  F          INVRECSIZE, Invalid save set record size in save set filename  E             Explanation: A save set record contains invalid metadata.   H             Action: Use OpenVMS BACKUP to restore the save set and check              for data corruption.  F          INVRECTYPE, Invalid save set record type in save set filename  E             Explanation: A save set record contains invalid metadata.C  H             Action: Use OpenVMS BACKUP to restore the save set and check              for data corruption.  B          INVOUTWC, Invalid output save set wild card specification  A             Explanation: The only legal wildcarding of the 'name'L>             or 'type' portions of an output save set file nameB             specification is a single '*'. Use of the '%' wildcardA             or combining the '*' with any other characters in the %             specification is illegal.E  F             Action: Re-enter the SAVESET command with a legal wildcard>             specification or with a nonwildcard specification.  8          JNLOPNERR, Error opening journal file: filename  G             Explanation: The journal file specified could not be openedI             successfully.   G             Action: Ensure that the file name is correct, that you have2H             write access to the device, and that the device is not full.  ;          JNLWRTERR, Error writing to Journal file: filenameE  H             Explanation: The journal file specified could not be written             to successfully.  H             Action: Ensure that you have write access to the device, and(             that the device is not full.  ,          MEMALLOC, Memory allocation failure  G             Explanation: SSMgr was unable to allocate necessary memory.   C             Action: Ensure sufficient resources for SSMgr operaton.f  I                                                        SSMgr Messages 5-5                     SSMgr Messages,         5.3 SSMgr FATAL Level Error Messages    A          NODEVNAM, No device name in save set specifier specifiere  E             Explanation: No device name was specified in a context ina6             which an explicit device name is required.  H             Action: Specify the device name with the save set specifier.  E          NOMERGEPHYS, AZ, is a physical save set, invalid as input to              MERGE   @             Explanation: MERGE operations cannot be performed on&             physical backup save sets.               Action: None.m  A          NOMULTITAPE, COPY/IDENTICAL output save set may not spany             multiple tapes  A             Explanation: End of tape (EOT) on the output tape was G             encountered during a SAVESET COPY/IDENTICAL operation. This.E             operation requires that the copied save set does not spanS             multiple tapes.e  D             Action: Use an output tape that has sufficient space forD             the save set or use the SAVESET COPY command without the!             /IDENTICAL qualifier.t  5          NONLOCALACC, device must be accessed locally   A             Explanation: The save set must be accessed on a local              device.   B             Action: Use only save sets that do not require network             access.   ,          REWINDFAIL, Could not rewind device  H             Explanation: Attempts to rewind the specified device failed.  A             Action: This error message is always accompanied by a$D             secondary system message. Correct the problem identified&             by that secondary message.  :          SECNOTINCR, Secondary save set not an incremental  C             Explanation: If the primary input save set in a SAVESET D             MERGE operation is an image save set, then the secondary?             input save set must be an incremental save set. See$C             Table 3-1 for a list of valid save set combinations for              MERGE.  >             Action: Retry the SAVESET MERGE operation with the1             appropriate secondary input save set.            5-6 SSMgr Messages           I                                                            SSMgr Messages I                                      5.3 SSMgr FATAL Level Error Messagess    G          TOOMANYERRS, Too many errors reading save set filename. Givinge             up.   G             Explanation: Too many errors were encountered while reading E             the save set. Probably a problem with the drive or media.r  F             Action: If the problem is with the drive, try mounting the'             media on a different drive.   A          UNSRECTYPE, Unsupported save set record type in save set              filename  <             Explanation: The save set contains a record typeD             inappropriate for the SAVESET operation being performed.  F             Action: Check that the save set being used is appropriate.  -         5.4 SSMgr WARNING level Error Mesages   >          NOUSERFILES, No user files written to output save set  C             Explanation: The output save set is empty: i.e. no userg6             files were written to the output save set.  :             Action: Ensure that this is what was expected.           5.5 Terminal Messages   A               The following informational messages are written to A               SYS$OUTPUT, SYS$ERROR, and the logfile based on the G               setting of /TERMINAL options. See the /TERMINAL qualifier A               descriptions for each of the commands in Chapter 3.y  -         5.5.1 ERRORS Option Terminal Messages   6          Block recovered from XOR in save set filename  B             Explanation: The ERRORS terminal option is enabled. AnH             unreadable block in save set filename was recovered via XOR.  <          Block recovered via read-ahead in save set filename  C             Explanation: The ERRORS terminal option is enabled. TheEE             error specified immediately above was recovered via read-E             ahead.  I                                                        SSMgr Messages 5-7F R  S               SSMgr Messages         5.5 Terminal MessagesK    A          Checksum error: block number number in save set filename5  A             Explanation: The ERRORS terminal option is enabled. AyF             checksum error was detected in block number number in save             set filename.   :          Current volume is not the next volume in this set  E             Explanation: The ERRORS terminal option is enabled. WhiletD             reading a multivolume tape set, the SSMgr has determinedF             that the currently loaded volume is not the next member of             the volume set.r  <          CRC error: block number number in save set filename  A             Explanation: The ERRORS terminal option is enabled. AsE             CRC error was detected in block number number in save setM             filename.N  7          Error recovery successful in save set filenameO  C             Explanation: The ERRORS terminal option is enabled. TheSH             error specified immediately above was successfully recovered             by SSMgr.[  '          ERRORS terminal option enabledj  G             Explanation: The ERRORS terminal option is enabled for this              SAVESET command.  :          Missing Block: number number in save set filename  A             Explanation: The ERRORS terminal option is enabled. A E             missing block was detected in block number number in saveG             set filename.   =          Read error: block number number in save set filename   A             Explanation: The ERRORS terminal option is enabled. AOF             read error was detected in block number number in save set             filename.t  3          Recovery unsuccessful in save set filename_  C             Explanation: The ERRORS terminal option is enabled. The B             error specified immediately above was not recoverable.           5-8 SSMgr Messages r         I                                                            SSMgr Messages I                                                     5.5 Terminal Messagest    <          Rewritten Block: number number in save set filename  A             Explanation: The ERRORS terminal option is enabled. AtE             rewritten block error was detected in block number numberr!             in save set filename.m  =          XOR error at block block-number in save set filenamen  B             Explanation: The ERRORS terminal option is enabled. AnE             XOR error was detected in block number number in save set              filename.   -         5.5.2 EVENTS Option Terminal Messages   '          EVENTS terminal option enableda  G             Explanation: The EVENTS terminal option is enabled for thisS             SAVESET command.            Opening file filename  H             Explanation: The EVENTS terminal option is enabled. SSMgr is1             attempting to open the file filename.   "          Output save set: filename  H             Explanation: The EVENTS terminal option is enabled. The fileG             filename has been successfully opened for use as the output              save set.A  )          Primary input save set: filenamee  H             Explanation: The EVENTS terminal option is enabled. The fileH             filename has been successfully opened for use as the primary             input save set.e  0          Resetting to beginning of file filename  C             Explanation: The EVENTS terminal option is enabled. The C             merge of an image save set with an incremental save set C             requires two passes over the incremental save set. ThistC             message indicates that SSMgr is resetting the secondaryO/             input save set for the second pass.n  H          Resuming operation on volume volume-number of save set filename  C             Explanation: The EVENTS terminal option is enabled. The G             save set filename is on a multivolume tape and operation is,4             resuming on volume number volume-number.  I                                                        SSMgr Messages 5-9                     SSMgr Messages         5.5 Terminal Messagest    $          Rewind of filename complete  G             Explanation: The EVENTS terminal option is enabled. /REWINDnG             was specified and the tape has been successfully rewound to              BOT.  2          Rewinding filename to beginning of volume  G             Explanation: The EVENTS terminal option is enabled. /REWINDo8             was specified and the tape is being rewound.  *          Scanning secondary input save set  G             Explanation: ... EVENTS ...enabled. An incremental save setnE             is being merged with an image save set. SSMgr is scanningIA             the incremental save set for file system information.t  +          Secondary input save set: filename   C             Explanation: The EVENTS terminal option is enabled. TheeE             file filename has been successfully opened for use as theo%             secondary input save set.a  D          Unable to continue writing to save set filename. Continuing             operation.  E             Explanation: The EVENTS terminal option is enabled. SSMgrrD             could not write to one of the multiple output save sets.G             SSMgr will continue the COPY or MERGE operation, writing to +             the remaining output save sets.a  *         5.5.3 LOG Option Terminal Messages  $          LOG terminal option enabled  D             Explanation: The LOG terminal option is enabled for this             SAVSESET command.   '          Processing user file: filename   E             Explanation: The LOG terminal option is enabled. The user 7             file filename is currently being processed.U               5-10 SSMgr Messagesf           I                                                            SSMgr MessagesiI                               5.6 Process Quota Exceeded (System Message)     3         5.6 Process Quota Exceeded (System Message)   I               If you see the "Process Quota Exceeded" system message, theeI               process quota exceeded is most likely PGFLQUO or DIOLM. YouiI               must rerun the SSMgr operation in a process with sufficient 4               quota to complete the SSMgr operation.                                                                              I                                                       SSMgr Messages 5-11i a                               F      _________________________________________________________________  F                                                                  Index      F      A______________________________   D______________________________  :      Account quotas                    DCL interface,  1-1        changing, 2-3(        process, 2-2                    EF        user, 2-2                       _______________________________9      Authorization Key,  2-7           Error report,  4-7         AUTHORIZEF        See OpenVMS Authorize           F______________________________  5                                        Files-11,  3-1   $      B______________________________F      BACKUP                            H______________________________  +        See OpenVMS BACKUP              HELP   F      _______________________________   I______________________________  6      Command Language Interface        Input save sets7         (CLI)                            on disks,  3-2nB        command summary, 1-2              on multivolume tape sets,/        help, 1-10                           3-3 7        qualifiers, 3-14                  on tapes,  3-2 3      Commands                          Installation @        COPY, 3-15                        before installing,  2-1E        MERGE, 3-37                       conditions for failure,  2-7eB        qualifiers, 3-14                  disk space required,  2-1C        specifiers, 3-1                   license registration,  2-1t9        VALIDATE, 3-57                    privileges,  2-1 9      COPY,  1-3, 3-15                    sample run,  2-9oB        example, 3-27, 3-29             Internationalization,  1-10*      CRC,  1-1, 4-2                    IVP6      Ctrl/T,  4-1                        example,  2-96                                          failure,  2-76                                          running,  2-7  F                                                                Index-1                   @                                           OpenVMS MESSAGE,  1-10@         L______________________________   Output save sets,  3-59         License                             on disks, 3-5ME          PAK,  2-1                          on multivolume tapes, 3-6t            registration,  2-1vI         License Management Facility       P______________________________e  A           (LMF),  1-10, 2-1               PAK (License PAK),  2-1 G         Log file, 4-8                     Process Quota Exceeded,  5-11 =                                           Purging files,  2-6 '         M______________________________ I         MERGE, 1-3, 3-37                  Q______________________________   ;          example,  3-46                   Qualifiers,  3-14l  0         MESSAGE                           Quotas  >          See OpenVMS MESSAGE                See Account quotas         MessagesI          during installation,  2-7        R______________________________ <          error level,  5-1                Registration,  2-1=          fatal level,  5-2                Release notes,  2-1i7          informational level,  5-1          option, 2-5n7          internationalization,  1-10      Reports,  4-1           listing,  5-1+          warning level,  5-7              S I         Multivolume tape sets, 3-3        _______________________________M;                                           SAVESET.LOG,  4-8L9         N______________________________   Save sets,  4-1oC         NETMBX, 1-10, 2-3                   as input to BACKUP, 1-9 G                                             Files-11 mount example, 3-8 ?         O                                   handling types, 1-4 6         _______________________________     input, 3-1B         OpenVMS, 1-1                        management policy, 1-39          Ctrl/T,  4-1                       physical, 3-1 ;          versions,  1-1, 2-1                specifiers, 3-1a6         OpenVMS AUTHORIZE, 2-3              types, 3-1/         OpenVMS BACKUP, 1-1, 3-1          SSMgrr9          image,  1-4                        benefits, 1-1pC          incremental,  1-4                  completion reports, 4-2cD          policy,  1-3                       disk space required, 2-1>          procedures,  2-4                   error reports, 4-77          strategies,  1-4                   errors, 4-2d9          time spent doing,  1-5             /FOREIGN, 1-9i@          version compatibility,  1-9        input save sets, 3-1=         OpenVMS HELP, 1-10                  installation, 2-1*9                                             log file, 4-8'<                                             privileges, 1-10           Index-2                             SSMgr (cont'd)I          purging files from previous      V______________________________f  C             versions,  2-6                VALIDATE,  1-2, 3-57, 4-1 >          recoverable errors,  4-4           example, 3-63, 4-2;          release notes,  2-1              VMScluster,  1-10n9          reports,  4-1                    VMSINSTAL,  2-3 8         SYS$SYSTEM, 2-2                     running, 2-4         System diskLI          backup,  2-4, 2-5                W______________________________:  :         T                                 Wildcards,  3-12A         _______________________________     input save sets, 3-12aD         Tape, 1-9                           journal file names, 3-13B          /FOREIGN,  3-1                     output save sets, 3-12         Tape scwitching, 3-3I         TMPMBX, 1-10, 2-3                 X______________________________o  3                                           XOR,  4-2                                                     I                                                                   Index-3 