11.01.2013 Views

ABCs of z/OS System Programming Volume 3 - IBM Redbooks

ABCs of z/OS System Programming Volume 3 - IBM Redbooks

ABCs of z/OS System Programming Volume 3 - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

The second-newest version is treated as though it had been created on the same day as the<br />

newest backup version. Therefore, the second-newest version (newest EXTRA backup copy)<br />

is not expired until the number <strong>of</strong> retention days specified by the RETAINDAYS value or the<br />

number <strong>of</strong> days specified in RETAIN DAYS EXTRA BACKUPS attribute in the management<br />

class have passed since the creation <strong>of</strong> the newest backup version. (The management class<br />

value is only used if RETAINDAYS was not specified for the version).<br />

EXPIREBV processing and RETAINDAYS<br />

For EXPIREBV processing, the RETAINDAYS value takes precedence over all existing<br />

criteria when expiring active and retained backup copies for SMS data sets and non-SMS<br />

data sets. EXPIREBV needs to be run to delete backup versions with RETAINDAYS values<br />

that have been met.<br />

The EXPIREBV command is used to delete unwanted backup and expired ABARS versions <strong>of</strong><br />

SMS-managed and non-SMS-managed data sets from DFSMShsm-owned storage. The<br />

optional parameters <strong>of</strong> the EXPIREBV command determine the deletion <strong>of</strong> the backup versions<br />

<strong>of</strong> non-SMS-managed data sets. The management class attributes determine the deletion <strong>of</strong><br />

backup versions <strong>of</strong> SMS-managed data sets. The management class fields Retain Extra<br />

Versions and Retain Only Version determine which ABARS versions or incremental backup<br />

versions are deleted. The RETAINDAYS parameter specified on the data set backup request<br />

determines how long a data set backup copy is kept for both SMS-managed and<br />

non-SMS-managed data sets.<br />

BACKDS command<br />

The BACKDS command creates a backup version <strong>of</strong> a specific data set. When you enter the<br />

BACKDS command, DFSMShsm does not check whether the data set has changed or has met<br />

the requirement for frequency <strong>of</strong> backup. When DFSMShsm processes a BACKDS<br />

command, it stores the backup version on either tape or the ML1 volume with the most<br />

available space.<br />

With z/<strong>OS</strong> V1R11, the RETAINDAYS keyword is an optional parameter on the BACKDS<br />

command specifying a number <strong>of</strong> days to retain a specific backup copy <strong>of</strong> a data set. If you<br />

specify RETAINDAYS, number <strong>of</strong> retain days is a required parameter that specifies a<br />

minimum number <strong>of</strong> days (0-50000) that DFSMShsm retains the backup copy. If you specify<br />

99999, the data set backup version never expires. Any value greater than 50000 (and other<br />

than 99999) causes a failure with an ARC1605I error message. A retain days value <strong>of</strong> 0<br />

indicates that:<br />

► The backup version might expire within the same day that it was created if EXPIREBV<br />

processing takes place or when the next backup version is created,<br />

► The backup version is kept as an active copy before roll-<strong>of</strong>f occurs,<br />

► The backup version is not managed as a retained copy.<br />

226 <strong>ABCs</strong> <strong>of</strong> z/<strong>OS</strong> <strong>System</strong> <strong>Programming</strong> <strong>Volume</strong> 3

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!