7.2.1 Estimating log file sizes
Estimate the size of the JP1/AJS3 log files for queueless jobs. When an error occurs, this log file information is used to investigate what operation or process caused the error. If the required information has not been kept, identifying the cause will take longer. Estimate the size of the log files as exactly as you can, according to how and what sort of job processing your system performs.
When using queueless jobs, estimate the size of the following log files:
-
Queueless log file
-
Queueless trace log file
-
Internal execution log file for queueless jobs
- Organization of this subsection
(1) Estimating the size of the queueless log file
A queueless log file contains log entries output by the queueless jobs executed by an agent. Queueless log files are used primarily to monitor the execution of work tasks.
The disk space required for a queueless log file depends on how many queueless jobs are executed by the agent. Estimate the appropriate log file size and change the default disk space if necessary. For details on the default disk space and maximum disk area used by queueless log files, see 1.2.5 List of log files and directories in the manual JP1/Automatic Job Management System 3 Troubleshooting.
Use the following formula to estimate the size of a queueless log file:
Size of a queueless log file (in bytes) = (60 + length-of-manager-host-name + length-of-scheduler-service-name + length-of-job's-full-name + length-of-agent-host-name) x 2 x number-of-jobs-to-save
For details about increasing the size of the queueless log file, see 3.5.1 Extending trace log files in the JP1/Automatic Job Management System 3 Configuration Guide (for Windows systems) or 13.4.4 Extending trace log files in the JP1/Automatic Job Management System 3 Configuration Guide (for UNIX systems).
(2) Estimating the size of the queueless trace log file
A queueless trace log contains traces output by queueless jobs and by commands related to the queueless job execution control. Queueless trace logs are used primarily to investigate the cause of a problem or to calculate how long a process took.
In the initial state, the queueless trace log file is set as follows.
- Path:
-
- In Windows:
%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\log\tracelog.ql
- In UNIX:
/var/opt/jp1ajs2/log/tracelog.ql
- Size:
-
Large enough for the traces output by approximately 10,000 jobs (specifically, 15 megabytes (15,360 kilobytes)).
Estimate an appropriate size for the trace log file and increase its size as needed. However, when you use only the queueless job manager function, you do not need to estimate the file size.
Use the following formula to estimate the size of a queueless trace log file:
Size of a queueless trace log file (in kilobyte) = 3,072 x (number-of-jobs-executed-from-the-time-a-problem-occurs-until-data-can-be-collected / 2,000)
- Example: Store one day's worth of queueless trace log entries.
-
-
If 12,000 jobs are executed per day
Size of the queueless trace log file = 3,072 x (12,000 / 2,000) = 18,432 kilobytes
-
For details about increasing the size of the queueless trace log file, see 3.5.1(2) Extending the queueless trace log file in the JP1/Automatic Job Management System 3 Configuration Guide (for Windows systems) or 13.4.4(2) Extending the queueless trace log file in the JP1/Automatic Job Management System 3 Configuration Guide (for UNIX systems).
(3) Estimating the size of the internal execution logs for queueless jobs
The internal execution log files for queueless jobs contain traces output by queueless jobs.
In the initial state, the internal execution log files for queueless jobs are set as follows.
- Path
-
- In Windows:
JP1/AJS3-installation-folder\log\ajsqlexeclog#1 JP1/AJS3-installation-folder\log\ajsqlexeclog_ftpd#2
- In UNIX:
/var/opt/jp1ajs2/log/ajsqlexeclog#3 /var/opt/jp1ajs2/log/ajsqlexeclog_ftpd#2
- #1
-
In a cluster configuration, the file name is:
JP1/AJS3-installation-folder\log\ajsqlexeclog-[logical-host-name]
logical-host-name is truncated after the 30th byte if the file name exceeds 255 bytes.
- #2
-
Created in JP1/AJS3 - Manager only.
- #3
-
In a cluster configuration, the file name is:
/var/opt/jp1ajs2/log/ajsqlexeclog-[logical-host-name]
logical-host-name is truncated after the 30th byte if the file name exceeds 255 bytes.
- Size
-
- For the ajsqlexeclog file:
-
Large enough for the internal log output by the queueless agent service for approximately 40,000 jobs (specifically, 24 megabytes (24,576 kilobytes)).
- For the ajsqlexeclog_ftpd file:
-
Large enough for the internal log output by the queueless file transfer service for approximately 20,000 jobs that involve file transfer (specifically, 10 megabytes (10,240 kilobytes)).
The size of an internal execution log for queueless job varies greatly depending on the number of queueless jobs executed, whether file transfer is involved, and other factors. Estimate an appropriate size for the internal log files and increase their size as needed.
Use the following formulae to estimate the size of the internal execution log files for queueless jobs:
Size of the ajsqlexeclog file (in kilobyte) = (number-of-queueless-jobs-executed-over-two-days x 600) / 1,024
Size of the ajsqlexeclog_ftpd file (in kilobyte) = (number-of-queueless-jobs-involving-file-transfer-executed-over-two-days x 500) / 1,024
- Example: Store internal execution log files for queueless jobs when:
-
-
10,000 queueless jobs are executed per day.
-
3,000 of those jobs involve the transmission of transfer files or result files.
Size of the ajsqlexeclog file (in kilobyte) =
((10,000 x 2) x 600) / 1,024 = 11,719 kilobytes
Size of the ajsqlexeclog_ftpd file (in kilobytes) =
((3,000 x 2) x 500) / 1,024 = 2,929 kilobytes
-
For details about increasing the size of the internal execution logs for queueless jobs, see ajsqlexecsetsz in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.