Source: VCADAA file at the DAYS timespan
VCA_VS file at the DAYS timespan
HSMMIG file at the DAYS timespan
Function: This facility allows the storage administrator to
monitor the daily movement of data between real
DASD and HSM migration volumes. Installations
using HSM should experience a daily migration of
less-active data to HSM level 1 and level 2
volumes. If HSM and/or SMS parameters are not set
correctly, or if certain groups or users abuse HSM
commands to cause data set movement, severe
capacity or performance problems may result.
A summary report will analyze the first and last
dates found in the input data, and create a
summary of the changes between those two dates.
This could be used, for example, to analyze data
from a Monday and a Friday and summarize changes
that occurred during the week. If potential
problems are found, history reports can be used to
provide more detailed information about certain
groups or users.
These reports may be useful when changes have been
made to HSM or SMS parameters, to validate the
changes are having their intended effect on the
operation of HSM.
Features: Summarization options allow you to analyze the
data based on its owner (using one or more of the
CA MICS accounting fields), its SMS storage class,
its SMS management class, or by system (SYSID).
These various levels of summarization make it easy
to isolate particular problems or trends.
Data filtering allows you to include data from
selected summary groups. For example, you could
choose to report on specific departments groups or
individuals, or on a specific SMS class.
Output reports from this facility include tabular
reports, printer plots, or color graphic plots.
Reporting can be based on the number of data sets,
the amount of allocated space, or both.
SMS
Issues: The ability to summarize by an SMS storage or
management class makes it easy to monitor the
activity within each of your defined classes. The
ability to filter and summarize by a specific
management class, for example, could be used to
verify that changes made to the HSM parameters in
a management class were working as intended.
ELEMENT DESCRIPTIONS
SYSID
This value appears at the top of each page and
identifies the System Identifier (system) to which
this data applies.
Owner
Specifies the department, group, or individual to
which this chart applies. This value is specified
as a report option, and represents one or more of
the CA MICS accounting fields assigned to a group
of data sets.
Storage Class
If summarization by storage class was requested,
this indicates the name of the SMS storage class
represented by this chart. All of the data sets
assigned to the indicated storage class were
summarized to produce this chart.
Management Class
If summarization by management class was
requested, this indicates the name of the SMS
management class represented by this chart. All
of the data sets assigned to the indicated
management class were summarized to produce this
chart.
Vertical Axis (Value)
The numeric values distributed vertically down the
left side of each page represent the scale of the
numeric values being plotted on that page, and
represent either a count of data sets or the
amount of space allocated. When requesting color
graphics plots, you have the option of specifying
the values that will appear on this axis. This
should be done with care, as all plots and groups
will have to adapt to the values you specify. For
printer plots, or when values are not specified,
SAS will generate the values automatically, based
on the content of the plotted data. We suggest
that these SAS defaults be used whenever possible,
because they will avoid many potential problems.
Horizontal Axis (Date)
Plots on the horizontal axis represent the date
(format ddmmmyy) corresponding to the value being
plotted. The number of entries appearing on the
horizontal axis is determined by the number of
cycles of CA MICS data specified as input to the
report.
Footnotes
Three footnotes will appear at the bottom of each
chart to indicate the values being plotted. The
format of each will vary depending on whether you
requested reporting by space or data sets. The
first three listed below appear for space
reporting, the last three for data set reporting.
Megabytes on Primary Storage
Indicates the amount of space, expressed in
megabytes, allocated on primary DASD volumes
by the data sets in this summary group.
Megabytes on HSM Level 1 Storage
Indicates the amount of space, expressed in
megabytes, allocated on DFHSM migration level
1 volumes by the data sets in this summary
group.
Megabytes on HSM Level 2 Storage
Indicates the amount of space, expressed in
megabytes, allocated on DFHSM migration level
2 volumes by the data sets in this summary
group.
Data Sets on Primary Storage
Indicates the number of data sets allocated on
primary DASD volumes by the users in this
summary group.
Data Sets on HSM Level 1 Storage
Indicates the number of data sets allocated on
DFHSM migration level 1 volumes by the users
in this summary group.
Data Sets on HSM Level 2 Storage
Indicates the number of data sets allocated on
DFHSM migration level 2 volumes by the users
in this summary group.
DASD/HSM DATA MOVEMENT (STGECE) CA MICS StorageMate ABC CORPORATION SYSID=SYSA Owner=FINANCE 15000 + | | 0 14000 + 0 0 | 0 | 0 13000 + | | V 12000 + a | l | u 11000 + e | | 10000 + | | 9000 + 2 2 | 2 2 | 2 8000 + | 1 1 1 1 | 1 7000 + | | 6000 + | | 5000 + | | 4000 + --+-----------------------+-----------------------+-----------------------+-----------------------+--- 01APR07 02APR07 03APR07 04APR07 05APR07 06APR07 Date 0 = Data sets on Primary Storage 1 = Data sets on HSM Level 1 Storage 2 = Data sets on HSM Level 2 Storage
Figure 4-27. DASD/HSM Data Movement / Plot
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |