                                               H                     POLYCENTER_Save_Set_Manager_for_OpenVMS_____________/                     User and Installation Guide   -                     Order Number: AA-QDKQE-TE     >                     This manual contains installation and userC                     information for the POLYCENTER Save Set Manager                      software.               F                     Operating Systems:            OpenVMS VAX VersionsC                                                   5.5-2 through 7.1 G                                                   and OpenVMS Alpha 6.1 =                                                   through 7.1   E                     Software Version:             POLYCENTER Save Set F                                                   Manager Version 1.3A        1                     Digital Equipment Corporation *                     Maynard, Massachusetts                 N               ________________________________________________________________               January 1997  C               The information in this document is subject to change H               without notice and should not be construed as a commitmentA               by Digital Equipment Corporation. Digital Equipment G               Corporation assumes no responsibility for any errors that *               may appear in this document.  H               The software described in this document is furnished underI               a license and may be used or copied only in accordance with (               the terms of such license.  E               No responsibility is assumed for the use or reliability F               of software on equipment that is not supplied by Digital@               Equipment Corporation or its affiliated companies.  G               Restricted Rights: Use, duplication, or disclosure by the H               U.S. Government is subject to restrictions as set forth inG               subparagraph (c) (1) (ii) of the Rights in Technical Data A               and Computer Software clause at DFARS 252.227-7013.   D                Digital Equipment Corporation 1997 Printed in U.S.A."               All Rights Reserved.  D               DECnet, OpenVMS, POLYCENTER, VAX, VAXcluster, VMS, andB               the DIGITAL logo are trademarks of Digital Equipment               Corporation.  I               This document was prepared using VAX DOCUMENT, Version 2.1.                                  F      _________________________________________________________________  F                                                               Contents      F      Preface...................................................    vii        1  Introduction  F          1.1  Advantages of SSMgr..............................    1-1F          1.2  SSMgr Functions..................................    1-2F          1.3  How SSMgr Changes Save Set Management Policy.....    1-3F          1.4  OpenVMS Compatibility............................    1-6F          1.4.1  OpenVMS BACKUP Utility ........................    1-6F          1.4.2  VMScluster Support ............................    1-6F          1.4.3  OpenVMS License Management Facility ...........    1-6F          1.4.4  Privileges ....................................    1-6F          1.4.5  Internationalization of Messages ..............    1-6F          1.4.6  OpenVMS HELP Utility ..........................    1-6        2  Installation Procedure  F          2.1  Preinstallation Requirements and Preparations....    2-1F          2.2  License Registration.............................    2-1F          2.2.1  Privileges and Disk Space .....................    2-1F          2.2.2  Process Account Quotas ........................    2-2F          2.2.3  User Account Quotas ...........................    2-2F          2.2.4  VMSINSTAL Requirements ........................    2-3F          2.2.5  Backing Up Your System Disk ...................    2-4F          2.3  Installing the SSMgr Software....................    2-4F          2.3.1  The Installation Procedure ....................    2-4F          2.3.2  Error Recovery ................................    2-7F          2.3.3  Installation on V5.5-2 Systems ................    2-8F          2.4  SSMgr Sample Installation........................    2-9F          2.5  Reporting Product Problems.......................   2-12        F                                                                    iii                            3  Using SSMgr  I            3.1  Input and Output Save Set Specifiers.............     3-1 I            3.1.1   Input Save Sets ...............................    3-1 I            3.1.1.1   Input Save Sets on Disk.....................     3-2 I            3.1.1.2   Input Save Sets on Tape.....................     3-2 I            3.1.1.3   Input Save Sets on Multivolume Tape Sets....     3-3 I            3.1.2   Output Save Sets ..............................    3-5 I            3.1.2.1   Output Save Sets on Disk....................     3-5 I            3.1.2.2   Output Save Sets on Tape....................     3-5 I            3.1.2.3   Output Save Sets on Multivolume Tape Sets...     3-6 I            3.1.3   Files-11 Mount Example ........................    3-8 I            3.1.4   Multiple Output Save Sets .....................    3-9 6            3.2  Wildcards in Save Set and Journal FileI                 Specifiers.......................................    3-12 I            3.2.1   Wildcard Constraints on Input Save Sets .......   3-12 I            3.2.2   Wildcard Constraints on Output Save Sets ......   3-12 I            3.2.3   Wildcard Constraints on Journal File Names ....   3-13 I            3.3  SSMgr Command Language Interface.................    3-14   I                 COPY.............................................    3-15   I                 MERGE............................................    3-37   I                 VALIDATE.........................................    3-57   %         4  Interpreting SSMgr Reports   I            4.1  Monitoring the Progress of SSMgr Operations......     4-1 I            4.2  Completion Reporting.............................     4-2 I            4.2.1   Normal Successful Completion ..................    4-2 @            4.2.2   Successful Completion with Save Set ConditionI                    Report.........................................    4-2 I            4.2.3   Error Reporting ...............................    4-7 I            4.2.4   Log File ......................................    4-8            5  SSMgr Messages   I            5.1  SSMgr INFORMATIONAL Level Messages...............     5-1 I            5.2  SSMgr ERROR Level Messages.......................     5-1 I            5.3  SSMgr FATAL Level Error Messages.................     5-2 I            5.4  SSMgr WARNING level Error Mesages................     5-7 I            5.5  Terminal Messages................................     5-7 I            5.5.1   ERRORS Option Terminal Messages ...............    5-7 I            5.5.2   EVENTS Option Terminal Messages ...............    5-9 I            5.5.3   LOG Option Terminal Messages ..................   5-10   
         iv                   I            5.6  Process Quota Exceeded (System Message)..........    5-11   
         Index              Examples  I            3-1     A Files-11 Mount ..............................    3-8   I            3-2     COPY Command ..................................   3-27   I            3-3     COPY Command with Multiple Output Save Sets ...   3-27   ;            3-4     COPY Command with IDENTICAL and OVERRIDE I                    Qualifiers on Save Set with Errors.............   3-29   <            3-5     COPY with Wildcarding, Journaling, and NoI                    Logfile........................................   3-30   I            3-6     COPY with /JOURNAL and /TERMINAL Qualifiers ...   3-33   @            3-7     COPY with /BLOCK_SIZE, /GROUP_SIZE, and /FULLI                    Qualifiers.....................................   3-34   I            3-8     MERGE Command .................................   3-47   @            3-9     MERGE Command with /FULL, /LOG, and /TERMINALI                    Qualifiers.....................................   3-48   @            3-10    MERGE Command with /FULL, /TERMINAL, /CHECKS,I                    and CRC Qualifiers.............................   3-52   <            3-11    MERGE Command with Journaling on All SaveI                    Sets...........................................   3-56   I            3-12    VALIDATE Command ..............................   3-63   I            3-13    VALIDATE with /Full Qualifier .................   3-63   I            3-14    VALIDATE All Save Sets in Directory ...........   3-65   I            3-15    VALIDATE with Journal Qualifier ...............   3-67   I            3-16    VALIDATE with Terminal Classes Enabled ........   3-68   I            4-1     Ctrl/T Report Example .........................    4-1   I            4-2     Normal Successful Completion Report ...........    4-3   I            4-3     Save Set Condition Report .....................    4-5   I            4-4     Error Report ..................................    4-7   I            4-5     Log File ......................................    4-9   I                                                                         v                             Tables  <            2-1     Process Account Quotas for the InstallingI                    Account........................................    2-2   I            3-1     SSMgr Commands and Qualifiers .................   3-14                                                                               
         vi                             I         _________________________________________________________________   I                                                                   Preface         I               The POLYCENTER Save Set Manager User and Installation Guide G               describes the procedures for configuring, installing, and I               operating the POLYCENTER Save Set Manager (SSMgr) software.            Intended Audience   A               This manual is intended primarily for use by system 9               managers, operators, and workstation users.            Structure   2               This manual is organized as follows:  ;               Chapter 1   Provides an overview of the SSMgr   ;               Chapter 2   Explains how to install the SSMgr   I               Chapter 3   Describes the command language interface of the                            SSMgr   1               Chapter 4   Describes SSMgr reports   I               Chapter 5   Lists the error messages generated by the SSMgr            Related Documents   >               The following table lists documents that contain2               information related to this product:  I               ___________________________________________________________ I               Document_Title____________________________Order_Number_____   C               POLYCENTER Save Set Manager for OpenVMS   AA-QDKQx-TE )               User and Installation Guide   I                                                                       vii                  I               ___________________________________________________________ I               Document_Title____________________________Order_Number_____   C               OpenVMS System Management Utilities       AA-PV5Px-TK #               Reference Manual: A-L   C               OpenVMS License Management Utility        AA-PVXUx-TK I               Manual_____________________________________________________   !         Documentation Conventions   @               The following conventions are used in this manual:  G               boldface    Boldface type indicates the first instance of G               type        terms being defined in text, in the glossary, "                           or both.  E               italic      Italic type indicates emphasis and complete H               type        manual titles. In the glossary, italic type isA                           also used to indicate cross-references.                                                              viii                         I                                                                         1 I         _________________________________________________________________   I                                                              Introduction     H               The POLYCENTER Save Set Manager for OpenVMS[TM] (SSMgr) isF               a layered software product that reduces the time used toF               create OpenVMS BACKUP save sets, while providing greater1               flexibility in save set management.   E               OpenVMS BACKUP users have had a rich set of options and E               a high level of data integrity available at the cost of <               greater down time during the backup operation.  D               SSMgr runs as a post-processor on save sets created byH               BACKUP, or other storage management software that conformsH               to the BACKUP save set structure. It allows some functionsA               that are currently done online with BACKUP, such as I               checking the integrity of save sets, making multiple copies I               of a save set, and XOR or cyclic redundancy checking (CRC), D               to be done offline using SSMgr. SSMgr does not replaceA               OpenVMS BACKUP for creating or restoring save sets.   C               SSMgr is supported for OpenVMS VAX[TM] Versions 5.5-2 H               through 7.1 and for OpenVMS Alpha[TM] Versions 6.1 throughG               7.1. SSMgr supports a DCL interface and all disk and tape 8               technologies supported by OpenVMS systems.           1.1 Advantages of SSMgr   I               Using SSMgr to manage your save sets provides the following                benefits:   E               o  You can run OpenVMS BACKUP with fewer time-consuming E                  data integrity options, such as /VERIFY, to complete H                  the operation with minimal down time. Once you have theI                  backup save set, you perform the validation and addition @                  of data integrity features offline using SSMgr.  I               o  You can reduce the number of full backups in your backup H                  cycle by substituting incremental backups and using the5                  save set merge feature of the SSMgr.   I                                                          Introduction 1-1                     Introduction         1.1 Advantages of SSMgr     E               o  Restore time is greatly reduced, because you can use H                  SSMgr to merge incremental backups into image save setsH                  to maintain a current image save set at all times. ThisF                  process replaces the practice of using OpenVMS BACKUPH                  to restore an image save set plus many incremental save                  sets.  I               o  SSMgr does not require access to any data outside of its H                  input save sets to run, so it can be run on any OpenVMSF                  system that can directly access those save sets or to)                  which they can be moved.   F               o  You can transfer save sets between tape technologies.  G               o  The data integrity of SSMgr save sets is comparable to E                  save sets created with other OpenVMS utilities using $                  full data checking.  F               o  You gain additional flexibility in managing your saveC                  set files by using the SSMgr commands for save set 7                  validation, copy, and merge functions.   G               o  You can monitor the integrity of archived save sets to F                  determine how badly the media has degraded over time,E                  and you can use SSMgr to reconstruct and restore the *                  save sets to fresh media.  G               o  You can create OpenVMS BACKUP Journal Files (.BJL) for .                  previously created save sets.  ?               o  You can create up to five copies of a save set                    simultaneously.  F               SSMgr performs its operations on save sets that strictlyG               conform to the OpenVMS BACKUP save set format for disk or H               tape devices. You can use save sets and journal files thatD               have been created by SSMgr as input to OpenVMS BACKUP.           1.2 SSMgr Functions   5               SSMgr performs the following functions:   D               o  VALIDATE-Validates that all data blocks in the saveG                  set can be read without error. Validation includes the E                  verification that any CRC or XOR protection recordedhE                  in the save set is consistent with the data they areTG                  protecting. This command may eliminate your need for ae:                  /VERIFY pass when you run OpenVMS BACKUP.           1-2 Introduction    n      I                                                              Introduction_I                                                       1.2 SSMgr Functions     I                  Tapes degrade over time, and the VALIDATE command allowshE                  you to monitor the degradation of your archived saveyD                  sets so that you can detect that degradation early,H                  thus minimizing data loss. If the save sets contain XORI                  redundancy protection and degradation is detected early,c8                  you may avoid any consequent data loss.  G               o  COPY-Used to make a copy of a save set, to reconstruct H                  data that has been found to be degenerated by VALIDATE,?                  or to transfer a save set to a different medialC                  technology. You also can change the format of save F                  sets, such as block or group size, and you can insertB                  or remove XOR and CRC protection in the save set.  G                  Using OpenVMS BACKUP, if you wished to create multiple G                  copies of a save set, such as a local copy and a vault5H                  copies, you had to perform your online backup operationD                  multiple times. With SSMgr, you need to perform theD                  OpenVMS BACKUP operation only once, after which youF                  can produce up to 5 copies offline with a single COPY                  operation.m  @               o  MERGE-Allows for a more flexible backup policy,H                  including merging incremental save sets into image saveG                  sets to create a fully restorable save set, or merging I                  incremental save sets into each other. The MERGE command.F                  can be used to reduce the frequency of image save setG                  operations (also called full backup) done with OpenVMSn                  BACKUP.  I               Both COPY and MERGE commands include the option to validate.F               their input save sets while performing their operations.  8         1.3 How SSMgr Changes Save Set Management Policy  I               A common BACKUP policy is to perform an image backup once a.G               week and incremental backups all other days. In the worst.E               case scenario, a disk could be lost on the seventh day,.F               after the last incremental backup had been performed andD               before the next image backup. To restore the disk, theD               image save set must first be restored and then the sixH               incremental save sets applied in sequence. The time neededI               to restore the data is longer if the period of time betweenl&               image backups is longer.  I                                                          Introduction 1-32                    Introduction8         1.3 How SSMgr Changes Save Set Management Policy                   Backup Strategies.  D               SSMgr allows you to select alternative policies as theG               best backup strategy for your installation. The following.H               two different policies using the SSMgr MERGE command couldF               dramatically reduce the time needed to restore the disk:  H               o  Perform an image backup on day one. Each following day,H                  perform an incremental backup and merge the incrementalE                  save set for the day with the image backup save set, G                  creating a new image save set. Repeat this process for D                  each subsequent day, merging that day's incrementalI                  save set with the image save set created by the previous E                  day's merge operation until you wish to perform your #                  next image backup.k  D                  This strategy results in a single large save set to3                  restore in the event of data loss.3  F               o  Perform an image backup on day one and an incremental?                  backup on day two. Perform another incremental @                  backup on day three and merge its save set withC                  the incremental save set from day two to produce a A                  cumulative incremental save set. Repeat for each D                  subsequent day, merging that day's incremental saveE                  set with the cumulative incremental save set created.H                  by the previous day's merge operation until you wish to0                  perform your next image backup.  D                  This strategy results in one image save set and oneE                  incremental save set to restore in the event of datas                  loss.  D               Merging an incremental save set with an image save setA               requires two SSMgr passes over the incremental saverC               set and one pass over the image save set. Merging two.D               incremental save sets requires one pass over each saveE               set. Therefore, depending upon the relative size of theAH               image and incremental save sets, you may prefer to use the7               second strategy instead of the first one.o                   1-4 Introduction           I                                                              Introduction I                          1.3 How SSMgr Changes Save Set Management Policy     4               Controlling Image Backup Save Set Size  E               Image save sets created by SSMgr merge operations of an F               image save set and one or more incremental save sets canH               grow to be larger than the backed-up disk's capacity. NoteG               that this same condition occurs when using OpenVMS BACKUPAI               to restore an image save set and all subsequent incremental                save sets.  I               The increase in size in both cases is due to directories or.I               files on the volume that were deleted or renamed subsequent.F               to the original image backup. Both BACKUP and SSMgr takeB               a conservative approach to the files that used to beI               contained in those deleted or renamed directories and theirsE               subdirectories; BACKUP does not delete these files wheneH               restoring an incremental save set that shows the directoryI               deleted, and SSMgr retains these files when merging in such &               an incremental save set.  D               Therefore, SSMgr MERGE operations do not eliminate theI               need for periodic image backups, but by using MERGE you can D               generally increase the interval between image backups.  F               Other Ways to Reduce the Time Spent on BACKUP Operations  F               The time spent on online OpenVMS BACKUP operations couldC               be further reduced by omitting the calculation of CRC F               protection in BACKUP, and adding in such protection in aF               COPY or MERGE operation in SSMgr. CRC protection and XORH               redundancy were originally put into BACKUP as a protectiveF               mechanism against the relatively poor quality tapes (andG               tape drives) of previous storage technologies; their main3D               use on modern tape systems is to protect against long-B               term degradation of tape media. CRC calculations areC               compute intensive and can reduce BACKUP throughput on H               less powerful VAX systems. XOR redundancy blocks can limitG               BACKUP throughput on slower tape technologies such as QICe               or RDAT.  F               Omitting these protections in BACKUP save set operationsH               results in greater throughput during the backup operation.H               These protections can then be inserted during a subsequentD               SSMgr COPY or MERGE operation. In the event that SSMgrG               detects an error on a recently produced save set, you can '               run OpenVMS BACKUP again.a  I                                                          Introduction 1-5e .  .               Introduction!         1.4 OpenVMS Compatibilityf    !         1.4 OpenVMS Compatibility   F               The following general comments apply to using SSMgr with               OpenVMS systems.  $         1.4.1 OpenVMS BACKUP Utility  G               Save sets created by any version of OpenVMS BACKUP, up to.G               and including V7.0, are accepted by SSMgr. Also, all save G               sets created by SSMgr are valid inputs to all versions of E               OpenVMS BACKUP. All save sets created by any version oftG               SSMgr are accepted by SSMgr, but not all SSMgr operationsMF               are valid for all types of save sets. For example, whileD               SSMgr can copy physical save sets, it cannot merge two!               physical save sets.   D               Unlike OpenVMS BACKUP, output tapes used by SSMgr mustE               be initialized before use and all tapes must be mountedr-               without the /FOREIGN qualifier.v            1.4.2 VMScluster Support  H               SSMgr runs as a single image on a single node and does not:               include any explicit VMScluster[TM] support.  1         1.4.3 OpenVMS License Management Facility   I               SSMgr uses the OpenVMS License Management Facility (LMF) to D               determine if a node is authorized to use the software.           1.4.4 Privileges  G               SSMgr requires no privileges other than TMPMBX and NETMBXw0               in order to perform its functions.  .         1.4.5 Internationalization of Messages  F               The OpenVMS MESSAGE utility is used by the SSMgr CommandG               Language Interface (CLI) to allow internationalization of (               error and status messages.  "         1.4.6 OpenVMS HELP Utility  D               An OpenVMS HELP utility file that describes the CLI isG               provided on the SSMgr distribution media and is installed G               with the software. Use the HELP SAVESET command to access /               this feature from the DCL prompt._           1-6 Introduction                         I                                                                         2tI         _________________________________________________________________   I                                                    Installation Procedure_    9         2.1 Preinstallation Requirements and Preparations_  @               This section discusses the system requirements andG               preparations necessary for installing the SSMgr software.a  @               The SSMgr kit includes online and hardcopy releaseB               notes. Digital strongly recommends that you read theD               release notes before proceeding with the installation.A               The release notes for printing to hardcopy are in a @               file named SYS$HELP:SAVESETUA013_RELEASE_NOTES.PS.:               The online release notes are in a file named2               SYS$HELP:SAVESETUA013.RELEASE_NOTES.  G               SSMgr requires that your system to be running OpenVMS VAX E               Versions 5.5-2 through 7.1 or OpenVMX Alpha 6.1 to 7.1. E               Installation may only be completed on a per-node basis.             2.2 License Registration  F               Before you install and run SSMgr on a new node, you mustI               first register a License Product Authorization Key (License_?               PAK) using the License Management Facility (LMF).   D               For complete information on using LMF, see the OpenVMS0               License Management Utility Manual.  '         2.2.1 Privileges and Disk Spacee  G               To install the SSMgr software, you must be logged into aneB               account that has either of the following privileges:                 o  SETPRVt  *               o  CMKRNL, WORLD, and SYSPRV    I                                                Installation Procedure 2-1a b  a               Installation Procedure          2.2 License Registration    E               SSMgr requires 3500 free disk blocks on the system diskyH               to install. To determine the number of free disk blocks onF               your system disk, enter the following command at the DCL               prompt:a  )               $ SHOW DEVICE SYS$SYSDEVICE   $         2.2.2 Process Account Quotas  G               The account you use to install SSMgr must have sufficientoI               quotas to enable you to perform the installation. Table 2-1gI               summarizes the process quotas required for the installationrE               account. Unless you are installing SSMgr in your systemVI               account, these process quotas are in addition to the normal I               process quotas and are necessary to ensure the proper level +               of resources for your system.s  I               Table_2-1_Process_Account_Quotas_for_the_Installing_Account   I               Process_Account__Quota_____________________________________   !               ASTLM            10u  !               BIOLM            10m  #               BYTLM            4000e  !               DIOLM            10m  !               ENQLM            20n  "               FILLM            300                  PRCLM            2  !               TQLM             10d  I               PGFLQUOTA________10000_____________________________________   !         2.2.3 User Account Quotasb  H               User account quotas are stored in the SYSUAF.DAT file. UseE               the OpenVMS AUTHORIZE utility to verify and change userrH               account quotas. First set your directory to SYS$SYSTEM andD               then run AUTHORIZE, as shown in the following example:  &               $ SET DEFAULT SYS$SYSTEM               $ RUN AUTHORIZEd               UAF>  "         2-2 Installation Procedure m  a      I                                                    Installation Procedure I                                                  2.2 License Registrations    H               At the UAF> prompt, enter the SHOW command with an account>               name to check a particular account. For example:                 UAF> SHOW SMITHa  H               To change a quota, enter the MODIFY command. The followingG               example changes the FILLM quota for the SMITH account ands*               then exits from the utility:  )               UAF> MODIFY SMITH /FILLM=50a               UAF> EXITa  D               Any account from which SSMgr is to be run must have atE               least the TMPMBX and NETMBX privileges. Use the OpenVMSnG               AUTHORIZE utility to determine whether users who will run 5               SSMgr have the privileges they require.a  C               After you exit from the AUTHORIZE utility, the system F               displays messages indicating whether or not changes wereI               made. Once the changes have been made, you must log out and =               log in again for the new quotas to take effect.   G               For more information on modifying account quotas, see the H               description of the AUTHORIZE utility in the OpenVMS System9               Management Utilities Reference Manual: A-L.i  $         2.2.4 VMSINSTAL Requirements  G               When invoked, VMSINSTAL first verifies that the followingl/               actions have already taken place:e  B               o  You have set your default device and directory to                  SYS$UPDATE.  :               o  You are logged into a privileged account.  ;               o  You have adequate quotas for installation.a  0               o  DECnet[TM] software is running.  F               o  You have determined if any users are logged in to the                  system.  H               If VMSINSTAL detects any problems during the installation,E               it notifies you and prompts you to continue or stop theaC               installation. In some instances, you can enter YES toiE               continue. Enter NO if you need to stop the installation $               and correct a problem.  I                                                Installation Procedure 2-3n d  i               Installation Procedure          2.2 License Registration    )         2.2.5 Backing Up Your System Disk   G               At the beginning of the installation procedure, VMSINSTALsG               prompts you about the backup of your system disk. DigitaluA               recommends that you back up your system disk before &               installing any software.  D               Use the backup procedures that are established at yourG               site. For details on performing a system disk backup, see E               the section on the BACKUP utility in the OpenVMS Systems8               Management Utilities Reference Manual: A-L  )         2.3 Installing the SSMgr Softwareh  E               This section contains a step-by-step description of thet%               installation procedure.l  (         2.3.1 The Installation Procedure  F               The SSMgr installation procedure consists of a series ofI               questions and informational messages. See Section 2.4 for a "               sample installation.  E               To start the installation, invoke the VMSINSTAL command E               procedure from a privileged account, such as the SYSTEM @               account. VMSINSTAL is in the SYS$UPDATE directory.  D               To abort the installation procedure at any time, enterG               Ctrl/Y. When you enter Ctrl/Y, the installation procedure C               deletes all files it has created up to that point and ?               exits. You can then start the installation again.e  "               1. Invoke VMSINSTAL.  I                  @SYS$UPDATE:VMSINSTAL saveset-name device-name OPTIONS Nt                    Where:b  I                  o  saveset-name-The installation name for the component.h?                     Use the installation name SAVESETUA013 whene%                     installing SSMgr.   H                  o  device-name-The name of the device on which you planH                     to mount the media. For example, MUA0: is the deviceE                     name for a tape drive. It is not necessary to usetH                     the console drive for this installation. However, ifH                     you do use the console drive, you should replace anyH                     media you removed once the installation is complete.  "         2-4 Installation Procedure s  o      I                                                    Installation Procedure I                                         2.3 Installing the SSMgr Softwareo    @                  o  OPTIONS N-This is an optional parameter thatC                     indicates you want to be prompted to review theeF                     release notes. If you do not include the OPTIONS ND                     parameter, VMSINSTAL does not issue this prompt.  I                     You should review the release notes before proceeding I                     with the installation in case they contain additionalgB                     information about the installation. If you areI                     restarting the installation and have already reviewedbI                     the release notes, you do not need to specify OPTIONSf                     N.  I                  The following example invokes VMSINSTAL to install SSMgr E                  from tape drive MUA0: and shows the system response. H                  This example uses the OPTIONS N release note parameter.  E                  $ @SYS$UPDATE:VMSINSTAL SAVESETUA013 MUA0: OPTIONS Ni  K                        VAX/VMS Software Product Installation Procedure V7.0t  ,                  It is 27-MAY-1996 at 07:03.  @                  Enter a question mark (?) at any time for help.  D                  If you do not supply either the product name or theH                  device name, VMSINSTAL prompts you for this informationD                  later in the installation procedure. VMSINSTAL doesF                  not prompt you for any options, so be sure to includeF                  OPTIONS N on the VMSINSTAL command line to access the7                  release notes during the installation.n  '               2. Confirm system backup.a  O                  * Are you satisfied with the backup of your system disk [YES]?t  B                  You should always back up your system disk beforeF                  performing an installation. If you are satisfied withF                  the backup of your system disk, press the Return key.E                  Otherwise, enter NO to discontinue the installation.yH                  After you back up your system disk, you can restart the                  installation.  /               3. Select a release notes option.e  '                  Release Notes Options:t  +                   1.  Display release notesg)                   2.  Print release notesa"                   3.  Both 1 and 2'                   4.  None of the above   I                                                Installation Procedure 2-5     r               Installation Procedure)         2.3 Installing the SSMgr Software     %                  * Select option [2]:   G                  If you specified OPTIONS N when you invoked VMSINSTAL, H                  you are now asked to choose one of the four options for-                  reviewing the release notes.   G                  If you select option 1, VMSINSTAL displays the release C                  notes immediately on the console terminal. You can F                  terminate the display at any time by entering Ctrl/C.  F                  If you select option 2, VMSINSTAL prompts you for the>                  name of the print queue that you want to use:  *                  * Queue name [SYS$PRINT]:  E                  You can press the Return key to send the file to theSE                  default output print device or you can enter another                   queue name.  G                  If you select option 3, VMSINSTAL displays the releasecC                  notes immediately on the console terminal and thennF                  prompts you for a queue name for the printed version.  I                  Select option 4 if you have already reviewed the released;                  notes and are restarting the installation.i  A                  Next, VMSINSTAL displays the following question:e  E                  * Do you want to continue the installation [N]?: YEShm                  %VMSINSTAL-I-RELMOVED, The product's release notes have been successfully moved to SYS$HELP.   I                  Enter YES to continue the installation. Otherwise, press F                  the Return key. In either case, the release notes are<                  copied to a file in the SYS$HELP directory.                 4. Purge files.   R                  * Do you want to purge files replaced by this installation [YES]?  A                  You have the option to purge files from previous >                  versions of SSMgr that are superseded by thisF                  installation. Purging is recommended; however, if youG                  need to keep files from the previous version, enter NO -                  in response to the question.A  E               5. Choose the Installation Verification Procedure (IVP)                   option.  K                  * Do you want to run the IVP after the installation [YES]?   =                  The IVP for SSMgr checks to be sure that the G                  installation is successful. It is recommended that you                   run the IVP.e  "         2-6 Installation Procedure s  w      I                                                    Installation ProcedureuI                                         2.3 Installing the SSMgr Software     >                  After SSMgr is installed, you can run the IVPG                  independently to verify that the software is available D                  on your system. You might need to run the IVP afterD                  a system failure to make sure that users can accessD                  SSMgr. You can run the IVP independently by running*                  SYS$TEST:SAVESET$IVP.COM.  3               6. Answer Authorization Key Question.   Y                  * Does this product have an authorization key registered and loaded? YESt  D                  If you do not have a license registered and loaded,F                  answer NO and the installation will continue, but theC                  IVP will not run, regardless of how you answer thetE                  previous IVP question. After registering and loadingnI                  the authorization key, you can run the IVP independentlye1                  by how you answer the questions.   /               7. End of installation procedure.   M                     Installation of Save Set Manager V1.3A completed at 14:52o  5                     VMSINSTAL procedure done at 14:52   G                  These lines are displayed when the entire installationi'                  procedure is complete.l  D                  You now can log out of the privileged account. NoteI                  that VMSINSTAL deletes or changes entries in the process I                  symbol tables during the installation. Therefore, if youMI                  are going to continue using the system manager's accountnF                  and you want to restore these symbols, you should log&                  out and log in again.           2.3.2 Error Recovery  @               If errors occur during the installation procedure,F               VMSINSTAL displays failure messages. If the installation8               fails, you will see the following message:  Z               %VMSINSTAL-E-INSFAIL, The installation of Save Set Manager V1.3A has failed.  <               If the IVP fails, you will see these messages:  T               The Save Set Manager V1.3A Installation Verification Procedure failed.  R               %VMSINSTAL-E-IVPFAIL, The IVP for Save Set Manager V1.3A has failed.  D               Errors can occur during the installation if any of the)               following conditions exist:   ;               o  The operating system version is incorrect.e  I                                                Installation Procedure 2-7                     Installation Procedure)         2.3 Installing the SSMgr Software     A               o  Quotas necessary for successful installation are                   insufficient.  H               o  System parameter values for successful installation are                  insufficient.  I               o  An image mismatch error is issued while running the IVP.s  ,         2.3.3 Installation on V5.5-2 Systems  H               OpenVMS images created using DEC C, such as SSMgr, requireC               the existence of compatible run time libraries on thenD               system on which they are installed. If you do not haveF               the DEC C components kit installed, or you have an olderE               DEC C components kit installed, attempting to run SSMgrn9               will result in one of the following errors:L  B               1)  %DCL-W-ACTIMAGE, error activating image DECC$SHR7                   -CLI-E-IMAGEFNF, image file not found1A                   $1$DIA0:[SYS14.SYSCOMMON.][SYSLIB]DECC$SHR.EXE;o  E               2)  %DCL-W-ACTIMAGE, error activating image CMA$TIS_SHRn-                    -CLI-E-IMGNAME, image fileiE                   $3$DUA0:[SYS9.SYSCOMMON.][SYSLIB]CMA$TIS_SHR.EXE;2-eL                    SYSTEM-F-SHRIDMISMAT, ident mismatch with shareable image  F               If your system is running OpenVMS Version 5.5-2, you mayF               see one of these mismatch errors. You must install AACRTE               from the SSMgr installation kit to clear this error, orV4               upgrade to a later version of OpenVMS.  G                 _______________________ Caution _______________________S  @                 Be sure that you carefully read the installationE                 information for AACRT before installing the software; ?                 you may choose to not install SSMgr until after ?                 upgrading to later version of OpenVMS software.a  F                 ______________________________________________________  G               For descriptions of the error messages generated by these A               conditions, see the OpenVMS documentation on systemkA               messages, recovery procedures, and OpenVMS softwaretA               installation. If you are notified that any of these$I               conditions exist, you should take the appropriate action asoG               described in the message. For information on installationt,               requirements, see Section 2.1.  "         2-8 Installation Procedure e  q      I                                                    Installation ProcedurelI                                             2.4 SSMgr Sample Installation     %         2.4 SSMgr Sample Installationr  G               This section contains a sample installation of SSMgr. ThefC               sample shows an installation for a system that had nonE               previous version of the SSMgr software installed. AfterQI               installation, a sample run of the Installation Verification '               Procedure (IVP) is shown.m  D               $ @sys$update:vmsinstal savesetUA013 disk$user:[ELVIS]  F               OpenVMS VAX Software Product Installation Procedure V7.0  )               It is 18-JUL-1996 at 10:14.   =               Enter a question mark (?) at any time for help._  R               %VMSINSTAL-W-NOTSYSTEM, You are not logged in to the SYSTEM account.L               %VMSINSTAL-W-ACTIVE, The following processes are still active:                  UCX$NTPDU                DECW$SERVER_0                UCX$TFTP_BG8c                DECW$MWMo                VUE$ELVIS_2                VUE$ELVIS_3                VUE$ELVIS_4                VUE$ELVIS_5                DECW$TE_0068M                ELVIS6               * Do you want to continue anyway [NO]? yN               * Are you satisfied with the backup of your system disk [YES]? y  7               The following products will be processed:                    SAVESET V1.3At  >               Beginning installation of SAVESET V1.3A at 10:15  D               %VMSINSTAL-I-RESTORE, Restoring product save set A ...Y               %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.D  N                Copyright Digital Equipment Corporation 1994, 1995.  All rights               reserved.   P               %SAVESET-I-VMSOK, Installing SAVESET V1.3A on OpenVMS Version V7.0Q               * Do you want to purge files replaced by this installation [YES]? y J               * Do you want to run the IVP after the installation [YES]? y  I                                                Installation Procedure 2-9                     Installation Procedure%         2.4 SSMgr Sample Installationo    4                       Product:      SAVE-SET-MANAGER'                       Producer:     DECo'                       Version:      1.3n/                       Release Date: 24-JUL-1996n  T               * Does this product have an authorization key registered and loaded? yD               %VMSINSTAL-I-RESTORE, Restoring product save set B ...  I                The Polycenter(TM) Save Set Manager for OpenVMS User Guidea@                has been moved to SYS$HELP:SAVESET_USER_GUIDE.PS.  \               %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...  8               This is the SAVESET IVP command procedure.  )               $ saveset validate blue.bcke,               ERRORS terminal option enabled,               EVENTS terminal option enabled]               Primary input save set ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]BLUE.BCK;1 openedCT                 POLYCENTER(TM) Save Set Manager V1.3A  Time: 18-JUL-1996 10:16:50.03  ,                   SAVESET function: VALIDATE[                   Primary input save set: ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]BLUE.BCK;1f#                     No journal filer0                   Final status of each save set:U                     Save set name:  ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]BLUE.BCK;1e!                No errors detectedo  +               $ saveset validate yellow.bck ,               ERRORS terminal option enabled,               EVENTS terminal option enabled_               Primary input save set ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]YELLOW.BCK;1 opened T                 POLYCENTER(TM) Save Set Manager V1.3A  Time: 18-JUL-1996 10:16:51.80  ,                   SAVESET function: VALIDATE]                   Primary input save set: ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]YELLOW.BCK;1a#                     No journal file 0                   Final status of each save set:W                     Save set name:  ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]YELLOW.BCK;1 !                No errors detectede  -               $ saveset copy blue.bck red.bcki,               ERRORS terminal option enabled,               EVENTS terminal option enabled]               Primary input save set ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]BLUE.BCK;1 opened T               Output save set ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]RED.BCK; openedT                 POLYCENTER(TM) Save Set Manager V1.3A  Time: 18-JUL-1996 10:16:53.88  #         2-10 Installation Proceduree s  l      I                                                    Installation Procedure I                                             2.4 SSMgr Sample Installation     (                   SAVESET function: COPY[                   Primary input save set: ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]BLUE.BCK;1 #                     No journal file,R                   Output save set: ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]RED.BCK;#                     No journal fileY0                   Final status of each save set:U                     Save set name:  ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]BLUE.BCK;1e!                No errors detected S                     Save set name:  ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]RED.BCK;e!                No errors detectedn  ;               $ saveset merge blue.bck yellow.bck green.bcki,               ERRORS terminal option enabled,               EVENTS terminal option enabled]               Primary input save set ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]BLUE.BCK;1 openedfZ               Secondary input save set ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]YELLOW.BCK;1               openedV               Output save set ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]GREEN.BCK; openedT                 POLYCENTER(TM) Save Set Manager V1.3A  Time: 18-JUL-1996 10:16:56.18  )                   SAVESET function: MERGE [                   Primary input save set: ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]BLUE.BCK;1 #                     No journal filew_                   Secondary input save set: ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]YELLOW.BCK;1n#                     No journal filevU                   Output save set: ELVBIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]GREEN.BCK; #                     No journal filee0                   Final status of each save set:U                     Save set name:  ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]BLUE.BCK;1a!                No errors detectedoW                     Save set name:  ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]YELLOW.BCK;1 !                No errors detected U                     Save set name:  ELVIS$DKB300:[SYS0.SYSUPD.SAVESETUA013]GREEN.BCK;f!                No errors detected   K               The SAVESET IVP command procedure has successfully completed. ?                Installation of SAVESET V1.3A completed at 10:16e  0                VMSINSTAL procedure done at 10:17            I                                               Installation Procedure 2-11  I                  Installation Procedure&         2.5 Reporting Product Problems    &         2.5 Reporting Product Problems  C               If you encounter a problem while using this software,hE               report it to Digital Customer Services in the U.S.A. 1-rF               800-354-9000. In other countries, report it through your%               usual support channels.n                                                                              #         2-12 Installation Procedure                          I                                                                         3 I         _________________________________________________________________   I                                                               Using SSMgr     E               This chapter describes how to use SSMgr, from preparing @               save sets to using the command language interface.  0         3.1 Input and Output Save Set Specifiers  C               SSMgr operates on save sets. Each SSMgr command takesnD               at least one input save set as a parameter. Some SSMgrI               commands create output save sets. Input save sets may be on I               disk or tape, and SSMgr can create output save sets on disk G               or tape. OpenVMS BACKUP defines several modes under whicheI               save sets may be created. Three of those save set types areo1               fully supported by SSMgr. They are:   H               o  Image save set-This also is called a full backup. It isF                  a functionally equivalent copy of an entire volume or                  volume set.  G               o  Incremental save set-This save set contains files that H                  were created or modified since the last save operation.  H               o  Selective-This also is called a file-oriented save set.F                  It is a collection of files saved for some particular                  reason.  I               Physical save sets (copies of entire volumes) are supportedgD               by SSMgr for VALIDATE and COPY operations, but not for               MERGE operations.m           3.1.1 Input Save Setst  F               Input save sets may have been created by OpenVMS BACKUP,C               by SSMgr, or by some other entity that creates valid, F               OpenVMS save sets. For SSMgr to operate on an input saveD               set, the device on which that save set resides must beG               mounted Files-11 (that is, not mounted /FOREIGN), must beeG               accessible by the process performing the SSMgr operation,r2               and must not require network access.  I                                                           Using SSMgr 3-1a n  h               Using SSMgr 0         3.1 Input and Output Save Set Specifiers    E               A save set is contained in a file whose contents have a?E               well-defined structure. A save set file may reside on aoG               disk, a bound volume set, a single tape, or a multivolumeYF               tape set. SSMgr does not validate, copy, or merge disks,G               tapes, or files. The units of operation are save sets. IneF               order for SSMgr to operate on these save sets, the filesC               containing them must be accessible in the appropriatesH               manner. The following sections describe how to ensure thatG               SSMgr can appropriately access input and output save setsh;               that are contained in files on various media.w  '         3.1.1.1 Input Save Sets on Disk   B               SSMgr can read save sets on any disk that is locallyI               connected and mounted Files-11. The process wishing to readoF               those files must be suitably privileged for read access.I               The disk may be a single disk volume or a bound volume set.e  H               Standard OpenVMS defaults apply in specifying the pathnameG               of the file containing the save set. That is, the default A               directory specification is assumed unless otherwise A               specified. If more than one input save set is being C               specified (such as the primary input save set and the F               secondary input save set in a MERGE operation), the saveE               sets may be on the same or different devices, or in the ,               same or different directories.  C               For the use of wildcards in specifying pathnames, see                Section 3.2   '         3.1.1.2 Input Save Sets on Tapen  D               Input save sets may be located on magnetic tape. SSMgrF               can read save sets on any tape that is locally connectedH               and mounted Files-11. SSMgr will always open any tape fileH               containing a save set read only. It does not matter if theG               tape is write-locked or not. In mounting a tape Files-11, C               the tape label must be specified, or the /OVERRIDE=ID 3               qualifier used on the $MOUNT command.d  I               Tape are sequential devices. SSMgr will begin searching forlG               specified file at the current position on the tape unless.H               the /REWIND qualifier is specified on the $SAVESET commandG               line. If /REWIND is specified, SSMgr will first rewind to 9               BOT and then search for the specified file.e           3-2 Using SSMgri a  t      I                                                               Using SSMgrgI                                  3.1 Input and Output Save Set Specifierse    G               If there is more than one input save set on tape (such ashI               the primary input save set and the secondary input save setuG               in a MERGE operation), each must be on a different volumeo4               and mounted in a different tape drive.  8         3.1.1.3 Input Save Sets on Multivolume Tape Sets  >               A file containing a save set may span tapes in aF               multivolume tape set. If that is so, the tapes must haveF               been mounted in a manner that allows continuation to theG               next tape in the set. There are several factors that need                to be considered.   H               Tape switching of Files-11-mounted tapes is handled by theG               OpenVMS magnetic tape ancillary control process (MTAACP),PG               which is part of the OpenVMS operating system, not SSMgr.oH               The MTAACP performs a number of checks on the continuationI               volume that is loaded into the tape drive, be it by a humancH               or by a mechanical loader. Two checks that are significantG               for input save sets that span tapes are the label (volumenC               identifier) check and the set id (fileset identifier)o               check.  F               Multivolume tape sets that are created by OpenVMS BACKUPC               or by other OpenVMS utilities follow a canonical tapeiD               labeling scheme if the creator of the multivolume tapeH               set does not explicitly specify the tape labels to be used%               for continuation tapes.   C               Labels generated for continuation tapes fill the six-iC               character volume identification field. The first fourdG               characters of the field contain the first four charactersrH               of the previous volume in the volume set. (If the label isG               less than four characters, the volume identifier field issF               padded with underscores.) The fifth and sixth charactersA               contain the relative volume number for that reel or D               cartridge in the volume set. For example, if the firstG               tape has a label of ABCDEF, the second and third would be F               labeled ABCD02 and ABCD03. If the first tape has a labelE               of AB, the second and third would be labeled AB__02 andM               AB__03.i  F               If SSMgr will be processing an input save set that spansA               tapes (whether it is an operation on a single large D               save set or an operation that processes many save setsC               through the use of wildcards and the /ALL qualifier),   I                                                           Using SSMgr 3-3_ _                  Using SSMgrh0         3.1 Input and Output Save Set Specifiers    C               the multivolume set must be appropriately mounted for F               continuation. If the labeling of the continuation volumeG               does not fit the labeling scheme recognized by MTAACP, it_H               will not mount and make available that volume for reading.H               If the multivolume tape set follows the canonical labelingF               scheme described above, it will mount and make availableH               that volume for continued processing. If not, the tape setI               must be mounted specifying the names of each tape volume ind#               the set. For example:   =                   $ MOUNT MUA0: BEATLE,JOHN,PAUL,GEORGE,RINGOo  I               The use of the /OVERRIDE=ID qualifier on the $MOUNT commandPH               will override the label check on the first volume only. ItH               does not carry over to continuation volumes. Therefore, ifG               the labels are like the ones in the previous example, the '               following $MOUNT command:p  +                   $ MOUNT/OVERRIDE=ID MUA0:a  A               would result in the volume BEATLE being mounted andrF               processed, but when the tape switch occurred, the MTAACPE               would send OPCOM messages asking for relative volume 2, H               BEAT02, to be mounted. At this point, the operation cannotI               continue, because the MTAACP will accept nothing other thans$               a tape labeled BEAT02.  >               A second check made by the MTAACP is the filesetF               identifier. In some instances, continuation volumes thatH               are initialized by OpenVMS BACKUP may not be recognized byG               the MTAACP as the correct next volume, even though it is.NI               In that case, an OPCOM message is issued that says that the .               tape is not the next in the set.  F               SSMgr does its own checking to ensure that what it findsI               on the next tape is indeed the continuation of the save setoG               it had been processing. Therefore, this check made by theiF               MTAACP can be safely overridden with the /OVERRIDE=SETID;               qualifier on the $MOUNT command. For example,3  M                   $ MOUNT/OVERRIDE=SETID MUA0:  BEATLE,JOHN,PAUL,GEORGE,RINGO                  3-4 Using SSMgrn r  c      I                                                               Using SSMgrvI                                  3.1 Input and Output Save Set Specifiersr             3.1.2 Output Save Sets  I               Output save sets may be created by SSMgr on any nonnetwork-VF               accessed disk, bound volume set, or tape device. As withD               input save sets, that device must be mounted Files-11.  (         3.1.2.1 Output Save Sets on Disk  I               SSMgr can create and write to save sets on any disk that is-I               locally connected and mounted Files-11. The process wishingII               to create and write those files must be suitably privileged H               for create and write access. The disk may be a single disk+               volume or a bound volume set.J  I               Standard OpenVMS defaults apply in specifying the pathnamestI               of the files containing the save sets. That is, the defaultaA               directory specification is assumed unless otherwisefE               specified. See Section 3.1.4 for special considerationsE?               around the creation of multiple output save sets.i  C               For the use of wildcards in specifying pathnames, see                Section 3.2.  (         3.1.2.2 Output Save Sets on Tape  E               Output save sets may be created on magnetic tape. SSMgrNE               can create save sets on any tape device that is locallyDB               connected and mounted Files-11. In mounting a singleE               tape Files-11, the tape label must be specified, or the I               /OVERRIDE=ID qualifier used on the $MOUNT command. Further,uH               the tape must have been initialized ($INITIALIZE) prior to(               mounting for use by SSMgr.  A               Tapes are sequential devices. SSMgr will create the:E               specified save set file after the last file on the tape G               unless the /REWIND qualifier is specified on the $SAVESET E               command line. If /REWIND is specified, SSMgr will firstiH               rewind to BOT and then create the specified save set file,=               overwriting whatever may have been on the tape.T  E               See Section 3.1.4 for special considerations around the 4               creation of multiple output save sets.  C               For the use of wildcards in specifying pathnames, seea               Section 3.2.  I                                                           Using SSMgr 3-5     e               Using SSMgrY0         3.1 Input and Output Save Set Specifiers    9         3.1.2.3 Output Save Sets on Multivolume Tape Sets   I               A save set created by SSMgr may span tapes in a multivolumet?               tape set. If that will be so, the tapes must haveSB               been initialized and mounted in a manner that allowsI               continuation to the next tape in the set. There are several 1               factors that need to be considered.T  H               Tape switching of Files-11-mounted tapes is handled by theG               OpenVMS magnetic tape ancillary control process (MTAACP),rG               which is part of the OpenVMS operating system, not SSMgr.sC               The MTAACP has certain expectations of a continuation E               tape that is loaded into the drive, be it by a human orUD               a mechanical loader. Those expectations are set by theB               parameters and qualifiers that had been specified inC               the $MOUNT command for that device. There are severalhC               different ways in which a multivolume tape set can beSF               mounted Files-11 for use by SSMgr to create and write to               output save sets:I  =                   $ MOUNT MUA0: BEATLE,JOHN,PAUL,GEORGE,RINGOr  D               In this example, five tapes have been initialized withD               the tape labels BEATLE, JOHN, PAUL, GEORGE, and RINGO.E               The tape that had been initialized as BEATLE is loaded,SH               and the $MOUNT command issued. When that tape is full, theH               MTAACP expects a tape that had been initialized as PAUL toG               be loaded next. If a mechanical loader is being used, andPI               the next tape in the loader has that label, operations willaH               proceed. If a tape is not automatically loaded, the MTAACPE               issues an OPCOM message requesting that relative volume[H               2, JOHN, be mounted. If a tape initialized with label JOHNH               is loaded into the drive, operations will continue on thatG               tape. If, however, an uninitialized tape or a tape with a H               label other than JOHN is loaded into the drive, the MTAACPG               will reject that tape and continue sending OPCOM messageso1               requesting relative volume 2, JOHN.:  &                   $ MOUNT MUA0: BEATLE  B               In this example, only the label of the first tape isD               specified on $MOUNT command line. A tape that had beenD               initialized as BEATLE is loaded and the $MOUNT commandB               issued. When that tape is full, the MTAACP expects aE               tape that been initialized as BEAT02 to be loaded next.aD               See Section 3.1.1.3 for a description of the canonicalG               continuation tape labeling algorithm for a description of7           3-6 Using SSMgr            I                                                               Using SSMgrlI                                  3.1 Input and Output Save Set Specifierse    H               what labels are expected when continuation tape labels are;               not explicitly specified on the command line.e  >                   $ MOUNT/INITIALIZE=CONTINUATION MUA0: BEATLE  B               In this example, only the label of the first tape isE               specified on the $MOUNT command line. When continuation D               tapes are loaded, either by a human or by a mechanicalB               loader, the MTAACP will change the tape label of theE               next tape that is loaded, using the algorithm described_C               above. That is, the label of the second tape would be @               reinitialized to BEAT02, the third to BEAT03, etc.  ?               In each of the examples above, the MTAACP expectsiE               continuation tapes to have been initialized. It is also B               possible to use uninitialized (unformatted) tapes asE               continuation tapes. This requires responding to MTAACP-mF               generated OPCOM messages with the /BLANK_TAPE qualifier.               For example:  J                   %%%%%%%%%%%  OPCOM, 10-MAY-1996 15:23:31.78  %%%%%%%%%%%-                   request 3, from user SNYDERo?                   MOUNT new relative volume 2 (BEAT02) on MUA0:f  B               With OPER and VOLPRO privileges, the following replyG               will result in the uninitialized tape being formatted andc7               labeled, allowing operations to continue:p  /                   $ REPLY/BLANK_TAPE=3 "BEAT02"e  B               The tape will be formatted and labeled as BEAT02 (orF               whatever you specify as the label you want), and mounted2               in the drive, allowing continuation.  G               If a continuation tape is loaded that has been formatted,fF               but the tape has a label that is not the one expected byE               the MTAACP, the following reply will result in the tape ?               being relabeled, allowing operations to continue:   +                   $ REPLY/INITIALIZE_TAPE=3n  G               The tape will be relabeled as BEAT02, and operations wille*               continue. An alternative is:  2                   $ REPLY/INITIALIZE_TAPE=3 "JOHN"  C               In this case, the tape will be relabeled as JOHN, and '               operations will continue.s  I                                                           Using SSMgr 3-7  t  e               Using SSMgrb0         3.1 Input and Output Save Set Specifiers    $         3.1.3 Files-11 Mount Example  D               Example 3-1 shows a session in which an image save setE               on tape is merged with an incremental save set on disk. D               The resulting "virtual" image save set is written to a               multivolume tape.   *               Example 3-1 A Files-11 Mount  +               $ INITIALIZE MKB200: MERGE0 1 +               $ INITIALIZE MKB200: MERGE1 2l%               $ MOUNT MKB100: IMAGE 3s8               %MOUNT-I-MOUNTED, IMAGE mounted on MKB100:-               $ MOUNT MKB200: MERGE0,MERGE1 4.9               %MOUNT-I-MOUNTED, MERGE0 mounted on MKB200:e  I               $ saveset merge mkb100:full.bck incr.bck mkb200:merge.bck 5r,               ERRORS terminal option enabled,               EVENTS terminal option enabled.               Opening file MKB100:[]FULL.BCK;1?               Primary input save set MKB100:[]FULL.BCK;1 openedrI               Secondary input save set DISK$USER:[ELVIS]INCR.BCK;1 openedS.               Opening file MKB200:[]MERGE.BCK;8               Output save set MKB200:[]MERGE.BCK; opened  S                POLYCENTER(TM) Save Set Manager V1.3A  Time: 18-JUL-1996 13:29:09.58c  )                   SAVESET function: MERGEd=                   Primary input save set: MKB100:[]FULL.BCK;1e#                     No journal file G                   Secondary input save set: DISK$USER:[ELVIS]INCR.BCK;1 #                     No journal filec6                   Output save set: MKB200:[]MERGE.BCK;#                     No journal files  0                   Final status of each save set:  7                     Save set name:  MKB100:[]FULL.BCK;1u(                       No errors detected  ?                     Save set name:  DISK$USER:[ELVIS]INCR.BCK;1 (                       No errors detected  I                                                  (continued on next page)e           3-8 Using SSMgr.           I                                                               Using SSMgrcI                                  3.1 Input and Output Save Set Specifierst    2               Example 3-1 (Cont.) A Files-11 Mount  7                     Save set name:  MKB200:[]MERGE.BCK;o(                       No errors detected  "               $ DISMOUNT MKB100: 6"               $ DISMOUNT MKB200: 7  I               1  The output save set will span two volumes. In this line,IE                  the first tape is initialized with the label merge0.   E               2  The first tape is removed from mkb200 and the second E                  tape is loaded. This second tape is then initialized E                  with the label merge1. After initializing that tape, F                  it is removed and the first tape is reloaded into the                  drive.n  D               3  The device containing the primary input save set is"                  mounted Files-11.  I               4  The device to which the "virtual" image save set will be3G                  written also is mounted Files-11 as a multivolume saveo                  set.s  E               5  The SAVESET MERGE operation is performed. The secondcG                  output tape is loaded either manually or with a loader 8                  when the first output tape reaches EOT.  0               6  The input device is dismounted.  F               7  The output device is dismounted, completing the merge                  operation.   '         3.1.4 Multiple Output Save Setse  F               SSMgr provides the ability to make up to 5 copies of anyI               output save set simultaneously. These copies may be writtenrI               to disk or tape. Each output save set pathname is specifiediG               as a separate parameter on the $SAVESET command line. Forn               example,  V                   $ SAVESET COPY MUA0:SS.BCK *.* [-]*.* MKA100:*.* MUA1:SS_ARCHIVE.BCK  E               In this example, the save set named SS.BCK is on a tapenF               mounted on tape drive MUA0:. Four copies are being made.H               Two of the copies are being written to disk, and two otherD               are being written to tape. The copies being written toD               disk are being written to the default directory and to  I                                                           Using SSMgr 3-9h a  c               Using SSMgr 0         3.1 Input and Output Save Set Specifiers    H               the parent directory, and in each case, the name SS.BCK isI               preserved. One tape copy is being written to a tape mountedbF               on MKA100: and the file name is again the same. The lastE               copy is being written to a tape mounted on MUA1: and is (               being name SS_ARCHIVE.BCK.  G               With the /ALL qualifier, SSMgr may be processing multiplerD               input save sets. With one exception, in the event of aG               failure to open or to write to any output save set, SSMgrdG               will attempt to continue operation to as many output saveeE               sets as it can, from as many input save sets as it can.   F               If there is a failure to open any one of the output saveI               sets for the second or subsequent input save sets, an error H               will be reported and operation will continue to all outputI               save sets that could be opened. If none could be opened, an I               error will be reported and operation will continue with theh*               next input save set, if any.  F               If SSMgr cannot successfully write to an output save setG               once it has been opened, that output file will be closed,aI               an error reported, and operation will continue to all other E               output save sets. If SSMgr encounters a condition where H               it can write to none of the output save sets, it will moveH               to the next input save set, if any, and continue operation               from there.t  I               The one exception to the continue-if-possible philosophy isCG               if there is a problem opening any output save set for theeG               first (or only) input save set for a given SSMgr command.aH               In that case, the command execution is terminated to allow6               the offending condition to be corrected.  H               There are several performance and resource implications to2               producing multiple output save sets:  I               o  Multiple copies can be written to the same disk, but for G                  each tape copy desired, there must be a dedicated tapeP                  drive.r  C               o  A SSMgr operation to multiple output save sets cantB                  proceed only as fast as the slowest output deviceF                  permits. If one device is involved in error recovery,:                  all others must wait until it's complete.           3-10 Using SSMgr    l      I                                                               Using SSMgreI                                  3.1 Input and Output Save Set Specifiersa    G               o  A set of I/O buffers is allocated for each output savehG                  set, with a maximum of four 64KB buffers allocated forP                  each.  G               o  XOR and CRC calculations are performed for each outputeG                  save set, thereby significantly increasing the computen'                  load of the operation.   F               o  For $ SAVESET COPY/IDENTICAL operation, there will beI                  significant slowdown with multiple output save sets. The H                  operation is optimized for a single output save set, anG                  optimization that does not transfer to multiple outputo%                  save set operations.s                                                                I                                                          Using SSMgr 3-11a b  h               Using SSMgrn=         3.2 Wildcards in Save Set and Journal File Specifiersu    =         3.2 Wildcards in Save Set and Journal File Specifiers   F               SSMgr supports standard OpenVMS wildcarding of input andF               output save set specifiers, as well as journal file nameD               specifiers. However, because of the semantics of SSMgr3               commands, there are some constraints.   5         3.2.1 Wildcard Constraints on Input Save Setss  G               By default, if a wildcard is used in the name of an inputbB               save set, only the first matching file found will beC               used. This is true for VALIDATE, COPY, and MERGE. ForSF               VALIDATE and COPY, you can elect to operate on all filesG               that match the wildcarded save set specifier by using the-G               /ALL qualifier. Because the MERGE command takes two inputuH               save set specifiers and one output save set specifier, theE               possible combinations of names of input and output saveJC               sets all using wildcards presents a dizzying semanticaA               matrix of resultant operations. Therefore, the /ALL ?               qualifier is not supported for the MERGE command.d  F               As it is, use of /ALL with the COPY command has semantic(               implications. For example:  2                   $ SAVESET COPY *.BCK FOO.BCK/ALL  F               If there are 10 files that match the wildcarded save setD               specifier, *.BCK, there will be 10 versions of foo.bckC               created. That is, the output save set for each of the F               10 COPY operations will have the same name, FOO.BCK, butE               a different version number. If there is a version limit H               placed on the directory, the first several copies could be7               deleted on creation of subsequent copies.r  6         3.2.2 Wildcard Constraints on Output Save Sets  E               Wildcarding of output save set specifiers is permitted. E               Resolution of the actual name of the output save set is G               based on the location of the wildcard or wildcards in then(               output save set specifier.  C               The components of a save set specifier are the deviceMA               name, the directory string, the file name, the filecF               type, and the version number. For example, the specifier1               dua1:[foo]bar.baz;3 breaks down as:            3-12 Using SSMgr h         I                                                               Using SSMgr I                     3.2 Wildcards in Save Set and Journal File Specifiers     #                   device:     dua1: #                   directory:  [foo]e!                   file name:  bar "                   file type:  .baz                    version:    ;3  E               Only the file name and file type components may containbF               wildcards. The only legal wildcard character is * and itF               must be the only character in that component of the fileE               specification. When the component contains the wildcardtE               character, the corresponding component from the primarybC               input file specification is used. If the component ispE               missing altogether, it is treated the same as if * weret               used.r  E                   $ SAVESET COPY DUA0:[FOO]BAR.BAZ;3 DUA1:[MUMBLE]*;6s  8               In this case, the output save set would beD               DUA1:[MUMBLE]BAR.BAZ;6 because the file name componentB               contains the wildcard and the file type component isD               missing. Therefore, both of those components mimic theE               corresponding component from the primary input save setr               specification.  8         3.2.3 Wildcard Constraints on Journal File Names  C               As with output save set specifiers, journal file name F               specifiers may contain wildcard characters. If the "fileF               name" component of the journal file specifier contains aD               wild card, the "file name" component of the associatedD               save set will be used. If the "file type" component ofG               the journal file specifier contains a wild card, then theh<               default journal file type (.BJL) will be used.  P                   Example 1:  SAVESET VALIDATE DUA0:[FOO]BAR.BAZ;3/JOURNAL=*.JOU  S                   In this case, the journal file would be written to BAR.JOU in thet$                   default directory.  R                   Example 2: SAVESET VALIDATE DUA0:[FOO]BAR.BAZ;3/JOURNAL=FOOBAR.*  S                   In this case, the journal file would be written to BAR.JOU in thez$                   default directory.  M                   Example 3: SAVESET VALIDATE DUA0:[FOO]BAR.BAZ;3/JOURNAL=*.*o  S                   In this case, the journal file would be written to BAR.JOU in thel$                   default directory.  I                                                          Using SSMgr 3-13     e               Using SSMgr ,         3.3 SSMgr Command Language Interface    ,         3.3 SSMgr Command Language Interface  D               This section describes the valid commands for SSMgr. AF               matrix of commands and qualifiers is shown in Table 3-1.  I               Table_3-1_SSMgr_Commands_and_Qualifiers____________________e  I               Command          _____________SAVESET_Command______________t  I               Qualifier________VALIDATE__COPY______MERGE_________________   5               /ALL             Yes       Yes       Nor  6               /BLOCK_SIZE      No        Yes       Yes  6               /BRIEF           Yes       Yes       Yes  6               /CHECKS          Yes       Yes       Yes  6               /COMMENT         No        Yes       Yes  6               /CRC             No        Yes       Yes  6               /FULL            Yes       Yes       Yes  6               /GROUP_SIZE      No        Yes       Yes  5               /IDENTICAL       No        Yes       Not  6               /JOURNAL         Yes       Yes       Yes  6               /LOG_FILE        Yes       Yes       Yes  5               /OVERRIDE        No        Yes       No   6               /REWIND          Yes       Yes       Yes  I               /TERMINAL________Yes_______Yes_______Yes___________________                        3-14 Using SSMgr    e      I                                                                      COPY       I         _________________________________________________________________t           COPY                  Copies a save set.           Format  >               COPY  input-ss output-ss [output-ss] [output-ss]+                     [output-ss] [output-ss]t           Parameters                 input-ss5               OpenVMS file name of an input save set.x                 output-ss C               OpenVMS file name(s) of the output save set(s). Up to C               5 output save sets may be specified. Unless otherwiseiG               specified by command qualifiers, the output save set williF               have the same attributes for XOR group size, block size,H               CRC, and other attributes as the input save set. Different@               qualifiers may be applied to each output save set.           Descriptione  I               The COPY command reads an OpenVMS BACKUP save set, verifiesiD               that it is readable and consistent, and creates 1 to 5G               copies of that save set. Any rewritten (redundant) blocksaI               in the input save set are eliminated in the COPY operation.tG               For an explanation of rewritten blocks, see Section 4.2.2sG               for Successful Completion with Save Set Condition Report.o  H               You can optionally specify software CRC and XOR protectionH               to be present, absent, or the same as the source save set.H               The default is to make the output save set the same as theG               input save set. The desired block size of the output save H               set can also be specified as different from the input saveD               set. The COPY command regenerates any bad blocks found#               during the operation.n  F                 ________________________ Note ________________________  C                 The size of the save set after a COPY operation may E                 be slightly smaller than the original save set due to D                 the way the OpenVMS BACKUP utility formats the data.  I                                                          Using SSMgr 3-15                     COPY      C                 SSMgr repacks its data records during processing to C                 reduce the space required; there is no loss of dataoD                 from the OpenVMS input save set, and the output save6                 set is compatible with OpenVMS BACKUP.  F                 ______________________________________________________                                                                                       3-16 Using SSMgr    p      I                                                                      COPYL                   Qualifiers                 /ALL                /[NO]ALL (default)                 Command qualifierB  G               This qualifier specifies the behavior of Save Set Manager 4               when save set names contain wildcards.  B               If ALL is specified, then all save sets matching theI               wildcarded input save set file specification are processed.   B               If NOALL is specified, then only the first file nameE               found that matches the wildcarded file specification isf               processed.  C               The qualifier is valid only for the VALIDATE and COPYs               functions.  $               The default is /NOALL.                 /BLOCK_SIZE=n0  '               Output save set qualifierr  D               This qualifier specifies the desired block size of theF               output save set. Valid values for n are between 2048 andG               65024, and are rounded up to the nearest multiple of 512.sH               The block size of the input save set is used if the BLOCK_.               SIZE qualifier is not specified.  E               As required by OpenVMS BACKUP, the upper limit for save I               sets on disk is 32256. If a larger block size is specified, 0               SSMgr will round it down to 32256.  @               This qualifier may not be used with the /IDENTICAL               qualifier.  B               The default is the block size of the input save set.                 /BRIEF (default)  I                                                          Using SSMgr 3-17r v  f               COPY                     Command qualifier.  H               This qualifier specifies that a minimum level of detail isI               to be echoed. The SAVESET function and save set name(s) arefH               echoed; any error information is displayed; and the resultE               of the SAVESET operation is reported. See /FULL for the 2               complete list of output information.  $               The default is /BRIEF.                                                                                 3-18 Using SSMgr s         I                                                                      COPY       (               /CHECKS=([NO]CRC, [NO]XOR)  &               Input save set qualifier  F               This qualifier specifies the optional consistency checksG               that will be performed on the input save set; the defaultt               is CRC, XOR.  F               You must specify the /CHECKS qualifier immediately afterF               the file name of each input save set when specifying theC               input save set. Example 3-12 also shows that when you D               specify both CRC and XOR checks, you must list them in7               parentheses with a comma separating them.   D               If CRC checking is specified and the input save set isG               written with CRC, then the CRC is computed for each blocktI               in the input save set. The computed CRC is compared against 1               the CRC stored in the block header.   E               If XOR checking is specified and the input save set was I               written with XOR redundancy, then a running XOR is computed F               across each XOR group of blocks. The running XOR is then(               compared to the XOR block.  B               Each of these options requires additional processingF               time and may impact the performance of SSMgr. Any CRC orD               XOR inconsistencies are written to the log file and anI               informational message is returned to the calling program or0-               user when processing completes.t                 /COMMENT=stringt  '               Output save set qualifier   F               This qualifier inserts a comment in the output save set.D               The comment string can be up to 252 characters. If theF               comment string is longer than one word or if it containsA               non-alphanumeric characters, it must be enclosed intE               quotation marks ("). The comment from the primary inputt<               save set is not copied to the output save set.  I               The default is no comment string written to the output saves               set.    I                                                          Using SSMgr 3-19i w                  COPY                     /CRC               /NOCRC  '               Output save set qualifier   G               Specifying /CRC causes the CRC to be computed across each I               block of the output save set and stored in the block headeryE               of each block of the output save set. Specifying /NOCRCaB               causes CRC computation to be inhibited on the outputF               save set. If this qualifier is not specified, the CRC isG               computed and stored in the output save set only if it wase,               present in the input save set.  @               This qualifier may not be used with the /IDENTICAL               qualifier.  C               The default is /CRC if the primary input save set waspG               written with CRC and /NOCRC if the primary input save seto&               was written without CRC.                                                             3-20 Using SSMgr    c      I                                                                      COPYe                     /FULLr                 Command qualifieri  H               This qualifier specifies that more detail is to be echoed.B               In addition to information displayed with the /BRIEFD               qualifier, the following information for each save set               is displayed:r                    Save set name$                  Save set group size$                  Save set block size-                  Number of blocks in save set 4                  Nondirectory user files in save set1                  Directory user files in save setc5                  Alias nondirectory files in save set 2                  Alias directory files in save set)                  Unrecoverable CRC errors '                  Recoverable CRC errorse,                  Recoverable checksum errors.                  Unrecoverable checksum errors                  XOR errorsm                  Read errors                  Write errors                   Record errors-                  Unrecoverable missing blocks +                  Recoverable missing blocksi!                  Rewritten blocks   $               The default is /BRIEF.                 /GROUP_SIZE=nN  '               Output save set qualifier   G               This qualifier specifies the XOR group size in the output I               save set. Valid values for n are between 0 and 100. A value <               of 0 specifies that no XOR should be computed.  G               If this qualifier is not specified, the group size of the H               input save set is used for the output save set group size.)               This is the default action.   @               This qualifier may not be used with the /IDENTICAL               qualifier.  I                                                          Using SSMgr 3-21g u  r               COPY                         /IDENTICAL                 Command qualifierw  D               This qualifier does a fast copy of the input save set.E               A fast copy operation copies the contents of each inputnF               save set block to the output save set without validationE               of the block's internal record structure. If errors are F               encountered during this operation, restart the operationG               and include the /OVERRIDE qualifier to continue operation F               even in spite of the errors. See the /OVERRIDE qualifier                description below.  H               Each save set is stored with information that reflects theG               environment in which it was created. In a normal save settG               copy, the information in the output save set reflects the H               environment in which the output save set was created. WithE               the /IDENTICAL qualifier, this information reflects thefB               environment in which the input save set was created.  G               The /IDENTICAL qualifier is not supported for multivolumeaF               output save sets, because you may not be able to restore               such a save set.  G               You may not use /GROUP_SIZE, /BLOCK_SIZE, /CRC, /COMMENT,tG               or /JOURNAL qualifiers with the /IDENTICAL qualifier. You I               may not use the /TERMINAL=LOG qualifier with the /IDENTICAL                qualifier.  *               /JOURNAL[=journal-file-name]                  Save set qualifier  B               This qualifier specifies whether SSMgr will create aC               journal file for the save set. The journal file is ansD               OpenVMS BACKUP journal file with an OpenVMS file name.I               If no journal file name is specified, the journal file willtE               be written to <saveset_name>.BJL in the current defaultt               directory.  F               If a journal file with the same name already exists, theI               new journal file is appended. If it does not already exist,r,               a new journal file is created.           3-22 Using SSMgr e  l      I                                                                      COPY       E               Journal files created by SSMgr will not list the labels E               of follow-on volumes in multivolume tape sets. Also, if D               COPY/IDENTICAL is used to copy a multivolume tape to aH               single volume tape, the journal file will still list it as%               a multivolume tape set.   I               These differences from Backup created journal files are dueeI               to a limitation in VMS that does not allow a non-privilegedaG               process to obtain the volume labels of a multivolume tape                set.  H               You must specify this qualifier immediately after the save:               set file name specifier on the command line.  @               This qualifier is valid for all save set file nameA               specifiers, input or output, on all SSMgr commands.i  D               This qualifier may not be combined with the /IDENTICAL               qualifier.  G               Journal files will be created for each save set specified B               on the command line that is followed by the /JOURNALH               qualifier. If more than one journal file is being created,4               each journal file name must be unique.  C               For example, SAVESET COPY FILES.BCK/JOURNAL FILES.SAV E               /JOURNAL is illegal, because the resulting journal file 9               names would each be, by default, FILES.BJL.a  (               The default is /NOJOURNAL.                              I                                                          Using SSMgr 3-23r e                  COPY      0               /LOG_FILE[=logfile-name] (default)               /NOLOG_FILEd                 Command qualifier   B               This qualifier causes SSMgr to write events to a logD               file specified by logfile-name. The logfile-name is anE               ASCII file with an OpenVMS file name. If not specified, E               the default log file name is SAVESET.LOG in the currentRH               default directory. You can suppress creating a default logH               file by using /NOLOG_FILE or by including /LOG_FILE=NL: onG               the command line. The following events are written to theA               SAVESET.LOG file:n  )               o  Each invocation of SSMgr   C               o  All output returned to the user or calling program   D               o  Any errors or warnings encountered while processing*                  input or output save sets  "               o  Operator requests  G               Wildcards may not be used in the specification of logfile                names.                 /OVERRIDE #               /NOOVERRIDE (default).                 Command qualifier   D               This qualifier allows you to override certain internalD               consistency checks to allow execution to continue withG               unreadable or unrecoverable blocks in the input save set._H               This qualifier allows you to make a complete and identical)               copy of a damaged save set._  G               You must use the /IDENTICAL qualifier when specifying the_F               /OVERRIDE qualifier to allow continued processing of theF               save set after encountering unrecoverable input save setE               errors. The /IDENTICAL and /OVERRIDE qualifiers must be E               specified in that order on the command line as shown in                Example 3-4.             3-24 Using SSMgr    s      I                                                                      COPY                      /REWIND !               /NOREWIND (default)E  0               Input or output save set qualifier  E               For magnetic tape volumes only, REWIND directs SSMgr to E               rewind the magnetic tape to the beginning-of-tape (BOT)YF               marker before reading or writing the volume. If /ALL wasF               specified, the rewind only happens once before the first                SAVESET operation.  C               You must specify this qualifier immediately after the C               applicable file name on the command line, as shown in_               Example 3-12._  E               The following consequences result when using the REWIND                qualifier:  H               o  If specified with an input save set, SSMgr searches forF                  the specified file starting at the BOT position. ThisF                  allows SSMgr to find files located before the current&                  position of the tape.  G               o  If specified with an output save set, SSMgr overwrites H                  the tape starting at the BOT position. All files on the.                  tape are therefore destroyed.  G               The default for this qualifier is /NOREWIND, which causesdA               SSMgr to start processing the tape from the currentu               position.o  9               /TERMINAL=([NO]ERRORS, [NO]EVENTS, [NO]LOG)                  Command qualifier   D               This qualifier specifies what class(es) of informationI               should be displayed on the user's terminal during executiont%               of the SAVESET command.n  I               If ERRORS is specified, then all error conditions occurring G               during execution are displayed as they occur, in addition I               to being included in the final report at the end of command ,               execution and in the log file.  H               If EVENTS is specified, then all nonerror event conditionsB               occurring during execution (e.g., tape switches) are&               displayed as they occur.  I                                                          Using SSMgr 3-25  c  e               COPY      D               If LOG is specified, then the names of all output userB               files (for COPY and MERGE) are displayed as they areH               written to the output save set. For VALIDATE, the names ofG               all input user files are displayed as they are processed.iB               The /TERMINAL=LOG qualifier may not be used with the#               /IDENTICAL qualifier.a    F                 ________________________ Note ________________________  D                 When a multivolume save set is copied using the COPYB                 /IDENTICAL command, volume switch information fromD                 the original input save set will be preserved in theA                 single volume copy, and it will be reported as ane                 EVENT.  F                 ______________________________________________________  =               The default is /TERMINAL=(ERRORS,EVENTS,NOLOG).                                                              3-26 Using SSMgr           I                                                                      COPYe                 Examples    &               Example 3-2 COPY Command  R               $ saveset copy mkb200:savesetua013.a/rewind disk$user:[kits]copy.sav,               ERRORS terminal option enabled,               EVENTS terminal option enabled6               Rewinding MKB200: to beginning of volume(               Rewind of MKB200: complete4               Opening file MKB200:[]SAVESETUA013.A;1E               Primary input save set MKB200:[]SAVESETUA013.A;1 openedh>               Output save set DISK$USER:[KITS]COPY.SAV; opened  R               POLYCENTER(TM) Save Set Manager V1.3A  Time: 18-JUL-1996 13:45:05.49  (                   SAVESET function: COPYC                   Primary input save set: MKB200:[]SAVESETUA013.A;1v#                     No journal files<                   Output save set: DISK$USER:[KITS]COPY.SAV;#                     No journal file   0                   Final status of each save set:  =                     Save set name:  MKB200:[]SAVESETUA013.A;1l(                       No errors detected  =                     Save set name:  DISK$USER:[KITS]COPY.SAV; (                       No errors detected  F                  In Example 3-2, the tape mounted on mkb200 is rewoundF                  and then the save set, SAVESETUA013.A, is copied fromI                  that tape to a file called copy.sav on disk$user:[kits], =                  with all save set characteristics preserved.k  E               Example 3-3 COPY Command with Multiple Output Save Sets   I                                                  (continued on next page)             I                                                          Using SSMgr 3-27r e  i               COPY      H               Example 3-3 (Cont.) COPY Command with Multiple Output Save&                                   Sets  D               $ saveset copy full.bck mkb200:image.bck/block=32768 -(               mkb500:full20.bck/group=20,               ERRORS terminal option enabled,               EVENTS terminal option enabledJ               Primary input save set DISK$USER:[NDIAMOND]FULL.BCK;1 opened.               Opening file MKB200:[]IMAGE.BCK;8               Output save set MKB200:[]IMAGE.BCK; opened/               Opening file MKB500:[]FULL20.BCK; 9               Output save set MKB500:[]FULL20.BCK; opened   R               POLYCENTER(TM) Save Set Manager V1.3A  Time: 18-JUL-1996 13:56:01.74  (                   SAVESET function: COPYH                   Primary input save set: DISK$USER:[NDIAMOND]FULL.BCK;1#                     No journal file 6                   Output save set: MKB200:[]IMAGE.BCK;#                     No journal filea7                   Output save set: MKB500:[]FULL20.BCK; #                     No journal filey  0                   Final status of each save set:  B                     Save set name:  DISK$USER:[NDIAMOND]FULL.BCK;1(                       No errors detected  7                     Save set name:  MKB200:[]IMAGE.BCK;t(                       No errors detected  8                     Save set name:  MKB500:[]FULL20.BCK;(                       No errors detected  ;                  In Example 3-3, two tape drives and a disk ?                  drive are being used. The input save set is onuG                  DISK$USER:[NDIAMOND] and is named FULL.BCK. Two copieshC                  of this save set are being made. One copy is being E                  written to the tape mounted on MKB200, with the sameyF                  name and other characteristics as the input save set,G                  except that the block size on the output tape is beingeF                  explicitly set to 32768, regardless of the block sizeI                  on the input save set. A second copy is being written topG                  the tape mounted on MKB500. For this copy, the name ofiI                  the save set is changed to FULL20.BCK, the group size ish  I                                                  (continued on next page)i           3-28 Using SSMgr l  n      I                                                                      COPYe      H               Example 3-3 (Cont.) COPY Command with Multiple Output Save&                                   SetsH                  being explicitly set to 20, and all other characterists5                  of the input save set are preserved.       B               Example 3-4 COPY Command with IDENTICAL and OVERRIDE<                           Qualifiers on Save Set with Errors  O               $ saveset copy/identical/override star.sav mkb200:rock.bck/rewind ,               ERRORS terminal option enabled,               EVENTS terminal option enabled6               Rewinding MKB200: to beginning of volume(               Rewind of MKB200: completeE               Primary input save set DISK$USER:[GRD]STAR.SAV;1 openedn-               Opening file MKB200:[]ROCK.BCK;d7               Output save set MKB200:[]ROCK.BCK; opened N               CRC error: block number 33 in save set DISK$USER:[GRD]STAR.SAV;1M               Error recovery successful in save set DISK$USER:[GRD]STAR.SAV;1lS               %SAVESET-I-MISSINGBLK, Missing block could not be regenerated in fileR*               DISK$USER:[GRDEAD]STAR.SAV;1N               CRC error: block number 35 in save set DISK$USER:[GRD]STAR.SAV;1I               Recovery unsuccessful in save set DISK$USER:[GRD]STAR.SAV;1 Q               %SAVESET-I-BADCRC, Data CRC error in file DISK$USER:[GRD]STAR.SAV;1 N               CRC error: block number 42 in save set DISK$USER:[GRD]STAR.SAV;1L               Block recovered from XOR in save set DISK$USER:[GRD]STAR.SAV;1N               CRC error: block number 48 in save set DISK$USER:[GRD]STAR.SAV;1I               Recovery unsuccessful in save set DISK$USER:[GRD]STAR.SAV;1 Q               %SAVESET-I-BADCRC, Data CRC error in file DISK$USER:[GRD]STAR.SAV;1eI               XOR error at block 55 in save set DISK$USER:[GRD]STAR.SAV;1sN               CRC error: block number 60 in save set DISK$USER:[GRD]STAR.SAV;1I               Recovery unsuccessful in save set DISK$USER:[GRD]STAR.SAV;1aQ               %SAVESET-I-BADCRC, Data CRC error in file DISK$USER:[GRD]STAR.SAV;1CI               XOR error at block 66 in save set DISK$USER:[GRD]STAR.SAV;1r  R               POLYCENTER(TM) Save Set Manager V1.3A  Time: 18-JUL-1996 14:38:49.31  I                                                  (continued on next page)             I                                                          Using SSMgr 3-29                     COPY      A               Example 3-4 (Cont.) COPY Command with IDENTICAL and F                                   OVERRIDE Qualifiers on Save Set with(                                   Errors  (                   SAVESET function: COPYF                   Primary input save set: DISK$USER:[GRDEAD]STAR.SAV;1#                     No journal file 5                   Output save set: MKB200:[]ROCK.BCK;e#                     No journal filet  0                   Final status of each save set:  @                     Save set name:  DISK$USER:[GRDEAD]STAR.SAV;1;                     Unrecoverable CRC errors:             3.;                     Recoverable CRC errors:               2U;                     XOR errors:                           2   6                     Save set name:  MKB200:[]ROCK.BCK;(                       No errors detected  B                  In Example 3-4, a copy of the save set, STAR.SAV,G                  located in the default disk directory, is being copiedsE                  to a tape mounted on tape device MKB200. The tape isdE                  rewound before the copy is initiated. An "identical"tG                  copy is being made; i.e., no internal record structurefF                  validation is being done and the save set informationC                  stored within the output save set will reflect the E                  environment in which the input save set was created, E                  rather than the environment in which the output save G                  set is being created. Further, the /OVERRIDE qualifier C                  results in continued operation even in the face ofhD                  errors, accepting the fact that the output save set-                  may not be fully restorable.t  C               Example 3-5 COPY with Wildcarding, Journaling, and No !                           Logfile   I                                                  (continued on next page)                        3-30 Using SSMgr o  s      I                                                                      COPYs      H               Example 3-5 (Cont.) COPY with Wildcarding, Journaling, and,                                   No Logfile  &               $ saveset copy/all/nologH               _Input Save Set: dka400:[dcsc030.kit]*.*/checks=(crc,xor)-               _/journal=*.bjlMB               _Output Save Set: mkb200:*.*/crc/comment="DCSC Copy"!               _Output Save Set 2:p,               ERRORS terminal option enabled,               EVENTS terminal option enabledK               Primary input save set DKA400:[DCSC030.KIT]DCSC030.A;1 openedm.               Opening file MKB200:[]DCSC030.A;8               Output save set MKB200:[]DCSC030.A; opened  R               POLYCENTER(TM) Save Set Manager V1.3A  Time: 18-JUL-1996 14:53:20.21  (                   SAVESET function: COPYI                   Primary input save set: DKA400:[DCSC030.KIT]DCSC030.A;1 @                     Journal file: DISK$GREEN:[DRAGON]DCSC030.BJL6                   Output save set: MKB200:[]DCSC030.A;#                     No journal fileo  0                   Final status of each save set:  C                     Save set name:  DKA400:[DCSC030.KIT]DCSC030.A;1 (                       No errors detected  7                     Save set name:  MKB200:[]DCSC030.A;e(                       No errors detected  K               Primary input save set DKA400:[DCSC030.KIT]DCSC030.B;1 openedS.               Opening file MKB200:[]DCSC030.B;8               Output save set MKB200:[]DCSC030.B; opened  R               POLYCENTER(TM) Save Set Manager V1.3A  Time: 18-JUL-1996 14:56:45.83  (                   SAVESET function: COPYI                   Primary input save set: DKA400:[DCSC030.KIT]DCSC030.B;1o@                     Journal file: DISK$GREEN:[DRAGON]DCSC030.BJL6                   Output save set: MKB200:[]DCSC030.B;#                     No journal fileT  0                   Final status of each save set:  I                                                  (continued on next page)c  I                                                          Using SSMgr 3-31e a  n               COPY      H               Example 3-5 (Cont.) COPY with Wildcarding, Journaling, and,                                   No Logfile  C                     Save set name:  DKA400:[DCSC030.KIT]DCSC030.B;1j(                       No errors detected  7                     Save set name:  MKB200:[]DCSC030.B; (                       No errors detected  K               Primary input save set DKA400:[DCSC030.KIT]DCSC030.C;1 opened .               Opening file MKB200:[]DCSC030.C;8               Output save set MKB200:[]DCSC030.C; opened  R               POLYCENTER(TM) Save Set Manager V1.3A  Time: 18-JUL-1996 15:02:50.30  (                   SAVESET function: COPYI                   Primary input save set: DKA400:[DCSC030.KIT]DCSC030.C;1e@                     Journal file: DISK$GREEN:[DRAGON]DCSC030.BJL6                   Output save set: MKB200:[]DCSC030.C;#                     No journal filen  0                   Final status of each save set:  C                     Save set name:  DKA400:[DCSC030.KIT]DCSC030.C;1h(                       No errors detected  7                     Save set name:  MKB200:[]DCSC030.C; (                       No errors detected  *                 Summary of COPY operations  <                   Total operations attempted:              3<                   Operations completing successfully:      3               $   5                  In Example 3-5, all the save sets inaG                  dka400:[dcsc030.kit] are copied to the tape mounted on H                  mkb200. No log file will be generated. CRC checking andG                  XOR checking will be performed on all the save sets asrI                  they are being copied. A journal of the files is createdoF                  for each save set and given the name of each save setG                  with the .bjl extension. CRC is computed for each saveeI                  set on the tape, and the comment, "DCSC copy" is entered I                  into the save set comment field because the journal file E                  name is the same for all three save sets copied. The E                  second and third save sets' journal file entries are   I                                                  (continued on next page)f           3-32 Using SSMgr d  n      I                                                                      COPY       H               Example 3-5 (Cont.) COPY with Wildcarding, Journaling, and,                                   No LogfileH                  appended to the journal file created for the first save                  set.n      E               Example 3-6 COPY with /JOURNAL and /TERMINAL Qualifiersg  9               $ saveset copy/terminal=(errors,events,log)k<               _Input Save Set: mkb200:SAVESETUA013.a/journal.               _Output Save Set: savesetua013.a!               _Output Save Set 2:E)               LOG terminal option enabledi,               ERRORS terminal option enabled,               EVENTS terminal option enabled4               Opening file MKB200:[]SAVESETUA013.A;1E               Primary input save set MKB200:[]SAVESETUA013.A;1 opened H               Output save set DISK$USER:[SOFTWARE]SAVESETUA013.A; openedK               Processing user file: [SOFTWARE.SAVESETUA013]KITINSTAL.COM;29 M               Processing user file: [SOFTWARE.SAVESETUA013]SAVESET$IVP.COM;14tH               Processing user file: [SOFTWARE.SAVESETUA013]SAVESET.CLD;4H               Processing user file: [SOFTWARE.SAVESETUA013]SAVESET.HLP;4;               Processing user file: [SOFTWARE.SAVESETUA013] +                SAVESETUA013.RELEASE_NOTES;3 ;               Processing user file: [SOFTWARE.SAVESETUA013]c.                SAVESETUA013_RELEASE_NOTES.PS;5;               Processing user file: [SOFTWARE.SAVESETUA013] (                SAVESET_COVER_LETTER.PS;6;               Processing user file: [SOFTWARE.SAVESETUA013] '                SAVESET_USER_GUIDE.PS;17 ;               Processing user file: [SOFTWARE.SAVESETUA013]''                SAVESET_USER_GUIDE.TXT;8   R               POLYCENTER(TM) Save Set Manager V1.3A  Time: 18-JUL-1996 15:31:56.90  I                                                  (continued on next page)r                I                                                          Using SSMgr 3-33                     COPY      B               Example 3-6 (Cont.) COPY with /JOURNAL and /TERMINAL,                                   Qualifiers  (                   SAVESET function: COPYC                   Primary input save set: MKB200:[]SAVESETUA013.A;1 3                     Journal file: SAVESETUA013.BJL; F                   Output save set: DISK$USER:[SOFTWARE]SAVESETUA013.A;#                     No journal file   0                   Final status of each save set:  =                     Save set name:  MKB200:[]SAVESETUA013.A;1 (                       No errors detected  G                     Save set name:  DISK$USER:[SOFTWARE]SAVESETUA013.A;u(                       No errors detected  ?                  Example 3-6 shows how to enable all classes of_I                  information that can be displayed to a terminal during asG                  copy operation that copies the save set SAVESETUA013.AuF                  from the tape mounted on MKB200 to the directory fromI                  which the command is issued. Note the prompt for anothereE                  output save set, should you decide to create another_B                  copy during the same operation. If you don't wantH                  another copy, hit <return>. A journal file of the name,E                  SAVESETUA013.BJL, is created in that same directory.   G               Example 3-7 COPY with /BLOCK_SIZE, /GROUP_SIZE, and /FULL $                           Qualifiers  7               $ saveset copy/full mkb200:savesetua013.aaF               _Output Save Set: copy.sav/block_size=3072/group_size=20!               _Output Save Set 2:V,               ERRORS terminal option enabled,               EVENTS terminal option enabled4               Opening file MKB200:[]SAVESETUA013.A;1E               Primary input save set MKB200:[]SAVESETUA013.A;1 openedtB               Output save set DISK$USER:[SOFTWARE]COPY.SAV; opened  R               POLYCENTER(TM) Save Set Manager V1.3A  Time: 18-JUL-1996 15:42:28.56  I                                                  (continued on next page)                3-34 Using SSMgr s         I                                                                      COPY       I               Example 3-7 (Cont.) COPY with /BLOCK_SIZE, /GROUP_SIZE, and 2                                   /FULL Qualifiers  (                   SAVESET function: COPYC                   Primary input save set: MKB200:[]SAVESETUA013.A;1 #                     No journal fileK@                   Output save set: DISK$USER:[SOFTWARE]COPY.SAV;#                     No journal filee  0                   Final status of each save set:  =                     Save set name:  MKB200:[]SAVESETUA013.A;1 <                     Save set group size:                  25>                     Save set block size:                  9216=                     Blocks in save set:                   106u;                     Nondirectory files in save set:       9 ;                     Directory files in save set:          0 ;                     Alias nondirectory files in save set: 0i;                     Alias directories in save set:        0 ;                     Unrecoverable CRC errors:             0 ;                     Recoverable CRC errors:               02;                     Unrecoverable checksum errors:        0r;                     Recoverable checksum errors:          0 ;                     XOR errors:                           0n;                     Read errors:                          0 ;                     Write errors:                         0v;                     Record errors:                        0M;                     Unrecoverable missing blocks:         0F;                     Recoverable missing blocks:           0a;                     Rewritten blocks:                     0 (                       No errors detected  I                                                  (continued on next page)                         I                                                          Using SSMgr 3-35u l  l               COPY      I               Example 3-7 (Cont.) COPY with /BLOCK_SIZE, /GROUP_SIZE, and 2                                   /FULL Qualifiers  A                     Save set name:  DISK$USER:[SOFTWARE]COPY.SAV; <                     Save set group size:                  20>                     Save set block size:                  3072=                     Blocks in save set:                   361F;                     Nondirectory files in save set:       9 ;                     Directory files in save set:          0 ;                     Alias nondirectory files in save set: 0 ;                     Alias directories in save set:        0o;                     Unrecoverable CRC errors:             0n;                     Recoverable CRC errors:               0d;                     Unrecoverable checksum errors:        0h;                     Recoverable checksum errors:          0 ;                     XOR errors:                           0 ;                     Read errors:                          0 ;                     Write errors:                         0w;                     Record errors:                        0t;                     Unrecoverable missing blocks:         0g;                     Recoverable missing blocks:           0 ;                     Rewritten blocks:                     0 (                       No errors detected  >                  In Example 3-7, the save set, SAVESETUA013.A,=                  is copied from the tape mounted on MKB200 totE                  DISK$USER:[SOFTWARE]COPY.SAV. The block size will be H                  3072 and the group size = 20 in the save set, COPY.SAV.I                  Note the prompt for an additional output save set if allOF                  the information is not entered on the initial commandI                  line. A full report will be generated upon completion ofr$                  the copy operation.                                   3-36 Using SSMgr           I                                                                     MERGEo      I         _________________________________________________________________s  
         MERGE]  )               Merges two input save sets.e           Format  B               MERGE  primary-input-ss secondary-input-ss output-ssD                      [output-ss] [output-ss] [output-ss] [output-ss]           Parameters                 primary-input-ssF               OpenVMS file name of an input save set. The primary saveE               set can be an image, incremental, or file-oriented save]               set.                  secondary-input-ssB               OpenVMS file name of a secondary input save set. TheI               secondary input save set is an incremental or file-oriented,H               save set that covers a period of time starting at the time/               the primary save set was created.R                 output-ss C               OpenVMS file name(s) of the output save set(s). Up to F               five output save sets may be specified. Unless otherwiseG               specified by command qualifiers, the output save set will F               have the same attributes for XOR group size, block size,F               CRC, and other attributes as the primary input save set.E               Different qualifiers may be applied to each output save$               set.           Descriptiony  H               The MERGE operation takes two OpenVMS BACKUP save sets andE               produces 1 to 5 output save sets. Acceptable input save H               sets include image backups, incremental backups, and file-E               oriented save sets. The following combinations of input4I               primary and secondary save sets result in the listed output                save sets:        I                                                          Using SSMgr 3-37            
         MERGE     I               ___________________________________________________________ /               Primary Input     Secondary Input I               Save_Set__________Save_Set__________Output_Save_Set________i  7               Image             Incremental       ImageE  =               Incremental       Incremental       Incremental   ?               Incremental       File-oriented     File-oriented   ?               File-oriented     Incremental       File-orientede  I               File-oriented_____File-oriented_____File-oriented__________   ;               No other combinations of save sets are legal.   E               The output save set contains the merge of the two input E               save sets. If the primary save set was an image backup,tD               the output saves set contain an image backup up to theD               time that the secondary input save set was created. IfD               the primary and secondary save sets were incrementals,B               the output save set will contain an incremental saveE               set that spans the combined time frame of the two inputt               incrementals.   B               The output save sets' CRC and XOR protections can beC               independently specified to be present, absent, or the D               same as the primary save set. If detected by SSMgr, anG               attempt to merge a primary save set with an inappropriater@               incremental save set, such as from another disk orD               noncontiguous time period, will result in a diagnosticE               message and an aborted operation. However, SSMgr cannot G               detect all such inappropriate combinations; the result of G               such an inappropriate merge will be a legal save set, buti1               its contents may not be meaningful.   E               The MERGE operation does not accept physical save sets.n           Qualifiers                 /BLOCK_SIZE=nS                   3-38 Using SSMgr           I                                                                     MERGE-      '               Output save set qualifierd  D               This qualifier specifies the desired block size of theF               output save set. Valid values for n are between 2048 andG               65024, and are rounded up to the nearest multiple of 512. I               The block size of the primary input save set is used if thet4               BLOCK_SIZE qualifier is not specified.  @               As required by OpenVMS BACKUP, the upper limit forD               save sets on disks is 32256. If a larger block size is;               specified, SSMgr will round it down to 32256.                  /BRIEF (default)                 Command qualifiera  E               This qualifier specifies that a minimum level of detailuH               is to be echoed. The SAVESET function and save set name(s)E               are echoed; any error information is displayed; and theSH               result of the SAVESET operation is reported. See /FULL for4               a complete list of output information.    '               /CHECKS=([NO]CRC,[NO]XOR)   &               Input save set qualifier  F               This qualifier specifies the optional consistency checksG               that will be performed on the input save set; the defaulte               is CRC, XOR.  C               You must specify this qualifier immediately after the E               file name of the save set on the command line, as shown0G               in Example 3-10. Example 3-12 shows that when you specify3H               both CRC and XOR checks, you must list them in parentheses+               with a comma separating them.   D               If CRC checking is specified and the input save set isG               written with CRC, then the CRC is computed for each blockCH               in the input save set. The CRC is compared against the CRC)               stored in the block header.         I                                                          Using SSMgr 3-39            
         MERGE       A               If XOR checking is specified and the input save setxD               was written with XOR redundancy, then a running XOR isG               computed across each XOR group of blocks. The running XORK+               is compared to the XOR block.   B               Each of these options requires additional processingF               time and may impact the performance of SSMgr. Any CRC orD               XOR inconsistencies are written to the log file and anI               informational message is returned to the calling program or .               user when the command completes.                                                                               3-40 Using SSMgr i         I                                                                     MERGE                          /COMMENT=stringE                 Command qualifier   F               This qualifier inserts a comment in the output save set.D               The string can be up to 252 characters. If the commentC               string is longer than one word or if it contains non- G               alphanumeric characters, it must be enclosed in quotationKG               marks ("). If not specified, no comment is written to the                output save set.                   /CRC               /NOCRC  '               Output save set qualifiert  G               Specifying /CRC causes the CRC to be computed across eachII               block of the output save set and stored in the block header E               of each block of the output save set. Specifying /NOCRCeB               causes CRC computation to be inhibited on the outputF               save set. If this qualifier is not specified, the CRC isG               computed and stored in the output save set only if it was 4               present in the primary input save set.                   /FULLt                 Command qualifierv  H               This qualifier specifies that more detail is to be echoed.B               In addition to information displayed with the /BRIEFD               qualifier, the following information for each save set               is displayed:                     Save set name$                  Save set group size$                  Save set block size-                  Number of blocks in save setM4                  Nondirectory user files in save set1                  Directory user files in save set 5                  Alias nondirectory files in save setn  I                                                          Using SSMgr 3-41p e  o      
         MERGEa      2                  Alias directory files in save set)                  Unrecoverable CRC errorsd'                  Recoverable CRC errors ,                  Recoverable checksum errors.                  Unrecoverable checksum errors                  XOR errorst                  Read errors                  Write errors2                  Record errors-                  Unrecoverable missing blocksp+                  Recoverable missing blocksp!                  Rewritten blocks                                                                            3-42 Using SSMgr o  e      I                                                                     MERGE                          /GROUP_SIZE=nR  '               Output save set qualifier   G               This qualifier specifies the XOR group size in the output I               save set. Valid values for n are between 0 and 100. A value D               of 0 specifies that no XOR should be computed. If thisG               qualifier is not specified, the group size of the primaryS%               input save set is used.     *               /JOURNAL[=journal-file-name]                  Save set qualifier  B               This qualifier specifies whether SSMgr will create aC               journal file for the save set. The journal file is ansD               OpenVMS BACKUP journal file with an OpenVMS file name.I               If no journal file name is specified, the journal file will E               be written to <saveset_name>.BJL in the current default)               directory.  F               If a journal file with the same name already exists, theI               new journal file is appended. If it does not already exist, ,               a new journal file is created.  E               Journal files created by SSMgr will not list the labelsOE               of follow-on volumes in multivolume tape sets. Also, iffD               COPY/IDENTICAL is used to copy a multivolume tape to aH               single volume tape, the journal file will still list it as%               a multivolume tape set.   I               These differences from Backup created journal files are due I               to a limitation in VMS that does not allow a non-privileged G               process to obtain the volume labels of a multivolume tape                set.  H               You must specify this qualifier immediately after the save:               set file name specifier on the command line.  @               This qualifier is valid for all save set file nameA               specifiers, input or output, on all SSMgr commands.s  I                                                          Using SSMgr 3-43            
         MERGEm      G               Journal files will be created for each save set specifiedsB               on the command line that is followed by the /JOURNALH               qualifier. If more than one journal file is being created,I               each journal file name must be unique. For example, SAVESETnI               MERGE FULL.BCK/JOURNAL INCR.BCK/JOURNAL FULL.BCK/JOURNAL iseH               illegal, because the resulting journal file names would be/               FULL.BJL, INCR.BJL, and FULL.BJL.   (               The default is /NOJOURNAL.                                                                                 3-44 Using SSMgr =         I                                                                     MERGE       0               /LOG_FILE[=logfile-name] (default)               /NOLOG_FILEA                 Command qualifierr  G               This qualifier causes SSMgr to write events to a log filevE               specified by logfile-name. The logfile-name is an ASCIITF               file with an OpenVMS file name. By default, a logfile isE               created for every execution of an SSMgr command. If not H               specified, the default log file name is SAVESET.LOG in theF               current default directory. You can suppress the creationH               of a default log file by using /NOLOG_FILE or bu includingI               /LOG_FILE=NL: on the command line. The following events are .               written to the SAVESET.LOG file:  )               o  Each invocation of SSMgrn  C               o  All output returned to the user or calling programA  D               o  Any errors or warnings encountered while processing                   input save sets  "               o  Operator requests  G               Wildcards may not be used in the specification of logfile5               names.                 /REWIND !               /NOREWIND (default)   0               Input or output save set qualifier  E               For magnetic tape volumes only, REWIND directs SSMgr to E               rewind the magnetic tape to the beginning-of-tape (BOT)o/               marker before reading the volume.   C               You must specify this qualifier immediately after theoC               applicable file name on the command line, as shown inR5               Example 3-12 for the /CHECKS qualifier.e  E               The following consequences result when using the REWINDm               qualifier:  H               o  If specified with an input save set, SSMgr searches forF                  the specified file starting at the BOT position. ThisF                  allows SSMgr to find files located before the current&                  position of the tape.  I                                                          Using SSMgr 3-45  s         
         MERGE       G               o  If specified with an output save set, SSMgr overwrites D                  the tape starting at BOT. All files on the tape are%                  therefore destroyed.   G               The default for this qualifier is /NOREWIND, which causesiA               SSMgr to start processing the tape from the currentm               position.     9               /TERMINAL=([NO]ERRORS, [NO]EVENTS, [NO]LOG)                  Command qualifier   D               This qualifier specifies what class(es) of informationI               should be displayed on the user's terminal during executiono%               of the SAVESET command.   I               If ERRORS is specified, then all error conditions occurringoG               during execution are displayed as they occur, in additioneI               to being included in the final report at the end of command ,               execution and in the log file.  H               If EVENTS is specified, then all nonerror event conditionsB               occurring during execution (e.g., tape switches) are&               displayed as they occur.  D               If LOG is specified, then the names of all output userB               files (for COPY and MERGE) are displayed as they areH               written to the output save set. For VALIDATE, the names ofG               all input user files are displayed as they are processed.   =               The default is /TERMINAL=(ERRORS,EVENTS,NOLOG).            Examples  F                  In Example 3-8, an image save set, full.bck, is beingF                  merged with an incremental save set, incr.bck, in theD                  default disk directory. Two copies of the resultantE                  virtual image save set are being created, one in thedB                  current default directory and another on the tapeI                  mounted on device mbk500:. Each output save set is namedu                  merge.bck.C               3-46 Using SSMgr    m      I                                                                     MERGE       '               Example 3-8 MERGE Command   J               $ saveset merge full.bck incr.bck merge.bck mkb500:merge.bck,               ERRORS terminal option enabled,               EVENTS terminal option enabledI               Primary input save set DISK$MUSIC:[MOZART]FULL.BCK;1 opened K               Secondary input save set DISK$MUSIC:[MOZART]INCR.BCK;1 openedsB               Output save set DISK$MUSIC:[MOZART]MERGE.BCK; opened.               Opening file MKB500:[]MERGE.BCK;8               Output save set MKB500:[]MERGE.BCK; opened  R               POLYCENTER(TM) Save Set Manager V1.3A  Time: 18-JUL-1996 16:03:43.18  )                   SAVESET function: MERGEeG                   Primary input save set: DISK$MUSIC:[MOZART]FULL.BCK;1 #                     No journal filesI                   Secondary input save set: DISK$MUSIC:[MOZART]INCR.BCK;1 #                     No journal filet@                   Output save set: DISK$MUSIC:[MOZART]MERGE.BCK;#                     No journal file 6                   Output save set: MKB500:[]MERGE.BCK;#                     No journal files  0                   Final status of each save set:  A                     Save set name:  DISK$MUSIC:[MOZART]FULL.BCK;1 (                       No errors detected  A                     Save set name:  DISK$MUSIC:[MOZART]INCR.BCK;1,(                       No errors detected  A                     Save set name:  DISK$MUSIC:[MOZART]MERGE.BCK; (                       No errors detected7                     Save set name:  MKB500:[]MERGE.BCK;b(                       No errors detected                    I                                                          Using SSMgr 3-47s    s      
         MERGEr          G               Example 3-9 MERGE Command with /FULL, /LOG, and /TERMINALi$                           Qualifiers  I               $ saveset merge/full/log=merge.log/terminal=error incr2.bck4,               _Secondary Save Set: incr3.bckG               _Output Save Set: incr4.bck/group_size=0/block_size=32256 !               _Output Save Set 2: ,               ERRORS terminal option enabled,               EVENTS terminal option enabledJ               Primary input save set DISK$MUSIC:[EAGLES]INCR2.BCK;1 openedL               Secondary input save set DISK$MUSIC:[EAGLES]INCR3.BCK;1 openedB               Output save set DISK$MUSIC:[EAGLES]INCR4.BCK; opened  R               POLYCENTER(TM) Save Set Manager V1.3A  Time: 18-JUL-1996 16:11:55.01  )                   SAVESET function: MERGE H                   Primary input save set: DISK$MUSIC:[EAGLES]INCR2.BCK;1#                     No journal fileeJ                   Secondary input save set: DISK$MUSIC:[EAGLES]INCR3.BCK;1#                     No journal file @                   Output save set: DISK$MUSIC:[EAGLES]INCR4.BCK;#                     No journal fileh  0                   Final status of each save set:  I                                                  (continued on next page)e                                           3-48 Using SSMgr    h      I                                                                     MERGEv      E               Example 3-9 (Cont.) MERGE Command with /FULL, /LOG, andi6                                   /TERMINAL Qualifiers  B                     Save set name:  DISK$MUSIC:[EAGLES]INCR2.BCK;1<                     Save set group size:                  10?                     Save set block size:                  32256t=                     Blocks in save set:                   146v=                     Nondirectory files in save set:       140t<                     Directory files in save set:          17;                     Alias nondirectory files in save set: 0 ;                     Alias directories in save set:        0 ;                     Files removed by merge:               0 ;                     Unrecoverable CRC errors:             0e;                     Recoverable CRC errors:               0 ;                     Unrecoverable checksum errors:        0l;                     Recoverable checksum errors:          0Z;                     XOR errors:                           0 ;                     Read errors:                          0 ;                     Write errors:                         0 ;                     Record errors:                        0t;                     Unrecoverable missing blocks:         0w;                     Recoverable missing blocks:           0n;                     Rewritten blocks:                     0 (                       No errors detected  I                                                  (continued on next page)e                                      I                                                          Using SSMgr 3-49            
         MERGEw      E               Example 3-9 (Cont.) MERGE Command with /FULL, /LOG, and 6                                   /TERMINAL Qualifiers  B                     Save set name:  DISK$MUSIC:[EAGLES]INCR3.BCK;1<                     Save set group size:                  10?                     Save set block size:                  32256 =                     Blocks in save set:                   234 ;                     Nondirectory files in save set:       4 <                     Directory files in save set:          17;                     Alias nondirectory files in save set: 0o;                     Alias directories in save set:        0m;                     Files removed by merge:               0 ;                     Unrecoverable CRC errors:             0t;                     Recoverable CRC errors:               0e;                     Unrecoverable checksum errors:        0p;                     Recoverable checksum errors:          0a;                     XOR errors:                           0 ;                     Read errors:                          0k;                     Write errors:                         0t;                     Record errors:                        0 ;                     Unrecoverable missing blocks:         0e;                     Recoverable missing blocks:           0 ;                     Rewritten blocks:                     0M(                       No errors detected  I                                                  (continued on next page)                                                3-50 Using SSMgr           I                                                                     MERGEs      E               Example 3-9 (Cont.) MERGE Command with /FULL, /LOG, anda6                                   /TERMINAL Qualifiers  A                     Save set name:  DISK$MUSIC:[EAGLES]INCR4.BCK;e;                     Save set group size:                  0o?                     Save set block size:                  32256 =                     Blocks in save set:                   326 =                     Nondirectory files in save set:       144r<                     Directory files in save set:          17;                     Alias nondirectory files in save set: 0T;                     Alias directories in save set:        0 ;                     Files removed by merge:               0 ;                     Unrecoverable CRC errors:             0e;                     Recoverable CRC errors:               0t;                     Unrecoverable checksum errors:        0 ;                     Recoverable checksum errors:          0f;                     XOR errors:                           0 ;                     Read errors:                          0 ;                     Write errors:                         0/;                     Record errors:                        0 ;                     Unrecoverable missing blocks:         0 ;                     Recoverable missing blocks:           0g;                     Rewritten blocks:                     0d(                       No errors detected  G                  Example 3-9 shows an incremental save set in the file,oI                  incr2.bck being merged with a later incremental save setiH                  in the file, incr3.bck, and being written to a save setH                  in the file, incr4.bck. A full report is generated uponH                  completion of the merge operation. All errors, if thereG                  are any, are displayed to the terminal. The group sizetG                  is set to 0, and the block size is set to 32256 in the ,                  merged save set, incr4.bck.                        I                                                          Using SSMgr 3-51  r  l      
         MERGE           H               Example 3-10 MERGE Command with /FULL, /TERMINAL, /CHECKS,-                            and CRC Qualifiers   1               $ saveset merge/full/terminal=evento;               _Primary Save Set: incr2.bck/checks=(crc,xor)y=               _Secondary Save Set: incr3.bck/checks=(crc,xor) -               _Output Save Set: incr4.bck/crc !               _Output Save Set 2:o,               ERRORS terminal option enabled,               EVENTS terminal option enabledJ               Primary input save set DISK$BIRD:[HUMMING]INCR2.BCK;1 openedL               Secondary input save set DISK$BIRD:[HUMMING]INCR3.BCK;1 openedB               Output save set DISK$BIRD:[HUMMING]INCR4.BCK; opened  R               POLYCENTER(TM) Save Set Manager V1.3A  Time: 18-JUL-1996 16:30:30.88  )                   SAVESET function: MERGE H                   Primary input save set: DISK$BIRD:[HUMMING]INCR2.BCK;1#                     No journal fileeJ                   Secondary input save set: DISK$BIRD:[HUMMING]INCR3.BCK;1#                     No journal file @                   Output save set: DISK$BIRD:[HUMMING]INCR4.BCK;#                     No journal filec  0                   Final status of each save set:  I                                                  (continued on next page)                                          3-52 Using SSMgr           I                                                                     MERGEr      G               Example 3-10 (Cont.) MERGE Command with /FULL, /TERMINAL, >                                    /CHECKS, and CRC Qualifiers  B                     Save set name:  DISK$BIRD:[HUMMING]INCR2.BCK;1<                     Save set group size:                  10?                     Save set block size:                  32256a=                     Blocks in save set:                   146 =                     Nondirectory files in save set:       140 <                     Directory files in save set:          17;                     Alias nondirectory files in save set: 0 ;                     Alias directories in save set:        0s;                     Files removed by merge:               0o;                     Unrecoverable CRC errors:             0 ;                     Recoverable CRC errors:               0s;                     Unrecoverable checksum errors:        0o;                     Recoverable checksum errors:          0a;                     XOR errors:                           0o;                     Read errors:                          0 ;                     Write errors:                         0t;                     Record errors:                        0t;                     Unrecoverable missing blocks:         0 ;                     Recoverable missing blocks:           0t;                     Rewritten blocks:                     0 (                       No errors detected  I                                                  (continued on next page)r                                      I                                                          Using SSMgr 3-53     l      
         MERGEn      G               Example 3-10 (Cont.) MERGE Command with /FULL, /TERMINAL,u>                                    /CHECKS, and CRC Qualifiers  B                     Save set name:  DISK$BIRD:[HUMMING]INCR3.BCK;1<                     Save set group size:                  10?                     Save set block size:                  32256/=                     Blocks in save set:                   234 ;                     Nondirectory files in save set:       4 <                     Directory files in save set:          17;                     Alias nondirectory files in save set: 0a;                     Alias directories in save set:        0l;                     Files removed by merge:               0e;                     Unrecoverable CRC errors:             0.;                     Recoverable CRC errors:               0e;                     Unrecoverable checksum errors:        0e;                     Recoverable checksum errors:          0 ;                     XOR errors:                           0e;                     Read errors:                          0h;                     Write errors:                         0O;                     Record errors:                        0m;                     Unrecoverable missing blocks:         0o;                     Recoverable missing blocks:           0 ;                     Rewritten blocks:                     0 (                       No errors detected  I                                                  (continued on next page)e                                               3-54 Using SSMgr           I                                                                     MERGE       G               Example 3-10 (Cont.) MERGE Command with /FULL, /TERMINAL, >                                    /CHECKS, and CRC Qualifiers  A                     Save set name:  DISK$BIRD:[HUMMING]INCR4.BCK;t<                     Save set group size:                  10?                     Save set block size:                  32256e=                     Blocks in save set:                   359 =                     Nondirectory files in save set:       144t<                     Directory files in save set:          17;                     Alias nondirectory files in save set: 0 ;                     Alias directories in save set:        0 ;                     Files removed by merge:               0 ;                     Unrecoverable CRC errors:             0 ;                     Recoverable CRC errors:               0f;                     Unrecoverable checksum errors:        0 ;                     Recoverable checksum errors:          0 ;                     XOR errors:                           0r;                     Read errors:                          0f;                     Write errors:                         0 ;                     Record errors:                        0w;                     Unrecoverable missing blocks:         0e;                     Recoverable missing blocks:           0 ;                     Rewritten blocks:                     0 (                       No errors detected  E                  Example 3-10 shows the merge of two incremental savebB                  sets, incr2.bck and incr3.bck, into the save set,F                  incr4.bck. A full report is generated upon completionH                  of the merge operation. All events are displayed to theG                  terminal. CRC and XOR checking is performed on both ofnF                  the input save sets, incr2.bck, and incr3.bck. CRC is9                  added to the merged save set, incr4.bck.n                          I                                                          Using SSMgr 3-55     p      
         MERGE           I               Example 3-11 MERGE Command with Journaling on All Save Sets   9               $ saveset merge incr2.bck/journal=incr2.bjl >               _Secondary Save Set: incr3.bck/journal=incr3.bjl;               _Output Save Set: incr4.bck/journal=incr4.bjle!               _Output Save Set 2:e,               ERRORS terminal option enabled,               EVENTS terminal option enabledH               Primary input save set DISK$BEE:[BONNET]INCR2.BCK;1 openedJ               Secondary input save set DISK$BEE:[BONNET]INCR3.BCK;1 opened@               Output save set DISK$BEE:[BONNET]INCR4.BCK; opened  R               POLYCENTER(TM) Save Set Manager V1.3A  Time: 18-JUL-1996 16:40:04.67  )                   SAVESET function: MERGEuF                   Primary input save set: DISK$BEE:[BONNET]INCR2.BCK;1+                     Journal file: INCR2.BJL H                   Secondary input save set: DISK$BEE:[BONNET]INCR3.BCK;1+                     Journal file: INCR3.BJL->                   Output save set: DISK$BEE:[BONNET]INCR4.BCK;+                     Journal file: INCR4.BJL   0                   Final status of each save set:  @                     Save set name:  DISK$BEE:[BONNET]INCR2.BCK;1(                       No errors detected  @                     Save set name:  DISK$BEE:[BONNET]INCR3.BCK;1(                       No errors detected  ?                     Save set name:  DISK$BEE:[BONNET]INCR4.BCK;G(                       No errors detected  E                  Example 3-11 shows the merge of two incremental save1A                  set, incr2.bck and incr3.bck, into the save set,cH                  incr4.bck. A journal file is created for each save set.                       3-56 Using SSMgr l  l      I                                                                  VALIDATE       I         _________________________________________________________________:           VALIDATE  E               Validates the internal consistency and readability of aM               save set.            Format                  VALIDATE  input-ss           Parameters                 input-ss6               OpenVMS file name of the input save set.           Descriptionr  I               The SSMgr VALIDATE command reads an OpenVMS BACKUP save setCF               and verifies that at least one copy of each block of theG               specified save set is readable or can be regenerated withr@               OpenVMS BACKUP or by using the SSMgr COPY command.  I               The VALIDATE command differs from the OpenVMS BACKUP/VERIFY I               operation in that it does not compare the save set contents F               with the data on disk. It only verifies that the data inA               the save set is readable and internally consistent.s  C               Any data integrity problems found during the VALIDATEr?               operation, including unreadable data, CRC and XOR F               consistency errors, and regenerated blocks, are reported               to the user.           Qualifiers                 /ALL                /[NO]ALL (default)                 Command qualifiern  G               This qualifier specifies the behavior of Save Set Manager 4               when save set names contain wildcards.  B               If ALL is specified, then all save sets matching the:               wildcarded file specification are processed.  I                                                          Using SSMgr 3-57                     VALIDATE      B               If NOALL is specified, then only the first file nameE               found that matches the wildcarded file specification is1               processed.  C               The qualifier is valid only for the VALIDATE and COPYR               functions.  $               The default is /NOALL.                 /BRIEF (default)                 Command qualifier   E               This qualifier specifies that a minimum level of detail H               is to be echoed. The SAVESET function and save set name(s)E               are echoed; any error information is displayed; and the-H               result of the SAVESET operation is reported. See /FULL for4               a complete list of output information.  $               The default is /BRIEF.  '               /CHECKS=([NO]CRC,[NO]XOR)z  &               Input save set qualifier  F               This qualifier specifies the optional consistency checks;               that will be performed on the input save set.d  C               You must specify this qualifier immediately after theiH               file name of the save set on the command line, as shown inI               Example 3-12. Example 3-12 also shows that when you specify H               both CRC and XOR checks, you must list them in parentheses+               with a comma separating them.   D               If CRC checking is specified and the input save set isG               written with CRC, then the CRC is computed for each block H               in the input save set. The CRC is compared against the CRCG               stored in the block header. If the input save set was not ?               written with CRC, then this qualifier is ignored.   A               If XOR checking is specified and the input save set D               was written with XOR redundancy, then a running XOR isG               computed across each XOR group of blocks. The running XOR E               is compared to the XOR block. If the input save set was E               not written with XOR redundancy, then this qualifier is                ignored.           3-58 Using SSMgr           I                                                                  VALIDATE       B               Each of these options requires additional processingC               time and may impact the performance of SSMgr. Any CRC F               or XOR inconsistencies are written to the log file and aF               diagnostic message is returned to the calling program or-               user when processing completes.z  /               The default is /CHECKS=(CRC,XOR).c                   /FULL                  Command qualifiero  H               This qualifier specifies that more detail is to be echoed.B               In addition to information displayed with the /BRIEFD               qualifier, the following information for each save set               is displayed:                     Save set name$                  Save set group size$                  Save set block size-                  Number of blocks in save set 4                  Nondirectory user files in save set1                  Directory user files in save seth5                  Alias nondirectory files in save seto2                  Alias directory files in save set)                  Unrecoverable CRC errors '                  Recoverable CRC errors ,                  Recoverable checksum errors.                  Unrecoverable checksum errors                  XOR errors                   Read errors                  Write errorsl                  Record errors-                  Unrecoverable missing blocksM+                  Recoverable missing blocks !                  Rewritten blocks   $               The default is /BRIEF.  *               /JOURNAL[=journal-file-name]        I                                                          Using SSMgr 3-59                     VALIDATE                      Save set qualifier  B               This qualifier specifies whether SSMgr will create aC               journal file for the save set. The journal file is anLD               OpenVMS BACKUP journal file with an OpenVMS file name.I               If no journal file name is specified, the journal file will E               be written to <saveset_name>.BJL in the current default                directory.  F               If a journal file with the same name already exists, theI               new journal file is appended. If it does not already exist,T,               a new journal file is created.  E               Journal files created by SSMgr will not list the labels E               of follow-on volumes in multivolume tape sets. Also, if D               COPY/IDENTICAL is used to copy a multivolume tape to aH               single volume tape, the journal file will still list it as%               a multivolume tape set.   I               These differences from BACKUP created journal files are due I               to a limitation in VMS that does not allow a non-privilegedsG               process to obtain the volume labels of a multivolume tape                set.  H               You must specify this qualifier immediately after the save:               set file name specifier on the command line.  @               This qualifier is valid for all save set file nameA               specifiers, input or output, on all SSMgr commands.m  (               The default is /NOJOURNAL.  0               /LOG_FILE[=logfile-name] (default)               /NOLOG_FILEi                 Command qualifieri  G               This qualifier causes SSMgr to write events to a log fileiE               specified by logfile-name. The logfile-name is an ASCIIlF               file with an OpenVMS file name. By default, a logfile isE               created for every execution of an SSMgr command. If notiH               specified, the default log file name is SAVESET.LOG in theF               current default directory. You can suppress the creationH               of a default log file by using /NOLOG_FILE or by includingI               /LOG_FILE=NL: on the command line. The following events are .               written to the SAVESET.LOG file:           3-60 Using SSMgr a  v      I                                                                  VALIDATE       )               o  Each invocation of SSMgr   C               o  All output returned to the user or calling programa  D               o  Any errors or warnings encountered while processing                   input save sets  "               o  Operator requests  G               Wildcards may not be used in the specification of logfileD               names.  3               The default is /LOG_FILE=SAVESET.LOG.:                                                                I                                                          Using SSMgr 3-61E u  i               VALIDATE                     /REWIND !               /NOREWIND (default)   &               Input save set qualifier  E               For magnetic tape volumes only, REWIND directs SSMgr to E               rewind the magnetic tape to the beginning-of-tape (BOT)$E               marker before reading the volume. This qualifier allows I               SSMgr to find save sets that are located before the current                tape position.  C               You must specify this qualifier immediately after therG               applicable file name of the save set on the command line, '               as shown in Example 3-12.m  G               The default for this qualifier is /NOREWIND, which causes A               SSMgr to start processing the tape from the currentaE               position. Any input save set that is located before thes=               current position of the tape will not be found.t  9               /TERMINAL=([NO]ERRORS, [NO]EVENTS, [NO]LOG)c                 Command qualifier4  D               This qualifier specifies what class(es) of informationI               should be displayed on the user's terminal during execution %               of the SAVESET command.   I               If ERRORS is specified, then all error conditions occurring G               during execution are displayed as they occur, in additioneI               to being included in the final report at the end of commandr,               execution and in the log file.  H               If EVENTS is specified, then all nonerror event conditionsB               occurring during execution (e.g., tape switches) are&               displayed as they occur.  D               If LOG is specified, then the names of all output userB               files (for COPY and MERGE) are displayed as they areH               written to the output save set. For VALIDATE, the names ofG               all input user files are displayed as they are processed.t  =               The default is /TERMINAL=(ERRORS,EVENTS,NOLOG).              3-62 Using SSMgr e  d      I                                                                  VALIDATE                  Examples    +               Example 3-12 VALIDATE Command   H               $ saveset validate mkb200:rock.bck/checks=(crc,xor)/rewind,               ERRORS terminal option enabled,               EVENTS terminal option enabled6               Rewinding MKB200: to beginning of volume(               Rewind of MKB200: complete.               Opening file MKB200:[]ROCK.BCK;1?               Primary input save set MKB200:[]ROCK.BCK;1 openedz  R               POLYCENTER(TM) Save Set Manager V1.3A  Time: 18-JUL-1996 19:17:42.17  ,                   SAVESET function: VALIDATE=                   Primary input save set: MKB200:[]ROCK.BCK;1 #                     No journal file 0                   Final status of each save set:  7                     Save set name:  MKB200:[]ROCK.BCK;1 (                       No errors detected  E                  In Example 3-12, a save set named ROCK.BCK on MKB200.G                  is validated with CRC checking and XORing. The tape is H                  rewound before the validation begins. A brief report is:                  generated upon completion of the command.  8               Example 3-13 VALIDATE with /Full Qualifier  Q               $ saveset validate mkb200:rock.bck/full/rewind/checks=(nocrc,noxor) ,               ERRORS terminal option enabled,               EVENTS terminal option enabled6               Rewinding MKB200: to beginning of volume(               Rewind of MKB200: complete.               Opening file MKB200:[]ROCK.BCK;1?               Primary input save set MKB200:[]ROCK.BCK;1 openede  R               POLYCENTER(TM) Save Set Manager V1.3A  Time: 18-JUL-1996 19:21:33.48  I                                                  (continued on next page)       I                                                          Using SSMgr 3-63                     VALIDATE      @               Example 3-13 (Cont.) VALIDATE with /Full Qualifier  ,                   SAVESET function: VALIDATE=                   Primary input save set: MKB200:[]ROCK.BCK;1 #                     No journal file 0                   Final status of each save set:  7                     Save set name:  MKB200:[]ROCK.BCK;1 <                     Save set group size:                  10?                     Save set block size:                  32256 =                     Blocks in save set:                   146r=                     Nondirectory files in save set:       140r<                     Directory files in save set:          17;                     Alias nondirectory files in save set: 0 ;                     Alias directories in save set:        0R;                     Unrecoverable CRC errors:             0 ;                     Recoverable CRC errors:               0h;                     Unrecoverable checksum errors:        0 ;                     Recoverable checksum errors:          0 ;                     XOR errors:                           0 ;                     Read errors:                          0:;                     Write errors:                         0 ;                     Record errors:                        0i;                     Unrecoverable missing blocks:         0c;                     Recoverable missing blocks:           0e;                     Rewritten blocks:                     0o(                       No errors detected  D                  Example 3-13 shows usage of the VALIDATE command toD                  validate ROCK.BCK with full details provided in theE                  report, without the optional CRC and XOR consistencyiD                  checking, without a journal file, without rewindingF                  the tape, and with ERRORS and EVENTS terminal classes                  enabled.,                               3-64 Using SSMgr           I                                                                  VALIDATE           >               Example 3-14 VALIDATE All Save Sets in Directory  :               $ saveset validate/all playoffs.*/checks=crc,               ERRORS terminal option enabled,               EVENTS terminal option enabledN               Primary input save set DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.96;1                opened   R               POLYCENTER(TM) Save Set Manager V1.3A  Time: 18-JUL-1996 19:31:19.04  ,                   SAVESET function: VALIDATES                   Primary input save set: DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.96;1 #                     No journal file   0                   Final status of each save set:M                     Save set name:  DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.96;1 (                       No errors detected  N               Primary input save set DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.97;1                opened.  R               POLYCENTER(TM) Save Set Manager V1.3A  Time: 18-JUL-1996 19:31:22.25  ,                   SAVESET function: VALIDATES                   Primary input save set: DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.97;1i#                     No journal filei  0                   Final status of each save set:  M                     Save set name:  DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.97;1e(                       No errors detected  N               Primary input save set DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.98;1                openedn  R               POLYCENTER(TM) Save Set Manager V1.3A  Time: 18-JUL-1996 19:31:23.24  ,                   SAVESET function: VALIDATES                   Primary input save set: DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.98;1 #                     No journal file   0                   Final status of each save set:  I                                                  (continued on next page)   I                                                          Using SSMgr 3-65_ _  _               VALIDATE      F               Example 3-14 (Cont.) VALIDATE All Save Sets in Directory  M                     Save set name:  DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.98;1 (                       No errors detected  N               Primary input save set DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.99;1                openedr  R               POLYCENTER(TM) Save Set Manager V1.3A  Time: 18-JUL-1996 19:31:25.02  ,                   SAVESET function: VALIDATES                   Primary input save set: DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.99;1w#                     No journal file   0                   Final status of each save set:  M                     Save set name:  DISK$AVALANCHE:[STANLEY_CUP]PLAYOFFS.99;1o(                       No errors detected  .                 Summary of VALIDATE operations  <                   Total operations attempted:              4<                   Operations completing successfully:      4  E                  Example 3-14 shows the validation of all of the saveiG                  sets in the DISK$AVALANCE:[STANLEY_CUP] directory. CRC D                  checking is performed on each save set, and a briefE                  report is generated upon the completion of each save)I                  set, followed by a summary report of all the operations.i                                         3-66 Using SSMgr           I                                                                  VALIDATE       :               Example 3-15 VALIDATE with Journal Qualifier  K               $ saveset validate mkb500:savesetua013.a/journal=kit.contents3,               ERRORS terminal option enabled,               EVENTS terminal option enabled4               Opening file MKB500:[]SAVESETUA013.A;1E               Primary input save set MKB500:[]SAVESETUA013.A;1 opened   R               POLYCENTER(TM) Save Set Manager V1.3A  Time: 18-JUL-1996 19:43:31.09  ,                   SAVESET function: VALIDATEC                   Primary input save set: MKB500:[]SAVESETUA013.A;1 .                     Journal file: KIT.CONTENTS  0                   Final status of each save set:=                     Save set name:  MKB500:[]SAVESETUA013.A;1c(                       No errors detected  0               $ backup/journal=kit.contents/list'               Listing of BACKUP journal I               Journal file DISK$PEAK:[PIKES]KIT.CONTENTS;1 on 18-JUL-1996/                19:44:23.45  H               Save set SAVESETUA013.A created on 18-JUL-1996 19:40:01.662               Volume number 1, volume label MERGE09                   [SOFTWARE.SAVESETUA013]KITINSTAL.COM;29u;                   [SOFTWARE.SAVESETUA013]SAVESET$IVP.COM;14 6                   [SOFTWARE.SAVESETUA013]SAVESET.CLD;46                   [SOFTWARE.SAVESETUA013]SAVESET.HLP;4E                   [SOFTWARE.SAVESETUA013]SAVESETUA013.RELEASE_NOTES;3 H                   [SOFTWARE.SAVESETUA013]SAVESETUA013_RELEASE_NOTES.PS;5B                   [SOFTWARE.SAVESETUA013]SAVESET_COVER_LETTER.PS;6A                   [SOFTWARE.SAVESETUA013]SAVESET_USER_GUIDE.PS;17CA                   [SOFTWARE.SAVESETUA013]SAVESET_USER_GUIDE.TXT;8i  #               End of BACKUP journaln  C                  Example 3-15 shows the validation of the save set, F                  SAVESETUA013.A, on the tape device, MKB500, that alsoH                  creates a journal file named, KIT.CONTENTS, showing theH                  files in the save set. Note that to see the contents ofD                  the resultant journal file, BACKUP must be invoked.      I                                                          Using SSMgr 3-67                     VALIDATE      A               Example 3-16 VALIDATE with Terminal Classes EnabledU  ?               $ saveset validate/terminal=(errors,events,log) - *               mkb500:savesetua013.a/rewind)               LOG terminal option enabledd,               ERRORS terminal option enabled,               EVENTS terminal option enabled6               Rewinding MKB500: to beginning of volume(               Rewind of MKB500: complete4               Opening file MKB500:[]SAVESETUA013.A;1E               Primary input save set MKB500:[]SAVESETUA013.A;1 openedHK               Processing user file: [SOFTWARE.SAVESETUA013]KITINSTAL.COM;29oM               Processing user file: [SOFTWARE.SAVESETUA013]SAVESET$IVP.COM;14 H               Processing user file: [SOFTWARE.SAVESETUA013]SAVESET.CLD;4H               Processing user file: [SOFTWARE.SAVESETUA013]SAVESET.HLP;4;               Processing user file: [SOFTWARE.SAVESETUA013] +                SAVESETUA013.RELEASE_NOTES;3S;               Processing user file: [SOFTWARE.SAVESETUA013] .                SAVESETUA013_RELEASE_NOTES.PS;5;               Processing user file: [SOFTWARE.SAVESETUA013]h(                SAVESET_COVER_LETTER.PS;6;               Processing user file: [SOFTWARE.SAVESETUA013]e'                SAVESET_USER_GUIDE.PS;17e;               Processing user file: [SOFTWARE.SAVESETUA013] '                SAVESET_USER_GUIDE.TXT;8   R               POLYCENTER(TM) Save Set Manager V1.3A  Time: 18-JUL-1996 19:51:55.14  ,                   SAVESET function: VALIDATEC                   Primary input save set: MKB500:[]SAVESETUA013.A;1b#                     No journal filem  0                   Final status of each save set:  =                     Save set name:  MKB500:[]SAVESETUA013.A;1=(                       No errors detected  C                  Example 3-16 shows the validation of the save set, E                  SAVESETUA013.A, on the tape device, MKB500, with all F                  classes of information: errors, events, and log beingF                  displayed to the terminal. The tape is rewound before1                  the validation operation begins.m               3-68 Using SSMgr e  m                    I                                                                         4uI         _________________________________________________________________   I                                                Interpreting SSMgr Reportse    G               This chapter describes the completion and interim reportsa!               generated by SSMgr.   7         4.1 Monitoring the Progress of SSMgr Operationsf  C               While SSMgr is running, you can use Ctrl/T to monitorOF               the progress of the SSMgr operation. Each time you enterB               Ctrl/T, SSMgr displays a progress report as shown in               Example 4-1.  /               Example 4-1 Ctrl/T Report Examplee  Z               1 JOE::SMITH 15:44:09 SAVESET$S CPU=00:19:00.12 PF=392532 IO=292279 MEM=1131=               2  Current input file:    [SMITH]WS_LOGIN.COM;1mJ               3  Input save set blocks:         5      Input files:     28J               4  Output save set blocks:        4      Output files:    24  F               1  The first line is the standard OpenVMS Ctrl/T output.  E               2  Name of last user file read from the input save set.o  I               3  Total number of save set blocks and user files that haveL;                  been read from the primary input save set.   G               4  Total number of save set blocks and user files writtenoG                  to the output save set. This is not displayed during ae$                  VALIDATE operation.  E               Entering Ctrl/T before SSMgr has read the first file of E               the input save set will cause "None" to be displayed as F               the current input file. On MERGE operations involving anH               image save set and an incremental save set, SSMgr displaysG               "None" in this field throughout the initial pass over the #               incremental save set.T    I                                            Interpreting SSMgr Reports 4-1     0      "         Interpreting SSMgr Reports          4.2 Completion Reporting              4.2 Completion Reporting  G               When an SSMgr command terminates, the final status and/ornE               a summary report is written to standard output. In mostrD               cases, this information also is written to a log file.  *         4.2.1 Normal Successful Completion  F               Every SSMgr operation that completes successfully issuesF               a completion report that details any errors or anomaliesH               found in the save sets. Refer to Example 4-2. If no errorsA               were detected, the report has the following format:u  B         4.2.2 Successful Completion with Save Set Condition Report  G               If SSMgr found errors or anomalies in the input save set, G               but was still able to successfully complete the requested F               operation, then a save set condition report is produced.B               This report breaks out the number and type of errorsD               detected, as well as a list of user files affected. AnH               error can be either recoverable or unrecoverable. An errorD               is recoverable if the save set was created with an XORF               group size greater than zero, and there was no more thanF               one error in an XOR group. The following types of errorsC               and anomalies are broken out for each input save set:r  6               o  recoverable/unrecoverable CRC errors.  H               o  recoverable/unrecoverable block header checksum errors.  :               o  recoverable/unrecoverable missing blocks.  C               o  XOR mismatch errors. The XOR block at the end of aiH                  group does not contain the XOR of all the blocks in theI                  group. Note that XOR mismatch errors are only consideredcI                  recoverable if CRC protection is present in the save set F                  and all data blocks in the XOR group had correct CRC.                 o  Read errors.i  H               o  Record header errors. A record header within a save setH                  block contains an invalid record type or invalid record                  length.    &         4-2 Interpreting SSMgr Reports .  a      I                                                Interpreting SSMgr ReportsiI                                                  4.2 Completion ReportingP    =               Example 4-2 Normal Successful Completion Reporte  M               1  $ saveset copy mkb200:rock.bck stones.sav/identical/overridea/               2  ERRORS terminal option enabled 0                   EVENTS terminal option enabled1               3  Opening file MKB200:[]ROCK.BCK;1 C                   Primary input save set MKB200:[]ROCK.BCK;1 opened F                   Output save set DISK$MUSIC:[WAVES]STONES.SAV; opened  U               4  POLYCENTER(TM) Save Set Manager V1.3A  Time: 18-JUL-1996 20:04:29.93   )               5    SAVESET function: COPY ?                     Primary input save set: MKB200:[]ROCK.BCK;12%                       No journal file B                     Output save set: DISK$MUSIC:[WAVES]STONES.SAV;%                       No journal filea  1               6    Final status of each save set:O  7                     Save set name:  MKB200:[]ROCK.BCK;17%               7    No errors detectedc  A                     Save set name:  DISK$MUSIC:[WAVES]STONES.SAV;C(                       No errors detected  0               1  Command as entered by the user.  5               2  Selected terminal options displayed.C  C               3  Information about progress of command and save setx                  names.m                 4  Report header.   A               5  Echo of the SSMgr command issued, separated into E                  function, input save set, output save set and status !                  of journal file.n  H               6  Status of each save set processed, including the statusE                  of multiple output save sets, if any were requested.=  >               7  No errors or anomalies, either recoverable or.                  unrecoverable, were detected.  D               o  Rewritten blocks. This is not an error, but a countD                  of the number of blocks which were rewritten due toC                  conditions such as bad spots on the media. If this I                  number is large, you may be able to significantly reduce.  I                                            Interpreting SSMgr Reports 4-3e           "         Interpreting SSMgr Reports          4.2 Completion Reporting    G                  the size of your save set by using SSMgr to copy it toL                  better media.  H               If recoverable errors were detected in the input save set,E               SSMgr also lists all files in the groups containing the G               errors. These files are still readable, but are no longereD               protected by XOR redundancy. If a second error were toH               develop within the same XOR group, user file data could be               lost.   C               If your save set contains recoverable errors, Digital @               recommends that you use the SSMgr COPY function toB               regenerate the XOR redundancy protection. If you areE               dealing with save sets on media that is very old or haseF               been improperly stored, Digital recommends that you copyA               the save set with the SAVESET COPY command with the H               /IDENTICAL and /OVERRIDE qualifers to another medium, thenG               SAVESET COPY the save set to a final medium with the /CRC I               and /GROUP qualifiers. This procedure accomplishes the copyeF               operation without the risk of running a second pass over                the suspect media.                                                &         4-4 Interpreting SSMgr Reports    s      I                                                Interpreting SSMgr Reports I                                                  4.2 Completion Reporting     3               Example 4-3 Save Set Condition Reporte  9               $ saveset merge zap4.sav zapcrc.sav foo.sav .                 ERRORS terminal option enabled.                 EVENTS terminal option enabled8                 Opening file DKB200:[ENGINEER]ZAP4.SAV;2I                 Primary input save set DKB200:[ENGINEER]ZAP4.SAV;2 openedt<                 Opening file DISK$100:[ENGINEER]ZAPCRC.SAV;1O                 Secondary input save set DISK$100:[ENGINEER]ZAPCRC.SAV;1 opened 8                 Opening file DISK$100:[ENGINEER]FOO.SAV;B                 Output save set DISK$100:[ENGINEER]FOO.SAV; openedN                 Resetting to beginning of file DISK$100:[ENGINEER]ZAPCRC.SAV;1X                 File DISK$100:[ENGINEER]ZAPCRC.SAV;1 has been reset to beginning of fileS                 POLYCENTER(TM) Save Set Manager V1.2  Time: 28-NOV-1995 20:38:36.57   )                   SAVESET function: MERGE 2                   Primary input save set: ZAP4.SAV6                   Secondary input save set: ZAPCRC.SAV*                   Output save set: FOO.SAV  G               1Save set name:  DISK$100:[ENGINEER.SSM.SRC.TMP]ZAP4.SAV;   8               2  Recoverable checksum errors:          1  /               3User files affected by error(s):LF                       [ENGINEER.SSM.VAXV60.OBJ]CONDITION_HANDLER.OBJ;3F                       [ENGINEER.SSM.VAXV60.OBJ]CONDITION_HANDLER.OBJ;2F                       [ENGINEER.SSM.VAXV60.OBJ]CONDITION_HANDLER.OBJ;1:                       [ENGINEER.SSM.VAXV60.OBJ]COPY.OBJ;25  I               4Save set name:  DISK$100:[ENGINEER.SSM.SRC.TMP]ZAPCRC.SAV;[  8               5  Recoverable CRC errors:               1  I                                                  (continued on next page)                     I                                            Interpreting SSMgr Reports 4-5e t         "         Interpreting SSMgr Reports          4.2 Completion Reporting    ;               Example 4-3 (Cont.) Save Set Condition Report   /               6User files affected by error(s): ,                       [ENGINEER]BATCH.COM;26/                       [ENGINEER]BL_SETUP.COM;15A/                       [ENGINEER]BL_SETUP.COM;14 /                       [ENGINEER]BL_SETUP.COM;13 )                       [ENGINEER]BYE.COM;2 -                       [ENGINEER]EVEPLUS.COM;6n*                       [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;4V+                       [ENGINEER]MEDIA.COM;1 ,                       [ENGINEER]NEWEVE.COM;50                       [ENGINEER]NOTES$EDIT.COM;2+                       [ENGINEER]NOTUP.COM;2I0                       [ENGINEER]PAGE_COUNT.COM;9/                       [ENGINEER]PDC_ORDER.COM;3 6                       [ENGINEER]RAIDEV_GKSTARTUP.COM;10                       [ENGINEER]READ_DEMO.COM;13,                       [ENGINEER]SETDEF.COM;3+                       [ENGINEER]STOCK.COM;2e*                       [ENGINEER]TEMP.COM;2*                       [ENGINEER]UUCP.COM;1/                       [ENGINEER]WAS_LOGIN.COM;2 .                       [ENGINEER]WS_LOGIN.COM;1  ?               1  Name of first input save set containing errorsv                  /anomalies.  ;               2  Summary of errors found in first save set.   G               3  List of user files in first input save set that are nor4                  longer protected by XOR redundancy.  @               4  Name of second input save set containing errors                  /anomalies.  I                                                  (continued on next page)   &         4-6 Interpreting SSMgr Reports           I                                                Interpreting SSMgr ReportseI                                                  4.2 Completion ReportingO    ;               Example 4-3 (Cont.) Save Set Condition Reporte  B               5  Summary of errors found in second input save set.  H               6  List of user files in second input save set that are no4                  longer protected by XOR redundancy.           4.2.3 Error Reporting   E               In the case of an SSMgr MERGE or COPY operation (excepttC               COPY/IDENTICAL/OVERRIDE), SSMgr cannot continue afterOE               detecting an unrecoverable error. If this occurs, SSMgr G               terminates with an error message as shown in Example 4-4.   &               Example 4-4 Error Report  /               $ saveset copy zap2.bck zcopy.bck ,               ERRORS terminal option enabled,               EVENTS terminal option enabledJ               Primary input save set DISK$USER:[SOFTWARE]ZAP2.BCK;1 openedC               Output save set DISK$USER:[SOFTWARE]ZCOPY.BCK; opened S               CRC error: block number 50 in save set DISK$USER:[SOFTWARE]ZAP2.BCK;1 Q               Block recovered from XOR in save set DISK$USER:[SOFTWARE]ZAP2.BCK;1E  T                 POLYCENTER(TM) Save Set Manager V1.3A  Time: 18-JUL-1996 20:16:28.18  (                   SAVESET function: COPYH                   Primary input save set: DISK$USER:[SOFTWARE]ZAP2.BCK;1#                     No journal fileSA                   Output save set: DISK$USER:[SOFTWARE]ZCOPY.BCK;S#                     No journal fileD  0                   Final status of each save set:  B                     Save set name:  DISK$USER:[SOFTWARE]ZAP2.BCK;1;                     Recoverable CRC errors:               1s  4                     User files affected by error(s):E                       [SOFTWARE.SAVESETUA013]SAVESET_USER_GUIDE.PS;17T  B                     Save set name:  DISK$USER:[SOFTWARE]ZCOPY.BCK;(                       No errors detected      I                                            Interpreting SSMgr Reports 4-7            "         Interpreting SSMgr Reports          4.2 Completion Reporting             4.2.4 Log File  H               In addition to standard output, SSMgr messages and reportsG               also are sent to a log file as shown in Example 4-5. Each1F               log file begins with a diagnostic message containing theH               time the SSMgr command was issued, followed by a report orF               error message identical to that sent to standard output.F               The default log file name is SAVESET.LOG, written to theF               user's default directory. See the /LOGFILE= qualifier toH               change the log file name or supress creating the log file.  E               A new log file is created for each invocation of SSMgr.S                                                                  &         4-8 Interpreting SSMgr Reports r  s      I                                                Interpreting SSMgr ReportseI                                                  4.2 Completion Reporting;    "               Example 4-5 Log File  @               $ saveset copy ssm.bck copy.sav/identical/override                 Log file:i  ,               ERRORS terminal option enabled,               EVENTS terminal option enabledM               Primary input save set DISK$ENGINEER:[SOFTWARE]SSM.BCK;1 openedUF               Output save set DISK$ENGINEER:[SOFTWARE]COPY.SAV; openedV               CRC error: block number 15 in save set DISK$ENGINEER:[SOFTWARE]SSM.BCK;1Q               Recovery unsuccessful in save set DISK$ENGINEER:[SOFTWARE]SSM.BCK;1IY               %SAVESET-I-BADCRC, Data CRC error in file DISK$ENGINEER:[SOFTWARE]SSM.BCK;1 Q               XOR error at block 26 in save set DISK$ENGINEER:[SOFTWARE]SSM.BCK;1 V               CRC error: block number 45 in save set DISK$ENGINEER:[SOFTWARE]SSM.BCK;1Q               Recovery unsuccessful in save set DISK$ENGINEER:[SOFTWARE]SSM.BCK;1 Y               %SAVESET-I-BADCRC, Data CRC error in file DISK$ENGINEER:[SOFTWARE]SSM.BCK;1sQ               XOR error at block 52 in save set DISK$ENGINEER:[SOFTWARE]SSM.BCK;1 V               CRC error: block number 68 in save set DISK$ENGINEER:[SOFTWARE]SSM.BCK;1Q               Recovery unsuccessful in save set DISK$ENGINEER:[SOFTWARE]SSM.BCK;1 Y               %SAVESET-I-BADCRC, Data CRC error in file DISK$ENGINEER:[SOFTWARE]SSM.BCK;1_Q               XOR error at block 78 in save set DISK$ENGINEER:[SOFTWARE]SSM.BCK;1   T                 POLYCENTER(TM) Save Set Manager V1.3A  Time: 18-JUL-1996 20:22:12.74  (                   SAVESET function: COPYK                   Primary input save set: DISK$ENGINEER:[SOFTWARE]SSM.BCK;1 #                     No journal fileoD                   Output save set: DISK$ENGINEER:[SOFTWARE]COPY.SAV;#                     No journal file   0                   Final status of each save set:  E                     Save set name:  DISK$ENGINEER:[SOFTWARE]SSM.BCK;1R;                     Unrecoverable CRC errors:             3$;                     XOR errors:                           3   E                     Save set name:  DISK$ENGINEER:[SOFTWARE]COPY.SAV;s(                       No errors detected            I                                            Interpreting SSMgr Reports 4-9                          I                                                                         5 I         _________________________________________________________________f  I                                                            SSMgr Messagesh    E               This section contains descriptions and user actions forc'               messages issued by SSMgr.     .         5.1 SSMgr INFORMATIONAL Level Messages  D          NOLOGFILE, Unable to create log file. Continuing operation.  F             Explanation: Attempt to create log file failed. The reasonE             for the failure follows this message. Operation continues              without logfile.  C             Action: Correct problem indicated by secondary message.t  H          NOLOGFILEWRITE, Unable to write log file. Continuing operation.  E             Explanation: Attempt to write to the log file failed. The B             reason for the failure follows this message. Operation&             continues without logfile.  C             Action: Correct problem indicated by secondary message.g  &         5.2 SSMgr ERROR Level Messages  B          BADCHECKSUM, Block header checksum error in file filename  C             Explanation: An unrecoverable error was found in a savetD             set block header. The data contained in the block is not             reliable.   A             Action: Use OpenVMS BACKUP to restore the recoverable $             portion of the save set.  0          BADCRC, Data CRC error in file filename  G             Explanation: An unrecoverable error was found in a save set,G             block CRC. The data contained in the block is not reliable.t  A             Action: Use OpenVMS BACKUP to restore the recoverabler$             portion of the save set.  I                                                        SSMgr Messages 5-1                     SSMgr Messages&         5.2 SSMgr ERROR Level Messages    +          BADXOR, XOR error in file filenamee  F             Explanation: The XOR block of a save set group in save setF             filename does not contain the valid XOR of the data blocksH             in that group and CRC protection is not present. The data in+             the entire group is unreliable.e  A             Action: Use OpenVMS BACKUP to restore the recoverableu$             portion of the save set.  4          INVSAVESET, filename is not a valid saveset  F             Explanation: Save set filename is not a valid OpenVMS save             set.               Action: None.a  C          MISSINGBLK, Missing block could not be regenerated in filei             filename  D             Explanation: There was an unrecoverable missing block inD             save set filename and there was insufficient metadata to,             reproduce the data in the block.  @             Action: None. The data in the missing block is lost.  ,         5.3 SSMgr FATAL Level Error Messages  A          BUG, A software bug was detected at line line, file file   8             Explanation: SSMgr detected an internal bug.  G             Action: Please submit an SPR and copies of the log file andlF             the input save sets. If this bug prevents you from copyingD             the input save sets, submit the output of BACKUP/LIST on$             those save sets instead.  3          DEVACCESS, Cannot access device devicename   @             Explanation: Attempts to access a save set on device#             devicename have failed.   G             Action: Verify that the path name given by the command lineaE             is correct, that the device is mounted, and that you haveV,             privileges to access the device.  9          DUPJNLFIL, Duplicate journal file name: filename   F             Explanation: For any single SAVESET command with more thanG             one journal file being created, each journal file name mustM             be unique.  H             Action: Verify that the save set file names used are unique.           5-2 SSMgr Messages n         I                                                            SSMgr Messages I                                      5.3 SSMgr FATAL Level Error Messages     4          FAILURE, SAVESET operation was unsuccessful  B             Explanation: The SAVESET operation could not complete.C             Additional messages follow indicating the nature of the              failure.  A             Action: Base user action on the immediately following              messages.d  1          FILECLOSE, could not close file filename   @             Explanation: SSMgr could not close the save set withD             filename. The reason for the failure appears immediately             after this message.   8             Action: Dependent on the reason for failure.  /          FILEOPEN, could not open file filename   E             Explanation: SSMgr could not open the file with filename. E             The reason for the failure appears immediately after this              message.  8             Action: Dependent on the reason for failure.  .          FILEREAD, error reading file filename  A             Explanation: SSMgr encountered and error reading filenD             filename. The reason for the failure appears immediately             after this message.e  8             Action: Dependent on the reason for failure.  A          FILERESET, could not reset to beginning of file filename   B             Explanation: SSMgr could not reset to the beginning ofA             the file filename. The reason for the failure appearsg+             immediately after this message.i  8             Action: Dependent on the reason for failure.  /          FILEWRITE, error writing file filename.  @             Explanation: SSMgr encountered an error writing fileD             filename. The reason for the failure appears immediately             after this message.   8             Action: Dependent on the reason for failure.  I                                                        SSMgr Messages 5-3e o  i               SSMgr Messages,         5.3 SSMgr FATAL Level Error Messages    9          IDENTCOPYFAIL, Identical copy of filename faileda  E             Explanation: The user specified /IDENTICAL on the SAVESET G             COPY command line, and the operation failed. The reason for ?             the failure appears immediately after this message.   8             Action: Dependent on the reason for failure.  D          INSUFSPACE, Insufficient space for filename to be allocated  B             Explanation: There is insufficient space on the targetE             output disk device to allow allocation of a file the sizet&             required by the operation.  F             Action: Specify a device that has sufficient space to hold             the output file.  C          INVADDRESS, Invalid address in save set record in save set              filename  E             Explanation: There is a nonzero value in address field of G             record header in non-LBN/VBN record. The associated data is              therefore suspect.  H             Action: Use OpenVMS BACKUP to restore the save set and check              for data corruption.  @          INVBLKSIZE, Invalid block size. Valid range: 2048-65535  D             Explanation: Save set blocks may be no smaller than 20481             bytes and no larger than 65535 bytes.   E             Action: Reenter the SAVESET command and specify a /BLOCK_t;             SIZE value in the range of 2048 to 65535 bytes.1  G          INVDEVCLASS, Could not open devicename. Device must be disk oro             tape  F             Explanation: SSMgr operates on disk and tape devices only.E             The device specified by devicename was not a disk or tapeb             device.$               Action: None.   C          INVFILATTR, Invalid file attribute in save set file recordg  F             Explanation: An invalid file attribute is stored in a saveF             set file record, indicating a corrupt or otherwise invalid             save set record.  C             Action: Re-enter the SAVESET command with a /GROUP_SIZEC'             value in the range 0 - 100.:           5-4 SSMgr Messages e  a      I                                                            SSMgr MessageseI                                      5.3 SSMgr FATAL Level Error MessagesL    ;          INVGRPSIZE, Invalid group size. Valid range: 0-100R  G             Explanation: Save set XOR groups may be no larger than 100.JE             A value of zero indicates no XOR should be written to theJ             save set.   G             Action: Reenter the SAVESET command with a GROUP_SIZE valueS"             in the range 0 to 100.  F          INVRECSIZE, Invalid save set record size in save set filename  E             Explanation: A save set record contains invalid metadata.   H             Action: Use OpenVMS BACKUP to restore the save set and check              for data corruption.  F          INVRECTYPE, Invalid save set record type in save set filename  E             Explanation: A save set record contains invalid metadata.   H             Action: Use OpenVMS BACKUP to restore the save set and check              for data corruption.  B          INVOUTWC, Invalid output save set wild card specification  A             Explanation: The only legal wildcarding of the 'name' >             or 'type' portions of an output save set file nameB             specification is a single '*'. Use of the '%' wildcardA             or combining the '*' with any other characters in theN%             specification is illegal.G  F             Action: Re-enter the SAVESET command with a legal wildcard>             specification or with a nonwildcard specification.  8          JNLOPNERR, Error opening journal file: filename  G             Explanation: The journal file specified could not be openedE             successfully.   G             Action: Ensure that the file name is correct, that you have]H             write access to the device, and that the device is not full.  ;          JNLWRTERR, Error writing to Journal file: filenameE  H             Explanation: The journal file specified could not be written             to successfully.  H             Action: Ensure that you have write access to the device, and(             that the device is not full.  ,          MEMALLOC, Memory allocation failure  G             Explanation: SSMgr was unable to allocate necessary memory.L  C             Action: Ensure sufficient resources for SSMgr operaton.e  I                                                        SSMgr Messages 5-5u i  i               SSMgr Messages,         5.3 SSMgr FATAL Level Error Messages    A          NODEVNAM, No device name in save set specifier specifier   E             Explanation: No device name was specified in a context in 6             which an explicit device name is required.  H             Action: Specify the device name with the save set specifier.  E          NOMERGEPHYS, AZ, is a physical save set, invalid as input tot             MERGEo  @             Explanation: MERGE operations cannot be performed on&             physical backup save sets.               Action: None.n  A          NOMULTITAPE, COPY/IDENTICAL output save set may not spans             multiple tapes  A             Explanation: End of tape (EOT) on the output tape was G             encountered during a SAVESET COPY/IDENTICAL operation. This E             operation requires that the copied save set does not spanp             multiple tapes.C  D             Action: Use an output tape that has sufficient space forD             the save set or use the SAVESET COPY command without the!             /IDENTICAL qualifier.a  5          NONLOCALACC, device must be accessed locally   A             Explanation: The save set must be accessed on a localt             device.d  B             Action: Use only save sets that do not require network             access.S  ,          REWINDFAIL, Could not rewind device  H             Explanation: Attempts to rewind the specified device failed.  A             Action: This error message is always accompanied by a D             secondary system message. Correct the problem identified&             by that secondary message.  :          SECNOTINCR, Secondary save set not an incremental  C             Explanation: If the primary input save set in a SAVESETaD             MERGE operation is an image save set, then the secondary?             input save set must be an incremental save set. SeeOC             Table 3-1 for a list of valid save set combinations fori             MERGE.  >             Action: Retry the SAVESET MERGE operation with the1             appropriate secondary input save set.r           5-6 SSMgr Messages           I                                                            SSMgr MessagesUI                                      5.3 SSMgr FATAL Level Error MessagesU    G          TOOMANYERRS, Too many errors reading save set filename. Giving              up.   G             Explanation: Too many errors were encountered while reading E             the save set. Probably a problem with the drive or media.   F             Action: If the problem is with the drive, try mounting the'             media on a different drive.e  A          UNSRECTYPE, Unsupported save set record type in save set              filename  <             Explanation: The save set contains a record typeD             inappropriate for the SAVESET operation being performed.  F             Action: Check that the save set being used is appropriate.  -         5.4 SSMgr WARNING level Error Mesages   >          NOUSERFILES, No user files written to output save set  C             Explanation: The output save set is empty: i.e. no user 6             files were written to the output save set.  :             Action: Ensure that this is what was expected.           5.5 Terminal Messages   A               The following informational messages are written to A               SYS$OUTPUT, SYS$ERROR, and the logfile based on the G               setting of /TERMINAL options. See the /TERMINAL qualifier A               descriptions for each of the commands in Chapter 3.a  -         5.5.1 ERRORS Option Terminal Messages   6          Block recovered from XOR in save set filename  B             Explanation: The ERRORS terminal option is enabled. AnH             unreadable block in save set filename was recovered via XOR.  <          Block recovered via read-ahead in save set filename  C             Explanation: The ERRORS terminal option is enabled. The E             error specified immediately above was recovered via read-.             ahead.  I                                                        SSMgr Messages 5-7                     SSMgr Messages         5.5 Terminal MessagesW    A          Checksum error: block number number in save set filenameS  A             Explanation: The ERRORS terminal option is enabled. AnF             checksum error was detected in block number number in save             set filename.l  :          Current volume is not the next volume in this set  E             Explanation: The ERRORS terminal option is enabled. While D             reading a multivolume tape set, the SSMgr has determinedF             that the currently loaded volume is not the next member of             the volume set.   <          CRC error: block number number in save set filename  A             Explanation: The ERRORS terminal option is enabled. AGE             CRC error was detected in block number number in save seta             filename.U  7          Error recovery successful in save set filenameO  C             Explanation: The ERRORS terminal option is enabled. TheSH             error specified immediately above was successfully recovered             by SSMgr.[  '          ERRORS terminal option enabledj  G             Explanation: The ERRORS terminal option is enabled for this              SAVESET command.  :          Missing Block: number number in save set filename  A             Explanation: The ERRORS terminal option is enabled. A E             missing block was detected in block number number in saveG             set filename.   =          Read error: block number number in save set filename   A             Explanation: The ERRORS terminal option is enabled. A F             read error was detected in block number number in save set             filename.   3          Recovery unsuccessful in save set filename_  C             Explanation: The ERRORS terminal option is enabled. The B             error specified immediately above was not recoverable.           5-8 SSMgr Messages c         I                                                            SSMgr Messages I                                                     5.5 Terminal Messagest    <          Rewritten Block: number number in save set filename  A             Explanation: The ERRORS terminal option is enabled. AtE             rewritten block error was detected in block number numberr!             in save set filename.m  =          XOR error at block block-number in save set filenamen  B             Explanation: The ERRORS terminal option is enabled. AnE             XOR error was detected in block number number in save set              filename.   -         5.5.2 EVENTS Option Terminal Messages   '          EVENTS terminal option enableda  G             Explanation: The EVENTS terminal option is enabled for thisS             SAVESET command.            Opening file filename  H             Explanation: The EVENTS terminal option is enabled. SSMgr is1             attempting to open the file filename.   "          Output save set: filename  H             Explanation: The EVENTS terminal option is enabled. The fileG             filename has been successfully opened for use as the output              save set.A  )          Primary input save set: filename,  H             Explanation: The EVENTS terminal option is enabled. The fileH             filename has been successfully opened for use as the primary             input save set.e  0          Resetting to beginning of file filename  C             Explanation: The EVENTS terminal option is enabled. The C             merge of an image save set with an incremental save set C             requires two passes over the incremental save set. ThistC             message indicates that SSMgr is resetting the secondaryO/             input save set for the second pass.n  H          Resuming operation on volume volume-number of save set filename  C             Explanation: The EVENTS terminal option is enabled. The G             save set filename is on a multivolume tape and operation is,4             resuming on volume number volume-number.  I                                                        SSMgr Messages 5-9                     SSMgr Messages         5.5 Terminal Messagest    $          Rewind of filename complete  G             Explanation: The EVENTS terminal option is enabled. /REWINDnG             was specified and the tape has been successfully rewound to              BOT.  2          Rewinding filename to beginning of volume  G             Explanation: The EVENTS terminal option is enabled. /REWINDo8             was specified and the tape is being rewound.  *          Scanning secondary input save set  G             Explanation: ... EVENTS ...enabled. An incremental save setnE             is being merged with an image save set. SSMgr is scanningIA             the incremental save set for file system information.t  +          Secondary input save set: filename   C             Explanation: The EVENTS terminal option is enabled. TheeE             file filename has been successfully opened for use as theo%             secondary input save set.a  D          Unable to continue writing to save set filename. Continuing             operation.  E             Explanation: The EVENTS terminal option is enabled. SSMgrrD             could not write to one of the multiple output save sets.G             SSMgr will continue the COPY or MERGE operation, writing to +             the remaining output save sets.a  *         5.5.3 LOG Option Terminal Messages  $          LOG terminal option enabled  D             Explanation: The LOG terminal option is enabled for this             SAVSESET command.   '          Processing user file: filename   E             Explanation: The LOG terminal option is enabled. The user 7             file filename is currently being processed.U               5-10 SSMgr Messagesf           I                                                            SSMgr MessagesiI                               5.6 Process Quota Exceeded (System Message)     3         5.6 Process Quota Exceeded (System Message)   I               If you see the "Process Quota Exceeded" system message, theeI               process quota exceeded is most likely PGFLQUO or DIOLM. YouiI               must rerun the SSMgr operation in a process with sufficient 4               quota to complete the SSMgr operation.                                                                              I                                                       SSMgr Messages 5-11i a                               F      _________________________________________________________________  F                                                                  Index      F      A______________________________   D______________________________  :      Account quotas                    DCL interface,  1-1        changing, 2-3(        process, 2-2                    EF        user, 2-2                       _______________________________9      Authorization Key,  2-7           Error report,  4-7         AUTHORIZEF        See OpenVMS Authorize           F______________________________  5                                        Files-11,  3-1   $      B______________________________F      BACKUP                            H______________________________  +        See OpenVMS BACKUP              HELP   F      _______________________________   I______________________________  6      Command Language Interface        Input save sets7         (CLI)                            on disks,  3-2nB        command summary, 1-2              on multivolume tape sets,/        help, 1-6                            3-3 7        qualifiers, 3-14                  on tapes,  3-2 3      Commands                          Installation @        COPY, 3-15                        before installing,  2-1E        MERGE, 3-37                       conditions for failure,  2-7eB        qualifiers, 3-14                  disk space required,  2-1C        specifiers, 3-1                   license registration,  2-1t9        VALIDATE, 3-57                    privileges,  2-1 9      COPY,  1-3, 3-15                    sample run,  2-9oA        example, 3-27, 3-29             Internationalization,  1-6s*      CRC,  1-1, 4-2                    IVP6      Ctrl/T,  4-1                        example,  2-96                                          failure,  2-76                                          running,  2-7  F                                                                Index-1                   ?                                           OpenVMS MESSAGE,  1-6 @         L______________________________   Output save sets,  3-59         License                             on disks, 3-5ME          PAK,  2-1                          on multivolume tapes, 3-6t            registration,  2-1vI         License Management Facility       P______________________________e  A           (LMF),  1-6, 2-1                PAK (License PAK),  2-1 G         Log file, 4-8                     Process Quota Exceeded,  5-11 =                                           Purging files,  2-6 '         M______________________________ I         MERGE, 1-3, 3-37                  Q______________________________   ;          example,  3-46                   Qualifiers,  3-14l  0         MESSAGE                           Quotas  >          See OpenVMS MESSAGE                See Account quotas         MessagesI          during installation,  2-7        R______________________________ <          error level,  5-1                Registration,  2-1=          fatal level,  5-2                Release notes,  2-1i7          informational level,  5-1          option, 2-5n7          internationalization,  1-6       Reports,  4-1           listing,  5-1+          warning level,  5-7              S I         Multivolume tape sets, 3-3        _______________________________M9                                           Save sets,  4-1TC         N______________________________     as input to BACKUP, 1-6.G         NETMBX, 1-6, 2-3                    Files-11 mount example, 3-8b?                                             handling types, 1-4X6         O                                   input, 3-1B         _______________________________     management policy, 1-39         OpenVMS, 1-1                        physical, 3-1S;          Ctrl/T,  4-1                       specifiers, 3-1 6          versions,  1-1, 2-1                types, 3-1;         OpenVMS AUTHORIZE, 2-3            SAVESET.LOG,  4-8r/         OpenVMS BACKUP, 1-1, 3-1          SSMgrr9          image,  1-4                        benefits, 1-1pC          incremental,  1-4                  completion reports, 4-2cD          policy,  1-3                       disk space required, 2-1>          procedures,  2-4                   error reports, 4-77          strategies,  1-4                   errors, 4-2d9          time spent doing,  1-5             /FOREIGN, 1-6i@          version compatibility,  1-6        input save sets, 3-1=         OpenVMS HELP, 1-6                   installation, 2-1*9                                             log file, 4-8';                                             privileges, 1-6            Index-2                             SSMgr (cont'd)I          purging files from previous      V______________________________f  C             versions,  2-6                VALIDATE,  1-2, 3-57, 4-1 >          recoverable errors,  4-4           example, 3-63, 4-2:          release notes,  2-1              VMScluster,  1-69          reports,  4-1                    VMSINSTAL,  2-3 8         SYS$SYSTEM, 2-2                     running, 2-4         System diskJI          backup,  2-4, 2-5                W______________________________o  :         T                                 Wildcards,  3-12A         _______________________________     input save sets, 3-12eD         Tape, 1-6                           journal file names, 3-13B          /FOREIGN,  3-1                     output save sets, 3-12         Tape scwitching, 3-3I         TMPMBX, 1-6, 2-3                  X______________________________   3                                           XOR,  4-2                                                     I                                                                   Index-3                                                                                                                                                                                                                                                                                                                                                                                                                 11
at.tuwien.lva.uebersetzerbau-lu 2246 2247 y n 2246 0 0 0 0 0 18227 100 611
alt.personals.spanking.the.monkey 5990 5991 y n 5990 0 0 0 0 0 18228 100 611
alt.smokers.camel 1297 1298 y n 1297 0 0 0 0 0 18229 100 611
alt.in.love.with.a.goat.montgomery-wood 3 4 y n 1 0 0 0 0 0 18230 100 611
alt.games.pc-calcio-7 227 228 y n 227 0 0 0 0 0 18231 100 611
microsoft.public.it.winserver 58503 58504 y n 58503 0 0 0 0 0 18232 100 611
alt.flarf.parp 159 160 y n 159 0 0 0 0 0 18233 100 611
pt.rec.desporto 4920 4921 m n 4920 0 0 0 0 0 18234 100 611
alt.newage.angels 3 4 y n 1 0 0 0 0 0 18235 100 611
alt.geo.emblaze-support 77 78 y n 77 0 0 0 0 0 18236 100 611
alt.discussioni.droghe 3 4 y n 1 0 0 0 0 0 18237 100 611
weblogic.developer.interest.90beta.server.usability 3 4 y n 3 0 0 0 0 0 18238 100 611
alt.pl.comp.os.freeunices.moderationtest 3 4 y n 1 0 0 0 0 0 18239 100 611
alt.drooling.animation.fandom 821 822 y n 821 0 0 0 0 0 18240 100 611
comp.lang.clipper 123455 123456 y n 123455 0 0 0 0 0 18241 100 611
alt.games.elder-scrolls 35363 35364 y n 35363 0 0 0 0 0 18242 100 611
microsoft.public.win16.programmer.ui 3727 3728 y n 3727 0 0 0 0 0 18243 100 611
alt.kazema.binaries 3 4 y n 1 0 0 0 0 0 18244 100 611
bit.listserv.yardimci 2 3 y n 0 0 0 0 0 0 18245 100 611
alt.religion.cyberchurches.ficotw 162 163 y n 162 0 0 0 0 0 18246 100 611
alt.no-advertising.files.images.sex.interracial 4241 4242 y n 4241 0 0 0 0 0 18247 100 611
de.alt.fan.konsumterror 68588 68588 y n 68587 0 1 0 0 0 18248 100 611
comp.sys.acorn.extra-cpu 15838 