Updated: 11 December 1998

OpenVMS System Messages: Companion Guide for Help Message Users

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.

• 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

SYSPWDTMO, system password timeout

SYSTRMERR, SYSINIT-terminal IO error

SYSVERCHK, system version mismatch - function aborted

SYSVERDIF, system version mismatch - reassemble and relink driver

SZTOOBIG, record size or block size greater than 65534

Copyright © Compaq Computer Corporation 1998. All rights reserved. Legal

6023PRO_018.HTML