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

ICONCLUDAT, inconsistent cluster data base

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.

ICONPFNDAT, inconsistent PFN data base

ICPAGELOC, inconsistent page location

IDENT, Standalone BACKUP 'string'; the date is 'date and time'

Facility: BACKUP, Backup Utility
Explanation: This is a standalone backup identification message.
User Action: Make sure that the displayed data is correct.

IDXHDRBAD, index file header is bad; backup used

Facility: MOUNT, Mount Utility
Explanation: The primary index file header is corrupt or unreadable; the backup volume is used to mount the volume.
User Action: Repair the volume using the ANALYZE/DISK_STRUCTURE/REPAIR command.

IDXMAPERR, I/O error on index file bitmap; volume locked

Facility: MOUNT, Mount Utility
Explanation: An I/O error was encountered during a mount operation. Existing files in the volume can be accessed, but other operations (for example, create and delete) are not possible.
User Action: Repair the volume with the ANALYZE/DISK_STRUCTURE/REPAIR command.

IFREPAGCNT, inconsistent free page count

ILLANSIBS, ANSI magnetic tape block size must be at least 18 characters

Facility: MOUNT, Mount Utility
Explanation: The block size specified for a magnetic tape is smaller than the minimum of 18 bytes required by the ANSI/ISO tape standard.
User Action: Correct the command and reenter it.

ILLEVTNUM, illegal event number

ILLOPT, qualifier(s) not appropriate to this device

Facility: MOUNT, Mount Utility
Explanation: A MOUNT or INITIALIZE command specifies qualifiers that do not apply to this device type or medium. Certain qualifiers are applicable only to magnetic tape, or only to disk, or only to the ISO 9660 or High Sierra file structures.
User Action: Enter the HELP command or refer to the OpenVMS DCL Dictionary for a list of qualifiers, then enter the corrected command.

ILLQUAL, invalid qualifier

Facility: MOUNT, Mount Utility
Explanation: Either a required qualifier was omitted from the command or an invalid qualifier was supplied with the command. Certain qualifiers are valid only in conjunction with other qualifiers (such as /SHADOW) or are valid only when optional software products are installed.
User Action: Refer to online Help or the OpenVMS DCL Dictionary for a description of valid qualifier combinations; then enter the corrected command.

ILLVEC, illegal interrupt or exception vector restart

IMGFILSPE, /IMAGE specification must have only device name

Facility: BACKUP, Backup Utility
Explanation: The file specification for a volume to be processed with the /IMAGE qualifier must contain only a device name.
User Action: Reenter the command, using the device name only.

Inappropriate SCA Control Message - FLAGS/OPC/STATUS/PORT 'xx/xx/xx/xx'
Facility: Cluster Port Driver
Explanation: The port driver closes the port-to-port virtual circuit to the remote port.
User Action: Retain the error logs and crash dumps from the local and remote systems, and contact a Digital support representative.

INCBADDIR, saved directory 'directory-name' has invalid format

Facility: BACKUP, Backup Utility
Explanation: In response to the /INCREMENTAL qualifier, the saved copy (in the input save set) of the specified directory is not in the expected format for a directory file. The file may have been corrupt when it was saved, or save-set data may have been lost.
User Action: After the incremental restoration is complete, check the files for correct format.

INCBDEX, boot device incompatible with existing shadow set

Facility: SHADOW, Volume Shadowing Software
Explanation: The boot device is not compatible with 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.

INCDELERR, error deleting 'file-name'

Facility: BACKUP, Backup Utility
Explanation: An error is encountered during an attempt to delete the specified file in response to the /INCREMENTAL qualifier.
User Action: Take action based on the accompanying message.

INCDELETE, deleted 'file-name'

Facility: BACKUP, Backup Utility
Explanation: The Backup utility deleted the specified file in response to the /INCREMENTAL qualifier. This message appears if the /LOG qualifier is specified.
User Action: None.

INCDEVLIS, disk and tape devices mixed in list

Facility: BACKUP, Backup Utility
Explanation: Disk and tape devices were mixed in a list of file specifications.
User Action: Reenter the command, ensuring that if a list is used, the devices in a list are the same type.

INCENTERR, error creating directory entry for 'file-name'

Facility: BACKUP, Backup Utility
Explanation: The Backup utility encountered an error during an attempt to create a directory entry for the specified file in response to the /INCREMENTAL qualifier.
User Action: Correct the error and reenter the command.

INCFILATR, incomplete file attribute data for 'file-name'

