Digital PDFs

AA-PV5TA-TK

1993

193 pages

Original

8.9MB

Document:	AA-PV5TA-TK OpenVMS AXP 1.5 VAX 6.0 System Messages Companion Guide for Help Message Users 199305
Order Number:	AA-PV5TA-TK
Revision:	0
Pages:	193
Original Filename:

OCR Text

OpenVMS System Messages:
.
Companion Guide for Help Message Users

Part Number: AA- PVSTA- TK

Open VMS System Messages:

Companion Guide for Help
Message Users
Order Number: AA-PVSTA-TK
May 1993

The Open VMS System Messages: Companion Guide for Help Message
Users describes how to use the online Help Message utility to obtain
online message descriptions. This manual also contains descriptions of
messages that can display on the operator's console when the system
and the Help Message utility are not fully functional.

Revision/Update Information:

This manual supersedes the Open VMS
System Messages: Companion Guide
for Help Message Users for OpenVMS
AXP Version 1.0.

Software Version:

OpenVMS AXP Version 1.5
OpenVMS VAX Version 6.0

Digital Equipment Corporation
Maynard, Massachusetts

May 1993

The information in this document is subject to change without notice and should not be construed
as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no
responsibility for any errors that may appear in this document.
The software described in this document is furnished under a license and may be used or copied
only in accordance with the terms of such license.
No responsibility is assumed for the use or reliability of software on equipment that is not supplied
by Digital Equipment Corporation or its affiliated companies.

© Digital Equipment Corporation 1993.
All Rights Reserved.
The postpaid Reader's Comments forms at the end of this document request your critical evaluation
to assist in preparing future documentation.
The following are trademarks of Digital Equipment Corporation: Alpha AXP, AXP, BI, Bookreader,
CI, CMI, DEC, DECnet, DECterm, Digital, HSC, LAT, MSCP, OpenVMS, SBI, TU, UDA, UNIBUS,
VAX, VAXcluster, VAX DOCUMENT, VAXport, VAX-11, VAX-11 RSX, VAX-11/750, VAX-11/780,
VAX 8200, VAX 8300, VMS, VMScluster, the AXP logo, and the DIGITAL logo.
All other trademarks and registered trademarks are the property of their respective holders.
ZK6023

This document was prepared using VAX DOCUMENT, Version 2.1.

Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Part I Tutorial Information
1 OpenVMS System Messages
1.1

1.1.1
1.2
1.3
1.4
1.5
1.5.1
1.5.2
1.5.3
1.5.4

Format of System Messages ................................... .
Messages with Different Formats ........................... .
System Reporting of Messages ................................. .
Retrieving a System Message .................................. .
Exception Conditions ........................................ .
Recovery Procedures ........................................ .
Recovering from Command Entry Errors ...................... .
Responding to Unavailable Resources ........................ .
Recovering from Programming Errors ........................ .
Reporting System Software or Hardware Errors ................ .

1-1

1-2
1-3
1-3
1-4
1-4
1-4
1-5
1-5
1-5

2 Help Message Utility (MSGHLP)
2.1
2.2

2.3
2.4
2.5
2.5.1
2.5.2
2.6
2.6.1
2.6.2

2.6.3
2.6.4

Features of Help Message .................................... .
HELP/MESSAGE Command and Qualifiers ....................... .
HELP/MESSAGE ........................................... .
Tips for Using the /FACILITY Qualifier .......................... .
Using SET MESSAGE to Access Uninstalled Messages ............. .
Customizing the Help Message Database ........................ .
Creating a .MSGHLP File ................................. .
Defining a Search Path in Your Login File ..................... .
Modifying the Help Message Database .......................... .
Adding Messages to the Database ........................... .
Deleting Messages from the Database ........................ .
Changing User-Supplied Data .............................. .
Changing Digital-Supplied Messages Documentation ............ .

2-1

2-3
2-4
2-7
2-7
2-8
2-8
2-9
2-10
2-10
2-11
2-12
2-13

Part II Message Descriptions
Index

iii

Tables
OpenVMS Facilities and Associated Documentation . . . . . . . . . . . . . .

Preface
Intended Audience
The Open VMS System Messages: Companion Guide for Help Message Users
is intended for everyone who uses the Help Message utility to access online
descriptions of system messages.
This manual also provides hardcopy descriptions ofmessages that can display on
the operator's console when the operating system and the Help Message utility
are not operational.

Document Structure
This manual consists of two parts:
•

Part I provides tutorial information about OpenVMS system messages and
explains how to access messages documentation:
Chapter 1 describes the standard message format, system reporting of
messages, and basic recovery procedures.
Chapter 2 explains how to access message descriptions using the online
Help Message utility.

•

Part II alphabetically lists and describes messages for these OpenVMS
facilities:
BACKUP
BUGCHECK
INSTALL
I OGEN
LAVC
LOGIN
MOUNT
STDRV
SYS BOOT
SYS GEN
SYSINIT
VAXport
Some messages from the LAT and SYSTEM facilities are also included.

Associated Documents
The Help Message database supplied with the OpenVMS operating system
documents messages for the facilities listed in Table 1. Where applicable, the
table cites one or more associated documents that contain information about the
facility.
Table 1 OpenVMS Facilities and Associated Documentation
Facility Code

Facility Name

Reference Manual

ACC

Accounting Utility

Open VMS System Management Utilities
Reference Manual

ACLEDIT

Access Control List Editor

Open VMS System Management Utilities
Reference Manual

AMAC

MACR0-32 Compiler for OpenVMS AXP

Migrating to an Open VMS AXP System:
Porting VAX MACRO Code
VAX MACRO and Instruction Set
Reference Manual

ANALDISK

Analyze/Disk_Structure Utility

Open VMS System Management Utilities
Reference Manual

AUDSRV

Audit Server

Open VMS VAX Guide to System Security
Open VMS AXP Guide to System Security

BACKUP

Backup Utility

Open VMS System Management Utilities
Reference Manual

BAD

Bad Block Locator Utility

Open VMS Bad Block Locator Utility
Manual

BUGCHECK

System Bugcheck

Open VMS AXP System Dump Analyzer
Utility Manual

CAF

Cluster Authorization File Service

VMScluster Systems for Open VMS

CDA

Compound Document Architecture

CDA Reference Manual

CDU

Command Definition Utility

Open VMS Command Definition,
Librarian, and Message Utilities Manual

CLI

Command Language Interpreter (DCL)

Open VMS DCL Dictionary

CMA

DECthreads (Digital's Multithreading
Run-Time Library)

Guide to DECthreads

CONV

Convert and Convert/Reclaim Utilities

Open VMS Record Management Utilities
Reference Manual

CREF

Cross-Reference Utility

Open VMS RTL Library (LIB$) Manual
Open VMS Programming Environment
Manual

DCL

DIGITAL Command Language

Open VMS DCL Dictionary

DCX

Data Compression/Expansion Facility

Open VMS Utility Routines Manual

DDTM

DECdtm Services

Open VMS System Manager's Manual

DIFF

DIFFERENCES Command

Open VMS DCL Dictionary

DISM

DISMOUNT Command

Open VMS DCL Dictionary

DNS

Digital Distributed Name Service
(DECdns)

DECnet for Open VMS Networking
Manual
(continued on next page)

Table 1 (Cont.) OpenVMS Facilities and Associated Documentation
Facility Code

Facility Name

Reference Manual

DSR

DIGITAL Standard Runoff

Open VMS DIGITAL Standard Runoff
Reference Manual

DTK

DECtalk Facility

Open VMS RTL DECtalk (DTK$) Manual

DTR

DECnet Test Receiver

DECnet for Open VMS Network
Management Utilities

DTS

DECnet Test Sender

DECnet for Open VMS Network
Management Utilities

DUMP

DUMP Command

Open VMS DCL Dictionary

EDF

FDL Editor

Open VMS Record Management Utilities
Reference Manual

EDT Editor

Open VMS EDT Reference Manual

ERF

Error Log Utility

Open VMS System Management Utilities
Reference Manual

EVL

Event Logger

DECnet for Open VMS Networking
Manual

EXCHANGE

Exchange Utility

Open VMS Exchange Utility Manual

FDL

FDL Utilities

Open VMS Record Management Utilities
Reference Manual

IMGACT

Image Activator

Open VMS Linker Utility Manual

INIT

INITIALIZE Command

Open VMS DCL Dictionary

INPSMB

Input Symbiont

OpenVMS System Manager's Manual

INSTALL

Install Utility

Open VMS System Management Utilities
Reference Manual

IO GEN

Open VMS System Management Utilities
Reference Manual

JBC

Job Controller

Open VMS System Services Reference
Manual

LAT

LAT Facility

Open VMS System Management Utilities
Reference Manual

LAVC

Local Area VMScluster

VMScluster Systems for Open VMS

LBR

Librarian Routines

Open VMS Command Definition,
Librarian, and Message Utilities Manual

LIB

Library Facility

Open VMS RTL Library (LIB$) Manual

LIBRAR

LIBRARY Command

Open VMS Command Definition,
Librarian, and Message Utilities Manual

LICENSE

License Management Utility

Open VMS License Management Utility
Manual

LINK

Linker Utility

Open VMS Linker Utility Manual

LMCP

Log Manager Control Program

Open VMS System Management Utilities
Reference Manual

Open VMS DCL Dictionary

MACRO

VAX MACRO Assembler

VAX MACRO and Instruction Set
Reference Manual

(continued on next page)

vii

Table 1 (Cont.) OpenVMS Facilities and Associated Documentation
Facility Code

Facility Name

Reference Manual

MAIL

Mail Utility

Open VMS User's Manual or MAIL Help

MESSAGE

Message Utility

Open VMS Command Definition,
Librarian, and Message Utilities Manual

MOM -

Maintenance Operation Module

DECnet for Open VMS Networkirig
Manual

MONITOR

Monitor Utility

Open VMS System Management Utilities
Reference Manual

MOUNT

Mount Utility

Open VMS System Management Utilities
Reference Manual

MSGHLP

Help Message Utility

Open VMS System Messages: Companion
Guide for Help Message Users
Open VMS System Manager's Manual

MTH

Mathematics Facility

Open VMS VAX RTL Mathematics
(MTH$) Manual
DPML, Digital Portable Mathematics
Library

NCP

Network Control Program

DECnet for Open VMS Network
Management Utilities

NICONFIG

Ethernet Configurator Module

DECnet for Open VMS Networking
Manual

OPCOM

Operator Communication Process

Open VMS System Manager's Manual

OTS

General Purpose Facility

Open VMS RTL General Purpose (OTS$)
Manual

PATCH

Patch Utility

Open VMS VAX Patch Utility Manual

PPL

Parallel Processing Facility

Open VMS RTL Parallel Processing
(PPL$) Manual

PRINT Command

Open VMS DCL Dictionary

PSM

Print Symbiont Modification Facility

Open VMS Utility Routines Manual

QMAN

Queue Manager

Open VMS System Manager's Manual

QUE MAN

Queuing Utility Commands

Open VMS System Manager's Manual

REM

Remote Terminal Support
and SET HOST Command

Open VMS DCL Dictionary

RENAME

RENAME Command

Open VMS DCL Dictionary

RMS

OpenVMS Record Management Services

Open VMS Record Management Services
Reference Manual

RUF

Recovery Unit Facility

Open VMS RMS Journaling Manual

RUN

Run Detached Utility

Open VMS DCL Dictionary

RUNOFF

DIGITAL Standard Runoff

Open VMS DIGITAL Standard Runoff
Reference Manual

SDA

System Dump Analyzer

Open VMS VAX System Dump Analyzer
Utility Manual
Open VMS AXP System Dump Analyzer
Utility Manual
(continued on next page)

viii

Table 1 (Cont.) OpenVMS Facilities and Associated Documentation
Facility Code

Facility Name

Reference Manual

SEARCH Command

Open VMS DCL Dictionary

SET

SET Command and SET Utility

Open VMS DCL Dictionary

SHOW

SHOW Command

Open VMS DCL Dictionary

SHOW

Show Cluster Utility

Open VMS System Management Utilities
Reference Manual

SMB

Symbiont/Queue-Manager Interface
Facility

Open VMS Utility Routines Manual

SMG

Screen Management Facility

Open VMS RTL Screen Management
(SMG$) Manual

SMI

System Management Integrator/Server

Open VMS System Manager's Manual

SMP

Symmetric Multiprocessing

Open VMS VAX Device Support Manual
Open VMS System Manager's Manual

SOR

Sort/Merge Utility

Open VMS DCL Dictionary

STACONFIG

Standalone Configure Process

STARTUP

SYSMAN Utility STARTUP Command

Open VMS System Manager's Manual

STD RV

System Startup Driver

Open VMS System Manager's Manual

STR

String Manipulation Facility

Open VMS RTL String Manipulation
(STR$) Manual

SUBMIT

SUBMIT Command

Open VMS DCL Dictionary

SUM

SUMSLP Batch Editing Utility

Open VMS SUMSLP Utility Manual

SYS BOOT

System Bootstrap Facility

Open VMS System Manager's Manual

SYSGEN

System Generation Utility

Open VMS System Management Utilities
Reference Manual

SYSINIT

System Initialization

Open VMS System Manager's Manual

SYS MAN

Cluster System Management Utility

Open VMS System Management Utilities
Reference Manual

SYSTEM

System Services

Open VMS System Services Reference
Manual

TIE

Translated Image Environment

DECmigrate for Open VMS AXP Version
1.0 Translating Images

TPU

DEC Text Processing Utility (DECTPU)

DEC Text Processing Utility Reference
Manual

TRACE

Traceback Facility

Open VMS Linker Utility Manual

UAF

Authorize Utility

Open VMS System Management Utilities
Reference Manual

UETP

User Environment Test Package

Open VMS AXP Version 1.5 Upgrade and
Installation Manual
Open VMS VAX version 6.0 Upgrade and
Installation Manual

VAXCLUSTER

VAXcluster and VMScluster Facilities

VMS cluster Systems for Open VMS

VAXport Driver

VMScluster Systems for Open VMS

Virtual Memory Boot

Open VMS System Manager's Manual

VMB

(continued on next page)

Table 1 (Cont.) OpenVMS Facilities and Associated Documentation
Facility Code

Facility Name

Reference Manual

VMSINSTAL

Install Procedures

Open VMS Developer's Guide to
VMSINSTAL

Conventions
In this manual, every use of OpenVMS AXP means the OpenVMS AXP operating
system, every use of OpenVMS VAX means the OpenVMS VAX. operating system,
and every use of OpenVMS means both the OpenVMS AXP operating system and
the OpenVMS VAX operating system.
The following conventions are also used in this manual:
'variable'

In message text, apostrophes delimit a variable field that is
replaced with an actual value when the message is issued.

Ctrllx

A sequence such as Ctrl/x indicates that you must hold down
the key labeled Ctrl while you press another key or a pointing
device button.

boldface text

Boldface text represents the name of an argument, an
attribute, or a reason.
Boldface text is also used to show user input in Bookreader
versions of the manual.

italic text

Italic text emphasizes important information, indicates
variables, and indicates complete titles of manuals.

UPPERCASE

Uppercase text indicates a command, the name of a routine,
the name of a file, the abbreviation for a system privilege, or
the facility code that prefixes a system message.

lowercase

In syntax statements and format descriptions, lowercase words
indicate a type of variable that you must enter.
A hyphen at the end of a command line in a coding example
indicates that the command continues on the following line.

numbers

All numbers in text are assumed to be decimal, unless
otherwise noted. Nondecimal radixes-binary, octal, or
hexadecimal-are explicitly indicated.

mouse

The term mouse refers to any pointing device, such as a mouse,
a puck, or a stylus.

Part I
Tutorial Information

1
OpenVMS System Messages
The OpenVMS operating system provides a centralized error message facility.
When you type a command at the terminal or execute an image that results in an
error, the system locates the message associated with the error and displays it.
The Help Message (MSGHLP) utility, described in Chapter 2, allows you to access
online messages documentation from the DCL prompt. If Help Message is not
installed on your system, refer to the OpenVMS System Messages and Recovery
Procedures Reference Manual and the latest Release Notes for comprehensive
OpenVMS system messages documentation.
Part II of OpenVMS System Messages: Companion Guide for Help Message
Users describes only those messages that can occur before the operating system
and Help Message are fully functional. Messages are alphabetically ordered
by message identification (see Section 1.1); exceptions to this rule are noted in
Section 1.1.1.
For users who do not have Help Message installed, Section 1.3 explains how
to retrieve a system message. This chapter also describes how to recover from
typical error conditions (see Section 1.5).

1.1 Format of System Messages
Most messages displayed by the OpenVMS operating system have the following
format:
%facility-s-identification, text
[-facility-s-identification, text]

A percent sign ( % ) prefixes the main message, and a hyphen ( - ) prefixes any
secondary messages that provide additional information about the error.
For example, the HELP/MESSAGE command calls OpenVMS Record
Management Services (RMS) to access the, database. If the database file cannot
be found, the MSGHLP facility displays a message indicating that it cannot
access the file; an RMS message and a SYSTEM message follow to indicate the
reason for the failure. In the following example, a HELP/MESSAGE command
includes the /LIBRARY qualifier to specify a private database, which MSGHLP
cannot find:
$ HELP/MESSAGE/LIBRARY=TOOLS: [MYPROJ]MYMESSAGES.MSGHLP$DATA ACCVIO
%MSGHLP-F-MDFERR, error accessing Help Message database file "TOOLS: [MYPROJ]
MYMESSAGES.MSGHLP$DATA"
-RMS-E-FNF, file not found
-SYSTEM-W-NOSUCHFILE, no such file

Any or all of the message fields can be suppressed by using the SET MESSAGE
command (see the Open VMS DCL Dictionary). The message fields are as follows:

1-1

OpenVMS System Messages
1.1 Format of System Messages
facility

An OpenVMS facility or component name.

s
A severity level indicator having one of the following values:
Code

Meaning

Description

Success

The system has successfully performed your request. In some
cases, the command processing continues after the message is
issued.

Information

The system has performed your request. The message
provides information about the process.

Warning

The command may have performed some, but not all, of
your request. The message may suggest that you verify the
command or the program output.

Error

The output or program result is incorrect, but the system may
attempt to continue execution.

Fatal (severe)

The system cannot continue to execute the request.

identification

A one-word code identifying the message-often an abbreviation of the message
text. Messages described in this manual are typically alphabetized by message
identification. (Section 1.1.1 describes some exceptions.)
text

Text of the message; usually describes the condition that produced the message.

1.1.1 Messages with Different Formats
Some messages have no identification. Others have no facility code, severity
level, or identification. In this manual, such messages are alphabetized by the
first word in the message-whether it is the facility name or the message text.
Facilities that often include the facility name, but no identification, in their
messages are:
•

System Bootstrap Facility (SYSBOOT)

•

System Initialization (SYSINIT)

For example, the following message is alphabetized under "SYSBOOT-E-Device":
SYSBOOT-E-Device names not allowed

The following facilities display some or all of their messages without facility
name, severity level, and identification:
•

System Bugcheck

•

VAXport

For example, the following VAXport message is alphabetized under
"Unrecognized":
Unrecognized SCA Packet

1-2

OpenVMS System Messages
1.2 System Reporting of Messages

1.2 System Reporting of Messages
Messages are displayed on the current device, which is identified by the logical
name SYS$0UTPUT. For an interactive user, this device is normally the
terminal; for batch job users, it is the batch job log file.
If the logical device SYS$ERROR is different from SYS$0UTPUT, the system
writes informational, warning, error, and fatal system messages to that device as
well. For example, if you execute a command procedure interactively and specify
the /OUTPUT qualifier, the system defines the file you specified as SYS$0UTPUT
for the procedure. SYS$ERROR remains assigned to your current error device.
Then, if any errors occur during the execution of the command procedure, the
error messages are displayed on your terminal and are entered in the specified
file.

1.3 Retrieving a System Message
When a DCL command, command procedure, or applications program completes
execution, it returns a condition code. The condition code indicates the execution
status of the command-whether it executed successfully or resulted in an error.
Each condition code corresponds to a system message. The command interpreter
saves the condition code as a 32-bit longword defined as the reserved global
symbol $STATUS. The condition code stored in $STATUS is a hexadecimal
number conforming to the format of an OpenVMS message code:
•

Bits 0-2 contain the severity level of the message.

•

Bits 3-15 contain the number of the corresponding message.

•

Bits 16-27 contain a number for the software component, or facility, that
generated the message.

•

Bits 28-31 contain internal control flags.

By default, the HELP/MESSAGE command accesses the value stored in $STATUS
and displays the corresponding message. The following paragraphs explain how
you can access similar information if the Help Message utility is not installed
on your system. Once you have the message, you can look up the message
description in a hardcopy manual.
The lexical function F$MESSAGE returns the message associated with a
condition code. To display the message for the current code on the default output
device, use the following command:
$ WRITE SYS$0UTPUT F$MESSAGE($STATUS)
%SYSTEM-F-POWERFAIL, power failure occurred

If you prefer to obtain the current value of $STATUS, use this command:
$ SHOW SYMBOL $STATUS
$STATUS == "%X00000364"

If you know the condition code for a message, you can use F$MESSAGE to
translate the code to its associated message. For example:
$ WRITE SYS$0UTPUT F$MESSAGE(%X00000001)
%SYSTEM-S-NORMAL, normal successful completion

You can omit leading zeros when specifying a code to F$MESSAGE. However, the
characters "%X" are necessary to identify a numeral as hexadecimal.

1-3

OpenVMS System Messages
1.4 Exception Conditions

1.4 Exception Conditions
During the execution of an image, the image can incur a fatal error known as an
exception condition. When an exception condition occurs, the system takes special
action.
If the image has not declared a condition handler, the system forces the image
to exit and displays a message indicating the reason for the exception. The
message includes the contents of these locations at the time of the exception: the
program counter (PC) and processor status (PS) on OpenVMS AXP systems, or
the program counter (PC) and processor status longword (PSL) on OpenVMS VAX
systems. This message is followed by a traceback; the system displays the status
of the call frames on the stack so that you can locate the procedure where the
condition occurred. Refer to the OpenVMS Programming Concepts Manual for a
more detailed discussion of condition handling.

1.5 Recovery Procedures
Error messages generally occur for the following reasons:
•

A command is entered incorrectly; it contains a spelling or syntax error or an
incorrect file specification. (See Section 1.5.1.)

•

A required resource is currently unavailable. (See Section 1.5.2.)

•

A programming error is detected during the execution of an image. (See
Section 1.5.3.)

•

A system software or hardware problem exists. (See Section 1.5.4.)

1.5.1 Recovering from Command Entry Errors
When an error occurs following interactive command entry, you must reenter the
command. Messages from the command interpreter are usually followed by a
display of the portion· of the command line that is rejected. Correct this portion of
the line before you reenter the command.
Errors that occur while a command is executing can indicate that you have
entered an invalid value for a parameter or qualifier. In these cases, you can use
the DCL command HELP or consult the OpenVMS DCL Dictionary to determine
the legal values before you try to reenter the command.
Errors in file specifications or device names can occur when you enter a file name
in a command that has a default file type, but the file name is currently defined
as a logical name. When the system translates the logical name, the resulting file
specification may not be valid within the context of the command.
The syntax of the file specification can be invalid for any of the following reasons:

1-4

•

A device name is not terminated with a colon.

•

A directory name is not enclosed in brackets.

•

A file name has more than 39 characters.

•

A file type has more than 39 characters.

•

An alphabetic version number is specified.

•

A node name is included and contains nonalphanumeric characters.

•

A connection to the target node could not be made.

OpenVMS System Messages
1.5 Recovery Procedures
1.5.2 Responding to Unavailable Resources
If the Set Resource Wait Mode ($SETRWM) system service is enabled (default
mode) and a required resource such as dynamic memory is unavailable, the
process is normally placed in a wait state until the resource becomes available.
However, under certain program conditions, the programmer can choose to
disable the resource wait mode so that when such a condition occurs, control
returns immediately to the calling program with an error status.

Other resources such as files, privileges, or devices are not subject to resource
wait mode, and their unavailability or absence always causes an error.
How a program responds to the unavailability of a resource depends primarily on
the application and the particular service called. In some instances, the program
may be able to continue execution and retry the service later. Or, it may be
necessary only to note that the program is required to wait.

1.5.3 Recovering from Programming Errors
If a program image terminates abnormally, you can get some information about
the error from the message. caused by unavailable resources When a program
image exits, the command interpreter uses the current value of general register
0 to obtain information about the exit status. If it is an abnormal (or error) exit,
the system message associated with the register 0 value is displayed.

Programming errors are caused by the following conditions:
•

Incorrect coding of arguments for called procedures (for example, system
services)

•

Logic errors in programming

•

Failure to establish the correct execution environment before executing the
image (for example, failure to make logical name assignments for input or
output files or devices)

The OpenVMS debugger can help you discover and correct programming errors.
For details on how to use the debugger, refer to the Open VMS Debugger Manual.

1.5.4 Reporting System Software or Hardware Errors
When a message notifies you that a system software or hardware error has
occurred, action is required by the system operator or system manager. If a
hardware device is not operational, inform the system manager. If you encounter
a software error, submit a Software Performance Report (SPR) to Digital and
include any system dump files or other relevant information.

1-5

2
Help Message Utility {MSGHLP)
Help Message (MSGHLP) is a versatile utility that allows you to quickly access
online descriptions of system messages from the DCL prompt on a character-cell
terminal (including DECterm windows).
Help Message displays message descriptions from the latest OpenVMS messages
documentation (the most recent version of the OpenVMS System Messages and
Recovery Procedures Reference Manual plus messages from any subsequent
releases). In addition, the Help Message database can optionally include other
source files, such as user-supplied messages documentation.
The HELP/MESSAGE command and qualifiers are described in the following
sections, including an overview of the facility's features and examples of a few
simple operations. Detailed information about customizing the Help Message
database follows the qualifier descriptions. System managers can refer to the
OpenVMS System Manager's Manual for more information about customizing the
Help Message database.

2.1 Features of Help Message
Basic Help Message features are summarized below.
•

By default, Help Message provides information on the status of the last
executed DCL command. To obtain message information after a DCL
command results in an error, type the following:
$ HELP/MESSAGE

You can abbreviate the command according to standard conventions or define
a key to evoke the basic HELP/MESSAGE command.
•

Help Message preserves the value of $STATUS, so you can incorporate the
HELP/MESSAGE command into a command procedure to obtain additional
information about errors. For example, you could include a command similar
to the following:
$ IF .NOT. $STATUS THEN HELP/MESSAGE

•

The default HELP/MESSAGE command operates on the value currently
stored in $STATUS. You can also access a message description by explicitly
specifying a status value in either decimal or hexadecimal. For example:
$ HELP/MESSAGE/STATUS=l2
$ HELP/MESSAGE/STATUS=%XC

•

You can also access message descriptions by specifying the message identifier
or other words from the message text in any order. For example, the following
commands both access ACCVIO messages.
$ HELP/MESSAGE ACCVIO
$ HELP/MESSAGE VIRTUAL ACCESS

2-1

Help Message Utility (MSGHLP)
2.1 Features of Help Message
•

By default, HELP/MESSAGE matches all words beginning with the specified
search string. You can refine a search to match exact words only.
In the following example, the first command outputs all messages containing
words beginning with the ACC string, while the second command selects only
those messages that contain ACC as a whole word. You can use Ctrl/Z to quit
out of any undesired long list of messages-or to terminate any other Help
Message operation.
$ HELP/MESSAGE/BRIEF ACC
$ HELP/MESSAGE/BRIEF/WORD_MATCH=WHOLE_WORD ACC

•

To refine your search even further, you can specify that only messages
produced by a certain facility be displayed. For example, the following
command displays only the ACCVIO message produced by the SYSTEM
facility.
$ HELP/MESSAGE/FACILITY=SYSTEM ACCVIO

•

You can also select all messages produced by one or more specified facilities.
To list the names of all facilities in the database, type the following:
$ HELP/MESSAGE/FACILITY=?

You can specify any facility name from the resulting list as a value for the
/FACILITY qualifier. Specify /BRIEF to output a list of the messages only,
without descriptions. Adding /SORT alphabetizes the output. For example,
the following command alphabetically lists all the messages for the DTS
facility:
$ HELP/MESSAGE/BRIEF/SORT/FACILITY=DTS

For more information about specifying facility names using the /FACILITY
qualifier, see Section 2.3.
•

By selecting the messages you want and directing them to a file, you can
create and print your own customized message documentation.
For example, the following command selects all messages issued by the
BACKUP facility and those messages documented as "Shared by several
facilities," alphabetizes them, and outputs them to a printable file called
MESSAGES.TXT.
$ HELP/MESSAGE/FACILITY=(BACKUP,SHARED)/SORT/OUTPUT=MESSAGES.TXT

