HP OpenVMS Systems

HP OpenView Performance Agent for OpenVMS
Dictionary of Operating System Performance Metrics

Print Date 01/2006
OVPA for OpenVMS V1.0 based on Release C.04.00

Copyright (c) 2005,2006 Hewlett-Packard Company, Inc.
All rights reserved.

Introduction:

This dictionary contains definitions of the OpenVMS operating system performance metrics for HP OpenView Performance Agent. This document is divided into the following sections:

"Metric Names by Data Class," which lists the metrics alphabetically by data class. Use these metric names for exporting data with the extract utility. You can also use these metric names in defining alarm conditions in your alarmdef file.
"Metric Definitions," which describes each metric in alphabetical order.

Please note that the metric help has been put in a more generic format and references are made to the other platforms that also support each of the metrics.

Metric Names by Data Class

OpenVMS GLOBAL Metrics
BLANK
DATE
DATE_SECONDS
DAY
INTERVAL
RECORD_TYPE
TIME
YEAR
GBL_ACTIVE_CPU
GBL_ACTIVE_PROC
GBL_ALIVE_PROC
GBL_CPU_IDLE_TIME
GBL_CPU_IDLE_UTIL
GBL_CPU_NICE_TIME
GBL_CPU_NICE_UTIL
GBL_CPU_SYS_MODE_TIME
GBL_CPU_SYS_MODE_UTIL
GBL_CPU_TOTAL_TIME
GBL_CPU_TOTAL_UTIL
GBL_CPU_USER_MODE_TIME
GBL_CPU_USER_MODE_UTIL
GBL_DISK_PHYS_BYTE
GBL_DISK_PHYS_BYTE_RATE
GBL_DISK_PHYS_IO
GBL_DISK_PHYS_IO_RATE
GBL_DISK_PHYS_READ
GBL_DISK_PHYS_READ_BYTE_RATE
GBL_DISK_PHYS_READ_RATE
GBL_DISK_PHYS_WRITE
GBL_DISK_PHYS_WRITE_BYTE_RATE
GBL_DISK_PHYS_WRITE_RATE
GBL_DISK_REQUEST_QUEUE
GBL_DISK_TIME_PEAK
GBL_DISK_UTIL
GBL_DISK_UTIL_PEAK
GBL_FS_SPACE_UTIL_PEAK
GBL_INTERRUPT
GBL_INTERRUPT_RATE
GBL_INTERVAL
GBL_LOADAVG
GBL_LOST_MI_TRACE_BUFFERS
GBL_MEM_CACHE
GBL_MEM_CACHE_UTIL
GBL_MEM_FREE
GBL_MEM_FREE_UTIL
GBL_MEM_PAGEIN
GBL_MEM_PAGEIN_BYTE
GBL_MEM_PAGEIN_BYTE_RATE
GBL_MEM_PAGEIN_RATE
GBL_MEM_PAGEOUT
GBL_MEM_PAGEOUT_BYTE
GBL_MEM_PAGEOUT_BYTE_RATE
GBL_MEM_PAGEOUT_RATE
GBL_MEM_PAGE_REQUEST
GBL_MEM_PAGE_REQUEST_RATE
GBL_MEM_SWAPIN_BYTE
GBL_MEM_SWAPIN_BYTE_RATE
GBL_MEM_SWAPOUT_BYTE
GBL_MEM_SWAPOUT_BYTE_RATE
GBL_MEM_SYS
GBL_MEM_SYS_UTIL
GBL_MEM_USER
GBL_MEM_USER_UTIL
GBL_MEM_UTIL
GBL_NET_COLLISION
GBL_NET_COLLISION_1_MIN_RATE
GBL_NET_COLLISION_PCT
GBL_NET_COLLISION_RATE
GBL_NET_ERROR
GBL_NET_ERROR_1_MIN_RATE
GBL_NET_ERROR_RATE
GBL_NET_IN_ERROR_PCT
GBL_NET_IN_PACKET
GBL_NET_IN_PACKET_RATE
GBL_NET_OUT_ERROR_PCT
GBL_NET_OUT_PACKET
GBL_NET_OUT_PACKET_RATE
GBL_NET_PACKET_RATE
GBL_NFS_CALL
GBL_NFS_CALL_RATE
GBL_NUM_DISK
GBL_NUM_NETWORK
GBL_NUM_USER
GBL_PROC_SAMPLE
GBL_RUN_QUEUE
GBL_STARTED_PROC
GBL_STARTED_PROC_RATE
GBL_STATTIME
GBL_SWAP_SPACE_USED
GBL_SWAP_SPACE_USED_UTIL
GBL_SWAP_SPACE_UTIL
GBL_SYSTEM_UPTIME_HOURS
GBL_SYSTEM_UPTIME_SECONDS
GBL_TT_OVERFLOW_COUNT
TBL_FILE_LOCK_USED
TBL_FILE_LOCK_UTIL
TBL_INODE_CACHE_USED
TBL_SHMEM_ACTIVE
TBL_SHMEM_TABLE_USED
TBL_SHMEM_TABLE_UTIL
TBL_SHMEM_USED

OpenVMS APPLICATION Metrics
BLANK
DATE
DATE_SECONDS
DAY
INTERVAL
RECORD_TYPE
TIME
YEAR
APP_ACTIVE_PROC
APP_ALIVE_PROC
APP_COMPLETED_PROC
APP_CPU_SYS_MODE_TIME
APP_CPU_SYS_MODE_UTIL
APP_CPU_TOTAL_TIME
APP_CPU_TOTAL_UTIL
APP_CPU_USER_MODE_TIME
APP_CPU_USER_MODE_UTIL
APP_MAJOR_FAULT
APP_MAJOR_FAULT_RATE
APP_MEM_RES
APP_MEM_UTIL
APP_MEM_VIRT
APP_MINOR_FAULT
APP_MINOR_FAULT_RATE
APP_NAME
APP_NUM
APP_PRI
APP_PROC_RUN_TIME
APP_SAMPLE

OpenVMS PROCESS Metrics
BLANK
DATE
DATE_SECONDS
DAY
INTERVAL
RECORD_TYPE
TIME
YEAR
PROC_APP_ID
PROC_CPU_SYS_MODE_TIME
PROC_CPU_SYS_MODE_UTIL
PROC_CPU_TOTAL_TIME
PROC_CPU_TOTAL_TIME_CUM
PROC_CPU_TOTAL_UTIL
PROC_CPU_TOTAL_UTIL_CUM
PROC_CPU_USER_MODE_TIME
PROC_CPU_USER_MODE_UTIL
PROC_EUID
PROC_GROUP_ID
PROC_INTEREST
PROC_INTERVAL_ALIVE
PROC_MAJOR_FAULT
PROC_MEM_RES
PROC_MEM_VIRT
PROC_MINOR_FAULT
PROC_PAGEFAULT
PROC_PAGEFAULT_RATE
PROC_PARENT_PROC_ID
PROC_PRI
PROC_PROC_ARGV1
PROC_PROC_ID
PROC_PROC_NAME
PROC_RUN_TIME
PROC_STOP_REASON
PROC_THREAD_COUNT
PROC_TTY
PROC_USER_NAME

OpenVMS DISK Metrics
BLANK
DATE
DATE_SECONDS
DAY
INTERVAL
RECORD_TYPE
TIME
YEAR
BYDSK_AVG_REQUEST_QUEUE
BYDSK_AVG_SERVICE_TIME
BYDSK_DEVNAME
BYDSK_DIRNAME
BYDSK_ID
BYDSK_PHYS_BYTE
BYDSK_PHYS_BYTE_RATE
BYDSK_PHYS_IO
BYDSK_PHYS_IO_RATE
BYDSK_PHYS_READ
BYDSK_PHYS_READ_BYTE
BYDSK_PHYS_READ_BYTE_RATE
BYDSK_PHYS_READ_RATE
BYDSK_PHYS_WRITE
BYDSK_PHYS_WRITE_BYTE
BYDSK_PHYS_WRITE_BYTE_RATE
BYDSK_PHYS_WRITE_RATE
BYDSK_REQUEST_QUEUE
BYDSK_UTIL

OpenVMS NETWORK INTERFACE Metrics
BLANK
DATE
DATE_SECONDS
DAY
INTERVAL
RECORD_TYPE
TIME
YEAR
BYNETIF_COLLISION
BYNETIF_COLLISION_1_MIN_RATE
BYNETIF_COLLISION_RATE
BYNETIF_ERROR
BYNETIF_ERROR_1_MIN_RATE
BYNETIF_ERROR_RATE
BYNETIF_ID
BYNETIF_IN_BYTE
BYNETIF_IN_BYTE_RATE
BYNETIF_IN_BYTE_RATE_CUM
BYNETIF_IN_PACKET
BYNETIF_IN_PACKET_RATE
BYNETIF_NAME
BYNETIF_OUT_BYTE
BYNETIF_OUT_BYTE_RATE
BYNETIF_OUT_BYTE_RATE_CUM
BYNETIF_OUT_PACKET
BYNETIF_OUT_PACKET_RATE
BYNETIF_PACKET_RATE

OpenVMS CPU Metrics
BLANK
DATE
DATE_SECONDS
DAY
INTERVAL
RECORD_TYPE
TIME
YEAR
BYCPU_CPU_CLOCK
BYCPU_CPU_SYS_MODE_TIME
BYCPU_CPU_SYS_MODE_UTIL
BYCPU_CPU_TOTAL_TIME
BYCPU_CPU_TOTAL_UTIL
BYCPU_CPU_USER_MODE_TIME
BYCPU_CPU_USER_MODE_UTIL
BYCPU_ID
BYCPU_INTERRUPT
BYCPU_INTERRUPT_RATE
BYCPU_STATE

OpenVMS FILESYSTEM Metrics
BLANK
DATE
DATE_SECONDS
DAY
INTERVAL
RECORD_TYPE
TIME
YEAR
FS_BLOCK_SIZE
FS_DEVNAME
FS_DEVNO
FS_DIRNAME
FS_FRAG_SIZE
FS_INODE_UTIL
FS_MAX_INODES
FS_MAX_SIZE
FS_SPACE_RESERVED
FS_SPACE_USED
FS_SPACE_UTIL
FS_TYPE

OpenVMS CONFIGURATION Metrics
BLANK
DATE
DATE_SECONDS
DAY
INTERVAL
RECORD_TYPE
TIME
YEAR
GBL_BOOT_TIME
GBL_COLLECTOR
GBL_CPU_CLOCK
GBL_DISTRIBUTION
GBL_GMTOFFSET
GBL_LOGFILE_VERSION
GBL_LOGGING_TYPES
GBL_MACHINE
GBL_MACHINE_MODEL
GBL_MEM_AVAIL
GBL_MEM_PHYS
GBL_NUM_APP
GBL_NUM_CPU
GBL_NUM_DISK
GBL_NUM_NETWORK
GBL_OSKERNELTYPE_INT
GBL_OSNAME
GBL_OSRELEASE
GBL_OSVERSION
GBL_SUBPROCSAMPLEINTERVAL
GBL_SWAP_SPACE_AVAIL
GBL_SWAP_SPACE_AVAIL_KB
GBL_SYSTEM_ID
GBL_THRESHOLD_CPU
GBL_THRESHOLD_NOKILLED
GBL_THRESHOLD_NONEW
GBL_THRESHOLD_PROCMEM
TBL_FILE_LOCK_AVAIL
TBL_INODE_CACHE_AVAIL
TBL_SHMEM_TABLE_AVAIL

METRIC DEFINITIONS

APP_ACTIVE_PROC

An active process is one that exists and consumes some CPU time. APP_ACTIVE_PROC is the sum of the alive-process-time/intervaltime ratios of every process belonging to an application that is active (uses any CPU time) during an interval.

The following diagram of a four second interval showing two processes, A and B, for an application should be used to understand the above definition. Note the difference between active processes, which consume CPU time, and alive processes which merely exist on the system.

     ----------- Seconds -----------

       1         2         3      4 

Proc

---- ----      ----      ----   ----

A    live      live      live   live

B    live/CPU  live/CPU  live   dead

Process A is alive for the entire four second interval, but consumes no CPU. A's contribution to APP_ALIVE_PROC is 4*1/4. A contributes 0*1/4 to APP_ACTIVE_PROC. B's contribution to APP_ALIVE_PROC is 3*1/4. B contributes 2*1/4 to APP_ACTIVE_PROC. Thus, for this interval, APP_ACTIVE_PROC equals 0.5 and APP_ALIVE_PROC equals 1.75.

Because a process may be alive but not active, APP_ACTIVE_PROC will always be less than or equal to APP_ALIVE_PROC.

This metric indicates the number of processes in an application group that are competing for the CPU. This metric is useful, along with other metrics, for comparing loads placed on the system by different groups of processes.

On non HP-UX systems, this metric is derived from sampled process data. Since the data for a process is not available after the process has died on this operating system, a process whose life is shorter than the sampling interval may not be seen when the samples are taken. Thus this metric may be slightly less than the actual value. Increasing the sampling frequency captures a more accurate count, but the overhead of collection may also rise.

APP_ALIVE_PROC

An alive process is one that exists on the system. APP_ALIVE_PROC is the sum of the alive-process-time/interval-time ratios for every process belonging to a given application.

     ----------- Seconds -----------

       1         2         3      4 

Proc

---- ----      ----      ----   ----

A    live      live      live   live

B    live/CPU  live/CPU  live   dead

Process A is alive for the entire four second interval but consumes no CPU. A's contribution to APP_ALIVE_PROC is 4*1/4. A contributes 0*1/4 to APP_ACTIVE_PROC. B's contribution to APP_ALIVE_PROC is 3*1/4. B contributes 2*1/4 to APP_ACTIVE_PROC. Thus, for this interval, APP_ACTIVE_PROC equals 0.5 and APP_ALIVE_PROC equals 1.75.

Because a process may be alive but not active, APP_ACTIVE_PROC will always be less than or equal to APP_ALIVE_PROC.

APP_COMPLETED_PROC

The number of processes in this group that completed during the interval.

APP_CPU_SYS_MODE_TIME

The time, in seconds, during the interval that the CPU was in system mode for processes in this group.

A process operates in either system mode (also called kernel mode on Unix or privileged mode on Windows) or user mode. When a process requests services from the operating system with a system call, it switches into the machine's privileged protection mode and runs in system mode.

On a system with multiple CPUs, this metric is normalized. That is, the CPU used over all processors is divided by the number of processors online. This represents the usage of the total processing capacity available.

APP_CPU_SYS_MODE_UTIL

The percentage of time during the interval that the CPU was used in system mode for processes in this group.

High system CPU utilizations are normal for IO intensive groups. Abnormally high system CPU utilization can indicate that a hardware problem is causing a high interrupt rate. It can also indicate programs that are not making efficient system calls.

APP_CPU_TOTAL_TIME

The total CPU time, in seconds, devoted to processes in this group during the interval.

APP_CPU_TOTAL_UTIL

The percentage of the total CPU time devoted to processes in this group during the interval. This indicates the relative CPU load placed on the system by processes in this group.

Large values for this metric may indicate that this group is causing a CPU bottleneck. This would be normal in a computationbound workload, but might mean that processes are using excessive CPU time and perhaps looping.

