OpenVMS System Messages: Companion Guide for Help Message Users

Updated: 11 December 1998

OpenVMS System Messages: Companion Guide for Help Message Users

Contents

Index

SAMEDEVICE, repeated reference to device 'device'

Facility: BACKUP, Backup Utility
Explanation: The specified device appeared more than once in the BACKUP command. A device may not appear more than once in either a list of input or output devices. Also, a device may not appear as both an input device and an output device. This occurs only in physical or image backup operations when the output is not a save set. The main purpose is to prevent the accidental initialization of the input disk to be saved. This situation will arise if the output specifier of the BACKUP command does not provide a device specification (or the device specification is syntactically incorrect) and the input device is the user's default device. In this case, the output device defaults to the current default device (the input device).
User Action: Check the command line to ensure that the device specifications are syntactically correct and that no device appears (explicitly or implicitly) more than once. Reenter the BACKUP command.

SAVSETCLU, save-set disk cluster factor must be 1

Facility: BACKUP, Backup Utility
Explanation: The specified volume has a volume cluster factor larger than 1. The volume cannot be used as a save-set disk.
User Action: Retry the operation using a properly initialized Files--11 On-Disk Structure Level 2 volume.

SAVSETNAM, save-set name must be in first list element

Facility: BACKUP, Backup Utility
Explanation: In a save-set specifier, the first or only element of a list must contain a file name. The following list elements, if any, must contain only a device name.
User Action: Reenter the command, with the save-set name in the first element of the list.

SBIAERROR, fatal SBIA 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.

SCANDEADPT, scan dead page table error

SCBRDERR, SCB physical read error halt

SCSSYSTEMID has NOT been set to a nonzero value
Facility: Cluster Port Driver
Explanation: The port driver will not attempt to start the port.
User Action: Modify the SCSSYSTEMID SYSGEN parameter and reboot the system. See the appropriate OpenVMS installation guide.

SECREFNEG, section reference count went negative

SERVE_ERR, error serving device DD'cnn': R0 status = 'nnnnnnnn'

Facility: STACONFIG, Standalone Configure Process
Explanation: A newly discovered device that fits all the serving parameters could not be served. If the value in the R0 status is 00000084, the device was not served because the server is not loaded.
User Action: Check to see that the MSCP server has been loaded properly. Use the SHOW DEVICE/SERVED command or examine SCS$GL_MSCP. This global address should be a valid system space address. If the R0 status is other than 84, get the corresponding message (using EXIT nn) and find out what is wrong with the device.

SERVERNOTACTIVE, security server is not active

Facility: SECSRV, Security Server
Explanation: A request was made of the security server but the server is not currently running.
User Action: Start the security server and retry the request.

SERVERRESTART, security server restarting

Facility: SECSRV, Security Server
Explanation: As requested, the security server is restarting.
User Action: None.

SERVERSHUTDOWN, security server shutting down

Facility: SECSRV, Security Server
Explanation: As requested, the security server is shutting down.
User Action: None required. If you wish to start a security server, use the DCL command SET SERVER SECURITY/START.

SERVERTERMINATED, an error caused the security server to terminate

Facility: SECSRV, Security Server
Explanation: An error caused the security server to perform cleanup and terminate break-in detection, evasion processing, and proxy processing.
User Action: Use the DCL command SET SERVER SECURITY/START to restart the security server. If this condition persists, contact a DIGITAL support representative.

SETLIMIT, too many volumes in volume set

Facility: MOUNT, Mount Utility
Explanation: The maximum permissible number of volumes in a volume set (255) has been reached.
User Action: Find the other volumes in the set and use them first.

SETMAX, value set to maximum for parameter 'name'

Facility: SYSBOOT, System Bootstrap Facility
Facility: SYSGEN, System Generation Utility
Explanation: The value entered in a SET command exceeds the maximum allowed.
User Action: Verify the intended number.

SETMIN, value set to minimum for parameter 'name'

Facility: SYSBOOT, System Bootstrap Facility
Facility: SYSGEN, System Generation Utility
Explanation: The value entered in a SET command is less than the minimum allowed.
User Action: Verify the intended number.

SHADBOOTFAIL, SHADOWING failed to boot from system disk shadow set

