Archiving inactive data
Advanced Archive for DFSMShsm supports multiple Archive scenarios.
In general, all of the archive scenarios involve identifying the inactive data sets and then
moving those data sets to the archive. However, where the archive scenarios differ most is in how
the inactive data sets are identified and selected for processing:
- Explicit identification of inactive ML2 data sets
- In this scenario, you specify data set selection criteria that the Archive function compares to the MCDS records (either by reading the MCDS or reading a flat file that contains the unloaded contents of the MCDS) to evaluate the ML2 candidate data sets. Data sets that meet the selection criteria are moved to the archive.
- Archiving L0 disk data sets
- In this scenario, you specify data set selection criteria that the Archive function compares to the output from an IDCAMS DCOLLECT to evaluate the candidate L0 disk data sets. Data sets that meet the selection criteria are moved to the archive.
- Setting up ML3-like policy for your SMS management classes
- In this scenario, you assign archive policies and archive groups to your SMS management class definitions and the Archive function automatically builds the data set selection criteria that implement the ML3-like storage tier.
Because there are differences between the scenarios in how the candidate data sets are evaluated by the Archive process and in how you modify the Archive job JCL, the procedures for the scenarios are documented separately.
The procedures for verifying that the archive contains the correct data sets are the same, regardless of scenario.