Job Management Partner 1/Performance Management - Agent Option for Enterprise Applications Description, User's Guide and Reference
- Organization of this subsection
- (1) Log information about the OS
- (2) Information about Performance Management
- (3) Operation information
- (4) Error information on screen displays
- (5) User dump (for Windows Server 2008)
- (6) Collecting a problem report (for Windows Server 2008)
- (7) Other information
(1) Log information about the OS
The following OS-related information must be collected:
Type of information Overview Default file name Collected by the jpcras command? System log Windows event log N/A Y Process information List of processes N/A Y System file hosts file system-folder\system32\drivers\etc\hosts Y services file system-folder\system32\drivers\etc\services Y OS information System information N/A Y Network status N/A Y Host name N/A Y Dump information Dr. Watson log#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
- Legend:
- Y: Can be collected.
- N/A: Not applicable.
- #1
- In Windows Server 2008, Dr. Watson has been changed to Problem Reports and Solutions.
- #2
- If your setup provides for output of log files to a different folder, make sure that you collect the data from the correct folder.
(2) Information about Performance Management
You should collect information about Performance Management, as listed below. In the case of a network error, you should also collect applicable files from the connection-destination machine.
Type of information Overview 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 (wraparound file method) installation-folder\log\jpclogw{01|02}#1 Y Common message log (for logical host operation) Message log output from Performance Management for logical host operation (sequential file method) environment-directory#2\jp1pc\log\jpclog{01|02}#1 Y Message log output from Performance Management for logical host operation (wraparound file method) environment-directory#2\jp1pc\log\jpclogw{01|02}#1 Y Configuration information Each configuration information file N/A Y Output results of the jpctool service list (jpcctrl list) command N/A Y Version information Product version N/A Y Historical information N/A Y Database information Agent Store service
- For Store version 1.0
installation-folder\agtm\store\instance-name\*.DB
installation-folder\agtm\store\instance-name\*.IDX
- For Store version 2.0
installation-folder\agtm\store\instance-name\STPD\
installation-folder\agtm\store\instance-name\STPI\
The following files under the above folders:
*.DB
*.IDX
Y Database information (for logical host operation) Agent Store service for logical host operation
- For Store version 1.0
environment-directory#2\jp1pc\agtm\store\instance-name\*.DB
environment-directory#2\jp1pc\agtm\store\instance-name\*.IDX
- For Store version 2.0
environment-directory#2\jp1pc\agtm\store\instance-name\STPD\
environment-directory#2\jp1pc\agtm\store\instance-name\STPI\
The following files under the above folders:
*.DB
*.IDX
Y Trace log Trace information for each Performance Management program service N/A#3 Y Install log#4 Message log during installation (for Windows Server 2003) %TEMP%\pfm_inst.log
All files under the following folder:
%windir%\TEMP\HCDINSTN Message log during installation
(for Windows Server 2008)All files under the %windir%\TEMP\HCDINST folder N Command information Environment parameters file installation-folder\agtm\agent\instance-name\jr3alget.ini
installation-folder\agtm\agent\instance-name\jr3slget.iniY Trace information N/A Y Timestamp file N/A Y Extraction results file installation-folder\agtm\agent\instance-name\log\ALERT
installation-folder\agtm\agent\instance-name\log\SYSLOGY#5 Command information (for logical host operation) Environment parameters file environment-directory#2\jp1pc\agtm\agent\instance-name\jr3alget.ini
environment-directory#2\jp1pc\agtm\agent\instance-name\jr3slget.iniY Trace information -- Y Timestamp file -- Y Extraction results file environment-directory#2\jp1pc\agtm\agent\instance-name\log\ALERT
environment-directory#2\jp1pc\agtm\agent\instance-name\log\SYSLOGY#5
- Legend:
- Y: Can be collected.
- N: Cannot be collected.
- N/A: Not applicable.
- #1
- 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.
- #2
- The environment directory is on the shared disk that was specified when the logical host was created.
- #3
- For details about the trace log storage folder, see 12.3.2 Log files and directories.
- #4
- Collect this log information if installation fails.
- #5
- If the default storage location is changed, the jpcras command cannot collect the information. Collect the information manually.
- For the storage location of the extraction results file, see the EXTRACTFILE section in 5.3.2 Settings and the EXTRACTFILE section in 6.3.2 Settings.
(3) Operation information
You should collect the following information about the operation being performed when the error occurred:
- Details of the operation
- Time the error occurred
- Machine configuration (the OS version, host name, and PFM - Manager and PFM - Agent configuration, and so on.)
- Whether the problem is replicable
- Performance Management user name used during logon, if the user has logged on from PFM - View
(4) Error information on screen displays
You should obtain printouts of the following:
- The active screen when the application error occurred
- The error message dialog box (including the contents of detail information if displayed)
- The Command Prompt window or the Administrator Console window, if the error occurred during command execution
(5) User dump (for Windows Server 2008)
In Windows Server 2008, if a Performance Management process is terminated due to an application error, collect a user dump.
(6) Collecting a problem report (for Windows Server 2008)
In Windows Server 2008, if a Performance Management process is terminated due to an application error, collect a problem report.
(7) Other information
You should also collect the following information:
- The contents of System and Application in the Event Viewer window of Windows (in Windows Server 2003 or Windows Server 2008)
- The contents of System Information, which is displayed by choosing Accessories and then System Tools (in Windows Server 2003 or Windows Server 2008)
- The command arguments that were specified, if the error occurred during command execution
All Rights Reserved. Copyright (C) 2010, Hitachi, Ltd.