Facility: BUGCHECK, System Bugcheck
Explanation: A system disk shadow set is in an inconsistent state during booting. Any of the following conditions can cause this error:

There is a failure to allocate memory.
One or more critical devices is inaccessible.
The boot device is the target of a full copy operation.
The boot device is not a source member of the existing shadow set.
A member of the system disk shadow set is write-locked.

User Action: Try any of these user actions, as appropriate:

If the boot device is the target of a full copy operation or is not a source member of the existing shadow set, change the device named in the VMB (primary bootstrap) to be a source member and reboot the node.
If the boot device is a source member of the existing shadow set, check the booting device's connections to all other shadow set members.
If all device and system connections are functioning, check the system parameter settings for inappropriate memory configurations.

SHADDETINCON, SHADOWING detects inconsistent state

Facility: BUGCHECK, System Bugcheck
Explanation: The volume shadowing software reached an irrecoverable or inconsistent state because a shadow set failed an internal consistency check.
User Action: Note the conditions leading to the error and contact a DIGITAL support representative. If the system is configured to produce a memory dump, retain the dump file.

SHADOWFAIL, failed to create (or add to) the shadow set

Facility: MOUNT, Mount Utility
Explanation: Either the shadow set cannot be created, or proposed shadow set members cannot be added to the shadow set.
User Action: Examine the status code of the failed operation and correct the error.

SHADOWLBS, clearing low-order bit in SHADOWING; function no longer supported

Facility: SYSBOOT, System Bootstrap Facility
Explanation: The low-order bit in the SYSGEN parameter SHADOWING was set at boot time. This bit has been cleared and the system was booted from the physical device named to VMB register 3 (R3). Unless you have migrated to phase II volume shadowing, no shadow sets will be created.
User Action: None.

SHADSCB, cannot read valid shadow set storage control block

Facility: MOUNT, Mount Utility
Explanation: MOUNT cannot read a valid copy of the storage control block for a shadow set virtual unit. This condition can indicate frequent membership changes in the shadow set.
User Action: Find and correct any problems that may create instability in the shadow set (for example, malfunctioning devices or communications problems among the nodes in the cluster).

SHADSCB, failed to read stable shadow set storage control block on relative volume 'volume-id'

Facility: RBLD, REBUILD Command (Mount Utility)
Explanation: The rebuild operation encountered numerous errors while reading the storage control block of the specified volume.
User Action: Check the hardware and retry the program. Contact a Digital support representative if the failures continue.

SHADUNSTABLE, shadow set membership is unstable

Facility: MOUNT, Mount Utility
Explanation: MOUNT cannot determine the current master member of the shadow set. This problem can occur if the shadow set is undergoing frequent changes in membership.
User Action: Find and correct any problems that may create instability in the shadow set (for example, malfunctioning devices or communications problems among the nodes in the cluster).

SHADZEROMBR, SHADOWING detects a zero member set

Facility: BUGCHECK, System Bugcheck
Explanation: Due to a synchronization problem, shadowing has detected a mounted virtual unit with no source members. This is an illegal state; to preserve data integrity, shadowing has crashed the node on which this condition was detected.
User Action: Document and report any events that occurred on other nodes in the cluster that also have the shadow set mounted. Reboot the node that crashed and remount all shadow sets.

SHASINGMBR, single member system shadow set formed

Facility: SYSINIT, System Initialization
Explanation: The system disk shadow set was in an inconsistent state during booting. The system continued booting despite the inconsistency, but the shadow set membership has changed to form a single-member shadow set consisting of only the boot device.
User Action: Evaluate the shadow set membership and perhaps add more disks.

SHDWCOPYREQ, shadow copy required

Facility: MOUNT, Mount Utility
Explanation: A shadow set member requires a shadow copy operation, but you specified that copy operations are not allowed.
User Action: Verify that the volume can be initialized (that is, ascertain that it contains no useful data), and reenter the command to allow shadow copy operations.

SHDWINCVOL, shadow set member device contains the wrong volume

Facility: MOUNT, Mount Utility
Explanation: The proposed shadow set member device contains a different volume than expected. Rather than be added to the shadow set and be initialized, the volume was not added to the shadow set.
User Action: Examine the volume to verify that it can be initialized (that is, ascertain that it contains no useful data), and reenter the command to add this volume to the shadow set.

