![[Contents]](FIGURE/CONTENT.GIF)
![[Glossary]](FIGURE/GLOSS.GIF)
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
![[Next]](FIGURE/AFTER.GIF)
Job Management Partner 1/Performance Management User's Guide
- Organization of this subsection
- (1) Log information about the OS
- (2) Performance Management information
- (3) PFM - Web Console information
- (4) Operation information
- (5) Error information on window displays
- (6) User dumps (Windows Server 2008)
- (7) Problem reports (Windows Server 2008)
- (8) Other information
(1) Log information about the OS
The following table lists the log information about the OS to be collected.
Type of information Outline Default file name Collected by the jpcras command Collected by the jpcwras command System log Windows event log N/A Y Y Process information List of processes N/A Y Y System file hosts file system-folder\system32\drivers\etc\hosts Y Y services file system-folder\system32\drivers\etc\service Y Y OS information System information N/A Y Y Network status N/A Y Y Host name N/A Y Y Dump information Dr. Watson log file#1 system-drive\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\drwtsn32.log#2
system-drive\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\user.dump#2Y Y
- Legend:
- Y: Can be collected
- N/A: Not applicable
- #1
- Windows Server 2008 provides Problem Reports and Solutions, which replace Dr. Watson.
- #2
- If your setup provides for output of log files to a different folder, be sure that you collect the data from the correct folder.
(2) Performance Management information
You need to collect the information about Performance Management listed below. In the case of a network error, you also need to collect applicable files from the connection-destination machine. The Performance Management information required to be collected is shown below.
Type of information Outline Default file name Collected by the jpcras command Common message log Message log output from Performance Management (sequential file method) installation-folder\log\jpclog{01|02}#1 Y Message log output from Performance Management (wrap-around file method) installation-folder\log\jpclogw{01|02}#1 Y Configuration information Each configuration information file N/A Y Output results of the jpctool service list command N/A Y Version information Product version N/A Y History information N/A Y Database information Name Server installation-folder\mgr\namesvr\*.DB
installation-folder\mgr\namesvr\*.IDXY Master Manager installation-folder\mgr\manager\*.DB
installation-folder\mgr\manager\*.IDXY Master Store installation-folder\mgr\store\*.DB
installation-folder\mgr\store\*.IDXY View Server installation-folder\mgr\viewsvr\data\*
installation-folder\mgr\viewsvr\Reports\*Y Agent Store and Remote Monitor Store installation-folder\xxxx#2\store\instance-name#3\*.DB
installation-folder\xxxx#2\store\instance-name#3\*.IDXY Agent Store (health check agent) installation-folder\agt0\store\*.DB
installation-folder\agt0\store\*.IDXY Trace log Trace information of each service in the Performance Management program N/A#4 Y Install log#5 Message log at the time of installation (in Windows Server 2003) TEMP-folder\pfm_inst.log N Message log at the time of installation
(in Windows Server 2008)Following files in the system-folder\TEMP\HCDINST folder:
- HCDMAIN.LOG and HCDMAINn.LOG#4
- HCDINST.LOG and HCDINSTn.LOG#4
- product-model-name.LOG
N Install log#6 system-folder\TEMP\HCDINST\product-model-name.LOG N Integrated installer log system-folder\TEMP\HCDINST\HCDMAIN.LOG
system-folder\TEMP\HCDINST\HCDMAIN#.LOG
(# indicates a number)N
- Legend:
- Y: Can be collected
- N: Cannot be collected
- N/A: Not applicable
- #1
- For details on the output format of the log files, see 13.5 Detecting problems by linking with the integrated system monitoring product.
- #2
- xxxx indicates the service key of each PFM - Agent or PFM - RM. For details on service keys of each PFM - Agent or PFM - RM, see the description of the naming rules in an appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.
- #3
- For a PFM - Agent or PFM - RM monitoring an application program which can start multiple service sets on a single host, there is a folder for each instance.
- #4
- For details on the trace log storage destination, see 14.3.2 Log information files.
- #5
- Collect this information if the installation fails.
- #6
- This is only applicable for Windows Server 2008.
(3) PFM - Web Console information
You need to collect the information about PFM - Web Console listed below. In the case of a network error, you also need to collect applicable files from the connection-destination machine. The PFM - Web Console information required to be collected is shown below.
Type of information Outline Default file name Collected by the jpcwras command Web server information Server log of Web server or Web container N/A Y Registry information Product registry information N/A Y Operation status log#1 Message log output from PFM - Web Console installation-folder\log\jpcwtrace1#2.log Y Message log output from a PFM - Web Console command
- For the jpcrpt command
- installation-folder\log\jpcrpt_process-ID-of-executed-command_log1#2.log
- For the jpcrdef, jpcasrec, or jpcaspsv command
- installation-folder\log\command-name_sub-command-name_log1#2.log
- For the jpcmkkey command
- installation-folder\log\jpcmkkey_log1#2.log
- For all other commands
- installation-folder\log\command-name_log1#2.log
Y File information List of PFM - Web Console installation files N/A Y Configuration Info PFM - Web Console configuration information installation-folder\config\*.*
installation-folder\sample\config\*.*Y PFM - Web Console log information (Un)installer log file system-drive\pfmwebconuninst.log#3
system-drive\pfmwebconinst.rtn#3
system-drive\pfmwebconinst.log#3
system-drive\pfmwebconuninst.rtn#3Y system-folder\TEMP
\HCDINST\product-model-name.LOG#4N
- Legend:
- Y: Can be collected
- N: Cannot be collected
- N/A: Not applicable
- #1
- For details on the output format of the operation status log, see the chapter explaining the log information in the manual Job Management Partner 1/Performance Management Reference.
- #2
- The value 1 is appended to the file name of the operation status log.
- #3
- In Windows Server 2003 only
- #4
- In Windows Server 2008 only
(4) Operation information
You need to collect the following information about the operation being performed when an error occurs:
- Details of the operation
- Time the error occurred
- Machine configuration (for example, the OS version, host name, and PFM - Manager and PFM - Agent or PFM - RM configuration)
- Whether the error is replicable
- When logged on from PFM - Web Console, the Performance Management user name at logon
(5) Error information on window displays
Obtain printouts of the following:
- The Web browser
- The window operation when the application error occurred
- The error message dialog box (including the contents displayed if there is a Details button)
- The Command Prompt window or the Administrator Console window, if the error occurred during command execution
(6) User dumps (Windows Server 2008)
If a Performance Management process stops due to an application error under Windows Server 2008, collect the user dumps.
(7) Problem reports (Windows Server 2008)
If a Performance Management process stops due to an application error under Windows Server 2008, collect the problem reports.
(8) Other information
You also need to collect the following information:
- The contents of System Information, which is displayed by choosing Accessories and then System Tools (applicable in Windows 2003 and Windows Server 2008)
- The command arguments that were specified, if the error occurred during command execution
- Java VM thread dump
When collecting PFM - Web Console information, collect the Java VM thread dump.
To collect the Java VM thread dump:
- Execute the following command ten times at three-second intervals.
# installation-directory/CPSB/CC/web/bin/cjdumpweb PFMWebConsole
- Execute the jpcwras command.
- Note:
- Because the operation of Java VM becomes unstable when collecting a thread dump, restart the PFM - Web Console service.
All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.