3.4.2 Estimating the size of the scheduler trace log file
This subsection explains how to estimate the size of the scheduler trace log file.
There are two types of scheduler trace logs, and the following trace information is output to the log files:
-
Common scheduler trace log
Scheduler trace information about operations and command execution from JP1/AJS3 - View and about monitoring of scheduler service processes
-
Scheduler trace log of each scheduler service
Scheduler trace information about job execution by the scheduler service
Common scheduler trace logs are output to the file specified in the TRACELOGFILE environment setting parameter.
The file to which the scheduler trace log of each scheduler service varies depending on the setting of the TRACELOGDIV environment setting parameter.
-
When yes is set for the TRACELOGDIV environment setting parameter
The scheduler trace log of each scheduler service is output to the file tracelog_scheduler-service-name under the directory specified in the TRACEDIVDIR environment setting parameter.
-
When no is set for the TRACELOGDIV environment setting parameter
The scheduler trace log of each scheduler service is output together with common scheduler trace logs to the file specified in the TRACELOGFILE environment setting parameter.
For details about this environment parameter, see 20.4 Setting up the scheduler service environment in the JP1/Automatic Job Management System 3 Configuration Guide.
By default, the size of each scheduler trace log file is set to 20 megabytes (20,480 kilobytes). This size of file can store the trace logs for the execution of about 2,000 jobs.
The required size of a scheduler trace log file is largely different depending on the jobnet structure, number of connections to JP1/AJS3 - View, and operation details. Also the log output destination varies depending on the setting of the TRACELOGDIV environment setting parameter. Estimate the required size of each scheduler trace log file as described next, and increase the size as needed.
Note that you can increase the size of the scheduler trace log file with the ajstrsetsz command. For details, see ajstrsetsz in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.
- Organization of this subsection
(1) When yes is set for the TRACELOGDIV environment setting parameter
If yes is set for the TRACELOGDIV environment setting parameter, estimate the file size as follows:
-
Common scheduler trace log
Appropriate trace log file capacity (units: kilobytes) = 3,072 x (number-of-jobs-executed-per-day#1 / 1,000) x number-of-scheduler-services x 1.5 x number-of-days-to-save-trace-logs#2
-
Scheduler trace log of each scheduler service (per scheduler service)#3
Appropriate trace log file capacity (units: kilobytes) = 3,072 x number-of-jobs-executed-per-day / 500 x 1.5 x number-of-days-to-save-trace-logs#2
- #1
-
Refers to operations performed on units by commands or from JP1/AJS3 - View.
- #2
-
Specify the number of days from the occurrence of the error to the collection of data.
- #3
-
Estimate the file size for each scheduler service.
- Example: Saving the trace log for one day (only for a physical host with one scheduler service)
-
-
3,000 jobs are executed per day.
-
500 hold-release and other commands are executed per day.
- Appropriate trace log file capacity (size of the file specified in the TRACELOGFILE environment setting parameter)
-
3,072 x ( 500 / 1,000) x 1 x 1.5 x 1 = 2,304 kilobytes
- Appropriate trace log file capacity (size of the file created under the directory specified in the TRACELOGDIVDIR environment setting parameter)
-
3,072 x 3,000 / 500 x 1.5 x 1 = 27,648 kilobytes
-
(2) When no is set for the TRACELOGDIV environment setting parameter
The appropriate capacity of trace log file is the sum of the size estimated for the common scheduler trace log and the size estimated for the scheduler trace log of each scheduler service. The two estimations are described in (1) When yes is set for the TRACELOGDIV environment setting parameter.
- Example: Saving the trace log for one day (only for a physical host with one scheduler service)
-
-
3,000 jobs are executed per day.
-
500 hold-release and other commands are executed per day.
- Common scheduler trace log:
-
3,072 x (500 / 1,000) x 1 x 1.5 x 1 = 2,304 kilobytes
Scheduler trace log of each scheduler service:
-
3,072 x 3,000 / 500 x 1.5 x 1 = 27,648 kilobytes
- Appropriate capacity of the trace log file (size of the file specified in the TRACELOGFILE environment setting parameter):
-
2,304 + 27,648 = 29,952 kilobytes
-