Document revision date: 30 March 2001

## OpenVMS System Management Utilities Reference Manual

Previous | Contents | Index

## /ALIAS

> Command Qualifier

> Specifies that the previous behavior of multiple processing of alias and primary file entries be maintained.

### Format

> /ALIAS save-set-spec (default)

> /NOALIAS

### Description

> The /ALIAS qualifier maintains the previous BACKUP behavior of treating alias file entries the same as primary file entries. Therefore, a primary file may be processed multiple times by BACKUP if one or more alias file entries reference the same primary file entry.

> If you specify /NOALIAS, alias directory and file entries are ignored. Therefore, multiple processing of primary files may be avoided, which saves time and save-set file space. If a restore operation is performed using the /ALIAS qualifier but the save set was created by using the /NOALIAS qualifier, a message is displayed that the /ALIAS qualifier will be ignored.

## /ASSIST

> Command Qualifier

> Allows operator or user intervention during a BACKUP operation if a magnetic tape mount request fails or if an operation requires another volume.

### Format

> /[NO]ASSIST input-specifier output-specifier

### Description

> The /ASSIST qualifier causes BACKUP to send messages to operator terminals when a failure occurs during a BACKUP mount request or when an operation requires another volume. BACKUP sends messages to operator terminals enabled to receive TAPES and CENTRAL messages. (See the description of the REPLY command in the OpenVMS DCL Dictionary for information about enabling and disabling operator terminals.) If a failure occurs, the operator can either abort the operation or correct the error condition and allow the operation to continue.

> If no operator terminal is enabled to receive TAPES and CENTRAL messages and to respond to a mount assist request, a message is displayed informing the user of the situation. If a volume is placed in the requested drive, no additional operator response is necessary. Any operator reply to a mount request is written to SYS$OUTPUT. When BACKUP is run interactively, SYS$OUTPUT is the user's terminal. When BACKUP is run in batch mode, SYS$OUTPUT is the batch job log file.

> If you specify /NOASSIST, mount messages appear on your terminal and are not sent to the operator.

> The default is /ASSIST. The /NOASSIST qualifier has no effect if the logical name SYS$COMMAND points to a device that is not a terminal (as is the case when you run BACKUP in a batch job). Specifying /NOASSIST when BACKUP is run in batch mode has no effect.

### Example

    $ BACKUP/NOASSIST [PAYROLL]*.*;* MTA1:PAYROLL.BCK/LABEL=WKY101

> This command mounts the volume labeled WKY101 on the MTA1 tape drive and copies all files in the [PAYROLL] directory to a save set named PAYROLL.BCK. The /NOASSIST qualifier directs BACKUP to send mount messages to your terminal rather than to the operator terminal. The WKY101 label indicates that WKY101 is a weekly BACKUP tape in group 1, volume number 01. (If the volume label of the tape is not WKY101, you can direct BACKUP to write the save set to the tape by choosing the OVERWRITE option at the BACKUP> prompt.)

## /BACKUP

> Input File-Selection Qualifier

> Selects files according to the BACKUP date written in the file header record by the BACKUP/RECORD command.

### Format

> input-specifier/BEFORE=time/BACKUP output-specifier

> input-specifier/SINCE=time/BACKUP output-specifier

### Description

> The /BACKUP qualifier is valid with Files--11 Structure Levels 2 and 5 volumes only and must be used with either the /BEFORE or /SINCE qualifier. You cannot use /BACKUP with the /CREATED, /MODIFIED, or /EXPIRED qualifiers in an image operation or in a physical operation.

> The /BACKUP qualifier selects files by comparing the date and time recorded in the BACKUP field of the file header record with the date and time specified with the /BEFORE or /SINCE qualifier. The date and time recorded in the file header record is the date and time the file was last saved or copied using the /RECORD command qualifier.

> When you use /BACKUP with /BEFORE, files with a BACKUP date prior to the specified date or time are selected. Files with no BACKUP date (that is, /RECORD was not specified when the file was saved or copied) are also selected.

> When you use /BACKUP with /SINCE, files with a BACKUP date equal to or later than the specified date or time are selected. Files with no BACKUP date (that is, /RECORD was not specified when the file was saved or copied) are not selected.

###

#### Examples

#1
    $ BACKUP/RECORD
    _From: [PAYROLL]*.*;*/BEFORE=01-SEP-2000/BACKUP
    _To: MTA1:SEP01.BCK

> In this command, the /BACKUP qualifier combined with the /BEFORE qualifier saves all versions of all files in the directory [PAYROLL] that have a BACKUP date written before September 1, 2000. The command qualifier /RECORD writes the date and time of the save operation to the file header record of each saved file.

