ENABLE TDPSTATS - Teradata Director Program

Teradata® Director Program Reference - 17.20

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Teradata Director Program
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-11-17
dita:mapPath
cki1641301536147.ditamap
dita:ditavalPath
obe1474387269547.ditaval
dita:id
frc1470439950465
Product Category
Teradata Tools and Utilities

Purpose

TDPSTATS measures the performance and assesses the efficiency of data movement between TDP and the database. TDPSTATS collects the following information over the course of one-minute intervals, then displays it on a normalized per second basis:
  • I/O count from the database to TDP
  • Messages received
  • Input retries
  • Kbytes received
  • I/O count from TDP to the database
  • Messages sent
  • Transmission retries
  • Kbytes sent

This data is useful for application tuning as well as performance benchmarking. The Kbytes in and Kbytes out values provide an overall measure of throughput efficiency.

Syntax



Usage Notes

TDPSTATS is stopped by the DISA TDPSTATS command. Use the DISPLAY TDPSTATS command to determine the status of TDPSTATS.

You can configure TDPSTATS to route output to the system console, or to a data set. The advantage of routing to the console is that you can view the data in real time, make adjustments to various tuning parameters, and observe the results immediately. The disadvantage is that the console can become cluttered with messages from TDPSTATS. The advantage of routing to a data set is that the data can be collected automatically and post-processed using a product such as Microsoft Excel to produce historical graphs or charts that can depict performance trends over longer periods of time. The disadvantage is the concomitant loss of immediacy.

To route data to the console, enter ENA TDPSTATS. At one-minute intervals, TDSPTATS writes two messages to the console (one for input statistics and the other for output statistics). This continues until TDPSTATS is terminated by entering DISA TDPSTATS, or until a TDP shutdown occurs.

To route data to a data set, include a DD statement to identify a sequential data set in the JCL for the TDP started task. The DDNAME of this file must be TDPSTATS. Generation data groups (GDGs) are acceptable, as is SYSOUT.

At one-minute intervals, TDPSTATS writes one record to this file using QSAM. Following are typical entries:

TDPSTATS FOR TDPC (VALUES ARE PER SECOND SAMPLED AT ONE-MINUTE INTERVALS
YYYY.DDD,HH:MM,IOIN,MSGSIN,RTRYIN,KBYTIN,IOOUT,MSGSOU,RTRYOU,KBYTOU
1999.215,09:51,000008,000064,000000,001455,000007,000063,000000,001593
1999.215,09:52,000000,000000,000000,000000,000000,000000,000000,000000
1999.215,09:53,000000,000000,000000,000000,000000,000000,000000,000000

The first record identifies the output as being generated by TDPSTATS for a specific TDP (in this case, TDPC).

The second record provides a legend for easier readability. Note that the actual data values are comma-separated; this facilitates their input into a spreadsheet program like Excel.

In both console and data set modes, if the communication configuration is changed (for example, starting and or stopping one or more CPs or NPs) while TDPSTATS is active, data associated with the current interval is discarded and TDPSTATS will be re-initialized. This results in the loss of data from one one-minute interval.

In data set mode, if an OPEN/CLOSE/EOV failure or I/O error associated with the TDPSTATS file occurs, TDPSTATS is permanently disabled for the life of the TDP address space, and restarting TDPSTATS will require restarting TDP.

Example: ENABLE TDPSTATS

ENABLE TDPSTATS

Completion Message

TDP2500 TDP THROUGHPUT STATISTICS REPORTER ENABLED