If the "other" application shows significant amounts of CPU, you may want to consider tuning your parm file so that process activity is accounted for in known applications.

   APP_CPU_TOTAL_UTIL =
     APP_CPU_SYS_MODE_UTIL + APP_CPU_USER_MODE_UTIL

NOTE: On Windows, the sum of the APP_CPU_TOTAL_UTIL metrics may not equal GBL_CPU_TOTAL_UTIL. Microsoft states that "this is expected behavior" because the GBL_CPU_TOTAL_UTIL metric is taken from the NT performance library Processor objects while the APP_CPU_TOTAL_UTIL metrics are taken from the Process objects. Microsoft states that there can be CPU time accounted for in the Processor system objects that may not be seen in the Process objects.

APP_CPU_USER_MODE_TIME

The time, in seconds, that processes in this group were in user mode during the interval.

User CPU is the time spent in user mode at a normal priority, at real-time priority (on HP-UX, AIX, and Windows systems), and at a nice priority.

APP_CPU_USER_MODE_UTIL

The percentage of time that processes in this group were using the CPU in user mode during the interval.

User CPU is the time spent in user mode at a normal priority, at real-time priority (on HP-UX, AIX, and Windows systems), and at a nice priority.

High user mode CPU percentages are normal for computationintensive groups. Low values of user CPU utilization compared to relatively high values for APP_CPU_SYS_MODE_UTIL can indicate a hardware problem or improperly tuned programs in this group.

APP_MAJOR_FAULT

The number of major page faults that required a disk IO for processes in this group during the interval.

APP_MAJOR_FAULT_RATE

The number of major page faults per second that required a disk IO for processes in this group during the interval.

APP_MEM_RES

On Unix systems, this is the size (in KB) of resident memory for processes in this group that were alive at the end of the interval. This consists of text, data, stack, as well as the process' portion of shared memory regions (such as, shared libraries, text segments, and shared data).

On HP-UX, for each process, resident memory (RSS) is calculated as

   RSS = sum of private region pages +
         (sum of shared region pages / number of references)

The number of references is a count of the number of attachments to the memory region. Attachments, for shared regions, may come from several processes sharing the same memory, a single process with multiple attachments, or combinations of these.

This value is only updated when a process uses CPU. Thus, under memory pressure, this value may be higher than the actual amount of resident memory for processes which are idle.

Refer to the help text for PROC_MEM_RES for additional information.

On Windows, this is the sum of the size (in KB) of the working sets for processes in this group during the interval. The working set counts memory pages referenced recently by the threads making up this group. Note that the size of the working set is often larger than the amount of pagefile space consumed.

APP_MEM_UTIL

On Unix systems, this is the approximate percentage of the system's physical memory used as resident memory by processes in this group that were alive at the end of the interval. This metric summarizes process private and shared memory in each application.

On Windows, this is an estimate of the percentage of the system's physical memory allocated for working set memory by processes in this group during the interval.

On HP-UX, this consists of text, data, stack, as well the process' portion of shared memory regions (such as, shared libraries, text segments, and shared data). The sum of the shared region pages is divided by the number of references.

On all other Unix systems, this consists of text, data, stack, as well as an estimate of the process' portion of shared memory.

On Unix systems, each application's total resident memory is summed. This value is then divided by the summed total of all applications resident memory and then multiplied by the ratio of available user memory versus total physical memory to arrive at a calculated percent of total physical memory. It must be remembered, however, that this is a calculated metric that shows the approximate percentage of the physical memory used as resident memory by the processes in this application during the interval.

On Windows, the sum of the working set sizes for each process in this group is kept as APP_MEM_RES. This value is divided by the sum of APP_MEM_RES for all applications defined on the system to come up with a ratio of this application's working set size to the total. This value is then multiplied by the ratio of available user memory versus total physical memory to arrive at a calculated percent of total physical memory.

This metric is not available for HP-UX MeasureWare Agent. It is available for HP-UX GlancePlus.

APP_MEM_VIRT

On Unix systems, this is the approximate size (in KB) of virtual memory for processes in this group that were alive at the end of the interval.

On Windows, this is the size (in KB) of paging file space used for processes in this group during the interval. This is the sum of the pagefile space used for all processes in this group. Groups of processes may have working set sizes (APP_MEM_RES) larger than the size of their pagefile space.

On AIX, this is the sum of the virtual memory region sizes for all processes in this group.

On all other Unix systems, this is the sum of the virtual memory region sizes for all processes in this group. Since this virtual memory size for each process includes shared regions, such as library text and data, the shared regions are counted multiple times in this metric. For example, if two processes are attached to a 10MB shared region, then 20MB is reported in this metric.

On Unix systems, this value is not affected by the reference count. As such, this metric can overestimate the virtual memory being used by processes in this group when they share memory regions.

APP_MINOR_FAULT

The number of minor page faults satisfied in memory (a page was reclaimed from one of the free lists) for processes in this group during the interval.

APP_MINOR_FAULT_RATE

The number of minor page faults per second satisfied in memory (pages were reclaimed from one of the free lists) for processes in this group during the interval.

APP_NAME

The name of the application (up to 20 characters). This comes from the parm file where the applications are defined.

The application called "other" captures all processes not aggregated into applications specifically defined in the parm file. In other words, if no applications are defined in the parm file, then all process data would be reflected in the "other" application.

APP_NUM

The sequentially assigned number of this application.

APP_PRI

On Unix systems, this is the average priority of the processes in this group during the interval.

On Windows, this is the average base priority of the processes in this group during the interval.

APP_PROC_RUN_TIME

The average run time for processes in this group that completed during the interval.

APP_SAMPLE

The number of samples of process data that have been averaged or accumulated during this sample.

BLANK

An empty field used for spacing reports. For example, this field can be used to create a blank column in a spreadsheet that may be used to sum several items.

BYCPU_CPU_CLOCK

The clock speed of the CPU in the current slot. The clock speed is in MHz for the selected CPU.

BYCPU_CPU_SYS_MODE_TIME

The time, in seconds, that this CPU was in system mode during the interval.

BYCPU_CPU_SYS_MODE_UTIL

The percentage of time that this CPU was in system mode during the interval.

BYCPU_CPU_TOTAL_TIME

The total time, in seconds, that this CPU was not idle during the interval.

BYCPU_CPU_TOTAL_UTIL

The percentage of time that this CPU was not idle during the interval.

BYCPU_CPU_USER_MODE_TIME

The time, in seconds, during the interval that this CPU was in user mode.

User CPU is the time spent in user mode at a normal priority, at real-time priority (on HP-UX, AIX, and Windows systems), and at a nice priority.

BYCPU_CPU_USER_MODE_UTIL

The percentage of time that this CPU was in user mode during the interval.

User CPU is the time spent in user mode at a normal priority, at real-time priority (on HP-UX, AIX, and Windows systems), and at a nice priority.

BYCPU_ID

The ID number of this CPU. On some Unix systems, such as SUN, CPUs are not sequentially numbered.

BYCPU_INTERRUPT

The number of device interrupts for this CPU during the interval.

BYCPU_INTERRUPT_RATE

The average number of device interrupts per second for this CPU during the interval.

On HP-UX, a value of "na" is displayed on a system with multiple CPUs.

BYCPU_STATE

A text string indicating the current state of a processor.

On HP-UX, this is either "enabled", "disabled" or "unknown". On all other systems, this is either "Offline", "Online" or "Unknown".

BYDSK_AVG_REQUEST_QUEUE

The average number of IO requests that were in the wait and service queues for this disk device over the cumulative collection time.

The cumulative collection time is defined from the point in time when either: a) the process (or kernel thread, if HP-UX) was first started, or b) the performance tool was first started, or c) the cumulative counters were reset (relevant only to GlancePlus, if available for the given platform), whichever occurred last.

For example, if 4 intervals have passed with average queue lengths of 0, 2, 0, and 6, then the average number of IO requests over all intervals would be 2.

Some Linux kernels, typically 2.2 and older kernels, do not support the instrumentation needed to provide values for this metric. This metric will be "na" on the affected kernels. The "sar -d" command will also not be present on these systems. Distributions and OS releases that are known to be affected include: TurboLinux 7, SuSE 7.2, and Debian 3.0.

BYDSK_AVG_SERVICE_TIME

The average time, in milliseconds, that this disk device spent processing each disk request during the interval. For example, a value of 5.14 would indicate that disk requests during the last interval took on average slightly longer than five onethousandths of a second to complete for this device.

This is a measure of the speed of the disk, because slower disk devices typically show a larger average service time. Average service time is also dependent on factors such as the distribution of I/O requests over the interval and their locality. It can also be influenced by disk driver and controller features such as I/O merging and command queueing. Note that this service time is measured from the perspective of the kernel, not the disk device itself. For example, if a disk device can find the requested data in its cache, the average service time could be quicker than the speed of the physical disk hardware.

This metric can be used to help determine which disk devices are taking more time than usual to process requests.

BYDSK_DEVNAME

The name of this disk device.

On HP-UX, the name identifying the specific disk spindle is the hardware path which specifies the address of the hardware components leading to the disk device.

On SUN, CDs and disks use the device name compliant with the SVR4 Interface Definition and the slice (partition) number is replaced with an asterisk. An example of a device name is "c0t3d0s*". These names are the same disk names displayed by "iostat'. Floppy devices are labeled with the device file name link from the /dev directory where "#" specifies a floppy device instance. See the man page for "disks" if your device labels are not SVID format. For more information about "instances", see the "path_to_inst" man page.

On AIX, this is the path name string of this disk device. This is the fsname parameter in the mount(1M) command. If more than one file system is contained on a device (that is, the device is partitioned), this is indicated by an asterisk ("*") at the end of the path name.

On OSF1, this is the path name string of this disk device. This is the file-system parameter in the mount(1M) command.

On Windows, this is the unit number of this disk device.

BYDSK_DIRNAME

The name of the file system directory mounted on this disk device. If more than one file system is mounted on this device, "Multiple FS" is seen.

BYDSK_ID

The ID of the current disk device. This is an identification number assigned to the disk device by scope.

BYDSK_PHYS_BYTE

The number of KBs of physical IOs transferred to or from this disk device during the interval.

On Unix systems, this includes all types of physical disk IOs including file system, virtual memory, and raw IO. The average KB transferred to or from the current disk device during the interval.

BYDSK_PHYS_BYTE_RATE

The average KBs per second transferred to or from this disk device during the interval.

On Unix systems, this includes all types of physical disk IOs including file system, virtual memory, and raw IOs.

BYDSK_PHYS_IO

The number of physical IOs for this disk device during the interval.

BYDSK_PHYS_IO_RATE

The average number of physical IO requests per second for this disk device during the interval.

On Unix systems, this counts disk reads and writes of all types, including virtual memory and raw IO.

BYDSK_PHYS_READ

The number of physical reads for this disk device during the interval.

On AIX, this is an estimated value based on the ratio of read bytes to total bytes transferred. The actual number of reads is not tracked by the kernel. This is calculated as

   BYDSK_PHYS_READ =
     BYDSK_PHYS_IO * (BYDSK_PHYS_READ_BYTE / BYDSK_PHYS_IO_BYTE)

BYDSK_PHYS_READ_BYTE

The KBs transferred from this disk device during the interval.

On Unix systems, all types of disk reads are counted, including file system, virtual memory, and raw IO.

BYDSK_PHYS_READ_BYTE_RATE

The average KBs per second transferred from this disk device during the interval.

On Unix systems, all types of disk reads are counted, including file system, virtual memory, and raw IO.

On OpenVMS, data will only be available when the disk has at approximately 30 read I/Os per interval.

BYDSK_PHYS_READ_RATE

The average number of physical reads per second for this disk device during the interval.

On AIX, this is an estimated value based on the ratio of read bytes to total bytes transferred. The actual number of reads is not tracked by the kernel. This is calculated as

   BYDSK_PHYS_READ_RATE =
     BYDSK_PHYS_IO_RATE * (BYDSK_PHYS_READ_BYTE / BYDSK_PHYS_IO_BYTE)

BYDSK_PHYS_WRITE

The number of physical writes for this disk device during the interval.

On AIX, this is an estimated value based on the ratio of write bytes to total bytes transferred because the actual number of writes is not tracked by the kernel. This is calculated as

   BYDSK_PHYS_WRITE =
     BYDSK_PHYS_IO * (BYDSK_PHYS_WRITE_BYTE / BYDSK_PHYS_IO_BYTE)

BYDSK_PHYS_WRITE_BYTE

The KBs transferred to this disk device during the interval.

On Unix systems, all types of disk writes are counted, including file system, virtual memory, and raw IO.

BYDSK_PHYS_WRITE_BYTE_RATE

The average KBs per second transferred to this disk device during the interval.

On Unix systems, all types of disk writes are counted, including file system, virtual memory, and raw IO.

On OpenVMS, data will only be available when the disk has at approximately 30 write I/Os per interval.

BYDSK_PHYS_WRITE_RATE

The average number of physical writes per second for this disk device during the interval.

On AIX, this is an estimated value based on the ratio of write bytes to total bytes transferred. The actual number of writes is not tracked by the kernel. This is calculated as

   BYDSK_PHYS_WRITE_RATE =
     BYDSK_PHYS_IO_RATE * (BYDSK_PHYS_WRITE_BYTE / BYDSK_PHYS_IO_BYTE)

BYDSK_REQUEST_QUEUE

The average number of IO requests that were in the wait queue for this disk device during the interval. These requests are the physical requests (as opposed to logical IO requests).

BYDSK_UTIL

On HP-UX, this is the percentage of the time during the interval that the disk device had IO in progress from the point of view of the Operating System. In other words, the utilization or percentage of time busy servicing requests for this device.

On the non-HP-UX systems, this is the percentage of the time that this disk device was busy transferring data during the interval.

This is a measure of the ability of the IO path to meet the transfer demands being placed on it. Slower disk devices may show a higher utilization with lower IO rates than faster disk devices such as disk arrays. A value of greater than 50% utilization over time may indicate that this device or its IO path is a bottleneck, and the access pattern of the workload, database, or files may need reorganizing for better balance of disk IO load.

On OpenVMS, data will only be available when the disk has a non-zero read/write I/Os per interval.

DATE

The date the information in this record was captured, based on local time. The date is an ASCII field in mm/dd/yy format unless localized. If localized, the separators may be different and the subfield may be in a different sequence. In ASCII files this field will always contain 8 characters. Each subfield (mm, dd, yy) will contain a leading zero if the value is less than 10. This metric is extracted from GBL_STATTIME, which is obtained using the time() system call at the time of data collection.

This field responds to language localization. For example, in Germany the field would appear as dd.mm.yy and in Italy it would be dd/mm/yy.

In binary files this field is in MPE CALENDAR format in the least significant 16 bits of the field. The most significant 16 bits should all be zero. Dividing the field by 512 will isolate the year (that is, 94). This field MOD 512 will isolate the day of the year.

DATE_SECONDS

The time that the data in this record was captured, expressed in seconds since January 1, 1970, based on local time. This is related to the standard time-stamp returned by the unix system call time(), but has had the local time zone correction applied.

DAY

The julian day of the year that the data in this record was captured. This metric is extracted from GBL_STATTIME.

BYNETIF_COLLISION

The number of physical collisions that occurred on the network interface during the interval. A rising rate of collisions versus outbound packets is an indication that the network is becoming increasingly congested. This metric does not currently include deferred packets.

