|
|
|
The CA MICS Space Collector Option (VCC) processes IBM VTOC and catalog information. It collects data pertaining to DASD storage usage and capacity and feeds that data to the CA MICS Space Analyzer Option (VCA), which stores it in the CA MICS database. The CA MICS Space Analyzer Option provides you with information and reports that help you to better manage your current storage environment by identifying problem areas in storage utilization, performing capacity planning and costing, and tracking and charging for storage usage. The CA MICS Space Collector Option performs two batch operations that can be used to feed data into the DAILY process of the CA MICS Space Analyzer Option for analysis. Along with the standard batch job, a batch job to collect Hierarchical File System (HFS) and zSeries File System (zFS) information can also be executed. The flow of data is displayed graphically in Figure 1-1.
DATA SOURCES +----------+ +-------------+ +-------------+ +----------+ +---------+ +---------+ | Indexed/ | | ICF | | VSAM | | DFHSM | | DFSMS | | OS/390 | | Standard | | Master/User | | Master/User | | MCDS and | | Address | | UNIX | | OS VTOCs | | Catalogs | | Catalogs | | BCDS | | Space | | (OMVS) | +----------+ +-------------+ +-------------+ +----------+ +---------+ +---------+ | | | | | | +----------------+----------------+-----------------+--------------+------------+ | | V ********************************************** ** CA MICS Space Collector Option ** ** (VCC) **<----+ ** ** | ********************************************** | | | | | +---------------+ | | | | +-+-------------+ | | | | | | Statistics & | | | | | +-----------+ | Error Reports |-+<--------+ | | | Control | | | | +-------------->| Data set | +---------------+ | | | | +-----------+ +---(or)---+---(or)---+ | | | | V V +------------+ +----------+ | Sequential | | SMF | | File | | | +------------+ +----------+ | | V V +----------+----------+ | | V +-----------------------------------+ | CA MICS Space Analyzer Option | | (VCA) | +-----------------------------------+ | V +------------------+ | | | CA MICS Database | | | +------------------+ | +---------+ +----------+ | +-+-------+ | | Terminal |<------------+------------>| Reports |-+ +----------+ +---------+
Figure 1-1. CA MICS Space Collector Option Data Flow
VCC's capabilities fall into the following categories:
o Product flexibility
o Data source facilities
o Support for IBM's Data Facility System Managed Storage
(DFSMS)
o Support for IBM's Data Facility Hierarchical Storage
Manager (DFHSM)
o Report facilities
o Data collection options and features
Product Flexibility
o VCC operates on all CA MICS-supported IBM z/OS
systems. Although it is designed to run below the
16-megabyte line on MVS/XA, it automatically changes
its addressing mode to run in 31-bit mode when it
references control blocks that reside above the
16-megabyte line.
o Because VCC has the option to reserve VTOCs, it
automatically modifies itself to run as nonswappable.
This is important, particularly in shared DASD
environments where an address space swap out can
result in several devices being held in reserve for
long periods of time. Running as nonswappable, VCC
ensures that device reserves are short, which keeps
devices available; it also ensures that other possible
CPU problems related to swap out do not occur.
o VCC keeps track of the last time it scanned a volume
so that you can calculate track-days, etc. This
allows you the flexibility of running VCC once a day
on all volumes or once an hour on high-activity
volumes.
Data Source Facilities
VCC obtains its information from the following data sources:
o Standard OS VTOCs
o Indexed VTOCs
o Standard VSAM master and user catalogs
o Master and user catalogs (VSAM and ICF)
o VSAM Volume Data Sets (VVDSs)
o The Migration Control Data Set (MCDS) and Backup
Control Data Set (BCDS) maintained by DFHSM
o z/OS UNIX System Services (USS) Hierarchical File
Systems
VCC reads Direct Access Storage Device volumes (DASD) to
obtain information from the following IBM or
vendor-equivalent device types:
o 2105 o 3380 (all models)
o 3340 o 3390 (all models)
o 3350 o 9345 (all models)
o 3375
The DASD volumes scanned must be online when VCC starts
running. It does not collect information from mass storage
devices and does not scan OS CVOLs because most users have
converted their OS CVOL catalogs to either VSAM or ICF
catalogs.
Using the data sources listed above, VCC gathers the
following data:
o Storage class, management class, data class, and
storage group names if available and applicable.
Storage group and Management class definition
information is available if DFSMS is active on the
host running VCC.
o The catalog status for VTOC data sets. This optional
check of whether data sets are properly cataloged
assists in storage management and migration to SMS.
o All Format 1 and 3 DSCB information, including data
set attributes and detailed extent information, found
in indexed and nonindexed VTOCs for VSAM and VTOC data
sets.
o All Format 4 DSCB information that describes the VTOC.
o Format 5 DSCB volume free space extent information.
If the VTOC is indexed, the interface to IBM's Common
VTOC Access Facility (CVAF) retrieves this information
from the index.
o Catalog information about VSAM data sets, including
how the data set was defined, data set extents on each
volume for both data and index components, and
alternate index information.
o Information taken from the self-describing records at
the beginning of each VSAM catalog, which is used to
manage the VSAM catalogs.
o Data that VCC generates when it encounters unusual
situations (for example, VTOC errors, broken DSCB
chains, and VSAM catalog errors) during the data
collection process
o Data set name, SMS class names, and basic space
allocated information for data sets migrated and
backed up by DFHSM.
o Capacity planning information from DFHSM for DASD and
tape volumes under control of DFHSM.
o Statistics and attributes from USS Hierarchical File
Systems residing on z/OS. This includes information on
the individual files within the file systems.
Support for IBM's Data Facility Hierarchical Storage Manager
(DFHSM)
The VCC interface to DFHSM allows you to create an inventory
of DFHSM-related information in a sequential data set or as
SMF records. If you use DFHSM, this inventory collects
information on inactive data that no longer resides on
primary DASD as well as on backup versions that reside on
DFHSM-managed tapes. This inventory allows you to measure
the growth of resources allocated to DFHSM and to account to
end users for this service. The CA MICS Space Analyzer
Option adds inventory data to the database.
Support for z/OS UNIX Systems Services (USS)
VCC provides the ability to obtain information for each
individual file within a mounted file system which resides on
z/OS DASD. Once this information is processed by the CA MICS
Space Analyzer Option and populated into the database, it can
be used to measure the growth of POSIX compliant files and
track its utilization over time.
Report Facilities
VCC provides reports that summarize the data that it reads.
These reports are designed to help you track VCC operation
and verify that it has read the appropriate VTOCs and
catalogs. More report information is available later in this
chapter.
Data Collection Options and Features
VCC offers a complete set of options and features to control
and enhance its high-speed data collection process. You can
specify various options by using parameters that VCC
processes prior to its data collection. VCC options and
features include the following:
o The ability to exploit host processors with multiple
CPUs by employing subtasking methodology. This feature
allows VCC to perform data collection at high speed.
o An INCLUDE or EXCLUDE list of volumes (selected by
volume serial number and/or device address), data
sets, catalogs, and mounted File Systems to
be processed or excluded from processing.
o The ability to:
- Specify the master catalog name, type (ICF or
VSAM), and location.
- Write data records to SMF or to a user-defined data
set.
- Specify a user-defined SMF record number for the
output records.
- Specify the number of subtasks used in performing
data collection.
- Selectively generate reports.
- Specify weather to collect information from:
- VTOCs
- ICF and VSAM Catalogs
- Mounted File Systems
- Hierarchical Storage Manager (DFSMS)
- Specify internal VCC performance tuning parameters.
- Detect and report both catalog structure errors and
VTOCs that are too small.
Most parameters have defaults. If VCC runs without a
parameter list, it will record all VTOC data on all online,
resident, and ready DASD devices. It will also scan all
supported catalogs on those volumes that are online and
ready.
This section contains the following topics:
1.1 Primary Areas of Application
1.2 Reporting and Inquiry Facilities
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |