Source: VCADAA file at the DETAIL timespan
VCA_VS file at the DETAIL timespan
HSMMIG file at the DETAIL timespan
HSBBAC file at the DETAIL timespan
Function: Graphically represents the usage of DFSMS classes
by department.
Monitors the use of various DFSMS classes. It
provides a view of what departments are using a
particular class, detects potential violations,
and ensures that DFSMS is assigning classes
correctly.
DFSMS classes are set either by the user or by the
DFSMS ACS routines, and are used to group data
sets with similar attributes and needs.
Features: The user specifies the type of class to be
summarized (data class, storage class, storage
group, or management class). The chart shows the
class names and the amount of space used by each
department.
Users can report class usage based on one or more
of the account fields, one or more data set name
nodes, or by using a user-defined table that
translates the data set name prefix into an owner
description.
Both color graphics and printer charts are
supported.
SMS This report is useful during SMS implementation to
Issues: ensure that your SMS ACS routines are assigning
class names as designed. After SMS
implementation, the report is useful for
monitoring the usage of SMS classes by various
departments/users.
COLUMN DESCRIPTIONS
Storage Class
The name of the DFSMS Storage Class for which this
chart applies. A value of '(NONE)' is used to
represent data sets that have not been assigned to
any class. The report options screen is used to
select which of the four DFSMS constructs (Storage
Class, Management Class, Data Class, or Storage
Group) will appear on this chart.
Management Class
The name of the DFSMS Management Class for which
this chart applies. A value of '(NONE)' is used
to represent data sets that have not been assigned
to any class. The report options screen is used
to select which of the four DFSMS constructs
(Storage Class, Management Class, Data Class, or
Storage Group) will appear on this chart.
Data Class
The name of the DFSMS Data Class for which this
chart applies. A value of '(NONE)' is used to
represent data sets that have not been assigned to
any class. The report options screen is used to
select which of the four DFSMS constructs (Storage
Class, Management Class, Data Class, or Storage
Group) will appear on this chart.
Storage Group
The name of the DFSMS Storage Group for which this
chart applies. A value of '(NONE)' is used to
represent data sets that have not been assigned to
any group. The report options screen is used to
select which of the four DFSMS constructs (Storage
Class, Management Class, Data Class, or Storage
Group) will appear on this chart. Because Storage
Group is not available for data sets managed by
HSM, values of 'HSM LV1' (migration level 1), 'HSM
LV2' (migration level 2) and 'HSM BACK' (HSM
backup) will appear in this column for HSM data.
Pie Slices
Each slice of the pie represents the total amount
of space allocated by the users of this DFSMS
class or group, expressed in millions of bytes
(megabytes).
Pie Labeling
The label for each pie slice contains the name of
the group represented by that slice. These
summarization groups can be constructed using one
or more VCA account elements, one or more nodes of
the data set name, or using a value derived from
your Data Set Group table.
SMS CLASS USAGE (STGELE) CA MICS StorageMate ABC CORPORATION System Identifier=SYS7 Management Class=STANDARD SUM PIE CHART OF MBATOT GROUPED BY OWNER ********************** SUPPORT-CENTER **** .**** *** . .*** *** . . *** ** . . ** ** .. . ** * . . * ** . . ** TSO-LONG-TERM ** 483.953 ** ** 2.31% ** DATA-BASES ** . .. ** * . . * ** . . ** * 8594.32 . . 3728.74 * * 40.99% ... 17.78% * * .. * * .. * * .. * * . * * * * + . . . . . . . . . . . . * * . . . . . * .. * * . * * . * * . * * .. * * . * * . * ** .. ** * . * ** . ** ** . ** ** .. 8112.58 ** ** 38.69% ** * * ** ** ** ** *** *** *** *** **** **** ********************** SYSTEM-DATA * ALLOCATED SPACE (MEGABYTES) BY GROUP
Figure 4-56. SMS Class Usage / Chart
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |