General policy definitions
Policy options
Each policy type supports additional options. The following table describes the options that are supported by more than one policy:
Option | Description | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
# of generations | This option is available for policies that create multiple backups of data sets or full volume dumps. It is available for policies defined without selecting the Use SMS policy check box, by setting the number of generations that are managed and kept in object storage, regardless of SMS attributes. | ||||||||||||
Use SMS policy | When you select this check box, the policy selects and processes only SMS-managed data sets and volumes, according to the SMS attribute # of generations. When you don't check this option, the policy selects all data sets and volumes according to the policy selection criteria and processes them according to options that you set in the policy definition. The default is not to use SMS policy. | ||||||||||||
Period/Retention | When you specify retention, the resources created by the policy become candidates for deletion by the lifecycle management process, according to the retention period or date that you specified. Retention is supported by only some of the policy types, and is available when you disable the Use SMS policy option. | ||||||||||||
Incremental backup | The policy back ups only data sets that have changed since the last backup. The policy determines whether a data set has been changed by examining the change bit. Incremental back up is the default. | ||||||||||||
Compression | Select the compression type according to the available components in your system. Some policies do not support all the compression types. The available compression types are as follows:
|
Policy filters
When the policy is running, resources that are included in the policy selection criteria become candidates for processing.
You can define the selection criteria by one of the following patterns:
- Data set name
- Volume name
- SMS storage group name
- z/OS Unix file name
For detailed explanation of pattern rules, click the question mark (?) icon next to Specify pattern(s) field.
To exclude resources from the selection criteria, use the filter criteria. The filter criteria defines an additional set of rules that the candidate resource must fulfill in order to be eligible for processing by the policy.
For example, the preceding selection criteria includes all data set names that begin with SYS2.*, and excludes data sets that have an SYS2.*.OLD suffix.
Certain policies have additional restrictions on the type of resources that you can select for processing.
The following resource filters are available:
- Data Set Name—Filters in/out data sets either by explicit name or by patterns using wild cards
- Volume Name—Filters in/out data sets and volumes either by explicit name or by patterns using wild cards
- Storage Group Name—Filters in/out data sets, volumes, and storage groups either by explicit name or by patterns using wild cards
- Data Set Is ZFS—Filters in/out data sets if they are type ZFS
- Data Set Organization—Filters out data sets by their organization grouped into the following types:
- Sequential—Includes all sequential organization data sets
- Partitioned—Includes partitioned data sets (PDS) or partitioned data set extended (PDSE)
- VSAM—Includes all VSAM organization data sets
To save the new policy, click Finish.