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

7.5.1 How to collect data in a Windows environment

Organization of this subsection

(1) Collecting dump information (in Windows Server 2008)

(2) Executing the data collection command

(3) Executing the data collection command (for logical host operation)

(4) Collecting the Windows event log

(5) Checking information about the operation

(6) Collecting error information on screen displays

(7) Collecting other information

(1) Collecting dump information (in Windows Server 2008)

To collect dump information in a Windows Server 2008 environment:
Open Task Manager.

Select the Processes tab.
Right-click the process name for which you want to collect dump information, and then select Create Dump File.
Dump files are stored in the following folder:
system-drive\Users\user-name\AppData\Local\Temp
Obtain the dump file from the folder created in step 3.
If you have changed the environment variable settings so that dump files are output to a different folder, obtain the dump file from that folder.

(2) Executing the data collection command

Use the jpcras command to collect data needed to determine the cause of an error. Note that an OS user with Administrator permissions must execute the procedure described below.

To execute the data collection command:
Log on to the host where the service subject to this data collection is installed.
At the command prompt, execute the following command to enable the command extensions of the command interpreter:
cmd /E:ON
Execute the jpcras command, with the data to be collected and the data storage folder to be used specified.
The following jpcras command stores all the available information in the c:\tmp\jpc\agt folder:
jpcras c:\tmp\jpc\agt all all
When you execute the jpcras command, the jpctool service list -id * -host * command is executed internally in order to obtain a list of PFM services and to check their activity status. If there is a firewall between the host where the command is executed and the host for the Performance Management system or if the system configuration is large, it might take a while for the jpctool service list -id * -host * command to execute. In such a case, you can suppress execution of the jpctool service list -id * -host * command, thus reducing the command execution time, by specifying 1 in the JPC_COLCTRLNOHOST environment variable.

For details about the jpcras command, see the chapter that describes commands in the manual Job Management Partner 1/Performance Management Reference.

Note on executing the command in a Windows Server 2008 environment

If the user account control functionality (UAC) is enabled in the operating system, the User Account Control dialog box might be displayed during command execution. If it is displayed, click the Continue button to continue data collection, or click the Cancel button to cancel data collection.

(3) Executing the data collection command (for logical host operation)

Performance Management information for logical host information is on the shared disk and must be collected in both the executing system and the standby system.

Use the jpcras command to collect data needed to determine the cause of an error. Note that an OS user with Administrator permissions must execute the procedure described below.

To execute the data collection command for logical host operation:
Place the shared disk online.
Information about the logical host is stored on the shared disk. At the executing node, make sure that the shared disk is online and then collect the information.
Execute the jpcras command in both the executing system and the standby system, with the data to be collected and the data storage folder to be used specified.
The following jpcras command stores all the available information in the c:\tmp\jpc\agt folder:
jpcras c:\tmp\jpc\agt all all
Executing the jpcras command without the lhost argument specified collects all the Performance Management information on the physical and logical hosts at that node. If there is a Performance Management in the logical host environment, the log files on the shared disk are acquired.
If the jpcras command is executed at a node where the shared disk is offline, files will not be acquired from the shared disk, but the command will terminate normally without resulting in an error.

Note

Execute the data collection command at both the executing node and the standby node to collect information. To examine an event before and after failover, you need the information from both systems (executing and standby).

For details about the jpcras command, see the chapter that describes commands in the manual Job Management Partner 1/Performance Management Reference.
Collect information about the cluster software.
This information is needed to determine whether the problem occurred in the cluster software or in Performance Management. Collect the information that provides control requests, such as startup and termination of Performance Management from the cluster software, and their results.

(4) Collecting the Windows event log

In the Windows Event Viewer window, check the Windows event log. Also output the log to a file.

(5) Checking information about the operation

Check and save information about the operation that was underway when the error occurred. The following lists the information that you need to check and save:

Details of the operation

Time the error occurred

Machine configuration (such as the version of each OS, host name, and configuration of PFM - Manager and PFM - RM for Platform)

Whether the problem is repeatable

Performance Management user name used during logon, if the user has logged on from PFM - Web Console

(6) Collecting error information on screen displays

Obtain a hardcopy of the following information:

The window operation when the application error occurred

The error message dialog box
If there is detailed information, also make a hardcopy of that information.

The Command Prompt window or the Administrator Console window, if the error occurred during command execution
To print the Command Prompt window or the Administrator Console window, specify the following settings for the Command Prompt Properties window:

Edit options on the Options page
Select Quick Edit Mode.

Layout page
For Screen buffer size, set Height to 500.

(7) Collecting other information

Information to be collected for all operating systems

If the error occurred during command execution, the argument specified for the command

Contents of the dialog box displayed by choosing Accessories, System Tools, and then System Information

In Windows Server 2003

Contents of System and Application in the Windows Event Viewer window

In Windows Server 2008

Contents of System and Application under Windows Logs in the left pane of the Windows Event Viewer window

[Contents][Back][Next]

[Trademarks]