Document revision date: 19 July 1999
|
|
|
|
OpenVMS System Messages: Companion Guide for Help
Message Users
JBCMIXUP, fatal job controller interaction problem
Facility: LOGIN, Login Procedure
Explanation: An internal error occurred in the job
controller during the login; the login cannot be performed.
User Action: Repeat the login procedure. If the
failure persists, notify the system operator or manager.
JNLACP, Fatal error detected by journal ACP
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.
JNLDRV, Fatal error detected by journal driver
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.
JOURNAL, journaling to 'file-spec'
Facility: BACKUP, Backup Utility
Explanation: The Backup utility is writing journal
records to the specified file in response to the /JOURNAL qualifier.
This message is displayed only if the /LOG qualifier is specified.
User Action: None.
KRNLSTAKNV, kernel stack not valid
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.
LABELERR, error in tape label processing on 'save-set-spec'
Facility: BACKUP, Backup Utility
Explanation: The Backup utility encountered an error
during an attempt to process the file labels on the specified volume.
User Action: Take action based on the accompanying message.
LARGECNT, 'device-name' is too large to be processed
Facility: BACKUP, Backup Utility
Explanation: The specified volume is too large to be
processed by the Backup utility. Possibly the specified cluster factor
is too small.
User Action: Retry the operation using a larger volume
cluster factor.
LBLOVRWRITE, volume label 'label' overwritten, new label is 'label'
Facility: BACKUP, Backup Utility
Explanation: The loaded volume was overwritten and a
new label was written to the volume. The labels specified in this
message provide additional information.
User Action: None.
LISINPSAV, /LIST requires save set as input
Facility: BACKUP, Backup Utility
Explanation: The input specification for a listing
operation must reference a save set.
User Action: Correct the specification and reenter the
command.
LKBGRANTED, LKB is granted, but shouldn't be
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.
LKBREFNEG, LKB reference count negative
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.
LOADERR, error configuring device 'device-name', driver 'driver-name'
Facility: IOGEN
Explanation: An error occurred during
autoconfiguration.
User Action: Take action based on the accompanying message.
LOCKERR, failed to lock volume
Facility: RBLD, REBUILD Command (Mount Utility)
Explanation: An error occurred while trying to lock
the volume set against modification.
User Action: Take action based on the accompanying
message.
LOCKMGRERR, error detected by Lock Manager
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.
LOGDISABL, logins are currently disabled - try again later
Facility: LOGIN, Login Procedure
Explanation: Logins are currently disabled.
User Action: Do not attempt to log in at this time.
Try again later.
LOGNAME, logical name is too long
Facility: MOUNT, Mount Utility
Explanation: A logical name contains more than 255
characters.
User Action: Correct and reenter the command.
Low 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. 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.