ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzahx_5.4.0.1/rzahxqapmsystem.xml

<?xml:stylesheet version="1.0" encoding="utf-8"?>
<?xml:stylesheet type="text/xsl" href="../rzahg/icdyntable.xsl"?>
<TABLE xmlns="x-schema:rzahxqapmsystem-schema.xml">
<TITLE>Performance data files: QAPMSYSTEM</TITLE>
<TH col="TD1">
Field Name
</TH>
<TH col="TD2">
Description
</TH>
<TH col="TD3">
Attribute
</TH>
<TR><TD1 valign="top">INTNUM</TD1><TD2 valign="top">Interval number: The nth sample database interval based on the start
time specified in the Create Performance Data (CRTPFRDTA) command.</TD2><TD3 valign="top">PD (5,0)</TD3></TR>
<TR><TD1 valign="top">DTETIM</TD1><TD2 valign="top">Interval date (yymmdd) and time (hhmmss): The date and time of the
sample interval.</TD2><TD3 valign="top">C (12)</TD3></TR>
<TR><TD1 valign="top">INTSEC</TD1><TD2 valign="top">Elapsed interval seconds: The number of seconds since the last sample
interval.</TD2><TD3 valign="top">PD (7,0)</TD3></TR>
<TR><TD1 valign="top">DTECEN</TD1><TD2 valign="top">Century digit.</TD2><TD3 valign="top">C (1)</TD3></TR>
<TR><TD1 valign="top">SYDPGF</TD1><TD2 valign="top">Directory page faults: Number of times a page of the auxiliary storage
directory was transferred to main storage for a look-up or an allocation operation.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYAPGF</TD1><TD2 valign="top">Access group member page faults: Number of times a page of an object
contained in an access group was transferred to main storage independently
of the access group. This transfer occurs when the containing access group
was purged, or because portions of the containing access group are displaced
from main storage.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYMPGF</TD1><TD2 valign="top">Microcode page faults: Number of times a page of microcode was transferred
to main storage.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYMCTR</TD1><TD2 valign="top">Microtask read operations: Number of transfers of one or more pages
of data from auxiliary storage because of a microtask rather than a process.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYMCTW</TD1><TD2 valign="top">Microtask write operations: Number of transfers of one or more pages
of data from main storage to auxiliary storage because of a microtask rather
than a process.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYSASP</TD1><TD2 valign="top">System auxiliary storage pool space available: Number of bytes of space
on auxiliary storage available for allocation in the system ASP that is not
currently assigned to machine interface (MI) objects or internal machine functions.</TD2><TD3 valign="top">PD (15,0)</TD3></TR>
<TR><TD1 valign="top">SYPRMW</TD1><TD2 valign="top">Permanent data transferred from main storage: Number of 512-byte blocks
of permanent data transferred from main storage to the system ASP in auxiliary
storage since the last sample.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYSIZC</TD1><TD2 valign="top">Size count: Total number of size exceptions.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYDECD</TD1><TD2 valign="top">Decimal data count: Total number of decimal data exceptions.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYSEZC</TD1><TD2 valign="top">Seize count: Total number of seize wait exceptions.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYSZWT</TD1><TD2 valign="top">Seize/wait time in milliseconds.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYSYNL</TD1><TD2 valign="top">Synchronous lock conflict count.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYASYL</TD1><TD2 valign="top">Asynchronous lock conflict count.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYVFYC</TD1><TD2 valign="top">Verify count.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYAUTH</TD1><TD2 valign="top">Object authority checks. The number of times that authority was checked
for objects. An authority check for one object can result in zero, one, or
more than one user authority lookups that can be cached or noncached (see
SYNUAL field description).</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYEXPN</TD1><TD2 valign="top">Total number of exceptions.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYLRT1</TD1><TD2 valign="top">Transactions in first response time monitor bracket: Total number of
local workstation transactions with response time less than the value of boundary
1 specified on the Advanced Local Response Time Options dialog from the Collection
Services properties page within the <span class="keyword">iSeries™ Navigator</span> interface.</TD2><TD3 valign="top">PD (9,0)</TD3></TR>
<TR><TD1 valign="top">SYLRT2</TD1><TD2 valign="top">Transactions in second response time monitor bracket: Total number
of local workstation transactions with response time less than the value of
boundary 2 and greater than the value of boundary 1 specified on the Advanced
Local Response Time Options dialog from the Collection Services properties
page within the <span class="keyword">iSeries Navigator</span> interface.</TD2><TD3 valign="top">PD (9,0)</TD3></TR>
<TR><TD1 valign="top">SYLRT3</TD1><TD2 valign="top">Transactions in third response time monitor bracket: Total number of
local workstation transactions with response time less than the value of boundary
3 and greater than the value of boundary 2 specified on the Advanced Local
Response Time Options dialog from the Collection Services properties page
within the <span class="keyword">iSeries Navigator</span> interface.</TD2><TD3 valign="top">PD (9,0)</TD3></TR>
<TR><TD1 valign="top">SYLRT4</TD1><TD2 valign="top">Transactions in fourth response time monitor bracket: Total number
of local workstation transactions with response time less than the value of
boundary 4 and greater than the value of boundary 3 specified on the Advanced
Local Response Time Options dialog from the Collection Services properties
page within the <span class="keyword">iSeries Navigator</span> interface.</TD2><TD3 valign="top">PD (9,0)</TD3></TR>
<TR><TD1 valign="top">SYLRT5</TD1><TD2 valign="top">Transactions in fifth response time monitor bracket: Total number of
local workstation transactions with response time greater than the value of
boundary 4 specified on the Advanced Local Response Time Options dialog from
the Collection Services properties page within the <span class="keyword">iSeries Navigator</span> interface.</TD2><TD3 valign="top">PD (9,0)</TD3></TR>
<TR><TD1 valign="top">SHCPU</TD1><TD2 valign="top">Total processing unit time (in milliseconds) used by microcode/system
jobs.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SMPLP</TD1><TD2 valign="top">Machine pool paging: Number of pages transferred in and out of machine
pool.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SMUPL</TD1><TD2 valign="top">Highest user pool paging: Highest number of pages transferred in and
out of any user pool.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SUPLI</TD1><TD2 valign="top">Pool with highest paging: Pool number with highest number of pages
transferred in and out.</TD2><TD3 valign="top">C (2)</TD3></TR>
<TR><TD1 valign="top">SMXDU</TD1><TD2 valign="top">Maximum disk utilization. The largest utilization of all single path
disk units and all paths of multipath disk units.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SMXDUI</TD1><TD2 valign="top">Actuator with maximum utilization.</TD2><TD3 valign="top">C (4)</TD3></TR>
<TR><TD1 valign="top">SMMMT</TD1><TD2 valign="top">Time (in seconds) spent at MRTMAX by all MRT requests.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SMME</TD1><TD2 valign="top">Number of requesters that routed to an MRT.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYFOPN</TD1><TD2 valign="top">Number of full opens system wide.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYIXRB</TD1><TD2 valign="top">Number of index rebuilds system wide.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYJOXR</TD1><TD2 valign="top">Start journal operations initiated by user.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYJOXP</TD1><TD2 valign="top">Stop journal operations initiated by user.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYJOIR</TD1><TD2 valign="top">Start journal operations initiated by system.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYJOIP</TD1><TD2 valign="top">Stop journal operations initiated by system.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYJOXD</TD1><TD2 valign="top">Journal deposits resulting from user-journaled objects.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYJOID</TD1><TD2 valign="top">Journal deposits resulting from system-journaled objects.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYJOJP</TD1><TD2 valign="top">Journal deposits resulting from system-journaled objects to user-created
journals.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYJOBJ</TD1><TD2 valign="top">Bundle writes to user-created journals.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYJOBD</TD1><TD2 valign="top">Bundle writes to internal system journals.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYJOJY</TD1><TD2 valign="top">Exposed access paths currently being journaled by the system.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYJOJN</TD1><TD2 valign="top">Exposed access paths currently not being journaled.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYJOSE</TD1><TD2 valign="top">System-estimated access path recovery time exposure in milliseconds.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYJORT</TD1><TD2 valign="top">System-managed access path tuning adjustments.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYJOND</TD1><TD2 valign="top">System-estimated access path recovery time exposure in milliseconds
if no access paths were being journaled by the system.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYHEAO</TD1><TD2 valign="top">Number of tolerated crossings of a 16 MB boundary within any teraspace.
Also called teraspace EAO exceptions.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYHFTS</TD1><TD2 valign="top">Number of space address computations (not addressing teraspace) that
required extra processing. This may occur when a subtraction or addition of
a signed value causes a result that is within the first page of a space object
or associated space for which the machine did not choose alignment. Also called
false traps.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYHFTH</TD1><TD2 valign="top">Number of teraspace address computations that required extra processing.
This occurs when a subtraction or addition of a signed value causes a result
that is within the first page after any 16 MB boundary in teraspace. Also
called false traps.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYSDBC</TD1><TD2 valign="top">Database CPU time. The amount of CPU time (in milliseconds) used for
database processing.</TD2><TD3 valign="top">PD (9,0)</TD3></TR>
<TR><TD1 valign="top">SYSSWC</TD1><TD2 valign="top">Secondary workload CPU time. The aggregate CPU time (in milliseconds)
of all jobs performing workloads that cannot fully exploit dedicated server
resources. <div class="note"><span class="notetitle">Note:</span> This metric measures non-Domino CPU usage on Domino<sup>®</sup> servers.
On non-Domino servers, this metric is not supported, so the reported value
is 0.</div>
</TD2><TD3 valign="top">PD (9,0)</TD3></TR>
<TR><TD1 valign="top">SYJOER</TD1><TD2 valign="top">Number of SMAPP evaluations requested. This count reveals how many
times implicitly journaled objects were examined for potential SMAPP eligibility
alterations. The evaluation can result in one of three outcomes: 1 - no action;
2 - start protecting this index via SMAPP; 3 - cease protecting this index
via SMAPP.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYJOES</TD1><TD2 valign="top">Number of SMAPP evaluations serviced. This is a count of evaluations
which led to a decision to change the protection state for a related index.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYJOIB</TD1><TD2 valign="top">Number of SMAPP index build time estimations. The number of times background
SLIC tasks have been asked to look at database keyed logical files or SQL
indexes in order to estimate how long it will take to rebuild the index from
scratch. Indexes whose estimated rebuild times are large will be SMAPPed.
A large count here suggests that applications are frequently opening and closing
files.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYJOS1</TD1><TD2 valign="top">First journal entry type. This field reports the most frequently occurring
among the various journal entry types that have caused the SLIC layer of journal
code to empty the journal cache prematurely. The number of bundles forced
by this entry type is reported in the field SYJOC1.</TD2><TD3 valign="top">C (2)</TD3></TR>
<TR><TD1 valign="top">SYJOC1</TD1><TD2 valign="top">Number of journal bundles forced prematurely by the journal entry type
reported in the field SYJOS1.</TD2><TD3 valign="top">PD (15,0)</TD3></TR>
<TR><TD1 valign="top">SYJOS2</TD1><TD2 valign="top">Second journal entry type. This field reports the second most frequently
occurring among the various journal entry types that have caused the SLIC
layer of journal code to empty the journal cache prematurely. The number of
bundles forced by this entry type is reported in the field SYJOC2.</TD2><TD3 valign="top">C (2)</TD3></TR>
<TR><TD1 valign="top">SYJOC2</TD1><TD2 valign="top">Number of journal bundles forced prematurely by the journal entry type
reported in the field SYJOS2.</TD2><TD3 valign="top">PD (15,0)</TD3></TR>
<TR><TD1 valign="top">SYJOS3</TD1><TD2 valign="top">Third journal entry type. This field reports the third most frequently
occurring among the various journal entry types that have caused the SLIC
layer of journal code to empty the journal cache prematurely. The number of
bundles forced by this entry type is reported in the field SYJOC3.</TD2><TD3 valign="top">C (2)</TD3></TR>
<TR><TD1 valign="top">SYJOC3</TD1><TD2 valign="top">Number of journal bundles forced prematurely by the journal entry type
reported in the field SYJOS3.</TD2><TD3 valign="top">PD (15,0)</TD3></TR>
<TR><TD1 valign="top">SYSDNFE</TD1><TD2 valign="top">The number of stream files which have been written to, but not forced
to permanent storage. This count includes files in the Root, QOpenSys, QDLS,
QOPT (when the files are on a volume that is not formatted in Universal Disk
Format (UDS)) and user-defined file systems.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYSDNFO</TD1><TD2 valign="top">The number of stream files currently exposed that have exceeded the
target exposure time. This count includes files in the Root, QOpenSys, QDLS,
QOPT (when the files are on a volume that is not formatted in Universal Disk
Format (UDS)) and user-defined file systems.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYSDTET</TD1><TD2 valign="top">Exposure time (in milliseconds). The number of milliseconds between
the time a stream file is written to and the time the file is forced to permanent
storage. This time is a total for all files that were exposed during the interval.
This count includes files in the Root, QOpenSys, QDLS, QOPT (when the files
are on a volume that is not formatted in Universal Disk Format (UDS)) and
user-defined file systems.</TD2><TD3 valign="top">PD (15,0)</TD3></TR>
<TR><TD1 valign="top">SYSDNST</TD1><TD2 valign="top">The number of tasks running that are forcing stream files to permanent
storage. This count includes files in the Root, QOpenSys, QDLS, QOPT (when
the files are on a volume that is not formatted in Universal Disk Format (UDS))
and user-defined file systems.</TD2><TD3 valign="top">PD (5,0)</TD3></TR>
<TR><TD1 valign="top">SYSDFAL</TD1><TD2 valign="top">The number of stream files that have been exposed and needed to be
forced. This count includes files in the Root, QOpenSys, QDLS, QOPT (when
the files are on a volume that is not formatted in Universal Disk Format (UDS))
and user-defined file systems.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYSDFRL</TD1><TD2 valign="top">The total number of stream files that have been asynchronously forced
to permanent storage. This count includes files in the Root, QOpenSys, QDLS,
QOPT (when the files are on a volume that is not formatted in Universal Disk
Format (UDS)) and user-defined file systems.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYSDPFD</TD1><TD2 valign="top">The number of stream file pages that have been asynchronously forced
to permanent storage. This count does not include pages forced by an fsync
operation. This count includes files in the Root, QOpenSys, QDLS, QOPT (when
the files are on a volume that is not formatted in Universal Disk Format (UDS))
and user-defined file systems.</TD2><TD3 valign="top">PD (15,0)</TD3></TR>
<TR><TD1 valign="top">SYSDPFF</TD1><TD2 valign="top">The number of stream file pages explicitly forced to permanent storage
as a result of an fsync operation. This count includes files in the Root,
QOpenSys, QDLS, QOPT (when the files are on a volume that is not formatted
in Universal Disk Format (UDS)) and user-defined file systems.</TD2><TD3 valign="top">PD (15,0)</TD3></TR>
<TR><TD1 valign="top">SYBTAC</TD1><TD2 valign="top">The number of asynchronous clear operations performed. This count includes
files in the Root, QOpenSys, QDLS, QOPT (when the files are on a volume that
is not formatted in Universal Disk Format (UDS)) and user-defined file systems.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYBTAP</TD1><TD2 valign="top">The number of asynchronous prebring operations performed. This count
includes files in the Root, QOpenSys, QDLS, QOPT (when the files are on a
volume that is not formatted in Universal Disk Format (UDS)) and user-defined
file systems.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYBTAPP</TD1><TD2 valign="top">The number of parallel prebring operations performed. This count includes
files in the Root, QOpenSys, QDLS, QOPT (when the files are on a volume that
is not formatted in Universal Disk Format (UDS)) and user-defined file systems.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYBTAPC</TD1><TD2 valign="top">The number of asynchronous create operations performed. This count
includes files in the Root, QOpenSys, QDLS, QOPT (when the files are on a
volume that is not formatted in Universal Disk Format (UDS)) and user-defined
file systems.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYBTAPD</TD1><TD2 valign="top">The number of asynchronous delete operations performed. This count
includes files in the Root, QOpenSys, QDLS, QOPT (when the files are on a
volume that is not formatted in Universal Disk Format (UDS)) and user-defined
file systems.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYLPTB</TD1><TD2 valign="top">LPAR time base. This field provides a way to determine the difference
between the system clocks on different partitions of a single system. This
field has no meaning when looked at on a stand-alone basis. However, when
this value is established on two (or more) partitions of a system, the difference
between these values is the time difference (in seconds) between the two partitions.</TD2><TD3 valign="top">B (11,0)</TD3></TR>
<TR><TD1 valign="top">SYNUAL</TD1><TD2 valign="top">Noncached user authority lookups. The number of times that a noncached
user authority lookup was performed. An authority check for one object can
result in zero, one, or more than one user authority lookups. A user authority
lookup can occur for the user, the user's groups, or an adopted user and can
be cached or noncached.</TD2><TD3 valign="top">PD (15,0)</TD3></TR>
<TR><TD1 valign="top">SYIFUS</TD1><TD2 valign="top">Interactive CPU time used. Total interactive CPU used (in milliseconds).</TD2><TD3 valign="top">PD (9,0)</TD3></TR>
<TR><TD1 valign="top">SYIFTE</TD1><TD2 valign="top">Interactive CPU time used over threshold. Interactive CPU used (in
milliseconds) when exceeding interactive CPU threshold.</TD2><TD3 valign="top">PD (9,0)</TD3></TR>
<TR><TD1 valign="top">SYIFTA</TD1><TD2 valign="top">Interactive CPU time available. The amount of interactive CPU time
that was available for use within the partition. This is the interactive capacity
configured for use within the partition (also represented as interactive threshold).</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYSPTU</TD1><TD2 valign="top">CPU time used. Total processing time (in milliseconds) used by the
partition</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYSCTA</TD1><TD2 valign="top">Total CPU time configured for the partition. Total processing time
(in milliseconds) that was configured or guaranteed for this partition. This
is the system processing capacity as determined by processor unit allocations
during the interval. Note: For uncapped partitions, the actual CPU used can
exceed this value.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYSUTA</TD1><TD2 valign="top">CPU time that could have been used by this partition. Total processing
time (in milliseconds) that could have been used by this partition (adjusted
for configuration changes over time). It includes both the guaranteed configured
capacity as well as the shared pool time that was not used by other partitions.
For capped and dedicated partitions, or if shared pool data is not available,
this is the same as Uncapped CPU time configured.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYSUTC</TD1><TD2 valign="top">Uncapped CPU time configured. The maximum amount of CPU time that this
partition is configured (allowed) to use within the shared pool (adjusted
for configuration changes over time). This field defines the Minimum of the
virtual processors configured and the configured shared pool processors. For
capped and dedicated partitions, this is the same as total CPU time configured
for the partition.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYSPLU</TD1><TD2 valign="top">Shared pool CPU time used. Total amount of CPU used within the shared
pool by all partitions that share the pool. Set to zero if a shared pool is
not used or the data is not available.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYSPLA</TD1><TD2 valign="top">Shared pool CPU time available. Total amount of CPU
available within the shared pool. This value is determined based on the number
of physical processors that are allocated to the pool. Set to zero if a shared
pool is not used or the data is not available.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYVCPU</TD1><TD2 valign="top">Virtual processor time configured. The processing time
capacity  (in milliseconds) visible to the operating system based on the number
of virtual processors configured and adjusted for configuration changes over
time. This field is similar to SYSUTC except it is not affected by the shared
pool configuration or the capped/uncapped state of the partition. The formula
SYVCPU/(INTSEC*1000) will yield the average number of virtual processors configured
in the interval.  <span class="uicontrol">Note:</span> Will be zero for data obtained
prior to V5R4</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYDPCH</TD1><TD2 valign="top">Total Dispatch Time.  The amount of time (in milliseconds)
that the operating system has dispatched a job, task, or thread to a processor.
This is not the same as CPU time used due to the effects of processor virtualization. <span class="uicontrol">Note:</span> this
field will contain data only if file QAPMJOBWT data is available</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">SYSHRF</TD1><TD2 valign="top">Shared processor flag. Indicates if the partition uses
shared processors:  <p> ‘ ‘ = unknown </p>
<p>'0'= Partition does not share
physical processors.</p>
<p>'1' = Partition shares physical processors. </p>
</TD2><TD3 valign="top">C (1)</TD3></TR>
<TR><TD1 valign="top">SYSIUL</TD1><TD2 valign="top">Reserved.</TD2><TD3 valign="top">PD (5,0)</TD3></TR>
<TR><TD1 valign="top">SYSCIU</TD1><TD2 valign="top">Reserved.</TD2><TD3 valign="top">PD (7,0)</TD3></TR>
<TR><TD1 valign="top">SYJDUM</TD1><TD2 valign="top">Reserved.</TD2><TD3 valign="top">PD (1,0)</TD3></TR>
<TR><TD1 valign="top">SYJDDM</TD1><TD2 valign="top">Reserved.</TD2><TD3 valign="top">C (3)</TD3></TR>
<TR><TD1 valign="top">SYJCA4</TD1><TD2 valign="top">Reserved.</TD2><TD3 valign="top">C (3)</TD3></TR>
<TR><TD1 valign="top">SYJPAS</TD1><TD2 valign="top">Reserved.</TD2><TD3 valign="top">C (3)</TD3></TR>
<TR><TD1 valign="top">SYJMRT</TD1><TD2 valign="top">Reserved.</TD2><TD3 valign="top">C (3)</TD3></TR>
<TR><TD1 valign="top">SYJS6E</TD1><TD2 valign="top">Reserved.</TD2><TD3 valign="top">C (3)</TD3></TR>
<TR><TD1 valign="top">SYJCME</TD1><TD2 valign="top">Reserved.</TD2><TD3 valign="top">C (3)</TD3></TR>
<TR><TD1 valign="top">SYJAUT</TD1><TD2 valign="top">Reserved.</TD2><TD3 valign="top">C (3)</TD3></TR>
<TR><TD1 valign="top">SYJBCH</TD1><TD2 valign="top">Reserved.</TD2><TD3 valign="top">C (3)</TD3></TR>
<TR><TD1 valign="top">SYJINT</TD1><TD2 valign="top">Reserved.</TD2><TD3 valign="top">C (3)</TD3></TR>
<TR><TD1 valign="top">SYJSPL</TD1><TD2 valign="top">Reserved.</TD2><TD3 valign="top">C (3)</TD3></TR>
</TABLE>