2737 lines
158 KiB
HTML
2737 lines
158 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 columns" />
|
||
|
|
<meta name="abstract" content="Each report includes columns of information. Look here for descriptions of that information." />
|
||
|
|
<meta name="description" content="Each report includes columns of information. Look here for descriptions of that information." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxreportperftools.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxsysrep.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxreportheader.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxcompreport.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="rzahxreportcolumns" />
|
||
|
|
<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 columns</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzahxreportcolumns"><a name="rzahxreportcolumns"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Performance Report columns</h1>
|
||
|
|
<div><p>Each report includes columns of information. Look here for descriptions
|
||
|
|
of that information.</p>
|
||
|
|
<div class="section"><dl><dt class="dlterm">>8.0</dt>
|
||
|
|
<dd>(Component) The number of times the response time was greater than 8 seconds.</dd>
|
||
|
|
<dt class="dlterm">%Write Cache Overruns</dt>
|
||
|
|
<dd>(Component) Percent of Write Cache Overruns during the collection interval.</dd>
|
||
|
|
<dt class="dlterm">---------- (pgmname)</dt>
|
||
|
|
<dd>(Transaction) The transaction totals record. For example, ---------- QUYLIST,.
|
||
|
|
This report line occurs each time the job has an active-to-wait transaction.
|
||
|
|
Totals are created for Rsp* (response time), <var class="varname">CPU Secs</var>,
|
||
|
|
and I/O counts for the transaction.</dd>
|
||
|
|
<dt class="dlterm">A-I Wait /Tns</dt>
|
||
|
|
<dd>(Transaction) The average time, in seconds, of active-to-ineligible wait
|
||
|
|
time per transaction. If this value is high, it may be because the time-slice
|
||
|
|
value is set too low for many of the interactive jobs. Consider increasing
|
||
|
|
the time slice-value.</dd>
|
||
|
|
<dt class="dlterm">Aborts Recd</dt>
|
||
|
|
<dd>(Resource Interval) The number of frames received that contained HDLC
|
||
|
|
abort indicators. This indicates that the remote equipment ended frames before
|
||
|
|
they were complete.</dd>
|
||
|
|
<dt class="dlterm">Act Jobs</dt>
|
||
|
|
<dd>(Job Interval) The number of selected jobs (interactive or noninteractive,
|
||
|
|
depending on the report section) that were active during the interval.</dd>
|
||
|
|
<dt class="dlterm">Act Level</dt>
|
||
|
|
<dd>(Component) Initial pool activity level.</dd>
|
||
|
|
<dt class="dlterm">Act Lvl</dt>
|
||
|
|
<dd>(System, Pool Interval) Activity level. For the Pool Activity section
|
||
|
|
of the Pool Interval Report, the activity level of the pool during the interval.
|
||
|
|
For the Storage Pool Utilization section of the System Report, the activity
|
||
|
|
level at the time of the first sample interval.</dd>
|
||
|
|
<dt class="dlterm">Act-Inel</dt>
|
||
|
|
<dd>(System, Component) Average number of active-to-ineligible job state transitions
|
||
|
|
per minute.</dd>
|
||
|
|
<dt class="dlterm">Act-Wait</dt>
|
||
|
|
<dd>(System, Component) Number of transitions per minute from active state
|
||
|
|
to wait state by processes assigned to this pool.</dd>
|
||
|
|
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />ACTIVE<img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />(Job Trace) The time the job was processing. <img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm">Active Devices</dt>
|
||
|
|
<dd>(System) Average number of active devices on the line.</dd>
|
||
|
|
<dt class="dlterm">Active display stations (local or remote)</dt>
|
||
|
|
<dd>(System) The number of local or remote display stations entering transactions
|
||
|
|
during the measurement period.</dd>
|
||
|
|
<dt class="dlterm">Active Jobs</dt>
|
||
|
|
<dd>(Transaction) The number of interactive jobs that were active during the
|
||
|
|
interval.</dd>
|
||
|
|
<dt class="dlterm">Active Jobs Per Interval</dt>
|
||
|
|
<dd>(System) Average number of jobs of this type that were active per sample
|
||
|
|
interval.</dd>
|
||
|
|
<dt class="dlterm">Active K/T /Tns</dt>
|
||
|
|
<dd>(Transaction) An average think time and keying time (or the delay time
|
||
|
|
between the end of one transaction and the start of the next transaction),
|
||
|
|
in seconds, for the active work stations (described under Est of AWS). Active
|
||
|
|
K/T /TNS delay time differs from Key/Think /TNS delay time in that any delay
|
||
|
|
time greater than 600 seconds has been rounded to 600 seconds. This technique
|
||
|
|
is used to reduce the effect of very casual users (those who may do intermittent
|
||
|
|
work or leave their work stations for long periods of time) on the estimate
|
||
|
|
of active work stations.</dd>
|
||
|
|
<dt class="dlterm">Active Wrk Stn</dt>
|
||
|
|
<dd>(Resource Interval) The number of work stations with activity.</dd>
|
||
|
|
<dt class="dlterm">Active/Rsp</dt>
|
||
|
|
<dd>(Transaction) The time the job spends (either waiting or active) during
|
||
|
|
transaction processing, while it holds an activity level.</dd>
|
||
|
|
<dt class="dlterm">Activity level</dt>
|
||
|
|
<dd>(System) The sum of activity levels for all interactive pools that had
|
||
|
|
interactive job activity running in them.</dd>
|
||
|
|
<dt class="dlterm">Activity Level Time</dt>
|
||
|
|
<dd>(Transaction) A breakdown of the transaction time spent <var class="varname">ACTIVE</var>,
|
||
|
|
waiting on a <var class="varname">SHORT WAIT</var>, and waiting on a <var class="varname">SEIZE/CFT</var> (seize
|
||
|
|
conflict). The <var class="varname">SHORT WAIT</var> and <var class="varname">SEIZE CFT</var> time
|
||
|
|
are included under <var class="varname">ACTIVITY LEVEL TIME</var>, because the activity-level
|
||
|
|
slot is not given up during these times. Note that the seize conflict time
|
||
|
|
is included in the active time, not added to it to get transaction/response
|
||
|
|
time, as is the case for waiting time.</dd>
|
||
|
|
<dt class="dlterm">Arith Ovrflw</dt>
|
||
|
|
<dd>(Component, Job Interval) The number of arithmetic overflow exceptions
|
||
|
|
that occurred for the selected interactive jobs during the interval.</dd>
|
||
|
|
<dt class="dlterm">ASP ID</dt>
|
||
|
|
<dd>(System, Resource Interval) Auxiliary storage pool identifier.</dd>
|
||
|
|
<dt class="dlterm">ASP Rsc Name</dt>
|
||
|
|
<dd>(System, Resource) Identifies the ASP resource name to which the disk
|
||
|
|
unit was allocated at collection time. </dd>
|
||
|
|
<dt class="dlterm">Async</dt>
|
||
|
|
<dd>(System, Component, Transaction, Job Interval) The number of asynchronous
|
||
|
|
disk I/O operations started by the selected interactive jobs during the interval.
|
||
|
|
The job that starts the I/O operation may continue processing without having
|
||
|
|
to wait for the I/O operation to complete. The I/O operation is completed
|
||
|
|
by a background system test.</dd>
|
||
|
|
<dt class="dlterm">Async DIO /Tns</dt>
|
||
|
|
<dd>(Transaction) The sum of the averages of the asynchronous DB READ, DB
|
||
|
|
WRITE, NDB READ, and NDB WRITE requests (the average number of asynchronous
|
||
|
|
I/O requests per transaction for the job).</dd>
|
||
|
|
<dt class="dlterm">Async Disk I/O</dt>
|
||
|
|
<dd>(System, Component, Transaction) Number of asynchronous disk input/output
|
||
|
|
operations per transaction.</dd>
|
||
|
|
<dt class="dlterm">Async Disk I/O per Second</dt>
|
||
|
|
<dd>(Component) Average asynchronous disk I/O operations per second.</dd>
|
||
|
|
<dt class="dlterm">Async Disk I/O Requests</dt>
|
||
|
|
<dd>(Transaction) The total number of asynchronous disk I/O requests for the
|
||
|
|
given combination of priority, job type, and pool.</dd>
|
||
|
|
<dt class="dlterm">Async I/O /Sec</dt>
|
||
|
|
<dd>(Job Interval) The average number of asynchronous disk I/O operations
|
||
|
|
started per second by the job during the interval. This is calculated by dividing
|
||
|
|
the asynchronous disk I/O count by the elapsed time.</dd>
|
||
|
|
<dt class="dlterm">Async I/O Per Second</dt>
|
||
|
|
<dd>(Job Interval) The average number of asynchronous disk I/O operations
|
||
|
|
started per second by the selected noninteractive jobs during the interval.</dd>
|
||
|
|
<dt class="dlterm">Async Max</dt>
|
||
|
|
<dd>(Transaction) Listed under Average DIO/Transaction, the maximum number
|
||
|
|
of asynchronous DBR, NDBR, and WRT I/O requests encountered for any single
|
||
|
|
transaction by that job. If the job is not an interactive or autostart job
|
||
|
|
type, the total disk I/O for the job is listed here.</dd>
|
||
|
|
<dt class="dlterm">Async Sum</dt>
|
||
|
|
<dd>(Transaction) Listed under Average DIO/Transaction, the sum of the averages
|
||
|
|
of the asynchronous DBR, NDBR, and WRT requests (the average number of asynchronous
|
||
|
|
I/O requests per transaction for the job).</dd>
|
||
|
|
<dt class="dlterm">Asynchronous DBR</dt>
|
||
|
|
<dd>(System, Job Interval, Pool Interval) The average number of asynchronous
|
||
|
|
database read operations on the disk per transaction for the job during the
|
||
|
|
intervals. This is calculated by dividing the asynchronous database read count
|
||
|
|
by the transactions processed. This field is not printed if the jobs in the
|
||
|
|
system did not process any transactions. For the Resource Utilization section
|
||
|
|
of the System Report, it is the number of asynchronous database read operations
|
||
|
|
per second. <div class="note"><span class="notetitle">Note:</span> The asynchronous I/O operations are performed by system
|
||
|
|
asynchronous I/O tasks.</div>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Asynchronous DBW</dt>
|
||
|
|
<dd>(System, Job Interval) The average number of asynchronous database write
|
||
|
|
operations on the disk per transaction for the selected jobs during the interval.
|
||
|
|
This is calculated by dividing the asynchronous database write count by the
|
||
|
|
transactions processed. This field is not printed if the jobs in the system
|
||
|
|
did not process any transactions. For the Resource Utilization section of
|
||
|
|
the System Report, it is the number of asynchronous database read operations
|
||
|
|
per second. <div class="note"><span class="notetitle">Note:</span> The asynchronous I/O operations are performed by system
|
||
|
|
asynchronous I/O tasks.</div>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Asynchronous disk I/O per transaction</dt>
|
||
|
|
<dd>(System) The average number of asynchronous physical disk I/O operations
|
||
|
|
per interactive transaction.</dd>
|
||
|
|
<dt class="dlterm">Asynchronous NDBR</dt>
|
||
|
|
<dd>(System, Job Interval, Pool Interval) The average number of asynchronous
|
||
|
|
nondatabase read operations per transaction for the jobs in the system during
|
||
|
|
the interval. This is calculated from the asynchronous nondatabase read count
|
||
|
|
divided by the transactions processed. This field is not printed if the jobs
|
||
|
|
in the system did not process any transactions. For the Resource Utilization
|
||
|
|
section of the System Report, it is the asynchronous nondatabase read operations
|
||
|
|
per second. <div class="note"><span class="notetitle">Note:</span> The asynchronous I/O operations are performed by system
|
||
|
|
asynchronous I/O tasks.</div>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Asynchronous NDBW</dt>
|
||
|
|
<dd>(System, Job Interval, Pool Interval) The average number of asynchronous
|
||
|
|
nondatabase write operations per transaction for the jobs in the system during
|
||
|
|
the interval. This is calculated from the asynchronous nondatabase write count
|
||
|
|
divided by the transactions processed. This field is not printed if the jobs
|
||
|
|
in the system did not process any transactions. For the Resource Utilization
|
||
|
|
section of the System Report, it is the number of asynchronous nondatabase
|
||
|
|
write operations per second.<div class="note"><span class="notetitle">Note:</span> The asynchronous I/O operations are performed
|
||
|
|
by system asynchronous I/O tasks.</div>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Avail Local Storage (K)</dt>
|
||
|
|
<dd>(Resource Interval) The number of kilobytes of free local storage in the
|
||
|
|
IOP.</dd>
|
||
|
|
<dt class="dlterm">Available Storage</dt>
|
||
|
|
<dd>(Component) Available local storage (in bytes). The average number of
|
||
|
|
bytes of available main storage in the IOP. The free local storage is probably
|
||
|
|
not joined because it has broken into small pieces.</dd>
|
||
|
|
<dt class="dlterm">Average</dt>
|
||
|
|
<dd>(Transaction) The average value of the item described in the column for
|
||
|
|
all transactions.</dd>
|
||
|
|
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />AVERAGE<img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />(Job Trace) Averages for the fields. The entry on the AVERAGE line in
|
||
|
|
the SEQUENCE column shows the number of STRTNS and ENDTNS pairs encountered.
|
||
|
|
For an interactive job, this is the number of transactions entered while the
|
||
|
|
trace was on if the default STRTNS and ENDTNS values were used.<img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm">Average Disk Activity Per Hour</dt>
|
||
|
|
<dd>(Component) See Disk Arm Seek Distance</dd>
|
||
|
|
<dt class="dlterm">Average DIO/Transaction</dt>
|
||
|
|
<dd>(Transaction) Seven columns of information about physical disk I/O counts.
|
||
|
|
Physical I/O contrasts with logical I/O shown elsewhere in these reports.
|
||
|
|
A logical I/O is a request sent at the program level that might result in
|
||
|
|
an access to auxiliary storage (DASD). A physical I/O refers to those requests
|
||
|
|
that actually result in access to auxiliary storage. <ul><li>Synchronous DBR</li>
|
||
|
|
<li>Synchronous NDBR</li>
|
||
|
|
<li>Synchronous Wrt</li>
|
||
|
|
<li>Synchronous Sum</li>
|
||
|
|
<li>Synchronous Max</li>
|
||
|
|
<li>Async Sum</li>
|
||
|
|
<li>Async Max</li>
|
||
|
|
</ul>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Average K per I/O</dt>
|
||
|
|
<dd>(Resource Interval) The average number of kilobytes transferred during
|
||
|
|
each disk read or write operation.</dd>
|
||
|
|
<dt class="dlterm">Average Phys I/O /Sec</dt>
|
||
|
|
<dd>(Resource Interval) The average number of physical disk read and write
|
||
|
|
operations per second made on all disks on the system.</dd>
|
||
|
|
<dt class="dlterm">Average Reads/Sec</dt>
|
||
|
|
<dd>(Resource Interval) The average number of physical disk read operations
|
||
|
|
per second made on all disks on the system.</dd>
|
||
|
|
<dt class="dlterm">Average Response</dt>
|
||
|
|
<dd>(System) Average response time (in seconds) for interactive transactions.
|
||
|
|
The Total/Average interactive response time does not include transactions
|
||
|
|
for DDM server jobs.</dd>
|
||
|
|
<dt class="dlterm">Average Response Time</dt>
|
||
|
|
<dd>(System) Average disk response time per I/O operation.</dd>
|
||
|
|
<dt class="dlterm">Average Response Time (seconds)</dt>
|
||
|
|
<dd>(System) The average interactive response time.</dd>
|
||
|
|
<dt class="dlterm">Average Service Time</dt>
|
||
|
|
<dd>(System) Average disk service time per I/O operation. This is the amount
|
||
|
|
of time a request would take if there were no contention.</dd>
|
||
|
|
<dt class="dlterm">Average Wait Time</dt>
|
||
|
|
<dd>(System) Average disk wait time per I/O operation. Normally due to contention.</dd>
|
||
|
|
<dt class="dlterm">Average Writes/Sec</dt>
|
||
|
|
<dd>(Resource Interval) The average number of physical disk write operations
|
||
|
|
per second made on all disks on the system.</dd>
|
||
|
|
<dt class="dlterm">Avg CPU /Tns</dt>
|
||
|
|
<dd>(Transaction) The average number of processing unit seconds per transaction
|
||
|
|
that fell in the given category.</dd>
|
||
|
|
<dt class="dlterm">Avg K/T /Tns</dt>
|
||
|
|
<dd>(Transaction) The average think time and keying time (or the delay time
|
||
|
|
between transaction boundaries), in seconds, for the interactive jobs.</dd>
|
||
|
|
<dt class="dlterm">Avg Length</dt>
|
||
|
|
<dd>(Lock) The average number of milliseconds a lock or seize was held.</dd>
|
||
|
|
<dt class="dlterm">Avg Rsp (Sec)</dt>
|
||
|
|
<dd>(Transaction) The average transaction response time in seconds.</dd>
|
||
|
|
<dt class="dlterm">Avg Rsp /Tns</dt>
|
||
|
|
<dd>(Transaction) The average response per transaction (in seconds) for the
|
||
|
|
transactions that fell into the given category.</dd>
|
||
|
|
<dt class="dlterm">Avg Rsp Time</dt>
|
||
|
|
<dd>(Component) Average transaction response time.</dd>
|
||
|
|
<dt class="dlterm">Avg Sec Locks</dt>
|
||
|
|
<dd>(Transaction) The average length of a lock in seconds attributed to interactive
|
||
|
|
or noninteractive waiters.</dd>
|
||
|
|
<dt class="dlterm">Avg Sec Seizes</dt>
|
||
|
|
<dd>(Transaction) The average length of a seize in seconds attributed to interactive
|
||
|
|
or noninteractive waiters.</dd>
|
||
|
|
<dt class="dlterm">Avg Time per Service</dt>
|
||
|
|
<dd>(Resource Interval) The amount of time a disk arm uses to process a given
|
||
|
|
request.</dd>
|
||
|
|
<dt class="dlterm">Avg Util</dt>
|
||
|
|
<dd>(System, Resource Interval) On the Disk Utilization Summary of the Resource
|
||
|
|
Report, the average percentage of available time that disks were busy. It
|
||
|
|
is a composite average for all disks on the system. On the Communications
|
||
|
|
Summary of the System Report, the average percentage of line capacity used
|
||
|
|
during the measured time interval.</dd>
|
||
|
|
<dt class="dlterm">Batch asynchronous I/O per second</dt>
|
||
|
|
<dd>(System) The average number of asynchronous physical disk I/O operations
|
||
|
|
per second of batch processing.</dd>
|
||
|
|
<dt class="dlterm">Batch CPU seconds per I/O</dt>
|
||
|
|
<dd>(System) The average number of system processing unit seconds used by
|
||
|
|
all batch jobs for each I/O performed by a batch job.</dd>
|
||
|
|
<dt class="dlterm">Batch CPU Utilization</dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />(Component) Percentage of available processing unit time used
|
||
|
|
by the jobs that the system considers to be batch. <div class="note"><span class="notetitle">Note:</span> For a multiple-processor
|
||
|
|
system, this is the average use across all processors.</div>
|
||
|
|
<img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm">Batch impact factor</dt>
|
||
|
|
<dd>(System) Batch workload adjustment for modeling purposes.</dd>
|
||
|
|
<dt class="dlterm">Batch permanent writes per second</dt>
|
||
|
|
<dd>(System) The average number of permanent write operations per second of
|
||
|
|
batch processing.</dd>
|
||
|
|
<dt class="dlterm">Batch synchronous I/O per second</dt>
|
||
|
|
<dd>(System) The average number of synchronous physical disk I/O operations
|
||
|
|
per second of batch processing.</dd>
|
||
|
|
<dt class="dlterm">BCPU / Synchronous DIO</dt>
|
||
|
|
<dd>(Transaction) The average number of batch processor unit seconds per synchronous
|
||
|
|
disk I/O operation.</dd>
|
||
|
|
<dt class="dlterm">Bin</dt>
|
||
|
|
<dd>(Transaction) The number of binary overflow exceptions.</dd>
|
||
|
|
<dt class="dlterm">Binary Overflow</dt>
|
||
|
|
<dd>(Component) Number of binary overflows per second.</dd>
|
||
|
|
<dt class="dlterm">BMPL - Cur and Inl</dt>
|
||
|
|
<dd>(Transaction) The number of jobs currently in the activity level (beginning
|
||
|
|
current multiprogramming level), and the number of jobs on the ineligible
|
||
|
|
queue (beginning ineligible multiprogramming level) for the storage pool that
|
||
|
|
the job ran in when the job left the wait state (the beginning of the transaction).<div class="note"><span class="notetitle">Note:</span> Multiprogramming
|
||
|
|
level (MPL) is used interchangeably with activity level.</div>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Bundle Wait Count</dt>
|
||
|
|
<dd>(Component) Total number of times the tasks and jobs waited for journal
|
||
|
|
bundles to be written to disk.</dd>
|
||
|
|
<dt class="dlterm">Bundle Wait Pct</dt>
|
||
|
|
<dd>(Component) Percentage of time (relative to the interval elapsed time)
|
||
|
|
spent waiting for journal bundles to be written to disk. </dd>
|
||
|
|
<dt class="dlterm">Bundle Writes System</dt>
|
||
|
|
<dd>(Component) Number of bundle writes to internal system journals. A bundle
|
||
|
|
write is a group of journal entries which are deposited together by the system.</dd>
|
||
|
|
<dt class="dlterm">Bundle Writes User</dt>
|
||
|
|
<dd>(Component) Number of bundle writes to user-created journals. A bundle
|
||
|
|
write is a group of journal entries which are deposited together by the system.</dd>
|
||
|
|
<dt class="dlterm">Bytes per Second Received</dt>
|
||
|
|
<dd>(System) Average number of bytes received per second.</dd>
|
||
|
|
<dt class="dlterm">Bytes per Second Transmitted</dt>
|
||
|
|
<dd>(System) Average number of bytes transmitted per second.</dd>
|
||
|
|
<dt class="dlterm">Bytes Recd per Sec</dt>
|
||
|
|
<dd>(Resource Interval) The average number of bytes received per second.</dd>
|
||
|
|
<dt class="dlterm">Bytes Trnsmitd per Sec</dt>
|
||
|
|
<dd>(Resource Interval) The average number of bytes transmitted per second.</dd>
|
||
|
|
<dt class="dlterm">Category</dt>
|
||
|
|
<dd>(Transaction) A group of transactions categorized together. In the Analysis
|
||
|
|
by Interactive Transaction Category, the transactions are categorized by the
|
||
|
|
processing unit model. The boundary values that are used to separate the transactions
|
||
|
|
are given in the <var class="varname">Avg CPU /Tns</var> column. For the Analysis
|
||
|
|
by Interactive Response Time, they are categorized by their response time.
|
||
|
|
For the Analysis by Interactive Key/Think Time, they are categorized by their
|
||
|
|
key/think time.</dd>
|
||
|
|
<dt class="dlterm">Cache Hit Statistics</dt>
|
||
|
|
<dd>(Component) Statistics data about use of cache including: <ul><li>The percent of Device Cache Read Hit for each arm.</li>
|
||
|
|
<li>The percent of Controller Cache Read Hit for each arm.</li>
|
||
|
|
<li>The percent of efficiency of write cache</li>
|
||
|
|
</ul>
|
||
|
|
<dl><dt class="dlterm">Device read</dt>
|
||
|
|
<dd>Device Read is the number of Device Cache Read Hits (DSDCRH) divided by
|
||
|
|
number of Device Read Operations (DSDROP), expressed as a percent</dd>
|
||
|
|
<dt class="dlterm">Controller read</dt>
|
||
|
|
<dd>Controller Read is the number Controller Cache Read Hits (DSCCRH) divided
|
||
|
|
by number of Read Commands (DSRDS), expressed as a percent.</dd>
|
||
|
|
<dt class="dlterm">Write efficiency</dt>
|
||
|
|
<dd>Write efficiency is the difference between Write Commands (DSWRTS) and
|
||
|
|
Device Write Operations (DSDWOP) divided by Write Commands (DSWRTS), expressed
|
||
|
|
as a percent.</dd>
|
||
|
|
<dt class="dlterm">EACS Read</dt>
|
||
|
|
<dd>The percent of read hits by the Extended Adaptive Cache Simulator.</dd>
|
||
|
|
<dt class="dlterm">EACS Resp</dt>
|
||
|
|
<dd>The percent of response time improvement by the Extended Adaptive Cache
|
||
|
|
Simulator.</dd>
|
||
|
|
</dl>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Channel</dt>
|
||
|
|
<dd>(Resource Interval) The B-channel used by the IDLC line. (special condition)</dd>
|
||
|
|
<dt class="dlterm">Cmn</dt>
|
||
|
|
<dd>(Job Interval) The number of communications I/O operations performed by
|
||
|
|
the selected interactive jobs during the interval.</dd>
|
||
|
|
<dt class="dlterm">Cmn I/O</dt>
|
||
|
|
<dd>(Component) Number of communications operations (Get, Put).</dd>
|
||
|
|
<dt class="dlterm">Cmn I/O Per Second</dt>
|
||
|
|
<dd>(Job Interval) The average number of communications I/O operations performed
|
||
|
|
per second by the selected noninteractive jobs during the interval.</dd>
|
||
|
|
<dt class="dlterm">Collision Detect</dt>
|
||
|
|
<dd>(Resource Interval) The number of times that the terminal equipment (TE)
|
||
|
|
detected that its transmitted frame had been corrupted by another TE attempting
|
||
|
|
to use the same bus.</dd>
|
||
|
|
<dt class="dlterm">Commit Ops</dt>
|
||
|
|
<dd>(Component) Commit operations performed. Includes application and system-provided
|
||
|
|
referential integrity commits.</dd>
|
||
|
|
<dt class="dlterm">Communications I/O Count</dt>
|
||
|
|
<dd>(System) Number of communications I/O operations.</dd>
|
||
|
|
<dt class="dlterm">Communications I/O Get</dt>
|
||
|
|
<dd>(System) Number of communication get operations per transaction.</dd>
|
||
|
|
<dt class="dlterm">Communications I/O Put</dt>
|
||
|
|
<dd>(System) Number of communication put operations per transaction.</dd>
|
||
|
|
<dt class="dlterm">Communications Lines</dt>
|
||
|
|
<dd>(System, Component, Job Interval, Pool Interval) For the Report Selection
|
||
|
|
Criteria, the list of communications lines selected to be included (SLTLINE
|
||
|
|
parameter) or excluded (OMTLINE parameter). These are the communications line
|
||
|
|
names you specify.</dd>
|
||
|
|
<dt class="dlterm">Control Units</dt>
|
||
|
|
<dd>(System, Component, Job Interval, Pool Interval) The list of control units
|
||
|
|
selected to be included (SLTCTL parameter) or excluded (OMTCTL parameter).
|
||
|
|
These are the controller names you specify.</dd>
|
||
|
|
<dt class="dlterm">Count</dt>
|
||
|
|
<dd>(Transaction, Lock) The number of occurrences of the item in the column.
|
||
|
|
For example, in a lock report, it is the number of locks or seizes that occurred.</dd>
|
||
|
|
<dt class="dlterm">CPU</dt>
|
||
|
|
<dd>(Transaction) The total processing unit seconds used by the jobs with
|
||
|
|
a given priority.</dd>
|
||
|
|
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />CPU<img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />(Job Trace) The approximation of the CPU used on this trace entry. This
|
||
|
|
is a calculated value based on the time used and the CPU model being run.<img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm">CPU /Tns</dt>
|
||
|
|
<dd>(Transaction, Job Interval) The amount of available processing unit time
|
||
|
|
per transaction in seconds.</dd>
|
||
|
|
<dt class="dlterm">CPU Model</dt>
|
||
|
|
<dd>(System) The processing unit model number.</dd>
|
||
|
|
<dt class="dlterm">CPU per I/O Async</dt>
|
||
|
|
<dd>(System) CPU use per asynchronous I/O.</dd>
|
||
|
|
<dt class="dlterm">CPU per I/O Sync</dt>
|
||
|
|
<dd>(System) CPU use per synchronous I/O.</dd>
|
||
|
|
<dt class="dlterm">CPU per Logical I/O</dt>
|
||
|
|
<dd>(System) Processing unit time used for each logical disk I/O operation.</dd>
|
||
|
|
<dt class="dlterm">CPU QM</dt>
|
||
|
|
<dd>(Transaction) The simple processing unit queuing multiplier.</dd>
|
||
|
|
<dt class="dlterm">CPU Sec</dt>
|
||
|
|
<dd>(Transaction) The processing unit time used by the job in this state.</dd>
|
||
|
|
<dt class="dlterm">CPU Sec /Sync DIO</dt>
|
||
|
|
<dd>(Transaction) The ratio of CPU seconds divided by synchronous disk I/O
|
||
|
|
requests for each type of job.</dd>
|
||
|
|
<dt class="dlterm">CPU Sec Avg and Max</dt>
|
||
|
|
<dd>(Transaction) The average processing unit time per transaction for the
|
||
|
|
job and the largest processing unit time used for a transaction in the job.
|
||
|
|
If the job is not an interactive or autostart job type, then only the total
|
||
|
|
processing unit time for the job is listed under the MAX column heading.</dd>
|
||
|
|
<dt class="dlterm">CPU Sec per Tns</dt>
|
||
|
|
<dd>(Transaction) The processing unit time per transaction.</dd>
|
||
|
|
<dt class="dlterm">CPU Seconds</dt>
|
||
|
|
<dd>(System, Transaction, Component) Average processing unit seconds used
|
||
|
|
per transaction. For System Summary Data, it is the total available processing
|
||
|
|
unit time used by the jobs during the trace period. For Priority-Jobtype-Pool
|
||
|
|
Statistics, it is the total processing unit seconds used by the jobs with
|
||
|
|
a given combination of priority, job type, and pool. For Batch Job Analysis,
|
||
|
|
it is the amount of available processor unit time used by the job in seconds.
|
||
|
|
For Concurrent Batch Job Statistics, it is the amount of available processor
|
||
|
|
unit time used by the jobs in the job set in seconds.</dd>
|
||
|
|
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />CPU SECONDS<img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />(Job Trace) The approximate processing unit time used for the transaction.<img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm">CPU seconds per transaction</dt>
|
||
|
|
<dd>(System) The average processing unit seconds per transaction.</dd>
|
||
|
|
<dt class="dlterm">CPU Util</dt>
|
||
|
|
<dd>(System, Component, Transaction, Job Interval, Pool Interval, Batch Job
|
||
|
|
Trace) Percentage of available processing unit time used. For multiple-processor
|
||
|
|
systems, this is the total utilization divided by the number of processors.</dd>
|
||
|
|
<dt class="dlterm">CPU Util per Transaction</dt>
|
||
|
|
<dd>(Component) The result of the CPU Utilization divided by the total number
|
||
|
|
of transactions for the job.</dd>
|
||
|
|
<dt class="dlterm">CPU Utilization (Batch)</dt>
|
||
|
|
<dd>The percentage of available CPU time that is used by batch jobs. This
|
||
|
|
is the average of all processors.</dd>
|
||
|
|
<dt class="dlterm">CPU Utilization (Interactive)</dt>
|
||
|
|
<dd>The percentage of available CPU time that is used by interactive jobs.
|
||
|
|
This is the average of all processors.</dd>
|
||
|
|
<dt class="dlterm">CPU Utilization (Total)</dt>
|
||
|
|
<dd>The percentage of available CPU time that is used by interactive and batch
|
||
|
|
jobs. This is the average of all processors.<div class="note"><span class="notetitle">Note:</span> <img src="./delta.gif" alt="Start of change" />For uncapped
|
||
|
|
partitions, the Total CPU utilization might exceed 100 percent.<img src="./deltaend.gif" alt="End of change" /></div>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">CPU/Async I/O</dt>
|
||
|
|
<dd>(Job Interval) The average number of milliseconds of processing unit time
|
||
|
|
taken for each asynchronous disk I/O operation. This is calculated by dividing
|
||
|
|
the milliseconds of the processing unit time the job used by the asynchronous
|
||
|
|
disk I/O count.</dd>
|
||
|
|
<dt class="dlterm">CPU/Sync I/O</dt>
|
||
|
|
<dd>(Job Interval) The average number of milliseconds of processing unit time
|
||
|
|
taken for each synchronous disk I/O operation. This is calculated from the
|
||
|
|
milliseconds of the processing unit time used by the job divided by the synchronous
|
||
|
|
disk I/O count.</dd>
|
||
|
|
<dt class="dlterm">CPU/Tns</dt>
|
||
|
|
<dd>(Transaction) The average number of processing seconds per transaction
|
||
|
|
for the job during the interval. This is calculated from the amount of processing
|
||
|
|
unit time used divided by the number of transactions processed.</dd>
|
||
|
|
<dt class="dlterm">Cpu/Tns (Sec)</dt>
|
||
|
|
<dd>(Transaction) The number of processing unit seconds per transaction.</dd>
|
||
|
|
<dt class="dlterm">Ctl</dt>
|
||
|
|
<dd>(Component) Controller identifier.</dd>
|
||
|
|
<dt class="dlterm">Cum CPU Util</dt>
|
||
|
|
<dd>(Transaction) The cumulative percentage of available processing unit time
|
||
|
|
used by the transactions that have an average response time per transaction
|
||
|
|
equal to or less than the given category. For example, in CPU by Priority
|
||
|
|
for All Jobs for Total Trace Period (System Summary Data), it is the unit
|
||
|
|
time used by the jobs with a priority higher or equal to the given priority.</dd>
|
||
|
|
<dt class="dlterm">Cum Pct Tns</dt>
|
||
|
|
<dd>(Transaction) Cumulative CPU percent per transaction. For system summary
|
||
|
|
data, it is the cumulative CPU percentage of all transactions that have an
|
||
|
|
average response time per transaction equal to or less than the given category.
|
||
|
|
For Interactive Program Transactions Statistics, it is the cumulative CPU
|
||
|
|
percentage of all transactions through the listed program. For Job Statistics
|
||
|
|
section, it is the cumulative CPU percentage of total transactions through
|
||
|
|
the listed job. For Interactive Program Statistics section, it is the cumulative
|
||
|
|
CPU percentage of all transactions through the listed program.</dd>
|
||
|
|
<dt class="dlterm">Cum Util</dt>
|
||
|
|
<dd>(System) Cumulative CPU use (a running total). <div class="note"><span class="notetitle">Note:</span> This is taken from
|
||
|
|
the individual jobs and may differ slightly from the total processing unit
|
||
|
|
use on the workload page.</div>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Cur Inl MPL</dt>
|
||
|
|
<dd>(Transaction) The number of jobs waiting for an activity level (ineligible)
|
||
|
|
in the storage pool.</dd>
|
||
|
|
<dt class="dlterm">Cur MPL</dt>
|
||
|
|
<dd>(Transaction) The number of jobs holding an activity level in the storage
|
||
|
|
pool.</dd>
|
||
|
|
<dt class="dlterm">Current User</dt>
|
||
|
|
<dd>(Job) The user under which the job was running at the end of each interval.
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">DASD Ops/Sec</dt>
|
||
|
|
<dd>(Component) Disk operations per second.</dd>
|
||
|
|
<dt class="dlterm">DASD Ops Per Sec Reads</dt>
|
||
|
|
<dd>(Resource) Number of reads per second</dd>
|
||
|
|
<dt class="dlterm">DASD Ops Per Sec Writes</dt>
|
||
|
|
<dd>(Resource) Number of writes per second</dd>
|
||
|
|
<dt class="dlterm">Datagrams Received</dt>
|
||
|
|
<dd>(Component) The total number of input datagrams received from interfaces.
|
||
|
|
This number includes those that were received in error.</dd>
|
||
|
|
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />DB<img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />(Job Trace) The number of physical database reads that occurred for the
|
||
|
|
entry.<img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm">DB Cpb Util</dt>
|
||
|
|
<dd>(Component) The percentage of database capability that is used to perform
|
||
|
|
database processing.</dd>
|
||
|
|
<dt class="dlterm">DB Fault</dt>
|
||
|
|
<dd>(System, Component) Average number of database faults per second.</dd>
|
||
|
|
<dt class="dlterm">DB Pages</dt>
|
||
|
|
<dd>(System, Component) Average number of database pages read per second.</dd>
|
||
|
|
<dt class="dlterm">DB Read</dt>
|
||
|
|
<dd>(Transaction) When listed in Physical I/O Counts column, it is the number
|
||
|
|
of database read requests while the job was in that state. When listed in
|
||
|
|
the Sync Disk I/O Rqs/Tns column, it is the average number of synchronous
|
||
|
|
database read requests per transaction.</dd>
|
||
|
|
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />DB READS<img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />(Job Trace) The number of physical database reads that occurred.<img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm">DB Write</dt>
|
||
|
|
<dd>(Transaction) When listed in the Sync Disk I/O Rqs/Tns column, it is the
|
||
|
|
average number of synchronous database write requests per transaction.</dd>
|
||
|
|
<dt class="dlterm">DB Wrt</dt>
|
||
|
|
<dd>(Transaction) When listed in the Physical I/O Counts column, it is the
|
||
|
|
number of database write requests while the job was in that state. When listed
|
||
|
|
in the Synchronous Disk I/O Counts column, it is the number of synchronous
|
||
|
|
database write requests per transaction.</dd>
|
||
|
|
<dt class="dlterm">DDM I/O</dt>
|
||
|
|
<dd>(Component, Job Interval) The number of logical database I/O operations
|
||
|
|
for a distributed data management (DDM) server job.</dd>
|
||
|
|
<dt class="dlterm">DDM Svr Wait /Tns</dt>
|
||
|
|
<dd>(Transaction) The average time, in seconds, that a source distributed
|
||
|
|
data management (DDM) server job spent waiting for the target system to respond
|
||
|
|
to a request for data per transaction. This value includes line time and time
|
||
|
|
spent by the target system responding to the request for data.</dd>
|
||
|
|
<dt class="dlterm">Dec</dt>
|
||
|
|
<dd>(Transaction) The number of decimal overflow exceptions.</dd>
|
||
|
|
<dt class="dlterm">Decimal Data</dt>
|
||
|
|
<dd>(Component) Data exception count per second. A data exception occurs when
|
||
|
|
data that is not valid is detected by arithmetic instructions. Examples are
|
||
|
|
signs or digit codes that are not valid in decimal instructions, or an insufficient
|
||
|
|
number of farthest left zeros in multiply instructions.</dd>
|
||
|
|
<dt class="dlterm">Decommit Ops</dt>
|
||
|
|
<dd>(Component) Decommit operations performed. Includes application and system-provided
|
||
|
|
referential integrity decommits. </dd>
|
||
|
|
<dt class="dlterm">Decimal Overflow</dt>
|
||
|
|
<dd>(Component) Number of decimal overflows per second.</dd>
|
||
|
|
<dt class="dlterm">Description</dt>
|
||
|
|
<dd>(Component) More detailed description of the exception type.</dd>
|
||
|
|
<dt class="dlterm">Detected Access Transmission Error (DTSE) In</dt>
|
||
|
|
<dd>(Resource Interval) The number of times the network termination 1 (NT1)
|
||
|
|
end point notified the terminal equipment (TE) of an error in data crossing
|
||
|
|
the ISDN U interface from the line transmission termination (LT) to the NT1
|
||
|
|
end point. The NT1 end point reports the errors to the TE through the maintenance
|
||
|
|
channel S1.</dd>
|
||
|
|
<dt class="dlterm">Detected Access Transmission Error (DTSE) Out</dt>
|
||
|
|
<dd>(Resource Interval) The number of times the network termination 1 (NT1)
|
||
|
|
end point notified the terminal equipment (TE) of an error in data crossing
|
||
|
|
the ISDN U interface from the NT1 end point to the LT. The NT1 end point reports
|
||
|
|
the errors to the TE through the maintenance channel S1.</dd>
|
||
|
|
<dt class="dlterm">Device</dt>
|
||
|
|
<dd>(Component) Device identifier.</dd>
|
||
|
|
<dt class="dlterm">DIO/Sec Async</dt>
|
||
|
|
<dd>(System) Number of asynchronous I/O operations per second.</dd>
|
||
|
|
<dt class="dlterm">DIO/Sec Sync</dt>
|
||
|
|
<dd>(System) Number of synchronous I/O operations per second.</dd>
|
||
|
|
<dt class="dlterm">Disk Arm Seek Distance</dt>
|
||
|
|
<dd>(Component) Average seek distance distributions per hour: <dl><dt class="dlterm">0</dt>
|
||
|
|
<dd>Number of zero seeks</dd>
|
||
|
|
<dt class="dlterm">1/12</dt>
|
||
|
|
<dd>Number of seeks between 0 and 1/12 of the disk</dd>
|
||
|
|
<dt class="dlterm">1/6</dt>
|
||
|
|
<dd>Number of seeks between 1/12 and 1/6 of the disk</dd>
|
||
|
|
<dt class="dlterm">1/3</dt>
|
||
|
|
<dd>Number of seeks between 1/6 and 1/3 of the disk</dd>
|
||
|
|
<dt class="dlterm">2/3</dt>
|
||
|
|
<dd>Number of seeks between 1/3 and 2/3 of the disk</dd>
|
||
|
|
<dt class="dlterm">>2/3</dt>
|
||
|
|
<dd>Number of seeks greater than 2/3 of the disk</dd>
|
||
|
|
</dl>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Disk Arms</dt>
|
||
|
|
<dd>(System) The number of disk arms for this IOP.</dd>
|
||
|
|
<dt class="dlterm">Disk Capacity</dt>
|
||
|
|
<dd>(Component) Average amount of disk space used or available. <dl><dt class="dlterm">MB</dt>
|
||
|
|
<dd>Millions of bytes available on the disk.</dd>
|
||
|
|
<dt class="dlterm">Percent</dt>
|
||
|
|
<dd>Percent of space available on the disk.</dd>
|
||
|
|
</dl>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Disk Controllers</dt>
|
||
|
|
<dd>(System) The number of disk storage controllers for this IOP.</dd>
|
||
|
|
<dt class="dlterm">Disk Feature</dt>
|
||
|
|
<dd>(System) The type of disk (9332, 9335, and so on).</dd>
|
||
|
|
<dt class="dlterm">Disk I/O Async</dt>
|
||
|
|
<dd>(System, Component) Total number of asynchronous disk I/O operations.</dd>
|
||
|
|
<dt class="dlterm">Disk I/O Logical</dt>
|
||
|
|
<dd>(Component) The number of logical disk operations, such as gets and puts.</dd>
|
||
|
|
<dt class="dlterm">Disk I/O per Second</dt>
|
||
|
|
<dd>(System) Average number of physical disk I/O operations per second.</dd>
|
||
|
|
<dt class="dlterm">Disk I/O Reads /Sec</dt>
|
||
|
|
<dd>(Resource Interval) The average number of disk read operations per second
|
||
|
|
by the disk IOP.</dd>
|
||
|
|
<dt class="dlterm">Disk I/O Requests</dt>
|
||
|
|
<dd>(Transaction) The total number of synchronous and asynchronous disk I/O
|
||
|
|
requests issued by the jobs during the trace period.</dd>
|
||
|
|
<dt class="dlterm">Disk I/O Sync</dt>
|
||
|
|
<dd>(System, Component) Total number of synchronous disk I/O operations.</dd>
|
||
|
|
<dt class="dlterm">Disk I/O Writes /Sec</dt>
|
||
|
|
<dd>(Resource Interval) The average number of disk write operations per second
|
||
|
|
by the disk IOP.</dd>
|
||
|
|
<dt class="dlterm">Disk IOPs</dt>
|
||
|
|
<dd>(System) The number of disk IOP controllers.</dd>
|
||
|
|
<dt class="dlterm">Disk mirroring</dt>
|
||
|
|
<dd>(System) Indicates whether disk mirroring is active.</dd>
|
||
|
|
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />Disk Space Used<img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />(Resource Interval) The total disk space used in gigabytes for the entire
|
||
|
|
system.<img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm">Disk transfer size (KB)</dt>
|
||
|
|
<dd>(System) The average number of kilobytes transferred per disk operation.</dd>
|
||
|
|
<dt class="dlterm">Disk utilization</dt>
|
||
|
|
<dd>(System) The fraction of the time interval that the disk arms were performing
|
||
|
|
I/O operations.</dd>
|
||
|
|
<dt class="dlterm">Dsk CPU Util</dt>
|
||
|
|
<dd>(System, Resource Interval) The percentage of CPU used by the disk unit.</dd>
|
||
|
|
<dt class="dlterm">Dtgm Req Transm Dscrd</dt>
|
||
|
|
<dd>(Component) The percentage of IP datagrams that are discarded because
|
||
|
|
of the following reasons: <ul><li>No route was found to transmit the datagrams to their destination.</li>
|
||
|
|
<li>Lack of buffer space.</li>
|
||
|
|
</ul>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Dtgm Req for Transm Tot</dt>
|
||
|
|
<dd>(Component) The total number of IP datagrams that local IP user-protocols
|
||
|
|
supplied to IP in requests for transmission.</dd>
|
||
|
|
<dt class="dlterm">Elapsed Seconds</dt>
|
||
|
|
<dd>(Transaction, Component) The elapsed time in seconds. For the Batch Job
|
||
|
|
Analysis section of the Transaction Report, it is the number of seconds elapsed
|
||
|
|
from when the job started to when the job ended. For the Concurrent Batch
|
||
|
|
Job Statistics section of the Transaction Report, it is the total elapsed
|
||
|
|
time of all jobs in that job set.</dd>
|
||
|
|
<dt class="dlterm">Elapsed Time</dt>
|
||
|
|
<dd>(Job Interval) The amount of time (minutes and seconds) for which the
|
||
|
|
job existed during the interval. This is the same as the interval length unless
|
||
|
|
the job started or ended during the interval, in which case it is less.</dd>
|
||
|
|
<dt class="dlterm">Elapsed Time--Seconds</dt>
|
||
|
|
<dd>(Transaction) Shows the time spent by the job, in the following columns: <dl><dt class="dlterm">Long Wait</dt>
|
||
|
|
<dd>Elapsed times in the state (such as waiting for the next transaction or
|
||
|
|
lock-wait time).</dd>
|
||
|
|
<dt class="dlterm">Active/Rsp</dt>
|
||
|
|
<dd>During transaction processing, the time the job spends (either waiting
|
||
|
|
or active) while it holds an activity level. At the end of a transaction (on
|
||
|
|
the transaction totals line), this is the time the job spent processing the
|
||
|
|
transaction in an activity level, for long waits caused by locks, and in the
|
||
|
|
ineligible state.</dd>
|
||
|
|
<dt class="dlterm">Inel Wait</dt>
|
||
|
|
<dd>The time the job spent in the ineligible wait state waiting for an activity
|
||
|
|
level.</dd>
|
||
|
|
</dl>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">EM3270 Wait /Tns</dt>
|
||
|
|
<dd>(Transaction) The average, in seconds, of the time spent waiting on the
|
||
|
|
host system communications for Systems Network Architecture (SNA) and binary
|
||
|
|
synchronous communications (BSC) 3270DE per transaction. Program logic is
|
||
|
|
required to determine if the emulation program is communicating with the display
|
||
|
|
or the host processing unit. Because there are requirements on event-wait
|
||
|
|
processing, not all transition combinations can be detected.</dd>
|
||
|
|
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />ENTRY<img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />(Job Trace) The instruction in the program where the program was given
|
||
|
|
control. This is true when a program is nonobservant and observant.<img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm">EORn</dt>
|
||
|
|
<dd>(Transaction) Listed in the Wait Code column, End of response time for
|
||
|
|
transaction n. These codes are in the wait code column, but they are not wait
|
||
|
|
codes. They indicate transaction boundary trace records.</dd>
|
||
|
|
<dt class="dlterm">EOTn</dt>
|
||
|
|
<dd>(Transaction) Listed in the Wait Code column, End of transaction for transaction
|
||
|
|
for type n. These codes are in the wait code column, but they are not wait
|
||
|
|
codes. They indicate transaction boundary trace records.</dd>
|
||
|
|
<dt class="dlterm">Estimated Exposr AP Not Jrnld</dt>
|
||
|
|
<dd>(Component) System-estimated access path recovery time exposure in minutes
|
||
|
|
if no access paths were being journaled by the system.</dd>
|
||
|
|
<dt class="dlterm">Estimated Exposr Curr System</dt>
|
||
|
|
<dd>(Component) System-estimated access path recovery time exposure in minutes.</dd>
|
||
|
|
<dt class="dlterm">Est Of AWS</dt>
|
||
|
|
<dd>(Transaction) An estimate of the number of active work stations for the
|
||
|
|
trace period or interval. Any delay time greater than 600 seconds has been
|
||
|
|
rounded to 600 seconds. This technique is used to reduce the effect of very
|
||
|
|
casual users (those who may do intermittent work or leave their work stations
|
||
|
|
for long periods of time) on the estimate of active work stations.</dd>
|
||
|
|
<dt class="dlterm">Event Wait /Tns</dt>
|
||
|
|
<dd>(Transaction) The average time, in seconds, of the event-wait time per
|
||
|
|
transaction. Often requests made by a job that runs on the system are made
|
||
|
|
to asynchronous jobs. These asynchronous jobs use an event to signal completion
|
||
|
|
of the request back to the requester. The event-wait time is the time the
|
||
|
|
requesting job waits for such a signal.</dd>
|
||
|
|
<dt class="dlterm">EVT</dt>
|
||
|
|
<dd>(Transaction) Listed in the Wait Code column, Event Wait. This is a long
|
||
|
|
wait that occurs when waiting on a message queue.</dd>
|
||
|
|
<dt class="dlterm">Exception Type</dt>
|
||
|
|
<dd>(Component) Type of program exception that results from the internal microprogram
|
||
|
|
instructions being run in internal microprogram instructions procedure. Because
|
||
|
|
these exceptions are monitored at a low level within the system, it is difficult
|
||
|
|
to associate these exceptions with specific end-user operations. The counts
|
||
|
|
are meaningful when the processing unit time required to process them affects
|
||
|
|
system performance. A variation in the counts may indicate a system change
|
||
|
|
that could affect performance. For example, a large variation in seize or
|
||
|
|
lock counts may indicate a job scheduling problem or indicate that contention
|
||
|
|
exists between an old application and a new one that uses the same resources.<div class="note"><span class="notetitle">Note:</span> To
|
||
|
|
see the seize and lock counts, you should collect the trace data by using
|
||
|
|
the <span class="cmdname">Start Performance Trace (STRPFRTRC)</span> command. Run the <span class="cmdname">Print
|
||
|
|
Transaction Report (PRTTNSRPT)</span> to list the objects and jobs that
|
||
|
|
are holding the locks.</div>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Exceptional wait</dt>
|
||
|
|
<dd>(System) The average exceptional wait time, in seconds, per transaction.
|
||
|
|
An <var class="varname">exceptional wait</var> is that portion of internal response
|
||
|
|
time that cannot be attributed to the use of the processor and disk. An exceptional
|
||
|
|
wait is caused by contention for internal resources of the system, for example,
|
||
|
|
waiting for a lock on a database record. <dl><dt class="dlterm">Constant</dt>
|
||
|
|
<dd>The portion of exceptional wait time held constant as throughput increases.</dd>
|
||
|
|
<dt class="dlterm">Variable</dt>
|
||
|
|
<dd>The portion of exceptional wait time that varies as throughput increases.</dd>
|
||
|
|
</dl>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Excp</dt>
|
||
|
|
<dd>(Component, Transaction) For the Component Report, it is the total number
|
||
|
|
of program exceptions that occurred per second. For the Transaction Report,
|
||
|
|
a Y in this column means that the transaction had exceptions. The types of
|
||
|
|
exceptions that are included are process access group exceptions, and decimal,
|
||
|
|
binary, and floating point overflow. See the Transition Report to see which
|
||
|
|
exceptions the transaction had.</dd>
|
||
|
|
<dt class="dlterm">Excp Wait</dt>
|
||
|
|
<dd>(Transaction) The amount of exceptional wait time for the jobs in the
|
||
|
|
job set in seconds.</dd>
|
||
|
|
<dt class="dlterm">Excp Wait /Tns</dt>
|
||
|
|
<dd>(Transaction) The average exceptional wait time, in seconds, per transaction.
|
||
|
|
This value is the sum of those waits listed under the Exceptional Wait Breakdown
|
||
|
|
by Job Type part.</dd>
|
||
|
|
<dt class="dlterm">Excp Wait Sec</dt>
|
||
|
|
<dd>(Transaction) The total amount of exceptional wait time in seconds for
|
||
|
|
the job.</dd>
|
||
|
|
<dt class="dlterm">Excs ACTM /Tns</dt>
|
||
|
|
<dd>(Transaction) The average time, in seconds, of the excess activity level
|
||
|
|
time per transaction (for example, time spent in the active state but not
|
||
|
|
using the processing unit). If enough activity levels are available and there
|
||
|
|
is plenty of interactive work of higher priority to do, a job waits longer
|
||
|
|
for processing unit cycles. If the value is greater than .3, look at jobs
|
||
|
|
that correspond to particular applications for more information. By looking
|
||
|
|
at these jobs, you might be able to determine which application's jobs are
|
||
|
|
contributing most to this value. Use the Transaction and Transition Reports
|
||
|
|
for these jobs for additional information. The formula for excessive activity-level
|
||
|
|
time is shown below: <pre>Active Time - [
|
||
|
|
(multiplier X CPU X Beginning Activity Level) +
|
||
|
|
(Number of synchronous disk I/O operations X .010)]</pre>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> If the beginning activity level is greater than 1, the multiplier
|
||
|
|
equals 0.5. If the beginning activity level is any other value, the multiplier
|
||
|
|
equals 1.</div>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />EXIT<img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />(Job Trace) The instruction number in the program where the program gave
|
||
|
|
up control.<img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm">Expert Cache</dt>
|
||
|
|
<dd>(System, Component) Directs the system to determine which objects or portions
|
||
|
|
of objects should remain in a shared main storage pool based on the reference
|
||
|
|
patterns of data within the object. Expert cache uses a storage management
|
||
|
|
tuner, which runs independently of the system dynamic tuner, to examine overall
|
||
|
|
paging characteristics and history of the pool. Some values that you might
|
||
|
|
see in this column are associated with the Work with Shared Pools (WRKSHRPOOL)
|
||
|
|
command: <ul><li>0=*FIXED, which indicates the system does not dynamically adjust the paging
|
||
|
|
characteristics of the storage pool. The system uses default values.</li>
|
||
|
|
<li>3=*CALC, which indicates the system dynamically adjusts the paging characteristics
|
||
|
|
of the storage pool for optimum performance.</li>
|
||
|
|
</ul>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Exposed AP System Journaled</dt>
|
||
|
|
<dd>(Component) The number of exposed access paths currently being journaled
|
||
|
|
by the system.</dd>
|
||
|
|
<dt class="dlterm">Exposed AP System Not Journaled</dt>
|
||
|
|
<dd>(Component) The number of exposed access paths currently not being journaled
|
||
|
|
by the system.</dd>
|
||
|
|
<dt class="dlterm">/F</dt>
|
||
|
|
<dd>(System, Resource Interval) The line speed of the protocol reported as
|
||
|
|
full duplex. This indicator applies to the line speeds for an Ethernet (ELAN)
|
||
|
|
token-ring (TRLAN) line, or an asynchronous transfer mode line.</dd>
|
||
|
|
<dt class="dlterm">Far End Code Violation</dt>
|
||
|
|
<dd>(Resource Interval) The number of unintended code violations detected
|
||
|
|
by the network termination 1 (NT1) end point for frames transmitted to the
|
||
|
|
NT1 end point on the interface for the T reference point. The NT1 end point
|
||
|
|
reports a violation to the termination equipment (TE) through the maintenance
|
||
|
|
channel S1.</dd>
|
||
|
|
<dt class="dlterm">Faults</dt>
|
||
|
|
<dd>(System) A value that represents the total page faults that occurred for
|
||
|
|
each job type or job priority during the collection. This is the same value
|
||
|
|
as shown in the JBTFLT field of the QAPMJOBS or QAPMJOBL file.</dd>
|
||
|
|
<dt class="dlterm">File</dt>
|
||
|
|
<dd>(Transaction) The file that contains the object.</dd>
|
||
|
|
<dt class="dlterm">Flp</dt>
|
||
|
|
<dd>(Transaction) The number of floating point overflow exceptions.</dd>
|
||
|
|
<dt class="dlterm">Flp Overflow</dt>
|
||
|
|
<dd>(Component) Number of floating point overflows per second.</dd>
|
||
|
|
<dt class="dlterm">Frame Retry</dt>
|
||
|
|
<dd>(Resource Interval) The number of attempts to retransmit a frame to a
|
||
|
|
remote controller.</dd>
|
||
|
|
<dt class="dlterm">Frames Received Pct Err</dt>
|
||
|
|
<dd>(Resource Interval) The percentage of frames received in error. Errors
|
||
|
|
can occur when the host system has an error or cannot process received data
|
||
|
|
fast enough.</dd>
|
||
|
|
<dt class="dlterm">Frames Received Total</dt>
|
||
|
|
<dd>(Resource Interval) The total number of frames received including frames
|
||
|
|
with errors and frames that are not valid.</dd>
|
||
|
|
<dt class="dlterm">Frames Transmitted Pct Err</dt>
|
||
|
|
<dd>(Resource Interval) The percentage of frames retransmitted due to error.</dd>
|
||
|
|
<dt class="dlterm">Frames Transmitted Total</dt>
|
||
|
|
<dd>(Resource Interval) The total number of frames transmitted.</dd>
|
||
|
|
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />FULL CLS<img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />(Job Trace) The number of full closes for all types of files.<img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />FULL OPN<img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />(Job Trace) The number of full opens for all types of files.<img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />FUNCTION<img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />(Job Trace) This causes the trace entry to be recorded. The possible trace
|
||
|
|
entries are as follows:
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><caption>Table 1. </caption><thead align="left"><tr valign="bottom"><th valign="bottom" id="d0e1264">Function ID</th>
|
||
|
|
<th valign="bottom" id="d0e1266">Description</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td valign="top" headers="d0e1264 ">DATA</td>
|
||
|
|
<td valign="top" headers="d0e1266 ">Data trace record</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e1264 ">CALL</td>
|
||
|
|
<td valign="top" headers="d0e1266 ">Call external</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e1264 ">XCTL</td>
|
||
|
|
<td valign="top" headers="d0e1266 ">Transfer control</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e1264 ">EVENT</td>
|
||
|
|
<td valign="top" headers="d0e1266 ">Event handler invocation</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e1264 ">EXTXHINV</td>
|
||
|
|
<td valign="top" headers="d0e1266 ">External exception handler invocation</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e1264 ">INTXHINV</td>
|
||
|
|
<td valign="top" headers="d0e1266 ">Internal exception handler invocation</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e1264 ">INTXHRET</td>
|
||
|
|
<td valign="top" headers="d0e1266 ">Return from internal exception handler</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e1264 ">INVEXIT</td>
|
||
|
|
<td valign="top" headers="d0e1266 ">Invocation exit</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e1264 ">RETURN</td>
|
||
|
|
<td valign="top" headers="d0e1266 ">Return external</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e1264 ">ITRMXRSG</td>
|
||
|
|
<td valign="top" headers="d0e1266 ">Invocation ended due to resignaling exception</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e1264 ">EXTXHRET</td>
|
||
|
|
<td valign="top" headers="d0e1266 ">Return external or from a procedure instruction</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e1264 ">PTRMTPP</td>
|
||
|
|
<td valign="top" headers="d0e1266 ">Termination phase end</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e1264 ">PTRMUNX</td>
|
||
|
|
<td valign="top" headers="d0e1266 ">End process due to an unhandled exception</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e1264 ">NOTUSED</td>
|
||
|
|
<td valign="top" headers="d0e1266 ">This type is a non-valid trace type</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e1264 ">ITERM</td>
|
||
|
|
<td valign="top" headers="d0e1266 ">Invocation ended</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e1264 ">CANCLINV</td>
|
||
|
|
<td valign="top" headers="d0e1266 ">Cancel invocation instruction</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
<img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm">Functional Areas</dt>
|
||
|
|
<dd>(System, Component, Transaction, Job Interval, Pool Interval) For Report
|
||
|
|
Selection Criteria, the list of functional areas selected to be included (SLTFCNARA
|
||
|
|
parameter) or excluded (OMTFCNARA parameter).</dd>
|
||
|
|
<dt class="dlterm">/H</dt>
|
||
|
|
<dd>(System, Resource Interval) The line speed of the protocol reported as
|
||
|
|
half duplex. This indicator applies to the line speeds for an Ethernet (ELAN)
|
||
|
|
token-ring (TRLAN) line, or an asynchronous transfer mode line.</dd>
|
||
|
|
<dt class="dlterm">HDW</dt>
|
||
|
|
<dd>(Transaction) Listed in the Wait Code column, Hold Wait (job suspended
|
||
|
|
or system request). The job released a lock it had on the object named on
|
||
|
|
the next detail line of the report (OBJECT --). The job that was waiting for
|
||
|
|
the object is named on this line (WAITER --) along with the amount of time
|
||
|
|
the job spent waiting for the lock to be released.</dd>
|
||
|
|
<dt class="dlterm">High Srv Time</dt>
|
||
|
|
<dd>(Resource Interval) The highest average service time in seconds for a
|
||
|
|
disk arm in the system.</dd>
|
||
|
|
<dt class="dlterm">High Srv Unit</dt>
|
||
|
|
<dd>The disk arm with the highest service time.</dd>
|
||
|
|
<dt class="dlterm">High Util</dt>
|
||
|
|
<dd>(Resource Interval) The percentage of use for the disk arm that has the
|
||
|
|
highest utilization.</dd>
|
||
|
|
<dt class="dlterm">High Util Unit</dt>
|
||
|
|
<dd>(Component, Resource Interval) The disk arm with the highest utilization.</dd>
|
||
|
|
<dt class="dlterm">High Utilization Disk</dt>
|
||
|
|
<dd>(Component) Percent of utilization of the most utilized disk arm during
|
||
|
|
this interval.</dd>
|
||
|
|
<dt class="dlterm">High Utilization Unit</dt>
|
||
|
|
<dd>(Component) Disk arm that had the most utilization during this interval.</dd>
|
||
|
|
<dt class="dlterm">Holder Job Name</dt>
|
||
|
|
<dd>(Transaction) The name of the job that held the object.</dd>
|
||
|
|
<dt class="dlterm">Holder Number</dt>
|
||
|
|
<dd>(Transaction) The number of the job that held the object.</dd>
|
||
|
|
<dt class="dlterm">Holder Pool</dt>
|
||
|
|
<dd>(Transaction) The pool that held the job while it was running.</dd>
|
||
|
|
<dt class="dlterm">Holder Pty</dt>
|
||
|
|
<dd>(Transaction) The priority of the holder's job.</dd>
|
||
|
|
<dt class="dlterm">Holder Type</dt>
|
||
|
|
<dd>(Transaction) The type and subtype of the holder's job.</dd>
|
||
|
|
<dt class="dlterm">Holder User Name</dt>
|
||
|
|
<dd>(Transaction) The name of the user that held the object.</dd>
|
||
|
|
<dt class="dlterm">Holder's Job Name</dt>
|
||
|
|
<dd>(Lock) The name of the job holding the lock.</dd>
|
||
|
|
<dt class="dlterm">I Frames Recd per Sec</dt>
|
||
|
|
<dd>(Resource Interval) The number of information frames received per second.</dd>
|
||
|
|
<dt class="dlterm">I Frames Trnsmitd per Sec</dt>
|
||
|
|
<dd>(Resource Interval) The number of information frames transmitted per second.</dd>
|
||
|
|
<dt class="dlterm">I/O Wait</dt>
|
||
|
|
<dd>(Resource Interval) The amount of time in which a given I/O request is
|
||
|
|
ready to be processed, but the disk arm is not yet available to perform the
|
||
|
|
request.</dd>
|
||
|
|
<dt class="dlterm">ICMP Messages Error</dt>
|
||
|
|
<dd>(Component) This is the number of Internet Control Message Protocol (ICMP)
|
||
|
|
messages that the entity received but determined that the messages had errors
|
||
|
|
or are messages that the entity did not send due to problems.</dd>
|
||
|
|
<dt class="dlterm">ICMP Messages Received</dt>
|
||
|
|
<dd>(Component) This is the total number of Internet Control Message Protocol
|
||
|
|
(ICMP) messages that the entity received.</dd>
|
||
|
|
<dt class="dlterm">ICMP Messages Sent</dt>
|
||
|
|
<dd>(Component) This is the total number of Internet Control Message Protocol
|
||
|
|
(ICMP) messages that the entity attempted to send.</dd>
|
||
|
|
<dt class="dlterm">Incoming Calls Pct Retry</dt>
|
||
|
|
<dd>(Resource Interval) The percentage of incoming calls that were rejected
|
||
|
|
by the network.</dd>
|
||
|
|
<dt class="dlterm">Incoming Calls Total</dt>
|
||
|
|
<dd>(Resource Interval) The total number of incoming call attempts.</dd>
|
||
|
|
<dt class="dlterm">Inel Time A-I/W-I</dt>
|
||
|
|
<dd>(Transaction) The amount of time the job spent in the ineligible state,
|
||
|
|
either coming from time slice end (active-to-ineligible) or from the wait
|
||
|
|
state (wait-to-ineligible).</dd>
|
||
|
|
<dt class="dlterm">Inel Wait</dt>
|
||
|
|
<dd>(Transaction) Listed in the Elapsed Time--Seconds column, the time the
|
||
|
|
job spent in the ineligible wait state waiting for an activity level.</dd>
|
||
|
|
<dt class="dlterm">Int Feat Util</dt>
|
||
|
|
<dd>(Component) The percentage of Interactive Feature that is used by all
|
||
|
|
jobs.</dd>
|
||
|
|
<dt class="dlterm">Inter CPU Utilization</dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />(Component) Percentage of available processing unit time used
|
||
|
|
by the jobs that the system considers to be interactive.<div class="note"><span class="notetitle">Note:</span> For
|
||
|
|
a multiple-processor system, this is the average use across all processors.</div>
|
||
|
|
<img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />INV<img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />(Job Trace) The call level of the program.<img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm">IOP</dt>
|
||
|
|
<dd>(Component) Input/output processor (IOP) Resource name and model number
|
||
|
|
for each communications IOP, DASD IOP, local workstation IOP, and multifunction
|
||
|
|
IOP. Communications IOP is the percent of CPU used in the IOP. The percent
|
||
|
|
does not necessarily mean that the IOP is doing any data transfers. Some of
|
||
|
|
the percent can be attributed to overhead of an active line.</dd>
|
||
|
|
<dt class="dlterm">IOP Name/Line</dt>
|
||
|
|
<dd>(System, Resource Interval) Input/output (IOP) processor resource name
|
||
|
|
and model number line.</dd>
|
||
|
|
<dt class="dlterm">IOP Name(Model)</dt>
|
||
|
|
<dd>(Resource Interval) The input/output processor (IOP) identification and
|
||
|
|
the model number in parentheses.</dd>
|
||
|
|
<dt class="dlterm">IOP Name</dt>
|
||
|
|
<dd>(System, Component) Input/Output processor (IOP) resource name.</dd>
|
||
|
|
<dt class="dlterm">IOP Name Network Interface</dt>
|
||
|
|
<dd>(Resource Interval) The IOP name of the network interface.</dd>
|
||
|
|
<dt class="dlterm">IOP Processor Util Comm</dt>
|
||
|
|
<dd>(Component, Resource) Utilization of IOP due to communications activity.</dd>
|
||
|
|
<dt class="dlterm">IOP Processor Util LWSC</dt>
|
||
|
|
<dd>(Component, Resource) Utilization of IOP due to local workstation activity.</dd>
|
||
|
|
<dt class="dlterm">IOP Processor Util DASD</dt>
|
||
|
|
<dd>(Component, Resource) Utilization of IOP due to DASD activity.</dd>
|
||
|
|
<dt class="dlterm">IOP Processor Util Total</dt>
|
||
|
|
<dd>(Component, Resource Interval) The total percent of utilization for each
|
||
|
|
local workstation, disk, and communications IOP.</dd>
|
||
|
|
<dt class="dlterm">IOP Util</dt>
|
||
|
|
<dd>(System) For the Disk Utilization section of the System Report, it is
|
||
|
|
the percentage of utilization for each input/output processor (IOP). <div class="note"><span class="notetitle">Note:</span> For
|
||
|
|
the multifunction I/O processors, this is utilization due to disk activity
|
||
|
|
only, not communications activity. For the System Model Parameter section
|
||
|
|
it is the fraction of the time interval the disk IOP was performing I/O operations.</div>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Itv End</dt>
|
||
|
|
<dd>(Component, Transaction, Job Interval, Pool Interval, Resource Interval)
|
||
|
|
The time (hour and minute) when the data was collected. For the Exception
|
||
|
|
Occurrence Summary and Interval Counts of the Component Report, it is the
|
||
|
|
ending time for the sample interval in which Collection Services recorded
|
||
|
|
the exception.</dd>
|
||
|
|
<dt class="dlterm">Job Maximum A-I</dt>
|
||
|
|
<dd>(Pool Interval) The highest number of active-state to ineligible-state
|
||
|
|
transitions by a selected job in the pool or subsystem.</dd>
|
||
|
|
<dt class="dlterm">Job Maximum A-W</dt>
|
||
|
|
<dd>(Pool) The highest number of active-to-wait state transitions by a selected
|
||
|
|
job in the pool or subsystem.</dd>
|
||
|
|
<dt class="dlterm">Job Maximum CPU Util</dt>
|
||
|
|
<dd>(Pool Interval) The highest percentage of available processing unit time
|
||
|
|
used by a selected job in the pool or subsystem.</dd>
|
||
|
|
<dt class="dlterm">Job Maximum Phy I/O</dt>
|
||
|
|
<dd>(Pool Interval) The highest number of physical disk input and output operations
|
||
|
|
by a selected job in the pool or subsystem.</dd>
|
||
|
|
<dt class="dlterm">Job Maximum Rsp</dt>
|
||
|
|
<dd>(Pool Interval) The highest response time in seconds per transaction by
|
||
|
|
a selected job in the pool or subsystem. The response time is the amount of
|
||
|
|
time spent waiting for and using the resources divided by the number of transactions.</dd>
|
||
|
|
<dt class="dlterm">Job Maximum Tns</dt>
|
||
|
|
<dd>(Pool Interval) The highest number of transactions by a selected job in
|
||
|
|
the pool or subsystem.</dd>
|
||
|
|
<dt class="dlterm">Job Maximum W-I</dt>
|
||
|
|
<dd>(Pool Interval) The highest number of wait-state to ineligible-state transitions
|
||
|
|
by a selected job in the pool or subsystem.</dd>
|
||
|
|
<dt class="dlterm">Job Name</dt>
|
||
|
|
<dd>(Component, Transaction, Job Interval, Batch Job Trace) Name of the job.
|
||
|
|
In the Job Summary Report of the Transaction Report, a job (identical job
|
||
|
|
name, user name, and job number) appears multiple times in this list if the
|
||
|
|
job uses the system <span class="cmdname">Reroute Job (RRTJOB)</span> command.</dd>
|
||
|
|
<dt class="dlterm">Job Number</dt>
|
||
|
|
<dd>(Component, Transaction, Job Interval, Batch Job Trace) The number of
|
||
|
|
the job which the summary line describes. In the Transaction Report, an asterisk
|
||
|
|
(*) before the job number indicates the job signed on during the measurement
|
||
|
|
period. An asterisk (*) after the job number indicates the job signed off
|
||
|
|
during the measurement period.</dd>
|
||
|
|
<dt class="dlterm">Job Pty</dt>
|
||
|
|
<dd>(Batch Job Trace) Priority of the job.</dd>
|
||
|
|
<dt class="dlterm">Job Set</dt>
|
||
|
|
<dd>(Transaction) The number of job sets is the number of batch jobs that
|
||
|
|
could be active at any time during the trace period. If two jobs run sequentially,
|
||
|
|
they show up as two jobs in the same job set. If two jobs run concurrently,
|
||
|
|
they show up in two different job sets.</dd>
|
||
|
|
<dt class="dlterm">Job Type</dt>
|
||
|
|
<dd>(All Reports except where noted for the Transaction Report) Job type and
|
||
|
|
subtype. Possible job type values include the following: <dl><dt class="dlterm">A</dt>
|
||
|
|
<dd>Autostart</dd>
|
||
|
|
<dt class="dlterm">B</dt>
|
||
|
|
<dd>Batch</dd>
|
||
|
|
<dt class="dlterm">BD</dt>
|
||
|
|
<dd>Batch immediate (Transaction only)<div class="note"><span class="notetitle">Note:</span> The batch immediate values are
|
||
|
|
shown as BCI on the Work with Active Job display and as BATCHI on the Work
|
||
|
|
with Subsystem Job display.</div>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">BE</dt>
|
||
|
|
<dd>Batch evoke (Transaction only)</dd>
|
||
|
|
<dt class="dlterm">BJ</dt>
|
||
|
|
<dd>Batch pre-start job (Transaction only)</dd>
|
||
|
|
<dt class="dlterm">C</dt>
|
||
|
|
<dd>Programmable workstation application server, which includes 5250 emulation
|
||
|
|
over APPC and <span class="keyword">iSeries™</span> Access
|
||
|
|
host servers running either APPC or TCP/IP. A job is reported as a <span class="keyword">iSeries</span> Access server if any of the
|
||
|
|
following items are true: <ul><li>Incoming APPC evoke requests one of the server program names. This also
|
||
|
|
applies to the pre-started jobs for the QSERVER, QCMN, and QSYSWRK subsystems
|
||
|
|
that are already waiting for the named program.</li>
|
||
|
|
<li>Incoming IP port number corresponds to one of the service name-description-port-numbers.
|
||
|
|
This also applies to the pre-started jobs for the QSERVER, QCMN, and QSYSWRK
|
||
|
|
subsystems that are already waiting for the assigned IP port number.</li>
|
||
|
|
<li>Incoming IPX socket number corresponds to one of the service name-description-port-numbers.
|
||
|
|
This also applies to the pre-started jobs for the QSERVER, QCMN, and QSYSWRK
|
||
|
|
subsystems that are already waiting for the assigned IPX port number.</li>
|
||
|
|
<li>Incoming 5250 display emulation jobs that come from APPC data streams
|
||
|
|
sent by 5250 emulation under OS/2<sup>®</sup> Communications Manager or WARP equivalent.</li>
|
||
|
|
</ul>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">D</dt>
|
||
|
|
<dd>Target distributed data management (DDM) server</dd>
|
||
|
|
<dt class="dlterm">I</dt>
|
||
|
|
<dd>Interactive. Interactive includes twinaxial data link control (TDLC),
|
||
|
|
5250 remote workstation, and 3270 remote workstation. For the Transaction
|
||
|
|
Report, this includes twinaxial data link control (TDLC), 5250 remote workstation,
|
||
|
|
3270 remote workstation, SNA pass-through, and 5250 Telnet.</dd>
|
||
|
|
<dt class="dlterm">L</dt>
|
||
|
|
<dd>Licensed Internal Code task</dd>
|
||
|
|
<dt class="dlterm">M</dt>
|
||
|
|
<dd>Subsystem monitor</dd>
|
||
|
|
<dt class="dlterm">P</dt>
|
||
|
|
<dd>SNA pass-through and 5250 Telnet pass-through. On the Transaction Report,
|
||
|
|
these jobs appear as I (interactive).</dd>
|
||
|
|
<dt class="dlterm">R</dt>
|
||
|
|
<dd>Spool reader</dd>
|
||
|
|
<dt class="dlterm">S</dt>
|
||
|
|
<dd>System</dd>
|
||
|
|
<dt class="dlterm">W</dt>
|
||
|
|
<dd>Spool writer, which includes the spool write job, and if Advanced
|
||
|
|
Function Printing™ (AFP™) is specified, the print driver job.</dd>
|
||
|
|
<dt class="dlterm">WP</dt>
|
||
|
|
<dd>Spool print driver (Transaction only)</dd>
|
||
|
|
<dt class="dlterm">X</dt>
|
||
|
|
<dd>Start system job</dd>
|
||
|
|
</dl>
|
||
|
|
<p>Possible job subtype values include the following:</p>
|
||
|
|
<dl><dt class="dlterm">D</dt>
|
||
|
|
<dd>Batch immediate job</dd>
|
||
|
|
<dt class="dlterm">E</dt>
|
||
|
|
<dd>Evoke (communications batch)</dd>
|
||
|
|
<dt class="dlterm">J</dt>
|
||
|
|
<dd>Pre-start job</dd>
|
||
|
|
<dt class="dlterm">P</dt>
|
||
|
|
<dd>Print driver job</dd>
|
||
|
|
<dt class="dlterm">T</dt>
|
||
|
|
<dd>Multiple requester terminal (MRT) (System/36™ environment only)</dd>
|
||
|
|
<dt class="dlterm">3</dt>
|
||
|
|
<dd>System/36</dd>
|
||
|
|
</dl>
|
||
|
|
<p>Noninteractive job types include:</p>
|
||
|
|
<ul><li>Autostart</li>
|
||
|
|
<li>Batch</li>
|
||
|
|
<li>Evoke</li>
|
||
|
|
<li><span class="keyword">iSeries</span> Access-Bch</li>
|
||
|
|
<li>Server </li>
|
||
|
|
<li>Spool</li>
|
||
|
|
<li>Distributed data management (DDM) server</li>
|
||
|
|
</ul>
|
||
|
|
Special interactive job categories include: <ul><li>Interactive</li>
|
||
|
|
<li>Multiple requester terminal (MRT)</li>
|
||
|
|
<li>Pass-through</li>
|
||
|
|
<li>System/36</li>
|
||
|
|
</ul>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Jobs</dt>
|
||
|
|
<dd>(System, Component, Transaction, Pool Interval, Job Interval) The jobs
|
||
|
|
you specify. The format of the entries is <samp class="codeph">jobnumber/username/jobname</samp>.
|
||
|
|
For the Report Selection Criteria report, it is the list of jobs selected
|
||
|
|
to be included (SLTJOB parameter) or excluded (OMTJOB parameter). This does
|
||
|
|
not include jobs selected by using the STLFCNARA or OMTFCNARA parameter.</dd>
|
||
|
|
<dt class="dlterm">K per I/O</dt>
|
||
|
|
<dd>(System, Resource Interval) The average number of kilobytes (1024 bytes)
|
||
|
|
read or written for each disk I/O operation.</dd>
|
||
|
|
<dt class="dlterm">K/T /Tns Sec</dt>
|
||
|
|
<dd>(Transaction) The average delay time, or time spent keying and thinking
|
||
|
|
between transactions for the job, in seconds. The value represents the time
|
||
|
|
interval between active-to-wait and wait-to-active or wait-to-ineligible job
|
||
|
|
state transitions.</dd>
|
||
|
|
<dt class="dlterm">KB per I/O Read</dt>
|
||
|
|
<dd>(Resource Interval) The average number of kilobytes (1 KB equals 1024
|
||
|
|
bytes) transferred per read operation.</dd>
|
||
|
|
<dt class="dlterm">KB per I/O Write</dt>
|
||
|
|
<dd>(Resource Interval) The average number of kilobytes (1024 bytes) transferred
|
||
|
|
per write operation.</dd>
|
||
|
|
<dt class="dlterm">KB Received/Second</dt>
|
||
|
|
<dd>(System, Component) The total number of kilobytes (1024) received per
|
||
|
|
second on the specified interface when it was active on the selected intervals,
|
||
|
|
which includes framing characters.</dd>
|
||
|
|
<dt class="dlterm">KB Transmitted/Second</dt>
|
||
|
|
<dd>(System, Component) The total number of kilobytes (1024) transmitted per
|
||
|
|
second from the specified interface when it was active on the selected intervals,
|
||
|
|
which includes framing characters.</dd>
|
||
|
|
<dt class="dlterm">KBytes Transmitted IOP</dt>
|
||
|
|
<dd>(Component, Resource Interval) Total kilobytes transmitted from an IOP
|
||
|
|
to the system across the bus.</dd>
|
||
|
|
<dt class="dlterm">KBytes Transmitted System</dt>
|
||
|
|
<dd>(Component, Resource Interval) Total kilobytes transmitted to the IOP
|
||
|
|
from the system across the bus.</dd>
|
||
|
|
<dt class="dlterm">Key/Think</dt>
|
||
|
|
<dd>(Transaction) The amount of time spent waiting for the work station user
|
||
|
|
by the program.</dd>
|
||
|
|
<dt class="dlterm">Key/Think /Tns</dt>
|
||
|
|
<dd>(Transaction) The average think time and keying time (or the delay time
|
||
|
|
between transaction boundaries), in seconds, for the interactive jobs.</dd>
|
||
|
|
<dt class="dlterm">L</dt>
|
||
|
|
<dd>(Lock) Whether this is a lock or seize conflict. The column contains an
|
||
|
|
L if lock, blank if seize.</dd>
|
||
|
|
<dt class="dlterm">LAPD Pct Frames Recd in Error</dt>
|
||
|
|
<dd>(Resource Interval) The percentage of frames received in error (applies
|
||
|
|
to D-channel only). Errors can occur when the host system has an error or
|
||
|
|
cannot process received data fast enough.</dd>
|
||
|
|
<dt class="dlterm">LAPD Pct Frames Trnsmitd Again</dt>
|
||
|
|
<dd>(Resource Interval) The percentage of frames retransmitted due to error
|
||
|
|
(applies to D-channel only).</dd>
|
||
|
|
<dt class="dlterm">LAPD Total Frames Recd</dt>
|
||
|
|
<dd>(Resource Interval) The total number of frames received including frames
|
||
|
|
with errors and frames that are not valid (applies to D-channel only).</dd>
|
||
|
|
<dt class="dlterm">LAPD Total Frames Trnsmitd</dt>
|
||
|
|
<dd>(Resource Interval) The total number of frames transmitted (applies to
|
||
|
|
D-channel only).</dd>
|
||
|
|
<dt class="dlterm">Last 4 Programs in Invocation Stack</dt>
|
||
|
|
<dd>(Transaction) The last four programs in the program stack. For example,
|
||
|
|
at the start of a transaction (such as when the work station operator presses
|
||
|
|
the Enter key), you see the program names QT3REQIO, QWSGET, and the program
|
||
|
|
that issued a read operation. At the end of the transaction (such as when
|
||
|
|
the program writes to the display), you see QT3REQIO, QWSPUT, and the program
|
||
|
|
that wrote the display. Usually, the third or fourth program in the stack
|
||
|
|
is the program shown in the transaction summary PGMNAME data. However, if
|
||
|
|
the <var class="varname">Wait Code</var> column has a value, the program in the column
|
||
|
|
labeled <var class="varname">Last</var> is the one that caused the trace record. If
|
||
|
|
there is no program name in a column, the program name was the same as the
|
||
|
|
previous one in the column, and the name is omitted.</dd>
|
||
|
|
<dt class="dlterm">Length of Wait</dt>
|
||
|
|
<dd>(Lock) The number of milliseconds the requester waited for the locked
|
||
|
|
object.</dd>
|
||
|
|
<dt class="dlterm">Lgl I/O /Sec</dt>
|
||
|
|
<dd>(Job Interval) The average number of logical disk I/O operations performed
|
||
|
|
per second by the job during the interval. This is calculated from the logical
|
||
|
|
disk I/O count divided by the elapsed time.</dd>
|
||
|
|
<dt class="dlterm">Library</dt>
|
||
|
|
<dd>(System, Transaction) The library that contains the object.</dd>
|
||
|
|
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />LIBRARY<img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />(Job Trace) The library name that contains the program associated with
|
||
|
|
the trace entry.<img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm">Line Count</dt>
|
||
|
|
<dd>(Job Interval) The number of lines printed by the selected noninteractive
|
||
|
|
jobs during the interval.</dd>
|
||
|
|
<dt class="dlterm">Line Descriptn</dt>
|
||
|
|
<dd>(Resource Interval) Line description name.</dd>
|
||
|
|
<dt class="dlterm">Line Errors</dt>
|
||
|
|
<dd>(Resource Interval) The total of all detected errors. Check the condition
|
||
|
|
of the line if this value increases greatly over time.</dd>
|
||
|
|
<dt class="dlterm">Line Speed</dt>
|
||
|
|
<dd>(System, Resource Interval) The line speed in kilobits (1 kilobit = 1000
|
||
|
|
bits) per second.</dd>
|
||
|
|
<dt class="dlterm">Line Type/Line Name</dt>
|
||
|
|
<dd>(Component, System) The type and name of the line description that is
|
||
|
|
used by the interface. For interfaces that do not use a line descriptions,
|
||
|
|
the Line Name field will be shown as *LOOPBACK, *OPC, or *VIRTUALIP with no
|
||
|
|
Line Type specified.</dd>
|
||
|
|
<dt class="dlterm">Line Util</dt>
|
||
|
|
<dd>(Resource Interval) The percent of available line capacity used by transmit
|
||
|
|
and receive operations.</dd>
|
||
|
|
<dt class="dlterm">LKRL</dt>
|
||
|
|
<dd>(Transaction) Lock Released. The job released a lock it had on the object
|
||
|
|
named on the next detail line of the report (OBJECT --). The job that was
|
||
|
|
waiting for the object is named on this line (WAITER --) along with the amount
|
||
|
|
of time the job spent waiting for the lock to be released.</dd>
|
||
|
|
<dt class="dlterm">LKW</dt>
|
||
|
|
<dd>(Transaction) Listed in the Wait Code column, Lock Wait. If there are
|
||
|
|
a number of these, or you see entries with a significant length of time in
|
||
|
|
the ACTIVE/RSP* column, additional analysis is necessary. The LKWT report
|
||
|
|
lines that precede this LKW report line show you what object is being waited
|
||
|
|
on, and who has the object.</dd>
|
||
|
|
<dt class="dlterm">LKWT</dt>
|
||
|
|
<dd>(Transaction) Listed in the Wait Code column, Lock Conflict Wait. The
|
||
|
|
job is waiting on a lock conflict. The time (*/ time /*) is the duration of
|
||
|
|
the lock conflict and, though not equal to the LKW time, should be very close
|
||
|
|
to it. The holder of the lock is named at the right of the report line (HOLDER
|
||
|
|
--). The object being locked is named on the next report line (OBJECT --).</dd>
|
||
|
|
<dt class="dlterm">Local End Code Violation</dt>
|
||
|
|
<dd>(Resource Interval) The number of times an unintended code violation was
|
||
|
|
detected by the terminal equipment (TE) for frames received at the interface
|
||
|
|
for the ISDN S/T reference point.</dd>
|
||
|
|
<dt class="dlterm">Local Not Ready</dt>
|
||
|
|
<dd>(Resource Interval) The percent of all receive-not-ready frames that were
|
||
|
|
transmitted by the host system. A large percentage often means the host cannot
|
||
|
|
process data fast enough (congestion).</dd>
|
||
|
|
<dt class="dlterm">Local work station IOP utilization</dt>
|
||
|
|
<dd>The fraction of the time interval the work station I/O processors are
|
||
|
|
busy.</dd>
|
||
|
|
<dt class="dlterm">Local work station IOPs</dt>
|
||
|
|
<dd>(System) The resource name and model number for each local workstation
|
||
|
|
IOP.</dd>
|
||
|
|
<dt class="dlterm">Lock Conflict</dt>
|
||
|
|
<dd>(Component) Number of lock exceptions per second. Database record contention
|
||
|
|
is reflected in this count. For more information, issue the <span class="cmdname">Start
|
||
|
|
Performance Trace (STRPFRTRC)</span> command and use the <span class="cmdname">Print
|
||
|
|
Transaction Report (PRTTNSRPT)</span> and <span class="cmdname">Print Lock Report (PRTLCKRPT)</span> commands.
|
||
|
|
This count could be very high, even under normal system operation. Use the
|
||
|
|
count as a monitor. If there are large variations or changes, explore these
|
||
|
|
variations in more detail.</dd>
|
||
|
|
<dt class="dlterm">Lock Wait /Tns</dt>
|
||
|
|
<dd>(Transaction) The average time, in seconds, of the lock-wait time per
|
||
|
|
transaction. If the value is high, investigate with the transaction detail
|
||
|
|
calculation and the <span class="cmdname">Print Lock Report (PRTLCKRPT)</span> command.</dd>
|
||
|
|
<dt class="dlterm">Logical</dt>
|
||
|
|
<dd>(Job Interval) The number of logical disk I/O operations performed by
|
||
|
|
the selected interactive jobs during the interval.</dd>
|
||
|
|
<dt class="dlterm">Logical Database I/O Other</dt>
|
||
|
|
<dd>(System) Other logical database operations per transaction. This includes
|
||
|
|
operations such as update and delete.</dd>
|
||
|
|
<dt class="dlterm">Logical Database I/O Read</dt>
|
||
|
|
<dd>(System) Logical database read operations per transaction.</dd>
|
||
|
|
<dt class="dlterm">Logical Database I/O Write</dt>
|
||
|
|
<dd>(System) Logical database write operations per transaction.</dd>
|
||
|
|
<dt class="dlterm">Logical DB I/O</dt>
|
||
|
|
<dd>(System) Average number of logical I/O operations per transaction.</dd>
|
||
|
|
<dt class="dlterm">Logical DB I/O Count</dt>
|
||
|
|
<dd>(System) Number of times an internal database I/O read, write, or miscellaneous
|
||
|
|
function was called. This does not include I/O operations to readers, writers,
|
||
|
|
or I/O operations caused by the <span class="cmdname">Copy Spooled File (CPYSPLF)</span> command
|
||
|
|
or the <span class="cmdname">Display Spooled File (DSPSPLF)</span> command. If you specify
|
||
|
|
SEQONLY(*YES), you see numbers that show each block of records read or written,
|
||
|
|
not the number of individual records read or written. Miscellaneous functions
|
||
|
|
include the following: updates, deletes, force-end-of-data, and releases.</dd>
|
||
|
|
<dt class="dlterm">Logical Disk I/O</dt>
|
||
|
|
<dd>(Component) Number of logical disk operations (Get, Put, Update, Other).</dd>
|
||
|
|
<dt class="dlterm">Logical I/O /Second</dt>
|
||
|
|
<dd>(System) Average number of logical disk I/O operations per second.</dd>
|
||
|
|
<dt class="dlterm">Logical I/O Per Second</dt>
|
||
|
|
<dd>(Job Interval) The average number of logical disk I/O operations performed
|
||
|
|
per second by the selected noninteractive jobs during the interval.</dd>
|
||
|
|
<dt class="dlterm">Long Wait</dt>
|
||
|
|
<dd>(Transaction) The time the job spent waiting for a system resource. An
|
||
|
|
example of a long wait would be a record-lock conflict. Also listed in the
|
||
|
|
Elapsed Time--Seconds column, it is the elapsed time in the state (such as
|
||
|
|
waiting for the next transaction or lock-wait time).</dd>
|
||
|
|
<dt class="dlterm">Long Wait Lck/Oth</dt>
|
||
|
|
<dd>(Transaction) The amount of time the job spent waiting for a system resource.
|
||
|
|
An example of a long wait would be a record-lock conflict.</dd>
|
||
|
|
<dt class="dlterm">Loss of Frame Alignment</dt>
|
||
|
|
<dd>(Resource Interval) The number of times a time period equivalent to two
|
||
|
|
48-bit frames elapsed without detecting valid pairs of line code violations.</dd>
|
||
|
|
<dt class="dlterm">MAC Errors</dt>
|
||
|
|
<dd>(Resource Interval) The number of medium access control (MAC) errors.</dd>
|
||
|
|
<dt class="dlterm">Main storage (MB)</dt>
|
||
|
|
<dd>(System) The total main storage size, as measured in megabytes. These
|
||
|
|
codes are in the wait code column, but they are not wait codes. They indicate
|
||
|
|
transaction boundary trace records.</dd>
|
||
|
|
<dt class="dlterm">Max Util</dt>
|
||
|
|
<dd>(System) Consistent use at or above the threshold value given will affect
|
||
|
|
system performance and cause longer response times or less throughput.</dd>
|
||
|
|
<dt class="dlterm">Maximum</dt>
|
||
|
|
<dd>(Transaction) The maximum value of the item that occurred in the column.</dd>
|
||
|
|
<dt class="dlterm">Member</dt>
|
||
|
|
<dd>(System, Transaction) For the System Report, this is the name of the performance
|
||
|
|
data member that was specified on the TOMBR parameter of the <span class="cmdname">Create
|
||
|
|
Performance Data (CRTPFRDTA)</span> command. For the Transaction Report,
|
||
|
|
the member that was involved in the conflict.</dd>
|
||
|
|
<dt class="dlterm">Minimum</dt>
|
||
|
|
<dd>(Transaction) The minimum value of the item that occurred in the column.</dd>
|
||
|
|
<dt class="dlterm">MRT Max Time</dt>
|
||
|
|
<dd>(System) The time spent waiting, after MRTMAX is reached, by jobs routed
|
||
|
|
to a multiple requester terminal.<div class="note"><span class="notetitle">Note:</span> No value appears in this column if
|
||
|
|
job type is not MRT.</div>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />MSGS<img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />(Job Trace) The number of messages sent to the job during each transaction.<img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm">MTU size (bytes)</dt>
|
||
|
|
<dd>(System) The size of the largest datagram that can be sent or received
|
||
|
|
on the interface. The size is specified in octets (bytes). For interfaces
|
||
|
|
that are used for transmitting network datagrams, this is the size of the
|
||
|
|
largest network datagram that can be sent on the interface.</dd>
|
||
|
|
<dt class="dlterm">Nbr A-I</dt>
|
||
|
|
<dd>(Transaction) The number of active-to-ineligible state transitions by
|
||
|
|
the job. This column shows the number of times that the job exceeded the time-slice
|
||
|
|
value assigned to the job, and had to wait for an activity-level slot before
|
||
|
|
the system could begin processing the transaction. If a value appears in this
|
||
|
|
column, check the work that the job was doing, and determine if changes to
|
||
|
|
the time-slice value are necessary.</dd>
|
||
|
|
<dt class="dlterm">Nbr Evt</dt>
|
||
|
|
<dd>(Transaction) The number of event waits that occurred during the job processing.</dd>
|
||
|
|
<dt class="dlterm">Nbr Jobs</dt>
|
||
|
|
<dd>(Transaction) The number of jobs.</dd>
|
||
|
|
<dt class="dlterm">Nbr Sign offs</dt>
|
||
|
|
<dd>(Transaction) The number of jobs that signed off during the interval.</dd>
|
||
|
|
<dt class="dlterm">Nbr Sign ons</dt>
|
||
|
|
<dd>(Transaction) The number of jobs that signed on during the interval.</dd>
|
||
|
|
<dt class="dlterm">Nbr Tns</dt>
|
||
|
|
<dd>(Transaction) The number of transactions in a given category. <div class="note"><span class="notetitle">Note:</span> The
|
||
|
|
values for transaction counts and other transaction-related information shown
|
||
|
|
on the reports you produce using the <span class="cmdname">Print Transaction Report (PRTTNSRPT)</span> command
|
||
|
|
may vary from the values shown on the reports you produce using the <span class="cmdname">Print
|
||
|
|
System Report (PRTSYSRPT)</span> and <span class="cmdname">Print Component Report (PRTCPTRPT)</span> commands.
|
||
|
|
These differences are caused because the PRTTNSRPT command uses trace data
|
||
|
|
as input, while the PRTSYSRPT and PRTCPTRPT commands use sample data as input.</div>
|
||
|
|
<p>If
|
||
|
|
there are significant differences in the values for transaction-related information
|
||
|
|
shown on these reports, do not use the data until you investigate why these
|
||
|
|
differences exist.</p>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Nbr W-I</dt>
|
||
|
|
<dd>(Transaction) The number of wait-to-ineligible state transitions by the
|
||
|
|
job. This column shows how many times the job had to wait for a transaction.</dd>
|
||
|
|
<dt class="dlterm">NDB Read</dt>
|
||
|
|
<dd>(Transaction) Listed in Physical I/O Counts column, it is the number of
|
||
|
|
nondatabase read requests while the job was in that state. Listed in the Sync
|
||
|
|
Disk I/O Rqs/Tns column, it is the average number of synchronous nondatabase
|
||
|
|
read requests per transaction.</dd>
|
||
|
|
<dt class="dlterm">NDB Write</dt>
|
||
|
|
<dd>(Transaction) Listed in the Sync Disk I/O Rqs/Tns column, it is the average
|
||
|
|
number of synchronous nondatabase write requests per transaction.</dd>
|
||
|
|
<dt class="dlterm">NDB Wrt</dt>
|
||
|
|
<dd>(Transaction) Listed in Physical I/O Counts column, the number of nondatabase
|
||
|
|
write requests while the job was in that state. Listed under Synchronous Disk
|
||
|
|
I/O Counts column, it is the number of synchronous nondatabase write requests
|
||
|
|
per transaction.</dd>
|
||
|
|
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />NON-DB<img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />(Job Trace) The number of physical nondatabase reads that occurred for
|
||
|
|
the entry.<img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm">Non-DB Fault</dt>
|
||
|
|
<dd>(System, Component) Average number of nondatabase faults per second.</dd>
|
||
|
|
<dt class="dlterm">Non-DB Pages</dt>
|
||
|
|
<dd>(System, Component) Average number of nondatabase pages read per second.</dd>
|
||
|
|
<dt class="dlterm">NON-DB RDS</dt>
|
||
|
|
<dd>(Job Trace) The number of physical nondatabase reads that occurred.</dd>
|
||
|
|
<dt class="dlterm">Non SMAPP</dt>
|
||
|
|
<dd>(Component) Journal deposits not directly related to SMAPP (System Managed
|
||
|
|
Access Path Protection).</dd>
|
||
|
|
<dt class="dlterm">Non-SSL Inbound Connect</dt>
|
||
|
|
<dd>(System) The number of non-SSL inbound connections accepted by the server.</dd>
|
||
|
|
<dt class="dlterm">Non-Unicast Packets Received</dt>
|
||
|
|
<dd>(System) The total number of non-unicast packets delivered to a higher-layer
|
||
|
|
protocol for packets received on the specified interface.</dd>
|
||
|
|
<dt class="dlterm">Non-Unicast Packets Sent</dt>
|
||
|
|
<dd>(System) The total number of packets that higher-level protocols requested
|
||
|
|
to be transmitted to a non-unicast address; therefore, this number includes
|
||
|
|
those packets that were discarded or were not sent as well as those packets
|
||
|
|
that were sent.</dd>
|
||
|
|
<dt class="dlterm">Number</dt>
|
||
|
|
<dd>(Transaction) The number of the job with which the transaction is associated.</dd>
|
||
|
|
<dt class="dlterm">Number I/Os per Second</dt>
|
||
|
|
<dd>(System) The number of I/Os per second for this particular IOP.</dd>
|
||
|
|
<dt class="dlterm">Number Jobs</dt>
|
||
|
|
<dd>(Transaction) The number of batch jobs in the job set.</dd>
|
||
|
|
<dt class="dlterm">Number Lck Cft</dt>
|
||
|
|
<dd>(Transaction) The number of lock-wait (including database record lock)
|
||
|
|
state conflicts that occurred during the job processing. If this number is
|
||
|
|
high, look at the Transaction and Transition Reports for the job to see how
|
||
|
|
long the lock-wait state conflicts were lasting. In addition, you can do further
|
||
|
|
investigation using the reports produced when you use the <span class="cmdname">Print Lock
|
||
|
|
Report (PRTLCKRPT)</span> command.</dd>
|
||
|
|
<dt class="dlterm">Number Lck Conflict</dt>
|
||
|
|
<dd>(Transaction) The number of times the job had a lock conflict.</dd>
|
||
|
|
<dt class="dlterm">Number Locks</dt>
|
||
|
|
<dd>(Transaction) The number of locks attributed to interactive or noninteractive
|
||
|
|
waiters.</dd>
|
||
|
|
<dt class="dlterm">Number of batch jobs</dt>
|
||
|
|
<dd>(System) The average number of active batch jobs. A batch job is considered
|
||
|
|
active if it averages at least one I/O per 5 minutes.</dd>
|
||
|
|
<dt class="dlterm">Number of Jobs</dt>
|
||
|
|
<dd>(System) Number of jobs.</dd>
|
||
|
|
<dt class="dlterm">Number of Packets Received with Errors</dt>
|
||
|
|
<dd>(System) The total number of packets that were received with errors or
|
||
|
|
discarded for other reasons. For example, a packet could be discarded to free
|
||
|
|
up buffer space.</dd>
|
||
|
|
<dt class="dlterm">Number Seizes</dt>
|
||
|
|
<dd>(Transaction) The number of seizes attributed to interactive or noninteractive
|
||
|
|
waiters.</dd>
|
||
|
|
<dt class="dlterm">Number Sze Cft</dt>
|
||
|
|
<dd>(Transaction) The number of seize/lock conflicts that occurred during
|
||
|
|
the job processing. If this number is high, look at the Transaction and Transition
|
||
|
|
Reports for the job to see how long the conflicts lasted, the qualified name
|
||
|
|
of the job that held the object, the name and type of object being held, and
|
||
|
|
what the job was waiting for.</dd>
|
||
|
|
<dt class="dlterm">Number Sze Conflict</dt>
|
||
|
|
<dd>(Transaction) The number of times the job had a seize conflict.</dd>
|
||
|
|
<dt class="dlterm">Number Tns</dt>
|
||
|
|
<dd>(System, Transaction) Total number of transactions processed. For example,
|
||
|
|
in the System Report it is the total number of transactions processed by jobs
|
||
|
|
in this pool. In the Transaction Report it is the number of transactions associated
|
||
|
|
with the program.</dd>
|
||
|
|
<dt class="dlterm">Number Traces</dt>
|
||
|
|
<dd>(Batch Job Trace) Number of traces.</dd>
|
||
|
|
<dt class="dlterm">Number Transactions</dt>
|
||
|
|
<dd>(System) Total number of transactions processed.</dd>
|
||
|
|
<dt class="dlterm">Object File</dt>
|
||
|
|
<dd>(Transaction) The file that contains the object.</dd>
|
||
|
|
<dt class="dlterm">Object Library</dt>
|
||
|
|
<dd>(Transaction) The library that contains the object.</dd>
|
||
|
|
<dt class="dlterm">Object Member</dt>
|
||
|
|
<dd>(Transaction) The member that was involved in the conflict.</dd>
|
||
|
|
<dt class="dlterm">Object Name</dt>
|
||
|
|
<dd>(Lock) The name of the locked object.</dd>
|
||
|
|
<dt class="dlterm">Object RRN</dt>
|
||
|
|
<dd>(Transaction) The relative record number of the record involved in the
|
||
|
|
conflict.</dd>
|
||
|
|
<dt class="dlterm">Object Type</dt>
|
||
|
|
<dd>(Transaction, Lock) The type of the locked object. The following are possible
|
||
|
|
object types: <dl><dt class="dlterm">AG</dt>
|
||
|
|
<dd>Access group</dd>
|
||
|
|
<dt class="dlterm">CB</dt>
|
||
|
|
<dd>Commit block</dd>
|
||
|
|
<dt class="dlterm">CBLK</dt>
|
||
|
|
<dd>Commit block</dd>
|
||
|
|
<dt class="dlterm">CD</dt>
|
||
|
|
<dd>Controller description</dd>
|
||
|
|
<dt class="dlterm">CLS</dt>
|
||
|
|
<dd>Class</dd>
|
||
|
|
<dt class="dlterm">CMD</dt>
|
||
|
|
<dd>Command</dd>
|
||
|
|
<dt class="dlterm">CTLD</dt>
|
||
|
|
<dd>Controller description</dd>
|
||
|
|
<dt class="dlterm">CTX</dt>
|
||
|
|
<dd>Context</dd>
|
||
|
|
<dt class="dlterm">CUD</dt>
|
||
|
|
<dd>Control unit description</dd>
|
||
|
|
<dt class="dlterm">CUR</dt>
|
||
|
|
<dd>Cursor</dd>
|
||
|
|
<dt class="dlterm">DEVD</dt>
|
||
|
|
<dd>Device description</dd>
|
||
|
|
<dt class="dlterm">DS</dt>
|
||
|
|
<dd>Data space</dd>
|
||
|
|
<dt class="dlterm">DSI</dt>
|
||
|
|
<dd>Data space index</dd>
|
||
|
|
<dt class="dlterm">DTAARA</dt>
|
||
|
|
<dd>Data area</dd>
|
||
|
|
<dt class="dlterm">EDTD</dt>
|
||
|
|
<dd>Edit description</dd>
|
||
|
|
<dt class="dlterm">FILE</dt>
|
||
|
|
<dd>File</dd>
|
||
|
|
<dt class="dlterm">JOBD</dt>
|
||
|
|
<dd>Job description</dd>
|
||
|
|
<dt class="dlterm">JOBQ</dt>
|
||
|
|
<dd>Job queue</dd>
|
||
|
|
<dt class="dlterm">JP</dt>
|
||
|
|
<dd>Journal port</dd>
|
||
|
|
<dt class="dlterm">JRN</dt>
|
||
|
|
<dd>Journal</dd>
|
||
|
|
<dt class="dlterm">JRNRCV</dt>
|
||
|
|
<dd>Journal receiver</dd>
|
||
|
|
<dt class="dlterm">JS</dt>
|
||
|
|
<dd>Journal space</dd>
|
||
|
|
<dt class="dlterm">LIB</dt>
|
||
|
|
<dd>Library</dd>
|
||
|
|
<dt class="dlterm">LIND</dt>
|
||
|
|
<dd>Line description</dd>
|
||
|
|
<dt class="dlterm">LUD</dt>
|
||
|
|
<dd>Logical unit description</dd>
|
||
|
|
<dt class="dlterm">MBR</dt>
|
||
|
|
<dd>Member</dd>
|
||
|
|
<dt class="dlterm">MEM</dt>
|
||
|
|
<dd>Database file member</dd>
|
||
|
|
<dt class="dlterm">MSGF</dt>
|
||
|
|
<dd>Message file</dd>
|
||
|
|
<dt class="dlterm">MSGQ</dt>
|
||
|
|
<dd>Message queue</dd>
|
||
|
|
<dt class="dlterm">ND</dt>
|
||
|
|
<dd>Network description</dd>
|
||
|
|
<dt class="dlterm">OCUR</dt>
|
||
|
|
<dd>Database operational cursor</dd>
|
||
|
|
<dt class="dlterm">OUTQ</dt>
|
||
|
|
<dd>Output queue</dd>
|
||
|
|
<dt class="dlterm">PGM</dt>
|
||
|
|
<dd>Program</dd>
|
||
|
|
<dt class="dlterm">PROG</dt>
|
||
|
|
<dd>Program</dd>
|
||
|
|
<dt class="dlterm">PRTIMG</dt>
|
||
|
|
<dd>Print image</dd>
|
||
|
|
<dt class="dlterm">QDAG</dt>
|
||
|
|
<dd>Composite piece - access group</dd>
|
||
|
|
<dt class="dlterm">QDDS</dt>
|
||
|
|
<dd>Composite piece - data space</dd>
|
||
|
|
<dt class="dlterm">QDDSI</dt>
|
||
|
|
<dd>Composite piece - data space index</dd>
|
||
|
|
<dt class="dlterm">QTAG</dt>
|
||
|
|
<dd>Temporary - access group</dd>
|
||
|
|
<dt class="dlterm">QTDS</dt>
|
||
|
|
<dd>Temporary - data space</dd>
|
||
|
|
<dt class="dlterm">QTDSI</dt>
|
||
|
|
<dd>Temporary - data space index</dd>
|
||
|
|
<dt class="dlterm">SBSD</dt>
|
||
|
|
<dd>Subsystem description</dd>
|
||
|
|
<dt class="dlterm">TBL</dt>
|
||
|
|
<dd>Table</dd>
|
||
|
|
</dl>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Omit Parameters</dt>
|
||
|
|
<dd>(System, Component, Transaction, Job Interval, Pool Interval) The criteria
|
||
|
|
used to choose the data records to be excluded from the report. The criteria
|
||
|
|
are generally specified using an OMTxxx parameter of the command. Only nondefault
|
||
|
|
values (something other than *NONE) are printed. If a parameter was not specified,
|
||
|
|
it does not appear on the report.</dd>
|
||
|
|
<dt class="dlterm">Op per Second</dt>
|
||
|
|
<dd>(System) Average number of disk operations per second.</dd>
|
||
|
|
<dt class="dlterm">Other Wait /Tns</dt>
|
||
|
|
<dd>(Transaction) The average time, in seconds, spent waiting that was not
|
||
|
|
in any of the previous categories per transaction. For example, the time spent
|
||
|
|
waiting during a save/restore operation when the system requested new media
|
||
|
|
(tape or diskette).</dd>
|
||
|
|
<dt class="dlterm">Outgoing Calls Pct Retry</dt>
|
||
|
|
<dd>(Resource Interval) The percentage of outgoing calls that were rejected
|
||
|
|
by the network.</dd>
|
||
|
|
<dt class="dlterm">Outgoing Calls Total</dt>
|
||
|
|
<dd>(Resource Interval) The total number of outgoing call attempts.</dd>
|
||
|
|
<dt class="dlterm">Over commitment ratio</dt>
|
||
|
|
<dd>(System) The main storage over commitment ratio (OCR).</dd>
|
||
|
|
<dt class="dlterm">PAG</dt>
|
||
|
|
<dd>(Transaction) The number of process access group faults.</dd>
|
||
|
|
<dt class="dlterm">PAG Fault</dt>
|
||
|
|
<dd>(Component, Job Interval) In the Exception Occurrence Summary of the Component
|
||
|
|
Report, it is the total number of times the program access group (PAG) was
|
||
|
|
referred to, but was not in main storage. The Licensed Internal Code no longer
|
||
|
|
uses process access groups for caching data. Because of this implementation,
|
||
|
|
the value will always be 0 for more current releases. In the Exception Occurrence
|
||
|
|
Summary of the Component Report, it is the number of faults involving the
|
||
|
|
process access group per second.</dd>
|
||
|
|
<dt class="dlterm">Page Count</dt>
|
||
|
|
<dd>(Job Interval) The number of pages printed by the selected noninteractive
|
||
|
|
jobs during the interval.</dd>
|
||
|
|
<dt class="dlterm">Pct CPU By Categories</dt>
|
||
|
|
<dd>(Transaction) The percentage of available processing unit time used by
|
||
|
|
the transactions that fell into the various categories. See the ANALYSIS by
|
||
|
|
Interactive Transaction Categories part of the System Summary Data Section
|
||
|
|
for an explanation of the categories.</dd>
|
||
|
|
<dt class="dlterm">Pct Data Characters Received in Error</dt>
|
||
|
|
<dd>(Resource Interval) The percent of data characters received with error.</dd>
|
||
|
|
<dt class="dlterm">Pct Data Characters Transmitted in Error</dt>
|
||
|
|
<dd>(Resource Interval) The percent of data characters transmitted with error.</dd>
|
||
|
|
<dt class="dlterm">Pct Datagrams Error</dt>
|
||
|
|
<dd>(Component) The percentage of datagrams that were discarded due to these
|
||
|
|
errors: <ul><li>The IP address in the destination field of the IP header was not a valid
|
||
|
|
address to be received at this entity.</li>
|
||
|
|
<li>The protocol was unknown or unsupported.</li>
|
||
|
|
<li>Not enough buffer space.</li>
|
||
|
|
</ul>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Pct Error Responses</dt>
|
||
|
|
<dd>(Component) Percentage of responses in error.</dd>
|
||
|
|
<dt class="dlterm">Pct Ex-Wt /Rsp</dt>
|
||
|
|
<dd>(Transaction) The percentage of the response time that is due to exceptional
|
||
|
|
wait.</dd>
|
||
|
|
<dt class="dlterm">Pct ICMP Messages Error</dt>
|
||
|
|
<dd>(Component) This is the number of Internet Control Message Protocol (ICMP)
|
||
|
|
messages that the entity received but determined that the messages had errors
|
||
|
|
or are messages that the entity did not send due to problems.</dd>
|
||
|
|
<dt class="dlterm">Pct Of Tns Categories</dt>
|
||
|
|
<dd>(Transaction) The percentage of all transactions that fell into the various
|
||
|
|
categories. See the Analysis by Interactive Transaction Categories part of
|
||
|
|
the System Summary Data Section for an explanation of the categories.</dd>
|
||
|
|
<dt class="dlterm">Pct Packets Received Error</dt>
|
||
|
|
<dd>(System) The percentage of packets that were received with errors or discarded
|
||
|
|
for other reasons. For example, a packet could be discarded to free up buffer
|
||
|
|
space.</dd>
|
||
|
|
<dt class="dlterm">Pct Packets Sent Error</dt>
|
||
|
|
<dd>(System) The percentage of packets that were not sent because of errors
|
||
|
|
or discarded for other reasons. For example, a packet could be discarded to
|
||
|
|
free up buffer space.</dd>
|
||
|
|
<dt class="dlterm">Pct PDUs Received in Error</dt>
|
||
|
|
<dd>(Resource Interval) The percent of protocol data units (PDUs) received
|
||
|
|
in error during the time interval. These errors can occur if the host system
|
||
|
|
has errors or cannot receive data fast enough (congestion). <div class="note"><span class="notetitle">Note:</span> A protocol
|
||
|
|
data unit (PDU) for asynchronous communications is a variable-length unit
|
||
|
|
of data that is ended by a protocol control character or by the size of the
|
||
|
|
buffer.</div>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Pct Poll Retry Time</dt>
|
||
|
|
<dd>(Resource Interval) The percent of the time interval the line was unavailable
|
||
|
|
while the IOP waited for a response from a work station controller (or remote
|
||
|
|
system) that was in disconnect mode. <div class="note"><span class="notetitle">Note:</span> To minimize this lost time:<ul><li>Vary on only the controllers that are turned on.</li>
|
||
|
|
<li>Turn on all controllers.</li>
|
||
|
|
<li>Use the <span class="cmdname">Change Line Description (SDLC) (CHGLINSDLC) </span>command
|
||
|
|
to set the connect poll timer to a small value (reduces wait time).</li>
|
||
|
|
<li>Use the <span class="cmdname">Change Controller Description (CHGCTLxxxx)</span> command
|
||
|
|
(where xxxx is APPC, FNC, RWS, or RTL, as appropriate) to set the NDMPOLLTMR
|
||
|
|
value to a large value (increases time between polls).</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Pct Tns</dt>
|
||
|
|
<dd>(Transaction) The percentage of the total transactions. For the System
|
||
|
|
Summary section of the Job Summary Report, the transactions are within the
|
||
|
|
given trace period with the given purge attribute. For the Interactive Program
|
||
|
|
Transaction Statistics section of the Job Summary Report, the percentage of
|
||
|
|
transactions that were associated with a program. For the Job Statistics section,
|
||
|
|
it is the percentage of total transactions that were due to this job. For
|
||
|
|
the Interactive Program Statistics section, it is all transactions that were
|
||
|
|
associated to a program.</dd>
|
||
|
|
<dt class="dlterm">Pct UDP Datagrams Error</dt>
|
||
|
|
<dd>(Component) The percentage of User Datagram Protocol (UDP) datagrams for
|
||
|
|
which there was no application at the destination port or that could not be
|
||
|
|
delivered for other reasons.</dd>
|
||
|
|
<dt class="dlterm">Percent Errored Seconds</dt>
|
||
|
|
<dd>(Resource Interval) The percentage of seconds in which at least one Detected
|
||
|
|
Access Transmission (DTSE) in or out error occurred.</dd>
|
||
|
|
<dt class="dlterm">Percent Frames Received in Error</dt>
|
||
|
|
<dd>(Resource Interval) The percent of all received frames that were received
|
||
|
|
in error. Errors can occur when the host system has an error or cannot process
|
||
|
|
received data fast enough (congestion).</dd>
|
||
|
|
<dt class="dlterm">Percent Full</dt>
|
||
|
|
<dd>(System) Percentage of disk space capacity in use.</dd>
|
||
|
|
<dt class="dlterm">Percent I Frames Trnsmitd in Error</dt>
|
||
|
|
<dd>(Resource Interval) The percent of transmitted information frames that
|
||
|
|
required retransmission. Retransmissions can occur when a remote device has
|
||
|
|
an error or cannot process received data fast enough (congestion).</dd>
|
||
|
|
<dt class="dlterm">Percent Severely Errored Seconds</dt>
|
||
|
|
<dd>(Resource Interval) The percent of seconds in which at least three Detected
|
||
|
|
Access Transmission (DTSE) in or out errors occurred.</dd>
|
||
|
|
<dt class="dlterm">Percent transactions (dynamic no)</dt>
|
||
|
|
<dd>(System) A measure of system main storage utilization. The percent of
|
||
|
|
all interactive transactions that were done with the purge attribute of dynamic
|
||
|
|
NO.</dd>
|
||
|
|
<dt class="dlterm">Percent transactions (purge no)</dt>
|
||
|
|
<dd>(System) A measure of system main storage utilization. The percent of
|
||
|
|
all interactive transactions that were done with the purge attribute of NO.</dd>
|
||
|
|
<dt class="dlterm">Percent transactions (purge yes)</dt>
|
||
|
|
<dd>(System) A measure of system main storage utilization. The percent of
|
||
|
|
all interactive transactions that were done with the purge attribute of YES.</dd>
|
||
|
|
<dt class="dlterm">Percent Util</dt>
|
||
|
|
<dd>(System) Average disk arm utilization (busy). Consistent use at or above
|
||
|
|
the threshold value provided for disk arm utilization affects system performance,
|
||
|
|
which causes longer response times or less throughput.<div class="note"><span class="notetitle">Note:</span> The percent busy
|
||
|
|
value is calculated from data measured in the I/O processor. When comparing
|
||
|
|
this value with percent busy reported by the <span class="cmdname">Work with Disk Status
|
||
|
|
(WRKDSKSTS)</span> command, some differences may exist. The WRKDSKSTS command
|
||
|
|
estimates percent busy based on the number of I/O requests, amount of data
|
||
|
|
transferred, and type of disk unit.</div>
|
||
|
|
<p>The system-wide average utilization
|
||
|
|
does not include data for mirrored arms in measurement intervals for which
|
||
|
|
such intervals are either in resuming or suspended status.</p>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Perm Size</dt>
|
||
|
|
<dd>(Component) Kilobytes placed within the permanent area; these are traditional
|
||
|
|
journal entries which can be retrieved and displayed.</dd>
|
||
|
|
<dt class="dlterm">Perm Write</dt>
|
||
|
|
<dd>(Component, Job Interval) The number of permanent write operations performed
|
||
|
|
for the selected jobs during the interval.</dd>
|
||
|
|
<dt class="dlterm">Permanent writes per transaction</dt>
|
||
|
|
<dd>(System) The average number of permanent write operations per interactive
|
||
|
|
transaction.</dd>
|
||
|
|
<dt class="dlterm">Physical I/O Count</dt>
|
||
|
|
<dd>(Transaction, Batch Job Trace) For the Job Summary section of the Batch
|
||
|
|
Job Trace Report, the number of synchronous and asynchronous disk operations
|
||
|
|
(reads and writes). For the Transition Report, the next five columns provide
|
||
|
|
information about the number of synchronous and asynchronous disk I/O requests
|
||
|
|
while the job was in the given state. The first line is the synchronous disk
|
||
|
|
I/O requests, and the second line is the asynchronous disk I/O requests. <dl><dt class="dlterm">DB Read</dt>
|
||
|
|
<dd>The number of database read requests while the job was in that state.</dd>
|
||
|
|
<dt class="dlterm">DB Wrt</dt>
|
||
|
|
<dd>The number of database write requests while the job was in that state.</dd>
|
||
|
|
<dt class="dlterm">NDB Read</dt>
|
||
|
|
<dd>The number of nondatabase read requests while the job was in that state.</dd>
|
||
|
|
<dt class="dlterm">NDB Wrt</dt>
|
||
|
|
<dd>The number of nondatabase write requests while the job was in that state.</dd>
|
||
|
|
<dt class="dlterm">Tot</dt>
|
||
|
|
<dd>The total number of DB Read, DB Wrt, NDB Read, and NDB Wrt requests.</dd>
|
||
|
|
</dl>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Physical Writes</dt>
|
||
|
|
<dd>(Component) Physical journal write operations to disk.</dd>
|
||
|
|
<dt class="dlterm">Pl</dt>
|
||
|
|
<dd>(Component, Transaction, Job Interval, Pool Interval) The number of the
|
||
|
|
pool in which the subsystem or job ran.</dd>
|
||
|
|
<dt class="dlterm">Pool</dt>
|
||
|
|
<dd>(Transaction, Job Interval, Batch Job Trace) The number of the pool containing
|
||
|
|
the transaction (for example, in which the job ran.)</dd>
|
||
|
|
<dt class="dlterm">Pool ID</dt>
|
||
|
|
<dd>(System) Pool identifier.</dd>
|
||
|
|
<dt class="dlterm">Pool ID Faults</dt>
|
||
|
|
<dd>(Component) User pool that had the highest page fault rate.</dd>
|
||
|
|
<dt class="dlterm">Pool Mch Faults/Sec</dt>
|
||
|
|
<dd>(Component) Average number of machine pool page faults per second.</dd>
|
||
|
|
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />Pool size (MB)<img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />(Component) For the Storage Pool Activity section of the Component Report
|
||
|
|
it is the initial pool size in megabytes.<img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm">Pool User Faults/Sec</dt>
|
||
|
|
<dd>(Component) Average number of user pool page faults per second, for the
|
||
|
|
user pool with highest fault rate during this interval.</dd>
|
||
|
|
<dt class="dlterm">Pools</dt>
|
||
|
|
<dd>(System, Component, Transaction, Job Interval, Pool Interval) In the Report-Selection
|
||
|
|
Criteria section, the list of pools selected to be included (SLTPOOLS parameter)
|
||
|
|
or excluded (OMTPOOLS parameter). Otherwise, the pools you specify. The values
|
||
|
|
can be from 1 through 64.</dd>
|
||
|
|
<dt class="dlterm">Prg</dt>
|
||
|
|
<dd>(Transaction) The purge attribute of the jobs.</dd>
|
||
|
|
<dt class="dlterm">Printer Lines</dt>
|
||
|
|
<dd>(System, Job Interval) The number of lines printed by the job during the
|
||
|
|
interval.</dd>
|
||
|
|
<dt class="dlterm">Printer Pages</dt>
|
||
|
|
<dd>(System, Job Interval) The number of pages printed by the job during the
|
||
|
|
interval.</dd>
|
||
|
|
<dt class="dlterm">Priority</dt>
|
||
|
|
<dd>(System, Transaction) The priority of the job.</dd>
|
||
|
|
<dt class="dlterm">Program</dt>
|
||
|
|
<dd>(Transaction) The name of the program with which the transaction is associated.</dd>
|
||
|
|
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />PROGRAM<img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />(Job Trace) The name of the program for the entry.<img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />PROGRAM CALL<img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />(Job Trace) The number of non-QSYS library programs called during the
|
||
|
|
step. This is not the number of times that the program named in the PROGRAM
|
||
|
|
NAME field was called.<img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />PROGRAM DATABASE I/O<img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />(Job Trace) The number of times the IBM-supplied database modules were
|
||
|
|
used during the transaction. The database module names have had the QDB prefix
|
||
|
|
removed (PUT instead of QDBPUT). The type of logical I/O operation performed
|
||
|
|
by each is as follows:<dl><dt class="dlterm">GETDR</dt>
|
||
|
|
<dd>Get direct</dd>
|
||
|
|
<dt class="dlterm">GETSQ</dt>
|
||
|
|
<dd>Get sequential</dd>
|
||
|
|
<dt class="dlterm">GETKY</dt>
|
||
|
|
<dd>Get by key</dd>
|
||
|
|
<dt class="dlterm">GETM</dt>
|
||
|
|
<dd>Get multiple</dd>
|
||
|
|
<dt class="dlterm">PUT, PUTM</dt>
|
||
|
|
<dd>Add a record</dd>
|
||
|
|
<dt class="dlterm">UDR</dt>
|
||
|
|
<dd>Update, delete, or release a record</dd>
|
||
|
|
</dl>
|
||
|
|
<img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />PROGRAM INIT<img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />(Job Trace) The number of times that the IBM-supplied initialization program
|
||
|
|
was called during the transaction. For RPG programs this is QRGXINIT, for
|
||
|
|
COBOL it is QCRMAIN. Each time the user program ends with LR (RPG) or END
|
||
|
|
(COBOL), the IBM-supplied program is also called. This is not the number of
|
||
|
|
times the program named in the PROGRAM NAME field was initialized. QCRMAIN
|
||
|
|
is used for functions other than program initialization (for example, blocked
|
||
|
|
record I/O, some data conversions).<img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm">Program Name</dt>
|
||
|
|
<dd>(Transaction) For the Job Summary section of the Transaction Report, the
|
||
|
|
name of the program in control at the start of the transaction. Other programs
|
||
|
|
may be used during the transaction. For the Transaction Report section, the
|
||
|
|
name of the program active at the start of the transaction. If ADR=UNKNWN
|
||
|
|
(address unknown) is shown under the column, the program was deleted before
|
||
|
|
the trace data was dumped to the database file. If ADR=000000 is shown under
|
||
|
|
the column, there was not enough trace data to determine the program name,
|
||
|
|
or there was no program active at that level in the job when the trace record
|
||
|
|
was created.</dd>
|
||
|
|
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />PROGRAM NAME<img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />(Job Trace) The name of the last program called that was not in the library
|
||
|
|
QSYS before the end of a transaction.<img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm">Protocol</dt>
|
||
|
|
<dd>(System) Line protocol. <ul><li>SDLC</li>
|
||
|
|
<li>ASYNC</li>
|
||
|
|
<li>BSC</li>
|
||
|
|
<li>X25</li>
|
||
|
|
<li>TRLAN</li>
|
||
|
|
<li>ELAN (Ethernet)</li>
|
||
|
|
<li>IDLC</li>
|
||
|
|
<li>DDI</li>
|
||
|
|
<li>FRLY</li>
|
||
|
|
<li><img src="./delta.gif" alt="Start of change" />PPP<img src="./deltaend.gif" alt="End of change" /></li>
|
||
|
|
</ul>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Pty</dt>
|
||
|
|
<dd>(Component, Transaction, Job Interval) Priority of the job. For the Concurrent
|
||
|
|
Batch Job Statistics section of the Transaction Report, it is the priority
|
||
|
|
of the jobs in the job set.</dd>
|
||
|
|
<dt class="dlterm">Purge</dt>
|
||
|
|
<dd>(Transaction) The purge attribute of the jobs.</dd>
|
||
|
|
<dt class="dlterm">PWrt</dt>
|
||
|
|
<dd>(Transaction) The number of permanent write I/O operations.</dd>
|
||
|
|
<dt class="dlterm">Queue Length</dt>
|
||
|
|
<dd>(Resource Interval) The average number of I/O requests that had to wait
|
||
|
|
in the queue for this unit.</dd>
|
||
|
|
<dt class="dlterm">Rank</dt>
|
||
|
|
<dd>(Transaction) The order. For the Job Summary section, it is the order
|
||
|
|
of the program according to the number of transactions. For the Job Statistics
|
||
|
|
section, it is the order of the job. For the Interactive Program Statistics
|
||
|
|
section, it is the order of the program. For the Individual Transaction Statistics
|
||
|
|
section, it is the order of the transaction according to the data being put
|
||
|
|
in order by importance. For the Largest Seize/Lock Conflicts section, it is
|
||
|
|
the order of the seize or lock conflict.</dd>
|
||
|
|
<dt class="dlterm">Ratio of write disk I/O to total disk I/O</dt>
|
||
|
|
<dd>(System) The fraction of the total disk activity that is due to writing
|
||
|
|
data to the disks.</dd>
|
||
|
|
<dt class="dlterm">Reads per Second</dt>
|
||
|
|
<dd>(Resource Interval) The average number of disk read operations performed
|
||
|
|
per second by the disk arm.</dd>
|
||
|
|
<dt class="dlterm">Receive CRC Errors</dt>
|
||
|
|
<dd>(Resource Interval) The number of received frames that contained a cycle
|
||
|
|
redundancy check (CRC) error. This indicates that the data was not received
|
||
|
|
error free.</dd>
|
||
|
|
<dt class="dlterm">Record Number</dt>
|
||
|
|
<dd>(Lock) For database file members, the relative record number of the record
|
||
|
|
within the database file member.</dd>
|
||
|
|
<dt class="dlterm">Remote LAN Pct Frames Recd</dt>
|
||
|
|
<dd>(Resource Interval) The number of frames received from a local area network
|
||
|
|
(LAN) connected to the locally attached LAN.</dd>
|
||
|
|
<dt class="dlterm">Remote LAN Pct Frames Trnsmitd</dt>
|
||
|
|
<dd>(Resource Interval) The number of frames transmitted to a local area network
|
||
|
|
(LAN) connected to the locally attached LAN.</dd>
|
||
|
|
<dt class="dlterm">Remote Not Ready</dt>
|
||
|
|
<dd>(Resource Interval) The percentage of all receive-not-ready frames that
|
||
|
|
were received by the host system. A large percentage often means the remote
|
||
|
|
device cannot process data fast enough (congestion).</dd>
|
||
|
|
<dt class="dlterm">Remote Seq Error</dt>
|
||
|
|
<dd>(Resource Interval) The percent of frames received out of order by a remote
|
||
|
|
device or system. This can occur when the remote device or system cannot process
|
||
|
|
data fast enough.</dd>
|
||
|
|
<dt class="dlterm">Req type</dt>
|
||
|
|
<dd>(Component) The type of request being reported.</dd>
|
||
|
|
<dt class="dlterm">Requests received</dt>
|
||
|
|
<dd>(System, Component) The number of requests of all types received by the
|
||
|
|
server.</dd>
|
||
|
|
<dt class="dlterm">Requestor's Job Name</dt>
|
||
|
|
<dd>(Lock) The name of the job requesting the locked object (the same as in
|
||
|
|
the detail listing).</dd>
|
||
|
|
<dt class="dlterm">Reset Packets Recd</dt>
|
||
|
|
<dd>(Resource Interval) The number of reset packets received by the network.
|
||
|
|
<span class="uicontrol">Reset packets</span> are packets retransmitted because an
|
||
|
|
error occurred.</dd>
|
||
|
|
<dt class="dlterm">Reset Packets Trnsmitd</dt>
|
||
|
|
<dd>(Resource Interval) The number of reset packets transmitted by the network.</dd>
|
||
|
|
<dt class="dlterm">Response</dt>
|
||
|
|
<dd>(System) Average system response (service) time.</dd>
|
||
|
|
<dt class="dlterm">Response Sec Avg and Max</dt>
|
||
|
|
<dd>(Transaction) The average (AVG) and maximum (MAX) transaction response
|
||
|
|
time, in seconds, for the job. The average response time is calculated as
|
||
|
|
the sum of the time between each pair of wait-to-active and active-to-wait
|
||
|
|
transitions divided by the number of pairs that were encountered for the job.
|
||
|
|
The MAX response time is the largest response time in the job.</dd>
|
||
|
|
<dt class="dlterm">Response Seconds</dt>
|
||
|
|
<dd>(System) Average response time in seconds per transaction.</dd>
|
||
|
|
<dt class="dlterm">Responses sent</dt>
|
||
|
|
<dd>(System, Component) The number of responses of all types sent by the server.</dd>
|
||
|
|
<dt class="dlterm">Rsp</dt>
|
||
|
|
<dd>(Component) Average interactive transaction response time in seconds.</dd>
|
||
|
|
<dt class="dlterm">Rsp Time</dt>
|
||
|
|
<dd>(Component, Resource Interval) The average external response time (in
|
||
|
|
seconds). For the Local Work Station IOP Utilizations section of the Resource
|
||
|
|
Interval Report, it is the response time for work stations on this controller.
|
||
|
|
For the Remote Work Stations section of the Component Report, it is the response
|
||
|
|
time for this work station.</dd>
|
||
|
|
<dt class="dlterm">Rsp Timer Ended</dt>
|
||
|
|
<dd>(Resource Interval) The number of times the response timer ended waiting
|
||
|
|
for a response from a remote device.</dd>
|
||
|
|
<dt class="dlterm">Rsp/Tns</dt>
|
||
|
|
<dd>(Component, Transaction, Job Interval) The average response time (seconds)
|
||
|
|
per transaction. For the Job Summary section of the Job Interval Report, it
|
||
|
|
is the response time per transaction for the selected interactive jobs during
|
||
|
|
the interval (the amount of time spent waiting for or using the system resources
|
||
|
|
divided by the number of transactions processed). This number will not be
|
||
|
|
accurate unless at least several seconds were spent processing transactions.</dd>
|
||
|
|
<dt class="dlterm">S/L</dt>
|
||
|
|
<dd>(Transaction) Whether the conflict was a seize (S) or lock (L) conflict.</dd>
|
||
|
|
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />SECONDS<img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />(Job Trace) The approximate time the job was waiting or active.<img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm">Segments Pct Rtrns</dt>
|
||
|
|
<dd>(Component) The percentage of segments retransmitted. This number is the
|
||
|
|
TCP segments that were transmitted and that contain one or more previously
|
||
|
|
transmitted octets (bytes).</dd>
|
||
|
|
<dt class="dlterm">Segments Rcvd per Second</dt>
|
||
|
|
<dd>(Component) The number of segments received per second. This number includes
|
||
|
|
those received in error and those received on currently established connections.</dd>
|
||
|
|
<dt class="dlterm">Segments Sent per Second</dt>
|
||
|
|
<dd>(Component) The number of segments sent per second. This number includes
|
||
|
|
those sent on currently established connections and excludes those that contain
|
||
|
|
only retransmitted octets (bytes).</dd>
|
||
|
|
<dt class="dlterm">Seize and Lock Conflicts</dt>
|
||
|
|
<dd>(Batch Job Trace) Number of seize conflicts and lock waits.</dd>
|
||
|
|
<dt class="dlterm">Seize Conflict</dt>
|
||
|
|
<dd>(Component) Number of seize exceptions per second. For more detailed information,
|
||
|
|
issue the Start Performance Trace (STRPFRTRC) command, and use the PRTTNSRPT
|
||
|
|
or PRTLCKRPT commands. This count could be very high, even under normal system
|
||
|
|
operation. Use the count as a monitor. If there are large variations or changes,
|
||
|
|
explore these variations in more detail.</dd>
|
||
|
|
<dt class="dlterm">Seize Hold Time</dt>
|
||
|
|
<dd>(Transaction) The amount of time that the transaction held up other jobs
|
||
|
|
in the system by a seize or lock on an object.</dd>
|
||
|
|
<dt class="dlterm">Seize Wait /Tns</dt>
|
||
|
|
<dd>(Transaction) The average time, in seconds, for all seize-lock conflicts
|
||
|
|
that occur during an average transaction. More than one seize-lock conflict
|
||
|
|
can occur during a single transaction for the same job. If this number is
|
||
|
|
high, investigate those jobs with seize conflicts. The Transaction Report
|
||
|
|
lists each conflict that occurs, the name of the holder, and the name of the
|
||
|
|
object held. For the Transaction by 5-Minute Intervals section of the Job
|
||
|
|
Summary Report, it is the average seize wait time per transaction in seconds.
|
||
|
|
This is the average amount of time that the transactions spent in a seize/lock
|
||
|
|
conflict. If this number is high, look at the Transaction and Transition Reports
|
||
|
|
for the jobs that are causing the excessive wait time.</dd>
|
||
|
|
<dt class="dlterm">Select Parameters</dt>
|
||
|
|
<dd>(System, Component, Transaction, Job Interval, Pool Interval) The criteria
|
||
|
|
used to choose the data records to be included in the report. The criteria
|
||
|
|
are generally specified using an SLTxxx parameter of the command. Only nondefault
|
||
|
|
values (something other than *ALL) are printed. If a parameter is not specified,
|
||
|
|
it does not appear on the report.</dd>
|
||
|
|
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />SEQNBR<img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />(Job Trace) The number of the trace entry.<img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />SEQNCE or SEQUENCE<img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />(Job Trace) The job trace sequence number in the detail report that this
|
||
|
|
summary line refers to.<img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm">Sequence Error</dt>
|
||
|
|
<dd>(Resource Interval) The number of frames received that contained sequence
|
||
|
|
numbers indicating that frames were lost.</dd>
|
||
|
|
<dt class="dlterm">Server job name</dt>
|
||
|
|
<dd>(System) The server job number. Identifies the child job for the server.</dd>
|
||
|
|
<dt class="dlterm">Server job user</dt>
|
||
|
|
<dd>(System) The server job user. Identifies the child job for the server.</dd>
|
||
|
|
<dt class="dlterm">Server name</dt>
|
||
|
|
<dd>(System) The server job name. Identifies the child job for the server.</dd>
|
||
|
|
<dt class="dlterm">Server start date/time</dt>
|
||
|
|
<dd>(System) The most recent start or restart time in format mm/dd/yy hh:mm:ss</dd>
|
||
|
|
<dt class="dlterm">Short Frame Errors</dt>
|
||
|
|
<dd>(Resource Interval) The number of short frames received. A short frame
|
||
|
|
is a frame that has fewer octets between its start flag and end flag than
|
||
|
|
are permitted.</dd>
|
||
|
|
<dt class="dlterm">Short Wait /Tns</dt>
|
||
|
|
<dd>(Transaction) The average time, in seconds, of short (active) wait time
|
||
|
|
per transaction. For the Interactive Program Statistics section, if the value
|
||
|
|
is high, it may be due to the use of data queues or to the use of DFRWRT(*NO)
|
||
|
|
or RSTDSP(*YES) in the program display files.</dd>
|
||
|
|
<dt class="dlterm">Short WaitX /Tns (Short wait extended)</dt>
|
||
|
|
<dd>(Transaction) The average time, in seconds, of wait time per transaction
|
||
|
|
that resulted due to a short (active) wait that exceeded 2 seconds, and caused
|
||
|
|
a long wait transition to occur. The activity level has been released but
|
||
|
|
this time is still counted against your total response time. Waits on data
|
||
|
|
queues or the use of DFRWRT(*NO) and/or RSTDSP(*YES) in the display files
|
||
|
|
could be reasons for this value to be high.</dd>
|
||
|
|
<dt class="dlterm">Size</dt>
|
||
|
|
<dd>(Component) Decimal data overflow and underflow exceptions per second.
|
||
|
|
An indication of improper field size on numeric calculations.</dd>
|
||
|
|
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />Size (MB)<img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />(System) The size of the pool in megabytes.<img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />Size (GB)<img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />(Pool Interval) The size of the pool in gigabytes.<img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm">Size (M)</dt>
|
||
|
|
<dd>(System) Disk space capacity in millions of bytes.</dd>
|
||
|
|
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />SHARE CLS<img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />(Job Trace) The number of shared closes for all types of files.<img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />SHARE OPN<img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />(Job Trace) The number of shared opens for all types of files.<img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm">SMAPP ReTune</dt>
|
||
|
|
<dd>(Component) System-managed access path protection tuning adjustments.</dd>
|
||
|
|
<dt class="dlterm">SMAPP System</dt>
|
||
|
|
<dd>(Component) SMAPP-induced journal entries deposited in system-provided
|
||
|
|
(default) journals.</dd>
|
||
|
|
<dt class="dlterm">SMAPP User</dt>
|
||
|
|
<dd>(Component) SMAPP-induced journal entries deposited in user-provided journals.</dd>
|
||
|
|
<dt class="dlterm">SOTn</dt>
|
||
|
|
<dd>(Transaction) Listed in the Wait Code column, Start of transaction n.
|
||
|
|
These codes are in the wait code column, but they are not wait codes. They
|
||
|
|
indicate transaction boundary trace records.</dd>
|
||
|
|
<dt class="dlterm">Spool CPU seconds per I/O</dt>
|
||
|
|
<dd>(System) The average number of system processing unit seconds used by
|
||
|
|
all spool jobs for each I/O performed by a spool job.</dd>
|
||
|
|
<dt class="dlterm">Spool database reads per second</dt>
|
||
|
|
<dd>(System) The average number of read operations to database files per second
|
||
|
|
of spool processing.</dd>
|
||
|
|
<dt class="dlterm">Spool I/O per second</dt>
|
||
|
|
<dd>(System) The average number of physical disk I/O operations per second
|
||
|
|
of spool processing.</dd>
|
||
|
|
<dt class="dlterm">Srv Time</dt>
|
||
|
|
<dd>(Component) Average disk service time per request in seconds not including
|
||
|
|
the disk wait time.</dd>
|
||
|
|
<dt class="dlterm">SSL Inbound Connections</dt>
|
||
|
|
<dd>(System) AThe number of SSL inbound connections accepted by the server.</dd>
|
||
|
|
<dt class="dlterm">Start</dt>
|
||
|
|
<dd>(Transaction) The time the job started.</dd>
|
||
|
|
<dt class="dlterm">Started</dt>
|
||
|
|
<dd>(Transaction) The time of the first record in the trace data, in the form
|
||
|
|
HH.MM.SS (hours, minutes, seconds).</dd>
|
||
|
|
<dt class="dlterm">State</dt>
|
||
|
|
<dd>(Transaction) The three possible job states are: <ul><li><span class="uicontrol">W</span>--(Wait state) not holding an activity level.</li>
|
||
|
|
<li><span class="uicontrol">A</span>--(Active or wait state) holding an activity level.</li>
|
||
|
|
<li><span class="uicontrol">I</span>--(Ineligible state) waiting for an activity level.</li>
|
||
|
|
</ul>
|
||
|
|
<p>The table below shows the possible job state transitions. For example,
|
||
|
|
from <span class="uicontrol">W</span> to <span class="uicontrol">A</span> is <span class="uicontrol">y</span>,
|
||
|
|
or yes, which means it is possible for a job to change from the <em>wait</em> state
|
||
|
|
to the <em>active</em> state.</p>
|
||
|
|
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="void" border="0" rules="none"><tbody><tr><td valign="top"> </td>
|
||
|
|
<td valign="top"> </td>
|
||
|
|
<td colspan="3" valign="top">To state</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top"> </td>
|
||
|
|
<td valign="top"> </td>
|
||
|
|
<td valign="top"><strong>A</strong></td>
|
||
|
|
<td valign="top"><strong>W</strong></td>
|
||
|
|
<td valign="top"><strong>I</strong></td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top">From</td>
|
||
|
|
<td valign="top"><strong>A</strong></td>
|
||
|
|
<td valign="top"><strong>y</strong></td>
|
||
|
|
<td valign="top"><strong>y</strong></td>
|
||
|
|
<td valign="top"><strong>y</strong></td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top">State</td>
|
||
|
|
<td valign="top"><strong>W</strong></td>
|
||
|
|
<td valign="top"><strong>y</strong></td>
|
||
|
|
<td valign="top"><strong>-</strong></td>
|
||
|
|
<td valign="top"><strong>y</strong></td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top"> </td>
|
||
|
|
<td valign="top"><strong>I</strong></td>
|
||
|
|
<td valign="top"><strong>y</strong></td>
|
||
|
|
<td valign="top"><strong>-</strong></td>
|
||
|
|
<td valign="top"><strong>-</strong></td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">State Transitions A-A</dt>
|
||
|
|
<dd>(Batch Job Trace) Number of active-to-active transitions.</dd>
|
||
|
|
<dt class="dlterm">State Transitions A-I</dt>
|
||
|
|
<dd>(Batch Job Trace) Number of active-to-ineligible transitions.</dd>
|
||
|
|
<dt class="dlterm">Stop</dt>
|
||
|
|
<dd>(Transaction) The time the job ended.</dd>
|
||
|
|
<dt class="dlterm">Stopped</dt>
|
||
|
|
<dd>(Transaction) The time of the last record in the trace data, in the form
|
||
|
|
HH.MM.SS (hours, minutes, seconds).</dd>
|
||
|
|
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />SUBFILE READS<img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />(Job Trace) The number of subfile reads.<img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />SUBFILE WRITES<img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />(Job Trace) The number of subfile writes.<img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm">Subsystem Name</dt>
|
||
|
|
<dd>(Pool Interval) The name of the subsystem.</dd>
|
||
|
|
<dt class="dlterm">Subsystems</dt>
|
||
|
|
<dd>(System, Component, Pool Interval) For the System Report, the subsystem
|
||
|
|
names you specify. Each name is a 10-character name. For the Component Report,
|
||
|
|
the list of subsystems selected to be included (SLTSBS parameter) or excluded
|
||
|
|
(OMTSBS parameter).</dd>
|
||
|
|
<dt class="dlterm">Sum</dt>
|
||
|
|
<dd>(Transaction) Listed in the Sync Disk I/O Rqs/Tns column, the sum of the
|
||
|
|
averages of the synchronous DB READ, DB WRITE, NDB READ, and NDB WRITE requests
|
||
|
|
(the average number of synchronous I/O requests per transaction for the job).</dd>
|
||
|
|
<dt class="dlterm">SWX</dt>
|
||
|
|
<dd>(Transaction) Listed in the Wait Code column, Short Wait Extended. The
|
||
|
|
short wait has exceeded a 2-second limit and the system has put the transaction
|
||
|
|
into a long wait. This long wait must be charged to the transaction response
|
||
|
|
time. In most cases, this active-to-wait transaction does not reflect a transaction
|
||
|
|
boundary.</dd>
|
||
|
|
<dt class="dlterm">Sync</dt>
|
||
|
|
<dd>(Job Interval) The number of synchronous disk I/O operations performed
|
||
|
|
by the selected interactive jobs during the interval.</dd>
|
||
|
|
<dt class="dlterm">Sync DIO /Tns</dt>
|
||
|
|
<dd>(Transaction) The average number of synchronous I/O requests per transaction
|
||
|
|
during the interval.</dd>
|
||
|
|
<dt class="dlterm">Sync Disk I/O</dt>
|
||
|
|
<dd>(System, Component, Transaction) Synchronous disk I/O operations.</dd>
|
||
|
|
<dt class="dlterm">Sync Disk I/O per Second</dt>
|
||
|
|
<dd>(Component) Average synchronous disk I/O operations per second.</dd>
|
||
|
|
<dt class="dlterm">Sync Disk I/O Requests</dt>
|
||
|
|
<dd>(Transaction) The total number of synchronous disk I/O requests for the
|
||
|
|
given combination of priority, job type, and pool.</dd>
|
||
|
|
<dt class="dlterm">Sync Disk I/O Rqs/Tns</dt>
|
||
|
|
<dd>(Transaction) The next five columns provide information about the number
|
||
|
|
of synchronous disk I/O requests per transaction: <dl><dt class="dlterm">DB Read</dt>
|
||
|
|
<dd>The average number of synchronous database read requests per transaction.</dd>
|
||
|
|
<dt class="dlterm">DB Write</dt>
|
||
|
|
<dd>The average number of synchronous database write requests per transaction.</dd>
|
||
|
|
<dt class="dlterm">NDB Read</dt>
|
||
|
|
<dd>The average number of synchronous nondatabase read requests per transaction.</dd>
|
||
|
|
<dt class="dlterm">NDB Write</dt>
|
||
|
|
<dd>The average number of synchronous nondatabase write requests per transaction.</dd>
|
||
|
|
<dt class="dlterm">Sum</dt>
|
||
|
|
<dd>The sum of the averages of the synchronous DB READ, DB WRITE, NDB READ,
|
||
|
|
and NDB WRITE requests (the average number of synchronous I/O requests per
|
||
|
|
transaction for the job).</dd>
|
||
|
|
</dl>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Sync I/O /Elp Sec</dt>
|
||
|
|
<dd>(Transaction) The average number of synchronous disk I/O requests for
|
||
|
|
all jobs, per second of elapsed time used by the jobs.</dd>
|
||
|
|
<dt class="dlterm">Sync I/O /Sec</dt>
|
||
|
|
<dd>(Job Interval) The average number of synchronous disk I/O operations performed
|
||
|
|
per second by the job during the interval. This is calculated from the synchronous
|
||
|
|
disk I/O count divided by the elapsed time.</dd>
|
||
|
|
<dt class="dlterm">Sync I/O Per Second</dt>
|
||
|
|
<dd>(Job Interval) The average number of synchronous disk I/O operations performed
|
||
|
|
per second by the selected noninteractive jobs during the interval.</dd>
|
||
|
|
<dt class="dlterm">Synchronous DBR</dt>
|
||
|
|
<dd>(System, Transaction, Job Interval, Pool Interval) The average number
|
||
|
|
of synchronous database read operations. It is the total synchronous database
|
||
|
|
reads divided by the total transactions. For the Pool Interval and Job Interval
|
||
|
|
Reports, it is calculated per transaction for the job during the intervals.
|
||
|
|
For the System Report, it is calculated per second. For the Transaction (Job
|
||
|
|
Summary) it is calculated per transaction. Listed under Average DIO/Transaction,
|
||
|
|
the average number of synchronous database read requests per transaction.
|
||
|
|
This field is not printed if the jobs in the system did not process any transactions.</dd>
|
||
|
|
<dt class="dlterm">Synchronous DBW</dt>
|
||
|
|
<dd>(System, Transaction, Job Interval, Pool Interval) The average number
|
||
|
|
of synchronous database write operations. It is the total synchronous database
|
||
|
|
writes divided by the total transactions. For the Pool Interval and Job Interval
|
||
|
|
Reports, it is calculated per transaction for the job during the intervals.
|
||
|
|
For the System Report, it is calculated per second. For the Transaction (Job
|
||
|
|
Summary) it is calculated per transaction. Listed under Average DIO/Transaction,
|
||
|
|
the average number of synchronous database read requests per transaction.
|
||
|
|
This field is not printed if the jobs in the system did not process any transactions.</dd>
|
||
|
|
<dt class="dlterm">Synchronous DIO / Act Sec</dt>
|
||
|
|
<dd>(System, Transaction) The number of synchronous disk I/O operations per
|
||
|
|
active second. The active time is the elapsed time minus the wait times.</dd>
|
||
|
|
<dt class="dlterm">Synchronous DIO / Ded Sec</dt>
|
||
|
|
<dd>(Transaction) The estimated number of synchronous disk I/O operations
|
||
|
|
per second as if the job were running in dedicated mode. Dedicated mode means
|
||
|
|
that no other job would be active or in contention for resources in the system.</dd>
|
||
|
|
<dt class="dlterm">Synchronous DIO / Elp Sec</dt>
|
||
|
|
<dd>(Transaction) The number of synchronous disk I/O operations per elapsed
|
||
|
|
second.</dd>
|
||
|
|
<dt class="dlterm">Synchronous Disk I/O Counts</dt>
|
||
|
|
<dd>(Transaction) The next five columns provide information about the number
|
||
|
|
of synchronous disk I/O requests per transaction: <dl><dt class="dlterm">DB Read</dt>
|
||
|
|
<dd>The number of synchronous database read requests per transaction.</dd>
|
||
|
|
<dt class="dlterm">DB Wrt</dt>
|
||
|
|
<dd>The number of synchronous database write requests per transaction.</dd>
|
||
|
|
<dt class="dlterm">NDB Read</dt>
|
||
|
|
<dd>The number of synchronous nondatabase read requests per transaction.</dd>
|
||
|
|
<dt class="dlterm">NDB Wrt</dt>
|
||
|
|
<dd>The number of synchronous nondatabase write requests per transaction.</dd>
|
||
|
|
<dt class="dlterm">Sum</dt>
|
||
|
|
<dd>The sum of the synchronous DB Read, DB Wrt, NDB Read, and NDB Wrt requests
|
||
|
|
(the number of synchronous I/O requests per transaction).</dd>
|
||
|
|
</dl>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Synchronous disk I/O per transaction</dt>
|
||
|
|
<dd>(System, Transaction) The average number of synchronous physical disk
|
||
|
|
I/O operations per interactive transaction.</dd>
|
||
|
|
<dt class="dlterm">Synchronous Max</dt>
|
||
|
|
<dd>(Transaction) The maximum number of synchronous DBR, NDBR, and WRT I/O
|
||
|
|
requests encountered for any single transaction by that job. If the job is
|
||
|
|
not an interactive or autostart job type, the total disk I/O for the job is
|
||
|
|
listed here.</dd>
|
||
|
|
<dt class="dlterm">Synchronous NDBR</dt>
|
||
|
|
<dd>(System, Transaction, Job Interval, Pool Interval) The average number
|
||
|
|
of synchronous nondatabase read operations per transaction for the jobs in
|
||
|
|
the system during the interval. For the Transaction Report, the operations
|
||
|
|
on the disk per transaction for the selected jobs in the pool. This is calculated
|
||
|
|
from the synchronous nondatabase read count divided by the transactions processed.
|
||
|
|
This field is not printed if the jobs in the system did not process any transactions.</dd>
|
||
|
|
<dt class="dlterm">Synchronous NDBW</dt>
|
||
|
|
<dd>(System, Job Interval, Pool Interval) The average number of synchronous
|
||
|
|
nondatabase write operations on the disk per transaction for the selected
|
||
|
|
jobs in the pool. For the System Report, it is the operations per transaction
|
||
|
|
for the jobs in the system during the interval. This is calculated from the
|
||
|
|
synchronous nondatabase write count divided by the transactions processed.
|
||
|
|
This field is not printed if the jobs in the system did not process any transactions.</dd>
|
||
|
|
<dt class="dlterm">Synchronous Sum</dt>
|
||
|
|
<dd>(Transaction) The sum of the averages of the synchronous DBR, NDBR, and
|
||
|
|
WRT requests (the average number of synchronous I/O requests per transaction
|
||
|
|
for the job).</dd>
|
||
|
|
<dt class="dlterm">Synchronous wrt</dt>
|
||
|
|
<dd>(Transaction) The average number of synchronous database and nondatabase
|
||
|
|
write requests per transaction.</dd>
|
||
|
|
<dt class="dlterm">System CPU per transaction (seconds)</dt>
|
||
|
|
<dd>(System) The average number of system processing unit seconds per interactive
|
||
|
|
transaction.</dd>
|
||
|
|
<dt class="dlterm">System disk I/O per transaction</dt>
|
||
|
|
<dd>(System) The total number of physical disk I/O operations attributed to
|
||
|
|
the system per interactive transaction.</dd>
|
||
|
|
<dt class="dlterm">System Starts</dt>
|
||
|
|
<dd>(Component) The number of start journal operations initiated by the system.</dd>
|
||
|
|
<dt class="dlterm">System Stops</dt>
|
||
|
|
<dd>(Component) The number of stop journal operations initiated by the system.</dd>
|
||
|
|
<dt class="dlterm">System Total</dt>
|
||
|
|
<dd>(Component) The total number of journal deposits resulting from system-journaled
|
||
|
|
objects. These are the deposits performed by system-managed access path protection
|
||
|
|
(SMAPP).</dd>
|
||
|
|
<dt class="dlterm">System ToUser</dt>
|
||
|
|
<dd>(Component) The number of journal deposits resulting from system-journaled
|
||
|
|
objects to user-created journals.</dd>
|
||
|
|
<dt class="dlterm">SZWG</dt>
|
||
|
|
<dd>(Transaction) Listed in the Wait Code column, Seize Wait Granted. The
|
||
|
|
job was waiting on a seize conflict. The original holder released the lock
|
||
|
|
that it had on the object, and the lock was then granted to the waiting job.
|
||
|
|
The job that was waiting for the object is named on this line (WAITER --)
|
||
|
|
along with the amount of time the job spent waiting for the seize conflict
|
||
|
|
to be released. The object that is held is named on the next line of the report
|
||
|
|
(OBJECT --).</dd>
|
||
|
|
<dt class="dlterm">SZWT</dt>
|
||
|
|
<dd>(Transaction) Listed in the Wait Code column, Seize/Lock Conflict Wait.
|
||
|
|
The job is waiting on a seize/lock conflict. The time (*/ time /*) is the
|
||
|
|
duration of the seize/lock conflict, and is included in the active time that
|
||
|
|
follows it on the report. The holder of the lock is named at the right of
|
||
|
|
the report line (HOLDER --). The object being held is named on the next report
|
||
|
|
line (OBJECT --).</dd>
|
||
|
|
<dt class="dlterm">Teraspace EAO</dt>
|
||
|
|
<dd>(Component) Listed in the Exception Occurrence summary and Interval Counts.
|
||
|
|
A teraspace effective address overflow (EAO) occurs when computing a teraspace
|
||
|
|
address that crosses a 16-boundary. A quick estimate indicates that a 1% performance
|
||
|
|
degradation would occur if there were 2,300 EAOs per second.</dd>
|
||
|
|
<dt class="dlterm">Thread</dt>
|
||
|
|
<dd>(Job Summary, Transaction, Transition) A thread is a unique flow of control
|
||
|
|
within a process. Every job has an initial thread associated with it. Each
|
||
|
|
job can start one or more secondary threads. The system assigns the thread
|
||
|
|
number to a job as follows: <ul><li>The system assigns thread IDs sequentially. When a job is started that
|
||
|
|
uses a job structure that was previously active, the thread ID that is assigned
|
||
|
|
to the initial thread is the next number in the sequence.</li>
|
||
|
|
<li>The first thread of a job is assigned a number.</li>
|
||
|
|
<li>Any additional threads from the same job are assigned a number that is
|
||
|
|
incremented by 1. For example: <pre>Job Name User Name/ Job Number
|
||
|
|
Thread
|
||
|
|
QJVACMDSRV SMITH 023416
|
||
|
|
QJVACMDSRV 00000006 023416
|
||
|
|
QJVACMDSRV 00000007 023416
|
||
|
|
QJVACMDSRV 00000008 023416</pre>
|
||
|
|
<p>A thread value greater than 1 does not necessarily mean the
|
||
|
|
job has had that many threads active at the same time. To determine how many
|
||
|
|
threads are currently active for the same job, use the WRKACTJOB, WRKSBSJOB,
|
||
|
|
or WRKUSRJOB commands to find the multiple three-part identifiers with the
|
||
|
|
same job name.</p>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Threads active</dt>
|
||
|
|
<dd>(System) The number of threads doing work when the data was sampled.</dd>
|
||
|
|
<dt class="dlterm">Threads idle</dt>
|
||
|
|
<dd>(System) The number of idle threads when the data was sampled.</dd>
|
||
|
|
<dt class="dlterm">Time</dt>
|
||
|
|
<dd>(Transaction) The time when the transaction completed, or when a seize
|
||
|
|
or lock conflict occurred. Also, a column heading that shows the time the
|
||
|
|
transition from one state to another occurred, in the HH.MM.SS.mmm arrangement.</dd>
|
||
|
|
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />TIME<img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />(Job Trace) The time of day for the trace entry. The time is sequentially
|
||
|
|
given in hours, minutes, seconds, and microseconds.<img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm">Tns</dt>
|
||
|
|
<dd>(Component, Pool Interval) The total number of transactions processed
|
||
|
|
by the selected jobs in the pool or subsystem.</dd>
|
||
|
|
<dt class="dlterm">Tns Count</dt>
|
||
|
|
<dd>(Component, Job Interval) The number of transactions performed by the
|
||
|
|
selected interactive jobs during the interval.</dd>
|
||
|
|
<dt class="dlterm">Tns/Hour</dt>
|
||
|
|
<dd>(Component, Transaction, Job Interval) The average number of transactions
|
||
|
|
per hour processed by the selected interactive jobs during the interval.</dd>
|
||
|
|
<dt class="dlterm">Tns/Hour Rate</dt>
|
||
|
|
<dd>(System) Average number of transactions per hour.</dd>
|
||
|
|
<dt class="dlterm">TOD of Wait</dt>
|
||
|
|
<dd>(Lock) The time of day of the start of the conflict.</dd>
|
||
|
|
<dt class="dlterm">Tot</dt>
|
||
|
|
<dd>(Transaction) Listed in Physical I/O Counts column, the total number of
|
||
|
|
DB Read, DB Wrt, NDB Read, and NDB Wrt requests.</dd>
|
||
|
|
<dt class="dlterm">Tot Nbr Tns</dt>
|
||
|
|
<dd>(Transaction) The total number of transactions the PRTTNSRPT program determined
|
||
|
|
from the input data that were accomplished for the job.</dd>
|
||
|
|
<dt class="dlterm">Total</dt>
|
||
|
|
<dd>(Component) Total exception counts for the reporting period.</dd>
|
||
|
|
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />TOTAL<img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />(Job Trace) Totals for the fields.<img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm">Total /Job</dt>
|
||
|
|
<dd>(Transaction) The total (sum) of the items in the column for the job.</dd>
|
||
|
|
<dt class="dlterm">Total characters per transaction</dt>
|
||
|
|
<dd>(System) The average number of characters either read from or written
|
||
|
|
to display station screens per interactive transaction.</dd>
|
||
|
|
<dt class="dlterm">Total CPU Sec /Sync DIO</dt>
|
||
|
|
<dd>(Transaction) The ratio of total CPU seconds divided by the total synchronous
|
||
|
|
disk I/O requests.</dd>
|
||
|
|
<dt class="dlterm">Total CPU Utilization</dt>
|
||
|
|
<dd><span><img src="./delta.gif" alt="Start of change" />(System, Component) Percentage of available processing
|
||
|
|
unit time used by the partition. For a multiple-processor system, this is
|
||
|
|
the average use across all processors. For dedicated partitions, <var class="varname">Total
|
||
|
|
CPU Utilization</var> is replaced by a utilization value for each processor
|
||
|
|
in the partition. Here is an example of this part of the display for a dedicated
|
||
|
|
partition with two processors: <img src="./deltaend.gif" alt="End of change" /></span><pre> Average CPU utilization . . . . . : 41.9
|
||
|
|
CPU 1 utilization . . . . . . . . : 41.7
|
||
|
|
CPU 2 utilization . . . . . . . . : 42.2</pre>
|
||
|
|
<p><img src="./delta.gif" alt="Start of change" />In shared processor partitions, individual CPU utilization
|
||
|
|
rows are not printed.<img src="./deltaend.gif" alt="End of change" /></p>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> This value is taken from a system counter.
|
||
|
|
Other processing unit uses are taken from the individual job work control
|
||
|
|
blocks (WCBs). These totals may differ slightly. <span><img src="./delta.gif" alt="Start of change" />For uncapped
|
||
|
|
partitions, <var class="varname">Total CPU utilization</var> might exceed 100 percent.<img src="./deltaend.gif" alt="End of change" /></span></div>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Total CPU Utilization (Database Capability)</dt>
|
||
|
|
<dd>(System) Shows you the DB2 Universal Database™ for <span class="keyword">iSeries</span> activity on your systems. This
|
||
|
|
field applies to all systems running V4R5 or later and includes all database
|
||
|
|
activity, including all SQL and data I/O operations.</dd>
|
||
|
|
<dt class="dlterm">Total CPU Utilization (Interactive Feature)</dt>
|
||
|
|
<dd>(System) The CPU Utilization (Interactive Feature) shows the CPU utilization
|
||
|
|
for all jobs doing 5250 workstation I/O operations relative to the capacity
|
||
|
|
of the system for interactive work. Depending on the system and associated
|
||
|
|
features purchased, the interactive capacity is equal to or less than the
|
||
|
|
total capacity of the system.</dd>
|
||
|
|
<dt class="dlterm">Total Data Characters Received</dt>
|
||
|
|
<dd>(Resource Interval) The number of data characters received successfully.</dd>
|
||
|
|
<dt class="dlterm">Total Data Characters Transmitted</dt>
|
||
|
|
<dd>(Resource Interval) The number of data characters transmitted successfully.</dd>
|
||
|
|
<dt class="dlterm">Total Datagrams Requested for Transmission</dt>
|
||
|
|
<dd>(Component) The percentage of IP datagrams that are discarded because
|
||
|
|
of the following reasons: <ul><li>No route was found to transmit the datagrams to their destination.</li>
|
||
|
|
<li>Lack of buffer space.</li>
|
||
|
|
</ul>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Total fields per transaction</dt>
|
||
|
|
<dd>(System) The average number of display station fields either read from
|
||
|
|
or written to per interactive transaction.</dd>
|
||
|
|
<dt class="dlterm">Total Frames Recd</dt>
|
||
|
|
<dd>(Resource Interval) The number of frames received, including frames with
|
||
|
|
errors and frames that are not valid.</dd>
|
||
|
|
<dt class="dlterm">Total I Frames Trnsmitd</dt>
|
||
|
|
<dd>(Resource Interval) The total number of information frames transmitted.</dd>
|
||
|
|
<dt class="dlterm">Total I/O</dt>
|
||
|
|
<dd>(System) Sum of the read and write operations.</dd>
|
||
|
|
<dt class="dlterm">Total PDUs Received</dt>
|
||
|
|
<dd>(Resource Interval) The number of protocol data units (PDUs) received
|
||
|
|
during the time interval. <div class="note"><span class="notetitle">Note:</span> A protocol data unit (PDU) for asynchronous
|
||
|
|
communications is a variable-length unit of data that is ended by a protocol
|
||
|
|
control character or by the size of the buffer.</div>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Total Physical I/O per Second</dt>
|
||
|
|
<dd>(Resource Interval) The average number of physical disk I/O operations
|
||
|
|
performed per second by the disk arm.</dd>
|
||
|
|
<dt class="dlterm">Total Responses</dt>
|
||
|
|
<dd>(Component, Resource Interval) The total number of transactions counted
|
||
|
|
along with the average response time for all active work stations or devices
|
||
|
|
on this controller for the report period.</dd>
|
||
|
|
<dt class="dlterm">Total Seize/Wait Time</dt>
|
||
|
|
<dd>(Component) The response time in milliseconds for each job.</dd>
|
||
|
|
<dt class="dlterm">Total Tns</dt>
|
||
|
|
<dd>(Component) Number of transactions processed in this pool.</dd>
|
||
|
|
<dt class="dlterm">Transaction Response Time (Sec/Tns)</dt>
|
||
|
|
<dd>(Transaction) The response time in seconds for each transaction. This
|
||
|
|
value includes no communications line time. Response times measured at the
|
||
|
|
work station exceed this time by the data transmission time (the time required
|
||
|
|
to transmit data from the work station to the processing unit and to transmit
|
||
|
|
the response data back to the work station from the processing unit).</dd>
|
||
|
|
<dt class="dlterm">Transactions per hour (local)</dt>
|
||
|
|
<dd>(System) The interactive transactions per hour attributed to local display
|
||
|
|
stations.</dd>
|
||
|
|
<dt class="dlterm">Transactions per hour (remote)</dt>
|
||
|
|
<dd>(System) The interactive transactions per hour attributed to remote display
|
||
|
|
stations.</dd>
|
||
|
|
<dt class="dlterm">Transient Size</dt>
|
||
|
|
<dd>(Component) Kilobytes placed within the journal transient area; these
|
||
|
|
are hidden journal entries produced by the system.</dd>
|
||
|
|
<dt class="dlterm">Transmit/Receive/Average Line Util</dt>
|
||
|
|
<dd>(Resource Interval) In duplex mode, the percentage of transmit line capacity
|
||
|
|
used, the percentage of receive line capacity used, and the average of the
|
||
|
|
transmit and receive capacities.</dd>
|
||
|
|
<dt class="dlterm">TSE</dt>
|
||
|
|
<dd>(Transaction) Listed in the Wait Code column, Time Slice End. The program
|
||
|
|
shown in the stack entry labeled LAST is the program that went to time slice
|
||
|
|
end.</dd>
|
||
|
|
<dt class="dlterm">Typ</dt>
|
||
|
|
<dd>(Component, Transaction) The system job type and subtype. The Component
|
||
|
|
Report allows only one character in this column. The Transaction Report allows
|
||
|
|
two characters. The Transaction Report reports the job type and job subtype
|
||
|
|
directly from the QAPMJOBS fields. The Component Report takes the job type
|
||
|
|
and job subtype values and converts it to a character that may or may not
|
||
|
|
be the value from the QAPMJOBS field. The possible job types are: <dl><dt class="dlterm">A</dt>
|
||
|
|
<dd>Autostart</dd>
|
||
|
|
<dt class="dlterm">B</dt>
|
||
|
|
<dd>Batch</dd>
|
||
|
|
<dt class="dlterm">BD</dt>
|
||
|
|
<dd>Batch immediate (Transaction only) <div class="note"><span class="notetitle">Note:</span> The batch immediate values are
|
||
|
|
shown as BCI on the Work with Active Job display and as BATCHI on the Work
|
||
|
|
with Subsystem Job display.</div>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">BE</dt>
|
||
|
|
<dd>Batch evoke (Transaction only)</dd>
|
||
|
|
<dt class="dlterm">BJ</dt>
|
||
|
|
<dd>Batch pre-start job (Transaction only)</dd>
|
||
|
|
<dt class="dlterm">C</dt>
|
||
|
|
<dd>Programmable work station application server, which includes 5250 emulation
|
||
|
|
over APPC and <span class="keyword">iSeries</span> Access
|
||
|
|
host servers running either APPC or TCP/IP. You can find the host server information
|
||
|
|
under the Host server administration topic in the <span class="keyword">iSeries</span> Information
|
||
|
|
Center. A job is reported as a <span class="keyword">iSeries</span> Access
|
||
|
|
server if any of the following items are true: <ul><li>Incoming APPC evoke requests one of the server program names. This also
|
||
|
|
applies to the pre-started jobs for the QSERVER, QCMN, and QSYSWRK subsystems
|
||
|
|
that are already waiting for the named program.</li>
|
||
|
|
<li>Incoming IP port number corresponds to one of the service name-description-port-numbers.
|
||
|
|
This also applies to the pre-started jobs for the QSERVER, QCMN, and QSYSWRK
|
||
|
|
subsystems that are already waiting for the assigned IP port number.</li>
|
||
|
|
<li>Incoming IPX socket number corresponds to one of the service name-description-port-numbers.
|
||
|
|
This also applies to the pre-started jobs for the QSERVER, QCMN, and QSYSWRK
|
||
|
|
subsystems that are already waiting for the assigned IPX port number.</li>
|
||
|
|
<li>Incoming 5250 display emulation jobs that come from APPC data streams
|
||
|
|
sent by 5250 emulation under OS/2 Communications Manager or WARP equivalent.</li>
|
||
|
|
</ul>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">D</dt>
|
||
|
|
<dd>Target distributed data management (DDM) server</dd>
|
||
|
|
<dt class="dlterm">I</dt>
|
||
|
|
<dd>Interactive. For the Component Report, this includes twinaxial data link
|
||
|
|
control (TDLC), 5250 remote workstation, and 3270 remote workstation. For
|
||
|
|
the Transaction Report, this includes twinaxial data link control (TDLC),
|
||
|
|
5250 remote workstation, 3270 remote workstation, SNA pass-through, and 5250
|
||
|
|
Telnet.</dd>
|
||
|
|
<dt class="dlterm">L</dt>
|
||
|
|
<dd>Licensed Internal Code Task</dd>
|
||
|
|
<dt class="dlterm">M</dt>
|
||
|
|
<dd>Subsystem monitor</dd>
|
||
|
|
<dt class="dlterm">P</dt>
|
||
|
|
<dd>SNA pass-through and 5250 Telnet pass-through. On the Transaction Report,
|
||
|
|
these jobs appear as I (interactive).</dd>
|
||
|
|
<dt class="dlterm">R</dt>
|
||
|
|
<dd>Spool reader</dd>
|
||
|
|
<dt class="dlterm">S</dt>
|
||
|
|
<dd>System</dd>
|
||
|
|
<dt class="dlterm">W</dt>
|
||
|
|
<dd>Spool writer, which includes the spool write job, and if Advanced
|
||
|
|
Function Printing (AFP) is specified, the print driver job.</dd>
|
||
|
|
<dt class="dlterm">WP</dt>
|
||
|
|
<dd>Spool print driver (Transaction only)</dd>
|
||
|
|
<dt class="dlterm">X</dt>
|
||
|
|
<dd>Start the system</dd>
|
||
|
|
</dl>
|
||
|
|
<p>The possible job subtypes are:</p>
|
||
|
|
<dl><dt class="dlterm">D</dt>
|
||
|
|
<dd>Batch immediate job</dd>
|
||
|
|
<dt class="dlterm">E</dt>
|
||
|
|
<dd>Evoke (communications batch)</dd>
|
||
|
|
<dt class="dlterm">J</dt>
|
||
|
|
<dd>Pre-start job</dd>
|
||
|
|
<dt class="dlterm">P</dt>
|
||
|
|
<dd>Print driver job</dd>
|
||
|
|
<dt class="dlterm">T</dt>
|
||
|
|
<dd>Multiple requester terminal (MRT) (System/36 environment only)</dd>
|
||
|
|
<dt class="dlterm">3</dt>
|
||
|
|
<dd>System/36</dd>
|
||
|
|
</dl>
|
||
|
|
<div class="note"><span class="notetitle">Notes:</span> <ol><li>Job subtypes do not appear on the Component Report.</li>
|
||
|
|
<li>If the job type is blank or you want to reassign it, use the Change Job
|
||
|
|
Type (CHGJOBTYP) command to assign an appropriate job type.</li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Type</dt>
|
||
|
|
<dd>(System, Transaction, Job Interval) One of the transaction types listed
|
||
|
|
in the description of the DTNTY field. <dl><dt class="dlterm">(System)</dt>
|
||
|
|
<dd>The disk type.</dd>
|
||
|
|
<dt class="dlterm">(Transaction)</dt>
|
||
|
|
<dd>The type and subtype of the job.</dd>
|
||
|
|
<dt class="dlterm">(Transaction)</dt>
|
||
|
|
<dd>For the Seize/Lock Conflicts by Object section, the type of seize/lock
|
||
|
|
conflict.</dd>
|
||
|
|
</dl>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">UDP Datagrams Received</dt>
|
||
|
|
<dd>(Component) The total number of User Datagram Protocol (UDP) datagrams
|
||
|
|
delivered to UDP users.</dd>
|
||
|
|
<dt class="dlterm">UDP Datagrams Sent</dt>
|
||
|
|
<dd>(Component) The total number of User Datagram Protocol (UDP) datagrams
|
||
|
|
sent from this entity.</dd>
|
||
|
|
<dt class="dlterm"> Uncap CPU Avail</dt>
|
||
|
|
<dd>(Component)Percentage of CPU time available to a partition in the shared
|
||
|
|
processors pool during the interval in addition to its configured CPU. This
|
||
|
|
value is relative to the configured CPU available for the particular partition. </dd>
|
||
|
|
<dt class="dlterm">Unicast Packets Received</dt>
|
||
|
|
<dd>(System) The total number of subnetwork-unicast packets delivered to a
|
||
|
|
higher-layer protocol. The number includes only packets received on the specified
|
||
|
|
interface.</dd>
|
||
|
|
<dt class="dlterm">Unicast Packets Sent</dt>
|
||
|
|
<dd>(System) The total number of packets that higher-level protocols requested
|
||
|
|
to be transmitted to a subnetwork-unicast address. This number includes those
|
||
|
|
packets that were discarded or were not sent.</dd>
|
||
|
|
<dt class="dlterm">Unit</dt>
|
||
|
|
<dd>(System, Component, Resource Interval) The number assigned by the system
|
||
|
|
to identify a specific disk unit or arm. An 'A' or 'B' following the unit
|
||
|
|
number indicates that the disk unit is mirrored. (For example, 0001A and 0001B
|
||
|
|
are a mirrored pair.)</dd>
|
||
|
|
<dt class="dlterm">Unit Name</dt>
|
||
|
|
<dd>The resource name of the disk arm.</dd>
|
||
|
|
<dt class="dlterm">User ID</dt>
|
||
|
|
<dd>(System, Component, Transaction, Job Interval, Pool) The list of users
|
||
|
|
selected to be included (SLTUSRID parameter) or excluded (OMTUSRID parameter).</dd>
|
||
|
|
<dt class="dlterm">User Name</dt>
|
||
|
|
<dd>(Component, Transaction, Job Interval, Batch Job Trace) Name of the user
|
||
|
|
involved (submitted the job, had a conflict, and so on.)</dd>
|
||
|
|
<dt class="dlterm">User Name/Thread</dt>
|
||
|
|
<dd>(Component, Transaction) If the job information contains a secondary thread,
|
||
|
|
then this column shows the thread identifier. If the job information does
|
||
|
|
not contain a secondary thread, then the column shows the user name. The system
|
||
|
|
assigns the thread number to a job as follows: <ul><li>The system assigns thread IDs sequentially. When a job is started that
|
||
|
|
uses a job structure that was previously active, the thread ID that is assigned
|
||
|
|
to the initial thread is the next number in the sequence.</li>
|
||
|
|
<li>The first thread of a job is assigned a number.</li>
|
||
|
|
<li>Any additional threads from the same job are assigned a number that is
|
||
|
|
incremented by 1. For example: <pre>Job Name User Name/ Job Number
|
||
|
|
Thread
|
||
|
|
QJVACMDSRV SMITH 023416
|
||
|
|
QJVACMDSRV 00000006 023416
|
||
|
|
QJVACMDSRV 00000007 023416
|
||
|
|
QJVACMDSRV 00000008 023416</pre>
|
||
|
|
<p>A thread value greater than 1 does not necessarily mean the
|
||
|
|
job has had that many threads active at the same time. To determine how many
|
||
|
|
threads are currently active for the same job, use the WRKACTJOB, WRKSBSJOB,
|
||
|
|
or WRKUSRJOB commands to find the multiple three-part identifiers with the
|
||
|
|
same job name.</p>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">User Starts</dt>
|
||
|
|
<dd>(Component) The number of start journal operations initiated by the user.</dd>
|
||
|
|
<dt class="dlterm">User Stops</dt>
|
||
|
|
<dd>(Component) The number of stop journal operations initiated by the user.</dd>
|
||
|
|
<dt class="dlterm">User Total</dt>
|
||
|
|
<dd>(Component) The total number of journal deposits resulting from system-journaled
|
||
|
|
objects.</dd>
|
||
|
|
<dt class="dlterm">Util</dt>
|
||
|
|
<dd>(Component, Resource Interval) The percent of utilization for each local
|
||
|
|
work station, disk, or communications IOP, controller, or drive.<div class="note"><span class="notetitle">Note:</span> The
|
||
|
|
system-wide average utilization does not include data for mirrored arms in
|
||
|
|
measurement intervals for which such intervals are either in resuming or suspended
|
||
|
|
status.</div>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Util 2</dt>
|
||
|
|
<dd>(Component, Resource) Utilization of co-processor.</dd>
|
||
|
|
<dt class="dlterm">Value</dt>
|
||
|
|
<dd>(Transaction) For the Individual Transaction Statistics section of the
|
||
|
|
Job Summary report, it is the value of the data being compared for the transaction.
|
||
|
|
For the Longest Seize/Lock Conflicts section, it is the number of seconds
|
||
|
|
in which the seize or lock conflict occurred.</dd>
|
||
|
|
<dt class="dlterm">Verify</dt>
|
||
|
|
<dd>(Component) Number of verify exceptions per second. Verify exceptions
|
||
|
|
occur when a pointer needs to be resolved, when blocked MI instructions are
|
||
|
|
used at security levels 10, 20, or 30, and when an unresolved symbolic name
|
||
|
|
is called. This count could be very high, even under normal system operation.
|
||
|
|
Use the count as a monitor. If there are large variations or changes, explore
|
||
|
|
these variations in more detail.</dd>
|
||
|
|
<dt class="dlterm">W-I Wait/Tns</dt>
|
||
|
|
<dd>(Transaction) The average time, in seconds, of wait-to-ineligible time
|
||
|
|
per transaction. This value is an indication of what effect the activity level
|
||
|
|
has on response time. If this value is low, the number of wait-to-ineligible
|
||
|
|
transitions probably has little effect on response time. If the value is high,
|
||
|
|
adding additional interactive pool storage and increasing the interactive
|
||
|
|
pool activity level should improve response time. If you are unable to increase
|
||
|
|
the interactive pool storage (due to limited available storage), increasing
|
||
|
|
the activity level may also improve response time. However, increasing the
|
||
|
|
activity level might result in excessive faulting within the storage pool.</dd>
|
||
|
|
<dt class="dlterm">Wait Code</dt>
|
||
|
|
<dd>(Transaction) The job state transition that causes the trace record to
|
||
|
|
be produced. The values can be as follows: <dl><dt class="dlterm">EVT</dt>
|
||
|
|
<dd>Event Wait. A long wait that occurs when waiting on a message queue.</dd>
|
||
|
|
<dt class="dlterm">EOTn</dt>
|
||
|
|
<dd>End of transaction for transaction for type n. These codes are in the
|
||
|
|
wait code column, but they are not wait codes. They indicate transaction boundary
|
||
|
|
trace records.</dd>
|
||
|
|
<dt class="dlterm">EORn</dt>
|
||
|
|
<dd>End of response time for transaction n. These codes are in the wait code
|
||
|
|
column, but they are not wait codes. They indicate transaction boundary trace
|
||
|
|
records.</dd>
|
||
|
|
<dt class="dlterm">Error Responses</dt>
|
||
|
|
<dd>(Component> The number of responses in error.</dd>
|
||
|
|
<dt class="dlterm">HDW</dt>
|
||
|
|
<dd>Hold Wait (job suspended or system request).</dd>
|
||
|
|
<dt class="dlterm">LKRL</dt>
|
||
|
|
<dd>Lock Released. The job released a lock it had on the object named on the
|
||
|
|
next detail line of the report (OBJECT --). The job that was waiting for the
|
||
|
|
object is named on this line (WAITER --) along with the amount of time the
|
||
|
|
job spent waiting for the lock to be released.</dd>
|
||
|
|
<dt class="dlterm">LKW</dt>
|
||
|
|
<dd>Lock Wait. If there are a number of these, or you see entries with a significant
|
||
|
|
length of time in the ACTIVE/RSP* column, additional analysis is necessary.
|
||
|
|
The LKWT report lines that precede this LKW report line show you what object
|
||
|
|
is being waited on, and who has the object.</dd>
|
||
|
|
<dt class="dlterm">LKWT</dt>
|
||
|
|
<dd>Lock Conflict Wait. The job is waiting on a lock conflict. The time (*/
|
||
|
|
time /*) is the duration of the lock conflict and, though not equal to the
|
||
|
|
LKW time, should be very close to it. The holder of the lock is named at the
|
||
|
|
right of the report line (HOLDER --). The object being locked is named on
|
||
|
|
the next report line (OBJECT --).</dd>
|
||
|
|
<dt class="dlterm">SOTn</dt>
|
||
|
|
<dd>Start of transaction n. These codes are in the wait code column, but they
|
||
|
|
are not wait codes. They indicate transaction boundary trace records.</dd>
|
||
|
|
<dt class="dlterm">SWX</dt>
|
||
|
|
<dd>Short Wait Extended. The short wait has exceeded a 2-second limit and
|
||
|
|
the system has put the transaction into a long wait. This long wait must be
|
||
|
|
charged to the transaction response time. In other words, this active-to-wait
|
||
|
|
transaction does not reflect a transaction boundary.</dd>
|
||
|
|
<dt class="dlterm">SZWG</dt>
|
||
|
|
<dd>(Transaction) Listed in the Wait Code column, Seize Wait Granted. The
|
||
|
|
job was waiting on a seize conflict. The original holder released the lock
|
||
|
|
that it had on the object, and the lock was then granted to the waiting job.
|
||
|
|
The job that was waiting for the object is named on this line (WAITER --)
|
||
|
|
along with the amount of time the job spent waiting for the seize conflict
|
||
|
|
to be released. The object that is held is named on the next line of the report
|
||
|
|
(OBJECT --).</dd>
|
||
|
|
<dt class="dlterm">SZWT</dt>
|
||
|
|
<dd>Seize/Lock Conflict Wait. The job is waiting on a seize/lock conflict.
|
||
|
|
The time (*/ time /*) is the duration of the seize/lock conflict, and is included
|
||
|
|
in the active time that follows it on the report. The holder of the lock is
|
||
|
|
named at the right of the report line (HOLDER --). The object being held is
|
||
|
|
named on the next report line (OBJECT --).</dd>
|
||
|
|
<dt class="dlterm">TSE</dt>
|
||
|
|
<dd>Time Slice End. The program shown in the stack entry labeled LAST is the
|
||
|
|
program that went to time slice end. Every time a job uses 0.5 seconds of
|
||
|
|
CPU time (0.2 seconds on the faster processors) between long waits, the system
|
||
|
|
checks if there are jobs of equal priority on the CPU queue. If there are,
|
||
|
|
then the next job with equal priority is granted the CPU and the interrupted
|
||
|
|
job is moved to the queue as the last of equal priority. The job, however,
|
||
|
|
retains its activity level. This is an internal time slice end. When a job
|
||
|
|
reaches the external time slice value, there can be a job state transition
|
||
|
|
from active to ineligible if another job is waiting for an activity level.
|
||
|
|
When a job is forced out of its activity level, its pages are liable to be
|
||
|
|
stolen by other jobs, and cause additional I/O when the job regains an activity
|
||
|
|
level. The IBM-supplied default values of 2 seconds for interactive jobs and
|
||
|
|
5 seconds for batch jobs may often be too high, especially for the high-end
|
||
|
|
processors. As an initial value, set the time slice at 3 times the average
|
||
|
|
CPU seconds per transaction.</dd>
|
||
|
|
<dt class="dlterm">WTO</dt>
|
||
|
|
<dd>Wait Timed Out. The job has exceeded the wait time-out limit defined for
|
||
|
|
a wait (such as a wait on a lock, a message queue, or a record).</dd>
|
||
|
|
</dl>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />WAITS<img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />(Job Trace) The number of waits that occurred. <img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />WAIT-ACT<img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />(Job Trace) In the Job Trace Analysis Summary, this is the time between
|
||
|
|
the ENDTNS and STRTNS programs is labeled WAIT-ACT. If you were tracing an
|
||
|
|
interactive job and used the default STRTNS and ENDTNS parameters, this value
|
||
|
|
is the time taken to process the transaction. <p>In the Job Trace Analysis
|
||
|
|
I/O Summary, this is the time that the job was inactive, probably due to typing
|
||
|
|
or think time by the user.</p>
|
||
|
|
<img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm">Wait-Inel</dt>
|
||
|
|
<dd>(System, Component) Average number of wait-to-ineligible job state transitions
|
||
|
|
per minute.</dd>
|
||
|
|
<dt class="dlterm">Work Station Controller</dt>
|
||
|
|
<dd>(Resource Interval) The name of the remote work station controller.</dd>
|
||
|
|
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />WRITES<img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />(Job Trace) The number of physical writes that occurred. <img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm">Writes per Second</dt>
|
||
|
|
<dd>(Resource Interval) The average number of disk write operations performed
|
||
|
|
per second by the disk arm.</dd>
|
||
|
|
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />WRITTEN<img src="./deltaend.gif" alt="End of change" /></dt>
|
||
|
|
<dd><img src="./delta.gif" alt="Start of change" />(Job Trace) The number of physical writes that occurred for the entry.<img src="./deltaend.gif" alt="End of change" /></dd>
|
||
|
|
<dt class="dlterm">WTO</dt>
|
||
|
|
<dd>(Transaction) Listed in the Wait Code column, Wait Timed Out. The job
|
||
|
|
has exceeded the wait time-out limit defined for a wait (such as a wait on
|
||
|
|
a lock, a message queue, or a record).</dd>
|
||
|
|
<dt class="dlterm">0.0-1.0</dt>
|
||
|
|
<dd>(Component, Resource Interval) The number of times the response time was
|
||
|
|
between 0 and 1 second.</dd>
|
||
|
|
<dt class="dlterm">1.0-2.0</dt>
|
||
|
|
<dd>(Component, Resource Interval) The number of times the response time was
|
||
|
|
between 1 and 2 seconds.</dd>
|
||
|
|
<dt class="dlterm">2.0-4.0</dt>
|
||
|
|
<dd>(Component, Resource Interval) The number of times the response time was
|
||
|
|
between 2 and 4 seconds.</dd>
|
||
|
|
<dt class="dlterm">4.0-8.0</dt>
|
||
|
|
<dd>(Component, Resource Interval) The number of times the response time was
|
||
|
|
between 4 and 8 seconds.</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="rzahxsysrep.htm">Example: System Report</a></div>
|
||
|
|
<div><a href="rzahxreportheader.htm" title="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.">Performance Report header</a></div>
|
||
|
|
<div><a href="rzahxcompreport.htm">Example: Component Report</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>
|