TPDC Manual (G06.24+)
Table Of Contents
- What’s New in This Manual
- About This Manual
- 1 TPDC Overview
- TPDC Components and Architecture
- Tandem Performance Data Collector (TPDC)
- Tandem Performance System File Label (TPSFL)
- Tandem Performance File Label (TPFL)
- Tandem Performance Load Measure (TPLM)
- Tandem Performance Load Data (TPLD)
- System Performance Analysis Using Measure (SPAM)
- Tandem Performance Deferred Processing (TPDP)
- Data Files (RWS, DWS, UWS)
- How TPDC Collects Data
- Example: Scheduling TPDC Data Collection
- TPDC Components and Architecture
- 2 Installing and Running TPDC
- 3 Using the Collected Data
- 4 Using the System Configuration Reports
- 5 Using the SPAM Performance Data Charts and Reports
- Overview of the Charts and Reports
- Performance Data Charts
- Acceleration Profiles of User Programs (AXLCHRT)
- Apportioned Program CPU Consumption (WKLOAD)
- Average CPU Utilization (ACUCHRT)
- Average Disc Utilization (ADUCHRT)
- Data Communications Line Overview (DATACOM)
- Disc Cache Performance (DCPCHRT)
- Disc File Block Splits Shares (BLKSPLT)
- Disc File I/O Activity Distribution (DFIODST)
- Disc File Overview (Alphabetic) (DFOATBL)
- Disc File Physical I/O Shares (DFPIOS)
- Disc File ‘Requests Blocked’ Shares (REQBLKD)
- Disc File System I/O Shares (DFSIOS)
- Disc I/Os per Second (DIOCHRT)
- Disc Response Time (DRTCHRT)
- EXPAND Communications Line Overview (EXPAND)
- Global Indicators (COVER)
- Logical Disc File I/O Wait Shares (LDFIOWT)
- SQL/MP Program Overview (SQLPROG)
- SQL/MP Statement Overview (SQLSTAT)
- Process Category Counts (PCOUNTS)
- Process/CPU Priority Distribution (PRIDIST)
- Program Disc File I/O Wait Shares (PGDIOWT)
- Program Logical File Open Shares (PGOPENS)
- Program Logical I/O Wait Shares (PGLIOWT)
- Program Overview (PGOVIEW)
- Program Spooler File I/O Wait Shares (PGSPLWT)
- Relative CPU Balance (RCBCHRT)
- Relative Disc Balance (RDBCHRT)
- TMF Overview (TMFVIEW)
- Performance Data Reports
- Busiest Disc Files (Logical I/O Wait Time, Overall) (IOWOVER)
- Busiest Disc Files (Logical I/Os, by Volume) (LIOBVOL)
- Busiest Disc Files (Physical I/Os, by Volume) (PIOBVOL)
- Busiest Disc Files (System I/Os, by Volume) (SIOBVOL)
- Busiest Processes (by CPU) (PBSYCPU)
- CPU Activity (CPUREPT)
- Disc Cache 1 (Activity, by Block Size) (CACHE1)
- Disc Process Activity (DPREPT)
- Disc Subsystem Activity (DSCREPT)
- EXPAND Network Line Activity (NETREPT)
- Global Indicators (COVER)
- Low Selectivity (Needle in a Haystack) SQL Table Access Report (HAYSTCK)
- Network System Activity (SYSREPT)
- New Process Creation Timeline (NEWPROC)
- PATHWAY System Processes (PATHWAY)
- Physical Disc I/O Activity (PDISCIO)
- Process Existence Timeline (PTIMLIN)
- Process Memory Utilization (by CPU) (PMEMCPU)
- Process Page Faults (by CPU) (PFLTCPU)
- Server Summary (from $RECEIVE File) (SERVICE)
- TMF Activity Report (TMFREPT)
- A Entity and Attribute Definitions
- B Cross-Reference of Enform Queries to Data Files
- C Enform Query Source File (QPGROUPS)
- Index
About This Manual
Tandem Performance Data Collector (TPDC) Manual—526357-001
xiv
Notation for Management Programming Interfaces
lowercase italic letters. Lowercase italic letters indicate variable items whose values are
displayed or returned. For example:
p-register
process-name
[ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed. For
example:
Event number = number [ Subject = first-subject-value ]
A group of items enclosed in brackets is a list of all possible items that can be
displayed, of which one or none might actually be displayed. The items in the list can
be arranged either vertically, with aligned brackets on each side of the list, or
horizontally, enclosed in a pair of brackets and separated by vertical lines. For
example:
proc-name trapped [ in SQL | in SQL file system ]
{ } Braces. A group of items enclosed in braces is a list of all possible items that can be
displayed, of which one is actually displayed. The items in the list can be arranged
either vertically, with aligned braces on each side of the list, or horizontally, enclosed in
a pair of braces and separated by vertical lines. For example:
obj-type obj-name state changed to state, caused by
{ Object | Operator | Service }
process-name State changed from old-objstate to objstate
{ Operator Request. }
{ Unknown. }
| Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in
brackets or braces. For example:
Transfer status: { OK | Failed }
% Percent Sign. A percent sign precedes a number that is not in decimal notation. The
% notation precedes an octal number. The %B notation precedes a binary number.
The %H notation precedes a hexadecimal number. For example:
%005400
%B101111
%H2F
P=%p-register E=%e-register
Notation for Management Programming Interfaces
This list summarizes the notation conventions used in the boxed descriptions of
programmatic commands, event messages, and error lists in this manual.