Job Management Partner 1/Performance Management - Agent Option for Virtual Machine Description, User's Guide and Reference

Appendix I.2 Format for saving action logs

This subsection explains the file format for saving action logs.

Action logs are output to the specified file (current output file), and an action log file that becomes full is saved as a different file (shift file). The flow for switching action log files follows.

1. Action logs are sequentially output to the current output file jpcaudit.log.
2. When the current output file becomes full, the action logs in it are saved in a shift file.
   The shift file name consists of the current output file name with a numerical suffix added to it. Whenever the current output file becomes full, the numerical suffix of the shift file name is incremented by 1. In other words, the larger the numerical suffix, the older the log file.
   

   Example:

   When the current output file jpcaudit.log becomes full, its content is saved in the shift file jpcaudit1.log.

   When the current output file becomes full again, the logs in it are moved to jpcaudit1.log and the existing shift file jpcaudit1.log is renamed jpcaudit2.log.

   When the number of log files exceeds the save limit (specified in the jpccomm.ini file), the oldest log file is deleted.
   
3. The current output file is initialized and new action logs are written into it.

To specify whether to output action logs, their output destination, and the number of logs that can be saved, use the jpccomm.ini file. For details about how to set up the jpccomm.ini file, see I.4 Settings for outputting action logs.

[Contents][Back][Next]

All Rights Reserved. Copyright (C) 2009, 2010, Hitachi, Ltd.