Facility: BACKUP, Backup Utility
Explanation: There is an unexpected change in the file identifier and the file attribute data is incomplete for the specified file. The Backup utility tried to restore a selected file from a save set, but the mounted volume did not contain the beginning of the file.
User Action: Retry the backup operation, using the volume that contains the beginning of the selected file as input.

INCFILSPE, /INCREMENTAL specification must have only device name

Facility: BACKUP, Backup Utility
Explanation: The file specification for a volume to be processed with the /INCREMENTAL qualifier must contain only a device name.
User Action: Reenter the command, using only the device name.

INCMEMNAM, specified shared memory name does not match

Facility: SYSGEN, System Generation Utility
Explanation: The logical name assigned to the shared memory by the SYSGEN command SHARE does not match the name in the database of shared memory that was previously specified.
User Action: Correct and reenter the command.

INCOMPACP, indicated ACP is incompatible with volume

Facility: MOUNT, Mount Utility
Explanation: The ACP specified is not an ACP for the requested device.
User Action: Reenter the command; specify an ACP that is appropriate for the particular device type.

INCOMPAT, qualifiers incompatible with already mounted volume

Facility: MOUNT, Mount Utility
Explanation: A DCL command MOUNT is entered to mount a shareable volume that is already mounted; the characteristics of the volume are already established and cannot be changed.
User Action: Use the DCL command SHOW DEVICE to determine how the volume is mounted. Reenter the DCL command MOUNT/SHARE without qualifiers.

INCOMPDRVACP, incompatible LATACP and LTDRIVER - LATACP terminating

Facility: LAT, LAT Facility
Explanation: An attempt to start LAT failed because of a mismatch between the LAT driver and LATACP.
User Action: Locate the mismatched image and remove it from the system.

INCONFOR, inconsistent /FOREIGN option. Cluster mounted 'option'

Facility: MOUNT, Mount Utility
Explanation: The qualifier specified on the current mounting node is different from the value used by other nodes that have already mounted the same disk.
User Action: Specify /FOREIGN or /NOFOREIGN in the MOUNT command to match the option used by the other nodes.

INCONOWNER, inconsistent /OWNER_UIC option. Verify volume owner

Facility: MOUNT, Mount Utility
Explanation: The UIC specified in the /OWNER_UIC qualifier is not consistent with the protection that this device has been mounted with on other nodes in the cluster.
User Action: Verify that the /OWNER_UIC option is specified consistently on all nodes.

INCONPROT, inconsistent /PROTECTION option. Verify volume protection

Facility: MOUNT, Mount Utility
Explanation: The protection specified in the /PROTECTION qualifier is not consistent with the protection that the device has been mounted with on other nodes in the cluster.
User Action: Verify that the /PROTECTION option is specified consistently on all nodes.

INCONQUALS, qualifier '/qualifier' contradicts qualifier '/qualifier'

Facility: BACKUP, Backup Utility
Explanation: The two specified qualifiers conflict and cannot be used together in the BACKUP command.
User Action: Reenter the BACKUP command with only one of the two qualifiers. For more information about how qualifiers affect the BACKUP command, see the OpenVMS System Management Utilities Reference Manual.

INCONQUOTA, inconsistent /(NO)QUOTA option. Cluster mounted 'option'

Facility: MOUNT, Mount Utility
Explanation: The quota option specified on the current mounting node is different from the quota option used by other nodes that have already mounted the same disk.
User Action: Specify /QUOTA or /NOQUOTA in the MOUNT command to match the option used by the other nodes.

INCONSDEV, inconsistent device types

Facility: MOUNT, Mount Utility
Explanation: Both disks and magnetic tapes appear in the list of devices to be mounted.
User Action: Specify one or the other and reenter the command; check the logical name assignments.

INCONSHR, inconsistent sharing option. Cluster mounted 'option'

Facility: MOUNT, Mount Utility
Explanation: The sharing option specified on the current mounting node is different from the sharing option used by other nodes that have already mounted the same disk.
User Action: Specify /SHARE or /NOSHARE in the MOUNT command to match the option used by the other nodes.

INCONSTATE, inconsistent I/O data base

INCONWRITE, inconsistent /(NO)WRITE option. Cluster mounted 'option'

Facility: MOUNT, Mount Utility
Explanation: The write option specified on the current mounting node is different from the write option used by other nodes that have already mounted the same disk.
User Action: Specify /WRITE or /NOWRITE in the MOUNT command to match the option used by the other nodes.

INCPTREF, increment page table reference count error

INCRVN, incorrect relative volume mounted on 'device-name'

