General policy definitions


This topic describes general policy definitions that are applicable to more than one policy.

Schedule

To schedule a policy to run automatically, use the Schedule tab. You can select daily, weekly, monthly, or yearly scheduling.

Policies_GeneralOptions_Schedule.jpg

Options

Each policy type supports additional options.

image-2024-11-8_10-55-51.png

The following is a description of the options that are supported by more than one policy.

Option

Description

Applicable policy type

Compression type

The compression to be used for the policy should be chosen according to the available components in the system. Some policies do not support all the compression types. The available compression types are:

Type

Description

None

No compression

Best practice
Use this compression type if the object storage is compressing at rest or if there aren't enough resources in z/OS.

Lz4

Most suitable where zIIP and zAAP processors are available. This type usually achieves a good compression ratio and is lightweight in its zIIP and zAAP consumption.

Best practice
Use this compression type if you have enough zIIP engines and no zEDC.

Gzip

Suitable for both zIIP, zAAP, and zEDC, when zEDC is available and defined in the agent. For more information, see Updating-the-agent-configuration-files.

Best practice
This compression type compresses better than lz4 and can also leverage the on-chip zEDC (from z15 and later) because it is Java-based even if you don't have zEDC license.

DFDSS-gzip

Suitable for zEDC only. zEDC should be available and defined in the agent in order to use this compression type, see the Installation Guide for more details. Note that scheduling the IO on the zEDC compression card consumes more GCP. This compression generates the best throughput but it does not utilize zIIP engines.

Important

This compression type is not available for Data Set Import policies.

Best practice
Use this compression type if you have zEDC compression cards (z14 or earlier), or a zEDC hardware license (z15 and later). You should only use this type if you don't have enough zIIP available, but you have extra GCP to run the zEDC.

DFDSS-compress

Most suitable where zIIP, zAAP, or zEDC are not available. It achieves a medium compression ratio and consumes GCP. 

Important

This compression type is not available for Data Set Import policies.

Data set backup

Full dump

UNIX files

Data set archive

Data set import

Use SMS policy

When you check this option, the policy selects and processes only SMS-managed data sets and volumes, according to the relevant SMS attributes.

If you do not 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.

Data set backup

Full dump

UNIX files

Data set archive

Retention method

When specifying retention, the resources created by the policy will be candidates for deletion by the lifecycle management process, according to the user specified retention period or date.

Retention is only available when you disable the use SMS policy option.

Data set backup

Data set import

# 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 checking the Use SMS policy option, by setting the number of generations that will be managed and kept in object storage, regardless of SMS attributes.

Data set backup

Full dump

UNIX files


Filters

When the policy is running, resources that are included in the policy selection criteria become candidates for processing. The selection criteria is defined by either a data set name pattern, volume name pattern, SMS storage group name pattern, or z/OS UNIX file name pattern. For detailed explanation of pattern rules, click the question mark (?) icon next to Specify pattern(s) field header.

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.

Policies_GeneralOptions_Filters.jpg

For example, the selection criteria above includes all data set names that begin with SYS2.*, excludes data sets that have an SYS2.*.OLD suffix.

Certain policies have additional restrictions on the type of resources that can be selected for processing, see the section describing each policy for more details.

Resource filter type

Description

Data Set Name

Allows filtering in/out data sets either by explicit name or by patterns using wild cards.

Volume Name

Allows filtering in/out data sets/volumes either by explicit name or by patterns using wild cards.

Storage Group Name

Allows filtering in/out data sets/volumes/storage groups either by explicit name or by patterns using wild cards.

Data Set Is ZFS

Allows filtering in/out data sets if they are type ZFS.

Data Set Organization

Allows filtering out data sets by their organization grouped into the following types:

  • Sequential—Including all sequential organization data sets
  • Partitioned—Including partitioned data sets (PDS) or partitioned data set extended (PDSE)
  • VSAM—Including all VSAM organization data sets

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*