ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

What are the different types of retention within TLMS?

book

Article ID: 212963

calendar_today

Updated On:

Products

TLMS Tape Management

Issue/Introduction

What are the different types of retention within TLMS?

Environment

Release : 14.0

Component : CA TLMS Tape Management

Resolution

Catalog Control - Type 1 and A

 

Data sets are retained at the current location as long as the data set name exists in the z/OS system catalog (SYSCATLG), regardless of the keep date. The first time you execute TRS after the data set is uncataloged, the tapes containing this data set will be either scratched or moved to the next location.

Data sets under catalog control will not be scratched or moved if they are less than 2 days old. To change this number, specify the system option CATDAYS (CAI.CTAPOPTN, member TLMSIPO), with a value of 0 to 3 days.

Use type A to apply to all data sets on chain.

 

Keep Date Control - Type 2 and B

 

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.

 

Catalog/Date Control - Type 3 and C

 

This type combines the first two types. Data sets are retained at the current location until the keep date has passed and the data set no longer resides in the SYSCATLG.

Use type C to apply to all data sets on chain.

 

 

Cycle Control - Type 4

 

Data sets are retained at the current location until the number of data sets at the location exceeds the quantity specified. Then the oldest data set, based on creation date and time, is either moved or scratched. Use the count field to specify the quantity. To use cycle control with Generation Data Groups (GDGs), data sets must be identified in the retention control statement as partially qualified with the dash specified in place of the generation number. No matter how the DSN parm is specified, the entire data set name (without GnnnnVnn) is used to determine how many cycles exist.

 

 

Elapsed Days Control - Type 5

 

Data sets are retained at the current location for the number of days specified. When the specified number of days has elapsed, the tape is either scratched or moved. Use the count field to specify the number of days. If the tape is at the data center, the number of days starts when the data set is created. If the tape is at an off-site location, the number of days starts from the moved date.

A day is a 24-hour period, from midnight to midnight. Therefore, if a tape is created at 2:00 PM on May 1 and retention is defined as one day (5DC0001), the tape will not be scratched or moved until after midnight on May 2, which is actually May 3.

 

 

Move Immediate Control - Type 6

 

Tapes are either scratched or moved from the data center the first time you run TRS after the data set is created. This type is valid only at the data center, the first location.

 

 

Manual Control - Type 7

 

Data sets are retained at the current location until they are either scratched or moved by specific manual instructions. The tape will never be scratched automatically. This retention type is valid only at the last location specified; therefore, it may be used at the data center only if there is no off-site movement specified.

 

 

Days Since Last Used Control - Type 8

 

Data sets are retained at the current location until a specified number of days has passed. When the data set has not been used for input or output for a certain number of days, it will be scratched or moved. Use the count field to specify the number of days. This type is valid only at the data center.

 

 

Expiration Date Keyword Control - Type 9

 

Data set retention is controlled by special values coded on the JCL parameter LABEL=EXPDT=value.

In this parameter, value can be one of the following:

Value

Retention is based on

Which is the same as type

970mm

Auxiliary message number (01-50)

 

98000

Foreign tape, bypass TLMS processing

 

98ddd

The number of days (ddd) since last used

8

99000

Catalog control

1

990cc

The number of cycles (cc)

4

991dd

Catalog/date control, where dd is the number of days since creation

3

992dd

Days since creation

 

99365

Manual control (permanent)

7

99366

Manual control (permanent)

 

 

This type allows you to specify data center retention in the JCL but still move the tape through off-site storage locations. If no keyword value is supplied, the CA TLMS keep date is used. This retention type is valid only at the data center.