ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzahx_5.4.0.1/rzahxqapmdps.htm

276 lines
15 KiB
HTML
Raw Normal View History

2024-04-02 14:02:31 +00:00
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en-us" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="security" content="public" />
<meta name="Robots" content="index,follow" />
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta name="DC.Type" content="reference" />
<meta name="DC.Title" content="Performance data files: QAPMDPS" />
<meta name="abstract" content="This database file contains data port services performance data. Data port services is Licensed Internal Code (LIC) that supports the transfer of large volumes of data between a source system and one of N specified (switchable) target systems in an iSeries cluster." />
<meta name="description" content="This database file contains data port services performance data. Data port services is Licensed Internal Code (LIC) that supports the transfer of large volumes of data between a source system and one of N specified (switchable) target systems in an iSeries cluster." />
<meta name="DC.Relation" scheme="URI" content="rzahxapsparent.htm" />
<meta name="DC.Relation" scheme="URI" content="rzahxcollectdatacs.htm" />
<meta name="DC.Relation" scheme="URI" content="rzahxcatfilerelation.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rzahxqapmdps" />
<meta name="DC.Language" content="en-us" />
<!-- All rights reserved. Licensed Materials Property of IBM -->
<!-- US Government Users Restricted Rights -->
<!-- Use, duplication or disclosure restricted by -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
<link rel="stylesheet" type="text/css" href="./ic.css" />
<title>Performance data files: QAPMDPS</title>
</head>
<body id="rzahxqapmdps"><a name="rzahxqapmdps"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Performance data files: QAPMDPS</h1>
<div><p>This database file contains data port services performance data.
Data port services is Licensed Internal Code (LIC) that supports the transfer
of large volumes of data between a source system and one of <em>N</em> specified
(switchable) target systems in an <span class="keyword">iSeries™</span> cluster.</p>
<div class="section"><p>Data port services, such as remote independent ASP mirroring,
is used by LIC clients. There is one record per IP address per
client per collection interval. </p>
<div class="tablenoborder"><!-- Link to dynamic table -->
<SCRIPT language="Javascript" type="text/javascript" src="../rzahg/iccommon.js"></SCRIPT>
<SCRIPT language="Javascript" type="text/javascript">
//<![CDATA[
//Do not split up the following string. Keep it on one line.
var textA = "<p>To easily compare and sort the data in this table, use the <a href='rzahxqapmdps.xml'>interactive table<\/a>.<\/p>";
if (isIE5) {
document.writeln(textA);
}
//]]>
</SCRIPT>
<!-- End of link to dynamic table --><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" id="d0e32">Field Name</th>
<th valign="top" id="d0e34">Description</th>
<th valign="top" id="d0e36">Attribute</th>
</tr>
</thead>
<tbody><tr><td valign="top" headers="d0e32 ">INTNUM</td>
<td valign="top" headers="d0e34 ">Interval number: The nth sample database interval based on the start
time specified in the Create Performance Data (CRTPFRDTA) command.</td>
<td valign="top" headers="d0e36 ">PD (5,0)</td>
</tr>
<tr><td valign="top" headers="d0e32 ">DTETIM</td>
<td valign="top" headers="d0e34 ">Interval date (yymmdd) and time (hhmmss): The date and time of the
sample interval.</td>
<td valign="top" headers="d0e36 ">C (12)</td>
</tr>
<tr><td valign="top" headers="d0e32 ">INTSEC</td>
<td valign="top" headers="d0e34 ">Elapsed interval seconds: The number of seconds since the last sample
interval.</td>
<td valign="top" headers="d0e36 ">PD (7,0)</td>
</tr>
<tr><td valign="top" headers="d0e32 ">DTECEN</td>
<td valign="top" headers="d0e34 ">Century digit. 0 indicates 19xx, and 1 indicates 20xx.</td>
<td valign="top" headers="d0e36 ">C (1)</td>
</tr>
<tr><td valign="top" headers="d0e32 ">DPTYPE</td>
<td valign="top" headers="d0e34 ">Client type. The type of client that is registered to data port services: <ul><li>1 -- Remote independent ASP mirroring.</li>
</ul>
</td>
<td valign="top" headers="d0e36 ">B (4,0)</td>
</tr>
<tr><td valign="top" headers="d0e32 ">DPNAME</td>
<td valign="top" headers="d0e34 ">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>
</td>
<td valign="top" headers="d0e36 ">C (10)</td>
</tr>
<tr><td valign="top" headers="d0e32 ">DPIPV</td>
<td valign="top" headers="d0e34 ">IP version. This field defines the IP version (4 or 6) for the target
IP address.</td>
<td valign="top" headers="d0e36 ">B (4,0)</td>
</tr>
<tr><td valign="top" headers="d0e32 ">DPIPAD</td>
<td valign="top" headers="d0e34 ">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.</td>
<td valign="top" headers="d0e36 ">H (16)</td>
</tr>
<tr><td valign="top" headers="d0e32 ">DPIPAS</td>
<td valign="top" headers="d0e34 ">Target IP address status. <span><img src="./delta.gif" alt="Start of change" />The valid value for this field
is 1 or 0.<img src="./deltaend.gif" alt="End of change" /></span> The value of this field is 1 if the target IP address is
currently being used for messaging; otherwise, it is 0.</td>
<td valign="top" headers="d0e36 ">C (1)</td>
</tr>
<tr><td valign="top" headers="d0e32 ">DPNID</td>
<td valign="top" headers="d0e34 ">Target node ID. The node ID of the target system in the cluster.</td>
<td valign="top" headers="d0e36 ">C (8)</td>
</tr>
<tr><td valign="top" headers="d0e32 ">DPDTA1</td>
<td valign="top" headers="d0e34 ">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>
</td>
<td valign="top" headers="d0e36 ">B (9,0)</td>
</tr>
<tr><td valign="top" headers="d0e32 ">DPDTA2</td>
<td valign="top" headers="d0e34 ">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>
</td>
<td valign="top" headers="d0e36 ">B (9,0)</td>
</tr>
<tr><td valign="top" headers="d0e32 ">DPDTA3</td>
<td valign="top" headers="d0e34 ">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>
</td>
<td valign="top" headers="d0e36 ">C (10)</td>
</tr>
<tr><td valign="top" headers="d0e32 ">DPDTA4</td>
<td valign="top" headers="d0e34 ">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>
</td>
<td valign="top" headers="d0e36 ">C (40)</td>
</tr>
<tr><td valign="top" headers="d0e32 ">DPASYN</td>
<td valign="top" headers="d0e34 ">Asynchronous mode. <span><img src="./delta.gif" alt="Start of change" />The valid value for this field is
1 or 0.<img src="./deltaend.gif" alt="End of change" /></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.</td>
<td valign="top" headers="d0e36 ">C (1)</td>
</tr>
<tr><td valign="top" headers="d0e32 ">DPMS</td>
<td valign="top" headers="d0e34 ">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.</td>
<td valign="top" headers="d0e36 ">B (18,0)</td>
</tr>
<tr><td valign="top" headers="d0e32 ">DPAS</td>
<td valign="top" headers="d0e34 ">Acknowledgments sent. The number of acknowledgments (ACKs) sent by
the client.</td>
<td valign="top" headers="d0e36 ">B (18,0)</td>
</tr>
<tr><td valign="top" headers="d0e32 ">DPNS</td>
<td valign="top" headers="d0e34 ">Negative acknowledgments sent. The number of negative acknowledgments
(NACKs) sent by the client.</td>
<td valign="top" headers="d0e36 ">B (18,0)</td>
</tr>
<tr><td valign="top" headers="d0e32 ">DPMR</td>
<td valign="top" headers="d0e34 ">Messages received. The number of messages received by the client.</td>
<td valign="top" headers="d0e36 ">B (18,0)</td>
</tr>
<tr><td valign="top" headers="d0e32 ">DPAR</td>
<td valign="top" headers="d0e34 ">Acknowledgments received. The number of acknowledgments (ACKs) received
by the client.</td>
<td valign="top" headers="d0e36 ">B (18,0)</td>
</tr>
<tr><td valign="top" headers="d0e32 ">DPNR</td>
<td valign="top" headers="d0e34 ">Negative acknowledgments received. The number of negative acknowledgments
(NACKs) received by the client.</td>
<td valign="top" headers="d0e36 ">B (18,0)</td>
</tr>
<tr><td valign="top" headers="d0e32 ">DPMRO</td>
<td valign="top" headers="d0e34 ">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.</td>
<td valign="top" headers="d0e36 ">B (18,0)</td>
</tr>
<tr><td valign="top" headers="d0e32 ">DPMRM</td>
<td valign="top" headers="d0e34 ">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.</td>
<td valign="top" headers="d0e36 ">B (18,0)</td>
</tr>
<tr><td valign="top" headers="d0e32 ">DPTMR</td>
<td valign="top" headers="d0e34 ">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>.</td>
<td valign="top" headers="d0e36 ">B (18,0)</td>
</tr>
<tr><td valign="top" headers="d0e32 ">DPMRR</td>
<td valign="top" headers="d0e34 ">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.</td>
<td valign="top" headers="d0e36 ">B (18,0)</td>
</tr>
<tr><td valign="top" headers="d0e32 ">DPMNA</td>
<td valign="top" headers="d0e34 ">Messages not acknowledged. The number of client messages sent that
did not receive an ACK or NACK in response.</td>
<td valign="top" headers="d0e36 ">B (18,0)</td>
</tr>
<tr><td valign="top" headers="d0e32 ">DPMBR</td>
<td valign="top" headers="d0e34 ">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.</td>
<td valign="top" headers="d0e36 ">B (18,0)</td>
</tr>
<tr><td valign="top" headers="d0e32 ">DPMBS</td>
<td valign="top" headers="d0e34 ">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.</td>
<td valign="top" headers="d0e36 ">B (18,0)</td>
</tr>
<tr><td valign="top" headers="d0e32 ">DPSMS</td>
<td valign="top" headers="d0e34 ">Small messages sent. Number of messages of size less than or equal
to 4K sent by the client.</td>
<td valign="top" headers="d0e36 ">B (18,0)</td>
</tr>
<tr><td valign="top" headers="d0e32 ">DPMMS</td>
<td valign="top" headers="d0e34 ">Medium messages sent. Number of messages of size greater than 4K but
less than or equal to 64K sent by the client.</td>
<td valign="top" headers="d0e36 ">B (18,0)</td>
</tr>
<tr><td valign="top" headers="d0e32 ">DPLMS</td>
<td valign="top" headers="d0e34 ">Large messages sent. Number of messages of size greater than 64K sent
by the client.</td>
<td valign="top" headers="d0e36 ">B (18,0)</td>
</tr>
<tr><td valign="top" headers="d0e32 ">DPSRTT</td>
<td valign="top" headers="d0e34 ">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.</td>
<td valign="top" headers="d0e36 ">B (18,0)</td>
</tr>
<tr><td valign="top" headers="d0e32 ">DPTRTT</td>
<td valign="top" headers="d0e34 ">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.</td>
<td valign="top" headers="d0e36 ">B (18,0)</td>
</tr>
<tr><td valign="top" headers="d0e32 ">DPRT</td>
<td valign="top" headers="d0e34 ">Round trips. The number of round trips. Divide total round trip time
by this value to get average round trip time.</td>
<td valign="top" headers="d0e36 ">B (18,0)</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzahxapsparent.htm" title="Managing performance on iSeries systems requires the use of a variety of specialized applications. Each of these applications offers a specific insight into system performance. This topic explains several applications and the intended use of each application.">Applications for performance management</a></div>
</div>
<div class="relconcepts"><strong>Related concepts</strong><br />
<div><a href="rzahxcollectdatacs.htm" title="Use Collection Services to collect performance data for later analysis by the Performance Tools for iSeries licensed program or other performance report applications, iSeries Navigator monitors, and the graph history function. (If you prefer viewing real-time performance data, system monitors provide an easy-to-use graphical interface for monitoring system performance.)">Collection Services</a></div>
</div>
<div class="relref"><strong>Related reference</strong><br />
<div><a href="rzahxcatfilerelation.htm" title="When you collect performance data using Collection Services, the data is stored in a management collection (*MGTCOL) object.">Performance data files: Collection Services system category and file relationships</a></div>
</div>
</div>
</body>
</html>