|
|
|
|
|
The subject of backup missions is covered in detail in Phase 5, and during that phase that you will learn how to design your backup missions. One topic included in Phase 5, however, is important to us now. In Phase 5, we give recommendations for backup mission naming standards.
Note: You should now read the section What Are Backup Missions? in Phase 5, and decide on your backup mission names, so that they can be specified in your report decollating mission definitions.
Backup Mission names are specified in the report decollating mission definition in the DO BACKUP statement, as indicated in the following example.
ON CLASS = T EXTWTR DEST FORM
PRT COPIES LVL USER DEST MAX COPIES
PRINT/CDAM PARMS =
WHEN LINE - COL - PRINT REF NXT CT AND/OR
STRING =
DO USER = * LVL LINE 006 COL 016 - 019 S T
SYNONYM = CONCAT =
DO NAME = *-FOR- LINE 003 COL 035 - 043
DO NAME = *P+* LINE 006 COL 016 - 019
DO PRINT = STD MUST =
DO BACKUP = BKP0031D
DO
In this example, we have specified that backup mission BKP0031D (when run) should backup the compressed dataset in which this report resides. (It is the backup mission definition that contains the information about how long to keep the report backed up.) Only after the backup mission has run, will a copy of the compressed dataset be archived.
If you do not specify a DO BACKUP statement, your report will not be backed up by Control-D, and the report will not be available for restoring.
Parent Topic |