103 lines
6.1 KiB
HTML
103 lines
6.1 KiB
HTML
|
<?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: QAPMARMTRT" />
|
||
|
|
<meta name="abstract" content="This database file contains information about Application Response Measurement (ARM) transaction types that are reported in the QAPMUSRTNS file." />
|
||
|
|
<meta name="description" content="This database file contains information about Application Response Measurement (ARM) transaction types that are reported in the QAPMUSRTNS file." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxapsparent.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="rzahxqapmarmtrt" />
|
||
|
|
<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: QAPMARMTRT</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzahxqapmarmtrt"><a name="rzahxqapmarmtrt"><!-- --></a>
|
||
|
|
<img src="./delta.gif" alt="Start of change" /><!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Performance data files: QAPMARMTRT</h1>
|
||
|
|
<div><p>This database file contains information about Application Response
|
||
|
|
Measurement (ARM) transaction types that are reported in the QAPMUSRTNS file.</p>
|
||
|
|
<div class="section"><p>This optional secondary file is created only when the system collects
|
||
|
|
performance data for ARM transactions. The QAPMARMTRT file contains one record
|
||
|
|
for each ARM transaction type that is known to the system. </p>
|
||
|
|
<p>Applications
|
||
|
|
use ARM APIs to provide information about the progress of application-level
|
||
|
|
transactions. If ARM transactions are enabled on a system, performance data
|
||
|
|
for the ARM transactions from ARM applications and middleware is reported
|
||
|
|
in the QAPMUSRTNS file. </p>
|
||
|
|
<p>You can identify the ARM transaction type by
|
||
|
|
a combination of the ARM application name and the ARM application group name.</p>
|
||
|
|
<p>The
|
||
|
|
ARM transaction type name has a prefix of <span class="q">"QARM"</span> followed by a 16-character
|
||
|
|
representation of an 8-byte internal ARM transaction type ID.</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='rzahxqapmarmtrt.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" width="25%" id="d0e31">Field Name</th>
|
||
|
|
<th valign="top" width="50%" id="d0e33">Description</th>
|
||
|
|
<th valign="top" width="25%" id="d0e35">Attribute</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td valign="top" width="25%" headers="d0e31 ">ATTYP</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e33 ">ARM transaction type.</td>
|
||
|
|
<td valign="top" width="25%" headers="d0e35 ">C (20)</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="25%" headers="d0e31 ">ATANAME</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e33 ">ARM application name.<div class="note"><span class="notetitle">Note:</span> This field is in Unicode.</div>
|
||
|
|
</td>
|
||
|
|
<td valign="top" width="25%" headers="d0e35 ">G (127)</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="25%" headers="d0e31 ">ATAGNAME</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e33 ">ARM application group name.<div class="note"><span class="notetitle">Note:</span> This field is in Unicode.</div>
|
||
|
|
</td>
|
||
|
|
<td valign="top" width="25%" headers="d0e35 ">G (255)</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td colspan="3" valign="top" headers="d0e31 d0e33 d0e35 "><div class="note"><span class="notetitle">Note:</span> <ol><li>The QAPMUSRTNS file contains specific data for the first 15 transaction
|
||
|
|
types for each job being reported. The rest of the data is combined in the
|
||
|
|
*OTHER transaction type. However, the QAPMARMTRT file contains records for
|
||
|
|
all ARM transaction types that are known to the system.</li>
|
||
|
|
<li>The ARM APIs are shipped in a disabled state. For information on how to
|
||
|
|
enable ARM APIs on a system, see <a href="../icbase/ewlminfo/eicaaenablearm.htm" target="_blank">Enable ARM on IBM-instrumented applications</a>.</li>
|
||
|
|
<li>Different ARM-instrumented applications and middleware products might
|
||
|
|
require specific configuration steps to enable the ARM instrumentation.</li>
|
||
|
|
<li>ARM transaction data is reported only for applications which call the
|
||
|
|
ARM API implementation that is shipped with the operating system.</li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
</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>
|
||
|
|
<img src="./deltaend.gif" alt="End of change" /></body>
|
||
|
|
</html>
|