Hitachi

Job Management Partner 1 Version 10 Job Management Partner 1/Performance Management - Remote Monitor for Platform Description, User's Guide and Reference


9.4.1 Data to be collected from a Windows environment

Organization of this subsection

(1) Log information about the OS

The following table lists the log information about the OS that needs to be collected.

Table 9‒11: Log information about the OS (for Windows)

No.

Type of information

Overview

Default file name

Collection by the jpcras command

1

System log

Windows event log

--

Y

2

WMI log

system-folder\system32\WBEM\Logs\*#

Y

3

Process information

List of processes

--

Y

4

System file

hosts file

system-folder\system32\drivers\etc\hosts

Y

5

services file

system-folder\system32\drivers\etc\services

Y

6

OS information

System information

--

Y

7

Network status

--

Y

8

Host name

--

Y

9

Windows firewall information

--

Y

10

Dump information (in Windows Server 2003)

Dr. Watson log file

system-drive\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\drwtsn32.log#

system-drive\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\user.dump#

Y

11

Dump information (in Windows Server 2008 or Windows Server 2012)

Problem report and solution log file

user-mode-process-dump-output-folder\program-name.process-ID.dmp

Example: jpcagt7.exe.2420.dmp

N

Legend:

Y: Can be collected

N: Cannot be collected

--: Not applicable

#

If you have set the log files to be output to a different folder, collect the data from the applicable folder.

(2) Information about Performance Management

The following table lists the Performance Management information that needs to be collected. In the case of a network connection error, you must also collect applicable files from the machine at the connection destination.

Table 9‒12: Information about Performance Management (for Windows)

No.

Type of information

Overview

Default file name

Collection by the jpcras command

1

Common message log

Message log output from Performance Management (sequential file method)

installation-folder\log\jpclog{01|02}#1

Y

2

Message log output from Performance Management (wrap-around file method)

installation-folder\log\jpclogw{01|02}#1

Y

3

Configuration information

Each configuration information file

--

Y

4

Output results of the jpctool service list command

--

Y

5

Version information

Product version

--

Y

6

Historical information

--

Y

7

Database information

Remote Monitor Store service

  • installation-folder\agt7\store\instance-name\STPD

  • installation-folder\agt7\store\instance-name\following-files-under-STPI-folder

    [Figure] *.DB

    [Figure] *.IDX

Y

8

Trace log

Trace information for each service of the Performance Management program

--#2

Y

9

Agent log

Normal log of the processing related to record collection by PFM - RM for Platform

  • installation-folder\agt7\agent\instance-name\log\collect_{01|02|03|04}#4

  • installation-folder\agt7\agent\instance-name\log\timer_{01|02|03|04}#4

  • installation-folder\agt7\agent\instance-name\log\target_monitoring-target-name_{01|02|03|04}#4

Y

10

Work data

Work data during performance data collection

  • installation-folder\agt7\agent\instance-name\targets\*

  • installation-folder\agt7\agent\instance-name\groups\*

Y

11

Install log#3

Message log during installation

  • %TEMP%\pfm_inst.log#5

  • system-folder\TEMP\HCDINST\*.LOG

N

12

Language environment information for system account

Language environment information for system account

  • installation-folder\agt7\agent\instance-name\log\system_lang.log

Y

Legend:

Y: Can be collected

N: Cannot be collected

--: Not applicable

#1

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.

#2

For details about the trace log storage folder, see 9.3.2(2) Trace log.

#3

Collect this log information if installation fails. %TEMP% indicates the folder that is set in TEMP when the set command is executed at the command prompt.

#4

For details about the agent log output method and the storage folder, see 9.3.2 Log files and directories to check.

#5

This applies to Windows Server 2003 only.

(3) Software information

The following table lists the types of information that must be collected by the various software when you want to use PFM - RM for Platform to collect performance data.

Table 9‒13: Software information

No.

Type of information

Overview

Acquiring command

Collection by the jpcras command

1

PuTTY

SSH client (plink) version information

plink.exe -V#1

Y

2

ActivePerl

Perl module (perl) version information

perl.exe -V#2

Y

Legend:

Y: Can be collected

#1

Specify the -V option for the absolute path name of the plink.exe command specified in SSH_Client when the instance environment was set up. Note that the command will not be executed in the following cases:

[Figure] SSH_Client is not specified.

[Figure] No file exists in the path specified in SSH_Client.

[Figure] The file name specified in SSH_Client is not plink.exe.

#2

Specify the -V option for the absolute path name of the perl.exe command specified in Perl_Module when the instance environment was set up. Note that the command will not be executed in the following cases:

[Figure] Perl_Module is not specified.

[Figure] No file exists in the path specified in Perl_Module.

[Figure] The file name specified in Perl_Module is not perl.exe.

(4) Operation information

You need the following information about the operation that was underway when an error occurred:

(5) Error information on screen displays

Obtain a hardcopy of the following information:

(6) User-mode process dump (in Windows Server 2008 or Windows Server 2012)

In a Windows Server 2008 or Windows Server 2012 environment, if a Performance Management process is stopped by an application error, collect a user-mode process dump.

(7) Collecting a problem report (in Windows Server 2008 or Windows Server 2012)

In a Windows Server 2008 or Windows Server 2012 environment, if a Performance Management process is stopped by an application error, collect a problem report.

(8) Other information

You also need the following information: