                                   =          Save_Set_Manager_for_OpenVMS________________________ $          User and Installation Guide  "          Order Number: AA-QDKQF-TE    3          This manual contains installation and user 7          information for the Save Set Manager software.               ;          Operating Systems:            OpenVMS VAX Versions <                                        5.5-2, 6.1, 6.2 & 7.1=                                        and OpenVMS Alpha 6.1, 0                                        6.2 & 7.1  7          Software Version:             Save Set Manager 3                                        Version 1.3B           &          Digital Equipment Corporation          Maynard, Massachusetts          C    ________________________________________________________________     May 1998   8    The information in this document is subject to change=    without notice and should not be construed as a commitment 6    by Digital Equipment Corporation. Digital Equipment<    Corporation assumes no responsibility for any errors that    may appear in this document.   =    The software described in this document is furnished under >    a license and may be used or copied only in accordance with    the terms of such license.   :    No responsibility is assumed for the use or reliability;    of software on equipment that is not supplied by Digital 5    Equipment Corporation or its affiliated companies.   <    Restricted Rights: Use, duplication, or disclosure by the=    U.S. Government is subject to restrictions as set forth in <    subparagraph (c) (1) (ii) of the Rights in Technical Data6    and Computer Software clause at DFARS 252.227-7013.  9     Digital Equipment Corporation 1998 Printed in U.S.A.     All Rights Reserved.   >    DECnet, OpenVMS, VAX, VAXcluster, VMS, and the DIGITAL logo3    are trademarks of Digital Equipment Corporation.   >    This document was prepared using VAX DOCUMENT, Version 2.1.                     ; ___________________________________________________________   <                                                     Contents      < ...................................................      vii      <   Advantages  of SSMgr..............................     1-1<   SSMgr  Functions..................................     1-2<   How  SSMgr Changes Save Set Management Policy.....     1-3<   OpenVMS  Compatibility............................     1-6<    OpenVMS    BACKUP Utility ........................    1-6<    VMScluster    Support ............................    1-6<    OpenVMS    License Management Facility ...........    1-6<    Privileges    ....................................    1-6<    Internationalization    of Messages ..............    1-6<    OpenVMS    HELP Utility ..........................    1-6  
  Procedure  <   Preinstallation  Requirements and Preparations....     2-1<   License  Registration.............................     2-1<    Privileges    and Disk Space .....................    2-1<    Process    Account Quotas ........................    2-2<    User    Account Quotas ...........................    2-2<    VMSINSTAL    Requirements ........................    2-3<    Backing    Up Your System Disk ...................    2-4<   Installing  the SSMgr Software....................     2-4<    The    Installation Procedure ....................    2-4<    Error    Recovery ................................    2-7<    Installation    on V5.5-2 Systems ................    2-8<   SSMgr  Sample Installation........................     2-9<   Reporting  Product Problems.......................    2-12        <                                                          iii         
   Using SSMgr   ?  3.1  Input and Output Save Set Specifiers.............     3-1 ?  3.1.1   Input Save Sets ...............................    3-1 ?  3.1.1.1   Input Save Sets on Disk.....................     3-2 ?  3.1.1.2   Input Save Sets on Tape.....................     3-2 ?  3.1.1.3   Input Save Sets on Multivolume Tape Sets....     3-3 ?  3.1.2   Output Save Sets ..............................    3-5 ?  3.1.2.1   Output Save Sets on Disk....................     3-5 ?  3.1.2.2   Output Save Sets on Tape....................     3-5 ?  3.1.2.3   Output Save Sets on Multivolume Tape Sets...     3-6 ?  3.1.3   Files-11 Mount Example ........................    3-8 ?  3.1.4   Multiple Output Save Sets .....................    3-9 ,  3.2  Wildcards in Save Set and Journal File?       Specifiers.......................................    3-12 ?  3.2.1   Wildcard Constraints on Input Save Sets .......   3-12 ?  3.2.2   Wildcard Constraints on Output Save Sets ......   3-12 ?  3.2.3   Wildcard Constraints on Journal File Names ....   3-13 ?  3.3  SSMgr Command Language Interface.................    3-14   ?       COPY.............................................    3-15   ?       MERGE............................................    3-37   ?       VALIDATE.........................................    3-57      Interpreting SSMgr Reports  ?  4.1  Monitoring the Progress of SSMgr Operations......     4-1 ?  4.2  Completion Reporting.............................     4-2 ?  4.2.1   Normal Successful Completion ..................    4-2 6  4.2.2   Successful Completion with Save Set Condition?          Report.........................................    4-2 ?  4.2.3   Error Reporting ...............................    4-7 ?  4.2.4   Log File ......................................    4-8      SSMgr Messages  ?  5.1  SSMgr INFORMATIONAL Level Messages...............     5-1 ?  5.2  SSMgr ERROR Level Messages.......................     5-1 ?  5.3  SSMgr FATAL Level Error Messages.................     5-2 ?  5.4  SSMgr WARNING level Error Mesages................     5-7 ?  5.5  Terminal Messages................................     5-7 ?  5.5.1   ERRORS Option Terminal Messages ...............    5-7 ?  5.5.2   EVENTS Option Terminal Messages ...............    5-9 ?  5.5.3   LOG Option Terminal Messages ..................   5-10          ?  5.6  Process Quota Exceeded (System Message)..........    5-11           ?  3-1     A Files-11 Mount ..............................    3-8   ?  3-2     COPY Command ..................................   3-27   ?  3-3     COPY Command with Multiple Output Save Sets ...   3-27   1  3-4     COPY Command with IDENTICAL and OVERRIDE ?          Qualifiers on Save Set with Errors.............   3-29   2  3-5     COPY with Wildcarding, Journaling, and No?          Logfile........................................   3-30   ?  3-6     COPY with /JOURNAL and /TERMINAL Qualifiers ...   3-33   6  3-7     COPY with /BLOCK_SIZE, /GROUP_SIZE, and /FULL?          Qualifiers.....................................   3-34   ?  3-8     MERGE Command .................................   3-47   6  3-9     MERGE Command with /FULL, /LOG, and /TERMINAL?          Qualifiers.....................................   3-48   6  3-10    MERGE Command with /FULL, /TERMINAL, /CHECKS,?          and CRC Qualifiers.............................   3-52   2  3-11    MERGE Command with Journaling on All Save?          Sets...........................................   3-56   ?  3-12    VALIDATE Command ..............................   3-63   ?  3-13    VALIDATE with /Full Qualifier .................   3-63   ?  3-14    VALIDATE All Save Sets in Directory ...........   3-65   ?  3-15    VALIDATE with Journal Qualifier ...............   3-67   ?  3-16    VALIDATE with Terminal Classes Enabled ........   3-68   ?  4-1     Ctrl/T Report Example .........................    4-1   ?  4-2     Normal Successful Completion Report ...........    4-3   ?  4-3     Save Set Condition Report .....................    4-5   ?  4-4     Error Report ..................................    4-7   ?  4-5     Log File ......................................    4-9   ?                                                               v          2  2-1     Process Account Quotas for the Installing?          Account........................................    2-2   ?  3-1     SSMgr Commands and Qualifiers .................   3-14                  > ______________________________________________________________  ?                                                         Preface         7    The The Save Set Manager User and Installation Guide <    describes the procedures for configuring, installing, and3    operating the Save Set Manager (SSMgr) software.   	  Audience   6    This manual is intended primarily for use by system.    managers, operators, and workstation users.    '    This manual is organized as follows:   0    Chapter 1   Provides an overview of the SSMgr  0    Chapter 2   Explains how to install the SSMgr  >    Chapter 3   Describes the command language interface of the                SSMgr  &    Chapter 4   Describes SSMgr reports  >    Chapter 5   Lists the error messages generated by the SSMgr  
  Documents  3    The following table lists documents that contain '    information related to this product:   >    ___________________________________________________________>    Document_Title____________________________Order_Number_____  8    The Save Set Manager for OpenVMS User     AA-QDKQx-TE    and Installation Guide   ?                                                             vii          >    ___________________________________________________________>    Document_Title____________________________Order_Number_____  8    OpenVMS System Management Utilities       AA-PV5Px-TK    Reference Manual: A-L  8    OpenVMS License Management Utility        AA-PVXUx-TK>    Manual_____________________________________________________    Conventions  5    The following conventions are used in this manual:   <    boldface    Boldface type indicates the first instance of<    type        terms being defined in text, in the glossary,                or both.   :    italic      Italic type indicates emphasis and complete=    type        manual titles. In the glossary, italic type is 6                also used to indicate cross-references.             ?                                                               1 > ______________________________________________________________  ?                                                    Introduction     4    The Save Set Manager for OpenVMS[TM] (SSMgr) is a9    layered software product that reduces the time used to ;    create OpenVMS BACKUP save sets, while providing greater &    flexibility in save set management.  :    OpenVMS BACKUP users have had a rich set of options and:    a high level of data integrity available at the cost of1    greater down time during the backup operation.   9    SSMgr runs as a post-processor on save sets created by =    BACKUP, or other storage management software that conforms =    to the BACKUP save set structure. It allows some functions 6    that are currently done online with BACKUP, such as>    checking the integrity of save sets, making multiple copies>    of a save set, and XOR or cyclic redundancy checking (CRC),9    to be done offline using SSMgr. SSMgr does not replace 6    OpenVMS BACKUP for creating or restoring save sets.  >    SSMgr is supported for OpenVMS VAX[TM] Versions 5.5-2, 6.1,:    6.2 & 7.1 and for OpenVMS Alpha[TM] Versions 6.1, 6.2 &<    7.1. SSMgr supports a DCL interface and all disk and tape-    technologies supported by OpenVMS systems.     Advantages  of SSMgr   >    Using SSMgr to manage your save sets provides the following    benefits:  :    o  You can run OpenVMS BACKUP with fewer time-consuming:       data integrity options, such as /VERIFY, to complete=       the operation with minimal down time. Once you have the >       backup save set, you perform the validation and addition5       of data integrity features offline using SSMgr.   >    o  You can reduce the number of full backups in your backup=       cycle by substituting incremental backups and using the *       save set merge feature of the SSMgr.  ?                                               Introduction  1-1          :    o  Restore time is greatly reduced, because you can use=       SSMgr to merge incremental backups into image save sets =       to maintain a current image save set at all times. This ;       process replaces the practice of using OpenVMS BACKUP =       to restore an image save set plus many incremental save        sets.   >    o  SSMgr does not require access to any data outside of its=       input save sets to run, so it can be run on any OpenVMS ;       system that can directly access those save sets or to        which they can be moved.  ;    o  You can transfer save sets between tape technologies.   <    o  The data integrity of SSMgr save sets is comparable to:       save sets created with other OpenVMS utilities using       full data checking.   ;    o  You gain additional flexibility in managing your save 8       set files by using the SSMgr commands for save set,       validation, copy, and merge functions.  <    o  You can monitor the integrity of archived save sets to;       determine how badly the media has degraded over time, :       and you can use SSMgr to reconstruct and restore the       save sets to fresh media.   <    o  You can create OpenVMS BACKUP Journal Files (.BJL) for#       previously created save sets.   4    o  You can create up to five copies of a save set       simultaneously.   ;    SSMgr performs its operations on save sets that strictly <    conform to the OpenVMS BACKUP save set format for disk or=    tape devices. You can use save sets and journal files that 9    have been created by SSMgr as input to OpenVMS BACKUP.     SSMgr  Functions   *    SSMgr performs the following functions:  9    o  VALIDATE-Validates that all data blocks in the save <       set can be read without error. Validation includes the:       verification that any CRC or XOR protection recorded:       in the save set is consistent with the data they are<       protecting. This command may eliminate your need for a/       /VERIFY pass when you run OpenVMS BACKUP.   
  Introduction          >       Tapes degrade over time, and the VALIDATE command allows:       you to monitor the degradation of your archived save9       sets so that you can detect that degradation early, =       thus minimizing data loss. If the save sets contain XOR >       redundancy protection and degradation is detected early,-       you may avoid any consequent data loss.   <    o  COPY-Used to make a copy of a save set, to reconstruct=       data that has been found to be degenerated by VALIDATE, 4       or to transfer a save set to a different media8       technology. You also can change the format of save;       sets, such as block or group size, and you can insert 7       or remove XOR and CRC protection in the save set.   <       Using OpenVMS BACKUP, if you wished to create multiple<       copies of a save set, such as a local copy and a vault;       copy, you had to perform your online backup operation 9       multiple times. With SSMgr, you need to perform the 9       OpenVMS BACKUP operation only once, after which you ;       can produce up to 5 copies offline with a single COPY        operation.  5    o  MERGE-Allows for a more flexible backup policy, =       including merging incremental save sets into image save <       sets to create a fully restorable save set, or merging>       incremental save sets into each other. The MERGE command;       can be used to reduce the frequency of image save set <       operations (also called full backup) done with OpenVMS
       BACKUP.   >    Both COPY and MERGE commands include the option to validate;    their input save sets while performing their operations.   .  How  SSMgr Changes Save Set Management Policy  >    A common BACKUP policy is to perform an image backup once a<    week and incremental backups all other days. In the worst:    case scenario, a disk could be lost on the seventh day,;    after the last incremental backup had been performed and 9    before the next image backup. To restore the disk, the 9    image save set must first be restored and then the six =    incremental save sets applied in sequence. The time needed >    to restore the data is longer if the period of time between    image backups is longer.   ?                                               Introduction  1-3n _  _        Backup Strategies  9    SSMgr allows you to select alternative policies as the-<    best backup strategy for your installation. The following=    two different policies using the SSMgr MERGE command could ;    dramatically reduce the time needed to restore the disk:V  =    o  Perform an image backup on day one. Each following day,6=       perform an incremental backup and merge the incrementalp:       save set for the day with the image backup save set,<       creating a new image save set. Repeat this process for9       each subsequent day, merging that day's incremental >       save set with the image save set created by the previous:       day's merge operation until you wish to perform your       next image backup.  9       This strategy results in a single large save set tos(       restore in the event of data loss.  ;    o  Perform an image backup on day one and an incrementaln4       backup on day two. Perform another incremental5       backup on day three and merge its save set with 8       the incremental save set from day two to produce a6       cumulative incremental save set. Repeat for each9       subsequent day, merging that day's incremental savec:       set with the cumulative incremental save set created=       by the previous day's merge operation until you wish toi%       perform your next image backup.   9       This strategy results in one image save set and onei:       incremental save set to restore in the event of data       loss.s  9    Merging an incremental save set with an image save set 6    requires two SSMgr passes over the incremental save8    set and one pass over the image save set. Merging two9    incremental save sets requires one pass over each saveO:    set. Therefore, depending upon the relative size of the=    image and incremental save sets, you may prefer to use thet,    second strategy instead of the first one.        
  Introduction  _  _    )    Controlling Image Backup Save Set Size_  :    Image save sets created by SSMgr merge operations of an;    image save set and one or more incremental save sets can.=    grow to be larger than the backed-up disk's capacity. Note.<    that this same condition occurs when using OpenVMS BACKUP>    to restore an image save set and all subsequent incremental
    save sets.3  >    The increase in size in both cases is due to directories or>    files on the volume that were deleted or renamed subsequent;    to the original image backup. Both BACKUP and SSMgr takeO7    a conservative approach to the files that used to be >    contained in those deleted or renamed directories and their:    subdirectories; BACKUP does not delete these files when=    restoring an incremental save set that shows the directory >    deleted, and SSMgr retains these files when merging in such    an incremental save set.r  9    Therefore, SSMgr MERGE operations do not eliminate thea>    need for periodic image backups, but by using MERGE you can9    generally increase the interval between image backups.t  ;    Other Ways to Reduce the Time Spent on BACKUP Operationsu  7    Time spent on online OpenVMS BACKUP operations couldY8    be further reduced by omitting the calculation of CRC;    protection in BACKUP, and adding in such protection in at;    COPY or MERGE operation in SSMgr. CRC protection and XORe=    redundancy were originally put into BACKUP as a protective ;    mechanism against the relatively poor quality tapes (and <    tape drives) of previous storage technologies; their main9    use on modern tape systems is to protect against long- 7    term degradation of tape media. CRC calculations are 8    compute intensive and can reduce BACKUP throughput on=    less powerful VAX systems. XOR redundancy blocks can limit.<    BACKUP throughput on slower tape technologies such as QIC    or RDAT..  ;    Omitting these protections in BACKUP save set operations.=    results in greater throughput during the backup operation.t=    These protections can then be inserted during a subsequent.9    SSMgr COPY or MERGE operation. In the event that SSMgrt<    detects an error on a recently produced save set, you can    run OpenVMS BACKUP again.  ?                                               Introduction  1-5.    -      OpenVMS  Compatibilityx  ;    The following general comments apply to using SSMgr witht    OpenVMS systems..    OpenVMS    BACKUP Utility  <    Save sets created by any version of OpenVMS BACKUP, up to<    and including V7.0, are accepted by SSMgr. Also, all save<    sets created by SSMgr are valid inputs to all versions of:    OpenVMS BACKUP. All save sets created by any version of<    SSMgr are accepted by SSMgr, but not all SSMgr operations;    are valid for all types of save sets. For example, while 9    SSMgr can copy physical save sets, it cannot merge two     physical save sets.  9    Unlike OpenVMS BACKUP, output tapes used by SSMgr mustE:    be initialized before use and all tapes must be mounted"    without the /FOREIGN qualifier.    VMScluster    Support  =    SSMgr runs as a single image on a single node and does not./    include any explicit VMScluster[TM] support.c  '  OpenVMS    License Management Facility   >    SSMgr uses the OpenVMS License Management Facility (LMF) to9    determine if a node is authorized to use the software.4    Privilegesp  <    SSMgr requires no privileges other than TMPMBX and NETMBX%    in order to perform its functions..  $  Internationalization    of Messages  ;    The OpenVMS MESSAGE utility is used by the SSMgr Command <    Language Interface (CLI) to allow internationalization of    error and status messages.s    OpenVMS    HELP Utility  9    An OpenVMS HELP utility file that describes the CLI is <    provided on the SSMgr distribution media and is installed<    with the software. Use the HELP SAVESET command to access$    this feature from the DCL prompt.  
  Introductions .  .        ?                                                               2.> ______________________________________________________________  ?                                          Installation Procedure.    /  Preinstallation  Requirements and Preparationsn  5    This section discusses the system requirements andC<    preparations necessary for installing the SSMgr software.  5    The SSMgr kit includes online and hardcopy releaseQ7    notes. Digital strongly recommends that you read the 9    release notes before proceeding with the installation. 6    The release notes for printing to hardcopy are in a5    file named SYS$HELP:SAVESETUA013_RELEASE_NOTES.PS.s/    The online release notes are in a file namedG'    SYS$HELP:SAVESETUA013.RELEASE_NOTES..  <    SSMgr requires that your system to be running OpenVMS VAX=    Versions 5.5-2, 6.1, 6.2 and 7.1 or OpenVMX Alpha 6.1, 6.2R<    and 7.1. Installation may only be completed on a per-node	    basis..    License  Registration  ;    Before you install and run SSMgr on a new node, you mustK>    first register a License Product Authorization Key (License4    PAK) using the License Management Facility (LMF).  9    For complete information on using LMF, see the OpenVMS.%    License Management Utility Manual..    Privileges    and Disk Space6  <    To install the SSMgr software, you must be logged into an7    account that has either of the following privileges:.      o  SETPRV      o  CMKRNL, WORLD, and SYSPRVQ  ?                                     Installation Procedure  2-1  s       :    SSMgr requires 3500 free disk blocks on the system disk=    to install. To determine the number of free disk blocks onl;    your system disk, enter the following command at the DCLo
    prompt:      $ SHOW DEVICE SYS$SYSDEVICE    Process    Account Quotas  <    The account you use to install SSMgr must have sufficient>    quotas to enable you to perform the installation. Table 2-1>    summarizes the process quotas required for the installation:    account. Unless you are installing SSMgr in your system>    account, these process quotas are in addition to the normal>    process quotas and are necessary to ensure the proper level     of resources for your system.  ?    Table_2-1__Process_Account_Quotas_for_the_Installing_Account   >    Process_Account__Quota_____________________________________      ASTLM            10      BIOLM            10      BYTLM            4000      DIOLM            10      ENQLM            20      FILLM            300e      PRCLM            2       TQLM             10  >    PGFLQUOTA________10000_____________________________________    User    Account Quotass  =    User account quotas are stored in the SYSUAF.DAT file. Use :    the OpenVMS AUTHORIZE utility to verify and change user=    account quotas. First set your directory to SYS$SYSTEM and 9    then run AUTHORIZE, as shown in the following example:       $ SET DEFAULT SYS$SYSTEMs    $ RUN AUTHORIZE    UAF>     Installation  Procedure g  b    =    At the UAF> prompt, enter the SHOW command with an accounto3    name to check a particular account. For example:_      UAF> SHOW SMITH  =    To change a quota, enter the MODIFY command. The following <    example changes the FILLM quota for the SMITH account and    then exits from the utility:       UAF> MODIFY SMITH /FILLM=50    UAF> EXIT  9    Any account from which SSMgr is to be run must have at_:    least the TMPMBX and NETMBX privileges. Use the OpenVMS<    AUTHORIZE utility to determine whether users who will run*    SSMgr have the privileges they require.  8    After you exit from the AUTHORIZE utility, the system;    displays messages indicating whether or not changes were_>    made. Once the changes have been made, you must log out and2    log in again for the new quotas to take effect.  <    For more information on modifying account quotas, see the=    description of the AUTHORIZE utility in the OpenVMS Systemi.    Management Utilities Reference Manual: A-L.    VMSINSTAL    Requirements  <    When invoked, VMSINSTAL first verifies that the following$    actions have already taken place:  7    o  You have set your default device and directory to        SYS$UPDATE._  /    o  You are logged into a privileged account._  0    o  You have adequate quotas for installation.  %    o  DECnet[TM] software is running.   ;    o  You have determined if any users are logged in to thec
       system.t  =    If VMSINSTAL detects any problems during the installation,d:    it notifies you and prompts you to continue or stop the8    installation. In some instances, you can enter YES to:    continue. Enter NO if you need to stop the installation    and correct a problem.h  ?                                     Installation Procedure  2-3e c  t      Backing    Up Your System Diska  <    At the beginning of the installation procedure, VMSINSTAL<    prompts you about the backup of your system disk. Digital6    recommends that you back up your system disk before    installing any software.o  9    Use the backup procedures that are established at your <    site. For details on performing a system disk backup, see:    the section on the BACKUP utility in the OpenVMS System-    Management Utilities Reference Manual: A-Le    Installing  the SSMgr Softwared  :    This section contains a step-by-step description of the    installation procedure.    The    Installation Procedure  ;    The SSMgr installation procedure consists of a series ofi>    questions and informational messages. See Section 2.4 for a    sample installation.u  :    To start the installation, invoke the VMSINSTAL command:    procedure from a privileged account, such as the SYSTEM5    account. VMSINSTAL is in the SYS$UPDATE directory.k  9    To abort the installation procedure at any time, enterf<    Ctrl/Y. When you enter Ctrl/Y, the installation procedure8    deletes all files it has created up to that point and4    exits. You can then start the installation again.      1. Invoke VMSINSTAL.a  >       @SYS$UPDATE:VMSINSTAL saveset-name device-name OPTIONS N         Where:  >       o  saveset-name-The installation name for the component.4          Use the installation name SAVESETUA013 when          installing SSMgr.  =       o  device-name-The name of the device on which you planr=          to mount the media. For example, MUA0: is the devicer:          name for a tape drive. It is not necessary to use=          the console drive for this installation. However, ifd=          you do use the console drive, you should replace any =          media you removed once the installation is complete.     Installation  Procedure    e    5       o  OPTIONS N-This is an optional parameter thato8          indicates you want to be prompted to review the;          release notes. If you do not include the OPTIONS Ni9          parameter, VMSINSTAL does not issue this prompt.d  >          You should review the release notes before proceeding>          with the installation in case they contain additional7          information about the installation. If you aref>          restarting the installation and have already reviewed>          the release notes, you do not need to specify OPTIONS          N.t  >       The following example invokes VMSINSTAL to install SSMgr:       from tape drive MUA0: and shows the system response.=       This example uses the OPTIONS N release note parameter.e  :       $ @SYS$UPDATE:VMSINSTAL SAVESETUA013 MUA0: OPTIONS N  @             VAX/VMS Software Product Installation Procedure V7.0  !       It is 27-MAY-1996 at 07:03.i  5       Enter a question mark (?) at any time for help.v  9       If you do not supply either the product name or ther=       device name, VMSINSTAL prompts you for this information 9       later in the installation procedure. VMSINSTAL does ;       not prompt you for any options, so be sure to include ;       OPTIONS N on the VMSINSTAL command line to access the ,       release notes during the installation.      2. Confirm system backup.  D       * Are you satisfied with the backup of your system disk [YES]?  7       You should always back up your system disk before ;       performing an installation. If you are satisfied with ;       the backup of your system disk, press the Return key.s:       Otherwise, enter NO to discontinue the installation.=       After you back up your system disk, you can restart thed       installation.e  $    3. Select a release notes option.         Release Notes Options:           1.  Display release notes        2.  Print release notes        3.  Both 1 and 2n        4.  None of the above  ?                                     Installation Procedure  2-5  e  o           * Select option [2]:  <       If you specified OPTIONS N when you invoked VMSINSTAL,=       you are now asked to choose one of the four options fors"       reviewing the release notes.  <       If you select option 1, VMSINSTAL displays the release8       notes immediately on the console terminal. You can;       terminate the display at any time by entering Ctrl/C.h  ;       If you select option 2, VMSINSTAL prompts you for then3       name of the print queue that you want to use:          * Queue name [SYS$PRINT]:   :       You can press the Return key to send the file to the:       default output print device or you can enter another       queue name.   <       If you select option 3, VMSINSTAL displays the release8       notes immediately on the console terminal and then;       prompts you for a queue name for the printed version.e  >       Select option 4 if you have already reviewed the release0       notes and are restarting the installation.  6       Next, VMSINSTAL displays the following question:  :       * Do you want to continue the installation [N]?: YESb       %VMSINSTAL-I-RELMOVED, The product's release notes have been successfully moved to SYS$HELP.  >       Enter YES to continue the installation. Otherwise, press;       the Return key. In either case, the release notes ares1       copied to a file in the SYS$HELP directory.f      4. Purge files.  G       * Do you want to purge files replaced by this installation [YES]?d  6       You have the option to purge files from previous3       versions of SSMgr that are superseded by thisr;       installation. Purging is recommended; however, if you <       need to keep files from the previous version, enter NO"       in response to the question.  :    5. Choose the Installation Verification Procedure (IVP)
       option.k  @       * Do you want to run the IVP after the installation [YES]?  2       The IVP for SSMgr checks to be sure that the<       installation is successful. It is recommended that you       run the IVP.    Installation  Procedure d  6    3       After SSMgr is installed, you can run the IVPm<       independently to verify that the software is available9       on your system. You might need to run the IVP aftere9       a system failure to make sure that users can accessm9       SSMgr. You can run the IVP independently by runningh       SYS$TEST:SAVESET$IVP.COM.r  (    6. Answer Authorization Key Question.  N       * Does this product have an authorization key registered and loaded? YES  9       If you do not have a license registered and loaded,i;       answer NO and the installation will continue, but thea8       IVP will not run, regardless of how you answer the:       previous IVP question. After registering and loading>       the authorization key, you can run the IVP independently&       by how you answer the questions.  $    7. End of installation procedure.  B          Installation of Save Set Manager V1.3B completed at 14:52  *          VMSINSTAL procedure done at 14:52  <       These lines are displayed when the entire installation       procedure is complete.  9       You now can log out of the privileged account. Notet>       that VMSINSTAL deletes or changes entries in the process>       symbol tables during the installation. Therefore, if you>       are going to continue using the system manager's account;       and you want to restore these symbols, you should loge       out and log in again.r    Error    Recovery  5    If errors occur during the installation procedure, ;    VMSINSTAL displays failure messages. If the installation -    fails, you will see the following message:   O    %VMSINSTAL-E-INSFAIL, The installation of Save Set Manager V1.3B has failed.e  1    If the IVP fails, you will see these messages:r  I    The Save Set Manager V1.3B Installation Verification Procedure failed.c  G    %VMSINSTAL-E-IVPFAIL, The IVP for Save Set Manager V1.3B has failed.P  9    Errors can occur during the installation if any of thet    following conditions exist:  0    o  The operating system version is incorrect.  ?                                     Installation Procedure  2-7          6    o  Quotas necessary for successful installation are       insufficient.   =    o  System parameter values for successful installation arem       insufficient.e  >    o  An image mismatch error is issued while running the IVP.  "  Installation    on V5.5-2 Systems  =    OpenVMS images created using DEC C, such as SSMgr, require 8    the existence of compatible run time libraries on the9    system on which they are installed. If you do not haven;    the DEC C components kit installed, or you have an older :    DEC C components kit installed, attempting to run SSMgr.    will result in one of the following errors:  7    1)  %DCL-W-ACTIMAGE, error activating image DECC$SHRa,        -CLI-E-IMAGEFNF, image file not found6        $1$DIA0:[SYS14.SYSCOMMON.][SYSLIB]DECC$SHR.EXE;  :    2)  %DCL-W-ACTIMAGE, error activating image CMA$TIS_SHR"         -CLI-E-IMGNAME, image file:        $3$DUA0:[SYS9.SYSCOMMON.][SYSLIB]CMA$TIS_SHR.EXE;2-A         SYSTEM-F-SHRIDMISMAT, ident mismatch with shareable imagep  ;    If your system is running OpenVMS Version 5.5-2, you mayo;    see one of these mismatch errors. You must install AACRTe:    from the SSMgr installation kit to clear this error, or)    upgrade to a later version of OpenVMS.n  =       _______________________ Caution _______________________   6       Be sure that you carefully read the installation;       information for AACRT before installing the software;a5       you may choose to not install SSMgr until afterr5       upgrading to later version of OpenVMS software.e  <       ______________________________________________________  <    For descriptions of the error messages generated by these6    conditions, see the OpenVMS documentation on system6    messages, recovery procedures, and OpenVMS software6    installation. If you are notified that any of these>    conditions exist, you should take the appropriate action as<    described in the message. For information on installation!    requirements, see Section 2.1.S    Installation  Procedure g  .      SSMgr  Sample Installationl  <    This section contains a sample installation of SSMgr. The8    sample shows an installation for a system that had no:    previous version of the SSMgr software installed. After>    installation, a sample run of the Installation Verification    Procedure (IVP) is shown.  9    $ @sys$update:vmsinstal savesetUA013 disk$user:[ELVIS]   ;    OpenVMS VAX Software Product Installation Procedure V7.0       It is 18-JUL-1996 at 10:14.  2    Enter a question mark (?) at any time for help.  G    %VMSINSTAL-W-NOTSYSTEM, You are not logged in to the SYSTEM account.lA    %VMSINSTAL-W-ACTIVE, The following processes are still active:t       UCX$NTPD     DECW$SERVER_0t     UCX$TFTP_BG8     DECW$MWM     VUE$ELVIS_2a     VUE$ELVIS_3      VUE$ELVIS_4r     VUE$ELVIS_5      DECW$TE_0068	     ELVISe+    * Do you want to continue anyway [NO]? yiC    * Are you satisfied with the backup of your system disk [YES]? yt  ,    The following products will be processed:        SAVESET V1.3B  3    Beginning installation of SAVESET V1.3B at 10:15n  9    %VMSINSTAL-I-RESTORE, Restoring product save set A ...sN    %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.  C     Copyright Digital Equipment Corporation 1994, 1995.  All rights     reserved.  E    %SAVESET-I-VMSOK, Installing SAVESET V1.3B on OpenVMS Version V7.0 F    * Do you want to purge files replaced by this installation [YES]? y?    * Do you want to run the IVP after the installation [YES]? y_  ?                                     Installation Procedure  2-9          )            Product:      SAVE-SET-MANAGER             Producer:     DEC            Version:      1.3$            Release Date: 24-JUL-1996  I    * Does this product have an authorization key registered and loaded? y 9    %VMSINSTAL-I-RESTORE, Restoring product save set B ...n  /     The Save Set Manager for OpenVMS User Guide 5     has been moved to SYS$HELP:SAVESET_USER_GUIDE.PS.i  Q    %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...S  -    This is the SAVESET IVP command procedure.e      $ saveset validate blue.bck!    ERRORS terminal option enabledS!    EVENTS terminal option enabledyR    Primary input save set ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]BLUE.BCK;1 opened:      Save Set Manager V1.3B  Time: 18-JUL-1996 10:16:50.03  !        SAVESET function: VALIDATE P        Primary input save set: ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]BLUE.BCK;1          No journal file%        Final status of each save set:KJ          Save set name:  ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]BLUE.BCK;1     No errors detected       $ saveset validate yellow.bck!    ERRORS terminal option enabledD!    EVENTS terminal option enabledgT    Primary input save set ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]YELLOW.BCK;1 opened9      Save Set Manager V1.3B Time: 18-JUL-1996 10:16:51.80R  !        SAVESET function: VALIDATE R        Primary input save set: ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]YELLOW.BCK;1          No journal file%        Final status of each save set:rL          Save set name:  ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]YELLOW.BCK;1     No errors detected  "    $ saveset copy blue.bck red.bck!    ERRORS terminal option enabledy!    EVENTS terminal option enableduR    Primary input save set ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]BLUE.BCK;1 openedI    Output save set ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]RED.BCK; openedu7    Save Set Manager V1.3B Time: 18-JUL-1996 10:16:53.88r    Installation   Proceduret h  o            SAVESET function: COPYeP        Primary input save set: ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]BLUE.BCK;1          No journal fileG        Output save set: ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]RED.BCK;_          No journal file%        Final status of each save set: J          Save set name:  ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]BLUE.BCK;1     No errors detectedH          Save set name:  ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]RED.BCK;     No errors detected  0    $ saveset merge blue.bck yellow.bck green.bck!    ERRORS terminal option enableda!    EVENTS terminal option enabledsR    Primary input save set ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]BLUE.BCK;1 openedO    Secondary input save set ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]YELLOW.BCK;1e	    openedeK    Output save set ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]GREEN.BCK; openeds7    Save Set Manager V1.3B Time: 18-JUL-1996 10:16:56.18e          SAVESET function: MERGEP        Primary input save set: ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]BLUE.BCK;1          No journal fileT        Secondary input save set: ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]YELLOW.BCK;1          No journal fileJ        Output save set: ELVBIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]GREEN.BCK;          No journal file%        Final status of each save set:tJ          Save set name:  ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]BLUE.BCK;1     No errors detectedL          Save set name:  ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]YELLOW.BCK;1     No errors detectedJ          Save set name:  ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]GREEN.BCK;     No errors detected  @    The SAVESET IVP command procedure has successfully completed.4     Installation of SAVESET V1.3B completed at 10:16  %     VMSINSTAL procedure done at 10:17s          ?                                    Installation Procedure  2-11l e  e      Reporting  Product Problems  8    If you encounter a problem while using this software,:    report it to Digital Customer Services in the U.S.A. 1-;    800-354-9000. In other countries, report it through your     usual support channels.                                                                              Installation   ProcedureE t  ]        ?                                                               3e> ______________________________________________________________  ?                                                     Using SSMgrt    :    This chapter describes how to use SSMgr, from preparing5    save sets to using the command language interface.s  &  Input  and Output Save Set Specifiers  8    SSMgr operates on save sets. Each SSMgr command takes9    at least one input save set as a parameter. Some SSMgra>    commands create output save sets. Input save sets may be on>    disk or tape, and SSMgr can create output save sets on disk<    or tape. OpenVMS BACKUP defines several modes under which>    save sets may be created. Three of those save set types are&    fully supported by SSMgr. They are:  =    o  Image save set-This also is called a full backup. It is ;       a functionally equivalent copy of an entire volume or        volume set.-  <    o  Incremental save set-This save set contains files that=       were created or modified since the last save operation..  =    o  Selective-This also is called a file-oriented save set.r;       It is a collection of files saved for some particularn
       reason.e  >    Physical save sets (copies of entire volumes) are supported9    by SSMgr for VALIDATE and COPY operations, but not for     MERGE operations.    Input    Save Setsa  ;    Input save sets may have been created by OpenVMS BACKUP,r8    by SSMgr, or by some other entity that creates valid,;    OpenVMS save sets. For SSMgr to operate on an input savet9    set, the device on which that save set resides must be <    mounted Files-11 (that is, not mounted /FOREIGN), must be<    accessible by the process performing the SSMgr operation,'    and must not require network access.s  ?                                                Using SSMgr  3-1t i  a    :    A save set is contained in a file whose contents have a:    well-defined structure. A save set file may reside on a<    disk, a bound volume set, a single tape, or a multivolume;    tape set. SSMgr does not validate, copy, or merge disks,e<    tapes, or files. The units of operation are save sets. In;    order for SSMgr to operate on these save sets, the files 8    containing them must be accessible in the appropriate=    manner. The following sections describe how to ensure thatT<    SSMgr can appropriately access input and output save sets0    that are contained in files on various media.    Input      Save Sets on Diskd  7    SSMgr can read save sets on any disk that is locallys>    connected and mounted Files-11. The process wishing to read;    those files must be suitably privileged for read access.e>    The disk may be a single disk volume or a bound volume set.  =    Standard OpenVMS defaults apply in specifying the pathnamee<    of the file containing the save set. That is, the default6    directory specification is assumed unless otherwise6    specified. If more than one input save set is being8    specified (such as the primary input save set and the;    secondary input save set in a MERGE operation), the saveS:    sets may be on the same or different devices, or in the!    same or different directories.l  8    For the use of wildcards in specifying pathnames, see    Section 3.2    Input      Save Sets on Tape   9    Input save sets may be located on magnetic tape. SSMgro;    can read save sets on any tape that is locally connectedo=    and mounted Files-11. SSMgr will always open any tape filed=    containing a save set read only. It does not matter if thed<    tape is write-locked or not. In mounting a tape Files-11,8    the tape label must be specified, or the /OVERRIDE=ID(    qualifier used on the $MOUNT command.  >    Tape are sequential devices. SSMgr will begin searching for<    specified file at the current position on the tape unless=    the /REWIND qualifier is specified on the $SAVESET commandp<    line. If /REWIND is specified, SSMgr will first rewind to.    BOT and then search for the specified file.  
  Using  SSMgru o  s    <    If there is more than one input save set on tape (such as>    the primary input save set and the secondary input save set<    in a MERGE operation), each must be on a different volume)    and mounted in a different tape drive.n  .  Input      Save Sets on Multivolume Tape Sets  3    A file containing a save set may span tapes in ae;    multivolume tape set. If that is so, the tapes must have ;    been mounted in a manner that allows continuation to thet<    next tape in the set. There are several factors that need    to be considered.  =    Tape switching of Files-11-mounted tapes is handled by thet<    OpenVMS magnetic tape ancillary control process (MTAACP),<    which is part of the OpenVMS operating system, not SSMgr.=    The MTAACP performs a number of checks on the continuationh>    volume that is loaded into the tape drive, be it by a human=    or by a mechanical loader. Two checks that are significante<    for input save sets that span tapes are the label (volume8    identifier) check and the set id (fileset identifier)	    check.a  ;    Multivolume tape sets that are created by OpenVMS BACKUP 8    or by other OpenVMS utilities follow a canonical tape9    labeling scheme if the creator of the multivolume taper=    set does not explicitly specify the tape labels to be used     for continuation tapes.  8    Labels generated for continuation tapes fill the six-8    character volume identification field. The first four<    characters of the field contain the first four characters=    of the previous volume in the volume set. (If the label is,<    less than four characters, the volume identifier field is;    padded with underscores.) The fifth and sixth characters 6    contain the relative volume number for that reel or9    cartridge in the volume set. For example, if the firste<    tape has a label of ABCDEF, the second and third would be;    labeled ABCD02 and ABCD03. If the first tape has a labelr;    of AB, the second and third would be labeled AB__02  andh
    AB__03.  ;    If SSMgr will be processing an input save set that spansh6    tapes (whether it is an operation on a single large9    save set or an operation that processes many save setsi8    through the use of wildcards and the /ALL qualifier),  ?                                                Using SSMgr  3-3  t  u    8    the multivolume set must be appropriately mounted for;    continuation. If the labeling of the continuation volumen<    does not fit the labeling scheme recognized by MTAACP, it=    will not mount and make available that volume for reading.t=    If the multivolume tape set follows the canonical labelingu;    scheme described above, it will mount and make availableV=    that volume for continued processing. If not, the tape set >    must be mounted specifying the names of each tape volume in    the set. For example:  2        $ MOUNT MUA0: BEATLE,JOHN,PAUL,GEORGE,RINGO  >    The use of the /OVERRIDE=ID qualifier on the $MOUNT command=    will override the label check on the first volume only. Its=    does not carry over to continuation volumes. Therefore, ifz<    the labels are like the ones in the previous example, the    following $MOUNT command:           $ MOUNT/OVERRIDE=ID MUA0:  6    would result in the volume BEATLE being mounted and;    processed, but when the tape switch occurred, the MTAACP :    would send OPCOM messages asking for relative volume 2,=    BEAT02, to be mounted. At this point, the operation cannotp>    continue, because the MTAACP will accept nothing other than    a tape labeled BEAT02.   3    A second check made by the MTAACP is the filesetf;    identifier. In some instances, continuation volumes thata=    are initialized by OpenVMS BACKUP may not be recognized by <    the MTAACP as the correct next volume, even though it is.>    In that case, an OPCOM message is issued that says that the#    tape is not the next in the set.i  ;    SSMgr does its own checking to ensure that what it finds >    on the next tape is indeed the continuation of the save set<    it had been processing. Therefore, this check made by the;    MTAACP can be safely overridden with the /OVERRIDE=SETIDc0    qualifier on the $MOUNT command. For example,  B        $ MOUNT/OVERRIDE=SETID MUA0:  BEATLE,JOHN,PAUL,GEORGE,RINGO      
  Using  SSMgrl o  f      Output    Save Sets  >    Output save sets may be created by SSMgr on any nonnetwork-;    accessed disk, bound volume set, or tape device. As withe9    input save sets, that device must be mounted Files-11.u    Output      Save Sets on Disk  >    SSMgr can create and write to save sets on any disk that is>    locally connected and mounted Files-11. The process wishing>    to create and write those files must be suitably privileged=    for create and write access. The disk may be a single diske     volume or a bound volume set.  >    Standard OpenVMS defaults apply in specifying the pathnames>    of the files containing the save sets. That is, the default6    directory specification is assumed unless otherwise:    specified. See Section 3.1.4 for special considerations4    around the creation of multiple output save sets.  8    For the use of wildcards in specifying pathnames, see    Section 3.2.$    Output      Save Sets on Tape  :    Output save sets may be created on magnetic tape. SSMgr:    can create save sets on any tape device that is locally7    connected and mounted Files-11. In mounting a singleY:    tape Files-11, the tape label must be specified, or the>    /OVERRIDE=ID qualifier used on the $MOUNT command. Further,=    the tape must have been initialized ($INITIALIZE) prior tof    mounting for use by SSMgr.t  6    Tapes are sequential devices. SSMgr will create the:    specified save set file after the last file on the tape<    unless the /REWIND qualifier is specified on the $SAVESET:    command line. If /REWIND is specified, SSMgr will first=    rewind to BOT and then create the specified save set file,f2    overwriting whatever may have been on the tape.  :    See Section 3.1.4 for special considerations around the)    creation of multiple output save sets.r  8    For the use of wildcards in specifying pathnames, see    Section 3.2.o  ?                                                Using SSMgr  3-5  s  l    /  Output      Save Sets on Multivolume Tape Setsi  >    A save set created by SSMgr may span tapes in a multivolume4    tape set. If that will be so, the tapes must have7    been initialized and mounted in a manner that allowsu>    continuation to the next tape in the set. There are several&    factors that need to be considered.  =    Tape switching of Files-11-mounted tapes is handled by the <    OpenVMS magnetic tape ancillary control process (MTAACP),<    which is part of the OpenVMS operating system, not SSMgr.8    The MTAACP has certain expectations of a continuation:    tape that is loaded into the drive, be it by a human or9    a mechanical loader. Those expectations are set by thea7    parameters and qualifiers that had been specified inh8    the $MOUNT command for that device. There are several8    different ways in which a multivolume tape set can be;    mounted Files-11 for use by SSMgr to create and write toR    output save sets:  2        $ MOUNT MUA0: BEATLE,JOHN,PAUL,GEORGE,RINGO  9    In this example, five tapes have been initialized withI9    the tape labels BEATLE, JOHN, PAUL, GEORGE, and RINGO.y:    The tape that had been initialized as BEATLE is loaded,=    and the $MOUNT command issued. When that tape is full, theV=    MTAACP expects a tape that had been initialized as PAUL to <    be loaded next. If a mechanical loader is being used, and>    the next tape in the loader has that label, operations will=    proceed. If a tape is not automatically loaded, the MTAACP4:    issues an OPCOM message requesting that relative volume=    2, JOHN, be mounted. If a tape initialized with label JOHNa=    is loaded into the drive, operations will continue on thatD<    tape. If, however, an uninitialized tape or a tape with a=    label other than JOHN is loaded into the drive, the MTAACP <    will reject that tape and continue sending OPCOM messages&    requesting relative volume 2, JOHN.          $ MOUNT MUA0: BEATLEa  7    In this example, only the label of the first tape iso9    specified on $MOUNT command line. A tape that had beenT9    initialized as BEATLE is loaded and the $MOUNT commandM7    issued. When that tape is full, the MTAACP expects a$:    tape that been initialized as BEAT02 to be loaded next.9    See Section 3.1.1.3 for a description of the canonical <    continuation tape labeling algorithm for a description of  
  Using  SSMgr  E  R    =    what labels are expected when continuation tape labels areP0    not explicitly specified on the command line.  3        $ MOUNT/INITIALIZE=CONTINUATION MUA0: BEATLE3  7    In this example, only the label of the first tape is::    specified on the $MOUNT command line. When continuation9    tapes are loaded, either by a human or by a mechanical 7    loader, the MTAACP will change the tape label of the :    next tape that is loaded, using the algorithm described8    above. That is, the label of the second tape would be5    reinitialized to BEAT02, the third to BEAT03, etc.o  4    In each of the examples above, the MTAACP expects:    continuation tapes to have been initialized. It is also7    possible to use uninitialized (unformatted) tapes asV:    continuation tapes. This requires responding to MTAACP-;    generated OPCOM messages with the /BLANK_TAPE qualifier.     For example:   ?        %%%%%%%%%%%  OPCOM, 10-MAY-1996 15:23:31.78  %%%%%%%%%%%D"        request 3, from user SNYDER4        MOUNT new relative volume 2 (BEAT02) on MUA0:  7    With OPER and VOLPRO privileges, the following replyE<    will result in the uninitialized tape being formatted and,    labeled, allowing operations to continue:  $        $ REPLY/BLANK_TAPE=3 "BEAT02"  7    The tape will be formatted and labeled as BEAT02 (ore;    whatever you specify as the label you want), and mountedc'    in the drive, allowing continuation.o  <    If a continuation tape is loaded that has been formatted,;    but the tape has a label that is not the one expected byO:    the MTAACP, the following reply will result in the tape4    being relabeled, allowing operations to continue:           $ REPLY/INITIALIZE_TAPE=3  <    The tape will be relabeled as BEAT02, and operations will    continue. An alternative is:e  '        $ REPLY/INITIALIZE_TAPE=3 "JOHN"A  8    In this case, the tape will be relabeled as JOHN, and    operations will continue.  ?                                                Using SSMgr  3-7e    P      Files-11    Mount Example  9    Example 3-1 shows a session in which an image save seti:    on tape is merged with an incremental save set on disk.9    The resulting "virtual" image save set is written to aY    multivolume tape.       Example 3-1  A Files-11 Mount       $ INITIALIZE MKB200: MERGE0 1     $ INITIALIZE MKB200: MERGE1 2    $ MOUNT MKB100: IMAGE 3-    %MOUNT-I-MOUNTED, IMAGE mounted on MKB100:E"    $ MOUNT MKB200: MERGE0,MERGE1 4.    %MOUNT-I-MOUNTED, MERGE0 mounted on MKB200:  >    $ saveset merge mkb100:full.bck incr.bck mkb200:merge.bck 5!    ERRORS terminal option enabledS!    EVENTS terminal option enabled #    Opening file MKB100:[]FULL.BCK;1l4    Primary input save set MKB100:[]FULL.BCK;1 opened>    Secondary input save set DISK$USER:[ELVIS]INCR.BCK;1 opened#    Opening file MKB200:[]MERGE.BCK;V-    Output save set MKB200:[]MERGE.BCK; opened1  8     Save Set Manager V1.3B Time: 18-JUL-1996 13:29:09.58          SAVESET function: MERGE2        Primary input save set: MKB100:[]FULL.BCK;1          No journal file<        Secondary input save set: DISK$USER:[ELVIS]INCR.BCK;1          No journal file+        Output save set: MKB200:[]MERGE.BCK;           No journal file  %        Final status of each save set:   ,          Save set name:  MKB100:[]FULL.BCK;1            No errors detectedh  4          Save set name:  DISK$USER:[ELVIS]INCR.BCK;1            No errors detected0  ?                                        (continued on next page)a  
  Using  SSMgr          (    Example 3-1 (Cont.)  A Files-11 Mount  ,          Save set name:  MKB200:[]MERGE.BCK;            No errors detected       $ DISMOUNT MKB100: 6     $ DISMOUNT MKB200: 7_  >    1  The output save set will span two volumes. In this line,:       the first tape is initialized with the label merge0.  :    2  The first tape is removed from mkb200 and the second:       tape is loaded. This second tape is then initialized:       with the label merge1. After initializing that tape,;       it is removed and the first tape is reloaded into thes       drive.  9    3  The device containing the primary input save set iss       mounted Files-11.s  >    4  The device to which the "virtual" image save set will be<       written also is mounted Files-11 as a multivolume save
       set.  :    5  The SAVESET MERGE operation is performed. The second<       output tape is loaded either manually or with a loader-       when the first output tape reaches EOT.e  %    6  The input device is dismounted.   ;    7  The output device is dismounted, completing the mergen       operation.    Multiple    Output Save Setsn  ;    SSMgr provides the ability to make up to 5 copies of anyl>    output save set simultaneously. These copies may be written>    to disk or tape. Each output save set pathname is specified<    as a separate parameter on the $SAVESET command line. For    example,d  K        $ SAVESET COPY MUA0:SS.BCK *.* [-]*.* MKA100:*.* MUA1:SS_ARCHIVE.BCK   :    In this example, the save set named SS.BCK is on a tape;    mounted on tape drive MUA0:. Four copies are being made.O=    Two of the copies are being written to disk, and two othert9    are being written to tape. The copies being written tou9    disk are being written to the default directory and toa  ?                                                Using SSMgr  3-9s o  e    =    the parent directory, and in each case, the name SS.BCK is >    preserved. One tape copy is being written to a tape mounted;    on MKA100: and the file name is again the same. The lasts:    copy is being written to a tape mounted on MUA1: and is    being name SS_ARCHIVE.BCK.   <    With the /ALL qualifier, SSMgr may be processing multiple9    input save sets. With one exception, in the event of a <    failure to open or to write to any output save set, SSMgr<    will attempt to continue operation to as many output save:    sets as it can, from as many input save sets as it can.  ;    If there is a failure to open any one of the output save >    sets for the second or subsequent input save sets, an error=    will be reported and operation will continue to all outputt>    save sets that could be opened. If none could be opened, an>    error will be reported and operation will continue with the    next input save set, if any.s  ;    If SSMgr cannot successfully write to an output save set <    once it has been opened, that output file will be closed,>    an error reported, and operation will continue to all other:    output save sets. If SSMgr encounters a condition where=    it can write to none of the output save sets, it will mover=    to the next input save set, if any, and continue operationE    from there.  >    The one exception to the continue-if-possible philosophy is<    if there is a problem opening any output save set for the<    first (or only) input save set for a given SSMgr command.=    In that case, the command execution is terminated to allowm+    the offending condition to be corrected.n  =    There are several performance and resource implications toM'    producing multiple output save sets:n  >    o  Multiple copies can be written to the same disk, but for<       each tape copy desired, there must be a dedicated tape       drive.  8    o  A SSMgr operation to multiple output save sets can7       proceed only as fast as the slowest output device ;       permits. If one device is involved in error recovery,s/       all others must wait until it's complete.r    Using   SSMgr $  E    <    o  A set of I/O buffers is allocated for each output save<       set, with a maximum of four 64KB buffers allocated for       each.   <    o  XOR and CRC calculations are performed for each output<       save set, thereby significantly increasing the compute       load of the operation.  ;    o  For $ SAVESET COPY/IDENTICAL operation, there will be >       significant slowdown with multiple output save sets. The=       operation is optimized for a single output save set, ane<       optimization that does not transfer to multiple output       save set operations.                                                              ?                                               Using SSMgr  3-11p w  h    3  Wildcards  in Save Set and Journal File SpecifiersV  ;    SSMgr supports standard OpenVMS wildcarding of input andi;    output save set specifiers, as well as journal file nameA9    specifiers. However, because of the semantics of SSMgrl(    commands, there are some constraints.  +  Wildcard    Constraints on Input Save Setsw  <    By default, if a wildcard is used in the name of an input7    save set, only the first matching file found will bee8    used. This is true for VALIDATE, COPY, and MERGE. For;    VALIDATE and COPY, you can elect to operate on all filesr<    that match the wildcarded save set specifier by using the<    /ALL qualifier. Because the MERGE command takes two input=    save set specifiers and one output save set specifier, the :    possible combinations of names of input and output save8    sets all using wildcards presents a dizzying semantic6    matrix of resultant operations. Therefore, the /ALL4    qualifier is not supported for the MERGE command.  ;    As it is, use of /ALL with the COPY command has semantice    implications. For example:   '        $ SAVESET COPY *.BCK FOO.BCK/ALLa  ;    If there are 10 files that match the wildcarded save set 9    specifier, *.BCK, there will be 10 versions of foo.bck 8    created. That is, the output save set for each of the;    10 COPY operations will have the same name, FOO.BCK, bute:    a different version number. If there is a version limit=    placed on the directory, the first several copies could bee,    deleted on creation of subsequent copies.  ,  Wildcard    Constraints on Output Save Sets  :    Wildcarding of output save set specifiers is permitted.:    Resolution of the actual name of the output save set is<    based on the location of the wildcard or wildcards in the    output save set specifier.r  8    The components of a save set specifier are the device6    name, the directory string, the file name, the file;    type, and the version number. For example, the specifierb&    dua1:[foo]bar.baz;3 breaks down as:    Using   SSMgr f  o            device:     dua1:        directory:  [foo]        file name:  bar        file type:  .bazf        version:    ;3.  :    Only the file name and file type components may contain;    wildcards. The only legal wildcard character is * and it$;    must be the only character in that component of the fileh:    specification. When the component contains the wildcard:    character, the corresponding component from the primary8    input file specification is used. If the component is:    missing altogether, it is treated the same as if * were    used.  :        $ SAVESET COPY DUA0:[FOO]BAR.BAZ;3 DUA1:[MUMBLE]*;6  -    In this case, the output save set would bed9    DUA1:[MUMBLE]BAR.BAZ;6 because the file name componentC7    contains the wildcard and the file type component ism9    missing. Therefore, both of those components mimic then:    corresponding component from the primary input save set    specification.t  .  Wildcard    Constraints on Journal File Names  8    As with output save set specifiers, journal file name;    specifiers may contain wildcard characters. If the "fileA;    name" component of the journal file specifier contains an9    wild card, the "file name" component of the associatede9    save set will be used. If the "file type" component of <    the journal file specifier contains a wild card, then the1    default journal file type (.BJL) will be used.o  E        Example 1:  SAVESET VALIDATE DUA0:[FOO]BAR.BAZ;3/JOURNAL=*.JOUe  H        In this case, the journal file would be written to BAR.JOU in the        default directory.T  G        Example 2: SAVESET VALIDATE DUA0:[FOO]BAR.BAZ;3/JOURNAL=FOOBAR.*P  H        In this case, the journal file would be written to BAR.JOU in the        default directory.c  B        Example 3: SAVESET VALIDATE DUA0:[FOO]BAR.BAZ;3/JOURNAL=*.*  H        In this case, the journal file would be written to BAR.JOU in the        default directory.S  ?                                               Using SSMgr  3-13n i  t    "  SSMgr  Command Language Interface  9    This section describes the valid commands for SSMgr. Af;    matrix of commands and qualifiers is shown in Table 3-1.e  >    Table_3-1__SSMgr_Commands_and_Qualifiers___________________  >    Command          ______________SAVESET_Command_____________  >    Qualifier________VALIDATE__COPY______MERGE_________________  *    /ALL             Yes       Yes       No  +    /BLOCK_SIZE      No        Yes       Yes   +    /BRIEF           Yes       Yes       Yeso  +    /CHECKS          Yes       Yes       Yeso  +    /COMMENT         No        Yes       Yesc  +    /CRC             No        Yes       Yes   +    /FULL            Yes       Yes       Yest  +    /GROUP_SIZE      No        Yes       Yes   *    /IDENTICAL       No        Yes       No  +    /JOURNAL         Yes       Yes       Yese  +    /LOG_FILE        Yes       Yes       Yes   *    /OVERRIDE        No        Yes       No  +    /REWIND          Yes       Yes       Yesi  >    /TERMINAL________Yes_______Yes_______Yes___________________              Using   SSMgr e  S    > ______________________________________________________________        Copies a save set.     3    COPY  input-ss output-ss [output-ss] [output-ss]d           [output-ss] [output-ss]          input-ssr*    OpenVMS file name of an input save set.      output-ss8    OpenVMS file name(s) of the output save set(s). Up to8    5 output save sets may be specified. Unless otherwise<    specified by command qualifiers, the output save set will;    have the same attributes for XOR group size, block size, =    CRC, and other attributes as the input save set. Different 5    qualifiers may be applied to each output save set.S    >    The COPY command reads an OpenVMS BACKUP save set, verifies9    that it is readable and consistent, and creates 1 to 5 <    copies of that save set. Any rewritten (redundant) blocks>    in the input save set are eliminated in the COPY operation.<    For an explanation of rewritten blocks, see Section 4.2.2<    for Successful Completion with Save Set Condition Report.  =    You can optionally specify software CRC and XOR protectionn=    to be present, absent, or the same as the source save set.e=    The default is to make the output save set the same as thev<    input save set. The desired block size of the output save=    set can also be specified as different from the input saven9    set. The COPY command regenerates any bad blocks founde    during the operation.  <       ________________________ Note ________________________  9       The size of the save set after a COPY operation mayt;       be slightly smaller than the original save set due to :       the way the OpenVMS BACKUP utility formats the data.  ?                                               Using SSMgr  3-15p h  h    9       SSMgr repacks its data records during processing tom9       reduce the space required; there is no loss of data :       from the OpenVMS input save set, and the output save,       set is compatible with OpenVMS BACKUP.  <       ______________________________________________________                                                                              Using   SSMgr q  t              /ALLo    /[NO]ALL (default)u      Command qualifier  <    This qualifier specifies the behavior of Save Set Manager)    when save set names contain wildcards.   7    If ALL is specified, then all save sets matching the >    wildcarded input save set file specification are processed.  7    If NOALL is specified, then only the first file namea:    found that matches the wildcarded file specification is
    processed.   8    The qualifier is valid only for the VALIDATE and COPY
    functions.A      The default is /NOALL.i      /BLOCK_SIZE=n      Output save set qualifier  9    This qualifier specifies the desired block size of thet;    output save set. Valid values for n are between 2048 ande<    65024, and are rounded up to the nearest multiple of 512.=    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>    sets on disk is 32256. If a larger block size is specified,%    SSMgr will round it down to 32256.e  5    This qualifier may not be used with the /IDENTICALd
    qualifier.c  7    The default is the block size of the input save set.       /BRIEF (default)a  ?                                               Using SSMgr  3-17  x  a        Command qualifier  =    This qualifier specifies that a minimum level of detail isd>    to be echoed. The SAVESET function and save set name(s) are=    echoed; any error information is displayed; and the result :    of the SAVESET operation is reported. See /FULL for the'    complete list of output information.t      The default is /BRIEF.o                                                                        Using   SSMgr _  E        /CHECKS=([NO]CRC, [NO]XOR)       Input save set qualifier-  ;    This qualifier specifies the optional consistency checksD<    that will be performed on the input save set; the default    is CRC, XOR.L  ;    You must specify the /CHECKS qualifier immediately aftern;    the file name of each input save set when specifying thea8    input save set. Example 3-12 also shows that when you9    specify both CRC and XOR checks, you must list them ine,    parentheses with a comma separating them.  9    If CRC checking is specified and the input save set is <    written with CRC, then the CRC is computed for each block>    in the input save set. The computed CRC is compared against&    the CRC stored in the block header.  :    If XOR checking is specified and the input save set was>    written with XOR redundancy, then a running XOR is computed;    across each XOR group of blocks. The running XOR is then     compared to the XOR block.P  7    Each of these options requires additional processingi;    time and may impact the performance of SSMgr. Any CRC or 9    XOR inconsistencies are written to the log file and an >    informational message is returned to the calling program or"    user when processing completes.      /COMMENT=string      Output save set qualifier  ;    This qualifier inserts a comment in the output save set.t9    The comment string can be up to 252 characters. If the1;    comment string is longer than one word or if it containsK6    non-alphanumeric characters, it must be enclosed in:    quotation marks ("). The comment from the primary input1    save set is not copied to the output save set.M  >    The default is no comment string written to the output save    set.   ?                                               Using SSMgr  3-19     e        /CRC1	    /NOCRCC      Output save set qualifier  <    Specifying /CRC causes the CRC to be computed across each>    block of the output save set and stored in the block header:    of each block of the output save set. Specifying /NOCRC7    causes CRC computation to be inhibited on the output ;    save set. If this qualifier is not specified, the CRC is0<    computed and stored in the output save set only if it was!    present in the input save set.B  5    This qualifier may not be used with the /IDENTICALK
    qualifier.K  8    The default is /CRC if the primary input save set was<    written with CRC and /NOCRC if the primary input save set    was written without CRC.                                                     Using   SSMgr    o        /FULL      Command qualifier  =    This qualifier specifies that more detail is to be echoed. 7    In addition to information displayed with the /BRIEF 9    qualifier, the following information for each save sets    is displayed:         Save set name        Save set group size        Save set block sizel"       Number of blocks in save set)       Nondirectory user files in save setl&       Directory user files in save set*       Alias nondirectory files in save set'       Alias directory files in save seti       Unrecoverable CRC errors       Recoverable CRC errors!       Recoverable checksum errors #       Unrecoverable checksum errors        XOR errors       Read errorsn       Write errors       Record errorso"       Unrecoverable missing blocks        Recoverable missing blocks       Rewritten blocks      The default is /BRIEF.a      /GROUP_SIZE=n      Output save set qualifier  <    This qualifier specifies the XOR group size in the output>    save set. Valid values for n are between 0 and 100. A value1    of 0 specifies that no XOR should be computed.i  <    If this qualifier is not specified, the group size of the=    input save set is used for the output save set group size.t    This is the default action.  5    This qualifier may not be used with the /IDENTICALm
    qualifier.e  ?                                               Using SSMgr  3-21p n         
    /IDENTICAL       Command qualifier  9    This qualifier does a fast copy of the input save set.T:    A fast copy operation copies the contents of each input;    save set block to the output save set without validatione:    of the block's internal record structure. If errors are;    encountered during this operation, restart the operationt<    and include the /OVERRIDE qualifier to continue operation;    even in spite of the errors. See the /OVERRIDE qualifiera    description below.   =    Each save set is stored with information that reflects thep<    environment in which it was created. In a normal save set<    copy, the information in the output save set reflects the=    environment in which the output save set was created. Withp:    the /IDENTICAL qualifier, this information reflects the7    environment in which the input save set was created.S  <    The /IDENTICAL qualifier is not supported for multivolume;    output save sets, because you may not be able to restore     such a save set.S  <    You may not use /GROUP_SIZE, /BLOCK_SIZE, /CRC, /COMMENT,<    or /JOURNAL qualifiers with the /IDENTICAL qualifier. You>    may not use the /TERMINAL=LOG qualifier with the /IDENTICAL
    qualifier.h      /JOURNAL[=journal-file-name]e      Save set qualifierr  7    This qualifier specifies whether SSMgr will create a 8    journal file for the save set. The journal file is an9    OpenVMS BACKUP journal file with an OpenVMS file name.e>    If no journal file name is specified, the journal file will:    be written to <saveset_name>.BJL in the current default
    directory.   ;    If a journal file with the same name already exists, thec>    new journal file is appended. If it does not already exist,!    a new journal file is created.o    Using   SSMgr a  s    :    Journal files created by SSMgr will not list the labels:    of follow-on volumes in multivolume tape sets. Also, if9    COPY/IDENTICAL is used to copy a multivolume tape to ap=    single volume tape, the journal file will still list it asi    a multivolume tape set.  >    These differences from Backup created journal files are due>    to a limitation in VMS that does not allow a non-privileged<    process to obtain the volume labels of a multivolume tape    set.g  =    You must specify this qualifier immediately after the savet/    set file name specifier on the command line.y  5    This qualifier is valid for all save set file name 6    specifiers, input or output, on all SSMgr commands.  9    This qualifier may not be combined with the /IDENTICAL 
    qualifier.   <    Journal files will be created for each save set specified7    on the command line that is followed by the /JOURNAL =    qualifier. If more than one journal file is being created, )    each journal file name must be unique.e  8    For example, SAVESET COPY FILES.BCK/JOURNAL FILES.SAV:    /JOURNAL is illegal, because the resulting journal file.    names would each be, by default, FILES.BJL.      The default is /NOJOURNAL.                             ?                                               Using SSMgr  3-23t    e    %    /LOG_FILE[=logfile-name] (default)r    /NOLOG_FILE      Command qualifier  7    This qualifier causes SSMgr to write events to a log 9    file specified by logfile-name. The logfile-name is an :    ASCII file with an OpenVMS file name. If not specified,:    the default log file name is SAVESET.LOG in the current=    default directory. You can suppress creating a default logd=    file by using /NOLOG_FILE or by including /LOG_FILE=NL: onr<    the command line. The following events are written to the    SAVESET.LOG file:      o  Each invocation of SSMgr  8    o  All output returned to the user or calling program  9    o  Any errors or warnings encountered while processingn       input or output save setss      o  Operator requestsb  <    Wildcards may not be used in the specification of logfile	    names.n      /OVERRIDE    /NOOVERRIDE (default)      Command qualifier  9    This qualifier allows you to override certain internal.9    consistency checks to allow execution to continue withc<    unreadable or unrecoverable blocks in the input save set.=    This qualifier allows you to make a complete and identical     copy of a damaged save set.  <    You must use the /IDENTICAL qualifier when specifying the;    /OVERRIDE qualifier to allow continued processing of the ;    save set after encountering unrecoverable input save setp:    errors. The /IDENTICAL and /OVERRIDE qualifiers must be:    specified in that order on the command line as shown in    Example 3-4.s    Using   SSMgr e  l    
    /REWIND    /NOREWIND (default)  %    Input or output save set qualifierf  :    For magnetic tape volumes only, REWIND directs SSMgr to:    rewind the magnetic tape to the beginning-of-tape (BOT);    marker before reading or writing the volume. If /ALL wasu;    specified, the rewind only happens once before the firstc    SAVESET operation.u  8    You must specify this qualifier immediately after the8    applicable file name on the command line, as shown in    Example 3-12.  :    The following consequences result when using the REWIND
    qualifier:e  =    o  If specified with an input save set, SSMgr searches for ;       the specified file starting at the BOT position. This ;       allows SSMgr to find files located before the currentf       position of the tape.b  <    o  If specified with an output save set, SSMgr overwrites=       the tape starting at the BOT position. All files on the #       tape are therefore destroyed.   <    The default for this qualifier is /NOREWIND, which causes6    SSMgr to start processing the tape from the current    position.  .    /TERMINAL=([NO]ERRORS, [NO]EVENTS, [NO]LOG)      Command qualifier  9    This qualifier specifies what class(es) of information >    should be displayed on the user's terminal during execution    of the SAVESET command.  >    If ERRORS is specified, then all error conditions occurring<    during execution are displayed as they occur, in addition>    to being included in the final report at the end of command!    execution and in the log file.   =    If EVENTS is specified, then all nonerror event conditionsc7    occurring during execution (e.g., tape switches) aree    displayed as they occur.i  ?                                               Using SSMgr  3-25  l  r    9    If LOG is specified, then the names of all output usere7    files (for COPY and MERGE) are displayed as they aret=    written to the output save set. For VALIDATE, the names ofh<    all input user files are displayed as they are processed.7    The /TERMINAL=LOG qualifier may not be used with thes    /IDENTICAL qualifier.  <       ________________________ Note ________________________  :       When a multivolume save set is copied using the COPY8       /IDENTICAL command, volume switch information from:       the original input save set will be preserved in the7       single volume copy, and it will be reported as anT       EVENT.  <       ______________________________________________________  2    The default is /TERMINAL=(ERRORS,EVENTS,NOLOG).                                                      Using   SSMgr A  E              Example 3-2  COPY Command  G    $ saveset copy mkb200:savesetua013.B/rewind disk$user:[kits]copy.savt!    ERRORS terminal option enabled !    EVENTS terminal option enabled +    Rewinding MKB200: to beginning of volumer    Rewind of MKB200: complete )    Opening file MKB200:[]SAVESETUA013.B;1s:    Primary input save set MKB200:[]SAVESETUA013.B;1 opened3    Output save set DISK$USER:[KITS]COPY.SAV; openedQ  7    Save Set Manager V1.3B Time: 18-JUL-1996 13:45:05.49_          SAVESET function: COPY_8        Primary input save set: MKB200:[]SAVESETUA013.B;1          No journal file1        Output save set: DISK$USER:[KITS]COPY.SAV;           No journal file  %        Final status of each save set:   2          Save set name:  MKB200:[]SAVESETUA013.B;1            No errors detected   2          Save set name:  DISK$USER:[KITS]COPY.SAV;            No errors detected   ;       In Example 3-2, the tape mounted on mkb200 is rewound ;       and then the save set, SAVESETUA013.B, is copied from/>       that tape to a file called copy.sav on disk$user:[kits],2       with all save set characteristics preserved.  ;    Example 3-3  COPY Command with Multiple Output Save Setse  ?                                        (continued on next page)_            ?                                               Using SSMgr  3-27_ _  _    >    Example 3-3 (Cont.)  COPY Command with Multiple Output Save                         Sets  9    $ saveset copy full.bck mkb200:image.bck/block=32768 -     mkb500:full20.bck/group=20t!    ERRORS terminal option enabledV!    EVENTS terminal option enableds?    Primary input save set DISK$USER:[NDIAMOND]FULL.BCK;1 openedr#    Opening file MKB200:[]IMAGE.BCK;e-    Output save set MKB200:[]IMAGE.BCK; openeda$    Opening file MKB500:[]FULL20.BCK;.    Output save set MKB500:[]FULL20.BCK; opened  7    Save Set Manager V1.3B Time: 18-JUL-1996 13:56:01.74o          SAVESET function: COPY =        Primary input save set: DISK$USER:[NDIAMOND]FULL.BCK;1i          No journal file+        Output save set: MKB200:[]IMAGE.BCK;s          No journal file,        Output save set: MKB500:[]FULL20.BCK;          No journal file  %        Final status of each save set:o  7          Save set name:  DISK$USER:[NDIAMOND]FULL.BCK;1a            No errors detectedY  ,          Save set name:  MKB200:[]IMAGE.BCK;            No errors detectedb  -          Save set name:  MKB500:[]FULL20.BCK;e            No errors detecteds  0       In Example 3-3, two tape drives and a disk4       drive are being used. The input save set is on<       DISK$USER:[NDIAMOND] and is named FULL.BCK. Two copies8       of this save set are being made. One copy is being:       written to the tape mounted on MKB200, with the same;       name and other characteristics as the input save set, <       except that the block size on the output tape is being;       explicitly set to 32768, regardless of the block sizea>       on the input save set. A second copy is being written to<       the tape mounted on MKB500. For this copy, the name of>       the save set is changed to FULL20.BCK, the group size is  ?                                        (continued on next page)t    Using   SSMgr         >    Example 3-3 (Cont.)  COPY Command with Multiple Output Save                         Sets=       being explicitly set to 20, and all other characterists *       of the input save set are preserved.    8    Example 3-4  COPY Command with IDENTICAL and OVERRIDE2                 Qualifiers on Save Set with Errors  D    $ saveset copy/identical/override star.sav mkb200:rock.bck/rewind!    ERRORS terminal option enabledn!    EVENTS terminal option enabledt+    Rewinding MKB200: to beginning of volumeO    Rewind of MKB200: complete :    Primary input save set DISK$USER:[GRD]STAR.SAV;1 opened"    Opening file MKB200:[]ROCK.BCK;,    Output save set MKB200:[]ROCK.BCK; openedC    CRC error: block number 33 in save set DISK$USER:[GRD]STAR.SAV;1_B    Error recovery successful in save set DISK$USER:[GRD]STAR.SAV;1H    %SAVESET-I-MISSINGBLK, Missing block could not be regenerated in file    DISK$USER:[GRDEAD]STAR.SAV;1nC    CRC error: block number 35 in save set DISK$USER:[GRD]STAR.SAV;1f>    Recovery unsuccessful in save set DISK$USER:[GRD]STAR.SAV;1F    %SAVESET-I-BADCRC, Data CRC error in file DISK$USER:[GRD]STAR.SAV;1C    CRC error: block number 42 in save set DISK$USER:[GRD]STAR.SAV;1,A    Block recovered from XOR in save set DISK$USER:[GRD]STAR.SAV;1oC    CRC error: block number 48 in save set DISK$USER:[GRD]STAR.SAV;1h>    Recovery unsuccessful in save set DISK$USER:[GRD]STAR.SAV;1F    %SAVESET-I-BADCRC, Data CRC error in file DISK$USER:[GRD]STAR.SAV;1>    XOR error at block 55 in save set DISK$USER:[GRD]STAR.SAV;1C    CRC error: block number 60 in save set DISK$USER:[GRD]STAR.SAV;1n>    Recovery unsuccessful in save set DISK$USER:[GRD]STAR.SAV;1F    %SAVESET-I-BADCRC, Data CRC error in file DISK$USER:[GRD]STAR.SAV;1>    XOR error at block 66 in save set DISK$USER:[GRD]STAR.SAV;1  8    Save Set Manager V1.3B  Time: 18-JUL-1996 14:38:49.31  ?                                        (continued on next page)S            ?                                               Using SSMgr  3-29c e  h    7    Example 3-4 (Cont.)  COPY Command with IDENTICAL andt<                         OVERRIDE Qualifiers on Save Set with                         Errors          SAVESET function: COPYa;        Primary input save set: DISK$USER:[GRDEAD]STAR.SAV;1           No journal file*        Output save set: MKB200:[]ROCK.BCK;          No journal file  %        Final status of each save set:a  5          Save set name:  DISK$USER:[GRDEAD]STAR.SAV;1u0          Unrecoverable CRC errors:             30          Recoverable CRC errors:               20          XOR errors:                           2  +          Save set name:  MKB200:[]ROCK.BCK;c            No errors detected   7       In Example 3-4, a copy of the save set, STAR.SAV,g<       located in the default disk directory, is being copied:       to a tape mounted on tape device MKB200. The tape is:       rewound before the copy is initiated. An "identical"<       copy is being made; i.e., no internal record structure;       validation is being done and the save set informationi8       stored within the output save set will reflect the:       environment in which the input save set was created,:       rather than the environment in which the output save<       set is being created. Further, the /OVERRIDE qualifier8       results in continued operation even in the face of9       errors, accepting the fact that the output save sets"       may not be fully restorable.  9    Example 3-5  COPY with Wildcarding, Journaling, and No                  Logfileu  ?                                        (continued on next page)o              Using   SSMgr         >    Example 3-5 (Cont.)  COPY with Wildcarding, Journaling, and"                         No Logfile      $ saveset copy/all/nolog =    _Input Save Set: dka400:[dcsc030.kit]*.*/checks=(crc,xor)-     _/journal=*.bjl7    _Output Save Set: mkb200:*.*/crc/comment="DCSC Copy"t    _Output Save Set 2:!    ERRORS terminal option enabledb!    EVENTS terminal option enabled @    Primary input save set DKA400:[DCSC030.KIT]DCSC030.A;1 opened#    Opening file MKB200:[]DCSC030.A;y-    Output save set MKB200:[]DCSC030.A; opened   7    Save Set Manager V1.3B Time: 18-JUL-1996 14:53:20.21           SAVESET function: COPY >        Primary input save set: DKA400:[DCSC030.KIT]DCSC030.A;15          Journal file: DISK$GREEN:[DRAGON]DCSC030.BJLt+        Output save set: MKB200:[]DCSC030.A;           No journal file  %        Final status of each save set:q  8          Save set name:  DKA400:[DCSC030.KIT]DCSC030.A;1            No errors detectedt  ,          Save set name:  MKB200:[]DCSC030.A;            No errors detectedo  @    Primary input save set DKA400:[DCSC030.KIT]DCSC030.B;1 opened#    Opening file MKB200:[]DCSC030.B;t-    Output save set MKB200:[]DCSC030.B; openedt  7    Save Set Manager V1.3B Time: 18-JUL-1996 14:56:45.83r          SAVESET function: COPYl>        Primary input save set: DKA400:[DCSC030.KIT]DCSC030.B;15          Journal file: DISK$GREEN:[DRAGON]DCSC030.BJLo+        Output save set: MKB200:[]DCSC030.B;m          No journal file  %        Final status of each save set:   ?                                        (continued on next page)n  ?                                               Using SSMgr  3-31  r  e    >    Example 3-5 (Cont.)  COPY with Wildcarding, Journaling, and"                         No Logfile  8          Save set name:  DKA400:[DCSC030.KIT]DCSC030.B;1            No errors detectedw  ,          Save set name:  MKB200:[]DCSC030.B;            No errors detected   @    Primary input save set DKA400:[DCSC030.KIT]DCSC030.C;1 opened#    Opening file MKB200:[]DCSC030.C; -    Output save set MKB200:[]DCSC030.C; opened.  7    Save Set Manager V1.3B Time: 18-JUL-1996 15:02:50.30           SAVESET function: COPY >        Primary input save set: DKA400:[DCSC030.KIT]DCSC030.C;15          Journal file: DISK$GREEN:[DRAGON]DCSC030.BJLf+        Output save set: MKB200:[]DCSC030.C;           No journal file  %        Final status of each save set:   8          Save set name:  DKA400:[DCSC030.KIT]DCSC030.C;1            No errors detectedu  ,          Save set name:  MKB200:[]DCSC030.C;            No errors detectedo        Summary of COPY operationsa  1        Total operations attempted:              3 1        Operations completing successfully:      3n    $  *       In Example 3-5, all the save sets in<       dka400:[dcsc030.kit] are copied to the tape mounted on=       mkb200. No log file will be generated. CRC checking ands<       XOR checking will be performed on all the save sets as>       they are being copied. A journal of the files is created;       for each save set and given the name of each save sett<       with the .bjl extension. CRC is computed for each save>       set on the tape, and the comment, "DCSC copy" is entered>       into the save set comment field because the journal file:       name is the same for all three save sets copied. The:       second and third save sets' journal file entries are  ?                                        (continued on next page)O    Using   SSMgr a  e    >    Example 3-5 (Cont.)  COPY with Wildcarding, Journaling, and"                         No Logfile=       appended to the journal file created for the first saver
       set.    ;    Example 3-6  COPY with /JOURNAL and /TERMINAL Qualifiers,  .    $ saveset copy/terminal=(errors,events,log)1    _Input Save Set: mkb200:SAVESETUA013.B/journal #    _Output Save Set: savesetua013.bm    _Output Save Set 2:    LOG terminal option enabled!    ERRORS terminal option enableda!    EVENTS terminal option enabledU)    Opening file MKB200:[]SAVESETUA013.B;1c:    Primary input save set MKB200:[]SAVESETUA013.B;1 opened=    Output save set DISK$USER:[SOFTWARE]SAVESETUA013.B; openedu@    Processing user file: [SOFTWARE.SAVESETUA013]KITINSTAL.COM;29B    Processing user file: [SOFTWARE.SAVESETUA013]SAVESET$IVP.COM;14=    Processing user file: [SOFTWARE.SAVESETUA013]SAVESET.CLD;4 =    Processing user file: [SOFTWARE.SAVESETUA013]SAVESET.HLP;4 0    Processing user file: [SOFTWARE.SAVESETUA013]      SAVESETUA013.RELEASE_NOTES;30    Processing user file: [SOFTWARE.SAVESETUA013]#     SAVESETUA013_RELEASE_NOTES.PS;5o0    Processing user file: [SOFTWARE.SAVESETUA013]     SAVESET_COVER_LETTER.PS;6i0    Processing user file: [SOFTWARE.SAVESETUA013]     SAVESET_USER_GUIDE.PS;170    Processing user file: [SOFTWARE.SAVESETUA013]     SAVESET_USER_GUIDE.TXT;8  7    Save Set Manager V1.3B Time: 18-JUL-1996 15:31:56.90f  ?                                        (continued on next page)l                ?                                               Using SSMgr  3-33e A  E    8    Example 3-6 (Cont.)  COPY with /JOURNAL and /TERMINAL"                         Qualifiers          SAVESET function: COPY 8        Primary input save set: MKB200:[]SAVESETUA013.B;1(          Journal file: SAVESETUA013.BJL;;        Output save set: DISK$USER:[SOFTWARE]SAVESETUA013.B;I          No journal file  %        Final status of each save set:r  2          Save set name:  MKB200:[]SAVESETUA013.B;1            No errors detectedg  <          Save set name:  DISK$USER:[SOFTWARE]SAVESETUA013.B;            No errors detected   4       Example 3-6 shows how to enable all classes of>       information that can be displayed to a terminal during a<       copy operation that copies the save set SAVESETUA013.B;       from the tape mounted on MKB200 to the directory fromo>       which the command is issued. Note the prompt for another:       output save set, should you decide to create another7       copy during the same operation. If you don't wantn=       another copy, hit <return>. A journal file of the name, :       SAVESETUA013.BJL, is created in that same directory.  =    Example 3-7  COPY with /BLOCK_SIZE, /GROUP_SIZE, and /FULLm                 Qualifiers  ,    $ saveset copy/full mkb200:savesetua013.b;    _Output Save Set: copy.sav/block_size=3072/group_size=20     _Output Save Set 2:!    ERRORS terminal option enabled.!    EVENTS terminal option enableda)    Opening file MKB200:[]SAVESETUA013.B;1d:    Primary input save set MKB200:[]SAVESETUA013.B;1 opened7    Output save set DISK$USER:[SOFTWARE]COPY.SAV; openedt  8    Save Set Manager V1.3B  Time: 18-JUL-1996 15:42:28.56  ?                                        (continued on next page)       Using   SSMgr s  i    ?    Example 3-7 (Cont.)  COPY with /BLOCK_SIZE, /GROUP_SIZE, and (                         /FULL Qualifiers          SAVESET function: COPYt8        Primary input save set: MKB200:[]SAVESETUA013.B;1          No journal file5        Output save set: DISK$USER:[SOFTWARE]COPY.SAV;o          No journal file  %        Final status of each save set:L  2          Save set name:  MKB200:[]SAVESETUA013.B;11          Save set group size:                  25s3          Save set block size:                  9216p2          Blocks in save set:                   1060          Nondirectory files in save set:       90          Directory files in save set:          00          Alias nondirectory files in save set: 00          Alias directories in save set:        00          Unrecoverable CRC errors:             00          Recoverable CRC errors:               00          Unrecoverable checksum errors:        00          Recoverable checksum errors:          00          XOR errors:                           00          Read errors:                          00          Write errors:                         00          Record errors:                        00          Unrecoverable missing blocks:         00          Recoverable missing blocks:           00          Rewritten blocks:                     0            No errors detected   ?                                        (continued on next page)I                      ?                                               Using SSMgr  3-35p e  s    ?    Example 3-7 (Cont.)  COPY with /BLOCK_SIZE, /GROUP_SIZE, and (                         /FULL Qualifiers  6          Save set name:  DISK$USER:[SOFTWARE]COPY.SAV;1          Save set group size:                  20 3          Save set block size:                  3072r2          Blocks in save set:                   3610          Nondirectory files in save set:       90          Directory files in save set:          00          Alias nondirectory files in save set: 00          Alias directories in save set:        00          Unrecoverable CRC errors:             00          Recoverable CRC errors:               00          Unrecoverable checksum errors:        00          Recoverable checksum errors:          00          XOR errors:                           00          Read errors:                          00          Write errors:                         00          Record errors:                        00          Unrecoverable missing blocks:         00          Recoverable missing blocks:           00          Rewritten blocks:                     0            No errors detectedN  3       In Example 3-7, the save set, SAVESETUA013.B, 2       is copied from the tape mounted on MKB200 to:       DISK$USER:[SOFTWARE]COPY.SAV. The block size will be=       3072 and the group size = 20 in the save set, COPY.SAV.n>       Note the prompt for an additional output save set if all;       the information is not entered on the initial commandO>       line. A full report will be generated upon completion of       the copy operation.                           Using   SSMgr C  .    > ______________________________________________________________        Merges two input save sets.    7    MERGE  primary-input-ss secondary-input-ss output-ss 9           [output-ss] [output-ss] [output-ss] [output-ss]:          primary-input-ssN;    OpenVMS file name of an input save set. The primary save :    set can be an image, incremental, or file-oriented save    set.s      secondary-input-ssv7    OpenVMS file name of a secondary input save set. Theo>    secondary input save set is an incremental or file-oriented=    save set that covers a period of time starting at the timeo$    the primary save set was created.      output-ss8    OpenVMS file name(s) of the output save set(s). Up to;    five output save sets may be specified. Unless otherwiseO<    specified by command qualifiers, the output save set will;    have the same attributes for XOR group size, block size, ;    CRC, and other attributes as the primary input save set.e:    Different qualifiers may be applied to each output save    set.     =    The MERGE operation takes two OpenVMS BACKUP save sets and2:    produces 1 to 5 output save sets. Acceptable input save=    sets include image backups, incremental backups, and file-i:    oriented save sets. The following combinations of input>    primary and secondary save sets result in the listed output
    save sets:             ?                                               Using SSMgr  3-37  n       >    ___________________________________________________________$    Primary Input     Secondary Input>    Save_Set__________Save_Set__________Output_Save_Set________  ,    Image             Incremental       Image  2    Incremental       Incremental       Incremental  4    Incremental       File-oriented     File-oriented  4    File-oriented     Incremental       File-oriented  >    File-oriented_____File-oriented_____File-oriented__________  0    No other combinations of save sets are legal.  :    The output save set contains the merge of the two input:    save sets. If the primary save set was an image backup,9    the output saves set contain an image backup up to ther9    time that the secondary input save set was created. IfE9    the primary and secondary save sets were incrementals,i7    the output save set will contain an incremental savee:    set that spans the combined time frame of the two input    incrementals.  7    The output save sets' CRC and XOR protections can be 8    independently specified to be present, absent, or the9    same as the primary save set. If detected by SSMgr, anv<    attempt to merge a primary save set with an inappropriate5    incremental save set, such as from another disk ore9    noncontiguous time period, will result in a diagnostic :    message and an aborted operation. However, SSMgr cannot<    detect all such inappropriate combinations; the result of<    such an inappropriate merge will be a legal save set, but&    its contents may not be meaningful.  :    The MERGE operation does not accept physical save sets.      /BLOCK_SIZE=n            Using   SSMgr A  n        Output save set qualifier  9    This qualifier specifies the desired block size of thev;    output save set. Valid values for n are between 2048 andt<    65024, and are rounded up to the nearest multiple of 512.>    The block size of the primary input save set is used if the)    BLOCK_SIZE qualifier is not specified.S  5    As required by OpenVMS BACKUP, the upper limit forO9    save sets on disks is 32256. If a larger block size isc0    specified, SSMgr will round it down to 32256.      /BRIEF (default)c      Command qualifier  :    This qualifier specifies that a minimum level of detail=    is to be echoed. The SAVESET function and save set name(s);:    are echoed; any error information is displayed; and the=    result of the SAVESET operation is reported. See /FULL forR)    a complete list of output information.C      /CHECKS=([NO]CRC,[NO]XOR)      Input save set qualifieru  ;    This qualifier specifies the optional consistency checksr<    that will be performed on the input save set; the default    is CRC, XOR.4  8    You must specify this qualifier immediately after the:    file name of the save set on the command line, as shown<    in Example 3-10. Example 3-12 shows that when you specify=    both CRC and XOR checks, you must list them in parenthesesC     with a comma separating them.  9    If CRC checking is specified and the input save set isa<    written with CRC, then the CRC is computed for each block=    in the input save set. The CRC is compared against the CRCc    stored in the block header.        ?                                               Using SSMgr  3-39          6    If XOR checking is specified and the input save set9    was written with XOR redundancy, then a running XOR isn<    computed across each XOR group of blocks. The running XOR     is compared to the XOR block.  7    Each of these options requires additional processing ;    time and may impact the performance of SSMgr. Any CRC or 9    XOR inconsistencies are written to the log file and an >    informational message is returned to the calling program or#    user when the command completes.                                                                       Using   SSMgr ;             /COMMENT=string      Command qualifier  ;    This qualifier inserts a comment in the output save set.e9    The string can be up to 252 characters. If the commente8    string is longer than one word or if it contains non-<    alphanumeric characters, it must be enclosed in quotation<    marks ("). If not specified, no comment is written to the    output save set.n        /CRCM	    /NOCRCt      Output save set qualifier  <    Specifying /CRC causes the CRC to be computed across each>    block of the output save set and stored in the block header:    of each block of the output save set. Specifying /NOCRC7    causes CRC computation to be inhibited on the outputt;    save set. If this qualifier is not specified, the CRC ism<    computed and stored in the output save set only if it was)    present in the primary input save set.         /FULL      Command qualifier  =    This qualifier specifies that more detail is to be echoed. 7    In addition to information displayed with the /BRIEFY9    qualifier, the following information for each save setf    is displayed:         Save set name        Save set group sizee       Save set block sizeM"       Number of blocks in save set)       Nondirectory user files in save set &       Directory user files in save set*       Alias nondirectory files in save set  ?                                               Using SSMgr  3-41  _  p    '       Alias directory files in save sety       Unrecoverable CRC errors       Recoverable CRC errors!       Recoverable checksum errors #       Unrecoverable checksum errorsC       XOR errors       Read errorsi       Write errors       Record errorsa"       Unrecoverable missing blocks        Recoverable missing blocks       Rewritten blocks                                                                  Using   SSMgr K  D          /GROUP_SIZE=n      Output save set qualifier  <    This qualifier specifies the XOR group size in the output>    save set. Valid values for n are between 0 and 100. A value9    of 0 specifies that no XOR should be computed. If this <    qualifier is not specified, the group size of the primary    input save set is used.        /JOURNAL[=journal-file-name]t      Save set qualifier.  7    This qualifier specifies whether SSMgr will create at8    journal file for the save set. The journal file is an9    OpenVMS BACKUP journal file with an OpenVMS file name. >    If no journal file name is specified, the journal file will:    be written to <saveset_name>.BJL in the current default
    directory..  ;    If a journal file with the same name already exists, the >    new journal file is appended. If it does not already exist,!    a new journal file is created.o  :    Journal files created by SSMgr will not list the labels:    of follow-on volumes in multivolume tape sets. Also, if9    COPY/IDENTICAL is used to copy a multivolume tape to a =    single volume tape, the journal file will still list it as0    a multivolume tape set.  >    These differences from Backup created journal files are due>    to a limitation in VMS that does not allow a non-privileged<    process to obtain the volume labels of a multivolume tape    set.0  =    You must specify this qualifier immediately after the savee/    set file name specifier on the command line.   5    This qualifier is valid for all save set file name 6    specifiers, input or output, on all SSMgr commands.  ?                                               Using SSMgr  3-430 D  0    <    Journal files will be created for each save set specified7    on the command line that is followed by the /JOURNALD=    qualifier. If more than one journal file is being created, >    each journal file name must be unique. For example, SAVESET>    MERGE FULL.BCK/JOURNAL INCR.BCK/JOURNAL FULL.BCK/JOURNAL is=    illegal, because the resulting journal file names would be:$    FULL.BJL, INCR.BJL, and FULL.BJL.      The default is /NOJOURNAL.4                                                                        Using   SSMgr e  e    %    /LOG_FILE[=logfile-name] (default)l    /NOLOG_FILE      Command qualifier  <    This qualifier causes SSMgr to write events to a log file:    specified by logfile-name. The logfile-name is an ASCII;    file with an OpenVMS file name. By default, a logfile ise:    created for every execution of an SSMgr command. If not=    specified, the default log file name is SAVESET.LOG in the ;    current default directory. You can suppress the creationT=    of a default log file by using /NOLOG_FILE or bu including >    /LOG_FILE=NL: on the command line. The following events are#    written to the SAVESET.LOG file:E      o  Each invocation of SSMgr  8    o  All output returned to the user or calling program  9    o  Any errors or warnings encountered while processingv       input save setsE      o  Operator requestsN  <    Wildcards may not be used in the specification of logfile	    names.o  
    /REWIND    /NOREWIND (default)  %    Input or output save set qualifierv  :    For magnetic tape volumes only, REWIND directs SSMgr to:    rewind the magnetic tape to the beginning-of-tape (BOT)$    marker before reading the volume.  8    You must specify this qualifier immediately after the8    applicable file name on the command line, as shown in*    Example 3-12 for the /CHECKS qualifier.  :    The following consequences result when using the REWIND
    qualifier::  =    o  If specified with an input save set, SSMgr searches forl;       the specified file starting at the BOT position. Thisf;       allows SSMgr to find files located before the currentr       position of the tape.]  ?                                               Using SSMgr  3-45A S  S    <    o  If specified with an output save set, SSMgr overwrites9       the tape starting at BOT. All files on the tape are;       therefore destroyed.  <    The default for this qualifier is /NOREWIND, which causes6    SSMgr to start processing the tape from the current    position.  .    /TERMINAL=([NO]ERRORS, [NO]EVENTS, [NO]LOG)      Command qualifier  9    This qualifier specifies what class(es) of information >    should be displayed on the user's terminal during execution    of the SAVESET command.  >    If ERRORS is specified, then all error conditions occurring<    during execution are displayed as they occur, in addition>    to being included in the final report at the end of command!    execution and in the log file.   =    If EVENTS is specified, then all nonerror event conditions 7    occurring during execution (e.g., tape switches) arer    displayed as they occur.M  9    If LOG is specified, then the names of all output user 7    files (for COPY and MERGE) are displayed as they are;=    written to the output save set. For VALIDATE, the names of <    all input user files are displayed as they are processed.  2    The default is /TERMINAL=(ERRORS,EVENTS,NOLOG).  ;       In Example 3-8, an image save set, full.bck, is being ;       merged with an incremental save set, incr.bck, in thei9       default disk directory. Two copies of the resultants:       virtual image save set are being created, one in the7       current default directory and another on the tape >       mounted on device mbk500:. Each output save set is named       merge.bck.            Using   SSMgr e  7        Example 3-8  MERGE CommandE  ?    $ saveset merge full.bck incr.bck merge.bck mkb500:merge.bckm!    ERRORS terminal option enabledv!    EVENTS terminal option enabledu>    Primary input save set DISK$MUSIC:[MOZART]FULL.BCK;1 opened@    Secondary input save set DISK$MUSIC:[MOZART]INCR.BCK;1 opened7    Output save set DISK$MUSIC:[MOZART]MERGE.BCK; openedS#    Opening file MKB500:[]MERGE.BCK;e-    Output save set MKB500:[]MERGE.BCK; opened   7    Save Set Manager V1.3B Time: 18-JUL-1996 16:03:43.18           SAVESET function: MERGE<        Primary input save set: DISK$MUSIC:[MOZART]FULL.BCK;1          No journal file>        Secondary input save set: DISK$MUSIC:[MOZART]INCR.BCK;1          No journal file5        Output save set: DISK$MUSIC:[MOZART]MERGE.BCK;:          No journal file+        Output save set: MKB500:[]MERGE.BCK;e          No journal file  %        Final status of each save set:   6          Save set name:  DISK$MUSIC:[MOZART]FULL.BCK;1            No errors detected1  6          Save set name:  DISK$MUSIC:[MOZART]INCR.BCK;1            No errors detected   6          Save set name:  DISK$MUSIC:[MOZART]MERGE.BCK;            No errors detectedr,          Save set name:  MKB500:[]MERGE.BCK;            No errors detected0                  ?                                               Using SSMgr  3-47a s         =    Example 3-9  MERGE Command with /FULL, /LOG, and /TERMINALR                 Qualifiers  >    $ saveset merge/full/log=merge.log/terminal=error incr2.bck!    _Secondary Save Set: incr3.bck <    _Output Save Set: incr4.bck/group_size=0/block_size=32256    _Output Save Set 2:!    ERRORS terminal option enabledi!    EVENTS terminal option enabled0?    Primary input save set DISK$MUSIC:[EAGLES]INCR2.BCK;1 openedcA    Secondary input save set DISK$MUSIC:[EAGLES]INCR3.BCK;1 openedo7    Output save set DISK$MUSIC:[EAGLES]INCR4.BCK; opened   7    Save Set Manager V1.3B Time: 18-JUL-1996 16:11:55.01           SAVESET function: MERGE=        Primary input save set: DISK$MUSIC:[EAGLES]INCR2.BCK;1           No journal file?        Secondary input save set: DISK$MUSIC:[EAGLES]INCR3.BCK;1K          No journal file5        Output save set: DISK$MUSIC:[EAGLES]INCR4.BCK;v          No journal file  %        Final status of each save set:   ?                                        (continued on next page)                                     Using   SSMgr         ;    Example 3-9 (Cont.)  MERGE Command with /FULL, /LOG, and ,                         /TERMINAL Qualifiers  7          Save set name:  DISK$MUSIC:[EAGLES]INCR2.BCK;1s1          Save set group size:                  10v4          Save set block size:                  322562          Blocks in save set:                   1462          Nondirectory files in save set:       1401          Directory files in save set:          17 0          Alias nondirectory files in save set: 00          Alias directories in save set:        00          Files removed by merge:               00          Unrecoverable CRC errors:             00          Recoverable CRC errors:               00          Unrecoverable checksum errors:        00          Recoverable checksum errors:          00          XOR errors:                           00          Read errors:                          00          Write errors:                         00          Record errors:                        00          Unrecoverable missing blocks:         00          Recoverable missing blocks:           00          Rewritten blocks:                     0            No errors detectedl  ?                                        (continued on next page)i                                    ?                                               Using SSMgr  3-49_ _  _    ;    Example 3-9 (Cont.)  MERGE Command with /FULL, /LOG, andm,                         /TERMINAL Qualifiers  7          Save set name:  DISK$MUSIC:[EAGLES]INCR3.BCK;1 1          Save set group size:                  10n4          Save set block size:                  322562          Blocks in save set:                   2340          Nondirectory files in save set:       41          Directory files in save set:          17t0          Alias nondirectory files in save set: 00          Alias directories in save set:        00          Files removed by merge:               00          Unrecoverable CRC errors:             00          Recoverable CRC errors:               00          Unrecoverable checksum errors:        00          Recoverable checksum errors:          00          XOR errors:                           00          Read errors:                          00          Write errors:                         00          Record errors:                        00          Unrecoverable missing blocks:         00          Recoverable missing blocks:           00          Rewritten blocks:                     0            No errors detected   ?                                        (continued on next page)a                                      Using   SSMgr    s    ;    Example 3-9 (Cont.)  MERGE Command with /FULL, /LOG, and ,                         /TERMINAL Qualifiers  6          Save set name:  DISK$MUSIC:[EAGLES]INCR4.BCK;0          Save set group size:                  04          Save set block size:                  322562          Blocks in save set:                   3262          Nondirectory files in save set:       1441          Directory files in save set:          17 0          Alias nondirectory files in save set: 00          Alias directories in save set:        00          Files removed by merge:               00          Unrecoverable CRC errors:             00          Recoverable CRC errors:               00          Unrecoverable checksum errors:        00          Recoverable checksum errors:          00          XOR errors:                           00          Read errors:                          00          Write errors:                         00          Record errors:                        00          Unrecoverable missing blocks:         00          Recoverable missing blocks:           00          Rewritten blocks:                     0            No errors detectedm  <       Example 3-9 shows an incremental save set in the file,>       incr2.bck being merged with a later incremental save set=       in the file, incr3.bck, and being written to a save setm=       in the file, incr4.bck. A full report is generated upone=       completion of the merge operation. All errors, if therer<       are any, are displayed to the terminal. The group size<       is set to 0, and the block size is set to 32256 in the!       merged save set, incr4.bck.n                      ?                                               Using SSMgr  3-51            >    Example 3-10  MERGE Command with /FULL, /TERMINAL, /CHECKS,#                  and CRC Qualifierss  &    $ saveset merge/full/terminal=event0    _Primary Save Set: incr2.bck/checks=(crc,xor)2    _Secondary Save Set: incr3.bck/checks=(crc,xor)"    _Output Save Set: incr4.bck/crc    _Output Save Set 2:!    ERRORS terminal option enabledn!    EVENTS terminal option enabled ?    Primary input save set DISK$BIRD:[HUMMING]INCR2.BCK;1 openediA    Secondary input save set DISK$BIRD:[HUMMING]INCR3.BCK;1 opened 7    Output save set DISK$BIRD:[HUMMING]INCR4.BCK; openeda  7    Save Set Manager V1.3B Time: 18-JUL-1996 16:30:30.88u          SAVESET function: MERGE=        Primary input save set: DISK$BIRD:[HUMMING]INCR2.BCK;1l          No journal file?        Secondary input save set: DISK$BIRD:[HUMMING]INCR3.BCK;1a          No journal file5        Output save set: DISK$BIRD:[HUMMING]INCR4.BCK;           No journal file  %        Final status of each save set:b  ?                                        (continued on next page)                                   Using   SSMgr r  e    =    Example 3-10 (Cont.)  MERGE Command with /FULL, /TERMINAL, 4                          /CHECKS, and CRC Qualifiers  7          Save set name:  DISK$BIRD:[HUMMING]INCR2.BCK;1e1          Save set group size:                  10 4          Save set block size:                  322562          Blocks in save set:                   1462          Nondirectory files in save set:       1401          Directory files in save set:          17 0          Alias nondirectory files in save set: 00          Alias directories in save set:        00          Files removed by merge:               00          Unrecoverable CRC errors:             00          Recoverable CRC errors:               00          Unrecoverable checksum errors:        00          Recoverable checksum errors:          00          XOR errors:                           00          Read errors:                          00          Write errors:                         00          Record errors:                        00          Unrecoverable missing blocks:         00          Recoverable missing blocks:           00          Rewritten blocks:                     0            No errors detected   ?                                        (continued on next page)                                     ?                                               Using SSMgr  3-53-    p    =    Example 3-10 (Cont.)  MERGE Command with /FULL, /TERMINAL,)4                          /CHECKS, and CRC Qualifiers  7          Save set name:  DISK$BIRD:[HUMMING]INCR3.BCK;1e1          Save set group size:                  10 4          Save set block size:                  322562          Blocks in save set:                   2340          Nondirectory files in save set:       41          Directory files in save set:          17t0          Alias nondirectory files in save set: 00          Alias directories in save set:        00          Files removed by merge:               00          Unrecoverable CRC errors:             00          Recoverable CRC errors:               00          Unrecoverable checksum errors:        00          Recoverable checksum errors:          00          XOR errors:                           00          Read errors:                          00          Write errors:                         00          Record errors:                        00          Unrecoverable missing blocks:         00          Recoverable missing blocks:           00          Rewritten blocks:                     0            No errors detected   ?                                        (continued on next page)                                       Using   SSMgr    c    =    Example 3-10 (Cont.)  MERGE Command with /FULL, /TERMINAL,s4                          /CHECKS, and CRC Qualifiers  6          Save set name:  DISK$BIRD:[HUMMING]INCR4.BCK;1          Save set group size:                  10 4          Save set block size:                  322562          Blocks in save set:                   3592          Nondirectory files in save set:       1441          Directory files in save set:          17 0          Alias nondirectory files in save set: 00          Alias directories in save set:        00          Files removed by merge:               00          Unrecoverable CRC errors:             00          Recoverable CRC errors:               00          Unrecoverable checksum errors:        00          Recoverable checksum errors:          00          XOR errors:                           00          Read errors:                          00          Write errors:                         00          Record errors:                        00          Unrecoverable missing blocks:         00          Recoverable missing blocks:           00          Rewritten blocks:                     0            No errors detectedl  :       Example 3-10 shows the merge of two incremental save7       sets, incr2.bck and incr3.bck, into the save set,e;       incr4.bck. A full report is generated upon completiont=       of the merge operation. All events are displayed to thel<       terminal. CRC and XOR checking is performed on both of;       the input save sets, incr2.bck, and incr3.bck. CRC isi.       added to the merged save set, incr4.bck.                        ?                                               Using SSMgr  3-55s p  f      ?    Example 3-11  MERGE Command with Journaling on All Save Setsr  .    $ saveset merge incr2.bck/journal=incr2.bjl3    _Secondary Save Set: incr3.bck/journal=incr3.bjlo0    _Output Save Set: incr4.bck/journal=incr4.bjl    _Output Save Set 2:!    ERRORS terminal option enabled !    EVENTS terminal option enabledd=    Primary input save set DISK$BEE:[BONNET]INCR2.BCK;1 openedl?    Secondary input save set DISK$BEE:[BONNET]INCR3.BCK;1 openedl5    Output save set DISK$BEE:[BONNET]INCR4.BCK; opened   7    Save Set Manager V1.3B Time: 18-JUL-1996 16:40:04.67R          SAVESET function: MERGE;        Primary input save set: DISK$BEE:[BONNET]INCR2.BCK;1:           Journal file: INCR2.BJL=        Secondary input save set: DISK$BEE:[BONNET]INCR3.BCK;1            Journal file: INCR3.BJL3        Output save set: DISK$BEE:[BONNET]INCR4.BCK;=           Journal file: INCR4.BJL  %        Final status of each save set:   5          Save set name:  DISK$BEE:[BONNET]INCR2.BCK;1s            No errors detectedo  5          Save set name:  DISK$BEE:[BONNET]INCR3.BCK;1.            No errors detectedc  4          Save set name:  DISK$BEE:[BONNET]INCR4.BCK;            No errors detectedi  :       Example 3-11 shows the merge of two incremental save6       set, incr2.bck and incr3.bck, into the save set,=       incr4.bck. A journal file is created for each save set.                 Using   SSMgr s  e    > ______________________________________________________________    :    Validates the internal consistency and readability of a    save set.        VALIDATE  input-ssr          input-ssv+    OpenVMS file name of the input save set.q      >    The SSMgr VALIDATE command reads an OpenVMS BACKUP save set;    and verifies that at least one copy of each block of thet<    specified save set is readable or can be regenerated with5    OpenVMS BACKUP or by using the SSMgr COPY command.t  >    The VALIDATE command differs from the OpenVMS BACKUP/VERIFY>    operation in that it does not compare the save set contents;    with the data on disk. It only verifies that the data in 6    the save set is readable and internally consistent.  8    Any data integrity problems found during the VALIDATE4    operation, including unreadable data, CRC and XOR;    consistency errors, and regenerated blocks, are reportedT    to the user.       /ALLs    /[NO]ALL (default)c        Command qualifier  <    This qualifier specifies the behavior of Save Set Manager)    when save set names contain wildcards.   7    If ALL is specified, then all save sets matching thet/    wildcarded file specification are processed.t    ?                                               Using SSMgr  3-57u f       7    If NOALL is specified, then only the first file namet:    found that matches the wildcarded file specification is
    processed.   8    The qualifier is valid only for the VALIDATE and COPY
    functions.e      The default is /NOALL.       /BRIEF (default)r      Command qualifier  :    This qualifier specifies that a minimum level of detail=    is to be echoed. The SAVESET function and save set name(s)i:    are echoed; any error information is displayed; and the=    result of the SAVESET operation is reported. See /FULL for )    a complete list of output information.e      The default is /BRIEF.n      /CHECKS=([NO]CRC,[NO]XOR)      Input save set qualifier   ;    This qualifier specifies the optional consistency checksn0    that will be performed on the input save set.  8    You must specify this qualifier immediately after the=    file name of the save set on the command line, as shown inr>    Example 3-12. Example 3-12 also shows that when you specify=    both CRC and XOR checks, you must list them in parentheses      with a comma separating them.  9    If CRC checking is specified and the input save set ise<    written with CRC, then the CRC is computed for each block=    in the input save set. The CRC is compared against the CRC <    stored in the block header. If the input save set was not4    written with CRC, then this qualifier is ignored.  6    If XOR checking is specified and the input save set9    was written with XOR redundancy, then a running XOR isk<    computed across each XOR group of blocks. The running XOR:    is compared to the XOR block. If the input save set was:    not written with XOR redundancy, then this qualifier is    ignored.I    Using   SSMgr .  ;    7    Each of these options requires additional processinge8    time and may impact the performance of SSMgr. Any CRC;    or XOR inconsistencies are written to the log file and a ;    diagnostic message is returned to the calling program orR"    user when processing completes.  $    The default is /CHECKS=(CRC,XOR).      /FULL      Command qualifier  =    This qualifier specifies that more detail is to be echoed.i7    In addition to information displayed with the /BRIEF:9    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)       Nondirectory user files in save set &       Directory user files in save set*       Alias nondirectory files in save set'       Alias directory files in save setZ       Unrecoverable CRC errors       Recoverable CRC errors!       Recoverable checksum errors #       Unrecoverable checksum errors        XOR errors       Read errors        Write errors       Record errors "       Unrecoverable missing blocks        Recoverable missing blocks       Rewritten blocks      The default is /BRIEF.l      /JOURNAL[=journal-file-name]2        ?                                               Using SSMgr  3-59g p  z        Save set qualifieru  7    This qualifier specifies whether SSMgr will create aE8    journal file for the save set. The journal file is an9    OpenVMS BACKUP journal file with an OpenVMS file name.v>    If no journal file name is specified, the journal file will:    be written to <saveset_name>.BJL in the current default
    directory.8  ;    If a journal file with the same name already exists, the >    new journal file is appended. If it does not already exist,!    a new journal file is created.y  :    Journal files created by SSMgr will not list the labels:    of follow-on volumes in multivolume tape sets. Also, if9    COPY/IDENTICAL is used to copy a multivolume tape to af=    single volume tape, the journal file will still list it ast    a multivolume tape set.  >    These differences from BACKUP created journal files are due>    to a limitation in VMS that does not allow a non-privileged<    process to obtain the volume labels of a multivolume tape    set.:  =    You must specify this qualifier immediately after the save /    set file name specifier on the command line.   5    This qualifier is valid for all save set file name 6    specifiers, input or output, on all SSMgr commands.      The default is /NOJOURNAL.e  %    /LOG_FILE[=logfile-name] (default)e    /NOLOG_FILE      Command qualifier  <    This qualifier causes SSMgr to write events to a log file:    specified by logfile-name. The logfile-name is an ASCII;    file with an OpenVMS file name. By default, a logfile is0:    created for every execution of an SSMgr command. If not=    specified, the default log file name is SAVESET.LOG in the ;    current default directory. You can suppress the creation =    of a default log file by using /NOLOG_FILE or by including0>    /LOG_FILE=NL: on the command line. The following events are#    written to the SAVESET.LOG file:     Using   SSMgr m  i        o  Each invocation of SSMgr  8    o  All output returned to the user or calling program  9    o  Any errors or warnings encountered while processing        input save sets       o  Operator requests   <    Wildcards may not be used in the specification of logfile	    names.   (    The default is /LOG_FILE=SAVESET.LOG.                                                              ?                                               Using SSMgr  3-61     S    
    /REWIND    /NOREWIND (default)      Input save set qualifier   :    For magnetic tape volumes only, REWIND directs SSMgr to:    rewind the magnetic tape to the beginning-of-tape (BOT):    marker before reading the volume. This qualifier allows>    SSMgr to find save sets that are located before the current    tape position.t  8    You must specify this qualifier immediately after the<    applicable file name of the save set on the command line,    as shown in Example 3-12.  <    The default for this qualifier is /NOREWIND, which causes6    SSMgr to start processing the tape from the current:    position. Any input save set that is located before the2    current position of the tape will not be found.  .    /TERMINAL=([NO]ERRORS, [NO]EVENTS, [NO]LOG)      Command qualifier  9    This qualifier specifies what class(es) of information >    should be displayed on the user's terminal during execution    of the SAVESET command.  >    If ERRORS is specified, then all error conditions occurring<    during execution are displayed as they occur, in addition>    to being included in the final report at the end of command!    execution and in the log file.   =    If EVENTS is specified, then all nonerror event conditionsa7    occurring during execution (e.g., tape switches) areu    displayed as they occur.   9    If LOG is specified, then the names of all output userB7    files (for COPY and MERGE) are displayed as they aree=    written to the output save set. For VALIDATE, the names of <    all input user files are displayed as they are processed.  2    The default is /TERMINAL=(ERRORS,EVENTS,NOLOG).    Using   SSMgr s  m          !    Example 3-12  VALIDATE Commandc  =    $ saveset validate mkb200:rock.bck/checks=(crc,xor)/rewindr!    ERRORS terminal option enabledv!    EVENTS terminal option enabled +    Rewinding MKB200: to beginning of volume0    Rewind of MKB200: complete #    Opening file MKB200:[]ROCK.BCK;1o4    Primary input save set MKB200:[]ROCK.BCK;1 opened  7    Save Set Manager V1.3B Time: 18-JUL-1996 19:17:42.17   !        SAVESET function: VALIDATEb2        Primary input save set: MKB200:[]ROCK.BCK;1          No journal file%        Final status of each save set:   ,          Save set name:  MKB200:[]ROCK.BCK;1            No errors detectede  :       In Example 3-12, a save set named ROCK.BCK on MKB200<       is validated with CRC checking and XORing. The tape is=       rewound before the validation begins. A brief report is /       generated upon completion of the command.o  .    Example 3-13  VALIDATE with /Full Qualifier  F    $ saveset validate mkb200:rock.bck/full/rewind/checks=(nocrc,noxor)!    ERRORS terminal option enabled5!    EVENTS terminal option enabledc+    Rewinding MKB200: to beginning of volume     Rewind of MKB200: complete #    Opening file MKB200:[]ROCK.BCK;1E4    Primary input save set MKB200:[]ROCK.BCK;1 opened  7    Save Set Manager V1.3B Time: 18-JUL-1996 19:21:33.48m  ?                                        (continued on next page)r      ?                                               Using SSMgr  3-63S    :    6    Example 3-13 (Cont.)  VALIDATE with /Full Qualifier  !        SAVESET function: VALIDATEt2        Primary input save set: MKB200:[]ROCK.BCK;1          No journal file%        Final status of each save set::  ,          Save set name:  MKB200:[]ROCK.BCK;11          Save set group size:                  10e4          Save set block size:                  322562          Blocks in save set:                   1462          Nondirectory files in save set:       1401          Directory files in save set:          17$0          Alias nondirectory files in save set: 00          Alias directories in save set:        00          Unrecoverable CRC errors:             00          Recoverable CRC errors:               00          Unrecoverable checksum errors:        00          Recoverable checksum errors:          00          XOR errors:                           00          Read errors:                          00          Write errors:                         00          Record errors:                        00          Unrecoverable missing blocks:         00          Recoverable missing blocks:           00          Rewritten blocks:                     0            No errors detected:  9       Example 3-13 shows usage of the VALIDATE command to 9       validate ROCK.BCK with full details provided in the :       report, without the optional CRC and XOR consistency9       checking, without a journal file, without rewindinge;       the tape, and with ERRORS and EVENTS terminal classes        enabled.                      Using   SSMgr           4    Example 3-14  VALIDATE All Save Sets in Directory  /    $ saveset validate/all playoffs.*/checks=crca!    ERRORS terminal option enabled0!    EVENTS terminal option enabled C    Primary input save set DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.96;1 
     opened  7    Save Set Manager V1.3B Time: 18-JUL-1996 19:31:19.04i  !        SAVESET function: VALIDATEiH        Primary input save set: DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.96;1          No journal file  %        Final status of each save set: B          Save set name:  DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.96;1            No errors detected   C    Primary input save set DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.97;1 
     opened  7    Save Set Manager V1.3B Time: 18-JUL-1996 19:31:22.25e  !        SAVESET function: VALIDATE;H        Primary input save set: DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.97;1          No journal file  %        Final status of each save set:   B          Save set name:  DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.97;1            No errors detectede  C    Primary input save set DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.98;1 
     opened  7    Save Set Manager V1.3B Time: 18-JUL-1996 19:31:23.24b  !        SAVESET function: VALIDATErH        Primary input save set: DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.98;1          No journal file  %        Final status of each save set:   ?                                        (continued on next page)   ?                                               Using SSMgr  3-65     0    <    Example 3-14 (Cont.)  VALIDATE All Save Sets in Directory  B          Save set name:  DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.98;1            No errors detectedr  C    Primary input save set DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.99;1 
     opened  7    Save Set Manager V1.3B Time: 18-JUL-1996 19:31:25.02   !        SAVESET function: VALIDATE H        Primary input save set: DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.99;1          No journal file  %        Final status of each save set:   B          Save set name:  DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.99;1            No errors detected   #      Summary of VALIDATE operations   1        Total operations attempted:              4 1        Operations completing successfully:      4   :       Example 3-14 shows the validation of all of the save<       sets in the DISK$AVALANCE:[STANLEY_CUP] directory. CRC9       checking is performed on each save set, and a briefc:       report is generated upon the completion of each save>       set, followed by a summary report of all the operations.                                Using   SSMgr    0    0    Example 3-15  VALIDATE with Journal Qualifier  @    $ saveset validate mkb500:savesetua013.b/journal=kit.contents!    ERRORS terminal option enabled !    EVENTS terminal option enabled )    Opening file MKB500:[]SAVESETUA013.B;1 :    Primary input save set MKB500:[]SAVESETUA013.B;1 opened  7    Save Set Manager V1.3B Time: 18-JUL-1996 19:43:31.09   !        SAVESET function: VALIDATE 8        Primary input save set: MKB500:[]SAVESETUA013.B;1#          Journal file: KIT.CONTENTS   %        Final status of each save set:m2          Save set name:  MKB500:[]SAVESETUA013.B;1            No errors detectedc  %    $ backup/journal=kit.contents/listt    Listing of BACKUP journal>    Journal file DISK$PEAK:[PIKES]KIT.CONTENTS;1 on 18-JUL-1996     19:44:23.45e  =    Save set SAVESETUA013.B created on 18-JUL-1996 19:40:01.66r'    Volume number 1, volume label MERGE0 .        [SOFTWARE.SAVESETUA013]KITINSTAL.COM;290        [SOFTWARE.SAVESETUA013]SAVESET$IVP.COM;14+        [SOFTWARE.SAVESETUA013]SAVESET.CLD;4M+        [SOFTWARE.SAVESETUA013]SAVESET.HLP;4r:        [SOFTWARE.SAVESETUA013]SAVESETUA013.RELEASE_NOTES;3=        [SOFTWARE.SAVESETUA013]SAVESETUA013_RELEASE_NOTES.PS;5e7        [SOFTWARE.SAVESETUA013]SAVESET_COVER_LETTER.PS;6 6        [SOFTWARE.SAVESETUA013]SAVESET_USER_GUIDE.PS;176        [SOFTWARE.SAVESETUA013]SAVESET_USER_GUIDE.TXT;8      End of BACKUP journal  8       Example 3-15 shows the validation of the save set,;       SAVESETUA013.B, on the tape device, MKB500, that alsoS=       creates a journal file named, KIT.CONTENTS, showing theS=       files in the save set. Note that to see the contents of:9       the resultant journal file, BACKUP must be invoked.     ?                                               Using SSMgr  3-67J n  f    7    Example 3-16  VALIDATE with Terminal Classes Enabled4  4    $ saveset validate/terminal=(errors,events,log) -    mkb500:savesetua013.b/rewind     LOG terminal option enabled!    ERRORS terminal option enabledr!    EVENTS terminal option enabled +    Rewinding MKB500: to beginning of volume     Rewind of MKB500: complete )    Opening file MKB500:[]SAVESETUA013.B;1C:    Primary input save set MKB500:[]SAVESETUA013.B;1 opened@    Processing user file: [SOFTWARE.SAVESETUA013]KITINSTAL.COM;29B    Processing user file: [SOFTWARE.SAVESETUA013]SAVESET$IVP.COM;14=    Processing user file: [SOFTWARE.SAVESETUA013]SAVESET.CLD;4 =    Processing user file: [SOFTWARE.SAVESETUA013]SAVESET.HLP;4_0    Processing user file: [SOFTWARE.SAVESETUA013]      SAVESETUA013.RELEASE_NOTES;30    Processing user file: [SOFTWARE.SAVESETUA013]#     SAVESETUA013_RELEASE_NOTES.PS;5q0    Processing user file: [SOFTWARE.SAVESETUA013]     SAVESET_COVER_LETTER.PS;6r0    Processing user file: [SOFTWARE.SAVESETUA013]     SAVESET_USER_GUIDE.PS;170    Processing user file: [SOFTWARE.SAVESETUA013]     SAVESET_USER_GUIDE.TXT;8  7    Save Set Manager V1.3B Time: 18-JUL-1996 19:51:55.14S  !        SAVESET function: VALIDATEi8        Primary input save set: MKB500:[]SAVESETUA013.B;1          No journal file  %        Final status of each save set:a  2          Save set name:  MKB500:[]SAVESETUA013.B;1            No errors detectedA  8       Example 3-16 shows the validation of the save set,:       SAVESETUA013.B, on the tape device, MKB500, with all;       classes of information: errors, events, and log being ;       displayed to the terminal. The tape is rewound beforei&       the validation operation begins.      Using   SSMgr s           ?                                                               4 > ______________________________________________________________  ?                                      Interpreting SSMgr Reportss    <    This chapter describes the completion and interim reports    generated by SSMgr.  -  Monitoring  the Progress of SSMgr Operationsi  8    While SSMgr is running, you can use Ctrl/T to monitor;    the progress of the SSMgr operation. Each time you enterd7    Ctrl/T, SSMgr displays a progress report as shown inl    Example 4-1.   %    Example 4-1  Ctrl/T Report Exampled  O    1 JOE::SMITH 15:44:09 SAVESET$S CPU=00:19:00.12 PF=392532 IO=292279 MEM=1131r2    2  Current input file:    [SMITH]WS_LOGIN.COM;1?    3  Input save set blocks:         5      Input files:     28u?    4  Output save set blocks:        4      Output files:    24e  ;    1  The first line is the standard OpenVMS Ctrl/T output.t  :    2  Name of last user file read from the input save set.  >    3  Total number of save set blocks and user files that have0       been read from the primary input save set.  <    4  Total number of save set blocks and user files written<       to the output save set. This is not displayed during a       VALIDATE operation.   :    Entering Ctrl/T before SSMgr has read the first file of:    the input save set will cause "None" to be displayed as;    the current input file. On MERGE operations involving ana=    image save set and an incremental save set, SSMgr displaysu<    "None" in this field throughout the initial pass over the    incremental save set.    ?                                 Interpreting SSMgr Reports  4-1e d  y      Completion  Reporting  <    When an SSMgr command terminates, the final status and/or:    a summary report is written to standard output. In most9    cases, this information also is written to a log file.i     Normal    Successful Completion  ;    Every SSMgr operation that completes successfully issues ;    a completion report that details any errors or anomalies =    found in the save sets. Refer to Example 4-2. If no errorsn6    were detected, the report has the following format:  8  Successful    Completion with Save Set Condition Report  <    If SSMgr found errors or anomalies in the input save set,<    but was still able to successfully complete the requested;    operation, then a save set condition report is produced. 7    This report breaks out the number and type of errorsa9    detected, as well as a list of user files affected. An =    error can be either recoverable or unrecoverable. An error 9    is recoverable if the save set was created with an XORs;    group size greater than zero, and there was no more thans;    one error in an XOR group. The following types of errorsa8    and anomalies are broken out for each input save set:  +    o  recoverable/unrecoverable CRC errors.c  =    o  recoverable/unrecoverable block header checksum errors.r  /    o  recoverable/unrecoverable missing blocks.s  8    o  XOR mismatch errors. The XOR block at the end of a=       group does not contain the XOR of all the blocks in thef>       group. Note that XOR mismatch errors are only considered>       recoverable if CRC protection is present in the save set;       and all data blocks in the XOR group had correct CRC.n      o  Read errors.  =    o  Record header errors. A record header within a save setn=       block contains an invalid record type or invalid recordt
       length.     Interpreting  SSMgr Reports e  J    3    Example 4-2  Normal Successful Completion Reporta  B    1  $ saveset copy mkb200:rock.bck stones.sav/identical/override$    2  ERRORS terminal option enabled%        EVENTS terminal option enabled &    3  Opening file MKB200:[]ROCK.BCK;18        Primary input save set MKB200:[]ROCK.BCK;1 opened;        Output save set DISK$MUSIC:[WAVES]STONES.SAV; openedu  :    4  Save Set Manager V1.3B Time: 18-JUL-1996 20:04:29.93      5    SAVESET function: COPY4          Primary input save set: MKB200:[]ROCK.BCK;1            No journal file7          Output save set: DISK$MUSIC:[WAVES]STONES.SAV;v            No journal file  &    6    Final status of each save set:  ,          Save set name:  MKB200:[]ROCK.BCK;1    7    No errors detected  6          Save set name:  DISK$MUSIC:[WAVES]STONES.SAV;            No errors detectedv  %    1  Command as entered by the user.   *    2  Selected terminal options displayed.  8    3  Information about progress of command and save set       names.      4  Report header.  6    5  Echo of the SSMgr command issued, separated into:       function, input save set, output save set and status       of journal file.  =    6  Status of each save set processed, including the statuse:       of multiple output save sets, if any were requested.  3    7  No errors or anomalies, either recoverable ort#       unrecoverable, were detected.t  9    o  Rewritten blocks. This is not an error, but a countr9       of the number of blocks which were rewritten due too8       conditions such as bad spots on the media. If this>       number is large, you may be able to significantly reduce  ?                                 Interpreting SSMgr Reports  4-3n r  s    <       the size of your save set by using SSMgr to copy it to       better media.q  =    If recoverable errors were detected in the input save set,g:    SSMgr also lists all files in the groups containing the<    errors. These files are still readable, but are no longer9    protected by XOR redundancy. If a second error were to =    develop within the same XOR group, user file data could bep    lost.  8    If your save set contains recoverable errors, Digital5    recommends that you use the SSMgr COPY function ton7    regenerate the XOR redundancy protection. If you areT:    dealing with save sets on media that is very old or has;    been improperly stored, Digital recommends that you copyp6    the save set with the SAVESET COPY command with the=    /IDENTICAL and /OVERRIDE qualifers to another medium, thenn<    SAVESET COPY the save set to a final medium with the /CRC>    and /GROUP qualifiers. This procedure accomplishes the copy;    operation without the risk of running a second pass overo    the suspect media.t                                                Interpreting  SSMgr Reports ]  )    )    Example 4-3  Save Set Condition Reportp  .    $ saveset merge zap4.sav zapcrc.sav foo.sav#      ERRORS terminal option enabledu#      EVENTS terminal option enabledm-      Opening file DKB200:[ENGINEER]ZAP4.SAV;2o>      Primary input save set DKB200:[ENGINEER]ZAP4.SAV;2 opened1      Opening file DISK$100:[ENGINEER]ZAPCRC.SAV;1iD      Secondary input save set DISK$100:[ENGINEER]ZAPCRC.SAV;1 opened-      Opening file DISK$100:[ENGINEER]FOO.SAV;e7      Output save set DISK$100:[ENGINEER]FOO.SAV; openedpC      Resetting to beginning of file DISK$100:[ENGINEER]ZAPCRC.SAV;1iM      File DISK$100:[ENGINEER]ZAPCRC.SAV;1 has been reset to beginning of filea9      Save Set Manager V1.3B Time: 28-NOV-1995 20:38:36.57L          SAVESET function: MERGE'        Primary input save set: ZAP4.SAVc+        Secondary input save set: ZAPCRC.SAV,        Output save set: FOO.SAV   <    1Save set name:  DISK$100:[ENGINEER.SSM.SRC.TMP]ZAP4.SAV;  -    2  Recoverable checksum errors:          1w  $    3User files affected by error(s):;            [ENGINEER.SSM.VAXV60.OBJ]CONDITION_HANDLER.OBJ;3 ;            [ENGINEER.SSM.VAXV60.OBJ]CONDITION_HANDLER.OBJ;2i;            [ENGINEER.SSM.VAXV60.OBJ]CONDITION_HANDLER.OBJ;10/            [ENGINEER.SSM.VAXV60.OBJ]COPY.OBJ;25   >    4Save set name:  DISK$100:[ENGINEER.SSM.SRC.TMP]ZAPCRC.SAV;  -    5  Recoverable CRC errors:               1B  ?                                        (continued on next page)t                  ?                                 Interpreting SSMgr Reports  4-5          1    Example 4-3 (Cont.)  Save Set Condition Report   $    6User files affected by error(s):!            [ENGINEER]BATCH.COM;26e$            [ENGINEER]BL_SETUP.COM;15$            [ENGINEER]BL_SETUP.COM;14$            [ENGINEER]BL_SETUP.COM;13            [ENGINEER]BYE.COM;2"            [ENGINEER]EVEPLUS.COM;6            [ENGINEER]FRED.COM;1o#            [ENGINEER]INIT$LSE.COM;3e#            [ENGINEER]INIT$LSE.COM;2c#            [ENGINEER]INIT$LSE.COM;1f            [ENGINEER]LN03.COM;4m             [ENGINEER]LOGIN.COM;6             [ENGINEER]LOGIN.COM;5             [ENGINEER]LOGIN.COM;4             [ENGINEER]MEDIA.COM;1!            [ENGINEER]NEWEVE.COM;5 %            [ENGINEER]NOTES$EDIT.COM;2              [ENGINEER]NOTUP.COM;2%            [ENGINEER]PAGE_COUNT.COM;9 $            [ENGINEER]PDC_ORDER.COM;3+            [ENGINEER]RAIDEV_GKSTARTUP.COM;1 %            [ENGINEER]READ_DEMO.COM;13 !            [ENGINEER]SETDEF.COM;3]             [ENGINEER]STOCK.COM;2            [ENGINEER]TEMP.COM;2a            [ENGINEER]UUCP.COM;1e$            [ENGINEER]WAS_LOGIN.COM;2#            [ENGINEER]WS_LOGIN.COM;1   4    1  Name of first input save set containing errors       /anomalies.v  0    2  Summary of errors found in first save set.  <    3  List of user files in first input save set that are no)       longer protected by XOR redundancy.r  5    4  Name of second input save set containing errorse       /anomalies.   ?                                        (continued on next page)C    Interpreting  SSMgr Reports    r    1    Example 4-3 (Cont.)  Save Set Condition Reportb  7    5  Summary of errors found in second input save set.   =    6  List of user files in second input save set that are no )       longer protected by XOR redundancy.     Error    Reportingc  :    In the case of an SSMgr MERGE or COPY operation (except8    COPY/IDENTICAL/OVERRIDE), SSMgr cannot continue after:    detecting an unrecoverable error. If this occurs, SSMgr<    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 enablede!    EVENTS terminal option enabledX?    Primary input save set DISK$USER:[SOFTWARE]ZAP2.BCK;1 openede8    Output save set DISK$USER:[SOFTWARE]ZCOPY.BCK; openedH    CRC error: block number 50 in save set DISK$USER:[SOFTWARE]ZAP2.BCK;1F    Block recovered from XOR in save set DISK$USER:[SOFTWARE]ZAP2.BCK;1  9      Save Set Manager V1.3B Time: 18-JUL-1996 20:16:28.18t          SAVESET function: COPYo=        Primary input save set: DISK$USER:[SOFTWARE]ZAP2.BCK;1E          No journal file6        Output save set: DISK$USER:[SOFTWARE]ZCOPY.BCK;          No journal file  %        Final status of each save set:p  7          Save set name:  DISK$USER:[SOFTWARE]ZAP2.BCK;1 0          Recoverable CRC errors:               1  )          User files affected by error(s):V:            [SOFTWARE.SAVESETUA013]SAVESET_USER_GUIDE.PS;17  7          Save set name:  DISK$USER:[SOFTWARE]ZCOPY.BCK;_            No errors detected     ?                                 Interpreting SSMgr Reports  4-7S S  f      Log    File  =    In addition to standard output, SSMgr messages and reportsO<    also are sent to a log file as shown in Example 4-5. Each;    log file begins with a diagnostic message containing theA=    time the SSMgr command was issued, followed by a report ori;    error message identical to that sent to standard output. ;    The default log file name is SAVESET.LOG, written to the9;    user's default directory. See the /LOGFILE= qualifier toa=    change the log file name or supress creating the log file.   :    A new log file is created for each invocation of SSMgr.                                                                  Interpreting  SSMgr Reports             Example 4-5  Log File  5    $ saveset copy ssm.bck copy.sav/identical/override       Log file:  !    ERRORS terminal option enabledS!    EVENTS terminal option enabled8B    Primary input save set DISK$ENGINEER:[SOFTWARE]SSM.BCK;1 opened;    Output save set DISK$ENGINEER:[SOFTWARE]COPY.SAV; opened K    CRC error: block number 15 in save set DISK$ENGINEER:[SOFTWARE]SSM.BCK;1VF    Recovery unsuccessful in save set DISK$ENGINEER:[SOFTWARE]SSM.BCK;1N    %SAVESET-I-BADCRC, Data CRC error in file DISK$ENGINEER:[SOFTWARE]SSM.BCK;1F    XOR error at block 26 in save set DISK$ENGINEER:[SOFTWARE]SSM.BCK;1K    CRC error: block number 45 in save set DISK$ENGINEER:[SOFTWARE]SSM.BCK;1 F    Recovery unsuccessful in save set DISK$ENGINEER:[SOFTWARE]SSM.BCK;1N    %SAVESET-I-BADCRC, Data CRC error in file DISK$ENGINEER:[SOFTWARE]SSM.BCK;1F    XOR error at block 52 in save set DISK$ENGINEER:[SOFTWARE]SSM.BCK;1K    CRC error: block number 68 in save set DISK$ENGINEER:[SOFTWARE]SSM.BCK;1eF    Recovery unsuccessful in save set DISK$ENGINEER:[SOFTWARE]SSM.BCK;1N    %SAVESET-I-BADCRC, Data CRC error in file DISK$ENGINEER:[SOFTWARE]SSM.BCK;1F    XOR error at block 78 in save set DISK$ENGINEER:[SOFTWARE]SSM.BCK;1  9      Save Set Manager V1.3B Time: 18-JUL-1996 20:22:12.74R          SAVESET function: COPYE@        Primary input save set: DISK$ENGINEER:[SOFTWARE]SSM.BCK;1          No journal file9        Output save set: DISK$ENGINEER:[SOFTWARE]COPY.SAV;a          No journal file  %        Final status of each save set:o  :          Save set name:  DISK$ENGINEER:[SOFTWARE]SSM.BCK;10          Unrecoverable CRC errors:             30          XOR errors:                           3  :          Save set name:  DISK$ENGINEER:[SOFTWARE]COPY.SAV;            No errors detecteda          ?                                 Interpreting SSMgr Reports  4-9A P  S        ?                                                               50> ______________________________________________________________  ?                                                  SSMgr Messages     :    This section contains descriptions and user actions for    messages issued by SSMgr.    $  SSMgr  INFORMATIONAL Level Messages  :  Unable          to create log file. Continuing operation.  <   Explanation: Attempt to create log file failed. The reason;   for the failure follows this message. Operation continues    without logfile.  9   Action: Correct problem indicated by secondary message.A  >  Unable               to write log file. Continuing operation.  ;   Explanation: Attempt to write to the log file failed. TheE8   reason for the failure follows this message. Operation   continues without logfile.  9   Action: Correct problem indicated by secondary message.h    SSMgr  ERROR Level Messages  8  Block            header checksum error in file filename  9   Explanation: An unrecoverable error was found in a save6:   set block header. The data contained in the block is not   reliable.   7   Action: Use OpenVMS BACKUP to restore the recoverablem   portion of the save set.  &  Data       CRC error in file filename  =   Explanation: An unrecoverable error was found in a save set =   block CRC. The data contained in the block is not reliable.:  7   Action: Use OpenVMS BACKUP to restore the recoverableP   portion of the save set.  ?                                             SSMgr Messages  5-1S A  ]    !  XOR       error in file filenamel  <   Explanation: The XOR block of a save set group in save set<   filename does not contain the valid XOR of the data blocks>   in that group and CRC protection is not present. The data in!   the entire group is unreliable.   7   Action: Use OpenVMS BACKUP to restore the recoverableO   portion of the save set.  *  filename           is not a valid saveset  <   Explanation: Save set filename is not a valid OpenVMS save   set.     Action: None.:  9  Missing           block could not be regenerated in fileo
   filename  :   Explanation: There was an unrecoverable missing block in:   save set filename and there was insufficient metadata to"   reproduce the data in the block.  6   Action: None. The data in the missing block is lost.  "  SSMgr  FATAL Level Error Messages  7  A    software bug was detected at line line, file fileM  .   Explanation: SSMgr detected an internal bug.  =   Action: Please submit an SPR and copies of the log file and,<   the input save sets. If this bug prevents you from copying:   the input save sets, submit the output of BACKUP/LIST on   those save sets instead.  )  Cannot          access device devicename   6   Explanation: Attempts to access a save set on device   devicename have failed.   =   Action: Verify that the path name given by the command line_;   is correct, that the device is mounted, and that you have "   privileges to access the device.  /  Duplicate          journal file name: filenamep  <   Explanation: For any single SAVESET command with more than=   one journal file being created, each journal file name mustn   be unique.  >   Action: Verify that the save set file names used are unique.    SSMgr  Messages /  S    *  SAVESET        operation was unsuccessful  8   Explanation: The SAVESET operation could not complete.9   Additional messages follow indicating the nature of the2
   failure.  7   Action: Base user action on the immediately following1   messages.   '  could          not close file filename:  6   Explanation: SSMgr could not close the save set with:   filename. The reason for the failure appears immediately   after this message.   .   Action: Dependent on the reason for failure.  %  could         not open file filenamet  ;   Explanation: SSMgr could not open the file with filename.a;   The reason for the failure appears immediately after thisn
   message.  .   Action: Dependent on the reason for failure.  $  error         reading file filename  7   Explanation: SSMgr encountered and error reading filer:   filename. The reason for the failure appears immediately   after this message.e  .   Action: Dependent on the reason for failure.  7  could          not reset to beginning of file filenamey  8   Explanation: SSMgr could not reset to the beginning of7   the file filename. The reason for the failure appears !   immediately after this message.s  .   Action: Dependent on the reason for failure.  %  error          writing file filenamel  6   Explanation: SSMgr encountered an error writing file:   filename. The reason for the failure appears immediately   after this message.r  .   Action: Dependent on the reason for failure.  ?                                             SSMgr Messages  5-3t    a    /  Identical              copy of filename failedt  ;   Explanation: The user specified /IDENTICAL on the SAVESETe=   COPY command line, and the operation failed. The reason forh5   the failure appears immediately after this message.o  .   Action: Dependent on the reason for failure.  :  Insufficient           space for filename to be allocated  8   Explanation: There is insufficient space on the target;   output disk device to allow allocation of a file the size    required by the operation.  <   Action: Specify a device that has sufficient space to hold   the output file.  9  Invalid           address in save set record in save setp
   filename  ;   Explanation: There is a nonzero value in address field ofR=   record header in non-LBN/VBN record. The associated data iso   therefore suspect.  >   Action: Use OpenVMS BACKUP to restore the save set and check   for data corruption.  6  Invalid           block size. Valid range: 2048-65535  :   Explanation: Save set blocks may be no smaller than 2048'   bytes and no larger than 65535 bytes.o  ;   Action: Reenter the SAVESET command and specify a /BLOCK_N1   SIZE value in the range of 2048 to 65535 bytes.   =  Could            not open devicename. Device must be disk or    tape  <   Explanation: SSMgr operates on disk and tape devices only.;   The device specified by devicename was not a disk or tapea	   device.      Action: None.s  9  Invalid           file attribute in save set file record   <   Explanation: An invalid file attribute is stored in a save<   set file record, indicating a corrupt or otherwise invalid   save set record.  9   Action: Re-enter the SAVESET command with a /GROUP_SIZE    value in the range 0 - 100.e    SSMgr  Messages M  0    1  Invalid           group size. Valid range: 0-100R  =   Explanation: Save set XOR groups may be no larger than 100..;   A value of zero indicates no XOR should be written to the6   save set.   =   Action: Reenter the SAVESET command with a GROUP_SIZE value:   in the range 0 to 100.  <  Invalid           save set record size in save set filename  ;   Explanation: A save set record contains invalid metadata.t  >   Action: Use OpenVMS BACKUP to restore the save set and check   for data corruption.  <  Invalid           save set record type in save set filename  ;   Explanation: A save set record contains invalid metadata.b  >   Action: Use OpenVMS BACKUP to restore the save set and check   for data corruption.  8  Invalid         output save set wild card specification  7   Explanation: The only legal wildcarding of the 'name' 4   or 'type' portions of an output save set file name8   specification is a single '*'. Use of the '%' wildcard7   or combining the '*' with any other characters in thei   specification is illegal.w  <   Action: Re-enter the SAVESET command with a legal wildcard4   specification or with a nonwildcard specification.  .  Error          opening journal file: filename  =   Explanation: The journal file specified could not be opened    successfully.c  =   Action: Ensure that the file name is correct, that you havem>   write access to the device, and that the device is not full.  1  Error          writing to Journal file: filename   >   Explanation: The journal file specified could not be written   to successfully.  >   Action: Ensure that you have write access to the device, and   that the device is not full.  "  Memory         allocation failure  =   Explanation: SSMgr was unable to allocate necessary memory.O  9   Action: Ensure sufficient resources for SSMgr operaton.h  ?                                             SSMgr Messages  5-5s         7  No         device name in save set specifier specifieru  ;   Explanation: No device name was specified in a context iny,   which an explicit device name is required.  >   Action: Specify the device name with the save set specifier.  ;  AZ,            is a physical save set, invalid as input toV   MERGE   6   Explanation: MERGE operations cannot be performed on   physical backup save sets.     Action: None.s  7  COPY/IDENTICAL            output save set may not spans   multiple tapes  7   Explanation: End of tape (EOT) on the output tape wasi=   encountered during a SAVESET COPY/IDENTICAL operation. This ;   operation requires that the copied save set does not span]   multiple tapes.e  :   Action: Use an output tape that has sufficient space for:   the save set or use the SAVESET COPY command without the   /IDENTICAL qualifier.o  +  device            must be accessed locallyZ  7   Explanation: The save set must be accessed on a localP	   device.n  8   Action: Use only save sets that do not require network	   access.i  "  Could           not rewind device  >   Explanation: Attempts to rewind the specified device failed.  7   Action: This error message is always accompanied by a :   secondary system message. Correct the problem identified   by that secondary message.  0  Secondary           save set not an incremental  9   Explanation: If the primary input save set in a SAVESETL:   MERGE operation is an image save set, then the secondary5   input save set must be an incremental save set. SeeR9   Table 3-1 for a list of valid save set combinations form   MERGE.  4   Action: Retry the SAVESET MERGE operation with the'   appropriate secondary input save set.f    SSMgr  Messages s       =  Too            many errors reading save set filename. Giving    up.N  =   Explanation: Too many errors were encountered while readingE;   the save set. Probably a problem with the drive or media.E  <   Action: If the problem is with the drive, try mounting the   media on a different drive.;  7  Unsupported           save set record type in save set 
   filename  2   Explanation: The save set contains a record type:   inappropriate for the SAVESET operation being performed.  <   Action: Check that the save set being used is appropriate.  #  SSMgr  WARNING level Error Mesagesc  4  No            user files written to output save set  9   Explanation: The output save set is empty: i.e. no userE,   files were written to the output save set.  0   Action: Ensure that this is what was expected.    Terminal  Messages   6    The following informational messages are written to6    SYS$OUTPUT, SYS$ERROR, and the logfile based on the<    setting of /TERMINAL options. See the /TERMINAL qualifier6    descriptions for each of the commands in Chapter 3.  #  ERRORS    Option Terminal MessagesN  ,  recovered     from XOR in save set filename  8   Explanation: The ERRORS terminal option is enabled. An>   unreadable block in save set filename was recovered via XOR.  2  recovered     via read-ahead in save set filename  9   Explanation: The ERRORS terminal option is enabled. The[;   error specified immediately above was recovered via read-]   ahead.  ?                                             SSMgr Messages  5-7  [  I    7  error:        block number number in save set filename   7   Explanation: The ERRORS terminal option is enabled. A <   checksum error was detected in block number number in save   set filename.   0  volume       is not the next volume in this set  ;   Explanation: The ERRORS terminal option is enabled. Whilee:   reading a multivolume tape set, the SSMgr has determined<   that the currently loaded volume is not the next member of   the volume set.   2  error:   block number number in save set filename  7   Explanation: The ERRORS terminal option is enabled. A ;   CRC error was detected in block number number in save set    filename.s  -  recovery     successful in save set filename   9   Explanation: The ERRORS terminal option is enabled. Then>   error specified immediately above was successfully recovered   by SSMgr.N    terminal      option enabledt  =   Explanation: The ERRORS terminal option is enabled for thisS   SAVESET command.  0  Block:       number number in save set filename  7   Explanation: The ERRORS terminal option is enabled. Ao;   missing block was detected in block number number in savel   set filename.   3  error:    block number number in save set filename1  7   Explanation: The ERRORS terminal option is enabled. A <   read error was detected in block number number in save set   filename.B  )  unsuccessful        in save set filename   9   Explanation: The ERRORS terminal option is enabled. The 8   error specified immediately above was not recoverable.    SSMgr  Messages i  t    2  Block:         number number in save set filename  7   Explanation: The ERRORS terminal option is enabled. AC;   rewritten block error was detected in block number numbere   in save set filename.   3  error   at block block-number in save set filename   8   Explanation: The ERRORS terminal option is enabled. An;   XOR error was detected in block number number in save set1   filename.R  #  EVENTS    Option Terminal Messages     terminal      option enabled   =   Explanation: The EVENTS terminal option is enabled for this    SAVESET command.    file       filename  >   Explanation: The EVENTS terminal option is enabled. SSMgr is'   attempting to open the file filename.o    save      set: filename  >   Explanation: The EVENTS terminal option is enabled. The file=   filename has been successfully opened for use as the outputt   save set.r    input       save set: filenames  >   Explanation: The EVENTS terminal option is enabled. The file>   filename has been successfully opened for use as the primary   input save set.g  &  to         beginning of file filename  9   Explanation: The EVENTS terminal option is enabled. Thei9   merge of an image save set with an incremental save set 9   requires two passes over the incremental save set. This 9   message indicates that SSMgr is resetting the secondarys%   input save set for the second pass.   >  operation        on volume volume-number of save set filename  9   Explanation: The EVENTS terminal option is enabled. The.=   save set filename is on a multivolume tape and operation isA*   resuming on volume number volume-number.  ?                                             SSMgr Messages  5-9f i  a      of      filename complete  =   Explanation: The EVENTS terminal option is enabled. /REWINDE=   was specified and the tape has been successfully rewound toS   BOT.  (  filename         to beginning of volume  =   Explanation: The EVENTS terminal option is enabled. /REWINDv.   was specified and the tape is being rewound.     secondary        input save set  =   Explanation: ... EVENTS ...enabled. An incremental save setR;   is being merged with an image save set. SSMgr is scanningK7   the incremental save set for file system information.E  !  input         save set: filenamen  9   Explanation: The EVENTS terminal option is enabled. The%;   file filename has been successfully opened for use as theA   secondary input save set.   :  to      continue writing to save set filename. Continuing   operation.  ;   Explanation: The EVENTS terminal option is enabled. SSMgrt:   could not write to one of the multiple output save sets.=   SSMgr will continue the COPY or MERGE operation, writing tos!   the remaining output save sets.V     LOG    Option Terminal Messages    terminal   option enabled  :   Explanation: The LOG terminal option is enabled for this   SAVSESET command.v    user          file: filename   ;   Explanation: The LOG terminal option is enabled. The userv-   file filename is currently being processed.       SSMgr   Messagest e       )  Process  Quota Exceeded (System Message)p  >    If you see the "Process Quota Exceeded" system message, the>    process quota exceeded is most likely PGFLQUO or DIOLM. You>    must rerun the SSMgr operation in a process with sufficient)    quota to complete the SSMgr operation.e                                                                            ?                                            SSMgr Messages  5-11  a                   ; ___________________________________________________________t  <                                                        Index      <                              _______________________________0  quotas                      DCL interface,  1-1   2-3l   2-2                        Ex                              _______________________________                                                         2-2Y                              Error report,  4-7                                      Key,e  ~                              F______________________________                                                           OpenVMS  +                              Files-11,  3-16   _________________________    H<                              _______________________________H                              HELP                                OpenVMS  U                              I_______________________________________________________a  ]                              Input save sets                                         LanguageM,                                on disks, 3-2s                                on multivolume tape sets,                                                   summary,iH                                  3-3                                 1-6S                                on tapes, 3-2                                   3-14 )                              Installation k                                before installing, 2-1                                                  3-15 t                                conditions for failure, 2-7                                                      3-37i                                disk space required, 2-1                                              3-14aj                                license registration, 2-1                                               3-1Y                                privileges, 2-1                                       3-57s_                                sample run, 2-9                                             1-3,nm                              Internationalization,  1-6                                                 3-27,e                              IVP                                1-1,                                                               4V                                example, 2-9                                        4-1+                                failure, 2-7o+                                running, 2-7i  <                                                      Index-1 e       4                                 OpenVMS MESSAGE, 1-6Q                                 Output save sets, 3-5____________________________x/                                  on disks,  3-5rt                                  on multivolume tapes,  3-6                                                      2-1     2-1                                  P____________________________Management                                                       Facili  6 (LMF),  1-6, 2-1                PAK (License PAK), 2-1<  file,  4-8                     Process Quota Exceeded, 5-112                                 Purging files, 2-6  ! ____________________________    Qn?   1-3,    3-37                  _______________________________ 0   3-46                          Qualifiers, 3-14  &                                 Quotas3  OpenVMS   MESSAGE               See Account quotas   ?  installation,       2-7        R______________________________h1  level,      5-1                Registration, 2-1e2  level,      5-2                Release notes, 2-1-  level,              5-1         option,  2-5e,   1-6                           Reports, 4-1   5-1S!  level,        5-7              Sf?  tape         sets,  3-3        _______________________________ 0                                 SAVESET.LOG, 4-8J                                 Save sets, 4-1____________________________p                                  as input to BACKUP,  1-6                                                   1-6,=                                  Files-11 mount example,  3-8e5                                  handling types,  1-4t, ____________________________     input,  3-18   1-1                            management policy,  1-3/   4-1                            physical,  3-1s1   1-1,         2-1               specifiers,  3-1l,  AUTHORIZE,      2-3             types,  3-1%  BACKUP,      1-1, 3-1          SSMgr /   1-4                            benefits,  1-1 9   1-4                            completion reports,  4-2E:   1-3                            disk space required,  2-14   2-4                            error reports,  4-7-   1-4                            errors,  4-2o/  spent    doing,  1-5            /FOREIGN,  1-6i6  compatibility,        1-6       input save sets,  3-13  HELP,      1-6                  installation,  2-1l/                                  log file,  4-8 1                                  privileges,  1-6a u  c    	  (cont'd)ow                                 V__________________________files                                                   fromi  8   versions, 2-6                 VALIDATE, 1-2, 3-57, 4-14  errors,            4-4          example,  3-63, 4-2/  notes,        2-1              VMScluster, 1-6t.   4-1                           VMSINSTAL, 2-3.   2-2                            running,  2-4  disk6?   2-4,       2-5                W______________________________8  /                                 Wildcards, 3-12i7 ____________________________     input save sets,  3-12 :   1-6                            journal file names,  3-138   3-1                            output save sets,  3-12  scwitching,   3-3?   1-6,     2-3                  X______________________________e  (                                 XOR, 4-2                                                  ?                                                         Index-3 