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

SYSINIT-E-create process error on STARTUP, status = 'status'
Facility: SYSINIT, System Initialization
Explanation: An error occurred while creating the STARTUP process.
User Action: Take action based on the accompanying message and reboot the system.

SYSINIT-E-error allocating pool - error log buffers not copied, status = 'status'
Facility: SYSINIT, System Initialization
Explanation: There was insufficient nonpaged pool available to allocate the error log recovery buffer used to store the error log messages for ERRFMT to copy out later to the error log file. Because not enough pool is available to allocate the storage area, the error log messages cannot be saved.
User Action: Increase the SYSGEN parameter NPAGEDYN so that enough nonpaged pool is available to allocate the error log recovery buffer.

SYSINIT-E-error creating shadowed system disk, status = 'status'
Facility: SYSINIT, System Initialization
Explanation: An error was encountered when creating the shadowed system disk. The 'status' field provides the actual failure status represented as a hexadecimal number.
User Action: Try to determine the cause of the failure. If a running system is not available to determine the ident, contact your software support organization to determine the ident for you.

SYSINIT-E-error loading message file, status = 'status'
Facility: SYSINIT, System Initialization
Explanation: The system message file, SYS$MESSAGE:SYSMSG.EXE, could not be loaded into the system. The 'status' field provides the failure status represented as a hexadecimal number.
User Action: Try to determine the cause of the failure. If you do not have a running system available to determine the ident, contact your software support organization to determine the ident for you.

SYSINIT-E-error loading RECOVERY_UNIT_SERVICES.EXE, status = 'status'
Facility: SYSINIT, System Initialization
Explanation: The OpenVMS RECOVERY_UNIT_SERVICES image, SYS$LOADABLE_IMAGES:RECOVERY_UNIT_SERVICES.EXE, could not be loaded into the system. The 'status' field provides the failure status represented as a hexadecimal number.
User Action: Try to determine the cause of the failure. If you do not have a running system available to determine the ident, contact your software support organization to determine the ident for you.

SYSINIT-E-error loading RMS.EXE, status = 'status'
Facility: SYSINIT, System Initialization
Explanation: The RMS file system image, SYS$LOADABLE_IMAGES:RMS.EXE, could not be loaded into the system. The 'status' field provides the failure status represented as a hexadecimal number.
User Action: Try to determine the cause of the failure. If you do not have a running system available to determine the ident, contact your software support organization to determine the ident for you.

SYSINIT-E-error mounting system device, status = 'status'
Facility: SYSINIT, System Initialization
Explanation: An error condition is preventing the system disk from being mounted. In general, these error conditions are no different from errors that prevent other volumes from being mounted, such as a random I/O error, a corrupted file system, or an incorrect ACP image.
User Action: Correct the problem that is preventing the system disk from being mounted, then reboot the system.

SYSINIT-E-error opening or mapping F11BXQP, status = 'status'
Facility: SYSINIT, System Initialization
Explanation: The OpenVMS file system, SYS$SYSTEM:F11BXQP.EXE, could not be opened or mapped. The 'status' field provides the failure status represented as a hexadecimal number.
User Action: Try to determine the cause of the failure. If you do not have a running system available to determine the ident, contact your software support organization to determine the ident for you.

SYSINIT-E-error opening page file, status = 'status'
Facility: SYSINIT, System Initialization
Explanation: The primary paging file, SYS$SYSTEM:PAGEFILE.SYS, could not be opened. The 'status' field provides the failure status.
User Action: Try to determine the cause of the failure. If you do not have a running system available to determine the ident, contact your software support organization to determine the ident for you.

SYSINIT-E-error opening swap file, status = 'status'
Facility: SYSINIT, System Initialization
Explanation: The system swap file, SYS$SYSTEM:SWAPFILE.SYS, could not be opened. The 'status' field provides the actual failure status.
User Action: Try to determine the cause of the failure. If you do not have a running system available to determine the ident, contact your software support organization to determine the ident for you.

SYSINIT-E-error opening system dump file, status = 'status'
Facility: SYSINIT, System Initialization
Explanation: The system dump file, SYS$MESSAGE:SYSDUMP.DMP, could not be loaded into the system. The 'status' field provides the failure status represented as a hexadecimal number.
User Action: If you do not have a running system available to determine the ident, contact your software support organization to determine the ident for you.

SYSINIT-E-error reading system dump file error log buffers, status = 'status'
Facility: SYSINIT, System Initialization
Explanation: An error occurred while reading the error log buffers in from the dump file. The hexadecimal error status value described by 'status' is the failure status returned after the read operation failed.
User Action: Check the system dump file for disk errors. It might be necessary to create a new dump file.

