|
The retention and deletion of BRMS created *SAVF's is a multi-step process.
The retention date is determined by values specified in the Media Policy.
When the STRMNTBRM EXPMED(*YES) command is run, a *SAVF expires when the retention date calculated by the settings in the Media Policy arrives.
You can review the retention dates for BRMS created *SAVF's, immediately expire it and even delete it from the system using the WRKSAVFBRM command.
The STRMNTBRM command will not only expire a *SAVF, it will also delete an expired *SAVF if it has been saved to a tape using the SAVSAVFBRM command.
If a *SAVF is not saved to tape, it can be deleted by the SAVSAVFBRM command after it has been expired by the STRMNTBRM command.
The SAVSAVFBRM command processes *SAVF files based on the control group they were created in, so if you're not planning on saving a the *SAVF's from a particular Control Group to a tape, make sure that the last entry in the control group is a SAVSAVFBRM command. For example:
In the example above, any expired *SAVF created by Control Group CASHEDITS will be removed from the system when the SAVSAVFBRM CTLGRP(CASHEDITS) command runs.
So, in summary...
- A *SAVF can be created by running a CONTROL GROUP.
- The *SAVF's expiration date is calculated by the settings in the Media Policy associated with the Control Group.
- The STRMNTBRM command will expire a *SAVF on the day is is scheduled to be expired.
- The STRMNTBRM command will also delete an expired *SAVF if it has already been saved to tape via the SAVSAVFBRM command.
- If an expired *SAVF is never going to be saved to tape, it can be deleted by running the SAVSAVFBRM command and specifying the name of the Control Group that created it.
|
