Innovation Data Processing - FDRARC – Data Migration & Space Management for z/OS

Technical Center

Sales

Products

Free Trial

Contact:

Latest News

Information Center

Worldwide Sites

FDRARC Technical Description

This section contains two examples of FDRARC to illustrate how easy it is to use.

Example 1

In this first example, data sets which have not been referenced in the last 60 days (indicated by the ADAYS=60 keyword) will be migrated from all online volumes.

After being deleted from disk, the data sets will be recorded in an Archive Control File, which is a very compact/efficient file that can hold the details of several hundred data sets in a single track.
The data sets will be recataloged for Auto-Recall (RECALL=YES), allowing batch jobs and online users to perform quick and transparent recalls if required, without causing unwanted delay or disruption.
The MIGRAT=YES option ensures that migrated datasets are cataloged to MIGRAT, which is recognized by IBM as indicating a migrated dataset. If the datasets are not recalled after 2 years and one month (RETPD=730), they will be removed from the control file.

//ARCHIVE     EXEC  PGM=FDRABR,REGION=0M
//SYSPRINT     DD   SYSOUT=*
//SYSPRIN1     DD   SYSOUT=*
//ARCHIVE      DD   DSN=FDRABR.ARCHIVE,DISP=SHR
//TAPE1        DD   DSN=ARC1,DISP=(,KEEP),UNIT=TAPE
//SYSIN        DD   *
    DUMP TYPE=ARC,ONLINE,ADAYS=60,RETPD=730,DSNENQ=USE,RECALL=YES,MIGRAT=YES

Example 2

For Data Centers without automated tape libraries (ATLs), or for those that require the fastest possible recall, the migrated data can be optionally directed to disk. Our second example illustrates the use of DASD and Tape to hold the migrated data.

The first copy, which will be retained for 30 days, will be sent to a pool of disks, as directed by the TAPE1 DD statement.
Any initial recalls (i.e. within the first 30 days) can be satisfied from disk without involving a tape mount.
A second copy of the data will also be sent to tape (via the TAPE11 DD) and will be retained for 730 days.

//ARCHIVE     EXEC  PGM=FDRABR,REGION=0M
//SYSPRINT     DD   SYSOUT=*
//SYSPRIN1     DD   SYSOUT=*
//ARCHIVE      DD   DSN=FDRABR.ARCHIVE,DISP=SHR
//TAPE1        DD   DSN=FDRABR.POOLDISK.POOL1,UNIT=DISK,
//                  VOL=SER=(ARC001,ARC002,ARC003),DISP=OLD,LABEL=RETPD=30
//TAPE11       DD   DSN=SMS2,UNIT=TAPE,DISP=(,KEEP),LABEL=RETPD=730
//SYSIN        DD   *
    DUMP TYPE=ARC,SMSMANAGE=YES,RECALL=YES,DSNENQ=USE,MIGRAT=YES
    MOUNT STORGRP=TSO1
    MOUNT STORGRP=TSO2

Interaction with DFSMS

The Data Migration in our second example above was being limited to data sets residing on DASD volumes currently belonging to the TSO1 and TSO2 DFSMS Storage Groups, as directed by the MOUNT STORGRP statements.

When operating against DFSMS-controlled DASD Volumes, either ABR selection criteria can be used, or (if SMSMANAGE=YES is coded, as above) the attributes of the SMS Management Class associated with each dataset can be employed in the selection process.

If the Management Class is chosen, and both SMS and non-SMS volumes are processed in the same run, ABR criteria will be used for the non-SMS volumes and ignored for SMS volumes.

Simulation

Any FDRARC job can be turned into a simulation by altering the “DUMP TYPE=ARC” to “SIM TYPE=ARC”. This verifies the migration criteria and reports on which data sets would get selected in a real execution, but NO DATA is actually migrated.

FDRARC's simulation facility is an essential tool for ensuring that the selection criteria you’ve coded will do exactly what you think it will.....before it actually does it for real.