OpenVMS System Messages: Companion Guide for Help Message Users

Updated: 11 December 1998

OpenVMS System Messages: Companion Guide for Help Message Users

Contents

Index

QIOCALLFAIL, QIO service call failure.
Unable to obtain inquiry data from one or more SCSI initiators.

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

QIOOPFAIL, QIO service operation failure.
Unable to obtain inquiry data from one or more SCSI initiators.

Facility: STACONFIG, Standalone Configure Process
Explanation: The operation requested by the $QIOW system service did not complete successfully.
User Action: Contact a DIGITAL support representative.

QUEUEMPTY, scheduling queue empty

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.

QUOTAFAIL, failed to activate quota file; volume locked

Facility: MOUNT, Mount Utility
Explanation: An error occurred that enabled the volume's quota file; the volume is locked against allocation.
User Action: Correct the problem with the quota file. Then dismount and remount the volume.

QUOTAFILE, quota file is too small - use DISKQUOTA to rebuild

Facility: BACKUP, Backup Utility
Explanation: During a restore or copy operation with the /IMAGE qualifier, the Backup utility found that the quota file, [000000]QUOTA.SYS;1, on the output volume is not large enough.
User Action: After the restore or copy operation is complete, use the SYSMAN command DISKQUOTA REBUILD to reconstruct the quota file.

QUOTAFNF, quota file not found on volume

Facility: MOUNT, Mount Utility
Explanation: The MOUNT command specified /QUOTA or /CACHE=QUOTA, but there is no quota file on the volume.
User Action: Create a quota file on the volume by using the SYSMAN command DISKQUOTA CREATE, or mount the disk without using explicit quota references.

QUOTARERR, I/O error reading quota file

Facility: RBLD, REBUILD Command (Mount Utility)
Explanation: The rebuild operation failed to read the quota file.
User Action: Take action based on the accompanying message.

RATINGNOTINIT, LAT rating image has not been initialized

Facility: LAT, LAT Facility
Explanation: During LATACP startup, the LAT$RATING image was found to be loaded but not initialized.
User Action: Be sure to start LAT by executing the LAT$STARTUP command procedure to access the support startup files supplied by Digital. The LAT$STARTUP command procedure executes other command procedures, including LAT$CONFIG, which loads the LAT$RATING image. If you make changes to the LAT$RATING image, be sure that the initialization entry points are still called by LTDRIVER when LTDRIVER is loaded.

RCTNOPRIV, LOG_IO privilege required to read disk RCT - operation continuing

Facility: BACKUP, Backup Utility
Explanation: The Backup utility cannot read bad block data from the disk because you do not have the LOG_IO privilege.
User Action: The backup operation finishes, but bad block information is not saved. If there are bad blocks, you might want to repeat the backup operation after enabling or acquiring the necessary privilege.

RCTUNRSZR, RCT unreadable, output SERIALNUM field set to 0

Facility: BACKUP, Backup Utility
Explanation: The disk's Replacement and Caching Table was unreadable. As a result, the output volume serial number is set to 0, and data is lost.
User Action: Reformat of replace the volume.

RDSNONRES, read data substitute page nonresident

READATTR, error reading attributes for 'file-spec'

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

READBAD, error reading bad block data on 'device-name'

Facility: BACKUP, Backup Utility
Explanation: The Backup utility encountered an error during an attempt to read the bad block data recorded on the specified volume.
User Action: Take action based on the accompanying message.

READBLOCK, error reading block 'n' of 'file-spec'

Facility: BACKUP, Backup Utility
Explanation: The Backup utility encountered an error during an attempt to read the specified block of the specified file. The accompanying message provides additional information.
User Action: Examine the file for corruption and reconstruct as necessary.

READBMAP, error reading storage bitmap on 'device-name'

Facility: BACKUP, Backup Utility
Explanation: The Backup utility encountered an error during an attempt to read the storage bitmap file, [000000]BITMAP.SYS;1, on the specified volume. The volume cannot be used as a save-set disk.
User Action: Reinitialize the volume, or select another volume and retry the operation.

READDIR, error reading directory 'directory-name'

Facility: BACKUP, Backup Utility
Explanation: An error was encountered during an attempt to read the specified directory file. The Backup utility terminates processing of the directory.
User Action: Use the DCL command DIRECTORY to examine the directory and reconstruct files as necessary.

READERR, error reading 'file-name'

Facility: BACKUP, Backup Utility
Explanation: Backup cannot read the specified file.
User Action: Determine why the file cannot be read and repeat the backup operation.

READERRS, excessive error rate reading 'save-set-spec'

