OpenVMS System Messages: Companion Guide for Help Message Users

Document revision date: 19 July 1999

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.

Cables have gone from CROSSED to UNCROSSED - REMOTE PORT 'xxx'
Facility: Cluster Port Driver
Explanation: A former crossed cable condition has been corrected.
User Action: None.

Cables have gone from UNCROSSED to CROSSED - REMOTE PORT 'xxx'
Facility: Cluster Port Driver
Explanation: A self-test loopback packet has detected a crossed cables condition or other software failure.
User Action: Check for crossed cable pairs. If none are found, contact a Digital support representative.

CANTASSIGN, Error assigning a channel to the PK device.

Facility: STACONFIG, Standalone Configure Process
Explanation: The $ASSIGN system service did not complete successfully.
User Action: Contact a Digital support representative.

CANTEXPREG, cannot expand virtual address space

Facility: BACKUP, Backup Utility
Explanation: Standalone BACKUP attempted unsuccessfully to expand its virtual address space.
User Action: If this error can be reliably reproduced, note the circumstances under which it occurs, including the BACKUP command used. Contact a Digital support representative.

CANTLOCK, cannot lock pages into memory; reboot if the system disk goes off line

Facility: BACKUP, Backup Utility
Explanation: Standalone BACKUP cannot lock the required pages into the working set.
User Action: Normally, no action is necessary. However, if the system disk goes off line, it will be necessary to reboot the system. The operation of standalone BACKUP is likely to be very slow because there is insufficient memory to lock down a small portion of the working set.

CAPTIVE, qualifier not allowed in captive accounts

Facility: LOGIN, Login Procedure
Explanation: An attempt was made to use qualifiers (for example, /CLI or /DISK) on a captive account that is logging in. If the account logging in is a captive account, no qualifiers may be used.
User Action: Retry without specifying qualifiers.

CBSNOTSUPTD, Attention - Phase I Shadowing is not supported as of OpenVMS VAX V6.1

Facility: MOUNT, Mount Utility
Facility: SYSBOOT, System Bootstrap Facility
Explanation: You specified a phase I volume shadowing virtual unit (DUSnn) in a command. OpenVMS VAX no longer supports phase I volume shadowing.
User Action: Reissue the command, using a phase II volume shadowing virtual unit name (DSAnn) consistent with phase II (host-based) volume shadowing.

CDROM_HS, 'volnam':'volsetnam' ('volnum' of 'volsetsiz'), 'text'

Facility: MOUNT, Mount Utility
Explanation: This message identifies a High Sierra formatted CD-ROM volume.
User Action: None.

CDROM_ISO, 'volnam':'volsetnam' ('volnum' of 'volsetsiz'), 'text'

Facility: MOUNT, Mount Utility
Explanation: This message identifies an ISO 9660 formatted CD-ROM volume.
User Action: None.

CEBREFNEG, negative reference count on shared memory CEB

CHMONIS, change mode instruction while on interrupt stack

CHMVEC, CHM vector bits <1:0> not 0

CI port timeout
Facility: Cluster Port Driver
Explanation: The port driver attempts to reinitialize the port; after 50 attempts, it marks the device off line.
User Action: Contact a Digital support representative to check the port hardware, the CI cable, and the node number configuration.

CIASHUTDOWN, breakin detection and evasion processing is shutting down

Facility: SECSRV, Security Server
Explanation: The break-in detection and evasion processing component of the security server is shutting down upon request.
User Action: None required. If you wish to restart the security server, issue the DCL command SET SERVER SECURITY/START.

CIASTARTINGUP, breakin detection and evasion processing now starting up

Facility: SECSRV, Security Server
Explanation: The break-in detection and evasion processing component of the security server is starting up, as requested.
User Action: None.

CIATERMINATED, an error caused breakin detection and evasion processing to terminate

Facility: SECSRV, Security Server
Explanation: An error occurred in the break-in detection and evasion processing component of the security server.
User Action: Contact a Digital support representative.

CIPORT, fatal error detected by CI port driver (PADRIVER)

CLIFAIL, error activating command interpreter 'CLI-name'

Facility: LOGIN, Login Procedure
Explanation: An error occurred while attempting to invoke the specified command interpreter for your process.
User Action: Ensure that the command interpreter image exists and that the image file has read access.

CLIPROT, error protecting command interpreter pages

Facility: LOGIN, Login Procedure
Explanation: An error occurred while attempting to protect the command interpreter pages.
User Action: Take action based on the accompanying message.

CLISYMTBL, error creating space for command interpreter symbol table

Facility: LOGIN, Login Procedure
Explanation: There is not enough virtual address space available to create the command interpreter symbol table.
User Action: Check that the system is set up with the value of VIRTUALPAGECNT large enough to allow the CLI to be mapped.

CLITBLFAIL, error activating command interpreter tables 'table-name'

Facility: LOGIN, Login Procedure
Explanation: LOGIN cannot access the specified command language interpreter tables.
User Action: Determine whether the specified tables exist and, if they do, make sure they are not protected against system read access.

CLITBLPROT, error protecting command interpreter tables pages

Facility: LOGIN, Login Procedure
Explanation: An error occurred when the system tried to write-protect the command interpreter table pages.
User Action: Try again. If the error recurs, report it to your system manager.

CLOSEIN, error closing 'file-name' as input

Facility: BACKUP, Backup Utility
Explanation: The Backup utility cannot close the specified input file for the reason stated in an accompanying RMS file system message.
User Action: Correct the error and retry the backup operation.

CLOSEOUT, error closing 'file-name' as output

Facility: BACKUP, Backup Utility
Explanation: The Backup utility cannot close the specified output file for the reason stated in an accompanying message.
User Action: Correct the error and retry the backup operation.

CLUEXIT, node voluntarily exiting VMScluster

Facility: BUGCHECK, System Bugcheck
Explanation: To avoid partitioning of the cluster, this system exited the cluster by crashing. Generally, this is a normal condition. If the condition persists, this processor may be configured incorrectly into two distinct OpenVMS Cluster systems. 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: Ensure that the cluster is properly configured.

CLUSTER, unsuitable cluster factor for 'device-name'

Facility: BACKUP, Backup Utility
Explanation: During an attempt to initialize an output volume, the Backup utility found that the cluster factor was too large or too small for the specified device.
User Action: If the input is a save set, use the BACKUP/LIST command to determine the volume initialization parameters of the input volumes. Refer to the description of the DCL command INITIALIZE, determine a suitable cluster factor, and initialize the output volumes using the INITIALIZE command. Then, reenter the command specifying the /NOINITIALIZE qualifier.

CMDERROR, error reported by command executor

Facility: LAT, LAT Facility
Explanation: The command executor module for LATCP cannot execute the command.
User Action: Take action based on the accompanying message.

CMDINPUT, error reading command input

Facility: LOGIN, Login Procedure
Explanation: An error occurred during the entry of the command; for example, the timeout period following the prompt for user name or password expired before a response was entered.
User Action: Repeat the login procedure.

CMDOBS, command obsolete - ignored

Facility: LAT, LAT Facility
Explanation: The specified LATCP command is obsolete; the command is ignored.
User Action: Discontinue use of this command.

CMDOBS, MSCP server must be loaded by setting SYSBOOT parameter MSCP_LOAD

Facility: SYSGEN, System Generation Utility
Explanation: The MSCP command in SYSGEN is now obsolete.
User Action: To load the MSCP server, set the SYSGEN parameter MSCP_LOAD. This will load the MSCP server during SYSBOOT.

Setting the SYSGEN parameter to load the MSCP server during SYSBOOT will result in a warning when you enter the MSCP command in SYSGEN. If this error is printed as the result of a startup command procedure, changing the parameter to load the server earlier will enable the old command procedure to complete successfully with only a warning message.

