![[OpenVMS documentation]](../../images/openvms_doc_banner_top.gif)
|
![[Site home]](../../images/buttons/bn_site_home_off.gif)
![[Send comments]](../../images/buttons/bn_comments_off.gif)
![[Help with this site]](../../images/buttons/bn_site_help_off.gif)
![[How to order documentation]](../../images/buttons/bn_order_docs_off.gif)
![[OpenVMS site]](../../images/buttons/bn_openvms_off.gif)
![[Compaq site]](../../images/buttons/bn_compaq_off.gif)
|
|
Updated:
11 December 1998
|
OpenVMS System Messages: Companion Guide for Help
Message Users
VALCNVERR, error converting value
Facility: MOUNT, Mount Utility
Explanation: A MOUNT switch parameter is invalid. For
example, a nonnumeric character might be specified in a numeric
parameter.
User Action: Correct the invalid parameter.
VASOVF, system virtual address space limit exceeded
Facility: SYSBOOT, System Bootstrap Facility
Explanation: The combination of SYSGEN parameters used
to specify various capacities within the operating system have pushed
the size of the operating system address space over the limit allowed
by the VAX architecture.
User Action: Reduce one of the parameters
(VIRTUALPAGECNT, BALSETCNT) that contribute to the virtual address
space size required by the OpenVMS system. By using AUTOGEN to set
these values for your system, you avoid selection of parameter
combinations that cause system space to overflow its architectural
boundaries.
VBNERROR, 'file-spec' has duplicate blocks 'n' through 'n'
Facility: BACKUP, Backup Utility
Explanation: The specified blocks of the specified
file were present more than once in the input save set. Data in the
save set may be corrupt.
User Action: Examine the file for corruption and
reconstruct as necessary. If this error occurs during a disk-to-disk
(copy) operation, it indicates a software error in the Backup utility;
in this case, contact a DIGITAL support representative.
VBNMAPFAIL, virtual block map failure
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an
irrecoverable, inconsistent condition. After all physical memory is
written to a system dump file, the system automatically reboots if the
BUGREBOOT system parameter is set to 1.
User Action: Use the BACKUP command with the /IGNORE=NOBACKUP qualifier to make a backup save set of the system dump file and the error log file active at the time of the error. Contact a DIGITAL support representative and describe the conditions leading to the error.
VBNMISSING, 'file-spec' has missing blocks 'n' through 'n'
Facility: BACKUP, Backup Utility
Explanation: The specified blocks of the specified
file were missing from the input save set. Data in the blocks is lost.
User Action: Examine the file for corruption and
reconstruct as necessary. If this error occurs during a disk-to-disk
(copy) operation, it indicates a software error in the Backup utility;
in this case, contact a DIGITAL support representative.
VBNPASTEOF, 'file-spec' has blocks 'n' through 'n' past end-of-file
Facility: BACKUP, Backup Utility
Explanation: The specified blocks of the specified
file were present in the input save set although they follow the
end-of-file block. Data in the save set may be corrupted.
User Action: Examine the file for corruption and
reconstruct as necessary. If this error occurs during a disk-to-disk
(copy) operation, it indicates a software error in the Backup utility;
in this case, contact a DIGITAL support representative.
VECINUSE, vector is in use
Facility: SYSGEN, System Generation Utility
Explanation: The interrupt vector address specified in
a CONNECT command is being used by another device.
User Action: Change the vector address in the device
driver and reenter the command.
VEC_TOBIG, symbol vector reset data exceeds table size
Facility: LOADER, Executive Image Loader
Explanation: An attempt to load an executive image
failed because the image's symbol vector updates for SYS$BASE_IMAGE and
SYS$PUBLIC_VECTORS exceed the size of the loader's internal tables.
User Action: Contact a DIGITAL support representative.
VERIFYERR, verification error for block 'n' of 'file-spec'
Facility: BACKUP, Backup Utility
Explanation: During a compare or verify operation, the
data in the specified block of the specified file did not agree with
the input file. If other file activity is occurring on the volume, the
error may result because another user modified the file during the
backup procedure.
User Action: None; however, note that the copies are
inconsistent.
Virtual Circuit Timeout - REMOTE PORT 'xxx'
Facility: Cluster Port Driver
Explanation: The port driver closed the virtual
circuit that the local CI port opened to the remote port. This closure
occurs if the remote node is running CI Microcode Version 7 or higher,
and the remote node failed to respond to any messages sent by the local
node.
User Action: This error is normal if the remote system
halted, crashed, or is shut down. This error may mean the local node's
PASTIMOUT SYSGEN parameter is set too low, especially if the remote
node is running privileged user-written software.
VMB-F-Bootfile not contiguous
Facility: VMB, Virtual Memory Boot
Explanation: The file [SYSEXE]SYSBOOT.EXE is located,
but is not contiguous.
User Action: The disk you are attempting to bootstrap
cannot be bootstrapped. Obtain another copy of the system disk.
VMB-F-Failed to initialize device
Facility: VMB, Virtual Memory Boot
Explanation: An error was encountered in the load path
while the OpenVMS operating system was trying to initialize the boot
device.
User Action: Try initializing again. If this fails,
contact a DIGITAL support representative.
VMB-F-I/O error reading boot file
Facility: VMB, Virtual Memory Boot
Explanation: An uncorrectable read error occurred
while the file [SYSEXE]SYSBOOT.EXE was being read.
User Action: Try rebooting the disk. If subsequent
attempts fail, obtain another copy of the system disk.
VMB-F-Nonexistent drive
Facility: VMB, Virtual Memory Boot
Explanation: The specified drive number does not exist.
User Action: Specify an appropriate device unit to the
console program, or use a different console bootstrap command procedure.
VMB-F-Unable to locate BOOT file
Facility: VMB, Virtual Memory Boot
Explanation: The file [SYSEXE]SYSBOOT.EXE could not be
found.
User Action: An attempt is being made to bootstrap a
volume that does not contain an OpenVMS binary system. Attempt to
reboot using an appropriate disk volume.
VMB-F-Unexpected exception
Facility: VMB, Virtual Memory Boot
Explanation: An unexpected exception occurred while
the primary bootstrap (VMB.EXE) was being executed. This condition
probably indicates a corrupted SYSBOOT.EXE file or a hardware failure.
User Action: Determine the source of the error, and
either obtain a new copy of the system disk or contact a DIGITAL support representative.
VMB-F-Unexpected machine check
Facility: VMB, Virtual Memory Boot
Explanation: An unexpected machine check occurred
while the primary bootstrap (VMB.EXE) was being executed. This
condition probably indicates a corrupted SYSBOOT.EXE file or a hardware
failure.
User Action: Determine the source of the error, and
either obtain a new copy of the system disk or contact a DIGITAL support representative.
VOLALRMNT, another volume of same label already mounted
Facility: MOUNT, Mount Utility
Explanation: This message can occur under either of
the following conditions:
- A request was made to mount a volume that has the same label as a
volume already mounted. Shared, group, and system volumes that are
mounted concurrently must have unique volume labels.
- A request was made to mount a volume that is already mounted
/GROUP for another group.
User Action: Take one of the following actions, as
appropriate:
- Mount the volume as a private volume if it does not have to be
shared.
- Mount the volume as a private volume and change its label using
the DCL command SET VOLUME/LABEL. Then dismount the volume and mount it
as originally intended.
- Wait until the conflicting volume has been dismounted.
- If the volume is already mounted to another group, wait for the
volume to be dismounted from that group.
You can determine the status and ownership of a conflicting volume by
using the DCL command SHOW DEVICES/FULL/MOUNTED.
VOLIDENT, label = 'volume-label', owner = 'user-name', format =
'volume-format'
Facility: MOUNT, Mount Utility
Explanation: This message identifies the label
information recorded on the volume after INCVOLLABEL or NOHOMEBLK
errors occur on a MOUNT request.
User Action: None. If the displayed volume label is
the one you want, reenter the command using this label.
VOLINSET, 'device-name' is already part of a volume set
Facility: BACKUP, Backup Utility
Explanation: The specified volume is already bound to
a volume set. The volume cannot be used as a save-set disk.
User Action: Retry the operation using a properly
initialized Files--11 On-Disk Structure Level 2 volume.
VOLINSET, volume is already part of another volume set
Facility: MOUNT, Mount Utility
Explanation: The volume specified in the DCL command
MOUNT/BIND is part of another volume set.
User Action: Check the device name specified. Either
use another volume or initialize this one.
VOLLABERR, its label does not match the one requested
Facility: BACKUP, Backup Utility
Explanation: The Backup utility tried to mount a tape
whose label does not match the ones specified with the /LABEL qualifier.
User Action: Mount the tape with the correct label.
VOLNAME, volume 'volume-name' in
Facility: MOUNT, Mount Utility
Explanation: This message is optionally issued with
the MOUNTDEV message. It includes the volume name of the volume being
mounted.
User Action: None.
VOLNOTPRESENT, relative volume 'volume-id' is not present
Facility: RBLD, REBUILD Command (Mount Utility)
Explanation: The rebuild operation could not find the
specified volume.
User Action: Ensure that all volumes in the volume set
are available. Take action based on the accompanying message.
VOLOERR, must override owner identifier field in VOL1 label on
'device-name'
Facility: MOUNT, Mount Utility
Explanation: The owner identifier field of the VOL1
label must be overridden to allow access to the tape. The OWNER_ID
option of the MOUNT/OVERRIDE command is used to interchange magnetic
tapes between the OpenVMS operating system and other Digital operating
systems.
User Action: Reenter the MOUNT command and include the
/OVERRIDE=OWNER_ID option.
VOLOOO, volume 'label' is out of order, Volume label 'label' was
expected
Facility: BACKUP, Backup Utility
Explanation: One or more volumes and their exact order
were specified in the command line. The loaded volume is not the
expected volume according to the order specified in the command line.
User Action: Examine the volume labels and their order
as specified in the command line. The user or the operator must respond
to the prompt to specify what action to take to complete this backup
operation.
VOLSETALRMNT, another volume set of same label already mounted
Facility: MOUNT, Mount Utility
Explanation: Either a volume set with the specified
name is already mounted in the OpenVMS Cluster environment, or the
devices were mounted into the volume set in a different order on
another node.
User Action: If the same volume set is already mounted
on another node, ensure that devices are mounted into the volume set in
the same order. Otherwise, wait for the other volume set to be
dismounted. The name of a volume set cannot be changed once it is
established.
VOLSETSTS, change of status for volume set 'volume-set-name'
Facility: MOUNT, Mount Utility
Explanation: MOUNT encountered a condition that
resulted in a change of state for the specified volume set.
User Action: Take action based on the accompanying message.
VOLSHDWMEM, mounting a shadow set member volume; volume write locked
Facility: MOUNT, Mount Utility
Explanation: The volume being mounted is a former
shadow set member. To prevent accidental destruction of data, this
volume is being mounted write-locked.
User Action: None required. To allow write access to
this volume, dismount the volume and remount it with the
/OVERRIDE=SHADOW_MEMBERSHIP qualifier.
VOLSTATUS, change of status for volume 'volume-name'
Facility: MOUNT, Mount Utility
Explanation: MOUNT encountered a condition that
resulted in a change of state for the specified volume.
User Action: Take action based on the accompanying message.
VOLUSED, volume with label 'label' was already used in this save
operation
Facility: BACKUP, Backup Utility
Explanation: The command specifies that accidental
volume overwrite is to be avoided. The label on the loaded volume
matches a volume label previously written in this save operation.
User Action: Examine the volume labels and their order
specified in the command line. The user or the operator must respond to
the prompt to specify what action to take to complete this backup
operation.
![[OpenVMS documentation]](../../images/openvms_doc_banner_bottom.gif)