SHDWMEMCOPY, 'ddcu:' added to the shadow set with a copy operation

Facility: MOUNT, Mount Utility
Explanation: The specified device is being added to the shadow set by a copy operation. When the copy operation is complete, the device will be a full shadow set member.
User Action: None.

SHDWMEMERGE, 'device-name' added to the shadow set with a merge operation

Facility: MOUNT, Mount Utility
Explanation: The specified device was successfully added to the shadow set. A merge operation was initiated, making this device a source member with merge semantics. The device is identical to the other members of the set except for possible incomplete write operations, for which the shadowing software will check.
User Action: None.

SHDWMEMFAIL, 'ddcu:' failed as a member of the shadow set

Facility: MOUNT, Mount Utility
Explanation: The specified device cannot be made a shadow set member.
User Action: Examine the accompanying failure status code, then correct the error and reenter the command.

SHDWMEMSUCC, 'ddcu:' is now a valid member of the shadow set

Facility: MOUNT, Mount Utility
Explanation: The specified device is now a full shadow set member.
User Action: None.

SHELVED, 'file-name' data not copied, file is shelved

Facility: BACKUP, Backup Utility
Explanation: An image mode save operation was performed on a file that is currently shelved. Therefore, only the file header was saved; no data was transferred to the save set.
User Action: None required. However, if you want to create an image backup that includes the contents of the specified file, use the UNSHELVE command to bring the file back on line before performing the image mode backup.

SHLVSTATE, 'file-name' has changed shelved state

Facility: BACKUP, Backup Utility
Explanation: During a compare or verify operation, the Backup utility detected that the data contents of the specified file have been shelved and the file contents are unavailable for verification. This condition can occur when shelving activity on the volume causes the file state to change from online to shelved.
User Action: Specify the /AUTOUNSHELVE qualifier on the SET PROCESS command to change the process shelving default to autounshelve, or disable shelving activity during the backup operation.

SHORTBLOCK, save-set block too short

Facility: BACKUP, Backup Utility
Explanation: The Backup utility encountered a physical block shorter than the value recorded for the save set. Data in the save set is corrupt.
User Action: None. Save-set data has been lost.

SHRCNTNEG, PFN share count negative

SLOWWS, performance adversely impacted by small working set size 'size'

Facility: BACKUP, Backup Utility
Explanation: The UAF working set quotas are too low for the Backup utility to operate efficiently.
User Action: The system manager should ensure that the SYSGEN and UAF parameters for all accounts that perform backup operations are at the recommended settings.

SOFTRERRS, 'n' recoverable media errors occurred reading 'save-set-spec'

Facility: BACKUP, Backup Utility
Explanation: The Backup utility successfully recovered from read errors in the specified save set the specified number of times by rereading the blocks in error.
User Action: None. However, if the number of errors appears excessive, consider retiring the save-set media when convenient.

Software is Closing Virtual Circuit - REMOTE PORT 'xxx'
Facility: Cluster Port Driver
Explanation: The port driver closed the virtual circuit to the remote port.
User Action: Check error log entries for the cause of the virtual circuit closure. Faulty transmission or reception on both paths, for example, causes this error and may be detected from the one or two previous error log entries noting bad paths to this remote node.

Software Shutting Down Port
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: Check other error log entries for the possible cause of the port reinitialization failure.

SOFTWERRS, 'n' recoverable media errors occurred writing 'save-set-spec'

Facility: BACKUP, Backup Utility
Explanation: The Backup utility recovered successfully from uncorrectable write errors in the specified save set the specified number of times by rewriting the blocks in error.
User Action: None. However, if the number of errors appears excessive, consider retiring the save-set media when convenient.

SPECIFY, specify option ('valid-options') BACKUP>

