OpenVMS System Messages: Companion Guide for Help Message Users

Updated: 11 December 1998

OpenVMS System Messages: Companion Guide for Help Message Users

Contents

Index

FACTBAD, cannot read factory bad block data on 'device-name'

Facility: BACKUP, Backup Utility
Explanation: Either the Backup utility or the DCL command INITIALIZE encountered an error during an attempt to read the bad block data recorded on the specified volume.
User Action: Correct the error and reenter the command, or notify the system manager. If the volume is under warranty, return it to the factory. Contact a DIGITAL support representative if necessary.

Failed to Locate Port Micro-code Image
Facility: Cluster Port Driver
Explanation: The port driver will not start the port.
User Action: Make sure that the console load media is present in the console drive, and reboot the system.

FATALERR, fatal error on 'save-set-spec'

Facility: BACKUP, Backup Utility
Explanation: The Backup utility encountered an irrecoverable error during an attempt to read or write the specified save set.
User Action: Take action based on the accompanying message.

FATALERR, fatal error reading startup database

Facility: STDRV, System Startup Driver
Explanation: The startup driver encountered a fatal error while trying to read the startup database files. The startup operation is aborted. If this message occurs during a system reboot, the OpenVMS software may not have been properly started.
User Action: Verify that the startup databases, defined by the logical names STARTUP$STARTUP_VMS, STARTUP$STARTUP_LAYERED, and STARTUP$PHASES, are all available and can be accessed.

FATALEXCPT, fatal executive or kernel mode exception

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.

FIDERROR, unexpected file change in 'file-spec'

Facility: BACKUP, Backup Utility
Explanation: A file boundary marker is missing from the input save set. Data in the save set may be corrupt. It is likely that parts of the specified file and one or more complete files are missing.
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.

FIDNOTFND, internal error. File to be processed not found on process list

Facility: BACKUP, Backup Utility
Explanation: The file context has been lost. This is an internal error.
User Action: If this error can be reliably reproduced, note the circumstances and the BACKUP command used, and contact a DIGITAL support representative.

FILCNTNONZ, open file count nonzero after process rundown

FILEACC, error accessing system authorization file

Facility: LOGIN, Login Procedure
Explanation: An error occurred while attempting to access the authorization file.
User Action: The system manager should ensure that the SYS$SYSTEM:SYSUAF.DAT file exists and has system read access. Then you can retry the login procedure.

FILNOPOST, file will not be subject to date-recording or deletion

Facility: BACKUP, Backup Utility
Explanation: This warning message indicates that the Backup utility will not post-process the file because its contents were not successfully verified.
User Action: Determine why the file could not be successfully verified and retry the backup operation.

FILNOTEXP, file is not expired on volume on 'volume-name'

Facility: MOUNT, Mount Utility
Explanation: A tape file cannot be overwritten because it has not reached its expiration date.
User Action: To overwrite or delete the file, mount the volume with the /OVERRIDE=EXPIRATION qualifier. You must be the owner of the volume or have volume protection (VOLPRO) privilege.

FNF, file not found

Facility: SYSGEN, System Generation Utility
Explanation: SYSGEN is unable to locate the driver image file. The default directory and disk device for driver images is SYS$SYSTEM. This message is also produced during an AUTOCONFIGURE operation if a UNIBUS device does not have a corresponding driver in SYS$SYSTEM.
User Action: Restore the image file to the system disk from a backup disk.

FRCPWDERR, error changing expired password

Facility: LOGIN, Login Procedure
Explanation: An error occurred while changing an expired password.
User Action: Take action based on the accompanying message.

FREEBADBUFF, attempted to free busy (or free) buffer

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

FREEMEM, error freeing virtual memory

Facility: BACKUP, Backup Utility
Explanation: An error was encountered during an attempt to free dynamic virtual memory. This message indicates a software error in the utility that produced it.
User Action: Contact a DIGITAL support representative.

FREEPAGREF, free page reference count is nonzero

FREWSLX, free working set list index, resource wait

GBLPAGSZRO, Global page share count is zero

GBLWSLXERR, Global working set list entry not found

GENMINUS1, shadow set virtual unit generation number invalid on 'device'

Facility: BACKUP, Backup Utility
Explanation: An attempt was made to use the BACKUP command on a member of a shadow set that has not yet been fully formed.
User Action: Wait for the shadow set to be fully formed and retry the backup operation.

GETCHN, error getting device characteristics for 'device-name'

Facility: BACKUP, Backup Utility
Explanation: The Backup utility encountered an error during an attempt to obtain the device characteristics of the input device.
User Action: Take action based on the accompanying message.

GPGNULPGFL, global page has null page file address

HALT, halt instruction restart

HDRCRC, software header CRC error

Facility: BACKUP, Backup Utility
Explanation: An incorrect value occurred in the header CRC field (BBH$W_CHECKSUM) of a save-set block. Data in the save set is corrupt.
User Action: None. The save-set data is lost.

HDRNOTMAP, allocated file header not mapped

HEADCOPIED, copied 'file-header' header

Facility: BACKUP, Backup Utility
Explanation: This /LOG message indicates that a file header only is copied. The file is marked NOBACKUP; therefore, no data is saved.
User Action: None.

HEADERERR, I/O error reading file header 'file-header' on relative volume 'volume-id'

Facility: RBLD, REBUILD Command (Mount Utility)
Explanation: The rebuild operation was unable to read the file header on the specified volume.
User Action: Take action based on the accompanying message.

High Priority Command 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.
User Action: Contact a DIGITAL support representative. 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.

HOMBLKBAD, primary home block is bad; backup used

Facility: MOUNT, Mount Utility
Explanation: The primary home block of a disk is corrupt or unreadable; the backup volume is used to mount the volume.
User Action: Repair the disk using the Analyze/Disk_Structure utility.

HOMBLKCHK, home block software consistency check

Facility: MOUNT, Mount Utility
Explanation: The home block in the volume failed the software consistency check during /BIND processing. The first occurrence of this message is a warning; the second is fatal.
User Action: Repair or reinitialize the volume and retry the operation.

HOMEBLOCK, failed to read home block on relative volume 'volume-id'

Facility: RBLD, REBUILD Command (Mount Utility)
Explanation: The rebuild operation cannot read the home block on the specified relative volume.
User Action: Take action based on the accompanying message.

HSC Error Logging Datagram Received - REMOTE PORT 'xxx'
Facility: Cluster Port Driver
Explanation: Upon receiving an error message from the HSC, the CI port driver logs the error and takes no other action. Since HSC informational error log datagrams are also recorded on the HSC console, it is useful to read them only if the HSC console does not record them for some reason (if it runs out of paper, for example).
User Action: The sending of HSC informational error log datagrams should be disabled with the appropriate HSC console command, since HSC informational error log datagrams take up considerable space in the error log data file.

Contents

Index

Legal

 
6023PRO_008.HTML