CMPOUTF11, /COMPARE requires save set as first input

Facility: BACKUP, Backup Utility
Explanation: In a compare operation between a save set and a disk volume, you must specify the save set as the first input and the disk volume as the second input.
User Action: Correct and reenter the command.

CNXMGRERR, error detected by VMScluster Connection Manager

COMPARED, compared 'file-spec'

Facility: BACKUP, Backup Utility
Explanation: The Backup utility successfully completed a compare operation. This message is displayed only when the /LOG command qualifier is used.
User Action: None.

CONFIGURED, Configured device 'device'

Facility: IOGEN
Explanation: The specified device has been configured.
User Action: None.

CONFQUAL, conflicting qualifiers, request aborted

Facility: SYSGEN, System Generation Utility
Explanation: You entered the SYSGEN command AUTOCONFIGURE with both the /EXCLUDE and /SELECT qualifiers.
User Action: Reenter the command, using only one of these qualifiers.

CONNERR, error connecting to 'terminal-name'

Facility: LOGIN, Login Procedure
Explanation: An error occurred when the system attempted to reconnect to the specified disconnected terminal.
User Action: Try again. If the error recurs, report it to your system manager.

CONSTERROR, security server experienced a CONSTRAINT_ERROR exception

Facility: SECSRV, Security Server
Explanation: An error occurred in the security server.
User Action: Contact a Digital support representative.

CONTINUE, unable to continue processing 'file-spec'

Facility: BACKUP, Backup Utility
Explanation: The specified file, which is being processed at a change of save-set volumes, is no longer accessible. The Backup utility terminates processing of the file. If other file activity is occurring on the volume, the error is probably caused because another user deleted the file during the backup process.
User Action: None; however, note that the file is incompletely processed.

CONTINUED, 'save-set-spec' contains a continued file - cannot append

Facility: BACKUP, Backup Utility
Explanation: In a save operation with the /NOREWIND qualifier, the specified volume contained a multivolume file that is continued on another volume; therefore, a file cannot be appended to the volume.
User Action: Retry the operation using the /REWIND qualifier to force the Backup utility to initialize the output volume or use another volume.

CONTRACT, contract virtual address space error

COPIED, copied 'file-spec'

Facility: BACKUP, Backup Utility
Explanation: The Backup utility successfully completed a save operation. This message is displayed only if the /LOG qualifier is specified.
User Action: None.

CORRUPTEMB, EMB packet header has been corrupted

Facility: BUGCHECK, System Bugcheck
Explanation: The system detected corruption of the system error log buffers. The system allocates space for error log entries from a set of common buffers. System software that makes use of the error logging routines typically writes into these entries. This message occurs when an attempt to write into an error log entry has overwritten other parts of the system error log buffers. The most common cause of this error is a coding error within a device driver.
User Action: Use the BACKUP command with the /IGNORE=NOBACKUP qualifier to make a backup save set of the system dump file generated by this error. Contact a Digital support representative and describe the conditions leading to the error.

COULDNTRESTART, security server cannot restart because of the following error:

Facility: SECSRV, Security Server
Explanation: The security server was directed to restart itself but the error reported in the accompanying message prevented this action.
User Action: Take action based on the accompanying message.

COULDNTSTART, security server cannot start functioning properly

Facility: SECSRV, Security Server
Explanation: The security server failed to start for the reason described in an accompanying message.
User Action: Take action based on the accompanying message.

CPU ucode not at required rev level for port activity
Facility: Cluster Port Driver
Explanation: The port driver will not attempt to start the port.
User Action: On a VAX-11/750 system, make sure that the console TU58 is present and up-to-date. Otherwise, contact a Digital support representative to check the port hardware.

CPUCEASED, CPU ceased execution

CPUNOTSUPP, The processor device on SCSI bus 'device-name',
ID 'slot-number', is not supported in a multihost SCSI VMScluster environment. The processor vendor ID is 'vendor-id' and the product ID is 'product-id'.

