Hitachi

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide


3.4.4 Estimating the size of trace log files for JP1/AJS3 Console

This subsection explains how to estimate the size of the trace log files used with JP1/AJS3 Console.

Organization of this subsection

(1) Estimating the size of the trace log file for JP1/AJS3 Console Manager

The settings for the JP1/AJS3 Console Manager trace log file in the initial status are as follows:

The capacity required for the trace log file differs greatly depending on the details of the definitions, the nature of the operations, and whether or not errors are encountered. Estimate an appropriate capacity for the trace log file and expand the current capacity if necessary.

The formula for estimating the size of the trace log file is as follows.

Appropriate-trace-log-file-capacity (units: kilobytes) =

(5.0 + number-of-monitoring-destination-hosts-per-root-business-scope (for-each-JP1-user) x 0.5)

x number-of-logins-from-the-occurrence-of-an-error-to-collection-of-data

Example: Saving a trace log for a 30-day period (for the physical host only)
  • A single JP1 user monitors applications at 30 target hosts.

  • There are 10 logins per day.

    Appropriate trace log file capacity = (5.0+30 x 0.5) x (10 x 30) = 6,000 kilobytes

(2) Estimating the size of the trace log file for JP1/AJS3 Console Agent

The settings for the JP1/AJS3 Console Agent trace log file in the initial status are as follows:

The capacity required for the trace log file differs greatly depending on the details of the definitions, the nature of the operations, and whether or not errors are encountered. Estimate an appropriate capacity for the trace log file and expand the current capacity if necessary.

The formula for estimating the size of the trace log file is as follows.

Appropriate-trace-log-file-capacity (units: kilobytes) =

(2.0 + (0.1 + (0.04 x number-of-monitored-scheduler-services))

x (time-from-the-occurrence-of-an-error-to-collection-of-data (units: seconds) / monitoring-interval (units: seconds)))

x number-of-monitored-JP1/AJS3-Console-View-hosts

Example: Saving a trace log for a 10-day period (for the physical host only)
  • Applications are monitored on the host using five JP1/AJS3 Console View hosts

  • Twenty scheduler services are monitored.

  • The monitoring interval is 300 seconds.

    Appropriate trace log file capacity = (2.0 + (0.1 + (0.04 x 20)) x (864,000 / 300)) x 5 = 12,970 kilobytes

For details on the procedure for expanding the trace log file, see the following references:

In Windows:

3.5.1 Extending trace log files in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1

In UNIX:

13.4.4 Extending trace log files in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1