3.4.5 Estimating the size of the logs output by execution
The number of the jobs except for queueless jobs, event jobs, and custom event jobs executed per days are less than 10,000. You do not need to estimate log size of job execution environment, you can use the default.
If the jobs except for queueless jobs, event jobs, and custom event jobs executed per days exceed 10,000, estimate log size.
Determine both the size and number of log files for each type of log. Then define the values you have estimated using the jajs_config command.
Execute following command and set for environment setting parameter, explained in (1) Environment setting parameters in the log configuration definition for the execution environment of QUEUE jobs and submit jobs, then restart JP1/AJS3.
jajs_config -k definition-key-name "environment setting parameter-name"=definition-contents ["environment setting parameter-name-2"=definition-contents-2]
Only one definition key can be specified in definition-key-name. If you want to set environment setting parameter different in a definition keys, you must execute the jajs_config command for each definition key.
- Supplementary notes
-
-
If you set more than one environment setting parameter different in definition key at the same time, you can use jbssetcnf command. For details about jbssetcnf command, see the explanation for jbssetcnf command in the JP1/Base User's Guide.
-
If you use jajs_config command, environment setting parameter name and definition are checked, but if you use jbssetcnf command, they do not be checked. We recommend using the jajs_config command to prevent the wrong contents being set.
-
Estimate the environment setting parameter as which a definition key can be set every scheduler service by the number of the jobs except for queueless jobs, event jobs, and custom event jobs by each scheduler service.
The following explains the environment setting parameters that you set in the log configuration definition file for the execution environment, and gives a rough guide to the log sizes you will need to set.
For details about the default disk space requirements and maximum disk space used, see 1.2.5 List of log files and directories in the manual JP1/Automatic Job Management System 3 Troubleshooting.
- Organization of this subsection
(1) Environment setting parameters in the log configuration definition for the execution environment of QUEUE jobs and submit jobs
The following table lists the environment setting parameters.
|
Log file name |
Definition key |
Environment setting parameter |
Definition contents |
|---|---|---|---|
|
Job execution manager log jpqmanexec{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15}.log#1 |
In scheduler service (common): [{JP1_DEFAULT|logical-host-name}\JP1AJS2\SCHEDULER\QUEUE\MANAGER\Log] In scheduler service (different): [{JP1_DEFAULT|logical-host-name}\JP1AJSMANAGER\scheduler-service-name\QUEUE\MANAGER\Log] In submit jobs: [{JP1_DEFAULT|logical-host-name}\JP1NBQMANAGER\Log] |
"ExecLogFileSize"=dword:size "ExecLogFileCount"=dword:number-of-files |
size Specify the log file size in kilobytes. You can set 200 to 8,000 (in decimal form, 512 to 32,768). number-of-files Specify the number of log files before log records are wrapped around to the first file again. You can set 2 to 10 (in decimal form, 2 to 16). |
|
Job execution agent log jpqagtexec{1|2|3|4|5|6|7|8}.log#2 jpqagtexeccld{1|2|3|4|5|6|7|8}.log jpqagtexecdmn{1|2|3|4|5|6|7|8}.log jpqagtexecmon{1|2|3|4|5|6|7|8}.log#3 |
[{JP1_DEFAULT|logical-host-name}\JP1NBQAGENT\Log] |
"ExecLogFileSize"=dword:size "ExecLogFileCount"=dword:number-of-files |
size Specify the log file size in kilobytes. You can set 200 to 8,000 (in decimal form, 512 to 32,768). number-of-files Specify the number of log files before log records are wrapped around to the first file again. You can set 2 to 10 (in decimal form, 2 to 16). |
|
Job execution internal log jpqagt_{00|01|02|03|04|05|06|07}.log jpqmon_{00|01|02|03|04|05|06|07}.log jpqnjpagt_{00|01|02|03|04|05|06|07}.log |
[{JP1_DEFAULT|logical-host-name}\JP1NBQAGENT\Log] |
"TraceLogFileSize"=dword:size "TraceLogFileCount"=dword:number-of-files |
size Specify the log file size in kilobytes. You can set 200 to 1,000 (in decimal form, 512 to 4,096). number-of-files Specify the number of log files before log records are wrapped around to the first file again. You can set 2 to 100 (in decimal form, 2 to 256). |
|
Job execution internal log jpqnjpdata_{00|01}.log |
"extTraceLogFileSize"=dword:size "extTraceLogFileCount"=dword:number-of-files |
||
|
Job execution internal log jpqclient_{00|01|02|03|04|05|06|07|08|09}.log jpqclientnjp_{00|01|02|03|04|05|06|07|08|09}.log |
[{JP1_DEFAULT|logical-host-name}\JP1NBQCLIENT\Log] |
"TraceLogFileSize"=dword:size "TraceLogFileCount"=dword:number-of-files |
size Specify the log file size in kilobytes. You can set 200 to 1,000 (in decimal form, 512 to 4,096). number-of-files Specify the number of log files before log records are wrapped around to the first file again. You can set 2 to 100 (in decimal form, 2 to 256). |
|
Job execution internal log jpqnjpdata_{00|01}.log |
"extTraceLogFileSize"=dword:size "extTraceLogFileCount"=dword:number-of-files |
||
|
Job execution internal log jpqman_{00|01|02|03}.log jpqmandb_{00|01|02|03}.log jpqmannjp_{00|01|02|03}.log |
In scheduler service (common): [{JP1_DEFAULT|logical-host-name}\JP1AJS2\SCHEDULER\QUEUE\MANAGER\Log] In scheduler service (different): [{JP1_DEFAULT|logical-host-name}\JP1AJSMANAGER\scheduler-service-name\QUEUE\MANAGER\Log] In submit jobs: [{JP1_DEFAULT|logical-host-name}\JP1NBQMANAGER\Log] |
"TraceLogFileSize"=dword:size "TraceLogFileCount"=dword:number-of-files |
size Specify the log file size in kilobytes. You can set 200 to 1,000 (in decimal form, 512 to 4,096). number-of-files Specify the number of log files before log records are wrapped around to the first file again. You can set 2 to 100 (in decimal form, 2 to 256). |
|
Job execution internal log jpqnjpdata_{00|01}.log |
"extTraceLogFileSize"=dword:size "extTraceLogFileCount"=dword:number-of-files |
||
|
Job execution internal log jpqnotify_{00|01}.log jpqnotifynjp_{00|01}.log |
In scheduler service (common): [{JP1_DEFAULT|logical-host-name}\JP1AJS2\SCHEDULER\QUEUE\NOTIFY\Log] In scheduler service (different): [{JP1_DEFAULT|logical-host-name}\JP1AJSMANAGER\scheduler-service-name\QUEUE\NOTIFY\Log] |
"TraceLogFileSize"=dword:size "TraceLogFileCount"=dword:number-of-files |
size Specify the log file size in kilobytes. You can set 200 to 1,000 (in decimal form, 512 to 4,096). number-of-files Specify the number of log files before log records are wrapped around to the first file again. You can set 2 to 100 (in decimal form, 2 to 256). |
|
Job execution internal log jpqnjpdata_{00|01}.log |
"extTraceLogFileSize"=dword:size "extTraceLogFileCount"=dword:number-of-files |
||
|
Job execution client log jpqcliexec{1|2}.log#4 |
[{JP1_DEFAULT|logical-host-name}\JP1NBQCLIENT\Log] |
"ExecLogFileSize"=dword:size "ExecLogFileCount"=dword:number-of-files |
size Specify the log file size in kilobytes. You can set 200 to 8,000 (in decimal form, 512 to 32,768). number-of-files Specify the number of log files before log records are wrapped around to the first file again. You can set 2 to 10 (in decimal form, 2 to 16). |
|
Job execution status report log jpqnfyexec{1|2}.log |
In scheduler service (common): [{JP1_DEFAULT|logical-host-name}\JP1AJS2\SCHEDULER\QUEUE\NOTIFY\Log] In scheduler service (different): [{JP1_DEFAULT|logical-host-name}\JP1AJSMANAGER\scheduler-service-name\QUEUE\NOTIFY\Log] |
"ExecLogFileSize"=dword:size"ExecLogFileCount"=dword:number-of-files |
size Specify the log file size in kilobytes. You can set 200 to 8,000 (in decimal form, 512 to 32,768). number-of-files Specify the number of log files before log records are wrapped around to the first file again. You can set 2 to 10 (in decimal form, 2 to 16). |
- #1
-
In a cluster system in Windows, the name of the job execution manager log file varies as follows depending on how JP1/AJS3 is installed:
- If JP1/AJS3 09-00 or later is installed as a new installation:
-
jpqmanexec{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15}.log
- If JP1/AJS3 is installed as an upgrade installation from JP1/AJS2:
-
If logical hosts have been configured before the upgrade installation, the file names used with JP1/AJS2 are inherited as the log file names in the cluster system.
jpqExecLog_man{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15}.log
- #2
-
In a cluster system in Windows, the name of the job execution manager log file varies as follows depending on how JP1/AJS3 is installed:
- If JP1/AJS3 09-00 or later is installed as a new installation:
-
jpqagtexec{1|2|3|4|5|6|7|8}.log
- If JP1/AJS3 is installed as an upgrade installation from JP1/AJS2:
-
If logical hosts have been configured before the upgrade installation, the file names used with JP1/AJS2 are inherited as the log file names in the cluster system.
jpqExecLog_agt{1|2|3|4|5|6|7|8}.log
- #3
-
In a cluster system in Windows, the name of the job execution manager log file varies as follows depending on how JP1/AJS3 is installed:
- If JP1/AJS3 09-00 or later is installed as a new installation:
-
jpqagtexecmon{1|2|3|4|5|6|7|8}.log
- If JP1/AJS3 is installed as an upgrade installation from JP1/AJS2:
-
If logical hosts have been configured before the upgrade installation, the file names used with JP1/AJS2 are inherited as the log file names in the cluster system.
jpqExecLog_agtmon{1|2|3|4|5|6|7|8}.log
- #4
-
In a cluster system in Windows, the name of the job execution manager log file varies as follows depending on how JP1/AJS3 is installed:
- If JP1/AJS3 09-00 or later is installed as a new installation:
-
jpqcliexec{1|2}.log
- If JP1/AJS3 is installed as an upgrade installation from JP1/AJS2:
-
If logical hosts have been configured before the upgrade installation, the file names used with JP1/AJS2 are inherited as the log file names in the cluster system.
jpqExecLog_cli{1|2}.log
The logs output in the execution environment are output to the following paths:
- In Windows, if the installation folder is the default installation folder or is in a folder protected by the system:
-
%ALLUSERSPROFILE\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\log
The default %ALLUSERSPROFILE% value is system-drive\ProgramData.
A folder protected by the system is the path to a folder in any of the following:
- system-drive\Windows
- system-drive\Program Files
- system-drive\Program Files (x86)
- In Windows, if the installation folder is other than the above:
-
JP1/AJS3-installation-folder\log
- In UNIX:
-
/var/opt/jp1ajs2/log
For details about the types of logs, see 1.2.5 List of log files and directories in the manual JP1/Automatic Job Management System 3 Troubleshooting.
(2) Guide to the size of the logs output in the execution environment for QUEUE jobs and submit jobs
The following table gives a rough guide to the log sizes to set. These sizes might vary, depending on your system environment.
|
Log file name |
Log size output per job (bytes) |
Log size output per 10,000 jobs (bytes) |
Calculation of the number of log files required to execute 10,000 jobs#1 |
Log capacity required to execute 10,000 jobs |
|---|---|---|---|---|
|
jpqmanexec{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15}.log#2, #3 |
400 |
3,997,696 |
4,800 KB / 1,024 KB |
1,024 KB x 5 files |
|
jpqagtexec{1|2|3|4|5|6|7|8}.log#4 |
277 |
2,768,896 |
3,300 KB / 512 KB |
512 KB x 7 files |
|
jpqagtexeccld{1|2|3|4|5|6|7|8}.log |
2 |
16,384 |
20 KB / 512 KB |
512 KB x 1 file |
|
jpqagtexecdmn{1|2|3|4|5|6|7|8}.log |
2 |
16,384 |
20 KB / 512 KB |
512 KB x 1 file |
|
jpqagtexecmon{1|2|3|4|5|6|7|8}.log#5 |
2 |
16,384 |
20 KB / 512 KB |
512 KB x 1 file |
|
jpqagt_{00|01|02|03|04|05|06|07}.log |
330 |
3,302,400 |
4,000 KB / 512 KB |
512 KB x 8 files |
|
jpqmon_{00|01|02|03|04|05|06|07}.log |
2 |
16,384 |
20 KB / 512 KB |
512 KB x 1 file |
|
jpqnjpagt_{00|01|02|03|04|05|06|07}.log |
2 |
16,384 |
20 KB / 512 KB |
512 KB x 1 file |
|
jpqnjpdata_{00|01}.log |
2 |
16,384 |
20 KB / 512 KB |
512 KB x 1 file |
|
jpqclient_{00|01|02|03|04|05|06|07|08|09}.log |
2,000 |
20,000,000 |
23,500 KB / 1,024 KB |
1,024 KB x 23 files |
|
jpqclientnjp_{00|01|02|03|04|05|06|07|08|09}.log |
2 |
16,384 |
20 KB / 1,024 KB |
1,024 KB x 1 file |
|
jpqnjpdata_{00|01}.log |
2 |
16,384 |
20 KB / 512 KB |
512 KB x 1 file |
|
jpqman_{00|01|02|03}.log#2 |
400 |
4,000,000 |
4,700 KB / 512 KB |
512 KB x 10 file |
|
jpqmandb_{00|01|02|03}.log#2 |
2 |
16,384 |
20 KB / 512 KB |
512 KB x 1 file |
|
jpqmannjp_{00|01|02|03}.log#2 |
500 |
5,000,000 |
5,900 KB / 512 KB |
512 KB x 12 files |
|
jpqnjpdata_{00|01}.log |
2 |
16,384 |
20 KB / 512 KB |
512 KB x 1 file |
|
jpqnotify_{00|01}.log#2 |
2 |
16,384 |
20 KB / 512 KB |
512 KB x 1 file |
|
jpqnotifynjp_{00|01}.log#2 |
130 |
1,300,000 |
1,600 KB / 512 KB |
512 KB x 4 files |
|
jpqnjpdata_{00|01}.log#2 |
2 |
16,384 |
20 KB / 512 KB |
512 KB x 1 file |
|
jpqcliexec{1|2}.log#6 |
2 |
16,384 |
20 KB / 512 KB |
512 KB x 1 file |
|
jpqnfyexec{1|2}.log |
2 |
16,384 |
20 KB / 512 KB |
512 KB x 1 file |
- #1
-
Calculate a value with some leeway.
- #2
-
This is not used with JP1/AJS3 - Agent, so no increase is necessary.
- #3
-
In a cluster system in Windows, the name of the job execution manager log file varies as follows depending on how JP1/AJS3 is installed:
- If JP1/AJS3 09-00 or later is installed as a new installation:
-
jpqmanexec{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15}.log
- If JP1/AJS3 is installed as an upgrade installation from JP1/AJS2:
-
If logical hosts have been configured before the upgrade installation, the file names used with JP1/AJS2 are inherited as the log file names in the cluster system.
jpqExecLog_man{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15}.log
- #4
-
In a cluster system in Windows, the name of the job execution manager log file varies as follows depending on how JP1/AJS3 is installed:
- If JP1/AJS3 09-00 or later is installed as a new installation:
-
jpqagtexec{1|2|3|4|5|6|7|8}.log
- If JP1/AJS3 is installed as an upgrade installation from JP1/AJS2:
-
If logical hosts have been configured before the upgrade installation, the file names used with JP1/AJS2 are inherited as the log file names in the cluster system.
jpqExecLog_agt{1|2|3|4|5|6|7|8}.log
- #5
-
In a cluster system in Windows, the name of the job execution manager log file varies as follows depending on how JP1/AJS3 is installed:
- If JP1/AJS3 09-00 or later is installed as a new installation:
-
jpqagtexecmon{1|2|3|4|5|6|7|8}.log
- If JP1/AJS3 is installed as an upgrade installation from JP1/AJS2:
-
If logical hosts have been configured before the upgrade installation, the file names used with JP1/AJS2 are inherited as the log file names in the cluster system.
jpqExecLog_agtmon{1|2|3|4|5|6|7|8}.log
- #6
-
In a cluster system in Windows, the name of the job execution manager log file varies as follows depending on how JP1/AJS3 is installed:
- If JP1/AJS3 09-00 or later is installed as a new installation:
-
jpqcliexec{1|2}.log
- If JP1/AJS3 is installed as an upgrade installation from JP1/AJS2:
-
If logical hosts have been configured before the upgrade installation, the file names used with JP1/AJS2 are inherited as the log file names in the cluster system.
jpqExecLog_cli{1|2}.log