Facility: STACONFIG, Standalone Configure Process
Explanation: An unsupported processor device was discovered on the bus.
User Action: If you are operating in a multihost SCSI OpenVMS Cluster environment, remove the specified unsupported device.

If you are not operating in a multihost SCSI OpenVMS Cluster environment, specify the processor device using the SYSGEN parameter SCSICLUSTER_Pn=abcd, where:

n = 1, 2, 3, or 4
ab = The first two letters of the processor's vendor ID
cd = The first two letters of the processor's product ID

CREATED, created 'file-name'

Facility: BACKUP, Backup Utility
Explanation: This informational message appears for every file that is created when the /LOG qualifier is used in the BACKUP command for a restore or copy operation.
User Action: None.

CREDIR, created directory 'directory-name'

Facility: BACKUP, Backup Utility
Explanation: The Backup utility successfully created the directory 'directory'. This message is displayed only if the /LOG qualifier is specified.
User Action: None.

CREDIRERR, error creating directory 'directory-name'

Facility: BACKUP, Backup Utility
Explanation: The Backup utility encountered an error during an attempt to create the specified directory.
User Action: Take action based on the accompanying message.

CRELNM_FAILED, failed to create logical name 'name' in table 'table-name'

Facility: MOUNT, Mount Utility
Explanation: The mount operation completed successfully, but the Mount utility could not create the requested logical name. An accompanying message explains the reason for the failure.
User Action: None required. If you wish, you can manually assign the logical name after the reason for the failure has been resolved.

CREPARFIL, unable to create parameter file

Facility: SYSGEN, System Generation Utility
Explanation: An error occurred during a write operation.
User Action: Reenter the command so that you can write to the file.

CREPRCFL, Could not create new process

Facility: BACKUP, Backup Utility
Explanation: Standalone BACKUP cannot create the process necessary to perform the requested additional backup operation.
User Action: Reboot the system with standalone BACKUP in order to perform further backup operations.

Datagram Free Queue Insert Failure
Facility: Cluster Port Driver
Explanation: The port driver attempts to reinitialize the port; after 50 failed attempts, it marks the device off line. This error is caused by a failure to obtain access to an interlocked queue. Possible sources of the problem are CI hardware failures or memory, SBI (VAX-11/780), CMI (VAX-11/750), BI, PCI, or XMI contention.
User Action: Contact a Digital support representative.

Datagram Free Queue Remove Failure
Facility: Cluster Port Driver
Explanation: The port driver attempts to reinitialize the port; after 50 failed attempts, it marks the device off line. This error is caused by a failure to obtain access to an interlocked queue. Possible sources of the problem are CI hardware failures or memory, SBI (VAX-11/780), CMI (VAX-11/750), BI, PCI, or XMI contention.
User Action: Contact a Digital support representative.

DBLERR, double error halt restart

Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an irrecoverable hardware error. Because of the severity of the error, further operation is impossible or it could corrupt user data. 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: Thoroughly test all system hardware components. If no hardware errors are located and if the problem persists, note the conditions at the time of the error. 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.

DEADLOCK, deadlock detected

Facility: MOUNT, Mount Utility
Explanation: The first 12 characters of an ISO 9660 CD-ROM's volume name and volume set name are the same. When an attempt is made to mount the volume, both names are used to construct an OpenVMS lock request to manage volumes within a volume set. However, if the first 12 characters of the names match, the lock request fails.
User Action: Mount the volume specifying a different volume set name.

DECPTREF, decrement page table reference count error

DEFCLI, you are not authorized to specify CLI parameters

Facility: LOGIN, Login Procedure
Explanation: Authorization is needed to specify an alternate command language interpreter (CLI) or alternate CLI tables.
User Action: Log in again without specifying the /CLI or /TABLES qualifiers after your user name.

DELCONPFN, fatal error in delete contents of PFN

DELETE, error deleting 'file-name' file ID ('numeric-string')

Facility: BACKUP, Backup Utility
Explanation: An error is encountered during an attempt to delete the file with the specified file identification in response to the /DELETE qualifier. The accompanying message provides additional information.
User Action: None.

DELETESWL, 'device-name' is write protected - file deletion pass not executed

Facility: BACKUP, Backup Utility
Explanation: The input device is software write locked. The Backup utility cannot perform the file deletion pass.
User Action: Dismount the input device, remount it writable, and either delete the files by hand or reenter the BACKUP command.

DELGBLSEC, delete global section error

DELGBLWCB, delete global section window error

DELPORT, deleted port 'port-name'

Facility: LAT, LAT Facility
Explanation: The specified port has been deleted by LATCP.
User Action: None.

DELSERVICE, deleted service 'service-name'

Facility: LAT, LAT Facility
Explanation: The specified service has been deleted by LATCP.
User Action: None.

DELWSLEX, delete working set list entry index error

DENIGNORED, /DENSITY qualifier not appropriate to this device; ignored

Facility: MOUNT, Mount Utility
Explanation: The /DENSITY qualifier was supplied on the command line for a device that does not support various densities. The qualifier is ignored.
User Action: Omit the /DENSITY qualifier to avoid getting this system message. Use the /MEDIA_FORMAT=[NO]COMPACTION qualifier if the device supports compaction.

DENSITY, 'saveset-spec' does not support specified density - default used

Facility: BACKUP, Backup Utility
Explanation: The specified tape hardware does not support the density selected by the /DENSITY qualifier. The Backup utility uses the default density.
User Action: Use a different tape device, or specify a different density.

DEQSUBLCKS, tried to dequeue lock with sublocks

DETSHADINCON, mount has detected an inconsistent state for shadowing

Facility: MOUNT, Mount Utility
Explanation: MOUNT has detected an internal inconsistency while attempting to mount a shadow set. This message indicates a failure in either MOUNT or the OpenVMS Volume Shadowing software.
User Action: Contact a Digital support representative and provide as much detail as possible about the circumstances surrounding this error.

DEVBUSY, mount or dismount in progress on device

Facility: MOUNT, Mount Utility
Explanation: A mount or dismount operation is currently in progress on the device, possibly on another node in the cluster. If the condition persists, the other mount may be waiting for an operator request to complete, or the device may be malfunctioning.
User Action: Determine where the mount or dismount is in progress and rectify the problem that is holding it up.

DEVCOUNT, number of devices must match number of volumes

Facility: MOUNT, Mount Utility
Explanation: The number of devices specified in the DCL command MOUNT to mount a disk volume set does not match the number of volume labels specified in the command.
User Action: Verify the names of the devices and volume labels for the command and then reenter the command with a matching number of devices and volume labels.

DEVDMT, device is marked for dismount

Facility: MOUNT, Mount Utility
Explanation: The device is in the process of being dismounted. No mount requests can be processed on this device until the dismount completes. If this condition persists, files are open on the device.
User Action: Close any open files on the device. If other processes have open files, the system manager may need to resolve the situation.

DEVICES, only one device allowed

Facility: MOUNT, Mount Utility
Explanation: More than one device was specified in the DCL command MOUNT. Only one volume at a time can be mounted for this specified type of mount.
User Action: Reenter the DCL command MOUNT, specifying only one device.

DEVNOFE, device does not support FORCED ERROR handling. To override use the /OVERRIDE=NO_FORCED_ERROR qualifier

Facility: MOUNT, Mount Utility
Explanation: The device being mounted into a shadow set does not support forced error handling and the /OVERRIDE=NO_FORCED_ERROR qualifier was not specified.
User Action: Specify the /OVERRIDE=NO_FORCED_ERROR qualifier and retry the operation.

DEVNOTKNWN, device not known: 'input'