Facility: BACKUP, Backup Utility
Explanation: The Backup utility encountered numerous read errors in the specified save set. The save-set media is probably unusable.
User Action: Retire the save-set media.

READIMAP, error reading index file bitmap on 'device-name'

Facility: BACKUP, Backup Utility
Explanation: The Backup utility encountered an error during an attempt to read the index file, [000000]INDEXF.SYS;1, on the specified volume. The volume cannot be used as a save-set disk.
User Action: Reinitialize the volume, or select another volume and retry the operation.

READJNLACE, error reading journal ACE for 'file-spec' file ID 'file-id'

Facility: BACKUP, Backup Utility
Explanation: The Backup utility cannot read the journal access control entry (ACE) for the specified file.
User Action: Determine if the access control list (ACL) cannot be written. This could be due to a corrupted ACL or some other hardware or software related error. Correct the problem, if possible, and retry the backup operation.

READSCB, I/O error reading storage control block on relative volume 'volume-id'

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

READVERR, virtual read error on file 'file-name' at block 'block-number'

Facility: BACKUP, Backup Utility
Explanation: The Backup utility received an error while reading a block associated with the specified file.
User Action: Determine why the file could not be read and repeat the backup operation.

READYREAD, mount volume 'n' on 'device-name' for reading. Enter "YES" when ready:

Facility: BACKUP, Backup Utility
Explanation: The Backup utility requires that the specified volume of an input save set be mounted on the specified device.
User Action: Mount the volume. If the utility is executing as an interactive job, enter YES in response to the prompt on SYS$COMMAND. If the utility is executing as a batch job, use the DCL command REPLY to signal completion.

READYWRITE, mount volume 'n' on 'device-name' for writing. Enter "YES" when ready:

Facility: BACKUP, Backup Utility
Explanation: The Backup utility requires that the specified volume of an output save set be mounted on the specified device.
User Action: None; however, note that the Backup utility will write on the volume and mount a suitable volume. If the utility is executing as an interactive job, enter YES in response to the prompt on SYS$COMMAND. If the utility is executing as a batch job, use the DCL command REPLY to signal completion.

REBLDREQD, a rebuild is required for 'volume-name'

Facility: RBLD, REBUILD Command (Mount Utility)
Explanation: The specified relative volume must be rebuilt, but the user specified that the rebuild operation should not be performed during the mount operation.
User Action: Use the SET VOLUME/REBUILD command to perform a rebuild operation to recover caching limits.

REBLDREQD, rebuild not performed; some free space unavailable; diskquota usage stale

Facility: MOUNT, Mount Utility
Explanation: You mounted a volume using the /NOREBUILD qualifier and the volume was last dismounted improperly, for example, because the system crashed.
User Action: Use the DCL command SET VOLUME/REBUILD to rebuild the volume and recover disk resources that were cached when the volume was improperly dismounted.

After you have rebuilt the volume, it is good practice to use the Analyze/Disk_Structure utility to check for other errors and inconsistencies.

REBUILD, volume was improperly dismounted; rebuild in progress

Facility: MOUNT, Mount Utility
Explanation: You mounted a volume using the /REBUILD qualifier (which is the default) and the volume was last dismounted improperly, for example, because the system crashed. The volume is being rebuilt to recover disk resources that were cached when the volume was improperly dismounted.
User Action: After you have rebuilt the volume, it is good practice to use the Analyze/Disk_Structure utility to check for other errors and inconsistencies.

Received Connect Without Path-Block - FLAGS/OPC/STATUS/PORT 'xx/xx/xx/xx'
Facility: Cluster Port Driver
Explanation: A virtual circuit class message that requests an SCS connection has been received from a remote system while there is no virtual circuit to that system. The port driver attempts to reinitialize the port; after 50 failed attempts, it marks the device off line.
User Action: Retain the error logs and crash dumps from the local and remote systems, and contact a DIGITAL support representative.

RECGTRBL, record size is greater than block size

Facility: MOUNT, Mount Utility
Explanation: The record size specified is greater than the block size (specified or defaulted).
User Action: Specify a smaller record size or a larger block size.

RECORDSWL, 'device-name' is write protected - backup date recording pass not executed

Facility: BACKUP, Backup Utility
Explanation: The input device is software write-locked. The Backup utility cannot perform the backup data recording pass.
User Action: Dismount the input device, remount it as writable, and reenter the BACKUP command.

REDCACHE, volume mounted with reduced cache size

