9.3.2 Log files and directories to check

(1) Common message log

This subsection describes the common message log, which is one of the types of log information for Performance Management.

The following table lists the output sources, the log file names, and the amount of disk space used for Windows.

Table 9‒5: File names of the common message log (for Windows)

No.	Type of log information	Output source	File name	Disk space used#1 (kilobytes)
1	Common message log	Performance Management	installation-folder\log\jpclog{01|02}#2	2,048 (x 2)
2			installation-folder\log\jpclogw{01|02}#2	2,048 (x 2)
3	Common message log (for logical host operation)	Performance Management for logical host operation	environment-folder#3 \jp1pc\log\jpclog{01|02}#2	2,048 (x 2)
4			environment-folder#3 \jp1pc\log\jpclogw{01|02}#2	2,048 (x 2)

#1

The value in parentheses is the number of log files that can be created for a single service. For example, 2,048 (x 2) indicates that a maximum of two log files, each with a size of 2,048 kilobytes, can be created. In this case, the total available disk space must be 4,096 kilobytes.

#2

The value 01 or 02 is appended to the file name of the common message log.

Sequential file method (jpclog)

Log information is first output to the log file whose name ends with 01. When the maximum log file size is reached, the suffix at the end of the log file name is changed from 01 to 02, and a new log file with the suffix 01 is created. Log information is then output to the new 01 log file. If a log file with a name ending in 02 already exists, that log file will be overwritten when the 01 suffix is changed to 02. The most recent log information is always output to the log file with a 01 suffix.

Wrap-around file method (jpclogw)

Log information is first output to the log file whose name ends with 01. When the maximum log file size is reached, a new log file with the suffix 02 is created. Log information is then output to the new 02 log file. If a log file with a name ending in 02 already exists, all data is deleted from that log file, and then log information is output from the beginning of the file. Thereafter, the log files are used alternately.

For details about how to output log information to log files, see the chapter that describes detection of Performance Management failures in the Job Management Partner 1/Performance Management User's Guide.

#3

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

The following table lists the output sources, the log file names, and the amount of disk space used for UNIX.

Table 9‒6: File names of the common message log (for UNIX)

No.	Type of log information	Output source	File name	Disk space used#1 (kilobytes)
1	Common message log	Performance Management	/opt/jp1pc/log/jpclog{01|02}#2	2,048 (x 2)
2			/opt/jp1pc/log/jpclogw{01|02}#2	2,048 (x 2)
3	Common message log (for logical host operation)	Performance Management for logical host operation	environment-directory#3 /jp1pc/log/jpclog{01|02}#2	2,048 (x 2)
4			environment-directory#3 /jp1pc/log/jpclogw{01|02}#2	2,048 (x 2)

#1

The value in parentheses is the number of log files that can be created for a single service. For example, 2,048 (x 2) indicates that a maximum of two log files, each with a size of 2,048 kilobytes, can be created. In this case, the total available disk space must be 4,096 kilobytes.

#2

The value 01 or 02 is appended to the file name of the common message log.

Sequential file method (jpclog)

Log information is first output to the log file whose name ends with 01. When the maximum log file size is reached, the suffix at the end of the log file name is changed from 01 to 02, and a new log file with the suffix 01 is created. Log information is then output to the new 01 log file. If a log file with a name ending in 02 already exists, that log file will be overwritten when the 01 suffix is changed to 02. The most recent log information is always output to the log file with a 01 suffix.

Wrap-around file method (jpclogw)

Log information is first output to the log file whose name ends with 01. When the maximum log file size is reached, a new log file with the suffix 02 is created. Log information is then output to the new 02 log file. If a log file with a name ending in 02 already exists, all data is deleted from that log file, and then log information is output from the beginning of the file. Thereafter, the log files are used alternately.

For details about how to output log information to the log files, see the chapter that describes detection of Performance Management failures in the Job Management Partner 1/Performance Management User's Guide.

#3

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

To Page Top

(2) Trace log

This subsection describes the trace log, which is one of the types of log information for Performance Management.

The following table lists the output sources and the storage folder names for Windows.

Table 9‒7: Names of trace log storage folders (for Windows)

No.	Type of log information	Output source	Folder name
1	Trace log	Action Handler service	installation-folder\bin\action\log\
2		Performance Management command	installation-folder\tools\log\
3		Remote Monitor Collector service	installation-folder\agt7\agent\instance-name\log\
4		Remote Monitor Store service	installation-folder\agt7\store\instance-name\log\
5		Status Server service	installation-folder\bin\statsvr\log\
6	Trace log (for logical host operation)	Action Handler service	environment-folder#\jp1pc\bin\action\log\
7		Performance Management command	environment-folder#\jp1pc\tools\log\
8		Remote Monitor Collector service	environment-folder#\jp1pc\agt7\agent\instance-name\log\
9		Remote Monitor Store service	environment-folder#\jp1pc\agt7\store\instance-name\log\

The following table lists the output sources and the storage directory names for UNIX.

Table 9‒8: Names of trace log storage directories (for UNIX)

No.	Type of log information	Output source	Directory name
1	Trace log	Action Handler service	/opt/bin/action/log/
2		Performance Management command	/opt/jp1pc/tools/log/
3		Remote Monitor Collector service	/opt/jp1pc/agt7/agent/instance-name/log/
4		Remote Monitor Store service	/opt/jp1pc/agt7/store/instance-name/log/
5		Status Server service	/opt/jp1pc/bin/statsvr/log/
6	Trace log (for logical host operation)	Action Handler service	environment-directory#/jp1pc/bin/action/log/
7		Performance Management command	environment-directory#/jp1pc/tools/log/
8		Remote Monitor Collector service	environment-directory#/jp1pc/agt7/agent/instance-name/log/
9		Remote Monitor Store service	environment-directory#/jp1pc/agt7/store/instance-name/log/

To Page Top

(3) Agent log

This subsection describes the agent log of PFM - RM for Platform, which is one of the types of log information for Performance Management.

The following table lists the output sources, output targets, log file names, and disk space used for Windows.

Table 9‒9: Agent log files (for Windows)

No.	Type of log information	Output source	Output target	File name	Default disk space used#1 (megabytes)
1	Normal log	PFM - RM for Platform	installation-folder\agt7\agent\instance-name\log\	collect_core_nn#2	3 (x 4)#3
2				collect_nn#2
3				timer_core_nn#2
4				timer_nn#2
5				target_monitoring-target-name_nn#2
6	Normal log (for logical host operation)	PFM - RM for Platform	environment-folder#4\jp1pc\agt7\agent\instance-name\log\	collect_core_nn#2	3 (x 4)#3
7				collect_nn#2
8				timer_core_nn#2
9				timer_nn#2
10				target_monitoring-target-name_nn#2

The following table lists the output sources, output targets, log file names, and disk space used for UNIX.

Table 9‒10: Agent log files (for UNIX)

No.	Type of log information	Output source	Output target	File name	Default disk space used#1 (megabytes)
1	Normal log	PFM - RM for Platform	/opt/jp1pc/agt7/agent/instance-name/log/	collect_nn#2	3 (x 4)#3
2				timer_nn#2
3				target_monitoring-target-name_nn#2
4	Normal log (for logical host operation)	PFM - RM for Platform	environment-directory#4/jp1pc/agt7/agent/instance-name/log/	collect_nn#2	3 (x 4)#3
5				timer_nn#2
6				target_monitoring-target-name_nn#2

To Page Top