Automatically rotating operation log files

This function automatically saves the output contents as a backup file when the File Access Log file or the Command Execution Log file reaches a certain size. As a result, you can suppress the disk utilization of the operation log so as not to exceed a certain amount, or save the operation log on a log server at regular intervals.

You can specify the automatic rotation of the Operation Log files with Operation Log Rotation Size (oplchangesize) and Operation Log Generations (oplgenerationcount) in the System Environment Settings.

When the operation log is output, if the file size exceeds the setting of Operation Log Rotation Size, the original file is renamed and backed up, and a new output file is created. The backup file is created in the same directory as the output destination of the operation log. The backup file is saved until the number of files reaches the value specified in Operation Log Generations. If the value is exceeded, the backup file is overwritten in order of generational management number, starting at 0001.

The backup file names are shown below.

File Access Log file

huloplfile_bk_nnnn.csv

Command Execution Log file

huloplcmd_bk_nnnn.csv

nnnn is the generational management number (four digits, ranging from 0001 to 9999).

Figure 2.42 Automatic Rotation of Operation Log Files

1) Size check

Check the file size before outputting the operation log. Output the operation log as it is and end the processing, when the file size does not exceed the setting in Operation Log Rotation Size.

2) Rotation

Rename and back up the Operation Log file, when the file size exceeds the setting in Operation Log Rotation Size.

3) Outputting the operation log

Create a fresh operation log file, and output the operation log.

4) Exceeding the number of generations

When the number of backup files exceeds the setting in Operation Log Generations, backup files are overwritten in order of generational management number, starting at 0001.