This data is not collected for non-broadcasting devices, such as loopback (lo), and is always zero.

For HP-UX 10.20 and other Unix systems, this is the same as the sum of the "Coll" column from the "netstat -i" command for a network device. See also netstat(1).

For HP-UX 11.0 and beyond, this metric will be the same as the sum of the "Single Collision Frames", "Multiple Collision Frames", "Late Collisions", and "Excessive Collisions" values from the output of the "lanadmin" utility for the network interface. Remember that "lanadmin" reports cumulative counts. For this release and beyond, "netstat -i" shows network activity on the logical level (IP) only.

AIX does not support the collision count for ethernet interface. The collision count is supported for token ring (tr) and loopback (lo) interface.

Physical statistics are packets recorded by the network drivers. These numbers most likely will not be the same as the logical statistics. The values returned for the loopback interface will show "na" for the physical statistics since there is no network driver activity.

Logical statistics are packets seen only by the Interface Protocol (IP) layer of the networking subsystem. Not all packets seen by IP will go out and come in through a network driver. Examples cases are the 127.0.0.1 (loopback interface). Pings or other network generating commands (ftp, rlogin, and so forth) to 127.0.0.1 will not change physical driver statistics. Pings to IP addresses on remote systems will change physical driver statistics.

On HP-UX 10.20, commands addressed to the local host always went down to the driver and the logical and physical counters were always updated.

This metric is updated at the sampling interval, regardless of the number of IP addresses on the system.

BYNETIF_COLLISION_1_MIN_RATE

The number of physical collisions per minute on the network interface during the interval. A rising rate of collisions versus outbound packets is an indication that the network is becoming increasingly congested. This metric does not currently include deferred packets.

This data is not collected for non-broadcasting devices, such as loopback (lo), and is always zero.

On HP-UX 10.20, commands addressed to the local host always went down to the driver and the logical and physical counters were always updated.

This metric is updated at the sampling interval, regardless of the number of IP addresses on the system.

BYNETIF_COLLISION_RATE

The number of physical collisions per second on the network interface during the interval. A rising rate of collisions versus outbound packets is an indication that the network is becoming increasingly congested. This metric does not currently include deferred packets.

This data is not collected for non-broadcasting devices, such as loopback (lo), and is always zero.

On HP-UX 10.20, commands addressed to the local host always went down to the driver and the logical and physical counters were always updated.

This metric is updated at the sampling interval, regardless of the number of IP addresses on the system.

BYNETIF_ERROR

The number of physical errors that occurred on the network interface during the interval. An increasing number of errors may indicate a hardware problem in the network.

On Unix systems, this data is not available for loop-back (lo) devices and is always zero.

For HP-UX 10.20 and other Unix systems, this is the same as the sum of "Ierrs" (RX errors: or RX-ERR on Linux) and "Oerrs" (TX errors: or TX-ERR on Linux) from the "netstat -i" command for a network device. See also netstat(1).

For HP-UX 11.0 and beyond, this metric will be the same as the sum of the "Inbound Errors" and "Outbound Errors" values from the output of the "lanadmin" utility for the network interface. Remember that "lanadmin" reports cumulative counts. For this release and beyond, "netstat -i" shows network activity on the logical level (IP) only.

On HP-UX 10.20, commands addressed to the local host always went down to the driver and the logical and physical counters were always updated.

This metric is updated at the sampling interval, regardless of the number of IP addresses on the system.

BYNETIF_ERROR_1_MIN_RATE

The number of physical errors per minute on the network interface during the interval.

On Unix systems, this data is not available for loop-back (lo) devices and is always zero.

On HP-UX 10.20, commands addressed to the local host always went down to the driver and the logical and physical counters were always updated.

This metric is updated at the sampling interval, regardless of the number of IP addresses on the system.

BYNETIF_ERROR_RATE

The number of physical errors per second on the network interface during the interval.

On Unix systems, this data is not available for loop-back (lo) devices and is always zero.

On HP-UX 10.20, commands addressed to the local host always went down to the driver and the logical and physical counters were always updated.

This metric is updated at the sampling interval, regardless of the number of IP addresses on the system.

BYNETIF_ID

The ID number of the network interface.

BYNETIF_IN_BYTE

The number of KBs received from the network via this interface during the interval. Only the bytes in packets that carry data are included in this rate.

On HP-UX 10.20, commands addressed to the local host always went down to the driver and the logical and physical counters were always updated.

This metric is updated at the sampling interval, regardless of the number of IP addresses on the system.

This metric is available on HP-UX 11.0 and beyond.

BYNETIF_IN_BYTE_RATE

The number of KBs per second received from the network via this interface during the interval. Only the bytes in packets that carry data are included in this rate.

On HP-UX 10.20, commands addressed to the local host always went down to the driver and the logical and physical counters were always updated.

This metric is updated at the sampling interval, regardless of the number of IP addresses on the system.

This metric is available on HP-UX 11.0 and beyond.

BYNETIF_IN_BYTE_RATE_CUM

The average number of KBs per second received from the network via this interface over the cumulative collection time. Only the bytes in packets that carry data are included in this rate.

On HP-UX 10.20, commands addressed to the local host always went down to the driver and the logical and physical counters were always updated.

This metric is updated at the sampling interval, regardless of the number of IP addresses on the system.

This metric is available on HP-UX 11.0 and beyond.

BYNETIF_IN_PACKET

The number of successful physical packets received through the network interface during the interval. Successful packets are those that have been processed without errors or collisions.

For HP-UX 10.20 and other Unix systems, this is the same as the sum of the "Ipkts" column (or RX on Linux) from the "netstat -i" command for a network device. See also netstat(1).

For HP-UX 11.0 and beyond, this metric will be the same as the sum of the "Inbound Unicast Packets" and "Inbound Non-Unicast Packets" values from the output of the "lanadmin" utility for the network interface. Remember that "lanadmin" reports cumulative counts. For this release and beyond, "netstat -i" shows network activity on the logical level (IP) only.

On HP-UX 10.20, commands addressed to the local host always went down to the driver and the logical and physical counters were always updated.

This metric is updated at the sampling interval, regardless of the number of IP addresses on the system.

BYNETIF_IN_PACKET_RATE

The number of successful physical packets per second received through the network interface during the interval. Successful packets are those that have been processed without errors or collisions.

On HP-UX 10.20, commands addressed to the local host always went down to the driver and the logical and physical counters were always updated.

This metric is updated at the sampling interval, regardless of the number of IP addresses on the system.

BYNETIF_NAME

The name of the network interface.

For HP-UX 11.0 and beyond, these are the same names that appear in the "Description" field of the "lanadmin" command output.

On all other Unix systems, these are the same names that appear in the "Name" column of the "netstat -i" command.

Some examples of device names are:

lo - loop-back driver
ln - Standard Ethernet driver
en - Standard Ethernet driver
le - Lance Ethernet driver
ie - Intel Ethernet driver
tr - Token-Ring driver
et - Ether Twist driver
bf - fiber optic driver

All of the device names will have the unit number appended to the name. For example, a loop-back device in unit 0 will be "lo0".

BYNETIF_OUT_BYTE

The number of KBs sent to the network via this interface during the interval. Only the bytes in packets that carry data are included in this rate.

On HP-UX 10.20, commands addressed to the local host always went down to the driver and the logical and physical counters were always updated.

This metric is updated at the sampling interval, regardless of the number of IP addresses on the system.

This metric is available on HP-UX 11.0 and beyond.

BYNETIF_OUT_BYTE_RATE

The number of KBs per second sent to the network via this interface during the interval. Only the bytes in packets that carry data are included in this rate.

On HP-UX 10.20, commands addressed to the local host always went down to the driver and the logical and physical counters were always updated.

This metric is updated at the sampling interval, regardless of the number of IP addresses on the system.

This metric is available on HP-UX 11.0 and beyond.

BYNETIF_OUT_BYTE_RATE_CUM

The average number of KBs per second sent to the network via this interface over the cumulative collection time. Only the bytes in packets that carry data are included in this rate.

On HP-UX 10.20, commands addressed to the local host always went down to the driver and the logical and physical counters were always updated.

This metric is updated at the sampling interval, regardless of the number of IP addresses on the system.

This metric is available on HP-UX 11.0 and beyond.

BYNETIF_OUT_PACKET

The number of successful physical packets sent through the network interface during the interval. Successful packets are those that have been processed without errors or collisions.

For HP-UX 10.20 and other Unix systems, this is the same as the sum of the "Opkts" column (or TX on Linux) from the "netstat -i" command for a network device. See also netstat(1).

For HP-UX 11.0 and beyond, this metric will be the same as the sum of the "Outbound Unicast Packets" and "Outbound Non-Unicast Packets" values from the output of the "lanadmin" utility for the network interface. Remember that "lanadmin" reports cumulative counts. For this release and beyond, "netstat -i" shows network activity on the logical level (IP) only.

On HP-UX 10.20, commands addressed to the local host always went down to the driver and the logical and physical counters were always updated.

This metric is updated at the sampling interval, regardless of the number of IP addresses on the system.

BYNETIF_OUT_PACKET_RATE

The number of successful physical packets per second sent through the network interface during the interval. Successful packets are those that have been processed without errors or collisions.

On HP-UX 10.20, commands addressed to the local host always went down to the driver and the logical and physical counters were always updated.

This metric is updated at the sampling interval, regardless of the number of IP addresses on the system.

BYNETIF_PACKET_RATE

The number of successful physical packets per second sent and received through the network interface during the interval. Successful packets are those that have been processed without errors or collisions.

On HP-UX 10.20, commands addressed to the local host always went down to the driver and the logical and physical counters were always updated.

This metric is updated at the sampling interval, regardless of the number of IP addresses on the system.

FS_BLOCK_SIZE

The maximum block size of this file system, in bytes.

On HP-UX, a value of "na" is displayed if the file system is not mounted.

On the other Unix systems, a value of "na" is displayed when the file system is no longer mounted. If the product is restarted, these unmounted file systems are not displayed until remounted.

FS_DEVNO

On Unix systems, this is the major and minor number of the file system.

On Windows, this is the unit number of the disk device on which the logical disk resides.

FS_DEVNAME

On Unix systems, this is the path name string of the current device.

On Windows, this is the disk drive string of the current device.

On HP-UX, this is the "fsname" parameter in the mount(1M) command. For NFS devices, this includes the name of the node exporting the file system. It is possible that a process may mount a device using the mount(2) system call. This call does not update the "/etc/mnttab" and its name is blank. This situation is rare, and should be corrected by syncer(1M). Note that once a device is mounted, its entry is displayed, even after the device is unmounted, until the midaemon process terminates.

On SUN, this is the path name string of the current device, or "tmpfs" for memory based file systems. See tmpfs(7).

FS_DIRNAME

On Unix systems, this is the path name of the mount point of the file system.

On Windows, this is the drive letter associated with the selected disk partition.

On HP-UX, if the logical volume has a mounted file system. This is the directory parameter of the mount(1M) command for most entries. Exceptions are:

For lvm swap areas, this field contains "lvm swap device".
For logical volumes with no mounted file systems, this field contains "Raw Logical Volume" (relevant only to MeasureWare Agent).

On HP-UX, the file names are in the same order as shown in the "/usr/sbin/mount -p" command. File systems are not displayed until they exhibit IO activity once the midaemon has been started. Also, once a device is displayed, it continues to be displayed (even after the device is unmounted) until the midaemon process terminates.

On SUN, only "UFS", "HSFS" and "TMPFS" file systems are listed. See mount(1M) and mnttab(4). "TMPFS" file systems are memory based filesystems and are listed here for convenience. See tmpfs(7).

On AIX, see mount(1M) and filesystems(4). On OSF1, see mount(2).

FS_FRAG_SIZE

The fundamental file system block size, in bytes.

On HP-UX, a value of "na" is displayed if the file system is not mounted.

On the other Unix systems, a value of "na" is displayed when the file system is no longer mounted. If the product is restarted, these unmounted file systems are not displayed until remounted.

FS_INODE_UTIL

Percentage of this file system's inodes in use during the interval.

On SUN, a value of "na" is displayed when the file system is no longer mounted. If the product is restarted, these unmounted file systems are not displayed until remounted.

On OpenVMS this is metric is calculated by dividing the disk used space by the disk cluster size and then dividing that number by the maximum disk size divided by the disk cluster size. Note that on OpenVMS inode concept does not apply. The value used is an OpenVMS specific metric.

FS_MAX_INODES

Number of configured file system inodes.

On SUN, a value of "na" is displayed when the file system is no longer mounted. If the product is restarted, these unmounted file systems are not displayed until remounted.

On OpenVMS, this metric is calculated by dividing the maximum disk size by the disk cluster size. This metric is used in the FS_MAX_INODES calculation above.

FS_MAX_SIZE

Maximum number that this file system could obtain if full, in MB.

On HP-UX, this metric is updated at 4 minute intervals to minimize collection overhead. Note that this is the user space capacity - it is the file system space accessible to non root users. The bdf command shows the total file system capacity which includes the extra file system space accessible to root users only.

For HP-UX 10.20 and beyond, a value of "na" may be displayed if the file system is not mounted.

On SUN, a value of "na" is displayed when the file system is no longer mounted. If the product is restarted, these unmounted file systems are not displayed until remounted.

On OpenVMS, this metric is based on the minimum file size, which is the disk cluster size.

FS_SPACE_RESERVED

The amount of file system space in MBs reserved for superuser allocation.

FS_SPACE_USED

The amount of file system space in MBs that is being used.

FS_SPACE_UTIL

Percentage of the file system space in use during the interval.

For HP-UX 10.20 and beyond, a value of "na" may be displayed if the file system is not mounted.

On SUN, a value of "na" is displayed when the file system is no longer mounted. If the product is restarted, these unmounted file systems are not displayed until remounted.

FS_TYPE

A string indicating the file system type. On Unix systems, some of the possible types are:

hfs - user file system
ufs - user file system
ext2 - user file system
cdfs - CD-ROM file system
vxfs - Veritas (vxfs) file system
nfs - network file system
nfs3 - network file system Version 3

On Windows, some of the possible types are:

NTFS - New Technology File System
FAT - 16-bit File Allocation Table
FAT32 - 32-bit File Allocation Table

FAT uses a 16-bit file allocation table entry (216 clusters).

FAT32 uses a 32-bit file allocation table entry. However, Windows 2000 reserves the first 4 bits of a FAT32 file allocation table entry, which means FAT32 has a theoretical maximum of 228 clusters. NTFS is native file system of Windows NT and Windows 2000.

GBL_ACTIVE_CPU

The number of CPUs online on the system.

For HP-UX and certain versions of Linux, the sar(1M) command allows you to check the status of the system CPUs.

For SUN and DEC, the commands psrinfo(1M) and psradm(1M) allow you to check or change the status of the system CPUs.

For AIX, the pstat(1) command allows you to check the status of the system CPUs.

GBL_ACTIVE_PROC

An active process is one that exists and consumes some CPU time. GBL_ACTIVE_PROC is the sum of the alive-process-time/intervaltime ratios of every process that is active (uses any CPU time) during an interval.

The following diagram of a four second interval during which two processes exist on the system should be used to understand the above definition. Note the difference between active processes, which consume CPU time, and alive processes which merely exist on the system.

     ----------- Seconds -----------

       1         2         3      4 

Proc

---- ----      ----      ----   ----

A    live      live      live   live

B    live/CPU  live/CPU  live   dead

Process A is alive for the entire four second interval but consumes no CPU. A's contribution to GBL_ALIVE_PROC is 4*1/4. A contributes 0*1/4 to GBL_ACTIVE_PROC. B's contribution to GBL_ALIVE_PROC is 3*1/4. B contributes 2*1/4 to GBL_ACTIVE_PROC. Thus, for this interval, GBL_ACTIVE_PROC equals 0.5 and GBL_ALIVE_PROC equals 1.75.

Because a process may be alive but not active, GBL_ACTIVE_PROC will always be less than or equal to GBL_ALIVE_PROC.

This metric is a good overall indicator of the workload of the system. An unusually large number of active processes could indicate a CPU bottleneck.

To determine if the CPU is a bottleneck, compare this metric with GBL_CPU_TOTAL_UTIL and GBL_RUN_QUEUE. If GBL_CPU_TOTAL_UTIL is near 100 percent and GBL_RUN_QUEUE is greater than one, there is a bottleneck.

GBL_ALIVE_PROC

An alive process is one that exists on the system. GBL_ALIVE_PROC is the sum of the alive-process-time/interval-time ratios for every process.

     ----------- Seconds -----------

       1         2         3      4 

Proc

---- ----      ----      ----   ----

A    live      live      live   live

B    live/CPU  live/CPU  live   dead

Because a process may be alive but not active, GBL_ACTIVE_PROC will always be less than or equal to GBL_ALIVE_PROC.

GBL_BOOT_TIME

The date and time when the system was last booted.

GBL_COLLECTOR

ASCII field containing collector name and version. The collector name will appear as either "SCOPE/xx V.UU.FF.LF" or "Coda RV.UU.FF.LF". xx identifies the platform; V = version, UU = update level, FF = fix level, and LF = lab fix id. For example, SCOPE/UX C.04.00.00; or Coda A.07.10.04.

GBL_CPU_CLOCK

The clock speed of the CPUs in MHz if all of the processors have the same clock speed. Otherwise, "na" is shown if the processors have different clock speeds.

GBL_CPU_IDLE_TIME

The time, in seconds, that the CPU was idle during the interval. This is the total idle time, including waiting for I/O.

On a system with multiple CPUs, this metric is normalized. That is, the CPU used over all processors is divided by the number of processors online.

GBL_CPU_IDLE_UTIL

The percentage of time that the CPU was idle during the interval. This is the total idle time, including waiting for I/O.

On Unix systems, this is the same as the sum of the "%idle" and "%wio" fields reported by the "sar -u" command.

On a system with multiple CPUs, this metric is normalized. That is, the CPU used over all processors is divided by the number of processors online.

GBL_CPU_NICE_TIME

The time, in seconds, that the CPU was in user mode at a nice priority during the interval.

On HP-UX, the NICE metrics include positive nice value CPU time only. Negative nice value CPU is broken out into NNICE (negative nice) metrics. Positive nice values range from 20 to 39. Negative nice values range from 0 to 19.

On Sun systems, this metric is only available on SunOS 4.1.X.

GBL_CPU_NICE_UTIL

The percentage of time that the CPU was in user mode at a nice priority during the interval.

On Sun systems, this metric is only available on SunOS 4.1.X.

GBL_CPU_SYS_MODE_TIME

The time, in seconds, that the CPU was in system mode during the interval.

GBL_CPU_SYS_MODE_UTIL

Percentage of time the CPU was in system mode during the interval.

This metric is a subset of the GBL_CPU_TOTAL_UTIL percentage.

This is NOT a measure of the amount of time used by system daemon processes, since most system daemons spend part of their time in user mode and part in system calls, like any other process.

High system mode CPU percentages are normal for IO intensive applications. Abnormally high system mode CPU percentages can indicate that a hardware problem is causing a high interrupt rate. It can also indicate programs that are not calling system calls efficiently.

GBL_CPU_TOTAL_TIME

The total time, in seconds, that the CPU was not idle in the interval.

This is calculated as

   GBL_CPU_TOTAL_TIME =
     GBL_CPU_USER_MODE_TIME + GBL_CPU_SYS_MODE_TIME

GBL_CPU_TOTAL_UTIL

Percentage of time the CPU was not idle during the interval.

This is calculated as

   GBL_CPU_TOTAL_UTIL =
     GBL_CPU_USER_MODE_UTIL + GBL_CPU_SYS_MODE_UTIL

   GBL_CPU_TOTAL_UTIL + GBL_CPU_IDLE_UTIL = 100%

This metric varies widely on most systems, depending on the workload. A consistently high CPU utilization can indicate a CPU bottleneck, especially when other indicators such as GBL_RUN_QUEUE and GBL_ACTIVE_PROC are also high. High CPU utilization can also occur on systems that are bottlenecked on memory, because the CPU spends more time paging and swapping.

NOTE: On Windows, this metric may not equal the sum of the APP_CPU_TOTAL_UTIL metrics. Microsoft states that "this is expected behavior" because this GBL_CPU_TOTAL_UTIL metric is taken from the performance library Processor objects while the APP_CPU_TOTAL_UTIL metrics are taken from the Process objects. Microsoft states that there can be CPU time accounted for in the Processor system objects that may not be seen in the Process objects.

GBL_CPU_USER_MODE_TIME

The time, in seconds, that the CPU was in user mode during the interval.

User CPU is the time spent in user mode at a normal priority, at real-time priority (on HP-UX, AIX, and Windows systems), and at a nice priority.

GBL_CPU_USER_MODE_UTIL

The percentage of time the CPU was in user mode during the interval.

User CPU is the time spent in user mode at a normal priority, at real-time priority (on HP-UX, AIX, and Windows systems), and at a nice priority.

This metric is a subset of the GBL_CPU_TOTAL_UTIL percentage.

High user mode CPU percentages are normal for computationintensive applications. Low values of user CPU utilization compared to relatively high values for GBL_CPU_SYS_MODE_UTIL can indicate an application or hardware problem.

GBL_DISK_PHYS_BYTE

The number of KBs transferred to and from disks during the interval. The bytes for all types of physical IOs are counted. Only local disks are counted in this measurement. NFS devices are excluded.

It is not directly related to the number of IOs, since IO requests can be of differing lengths.

On Unix systems, this includes file system IO, virtual memory IO, and raw IO.

On Windows, all types of physical IOs are counted.

On SUN, if a CD drive is powered off, or no CD is inserted in the CD drive at boottime, the operating system does not provide performance data for that device. This can be determined by checking the "by-disk" data when provided in a product. If the CD drive has an entry in the list of active disks on a system, then data for that device is being collected.

GBL_DISK_PHYS_BYTE_RATE

The average number of KBs per second at which data was transferred to and from disks during the interval. The bytes for all types physical IOs are counted. Only local disks are counted in this measurement. NFS devices are excluded.

This is a measure of the physical data transfer rate. It is not directly related to the number of IOs, since IO requests can be of differing lengths.

This is an indicator of how much data is being transferred to and from disk devices. Large spikes in this metric can indicate a disk bottleneck.

On Unix systems, this includes file system IO, virtual memory IO, and raw IO.

GBL_DISK_PHYS_IO

The number of physical IOs during the interval. Only local disks are counted in this measurement. NFS devices are excluded.

On Unix systems, this includes all types of physical reads and writes to and from disk, including file system IO, virtual memory IO and raw IO.

On HP-UX, this is calculated as

   GBL_DISK_PHYS_IO =
     GBL_DISK_FS_IO + GBL_DISK_VM_IO +
     GBL_DISK_SYSTEM_IO + GBL_DISK_RAW_IO

GBL_DISK_PHYS_IO_RATE

The number of physical IOs per second during the interval. Only local disks are counted in this measurement. NFS devices are excluded.

On Unix systems, this includes all types of physical reads and writes to and from disk, including file system IO, virtual memory IO and raw IO.

On HP-UX, this is calculated as

   GBL_DISK_PHYS_IO_RATE =
     GBL_DISK_FS_IO_RATE + GBL_DISK_VM_IO_RATE +
     GBL_DISK_SYSTEM_IO_RATE + GBL_DISK_RAW_IO_RATE

GBL_DISK_PHYS_READ

The number of physical reads during the interval. Only local disks are counted in this measurement. NFS devices are excluded.

On Unix systems, all types of disk reads are counted, including file system, virtual memory, and raw reads.

On HP-UX, there are many reasons why there is not a direct correlation between the number of logical IOs and physical IOs. For example, small sequential logical reads may be satisfied from the buffer cache, resulting in fewer physical IOs than logical IOs. Conversely, large logical IOs or small random IOs may result in more physical than logical IOs. Logical volume mappings, logical disk mirroring, and disk striping also tend to remove any correlation.

On HP-UX, this is calculated as

   GBL_DISK_PHYS_READ =
     GBL_DISK_FS_READ + GBL_DISK_VM_READ +
     GBL_DISK_SYSTEM_READ + GBL_DISK_RAW_READ

GBL_DISK_PHYS_READ_BYTE_RATE

The average number of KBs transferred from the disk per second during the interval. Only local disks are counted in this measurement. NFS devices are excluded.

GBL_DISK_PHYS_READ_RATE

The number of physical reads per second during the interval. Only local disks are counted in this measurement. NFS devices are excluded.

On Unix systems, all types of disk reads are counted, including file system, virtual memory, and raw reads.

On HP-UX, this is calculated as

   GBL_DISK_PHYS_READ_RATE =
     GBL_DISK_FS_READ_RATE + GBL_DISK_VM_READ_RATE +
     GBL_DISK_SYSTEM_READ_RATE + GBL_DISK_RAW_READ_RATE

GBL_DISK_PHYS_WRITE

The number of physical writes during the interval. Only local disks are counted in this measurement. NFS devices are excluded.

On Unix systems, all types of disk writes are counted, including file system IO, virtual memory IO, and raw writes.

On HP-UX, since this value is reported by the drivers, multiple physical requests that have been collapsed to a single physical operation (due to driver IO merging) are only counted once.

On HP-UX, there are many reasons why there is not a direct correlation between logical IOs and physical IOs. For example, small logical writes may end up entirely in the buffer cache, and later generate fewer physical IOs when written to disk due to the larger IO size. Or conversely, small logical writes may require physical prefetching of the corresponding disk blocks before the data is merged and posted to disk. Logical volume mappings, logical disk mirroring, and disk striping also tend to remove any correlation.

On HP-UX, this is calculated as

   GBL_DISK_PHYS_WRITE =
     GBL_DISK_FS_WRITE + GBL_DISK_VM_WRITE +
     GBL_DISK_SYSTEM_WRITE + GBL_DISK_RAW_WRITE

GBL_DISK_PHYS_WRITE_BYTE_RATE

The average number of KBs transferred to the disk per second during the interval. Only local disks are counted in this measurement. NFS devices are excluded.

GBL_DISK_PHYS_WRITE_RATE

The number of physical writes per second during the interval. Only local disks are counted in this measurement. NFS devices are excluded.

On Unix systems, all types of disk writes are counted, including file system IO, virtual memory IO, and raw writes.

On HP-UX, since this value is reported by the drivers, multiple physical requests that have been collapsed to a single physical operation (due to driver IO merging) are only counted once.

On HP-UX, this is calculated as

   GBL_DISK_PHYS_WRITE_RATE =
     GBL_DISK_FS_WRITE_RATE + GBL_DISK_VM_WRITE_RATE +
     GBL_DISK_SYSTEM_WRITE_RATE + GBL_DISK_RAW_WRITE_RATE

GBL_DISK_REQUEST_QUEUE

The total length of all of the disk queues at the end of the interval.

GBL_DISK_TIME_PEAK

The time, in seconds, during the interval that the busiest disk was performing IO transfers. This is for the busiest disk only, not all disk devices. This counter is based on an end-to-end measurement for each IO transfer updated at queue entry and exit points.

Only local disks are counted in this measurement. NFS devices are excluded.

GBL_DISK_UTIL

On HP-UX, this is the average percentage of time during the interval that all disks had IO in progress from the point of view of the Operating System. This is the average utilization for all disks.

On all other Unix systems, this is the average percentage of disk in use time of the total interval (that is, the average utilization).

Only local disks are counted in this measurement. NFS devices are excluded.

GBL_DISK_UTIL_PEAK

The utilization of the busiest disk during the interval.

On HP-UX, this is the percentage of time during the interval that the busiest disk device had IO in progress from the point of view of the Operating System.

On all other systems, this is the percentage of time during the interval that the busiest disk was performing IO transfers.

It is not an average utilization over all the disk devices. Only local disks are counted in this measurement. NFS devices are excluded.

A peak disk utilization of more than 50 percent often indicates a disk IO subsystem bottleneck situation. A bottleneck may not be in the physical disk drive itself, but elsewhere in the IO path.

GBL_DISTRIBUTION

The software distribution, if available.

GBL_FS_SPACE_UTIL_PEAK

The percentage of occupied disk space to total disk space for the fullest file system found during the interval. Only locally mounted file systems are counted in this metric.

This metric can be used as an indicator that at least one file system on the system is running out of disk space.

On Unix systems, CDROM and PC file systems are also excluded. This metric can exceed 100 percent. This is because a portion of the file system space is reserved as a buffer and can only be used by root. If the root user has made the file system grow beyond the reserved buffer, the utilization will be greater than 100 percent. This is a dangerous situation since if the root user totally fills the file system, the system may crash.

On Windows, CDROM file systems are also excluded.

GBL_GMTOFFSET

The difference, in minutes, between local time and GMT (Greenwich Mean Time).

GBL_INTERRUPT

The number of IO interrupts during the interval.

GBL_INTERRUPT_RATE

The average number of IO interrupts per second during the interval.

On SUN, this value includes clock interrupts. Clock interrupts occur 100 per second. To get non-clock device interrupts, subtract 100 from the value.

GBL_INTERVAL

The amount of time in the interval.

This measured interval is slightly larger than the desired or configured interval if the collection program is delayed by a higher priority process and cannot sample the data immediately.

GBL_LOADAVG

The average load average of the system during the interval.

This metric is derived from a kernel variable (avenrun) which is calculated by summing the number of runnable processes and averaging the samples over the last minute. Processes marked "runnable" include:

a process using the CPU at the time of the sample
a process waiting for the CPU at the time of the sample
a process paused on a "short disk wait" at the time of the sample

Because this metric can include processes which are waiting for disk IO to complete, it is not a reliable CPU bottleneck indicator. Several standard UNIX commands, such as uptime(1), display avenrun as the "1-minute Load Average."

GBL_LOST_MI_TRACE_BUFFERS

The number of trace buffers lost by the measurement processing daemon.

On HP-UX systems, if this value is > 0, the measurement subsystem is not keeping up with the system events that generate traces.

For other Unix systems, if this value is > 0, the measurement subsystem is not keeping up with the ARM API calls that generate traces.

GBL_MACHINE

On most Unix systems, this is a text string representing the type of computer. This is similar to what is returned by the command "uname -m".

On AIX, this is a text string representing the model number of the computer. This is calculated by decoding the unique ID number portion of the machine ID number returned by the "uname -m" command.