Facility: BACKUP, Backup Utility
Explanation: Either the wrong volume of a multivolume disk save-set was mounted, or the positional order of the devices in the input specification does not agree with the relative volume numbers recorded on the volumes.
User Action: Locate and mount the correct volume.

INCSETCNT, incorrect number of devices in input specification

Facility: BACKUP, Backup Utility
Explanation: The number of devices in the input specification does not agree with the volume set count recorded on relative volume 1.
User Action: Reenter the command with the correct number of devices.

INCSHAMEM, incompatible shadow set member

Facility: SHADOW, Volume Shadowing Software
Explanation: One or more of the shadow set member storage control blocks is incompatible with the boot device storage control block.
User Action: Reboot the system excluding incompatible members.

INDEXTOSM, index file is too small on output device 'device-name'

Facility: BACKUP, Backup Utility
Explanation: The /NOINITIALIZE qualifier was specified on the output disk for an image backup, but the size of INDEXF.SYS on the output disk cannot accommodate the number of files on the input disk.
User Action: Initialize the output disk and increase the number of headers on the disk by using the /HEADERS and /MAXIMUM_FILES qualifiers on the INITIALIZE command. The output disk must contain as many or more headers as there are files on the input disk.

INPUTERR, error opening primary input file SYS$INPUT

Facility: LOGIN, Login Procedure
Explanation: The system cannot open the current input device and cannot perform the login.
User Action: Take action based on the accompanying message.

INSBUFSPACE, insufficient virtual memory to accommodate minimum buffer count

Facility: BACKUP, Backup Utility
Explanation: Not enough virtual memory was available to the process to allocate the minimum number of buffers required to perform the backup operation.
User Action: The system manager should ensure that the SYSGEN and UAF parameters for all accounts that perform backup operations are at the recommended settings.

INSNFREPAG, insufficient nonfree pages

INSNPDYN, insufficient non-paged dynamic memory

Facility: SHADOW, Volume Shadowing Software
Explanation: There is not enough room in the nonpaged pool for shadowing to allocate data structures required during boot time.
User Action: Reboot the system, stop during SYSBOOT, and increase the value of the parameter NPAGEDYN.

INSQUOTA, insufficient quota to map file - check BYTLM

Facility: BACKUP, Backup Utility
Explanation: The Backup utility was processing a file that cannot be mapped because of insufficient quotas.
User Action: The system manager should ensure that the SYSGEN and UAF parameters for all accounts that perform backup operations are at the recommended settings.

INSRES, insufficient resources to complete operation

Facility: LAT, LAT Facility
Explanation: The system does not have enough resources to service the request.
User Action: Contact the system manager to determine which system resource is inadequate.

INSSWPFIL, insufficient swap file space

Insufficient Non-paged Pool for Initialization
Facility: Cluster Port Driver
Explanation: The port driver was unable to allocate sufficient memory from either nonpaged pool or bus addressable pool (BAP) in order to complete initialization. The port driver will not attempt to start the port.
User Action: Examine the current values for SYSGEN parameters NPAGDYN, NPAGEVIR, NPAG_BAP_MIN, NPAG_BAP_MAX, and NPAG_BAP_MAX_PA to determine which might be too small. Note the guidelines for the following SYSGEN parameters:

NPAG_BAP_MIN and NPAG_BAP_MAX If the system has a CIPCA, CIXCD, or KFMSB adapter, NPAG_BAP_MIN should be at least 256KB times the sum of these adapter types and NPAG_BAP_MAX should be at least 4MB times the sum of these adapter types. For each calculation, each KFMSB must be counted twice because it is a 2-port adapter.

NPAG_BAP_MAX_PA On a PCI system, NPAG_BAP_MAX_PA should be 107374182 (1GB) after the reboot with AUTOGEN during installation. Do not set NPAG_BAP_MAX_PA to any value greater than 1GB or less than FFFFFFFF (hexadecimal) or the system may not be able to boot.

These guidelines may change. Check the documentation accompanying the OpenVMS release you are running for the latest recommendations.

Insufficient Non-paged Pool for Virtual Circuits
Facility: Cluster Port Driver
Explanation: After finding that insufficient memory resources are available for normal communication, the port driver breaks a virtual circuit.
User Action: Increase the NPAGEDYN pool SYSGEN parameter and reboot the system.

INSWAPERR, inswap read error

INVADAP, invalid adapter name specified

Facility: SYSGEN, System Generation Utility
Explanation: The specified adapter number is found to be invalid after bootstrap.
User Action: Reenter the command, using the correct adapter number.