#2
    $ BACKUP/RECORD [ACCOUNTS...]/SINCE=YESTERDAY/BACKUP MTA1:ACC.BCK

> In this command, the /BACKUP qualifier combined with the /SINCE qualifier saves all files in all subdirectories of [ACCOUNTS] that have a BACKUP date written since yesterday (24 hours before midnight last night). The command qualifier /RECORD writes the date and time of the save operation to the file header record of each saved file.

## /BEFORE

> Input File-Selection Qualifier

> Selects files dated earlier than the date and time you specify.

### Format

> input-specifier/BEFORE=time output-specifier

### Description

> The /BEFORE qualifier selects files by comparing the date and time in the specified field of each file header record with the date and time you specify in the command line. The following list shows the other input file-selection qualifiers (and their functions) that you can use with the /BEFORE qualifier. Use these other qualifiers only one at a time in your command line.

> /BACKUP | Selects files last saved or copied by BACKUP/RECORD before the date specified. Also selects files with no BACKUP date.
> /CREATED | Selects files created before the date specified.
> /EXPIRED | Selects files that have expired as of the date specified.
> /MODIFIED | Selects files last modified before the date specified. If you specify /BEFORE without another qualifier, /MODIFIED is used by default.

> Specify the date and time as a delta time or as an absolute time using the format [dd-mmm-yyyy[:]][hh:mm:ss.cc]. You can also use one of the following reserved words to specify the date and time:

> BACKUP | The BACKUP date of the file written by a previous BACKUP/RECORD operation (available only on Files--11 Structure Levels 2 or 5 volumes)
> TODAY | The current day, month, and year at 00:00:00.0 o'clock
> TOMORROW | 24 hours after midnight last night
> YESTERDAY | 24 hours before midnight last night

> The /BEFORE qualifier is not valid in incremental restore operations.

### Example

    $ BACKUP [POLICIES]*.*;*/BEFORE=TODAY/EXPIRED  DMA1:OLDPOL.BCK/SAVE_SET

> This command saves all files in the directory [POLICIES] that have expiration dates preceding today's date.

## /BLOCK_SIZE

> Output Save-Set Qualifier

> Specifies the output block size in bytes for data records in a BACKUP save set.

### Format

> input-specifier output-save-set-spec/BLOCK_SIZE=n

### Description

> You can specify a block size between 2048 and 65,535 bytes. BACKUP may adjust this value according to the constraints of the BACKUP format. Although BACKUP may adjust the block size you specify, it does not adjust the block size over the maximum of 65,535.

> If you specify /BLOCK_SIZE in a magnetic tape save operation, BACKUP ignores any block size defined by the /BLOCK_SIZE qualifier to the DCL command MOUNT.

> If the block size is set to a large value for a save set on magnetic tape, it is possible for the magnetic tape to run off its reel or for a large number of write errors to be logged. If this occurs, avoid using large block sizes. If the problem recurs with the same magnetic tape, avoid using that tape for future BACKUP operations.

> The default block size for magnetic tape is 8192 bytes; the default for disk is 32,256 bytes.

### Example

    $ BACKUP/RECORD DRA2:[LEE...]/SINCE=BACKUP MTA0:SAVEWORK.BCK/BLOCK_SIZE=10000

> This command saves a directory tree on DRA2 to a magnetic tape mounted on drive MTA0. The input file-selection qualifier /SINCE=BACKUP instructs BACKUP to process only those files in the specified directory tree that have been modified since the last BACKUP/RECORD operation. The output save-set qualifier /BLOCK_SIZE directs BACKUP to assign a block size of 10,240 (BACKUP rounds the specified block size of 10,000 up to the next multiple of 512).

## /BRIEF

> Command Qualifier

> Lists the file specification, size, and creation date for each file in the save set. (The size listed is the actual size of the file saved, rather than the number of blocks allocated to the file.) The /BRIEF qualifier is valid only with the /LIST qualifier and is the default format for BACKUP listings. Specify the /FULL qualifier to list the information in a format similar to that displayed by the DCL command DIRECTORY/FULL.

### Format

> /LIST/BRIEF save-set-spec

### Example

    $ BACKUP/LIST/BRIEF DBA2:[SAVE]23MAR00.BCK/SAVE_SET

    Listing of save set(s)

    Save set:          23MAR00.BCK
    Written by:        MOROCI
    UIC:               [000200,000200]
    Date:              23-MAR-2000 14:18:16.00
    Command:           BACKUP [SAVE] DBA2:[SAVE]23MAR00.BCK/SAVE_SET

    Operating system:  OpenVMS Alpha Version 7.3

    BACKUP version:    V7.3
    CPU ID register:   08000000
    Node name:         _SUZI::
    Written on:        _DBA2:
    Block size:        32,256
    Group size:        10
    Buffer count:      3

    [SAVE]INFO.TXT;4                  5   4-FEB-2000 13:12
    [SAVE]LAST.DAT;1                  1  18-JAN-2000 14:11
    [SAVE]WORK.DAT;3                 33   1-JAN-2000 10:02

    Total of 3 files, 39 blocks
    End of save set

