OpenVMS System Messages: Companion Guide for Help Message Users

Updated: 11 December 1998

OpenVMS System Messages: Companion Guide for Help Message Users

Contents

Index

BADACP, invalid syntax on /PROCESSOR qualifier

Facility: MOUNT, Mount Utility
Explanation: The keyword or file specification value specified for the /PROCESSOR qualifier is not specified correctly.
User Action: Reenter the command; refer to the OpenVMS DCL Dictionary for the correct syntax.

BADALORQSZ, bad memory allocation request size

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.

BADBLKSIZE, 'save-set-spec' has inconsistent block size

Facility: BACKUP, Backup Utility
Explanation: The volume mounted as a continuation volume of a multivolume save set is not recorded with the same block size as previous volumes of the save set. This volume is probably not part of the same save set.
User Action: Locate and mount the correct continuation volume.

BADBLOCK, bad blocks on 'device-name' do not match input

Facility: BACKUP, Backup Utility
Explanation: In a copy or restore operation with the /PHYSICAL qualifier, a bad block is present on the output volume in a location where the input volume had a good block. The backup operation will not result in a valid Files--11 volume.
User Action: Reevaluate the operation; another mode of operation, such as the /IMAGE qualifier, may be appropriate. Or retry the operation using either the original input volume or an error-free output volume.

BADBOOTCB, corrupted Boot Control Block

BADBUFADR, ACP buffer address out of range of buffer pool

BADBUFTYP, bad ACP buffer type code

BADCACHE, invalid syntax on /CACHE qualifier

Facility: MOUNT, Mount Utility
Explanation: At least one option specified with the /CACHE qualifier contains an invalid syntax.
User Action: Correct the command and reenter it. The /CACHE qualifier must include one or more keywords and values enclosed in parentheses, as shown here:

/CACHE=(keyword[,keyword,...])

Possible keywords are the following:

EXTENT= n Enables extent caching, where n is the number of entries in the extent cache.

NOEXTENT Disables extent caching.

FILE_ID= n Enables file identification caching, where n is the number of entries and must be greater than 1.

NOFILE_ID Disables file identification caching.

LIMIT= n Specifies the maximum amount of free space in the extent cache, where n is the number of one-thousandths of the currently available free space on the disk.

QUOTA= n Enables quota caching, where n is the number of entries in the quota cache.

NOQUOTA Disables quota caching.

TAPE_DATA Enables write caching for a magnetic tape device.

WRITETHROUGH Disables writeback caching.

See the MOUNT documentation or Help for more information about these keywords and their values.

BADCHKSUM, shared memory data structures corrupted - reinitialization necessary

Facility: SYSGEN, System Generation Utility
Explanation: A CRC check of the constant fields in the shared memory data page has detected an error.
User Action: Reboot all processors using the shared memory.

BADDALRQSZ, bad memory deallocation request size or address

BADDATA, error in block 'nn' of 'file-spec' detected during save

Facility: BACKUP, Backup Utility
Explanation: A read error for the specified block of the specified file occurred when the save set was created. Data in this block may be corrupt.
User Action: Examine the file for corruption and reconstruct it 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.

BADDATCHK, invalid keyword on /DATACHECK qualifier

Facility: MOUNT, Mount Utility
Explanation: The keyword specified for the /DATACHECK qualifier must be either READ or WRITE.
User Action: Correct and reenter the command.

BADDAY, you are not authorized to login today

Facility: LOGIN, Login Procedure
Explanation: There are restrictions from the class of login that you are attempting. The system manager can restrict user use of a login class on specific days.
User Action: If possible, try a different login class. For example, if you are restricted from BATCH logins today, try an interactive class (LOCAL, REMOTE, or DIALUP). If you are restricted from all classes of logins today, you cannot log in until you are permitted to use the system. You may also want to ask your system manager about the login restrictions for your account.

BADDENS, unknown value on /DENSITY qualifier

Facility: MOUNT, Mount Utility
Explanation: The value specified for a tape density must be 800, 1600, or 6250; the value specified for a diskette must be SINGLE or DOUBLE.
User Action: Correct and reenter the command.

BADDIR, directory 'directory' has invalid format

