                                 =          Save_Set_Manager_for_OpenVMS________________________ $          User and Installation Guide    "          Order Number: AA-QDKQH-TE    3          This manual contains installation and user 7          information for the Save Set Manager software.               ;          Operating Systems:            OpenVMS VAX Versions ;                                        6.2, 7.1, 7.2 & 7.3. =                                        and OpenVMS Alpha 6.2, ;                                        7.1-2 , 7.2-1 & 7.3.   7          Software Version:             Save Set Manager 2                                        Version 1.5          $          Compaq Computer Corporation          Houston, Texas          C    ________________________________________________________________ 
    April 2001   $    2001 Compaq Computer Corporation  5    Compaq, the Compaq logo, VAX and VMS Registered in :    U.S. Patent and trademark Office. OpenVMS and Tru64 are<    trademarks of Compaq Information Technologies Group, L.P.,    in the United States and other countries.  :    Motif, and UNIX are trademarks of The Open Group in the%    United States and other countries.   =    All other product names mentioned herein may be trademarks !    of their respective companies.   <    Confidential computer software. Valid license from Compaq;    required for possession, use or copying. Consistent with 7    FAR 12.211 and 12.212, Commercial Computer Software, :    Computer Software Documentation, and Technical Data for=    Commercial Items are licensed to the U.S. government under (    vendor's standard commercial license.  8    Compaq shall not be liable for technical or editorial8    errors or omissions contained herein. The information8    in this document is provided "as is" without warranty;    of any kind and is subject to change without notice. The >    warranties for Compaq products are set forth in the express:    limited warranty statements accompanying such products.8    Nothing herein should be construed as constituting an    additional warranty.   5    Compaq service tool software, including associated >    documentation, is the property of and contains confidential>    technology of Compaq Computer Corporation. Service customer=    is hereby licensed to use the software only for activities 8    directly relating to the delivery of, and only during;    the term of, the applicable services delivered by Compaq 7    or its authorized service provider. Customer may not 6    modify or reverse engineer, remove, or transfer the>    software or make the software or any resultant diagnosis or<    system management data available to other parties without>    Compaq's or its authorized service provider's consent. Upon:    termination of the services, customer will, at Compaq's:    or its service provider's option, destroy or return the;    software and associated documentation in its possession.       Printed in the U.S.A.  =    This document was prepared using VAX DOCUMENT Version 2.1.                      ; ___________________________________________________________   <                                                     Contents      <  Preface................................................ vii         Introduction  <  1.1   Advantages of SSMgr...........................    1-1<  1.2   SSMgr Functions...............................    1-2,  1.3   How SSMgr Changes Save Set Management<        Policy........................................    1-3<  1.4   OpenVMS Compatibility.........................    1-6.  1.4.1     ODS and Extended File Specification<            Support...................................    1-6<  1.4.1.1     Disk Concepts...........................    1-6<  1.4.2     OpenVMS BACKUP Utility....................    1-9<  1.4.3     VMScluster Support........................   1-10<  1.4.4     OpenVMS License Management Facility.......   1-10<  1.4.5     Privileges................................   1-10<  1.4.6     Internationalization of Messages..........   1-10<  1.4.7     OpenVMS HELP Utility......................   1-10     Installation Procedure  '  2.1   Preinstallation Requirements and <        Preparations..................................    2-1<  2.2   License Registration..........................    2-1<  2.2.1     Privileges and Disk Space.................    2-1<  2.2.2     Process Account Quotas....................    2-2<  2.2.3     User Account Quotas.......................    2-2<  2.2.4     VMSINSTAL Requirements....................    2-3<  2.2.5     Backing Up Your System Disk...............    2-4<  2.3   Installing the SSMgr Software.................    2-4<  2.3.1     The Installation Procedure................    2-4<  2.3.2     Error Recovery............................    2-8<  2.4   SSMgr Sample Installation.....................    2-8  <                                                          iii         ?    2.5   Reporting Product Problems....................    2-11   
   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 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    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 0    3.2.2     Wildcard Constraints on Output Save?              Sets......................................    3-12 1    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 0    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-3       COPY Command with Multiple Output Save ?              Sets......................................    3-27   5    3-4       COPY Command with IDENTICAL and OVERRIDE ?              Qualifiers on Save Set with Errors........    3-29   6    3-5       COPY with Wildcarding, Journaling, and No?              Logfile...................................    3-30   -    3-6       COPY with /JOURNAL and /TERMINAL ?              Qualifiers................................    3-33   4    3-7       COPY with /BLOCK_SIZE, /GROUP_SIZE, and?              /FULL Qualifiers..........................    3-34   ?    3-8       MERGE Command.............................    3-47   0    3-9       MERGE Command with /FULL, /LOG, and?              /TERMINAL Qualifiers......................    3-48   1    3-10      MERGE Command with /FULL, /TERMINAL, ?              /CHECKS, and CRC Qualifiers...............    3-52   6    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   ?                                                               v          ?    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   /    1-1       OpenVMS File Structure Options - A ?              Comparison................................     1-7   6    2-1       Process Account Quotas for the Installing?              Account...................................     2-2   ?    3-1       SSMgr Commands and Qualifiers.............    3-14                  > ______________________________________________________________  ?                                                         Preface         =    The Save Set Manager User and Installation Guide describes <    the procedures for configuring, installing, and 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 6.2, 7.1,;    7.2 & 7.3 and for OpenVMS Alpha[TM] Versions 6.2, 7.1-2, ;    7.2-1 & 7.3. SSMgr supports a DCL interface and all disk 6    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-3              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:   =    o  Perform an image backup on day one. Each following day, =       perform an incremental backup and merge the incremental :       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 to (       restore in the event of data loss.  ;    o  Perform an image backup on day one and an incremental 4       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 save :       set with the cumulative incremental save set created=       by the previous day's merge operation until you wish to %       perform your next image backup.   9       This strategy results in one image save set and one :       incremental save set to restore in the event of data       loss.   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 save :    set. Therefore, depending upon the relative size of the=    image and incremental save sets, you may prefer to use the ,    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.   >    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 take 7    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.   9    Therefore, SSMgr MERGE operations do not eliminate the >    need for periodic image backups, but by using MERGE you can9    generally increase the interval between image backups.   ;    Other Ways to Reduce the Time Spent on BACKUP Operations   7    Time spent on online OpenVMS BACKUP operations could 8    be further reduced by omitting the calculation of CRC;    protection in BACKUP, and adding in such protection in a ;    COPY or MERGE operation in SSMgr. CRC protection and XOR =    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. =    These protections can then be inserted during a subsequent 9    SSMgr COPY or MERGE operation. In the event that SSMgr <    detects an error on a recently produced save set, you can    run OpenVMS BACKUP again.  ?                                               Introduction  1-5            OpenVMS  Compatibility   ;    The following general comments apply to using SSMgr with     OpenVMS systems.   /  ODS    and Extended File Specification Support   =    SSMgr V1.5 supports all operations on ODS-5 disks on Alpha 9    Systems running OpenVMS V7.2-1 and V7.3. This includes     support for EFS.   =    The following information is useful in understanding how a =    disk may be configured to enhance data access for improved     performance.     Disk      Concepts   6    Disk structures may be defined as either logical or>    physical and the two types interact with each other to some=    degree. That is, you cannot manipulate a logical structure =    without considering the effect on a corresponding physical 
    structure.   6    Note that RMS disk files reside on Files-11 On-Disk9    Structure (ODS) disks. Files-11 is the name applied to 9    the disk structures supported by the operating system.   8    Files-11 disk structures are further characterized as7    being either on-disk structures or CD-ROM volume and <    file structures. The Files-11 structure is a hierarchical9    organization of files, their data, and the directories !    needed to gain access to them.   :    The OpenVMS file system implements the Files-11 on-disk<    structure and provides random access to the files located:    on the disk or CD-ROM. Users can read from and write to*    disks; they can only read from CD-ROMs.  9    On-disk structures include Levels 1, 2, and 5. (Levels 8    3 and 4 are internal names for ISO and High Sierra CD;    formats.) ODS-1 and ODS-2 structures have been available $    on OpenVMS systems for some time.  =    Beginning with OpenVMS Version 7.2-1 on Alpha systems, you '    can also specify ODS-5 format disks.   >    Table 1-1 compares the specific characteristics of Files-11.    On-Disk Structure (ODS) Levels 1, 2, and 5.  
  Introduction            >    Table_1-1__OpenVMS_File_Structure_Options_-_A_Comparison___                  ODS-1(VAX>    Characteristonly)_________ODS-2_________ODS-5______________  5    File names  9.3           39.39         238 bytes, =                                            including the dot. <                                            For Unicode, that<                                            is 119 characters=                                            including the dot.   7    Character   Uppercase     Uppercase     ISO Latin-1, 2    set         alphanumeric  alphanumeric  Unicode(                              plus hyphen(                              (-), dollar!                              sign %                              ($), and '                              underscore                                (_)  8    File        32,767        32,767        32,767 limit;9    versions    limit;        limit;        version limits 9                version       version       are supported. '                limits        limits are &                are not       supported                supported  :    Directories No            Alpha:        Alpha: 255 VAX:9                hierarchies   255[2] VAX:   8 (with rooted 7                of            8 (with       logical, 16) #                directories   rooted %                and subdi-    logical,                  rectories;    16)                directory                entries are                not ordered                [1]  >    [1]RSX-11M,_RSX-11D,_RSX-11M-PLUS,_and_IAS_systems_do_not__  =    support subdirectories and alphabetical directory entries. 7    [2]Prior to OpenVMS Version 7.2 and 7.3, RMS limited     directory levels to 8 or 16.   ?                                        (continued on next page)   ?                                               Introduction  1-7          8    Table 1-1 (Cont.)  OpenVMS File Structure Options - A>    ___________________Comparison______________________________                  ODS-1(VAX>    Characteristonly)_________ODS-2_________ODS-5______________  >    OpenVMS     Local access  Files can     Files can be shared<    Cluster     only; files   be shared     across a cluster.8    Access      cannot be     across a      However, only<                shared        cluster       computers running:                across a                    OpenVMS Version9                cluster                     7.2 and 7.3 or :                                            later can mount;                                            ODS-5 disks. VAX <                                            computers running:                                            Version 7.2 and;                                            7.3 or later can >                                            see only files with=                                            ODS-2 style names.   <    Disk        Unprotected   Protected     Protected objects$                objects       objects  4    Disk        Not           Supported     Supported    quotas      supported  4    Multivolume Not           Supported     Supported    files and   supported	    volume     sets   4    Placement   Not           Supported     Supported    control     supported  :    Caches      No caching    Caching of    Caching of file9                of file       file header   header blocks, >                header        blocks, file  file identification;                blocks, file  identifica-   slots, or extent 2                identifica-   tion slots,   entries&                tion slots,   or extent$                or extent     entries                entries  4    Clustered   Not           Supported     Supported    Allocation  supported  ?                                        (continued on next page)   
  Introduction          8    Table 1-1 (Cont.)  OpenVMS File Structure Options - A>    ___________________Comparison______________________________                  ODS-1(VAX>    Characteristonly)_________ODS-2_________ODS-5______________  4    Backup      Not           Supported     Supported    Home Block  supported  ;    Protection  E means       E means       E means "execute 2    code E      "extend" for  "execute      access"$                the RSX-11M   access"                operating                system but                 is ignored                 by system                but is                 ignored                by OpenVMS   >    Enhanced    Not           Enhanced      Enhanced protection=    protection  supported     protection    features supported %    features                  features &    (for                      supported    example, 	    access 
    control	    lists)   4    RMS         Not           Supported     Supported>    journaling__supported______________________________________  =    For details please read Chapter 1 Introduction of Guide to     OpenVMS File Applications.     OpenVMS    BACKUP Utility  <    Save sets created by any version of OpenVMS BACKUP, up to<    and including V7.3, 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.  ?                                               Introduction  1-9          9    Unlike OpenVMS BACKUP, output tapes used by SSMgr must :    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.   '  OpenVMS    License Management Facility   >    SSMgr uses the OpenVMS License Management Facility (LMF) to9    determine if a node is authorized to use the software.     Privileges   <    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.     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.                          
  Introduction              ?                                                               2 > ______________________________________________________________  ?                                          Installation Procedure     /  Preinstallation  Requirements and Preparations   5    This section discusses the system requirements and <    preparations necessary for installing the SSMgr software.  5    The SSMgr kit includes online and hardcopy release 6    notes. Compaq strongly recommends that you read the9    release notes before proceeding with the installation. 4    The release notes for printing to hardcopy are in5    a file named SYS$HELP:SAVESET015_RELEASE_NOTES.PS. /    The online release notes are in a file named %    SYS$HELP:SAVESET015.RELEASE_NOTES.   <    SSMgr requires that your system to be running OpenVMS VAX=    Versions 6.2, 7.1 , 7.2 and 7.3 or OpenVMX Alpha 6.2, 7.1- <    2, 7.2-1 and 7.3. Installation may only be completed on a    per-node basis.    License  Registration  ;    Before you install and run SSMgr on a new node, you must >    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 Space   <    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 SYSPRV   ?                                     Installation Procedure  2-1          :    SSMgr requires 3500 free disk blocks on the system disk=    to install. To determine the number of free disk blocks on ;    your system disk, enter the following command at the DCL 
    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            300       PRCLM            2       TQLM             10  >    PGFLQUOTA________10000_____________________________________    User    Account Quotas   =    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$SYSTEM     $ RUN AUTHORIZE    UAF>     Installation  Procedure         =    At the UAF> prompt, enter the SHOW command with an account 3    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 System .    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 the 
       system.   =    If VMSINSTAL detects any problems during the installation, :    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.   ?                                     Installation Procedure  2-3            Backing    Up Your System Disk   <    At the beginning of the installation procedure, VMSINSTAL;    prompts you about the backup of your system disk. Compaq 6    recommends that you back up your system disk before    installing any software.   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-L     Installing  the SSMgr Software   :    This section contains a step-by-step description of the    installation procedure.    The    Installation Procedure  ;    The SSMgr installation procedure consists of a series of >    questions and informational messages. See Section 2.4 for a    sample installation.   :    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.   9    To abort the installation procedure at any time, enter <    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.   >       @SYS$UPDATE:VMSINSTAL saveset-name device-name OPTIONS N         Where:  >       o  saveset-name-The installation name for the component.=          Use the installation name SAVESET015 when installing           SSMgr.   =       o  device-name-The name of the device on which you plan =          to mount the media. For example, MUA0: is the device :          name for a tape drive. It is not necessary to use=          the console drive for this installation. However, if =          you do use the console drive, you should replace any =          media you removed once the installation is complete.     Installation  Procedure         5       o  OPTIONS N-This is an optional parameter that 8          indicates you want to be prompted to review the;          release notes. If you do not include the OPTIONS N 9          parameter, VMSINSTAL does not issue this prompt.   >          You should review the release notes before proceeding>          with the installation in case they contain additional7          information about the installation. If you are >          restarting the installation and have already reviewed>          the release notes, you do not need to specify OPTIONS          N.   >       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.   8       $ @SYS$UPDATE:VMSINSTAL SAVESET015 MUA0: OPTIONS N  @             VAX/VMS Software Product Installation Procedure V7.3  !       It is 14-MAR-2001 at 07:03.   5       Enter a question mark (?) at any time for help.   9       If you do not supply either the product name or the =       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. :       Otherwise, enter NO to discontinue the installation.=       After you back up your system disk, you can restart the        installation.   $    3. Select a release notes option.  ?                                     Installation Procedure  2-5                 Release Notes Options:           1.  Display release notes        2.  Print release notes        3.  Both 1 and 2         4.  None of the above         * Select option [2]:  <       If you specified OPTIONS N when you invoked VMSINSTAL,=       you are now asked to choose one of the four options for "       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.   ;       If you select option 2, VMSINSTAL prompts you for the 3       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.   >       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 are 1       copied to a file in the SYS$HELP directory.       4. Purge files.  G       * Do you want to purge files replaced by this installation [YES]?   6       You have the option to purge files from previous3       versions of SSMgr that are superseded by this ;       installation. Purging is recommended; however, if you <       need to keep files from the previous version, enter NO"       in response to the question.    Installation  Procedure         :    5. Choose the Installation Verification Procedure (IVP)
       option.   @       * 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.  3       After SSMgr is installed, you can run the IVP <       independently to verify that the software is available9       on your system. You might need to run the IVP after 9       a system failure to make sure that users can access 9       SSMgr. You can run the IVP independently by running        SYS$TEST:SAVESET$IVP.COM.   (    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, ;       answer NO and the installation will continue, but the 8       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.  A          Installation of Save Set Manager V1.5 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. Note >       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 log        out and log in again.     ?                                     Installation Procedure  2-7            Error    Recovery  5    If errors occur during the installation procedure, ;    VMSINSTAL displays failure messages. If the installation -    fails, you will see the following message:   N    %VMSINSTAL-E-INSFAIL, The installation of Save Set Manager V1.5 has failed.  1    If the IVP fails, you will see these messages:   H    The Save Set Manager V1.5 Installation Verification Procedure failed.  F    %VMSINSTAL-E-IVPFAIL, The IVP for Save Set Manager V1.5 has failed.  9    Errors can occur during the installation if any of the     following conditions exist:  0    o  The operating system version is incorrect.  6    o  Quotas necessary for successful installation are       insufficient.   =    o  System parameter values for successful installation are        insufficient.   >    o  An image mismatch error is issued while running the IVP.    SSMgr  Sample Installation   <    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.  7    $ @sys$update:vmsinstal saveset015 disk$user:[ELVIS]   ;    OpenVMS VAX Software Product Installation Procedure V7.3   2    Enter a question mark (?) at any time for help.  G    %VMSINSTAL-W-NOTSYSTEM, You are not logged in to the SYSTEM account. A    %VMSINSTAL-W-ACTIVE, The following processes are still active:     Installation  Procedure              UCX$NTPD     DECW$SERVER_0      UCX$TFTP_BG8     DECW$MWM     VUE$ELVIS_2      VUE$ELVIS_3      VUE$ELVIS_4      VUE$ELVIS_5      DECW$TE_0068	     ELVIS +    * Do you want to continue anyway [NO]? y C    * Are you satisfied with the backup of your system disk [YES]? y   ,    The following products will be processed:        SAVESET V1.5   2    Beginning installation of SAVESET V1.5 at 10:15  9    %VMSINSTAL-I-RESTORE, Restoring product save set A ... N    %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.  -    Copyright Compaq Computer Corporation 2001     All rights reserved.   D    %SAVESET-I-VMSOK, Installing SAVESET V1.5 on OpenVMS Version V7.3F    * Do you want to purge files replaced by this installation [YES]? y?    * Do you want to run the IVP after the installation [YES]? y   )            Product:      SAVE-SET-MANAGER             Producer:     Compaq             Version:      1.5&            Release Date: 14-March-2001  I    * Does this product have an authorization key registered and loaded? y 9    %VMSINSTAL-I-RESTORE, Restoring product save set B ...   /     The Save Set Manager for OpenVMS User Guide 5     has been moved to SYS$HELP:SAVESET_USER_GUIDE.PS.   Q    %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...   -    This is the SAVESET IVP command procedure.       $ saveset validate blue.bck!    ERRORS terminal option enabled !    EVENTS terminal option enabled P    Primary input save set ELVIS$DKB300:[SYS0.SYSUPD.SAVESET015]BLUE.BCK;1 opened;      Save Set Manager V1.5  Time: 14-March-2001 10:16:50.03   ?                                     Installation Procedure  2-9          !        SAVESET function: VALIDATE N        Primary input save set: ELVIS$DKB300:[SYS0.SYSUPD.SAVESET015]BLUE.BCK;1          No journal file%        Final status of each save set: H          Save set name:  ELVIS$DKB300:[SYS0.SYSUPD.SAVESET015]BLUE.BCK;1     No errors detected       $ saveset validate yellow.bck!    ERRORS terminal option enabled !    EVENTS terminal option enabled R    Primary input save set ELVIS$DKB300:[SYS0.SYSUPD.SAVESET015]YELLOW.BCK;1 opened:      Save Set Manager V1.5 Time: 14-March-2001 10:16:51.80  !        SAVESET function: VALIDATE P        Primary input save set: ELVIS$DKB300:[SYS0.SYSUPD.SAVESET015]YELLOW.BCK;1          No journal file%        Final status of each save set: J          Save set name:  ELVIS$DKB300:[SYS0.SYSUPD.SAVESET015]YELLOW.BCK;1     No errors detected  "    $ saveset copy blue.bck red.bck!    ERRORS terminal option enabled !    EVENTS terminal option enabled P    Primary input save set ELVIS$DKB300:[SYS0.SYSUPD.SAVESET015]BLUE.BCK;1 openedG    Output save set ELVIS$DKB300:[SYS0.SYSUPD.SAVESET015]RED.BCK; opened 8    Save Set Manager V1.5 Time: 14-March-2001 10:16:53.88          SAVESET function: COPY N        Primary input save set: ELVIS$DKB300:[SYS0.SYSUPD.SAVESET015]BLUE.BCK;1          No journal fileE        Output save set: ELVIS$DKB300:[SYS0.SYSUPD.SAVESET015]RED.BCK;           No journal file%        Final status of each save set: H          Save set name:  ELVIS$DKB300:[SYS0.SYSUPD.SAVESET015]BLUE.BCK;1     No errors detectedF          Save set name:  ELVIS$DKB300:[SYS0.SYSUPD.SAVESET015]RED.BCK;     No errors detected                Installation   Procedure          0    $ saveset merge blue.bck yellow.bck green.bck!    ERRORS terminal option enabled !    EVENTS terminal option enabled P    Primary input save set ELVIS$DKB300:[SYS0.SYSUPD.SAVESET015]BLUE.BCK;1 openedM    Secondary input save set ELVIS$DKB300:[SYS0.SYSUPD.SAVESET015]YELLOW.BCK;1 	    opened I    Output save set ELVIS$DKB300:[SYS0.SYSUPD.SAVESET015]GREEN.BCK; opened 8    Save Set Manager V1.5 Time: 14-March-2001 10:16:56.18          SAVESET function: MERGEN        Primary input save set: ELVIS$DKB300:[SYS0.SYSUPD.SAVESET015]BLUE.BCK;1          No journal fileQ        Secondary input save set:ELVIS$DKB300:[SYS0.SYSUPD.SAVESET015]YELLOW.BCK;1           No journal fileH        Output save set: ELVBIS$DKB300:[SYS0.SYSUPD.SAVESET015]GREEN.BCK;          No journal file%        Final status of each save set: H          Save set name:  ELVIS$DKB300:[SYS0.SYSUPD.SAVESET015]BLUE.BCK;1     No errors detectedJ          Save set name:  ELVIS$DKB300:[SYS0.SYSUPD.SAVESET015]YELLOW.BCK;1     No errors detectedH          Save set name:  ELVIS$DKB300:[SYS0.SYSUPD.SAVESET015]GREEN.BCK;     No errors detected  @    The SAVESET IVP command procedure has successfully completed.3     Installation of SAVESET V1.5 completed at 10:16   %     VMSINSTAL procedure done at 10:17     Reporting  Product Problems  8    If you encounter a problem while using this software,9    report it to Compaq Customer Services in the U.S.A. 1- ;    800-354-9000. In other countries, report it through your     usual support channels.                  ?                                    Installation Procedure  2-11              ?                                                               3 > ______________________________________________________________  ?                                                     Using SSMgr     :    This chapter describes how to use SSMgr, from preparing5    save sets to using the command language interface.   &  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 SSMgr >    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. ;       It is a collection of files saved for some particular 
       reason.   >    Physical save sets (copies of entire volumes) are supported9    by SSMgr for VALIDATE and COPY operations, but not for     MERGE operations.    Input    Save Sets   ;    Input save sets may have been created by OpenVMS BACKUP, 8    by SSMgr, or by some other entity that creates valid,;    OpenVMS save sets. For SSMgr to operate on an input save 9    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.   ?                                                Using SSMgr  3-1          :    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, <    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 that <    SSMgr can appropriately access input and output save sets0    that are contained in files on various media.    Input      Save Sets on Disk   7    SSMgr can read save sets on any disk that is locally >    connected and mounted Files-11. The process wishing to read;    those files must be suitably privileged for read access. >    The disk may be a single disk volume or a bound volume set.  =    Standard OpenVMS defaults apply in specifying the pathname <    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 save :    sets may be on the same or different devices, or in the!    same or different directories.   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. SSMgr ;    can read save sets on any tape that is locally connected =    and mounted Files-11. SSMgr will always open any tape file =    containing a save set read only. It does not matter if the <    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 command <    line. If /REWIND is specified, SSMgr will first rewind to.    BOT and then search for the specified file.  
  Using  SSMgr          <    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.   .  Input      Save Sets on Multivolume Tape Sets  3    A file containing a save set may span tapes in a ;    multivolume tape set. If that is so, the tapes must have ;    been mounted in a manner that allows 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.=    The MTAACP performs a number of checks on the continuation >    volume that is loaded into the tape drive, be it by a human=    or by a mechanical loader. Two checks that are significant <    for input save sets that span tapes are the label (volume8    identifier) check and the set id (fileset identifier)	    check.   ;    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 tape =    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 first <    tape has a label of ABCDEF, the second and third would be;    labeled ABCD02 and ABCD03. If the first tape has a label ;    of AB, the second and third would be labeled AB__02  and 
    AB__03.  ;    If SSMgr will be processing an input save set that spans 6    tapes (whether it is an operation on a single large9    save set or an operation that processes many save sets 8    through the use of wildcards and the /ALL qualifier),  ?                                                Using SSMgr  3-3          8    the multivolume set must be appropriately mounted for;    continuation. If the labeling of the continuation volume <    does not fit the labeling scheme recognized by MTAACP, it=    will not mount and make available that volume for reading. =    If the multivolume tape set follows the canonical labeling ;    scheme described above, it will mount and make available =    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. It =    does not carry over to continuation volumes. Therefore, if <    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 cannot >    continue, because the MTAACP will accept nothing other than    a tape labeled BEAT02.   3    A second check made by the MTAACP is the fileset ;    identifier. In some instances, continuation volumes that =    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.   ;    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=SETID 0    qualifier on the $MOUNT command. For example,  B        $ MOUNT/OVERRIDE=SETID MUA0:  BEATLE,JOHN,PAUL,GEORGE,RINGO      
  Using  SSMgr            Output    Save Sets  >    Output save sets may be created by SSMgr on any nonnetwork-;    accessed disk, bound volume set, or tape device. As with 9    input save sets, that device must be mounted Files-11.     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 disk      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 single :    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 to     mounting for use by SSMgr.   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, 2    overwriting whatever may have been on the tape.  :    See Section 3.1.4 for special considerations around the)    creation of multiple output save sets.   8    For the use of wildcards in specifying pathnames, see    Section 3.2.   ?                                                Using SSMgr  3-5          /  Output      Save Sets on Multivolume Tape Sets   >    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 allows >    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 the 7    parameters and qualifiers that had been specified in 8    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 to     output save sets:  2        $ MOUNT MUA0: BEATLE,JOHN,PAUL,GEORGE,RINGO  9    In this example, five tapes have been initialized with 9    the tape labels BEATLE, JOHN, PAUL, GEORGE, and RINGO. :    The tape that had been initialized as BEATLE is loaded,=    and the $MOUNT command issued. When that tape is full, the =    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 MTAACP :    issues an OPCOM message requesting that relative volume=    2, JOHN, be mounted. If a tape initialized with label JOHN =    is loaded into the drive, operations will continue on that <    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: BEATLE   7    In this example, only the label of the first tape is 9    specified on $MOUNT command line. A tape that had been 9    initialized as BEATLE is loaded and the $MOUNT command 7    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          =    what labels are expected when continuation tape labels are 0    not explicitly specified on the command line.  3        $ MOUNT/INITIALIZE=CONTINUATION MUA0: BEATLE   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.   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 as :    continuation tapes. This requires responding to MTAACP-;    generated OPCOM messages with the /BLANK_TAPE qualifier.     For example:   ?        %%%%%%%%%%%  OPCOM, 14-MAR-2001 15:23:31.78  %%%%%%%%%%% "        request 3, from user SNYDER4        MOUNT new relative volume 2 (BEAT02) on MUA0:  7    With OPER and VOLPRO privileges, the following reply <    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 (or ;    whatever you specify as the label you want), and mounted '    in the drive, allowing continuation.   <    If a continuation tape is loaded that has been formatted,;    but the tape has a label that is not the one expected by :    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:   '        $ REPLY/INITIALIZE_TAPE=3 "JOHN"   8    In this case, the tape will be relabeled as JOHN, and    operations will continue.  ?                                                Using SSMgr  3-7            Files-11    Mount Example  9    Example 3-1 shows a session in which an image save set :    on tape is merged with an incremental save set on disk.9    The resulting "virtual" image save set is written to a     multivolume tape.       Example 3-1  A Files-11 Mount       $ INITIALIZE MKB200: MERGE0 1     $ INITIALIZE MKB200: MERGE1 2    $ MOUNT MKB100: IMAGE 3-    %MOUNT-I-MOUNTED, IMAGE mounted on MKB100: "    $ 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 enabled !    EVENTS terminal option enabled #    Opening file MKB100:[]FULL.BCK;1 4    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; -    Output save set MKB200:[]MERGE.BCK; opened   9     Save Set Manager V1.5 Time: 14-March-2001 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 detected   4          Save set name:  DISK$USER:[ELVIS]INCR.BCK;1            No errors detected   ?                                        (continued on next page)   
  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 the        drive.  9    3  The device containing the primary input save set is        mounted Files-11.   >    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.   %    6  The input device is dismounted.   ;    7  The output device is dismounted, completing the merge        operation.    Multiple    Output Save Sets   ;    SSMgr provides the ability to make up to 5 copies of any >    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,   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. =    Two of the copies are being written to disk, and two other 9    are being written to tape. The copies being written to 9    disk are being written to the default directory and to   ?                                                Using SSMgr  3-9          =    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 last :    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 output >    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.   ;    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 move =    to the next input save set, if any, and continue operation     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 allow +    the offending condition to be corrected.   =    There are several performance and resource implications to '    producing multiple output save sets:   >    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, /       all others must wait until it's complete.     Using   SSMgr         <    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, an <       optimization that does not transfer to multiple output       save set operations.                                                              ?                                               Using SSMgr  3-11          3  Wildcards  in Save Set and Journal File Specifiers   ;    SSMgr supports standard OpenVMS wildcarding of input and ;    output save set specifiers, as well as journal file name 9    specifiers. However, because of the semantics of SSMgr (    commands, there are some constraints.  +  Wildcard    Constraints on Input Save Sets   <    By default, if a wildcard is used in the name of an input7    save set, only the first matching file found will be 8    used. This is true for VALIDATE, COPY, and MERGE. For;    VALIDATE and COPY, you can elect to operate on all files <    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 semantic     implications. For example:   '        $ SAVESET COPY *.BCK FOO.BCK/ALL   ;    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, but :    a different version number. If there is a version limit=    placed on the directory, the first several copies could be ,    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.   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 specifier &    dua1:[foo]bar.baz;3 breaks down as:    Using   SSMgr                 device:     dua1:        directory:  [foo]        file name:  bar        file type:  .baz         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 file :    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 be 9    DUA1:[MUMBLE]BAR.BAZ;6 because the file name component 7    contains the wildcard and the file type component is 9    missing. Therefore, both of those components mimic the :    corresponding component from the primary input save set    specification.   .  Wildcard    Constraints on Journal File Names  8    As with output save set specifiers, journal file name;    specifiers may contain wildcard characters. If the "file ;    name" component of the journal file specifier contains a 9    wild card, the "file name" component of the associated 9    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.   E        Example 1:  SAVESET VALIDATE DUA0:[FOO]BAR.BAZ;3/JOURNAL=*.JOU   H        In this case, the journal file would be written to BAR.JOU in the        default directory.   G        Example 2: SAVESET VALIDATE DUA0:[FOO]BAR.BAZ;3/JOURNAL=FOOBAR.*   H        In this case, the journal file would be written to BAR.JOU in the        default directory.   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.   ?                                               Using SSMgr  3-13          "  SSMgr  Command Language Interface  9    This section describes the valid commands for SSMgr. A ;    matrix of commands and qualifiers is shown in Table 3-1.   >    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       Yes   +    /CHECKS          Yes       Yes       Yes   +    /COMMENT         No        Yes       Yes   +    /CRC             No        Yes       Yes   +    /FULL            Yes       Yes       Yes   +    /GROUP_SIZE      No        Yes       Yes   *    /IDENTICAL       No        Yes       No  +    /JOURNAL         Yes       Yes       Yes   +    /LOG_FILE        Yes       Yes       Yes   *    /OVERRIDE        No        Yes       No  +    /REWIND          Yes       Yes       Yes   >    /TERMINAL________Yes_______Yes_______Yes___________________              Using   SSMgr         > ______________________________________________________________        Copies a save set.     3    COPY  input-ss output-ss [output-ss] [output-ss]            [output-ss] [output-ss]          input-ss *    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.     >    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 protection =    to be present, absent, or the same as the source save set. =    The default is to make the output save set the same as the <    input save set. The desired block size of the output save=    set can also be specified as different from the input save 9    set. The COPY command regenerates any bad blocks found     during the operation.  <       ________________________ Note ________________________  9       The size of the save set after a COPY operation may ;       be slightly smaller than the original save set due to :       the way the OpenVMS BACKUP utility formats the data.  ?                                               Using SSMgr  3-15          9       SSMgr repacks its data records during processing to 9       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                   /ALL     /[NO]ALL (default)       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 name :    found that matches the wildcarded file specification is
    processed.   8    The qualifier is valid only for the VALIDATE and COPY
    functions.       The default is /NOALL.       /BLOCK_SIZE=n      Output save set qualifier  9    This qualifier specifies the desired block size of the ;    output save set. Valid values for n are between 2048 and <    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.   :    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.   5    This qualifier may not be used with the /IDENTICAL 
    qualifier.   7    The default is the block size of the input save set.       /BRIEF (default)   ?                                               Using SSMgr  3-17              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 for the'    complete list of output information.       The default is /BRIEF.                                                                         Using   SSMgr             /CHECKS=([NO]CRC, [NO]XOR)       Input save set qualifier   ;    This qualifier specifies the optional consistency checks <    that will be performed on the input save set; the default    is CRC, XOR.   ;    You must specify the /CHECKS qualifier immediately after ;    the file name of each input save set when specifying the 8    input save set. Example 3-12 also shows that when you9    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 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.   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 processing completes.      /COMMENT=string      Output save set qualifier  ;    This qualifier inserts a comment in the output save set. 9    The comment string can be up to 252 characters. If the ;    comment string is longer than one word or if it contains 6    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.   >    The default is no comment string written to the output save    set.   ?                                               Using SSMgr  3-19              /CRC 	    /NOCRC       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 is <    computed and stored in the output save set only if it was!    present in the input save set.   5    This qualifier may not be used with the /IDENTICAL 
    qualifier.   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             /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 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 set        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.       /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.   <    If this qualifier is not specified, the group size of the=    input save set is used for the output save set group size.     This is the default action.  5    This qualifier may not be used with the /IDENTICAL 
    qualifier.   ?                                               Using SSMgr  3-21            
    /IDENTICAL       Command qualifier  9    This qualifier does a fast copy of the input save set. :    A fast copy operation copies the contents of each input;    save set block to the output save set without validation :    of the block's internal record structure. If errors are;    encountered during this operation, restart the operation <    and include the /OVERRIDE qualifier to continue operation;    even in spite of the errors. See the /OVERRIDE qualifier     description below.   =    Each save set is stored with information that reflects the <    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. With :    the /IDENTICAL qualifier, this information reflects the7    environment in which the input save set was created.   <    The /IDENTICAL qualifier is not supported for multivolume;    output save sets, because you may not be able to restore     such a save set.   <    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.       /JOURNAL[=journal-file-name]       Save set qualifier   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. >    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.     Using   SSMgr         :    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 as     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.  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.   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-23          %    /LOG_FILE[=logfile-name] (default)     /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 log =    file by using /NOLOG_FILE or by including /LOG_FILE=NL: on <    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 processing        input or output save sets       o  Operator requests   <    Wildcards may not be used in the specification of logfile	    names.       /OVERRIDE    /NOOVERRIDE (default)      Command qualifier  9    This qualifier allows you to override certain internal 9    consistency checks to allow execution to continue with <    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 set :    errors. The /IDENTICAL and /OVERRIDE qualifiers must be:    specified in that order on the command line as shown in    Example 3-4.     Using   SSMgr         
    /REWIND    /NOREWIND (default)  %    Input or output 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 or writing the volume. If /ALL was ;    specified, the rewind only happens once before the first     SAVESET operation.   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:   =    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 current        position of the tape.   <    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.   9    The default for this qualifier is /NOREWIND. On input, 9    the tape will be searched starting at the current tape >    position. On output, the new file will be opened at end-of-    data.  .    /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) are     displayed as they occur.   ?                                               Using SSMgr  3-25          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.7    The /TERMINAL=LOG qualifier may not be used with the     /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 an        EVENT.  <       ______________________________________________________  2    The default is /TERMINAL=(ERRORS,EVENTS,NOLOG).                                                      Using   SSMgr                   Example 3-2  COPY Command  G    $ saveset copy mkb200:savesetua013.B/rewind disk$user:[kits]copy.sav !    ERRORS terminal option enabled !    EVENTS terminal option enabled +    Rewinding MKB200: to beginning of volume     Rewind of MKB200: complete %    Opening file MKB200:[]SAVESET015;1 6    Primary input save set MKB200:[]SAVESET015;1 opened3    Output save set DISK$USER:[KITS]COPY.SAV; opened   8    Save Set Manager V1.5 Time: 14-March-2001 13:45:05.49          SAVESET function: COPY 4        Primary input save set: MKB200:[]SAVESET015;1          No journal file1        Output save set: DISK$USER:[KITS]COPY.SAV;           No journal file  %        Final status of each save set:   .          Save set name:  MKB200:[]SAVESET015;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, SAVESET015, is copied from that>       tape to a file called copy.sav on disk$user:[kits], with-       all save set characteristics preserved.   ;    Example 3-3  COPY Command with Multiple Output Save Sets   ?                                        (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=20 !    ERRORS terminal option enabled !    EVENTS terminal option enabled ?    Primary input save set DISK$USER:[NDIAMOND]FULL.BCK;1 opened #    Opening file MKB200:[]IMAGE.BCK; -    Output save set MKB200:[]IMAGE.BCK; opened $    Opening file MKB500:[]FULL20.BCK;.    Output save set MKB500:[]FULL20.BCK; opened  8    Save Set Manager V1.5 Time: 14-March-2001 13:56:01.74          SAVESET function: COPY =        Primary input save set: DISK$USER:[NDIAMOND]FULL.BCK;1           No journal file+        Output save set: MKB200:[]IMAGE.BCK;           No journal file,        Output save set: MKB500:[]FULL20.BCK;          No journal file  %        Final status of each save set:   7          Save set name:  DISK$USER:[NDIAMOND]FULL.BCK;1             No errors detected   ,          Save set name:  MKB200:[]IMAGE.BCK;            No errors detected   -          Save set name:  MKB500:[]FULL20.BCK;             No errors detected   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 size >       on the input save set. A second copy is being written to<       the tape mounted on MKB500. For this copy, the name of  ?                                        (continued on next page)     Using   SSMgr         >    Example 3-3 (Cont.)  COPY Command with Multiple Output Save                         Sets  >       the save set is changed to FULL20.BCK, the group size is=       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 enabled !    EVENTS terminal option enabled +    Rewinding MKB200: to beginning of volume     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;1 C    CRC error: block number 35 in save set DISK$USER:[GRD]STAR.SAV;1 >    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;1 C    CRC error: block number 48 in save set DISK$USER:[GRD]STAR.SAV;1 >    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;1 >    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  9    Save Set Manager V1.5  Time: 14-March-2001 14:38:49.31   ?                                        (continued on next page)           ?                                               Using SSMgr  3-29          7    Example 3-4 (Cont.)  COPY Command with IDENTICAL and <                         OVERRIDE Qualifiers on Save Set with                         Errors          SAVESET function: COPY ;        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:   5          Save set name:  DISK$USER:[GRDEAD]STAR.SAV;1 0          Unrecoverable CRC errors:             30          Recoverable CRC errors:               20          XOR errors:                           2  +          Save set name:  MKB200:[]ROCK.BCK;             No errors detected   7       In Example 3-4, a copy of the save set, STAR.SAV, <       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 information 8       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 set "       may not be fully restorable.  9    Example 3-5  COPY with Wildcarding, Journaling, and No                  Logfile   ?                                        (continued on next page)               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"     _Output Save Set 2:!    ERRORS terminal option enabled !    EVENTS terminal option enabled @    Primary input save set DKA400:[DCSC030.KIT]DCSC030.A;1 opened#    Opening file MKB200:[]DCSC030.A; -    Output save set MKB200:[]DCSC030.A; opened   8    Save Set Manager V1.5 Time: 14-March-2001 14:53:20.21          SAVESET function: COPY >        Primary input save set: DKA400:[DCSC030.KIT]DCSC030.A;15          Journal file: DISK$GREEN:[DRAGON]DCSC030.BJL +        Output save set: MKB200:[]DCSC030.A;           No journal file  %        Final status of each save set:   8          Save set name:  DKA400:[DCSC030.KIT]DCSC030.A;1            No errors detected   ,          Save set name:  MKB200:[]DCSC030.A;            No errors detected   @    Primary input save set DKA400:[DCSC030.KIT]DCSC030.B;1 opened#    Opening file MKB200:[]DCSC030.B; -    Output save set MKB200:[]DCSC030.B; opened   8    Save Set Manager V1.5 Time: 14-March-2001 14:56:45.83          SAVESET function: COPY >        Primary input save set: DKA400:[DCSC030.KIT]DCSC030.B;15          Journal file: DISK$GREEN:[DRAGON]DCSC030.BJL +        Output save set: MKB200:[]DCSC030.B;           No journal file  %        Final status of each save set:   ?                                        (continued on next page)   ?                                               Using SSMgr  3-31          >    Example 3-5 (Cont.)  COPY with Wildcarding, Journaling, and"                         No Logfile  8          Save set name:  DKA400:[DCSC030.KIT]DCSC030.B;1            No errors detected   ,          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   8    Save Set Manager V1.5 Time: 14-March-2001 15:02:50.30          SAVESET function: COPY >        Primary input save set: DKA400:[DCSC030.KIT]DCSC030.C;15          Journal file: DISK$GREEN:[DRAGON]DCSC030.BJL +        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 detected   ,          Save set name:  MKB200:[]DCSC030.C;            No errors detected         Summary of COPY operations   1        Total operations attempted:              3 1        Operations completing successfully:      3     $  *       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 and <       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 set <       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  ?                                        (continued on next page)     Using   SSMgr         >    Example 3-5 (Cont.)  COPY with Wildcarding, Journaling, and"                         No Logfile  :       second and third save sets' journal file entries are=       appended to the journal file created for the first save 
       set.  ;    Example 3-6  COPY with /JOURNAL and /TERMINAL Qualifiers   .    $ saveset copy/terminal=(errors,events,log)-    _Input Save Set: mkb200:SAVESET015/journal     _Output Save Set: saveset015     _Output Save Set 2:    LOG terminal option enabled!    ERRORS terminal option enabled !    EVENTS terminal option enabled %    Opening file MKB200:[]SAVESET015;1 6    Primary input save set MKB200:[]SAVESET015;1 opened9    Output save set DISK$USER:[SOFTWARE]SAVESET015; opened >    Processing user file: [SOFTWARE.SAVESET015]KITINSTAL.COM;29@    Processing user file: [SOFTWARE.SAVESET015]SAVESET$IVP.COM;14;    Processing user file: [SOFTWARE.SAVESET015]SAVESET.CLD;4 ;    Processing user file: [SOFTWARE.SAVESET015]SAVESET.HLP;4 .    Processing user file: [SOFTWARE.SAVESET015]     SAVESET015.RELEASE_NOTES;3.    Processing user file: [SOFTWARE.SAVESET015]!     SAVESET015_RELEASE_NOTES.PS;5 .    Processing user file: [SOFTWARE.SAVESET015]     SAVESET_COVER_LETTER.PS;6 .    Processing user file: [SOFTWARE.SAVESET015]     SAVESET_USER_GUIDE.PS;17.    Processing user file: [SOFTWARE.SAVESET015]     SAVESET_USER_GUIDE.TXT;8  8    Save Set Manager V1.5 Time: 14-March-2001 15:31:56.90    ?                                        (continued on next page)             ?                                               Using SSMgr  3-33          8    Example 3-6 (Cont.)  COPY with /JOURNAL and /TERMINAL"                         Qualifiers          SAVESET function: COPY 4        Primary input save set: MKB200:[]SAVESET015;1$          Journal file: SAVESET015JL;7        Output save set: DISK$USER:[SOFTWARE]SAVESET015;           No journal file  %        Final status of each save set:   .          Save set name:  MKB200:[]SAVESET015;1            No errors detected   8          Save set name:  DISK$USER:[SOFTWARE]SAVESET015;            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 SAVESET015;       from the tape mounted on MKB200 to the directory from >       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 want =       another copy, hit <return>. A journal file of the name, 6       SAVESET015JL, is created in that same directory.  =    Example 3-7  COPY with /BLOCK_SIZE, /GROUP_SIZE, and /FULL                  Qualifiers  (    $ saveset copy/full mkb200:SAVESET015;    _Output Save Set: copy.sav/block_size=3072/group_size=20     _Output Save Set 2:!    ERRORS terminal option enabled !    EVENTS terminal option enabled %    Opening file MKB200:[]SAVESET015;1 6    Primary input save set MKB200:[]SAVESET015;1 opened7    Output save set DISK$USER:[SOFTWARE]COPY.SAV; opened   ?                                        (continued on next page)           Using   SSMgr         ?    Example 3-7 (Cont.)  COPY with /BLOCK_SIZE, /GROUP_SIZE, and (                         /FULL Qualifiers  9    Save Set Manager V1.5  Time: 14-March-2001 15:42:28.56           SAVESET function: COPY 4        Primary input save set: MKB200:[]SAVESET015;1          No journal file5        Output save set: DISK$USER:[SOFTWARE]COPY.SAV;           No journal file  %        Final status of each save set:   .          Save set name:  MKB200:[]SAVESET015;11          Save set group size:                  25 3          Save set block size:                  9216 2          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)                   ?                                               Using SSMgr  3-35          ?    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:                  3072 2          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 detected   2       In Example 3-7, the save set, SAVESET015, 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. >       Note the prompt for an additional output save set if all;       the information is not entered on the initial command >       line. A full report will be generated upon completion of       the copy operation.                           Using   SSMgr         > ______________________________________________________________        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-ss ;    OpenVMS file name of an input save set. The primary save :    set can be an image, incremental, or file-oriented save    set.       secondary-input-ss 7    OpenVMS file name of a secondary input save set. The >    secondary input save set is an incremental or file-oriented=    save set that covers a period of time starting at the time $    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 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 primary input save set. :    Different qualifiers may be applied to each output save    set.     =    The MERGE operation takes two OpenVMS BACKUP save sets and :    produces 1 to 5 output save sets. Acceptable input save=    sets include image backups, incremental backups, and file- :    oriented save sets. The following combinations of input>    primary and secondary save sets result in the listed output
    save sets:             ?                                               Using SSMgr  3-37          >    ___________________________________________________________$    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 the 9    time that the secondary input save set was created. If 9    the primary and secondary save sets were incrementals, 7    the output save set will contain an incremental save :    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, an <    attempt to merge a primary save set with an inappropriate5    incremental save set, such as from another disk or 9    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             Output save set qualifier  9    This qualifier specifies the desired block size of the ;    output save set. Valid values for n are between 2048 and <    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.   5    As required by OpenVMS BACKUP, the upper limit for 9    save sets on disks is 32256. If a larger block size is 0    specified, SSMgr will round it down to 32256.      /BRIEF (default)       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 for )    a complete list of output information.       /CHECKS=([NO]CRC,[NO]XOR)      Input save set qualifier   ;    This qualifier specifies the optional consistency checks <    that will be performed on the input save set; the default    is CRC, XOR.   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 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 CRC is compared against the CRC     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 is <    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. 9    The string can be up to 252 characters. If the comment 8    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.         /CRC 	    /NOCRC       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 is <    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 /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  ?                                               Using SSMgr  3-41          '       Alias directory files in save set        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                                                                  Using   SSMgr               /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]       Save set qualifier   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. >    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.   :    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 as     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.  ?                                               Using SSMgr  3-43          <    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. 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.                                                                         Using   SSMgr         %    /LOG_FILE[=logfile-name] (default)     /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 is :    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 bu including >    /LOG_FILE=NL: on 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 processing        input save sets       o  Operator requests   <    Wildcards may not be used in the specification of logfile	    names.   
    /REWIND    /NOREWIND (default)  %    Input or output 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.  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 for ;       the specified file starting at the BOT position. This ;       allows SSMgr to find files located before the current        position of the tape.   ?                                               Using SSMgr  3-45          <    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) are     displayed as they occur.   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 the 9       default disk directory. Two copies of the resultant :       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             Example 3-8  MERGE Command   ?    $ saveset merge full.bck incr.bck merge.bck mkb500:merge.bck !    ERRORS terminal option enabled !    EVENTS terminal option enabled >    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; opened #    Opening file MKB500:[]MERGE.BCK; -    Output save set MKB500:[]MERGE.BCK; opened   8    Save Set Manager V1.5 Time: 14-March-2001 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;           No journal file  %        Final status of each save set:   6          Save set name:  DISK$MUSIC:[MOZART]FULL.BCK;1            No errors detected   6          Save set name:  DISK$MUSIC:[MOZART]INCR.BCK;1            No errors detected   6          Save set name:  DISK$MUSIC:[MOZART]MERGE.BCK;            No errors detected ,          Save set name:  MKB500:[]MERGE.BCK;            No errors detected                   ?                                               Using SSMgr  3-47            =    Example 3-9  MERGE Command with /FULL, /LOG, and /TERMINAL                  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 enabled !    EVENTS terminal option enabled ?    Primary input save set DISK$MUSIC:[EAGLES]INCR2.BCK;1 opened A    Secondary input save set DISK$MUSIC:[EAGLES]INCR3.BCK;1 opened 7    Output save set DISK$MUSIC:[EAGLES]INCR4.BCK; opened   8    Save Set Manager V1.5 Time: 14-March-2001 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;1           No journal file5        Output save set: DISK$MUSIC:[EAGLES]INCR4.BCK;           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;1 1          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-49          ;    Example 3-9 (Cont.)  MERGE Command with /FULL, /LOG, and ,                         /TERMINAL Qualifiers  7          Save set name:  DISK$MUSIC:[EAGLES]INCR3.BCK;1 1          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:          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         ;    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 detected   <       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 set =       in the file, incr4.bck. A full report is generated upon =       completion of the merge operation. All errors, if there <       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.                       ?                                               Using SSMgr  3-51            >    Example 3-10  MERGE Command with /FULL, /TERMINAL, /CHECKS,#                  and CRC Qualifiers     &    $ 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 enabled !    EVENTS terminal option enabled ?    Primary input save set DISK$BIRD:[HUMMING]INCR2.BCK;1 opened A    Secondary input save set DISK$BIRD:[HUMMING]INCR3.BCK;1 opened 7    Output save set DISK$BIRD:[HUMMING]INCR4.BCK; opened   8    Save Set Manager V1.5 Time: 14-March-2001 16:30:30.88          SAVESET function: MERGE=        Primary input save set: DISK$BIRD:[HUMMING]INCR2.BCK;1           No journal file?        Secondary input save set: DISK$BIRD:[HUMMING]INCR3.BCK;1           No journal file5        Output save set: DISK$BIRD:[HUMMING]INCR4.BCK;           No journal file  %        Final status of each save set:   ?                                        (continued on next page)                                 Using   SSMgr         =    Example 3-10 (Cont.)  MERGE Command with /FULL, /TERMINAL, 4                          /CHECKS, and CRC Qualifiers  7          Save set name:  DISK$BIRD:[HUMMING]INCR2.BCK;1 1          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          =    Example 3-10 (Cont.)  MERGE Command with /FULL, /TERMINAL, 4                          /CHECKS, and CRC Qualifiers  7          Save set name:  DISK$BIRD:[HUMMING]INCR3.BCK;1 1          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:          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         =    Example 3-10 (Cont.)  MERGE Command with /FULL, /TERMINAL, 4                          /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 detected   :       Example 3-10 shows the merge of two incremental save7       sets, incr2.bck and incr3.bck, into the save set, ;       incr4.bck. A full report is generated upon completion =       of the merge operation. All events are displayed to the <       terminal. CRC and XOR checking is performed on both of;       the input save sets, incr2.bck, and incr3.bck. CRC is .       added to the merged save set, incr4.bck.                        ?                                               Using SSMgr  3-55            ?    Example 3-11  MERGE Command with Journaling on All Save Sets   .    $ saveset merge incr2.bck/journal=incr2.bjl3    _Secondary Save Set: incr3.bck/journal=incr3.bjl 0    _Output Save Set: incr4.bck/journal=incr4.bjl    _Output Save Set 2:!    ERRORS terminal option enabled !    EVENTS terminal option enabled =    Primary input save set DISK$BEE:[BONNET]INCR2.BCK;1 opened ?    Secondary input save set DISK$BEE:[BONNET]INCR3.BCK;1 opened 5    Output save set DISK$BEE:[BONNET]INCR4.BCK; opened   8    Save Set Manager V1.5 Time: 14-March-2001 16:40:04.67          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;1             No errors detected   5          Save set name:  DISK$BEE:[BONNET]INCR3.BCK;1             No errors detected   4          Save set name:  DISK$BEE:[BONNET]INCR4.BCK;            No errors detected   :       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         > ______________________________________________________________    :    Validates the internal consistency and readability of a    save set.        VALIDATE  input-ss           input-ss +    OpenVMS file name of the input save set.       >    The SSMgr VALIDATE command reads an OpenVMS BACKUP save set;    and verifies that at least one copy of each block of the <    specified save set is readable or can be regenerated with5    OpenVMS BACKUP or by using the SSMgr COPY command.   >    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 reported     to the user.       /ALL     /[NO]ALL (default)         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 file specification are processed.     ?                                               Using SSMgr  3-57          7    If NOALL is specified, then only the first file name :    found that matches the wildcarded file specification is
    processed.   8    The qualifier is valid only for the VALIDATE and COPY
    functions.       The default is /NOALL.       /BRIEF (default)       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 for )    a complete list of output information.       The default is /BRIEF.       /CHECKS=([NO]CRC,[NO]XOR)      Input save set qualifier   ;    This qualifier specifies the optional consistency checks 0    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 in >    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 is <    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 is <    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.     Using   SSMgr         7    Each of these options requires additional processing 8    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 or "    user when processing completes.  $    The default is /CHECKS=(CRC,XOR).      /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 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 set        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.       /JOURNAL[=journal-file-name]         ?                                               Using SSMgr  3-59              Save set qualifier   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. >    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.   :    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 as     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.   %    /LOG_FILE[=logfile-name] (default)     /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 is :    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 including >    /LOG_FILE=NL: on the command line. The following events are#    written to the SAVESET.LOG file:     Using   SSMgr             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          
    /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.   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 conditions 7    occurring during execution (e.g., tape switches) are     displayed as they occur.   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).    Using   SSMgr               !    Example 3-12  VALIDATE Command   =    $ saveset validate mkb200:rock.bck/checks=(crc,xor)/rewind !    ERRORS terminal option enabled !    EVENTS terminal option enabled +    Rewinding MKB200: to beginning of volume     Rewind of MKB200: complete #    Opening file MKB200:[]ROCK.BCK;1 4    Primary input save set MKB200:[]ROCK.BCK;1 opened  6    Save Set Manager V1.5 Time: 14-MAR-2001 19:17:42.17  !        SAVESET function: VALIDATE 2        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 detected   :       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.   .    Example 3-13  VALIDATE with /Full Qualifier  F    $ saveset validate mkb200:rock.bck/full/rewind/checks=(nocrc,noxor)!    ERRORS terminal option enabled !    EVENTS terminal option enabled +    Rewinding MKB200: to beginning of volume     Rewind of MKB200: complete #    Opening file MKB200:[]ROCK.BCK;1 4    Primary input save set MKB200:[]ROCK.BCK;1 opened  ?                                        (continued on next page)           ?                                               Using SSMgr  3-63          6    Example 3-13 (Cont.)  VALIDATE with /Full Qualifier  6    Save Set Manager V1.5 Time: 14-MAR-2001 19:21:33.48  !        SAVESET function: VALIDATE 2        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:                  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          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 rewinding ;       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=crc !    ERRORS terminal option enabled !    EVENTS terminal option enabled C    Primary input save set DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.96;1 
     opened  6    Save Set Manager V1.5 Time: 14-MAR-2001 19:31:19.04  !        SAVESET function: VALIDATE H        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  6    Save Set Manager V1.5 Time: 14-MAR-2001 19:31:22.25  !        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 detected   C    Primary input save set DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.98;1 
     opened  6    Save Set Manager V1.5 Time: 14-MAR-2001 19:31:23.24  !        SAVESET function: VALIDATE H        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          <    Example 3-14 (Cont.)  VALIDATE All Save Sets in Directory  B          Save set name:  DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.98;1            No errors detected   C    Primary input save set DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.99;1 
     opened  6    Save Set Manager V1.5 Time: 14-MAR-2001 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 brief :       report is generated upon the completion of each save>       set, followed by a summary report of all the operations.                                Using   SSMgr         0    Example 3-15  VALIDATE with Journal Qualifier  <    $ saveset validate mkb500:SAVESET015/journal=kit.contents!    ERRORS terminal option enabled !    EVENTS terminal option enabled %    Opening file MKB500:[]SAVESET015;1 6    Primary input save set MKB500:[]SAVESET015;1 opened  6    Save Set Manager V1.5 Time: 14-MAR-2001 19:43:31.09  !        SAVESET function: VALIDATE 4        Primary input save set: MKB500:[]SAVESET015;1#          Journal file: KIT.CONTENTS   %        Final status of each save set: .          Save set name:  MKB500:[]SAVESET015;1            No errors detected   %    $ backup/journal=kit.contents/list     Listing of BACKUP journal>    Journal file DISK$PEAK:[PIKES]KIT.CONTENTS;1 on 14-MAR-2001     19:44:23.45   9    Save set SAVESET015 created on 14-MAR-2001 19:40:01.66 '    Volume number 1, volume label MERGE0 ,        [SOFTWARE.SAVESET015]KITINSTAL.COM;29.        [SOFTWARE.SAVESET015]SAVESET$IVP.COM;14)        [SOFTWARE.SAVESET015]SAVESET.CLD;4 )        [SOFTWARE.SAVESET015]SAVESET.HLP;4 6        [SOFTWARE.SAVESET015]SAVESET015.RELEASE_NOTES;39        [SOFTWARE.SAVESET015]SAVESET015_RELEASE_NOTES.PS;5 5        [SOFTWARE.SAVESET015]SAVESET_COVER_LETTER.PS;6 4        [SOFTWARE.SAVESET015]SAVESET_USER_GUIDE.PS;174        [SOFTWARE.SAVESET015]SAVESET_USER_GUIDE.TXT;8      End of BACKUP journal  8       Example 3-15 shows the validation of the save set,7       SAVESET015, on the tape device, MKB500, that also 9       creates a journal file named, KIT.CONTENTS, showing >       the files in the save set. Note that to see the contents<       of the resultant journal file, BACKUP must be invoked.    ?                                               Using SSMgr  3-67          7    Example 3-16  VALIDATE with Terminal Classes Enabled   4    $ saveset validate/terminal=(errors,events,log) -    mkb500:SAVESET015/rewind     LOG terminal option enabled!    ERRORS terminal option enabled !    EVENTS terminal option enabled +    Rewinding MKB500: to beginning of volume     Rewind of MKB500: complete %    Opening file MKB500:[]SAVESET015;1 6    Primary input save set MKB500:[]SAVESET015;1 opened>    Processing user file: [SOFTWARE.SAVESET015]KITINSTAL.COM;29@    Processing user file: [SOFTWARE.SAVESET015]SAVESET$IVP.COM;14;    Processing user file: [SOFTWARE.SAVESET015]SAVESET.CLD;4 ;    Processing user file: [SOFTWARE.SAVESET015]SAVESET.HLP;4 .    Processing user file: [SOFTWARE.SAVESET015]     SAVESET015.RELEASE_NOTES;3.    Processing user file: [SOFTWARE.SAVESET015]!     SAVESET015_RELEASE_NOTES.PS;5 .    Processing user file: [SOFTWARE.SAVESET015]     SAVESET_COVER_LETTER.PS;6 .    Processing user file: [SOFTWARE.SAVESET015]     SAVESET_USER_GUIDE.PS;17.    Processing user file: [SOFTWARE.SAVESET015]     SAVESET_USER_GUIDE.TXT;8  6    Save Set Manager V1.5 Time: 14-MAR-2001 19:51:55.14  !        SAVESET function: VALIDATE 4        Primary input save set: MKB500:[]SAVESET015;1          No journal file  %        Final status of each save set:   .          Save set name:  MKB500:[]SAVESET015;1            No errors detected   8       Example 3-16 shows the validation of the save set,6       SAVESET015, on the tape device, MKB500, with all;       classes of information: errors, events, and log being ;       displayed to the terminal. The tape is rewound before &       the validation operation begins.      Using   SSMgr             ?                                                               4 > ______________________________________________________________  ?                                      Interpreting SSMgr Reports     <    This chapter describes the completion and interim reports    generated by SSMgr.  -  Monitoring  the Progress of SSMgr Operations   8    While SSMgr is running, you can use Ctrl/T to monitor;    the progress of the SSMgr operation. Each time you enter 7    Ctrl/T, SSMgr displays a progress report as shown in     Example 4-1.   %    Example 4-1  Ctrl/T Report Example   O    1 JOE::SMITH 15:44:09 SAVESET$S CPU=00:19:00.12 PF=392532 IO=292279 MEM=1131 2    2  Current input file:    [SMITH]WS_LOGIN.COM;1?    3  Input save set blocks:         5      Input files:     28 ?    4  Output save set blocks:        4      Output files:    24   ;    1  The first line is the standard OpenVMS Ctrl/T output.   :    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 an =    image save set and an incremental save set, SSMgr displays <    "None" in this field throughout the initial pass over the    incremental save set.    ?                                 Interpreting SSMgr Reports  4-1            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.      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 errors 6    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 errors 9    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 XOR ;    group size greater than zero, and there was no more than ;    one error in an XOR group. The following types of errors 8    and anomalies are broken out for each input save set:  +    o  recoverable/unrecoverable CRC errors.   =    o  recoverable/unrecoverable block header checksum errors.   /    o  recoverable/unrecoverable missing blocks.   8    o  XOR mismatch errors. The XOR block at the end of a=       group does not contain the XOR of all the blocks in the >       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.       o  Read errors.  =    o  Record header errors. A record header within a save set =       block contains an invalid record type or invalid record 
       length.     Interpreting  SSMgr Reports         3    Example 4-2  Normal Successful Completion Report   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; opened   ;    4  Save Set Manager V1.5 Time: 14-March-2001 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;             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 detected   %    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 status :       of multiple output save sets, if any were requested.  3    7  No errors or anomalies, either recoverable or #       unrecoverable, were detected.   9    o  Rewritten blocks. This is not an error, but a count 9       of the number of blocks which were rewritten due to 8       conditions such as bad spots on the media. If this>       number is large, you may be able to significantly reduce  ?                                 Interpreting SSMgr Reports  4-3          <       the size of your save set by using SSMgr to copy it to       better media.   =    If recoverable errors were detected in the input save set, :    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 be     lost.  7    If your save set contains recoverable errors, Compaq 5    recommends that you use the SSMgr COPY function to 7    regenerate the XOR redundancy protection. If you are :    dealing with save sets on media that is very old or has>    been improperly stored, Compaq recommends that you copy the=    save set with the SAVESET COPY command with the /IDENTICAL :    and /OVERRIDE qualifers to another medium, then SAVESET8    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 over     the suspect media.                                                 Interpreting  SSMgr Reports         )    Example 4-3  Save Set Condition Report   .    $ saveset merge zap4.sav zapcrc.sav foo.sav#      ERRORS terminal option enabled #      EVENTS terminal option enabled -      Opening file DKB200:[ENGINEER]ZAP4.SAV;2 >      Primary input save set DKB200:[ENGINEER]ZAP4.SAV;2 opened1      Opening file DISK$100:[ENGINEER]ZAPCRC.SAV;1 D      Secondary input save set DISK$100:[ENGINEER]ZAPCRC.SAV;1 opened-      Opening file DISK$100:[ENGINEER]FOO.SAV; 7      Output save set DISK$100:[ENGINEER]FOO.SAV; opened C      Resetting to beginning of file DISK$100:[ENGINEER]ZAPCRC.SAV;1 M      File DISK$100:[ENGINEER]ZAPCRC.SAV;1 has been reset to beginning of file :      Save Set Manager V1.5 Time: 14-March-2001 20:38:36.57          SAVESET function: MERGE'        Primary input save set: ZAP4.SAV +        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:          1   $    3User files affected by error(s):;            [ENGINEER.SSM.VAXV60.OBJ]CONDITION_HANDLER.OBJ;3 ;            [ENGINEER.SSM.VAXV60.OBJ]CONDITION_HANDLER.OBJ;2 ;            [ENGINEER.SSM.VAXV60.OBJ]CONDITION_HANDLER.OBJ;1 /            [ENGINEER.SSM.VAXV60.OBJ]COPY.OBJ;25   >    4Save set name:  DISK$100:[ENGINEER.SSM.SRC.TMP]ZAPCRC.SAV;  -    5  Recoverable CRC errors:               1   ?                                        (continued on next page)                   ?                                 Interpreting SSMgr Reports  4-5          1    Example 4-3 (Cont.)  Save Set Condition Report   $    6User files affected by error(s):!            [ENGINEER]BATCH.COM;26 $            [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;1 #            [ENGINEER]INIT$LSE.COM;3 #            [ENGINEER]INIT$LSE.COM;2 #            [ENGINEER]INIT$LSE.COM;1             [ENGINEER]LN03.COM;4              [ENGINEER]LOGIN.COM;6             [ENGINEER]LOGIN.COM;5             [ENGINEER]LOGIN.COM;4             [ENGINEER]MEDIA.COM;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;2             [ENGINEER]UUCP.COM;1 $            [ENGINEER]WAS_LOGIN.COM;2#            [ENGINEER]WS_LOGIN.COM;1   4    1  Name of first input save set containing errors       /anomalies.   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.   5    4  Name of second input save set containing errors        /anomalies.   ?                                        (continued on next page)     Interpreting  SSMgr Reports         1    Example 4-3 (Cont.)  Save Set Condition Report   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    Reporting   :    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 enabled !    EVENTS terminal option enabled ?    Primary input save set DISK$USER:[SOFTWARE]ZAP2.BCK;1 opened 8    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  :      Save Set Manager V1.5 Time: 14-March-2001 20:16:28.18          SAVESET function: COPY =        Primary input save set: DISK$USER:[SOFTWARE]ZAP2.BCK;1           No journal file6        Output save set: DISK$USER:[SOFTWARE]ZCOPY.BCK;          No journal file  %        Final status of each save set:   7          Save set name:  DISK$USER:[SOFTWARE]ZAP2.BCK;1 0          Recoverable CRC errors:               1  )          User files affected by error(s): 8            [SOFTWARE.SAVESET015]SAVESET_USER_GUIDE.PS;17  7          Save set name:  DISK$USER:[SOFTWARE]ZCOPY.BCK;             No errors detected     ?                                 Interpreting SSMgr Reports  4-7            Log    File  =    In addition to standard output, SSMgr messages and reports <    also are sent to a log file as shown in Example 4-5. Each;    log file begins with a diagnostic message containing the =    time the SSMgr command was issued, followed by a report or ;    error message identical to that sent to standard output. ;    The default log file name is SAVESET.LOG, written to the 8    user's default directory. See the /LOGFILE= qualifier:    to 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 enabled !    EVENTS terminal option enabled B    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;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 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;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 78 in save set DISK$ENGINEER:[SOFTWARE]SSM.BCK;1  :      Save Set Manager V1.5 Time: 14-March-2001 20:22:12.74          SAVESET function: COPY @        Primary input save set: DISK$ENGINEER:[SOFTWARE]SSM.BCK;1          No journal file9        Output save set: DISK$ENGINEER:[SOFTWARE]COPY.SAV;           No journal file  %        Final status of each save set:   :          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 detected           ?                                 Interpreting SSMgr Reports  4-9              ?                                                               5 > ______________________________________________________________  ?                                                  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.   >  Unable               to write log file. Continuing operation.  ;   Explanation: Attempt to write to the log file failed. The 8   reason for the failure follows this message. Operation   continues without logfile.  9   Action: Correct problem indicated by secondary message.     SSMgr  ERROR Level Messages  8  Block            header checksum error in file filename  9   Explanation: An unrecoverable error was found in a save :   set block header. The data contained in the block is not   reliable.   7   Action: Use OpenVMS BACKUP to restore the recoverable    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 recoverable    portion of the save set.  ?                                             SSMgr Messages  5-1          !  XOR       error in file filename   <   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 recoverable    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 file 
   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 file   .   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: filename   <   Explanation: For any single SAVESET command with more than=   one journal file being created, each journal file name must    be unique.  >   Action: Verify that the save set file names used are unique.    SSMgr  Messages         *  SAVESET        operation was unsuccessful  8   Explanation: The SAVESET operation could not complete.9   Additional messages follow indicating the nature of the 
   failure.  7   Action: Base user action on the immediately following    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 filename   ;   Explanation: SSMgr could not open the file with filename. ;   The reason for the failure appears immediately after this 
   message.  .   Action: Dependent on the reason for failure.  $  error         reading file filename  7   Explanation: SSMgr encountered and error reading file :   filename. The reason for the failure appears immediately   after this message.   .   Action: Dependent on the reason for failure.  7  could          not reset to beginning of file filename   8   Explanation: SSMgr could not reset to the beginning of7   the file filename. The reason for the failure appears !   immediately after this message.   .   Action: Dependent on the reason for failure.  %  error          writing file filename   6   Explanation: SSMgr encountered an error writing file:   filename. The reason for the failure appears immediately   after this message.   .   Action: Dependent on the reason for failure.  ?                                             SSMgr Messages  5-3          /  Identical              copy of filename failed   ;   Explanation: The user specified /IDENTICAL on the SAVESET =   COPY command line, and the operation failed. The reason for 5   the failure appears immediately after this message.   .   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 set 
   filename  ;   Explanation: There is a nonzero value in address field of =   record header in non-LBN/VBN record. The associated data is    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.   ;   Action: Reenter the SAVESET command and specify a /BLOCK_ 1   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 tape 	   device.      Action: None.   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.     SSMgr  Messages         1  Invalid           group size. Valid range: 0-100   =   Explanation: Save set XOR groups may be no larger than 100. ;   A value of zero indicates no XOR should be written to the    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.   >   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.   >   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 the    specification is illegal.   <   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.   =   Action: Ensure that the file name is correct, that you have >   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.   9   Action: Ensure sufficient resources for SSMgr operaton.   ?                                             SSMgr Messages  5-5          7  No         device name in save set specifier specifier   ;   Explanation: No device name was specified in a context in ,   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 to    MERGE   6   Explanation: MERGE operations cannot be performed on   physical backup save sets.     Action: None.   7  COPY/IDENTICAL            output save set may not span    multiple tapes  7   Explanation: End of tape (EOT) on the output tape was =   encountered during a SAVESET COPY/IDENTICAL operation. This ;   operation requires that the copied save set does not span    multiple tapes.   :   Action: Use an output tape that has sufficient space for:   the save set or use the SAVESET COPY command without the   /IDENTICAL qualifier.   +  device            must be accessed locally   7   Explanation: The save set must be accessed on a local 	   device.   8   Action: Use only save sets that do not require network	   access.   "  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 SAVESET :   MERGE operation is an image save set, then the secondary5   input save set must be an incremental save set. See 9   Table 3-1 for a list of valid save set combinations for    MERGE.  4   Action: Retry the SAVESET MERGE operation with the'   appropriate secondary input save set.     SSMgr  Messages         =  Too            many errors reading save set filename. Giving    up.   =   Explanation: Too many errors were encountered while reading ;   the save set. Probably a problem with the drive or media.   <   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 Mesages   4  No            user files written to output save set  9   Explanation: The output save set is empty: i.e. no user ,   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 Messages   ,  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          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. While :   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.   -  recovery     successful in save set filename   9   Explanation: The ERRORS terminal option is enabled. The >   error specified immediately above was successfully recovered   by SSMgr.     terminal      option enabled   =   Explanation: The ERRORS terminal option is enabled for this    SAVESET command.  0  Block:       number number in save set filename  7   Explanation: The ERRORS terminal option is enabled. A ;   missing block was detected in block number number in save    set filename.   3  error:    block number number in save set filename   7   Explanation: The ERRORS terminal option is enabled. A <   read error was detected in block number number in save set   filename.   )  unsuccessful        in save set filename   9   Explanation: The ERRORS terminal option is enabled. The 8   error specified immediately above was not recoverable.    SSMgr  Messages         2  Block:         number number in save set filename  7   Explanation: The ERRORS terminal option is enabled. A ;   rewritten block error was detected in block number number    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 set    filename.   #  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.     save      set: filename  >   Explanation: The EVENTS terminal option is enabled. The file=   filename has been successfully opened for use as the output    save set.     input       save set: filename   >   Explanation: The EVENTS terminal option is enabled. The file>   filename has been successfully opened for use as the primary   input save set.   &  to         beginning of file filename  9   Explanation: The EVENTS terminal option is enabled. The 9   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 secondary %   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 is *   resuming on volume number volume-number.  ?                                             SSMgr Messages  5-9            of      filename complete  =   Explanation: The EVENTS terminal option is enabled. /REWIND =   was specified and the tape has been successfully rewound to    BOT.  (  filename         to beginning of volume  =   Explanation: The EVENTS terminal option is enabled. /REWIND .   was specified and the tape is being rewound.     secondary        input save set  =   Explanation: ... EVENTS ...enabled. An incremental save set ;   is being merged with an image save set. SSMgr is scanning 7   the incremental save set for file system information.   !  input         save set: filename   9   Explanation: The EVENTS terminal option is enabled. The ;   file filename has been successfully opened for use as the    secondary input save set.   :  to      continue writing to save set filename. Continuing   operation.  ;   Explanation: The EVENTS terminal option is enabled. SSMgr :   could not write to one of the multiple output save sets.=   SSMgr will continue the COPY or MERGE operation, writing to !   the remaining output save sets.      LOG    Option Terminal Messages    terminal   option enabled  :   Explanation: The LOG terminal option is enabled for this   SAVSESET command.     user          file: filename   ;   Explanation: The LOG terminal option is enabled. The user -   file filename is currently being processed.       SSMgr   Messages          )  Process  Quota Exceeded (System Message)   >    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.                                                                             ?                                            SSMgr Messages  5-11                      ; ___________________________________________________________   <                                                        Index      <                              _______________________________0  quotas                      DCL interface,  1-1   2-3    2-2                        Ex                              _______________________________                                                         2-2Y                              Error report,  4-7                                      Key,   ~                              F______________________________                                                           OpenVMS  +                              Files-11,  3-1    _________________________    H<                              _______________________________H                              HELP                                OpenVMS  U                              I_______________________________________________________   ]                              Input save sets                                         Language ,                                on disks, 3-2s                                on multivolume tape sets,                                                   summary, I                                  3-3                                 1-10 S                                on tapes, 3-2                                   3-14 )                              Installation k                                before installing, 2-1                                                  3-15 t                                conditions for failure, 2-8                                                      3-37i                                disk space required, 2-1                                              3-14 j                                license registration, 2-1                                               3-1Y                                privileges, 2-1                                       3-57 _                                sample run, 2-8                                             1-3, o                              Internationalization,  1-10                                                  3-27,                               IVP                                1-1,                                                               4V                                example, 2-8                                        4-1+                                failure, 2-8 +                                running, 2-7   <                                                      Index-1         5                                 OpenVMS MESSAGE, 1-10 Q                                 Output save sets, 3-5____________________________ /                                  on disks,  3-5 t                                  on multivolume tapes,  3-6                                                      2-1     2-1                                  P____________________________Management                                                       Facili  6 (LMF),  1-10, 2-1               PAK (License PAK), 2-1<  file,  4-8                     Process Quota Exceeded, 5-112                                 Purging files, 2-6  ! ____________________________    Q ?   1-3,    3-37                  _______________________________ 0   3-46                          Qualifiers, 3-14  &                                 Quotas3  OpenVMS   MESSAGE               See Account quotas   ?  installation,       2-8        R______________________________ 1  level,      5-1                Registration, 2-1 2  level,      5-2                Release notes, 2-1-  level,              5-1         option,  2-5 ,   1-10                          Reports, 4-1   5-1 !  level,        5-7              S ?  tape         sets,  3-3        _______________________________ 0                                 SAVESET.LOG, 4-8J                                 Save sets, 4-1____________________________q                                  as input to BACKUP,  1-9                                                   1-10, =                                  Files-11 mount example,  3-8 5                                  handling types,  1-4 , ____________________________     input,  3-18   1-1                            management policy,  1-3/   4-1                            physical,  3-1 1   1-1,         2-1               specifiers,  3-1 ,  AUTHORIZE,      2-3             types,  3-1%  BACKUP,      1-1, 3-1          SSMgr /   1-4                            benefits,  1-1 9   1-4                            completion reports,  4-2 :   1-3                            disk space required,  2-14   2-4                            error reports,  4-7-   1-4                            errors,  4-2 /  spent    doing,  1-5            /FOREIGN,  1-9 6  compatibility,        1-9       input save sets,  3-13  HELP,      1-10                 installation,  2-1 /                                  log file,  4-8 2                                  privileges,  1-10         	  (cont'd) w                                 V__________________________files                                                   from   8   versions, 2-6                 VALIDATE, 1-2, 3-57, 4-14  errors,            4-4          example,  3-63, 4-20  notes,        2-1              VMScluster, 1-10.   4-1                           VMSINSTAL, 2-3.   2-2                            running,  2-4  disk ?   2-4,       2-5                W______________________________   /                                 Wildcards, 3-12 7 ____________________________     input save sets,  3-12 :   1-9                            journal file names,  3-138   3-1                            output save sets,  3-12  scwitching,   3-3?   1-10,     2-3                 X______________________________   (                                 XOR, 4-2                                                  ?                                                         Index-3 