Hitachi

JP1 Version 12 JP1/Automatic Job Management System 3 System Design (Configuration) Guide


3.4.6 Estimating the size of log files output by a flow control subprocess

A flow control subprocess outputs log files in an environment in which wait conditions are used. You do not need to estimate the log file size for an environment in which wait conditions are not used. For details about using wait conditions, see 6.1.8 Settings for using wait conditions in the JP1/Automatic Job Management System 3 Configuration Guide.

A flow control subprocess outputs two log files for each scheduler service. The default size of one file is 10,240 kilobytes.

The size of log data differs greatly depending on the execution count for units with wait conditions and the number of units whose end is being waited for. You should estimate an appropriate size for the log file so that logs for the number of days from the occurrence of an error to the collection of data can be saved.

Organization of this subsection

(1) Formula for estimating the size of log files output by a flow control subprocess

The following table describes the variables required for estimating the size of log files output by a flow control subprocess.

Table 3‒31: Variables required for estimating the size of log files output by a flow control subprocess

Variable

Description

a

Number of units with wait conditions executed per day#

b

Total number of waits per day

c

Size of the full name of the unit (units: bytes)

d

Number of units executed per day whose end is being waited for#

e

Number of temporary change operations performed for wait conditions per day

f

Number of root jobnets executed per day in a scheduler service that has units with wait conditions#

#

If a unit is executed more than once per day, multiply the value by the execution count.

To estimate the log file size, replace these variables in the following formula with values:

Log file size output by a flow control subprocess (units: kilobytes) =

{300 + (a x 7 + b x 4 + d x 3 + e x 3 + f x 3) x (300 + c x 2)} / 1,024

For logs that are to be kept for more than one day, multiply the estimated log file size by the number of days the logs are to be kept. Because a maximum of two log files are output, if you want to estimate the size for one file, divide the result by two.

(2) Example of estimating the size of log files output by a flow control subprocess

The following describes an example of estimating the size of log files output by a flow control subprocess.

The example uses the following values for the variables required to estimate the size.

Table 3‒32: Variable values required for estimating the size of log files output by a flow control subprocess

Variable

Variable value

Description

a

300

300 units with wait conditions are executed per day (each unit is executed only once).

b

300

Waiting occurs 300 times per day.

c

50

The full unit name is specified with 50 bytes.

d

300

300 units whose ends are being waited for are executed per day (each unit is executed only once).

e

30

The temporary change operation for wait conditions is performed 30 times per day.

f

100

100 root jobnets are executed per day in a scheduler service that has units with wait conditions (each root jobnet is executed only once).

The formula for this example is as follows:

Log file size output by a flow control subprocess (units: kilobytes) =

{300 + (300 x 7 + 300 x 4 + 300 x 3 + 30 x 3 + 100 x 3) x (300 + 50 x 2)} / 1,024

= 1,794 (rounded up)

To keep this log data for ten days, you can estimate the size of one log file as follows:

1,794 x 10 days / 2 = 8,970 (units: kilobytes)

(3) Expanding the size of log files output by a flow control subprocess

If the file size you estimated in (1) Formula for estimating the size of log files output by a flow control subprocess is greater than the default (10,240 kilobytes), you need to increase the log file size. To do so, execute the jajs_config command to set the FLBDLOGSIZE environment setting parameter to a value slightly greater than the estimated value.

For details about the environment setting parameters, see 20.4 Setting up the scheduler service environment in the JP1/Automatic Job Management System 3 Configuration Guide.