Data sets are retained at the current location until the CA TLMS keep date has passed. When the keep date has passed, the data set is either scratched or moved.
The librarian can use the UPD command to extend the keep date, if instructed to do so by the data set owner (unless a number is entered in the count field as explained below).
The KDATE system option can be used to determine whether JCL, if coded, overrides the default retention. If you do not want to use the keep date in the JCL, and do not have it defined by the DEF system option, you can specify a number of days in the count field. The number of days you specify is added to the creation date to determine the keep date each time TRS is run. This is useful for data sets that must be kept for a certain number of days, for example, 90 days or 365 days. If you use this method to determine the keep date, you cannot extend the keep date manually as stated above, because the recalculated date will be used by TRS.
Note: Specifying a number of days in the count field overrides RETPD or EXPDT in the JCL.
A data set is not available for scratch until the day after its keep date. For example, if a data set is created on May 1 and uses the default number of 3 days, the keep date will be May 4. This means that this data set will not be available for scratch until May 5.
See the Configuration Guide for an explanation of the KDATE system option.
Use type B to apply to all data sets on chain.
| Copyright © 2014 CA. All rights reserved. |
|