|
|
|
Source: VCAVOA file at the DETAIL timespan
HARDVA file at the DAYS timespan
Function: Concisely summarizes performance and capacity
information at the device type level. This
information is reported for each unique device
type and for each logical system (SYSID).
This makes it easy to identify potential
performance, capacity or balance problems at the
device type level.
Users planning for storage products that support
volume pooling can use this report to design
volume groupings that will find combinations that
provide optimum availability and free space.
Features: Two different CA MICS files are combined to
produce this report; one provides space
information and the other provides performance
information. The HARDVA file can be filtered at
the hour or zone level so that the performance
information reflects a specific time period.
Volumes that appear in the HARDVA file but not the
VCAVOA file (because they were not scanned) can be
included or excluded by user option. If included,
values for these volumes are not included in the
space totals, but are included in the response
time and I/O rate values.
Generation of the summary report is automatic.
SMS The response time and capacity values obtained
Users: from this report can help when defining SMS
storage classes and storage groups.
COLUMN DESCRIPTIONS
Device Type
The type of I/O device.
Number of Volumes
The number of volumes found within the input data
that were found to have this device type.
Total Capacity (MB)
The total potential capacity of all the volumes of
this device type, expressed in millions of bytes
(megabytes).
Space Allocated (MB)
The total amount of space allocated by all the
data sets on all the volumes of this device type,
expressed in millions of bytes (megabytes).
Space Used (MB)
The total amount of space used by all the data
sets on all the volumes of this device type,
expressed in millions of bytes (megabytes).
Space Free (MB)
The total amount of space free (unallocated) on
all the volumes of this device type, expressed in
millions of bytes (megabytes).
Total Data Sets
The total number of data sets residing on all the
volumes with this device type.
Non-VSAM # Data Sets
The number of non-VSAM data sets residing on all
the volumes with this device type.
Non-VSAM Alloc (MB)
The total amount of space, expressed in millions
of bytes (megabytes), allocated by all the
non-VSAM data sets residing on volumes with this
device type.
VSAM # Data Sets
The number of VSAM data sets residing on all the
volumes with this device type.
VSAM Alloc (MB)
The total amount of space, expressed in millions
of bytes (megabytes), allocated by all the VSAM
data sets residing on volumes with this device
type.
Average I/O Rate
The total number of I/O requests per second being
received by all the volumes with this device type.
This value is the sum of the rates for the
individual volumes within the summarization.
Average Response Time
The average time a user of this device type waits,
in thousandths of a second (milliseconds), for an
I/O request to complete. This is recalculated at
the device type level, using the same technique
used to calculate this value for an individual
volume.
VOLUME CONFIGURATION (STGEPB) 5 CA MICS StorageMate - SUMMARY ABC CORPORATION ----------------------------------------------------- System Identifier=SYS7 ----------------------------------------------------- Device Number Total Space Space Space Total +-- Non-VSAM --+ +---- VSAM ----+ +-- Average --+ Type of Capacity Allocated Used Free Data # Data Alloc # Data Alloc I/O Response Volumes (MB) (MB) (MB) (MB) Sets Sets (MB) Sets (MB) Rate Time 3380 78 49664.77 42616.69 27858.76 6836.06 14773 13812 36105.71 961 6510.98 2.640 0.026 3390-2 10 6367.32 6228.07 4778.48 106.97 2399 2300 5606.31 99 621.76 1.537 0.026 -------- ----- --------- --------- --------- --------- ------- ------- --------- ------- --------- ------ ------ SYSID 88 56032.09 48844.76 32637.24 6943.03 17172 16112 41712.02 1060 7132.74 2.515 0.026
Figure 4-70. Volume Configuration / Summary
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |