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
2-1
2 Installing and Running TPDC
Installing TPDC
You use DSM/SCM to move the TPDC product files from the site update tape (SUT) to
your disk. For more information about DSM/SCM, see the DSM/SCM User’s Guide.
TPDC installation does not require a system generation (SYSGEN) and has minimal
impact on the system.
Task 1: Install the TPDC Product Files
1. Run DSM/SCM to install TPDC. See the DSM/SCM User’s Guide.
2. Log on as the super ID.
3. Volume to the disk location of the TPDC product files:
1>VOLUME $volname.ZTPDC
4. Run FUP/in SECURE/, which results in:
•
Ownership of the object files (TPFL and TPSFL) is given to the super ID.
•
The object files’s security is set to A-A-.
•
The PROGID attribute is set to ON for these object files.
The two object files can now read the volume disk directories.
At execution, the Tandem Performance System File Label (TPSFL) component
performs several basic checks to ensure that it can operate successfully, including
validating that the object file for TPSFL is owned by the super ID and the PROG-ID
attribute is set. The TPFL and TPSFL components must be owned by the super ID with
the PROGID attribute set so that TPSFL can obtain access to the disk directories on
the system.
DP2 provides a variety of levels of security to ensure that no one writes data to the
drive, so there is no exposure for the data on the drive.
To leave the component object files in the distribution subvolume, use the RUN
command:
$volume.ZTPDC.Componentname/ options/ runstring
Topic Page
Installing TPDC
2-1
Running TPDC (Data Collection) 2-5
Running Deferred Processing (TPDP) 2-7