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

<?xml:stylesheet version="1.0" encoding="utf-8"?>
<?xml:stylesheet type="text/xsl" href="../rzahg/icdyntable.xsl"?>
<TABLE xmlns="x-schema:rzahxqapmdisk-schema.xml">
<TITLE>Performance data files: QAPMDISK</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 <em>n</em>th 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 (<var class="varname">yymmdd</var>) and time (<var class="varname">hhmmss</var>):
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">IOPRN</TD1><TD2 valign="top">IOP resource name</TD2><TD3 valign="top">C (10)</TD3></TR>
<TR><TD1 valign="top">DIOPID</TD1><TD2 valign="top">Reserved</TD2><TD3 valign="top">C (1)</TD3></TR>
<TR><TD1 valign="top">DSARM</TD1><TD2 valign="top">Disk arm number: Specifies the unique identifier of the unit. Each
actuator arm on the disk drives available to the machine represents a unit
of auxiliary storage. The value of the unit number is assigned by the system
when the unit is allocated to an ASP.</TD2><TD3 valign="top">C (4)</TD3></TR>
<TR><TD1 valign="top">DSTYPE</TD1><TD2 valign="top">Disk drive type such as 9332, 9335, or 6100.</TD2><TD3 valign="top">C (4)</TD3></TR>
<TR><TD1 valign="top">DSDRN</TD1><TD2 valign="top">Device resource name. Typically, there is one disk (device) resource
per disk unit except for a multipath disk unit that has multiple disk resources
associated with it (see note <A HREF="#rzahxqapmdisk__qapmdisknote5" shape="rect">5</A>).</TD2><TD3 valign="top">C (10)</TD3></TR>
<TR><TD1 valign="top">DSSCAN</TD1><TD2 valign="top">Number of search string commands: This count is always zero, because
search string commands are not supported for the 9332, 9335, or 6100.</TD2><TD3 valign="top">PD (5,0)</TD3></TR>
<TR><TD1 valign="top">DSBLKR		 </TD1><TD2 valign="top"><span>Number of blocks read: Block is one sector
on the disk drive.</span></TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSBLKW	</TD1><TD2 valign="top"><span>Number of blocks written: Block is one
sector on the disk drive.</span>	</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSBLKR</TD1><TD2 valign="top">Number of blocks read: The block length is 520 bytes, which includes
8 bytes of system control information.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSBLKW</TD1><TD2 valign="top">Number of blocks written: The block length is 520 bytes, which includes
8 bytes of system control information.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSIDLC</TD1><TD2 valign="top">Processor idle loop counter (see note <A HREF="#rzahxqapmdisk__qapmdisknote1" shape="rect">1</A>):
The number of times the disk controller passed through the idle loop. This
count is increased differently for the 9332 and the 9335. For the 9332, this
counter is increased only if the disk controller is totally idle (for example,
no I/O operations are active.) For the 9335, even though the disk controller
may be idle and the counter gets increased, an I/O operation can be active
(for example, seek is being performed.) This field is nonzero for drive types
that support a dedicated disk processor and zero for other drive types. <p>DSIDLC
and DSIDLT are duplicated across all arms for the same disk controller.</p>
</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSIDLT</TD1><TD2 valign="top">Processor idle loop time (see note <A HREF="#rzahxqapmdisk__qapmdisknote3" shape="rect">3</A>):
The time (in hundredths of microseconds) to make one pass through the idle
loop. This field is nonzero for drive types that support a dedicated disk
processor and zero for other drive types. The value reported could be a multiple
of the actual idle loop time. In that case, the value reported for the processor
idle loop count field (DSIDLC) is reduced accordingly so that the calculated
processor utilization is correct. <p>DSIDLC and DSIDLT are duplicated across
all arms for the same disk controller.</p>
</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSSK1</TD1><TD2 valign="top">Number of seeks &gt; 2/3: The number of times the arm traveled more
than 2/3 of the disk on a seek.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSSK2</TD1><TD2 valign="top">Number of seeks &gt; 1/3 and &lt; 2/3 (see note <A HREF="#rzahxqapmdisk__qampmdisknote2" shape="rect">2</A>):
The number of times the arm traveled more than 1/3 but less than 2/3 of the
disk on a seek.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSSK3</TD1><TD2 valign="top">Number of seeks &gt; 1/6 and &lt; 1/3 (see note <A HREF="#rzahxqapmdisk__qampmdisknote2" shape="rect">2</A>):
The number of times the arm traveled more than 1/6 but less than 1/3 of the
disk on a seek.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSSK4</TD1><TD2 valign="top">Number of seeks &gt; 1/12 and &lt; 1/6 (see note <A HREF="#rzahxqapmdisk__qampmdisknote2" shape="rect">2</A>):
The number of times the arm traveled more than 1/12 but less than 1/6 of the
disk on a seek.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSSK5</TD1><TD2 valign="top">Number of seeks &lt; 1/12 (see note <A HREF="#rzahxqapmdisk__qampmdisknote2" shape="rect">2</A>):
The number of times the arm traveled from its current position but less than
1/12 of the disk on a seek.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSSK6</TD1><TD2 valign="top">Number of zero seeks (see note <A HREF="#rzahxqapmdisk__qampmdisknote2" shape="rect">2</A>):
The number of times the access arm did not physically move on a seek request.
The operation may have resulted in a head switch. This field is 0 for disk
drive type 6100. The number of zero seeks will be accumulated in DSSK5.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSQUEL</TD1><TD2 valign="top">Total queue elements: The number of I/O operations waiting service
at sample time. This number includes the I/O operation that is in progress.
Divide this by DSSMPL to get the average queue length.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSNBSY</TD1><TD2 valign="top">Number of times arm not busy: The number of times there were no outstanding
I/O operations active at sample time.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSSMPL	</TD1><TD2 valign="top"><span>Number of samples taken: The number of
samples taken for the DSQUEL and DSNBSY fields.</span>	</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSCAP</TD1><TD2 valign="top">Drive capacity (in bytes): Total number of bytes of auxiliary storage
provided on the unit for the storage of objects and internal machine functions
when the ASP containing it is not under checksum protection. The unit reserved
system space value is subtracted from the unit capacity to calculate this
capacity.</TD2><TD3 valign="top">PD (15,0)</TD3></TR>
<TR><TD1 valign="top">DSAVL</TD1><TD2 valign="top">Drive available space (in bytes): Total number of bytes of auxiliary
storage space that is not currently assigned to objects or internal machine
functions, and therefore is available on the unit.</TD2><TD3 valign="top">PD (15,0)</TD3></TR>
<TR><TD1 valign="top">DSASP</TD1><TD2 valign="top">ASP number: Specifies the ASP to which this unit is currently allocated.
A value of 1 specifies the system ASP. A value from 2 through 32 specifies
a basic ASP. A value from 33 to 255 specifies an independent ASP. A value
of 0 indicates that this unit is currently not allocated.</TD2><TD3 valign="top">PD (5,0)</TD3></TR>
<TR><TD1 valign="top">DSCSS</TD1><TD2 valign="top">Reserved</TD2><TD3 valign="top">C (2)</TD3></TR>
<TR><TD1 valign="top">DSPCAP</TD1><TD2 valign="top">Reserved</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSPAVL</TD1><TD2 valign="top">Reserved</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DMFLAG</TD1><TD2 valign="top">' ' means this arm is not locally mirrored. 'A' means this is the designated
first arm of a locally mirrored pair. 'B' means this is the designated second
arm of a locally mirrored pair.</TD2><TD3 valign="top">C (1)</TD3></TR>
<TR><TD1 valign="top">DMSTS</TD1><TD2 valign="top">Local mirroring status. 1 = active, 2 = resuming, 3 = suspended</TD2><TD3 valign="top">PD (1,0)</TD3></TR>
<TR><TD1 valign="top">DMIRN</TD1><TD2 valign="top">Locally mirrored IOP resource name</TD2><TD3 valign="top">C (10)</TD3></TR>
<TR><TD1 valign="top">DMDRN</TD1><TD2 valign="top">Locally mirrored device resource name</TD2><TD3 valign="top">C (10)</TD3></TR>
<TR><TD1 valign="top">DSRDS</TD1><TD2 valign="top">Number of read data commands.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSWRTS</TD1><TD2 valign="top">Number of write data commands.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSBUFO</TD1><TD2 valign="top">Number of buffer overruns: The number of times that data was available
to be read into the disk controller buffer from the disk, but the disk controller
buffer still contained valid data that was not retrieved by the storage device
controller. Consequently, the disk had to take an additional revolution until
the buffer was available to accept data. This field is 0 for disk drive type
6100.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSBUFU</TD1><TD2 valign="top">Number of buffer underruns: The number of times that the disk controller
was ready to transfer data to the disk on a write, but the disk controller
buffer was empty. The data was not transferred in time by the disk IOP to
the disk controller buffer. The disk was forced to take an extra revolution
awaiting the data. This field is 0 for disk drive type 6100.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSMDLN</TD1><TD2 valign="top">Model Number: The model number of the disk drive.</TD2><TD3 valign="top">C (4)</TD3></TR>
<TR><TD1 valign="top">DSDCRH</TD1><TD2 valign="top">Device cache read hits: The number of times that all of the data requested
by the read operation was obtained from the device read or write cache.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSDCPH</TD1><TD2 valign="top">Device cache partial read hits: The number of times that a portion,
but not all, of the data requested by the read operation was obtained by the
device read or write cache. A physical operation to the device media was required
to obtain the remaining data.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSDCWH</TD1><TD2 valign="top">Device cache write hits: The number of times that the data associated
with a write operation replaces, or is combined with, existing data in the
device write cache, thereby eliminating a write operation.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSDCFW</TD1><TD2 valign="top">Device cache fast writers: The number of times that space was available
in the device write cache for the data associated with a write operation and
a response was returned immediately.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSDROP</TD1><TD2 valign="top">Device read operations: The number of read operations issued to the
device by the controller. This includes operations generated for redundant
system data areas. It does not include operations generated for diagnostics
or access to the controller reserved area that occur during this idle time.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSDWOP</TD1><TD2 valign="top">Device write operations: The number of write operations issued to the
device by the controller. This includes operations generated for redundant
system data areas. It does not include operations generated for diagnostics
or access to the controller reserved area that occur during this idle time.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSCCRH</TD1><TD2 valign="top">Controller cache read hits: The number of times that all of the data
requested by the read operation was obtained from the controller read or write
cache.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSPCPH</TD1><TD2 valign="top">Controller cache partial read hits: The number of times that a portion
of the data requested by the read operation was obtained from the controller
read and write cache. An operation to the device was required to obtain the
remaining data.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSCCWH</TD1><TD2 valign="top">Controller cache writes hits: The number of times that the data associated
with the write operation replaces or is combined with existing data in the
controller write cache. This eliminates a write operation.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSCCFW</TD1><TD2 valign="top">Controller cache fast writes: The number of times that space was available
in the controller write cache for the data associated with a write operation
and a response was returned immediately.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSCOMP</TD1><TD2 valign="top">Compressed Unit indicator. '0' if disk data is not compressed and '1'
if disk data is compressed.</TD2><TD3 valign="top">C (1)</TD3></TR>
<TR><TD1 valign="top">DSPBU</TD1><TD2 valign="top">Physical blocks used. For compressed units, this field contains the
total number of physical blocks used (written) in the device user data area.
For non-compressed units, this field contains 0.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSPBA</TD1><TD2 valign="top">Physical blocks allocated. For compressed units, this field contains
the total number of physical blocks committed (reserved) in the device user
data area for DASD extents. This value includes all of the Physical Blocks
Used. For non-compressed units, this field contains 0.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSLBW</TD1><TD2 valign="top">Logical blocks written. For compressed units, this field contains the
total number of logical blocks written in the device user data area. This
value represents the total amount of data written to allocated extents. For
non-compressed units, this field contains 0.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSLBA</TD1><TD2 valign="top">Logical blocks allocated. For compressed units, this field contains
the total number of logical blocks contained in allocated compression groups.
This value represents the total sum of all allocated compression groups in
the device user data area. For non-compressed units, this field contains 0.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSPBCO</TD1><TD2 valign="top">Physical blocks for compression overhead. For compressed units, this
field contains the total number of physical blocks that are used for compression
directory structures and reserved areas that are unavailable for storing user
data. For non-compressed units, this field contains 0.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSFGDR</TD1><TD2 valign="top">Foreground directory reads. For compressed units, this field is the
number of device read operations that have been performed to read directory
structures required to complete host system commands. For non-compressed units,
this field contains 0.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSFGDW</TD1><TD2 valign="top">Foreground directory writes. For compressed units this is the number
of device write operations that have been performed to write directory structures
required to complete host system commands. For non-compressed units, this
field contains 0.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSBGDR</TD1><TD2 valign="top">Background directory reads. For compressed units, this is the number
of device read operations that have been performed in the management of compression
directory structures, but were not immediately required to complete host system
commands. For non-compressed units, this field contains 0.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSBGDW</TD1><TD2 valign="top">Background directory writes. For compressed units, this is the number
of device write operations. For non-compressed units, this field contains
0.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSFGRE</TD1><TD2 valign="top">Foreground read exceptions. For compressed units, this is the number
of times an additional device read operation was issued to read data that
had been stored in the exception area on a compressed device (this count applies
only to multi-page operations). This count reflects only those operations
immediately required to complete host system commands.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSFGWE</TD1><TD2 valign="top">Foreground write exceptions. For compressed units, this field is the
number of times an additional device write operation was issued to write data
into the exception area on a compressed device (this count applies only to
multi-page operations). This count reflects only those operations immediately
required to complete host system commands. For non-compressed units, this
field contains 0.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSFGS</TD1><TD2 valign="top">Foreground sweeps. For compressed units, a sweep is the process used
to store a 1-MB compression group in the correct number of sectors so there
are no unused areas in the data region and no used areas in the exception
region of the compression group. The number of foreground sweeps is the number
of times an entire 1-MB compression group was required to be swept to complete
host system commands. The sweep is needed because the data for a host system
write operation does not fit into the physical space reserved. The new data
does not compress as well as the data that was previously in the space. For
non-compressed units, this field contains 0.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSBGS</TD1><TD2 valign="top">Background sweeps. For compressed units, a sweep is the process used
to store a 1-MB compression group in the correct number of sectors so there
are no unused areas in the data region and no used areas in the exception
region of the compression group. The number of background sweeps is the number
of times an entire 1-MB compression group was swept to maintain the compressed
data storage efficiency. This count reflects only those sweeps that were not
immediately required to complete host system commands. Background sweeps are
intended to increase performance or increase usable capacity of drive. For
non-compressed units, this field contains 0.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSCERC</TD1><TD2 valign="top">Controller simulated read cache hits: The number of times that all
of the data requested by the read operation could have been, but was not,
obtained from a controller read cache (not the controller write cache). This
field is updated only when Extended Adaptive Cache Simulator is enabled.</TD2><TD3 valign="top">PD (11,0)</TD3></TR>
<TR><TD1 valign="top">DSASPN</TD1><TD2 valign="top">ASP resource name. Specifies the resource name of the ASP to which
this unit is currently allocated. A value of blanks specifies the system ASP
or a basic ASP.</TD2><TD3 valign="top">C (10)</TD3></TR>
<TR><TD1 valign="top">DSPS</TD1><TD2 valign="top">Parity set. <span>The valid value for this field is '1' or
'0'.</span> The value of this field is '1' when the disk unit is in a parity
set; otherwise, it is  '0'.</TD2><TD3 valign="top">C (1)</TD3></TR>
<TR><TD1 valign="top">DSHAPS</TD1><TD2 valign="top">High availability parity set. <span>The valid value for this
field is '1' or '0'.</span> The value of this field is '1' when the disk unit
is in a high availability parity set; otherwise, it is  '0'.</TD2><TD3 valign="top">C (1)</TD3></TR>
<TR><TD1 valign="top">DSMU</TD1><TD2 valign="top">Multipath unit. <span>The valid value for this field is '1'
or '0'.</span> The value of this field is '1' when the disk resource represents
a multipath disk unit (see note <A HREF="#rzahxqapmdisk__qapmdisknote5" shape="rect">5</A>);
otherwise, it is '0'.</TD2><TD3 valign="top">C (1)</TD3></TR>
<TR><TD1 valign="top">DSIP</TD1><TD2 valign="top">Initial path of multipath unit. <span>The valid value for
this field is '1' or '0'.</span> The value of this field is '1' when the disk
resource represents the initial path of a multipath disk unit; otherwise it
is  '0'. The initial path is the first path observed by the system. It can
change after restarting the system (IPL). The resource name of the initial
path can be used for reporting a multipath disk unit under a single resource
name.</TD2><TD3 valign="top">C (1)</TD3></TR>
<TR><TD1 valign="top">DSPC</TD1><TD2 valign="top">Production copy of remotely mirrored independent ASP. <span>The
valid value for this field is '1' or '0'.</span> The value of this field is
'1' when the disk unit is in a production copy of a remotely mirrored independent
ASP; otherwise, it is  '0'.</TD2><TD3 valign="top">C (1)</TD3></TR>
<TR><TD1 valign="top">DSMC</TD1><TD2 valign="top">Mirror copy of remotely mirrored independent ASP. <span>The
valid value for this field is '1' or '0'.</span> The value of this field is
'1' when the disk unit is in a mirror copy of a remotely mirrored independent
ASP; otherwise, it is  '0'.</TD2><TD3 valign="top">C (1)</TD3></TR>
<TR><TD1 valign="top"><span>DSRDT</span>	</TD1><TD2 valign="top"><span>RAID type: type of RAID parity set for
this disk unit. The valid value for this field is '1' or '0'. This field
only has meaning for disk units in a parity set (DSPS field set to '1'). 
'0' = RAID 5 parity set, '1' = RAID 6 parity set.</span></TD2><TD3 valign="top"><span>C (1) </span></TD3></TR>
<TR><TD1 valign="top"><span>DSIOPF</span>		</TD1><TD2 valign="top"><span>Managed by IOP (See note <A HREF="#rzahxqapmdisk__qapmdisknote6" shape="rect">6</A>).
The valid value for this field is '1' or '0'. The value of this field is '1'
when this disk unit is attached to the disk storage adapter which is managed
by IOP; otherwise, it is  '0'.</span></TD2><TD3 valign="top"><span>C (1) </span></TD3></TR>
<TR><TD1 valign="top"><span>DSCAT</span>	</TD1><TD2 valign="top"><span>Disk unit category. This field indicates
if this disk unit has some special characteristics, which may require a special
interpretation of its performance data. This can also be determined by examining
device type and model for this disk unit. X’00’ = no special category applies,
X’01’ = this disk unit is located in external storage media.</span>	</TD2><TD3 valign="top"><span>C (1) </span></TD3></TR>
</TABLE>