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

8.4.1 In UNIX

Organization of this subsection

(1) OS' log information

(2) Performance Management information

(3) Operation details

(4) Error information

(5) Other information

(1) OS' log information

You need to collect the OS-related log information indicated in the following table.

Table 8-4 OS-related log information

Information type Overview Default file name Can be collected using the jpcras command?

System log syslog

For HP-UX
/var/adm/syslog/syslog.log

For Solaris
/var/adm/messages*

For AIX
/var/adm/syslog*

For Linux
/var/log/messages*

Y^#1

Process information List of processes -- Y

System files hosts file /etc/hosts Y

/etc/inet/ipnodes^#2 Y^#3

services file /etc/services Y

OS information Patch information -- Y

Kernel information -- Y

Version information -- Y

Network status -- Y

Environment variable -- Y

Host name -- Y

Dump information core file^#4 -- Y

Legend:

Y: Can be collected

--: Not applicable

#1

You cannot collect this data when using a system that is set to output data using the default path and file name. Collect the data manually.

#2

The /etc/inet/ipnodes file exists only in Solaris. Collect this file together with the /etc/hosts file.

#3

Only the jpcras command in PFM - Manager 09-00 or later, or PFM - Base 09-00 or later, can collect this data.

#4

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

Information type	Overview	Default file name	Can be collected using the jpcras command?
System log	syslog	For HP-UX /var/adm/syslog/syslog.log For Solaris /var/adm/messages* For AIX /var/adm/syslog* For Linux /var/log/messages*	Y^#1
Process information	List of processes	--	Y
System files	hosts file	/etc/hosts	Y
/etc/inet/ipnodes^#2	Y^#3
services file	/etc/services	Y
OS information	Patch information	--	Y
Kernel information	--	Y
Version information	--	Y
Network status	--	Y
Environment variable	--	Y
Host name	--	Y
Dump information	core file^#4	--	Y

(2) Performance Management information

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 8-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

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

Output results of the jpctool service list (jpcctrl list) command -- Y

Version information Product version -- Y

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
/opt/jp1pc/agtu/agent/jpcapp
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 manual Job Management Partner 1/Performance Management User's Guide.

#2

For details about the trace log storage destination directory, see 8.3.2 Log files and directories.

#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.

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
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
Output results of the jpctool service list (jpcctrl list) command	--	Y
Version information	Product version	--	Y
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	/opt/jp1pc/agtu/agent/jpcapp	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

(3) Operation details

You need the following types of information on the operation that was taking place when the error occurred:

Operation details

Time at which the error occurred

Machine configuration (including each OS version, host name, and the configurations of PFM - Manager and PFM - Agent)

Whether the error can be reproduced

Performance Management user name used for logon if the user logged on from PFM - Web Console

(4) Error information

You need to collect the following error information:

Messages output to the console if the error occurred during command execution

(5) Other information

The following types of information are also necessary:

The argument specified for the command if the error occurred during command execution

[Contents][Back][Next]

[Trademarks]