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
TPDC Overview
Tandem Performance Data Collector (TPDC) Manual—526357-001
1-4
Tandem Performance Load Data (TPLD)
Tandem Performance Load Data (TPLD)
The TPLD component loads the consolidated data file and creates component TPDC
entity data files, from which you can generate optional reports using Enform and other
programs.
System Performance Analysis Using Measure (SPAM)
The SPAM component loads the consolidated performance data (UWS) file and
creates both Measure and aggregate entity files used to generate reports. After all of
these entities are created, the HP Enform product can use the compiled queries to
generate performance charts and reports.To invoke SPAM use the TGATHER TACL
macro. The compiled queries are invoked by the TPRODUCE TACL macro.
Tandem Performance Deferred Processing (TPDP)
The TPDP component can be run at any time to generate consolidated performance
data (UWS) files based on data you have collected and retained on disk using TPDC.
Using deferred processing (by running TPDC with the DEFER option and later using
TPDP) lets you perform the processor-intensive UWS file creation at a time when your
system resources are less in demand. The DEFER option notifies TPDC to retain its
data, but you must notify TPDP to retain the data as well, or the data (DWS file and
raw Measure data) is not kept after TPDP runs.
Data Files (RWS, DWS, UWS)
Three data file formats are used during TPDC processing:
•
RWS file — Created by TPDC at the start of data collection. This file stores all
collected data while TPDC runs. At the end of data collection, TPDC uses this file’s
data to create the DWS file. Once the DWS file is created, the RWS file is purged.
If TPDC terminates unexpectedly, or if the CPU TPDC runs on fails during data
collection, the RWS file can be used as the input file into TPDP or to generate
reports on the collected data even though TPDC did not create a DWS file for it.
•
DWS file — Created by TPDC at the end of data collection based on the RWS file
data. This file optimizes the data so it can be fed into the consolidated UWS file
format.
Unless otherwise specified, the DWS file is deleted once it is used to create a
UWS file. Therefore, to keep performance data on your system so you can later
generate more reports from it, when running TPDC, TPDP, or to specify that the
DWS file be retained, use the RETAIN option.
•
UWS file — created by TPDC itself, TPDP, or based on the DWS (or RWS) file.
These consolidated performance data files are used directly to create the
performance reports for your system. For interval processing, a UWS file is created
for each interval.