7. RETURN CODES AND MESSAGES › 7.2 Messages Description › 7.2.2 VCCNTRL Messages
7.2.2 VCCNTRL Messages
VCCBL01I
--------
Diagnostic dump for Unit(XXXX) Volume(VVVVVV)
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 Technical Support personnel
in determining the cause of the problem. Refer also to
VCCBL03E.
VCCBL03W
--------
I/O error on Unit(XXXX) Volume(VVVVVV) IOSCOD(AA)
CSW(BBBBBBBB ZZZZZZZZ)
VCC issues this message after several unsuccessful attempts
to communicate with the DASD storage subsystem or control
unit that volume 'vvvvvv' is attached to. 'xxxx' indicates
the device address. 'zzzzzz' is diagnostic information
returned in the Channel Status Word (CSW) to aid CA Technical
Support personnel in determining the cause of the problem. CA
Technical Support personnel may direct you to rerun VCC with
the TRACE=Y run-time parameter to provide further diagnostic
information. You can also check with your local Technical
Support personnel to determine if the DASD storage subsystem
has the most recent microcode level.
VCCNTRL action: Processing continues. Message VCCCN26W will
indicate the action taken by VCC for the
volume shown within the message.
Note: Some information regarding the device
that contained the error may not be
available in the VCCDATA record. This can
affect other CA MICS components that use
this data, such as the Accounting and
Chargeback Option and the Space Analyzer
Option (VCA).
VCCCN06E
--------
Load failed for Module(XXXXXXXX)
VCC issues this message if the LOAD for a VCC module fails,
and that module is required for proper VCC operation. A LOAD
failure can occur for one or more of the following reasons:
o The modules are missing from the VCC STEPLIB data
set.
o The required STEPLIB DD statement is missing from the
VCC JCL.
o The modules are missing from the linklist.
VCCNTRL action: Processing is terminated until the situation
that caused the error is corrected.
VCCCN07E
--------
Volume Table getmain failed; Increase region size and rerun
VCC issues this message if the GETMAIN for the DASD
configuration list and the VSCT fails (return code from
GETMAIN ^= 0). The GETMAIN is done from subpool zero;
therefore, to correct this situation you need to increase the
VCC JCL region size.
VCCNTRL action: Processing is terminated until the situation
that caused the error is corrected.
VCCCN09E
--------
Getmain failed for control file buffer; increase region size
and rerun
VCC issues this message if the GETMAIN for the control file
I/O buffer fails. This message is applicable only when SMF
is not the VCC recording medium (SMF=N). The size of the
buffer is the larger of:
o The largest SMF physical record (4089 bytes for VCC).
o The control file logical record length.
Increase the region size on the EXEC statement and rerun
VCC.
VCCNTRL action: Processing is terminated until the situation
that caused the error is corrected.
VCCCN10E
--------
Backup of VCCDATA data set has not been performed.
Perform backup and rerun
VCC issues this message only if SMF is not the VCC recording
medium (SMF=N). In this situation, the third step of the VCC
job did not complete successfully. Make sure that the backup
of the VCCDATA data set is done (this creates the SMF file
that goes into the CA MICS DAILY run) and that the third step
of the VCC job is run (this clears the "do backup" flag in
the VCCNTROL data set).
VCCNTRL action: Processing is terminated until the situation
that caused the error is corrected.
VCCCN11I
--------
Volume(VVVVVV) was processed during a previous VCC run but is
not in the current configuration
The VCCNTRL module has encountered a volume in the control
file that is not online in the current DASD configuration.
This message is informational only. You should research
this situation to make sure that DASD devices are not
mistakenly being missed by VCC.
VCCNTRL action: Processing continues normally.
VCCCN12I
--------
The following set of error messages is displayed under the
common identifier of VCCCN12I at the master console through
the use of the Write To Operator (WTO) facility. The
specification of the WTO run-time parameter enables this
action. The purpose of this VCC feature is to notify the
operator that VCC encountered some abnormal conditions that
may need to be examined further. VCC issues the following
WTO messages if problems (or potential problems) occur during
VCC processing:
ZZ VTOC scanning subtasks abended. Keep the
SYS1.DUMP__ data sets for diagnosis.
ZZ VSAM scanning subtasks abended. Keep the
SYS1.DUMP__ data sets for diagnosis.
VCCNTRL action: VCC termination processing continues.
See Section 5.3.2 for specifics on handling SYS1.DUMP
data sets.
The following WTO message is issued if VCC runs without
encountering any unusual problems:
VCC PROCESSING TERMINATED NORMALLY.
VCCNTRL action: VCC termination processing continues.
VCCCN13I
--------
The following set of error messages is displayed under the
common identifier of VCCCN13I at the master console through
the use of the Write To Operator (WTO) facility. The
specification of the WTO run-time parameter enables this
action. The purpose of this VCC feature is to notify the
operator that VCC encountered some abnormal conditions that
may need to be examined further. VCC issues the following
WTO messages if problems (or potential problems) occur during
VCC processing:
One or more WARNING messages have been issued
One or more ERROR messages have been issued
VCCNTRL action: VCC termination processing continues.
See Section 5.3.2 for specifics on handling SYS1.DUMP
data sets.
The following WTO message is issued if VCC runs without
encountering any unusual problems:
VCC PROCESSING TERMINATED NORMALLY.
VCCNTRL action: VCC termination processing continues.
VCCCN14W
--------
VCCVTOC work area getmain failed; Increase region size and
rerun
VCC issues this message if the GETMAIN in a VCCVTOC subtask
fails. Because other VCCVTOC subtasks may already have
obtained their work areas, this is a warning message. If no
data was collected, increase the region parameter on the EXEC
statement and rerun VCC.
VCCNTRL action: VCC termination processing continues.
VCCCN15E
--------
Internal error; Insufficient space for tables related to
devices; Issuing SDUMP
Save the SYS1.DUMPxx created by this message. Then increase
REGION size and rerun.
Note:
-----
VCC generates messages VCCCN16E through VCCCN22E when the
VCCNTRL module determines that the VTOC/catalog scan subtasks
had a problem writing records to the z/OS SMF data set.
These problems will not occur if VCC is using a separate data
set as the VCC recording medium. These messages are as
follows:
VCCCN16E
--------
VCC SMF record RDW is less than 18 bytes
VCC issues this message if an SMF record created by VCC is
less than 18 bytes in length (including the RDW). This is a
VCC problem and should be reported to CA Technical Support.
VCCCN17E
--------
SMF is not active
This message is issued if SMF recording is not active. Report
this message to your system programmer.
VCCCN18E
--------
IEFU83 SMF exit rejecting VCC SMF records
VCC issues this message if the IEFU83 SMF exit is rejecting
SMF records with the VCC SMFID (default is 198). If this is
occurring, make certain that the exit is modified to accept
VCC SMF records.
VCCCN19E
--------
VCC SMF data record has been lost
VCC issues this message if all the SYS1.MAN files are full
and no more SMF records can be written. Report this problem
to your system programmer.
VCCCN20E
--------
VCC SMF record number is not being recorded; Check SMFPRMXX
parmlib member
VCC issues this message if the SMFPRMXX SYS1.PARMLIB member
used in the current IPL specifies that SMF records with the
VCC SMFID are to be ignored. Modify SMFPRMXX to enable VCC
SMF recording.
VCCCN21E
--------
SMFWTM SVC could not establish error recovery
VCC issues this message if the SMF writer SVC (SVC 83) could
not establish recovery. Inform your system programmer.
VCCNTRL action: VCC termination processing continues.
VCCCN22E
--------
VCC SMF record not written due to SMF buffer shortage
VCC issues this message if SMF does not have enough buffers
to handle the record output rate currently being experienced
by the system. Inform your system programmer.
VCCNTRL action: VCC termination processing continues.
VCCCN23E
--------
VCC could not write a record to SMF
VCC issues this message if the GETMAIN for VCCWRITR buffers
fail. Because the size of this area is determined by the
value of the NUMWTRBUF parameter and the number of subtasks
specified, you may want to either increase the region size or
adjust those parameters.
VCCNTRL action: VCC termination processing continues.
VCCCN24E
--------
VCCNTRL module is not APF authorized; Re-link module with
AC=1 into an APF authorized load library
VCC issues this message if the VCCNTRL module is not APF-
authorized. VCC must run as an authorized task to perform
many of its tasks. This error can be caused by not placing
VCC modules in an authorized library, or by not coding the
AC=1 option when using the linkage editor to link module
VCCNTRL.
VCCNTRL action: VCC termination processing continues.
VCCCN25W
--------
SMS managed volumes were found online with SMS inactive;
Storage group set to blanks
VCC issues this warning message at normal termination if the
SMS address space was unavailable for the extraction of
storage group information. The storage group is set to
blanks in the record. If SMS is inactive, but no SMS-managed
volumes were detected during the scan, this message is not
produced.
VCCCN26W
--------
Volume(VVVVVV) on Device(DDDD) has an unknown device type;
MMMMMMMMMMMMMMMM
VCC was unable to obtain device hardware information for
volume (vvvvvv). 'hhhh' is the device unit address. If the
message indicates that the volume was excluded, this can
indicate that the hardware device is unsupported by VCC, or
the DASD storage subsystem does not have the most recent
microcode level. If the microcode level is current and the
problem persists after rerunning VCC, contact CA Technical
Support for further direction.
VCCNTRL action: The message indicates the action taken for
the volume shown. If the message indicates
that defaults are used, this can affect the
results of other CA MICS components such as
the Accounting and Chargeback Option and the
Space Analyzer Option (VCA).
VCCCN27I
--------
Stalled subtasks detected; Proceeding with main task
termination
An abnormal condition has occurred. During termination of the
main task of VCC, a last minute check of the TCB chain has
revealed that one or more subtasks are still present. This
is indicative of some sort of error in either the VSAM or
VTOC subtasks and probably traceable to messages written by
either VCCVSCAN or VCCVTOC. Rather than WAIT any further for
subtask termination that may never occur, VCC produces and
writes this message to the console log. It will get the
operator's attention since it requires manual deletion (it
will not roll off automatically.)
VCCNTRL action: VCC will issue the message to the console
only (not VCCSTATS) and then proceed to
terminate normally. z/OS will abend the
job with an S-A03 abend code.
The true error can be traced back to a subtask that has begun
but for some reason has not finished. Examine the VCCVTMSG
and VCCVSMSG logs and the VCCSTATS report to identify the
object (VTOC or catalog) where VCC processing failed to
finish.
VCCCN28W
--------
Volume(VVVVVV) not found in the VCCNTROL file; Default
duration will be assigned to all data sets on this volume
vvvvvv is either a brand-new volume serial number to this VCC
configuration or vvvvvv is back online after having been
offline in the prior VCC run. This is a warning message to
alert you that the VCA default DURATION will be used for all
data sets on this volume.
VCCNTRL action: VCC will issue the message and set the
previous VCC run time for this volume to
zero, which triggers the default duration
processing in VCA.
VCCCN29E
--------
SRM DONTSWAP failed for collector address space
Some IBM operating services that are invoked by the VCC
Space Collector Option require the VCC address space to be
temporarily non-swappable. A request to the SYSEVENT
DONTSWAP service to request non-swappable status failed.
VCCNTRL action: VCC terminates with a condition code of 12
since it is unable to utilize certain system
services.
VCCCN32I
--------
Data collection "backup-required" flag set in control file
The "backup-required" flag has been set and hardened to disk
in the VCC control file. The collection file backup and
control file reset steps must be completed successfully prior
to the next VCC Space Collector Option execution.
VCCNTRL action: VCC continues with termination processing.
VCCCN33E
--------
CA MICS Space Collector ABEND zzzz Rsn(rrrrrrrr)
Mod(mmmmmmmm) Info(iiiiiiii)
This message is issued if an abend occurs in the main task
of VCC. The message appears in the VCCSTATS log if it is
OPEN and is always written to the JES user log and the
console.
VCCNTRL action: A complete SVC dump is written to a
SYS1.DUMPxx data set. If VCCSTATS is OPEN,
a complete status report is written to
VCCSTATS. Scanning is probably incomplete.
Volumes not scanned and catalog structures
not scanned are indicated by the message
flag **NOT READ** in the rightmost column of
the report.
Report the problem to CA Technical Support. Save the
SYS1.DUMPxx data set and the complete VCC job including
VCCSTATS, VCCVTMSG, VCCVSMSG, and VCCHSMSG.
VCCCN34W or VCCVT34W
-------- --------
Failure to unpin device number hhhh; Vol(vvvvvv) Ret(dd)
Rsn(ee)
See the description for this message in section 7.2.7
(VCCVT34W).
VCCCN35I
--------
Normal termination resource recovery complete
Processing for the VCC Space Collector Option has completed
normally, and recovery and cleanup of all critical resources
have been completed successfully.
VCCCN36I
--------
Abnormal termination resource recovery complete
Processing for the VCC Space Collector Option has completed
following an abnormal condition. Recovery and cleanup of
all critical resources have been completed successfully.