2-2

•

You can define a logical name in your login file to override a system-defined
search path for the Help Message database and create a customized database
that includes your own message descriptions (see Section 2.5.2).

•

You can add your own messages documentation to the Help Message database
(see Section 2.6.1).

•

You can delete messages from the database (see Section 2.6.2).

•

Users with write access to Digital-supplied MSGHLP$DATA files (usually
the system manager) can further customize the Help Message database (for
example, add a comment to a Digital-supplied message description).

•

You can exit out of any Help Message display by typing Ctrl/Z.

Help Message Utility (MSGHLP)
2.1 Features of Help Message
Following the HELP/MESSAGE command and qualifier descriptions, detailed
information is provided for the following tasks:
•

Customizing the Help Message database (see Section 2.5)
Describes the files you can manipulate and explains how to use search paths
to set up one or more Help Message databases.

•

Modifying the Help Message database (see Section 2.6)
Describes how to add, delete, or change information in the database.

If you experience performance problems with Help Message or have requirements
that you cannot satisfy using the procedures described in this chapter, consult
your system manager.

2.2 HELP/MESSAGE Command and Qualifiers
The HELP/MESSAGE command and qualifiers are described ori the following
pages.

2-3

Help Message Utility (MSGHLP)
HELP/MESSAGE

HELP/MESSAGE
Displays descriptions of system messages.

Format
HELP/MESSAGE

[/qualifier[ ... ]] [search-string]

Parameter
search-string

Specifies a message identifier or one or more words from a message's text. By
default, HELP/MESSAGE displays a description of the message produced by the
last executed command (that is, the message corresponding to the condition code
currently stored in the CLI symbol $STATUS). (Some exceptions are discussed in
Section 2.4.)
The Help Message utility (MSGHLP) operates on the search string using the
following conventions:
•

Words containing fewer than three alphanumeric characters are ignored.

•

Words can be listed in any order.
You can minimize search time by specifying the most unusual word first.

•

Nonalphanumeric characters are ignored in the search. Exceptions are the
percent sign ( % ) and hyphen ( - ) when they prefix a message. Therefore, you
can paste a full message into the search string, provided you include these
special characters and delete any variables (such as file names) that were
inserted into the message.
If Help Message fails to find a pasted message in the database, submit the
command again and omit the leading special character, facility, and severity.
Some common messages are documented as "shared" messages rather than
facility-specific messages.

•

Help Message matches all words that begin with the characters specified in
the search string. Use /WORD_MATCH=WHOLE_WORD to specify that only
whole words be matched.

Qualifiers
/BRIEF

_Outputs the message text only.
/DELETE=filename.MSGHLP

Deletes all messages contained in the specified .MSGHLP file from one of the
following files:

2-4

•

SYS$HELP:MSGHLP$LIBRARY.MSGHLP$DATA (the default
.MSGHLP$DATA file)

•

The first .MSGHLP$DATA file in the default search path (defined by logical
name MSGHLP$LIBRARY)

•

A .MSGHLP$DATA file specified with the /LIBRARY qualifier

•

The first .MSGHLP$DATA file in a search path specified by the /LIBRARY
qualifier

Help Message Utility (MSGHLP)
HELP/MESSAGE
You must have write access to Digital-supplied .MSGHLP$DATA files to delete
messages from the Digital-supplied database.
~~~~~~~~~~~~

Note ~~~~~~~~~~~~

If you create a .MSGHLP file by specifying a search string, check
the output .MSGHLP file to be sure the search did not pick up any
unexpected messages that you do not want to delete from the database.
Edit any such messages out of the .MSGHLP file before you perform the
delete operation.

/EXTRACT=filename.MSGHLP

Extracts messages from the database and generates a .MSGHLP file that can
be edited, if desired, and used as input for /INSERT and /DELETE operations.
/EXTRACT retrieves data from a .MSGHLP$DATA file or logical search path
specified by /LIBRARY or by the default search path defined by logical name
MSGHLP$LIBRARY. If /EXTRACT is not specified, Help Message produces
output in standard text format by default (see /OUTPUT).
/FACILITY=?
/FACILITV=(facility-name [, ... ])
/FACILITY=ALL

Specifies which facilities in the database are to be searched for a match.
Enter /FACILITY=? to output a list of all facilities in the default database or in a
database specified by /LIBRARY.
To narrow your search, specify one or more facility names with /FACILITY.
(Multiple facilities must be enclosed in parentheses and be separated by commas.)
Help Message then outputs only matching messages produced by the specified
facility or facilities.
Specify /FACILITY=ALL to output messages for all facilities in the database.
/FACILITY=ALL is the default unless another facility is implied; for example,
specifying /STATUS or defaulting to the value of the CLI symbol $STATUS
automatically identifies a specific facility. Similarly, cutting and pasting a
message that includes a facility name invalidates use of the /FACILITY qualifier.
/FULL (default)

Outputs the complete message description, including message text, facility name,
explanation, user action, and user-supplied comment, if any.
/INSERT=filename.MSGHLP

Updates one of the following files with new or changed information from the
specified .MSGHLP file:
•

SYS$HELP:MSGHLP$LIBRARY.MSGHLP$DATA (the default
.MSGHLP$DATA file)

•

The first .MSGHLP$DATA file in the default search path (defined by logical
name MSGHLP$LIBRARY)

•

A .MSGHLP$DATA file specified with the /LIBRARY qualifier

•

The first .MSGHLP$DATA file in a search path specified by the /LIBRARY
qualifier

2-5

Help Message Utility (MSGHLP)
HELP/MESSAGE
You must have write access for the Digital-supplied .MSGHLP$DATA files to
insert data into these files. User-supplied data is identified by change bars in
Help Message output.
/LIBRARY=disk:[directory]filename.MSGHLP$DATA
/LIBRARY=logical-name

Defines the messages database for the current command to be a particular
.MSGHLP$DATA file or a search path defined by a logical name.
For most operations, the default database is either
SYS$HELP:MSGHLP$LIBRARY.MSGHLP$DATA or a search path of
.MSGHLP$DATA files defined by logical name MSGHLP$LIBRARY.
For /DELETE and /INSERT operations, the default database is either
SYS$HELP:MSGHLP$LIBRARY.MSGHLP$DATA or the first file in a search
path defined by logical name MSGHLP$LIBRARY.
/OUTPUT=files pee

Writes output to the specified file. By default, Help Message writes output to
SYS$0UTPUT, which is normally the terminal.
/PAGE (default for screen display)
/NO PAGE

Displays terminal output one screen at a time. The page length is automatically
set to 1 line less than the value specified by SET TERMINAL/PAGE. (Use of
/PAGE is incompatible with /OUTPUT=filespec.)
/SORT
/NOSORT (default)

Sorts output in alphabetical order.
/STATUS=status-code
/STATUS='symbol'
/STATUS='$STATUS' (default)

Outputs the message corresponding to the specified status code. You can specify
the status code with a decimal or hexadecimal number or a symbol enclosed in
apostrophes. You can omit leading zeros, but you must prefix any hexadecimal
number with "%X".
If a HELP/MESSAGE command does not include a search string, Help Message
by default outputs the message corresponding to the CLI symbol $STATUS;
that is, Help Message displays information on how the last executed command
completed.

You cannot specify a search string or /FACILITY with /STATUS. /FACILITY is
also illegal if you omit the search string and default to /STATUS='$STATUS'.
/WORD_MATCH=INITIAL_SUBSTRING (default)
/WORD_MATCH=WHOLE_WORD

/WORD_MATCH=INITIAL_SUBSTRING matches all words that begin with a
word specified in the search string. The search string can contain multiple words
to be matched. Only messages that match every word in the search string (in any
order) are output.
/WORD_MATCH=WHOLE_WORD matches whole words only and refines your
search to the exact words specified. For example, an exact search on ACC screens
out dozens of other messages containing words that begin with the letters ACC.

2-6

Help Message Utility (MSGHLP)
2.3 Tips for Using the /FACILITY Qualifier

2.3 Tips for Using the /FACILITY Qualifier
When you specify /FACILITY=?, Help Message outputs the names of all facilities
in the database. Unless you specify /SORT, the output alphabetically lists the
facility names for the first .MSGHLP$DATA file in the database, then the second
.MSGHLP$DATA file, and so on.
In addition to the facility names listed in response to /FACILITY=?,
Digital has included a few internal nicknames to simplify access to certain
facilities. "DCL" and "SHARED" are two such nicknames. For example, in
MSGHLP$LIBRARY.MSGHLP$DATA, the nickname "DCL" maps to the official
facility name, "CLI, Command Language Interpreter (DCL)". DCL does not
appear in the list of facility names, but if you enter /FACILITY=DCL in a
command, Help Message outputs the CLI messages. Similarly, specifying
/FACILITY=SHARED outputs messages that are documented as "Shared by
several facilities."
Help Message searches for facility names from the beginning of the facility name's
string only-not on each word of the string as with the message text. Therefore,
you must enter enough characters to narrow your search to the desired field.
For example, a search on /FACILITY=RUN selects messages for two facilities:
•

RUN, Run Detached Utility

•

RUNOFF, DIGITAL Standard Runoff (DSR)

To find the RUN messages only, you must enter enough literal characters to make
the search string unique; for example, /FACILITY="RUN,". The double quotes
are required in order to include the comma (and any following words) in the
search string. Since the double quotes direct Help Message to search for a literal
string, you must specify the precise capitalization used for the facility name in
the database.

2.4 Using SET MESSAGE to Access Uninstalled Messages
Certain messages, such as the NCP (Network Control Program) messages, are
not installed as system messages. Therefore, a value stored in $STATUS is not
recognized unless the NCP message file is known to the system. This is easily
done by using the SET MESSAGE command to include any unknown messages
.EXE files. For example:
$ SET MESSAGE SYS$MESSAGE:NETWRKMSG.EXE
$ SET MESSAGE SYS$MESSAGE:SYSMGTMSG.EXE

These commands include the NCP messages (in 'file
SYS$MESSAGE:NETWRKMSG.EXE) and the BACKUP messages (in file
SYS$MESSAGE:SYSMGTMSG.EXE) as part of the system.
An alternative to accessing the message description by using the value stored in
$STATUS is to enter the HELP/MESSAGE command and specify the message
identifier or message text in the search string.

2-7

Help Message Utility (MSGHLP)
2.5 Customizing the Help Message Database

2.5 Customizing the Help Message Database
You can create one or more customized Help Message databases by changing
information in the database files (see Section 2.6) and by selecting which files
to include in a database. No matter how you customize your database, you will
typically manipulate two kinds of files:
•

.MSGHLP$DATA files
One or more .MSGHLP$DATA files form the Help Message database that is
accessed by the HELP/MESSAGE command (see Section 2.2). If you have
write access to the .MSGHLP$DATA files, you can customize the database by
inserting or deleting data contained in .MSGHLP files. (.MSGHLP files are
described later in this list.)
The system manager can define a system logical name to set up a systemwide Help Message database that includes all or selected .MSGHLP$DATA
files in a search path. You can also set a logical name in your login file to
include or exclude specific .MSGHLP$DATA files in your personalized Help
Message database (see Section 2.5.2).

•

.MSGHLP files
A .MSGHLP file is used as input to change the content of a .MSGHLP$DATA
file. The contents of a .MSGHLP file are applied to a .MSGHLP$DATA
file either as data to be inserted or as data to be deleted from the
.MSGHLP$DATA file. Various options are described in subsections to
Section 2.6.

By setting up different search paths for multiple .MSGHLP$DATA files at the
system or process level, you can create a variety of Help Message databases.
The Help Message qualifier /LIBRARY allows you to access or change a specific
.MSGHLP$DATA file or search path. For more information, see Section 2.5.2.

2.5.1 Creating a .MSGHLP File
There are two ways to create a .MSGHLP file, depending upon the purpose for
which you intend to use the file, as follows:
•

Use the /EXTRACT qualifier with the HELP/MESSAGE command.
Use this method when you want to modify or delete information in the
database.
Users with write access to Digital-supplied .MSGHLP$DATA files can use a
.MSGHLP file created in this fashion to add a comment to a Digital-supplied
message or to delete Digital-supplied information from the database. See the
OpenVMS System Manager's Manual for details.

•

Write the file from scratch.
Use this technique when you have new messages to add to the database. (See
the .MSGHLP file format in the example that follows.)

The following example uses the /EXTRACT qualifier to extract hypothetical
message NOSNO from the default database and create a file named
NOSNO.MSGHLP to contain the message description.
$ HELP/MESSAGE/EXTRACT=NOSNO.MSGHLP NOSNO

2-8

Help Message Utility (MSGHLP)
2.5 Customizing the Help Message Database
The .MSGHLP file format uses a unique numerical prefix to designate the
message, facility, explanation, and user action sections of the message description.
lNOSNO, can't ski; no snow
2XCSKI, XCSKI Program
3Your attempt to ski failed because there is no snow.
4Wait until there is snow and attempt the operation again.

When creating a .MSGHLP file, limit your text to 60 characters per line so that
the Help Message output does not exceed the terminal display area~
Other sections in this chapter explain how you can use the contents of a
.MSGHLP file, edited or unedited, to add data to or delete data from a
.MSGHLP$DATA file.

2.5.2 Defining a Search Path in Your Login File
The Help Message database comprises one or more .MSGHLP$DATA files that
can be accessed individually by the .MSGHLP$DATA file name or collectively by
a search path that names one or more .MSGHLP$DATA files.
Your system manager sets up a default Help Message database on the system
or accepts the installation default. When you instruct Help Message to display
messages or to output messages to a file, Help Message defaults to the main
OpenVMS messages file (SYS$HELP:MSGHLP$LIBRARY.MSGHLP$DATA)
unless a search path is defined by logical name MSGHLP$LIBRARY at the
system or user level.
You can create your own .MSGHLP$DATA files to add to the database (see
Section 2.6.1). None of the .MSGHLP$DATA files need be installed on the system
disk. Once you have created the .MSGHLP$DATA files, you can create a logical
name in your login file (SYS$LOGIN:LOGIN.COM) to define a search path
that names the .MSGHLP$DATA files you want to include in your customized
database.
For example, the following command in your login file defines your Help Message
default search path to include the main OpenVMS messages file and another file
called MYMESSAGES.MSGHLP$DATA:
$DEFINE MSGHLP$LIBRARY SYS$COMMON: [SYSHLP]MSGHLP$LIBRARY.MSGHLP$DATA,_$ TOOLS: [MYPROJ]MYMESSAGES.MSGHLP$DATA

You can set up multiple logical names to create customized search paths that
restrict the Help Message database to minimize search time or that add personal
.MSGHLP$DATA files to the database. For example, the following logical name
omits the main OpenVMS messages file and names two other .MSGHLP$DATA
files instead:
$ DEFINE MSGHLP_ABCDEF TOOLS: [MYPROJ]ABC.MSGHLP$DATA,TOOLS: [MYPROJ]DEF.MSGHLP$DATA

You can use the /LIBRARY qualifier with the HELP/MESSAGE command to
specify a logical name or a .MSGHLP$DATA file. For example, the following
command specifies that Help Message. search only the file DEF.MSGHLP$DATA
for message TROUBLE:
$ HELP/MESSAGE/LIBRARY=TOOLS: [MYPROJ]DEF.MSGHLP$DATA TROUBLE

The following command specifies that Help Message search all the files defined
by logical name MSGHLP_ABCDEF (defined in an earlier coding example), which
includes both ABC.MSGHLP$DATA and DEF.MSGHLP$DATA:
$ HELP/MESSAGE/LIBRARY=MSGHLP_ABCDEF TROUBLE

2-9

Help Message Utility (MSGHLP)
2.5 Customizing the Help Message Database
If you have defined no search paths in your account, the following command

directs Help Message to search the default database defined at the system level:
$ HELP/MESSAGE TROUBLE

Typically Help Message searches all .MSGHLP$DATA files in a search path.
However, on /INSERT and /DELETE operations, Help Message operates on only
one .MSGHLP$DATA file: either a file specified with the /LIBRARY qualifier, a
default .MSGHLP$DATA file, or the first .MSGHLP$DATA file in a default or
specified search path.
Unless you have write access to the Digital-supplied .MSGHLP$DATA files, it
makes sense to put the .MSGHLP$DATA file that you are most likely to update
first in a search string. For example, if you have the first of the following two
commands in your login file, the second command would by default update file
MYMESSAGES.MSGHLP$DATA:
$ DEFINE MSGHLP$LIBRARY TOOLS: [MYPROJ]MYMESSAGES.MSGHLP$DATA,_$ SYS$COMMON: [SYSHLP]MSGHLP$LIBRARY.MSGHLP$DATA
$ HELP/MESSAGE/INSERT=NEW MESSAGES.MSGHLP

An alternative is to use the /LIBRARY qualifier to override the default
.MSGHLP$DATA file and specify the file that you want to update. For example:
$DEFINE MSGHLP$LIBRARY SYS$COMMON: [SYSHLP]MSGHLP$LIBRARY.MSGHLP$DATA,_$ TOOLS: [MYPROJ]MYMESSAGES.MSGHLP$DATA
$ HELP/MESSAGE/INSERT=NEW_MESSAGES.MSGHLP_$ /LIBRARY=TOOLS: [MYPROJ]MYMESSAGES.MSGHLP$DATA

2.6 Modifying the Help Message Database
You can modify the database by adding or deleting information. When you add
information to the database, user-supplied documentation displays with a change
bar in the left margin to distinguish it from Digital-supplied data.
Only users with write access to Digital-supplied .MSGHLP$DATA files can delete
Digital-supplied data or update these files (see the OpenVMS System Manager's
Manual for details). However, any user can create a private .MSGHLP$DATA file
·and include it in the Help Message database (see Section 2.5.2).
The following sections explain how to make these modifications:
•

Add messages to the database (see Section 2.6.1).

•

Delete user-supplied messages from the database (see Section 2.6.2).

•

Change user-supplied information in the database (see Section 2.6.3).

•

Change Digital-supplied messages documentation (see Section 2.6.4).

2.6.1 Adding Messages to the Database
You can add new messages to the database by creating a .MSGHLP$DATA file
and adding it to a Help Message database search path. The .MSGHLP$DATA file
that you create remains intact throughout system upgrades.
Follow these steps to add new messages to the Help Message database:
1. Create a .MSGHLP file with all your message descriptions in it. (The
formatted data in the .MSGHLP file is used as input to create the
.MSGHLP$DATA file.) (See Section 2.5.1 for an example of the .MSGHLP file
format.)

2-10

Help Message Utility (MSGHLP)
2.6 Modifying the Help Message Database
2. Use the .MSGHLP file to create a .MSGHLP$DATA file. Use the /LIBRARY
qualifier to specify the name of the .MSGHLP$DATA file that you want to
create:
$ HELP/MESSAGE/INSERT=MYMESSAGES.MSGHLP_$ /LIBRARY=TOOLS: [MYPROJ]MYMESSAGES.MSGHLP$DATA

3. Add the new .MSGHLP$DATA file to a Help Message database search path,
as described in Section 2.5.2.

2.6.2 Deleting Messages from the Database
You can delete any message, provided you have write access to the
.MSGHLP$DATA ,file that contains the message. User-supplied data displays
with change bars in the left margin to distinguish it from Digital-supplied data.
Digital-supplied messages can be deleted only by users with write access to
Digital-supplied .MSGHLP$DATA files, usually the system manager. (See the
OpenVMS System Manager's Manual for details.)
Use a .MSGHLP file to delete messages, as follows:
1. Extract the message that you want to delete into a .MSGHLP file. The
following example extracts hypothetical message PROBLEM from the default
database:
$ HELP/MESSAGE/EXTRACT=PROBLEM.MSGHLP PROBLEM

Check the contents of PROBLEM.MSGHLP to see if the Help Message search
picked up any other messages that you were not expecting. If necessary,
edit the file to include only the messages that you want to delete from the
database.

3. Use the /DELETE qualifier to delete the messages in PROBLEM.MSGHLP
from the .MSGHLP$DATA file:
$ HELP/MESSAGE/DELETE=PROBLEM.MSGHLP

Remember that a delete operation acts on only the first .MSGHLP$DATA file
in a search path. If necessary, you can use the /LIBRARY qualifier to specify
a particular .MSGHLP$DATA file. See Section 2.5.2 for more information
about default databases and search paths.
If you keep the PROBLEM.MSGHLP file, you can later use this file with
the /INSERT qualifier to put the deleted messages back into the database,
possibly in a different .MSGHLP$DATA file.
4. When you delete messages from the database, free space is created
in the library. The following command sequence compresses
MYMESSAGES.MSGHLP$DATA to use as little disk space as possible:
$ CONVERT TOOLS: [MYPROJ]MYMESSAGES.MSGHLP$DATA_$ TOOLS: [MYPROJ]MYMESSAGES.MSGHLP$DATA
$ PURGE TOOLS: [MYPROJ]MYMESSAGES.MSGHLP$DATA

2-11

Help Message Utility (MSGHLP)
2.6 Modifying the Help Message Database
2.6.3 Changing User-Supplied Data
You can change any user-supplied data, provided you have write access to the
.MSGHLP$DATA file. User-supplied data displays with change bars in the left
margin to distinguish it from Digital-supplied data.
Digital-supplied documentation can be modified only by users with write access
to Digital-supplied .MSGHLP$DATA files, usually the system manager. (See the
Open VMS System Manager's Manual for details.) Other users can make a copy of
a Digital-supplied message and edit that to fit their needs (see Section 2.6.4).
The procedure for updating an existing message is slightly different depending on
which field you want to change. Both procedures are described in the following
sections.
Changing the Explanation or User Action Fields

Follow these steps to change the explanation or user action fields:
1. Extract the message that you want to edit into a .MSGHLP file.
The following example extracts hypothetical message FIXIT from
MYMESSAGES.MSGHLP$DATA.
$ HELP/MESSAGE/EXTRACT=FIXIT.MSGHLP_$ /LIBRARY=TOOLS: [MYPROJ]MYMESSAGES.MSGHLP$DATA FIXIT

Edit the explanation or user action fields in- FIXIT.MSGHLP.

3. Update MYMESSAGES.MSGHLP$DATA using the edited FIXIT.MSGHLP
file as input. For example:
$ HELP/MESSAGE/INSERT=FIXIT.MSGHLP_$ /LIBRARY=TOOLS: [MYPROJ]MYMESSAGES.MSGHLP$DATA
Changing the Message Text or Facility Fields

Help Message updates an existing message entry by comparing the message text
and facility name fields for an identical match before changing any data in the
explanation or user action fields. Therefore, if you want to change the message
text of an existing message, you must delete the current message before you
insert the revised message. Otherwise, both the old and the new message will
appear in the database.
1. Extract the message that you want to edit into a .MSGHLP file. The following
example extracts hypothetical message PROBLEM from the default database:
$ HELP/MESSAGE/EXTRACT=PROBLEM.MSGHLP PROBLEM

2. Check the contents of PROBLEM.MSGHLP to see if the Help Message search
picked up any other messages that you were not expecting. If necessary,
edit the file to include only the messages that you want to delete from the
database.
3. Use the /DELETE qualifier to delete the messages in PROBLEM.MSGHLP
from the .MSGHLP$DATA file:
$ HELP/MESSAGE/DELETE=PROBLEM.MSGHLP

See Section 2.6.2 for full details about deleting messages from the database.
4. Edit the message text or facility name in the .MSGHLP file.
5. Update the database using the edited .MSGHLP file as input. For example:
$ HELP/MESSAGE/INSERT=PROBLEM.MSGHLP

2-12

Help Message Utility (MSGHLP)
2.6 Modifying the Help Message Database
This command updates the default .MSGHLP$DATA file. Section 2.5.2
describes how the default database for an insert operation can differ from the
default database for an output operation.

2.6.4 Changing Digital-Supplied Messages Documentation
If you have write access to Digital-supplied .MSGHLP$DATA files, refer to the
OpenVMS System Manager's Manual for information about modifying or deleting
Digital-supplied messages documentation.
If you do not have write access to Digital-supplied .MSGHLP$DATA files, there
are two ways you can add comments to or modify a Digital-supplied message:
•

Ask a user with write access to the files, usually the system manager, to add
your comment to the database. This is the best solution if your comment
would be helpful to other users on the system.
Please report to Digital any errors in a message text string so that we can
correct the problem in future databases.

•

Create a copy of the Digital message in your own .MSGHLP$DATA file and
edit the description to suit your needs. Follow these steps:
1. Extract the Digital-supplied message that you want to edit. The following
example extracts the message BAD_NEWS from a default database that
includes this hypothetical Digital-supplied message:
$ HELP/MESSAGE/EXTRACT=BAD_NEWS.MSGHLP BAD_NEWS

2. Edit any fields in BAD_NEWS.MSGHLP to say whatever you want.
3. Update your own .MSGHLP$DATA file using the edited BAD_
NEWS.MSGHLP file as input. For example:
$ HELP/MESSAGE/INSERT=BAD_NEWS.MSGHLP/LIBRARY=TOOLS: [MYPROJ]_$ MYMESSAGES.MSGHLP$DATA

If your .MSGHLP$DATA file is included in a search path of the main database,
a Help Message search will output both the Digital-supplied message and your
version of the message. Your version is distinguished by change bars in the left
margin.

2-13

Part II
Message Descriptions

This part of the manual alphabetically lists and describes messages for the
following OpenVMS facilities:

•
•
•
•
•
•
•
•

•
•
•

BACKUP
BUGCHECK
INSTALL
IOGEN
LAVC
LOGIN
MOUNT
STD RV
SYSBOOT
SYSGEN
SYSINIT

• VAXport
Some messages from the LAT and SYSTEM facilities are also included. For
descriptions of other OpenVMS messages, use the Help Message utility described
in Part I of this manual or refer to the Open VMS System Messages and Recovery
Procedures Reference Manual and the latest Release Notes.

Message Descriptions

ABORT, abort
Facility: SYSGEN, System Generation Utility
Explanation: This message is issued with accompanying messages to
indicate that the action is aborted.
User Action: Take appropriate action based on information in the
accompanying message.
ABORT, operator requested abort on fatal error
Facility: BACKUP, Backup Utility
Explanation: In response to a BACKUP-I-SPECIFY prompt, the user or
operator entered the QUIT option; the Backup utility terminated.
User Action: None.
ACCERR, nonblank accessibility field in volume labels on 'device-name'
Facility: MOUNT, Mount Utility
Explanation: The accessibility field on the magnetic tape, which is mounted
on the device indicated, has a nonblank accessibility field. This field denies
access to the tape.
User Action: Mount the magnetic tape with the
/OVERRIDE=ACCESSIBILITY qualifier. (The user must be the owner
of the volume or have VOLPRO privilege.)
ACCONFLICT, 'file-name' is open for write by another user
Facility: BACKUP, Backup Utility
Explanation: The Backup utility opened the specified file while another user
was writing the file; /IGNORE=INTERLOCK qualifier is specified with the
DCL command BACKUP.
User Action: Note that the saved copy of the file may be inconsistent.
ACNTEXC, you are at maximum allowed processes for your account name
Facility: LOGIN, Login Procedure
Explanation: No more processes can be logged in under this account.
User Action: Wait until another process logged in under this account has
logged out.
ACNTEXPIR, your account has expired - contact your system manager
Facility: LOGIN, Login Procedure
Explanation: The user account has expired. When creating an account, the
system manager can limit it to a specific time period, after which the account
becomes invalid.
User Action: Ask your system manager to renew your account.
ACPMBFAIL, ACP failure to read mailbox
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing

Message Descriptions

the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
ACPNAME, ACP file name is too long
Facility: MOUNT, Mount Utility
Explanation: The file name specified for an ACP image has more than nine
characters.
User Action: Reenter the command and specify the correct ACP file name.
ACPRECURS, attempted recursion in ACP secondary operation
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
ACPTIME, ACP does not respond
Facility: MOUNT, Mount Utility
Explanation: The ACP that is requested in the DCL command MOUNT
cannot be initialized. Either the specified image is not an ACP or a system
error has occurred.
User Action: Verify that the image is an ACP. If it is an ACP, consult your
system manager to determine what events in the system might prevent the
ACP from starting.
ACPUNSTAK, attempted unstack in ACP primary context
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
ACPVAFAIL, ACP failure to return virtual address space
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing

Message Descriptions

the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
ACTIVATE, activating ICBM 'file-name'
Facility: IOGEN
Explanation: This log message reports the IOGEN Configuration Building
Module (ICBM) names.
User Action: None.
ACTIVEBCB, buffer active during reel switch
Facility: BACKUP, Backup Utility
Explanation: A software error occurred in the Backup utility.
User Action: Submit a Software Performance Report (SPR).
ALCPHD, allocate process header 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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
ALCSMBCLR, ACP tried to allocate space already allocated
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
ALLOCFAIL, file structure allocation failure for 'device-name'
Facility: BACKUP, Backup Utility
Explanation: Insufficient contiguous space is available on the specified
volume to allocate the files necessary to initialize the volume as a Files-11
structured volume. This error may be caused by an excessive number of bad
blocks.
User Action: Retry the operation using another volume.

Message Descriptions

ALLOCMEM, error allocating virtual memory
Facility: BACKUP, Backup Utility
Explanation: An error occurred during an attempt to allocate dynamic
virtual memory. An accompanying message provides additional information.
User Action: Correct the condition that caused the error and reenter the
command. It may be necessary to increase the page file quota of the account
or the SYSGEN parameter VIRTUALPAGECNT.
APTREFHIGH, inconsistent active page table reference count
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
APTWRTERR, active page table swap write 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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
AQBTIME, ACP queue is unstable
Facility: MOUNT, Mount Utility
Explanation: The system cannot start the ACP specified in the DCL
command MOUNT request. This message indicates an error in the operating
system software.
User Action: Consult the system manager to determine what events in the
system might be preventing ACPs from starting.
ASSIGNFAIL, could not assign 'device' as system disk
Facility: BACKUP, Backup Utility
Explanation: Standalone BACKUP could not assign a channel to the disk
from which it was booted.
User Action: Determine why the channel assign failed. If possible, correct
the problem and retry the backup operation. Otherwise, submit a Software
Performance Report (SPR) including full configuration details and a log of the
output.

Message Descriptions

ASUSPECT, customer defined text
Facility: LAVC, Local Area VMScluster
Explanation: The local area VMScluster network failure analysis located a
network problem and reported this network component as suspect.
User Action: Several PEDRIVER channels that were using this network
component have failed. The analysis indicates that this component or
something connected to it is likely to have caused the network problems.
Have the system manager or network manager look into the network
problem.
ASYNCWRTER, asynchronous write memory failure
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
AUTOLOGIN, account is auto-login only
Facility: LOGIN, Login Procedure
Explanation: The automatic login feature permits users to log in to the
system without specifying a user name. An automatic login account cannot be
accessed by a normal interactive login or by an explicit DECnet for OpenVMS
access control string. This message is written to the system accounting and
security audit records; the NOTVALID message displays to the user.
User Action: None.
AUTOMEMCOPY, 'device-name' automatically added to the shadow set with a
copy operation
Facility: MOUNT, Mount Utility
Explanation: The MOUNT qualifier /INCLUDE was specified allowing
members that were previously part of the shadow set to be automatically
added to the set. The indicated device was successfully added to the shadow
set. A copy operation was initiated making this device a target for all blocks.
User Action: None.
AUTOMEMERGE, 'device-name' automatically added to the shadow set with a
merge operation
Facility: MOUNT, Mount Utility
Explanation: The MOUNT qualifier /INCLUDE was specified allowing
members that were previously part of the shadow set to be automatically
added to the set. The indicated device was successfully added to the shadow
set with merge semantics. The device is identical to the other members of the
set except for possible incomplete writes for which the shadowing software
will check.
User Action: None.

Message Descriptions

AUTOMEMSUCC, 'device-name' automatically added to the shadow set
Facility: MOUNT, Mount Utility
Explanation: The MOUNT qualifier /INCLUDE was specified allowing
members that were previously part of the shadow set to be automatically
added to the set. The indicated device was successfully added to the shadow
set as a consistent member.
User Action: None.
BADACP, invalid syntax on /PROCESSOR qualifier
Facility: MOUNT, Mount Utility
Explanation: The keyword or file specification value specified for the
/PROCESSOR qualifier is not specified correctly.
User Action: Reenter the command; refer to the OpenVMS DCL Dictionary
for the correct syntax.
BADALORQSZ, bad memory allocation request size
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
BADBLKSIZE, 'save-set-spec' has inconsistent block size
Facility: BACKUP, Backup Utility
Explanation: The volume mounted as a continuation volume of a
multivolume save set is not recorded with the same block size as previous
volumes of the save set. This volume is probably not part of the same save
set.
User Action: Locate and mount the correct continuation volume.
BAD BLOCK, bad blocks on 'device-name' do not match input
Facility: BACKUP, Backup Utility
Explanation: In a copy or restore operation with the /PHYSICAL qualifier,
a bad block is present on the output volume in a location where the input
volume had a good block. The backup operation will not result in a valid
Files-11 volume.
User Action: Reevaluate the operation; another mode of operation, such
as the /IMAGE qualifier, may be appropriate. Or retry the operation using
either the original input volume or an error-free output volume.

Message Descriptions

BADBOOTCB, corrupted Boot Control Block
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
BADBUFADR, ACP buffer address out of range of buffer pool
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
BADBUFTYP, bad ACP buffer type code
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
BADCACHE, invalid syntax on /CACHE qualifier
Facility: MOUNT, Mount Utility
Explanation: The options given with the /CACHE qualifier have invalid
syntax.
User Action: Verify the command and reenter the correct syntax.
BADCHKSUM, shared memory data structures corrupted - reinitialization
necessary
Facility: SYSGEN, System Generation Utility
Explanation: A CRC check of the constant fields in the shared memory
datapage has detected an error.
User Action: Reboot all processors using the shared memory.

Message Descriptions

BADDALRQSZ, bad memory deallocation request size or address
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
BADDATA, error in block 'nn' of 'filespec' detected during save
Facility: BACKUP, Backup Utility
Explanation: A read error for the specified block of the specified file
occurred when the save set was created. Data in this block may be corrupt.
User Action: Examine the file for corruption and reconstruct as necessary. If
this error occurs during a disk-to-disk (copy) operation, it indicates a software
error in the Backup utility. In this case, submit a Software Performance
Report (SPR).
BADDATCHK, invalid keyword on /DATACHECK qualifier
Facility: MOUNT, Mount Utility
Explanation: The keyword specified for the /DATACHECK qualifier is
neither READ nor WRITE.
User Action: Reenter the command; specify either READ or WRITE.
BADDAY, you are not authorized to login today
Facility: LOGIN, Login Procedure
Explanation: There are restrictions from the class of login that the user
is attempting. The system manager can restrict user use of a login class on
specific days.
User Action: If possible, try a different login class. For example, if you
are restricted from BATCH logins today, try an interactive class (LOCAL,
REMOTE, or DIALUP). If you are restricted from all classes of logins today,
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.
BADDENS, unknown value on /DENSITY qualifier
Facility: MOUNT, Mount Utility
Explanation: The value specified for a tape density is not 800, 1600, or
6250. The value specified for a diskette is not single or double.
User Action: Reenter the command; specify either 800, 1600, or 6250 for the
density.

Message Descriptions

BADDIR, directory 'directory' has invalid format
Facility: BACKUP, Backup Utility
Explanation: The specified directory file is not in the expected format for a
directory file. The file is corrupt.
User Action: Use the DCL command SET FILE/NODIRECTORY to delete
the corrupt directory file, then use the DCL command ANALYZE/DISK_
STRUCTURE /REPAIR to place the lost files in the [SYSLOST] directory. The
lost files can then be copied to a new directory.
BADFID, ACP file number out of range for this volume
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
BADFILE, invalid filename is 'file-name'
Facility: STDRV, System Startup Driver
Explanation: The named startup component file name is invalid. The
specific reason for the error is printed before this message.
User Action: Use the STARTUP MODIFY FILE command at the SYSMAN>
prompt to correct the file name.
BADFLAG, bad enable/disable flag 'flag'
Facility: STDRV, System Startup Driver
Explanation: The enable/disable flag describing how the list of nodes
associated with a startup component file should be used is invalid.
User Action: Use the SYSMAN command STARTUP ENABLE/DISABLE to
modify this entry in the startup component file.
BADFORKIPL, bad FORK exit interrupt priority level
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)

Message Descriptions

BADHOMBLK, bad home block encountered on volume
Facility: MOUNT, Mount Utility
Explanation: An I/O error occurred while reading a home block during
/BIND processing. A subsequent message explains the nature of the error.
The first occurrence of this message is a warning; the second is fatal.
User Action: Repair using the Analyze/Disk_Structure utility or reinitialize
the volume and retry the operation.
BADHOUR, you are not authorized to login at this time
Facility: LOGIN, Login Procedure
Explanation: At the present time, there are restrictions from the class of
login being attempting. The login classes are: LOCAL, DIALUP, REMOTE,
NETWORK, and BATCH. The system manager can restrict 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.
BADJRNL, invalid syntax on /JOURNAL qualifier
Facility: MOUNT, Mount Utility
Explanation: The wrong command line syntax was entered.
User Action: Correct the syntax and reenter.
BADLCKWSLE, bad locked working set list entry, not a page table
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
BADMCKCOD, bad machine check code
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error and that includes a backup save set
containing the system dump file and the error log file active at the time of the
error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command
that prqduces the save set included with the SPR.)

