You might need to tell your tape management system that a volume needs to be permanently retained.
If you are using IBM's DFSMSrmm or DFRMM tape management system products, you should define policies (vital record specifications) to cover the TSM tape data sets. A single policy specifying the TSM high level qualifier includes all TSM tape data sets.
You can retain all DFSMShsm tapes that require no movement, with the exception of tapes written by ABARS, by specifying the RMM TSO subcommands shown in following example:
+--------------------------------------------------------------------------------+ |RMM ADDVRS DSNAME('mprefix.**') COUNT(99999) OWNER(owner) | |RMM ADDVRS DSNAME('bprefix.**') COUNT(99999) OWNER(owner) | |RMM ADDVRS DSNAME('authid.**') COUNT(99999) OWNER(owner) | +--------------------------------------------------------------------------------+
where:
For more information on defining policies, see DFSMS/MVS DFSMSrmm Implementation and Customization Guide. For more information on vital record specifications, see DFSMSrmm Guide and Reference.
If you are using a different tape management system, one of the most commonly used ways to specify permanent tape retention is by setting up the expiration date in the device class definition within TSM. Be aware of the following when setting up the expiration date:
Here is an example of how to update the cartridge device class for permanent retention using the expiration date of 99365 (December 31, 1999):
+--------------------------------------------------------------------------------+ |update devclass cartridge expiration=99365 | +--------------------------------------------------------------------------------+