3. USAGE GUIDELINES › 3.1 Setting Up VCC for Operation › 3.1.4 Scheduling Considerations with CA MICS and DFHSM › 3.1.4.1 Hourly Collection of Volume Data (DATAINFO)
3.1.4.1 Hourly Collection of Volume Data (DATAINFO)
This option allows you to take an inventory of the volumes on
a more frequent basis than the entire inventory you take at
the data set level.
Assuming you would find it useful to collect data about the
changes in key volume level statistics on an hourly basis
during prime shift hours you could "clone" your production
run setup and make several modifications to support this
special type of data collection:
o Establish VCC as a separate PROC in a PROCLIB so a
START command can be automatically issued hourly by
JES2 or by a production scheduling package.
The JCL in this PROC must be different from the JCL in
the PROC for the "daily" version of VCC. Key
differences are the following:
- The "hourly" PROC must ALWAYS allocate a different
VCCNTROL file to preserve the DURATION calculations
needed for data set level processing.
- The "hourly" PROC should allocate VCCDATA to a GDS
(generation data set).
- The "hourly" PROC should allocate a VCCPARMS data
set that specifies:
DATAINFO=N (VCC writes only 1 record per VOLSER)
HSM=N (only collect DFHSM inventory daily)
SERIALIZE=N (no RESERVEs on VTOCs)
CATCHECK=N (no LOCATEs to slow down scanning)
VSAMSUBT=0 (no reading catalogs or VVDSs)
VTOCSUBT=16 (specify a high level of multitasking)
INCLUDEVOL or EXCLUDEVOL statements are allowed to
subset the data if desired. For example, all volumes
belonging to a storage group in which only temporary
data sets are allocated could represent a pool of
volumes you would like to monitor hourly with this
method. INCLUDEVOL is a facility for subsetting the
scanning accordingly along with the above list.
