Schedlogmax

This option causes the log files that get created for scheduler events (dsmsched.log) and web client events (dsmwebcl.log) to wrap around when they reach their maximum size. As scheduler and web client events are logged, log records are added to the end of the log files until the maximum specified size is reached. When the maximum specified size is reached, a log record saying Continued at beginning of file is placed as the last record in the file. Subsequent logging is resumed at the beginning of the file. The end of the wrapped log is indicated by a record saying END OF DATA.

When you set the schedlogmax option, scheduler and web client log messages are not saved in a prune file. If you want to prune logs and save the pruned log entries to another file, see the schedlogretention option.

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.

If you change from log pruning (schedlogretention option) to log wrapping (schedlogmax option), all records in the existing logs are copied to a file containing the pruned entries. For example, log records pruned from the dsmsched.log file are copied to dsmsched.pru. Log records pruned from dsmwebcl.log are copied to dsmweblog.pru. The existing logs (dsmsched.log and dsmwebcl.log) are emptied, and logging begins using the new log wrapping criteria.

If you simply change the value of the schedlogmax option, the existing log is extended or shortened to accommodate the new size. If the value is reduced, the oldest entries are deleted to reduce the file to the new size.

If neither schedlogmax nor schedlogretention is specified, the error log can grow without any limit on its 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 a file called dsmwebcl.pru, and new log entries are created in dsmsched.log and dsmwebcl.log, and both files wrap when they reach their maximum size.

LOGHEADERREC 661  104857600 IBM Spectrum Protect 8.1.0.0 Fri Dec 9 06:46:53 2014

Note that the dates and time stamps in the LOGHEADERREC text are not translated or formatted using the settings specified on the dateformat or timeformat options.

Supported Clients

This option is valid for all clients.

Options File

Place this option in the client system-options file (dsm.sys) within a server stanza.

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

You can also set this option on the Client Preferences > Scheduler tab in the GUI, by selecting Enable scheduler log file wrapping and by specifying a non-zero maximum size for the log file. To prevent log file wrapping, set the maximum size to zero. When the maximum wrapping is set to zero, clearing or setting the Enable scheduler log file wrapping option has no effect; log wrapping does not occur if the maximum size is set to zero.

Parameters

size

Specifies the maximum size, in megabytes, for the log file. The range of values is 0 to 2047; the default is 0, which disables log file wrapping and allows the log file to grow indefinitely.