> This command lists the BACKUP summary information and the file name, size, and creation date for each file in the save set. Note that the input save-set qualifier /SAVE_SET is required to identify the input specifier as a save set on a Files--11 medium.

## /BUFFER_COUNT

> Command Qualifier

> This qualifier is obsolete. You can still specify the /BUFFER_COUNT qualifier, although it has no effect. (This ensures that command procedures containing this qualifier will still operate correctly.) Compaq recommends that you remove the /BUFFER_COUNT qualifier from command procedures.

## /BY_OWNER

> Input File-Selection Qualifier

> Selects files for processing according to the user identification code (UIC).

### Format

> input-specifier/BY_OWNER[=[uic]] output-specifier

### Description

> If you specify /BY_OWNER without a UIC, BACKUP selects all files whose UIC matches that of the current process.

> Specify either a numeric UIC as octal numbers or an alphanumeric UIC in the form [g,m]. Wildcards are permitted. Note that the brackets are required.

> [g,m]

> g | An octal number in the range 0 to 37776 representing the group number or an alphanumeric group name
> m | An octal number in the range 0 to 177776 representing the member number or an alphanumeric member name

> If you do not specify /BY_OWNER, BACKUP processes all files specified by the input specifier.

###

#### Examples

#1
    $ BACKUP [SNOW...]/BY_OWNER MT$DRIVE:SNOW.BCK/LABEL=TAPE01

> In this example, BACKUP mounts the tape with the label TAPE01 on drive MT$DRIVE and saves all files in the directory and subdirectories of [SNOW] with the UIC of the current default process to the save set SNOW.BCK.

#2
    $ BACKUP [SUNDANCE]/BY_OWNER=[727,46]  DBA1:STABLE.BCK/SAVE_SET

> In this example, all files in the directory [SUNDANCE] with an owner UIC of [727,46] are saved to the sequential-disk save set STABLE.BCK on DBA1.

## /BY_OWNER

> Output File Qualifier

> Redefines the owner user identification code (UIC) for restored files.

### Format

> input-specifier output-specifier/BY_OWNER[=option]

### Description

> The following options are available:

> DEFAULT | Sets the owner UIC to the user's current default UIC. This option is the default if you do not specify the /BY_OWNER qualifier, except in image and incremental restore operations, when ORIGINAL is the default option.
> ORIGINAL | Retains the owner UIC of the file being restored. This option is the default if you specify the /BY_OWNER qualifier with no option. This option is also the default for incremental restore operations. To use this option, the UIC must be yours, or you must have the SYSPRV user privilege or be the owner of the output volume.
> PARENT | Sets the owner UIC to the owner UIC of the directory to which the file is being restored or copied. To use this option, the parent UIC must be yours, or you must have the SYSPRV user privilege or be the owner of the output volume.
> [uic] | Sets the owner UIC to the UIC specified. Use the [g,m] format (as described in the input file-selection qualifier /BY_OWNER). To use this option, the UIC must be yours, or you must have the SYSPRV user privilege or be the owner of the output volume.

> In restore operations where the command qualifier /IMAGE or /INCREMENTAL is specified, the default is /BY_OWNER=ORIGINAL.

### Example

    $ BACKUP DBA2:ACCOUNTS.BCK/SAVE_SET [CLEAVER...]/BY_OWNER=PARENT

> In this example, the sequential-disk save set ACCOUNTS.BCK is restored to the directory tree [CLEAVER...], assigning each restored file the owner UIC of the [CLEAVER] directory.

## /BY_OWNER

> Output Save-Set Qualifier

> Specifies the owner user identification code (UIC) of the save set.

### Format

> input-specifier output-save-set-spec/BY_OWNER=uic

### Description

> If the /BY_OWNER qualifier is omitted, the UIC of the current process is used. To use this qualifier on Files--11 save sets, you need the user privilege SYSPRV, or the UIC must be your own.

> Specify either a numeric UIC as octal numbers or an alphanumeric UIC in the form [g,m]. Wildcards are permitted. Note that the brackets are required.

> [g,m]

> g | An octal number in the range 0 to 37776 representing the group number or alphanumeric group name
> m | An octal number in the range 0 to 177776 representing the member number or alphanumeric member name

