H.2 Format for saving action log files
Action log data is output to a default file (the current output file). When the log file becomes full, it is then saved as a separate file (a shift file). The following describes the manner in which switching takes place between these files.
-
Action log data is output sequentially to the current output file jpcaudit.log.
-
When the current output file becomes full, the action log data in the file is saved to a shift file.
Shift files have the same name as the current output file, but with a number appended onto the end of them. When a new shift file is created, the number on the end of the shift file names are all increased by one. Essentially, the higher the number, the older the file is.
- Example:
-
When the current output file jpcaudit.log becomes full, its contents are stored in a shift file jpcaudit1.log.
When the current output file fills again, its logs are shifted to the file jpcaudit1.log, and the existing shift file jpcaudit1.log is renamed to jpcaudit2.log.
When the number of log files exceeds the maximum specified in the jpccomm.ini file, the oldest log files are deleted first.
-
The current output file is cleared, and the system resumes writing action log data to the file.
The settings that determine whether action logs are output, the location to which the logs are output, and the maximum number of log files that can be made are in the jpccomm.ini file. For details about how to enter these settings in the jpccomm.ini file, see H.4 Settings for outputting action log data.