3.2.1 Estimating the data flow on the network
We will explain how to estimate the following data volumes:
-
Between JP1/AJS3 - Manager and JP1/AJS3 - Agent
-
Between JP1/AJS3 - View and JP1/AJS3 - Manager
-
Between JP1/AJS3 Console View and JP1/AJS3 - Manager
- Organization of this subsection
(1) Estimating the data volume between JP1/AJS3 - Manager and JP1/AJS3 - Agent
You need to estimate the data involved in job executions and the transferring of execution results.
The following table shows an estimate for the volume of data between JP1/AJS3 - Manager and JP1/AJS3 - Agent.
Estimate the same data volume when using queueless jobs too.
|
Type of information |
Estimated volume of transferred data per job (units: bytes) |
|---|---|
|
Job execution request transfers |
|
|
Job result transfers |
600 + manager-host-name-size + agent-host-name-size + result-file-size (standard output, standard error output)#3 |
|
Event job execution request transfers |
Minimum: 256 Maximum: 25,600 |
|
Event job result transfers |
Minimum: 512 Maximum: 7,168 |
- #1
-
For contents defined in the UNIX and PC job definitions, see ajsprint in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1 and 4.2.6 UNIX/PC job definition in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.
To pass the information sent from an event job to the target job, add the size of the macro variables in the above estimate. For details about the size of the information to be passed to each type of event job, see B. Information Passed by Event Jobs in the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide.
- #2
-
The formula for estimating the size of the transfer file is as follows:
file-count
![[Figure]](GRAPHICS/SIGMA.GIF)
(file-name-length + file-size + (12 x number-of-lines-in-file) + 100)
- #3
-
The formula for estimating the size of the result file is as follows:
file-count
(result-file-size + (12 x number-of-lines-in-file) + 116)
In cases where the system monitors an agent host where a problem not in the above table occurred, or where jobs registered for execution are monitored by polling, data is exchanged between JP1/AJS3 - Manager and JP1/AJS3 - Agent. The volume of data per polling in such cases is shown below. Note that polling cannot monitor queueless jobs.
|
Type of data |
Estimated volume of transferred data per polling (units: bytes) |
|---|---|
|
Agent host status confirmation request transfers during trouble |
300 |
|
Status confirmation request transfers for jobs being executed |
350 + size-of-agent-host-name |
(2) Estimating the data volume between JP1/AJS3 - View and JP1/AJS3 - Manager
You need to estimate the volume of data relating to such items as the definition of jobnets. Since the data size for communications for operation and so on is relatively small, we will not estimate it here.
The estimated volume of data between JP1/AJS3 - View and JP1/AJS3 - Manager is shown in the table below.
|
Window displayed |
Estimated volume of transferred data (units: bytes) |
|---|---|
|
JP1/AJS3 - View (Main window) |
number-of-units x 500 |
|
JP1/AJS3 - View (Summary Monitor window) |
total-number-of-schedules#1 x 400 |
|
Jobnet Editor |
number-of-units x 250 + number-of-relation-lines x 50 |
|
Jobnet Monitor |
number-of-units x 300 + number-of-relation-lines x 50 |
|
Daily Schedule or Monthly Schedule |
total-number-of-schedules#1, #2 x 150 |
|
Search |
number-of-search-results x 450 |
- #1
-
This is the number of execution schedules and execution results for all of the units under the root jobnet.
If a job group is specified for operation, this number is the number of execution schedules and execution results for all of the units under the root jobnet directly under the job group.
- #2
-
This item also includes the number of schedules for unregistered units when the Monthly Schedule window displays execution schedules for unregistered units.
The following are some example estimates of data volumes:
-
When a jobnet defined with 300 units and 100 relation lines is checked in the Jobnet Monitor window:
300 x 300 + 100 x 50 = 95,000 (units: bytes)
-
When the execution schedule and execution results for an operation in which the daily execution of 100 jobnets with 100 jobs defined for them is planned is checked in the Daily Schedule window:
100 x 100 x 150 = 1,500,000 (units: bytes)
JP1/AJS3 - View acquires information from JP1/AJS3 - Manager automatically at regular intervals. The defaults are 30 seconds for the Jobnet Monitor window, and 300 seconds for other windows. Settings can be made from 30 seconds upward. When you have to estimate the volume of data flowing in the network, make the calculation based on the update interval of JP1/AJS3 - View and the data size required for each window.
(3) Estimating the data volume between JP1/AJS3 Console View and JP1/AJS3 Console Manager
Here we explain how to estimate the volume of data between JP1/AJS3 Console View and JP1/AJS3 Console Manager
|
Type of data volume being estimated |
Estimate (units: bytes) |
|---|---|
|
Data flow when defining (newly creating, updating) AJS3 unit monitored objects, or when displaying definition information |
250 + (host-name-length#-specified-for-the-monitoring- destination-host-name + unit-full- name-length-specified-for-the-AJS3-unit-monitored-objects#) |
|
Data volume when multiple objects are copied and pasted |
number-of-objects-pasted x 150 |
|
Data volume when multiple objects are deleted |
number-of-objects-deleted x 100 |
|
Data volume when displaying screens |
defined-number-of-monitored-objects x 200 + 100 |
- #
-
If " or # occur in the specified character strings, estimate them as two bytes.