On Windows, this is a text string representing the type of the computer. For example, "80686".

GBL_MACHINE_MODEL

The CPU model. This is similar to the information returned by the GBL_MACHINE metric and the uname command. However, this metric returns more information on some processors.

On HP-UX, this is the same information returned by the model command.

GBL_MEM_AVAIL

The amount of physical available memory in the system (in MBs unless otherwise specified).

Beginning with the OVPA 4.0 release, this metric is now reported in MBytes to better report the significant increases in system memory capacities.

WARNING: This change in scale applies to this metric when logged by OVPA or displayed with GlancePlus for this release and beyond. However, the presentation of this metric recorded in legacy data (data logged with OVPA C.03 and previous releases), will remain in units of KBytes when viewed with extract or OVPM.

On Windows, memory resident operating system code and data is not included as available memory.

GBL_MEM_CACHE

The amount of physical memory (in MBs unless otherwise specified) used by the buffer cache during the interval.

Beginning with the OVPA 4.0 release, this metric is now reported in MBytes to better report the significant increases in system memory capacities.

On HP-UX, the buffer cache is a memory pool used by the system to stage disk IO data for the driver.

On SUN, this value is obtained by multiplying the system page size times the number of buffer headers (nbuf). For example, on a SPARCstation 10 the buffer size is usually (200 (page size buffers) * 4096 (bytes/page) = 800 KB).

On SUN, the buffer cache is a memory pool used by the system to cache inode, indirect block and cylinder group related disk accesses. This is different from the traditional concept of a buffer cache that also holds file system data. On Solaris 5.X, as file data is cached, accesses to it show up as virtual memory IOs. File data caching occurs through memory mapping managed by the virtual memory system, not through the buffer cache. The "nbuf" value is dynamic, but it is very hard to create a situation where the memory cache metrics change, since most systems have more than adequate space for inode, indirect block, and cylinder group data caching. This cache is more heavily utilized on NFS file servers.

On AIX, this value should be minimal since most disk IOs are done through memory mapped files.

GBL_MEM_CACHE_UTIL

The percentage of physical memory used by the buffer cache during the interval.

On HP-UX, the buffer cache is a memory pool used by the system to stage disk IO data for the driver.

On SUN, this percentage is based on calculating the buffer cache size by multiplying the system page size times the number of buffer headers (nbuf). For example, on a SPARCstation 10 the buffer size is usually (200 (page size buffers) * 4096 (bytes/page) = 800 KB).

On AIX, this value should be minimal since most disk IOs are done through memory mapped files.

GBL_MEM_FREE

The amount of memory not allocated (in MBs unless otherwise specified). As this value drops, the likelihood increases that swapping or paging out to disk may occur to satisfy new memory requests.

Beginning with the OVPA 4.0 release, this metric is now reported in MBytes to better report the significant increases in system memory capacities.

On SUN, low values for this metric may not indicate a true memory shortage. This metric can be influenced by the VMM (Virtual Memory Management) system.

GBL_MEM_FREE_UTIL

The percentage of physical memory that was free at the end of the interval.

GBL_MEM_PAGEIN

On most Unix systems, this is the total number of page ins from the disk during the interval. This includes pages paged in from paging space and from the file system.

On AIX, this is the total number of page ins from the disk during the interval. This includes pages paged in from paging space.

On some Unix systems, this is the same as the "page ins" value from the "vmstat -s" command. Remember that "vmstat -s" reports cumulative counts.

On AIX, this metric cannot be compared to the "pi" value from the "vmstat" command. The "pi" value only reports the number of pages paged in from paging space.

This metric is available on HP-UX 11.0 and beyond.

GBL_MEM_PAGEIN_BYTE

The number of KBs (or MBs if specified) of page ins during the interval.

GBL_MEM_PAGEIN_BYTE_RATE

The number of KBs per second of page ins during the interval.

On SUN, this metric cannot be compared to GBL_MEM_PAGEIN_RATE, because it includes file I/O activity.

GBL_MEM_PAGEIN_RATE

The total number of disk blocks paged into memory (or page ins) per second from the disk during the interval. This includes pages paged in from paging space and from the file system.

On some Unix systems, this is the same as the "page ins" value from the "vmstat -s" command. Remember that "vmstat -s" reports cumulative counts.

On AIX, this metric cannot be compared to the "pi" value from the "vmstat" command. The "pi" value only reports the number of pages paged in from paging space.

On SunOS 5.7 and 5.8, this includes page-ins from paging space, but does not include file system page-ins (fpi). For SunOS 5.7, this is the same as the sum of "epi" and "api" values from the "memstat" command, divided by page size in KB. For SunOS 5.8, this is the same as the sum of "epi" and "api" values from the "vmstat -p" command, divided by page size in KB.

GBL_MEM_PAGEOUT

The total number of page outs to the disk during the interval. This includes pages paged out to paging space and to the file system.

For SunOS 5.7 and 5.8, as well as for AIX, the number of page outs does not include file system page outs.

On HP-UX 11i, the value shown is forced page outs initiated by vhand that are due to memory pressure. For HP-UX 11.0, the page out activity may include memory mapped IOs on some file systems (for example, VxFS).

On some Unix systems, this is the same as the "page outs" value from the "vmstat -s" command. Remember that "vmstat -s" reports cumulative counts.

On AIX, this metric cannot be compared to the "po" value from the "vmstat" command. The "po" value only reports the number of pages paged out to paging space.

GBL_MEM_PAGEOUT_BYTE

The number of KBs (or MBs if specified) of page outs during the interval.

This metric is available on HP-UX 11.0 and beyond.

GBL_MEM_PAGEOUT_BYTE_RATE

The number of KBs (or MBs if specified) per second of page outs during the interval.

On SUN, this metric cannot be compared to GBL_MEM_PAGEOUT_RATE, because it includes file I/O activity.

GBL_MEM_PAGEOUT_RATE

The total number of page outs to the disk per second during the interval. This includes pages paged out to paging space and, except on AIX, to the file system.

On some Unix systems, this is the same as the "page outs" value from the "vmstat -s" command. Remember that "vmstat -s" reports cumulative counts.

On AIX, this metric cannot be compared to the "po" value from the "vmstat" command. The "po" value only reports the number of pages paged out to paging space.

On SunOS 5.7 and 5.8, this includes page-outs to paging space, but does not include file system page-outs (fpo). For SunOS 5.7, this is the same as the sum of "epo" and "apo" values from the "memstat" command, divided by page size in KB. For SunOS 5.8, this is the same as the sum of "epo" and "apo" values from the "vmstat -p" command, divided by page size in KB.

On Windows, this counter also includes paging traffic on behalf of the system cache to access file data for applications and so may be high when there is no memory pressure.

GBL_MEM_PAGE_REQUEST

The number of page requests to or from the disk during the interval.

On AIX, this includes pages paged in and out to paging space. It also includes IO to files in the local file system since files are implicitly memory mapped and the IO is handled by the virtual memory system.

For SunOS 5.6, this includes page-ins and page-outs to paging space. It also includes IO to files in the local file system since files are implicitly memory mapped and the IO is handled by the virtual memory system. For SunOS 5.7 and 5.8, this includes page-ins and page-outs to paging space. This does not include IO to files in the local file system.

For SunOS 5.6, this is the same as the sum of "page ins" and "page outs" values from the "vmstat -s" command. Remember that "vmstat -s" reports cumulative counts. For SunOS 5.7, this is the same as the sum of the "epi", "epo", "api" and "apo" values from the "memstat" command, divided by page size in KB. For SunOS 5.8, this is the same as the sum of the "epi", "epo", "api" and "apo" values from the "vmstat -p" command, divided by page size in KB.

On Unix systems, this is typically the same as the sum of the "page ins" and "page outs" values from the "vmstat -s" command. Remember that "vmstat -s" reports cumulative counts.

On AIX, this metric cannot be compared to either the "pi" or "po" values from the "vmstat" command. The "pi" value only reports the number of pages paged in from paging space, while the "po" value only reports the number of pages paged out to paging space.

GBL_MEM_PAGE_REQUEST_RATE

The number of page requests to or from the disk per second during the interval.

On AIX, this includes pages paged in/out to paging space. It also includes IO to files in the local file system since files are implicitly memory mapped and the IO is handled by the virtual memory system.

For SunOS 5.6, this is the same as the sum of the "page ins" and "page outs" values from the "vmstat -s" command. Remember that "vmstat -s" reports cumulative counts. For SunOS 5.7, this is the same as the sum of the "epi", "epo", "api" and "apo" values from the "memstat" command, divided by page size in KB. For SunOS 5.8, this is the same as the sum of the "epi", "epo", "api" and "apo" values from the "vmstat -p" command, divided by page size in KB.

On Unix systems, this is typically the same as the sum of the "page ins" and "page outs" values from the "vmstat -s" command. Remember that "vmstat -s" reports cumulative counts.

Higher than normal rates can indicate either a memory or a disk bottleneck. Compare GBL_DISK_UTIL_PEAK and GBL_MEM_UTIL to determine which resource is more constrained. High rates may also indicate memory thrashing caused by a particular application or set of applications. Look for processes with high major fault rates to identify the culprits.

GBL_MEM_PHYS

The amount of physical memory in the system (in MBs unless otherwise specified).

Beginning with the OVPA 4.0 release, this metric is now reported in MBytes to better report the significant increases in system memory capacities.

On HP-UX, banks with bad memory are not counted. Note that on some machines, the Processor Dependent Code (PDC) code uses the upper 1MB of memory and thus reports less than the actual physical memory of the system. Thus, on a system with 256MB of physical memory, this metric and dmesg(1M) might only report 267,386,880 bytes (255MB). This is all the physical memory that software on the machine can access.

On Windows, this is the total memory available, which may be slightly less than the total amount of physical memory present in the system. This value is also reported in the Control Panel's About Windows NT help topic.

GBL_MEM_SWAPIN_BYTE

The number of KBs transferred in from disk due to swap ins (or reactivations on HP-UX) during the interval.

On HP-UX, process swapping was replaced by a combination of paging and deactivation. Process deactivation occurs when the system is thrashing or when the amount of free memory falls below a critical level. The swapper then marks certain processes for deactivation and removes them from the run queue. Pages within the associated memory regions are reused or paged out by the memory management vhand process in favor of pages belonging to processes that are not deactivated. Unlike traditional process swapping, deactivated memory pages may or may not be written out to the swap area, because a process could be reactivated before the paging occurs.

To summarize, a process swap-out on HP-UX is a process deactivation. A swap-in is a reactivation of a deactivated process. Swap metrics that report swap-out bytes now represent bytes paged out to swap areas from deactivated regions. Because these pages are pushed out over time based on memory demands, these counts are much smaller than HP-UX 9.x counts where the entire process was written to the swap area when it was swappedout. Likewise, swap-in bytes now represent bytes paged in as a result of reactivating a deactivated process and reading in any pages that were actually paged out to the swap area while the process was deactivated.

GBL_MEM_SWAPIN_BYTE_RATE

The number of KBs per second transferred from disk due to swap ins (or reactivations on HP-UX) during the interval.

GBL_MEM_SWAPOUT_BYTE

The number of KBs (or MBs if specified) transferred out to disk due to swap outs (or deactivations on HP-UX) during the interval.

On AIX, under no memory pressure, page scan rates remain close to zero. If a process demands memory and an insufficient amount is available, the page scan daemon will increase the scan rate in order to free up memory. Also, if the Free Frame falls below the Low Memory Threshold, the system suspends existing processes and prevents new ones from starting. At that point, the page scan daemon starts scanning pages at the highest speed possible to free up pages and the operating system attempts to steal real memory from pages unlikely to be referenced in the near future. If it fails to reach the free memory goal this way, then swap outs begin. Usually a scan rate greater than 150 and a swap out rate greater than 100 indicates memory pressure. High swap out rates also indicate memory thrashing. The size of the free list must be kept above the low threshold for several reasons. For example, the AIX operating system sequential prefetch algorithm requires up to 8 free frames at a time for each process performing sequential reads. Also, the Virtual Memory Management must avoid deadlocks within the operating system itself, which can occur if there were not enough space to read in a required page in order to free a page frame.

GBL_MEM_SWAPOUT_BYTE_RATE

The number of KBs (or MBs if specified) per second transferred out to disk due to swap outs (or deactivations on HP-UX) during the interval.

GBL_MEM_SYS

The amount of physical memory (in MBs unless otherwise specified) used by the system (kernel) during the interval. System memory does not include the buffer cache.

Beginning with the OVPA 4.0 release, this metric is now reported in MBytes to better report the significant increases in system memory capacities.

On HP-UX 10.20 and 11.0, this metric does not include some kinds of dynamically allocated kernel memory. This has always been reported in the GBL_MEM_USER* metrics.

On HP-UX 11i and beyond, this metric includes some kinds of dynamically allocated kernel memory.

GBL_MEM_SYS_UTIL

The percentage of physical memory used by the system during the interval.

System memory does not include the buffer cache.

On HP-UX 10.20 and 11.0, this metric does not include some kinds of dynamically allocated kernel memory. This has always been reported in the GBL_MEM_USER* metrics.

On HP-UX 11i and beyond, this metric includes some kinds of dynamically allocated kernel memory.

GBL_MEM_USER

The amount of physical memory (in MBs unless otherwise specified) allocated to user code and data at the end of the interval. User memory regions include code, heap, stack, and other data areas including shared memory. This does not include memory for buffer cache.

Beginning with the OVPA 4.0 release, this metric is now reported in MBytes to better report the significant increases in system memory capacities.

On HP-UX 10.20 and 11.0, this metric includes some kinds of dynamically allocated kernel memory.

On HP-UX 11i and beyond, this metric does not include some kinds of dynamically allocated kernel memory. This is now reported in the GBL_MEM_SYS* metrics.

Large fluctuations in this metric can be caused by programs which allocate large amounts of memory and then either release the memory or terminate. A slow continual increase in this metric may indicate a program with a memory leak.

GBL_MEM_USER_UTIL

The percent of physical memory allocated to user code and data at the end of the interval. This metric shows the percent of memory owned by user memory regions such as user code, heap, stack and other data areas including shared memory. This does not include memory for buffer cache.

On HP-UX 10.20 and 11.0, this metric includes some kinds of dynamically allocated kernel memory.

On HP-UX 11i and beyond, this metric does not include some kinds of dynamically allocated kernel memory. This is now reported in the GBL_MEM_SYS* metrics.

GBL_MEM_UTIL

The percentage of physical memory in use during the interval. This includes system memory (occupied by the kernel), buffer cache and user memory.

On HP-UX, this calculation is done using the byte values for physical memory and used memory, and is therefore more accurate than comparing the reported kilobyte values for physical memory and used memory.

On SUN, high values for this metric may not indicate a true memory shortage. This metric can be influenced by the VMM (Virtual Memory Management) system.

GBL_NET_COLLISION

The number of collisions that occurred on all network interfaces during the interval. A rising rate of collisions versus outbound packets is an indication that the network is becoming increasingly congested. This metric does not include deferred packets.

For HP-UX 10.20 and other Unix systems, this is the same as the sum of the "Coll" column from the "netstat -i" command for a network device. See also netstat(1).

This metric is updated at the sampling interval, regardless of the number of IP addresses on the system.

