Cloud Data Manager

Action delete-expired

Deleting imported data sets

An Imported data set is a data set that was migrated from another media, and is a copy of the original data set. The expiration date of imported data sets can be set in the import policy. See Importing data sets from tapes for more details.

Deleting archived data sets

The recorded expiration date of an archived data set is established upon archive. On the due day, life cycle management verifies that the expiration date has not changed.

Determining the expiration date for archived data sets

For all data sets, life cycle management first explores the following data set attributes:

1. Expiration date in the data set’s VTOC entry at time of archive

2. Expiration date in the data set’s catalog entry at time of archive

  • For VSAM data sets, the catalog entry of the cluster is searched for a valid expiration date.

  • For non-VSAM data sets, both the VTOC entry and the catalog entry are searched for a valid expiration date. The latest date among the two is considered to be the determinative expiration date.

If a valid expiration date is found and it is earlier than the current date, the data set and its catalog entries are deleted. If no valid expiration date was found, the data set is not deleted. If the expiration date is later than the current date, the data set expiration date is updated.

Determining the expiration date for SMS-managed archived data sets

For SMS-managed data sets, the process continues and searches the data set’s Management Class expiration attributes. The data set’s Management Class is determined according to SMS rules:

1. The data set’s Management Class, if one is assigned.

2. If not assigned, the SMS base configuration default Management Class, if one is assigned

3. If not assigned, the Management Class default values

The Management Class expiration attributes are compared to the data set’s VTOC attributes:

  • The data set’s creation date is compared to EXPIRE AFTER DATE/DAYS

  • The data set’s last reference date is compared to PRIMARY DAYS NON-USAGE

If both Management Class expiration attributes have values that express a valid expiration date, the latest date of the two is considered to be the determinative expiration date. If a valid expiration date is determined and it is earlier than the current date, the data set and its catalog entry are deleted. If no valid expiration date was found, the data set is not deleted and will be kept until manually deleted. If the date has not passed yet, the data set is not deleted and its expiration date is updated to the new date.

If the data set has an assigned Management Class that does not exist, an error message is displayed. In this case it is possible to delete it using the DELARC command, or to redefine the Management Class.

Archived Generation Data Sets

The decision to check whether the archived GDS is eligible for deletion is determined by parameters in the agent’s configuration file. See the installation guide for more details. A GDS will be deleted according to expiration date and catalog entries, in the following manner:

  • An archived GDS with an explicit expiration date will be deleted according to the expiration date, regardless of whether it is active or rolled off.

  • An archived GDS without an explicit expiration date will be deleted once it is rolled off. Life cycle management treats a GDS without a catalog entry as rolled off.

  • An archived GDS that has no expiration date, no catalog entry and no GDG base catalog entry will not be deleted at all, to avoid accidental deletes due to problems in the z/OS catalog.

  • An archived GDS with a GDG base catalog entry defined with the PURGE parameter will be deleted when rolled off - even if its expiration date has not been reached yet.

  • An archived GDS whose GDG base catalog entry was defined with the NOPURGE parameter will not be deleted when rolled off, as long as its expiration date has not been reached. The expiration date is determined either in the VTOC, Catalog or Management class.

  • Changing the SCRATCH attribute of an existing GDG base catalog entry from SCRATCH to NOSCRATCH will not affect an already archived GDS - the archived GDS will be handled according to the GDG base catalog entry at the time of archive. New GDSs of the same GDG base catalog entry will not be archived.

Archived permanent data sets

Data sets with the following expiration dates are considered permanent and will not be deleted by life cycle management if archived:

Catalog PERM dates

9999.999

1999.999

1999.365

1999.366

Catalog EMPTY dates

0000.000

No expiration date

VTOC PERM dates

1999.999

1999.365

1999.366

VTOC EMPTY dates

0000.000

No expiration date

Deleting archives manually vs. an automated process

The Management Class default expiration attribute value is “NO LIMIT”, meaning that by default, an archived data set will not be deleted by automatic processes, but can be deleted by a manual action such as the DELARC CLI command.

HSM SETSYS EXPIREDATASETS for archived data sets compatibility

The default value of the HSM EXPIREDATASETS parameter is NO, meaning that data sets that were created with an explicit expiration date in the catalog or VTOC, will not be deleted by an automatic process. When setting the HSM EXPIREDATASETS parameter to SCRATCH, HSM will delete the expired data sets during space management. Model9 life cycle management is compatible to EXPIREDATASETS(SCRATCH) only.

The default value of the HSM EXPIREDATASETS parameter is NO, meaning that data sets that were created with an explicit expiration date in the catalog or VTOC, will not be deleted by an automatic process. When setting the HSM EXPIREDATASETS parameter to SCRATCH, HSM will delete the expired data sets during space management. Model9 life cycle management is compatible to EXPIREDATASETS(SCRATCH) only.

Sync with storage

When deleting archived and imported data sets using Life cycle management or the a CLI command, the data set might still be visible in the web UI. To update the web UI, the management server performs an automatic synchronization with the storage device every 5 minutes. A "Sync With Storage" button is available in the AGENTS screen to initiate the process on demand. This action requires “admin” permission. A message is displayed in the AGENTS page when the action is completed.