TDP1282 type USAGE: nnnnn MESSAGES, nnnnn I/O, nnnnn BYTES - Teradata Tools and Utilities

Teradata Director Program (TDP Prefix) Messages

Product
Teradata Tools and Utilities
Release Number
15.xx,16.xx
Language
English (United States)
Last Update
2018-10-23
dita:id
B035-1096-TDP
lifecycle
latest
Product Category
Teradata® Tools and Utilities

TDP1282 type USAGE: nnnnn MESSAGES, nnnnn I/O, nnnnn BYTES

Explanation:

In response to a "DISPLAY CP DETAIL" or "DISPLAY NP DETAIL" command, this message is issued once for the OUTPUT direction, once for the INPUT direction, and if the TDP INITIAL SELECTCP LOWDATA command is in effect, once to TOTAL both directions, to display the number of Teradata Database messages (requests for OUTPUT; responses for INPUT), the number of I/Os (using the channel for CPs; using the network for NPs), and the number of bytes transferred.

Notes:

The number of I/Os does not equal the number of messages because multiple short messages may require only one I/O whereas long messages may require multiple I/Os. For NP input using the TCP transport, TCP may return from one byte to the maximum size of an encapsulation transfer, so the number of receive operations needed to obtain any one response could be very large. For NPs, the input and output I/O counts include exchanges to ensure that network communication is intact, and also include explicit confirmations that data sent is received, both of which will increase the I/O count beyond the message count, even when there are no application requests active. So for NPs, the I/O count includes network and encapsulation imposed overhead. The number of bytes is greater than the length of requests sent or responses received by the application because of added boilerplate required by the Teradata Database for every request and response, as well as added boilerplate required by the protocol used to communicate with the Database (which differs for CIC-type CPs, CCU-type CPs, or NPs).

Generated By:

TDP.