Message Descriptions

BADMODE, invalid mode 'mode' for file 'file-name'
Facility: STDRV, System Startup Driver
Explanation: A startup component file in the startup component database
has an execution mode that is not DIRECT, BATCH, CALLED, SPAWN, or
ANY.
User Action: To correct the component execution mode, use the STARTUP
MODIFY FILE command at the SYSMAN> prompt.
BADOVR, unknown keyword on /OVERRIDE qualifier
Facility: MOUNT, Mount Utility
Explanation: The command syntax for the /OVERRIDE qualifier is invalid.
User Action: Use the DCL command HELP or refer to the Open VMS DCL
Dictionary for the legal keywords, and reenter the command.
BADPAGFILA, bad page file address allocated
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
BADPAGFILD, bad page file address deallocated
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
BADPAGTYPE, bad page type
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)

Message Descriptions

BADPARAM, insufficient shared memory to create specified data structures
Facility: SYSGEN, System Generation Utility
Explanation: The sum of all the data structures specified is more than the
available amount of shared memory.
User Action: Recalculate memory usage and reenter the command.
BADPRO, invalid syntax on /PROTECTION qualifier
Facility: MOUNT, Mount Utility
Explanation: The command syntax for the /PROTECTION qualifier is
incorrect.
User Action: Type the DCL command HELP SPECIFY PROTECTION or
refer to the OpenVMS DCL Dictionary for the correct syntax, and reenter the
command.
BADQHDR, interlocked queue header corrupted
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
BADQUAL, qualifier '/qualifier' is inconsistent with the operation type
Facility: BACKUP, Backup Utility
Explanation: The specified qualifier cannot be used with the type of
BACKUP operation indicated by the BACKUP command.
User Action: Reenter the BACKUP command without the specified qualifier
or select a different operation type. For more information on how qualifiers
affect the BACKUP command, see the Open VMS System Management
Utilities Reference Manual.
BAD REPLY, unknown type of operator reply, reply is 'reply'
Facility: BACKUP, Backup Utility
Explanation: The operator's reply indicated in the message is an unknown
type and cannot be processed.
User Action: See the operator or your system manager for an indication of
the problem.
BADREPLY, unknown type of operator reply, reply = 'text'
Facility: MOUNT, Mount Utility
Explanation: An error occurred in OPCOM.
User Action: Retry the MOUNT request.

Message Descriptions

BADRSEIPL, bad IPL at entrance to report schedule event
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
BADRVNWCB, inconsistent RVN in window map pointer
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
BADSBMBLK, ACP tried to reference off end of bitmap
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
BADSETAFF, attempt to set process affinity to primary CPU failed
Facility: SYSGEN, System Generation Utility
Explanation: SYSGEN cannot set process affinity to the primary CPU.
User Action: Submit a Software Performance Report (SPR).
BADSETCNT, incorrect number of devices in output specification
Facility: BACKUP, Backup Utility
Explanation: The output specification for a copy, restore, or compare
operation with the /IMAGE qualifier must be a list containing the same
number of devices as the number of volumes in the input volume set.
User Action: If the input is a save set, use the DCL command BACKUP
/LIST to determine how the save set was created; reenter the command.

Message Descriptions

BADSWPVBN, swap VBN specified for non-process page
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
BADTYPE, invalid file type in file 'file-name'
Facility: STDRV, System Startup Driver
Explanation: A startup component file in the startup component database
has a file type which is not COM or EXE.
User Action: Use the SYSMAN command STARTUP MODIFY FILE to
correct the file name.
BADUIC, invalid UIC syntax
Facility: MOUNT, Mount Utility
Explanation: The command contains an invalid UIC. The group and
member portions of a UIC must both be specified and separated by a comma.
User Action: Reenter the command; use the DCL command HELP or refer
to the OpenVMS DCL Dictionary for the correct syntax.
BADUNDFAT, invalid keyword on /UNDEFINED_FAT qualifier
Facility: MOUNT, Mount Utility
Explanation: The MOUNT command specified an invalid keyword with the
/UNDEFINED_FAT qualifier.
User Action: Select a correct combination of keywords from the following
categories:
Record format keywords:
•

FIXED:record-attributes ... ,record-size

•

VARIABLE:record-attributes ...

•

STREAM:record-size

•

STREAM_LF:record-size

•

STREAM_CR:record-size

•

LSB_VARIABLE:record-attributes ...

Record attribute keywords:

•

NONE (None)

•

CR (Carriage_return)

•

FTN (Fortran)

•

PRN (Print)

•

NOBKS (No-Block-Span)

Message Descriptions

Record size attribute: a decimal number from 1 to 32767
For more information about selecting keywords, refer to the OpenVMS System
Management Utilities Reference Manual.
BADVOLl, bad VOLl ANS label
Facility: MOUNT, Mount Utility
Explanation: The protection encoded on a magnetic tape volume label is
invalid or the label itself is invalid; the magnetic tape ACP cannot process the
tape. The tape is defective; it is not an ANSI-labeled tape, or the hardware
device is not reading the tape properly.
User Action: Verify the tape volume. If necessary, mount the tape as a
foreign volume and try to read it.
BADWCBPT, bad WCB pointer in IRP
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
BATCHNOOPR, no operator available to service batch request
Facility: MOUNT, Mount Utility
Explanation: The MOUNT request is aborted because the batch job requires
operator assistance and no operator is present.
User Action: Call the operator and retry the request.
BDPPURGERR, buffered datapath purge incomplete
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
BIIC failure - BICSR/BER/CNF 'xxxxxxxx/xxxxxxxx/xxxxxxxx'
Facility: VAXport Driver
Explanation: The port driver attempts to reinitialize the port; after 50 failed
attempts it marks the device off line.
User Action: Call Digital Services to check the port hardware.

Message Descriptions

BITMAPERR, I/O error on storage bitmap; volume locked
Facility: ·MOUNT, Mount Utility
Explanation: An I/O error is encountered during a mount operation.
Existing files on the volume can be accessed but other operations, for
example, CREATE and DELETE, are not possible.
User Action: Repair the volume using the Analyze/Disk_Structure utility.
BITMAPINV, storage bitmap is invalid, volume locked
Facility: MOUNT, Mount Utility
Explanation: The volume's storage bitmap contains invalid data.
User Action: Use the Analyze/Disk_Structure utility to repair the bitmap.
BLKZERO, block zero of 'device-name' is bad - volume not bootable
Facility: BACKUP, Backup Utility
Explanation: The boot block of the specified volume is not usable.
User Action: Note that the volume probably cannot be used as a system
volume for a VAX-11 processor model that requires access to the boot block
during a bootstrap operation.
BLOCKCRC, software block CRC error
Facility: BACKUP, Backup Utility
Explanation: An incorrect value occurred in the block CRC field of a
save-set block. Data in the save set is corrupt.
User Action: None. Save-set data has been lost.
BLOCKLOST, block of 'filespec' lost due to unrecoverable error
Facility: BACKUP, Backup Utility
Explanation: The Backup utility encountered an irrecoverable error
in reading the specified save set and cannot correct the error using the
redundancy information.
User Action: None. Save-set data has been lost.
BRDMSGLOST, broadcast queue pointer has no related entry
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
BUFFERSLOST, all buffers are lost
Facility: BACKUP, Backup Utility
Explanation: A software error occurred in the Backup utility.
User Action: Submit a Software Performance Report (SPR).

Message Descriptions

BVP failure - Status/Error/Data 'xxxxxxxx/xxxxxxxx/xxxxxxxx'
Facility: VAXport Driver
Explanation: The port driver attempts to reinitialize the port; after 50 failed
attempts, it marks the device off line.
User Action: Call Digital Services to check the port hardware.
BVP timeout - Status/Error/Data 'xxxxxxxx/xxxxxxxx/xxxxxxxx'
Facility: VAXport Driver
Explanation: The port driver attempts to reinitialize the port; after 50 failed
attempts, it marks the device off line.
User Action: Call Digital Services to check the port hardware.
Cables have gone from CROSSED to UNCROSSED
Facility: VAXport Driver
Explanation: The VAXport driver logs this event.
User Action: None.
Cables have gone from UNCROSSED to CROSSED
Facility: VAXport Driver
Explanation: The VAXport driver logs this event.
User Action: Check for crossed cable pairs.
CANTEXPREG, cannot expand virtual address space
Facility: BACKUP, Backup Utility
Explanation: Standalone BACKUP attempted unsuccessfully to expand its
virtual address space.
User Action: If this error can be reliably reproduced, the BACKUP
command used and a description of the circumstances should be submitted
along with a Software Performance Report (SPR).
CANTLOCK, cannot lock pages into memory. If the system disk goes off line,
reboot
Facility: BACKUP, Backup Utility
Explanation: Standalone BACKUP could not lock the required pages into
the working set.
User Action: Normally, no action is necessary. However, if the system disk
goes off line, it will be necessary to reboot the system. The operation of
standalone BACKUP is likely to be very slow because there is insufficient
memory to lock down a small portion of the working set.
CAPTIVE, qualifier not allowed in captive accounts
Facility: LOGIN, Login Procedure
Explanation: An attempt was made to use qualifiers (for example, /CLI
or /DISK) on an account logging in that is a captive account. If the account
logging in is a captive account, no qualifiers may be changed.
User Action: Retry without specifying qualifiers.

Message Descriptions

CD-ROM_HS, 'volnam': 'volsetnam' ( 'volnum' of 'volsetsiz' ), 'text'
Facility: MOUNT, Mount Utility
Explanation: This message identifies a High Sierra formatted CD-ROM
volume.
User Action: None.
CD-ROM_ISO, 'volnam': 'volsetnam' ( 'volnum' of 'volsetsiz' ), 'text'
Facility: MOUNT, Mount Utility
Explanation: This message identifies an ISO 9660 formatted CD-ROM
volume.
User Action: None.
CEBREFNEG, negative reference count on shared memory CEB
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
CHMONIS, change mode instruction while on interrupt stack
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
CHMVEC, CHM vector bits <1:0> not 0
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)

Message Descriptions

CIPORT, fatal error detected by CI port driver (PADRIVER)
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
CJFERR, journaling error; volume dismounted to ensure data integrity
Facility: MOUNT, Mount Utility
Explanation: The attempt to activate the recovery unit journal (RUJ) on the
volume failed. Because the RUJ might contain an active recovery unit, the
volume is dismounted to minimize the danger of corrupting the data on the
volume. This message is usually followed by another message that describes
the error condition that caused RUJ activation to fail.
User Action: Correct the error condition and reenter the MOUNT command,
or reenter the MOUNT command including the /NOJOURNAL qualifier. With
the latter approach, MOUNT will not attempt to activate the RUJ. This
approach removes the symptom but not the cause of the failure and may
leave the volume in an inconsistent state.
CLIFAIL, error activating command interpreter 'CLI-name'
Facility: LOGIN, Login Procedure
Explanation: An error occurred while attempting to invoke the specified
command interpreter for your process.
User Action: Ensure that the command interpreter image exists and that
the image file has read access.
CLIPROT, error protecting command interpreter pages
Facility: LOGIN, Login Procedure
Explanation: An error occurred while attempting to protect the command
interpreter pages. An accompanying message will provide more information.
User Action: Correct the problem described by the accompanying message
and try again.
CLISYMTBL, error creating space for command interpreter symbol table
Facility: LOGIN, Login Procedure
Explanation: There is not enough virtual address space available to create
the command interpreter symbol table.
User Action: Check that the system is set up with the value of
VIRTUALPAGECOUNT large enough to allow the CLI to be mapped.

Message Descriptions

CLITBLFAIL, error activating command interpreter tables 'table-name'
Facility: LOGIN, Login Procedure
Explanation: LOGIN cannot access the specified command language
interpreter tables.
User Action: Determine whether the specified tables exist and, if they do,
make sure they are not protected against system read access.
CLITBLPROT, error protecting command interpreter tables pages
Facility: LOGIN, Login Procedure
Explanation: An error occurred when the system tried to write-protect the
command interpreter table pages.
User Action: Try again. If the error reoccurs, report it to your system
manager.
CLUEXIT, node voluntarily exiting VA.Xcluster
Facility: BUGCHECK, System Bugcheck
Explanation: To avoid partitioning of the VMScluster, this system exited
the VMScluster by crashing. Generally, this is a normal condition. If the
condition persists, this processor may be configured incorrectly into two
distinct VMScluster systems. 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: Ensure that the VMScluster is properly configured.
CLUSTER, unsuitable cluster factor for 'device-name'
Facility: BACKUP, Backup Utility
Explanation: During an attempt to initialize an output volume, the Backup
utility found that the cluster factor was too large or too small for the specified
device.
User Action: If the input is a save set, use the BACKUP/LIST command to
determine the volume initialization parameters of the input volumes. Refer
to the description of the DCL command INITIALIZE, determine a suitable
cluster factor, and initialize the output volumes using the DCL command
INITIALIZE. Then, reenter the command specifying the /NOINITIALIZE
qualifier.
CMDERROR, error reported by command executor
Facility: LAT, LAT Facility
Explanation: The command executor module for LATCP cannot execute the
command for the reason given in the accompanying message.
User Action: Take appropriate action based on information in the
accompanying message.
CMDINPUT, error reading command input
Facility: LOGIN, Login Procedure
Explanation: An error occurred during the entry of the command; for
example, the timeout period following the prompt for user name or password
expired before a response was entered.
User Action: Repeat the login procedure.

Message Descriptions

CMDOBS, command obsolete - ignored
Facility: LAT, LAT Facility
Explanation: The specified LATCP command is obsolete; the command is
ignored.
User Action: Discontinue use of this command.
CMDOBS, MSCP server must be loaded by setting SYSBOOT parameter
MSCP_LOAD
Facility: SYSGEN, System Generation Utility
Explanation: The MSCP command within SYSGEN is now obsolete. The
proper way for loading the MSCP server is to set the SYSGEN parameter
MSCP_LOAD. This will load the MSCP server during SYSBOOT.
User Action: Setting the SYSGEN parameter to load the MSCP server
during SYSBOOT will result in a warning when the MSCP command
within SYSGEN is entered. If this error is printed as the result of a startup
command procedure, changing the parameter to load the server earlier will
enable the old command procedure to complete successfully with only a
warning message.
CMPOUTFll, /COMPARE requires save set as first input
Facility: BACKUP, Backup Utility
Explanation: In a compare operation between a save set and a disk volume,
you must specify the save set as the first input and the disk volume as the
second input.
User Action: Correct and reenter the command.
CNXMGRERR, error detected by VAXcluster Connection 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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
COMPARED, compared 'filespec'
Facility: BACKUP, Backup Utility
Explanation: The Backup utility successfully completed a compare
operation. This message is displayed only when the /LOG command qualifier
is used.
User Action: None.
CONNERR, error connecting to 'terminal-name'
Facility: LOGIN, Login Procedure
Explanation: An error occurred when the system attempted to reconnect to
the specified disconnected terminal.
User Action: Try again. If the error reoccurs, report it to your system
manager.
23

Message Descriptions

CONFIGURED, Configured device 'device'
Facility: !OGEN
Explanation: This message notes that the specified device has been
configured.
User Action: None.
CONFQUAL, conflicting qualifiers, request aborted
Facility: SYSGEN, System Generation Utility
Explanation: The SYSGEN command AUTOCONFIGURE is entered
specifying both the /EXCLUDE and /SELECT qualifiers.
User Action: Reenter the command with only one qualifier.
CONTINUE, unable to continue processing 'filespec'
Facility: BACKUP, Backup Utility
Explanation: The specified file, which is being processed at a change
of save-set volumes, is no longer accessible. The accompanying message
provides additional information and the Backup utility terminates processing
of the file. If other file activity is occurring on the volume, the error is
probably caused because another user deleted the file during the backup
process.
User Action: Note that the file is incompletely processed.
CONTINUED, 'save-set-spec' contains a continued file - cannot append
Facility: BACKUP, Backup Utility
Explanation: In a save operation with the /NOREWIND qualifier, the
specified volume contained a multivolume file that is continued on another
volume, and therefore a file cannot be appended to the volume.
User Action: Retry the operation using the /REWIND qualifier to force the
Backup utility to initialize the output volume or use another volume.
CONTRACT, contract virtual address space 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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
COPIED, copied 'filespec'
Facility: BACKUP, Backup Utility
Explanation: The Backup utility successfully completed a save operation.
This message is displayed only if the /LOG qualifier is specified.
User Action: None.

Message Descriptions

CORRUPTEMB, EMB packet header has been corrupted
Facility: BUGCHECK, System Bugcheck
Explanation: The system has detected corruption of the system error log
buffers. The system allocates space for error log entries from a set of common
buffers. System software that makes use of the error logging routines
typically writes into these entries. This message occurs when an attempt to
write into an error log entry has overwritten other parts of the system error
log buffers. The most common cause of this error is a coding error within a
device driver.
User Action: Submit a Software Performance Report (SPR) that includes
a backup save set of the system dump file generated by this error. (Use the
/IGNORE=NOBACKUP qualifier on the BACKUP command that produces
the save set included with your SPR.)
CPU ucode not at required rev level for port activity
Facility: VAXport Driver
Explanation: The port driver will not attempt to start the port.
User Action: On a VAX-11/750 system, make sure that the console TU58
is present and up to date. Otherwise, call Digital Services to check the port
hardware.
CPUCEASED, CPU ceased execution
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
CREDIR, created directory 'directory-name'
Facility: BACKUP, Backup Utility
Explanation: The Backup utility successfully created the directory
' directory' . This message is displayed only if the /LOG qualifier is specified.
User Action: None.
CREDIRERR, error creating directory 'directory-name'
Facility: BACKUP, Backup Utility
Explanation: The Backup utility encountered an error during an attempt to
create the specified directory. The accompanying message provides additional
information.
User Action: Correct the condition that caused the error and reenter the
command.
CREPARFIL, unable to create parameter file
Facility: SYSGEN, System Generation Utility
Explanation: An error occurred during a write operation.
User Action: Reenter the command so that you can write to the file.
25

Message Descriptions

CREPRCFL, Could not create new process
Facility: BACKUP, Backup Utility
Explanation: Standalone BACKUP could not create the necessary process to
perform the requested additional backup operation.
User Action: Reboot the system with standalone BACKUP in order to
perform further backup operations.
Datagram Free Queue Insert Failure
Facility: VAXport Driver
Explanation: The VAXport 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), or BI
(VAX 8200, VAX 8300, and VAX 8800) contention.
User Action: Call Digital Services.
Datagram Free Queue Remove Failure
Facility: VAXport Driver
Explanation: The VAXport 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), or BI
(VAX 8200, VAX 8300, and VAX 8800) contention.
User Action: Call Digital Services.
DBLERR, double error halt restart
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an irrecoverable hardware
error. Because of the severity of the error, further operation is impossible; or
if it is possible, it may corrupt user data. 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: Thoroughly test all system hardware components. If no
hardware errors are located and if the problem persists, submit a Software
Performance Report (SPR). The SPR should describe the conditions at the
time of the error, and should include a backup save set containing the system
dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command to produce the
save set.)
DECPTREF, decrement page table reference count 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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)

Message Descriptions

