5.3.1 Overview of the performance report output function

The performance report output function collectively outputs information about the amount of data processed by the scheduler services and the job execution status to a CSV file. The information output to the file provides a performance report on the number of started jobs and queued jobs, and other operating status information about the scheduler services, all of which can be aggregated on an hourly basis. With such information, you can check the peak times of job execution and the operating status changing with time. If you use Excel or a similar program, you can also display the CSV-formatted information in graph format. By graphically aggregating or analyzing the output information, you can more easily understand the operating status of JP1/AJS3.

Figure 5‒1: Overview of the procedure from outputting a performance report to aggregating or analyzing the output information

The following table shows the types of information output to a performance report.

Table 5‒2: Types of information output to a performance report
Type of output information	Description
Amount of data processed by scheduler services	Number of started jobnets and jobs Number of ended jobnets and jobs
Job execution status	Number of jobs waiting to be processed Information about the jobs now being processed

To output performance reports, you must enable the performance report output function. When you enable the function, it starts outputting performance log files (in binary format). When you run the ajsreport command at the manager host, the contents of the performance log file are output to a CSV file. Operation status log data output to performance log files is retained in the files for seven days by default. The retention period of status log data can be changed by using the AJSREPORTSTOREDAYPERIOD environment setting parameter. The maximum retention period that can be set is 21 days. The ajsreport command can be used to set the target scheduler service, the period for which output data is to be aggregated, and the aggregation interval. The ajsreport command provides options that allow you to specify such settings when running the command. For example, periodically outputting the operating status to CSV files provides an understanding of the current operating status, and allows for comparison with a past operating status.

Figure 5‒2: Overview of periodically outputting performance reports for comparison

For details about the procedure for setting up the performance report output function, in Windows, see 6.6 Settings related to the output of performance reports in the JP1/Automatic Job Management System 3 Configuration Guide. In UNIX, see 15.7 Settings related to the output of performance reports in the JP1/Automatic Job Management System 3 Configuration Guide.

For details about estimating the size of performance log files, see 3.4.8 Estimating the size of performance log files in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

For details about the ajsreport command, see ajsreport in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

Note

If you move the system time backward during operation of JP1/AJS3 - Manager, delete the performance log files according to the following procedure:

Stop the JP1/AJS3 services.
Save the output results of the ajsreport command.
Delete all files under the directory to which performance log files are output.

For information about the output-destination directory of the performance log files, see 1.2.5 List of log files and directories in the manual JP1/Automatic Job Management System 3 Troubleshooting and 20.4.2(115) AJSREPORTDIR in the JP1/Automatic Job Management System 3 Configuration Guide.

To Page Top