78 ICF Catalog Backup and Recovery: A Practical Guide
recovery could be started, only to find there was no backup. Two years earlier,
when the catalog was first allocated, someone forgot to add the appropriate new
EXPORT step in the catalog backup job for this catalog, and all this time passed
without any backups being taken. With the double-asterisk facility in the Catalog
RecoveryPlus BACKUP command, any new, deleted, or renamed catalogs are
automatically put into the selection list the next time BACKUP is executed.
Backing up BCSs at different frequencies
In many ICF environments, some BCSs are volatile. Others are relatively static,
depending on frequency of allocations and deletions of data sets through those
BCSs. Also, the speed of recovery required for one BCS might be significantly
different than that for other BCSs. For these reasons, you should consider setting
up multiple backup jobs, where some are run at different frequencies than others,
and each job identifies the specific BCSs and/or VVDSs to be backed up at that
time.
For backing up your BCSs, the ease with which this can be done depends on
how good your BCS naming conventions are, by allowing you to specify mask
values for specific groups of BCSs to be backed up in each job.
For example, you might want all BCSs that catalog application development data
sets (assume these are highly active) backed up every four hours, whereas
those BCSs that catalog stable production data sets could be backed up once a
day. You could specify the following mask in your command that executes every
four hours:
BACKUP BCS(UCAT.DEV.**) ...
Or, you code the following mask in your command that executes once a day:
BACKUP BCS(UCAT.PROD.**) ...
6.4.2 Specifying VVDSs to be backed up
With the BACKUP VVDS command, you have similar options for specification of
one or more VVDSs to be backed up in a single command, and all selected
VVDSs will be backed up to a single output file.
To make coding simpler, the actual data set name of the VVDS is not specified,
but rather, you specify the
volser
for the VVDS to be backed up. Since the
standard (and required) data set name of a VVDS is SYS1.VVDS.V
volser
, it is a
simple matter for CR+ to convert the specified
volser
list into VVDS names.
You can specify a single VVDS, as illustrated in Figure 6-11, to be backed up to
the output file designated by the OUTFILE keyword.
Chapter 6. Using Catalog RecoveryPlus 79
Figure 6-11 Back up a single VVDS
Or, you can specify multiple, explicit VVDS names, as illustrated in Figure 6-12,
all of which will be backed up to the single output file designated by the OUTFILE
keyword.
Figure 6-12 Back up multiple VVDSs, explicitly-specified
Or, you can specify a
volser
mask, and all of the VVDSs selected by the mask
filter will be backed up to the single output file. In Figure 6-13, all VVDSs that
match the mask value VBOX* are backed up.
Figure 6-13 Back up multiple VVDSs, with a mask filter
Or, you can back up the VVDSs on all volumes in your entire system, as
illustrated in Figure 6-14.
Figure 6-14 Back up all VVDSs in the environment
When using mask filter values to identify VVDSs, you can also use the
EXCLUDEVVDS keyword, to specifically exclude those VVDSs that you do not
want to include in the selection list created by the mask filter, as shown in
Figure 6-15.
//BCKCPY DD DSN=BKUP.VVDSBAKS(+1),DISP=(,CATLG),
// UNIT=SYSALLDA,SPACE=(CYL,(10,10),RLSE)
BACKUP VVDS(VBOX01) OUTFILE(BCKCPY)
//BCKCPY DD DSN=BKUP.VVDSBAKS(+1),DISP=(,CATLG),
// UNIT=SYSALLDA,SPACE=(CYL,(10,10),RLSE)
BACKUP VVDS(VBOX01 VBOX02 VBOX03) OUTFILE(BCKCPY)
//BCKCPY DD DSN=BKUP.VVDSBAKS(+1),DISP=(,CATLG),
// UNIT=SYSALLDA,SPACE=(CYL,(10,10),RLSE)
BACKUP VVDS(VBOX*) OUTFILE(BCKCPY)
//BCKCPY DD DSN=BKUP.VVDSBAKS(+1),DISP=(,CATLG),
// UNIT=SYSALLDA,SPACE=(CYL,(10,10),RLSE)
BACKUP VVDS(**) OUTFILE(BCKCPY)

Get ICF Catalog Backup and Recovery: A Practical Guide now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.