7.3.2 Log file and folder list

(1) Common message log

For the common message log, which is one of Performance Management's log information types, the following table lists the service name or control name of the program that outputs the log, the file name of the log, and the disk space used by the log.

Table 7‒5: Common message log file name

Log information type	Output source	File name	Disk usage#1 (kilobytes)
Common message log	Performance Management	installation-folder\log\jpclog{01|02}#2	2,048 (2)
		installation-folder\log\jpclogw{01|02}#2	2,048 (2)
Common message log (in logical host environment)	Performance Management running on logical host	environment-folder#3 \jp1pc\log\jpclog{01|02}#2	2,048 (2)
		environment-folder#3 \jp1pc\log\jpclogw{01|02}#2	2,048 (2)

#1

Numbers in parentheses indicate the maximum number of log files that are created for each service. For example, "2,048 (2)" means a maximum of two log files, each with a size of 2.048 kilobytes, can be created. In this case, the total disk usage is 4,096 kilobytes.

#2

The file name of the common message log has a suffix of either 01 or 02.

When the sequential file (jpclog) method is used

Log information is first output to a log file with the 01 suffix. When the log file size reaches its upper limit, the log file name suffix is changed from 01 to 02 and a new log file with the 01 suffix is created. From this point on, log information is output to the log file with the 01 suffix. If a log file with the 02 suffix already exists, it is overwritten. The latest log is always output to the log file with the 01 suffix.

When the wrap-around file (jpclogw) method is used

Log information is first output to a log file with the 01 suffix. When the log file size reaches its upper limit, a new log file with the 02 suffix is created. From this point on, log information is output to the log file with the 02 suffix. If a log file with the 02 suffix already exists, all of its data is deleted first and then logs are output to this log file, beginning at the first line. Thereafter, the log output destination is alternated.

For details about log file output methods, see the chapter that explains error detection in the Job Management Partner 1/Performance Management User's Guide.

#3

The environment folder is a folder that was specified on the shared disk when the logical host was created.

To Page Top

(2) Trace log

Of the five types of log information that are output by Performance Management, the table below shows the service name or control name that outputs the trace log of PFM - RM for Virtual Machine, and the folder name at the destination where the log is saved.

Table 7‒6: Trace log storage folder name

Log information type	Output source	Folder name
Trace log	Action Handler service	installation-folder\bin\action\log\
	Performance Management command	installation-folder\tools\log\
	Remote Monitor Collector service	installation-folder\agt8\agent\instance-name\log\
	Remote Monitor Store service	installation-folder\agt8\store\instance-name\log\
	Migration command	installation-folder\agt8\tools\log\
	Status Server service	installation-folder\bin\statsvr\log\
Trace log (in logical host environment)	Action Handler service	environment-folder#\jp1pc\bin\action\log\
	Performance Management command	environment-folder#\jp1pc\tools\log\
	Remote Monitor Collector service	environment-folder#\jp1pc\agt8\agent\instance-name\log\
	Remote Monitor Store service	environment-folder#\jp1pc\agt8\store\instance-name\log\

#

The environment folder is a folder that was specified on the shared disk when the logical host was created.

To Page Top

(3) Collected log

Of the five types of log information that are output by Performance Management, the table below shows log file names, disk usage, and the service name or control name that outputs the collected log of PFM - RM for Virtual Machine.

A collected log is created for each monitoring target.

Table 7‒7: Collected log files

Log information type	Output source	Output destination	File name	Default disk usage#1 (megabytes)
Regular log	PFM - RM for Virtual Machine	installation-folder\agt8\agent\instance-name\log\	VM_Type_monitoring-target-name{1|2|3|4|5|6|7|8}.log#2	128
Regular log (in logical host environment)	PFM - RM for Virtual Machine	environment-folder#3 \jp1pc\agt8\agent\instance-name\log\	VM_Type_monitoring-target-name{1|2|3|4|5|6|7|8}.log#2	128

#1

The maximum file size of the collected log can be checked or modified using the following procedures:

• Execute the jpcconf inst setup command.

• View the Remote Monitor Configuration property in the PFM - Web Console window.

For details about the procedure that uses the jpcconf inst setup command, see 2.4.2 Updating an instance environment.

#2

The collected log uses the wrap-around file method. This method adds data to the latest log, without deleting the existing log. When the file size of a log exceeds the specified size, a new file with the log file number incremented by one is created. When the maximum number of logs that can be generated is reached (fixed at 8), the first file is overwritten.

#3

The environment folder is a folder that was specified on the shared disk when the logical host was created.

To Page Top