115 lines
8.2 KiB
HTML
115 lines
8.2 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="task" />
|
||
|
|
<meta name="DC.Title" content="Configure performance explorer" />
|
||
|
|
<meta name="abstract" content="To collect detailed trace information, you need to tailor performance explorer to work optimally with the application process from which the trace is being taken." />
|
||
|
|
<meta name="description" content="To collect detailed trace information, you need to tailor performance explorer to work optimally with the application process from which the trace is being taken." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxpexparent.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxpexend.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxpexcon.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxpexconpexdef.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/addpexftr.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/strpex.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/prtpexrpt.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxpexcon.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="rzahxpexcfg" />
|
||
|
|
<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>Configure performance explorer</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzahxpexcfg"><a name="rzahxpexcfg"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Configure performance explorer</h1>
|
||
|
|
<div><p>To collect detailed trace information, you need to tailor performance
|
||
|
|
explorer to work optimally with the application process from which the trace
|
||
|
|
is being taken.</p>
|
||
|
|
<div class="section">To configure performance explorer, follow these steps:</div>
|
||
|
|
<ol><li class="stepexpand"><span>Create a session definition that informs the <span class="keyword">iSeries™</span> server
|
||
|
|
which performance data you want to collect. On the Add Performance Explorer
|
||
|
|
Definition (ADDPEXDFN) display, specify the collection type and a name for
|
||
|
|
the definition. This definition is stored as a database member by that name
|
||
|
|
in the QAPEXDFN file in library QUSRSYS. The name that you specify is used
|
||
|
|
on the <span class="cmdname">Start Performance Explorer (STRPEX)</span> command.</span></li>
|
||
|
|
<li class="stepexpand"><span>Add a filter (<span class="cmdname">Add PEX Filter (ADDPEXFTR)</span> command).
|
||
|
|
A performance explorer filter identifies the performance data that is to be
|
||
|
|
collected during a performance explorer session, and is meant to limit the
|
||
|
|
amount of data collected by specifying a compare value for specific events.</span></li>
|
||
|
|
<li class="stepexpand"><span>Start collecting data (<span class="cmdname">Start Performance Explorer (STRPEX)</span> command).
|
||
|
|
A job may be in more than one performance explorer collection if the *PMCO
|
||
|
|
event is not being collected. If the *PMCO event is being collected, then
|
||
|
|
a job can be in more than one collection only if all the collections have
|
||
|
|
the same interval specification (ADDPEXDFN INTERVAL() parameter). <span><img src="./delta.gif" alt="Start of change" />You
|
||
|
|
can specify a definition and optional filter on the <span class="cmdname">STRPEX</span> command.<img src="./deltaend.gif" alt="End of change" /></span></span></li>
|
||
|
|
<li class="stepexpand"><span>Run your command, program, or workload for data that you want to
|
||
|
|
analyze.</span></li>
|
||
|
|
<li class="stepexpand"><span>Stop collecting the data and save it to database files for analysis.
|
||
|
|
Use the <span class="cmdname">End Performance Explorer (ENDPEX)</span> command to stop
|
||
|
|
the collection.</span></li>
|
||
|
|
<li class="stepexpand"><span>Analyze the performance data. The <span class="cmdname">Print Performance Explorer
|
||
|
|
Report (PRTPEXRPT)</span> command, included in the Performance Tools licensed
|
||
|
|
program, provides unique reports for each type of data (statistical, profile,
|
||
|
|
trace profile, or trace). </span> <div class="p"><img src="./delta.gif" alt="Start of change" />The following are other
|
||
|
|
options for analysis:<ul><li>Write your own queries for the set of database files.</li>
|
||
|
|
<li>Use iDoctor for <span class="keyword">iSeries</span>.
|
||
|
|
iDoctor is a set of software performance analysis tools and associated services
|
||
|
|
that extend your ability to evaluate the health of your system by gathering
|
||
|
|
detailed information and providing automated, graphical analysis of this data. </li>
|
||
|
|
<li>Use the IBM<sup>®</sup> Performance
|
||
|
|
Trace Data Visualizer for <span class="keyword">iSeries</span> (PTDV).
|
||
|
|
PTDV is a Java™ application that you can use for performance analysis
|
||
|
|
of applications. PTDV works with the Performance Explorer to allow you to
|
||
|
|
view program flows and get details such as CPU time, wall clock time, number
|
||
|
|
of cycles, and number of instructions, summarized by trace, job, thread, and
|
||
|
|
procedures. </li>
|
||
|
|
</ul>
|
||
|
|
<img src="./deltaend.gif" alt="End of change" /></div>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand"><img src="./delta.gif" alt="Start of change" /><span>To end the performance explorer session,
|
||
|
|
use the End Performance Explorer (ENDPEX) command.</span><img src="./deltaend.gif" alt="End of change" /></li>
|
||
|
|
</ol>
|
||
|
|
<div class="section"><p>All of the performance explorer commands can be accessed with one
|
||
|
|
of the following methods:</p>
|
||
|
|
<ul><li>The command interface. Type the commands from the command line. All the
|
||
|
|
commands are part of the <span class="keyword">i5/OS™</span> operating
|
||
|
|
system, except the <span class="cmdname">Print Performance Explorer Report (PRTPEXRPT)</span> command.</li>
|
||
|
|
<li>The Performance Tools menu options.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzahxpexend.htm">Ending performance explorer</a></strong><br />
|
||
|
|
To end the performance explorer session, use the <span class="cmdname">End Performance
|
||
|
|
Explorer (ENDPEX)</span> command.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzahxpexparent.htm" title="Collects more detailed information about a specific application, program or system resource, and provides detailed insight into a specific performance problem. This includes the capability both to perform several types and levels of traces and to run detailed reports.">Performance explorer</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzahxpexcon.htm" title="Performance explorer works by collecting detailed information about a specified system process or resource. This topic explains how performance explorer works, and how best to use it.">Performance explorer concepts</a></div>
|
||
|
|
<div><a href="rzahxpexconpexdef.htm" title="The parameters and conditions that determine what data performance explorer collects and how it collects it are configured and stored using performance explorer definitions. This topic explains how to use these definitions and provides a sample illustrating a simple definition.">Performance explorer definitions</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="../cl/addpexftr.htm">Add PEX filter (ADDPEXFTR) command</a></div>
|
||
|
|
<div><a href="../cl/strpex.htm">Start Performance Explorer (STRPEX) command</a></div>
|
||
|
|
<div><a href="../cl/prtpexrpt.htm">Print Performance Explorer Report (PRTPEXRPT) command</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|