Facility: BACKUP, Backup Utility
Explanation: The specified directory file is not in the expected format for a directory file. The file is corrupt.
User Action: Use the DCL command SET FILE/NODIRECTORY to delete the corrupt directory file, then use the DCL command ANALYZE/DISK_STRUCTURE/REPAIR to place the lost files in the [SYSLOST] directory. The lost files can then be copied to a new directory.

BADFID, ACP file number out of range for this volume

BADFILE, invalid filename is 'file-name'

Facility: STDRV, System Startup Driver
Explanation: The startup component file name is invalid.
User Action: Use the STARTUP MODIFY FILE command at the SYSMAN> prompt to correct the file name.

BADFLAG, bad enable/disable flag 'flag'

Facility: STDRV, System Startup Driver
Explanation: The enable/disable flag describing how the list of nodes associated with a startup component file should be used is invalid.
User Action: Use the SYSMAN command STARTUP ENABLE/DISABLE to modify this entry in the startup component file.

BADFORKIPL, bad FORK exit interrupt priority level

BAD_GSD, an inconsistency was detected while traversing the GST

Facility: LOADER, Executive Image Loader
Explanation: An executive image was loaded containing a global symbol that is not vectored through either the SYS$BASE_IMAGE or the SYS$PUBLIC_VECTORS image.
User Action: Use either /NOSYSSHR or /NOSYSLIB to correct the link procedure to exclude any shareable image other than SYS$BASE_IMAGE or SYS$PUBLIC_VECTORS.

BADHOMBLK, bad home block encountered on volume

Facility: MOUNT, Mount Utility
Explanation: An I/O error occurred while reading a home block during /BIND processing. The first occurrence of this message is a warning; the second is fatal.
User Action: Repair using the Analyze/Disk_Structure utility, or reinitialize the volume and retry the operation.

BADHOUR, you are not authorized to login at this time

Facility: LOGIN, Login Procedure
Explanation: Currently, there are restrictions from the class of login you are attempting. The login classes are: LOCAL, DIALUP, REMOTE, NETWORK, and BATCH. The system manager can restrict use of each login class at specific times.
User Action: If possible, try a different login class. For example, if you are currently restricted from BATCH logins, try an interactive class (LOCAL, REMOTE, or DIALUP). If you are currently restricted from all login classes, you cannot log in until you are permitted to use the system. You may also want to ask your system manager about the login restrictions for your account.

BADIMGOFF, image offset not within any image section

Facility: LOADER, Executive Image Loader
Explanation: During an image load request, a relocation or fixup operation was attempted on an image offset that has no resultant address within the image.
User Action: Disable executive slicing by specifying the LDR$V_NO_SLICE option or by using the LOAD_SYS_IMAGES system parameter. Correct the bad references in the source code.

BADINIT, unknown keyword on /INITIALIZE qualifier

Facility: MOUNT, Mount Utility
Explanation: An invalid keyword is specified with the /INITIALIZE qualifier.
User Action: Correct and reenter the command.

BADLCKWSLE, bad locked working set list entry, not a page table

BADMCKCOD, bad machine check code

BADMDFMT, invalid syntax on /MEDIA_FORMAT qualifier

Facility: MOUNT, Mount Utility
Explanation: The syntax of the /MEDIA_FORMAT qualifier is invalid.
User Action: Correct the command and reenter it. The /MEDIA_FORMAT qualifier can have one of three values: COMPACTION or NOCOMPACTION for tape media, or CDROM for disk media.

BADMODE, invalid mode 'mode' for file 'file-name'

Facility: STDRV, System Startup Driver
Explanation: A file in the startup component database has an execution mode that is not DIRECT, BATCH, CALLED, SPAWN, or ANY.
User Action: To correct the component execution mode, use the STARTUP MODIFY FILE command at the SYSMAN> prompt.

BADOPTDSC, invalid callable interface option descriptor, argument position 'position', option type = 'option-type', descriptor = 'descriptor' 'descriptor'

Facility: BACKUP, Backup Utility
Explanation: An invalid or zero-length string descriptor was specified for an option value.
User Action: Note the values found and their relative position in the set of options specified to the BACKUP API; then correct the string descriptor specification.