SYSINIT-E-error taking out lock on system disk, status = 'status'
Facility: SYSINIT, System Initialization
Explanation: An error was encountered when acquiring a clusterwide lock on the system device. The 'status' field provides the actual failure status.
User Action: Try to determine the cause of the failure. If you do not have a running system available to determine the ident, contact your software support organization to determine the ident for you.

SYSINIT-E-failed to create system logical names, status = 'status'
Facility: SYSINIT, System Initialization
Explanation: An error occurred while attempting to create a logical name needed by SYSINIT (SYS$SYSTEM, SYS$SHARE, SYS$MESSAGE). The complete list of errors that can occur when creating logical names is given in the OpenVMS System Services Reference Manual. The error that occurred while SYSINIT was executing (assuming that the SYSINIT image is not corrupted) is due to insufficient paged dynamic memory.
User Action: Set the SYSGEN parameter PAGEDYN to a reasonable value (at least 10,000) and reboot the system.

SYSINIT-E-page file or swap file control block initialization error, status = 'status'
Facility: SYSINIT, System Initialization
Explanation: An error occurred, for one of the following reasons, while attempting to install the primary paging or swap file:

There is not enough nonpaged pool for the PFL bitmap.
The SYSGEN parameter PAGFILCNT is set to 0.
The file is badly fragmented and an error occurred while trying to map the file completely.

User Action: Correct the error using one of the following methods and reboot the system:

If there is not enough nonpaged pool, see the message INSFMEM for information about making enough nonpaged pool available for booting the system.
Do not set PAGFILCNT to 0.
The complete mapping of a file can be prevented if there is not enough nonpaged dynamic memory or if the SYSGEN parameter PQL_DBYTLM is set too small.

SYSINIT-E-recoverable error encountered when mounting system device, status='status'
Facility: SYSINIT, System Initialization
Explanation: A recoverable disk I/O error was encountered when mounting the system disk. The mount operation will be retried automatically.
User Action: None.

SYSINIT-E-unable to obtain lock for system ID resource, status = 'status'
Facility: SYSINIT, System Initialization
Explanation: An error was encountered when acquiring a system-owned lock whose name contains the system ID. The 'status' field provides the failure status represented as a hexadecimal number.
User Action: Try to determine the cause of the failure. If you do not have a running system available to determine the ident, contact your software support organization to determine the ident for you.

SYSINIT-I- found a valid OpenVMS Cluster quorum disk
Facility: SYSINIT, System Initialization
Explanation: The cluster quorum disk and quorum file have been located and validated.
User Action: None.

SYSINIT-I- no dump file - error log buffers not saved
Facility: SYSINIT, System Initialization
Explanation: The system disk does not have either a dump file SYSDUMP.DMP or a page file PAGEFILE.SYS; therefore, the contents of the error log buffers at the time of the last shutdown/crash that were saved in the dump file are not available for recovery from the dump file into the error log buffer recovery area.
User Action: Create a page file PAGEFILE.SYS or a dump file SYSDUMP.DMP on the system disk, and reboot the system so that a dump file is available and error log buffers are saved across a shutdown or system failure.

SYSINIT-I- PAGEFILE.SYS not found - system initialization continuing...
Facility: SYSINIT, System Initialization
Explanation: The primary paging file, SYS$SYSTEM:PAGEFILE.SYS, could not be found.
User Action: Use the command procedure SYS$UPDATE:SWAPFILES.COM to place a page file in the system directory SYS$SYSTEM. Alternatively, one or more secondary page files can be installed by editing the SYS$SPECIFIC:[SYSMGR]SYPAGSWPFILES.COM file.

SYSINIT-I- waiting to form or join an OpenVMS Cluster
Facility: SYSINIT, System Initialization
Explanation: The cluster quorum disk and nodes are being searched to form a cluster quorum.
User Action: None.

SYSINIT-W- dump file write errors - error log buffers not saved
Facility: SYSINIT, System Initialization
Explanation: Since the entire dump file contents are suspect, the dump file write is not successfully completed, and no attempt is made to recover the saved error log messages from the dump file.
User Action: None.

SYSINIT-W- invalid dump header version - error log buffers not saved
Facility: SYSINIT, System Initialization
Explanation: The dump file contains the contents of a dump written under a version of the OpenVMS operating system different from the version that is being booted now. Therefore, the error log messages saved in the dump file are not read out from the dump file, since the format of the dump file and error log messages may be different from that format being used on this version. This message is primarily to warn users that some error log messages have been lost.
User Action: None.

SYSLOG, unable to modify SYS$DEVICE/SYS$DISK logicals

