3. USAGE GUIDELINES › 3.1 Setting Up VCC for Operation › 3.1.5 VCC Reporting › 3.1.5.2 VCC Run Status/Run Statistics
3.1.5.2 VCC Run Status/Run Statistics
The following reports generated by the standard DASD
collection process are described below:
o VCC Initialization and Parameter Message Log
o VCC Processing Summary
o VTOC Scan Summary
o Catalog Scan Summary
o IBM DFSMS Storage Group Summary
The following reports generated by the USS File System
Collector are described below:
o Processing Summary
o File System Summary
VCC Initialization and Parameter Message Log
This section of the VCC Run Status Report is produced during
standard VCC initialization. VCCNTRL initialization error
messages, an echo of the run-time parameters, and parameter
scan error messages appear in this section. See the VCCNTRL
and VCCPARSE message descriptions in Chapter 7, Return Codes
and Messages, for a list of these messages.
Figure 3-1 shows a typical Initialization and Parameter
Message Log.
VCC Processing Summary
This section of the VCC Run Status Report is produced by both
the standard and USS File System collection process just
prior to termination.
Figure 3-4 contains a typical example of the standard VCC
Processing Summary. Figure 3-10 contains a typical example
of the Processing Summary for the HFS collection process.
The following describes the entries produced by both
collection processes.
Catalog Scan Elapsed Time - The total elapsed time, in
hh:mm:ss.th format, it took VCC to process
the master and all user catalogs on the
systems that were selected to be scanned.
Central Processors - The number of central processors online
and available for use on the z/OS image that
VCC was executing.
Collection CPU Time - The total amount of CPU usage time.
Collection Duration - The total elapsed time in hours,
minutes, seconds, and hundredths of seconds
that VCC took to perform the SCAN process.
Collection Error Messages Issued - The number of error
(TYPE=E) messages contained in the VCC
Message log.
Collection Highest Completion Code - The highest condition
code passed to z/OS by VCC.
Collection Warning Messages Issued - The number of warning
(TYPE=W) messages contained in the VCC
message log.
Collector Records Written - The number of records that VCC
wrote. These records are either written to
SMF or to a data set (user-selectable VCC
option).
Collector Run Number - The internal number generated by VCC
for identifying each unique collection
execution.
Collector Subtasks Started - The total number of subtasks
started by VCC to perform the scan process.
Collector Subtask Buffer Wait Count - The total number of
times that a VCC subtask had to wait for
output buffers. Use this value to determine
the value of the NUMWTRBUF VCC run-time
parameter.
DASD Devices Online - The total number of DASD devices in the
I/O configuration of the system on which VCC
executed. This is the number of devices in
the volume table built by VCC initialization
(see Chapter 5, Operation).
DASD Devices Scanned - The count of the number of DASD
devices in the I/O configuration that were
eligible to be processed by VCC. This takes
into account INCLUDE/EXCLUDEVOL. It is the
number of DASD devices in the VSCT (see
Chapter 5, Operation).
Free Extent Thresholds - Displays the distribution threshold
values specified by the user or defaulted
by the system. These values are used to
provide a distribution analysis of the
amount of free space on a DASD volume. Each
value represents the maximum number of DASD
tracks for inclusion in the threshold level.
HFS Data Sets Detected - The number of Hierarchical File
System data sets that VCC detected during
the VTOC scan process.
ICF BCS Catalog Records - The number of ICF BCS records VCC
read during the catalog scan process.
ICF BCS Catalogs Scanned - The number of ICF Basic Catalog
Structure (BCS) data sets that were scanned
by VCC.
ICF BCS NonVSAM Records - The number of ICF BCS records
related to non-VSAM catalog entries VCC read
during the catalog scan process.
ICF VVDS Catalog Records - The number of ICF VVDS records VCC
read during the catalog scan process.
ICF VVDS Catalogs Scanned - The number of ICF VSAM volume
data sets (VVDSs) that were scanned by VCC.
ICF VVDS NonVSAM Records - The number of ICF VVDS records
related to non-VSAM entries VCC read during
the catalog scan process.
IPL Volume - The volume serial number of the system
resident DASD volume.
Max DSCB Extent Queue Length - The largest number of VTOC
Format 3 DSCB entries in the DSCB resolution
queues at any one time.
Max DSCB Dataset Queue Length - The largest number of VTOC
DSCB chain resolution entries in the DSCB
resolution queues at any one time.
Operating System Level - The version level and function
modification ID (FMID) of the operating
system on which VCC was executed, displayed
primarily to provide information to
Technical Support, if needed. For
assistance, contact Technical Support at
http://ca.com/support.
PDSE Data Sets Analyzed - The number of PDS/E type data sets
that were successfully processed during the
VTOC scan process.
PDSE Data Sets Detected - The number of PDS/E type data
sets that VCC detected during the VTOC scan
process.
Physical Processors Detected - The number of central
processors online and available for use on
the z/OS image that VCC was executing.
Previous Collection Run On System - The name of the last z/OS
system that ran VCC.
Previous Collection Date - The date and time of the last
successful VCC run. The timestamp shown is
placed in the VCC record and is used by the
CA MICS Space Collector Option to compute
the duration to use for DASD space charging
in Accounting and Chargeback. If the VCC
control file is new or null at the time of
the VCC run, the word "UNKNOWN" is placed on
this line and the CA MICS Space Collector
Option computes a default duration based
on VCA parameter generation values.
Previous Process Time - The VCC processing start time and
Julian date for the previous VCC run.
Note: If the last VCC run ended with
condition code zero although no records were
produced (which may or may not indicate an
error), this timestamp is updated. The
timestamp shown is placed in the VCC record
and is used by the CA MICS Space Collector
Option to compute the duration to use for
DASD space charging in Accounting and
Chargeback. If the VCC control file is new
or null at the time of the VCC run, the word
"UNKNOWN" is placed on this line and the CA
MICS Space Collector Option computes a
default duration based on VCA parameter
generation values.
Processing Start Time - The VCC processing start time and
Julian date.
SCP FMID - The function modification ID (FMID) for z/OS
is shown for technical support purposes.
SMFID - The SMF ID of the z/OS image on which VCC
executed.
SMS Level - The version, release, and modification level
of the Data Facility Product (DFP) or System
Managed Storage (SMS) for technical support
purposes. The SMS level is shown in the
format vv.rr.mm.
SMS or DFP Level - The version, release, and modification
level of the Data Facility Product (DFP) or
System Managed Storage (SMS) for technical
support purposes. The SMS level is shown in
the format vv.rr.mm whereas the DFP level is
shown in the format v.r.m.l.
SYSID - The SMF ID of the z/OS image on which VCC
executed.
Sysplex Name - The eight-character name of the z/OS sysplex
of which this system image is a member.
System Name - The eight-character name of the z/OS image
on which VCC executed.
System Control Program - The level of z/OS on which VCC was
executed, displayed primarily to provide
information to Technical Support, if
needed. For assistance, contact Technical
Support at http://ca.com/support.
Temporary Datasets Auto-Excluded - IF TEMPDSN=N is in effect
for the VCC run, the count shown indicates
the number of records VCC did not write to
its output data set (VCCDATA).
Total Online DASD Devices - The total number of DASD devices
in the I/O configuration of the system on
which VCC executed. This is the number of
devices in the volume table built by VCC
initialization (see Chapter 5, Operation).
Uncataloged NonVSAM Datasets - If CATCHECK=Y is in effect for
the VCC run, the count of data sets that
were found to be either uncataloged or
invalidly cataloged is shown here. When
CATCHECK=N is in effect, a question mark (?)
is shown to indicate that this statistic is
not known from this VCC scan.
USS File Systems Detected - The number of accessible file
systems detected by VCC.
USS File Systems Monitored - The number of accessible file
systems that VCC generated data for.
USS File System Files Detected - The number of files within a
file system that VCC found.
USS File System Directories - The number of directories
within a file system that VCC found.
VCC Records Bypassed - The number of records that were not
written due to a validity check on the
record length done by VCCWRITR. In some
cases, a bad catalog cell causes a record of
excessive length to be constructed and
passed to VCCWRITR. Rather than abend,
VCCWRITR will SNAP a portion of the record
(up to the maximum LRECL in the DCB) and
count the record as bypassed. Normally, the
count that appears here should be zero. If
non-zero, you can usually examine the SNAP
output and locate the data set name. Other
facilities such as IDCAMS DIAGNOSE or PDF
can be used to determine if a data set or
catalog entry is invalid.
VCC Records Written - The number of records that VCC wrote.
These records are either written to SMF or
to a data set (user-selectable VCC option).
VSAM Catalog Records - The number of VSAM catalog records VCC
read during the catalog scan process. This
number includes direct reads that were done
to get information from catalog extension
records. Therefore, a catalog record can be
counted twice.
VSAM Catalogs Scanned - The number of standard VSAM catalogs
that were actually processed by VCC.
VTOC Dataset Records - The number of VTOC DSCBs that VCC read
during the VTOC scan process.
VTOC Scan Elapsed Time - The total elapsed time, in
hh:mm:ss.th format, it took VCC to process
the VTOCs on the DASD devices that were
selected to be scanned.
zSeries File Systems Detected - The number of zFS type data
sets that VCC detected during the VTOC scan
process.
VTOC Scan Summary
This section of the VCC Run Status Report is a list by DASD
device unit address of every DASD volume in the I/O
configuration whose device type VCC supports. This report
contains the following information:
VOLUME - The volume serial number of the DASD device.
UNIT ADDR - The unit address of the DASD device.
DEVICE TYPE - The device type of the DASD device.
Figure 3-7 shows an example of the VTOC Scan Summary.
The following information will be present only if the VTOC
of the DASD device was scanned by VCC.
SCAN ELAPSED TIME - The elapsed time in seconds it took VCC
to scan the VTOC on the device.
%TOTAL SPACE USED - The amount of storage space allocated on
the volume expressed as a percentage.
TOTAL VTOC TRKS - The size of the VTOC in tracks.
DSCB USE STATISTICS - A set of DSCB counts that are useful in
determining:
o VTOC over-/underallocation
o VTOC DSCB spread (how many DSCBs are
used in relation to the high used DSCB)
TOTAL - The total number of preformatted 140-byte
DSCBs in the VTOC.
USED - The number of DSCBs in the VTOC that are in
use (not binary zeros).
F1 - The number of Format 1 (data set identifier)
DSCBs in the VTOC. The sum of this number
and the number of Format 8 DSCBs below
represent the number of data sets on the
DASD device.
F3 - The number of Format 3 (Format 1 data set
extents greater than 3) DSCBs in the VTOC.
F5 - The number of Format 5 (volume free space
extents) DSCBs in the VTOC.
F7 - The number of Format 7 (extended free space
extents) DSCBs in the VTOC.
F8 - The number of Format 8 (data set identifier)
DSCBs in the VTOC. The sum of this number
and the number of Format 1 DSCBs above
represent the number of data sets on the
DASD device. The Format 8 DSCB is used for
data sets that are eligible for placement in
cylinder-managed space on an Extended
Address Volume (EAV).
F9 - The number of Format 9 (data set attribute
information) DSCBs in the VTOC. These DSCBs
occur only in conjunction with Format 8
DSCBs for data sets eligible for placement
in cylinder-managed space on an EAV.
HIGH USED - The DSCB number in the VTOC of the last DSCB
in use. This number is equivalent to the
number of VSAM READ macros issued by VCCVTOC
to read the VTOC.
The fields in the next set indicate specific attributes of
the DASD volume. "Y" indicates that the attribute is
available or true. "N" indicates that it is unavailable.
"?" indicates unknown or unable to determine if the specific
attribute is available.
V I X - Specifies whether a VTOC index exists on the DASD
volume.
V V D - Specifies whether an ICF VVDS exists on the DASD
volume.
I C F - Specifies whether an ICF BCS exists on the DASD
volume.
S M S - Indicates the DFSMS ownership status of this
volume. If an "I" appears in this field, the
volume is in the process of being converted to
SMS. The volume status is "INITIAL," indicating
that some data sets are under SMS control.
S H R - Indicates whether the DASD device is identified to
the operating system as a device that is sharable
between multiple systems.
E A V - Indicates whether the DASD device is identified to
the operating system as an Extended Address Volume
(EAV). An EAV volume is one that is configured
with more than 65,520 cylinders. Cylinder-managed
space exists and extended attribute DSCBs, format
8 and 9 DSCBs, are permitted in the VTOC.
STORAGE GROUP - If SMS is active and the volume is
SMS-managed, the storage group name is
shown.
PROCESS STATUS - Indicates error situations (if any) that
occurred during the scan of a volume. This
report field will be present for all DASD
devices in this section of the VCC Run
Status Report.
The possible status values are:
Device Not Ready - VCC bypassed the
processing of this device because the
device was not ready at the time the
VTOC scan control table (VSCT) was
built.
DSN Residuals - One or more queue elements
for Format 1 DSCBs were found during
end of VTOC processing. This
condition can only occur when an
error condition is encountered that
causes premature termination of scan
processing for a DASD volume.
EXT Not Found - A locate request for a
Format 3 DSCB on the EXT queue
resulted in a not-found condition.
This may be caused by an invalid
pointer in a Format 1 or 3 DSCB as
the result of an interrupted VTOC
update process. The scan result may
or may not be in error depending on
the condition of the VTOC.
EXT Residuals - One or more residual
Format 3 DSCB extent records were
read, but the associated Format 1
DSCB records for them had not been
read by the VCC scan task. This
condition will most likely occur when
processing DASD volumes with
extremely high activity if the
SERIALIZE=N option is in effect for
the VCC scanner. This condition
might also occur as a result of a
system crash that occurred during an
update of the VTOC that has resulted
in a corrupted VTOC.
Incomplete Scan - A DASD volume being
processed encountered an error
condition. One or more data records
have been written to the volume
record free extent segment, but not
all of the VTOC has been successfully
processed.
Lost Tracks - VCC VTOC processing of this
volume could not account for all of
the tracks on the volume. The sum of
the allocated tracks, free tracks,
size of VTOC, and 1 for track 0 did
not equal the track capacity of the
volume.
Migration Level 1 - The DASD volume being
scanned was determined to be a DFHSM
migration level 1 storage volume.
Only the VTOC Volume Record will be
output for this volume, regardless of
the value of the DATAINFO= parameter.
Mount Attributes - VCC processing of this
device was bypassed because the
device was not mounted in a manner
that satisfied the requirements of
VCC (online and resident).
No VTOC Found - VCC was unable to process
a DASD volume because a valid pointer
to the VTOC did not exist in the UCB
for the device.
Processing Error - An error occurred
during the processing of the VTOC on
the DASD device. The VTOC scan log
will contain a description of the
error.
PDSE Extended - The DASD volume was
explicitly specified on an
EXTENDEDPDSE parameter statement
causing extended attribute data for
the PDS/Es on the volume to be
collected.
PDSE No Extended - The DASD volume was
explicitly specified on an
NOEXTENDEDPDSE parameter statement
causing extended attribute data for
the PDS/Es on the volume NOT to be
collected.
Record Overflow - A volume contained more
free space extents than could be
placed into the data record. The VTOC
Volume Record free extent segment
will be incomplete.
Reserve Bypassed - A hardware RESERVE was
not done for this volume before it
was processed. This was because
either the volume was specified in a
BYPASSRES parameter or because the
RESRETRY limit was exceeded and
RESFAILOK=Y was coded or defaulted.
Scan Abend Sxxx - An abend occurred during
scan processing of a DASD volume.
The Sxxx value indicates the abend
code returned by the system. Scan
processing for the volume is
terminated and one of two actions is
taken. If the abend code is
determined to be recoverable, such as
an S213-04 from an invalid VTOC,
processing for the volume is
terminated, the environment is
cleaned up, and processing continues
with the next DASD volume. If the
abend is determined to be
non-recoverable, processing for the
volume is terminated and the scan
subtask terminates after cleanup
processing.
Status Bypassed - The UCB status of the
DASD volume was found to contain
indicators that would prevent
successful scan processing of the
volume. If this condition persists
for three successive attempts, the
volume is permanently bypassed for
this processing execution.
Volume Excluded - VCC bypassed processing
of this device because the device
either was not INCLUDEd or was
specifically EXCLUDEd.
Volume Not Read - A VTOC was not processed
because of a critical error.
Volume Reserved - VCC could not process
this volume because it was reserved
by another user and VCC could not
reserve it. You will receive this
message if the RESRETRY limit was
exceeded and RESFAILOK=N was coded.
VM Volume - Indicates a DASD volume that
has been formatted for use by a VM
operating system. These volumes
either have no VTOC or a non-standard
VTOC that cannot be processed by the
VCC scan task.
Figure 3-7 shows an example of a VCC Run Status Report.
Catalog Scan Summary
This section of the VCC Run Status Report lists the catalogs
that were processed by VCC. The following information is
given:
CATALOG NAME - The name of the catalog that was scanned.
VOLUME - The volume serial number of the DASD device
on which the catalog resides.
UNIT ADDR - The unit address of the DASD device on which
the catalog resides.
CATALOG TYPE - The type of catalog. This value can be:
ICF - for ICF BCS Catalogs
VVDS - for ICF VVDS Catalogs
VSAM - for VSAM catalogs
CATALOG RECORDS READ - The number of records that were read
from the catalog by VCC.
CATALOG ENTRY TYPES - The number of entries in the catalog
that were actually processed by VCC. It can
be any of the following:
VSAM CLUSTER - the number of VSAM clusters
in the catalog.
AIX - the number of alternate
indexes in the catalog.
CATALOG - the number of user catalog
CONNECTOR connector entries in the
catalog that VCC actually
processed.
NONVSAM - the number of non-VSAM
entries in the catalog.
CATALOG PROCESS TIME - The total elapsed time in seconds it
took VCC to scan this catalog or VVDS.
PROCESS STATUS - The error situations that occurred during
the scan of the catalog. The possible
values are:
* Not Read * - A BCS, VVDS or VSAM catalog
was not processed because of a
critical error.
Allocation Error - The catalog could not
be allocated. Check the Catalog Scan
Log for the allocation error return
and reason codes. Refer to the
applicable IBM publication for
information regarding the return and
reason codes.
D/I S-O-F Error - An error occurred during
the processing of a VSAM catalog
record. The data/index cell
sets-of-fields information is not
accurate.
EXT S-O-F Error - An error occurred during
the processing of a VSAM catalog
record. An extension record's
sets-of-fields information is not
accurate.
Locate Error - The catalog could not be
located via SVC 26 (LOCATE).
MODCB Error - An error occurred during the
execution of a VSAM MODCB macro.
Check the Catalog Scan Log for the
MODCB error return and reason codes.
Refer to the applicable IBM
publication for information regarding
the return and reason codes.
Open Error - An error occurred during the
OPEN of a VSAM catalog. Check the
VCC JOBLOG for VSAM error messages.
Refer to the applicable IBM
publication for information regarding
the return and reason codes.
Point Error - An error occurred during the
execution of a VSAM POINT macro.
Check the Catalog Scan Log for the
error return and reason codes. Refer
to the applicable IBM publication for
information regarding the return and
reason codes.
Processing Error - Scan processing for a
BCS, VVDS. or VSAM catalog did not
complete. The interruption was
probably due to an abend condition.
Refer to the Catalog Scan Log for
additional information.
Read Error - An error occurred during the
execution of a VSAM GET macro. Check
the Catalog Scan Log for the error
return and reason codes. Refer to
the applicable IBM publication for
information regarding the return and
reason codes.
SMF Write Error - An error condition code
was returned from the SMFWTM service
while attempting to write the VCC
Catalog record to SMF. Refer to the
Catalog Scan Log for additional
information.
Unknown Status - An error condition was
encountered while processing a BCS,
VVDS, or VSAM catalog. The status
information returned was unknown to
the scan task. Refer to the Catalog
Scan Log for additional information.
Figure 3-5 shows an example of the Catalog Scan Summary.
IBM DFSMS Storage Group Summary
This section of the VCC Run Status Report contains a list
of all the DFSMS storage groups found on the system that
ran VCC. This report contains the following information:
STORAGE GROUP NAME - The name of the DFSMS storage group.
STATUS - The status of the storage group at the
time of the VCC volume VTOC scan (that
is, ENABLED, DISABLED, QUIESCED, and so
on).
TOTAL SPACE (TRACKS) - The total storage capacity in tracks
for the storage group.
PERCENT USED - The percentage of space used for the
storage group.
VOLUME COUNT - The total number of DASD volumes found
that belong to the storage group.
VOLUME LIST - A list of DASD volumes that belong to
the storage group.
Figure 3-6 shows an example of the DFSMS Storage Group
Summary.