DEFCLI, you are not authorized to specify CLI parameters
Facility: LOGIN, Login Procedure
Explanation: Authorization is needed to specify an alternate command
language interpreter (CLI), or alternate CLI tables.
User Action: Log in again without specifying the /CLI or /TABLES qualifiers
after your user name.
DELCONPFN, fatal error in delete contents of PFN
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
DELETE, error deleting 'file-name' file ID ('numeric-string')
. Facility: BACKUP, Backup Utility
Explanation: An error is encountered during an attempt to delete the file
with the specified file identification in response to the /DELETE qualifier.
The accompanying message provides additional information.
User Action: None.
DELETED, previous Known File Entry has been deleted
Facility: INSTALL, Install Utility
Explanation: This message is displayed as the result of issuing a REPLACE
command in INSTALL. If the REPLACE command failed to create a new
Known File Entry for any reason, this message is displayed to explicitly
declare that the previous Known File Entry has been successfully removed.
This message is a warning explaining why even the old entry no longer exists
in case REPLACE failed to create a new entry.
User Action: None.
DELETESWL, 'device-name' is write protected - file deletion pass not executed
Facility: BACKUP, Backup Utility
Explanation: The input device is software write locked. The Backup utility
cannot perform the file deletion pass.
User Action: Dismount the input device, remount it writable, and either
delete the files by hand or reenter the BACKUP command.
DELGBLSEC, delete global section 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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
27

Message Descriptions

the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
DELGBLWCB, delete global section window 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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
DELPORT, deleted port 'port-name'
Facility: LAT, LAT Facility
Explanation: The specified port has been deleted by LATCP.
User Action: None.
DELSERVICE, deleted service 'service-name'
Facility: LAT, LAT Facility
Explanation: The specified service has been deleted by LATCP.
User Action: None.
DELWSLEX, delete working set list entry index 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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
DENSITY, 'saveset-spec' does not support specified density - default used
Facility: BACKUP, Backup Utility
Explanation: The specified tape hardware does not support the density
selected by the /DENSITY qualifier. The Backup utility uses the default
density.
User Action: Use a different tape device, or specify a different density.

Message Descriptions

DEQSUBLCKS, tried to dequeue lock with sublocks
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
DEVCOUNT, number of devices must match number of volumes
Facility: MOUNT, Mount Utility
Explanation: The number of devices specified in the DCL command
MOUNT to mount a disk volume set did not match the number of volume
labels specified in the command.
User Action: Check the command line. Verify the names of the devices
and volume labels for the command and then reenter the command with a
matching number of devices and volume labels.
DEVICES, only one device allowed
Facility: MOUNT, Mount Utility
Explanation: More than one device was specified in the DCL command
MOUNT. Only one volume at a time can be mounted for this specified type of
MOUNT.
User Action: Reenter the DCL command MOUNT specifying only one
device.
DEVNOTKNWN, device not known: 'input'
Facility: SYSGEN, System Generation Utility
Explanation: The specific device was unknown when the SYSGEN command
CONFIGURE was entered.
User Action: See the OpenVMS VAX Device Support Manual for the correct
UNIBUS controller name.
DIAGPACK, disk is a diagnostic pack
Facility: BACKUP, Backup Utility
Explanation: Either a Backup utility operation attempted to use a volume
identified as a diagnostic volume, or the DCL command INITIALIZE was
entered to initialize a volume that is identified as a diagnostic volume. In
either case, the volume cannot be used.
User Action: Retry the operation using another volume.

Message Descriptions

DIRENTRY, ACP failed to find same directory entry
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
DISKCLASS, fatal error detected by Disk Class driver (DUDRIVER)
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
DISKFRAG, free space on 'device-name' is too fragmented
Facility: BACKUP, Backup Utility
Explanation: The number of free extents on the specified volume is
unreasonably large. The volume cannot be used as a save-set disk.
User Action: Reinitialize the volume or select another volume and retry the
operation.
DISMAL, all of the volumes have been dismounted
Facility: MOUNT, Mount Utility
Explanation: All of the volumes mounted by this invocation of $MOUNT
or the MOUNT command have been dismounted because of errors that were
detected after the volumes had been mounted. Messages explaining the
nature of the error that forced the dismount usually precede this message.
User Action: Take the corrective measures mandated by the error messages
preceding DISMAL, and reenter the MOUNT command.
DISMOUNTD, volume 'volume-name' of volume-set 'volume-set-name'
dismounted
Facility: MOUNT, Mount Utility
Explanation: The specified volume of the specified volume set has been
dismounted because of errors encountered in processing the volume after it
is mounted. An error with part of a volume set causes the entire volume set
to be dismounted. This message appears for each member of the volume set
that is dismounted due to the error condition. Only those volumes that were
mounted by this invocation of the MOUNT command are listed. If the volume
set name is not available, the string name n/a appears as the name of the
volume set.
11

Message Descriptions

A message describing the error that caused the volume to be dismounted
usually precedes this message.
User Action: Correct the error condition specified in the accompanying
message and reenter the MOUNT command.
DISMPART, some of the volumes have been dismounted
Facility: MOUNT, Mount Utility
Explanation: Some of the volumes that were mounted by this invocation
of the Mount utility or the MOUNT command have been dismounted due to
errors detected after the volumes had been mounted. Preceding messages
explain the nature of the error that forced the dismount. Also preceding this
message is a list of the volumes that were dismounted.
User Action: Take the corrective measures mandated by the error messages
preceding DISMPART, and reenter the MOUNT command.
DISRECONNECT, you are not authorized to do reconnections
Facility: LOGIN, Login Procedure
Explanation: Authorization is needed to reconnect to disconnected processes.
User Action: Log in again without specifying the /CONNECT qualifier after
your user name.
DISUSER, account is disabled
Facility: LOGIN, Login Procedure
Explanation: An attempt is made to log in to an account when the account
is disabled. An account's system access can be restricted by setting the
DISUSER flag in the user authorization file. This message is written to
the system accounting and security audit records; the NOTVALID message
displays to the user.
User Action: None.
DOUBLDALOC, double deallocation of swap file space
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
DOUBLDEALO, double deallocation of memory block
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.

Message Descriptions

(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
DRIVENAM, driver name is 'driver-name'
Facility: SYSGEN, System Generation Utility
Explanation: This message is issued with the message SYSVERDIF to
identify the driver.
User Action: See the SYSGEN message SYSVERDIF for user action
information.
DUALLOC, dual allocation on volume 'n'
Facility: MOUNT, Mount Utility
Explanation: A logical block on the relative volume identified in the
message is allocated to more than one file.
User Action: Use the DCL command ANALYZE/DISK_STRUCTURE
/NOREPAIR for the volume. This command invokes the Analyze/Disk_
Structure utility, which issues a message for each occurrence of dual file
allocation. These messages identify the file name, the range of logical block
numbers that have been duly allocated, and the virtual block numbers that
the logical blocks map to. The messages can be examined to determine the
files involved in each case of dual allocation. Then, without allowing other
file activity, copy all but one file involved in each case of dual allocation to a
new version. After new versions of the applicable files are created, delete the
versions containing dual allocation. In this way, blocks that are not actually
free are marked as free blocks in the storage bit map. Next, rerun the utility
on the volume, using the ANALYZE/DISK_STRUCTURE/REPAIR command.
Finally, examine each file and reconstruct from backup media those files that
have been corrupted.
Dump aborted, page tables may be corrupted
Facility: BUGCHECK, System Bugcheck
Explanation: When writing a selective dump (SYSGEN parameter
DUMPSTYLE set to 1), the OpenVMS operating system relies heavily on
the integrity of the various system and process page tables. This message
indiCates that the system might have detected corruption in these page
tables, and it will abort further dumping. You might not be able to analyze
the dump.
User Action: Submit a Software Performance Report (SPR).
DUPDEVSPC, duplicate device specified
Facility: MOUNT, Mount Utility
Explanation: The same tape device is specified more than once in a list of
tape devices for the DCL command MOUNT.
User Action: Reenter the MOUNT command specifying each device only
once.
DUPLABEL, duplicate label 'label' not allowed with /EXACT_ORDER qualifier
Facility: BACKUP, Backup Utility
Explanation: Duplicate labels cannot be specified with the /EXACT_ORDER
qualifier. The specified label matches' a label that was entered previously.
User Action: Reenter the command specifying one or more unique labels.

Message Descriptions

DUPRVN, duplicate volume number already mounted
Facility: MOUNT, Mount Utility
Explanation: A volume of the same relative volume number and the same
volume set name is already mounted. An attempt is being made to mount a
volume that belongs to a volume set with the same name as a volume set that
is already mounte~.
User Action: Make sure that the correct volume has been mounted. Verify
that the volume status (!SHARE, /NOSHARE, /GROUP, or /SYSTEM) is
defined consistently with volumes already mounted.
DUPVOLNAM, volume label already present in set
Facility: MOUNT, Mount Utility
Explanation: During an attempt to add a volume to an existing volume set,
the specified volume set is found to contain a volume with the label specified.
User Action: Verify the labels on the existing volumes in the set. Choose a
new label for the volume you are adding to the set, reinitialize the volume,
and reenter the DCL command MOUNT/BIND.
EMPTYFILE, zero-length page or swap file cannot be installed
Facility: SYSGEN, System Generation Utility
Explanation: An attempt was made to install a zero-length page or
swapping file, which cannot be installed.
User Action: None.
EMPTYLST, Known File Entry List is empty
Facility: INSTALL, Install Utility
Explanation: There are no entries in the known file entry list. Therefore,
LIST, DELETE, REMOVE, and PURGE will have no effect.
User Action: None.
EOFMISMATCH, end of file position mismatch for 'filespec'
Facility: BACKUP, Backup Utility
Explanation: During a compare or verify operation, the end-of-file pointer
for the specified file did not agree with the input file. If other file activity
is occurring on the volume, the error may be caused because another user
modified the file during the backup operation.
User Action: Note that the copies are inconsistent.
EQV_NOTICE, equivalent name - device 'controller-name' will be output as
'controller-name'
Facility: SYSGEN, System Generation Utility
Explanation: An equivalent name for a controller is entered with the
SYSGEN command CONFIGURE. This message is informational.
User Action: None.

Message Descriptions

ERASEBLKS, blocks reclaimed on relative volume N not completely erased
Facility: MOUNT, Mount Utility
Explanation: While rebuilding a volume set, some of the blocks being
reclaimed could not be erased. The accompanying message provides
additional information.
User Action: Take appropriate action based on information in the
accompanying message.
ERRCACHFUL, error cache is full
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 will automatically reboot if the BUGREBOOT system parameter is set
to 1.
User Action: Submit a Software Performance Report (SPR) describing the
conditions leading to the error. In the SPR, include a listing of the backup
save set containing the system dump file and the error log file active at
the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the
BACKUP command that produces the save set included with the SPR.)
ERRHALT, halt with error interrupt pending
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 will automatically reboot if the BUGREBOOT system parameter is set
to 1.
User Action: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
Error reporting suppressed, memory dump continuing
Facility: BUGCHECK, System Bugcheck
Explanation: This message indicates that too many errors occurred while
writing a dump to the disk; it is no longer appropriate to continue to send
messages for each error, and error reporting is suppressed. The system
continues to attempt to write the dump.
User Action: When the system reboots, copy the dump to another file.
Determine the text associated with the hexadecimal statuses of previous
messages by using the F$MESSAGE lexical function or its equivalent. If
the status indicates a possible disk problem, see the user action for the
accompanying message.
Error writing 'nn' block(s), starting at vbn 'vv' - status = 'ss'
Facility: BUGCHECK, System Bugcheck
Explanation: An error occurred while writing a dump to the disk. The
status is the error returned by the QIO$ system service that attempted the
write operation. The system continues to attempt to write the dump.
User Action: When the OpenVMS operating system reboots, copy the dump
to another file. Determine the text associated with the hexadecimal status

Message Descriptions

by using the F$MESSAGE lexical function or its equivalent. If the status
indicates a possible disk problem, see the user action for the accompanying
message.
EVADE, breakin evasion in effect
Facility: LOGIN, Login Procedure
Explanation: Access to an account is denied because break-in evasion is in
effect for that account. This message is written to the system accounting and
security audit records; the NOTVALID message displays to the user.
User Action: None.
EXHFUL, file extension header has no room
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 will automatically reboot if the BUGREBOOT system parameter is set
to 1.
User Action: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
EXISTS, Known File Entry for a version of this. file already exists
Facility: INSTALL, Install Utility
Explanation: A known file entry already exists for this file name on the
specified device and directory.
User Action: Contact your system manager.
EXLABELERR, volume label processing failed because 'reason'
Facility: BACKUP, Backup Utility
Explanation: The BACKUP command specified /EXACT_ORDER for label
processing and one of the following problems was detected in the label
comparison of the mounted tape volume:
•

The volume label of the mounted tape has already been used in the
backup operation.

•

The volume label of the mounted tape is not the expected label, according
to the order of volumes listed in the /LABEL qualifier.

An accompanying message explains why label processing failed.
User Action: Take action based on the accompanying message. Depending
upon the reason for the failure, you can take one of the following actions:

•

Quit the operation.

•

Put a new volume in the drive and continue processing.

•

Overwrite the volume label and continue processing.

•

Use the tape that you have mounted.

If the mounted volume has a label that was used previously in the backup
operation, your only options are to quit the operation or load a new tape to
avoid losing data.

Message Descriptions

EXLICENSE, licensed number of system users exceeded
Facility: LOGIN, Login Procedure
Explanation: The maximum number of interactive users for which your
system is licensed have already logged in. Further logins are currently
disabled.
User Action: Log in after another user has logged off. If the maximum
number of users is exceeded frequently, ask your system manager whether
the system's license can be upgraded.
EXPANDPHD, expand process header 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 will automatically reboot if the BUGREBOOT system parameter is set
to 1.
User Action: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
EXQUOTA, maximum number of users exceeded - try again later
Facility: LOGIN, Login Procedure
Explanation: The installation-defined maximum number of users has been
reached.
User Action: Wait and try to log in later, after other users have logged out.
EXTCACHIV, contents of extent cache is garbage
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 will automatically reboot if the BUGREBOOT system parameter is set
to 1.
User Action: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
EXTENDED, 'filespec' extended
Facility: SYSGEN, System Generation Utility
Explanation: This message is the result of the SYSGEN command CREATE
and indicates that the specified file has been extended.
User Action: No action is required.

Message Descriptions

FACTBAD, cannot read factory bad block data
Facility: BACKUP, Backup Utility
Explanation: Either the Backup utility or the DCL command INITIALIZE
encountered an error during an attempt to read the bad block data recorded
on the specified volume. An accompanying message provides additional
information.
User Action: Either correct the condition that caused the error and reenter
the command, or notify the system manager. If the volume is under warranty,
it should be returned to the factory. Contact Digital Services if necessary.
FAIL, failed to 'execute-verb' entry for 'filespec'
Facility: INSTALL, Install Utility
Explanation: A failure to ADD, CREATE, DELETE, REMOVE, or
REPLACE a known file entry occurred. An accompanying error message
explains the failure.
User Action: Correct the situation indicated by the accompanying error
message and reenter the command.
FAILED, failed to perform 'execute-verb' operation
Facility: INSTALL, Install Utility
Explanation: A PURGE or listing operation failed to execute completely. An
accompanying message explains the failure.
User Action: Correct the situation indicated by the accompanying error
message and reenter the command.
Failed to Locate Port Micro-code Image
Facility: VAXport Driver
Explanation: The port driver will not start the port.
User Action: Make sure that the console load media is present in the
console drive, and reboot the system.
FAILGETVM, failed to allocate 'nn' bytes of virtual memory
Facility: INSTALL, Install Utility
Explanation: INSTALL failed to allocate sufficient work space for itself.
Either your PGFLQUO value is too low for your account, or the system's
VIRTUALPAGECNT SYSGEN parameter is too low.
User Action: Contact your system manager.
FATALERR, fatal error on· 'save-set-spec'
Facility: BACKUP, Backup Utility
Explanation: The Backup utility encountered an irrecoverable error during
an attempt to read or write the specified save set. The accompanying message
provides additional information.
User Action: Correct the condition that caused the error and reenter the
command.

Message Descriptions

FATALERR, fatal error reading startup database
Facility: STDRV, System Startup Driver
Explanation: The startup driver encountered a fatal error while trying to
read the startup database files. The startup operation is aborted. If this
message occurs during a system reboot, the OpenVMS software may not have
been properly started.
User Action: Verify that the startup databases, defined by the logical
names STARTUP$STARTUP_VMS, STARTUP$STARTUP_LAYERED, and
STARTUP$PHASES, are all available and can be accessed.
FATALEXCPT, fatal executive or kernel mode exception
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an unrecoverable,
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
FIDERROR, unexpected file change in 'filespec'
Facility: BACKUP, Backup Utility
Explanation: A file boundary marker is missing from the input save set.
Data in the save set may be corrupt. It is likely that parts of the specified file
and one or more complete files are missing.
User Action: Examine the file for corruption and reconstruct as necessary. If
this error occurs during a disk-to-disk (copy) operation, it indicates a software
error in the Backup utility; in this case, submit a Software Performance
Report (SPR).
FIDNOTFND, internal error. File to be processed not found on process list
Facility: BACKUP, Backup Utility
Explanation: The file context has been lost. This is an internal error.
User Action: If this error can be reliably reproduced, the BACKUP
command that was used and a description of the circumstances should be
submitted along with a Software Performance Report (SPR).
FILCNTNONZ, open file count nonzero after process rundown
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an unrecoverable,
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)

Message Descriptions

FILEACC, error accessing system authorization file
Facility: LOGIN, Login Procedure
Explanation: An error occurred while attempting to access the authorization
file.
User Action: The system manager should ensure that the
SYS$SYSTEM:SYSUAF.DAT file exists and has system read access.
Then the user can retry the login procedure.
FILNOPOST, file will not be subject to date-recording or deletion
Facility: BACKUP, Backup Utility
Explanation: This is a warning message indicating that BACKUP will not
post-process the file because its contents were not successfully verified.
User Action: Determine why the file could not be successfully verified and
retry the backup operation.
FILNOTEXP, file is not expired
Facility: MOUNT, Mount Utility
Explanation: A tape file cannot be overwritten because it has not reached
its expiration date.
User Action: To overwrite or delete the file, mount the volume with the
/OVERRIDE=EXPIRATION qualifier. You must be the owner of the volume
or have volume protection (VOLPRO) privilege.
FNF, file not found
Facility: SYSGEN, System Generation Utility
Explanation: SYSGEN is unable to locate the driver image file. The default
directory and disk device for driver images is SYS$SYSTEM. This message is
also produced during an AUTOCONFIGURE operation if a UNIBUS device
does not have a corresponding driver in SYS$SYSTEM.
User Action: Restore the image file to the system disk from a backup disk.
FRCPWDERR, error changing expired password
Facility: LOGIN, Login Procedure
Explanation: An error occurred while changing an expired password. This
message is usually accompanied by an additional message describing the
exact cause of the error.
User Action: Take appropriate action based on information in the
accompanying message.
FREEBADBUF, attempted to free busy (or free) buffer
Facility: BACKUP, Backup Utility
Explanation: A software error occurred in BACKUP.
User Action: Submit a Software Performance Report (SPR).
FREEMEM, error freeing virtual memory
Facility: BACKUP, Backup Utility
Explanation: An error was encountered during an attempt to free dynamic
virtual memory. An accompanying message provides additional information.
This message indicates a software error in the utility that produced it.
User Action: Submit a Software Performance Report (SPR).

Message Descriptions

FREEPAGREF, free page reference count is nonzero
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an unrecoverable,
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
FREWSLX, free working set list index, resource wait
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an unrecoverable,
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produce~ the save set included with the SPR.)
GBLPAGSZRO, Global page share count is zero
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
GBLWSLXERR, Global working set list entry not found
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)

Message Descriptions

GENMINUSl, shadow set virtual unit generation number invalid on 'device'
Facility: BACKUP, Backup Utility
Explanation: An attempt was made to use BACKUP on a member of a
shadow set which has not yet been fully formed.
User Action: Wait for the shadow set to be fully formed and retry the
backup operation.
GETCHN, error getting device characteristics for 'device-name'
Facility: BACKUP, Backup Utility
Explanation: The Backup utility encountered an error during an attempt
to obtain the device characteristics of the input device. The accompanying
message provides additional information.
User Action: Correct the condition that caused the error and reenter the
command.
GPGNULPGFL, global page has null page file address
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
HALT, halt instruction restart
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 automaticallys reboot if the BUGREBOOT system parameter is set
to 1.
User Action: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
HDRCRC, software header CRC error
Facility: BACKUP, Backup Utility
Explanation: An incorrect value occurred in the header CRC field
(BBH$W_CHECKSUM) of a save-set block. Data in the save set is corrupt.
User Action: None. The save-set data is lost.

Message Descriptions

HDRNOTMAP, allocated file header not mapped
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
HDRNOTRES, unable to make image header resident
Facility: INSTALL, Install Utility
Explanation: Insufficient pool is available to make the header resident, or
the file has an image header larger than one block.
User Action: Use the SYSGEN parameter PAGEDYN to increase the pool.
Only files with one block image headers may be made resident.
HEADCOPIED, copied 'file-header' header
Facility: BACKUP, Backup Utility
Explanation: The /LOG message indicating that a file header only is copied.
The file is marked NOBACKUP; therefore, no data is saved.
User Action: None.
HELP, enter HELP for INSTALL help
Facility: INSTALL, Install Utility
Explanation: This message is informational.
User Action: Enter HELP for INSTALL help.
High Priority Command Queue Insert Failure
Facility: VAXport Driver
Explanation: The VAXport driver attempts to reinitialize the port; after 50
failed attempts it marks the device off line.
User Action: Call Digital Services. 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), or BI
(VAX 8200, VAX 8300, and VAX 8800) contention.
HOMBLKBAD, primary home block is bad; backup used
Facility: MOUNT, Mount Utility
Explanation: The primary home block of a disk is corrupt or unreadable;
the backup volume is used to mount the volume.
User Action: Repair the disk using the Analyze/Disk_Structure utility.

Message Descriptions

HOMBLKCHK, home block software consistency check
Facility: MOUNT, Mount Utility
Explanation: The home block in the volume failed the software consistency
check during /BIND processing. The first occurrence of this message is a
warning; the second is fatal.
User Action: Repair or reinitialize the volume and retry the operation.
HSC Error Logging Datagram Received
Facility: VAXport Driver
Explanation: Upon receiving an error message from the HSC, the CI port
driver logs the error and takes no other action. Since HSC informational
error log datagrams are also recorded on the HSC console, it is useful to read
them only if the HSC console does not record them for some reason (if it runs
out of paper, for example).
User Action: The sending of HSC informational error log datagrams
should be disabled with the appropriate HSC console command, since HSC
informational error log datagrams take up considerable space in the error log
data file.
ICONCLUDAT, inconsistent cluster data base
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
ICONPFNDAT, inconsistent PFN data base
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
ICPAGELOC, inconsistent page location
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing

Message Descriptions

the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
ID ENT, standalone BACKUP ' string' ; the date is ' date and time'
Facility: BACKUP, Backup Utility
Explanation: This is a standalone backup identification message.
User Action: Make sure that the displayed data is correct.
IDXHDRBAD, index file header is bad; backup used
Facility: MOUNT, Mount Utility
Explanation: This message is generated by the DCL command MOUNT.
The primary index file header is corrupt or unreadable; the backup volume is
used to mount the volume.
User Action: Repair the volume with the ANALYZE/DISK_STRUCTURE
/REPAIR command.
IDXMAPERR, I/O error on index file bitmap; volume locked
Facility: MOUNT, Mount Utility
Explanation: I/O error encountered during a mount operation. Existing files
in the volume can be accessed but other operations (for example, create and
delete) are not possible.
User Action: Repair the volume with the ANALYZE/DISK_STRUCTURE
/REPAIR command.
IFREPAGCNT, inconsistent free page count
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
ILLANSIBS, ANS magnetic tape block size must be at least 18 characters
Facility: MOUNT, Mount Utility
Explanation: The label specified for a magnetic tape contains less than 18
characters.
User Action: Reenter the command; specify a minimum value of 18 for the
block size.

Message Descriptions

ILLEVTNUM, illegal event number
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
ILLOPT, qualifiers not appropriate to this device
Facility: MOUNT, Mount Utility
Explanation: A DCL MOUNT or INITIALIZE command specified qualifiers
that apply only to disk devices for a tape device, or qualifiers that apply only
to tape devices for a disk device.
User Action: Use the DCL command HELP or refer to the Open VMS
DCL Dictionary for a list of qualifiers, and reenter the command with the
appropriate qualifiers.
ILLQUAL, invalid qualifier
Facility: MOUNT, Mount Utility
Explanation: An invalid qualifier is given in the command.
User Action: Replace the qualifier and reenter the command.
ILLVEC, illegal interrupt or exception vector restart
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
IMGFILSPE, /IMAGE specification must have only device name
Facility: BACKUP, Backup Utility
Explanation: The file specification for a volume to be processed with the
/IMAGE qualifier must contain only a device name.
User Action: Reenter the command using the device name only.
IMGHDR, error while accessing image header
Facility: INSTALL, Install Utility
Explanation: INSTALL encountered an error when trying to access the
image header. An accompanying error message explains the failure.
User Action: Correct the situation indicated by the accompanying error
message and reenter the command.

Message Descriptions

IMGTRACED, /TRACEBACK image cannot be privileged or execute_only
Facility: INSTALL, Install Utility
Explanation: This message indicates that an attempt is made to CREATE
or REPLACE a known file image with either the /PRIVILEGE or /EXECUTE_
ONLY qualifiers, and that the image had been linked with the /TRACEBACK
qualifier.
User Action: Relink the image using the /NOTRACEBACK qualifier and
retry the image installation.
Inappropriate SCA Control Message
Facility: VAXport Driver
Explanation: The VAXport driver closes the port-to-port virtual circuit to
the remote port.
User Action: Submit a Software Performance Report (SPR) including the
error logs and the crash dumps from the local and remote systems.
INCBADDIR, saved directory 'directory-name' has invalid format
Facility: BACKUP, Backup Utility
Explanation: In response to the /INCREMENTAL qualifier, the saved copy
(in the input save set) of the specified directory is not in the expected format
for a directory file. The file may have been corrupt when it was saved, or save
set data may have been lost.
User Action: After the incremental restoration is complete, check the files
for correct format.
INCDELERR, error deleting 'file-name'
Facility: BACKUP, Backup Utility
Explanation: An error is encountered during an attempt to delete the
specified file in response to the /INCREMENTAL qualifier. The accompanying
message provides additional information.
User Action: Correct the condition that caused the error and reenter the
command.
INCDELETE, deleted 'file-name'
Facility: BACKUP, Backup Utility
Explanation: The Backup utility deleted the specified file in response to the
/INCREMENTAL qualifier. This message appears if the /LOG qualifier is
specified.
User Action: None.
INCDEVLIS, disk and tape devices mixed in list
Facility: BACKUP, Backup Utility
Explanation: Disk and tape devices were mixed in a list of file specifications.
User Action: Reenter the command ensuring that if a list is used, the
devices in a list are the same type.

Message Descriptions

INCENTERR, error creating directory entry for 'file-name'
Facility: BACKUP, Backup Utility
Explanation: The Backup utility encountered an error during an
attempt to create a directory entry for the specified file in response to the
/INCREMENTAL qualifier.
User Action: Correct the condition that caused the error and reenter the
command.
INCFILATR, incomplete file attribute data for 'file-name'
Facility: BACKUP, Backup Utility
Explanation: There is an unexpected change in the file identifier and the file
attribute data is incomplete for the specified file. BACKUP tried to restore
a selected file from a save set, but the mounted volume did not contain the
beginning of the file.
User Action: Retry the backup operation using the volume which contains
the beginning of the selected file as input.
INCFILSPE, /INCREMENTAL specification must have only device name
Facility: BACKUP, Backup Utility
Explanation: The file specification for a volume to be processed with the
/INCREMENTAL qualifier must contain only a device name.
User Action: Reenter the command using only the device name.
INCMEMNAM, specified shared memory name does not match
Facility: SYSGEN, System Generation Utility
Explanation: The logical name assigned to the shared memory by the
SYSGEN command SHARE does not match the name in the database of
shared memory that was previously specified.
User Action: Reenter the command with the correct name.
INCOMPACP, indicated ACP is incompatible with 'volume'
Facility: MOUNT, Mount Utility
Explanation: The ACP specified is not an ACP for the requested device.
User Action: Reenter the command; specify an ACP that is appropriate for
the particular device type.
INCOMPAT, qualifiers incompatible with already mounted volume
Facility: MOUNT, Mount Utility
Explanation: A DCL command MOUNT is entered to mount a shareable
volume that is already mounted; the characteristics of the volume are already
established and cannot be changed.
User Action: Use the DCL command SHOW DEVICE to determine how the
volume is mounted. Reenter the DCL command MOUNT/SHARE without
qualifiers.

Message Descriptions