INVATTSIZ, invalid attribute record size in save set

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

INVATTSTR, invalid attribute record structure level in save set

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

INVATTVAL, invalid attribute record value in save set

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

INVBJLEOF, invalid end-of-file position in BACKUP journal

Facility: BACKUP, Backup Utility
Explanation: The end-of-file pointer recorded for the journal file specified by the /JOURNAL qualifier is invalid. The journal file is corrupt and cannot be used.
User Action: Reconstruct the journal file from backup media.

INVBJLSIZ, invalid record size in BACKUP journal

Facility: BACKUP, Backup Utility
Explanation: An invalid record size occurred in the journal file specified by the /JOURNAL qualifier. The journal file is corrupt and cannot be used.
User Action: Reconstruct the journal file from backup media.

INVBJLSTR, invalid structure level in BACKUP journal

Facility: BACKUP, Backup Utility
Explanation: The structure level recorded in the journal file specified by the /JOURNAL qualifier is invalid. The journal file is corrupt and cannot be used.
User Action: Reconstruct the journal file from backup media.

INVBJLTYP, invalid record type in BACKUP journal

Facility: BACKUP, Backup Utility
Explanation: An invalid record type occurred in the journal file specified by the /JOURNAL qualifier. The journal file is corrupt and cannot be used.
User Action: Reconstruct the journal file from backup media.

INVBLKHDR, invalid block header in save set

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

INVBLKSIZE, invalid block size in save set

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

INVCHAN, invalid ACP channel number

INVCJFIOD, invalid IO database structure (journaling)

INVCMD, invalid command

Facility: LAT, LAT Facility
Explanation: The specified LATCP command is invalid.
User Action: Take action based on the accompanying message.

INVDEVTYP, invalid backup device type 'file-spec'

Facility: BACKUP, Backup Utility
Explanation: The specified device type is invalid.
User Action: Reenter the command, specifying a disk or tape device.

INVDPT, invalid driver image - DPT$B_TYPE, VBN 2 .NEQ. DYN$C_DPT

Facility: SYSGEN, System Generation Utility
Explanation: The driver image file specified in the SYSGEN command LOAD, RELOAD, or CONNECT does not pass a basic validity check. This error can be caused by one of the following conditions:

Not having the driver prologue table (DPT) as the first code-generating component of the driver
Not linking the driver as an executable image based at 0
Having PSECT statements in the driver program
Any other problem that causes the driver prologue table not to be in the second block (VBN 2) of the image file

User Action: Correct the driver code and reenter the command.

INVDPTINI, invalid driver prologue init table value

Facility: SYSGEN, System Generation Utility
Explanation: One of the following conditions exists:

The initialization or reinitialization entry in the driver prologue table has an invalid control block type code; that is, one other than DDB, UCB, CRB, or IDB.
The initialization or reinitialization entry in the driver prologue table has an invalid store function; that is, one other than B, W, L, R, V, @B, @W, @L, @R, or @V.

User Action: Correct the DPT_STORE macro in the driver prologue table.

INVEXCEPTN, exception while above ASTDEL or on interrupt stack

INVFID, invalid file id in save set - cannot restore /IMAGE

Facility: BACKUP, Backup Utility
Explanation: An attempt is made to restore a file with a zero file identification in /IMAGE mode. This may occur if the save set is written by an operating system other than an OpenVMS operating system.
User Action: Use a mode other than /IMAGE to restore the file.

INVFILEXT, invalid file extension linkage in 'file-spec'

Facility: BACKUP, Backup Utility
Explanation: The specified save-set file has an invalid pointer to a following segment of the file. The remainder of the file is not accessible.
User Action: Attempt to recover data by beginning a restore operation with the first unprocessed file segment.

INVHOMBLK, 'device-name' has invalid home block

Facility: BACKUP, Backup Utility
Explanation: The specified volume has an invalid Files--11 home block.
User Action: Repair the volume using the Analyze/Disk_Structure utility.

INVINPUT, invalid SYS$INPUT for interactive login

Facility: LOGIN, Login Procedure
Explanation: SYS$INPUT is a logical name for the input from a process to the system. When the system is used interactively, SYS$INPUT is assigned to your terminal by default. The system then acts upon the input it receives from your terminal. During your process, you can redefine SYS$INPUT to a data file; the system will then read input from the file. However, you cannot initiate an interactive process while SYS$INPUT is defined as a file. File-structured storage devices are not permitted as SYS$INPUT for interactive processes. The purpose of this restriction is to prevent LOGIN from reading a user name and password from a file.
User Action: Use a non-file-structured device as SYS$INPUT for an interactive process.