GBL_NET_COLLISION_1_MIN_RATE

The number of collisions per minute on all network interfaces during the interval.

Collisions occur on any busy network, but abnormal collision rates could indicate a hardware or software problem.

GBL_NET_COLLISION_PCT

The percentage of collisions to total outbound packet attempts during the interval. Outbound packet attempts include both successful packets and collisions.

A rising rate of collisions versus outbound packets is an indication that the network is becoming increasingly congested.

This metric does not currently include deferred packets.

This metric is updated at the sampling interval, regardless of the number of IP addresses on the system.

AIX does not support the collision count for ethernet interface. The collision count is supported for token ring (tr) and loopback (lo) interface. For more information please refer to netstat(1) man page.

GBL_NET_COLLISION_RATE

The number of collisions per second on all network interfaces during the interval.

A rising rate of collisions versus outbound packets is an indication that the network is becoming increasingly congested.

This metric is updated at the sampling interval, regardless of the number of IP addresses on the system.

GBL_NET_ERROR

The number of errors that occurred on all network interfaces during the interval.

For HP-UX 10.20 and other Unix systems, this is the same as the sum of "Ierrs" (or RX on Linux) and "Oerrs" (or TX on Linux) from the "netstat -i" command for a network device. See also netstat(1).

This metric is updated at the sampling interval, regardless of the number of IP addresses on the system.

GBL_NET_ERROR_1_MIN_RATE

The number of errors per minute on all network interfaces during the interval. This rate should normally be zero or very small. A large error rate can indicate a hardware or software problem.

GBL_NET_ERROR_RATE

The number of errors per second on all network interfaces during the interval.

GBL_NET_IN_ERROR_PCT

The percentage of inbound network errors to total inbound packet attempts during the interval. Inbound packet attempts include both packets successfully received and those that encountered errors.

A large number of errors may indicate a hardware problem on the network. The percentage of inbound errors to total packets attempted should remain low.

GBL_NET_IN_PACKET

The number of successful packets received through all network interfaces during the interval. Successful packets are those that have been processed without errors or collisions.

For HP-UX 10.20 and other Unix systems, this is the same as the sum of the "Ipkts" column (or RX on Linux) from the "netstat -i" command for a network device. See also netstat(1).

This metric is updated at the sampling interval, regardless of the number of IP addresses on the system.

On Windows system, the packet size for NBT connections is defined as 1 Kbyte.

GBL_NET_IN_PACKET_RATE

The number of successful packets per second received through all network interfaces during the interval. Successful packets are those that have been processed without errors or collisions.

This metric is updated at the sampling interval, regardless of the number of IP addresses on the system.

On Windows system, the packet size for NBT connections is defined as 1 Kbyte.

GBL_NET_OUT_ERROR_PCT

The percentage of outbound network errors to total outbound packet attempts during the interval. Outbound packet attempts include both packets successfully sent and those that encountered errors.

The percentage of outbound errors to total packets attempted to be transmitted should remain low.

GBL_NET_OUT_PACKET

The number of successful packets sent through all network interfaces during the last interval. Successful packets are those that have been processed without errors or collisions.

For HP-UX 10.20 and other Unix systems, this is the same as the sum of the "Opkts" column (or TX on Linux) from the "netstat -i" command for a network device. See also netstat(1).

This metric is updated at the sampling interval, regardless of the number of IP addresses on the system.

On Windows system, the packet size for NBT connections is defined as 1 Kbyte.

GBL_NET_OUT_PACKET_RATE

The number of successful packets per second sent through the network interfaces during the interval. Successful packets are those that have been processed without errors or collisions.

This metric is updated at the sampling interval, regardless of the number of IP addresses on the system.

On Windows system, the packet size for NBT connections is defined as 1 Kbyte.

GBL_NET_PACKET_RATE

The number of successful packets per second (both inbound and outbound) for all network interfaces during the interval. Successful packets are those that have been processed without errors or collisions.

GBL_NFS_CALL

The number of NFS calls the local system has made as either a NFS client or server during the interval.

This includes both successful and unsuccessful calls. Unsuccessful calls are those that cannot be completed due to resource limitations or LAN packet errors.

NFS calls include create, remove, rename, link, symlink, mkdir, rmdir, statfs, getattr, setattr, lookup, read, readdir, readlink, write, writecache, null and root operations.

GBL_NFS_CALL_RATE

The number of NFS calls per second the system made as either a NFS client or NFS server during the interval.

Each computer can operate as both a NFS server, and as an NFS client.

This metric includes both successful and unsuccessful calls. Unsuccessful calls are those that cannot be completed due to resource limitations or LAN packet errors.

NFS calls include create, remove, rename, link, symlink, mkdir, rmdir, statfs, getattr, setattr, lookup, read, readdir, readlink, write, writecache, null and root operations.

GBL_NUM_APP

The number of applications defined in the parm file plus one (for "other").

The application called "other" captures all other processes not defined in the parm file.

You can define up to 128 applications.

GBL_NUM_CPU

The number of CPUs physically on the system. This includes all CPUs, either online or offline.

For HP-UX and certain versions of Linux, the sar(1M) command allows you to check the status of the system CPUs.

For SUN and DEC, the commands psrinfo(1M) and psradm(1M) allow you to check or change the status of the system CPUs.

GBL_NUM_DISK

The number of disks on the system. Only local disk devices are counted in this metric.

On HP-UX, this is a count of the number of disks on the system that have ever had activity over the cumulative collection time.

GBL_NUM_NETWORK

The number of network interfaces on the system. This includes the loopback interface. On certain platforms, this also include FDDI, Hyperfabric, ATM, Serial Software interfaces such as SLIP or PPP, and Wide Area Network interfaces (WAN) such as ISDN or X.25. The "netstat -i" command also displays the list of network interfaces on the system.

GBL_NUM_USER

The number of users logged in at the time of the interval sample. This is the same as the command "who | wc -l'.

For Unix systems, the information for this metric comes from the utmp file which is updated by the login command. For more information, read the man page for utmp. Some applications may create users on the system without using login and updating the utmp file. These users are not reflected in this count.

This metric can be a general indicator of system usage. In a networked environment, however, users may maintain inactive logins on several systems.

On Windows, the information for this metric comes from the Server Sessions counter in the Performance Libraries Server object. It is a count of the number of users using this machine as a file server.

GBL_OSKERNELTYPE_INT

This indicates the word size of the current kernel on the system. Some hardware can load the 64-bit kernel or the 32-bit kernel. This metric is available on HP-UX 11.0 and beyond.

GBL_OSNAME

A string representing the name of the operating system. On Unix systems, this is the same as the output from the "uname -s" command.

GBL_OSRELEASE

The current release of the operating system. This is the same as the output from the "uname -r" command.

GBL_OSVERSION

A string representing the version of the operating system. This is the same as the output from the "uname -v" command. This string is limited to 20 characters, and as a result, the complete version name might be truncated.

On Windows, this is a string representing the service pack installed on the operating system.

GBL_PROC_SAMPLE

The number of process data samples that have been averaged into global metrics (such as GBL_ACTIVE_PROC) that are based on process samples.

GBL_RUN_QUEUE

On the non HP-UX systems, this is the average number of "runnable" processes during the interval.

On HP-UX, this is the average number of "runnable" processes or kernel threads over all processors during the interval. The value shown for the run queue represents the average of the 1- minute load averages for all processors.

On Windows, this is approximately the average Processor Queue Length during the interval.

On HP-UX, this metric is derived from a kernel variable (avenrun) which is calculated by summing the number of runnable processes or kernel threads for each processor and averaging the samples over the last minute. Processes or kernel threads marked "runnable" include:

a process or kernel thread using the CPU at the time of the sample
a process or kernel thread waiting for the CPU at the time of the sample
a process or kernel thread paused on a "short disk wait" at the time of the sample (HP-UX 10.20 and 11.0)

On HP-UX 10.20 and 11.0, this metric can include processes or kernel threads which are waiting for disk IO to complete. Because of that, it is not a reliable CPU bottleneck indicator.

On HP-UX 11i, this metric does not include processes or kernel threads which are waiting for disk IO to complete.

Several standard UNIX commands, such as uptime(1), display avenrun as the "1-minute Load Average."

HP-UX Run Queue Example shows an example between the RUN/PRI/CPU Queue differences for multi-cpu systems.

On SUN, this metric is updated by the kernel every second by counting the number of processes which are in the SRUN state at the time of update. Processes in the SRUN state are in memory, ready to run, and just waiting to get the CPU.

On AIX, this metric is updated by the kernel every 5 seconds by counting the number of processes which are in the SRUN state at the time of update. Processes in the SRUN state are in memory, ready to run, and just waiting to get the CPU. It is an average over the number of times the kernel has updated the run queue length counter during the interval. This is the same number reported as runq-sz by the "sar -q" command.

On Unix systems, GBL_RUN_QUEUE is normally a very small number. Larger than normal values for this metric indicate CPU contention among processes. This CPU bottleneck is also normally indicated by 100 percent GBL_CPU_TOTAL_UTIL. It may be OK to have GBL_CPU_TOTAL_UTIL be 100 percent if no other processes are waiting for the CPU. However, if GBL_CPU_TOTAL_UTIL is 100 percent and GBL_RUN_QUEUE is greater than the number of processors, it indicates a CPU bottleneck.

On Windows, the Processor Queue reflects a count of process threads which are ready to execute. A thread is ready to execute (in the Ready state) when the only resource it is waiting on is the processor. The Windows operating system itself has many system threads which intermittently use small amounts of processor time. Several low priority threads intermittently wake up and execute for very short intervals. Depending on when the collection process samples this queue, there may be none or several of these low-priority threads trying to execute. Therefore, even on an otherwise quiescent system, the Processor Queue Length can be high. High values for this metric during intervals where the overall CPU utilization (gbl_cpu_total_util) is low do not indicate a performance bottleneck. Relatively high values for this metric during intervals where the overall CPU utilization is near 100% can indicate a CPU performance bottleneck.

GBL_STARTED_PROC

The number of processes that started during the interval.

GBL_STARTED_PROC_RATE

The number of processes that started per second during the interval.

GBL_STATTIME

An ASCII string representing the time at the end of the interval, based on local time.

GBL_SUBPROCSAMPLEINTERVAL

The SubProcSampleInterval parameter sets the internal sampling interval of process data. This option only changes the frequency of how often the operating system process table is scanned in order to accumulate process statistics during a log interval and does not change the logging interval for process data logging. If, for example, the CPU utilization is higher than expected (possibly due to a large operating system process table), you can decrease the utilization by increasing the sampling interval.

Note: Increasing the SUBPROC sample interval (SUBPROC can be used interchangeably with SUBPROCSAMPLEINTERVAL) parameter may decrease the accuracy of application data and process data since short-lived processes (those completing within a sample interval) cannot be captured and hence logged by scopeux.

To set process subintervals to 5 (default), 10, 15, 20, 30, or 60 seconds (these are the only values allowed), you will have to enter the SUBPROC or SUBPROCSAMPLEINTERVAL sample interval parameter in your parm file. You cannot input a value lower than 5. For example, to set the interval to 15 seconds, add one of the following lines in your parm file:

   SUBPROC=15
     or
   SUBPROCSAMPLEINTERVAL=15

Changes made to the parm file are logged every time the Performance Agent is restarted. To check changes made to the SUBPROC sample interval parameter in your parm file, you can use the following command:

  # utility -xs -D |grep -i sub
  04/23/99 13:04 Process Collection Sample SubInterval
                                5 seconds -> 5 seconds
  04/23/99 14:31 Process Collection Sample SubInterval
                               5 seconds -> 15 seconds
  04/23/99 14:43 Process Collection Sample SubInterval
                              15 seconds -> 30 seconds

Specify the full pathname of the performance tool bin directory as needed.

You can also export the GBL_SUBPROCSAMPLEINTERVAL metric from the Configuration data.

GBL_SWAP_SPACE_AVAIL

The total amount of potential swap space, in MB.

On SUN, this is the total amount of swap space available from the physical backing store devices (disks) plus the amount currently available from main memory. This is the same as (used + available) /1024, reported by the "swap -s" command.

On Linux, this is same as (Swap: total) as reported by the "free -m" command.

On Unix systems, this metric is updated every 30 seconds or the sampling interval, whichever is greater.

GBL_SWAP_SPACE_AVAIL_KB

The total amount of potential swap space, in KB.

On HP-UX, this is the sum of the device swap areas enabled by the swapon command, the allocated size of any file system swap areas, and the allocated size of pseudo swap in memory if enabled. Note that this is potential swap space. Since swap is allocated in fixed (SWCHUNK) sizes, not all of this space may actually be usable. For example, on a 61MB disk using 2 MB swap size allocations, 1 MB remains unusable and is considered wasted space.

On HP-UX, this is the same as (AVAIL: total) as reported by the "swapinfo -t" command.

On Unix systems, this metric is updated every 30 seconds or the sampling interval, whichever is greater.

GBL_SWAP_SPACE_USED

The amount of swap space used, in MB.

On HP-UX, "Used" indicates written to disk (or locked in memory), rather than reserved. This is the same as (USED: total - reserve) as reported by the "swapinfo -mt" command.

On SUN, "Used" indicates amount written to disk (or locked in memory), rather than reserved. Swap space is reserved (by decrementing a counter) when virtual memory for a program is created. This is the same as (bytes allocated)/1024, reported by the "swap -s" command.

On Linux, this is same as (Swap: used) as reported by the "free -m" command.

On Unix systems, this metric is updated every 30 seconds or the sampling interval, whichever is greater.

GBL_SWAP_SPACE_USED_UTIL

The amount of swap space used, in MB.

On HP-UX, "Used" indicates written to disk (or locked in memory), rather than reserved. This is the same as (USED: total - reserve) as reported by the "swapinfo -mt" command.

On SUN, global swap space is tracked through the operating system. Device swap space is tracked through the devices. For this reason, the amount of swap space used may differ between the global and by-device metrics. Sometimes pages that are marked to be swapped to disk by the operating system are never swapped. The operating system records this as used swap space, but the devices do not, since no physical IOs occur. (Metrics with the prefix "GBL" are global and metrics with the prefix "BYSWP" are by device.)

On Linux, this is same as (Swap: used) as reported by the "free -m" command.

On Unix systems, this metric is updated every 30 seconds or the sampling interval, whichever is greater.

GBL_SWAP_SPACE_UTIL

The percent of available swap space that was being used by running processes in the interval.

On Windows, this is the percentage of virtual memory, which is available to user processes, that is in use at the end of the interval. It is not an average over the entire interval. It reflects the ratio of committed memory to the current commit limit. The limit may be increased by the operating system if the paging file is extended. This is the same as (Committed Bytes / Commit Limit) * 100 when comparing the results to Performance Monitor.

On HP-UX, swap space must be reserved (but not allocated) before virtual memory can be created. If all of available swap is reserved, then no new processes or virtual memory can be created. Swap space locations are actually assigned (used) when a page is actually written to disk or locked in memory (pseudo swap in memory). This is the same as (PCT USED: total) as reported by the "swapinfo -mt" command.

On Unix systems, this metric is a measure of capacity rather than performance. As this metric nears 100 percent, processes are not able to allocate any more memory and new processes may not be able to run. Very low swap utilization values may indicate that too much area has been allocated to swap, and better use of disk space could be made by reallocating some swap partitions to be user filesystems.

