ibm-information-center/dist/eclipse/plugins/i5OS.ic.cl_5.4.0.1/strpfrcol.htm

153 lines
7.6 KiB
HTML

<!doctype html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head><META http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Start Performance Collection (STRPFRCOL)</title>
<link rel="stylesheet" type="text/css" href="../rzahg/ic.css">
</head>
<body bgcolor="white">
<script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<a name="STRPFRCOL.Top_Of_Page"></a>
<h2>Start Performance Collection (STRPFRCOL)</h2>
<table width="100%">
<tr>
<td valign="top" align="left"><b>Where allowed to run: </b>All environments (*ALL)<br>
<b>Threadsafe: </b>No
</td>
<td valign="top" align="right">
<a href="#STRPFRCOL.PARAMETERS.TABLE">Parameters</a><br>
<a href="#STRPFRCOL.COMMAND.EXAMPLES">Examples</a><br>
<a href="#STRPFRCOL.ERROR.MESSAGES">Error messages</a></td>
</tr>
</table>
<div> <a name="STRPFRCOL"></a>
<p>The Start Performance Collection (STRPFRCOL) command starts the system-level collection of performance data by Collection Services. The properties of the system-level collection are controlled by the Collection Services configuration, which can be changed using the Configure Performance Collection (CFGPFRCOL) command. The data included in the system-level collection is determined by the value specified on the Collection profile parameter.
</p>
<p>Performance data collection is conducted by the Collection Services server job (QYPSPFRCOL). If this job is not active, it will be started as a result of this command. If the job is active, any change to the collection profile will take effect immediately and the collection will continue uninterrupted.
</p>
<p>QYPSPFRCOL creates a management collection object (*MGTCOL) to store performance data. Data collected will include both the system-level collection profile categories as well as data collected on behalf of client applications (for example, iSeries Navigator monitors or Performance Collector APIs). All data is stored in the current management collection object. This data may be processed using the Create Performance Data (CRTPFRDTA) command to generate the performance database files.
</p>
<p>Cycling the performance collection will cause the Collection Services server job to create a new management collection object prior to implementing the specified Collection profile. Note: cycling may result in the loss of one interval of data and will also impact any client applications that are using Collection Services.
</p>
</div>
<table width="100%">
<tr><td align="right"><a href="#STRPFRCOL.Top_Of_Page">Top</a></td></tr>
</table>
<hr size="2" width="100%">
<div>
<h3><a name="STRPFRCOL.PARAMETERS.TABLE">Parameters</a></h3>
<table border="1" cellpadding="4" cellspacing="0">
<!-- col1="10" col2="15" col3="30" col4="10" -->
<tr>
<th bgcolor="aqua" valign="bottom" align="left">Keyword</th>
<th bgcolor="aqua" valign="bottom" align="left">Description</th>
<th bgcolor="aqua" valign="bottom" align="left">Choices</th>
<th bgcolor="aqua" valign="bottom" align="left">Notes</th>
</tr>
<tr>
<td valign="top"><a href="#STRPFRCOL.COLPRF"><b>COLPRF</b></a></td>
<td valign="top">Collection profile</td>
<td valign="top"><b><u>*CFG</u></b>, *MINIMUM, *STANDARD, *STANDARDP, *ENHCPCPLN, *CUSTOM</td>
<td valign="top">Optional, Positional 1</td>
</tr>
<tr>
<td valign="top"><a href="#STRPFRCOL.CYCCOL"><b>CYCCOL</b></a></td>
<td valign="top">Cycle collection</td>
<td valign="top"><b><u>*NO</u></b>, *YES</td>
<td valign="top">Optional, Positional 2</td>
</tr>
</table>
<table width="100%">
<tr><td align="right"><a href="#STRPFRCOL.Top_Of_Page">Top</a></td></tr>
</table>
</div>
<div> <a name="STRPFRCOL.COLPRF"></a>
<h3>Default collection profile (COLPRF)</h3>
<p>Specifies the collection profile. This will determine which categories will be included in the system-level collection. Specifying a profile for this parameter will change the default collection profile in the Collection Services configuration. The default collection profile may also be changed using the Configure Performance Collection (CFGPFRCOL) command.
</p>
<dl>
<dt><b><u>*CFG</u></b></dt>
<dd>The collection will use the currently configured value. If the configured value has never been modified, the collection profile will be *STANDARDP.
</dd>
<dt><b>*MINIMUM</b></dt>
<dd>The minimum data collection recommended. Includes the following categories: *SYSBUS, *POOL, *HDWCFG, *SYSCPU, *SYSLVL, *JOBMI, *JOBOS, *DISK, and *IOPBASE.
</dd>
<dt><b>*STANDARD</b></dt>
<dd>The standard profile includes all categories which are typically needed by the Performance Tools for iSeries, with the exception of communications data. It includes all categories in the *MINIMUM profile, as well as the following categories: *POOLTUNE, *SUBSYSTEM, *SNADS, *LCLRSP, *APPN, *SNA, *TCPBASE, *USRTNS, and *LPAR. The category *DOMINO will be included if the product Domino for iSeries has been installed on the system. The category *HTTP will be included if the product IBM HTTP Server for iSeries (powered by Apache) has been installed on the system.
</dd>
<dt><b>*STANDARDP</b></dt>
<dd>The standard plus profile includes all categories which are typically needed by the Performance Tools for iSeries, including communications data. It includes all categories in the *STANDARD profile, as well as the following categories: *IPCS, *CMNBASE, *CMNSTN, *CMNSAP, *TCPIFC, and *DPS.
</dd>
<dt><b>*ENHCPCPLN</b></dt>
<dd>The enhanced capacity planner profile includes all categories in the *STANDARDP profile, with the addition of *INTPEX.
</dd>
<dt><b>*CUSTOM</b></dt>
<dd>The custom profile includes categories as defined by the user. This profile must be defined using the Collection Services function in iSeries Navigator.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#STRPFRCOL.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="STRPFRCOL.CYCCOL"></a>
<h3>Cycle collection (CYCCOL)</h3>
<p>Specifies whether the collection should be cycled. Cycling the collection will cause data to be collected in a new management collection object (*MGTCOL).
</p>
<dl>
<dt><b><u>*NO</u></b></dt>
<dd>Data will continue to be collected in the current collection object.
</dd>
<dt><b>*YES</b></dt>
<dd>Data will be collected in a new collection object.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#STRPFRCOL.Top_Of_Page">Top</a></td></tr>
</table>
<hr size="2" width="100%">
<div><h3><a name="STRPFRCOL.COMMAND.EXAMPLES">Examples</a> </h3>
<p><b>Example 1: Starting the Performance Collection</b>
</p>
<p>
<pre>
STRPFRCOL
</pre>
</p>
<p>This command will cause the Collection Services server job (QYPSPFRCOL) to start the system-level collection of performance data using the currently configured default collection profile.
</p>
<p><b>Example 2: Starting with Collection Profile and Cycle Collection</b>
</p>
<p>
<pre>
STRPFRCOL COLPRF(*MINIMUM) CYCCOL(*YES)
</pre>
</p>
<p>This command will cause the Collection Services server job (QYPSPFRCOL) to cycle and begin collecting performance data in a new management collection object (*MGTCOL) using the *MINIMUM collection profile. Note: this command will also change the configured default collection profile to *MINIMUM.
</p>
</div>
<table width="100%">
<tr><td align="right"><a href="#STRPFRCOL.Top_Of_Page">Top</a></td></tr>
</table>
<hr size="2" width="100%">
<div><h3><a name="STRPFRCOL.ERROR.MESSAGES">Error messages</a> </h3>
<p><b><u>*ESCAPE Messages</u></b>
</p>
<dl>
<dt><b>CPF3CF2</b></dt>
<dd>Error(s) occurred during running of &amp;1 API.
</dd>
<dt><b>CPFB94A</b></dt>
<dd>Collector communications error. Reason code &amp;1.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#STRPFRCOL.Top_Of_Page">Top</a></td></tr>
</table>
</body>
</html>