3.4.5 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 and JP1/AJS3 Console View.
- Organization of this subsection
(1) Estimating the size of log files for JP1/AJS3 - View
The following log files for JP1/AJS3 - View are explained here:
-
Storage location
- In Windows 8.1, Windows 8, Windows Server 2012, Windows 7, Windows Server 2008, or Windows Vista:
-
%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\log\ajs2view#nnnn_{1|2}.log#
The default %ALLUSERSPROFILE% value is system-drive\ProgramData.
- In Windows Server 2003 or Windows XP Professional:
-
JP1/AJS3 - View-installation-folder\log\ajs2view#nnnn_{1|2}.log#
- #
-
When you start multiple instances of JP1/AJS3 - View, a value between 0001 and 9999 is assigned to nnnn of #nnnn_. If you do not start multiple instances of JP1/AJS3 - View, #nnnn_ is omitted.
-
Size
You can specify a size from 1 to 512 in megabytes (the default is 1 megabyte).
To change the log file size, open the Preferences dialog box of JP1/AJS3 - View, click the Other tab, and use Max. log file size.
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.
|
Item |
Log size (units: kilobytes) |
|---|---|
|
Starting JP1/AJS3 - View |
10 |
|
Ending JP1/AJS3 - View |
10 |
|
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.
|
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.
-
(2) Estimating the size of log files for JP1/AJS3 Console View
The following log files for JP1/AJS3 Console View are explained here:
-
Storage location
- In Windows 8.1, Windows 8, Windows Server 2012, Windows 7, Windows Server 2008, or Windows Vista:
-
%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\log\ajs2coview#nnnn_{1|2}.log#
The default %ALLUSERSPROFILE% value is system-drive\ProgramData.
- In Windows Server 2003 or Windows XP Professional:
-
JP1/AJS3 - View-installation-folder\log\ajs2coview#nnnn_{1|2}.log#
- #
-
When you start multiple instances of JP1/AJS3 Console View, a value between 0001 and 9999 is assigned to nnnn of #nnnn_. If you do not start multiple instances of JP1/AJS3 Console View, #nnnn_ is omitted.
-
Size
You can specify a size from 1 to 512 in megabytes (the default is 1 megabyte).
To change the log file size, open the Preferences dialog box of JP1/AJS3 Console View, click the Other tab, and use Max. log file size.
The required log file size depends on the trace level, operation details, and errors. The following table shows the guidelines for estimating the log file size when the trace level is 3 (default).
Add one megabyte for estimation because more operations might fail than you expect.
|
Item |
Log size (units: kilobytes) |
|---|---|
|
Starting JP1/AJS3 Console View |
10 |
|
Ending JP1/AJS3 Console View |
10 |
|
Operations#1 |
3 x n |
|
Operation failure |
4 x m |
|
Acquisition of status |
0.5 x |
|
Operation on a monitored object#2 |
5 x n |
|
Connection check#3 |
0.5 x l |
- Legend:
-
![[Figure]](GRAPHICS/SIGMA.GIF)
:
-
Total number of objects in the root business scope
- a:
-
Number of status updates for each root jobnet to be monitored#4
- b:
-
Number of objects in the root business scope
- c:
-
Number of AJS3 unit monitored objects whose status is unknown
- d:
-
Number of times to switch from the definition mode to the monitoring mode and the number of reconnections
- n:
-
Number of operations
- m:
-
Number of operation failures
- l:
-
Number of connection checks = JP1/AJS3 Console View-active-time/connection-check-interval (default: 300 seconds)
- #1
-
Indicates menu operations and opening or closing of dialog boxes. Operations also include the creation of new objects and changing of icon positions in the Main Scope window.
When you operate multiple objects simultaneously, estimate the log file size in the same manner you estimate the log file size when you operate objects individually.
- #2
-
Indicates registration for execution or re-execution for AJS3 unit monitored objects.
- #3
-
Operation automatically performed inside JP1/AJS3 Console View. JP1/AJS3 Console View periodically checks the connection with JP1/AJS3 Console Manager based on the communication option in JP1/AJS3 Console View, KEEP_ALIVE value (default: 300 seconds).
For details about communication options, see 14.2.4 Specifying communication options in the Job Management Partner 1/Automatic Job Management System 3 Operator's Guide.
- #4
-
For the number of status updates, use the smaller of the following:
-
Number of root jobnet startups times 10
-
Monitoring time of JP1/AJS3 Console divided by the monitoring interval
For the number of root jobnet startups, estimate the number of times the monitored jobnet is executed within the monitoring period of JP1/AJS3 Console.
When you monitor a jobnet with a start condition, for the number of startups, estimate the number of times the start condition is established.
-
- Examples:
-
To estimate the required log file size for keeping a one-week log, use the following conditions:
-
JP1/AJS3 Console View is used to monitor work tasks for one week.
-
The monitoring interval of JP1/AJS3 Console is 300 seconds.
-
There are 50 AJS3 unit monitored objects in the entire root business scope.
-
All the monitored root jobnets are executed twice a day.
-
One operation is performed per hour.
-
The rate of operation failure is 0.1.
-
One operation is performed on monitored objects every six hours.
The required log file size is as follows:
-
For starting or ending JP1/AJS3 Console 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 acquiring status
0.5 x 50 x (2 x 7 x 10) + (0.5 x 50 + 4 x 0) x (1 + 0) = 3,525 kilobytes
-
For operations on monitored objects
5 x 24 x 7 / 6 = 140 kilobytes
-
For checking connections
0.5 x 3,600 x 24 x 7 / 300 = 1,008 kilobytes
-
Total
20 + 504 + 68 + 3,525 + 140 + 1,008 = 5,265 (kilobytes) = 5.1 (megabytes)
Round the above number and add 1 megabyte for leeway. The result is 7 megabytes.
-