182 lines
14 KiB
HTML
182 lines
14 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="concept" />
|
||
|
<meta name="DC.Title" content="Performance Tools reports" />
|
||
|
<meta name="abstract" content="Performance Tools reports provide information on data that has been collected over time. Use these reports to get additional information about the performance and use of system resources." />
|
||
|
<meta name="description" content="Performance Tools reports provide information on data that has been collected over time. Use these reports to get additional information about the performance and use of system resources." />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzahxperftoolsdesc.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzahxptreportprint.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzahxjobtraceinfo.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzahxjobtraceanalysisum.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzahxjobtraceanalysisio.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzahxreportcolumns.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzahxcollectinfoexample.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzahxptreportprint.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzahxcollectdatacs.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzahxcollectinfoappperf.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="../books/sc415340.pdf" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzahxreportpex.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzahxreportpm400.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="rzahxreportperftools" />
|
||
|
<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 Tools reports</title>
|
||
|
</head>
|
||
|
<body id="rzahxreportperftools"><a name="rzahxreportperftools"><!-- --></a>
|
||
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
<h1 class="topictitle1">Performance Tools reports</h1>
|
||
|
<div><p>Performance Tools reports provide information on data that has
|
||
|
been collected over time. Use these reports to get additional information
|
||
|
about the performance and use of system resources.</p>
|
||
|
<p>The Performance Tools reports provide an easy way for you to look at your
|
||
|
collected data and isolate performance problems. After you have collected
|
||
|
performance data over time, you can print the reports to see how and where
|
||
|
system resources are being used. The reports can direct you to specific application
|
||
|
programs, users, or inefficient workloads that are causing slower overall
|
||
|
response times.</p>
|
||
|
<p>Collection Services provides data for most of the Performance Tools reports
|
||
|
with the exception of the Transaction, Lock, and Trace reports. You must use
|
||
|
the <span class="cmdname">Start Performance Trace (STRPFRTRC)</span> and <span class="cmdname">End
|
||
|
Performance Trace (ENDPFRTRC)</span> commands to collect the trace information
|
||
|
for those three reports.</p>
|
||
|
<p>The following list describes each report, gives a brief overview as to
|
||
|
why you would use a particular report, and links to samples of each report.
|
||
|
In addition, each report is discussed in detail in the Performance Tools book.</p>
|
||
|
|
||
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th colspan="4" valign="top" id="d0e35">Overview of Performance Tools reports</th>
|
||
|
</tr>
|
||
|
<tr><th valign="top" id="d0e38">Report</th>
|
||
|
<th valign="top" id="d0e40">Description</th>
|
||
|
<th valign="top" id="d0e42">What is shown</th>
|
||
|
<th valign="top" id="d0e44">How you use the information</th>
|
||
|
</tr>
|
||
|
</thead>
|
||
|
<tbody><tr><td valign="top" headers="d0e35 d0e38 "><a href="rzahxsysrep.htm">Example: System Report</a></td>
|
||
|
<td valign="top" headers="d0e35 d0e40 ">Uses Collection Services data to provide an overview of how the system
|
||
|
is operating. The report contains summary information on the workload, resource
|
||
|
use, storage pool utilization, disk utilization, and communications. Run and
|
||
|
print this report often to give you a general idea of your system use.</td>
|
||
|
<td valign="top" headers="d0e35 d0e42 ">System workload. The report includes the database capabilities data.</td>
|
||
|
<td valign="top" headers="d0e35 d0e44 ">Workload projection</td>
|
||
|
</tr>
|
||
|
<tr><td valign="top" headers="d0e35 d0e38 "><a href="rzahxcompreport.htm">Example: Component Report</a></td>
|
||
|
<td valign="top" headers="d0e35 d0e40 ">Uses Collection Services data to provide information about the same
|
||
|
components of system performance as a System Report, but at a greater level
|
||
|
of detail. This report helps you find which jobs are consuming high amounts
|
||
|
of system resources, such as CPU, disk, and so on.</td>
|
||
|
<td valign="top" headers="d0e35 d0e42 ">Resource use, communications, system and user jobs. The report includes
|
||
|
the database capabilities data and the Interactive Feature utilization.</td>
|
||
|
<td valign="top" headers="d0e35 d0e44 ">Hardware growth and configuration processing trends</td>
|
||
|
</tr>
|
||
|
<tr><td valign="top" headers="d0e35 d0e38 "><a href="rzahxtranrpt.htm">Example: Transaction Reports</a></td>
|
||
|
<td valign="top" headers="d0e35 d0e40 ">Uses trace data to provide detailed information about the transactions
|
||
|
that occurred during the performance data collection.</td>
|
||
|
<td valign="top" headers="d0e35 d0e42 ">Workload and utilization of CPU, disk, main storage, transaction workload,
|
||
|
object contention</td>
|
||
|
<td valign="top" headers="d0e35 d0e44 ">Workload projection, pool configuration, application design, file contention,
|
||
|
and program use</td>
|
||
|
</tr>
|
||
|
<tr><td valign="top" headers="d0e35 d0e38 "><a href="rzahxlockrpt.htm">Example: Lock Report</a></td>
|
||
|
<td valign="top" headers="d0e35 d0e40 ">Uses trace data to provide information about lock and seize conflicts
|
||
|
during system operation. With this information you can determine if jobs are
|
||
|
being delayed during processing because of unsatisfied lock requests or internal
|
||
|
machine seize conflicts. These conditions are also called waits. If they are
|
||
|
occurring, you can determine which objects the jobs are waiting for and the
|
||
|
length of the wait.</td>
|
||
|
<td valign="top" headers="d0e35 d0e42 ">File, record, or object contention by time; the holding job or object
|
||
|
name; the requesting job or object name</td>
|
||
|
<td valign="top" headers="d0e35 d0e44 ">Problem analysis. Reduction or elimination of object contention.</td>
|
||
|
</tr>
|
||
|
<tr><td valign="top" headers="d0e35 d0e38 "><a href="rzahxtracereport.htm">Example: Batch Job Trace Report</a></td>
|
||
|
<td valign="top" headers="d0e35 d0e40 ">Uses trace data to show the progression of different job types (for
|
||
|
example, batch jobs) traced through time. Resources utilized, exceptions,
|
||
|
and state transitions are reported.</td>
|
||
|
<td valign="top" headers="d0e35 d0e42 ">Job class time-slice end and trace data</td>
|
||
|
<td valign="top" headers="d0e35 d0e44 ">Problem analysis and batch job progress</td>
|
||
|
</tr>
|
||
|
<tr><td valign="top" headers="d0e35 d0e38 "><a href="rzahxjobintervalreport.htm">Example: Job Interval Report</a></td>
|
||
|
<td valign="top" headers="d0e35 d0e40 ">Uses Collection Services data to show information on all or selected
|
||
|
intervals and jobs, including detail and summary information for interactive
|
||
|
jobs and for noninteractive jobs. Because the report can be long, you may
|
||
|
want to limit the output by selecting the intervals and jobs you want to include.</td>
|
||
|
<td valign="top" headers="d0e35 d0e42 ">Jobs by interval</td>
|
||
|
<td valign="top" headers="d0e35 d0e44 ">Job data</td>
|
||
|
</tr>
|
||
|
<tr><td valign="top" headers="d0e35 d0e38 "><a href="rzahxpoolintervalreport.htm">Example: Pool Interval Report</a></td>
|
||
|
<td valign="top" headers="d0e35 d0e40 ">Uses Collection Services data to provide a section on subsystem activity
|
||
|
and a section on pool activity. Data is shown for each sample interval. Because
|
||
|
the report can be long, you may want to limit the output by selecting the
|
||
|
intervals and jobs you want to include.</td>
|
||
|
<td valign="top" headers="d0e35 d0e42 ">Pools by interval</td>
|
||
|
<td valign="top" headers="d0e35 d0e44 ">Pool data</td>
|
||
|
</tr>
|
||
|
<tr><td valign="top" headers="d0e35 d0e38 "><a href="rzahxresourceinterval.htm">Example: Resource Interval Report</a></td>
|
||
|
<td valign="top" headers="d0e35 d0e40 ">Uses Collection Services data to provide resource information on all
|
||
|
or selected intervals. Because the report can be long, you may want to limit
|
||
|
the output by selecting the intervals you want to include.</td>
|
||
|
<td valign="top" headers="d0e35 d0e42 ">Resources by interval</td>
|
||
|
<td valign="top" headers="d0e35 d0e44 ">System resource use</td>
|
||
|
</tr>
|
||
|
</tbody>
|
||
|
</table>
|
||
|
</div>
|
||
|
<p>Performance explorer and Collection Services are separate collecting agents.
|
||
|
Each one produces its own set of database files that contain grouped sets
|
||
|
of collected data. You can run both collections at the same time.</p>
|
||
|
</div>
|
||
|
<div>
|
||
|
<ul class="ullinks">
|
||
|
<li class="ulchildlink"><strong><a href="rzahxptreportprint.htm">Print the performance reports</a></strong><br />
|
||
|
You can print reports using the performance data that you collected. Prior to V5R1, Option 3 (Print performance report) displayed a list of performance members that were located in the QAPMCONF file.</li>
|
||
|
<li class="ulchildlink"><strong><a href="rzahxjobtraceinfo.htm">Example: Job Trace Information report</a></strong><br />
|
||
|
This sample report shows the QPPTTRCD file. The Print Job Trace
|
||
|
(<span class="cmdname">PRTJOBTRC</span>) command generates printer files
|
||
|
QPPTTRCD, QPPTTRC1 and QPPTTRC2.</li>
|
||
|
<li class="ulchildlink"><strong><a href="rzahxjobtraceanalysisum.htm">Example: Job Trace Analysis Summary report</a></strong><br />
|
||
|
This sample report shows the QPPTTRC1 file. The Print Job Trace
|
||
|
(<span class="cmdname">PRTJOBTRC</span>) command generates printer files QPPTTRCD, QPPTTRC1
|
||
|
and QPPTTRC2. The Trace Analysis Summary report (QPPTTRC1) shows the job trace
|
||
|
details by transaction.</li>
|
||
|
<li class="ulchildlink"><strong><a href="rzahxjobtraceanalysisio.htm">Example: Job Trace Analysis I/O Summary report</a></strong><br />
|
||
|
This sample report shows the QPPTTRC2 file. The Print Job Trace
|
||
|
(<span class="cmdname">PRTJOBTRC</span>) command generates printer files QPPTTRCD, QPPTTRC1
|
||
|
and QPPTTRC2. The Trace Analysis I/O Summary report (QPPTTRC2) shows the job
|
||
|
trace details by transaction.</li>
|
||
|
<li class="ulchildlink"><strong><a href="rzahxreportcolumns.htm">Performance Report columns</a></strong><br />
|
||
|
Each report includes columns of information. Look here for descriptions of that information.</li>
|
||
|
</ul>
|
||
|
|
||
|
<div class="familylinks">
|
||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzahxperftoolsdesc.htm" title="The Performance Tools licensed program includes many features to help you gather, analyze, and maintain system performance information. This includes assistance in managing performance over a distributed network, collecting and reporting on both summary and trace data, and capacity planning.">Performance Tools</a></div>
|
||
|
</div>
|
||
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
<div><a href="rzahxptreportprint.htm" title="You can print reports using the performance data that you collected. Prior to V5R1, Option 3 (Print performance report) displayed a list of performance members that were located in the QAPMCONF file.">Print the performance reports</a></div>
|
||
|
<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><a href="rzahxreportpex.htm" title="After you have collected performance data with a performance explorer session, you can view it by running the included reports or by querying the database files directly.">Performance explorer reports</a></div>
|
||
|
<div><a href="rzahxreportpm400.htm" title="The iSeries server can be configured to send Collection Services data directly to IBM with PM iSeries. IBM then generates several reports that you can either view on the Web or have sent directly to you. Activating PM iSeries to automatically generate your reports not only saves you time and resources, but also allows you to plan ahead by forecasting your future growth needs.">PM iSeries reports</a></div>
|
||
|
</div>
|
||
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
<div><a href="rzahxcollectinfoappperf.htm" title="An application might be performing slowly for a variety of reasons. You can use several of the tools included in i5/OS and other licensed programs to help you get more information.">Collect information about an application's performance</a></div>
|
||
|
</div>
|
||
|
<div class="relinfo"><strong>Related information</strong><br />
|
||
|
<div><a href="rzahxcollectinfoexample.htm" title="In this scenario, you have just upgraded or migrated your system and it now appears to be running slower than before. This scenario will help you identify and fix your performance problem.">Scenario: Improve system performance after an upgrade or migration</a></div>
|
||
|
<div><a href="../books/sc415340.pdf" target="_blank">Performance Tools PDF</a></div>
|
||
|
</div>
|
||
|
</div>
|
||
|
</body>
|
||
|
</html>
|