7. RETURN CODES AND MESSAGES › 7.2 Messages Description › 7.2.7 VCCVTOC Messages
7.2.7 VCCVTOC Messages
VCCVT01E
--------
TASK(nn) Getmain failed for DSCB resolution queues; Subtask
terminated
The GETMAIN for the storage area that holds the queues used
to resolve DSCB CCHHR chain pointers fails. If you want to
run with the number of VTOC scan subtasks that were
specified, increase the region size and rerun VCC.
VCCVTOC action: The subtask issuing the error message
terminates. All other subtask processing
continues.
VCCVT02E
--------
TASK(nn) Unable to establish recovery environment; Subtask
terminated
The ESTAEX issued by VCCVTOC fails. If a subtask runs without
abend recovery, unending waits can result; therefore, the
subtask terminates.
VCCVTOC action: The subtask issuing the error message
terminates. All other subtask processing
continues.
VCCVT03E
--------
TASK(nn) Getmain failed for I/O area; Subtask terminated
The GETMAIN for the area that builds VSAM data event control
blocks fails and VTOC scan processing cannot continue.
Increase VCC region size and rerun.
VCCVTOC action: The subtask issuing the error message
terminates. All other subtask processing
continues.
VCCVT04E
--------
TASK(nn) Getmain failed for I/O buffer; Subtask terminated
The GETMAIN for the area that VSAM uses as an I/O buffer to
read in a track's worth of DSCBs fails. Increase the region
size and rerun.
VCCVTOC action: The subtask issuing the error message
terminates. All other subtask processing
continues.
VCCVT05W
--------
TASK(nn) Allocation error - Vol(vvvvvv) Ret(eeeeeeee)
Rsn(rrrrrrrr)
The allocation for the volume on which a VTOC resides fails.
For the error reason, information reason, and return code
meanings, see IBM publication GC28-0627, OS/VS2 MVS System
Programming Library: Job Management.
VCCVTOC action: The subtask issuing the error message
terminates processing for the VTOC on that
volume and continues normally.
VCCVT06W
--------
TASK(nn) CVAF map volume error, Vol(vvvvvv) Ret(eeeeeeee)
Rsn(rrrrrrrr)
A call to CVAF for volume free space extents fails. You can
determine the volume serial number of the device by examining
the VCC VTOC scan log (the output on VCCVTMSG) and finding
the VCCVT10I message issued by the same task (nn). VCCVTOC
is in the middle of building the VTOC/VOLUME SMF record free
space extents.
VCCVTOC action: The subtask issuing the warning message
continues processing the VTOC as if it did
not have an index. The SMF record is
written as is, with an error indication
turned on indicating that an error occurred.
VCCVT07W
--------
TASK(nn) CVAF map VTOC error - Vol(vvvvvv) Ret(eeeeeeee)
Rsn(ssssssss)
A call to CVAF for the number of free DSCBs in the VTOC
fails. You can determine the volume serial number in the
same way as with message VCCVT06W.
VCCVTOC action: The subtask issuing the warning message will
read the entire VTOC since the number of
used DSCBs cannot be determined.
VCCVT08W
--------
TASK(nn) VTOC not initialized - Vol(vvvvvv) volume not
processed
The DASD volume specified by Vol(vvvvvv) did not contain a
valid Volume Table of Contents (VTOC); therefore, the scan
task is unable to process the volume.
VCCVTOC action: The subtask issuing the error message will
terminate processing of the current VTOC and
continue with the next VTOC.
VCCVT09I
--------
TASK(nn) VTOC collection scan processing termination complete
A VCCVTOC subtask cannot find another VTOC to process; it
terminates.
VCCVTOC action: The subtask issuing this message continues
with termination.
VCCVT10I
--------
TASK(nn) VTOC scan initiation - Vol(vvvvvv) Unit(uuuu)
Device(dddddd)
A VCCVTOC subtask is about to begin processing a VTOC on
volume serial number vvvvvv.
VCCVTOC action: The subtask issuing this message continues
processing the VTOC.
VCCVT11I
--------
TASK(nn) VTOC scan completion - Vol(vvvvvv)
A VCCVTOC subtask has completed processing a VTOC on volume
serial number vvvvvv.
VCCVTOC action: The subtask issuing this message continues
processing the next VTOC (if any).
VCCVT12I
--------
TASK(nn) Reserve not obtained - Vol(vvvvvv) will be re-tried
again later
A VCCVTOC subtask has tried three times to ENQ/RESERVE a VTOC
and has failed on each attempt.
VCCVTOC action: The subtask will place this volume back on
the queue for later processing, and will
increment the RESRETRY value for this
volume.
VCCVT13E
--------
TASK(nn) Critical scan error; processing termination
initiated
A VCCVTOC subtask is about to select another VTOC for
processing but on examining the global error flags, finds
that a critical error has occurred, causing VCC to terminate
further processing.
VCCVTOC action: The subtask issuing this message terminates.
VCCVT14E
--------
TASK(nn) Scan task ABEND zzzzz- Vol(vvvvvv) Rsn(rrrrrrrr)
Data Collection Not Initiated
where: nn = Task number that abended
zzzzz = System abend code in hex (Shhh) or
user abend code in decimal (Udddd)
vvvvvv = Volume being addressed at time of
abend
VCCVTOC action: Checking performed on VTOCERR values.
DUMP taken to a SYS1.DUMPxx data set (*).
Message echoed to console and JES log.
VSAM subtask terminates.
Note that a dump is only taken for the first VTOC subtask
that abends. If more than one subtask of this type abends,
the message is written to document which structure was being
processed, but the dump is bypassed.
See section 5.3.2 for instructions on what to do with the
dumps if you receive this message.
VCCVT15W
--------
TASK(nn) qqq Queue residuals - Vol(vvvvvv) possible DSCB
chain corruption
A VCCVTOC subtask completes processing for a VTOC and finds
that there are still unresolved entries in the DSCB
resolution queues. This condition can occur if VCC is run
without VTOC serialization and an update of the VTOC occurs
during VCC processing, causing VCC to miss a DSCB chain
connection and resulting in unresolved entries in the
resolution queues. There may actually be a broken DSCB chain
resulting from a hardware error. If this message occurs, you
should take action to determine the extent of the problem.
where: qqq = DSN if data set resolution queue or
EXT if free space resolution queue
vvvvvv = Volume being processed at time of
abend
VCCVTOC action: The subtask issuing this message continues
with the next VTOC.
VCCVT16E
--------
TASK(nn) SMF interface error - Scan processing terminated
A VCCVTOC subtask receives a non-zero return code from the
VCCWRITR routine, and SMF was selected as the VCC recording
medium.
VCCVTOC action: The subtask issuing this message terminates.
VCCVT17W
--------
TASK(nn) Unable to open VTOC - Vol(vvvvvv)
A VCCVTOC subtask cannot open a VTOC.
VCCVTOC action: The subtask issuing this message continues
with the next VTOC.
VCCVT18W
--------
TASK(nn) SMF record overflow - Vol(vvvvvv) freespace extent
segments incomplete
A VCCVTOC subtask is building the VTOC/VOLUME record and runs
out of room in the record to add more free space segments.
This is a warning message because volume free space segments
are not used for DASD space accounting. The VCA reports for
the volume will not be valid.
VCCVTOC action: The subtask issuing this message continues
with the next VTOC.
VCCVT19W
--------
TASK(nn) Lost tracks detected - Vol(vvvvvv) Lost(tttttttt)
where: vvvvvv = Volume being addressed at time of
abend
tttttttt = The number of tracks, in decimal, that
were unaccounted for by the scan task.
The verification calculation performed by the VTOC scan task
failed to reconcile the total number of tracks on the DASD
volume with the number of tracks that should exist based on
the physical geometry of the device. There can be different
causes for this condition. The most common cause is when
orphan extent DSCBs exist in the VTOC.
VCCVTOC action: The subtask issuing this message continues
with the next VTOC.
VCCVT20E
--------
TASK(nn) Getmain failed for VSAM scan work area; Subtask
terminated
The GETMAIN for the storage area that is used when data sets
of the form SYS1.VVDS.Vvolser are added to the CNQ fails. If
you want to run with the number of VTOC scan subtasks that
were specified, increase the region size and rerun VCC.
VCCVTOC action: The subtask issuing the error message
terminates. All other subtask processing
continues.
VCCVT21W
--------
TASK(nn) Reserve retry failed - Vol(vvvvvv) reserve will not
be done
Repeated attempts to reserve the VTOC for the indicated
volume have failed (the number of attempts is specified by
the RESRETRY run-time option). Because RESFAILOK=Y was coded
or defaulted, the reserve is bypassed for this volume.
VCCVTOC action: The subtask issuing the error message
will process the volume without doing a
reserve against it. Data errors may result.
VCCVT22W
--------
TASK(nn) Reserve retry failed - Vol(vvvvvv) will not be
processed
Repeated attempts to reserve the VTOC for the indicated
volume have failed (the number of attempts is specified by
the RESRETRY run-time option). Because RESFAILOK=N was
coded, the volume will not be processed.
VCCVTOC action: The subtask issuing the error message
will bypass this volume and select another
one to process. The volume will not be
processed in this VCC run.
VCCVT23W
--------
TASK(nn) Storage group error - Vol(vvvvvv) Ret(eeee)
Rsn(rrrr)
where:
vvvvvv is the volume serial number for which storage
group information was requested
eeee is the return code from the SMS address space
in decimal
rrrr is the reason code associated with the SMS
request and error
This message is produced when an attempt to get the storage
group name for a volume resulted in an error.
Processing continues with the name of the storage group set
to blanks for this volume.
VCCVT24W
--------
TASK(nn) Track calc error nnn - Vol(vvvvvv) Ret(eeee)
Rsn(rrrr) defaulting to Device(3390)
where:
nnn is either "(P)" or "(D)" depending on whether
the TRKCALC information was requested for the
number of 4 KB pages per track (P) or the
number of DSCBs per track (D).
vvvvvv is the volume serial number for which
TRKCALC information was requested
eeee is the return code from the TRKCALC service
routine
rrrr is the reason code associated with the
TRKCALC error code
This message is produced when an attempt to get geometric
information about a DASD volume resulted in an error.
Processing continues with the information defaulted to a
DASD device type 3390.
VCCVT25I
--------
TASK(nn) VTOC collector initialization processing is
complete; TCB(tttttt)
where:
tttttt is the virtual storage address in hex of the
task control block (TCB) for the subtask
This message is produced following subtask initialization
completion for VTOC scanning.
VCCVTOC action: The subtask begins VTOC scan processing.
VCCVT26W
--------
TASK(nn) Status check error - Vol(vvvvvv) allocation will
not be done
where:
vvvvvv is the volume serial number of the VTOC for
which allocation was attempted
This message is produced whenever status indicators in the
UCB for the selected DASD volume indicate a condition that
will prevent successful allocation of the volume.
The queue entry for the selected volume is placed back on
the scan queue and the next available volume is selected.
VCCVT27W
--------
TASK(nn) Status check error - Vol(vvvvvv) device is being
bypassed
where:
vvvvvv is the volume serial number of the VTOC for
which allocation was attempted
This message is produced whenever status indicators in the
UCB for the selected DASD volume indicate a condition that
will prevent successful allocation of the volume.
The queue entry for the selected volume is placed back on
the scan queue and the next available volume is selected.
VCCVT28I
--------
TASK(nn) VTOC collector fixed pp I/O buffer pages
where:
pp is the number of 4 KB I/O buffer pages that were
fixed by the collector subtask
When conditions permit, the scan subtask will attempt to page
fix the I/O buffers to improve performance.
VCCVTOC action: Processing continues normally. This is an
informational message.
VCCVT29W
--------
TASK(nn) DEVTYPE return error - Vol(vvvvvv) Ret(rr) Rsn(xx)
where:
vvvvvv = Volume being processed at time of the
error return from the DEVTYPE service
rr = is the return code from the DEVTYPE service
xx = is the reason code associated with the
DEVTYPE service
VCCVTOC action: The subtask issuing this message continues
with the next VTOC.
VCCVT30W
--------
TASK(nn) qqq Element(s) NTF - Vol(vvvvvv) possible DSCB
extent corruption
A VCCVTOC subtask was unable to locate a specified qqq
element on the qqq queue. This is typically an extent entry
for a data set being processed. This condition can occur if
VCC is run without VTOC serialization and an update of the
VTOC occurs during VCC processing, causing VCC to miss a DSCB
chain connection and resulting in unresolved entries in the
resolution queues. There may actually be a broken DSCB chain
resulting from a hardware error. If this message occurs, you
should take action to determine the extent of the problem.
where: qqq = EXT if free space resolution queue
vvvvvv = Volume being processed at time of
abend
VCCVTOC action: The subtask issuing this message continues
with the next VTOC.
VCCVT31W
--------
TASK(nn) ABEND zzzz Recovery - Vol(vvvvvv) Data Collection
Not Initiated
A recoverable abend occurred while processing a VTOC. Since
the abend was determined to be recoverable, recovery is
invoked that performs cleanup on the environment and
releases any held resources. The most common recoverable
abend is a S213, which occurs when attempting to open a VTOC
and there is no VTOC on the DASD volume.
where: zzzz = System abend code in hex (Shhh) or
user abend code in decimal (Udddd)
vvvvvv = Volume being processed at time of
abend
VCCVTOC action: The subtask issuing this message continues
with the next VTOC.
VCCVT32E
--------
TASK(nn) ABEND zzzz Recursion - Vol(vvvvvv) Data Collection
Not Initiated
An abend occurred during recovery processing of a previous
abend condition. Regardless of whether the previous abend
was recoverable or not, the subsequent abend has rendered the
situation non-recoverable and the subtask will terminate.
where: zzzz = System abend code in hex (Shhh) or
user abend code in decimal (Udddd)
vvvvvv = Volume being processed at time of
abend
VCCVTOC action: The subtask issuing this message is
terminated.
VCCVT34W or VCCCN34W
-------- --------
TASK(nn) Failure during UNPIN - Vol(vvvvvv) Device(dddd)
Ret(eeee) Rsn(rrrr)
where:
vvvvvv is the volume serial number for which an
attempt to UNPIN the UCB was requested.
dddd is the device number for which an attempt
to UNPIN the UCB was requested.
eeee is the return code from the UCB services
(in hex).
rrrr is the reason code associated with the UCB
service request and failure (in hex).
These codes are documented in the appropriate IBM
publication.
Pinning a UCB ensures that the UCB cannot be deleted while a
program is in the process of looking at a UCB. VCCNTRL
establishes the PIN status for all online devices that will
be scanned, issuing the UNPIN service for devices to be
EXCLUDED. VCCVTOC issues the UNPIN service for devices that
scanned successfully; VCCVTOC also issues the UNPIN service
in the ESTAEX (error routine) for devices where the VTOC
scan did not complete successfully.
VCCVTOC action: Processing continues after the message to
VCCVTMSG.
VCCNTRL action: Processing continues after the message to
VCCSTATS.
VCCVT40W
--------
TASK(nn) Allocation error - Vol(vvvvvv) Ret(ee)
Rsn(rrrrrrrr) DSN(dd)
where:
vvvvvv is the volume serial number of the DASD
volume where the data set is located.
eeee is the return code from allocation
services (in hex).
rrrr is the reason code from allocation services
(in hex).
dd is the data set name of the data set being
processed.
Prior to obtaining the extended attributes for a data set,
the data set is dynamically allocated. This message indicates
that an error occurred during this allocation.
VCCVTOC action: Processing continues after the message to
VCCVTMSG. All of the normal processing for
the data set is performed, but none of the
extended attribute data is collected. The
attributes not collected are those
concerning internal space utilization for
PDS/E data sets.
VCCVT41I
--------
TASK(nn) ssss uuuuuuuuuuuuuuu - Vol(vvvvvv) DSN(dd)
where:
ssss is the type of data set being processed
(for example, "PDSE").
uuuuuu tells what is preventing the collection
of extended attributes for the data set
(for example, "Uncataloged").
vvvvvv is the volume serial number of the DASD
volume where the data set is located.
dd is the data set name of the data set being
processed.
The Data Set Attribute Retrieval (DSAR) function has
encountered a condition that prevents it from collecting the
extended attributes for the data set being processed. In
this event, the extended attribute elements for the data set
being processed will contain zeros.
VCCVTOC action: Processing continues after the message to
VCCVTMSG. All of the normal processing for
the data set is performed, but none of the
extended attribute data is collected. The
attributes not collected are those
concerning internal space utilization for
PDS/E data sets.
VCCVT42I
--------
TASK(nn) ssss Error returned - Ret(eeeeeeee) Rsn(rrrrrrrr)
DSN(dd)
where:
ssss is the type of data set being processed.
(for example, "PDSE")
eeeeeeee is the return code value in hex that was
returned during DSAR processing. In some
cases, the return code may have been
returned by an operating system service.
rrrrrrrr is the reason code value in hex that was
returned during DSAR processing. In some
cases, the reason code may have been
returned by an operating system service.
dd is the data set name of the data set being
processed.
The Data Set Attribute Retrieval (DSAR) function has
encountered a condition that prevents it from collecting the
extended attributes for the data set being processed. In
this event, the extended attribute elements for the data set
being processed will contain zeros. This message may be
accompanied by 1 or more VCCVT47I messages that provide
additional descriptive information.
VCCVTOC action: Processing continues after the message to
VCCVTMSG. All of the normal processing for
the data set is performed, but none of the
extended attribute data is collected. The
attributes not collected are those
concerning internal space utilization for
PDS/E data sets.
VCCVT43E
--------
TASK(nn) ssss Attribute error - Field(aaaaaa) Ret(ee)
DSN(dd)
where:
ssss is the type of data set being processed
(for example, "PDSE").
aaaaaa is the name of the attribute element that was
being processed by the DSAR service.
ee is the return code value in hex that was
returned during DSAR processing.
dd is the data set name of the data set being
processed.
The Data Set Attribute Retrieval (DSAR) function has
encountered an attribute specification error condition that
prevents it from collecting the extended attributes for the
data set being processed. In this event, the extended
attribute elements for the data set being processed will
contain zeros. This message may be accompanied by 1 or more
VCCVT47I messages that provide additional descriptive
information.
VCCVTOC action: Processing continues after the message to
VCCVTMSG. All of the normal processing for
the data set is performed, but none of the
extended attribute data is collected. The
attributes not collected are those
concerning internal space utilization for
PDS/E data sets.
VCCVT44E
--------
TASK(nn) ssss Missing data - Field(aaaaaa) DSN(dd)
where:
ssss is the type of data set being processed
(for example, "PDSE").
aaaaaa is the name of the attribute element that was
being processed by the DSAR service.
dd is the data set name of the data set being
processed.
The Data Set Attribute Retrieval (DSAR) function has received
incomplete extended attribute data from the operating system.
The design does not permit partial data element population.
In this event, all extended attribute elements for the data
set being processed will contain zeros. This message may be
accompanied by 1 or more VCCVT47I messages that provide
additional descriptive information.
VCCVTOC action: Processing continues after the message to
VCCVTMSG. All of the normal processing for
the data set is performed, but none of the
extended attribute data is collected. The
attributes not collected are those
concerning internal space utilization for
PDS/E data sets.
VCCVT45E
--------
TASK(nn) ssss Unknown error - Flags(xxxxxx) DSN(dd)
where:
ssss is the type of data set being processed
(for example, "PDSE").
xxxxxx is an information field containing hex values
indicating status of the error condition.
dd is the data set name of the data set being
processed.
The caller of the Data Set Attribute Retrieval (DSAR)
function has been presented with a subordinate error code
that is not known to the caller. The most likely cause of
this condition is a version mismatch of VCC modules in the
LOADLIB being used for the execution. In this event, the
extended attribute elements for the data set being processed
will contain zeros. This message may be accompanied by 1 or
more VCCVT47I messages that provide additional descriptive
information.
VCCVTOC action: Processing continues after the message to
VCCVTMSG. All of the normal processing for
the data set is performed, but none of the
extended attribute data is collected. The
attributes not collected are those
concerning internal space utilization for
PDS/E data sets.
VCCVT46E
--------
TASK(nn) ssss Unknown return - Ret(eeeeee) DSN(dd)
where:
ssss is the type of data set being processed
(for example, "PDSE").
eeeeee is the return code value in hex that was
returned during DSAR processing.
dd is the data set name of the data set being
processed.
The caller of the Data Set Attribute Retrieval (DSAR)
function has been presented with a return code that is not
known to the caller. The most likely cause of this condition
is a version mismatch of VCC modules in the LOADLIB being
used for the execution. In this event, the extended
attribute elements for the data set being processed will
contain zeros. This message may be accompanied by 1 or more
VCCVT47I messages that provide additional descriptive
information.
VCCVTOC action: Processing continues after the message to
VCCVTMSG. All of the normal processing for
the data set is performed, but none of the
extended attribute data is collected. The
attributes not collected are those
concerning internal space utilization for
PDS/E data sets.
VCCVT47I
--------
TASK(nn) + variable_text
The Data Set Attribute Retrieval (DSAR) function has
encountered an exception condition as noted by a message in
the VCCVT41I thru VCCVT46E range. This message contains
self-describing text that provides additional information
about the exception condition.
VCCVTOC action: Processing continues after the message to
VCCVTMSG. All of the normal processing for
the data set is performed, but none of the
extended attribute data is collected. The
attributes not collected are those
concerning internal space utilization for
PDS/E data sets.
VCCVT50W
--------
TASK(nn) ssss mmmmmmmmmmmmmmm - Vol(vvvvvv) Ret(rr) Rsn(xx)
DSN(dd)
The Data Set Attribute Retrieval (DSAR) function was
attempting to process a PDS/E data set that is probably
damaged or corrupted. An S0F4 abend has occurred within a
system service during this processing. Additional
information will appear in a VCCVT51W scan log message.
where:
ssss = The type file that was being processed when
the error condition occurred; currently this
will either be PDSE or HFS
mmmmmm = Description of the error condition that was
presented to the VTOC scan task; possible
descriptions include:
Info Returned
Warning
Invalid Parm
Caller Error
Environmental
Dir I/O Error
Media Error
Logical Error
Severe Error
Unknown Error
vvvvvv = Volume being processed at time the error
condition occurred
rr = is the return code from the system service
xx = is the reason code associated with the
return code from the system service
VCCVTOC action: Processing continues after the message to
VCCVTMSG. All of the normal processing for
the data set is performed, but none of the
extended attribute data is collected. The
attributes not collected are those
concerning internal space utilization for
PDS/E data sets.
