7.3.2 List of log files and directories

This subsection describes the log information output by a Performance Management program. Performance Management outputs the following log information:

For details about the output file name and file size of the operation status log, see the chapter on troubleshooting in the JP1/Performance Management User's Guide.

Organization of this subsection

(1) Common message log
(2) Trace log
(3) Agent log

(1) Common message log

This subsection describes the common message log output by Performance Management. The following tables show the name of the service or command that outputs the log, the name of the log file, and the disk space used by each file, for each OS.

Table 7‒3: Common message log file names
Type of log	Output source	File name	Disk usage^#1 (KB)
Common message log	Performance Management	`installation-folder\log\jpclog`{`01\|02`}^#2	2,048 (x2)
Common message log	Performance Management	`installation-folder\log\jpclogw`{`01\|02`}^#2	2,048 (x2)
Common message log (logical host use)	Performance Management on logical host	`environment-directory`^#3 `\jp1pc\log\jpclog`{`01\|02`}^#2	2,048 (x2)
Common message log (logical host use)	Performance Management on logical host	`environment-directory`^#3 `\jp1pc\log\jpclogw`{`01\|02`}^#2	2,048 (x2)

#1

The number enclosed in brackets indicates the number of log files created for the service. For example, if the disk usage is 2,048 (x2), Performance Management creates one or two log files, each taking up a maximum of 2,048 kilobytes of disk space. In this case, the total disk usage will be 4,096 KB.

#2

Common message log files are suffixed with 01 or 02.

When using sequential files (jpclog): Initially, log information is output to a log file with the suffix 01. When the log file reaches the maximum size, its suffix is changed from 01 to 02, and a new log file is created with the suffix 01. Subsequent log information is output to the new log file. If a log file with the suffix 02 already exists, it is overwritten. The latest log information is always output to the log file with the suffix 01.
When using wraparound files (jpclogw): Initially, log information is output to a log file with the suffix 01. When the log file reaches the maximum size, a new log file is created with the suffix 02. Subsequent log information is output to the new log file. If a log file with the suffix 02 already exists, the entire contents of the file are deleted, and new log information is added from the top of the file. Performance Management then alternates between the two files as each fills with data.

For details about the output format of the log files, see the chapter on detecting errors in Performance Management in the JP1/Performance Management User's Guide.

#3

The environment directory is the directory you specified on the shared disk when creating the logical host.

To Page Top

(2) Trace log

This subsection describes the trace logs output by Performance Management. The following tables list the name of the service or command that outputs trace logs for PFM - Agent for Microsoft SQL Server and the directory where the logs are stored, for each OS.

Table 7‒4: Trace log storage folders
Type of log	Output source	Folder name
Trace log	Action Handler service	`installation-folder\bin\action\log\`
	Performance Management command	`installation-folder\tools\log\`
	Agent Collector service	`installation-folder\agtq\agent\instance-name\log\`
	Agent Store service	`installation-folder\agtq\store\instance-name\log\`
	Status Server service	`installation-folder\bin\statsvr\log\`
Trace log (logical host use)	Action Handler service	`environment-directory`^#`\jp1pc\bin\action\log\`
	Performance Management command	`environment-directory`^#`\jp1pc\tools\log\`
	Agent Collector service	`environment-directory`^#`\jp1pc\agtq\agent\instance-name\log\`
	Agent Store service	`environment-directory`^#`\jp1pc\agtq\store\instance-name\log\`

#: The environment directory is the directory you specified on the shared disk when creating the logical host.

To Page Top

(3) Agent log

This subsection describes the agent logs output by Performance Management. The following tables list the name of the service or command that outputs agent logs for PFM - Agent for Microsoft SQL Server, the name of the log file, and the disk space used by each file.

Table 7‒5: Agent log files
Type of log	Output source	Default output destination^#1	File name	Default Disk usage^#1 (MB)
Normal log	PFM - Agent for Microsoft SQL Server	`installation-folder\agtq\agent\instance-name\log\`	`agtqinf`{`01`\|`02`}^#2	16
Error log	PFM - Agent for Microsoft SQL Server	`installation-folder\agtq\agent\instance-name\log\`	`agtqerr`{`01`\|`02`}^#2	16
Normal log (logical host use)	PFM - Agent for Microsoft SQL Server	`environment-directory`^#3`\jp1pc\agtq\agent\instance-name\log\`	`agtqinf`{`01`\|`02`}^#2	16
Error log (logical host use)	PFM - Agent for Microsoft SQL Server		`agtqerr`{`01`\|`02`}^#2	16

#1

You can use the following methods to check and change the output destination of agent logs and the maximum file size:

jpcconf inst setup command
Agent Configuration property in the PFM - Web Console window

For details about how to use the jpcconf inst setup command to change the settings, see 2.4.2 Updating an instance environment.

#2

Agent logs are output using two sequential files. The file names are suffixed with 01 or 02, which have the following meanings:

01: Current file
02: Backup file

For details about sequential files, see When using sequential files (jpclog) in (1) Common message log.

#3

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

To Page Top