|
|
|
|
|
Control-M/Tape supports a variety of expiration types. These are listed in the table below:
Table 186 Control-M/Tape Expiration Types
Expiration Type |
Sample Value |
Description |
|---|---|---|
Specific date |
10/05/93 |
Expires on the date indicated. |
Cycle |
05 |
Expires when five cycles (versions) of the data set exist. |
EDM |
|
External Data Manager decides when the volume is to expire. |
Catalog |
|
Data set expires when its entry no longer exists in the operating system catalog. |
Last access |
30 |
Data set expires when it has not been accessed for 30 days. |
Days |
30 |
Data set expires when 30 days have passed since the creation date. |
Permanent |
|
Data set never expires. |
Return from Vault |
|
Data set expires after the volume’s specified vault pattern is completed (meaning, the volume has returned from the vault). |
JCL EXPDT |
93310 |
Data set expires according to the JCL EXPDT/RETPD field. |
The retention period of a data set is the combination of up to three expiration dates, with a logical relation between them (And/Or). For example:
DO RETENTION = CYCLES 0003 PREFIX N (Y/N) And/Or A
JCL EXPDT And/Or
DO
Note: For a more detailed description of retention cycle definitions, refer to parameter CYCLECNT in the INCONTROL for z/OS Installation Guide: Installing.
The above rule determines that the data set expires when three cycles of the data set exist and the JCL EXPDT/RETPD/DATACLAS date has been reached.
The JCL EXPDT parameter can specify a special value (for example, 99365), thus causing the data set to be permanently retained.
Parent Topic |