BADOPTTYP, invalid callable interface option type, argument position 'position', option type = 'option-type'

Facility: BACKUP, Backup Utility
Explanation: An invalid option type was detected in the set of options.
User Action: Note the option type value found and its relative position in the set of options specified to the BACKUP API; then correct the type of option specified. (Refer to the BACKUP API definitions files for valid option type values.)

BADOPTVAL, invalid callable interface option value, argument position 'position', option type = 'option-type', option value = 'option-value'

Facility: BACKUP, Backup Utility
Explanation: An invalid option value was detected in the set of options.
User Action: Note the option value found and its relative position in the set of options specified to the BACKUP API; then correct the specified option value. (Refer to the BACKUP documentation and the BACKUP API definitions files for valid option values.)

BADOPTVALQ, invalid callable interface option value, argument position 'position', option type = 'option-type', option value = 'option-value' 'option-value'

Facility: BACKUP, Backup Utility
Explanation: An invalid option quadword value was detected in the set of options.
User Action: Note the option value found and its relative position in the set of options specified to the BACKUP API; then correct the specified option value. (Refer to the BACKUP documentation and the BACKUP API definitions files for valid option values.)

BADOVR, unknown keyword on /OVERRIDE qualifier

Facility: MOUNT, Mount Utility
Explanation: The command syntax for the /OVERRIDE qualifier is invalid.
User Action: Enter the DCL command HELP or refer to the OpenVMS DCL Dictionary for the legal keywords, then enter the corrected command.

BADPAGFILA, bad page file address allocated

BADPAGFILD, bad page file address deallocated

BADPAGTYPE, bad page type

BADPARAM, insufficient shared memory to create specified data structures

Facility: SYSGEN, System Generation Utility
Explanation: The sum of all the data structures specified is more than the available amount of shared memory.
User Action: Recalculate memory usage and reenter the command.

BADPRO, invalid syntax on /PROTECTION qualifier

Facility: MOUNT, Mount Utility
Explanation: The command syntax for the /PROTECTION qualifier is incorrect.
User Action: Enter the DCL command HELP SPECIFY PROTECTION or refer to the OpenVMS DCL Dictionary for the correct syntax, then enter the corrected command.

BADQHDR, interlocked queue header corrupted

BADQUAL, qualifier '/qualifier' is inconsistent with the operation type

Facility: BACKUP, Backup Utility
Explanation: The specified qualifier cannot be used with the type of Backup operation indicated by the BACKUP command.
User Action: Reenter the BACKUP command without the specified qualifier or select a different operation type. For more information on how qualifiers affect the BACKUP command, see the OpenVMS System Management Utilities Reference Manual.

BADREFCNT, faulty reference count maintenance

Facility: LOADER, Executive Image Loader
Explanation: A call was made to the SYS$REMOVE_REF system service and the outstanding reference count for the image is negative.
User Action: Check all references to the routines in the executive image to ensure that each SYS$MAKE_REF has only one associated SYS$REMOVE_REF.

BADREPLY, invalid operator reply message

Facility: MOUNT, Mount Utility
Explanation: The operator response to an operator mount request contained an invalid qualifier or reply text.
User Action: The operator must reply to the mount request with one of the following qualifiers:

/ABORT=identification-number
/PENDING=identification-number
/TO=identification-number
If /TO is used, the operator can redirect the mount to a different device by specifying SUBSTITUTE in the reply text, as follows:
REPLY/TO=identification-number "SUBSTITUTE device-name"

BADREPLY, unknown type of operator reply; reply is 'message-type' 'message-status' 'reply-id' 'message-text'

Facility: BACKUP, Backup Utility
Explanation: The operator's reply is an unknown type and cannot be processed.
User Action: See the operator or your system manager to determine the problem.

BADRSEIPL, bad IPL at entrance to report schedule event

BADRVNWCB, inconsistent RVN in window map pointer

BADSBMBLK, ACP tried to reference off end of bitmap

BADSECSYS, failed to create or access SECURITY.SYS

Facility: MOUNT, Mount Utility
Explanation: The Mount utility was unable to create and write the SECURITY.SYS file on a volume that was initialized prior to OpenVMS Version 6.0, usually because the device is full.
User Action: Try any of the following actions:

