|
|
|
|
|
The CA-TLMS Tape Retention System (TRS) uses the information stored in the VMF and RMF to control volume retention. Retention for a dataset may be defined in
If retention for a dataset is specified in more than one of these locations, CA-TLMS applies the retention definition with the highest priority, as demonstrated in the following table.
Table 10 CA-TLMS Retention Definition Priorities
Retention Definition Type |
Priority |
|---|---|
RMF entry |
Highest priority |
Retention specified in JCL (e.g., using parameter EXPDT) |
Medium priority |
Retention specified in the RMF Default record |
Lowest priority |
The conversion programs determine the appropriate retention for each dataset and automatically convert CA-TLMS retention policies to Control-M/Tape rule definitions. The name of each Control-M/Tape rule definition generated from CA-TLMS retention policies begins with a prefix specified during conversion.
Note: Control-M/Tape retention rules are created from information in the RMF. Therefore, they do not reflect the Tape Default Retention (DEF Statements) specified in member TLMSIPO of the CAI.PPOPTION library. Tape Default Retention can affect Keep Data Control (Type 2) datasets.
To ensure compatibility with CA-TLMS during implementation of Control-M/Tape, you must define Control-M/Tape rules that specify the information contained in the DEF statements in use at your site.
Parent Topic |