12.3.2 Lists of log files and directories to be collected during troubleshooting
This section describes the log information that is output from Performance Management. For details about the name and size of the file to which the operation status log information is output, see the chapter that describes error handling procedures in the Job Management Partner 1/Performance Management User's Guide.
- Organization of this subsection
(1) Common message log
This section describes the common message log, which is one of the types of log information for Performance Management. The following table lists tables list by OS the service name or control name and the log file names for the log output source files, as well as the amount of disk space each uses.
|
Type of log information |
Output source |
File name |
Disk space used#1 (KB) |
|---|---|---|---|
|
Common message log |
Performance Management |
installation-folder\log\jpclog{01|02}#2 |
2,048 (x 2) |
|
installation-folder\log\jpclogw{01|02}#2 |
2,048 (x 2) |
||
|
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) |
|
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 KB, can be created. In this case, the total available disk space is 4,096 KB.
- #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 01 suffix 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 is 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.
- Wraparound 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 a 02 suffix 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 it and 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 directory is on the shared disk that was specified when the logical host was created.
Table 12‒3: File name of the common message log (UNIX) Type of log information
Output source
File name
Disk space used#1 (KB)
Common message log
Performance Management
/opt/jp1pc/log/jpclog{01|02}#2
2,048
(x 2)
/opt/jp1pc/log/jpclogw{01|02}#2
2,048
(x 2)
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)
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 KB, can be created. In this case, the total available disk space is 4,096 KB.
- #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 01 suffix 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 is 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.
- Wraparound 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 a 02 suffix 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 it and 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 directory is on the shared disk that was specified when the logical host was created.
(2) Trace log
This section describes the trace log, which is one of the types of log information for Performance Management. The tables below list, for each OS, the service names or control names that are the output sources of PFM - Agent trace logs, as well as the names of the storage folders.
|
Type of log information |
Output source |
Folder name |
|---|---|---|
|
Trace log |
Agent Collector service |
installation-folder\agtm\agent\instance-name\log\ |
|
Agent Store service |
installation-folder\agtm\store\instance-name\log\ |
|
|
Trace log (for logical host operation) |
Agent Collector |
environment-directory#\jp1pc\agtm\agent\instance-name\log\ |
|
Agent Store |
environment-directory#\jp1pc\agtm\store\instance-name\log\ |
- #
-
The environment directory is on the shared disk that was specified when the logical host was created.
Table 12‒5: Names of the trace log storage directories (UNIX) Type of log information
Output source
Directory name
Trace log
Agent Collector service
/opt/jp1pc/agtm/agent/instance-name/log/
Agent Store service
/opt/jp1pc/agtm/store/instance-name/log/
Trace log (for logical host operation)
Agent Collector
environment-directory#/jp1pc/agtm/agent/instance-name/log/
Agent Store
environment-directory#/jp1pc/agtm/store/instance-name/log/
- #
-
The environment directory is on the shared disk that was specified when the logical host was created.