Document revision date: 30 March 2001

## OpenVMS System Manager's Manual

Previous | Contents | Index

## 11.9 Understanding OPCOM and Volumes

If you have a standalone workstation or easy access to disk and tape drives at your facility, you probably can mount and initialize your own volumes. At some sites, however, an operator performs these tasks. Using the services of an operator might be necessary because the drive you want to use is located remotely or because you do not have the necessary privileges to manipulate a volume.

To communicate with the operator at your site, consult the operator about site-specific procedures. Depending on how your system is customized, using the operator communication manager (OPCOM) might be necessary. The OPCOM system process allows you to request assistance from the operator and allows the operator to respond to your requests. ( Section 2.4 explains OPCOM.)

### 11.9.1 Requesting Operator Assistance

Note Please consult your operator about your site-specific procedures. Your site may not use OPCOM or may use it differently from the examples in this section.

If you want the operator to mount a tape for you, use OPCOM to ask the operator to mount the tape.

How to Perform This Task

Enter either the REQUEST/REPLY or the REQUEST/TO command:

- The /REPLY qualifier assigns your request a unique number to which the operator can respond.
- If your facility is very large, several operators might each have specific tasks. If this is the case, use the REQUEST/TO command, which allows you to send a message to a specific operator (identified by a keyword).

If you request operator assistance and an operator is not available, you receive the following message:

    %MOUNT-I-NOOPR, no operator available to service request

This indicates that the operator has disabled the operator's terminal. To abort your request, press Ctrl/Z.

You can also use the /[NO]ASSIST qualifier with either the BACKUP or the MOUNT command:

- If a mount request fails and you specified /ASSIST, mount failure messages appear on the operator terminal (if OPCOM is enabled). The /ASSIST qualifier is the default for both the BACKUP and MOUNT commands.
- If you specified /NOASSIST, mount failure messages appear on your terminal instead of on the operator terminal.
- If you are on a workstation but forget to specify /NOASSIST, OPCOM (if OPCOM is running) requests that the operator load the next volume.
  If you have the OPER privilege, you can respond to the request by using another terminal window to enter the following commands:

      $ REPLY/ENABLE=TAPES
      $ REPLY/TO=identification-number "message text"

Examples

1. To request the operator to mount a tape, enter a command similar to the following one:

       $ REQUEST/REPLY "Is anyone using drive MUA12?"
       %OPCOM-S-OPRNOTIF, operator notified, waiting...12:21:12.46
       %OPCOM-S-OPREPLY, PLEASE DIRECT YOUR REQUEST TO THE TAPE OPERATOR
       2-APR-2000 12:26:13.12. request 2 completed by operator OPA0
       $

   The /REPLY qualifier assigns your request a unique number (in this case, 2) to which the operator can respond. Note that you cannot enter any additional commands until the operator responds.
2. The following example shows you how to direct your request to a specific operator using the /TO qualifier:

       $ REQUEST/TO=TAPES "Is anyone using drive MUA12?"
       %OPCOM-S-OPRNOTIF, operator notified, waiting...12:40:11.32
       %OPCOM-S-OPREPLY, I'M DONE GO AHEAD
       2-APR-2000 12:45:26.18. request 5 completed by operator OPA0
       $

## 11.10 Listing the Contents of a BACKUP Save Set

BACKUP allows you to obtain information about save sets and the files in a save set. You can display this information at your terminal or send it to an output file.

Because BACKUP writes save sets in a format that only BACKUP can interpret, a list operation is the only way to determine the contents of a save set without restoring the save set. You can perform a list operation in conjunction with any other BACKUP operation.

By default, a save-set listing supplies information about files in the save set similar to the information supplied by the DCL command DIRECTORY/DATE/SIZE, including the actual number of blocks used for each file.

You can also perform a BACKUP list operation to list the contents of a BACKUP journal file. BACKUP journal files, which are created during a save operation by using the command qualifier /JOURNAL[=file-spec], contain on-disk records of BACKUP save operations and the file specifications of the files saved during each operation. Section 11.13.4 contains more information about creating and listing BACKUP journal files.

How to Perform This Task

To list the contents of a BACKUP save set, perform the following actions:

1. Insert the media containing the save set into the drive.
2. If the volume is a disk, mount the disk as described in Section 11.8.2 (BACKUP mounts tapes automatically).
3. Enter the BACKUP/LIST command in the format specified in the OpenVMS System Management Utilities Reference Manual. The /REWIND qualifier rewinds the tape to the beginning before searching for the save set. To list all the save sets on a volume, include the asterisk wildcard character (*) with the device specification.
   To list the contents of save sets does not require you to know the names of save sets on magnetic tape. Enter the device specification of the drive in which the tape is inserted with the BACKUP/LIST command. BACKUP reads the next save set it encounters on the magnetic tape and stops processing when it reaches the end of that save set. BACKUP does not automatically rewind to the beginning-of-tape marker unless you include the /REWIND qualifier in your command. Therefore, you can list the next save set (if one exists) by repeating the BACKUP/LIST command. If no more save sets exist on the tape, BACKUP issues the following error messages:

       %BACKUP-F-OPENIN, error opening MUA0:[000000].; as input
       -SYSTEM-W-NOSUCHFILE, no such file

Examples

1. To obtain save-set information about a magnetic tape save set named 2MAR1555.BCK in the drive MIA0:, enter the following command:

       $ BACKUP/LIST MIA0:2MAR1555.BCK/REWIND
       Listing of save set(s)
       Save set:          2MAR1555.BCK
       Written by:        POLYANNA
       UIC:               [000200,000207]
       Date:              21-MAY-2000 09:36:14.68
       Command:           BACKUP/LOG [USER.SAVE] MIA0:2MAR555.BCK/REWIND/LABEL=WKY201

       Operating system:  OpenVMS Alpha Version 7.3

       BACKUP version:    7.3
       CPU ID register:   08000000
       Node name:         _SUZI::
       Written on:        _MIA0:
       Block size:        8192
       Group size:        10
       Buffer count:      3
       [USER.SAVE]ANOTHER.DAT;1                  1  18-MAY-2000 14:10
       [USER.SAVE]LAST.DAT;1                     1  18-MAY-2000 14:11
       [USER.SAVE]THAT.DAT;1                     7  18-MAY-2000 14:10
       [USER.SAVE]THIS.DAT;2                     1  18-MAY-2000 13:44
       Total of 4 files, 10 blocks
       End of save set

2. The following command rewinds the tape to the beginning and lists all save sets on the volume MIA0:

       $ BACKUP/LIST MIA0:*.*/REWIND

3. The following command combines a list operation with a save operation to magnetic tape:

       $ BACKUP/LIST=MYBACK.DAT [PRAMS] MTA0:2MAR1555.BCK/LABEL=DLY201

   BACKUP verifies that the volume label is DLY201 and copies the contents of the directory [PRAMS] to a save set named 2MAR1555.BCK. The command qualifier LIST causes BACKUP to write save-set information to the file MYBACK.DAT as the save operation proceeds.

## 11.11 Understanding Multivolume BACKUP Operations

When you save data with BACKUP, the save set often spans more than one volume, creating a multivolume save set. When this occurs, BACKUP fits as much data as it can on the first volume, then dismounts it. Depending on whether you specified more than one drive in the BACKUP command line or if you are using a tape loader, BACKUP then performs the following actions:

- If you specified only one drive in the BACKUP command line and you are not using a tape loader or operator assistance, BACKUP prompts you to remove the tape that is in the drive and insert another one:

      %BACKUP-I-RESUME, resuming operation on volume 2
      %BACKUP-I-READYWRITE, mount volume DAILY02 on MUA0: for writing
      Respond with YES when ready:

  Note If you are using OPCOM and the /ASSIST qualifier (the default), the following message appears on your terminal:
      %BACKUP-I-RESUME, resuming operation on volume 2
      %MOUNT-I-OPRQST, Please mount volume DAILY02 in device MUA0:
      BACKUP requests: Saveset DAILY.SAV, Volume number 02, write ENABLED

  After you insert and load the second volume (or an operator fulfills the mount request), BACKUP continues writing data to the second volume.
- If you specified multiple drives on the command line, BACKUP continues writing data to the second volume, assuming the drive is loaded, is on line, and has the correct volume label. BACKUP unloads the first volume and displays the following message:

      %BACKUP-I-RESUME, resuming operation on volume 2

- If you are using a tape loader, BACKUP continues writing data to the tape in the next slot, assuming the tape loader has an adequate supply of correctly labeled tapes. BACKUP rewinds and unloads the first tape and displays the following message:

      %BACKUP-I-RESUME, resuming operation on volume 2
         .
         .
         .

### 11.11.1 Multivolume Tape Labeling

In a multivolume save-set operation, BACKUP does not initialize the first volume (unless you use the /REWIND qualifier). BACKUP does initialize subsequent volumes. BACKUP determines the volume labels for subsequent volumes as follows:

- If you did not specify a label on the command line, BACKUP uses the first six characters of the save-set name to create a label for the first volume (unless you use the /EXACT_ORDER qualifier, in which case BACKUP preserves the volume label on the tape). For subsequent volumes, BACKUP uses the first four characters from the label of the first volume plus the number of the volume in the sequence. For example, suppose you are saving files that require three tapes and the save-set name is BACKUP. If you do not specify a label, the first tape is labeled BACKUP, the second BACK02, and the third BACK03.
- If you specified a single label on the command line using the /LABEL qualifier and it matches the label of the first volume, BACKUP labels subsequent volumes with the first four characters of the label from the first volume plus the number of the volume in the sequence. For example, suppose you are saving files that require three tapes and the first tape is labeled TAPE. The second tape gets the label TAPE02, and the third tape gets the label TAPE03.
- If you specified multiple labels on the command line using the /LABEL qualifier (without the /EXACT_ORDER qualifier), BACKUP uses the labels you specify. If the operation requires more labels than you specified, BACKUP uses the first four characters of the last volume label and the volume number of the tape.
- You can use the /EXACT_ORDER qualifier in conjunction with the /LABEL qualifier to specify the order in which you want BACKUP to use the labels. BACKUP continues the operation as long as the label of the tape in the drive matches the corresponding label on the command line. If you do not specify enough labels on the command line to complete the operation, BACKUP prompts you to enter a label for the tape in the drive.

As a safeguard against initializing or writing the wrong tape, BACKUP compares the label that you specify on the command line to the label of the tape in the drive. Section 11.12 describes how BACKUP processes tape labels and handles a label mismatch.

### 11.11.2 MOUNT Messages When Backing Up Tapes

The MOUNT utility generates VOLINV messages on continuation tape volumes during backups when you use devices that have loaders or when the stackers or loaders become empty. The following example shows messages displayed:

    %MOUNT-I-MOUNTED, ABCD03 mounted on _$4$MUA3: (HSC70)
    %BACKUP-I-RESUME, resuming operation on volume 4
    %MOUNT-F-VOLINV, volume is not software enabled
    %BACKUP-I-READYWRITE, mount volume 4 on _$4$MUA3: for writing
    Enter "YES" when ready: yes
    %MOUNT-I-MOUNTED, ABCD04 mounted on _$4$MUA3: (HSC70)

Once the devices are put back on line or the media is made ready, the backup session continues or finishes as expected. This problem will be addressed in a future release.

## 11.12 Understanding BACKUP Tape Label Processing

After mounting a tape, BACKUP processes information stored in the volume header record of the tape before writing to it. Specifically, BACKUP performs the following actions:

- Checks the volume protection information to ensure that you have the right to access the volume in the manner you requested.
- Checks the tape expiration date to prevent you from initializing a magnetic tape that has not yet expired.
- Compares the volume label specified in the BACKUP command line (either explicitly with the /LABEL qualifier or implicitly through the save-set name) to the volume label of the tape to prevent you from creating a save set on the wrong magnetic tape. BACKUP uses the following guidelines when processing tape labels:
  - If you specify a label that is longer than six characters, BACKUP truncates the label to six characters.
  - If the volume label is less than six characters long, BACKUP pads the volume label with the blank character to six characters.
  - The first four characters of the volume label either must match the first four characters of the label specified in the BACKUP command line exactly, or must end with one or more underscore characters. If the first four characters of the volume label end with one or more underscore characters, and the label specified in the command line matches the part of the volume label that appears before the underscore characters, BACKUP accepts the match. (For example, the volume label ABN_ matches the command line label ABN but does not match the command line label ABNE.)
  - If the fifth and sixth characters of the volume label are numbers between 0 and 9, BACKUP does not compare these characters with corresponding characters in the label specified in the BACKUP command line. Otherwise, the fifth and sixth characters in the volume label must exactly match the corresponding characters in the label specified in the BACKUP command line.

If the labels match, you have the proper protection, and the tape is expired, BACKUP performs the designated operation.

If you specify more than one label with the /LABEL qualifier and you do not specify the /EXACT_ORDER qualifier, the BACKUP operation succeeds if any of the labels you specify match the tape's volume label. For example, if the tape's volume label is MA1686, the BACKUP operation will succeed if you specify the following list of labels with the /LABEL qualifier:

    /LABEL=(MA1684,MA1685,MA1686)

If the volume labels do not match, BACKUP displays the following error message:

    %MOUNT-I-MOUNTED, DKA0 mounted on _SODAK$MUA0:
    %BACKUP-W-MOUNTERR, volume 1 on _SODAK$MUA0 was not mounted because
     its label does not match the one requested
    %BACKUP-W-EXLABEER, volume label processing failed because
     volume MB1684 is out of order, Volume label MA1684 was expected
     specify option (QUIT, NEW tape, OVERWRITE tape, USE loaded tape)
    BACKUP>