Facility: MOUNT, Mount Utility
Explanation: The /PROCESSOR=UNIQUE qualifier was used with the MOUNT command when insufficient paged pool was available to allocate a file system buffer cache using the sizes specified by the ACP_MAPCACHE, ACP_DIRCACHE, ACP_HDRCACHE, and ACP_DINDXCACHE SYSGEN parameters. Instead, a unique cache with a minimal number of buffers has been allocated.
User Action: Remove the /PROCESSOR=UNIQUE qualifier. If you need discrete I/O buffer caches, increase the size of the SYSGEN parameter PAGEDYN to account for the number of I/O buffers required. Also, increase the value of the SYSGEN parameter SYSMWCNT to avoid increased system paging.

REFCNTNEG, PFN reference count is negative

Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an inconsistent condition. After all physical memory is written to a system dump file, the system will automatically reboot 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.

Remote System Conflicts with Known System - REMOTE PORT 'xxx'
Facility: Cluster Port Driver
Explanation: The port driver configuration poller discovered a remote system with SCSSYSTEMID or SCSNODE equal to that of another system to which a virtual circuit is already open.
User Action: Shut down the new system as soon as possible. Reboot it with a unique SCSSYSTEMID and SCSNODE. Do not leave the new system up any longer than necessary. If you are running in an OpenVMS Cluster environment and two systems with conflicting identity are polling when another virtual circuit failure occurs in the OpenVMS Cluster environment, systems in the cluster environment might crash with a CLUEXIT bugcheck.

REMOUVOL, REMOUNT relative volume 'nn' 'volume-label' on 'device-name'

Facility: MOUNT, Mount Utility
Explanation: An error requiring operator intervention occurred on a magnetic tape.
User Action: Perform the required physical actions and use the DCL command REPLY to notify the system that the volume is ready.

REPLY, operator reply is 'response'

Facility: BACKUP, Backup Utility
Explanation: This informational message displays the operator's response to the Backup query.
User Action: None.

REPLYERR, error in operator reply, type = 'n', status = 'nnnn', ID = 'nnn', reply = 'operator reply'

Facility: MOUNT, Mount Utility
Explanation: The operator entered an invalid reply to the operator mount request.
User Action: The operator must enter a valid reply to the operator mount request. Check the accompanying message for details about what was wrong with the original reply.

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

RESTRICT, you are not authorized to login from this source

Facility: LOGIN, Login Procedure
Explanation: Authorization is needed for the login class you are attempting from the current source. The login classes are: LOCAL, DIALUP, REMOTE, NETWORK, and BATCH. The system manager can restrict your 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.

RESUME, resuming operation on volume 'n'

Facility: BACKUP, Backup Utility
Explanation: The Backup utility is continuing an operation on the specified volume of a save set.
User Action: None.

RMSBUG, RMS has detected an invalid condition

RMTMNTFAIL, 'device-name' failed to mount on node 'node-name'

Facility: MOUNT, Mount Utility
Explanation: An attempt to mount a device clusterwide failed to mount the device on a remote node.
User Action: Take action based on the accompanying message.

RMTMNTSUCC, 'device-name' mounted successfully on node 'node-name'

Facility: MOUNT, Mount Utility
Explanation: The mount operation on the specified remote device has completed successfully.
User Action: None.

RQSTDON, operator request canceled - mount completed successfully

Facility: MOUNT, Mount Utility
Explanation: A previously issued operator request has been canceled and the mount operation has completed successfully.
User Action: None.

RSBREFNEG, RSB reference count negative

RSBREFNZRO, tried to deallocate RSB with non-zero ref. count

RSTRTDIS, restart disabled for this backup session

Facility: BACKUP, Backup Utility
Explanation: The save set being written was started in the end-of-tape (EOT) region of the previous tape. No data was written on the previous tape, only ANSI labels. Because the present tape is logical volume #2, but no data has been written, the Backup utility cannot collect its restart checkpoint data. As a result, restart is disabled.
User Action: None.

RSV_ERR, cannot have RSV device - set to zero

Facility: SYSGEN, System Generation Utility
Explanation: RSV is a reserved device name and cannot be specified to the SYSGEN command CONFIGURE.
User Action: Do not specify RSV as a device name.

RUF, fatal error detected by Recovery Unit Facility

RVN1NOTMT, root volume is not mounted

Facility: MOUNT, Mount Utility
Explanation: The root volume for the volume set specified in the DCL command MOUNT/BIND is not mounted. The root volume must be mounted when you add a new volume to an existing volume set.
User Action: Verify that the root volume is mounted and on line; if it is not, mount it and reenter the command. Verify the device names and volume labels specified in the command and retry the operation.

Contents

Index

Legal

 
6023PRO_015.HTML