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

Notes on records

Note the following points when collecting records.

Notes on performance information when modifying system resources

Note the following when using the DLPAR function of AIX 5L V5.3 or later, the vPars function of HP-UX 11i, or the DR function of Solaris 9 or later to modify the system resources:

• Regardless of whether a PFM - Agent for Platform service is running or stopped, if the system resources are modified, there is no continuity between the performance data before and after the modification. Therefore, the performance data before and after the modification must be treated as separate.
  If necessary, back up the Store database before modifying the system resources, then clear the Store database and begin collecting new performance data. For details about how to back up the Store database, see the chapter explaining backup and restoration in the manual Job Management Partner 1/Performance Management User's Guide.
  
• For the DR function of Solaris 9 or later, if the system resources are modified while a PFM - Agent for Platform service is running, the performance data listed in Table 6-10 cannot be correctly collected. Therefore, before modifying the system resources, stop the PFM - Agent for Platform service. After the modification, restart the PFM - Agent for Platform service. For details about how to start and stop services, see the chapter explaining how to start and stop Performance Management in the manual Job Management Partner 1/Performance Management User's Guide.
  The table below shows the types of system resources that are affected if they are modified while a PFM - Agent for Platform service is running, and the actions that you can take to correctly display reports after the modification.
  

  Table 6-10 System resource types and actions to be taken to correctly display reports after modification

  Record	OS and name of the function used to modify system resources	System resource type	Actions to be taken after modification
  CPU - Per Processor Detail (PI_CPUP)#1	DLPAR of AIX 5L V5.3 or later vPars of HP-UX 11i DR of Solaris 9 or later	CPU	For a real-time report: Display the report again. For a historical report: Specify the display period so that it does not include the date and time when the system resources were modified.
  Device Detail (PI_DEVD)#1	DR of Solaris 9 or later	Device
  Device Summary (PI_DEVS)#1
  Network Interface Detail (PI_NIND)#1		LAN board
  Network Interface Summary (PI_NINS)#1
  System Summary Overview (PI)#2	DLPAR of AIX 5L V5.3 or later	CPU Memory
  	vPars of HP-UX 11i	CPU
  	DR of Solaris 9 or later	CPU Memory

  #1

  Fields other than those listed below are affected by a system resource modification:

  Interval (INTERVAL)

  Record Time (RECORD_TIME)

  Record Type (INPUT_RECORD_TYPE)

  Fields that are added only when data is recorded in the Store database

  #2

  The table below shows the fields that are affected by a system resource modification.

  Table 6-11 Fields that are affected by a system resource modification

  System resource type	Target field
  CPU	Active CPUs (NUMBER_OF_ACTIVE_CPUS) CPU % (KERNELMODE_USERMODE_PERCENT) Context Switches (CONTEXT_SWITCHES) Context Switches/sec (CONTEXT_SWITCHES_PER_SECOND) Idle % (IDLE_TIME_PERCENT) Interrupts (INTERRUPTS) Interrupts/sec (INTERRUPTS_PER_SECOND) Kernel CPU % (KERNELMODE_PERCENT) System Calls (SYSTEM_CALLS) System Calls/sec (SYSTEM_CALLS_PER_SECOND) Total Kernel-Mode Time (TOTAL_KERNELMODE_TIME) Total Idle Time (TOTAL_IDLE_TIME) Total User-Mode Time (TOTAL_USERMODE_TIME) Total Wait Time (TOTAL_WAIT_TIME) Traps (TRAPS) Traps/sec (TRAPS_PER_SECOND) User CPU % (USERMODE_PERCENT) Wait % (WAIT_TIME_PERCENT)
  Memory	Alloc Mem % (ALLOCATED_MEMORY_PERCENT) Alloc Mem Mbytes (ALLOCATED_MEMORY_MBYTES) Free Mem % (FREE_MEMORY_PERCENT) Free Mem Mbytes (FREE_MEMORY_MBYTES) Total Physical Mem Mbytes (TOTAL_MEMORY_MBYTES)

Performance information about resources that are logically partitioned

When the Micro-Partitioning function is used in AIX 5L V5.3 or later, a record is created for each logically partitioned processor. Therefore, even when resources are part of the same physical resource, their performance is not affected by other logical resources. Note that for a single-instance record of the PI record type, the combined total value of all resources including logical resources is displayed.

The table below shows the records and fields that are affected by the Micro-Partitioning function.

Table 6-12 Records and fields that are affected by the Micro-Partitioning function

Record name	Field name
CPU - Per Processor Detail (PI_CPUP)	All
Process Detail (PD)	CPU % (CPU_PERCENT_USED)
Process Detail Interval (PD_PDI)
Program Summary (PD_PGM)
System Summary Overview (PI)	Active CPUs (NUMBER_OF_ACTIVE_CPUS)
	CPU % (KERNELMODE_USERMODE_PERCENT)
	Idle % (IDLE_TIME_PERCENT)
	Kernel CPU % (KERNELMODE_PERCENT)
	Total Idle Time (TOTAL_IDLE_TIME)
	Total Kernel-Mode Time (TOTAL_KERNELMODE_TIME)
	Total User-Mode Time (TOTAL_USERMODE_TIME)
	User CPU % (USERMODE_PERCENT)
	Wait % (WAIT_TIME_PERCENT)
Terminal Summary (PD_TERM)	CPU % (CPU_PERCENT_USED)
User Summary (PD_USER)
Workgroup Summary (PI_WGRP)

Record generation results when data cannot be collected

The following explains the record generation results when data to be stored in fields cannot be collected:

Records cannot be generated

When PFM - Agent for Platform cannot collect performance data to be stored in the fields defined as ODBC key fields, no records are generated.

Information on terminated processes

Functions for collecting information on terminated processes cannot be used. Therefore, the performance data for the fields shown below cannot be collected.

Table 6-13 Fields for which performance data cannot be collected

Record name	Field name
Process Detail (PD)	Accounting Flags (ACCOUNTING_FLAGS)
	End Time (END_TIME)
	Exit Status (EXIT_STATUS)
	Mem Charge (MEMORY_CHARGE)
Process Detail Interval (PD_PDI)	Accounting Flags (ACCOUNTING_FLAGS)
	End Time (END_TIME)
	Exit Status (EXIT_STATUS)

Notes on reserved records

If PFM - Agent for Platform 07-00 or earlier is upgraded to 08-00 or later, records reserved in 08-00 or later appear in Record in the New Report > Field window of the PFM - Web Console report wizard during history collection setup. These records can be modified. However, if they are modified and then specified for data collection, no records will be collected. The following message is issued to the common message log during the first collection attempt only:

KAVF10600-W An invalid collection event occurred. (record-id, rc=maintenance-code)

Reference note

When you perform a new installation of PFM - Agent for Platform 08-00 or later, the properties of the reserved records are not displayed.

Note on specifying a process name in an alarm condition

When you specify a process name in an alarm condition for the PD_APP or PI_WGRP record, only the string length that is within the range of data that can be collected for the PD record is used to determine the alarm condition. Accordingly, when the process name exceeds the data range as shown in the example below, and you specify *xyz in the alarm condition, the expected condition judgment cannot be performed, since PFM - Agent for Platform does not hold the xyz part. In this case, specify an alarm condition within the range of data that can be collected for the PD record by, for example, specifying abc*.

Example:

abc... xyz (the xyz part is outside the range that can be collected for the PD record)

[Contents][Back][Next]

All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.