Facility: SYSGEN, System Generation Utility
Explanation: The specific device is unknown.
User Action: See the OpenVMS VAX Device Support Manual for the correct UNIBUS controller name.

DEVSHAMEM, device is already mounted as a shadow set member

Facility: MOUNT, Mount Utility
Explanation: The device you attempted to mount as a nonshadowed device is already mounted elsewhere in the cluster as a shadow set member.
User Action: Mount the device as a member of a shadow set. You can use DSA: to specify a generic virtual unit if you do not know which virtual unit contains the device.

DIAGPACK, 'disk' is a diagnostic pack

Facility: BACKUP, Backup Utility
Explanation: Either a Backup utility operation attempted to use a volume identified as a diagnostic volume, or the INITIALIZE command was used to initialize a diagnostic volume. In either case, the volume cannot be used.
User Action: Retry the operation using another volume.

DIFVOLMNT, different volume already mounted on this device

Facility: MOUNT, Mount Utility
Explanation: Previously, a different volume was mounted on this device on another node in the cluster. The device may be in mount verification on the other node. Either the original volume was removed from the device and replaced with another, or its volume identification was overwritten.
User Action: Restore the previously mounted volume to the device. If this is not possible, dismount the device on all nodes that currently have it mounted. Then retry the mount operation.

DIRENTRY, ACP failed to find same directory entry

DISKCLASS, fatal error detected by Disk Class driver (DUDRIVER)

DISKFRAG, free space on 'device-name' is too fragmented

Facility: BACKUP, Backup Utility
Explanation: The number of free extents on the specified volume is unreasonably large. The volume cannot be used as a save-set disk.
User Action: Reinitialize the volume, or select another volume and retry the operation.

DISMAL, all of the volumes have been dismounted

Facility: MOUNT, Mount Utility
Explanation: All of the volumes mounted by this invocation of $MOUNT or the MOUNT command have been dismounted because of errors that were detected after the volumes were mounted.
User Action: Take the action based on the preceding messages, and reenter the MOUNT command.

DISMOUNTD, volume 'volume-name' of volume-set 'volume-set-name' dismounted

Facility: MOUNT, Mount Utility
Explanation: The specified volume of the specified volume set has been dismounted because of errors encountered in processing the volume after it is mounted. An error with part of a volume set causes the entire volume set to be dismounted. This message appears for each member of the volume set that is dismounted due to the error condition. Only those volumes that were mounted by this invocation of the MOUNT command are listed. If the volume set name is not available, the string "name n/a" appears as the name of the volume set.
User Action: Take action based on the accompanying message and reenter the MOUNT command.

DISMPART, some of the volumes have been dismounted

Facility: MOUNT, Mount Utility
Explanation: Some of the volumes that were mounted by this invocation of the Mount utility or the MOUNT command have been dismounted due to errors detected after the volumes were mounted.
User Action: Take action based on the preceding messages, and reenter the MOUNT command.

DISRECONNECT, you are not authorized to do reconnections

Facility: LOGIN, Login Procedure
Explanation: Authorization is needed to reconnect to disconnected processes.
User Action: Log in again without specifying the /CONNECT qualifier after your user name.

DISUSER, account is disabled

Facility: LOGIN, Login Procedure
Explanation: An attempt is made to log in to an account when the account is disabled. An account's system access can be restricted by setting the DISUSER flag in the user authorization file. This message is written to the system accounting and security audit records; the NOTVALID message displays to the user.
User Action: None.

DOUBLDALOC, double deallocation of swap file space

DOUBLDEALO, double deallocation of memory block

DRIVENAM, driver name is 'driver-name'

Facility: SYSGEN, System Generation Utility
Explanation: This message is issued with the message SYSVERDIF to identify the driver.
User Action: See the SYSGEN message SYSVERDIF for user action information.

DRVERR, fatal drive error

