4.9 Function for automatically re-organizing the command execution log file
If an unexpected forced system termination or a power outage occurs while command execution logs are being written into the command execution log file that is used by the JP1/Base command execution function, the command execution log file might become corrupted.
The function for automatically re-organizing the command execution log file enables you to repair the command execution log file or detect file corruption at an early stage when you restart JP1/Base after an unexpected forced system termination. The initial setting is that this function is enabled.
The amount of time required for JP1/Base startup might increase depending on the size of the command execution log file. If the amount of startup time becomes an operation issue, consider either decreasing the number of records in the command execution log file or disabling the automatic re-organization function.
The amount of time required for automatically re-organizing the command execution log file can be estimated based on the sum of the amounts of the execution time of the commands below. Execution time becomes longer in proportion to the file size.
- Command execution example
-
Stop JP1/Base before executing the following commands.
- For Windows:
Jiscond installation-folder\log\COMMAND\ACTISAMLOGV8 Jiscond installation-folder\log\COMMAND\CMDISAMLOGV8
- For UNIX:
/opt/jp1base/bin/Jiscond /var/opt/jp1base/log/COMMAND/actisamlogv8 /opt/jp1base/bin/Jiscond /var/opt/jp1base/log/COMMAND/cmdisamlogv8
The procedure for disabling this function is as follows:
-
Rename or delete jp1bs_spmd_pre.conf.#
-
Restart JP1/Base and all products that use JP1/Base.
The function is disabled.
- #
-
jp1bs_spmd_pre.conf is stored in the following directory:
- In Windows:
installation-folder\conf\ shared-folder\jp1base\conf\ (applicable to cluster use)
- In UNIX:
/etc/opt/jp1base/conf/ shared-directory/jp1base/conf/ (applicable to cluster use)
- Note:
-
On Windows, a locked file or record in the ISAM database may remain locked when a service ends abnormally. Unlock the file or record using the Jislckfree command.