Creating a data set archive policy
To define a policy for data set archive, select DATA SET ARCHIVE in the Type field.
Schedule
For a description of how to use the Schedule tab, see Schedule.
Options
Common options
For a description of the following options, see Policy options:
- Compression type
- Use SMS policy
Policy-specific options
Option | Description |
---|---|
Primary days non-usage | This option is not available if you check Use SMS policy. When it is available, it applies to all data sets, overwriting SMS attributes of SMS-managed data sets. |
Allow archive only if backup exists | Check this option (default) to ensure that only data sets with a current backup copy will be archived. The data set will not be archived if:
The policy will archive the data set only if the change bit is off, and there is a valid backup copy. The policy does not check whether the backup copy is the most current one, and there is no protection from manually deleting a backup of an archived data set. |
Override retention | Allows overriding the retention period that will be set for all archives done by this policy. The following override retention options are available:
|
Filters
For a description of how to use the Filters tab to select resources for processing, see Filters.
Policy-specific filtering considerations
During an activity run, the policy uses the defined filters and policy options to select resources, excluding the following:
- Non-SMS managed data sets with unmovable or absolute DSORG
- Non-SMS managed multi-volume data sets
- Catalogs
- Temporary data sets
- Data sets using symbols to specify a VOLSER (Indirect Volume Serial Support)
- All uncataloged data sets including VTOC Indexes
- SYS1.** data sets including VVDSs
- Generation Data Sets that are either without a catalog entry, non-SMS managed, non-active, or whose GDG base is defined with NOSCRATCH
- ALIASes
The catalog entry of the archived data set is not SMS-managed.