### Example

    $ BACKUP [CLEAVER...] MFA2:ACCOUNTS.BCK/BY_OWNER=[301,310]/LABEL=TAPE01

> In this example, BACKUP mounts the tape with the label TAPE01 on drive MFA2. Next, BACKUP saves the directory tree [CLEAVER...] to a save set named ACCOUNTS.BCK. The output save-set qualifier /BY_OWNER assigns an owner UIC of [301,310] to the save set.

## /COMMENT

> Output Save-Set Qualifier

> Places a comment in an output save set. If the comment string is longer than one word or if it contains nonalphanumeric characters, you must enclose it in quotation marks (" "). A DCL command can contain a maximum of 1024 characters.

### Format

> input-specifier output-save-set-spec /COMMENT=string

### Example

    $ BACKUP [REMARKS] DMA1:20JULREM.BCK/SAVE_SET -
    _$ /COMMENT="Remote operations for July 20, 2000"
    $ BACKUP/LIST DMA1:20JULREM.BCK/SAVE_SET
    Listing of save set

    Save set:          20JULREM.BCK
    Written by:        WALRUS
    UIC:               [360,054]
    Date:              20-JUL-2000 15:22:06.62
    Command:           BACKUP [REMARKS] DMA1:20JULREM.BCK/SAVE_SET/COMMENT=Remote
    operations for July 20, 2000

    Operating system:  OpenVMS Alpha Version V7.3

    BACKUP version:    V7.3
    CPU ID register:   0138084C
    Node name:         _ABBEY::
    Written on:        _ABBEY$DMA1:
    Block size:        32256
    Group size:        10
    Buffer count:      3

    [REMARKS]BAC.RES;1                                       2  20-JUL-2000 14:13
    [REMARKS]COM.LIS;1                                       1  20-JUL-2000 14:04
    [REMARKS]DTOP.DIR;1                                      1  20-JUL-2000 14:18
    .
    .
    .
    Total of 40 files, 535 blocks
    End of save set

> The first BACKUP command saves the directory [REMARKS] to a sequential-disk save set and records a comment. The BACKUP/LIST command displays the contents of the newly created save set. Note that the /SAVE_SET qualifier is required when creating a save set on disk.

## /COMPARE

> Command Qualifier

> Compares the save set, device, file, or files specified by the first parameter with the contents of the Files--11 device, file, or files specified by the second parameter and displays an error message if it finds a difference.

### Format

> /COMPARE file-spec file-spec

> /COMPARE save-set-spec file-spec

> /IMAGE/COMPARE device-spec device-spec

> /IMAGE/COMPARE save-set-spec device-spec

> /PHYSICAL/COMPARE device-spec device-spec

> /PHYSICAL/COMPARE save-set-spec device-spec

### Description

> In a BACKUP compare operation, the first parameter can be a Files--11 file or a wildcard character representing a set of files, a BACKUP save set on disk or magnetic tape, a tape device, or a disk device. The second parameter must be a Files--11 disk file, a wildcard character representing a set of files or a Files--11 disk device, unless you specify the command qualifier /PHYSICAL. When you specify /PHYSICAL, and the first parameter specifies a disk device, both disks in the compare operation must be mounted with the /FOREIGN qualifier.

> BACKUP displays the following error message if it encounters a difference between files it compares:

>     %BACKUP-E-VERIFYERR, verification error for ...

> Use the /COMPARE qualifier to compare a save set with original files or to compare files or volumes copied using BACKUP with original files. Because BACKUP processes files by blocks, comparing files not produced by BACKUP is likely to cause mismatch errors in files that are apparently identical.

> If you do not specify a version number with the file specification, the default is ;* (the asterisk wildcard character), which processes all versions of the file.

> Both parameters in a compare operation are input specifiers.

> If you are comparing two entire Files--11 volumes, use an image compare operation, as follows:

>     $ BACKUP/IMAGE/COMPARE DBA1: DBA2:

> You cannot use the command qualifier /DELETE or /RECORD in compare operations.

> Do not perform compare operations on files that were restored or copied using the output file qualifier /NEW_VERSION because this qualifier causes version numbers to change.

###

#### Examples

#1
    $ BACKUP/COMPARE JAZZ.DAT BLUES.DAT

> This example compares two Files--11 files. Because no version number is specified, BACKUP compares all versions of each file.

#2
    $ BACKUP/COMPARE/IMAGE MTA0:SWING.BCK DBA2:

> This example compares an image save set stored on magnetic tape and a Files--11 volume.

Previous | Next | Contents | Index

| privacy and legal statement |
6048PRO_016.HTML