274 lines
24 KiB
HTML
274 lines
24 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="Collection Services" />
|
||
|
|
<meta name="abstract" content="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.)" />
|
||
|
|
<meta name="description" content="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.)" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxapsparent.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxcollservscenario.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahx3b3.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahx3b4.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxcollservuserdef.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahx3b5.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxcollservusertran.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxcollectdatapart.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxcollservwait.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxcollservdisk.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxcollectarmperformancedata.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxqapmdisk.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxqapmdps.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxqapmiopd.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxqapmjobmi.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxqapmjobs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxqapmjsum.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxqapmlpar.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxqapmsys.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxqapmsyscpu.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxqapmsystem.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxplanbench.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxplanperfstrategy.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxsetup.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxtrack.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxcollectinfosysperf.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahx3b13.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxdisplayperfdata.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxebusnet.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxqapmtcp.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxqapmtcpifc.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/strpfrcol.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzaj2/rzaj2overview.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../apis/perfmgmt.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxplangrow1pmsetup1a.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxperfdatafiles1.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahx3b6.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahx3b4.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxmonparent.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxmoncon.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxgrphparent.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxgrphcon.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxgrphcfg.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxplangrow1pmmgg9.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxreportpm400.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxperftoolsdesc.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxperftoolsconcepts.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxreportperftools.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="rzahxcollectdatacs" />
|
||
|
|
<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>Collection Services</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzahxcollectdatacs"><a name="rzahxcollectdatacs"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Collection Services</h1>
|
||
|
|
<div><p>Use Collection Services to collect performance data for later analysis
|
||
|
|
by the Performance Tools for <span class="keyword">iSeries™</span> licensed
|
||
|
|
program or other performance report applications, <span class="keyword">iSeries Navigator</span> 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.)</p>
|
||
|
|
<p>Collection Services collects data that identifies the relative amount of
|
||
|
|
system resource used by different areas of your system. Use Collection Services
|
||
|
|
to:</p>
|
||
|
|
<ul><li>Easily manage your collection objects</li>
|
||
|
|
<li>Collect performance data continuously and automatically with minimal system
|
||
|
|
overhead</li>
|
||
|
|
<li>Control what data is collected and how the data is used</li>
|
||
|
|
<li>Move performance data between releases without converting the data</li>
|
||
|
|
<li>Create performance data files that are used by Performance Tools</li>
|
||
|
|
<li>Integrate your own programs to collect user-defined performance data into
|
||
|
|
Collection Services.</li>
|
||
|
|
</ul>
|
||
|
|
<div class="section"><h4 class="sectiontitle">How Collection Services works</h4><p>Collection Services
|
||
|
|
replaces the <span class="keyword">i5/OS™</span> performance
|
||
|
|
monitor, which was called by the <span class="cmdname">Start Performance Monitor (STRPFRMON)</span> command.
|
||
|
|
The Performance Monitor (STRPFRMON command) has not been available since V4R5.
|
||
|
|
When you used the <span class="keyword">i5/OS</span> performance
|
||
|
|
monitor, your data was collected into as many as 30 database files.</p>
|
||
|
|
<p>Collection
|
||
|
|
Services capabilities introduce a new process of collecting performance data.
|
||
|
|
Collection Services stores your data for each collection in a single collection
|
||
|
|
object, from which you can create as many different sets of database files
|
||
|
|
as you need. This means a lower system overhead when collecting performance
|
||
|
|
data. Even if you elect to create the database files during collection, you
|
||
|
|
still experience a performance advantage over the <span class="keyword">i5/OS</span> performance
|
||
|
|
monitor because Collection Services uses a lower priority (50) batch job to
|
||
|
|
update these files. The reduction in collection overhead makes it practical
|
||
|
|
to collect performance data in greater detail and at shorter intervals on
|
||
|
|
a continuous basis. Collection Services enables you to establish a network-wide
|
||
|
|
system policy for collecting and retaining performance data and to implement
|
||
|
|
that policy automatically. For as long as you retain the management collection
|
||
|
|
objects, if the need arises, you have the capability to look back and analyze
|
||
|
|
performance-related events down to the level of detail that you collected.</p>
|
||
|
|
<br /><img src="rzahx502.gif" alt="Overview of Collections Services" /><br /><p>Collection Services allows you to gather performance data with
|
||
|
|
little or no observable impact on system performance. You can use <span class="keyword">iSeries Navigator</span> to configure Collection Services
|
||
|
|
to collect the data you want as frequently as you want to gather it. A collection
|
||
|
|
object, *MGTCOL, serves as an efficient storage medium to hold large quantities
|
||
|
|
of performance data. Once you have configured and started Collection Services,
|
||
|
|
performance data is continuously collected. When you need to work with performance
|
||
|
|
data, you can copy the data you need into a set of performance database files.</p>
|
||
|
|
<p>The
|
||
|
|
figure above provides an overview of the following Collection Services elements:</p>
|
||
|
|
<dl><dt class="dlterm">User interfaces</dt>
|
||
|
|
<dd>Several methods exist that allow you to access the different elements
|
||
|
|
of Collection Services. For example, you can use CL commands, APIs, and the<span class="keyword">iSeries Navigator</span> interface.</dd>
|
||
|
|
<dt class="dlterm">General properties</dt>
|
||
|
|
<dd>General properties define how a collection should be accomplished and
|
||
|
|
they control automatic collection attributes.</dd>
|
||
|
|
<dt class="dlterm">Data categories</dt>
|
||
|
|
<dd>Data categories identify the types of data to collect. You can configure
|
||
|
|
categories independently to control what data is collected and how often the
|
||
|
|
data is collected.</dd>
|
||
|
|
<dt class="dlterm">Collection profiles</dt>
|
||
|
|
<dd>Collection profiles provide a means to save and activate a particular
|
||
|
|
category configuration.</dd>
|
||
|
|
<dt class="dlterm">Performance collector</dt>
|
||
|
|
<dd>The performance collector uses the general properties and category information
|
||
|
|
to control the collection of performance data. You can start and stop the
|
||
|
|
performance collector, or configure it to run automatically.</dd>
|
||
|
|
<dt class="dlterm">Collection Object</dt>
|
||
|
|
<dd>The collection object, *MGTCOL, serves as an efficient storage medium
|
||
|
|
for large quantities of performance data.</dd>
|
||
|
|
<dt class="dlterm"><span class="cmdname">Create Performance Data (CRTPRFDTA)</span> command</dt>
|
||
|
|
<dd>The CRTPFRDTA command processes data that is stored in the management
|
||
|
|
collection object and generates the performance database files.</dd>
|
||
|
|
<dt class="dlterm">Performance database</dt>
|
||
|
|
<dd>The database files store the data that is processed by the CRTPFRDTA command.
|
||
|
|
The files can be divided into these categories: Performance data files that
|
||
|
|
contain time interval data, configuration data files, trace data files.</dd>
|
||
|
|
</dl>
|
||
|
|
<p>For an illustration of how Collection Services and system
|
||
|
|
and job monitors work together on the system, refer to System and Job monitor
|
||
|
|
interaction with Collection Services.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">How to start Collection Services</h4><p>You can start Collection
|
||
|
|
Services by using any of the following methods. However, the information in
|
||
|
|
the Performance topic focuses on <span class="keyword">iSeries Navigator</span> methods.</p>
|
||
|
|
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" id="d0e233">Starting method</th>
|
||
|
|
<th valign="top" id="d0e235">Description</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td valign="top" headers="d0e233 "><span class="cmdname">Start Performance Collection (STRPFRCOL)</span> command</td>
|
||
|
|
<td valign="top" headers="d0e235 ">Use the STRPFRCOL command to start the system-level collection of performance
|
||
|
|
data by Collection Services.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e233 "><span class="keyword">iSeries Navigator</span></td>
|
||
|
|
<td valign="top" headers="d0e235 ">Perform a variety of Collection Services tasks by using <span class="keyword">iSeries Navigator</span>.
|
||
|
|
The table that follows below lists these tasks and links you to information
|
||
|
|
about how to complete them.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e233 ">Performance Management APIs</td>
|
||
|
|
<td valign="top" headers="d0e235 ">Use Performance Management APIs to start, customize, end, and cycle
|
||
|
|
collections. In addition, you can use the APIs to work with the management
|
||
|
|
collection objects or define your own transactions.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e233 ">Traditional menu options</td>
|
||
|
|
<td valign="top" headers="d0e235 ">Type <span class="uicontrol">GO PERFORM</span> in the character-based interface
|
||
|
|
and select option 2 (Collect performance data) from the Performance Tools
|
||
|
|
main menu. For additional information, go to the Performance Tools book.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e233 ">PM <span class="keyword">iSeries</span></td>
|
||
|
|
<td valign="top" headers="d0e235 ">PM <span class="keyword">iSeries</span> automates
|
||
|
|
the start of Collection Services and then creates the database files during
|
||
|
|
collection.</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzahxcollservscenario.htm">System and job monitor interaction with Collection Services</a></strong><br />
|
||
|
|
Collection services is both a valuable tool for performance analysis as a stand alone application and as a utility used by other applications for the collection of performance data.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzahx3b3.htm">Create database files from Collection Services data</a></strong><br />
|
||
|
|
Collection Services places the data you collected into management collection objects.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzahx3b4.htm">Customize data collections</a></strong><br />
|
||
|
|
When you use Collection Services to collect performance data, you control what data is collected and how often it is collected.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzahxcollservuserdef.htm">User-defined categories in Collection Services</a></strong><br />
|
||
|
|
The user-defined categories function in Collection Services enables applications to integrate performance data collection into Collection Services.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzahx3b5.htm">Manage collection objects</a></strong><br />
|
||
|
|
When you use Collection Services to collect performance data, each collection is stored in a single object.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzahxcollservusertran.htm">User-defined transactions</a></strong><br />
|
||
|
|
Collection Services and performance explorer collect performance data that you define in your applications.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzahxcollectdatapart.htm">Collecting performance data across partitions</a></strong><br />
|
||
|
|
IBM<sup>®</sup> Performance
|
||
|
|
Management for <img src="eserver.gif" alt="eServer" /> <span class="keyword">iSeries</span> (PM eServer™ <span class="keyword">iSeries</span>) automatically triggers Collection
|
||
|
|
Services to gather nonproprietary performance and capacity data from your
|
||
|
|
server and then sends the data to IBM<sup>®</sup> for analysis.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzahxcollservwait.htm">Find wait statistics for a job, task, or thread</a></strong><br />
|
||
|
|
During the running of a job, task, or thread, conditions arise that cause that process to wait (for example, while the system resolves a lock or hold on a required object).</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzahxcollservdisk.htm">Understanding disk consumption by Collection Services</a></strong><br />
|
||
|
|
The amount of disk resource Collection Services consumes varies greatly depending on the settings that you use.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzahxcollectarmperformancedata.htm">Collect ARM performance data</a></strong><br />
|
||
|
|
You can use collection services to collect Application Response Measurement (ARM) performance data.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<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="rzahxplanbench.htm" title="Setting good system benchmarks will give you performance data for a properly tuned system. These performance benchmarks from both before and after system changes provide important information for both troubleshooting and planning.">Set system benchmarks</a></div>
|
||
|
|
<div><a href="rzahxtrack.htm" title="Tracking your system performance over time allows you to plan for your system's growth and ensures that you have data to help isolate and identify the cause of performance problems. Learn which applications to use and how to routinely collect performance data.">Track performance</a></div>
|
||
|
|
<div><a href="rzahx3b13.htm" title="Deciding when to dump trace data is a significant decision because the dump affects system performance.">Dump trace data</a></div>
|
||
|
|
<div><a href="../rzaj2/rzaj2overview.htm">iSeries Navigator</a></div>
|
||
|
|
<div><a href="rzahxperfdatafiles1.htm" title="You can generate database files from the collection objects maintained by Collection Services. Use this topic to find the names, descriptions and attributes of these database files.">Performance data files</a></div>
|
||
|
|
<div><a href="rzahx3b6.htm" title="When you review and analyze performance data, the actual local time of the collection can be significant.">Time zone considerations for Collection Services</a></div>
|
||
|
|
<div><a href="rzahxmoncon.htm" title="Monitors can display real-time performance data. Additionally, they can continually monitor your system in order to run a selected command when a specified threshold is reached. Learn how monitors work, what they can monitor, and how they can respond to a given performance situation.">Monitor concepts</a></div>
|
||
|
|
<div><a href="rzahxgrphparent.htm" title="Graph history provides a graphical display of performance data collected by Collection Services over a specified period of time.">Graph history</a></div>
|
||
|
|
<div><a href="rzahxgrphcon.htm" title="Contains a description of the available options for managing and displaying records of performance data.">Graph history concepts</a></div>
|
||
|
|
<div><a href="rzahxplangrow1pmmgg9.htm" title="PM iSeries uses Collection Services to gather performance data. Learn how PM iSeries and Collection Services work together to provide the data you need.">Data collection considerations for PM iSeries</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><a href="rzahxperftoolsconcepts.htm" title="Describes a variety of tools to help you collect and analyze performance information. Find detailed information about exactly which tools perform which functions and how they work.">Performance Tools concepts</a></div>
|
||
|
|
<div><a href="rzahxreportperftools.htm" title="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.">Performance Tools reports</a></div>
|
||
|
|
<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>
|
||
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
||
|
|
<div><a href="rzahxplangrow1pmsetup1a.htm" title="PM iSeries ships with i5/OS, but you must activate it to use its collecting capabilities.">Activate PM iSeries</a></div>
|
||
|
|
<div><a href="rzahx3b4.htm" title="When you use Collection Services to collect performance data, you control what data is collected and how often it is collected.">Customize data collections</a></div>
|
||
|
|
<div><a href="rzahxgrphcfg.htm" title="This topic contains step-by-step instructions to view graph history through iSeries Navigator.">Use graph history</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="rzahxqapmdps.htm" title="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.">Performance data files: QAPMDPS</a></div>
|
||
|
|
<div><a href="rzahxplanperfstrategy.htm" title="Different business needs require different performance management strategies. Here are three basic business models and their suggested performance management strategies.">Select a performance management strategy</a></div>
|
||
|
|
<div><a href="rzahxsetup.htm" title="iSeries servers include powerful applications for managing system performance. However, they must be properly configured in order to meet the specific needs of your unique business environment. Learn how to configure applications to routinely collect, monitor, and analyze performance data.">Set up your environment to manage performance</a></div>
|
||
|
|
<div><a href="rzahxcollectinfosysperf.htm" title="Collection Services regularly collects information about system performance. Often, analyzing performance data begins with this information.">Collect system performance data</a></div>
|
||
|
|
<div><a href="rzahxdisplayperfdata.htm" title="After you have collected performance data, learn how to display the data using the most appropriate tool for your purposes.">Display performance data</a></div>
|
||
|
|
<div><a href="rzahxebusnet.htm" title="The network design, hardware resources and traffic pressure often have a significant effect on the performance of e-business applications. You can use this topic for information on how to optimize network performance, and tune server communication resources.">Network performance</a></div>
|
||
|
|
<div><a href="rzahxqapmtcp.htm" title="This database file contains system-wide TCP/IP data.">Performance data files: QAPMTCP</a></div>
|
||
|
|
<div><a href="rzahxqapmtcpifc.htm" title="This database file contains TCP/IP data related to individual TCP/IP interfaces.">Performance data files: QAPMTCPIFC</a></div>
|
||
|
|
<div><a href="../cl/strpfrcol.htm">Start Performance Collection (STRPFRCOL) command</a></div>
|
||
|
|
<div><a href="../apis/perfmgmt.htm">Performance Management APIs</a></div>
|
||
|
|
<div><a href="rzahxmonparent.htm" title="Monitors display current information about the performance of your systems. Additionally, you can use them to carry out predefined actions when a specific event occurs. You can use the system, message, job, file, and B2B transaction monitors to display and monitor information about your systems. The system and job monitors use the performance data collected by Collection Services.">iSeries Navigator monitors</a></div>
|
||
|
|
<div><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="relinfo"><strong>Related information</strong><br />
|
||
|
|
<div><a href="rzahxqapmdisk.htm">Performance data files: QAPMDISK</a></div>
|
||
|
|
<div><a href="rzahxqapmiopd.htm">Performance data files: QAPMIOPD</a></div>
|
||
|
|
<div><a href="rzahxqapmjobmi.htm">Performance data files: QAPMJOBMI</a></div>
|
||
|
|
<div><a href="rzahxqapmjobs.htm">Performance data files: QAPMJOBS and QAPMJOBL</a></div>
|
||
|
|
<div><a href="rzahxqapmjsum.htm">Performance data files: QAPMJSUM</a></div>
|
||
|
|
<div><a href="rzahxqapmlpar.htm">Performance data files: QAPMLPAR</a></div>
|
||
|
|
<div><a href="rzahxqapmsys.htm">Performance data files: QAPMSYS and QAPMSYSL</a></div>
|
||
|
|
<div><a href="rzahxqapmsyscpu.htm">Performance data files: QAPMSYSCPU</a></div>
|
||
|
|
<div><a href="rzahxqapmsystem.htm">Performance data files: QAPMSYSTEM</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|