114 lines
8.8 KiB
XML
114 lines
8.8 KiB
XML
|
<?xml:stylesheet version="1.0" encoding="utf-8"?>
|
||
|
|
<?xml:stylesheet type="text/xsl" href="../rzahg/icdyntable.xsl"?>
|
||
|
|
<TABLE xmlns="x-schema:rzahxqapmdps-schema.xml">
|
||
|
|
<TITLE>Performance data files: QAPMDPS</TITLE>
|
||
|
|
<TH col="TD1">
|
||
|
|
Field Name
|
||
|
|
</TH>
|
||
|
|
<TH col="TD2">
|
||
|
|
Description
|
||
|
|
</TH>
|
||
|
|
<TH col="TD3">
|
||
|
|
Attribute
|
||
|
|
</TH>
|
||
|
|
<TR><TD1 valign="top">INTNUM</TD1><TD2 valign="top">Interval number: The nth sample database interval based on the start
|
||
|
|
time specified in the Create Performance Data (CRTPFRDTA) command.</TD2><TD3 valign="top">PD (5,0)</TD3></TR>
|
||
|
|
<TR><TD1 valign="top">DTETIM</TD1><TD2 valign="top">Interval date (yymmdd) and time (hhmmss): The date and time of the
|
||
|
|
sample interval.</TD2><TD3 valign="top">C (12)</TD3></TR>
|
||
|
|
<TR><TD1 valign="top">INTSEC</TD1><TD2 valign="top">Elapsed interval seconds: The number of seconds since the last sample
|
||
|
|
interval.</TD2><TD3 valign="top">PD (7,0)</TD3></TR>
|
||
|
|
<TR><TD1 valign="top">DTECEN</TD1><TD2 valign="top">Century digit. 0 indicates 19xx, and 1 indicates 20xx.</TD2><TD3 valign="top">C (1)</TD3></TR>
|
||
|
|
<TR><TD1 valign="top">DPTYPE</TD1><TD2 valign="top">Client type. The type of client that is registered to data port services: <ul><li>1 -- Remote independent ASP mirroring.</li>
|
||
|
|
</ul>
|
||
|
|
</TD2><TD3 valign="top">B (4,0)</TD3></TR>
|
||
|
|
<TR><TD1 valign="top">DPNAME</TD1><TD2 valign="top">Client name. The name of the client registered to data port services.
|
||
|
|
This name is unique for a particular client type but might not be unique across
|
||
|
|
all client types. This name is defined as follows by client type: <ul><li>1 -- ASP resource name of remotely mirrored primary independent ASP.</li>
|
||
|
|
</ul>
|
||
|
|
</TD2><TD3 valign="top">C (10)</TD3></TR>
|
||
|
|
<TR><TD1 valign="top">DPIPV</TD1><TD2 valign="top">IP version. This field defines the IP version (4 or 6) for the target
|
||
|
|
IP address.</TD2><TD3 valign="top">B (4,0)</TD3></TR>
|
||
|
|
<TR><TD1 valign="top">DPIPAD</TD1><TD2 valign="top">Target IP address. The IP address of the target system. This record
|
||
|
|
reports statistics for the client's communication on the connection associated
|
||
|
|
with this IP address. An IP version 4 address, which is 4 bytes wide, is right-justified
|
||
|
|
and padded with zeroes.</TD2><TD3 valign="top">H (16)</TD3></TR>
|
||
|
|
<TR><TD1 valign="top">DPIPAS</TD1><TD2 valign="top">Target IP address status. <span>The valid value for this field
|
||
|
|
is 1 or 0.</span> The value of this field is 1 if the target IP address is
|
||
|
|
currently being used for messaging; otherwise, it is 0.</TD2><TD3 valign="top">C (1)</TD3></TR>
|
||
|
|
<TR><TD1 valign="top">DPNID</TD1><TD2 valign="top">Target node ID. The node ID of the target system in the cluster.</TD2><TD3 valign="top">C (8)</TD3></TR>
|
||
|
|
<TR><TD1 valign="top">DPDTA1</TD1><TD2 valign="top">Client data 1. Optional data provided by the client. This data is defined
|
||
|
|
as follows by client type: <ul><li>1 -- ASP number of remotely mirrored primary independent ASP.</li>
|
||
|
|
</ul>
|
||
|
|
</TD2><TD3 valign="top">B (9,0)</TD3></TR>
|
||
|
|
<TR><TD1 valign="top">DPDTA2</TD1><TD2 valign="top">Client data 2. Optional data provided by the client. This data is defined
|
||
|
|
as follows by client type: <ul><li>1 -- Not defined.</li>
|
||
|
|
</ul>
|
||
|
|
</TD2><TD3 valign="top">B (9,0)</TD3></TR>
|
||
|
|
<TR><TD1 valign="top">DPDTA3</TD1><TD2 valign="top">Client data 3. Optional data provided by the client. This data is defined
|
||
|
|
as follows by client type: <ul><li>1 -- Not defined.</li>
|
||
|
|
</ul>
|
||
|
|
</TD2><TD3 valign="top">C (10)</TD3></TR>
|
||
|
|
<TR><TD1 valign="top">DPDTA4</TD1><TD2 valign="top">Client data 4. Optional data provided by the client. This data is defined
|
||
|
|
as follows by client type: <ul><li>1 -- Not defined.</li>
|
||
|
|
</ul>
|
||
|
|
</TD2><TD3 valign="top">C (40)</TD3></TR>
|
||
|
|
<TR><TD1 valign="top">DPASYN</TD1><TD2 valign="top">Asynchronous mode. <span>The valid value for this field is
|
||
|
|
1 or 0.</span> The value of this field is 1 for asynchronous mode; otherwise,
|
||
|
|
this field is 0 for synchronous mode. For asynchronous mode, the client sends
|
||
|
|
a message and receives an ACK back when the message is received but before
|
||
|
|
it is processed by the remote client. For synchronous mode, the client sends
|
||
|
|
a message and receives an ACK back after the message is received and processed
|
||
|
|
by the remote client.</TD2><TD3 valign="top">C (1)</TD3></TR>
|
||
|
|
<TR><TD1 valign="top">DPMS</TD1><TD2 valign="top">Messages sent. The number of messages sent by the client. This value
|
||
|
|
is incremented when the client requests a send; it does not depend on whether
|
||
|
|
the send is successful.</TD2><TD3 valign="top">B (18,0)</TD3></TR>
|
||
|
|
<TR><TD1 valign="top">DPAS</TD1><TD2 valign="top">Acknowledgments sent. The number of acknowledgments (ACKs) sent by
|
||
|
|
the client.</TD2><TD3 valign="top">B (18,0)</TD3></TR>
|
||
|
|
<TR><TD1 valign="top">DPNS</TD1><TD2 valign="top">Negative acknowledgments sent. The number of negative acknowledgments
|
||
|
|
(NACKs) sent by the client.</TD2><TD3 valign="top">B (18,0)</TD3></TR>
|
||
|
|
<TR><TD1 valign="top">DPMR</TD1><TD2 valign="top">Messages received. The number of messages received by the client.</TD2><TD3 valign="top">B (18,0)</TD3></TR>
|
||
|
|
<TR><TD1 valign="top">DPAR</TD1><TD2 valign="top">Acknowledgments received. The number of acknowledgments (ACKs) received
|
||
|
|
by the client.</TD2><TD3 valign="top">B (18,0)</TD3></TR>
|
||
|
|
<TR><TD1 valign="top">DPNR</TD1><TD2 valign="top">Negative acknowledgments received. The number of negative acknowledgments
|
||
|
|
(NACKs) received by the client.</TD2><TD3 valign="top">B (18,0)</TD3></TR>
|
||
|
|
<TR><TD1 valign="top">DPMRO</TD1><TD2 valign="top">Messages retried once. The number of client messages retried only once.
|
||
|
|
The messages counted are those associated with a data port services initiated
|
||
|
|
retry and not a TCP-initiated retry.</TD2><TD3 valign="top">B (18,0)</TD3></TR>
|
||
|
|
<TR><TD1 valign="top">DPMRM</TD1><TD2 valign="top">Messages retried more than once. The number of client messages retried
|
||
|
|
more than once. The messages counted are those associated with data port services
|
||
|
|
initiated retries and not TCP-initiated retries. If a message is retried two
|
||
|
|
or more times, then this value is incremented by 1.</TD2><TD3 valign="top">B (18,0)</TD3></TR>
|
||
|
|
<TR><TD1 valign="top">DPTMR</TD1><TD2 valign="top">Total message retries. The total number of client message retries.
|
||
|
|
The retries counted are data port services initiated retries and not TCP-initiated
|
||
|
|
retries. If a message is retried <em>n</em> times, then this value is incremented
|
||
|
|
by <em>n</em>.</TD2><TD3 valign="top">B (18,0)</TD3></TR>
|
||
|
|
<TR><TD1 valign="top">DPMRR</TD1><TD2 valign="top">Messages rerouted to alternate address. The number of messages rerouted
|
||
|
|
to an alternate IP address because the attempt to transmit the message timed
|
||
|
|
out too many times.</TD2><TD3 valign="top">B (18,0)</TD3></TR>
|
||
|
|
<TR><TD1 valign="top">DPMNA</TD1><TD2 valign="top">Messages not acknowledged. The number of client messages sent that
|
||
|
|
did not receive an ACK or NACK in response.</TD2><TD3 valign="top">B (18,0)</TD3></TR>
|
||
|
|
<TR><TD1 valign="top">DPMBR</TD1><TD2 valign="top">Message bytes received. The number of bytes associated with messages
|
||
|
|
received by the client. This does not include bytes associated with retries
|
||
|
|
or ACK and NACK responses.</TD2><TD3 valign="top">B (18,0)</TD3></TR>
|
||
|
|
<TR><TD1 valign="top">DPMBS</TD1><TD2 valign="top">Message bytes sent. The number of bytes associated with messages sent
|
||
|
|
by the client. This does not include bytes associated with retries or ACK
|
||
|
|
and NACK responses. This value is incremented when the client requests a send;
|
||
|
|
it does not depend on whether the send is successful.</TD2><TD3 valign="top">B (18,0)</TD3></TR>
|
||
|
|
<TR><TD1 valign="top">DPSMS</TD1><TD2 valign="top">Small messages sent. Number of messages of size less than or equal
|
||
|
|
to 4K sent by the client.</TD2><TD3 valign="top">B (18,0)</TD3></TR>
|
||
|
|
<TR><TD1 valign="top">DPMMS</TD1><TD2 valign="top">Medium messages sent. Number of messages of size greater than 4K but
|
||
|
|
less than or equal to 64K sent by the client.</TD2><TD3 valign="top">B (18,0)</TD3></TR>
|
||
|
|
<TR><TD1 valign="top">DPLMS</TD1><TD2 valign="top">Large messages sent. Number of messages of size greater than 64K sent
|
||
|
|
by the client.</TD2><TD3 valign="top">B (18,0)</TD3></TR>
|
||
|
|
<TR><TD1 valign="top">DPSRTT</TD1><TD2 valign="top">Smoothed round trip time in microseconds. Current estimate of the average
|
||
|
|
round trip time up to the time the data was collected (see DTETIM field).
|
||
|
|
This estimate is maintained by data port services. The round trip time is
|
||
|
|
the time it takes for a client message to be sent and acknowledged successfully.</TD2><TD3 valign="top">B (18,0)</TD3></TR>
|
||
|
|
<TR><TD1 valign="top">DPTRTT</TD1><TD2 valign="top">Total round trip time in microseconds. The sum of all of the round
|
||
|
|
trip times. The round trip time is the time it takes for a client message
|
||
|
|
to be sent and acknowledged successfully. Divide this value by round trips
|
||
|
|
to get the average round trip time.</TD2><TD3 valign="top">B (18,0)</TD3></TR>
|
||
|
|
<TR><TD1 valign="top">DPRT</TD1><TD2 valign="top">Round trips. The number of round trips. Divide total round trip time
|
||
|
|
by this value to get average round trip time.</TD2><TD3 valign="top">B (18,0)</TD3></TR>
|
||
|
|
</TABLE>
|