Mount the device using the /NOWRITE qualifier.
Mount the device with /OVERRIDE=SECURITY if the security policy of the system permits this. Once the disk is mounted, free up approximately 10 blocks on the disk, and then remount the disk without using the /OVERRIDE=SECURITY qualifier.
Mount the device on a version of OpenVMS prior to Version 6.0 and free up about 10 blocks on the disk. Then remount the disk on the later version of the system.

BADSETAFF, attempt to set process affinity to primary cpu failed

Facility: SYSGEN, System Generation Utility
Explanation: SYSGEN cannot set process affinity to the primary CPU.
User Action: Contact a DIGITAL support representative.

BADSETCNT, incorrect number of devices in output specification

Facility: BACKUP, Backup Utility
Explanation: The output specification for a copy, restore, or compare operation with the /IMAGE qualifier must be a list containing the same number of devices as the number of volumes in the input volume set.
User Action: If the input is a save set, use the DCL command BACKUP/LIST to determine how the save set was created; reenter the command.

BADSHADOW, invalid syntax on /SHADOW qualifier

Facility: MOUNT, Mount Utility
Explanation: The MOUNT command contains invalid shadow set syntax.
User Action: Correct the syntax and reenter the command, or correct the program that caused the error.

BADSWPVBN, swap VBN specified for non-process page

BADTYPE, invalid file type in file 'file-name'

Facility: STDRV, System Startup Driver
Explanation: A startup component file in the startup component database has a file type that is not .COM or .EXE.
User Action: Use the SYSMAN command STARTUP MODIFY FILE to correct the file name.

BADUIC, invalid UIC syntax

Facility: MOUNT, Mount Utility
Explanation: The command contains an invalid UIC. The group and member portions of a UIC must both be specified and be separated by a comma, or a valid rights identifier must be specified.
User Action: Enter the DCL command HELP or refer to the OpenVMS DCL Dictionary for the correct syntax, then enter the corrected command.

BADUNDFAT, invalid keyword on /UNDEFINED_FAT qualifier

Facility: MOUNT, Mount Utility
Explanation: The MOUNT command specified an invalid keyword with the /UNDEFINED_FAT qualifier.
User Action: Select a correct combination of keywords from the following categories.

Record format keywords:

FIXED:record-attributes...,record-size
VARIABLE:record-attributes...
STREAM:record-size
STREAM_LF:record-size
STREAM_CR:record-size
LSB_VARIABLE:record-attributes...

Record attribute keywords:

NONE (None)
CR (Carriage_return)
FTN (Fortran)
PRN (Print)
NOBKS (No-Block-Span)

Record size attribute: a decimal number from 1 to 32767

For more information about selecting keywords, refer to the OpenVMS System Management Utilities Reference Manual.

BADVOL1, bad VOL1 ANSI label

Facility: MOUNT, Mount Utility
Explanation: The protection encoded on a magnetic tape volume label is invalid or the label itself is invalid; the magnetic tape ACP cannot process the tape. Or, the tape is defective; it is not an ANSI-labeled tape, or the hardware device is not reading the tape properly.
User Action: Verify the tape volume. If necessary, mount the tape as a foreign volume and try to read it.

BADWCBPT, bad WCB pointer in IRP

BATCHNOOPR, no operator available to service batch request

Facility: MOUNT, Mount Utility
Explanation: The MOUNT request has been aborted because the batch job requires operator assistance and no operator is present.
User Action: Either locate an operator or correct the condition that requires operator intervention. Then resubmit the batch job.

BDNOMBREX, boot device is not a member of existing shadow set

Facility: SHADOW, Volume Shadowing Software
Explanation: The boot device is not a member of the existing system disk shadow set recorded in the boot device storage control block.
User Action: Reboot the system using one of the other existing system disk shadow set members.

BDPPURGERR, buffered datapath purge incomplete

BIIC failure - BICSR/BER/CNF 'xxxxxxxx/xxxxxxxx/xxxxxxxx'
Facility: Cluster Port Driver
Explanation: The port driver attempts to reinitialize the port; after 50 failed attempts it marks the device off line.
User Action: Contact a DIGITAL support representative to check the port hardware.

BITMAPERR, I/O error on storage bitmap; volume locked

