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

Tandem Performance Data Collector (TPDC) Manual—526357-001
1-1
1 TPDC Overview
The Tandem Performance Data Collector (TPDC) is an HP host-based performance
data collection and relationship product for HP NonStop Kernel systems. TPDC
significantly reduces the expertise and manpower required to collect performance data.
It provides an all-in-one approach to collection and integration of performance
information.
One of the challenges in performance analysis is making sure that you have all the
data necessary to perform the analysis successfully. To correctly evaluate
measurement data, you need several pieces of information. You need to:
•
Know the configuration of software and hardware components on the system.
•
Make sure that no dynamic changes take place during the period measured.
To acquire all this information on a NonStop Kernel system requires the use of several
software tools, which you do not need to access directly with TPDC: Measure, FUP,
PUP, PEEK, SCF, and DSAP.
By carefully coordinating the scheduling and execution of these tools, you can get
accurate information about the running environment and items in the period of interest.
You can defer processing to times when system resources are more available, and you
can measure small intervals within a measuring period for greater levels of detail.
Unfortunately, the data from these different tools is not in a consistent format for
analysis. A lot of the data (from FUP, PUP, PEEK, SCF, and DSAP) is in ASCII report
format instead of data structures, which makes relating the data difficult. Also, report
data formats could change in certain tools, which could further complicate matters.
TPDC collects the data from all these sources and consolidates it into a single,
consistent data source so you can analyze all the information for a measured period
together.
Topic Page
TPDC Components and Architecture
1-2
How TPDC Collects Data 1-5
Example: Scheduling TPDC Data Collection 1-8