Depending on the option you specify, you can quit the backup operation (QUIT), dismount the old tape and mount a new one (NEW), overwrite the data on the tape (OVERWRITE), or USE the loaded tape.

If you specify more than one label with the /LABEL qualifier and you also specify the /EXACT_ORDER qualifier, BACKUP compares the label of the loaded tape with the first label that you specified with the /LABEL qualifier. If the labels match, BACKUP begins the operation. If the labels do not match, BACKUP prompts you with the previous message.

Assuming the volume labels of the tapes you use match the corresponding labels on the command line, BACKUP continues processing until it completes the operation or runs out of volume labels. If you do not specify enough labels on the command line to complete the operation or if the tape loaded does not have an ANSI label, BACKUP prompts you to enter a label for the tape in the drive.

If you use blank tapes or tapes that you intend to overwrite, use the /IGNORE=LABEL_PROCESSING qualifier. This suppresses the previous BACKUP message, which normally occurs if BACKUP encounters a non-ANSI-labeled tape during a save operation.

For more information about the /EXACT_ORDER, /IGNORE, and /LABEL qualifiers, refer to the OpenVMS System Management Utilities Reference Manual.

## 11.13 Backing Up Files and Directories

This section explains copying files, backing up files and directories, comparing files, and creating and listing BACKUP journal files.

Note When you use the Backup utility with files, BACKUP processes relative version -0 as if it were 0, saving the most recent version instead of the earliest version of the file for processing.

### 11.13.1 Copying Files to Other Files

You can copy files using BACKUP. The copy function of the BACKUP command differs from the DCL command COPY because it preserves certain file information such as the version number, creation dates, revision dates, and protection codes (although, by default, the owner UIC of the copies is the UIC of the current process). Also, unlike the DCL command COPY, you can use BACKUP to copy entire directory trees, maintaining the directory structure.

How to Perform This Task

To make identical disk-to-disk copies of files, use the following format:

`BACKUP input-specifier output-specifier`

Examples

1. The following command copies the file EMPLOYEES.DAT in the current directory to the directory [BATES.TEST]:

       $ BACKUP EMPLOYEES.DAT USER1:[BATES.TEST]EMPLOYEES.DAT

2. You can also create copies of entire directory trees. For example:

       $ BACKUP USER1:[BATES...] USER2:[BATES...]

   This command re-creates the directory structure of user BATES on the disk named USER2:
3. The following command copies all files in the directory tree [LYKINS...] to the directory tree [OWLCR...] on the same disk:

       $ BACKUP [LYKINS...]*.*;* [OWLCR...]*.*;*

Note Disk-to-disk copy operations initiated using the /VERIFY qualifier might attempt to verify files that are not copied. For example, if an error prevents you from successfully copying a file from one disk to another location and you specified the /VERIFY qualifier for that operation, the system displays two error messages: one indicates that the file was not copied, and the other indicates that the file was not verified.

### 11.13.2 Backing Up Files and Directories to a Save Set

One of the most common BACKUP operations is to save files to a save set. There are several types of save sets. For more information about save sets, see Section 11.5.

How to Perform This Task

To back up files or directories, use the BACKUP command in the following format:

`BACKUP input-specifier output-specifier [/SAVE_SET] [/LABEL=label]`

The input-specifier specifies the file you want to back up, and the output-specifier specifies the device and save-set name.

When you save data to disk, use the output save-set qualifier /SAVE_SET. If you do not specify /SAVE_SET, BACKUP copies files in standard file format rather than creating a BACKUP save set. When you save data to tape, you do not need to specify /SAVE_SET; BACKUP treats all magnetic tape files as save sets. Use the /LABEL qualifier to specify the label of the tape you are using.

Examples

1. The following commands back up the file EMPLOYEES.DAT to a save set:

       $ ALLOCATE MUA0: TAPE1(1)
       %DCL-I-ALLOC, MUA0: allocated
       $ INITIALIZE TAPE1 DLY101(2)
       $ BACKUP/LOG EMPLOYEES.DAT MUA0:EMPL_MAY91.BCK/LABEL=DLY101(3)
       %MOUNT-I-MOUNTED, BACKUP mounted on _MUA0:
       BACKUP-S-COPIED, copied DUA0:[SCHULT]EMPLOYEES.DAT;32
       $

   In this example, the individual commands performs the following actions:

   Previous | Next | Contents | Index

   | privacy and legal statement |
   6017PRO_046.HTML