The hsmlogretention option specifies how many days to maintain HSM log entries before pruning, and whether to save the pruned entries.
The HSM log is pruned when the first entry is written to the log after a Tivoli® Storage Manager for Space Management command or daemon is started. Some Tivoli Storage Manager for Space Management client daemons run continuously. Stop the daemons and start them again or activate one of the HSM commands to prune the HSM log.
You must use an authorized user ID to use this option.
If you use the hsmlogmax option instead of the hsmlogretention option, all records in the existing log are copied to the pruned log file, dsmhsm.pru. Then the existing log is emptied, and logging begins under the new size criteria.
Options File
Place this option in the client system options file dsm.sys within a server stanza.
Syntax
.-N-----------. >>-HSMLOGRetention--+-------------+---------------------------->< | .-D-. | '-days--+---+-' '-S-'
Parameters
- N
- Do not prune the log. The HSM log grows indefinitely. This is the default.
- days
- The number of days to keep log file entries before pruning the log. The range of values is 0 - 9999.
- D or S
- Specifies whether to save the pruned entries. You must also specify
the days parameter. Enter a space or comma to separate
the days parameter from the D or S parameter.
- D
- Discard the HSM log entries when you prune the log. This is the default.
Example task: Prune the log every 7 days. Discard the pruned log entries.
Example command: hsmlogr 7 d
- S
- Save the HSM log entries when you prune the log. The pruned entries are copied
from the HSM log to the dsmhsm.pru file that is in the same
directory as the HSM log.
Example task: Prune the log every 100 days. Save the pruned log entries.
Example command: hsmlogr 100,s