Facility: SHADOW, Volume Shadowing Software
Explanation: Shadowing could not update system disk pointers and logical names to point to a virtual unit.
User Action: Consult your system manager about the problem. The system manager can check error logs for device problems, change system parameter settings if necessary, or take other action to correct the problem.

SYSPWDTMO, system password timeout

Facility: LOGIN, Login Procedure
Explanation: A user failed to correctly enter the system password within the allotted time period (as defined by the SYSGEN parameter LGI_PWD_TMO). This message is written to the system accounting and security audit records. The user does not receive a message when this error occurs.
User Action: None.

SYSTRMERR, SYSINIT-terminal IO error

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.

SYSVERCHK, system version mismatch - function aborted

Facility: SYSGEN, System Generation Utility
Explanation: An attempt to do a WRITE CURRENT operation failed because the SYSGEN.EXE version does not match the SYS.EXE version.
User Action: Reenter the command, specifying the proper version of SYSGEN.EXE.

SYSVERDIF, system version mismatch - reassemble and relink driver

Facility: SYSGEN, System Generation Utility
Explanation: A driver mismatch has been encountered.
User Action: Reassemble and relink all drivers at each major release of the OpenVMS operating system.

SZTOOBIG, record size or block size greater than 65534

Facility: MOUNT, Mount Utility
Explanation: The record size specified by /RECORDSIZE or the block size specified by /BLOCKSIZE is greater than 65534.
User Action: Correct the command and reenter it.

TAPEALLODIFFF, The TAPE_ALLOCLASS parameter value for the processor
on SCSI bus 'device-name', ID 'slot-number', is different from the value on this system. This condition creates multiple names for the same device, which can lead to data corruption.

Facility: STACONFIG, Standalone Configure Process
Explanation: The value of the SYSGEN tape allocation class parameter differs between the local node and the specified remote node.
User Action: Set the TAPE_ALLOCLASS parameter to the same nonzero value on both nodes.

TAPEALLOZERF, This system and/or the processor on SCSI bus
'device-name', ID 'slot-number', has a zero TAPE_ALLOCLASS value. This condition creates multiple names for the same device, which can lead to data corruption.

Facility: STACONFIG, Standalone Configure Process
Explanation: The local node, remote node, or both nodes have the SYSGEN tape allocation class parameter set to zero.
User Action: Set the TAPE_ALLOCLASS parameter to the same nonzero value for both nodes.

TAPECLASS, fatal error detected by Tape Class driver (TUDRIVER)

TAPEFULL, 'save-set-spec' is full

Facility: BACKUP, Backup Utility
Explanation: The specified volume contains file data that extends past the end-of-tape reflective strip, indicating that no space is available for more data.
User Action: Retry the operation using another volume.

TASKERROR, security server experienced a TASKING_ERROR exception

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

TIMORDSCB, Timeout attempting to read boot device SCB

Facility: SHADOW, Volume Shadowing Software
Explanation: Shadowing was not able to read the boot device storage control block (SCB) during boot time for the number of seconds specified in the SHADOW_SYS_TMO system parameter.
User Action: Verify that the boot device is ready and that the volume is properly loaded on the device.

TIMOUPDSCB, Timeout attempting to update system disk member SCBs

Facility: SHADOW, Volume Shadowing Software
Explanation: Shadowing was not able to update system disk member storage control blocks (SCBs) during boot time for the number of seconds specified in the SHADOW_SYS_TMO system parameter.
User Action: Verify that the shadow set system disk devices are ready and that the volume is properly loaded on each device.

TIPCUFLOW, NETACP - transmit count underflow

TMSCPLDERR, TMSCP server must be loaded by setting SYSGEN parameter TMSCP_LOAD

Facility: SYSGEN, System Generation Utility
Explanation: An attempt was made to load the TMSCP server using the TMSCP command in SYSGEN.
User Action: Always load the TMSCP server by setting the SYSGEN parameter TMSCP_LOAD to 1. This action loads the server, which services all locally connected MSCP type tape drives during SYSBOOT.

TMSCPSERV, Fatal error detected by TMSCP server

Facility: BUGCHECK, System Bugcheck
Explanation: The TMSCP server encountered an irrecoverable error.
User Action: Keep a copy of the crash dump and contact a Digital support representative.

TOOMANYSUB, SPAWN failed, too many subprocesses. DIRECT mode used.

Facility: STDRV, System Startup Driver
Explanation: The startup database directed the startup driver to run too many spawned subprocesses. STDRV ran one or more of the processes in the main startup procedure using DIRECT mode. System startup should complete normally.
User Action: Use SYSMAN's STARTUP commands to display and modify the startup database to spawn fewer subprocesses.

