3. USAGE GUIDELINES › 3.1 Setting Up VCC for Operation › 3.1.1 Selecting the Runtime Parameters › 3.1.1.2 Runtime Parameter Specification
3.1.1.2 Runtime Parameter Specification
VCC parameter specification follows much the same rules that
govern most 80-byte card parameter formats. Every attempt
has been made to simplify the format of the run-time
parameters. The rules for the VCC parameter set are the
following:
o Use columns 1 through 72 inclusive to enter VCC
parameters.
o Begin parameters in any of the above columns of a card
image.
o You cannot continue parameters that do not contain a
list of values to another card.
o A parameter list is a series of values enclosed in
parentheses and separated by commas. Nested
parentheses are not allowed. You can continue a
parameter list onto another card image by specifying a
comma followed by a blank. The only limit to the
number of continuation cards for a parameter is the
maximum number of values that are allowed for the
parameter.
o Specify all data set names, volume serial numbers, and
device addresses generically by coding an asterisk (*)
as the terminator for the value.
o Comment statements are recognized by an asterisk (*)
in column 1 of a card image.
o Specify comments following each card image parameter
statement or list value as long as there is at least
one blank following the parameter specification.
o The VCC run-time parameter formats are divided into
the following categories:
- Parameter keywords with one operand.
- Parameter keywords with a list of operands enclosed
in parentheses. The parentheses must be coded,
even if only one operand is entered.
o You must separate an operand from the parameter
keyword specification by an equal sign (=) with no
intervening blanks.
VCC Run-time Parameters Summary Table
+------------------+------------------------+-------+-------+
| Parameter | Specification |Default| Notes |
+------------------+------------------------+-------+-------+
|BYPASSBKUP |Y or N |N | 4,5 |
|BYPASSRES |(volser,...,volser) | | 4,5 |
|CATCHECK |Y or N |N | 3 |
|DATAINFO |Y or N |Y | 1 |
|DATALEVEL |(ALL,HFSDIR,TEMP) |ALL | 1,6 |
|DIAGDUMP | | | 6,8,9 |
+------------------+------------------------+-------+-------+
|EXCLUDECAT |(dsn,dsn,...,dsn.*) | | 3 |
|EXCLUDEDEV |(dev,dev,...,dev) | | 3,H |
|EXCLUDEDSN |(dsn,dsn,...,dsn.*) | | 3 |
|EXCLUDEDV4 |(dev,dev,...,dev) | | 3,H |
|EXCLUDEPATH |(path,path,...path) | | 3,6 |
|EXCLUDEVOL |(volser,...,volser) | | 3 |
|EXCLUDVVDS |(dsn,dsn,dsn,dsn.*) | | 3 |
+------------------+------------------------+-------+-------+
|EXTENDEDPDSE |(volser,...,volser) | | 1,2 |
|FXTHRESHOLD |(trk1,trk2,...,trk7) | | 3 |
|HFSERR |numeric value (1-16) |0 | 4,6 |
|HFSDIRBUFFER |numeric value (8-256) |16 | 4,6 |
|HFSDIRLEVEL |numeric value (1-512) |32 | 4,6 |
|HFSSUBT |numeric value (1-16) |CPUs*3 | 4,6 |
|HSM |Y or N |N | 1 |
|HSMBACKUP |Y or N |Y | 1 |
|HSMMIGRATE |Y or N |Y | 1 |
|HSMSMF |Y or N |N | 1 |
|HSMSMFID |numeric value |197 | 1 |
+------------------+------------------------+-------+-------+
|INCLUDECAT |(dsn,dsn,...,dsn .*) | | 3 |
|INCLUDEDEV |(dev,dev,...,dev) | | 3,H |
|INCLUDEDSN |(dsn,dsn,...,dsn.*) | | 3 |
|INCLUDEDV4 |(dev,dev,...,dev) | | 3,H |
|INCLUDEPATH |(path,path,...path) | | 3,6 |
|INCLUDEVOL |(volser,...,volser) | | 3 |
|INCLUDVVDS |(dsn,dsn,dsn,dsn.*) | | 3 |
|LINECOUNT |numeric value (30-999) |60 | 5 |
+------------------+------------------------+-------+-------+
|NUMWTRBUF |numeric value (5-200) |25 | 4,5 |
|OPERMSGS |Y or N |Y | 5 |
|REMOVEMNT |Y or N |N | 3 |
|RESERVEMNT |Y or N |N | 3 |
|RESFAILOK |Y or N |Y | 4,5 |
|RESRETRY |numeric value (1-250) |10 | 4,5 |
+------------------+------------------------+-------+-------+
|SERIALIZE |Y or N |N | 4,5 |
|SMF |Y or N |N | 1 |
|SMFID |numeric value |198 | 1 |
|SPACEUSEDEQALLOC |Y or N |Y | 1,2,3 |
|SREPORT |Y or N |Y | 2 |
|STATUS | | | 6,8 |
+------------------+------------------------+-------+-------+
+------------------+------------------------+-------+-------+
| Parameter | Specification |Default| Notes|
+------------------+------------------------+-------+-------+
|TEMPDSN |Y or N |N | 1 |
|TEST |Y or N |N | 4,9 |
|TRACE |Y or N |N | 4,5,9 |
|UNCATPDSE |Y or N |N | 4,5 |
|USEREXIT |Y, N or module_name |N | 6,7 |
|USERIDZERO |user_id_name |BPXROOT| 6 |
|VSAMERR |numeric value (1-16) |0 | 4 |
|VSAMSUBT |numeric value (1-16) |4 | 4 |
|VTOCERR |numeric value (1-16) |0 | 4 |
|VTOCSUBT |numeric value (1-16) |8 | 4 |
|WTO |Y or N |Y | 5 |
+------------------+------------------------+-------+-------+
Notes Legend:
------------
1 - Keyword affects data recording
2 - Keyword affects reporting
3 - Keyword affects scan processing
4 - Keyword affects performance
5 - Keyword modifies operational characteristics
6 - Keyword applies only to USS file system job (VCCRUNH)
7 - Module_name applies only to USS file system job (VCCRUNH)
8 - Parameter is supplied via z/OS Modify Operator command
9 - Technical Support use only
H - Keyword is not supported in file system job (VCCRUNH)
Parameter Detailed Descriptions (in alphabetical order)
Note: In the descriptions below, "standard" refers to the
VCC collector, and "HFS" refers to the USS file system
collector.
BYPASSBKUP (standard and HFS) - When specified as Y, VCC
will bypass the check of the backup flag in the
control file. This flag is set if a previous VCC
run failed to perform a successful backup. All
future VCC runs will fail until this flag is
cleared. To skip checking this flag, specify
BYPASSBKUP=Y.
Default: BYPASSBKUP=N
BYPASSRES (standard) - Specifies the volume serial numbers of
volumes for which a hardware RESERVE should not be
issued before processing the VTOC. Consider
specifying volumes that have a high level of
RESERVE activity or tend to conflict with VCC and
cause processing delays. Try to limit the size of
this list, because the contents of a VTOC can
change during processing if a RESERVE has not been
issued. Specify a list of volume serial numbers.
The list can contain generic specifications to
reduce the amount of keying involved. A maximum
of 2000 volume serial numbers may be specified in
this list.
Example: BYPASSRES=(SYSRES,PAG*,TSOWK*)
CATCHECK (standard) - When specified as Y, VCC issues a
LOCATE SVC for each VTOC data set that passes all
filter criteria. The catalog status of the data
set is recorded in a flag byte in the non-VSAM
segment of the VCC record.
WARNING: CATCHECK processing increases the amount
of time it takes VCC to complete the
processing of a given VTOC. Therefore,
coding CATCHECK=Y forces VCC to set
SERIALIZE=N.
The CATCHECK feature provides an easy way to
identify VTOC data sets that are not cataloged or
that are cataloged to a different volume in
preparation for SMS migration, specifically volume
conversion. Use CATCHECK=Y infrequently since the
LOCATE SVC function adds significant overhead.
For example, CPU time will more than double.
One suggestion is to establish two different
members of a VCCPARMS data set, and have a job
scheduling package or production control system
use a "standard" set of parameters for each VCC
run, except for the Sunday of each week. On
Sunday, CATCHECK=Y would lengthen the elapsed time
for VCC but provide a cycle in the database that
could be examined for uncataloged "problem" data
sets.
The CA MICS StorageMate Option contains a series
of standard reports that exploit the CATCHECK
feature by identifying problem data sets that will
inhibit SMS migration.
Default: CATCHECK=N
DATAINFO (standard) - Specifies whether VCC records data
set information or writes only volume information
to the VCCDATA file (or SMF). DATAINFO=N produces
the fastest possible scan with one record produced
for each volume scanned. Perhaps one scan per day
is run with DATAINFO=Y to collect information for
accounting applications and other scans are run
every hour with DATAINFO=N for storage
applications.
Default: DATAINFO=Y
DATALEVEL (HFS) - Specifies the level of information that VCC
will record. The operands for this keyword are the
following:
ALL - VCC will record all levels of
information.
HFSDIR - VCC will record file system and
directory level information for all
Hierarchical File Systems.
TEMP - VCC will record files stored on the
z/OS UNIX Temporary File System (TFS).
Default: DATALEVEL(ALL)
Example: DATALEVEL(TEMP,HFSDIR)
DIAGDUMP (HFS) - Facilitates problem solving by enabling VCC
to produce diagnostic information. To be
used at the direction of Technical Support.
For assistance, contact Technical Support at
http://ca.com/support.
EXCLUDECAT/INCLUDECAT (standard) - Specifies the names of the
catalogs that are not eligible or that are
eligible for processing by VCC. INCLUDECAT or
EXCLUDECAT is specified as a list of data set
names. Up to 200 data set names may be included
in the list. You can reduce the amount of keying
involved by listing generic specifications.
INCLUDECAT and EXCLUDECAT are mutually exclusive.
By default, VCC scans all catalogs it can find
connected to the master catalog.
Example: EXCLUDECAT=(SYS1.XCAT.*,SYS1.USERCAT1,
SYS1.USERCAT2)
EXCLUDEDEV/INCLUDEDEV (standard) - Specifies three-digit
device addresses that are not eligible or that are
eligible for processing by VCC. Specify
INCLUDEDEV or EXCLUDEDEV as a list of device
addresses. Up to 2000 device addresses may be
included in the list. You can reduce the amount
of keying involved by using generic
specifications. Only one of the following
parameters may be used for a VCC scan:
INCLUDEDEV, EXCLUDEDEV, INCLUDEDV4, or EXCLUDEDV4.
By default VCC scans all DASD volumes that are
online, resident, and ready. If you also code the
INCLUDEVOL/EXCLUDEVOL parameter, both the volume
serial number and device address tests must be met
or VCC will not select the volume.
Example: EXCLUDEDEV=(480,3B1,8FF,52*,54*,900)
EXCLUDEDSN/INCLUDEDSN (standard and HFS) - Specifies the data
sets that are not eligible or that are eligible
for processing by VCC. INCLUDEDSN or EXCLUDEDSN
is specified as a list of data set names. Up to
200 data set names may be specified in the list.
This list can contain generic specifications to
reduce the amount of keying involved. INCLUDEDSN
and EXCLUDEDSN are mutually exclusive. By
default, VCC records DASD space utilization data
for all data sets it encounters during the VTOC
and catalog scans.
Example: EXCLUDEDSN=(SYS1.*,SYS2.*,SYS3.*)
EXCLUDEDV4/INCLUDEDV4 (standard) - Specifies four-digit
device addresses that are not eligible or that are
eligible for processing by VCC. Specify
INCLUDEDV4 or EXCLUDEDV4 as a list of device
addresses. Up to 2000 device addresses may be
included in the list. You can reduce the amount
of keying involved by using generic
specifications. Only one of the following
parameters may be used for a VCC scan:
INCLUDEDV4, EXCLUDEDV4, INCLUDEDEV, or EXCLUDEDEV.
By default, VCC scans all DASD volumes that are
online, resident, and ready. If you also code the
INCLUDEVOL/EXCLUDEVOL parameter, both the volume
serial number and device address tests must be met
or VCC will not select the volume.
Example: EXCLUDEDV4=(04*,13B1,18FF,252*,254*,29*)
EXCLUDEPATH/INCLUDEPATH (HFS) - Specifies the HFS paths that
are not eligible or that are eligible for
processing by VCC. INCLUDEPATH or EXCLUDEPATH is
specified as a list of HFS paths. Up to 200 paths
may be included in the list. This list can contain
generic specifications to reduce the amount of
keying involved. INCLUDEPATH and EXCLUDEPATH are
mutually exclusive. By default, VCC scans all HFS
paths it can find. If you also code any other
INCLUDE or EXCLUDE parameter, all tests must be
met for the HFS path to be scanned.
EXCLUDEVOL/INCLUDEVOL (standard and HFS) - Specifies the
volume serial numbers that are not eligible or
that are eligible for processing by VCC.
INCLUDEVOL or EXCLUDEVOL is specified as a list of
volume serial numbers. Up to 2000 volume serial
numbers may be included in the list. This list
can contain generic specifications to reduce the
amount of keying involved. INCLUDEVOL and
EXCLUDEVOL are mutually exclusive. By default,
VCC scans all DASD volumes that are online,
resident, and ready. If you also code the
INCLUDEDEV/EXCLUDEDEV parameter, both the volume
serial number and device address tests must be met
or VCC will not select the volume.
Example: INCLUDEVOL=(IPLA01,TSO*,SCR001)
EXCLUDVVDS/INCLUDVVDS (standard) - Specifies the names of the
VSAM volume data sets that are not eligible or
that are eligible for processing by VCC.
INCLUDVVDS or EXCLUDVVDS is specified as a list of
data set names. Up to 200 data set names may be
included in the list. This list can contain
generic specifications to reduce the amount of
keying involved. Also, because all VVDS names
start with the characters 'SYS1.VVDS.V', you can
use a dollar sign ('$') in this parameter to
replace these characters. Thus, SYS1.VVDS.VSYSRES
and $SYSRES are logically identical. INCLUDVVDS
and EXCLUDVVDS are mutually exclusive. By
default, VCC will scan all VVDSs it can find.
This parameter is useful in limiting the scope of
a VCC scan for problem-solving purposes,
eliminating bad VVDSs from scanning until they are
fixed.
Example: EXCLUDVVDS=(SYS1.VVDS.VIPL*,$PAGE*)
EXTENDEDPDSE (standard) - Specifies how collection of the
extended PDS/E attribute data is to be handled.
This parameter functions at either the global or
local level. At the global level the parameter
controls whether or not the extended PDS/E
attribute data is collected for all DASD volumes
that are to be scanned. At the local level the
parameter can be used to specify specific volumes
or groups of volumes that will or will not have
the extended PDS/E attribute data collected.
EXTENDEDPDSE or NOEXTENDEDPDSE can be specified as
a list of volume serial numbers. Up to 2000
volume serial numbers may be included in the list.
This list can contain generic specifications to
reduce the amount of keying involved.
EXTENDEDPDSE and NOEXTENDEDPDSE are mutually
exclusive. By default, VCC collects extended
PDS/E attribute data for all DASD volumes that are
online, resident, and ready.
Examples:
1. EXTENDEDPDSE
Specifies collection of extended PDS/E
attribute data for all scanned DASD volumes.
2. NOEXTENDEDPDSE
Specifies that collection of extended PDS/E
attribute data will NOT be performed for any
scanned DASD volumes.
3. EXTENDEDPDSE(ABC001,XYZ*)
Specifies collection of extended PDS/E
attribute data for DASD volume 'ABC001' and
all DASD volumes where the volume serial
numbers begin with the characters 'XYZ'.
4. NOEXTENDEDPDSE(ABC001,XYZ*)
Specifies that collection of extended PDS/E
attribute data will NOT be performed for
DASD volume 'ABC001' or any DASD volumes
where the volume serial numbers begin with
the characters 'XYZ'.
FXTHRESHOLD (standard) - Specifies the thresholds to be used
in collecting the free-extent buckets count.
These counts are populated into the VOASPF01
through VOASPF08 data elements. This parameter
allows the user to specify the threshold, in
tracks, for the first seven free-extent buckets.
The eighth free-extent bucket threshold is always
set to high value in order to count any extent
sizes not contained within the first seven defined
buckets.
Example:
FXTHRESHOLD=(100,200,300,400,600,800,1000)
The values shown in the above example are the
default values used in case a threshold statement
is not supplied. The default values will yield
the following counts in the free extent buckets:
VOASPF01 - 1 to 100 track free extents
VOASPF02 - 101 to 200 track free extents
VOASPF03 - 201 to 300 track free extents
VOASPF04 - 301 to 400 track free extents
VOASPF05 - 401 to 600 track free extents
VOASPF06 - 601 to 800 track free extents
VOASPF07 - 801 to 1000 track free extents
VOASPF08 - 1001 and over track free extents
HFSERR (HFS) - Defines the maximum number of subtasks
that VCC uses to scan file systems that are
allowed to terminate with a "critical" error
without affecting the entire run (other subtasks).
Specify this parameter as a number between 0 and
16. The default is 0. The specified value should
never exceed the number of tasks specified in
HFSSUBT keyword minus 1.
Example: HFSERR=3
HFSSUBT=4
See Section 5.3, Abnormal Termination Processing,
for a discussion of considerations when choosing
this value.
HFSDIRBUFFER (HFS) - Defines the size of individual buffers
that are obtained to scan file systems. This
value is specified in units of 1024 bytes. (For
example, HFSDIRBUFFER=4 equals 4*1024 of 4096
bytes per buffer.) This parameter functions in
conjunction with the HFSDIRLEVEL parameter in that
there is one buffer obtained for every directory
level specified by the HFSDIRLEVEL parameter. A
larger size can yield better performance, but it
will also cause more virtual storage to be
obtained during scanning.
Default: HFSDIRBUFFER=16
HFSDIRLEVEL (HFS) - Defines the number of file system (HFS)
directory levels that can be scanned. Each HFS
path name is comprised of one or more nodes. (For
example, /aaaa/bbbb/cccc/ contains three nodes or
directory levels.) Complex path names typically
consist of numerous nodes requiring a higher value
for the parameter. This value must be set to a
value that is as large as or larger than the
maximum number of directory nodes that will be
processed.
Default: HFSDIRLEVEL=32
This parameter is no longer of any relevant
importance. The HFS scan logic has been improved
to dynamically adapt to increases in the number of
directory levels. This eliminates the problem of
potential reruns caused by exceeding the number
of directory levels specified by the HFSDIRLEVEL
parameter.
HFSSUBT (HFS) - Defines the number of subtasks that VCC
uses to scan Hierarchical File Systems that are
mounted and reside on z/OS. Specify this
parameter as a number between 0 and 16. The
specified value should never exceed the number of
devices being processed during a particular scan
execution.
Default: HFSSUBT=(number_of_processors * 3)
See the VTOCSUBT parameter below for a discussion
of considerations when choosing this value.
HSM (standard) - Specifies whether the VCC-HSM
interface should be attached to collect data about
data sets under the management of DFHSM.
This interface runs as a separate subtask creating
data records in the VCCHSM data set (or SMF) and
creates its own separate summary report on the
VCCHSMSG file.
This parameter value has the effect of
establishing defaults for other parameters related
to HSM processing. For example, HSMBACKUP=Y has
no effect unless HSM=Y is in effect. If HSM=Y is
in effect, HSMBACKUP=Y is the default.
Default: HSM=N
HSMBACKUP (standard) - Specifies whether the VCC-HSM
interface should collect data from the HSM Backup
Control Data Set (BCDS). There are potentially
many records that will be created. If your
application does not anticipate using this data,
you can save elapsed time and space on the VCCHSM
data set and in the database by disabling the
collection of data about backup versions.
The default is Y whenever HSM=Y is coded.
Default: HSMBACKUP=Y
HSMMIGRATE (standard) - Specifies whether the VCC-HSM
interface collects data from the HSM Migration
Control Data Set (MCDS). With this option, the
VCC-HSM interface can track data sets across the
entire hierarchy of storage managed by HSM.
The default is Y whenever HSM=Y is coded.
Default: HSMMIGRATE=Y
HSMSMF (standard) - Specifies whether the VCC-HSM
interface should write the output data records to
SMF or to the VCCHSM data set.
We recommend you write the HSM records to the
VCCHSM data set rather than log them directly to
SMF. This is because of the relatively high
volume of records this interface creates and
the associated probability of overflowing the SMF
buffer.
If you want to consolidate the data on SMF, you
could consider appending the VCCHSM data set to
the dumped SMF data set as an alternative to
direct SMF logging.
Default: HSMSMF=N
HSMSMFID (standard) - Specifies the SMF record number the
VCC-HSM interface uses in writing out data
records.
You should only change this number if you are
actually going to log data to SMF via the HSMSMF=Y
parameter above. If you change this from the
default value, you will need to coordinate a LOCAL
MODIFICATION to the sharedprefix.MICS.GENLIB
member named HSMGENIN.
If remote data centers have HSM data to be
collected and processed by CA MICS at a central
location, the HSMSMFID value chosen must be the
same by the time it is processed by a central CA
MICS. If you cannot synchronize this, a copy
utility could change the byte in the record to the
common value coded in the HSMGENIN member of
sharedprefix.MICS.GENLIB.
If you want to consolidate the data on SMF, you
could consider appending the VCCHSM data set to
the dumped SMF data set.
Default: HSMSMFID=197
LINECOUNT (standard and HFS) - Specifies the maximum number
of lines per page for the message log. While
writing messages to the message log, VCC will skip
to a new page and generate the heading lines each
time this value is reached. The value specified
for LINECOUNT is also used for VCC Statistics
Reports as well.
Default: LINECOUNT=62
NUMWTRBUF (standard and HFS) - Specifies the number of
buffers that VCC should obtain for the output
writer subtask. The various VCC subtasks use
these buffers to store output records while the
VCC writer subtask is busy writing information to
the VCCDATA output file or to SMF. Specifying too
small a value will cause delays while the subtask
waits for a buffer to become available.
Specifying too large a value will increase both
the region size and CPU usage of VCC. Consider
using a larger value if you are writing scan data
to a data set, rather than to SMF. Specify a
number between 10 and 100.
Default: NUMWTRBUF=25
OPERMSGS (standard and HFS) - Specifies whether or not VCC
should notify operations if unusual or
catastrophic situations occur during a VCC run.
VCC will issue Write-to-Operator messages (WTOs)
to the master console in these situations.
Default: WTO=Y
REMOVEMNT (standard and HFS) - Specifies whether or not DASD
devices that are neither permanently resident nor
reserved are to be scanned by VCC. Removable
volumes can be dismounted either at the end of the
job in which they were last used or when the unit
on which the volume is mounted is needed for
another volume.
Default: REMOVEMNT=N
RESERVEMNT (standard and HFS) - Specifies whether or not DASD
devices that are mounted with the PRIVATE,
RESERVED attributes are to be scanned by VCC.
Default: RESERVEMNT=N
RESFAILOK (standard) - Specifies the action that VCC should
take when it cannot RESERVE a volume that it is
attempting to process. You control the number of
times that VCC will attempt the RESERVE by the
RESRETRY parameter. Specify RESFAILOK=Y (Yes) if
you want VCC to continue processing the volume
without reserving it. Use this option with
caution, as VTOCs that are not reserved can have
their data changed while being processed by VCC.
Specify RESFAILOK=N (No) if you want VCC to bypass
the volume and not process it.
Default: RESFAILOK=Y
RESRETRY (standard) - Specifies the number of times that
VCC attempts to RESERVE a volume before taking the
action specified by the RESFAILOK parameter. A
retry consists of three RESERVEs, one second
apart. If VCC cannot reserve the volume in these
three attempts and the RESRETRY limit has not been
exceeded, VCC places the volume back on the queue
and tries later with another subtask. Thus,
specifying RESRETRY=4 causes up to 12 RESERVEs (3
times 4) to be issued for a volume before taking
the RESFAILOK action. Use this option with
caution, as VTOCs that are not reserved can have
their data changed while being processed by VCC.
Specify a number between 1 and 250.
Default: RESRETRY=10
SERIALIZE (standard) - Controls issuing of a cross-system
ENQ on the SYSVTOC resource for a given volume.
This type of ENQ results in a hardware RESERVE
being issued for the entire device until the
SYSVTOC resource is released (DEQueued). This
option preserves the integrity of reading a VTOC
to ensure that VCC can obtain the correct data set
information. Specifying a Y causes an ENQ/RESERVE
to be issued before the start of each VTOC scan.
Specifying an N bypasses the issuing of the
ENQ/RESERVE for ALL VTOCs during the current
execution. There is a small possibility that not
reserving the VTOC during the scan can cause data
integrity problems. Reserving the VTOC can cause
operational problems with other jobs and online
systems, ESPECIALLY when VCC is run during a prime
shift or a busy period.
Note: We recommend that you always use SERIALIZE=N
to avoid operational bottlenecks due to ENQ waits.
Never use SERIALIZE=Y during peak load. The only
time you should use SERIALIZE=Y is when absolute
data integrity is necessary (for example, when you
are utilizing Accounting and Chargeback data) and
only then when it is an off-peak time.
You should consider BYPASSRES lists for "system"
type volumes such as PAGE, SPOOL, and (DFHSM) ML1
volumes.
SMF (standard and HFS) - Specifies the recording
medium VCC uses to record DASD space utilization
data. Y (yes) tells VCC to record to SMF. N (no)
tells VCC to record to a data set.
Default: SMF=N
Note: If you code SMF=Y, make sure z/OS is
prepared to write the proper SMF record as coded
by SMFID (below). To verify this, check
SYS1.PARMLIB(SMFPRMxx) as discussed in the
appropriate IBM documentation.
SMFID (standard and HFS) - Specifies the SMF record
number that VCC places in each record it writes.
You can specify SMFID as a number between 128 and
255 inclusive. If the default conflicts with an
SMF record number being produced by another
product, change the record number VCC produces
with this parameter.
Note: CA MICS must also know about any changes to
this parameter.
If remote data centers have DASD data to be
collected and processed by CA MICS at a central
location, the SMFID value chosen must be the same
by the time it is processed by a central CA MICS.
If this cannot be synchronized, a copy utility
could change the byte in the record to the common
value coded in the VCAGENIN member of
sharedprefix.MICS.GENLIB.
Default: SMFID=198
SPACEUSEDEQALLOC/NOSPACEUSEDEQALLOC (standard) - This
parameter, when specified, causes the VTOC scan
tasks to set the value of the space-used field in
the collection record to the space-allocated value
for PDS/E and HFS data sets. The default for this
parameter is on and may only be turned off
(NOSPACEUSEDEQALLOC) when used in conjunction with
the specification of the DATAINFO=N parameter,
which produces only the volume total records for a
DASD volume. See also the PDSEUSED/NOPDSEUS
parameter in the CA MICS Space Analyzer Option
guide for additional information regarding the
interaction of the parameters.
Default: SPACEUSEDEQALLOC
SREPORT (standard) - Determines the sort order of the
VCCSTATS report. The default shows the volumes
processed in sequence by volume serial number.
Coding SREPORT=N overrides this to list volumes by
device address.
Default: SREPORT=Y
STATUS (HFS) - This parameter is issued via the z/OS
Modify Operator command (F jobname,STATUS) to
produce status information regarding VCC
processing. It is only available to the batch job
that is used to obtain z/OS UNIX HFS information.
TEMPDSN (standard) - Provides for the automatic
recognition and exclusion of system-generated
temporary data sets from the VCC inventory. The
space occupied by a temporary data set is still
counted toward the totals kept for the VCAVOA
file, but TEMPDSN=N prevents VCC from writing a
record to the VCCDATA file for the temporary data
set itself.
You should remove any EXCLUDEDSN=(SYS94*)
statements you may have in your VCCPARMS.
Default: TEMPDSN=N
TEST (standard and HFS) - Facilitates problem solving
by enabling VCC to produce diagnostic information.
The Y (yes) specification enables this facility,
which may result in voluminous output. Use the
INCLUDE/EXCLUDE run-time parameters described in
this section to limit the amount of output.
This parameter is intended to be used at the
direction of Technical Support. For assistance,
contact Technical Support at
http://ca.com/support.
Default: TEST=N
TRACE (standard and HFS) - Facilitates problem solving
by enabling VCC to produce diagnostic information.
Enabling this facility produces voluminous output.
Use the INCLUDE/EXCLUDE run-time parameters
described in this section to limit the amount of
output.
This parameter is intended to be used at the
direction of Technical Support. For assistance,
contact Technical Support at
http://ca.com/support.
Default: TRACE=N
UNCATPDSE (standard) - Specifies whether VCC is to collect
extended attribute information for uncataloged
PDS/E data sets. Normal VCC processing only
collects extended attribute information for
cataloged PDS/E data sets. Since PDS/E data sets
are not required to be cataloged, there could be a
considerable number of data sets for which
extended attribute information would not be
collected. This information includes the actual
space utilization within the PDS/E data sets.
One potential side effect of enabling this
parameter is the possibility that there may be
corrupted PDS/E data sets residing on DASD
volumes. Certain corrupted PDS/E data sets may
cause S0F4 abend conditions to appear while VCC is
processing. These abends occur in a system
service and cannot be intercepted by the VCC
modules. The system service recovers from the
abend and processing continues. The only loss is
the extended attribute data for the corrupted
PDS/E data set; otherwise, normal processing
continues. Information about the corrupted data
sets is written to the VTOC Scan Log and may be
used to analyze the data sets in question. A
possible solution is to delete the corrupted PDS/E
data set. If there are a large number of these
data sets, you may want to modify the VCC run JCL
and change the DD statement for the SYSUDUMP
output to the following:
//SYSUDUMP DD DUMMY
This will prevent the output queue from filling up
as a result of the dumps produced by the S0F4
abends. Once the corrupted data sets have been
identified and corrected or deleted, the normal
SYSUDUMP specification can be returned.
Default: UNCATPDSE=N
USEREXIT (standard) - Specifies whether VCC invokes a user
exit to perform user processing of Format 1 VTOC
DSCBs and the VCC output record. See Chapter 5
for more information. For the batch job used to
collect HFS information, this parameter allows
specification of the module name of the user exit
that performs additional processing to the VCC
output records.
Default: USEREXIT=N or USEREXIT=NONE.
USERIDZERO (HFS) - Specifies a 1 to 8 character name value
as a default user ID to be written to the output
records during HFS scan processing. This
parameter has no effect on the security access to
HFS file structures required for the scan.
Default: USERIDZERO=BPXROOT
VSAMERR (standard) - Defines the number of VSAM/ICF
catalog scan subtasks that can terminate with a
"critical" error without affecting the entire run
(other subtasks).
Specify this parameter as a number between 0 and
31. The default is 0. The specified value should
not exceed the number of tasks specified in
VSAMSUBT keyword minus 1.
Example: VSAMERR=3
VSAMSUBT=4
See Section 5.3, Abnormal Termination Processing,
for a discussion of considerations when choosing
this value.
VSAMSUBT (standard) - Defines the number of subtasks that
VCC uses to scan VSAM/ICF catalogs and VVDS data
sets. Specify this parameter as a number between
0 and 32. The value you specify should never
exceed the number of devices being processed
during a particular scan execution.
Default: VSAMSUBT=4
See the VTOCSUBT parameter for a discussion of
considerations when choosing this value.
VTOCERR (standard) - Defines the number of VCCVTOC
subtasks that can terminate with a "critical"
error without affecting the entire run (for
example, other subtasks).
Specify this parameter as a number between 0 and
31. The default is 0. The value you specify
should not exceed the number of tasks specified in
VTOCSUBT keyword minus 1.
Example: VTOCERR=2
VTOCSUBT=8
See Section 5.3, Abnormal Termination Processing,
for a discussion of considerations when choosing
this value.
VTOCSUBT (standard) - Defines the number of subtasks to be
used to scan VTOCs. Specify this parameter as a
number between 0 and 32. The specified value
should never exceed the number of devices being
processed during a particular scan execution.
Default: VTOCSUBT=8
VCC uses the values of the VTOCSUBT, VSAMSUBT, and
HFSSUBT parameters to govern how fast it scans the
DASD configuration. The main purpose is to make
the most efficient use of I/O wait time by
overlapping VCC I/O requests between subtasks.
(While one subtask is waiting for I/O to complete,
others can be processing their data.)
This subtask facility also provides a means by
which VCC I/O can be distributed across the I/O
configuration.
Use these parameters wisely, especially in the
case of the VTOC scan, because a large amount of
memory is obtained for I/O buffers and DSCB chain
resolution queues by each VTOC scan subtask.
WTO (standard) - (Write To Operator) Specifies whether
or not VCC should notify operations if unusual or
catastrophic situations occur during a VCC run.
VCC will issue WTOs to the master console in these
situations. See Chapter 7, Return Codes and
Messages, for message identifier VCCCN13I.
Default: WTO=Y
Copyright © 2014 CA.
All rights reserved.
|
|