Job Management Partner 1/Performance Management Planning and Configuration Guide

4.8.2 Notes on temporary files

Organization of this subsection

(1) Output directory for temporary files

(2) Estimating the size of temporary files

(1) Output directory for temporary files

The Agent Collector, Remote Monitor Collector, Agent Store, Remote Monitor Store, and Master Store services create temporary files in the following directories when you display real-time or historical reports in PFM - Web Console, display event histories, or acquire historical data using the ODBC driver:

In Windows:

The directory specified by the TMP system environment variable.

In UNIX:

The directory specified by the TMPDIR environment variable.

If TMPDIR is not defined, temporary files are created in /var/tmp or /tmp.

The Agent Collector, Remote Monitor Collector, Agent Store, Remote Monitor Store, and Master Store services might output the KAVE00105-E message when there is insufficient disk space on the disk where the directory is located.

In this case, if you are unable to secure any more free space, you can change the directory in which temporary files are created by defining the following environment variable:

Environment variable Description

JPC_TMPDIR Specifies the path to the directory where temporary files are to be output.

Note

In Windows, define the JPC_TMPDIR environment variable as a system environment variable. If you have configured Performance Management to start automatically in UNIX by using an automatic start script, use the following procedure to edit the automatic start script file:

Log on as the root user.

Open the automatic start script file jpc_start in an editor, for example vi, and locate a line that resembles the following:
export PATH SHLIB_PATH LD_LIBRARY_PATH LIBPATH HCCLIBCNF

Modify the line you located in step 2 as follows:
JPC_TMPDIR=temporary-file-output-directory
export PATH SHLIB_PATH LD_LIBRARY_PATH LIBPATH HCCLIBCNF JPC_TMPDIR
Note: Ensure that the disk where the path specified in temporary-file-output-directory is located has sufficient free space.

Restart the system.

Environment variable	Description
JPC_TMPDIR	Specifies the path to the directory where temporary files are to be output.

(2) Estimating the size of temporary files

Use the following formula to calculate the size of the temporary files created when you display a report or use the ODBC driver to acquire historical data. The maximum size of temporary files is 2GB. Adjust the conditions for the report or ODBC driver so that the calculated size is within the limit.

total-size-of-specified-fields * number-of-instances * number-of-records [bytes]

(a) For non-PA records

The total-size-of-specified-fields in the formula is the total size of the fields specified in the report or for the ODBC driver.

Calculation example for the record PD_PDI in PFM - Agent for Platform (Windows)

The formula when displaying a historical report with the following conditions is shown below.

"Date and Time" field (char(6) type: 6 bytes) is specified^#1

ODBC key field is specified^#1
"Program" field (string type: 256 bytes)
"PID" field (ulong type: 4 bytes)

Other specified fields:
"CPU %" field (float type: 4 bytes)
"User" field (string type: 36 bytes)
"Date" field (char(3) type: 6 bytes)^#2

Number of instances collected per minute:
200 instances

Collection period (number of records requested)
A report that displays the per-minute records collected over one day contains a total of 1440 records (60 minutes * 24 hours).

Formula: ( 6 + 256 + 4 + 4 + 36 + 6 ) * 200 * 1440 = 89,856,000 [bytes]

#1

When displaying a real-time or historical report, the "Date and Time" field and the ODBC key field are always acquired regardless of whether or not they appear in the report. When acquiring data using the ODBC driver, the driver acquires only those fields specified in the acquisition conditions.

#2

The "Date" and "Time" fields, which are automatically appended to data recorded in the Store database, occupy 6 bytes each in the case of a historical report, and 3 bytes each when acquired by the ODBC driver. Other fields must be calculated with the size matching the type described in each PFM - Agent or PFM - RM manual.

Because the instance count differs each time record collection takes place, use the above only as a general guideline. For details about the data type of each field and the size of each data type and ODBC key field, see the chapter about records in the manuals for PFM - Agent and PFM - RM.

(b) For PA records

When calculating the temporary file size for a PA record, use 4409 as the total-size-of-specified-fields, 1 as the number-of-instances, and the number of events that occurred during the specified period as the number-of-records.

Supplemental information:

The size of a temporary file is proportional to the number of records specified in the report and number of instances in those records. For this reason, if you anticipate that the size of the temporary file will exceed 2 GB, you can adjust the amount of data displayed by reducing the maximum number of records that can be displayed in PFM - Web Console when you configure the display settings for historical reports and event histories. In the Maximum number of records field of the display settings for historical reports, enter the result of the formula number-of-instances * number-of-records.

Note

In UNIX, the maximum size of temporary files might be less than 2 GB due to restrictions imposed on file sizes by the ulimit command. Even if the size of a temporary file from the above estimation does not exceed 2 GB, if the message KAVE00103-E appears while displaying reports, use the ulimit command to check the maximum value for the file size.

[Contents][Back][Next]

[Trademarks]