INCONQUALS, qualifier '/qualifier' contradicts qualifier '/qualifier'
Facility: BACKUP, Backup Utility
Explanation: The two qualifiers specified are in conflict with one another
and cannot be used together in the BACKUP command.
User Action: Reenter the BACKUP command with only one of the two
qualifiers. For more information about how qualifiers affect the BACKUP
command, see the Open VMS System Management Utilities Reference Manual.
INCONSDEV, inconsistent device types
Facility: MOUNT, Mount Utility
Explanation: Both disks and magnetic tapes appear in the list of devices to
be mounted.
User Action: Specify one or the other and reenter the command; check the
logical name assignments.
INCONSTATE, inconsistent I/O data base
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
INCPTREF, increment page table reference count 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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
INCRVN, incorrect relative volume mounted on 'device-name'
Facility: BACKUP, Backup Utility
Explanation: Either the wrong volume of a multivolume disk save-set was
mounted, or the positional order of the devices in the input specification does
not agree with the relative volume numbers recorded on the volumes.
User Action: Locate and mount the correct volume.
INCSETCNT, incorrect number of devices in input specification
Facility: BACKUP, Backup Utility
Explanation: The number of devices in the input specification does not
agree with the volume set count recorded on relative volume 1.
User Action: Reenter the command with the correct number of devices.
48

Message Descriptions

INDEXTOSM, index file is too small on output device 'device-name'
Facility: BACKUP, Backup Utility
Explanation: The /NOINITIALIZE qualifier was specified on the output disk
for an image backup, but the size of INDEXF.SYS on the output disk cannot
accommodate the number of files on the input disk.
User Action: Initialize the output disk and increase the number of headers
on the disk by using the /HEADERS and IMAXIMUM_FILES qualifiers on
the INITIALIZE command. The output disk must contain as many or more
headers as there are files on the input disk.
INPUTERR, error opening primary input file SYS$INPUT
Facility: LOGIN, Login Procedure
Explanation: The system cannot open the current input device and cannot
perform the login. This message is usually accompanied by another message
indicating the reason for the failure.
User Action: Take corrective action based on the accompanying message,
and repeat the login procedure.
INSFMEM, insufficient dynamic memory
Facility: SYSGEN, System Generation Utility
Explanation: There is not enough room in the nonpaged pool to load a
driver or create a control block for it. If this message is associated with a
vector disabled (VECDIS) status code, the current process issued a vector
instruction, but insufficient system nonpaged dynamic memory exists to
establish the process as a vector consumer.
User Action: Reboot the system, stopping in SYSBOOT, and increase the
value of the parameter NPAGEDYN.
INSNFREPAG, insufficient nonfree pages
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
INSRES, insufficient resources to complete operation
Facility: LAT, LAT Facility
Explanation: The system does not have enough resources to service the user
request.
User Action: Contact the system manager to determine which system
resource is inadequate.

Message Descriptions

INSSWPFIL, insufficient swap file space
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
Insufficient Non-paged Pool for Initialization
Facility: VAXport Driver
Explanation: The port driver will not attempt to start the port.
User Action: Increase the NPAGEDYN pool SYSGEN parameter and reboot
the system.
Insufficient Non-paged Pool for Virtual Circuits
Facility: VAXport Driver
Explanation: After finding that insufficient memory resources are available
for normal communication, the port driver breaks a virtual circuit.
User Action: Increase the NPAGEDYN pool SYSGEN parameter and reboot
the system.
INSWAPERR, inswap read 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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
INTRNLERR, Internal Error: 'code'
Facility: INSTALL, Install Utility
Explanation: INSTALL encountered an internal error.
User Action: Submit a Software Performance Report (SPR).
INVADAP, invalid adapter name specified
Facility: SYSGEN, System Generation Utility
Explanation: The specified adapter number is found to be invalid after
bootstrap.
User Action: Reenter the command using the correct adapter number.

Message Descriptions

INVATTSIZ, invalid attribute record size in save set
Facility: BACKUP, Backup Utility
Explanation: An incorrect value occurred in the attribute size field of a
save-set record. Data in the save set is corrupt.
User Action: None. Save-set data has been lost.
INVATTSTR, invalid attribute record structure level in save set
Facility: BACKUP, Backup Utility
Explanation: An incorrect value occurred in the structure level field of a
save-set record. Data in the save set is corrupt.
User Action: None. Save-set data has been lost.
INVATTVAL, invalid attribute record value in save set
Facility: BACKUP, Backup Utility
Explanation: An incorrect value occurred in a save-set attribute record.
Data in the save set is corrupt.
User Action: None. Save-set data has been lost.
INVBJLEOF, invalid end of file position in BACKUP journal
Facility: BACKUP, Backup Utility
Explanation: The end-of-file pointer recorded for the journal file specified by
the /JOURNAL qualifier is invalid. The journal file is corrupt and cannot be
used.
User Action: Reconstruct the journal file from backup media.
INVBJLSIZ, invalid record size in BACKUP journal
Facility: BACKUP, Backup Utility
Explanation: An invalid record size occurred in the journal file specified by
the /JOURNAL qualifier. The journal file is corrupt and cannot be used.
User Action: Reconstruct the journal file from backup media.
INVBJLSTR, invalid structure level in BACKUP journal
Facility: BACKUP, Backup Utility
Explanation: The structure level recorded in the journal file specified by
the /JOURNAL qualifier is invalid. The journal file is corrupt and cannot be
used.
User Action: Reconstruct the journal file from backup media.
INVBJLTYP, invalid record type in BACK.UP journal
Facility: BACKUP, Backup Utility
Explanation: An invalid record type occurred in the journal file specified by
the /JOURNAL qualifier. The journal file is corrupt and cannot be used.
User Action: Reconstruct the journal file from backup media.
INVBLKHDR, invalid block header encountered in save set
Facility: BACKUP, Backup Utility
Explanation: An incorrect value occurred in the block header of a save-set
block. Data in the save set is corrupt.
User Action: None. Save-set data is lost.

Message Descriptions

INVBLKSIZE, invalid block size in save set
Facility: BACKUP, Backup Utility
Explanation: An incorrect value occurred in the block size field of a save-set
block. Data in the save set is corrupt.
User Action: None. Save-set data is lost.
INVCHAN, invalid ACP channel number
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
INVCJFIOD, invalid IO database structure (journaling)
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
INVCMD, invalid command
Facility: LAT, LAT Facility
Explanation: The specified LATCP command was invalid for the reason
given in an accompanying message.
User Action: Take appropriate action based on information in the
accompanying message.
INVDEVTYP, invalid backup device type 'filespec'
Facility: BACKUP, Backup Utility
Explanation: The specified device must be a disk or tape device.
User Action: Reenter the command.
INVDPT, invalid driver image - DPT$_TYPE, VBN 2 .NEQ.DYN$C_DPT
Facility: SYSGEN, System Generation Utility
Explanation: The driver image file specified in a SYSGEN command LOAD,
RELOAD, or CONNECT did not pass a basic validity check. This error can
be caused by one of the following conditions:

•

Not having the driver prologue table (DPT) as the first code-generating
component of the driver

•

Not linking the driver as an executable image based at zero

Message Descriptions

•

Having PSECT statements in the driver program

•

Any other problem that causes the driver prologue table not to be in the
second block (VBN 2) of the image file

User Action: Correct the driver code and reenter the command.
INVDPTINI, invalid driver prologue init table value
Facility: SYSGEN, System Generation Utility
Explanation: One of the following conditions exists:
•

The initialization or reinitialization entry in the driver prologue table has
an invalid control block type code; that is, one other than DDB, UCD,
CRB, or IDB.

•

The initialization or reinitialization entry in the driver prologue table has
an invalid store function; that is, one other than B, W, L, R, V, @B, @W,
@L, @R, or @V.

User Action: Correct the DPT_STORE macro in the driver prologue table.
INVEXCEPTN, exception while above ASTDEL or on interrupt stack
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
INVFID, invalid file id in save set - cannot restore /IMAGE
Facility: BACKUP, Backup Utility
Explanation: An attempt is made to restore a file with a zero file
identification in /IMAGE mode. This may occur if the save set is written by a
non OpenVMS operating system.
User Action: Use a non /IMAGE mode to restore the file.
INVFILEXT, invalid file extension linkage in 'filespec'
Facility: BACKUP, Backup Utility
Explanation: The specified save set file has an invalid pointer to a following
segment of the file. The remainder of the file is not accessible.
User Action: Attempt to recover data by beginning a restore operation with
the first unprocessed file segment.
INVHOMBLK, 'device-name' has invalid home block
Facility: BACKUP, Backup Utility
Explanation: The specified volume has an invalid Files-11 home block.
User Action: Repair the volume using the Analyze/Disk_Structure utility.

Message Descriptions

INVINPUT, invalid SYS$INPUT for interactive login
Facility: LOGIN, Login Procedure
Explanation: SYS$INPUT is a logical name for the input from a process to
the system. When the system is used interactively, SYS$INPUT is assigned
to your terminal by default. The system then acts upon the input it receives
from your terminal. During your process, you can redefine SYS$INPUT
to a data file; the system will then read input from the file. However, you
cannot initiate an interactive process while SYS$INPUT is defined as a
file. File-structured storage devices are not permitted as SYS$INPUT for
interactive processes. The purpose of this restriction is to prevent LOGIN
from reading a user name and password from a file.
User Action: Use a non-file-structured device as SYS$INPUT for an
interactive process.
INVLDRESP, invalid operator response
Facility: MOUNT, Mount Utility
Explanation: The operator responded to a request with an invalid reply.
User Action: None. The request is automatically reentered.
INVLOCKID, invalid lock id
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
INVPARFIL, invalid parameter file
Facility: SYSGEN, System Generation Utility
Explanation: An error occurred accessing the file specified in a USE or
WRITE operation.
User Action: Check that the file is not protected against read or write access
and then reenter your command. If the error occurs again, but the file can
be read or written by other utilities, submit a Software Performance Report
(SPR). Include a copy of the invalid parameter file with the SPR.
INVPRVNAM, 'privilege' is not a valid privilege
Facility: INSTALL, Install Utility
Explanation: An invalid privilege name is specified.
User Action: Correct the privilege name and reenter the ·command.

Message Descriptions

INVPTEFMT, invalid page table entry format
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
INVPWD, invalid password
Facility: LOGIN, Login Procedure
Explanation: The specified password is incorrect. This message is written
to the system accounting and security audit records; the NOTVALID message
displays to the user.
User Action: None.
INVQALPOS, invalid '/qualifier' qualifier positional use
Facility: BACKUP, Backup Utility
Explanation: The specified command qualifier was incorrectly positioned in
the command.
User Action: Reenter the command, being sure to properly order the input
and output fields and the global qualifiers.
INVRECSIZ, invalid record size in save set
Facility: BACKUP, Backup Utility
Explanation: An incorrect value occurred in the record size field
(BRH$W_RSIZE) of a save-set record. Data in the save set is corrupt.
User Action: None. Save-set data is lost.
INVRECTYP, invalid record type in save set
Facility: BACKUP, Backup Utility
Explanation: An incorrect value occurred in the record type field of a
save-set record. Data in the save set is corrupt.
User Action: None. Save-set data is lost.
INVREQ, the parameter 'parameter' is invalid.
Facility: STDRV, System Startup Driver
Explanation: The startup driver is executed with an invalid first parameter.
User Action: If the error occurs during a system boot, check the value of
the SYSGEN parameter STARTUP_Pl. If errors occur after a @STARTUP
command procedure, verify that the first parameter is FULL, MINIMUM,
UPGRADE, or the name of the system component to restart.

Message Descriptions

INVRSPID, RSPID 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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
INVSHDWMEM, shadow set member 'ddcu:' is 'newer' than the shadow set
Facility: MOUNT, Mount Utility
Explanation: Volumes being added to an existing shadow set cannot have a
higher generation number than the shadow set.
User Action: Determine which volume should be the target of the shadow
copy operation. Recreate the shadow set, and add the target of the copy
operations to it.
INVSTRUCT, invalid structure level in save set
Facility: BACKUP, Backup Utility
Explanation: An incorrect value occurred in the structure level field of a
save-set block. Data in the save set is corrupt.
User Action: None. Save-set data is lost.
INVTQEFMT, invalid time queue entry format
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
INVVEC, invalid or unspecified interrupt vector
Facility: SYSGEN, System Generation Utility
Explanation: Either no interrupt vector is specified in a SYSGEN command
CONNECT, or the one that is specified is not within the UNIBUS interrupt
vector address range.
User Action: Reenter the command specifying a valid vector number.

Message Descriptions

IVBAKADIO, invalid backing store address for I/O
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
·
IVGBLTYP, invalid global master PTE type
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
IVLISTK, interrupt stack invalid restart
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
IVQUAL, invalid qualifier
Facility: INSTALL, Install Utility
Explanation: An invalid qualifier is specified.
User Action: Reenter the command line.
IVSSRVRQST, invalid system service request
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.

Message Descriptions

(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
IVWSETLIST, invalid working set list entry
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
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 of the problem.
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)

Message Descriptions

JOURNAL, journaling to 'filespec'
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.
KRNLST.AKNv, 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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
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. The accompanying message
provides additional information.
User Action: Correct the condition that caused the error and reenter the
command.
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. The error may be caused because 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.

Message Descriptions

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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
LOAD ERR, error configuring 'device-name' as 'driver-name'
Facility: !OGEN
Explanation: An error occurred during autoconfiguration.
User Action: Take appropriate action based on information in 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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
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.

Message Descriptions

LOGNAME, logical name is too long
Facility: MOUNT, Mount Utility
Explanation: A logical name contains more than 63 characters.
User Action: Reenter the command; specify a logical name that has fewer
than 63 characters.
Low Priority Command Queue Insert Failure
Facility: VAXport Driver
Explanation: The VAXport 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), or BI
(VAX 8200, VAX 8300, and VAX 8800) contention.
User Action: Call Digital Services.
MACHINECHK, machine check while in kernel mode
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an irrecoverable hardware
error. Because of the severity of the error, further operation is impossible,
or if it is possible, it might corrupt user data. After all physical memory
is written to a system dump file, the system automatically reboots if the
BUGREBOOT system parameter is set to one.
User Action: Submit a Software Performance Report (SPR) that describes
the condition leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
MAKEWSLE, make working set list entry 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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
MAPCNTZER, attempted to generate zero length map pointer
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)

Message Descriptions

MAPHDRBAD, storage map header is bad; volume locked
Facility: MOUNT, Mount Utility
Explanation: An I/O error is encountered during a mount operation or the
header is corrupted. Existing files on the volume can be accessed but other
operations, for example, create and delete, are not possible.
User Action: Copy the files that are still accessible to a new volume.
Reconstruct, as necessary, from backup media.
MAXBAD, bad block table overflow
Facility: BACKUP, Backup Utility
Explanation: The specified volume has too many bad blocks; either the DCL
command INITIALIZE cannot initialize the volume, or the Backup utility
cannot process the volume. This message generally indicates that the disk
volume can no longer be used.
User Action: Check the status of the device and reenter the command.
If the failure persists, reformat the disk. Notify the system manager. If
the failure still persists and the disk pack is under warranty, it should be
returned to Digital.
MAXDEV, too many devices
Facility: MOUNT, Mount Utility
Explanation: More than 16 tape devices were specified in the DCL command
MOUNT or DISMOUNT.
User Action: Reenter the MOUNT or DISMOUNT command and specify
fewer than 16 devices.
MAXLAB, too many volume labels
Facility: MOUNT, Mount Utility
Explanation: More than 16 tape labels were specified in a DCL command
MOUNT.
User Action: Reenter the DCL command MOUNT; specify fewer than 16
volume labels.
MAXLINKS, maximum links already defined
Facility: LAT, LAT Facility
Explanation: The link cannot be created because the maximum number of
allowable links is already defined.
User Action: None.
MAXSERV, maximum number of services exceeded
Facility: LAT, LAT Facility
Explanation: An attempt was made to create more than 255 services on the
local node.
User Action: A service must be deleted in order to add one.

Message Descriptions

MAXTOOBIG, maxunits specified is too large
Facility: SYSGEN, System Generation Utility
Explanation: The /MAXUNITS qualifier, as specified, caused an overrun in
a word-sized length field when the length of the IDB is calculated.
User Action: Reenter the SYSGEN command CONNECT with a smaller
/MAXUNITS number.
MAXUNITS, unit number greater than the maximum units specified
Facility: SYSGEN, System Generation Utility
Explanation: A unit number is encountered in creating the I/O database
that is larger than the maximum number of units allowed (default= 8).
User Action: Retry the operation using the /MAXUNITS qualifier on the
SYSGEN command CONNECT.
MAXVOLS, too many volumes in volume set 'device-name'
Facility: BACKUP, Backup Utility
Explanation: The volume set count recorded in the home block of relative
volume 1 of an input volume set is greater than 255. Possibly, this value has
been corrupted. Neither the Backup utility nor the Analyze/Disk_Structure
utility can process the volume.
User Action: Reconstruct the volume set from backup media.
MBACBHUNG, MBA CBHUNG bit set
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
MBXCRERR, error creating operator reply mailbox
Facility: MOUNT, Mount Utility
Explanation: The reply mailbox could not be created. This message is
issued with an accompanying message.
User Action: Take appropriate action based on information in the
accompanying message.
MBXRDERR, error reading operator reply mailbox
Facility: MOUNT, Mount Utility
Explanation: You are unable to read a mailbox. This message is issued with
an accompanying message.
User Action: Take appropriate action based on information in the
accompanying message.

Message Descriptions

Memory dump complete after 'nn' write error(s)
Facility: BUGCHECK, System Bugcheck
Explanation: This message indicates that the memory dump is finished;
however, there are one or more write errors.
User Action: When the system reboots, copy the dump to another file.
Determine the text associated with the hexadecimal status of previous
messages by using the F$MESSAGE lexical function or its equivalent. If
the status indicates a possible disk problem, see the user action for the
accompanying message.
Memory dump incomplete - dump file 'nn' blocks too small
Facility: BUGCHECK, System Bugcheck
Explanation: This message indicates that the system was unable to
write out the remaining 'nn' pages of a complete, physical memory dump
(SYSGEN parameter DUMPSTYLE set to 0). The dump cannot be used
because analysis depends on the System Page Table, which is kept in the
uppermost physical pages of memory (that is, the last data to be written if
this style of dump is written).
User Action: If there is room on the volume that holds the system dump file,
expand the dump file. If space is limited, try to write a selective dump. Refer
to the Open VMS System Manager's Manual for the correct procedures.
Message Free Queue Insert Failure
Facility: VAXport Driver
Explanation: The VAXport 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), or BI (VAX 8200, VAX 8300, and VAX 8800)
contention.
User Action: Contact Digital Services.
Message Free Queue Remove Failure
Facility: VAXport Driver
Explanation: The VAXport 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), or BI (VAX 8200, VAX 8300, and VAX 8800)
contention.
User Action: Call Digital Services.
MFYNULPGFL, FREWSLE - no backing store, page not modified
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing

Message Descriptions

the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
Micro-code Verification Error
Facility: VAXport Driver
Explanation: The port driver attempts to reinitialize the port; after 50 failed
attempts, it marks the device off line.
User Action: Call Digital Services to check the port hardware.
MISCONFUNI, UNIBUS device 'device-name' has been misconfigured,
interrupt vector should be 'interrupt-vector-value'
Facility: SYSGEN, System Generation Utility
Explanation: The vector on the device specified in the message needs to be
changed.
User Action: Call Digital Services.
MOD LINK, modified link 'link-name'
Facility: LAT, LAT Facility
Explanation: The specified link has been modified by LATCP.
User Action: None.
MODNODE, modified characteristic(s) of local node
Facility: LAT, LAT Facility
Explanation: Characteristics of the local node have been modified by
LATCP.
User Action: None.
MODOUTAI, RMS after-image journaling disabled on saved copy of 'filespec'
Facility: BACKUP, Backup Utility
Explanation: After-image journaling has been disabled on the saved copy of
the file. This message is informational.
User Action: None.
MODOUTAIS, RMS after-image journaling disabled on saved copy of 'filespec'
(I file-id I)
Facility: BACKUP, Backup Utility
Explanation: After-image journaling has been disabled on the saved copy of
the file in the standalone backup operation. That is, if the disk is restored,
the journal command must be reentered. This message is informational.
User Action: None.
MODOUTBI, RMS before-image journaling disabled on saved copy of 'filespec'
Facility: BACKUP, Backup Utility
Explanation: Before-image journaling has been disabled in the backup
operation. That is, if the disk is restored, the journal command must be
reentered. This message is informational.
User Action: None.

Message Descriptions

MODOUTBIS, RMS before-image journaling disabled on saved copy of 'filespec'
(I file-id I)
Facility: BACKUP, Backup Utility
Explanation: Before-image journaling has been disabled on the saved copy
of the file in the standalone backup operation. That is, if the disk is restored,
the journal commands must be reentered. This message is informational.
User Action: None.
MOD PORT, modified port 'port-name'
Facility: LAT, LAT Facility
Explanation: The specified port has been modified by LATCP.
User Action: None.
MODRELNBAK, no backing store address for modified page
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
MODSERVICE, modified service 'service-name'
Facility: LAT, LAT Facility
Explanation: The specified service has been modified by LATCP.
User Action: None.
MOUNEWVOL, MOUNT new relative volume nn (volume label) on devicename'
Facility: MOUNT, Mount Utility
Explanation: During a write operation, the end-of-tape has been reached on
the last reel of a volume set.
User Action: Mount a new relative volume to be added to the tape set.
1

MOUNTDEV, please mount 'name' device 'device-name'
Facility: MOUNT, Mount Utility
Explanation: A request for operator assistance on MOUNT occurred.
User Action: Wait for operator assistance, perform the request yourself, or
abort the request.
MOUNTED, 'volume-label' mounted on 'device-name'
Facility: MOUNT, Mount Utility
Explanation: This message verifies a request.
User Action: None.

Message Descriptions

MOUNTERR, volume 'volume' on 'device' was not mounted because 'reason'
Facility: BACKUP, Backup Utility
Explanation: The Backup utility was unable to mount the specified volume
for one of the following reasons:
•

The expiration date specified in the volume label is in the future. That is,
the data on the volume has not expired.

•

Its label does not match. the one requested. The label specified in the
BACKUP command (either explicitly or implicitly) does not match the
label on the volume.

•

It is protected against access. The protection specified in the volume
header disallows access by the person entering the BACKUP command.

User Action: At this point, the Backup utility allows you to either quit the
operation, overwrite the volume label and continue, or put a new volume in
the drive and continue processing. To abort the operation, enter the QUIT
command at the BACKUP> prompt. To overwrite information in the volume
header and continue processing, enter the OVERWRITE command at the
BACKUP> prompt. To restart the operation with a new volume, enter the
NEW command at the BACKUP> prompt. If the QUIT or NEW command is
chosen, BACKUP automatically dismounts the volume.
MOUNTFll, 'filespec' must be mounted Files-11
Facility: BACKUP, Backup Utility
Explanation: The specified volume is mounted with the /FOREIGN qualifier.
However, for the given operation, the volume must be mounted without the
/FOREIGN qualifier.
User Action: Reevaluate the operation, checking that the correct I/O devices
have been specified and that the /SAVE_SET, /PHYSICAL, and /IMAGE
qualifiers are properly used. Then, if appropriate, mount the specified volume
without the /FOREIGN qualifier, and reenter the command.
MOUNTFOR, 'device' must be mounted /FOREIGN
Facility: BACKUP, Backup Utility
Explanation: The specified volume is mounted without the /FOREIGN
qualifier. However, for the given operation, the volume must be mounted with
the /FOREIGN qualifier.
User Action: Reevaluate the operation, checking that the correct I/O devices
have been specified and that the /SAVE_SET, /PHYSICAL, and /IMAGE
qualifiers are properly used. Then, if appropriate, mount the specified volume
with the /FOREIGN qualifier, and reenter the command.
MOUVOL, MOUNT relative volume 'nn' on 'device-name'
Facility: MOUNT, Mount Utility
Explanation: During a read operation, the operator is requested to mount
the next reel in a multivolume set.
User Action: Mount the indicated reel on the device specified.

Message Descriptions

MSCPSERV, encountered unrecoverable error
Facility: BUGCHECK, System Bugcheck
Explanation: The MSCP server encountered an unrecoverable error.
User Action: Submit a Software Performance Report (SPR). Include a copy
of the crash dump with the SPR.
MTXCNTNONZ, mutex count nonzero at system service exit
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: Submit a Software Performance Report (SPR) Software
Performance Report (SPR) that describes the conditions leading to the error.
Include a backup save set containing the system dump file and the error log
file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier
with the BACKUP command that produces the save set included with the
SPR.)
NAMETOOLONG, link name is too long
Facility: LAT, LAT Facility
Explanation: An attempt was made to create or set a link with a name
longer than 16 characters.
User Action: Use link names of 16 or fewer characters.
NEGSHBREF, shared memory control block negative refcnt
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
NETNOBUF, NETACP - buffer allocation failure
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)

Message Descriptions

NETNOSTATE, NETACP - no state transition
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
NETRCVPKT, NETACP - no receive I/O packet
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
NETSYSSRV, NETACP - unexpected system service failure
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
NETTRANCNT, NETACP - transaction count zero
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)

Message Descriptions

NETUAFACC, error accessing network authorization file
Facility: LOGIN, Login Procedure
Explanation: LOGIN could not read the SYS$SYSTEM:NETPROXY.DAT
network user authorization file.
User Action: Determine whether the file SYS$SYSTEM:NETPROXY.DAT
exists and, if it does, make sure it is not protected against system read access.
NEWLINK, created link •link-name'
Facility: LAT, LAT Facility
Explanation: The specified link has been created by LATCP.
User Action: None.
NEWLOGNAME, created logical name 'logical-name' in table 'table-name'
Facility: LAT, LAT Facility
Explanation: The specified logical name has been created by LATCP in the
specified table.
User Action: None.
NEWPORT, created port 'port-name'
Facility: LAT, LAT Facility
Explanation: The specified port has been created by LATCP.
User Action: None.
NEWSAVSET, now beginning save set 'save set'
Facility: BACKUP, Backup Utility
Explanation: This message indicates the beginning of a new save set during
a wildcard list or restore operation.
User Action: None.
NEWSERVICE, created service 'service-name'
Facility: LAT, LAT Facility
Explanation: The specified service has been created by LATCP.
User Action: None.
NEWTAPE, place volume 'volume' on device 'device'
Facility: BACKUP, Backup Utility
Explanation: The volume should be placed on the specified device.
User Action: If the /NOASSIST qualifier is entered, the user should place
the volume in the drive. Otherwise, the user should wait for the operator to
do so.
NEXNOTUBA, nexus is not a UNIBUS adapter
Facility: SYSGEN, System Generation Utility
Explanation: This message is returned from SHOW/UNIBUS when an
adapter other than a UNIBUS adapter is specified.
User Action: Reenter the command with a valid UNIBUS adapter.

Message Descriptions

NEXTVOL, volume 'volume' mounted - operation continues
Facility: BACKUP, Backup Utility
Explanation: This message indicates that the next volume required for the
backup operation has been mounted.
User Action: None.
No Path - Block During Virtual Circuit Close
Facility: VAXport Driver
Explanation: The VAXport driver attempts to reinitialize the port; after 50
failed attempts, it marks the device off line.
User Action: Submit a Software Performance Report (SPR) including the
error logs and the crash dumps from the local and remote systems.
NOACP, no LATACP to process request
Facility: LAT, LAT Facility
Explanation: Information was requested from the local LAT software, but
LATACP is not currently running on the local node.
User Action: Check to see whether LAT startup has executed correctly or if
LAT shutdown has been performed on the local node.
NOACPCHAN, failure to assign ACP channel
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
NOACPDEV, device named by /PROCESSOR:SAME has no ACP
Facility: MOUNT, Mount Utility
Explanation: The /PROCESSOR qualifier requested that the ACP currently
processing a specified device be used for another device, but the first device
does not have an ACP.
User Action: Reenter the command; select a different option for the
/PROCESSOR qualifier.
NOACPMAIL, failure to create ACP mailbox
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
71

Message Descriptions

