HOWTO:Housekeeping
Housekeeping
Housekeeping Considerations
In general, it is only needed to keep an eye on the fallback history. The fallback library may grow quickly, especially on the production machines. It should be cleared on a regular basis with the CLRFBSOMS command.
Other parts of TD/OMS will grow as well but they will not be in your way.
Cleanup after a failed transfer
TD/OMS may not remove transfer artifacts to aid issue resolution. After you have resolved the remote or local issue you have to cleanup any artifacts from the transfer run.
The libraries that TD/OMS uses are all using the following pattern: CCnnnnnn. E.g., OM012345. Please make sure that the following libraries are removed:
Local System
- OMnnnnnn - This is the library where the old objects are moved to during a run
- ONnnnnnn - This is the library where the new objects are moved to during a rollback
- ODnnnnnn - This is the temporary distribution library on the sending machine
- /OMnnnnnn - The transfer directory in the root of the file system
Remote System
- OMnnnnnn - This is the library where the old objects are moved to during a run
- ONnnnnnn - This is the library where the new objects are moved to during a rollback
- ORnnnnnn - This is the temporary distribution library on the receiving machine
- /OMnnnnnn - The transfer directory in the root of the file system
Removing Fallback History
The Clear Fall Back Save library (CLRFBSOMS) command is used to remove all or some entries from the Fall Back Save libraries file and remove the corresponding savefiles from the Fall Back Save library. You should schedule it on a regular basis to avoid a large size of the fallback save library.
The fallback save library is defined per application in the application definition function (STRAD).
You may also selectively purge saved fallback entries. The function name is Fallback Library Maintenance and it is started from the recovery menu or through the STRFBLM command.
See:
Command Clear Fall Back Save library
Fallback Library Maintenance
Removing Log Entries
If you want you may remove log entries with the CLRLOGOMS command. It is recommended to keep at least 7 years of history.
Removing archived sources
You may remove archived sources but we also recommend to keep a long history. They do not take a lot of space and you never know who comes asking. In case you want to remove the sources you can use the Dumped Sources Maintenance (STRDSM) function to purge them with F14.