Schedlogretention

The schedlogretention option specifies the number of days to keep entries in the schedule log (dsmsched.log) and the web client log (dsmwebcl.log), and whether to save the pruned entries in another file.

The schedule log (dsmsched.log) is pruned when the scheduler starts and after a scheduled event completes. Pruned entries are written to a file called dsmsched.pru.

The web client log (dsmwebcl.log) is pruned during the initial start of the client acceptor daemon. Pruned entries are written to a file called dsmwebcl.pru.

If you change from log pruning (schedlogretention option) to log wrapping (schedlogmax option), all records in the existing log are copied to the pruned log (dsmsched.pru and dsmwebcl.pru), and the existing logs (dsmsched.log and dsmwebcl.log) are emptied, and logging begins using the new log wrapping criteria.

If you change from log wrapping (schedlogmax option) to log pruning (schedlogretention option), all existing log entries are retained and the log is pruned using the new schedlogretention criteria. Pruned entries are saved in their corresponding *.pru files.

If neither schedlogmax nor schedlogretention is specified, the logs can grow without any limit on their size. You must manually manage the log contents to prevent the log from depleting disk resources. When the log has been created with neither option specified, if you later issue a command and specify the schedlogretention option, the log is pruned using the retention value specified. When the log has been created with neither option specified, if you later issue a command and specify the schedlogmax option, the existing log is treated as if it was a pruned log. That is, the content of the dsmsched.log file is copied to a file called dsmsched.pru, the content of dsmwebcl.log is copied to dsmwebcl.pru, and new log entries are created in both dsmsched.log and dsmwebcl.log, and both files wrap when they reach their maximum size.

Note: If you specify schedlogretention option to create pruned logs, you cannot specify the schedlogmax option. Logs can be pruned or wrapped, but not both.

Supported Clients

This option is valid for all clients.

Options File

AIX operating systems HP-UX operating systems Linux operating systems Oracle Solaris operating systems Mac OS X operating systems Place this option in the dsm.sys file within a server stanza.

Windows operating systems Place this option in the client options file (dsm.opt).

AIX operating systems HP-UX operating systems Linux operating systems Mac OS X operating systems Oracle Solaris operating systems Windows operating systems You can also set this option on the Client preferences > Scheduler tab in the GUI, by selecting Prune old entries and by specifying a value for Prune entries older than. Selecting the Save pruned entries option saves the pruned scheduler log entries in the dsmsched.pru log file. Selecting Save pruned entries also saves web client log entries in the dsmwebcl.pru log file.

Syntax


                      .-N----.  .-D-.   
>>-SCHEDLOGRetention--+------+--+---+--------------------------><
                      '-days-'  '-S-'

Parameters

N or days

Specifies how long to wait before pruning the log.

N: Do not prune the log. This permits the log to grow indefinitely. This is the default.
days: Specifies the number of days to keep log file entries before pruning. The range of values is zero through 9999.

D or S

Specifies whether to save the pruned entries. Use a space or comma to separate this parameter from the previous one.

D: Discards the log entries when pruning the log. This is the default.
S: Saves the log entries when pruning the log.
Pruned entries are copied to the file of pruned entries (dsmsched.pru or dsmsched.pru), which is stored in the same directory as the log.

Examples

Options file:: schedlogretention 30 S
Command line:: -schedlogretention=30,S

This option is valid only on the initial command line. It is not valid in interactive mode.