Facility: BACKUP, Backup Utility
Explanation: This message is returned to the operator. It indicates that the Backup utility encountered a recoverable error.
User Action: The operator must select one of the options listed in the message. The options listed depend upon the recoverable error that was encountered. Possible options are: QUIT, CONTINUE, RESTART, NEW, OVERWRITE and USE. If the QUIT option is selected, the Backup utility will terminate. If the CONTINUE option is selected, the Backup utility will ignore the error and continue processing. If the RESTART option is selected, the Backup utility will restart the operation at the beginning of the current volume. If the NEW option is selected, the Backup utility will dismount the current tape volume and request that a new tape volume be mounted. If the OVERWRITE option is selected, the Backup utility will overwrite the currently loaded volume label. If the USE option is selected, the Backup utility will use the currently loaded volume label.

SPECLBL, the label was not specified
specify label (up to 6 characters)

Facility: BACKUP, Backup Utility
Explanation: This message can occur when no operator assistance is specified. Exact label checking is in effect, but the command line did not specify enough labels to cover the current volume.
User Action: Specify a volume label to be used in exact volume order checking.

SPF_TOBIG, second pass fixup data exceeds table size

Facility: LOADER, Executive Image Loader
Explanation: The loader's internal tables cannot accommodate all of the executive image fixups that must be postponed to later in the bootstrap operation.
User Action: Contact a DIGITAL support representative.

SPTFULL, system page table is full

Facility: SYSGEN, System Generation Utility
Explanation: There is no space available in the system page table to allocate a system page for the device (requested by DPT$_MSVP in the driver prologue table).
User Action: Reboot the system, stopping in SYSBOOT, and increase the value of the system page table parameter (SPTREQ).

SRCMBRADD, source member added to virtual unit

Facility: MOUNT, Mount Utility
Explanation: A volume has been added as a valid source member to an already mounted shadow set. This action occurs only when MOUNT determines that the new member's storage control block exactly matches the storage control block of the mounted virtual unit. This would be the case if you add a new shadow set member that was created by executing a BACKUP command with the /PHYSICAL qualifier from the virtual unit. This action does not occur during normal use of shadow sets.
User Action: If you receive this message after intentionally adding a member with a matching storage control block, no action is required. However, if this message is unexpected, the data on the device could be corrupted. In that case, you may want to dismount the new member.

SRVALLOAD, the MSCP server is already loaded

Facility: SYSGEN, System Generation Utility
Explanation: An attempt was made to load the MSCP server using the MSCP command in SYSGEN, and the server is already loaded using the SYSGEN parameter MSCP_LOAD. The MSCP server has been loaded the recommended way. This warning is printed to remind you that this command is obsolete.
User Action: If this warning is printed because the MSCP command is still in a startup command procedure, this command should be edited out of the procedure.

SSATEOV, this save-set was started in the end-of-tape region

Facility: BACKUP, Backup Utility
Explanation: The current save set was started in the end-of-tape region. No data was written, only ANSI labels.
User Action: None.

SSCHANGE, unexpected end of save set on 'device-name'

Facility: BACKUP, Backup Utility
Explanation: Internal consistency checks have detected that the current save set has ended, and the Backup utility is reading a new save set.
User Action: You will be prompted to continue or quit. If you choose to continue, the Backup utility will continue reading the new save set.

SSNAMTRUNC, save-set name too long, truncated to 'save-set-name'

Facility: BACKUP, Backup Utility
Explanation: The specified label exceeds the maximum length and was truncated to the legal limit of 6 characters.
User Action: Specify a volume label with 6 or fewer characters.

SSRVEXCEPT, unexpected system service exception

STARTDELETE, starting file deletion pass

Facility: BACKUP, Backup Utility
Explanation: The Backup utility is beginning to delete files in response to the /DELETE qualifier.
User Action: None.

Starting memory dump...
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS operating system reached an irrecoverable or inconsistent situation and is beginning a bugcheck sequence. If the system is configured to write a memory dump, messages similar to the following messages might accompany the dump:

Header and error log buffers dumped...
SPT & GPT dumped...
System space (S0) dumped...
Global pages dumped...
'process-name' dumped...
'process-name' dumped...
**** Memory dump complete...

These messages give information about the progress of the writing of that dump. These messages appear if the SYSGEN parameter DUMPSTYLE is set so that a selective dump (that is, a dump of selected portions of system space and process address space in virtual memory) is written.

A selective dump is similar to a complete dump when writing the dump header and system error log buffers. Following these items, it differs from the complete dump by immediately writing out the system and global page tables. The page tables and system space are the minimum content needed to analyze a crash dump; configuring your dump file so that this minimum cannot be dumped causes the dump to be useless.

