Performance Management information to be collected

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

You need to collect the types of information related to Performance Management that are described below. If the error occurred in network connection, you also need to collect information from the connection destination machine. The following table describes the information related to Performance Management.

Table 11-5 Performance Management information

Information type	Description	Default file name	Collection by the jpcras command possible
Common message log	Message log output by Performance Management (sequential file method)	/opt/jp1pc/log/jpclog{01\|02}^#1	Y
Common message log	Message log output by Performance Management (wrap-around method)	/opt/jp1pc/log/jpclogw{01\|02}^#1	Y
Configuration information	Information file for each configuration	--	Y
Configuration information	Output results of the jpctool service list (jpcctrl list) command	--	Y
Version information	Product version	--	Y
Version information	History information	--	Y
Database information	Agent Store	For Store 1.0 /opt/jp1pc/agtu/store/.DB /opt/jp1pc/agtu/store/.IDX For Store 2.0 /opt/jp1pc/agtu/store/STPD /opt/jp1pc/agtu/store/STPI The following files under the /opt/jp1pc/agtu/store/STPL directory: .DB .IDX	Y
Trace log	Trace information on each service of a Performance Management program	--^#2	Y
Definition file	Application definition file (09-00 or earlier)	/opt/jp1pc/agtu/agent/jpcapp	Y
Definition file	Application definition file (10-00 or later)	/opt/jp1pc/agtu/agent/jpcapp2	Y
Information about the function for collecting user-specific performance data	Configuration information	/opt/jp1pc/agtu/agent/jpcuser/jpcuser.ini	Y
	Debug log	/opt/jp1pc/agtu/agent/jpcuser/debug/jpcuser_dbg_{01\|02\|03\|04\|05}.log	Y
	Trace log	/opt/jp1pc/agtu/agent/jpcuser/log/trace/msglog{01\|02}	Y
	Public log	/opt/jp1pc/agtu/agent/jpcuser/log/public/jpclog{01\|02}	Y
	User data file	/opt/jp1pc/agtu/agent/jpcuser/userdata/jpcuser_{UPI\|UPIB\|UPD\|UPDB}	Y
	Core dump file^#3	/opt/jp1pc/agtu/agent/jpcuser/core	Y
Installation log^#4	Default log of Hitachi PP Installer	/etc/.hitachi/.hitachi.log /etc/.hitachi/.hitachi.log{01\|02\|03\|04\|05} /etc/.hitachi/.install.log /etc/.hitachi/.install.log{01\|02\|03\|04\|05}	N

Legend:: Y: Can be collected.; N: Cannot be collected.; --: Not applicable

#1: For details about log file output methods, see the chapter explaining error detection in Performance Management in the Job Management Partner 1/Performance Management User's Guide.

#2: For details about the trace log storage destination directory, see 11.3.2 Log files and directories to check.

#3: In HP-UX 11i V3 (IPF), you can use the coreadm command to change the name of a core dump file. After renaming, the jpcras command cannot collect any files whose name does not begin with core. For these files, collect information manually.

#4: Collect this log if installation fails.

11.4.2 Performance Management information to be collected