7. RETURN CODES AND MESSAGES › 7.2 Messages Description › 7.2.9 VCCMAIN Messages
7.2.9 VCCMAIN Messages
VCC0001I variable_text
--------
This is an informational message issued to the System
Console. No response is necessary. VCC processing continues.
VCC0002I variable_text
--------
This is an informational message with no response necessary.
VCC processing continues.
VCC0003I variable_text
--------
This is an informational message with no response necessary.
VCC processing continues.
VCC0005I Console operators reply was: xxxxxx
--------
This is an informational message indicating the System
Console Operators response to an action message. VCC
processing continues.
VCC0006E Invalid reply - xxxxxx
--------
'xxxxx' in the above message indicates the incorrect response
the System Console Operator used in responding to an action
message. View the message log to find the action message
that was issued prior to this one. Make sure the response is
among the list of valid responses shown for the action
message. VCC processing continues.
VCC0007E Invalid parameter - xxxxxx
--------
'xxxxx' in the above message indicates the incorrect value
specified for a VCC parameter. Correct the value and resubmit
the VCC run.
VCC0008E Invalid keyword - xxxxxx
--------
'xxxxx' in the above message indicates the incorrect VCC
parameter specified. Correct the value and resubmit the VCC
run.
VCC0009E Unable to continue processing - reason_text
--------
This message signals that VCC encountered a problem during
processing and was unable to recover. 'reason_text'
identifies the cause of the problem. Processing is
terminated. Research the cause and rerun VCC. the following
are possible values for 'reason_text':
NOT ENOUGH STRG - VCC was unable to continue process because
insufficient virtual main storage was
allocated. Increase the size on the REGION
JCL parameter.
NOT AUTHORIZED - VCC is not running as an authorized program.
Make sure that the VCC modules are located
in an authorized library. If a JOBLIB or
STEPLIB DD is used, make sure that all other
concatenated libraries are also authorized.
The z/OS restriction that any unauthorized
library in an authorized JOBLIB/STEPLIB
concatenation forces all libraries to be
treated as unauthorized may have been in
effect in this case.
VOLTBL FULL - The DASD volume table allocated by VCC has
reached its limit. Restart VCC.
VCC0010I Processing completed, Return Code nn
--------
This message signals that VCC processing has completed. 'nn'
is the return code.
VCC0011E Required DD statement xxxxxxx not specified
--------
This message is issued when VCC detects that a required DD
JCL statement was not specified. 'xxxxxxx' indicates the
DDname. Add the correct JCL statement and resubmit the VCC
run.
VCC0012I CA MICS Space Collector Initialization in Progress
--------
This message signals that VCC initialization processing is in
progress.
VCC0013I CA MICS Space Collector Initialization Complete
--------
This message signals that VCC initialization processing has
ended successfully. VCC is now ready for full processing.
VCC0014I nnn,nnn,nnn records written to dsname on volume
-------- volser
This message indicates the number of records written to the
VCC output data set. 'dsname' is the output data set name;
'volser' is the volume serial location of the output data
set.
VCC0015I Recording data on volume volser, Dataset: dsn
--------
This message is issued when VCC has started writing records
to the output data set. 'volser' is the volume serial
location of the output data set; 'dsn' is the output data set
name.
VCC0016E I/O error on file ddn - desc
--------
This message indicates that an error occurred while VCC was
reading or writing to the data set referenced by DDname
'ddn'. 'desc' is the description of the actual error
encountered. Correct the problem and rerun VCC.
VCC0017I Read USS File Systems Subtask nn
-------- Started|Suspended|Ended
This message indicates when the various types of subtasks
within VCC start or complete processing. 'xxxxx' is the
subtask type, such as READVTOC, READCTLG, READHFS. 'nn' is
the sequence number of the subtask. The two digit subtask
identifier is located right after the timestamp for every
message issued by a subtask within the message log data set
(SYSPRINT).
Informational only.
VCC0018I Now scanning xxxxxxx yyyyyyy
--------
This message indicates when a VCC subtask has started to
process a file system, DASD Volume, or System Catalog.
'yyyyyy' is the entity name such as the volume serial or
data set name. 'xxxxxx' is the entity type identifying what
the entity is. This message is informational only.
VCC0019E modname was unable to obtain nnnnnK
--------
The indicated VCC module was unable to obtain enough virtual
storage for its processing. Increase the region size at least
by the amount shown and rerun VCC.
VCC0020I Set VolumeTableLength(nnnnK)
--------
This message indicates the amount of storage allocated in
units of 'k' (1,024 bytes) by VCC in building its internal
DASD Volume Table.
VCC0021I nn,nnn Mounted file systems found
--------
This message indicates the number of Hierarchical File
Systems mounted on z/OS that VCC found and will process.
VCC0022I nn,nnn online DASD volumes found
--------
This message indicates the number of Direct Access Storage
Devices online and available to VCC that will be processed.
VCC0023E I/O error on unit xxxx Volume: vvvvvv - EC: zzzz
--------
VCC issues this message when it has been unable to
communicate successfully with the DASD Storage Subsystem or
Control unit that volume 'vvvvvv' is attached to. 'xxxx'
indicates the device address. 'zzzz' is diagnostic
information returned in the Channel Status Word (CSW) to aid
CA MICS Product Support personnel in determining the cause of
the problem.
Processing continues for the next volume. Some information
regarding the device that contained the error may not be
available in the VCCDATA record.
VCC0024I Diagnostic trace requested for unit xxxx vol:vvvvv
--------
VCC issues this message when an error has been detected while
trying to access information from the Control Unit for the
indicated volume (vvvvvv), and the TRACE=Y parameter was
specified. 'xxxx' indicates the device address. The
information provided assists CA MICS Product Support
personnel in determining the cause of the problem. Also, see
VCC0023E.
VCC0025W Device information unavailable for volume vvvvv on
-------- unit zzzz
VCC issues this message when a DASD device is not in the
ready state or VCC could not communicate successfully with
the DASD Storage Subsystem or Control unit that volume
'vvvvvv' is attached to. 'zzzz' indicates the device
address. Determine why the device was unavailable during the
VCC run. The indicated volume will not be processed by VCC.
Processing continues for the next volume. Return code 4 is
set.
VCC0026W nnnn Warning|Error message(s) were issued. Please
-------- check job output.
This message is issued to the System Console during
termination processing indicating that warning and/or error
messages were issued during VCC processing. This message
helps to alert the personnel responsible for checking for a
successful VCC run.
VCC0027W Insufficient authorization to scan file systems.
--------
This message is issued when VCC does not have the required
access level to scan a file system. Ensure that VCC has
authority to use the resource type IBMFAC with the resource
BPX.DAEMON.
VCC0028E Run required backup for output file: ddname
-------- Dataset: dsn
This message is issued when VCC detected that the previous
output data set was not copied successfully. Refer to the
BYPASSBKUP runtime parameter described earlier within this
document.
VCC0030W No ddname DD statement specified, Default values
-------- in effect.
VCC could not open the VCCPARMS DD statement. VCC will use
its default values. VCC processing continues.
VCC0031I Input parameter file ddname dsn on volume volser
--------
This informational message identifies where VCC obtained its
runtime parameters. Processing continues.
VCC0032E Missing equals sign
--------
A parameter keyword has been identified but is not
immediately preceded by an equals sign (with no intervening
blanks). Parameter keyword parsing continues. Return code 8
is set.
VCC0033E Keyword value must be "Y" or "N"
--------
A parameter keyword is encountered whose only valid values
are Y (yes) and N (no), and one of these values was not
entered. Parameter keyword parsing continues. Return code 8
is set.
VCC0034E Keyword value must be numeric
--------
A parameter keyword requiring numeric values contains a value
that is not numeric. Parameter keyword parsing continues.
Return code 8 is set.
VCC0036E Keyword value too large
--------
A parameter keyword requiring numeric values was encountered,
but the numeric value entered is too large for VCC to handle.
Parameter keyword parsing continues. Return code 8 is set.
VCC0037E Keyword value out of allowable range
--------
A parameter keyword is encountered whose only valid options
are numeric values and the numeric value entered is outside
of the range of values allowed for this keyword. Parameter
keyword parsing continues. Return code 8 is set.
VCC0038E Invalid keyword value
--------
A parameter keyword is encountered that has a list of valid
numeric or character values associated with it, but the value
entered is not in this list. Parameter keyword parsing
continues. Return code 8 is set.
VCC0039E Keyword specification too long
--------
A parameter keyword value was encountered that has a maximum
length that was exceeded. Parameter keyword parsing
continues. Return code 8 is set.
VCC0040E Invalid data set name
--------
A parameter keyword is encountered whose value must be data
set names and one of the values specified is not a valid data
set name. Parameter keyword parsing continues. Return code
8 is set.
VCC0041E Missing left|right parenthesis
--------
A parameter keyword is encountered whose values must be
enclosed in parentheses and the left or right parenthesis is
missing. Parameter keyword parsing continues. Return code 8
is set.
VCC0043E Keyword terminator must be blank
--------
A parameter keyword is encountered that can have only one
option and the option specified does not end in a blank
character. Parameter keyword parsing continues. Return code
8 is set.
VCC0044E Missing keyword value
--------
A parameter keyword is encountered that has no value
specified after the equals sign and no intervening blanks.
Parameter keyword parsing continues. Return code 8 is set.
VCC0045E Invalid list separator character
--------
A parameter keyword is encountered whose value must be a data
set name or other alphanumeric value, yet does not end with a
comma, period, or right parenthesis. Parameter keyword
parsing continues. Return code 8 is set.
VCC0046E Missing terminator
--------
A parameter keyword is encountered whose value does not
terminate on the same card. For keywords with a list of
options, one of the items in the list does not terminate on
the same card on which the options began. Parameter keyword
parsing continues. Return code 8 is set.
VCC0047E Keyword mutually exclusive with another
--------
A parameter keyword is encountered whose mutually exclusive
counterpart has been encountered previously. This applies to
all INCLUDE/EXCLUDE parameter keywords. Parameter keyword
parsing continues. Return code 8 is set.
VCC0048E Generic specification not allowed for this keyword
--------
A parameter keyword is encountered whose operand contains an
asterisk. Parameter keyword parsing continues. Return code
8 is set.
VCC0049E Maximum entries for keyword exceeded nnn
--------
A parameter keyword is encountered whose options are a list
of values, and the number of entries specified in this list
exceeds the maximum allowed for the keyword. The string nnn
in the message text is replaced by the maximum number of
entries defined for the parameter keyword currently being
parsed. Parameter keyword parsing continues. Return code 8
is set.
VCC0050W Keyword is obsolete and should be removed
--------
A parameter keyword is encountered that has been obsoleted
and VCC no longer uses. The parameter keyword and its value
are ignored. Parameter keyword parsing continues. Return
code 4 is set.
VCC0051W Incorrect keyword value; xxxxx=yyyyy in effect
--------
The parameter value is insufficient or conflicts with the
value of a previously specified keyword. VCC will force the
value shown by 'xxxxx=yyyyyy'. Processing continues and
return code 4 is set.
VCC0052E Keyword value conflict - xxxxxx
--------
VCC detected a conflict with the indicated parameter 'xxxxx'
and another parameter specification. VCC is terminated.
Resolve the conflict and rerun VCC.
VCC0053E Expected continuation not received
--------
VCC was expecting an operand of a runtime parameter to
continue onto the next statement but did not find it.
Respecify or add the missing operand and rerun VCC.
VCC0054W Entry ignored - duplicate specification
--------
VCC detected a runtime parameter that was already specified
previously. The parameter shown prior to this message is
ignored. Remove the duplicate parameter if desired.
VCC0059W Unable to write output record type nnn - RSN=zz
--------
VCC was unable to write the output record to the data set
referenced by the VCCDATA DD statement or to the SMF z/OS
subsystem. 'zz' indicates the reason code for determining the
cause. The following is a list of causes and their associated
reason codes:
Reason code Description
----------- ---------------------------------------------
1 VCC SMF RECORD RDW IS LESS THAN 18 BYTES. If a
user exit is being used, make sure that the
exit is not creating records less than 18 bytes
in length. Otherwise, this is a problem that
should be reported to CA MICS Product Support.
2 VCC SMF RECORD RDW IS GREATER THAN 4096 BYTES.
If a user exit is being used, make sure that
the exit is not creating records greater than
4K in length. Otherwise, this is a problem that
should be reported to CA MICS Product Support.
6 SMF IS NOT ACTIVE. Report this message to your
systems programmer.
7 SMF EXIT IS REJECTING VCC SMF RECORDS
SMF Exit IEFU83 is rejecting SMF records with
the record type 'nnn'. See your systems
programmer to ascertain if you are using the
proper SMF record type.
8 VCC SMF DATA RECORD HAS BEEN LOST
All z/OS SMF data logging data sets are full so
no more SMF records can be written. Report
this problem to your systems programmer.
9 SMF BUFFER SHORTAGE
SMF does not have enough buffers to handle the
record output rate currently being experienced
by the system. Inform your systems programmer.
10 SMFWTM SEVERE ERROR
Report this problem to your systems programmer.
VCC will try to continue processing. If unsuccessful, or the
problem occurs again, VCC will terminate.
VCC0060W SMF recording is suppressed for record type nnn
--------
VCC detected that SMF record type 'nnn' is not being recorded
by the SMF subsystem. VCC will terminate processing. Report
this problem to your systems programmer.
VCC0061W xxxxxxxx Request failed RC=yy, RSN=zzzz pppp
--------
VCC was unsuccessful in performing the request indicated by
'xxxxxx'. The return ('yy') and reason codes ('zzzz') in the
message text are provided to assist in determining the cause
of the problem. VCC processing will continue. Function
names that begin with 'USS' are z/OS UNIX System Services
requests. The POSIX path name causing the error ('pppp') may
be shown in the message text. You make look up the return
and reason codes in the z/OS UNIX System Services Messages
and Codes documentation to determine the cause of the
failure. Try to correct the problem. Otherwise report this
message to CA MICS Product Support.
VCC0062E xxxxxxxx Request failed RC=yy, RSN=zzzz pppp
--------
VCC was unsuccessful in performing the required request
indicated by 'xxxxxx' 'xx' and 'yy' (return and reason codes
to assist in determining the cause of the problem). VCC
processing will terminate. Report this message to CA MICS
Product Support.
VCC0063E Abend xxxxx detected by mod in yyyyy
--------
VCC's ESTAE routine received control due to an abnormal
condition. 'xxxxx' indicates the abend code. 'mod' is the
VCC module that detected the error. 'yyyy' is the CSECT or
subroutine name. VCC will issue an SVCDUMP to the system
dump data sets and terminate. Save the dump and report this
message to CA MICS Product Support.
VCC0064I Diagnostic dump request of xxxxxx started|ended
--------
VCC issues this informational message indicating the status
of the request to dump VCC's virtual storage. Informational.
VCC0065I Collection shutdown requested
--------
When this message is issued VCC has obtained a request from
the System Console Operator to terminate processing.
This message is informational only.
VCC0066W xxxxxx request failed yyyyyyy
--------
VCC was unsuccessful in performing the request indicated by
'xxxxxx', but was able to continue processing. 'yyyy'
indicates the action taken by VCC so that it could continue
processing. You may review the cause of the problem and
correct it for a future execution of VCC.
VCC0070I Control Data Set dsn is on volume vvvvvv
--------
VCC issues this informational message when its control data
set is opened. VCC Processing continues.
VCC0071A Control Data Set in use by xxxxx on system yyyyy
-------- Reply: 'W'-Wait or 'C'-Cancel
VCC issues this message to the System Console when it detects
that the control data set is in use for an unusually long
period of time by another job. 'xxxxx' is the jobname, and
'yyyyy' is the name of the system that 'xxxxx' is executing
on. The Console Operator should determine if the indicated
job is running successfully. If this is the case, reply 'W'
to wait for the job. Otherwise reply 'C' to cancel this VCC
run. Rerun VCC at a later time.
VCC0072A Control Data Set in use by xxxxx on system yyyyy
-------- Reply: 'U'-Reset/Use, 'W'-Wait, or 'C'-Cancel
VCC issues this message to the System Console when it detects
that the control data set is in use for an unusually long
period of time by another job. 'xxxxx' is the jobname, and
'yyyyy' is the name of the system that 'xxxxx' is executing
on. The Console Operator should determine if the indicated
job is running successfully. If this is the case, reply 'W'
to wait for the job. If job 'xxxxx' is not currently
executing, reply 'U' to reset the control file. Most likely
the previous VCC run using the control file ended abnormally
leaving the control file in a locked condition. If the reply
is 'C' VCC will be terminated.
VCC0073E Insufficient space for Control Data Set
--------
VCC issues this message when it detects that the control data
set allocated does not contain sufficient space needed by
VCC. VCC will terminate. Reallocate the control data set
with more space and rerun VCC.
VCC0074E Control Data Set is corrupted
--------
VCC detected that the control data set has been overwritten
with other unknown information. A dump will be written to the
data set referenced by the VCCSNAP DD statement. Save the
dump and Report this message to CA MICS Product Support. VCC
processing terminates.
VCC0075E Control Data Set integrity exposure
--------
VCC detected that the control data set has lost its data
integrity due to another VCC job running on another system.
This problem may occur when DASD RESERVES have been converted
to ENQUEUES by a system product. VCC processing terminates.
A dump will be written to the data set referenced by the
VCCSNAP DD statement. Save the dump and report this message
to CA MICS Product Support.
VCC0077A Control Data Set in use by xxxxx
-------- Reply: 'U'-Reset/Use, 'W'-Wait, or 'C'-Cancel
VCC issues this message to the System Console when it detects
that the control data set is in use for an unusually long
period of time by another VCC Job named 'xxxxxx'. The
Console Operator should determine if the indicated job is
running successfully. If this is the case, reply 'W' to wait
for the job. If job 'xxxxx' is not currently executing reply
'U' to reset the control file. Most likely the previous VCC
run using the control file ended abnormally leaving the
control file in a locked condition. If the reply is 'C' VCC
will be terminated.
VCC0078I Control Data Set initialized|converted
--------
VCC issues this informational message when the control data
set has been either converted from its old format or is a new
data set that has been initialized successfully. VCC
processing continues.
VCC0080I xxxxxx entry yyyyy expired, removed from control
-------- file
While writing necessary information regarding the devices
and/or file systems scanned, VCC found an entry that has
expired and has removed the entry from the control file.
'xxxxxx' indicates the entry type such as volume, file
system, or system catalog. 'yyyyy' indicates the entry name.
This message is informational. VCC processing continues.
VCC0081I Control Data Set extended by nnnk
--------
During processing VCC has detected that the control data set
is too small to store necessary information regarding the
devices and/or file systems scanned. This message indicates
that VCC has successfully extended the size of the control
data set by the number of bytes shown. VCC processing will
continue.
VCC0084I nnnn xxxxx were already processed
--------
This message is issued when VCC has detected that some
entities were already processed previously by VCC. Hence the
entities, either volumes, file systems or system catalogs,
will not be processed during this collection run. 'nnnn'
indicates the number of entities that will not be processed.
'xxxxx' indicates the entity type.
This message is informational. VCC processing continues.
VCC0085I variable_text
--------
This is an informational message issued to the System
Console in response to an operator command. No response
is necessary. VCC processing continues.
VCC0089I Set ReadDirectoryLevels(nnn)
--------
This is an informational message issued to report the number
of file system directory read levels that are being used for
the USS FIle System scan execution. This value is either
specified or defaulted by the HFSDIRLEVEL parameter. No
response is necessary. VCC processing continues.
VCC0090I Set DirectoryBufferSize(nnK)
--------
This is an informational message issued to report the size of
the file sYstem Directory Read Buffers that are being used
for the USS File System scan execution. This value is either
specified or defaulted by the HFSDIRBUFFER parameter. No
response is necessary. VCC processing continues.
VCC0091I Group|User ID Build Processed nnnn Definitions
--------
This is an informational message issued to report on the
number of Group or User ID definitions that were read from
the USS Group or User database. No response is necessary.
VCC processing continues.
VCC0092I Group|User ID Build Created nnnn Table Entries
--------
This is an informational message issued to report on the
number of Group or User ID entries that were created in the
storage table used during scan processing. This number will
almost always be less than the corresponding number reported
in the VCC0091I message due to the elimination of duplicates.
No response is necessary. VCC processing continues.
VCC0093I Group|User ID Build Released nnnK of Unused Storage
--------
This is an informational message issued that indicates how
much unused virtual storage was released after completion of
the Group or User ID table build process. No response is
necessary. VCC processing continues.
VCC0094E Group|User ID Build Maximum Table Entries Exceeded
--------
This is an error message issued to indicate that either the
Group ID or the User ID table has overflowed. It is unlikely
that this condition will be raised. This is due to the design
which allocates extremely large virtual storage areas for the
tables then releases the unused portions. The default size
for each of the tables is adequate to contain 32,767 entries.
No response is necessary. VCC processing continues.
VCC0100I File Systems Processed.........nnnn
--------
This is an informational message issued to report on the
number of files systems that the identified subtask
processed. No response is necessary. VCC processing
continues.
