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

394 lines
22 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: QAPMMIOP" />
<meta name="abstract" content="This database file includes multifunction IOP file entries and lists the fields in the multifunction IOP file." />
<meta name="description" content="This database file includes multifunction IOP file entries and lists the fields in the multifunction IOP 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="rzahxqapmmiop" />
<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: QAPMMIOP</title>
</head>
<body id="rzahxqapmmiop"><a name="rzahxqapmmiop"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Performance data files: QAPMMIOP</h1>
<div><p>This database file includes multifunction IOP file entries and
lists the fields in the multifunction IOP file.</p>
<div class="section"><p> </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='rzahxqapmmiop.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="d0e25">Field Name</th>
<th valign="top" width="50%" id="d0e27">Description</th>
<th valign="top" width="25%" id="d0e29">Attribute</th>
</tr>
</thead>
<tbody><tr><td valign="top" width="25%" headers="d0e25 ">INTNUM</td>
<td valign="top" width="50%" headers="d0e27 ">Interval number: The nth sample database interval based on the start
time specified in the <span class="cmdname">Create Performance Data (CRTPFRDTA)</span> command.</td>
<td valign="top" width="25%" headers="d0e29 ">PD (5,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">DTETIM</td>
<td valign="top" width="50%" headers="d0e27 ">Interval date (yymmdd) and time (hhmmss): The date and time of the
sample interval.</td>
<td valign="top" width="25%" headers="d0e29 ">C (12)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">INTSEC</td>
<td valign="top" width="50%" headers="d0e27 ">Elapsed interval seconds: The number of seconds since the last sample
interval.</td>
<td valign="top" width="25%" headers="d0e29 ">PD (7,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">IOPRN</td>
<td valign="top" width="50%" headers="d0e27 ">IOP resource name.</td>
<td valign="top" width="25%" headers="d0e29 ">C(10)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MIIOP</td>
<td valign="top" width="50%" headers="d0e27 ">Reserved</td>
<td valign="top" width="25%" headers="d0e29 ">C (1)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MITYPE</td>
<td valign="top" width="50%" headers="d0e27 ">IOP type.</td>
<td valign="top" width="25%" headers="d0e29 ">C (4)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MIPRCU</td>
<td valign="top" width="50%" headers="d0e27 ">Processor utilization: The number of fixed-time intervals that this
multifunction IOP spent in the idle state.</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MIRAMU</td>
<td valign="top" width="50%" headers="d0e27 ">Available local storage (in bytes): The number of bytes of free local
storage in the IOP. The free local storage will probably be non-contiguous
because of fragmentation.</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MITPKT</td>
<td valign="top" width="50%" headers="d0e27 ">Total packets transferred.</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MIKBYO</td>
<td valign="top" width="50%" headers="d0e27 ">Total KB transmitted from an IOP to the system across the bus.</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MIKBYI</td>
<td valign="top" width="50%" headers="d0e27 ">Total KB transmitted to the IOP from the system across the bus.</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MIOPSR</td>
<td valign="top" width="50%" headers="d0e27 ">OPSTART bus unit message received from another bus unit using normal
flow.</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MIOPSS</td>
<td valign="top" width="50%" headers="d0e27 ">OPSTART bus unit message received from another bus unit using reverse
flow method 2 (always 0).</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MISGLR</td>
<td valign="top" width="50%" headers="d0e27 ">Signals received.</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MIOPST</td>
<td valign="top" width="50%" headers="d0e27 ">OPSTARTs sent.</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MISLGS</td>
<td valign="top" width="50%" headers="d0e27 ">Signals sent.</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MIRSTQ</td>
<td valign="top" width="50%" headers="d0e27 ">Restart queues sent.</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MIRQDO</td>
<td valign="top" width="50%" headers="d0e27 ">DMA requests sent for output of data: The number of requests the IOP
sends to the system for data to be sent from the IOP to the system across
the bus.</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MIRQDI</td>
<td valign="top" width="50%" headers="d0e27 ">DMA requests sent for input of data: The number of requests the IOP
sends to the system for data to be sent to the IOP from the system across
the bus.</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MIBNAR</td>
<td valign="top" width="50%" headers="d0e27 ">Occurrences of BNA received.</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MIIDLC</td>
<td valign="top" width="50%" headers="d0e27 ">Idle loop count <a href="#rzahxqapmmiop__qapmmiopnote">(see notes)</a>:
The number of times the primary IOP processor ran an idle loop. This is done
when the IOP has no work to perform. This count is used with the idle loop
time to calculate the primary IOP processor utilization in seconds.</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MIIDLT</td>
<td valign="top" width="50%" headers="d0e27 ">Idle loop time <a href="#rzahxqapmmiop__qapmmiopnote">(see notes)</a>:
the time (in hundredths of microseconds) for the primary IOP processor to
run the idle loop once. The value reported could be a multiple of the actual
idle loop time. In that case, the value reported for the idle loop count is
reduced by the same multiple so that the calculated IOP processor utilization
is correct</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MISYSF</td>
<td valign="top" width="50%" headers="d0e27 ">IOP system function time: Total processing unit time (in milliseconds)
used by the IOP for basic system function that is running in the primary IOP
processor.</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MIDISK</td>
<td valign="top" width="50%" headers="d0e27 ">Disk time: Total processing unit time (in milliseconds) used by disk
tasks that are running in the primary IOP processor.</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MICOMM</td>
<td valign="top" width="50%" headers="d0e27 ">Total communications time: Total processing unit time (in milliseconds)
used by all the communications protocol tasks that are running in the primary
IOP processor.</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MISDLC</td>
<td valign="top" width="50%" headers="d0e27 ">SDLC communications time: Total processing unit time (in milliseconds)
used by SDLC communications tasks that are running in the primary IOP processor.</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MIASYN</td>
<td valign="top" width="50%" headers="d0e27 ">ASYNC communications time: Total processing unit time (in milliseconds)
used by asynchronous communications tasks that are running in the primary
IOP processor.</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MIBSC</td>
<td valign="top" width="50%" headers="d0e27 ">BSC communications time: Total processing unit time (in milliseconds)
used by BSC communications tasks that are running in the primary IOP processor.</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MIX25L</td>
<td valign="top" width="50%" headers="d0e27 ">X.25 LLC communications time: Total processing unit time (in milliseconds)
used by X.25 LLC communications tasks that are running in the primary IOP
processor.</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MIX25P</td>
<td valign="top" width="50%" headers="d0e27 ">X.25 PLC communications time: Total processing unit time (in milliseconds)
used by X.25 packet layer communications (PLC) tasks that are running in the
primary IOP processor.</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MIX25D</td>
<td valign="top" width="50%" headers="d0e27 ">X.25 DLC communications time: Total processing unit time (in milliseconds)
used by X.25 data link control (DLC) and Point-to-Point Protocol (PPP) communications
tasks that are running in the primary IOP processor.</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MILAN</td>
<td valign="top" width="50%" headers="d0e27 ">LAN communications time: Total processing unit time (in milliseconds)
used by token-ring network, Ethernet, frame relay, fiber distributed data
interface (FDDI), and asynchronous transfer mode (ATM) communications tasks.
This includes processing time due to token-ring and Ethernet LAN emulation.</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MISDLD</td>
<td valign="top" width="50%" headers="d0e27 ">SDLC short-hold mode time: Total processing unit time (in milliseconds)
used by SDLC short-hold mode tasks that are running in the primary IOP processor.</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MIRV02</td>
<td valign="top" width="50%" headers="d0e27 ">ISDN communications time: Total processing unit time (in milliseconds)
used by ISDN LAPD, LAPE, and PMI communications tasks that are running in
the primary IOP processor.</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MIRV03</td>
<td valign="top" width="50%" headers="d0e27 ">ISDN communications time: Total processing unit time (in milliseconds)
used by ISDN Q.931 communications tasks that are running in the primary IOP
processor.</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MISP</td>
<td valign="top" width="50%" headers="d0e27 ">Service processor time: Total processing unit time (in milliseconds)
used by the service processor function that is running in the primary IOP
processor.</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MIF1ID</td>
<td valign="top" width="50%" headers="d0e27 ">Subfunction 1 ID: The identifier for additional functions that may
be running in the primary IOP processor.</td>
<td valign="top" width="25%" headers="d0e29 ">C (2)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MIF1TM</td>
<td valign="top" width="50%" headers="d0e27 ">Subfunction 1 time: Total processing unit time (in milliseconds) used
by the IOP function that is running in the primary IOP processor</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MIF2ID</td>
<td valign="top" width="50%" headers="d0e27 ">Subfunction 2 ID: The identifier for additional functions that may
be running in the primary IOP processor.</td>
<td valign="top" width="25%" headers="d0e29 ">C (2)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MIF2TM</td>
<td valign="top" width="50%" headers="d0e27 ">Subfunction 2 time: Total processing unit time (in milliseconds) used
by the IOP function that is running in the primary IOP processor</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MIF3ID</td>
<td valign="top" width="50%" headers="d0e27 ">Subfunction 3 ID: The identifier for additional functions that may
be running in the primary IOP processor.</td>
<td valign="top" width="25%" headers="d0e29 ">C (2)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MIF3TM</td>
<td valign="top" width="50%" headers="d0e27 ">Subfunction 3 time: Total processing unit time (in milliseconds) used
by the IOP function that is running in the primary IOP processor.</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MIF4ID</td>
<td valign="top" width="50%" headers="d0e27 ">Subfunction 4 ID: The identifier for additional functions that may
be running in the primary IOP processor.</td>
<td valign="top" width="25%" headers="d0e29 ">C(2)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MIF4TM</td>
<td valign="top" width="50%" headers="d0e27 ">Subfunction 4 time: Total processing unit time (in milliseconds) used
by the IOP function that is running in the primary IOP processor.</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MIF5ID</td>
<td valign="top" width="50%" headers="d0e27 ">Subfunction 5 ID: The identifier for additional functions that are
running in the primary IOP processor.</td>
<td valign="top" width="25%" headers="d0e29 ">C(2)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MIF5TM</td>
<td valign="top" width="50%" headers="d0e27 ">Subfunction 5 time in milliseconds used by the IOP function that is
running in the primary IOP processor.</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MITWNX</td>
<td valign="top" width="50%" headers="d0e27 ">Total processing unit time (in milliseconds) used by workstation and
local twinaxial tasks that are running in the primary IOP processor.</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MICPU2</td>
<td valign="top" width="50%" headers="d0e27 ">Processor 2 utilization: The utilization (in milliseconds) of the second
IOP processor that handles specialized function. This field applies to <span class="keyword">Integrated xSeries<sup>®</sup> Server</span> (excluding I/O adapter versions)
and is zero for other IOPs. Collection Services will not report values for <span class="keyword">Integrated xSeries Server</span>.</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MIADP</td>
<td valign="top" width="50%" headers="d0e27 ">Reserved.</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MIOTH</td>
<td valign="top" width="50%" headers="d0e27 ">Other function time: Total processing unit time (in milliseconds) used
by other IOP functions that are running in the primary IOP processor. Other
functions include those that cannot be reported in the subfunction 1-5 ID
fields because all of the subfunction 1-5 ID fields are in use.</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MIINT</td>
<td valign="top" width="50%" headers="d0e27 ">Interrupt level time: Total processing unit time (in milliseconds)
used by interrupt level processing that is running in the primary IOP processor.
This does not include interrupt level processing time that can be associated
with a particular task.</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
<tr><td valign="top" width="25%" headers="d0e25 ">MIRA</td>
<td valign="top" width="50%" headers="d0e27 ">Remote access time: Total processing unit time (in milliseconds) used
by the remote access tasks that are running in the primary IOP processor.</td>
<td valign="top" width="25%" headers="d0e29 ">PD (11,0)</td>
</tr>
</tbody>
</table>
</div>
<div class="note" id="rzahxqapmmiop__qapmmiopnote"><a name="rzahxqapmmiop__qapmmiopnote"><!-- --></a><span class="notetitle">Notes:</span> The idle loop
count and time are used to calculate the multifunction IOP utilization as
follows:<ol><li>Convert the product of the idle loop count times the idle loop time from
hundredths of microseconds to seconds. Subtract this from the interval time,
and divide the results by the interval time. For example: <blockquote>IOP utilization
= (INTSEC - (MIIDLE * MIIDLT)/10**8) / INTSEC</blockquote>
</li>
<li>The performance monitor reports I/O processor (IOP) statistics different
beginning with Version 3 Release 7. Therefore, performance statistics for
IOPs introduced in Version 3 Release 7 or later releases are reported in the
QAPMMIOP file. Performance statistics are reported in the QAPMMIOP file even
if the IOP supports only one of the three IOP functions (communications, disk,
or local workstation). Performance statistics for IOPs that were introduced
before Version 3 Release 7 will continue to be reported in the appropriate
IOP file (QAPMCIOP, QAPMDIOP, QAPMLIOP, and QAPMMIOP).</li>
<li>The function 1 - 5 identifiers are for additional functions that may be
running in the primary IOP. Each function identifier has an associated function
time value. The function identifier may have the following value:
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><tbody><tr><td valign="top" width="16.666666666666664%">Value</td>
<td valign="top" width="83.33333333333334%">Description</td>
</tr>
<tr><td valign="top" width="16.666666666666664%">00</td>
<td valign="top" width="83.33333333333334%">No time value supplied.</td>
</tr>
<tr><td valign="top" width="16.666666666666664%">11</td>
<td valign="top" width="83.33333333333334%"><span class="keyword">Integrated xSeries Server</span> pipe task (<span class="keyword">Integrated xSeries Server</span> was previously known as file
server I/O processor and FSIOP)</td>
</tr>
<tr><td valign="top" width="16.666666666666664%">20</td>
<td valign="top" width="83.33333333333334%">Storage subsystem task</td>
</tr>
<tr><td valign="top" width="16.666666666666664%">22</td>
<td valign="top" width="83.33333333333334%">Tape task</td>
</tr>
<tr><td valign="top" width="16.666666666666664%">23</td>
<td valign="top" width="83.33333333333334%">Diskette task</td>
</tr>
<tr><td valign="top" width="16.666666666666664%">24</td>
<td valign="top" width="83.33333333333334%">Optical task</td>
</tr>
<tr><td valign="top" width="16.666666666666664%">30</td>
<td valign="top" width="83.33333333333334%">Communications subsystem task</td>
</tr>
<tr><td valign="top" width="16.666666666666664%">42</td>
<td valign="top" width="83.33333333333334%">Localtalk task</td>
</tr>
<tr><td valign="top" width="16.666666666666664%">43</td>
<td valign="top" width="83.33333333333334%">Wireless task</td>
</tr>
<tr><td valign="top" width="16.666666666666664%">60</td>
<td valign="top" width="83.33333333333334%">Cryptography task</td>
</tr>
</tbody>
</table>
</div>
</li>
</ol>
</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>
</body>
</html>