Interstage Shunsaku Data Manager Operator's Guide - Microsoft(R) Windows(R) 2000/ Microsoft(R) Windows Server(TM) 2003 - - UNIX - |
Contents
Index
![]() ![]() |
Appendix A Execution Parameters in Environment Files | > A.5 Searcher Environment Files |
This section explains the meaning of the searcher environment execution file.
This parameter specifies the absolute path of the directory for storing error messages output by the searcher, and the files to which notification information is output.
The files below will be created under this directory and the log file will switch according to the value specified at the LogFileSwitch parameter. This cycle will continue for the same number as specified in the LogFileBackup parameter. In addition, during the operation, the file also switch when the file size is more than the value specified at the LogFileSize parameter.
If LogFileSwitch parameter is not specified
If LogFileSwitch parameter is specified
The file will be overwritten if the searcher identifier_generation number_old.log has already existed.
Refer to the notes for the LogFileFolder parameter in the conductor environment file for more information on how to set up the access privileges to this folder.
This parameter specifies the size at which the searcher log file will switch over. Specify a value between 0 and 500 inclusive. The unit of the number is megabyte.
If this parameter is omitted, it defaults to 100.
If 0 is specified, the log will not be collected.
This parameter specifies the number of searcher backup log file.
The log file currently in use is not counted in the number of backup file.
Specify a value between 1 and 100 inclusive.If 0 is specified, the backup file will not be created and only the file currently in use exists. The file before switch will be deleted after switching the file.
This parameter specifies the number of days at which the searcher log file will switch over.
Specify a value between 1 and 100 inclusive.
If 0 is specified, the log file will be switch according to the file size specified at the LogFileSize parameter. If 1 or more is specified, the file will be switched at 0 am during the operation or when the process starts and the date of the last log file that has been switched is different.
However, if the file size has exceeded the size specified at the LogFileSize parameter, the file will be switched regardless of the specified number of days.
If this parameter is omitted, it defaults to 0.
The name of the searcher log file is as follows:
Searcher identifier_0_YYYYMMDDhhmm.log: The log file currently in use
searcher identifier_1_old_YYYYMMDDhhmm.log: One generation before the current log file
searcher identifier_2_old_YYYYMMDDhhmm.log: : Two generations before the current log file
The time when the log file has switched will be displayed as YYYYMMDDhhmm (YYYY: Year, MM: Month, DD: Day, hh: Hour, mm: Minute)
Example 1
Specify "LogFileBackup: 2", "LogFileSwitch: 1"
The following log file name will be displayed when start the Shunsaku system after 0 am in 22 April, 2006.
shuns01_0_200604211235.log
Rename the file currently in use, and then create the backup file that contains data up to 22 April, 2006.
shuns01_0_200604220000.log shuns01_1_old_200604211235.log
If start Shunsaku system after 0 am in 23 April, 2006, the file name will be as follows:
shuns01_0_200604230000.log shuns01_1_old_200604220000.log shuns01_2_old_200604211235.log
If start Shunsaku system after 0 am in 24 April, 2006, the number of backup file is more than 2, therefore, the oldest file will be deleted as follows:
shuns01_0_200604240000.log shuns01_1_old_200604230000.log shuns01_2_old_200604220000.log
Example 2
If the file size has exceeded the size specified in the LogFileSize parameter, the file name will be as follows:
shuns01_0_200604230000.log
If the log file has been switched because the file size has exceeded the size specified in the LogFileSize parameter, the file name will be switch to the name below after the schedule is passed (23 April,2006 0:34 am)
shuns01_0_200604231234.log shuns01_1_old_200604230000.log
Example 3
If the LogFileSwitch parameter is not used, the file name will be switched as follows:
shuns01.log
If the file size has exceeded the value specified in LogFileSize parameter, the generation number will be added.
shuns01.log shuns01_1_old.log
This parameter specifies the storage directory of the searcher performance log file in absolute path.
The files below will be created under this directory and the log file will switch according to the value specified at the PfmFileSwitch parameter. This cycle will continue for the same number as specified in the PfmFileBackup parameter.
In addition, the file will be switched when the size of the file using is over the size specified at the PfmFileSize parameter.
If the PfmFileSwitch parameter is not specified
If the PfmFileSwitch parameter is specified
The file will be overwritten if the searcher identifier_pfm _generation number_old.log has already existed.
This parameter specifies the size at which the searcher performance log file will switch over.
Specify a value between 1 and 500 inclusive. The unit of the number is megabyte.
If this parameter is omitted, it defaults to 100.
If 0 is specified, the performance log will not be collected.
This parameter specifies the number of searcher backup performance log file.
The performance log file currently in use is not counted in the number of backup file.
Specify a value between 1 and 100 inclusive. If 0 is specified, the backup file will not be created and only the file currently in use exists. The file before switch will be deleted after switching the file.
The file before switching will be deleted after switching the file.
If the number of backup performance log file exceeds the value specified in this parameter, the oldest backup file will be deleted.
If this parameter is omitted, the system will hold only the first generation backup file.
This parameter specifies the number of days at which the searcher performance log file will switch over.
Specify a value between 1 and 100 inclusive. If 0 is specified, the log file will be switch according to the file size specified at the PfmFileSize parameter. If 1 or more is specified, the file will be switched at 0 am during the operation or when the process starts and the date of the last performance log file that has been switched is different.
However, if the file size has exceeded the size specified at the LogFileSize parameter, the file will be switched regardless of the specified number of days.
If this parameter is omitted, it defaults to 0.
The name of the searcher performance log file is as follows:
Searcher identifier_pfm_0_YYYYMMDDhhmm.log: : The performance log file currently in use
searcher identifier_pfm_1_old_YYYYMMDDhhmm.log: One generation before the current performance log file
searcher identifier_pfm_2_old_YYYYMMDDhhmm.log: Two generations before the current performance log file
The time when the performance log file has switched will be displayed as YYYYMMDDhhmm (YYYY: Year, MM: Month, DD: Day, hh: Hour, mm: Minute)
This parameter specifies the absolute path of the directory where the core file will be output if an abnormality occurs with the searcher.
The size of the core file that is output is the same as the amount of memory that the searcher uses.
This parameter is mandatory.
Refer to the notes for the LogFileFolder parameter in the conductor environment file for more information on how to set up the access privileges to this folder.
This parameter specifies the Shunsaku system name.
This parameter must be specified if the startup commands for V6.0 and earlier shuncstart, shundstart, shunsstart, and shunostart) are used.
If this parameter is omitted, the startup commands for V6.0 and earlier (shuncstart, shundstart, shunsstart, and shunostart) cannot be used.
This parameter does not need to be specified if only the V8.0 startup command (shunsysstart) is used.
Contents
Index
![]() ![]() |