163 lines
11 KiB
HTML
163 lines
11 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 Report header" />
|
||
|
<meta name="abstract" content="Each report, regardless of the type or section, contains information in the header of the report that identifies characteristics of the data. Look here for descriptions of the header information." />
|
||
|
<meta name="description" content="Each report, regardless of the type or section, contains information in the header of the report that identifies characteristics of the data. Look here for descriptions of the header information." />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzahxreportperftools.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzahxreportcolumns.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzahxtranrptjob.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzahxtranrpttransaction.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzahxtranrpttransition.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzahxlockrpt.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzahxtracereport.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzahxjobintervalreport.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzahxpoolintervalreport.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzahxresourceinterval.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="rzahxreportheader" />
|
||
|
<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 Report header</title>
|
||
|
</head>
|
||
|
<body id="rzahxreportheader"><a name="rzahxreportheader"><!-- --></a>
|
||
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
<h1 class="topictitle1">Performance Report header</h1>
|
||
|
<div><p>Each report, regardless of the type or section, contains information
|
||
|
in the header of the report that identifies characteristics of the data. Look
|
||
|
here for descriptions of the header information.</p>
|
||
|
<div class="section"><dl><dt class="dlterm">Report title</dt>
|
||
|
<dd>Identifies the type of performance report on the first line. The second
|
||
|
line identifies the section of the report.</dd>
|
||
|
<dt class="dlterm">Current date and time</dt>
|
||
|
<dd>Indicates the date and time the report was printed.</dd>
|
||
|
<dt class="dlterm">Report page number</dt>
|
||
|
<dd>Identifies the page of the report.</dd>
|
||
|
<dt class="dlterm">Perf data from <var class="varname">time</var> to <var class="varname">time</var> at <var class="varname">interval</var></dt>
|
||
|
<dd>Indicates the time period over which the data was collected and at what
|
||
|
interval.</dd>
|
||
|
<dt class="dlterm">User-selected report title</dt>
|
||
|
<dd>Indicates the name assigned to the report by a user.</dd>
|
||
|
<dt class="dlterm">Member</dt>
|
||
|
<dd>Indicates the performance data member used in the report. This name corresponds
|
||
|
to the name used on the MBR parameter of the Create Performance data (CRTPFRDTA)
|
||
|
command.</dd>
|
||
|
<dt class="dlterm">Library</dt>
|
||
|
<dd>Identifies the library where the performance data used for a particular
|
||
|
report is located.</dd>
|
||
|
<dt class="dlterm">Model/Serial</dt>
|
||
|
<dd>Indicates the model and serial number of the server on which the performance
|
||
|
data for the report was collected. The serial number can be 10 characters.</dd>
|
||
|
<dt class="dlterm">Main storage size</dt>
|
||
|
<dd>Indicates the size of the main storage on the server on which the performance
|
||
|
data was collected.</dd>
|
||
|
<dt class="dlterm">Started</dt>
|
||
|
<dd>Indicates the date and time Collection Services started collecting performance
|
||
|
data for the report. Depending on whether or not you select specific intervals
|
||
|
or a specific starting time, you could see the following: <ul><li>If you specify no intervals at which to run the report, the start date
|
||
|
and time is the date and time at which the data was collected.</li>
|
||
|
<li>If you specify specific intervals at which to run the report, the start
|
||
|
date and time is the date and time at which the data was collected.<div class="note"><span class="notetitle">Note:</span> For
|
||
|
the System Report only, you should consult the Report Selection Criteria section
|
||
|
to find out which intervals were selected.</div>
|
||
|
</li>
|
||
|
</ul>
|
||
|
</dd>
|
||
|
<dt class="dlterm">Stopped</dt>
|
||
|
<dd>The date and time Collection Services stopped collecting performance data
|
||
|
for this report. Depending on whether or not you select specific intervals
|
||
|
or a specific ending time, you could see the following: <ul><li>If you specify no intervals at which to run the report, the stop date
|
||
|
and time is the date and time at which the data was collected.</li>
|
||
|
<li>If you specify specific intervals at which to run the report, the stop
|
||
|
date and time is the date and time at which the data was collected. <div class="note"><span class="notetitle">Note:</span> For
|
||
|
the System Report only, you should consult the Report Selection Criteria section
|
||
|
to find out which intervals were selected.</div>
|
||
|
</li>
|
||
|
</ul>
|
||
|
</dd>
|
||
|
<dt class="dlterm">System name</dt>
|
||
|
<dd>Indicates the name of the server on which the performance data was collected
|
||
|
for the report.</dd>
|
||
|
<dt class="dlterm">Version/Release level</dt>
|
||
|
<dd><samp class="codeph">x/ x.0</samp> indicates which version and release level of the
|
||
|
operating system the server was running at the time the performance data was
|
||
|
collected.</dd>
|
||
|
<dt class="dlterm">Partition ID</dt>
|
||
|
<dd>Identifies the ID of the partition on which the collection was run. This
|
||
|
change accommodates the logical partition implementation. Here are some of
|
||
|
the values that you might see: <ul><li>If your system is not partitioned (which is the default) or you used Collection
|
||
|
Services to collect and print the performance data for the primary partition
|
||
|
of a logical partition system, this value is 00.</li>
|
||
|
<li>If you collected data with the <span class="cmdname">Start Performance Monitor (STRPFRMON)</span> command
|
||
|
in a previous release, the value for the partition ID is 00.</li>
|
||
|
<li>If you used Collection Services to collect and print the performance data
|
||
|
in any secondary partition of a logical partition system, this value is the
|
||
|
same as the partition ID that is shown on the Work with System Partitions
|
||
|
display under the <span class="cmdname">Start Service Tools (STRSST)</span> command.</li>
|
||
|
</ul>
|
||
|
</dd>
|
||
|
<dt class="dlterm">Feature Code</dt>
|
||
|
<dd>Identifies the Interactive feature code value for the server.</dd>
|
||
|
<dt class="dlterm"> <span class="uicontrol">Int Threshold</span> </dt>
|
||
|
<dd>Indicates the percent of the total system CPU for interactive work that
|
||
|
was used during the collection period. The value is obtained from the QAPMCONF
|
||
|
file (GKEY IT) and reflects the configuration metric obtained when the collection
|
||
|
started. You should be aware that this value may change for each interval
|
||
|
within a collection period due to dynamic changes in logical partition configuration.</dd>
|
||
|
<dt class="dlterm">Virtual Processors</dt>
|
||
|
<dd>The number of virtual processors configured for the partition. The value
|
||
|
is obtained from the QAPMCONF file (GKEY 13)and reflects the configuration
|
||
|
metric obtained when the collection started. You should be aware that this
|
||
|
value may change for each interval within a collection period due to dynamic
|
||
|
changes in logical partition configuration.</dd>
|
||
|
<dt class="dlterm">Processor Units</dt>
|
||
|
<dd>The number of processor units allocated to the partition. The value is
|
||
|
obtained from the QAPMCONF file (GKEY PU) and reflects the configuration metric
|
||
|
obtained when the collection started. You should be aware that this value
|
||
|
may change for each interval within a collection period due to dynamic changes
|
||
|
in logical partition configuration. <p>Processing units are a unit of measure
|
||
|
for shared processing power across one or more virtual processors. One shared
|
||
|
processing unit on one virtual processor accomplishes approximately the same
|
||
|
work as one dedicated processor. One shared processing unit on two virtual
|
||
|
processors accomplishes approximately half the work of two dedicated processors.</p>
|
||
|
</dd>
|
||
|
<dt class="dlterm">Column headings</dt>
|
||
|
<dd>Each report also has several columns that make up the information of the
|
||
|
report. Some are specific to a particular report and others are consistent
|
||
|
between reports. For short descriptions of these columns, see the Performance
|
||
|
Report columns page.</dd>
|
||
|
</dl>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div>
|
||
|
<div class="familylinks">
|
||
|
<div class="parentlink"><strong>Parent topic:</strong> <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>
|
||
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
<div><a href="rzahxreportcolumns.htm" title="Each report includes columns of information. Look here for descriptions of that information.">Performance Report columns</a></div>
|
||
|
<div><a href="rzahxtranrptjob.htm" title="The Job Summary Report Option report provides general job information. Always request this report first.">Transaction Report - Job Summary Report Option</a></div>
|
||
|
<div><a href="rzahxtranrpttransaction.htm" title="The Transaction Report (RPTTYPE(*TNSACT)) option provides detailed information about each transaction that occurred in the job.">Transaction Report - Transaction Report Option</a></div>
|
||
|
<div><a href="rzahxtranrpttransition.htm" title="The Transition Report (RPTTYPE(*TRSIT)) option provides information similar to that of the Transaction Report, but the data (for example, processing unit time, I/O requests) is shown for each job state transition, rather than just the transitions shown when the job is waiting for work station input.">Transaction Report - Transition Report Option</a></div>
|
||
|
<div><a href="rzahxlockrpt.htm" title="There are two sections to a lock report.">Example: Lock Report</a></div>
|
||
|
<div><a href="rzahxtracereport.htm" title="This sample report shows the Job Summary section of the Batch Job Trace Report. This section of the report provides the number of traces, the number of I/O operations, the number of seize and lock conflicts, and the number of state transitions for each batch job.">Example: Batch Job Trace Report</a></div>
|
||
|
<div><a href="rzahxjobintervalreport.htm" title="There are five sections of a Job Interval report.">Example: Job Interval Report</a></div>
|
||
|
<div><a href="rzahxpoolintervalreport.htm" title="There are two sections to the Pool Interval Report.">Example: Pool Interval Report</a></div>
|
||
|
<div><a href="rzahxresourceinterval.htm" title="There are six sections to the Resource interval report.">Example: Resource Interval Report</a></div>
|
||
|
</div>
|
||
|
</div>
|
||
|
</body>
|
||
|
</html>
|