On Unix systems, this metric is updated every 30 seconds or the sampling interval, whichever is greater.

GBL_SYSTEM_ID

The network node hostname of the system. This is the same as the output from the "uname -n" command.

On Windows, the name obtained from GetComputerName.

GBL_SYSTEM_UPTIME_HOURS

The time, in hours, since the last system reboot.

GBL_SYSTEM_UPTIME_SECONDS

The time, in seconds, since the last system reboot.

GBL_THRESHOLD_CPU

The percent of CPU that a process must use to become interesting during an interval. The default for this threshold is "5.0", which means a process must have a value of at least 5.0% for PROC_CPU_TOTAL_UTIL to exceed this threshold.

All threshold values are supplied by the parm file. A process must exceed at least one threshold value in any given interval before it will be considered interesting and be logged.

GBL_THRESHOLD_NOKILLED

This is a flag specifying that terminating processes are not interesting. The flag is set by the THRESHOLD NOKILLED statement in the parm file. If this flag is set, then the process will be logged only if it exceeds at least one of the thresholds. The default (blank) is for the flag to be turned off, which means a terminating process will be logged in the interval it exits even if it did not exceed any thresholds during that interval. This is so that the death of a process is recorded even if it does not exceed any of the thresholds.

On HP-UX, an exception to this is short-lived processes that are alive for less than one second. By default, short-lived processes are not considered interesting. However, there is a flag (THRESHOLD_SHORTLIVED) to turn on the logging of short-lived processes.

GBL_THRESHOLD_NONEW

This is a flag specifying that newly created processes are not interesting. The flag is set by the THRESHOLD NONEW statement in the parm file. If this flag is set, then the process will be logged only if it exceeds at least one of the thresholds. The default (blank) is for the flag to be turned off, which means a new process will be logged in the interval it was created even if it did not exceed any thresholds during that interval. This is so that the existence of a process is recorded even if it does not exceed any of the thresholds.

GBL_THRESHOLD_PROCMEM

The virtual memory in MB that a process must use to become interesting during an interval. The default for this threshold is 500 MB and is compared with the value of the PROC_MEM_VIRT metric.

All threshold values are supplied by the parm file. A process must exceed at least one threshold value in any given interval before it will be considered interesting and be logged.

GBL_TT_OVERFLOW_COUNT

The number of new transactions that could not be measured because the Measurement Processing Daemon's (midaemon) Measurement Performance Database is full. If this happens, the default Measurement Performance Database size is not large enough to hold all of the registered transactions on this system. This can be remedied by stopping and restarting the midaemon process using the -smdvss option to specify a larger Measurement Performance Database size. The current Measurement Performance Database size can be checked using the midaemon -sizes option.

INTERVAL

The number of seconds in the measurement interval.

For the process data class, this is the number of seconds the process was alive during the interval.

PROC_APP_ID

The ID number of the application to which the process (or kernel thread, if HP-UX) belonged during the interval.

Application "other" always has an ID of 1. There can be up to 128 user-defined applications, which are defined in the parm file.

PROC_CPU_SYS_MODE_TIME

The CPU time in system mode in the context of the process (or kernel thread, if HP-UX) during the interval.

On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation.

PROC_CPU_SYS_MODE_UTIL

The percentage of time that the CPU was in system mode in the context of the process (or kernel thread, if HP-UX) during the interval.

Unlike the global and application CPU metrics, process CPU is not averaged over the number of processors on systems with multiple CPUs. Single-threaded processes can use only one CPU at a time and never exceed 100% CPU utilization.

High system mode CPU utilizations are normal for IO intensive programs. Abnormally high system CPU utilization can indicate that a hardware problem is causing a high interrupt rate. It can also indicate programs that are not using system calls efficiently.

A classic "hung shell" shows up with very high system mode CPU because it gets stuck in a loop doing terminal reads (a system call) to a device that never responds.

On multi-processor HP-UX systems, processes which have component kernel threads executing simultaneously on different processors could have resource utilization sums over 100%. The maximum percentage is 100% times the number of CPUs online.

PROC_CPU_TOTAL_TIME

The total CPU time, in seconds, consumed by a process (or kernel thread, if HP-UX) during the interval.

On HP-UX, the total CPU time is the sum of the CPU time components for a process or kernel thread, including system, user, context switch, interrupts processing, realtime, and nice utilization values.

PROC_CPU_TOTAL_TIME_CUM

The total CPU time consumed by a process (or kernel thread, if HP-UX) over the cumulative collection time. CPU time is in seconds unless otherwise specified.

This is calculated as

   PROC_CPU_TOTAL_TIME_CUM =
     PROC_CPU_SYS_MODE_TIME_CUM + PROC_CPU_USER_MODE_TIME_CUM

PROC_CPU_TOTAL_UTIL

The total CPU time consumed by a process (or kernel thread, if HP-UX) as a percentage of the total CPU time available during the interval.

On HP-UX, the total CPU utilization is the sum of the CPU utilization components for a process or kernel thread, including system, user, context switch, interrupts processing, realtime, and nice utilization values.

PROC_CPU_TOTAL_UTIL_CUM

The total CPU time consumed by a process (or kernel thread, if HP-UX) as a percentage of the total CPU time available over the cumulative collection time.

PROC_CPU_USER_MODE_TIME

The time, in seconds, the process (or kernel threads, if HP-UX) was using the CPU in user mode during the interval.

User CPU is the time spent in user mode at a normal priority, at real-time priority (on HP-UX, AIX, and Windows systems), and at a nice priority.

PROC_CPU_USER_MODE_UTIL

The percentage of time the process (or kernel thread, if HP-UX) was using the CPU in user mode during the interval.

User CPU is the time spent in user mode at a normal priority, at real-time priority (on HP-UX, AIX, and Windows systems), and at a nice priority.

PROC_EUID

The Effective User ID of a process.

On HP-UX, this metric is specific to a process. If this metric is reported for a kernel thread, the value for its associated process is given.

PROC_GROUP_ID

On HP-UX and AIX, this is the effective group ID number of the process. On all other systems, this is the real group ID number of the process.

On HP-UX, this metric is specific to a process. If this metric is reported for a kernel thread, the value for its associated process is given.

PROC_INTERVAL_ALIVE

The number of seconds that the process (or kernel thread, if HPUX) was alive during the interval. This may be less than the time of the interval if the process (or kernel thread, if HP-UX) was new or died during the interval.

PROC_MAJOR_FAULT

Number of major page faults for this process (or kernel thread, if HP-UX) during the interval.

On HP-UX, Major page faults and minor page faults are a subset of vfaults (virtual faults). Stack and heap accesses can cause vfaults, but do not result in a disk page having to be loaded into memory.

PROC_MEM_RES

On Unix systems, this is the size (in KB) of resident memory for the process. This consists of text, data, stack, as well as the process' portion of shared memory regions (such as, shared libraries, text segments, and shared data).

On Windows, this is the number of KBs in the working set of this process. The working set includes the memory pages touched recently by the threads of the process. If free memory in the system is above a threshold, then pages are left in the working set even if they are not in use. When free memory falls below a threshold, pages are trimmed from the working set, but not necessarily paged out to disk from memory. If those pages are subsequently referenced, they will be page faulted back into the working set. Therefore, the working set is a general indicator of the memory resident set size of this process, but it will vary depending on the overall status of memory on the system. Note that the size of the working set is often larger than the amount of pagefile space consumed (PROC_MEM_VIRT).

On HP-UX, resident memory (RSS) is calculated as

   RSS = sum of private region pages +
         (sum of shared region pages / number of references)

This value is only updated when a process uses CPU. Thus, under memory pressure, this value may be higher than the actual amount of resident memory for processes which are idle.

On HP-UX 10.20, the kernel instrumentation doubles the reported size of private regions. To compensate for this, the total reported RSS for each process is halved. On HP-UX 11.0 and beyond, this metric accurately reports the resident memory for the process. Note, a value of "na" may be shown for the swapper process.

On SUN, a value of "na" is displayed when this information is unobtainable. This information is not obtained for the fsflush, pageout and sched processes. It may also be unavailable for <defunct> processes.

On AIX, this is the same as the RSS value shown by "ps v".

On HP-UX, this metric is specific to a process. If this metric is reported for a kernel thread, the value for its associated process is given.

PROC_MEM_VIRT

On HP-UX, this consists of the sum of the virtual set size of all private and shared memory regions used by this process. This metric is not affected by the reference count for those regions which are shared.

Note, a value of "na" may be shown for the swapper process.

On HP-UX, this metric is specific to a process. If this metric is reported for a kernel thread, the value for its associated process is given.

On all other Unix systems, this is the number of KBs of virtual memory allocated to the process. This consists of private text, private data, private stack and shared memory.

On Windows, this is the number of KBs the process has used in the paging file(s). Paging files are used to store pages of memory used by the process, such as local data, that are not contained in other files. Examples of memory pages which are contained in other files include pages storing a program's .EXE and .DLL files. These would not be kept in pagefile space. Thus, often programs will have a memory working set size (PROC_MEM_RES) larger than the size of its pagefile space.

On SUN, a value of "na" is displayed when this information is unobtainable. This information is not obtained for the fsflush, pageout and sched processes. It may also not be available for <defunct> processes.

PROC_MINOR_FAULT

Number of minor page faults for this process (or kernel thread, if HP-UX) during the interval.

PROC_PAGEFAULT

The number of page faults that occurred during the interval for the process.

PROC_PAGEFAULT_RATE

The number of page faults per second that occurred during the interval for the process.

PROC_PARENT_PROC_ID

The parent process' PID number.

On HP-UX, this metric is specific to a process. If this metric is reported for a kernel thread, the value for its associated process is given.

PROC_PRI

On Unix systems, this is the dispatch priority of a process (or kernel thread, if HP-UX) at the end of the interval. The lower the value, the more likely the process is to be dispatched.

On Windows, this is the current base priority of this process.

On HP-UX, whenever the priority is changed for the selected process or kernel thread, the new value will not be reflected until the process or kernel thread is reactivated if it is currently idle (for example, SLEEPing).

On HP-UX, the lower the value, the more the process or kernel thread is likely to be dispatched. Values between zero and 127 are considered to be "real-time" priorities, which the kernel does not adjust. Values above 127 are normal priorities and are modified by the kernel for load balancing. Some special priorities are used in the HP-UX kernel and subsystems for different activities. These values are described in /usr/include/sys/param.h. Priorities less than PZERO 153 are not signalable.

Note that on HP-UX, many network-related programs such as inetd, biod, and rlogind run at priority 154 which is PPIPE. Just because they run at this priority does not mean they are using pipes. By examining the open files, you can determine if a process or kernel thread is using pipes.

For HP-UX 10.0 and later releases, priorities between -32 and -1 can be seen for processes or kernel threads using the Posix Realtime Schedulers. When specifying a Posix priority, the value entered must be in the range from 0 through 31, which the system then remaps to a negative number in the range of -1 through -32. Refer to the rtsched man pages for more information.

On a threaded operating system, such as HP-UX 11.0 and beyond, this metric represents a kernel thread characteristic. If this metric is reported for a process, the value for its last executing kernel thread is given. For example, if a process has multiple kernel threads and kernel thread one is the last to execute during the interval, the metric value for kernel thread one is assigned to the process.

On AIX, values for priority range from 0 to 127. Processes running at priorities less than PZERO (40) are not signalable.

On Windows, the higher the value the more likely the process or thread is to be dispatched. Values for priority range from 0 to 31. Values of 16 and above are considered to be "realtime" priorities. Threads within a process can raise and lower their own base priorities relative to the process's base priority.

On Sun Systems this metric is only available on 4.1.X.

PROC_PROC_ARGV1

The first argument (argv[1]) of the process argument list or the second word of the command line, if present.

PROC_PROC_ID

The process ID number (or PID) of this process that is used by the kernel to uniquely identify this process. Process numbers are reused, so they only identify a process for it's lifetime.

On HP-UX, this metric is specific to a process. If this metric is reported for a kernel thread, the value for its associated process is given.

PROC_PROC_NAME

The process program name. It is limited to 16 characters.

On Unix systems, this is derived from the 1st parameter to the exec(2) system call.

On HP-UX, this metric is specific to a process. If this metric is reported for a kernel thread, the value for its associated process is given.

On Windows, the "System Idle Process" is not reported by the MeasureWare Agent since Idle is a process that runs to occupy the processors when they are not executing other threads. Idle has one thread per processor.

PROC_RUN_TIME

The elapsed time since a process (or kernel thread, if HP-UX) started, in seconds.

This metric is less than the interval time if the process (or kernel thread, if HP-UX) was not alive during the entire first or last interval.

On a threaded operating system such as HP-UX 11.0 and beyond, this metric is available for a process or kernel thread.

PROC_STOP_REASON

A text string describing what caused the process (or kernel thread, if HP-UX) to stop executing. For example, if the process is waiting for a CPU while higher priority processes are executing, then its block reason is PRI. A complete list of block reasons follows:

String   Reason for Process Block
------------------------------------
died    Process terminated during
        the interval.

new     Process was created (via the
        exec() system call) during
        the interval.

NONE    Process is ready to run.  It
        is not apparent that the
        process is blocked.

OTHER   Waiting for a reason not
        decipherable by the
        measurement software.

PRI     Process is on the run queue.

SLEEP   Waiting for an event to
        complete.

TRACE   Received a signal to stop
        because parent is tracing
        this process.

ZOMB    Process has terminated and
        the parent is not waiting.

PROC_THREAD_COUNT

The total number of kernel threads for the current process.

PROC_TTY

The controlling terminal for a process. This field is blank if there is no controlling terminal. On HP-UX, Linux, and AIX, this is the same as the "TTY" field of the ps command.

On all other Unix systems, the controlling terminal name is found by searching the directories provided in the /etc/ttysrch file. See man page ttysrch(4) for details. The matching criteria field ("M", "F" or "I" values) of the ttysrch file is ignored. If a terminal is not found in one of the ttysrch file directories, the following directories are searched in the order here: "/dev", "/dev/pts", "/dev/term" and "dev/xt". When a match is found in one of the "/dev" subdirectories, "/dev/" is not displayed as part of the terminal name. If no match is found in the directory searches, the major and minor numbers of the controlling terminal are displayed. In most cases, this value is the same as the "TTY" field of the ps command.

On HP-UX, this metric is specific to a process. If this metric is reported for a kernel thread, the value for its associated process is given.

PROC_USER_NAME

On Unix systems, this is the login account of a process (from /etc/passwd). If more than one account is listed in /etc/passwd with the same user ID (uid) field, the first one is used. If an account cannot be found that matches the uid field, then the uid number is returned. This would occur if the account was removed after a process was started.

On Windows, this is the process owner account name, without the domain name this account resides in.

On HP-UX, this metric is specific to a process. If this metric is reported for a kernel thread, the value for its associated process is given.

RECORD_TYPE

ASCII string that identifies the record. Possibilities include:

GLOB for global 5 minute detail
GSUM for global hourly summary
APPL for application 5 minute detail
ASUM for application hourly summary
CONF for configuration
TRAN for transaction tracker  detail
TSUM for transaction tracker summary

Except for Windows Desktop, this includes:

PROC for process 1 minute detail
DISK for disk device 5 minute detail
DSUM for disk device summary

On HP-UX, this also includes:

VOLS for logical volume disk detail
VSUM for logical volume disk summary

TBL_FILE_LOCK_AVAIL

The configured number of file or record locks that can be allocated on the system. Files and/or records are locked by calls to lockf(2).

TBL_FILE_LOCK_USED

The number of file or record locks currently in use. One file can have multiple locks. Files and/or records are locked by calls to lockf(2).

On Unix systems, this metric is updated every 30 seconds or the sampling interval, whichever is greater.

TBL_FILE_LOCK_UTIL

The percentage of configured file or record locks currently in use.

On Unix systems, this metric is updated every 30 seconds or the sampling interval, whichever is greater.

TBL_INODE_CACHE_AVAIL

On HP-UX, this is the configured total number of entries for the incore inode tables on the system. For HP-UX releases prior to 11.2x, this value reflects only the HFS inode table. For subsequent HP-UX releases, this value is the sum of inode tables for both HFS and VxFS file systems (ninode plus vxfs_ninode).

On HP-UX, file system directory activity is done through inodes that are stored on disk. The kernel keeps a memory cache of active and recently accessed inodes to reduce disk IOs. When a file is opened through a pathname, the kernel converts the pathname to an inode number and attempts to obtain the inode information from the cache based on the filesystem type. If the inode entry is not in the cache, the inode is read from disk into the inode cache.

On HP-UX, the number of used entries in the inode caches are usually at or near the capacity. This does not necessarily indicate that the configured sizes are too small because the tables may contain recently used inodes and inodes referenced by entries in the directory name lookup cache. When a new inode cache entry is required and a free entry does not exist, inactive entries referenced by the directory name cache are used. If after freeing inode entries only referenced by the directory name cache does not create enough free space, the message "inode: table is full" message may appear on the console. If this occurs, increase the size of the kernel parameter, ninode. Low directory name cache hit ratios may also indicate an underconfigured inode cache.

On HP-UX, the default formula for the ninode size is:

  ninode = ((nproc+16+maxusers)+32+ (2*npty)+(4*num_clients))

On all other Unix systems, this is the number of entries in the inode cache. This is a size. All entries are not always in use. The cache size is dynamic.

Entries in this cache are reused as files are closed and new ones are opened. The size of the cache will go up or down in chunks as more or less space is required in the cache.

Inodes are used to store information about files within the file system. Every file has at least two inodes associated with it (one for the directory and one for the file itself). The information stored in an inode includes the owners, timestamps, size, and an array of indices used to translate logical block numbers to physical sector numbers. There is a separate inode maintained for every view of a file, so if two processes have the same file open, they both use the same directory inode, but separate inodes for the file.

TBL_INODE_CACHE_USED

The number of inode cache entries currently in use.

On HP-UX, this is the number of "non-free" inodes currently used. Since the inode table contains recently closed inodes as well as open inodes, the table often appears to be fully utilized. When a new entry is needed, one can usually be found by reusing one of the recently closed inode entries.

On HP-UX, the default formula for the ninode size is:

  ninode = ((nproc+16+maxusers)+32+ (2*npty)+(4*num_clients))

On Unix systems, this metric is updated every 30 seconds or the sampling interval, whichever is greater.

TBL_SHMEM_ACTIVE

The size (in KBs unless otherwise specified) of the resident shared memory segments that have running processes attached to them. This may be less than the amount of shared memory used on the system because a shared memory segment may exist and not have any process attached to it.

On Unix systems, this metric is updated every 30 seconds or the sampling interval, whichever is greater.

TBL_SHMEM_TABLE_AVAIL

The configured number of shared memory segments that can be allocated on the system.

On SUN, the InterProcess Communication facilities are dynamically loadable. If the amount available is zero, this facility was not loaded when data collection began, and its data is not obtainable. The data collector is unable to determine that a facility has been loaded once data collection has started. If you know a new facility has been loaded, restart the data collection, and the data for that facility will be collected. See ipcs(1) to report on interprocess communication resources.

TBL_SHMEM_TABLE_USED

On HP-UX, this is the number of shared memory segments currently in use. A shared memory segment is allocated by a program using the shmget(2) call. Also refer to ipcs(1).

On all other Unix systems, this is the number of shared memory segments that have been built. This includes shared memory segments with no processes attached to them. A shared memory segment is allocated by a program using the shmget(2) call. See ipcs(1) to list shared memory segments.

On Unix systems, this metric is updated every 30 seconds or the sampling interval, whichever is greater.

TBL_SHMEM_TABLE_UTIL

The percentage of configured shared memory segments currently in use.

On Unix systems, this metric is updated every 30 seconds or the sampling interval, whichever is greater.

TBL_SHMEM_USED

The size (in KBs unless otherwise specified) of the resident shared memory segments.

This may be less than the amount requested if any segments are swapped out. It may be greater than the amount requested due to internal fragmentation of the shared memory pool.

Additionally on SUN, it includes memory segments to which no processes are attached. If a shared memory segment has zero attachments, the space may not always be allocated in memory. See ipcs(1) to list shared memory segments.

On Unix systems, this metric is updated every 30 seconds or the sampling interval, whichever is greater.

TIME

The local time of day for the start of the interval. The time is an ASCII field in hh:mm 24-hour format. This field will always contain 5 characters in ASCII files. The two subfields (hh, mm) will contain a leading zero if the value is less than 10. This metric is extracted from GBL_STATTIME, which is obtained using the time() system call at the start of the interval.

This field responds to language localization.

In binary files this field contains four byte size subfields. The most significant byte contains the hour, the next most significant byte contains the minute, then the seconds and finally the tenths of a second. The left two bytes can be isolated by dividing by 65536. HHMM = TIME/65536. Then HOUR = HHMM/256 and MINUTE = HHMM mod 256.

TT_ABORT

The number of aborted transactions during the last interval for this transaction.

TT_APP_NAME

The registered ARM Application name.

TT_CLIENT_ADDRESS

The correlator address. This is the address where the child transaction originated.

TT_TRAN_1_MIN_RATE

For this transaction name, the number of completed transactions calculated to a 1 minute rate. For example, if you completed five of these transactions in a 5 minute window, the rate is one transaction per minute.

On SUN systems, this metric is only available on 5.X or later.

TT_CLIENT_TRAN_ID

A numerical ID that uniquely identifies the transaction class in this correlator.

TT_COUNT

The number of completed transactions during the last interval for this transaction.

TT_FAILED

The number of Failed transactions during the last interval for this transaction name.

TT_INFO

The registered ARM Transaction Information for this transaction.

TT_NAME

The registered transaction name for this transaction.

TT_SLO_COUNT

The number of completed transactions that violated the defined Service Level Objective (SLO) by exceeding the SLO threshold time during the interval.

TT_SLO_PERCENT

The percentage of transactions which violate service level objectives.

On SUN systems, this metric is only available on 5.X or later.

TT_SLO_THRESHOLD

The upper range (transaction time) of the Service Level Objective (SLO) threshold value. This value is used to count the number of transactions that exceed this user-supplied transaction time value.

TT_TRAN_ID

The registered ARM Transaction ID for this transaction class as returned by arm_getid(). A unique transaction id is returned for a unique application id (returned by arm_init), tran name, and meta data buffer contents.

TT_UNAME

The registered ARM Transaction User Name for this transaction.

If the arm_init function has NULL for the appl_user_id field, then the user name is blank. Otherwise, if "*" was specified, then the user name is displayed.

For example, to show the user name for the armsample1 program, use:

   appl_id = arm_init("armsample1","*",0,0,0);

To ignore the user name for the armsample1 program, use:

   appl_id = arm_init("armsample1",NULL,0,0,0);

TT_WALL_TIME_PER_TRAN

The average transaction time, in seconds, during the last interval for this transaction.

TT_USER_MEASUREMENT_AVG

If the measurement type is a numeric or a string, this metric returns "na".

If the measurement type is a counter, this metric returns the average counter differences of the transaction or transaction instance during the last interval. The counter value is the difference observed from a counter between the start and the stop (or last update) of a transaction.

If the measurement type is a gauge, this returns the average of the values passed on any ARM call for the transaction or transaction instance during the last interval.

TT_USER_MEASUREMENT_AVG_2

If the measurement type is a numeric or a string, this metric returns "na".

If the measurement type is a gauge, this returns the average of the values passed on any ARM call for the transaction or transaction instance during the last interval.

TT_USER_MEASUREMENT_AVG_3

If the measurement type is a numeric or a string, this metric returns "na".

If the measurement type is a gauge, this returns the average of the values passed on any ARM call for the transaction or transaction instance during the last interval.

TT_USER_MEASUREMENT_AVG_4

If the measurement type is a numeric or a string, this metric returns "na".

If the measurement type is a gauge, this returns the average of the values passed on any ARM call for the transaction or transaction instance during the last interval.

TT_USER_MEASUREMENT_AVG_5

If the measurement type is a numeric or a string, this metric returns "na".

If the measurement type is a gauge, this returns the average of the values passed on any ARM call for the transaction or transaction instance during the last interval.

TT_USER_MEASUREMENT_AVG_6

If the measurement type is a numeric or a string, this metric returns "na".

If the measurement type is a gauge, this returns the average of the values passed on any ARM call for the transaction or transaction instance during the last interval.

TT_USER_MEASUREMENT_MAX

If the measurement type is a numeric or a string, this metric returns "na".

If the measurement type is a counter, this metric returns the highest measured counter value over the life of the transaction or transaction instance. The counter value is the difference observed from a counter between the start and the stop (or last update) of a transaction.

If the measurement type is a gauge, this metric returns the highest value passed on any ARM call over the life of the transaction or transaction instance.

TT_USER_MEASUREMENT_MAX_2

If the measurement type is a numeric or a string, this metric returns "na".

If the measurement type is a gauge, this metric returns the highest value passed on any ARM call over the life of the transaction or transaction instance.

TT_USER_MEASUREMENT_MAX_3

If the measurement type is a numeric or a string, this metric returns "na".

If the measurement type is a gauge, this metric returns the highest value passed on any ARM call over the life of the transaction or transaction instance.

TT_USER_MEASUREMENT_MAX_4

If the measurement type is a numeric or a string, this metric returns "na".

If the measurement type is a gauge, this metric returns the highest value passed on any ARM call over the life of the transaction or transaction instance.

TT_USER_MEASUREMENT_MAX_5

If the measurement type is a numeric or a string, this metric returns "na".

If the measurement type is a gauge, this metric returns the highest value passed on any ARM call over the life of the transaction or transaction instance.

TT_USER_MEASUREMENT_MAX_6

If the measurement type is a numeric or a string, this metric returns "na".

If the measurement type is a gauge, this metric returns the highest value passed on any ARM call over the life of the transaction or transaction instance.

TT_USER_MEASUREMENT_MIN

If the measurement type is a numeric or a string, this metric returns "na".

If the measurement type is a counter, this metric returns the lowest measured counter value over the life of the transaction or transaction instance. The counter value is the difference observed from a counter between the start and the stop (or last update) of a transaction.

If the measurement type is a gauge, this metric returns the lowest value passed on any ARM call over the life of the transaction or transaction instance.

TT_USER_MEASUREMENT_MIN_2

If the measurement type is a numeric or a string, this metric returns "na".

If the measurement type is a gauge, this metric returns the lowest value passed on any ARM call over the life of the transaction or transaction instance.

TT_USER_MEASUREMENT_MIN_3

If the measurement type is a numeric or a string, this metric returns "na".

If the measurement type is a gauge, this metric returns the lowest value passed on any ARM call over the life of the transaction or transaction instance.

TT_USER_MEASUREMENT_MIN_4

If the measurement type is a numeric or a string, this metric returns "na".

If the measurement type is a gauge, this metric returns the lowest value passed on any ARM call over the life of the transaction or transaction instance.

TT_USER_MEASUREMENT_MIN_5

If the measurement type is a numeric or a string, this metric returns "na".

If the measurement type is a gauge, this metric returns the lowest value passed on any ARM call over the life of the transaction or transaction instance.

TT_USER_MEASUREMENT_MIN_6

If the measurement type is a numeric or a string, this metric returns "na".

If the measurement type is a gauge, this metric returns the lowest value passed on any ARM call over the life of the transaction or transaction instance.

TT_USER_MEASUREMENT_NAME

The name of the user defined transactional measurement. The length of the string complies with the ARM 2.0 standard, which is 44 characters long (there are 43 usable characters since this is a NULL terminated character string).

TT_USER_MEASUREMENT_NAME_2

TT_USER_MEASUREMENT_NAME_3

TT_USER_MEASUREMENT_NAME_4

TT_USER_MEASUREMENT_NAME_5

TT_USER_MEASUREMENT_NAME_6

TTBIN_TRANS_COUNT_1

The number of completed transactions in this range during the last interval.

On Sun systems, this metric is only available on 5.X or later.

TTBIN_TRANS_COUNT_2

The number of completed transactions in this range during the last interval.

On Sun systems, this metric is only available on 5.X or later.

TTBIN_TRANS_COUNT_3

The number of completed transactions in this range during the last interval.

On Sun systems, this metric is only available on 5.X or later.

TTBIN_TRANS_COUNT_4

The number of completed transactions in this range during the last interval.

On Sun systems, this metric is only available on 5.X or later.

TTBIN_TRANS_COUNT_5

The number of completed transactions in this range during the last interval.

On Sun systems, this metric is only available on 5.X or later.

TTBIN_TRANS_COUNT_6

The number of completed transactions in this range during the last interval.

On Sun systems, this metric is only available on 5.X or later.

TTBIN_TRANS_COUNT_7

The number of completed transactions in this range during the last interval.

On Sun systems, this metric is only available on 5.X or later.

TTBIN_TRANS_COUNT_8

The number of completed transactions in this range during the last interval.

On Sun systems, this metric is only available on 5.X or later.

TTBIN_TRANS_COUNT_9

The number of completed transactions in this range during the last interval.

On Sun systems, this metric is only available on 5.X or later.

TTBIN_TRANS_COUNT_10

The number of completed transactions in this range during the last interval.

On Sun systems, this metric is only available on 5.X or later.

TTBIN_UPPER_RANGE_1

The upper range (transaction time) for this bin.

There are a maximum of nine user-defined transaction response time bins (TTBIN_UPPER_RANGE). The last bin, which is not specified in the transaction configuration file (ttdconf.mwc on Windows or ttd.conf on UNIX platforms), is the overflow bin and will always have a value of -2 (overflow). Note that the values specified in the transaction configuration file cannot exceed 2147483.6, which is the number of seconds in 24.85 days. If the user specifies any values greater than 2147483.6, the numbers reported for those bins or Service Level Objectives (SLO) will be -2.

On Sun systems, this metric is only available on 5.X or later.

TTBIN_UPPER_RANGE_2

The upper range (transaction time) for this bin.

On Sun systems, this metric is only available on 5.X or later.

TTBIN_UPPER_RANGE_3

The upper range (transaction time) for this bin.

On Sun systems, this metric is only available on 5.X or later.

TTBIN_UPPER_RANGE_4

The upper range (transaction time) for this bin.

On Sun systems, this metric is only available on 5.X or later.

TTBIN_UPPER_RANGE_5

The upper range (transaction time) for this bin.