Facility: MOUNT, Mount Utility
Explanation: In a SCSI OpenVMS Cluster environment, a request has been made to mount a device on a shared SCSI bus and the device does not support SCSI-2 tagged command queuing (TCQ).
User Action: If you want to mount a device on a shared SCSI bus, the device must support TCQ.

DSSI Terminator Power failure, possible blown fuse.
Facility: Cluster Port Driver
Explanation: The adapter has detected a hardware problem.
User Action: Check the terminator fuse. If it is blown, replace it or contact a Digital support representative to check the DSSI hardware.

DUALLOC, dual allocation on volume 'n'

Facility: RBLD, REBUILD Command (Mount Utility)
Explanation: A logical block on the specified relative volume is allocated to more than one file.
User Action: Execute the DCL command ANALYZE/DISK_STRUCTURE/NOREPAIR for the volume. This command invokes the Analyze/Disk_Structure utility, which issues a message for each case of dual file allocation. Each message identifies the file name, the range of logical block numbers that are allocated, and the virtual block numbers that map to the logical blocks.

After you determine the files involved in each case of dual allocation, disallow any other file activity for them and copy all but one file to a new version. Then delete the versions containing dual allocation. This causes blocks that are not actually free to be marked as free blocks in the storage bit map.

Finally, reexecute the ANALYZE/DISK_STRUCTURE/REPAIR command. Then examine each file and reconstruct from backup media any files that have been corrupted.

Dump aborted, page tables may be corrupted
Facility: BUGCHECK, System Bugcheck
Explanation: When writing a selective dump (SYSGEN parameter DUMPSTYLE set to 1), the OpenVMS operating system relies heavily on the integrity of the various system and process page tables. This message indicates that the system might have detected corruption in these page tables, and it will abort further dumping. You might not be able to analyze the dump.
User Action: Contact a Digital support representative.

DUPDEVSPC, duplicate device specified

Facility: MOUNT, Mount Utility
Explanation: The same tape device is specified more than once in a list of tape devices for the DCL command MOUNT.
User Action: Reenter the MOUNT command, specifying each device only once.

DUPLABEL, duplicate label 'label' not allowed with /EXACT_ORDER qualifier

Facility: BACKUP, Backup Utility
Explanation: Duplicate labels cannot be specified with the /EXACT_ORDER qualifier. The specified label matches a label that was entered previously.
User Action: Reenter the command, specifying unique labels.

DUPOPT, previously specified callable interface option type invalid, argument position 'position', option type = 'option-type'

Facility: BACKUP, Backup Utility
Explanation: An option type is specified more than once in the set of options. It is illegal to specify duplicates for this option type.
User Action: Note the value of the option type found and its relative position in the set of options specified to the BACKUP API; then remove redundant specifications of this option type. (Refer to the BACKUP documentation and the BACKUP API definitions files for valid option values.)

DUPRVN, duplicate volume number already mounted

Facility: MOUNT, Mount Utility
Explanation: A volume of the same relative volume number and the same volume set name is already mounted. An attempt is being made to mount a volume that belongs to a volume set with the same name as a volume set that is already mounted.
User Action: Make sure that the correct volume has been mounted. Verify that the volume status (/SHARE, /NOSHARE, /GROUP, or /SYSTEM) is defined consistently with volumes already mounted.

DUPVOLNAM, volume label already present in set

Facility: MOUNT, Mount Utility
Explanation: During an attempt to add a volume to an existing volume set, the specified volume set is found to contain a volume with the label specified.
User Action: Verify the labels on the existing volumes in the set. Choose a new label for the volume you are adding to the set, reinitialize the volume, and reenter the DCL command MOUNT/BIND.

DZRO_ISD, image contains demand zero sections

Facility: LOADER, Executive Image Loader
Explanation: A load request was made for an executive image that illegally contains demand zero sections.
User Action: Correct the link procedure used to build the executive image; specify the appropriate PSECT_ATTR and COLLECT statements to eliminate the demand zero sections.

Contents

Index

privacy and legal statement

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.