NOADAPTER, no adapter (nexus) number specified
Facility: SYSGEN, System Generation Utility
Explanation: The /ADAPTER qualifier must be specified in the SYSGEN
command CONNECT.
User Action: Reenter the command specifying the /ADAPTER qualifier.
NOALOCLASS, allocation class not allowed with shadowing phase II virtual
unit name
Facility: MOUNT, Mount Utility
Explanation: An allocation class was specified in the name of the virtual
unit. Allocation classes are not allowed in virtual unit names with volume
shadowing phase II (OpenVMS Volume Shadowing).
User Action: Reenter the command without specifying an allocation class
on the virtual unit. The virtual unit must be specified in the form DSA or
DSAnnnn, where nnnn represents a unique number from 0 to 9999.
NOAQBACP, no AQB for 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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
NOAUTOCNF, autoconfigure all is inhibited
Facility: SYSGEN, System Generation Utility
Explanation: The SYSGEN parameter NOAUTOCONFG is set to 1.
User Action: Set NOAUTOCONFG to 0 and reenter the command.
NO BACKUP, 'string' data not copied, file marked NO BACKUP
Facility: BACKUP, Backup Utility
Explanation: A save operation is performed on a file marked NOBACKUP.
Therefore, the file header only is saved, no data is transferred to the save set.
User Action: Set file so that it can be backed up with SET FILE/BACKUP
command or add the /IGNORE=NOBACKUP qualifier to the BACKUP
command line.
NOBADDATA, bad data block not found on 'device-name'
Facility: BACKUP, Backup Utility
Explanation: Software bad block data is not present on the volume. The
volume has been initialized with no bad blocks.
User Action: Execute the Bad Block Locator utility before using the volume.

Message Descriptions

NOBITMAP, no valid storage bit map found on 'device-name'
Facility: BACKUP, Backup Utility
Explanation: The Backup utility encountered an error during an attempt to
search for the storage bitmap file, [OOOOOO]BITMAP.SYS;l, on the specified
volume. The volume cannot be used as a save-set disk.
User Action: Retry the operation using a properly initialized Files-11
Structure Level 2 volume.
NOBUFPCKT, required buffer packet not present
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
NOBVPVCB, blocked volume virtual page not found in VCB
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
NOCMK, operation requires CMKRNL privilege
Facility: INSTALL, Install Utility
Explanation: The CMKRNL privilege is needed to perform the requested
operation.
User Action: Exit INSTALL and use SET/PROC/PRIV=CMKRNL.
NODEVADAP, no devices on adapter 'n'
Facility: SYSGEN, System Generation Utility
Explanation: A SHOW/CONFIGURATION operation is tried on an adapter
that has no devices.
User Action: Reenter the command specifying an adapter that has devices.
NODEVAVL, device 'device-name' is not available for mounting. ['optional
comment']
Facility: MOUNT, Mount Utility
Explanation: Someone else has allocated the device you requested.
User Action: Abort the MOUNT and retry specifying another device.

Message Descriptions

NO FILES, no files selected from 'filespec'
Facility: BACKUP, Backup Utility
Explanation: No files matched the input file selection criteria.
User Action: Reevaluate the operation to ensure that the correct results are
obtained.
NOGBLSEC, no global sections created for 'filespec'
Facility: INSTALL, Install Utility
Explanation: When creating a known file entry for a shareable image,
INSTALL is not able to create global sections for that image. The image is
not shareable.
NOHDJMT, no Head-JMT in JMT list (journaling)
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
NOHDRRES, compatibility mode image, 'filespec' , cannot be header resident
Facility: INSTALL, Install Utility
Explanation: The /HEADER qualifier is ignored. Resident headers are not
used with compatibility mode images. The known file entry is successfully
created.
User Action: None.
NOHOMEBLK, no valid home block found on 'device-name'
Facility: BACKUP, Backup Utility
Explanation: The Backup utility encountered an error during an attempt
to search for the Files-11 home block on the specified volume. The volume
cannot be used as a save set disk.
User Action: Retry the operation using a properly initialized Files-11
Structure Level 2 volume.
NOICBM, failed to find an ICBM with the prefix 'prefix'
Facility: IOGEN
Explanation: No IOGEN Configuration Building Module (ICBM) could be
found with the specified prefix. Either the file does not exist or the file is not
installed.
User Action: Check if the file exists and ensure that it is installed as a
known image. See the Install utility in the OpenVMS System Management
Utilities Reference Manual for instructions on installing a known image.

Message Descriptions

NOIDBAVAIL, unable to allocate an IDB
Facility: LAT, LAT Facility
Explanation: LATCP cannot allocate enough virtual memory for an internal
data structure needed to execute a command. An accompanying message
explains why the virtual memory cannot be allocated.
User Action: Take appropriate action based on information in the
accompanying message.
NOINDEXF, no valid index file header found on 'device-name'
Facility: BACKUP, Backup Utility
Explanation: The Backup utility encountered an error during an attempt
to search for the index file, [OOOOOO]INDEXF.SYS;l, on the specified volume.
The volume cannot be used as a save set disk.
User Action: Retry the operation using a properly initialized Files-11
Structure Level 2 volume.
NOITMLST, unable to allocate virtual memory for command itemlist
Facility: LAT, LAT Facility
Explanation: LATCP cannot allocate enough virtual memory for a LAT item
list needed to execute a command. An accompanying message explains why
the virtual memory cannot be allocated.
User Action: Take appropriate action based on information in the
accompanying message.
NOKFEFND, Known File Entry not found
Facility: INSTALL, Install Utility
Explanation: There is no known file entry in the known file list for the file
you want to create, replace, or list.
User Action: Use /LIST to find out what entries are in the file list.
NOLIST, there is no Known File Entry List
Facility: INSTALL, Install Utility
Explanation: The known file entry list is not created. Therefore, LIST,
DELETE, REMOVE, and PURGE will have no effect.
User Action: None. The list is created automatically when the first known
file is created with the ADD, CREATE, or REPLACE commands.
NOLOAD, network and sequentially loaded files are not installable
Facility: INSTALL, Install Utility
Explanation: Known file entries cannot be created for files that are stored
on magnetic tape or that are accessible through a network.
User Action: Transfer the file to a disk and then install it.

Message Descriptions

NOMULTBK, ACP multiple block buffering not supported yet
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
NONCONTIG, 'file-name' is not contiguous due to insufficient contiguous space
Facility: BACKUP, Backup Utility
Explanation: The specified file is originally allocated contiguous blocks.
However, because the output volume lacked enough space for contiguous
blocks, the file has been allocated noncontiguous blocks.
User Action: If necessary, reorganize the volume to free a sufficient number
of contiguous blocks and reenter the command.
NONEDEL, no files processed on deletion pass
Facility: BACKUP, Backup Utility
Explanation: The Backup utility did not process any files in the deletion
pass. That is, no files were deleted by the backup operation.
User Action: None.
NONEREC, no files processed on recording pass
Facility: BACKUP, Backup Utility
Explanation: The Backup utility did not process any files in the recording
pass. That is, no files had their backup date updated by the backup operation.
User Action: None.
NONEXSTACP, Nonexistent ACP process
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
NONLOCAL, device is not a local device
Facility: MOUNT, Mount Utility
Explanation: The device name specified in a command or program request
is not a local device; that is, the device name contains a network node name.
User Action: Verify the device name (or logical name, if a logical name is
specified), and reenter the command specifying a device in the host system.

Message Descriptions

NONODE, node name has not been initialized
Facility: LAT, LAT Facility
Explanation: The local LAT node has not been initialized.
User Action: Use the LATCP command SET NODE to initialize the local
LAT node.
NONPHYSET, nonphysical save set supplied to physical operation
Facility: BACKUP, Backup Utility
Explanation: A save set created without the /PHYSICAL qualifier is used as
input to an operation with the /PHYSICAL qualifier.
User Action: Use the BACKUP/LIST command to determine how the save
set is created. Reevaluate the operation and reenter the command.
NONSMPDRV, nonsmpized driver cannot be loaded
Facility: SYSGEN, System Generation Utility
Explanation: SYSGEN cannot load this driver because the driver has not
been modified to support symmetric multiprocessing (SMP).
User Action: Modify the driver to conform to symmetric multiprocessing
requirements, or turn off SMP. ,
NONSTDUNI, unibus in nonstandard configuration, device 'device-name' vector
is wrong
Facility: SYSGEN, System Generation Utility
Explanation: The vector on the device specified in the message needs to be
reconfigured.
User Action: Call Digital Services.
NOOPER, no operator is available to handle the request
Facility: BACKUP, Backup Utility
Explanation: There are no operator terminals enabled to handle this
request.
User Action: Either service the request yourself or abort the request. To
ensure that no operator intervention is required in a backup operation,
specify the /NOASSIST qualifier on the command line.
NOOPR, no operator available to service request
Facility: MOUNT, Mount Utility
Explanation: No operator is present to service the request.
User Action: Service the request yourself or abort the request.
NOPAGEDYN, unable to allocate enough paged dynamic memory
Facility: INSTALL, Install Utility
Explanation: INSTALL cannot complete the operation because paged
dynamic memory is not accessible.
User Action: Contact your system manager.

Message Descriptions

NOPARAM, no such parameter
Facility: SYSBOOT, System Bootstrap Facility
Facility: SYSGEN, System Generation Utility
Explanation: The parameter name specified in a SET or SHOW command is
not valid.
User Action: Reenter the command specifying a valid parameter name.
NOPATHTBL, invalid or nonexistent path table; built from directories
Facility: SYSTEM, System Services
Explanation: Either a path table record was not found or it was illegally
formatted according to the ISO 9660 standard. An in-memory path table is
constructed at MOUNT time by walking the entire directory structure. This
operation can take a few minutes.
User Action: Notify the manufacturer of the CD-ROM media that their
product is noncompliant.
NOPREV, no previous entry exists - new entry created for 'image'
Facility: INSTALL, Install Utility
Explanation: A Known File Entry is created by means of the REPLACE
command, and there is no previous entry that had to be deleted first.
User Action: None. The use of REPLACE implies that an old entry is
expected to exist, but did not exist.
NOPRIV, user denied privilege to write to volume on 'device-name'
Facility: MOUNT, Mount Utility
Explanation: The user requested initialization of a volume but does not
have the privilege to write to it.
User Action: Mount either a tape that the user has write privilege to, or
a blank tape. Request initialization of this tape when replying to the next
mount request.
NOPTBLDIR, no path table or directory records found
Facility: SYSTEM, System Services
Explanation: An attempt was made to mount media that is noncompliant
with the ISO 9660 standard. This is a fatal error.
User Action: Notify the manufacturer of the CD-ROM media that their
product is noncompliant.
NORCP, RCP not active
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)

Message Descriptions

NORCVBUF, NETACP - no receive buffer available
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
NOSCS, error loading SCS code
Facility: SYSGEN, System Generation Utility
Explanation: SCSLOA.EXE could not be loaded.
User Action: Do not attempt to load SCSLOA.EXE.
NOSHDWMEM, no eligible shadow set members to mount the shadow set
Facility: MOUNT, Mount Utility
Explanation: There are no valid volumes to create the shadow set. This
error message is followed by the failed status code for each proposed member.
User Action: Examine the status codes, correct the situation, and reenter
the command.
NOSHMGSD, No shared memory global section dsc found for page
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
NOSHRD, file can not be made shared
Facility: INSTALL, Install Utility
Explanation: Only native-mode images and compatibility-mode images
supported by the AME and provided by VAX-11 RSX systems are supported
as shareable known files.
User Action: Reinstall without the /SHAR qualifier.
NOSLS, qualifier '/qualifier' is invalid when SLS is not installed
Facility: BACKUP, Backup Utility
Explanation: The command line contains a qualifier specific to the Storage
Library System (SLS), but SLS is not installed on the system where the
BACKUP command was executed.
User Action: Remove the qualifier that is specific to SLS or install SLS on
the system where the BACKUP command is executed.

Message Descriptions

NOSUCHFILE, file 'file-name' does not exist.
Facility: STDRV, System Startup Driver
Explanation: A startup component file specified in the startup database
does not exist during system startup.
User Action: Verify that the entry in the startup database is correct. If it
is correct, verify that the component file is located in the SYS$STARTUP
directory.
NOSUCHMEM, no shared memory found at specified NEXUS
Facility: SYSGEN, System Generation Utility
explanation: The desired shared memory unit number is not found in a
search of the backplane interconnect adapter list.
User Action: Reenter the command with the correct device unit number.
NOSUCHRVN, NOLUME = 'number' invalid, volume set contains 'number'
volumes
Facility: BACKUP, Backup Utility
Explanation: The value specified for the NOLUME qualifier is larger than
the number of volumes in the volume set.
User Action: Reenter the command using a smaller value.
NOSUCHSEC, no such (global) section
Facility: SYSTEM, System Services
Explanation: The global section name specified in a request to map a global
section does not exist.
User Action: Check for a programming error. Verify that the program that
creates the global section successfully created the section, and that the section
has not been deleted. Also, check that the logical name strings specifying the
global section name match.
NOSUCHUSER, no such user
Facility: LOGIN, Login Procedure
Explanation: The specified user name does not exist. This message is
written to the system accounting and security audit records; the NOTVALID
message displays to the user.
User Action: None.
NOSYSDISK, no access to system disk
Facility: BACKUP, Backup Utility
Explanation: The system disk is not accessible.
User Action: Determine why the system disk is inaccessible. If possible,
make the system disk operational and retry the BACKUP command.
Not enough SPTEs to take selective system dump - switching to complete memory
dump
Facility: BUGCHECK, System Bugcheck
Explanation: When writing a selective dump (SYSGEN parameter
DUMPSTYLE set to 1), the OpenVMS operating system needs to remap
portions of memory for easy access and for efficient writing of the dump file.
The OpenVMS operating system requests 127 System Page Table Entries

Message Descriptions

(SPTEs) during the bootstrap sequence so that the SPTEs are ready when
needed. If the system is configured so that there are not sufficient SPTEs to
create a selective dump, the system attempts to write a complete dump.
User Action: When the system comes back up, run AUTOGEN and reboot
with a larger SYSGEN parameter SPTREQ.
NOTlSTVOL, 'save-set-spec' is not the start of a save set
Facility: BACKUP, Backup Utility
Explanation: The volume mounted as the first volume of the specified save
set is a continuation volume. This is valid if the operation is not a restore
with the /IMAGE qualifier.
User Action: Reevaluate the operation to ensure that the correct results are
obtained.
NOTlSTVOL, tape 'tape-name' is not the start of a save set
Facility: BACKUP, Backup Utility
Explanation: A restore or compare operation did not begin with the first
volume in the save set. The Backup utility allows you to begin restore and
compare operations without mounting the first volume.
User Action: None.
NOTACLU, 'device-name' is not a cluster-wide device
Facility: MOUNT, Mount Utility
Explanation: An attempt was made to mount a device on all nodes in the
cluster by specifying the /CLUSTER qualifier; however, the device specified is
not available, nor can it be made available, clusterwide.
User Action: Reenter the command without the /CLUSTER qualifier.
NOTANSI, not ANSI volume on 'device-name'
Facility: MOUNT, Mount Utility
Explanation: The volume on the specified device is not an ANSI-formatted
magnetic tape.
User Action: Initialize the tape and reenter the mount request or mount the
tape foreign.
NOTANSI, tape is not valid ANSI format
Facility: BACKUP, Backup Utility
Explanation: The volume does not have ANSI standard labels.
User Action: Locate and mount the correct volume.
NOTASCII, parameter 'name' is not ASCII type
Facility: SYSBOOT, System Bootstrap Facility
Facility: SYSGEN, System Generation Utility
Explanation: An ASCII value is specified in a SET command for a
non-ASCII parameter.
User Action: Reenter the command specifying a correct parameter value.

Message Descriptions

NOTBKBLOCK, invalid subsystem code in save set
Facility: BACKUP, Backup Utility
Explanation: An incorrect value occurred in the subsystem code field of a
save-set block. Data in the save set is corrupt. The save-set data is lost.
User Action: None.
NOTCOM, BATCH mode can only be used for .COM files
Facility: STDRV, System Startup Driver
Explanation: An entry in the STARTUP component file specifies a
component file to be run with the BATCH command whose file type is not
COM.
User Action: Use the STARTUP MODIFY FILE command at the SYSMAN>
prompt to correct either the file name or the execution mode.
NOTDDBDDB, corrupted DDB list
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
NOTDISM, unable to dismount 'device-id'
Facility: BACKUP, Backup Utility
Explanation: The Backup utility cannot dismount a tape drive specified by
the command line qualifier /RELEASE_TAPE. An accompanying message
indicates the type of user action required, if any.
User Action: Take appropriate action based on information in the
accompanying message.
NOTFCBFCB, FCB linkage broken
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)

Message Descriptions

NOTFCBWCB, Bad FCB pointer in window
Facility: BUGCHECK, Syst.em 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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
NOTFCPWCB, Not FCP window in IRP
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
·
NOTGENDEV, not a generic device
Facility: MOUNT, Mount Utility
Explanation: An invalid generic device was specified.
User Action: Retry the operation specifying a valid generic device.
NOTIRPAQB, Not IRP pointer in AQB
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
NOTJOURNAL, 'filespec' is not a BACKUP journal
Facility: BACKUP, Backup Utility
Explanation: The specified file does not have the appropriate file attributes.
It is not a Backup utility journal file.
User Action: Locate the correct file and reenter the command.

Message Descriptions

NOTLABEL, 'volume-label' not on 'device-name'
Facility: MOUNT, Mount Utility
Explanation: The operator responded to a message from the magnetic tape
ACP with a successful completion, but the volume is not correct. The volume
label specified by the original DCL command MOUNT, or the reply to an
operator mount request, does not match the volume label on the specified
device.
User Action: Include the correct label in the next reply to an operator
mount request or mount the correct volume on the device. If you do not
want to check the label, use the OVERRIDE:ID qualifier in the original DCL
command MOUNT. Verify that the device is on line.
NOTLKB, Structure is not an LKB
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
NOTLOADED, LAT terminal port driver (LTDRIVER) is not loaded
Facility: LAT, LAT Facility
Explanation: An attempt was made to execute LATACP when LTDRIVER
was not loaded.
User Action: Check to see whether the LAT software is properly configured.
NOTMODEM, VAX/VMS host system modem not wired correctly - contact your
system manager
Facility: LOGIN, Login Procedure
Explanation: The modem connected to the OpenVMS system is not
asserting the proper signal control. The terminal line is set to /MODEM and
TTDRIVER did not detect all the necessary modem signals within 30 seconds
of a login attempt.
User Action: The system manager should ensure that the following
conditions are met:
•

The modem cable connecting the modem provides the correct signal.

•

The terminal port supports modem use.

•

The modem provides the correct signals in the correct order.

For information on how the TTDRIVER identifies a valid modem line, refer to
the section on modem control of terminal drivers in the OpenVMS I I 0 User's
Reference Manual.

Message Descriptions

NOTMTLMTL, Corrupted mounted volume list
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
CUse the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
NOTNUMBER, parameter 'name' is not numeric type
Facility: SYSBOOT, System Bootstrap Facility
Facility: SYSGEN, System Generation Utility
Explanation: A numeric value is specified in a SET command for a
nonnumeric parameter.
User Action: Reenter the command specifying a correct parameter value.
NOTPARAM, not a parameter file
Facility: SYSGEN, System Generation Utility
Explanation: The file specified in the SYSGEN command USE is not a valid
parameter file.
User Action: Use a valid parameter file that is either provided by the
OpenVMS operating system, or created by the SYSGEN command WRITE in
SYSGEN.
NOTPCB, Structure not PCB
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an irrecoverable, inconsistent
condition. After all physical memory is written to a system dunip file, the
system automatically reboots if the BUGREBOOT system parameter is set
to 1.
User Action: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
NOTRAN, logical name cannot be translated
Facility: MOUNT, Mount Utility
Explanation: The DCL command MOUNT or INITIALIZE attempted logical
name translation on a device name or logical name and failed to translate the
logical name. This error is most likely to occur when logical names are nested
too deeply or if a logical name is assigned to itself.
User Action: Use the DCL command SHOW LOGICAL to verify the
translation of the device name or logical name. If necessary, reassign the
logical name before reentering the DCL command MOUNT or INITIALIZE.

Message Descriptions

NOTRELVOL, relative volume 'nnn' not on device
Facility: MOUNT, Mount Utility
Explanation: Each volume in a volume set has a relative number beginning
with 1. The volume mounted on the device is not the relative volume
requested in the previous mount request.
User Action: Mount the correct volume on the device, or abort the mount
request if you do not have the correct volume.
NOTRULUCB, Bad RUL pointer in UCB (journaling)
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
NOTRVTVCB, Not PVT pointer in VCB
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
NOTSAVESET, 'save set spec' is not a backup save set
Facility: BACKUP, Backup Utility
Explanation: The specified file does not have the appropriate file attributes.
It is not a save set.
User Action: Locate the correct file and reenter the command.
NOTSHDWDEV, not a shadowing device
Facility: MOUNT, Mount Utility
Explanation: There are two possible causes for this error message:
•

The form DSA was not used to specify the virtual unit name in the mount
command, causing the mount command to fail.

•

An attempt was made to mount a volume that does not support volume
shadowing in a shadow set (for example, a magnetic tape cannot become
a shadow set member).

User Action: Correct the command syntax and enter the command again.

Message Descriptions

NOTUCBIRP, not UCB pointer in IRP
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
NOTUCBRVT, not UCB pointer in RVT
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
NOTUCBUCB, corrupted UCB list
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. ·Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
NOTUCBWCB, bad UCB pointer in window
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a BACKUP save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)

Message Descriptions

NOTVALID, user authorization failure
Facility: LOGIN, Login Procedure
Explanation: An incorrect user name, password, or both was entered. The
USERAUTH message simultaneously displays to the system manager.
User Action: Repeat the login procedure.
NOTVCBUCB, not VCB pointer in UCB
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
NOTVOLSET, volume on 'device-name' not in volume set 'volume-label'
Facility: MOUNT, Mount Utility
Explanation: The file set identifier of the first file in a volume set identifies
the volume set. The volume mounted on the device is not part of the specified
volume set.
User Action: Mount the correct volume on the device, or abort the mount
request if you do not have the correct volume.
NOTVVPVCB, not volume virtual page pointer in VCB
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
NOTWCBIRP, not WCB Pointer in IRP
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)

Message Descriptions

NOTWCBWCB, corrupted WCB list
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
NOUNLOAD, driver is not unloadable
Facility: SYSGEN, System Generation Utility
Explanation: Either an attempt is made to reload a driver that is marked
unloadable (DPT$M_NOUNLOAD) in the driver prologue table, or the unload
routine of the driver indicates that the driver should not be unloaded.
User Action: None.
NOUSRWCS, no user WCS halt restart
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing
the system dump file and the error log file active at the time of the error.
(Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that
produces the save set included with the SPR.)
NOVALUE, qualifier 'qualifier' requires value
Facility: BACKUP, Backup Utility
Explanation: No value was given for the specified qualifier.
User Action: Specify a value for the qualifier and reenter the BACKUP
command.
NOVER, no file version obtained for 'filespec'
Facility: INSTALL, Install Utility
Explanation: INSTALL could not obtain the file version number of the
image file for the known file entry being listed.
User Action: Ensure that the image file exists, and check the file protection.
NOVOLDATA, volume summary data for 'device-name' not found - /IMAGE
cannot be used
Facility: BACKUP, Backup Utility
Explanation: In a restore operation with the /IMAGE qualifier, no volume
initialization data exists. Either the save set is created without the /IMAGE
qualifier, or save-set data has been lost.
User Action: Attempt to recover data without the /IMAGE qualifier. If this
error occurs during a disk-to-disk (copy) operation, it indicates a software
89

Message Descriptions

error in the Backup utility; in this case, submit a Software Performance
Report (SPR).
NOVOLDESC, no CD-ROM volume descriptor found
Facility: SYSTEM, System Services
Explanation: Either an attempt was made to mount media that is
noncompliant with the ISO 9660 standard or a CD-ROM volume descriptor
with a matching volume name was not found.
User Action: Try to determine the correct volume name by issuing a
MOUNT/OVERRIDE=IDENTIFIER command. If this fails, notify the
manufacturer of the CD-ROM media that their product is noncompliant.
ODS2SAVE, save set disk on 'device-name' must be structure level 2
Facility: BACK.UP, Backup Utility
Explanation: The specified volume is not a Files-11 Structure Level 2
volume. The volume cannot be used as a save-set disk.
User Action: Retry the operation using a properly initialized Files-11
Structure Level 2 volume.
OFFLINE, 'device-name' : offiine
Facility: MOUNT, Mount Utility
Explanation: The given device is off line. The requested action cannot be
completed.
User Action: Place the device on line and reenter the command.
ONEFllDEV, both input and output must not be save sets
Facility: BACK.UP, Backup Utility
Explanation: When the BACK.UP command was executed, you specified
that both input and output files reference a save set. Either the input or the
output specification, not both, can reference a save set.
User Action: Reenter the command.
ONEFllOUT, file-structured output must not be a list
Facility: BACK.UP, Backup Utility
Explanation: The output specification for a copy, restore, or compare
operation without the /IMAGE qualifier is a list of file specifications. (The
Backup utility does not accept this.)
User Action: Modify your output specification and reenter the command.
ONEIMGDEV, /IMAGE input specification must not be a list
Facility: BACK.UP, Backup Utility
Explanation: The specification for an input volume set to be processed with
the /IMAGE qualifier is a list of file specifications. (The Backup utility does
not accept this.)
User Action: Modify your input specification and reenter the command.

Message Descriptions

ONEPHYDEV, /PHYSICAL specification must not be a list
Facility: BACKUP, Backup Utility
Explanation: The specification for a physical volume is a list of file
specifications. (The Backup utility does not accept this.)
User Action: Modify your specification and reenter the command.
OPENDIR, error opening directory 'directory-name'
Facility: BACKUP, Backup Utility
Explanation: An error was encountered during an attempt to open the
specified directory file. An accompanying message provides additional
information. The Backup utility cannot process files in this directory or its
subdirectories.
User Action: Correct the condition that caused the error and reenter the
command line.
OPENFAIL, failure opening component file 'file-number', 'file-name'
Facility: STDRV, System Startup Driver
Explanation: The startup driver failed to open one of the system files that
describes the tasks that need to be performed at startup time. The startup
operation attempts to continue, but may not properly perform all startup
tasks.
User Action: Make sure that the named file is available and can be read.
OPENIN, error opening 'file-name' as input
Facility: LOGIN, Login Procedure
Explanation: A file to be read by LOGINOUT (for example, a file containing
the announcement message) cannot be opened.
User Action: Ensure that the file exists and that it has read access.
OPERABORT, operator has aborted request, reply is 'reply'
Facility: BACKUP, Backup Utility
Explanation: The operator has aborted or canceled the request.
User Action: Determine the reason for the cancellation from the reply given
in the message and proceed accordingly.
OPERASSIST, operator assistance has been requested
Facility: BACKUP, Backup Utility
Explanation: This message notifies you that operator assistance has been
requested.
User Action: None.
OPERFAIL, error requesting operator service
Facility: BACKUP, Backup Utility
Explanation: The Backup utility encountered an error during an attempt to
interact with the operator. The accompanying message provides additional
information. The error may be caused because the operator replied to the
request with REPLY/ABORT.
User Action: Correct the condition that caused the error and reenter the
command.

Message Descriptions

OPERSPEC, specify option ('options')
Facility: BACKUP, Backup Utility
Explanation: This message is returned to the operator. It indicates that
the Backup utility encountered a recoverable error. The operator must select
one of the options listed in the message. The possible options are QUIT,
CONTINUE, and RESTART. 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.
User Action: The operator should evaluate the preceding errors and select
the appropriate option.
OPRABORT, mount aborted by operator
Facility: MOUNT, Mount Utility
Explanation: This is the final message in a series of messages issued from
MOUNT to the operator. The operator has refused your request.
User Action: None.
OPREPLY, 'message-text'
Facility: MOUNT, Mount Utility
Explanation: An operator's response to the DCL command, REQUEST, is
displayed on the terminal. This message is informational.
User Action: None.
OPREPLY, operator reply is ' string'
Facility: BACKUP, Backup Utility
Explanation: The operator replied to an operator request with the text
string contained within quotes in the message.
User Action: None.
OPRQST, operator request: 'request'
Facility: MOUNT, Mount Utility
Explanation: This message announces an operator request.
User Action: None.
OPRQSTCAN, operator request canceled
Facility: MOUNT, Mount Utility
. Explanation: The MOUNT request was canceled by pressing Ctrl/Y.
User Action: None.
OPRQSTDON, operator request canceled - mount completed successfully
Facility: MOUNT, Mount Utility
Explanation: The operator request is canceled because the request is
completed.
User Action: None.

Message Descriptions

