Exception File for VOLSER Restore Jobs

Template Programming Interface Guide › Restore Job Exception Files › Exception File for VOLSER Restore Jobs

Exception File for VOLSER Restore Jobs

The following table outlines the structure of a VOLSER restore job exception file. The table lists the records in the order you or an authorized client might use them in a file.

Record	Information Specified	Required	Quantity Allowed
COMMENT	Comment	No	1
*¹	Additional comments	No	Multiple
EXCEPT	Domains to process differently than specified in job template file	Yes	Multiple; at least 1
BASEVOL	Base tapes in primary and copy tape sets to process ²	Yes, if no INPUT record	1 for each EXCEPT record
INPUT	Tape from which to restore data	Yes, if no BASEVOL record	Multiple
OPTIONS	Processing options for domains identified on EXCEPT record	No	Multiple
REPORT	Report options for domains identified on EXCEPT record	No	1 for each EXCEPT record
RESTO	Target domain to which to restore data; required after an EXCEPT ABSTRACT record	No	1 for each EXCEPT record
INCLUDE	Files or minidisk extents to restore from domains identified on EXCEPT record	No	Multiple
EXCLUDE	Files or minidisk extents to not restore from domains identified on EXCEPT record	No	Multiple
USRRECORD²	Original file information CA VM:Backup requires to restore data Used by authorized clients only.	No	Multiple
CHECKSUM²	Number that protects file from manual modification Used by authorized clients only.	No	1; last in file

¹ When a job is exported from CA VM:Backup, all *records appear in order after the COMMENT record or, if no COMMENT record is specified, at the beginning of the file

² Used by authorized clients only.

Example VOLSER Exception File

The following example shows an exception file that can be used for a VOLSER restore job. The file defines the following exceptions to the associated restore job:

For minidisk 200 belonging to user ID TEST2, restore all files to minidisk 100 belonging to the same user ID, TEST2. Before the files are restored, the minidisk will be formatted. The files will be restored from either primary tape volume VMB001 or twin volume VMB002.
For minidisk 191 belonging to user ID TEST1, restore two files: TEST DATA1 renaming it to T DATA1, and TEST DATA4. If the files exist on disk, replace them with the restored files. The files will be restored from either primary tape volume VMB001 or twin tape volume VMB002.
For minidisk 391 belonging to user ID TEST1, restore two files: TEST DATA1 renaming it to OLDTEST DATA1, and TEST DATA4 renaming it to OLDTEST DATA4. Restore the files to the reader of user ID TEST1. The files will be restored from primary tape volume VMB006.
For directory TEST1.FIRST.SECOND in file pool SFS, restore three files back to the same file space, renaming one of them. Do not restore SFS authorizations or aliases. Replace any existing files and use a new date. Do not restore any SFS authorizations. The files will be restored from primary tape volume VMB021 or twin volume VMB121.
For directory TEST1.FIRST.SECOND in file pool SFS, restore one file to the reader of user ID TEST1. The file will be restored from primary tape volume VMB021.

For directory TEST1.SCRIPTS in file pool VMSYSU, restore all files to the minidisk 432 of user ID MARKE. Restore with a new date and replace any existing files. The files will be restored from primary tape volume VMB021 or twin volume VMB121.

EXCEPT USERID TEST2 200
INPUT 0 VOLSER VMB001
INPUT 1 VOLSER VMB002
RESTO DISK TEST2 100
OPTIONS RESDATE OLDDATE
OPTIONS RESTYPE FORMAT
INCLUDE FILE * *

EXCEPT USERID TEST1 191
INPUT 0 VOLSER VMB001
INPUT 1 VOLSER VMB002
OPTIONS RESTYPE REPLACE
OPTIONS RESDATE OLDDATE
INCLUDE CMSFILE TEST DATA1 RENAME T DATA1
INCLUDE CMSFILE TEST DATA4

EXCEPT USERID TEST1 391
INPUT 1 VOLSER VMB006
RESTO RDR TEST1
INCLUDE FILE TEST DATA1 RENAME OLDTEST DATA1
INCLUDE FILE TEST DATA4 RENAME OLDTEST DATA4

EXCEPT DIRECTORY SFS:TEST1.FIRST.SECOND
INPUT 0 VOLSER VMB021
INPUT 1 VOLSER VMB121
OPTIONS RESAUTH NO
OPTIONS RESALIAS NO
OPTIONS RESDATE NEWDATE
OPTIONS RESSFS REPLACE
INCLUDE FILE JUNK FILE1 RENAME REAL FILE1
INCLUDE FILE JUNK FILE4
INCLUDE FILE JUNK FILE5

EXCEPT DIRECTORY SFS:TEST1.FIRST.SECOND
INPUT 0 VOLSER VMB021
RESTO RDR TEST1
OPTIONS RESAUTH NO
INCLUDE FILE JUNK FILE5

EXCEPT DIRECTORY VMSYSU:TEST1.SCRIPTS
INPUT 0 VOLSER VMB030
RESTO DISK MARKE 432
OPTIONS RESAUTH NO
OPTIONS RESALIAS NO
OPTIONS RESEXTERN NO
OPTIONS RESDATE NEWDATE
OPTIONS RESTYPE REPLACE
INCLUDE FILE * *

* Record

OPTIONAL

Use the * record to add comments to exception files in addition to the comment specified on the COMMENT record. When you manage exception files through the CA VM:Backup screens, CA VM:Backup displays the comment on the COMMENT record on the screen; comments on * records are not displayed on the screen.

You can use * records with the COMMENT record or by themselves, and you can include as many as you need. You can place * records anywhere in the file; however, when the file is exported, CA VM:Backup places all * records in order after the COMMENT record or, if no COMMENT record exists, at the beginning of the file.

Note: This record is available only through TPI. Using this record will not prevent you from managing the exception file through the CA VM:Backup screens.

* [text]

Definitions

text: Can include up to 80 characters of comment text; any additional text is truncated. You must enter the asterisk (*) in column 1 of the record. You can use uppercase and lowercase letters; when you import or export the file, text case is preserved.