Facility: MOUNT, Mount Utility
Explanation: An I/O error was encountered during a mount operation. Existing files on the volume can be accessed, but other operations (for example, create and delete) are not possible.
User Action: Either repair the volume using the Analyze/Disk_Structure utility or copy the volume using the Backup utility.

BITMAPERR, I/O error reading index file bitmap on relative volume 'volume-id'

Facility: RBLD, REBUILD Command (Mount Utility)
Explanation: The rebuild operation encountered an error while reading the index file on the specified volume.
User Action: Take action based on the accompanying message.

BITMAPINV, storage bitmap is invalid, volume locked

Facility: MOUNT, Mount Utility
Explanation: The volume's storage bitmap contains invalid data.
User Action: Use the Analyze/Disk_Structure utility to repair the bitmap.

BLKZERO, block 0 of 'device-name' is bad - volume not bootable

Facility: BACKUP, Backup Utility
Explanation: The boot block of the specified volume is not usable.
User Action: None. However, the volume probably cannot be used as a system volume for a VAX-11 processor model that requires access to the boot block during a bootstrap operation.

BLOCKCRC, software block CRC error

Facility: BACKUP, Backup Utility
Explanation: An incorrect value occurred in the block CRC field of a save-set block. Data in the save set is corrupt.
User Action: None. Save-set data has been lost.

BLOCKLOST, block of 'file-spec' lost due to unrecoverable error

Facility: BACKUP, Backup Utility
Explanation: The Backup utility encountered an irrecoverable error in reading the specified save set and cannot correct the error using the redundancy information.
User Action: None. Save-set data has been lost.

BOOT-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.

BOOT-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.

BOOT-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.

BOOT-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.

BOOT-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.

BOOT-F-Unexpected exception
Facility: VMB, Virtual Memory Boot
Explanation: An unexpected exception occurred while the primary bootstrap (VMB.EXE) was executing. This condition may indicate a corrupt SYSBOOT.EXE file or 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.

BOOT-F-Unexpected machine check
Facility: VMB, Virtual Memory Boot
Explanation: An unexpected machine check occurred while the primary bootstrap (VMB.EXE) was executing. This condition may indicate a corrupt SYSBOOT.EXE file or 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.

BRDMSGLOST, broadcast queue pointer has no related entry

BUFFERSLOST, all buffers are lost

Facility: BACKUP, Backup Utility
Explanation: A software error occurred in the Backup utility.
User Action: Contact a DIGITAL support representative.

BUFFQUAL, /BUFFER_COUNT qualifier obsolete - ignored

Facility: BACKUP, Backup Utility
Explanation: The Backup utility is ignoring the /BUFFER_COUNT qualifier, which is no longer valid with the BACKUP command. The backup operation proceeds as usual.
User Action: Do not specify the /BUFFER_COUNT qualifier with the BACKUP command.

BVP failure - Status/Error/Data 'xxxxxxxx/xxxxxxxx/xxxxxxxx'
Facility: Cluster Port Driver
Explanation: The port driver attempts to reinitialize the port; after 50 failed attempts, it marks the device off line.
User Action: Contact a DIGITAL support representative to check the port hardware.

BVP timeout. - Status/Error/Data 'xxxxxxxx/xxxxxxxx/xxxxxxxx'
Facility: Cluster Port Driver
Explanation: The port driver attempts to reinitialize the port; after 50 failed attempts, it marks the device off line.
User Action: Contact a DIGITAL support representative to check the port hardware.

Contents

Index

Legal

 
6023PRO_004.HTML

EXTENT= n	Enables extent caching, where n is the number of entries in the extent cache.
NOEXTENT	Disables extent caching.
FILE_ID= n	Enables file identification caching, where n is the number of entries and must be greater than 1.
NOFILE_ID	Disables file identification caching.
LIMIT= n	Specifies the maximum amount of free space in the extent cache, where n is the number of one-thousandths of the currently available free space on the disk.
QUOTA= n	Enables quota caching, where n is the number of entries in the quota cache.
NOQUOTA	Disables quota caching.
TAPE_DATA	Enables write caching for a magnetic tape device.
WRITETHROUGH	Disables writeback caching.