Explanation
NONSMSVERSIONS is an optional parameter specifying that you want
backup versions of non-SMS-managed data sets processed during processing
of the EXPIREBV command.
The following are optional parameters of the NONSMSVERSIONS parameter:
- DELETEIFBACKEDUP
- Controls the deletion of retired versions. If the age of a retired
version exceeds days, the retired version is deleted along
with all other backup versions that were made for the same cataloged
non-SMS-managed data set.
- CATALOGEDDATA
- Controls the deletion of backup versions (other than the retired
version) of non-SMS-managed data sets that were cataloged when they
were backed up. If the difference between the scratch date recorded
by a prior EXPIREBV command and the current date exceeds days,
all backup versions of the cataloged data set, except the retired
version, are deleted. If the cataloged data set has not been deleted,
the days parameter is ignored and all excess backup versions
(as a result of an (H)ALTERDS command) are deleted.
- UNCATALOGEDDATA
- Controls the deletion of backup versions made of non-SMS-managed
data sets that were uncataloged when they were backed up. If the age
of a backup version exceeds days, the backup version is deleted.
- days
- Number of days (0–9999) to keep a retired version (DELETEIFBACKUP),
a backup version of a cataloged data set after the EXPIREBV command
determines the data set has been deleted (CATALOGDDATA), or a backup
version of an uncataloged data set (UNCATALOGEDDATE).
Defaults
If RETAINDAYS is specified at the time of data set backup, the
RETAINDAYS value takes precedence over NONSMSVERSION. If RETAINDAYS
is not specified and you do not specify NONSMSVERSIONS on the command,
backup versions of non-SMS-managed data sets are not processed.
If you specify DELETEIFBACKEDUP with no days value, the DFSMShsm
default is 150 days. If you do not specify DELETEIFBACKEDUP on the
command, retired versions are not processed.
If you specify CATALOGEDDATA with no days value, the default for
days is 60. If you do not specify CATALOGEDDATA on the command, backup
versions of cataloged, non-SMS-managed data sets are not processed.
If you specify UNCATALOGEDDATA, you must specify days.
If you do not specify UNCATALOGEDDATA on the command, backup versions
of uncataloged, non-SMS-managed data sets are not processed.
Usage notes: - The result of the CATALOGEDDATA and UNCATALOGEDDATA subparameters
is based on whether a data set was cataloged or uncataloged when a
given backup version was created, not its current status.
- Eligibility for deletion of a backup version under the CATALOGEDDATA
criterion is based on the number of days that have passed since a
prior EXPIREBV command determined that a cataloged data set has been
scratched. This means that you must issue the EXPIREBV command a minimum
of two times: once to record that the cataloged data set has been
scratched and once to calculate whether the difference between the
current date and the recorded scratch date exceeds the specified number
of days.
- At least one of the optional subparameters of NONSMSVERSIONS must
be specified.
- The EXPIREBV command examines only the latest backup version for
a data set name to determine the existence of a retired version, and
it treats all backup versions older than the latest version (and all
versions of data sets uncataloged at the time of backup) as nonretired
versions. (A retired version is the backup version DFSMShsm creates
before it scratches a data set during data set retirement. DFSMShsm
does not automatically delete retired versions.)
- If the SETSYS versions parameter is decreased and the EXPIREBV
command is executed prior to the time the next backup version is created,
all excess versions—whether cataloged or uncataloged—are
deleted.
- Eligibility for deletion of a backup version under the CATALOGEDDATA
criterion for existing cataloged data sets is based on the current
version limit.