Auto Recall and Pooldisk Examples
All examples in this section are found in the JCL library installed with FDR. The member names are EX5121x.
Any of the examples in Archive-Backup-Examples can be used to archive data sets to tape for Auto-Recall. Just be sure to specify RECALL=YES and MIGRAT=YES on the DUMP statement, or make options ARCRECALL and MIGRAT the default in the FDR Global Options (see ABR-Options).
This section illustrates archiving to DASD and tape, and the procedures necessary to maintain the output DASD volumes. Typically, data sets are archived to DASD, with a short retention period, so that auto-recall requests issued in the first few days after archive can be processed quickly without tape mounts. However, if you have an Automated Tape Library (ATL) or Virtual Tape System (VTS) that can satisfy tape mounts quickly, you may want to archive only to tape.
Archive for Auto Recall example
Archive data sets and re-catalog them for Auto-Recall (see Recall Indicator in ABR Auto-Recall – Introduction). DYNARC is used to allocate the standard Archive Control File, since it is the only one used for Auto-Recall. COPY 1 of the backup data set is placed on a pool of DASD volumes with a retention period of 30 days; it is compressed by FDR. A duplicate copy is created on 3590 scratch tapes with a retention of 1000 days; it is compressed by the hardware compression feature of the tape drive.
In this example, the COPY2 files created on TAPE11 might be sent off-site for disaster recovery. At the disaster site, to cause ABR to automatically use the off-site tapes for restores instead of the POOLDISK files, change option ARCOPY to “2” in the FDR Global Options (see ABR-Options).
For on-site restores, ABR automatically uses COPY1 on POOLDISK until its expiration date (30 days) is reached, then it automatically tries to use COPY2 on tape. If the COPY2 tapes are off-site, or if you want to keep two copies for on-site restore after the migrated copy on DASD expires use the following FDRTSEL example.
Move DASD archives to tape example
Use FDRTSEL to select Archive Backup files on POOLDISK (COPY1) that expire within the next three days, moving them to tape. The expiration of the COPY1 on tape is 700 days from now. The Archive Control File is updated to point to the new COPY1, and the DASD backup files are scratched. See FDRTSEL-Introduction for more details on FDRTSEL.
Catalog POOLDISK data set example
This is an example of using IDCAMS to create a catalog entry for an ABR POOLDISK. This allows the POOLDISK to be referred to by name without having to specify the DASD volume serial numbers in the ABR JCL. A DELETE statement is included to delete any previous definition. This is only a catalog entry; no actual data set is created.
Clean Up DASD ABR backups example
Clean up expired ABR backup files from two POOLs of DASD. ABR searches the volumes specified for data sets that meet ABR’s naming conventions for backup data sets. If they have expired, ABR scratches these data sets without taking a backup. The second POOL is referenced as a cataloged data set.
This job should be run occasionally if you are doing ABR Archive Backups or Volume Backups to DASD, to clean up expired files and maintain as much free space as possible on those DASD volumes. However, since FDRTSEL can copy and scratch the DASD backups (see Move DASD Archives to Tape Example) and FDRARCH REORG scratches expired DASD backups, this job usually selects data sets that were not scratched for some reason.