OPRSNDERR, error sending request to operator
Facility: MOUNT, Mount Utility
Explanation: MOUNT failed in an attempt to send a message to the
operator. This message is issued with an accompanying message.
User Action: Take appropriate action based on information in the
accompanying message.
OPSPECLBL, the label was not specified
specify EXACT_ORDER label (up to 6 characters)
Facility: BACKUP, Backup Utility
Explanation: Exact label checking is in effect, but the command line did not
specify enough labels to cover the current volume.
User Action: The user or the operator must specify a volume label to be
used in exact volume order checking.
OUTOFRANGE, value specified is not within the legal range for this qualifier
Facility: LAT, LAT Facility
Explanation: A value was specified that is out of range for a LATCP
qualifier.
User Action: Specify a value within the legal range (see the OpenVMS
System Management Utilities Reference Manual).
OUTPUTERR, error opening primary output file SYS$0UTPUT
Facility: LOGIN, Login Procedure
Explanation: The system cannot open the current output device and cannot
perform the login. This message is usually accompanied by an RMS file
system message indicating the reason for the failure.
User Action: Take corrective action based on the accompanying message,
and repeat the login procedure, if possible.
OUT_RANGE, number cannot be less than 1 or larger than 127
Facility: SYSGEN, System Generation Utility
Explanation: A SYSGEN command, CONFIGURE, was entered with a
number that is either too small or too large.
User Action: Reenter the command specifying a number within the range of
1to127.
OUTSWPERR, outswap write 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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)

Message Descriptions

OVERFLOW, overflow in floating addresses, illegal configuration
Facility: SYSGEN, System Generation Utility
Explanation: The SYSGEN command, CONFIGURE, computed an illegal
floating address for a CSR or vector.
User Action: Reenter the SYSGEN command CONFIGURE with the correct
number of controllers.
OVERWRITE, relative volume 'volume-name' on device 'device-name' will be
overwritten
Facility: BACKUP, Backup Utility
Explanation: This message notifies you that the volume header of the
indicated volume will be overwritten with the information requested by the
BACKUP command.
User Action: None.
PAGEREDERR, page read 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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
PAGEWRTERR, page write 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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
PAGNTRNVAL, page not in transition or 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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)

Message Descriptions

Parallel Path is Closing Virtual Circuit - REMOTE PORT 'xxx'
Facility: VAXport Driver
Explanation: The Port Driver switched communications from a low
performance communication link to a high performance communication
link. This event is a normal virtual circuit shutdown.
User Action: None.
PARSE, error opening 'filespec'
Facility: BACKUP, Backup Utility
Explanation: The Backup utility encountered an error during an attempt
to access the specified file. The accompanying message provides additional
information.
User Action: Correct the condition that caused the error and reenter the
command.
Path #0. Has become working but CROSSED to Path #1. - REMOTE PORT
'XXX'

Facility: VAXport Driver
Explanation: The VAXport driver logs this event.
User Action: Check for crossed-cable pairs.
Path #0. Has gone from BAD to GOOD
Facility: VAXport Driver
Explanation: The VAXport driver logs this event.
User Action: None.
Path #0. Has gone from GOOD to BAD
Facility: VAXport Driver
Explanation: The VAXport driver logs this event.
User Action: Check Path A cables for breaks or improper connections.
Path #0. Loopback has gone from BAD to GOOD
Facility: VAXport Driver
Explanation: The VAXport driver logs this event.
User Action: None.
Path #0. Loopback has gone from GOOD to BAD
Facility: VAXport Driver
Explanation: The VAXport driver logs this event.
User Action: Check for crossed-cable pairs or faulty CI hardware.
Path #1. Has become working but CROSSED to Path #0. - REMOTE PORT
'XXX'

Facility: VAXport Driver
Explanation: The VAXport driver logs this event.
User Action: Check for crossed-cable pairs.

Message Descriptions

Path #1. Has gone from BAD to GOOD
Facility: VAXport Driver
Explanation: The VAXport driver logs this event.
User Action: None.
Path #1. Has gone from GOOD to BAD
Facility: VAXport Driver
Explanation: The VAXport driver logs this event.
User Action: Check Path B cables for breaks or improper connections.
Path #1. Loopback has gone from BAD to GOOD
Facility: VAXport Driver
Explanation: The VAXport driver logs this event.
User Action: None.
Path #1. Loopback has gone from GOOD to BAD
Facility: VAXport Driver
Explanation: The VAXport driver logs this event.
User Action: Check for crossed-cable pairs or faulty CI hardware.
PFNLISTCNT, inconsistent PFN list count
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
PFNREFNZRO, PFN reference count nonzero
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)

Message Descriptions

PGFGBLBAD, pagefault, global page table entry bad format
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
PGFIPLHI, pagefault with IPL too high
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
PGFLOCBAD, pagefault, location field has bad value
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
PHYDEVGEO, device type of 'device-name' does not match input
Facility: BACKUP, Backup Utility
Explanation: In an operation with the /PHYSICAL qualifier, the output
device must be the same type as the input device.
User Action: Reevaluate the operation; another mode of operation, such
as using the /IMAGE qualifier, may be appropriate. Or, retry the operation
specifying the same type of device.
PHYFILSPE, /PHYSICAL specification must have only device name
Facility: BACKUP, Backup Utility
Explanation: When the /PHYSICAL command qualifier was used, more than
a device name was specified as an input-specifier or output-specifier. The file

Message Descriptions

specification for a volume to be processed with the /PHYSICAL qualifier must
contain only a device name.
User Action: Refer to the Open VMS System Management Utilities Reference
Manual for information on the /PHYSICAL command qualifier and reenter
the command.
PHYSET, physical save set supplied to nonphysical operation
Facility: BACKUP, Backup Utility
Explanation: A save set created with the /PHYSICAL qualifier cannot be
used as input to an operation without specifying the /PHYSICAL qualifier.
User Action: Use the DCL command BACKUP/LIST to determine how the
save set is created. Reevaluate the operation, and reenter the command.
Port Error Bits Set - CNF/PMC/PSR 'xxxxxxxx!xxxxxxxxlxxxxxxxx'
Facility: VAXport Driver
Explanation: The port driver attempts to reinitialize the port; after
50 attempts, it marks the device off line.
User Action: Check the error logs for a sanity timeout. This sanity timeout
is indicated by bit 6 of the PSR (PSR = 'xxxxxx4x' ). The error logs describe
the sanity timeout bit as a "Maintenance Timer Expiration."· If sanity
timeouts occur, check the console log to see if the operator has halted
and continued the system for any reason. If the console log does not show
operator intervention, increase the PASTIMOUT SYSGEN parameter until
the timeouts no longer occur. For nontimeout errors, call Digital Services to
check the port hardware.
Port has Closed Virtual Circuit
Facility: VAXport Driver
·Explanation: The VAXport driver closes the virtual circuit that the local
VAXport opened to the remote port.
User Action: Check the PP$DB_STATUS field of the error log entry to see
why the virtual circuit is closed. This error is normal if the remote system
crashed or is shut down.
Port is going off line
Facility: VAXport Driver
Explanation: The port driver halted port operations because of an
unrecoverable error or because the retry count has been exceeded.
User Action: Examine the accompanying messages to determine the reason
for the port shutdown. Take corrective action and reboot the system.
Port Power Down
Facility: VAXport Driver
Explanation: The port driver detected a power down interrupt from the
port.
User Action: Call Digital Services to check the port power supply.
Port Power Up
Facility: VAXport Driver
Explanation: The port driver logs this event.
User Action: None.
98

Message Descriptions

Port timeout
Facility: VAXport Driver
Explanation: The port driver attempts to reinitialize the port; after
50 attempts, it marks the device off line.
.
User Action:. Call Digital Services to check the port hardware, the CI cable,
and the node number configuration.
Port Transition Failure - CNF/PMC/PSR 'xxxxxxxxlxxxxxxxxlxxxxxxxx'
Facility: VAXport Driver
Explanation: The port driver attempts to reinitialize the port; after 50 failed
attempts, it marks the device off line.
User Action: Call Digital Services to check the port hardware.
Port ucode not at current rev level. PROM/RAM rev is· 'xxxx/xxxx'
Facility: VAXport Driver
Explanation: The port driver continues port operation.
User Action: Check the console storage device for the latest microcode
version. For ports with on-board microcode, call Digital Services to upgrade
the port microcode. Prolonged operation of the port with obsolete microcode is
not supported by Digital.
POSERROR, error positioning 'filespec'
Facility: BACKUP, Backup Utility
Explanation: The Backup utility encountered an error during an attempt to
reposition the specified file. The accompanying message provides additional
information.
User Action: Correct the condition that caused the error and reenter the
command.
POSITERR, error positioning ' save-set-spec'
Facility: BACKUP, Backup Utility
Explanation: The Backup utility encountered an error during an attempt to·
reposition the specified save-set volume. The accompanying message provides
additional information.
User Action: Correct the condition that caused the error and reenter the
command.
PREFIX, searching for ICBM with the prefix 'prefix'
Facility: IOGEN
Explanation: This message displays while IO AUTOCONFIGURE searches
through IOGEN Configuration Building Modules (ICBMs), configures devices,
and loads drivers.
User Action: None.
PROCDONE, operation completed. Processing finished at 'date-time'
Facility: BACKUP, Backup Utility
Explanation: Standalone backup processing has completed.
User Action: None.

Message Descriptions

PROCGONE, Process not in system
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
PROCINDEX, error processing index file on 'device,' RVN 'n'
Facility: BACKUP, Backup Utility
Explanation: The Backup utility encountered an error during an attempt
to process the index file, [OOOOOO]INDEXF.SYS;l, on the specified relative
volume of the specified device. The accompanying message provides
additional information.
User Action: Correct the condition that caused the error and reenter the
command.
PRTEXT, file only partially extended. Volume may be too fragmented.
Facility: SYSGEN, System Generation Utility
Explanation: The SYSGEN command CREATE failed due to insufficient
disk space.
User Action: Clean up your disk space or specify a smaller /SIZE qualifier.
PRVNOTUNQ, privilege name 'name' is not unique
Facility: INSTALL, Install Utility
Explanation: An abbreviation was entered for a privilege name that is not
unique.
User Action: Specify at least four characters for the privilege name and
retry.
PSUSPECT, customer defined text
Facility: LAVC, Local Area VMScluster
Explanation: The local area VMScluster network failure analysis has
located a network problem and reported this network component as the
primary suspect. Several PEDRIVER channels that were using this network
component have failed. The analysis indicates that this component or
something connected to it is the most likely cause of the network problems.
User Action: Ask the system manager or network manager to look into the
network problem.

100

Message Descriptions

PTELENVIOL, unexpected page table length violation
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
PTRCNT, ACP block count exceeds retrieval pointer size
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
PURGWSSCN, purge working set scan 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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
PWDEXPIR, your password has expired - contact your system manager
Facility: LOGIN, Login Procedure
Explanation: The password is valid for a specific length of time as
determined by your system manager. When a password reaches the end
of its specified time period, it expires and can no longer be used to gain access
to the system. This is a system security feature that forces users to change
their passwords on a regular basis. You should have been receiving advance
messages notifying you when your password would expire.
User Action: Ask your system manager for a new password.

101

Message DesC?riptions

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: Submit a Software Performance Report (SPR) that.describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
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. A subsequent message describes the
nature of the error.
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, [OOOOOO]QUOTA.SYS;l, 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 using the SYSMAN command
DISKQUOTA CREATE.
RCTUNRSZR, RCT unreadable, output SERIALNUM field set to zero
Facility: BACKUP, Backup Utility
Explanation: This message warns the user that the disk's Replacement and
Caching Table was unreadable. As a result, the output volume serial number
is set to 0.
User Action: None.
RDSNONRES, read data substitute page nonresident
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
102

Message Descriptions

/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
READATTR, error reading attributes for 'filespec'
Facility: BACKUP, Backup Utility
Explanation: The Backup utility encountered an error during an attempt
to read the file attributes of the specified file. The accompanying message
provides additional information.
User Action: Correct the condition that caused the error and reenter the
command.
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. The accompanying
message provides additional information.
User Action: Correct the condition that caused the error and reenter the
command.
READ BLOCK, error reading block 'n' of 'filespec'
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, [OOOOOO]BITMAP.SYS;l, 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. An accompanying message provides additional
information. The Backup utility terminates processing of the directory.
User Action~ Examine the directory using the DCL command DIRECTORY
and reconstruct files as necessary.
READ ERRS, 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 medium is probably unusable.
User Action: Retire the save-set medium.

103

Message Descriptions

READ IMAP, 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, [OOOOOOJINDEXF.SYS;l, 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.
READYREAD, mount volume 'n' on 'device-name' for reading
Press return 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
Press return 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: 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.
REBLDREQ, rebuild not performed; some free spaces unavailable; disk quota
usage stale
Facility: MOUNT, Mount Utility
Explanation: A volume has been improperly dismounted (such as during a
system crash), and subsequently mounted with the /NOREBUILD qualifier
of the MOUNT command. The error occurs because a volume that has been
dismounted improperly must be rebuilt to recover any caching limits that
were enabled on the volume when it is dismounted. The rebuild operation
restores the volume's disk quota information and recovers any preallocated
free space in the EXTENT cache and any file numbers in the FILE_ID cache.
User Action: Rebuild the volume by entering the DCL command SET
VOLUME/REBUILD.
REBUILD, volume is improperly dismounted; rebuild in progress
Facility: MOUNT, Mount Utility
Explanation: A disk is improperly dismounted and information is lost.
REBUILD will reconstruct the file structure on the volume.
User Action: None.
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.
104

Message Descriptions

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: This message occurs when the /PROCESSOR=UNIQUE
qualifier is used with the MOUNT co~mand and insufficient paged pool
is 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 is allocated.
The usual reason to use the /PROCESSOR=UNIQUE qualifier before
OpenVMS Version 4.0 is to avoid the problem of file system activity on
one volume degrading file system performance on other volumes. This
degradation is caused by the single-threaded nature of the file system ACP. In
OpenVMS Version 4.0, the procedure-based file system XQP provides a higher
level of concurrency than is previously possible even with multiple ACPs. The
/PROCESSOR qualifier is retained to allow discrete I/O buffer caches to be
associated wit~ specific volumes, instead of all volumes sharing the same I/O
buffer cache, which is the default behavior.
User Action: Remove the /PROCESSOR= UNIQUE qualifier. However, 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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
Remote System Conflicts with Known System
Facility: VAXport Driver
Explanation: The VAXport 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 the new system down as soon as possible. Reboot it with
a unique SCSYSTEMID and SCSNODE. Do not leave the new system up any
longer than necessary. If you are running a VMScluster and two systems
with conflicting identity are polling when any other virtual circuit failure

105

Message Descriptions

takes place in the VMScluster, then systems in the VMScluster may crash
with a CLUEXIT bugcheck.
REMOUVOL, REMOUNT relative volume nn (volume label) on 'device-name'
Facility: MOUNT, Mount Utility
Explanation: An error occurred on a magnetic tape requiring operator
intervention.
User Action: Perform the required physical actions and use the DCL
command REPLY to notify the ACO the volume is ready.
REMOVED, entry for 'filespec' has been removed
Facility: INSTALL, Install Utility
Explanation: The Known File Entry was removed successfully. This
message is informational.
User Action: None.
Response Queue Remove Failure
Facility: VAXport Driver
Explanation: The VAXport 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), or BI
(VAX 8200, VAX 8300, and VAX 8800) contention.
User Action: Call Digital Services.
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.

106

Message Descriptions

RMSBUG, RMS has detected an invalid condition
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
RQSTDONE, request 'number' is satisfied
Facility: MOUNT, Mount Utility
Explanation: The request completed successfully and was cancelled by the
requestor.
User Action: None.
RSBREFNEG, RSB 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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
RSBREFNZRO, tried to deallocate RSB with non-zero ref. count
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
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
SYSGEN CONFIGURE.
User Action: Do not specify RSV as a device name.

107

Message Descriptions

RUF, fatal error detected by Recovery Unit Facility
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
RVNlNOTMT, 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 not,
mount it and reenter the command. Verify the device names and volume
labels specified in the command and retry the operation.
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
devices or a list of 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 saveset. 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 did
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 would default to the current default device (the input device).
User Action: Check the command line to ensure that the device
specifications are syntatically 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 had 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
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: Enter the command again, with the save-set name in the first
element of the list.

108

Message Descriptions

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 will automatically reboot if the BUGREBOOT system parameter is set
to 1.
User Action: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
SCANDEADPT, scan dead page table 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 will automatically reboot if the BUGREBOOT system parameter is set
to 1.
User Action: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
SCBRDERR, SCB physical read error halt
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 will automatically reboot if the BUGREBOOT system parameter is set
to 1.
User Action: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
SCSSYSTEMID has NOT been set to a nonzero value
Facility: VAXport 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
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 will automatically reboot if the BUGREBOOT system parameter is set
to 1.
User Action: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the

109

Message Descriptions

/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
SETLIMIT, too many volumes on 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: Any of the following conditions can cause this error:
•

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

User Action: Try one or more of these user actions:
•

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 name in VMB 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 fine, check the SYSGEN
parameter settings for inappropriate memory configurations.

SHADDETINCON, SHADOWING detects inconsistent state
Facility: BUGCHECK, System Bugcheck
Explanation: The volume shadowing software reached an unrecoverable or
inconsistent situation because the software failed an internal inconsistency
check.
User Action: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. If the system is configured to produce a
memory dump, include the dump file with the SPR.

110

Message Descriptions

SHORTBLOCK, save set block is 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
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 will automatically reboot if the BUGREBOOT system parameter is set
to 1.
User Action: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
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 medium when convenient.
Software is Closing Virtual Circuit
Facility: VAXport Driver
Explanation: The VAXport driver closes 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: VAXport Driver
Explanation: The VAXport 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 medium when convenient.

111

Message Descriptions

SPECIFY, specify option ('valid-options')
Facility: BACKUP, Backup Utility
Explanation: The Backup utility encountered a fatal error. A recovery
action must be selected. If the QUIT option is selected, the utility will
terminate. If the CONTINUE option is selected, the utility will ignore the
error. If the RESTART option is selected, the utility will restart the operation
at the beginning of the current save-set volume.
User Action: Evaluate the preceding errors and select one of the options
listed in the message. If the utility is executing as an interactive job, enter
the option in response to the prompt on SYS$COMMAND. If the utility is
executing as a batch job, use the DCL command REPLY to enter the option.
SPECLBL, the label was not specified
Specify EXACT_ORDER 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: The user must specify a volume label to be used in exact
volume order checking.
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).
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 within 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.
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 the
continue option, the Backup utility will continue reading the new save set.

112

Message Descriptions

SSRVEXCEPT, unexpected system service exception
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
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 unrecoverable or
inconsistent situation and is beginning a bugcheck sequence. If the system
is configured to take a memory dump, messages similar to the following
messages might accompany the dump:
Header and error log buffers dumped ...
SPT & GPT dumped ...
System space (SO) 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 PO and Pl
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.

113

Message Descriptions

Global and process pages are optional when writing a dump in that 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 the situation that caused the OpenVMS
operating system to write the memory dump indicates that you should
submit a Software Performance Report (SPR), a copy of the dump file should
accompany the SPR.
Starting memory dump ... Memory dump complete
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS operating system reached an unrecoverable or
inconsistent situation and is beginning a bugcheck sequence. If the system is
configured to take 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, ifthe situation that caused the system to write
the memory dump indicates that you should submit a Software Performance
Report (SPR), a copy of the dump file just written should accompany the SPR.
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 back-up dates in response to the /RECORD qualifier.
User Action: If the /SINCE=BACKUP or /BEFORE=BACKUP qualifiers are
used, note that data will be lost if the operation is restarted using the same
output medium. 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 online 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 A~tion: Ensure that the device from which standalone backup booted
stays online during the entire backup operation.

114

Message Descriptions

STATENTSVD, software state not saved during powerfail
Facility: BUGCHECK, System Bugcheck
Explanation: Before power is lost, the volatile software state of the VAX
processor is 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
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
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: Reenter the command specifying a shorter string.
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.
SUBALL, device ' device' has been allocated to this subprocess
Facility: BACKUP, Backup Utility
Explanation: The backup operation is being run from a subprocess. The
device has been explicitly allocated to the subprocess to ensure that a
subsequent volume can be mounted if a volume switch occurs.
User Action: None.

115

Message Descriptions

SUBNOALL, unable to allocate device 'device' to this subprocess
Facility: BACKUP, Backup Utility
Explanation: The backup operation is being run from a subprocess. The
device cannot be explicitly allocated to the subprocess because it is already
mounted or allocated to another process.
User Action: If the backup operation could require a subsequent volume,
the operation should be aborted because backup will not be able to mount
subsequent volumes. The device is not explicitly owned by the subprocess,
so it will be owned by the parent process when the volume dismount is
performed to load the next volume.
SWAPAGINS, all additional page and 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/swap file, reboot and
install the correct file.
SWAPWSLE, swap working set list entries 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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
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
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
116

Message Descriptions

SYSBOOT-E-Bad image header detected while checking system version
Facility: SYSBOOT, System Bootstrap Facility
Explanation: The versions of the system loadable image being read do not
match the current OpenVMS operating system versions. The images on your
system disk are incompatible.
User Action: Obtain a new copy of the OpenVMS system disk.
SYSBOOT-E-Device names not allowed
Facility: SYSBOOT, System Bootstrap Facility
Explanation: Device names are not valid when specifying a parameter
with the USE command. The device defaults to the system root (usually the
[SYSO.] directory on the system device).
User Action: Reenter the command without a device name.
SYSBOOT-E-End of file error reading
Facility: SYSBOOT, System Bootstrap Facility
Explanation: An end-of-file error occurred while SYSBOOT was reading a
system loadable image; the error message includes the file name. The system
disk may be corrupt.
User Action: Attempt to reboot the system or try a different drive. If this
fails, obtain a new copy of the OpenVMS system disk.
SYSBOOT-E-Error reading file
Facility: SYSBOOT, System Bootstrap Facility
Explanation: An irrecoverable error occurred while SYSBOOT was reading
a parameter file in response to a USE command. The error message contains
the file name.
User Action: Reenter the command specifying the correct file name.
SYSBOOT-E-I/O error reading file
Facility: SYSBOOT, System Bootstrap Facility
Explanation: An irrecoverable I/O error occurred while SYSBOOT was
reading a parameter file or a system loadable image. If the error occurred
while a parameter file was being read, SYSBOOT does not perform the
requested action. If the error occurred while a system loadable image was
being read, SYSBOOT terminates the bootstrap operation.
User Action: Attempt to reboot the system or try a different drive.
SYSBOOT-E-Not a parameter file
Facility: SYSBOOT, System Bootstrap Facility
Explanation: A file specified in a USE command is not a parameter file. The
error message contains the file name.
User Action: Reenter the command specifying a parameter file.
SYSBOOT-E-System version mismatch found
Facility: SYSBOOT, System Bootstrap Facility
Explanation: The versions of the system loadable image being read do not
match the current OpenVMS operating system versions. The images on your
system disk are incompatible.
User Action: Obtain a new copy of the OpenVMS system disk.

117

Message Descriptions

SYSBOOT-E-Unable to locate file
Facility: SYSBOOT, System Bootstrap Facility
Explanation: SYSBOOT cannot locate a file; error message will contain the
file name.
User Action: Reenter the command specifying the correct file name or mount
the correct medium in the console drive.
SYSBOOT-F-Boot time files have too many noncontiguous pieces
Facility: SYSBOOT, System Bootstrap Facility
Explanation: This error occurs during system initialization. The system
dump, page, or swap file is overly fragmented; that is, approximately
100 pieces.
User Action: Back up the system disk using the backup disk as the new
system disk. The Backup utility copies the files in a such way that the files
consist of fewer fragments.
SYSBOOT-F-FBIC version less than minimum required for VMS
Facility: SYSBOOT, System Bootstrap Facility
Explanation: The hardware ECO level is below the level required for correct
software operation.
User Action: Call Digital Services.
SYSBOOT-F-Invalid console ID
Facility: SYSBOOT, System Bootstrap Facility
Explanation: The console type code in the console identification register
does not correspond to any supported console device for the VAX-11 processor
being booted.
User Action: Call Digital Services.
SYSBOOT-F-Microcode revision level too low to boot
Facility: SYSBOOT, System Bootstrap Facility
Explanation: The hardware ECO level for the VAX-11 processor being
booted is below that required to boot the OpenVMS operating system.
User Action: Call Digital Services.
SYSBOOT-F-Not enough nonpaged pool to map
Facility: SYSBOOT, System Bootstrap Facility
Explanation: SYSBOOT is unable to allocate sufficient nonpaged pool to
map a driver or system loadable image. The error message will include the
file name.
User Action: Reboot the system with a larger value for NPAGEDYN.
SYSBOOT-F-Pageable system space exceeds 512 MB
Facility: SYSBOOT, System Bootstrap Facility
Explanation: The size of pageable system space exceeds that which can
safely be mapped with page file backing store.
User Action: Reconfigure the system to require less page able system space
and reboot the system. Reduce one or more of the PAGEDYN and GBLPAGES
parameters.

118

Message Descriptions

SYSBOOT-F-PFN allocation overwrites CI ucode
Facility: SYSBOOT, System Bootstrap Facility
Explanation: The allocation of physical pages for the system page table,
nonpaged dynamic pool, interrupt stack, and resident executive overwrites
the CI microcode.
User Action: Reconfigure the system to require less physical memory and
reboot the system. Reduce one or more parameters controlling the allocation
of physical memory: NPAGEDYN, BALSETCNT, and VIRTUALPAGECNT.
SYSBOOT-F-PFN bit map conflict - Physical page count set too low
Facility: SYSBOOT, System Bootstrap Facility
Explanation: SYSBOOT cannot find sufficient contiguous pages of physical
memory (within the bounds specified by the parameter PHYSICALPAGES) to
contain the PFN bitmap.
User Action: Reboot the system with a larger value for PHYSICALPAGES.
SYSBOOT-F-Switch of boot volume attempted with SO_PAGING=O, must be 1
Facility: SYSBOOT, System Bootstrap Facility
Explanation: An attempt was made to switch the boot volume while system
paging was turned on. System paging must be turned off.
User Action: Set the system parameter SO_PAGING to 1 and reboot.
SYSBOOT-F-System revision less than minimum required for VMS
Facility: SYSBOOT, System Bootstrap Facility
Explanation: The hardware ECO level is below the level required for correct
software operation.
User Action: Call Digital Services.
SYSBOOT-F-Unable to allocate physical memory
Facility: SYSBOOT, System Bootstrap Facility
Explanation: The sum of pages required for the system page table, non paged
dynamic pool, interrupt stack, and resident executive exceeds available
physical memory.
User Action: Reconfigure the system to require less physical memory and
reboot the system. Reduce one or more parameters controlling the allocation
of physical memory: NPAGEDYN, BALSETCNT, ~nd VIRTUALPAGECNT.
SYSBOOT-F-Unable to allocate PTEs for Boot Driver
Facility: SYSBOOT, System Bootstrap Facility
Explanation: SYSBOOT is unable to allocate the system page table entries
(PTEs) needed by the boot driver.
User Action: Increase the value of parameter SPTREQ.
SYSBOOT-F-Unable to allocate SPT+PHD+SCB
Facility: SYSBOOT, System Bootstrap Facility
Explanation: SYSBOOT cannot find enough contiguous pages of physical
memory to contain the required system page table (SPT), process header
(PHD), and system control block (SCB).
User Action: Reduce parameters controlling SPT size: VIRTUALPAGECNT,
BALSETCNT, REALTIME_SPTS, and SPTREQ.

119

Message Descriptions

SYSBOOT-F-Unable to locate storage bit map file
Facility: SYSBOOT, System Bootstrap Facility
Explanation: SYSBOOT cannot locate the storage bitmap file (BITMAP.SYS)
in directory [000000] on the system disk. The system disk is either defective
or corrupt.
User Action: Obtain a new copy of the OpenVMS system disk.
SYSBOOT-F-Unable to locate SYS.EXE
Facility: SYSBOOT, System Bootstrap Facility
Explanation: SYSBOOT cannot locate the system image file in directory
[SYS$LDR] on the bootstrap volume. The system disk is either defective or
corrupt, or the disk being accessed is not the system disk.
User Action: Obtain a new copy of the OpenVMS system disk.
SYSBOOT-F-Unable to read continuation volume
Facility: SYSBOOT, System Bootstrap Facility
Explanation: An error occurred while trying to read the continuation volume
when booting the OpenVMS operating system from multiple volumes.
User Action: Attempt to reboot the system; try a different drive or obtain a
new copy of the OpenVMS system disk.
SYSBOOT-F-Unexpected exception
Facility: SYSBOOT, System Bootstrap Facility
Explanation: An unexpected exception occurred indicating a probable
hardware error or SYSBOOT logic error.
User Action: Call Digital Services.
SYSBOOT-F-Unexpected machine check
Facility: SYSBOOT, System Bootstrap Facility
Explanation: An unexpected machine checkoccurred indicating a probable
hardware error or SYSBOOT logic error.
User Action: Call Digital Services.
SYSBOOT-F-Unknown processor
Facility: SYSBOOT, System Bootstrap Facility
Explanation: The processor type code in the system identification register
does not correspond to any supported model of a VAX-11 processor.
User Action: Digital Services.
SYSBOOT-I-GBLPAGES have been trimmed
Facility: SYSBOOT, System Bootstrap Facility
Explanation: The combined size of the system and global page tables
exceeds the OpenVMS architectural maximum (4,194,303 pages). SYSBOOT
has reduced the size of the global page table by decreasing the SYSGEN
parameter GBLPAGES.
· User Action: Review the ACTIVE value of the GBLPAGES parameter to
make sure it is large enough to support normal system operation in your
environment. Using SYSMAN, reevaluate the values of the parameters that
determine the size of the system and global page tables, especially if the value

