Appendix A: MESSAGES › A.1 VCA Component Messages
A.1 VCA Component Messages
This appendix lists all messages generated by the VCA
component of the CA MICS Space Analyzer. Some messages are
generated during the processing of the control statements,
while others are caused by various conditions in the data
found during the processing. The messages are listed in
ascending numerical sequence and include the full text of the
message, the type, the reason for the message, appropriate
user action, and applicable references to documentation.
The following type codes are used to categorize the messages:
Information Designates a note that documents a CA MICS
option or potentially important feature in
the data.
Warning Designates a condition in either the date or
the control statements that does not affect
the CA MICS Space Analyzer's operation, but
that may lead to unexpected results.
Error Designates that a problem has been
encountered with a control statement that
will prevent a successful run of the
product. Execution is stopped after all
control statements are processed.
The message text often includes references to information
that is contained in a control statement or values of
permanent or temporary variables created during CA MICS
processing. In the description below, the message text
contains a word beginning with a percent sign (%), which
indicates that a value will be substituted into the text at
execution time. For example, message VCA00016 reads as
follows:
TEXT: >>>>> SYSID NOT 1 TO 4 CHARACTERS IN LENGTH.
SYSID=%TOKEN2.
A possible version of the printed message in the MICSLOG
might be:
TEXT: >>>>> SYSID NOT 1 TO 4 CHARACTERS IN LENGTH.
SYSID=SYS008 .
+-----------------+
| V C A 0 0 0 0 1 |
+-----------------+
TEXT: VCA PARAMETER GENERATION STARTED.
TYPE: Information
REASON: The beginning of the VCAPGEN job is noted.
ACTION: None
REFERENCES: Section 7.3.1
+-----------------+
| V C A 0 0 0 0 2 |
+-----------------+
TEXT: VCA PARAMETER GENERATION COMPLETED SUCCESSFULLY.
TYPE: Information
REASON: The end of the VCAPGEN job is noted.
ACTION: None
REFERENCES: Section 7.3.1
+-----------------+
| V C A 0 0 0 1 0 |
+-----------------+
TEXT: ---- VCAOPS MEMBER:
TYPE: Information
REASON: The content of the prefix.MICS.PARMS member
called VCAOPS follows this message line.
ACTION: None
REFERENCES: Section 7.3.1
+-----------------+
| V C A 0 0 0 1 1 |
+-----------------+
TEXT: %LINE
TYPE: Information
REASON: This is a general purpose message used by both
VCAPGEN processing and by the DAILY job (step
DAY090). The value of the variable LINE is
displayed on the MICSLOG output data set for
informational purposes.
ACTION: None
REFERENCES: Section 7.3.1
+-----------------+
| V C A 0 0 0 1 5 |
+-----------------+
TEXT: >>>>> KEYWORD NOT RECOGNIZED KEYWORD=%TOKEN1.
TYPE: Error
REASON: The displayed keyword is not defined for VCAPGEN.
ACTION: Correct the keyword and resubmit the job.
REFERENCES: Section 7.3.1
+-----------------+
| V C A 0 0 0 1 6 |
+-----------------+
TEXT: >>>>> SYSID NOT 1 TO 4 CHARACTERS IN LENGTH.
SYSID=%TOKEN2.
TYPE: Error
REASON: SYSID cannot exceed 4 characters.
ACTION: Correct the OPTIONS statement value for SYSID or
consider using '*' to represent all SYSID values.
REFERENCES: Section 7.3.1
+-----------------+
| V C A 0 0 0 1 7 |
+-----------------+
TEXT: >>>>> INTERVAL TIME VALUE MUST BE 1-999 HOURS.
VALUE=%TOKEN3.
TYPE: Error
REASON: The default duration value is not within the
proper range. This value should be based on how
frequently the CA MICS Space Collector job (VCC
scan) is run, creating input for this database
unit. For example, if the VCC scan is run once
per day, this value should be set to 24 to
represent 24 hours.
On the other hand, if VCC scan is run hourly,
then this parameter should be set to 1.
ACTION: Correct the OPTIONS statement value for the
default duration and resubmit.
REFERENCES: Section 7.3.1
+-----------------+
| V C A 0 0 0 2 0 |
+-----------------+
TEXT: ---- END OF VCAOPS MEMBER.
TYPE: Information
REASON: The content of the prefix.MICS.PARMS member has
been displayed above this message line.
ACTION: None
REFERENCES: Section 7.3.1
+-----------------+
| V C A 0 0 0 2 4 |
+-----------------+
TEXT: OPTIONS STATEMENT MISSING. ASSUMING DURATION OF 24
HOURS AND ACCEPTANCE OF INPUT FROM ANY SYSID.
TYPE: Information
REASON: Options statement in VCAOPS is missing. A
default DURATION of 24 hours is being used and
data from all SYSIDS will be processed.
ACTION: None
REFERENCES: Section 7.3.1
+-----------------+
| V C A 0 0 0 2 5 |
+-----------------+
TEXT: BCSREQUIRED STATEMENT MISSING. ASSUMING NO
REQUIREMENT FOR BCS (ONLY VVDS) FOR VSAM.
TYPE: Information
REASON: BCSREQUIRED statement in VCAOPS is missing.
Default being used is BCSREQUIRED NO.
ACTION: None
REFERENCES: Section 7.3.1
+-----------------+
| V C A 0 0 0 2 6 |
+-----------------+
TEXT: EXTENTDETAIL STATEMENT MISSING. ASSUMING NO
RETENTION FOR DETAIL EXTENT DATA BEYOND 16
EXTENTS.
TYPE: Information
REASON: EXTENTDETAIL statement in VCAOPS is missing.
Default being used is EXTENTDETAIL NO.
ACTION: None
REFERENCES: Section 7.3.1
+-----------------+
| V C A 0 0 0 2 7 |
+-----------------+
TEXT: ACCOUNTING STATEMENT MISSING. ASSUMING
COMPUTATION OF DASD COST AT -DAYS- TIMESPAN.
TYPE: Information
REASON: ACCOUNTING statement in VCAOPS is missing.
Default being used is ACCOUNTING DAYS.
ACTION: None
REFERENCES: Section 7.3.1
+-----------------+
| V C A 0 0 0 2 8 |
+-----------------+
TEXT: INVALID PARAMETER FOR %TOKEN1 KEYWORD. SPECIFY
%CHOICE1 OR %CHOICE2.
TYPE: Error
REASON: The syntax for this statement requires the
choice between two parameter alternatives.
ACTION: Correct the VCAOPS member and resubmit the job.
REFERENCES: Section 7.3.1
+-----------------+
| V C A 0 0 0 3 0 |
+-----------------+
TEXT: >>>>> ERROR(S) ENCOUNTERED IN VCAOPS PARM
DEFINITIONS.
>>>>> $VCAMSTR GENERATION ABORTED.
>>>>> CORRECT ERROR(S) AND EXECUTE AGAIN.
TYPE: Error
REASON: VCAPGEN processing has encountered a syntax
error.
ACTION: Correct the errors as indicated by prior messages
and resubmit VCAPGEN.
REFERENCES: Section 7.3.1
+-----------------+
| V C A 0 0 0 7 5 |
+-----------------+
TEXT: VCACGEN option default taken
Option: PDSEUSED/NOPDSEUS Default: NOPDSEUS
TYPE: Information
REASON: The OPTION statement in
sharedprefix.MICS.GENLIB(VCAGENIN) did not
specify a value, so the default value was used.
ACTION: None
REFERENCES: None
+-----------------+
| V C A 0 0 1 0 0 |
+-----------------+
TEXT: --------------- BEGIN PHASE 1 ---------------
TYPE: Information
REASON: This message is displayed during the building of
the first observation in the first DATA step of
the DAY090 job step.
ACTION: None
REFERENCES: None
+-----------------+
| V C A 0 0 1 0 1 |
+-----------------+
TEXT: AT LEAST ONE RECORD WITH SYSID NOT DEFINED IN
VCAOPS (%ORGSYSID). THE DEFAULT DURATION WILL BE
USED.
TYPE: Warning
REASON: A SYSID that is not defined in VCAOPS has been
encountered in the input data being processed.
Default DURATION will be assigned to this SYSID.
ACTION: If you want to specify a DURATION for this SYSID,
update VCAOPS and run VCAPGEN.
REFERENCES: Section 7.3.1
+-----------------+
| V C A 0 0 1 0 2 |
+-----------------+
TEXT: AT LEAST ONE RECORD READ WITH BAD VCC RECORD ID.
(%WRKID). SUCH RECORDS ARE DELETED.
TYPE: Warning
REASON: A record was found with a record ID that is
invalid. The record ID must be 'VCC'. The
records are deleted and the option deleted counter
is incremented.
ACTION: Check to see if invalid data is being input to
the DAY090 step.
REFERENCES: None
+-----------------+
| V C A 0 0 1 0 3 |
+-----------------+
TEXT: VCC VERSIONS PRIOR TO 101 ARE NO LONGER SUPPORTED
TYPE: Error
REASON: The input data being processed is from a version
of the Space Collector that is not supported.
ACTION: Apply required VCC maintenance from the PSP tape.
For assistance, contact Technical Support at
http://ca.com/support.
REFERENCES: None
+-----------------+
| V C A 0 0 1 0 4 |
+-----------------+
TEXT: FIRST INPUT TIMESTAMP THIS RUN=%ENDTS FROM
SYSTEM %ORGSYSID.
TYPE: Information
REASON: This message is issued for the first record read
by VCA. It gives the ENDTS and the SYSID.
ACTION: None
REFERENCES: None
+-----------------+
| V C A 0 0 1 1 0 |
+-----------------+
TEXT: >>>>> VOL=%VOLSER DSN=%DSNAME NUMBER OF DATA SET
EXTENTS IS INVALID. EXTNO=%DAAEXTNO
TYPE: Error
REASON: The extent information for the data set being
processed is invalid.
ACTION: Use ISPF to verify that the DSNAME is valid.
Consider using a function to consolidate the data
set into one extent.
REFERENCES: None
+-----------------+
| V C A 0 0 1 1 1 |
+-----------------+
TEXT: >>>>> SYSID=%SYSID VOL=%VOLSER DSN=%DSNAME
----- DS1LSTAR VALUE FROM VTOC IS INVALID.
TYPE: Warning
REASON: The DS1LSTAR value read from the VTOC is invalid.
Using the value would result in invalid space used
value. Space used is set equal to space
allocated.
ACTION: None
REFERENCES: None
+-----------------+
| V C A 0 0 1 1 2 |
+-----------------+
TEXT: >>>>> SYSID=%SYSID VOL=%VOLSER DSN=%DSNAME
----- SPACE USED IS GREATER THAN SPACE ALLOCATED.
TYPE: Warning
REASON: The DS1LSTAR value read from the VTOC is invalid.
Because space used is greater than space
allocated, space used is set to be equal to space
allocated.
ACTION: Data sets with an invalid DS1LSTAR should be
investigated and repaired if possible with the
appropriate utility function (COPY, COMPRESS,
EDIT(SAVE), etc).
REFERENCES: Section 4.3, Exception Report EXC09019.
+-----------------+
| V C A 0 0 1 1 3 |
+-----------------+
TEXT: >>>>> SYSID=%SYSID VOL=%VOLSER DSN=%DSNAME
----- KEY RANGE QUALIFIER BEYOND END OF RECORD -
SET TO BLANKS.
TYPE: Warning
REASON: The input record from VCC has an internal pointer
problem so that the key range qualifier cannot be
read from that record.
ACTION: This problem likely originates with the VSAM file
and its catalog data. Examine it and possibly
correct problems by deleting and redefining the
data set.
REFERENCES: None
+-----------------+
| V C A 0 0 1 1 4 |
+-----------------+
TEXT: >>>>> SYSID=%SYSID VOL=%VOLSER DSN=%DSNAME
----- EXTENT INFO BEYOND END OF RECORD - INFO LOST.
TYPE: Warning
REASON: The input record from VCC has an internal pointer
problem so that VSAM extent information cannot be
read from that record.
ACTION: This problem likely originates with the VSAM file
and its catalog data. Examine it and possibly
correct problems by deleting and redefining the
data set.
REFERENCES: None
+-----------------+
| V C A 0 0 1 1 5 |
+-----------------+
TEXT: >>>>> SYSID=%SYSID VOL=%VOLSER DSN=%DSNAME
----- INVALID LOW/HIGH KEY LENGTH FOUND, SETTING TO
BLANKS.
TYPE: Warning
REASON: The input record from VCC has an internal pointer
problem so that either the VSAM low key or high
key cannot be read from that record.
ACTION: This problem likely originates with the VSAM file
and its catalog data. Examine it and possibly
correct problems by deleting and redefining the
data set.
REFERENCES: None
+-----------------+
| V C A 0 0 2 0 0 |
+-----------------+
TEXT: --------------- BEGIN PHASE 2 ---------------
TYPE: Information
REASON: This message is displayed during the start of
phase 2 of the DAY090 job step.
ACTION: None
REFERENCES: None
+-----------------+
| V C A 0 0 3 0 0 |
+-----------------+
TEXT: --------------- BEGIN PHASE 3 ---------------
TYPE: Information
REASON: This message is displayed during the start of
phase 3 of the DAY090 job step.
ACTION: None
REFERENCES: None
+-----------------+
| V C A 0 0 3 0 1 |
+-----------------+
TEXT: CATALOG RESTART REPORT
THE FOLLOWING VOLUMES WERE NOT SUCCESSFULLY
PROCESSED BY VCC. ALL CATALOGED DATA SETS
COLLECTED FROM THESE VOLUMES WILL BE EXCLUDED FROM
THE VCA_VS FILE.
TYPE CLUSTER NAME DATA SET NAME
---- -------------- -------------
TYPE: Warning
REASON: This report will be printed as part of the MICSLOG
if the Space Collector fails to completely
process a volume. It documents that the VCC
records collected from your catalogs describing
the VSAM data sets on these volumes have been
received and ignored by the Space Analyzer.
This is an informational report and shows that the
normal error detection and restart process is
working correctly.
ACTION: The Space Collector's output should be examined to
determine the problem.
REFERENCES: None
+-----------------+
| V C A 0 0 3 0 2 |
+-----------------+
TEXT: >>>>> VOLUME=%VOLSER - SYSID=%SYSID %ENDTS -
VOL. NOT SUCCESSFULLY PROCESSED
TYPE: Warning
REASON: This message is issued for every volume that is
not successfully processed by the Space collector.
The data set information collected from the
indicated volume will not be written to the VCA_VS
file.
ACTION: The Space Collector's output should be examined to
determine the problem.
REFERENCES: None
+-----------------+
| V C A 0 0 3 0 8 |
+-----------------+
TEXT: >>>>> %NNNNN DATA SETS IGNORED FROM %WRKMSG2
VOLUMES.
TYPE: Warning
REASON: This message gives the total number of data sets
whose information is not written to the VCA_VS
file.
ACTION: See the VCA00302 message that precedes this
message for the action that must be taken.
REFERENCES: None
+-----------------+
| V C A 0 0 4 0 0 |
+-----------------+
TEXT: --------------- BEGIN PHASE 4 ---------------
TYPE: Information
REASON: This message is displayed during the start of
phase 4 of the DAY090 job step.
ACTION: None
REFERENCES: None
+-----------------+
| V C A 0 0 4 0 1 |
+-----------------+
TEXT: ATTRIBUTES AND STATISTICS EXCEPTION REPORT
THE PRIMARY VOLUME FOR THE FOLLOWING VSAM DATA SETS
WAS NOT PROCESSED BY VCC. SINCE THE ATTRIBUTES AND
STATISTICS ELEMENTS ARE ONLY PRESENT IN THE PRIMARY
VOLUME VVDS, MANY ELEMENTS WILL BE ZERO IN THE
VCA_VS FILE.
TYPE VOLUME CLUSTER NAME DATA SET NAME
---- ------ ------------ -------------
TYPE: Warning
REASON: VSAM data sets allocated on multiple volumes or
split into multiple key ranges have important data
recorded only in the first or primary volume's
VVDS. This information affects 37 data elements
that must be copied to the other VCA_VS
observations collected for this data set. This
report will be printed as part of the MICSLOG if
the primary volume's AMDSB is not present (the
primary volume was excluded from VCC or VCC volume
processing failed).
ACTION: The Space Collector output may need to be examined
to determine if some volumes are not being
scanned. If some volumes are being specifically
excluded from the Space Collector Scan job and
those volumes are the primary volumes for the VSAM
data sets indicated following this message, then
no action may be necessary. However, the impact
of many elements in the VCA_VS file for these data
sets being zero must be considered.
REFERENCES: None
+-----------------+
| V C A 0 0 4 0 2 |
+-----------------+
TEXT: >>>>> SYSID=%SYSID %ENDTS - DATA SETS CONTAIN
INCOMPLETE DATA IN VCA_VS
TYPE: Warning
REASON: This message is issued after VCA00401.
ACTION: See VCA00401W and VCA00403W.
REFERENCES: None
+-----------------+
| V C A 0 0 4 0 3 |
+-----------------+
TEXT: %DAAVCOMP %VOLSER %DAACNAME %DSNAME
TYPE: Warning
REASON: The data sets that have incomplete information due
to reasons described for the VCA00401W message are
indicated.
ACTION: See the VCA00401W message.
REFERENCES: None
+-----------------+
| V C A 0 0 4 1 0 |
+-----------------+
TEXT: %SYSID %DAAVCOMP %VOLSER %DAACNAME %DSNAME
>>>>> SPACE USED BY THE ABOVE DATA SET IS
GREATER THAN THE SPACE ALLOCATED.
TYPE: Warning
REASON: The space used is found to be greater than the
space allocated. Possible corrupted values in the
catalog. The value of space used is set to be
equal to space allocated.
ACTION: None
REFERENCES: None
+-----------------+
| V C A 0 0 4 1 1 |
+-----------------+
TEXT: VSAM EXCEPTION REPORT
THE FOLLOWING VOLUMES CONTAIN VSAM OBJECTS THAT
DO NOT HAVE VCC RECORDS FROM BOTH
A BASE CATALOG STRUCTURE (BCS) AND A VSAM
VOLUME DATA SET (VVDS) OR THAT ARE
DUPLICATED IN AN OLD-STYLE VSAM CATALOG, BCS,
AND/OR VVDS.
TYPE: Information
If you have turned the VVDS/BCS merge processing
option back on as described earlier (VCAXBCS macro
symbol changed from NO to YES), then all VSAM data
sets must have a VVDS record and a matching BCS
record. When a VSAM data set has only a VVDS
record, it is listed in this report and excluded
from the VCA_VS file.
Because the BCS record contains only seven data
elements, this report will be produced regardless
of the VCAXBCS value when a VSAM data set has a
BCS record but does not have a matching VVDS
record. The BCS record describing the VSAM data
set will be listed but will not be added to the
VCA_VS file. You must research the Space Collector
run to determine why the VVDS was not processed.
This report is also produced if a VSAM data set has
records collected from two or more old-style VSAM
catalogs, ICF Base Catalogs, or VVDS catalogs. All
duplicate defined VSAM data sets are listed and are
accompanied by VCA00413W, VCA00417I, and depending
upon the type of error encountered, messages
VCA00414W, VCA00415W, or VCA00416W.
ACTION: See VCA00417I for the Cluster, data set name, and
catalog name. Messages VCA00414W, VCA00415W, and
VCA00416W indicate the specific reasons for the
data set information not being written to the
VCA_VS file.
REFERENCES: None
+-----------------+
| V C A 0 0 4 1 2 |
+-----------------+
TEXT: TYPE (CAT) CLUSTER NAME REASON
DATA SET NAME CATALOG NAME
---- ----- ------------- -----------
TYPE: Information
REASON: This is a header message for VCA00414I, VCA00415I,
VCA00416I, and VCA00417I messages.
ACTION: None
REFERENCES: None
+-----------------+
| V C A 0 0 4 1 3 |
+-----------------+
TEXT: >>>>> VOLUME=%VOLSER - SYSID=%SYSID %WRKENDTS -
DATA SETS HAVE BEEN DELETED FROM VCA_VS
TYPE: Warning
REASON: This message is issued for every volume that has
data sets that were not written to the VCA_VS
file.
ACTION: None
REFERENCES: None
+-----------------+
| V C A 0 0 4 1 4 |
+-----------------+
TEXT: %DAACNAME DUPLICATE CATALOG ENTRIES
TYPE: Warning
REASON: Duplicate catalog entries have been detected for
the data set indicated by VCA00417I message.
DAACNAME is the Cluster name. The data set
information is not written to the VCA_VS file.
ACTION: Contact the DASD management group at your site to
resolve the problem.
REFERENCES: None
+-----------------+
| V C A 0 0 4 1 5 |
+-----------------+
TEXT: %DAACNAME NO MATCHING VVDS RECORD
TYPE: Warning
REASON: An entry for a VSAM data set was found in the BCS
catalog but no matching VVDS record was found.
ACTION: The data set information is not written to the
VCA_VS file. This could mean that there is an
entry in the catalog regarding this VSAM data set
although the data set no longer exists or the
volume on which the data set resides may be
excluded from the Space Collector scan job. If the
problem is the first case, contact the DASD
management group at your site to correct this
situation.
REFERENCES: None
+-----------------+
| V C A 0 0 4 1 6 |
+-----------------+
TEXT: %DAACNAME NO MATCHING BCS RECORD
TYPE: Warning
REASON: This message is issued when there is an entry for
a VSAM data set in the VVDS but not in any BCS.
BCSREQUIRED YES option has been specified in
VCAOPS indicating that an entry must be found for
a VSAM data set in the BCS catalog as well as the
VVDS so that the data set information can be
written to the VCA_VS file. The observation is
not written to the VCA_VS file.
ACTION: This situation could occur if the BCS catalog is
excluded from the Space Collector scan job. If
this is not the reason, then you may need to
contact the DASD management group at your site to
report this situation.
REFERENCES: None
+-----------------+
| V C A 0 0 4 1 7 |
+-----------------+
TEXT: %DAAVCOMP (%WRKTYPE) %DSNAME CATALOG = %WRKCATNM
TYPE: Information
REASON: This message is issued after VCA00414W, VCA00415W,
or VCA00416W messages. It indicates whether the
data set is a sequence set data set, the data set
name, and the catalog name and whether the entry
was found in a BCS or VVDS (B or V) catalog.
ACTION: None
REFERENCES: None
+-----------------+
| V C A 0 0 4 1 8 |
+-----------------+
TEXT: >>>>> %NNNNN VSAM DATA SETS DELETED FROM
%VVVVV VOLUMES.
TYPE: Warning
REASON: This message gives the total count of all the VSAM
data sets (NNNNN) from (VVVVV) whose information
is not written to the VCA_VS file.
ACTION: None
REFERENCES: None
+-----------------+
| V C A 0 0 4 1 9 |
+-----------------+
TEXT: >>>>> %WRKMSG1 VSAM DATA SETS DELETED FROM VCA_VS
VIA USRS_VS EXIT.
TYPE: Information
REASON: This message is issued if data sets were deleted
by means of the USRS_VS exit. This is a user-
defined exit.
ACTION: None
REFERENCES: None
+-----------------+
| V C A 0 0 5 0 0 |
+-----------------+
TEXT: --------------- BEGIN PHASE 5 ---------------
TYPE: Information
REASON: This message is displayed during the start of
phase 5 of the DAY090 job step.
ACTION: None
REFERENCES: None
+-----------------+
| V C A 0 0 5 0 1 |
+-----------------+
TEXT: VSAM/VOLUME EXCEPTION REPORT THE FOLLOWING
VOLUME(S) WERE NOT PROCESSED BY VCC. ALL VSAM DATA
SETS COLLECTED ARE ADDED TO THE VCA_VS FILE BUT ARE
NOT SUMMARIZED IN THE VCAVOA FILE.
TYPE CLUSTER NAME DATA SET NAME
----- ------------ -------------
TYPE: Information
REASON: This report title message is issued when volume
level observations were not found for certain
volumes. The volume level information for the
volume indicated in VCA00502W message is not
written to the VCAVOA file.
ACTION: See the VCA00502W message for action that may need
to be taken.
REFERENCES: None
+-----------------+
| V C A 0 0 5 0 2 |
+-----------------+
TEXT: >>>>> VOLUME=%VOLSER - SYSID=%SYSID %WRKENDTS -
VSAM DATA SETS HAVE NO VCAVOA OBSERVATION
TYPE: Warning
REASON: Volume level information has not been found for
the volume indicated in the message. The VCAVOA
file will not contain any information regarding
this volume.
ACTION: The Space Collector scan job output needs to be
examined to identify why the volume level
information records were not written.
REFERENCES: None
+-----------------+
| V C A 0 0 5 0 3 |
+-----------------+
TEXT: %DAAVCOMP %DAACNAME %DSNAME
TYPE: Information
REASON: This message is issued after VCA00502W. The data
sets indicated by this message would have
contributed to space calculations in the VOA file
for the volume indicated in the VCA00502W message.
The information regarding these data sets is
present in the VCA_VS file.
ACTION: None
REFERENCES: None
+-----------------+
| V C A 0 0 5 0 9 |
+-----------------+
TEXT: >>>>> %WRKMSG1 VOLUME RECORDS DELETED FROM VCAVOA
VIA USRSVOA EXIT.
TYPE: Information
REASON: This message is issued if data sets were deleted
by means of the USRSVOA exit. This is a user-
defined exit.
ACTION: None
REFERENCES: None
+-----------------+
| V C A 0 0 6 0 0 |
+-----------------+
TEXT: --------------- BEGIN PHASE 6 ---------------
TYPE: Information
REASON: This message is displayed during the start of
phase 6 of the DAY090 job step.
ACTION: None
REFERENCES: None
+-----------------+
| V C A 0 0 6 0 1 |
+-----------------+
TEXT: THIS REPORT IDENTIFIES SEVERAL POSSIBLE ERROR
CONDITIONS WHICH STEM FROM PROBLEMS IN THE VCC
COLLECTION PROCESS --- OR --- DFSMS FLAG
INCONSISTENCIES AT THE VOLUME OR THE DATA SET
LEVEL.
FOR MESSAGE GROUP VCA00602W, EITHER:
(1) SMS MANAGED VOLUME CONTAINS DATA SETS WHICH
ARE NOT SMS-MANAGED (MISSING SMS CELL)
OR
(2) FORMAT-1 DSCB FIELDS RESERVED FOR USE BY
DFSMS HAVE BEEN USED BY NON-IBM CODE RESULTING
IN A FALSE INDICATION OF AN SMS-MANAGED DATA
SET.
ACTION: OBSERVATION IS WRITTEN WITH SMS DATA
ELEMENTS MISSING
FOR MESSAGE GROUP VCA00607W:
(1) VCC DATA COLLECTION FOR THE SPECIFIED VOLUME
DID NOT COMPLETE PROPERLY. THE CAUSE IS SHOWN
IN THE VCCSTATS REPORT.
ACTION: OBSERVATION IS DISCARDED FROM THE VCADAA
FILE (SINCE VCAVOA OBSERVATION IS MISSING).
TYPE: Information
REASON: This report title is issued for the reasons
described in the message title.
ACTION: None
REFERENCES: None
+-----------------+
| V C A 0 0 6 0 2 |
+-----------------+
TEXT: >>>>> VOLUME=%VOLSER - SYSID=%SYSID %WRKENDTS -
ERRORS MATCHING VVDS (DFSMS CELL) DATA TO VTOC
TYPE: Warning
REASON: Errors were encountered during the matching of
SMS information found in the VVDS to the SMS
information found in the FORMAT1 DSCB (VTOC
information). A message VCA00603W or VCA00604W
will follow.
ACTION: Refer to VCA00603W or VCA00604.
REFERENCES: None
+-----------------+
| V C A 0 0 6 0 3 |
+-----------------+
TEXT: %DAADSTYP %DSNAME DFSMS INFORMATION CELL MISSING
TYPE: Warning
REASON: The DFSMS information cell in the VVDS is missing.
This could be because the data set being flagged
as a SMS managed data set in the VTOC is not
really a SMS managed data set, but the FORMAT-1
DSCB fields reserved for use by DFSMS have been
used by non-IBM code, resulting in a false
indication of an SMS-managed data set. This
message may be issued if the catalog portion of
the scan is turned off by specifying VSAMSUBT=0.
ACTION: The DFSMS fields will be missing in the VCA files.
REFERENCES: None
+-----------------+
| V C A 0 0 6 0 4 |
+-----------------+
TEXT: %DAADSTYP %DSNAME VTOC REC. NOT FLAGGED
AS A MANAGED DATA SET
TYPE: Warning
REASON: SMS information was found in the VVDS for a data
set. However, there is no SMS information for
this data set in the VTOC.
ACTION: Check to see if DAASMSID is turned off in
VCAGENIN.
REFERENCES: None
+-----------------+
| V C A 0 0 6 0 5 |
+-----------------+
TEXT: %DAADSTYP %DSNAME VOL. PROCESSING FAILED
- THIS RECORD IGNORED
TYPE: Warning
REASON: This message is issued when the volume record is
not found. This can mean that some kind of
failure occurred while the Space Collector was
trying to read the volume.
ACTION: Check the output of VCCSTATS message output for
the Space Collector scan job.
REFERENCES: None
+-----------------+
| V C A 0 0 6 0 6 |
+-----------------+
TEXT: %DSNAME MANAGED DATA SET IN VVDS BUT
NOT PRESENT IN VTOC
TYPE: Warning
REASON: This message is issued when the volume record is
present and the VVDS record is present but the
VTOC record for this data set is not present.
This could happen if the volume was being read by
VCC and it encounters a problem later on, so the
volume is only partially processed resulting in
some data sets being missed from the processing.
ACTION: Check the VCCSTATS output in the Space Collector
scan job to determine the problem.
REFERENCES: None
+-----------------+
| V C A 0 0 6 0 7 |
+-----------------+
TEXT: >>>>> VOLUME=%VOLSER - SYSID=%SYSID %WRKENDTS -
VOL. NOT SUCCESSFULLY PROCESSED
TYPE: Warning
REASON: This message is issued when errors are detected in
matching the volume records with the catalog and
VTOC records.
ACTION: See accompanying messages for action.
REFERENCES: None
+-----------------+
| V C A 0 0 6 0 8 |
+-----------------+
TEXT: >>>>> %COUNT1 DATA SETS IGNORED FROM %COUNT2
VOLUMES.
TYPE: Warning
REASON: This message is issued after the exception report
and gives the total data sets whose SMS
information was ignored due to the various causes
described in the messages COUNT1 = count of data
sets and COUNT2 = count of volumes.
ACTION: None
REFERENCES: None
+-----------------+
| V C A 0 0 6 0 9 |
+-----------------+
TEXT: >>>>> %NNNNNN DATA SETS DELETED FROM VCADAA VIA
USRSDAA EXIT.
TYPE: Information
REASON: This message is issued if data sets were deleted
by means of the USRSDAA exit. This is a user-
defined exit.
ACTION: None
REFERENCES: None
+-----------------+
| V C A 0 0 6 2 0 |
+-----------------+
TEXT: DFHSM-OWNED (ML1) DATA SETS FROM SYSID %SYSID
ENDTS %WRKENDTS)
-- HIGH-ORDER DSNAME QUALIFIER DETECTED IS:
%DSNODE1
TYPE: Information
REASON: When building the VCADAA file, VCA performs
pattern recognition on the DSNAME in search of
data set name characteristics that indicate a
DFHSM-owned data set migrated to a ML1 volume or a
backup version staged temporarily on a ML1 volume.
By doing so, there is a small risk that a user may
have inadvertently named a data set so that it is
mistaken for a ML-1 resident data set owned by
DFHSM. For example, if you allocate:
DSN=userid.HMIG.TEST.PLAN.DATA.FINAL
This would be mistaken for a ML1 data set because
the 2nd qualifier is HMIG and the 3rd qualifier
starts with the letter T, and it is 6 nodes in
total.
ACTION: When VCA finds a data set meeting the criteria of
a ML1 data set, it issues this message showing the
first-level (high-order) qualifier it found for
the data set. This value should correspond to the
MIGRATEPREFIX or the BACKUPPREFIX parameters of
the SETSYS command as established by the DFHSM
systems administrator. It is usually HSM or DFHSM
but can vary from company to company. The
important point is that it is a constant for any
given DFHSM implementation.
Therefore, you should have only one of these
messages. If you have more than one, it is likely
that a user data set has a pattern that is close
to that of DFHSM and these data sets should be
renamed.
REFERENCES: DFHSM Version 2.5 System Programmer's Command
Reference SH35-0084
DFHSM Version 2.5 System Programmer's Guide
SH35-0085
+-----------------+
| V C A 0 1 3 0 0 |
+-----------------+
TEXT: THE FOLLOWING FILE SYSTEMS AND THEIR DIRECTORY
ENTRIES WERE REJECTED BECAUSE OF INCOMPLETE SCAN.
TYPE: Information
REASON: This report will be printed as part of the MICSLOG
if the Space Collector fails to completely process
a file system and all its directory entries. A
subtype 3 record is written after successfully
collecting a file system and all its directory
entries. If either the file system record
(subtype 8) or its corresponding subtype 3 record
is missing, a problem in the scan is indicated and
the file system is rejected. The file system name
is displayed in the report. This is an
informational report and shows that the normal
error detection and restart process is working
correctly.
ACTION: The USS File Systems Collector output should be
examined to determine the problem.
REFERENCES: None
+-----------------+
| V C A 0 1 3 0 1 |
+-----------------+
TEXT: %DSNAME
TYPE: Information
REASON: This message is issued for every file system that
is not successfully processed by the USS File
Systems Collector. Information collected by the
file system or any of its directory entries will
not be written to the HFSDIR file.
ACTION: The USS File Systems Collector's output should be
examined to determine the problem.
REFERENCES: None
+-----------------+
| V C A 0 1 3 0 2 |
+-----------------+
TEXT: --------------------------------------------
TOTAL FILE SYSTEMS REJECTED=%MTYP7DEL',
--------------------------------------------
TYPE: Information
REASON: This message precedes messages VCA1300 and VCA1301
mentioned above. It shows a total count for the
file systems that were not scanned successfully.
ACTION: None
REFERENCES: None
+-----------------+
| V C A 0 1 3 0 3 |
+-----------------+
TEXT: --------------------------------------------
TOTAL DIRECTORY ENTRIES REJECTED=%MTYP8DEL',
--------------------------------------------
TYPE: Information
REASON: This message follows message VCA1304 mentioned
below. It shows a total count for the file systems
directory entries that were not scanned
successfully.
ACTION: None
REFERENCES: None
+-----------------+
| V C A 0 1 3 0 4 |
+-----------------+
TEXT: SYSID=%SYSID,RSRCEID=%RSRCEID,HFSRUN=%HFSRUN,VOL
SER=%VOLSER,TASKID=%TASKID
TYPE: Information
REASON: This message is issued for every file system's
directory entry that has not been successfully
processed by the USS File Systems Collector. The
file system or any of its directory entries
information collected will not be written to the
HFSDIR file.
ACTION: None
REFERENCES: None
+-----------------+
| V C A 0 1 3 1 8 |
+-----------------+
TEXT: >>>>> HFS DATA IS DETECTED BUT NOT PROCESSED
BECAUSE NOHFS OPTION IS SET IN VCAGENIN.
>>>>> ---------------------------------------
>>>>> HFS RECORDS READ FROM INPUT DATA = %HFSIN
TYPE: Information
REASON: This message is issued if HFS data is read during
DAY090 processing, but the HFS option in VCAGENIN
is set as NOHFS. This option controls whether the
USS Directory Entry (HFSDIR) file will be built or
ignored. The code to process HFS data is bypassed.
ACTION: Since HFS data is collected by executing the USS
File Systems Collector, which is independent of
the CA MICS Space Collector (VCC), you should
determine whether the HFS data should be
processed.
REFERENCES: None
+-----------------+
| V C A 0 1 3 1 9 |
+-----------------+
TEXT: >>>>> %RECXDIR DATA SETS DELETED FROM HFSDIR VIA
USRSDIR EXIT.
TYPE: Information
REASON: This message is issued if data sets were deleted
by means of the USRSDIR exit. This is a user-
defined exit.
ACTION: None
REFERENCES: None
Copyright © 2014 CA.
All rights reserved.
|
|