The global pages written during the dump are written separately from the processes that might reference them. This allows a single copy of each global page to exist in the dump. Processes are selected to have their P0 and P1 spaces dumped in the following order: current processes (if any) on the CPU that initiated the bugcheck, special system processes, current processes (if any) on other CPUs, and any other processes. A message giving the name of the process follows the writing of the dump for that process if it completed successfully.

Global and process pages are optional when writing a dump because the dump may still yield useful information if they are not present. However, Digital recommends that you use a dump file at least as large as the one created by AUTOGEN. If the dump file is not large enough to hold all process and page files, the dump is still considered to have finished normally.
User Action: None. However, if you wish, save a copy of the dump file and contact a DIGITAL support representative.

Starting memory dump...Memory dump complete
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS operating system reached an irrecoverable or inconsistent situation and is beginning a bugcheck sequence. If the system is configured to write a memory dump, these messages accompany the dump. No other messages appear if the SYSGEN parameter DUMPSTYLE is set so that a full dump (that is, a dump of all physical memory) is written.
User Action: None. However, if you wish, save a copy of the dump file and contact a DIGITAL support representative.

STARTRECORD, starting backup date recording pass

Facility: BACKUP, Backup Utility
Explanation: The Backup utility completed a save or copy operation and is beginning to update backup dates in response to the /RECORD qualifier.
User Action: If the /SINCE=BACKUP or /BEFORE=BACKUP qualifier is used, note that data will be lost if the operation is restarted using the same output media. If it is necessary to restart the operation because of a system failure, use another volume.

STARTUP, VMS startup begun at 'dd-mmm-yyyy hh:mm:ss.ss'

Facility: STDRV, System Startup Driver
Explanation: The OpenVMS operating system has begun executing the system startup driver, which is used to start up individual OpenVMS system processes and to start the OpenVMS operating system after a reboot. This message is informational.
User Action: None.

STARTVERIFY, starting verification pass

Facility: BACKUP, Backup Utility
Explanation: The Backup utility completed the operation on the current volume and is beginning to verify data in response to the /VERIFY qualifier.
User Action: None.

STASMALLMEM, small memory system. Booted device must stay on line during operation.

Facility: BACKUP, Backup Utility
Explanation: The amount of system memory is too small to lock all of standalone backup into the working set.
User Action: Ensure that the device from which standalone backup booted stays on line during the entire backup operation.

STATENTSVD, software state not saved during powerfail

Facility: BUGCHECK, System Bugcheck
Explanation: Before power was lost, the volatile software state of the processor was not completely saved in memory. 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: Check all processor mechanisms related to the detection of a power failure. Be sure that no peripheral adapter recognizes an impending power failure before the processor does because, in that case, the processor would be prevented from handling the failing power condition.

STRNOTWCB, data structure not window block

STRTOOLNG, specified string is too long

Facility: SYSBOOT, System Bootstrap Facility
Facility: SYSGEN, System Generation Utility
Explanation: A string specified in a SET command is longer than the maximum length for that parameter.
User Action: Correct and reenter the command.

STRUCLEV, inconsistent structure level on 'device-name'

Facility: BACKUP, Backup Utility
Explanation: The Files--11 structure level of the specified volume is different from other volumes in the same list of devices. The volume must not be part of the same volume set.
User Action: Locate and mount the correct volume.

SWAPAGINS, all additional page or swap files already installed

Facility: SYSGEN, System Generation Utility
Explanation: Two second-page or swap files were installed.
User Action: If it is necessary to change the page or swap file, reboot and install the correct file.

SWAPWSLE, swap working set list entries error

SYNTAX, syntax error

Facility: SYSBOOT, System Bootstrap Facility
Explanation: A syntax error is detected.
User Action: Reenter the command with the correct syntax.

SYNTAX, syntax error: 'string'

Facility: SYSGEN, System Generation Utility
Explanation: A syntax error is detected. The 'string' part of the message displays the nonparsed input.
User Action: Reenter the command with the correct syntax.

SYSADJWSL, system service adjust working set limit error

Contents

Index

Legal

 
6023PRO_016.HTML