120

Message Descriptions

computed by AUTOGEN has been overridden in MODPARAMS.DAT. (Refer
to the OpenVMS System Management Utilities Reference Manual.)
SYSBOOT-W-DMPFRG SYSDUMP.DMP is too fragmented to be used
Facility: SY_SBOOT, System Bootstrap Facility
Explanation: The system dump file is severely fragmented.
User Action: Back up the system disk and use the backup disk as the new
system disk.
SYSBOOT-W-ECO level less than minimum required for VMS
Facility: SYSBOOT, System Bootstrap Facility
Explanation: The hardware ECO level is below the level required for correct
software operation.
User Action: Call Digital Services. The bootstrap operation may be
continued, but the integrity of the software may be compromised.
SYSBOOT-W-FPLA, PCS, or WCS version less than minimum required for VMS
Facility: SYSBOOT, System Bootstrap Facility
Explanation: The hardware ECO level is below the level required for correct
software operation.
User Action: Call Digital Services. The bootstrap operation may be
continued, but the integrity of the software may be compromised.
SYSBOOT-W-Maximum WS raised to PHD+MINWSCNT
Facility: SYSBOOT, System Bootstrap Facility
Explanation: SYSBOOT raised the specified maximum working set size
to accommodate the minimum working set size allowed by the OpenVMS
operating system. To execute, every process requires a minimum fluid
working set (MINWSCNT) plus space for its process header (PHD).
User Action: None.
SYSBOOT-W-Microcode patch level less than minimum required for VMS
Facility: SYSBOOT, System Bootstrap Facility
Explanation: The hardware ECO level is below the level required for correct
software operation.
User Action: Call Digital Services. The bootstrap operation may be
continued, but the integrity of the software may be compromised.
SYSBOOT-W-Microcode version less than minimum required for VMS
Facility: SYSBOOT, System Bootstrap Facility
Explanation: The hardware ECO level is below the level required for correct
software operation.
User Action: Call Digital Services. The bootstrap operation may be
continued, but the integrity of the software may be compromised.

121

Message Descriptions

SYSBOOT-W-Primary home block is bad
Facility: SYSBOOT, System Bootstrap Facility
Explanation: The primary home block of the system disk could not be read
and an alternate block was selected for use as the home block.
User Action: Back up the system disk and then use the backup disk as the
new system disk. The current system disk should be reinitialized.
SYSBOOT-W-Sy~tem ROM version less than minimum required for VMS

Facility: SYSBOOT, System Bootstrap Facility
Explanation: The hardware ECO level is below the level required for correct
software operation.
User Action: Call Digital Services. The bootstrap operation may be
continued, but the integrity of the software may be compromised.
SYSBOOT-W-WS default and quota raised to PDH+MINWSCNT
Facility: SYSBOOT, System Bootstrap Facility
Explanation: SYSBOOT raised the default working set size specified to
accommodate the sizes of the process header plus the minimum fluid working
set size.
User Action: None.
SYSINIT, 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, 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.
SYSINIT, 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.

122

Message Descriptions

SYSINIT, primary 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:[SYSMGRJSYPAGSWPFILES.COM file.
SYSINIT-E-create process error on STARTUP, status = 'status'
Facility: SYSINIT, System Initialization
Explanation: An error occurred while creating the STARTUP process. An
accompanying message provides more information.
User Action: Take corrective 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, which can determine the ident for you.
SYSINIT-E-error loading message file, status = 'status'
Facility: SYSINIT, System Initialization
Explanation: The system message file, SYS$MESSGAE: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

123

Message Descriptions

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 and reboot the system.
SYSINIT-E-error opening or mapping FllBXQP, 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.

124

Message Descriptions

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

•

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:

125

Message Descriptions

•

If there is not enough non paged pool, see the message INSFMEM for
_information about making enough nonpaged pool available for booting the
system.

•

Do not set PAGFILCNT to zero.

•

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 1/0 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.
SYSPWDTMO, system password timeout
Facility: LOGIN, Login Proce~ure
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
SYSVERCHK, system version mismatch - function aborted
Facility: SYSGEN, System Generation Utility
Explanation: An attempt to do a WRITE CURRENT operation failed
because the version of SYSGEN.EXE does not match SYS.EXE.
User Action: Reenter the command with the proper version of
SYSGEN.EXE.

126

Message Descriptions

SYSVERDIF, system version mismatch - please relink
Facility: INSTALL, Install Utility
Explanation: The image being installed is not linked against the current
version of the system.
User Action: Relink the image and retry the installation.
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 or block size specified by /RECORDSIZE or
/BLOCKSIZE is greater than 65,534.
User Action: Check the source program 'and make the necessary correction.
TAPECLASS, fatal error detected by Tape Class driver (TUDRIVER)
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
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.
TIPCUFLOW, NETACP - transmit count underflow
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)

127

Message Descriptions

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 within SYSGEN.
User Action: The proper way to load the TMSCP server is to set the
SYSGEN parameter TMSCP_LOAD to 1. This action loads the server, which
services all locally connected MSCP type tape drives during SYSBOOT.
TMSCPSERV, encountered unrecoverable error
Facility: BUGCHECK, System Bugcheck
Explanation: The TMSCP server encountered an unrecoverable error.
User Action: Submit a Software Performance Report (SPR). Include a copy
of the crash dump with the SPR.
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 the SYSMAN utility'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 is entered with too
many controllers specified for a given type.
User Action: Reenter the SYSGEN command CONFIGURE with the correct
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 within SYSGEN. The TMSCP server has already been
loaded in the recommended way.
User Action: The proper way to load the TMSCP server is to set the
SYSGEN parameter TMSCP_LOAD to 1. This action loads the server, which
services all locally connected MSCP-type tape drives during SYSBOOT.
TWICE, device 'controller-name' - count changed from 'count' to 'count'
Facility: SYSGEN, System Generation Utility
Explanation: A controller name is specified twice for a given SYSGEN
command CONFIGURE.
User Action: Verify the value you intend to use.

128

Message Descriptions

UBMAPEXCED, UNIBUS map register allocation exceeded
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
UDAPORT, fatal error detected by UDA port driver (PUDRIVER)
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the·
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
UNABLCREVA, unable to create virtual address space
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
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: VAXport Driver
Explanation: The port driver attempts to reinitialize the port; after 50 failed
attempts, it marks the device off line.
User Action: Call Digital Services to check the port hardware.

129

Message Descriptions

UNEXPIOINT, unexpected I/O adapter interrupt
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKPP qualifier with the BACKUP command that produces
the save set included with the SPR.)
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 entered.
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: Retry specifying a different CPU type.
UNKDEV, unknown device type
Facility: MOUNT, Mount Utility
Explanation: The device type specified is unknown or invalid.
User Action: Verify the device name (or logical name if a logical name is
specified), and reenter the command with the correct device name.
UNKNPRQ, unknown Inter-processor Request Message
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
UNKRSTRT, unknown restart code
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
130

Message Descriptions

/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
Unrecognized SCA Packet
Facility: VAXport Driver
Explanation: The VAXport 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: Submit a Software Performance Report (SPR), including the
error log file that contains this entry and the crash dumps from both the local
and remote systems.
UNRELVOL, volume is not part of volume set being mounted
Facility: MOUNT, Mount Utility
Explanation: A volume was specified to be mounted that is not part of a
volume set.
User Action: Either mount the specified volume separately or specify the
/BIND qualifier with the DCL command MOUNT.
UNSUPRTCPU, unsupported CPU
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
UNXINTEXC, unexpected interrupt or exception
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
UNXSIGNAL, unexpected signal name in 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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the

131

Message Descriptions

system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
USERAUTH, error accessing authorization record
Facility: LOGIN, Login Procedure
Explanation: The Login processor could not read the specific 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.
VASOVF, system virtual address space limit exceeded
Facility: SYSBOOT, System Bootstrap Facility
Explanation: The combination of SYSGEN parameters used to specify
various capacities within the operating system have pushed the size of
the operating system address space over the limit allowed by the VAX
architecture.
User Action: Reduce one or more parameters that contribute to the virtual
address space size required by the OpenVMS system: VIRTUALPAGECNT,
BALSETCNT. By using AUTOGEN to set these values for your system, you
will avoid selection of parameter combinations that cause system space to
overflow its architectural boundaries.
VAXport is going off line
Facility: VAXport Driver
Explanation: The VAXport driver halts port operations.
User Action: Restore power to the port hardware.
VAXport is reinitializing
Facility: VAXport Driver
Explanation: The VAXport reinitializes the port and restarts port
operations.
User Action: None.
VBNERROR, 'filespec' has duplicate blocks 'n' through 'n'
Facility: BACKUP, Backup Utility
Explanation: The specified blocks of the specified file were present more
than once in the input save set. Data in the save set may be corrupt.
User Action: Examine the file for corruption and reconstruct as necessary. If
this error occurs during a disk-to-disk (copy) operation, it indicates a software
error in the Backup utility; in this case, submit a Software Performance
Report (SPR).

132

Message Descriptions

VBNMAPFAIL, virtual block map failure
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
VBNMISSING, 'filespec' has missing blocks 'n' through 'n'
Facility: BACKUP, Backup Utility
Explanation: The specified blocks of the specified file were missing from the
input save set. Data in the blocks is lost.
User Action: Examine the file for corruption and reconstruct as necessary. If
this error occurs during a disk-to-disk (copy) operation, it indicates a software
error in the Backup utility; in this case, submit a Software Performance
Report (SPR).
VBNPASTEOF, 'filespec' has blocks 'n' through 'n' past end of file
Facility: BACKUP, Backup Utility
Explanation: The specified blocks of the specified file were present in the
input save set although they follow the end of file block. Data in the save set
may be corrupted.
User Action: Examine the file for corruption and reconstruct as necessary. If
this error occurs during a disk-to-disk (copy) operation, it indicates a software
error in the Backup utility; in this case, submit a Software Performance
Report (SPR).
VECINUSE, vector is in use
Facility: SYSGEN, System Generation Utility
Explanation: The interrupt vector address that is specified in a SYSGEN
command CONNECT is being used by another device.
User Action: Change the vector address in the device driver and reenter the
SYSGEN command CONNECT.
VERIFYERR, verification error for block 'n' of 'filespec'
Facility: BACKUP, Backup Utility
Explanation: During a compare or verify operation, the data in the specified
block of the specified file did not agree with the input file. If other file
activity is occurring on the volume, the error may result because another user
modified the file during the backup procedure.
User Action: Note that the copies are inconsistent.

133

Message Descriptions

Virtual Circuit Timeout
Facility: VAXport Driver
Explanation: The VAXport driver closes the virtual circuit that the local
CI port opened to the remote port. This closure occurs if the remote node
is running CI Microcode Version 7 or higher, and the remote node failed to
respond to any messages sent by the local node.
User Action: This error is normal if the remote system halted, crashed, or
is shut down. This error may mean the local node's PASTIMOUT SYSGEN
parameter is set too low, especially if the remote node is running privileged
user-written software.
VOLALRMNT, another volume of same label already mounted
Facility: MOUNT, Mount Utility
Explanation: This message can occur under either of the following
conditions:
•

A request was made to mount a volume that has the same label as a
volume already mounted. Shared, group, and system volumes that are
mounted concurrently must have unique volume labels.

•

A request was made to mount a volume that is already mounted /GROUP
for another group.

User Action: Take one of the following actions, as appropriate:
•

Mount the volume as a private volume if it does not have to be shared.

•

Wait until the conflicting volume has been dismounted.

•

If the volume is already mounted to another group, wait for the volume to
be dismounted from that group.

You can determine the status and ownership of a conflicting volume by using
the DCL command SHOW DEVICES/FULL/MOUNTED.
VOLIDENT, label= 'volume-label', owner= 'user-name', format= 'volumeformat'
Facility: MOUNT, Mount Utility
Explanation: This message identifies an incorrectly specified volume after
the INCVOLLABEL and NOHOMEBLK errors in a MOUNT request.
User Action: None. If the volume protection allows access to the volume,
reenter the DCL command MOUNT.
VOLINSET, 'device-name' is already part of a volume set
Facility: BACKUP, Backup Utility
Explanation: The specified volume is already bound to a volume set. The
volume cannot be used as a save-set disk.
User Action: Retry the operation using a properly initialized Files-11
Structure Level 2 volume.

134

Message Descriptions

VOLINSET, volume is already part of another volume set
Facility: MOUNT, Mount Utility
Explanation: The volume specified in the DCL command MOUNT/BIND is
part of another volume set.
User Action: Check the device name specified. Either use another volume or
initialize this one.
VOLNAME, volume 'volume-name' in
Facility: MOUNT, Mount Utility
Explanation: This message is optionally issued with the MOUNTDEV
message. It includes the volume name of the volume being mounted.
User Action: None.
VOLO ERR, must override owner identifier field in VOLl label on 'device-name'
Facility: MOUNT, Mount Utility
Explanation: The owner identifier field of the VOLl label must be
overridden to allow access to the tape. The OWNER_ID option of the MOUNT
/OVERRIDE command is used to interchange magnetic tapes between the
OpenVMS operating system and other Digital operating systems.
User Action: Reenter the MOUNT command and include the
/OVERRIDE=OWNER_ID option.
VOLOOO, volume 'label' is out of order, volume label 'label' was expected
Facility: BACKUP, Backup Utility
Explanation: One or more volumes and their exact order were specified in
the command line. The loaded volume is not the expected volume according
to the order specified in the command line.
User Action: Examine the volume labels and their order as specified in
the command line. The user or the operator must respond to the prompt to
specify what action to take to complete this backup operation.
VOLSETSTS, change of status for volume set 'volume-set-name'
Facility: MOUNT, Mount Utility
Explanation: MOUNT encountered a condition that resulted in a change
of state for the specified volume set. Accompanying messages describe the
nature of the change.
User Action: Take appropriate action based on information in the
accompanying message.
VOLSHDWMEM, mounting a shadow set member volume; volume write locked
Facility: MOUNT, Mount Utility
Explanation: This message indicates that the volume being mounted is a
former shadow set member. To prevent accidental destruction of data, this
volume is being mounted write-locked.
User Action: To allow write access to this volume, dismount the volume and
remount it with the /OVERRIDE=SHADOW_MEMBERSHIP qualifier.

135

Message Descriptions

VOLSTATUS, change of status for volume 'volume-name'
Facility: MOUNT, Mount Utility
Explanation: MOUNT encountered a condition that resulted in a change of
state for the specified volume. Accompanying messages describe the nature of
the change.
User Action: Take appropriate action based on information in the
accompanying message.
VOLUSED, volume with label 'label' was already used in this save operation
Facility: BACKUP, Backup Utility
Explanation: The command specifies that accidental volume overwrite is to
be avoided. The label on the loaded volume matches a volume label previously
written in this save operation.
User Action: Examine the volume labels and their order specified in the
command line. The user or the operator must respond to the prompt to
specify what action to take to complete this backup operation.
WACKQEMPTY, NETACP - ack wait 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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
WAITIDLEBCB, attempted wait on idle buffer
Facility: BACKUP, Backup Utility
Explanation: A software error occurred in the Backup utility.
User Action: Submit a Software Performance Report (SPR).
WCBFCBMNG, WCB/FCB correspondence broken
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)

136

Message Descriptions

WCSCORR, WCS error correction failed
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
WORKING, customer defined text
Facility: LAVC, Local Area VMScluster
Explanation: The local area VMScluster network failure analysis
determined that this network component is working.
User Action: If the network component is indeed working, no user action
is required. However, if this message displays when the network component
is not working, have the system manager or network manager look into the
network problem. In such a case, the network description does not accurately
represent the physical network. Review the defined network components
by calling SYS$LAVC_DEFINE_NET_COMPONENT. Review the defined
network path descriptions by calling SYS$LAVC_DEFINE_NET_PATH.
Correct any problems as necessary.
WRITEACT, ACTIVE system parameters modified by process ID 'pid'
Facility: SYSGEN, System Generation Utility
Explanation: This message is written to the operator's console when
a WRITE ACTIVE operation is done from SYSGEN. This message is a
monitoring aid for the system manager.
User Action: None.
WRITEATTR, error writing attributes for 'filespec'
Facility: BACKUP, Backup Utility
Explanation: The Backup utility encountered an error during an attempt
to write the file attributes of the specified file. The accompanying message
provides additional information.
User Action: Correct the condition that caused the error and reenter the
command.
WRITEBACK, error writing backup date for 'device-name' file ID ('file-id')
Facility: BACKUP, Backup Utility
Explanation: The Backup utility encountered an error during an attempt
to update the backup date of the specified file. The accompanying message
provides additional information. If other file activity is occurring on the
volume, the error may be caused by another user who may have deleted the
file during the backup procedure.
User Action: If necessary, correct the condition that caused the error and
reenter the command.

137

Message Descriptions

WRITEBLOCK, error writing block 'n' of 'filespec'
Facility: BACKUP, Backup Utility
Explanation: The Backup utility encountered an error during an attempt
to write the specified block of the specified file. The accompanying message
provides additional information.
User Action: Examine the file for corruption; reconstruct the file as
necessary.
WRITECUR, CURRENT system parameters modified by process ID 'pid' into
file 'filespec'
Facility: SYSGEN, System Generation Utility
Explanation: This message is written to the operator's console when a
WRITE CURRENT operation is done from SYSGEN. This message is a
monitoring aid for the system manager.
User Action: None.
WRITEJNLACE, error writing journal ACE for 'filespec' file ID 'file-id'
Facility: BACKUP, Backup Utility
Explanation: The Backup utility could not write out the journal access
control entry (ACL) for the specified file.
User Action: Determine why the ACL could not be written. This could
be due to a corrupt ACL or some other hardware or software related error.
Correct the problem if possible and retry the backup operation.
WRITELOCK, volume is write locked
Facility: MOUNT, Mount Utility
Explanation: This message indicates that the DCL command MOUNT found
the volume to be write-locked.
User Action: None, unless you wish to write on the volume. In that case,
you must write-enable the drive, and dismount and mount the volume.
WRITENABLE, write enable volume 'n' on 'device-name'
Facility: BACKUP, Backup Utility
Explanation: The Backup utility requires that the specified volume of an
output save set be write-enabled.
User Action: Note that the Backup utility will write on the volume, ensure
that a suitable volume has been mounted, and write-enable the volume. If
the utility is executing as an interactive job, reply YES to the prompt on
SYS$COMMAND. If the utility is executing as a batch job, use the DCL
command REPLY to signal completion.
WRITERRS, excessive error rate writing ' save-set-spec'
Facility: BACKUP, Backup Utility
Explanation: The Backup utility encountered numerous write errors in the
specified save set. The save-set medium is probably unusable.
User Action: Retire the save-set medium.

138

Message Descriptions

WRITESCB, write error on storage control block; volume is write locked
Facility: MOUNT, Mount Utility
Explanation: An I/O error occurred while the volume was being mounted;
the volume has been write-locked to protect its integrity.
User Action: Check the hardware and retry the program.
WRONGVOL, device 'device-name' contains the wrong volume
Facility: MOUNT, Mount Utility
Explanation: The specified volume does not match the volume in the drive.
User Action: Correct the volume name and retry the operation.
WRONGVOL, 'save-set-spec' is not the next volume in the set
Facility: BACKUP, Backup Utility
Explanation: The volume mounted as a continuation volume of a
multivolume save set is not the successor of the previous volume of the
save set. Volumes must be processed in the order of their creation.
User Action: Locate and mount the correct continuation volume.
WRTHOMBLK, I/O error writing home block
Facility: MOUNT, Mount Utility
Explanation: An I/O error occurred writing the home block of a volume
during the MOUNT/BIND operation.
User Action: Check that the hardware is functioning properly. Reinitialize
the disks and retry the operation.
WRTINVBUF, ACP attempted to write an invalid buffer
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
WRTINVHDR, ACP attempted to write an invalid file header
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)

139

Message Descriptions

WRTPGSBAK, write pages back - inconsistent data base
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
WS default and quota raised to PHD +MINWSCNT
Facility: SYSBOOT, System Bootstrap Facility
Explanation: The default size of the working set has been increased to equal
the sum of the working set count (which is the count of fluid working set
pages), plus the process header.
User Action: None.
WSLENOVAL, working set list entry 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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
·
WSLPAGCNT, working set list page count 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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
WSLVANVAL, working set list virtual adr has non-valid PTE
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the

140

Message Descriptions

system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
WSLXVANMAT, working set list entry does not match VA
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
WSSIZEERR, working set size less than pages in use
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)
XORERRS, 'n' errors recovered by redundancy group in 'save-set-spec'
Facility: BACKUP, Backup Utility
Explanation: The Backup utility successfully recovered from uncorrectable
read errors in the specified save set the specified number of times by using
the redundancy information.
User Action: None. However, if the number of errors appears excessive,
consider retiring the save-set medium at a convenient time.
XQPERR, Error detected by file system XQP
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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)

141

Message Descriptions

ZEROPAGE, Zero page table entry from swap map
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an irrecoverable, inconsistent
condition. After all of 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: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error. Include a backup save set containing the
system dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier with the BACKUP command that produces
the save set included with the SPR.)

142

Index
c
Condition codes
definition, 1-3

E
Exception conditions
system messages for, 1-4

F
F$MESSAGE lexical function, 1-3

H
HELP/MESSAGE command, 2-4
in a command procedure, 2-1
qualifiers, 2-4
Help Message utility (MSGHLP), 2-1
adding .MSGHLP$DATA files to the database
2-9
'
adding messages to the database, 2-10
changing Digital-supplied data, 2-13
changing user-supplied text in the database
2-12
'
compressing the database after deletions 2-11
creating a .MSGHLP$DATA file, 2-10 '
creating a .MSGHLP file, 2-8
customizing the database, 2-8
using a process-level search path, 2-9
default database, 2-9
default operation, 2-1
deleting messages from the database 2-11
facilities in the database, 2-2
'
/FACILITY qualifier, 2-7
features, 2-1
HELP/MESSAGE command 2-4
/LIBRARY qualifier, 2-9 '
matching exact words only, 2-2
modifying the database, 2-10
search path of database files
in login file, 2-9
specifying database files with /LIBRARY, 2-9

M
MSGHLP
See Help Message utility
.MSGHLP$DATA files
creating, 2-10
using to customize the Help Message database
2-8
'
.MSGHLP files
creating, 2-8
format of, 2-9
using to create a .MSGHLP$DATA file 2-11
using to delete messages from the HELP
/MESSAGE database, 2-11
using to modify a .MSGHLP$DATA file, 2-8

N
NCP (Network Control Program) messages
accessing message descriptions using Help
Message, 2- 7

R
Recovery procedures
for command entry errors, 1-4
for errors due to unavailable resources 1-5
for programming errors, 1-5
'

s
SET MESSAGE command
used to access uninstalled messages, 2-7
$STATUS symbol
accessing value stored in, 1-3
System messages
accessing message data without using Help
Message, 1-3
accessing system messages, 1-1
condition codes, 1-3
exception conditions, 1-4
format, 1-1
recovery procedures, 1-4

lndex-1

NOTES

How to Order Additional Documentation

Technical Support
If you need help deciding which documentation best meets your needs, call 800-DIGITAL (800-344-4825)
and press 2 for technical assistance.

Electronic Orders
If you wish to place an order through your account at the Electronic Store, dial 800-234-1998, using a
modem set to 2400- or 9600-baud. You must be using a VT terminal or terminal emulator set at 8 bits, no
parity. If you need assistance using the Electronic Store, call 800-DIGITAL (800-344-4825) and ask for an
Electronic Store specialist.

Telephone and Direct Mail Orders
From

Call

Write

U.S.A.

DECdirect
Phone: 800-DIGITAL
(800-344-4825)
FAX: (603) 884-5597

Digital Equipment Corporation
P.O. Box CS2008
Nashua, NH 03061

Puerto Rico

Phone: (809) 781-0505
FAX: (809) 749-8377

Digital Equipment Caribbean, Inc.
3 Digital Plaza, 1st Street
Suite 200
Metro Office Park
San Juan, Puerto Rico 00920

Canada

Phone: 800-267-6215
FAX: (613) 592-1946

Digital Equipment of Canada Ltd.
100 Herzberg Road
Kanata, Ontario,. Canada K2K 2A6
Attn: DECdirect Sales
Local Digital subsidiary or
approved distributor

International
Internal Orders 1
(for software
documentation)

DTN: 241-3023
(508) 874-3023

Software Supply Business (SSB)
Digital Equipment Corporation
1 Digital Drive
Westminster, MA 01473

Internal Orders
(for hardware
documentation)

DTN: 234-4325
(508) 351-4325
FAX: (508) 351-4467

Publishing & Circulation Services
Digital Equipment Corporation
NR02-2
444 Whitney Street
Northboro, MA 01532

1Call to request an Internal Software Order Form (EN-01740-07).

Reader's Comments

OpenVMS System Messages:
Companion Guide for
Help Message Users

AA-PV5TA-TK
Your comments and suggestions help us improve the quality of our publications.
Thank you for your assistance.

I rate this manual's:
Accuracy (product works as manual says)
Completeness (enough information)
Clarity (easy to understand)
Organization (structure of subject matter)
Figures (useful)
Exam pl es (useful)
Index (ability to find topic)
Page layout (easy to find information)

Excellent

Good

Fair

Poor

D
D
D
D
D
D
D
D

I would like to see more/less

What I like best about this manual is

What I like least about this manual is

I found the following errors in this manual:
Page

Description

Additional comments or suggestions to improve this manual:

For software manuals, please indicate which version of the software you are using:

Name/Title

Dept.

Company

Date

Mailing Address
Phone

Do Not Tear - Fold Here and Tape
No Postage
Necessary
if Mailed
in the
United States

BUSINESS REPLY MAIL
FIRST CLASS PERMIT NO. 33 MAYNARD MASS.
POSTAGE WILL BE PAID BY ADDRESSEE

DIGITAL EQUIPMENT CORPORATION
OpenVMS Documentation
110 SPIT BROOK ROAD ZK03-4/U08
NASHUA, NH 03062-2642

II I1111iiIiiI111iiI1111I1I11I1I1II111I11I1iiii1I1I1 I
Do Not Tear-Fold Here - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Reader's Comments

OpenVMS System Messages:
Companion Guide for
Help Message Users

AA-PV5TA-TK
Your comments and suggestions help us improve the quality of our publications.
Thank you for your assistance.

I rate this manual's:
Accuracy (product works as manual says)
Completeness (enough information)
Clarity (easy to understand)
Organization (structure of subject matter)
Figures (useful)
Examples (useful)
Index (ability to find topic)
Page layout (easy to find information)

Excellent
D
D
D
D
D
D
D
D

Good

Fair

Poor

D
D
D
D
D
D
D
D

I would like to see more/less

What I like best about this manual is

·What I like least about this manual is

I found the following errors in this manual:
Page

Description

Additional comments or suggestions to improve this manual:

For software manuals, please indicate which version of the software you are using:

N ame!I'i tle

Dept.
Date

Company
Mailing Address
Phone

Do Not Tear - Fold Here and Tape
No Postage
Necessary
if Mailed
in the
United States

BUSINESS REPLY MAIL
FIRST CLASS PERMIT NO. 33 MAYNARD MASS.
POSTAGE WILL BE PAID BY ADDRESSEE

DIGITAL EQUIPMENT CORPORATION
OpenVMS Documentation
110 SPIT BROOK ROAD ZK03-4/U08
NASHUA, NH 03062-2642

III11111II1II1111II1111I1I11I1I1II111I11I11I1I1I1I1 I
---

Do Not Tear - Fold Here