Hitachi

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


3.4.4 Estimating the size of log files for JP1/AJS3 - View

This subsection explains how to estimate the size of log files that are output by JP1/AJS3 - View.

The following log files for JP1/AJS3 - View are explained here:

The required log file size depends on the trace level, operation details, and errors. The following tables show the guidelines for estimating the log file size when the trace level is 3 (default).

Add one megabyte for estimation because re-connections might be required when JP1/AJS3 - Manager is disconnected or more operations might fail than you expect.

Table 3‒26: Estimating the log file size for JP1/AJS3 - View

Item

Log size (units: kilobytes)

Starting JP1/AJS3 - View

10

Ending JP1/AJS3 - View

10

Table 3‒27: Estimating the log file size for windows (common)

Item

Log size (units: kilobytes)

Operations#

3 x n

Operation failures

4 x m

Legend:

n: Number of operations

m: Number of operation failures

#

Indicates menu operations and closing or opening dialog boxes. Operations also include the creation of new units and changing of icon positions in the Jobnet Editor window.

When you operate multiple units simultaneously, estimate the log file size in the same manner you estimate the log file size when you operate units individually.

Table 3‒28: Estimating the log file size for each window

Window

Log size per operation (units: kilobytes)

View

Refresh

Automatic update

Selecting a tree node#1

JP1/AJS3 - View (Main window)

3 + 2 x a

2

2

2

JP1/AJS3 - View (Summary Monitor window)

5 x b

5 x b

5 x b

--

Jobnet Editor

4 + 0.5 x (c - 1 ) +5 x a

2

--

5

Jobnet Monitor

5 + 0.5 x (c - 1) + 4 x a

3 + 0.5 x d + 0.5 x e

1 + 0.5 x d + 0.5 x e

4

Monthly Schedule

5 + 0.5 x (c - 1) + f

2 + f

--

1

Daily Schedule#2

4 + 0.5 x (c - 1) + f

2 + f

2 + f

1

Calendar#3

5

3

--

--

Search

0.5

--

--

--

Legend:
a:

Number of the hierarchy level of the first unit to be selected in the tree area in the displayed window

The level of the root is 0.

b:

Number of units to be monitored

c:

Number of the hierarchy level of the unit for which the window is displayed

d:

Number of Monitor Details dialog boxes to be displayed

e:

Number of Execution Result Details dialog boxes to be displayed

f:

Number of target root jobnets, or the number of root jobnets immediately under the target job group when 1 is displayed for the root jobnet

--:

Not applicable

#1

Indicates the selection or expansion of a unit in the tree area.

#2

Indicates the Daily Schedule (Hierarchy) window or the Daily Schedule (All Jobs) window.

#3

Indicates the Edit Monthly Calendar window or the Edit Annual Calendar window.

Examples:

To estimate the log file size required to keep a one-week log, use the following conditions:

  • The period that JP1/AJS3 - View runs to monitor tasks is one week.

  • The JP1/AJS3 - View window is automatically update every 300 seconds.

  • The Daily Schedule (Hierarchy) window for the job groups (including 10 root jobnets below) in the root job group is displayed and automatically updated every 300 seconds.

  • One operation is performed per hour.

  • The rate of operation failure is 0.1.

The required log file size is as follows:

  • For starting or ending JP1/AJS3 - View

    20 kilobytes

  • For menu operations

    3 x 24 x 7 = 504 kilobytes

  • For operation failures

    4 x 24 x 7 / 10 = 68 kilobytes

  • For displaying the JP1/AJS3 - View window

    3 kilobytes

  • For automatic update in the JP1/AJS3 - View window

    2 x 3,600 x 24 x 7 / 300 = 4,032

  • For displaying the Daily Schedule (Hierarchy) window

    4 + 0.5 x (1 - 1) + 10 = 14

  • For automatic update in the Daily Schedule (Hierarchy) window

    (2 + 10) x 3,600 x 24 x 7 / 300 = 24,192

  • Total

    20 + 504 + 68 + 3 + 4,032 + 14 + 24,192 = 28,833 (kilobytes) = 28.1 (megabytes)

When you round the above number and add 1 megabyte for leeway, the result is 30 megabytes.