TOO_MNY, too many of this device type

Facility: SYSGEN, System Generation Utility
Explanation: The SYSGEN command CONFIGURE specifies too many controllers for the given device type.
User Action: Reenter the command with a valid number of controllers.

TSRVALLOAD, the TMSCP server is already loaded

Facility: SYSGEN, System Generation Utility
Explanation: An attempt was made to load the TMSCP server using the TMSCP command in SYSGEN. The TMSCP server has already been loaded in the recommended way by setting the SYSGEN parameter TMSCP_LOAD to 1. This action loads the server, which services all locally connected MSCP-type tape drives during SYSBOOT.
User Action: None.

TWICE, device 'controller-name' - count changed from 'count' to 'count'

Facility: SYSGEN, System Generation Utility
Explanation: A controller name has been specified twice for the CONFIGURE command.
User Action: Verify the value you intend to use.

UBMAPEXCED, UNIBUS map register allocation exceeded

UDAPORT, fatal error detected by UDA port driver (PUDRIVER)

UNABLCREVA, unable to create virtual address space

UNDEFLINK, undefined link

Facility: LAT, LAT Facility
Explanation: A link was specified that does not exist on the local node.
User Action: Use the LATCP command SHOW LINK to see which links exist on the local node.

Unexpected Interrupt - CNF/PMC/PSR '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.

Unexpected Interrupt - NODESTS/CASR(H)/(L) 'xxxxxxxx/xxxxxxxx/xxxxxxxx'
Facility: Cluster Port Driver
Explanation: The adapter has issued a hardware interrupt when the driver is not prepared to handle one. This indicates that the driver and adapter are no longer synchronized. 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 system, and contact a Digital support representative.

UNEXPIOINT, unexpected I/O adapter interrupt

UNEXPIRED, its expiration date is in the future

Facility: BACKUP, Backup Utility
Explanation: The Backup utility tried to mount a tape that cannot be initialized because it has an expiration date in the future.
User Action: Mount another tape that can be initialized, or remove the /REWIND qualifier from the BACKUP command.

UNKADAP, unknown adapter type encountered

Facility: SYSGEN, System Generation Utility
Explanation: An internal error occurred when SYSGEN tried to parse an adapter name.
User Action: Check the command line for errors and reenter.

UNKCPU, unknown CPU type encountered

Facility: SYSGEN, System Generation Utility
Explanation: An unknown CPU type was specified with the SYSGEN command SHOW/ADAPTER.
User Action: Reenter the command, specifying a valid CPU type.

UNKDEV, unknown device type

Facility: MOUNT, Mount Utility
Explanation: The device type is unknown or invalid.
User Action: Correct the device name (or logical name if a logical name is specified) and reenter the command.

UNKNPRQ, unknown Inter-processor Request Message

UNKRSTRT, unknown restart code

UNL_PEN, exec image unload is pending

Facility: LOADER, Executive Image Loader
Explanation: A call was made to LDR$UNLOAD_IMAGE to unload an executive image that is in use. The image is marked to be unloaded later.
User Action: None.

UNLOCKERR, failed to unlock volume

Facility: RBLD, REBUILD Command (Mount Utility)
Explanation: An error occurred while trying to unlock the volume.
User Action: Take action based on the accompanying message.

Unrecognized SCA Packet - 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. If the virtual circuit is already closed, the port driver inhibits datagram reception from the remote port.
User Action: Save the error log file that contains this entry and the crash dumps from both the local and remote systems. Then contact a Digital support representative.

UNRELVOL, volume is not part of volume set being mounted

Facility: MOUNT, Mount Utility
Explanation: A disk volume that is not part of a volume set was specified in a MOUNT command that specified other volumes. Only volumes belonging to the same volume set can be mounted using the same MOUNT command.
User Action: Mount the specified volume using a separate command, or specify the /BIND qualifier in the MOUNT command.

UNSUPRTCPU, unsupported CPU

UNXINTEXC, unexpected interrupt or exception

UNXSIGNAL, unexpected signal name in ACP

USERAUTH, error accessing authorization record

Facility: LOGIN, Login Procedure
Explanation: The login processor cannot read the user record for this user.
User Action: Try the operation again later.

USEREXC, you are at maximum allowed processes for your user name

Facility: LOGIN, Login Procedure
Explanation: No more processes can be logged in under this user name. The EXQUOTA message simultaneously displays to the system manager.
User Action: Wait until another process using this user name has logged out, and retry.

Contents

Index

privacy and legal statement

6023PRO_018.HTML