INVLDRESP, invalid operator response

Facility: MOUNT, Mount Utility
Explanation: The operator responded to a request with an invalid reply.
User Action: None. The request is automatically reentered.

INVLOCKID, invalid lock id

INVPARFIL, invalid parameter file

Facility: SYSGEN, System Generation Utility
Explanation: An error occurred accessing the file specified in a USE or WRITE operation.
User Action: Check that the file is not protected against read or write access and then reenter your command. If the error occurs again, but the file can be read or written by other utilities, retain a copy of the invalid parameter file and contact a Digital support representative.

INVPTEFMT, invalid page table entry format

INVPWD, invalid password

Facility: LOGIN, Login Procedure
Explanation: The specified password is incorrect. This message is written to the system accounting and security audit records; the NOTVALID message displays to the user.
User Action: None.

INVQALPOS, invalid '/qualifier' qualifier positional use

Facility: BACKUP, Backup Utility
Explanation: The specified command qualifier was incorrectly positioned in the command.
User Action: Reenter the command, being sure to properly order the input and output fields and the global qualifiers.

INVQUAVAL, value 'value' invalid for '/qualifier' qualifier

Facility: BACKUP, Backup Utility
Facility: MOUNT, Mount Utility
Explanation: The specified value is not valid for the specified qualifier.
User Action: Use the DCL HELP command or refer to the OpenVMS DCL Dictionary for the valid qualifier values. Then enter the corrected command.

INVRECSIZ, invalid record size in save set

Facility: BACKUP, Backup Utility
Explanation: An incorrect value occurred in the record size field (BRH$W_RSIZE) of a save-set record. Data in the save set is corrupt.
User Action: None. Save-set data is lost.

INVRECTYP, invalid record type in save set

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

INVREQ, the parameter 'parameter' is invalid.

Facility: STDRV, System Startup Driver
Explanation: The startup driver is executed with an invalid first parameter.
User Action: If the error occurs during a system boot, check the value of the SYSGEN parameter STARTUP_P1. If errors occur after a @STARTUP command procedure, verify that the first parameter is FULL, MINIMUM, UPGRADE, or the name of the system component to restart.

INVRSPID, RSPID not valid

INVSSDVU, invalid shadow system disk virtual unit number

Facility: SHADOW, Volume Shadowing Software
Explanation: The shadowed system disk virtual unit number is greater than 9999.
User Action: Use a shadowed system disk virtual unit number less than or equal to 9999.

INVSTRUCT, invalid structure level in save set

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

INVTQEFMT, invalid time queue entry format

INVVEC, invalid or unspecified interrupt vector

Facility: SYSGEN, System Generation Utility
Explanation: Either no interrupt vector is specified in the SYSGEN command CONNECT, or the one that is specified is not within the UNIBUS interrupt vector address range.
User Action: Reenter the command, specifying a valid vector number.

ISACPYTRGT, member was target of incomplete copy

Facility: MOUNT, Mount Utility
Explanation: A specified member of a shadow set was the target of a shadow copy operation that did not complete. The member's contents are not valid. A copy target cannot be a shadow set virtual unit; it can be added into a shadow set only as a copy target.
User Action: Find or initialize another volume to be the shadow set master.

ISAMBR, 'device-name' is a member of the shadow set

Facility: MOUNT, Mount Utility
Explanation: The specified device is already a member of the shadow set.
User Action: None. For completeness, MOUNT reports the status of all members of the shadow set.

IVBAKADIO, invalid backing store address for I/O

IVGBLTYP, invalid global master PTE type

IVLISTK, interrupt stack invalid restart

IVSSRVRQST, invalid system service request

IVWSETLIST, invalid working set list entry

Contents

Index

privacy and legal statement

6023PRO_009.HTML

NPAG_BAP_MIN and NPAG_BAP_MAX	If the system has a CIPCA, CIXCD, or KFMSB adapter, NPAG_BAP_MIN should be at least 256KB times the sum of these adapter types and NPAG_BAP_MAX should be at least 4MB times the sum of these adapter types. For each calculation, each KFMSB must be counted twice because it is a 2-port adapter.
NPAG_BAP_MAX_PA	On a PCI system, NPAG_BAP_MAX_PA should be 107374182 (1GB) after the reboot with AUTOGEN during installation. Do not set NPAG_BAP_MAX_PA to any value greater than 1GB or less than FFFFFFFF (hexadecimal) or the system may not be able to boot.