Digital PDFs

AA-LA18A-TE

December 1988

390 pages

Original

16MB

Document:	VMS System Messages and Recovery Procedures Reference Manual: Partll
Order Number:	AA-LA18A-TE
Revision:
Pages:	390
Original Filename:	http://bitsavers.org/pdf/dec/vax/vms/5.0/AA-LA18A-TE_VMS_5.0_System_Messages_and_Recovery_Procedures_Reference_Manual_Part_2_198804.pdf

OCR Text

VMS System Messages
and Recovery Procedures
Reference Manual: Part II
Order Number: AA-LA 1 SA-TE

April 1988
The VMS System Messages and Recovery Procedures Reference Manual:
Part // lists messages MACHINECHK through ZEROP AGE produced by the
VMS operating system. Each message is accompanied by an explanation
and, where applicable, a suggested recovery procedure.

Revision/Update Information:

This document supersedes the
VAX/VMS System Messages and
Recovery Procedures Reference Manual,
Version 4.4.

Software Version:

VMS Version 5.0

digital equipment corporation
maynard, massachusetts

April 1988
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.
Copyright © 1988 by Digital Equipment Corporation
All Rights Reserved.
Printed in U.S.A.
The postpaid READER'S COMMENTS form on the last page of this document
requests the user's critical evaluation to assist in preparing future documentation.
The following are trademarks of Digital Equipment Corporation:
DEC
DEC/CMS
DEC/MMS
DECnet
DECsystem-10
DECSYSTEM-20
DEC US
DECwriter

DIBOL
EduSystem
IAS
MASSBUS
PDP
PDT
RSTS
RSX

UNIBUS
VAX
VAXcluster
VMS
VT

~urnuo~o™
ZK4660

HOW TO ORDER ADDITIONAL DOCUMENTATION
DIRECT MAIL ORDERS
USA & PUERTO Rico*

CANADA

INTERNATIONAL

Digital Equipment Corporation
P.O. Box CS2008
Nashua, New Hampshire
03061

Digital Equipment
of Canada Ltd.
100 Herzberg Road
Kanata, Ontario K2K 2A6
Attn: Direct Order Desk

Digital Equipment Corporation
PSG Business Manager
c/o Digital's local subsidiary
or approved distributor

In Continental USA and Puerto Rico call 800-258-1710.
In New Hampshire, Alaska, and Hawaii call 603-884-6660.
In Canada call 800-267-6215.
*Any prepaid order from Puerto Rico must be placed with the local Digital subsidiary (809-754-7575).
Internal orders should be placed through the Software Distribution Center (SOC), Digital Equipment
Corporation, Westminster, Massachusetts 01473.

Production Note
This book was produced with the VAX DOCUMENT electronic publishing
system, a software tool developed and sold by DIGITAL. In this system,
writers use an ASCII text editor to create source files containing text and
English-like code; this code labels the structural elements of the document,
such as chapters, paragraphs, and tables. The VAX DOCUMENT software,
which runs on the VMS operating system, interprets the code to format the
text, generate a table of contents and index, and paginate the entire document.
Writers can print the document on the terminal or line printer, or they can use
DIGITAL-supported devices, such as the LN03 laser printer and PostScript®
printers (PrintServer 40 or LN03R ScriptPrinter), to produce a typeset-quality
copy containing integrated graphics.

PostScript is a trademark of Adobe Systems, Inc.

Contents
PREFACE

vii

NEW AND CHANGED FEATURES

xiii

CHAPTER 1 INTRODUCTION

1-1

1.1

MESSAGE DISPLAY

1-1

1.2

RETRIEVING A SYSTEM MESSAGE

1-1

1.3

EXCEPTION CONDITIONS

1-2

1.4
1.4.1
1.4.2
1.4.3

FORMAT OF SYSTEM MESSAGES
Messages Without IDENTS
Severity Levels
Linked Messages

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

1.5
1.5.1
1.5.2
1.5.3
1.5.4

RECOVERY PROCEDURES
Recovering from Command Entry Errors
Unavailable Resources
Recovering from Programming Errors
Reporting System Software or Hardware Errors

1-4
1-5
1-5
1-6
1-6

1.6

EXAMPLES

1-6

CHAPTER 2 MESSAGES

2-1

TABLES
1

Facility Abbreviations

vii

Preface
Intended Audience
The VMS System Messages and Recovery Procedures Reference Manual: Part II
is intended for all users of the VMS operating system, including programmers
and system managers.

Document Structure
This manual consists of two chapters:
Chapter 1 describes the format of the messages and explains how to locate a
message.
Chapter 2 lists messages MACHINECHK through ZEROP AGE alphabetically
by message code. All messages are accompanied by explanatory text and,
where applicable, a suggested user action.

Associated Documents
The VMS System Messages and Recovery Procedures Reference Manual: Part
II is the second part of the VMS System Messages and Recovery Procedures
Reference Volume. You can find messages AAA through LUNRESSYS in the

VMS System Messages and Recovery Procedures Reference Manual: Part I.
This manual documents messages for the facilities listed below. The list
includes an associated document for each facility. You can refer to the
associated document for detailed information about a facility.
Table 1

Facility Abbreviations

Facility
Abbreviation

Facility Name

Document

ACCOUNTING

Accounting Utility

VMS Accounting Utility
Manual

A CLEO IT

Access Control list Editor

VMS Access Control
List Editor Manual

AUTHORIZE

Authorize Utility

VMS Authorize Utility
Manual

BACKUP

Backup Utility

VMS Backup Utility
Manual

BAD

Bad Block Locator Utility

VMS Bad Block Locator
Utility Manual

CDU

Command Definition Utility

VMS Command
Definition Utility Manual

Command Language Interpreter
(DCL)

Guide to Using VMS
Command Procedures

vii

Preface

viii

Table 1 (Cont.)

Facility Abbreviations

Facility
Abbreviation

Facility Name

Document

CONVERT

Convert Utility

VMS Convert and
Convert/Reclaim Utility
Manual

CONVERLR

Convert/Reclaim Utility

VMS Convert and
Convert/Reclaim Utility
Manual

CREF

Cross-Reference Utility

Guide to VMS
Programming Resources

DCL

DIGIT AL Command Language

VMS DCL Dictionary

DCX

Disk Compression Facility

VMS Utility Routines
Manual

DEBUG

VMS Debugger

VMS Debugger Manual

DIFF

DIFFERENCES Command

VMS DCL Dictionary

DISMOUNT

DISMOUNT Command

VMS DCL Dictionary

DSR

VAX DIGIT AL Standard Runoff

VAX DIGITAL Standard
Runoff Reference Manual

DTR

DECnet Program Protocol

VMS DECnet Test
Sender/DECnet Test
Receiver Utility Manual

DTK

VMS RTL DECtalk (DTK$) Facility

VMS RTL DECtalk
(DTK$) Manual

DUMP

File Dump Utility

VMS DCL Dictionary

EDT

EDT Editor

VAX EDT Reference
Manual

ERF

Error Log Utility

VMS Error Log Utility
Manual

EVL

Event Logger

VMS Networking
Manual

EXCHANGE

Exchange Utility

VMS Exchange Utility
Manual

FOL

Create/FOL Utility

VMS File Definition
Language Facility Manual

FOL

Edit/FOL Utility

VMS File Definition
Language Facility Manual

IMPSMB

Input Symbiont

Guide to Maintaining a
VMS System

INIT

INITIALIZE Command

VMS DCL Dictionary

INSTALL

Install Utility

VMS Install Utility
Manual

JBC

Job Controller

VMS System Services
Reference Manual

Preface

Table 1 (Cont.)

Facility Abbreviations

Facility
Abbreviation

Facility Name

Document

LATCP

LAT Control Program

VMS LAT Control
Program (LA TCP)
Manual

LBR

Librarian Utility

VMS Librarian Utility
Manual

LIB

VMS RTL Library (LIB$) Facility

VMS RTL Library (L/8$)
Manual

LIBRAR

LIBRARY Command

VMS Librarian Utility
Manual

LINK

Linker Utility

VMS Linker Utility
Manual

VMS DCL Dictionary

MACRO

VAX Macro Assembler

VAX MACRO and
Instruction Set
Reference Manual

MAIL

Mail Utility

VMS Mail Utility Manual

MESSAGE

Message Utility

VMS Message Utility
Manual

MOM

Maintenance Operation Module

VMS Networking
Manual

MONITOR

Monitor Utility

VMS Monitor Utility
Manual

MOUNT

MOUNT Command

VMS DCL Dictionary

MTH

VMS RTL Mathematics (MTH$)
Facility

VMS RTL Mathematics
(MTH$) Manual

NCP

Network Control Program

VMS Networking
Manual

NET

DECnet Test Program Protocol

VMS Networking
Manual

NICE

Network Information and Control
Exchange

VMS Networking
Manual

OPCOM

Operator Communication

Guide to Maintaining a
VMS System

OTS

VMS RTL General Purpose (OTS$)
Facility

VMS RTL General
Purpose (0TS$) Manual

PATCH

Patch Utility

VMS Patch Utility
Manual

PPL

VMS RTL Parallel Processing
(PPL$) Facility

VMS RTL Parallel
Processing (PPL$)
Manual

PRINT Command

VMS DCL Dictionary

PSI

Packetnet System Interface

VMS Networking
Manual

Preface

Table 1 (Cont.}

Facility Abbreviations

Facility
Abbreviation

Facility Name

Document

PSM

Print Symbiont

VMS Utility Routines
Manual

OU EM AN

Queue Manager

Guide to Maintaining a
VMS System

REM

Set Host Facility

VMS DCL Dictionary

RENAME

RENAME Command

VMS DCL Dictionary

RMS

VMS Record Management Services

VMS Record
Management Services
Manual

RUNOFF

DIGIT AL Standard Runoff

VAX DIGITAL Standard
Runoff Reference Manual

SDA

System Dump Analyzer

VMS System Dump
Analyzer Utility Manual

SEARCH Command

VMS DCL Dictionary

SET

SET Command

VMS DCL Dictionary

SHOW

SHOW Command

VMS DCL Dictionary

SMB

Symbiont Services

VMS Utility Routines
Manual

SMG

VMS RTL Screen Management
(SMG$) Facility

VMS RTL Screen
Management (SMG$)
Manual

SMI

System Management lntergator
/Server

Guide to Maintaining a
VMS System

SORT

Sort/Merge Utility

VMS Sort/Merge Utility
Manual

STR

VMS RTL String Manipulation
(STR$) Facility

VMS RTL String
Manipulation (STR$)
Manual

SUBMIT

SUBMIT Command

VMS DCL Dictionary

SUM

Source Update Merge Utility

VMS SUMSLP Utility
Manual

SYSBOOT

System Bootstrap Facility

Guide to Maintaining a
VMS System

SYSGEN

System Generation Utility

VMS System Generation
Utility Manual

SYSMAN

Cluster System Management
Utility

Guide to Maintaining a
VMS System

SYSTEM

VMS System Services

VMS System Services
Reference Manual

TRACE

Traceback Facility

VMS Linker Utility
Manual

VAXCLUSTER

V AXcluster Facility

VMS VAXcluster
Manual

Preface

Table 1 (Cont.)

Facility Abbreviations

Facility
Abbreviation

Facility Name

Document

VAXport

V AXport Driver

VMS VAXcluster
Manual

VAXTPU

VAX Text Processing Utility

VAX Text Processing
Utility Manual

VERIFY

Verify Utility

VMS Analyze/Disk_
Structure Utility Manual

VMSINSTAL

VMSINST AL Procedures

VMS Developer's Guide
to VMSINSTAL

Convention

Meaning

Conventions
In examples, a key name (usually abbreviated)
shown within a box indicates that you press
a key on the keyboard; in text, a key name is
not enclosed in a box. In this example, the key
is the RETURN key. (Note that the RETURN
key is not usually shown in syntax statements
or in all examples; however, assume that you
must press the RETURN key after entering a
command or responding to a prompt.)
CTRL/C

A key combination, shown in uppercase with a
slash separating two key names, indicates that
you hold down the first key while you press the
second key. For example, the key combination
CTRL/C indicates that you hold down the key
labeled CTRL while you press the key labeled C.
In examples, a key combination is enclosed in a
box.

$SHOW TIME
05-JUN-198811:55:22

In examples, system output (what the system
displays) is shown in black. User input (what
you enter) is shown in red.

$ TYPE MYFILE.DAT

In examples, a vertical series of periods, or
ellipsis, means either that not all the data that
the system would display in response to a
command is shown or that not all the data a
user would enter is shown.

input-file, ...

In examples, a horizontal ellipsis indicates
that additional parameters, values, or other
information can be entered, that preceding
items can be repeated one or more times, or
that optional arguments in a statement have
been omitted.

Preface

xii

Convention

Meaning

[logical-name]

Brackets indicate that the enclosed item is
optional. (Brackets are not, however, optional
in the syntax of a directory name in a file
specification or in the syntax of a substring
specification in an assignment statement.)

quotation marks
apostrophes

The term quotation marks is used to refer
to double quotation marks (" ). The term
apostrophe ( ·) is used to refer to a single
quotation mark.

New and Changed Features
Many new error messages have been added to each facility for Version 5.0.

xiii

Introduction

1 .1

Message Display
VMS 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. Also,
the system sometimes generates messages when a command has completed
successfully.
Messages are displayed on the current device and are identified by the
logical name SYS$0UTPUT. For an interactive user, this device is normally a
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 error 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
entered in the specified file.

1.2

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 numeral conforming to the format of a VMS
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.

You can display the current value of $STATUS by entering the following
command:
$ SHOW SYMBOL $STATUS
$STATUS == "%X00000364"

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:

1-1

Introduction
1 .2 Retrieving a System Message

$ WRITE SYS$0UTPUT F$MESSAGE($STATUS)
%SYSTEM-F-POWERFAIL, power failure occurred

Most of the messages in Chapter 2 of this manual are alphabetized by IDENT,
which is a short character string that uniquely identifies each message. If you
know the condition code for a message and you want to find its IDENT and
message text, 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

Note that 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

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 the Program Counter (PC) and Processor
Status Longword (PSL) at the time of the exception. 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 VMS RTL Library (LIB$) Manual for a more detailed discussion of condition
handling.

1 .4

Format of System Messages
Most of the messages displayed by the VMS operating system have the
following format:
%FACILITY-L-IDENT, TEXT
[-FACILITY-L-IDENT, TEXT]

FACILITY
A VMS facility or component name. A percent sign (%)prefixes the first
message entered, and a hyphen ( - ) prefixes each subsequent message.

L
A severity level indicator with one of the following values:
Code

Meaning

Success
Information

1-2

Warning

Error

Fatal, or severe error

Introduction
1 .4 Format of System Messages

IDENT
An abbreviation of the message text; the message descriptions are
alphabetized by this abbreviation.
TEXT
The explanation of the message.
[-FACILITY-L-IDENT,TEXT]
The next message.
An example of this type of message is shown as follows where LINK is the
facility name, E is the severity level, FATALERROR is the IDENT, and "fatal
error message issued" is the message text:
%LINK-E-FATALERROR, fatal error message issued

1.4.1

Messages Without IDENTS
The following facilities generate messages without IDENTS:
•

System Bootstrap Utility (SYSBOOT)

•

System Initialization (SYSINIT)

•

Virtual Memory Boot (VMB)

Such messages are alphabetized by facility name as shown in the following
example:
SYSBOOT-F-Unable to allocate physical memory

In this message SYSBOOT is the facility name, F is the severity level, and
"Unable to allocate physical memory" is the message text.
The following facilities display their messages without IDENTS and facility
names:
•

EDT Editor

•

DIGITAL Standard Runoff

•

System Management Utility

•

VAXport

You can find explanations and user actions for these messages by looking up
the first word of the message text. For example, the EDT editor generates the
following message:
Could not align tabs with cursor

The entry for this message can be found under "Could" in Chapter 2 of the

VMS System Messages and Recovery Procedures Reference Manual: Part I.

1-3

Introduction
1 .4 Format of System Messages

1.4.2

Severity Levels
The severity level of a message is included in the status message from
the component. You can identify the type of message you have received
by its severity level. Success and information messages inform you that
the system has performed your request. In some cases, the command
processing continues after issuing a success message. In other cases, the
message indicates that the command processing is complete.
Warning messages indicate that the command may have performed some, but
not all, of your request, and that you may have to verify the command or
program output.
Error messages indicate that the output or program result is incorrect, but the
system may attempt to continue execution.
Fatal messages indicate that the system cannot continue execution of the
request.

1.4.3

Linked Messages
Frequently, a system message will appear with more than one message.
When more than one message is issued, subsequent messages are prefixed
with a hyphen ( - ) rather than a percent sign ( % ). A series of messages
can help you determine the location of an error. Linked messages usually
display the return status of the different facilities called and provide a detailed
explanation of the error.
For example, the DCL command TYPE calls VMS Record Management
Services (VMS RMS) to locate and open a file. If the file does not exist, the
DCL command TYPE displays a message indicating that it cannot open the
file; a VMS RMS message follows, indicating the reason.
$ TYPE WWWW. FOR
%TYPE-W-OPENIN, error opening DB1:[JONES]WWWW.FOR; as input
-RMS-E-FNF, file not found

1.5

Recovery Procedures
Error messages generally occur for the following reasons:

1-4

•

A command is entered incorrectly; it contains a spelling or syntax error or
an incorrect file specification.

•

A required resource is currently unavailable.

•

A programming error is detected during the execution of an image.

•

A system software or hardware problem exists.

Introduction
1.5 Recovery Procedures

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 may 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 VMS 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 is invalid for one of the following reasons:

1.5.2

•

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 characters other than numerics or
alphabetics.

•

A connection to the target node could not be made.

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

Introduction
1.5 Recovery Procedures

1.5.3

Recovering from Programming Errors
If a program image terminates abnormally, you can get some information
about the error from the message. When a program image exits, the
command interpreter uses the current value of general register zero to obtain
information about the exit status. If it is an abnormal (or error) exit, the
system message associated with the register zero 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 VMS Debugger can help you discover and correct programming errors.
For details on how to use the debugger, refer to the 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.
The Introduction to VMS System Management provides information on how
to submit a Software Performance Report (SPR) to DIGITAL when you
encounter a software error. This guide also contains information on how
to run utilities that can verify that a hardware device is operational. If the
hardware device is not operational, inform the system manager.

1.6

Examples
[I

$ LINK DDD

%LINK-F-OPENIN,error opening device: [dir]DDD.OBJ; as input
%RMS-E-FNF, file not found

This LINK command used with the incorrect file name results in this series
of messages. These messages have all four portions: facility, severity level,
identification, and text.
~

$ SET MESSAGE/NOIDENTIFICATION

This SET MESSAGE command used with the /NOIDENTIFICATION qualifier
suppresses the IDENT portion of any messages that follow.
~

$ LINK DDD
%LINK-F,error opening device: [dir]DDD.OBJ; as input
%RMS-E, file not found

The LINK command used with the erroneous file name again results in a
series of messages without the IDENT portion.

1-6

Introduction
1.6 Examples

$ WRITE SYS$0UTPUT F$MESSAGE($STATUS)
%LINK-F-OPENIN, error opening 'input-file' as input"

The lexical function F$MESSAGE displays the value of the most recent
message stored in $STATUS.

1-7

Messages

MACHINECHK,

machine check while in kernel mode

Facility: BUGCHECK, System Bugcheck
Explanation: The VMS 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 of physical memory is written to
a system dump file, the system will automatically reboot if the BUGREBOOT
system parameter is set to one.
User Action: Thoroughly test all system hardware components. If no
hardware errors are located and if the problem persists, submit a Software
Performance Report. 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 on the BACKUP command to produce the
save set.)

MACLBFMTER,

macro library format error

Facility: MACRO, VAX MACRO Assembler
Explanation: A format error occurred in the MACRO library.
User Action: Retry the assembly and, if the error still occurs, use the DCL
command LIBRARY (see the VMS DCL Dictionary) to re-create the library
from the source code.

MACNAMLNG,

macro 'macro-name' name is too long in 'library-name'

Facility: LIBRAR, LIBRARY Command
Explanation: This error message is generated by the DCL command
LIBRARY. The name of the macro you attempted to insert into the library
exceeds the name-length limit.
User Action: Either rename the macro or extend the library's name-length
limit.

MACRO or KEY required
Facility: EDT, EDT Editor
Explanation: The EDT command DEFINE is incomplete. You must specify
either MACRO or KEY with the EDT command DEFINE using the format
DEFINE MACRO or DEFINE KEY.
User Action: Reenter the command including either MACRO or KEY.

2-1

Messages

MAILBOX,

mailbox error

Facility: CNF, NI Configurator
Explanation: An error occurred while reading a mailbox.
User Action: See the accompanying message to determine the appropriate
action.

MAKEWSLE,

make working set list entry error

Facility: BUGCHECK, System Bugcheck
Explanation: The VMS software detected an irrecoverable, inconsistent
cor.dition. 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, 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 on the BACKUP command
that produces the save set included with the SPR.)

MANY_TO_ONE,

input specifies multiple files, output a single file

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility encountered a COPY command which
has an input file specification which potentially represents more than one file,
and an output specification which gives exactly one file.
User Action: Reenter the command with a wildcard output file. EXCHANGE
does not append multiple input files into a single output file, if that is what is
desired, it will be necessary to copy the files to a Files-11 volume and use the
VMS COPY or APPEND commands to concatenate them. EXCHANGE can
then be used to copy the result file to the output volume.

MAP AREA,

file ('file-id') 'filename' invalid map area

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the specified file has a corrupted
map area.
User Action: The damage can probably be repaired by copying the file to
a new version and deleting the original version. It might be necessary to
reconstruct the file from backup media.

MAPCNTZER,

attempted to generate zero length map pointer

2-2

Messages

MAPHDRBAD,

storage map header is bad; volume locked

Facility: MOUNT, Mount Utility
Explanation: An 1/0 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.
MATCH,

match found against input string

Facility: STR, String Manipulation Facility
Explanation: A match is found for the input string that is passed to the
routine. This message indicates a success.
User Action: None.
MATCHED,

file specification-'xxx' records, 'yyy' matches

Facility: SEARCH, SEARCH Command
Explanation: This message displays the name of the file, the number of
records searched, and the number of records containing matches. This
message is informational.
User Action: None.
MATQUOMIS,

matching quote is missing

Facility: DEBUG, VMS Debugger
Explanation: The matching quote at the end of a quoted string is missing.
User Action: Correct the error and reenter the command.
Max input line of 2814749767 exceeded, file input terminated

Facility: EDT, EDT Editor
Explanation: You attempted to put more than 2,814,749,767 lines into a
buffer. EDT stops accepting additional lines when it reaches this limit.
User Action: None.
Max line number exceeded-lines no longer ascending; resequence recommended

Facility: EDT, EDT Editor
Explanation: EDT reached the limits of its line numbering capacity. If you
continue to add lines to your buffer, EDT is no longer able to number them
uniquely.
User Action: You should resequence the buffer if you have fewer lines than
line numbers.
Max number of lines for this buffer exceeded

Facility: EDT, EDT Editor
Explanation: You cannot add any more lines to this buffer.
User Action: You can place any remaining lines in a different buffer.

2-3

Messages

MAXBAD,

bad block table overflow

Facility: INIT, INITIALIZE Command and 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 and DISMOUNT, DISMOUNT Command
Explanation: More than 16 tape devices were specified in the DCL command
MOUNT or the DCL command DISMOUNT.
User Action: Reenter the DCL command MOUNT _or the DCL command
DISMOUNT; specify fewer than 16 devices.

MAXDIF,

maximum number of difference records encountered-DIP aborted

Facility: DIFF, DIFFERENCES Command
Explanation: The number of differences that have been found exceeds the
number that you specified with the /MAXIMUM_DIFFERENCES qualifier.
Therefore, the Differences Utility has terminated, listing only those difference
records that it encountered before the maximum is reached.
User Action: None.

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: LATCP, LAT Control Program
Explanation: The maximum of two links on a CREATE LINK command
already exists.
User Action: None.

MAXMAPPEDBUF,

a single buffer can be mapped to at most 'count' windows

Facility: VAXTPU, VAX Text Processing Utility
Explanation: You attempted to map a window to a buffer that already has its
maximum upper limit of windows mapped to it.
User Action: Map the window to a different buffer.

2-4

Messages

MAXPARM,

too many parameters-reenter command with fewer parameters

Facility: CLI, Command Language Interpreter (DCL)
Explanation: A command contained more than the maximum number of
parameters allowed. This error can be caused by:

•

Leaving blanks on a command line where a special character, for example,
a comma or plus sign, is required.

•

Using symbol names or logical names which, when substituted or
translated, contain embedded blank characters.

•

Failing to place quotation marks around a character string with embedded
blanks.

User Action: Determine the reason for the error and correct the syntax of the
command. Use the DCL command HELP or refer to the VMS DCL Dictionary
to determine the correct number of parameters for the command.

MAXSERV,

maximum number of services exceeded

Facility: LATCP, LAT Control Program
Explanation: Eight services have already been created on a service node.
User Action: Delete one of the existing services before creating a new one.

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 1/0 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.

MAXVALUE,

maximum value is 'integer'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The argument value that you used exceeds the maximum value
allowed.
User Action: Use an argument that is within the valid boundaries.

2-5

Messages

MAXVOLS,

too many volumes in volume set 'device-name'

Facility: VERIFY, Verify Utility and 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 Verify Utility can process
the volume.
User Action: Reconstruct the volume set from backup media.

MAYNOTINDX,

this mode may not be indexed

Facility: MACRO, VAX MACRO Assembler
Explanation: The base mode is register, immediate, or literal mode.
User Action: Change the addressing mode.

MBACBHUNG,

MBA CBHUNG bit set

MBC,

invalid multi-block count

Facility: RMS, VMS Record Management Services
Explanation: The multiblock count field of the RAB contains an invalid
value. The multiblock count must be in the range of 0 to 127.
User Action: Verify that the call to the VMS RMS service is coded correctly.

MBFULL,

mailbox is full

Facility: SYSTEM, VMS System Services
Explanation: A write request to a mailbox failed because the mailbox is full
and resource wait mode is not enabled. Its reader has not read the messages
it contains.
User Action: The writer of the mailbox can wait and try to write a message
later, if possible. If the error occurs frequently, the amount of buffer space
allocated when the mailbox is created should be increased so that more
messages can be written before any are read.

2-6

Messages

MBTOOSML,

mailbox is too small for request

Facility: SYSTEM, VMS System Services
Explanation: A write request to a mailbox failed because the message is
larger than the maximum message size specified when the mailbox is created.
User Action: Verify that the call to the service is coded correctly. Verify the
maximum message size specified for the mailbox, and increase the size if
necessary.
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 corrective action based on 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 corrective action based on the accompanying message.
MCHECK,

detected hardware error

Facility: SYSTEM, VMS System Services
Explanation: A hardware machine check has occurred.
User Action: Notify the system manager.
MCHECK,

unexpected Machine Check

Facility: VAXCLUSTER, VAXcluster Facility
Explanation: A machine check exception occurred during bootstrap
execution.
User Action: Run diagnostics on the satellite to check for hardware problems.
MCHINSTSYN,

machine instruction syntax error

Facility: MACRO, VAX MACRO Assembler
Explanation: A syntax error occurred in an instruction, for example,
MOVL, A.
User Action: Correct the instruction syntax.
MCNOTVALID,

device microcode is not valid

Facility: SYSTEM, VMS System Services
Explanation: The microcode has not yet been successfully loaded or has
become invalid. This is true only for the start microprocessor, initialize
LP All-K, set clock, and start data transfer request.
User Action: Contact a DIGITAL field service representative.

2-7

Messages

MDBSFCRUPT,

manufacturer's detected bad sector file is corrupt on 'devicename'

Facility: BAD, Bad Block Locator Utility
Explanation: The header information in the redundant MDBSF is corrupted.
User Action: Have the medium inspected.

MDBSFRFAI,

failed to read the manufacturer detected bad sector file on 'devicename'

Facility: BAD, Bad Block Locator Utility
Explanation: This error can occur as the result of any of the following
reasons:

•

The Bad Block Locator Utility could not locate a valid MDBSF.

•

The Bad Block Locator Utility could not rebuild the MDBSF and SDBSF
as a result of the execution context, for example, /EXERCISE=KEEP or
/BAD_BLOCKS.

•

The Bad Block Locator Utility could not locate a track copy of the
SDBSF (before the last track copy) for display purposes as a result of
the execution context /NOEXERCISE/BAD_BLOCKS/OUTPUT.

User Action: Reinvoke the Bad Block Locator Utility with a suitable execution
context to allow the utility to either display a converted device's bad block
file without any attempt to modify its contents. Note that the device is
converted through the MCR BAD /OVR command. Do not use the /BAD_
BLOCKS qualifier or the /EXERCISE=KEEP qualifier or allow the Bad Block
Locator Utility to re-create the bad blocks files with the default execution
context of ANALYZE/MEDIA/EXERCISE 'device-name'. This implies the
/EXERCISE=NOKEEP qualifier and no user-supplied bad block information.
Therefore, do not specify the /BAD_BLOCKS qualifier.

MDFYERR,

unable to update record

Facility: AUTHORIZE, Authorize Utility
Explanation: Your record is not updated.
User Action: Take corrective action based on the accompanying messages.

MDFYMSG,

user records updated

Facility: AUTHORIZE, Authorize Utility
Explanation: Your records were updated. This is an informational message.
User Action: None.

MEDOFL,

disk boot driver failure to open boot device

Facility: VAXCLUSTER, VAXcluster Facility
Explanation: The satellite node could not put its remote system disk on line.
User Action: Check the state of the system disk on the boot node. Use
the SHOW DEVICE/SERVED command to ensure that the system disk is
servable and on line.

2-8

Messages

MEDOFL,

medium is offline

Facility: SYSTEM, VMS System Services
Explanation: An 1/0 request cannot be satisfied because the device specified
is not on line and does not have a physical volume mounted on it. For
example, on a STARTUP request, the DEUNA hardware detected that the
table from the DEUNA on the UNIBUS is not connected to the DEUNA
bulkhead panel.
User Action: Connect the cable from the DEUNA module on the UNIBUS to
the DEUNA bulkhead panel. Mount the required volume on the device and
repeat the request.
MEI, missing at least one .ENDIF command
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: End-of-file is detected and at least one conditional DSR
command (.IF/ .IFNOT) is not legally terminated.
User Action: Insert the missing conditional commands. Check to see that
DSR commands .IF/ .ENDIF are matched within .REQUIRE files.
MEMBUG,

dynmem error size= 'nn' addr = 'nn' error= 'nn'

Facility: PATCH, Patch Utility
Explanation: An internal PATCH error has occurred.
User Action: Submit a Software Performance Report with a copy of the
Image File and the Link Map. Indicate the information contained in the error
message.
MEMBUG, memory (de)allocation bug 'number', 'address', 'number'
Facility: LINK, Linker Utility
Explanation: There is a problem with the linker.
User Action: Submit a Software Performance Report.
MEMERRS,

errors occurred writing memory contents to the dump file

Facility: SDA, System Dump Analyzer
Explanation: The first block of the dump file contains information indicating
that there were errors while writing out the contents of memory to the dump
file.

User Action: None. The dump file might not be useful for analysis.
MEMFUL,

insufficient virtual address space to complete this link

Facility: LINK, Linker Utility
Explanation: Your virtual address space is not large enough to complete the
link.
User Action: Either increase the virtual address space available or decrease
the size of the image. You can decrease the size of the image by (1) using
shareable images or by (2) encouraging demand-zero compression if the
image contains large data arrays. Contact your system manager to increase
your VIRTUALP AGCNT or PAGFILQUOTA.

2-9

Messages

MEMNOTSVD,

memory not saved in the dump file

Facility: SDA, System Dump Analyzer
Explanation: An attempt was made to examine the contents of a physical
memory location that was not saved when the subsetted dump file was
written. The requested information is not contained in the dump file.
User Action: None.

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. You
can 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 complete
Facility: SYSTEM, VMS System Services
Explanation: No errors were encountered during the dump write. This
message indicates a normal status.
User Action: None.

Memory dump complete after "dn" write errors
Facility: SYSTEM, VMS System Services
Explanation: Errors were encountered during the dump write operation.
User Action: Be aware that analysis of the crash dump might not be possible.

Memory dump incomplete-dump file "dn" blocks too small
Facility: SYSTEM, VMS System Services
Explanation: Output after writing out the memory dump if there is no room
in the dump file before writing out the full contents of physical memory and
the dump file is at least two blocks too small.
User Action: Make the memory dump file larger.

Memory dump incomplete-dump file 1 block too small
Facility: SYSTEM, VMS System Services
Explanation: Output after writing out the memory dump if there is no room
in the dump file before writing out the full contents of physical memory and
the dump file is one block too small.
User Action: Make the memory dump file larger.

2-10

Messages

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 you have room on the volume that holds the system dump
file, you can expand the dump file. If space is limited, you can try to write a
selective dump. Refer to the Guide to Setting Up a VMS System for the correct
procedures.

MERGE,

'n' records to be merged

Facility: ACCOUNTING, Accounting Utility
Explanation: When the /LOG qualifier is used with the /SORT qualifier, this
informational message describes the number of records to be sorted.
User Action: None.

Message Free Queue Insert Failure
Facility: VAXport, 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
(11/780), CMI (11/750), or BI (8200, 8300, and 8800) contention.
User Action: Contact your DIGITAL Field Service representative.

Message Free Queue Remove Failure
Facility: VAXport, VAXport Driver
Explanation: The VAXport driver attempts to reinitialize the port; after 50
failed attempts it marks the device off line.

MFN,

number illegal or malformed: 'string'

Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: A plus sign ( +) or a minus sign ( - ) is used alone, instead of +n
or -n.
User Action: Insert then value.

2-11

Messages

MFS,

missing or improperly delimited file spec: 'string'

Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: The file specification for the DSR command .REQUIRE is not
enclosed in apostrophes or quotation marks.
User Action: Enclose the file specification in apostrophes or quotation marks.
MFYNULPGFL,

FREWSLE-no backing store, page not modified

management program error

Facility: NCP, Network Control Program
Explanation: A software error occurred in the network management software.
User Action: Submit a Software Performance Report.
MHDERR,

module header error for 'module-name' in 'library-name'

Facility: LIBRAR, LIBRARY Command
Explanation: The specified module has an invalid header.
User Action: Compress the library before reentering the command line.
Micro-code Verification Error,

Facility: VAXport, 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 field service to check the port hardware.
MINVALUE,

minimum value is 'integer'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: You specified an argument value that is less than the minimum
value allowed.
User Action: Specify an argument that is within the valid boundaries.

2-12

Messages

MIRBFOVF,

mirror buffer exceeded

Facility: MOM, Maintenance Operation Module
Explanation: An attempt to allocate a buffer to be used for a LOOP NODE
or LOOP EXECUTOR command has failed. This might be because virtual
memory has been exhausted.
User Action: Increase the amount of virtual memory available for the
process.
MIRCTF,

mirror connect failed error

Facility: NCP, Network Control Program
Explanation: This error occurs if the connection to a loopback mirror fails.
A loopback mirror is a process created by the Network Control Program
command LOOP NODE to transmit test messages. The error indicates the
reason for the connection failure. Some possible reasons for connection
failure are an invalid or unrecognizable node name, a lack of network
resources, or a busy or unreachable node.
1

User Action: If the error occurred because of an incorrect node identifier,
correct the identifier and reenter your command. If network resources are
currently insufficient or if the node is inaccessible, reenter your command
when the network and node become available.
MIRDIS,

mirror link disconnected error

Facility: NCP, Network Control Program
Explanation: This error occurs if the connection to a loopback mirror is made
but subsequently disconnected. A loopback mirror is a process created by the
Network Control Program command LOOP NODE to transmit test messages.
The 1error 1 indicates the reason for the disconnection.
User Action: If the error occurred because of an incorrect node identifier,
correct the identifier and reenter your command. If network resources are
currently insufficient or if the node is inaccessible, reenter your command
when the network and node become available.
MISCONFUNI,

unibus/qbus 'device-name' is misconfigured

Facility: SYSGEN, System Generation Utility
Explanation: The vector on the device specified in the message needs to be
changed.
User Action: Call Field Service.
MISENDSTA,

missing END statement

Facility: SMG, Screen Management Facility
Explanation: The Termtable compiler expected an END statement to
terminate the current terminal definition and this END statement is missing.
User Action: Check your terminal definitions.

2-13

Messages

MISFILSPE,

missing file specification in REQUIRE statement

Facility: SMG, Screen Management Facility
Explanation: The REQUIRE statement needs a file name in order to locate
external definitions which should become part of your Termtable.
User Action: Check your TERMTABLE.TXT. Add a file name to the
REQUIRE statement.
MISINVNUM,

misplaced invocation number in 'path-name'

Facility: DEBUG, VMS Debugger
Explanation: The invocation number was not placed after the innermost
(rightmost) routine name in the specified path name.
User Action: Correct the path name and reenter the command.
MISMODBEG,

missing Module-Begin record in DST (compiler error)

Facility: DEBUG, VMS Debugger
Explanation: An expected Module-Begin record was not found in the Debug
Symbol Table. This indicates a probable error in the compiler output.
User Action: Submit a Software Performance Report.
MISMODEND,

missing Module-End in DST for 'path-name' (compiler error)

Facility: DEBUG, VMS Debugger
Explanation: An expected Module-End record was not found in the Debug
Symbol Table. This indicates a probable error in the compiler output.
User Action: Submit a Software Performance Report.
MISNAMREQ,

expected NAME or REQUIRE

Facility: SMG, Screen Management Facility
Explanation: The Termtable compiler expected TERMTABLE.TXT to begin
with a terminal definition NAME statement or a REQUIRE statement.
Something else is encountered.
User Action: Check your TERMTABLE.TXT.
MISREQP AR,

missing required parameter

Facility: JBC, Job Controller
Explanation: An item code that is required for the requested function is not
present.
User Action: Specify the required item.
MISSINGEND,

missing .END statement

Facility: MACRO, VAX MACRO Assembler
Explanation: There is no .END directive at the end of the module. The
assembler inserted an .END directive after the last line.
User Action: Insert an .END directive.

2-14

Messages

MISSINGQUOTE,

missing quote

Facility: VAXTPU, VAX Text Processing Utility
Explanation: Your program has an opening quote character without a
matching closing quote on the same line.
User Action: Add the missing closing quote and recompile your program.

MISSNGP ARM,

missing parameter 'parameter-name'

Facility: CDU, Command Definition Utility
Explanation: The parameters specified for a designated verb in the command
definition file are not consecutively named Pl, P2, ...
User Action: Rename the parameters consecutively.

MISSNGSYM,

missing argument

Facility: CDU, Command Definition Utility
Explanation: A required argument is missing from the CLD file.
User Action: Add the missing argument to your CLD file.

MISS_pARAM,

a required subroutine parameter is missing

Facility: SORT, Sort/Merge Utility
Explanation: You have omitted a required argument.
User Action: Identify which argument is missing and specify it.

MISSP ASS,

missing PASSWORD command

Facility: INPSMB, Input Symbiont
Explanation: A batch job entered from a card reader does not contain a
PASSWORD command following the JOB command.
User Action: Correct the error and reenter the job.

MISSQUO,

unmatched quotation marks in argument

Facility: PATCH, Patch Utility
Explanation: You did not use matching quotation marks or apostrophes to
enclose an argument.
User Action: Reenter the command using the correct quotation.

MISSQUOTE,

quoted string not terminated before end of line

Facility: CDU, Command Definition Utility
Explanation: CDU encountered an end-of-line while reading a quoted string
from a CLD file.
User Action: Edit the CLD file so that quoted strings do not cross line
boundaries.

2-15

Messages

MISSYMTAB,

missing symbol table

Facility: VAXTPU, VAX Text Processing Utility
Explanation: A required symbol table is missing.
User Action: Use the required symbol table or create one.

MISTERNAM,

definition must begin with a terminal name

Facility: SMG, Screen Management Facility
Explanation: Capabilities were preceded by the name of a terminal.
User Action: Check your terminal definitions. Make sure that each definition
starts with NAME= 'terminal-name'.

MIXEDTYPES,

operator with mixed or unsupported data types

Facility: VAXTPU, VAX Text Processing Utility
Explanation: An operator is being used with operands of different or
unsupported data types.
User Action: Check the data type of each operand being used and make sure
that the operator supports this.

MKD,

ACP could not mark file for deletion

Facility: RMS, VMS Record Management Services
Explanation: The file system ACP cannot delete the file. This message is
associated with a system status code returned from a file system ACP QIO
requests made by VMS RMS.
User Action: The status value (STV) field of the FAB contains a system status
code that provides more information about the condition. Take corrective
action based on this status code.

MLBOPNERR,

error opening macro library

Facility: MACRO, VAX MACRO Assembler
Explanation: An error occurred while attempting to open a macro library.
User Action: Ensure that the file specification is a valid macro library.

MNL,

missing number or letter: 'string'

Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: A required numerical value or text value is missing.
User Action: Insert the missing value.

MODIFIED,

'file/directory /volume' modified

Facility: SET, SET Facility
Explanation: The requested file, directory, or volume is modified. This
message is displayed when you specify the /LOG qualifier. The operation is
successful.
User Action: None.

2-16

Messages

MODIFYERR,

modify error code of xx on file filespec

Facility: PATCH, Patch Utility
Explanation: A VMS RMS $MODIFY request failed because of the error
code, represented as xx
1

•

User Action: Correct the error (represented as xx) and retry the request.
MODNAM,

module 1module-name 1 name length is illegal-not 1 to 1decimalnumber'

Facility: LINK, Linker Utility
Explanation: A module contained a header record with an invalid module
name.
User Action: Submit a Software Performance Report on the appropriate
language processor.
MODNAMLNG, illegal module-name 1module-name 1 of nnn characters in
library-name /
1

Facility: LIBRAR, LIBRARY Command
Explanation: This error message is generated by the DCL command
LIBRARY. The name of the object module you attempted to insert into
the library exceeds the name-length limit.
User Action: Rename the module before inserting it into the library.
1

MODNOTADD, insufficient symbol table space to add module module-name

Facility: PATCH, Patch Utility
Explanation: The PATCH command SET MODULE failed. This typically
occurs when there is not enough space in the symbol table to accommodate
the additional module or modules.
User Action: To make room for the new modules, enter the following
PATCH commands:
•

SHOW MODULE command to determine which modules are in the
symbol

•

CANCEL MODULE command specifying the module names whose
symbols are no longer required

•

SET MODULE command

MODNOTFND, library module 1module-name 1 not found in record 1number1,
Facility: PSM, Print Symbiont
Explanation: This status is returned by a print symbiont library input routine
indicating the specified library module is not found while processing this
record. The print symbiont failed to locate the specified module in the device
control library associated with this queue.
User Action: Insert the library module or specify the correct module library.

2-17

Messages

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'
('file-id')

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.
MODOUTBIS,

RMS before-image journaling disabled on saved copy of 'filespec'
('file-id')

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.
MODQUOTA,

error modifying quota record for ['UIC']

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility encountered an error during an attempt
to modify the usage data in the quota file entry for the specified UIC. The
accompanying message provides additional information.
User Action: Correct the condition that caused the error and reenter the
Verify Utility command line.

2-18

Messages

MODRELNBAK,

no backing store address for modified page

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.
MOUNTDEV,

please mount 'name' device 'device-name'

Facility: MOUNT, Mount Utility
Explanation: A request for operator assistance on MOUNT has occurred.
User Action: You can 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 is an informational message that verifies a request.
User Action: None.
MOUNTERR,

volume 'volume' on 'device' was not mounted because 'reason'

Facility: BACKUP, Backup Utility
Explanation: BACKUP 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 BACKUP 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>

2-19

Messages

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 will automatically dismount the volume.
MOUNTERROR,

error occurred during VMS mount on 'volume-name'

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility encounted an error while using the
$MOUNT system service to mount a volume.
User Action: A second message will follow, giving the specific condition
discovered by the $MOUNT service. Take corrective action based on the
second message.

MOUNTFl l,

'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 1/0 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 1/0 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.

MOUNTVER 'device-name' contains the wrong volume. Mount verification in
progress.
Facility: SYSTEM, VMS System Services
Explanation: The media in the named disk or tape drive has been changed
and is no longer that expected by the system. Mount verification recovery
procedures started.
User Action: Return the correct media to the named disk or tape drive.

MOUNTVER 'device-name' has aborted mount verification
Facility: SYSTEM, VMS System Services
Explanation: Mount verification was unable to restore access to the named
disk or tape. Either access could not be restored in the timeout interval
specified by system parameters, or an error occurred during the attempts to
restore access from which no recovery was possible.
User Action: The named disk or tape is inaccessible to system users. Access
can be restored only by dismounting and remounting device.

2-20

Messages

MOUNTVER 'device-name' has been write-locked. Mount verification in progress
Facility: SYSTEM, VMS System Services
Explanation: The write-locking hardware on the named disk or tape drive
was activated at a time when there is write activity for the device. Mount
verification recovery procedures have started.
User Action: Deactivate the write-locking hardware on the named disk or
tape.

MOUNTVER 'device-name' has completed mount verification
Facility: SYSTEM, VMS System Services
Explanation: The previously named problem, which initiated mount
verification is corrected. Normal access is restored to the named disk or
tape.
User Action: None.

MOUNTVER 'device-name' is offline. Mount verification in progress
Facility: SYSTEM, VMS System Services
Explanation: The named disk or tape is off line. Mount verification recovery
procedures have been initiated.
User Action: If manual intervention is required to make the named disk
or tape operative, perform the necessary action. For example, if a disk has
become off line because its unit plug was removed, replace the unit plug.

MOUNVTER 'member-unit' has been removed from shadow set
Facility: SYSTEM, VMS System Services
Explanation: The named shadow set member unit has been removed from
its shadow set. The name of the shadow set virtual unit appears in an
accompanying "shadow set has been reduced" message.
User Action: Correct the problem that caused the member's removal and
return the member to the shadow set using a MOUNT command.

MOUNVTER 'member-unit' is a possible shadow set member
Facility: SYSTEM, VMS System Services
Explanation: The named member drive was recently operational in a shadow
set that has been reduced to zero working members. The name of the affected
shadow set virtual unit appears in a previous "zero working members"
message.
User Action: Take action to make the member drive operational.

2-21

Messages

MOUNVTER 'member-unit' is an incorrect shadow set member volume.
Facility: SYSTEM, VMS System Services
Explanation: The media in the named member drive has been changed
and is no longer than expected. In most cases, this message is followed by
a message indicating that the named member has been removed from the
shadow set. However, if the shadow set has been reduced to zero members,
mount verification does not remove the member drive but waits for the
correct media to be returned to the member drive.
User Action: If the member is not removed from the shadow set, return the
correct media to the named member drive.

MOUNVTER 'member-unit' shadow copy has been completed
Facility: SYSTEM, VMS System Services
Explanation: A previously initiated shadowing copy operation, targeted at
the named member drive, finished.
User Action: None.

MOUNVTER 'member-unit' shadow copy has been started
Facility: SYSTEM, VMS System Services
Explanation: A shadowing copy operation started with the named member
drive as its target.
User Action: None.

MOUNVTER 'shadow-unit' all shadow set copy operations are completed
Facility: SYSTEM, VMS System Services
Explanation: All required shadowing copy operations have been completed
for the named shadow set virtual unit. The shadow set is not internally
consistent and is fully subject to normal shadowing data propagation and
availability rules.
User Action: None.

MOUNVTER 'shadow-unit' contains zero working members
Facility: SYSTEM, VMS System Services
Explanation: The named shadow set virtual unit has no working member
drives. Accompanying "possible shadow set member" messages name
previously working member drives that mount verification expects to be
returned to operational status.
User Action: Take action to make one of the subsequently named member
drives operational.

2-22

Messages

MOUNVTER 'shadow-unit' does not contain the member named to VMB. System
may not reboot.
Facility: SYSTEM, VMS System Services
Explanation: The named shadow set virtual unit is the virtual unit from
which the system has been booted. For this particular shadow set virtual unit,
the single shadow set member named in the input to the primary bootstrap
program (VMB) is no longer a shadow set member. Because of shadow set
booting mechanics, this condition may render the system unbootable.
User Action: The single shadow set member named in the input to the
primary bootstrap program (VMB) MUST be returned as a member of the
system disk shadow set ASAP.
MOUNVTER 'shadow-unit' shadow set has been reduced
Facility: SYSTEM, VMS System Services
Explanation: The named shadow set virtual unit has had one or more
members removed, as described in previous "member has been removed"
messages.
User Action: Correct the problem that caused the member's removal and
return the member to the shadow set using a MOUNT command.
MOUNVTER 'shadow-unit' shadow set has changed state. Mount verification in
progress.
Facility: SYSTEM, VMS System Services
Explanation: The named shadow set virtual unit has signaled a possible
change of membership or accessibility status. Mount verification recovery
procedures have been initiated.
User Action: No action is necessary unless indicated by additional mount
verification messages.
MOUSEINV,

mouse location information is invalid

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The mouse information is only valid after a mouse key has
been received. You are attempting to use a mouse function before a mouse
key is pressed.
User Action: Mouse functions should only be called by procedures bound to
the mouse keys.
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.

2-23

Messages

MOVEFILES, files will now be moved to their target directories.
Facility: VMSINSTAL, Install Procedures
Explanation: If sufficient disk space is available at the beginning of an
installation, VMSINSTAL builds new files in a working directory for the
optional product or update. After all the files are built, they are moved to
their target directories. This message is informational.
User Action: None.

MOVETOCOPY, move from unmodifiable buffer 'string' changed to copy
Facility: VAXTPU, VAX Text Processing Utility
Explanation: You cannot change the source buffer, so the MOVE_TEXT
request has been changed to a COPY_TEXT.
User Action: Use the SET (MODIFIABLE, ... ) built-in to allow
modifications.

MQS, missing or improperly delimited quoted strings: 'string'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: A beginning or ending apostrophe or quotation mark is missing
from the quoted text value.
User Action: Insert the missing apostrophe or quotation mark.

MRC,

another n crossed margin or bad right indent attempts detected and
accumulated. Now being reported

Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: A specific number (n) of similar horizontal spacing errors have
been detected and are now being reported. These errors are triggered by DSR
commands .CHAPTER or .APPENDIX or by the end-of-file. The count of
errors is cleared after each DSR command .CHAPTER and .APPENDIX or
after the end-of-file.
User Action: Check the margin and indent settings.

MRG, margins crossed, or attempted indent too far right
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: The right margin has crossed the left margin or the left margin
has crossed the right margin, or an invalid indent has been specified.
User Action: Check the margin and indent settings.

MRGGTMTCH, value of 'x' for /MERGE is greater than /MATCH value of 'y'
/MERGE set to 'y'
Facility: DIFF, DIFFERENCES Command
Explanation: You specified a /MERGE value greater than the /MATCH
value.
User Action: Decrease the /MERGE value. The /MERGE value must always
be less than or equal to the /MATCH value.

2-24

Messages

MRN, invalid maximum record number or record number exceeds MRN
Facility: RMS, VMS Record Management Services
Explanation: An incorrect record number is specified in one of the following
ways:

The maximum record number field contains a negative value for the
creation of a relative file.

The relative record number (pointed to by KBF) for a random operation
to a relative file exceeds the maximum record number specified when the
file is created.

User Action: Verify that the call to the VMS RMS service is coded correctly.
Modify the program, if necessary, to detect and respond to the condition.

MRS,

invalid maximum record size
Facility: RMS, VMS Record Management Services
Explanation: The maximum record size (MRS) field contains zero for a
$CREATE operation with fixed length records or a relative file. Or the
maximum record size specified for a magnetic tape file is less than 18.
User Action: Verify that the call to the VMS RMS service is coded correctly.

MRS, missing one or more .RESTORE commands at end of file
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: You have specified fewer .RESTORE commands than .SAVE
commands.
User Action: Specify the correct number of .RESTORE commands.

MSCPNOTLD,

MSCP-Server code not loaded

Facility: SET, SET Facility and SHOW, SHOW Command
Explanation: The code for the MSCP Server is not loaded at system
generation.
User Action: Make sure the MSCP Server code is loaded before trying to
enter the SET DEVICE command or the SHOW DEVICE command.

MSCPSERV, encountered unrecoverable error
Facility: MSCP, MSCP Server
Explanation: The MSCP server encountered an unrecoverable error.
User Action: Submit a Software Performance Report. Include a copy of the
crash dump with the report.

MSGBUFSET,

attempt to change modifiable setting of message buffer

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The message buffer cannot be set to be either modifiable or
unmodifiable.
User Action: Do not attempt to change the modifiable setting of the message
buffer.

2-25

Messages

MSGCMAIIF,

missing comma in .IIF statement

Facility: MACRO, VAX MACRO Assembler
Explanation: The condition is not separated from the statement in an .IIF
directive.
User Action: Insert a comma in the directive.
MSGNOTFND,

message not in system message file

Facility: SYSTEM, VMS System Services
Explanation: A message identification number specified in a system service
call or a lexical function does not have a message associated with it.
User Action: Check for a programming error.
MSGNOTFND,

message was not found, the default message has been returned

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The message identification code that you specified was not
found. The default message is returned.
User Action: None.
MTLBLLONG,

label specified for 'device-name' is longer than 6 characters

Facility: INIT, INITIALIZE Command
Explanation: The label the operator specified for the device is longer than six
characters.
User Action: Respecify the label with six or fewer characters.
MTLBLLONG,

magnetic tape volume label can be no more than six characters

Facility: SYSTEM, VMS System Services
Explanation: The label specified for a magnetic tape volume has more than
six characters.
MTLBLNONA, label specified for 'device-name' contains non-ANSI "a" characters
Facility: INIT, INITIALIZE Command
Explanation: The operator used invalid ANSI "a" characters in the volume
label. The set of valid ANSI "a" characters includes: digits 0 ... 9, uppercase
A ... Z, space, and! "% & '() * + ,-. /: ; < => ?.
User Action: Reenter the command with valid ANSI "a" characters.

2-26

Messages

MTXCNTNONZ,

mutex count nonzero at system service exit

cluster 'cluster-name' multiply defined in options file 'filename'

Facility: LINK, Linker Utility
Explanation: A cluster is defined more than once in an options file.
User Action: Delete one of the definitions and relink.
MULDEF,

symbol 'symbol-name' multiply defined in module 'module-name' file
'filename'

Facility: LINK, Linker Utility
Explanation: A global symbol is defined with different values.
User Action: Delete one of the definitions and relink.
MULDEFLBL,

multiple definition of label

Facility: MACRO, VAX MACRO Assembler
Explanation: The same label is defined twice in the module.
User Action: Delete the second label definition or change one of the labels to
a different symbol name.
MULDEFPSC,

psect 'psect-name' multiply defined in module 'module-name' file
'filename'

Facility: LINK, Linker Utility
Explanation: A psect is defined more than once in a single object module.
User Action: Correct the source, recompile, and relink.
MULPRI,

multiple primary definition in statement n

Facility: FDL, Create/FDL Utility and FDL, Edit/FDL Utility
Explanation: You have specified the same primary attribute in more than one
place in the FDL file. The line number given is where the second definition
appears.
User Action: Delete one of the definitions.

2-27

Messages

MULPSC,

conflicting attributes for psect 'psect-name' in module 'module-name'
file 'filename'

Facility: LINK, Linker Utility
Explanation: The attributes for a psect were found to be different in
subsequent modules of the link.
User Action: Correct the source so that all instances of the same psect have
the same attributes.

MULSEC,

multiple secondary definition in statement n

Facility: FDL, Create/FDL Utility and FDL, Edit/FDL Utility
Explanation: You have specified the same secondary attribute in more than
one place in a primary. The line number is where the second definition
appears.
User Action: Delete one of the definitions.

MULSHRPCS,

psect 'string' defined in shareable image 'image name' is multiply
defined in shareable image 'image name'

Facility: LINK, Linker Utility
Explanation: A program section defining COMMON area (such as those used
in VAX BASIC, VAX PL/I, VAX FORTRAN, and VAX C) is defined in two
shareable images. The linker is not able to properly resolve references to it.
User Action: For further information on Shareable Images, refer to the
Linker Utility in the VMS Linker Utility Manual, which explains how to link
COMMON areas.

MUL TALLOC,

file ('file-id') 'filename' multiply allocated blocks VBN 'n' to 'n'
LBN 'n' to 'n', RVN 'n'

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the specified logical blocks on the
specified relative volume were allocated to more than one file. These blocks
are the specified virtual blocks of the specified file.
User Action: Examine all the multiply allocated blocks messages to determine
the files involved in each instance of multiple allocation. Then, without
allowing other file activity, perform the following functions:

2-28

•

Copy all but one file involved in each instance to a new version.

•

Delete the version of each file that is copied that contains the multiple
allocation. This action marks blocks free in the storage bit map that are
not, in fact, free blocks.

•

Reenter the Verify Utility command line with the /REPAIR qualifier to
correct the storage bit map.

•

Examine each file for corruption and reconstruct from backup media as
necessary.

Messages

MULTCHNG,

attribute cannot be specified twice

Facility: CDU, Command Definition Utility
Explanation: You specified multiple syntax for a single qualifier.
User Action: Include one syntax reference for each qualifier.

MULTECO,

multiple eco levels ('nn' and 'nn') set for one patch

Facility: PATCH, Patch Utility
Explanation: You attempted to define a second ECO level before setting the
first ECO level.
User Action: To set the first ECO level, enter the PATCH Utility command
UPDATE.

MULTEXTHDR,

file ('file-id') 'filename' multiply allocated extension file header

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the specified extension file header
is in the extension header chain of more than one file.
User Action: The damage can be repaired by copying the volume to fresh
media or by copying all the files to new versions and then deleting the
original versions. Examine each file for corruption and reconstruct from
backup media as necessary.

MUL TFR,

multiply defined transfer address in module 'module-name' file
'filename'

Facility: LINK, Linker Utility
Explanation: More than one object module contains a strong transfer address.
User Action: Delete all but one of the transfer addresses.

MULTIDEF,

parameter/localjconstant 'name' multiply defined

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The parameter, local, or constant is defined more than once.
User Action: Rename the parameter, local, or constant so that it has a unique
name.

MULTIPLENAMES,

there is more than one name matching, all are returned

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The built-in procedure EXP AND_NAME has found more than
one name matching the given string and has returned a string of concatenated
names that match.
User Action: None.

2-29

Messages

MUL TISELECT, multiple identical CASE selectors
Facility: VAXTPU, VAX Text Processing Utility
.Explanation: Multiple identical selectors were specified in a single CASE
statement or error condition handler.
User Action: Specify a selector only once.

MUL TOPR,

multiple successive operators in expression

Facility: PATCH, Patch Utility and DEBUG, VMS Debugger
Explanation: You entered an expression containing adjacent operators.
User Action: Use angle brackets or parentheses, depending on the current
language, to separate the operators or enter a valid expression.

MUL TRMS,

multiple RMS vectors specified

Facility: SYSTEM, VMS System Services
Explanation: This severe error message is associated with a status code
returned from a system service request. Multiple VMS RMS vectors have
been specified for privileged shareable images.
User Action: Only one VMS RMS vector can be specified for an executable
image. Remove the vector associated with the problem and relink.

MUSTBECONST,

expression must be a compile-time constant

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The compiler requires a compile-time-constant-expression, and
the expression used does not meet these criteria.
User Action: Evaluate and correct the expression.

MUSTBEONE,

string must be 1 character long

Facility: VAXTPU, VAX Text Processing Utility
Explanation: A keyname must be one character only.
User Action: Enter the string again using a one-character keyname.

MUSTCLOSEFL,

must close file

Facility: SYSTEM, VMS System Services
Explanation: No more operations can be performed on a file, for example,
because the position on a magnetic tape is lost. The file must be closed before
processing can continue.
User Action: Retry the operation; take corrective action based on previously
reported errors.

MVABORTED,

'date-time', Mount verification aborted for device 'device-name'

Facility: OPCOM, Operator Communication
Explanation: The mount verification was aborted for some reason, possibly
because the volume was compromised.
User Action: Dismount and remount the volume.

2-30

Messages

MVCOMPLETE,

'date-time', Mount verification completed for device 'devicename'

Facility: OPCOM, Operator Communication
Explanation: Mount verification has successfully completed.
User Action: None.
NAFADDERR,

unable to add record to NETPROXY.DAT

Facility: AUTHORIZE, Authorize Utility
Explanation: The record you specified could not be added to the network
user authorization file (NETPROXY.DAT). This message should be
accompanied by a VMS RMS message that identifies the specific reason for
the error. For example, this error occurs if you try to add a record authorizing
a remote user to access more than one local account. Each user at a remote
node is allowed to access the files of only one user on the local node.
User Action: If possible, correct the condition identified by the VMS RMS
message and reenter your command. Otherwise, examine the network user
authorization file to determine why the record could not be added. You can
display the contents of the file by using the AUTHORIZE command
SHOW /PROXY. You can write the contents of NETPROXY.DAT to a listing
file by using the AUTHORIZE command LIST/PROXY. If you want to delete
a current record from NETPROXY.DAT in order to add a new record, use the
AUTHORIZE command REMOVE/PROXY.
NAFAEX,

NETPROXY.DAT already exists

Facility: AUTHORIZE, Authorize Utility
Explanation: A network user authorization file (NETPROXY.DAT) already
exists for the local node.
User Action: If you want to create a new network user authorization file,
either delete or rename the current one (if you have sufficient privilege
to do so). Once the current file has been deleted or renamed, reenter the
AUTHORIZE command CREATE/PROXY. Note that you must have sufficient
privilege to create a new file.
NAFCONERR,

connect error on NETPROXY.DAT

Facility: AUTHORIZE, Authorize Utility
Explanation: Connect error on to network user authorization file
(NETPROXY.DAT).
User Action: Take corrective action based on the accompanying messages.
NAFCREERR,

unable to create NETPROXY.DAT

Facility: AUTHORIZE, Authorize Utility
Explanation: A network user authorization file (NETPROXY.DAT) could not
be created. This message should be accompanied by a VMS RMS message
that identifies the specific reason why the file could not be created. For
example, this error occurs if you do not have sufficient privilege to create the
file.
User Action: Correct the condition identified by the RMS message and
reenter your command.

2-31

Messages

NAFDNE,

NETPROXY.DAT does not exist

Facility: AUTHORIZE, Authorize Utility
Explanation: A network user authorization file (NETPROXY.DAT) does not
exist on the local node.
User Action: If you have sufficient privilege, use the AUTHORIZE command
CREATE/PROXY to create a network user authorization file. Then you can
add records to the file by using the AUTHORIZE command ADD /PROXY.

NAFDONEMSG,

network authorization file modified

Facility: AUTHORIZE, Authorize Utility
Explanation: The network user authorization file (NETPROXY.DAT) has
been modified to reflect the change directed by your command.
User Action: None.

NAFNOMODS,

no modifications made to network authorization file

Facility: AUTHORIZE, Authorize Utility
Explanation: No modifications have been made to the network user
authorization file (NETPROXY.DAT).
User Action: None.

NAFUAEERR,

entry already exists in NETPROXY.DAT

Facility: AUTHORIZE, Authorize Utility
Explanation: The record you have tried to add to the network user
authorization file is already in the file; it has not been duplicated.
User Action: None.

NAM, invalid NAM block or NAM block not accessible
Facility: RMS, VMS Record Management Services
Explanation: The VMS RMS NAM block is not in the correct format, or it is
not in an area of memory that can be written by the caller.
User Action: Verify that the call to the VMS RMS service is coded correctly
and that the NAM block was not modified during execution of the program.

NAMETOOBIG,

user name too long

Facility: AUTHORIZE, Authorize Utility
Explanation: The user name you specified is longer than 12 characters.
User Action: Enter a user name no longer than 12 characters.

2-32

Messages

NAOFIL,

unable to open SYSUAF.DAF

Facility: AUTHORIZE, Authorize Utility
Explanation: The system user authorization file cannot be opened. This error
can occur if the file is not located in the current default directory, or if you
do not have sufficient privilege to access the file. This message should be
accompanied by a VMS RMS message specifying the reason why the file
cannot be opened.
User Action: If the file could not be found, set your default directory to
SYS$SYSTEM and then reenter your command. If you do not have sufficient
privilege to access the file, there is nothing you can do unless your system
manager can grant you the necessary privilege.
NAONAF,

unable to open NETPROXY.DAT

Facility: AUTHORIZE, Authorize Utility
Explanation: The network user authorization file (NETPROXY.DAT) could
not be opened. This message should be accompanied by a VMS RMS
message that identifies the specific reason for the error. Possible reasons
are insufficient privilege, file protection violation, or location of the file in the
wrong directory.
User Action: If you do not have sufficient privilege to open
NETPROXY.DAT, there is nothing you can do except to ask a privileged
user, such as your system manager, to access the file for you. If you do have
sufficient privilege, make sure the file is located in the proper directory and is
not protected against read or write access. Then reenter your command.
NARG,

wrong number of arguments

Facility: CONVERT, Convert Utility
Explanation: You specified an incorrect number of arguments in a call to
CONV$PASSJILES, CONV$PASS_OPTIONS, or CONV$CONVERT.
User Action: Refer to the VMS System Services Reference Manual for details
about calling these routines.
NCBFAIL,

undefined object on local node

Facility: MOM, Maintenance Operation Module
Explanation: An error has been detected in a Network Control Block. This is
a program logic error and should be reported.
User Action: Submit a Software Performance Report.
NCS,

no corresponding SAVE for attempted RESTORE
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: You have specified more .RESTORE commands than .SAVE
commands.
User Action: Specify the correct number of .RESTORE commands.

2-33

Messages

NEEDBOTH,

no authorization file-need both a password and a group number

Facility: CAF, Cluster Authorization File Service
Explanation: You specified an invalid group number with the
CONFIGURATION SET CLUSTER_AUTHORIZATION command.
User Action: Reenter the command with a numeric group number between 1
and 65535.

NEEDFILENAME,

type file name or just RETURN to delete buffer 'buffer-name'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: You modified a writable buffer, but there is no file name
associated with the buffer.
User Action: Enter a file name if you want the contents of the buffer written
to a file. Otherwise, press the RETURN key.

NEEDMORE,

unexpected end of command line

Facility: DEBUG, VMS Debugger
Explanation: The command entered is not complete. A required part of the
command is omitted.
User Action: Reenter the complete command.

NEEDTERMS,

you must specify some word terminators for FILL

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The built-in procedure FILL requires you to supply characters
that determine where to break the lines being filled.
User Action: Specify a string that contains at least one word terminator that
you want the built-in procedure FILL to use.

NEEDTOASSIGN,

built-in call must return a value

Facility: VAXTPU, VAX Text Processing Utility
Explanation: This built-in procedure may only be used in situations where
its return value is used. The built-in procedure must be on the right-hand
side of an assignment statement.
User Action: You must use this built-in procedure as part of an assignment
statement or as part of an expression.

NEF,

not positioned to EOF on $PUT (sequential organization only)
Facility: RMS, VMS Record Management Services
Explanation: A VMS RMS $PUT request is attempted for a sequential file
that is not currently positioned at the end of the file.
User Action: Verify that the call to the VMS RMS service is programmed
correctly. Modify your program, if necessary, to detect and respond to the
condition.

2-34

Messages

NEGATED,

entity explicitly negated in command string

Facility: CLI, Command Language Interpreter (DCL)
Explanation: The specified qualifier or keyword is present in its negated form
(with NO).
User Action: None.
NEGSHBREF,

shared memory control block negative refcnt

negative string length

Facility: STR, String Manipulation Facility
Explanation: Successful completion except that a length parameter to a string
routine had a negative value. Lengths of strings must always be positive or
zero; zero is used.
User Action: Verify that all parameters containing string lengths do not
contain negative numbers.
NEGTIM,

a negative time is computed

Facility: LIB, Library Facility
Explanation: The computed time is less than the system zero date (17-NOV1858).
User Action: Examine each argument and the order which they are passed.
Debug and correct the problem.
NESTERROR,

nesting level exceeded

Facility: VAXTPU, VAX Text Processing Utility
Explanation: A nested CASE, LOOP, or IF statement exceeds the maximum
nesting level of 20.
User Action: Do not nest CASE, LOOP, or IF statements more than 20 levels
deep.
NESTLEVEL,

nesting level exceeded in macro 'macro-name' file 'library-name'

Facility: LIBRAR, LIBRARY Command
Explanation: This error message is generated by the DCL command
LIBRARY. The specified macro exceeded the nesting limit of 63.
User Action: Change the macro before inserting it into the library.

2-35

Messages

NET,

network operation failed at remote node; DAP code= xxxxxxxx

Facility: RMS, VMS Record Management Services
Explanation: The file system of the target node could not perform the
requested operation, and VMS RMS is unable to map the Data Access
Protocol status code into a more specific VMS RMS completion code. The
status value (STV) field of the FAB or RAB contains the DAP status code.
User Action: Consult the appropriate DECnet manual for the remote node to
interpret the status code and take corrective action.
NETASN,

failed to declare name to network

Facility: CNF, NI Configurator
Explanation: An error occurred when NICONFIG attempted to declare itself
to the network as a known object.
User Action: See the accompanying message to determine the appropriate
action.
NETASN,

unable to assign a channel to NET

Facility: EVL, Event Logger
Explanation: An EVL $ASSIGN system service failed to assign a channel to
the network.
User Action: Refer to the VMS System Services Reference Manual for the
meaning of this system service error, and correct the problem.
NETDAS,

error deassigning a channel to the device NET

Facility: EVL, Event Logger
Explanation: An error occurred when EVL attempted to deassign a channel
to break a link with the event receiver.
User Action: Refer to the VMS System Services Reference Manual for the
meaning of this system service error, and correct the problem.
NETDIS,

disconnect on remote terminal DECnet link

Facility: REM, Set Host Facility
Explanation: The remote terminal facility received a disconnect status from
DECnet.
User Action: Try again.

2-36

Messages

NETERR,

DECnet channel error on remote terminal link

Facility: REM, Set Host Facility
Explanation: A DECnet-VAX error on the remote terminal link caused the
connection to be broken. This message may be accompanied by another
message identifying the specific reason why the connection is broken. One
possible cause is an incorrect local node name or address. For instance, the
address of the local node (the node from which you entered your command)
may conflict with an address for another node in the remote node's network
configuration database.
User Action: Use the Network Control Program (NCP) to examine the status
of the remote node's database. The NCP command SHOW displays network
data, and the NCP command LOOP NODE tests data transmission to a
specified node.
NETFAIL,

network operation failed at remote node

Facility: RMS, VMS Record Management Services
Explanation: The requested operation could not be performed by the file
system at the remote node. The status value (STV) field contains a FAL status
code that describes the failure in the context of the remote system.
User Action: Take corrective action based on the accompanying message.
NETIO,

network communication error

Facility: NCP, Network Control Program
Explanation: A network error occurred. Information accompanying this
message explains the reason for this error.
User Action: The action required depends upon the accompanying error
message. When you enter the next command, NCP automatically creates a
new link to NML.
NETIOERR,

network I/O error

Facility: MAIL, Mail Utility
Explanation: An I/O error occurred while transmitting a MAIL message with
DECnet-VAX.
User Action: Take corrective action based on the accompanying message.
NETLSTMSG, listing file NETPROXY.LIS complete
Facility: AUTHORIZE, Authorize Utility
Explanation: The contents of the network user authorization file
(NETPROXY.DAT) have been written to the listing file named
NETPROXY.LIS.
User Action: None.

2-37

Messages

NETMBX,

link mailbox code

Facility: REM, Set Host Facility
Explanation: A remote terminal network link is broken for unexpected
reasons.
User Action: Refer to DECnet-VAX documentation for more information.

NETMBX,

NICONFIG requires NETMBX privilege

Facility: CNF, NI Configurator
Explanation: NICONFIG must run with NETMBX privilege.
User Action: Install NICONFIG with NETMBX privilege or run it from an
account with NETMBX privilege.

NETNOBUF,

NETACP-buffer allocation failure

NETNOSTATE,

NETACP-no state transition

NETRCVPKT,

NETACP-no receive If O packet

2-38

Messages

NETSYSSRV,

NETACP-unexpected system service failure

NETACP-transaction count zero

network

Facility: OPCOM, Operator Communication
Explanation: This message is issued when operator status is requested either
explicitly by the REPLY /STATUS command or implicitly as with the REPLY
/ENABLE command. It indicates that the operator's terminal is enabled for
"NETWORK" class operations.
User Action: None.
NEWCOMPFIL,

current component file

Facility: SYSMAN, Cluster System Management Utility
Explanation: The name of the current startup component database has been
changed to the file specification named. This is output when the /LOG
qualifier is specified with the STARTUP command SET DATABASE.
User Action: Verify that the named database is correct.
NEWFILES,

'nnn' files created

Facility: Shared by several facilities
Explanation: The command displays the number of new files successfully
created. This message is informational.
User Action: None.

2-39

Messages

NEWP AGE,

attempted to write into new page

Facility: PSM, Print Symbiont
Explanation: This status is returned by a print symbiont format routine
indicating the attempt to write into a new page.
User Action: None.

NEWQUEUE,

new system job queue file 'filespec' created

Facility: JBC, Job Controller
Explanation: The system created a new system job queue file.
User Action: This message is informational. Note, however, that any jobs
currently entered in the old queue file have been lost. They have not been
transferred to the newly created queue file.

NEWSAVSET,

now beginning save set 'save set'

Facility: BACKUP, Backup Utility
Explanation: This informational message indicates the beginning of a new
save set during a wildcard list or restore operation.
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.

NEXTVOL,

volume 'volume' mounted-operation continues

Facility: BACKUP, Backup Utility
Explanation: This is an informational message which indicates that the next
volume required for the BACKUP operation has been mounted.
User Action: None.

NIA,

negative indent attempted
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: You attempted to indent text to the left of the left margin limit
of zero.
User Action: Correct the indent or left margin setting.

2-40

Messages

NIC

another 'n' negative indents detected and accumulated. Now being
reported.
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: A specific number of negative indents (to the left of .LMO)
are detected and reported. These errors are triggered by DSR commands
.CHAPTER or .APPENDIX, or by the end-of-file. The count of errors is
cleared after each DSR command .CHAPTER and .APPENDIX, or after the
end-of-file.
User Action: Correct the indent or left margin setting.

NMF,

no more files found

Facility: RMS, VMS Record Management Services
Explanation: The directory or volume set does not contain any more files that
meet the file specification (wildcard operation). This status code is returned
on a VMS RMS $SEARCH or $REMOVE operation.
User A~tion: Modify the source program, if necessary, to detect and respond
to the condition.

NMLRSP, listener response-' text'
Facility: NCP, Network Control Program
Explanation: The previous message line shows the format of response
messages from the network management listener (NML). NML receives
network management commands (from the Network Control Program, for
instance) and performs local network management functions as well as
control and information functions that are requested by remote nodes. An
NML response message may be as many as three display lines. The first line
of an NML message contains the reason for the error (this will be shown in
the 'text' part of the line). The second line contains an entity code (if there is
a code present in the response). The third line contains additional error text
(if there is text in the response).
User Action: Take corrective action based on the first line of the message.

No definition
Facility: EDT, EDT Editor
Explanation: You have requested a SHOW KEY definition for an undefined
key.
User Action: Ensure that you specify a defined key when you request a
SHOW KEY definition.

No help available for that key
Facility: EDT, EDT Editor
Explanation: There is no information in the current EDT HELP file on the
use of the key you have pressed.
User Action: If you have another HELP file available on your system that
contains the information, use the SET HELP command to gain access to that
HELP file.

2-41

Messages

No more than 65,535 lines can be processed in a single command
Facility: EDT, EDT Editor
Explanation: You specified a range that exceeds 65,535 lines.
User Action: Reenter the command specifying a smaller range.
NO,

no
Facility: VAXTPU, VAX Text Processing Utility
Explanation: This is a prototype negative response.
User Action: None.

No output file name
Facility: EDT, EDT Editor
Explanation: You have used the EDT command EXIT without having
specified a file name, either in the EDT command EXIT or in the command
line.
User Action: Reenter the command specifying a file name or enter QUIT.
No output file written
Facility: EDT, EDT Editor
Explanation: You attempted to put text into an output file, but EDT cannot
handle the record format of that text.
User Action: You must change the record format of the file, if possible,
before editing it.
No Path-Block During Virtual Circuit Close,
Facility: VAXport, 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 to DIGITAL including
the error logs and the crash dumps from the local and remote systems.
No select range active
Facility: EDT, EDT Editor
Explanation: You did not create a select range prior to entering the EDT
command APPEND or CUT.
User Action: Create a select range (using the select key) before you enter the
command.
No such line
Facility: EDT, EDT Editor
Explanation: There are no original line numbers for the specified range.
User Action: Ensure that a specified range has line numbers.

2-42

Messages

NOACCESSW,

no write access to virtual address 'address-value'

Facility: DEBUG, VMS Debugger
Explanation: A DEPOSIT, SET BREAK, or SET TRACE command specified
the address 'address-value'. The debugger does not have write access to that
page. The debugger requires write access to be able to set up breakpoints and
tracepoints. You cannot do the requested operation without proper access.
User Action: None.
NOACCMAN,

account manipulation on alternate roots not supported.

Facility: VMSINSTAL, Install Procedures
Explanation: The product being installed to an alternate system root cannot
update the user authorization file (SYSUAF).
User Action: Do not attempt to update the user authorization file from an
alternate system root.
NOACCPTMSG,

remote node cannot accept this message format

Facility: MAIL, Mail Utility
Explanation: MAIL cannot send a message of this format to the specified
remote node.
User Action: Convert the message to text and send the message to the
remote recipient again.
NOACESS,

cannot access image section

Facility: PATCH, Patch Utility
Explanation: You specified an address contained in an image section that is
not within this image file.
User Action: Retry specifying an address contained in an image file.
NOACNT,

operation requires ACNT privilege

Facility: SYSTEM, VMS System Services
Explanation: A command or program requested a system function that
requires ACNT privilege; the current process does not have this privilege.
User Action: If the message is in response to a command entered
interactively, verify that you have not used a command or a qualifier for
a particular command that requires a specific privilege.
If the message occurs during the execution of a program, determine the

system service call that resulted in the error. Verify that you have not used
a service or an argument for a particular service that requires a user privilege
that you do not have.
In either case, correct the command or program so that you do not request
the privilege. If you determine that you need the privilege for an application,
contact your system manager to obtain the necessary privilege.

2-43

Messages

NOACPCHAN,

failure to assign ACP channel

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

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.

NOALLOC, ignoring /ALLOCATION, not valid for output volume
Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility ignored an /ALLOCATION qualifier,
which is not meaningful.
User Action: Leave the allocation off, it is not needed.

2-44

Messages

NOALLSPOOL,

operation requires ALLSPOOL privilege

Facility: SYSTEM, VMS System Services
Explanation: A command or program requested a system function that
requires ALLSPOOL privilege; the current process does not have this
privilege.
User Action: If the message is in response to a command entered
interactively, verify that you have not used a command or a qualifier for
a particular command that requires a specific user privilege.
If the message occurs during the execution of a program, determine the
system service call that resulted in the error. Verify that you have not used
a service or an argument for a particular service that requires a user privilege
that you do not have.

In either case, correct the command or program so that you do not request
the privileged function. If you determine that you need the privilege for an
application, contact your system manager to obtain the necessary privilege.
NOAL TPRI,

operation requires ALTPRI privilege

Facility: SYSTEM, VMS System Services
Explanation: A command or program requested a system function that
requires AL TPRI privilege; the current process does not have this privilege.
User Action: If the message is in response to a command entered
interactively, verify that you have not used a command or a qualifier for
a particular command that requires a specific user privilege.
If the message occurs during the execution of a program, determine the

system service call that resulted in the error. Verify that you have not used
a service or an argument for a particular service that requires a user privilege
that you do not have.
In either case, correct the command or program so that you do not request
the privileged function. If you determine that you need the privilege for an
application, contact your system manager to obtain the necessary privilege.
NOANGLE,

unmatched angle brackets in expression

Facility: PATCH, Patch Utility and DEBUG, VMS Debugger
Explanation: You entered an expression that has an unequal number of
right angle brackets to left angle brackets. Or the brackets are not correctly
positioned.
User Action: Make the number of right angle brackets equal to the number
of left angle brackets and ensure that the brackets are in the correct position.

NOANSWER,

no answer is detected on the phone line

Facility: DTK, DECtalk Facility
Explanation: The routine DTK$DIAL _PHONE was called to dial a phone
number and no one answered the call.
User Action: Try calling again later.

2-45

Messages

NOAQB,

ACP queue header not found

Facility: SYSTEM, VMS System Services
Explanation: When an ACP started, it is unable to locate its queue header.
This error is the result of running an ACP with the DCL command RUN.
User Action: ACPs can be started only with the DCL command MOUNT.
If this message results from a DCL command MOUNT, gather as much
information as possible and submit a Software Performance Report.
NOAQBACP,

no AQB for ACP

missing argument for option

Facility: AUTHORIZE, Authorize Utility
Explanation: You specified a qualifier without a required argument.
User Action: Reenter your command and include the required argument.
NO_ARGS,

missing arguments for substitution

Facility: SMG, Screen Management Facility
Explanation: You requested a capability that requires user arguments such as
row and column numbers. You failed to provide those arguments.
User Action: Check the number of arguments required by this capability and
correct your call to SMG$GET_TERM_DATA.
NOASSIGNMENT,

expression without assignment

Facility: VAXTPU, VAX Text Processing Utility
Explanation: You used an expression without a :=to assign it to a variable.
User Action: Add the appropriate assignment to the statement.
NOAUTOCNF,

autoconfigure all is inhibited

Facility: SYSGEN, System Generation Utility
Explanation: The SYSGEN parameter NOAUTOCONFG is set to one.
User Action: Set NOAUTOCONFG to zero and reenter the command.

2-46

Messages

NOAVAIL,

field 'field-name' not available in this report

Facility: SHOW CLUSTER, Show Cluster Utility
Explanation: The field name entered does not apply to the currently selected
report and therefore cannot be added to the report. The name is, however,
valid in a different report.
User Action: Select a different report.
NOBACKUP,

'string' data not copied, file marked NOBACKUP

Facility: BACKUP, Backup Utility
Explanation: A save operation is performed on a file marked NO BACKUP.
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 block data not found on volume

Facility: INIT, INITIALIZE Command
Explanation: No bad block information is recorded in the Software or
Manufacturer's Bad Block areas. You have a good disk.
User Action: None.
NOBADDATA, bad data block not found on 'device-name'
Facility: INIT, INITIALIZE Command and BACKUP, Backup Utility
Explanation: This is a warning message generated by either the DCL
command INITIALIZE or the Backup Utility; 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.
NOBADINFO, no bad block information available for 'device-name'
Facility: BAD, Bad Block Locator Utility
Explanation: A device that is not a last track device does not contain a bad
block file. The utility will create a new SDBSF in nonlast track format.
User Action: None.
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 bit map 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.

2-47

Messages

NOBRANCH, instruction requires branch-type operand
Facility: PATCH, Patch Utility and DEBUG, VMS Debugger
Explanation: You attempted to enter a branch-type instruction with an
invalid operand for a destination field. For example, PATCH does not accept
the following command: DEPOSIT /INSTRUCTION GO= 'BNEQ RO'. Or a
DEBUG command DEPOSIT specified a branch-type instruction that specified
an illegal addressing mode as the operand.
User Action: Reenter the command using a valid branch operand in the
destination field.

NOBREAKPOINT,

no breakpoint is active

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The attempted call is valid only after a breakpoint.
User Action: Only enter the call in response to a breakpoint.

NOBREAKS,

no breakpoints are set

Facility: DEBUG, VMS Debugger
Explanation: The SHOW BREAK command is entered and no breakpoints
were set.
User Action: None.

NOBUFPCKT,

required buffer packet not present

NOBUGCHK,

CPU 'CPU-ID' failed to service bugcheck request

Facility: SDA, System Dump Analyzer
Explanation: The CPU identified by 'CPU-ID' did not save its state when the
system failed. As a result, context information about this CPU is not available
in the dump file.
User Action: None.

2-48

Messages

NOBUGCHK,

operation requires BUGCHK privilege

Facility: SYSTEM, VMS System Services
Explanation: A command or program requested a system function that
requires BUGCHK privilege; the current process does not have this privilege.
User Action: If the message is in response to a command entered
interactively, verify that you have not used a command or a qualifier for
a particular command that requires a specific user privilege.
If the message occurs during the execution of a program, determine the

system service calls that resulted in the error. Verify that you have not used
a service or an argument for a particular service that requires a user privilege
that you do not have.
In either case, correct the command or program so that you do not request
the privileged function. If you determine that you need the privilege for an
application, contact your system manager to obtain the necessary privilege.
NOBVPVCB,

blocked volume virtual page not found in VCB

NOBYP ASS,

operation requires BYPASS privilege

Facility: SYSTEM, VMS System Services
Explanation: A command or program requested a system function that
requires BYPASS privilege; the current process does not have this privilege.
User Action: If the message is in response to a command entered
interactively, verify that you have not used a command or a qualifier for
a particular command that requires a specific user privilege.
If the message occurs during the execution of a program, determine the

system service call that resulted in the error. Verify that you have not used
a service or an argument for a particular service that requires a user privilege
that you do not have.
In either case, correct the command or program so that you do not request
the privileged function. If you determine that you need the privilege for an
application, contact your system manager to obtain the necessary privilege.

2-49

Messages

NOCACHE,

insufficient virtual memory to allocate a new cache

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The system does not have enough memory available to allocate
a new cache for your process.
User Action: First, delete unneeded strings, ranges, markers, windows, and
buffers, then reenter your command. If the error recurs, increase the value of
the SYSGEN parameter VIRTUALPAGECNT. If the available memory is still
insufficient for your editing environment, try to increase your account's page
file quota. Finally, if the error persists, ask your system manager to increase
available memory.
NOCALLS,

no active call frames

Facility: TRACE, Traceback Facility and DEBUG, VMS Debugger
Explanation: There are no call frames on the stack for traceback to display.
This message usually occurs when a user image issues a RET instruction that
returns control to the command interpreter or when the DEBUG command
SHOW CALLS is entered. This message is informational.
User Action: None.
NOCALLUSER,

could not find a routine for CALL _USER to invoke

Facility: VAXTPU, VAX Text Processing Utility
Explanation: You must specify a routine for this built-in procedure to invoke.
User Action: Provide a routine for CALL _USER to use.
NOCARRIAGE, ignoring /CARRIAGE_CONTROL, not valid for output volume
Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility ignored a /CARRIAGE-CONTROL
qualifier which could not be applied to the volume.
User Action: Leave the qualifier off for that volume type.
NOCCAT,

parameter concatenation not allowed-check use of plus ( +)

Facility: CLI, Command Language Interpreter (DCL)
Explanation: A command that accepts either only a single-input value for
a parameter or a list of input values separated by commas for a parameter
containing multiple values separated by plus signs ( + ).
User Action: Reenter the command with a single file specification. If
necessary, enter the command once for each file.
NO_CHADIS,

no change in virtual display

Facility: SMG, Screen Management Facility
Explanation: The requested number of columns to change is 0, so nothing in
the virtual display is changed.
User Action: None.

2-50

Messages

NOCLASS,

requested input file classes not found or are incompatible

Facility: MONITOR, Monitor Utility
Explanation: The MONITOR request has been terminated because none of
the requested MONITOR classes were present in a valid form in the specified
input recording file. This situation may result from having specified an
incorrect input file. Also, this situation could result from an attempt to play
back classes from a recording file generated by a newer version of MONITOR.
User Action: Reenter the MONITOR request, specifying only classes that are
contained in the input recording file. Specify the correct input file if it had
been incorrectly specified. If the set of classes contained in the input file is
unknown, request all classes; only those present in the input file will be used.
NOCLASSES,

no classes specified

Facility: MONITOR, Monitor Utility
Explanation: A MONITOR request is executed with the Monitor Utility
command, but no information is provided to identify which classes to
monitor.
User Action: Reenter the Monitor Utility command, specifying at least one
class name parameter.
NOCU,

no CU present to perform function

Facility: DEBUG, VMS Debugger
Explanation: No command line interpreter exists in the target process. You
cannot perform the attempted operation.
User Action: None.
NOCU,

no CU present to perform function

Facility: LIB, Library Facility
Explanation: The calling process did not have a CU to perform the function
or the CU did not support the request type.
User Action: Ensure that the calling process has a CU and that the CLI
supports the request type. (Note that an image run as a subprocess or
detached process does not have a CU.)
NOCLITABLE,

image 'image-name' is not a CLI table

Facility: CDU, Command Definition Utility
Explanation: The input tables have an invalid format. Either an invalid file
is entered or a valid file is entered but then became corrupted.
User Action: Do not use this file again with the SET command.

2-51

Messages

NOCLUDEV,

server not loaded, no cluster device

Facility: STACONFIG, Standalone Configure Process
Explanation: No port descriptor table was found on this node. Either there is
no CI or NI adapter on this node, or the port drivers corresponding to either
of the devices has not been loaded.
User Action: Make sure the node you are loading the server on is configured
so that it can participate in a VAXcluster. If it does not have either an
Ethernet or a CI adapter, the MSCP server cannot be loaded (set MSCP_
LOAD to a 0). If you have one of the above adapters, make sure the
VAXCLUSTER parameter is set to a nonzero value. If the node participates in
a Local Area VAXcluster, that NISCS_LOAD is set to 1.

NOCLUSTER,

server not loaded, SCS not available

Facility: STACONFIG, Standalone Configure Process
Explanation: The SYSGEN parameters for this system request that the MSCP
server be loaded, but none of the underlying SCS services are loaded. These
SCS services are necessary for the operation of the MSCP server.
User Action: Make sure that the VAXCLUSTER parameter is set to a nonzero
value, or change the MSCP_LOAD parameter to 0, so the server is not
loaded.

NOCMDMEM,

no command memory has been allocated

Facility: Shared by several facilities
Explanation: If returned from a DR32 support routine call, either command
memory is never allocated, or the DR32 transfer is complete and the memory
has been deallocated.
User Action: If the DR32 transfer has completed, this is an informational
message. If command memory is never allocated, make sure the XF$SETUP
support routine is called before trying to access command packets.

NOCMDPROC,

error opening captive command procedure-access denied

Facility: CU, Command Language Interpreter (DCL)
Explanation: When you attempted to log in, you were logged out
because you have a captive account and DCL received an error during
the login. For example, DCL could not find your LOGIN.COM file.
You may also have incorrect protection on the system's SYLOGIN file
(SYS$MANAGER:SYLOGIN.COM or /SYSTEM/EXEC logical). The system's
SYLOGIN file must be protected with at least WORLD:E access to the file and
the directory which contains it.
User Action: See your system manager.

2-52

Messages

NOCMEXEC,

operation requires CMEXEC privilege

Facility: SYSTEM, VMS System Services
Explanation: A command or program requested a system function that
requires CMEXEC privilege; the current process does not have this privilege.
User Action: If the message is in response to a command entered
interactively, verify that you have not used a command or a qualifier for
a particular command that requires a specific user privilege.
If the message occurs during the execution of a program, determine the

system service call that resulted in the error. Verify that you have not used
a service or an argument for a particular service that requires a user privilege
that you do not have.
In either case, correct the command or program so that you do not request
the privileged function. If you determine that you need the privilege for an
application, contact your system manager to obtain the necessary privilege.
NOCMK,

operation requires CMKRNL privilege

Facility: INSTALL, Install Utility
Explanation: You must have CMKRNL privilege to perform the requested
operation.
User Action: Exit INSTALL and use SET/PROC/PRIV=CMKRNL.

NOCMKRNL,

operation requires CMKRNL privilege

Facility: SYSTEM, VMS System Services and JBC, Job Controller
Explanation: A command or program requested a system function that
required CMKRNL privilege; the current process does not have this privilege.
User Action: If the message is in response to a command entered
interactively, verify that you have not used a command or a qualifier for
a particular command that requires a specific user privilege.
If the message occurs during the execution of a program, determine the

system service call that resulted in the error. Verify that you have not used
a service or an argument for a particular service that requires a user privilege
that you do not have.
In either case, correct the command or program so that you do not request
the privileged function. If you determine that you need the privilege for an
application, contact your system manager to obtain the necessary privilege.
NOCOMD,

no command on line-reenter with alphabetic first character

Facility: CU, Command Language Interpreter (DCL)
Explanation: A command begins with a nonalphabetic character.
User Action: If you entered a symbol name, verify that the symbol is defined
by using the DCL command SHOW SYMBOL, and reenter the command.
If the error occurred in a command procedure, verify the syntax of the

command lines and check for continued lines.

2-53

Messages

NOCOMMSTLEV,

input files do not have a common file structure level

Facility: MONITOR, Monitor Utility
Explanation: A list of files is specified for the /INPUT qualifier, but the
files had different MONITOR file structure levels, that is, they were created
by different versions of the Monitor Utility. A multifile summary may be
generated only when all the input files have the same file structure level. The
file structure level is stored in the MONITOR file header record, and may be
examined by using the DUMP utility.
User Action: Reenter the MONITOR request specifying an input file list
consisting of files that have the same file structure level.

NOCONNECT,

unable to connect to remote node 'node-name'

Facility: MONITOR, Monitor Utility
Explanation: The network could not connect to a remote node. This error
can occur if the specified node is unreachable when the CLUSTER class is
requested.
User Action: Determine whether the network is working properly on the
remote node. When the node is accessible, reenter the MONITOR command.

NOCONSOLE,

unknown CPU type number. Console volume cannot be
remounted.

Facility: VMSINSTAL, Install Procedures
Explanation: While attempting to remount the console medium, VMSINSTAL
could not determine your CPU type.
User Action: Contact your DIGITAL field service representative.

NOCONTIG,

bootfile not contiguous

Facility: VAXCLUSTER, VAXcluster Facility
Explanation: The file SYSBOOT.EXE is noncontiguous on the system disk.
The primitive bootstrap file system cannot read a noncontiguous file.
User Action: Rebuild the system disk to obtain enough contiguous free space
for SYSBOOT.

NOCONTIG,

noncontiguous image file being written

Facility: PATCH, Patch Utility
Explanation: The output file is a noncontiguous image file.
User Action: If you require a contiguous output file after you exit from
PATCH, use the DCL command in the following format:
COPY /CONTIGUOUS input-filespec output-filespec

NOCONVBOOT,

not authorized to perform conversational bootstrap

Facility: VAXCLUSTER, VAXcluster Facility
Explanation: Conversational bootstrap operations are not authorized for the
satellite node.
User Action: Consult the cluster manager.

2-54

Messages

NOCOPBAD,

cannot create .BAD file with wildcard names

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility could not create an RT-11 file with a file
type of .BAD because the input or output file names contained a wildcard.
User Action: Since the file type of .BAD is given special meaning by RT-11,
you probably want to choose a different file type for your file.
NOCOPBADDEL,

cannot delete existing .BAD file

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility could not copy an RT-11 file with a file
type of .BAD because the same file already exists on the volume.
User Action: Since the file type of .BAD is given special meaning by RT-11,
you probably want to choose a different file type for your file.
NOCOPDUP,

already copied file with same output name in this command

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility did not copy the listed file, because the
current command had already copied a file with the same output name.
User Action: Copy the file with another command, specifying an output
name which does not conflict with other files.
NOCOPLOCK,

cannot create files, volume volume is write-locked

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility could not perform a COPY command
because the output volume is write-locked.
User Action: Remount the output volume with write access, then reenter the
command.
NOCOPNODEL,

file already exists and /NODELETE requested

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility did not perform a COPY command. The
output file already existed and the /NODELETE qualifier is specified.
User Action: This message means that the /NODELETE qualifier actually
prevented a file from being deleted. It normally requires no response. If it
is desired to delete the original file and perform the copy, then reenter the
command without the /NODELETE qualifier.
NOCOPPROT,

file with same name is protected against modification

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility did not perform a COPY command. The
output file already existed and is protected from being deleted.
User Action: If it is desired to perform the copy, use the RENAME
/NOPROTECT command to remove the protection from the output file.

2-55

Messages

NOCOPSAMDEV,

illegal wildcard copy to same device

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility refused to perform a copy operation, due
to illegal use of wildcards or the /REPLACE qualifier.
User Action: EXCHANGE will not perform a wildcard copy from a foreign
volume back to the same foreign volume, since it can be difficult or impossible
to prevent a loop with files being copied more than once. It also will not
perform a /REPLACE copy of a file to itself, since that implies deleting the
file before the copy.
NOCOPSYSDEL,

cannot delete existing .SYS file without /SYSTEM

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility refused to copy a file with file type of
.SYS because an existing file of the same name would have to be deleted.
User Action: If you want to delete the old file and copy the new file, then
reenter the copy command with the /SYSTEM qualifier.
NOCOPYBOOT,

unable to copy boot information

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility encountered a problem while attempting
a COPY /BOOT operation.
User Action: This command will be followed by a second message giving the
specific condition found. Take corrective action based on the contents of the
second message.
NOCOPYBUF,

cannot COPY a buffer to itself

Facility: VAXTPU, VAX Text Processing Utility
Explanation: You attempted to copy a buffer while you were working in the
buffer. You cannot copy a buffer to itself; doing so would cause an infinite
loop.
User Action: Move to another buffer before starting the copy operation.
NOCPUS,

requested cpu[s] are not active

Facility: MONITOR, Monitor Utility
Explanation: The CPUs specified with the /CPU qualifier are not active on
the requested node.
User Action: Correct the CPU specification and reenter the MONITOR
command.

2-56

Messages

NOCSP,

no SMI thread in remote Cluster Server Process

Facility: SMI, System Management Intergator/Server
Explanation: A remote SYSMAN command could not be delivered to the
SMISERVER process in the indicated node for one of the following reasons:
•

The remote system is running a version of VMS lower than Version 5.0.

•

The CLUSTER_SERVER process on the remote system stopped, aborted,
or is not yet started during system initialization.

User Action: Determine the reason for the failure and correct the problem.
NOCURLOC,

current location not defined

Facility: DEBUG, VMS Debugger
Explanation: '.' is not currently defined.
User Action: Do not reference '.'until an EXAMINE or EVALUATE
/ADDRESS command has been performed.
NOCURRENTBUF,

no buffer has been selected as default

Facility: VAXTPU, VAX Text Processing Utility
Explanation: You tried to use a built-in procedure to modify the current
buffer when you were not working in a buffer. This error occurs when no
buffers have been created, because there is no buffer to serve as the default
buffer.
User Action: Establish a current buffer. To do this, either move to a buffer
or associate a buffer with a window and map the window to the screen.
NOD,

error in node name

Facility: RMS, VMS Record Management Services
Explanation: The node name portion of a file specification is not in the
correct syntax.
User Action: Check the syntax of the node name specification and retry the
operation. Verify that the call to the VMS RMS service is coded correctly.
NODECODE,

cannot decode instruction

Facility: PATCH, Patch Utility and DEBUG, VMS Debugger
Explanation: Either the Patch Utility or the VMS Debugger encountered an
undefined opcode or illegal addressing mode while attempting to decode the
instruction. This can be caused by specifying an address that is in the middle
of an instruction or is in a data area.
User Action: Correct the location and reenter.
NODEDISABLED,

node is not currently enable for file

Facility: SMI, System Management Intergator/Server
Explanation: A STARTUP DISABLE action tried to disable a component file
on a node that the component file is not enabled on.
User Action: None.

2-57

Messages

NODEENABLED,

node is already enabled for file

Facility: SMI, System Management Intergator/Server
Explanation: A STARTUP ENABLE action tried to enable a component file
on a node that the component file is already enabled on.
User Action: None.

NODEFINITION,

key 'key-name' currently has no definition

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The key you pressed is not defined.
User Action: Use the built-in procedure DEFINE_KEY if you want to define
a function for the key.

NODEFPWD,

Warning: DEFAULT password change has no effect on added
records

Facility: AUTHORIZE, Authorize Utility
Explanation: The DEFAULT password for added records is always USER,
regardless of the DEFAULT record specified.
User Action: None.

NODEINIERR,

error during node initialization

Facility: MONITOR, Monitor Utility
Explanation: An error occurred during the initialization of a node. This error
can occur if an attempted connection to a remote node fails.
User Action: Determine whether the network is working properly on the
remote node. When the node can be successfully initialized, reenter the
MONITOR command.

NODELIMTR,

missing or invalid instruction operand delimiter

Facility: DEBUG, VMS Debugger
Explanation: A DEPOSIT command specified an invalid instruction operand
format.
User Action: Reenter the command with valid operands.

NODELLOCK,

file 'filename' not deleted, volume is write-locked

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility could not perform a DELETE command
because the output volume is write-locked.
User Action: Remount the output volume with write access, then reenter the
command.

2-58

Messages

NODENOTAVAIL,

requested nodes are not available

Facility: MONITOR, Monitor Utility
Explanation: The remote nodes specified in a MONITOR request are not
currently accessible over the network. Therefore, they are not available for
data collection from the local node.
User Action: Determine why the remote nodes are not available. Reenter the
MONITOR command when they do become accessible from the local node.
NODENOTCLU,

node not currently in cluster

Facility: SYSMAN, Cluster System Management Utility
Explanation: During a STARTUP ENABLE action, a node that is not
currently in the cluster was specified.
User Action: Verify that node name is correct. If it is incorrect, reenter the
command.
NODENOTMEM,

node 'node-name' is not a member of this cluster

Facility: MONITOR, Monitor Utility
Explanation: The requested node is not a member of the VAXcluster
specified in the request. MONITOR can only collect data from nodes within a
VAXcluster.
User Action: Select nodes that are members of the requested VAXcluster and
reenter your command.
NODENOTPRES,

1 or more nodes requested do not exist in input file

Facility: MONITOR, Monitor Utility
Explanation: At least one of the nodes requested during a playback
command does not exist in the input file.
User Action: Enter the command without a node name specification to
determine which nodes are contained within the file. Then select the correct
nodes and reenter your command.
NODERR,

error returned from node "nnnnnn"

Facility: SYSMAN, Cluster System Management Utility
Explanation: A command returned an error on node "nnnnnn". The error
message follows. Execution will be attempted on the next node in the
environment.
User Action: Take action according to the accompanying error message.
NODESTQUE,

no such destination queue

Facility: SYSTEM, VMS System Services
Explanation: In a request to the symbiont manager, the specified destination
queue does not exist.
User Action: Reenter the command, specifying a valid destination queue.

2-59

Messages

NODETACH,

operation requires DETACH privilege

Facility: SY,STEM, VMS System Services
Explanation: A command or program requested a system function that
requires DETACH privilege; the current process does not have this privilege.
User Action: If the message is in response to a command entered
interactively, verify that you have not used a command or a qualifier for
a particular command that requires a specific user privilege.
If the message occurs during the execution of a program, determine the
system service call that resulted in the error. Verify that you have not used
a service or an argument for a particular service that requires a user privilege
that you do not have.

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.
NODEVAVL,

no device available

Facility: SYSTEM, VMS System Services
Explanation: You tried to allocate an unavailable device.
User Action: Wait until a device is available and retry allocation.
NODEVICE,

missing or incorrect device name in 'command-line'

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility did not find device name in a command
line.
User Action: Check the command for a misspelling or other error, and
reenter the command with a correct device name.
NODEXIT,

lost connection to node 'node-name'. Node removed!

Facility: MONITOR, Monitor Utility
Explanation: The connection to a remote node is broken. This error can
occur if the remote node shuts down.
User Action: Determine why the remote node is removed from the network.
When the remote node is accessible again, reenter the MONITOR command.

2-60

Messages

NODIAGNOSE,

operation requires DIAGNOSE privilege

Facility: SYSTEM, VMS System Services
Explanation: A command or program requested a system function that
requires DIAGNOSE privilege; the current process does not have this
privilege.
User Action: If the message is in response to a command entered
interactively, verify that you have not used a command or a qualifier for
a particular command that requires a specific user privilege.
If the message occurs during the execution of a program, determine the

system service call that resulted in the error. Verify that you have not used
a service or an argument for a particular service that requires a user privilege
that you do not have.
In either case, correct the command or program so that you do not request
the privileged function. If you determine that you need the privilege for an
application, contact your system manager to obtain the necessary privilege.
NODIATONE,

no dial tone is detected on the phone line

Facility: DTK, DECtalk Facility
Explanation: The routine DTK$DIAL_PHONE is called to dial a phone
number and no dial tone is detected on the phone line.
User Action: Correct the telephone line problem and call again.
NODIRLISM, no source directory list in effect for 'path-name'
Facility: DEBUG, VMS Debugger
Explanation: The command CANCEL SOURCE/MODULE='path-name'
failed because there is no source directory search list in effect for module
'path-name'.
User Action: This is an informational message. However, if the wrong
module was specified, the command should be reentered with the correct
name.
NODIRLIST,

no source directory list in effect

Facility: DEBUG, VMS Debugger
Explanation: The DEBUG command CANCEL SOURCE had no effect
because no source directory search list is currently in effect. This message is
informational.
User Action: None.
NODISKQUOTA,

no disk quota entry for this UIC

Facility: SYSTEM, VMS System Services
Explanation: The specified quota file entry does not exist.
User Action: Check the UIC given. Either add a quota file entry for it or use
another UIC.

2-61

Messages

NODSTQUE,

no such destination queue

Facility: JBC, Job Controller
Explanation: The specified destination queue does not exist.
User Action: None.

NODTOOBIG,

node name too long

Facility: AUTHORIZE, Authorize Utility
Explanation: VMS node names cannot exceed six characters. A node name
may consist of 1 to 6 alphanumeric characters; at least one character must be
alphabetic.
User Action: Check the node name and reenter your command with the
correct name.

NODUPEXC,

equal-key routine and no duplicates options cannot both be
specified

Facility: SORT, Sort/Merge Utility
Explanation: You specified both an equal-key routine and the SOR$M_
NODUPS option when only one or the other option is allowed.
User Action: Specify either the equal-key routine or the no duplicates option.

NOELEM,

no element found

Facility: STR, String Manipulation Facility
Explanation: The input string passed to STR$ELEMENT does not contain at
least the number of delimiters specified in the ELEMENT-NO item code.
User Action: Examine SRC_DESC and ELEMENT_NO and make
corrections.

NOENCODE,

cannot encode instruction 'instr'

Facility: PATCH, Patch Utility
Explanation: The instruction contained an illegal opcode or operand. The
branch destination may not be reachable from the location for which it is
destined.
User Action: Retry specifying a legal opcode or operand.

NOENCODE,

cannot encode instruction 'n'

Facility: PATCH, Patch Utility
Explanation: The instruction cannot be encoded. Possible causes include:
invalid addressing modes, invalid syntax, not enough operands, or too many
operands.
User Action: Determine the cause of the problem.

2-62

Messages

NOEND,

string beginning with 'string_value' is missing end delimiter 'delimiter_
character'

Facility: DEBUG, VMS Debugger
Explanation: A DEPOSIT command specified an ASCII string or
INSTRUCTION string beginning with characters 'string_value' that do
not have a terminating apostrophe.
User Action: Reenter the command with characters containing a terminating
apostrophe.
NOENDOFLINE,

returning a range of text with no end of line

Facility: VAXTPU, VAX Text Processing Utility
Explanation: VAXTPU is returning a range of text without an end-of-line
indicator.
User Action: None.
NOEOBSTR,

cannot return a string at end of buffer

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The built-in procedures CURRENT_LINE and CURRENT_
CHARACTER return the null string if you are positioned at the end of the
buffer (EOB). This warning distinguishes this case from that of end of line.
User Action: Move back from the end of the buffer.
NOEOM,

module 1module-name' does not contain end of module records

module 1module-name' is not terminated with EOM record in 1libraryname1

Facility: LIBRAR, LIBRARY Command
Explanation: This error message is generated by the DCL command
LIBRARY. The module you attempted to insert into the library does not
contain a legal EOM record.
User Action: Recompile the object module.
NOEOM,

no end of module record found in module 1module-name 1 file 1filename'

Facility: LINK, Linker Utility
Explanation: A module did not contain an end-of-module record.
User Action: Submit a Software Performance Report. Include the language
compiler in the report.

2-63

Messages

NOEPM,

undefined entry mask of symbol 'symbol-name' referenced in module
'module-name' file 'filename'

Facility: LINK, Linker Utility
Explanation: An entry mask of an undefined symbol is referenced with the
MACRO .MASK directive.
User Action: Either define the entry point or delete the reference to it.
NOEXQUOTA,

operation requires EXQUOTA privilege

Facility: SYSTEM, VMS System Services
Explanation: A command or program requested a system function that
requires EXQUOTA privilege; the current process does not have this privilege.
User Action: If the message is in response to a command entered
interactively, verify that you have not used a command or a qualifier for
a particular command that requires a specific user privilege.
If the message occurs during the execution of a program, determine the
system service call that resulted in the error. Verify that you have not used
a service or an argument for a particular service that requires a user privilege
that you do not have.

'field-name' is not a field in this record

Facility: DEBUG, VMS Debugger
Explanation: An attempt was made to reference a field that is not defined in
the record.
User Action: Check the field specified to ensure that it is defined in the
record.
NOFILE,

no file found

Facility: SEARCH, SEARCH Command
Explanation: The DCL command SEARCH is unable to open any files in the
input file list. Therefore, no files were searched.
User Action: If files were incorrectly specified, reenter the command with
correct file specifications.
NOFILE,

[new] file 'filename' does not exist.

Facility: VMSINSTAL, Install Procedures
Explanation: VMSINSTAL cannot find an existing (or new) file with the
given name.
User Action: If you can determine and correct the problem, reinstall the
product. Otherwise, contact your DIGITAL field service representative.

2-64

Messages

NOFILEACCESS,

unable to access file filename

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The file you tried to open could not be accessed. The
accompanying VMS RMS error message explains why.
User Action: Follow the recovery procedure for the specified VMS RMS
message.
NOFILEID,

no file identification is specified

Facility: PSM, Print Symbiont
Explanation: This status is returned indicating no file identification number
is specified with this request. This error usually indicates a problem in the
creation of a batch log file.
User Action: Correct the problem in the batch command file and resubmit
the job.
NOFILEROUTINE,

no routine specified to perform FILE 1/0

Facility: VAXTPU, VAX Text Processing Utility
Explanation: This message is returned from the callable interface by
TPU$INITIALIZE. It indicates that a valid 1/0 routine is not specified.
User Action: Specify an 1/0 routine.
NOFILES,

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.
NOFILNAM,

no file specification found

Facility: LBR, Librarian Subroutine Package
Explanation: In the LBR$0PEN routine, the FNS argument is invalid or not
provided or the NAM block is not filled in.
User Action: Correct the problem before calling the routine.
NOFILPURG,

no files purged for filespec'

Facility: Shared by several facilities
Explanation: No files matching the given file specification were candidates
for purging.
User Action: None. The directory is already purged.
NOFORMLARG,

no formal argument for .IRP /.IRPC

Facility: MACRO, VAX MACRO Assembler
Explanation: There were no formal arguments in an .IRP or .IRPC directive.
User Action: Correct the syntax of the .IRP or .IRPC directive.

2-65

Messages

NOFREE,

no free storage available

Facility: PATCH, Patch Utility and DEBUG, VMS Debugger
Explanation: An internal PATCH error has occurred. Or no free storage is
available for the debugger to execute the command.
User Action: If this message is generated by the Patch Utility, submit a
Software Performance Report. If this message is generated by the debugger,
increase free storage by using the CANCEL MODULE command and then
reenter the command.

NOGBL,

some or all global symbols not accessible

Facility: PATCH, Patch Utility
Explanation: When you initialized PATCH, either no global symbol
information is available to PATCH or the symbol table is not large enough to
incorporate all the global symbol information.
User Action: To ensure that global symbol information is passed to the
PATCH utility, reassemble or recompile and link your program including the
debug or traceback facility.

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.

NOGLOBALS,

some or all global symbols not accessible

Facility: DEBUG, VMS Debugger
Explanation: The image is linked with the /NODEBUG qualifier, and there
are no global symbols in the symbol table.
User Action: Relink the image with the /DEBUG qualifier.

NOGROUP,

operation requires GROUP privilege

Facility: SYSTEM, VMS System Services
Explanation: A command or program requested a system function that
requires GROUP privilege; the current process does not have this privilege.
User Action: If the message is in response to a command entered
interactively, verify that you have not used a command or a qualifier for
a particular command that requires a specific user privilege.
If the message occurs during the execution of a program, determine the

system service call that resulted in the error. Verify that you have not used
a service or an argument for a particular service that requires a user privilege
that you do not have.
In either case, correct the command or program so that you do not request
the privileged function. If you determine that you need the privilege for an
application, contact your system manager to obtain the necessary privilege.

2-66

Messages

NOGRPNAM,

operation requires GRPNAM privilege

Facility: SYSTEM, VMS System Services
Explanation: A command or program requested a system function that
requires GRPNAM privilege; the current process does not have this privilege.
User Action: If the message is in response to a command entered
interactively, verify that you have not used a command or a qualifier for
a particular command that requires a specific user privilege.
If the message occurs during the execution of a program, determine the
system service call that resulted in the error. Verify that you have not used
a service or an argument for a particular service that requires a user privilege
that you do not have.

wildcard group numbers not allowed

Facility: AUTHORIZE, Authorize Utility
Explanation: Wildcard characters are not allowed in the UIC group number
field for the command you entered.
User Action: Reenter your command with a specific UIC group number
instead of a wild card character.
NOGSDREF,

no GSD reference to shareable image symbol 'symbol' found in
module 'module-name' file 'filename'

Facility: LINK, Linker Utility
Explanation: A reference to a symbol in a shareable image is found in Pass
2 of the linking operation; yet, there is not a GSD reference to the symbol
found in Pass 1.
User Action: This is a compiler error. Submit a Software Performance
Report. Include the appropriate compiler in the report.
NOHANDLER,

no condition handler found

Facility: SYSTEM, VMS System Services
Explanation: A request to delete an exit handler returned a warning code
indicating that the specified handler does not exist.
User Action: Check for a programming error.

2-67

Messages

NOHDJMT,

no Head-JMT in JMT list (journaling)

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.
User Action: None. The known file entry is successfully created.
NOHIDDEN,

cannot modify hidden ACEs

Facility: SET, SET Facility
Explanation: The ACE currently being added or replaced has the HIDDEN
option set.
User Action: Remove the HIDDEN option before attempting to add the ACE.
NOHISTORY,

library has no update history

Facility: LBR, Librarian Subroutine Package
Explanation: This library is created with the maximum number of history
records equal to zero.
User Action: None.
NOHLPLIBS,

no default help libraries can be opened

Facility: LBR, Librarian Subroutine Package
Explanation: You called LBR$0UTPUT_HELP without passing the name of
a help library, and you have no default libraries defined.
User Action: Either pass in the name of the library or define HLP$LIBRARY
to be a library name.
NOHLPTXT,

help text not found

Facility: LBR, Librarian Subroutine Package
Explanation: There is no help text associated with the specified key path.
User Action: Check that the help module is properly formatted.

2-68

Messages

NOHLPTXT,

no level 1 help text found in 'input filespec'

Facility: LIBRAR, LIBRARY Command
Explanation: The specified input file does not contain a properly formatted
help file.
User Action: Reformat the help file before reentering the command line.

NOHOME,

volume does not contain a valid home block

Facility: SET, SET Facility
Explanation: You attempted to perform a SET VOLUME on a disk that is not
Files-11.
User Action: None. You cannot perform a SET VOLUME on a disk that is
not Files-11.

NOHOMEBLK,

Files-11 home block not found on volume

Facility: SYSTEM, VMS System Services
Explanation: Either the volume is not a Files-11 volume or it is completely
unreadable.
User Action: Verify that the correct volume is mounted. Mount the volume
as foreign.

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.

NOIDNAM,

no ID name is specified

Facility: AUTHORIZE, Authorize Utility
Explanation: The command you entered requires that you include an
identifier name.
User Action: Check the VMS Authorize Utility Manual for the syntax rules
regarding identifier names for the command you want to use. Then reenter
the command including an identifier name.

NOIMGFIL,

image file not created

Facility: LINK, Linker Utility
Explanation: This secondary message is issued when the linker encounters
an error that prevents the generation of an image file.
User Action: None.

2-69

Messages

NOINDEX,

no index information in file 'filename'

Facility: DSR, DIGITAL Standard Runoff
Explanation: The indicated file does not contain any index entries.
User Action: Check the corresponding input file to be sure there are index
entries.
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.
NOINIT,

PPL$INITIALIZE is not called

Facility: PPL, Parallel Processing Facility
Explanation: PPL$INITIALIZE must be called before this routine.
User Action: Recode your program to ensure that calls are in the correct
order. PPL$INITIALIZE is performed automatically for most calls, but not for
those calls that require the prior creation of an element.
NOINPFILES,

no usable input files

Facility: MONITOR, Monitor Utility
Explanation: A multifile summary is requested but none of the files specified
in the /INPUT list could be used.
User Action: Examine the IGNFIL error messages preceding this message.
Each one identifies a file which is ignored, and provides an accompanying
message explaining why the file could not be used. Reenter the MONITOR
request specifying at least one input file which can be used. A typical
situation where input files are ignored is one where the /BEGINNING
and/or /ENDING qualifiers are specified, and the ignored files do not contain
data in the range of the requested time.
NOINPTAB,

new tables file cannot be written unless input tables supplied

Facility: CDU, Command Definition Utility
Explanation: You tried to write empty tables to your process. Either you
did not provide input tables or you specified the /TABLES qualifier in the
command string and there were no CLD files.
User Action: Include the name of the input tables in the command string.
Or if there are no CLD files, do not specify the /TABLES qualifier in the
command string.

2-70

Messages

NOINSTRAN, cannot translate instruction
Facility: SDA, System Dump Analyzer
Explanation: SDA cannot translate the specified instruction into VAX
MACRO instruction format.
User Action: None.

NOINSTRAN, cannot translate opcode at location 'address-value'
Facility: DEBUG, VMS Debugger
Explanation: The address specified in the EXAMINE command is not the
beginning of a valid VAX instruction. This can be caused by specifying an
address that is in the middle of an instruction or by an address that is in a
data area.
User Action: Specify an address that contains a valid instruction.

NOINTABLE,

an output table image must be created using an input table

Facility: CDU, Command Definition Utility
Explanation: You tried to write empty tables to your process. Either you
did not provide input tables or you specified the /TABLES qualifier in the
command string and there were no CLD files.
User Action: Include the name of the input tables in the command string.
Or, if there are no CLD files, do not specify the /TABLES qualifier in the
command string.

NOIOCHAN,

cannot piggyback I/O channel with PUTMSG

Facility: TRACE, Traceback Facility
Explanation: This message is associated with a traceback internal consistency
check.
User Action: Submit a Software Performance Report.

NOIOCHAN,

no If O channel available

Facility: SYSTEM, VMS System Services
Explanation: The process exceeds the number of I/O channels that can be
assigned at one time.
User Action: Deassign another channel, or close a file and retry the
operation. Check for a program error that fails to deassign channels or
close files. Also check the SYSGEN parameter CHANNELCNT to see if it is
high enough.

NOJOBCTX,

no job context

Facility: JBC, Job Controller
Explanation: A call was made to the $GETQUI system service requesting the
$QUI_DISPLAY_FILE function without first establishing a job context for this
call.
User Action: Modify the application to first establish a job context by calling
the $GETQUI system service in wildcard mode using either the
QUI$_DISPLAY_JOB or the QUI$_DISPLAY_ENTRY function codes.

2-71

Messages

NOJOBID,

job 'nnn' not found in 'queue-name' queue

Facility: Shared by several facilities
Explanation: A request to modify or delete a job failed because the job does
not exist. The message identifies the job by job name or job identification
number, depending on the command specification.
User Action: Verify that the job identification number or job name is entered
correctly. If it is not, reenter the command with the correct job identification
number or job name. If the job identification number or job name is correct,
this message indicates that the job is no longer in the queue; that is, the job
has already been processed or is currently being processed.
NOJOBNAME,

job 'job-name' not found in 'queue-name' queue

editing session is not being journaled

Facility: VAXTPU, VAX Text Processing Utility
Explanation: VAXTPU is invoked without opening a journal file.
User Action: If you want to open a journal file, use the built-in procedure
JOURNAL_OPEN.
NOKEY,

no such key

Facility: CONVERT, Convert Utility
Explanation: You have specified a legal but nonexistent value with /KEY.
For example, if the file has two keys, 0 and 1, and you specify /KEY=2, you
will receive this error message.
User Action: Specify a valid number with /KEY.
NOKEYMAP,

attempt to access an undefined key map 'key-map-name'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: You are referring to a key map that has not yet been created.
User Action: Enter the built-in procedure SHOW (KEY_MAPS) on the
command line to obtain the names of vaHd key maps.

2-72

Messages

NOKEYMAPLIST,

attempt to access an undefined key-map list 1key-map-listname1

Facility: VAXTPU, VAX Text Processing Utility
Explanation: You are referring to a key-map list that has not yet been
created.
User Action: Enter the built-in procedure SHOW (KEY_MAPS_LISTS) on
the command line for a list of valid key-map list names.
NOKEYW,

qualifier name is missing-append the name to the slash

Facility: CLI, Command Language Interpreter (DCL)
Explanation: A slash character ( /) is present on a command but is not
followed by a qualifier keyword name.
User Action: Reenter the command specifying the qualifier or removing the
slash.
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.
NOLASTVAL,

last value is not defined

Facility: DEBUG, VMS Debugger
1

Explanation: \ is not currently defined.
User Action: Do not reference
, has been performed.
NOLBLS,

1
\

until a DEPOSIT or EVALUATE command

label ignored-use only within command procedures

Facility: CLI, Command Language Interpreter (DCL)
Explanation: This message is output if you try to put a label on a command
line that is supplied to DCL interactively. Labels are not appropriate in
this context and are ignored. Any command that follows the label will be
executed.
User Action: None.
NOLCL,

image does not contain local symbols

Facility: PATCH, Patch Utility
Explanation: When you initialized PATCH, no local symbol information is
available to PATCH.
User Action: To ensure that local symbol information is passed to PATCH,
reassemble or recompile and link your program including the DEBUG or
Traceback Facility.

2-73

Messages

NOLICENSE,

operation requires software license

Facility: SYSTEM, VMS System Services
Explanation: You are requesting a function that requires a software license.
This function cannot be done until the license kit is installed. (DECnet-VAX
is the only software license that is currently associated with this message.)
User Action: Buy the license and install the license kit.
NOLINK,

specified link has not been defined.

Facility: LATCP, LAT Control Program
Explanation: The specified link is not defined, or a link name is required and
is not specified.
User Action: Ensure that the link exists on your service node and reenter the
command.
NOLINKS,

no slots in logical link vector

Facility: SYSTEM, VMS System Services
Explanation: The maximum number of allowable logical network links exists
and no more slots are available to establish another link.
User Action: Wait and retry the request later. If the problem persists, ask
the system manager to increase the allowed number of logical links. Or,
if you have SYSPRV, you could run the Network Control Program (NCP)
and change the number of maximum allowable links yourself. To increase
the number of allowable links, use the NCP command SET EXECUTOR
MAXIMUM LINKS n, where the valid range for n is between 1 and 960,
unless the ALIAS MAXIMUM LINKS parameter is also specified, in which
case the valid range is between 1 and 512. A reasonable range for maximum
links on most networks is between 25 and 50.
NOLINXXX,

lines 'xxx:yyy' do not exist

Facility: DEBUG, VMS Debugger
Explanation: The line number range 'xxx:yyy' specified on the DEBUG
command TYPE does not exist. There are no such line numbers in the
specified module (or the default module).
User Action: Reenter the command specifying line numbers that do exist.
NOLIST,

list of parameter values not allowed-check use of comma (,)

Facility: CU, Command Language Interpreter (DCL)
Explanation: A command that accepts only a single input value for a
parameter contains multiple values separated by commas (, ).
User Action: Reenter the command; specify only one file. If necessary, enter
the command once for each file specified.
NOLIST,

parameter list not allowed

Facility: DSR, DIGITAL Standard Runoff
Explanation: The command does not accept a list of parameters.
User Action: Eliminate the parameter list.

2-74

Messages

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.
NOLISTENER,

specified remote system process not listening

Facility: SYSTEM, VMS System Services
Explanation: A system facility attempted to connect to a remote process that
is not enabled for connections.
User Action: Ensure that the remote process is receiving connections.
NOLITERAL,

no LITERAL translation exists for 'xx'

Facility: PATCH, Patch Utility, or DEBUG, VMS Debugger
Explanation: If the Patch Utility generated this message, the value
represented as 'xx' does not have a symbolic equivalent associated with it.
Either there is no name for 'xx' or the symbolic names were not included at
compile or link time. If the debugger generated this message, the command
attempted to find a literal translation for a value. The debugger does not
support this operation.
User Action: If the Patch Utility generated this message, ensure that local
symbol information is passed to PATCH, by reassembling or recompiling and
linking your program including the DEBUG or Traceback Facility.
NOLOAD,

network and sequentially loaded files are not installable

Facility: INSTALL, Install Utility
Explanation: Known file entries cannot be created for files that stored on
magnetic tape or that are accessible through a network.
User Action: Transfer the file to a disk and then install it.
NOLOCALS,

image does not contain local symbols

Facility: DEBUG, VMS Debugger
Explanation: All the modules in the image were compiled or assembled
without traceback information. There is no local symbol information in the
image.
User Action: Recompile or reassemble the modules using the /DEBUG
qualifier and then relink them.
NOLOCKID,

no lock id, available

Facility: SYSTEM, VMS System Services
Explanation: The system's lock identification table is full when an $ENQ
system service request is attempted.
User Action: Either retry the program or increase the size of the lock id table
by increasing the value of the SYSGEN parameter LOCKIDTBL.

2-75

Messages

NOLOGNAM,

no logical name match

Facility: SYSTEM, VMS System Services
Explanation: A specified logical name does not exist or cannot be deleted by
the current access mode.
User Action: Check for a programming error. Verify the spelling of the
logical name.
NOLOGTAB,

no logical name table match

Facility: SYSTEM, VMS System Services
Explanation: The specified logical name does not exist.
User Action: Check for a programming error. Verify the spelling of the
logical name table.
NOLOWVER,

no lower version of file 'filespec' found

Facility: DIFF, DIFFERENCES Command
Explanation: The Differences Utility cannot default the revision file
specification because no lower version of the master file exists.
User Action: Check that the file exists. Reenter the command, explicitly
specifying the revision file specification.
NOMACFOUND,

no .MACRO found in 'input-filespec'

Facility: LIBRAR, LIBRARY Command
Explanation: The specified input file does not contain a properly formatted
macro.
User Action: Reformat the macro source file.
NOMALFUNl,

no malfunctions detected since power up

Facility: DTK, DECtalk Facility
Explanation: This is an informational message telling you that no
malfunctions occurred since the DECtalk device was turned on. This is
the first reply.
User Action: None.
NOMALFUN2,

no malfunctions detected since power up

Facility: DTK, DECtalk Facility
Explanation: This is an informational message telling you that no
malfunctions occurred since the DECtalk device was turned on. This is
the second or later reply.
User Action: None.

2-76

Messages

NOMATCH,

'filespec'-'xxx' records

Facility: SEARCH, SEARCH Command
Explanation: This message displays the name of the file and the number of
records searched. The search strings were not found in the file. This message
is informational.
User Action: None.

NOMATCH,

no match found against input string

Facility: STR, String Manipulation Facility
Explanation: There is no match found for the input string that is passed to
the routine.
User Action: None.

NOMATCHES,

no strings matched

Facility: SEARCH, SEARCH Command
Explanation: The search operation is able to open and search one or
more files, but the files did not contain the search strings. This message
is informational.
User Action: None.

NOMATCHFOU,

no match found

Facility: LBR, Librarian Subroutine Package
Explanation: The specified module does not appear in the module name
table.
User Action: Ensure that the module exists in the current library.

NOMBX,

no associated mailbox for inbound connects

Facility: SYSTEM, VMS System Services
Explanation: A channel specified for network operations does not have a
mailbox associated with it.
User Action: Correct the source program to create a mailbox, and associate
the mailbox with the channel on the assign request.

NOMEMBER,

specified node has left cluster

Facility: SMI, System Management Intergator/Server
Explanation: The cluster configuration changed while processing a SYSMAN
command. The command continues on the next node in the environment.
User Action: None.

NOMODNAM,

no module name found for 'input filespec'

Facility: LIBRAR, LIBRARY Command
Explanation: An attempt is made to insert unnamed text modules into a text
library.
User Action: Use the /MODULE qualifier to name the text modules.

2-77

Messages

NOMODS,

no input modules specified (or found)

Facility: LINK, Linker Utility
Explanation: The command line did not specify any input modules.
User Action: Reenter the command, specifying some modules to link.
NOMODS,

no modification made

Facility: CDU, Command Definition Utility
Explanation: The process tables were not modified because a CLD file is not
entered in the command string.
User Action: Add CLD file to the command string.
NOMODS,

no modifications made to system authorization file

Facility: AUTHORIZE, Authorize Utility
Explanation: This is an informational message.
User Action: None.
NOMORE,

wildcard request complete

Facility: DEBUG, VMS Debugger
Explanation: This is a debugger internal error code.
User Action: Submit a Software Performance Report.
NOMORECHAR,

no more characteristics found

Facility: JBC, Job Controller
Explanation: No more characteristics exist that match a wildcard name
specified for the QUI$_DISPLAY_CHARACTERISTICS function of the
$GETQUI system service. This condition indicates that at least one match had
been found in previous calls during the wildcard search for characteristics.
User Action: Note the condition and, if necessary, modify the source
program to detect and respond to the condition.
NOMOREENT,

no more entries found

Facility: JBC, Job Controller
Explanation: No more job entries exist for the specified user name. This
condition is returned for the QUI$_DISPLAY_ENTRY function of a call to the
$GETQUI system service. It indicates that at least one entry had been found
in previous calls during the wildcard search for entries.
User Action: Note the condition and, if necessary, modify the source
program to detect and respond to the condition.

2-78

Messages

NOMOREFILE,

no more files found

Facility: JBC, Job Controller
Explanation: No more files for the specified batch or print job exist. This
condition is returned for the QUI$_DISPLAY_FILE function of a call to the
$GETQUI system service. It indicates that at least one file had been found in
previous calls during the wildcard search for files.
User Action: Note the condition and, if necessary, modify the source
program to detect and respond to the condition.
NOMOREFILES,

no more files

Facility: SYSTEM, VMS System Services
Explanation: No more files match a wildcard in a file specification string. At
least one match is found.
User Action: Note the condition. Modify the source program, if necessary, to
detect and respond to the condition.
NOMOREFORM,

no more forms found

Facility: JBC, Job Controller
Explanation: No more forms match a wildcard name specified for the
QUI$_DISPLAY_FQRM function of the $GETQUI system service. This
condition indicates that at least one match had been found in previous calls
during the wildcard search for forms.
User Action: Note the condition and, if necessary, modify the source
program to detect and respond to the condition.
NOMOREITEMS,

no more items in message

Facility: SMB, Symbiont Services
Explanation: This value is returned by the SMB$READ_MESSAGE routine
indicating no items remain on the list.
User Action: Note the condition and, if necessary, modify the source code to
detect the condition.
NOMOREJOB,

no more jobs found

Facility: JBC, Job Controller
Explanation: No more jobs for the specified batch or print queue exist. This
condition is returned for the QUI$_DISPLAY_JOB function of a call to the
$GETQUI system service. It indicates that at least one job had been found in
previous calls during the wildcard search for jobs.
User Action: Note the condition and, if necessary, modify the source
program to detect and respond to the condition.

2-79

Messages

NOMOREKEYS,

no more keys defined

Facility: SMC, Screen Management Facility
Explanation: SMC$LIST_KEY_DEFS, when called repeatedly, returns all the
key definitions in a key table. When there are no more definitions, this error
is returned.
User Action: Modify your program to expect this condition, if necessary.
NOMOREMSC,

no more messages

Facility: MAIL, Mail Utility
Explanation: You have no more messages to read.
User Action: If you want to read your messages again, enter the MAIL
command READ; otherwise, no action is required.
NOMOREPROC,

no more processes

Facility: SYSTEM, VMS System Services
Explanation: The search for processes is complete.
User Action: Note the condition. Modify the source program, if necessary, to
detect and respond to the condition.
NOMOREQUE,

no more queues found

Facility: JBC, Job Controller
Explanation: No more queues match a wildcard name specified for the
QUI$_DISPLAY_QUEUE function of the $CETQUI system service. This
condition indicates that at least one match had been found in previous calls
during the wildcard search for queues.
User Action: Note the condition and, if necessary, modify the source
program to detect and respond to the condition.
NO_MORMSC,

no more broadcast messages are available

Facility: SMC, Screen Management Facility
Explanation: A call to SMC$GET_BROADCAST_MESSACE found that there
are no more messages to be obtained.
User Action: None.
NOMP,

qualifier only valid for multiprocessor systems

Facility: Shared by several facilities
Explanation: This error is returned when the system is not running in a
multiprocessor configuration.
User Action: None.
NOMSCS,

no messages

Facility: MAIL, Mail Utility
Explanation: There are no mail messages.
User Action: None.

2-80

Messages

NOMSGS,

no messages defined

Facility: MESSAGE, Message Utility
Explanation: No messages have been defined in the message source file.
User Action: Ensure that at least one message definition appears in the
message source file.

NOMTCHENDM,

no matching .ENDM for macro 'macro-name' in library
'library-name'

Facility: LIBRAR, LIBRARY Command
Explanation: The specified macro does not contain a matching .ENDM line.
User Action: Reformat the macro source file.

NOMTCHENDR,

'location' missing .ENDR for macro 'macro-name' in 'libraryname'

Facility: LIBRAR, LIBRARY Command
Explanation: The Librarian Utility found a matching .ENDM before the
required .ENDR.
User Action: Correct the macro source file.

NOMTCHFOU,

no match found

Facility: LBR, Librarian Subroutine Package
Explanation: The specified module does not appear in the Module Name
Table (MNT).
User Action: Ensure that the module exists in the current library.

NOMTCHFOU,

no matches found for 'module-name'

Facility: LIBRAR, LIBRARY Command
Explanation: The module specified with the /ONLY qualifier is not in the
Module Name Table (MNT).
User Action: Ensure that the specified module exists.

NOMUL TBK,

ACP multiple block buffering not supported yet

2-81

Messages

NONAMES,

there are no names matching the one requested

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The built-in procedure EXP AND_NAME cannot find any
names matching the one you requested.
User Action: None.
NONANSICRT,

SYS$INPUT must be a supported CRT

Facility: VAXTPU, VAX Text Processing Utility
Explanation: You ran VAXTPU with SYS$INPUT associated with a terminal
that does not have the appropriate characteristics, or you ran VAXTPU from a
command procedure without assigning SYS$INPUT to SYS$COMMAND.
User Action: Run VAXTPU from a supported device or use the
/NODISPLAY command qualifier. In a command procedure, assign
SYS$INPUT to SYS$COMMAND before invoking VAXTPU.
NONBRDMSG,

nonbroadcast message returned

Facility: SMC, Screen Management Facility
Explanation: A call to SMG$GET_BROADCASL.MESSAGE found that a
nonbroadcast message was returned.
User Action: None.
NONCONTIG,

'filename' is not contiguous due to insufficient contiguous space

Facility: PATCH, Patch Utility, 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.
NONCONTIG,

noncontiguous image file being written

Facility: PATCH, Patch Utility
Explanation: The image file being written by PATCH is not contiguous. This
error may be relevant to device drivers.
User Action: None.
NONEDEL..

no files processed on deletion pass

Facility: BACKUP, Backup Utility
Explanation: BACKUP did not process any files in the deletion pass. That is,
no files were deleted by the BACKUP operation.
User Action: None.

2-82

Messages

NONEFOUND,

no folders found in file 'filename' with a folder name greater
than 'filename'

Facility: MAIL, Mail Utility
Explanation: User entered a DIR/FOLDER/START=string command, but
there were no folders found alphabetically higher than the specified string.
User Action: None.
NONEREC,

no files processed on recording pass

Facility: BACKUP, Backup Utility
Explanation: BACKUP 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.
NONET,

network unavailable

Facility: SHOW, SHOW Command
Explanation: The network is unavailable.
User Action: None.
NONETMBX,

operation requires NETMBX privilege

Facility: SYSTEM, VMS System Services
Explanation: A command or program requested a system function that
requires NETMBX privilege; the current process does not have this privilege.
User Action: If the message is in response to a command entered
interactively, verify that you have not used a command or a qualifier for
a particular command that requires a specific user privilege.
If the message occurs during the execution of a program, determine the
system service call that resulted in the error. Verify that you have not used
a service or an argument for a particular service that requires a user privilege
that you do not have.

no new messages

Facility: MAIL, Mail Utility
Explanation: User has requested a READ /NEW, DIR/NEW, or SELECT
/NEW command and there is no new (unread) mail.
User Action: None.
NONEXDRV,

nonexistent drive

Facility: SYSTEM, VMS System Services
Explanation: The drive specified in an I/O request either does not exist or
the drive select plug is removed.
User Action: Verify the availability and status of the device. Also, check the
source program for errors.

2-83

Messages

NONEXIST,

authorization file does not exist

Facility: CAF, Cluster Authorization File Service
Explanation: A SYSMAN CONFIGURATION SHOW
CLUSTER_AUTHORIZATION command has been entered and
SYS$SYSTEM:CLUSTER_AUTHORIZE.DAT does not exist.
User Action: Create the file on all the cluster members with a
CONFIGURATION SET CLUSTER_AUTHORIZATION command at the
SYS MAN> prompt.
NONEXISTBUF,

buffer 'buffer-name' does not exist

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The buffer that you are trying to use has not been created.
User Action: Use a current buffer or create a new one.
NONEXPR,

nonexistent process

Facility: DEBUG, VMS Debugger
Explanation: A process name or a process identification specified in a
command is not valid.
User Action: Verify that the process name or identification is correct and that
the process is not already deleted. Also verify that you have the required
privilege to access the process.
NONEXPR,

nonexistent process

Facility: SYSTEM, VMS System Services
Explanation: A process name or process identification specified in a
command or system service request is not valid.
User Action: Verify that the process name or identification is correct and that
the process is not already deleted. If a process name is entered, the process
must be in the same group.
NONEXSTACP,

Nonexistent ACP process

2-84

Messages

NONLOCAL,

device is not a local device

Facility: SYSTEM, VMS System Services, MOUNT, Mount Utility and INIT,
INITIALIZE Command
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.
NONODE,

node name has not been initialized

Facility: LATCP, LAT Control Program
Explanation: You attempted to start the LAT port driver without setting up a
proper LAT node name.
User Action:
1

Define your node name in one of the following ways:
•

Equate your node name to the logical name SYS$NODE.

•

Use the SET NODE command.

•

Use the START NODE command.

Start the LAT port driver again.

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.
NONPIC,

cannot map section AS to same addresses as others mapped it

Facility: PPL, Parallel Processing Facility
Explanation: PPL cannot map requested address space to the same addresses
in all processes.
User Action: If it is critical to the application that the requested space appear
at the same addresses in all processes, the user must take steps to ensure that
enough space is made available. This may require increasing system quotas
or reserving the required addresses through link time operations.
NONPICDAT,

'number' relocatable address references in 'module-name' file
'filename'

Facility: LINK, Linker Utility
Explanation: This message informs you of the number of .ADDRESS fixups
to be done in each module by the image activator at run time. It is issued
only if a full map is requested.
User Action: None.

2-85

Messages

NONPICIMG,

shareable image 'image-name' is non-position-independent

Facility: LINK, Linker Utility
Explanation: While building a position-independent shareable image, a
shareable image is input that is not position-independent. The shareable
image being created is also built non-position-independent.
User Action: None. If possible, rebuild the non-position-independent
shareable image so that it is position-independent.
NONPICREF,

failure to use .ADDRESS for relocatable data in psect 'psect-name'
offset 'number' in module 'module-name' file 'filename'

Facility: LINK, Linker Utility
Explanation: A reference is made to relocatable data using other than the
MACRO .ADDRESS directive in a shareable image.
User Action: Use the MACRO .ADDRESS directive in reference to relocatable
data; otherwise, the image will be position-dependent.
NONSMPDRV,

non SMP 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/qbus 'device-name' in nonstandard configuration

Facility: SYSGEN, System Generation Utility
Explanation: The vector on the device specified in the message needs to be
reconfigured.
User Action: Call your DIGITAL field service representative.
NONXTLIN,

next line for source display not defined

Facility: DEBUG, VMS Debugger
Explanation: The DEBUG command TYPE or SEARCH is entered without
specifying a line number (for example, the next line after the last source line
printed should be used). But no next source line is currently defined.
User Action: Reenter the command explicitly specifying the desired line
number.
NOONE_ENABLED , no one presently enabled for event notification
Facility: PPL, Parallel Processing Facility
Explanation: Event trigger is successfully queued, and no one is presently
enabled to receive it. The first caller to enable the trigger will receive it.
User Action: Continue normally.

2-86

Messages

NOOPENJOB,

no open job for requesting process

Facility: JBC, Job Controller
Explanation: The requesting process did not open a job with the SJC$_
CREATE_JOB function prior to making the current $SNDJBC request, or
did not open a job with the SMR$K_CREJOB function prior to making the
current $SNDSMB request.
User Action: Modify the program to open a job first.
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.
NOOPER,

OPER privilege required on all nodes, access rejected

Facility: SMI, System Management Intergator/Server
Explanation: OPER privilege is required to run SYS MAN. If any nonlocal
environment is used, OPER privilege must also be authorized in the UAF on
each remote node.
User Action: Correct the authorized privileges in the associated UAF files.
NOOPER,

SYSMAN requires OPER privilege

Facility: SYSMAN, Cluster System Management Utility
Explanation: You are required to have OPER privilege.
User Action: Enter a SET PROCESS /PRIVILEGE=OPER command from the
DCL level before entering SYSMAN commands.
NOOPER,

operation requires OPER privilege

Facility: SYSTEM, VMS System Services and JBC, Job Controller
Explanation: A command or program requested a system function that
requires OPER privilege; the current process does not have this privilege.
User Action: If the message is in response to a command entered
interactively, verify that you have not used a command or a qualifier for
Cl particular command that requires a specific user privilege.
If the message occurs during the execution of a program, determine the

system service call that resulted in the error. Verify that you have not used
a service or an argument for a particular service that requires a user privilege
that you do not have.
In either case, correct the command or program so that you do not request
the privilege function. If you determine that you need the privilege for an
application, contact your system manager to obtain the necessary privilege.

2-87

Messages

NOOPR,

no operator available to service request

Facility: MOUNT, Mount Utility
Explanation: There is no operator present to service the request.
User Action: You can either service the request yourself or abort the request.

NOOPRND,

missing operand in expression

Facility: PATCH, Patch Utility and DEBUG, VMS Debugger
Explanation: One or more operands were omitted from the expression.
User Action: Add the correct number of operands and retry.

NOOUTPUT,

no output selected ... specify /DISPLAY, /RECORD, or
/SUMMARY

Facility: MONITOR, Monitor Utility
Explanation: The MONITOR request selected (explicitly or implicitly) none
of the three possible output types (DISPLAY, RECORD, SUMMARY).
User Action: Reenter the MONITOR request, specifying any combination of
the qualifiers: /DISPLAY, /RECORD, or /SUMMARY.

NOOUTQUAL,

the /SHOW qualifier is invalid without specifing the /OUTPUT
qualifier

Facility: BAD, Bad Block Locator Utility
Explanation: The /SHOW qualifier is specified without specifying the
/OUTPUT qualifier.
User Action: Specify the /OUTPUT qualifier with the /SHOW qualifier in
the command.

NO Pl VA,

Pl space not supported in shareable images

Facility: SYSTEM, VMS System Services
Explanation: Pl space is not supported in shareable images.
User Action: Relink the image, positioning all binary data in PO space.

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.

NOP ARAM,

no such parameter

Facility: SYSGEN, System Generation Utility
Explanation: The parameter name specified in a SYSGEN command SET or
SHOW is not valid.
User Action: Reenter the command specifying a valid parameter name.

2-88

Messages

NOPAREN, value improperly delimited-supply parenthesis
Facility: CLI, Command Language Interpreter (DCL)
Explanation: A value supplied as part of a parenthesized value list for a
parameter, qualifier, or keyword is missing a delimiting parenthesis.
User Action: Reenter the command with the missing parenthesis.

NOP ARENT,

there is no parent process to attach

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The current process is the top-level process. There is no parent
process.
User Action: None. Without a parent process there is nothing to attach to.

NOP ARENT,

there is no parent to which to attach

Facility: MAIL, Mail Utility
Explanation: User specified an ATTACH/PARENT command, and the
current process is not a subprocess. The ATTACH/PARENT command is
only legal in a subprocess.
User Action: None.

NOP ARM,

either a parameter name or group qualifier is required

Facility: SYSMAN, Cluster System Management Utility
Explanation: A PARAMETERS SHOW command must include either a
parameter name to be displayed or a qualifier specifying a parameter group.
User Action: Respecify the command with a parameter name or group
qualifier.

NOP ARM, no parameters
Facility: NCP, Network Control Program
Explanation: No parameters were specified for a command.
User Action: Reenter the command with parameters.

NOP ASS,

need remote password and SYS$COMMAND not a terminal

Facility: SYSMAN, Cluster System Management Utility
Explanation: An environment that requires an access-control password and
SYSMAN is not being run interactively. A password can only be read when
SYS$COMMAND is a terminal device.
User Action: Rerun SYSMAN interactively.

NOPASSWORD,

password must be supplied

Facility: MOM, Maintenance Operation Module
Explanation: In this LOOP NODE or LOOP EXECUTOR command, a
password must be supplied.
User Action: Supply a password with the LOOP command.

2-89

Messages

NOPATAREA,

insufficient patch area at 'addr', size= 'nn'

Facility: PATCH, Patch Utility
Explanation: The current user-defined patch area is not large enough to store
the given code.
User Action: Use the default patch area or an alternate user-defined patch
area of a larger size.

NOPE,

permanent qualifier not specified

Facility: Shared by several facilities
Explanation: You tried to set a terminal characteristic for a terminal that is
not allocated to a user process. The default action of the DCL command SET
TERMINAL is to set a specified terminal characteristic for the duration of
the current terminal session for the user to whom the terminal is allocated.
Therefore, if the terminal is not allocated, the /PERMANENT qualifier must
be used with the SET TERMINAL command. You must have the LOG_JQ or
PHY_IO user privilege to use the /PERMANENT qualifier.

NOPERATOR,

no operator coverage

Facility: OPCOM, Operator Communication
Explanation: A DCL command REQUEST specified a nonexistent operator.
No terminals are currently enabled for that operator name.
User Action: Reenter the DCL command REQUEST specifying an alternative
operator.

NOPFNMAP, operation requires PFNMAP privilege
Facility: SYSTEM, VMS System Services
Explanation: A command or program requested a system function that
requires PFNMAP privilege; the current process does not have this privilege.
User Action: If the message is in response to a command entered
interactively, verify that you have not used a command or a qualifier for
a particular command that requires a specific user privilege.
If the message occurs during the execution of a program, determine the

system service call that resulted in the error. Verify that you did not use a
service or an argument for a particular service that requires a user privilege
that you do not have.
In either case, correct the command or program so that you do not request
the privileged function. If you determine that you need the privilege for an
application, contact your system manager to obtain the necessary privilege.
NOPRED,

logical predecessor not defined

Facility: DEBUG, VMS Debugger
Explanation: The logical predecessor of the identifier or instruction
referenced is not defined. This message is informational.
User Action: None.

2-90

Messages

NOPREV,

no previous entry exists-new entry created for 'image'

Facility: INSTALL, Install Utility
Explanation: A Known File Entry is created via 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 didn't.
NOPRINT,

file 'filename' cannot be printed.

Facility: VMSINSTAL, Install Procedures
Explanation: The product installation required the printing of one or more
files. The files could not be queued for printing.
User Action: An undefined SYS$PRINT queue at your site probably caused
this error. If you do not care that the files could not be printed, ignore this
message. Otherwise, define a SYS$PRINT queue and reinstall the product.
NOPRIV, insufficient privilege or queue protection violation
Facility: JBC, Job Controller
Explanation: The queue protection denies access to the queue for the
specified operation.
User Action: None.
NOPRIV,

operation requires SYSPRV privilege

Facility: CAF, Cluster Authorization File Service
Explanation: Any access to the cluster authorization file requires SYSPRV
privilege.
User Action: Enter a SET PROFILE/PRIVILEGE=SYSPRV command, then
reenter your original command.
NOPRIV,

no privilege for attempted operation

Facility: SYSTEM, VMS System Services and JBC, Job Controller
Explanation: A command or program requested a system function that
requires a specific user privilege or privileges; the current process does not
have the requisite privilege or privileges.
Or a program image attempted to access, modify, or delete a control area
created and owned by a more privileged access mode; such areas include
pages in memory, I/O channels, or timer queue entries.
Or a command or program requested file or volume access which is denied.
Or the requesting process does not have the privilege to read or write to this
mailbox. (The protection mask is defined when the Mailbox is created.)
User Action: If the message is in response to a command entered
interactively, verify that you have not used a command or a qualifier for
a particular command that requires a specific user privilege or privileges.

2-91

Messages

If the message occurs during the execution of a program, determine the
system service call that resulted in the error. Verify that you have not used
a service or an argument for a particular service that requires a user privilege
that you do not have. Or verify that you are not attempting to modify a VMS
RMS or system-owned data area or memory page.

user denied privilege to write to volume on 'device-name'

Facility: MOUNT, Mount Utility
Explanation: The user has requested initialization of a volume and 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.

NOPRMCEB,

operation requires PRMCEB privilege

Facility: SYSTEM, VMS System Services
Explanation: A command or program requested a system function that
requires PRMCEB privilege; the current process does not have this privilege.
User Action: If the message is in response to a command entered
interactively, verify that you have not used a command or a qualifier for
a particular command that requires a specific user privilege.
If the message occurs during the execution of a program, determine the
system service call that resulted in the error. Verify that you have not used
a service or an argument for a particular service that requires a user privilege
that you do not have.

operation requires PRMGBL privilege

Facility: SYSTEM, VMS System Services
Explanation: A command or program requested a system function that
requires PRMGBL privilege; the current process does not have this privilege.
User Action: If the message is in response to a command entered
interactively, verify that you have not used a command or a qualifier for
a particular command that requires a specific user privilege.
If the message occurs during the execution of a program, determine the
system service call that resulted in the error. Verify that you have not used
a service or an argument for a particular service that requires a user privilege
that you do not have.

In either case, correct the command or program so that you do not request
the privilege function. If you determine that you need the privilege for an
application, contact your system manager to obtain the necessary privilege.

2-92

Messages

NOPRMMBX,

operation requires PRMMBX privilege

Facility: SYSTEM, VMS System Services
Explanation: A command or program requested a system function that
requires PRMMBX privilege; the current process does not have this privilege.
User Action: If the message is in response to a command entered
interactively, verify that you have not used a command or a qualifier for
a particular command that requires a specific user privilege.
If the message occurs during the execution of a program, determine the

system service call that resulted in the error. Verify that you have not used
a service or an argument for a particular service that requires a user privilege
that you do not have.
In either case, correct the command or program so that you do not request
the privileged function. If you determine that you need the privilege for an
application, contact your system manager to obtain the necessary privilege.
NOPROC,

the kit installation procedure is missing.

Facility: VMSINSTAL, Install Procedures
Explanation: The main installation procedure for the product is not located
on the distribution media.
User Action: Contact your DIGITAL field service representative.

NOPROCESS,

no subprocess to interact with

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The subprocess you tried to send data to or receive data from
does not exist.
User Action: Re-create the subprocess.

NOPRODS,

None of the specified products were found.

Facility: VMSINSTAL, Install Procedures
Explanation: None of the products you specified for installation exist on the
distribution media.
User Action: Specify products that exist on the media.

NOPROT,

protocol not supported on remote node

Facility: REM, Set Host Facility
Explanation: A DCL command SET HOST has been entered on a node that
does not support the remote terminal protocol.
User Action: None.

NOPSCTS,

no psects defined in module 'module-name' file 'filename'

Facility: LINK, Linker Utility
Explanation: The specified module did not define any psects. At least one
psect must be defined in each object module.
User Action: Define a psect in the specified module.

2-93

Messages

NOPSWAPM,

operation requires PSWAPM privilege

Facility: SYSTEM, VMS System Services
Explanation: A command or program requested a system function that
requires PSWAPM privilege; the current process does not have this privilege.
User Action: If the message is in response to a command entered
interactively, verify that you have not used a command or a qualifier for
a particular command that requires a specific user privilege.
If the message occurs during the execution of a program, determine the

system service call that resulted in the error. Verify that you have not used
a service or an argument for a particular service that requires a user privilege
that you do not have.
In either case, correct the command or program so that you do not request
the privileged function. If you determine that you need the privilege for an
application, contact your system manager to obtain the necessary privilege.
NOQFILE,

no disk quota file available

Facility: SYSTEM, VMS System Services
Explanation: The quota file does not exist.
User Action: Verify that you are using the correct device. Create the quota
file.

NOQUAL,

no qualifier in statement

Facility: FDL, Edit/FDL Utility
Explanation: You specified a secondary that requires a qualifier, but none is
given.
User Action: Specify a qualifier for a secondary.

NOQUAL,

no qualifier in statement n

Facility: FDL, Create/FDL Utility
Explanation: You have left off a qualifier from the attribute keyword.
User Action: Edit the FDL file and add the qualifier.

NOQUAL,

qualifiers not allowed-supply only verb and parameters

Facility: CU, Command Language Interpreter (DCL)
Explanation: A command that has no qualifiers is specified with a qualifier.
User Action: Reenter the command; do not specify any qualifiers.

NOQUECTX,

no queue context

Facility: JBC, Job Controller
Explanation: A call was made to the $GETQUI system service requesting the
$QUI_DISPLAY_JOB function without first establishing a queue context for
this call.
User Action: Modify the application to first establish a queue context by
calling the $GETQUI system service in wildcard mode using the
QUI$_DISPLAY_QUEUE function code.

2-94

Messages

NOQUESP ACE,

no space in system job queue file

Facility: JBC, Job Controller
Explanation: The system job queue file is full and cannot be extended.
User Action: Notify the system manager, as this condition indicates a lack of
space on the disk that contains the system job queue file. In the meantime,
wait for existing jobs to complete and reenter your request.

NOQUEUE,

'queue-name' queue does not exist

Facility: Shared by several facilities
Explanation: A request to enter or change a queued file failed because the
queue does not exist.
User Action: Verify the queue name in the command and reenter the
command. To determine the names and status of currently available queues,
use the DCL command SHOW QUEUE/DEVICES/BATCH.

Note that the DCL commands SET QUEUE and SHOW QUEUE do not
translate logical names. If you specified a logical name, reenter the command
with the physical queue name.
NOQUOTE,

quoted string missing end quote

Facility: AUTHORIZE, Authorize Utility
Explanation: Your command line is missing a quotation mark (" ).
User Action: Reenter the command line with both quotation marks.

NORCP,

RCP not active

NORCVBUF,

NETACP-no receive buffer available

2-95

Messages

NO READ,

unable to access location

Facility: SDA, System Dump Analyzer
Explanation: SDA is unable to read a certain location. The inaccessible
location may be an implied reference to memory made during the execution
of an SDA command.
User Action: None.
NOREDEFINE,

built-in procedure 'procedure-name' cannot be redefined

Facility: VAXTPU, VAX Text Processing Utility
Explanation: Your program uses a VAXTPU built-in procedure name as the
name of a user-written procedure. Built-in procedures cannot be superseded
by user-defined procedures.
User Action: Give your procedure a name that does not conflict with any of
the names of the VAXTPU built-in procedures.
NOREF,

page reference not found

Facility: DSR, DIGITAL Standard Runoff
Explanation: An internal error has occurred.
User Action: Submit a Software Performance Report. If possible, include the
file that caused the error in the report.
NORELNOTE,

unable to locate release notes

Facility: VMSINSTAL, Install Procedures
Explanation: You specified the Release Notes option during a layered product
installation. The product does not include online release notes.
User Action: None.
NORELOC,

relocation of CASE instructions not supported

Facility: PATCH, Patch Utility
Explanation: The PATCH Utility does not automatically move CASE
instructions to the patch area.
User Action: CASE instructions may be moved to the patch area by using
PATCH commands DELETE/INSTRUCTION and DEPOSIT/INSTRUCTION
/PATCH_AREA and the MACRO assembler directive .WORD.
NOREMOTE,

remote node name not permitted in 'string'

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility found a network node name in a context
where network access is not permitted.
User Action: Reenter the command specifying a local device name, or log in
to the desired node and reenter the EXCHANGE command on that node.

2-96

Messages

NORENDEV,

cannot RENAME to a different device

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility encountered a RENAME command which
attempted to rename a file from one device to another.
User Action: Use the COPY command to move a file to another device, or
check the RENAME command for a misspelled device name.
NORENEXISTS,

file 'filename' not renamed, 'filename' already exists

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility cannot rename a file because a file with
the same name already exists.
User Action: Choose a file name that does not already exist, or delete the
existing file and redo the RENAME command.
NORENLOCK,

file 'filename' not renamed, volume is write locked

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility could not perform a RENAME command
because the output volume is write locked.
User Action: Remount the output volume with write access, then reenter the
command.
NOREP AIR,

one or more volumes write locked-/REP AIR canceled

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that one or more volumes of the
volume set are write locked, and therefore a /REP AIR operation cannot be
executed.
User Action: Write enable all volumes of the volume set and reenter the
Verify Utility command line.
NOREQ,

symbol 'symbol-name' not found in SDA symbol table

Facility: SDA, System Dump Analyzer
Explanation: SDA cannot find a symbol in the SYS.STB file that is vital to its
initialization.
User Action: None.
NOREQSYM,

symbol 'name' not found in system symbol table

Facility: SDA, System Dump Analyzer
Explanation: SDA cannot find a symbol in the SYS.STB file that is required
for proper initialization of SDA.
User Action: Check the integrity of the symbol table file.

2-97

Messages

NORESTART,

job is not restartable

Facility: JBC, Job Controller
Explanation: The specified job cannot be requeued because it is not defined
to be restartable.
User Action: None.
NORETURNVALUE,

built-in does not return a value

Facility: VAXTPU, VAX Text Processing Utility
Explanation: This built-in does not return a value and cannot be used in
situations in which a return value will be used.
User Action: Do not use this built-in as part of an assignment statement or
as part of an expression.
NORIGHTSDB,

rights data base file not found

Facility: AUTHORIZE, Authorize Utility and SYSTEM, VMS System Services
Explanation: An attempt to access the rights database failed because the file
does not exist or could not be found (if redirected with a logical name).
User Action: Create a rights database using the AUTHORIZE command
CREATE/RIGHTS, or contact the system manager to determine why the
rights database file does not exist or is not available.
NORMAL,

normal successful completion

Facility: Shared by several facilities
Explanation: This success message indicates that the operation completed
normally. This is an informational message.
User Action: None.
NORMAL,

success

Facility: LIBRAR, LIBRARY Command and LBR, Librarian Subroutine
Package
Explanation: This success message is associated with a code returned by the
librarian, or generated by the DCL command LIBRARY. The operating system
does not normally display this message. This is a success status code.
User Action: None.
NORMAL _EXIT,

normal exit-ppl index

Facility: PPL, Parallel Processing Facility
Explanation: This message indicates the occurrence of the normal participant
termination event.
User Action: Since the application requested this notification, response is
application-dependent.

2-98

Messages

NOROOM,

no room for new entry

Facility: NCP, Network Control Program
Explanation: Insufficient space for new table entry. For example, there is not
enough paged pool to allocate room for a new node to be defined.
User Action: Increase the resources DECnet is allocated.

NOROOM,

no room in dictionary for definition

Facility: DTK, DECtalk Facility
Explanation: There is no room left in the dictionary for this definition.
User Action: Correct your program so that it requests fewer dictionary entries
or so that each entry is smaller.

NORSTBLD,

cannot build symbol table

Facility: DEBUG, VMS Debugger
Explanation: The debugger is unable to build a symbol table because of
errors in the format of the image file.
User Action: Relink the image and, if the error is reproducible, submit a
Software Performance Report explaining how the image file is created.

NORSTBLD,

cannot build symbol table

Facility: PATCH, Patch Utility
Explanation: When PATCH is initialized, it could not allocate space to build
a symbol table.
User Action: Check with your System Manager to ensure that the system is
bootstrapped with enough virtual address space.

NORTTB, internal error-No routine table for object
Facility: SMI, System Management Intergator/Server
Explanation: An object is defined in server tables, but the entry point is 0.
User Action: Submit a Software Performance Report showing all SYSMAN
commands leading to this error.

NOSAVESET,

Required save set 'letter' does not exist.

Facility: VMSINSTAL, Install Procedures
Explanation: The product save set with the specified letter, which is required
for the installation, does not exist on the distribution media.
User Action: Contact your DIGITAL field service representative.

NOSCOPE,

no scope exists to look up line 'line-number'

Facility: DEBUG, VMS Debugger
Explanation: The specified 'line-number' cannot be found because there is
no current scope to look it up in.
User Action: Specify the module explicitly and retry the operation.

2-99

Messages

NOSCS,

error loading SCS code

Facility: SYSGEN, System Generation Utility
Explanation: You were unable to load SCSLOA.EXE.
User Action: Do not attempt to load SCSLOA.EXE.
NOSECEX,

no such section exists

Facility: PPL, Parallel Processing Facility
Explanation: The section specified to flush or delete does not exist.
User Action: Recode your program to ensure that the section to flush or
delete has been created.
NOSELECT,

no select active

Facility: VAXTPU, VAX Text Processing Utility
Explanation: You tried to select a range of text with only the built-in
procedure SELECT_RANGE (and not with the built-in procedure SELECT
as well).
User Action: Begin a selection by using the built-in procedure SELECT.
NOSENDBUF,

cannot SEND a buffer to a process using the buffer

Facility: VAXTPU, VAX Text Processing Utility
Explanation: You tried to send a buffer to a process using the buffer for its
output. This can result in an infinite loop.
User Action: Move or copy the data to a different buffer and send the new
one.
NOSERVER,

SMI Server not running in target node

Facility: SMI, System Management Intergator/Server
Explanation: Process SMISERVER is not running in the indicated node
•

It may have been stopped with the STOP command.

•

It may have been aborted.

•

The remote system has not progressed far enough in the system startup
procedure to have started SMISERVER.

User Action: Determine why SMISERVER is not running. Restart it if
necessary with the following command run from the SYSTEM account on the
target system:
$ ©SYS$SYSTEM:STARTUP SMISERVER

NOSERVERS, No known servers,
Facility: LATCP, LAT Control Program
Explanation: You entered a SHOW COUNTERS /SERVER or SHOW
SERVERS command, but there are no servers in the LATCP database.
User Action: None.

2-100

Messages

NOSETPRV,

operation requires SETPRV privilege

Facility: SYSTEM, VMS System Services
Explanation: A command or program requested a system function that
requires SETPRV privilege; the current process does not have this privilege.
User Action: If the message is in response to a command entered
interactively, verify that you have not used a command or a qualifier for
a particular command that requires a specific user privilege.
If the message occurs during the execution of a program, determine the
system service call that resulted in the error. Verify that you have not used
a service or an argument for a particular service that requires a user privilege
that you do not have.

You are not running on an account with SETPRV privilege.

Facility: VMSINSTAL, Install Procedures
Explanation: When VMSINSTAL begins an installation, it makes sure that
your account has the SETPRV privilege. This check failed.
User Action: You are asked if you want to continue the installation.
DIGITAL recommends that you correct this situation before continuing.
NOSEVER,

severity unspecified, ERROR used

Facility: MESSAGE, Message Utility
Explanation: The severity of a facility's messages has not been defined. The
Message Utility has assigned the level ERROR to the messages.
User Action: Add the appropriate severity levels to the message source
file, either with severity definitions or with severity qualifiers on message
definitions.
NOSHMBLOCK,

no free shared memory block available for creation

Facility: SYSTEM, VMS System Services
Explanation: No free shared memory control block (mailbox, common event
flag cluster, or global section descriptor) is available for creation.
User Action: Wait for the resource to become available, or reboot the system
and reinitialize shared memory, specifying more of the needed resource.

2-101

Messages

NOSHMEM,

operation requires SHMEM privilege

Facility: SYSTEM, VMS System Services
Explanation: A command or program requested a system function that
requires SHMEM privilege; the current process does not have this privilege.
User Action: If the message is in response to a command entered
interactively, verify that you have not used a command or a qualifier for
a particular command that requires a specific user privilege.
If the message occurs during the execution of a program, determine the

system service call that resulted in the error. Verify that you have not used
a service or an argument for a particular service that requires a user privilege
that you do not have.
In either case, correct the command or program so that you do not request
the privileged function. If you determine that you need the privilege for an
application, contact your system manager to obtain the necessary privilege.
NOSHMGSD,

No shared memory global section dsc found for page

variable SHOW_BUFFER does not exist or is not a buffer

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The built-in procedure SHOW depends on SHOW_BUFFER
existing as a variable that references a buffer.
User Action: Create the variable SHOW_BUFFER and have it reference a
buffer before retrying SHOW.
NOSHRD,

file cannot be made SHARED

Facility: INSTALL, Install Utility
Explanation: Only native-mode images and compatibility-mode images
supported by the AME provided by VAX RSX are supported as shareable
known files.
User Action: Reinstall without the /SHAR qualifier.

2-102

Messages

NOSHRIMG,

image activator message

Facility: SYSTEM, VMS System Services
Explanation: Privileged shareable images, also known as user-written system
services or protected images, cannot reference other shareable images. This
check is made when the privileged shareable image is activated. If a reference
to another image is detected, the entire activation is aborted and this error
message is issued.
User Action: Rewrite the privileged shareable image so that it does not
reference other shareable images.
NOSIGNAL,

no signal currently active

Facility: SYSTEM, VMS System Services
Explanation: A call to the Unwind Call Stack ($UNWIND) system service
is made when there is no exception condition. The procedure that is calling
$UNWIND is not called by the exception dispatcher.
User Action: Check for a programming error.
NOSLOT,

no pcb available

Facility: SYSTEM, VMS System Services
Explanation: The maximum number of processes that can be created at one
time has been exceeded.
User Action: Wait for another process to be deleted, or increase the
MAXPROCESSCNT system parameter.
NOSOLICIT,

interrupt message not solicited

Facility: SYSTEM, VMS System Services
Explanation: The program attempted to send an interrupt message to a
partner on a remote node, but the DECnet-VAX implementation on that node
has not solicited a message.
User Action: Wait and retry the request.
NOSP ACE,

failure to map symbol table, EXPREG status = 'xxxxxxxx'

Facility: TRACE, Traceback Facility
Explanation: The traceback facility cannot perform a symbolic traceback
because the symbol table cannot be mapped. The hexadecimal status
code from the Expand Program/Control Region ($EXPREG) system service
indicates the reason for the failure.
User Action: Submit a Software Performance Report.

2-103

Messages

NOSP ACE,

There are not enough blocks to restore the system disk.

Facility: VMSINSTAL, Install Procedures
Explanation: After installation on a dual-RL02 system, VMSINSTAL attempts
to restore your system disk to its original tailoring configuration. However,
there are not enough free blocks left on the system disk.
User Action: VMSINSTAL tells you how many additional free blocks are
required. Do the following:
1

Purge and delete files to make more space on the system disk.

Restore the original tailoring configuration.

NOSRCHSTR,

search string not set

Facility: DEBUG, VMS Debugger
Explanation: No current search string is defined for the DEBUG command
SEARCH. The SEARCH command is entered without a search string,
indicating that the current search string should be used. But no previous
SEARCH command has been entered to define a current search string.
User Action: Explicitly specify the desired search string on the command.
NOSRCLIN,

no source line for address 'address_value'

Facility: DEBUG, VMS Debugger
Explanation: No source line corresponds to the address 'address_value'
specified with the EXAMINE/SOURCE command. This message is
informational.
User Action: None.
NOSTATS,

run-time statistics not available

Facility: ERF, Error Log Utility
Explanation: An internal consistency error was encountered.
User Action: Submit a Software Performance Report.
NOSTRING,

no search string specified

Facility: SEARCH, SEARCH Command
Explanation: You did not specify a search string.
User Action: Specify a search string.
NOSTRMEM,

string allocation failure

Facility: VAXTPU, VAX Text Processing Utility
Explanation: An internal VAXTPU failure occurred.
User Action: Submit a Software Performance Report.

2-104

Messages

NOSUBEXI,

a subprocess does not exist for this virtual display

Facility: SMG, Screen Management Facility
Explanation: A subprocess does not exist for the specified virtual display.
User Action: Call SMG$CREATE_SUBPROCESS to create a subprocess for
this virtual display.

NOSUCC,

logical successor not defined

Facility: DEBUG, VMS Debugger
Explanation: The logical successor of the referenced instruction or identifier
is not defined.
User Action: None.

NOSUCHACE,

ACE for object 'filename' does not exist

Facility: SET, SET Facility
Explanation: The specified ACE to be deleted or replaced does not exist.
User Action: Verify the existence of the ACEs being replaced or deleted with
the DIRECTORY/ ACL command or the DCL SHOW ACL command.

NOSUCHBPT,

no such breakpoint

Facility: DEBUG, VMS Debugger
Explanation: The CANCEL BREAK command specified an address that is not
the address of a breakpoint.
User Action: Use the SHOW BREAK command to find the location of the
current breakpoints, and then cancel any of these breakpoints that you want
to cancel.

NOSUCHCHAR,

no such characteristic

Facility: JBC, Job Controller
Explanation: The specified characteristic does not exist. In a wildcard
$GETQUI operation, no more characteristics matching the specified selector
exist.
User Action: None.

NOSUCHCPU,

CPU does not exist, system is not a multiprocessor, or
multiprocessing disabled

Facility: SMP, Symmetric Multiprocessing
Explanation: This message is output by the $START /CPU, $STOP /CPU, or
$SHOW CPU command in one of the following cases:

Case 1: A $START/CPU, $STOP/CPU, or $SHOW CPU command
was entered which specified one or more CPU IDs not present in the
configuration.
Case 2: The command was entered on a single CPU configuration or on
a CPU type that does not support multiprocessing operation.

2-105

Messages

Case 3: A $START /CPU or $STOP /CPU command was entered on a
multiprocessor configuration in which multiprocessing has been disabled
through the MULTIPROCESSING SYSGEN parameter.
Explanation: The action to take for each case follows:
Case 1: Enter the $SHOW CPU command to determine what CPU
IDs are present in the configuration, and reenter the failed command
specifying the correct CPUs and omitting the CPUs not present.
Case 2: None. This command is not useful on such CPUs.
Case 3: Reset this parameter and reboot the system to enable
multiprocessor operation.
NOSUCHCTX,

context parameter invalid or no previous SMI$INIT

Facility: SMI, System Management Intergator/Server
Explanation: This message indicates an internal error. SMI call specifies an
invalid context handle.
User Action: Submit a Software Performance Report showing the SYSMAN
commands leading to the error.
NOSUCHDEV,

nonexistent drive

Facility: VAXCLUSTER, VAXcluster Facility
Explanation: A nonexistent drive was specified for the satellite system disk.
User Action: Check the load assist parameter specification in the DECnet
MOP database using NCP. Ensure that the correct system disk is specified
and make sure it is served using the SHOW DEVICE/SERVED command.
NOSUCHDEV,

no such device available

Facility: SYSTEM, VMS System Services
Explanation: A device name specified for a command or program does not
exist, or a system volume is not ready and available for use.
User Action: Verify that the device name is specified correctly, and that the
device is available in your system configuration. Use the DCL command
SHOW DEVICES to determine whether such a device exists.
If the device is coded as a logical name, verify that it is assigned a valid

equivalence name.
NOSUCHELE,

no element with the specified ID exists

Facility: PPL, Parallel Processing Facility
Explanation: No element is specified by the input identification.
User Action: Recode your program to ensure that the input identification is
for a created element.

2-106

Messages

NOSUCHENT,

no such entry

Facility: JBC, Job Controller
Explanation: The specified job entry in the system queue file does not exist.
User Action: None.
NOSUCHFILE,

no such file

Facility: SYSTEM, VMS System Services
Explanation: The message indicates that no file with the given file
specification identifier exists, or that the directory entry points to a file that is
deleted.
User Action: Note the condition. Modify the source program, if necessary, to
detect and respond to the condition.
NOSUCHFILE,

no such file

Facility: JBC, Job Controller
Explanation: The specified file does not exist. In a wildcard $GETQUI
operation, no more files matching the specified selector exist.
User Action: None.
NOSUCHFILE, startup file does not exist
Facility: START, 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.
NOSUCHFORM,

no such form

Facility: JBC, Job Controller
Explanation: The specified form does not exist. In a wildcard $GETQUI
operation, no more forms matching the specified selector exist.
User Action: None.
NOSUCHJOB,

no such job

Facility: JBC, Job Controller
Explanation: The specified job does not exist. In a wildcard $GETQUI
operation, no more jobs matching the specified selector exist.
User Action: None.
NOSUCHLOC ,

no lock with the specified ID exists

Facility: PPL, Parallel Processing Facility
Explanation: No lock element is specified by the input identification.
User Action: Recode your program to ensure that the input identification is
for a created lock element.

2-107

Messages

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.

NOSUCHMOD,

module 'module-name' not found in library 'library-name'

Facility: LINK, Linker Utility
Explanation: A module requested from a library with the /INCLUDE
qualifier could not be found.
User Action: Correct the command line and relink.

NOSUCHMODU,

module 'path-name' is not in module chain

Facility: DEBUG, VMS Debugger
Explanation: The module 'path-name', specified in the SET MODULE
command, does not exist in the image. This message can be caused when: (1)
a module name has been entered incorrectly or (2) a module is compiled with
the /NOTRACE switch.
User Action: Specify a module that is in the image.

NOSUCHMODU,

no such module name 'module-name'

Facility: PATCH, Patch Utility
Explanation: The specified module name is not contained in the image file.
User Action: Retry the operation specifying a module name that is contained
in the image file.

NOSUCHNAM , no element with the specified name exists
Facility: PPL, Parallel Processing Facility
Explanation: The name you input does not specify an existing element.
User Action: Recode your program to ensure that the name matches a
created element.

NOSUCHNODE,

no such node while stopping queue 'queue-name' continuing to
stop other queues

Facility: JBCUPGRAD, Queue Upgrade Utility
Explanation: This error occurred during a $SNDJBC system service call
attempting to reset the queue. The specified queue is on a node other than
the node on which the upgrade procedure is being executed.
User Action: Be aware that queue is in an inconsistent state.

2-108

Messages

NOSUCHNODE,

remote node is unknown or not reachable

Facility: JBC, Job Controller
Explanation: A DCL command such as START/QUEUE was executed, or a
call to the $SNDJBC system service was made that requires the job controller
on one node of a cluster to communicate with the job controller on another
node to perform the requested operation. This condition indicates that the
remote job controller could not be reached because an invalid node name
was specified, the remote node is not reachable, or the job controller on the
remote node is not running.
User Action: Check the node name specified and verify that the remote node
is currently in the cluster, then retry the operation.
NOSUCHNODE,

remote node 'node-name' not known or unavailable.

Facility: VMSINSTAL, Install Procedures
Explanation: You are trying to install a product on a remote node that is
either unknown or unavailable.
User Action: Specify an existing node name or try the installation again
when the node becomes available.
NOSUCHNODE,

specified node does not exist

Facility: SYSTEM, VMS System Services
Explanation: The node name portion of a file or task specification refers to a
node that is unknown to the network ACP.
User Action: Check the node name specification. Verify the status of the
network and available nodes with the DCL command SHOW NETWORK.
NOSUCHOBJ,

network object is unknown at remote node

Facility: SYSTEM, VMS System Services
Explanation: An attempt is made to initiate a DECnet-VAX logical link
connection. The target object of the connect could not be found on the
specified node. The object name or object number is unknown, or the
command file used to start the object could not be found.
User Action: Notify the system manager of the remote node. Refer to the
VMS Networking Manual for additional information.
NO_SUCH_PARTY,

no such party in this application

Facility: PPL, Parallel Processing Facility
Explanation: The specified participant does not exist in this application.
User Action: Recode your program to ensure that the correct participant is
specified in the call to this routine.
NOSUCHQUE,

no such queue

Facility: JBC, Job Controller
Explanation: The specified queue does not exist. In a wildcard $GETQUI
operation, no more queues matching the specified selector exist.
User Action: None.

2-109

Messages

NOSUCHRQST,

no such request

Facility: OPCOM, Operator Communication
Explanation: A DCL command REPLY specified a nonexistent message
identification number.
User Action: Verify the message identification number displayed in the
message; reenter the command with the correct message number. If the
request is canceled by the user who issued it, no action is necessary.
NOSUCHRTN,

unknown CLI routine 'routine-name'

Facility: CDU, Command Definition Utility
Explanation: You specified a routine name instead of an object module in
your CLD file when generating CLI tables.
User Action: Remove the routine name from the CLD file.
NOSUCHRVN,

/VOLUME = 'number' invalid, volume set contains 'number'
volumes

Facility: BACKUP, Backup Utility
Explanation: The value specified for the /VOLUME 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, VMS 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.
NOSUCHSERV,

service name does not exist

Facility: LATCP, LAT Control Program
Explanation: You attempted to use the SET command to modify a service
not previously set up with a CREATE command.
User Action: Use the SHOW CHARACTERISTICS command to look at the
services defined for your node. Use the CREATE SERVICE command to
create the service (up to 8 allowed) for your node. Reenter the command.
NOSUCHSYM,

no such symbol

Facility: LIB, Library Facility
Explanation: You specified an undefined symbol.
User Action: Retry the operation specifying a defined symbol.

2-110

Messages

NOSUCHSYM,

no such symbol

Facility: P ATCR Patch Utility
Explanation: A symbol is specified that is not contained in the PATCH
symbol table.
User Action: Use the PATCH Utility command SET MODULE to bring local
symbols into the PATCH symbol table.
NOSUCHTPT,

no such tracepoint

Facility: DEBUG, VMS Debugger
Explanation: The CANCEL TRACE command specified an address that is not
the address of a tracepoint.
User Action: Use the SHOW TRACE command to display the current
tracepoints and then cancel any that you want to cancel.
NOSUCHUSER,

Facility: SYSTEM, VMS System Services
Explanation: An attempt is made to initiate a DECnet-VAX logical link
connection. The supplied access control string is not recognized at the
remote node. In particular, the username, password, or account field is not
recognized.
User Action: The access control string specified is incorrect. If default access
control is specified, notify the system manager that the DECnet configuration
database needs to be updated.
This error can be returned if the specified access control string is not
recognized (for example, no record in the UAF), is too long, or contained
illegal characters.
Refer to the VMS Networking Manual for additional information.
NOSUCHUSER,

user 'username' not currently logged in

Facility: SHOW, SHOW Command
Explanation: When using the SHOW USER command, you specified a user
who is not currently logged in.
User Action: None.
NOSUCHUSR

no such user 'username'

Facility: MAIL, Mail Utility
Explanation: You attempted to send a message to a user that does not exist
as an authorized user of the computer system. If you attempted to send the
message to mutiple users and at least one is authorized, this message appears
for each unauthorized user, followed by the question: "Do you want to send
it anyway (Y /N)?"
User Action: Reenter the command and specify a valid username. If you are
asked if you want to send the message anyway, respond Y (yes) or N (no).

2-111

Messages

NOSUCHVERB,

the CU table does not contain verb name 'verb-name'

Facility: CDU, Command Definition Utility
Explanation: The verb you tried to delete is not defined in the current CU
table.
User Action: Make sure that the syntax is correct and try to delete the verb
again.

NOSUCHWPT,

no such watchpoint

Facility: DEBUG, VMS Debugger
Explanation: The CANCEL WATCH command specified an address that is
not the address of a watchpoint.
User Action: Use the SHOW WATCH command to display the current
watchpoints and then cancel any that you want to cancel.

NOSUMM,

an input file may be specified only when /SUMMARY is present

Facility: MONITOR, Monitor Utility
Explanation: A list of files is specified on the /INPUT qualifier, indicating a
multifile summary request, but the /NOSUMMARY qualifier is also present,
explicitly or implicitly. A list of files may be specified only for a multifile
summary request.
User Action: If a multifile summary is desired, reenter the MONITOR
request, specifying the /SUMMARY qualifier. If a multifile summary is not
desired, reenter the MONITOR request specifying the /INPUT qualifier with
a single file.

NOSYMBOL,

symbol 'xxx' is not in the symbol table

Facility: PATCH, Patch Utility and DEBUG, VMS Debugger
Explanation: The symbol 'xxx' cannot be located in the utility's symbol table.
This can be caused when the module that defines the symbol has not been
added to the utility's symbol table, or when a symbol name that is not in the
image has been entered.
User Action: Add the required module to the utility's symbol table with the
SET MODULE command or specify the correct symbol name.

NOSYMBOLS,

no 'block-type' symbols found to format this block

Facility: SDA, System Dump Analyzer
Explanation: SDA cannot locate the symbols needed to format a block as a
particular block type.
User Action: Use the SDA command READ to include the specific block type
symbols in the SDA symbol table.

2-112

Messages

NOSYMBOLS,

no global symbol table found in 'image-name'

Facility: LIBRAR, LIBRARY Command
Explanation: There is no symbol table in the shareable image.
User Action: The linker always produces a symbol table, even if it is empty.
If this error persists after relinking, submit a Software Performance Report
with the relevant files.
NOSYSACT,

no action on .SYS files

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility did not perform the requested action on
files with the file type SYS.
User Action: Normally no action is required, since SYS files get special
treatment. If it is desired to modify SYS files, reenter the command with the
/SYSTEM qualifier.
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.
NOSYSGBL,

operation requires SYSGBL privilege

Facility: SYSTEM, VMS System Services
Explanation: A command or program requested a system function that
requires SYSGBL privilege; the current process does not have this privilege.
User Action: If the message is in response to a command entered
interactively, verify that you have not used a command or a qualifier for
a particular command that requires a specific user privilege.
If the message occurs during the execution of a program, determine the
system service call that resulted in the error. Verify that you have not used
a service or an argument for a particular service that requires a user privilege
that you do not have.

operation requires SYSLCK privilege

Facility: SYSTEM, VMS System Services
Explanation: You tried to lock a systemwide resource when you did not have
SYSLCK privilege.
User Action: Ask the system manager for SYSLCK privilege; or remove the
LCK$M_SYSTEM flag.

2-113

Messages

NOSYSNAM,

operation requires SYSNAM privilege

Facility: SYSTEM, VMS System Services and JBC, Job Controller
Explanation: A command or program requested a system function that
requires SYSNAM privilege; the current process does not have this privilege.
User Action: If the message is in response to a command entered
interactively, verify that you have not used a command or a qualifier for
a particular command that requires a specific user privilege.
If the message occurs during the execution of a program, determine the

system service call that resulted in the error. Verify that you have not used
a service or an argument for a particular service that requires a user privilege
that you do not have.
In either case, correct the command or program so that you do not request
the privilege function. If you determine that you need the privilege for an
application, contact your system manager to obtain the necessary privilege.
NOSYSPRV,

operation requires SYSPRV privilege

Facility: SYSTEM, VMS System Services
Explanation: A command or program requested a system function that
requires SYSPRV privilege; the current process does not have this privilege.
User Action: If the message is in response to a command entered
interactively, verify that you have not used a command or a qualifier for
a particular command that requires a specific user privilege.
If the message occurs during the execution of a program, determine the

system service call that resulted in the error. Verify that you have not used
a service or an argument for a particular service that requires a user privilege
that you do not have.
In either case, correct the command or program so that you do not request
the privilege function. If you determine that you need the privilege for an
application, contact your system manager to obtain the necessary privilege.
Not enough SPTEs to take selective system dump memory dump

switching to complete

Facility: BUGCHECK, System Bugcheck
Explanation: When writing a selective dump (SYSGEN parameter
DUMPSTYLE set to 1), the VMS operating system needs to remap portions of
memory for easy access and for efficient writing of the dump file. The VMS
operating system requests 127 System Page Table Entries (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.

2-114

Messages

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.
User Action: None. The Backup Utility allows you to begin restore and
compare operations without mounting the first volume.
NOTALLPRIV,

not all requested privileges authorized

Facility: SYSTEM, VMS System Services
Explanation: You requested unauthorized privileges from $SETPRV. Only
authorized privileges will be granted.
User Action: If necessary, ask the system manager to grant you the
appropriate privileges.
NOTALLSYM,

unable to initialize symbols for default modules

Facility: PATCH, Patch Utility
Explanation: The PATCH symbol table did not have enough room to include
symbols for all the modules normally inserted into the table upon execution
of PATCH.
User Action: To make room for the new modules, enter the PATCH
command SHOW MODULE to determine which modules are in the symbol
table, then enter the PATCH command CANCEL MODULE specifying the
module names whose symbols are no longer required. Then reenter the
PATCH command SET MODULE.
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.

2-115

Messages

NOTAPEOP,

no tape operator

Facility: SYSTEM, VMS System Services
Explanation: An operation failed because no system operator is available to
satisfy a requirement for manual assistance; for example, to mount the next
volume in a multivolume tape file.
User Action: Ensure that the tapes were mounted on the original mount
request or run the job when an operator is present.
NOTARRAY, indexed variable is not an array
Facility: VAXTPU, VAX Text Processing Utility
Explanation: The variable being indexed is not an array.
User Action: Use indexing with array variables only.
NOTARRAY,

type of variable is not array

Facility: DEBUG, VMS Debugger
Explanation: The variable being treated as an array has not been defined as
one.
User Action: Check that the correct variable reference is being made.
NOTASSIGN,

queue not assigned

Facility: JBC, Job Controller
Explanation: The specified queue cannot be deassigned because it is not
assigned.
User Action: None.
NOTASTRUCT,

'symbol-name' was not declared as a structure

Facility: DEBUG, VMS Debugger
Explanation: A VAX BLISS-32 structure reference specified a symbol
'symbol-name' that was not declared a structure.
User Action: Reenter the command with a valid symbol reference.
NOT_A_TERM,

pasteboard attached to a device that is not a terminal

Facility: SMG, Screen Management Facility
Explanation: This is an informational message stating that the pasteboard
has been created, but that the output device is not a terminal.
User Action: None.
NOT_A_TRM,

device is not a terminal

Facility: DTK, DECtalk Facility
Explanation: This is an informational message telling you that the output
device is not a terminal.
User Action: None.

2-116

Messages

NOT_AVAILABLE , requested resource not available now
Facility: PPL, Parallel Processing Facility
Explanation: Success status returned when the user requests immediate
nonblocking access to a resource that is not available.
User Action: Continue normally.
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 corrupted. The save set data is lost.
User Action: None.
NOTBOOCAP, not a boolean capability
Facility: SMG, Screen Management Facility
Explanation: The Termtable compiler expected a Boolean capability name
but encountered something else.
User Action: Check your terminal definiton. Perhaps you misspelled the
Boolean capability name or omitted another statement such as STRING or
NUMERIC which would have terminated Boolean capabilities.
NOTCLASS,

'device-name' not a 'type' device, type is 'type'

Facility: SHOW, SHOW Command
Explanation: The specified device is not the type of device that you specified
in the command line.
User Action: None.
NOTCMPL T,

'input-filespec' not completely copied

Facility: Shared by several facilities
Explanation: A copy operation began but did not finish. This message is
accompanied by a VMS RMS message indicating the reason for the failure.
User Action: Take corrective action based on the accompanying message.
Use the DCL command TYPE or DUMP to verify the contents of the output
file, and delete the output file before reentering the command.
NOTCOM,

BATCH mode can only be used for .COM files

Facility: START, 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.

2-117

Messages

NOTCOPIED,

'input-filespec' not copied

Facility: Shared by several facilities
Explanation: A requested input file could not be copied. This message is
usually accompanied by a VMS RMS message indicating the reason for the
failure.
User Action: Take corrective action based on the accompanying message.

NOTCOPIED,

file 'filename' not copied to 'filespec'

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility did not copy a file.
User Action: This message will be followed by a message describing the
actual reason the copy could not be done. Take corrective action based on the
following message.

NOTCOP_RETRY,

error copying 'filename', will retry

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility encountered an error while copying the
file, but after taking corrective action EXCHANGE will retry the copy.
User Action: This is most likely due to EXCHANGE discovering a bad block
on a volume, and EXCHANGE will try again to copy the file to a good space
on the volume.

NOTCREATOR,

request denied, user is not on creator port

Facility: SYSTEM, VMS System Services
Explanation: A shared memory global section may be deleted or updated
only by a process running on the same processor as the creator of the section.
If the processor becomes inoperative, no one owns the section.
User Action: Enter the request from the creator's processor. After a processor
becomes inoperative, it will be necessary to reboot and reinitialize the shared
memory in order to delete those sections without owners.

NOTCURPC,

target of EXAMINE/OPERANDS is not the current PC results may
be unexpected

Facility: DEBUG, VMS Debugger
Explanation: The operands being examined will probably give incorrect
results, most likely because the context for the instruction is not set up
properly. Specifically, the values of registers used in address computations
depend on the previous series of instructions being executed, which is not
done in this case.
User Action: Only use EXAMINE/OPERANDS with .0\ %PC.

2-118

Messages

NOTDDBDDB,

corrupted DDB list

illegal character in decimal string

Facility: MACRO, VAX MACRO Assembler
Explanation: A decimal string contained a character other than the digits 0
through 9 and a leading plus or minus sign.
User Action: Correct the syntax of the decimal string.
NOTDEFINABLE,

that key is not definable

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The key that you tried to define using the built-in procedure
DEFINE_KEY is not a definable key.
User Action: Use a definable key as outlined in the description of the
DEFINE_KEY built-in procedure in the VAX Text Processing Utility Manual.
NOTDELETED,

file filename not deleted
1

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility did not delete the specified file.
User Action: This message will be followed by another message giving the
reason why the file could not be deleted. Take corrective action based on the
second message.
NOTDELETED,

purging a record not marked as deleted

Facility: VAXTPU, VAX Text Processing Utility
Explanation: An internal VAXTPU failure occurred.
User Action: Submit a Software Performance Report.
NOTDIR,

file is not a directory

Facility: SET, SET Facility
Explanation: The specified file is not a directory file.
User Action: Reenter specifying an existing directory file.

2-119

Messages

NOTDISCON,

terminal is not disconnectable-explicitly specify LOGOUT

Facility: CU, Command Language Interpreter (DCL)
Explanation: An attempt has been made to disconnect a terminal that has
not been set as disconnectable from the current process. A disconnect under
these circumstances would log out the user and, therefore, is not permitted.
User Action: Either explicitly log out or set the terminal as disconnectable by
using the SET TERMINAL/PERMANENT /DISCONNECT command and try
again.
NOTDISK,

device must be a Files-11 format disk

Facility: SET, SET Facility
Explanation: The operation that you are trying to perform requires a Files-11
format disk. The device that is specified does not meet these requirements.
For example, this message is produced when you enter the SET VOLUME
command to a tape or terminal. The SET VOLUME command only accepts
Files-11 devices.
User Action: Make sure that the device meets the requirements of a Files-11
format disk before performing the operation.
NOTDONE,

'feature-name' not yet a supported feature

Facility: PATCH, Patch Utility and DEBUG, VMS Debugger
Explanation: The feature you attempted to use is recognized but not
implemented by PATCH. The name of the feature is indicated in the error
message. Or the DEBUG command DEPOSIT specified an instruction with a
literal that the debugger does not support at this time.
User Action: None.
NOTDONE,

command not complete

Facility: NCP, Network Control Program
Explanation: Not enough command information has been supplied to
determine the intent of the command. Prompting does not occur because
the command is included in a command procedure.
User Action: Modify the command in the command procedure to make it a
valid command.
NOTENABOPT,

not a legal ENABLE option

Facility: MACRO, VAX MACRO Assembler
Explanation: An argument to an .ENABLE or .DISABLE directive is not a
legal option.
User Action: Delete the option or replace it with a legal option.
NOTENUFOPR,

not enough operands supplied

Facility: MACRO, VAX MACRO Assembler
Explanation: The instruction requires more operands than were specified in
the statement.
User Action: Either add the operands or change the instruction.

2-120

Messages

NOTERM,

command device is not a terminal

Fadlity: REM, Set Host Facility
Explanation: SET HOST is invoked from a batch job. (SYS$COMMAND is
not a terminal.) You can invoke SET HOST only from interactive terminal
sessions.
User Action: None.
NOTERMS,

no such terminal

Facility: LATCP, LAT Control Program
Explanation: A nonexistent port is specified in a SHOW command.
User Action: Ensure that the port exists and reenter the command. Use the
SHOW PORTS command to look at the ports for your service node.
NOTERRORKEYWORD, error handler selector is not an error keyword
Facility: VAXTPU, VAX Text Processing Utility
Explanation: The specified error handler selector is not an error keyword.
User Action: Specify only error keywords as error selectors.
NOTFCBFCB,

FCB linkage broken

Bad FCB pointer in window

2-121

Messages

NOTFCPWCB,

Not FCP window in IRP

NOTFILEDEV,

device is not file structured

Facility: Shared by several facilities
Explanation: A file specification containing a directory, or file name and/or
file type is used· for an I/ 0 operation for a device that does not support
random access, for example, a line printer.
User Action: Verify the device name and the file specification; if a logical
name is specified, ensure that the correct equivalence name is assigned.
Correct the source program or reenter the command, as applicable.

NOTFOU,

not found

Facility: LIB, Library Facility
Explanation: LIB$FIND_VM--20NE could not locate another VM zone.
This message is a success status.
User Action: None.

NOTFOUND,

specified entry not found

Facility: ERF, Error Log Utility
Explanation: No entries matching the specified selection criteria were found.
User Action: None.

NOTFOUND,

no messages containing 'text' found

Facility: MAIL, Mail Utility
Explanation: You entered a DCL command SEARCH specifying text to be
found in a message. This text is not found.
User Action: Attempt to search for different text.

NOTFR,

no transfer address

Facility: CLI, Command Language Interpreter (DCL)
Explanation: The image file does not have a transfer address.
User Action: Check that the source program has specified a transfer address
and, if necessary, reassemble and relink the program.

2-122

Messages

NOTFROMLAT,

Unable to shut down LAT from a LAT terminal

Facility: LATCP, LAT Control Program
Explanation: You entered a LATCP STOP NODE command from a LAT
terminal.
Explanation: Reenter the command from a console on your service node.

NOTGENDEV,

not a generic device

Facility: MOUNT, Mount Utility
Explanation: You specified an invalid generic device.
User Action: Retry the operation specifying a valid generic device.

NOTHEN,

IF or ON statement syntax error-check placement of THEN keyword

Facility: CLI, Command Language Interpreter (DCL)
Explanation: The syntax of an IF or an ON statement is incorrect.
User Action: Correct the syntax of the statement by including the THEN
statement in the proper place.

NOTHLPLIB,

not a HELP library

Facility: LBR, Librarian Subroutine Package
Explanation: The library specified in LBR$GET_HELP is not a help library.
User Action: Determine that the library is a help library before calling the
routine; specify the correct library name.

NOTIDFMT,

ID name parameter does not translate to ID format

Facility: AUTHORIZE, Authorize Utility
Explanation: The identifier name that you specified does not translate to
a corresponding value in general identifier format. Identifier name values
translate to either general identifier format or UIC format. General identifier
names may be 1 through 31 alphanumeric characters and are stored with an
integer value in the range of 32,768 to 268,435,455. General identifiers are
created by the AUTHORIZE command ADD/IDENTIFIER.

When you use the AUTHORIZE command GRANT/IDENTIFIER, the first
identifier you specify must be in general identifier format. In other words,
you cannot grant a UIC-format identifier to another UIC-format identifier.
User Action: Determine why the identifier name is not a general ID. You can
display an identifier name and its corresponding value with the AUTHORIZE
command SHOW /IDENTIFIER. To change the value of an identifier name,
use the AUTHORIZE command MODIFY /IDENTIFIER.

NOTIDX, output file is not an indexed file
Facility: CONVERT, Convert Utility and CONVERT, Convert/Reclaim
Utility
Explanation: You specified the /MERGE qualifier and the output file is not
an indexed file.
User Action: Specify /NOMERGE and try again.

2-123

Messages

NOTIFY,

/NOTIFY not allowed-do not use with /WAIT or in batch jobs

Facility: CLI, Command Language Interpreter (DCL)
Explanation: /NOTIFY should only be used when you specify the /WAIT
qualifier and when the SP AWN command is executed from within a
noninteractive process.
User Action: Do not use /NOTIFY.
NOTIMGLIB,

file 'filename' is not a shareable image symbol table library

Facility: LINK, Linker Utility
Explanation: The system library IMAGELIB is found, but is not a shareable
image library.
User Action: Correct the file name and relink.
NOTIMP,

not implemented

Facility: Shared by several facilities
Explanation: You tried to use a call, routine, or feature that is not
implemented in this version.
User Action: Use a higher version of the routine or feature, or code your
program to eliminate this call.
NOT-1MPL,

function not implemented for this object

Facility: SMI, System Management Intergator/Server
Explanation: Internal error. The function you requested of an SMI object is
not defined.
User Action: Submit a Software Performance Report showing the exact
sequence of SYSMAN commands leading to the error.
NOTIMPLAN,

'expression-type' is not implemented at command level

Facility: DEBUG, VMS Debugger
Explanation: The 'expression-type' is not supported at this type.
User Action: Specify a type of expression that the debugger supports.
NOTIMPOPCODE,

opcode in delayed work queue not implemented

Facility: VAXTPU, VAX Text Processing Utility
Explanation: An internal VAXTPU failure occurred.
User Action: Submit a Software Performance Report.
NOTINANIF,

statement outside condition body

Facility: MACRO, VAX MACRO Assembler
Explanation: A JF_FALSE, .IF_TRUE, .ILTRUE_FALSE, .IFF, .IFT, or .IFTF
subconditional directive is not in a conditional assembly block.
User Action: Replace the subconditional directive with a conditional directive
or delete the subconditional directive.

2-124

Messages

NOTINITED,

LAT terminal port driver controller init not called

Facility: LATCP, LAT Control Program
Explanation: The LAT port driver cannot start because it is not properly
initialized.
User Action: Refer to the SYS$MANAGER:LTLOAD.COM command
procedure that is included with your LAT /VMS distribution software.
NOTINMACRO,

statement not in MACRO body

Facility: MACRO, VAX MACRO Assembler
Explanation: A .NARG, .ENDM, or .ENDR directive is used outside the
context of a macro.
User Action: Correct the code.
NOTINPHYS,

'location' not in physical memory

Facility: SDA, System Dump Analyzer
Explanation: The memory location you requested as a parameter to the SDA
command EXAMINE is not in physical memory when the system failed.
User Action: Reenter the command, specifying another address.
NOTINSTALL,

writeable shareable images must be installed

Facility: SYSTEM, VMS System Services
Explanation: Writable shareable images must be installed.
User Action: Install the shareable image specifying /SHARE/WRITE.
NOTINTBLSZ, block size is greater than 2048
Facility: SYSTEM, VMS System Services
Explanation: Your block size is greater than 2048 bytes (the default).
User Action: For a block size greater than 2048 bytes, you must specify the
number of blocks required with the /BLOCK qualifier as shown below:
MOUNT/BLOCK=n

NOTIRPAQB,

Not IRP pointer in AQB

2-125

Messages

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.

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.

NOTLABELMT,

tape is not labeled

Facility: SYSTEM, VMS System Services
Explanation: A request to read a tape failed because the tape does not have
standard labels.
User Action: Verify the tape volume. Mount the tape as a foreign tape, if
necessary, to read it. If the tape is to be rewritten, initialize it before retrying
the program.

NOTLEARNING,

you have not begun a learn sequence

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The built-in procedure LEARN _END executed without the
built-in procedure LEARN _BEGIN preceding it.
User Action: You must start a learn sequence before you can save keystrokes.

NOTLGLISOP,

not a legal listing option

Facility: MACRO, VAX MACRO Assembler
Explanation: The argument to a .SHOW, .NOSHOW, .LIST, or .NLIST
directive is not a legal option.
User Action: Delete the illegal option or replace it with a legal option.

2-126

Messages

NOTLKB,

Structure is not an LKB

LAT terminal port driver (LTDRIVER) is not loaded

Facility: LATCP, LAT Control Program
Explanation: You attempted to start the LAT port driver before loading the
driver with the SYSGEN CONNECT command.
User Action: Use the SYSGEN CONNECT command to connect the LAT
port driver. Start the LAT port driver again. For information about using
the SYSGEN command, see the SYS$MANAGER:LTLOAD.COM command
procedure that is included with your LAT /VMS distribution software.
NOTLOCKED,

'filename' not locked

Facility: SET, SET Facility
Explanation: The file that you want to lock is already locked.
User Action: None.
NOTLOCKED,

'filespec is not locked

Facility: Shared by several facilities
Explanation: The file specified by a DCL command UNLOCK is not locked.
This message is informational.
User Action: None.
NOTMOD,

volume volume-name' not modified

Facility: SET, SET Facility
Explanation: The volume is not modified. This message is accompanied by
another message.
User Action: Take corrective action based on the accompanying message.
NOTMODIFIABLE,

attempt to change unmodifiable buffer 'string'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: You cannot change the specified buffer.
User Action: Use the SET (MODIFIABLE, ... ) built-in to allow
modifications.

2-127

Messages

NOTMODIFIED,

no pages in the section were modified

Facility: SYSTEM, VMS System Services
Explanation: The update request completed successfully without queueing
any I/O requests because no pages in the input address range had been
modified.
User Action: The operating system does not normally display this message;
the user program should be able to detect and respond to the condition.

NOTMOUNTED,

volume 'volume-name' has not been mounted on EXCHANGE

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility received a DISMOUNT command for a
volume which is not mounted.
User Action: Check the command for a misspelled device name.

NOTMPMBX,

operation requires TMPMBX privilege

Facility: SYSTEM, VMS System Services
Explanation: A command or program requested a system function that
requires TMPMBX privilege; the current process does not have this privilege.
User Action: If the message is in response to a command entered
interactively, verify that you have not used a command or a qualifier for
a particular command that requires a specific user privilege.
If the message occurs during the execution of a program, determine the

system service call that resulted in the error. Verify that you have not used
a service or an argument for a particular service that requires a user privilege
that you do not have.
In either case, correct the command or program so that you do not request
the privileged function. If you determine that you need the privilege for an
application, contact your system manager to obtain the necessary privilege.
NOTMTLMTL,

Corrupted mounted volume list

NOTNEG,

qualifier or keyword not negatable-remove "NO" or omit

Facility: CU, Command Language Interpreter (DCL)
Explanation: The word "NO" preceded a qualifier or keyword, but the
qualifier or keyword cannot be specified as a negative.
User Action: Use the DCL command HELP or refer to the VMS DCL
Dictionary for a list of negatable qualifiers and keywords.

2-128

Messages

NOTNETDEV,

not a network communication device

Facility: SYSTEM, VMS System Services
Explanation: The device specified is not a network communications device,
and the control function cannot be performed.
User Action: Check for a programming error. Verify that the device specified
in the queue IjO request is a valid communications device.
NOTNUMCAP,

not a numeric capability

Facility: SMG, Screen Management Facility
Explanation: The Termtable compiler expected a numeric capability name
but encountered something else.
User Action: Check your terminal definition. Perhaps you have misspelled
the numeric capability name or omitted another statement, such as STRING
or BOOLEAN which would have terminated numeric capabilities.
NOTOBJLIB,

file 'filename' is not an object library

Facility: LINK, Linker Utility
Explanation: The specified file is not an object library. The linker processes
only object and shareable image libraries.
User Action: Specify only object or shareable image libraries.
NOTOBJLIB,

library 'library-name' is not an object library

Facility: LIBRAR, LIBRARY Command
Explanation: An attempt is made to cross-reference a library or to use the
/REMOVE qualifier in a macro, help, or text library.
User Action: Reenter the command line, specifying an object library that
contains the requested symbol.
NOTODS2,

'qualifier' qualifier invalid on Files-11 Structure Level 1 disk

Facility: SET, SET Facility
Explanation: The specified qualifier is not valid for a Files-11 Structure Level
1 volume, file, or directory.
User Action: Reenter the command specifying a valid qualifier.
NOTONSCREEN,

text cannot be scrolled unless window is on screen

Facility: VAXTPU, VAX Text Processing Utility
Explanation: You are trying to use the built-in procedure SCROLL on a
window that is either not mapped to the screen, or is totally occluded by
other windows.
User Action: Map the window to the screen before using the built-in
procedure SCROLL.

2-129

Messages

NOTORIGSRC,

original version of source file not found file used is 'filespec'

Facility: DEBUG, VMS Debugger
Explanation: A source file was found for some module. But the revision date
and time or the file size indicates that this may not be the same version of the
file that was used in the original compilation of the module. This warning
message indicates that future source line displays from this source file may
not correspond to the actual source used to compile the module.
User Action: None, unless the original source is available. Then you can use
the SET SOURCE command to indicate the location of the source to DEBUG.
NOTP ARAM,

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 VMS or
created by the SYSGEN command WRITE in SYSGEN.
NOTPASTED,

given display is not pasted to given pasteboard

Facility: SMG, Screen Management Facility
Explanation: An attempt is made to unpaste or move a display that is not
pasted to the specified pasteboard.
User Action: Check that you are referencing the correct virtual display.
Verify that the display has not been unpasted or that you forgot to paste it.
NOTPATADR,

patch address is 'addrl' not 'addr2'

Facility: PATCH, Patch Utility
Explanation: You typed the incorrect starting address of the patch area.
User Action: To determine the correct starting address, enter either the
PATCH command SHOW PATCH_AREA or the PATCH command ALIGN
/BYTE. When you enter the PATCH command ALIGN/BYTE, PATCH
defines a symbol as the current starting address.
NOTPCB,

Structure not PCB

2-130

Messages

NOTPRINTED,

failed to queue spool file for print

Facility: SYSTEM, VMS System Services
Explanation: An error occurred while an implicitly spooled file is queued for
print. The file has not been printed and the data is lost.
User Action: The system manager should ensure that the job controller
works correctly and that the printer" or terminal is spooled to the correct
queue.

NOTPSECOPT,

not a valid PSECT option

Facility: MACRO, VAX MACRO Assembler
Explanation: The attribute specified in the .PSECT directive is invalid.
User Action: Delete the invalid attribute or replace it with a valid one.

NOTPSECT,

relocation base set to other than psect base in module 'modulename' file 'filename'

Facility: LINK, Linker Utility
Explanation: An object module specified other than a psect base in a set
relocation base command.
User Action: Submit a Software Performance Report. Include the appropriate
language compiler in the report.

NOTPTR,

variable must be of pointer or file type

Facility: DEBUG, VMS Debugger
Explanation: The variable should be a pointer or a file type.
User Action: Specify a variable of pointer or file type.

NOTQUEUED,

request not queued

Facility: SYSTEM, VMS System Services
Explanation: The $ENQ system services request, specifying the flag bit
LCK$M_NOQUEUE, could not be granted.
User Action: Wait and retry the operation. ·

NOTQUO,

unquoted argument not allowed in ASCII or INSTRUCTION modes

Facility: PATCH, Patch Utility
Explanation: While in ASCII or INSTRUCTION mode, you entered an
argument not enclosed within matching apostrophes or quotation marks.
User Action: Add matching apostrophes or quotation marks to your
argument and reenter.

NOTRACES,

no tracepoints are set, no opcode tracing

Facility: DEBUG, VMS Debugger
Explanation: There are no tracepoints or opcode tracing set. This message is
informational.
User Action: None.

2-131

Messages

NOTRAN,

logical name cannot be translated

Facility: INIT, INITIALIZE Command and 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.
NOTRAN,

no string translation performed

Facility: SYSTEM, VMS System Services
Explanation: A request to translate a logical name returned with no
translation performed. The system returns the input logical name string
as the equivalence name string. (Because this is a success message, it is not
normally displayed.)
User Action: Note the condition. Modify the source program, if necessary, to
detect and respond to the condition.
NOTRAN,

no translation for logical name 'name'

Facility: SHOW, SHOW Command
Explanation: There is no translation for the specified logical name.
User Action: None.
NOTREADIN,

you are not reading a message

Facility: MAIL, Mail Utility
Explanation: The MAIL command you typed, (DELETE, FILE, FORWARD,
PRINT, or REPLY) is appropriate only when you are reading a message.
User Action: Read the desired message using the MAIL command READ and
then enter the appropriate command in response to the MAIL> prompt.
NOTRELVOL,

relative volume 'nnn' not on device

Facility: MOUNT, Mount Utility
Explanation: Each volume in a volume set has a relative number beginning
with one. 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.
NOTRENAMED,

'filename' not renamed

Facility: RENAME, RENAME Command
Explanation: The specified file is not renamed.
User Action: Correct the error according to the accompanying message.

2-132

Messages

NOTRES,

process swapped out

Facility: SDA, System Dump Analyzer
Explanation: This message occurs if the process name specified in a SHOW
PROCESS or SET PROCESS command represents a process that is swapped
out of the balance set when the system failed.
User Action: None.
NOTRMSOUT,

RMS is not being used to perform output

Facility: SMG, Screen Management Facility
Explanation: SMG$SNAPSHOT is used with files and unknown devices to
capture the contents of the pasteboard at various times. If SMG$SNAPSHOT
is called for a pasteboard associated with a video terminal, then it takes no
action and returns this informational message.
User Action: None.
NOTRULUCB,

Bad RUL pointer in UCB (journaling)

Not RVT pointer in VCB

the markers are not in the same buffer

Facility: VAXTPU, VAX Text Processing Utility
Explanation: You passed markers to the built-in procedure CREATE_
RANGE that are not in the same buffer. A range cannot span buffers.
User Action: Create the range with markers in the same buffer.

2-133

Messages

NOTSAMEDEV,

cannot RENAME to a different device

Facility: RENAME, RENAME Command
Explanation: An attempt is made to rename a file name from one device to
another.
User Action: Use the DCL command COPY instead of the DCL command
RENAME.
NOTSAMEDEV,

input and output must be same device for boot copy

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility encountered an attempt to COPY /BOOT
between devices.
User Action: Reenter the command, specifying the same device for input and
output. You can also omit the name of the output device, since EXCHANGE
will assume you mean the same as the input device.
NOTSAVED,

'LMB-name' not saved in the dump file

Facility: SDA, System Dump Analyzer
Explanation: Information corresponding to a Logical Memory Block (LMB)
has not been saved in this subsetted dump file. The dump file may or may
not be useful for analysis depending on which LMB was not saved. If the
SDA image retains control after the error, then some analysis is possible, but
some information might not be available in the dump file.
User Action: None. The dump file may not be useful for analysis.
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.
NOTSEQ,

output file is not a sequential file

Facility: CONVERT, Convert Utility
Explanation: You specified the/ APPEND qualifier and the output file is not
sequential.
User Action: Specify /NOAPPEND and try again.
NOTSET,

LAT terminal port driver multicast data not set

Facility: LATCP, LAT Control Program
Explanation: The LATCP Utility did not attempt to set the LTDRIVER
parameter area because of a previous error.
User Action: Correct the error condition that prevented the parameter area in
LTD RIVER from being initialized.

2-134

Messages

NOTSET,

process not set to /CPU=[NO]ATTACHED

Facility: Shared by several facilities
Explanation: The process is already in the requested state.
User Action: None.
NOTSHRIMG,

file 'filename' is not a shareable image

Facility: LIBRAR, LIBRARY Command
Explanation: The file given as input to a shareable image library is not a
shareable image.
User Action: Relink the image using the LINK/SHARE option.
NOTSPLADDR,

memory at 'address' does not begin a spin lock structure

Facility: SDA, System Dump Analyzer
Explanation: The memory at the specified address to the SDA command
SHOW spin locks does not contain the type field corresponding to a spin lock
structure.
User Action: Reenter the command; specify a different address.
NOTSQDEV,

not a sequential device

Facility: SYSTEM, VMS System Services
Explanation: You tried sequential access with a random access device.
User Action: Use random access with this device.
NOTSTARTED,

LAT terminal port driver not started

Facility: LATCP, LAT Control Program
Explanation: Your attempt to start the LAT port driver is unsuccessful.
User Action: Determine the specific cause of the failure and reenter the
command.
NOTSTOPPED,

LAT terminal port driver not stopped

Facility: LATCP, LAT Control Program
Explanation: A STOP NODE command failed to stop the LAT protocol.
User Action: Determine the specific cause of the failure and reenter the
command.
NOTSTRCAP,

not a string capability

Facility: SMG, Screen Management Facility
Explanation: The Termtable compiler expected a string capability name but
encountered something else.
User Action: Check your terminal definition. Perhaps, you have misspelled
the string capability name or omitted another statement such as BOOLEAN
or NUMERIC which would have terminated string capabilities.

2-135

Messages

NOTSTRUCTl,

qualifiers not available with structure level 1

Facility: INIT, INITIALIZE Command
Explanation: This message is generated by the DCL command INITIALIZE.
Qualifiers were used requesting features not available with Files-11 Structure
Level 1, for example, /CLUSTER and /DATACHECK.
User Action: Use structure level 2 or omit the qualifiers.
NOTSYSTEM,

you are not logged in to the SYSTEM account.

Facility: VMSINSTAL, Install Procedures
Explanation: When VMSINSTAL begins an installation, it makes sure that
you are logged in to the SYSTEM account. This check has failed.
User Action: You will be asked if you want to continue the installation.
DIGITAL recommends that you correct this situation before continuing.
NOTUCBIRP,

not UCB pointer in IRP

not UCB pointer in RVT

2-136

Messages

NOTUCBUCB,

corrupted UCB list

Facility: BUGCHECK, System Bugcheck
Explanation: The VMS 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, 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 on the BACKUP command
that produces the save set included with the SPR.)
NOTUCBWCB/Bad UCB pointer in window,
Facility: BUGCHECK, System Bugcheck
Explanation: The VMS 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, 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 on the BACKUP command
that produces the save set included with the SPR.)
NOTUICFMT,

user id parameter does not translate to UIC format

Facility: AUTHORIZE, Authorize Utility
Explanation: The user specification in your command does not translate to a
UIC identifier (an identifier in UIC format).
User Action: Determine why the user specification is not a DIC-format ID.
You can display user names and their corresponding UIC values by using the
AUTHORIZE command SHOW.
NOTUQPORT,

device not connected to a UNIBUS/Q-bus port

Facility: SET, SET Facility
Explanation: You entered the DCL command SET DEVICE/DFAG for
a device other than a UDASO controlled disk, a RC25, or a TU81. This
command is valid only for these devices.
User Action: Check the device number. Make sure it is one of the devices
listed above.
NOTVALID, information not in physical memory
Facility: SDA, System Dump Analyzer
Explanation: The virtual address you specified is not currently in physical
memory or is not in physical memory at the time of the dump. You are not
able to examine the address.
User Action: None.

2-137

Messages

NOTVALLEN,

fixed record length of 'numeric-string' is too large

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility discovered a value on a /RECORD_
FORMAT=(FIXED=n) command which is too large.
User Action: Reenter the command with a smaller record length.

NOTVCBUCB,

not VCB pointer in UCB

NOTVOLSET,

volume is not part of a volume set

Facility: SYSTEM, VMS System Services
Explanation: An attempt is made to reference a specific volume in a volume
set, through the file ID or placement control, when the specified volume is
not part of a volume set.
User Action: Verify that the correct device name is specified or remove the
volume-specific reference.

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

2-138

Messages

NOTWCBIRP,

not WCB Pointer in IRP

corrupted WCB list

not yet implemented

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The built-in being used has not yet been implemented.
User Action: You must use a different built-in that has been implemented.
NOUNIQUE,

symbol 'symbol-name' is not unique

Facility: DEBUG, VMS Debugger
Explanation: The symbol specified was not in a default scope or was defined
in more than one scope.
User Action: Specify the scope of the symbol in a path name or change the
default scope.
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.

2-139

Messages

NOUPDATE,

no patch for update qualifier ECO level 'nn'

Facility: PATCH, Patch Utility
Explanation: When a command procedure is submitted for interactive or
batch execution (by typing PATCH/UPDATE= (eco-level, ... )), an ECO
level is specified that is not included in the command procedure.
User Action: Check your command procedure for correct ECO levels and
retry.
NOUSERNAME,

missing user name

Facility: AUTHORIZE, Authorize Utility
Explanation: The command you are using requires a user name. A user
name is the member name from the alphanumeric form of a user's UIC (user
identification code).
User Action: Reenter your command including a user name.
NOUSERNAME,

username must be supplied

Facility: MOM, Maintenance Operation Module
Explanation: In this LOOP NODE or LOOP EXECUTOR command, a user
name must be supplied.
User Action: Supply a user name with the LOOP command.
NOUSERPASS,

username and password must be supplied

Facility: MOM, Maintenance Operation Module
Explanation: In this LOOP NODE or LOOP EXECUTOR command, both a
user name and a password must be supplied.
User Action: Supply a user name and a password with the LOOP command.
NOUSERSPEC,

missing user specification

Facility: AUTHORIZE, Authorize Utility
Explanation: The command you are using requires a user specification. A
user specification may be a user name (for example, CAESAR), or a user
identification code (for example, [100,44]).
User Action: Reenter your command including a user specification.
NOUSRWCS,

no user WCS halt restart

2-140

Messages

NOVALATPC,

entity 'symbol-name' does not have a value at the current PC
(was optimized away)

Facility: DEBUG, VMS Debugger
Explanation: The value of the specified variable does not exist at this point
in the program's execution. For example, the variable might be assigned to a
register that is currently being used for some other purpose.
User Action: Retry the operation at a point in the program's execution when
the variable is being referenced.

NOVALPRS,

$SEARCH operation not preceded by valid $PARSE

Facility: RMS, VMS Record Management Services
Explanation: A VMS RMS wildcard $SEARCH operation was attempted with
no preceding valid $PARSE operation.
User Action: Verify that the sequence of VMS RMS service calls is coded
correctly and that the NAM block is not inadvertently modified during
execution of the program.

NOVALU,

value not allowed-remove value specification

Facility: CLI, Command Language Interpreter (DCL)
Explanation: A qualifier or keyword that does not accept a value is specified
with a value.
User Action: Use the DCL command HELP or refer to the VMS DCL
Dictionary for the correct syntax and reenter the command.

NOVALUE,

'keyword' keyword requires a value

Facility: Shared by several facilities
Explanation: The keyword indicated must be specified with a value.
User Action: Reenter the command; specify a value for the indicated
keyword.

NOVAL UE, 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.

NOVALUE,

reference does not have a value

Facility: DEBUG, VMS Debugger
Explanation: The command specified a reference that has no value.
User Action: Change the reference.

2-141

Messages

NOYER,

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.
NOVIRMEM,

error allocating virtual memory

Facility: DUMP, File Dump Utility
Explanation: The File Dump Utility encountered an error during an attempt
to allocate dynamic virtual memory. The accompanying message provides
additional information.
User Action: Correct the condition that caused the error and reenter
the command. The account's page file quota or the SYSGEN parameter
VIRTUALP AGECNT may need to be increased.
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
error in the Backup Utility; in this case, submit a Software Performance
Report.
NOVOLPRO,

operation requires VOLPRO privilege

Facility: SYSTEM, VMS System Services
Explanation: A command or program requested a system function that
requires VOLPRO privilege; the current process does not have this privilege.
User Action: If the message is in response to a command entered
interactively, verify that you have not used a command or a qualifier for
a particular command that requires a specific user privilege.
If the message occurs during the execution of a program, determine the
system service call that resulted in the error. Verify that you have not used
a service or an argument for a particular service that requires a user privilege
that you do not have.

no volumes are currently mounted

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility could not show mounted volumes,
because none were mounted.
User Action: Only use the EXCHANGE SHOW command if there is
something to show.

2-142

Messages

NOWATCHES,

no watchpoints are set

Facility: DEBUG, VMS Debugger
Explanation: No watchpoints are set. This message is informational.
User Action: None.
NOWATTAR,

cannot watch-protect target

Facility: DEBUG, VMS Debugger
Explanation: You are attempting to set a watchpoint on a location that is
either not in your program or is on the stack (Pl space). These two kinds of
locations cannot be watchpointed.
User Action: None, unless you specified the wrong location.
NOWBPT,

cannot insert breakpoint

Facility: DEBUG, VMS Debugger
Explanation: This message indicates an internal debugger error.
User Action: Submit a Software Performance Report.
NOWILD,

no wildcard permitted

Facility: Shared by several facilities
Explanation: Wildcards are not permitted in this context.
User Action: Respecify using exact file specifications.
NO_WINASSOC,

no viewport has been associated with the display

Facility: SMG, Screen Management Facility
Explanation: A viewport window is not associated with the virtual display.
User Action: Create a viewport on the virtual display.
NOWINDOW,

attempt to position the cursor outside all of the mapped windows

Facility: VAXTPU, VAX Text Processing Utility
Explanation: You can move the cursor only to a position inside a mapped
window.
User Action: Move the mouse inside a window, and attempt to position the
mouse again.
NOWOPCO,

cannot replace breakpoint with opcode

Facility: DEBUG, VMS Debugger
Explanation: This message indicates an internal debugger error.
User Action: Submit a Software Performance Report.

2-143

Messages

NOWORLD,

operation requires WORLD privilege

Facility: SYSTEM, VMS System Services
Explanation: A command or program requested a system function that
requires WORLD privilege; the current process does not have this privilege.
User Action: If the message is in response to a command entered
interactively, verify that you have not used a command or a qualifier for
a particular command that requires a specific user privilege.
If the message occurs during the execution of a program, determine the
system service call that resulted in the error. Verify that you have not used
a service or an argument for a particular service that requires a user privilege
that you do not have.

work files required, cannot do sort in memory as requested

Facility: SORT, Sort/Merge Utility
Explanation: The /WORK-FILES=O qualifier is specified indicating the data
would fit in memory, but the data is too large.
User Action: Either increase the working set quota, or allow the Sort Utility
to use two or more work files.
NOWRT,

cannot create writeable section to read-only file

Facility: SYSTEM, VMS System Services
Explanation: An image file that is read-only opened contains a writeable
section. You cannot create a writeable section to a read-only file.
User Action: Close and open the file correctly. If the Install Utility returns
this error, reenter the command but use the /WRITE qualifier in addition to
/SHARE qualifier.
NPK,

no primary key defined for indexed file
Facility: RMS, VMS Record Management Services
Explanation: A VMS RMS $CREATE service is executed for an indexed file
and no primary key XAB definition is provided.
User Action: Verify that the VMS RMS service is coded correctly.

NSADDR,

address 'addr' is not within image

Facility: PATCH, Patch Utility
Explanation: You specified an address outside the address range of the image
file.
User Action: Retry the operation specifying the correct address.

2-144

Messages

NSF,

.END LIST/.END NOTE not in same file as .LISTj.NOTE: 'string'

Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: You made an illegal attempt to start a list or note in one file
and end it in another.
User Action: End the list or note in the same file where you started it.
NTD,

files nested too deep: 'string'

Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: You attempted to nest .REQUIRE files more than 10 deep.
User Action: Reduce the number of nested .REQUIRE files.
NUDFENVS,

'number' undefined environments:

Facility: LINK, Linker Utility
Explanation: Undefined environments were encountered by the linker at the
end of Pass 1.
User Action: Ensure that all referenced environments are defined.
NUDFLSYMS,

'number' undefined module-local symbols:

Facility: LINK, Linker Utility
Explanation: Undefined module-local symbols were encountered by the
linker at the end of Pass 1.
User Action: Ensure that all referenced module-local symbols are defined.
NUDFSYMS,

'number' undefined symbols:

Facility: LINK, Linker Utility
Explanation: Undefined symbols were encountered by the linker. This
message is issued at the end of Pass 1 of the link.
User Action: Ensure that all symbols referenced are defined.
NULFIL,

missing or invalid file specification-respecify

Facility: CU, Command Language Interpreter (DCL)
Explanation: The command interpreter expected a file specification following
an execute procedure symbol (@ ), a prompting message, a plus sign ( + ), or a
comma (, ), but no file specification is entered.
User Action: Reenter the command; put the file specification in the proper
position.
NULIDX,

index is empty

Facility: LBR, Librarian Subroutine Package
Explanation: The specified index is found empty on a call to LBR$GET_
INDEX. Processing continues.
User Action: None.

2-145

Messages

NULLFILE,

file 'filespec' contains no records

Facility: SEARCH, SEARCH Command
Explanation: The specified file is empty. This may be because the file is
currently being written by another process. This message is informational.
User Action: None.
NULLPRI,

null primary block

Facility: FDL, Create/FDL Utility and FDL, Edit/FDL Utility
Explanation: You specified a primary that requires secondaries, but none
were given.
User Action: Specify secondaries for the primary.
NULLPRIV,

no privileges specified-no action taken

Facility: SYSMAN, Cluster System Management Utility
Explanation: A SET PROFILE command specified neither a change in
privileges nor a change in the default device or directory.
User Action: Reenter the command with the appropriate qualifiers.
NULLSTRING,

null string used

Facility: VAXTPU, VAX Text Processing Utility
Explanation: A null string was used where a non-null string is required.
User Action: Enter a non-null string.
NULSAVESET,

null save set name specified to RESTORE_SAVESET.

Facility: VMSINSTAL, Install Procedures
Explanation: A product installation procedure contained an incorrect call to
RESTORE_SAVESET.
User Action: Contact your DIGITAL field service representative.
NUMBER,

invalid numeric value-supply an integer

Facility: CU, Command Language Interpreter (DCL)
Explanation: A numeric value is specified for a DCL command that expects
values in certain radices, or interprets values within a particular context. For
example, the number 999 is entered when an octal value is required. Or an
alphabetic value is specified in a context that requires a numeric value, for
example, a file version number.
User Action: Use the DCL command HELP or refer to the VMS DCL
Dictionary for the legal values and reenter the command.

2-146

Messages

NUMELEMENTS,

number of elements incorrect for component

Facility: LIB, Library Facility
Explanation: You specified an incorrect number of elements for the
component.
User Action: Examine the arguments to LIB$INIT_DATE_TIME_CONTEXT.
Begin debugging procedures to verify and correct the problem.

Numeric value illegal
Facility: EDT, EDT Editor
Explanation: You specified a number that is too large for the command
specifier.
User Action: Reenter the command specifying a valid value.

Numeric value required
Facility: EDT, EDT Editor
Explanation: The command did not have a numeric value at the point of
the " in the command.
User Action: Reenter the command specifying a numeric value at the point
of the ".

NUM_KEY,

too many keys specified

Facility: SORT, Sort/Merge Utility
Explanation: Up to 255 key definitions are allowed. Either too many key
definitions have been specified or the NUMBER value is wrong.
User Action: Check your command string key field specifications.

NUMOPRNDS,

'xx' instructions must have 'nn' operands

Facility: PATCH, Patch Utility and DEBUG, VMS Debugger
Explanation: An operand is omitted from the MACR0-11 instruction. If the
debugger issues this message, a DEBUG command DEPOSIT specified the 'xx'
instruction with an incorrect number of operands. This instruction requires
'nnn' operands.
User Action: Reenter the command with the correct number of operands.

NUMTRUNC,

number truncated

Facility: PATCH, Patch Utility and DEBUG, VMS Debugger
Explanation: The PATCH Utility or the Debugger truncated a numeric data
entry because it exceeded the length of the data type.
User Action: None.

2-147

Messages

NUMVAL,

error code of 'xx' requesting update value

Facility: PATCH, Patch Utility
Explanation: A command interpreter callback request failed due to the error
code represented as 'xx'.
User Action: Retry the request using the correct error code (represented as
'xx').

NVROPRFAI,

the last NVR operation has failed

Facility: DTK, DECtalk Facility
Explanation: A NVR operation failure occurred since the DECtalk device was
turned on.
User Action: Check the DECtalk hardware.

OBJ,

invalid object identification
Facility: NCP, Network Control Program
Explanation: The identification of the object is not a valid object name.
User Action: Check the syntax rules for object identifiers, and reenter your
command with the correct object identifier.

OBJLOCKED,

object currently locked by another user

Facility: SYSTEM, VMS System Services
Explanation: An attempt is to modify the access control list (ACL) of an
object while another user is modifying the object's ACL.
User Action: Repeat the operation at a later time.

OBTEVT,

error when reading raw events

Facility: EVL, Event Logger
Explanation: NETACP returned an error while EVL is reading unprocessed
events. This message may be accompanied by a secondary message indicating
a system configuration or process quota problem with the EVL process.
User Action: Ensure that EVL has adequate quota and that the VMS system
is configured properly. The account under which EVL runs is specified in the
network Configuration Data Base.

OCCLUDED, built-in/keyword 'name' occluded by declaration
Facility: VAXTPU, VAX Text Processing Utility
Explanation: You declared a parameter, local, or constant that has the same
name as a built-in or keyword. Your declaration obstructs the built-in or
keyword.
User Action: None.

2-148

Messages

ODS2SAVE,

save set disk on 'device-name' must be structure level 2

Facility: BACKUP, 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.
OFFHOOK,

telephone is offhook (active)

Facility: DTK, DECtalk Facility
Explanation: This is an informational message telling you that the phone is
off the hook (a call is active).
User Action: None.
OFFLINE,

'device-name' : offline

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.
OK_ALK,

record is already locked

Facility: RMS, VMS Record Management Services
Explanation: A VMS RMS request to lock a record returns this success status
code when the specified record is already locked. This is a success status.
User Action: None.
OK_DEL,

deleted record successfully accessed

Facility: RMS, VMS Record Management Services
Explanation: A VMS RMS request to access a deleted record returns this
success status code when the specified record is accessed. This is a success
status.
User Action: None.
OK_DUP,

record inserted had duplicate key

Facility: RMS, VMS Record Management Services
Explanation: A VMS RMS $PUT or $UPDATE service completed
successfully. The record inserted or updated had one or more key values
that duplicated the values of other records. This is a success status.
User Action: None.

2-149

Messages

OK_IDX,

index update error occurred

Fadlity: RMS, VMS Record Management Services
Explanation: A VMS RMS $PUT or $UPDATE service completed
successfully. However, the index could not be completely updated. No
access paths to the record have been lost; access to the record will take
longer.
User Action: The status value (STV) field of the RAB contains the VMS RMS
error that occurred during index update. Take corrective action based on that
value. File reorganization with the CONVERT command is recommended to
improve performance.
OK_LIM,

retrieved record exceeds specified key value

Facility: RMS, VMS Record Management Services
Explanation: A VMS RMS $GET or $FIND request returns this success code
if the retrieved record exceeds the specified key value and if the RAB$V_LIM
option is specified. This is a success status.
User Action: None.
OK_NOP,

XAB not filled in for block I/O

Facility: RMS, VMS Record Management Services
Explanation: A VMS RMS $OPEN or $DISPLAY service that specified
block IjO access (BIO) completed successfully. However, one or more key
definition or allocation XABs were not filled in. This is a success status.
User Action: None.
OK_RLK,

record locked but read anyway

Facility: RMS, VMS Record Management Services
Explanation: A VMS RMS request to read a locked record completed
successfully. This is a success status.
User Action: None.
OK_RNF,

nonexistent record successfully accessed

Facility: RMS, VMS Record Management Services
Explanation: A VMS RMS request to access a nonexistent record completed
successfully. This is a success status.
User Action: None.
OK_RRL,

record locked against read but read anyway

Facility: RMS, VMS Record Management Services
Explanation: A VMS RMS request to read a record locked against read is
completed successfully. This is a success status.
User Action: None.

2-150

Messages

OK_WAT,

record locked after wait

Facility: RMS, VMS Record Management Services
Explanation: A VMS RMS request to access a record locked after wait
completed successfully. This is a success status.
User Action: None.
OLDINSCHK,

memory location 'addr' not equal to 'xx'

Facility: PATCH, Patch Utility
Explanation: The verification of the contents of the given address failed.
User Action: Reenter the PATCH command specifying the correct value.
OLDUBRARY,

old format library opened

Facility: LBR, Librarian Subroutine Package
Explanation: This success message is generated by the Librarian routines
when a library that is not in the current format is opened.
User Action: None.
OLDMISMCH,

old format library type mismatch

Facility: LBR, Librarian Subroutine Package
Explanation: The requested Version 1.0 library is a different type from the
type expected. Processing continues based on the actual library type.
User Action: None.
OLDTAB,

command tables have obsolete format-use SET COMMAND to
recreate

Facility: CU, Command Language Interpreter (DCL)
Explanation: CU encountered a command table with an obsolete format
while trying to automatically update it to the current format. The obsolete
command table must be manually updated.
User Action: Use Command Definition Utility command SET COMMAND to
recreate the tables.
OLDVALCHK,

memory location 'addr' not equal to 'xx'

Facility: PATCH, Patch Utility
Explanation: The verification of the contents of the given address failed.
User Action: Reenter the PATCH command specifying the correct value.

2-151

Messages

On output page pn; on input line 'ln' of page 'pn' of file 'filename'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: This is a standard error message line that specifies the location
of an error string. This message indicates the number of the page (pn) in the
output file affected by the error and the name of the input file (filename),
including the input page (pn) and the line number (ln) in which the error
occurred.
User Action: Find and correct the error string.
ONCOMD,

ON command too large-decrease the length of the THEN clause

Facility: CLI, Command Language Interpreter (DCL)
Explanation: The command action for an ON command in a command
procedure is too complex to be evaluated or too large to be stored.
User Action: Correct the command procedure simplifying the ON command
action.
ONDELRECLIST,

attempt to access a record on the deleted list

Facility: VAXTPU, VAX Text Processing Utility
Explanation: An internal VAXTPU failure occurred.
User Action: Submit a Software Performance Report.
ONEDELTIM,

at least one delta time is required

Facility: LIB, Library Facility
Explanation: The LIB$DATE_TIME routine requires at least one of the
inputs to be a delta time.
User Action: Examine each argument. Determine which argument is
incorrect and replace it with a delta time.
ONEENTQUE,

one entry in queue

Facility: LIB, Library Facility
Explanation: The procedure successfully completed. An entry is added to the
front of the queue. As a result, the queue contains one entry.
User Action: None.
ONEFl 1DEV,

both input and output must not be save sets

Facility: BACKUP, Backup Utility
Explanation: When you executed the BACKUP command, 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.

2-152

Messages

ONEFl 1OUT,

file-structured output must not be a list

Facility: BACKUP, Backup Utility
Explanation: The output specification for a copy, restore, or compare
operation without the /IMAGE qualifier is a list of file specifications.
(BACKUP does not accept this.)
User Action: Modify your output specification and reenter the command.
ONEIMGDEV,

/IMAGE input specification must not be a list

Facility: BACKUP, Backup Utility
Explanation: The specification for an input volume set to be processed with
the /IMAGE qualifier is a list of file specifications. (BACKUP does not accept
this.)
User Action: Modify your input specification and reenter the command.
ONELEARN,

cannot start a learn sequence while one is active

Facility: VAXTPU, VAX Text Processing.Utility
Explanation: You can create only one learn sequence at a time.
User Action: Terminate the current learn sequence before starting a new one.
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. (BACKUP does not accept this.)
User Action: Modify your specification and reenter the command.
ONERR,

invalid ON condition-use WARNING, SEVERE, ERROR or
CONTROL_Y

Facility: CU, Command Language Interpreter (DCL)
Explanation: The keyword specified in the DCL command ON to indicate
the condition is not recognized.
User Action: Correct the DCL command ON, using one of the keywordsCONTROL _ Y, WARNING, ERROR, or SEVERE_ERROR.
ONESELECT,

select already active, maximum 1 per buffer

Facility: VAXTPU, VAX Text Processing Utility
Explanation: You used the built-in procedure SELECT a second time within
the same buffer.
User Action: Set the previous select mark to 0 or delete the current select
range with the DELETE built-in procedure.

2-153

Messages

ONEVAL,

list of values not allowed-check use of comma (,)

Facility: CU, Command Language Interpreter (DCL)
Explanation: A qualifier, keyword, or parameter that accepts only a single
value is specified with multiple values.
User Action: Reenter the command specifying only one value.

ONHOOK,

telephone is onhook (inactive)

Facility: DTK, DECtalk Facility
Explanation: This is an informational message telling you that the phone is
on the hook (no call is active).
User Action: None.

ONLEVL,

invalid ON context-use only within command procedures

Facility: CU, Command Language Interpreter (DCL)
Explanation: An ON command is issued interactively. It can be issued only
from within a command procedure.
User Action: None.

ONOVF,

no room for ON command-symbol overflow, delete some symbols

Facility: CU, Command Language Interpreter (DCL)
Explanation: Symbol or keypad definitions have exhausted the command
interpreter's space for storing values.
User Action: If necessary, interrupt the command procedure with CTRL/Y
and stop its execution. Use the DCL commands SHOW SYMBOL and SHOW
KEY to determine how many global symbols and keypad symbols are defined;
delete unused symbols to recover symbol table space.
If the error occurs frequently, simplify the command procedure or procedures.

Use local symbols within procedures whenever possible.
OPCCUS,

opcode reserved to customer fault at PC = 'location', PSL = 'xxxxxxxx'

Facility: SYSTEM, VMS System Services
Explanation: An operation code beginning with AXFC is encountered during
execution of an image. This message indicates an exception condition and is
usually followed by a display of the condition arguments, registers, and stack
at the time of the exception.
User Action: Examine the PC and virtual address displayed in the message
to determine the instruction that caused the error.

OPCDEC,

opcode reserved to DIGITAL fault at PC = 'location', PSL = 'xxxxxxxx'

Facility: SYSTEM, VMS System Services
Explanation: The operation code at the indicated address is not known. This
message indicates an exception condition and is usually followed by a display
of the condition arguments, registers, and stack at the time of the exception.
User Action: Examine the PC and virtual address displayed in the message
to determine the instruction that caused the error.

2-154

Messages

OPEFAI,

operation failure 'error'

Facility: NCP, Network Control Program
Explanation: The requested operation failed for the reason identified in the
'error' part of the message.
User Action: Take corrective action based on the system-specific error
message.

OPEJBCMBX,

error opening job controller mailbox

Facility: JBC, Job Controller
Explanation: The job controller encountered an error assigning a channel to
its mailbox. The accompanying message provides additional information.
User Action: Take action based on the accompanying message.

OPENBITMAP,

error opening BITMAP.SYS, RVN 'n'

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility encountered an error during an attempt
to open the storage bit map file, [OOOOOO]BITMAP.SYS;l, on the specified
relative volume. The accompanying message provides additional information.
User Action: Correct the condition that caused the error and reenter the
Verify Utility command line.

OPENDIR,

error opening directory 'directory-name

Facility: BACKUP, Backup Utility and VERIFY, Verify Utility
Explanation: Either the Backup Utility or the Verify Utility encountered
an error during an attempt to open the specified directory file. The
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.

OPENDIR,

error opening parent directory for 'directory-name

Facility: SET, SET Facility
Explanation: A parent directory could not be opened.
User Action: Take corrective action based on the accompanying message.

OPENEXC,

error opening exception file filespec'

Facility: CONVERT, Convert Utility
Explanation: This message will be accompanied by an RMS message that
explains the error.
User Action: Correct the error described by the RMS message and try again.

2-155

Messages

OPENFDL,

error opening FDL file

Facility: FDL, Create/FDL Utility and FDL, Edit/FDL Utility
Explanation: This message will be accompanied by an RMS message that
explains the error.
User Action: Correct the error described in the RMS error message and try
again.

OPENFILE,

error creating event file 'file-id'

Facility: EVL, Event Logger
Explanation: An error occurred while creating an event file. All events
destined for that sink will be discarded. This message displays the name of
the file. This message is issued with an accompanying message.
User Action: Take corrective action based on the accompanying message.

OPENFILE, file ('file-id') 'filename' error opening file for read check
Facility: VERIFY, Verify Utility
Explanation: The Verify Utility encountered an error during an attempt
to open the specified file to execute the /READ_CHECK function. The
accompanying message provides additional information.
User Action: Correct the condition that caused the error and reenter the
Verify Utility command line.

OPENFOREIGN,

unable to open 'device-name' as a foreign volume

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility encounted an RMS error while trying to
$OPEN or $CONNECT to a foreign-mounted device.
User Action: This message will be followed by one or two lines of RMS error
messages. Please take corrective action based on the actual error condition
that RMS discovered.

OPENIN,

'input-filespec' open error

Facility: LIBRAR, LIBRARY Command
Explanation: One of the following conditions prevented the DCL command
LIBRARY from opening the input file:

•

The user directory is protected against read operations.

•

A physical device problem occurred; for example, the volume is not
mounted.

•

The specified directory does not exist.

•

The specified file does not exist.

•

Create or compress operations do not allow enough room or quota to
allocate the new library file.

User Action: Correct the problem and reenter the command line.

2-156

Messages

OPENIN,

error opening 'filespec' as input

Facility: MACRO, VAX MACRO Assembler
Explanation: The assembler encountered an 1/0 error when opening an
input source or macro library file; filespec is the file specification of the file
being opened. This message is produced when the file cannot be found.
User Action: Retry the assembly or make a new copy of the input file and
try the assembly.
OPENIN,

error opening 'input-filespec' as input

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The file could not be opened for input. The message should be
accompanied by a VMS RMS message indicating why the error occurred.
User Action: Follow the recovery procedure for the specified VMS RMS
message.
OPENIN,

error opening 'input-filespec' as input

Facility: Shared by several facilities
Explanation: An input file cannot be opened. This message is usually
accompanied by a VMS RMS message indicating the reason for the failure.
User Action: Take corrective action based on the associated message.
OPENINDEX,

error opening INDEXF.SYS, RVN 'n'

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility encountered an error during an attempt to
open the index file, [OOOOOO]INDEXF.SYS;l, on the specified relative volume.
The accompanying message provides additional information.
User Action: Correct the condition that caused the error and reenter the
Verify Utility command line.
OPENMON,

error creating logical link to monitor process 'sink-name'

Facility: EVL, Event Logger
Explanation: An error occurred while establishing a logical link to a sink
monitor program. The program image or command file may not be present.
All events destined for that sink will be discarded.
User Action: Take corrective action based on the accompanying message.
OPENOUT,

error opening 'output-filespec' as output

Facility: Shared by several facilities
Explanation: An output file cannot be opened. This message is usually
accompanied by a VMS RMS message indicating the reason for the failure.
User Action: Take corrective action based on the associated message.

2-157

Messages

OPENOUT,

error opening 'filespec' as output

Facility: MACRO, VAX MACRO Assembler
Explanation: The assembler encountered an I/O error when opening an
output object module or listing file; filespec is the file specification of the file
being opened. The message is produced when the device is write locked or is
not mounted.
User Action: Retry the assembly. If the error is reproducible, notify your
system manager.
OPENOUT,

error opening 'output-filespec'

Facility: LIBRAR, LIBRARY Command
Explanation: During a VMS RMS operation, an error is encountered while
opening an output file.
User Action: Determine that the file is open and that you have WRITE
privilege to it.
OPENOUT,

error opening 'output-filespec' as output

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The file could not be opened for output. The message should
be accompanied by a VMS RMS message indicating the reason for error.
User Action: Follow the recovery procedure for the specified VMS RMS
message.
OPENOUT,

unable to create, open, or connect to an output

Facility: ACCOUNTING, Accounting Utility
Explanation: An output file cannot be opened. This message is usually
accompanied by a VMS RMS message indicating the reason for the failure.
User Action: Take corrective action based on the associated message.
OPENQUOTA,

error opening QUOTA.SYS

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility encountered an error during an attempt
to open the quota file, [OOOOOO]QUOTA.SYS;l, on relative volume 1. The
accompanying message provides additional information. This condition is
normal if quotas are not enforced on the volume.
User Action: If necessary, correct the condition that caused the error and
reenter the Verify Utility command line.
OPENUAF,

error opening user authorization file

Facility: INPSMB, Input Symbiont
Explanation: The system encountered an error opening the user
authorization file to validate a batch job entered from a card reader. The
accompanying message provides additional information.
User Action: Consult your system manager.

2-158

Messages

OPENVIRTUAL, unable to open 'filename' as a virtual volume
Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility encountered an RMS error while trying to
$OPEN or $CONNECT to a Files-11 file being used as a virtual device.
User Action: This message will be followed by one or two lines of RMS error
messages. Please take corrective action based on the actual error condition
that RMS discovered.

OPERl,

OPERl

Facility: OPCOM, Operator Communication
Explanation: This message is issued when operator status is requested either
explicitly by the REPLY /STATUS command or implicitly as with the
REPLY /ENABLE command. It indicates that the operator's terminal is
enabled for "CARDS" class operations.
User Action: None.

OPERlO,

OPERlO

Facility: OPCOM, Operator Communication
Explanation: This message is issued optionally with the OPERSTS message.
It describes the classes of operator requests that the current operator is
enabled to act upon.
User Action: None.

OPERl l,

OPERl 1

OPER12,

OPER12

OPER2,

OPER2

Facility: OPCOM, Operator Communication
Explanation: This message is issued optionally with the OPERSTS message.
It describes the classes of operator requests that the current operator is

enabled to act upon.
User Action: None.

2-159

Messages

OPER3,

OPER3

OPER4,

OPER4

OPERS,

OPERS

OPER6,

OPER6

OPER7,

OPER7

OPER8,

OPER8

2-160

Messages

OPER9,

OPER9

Facility: OPCOM, Operator Communication
Explanation: This message is issued optionally with the OPERSTS message.
It describes the classes of operator requests that the current operator is

enabled to act upon.
User Action: None.

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.

OPERREQ,

OPER privilege required for /ACCESSED qualifier

Facility: SET, SET Facility
Explanation: OPER privilege is required for this qualifier.
User Action: See your system manager about obtaining OPER privilege.

OPERSPEC,

specify option ('options')

Facility: BACKUP, Backup Utility
Explanation: This message is returned to the operator. It indicates that
BACKUP has 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, BACKUP will
terminate. If the CONTINUE option is selected, BACKUP will ignore the
error and continue processing. If the RESTART option is selected, BACKUP
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.

2-161

Messages

OPERSTS,

operator status for operator 'operator-name'

Facility: OPCOM, Operator Communication
Explanation: This message displays information in response to the DCL
command REPLY /STATUS entered by an operator.
User Action: None.
OPINCOMPL,

operation is incomplete

Facility: SYSTEM, VMS System Services
Explanation: This message is associated with a status code returned from
a DRll-W interface operation. A block mode transfer operation completed
without transferring the requested number of bytes. The DRl 1-W generated
an end-of-transfer interrupt without transferring all the data. This message
results from a hardware error.
Some disk devices can also return this message. On a WRITE request the XE
unit has not completed restarting after a hardware failure.
Some magnetic tape devices can also return this message if there is an attempt
to read beyond the logical end of volume.
User Action: Check for a hardware error. Wait a few seconds before entering
another WRITE request.
OPNERR,

open error code of 'xx' on file 'filespec'

Facility: PATCH, Patch Utility
Explanation: A VMS RMS $OPEN request failed due to the error code
represented as 'xx'.
User Action: Correct the error code (representing as xx) and retry.
OPNOTPERDOS,

operation not permitted on DOS-11 volume 'volume-name'

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility encountered a command which could
not be performed on a DOS-11 volume, such as a RENAME or DELETE
command.
User Action: Think of something else that you want to do, since EXCHANGE
will not perform the operation.
OPNOTPERFl 1,

operation not permitted on Files-11 volume 'volume-name'

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility encountered a command which could
not be performed on a Files-11 volume, such as a DELETE or DIRECTORY
command.
User Action: Think of something else that you want to do, since EXCHANGE
will not perform the operation.

2-162

Messages

OPNOTSUP,

operation is not supported on this device

Facility: SMC, Screen Management Facility
Explanation: The requested operation cannot be performed, since the
terminal hardware does not support this feature.
User Action: Run the application on a terminal that supports this feature.

OPNSNK,

unable to open link to event receiver

Facility: EVL, Event Logger
Explanation: An error occurred when EVL attempted to open a logical link
to an event receiver on a sink node. The sink node may not be reachable in
the network, or the VMS system or network may be misconfigured.
User Action: Take correction action based on the accompanying message.

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.

OPREPL,

reply'

Facility: OPCOM, Operator Communication
Explanation: This is the operator's reply to a user's request or question.
User Action: Determined by the operator's reply.

OPREPLY,

'message-text1

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.

OPRNDLNG,

operand 'xx too long for internal buffers
1

Facility: PATCH, Patch Utility
Explanation: An internal PATCH error has occurred.
User Action: Submit a Software Performance Report.

2-163

Messages

OPRNDSYNX,

operand syntax error

Facility: MACRO, VAX MACRO Assembler
Explanation: An operand contained a syntax error.
User Action: Correct the operand syntax.

OPRNOTIF,

operator notified, waiting .. 'system time'

Facility: OPCOM, Operator Communication
Explanation: The DCL command REQUEST is entered with the /REPLY
qualifier; the request has been sent and displayed on the operator's terminal.
You cannot enter any commands until the operator responds to your request.
User Action: If you want to interrupt the request, press CTRL/C and enter
another message to the operator or press CTRL/Z to cancel the request.

OPRQST,

operator request: 'request'

Facility: MOUNT, Mount Utility
Explanation: This message announces an operator request. This message is
informational.
User Action: None.

OPRQSTCAN,

operator request canceled

Facility: MOUNT, Mount Utility
Explanation: You canceled your request by pressing CTRL/Y; this canceled
the MOUNT request.
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.

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 corrective action based on the accompanying message.

OPSYNTAX,

instruction operand syntax error

Facility: PATCH, Patch Utility and DEBUG, VMS Debugger
Explanation: There is a syntactical error in an operand within an instruction.
Or the DEBUG command DEPOSIT contained an instruction with an operand
syntax error.
User Action: Correct the syntax and retry.

2-164

Messages

OPTARGMIS,

missing argument in options file 'filename'

Facility: LINK, Linker Utility
Explanation: A required argument for an option is missing.
User Action: Correct the option line and relink.

OPTIGNSHR,

option ignored for shareable image

Facility: LINK, Linker Utility
Explanation: An option that does not apply to a shareable image is specified
in an options file. The linker ignores the option when creating a shareable
image.
User Action: Remove the option from the options file.

OPTIGNSYS,

option ignored for system image

Facility: LINK, Linker Utility
Explanation: You specified an option in an options file that is ignored for
system images.
User Action: Remove the option.

OPTLIN,

options line in error 'text' 'text' 'text'

Facility: LINK, Linker Utility
Explanation: Errors were found on the command line during options file
processing.
User Action: None.

OPTSYNERR,

syntax error in options file 'filename'

Facility: LINK, Linker Utility
Explanation: A syntax error is detected in the options file. The next line of
the error message displays the line in error.
User Action: Correct the error and relink.

OPTVALERR,

'name' option value 'decimal-number' is out of range ('decimalnumber' to 'decimal-number') in options file 'file -name'

Facility: LINK, Linker Utility
Explanation: An option specified an illegal value.
User Action: Correct the option line and relink.

ORDER,

routine called out of order

Facility: CONVERT, Convert Utility
Explanation: You have called one of the callable routines out of order.
The required order is CONV$P ASS_FILES, CONV$PASS_OPTIONS, and
CONV$CONVERT.
User Action: Fix the order and try again.

2-165

Messages

ORG,

invalid file organization value

Facility: RMS, VMS Record Management Services
Explanation: An invalid file organization is encountered on a $OPEN system
service or specified for a $CREATE system service. Files must be either
sequential, relative, or indexed, unless block I/O processing is requested.
User Action: Verify that the call to the VMS RMS system service is coded
correctly.
ORIGINAL line numbers no longer an EDT feature

Facility: EDT, EDT Editor
Explanation: EDT has been revised to enable users to edit sequencenumbered files and to retain the sequence numbers for future work. The
new capabilities replace the original line number feature.
User Action: None.
OSCTOOLON,

operating system command string too long in record 'recordnumber'

Facility: PSM, Print Symbiont
Explanation: This status is returned indicating operating system command
string is longer than allowed in this record number.
User Action: None.
OUTCMDLNG,

output command line too long for buffer

Facility: PATCH, Patch Utility
Explanation: An internal PATCH error has occurred.
User Action: Submit a Software Performance Report.
OUTCONERR,

output conversion error

Facility: OTS, General Purpose Facility
Explanation: The result would have exceeded the fixed-length string.
User Action: Increase the length of the fixed-length string and retry the
operation.
OUTORDER,

key or area primary defined out of order in statement 'n'

Facility: FDL, Create/FDL Utility, FDL, Edit/FDL Utility
Explanation: If there are two or more AREA sections, they must be in
ascending order by area number and must follow each other. If there are two
or more KEY sections, they too must be consecutive and adjacent.
User Action: Fix the order.

2-166

Messages

OUTPUT,

command execution on node 'nnnnnn'

Facility: SYSMAN, Cluster System Management Utility
Explanation: A DO command generated output from node 'nnnnnn'. The
output follows this message.
User Action: If you do not want to see the output, press CTRL/C to return
to the SYSMAN> prompt.
Output file could not be closed
Facility: EDT, EDT Editor
Explanation: EDT opened the output file and copied the MAIN buffer text
into that file. However, for some reason at the system level, EDT cannot close
that file.
User Action: Correct the problem indicated in the accompanying message.
Output file could not be created
Facility: EDT, EDT Editor
Explanation: EDT could not create the output file with the file specification
you supplied with the EXIT command. This error can be caused by problems
in the file name itself (either it contains too many characters or it contains
an invalid character). Other causes include problems in the directory
specification, if you used one (either the directory does not exist, you do
not have access to it, or the directory specification format is incorrect). This
message could also mean that a problem with the file system exists, such as
insufficient disk space.
User Action: After determining the cause of the problem, correct it.
Output file could not be opened
Facility: EDT, EDT Editor
Explanation: EDT will display another message describing the error.
User Action: Take corrective action based on the accompanying message.
OUTPUTLOST,

output being lost, both NOTERMINAL and NOLOG are in effect

Facility: DEBUG, VMS Debugger
Explanation: The SET OUTPUT command has set the output conditions to
NOTERMINAL and NOLOG; consequently, the output is not displayed on
the terminal or written to a log file. The output normally displayed by the
debugger will not be available.
User Action: Use the SET OUTPUT command to send output to the terminal
or to a log file.
OUT_RANGE, number cannot be less than 1 or larger than 127
Facility: SYSGEN, System Generation Utility
Explanation: You entered a SYSGEN command CONFIGURE with a number
that is either too small or too large.
User Action: Reenter the command specifying a number within the range of
1 to 127.

2-167

Messages

OUTSIMG,

attempted store location 'address' is outside 'name' ('address' to
'address') in module 'module-name' file 'filename'

Facility: LINK, Linker Utility
Explanation: An attempt is made to store outside the specified program
segment. This may be caused by an attempt to initialize a shared COMMON
of a shareable image when linking against the shareable image.
User Action: Initialize the data either at execution time or when linking the
shareable image containing the COMMON.
OUTSIMGP,

attempted store location 'address' is outside 'name' ('address' to
'address') in psect 'psect-name' module 'module-name' file 'filename'

Facility: LINK, Linker Utility
Explanation: An attempt is made to store an address outside the specified
program segment. This is generally due to an attempt to initialize a shared
COMMON of a shareable image when linking against the shareable image.
This message is issued if the psect name is known.
User Action: Initialize the data at execution time.
OUTSTRTRU,

output string truncated

Facility: LIB, Library Facility
Explanation: The source and destination strings are character coded text
datum, and the destination string cannot contain all of the output string. The
output string is truncated.
User Action: None.
OUTSWPERR,

outswap write error

overflow in floating addresses, illegal configuration

Facility: SYSGEN, System Generation Utility
Explanation: The SYSGEN command CONFIGURE has computed an illegal
floating address for a CSR or vector.
User Action: Reenter the SYSGEN command CONFIGURE with the correct
number of controllers.

2-168

Messages

OVERLAPRANGE,

overlapping ranges, result is unpredictable

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The source and destination ranges of a COPY_TEXT or
MOVE_TEXT overlap. The operation was terminated, but the resulting
buffer contents are unpredictable.
User Action: Do not specify overlapping ranges to COPY_TEXT or
MOVE_TEXT.
OVERLAY,

'filespec' being overwritten

Facility: Shared by several facilities
Explanation: A file is being successfully overwritten. This message is a
success return.
User Action: None.
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.
OVRALI,

conflicting alignment on overlayed psect 'psect-name' in module
'module-name' file 'filename'

Facility: LINK, Linker Utility
Explanation: Different definitions of an overlayed psect contain different
alignment specifications.
User Action: Ensure that the specified psect has the same alignment in all
modules referencing it.
OVRDSKQUOTA,

disk usage exceeds disk quota

Facility: SYSTEM, VMS System Services
Explanation: This message is associated with a status code returned by a file
system ACP QIO request. Disk usage exceeds the specified quota.
User Action: None.
OVRFLW,

too much data-modify size of field or size of data

Facility: CLI, Command Language Interpreter (DCL)
Explanation: A data value specified is larger than the area defined to receive
it; for example, a DCL command DEPOSIT requested that a value larger than
1 byte be deposited in a 1-byte area.
User Action: Verify the value and the area to receive it; correct the value or
the receiving area and reenter the command.

2-169

Messages

OVRSIZ,

oversized management command message

Facility: NCP, Network Control Program
Explanation: A message from NCP using the Network Information and
Control Exchange (NICE) protocol is too long for the Network Management
Listener (NML) to receive.
User Action: Submit a Software Performance Report showing all the
commands leading to this error.
P ACTOOLONG,

packed decimal string too long

Facility: MACRO, VAX MACRO Assembler
Explanation: The numeric string in a .PACKED directive has more than 31
digits.
User Action: Reduce the length of the decimal string.
PAD,

PAD option ignored, output record format not fixed
Facility: CONVERT, Convert Utility
Explanation: You can pad records only with the FIXED record format in the
output file.
User Action: Either change the output file record format to FIXED, or do not
specify a /PAD qualifier on the command line.

PAGECRIT,

page file space critical, system trying to continue

Facility: SYSTEM, VMS System Services
Explanation: The system is running out of page file space. This message is
more critical than the PAGEFRAG message.
User Action: Create a new page file with more space. See the Guide to
Setting Up a VMS System.
P AGEFRAG,

page file badly fragmented, system continuing

Facility: SYSTEM, VMS System Services
Explanation: The system is running out of page file space.
User Action: Create a new page file with more space. See the Guide to
Setting Up a VMS System.
P AGEREDERR, page read error
Facility: BUGCHECK, System Bugcheck
Explanation: The VMS 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, 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 on the BACKUP command
that produces the save set included with the SPR.)

2-170

Messages

Pages written to 'filename'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: This message indicates the number of pages written to the
specified output file (filename).
User Action: None.

P AGEWRTERR,

page write error

P AGNTRNVAL,

page not in transition or valid

P AGOWNVIO,

page owner violation

Facility: SYSTEM, VMS System Services
Explanation: An image attempted to change a page in memory that is owned
by a more privileged access mode. For example, an image executing in user
mode attempted to delete a page owned by supervisor mode.
User Action: Check for a programming error. Verify that pages referred to in
system service calls are owned by the calling access mode.

2-171

Messages

PAGRDERR,

page read error, reason mask= 'xx', virtual-address= 'location', PC
= 'location', PSL = 'xxxxxxxx'

Facility: SYSTEM, VMS System Services
Explanation: The system failed to read a page from disk into memory during
a page fault operation. This message indicates an exception condition and is
usually followed by a display of the condition arguments, registers, and stack
at the time of the exception.
User Action: Check the status of the device and repeat the request. Also
check for a FORCEDERROR message on the image or in the page file by
using the DCL command ANALYZE/DISK_STRUCTURE/READ_CHECK. If
the failure persists, notify your system manager.

Parallel Path is Closing Virtual Circuit-REMOTE PORT 'xxx' ,
Facility: VAXport, 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.

PARENREQ,

parenthesis required in 'DEBUG-command-segment' /TYPE:(X)'

Facility: DEBUG, VMS Debugger
Explanation: The 'DEBUG-command-segment' is either SET TYPE,
DEPOSIT, or EXAMINE. You did not include parentheses in one of these
commands.
User Action: Place parentheses around the type of expression specified.

Parenthesis mismatch
Facility: EDT, EDT Editor
Explanation: The number of right parentheses[)] does not match the number
of left parentheses [(]. This error occurs when you are entering a change
mode command string.
User Action: Modify your change mode command string to include an equal
number of properly nested left and right parentheses.

PARGTMTCH,

value of 'x' for /PARALLEL is greater than /MATCH value of 'y',
/PARALLEL set to 'y'

Facility: DIFF, DIFFERENCES Command
Explanation: A /PARALLEL value is specified that is greater than the
/MATCH value.
User Action: Decrease the /PARALLEL value. The /PARALLEL value must
always be less than or equal to the /MATCH value.

2-172

Messages

PARITY,

disk boot driver parity error

Facility: VAXCLUSTER, VAXcluster Facility
Explanation: There is a hardware error during a transfer from the satellite
system disk.
User Action: Check the error log for both the Ethernet and system disk, run
diagnostics for the suspect hardware, or contact your DIGITAL field service
representative.
PARITY,

parity error

Facility: SYSTEM, VMS System Services
Explanation: The exact meaning of this message depends on the device.
If this message is associated with a status code returned by a request to a
DRll-W interface, a parity error is detected in a block mode transfer when
the Buffered Data Path of the UNIBUS adapter is purged.
If this message is associated with a status code returned by a request to a
DR32 interface, either the microcode is not loaded successfully or the DR32
controller detected a parity error and a hardware malfunction is indicated.
The second longword of the 1/0 status block contains additional information
pertaining to this malfunction for the DR32; the following bit values are
associated with SS$_PARITY:

XF$V_IQS_WCSPE
XF$V_IOS_CIPE
XF$V_IQS_DIPE
XF$V_IOS_P ARERR
If this message is associated with a status code returned by a request to a disk
driver, one or more of the following conditions can cause this error:

•

Drive parity error

•

ECC hard error

•

Header compare error

•

Map parity error

•

Header CRC error

•

MASSBUS control parity error

If this message is associated with a status code returned by a request to a
magnetic tape driver, one or more of the following conditions can cause this
error:

2-173

Messages

Attempt to read beyond the logical end of volume
CRC error (NRZI only)
Control bus parity error
Correctable data error (PE only)
Correctable skew (PE only)
Data bus parity error
Incorrectable error (PE only)
Invalid tape mark (NRZI only)
Nonstandard gap
Longitudinal parity error (NRZI only)
Format error (PE only)
Vertical parity error (NRZI only)
Map parity error
MASSBUS control parity error
MASSBUS data parity error
Read data substitute
If this message is associated with a status code returned by a request to an
LPAll-K driver, a parity error occurred in a USA-buffered datapath.
If this message is associated with a status code returned by a request to a
terminal driver, a parity bit mismatch is detected by the device interface
during a read operation. The 1/0 operation stopped when the mismatch is
detected. (Data is received up to this point in the operation.) SS$_PARITY is
meaningful only on terminal lines that have parity enabled.

User Action: Action depends on the type of device to which the 1/0 request
is directed.
P ARMDEL,

invalid parameter delimiter-check use of special characters

Facility: CLI, Command Language Interpreter (DCL)
Explanation: A command contains an invalid character following the
specification of a parameter. Or an invalid character is present in a file
specification.
User Action: Check the command string for a spelling or grammatical error.
Reenter the command.
PARNOTGRANT,

parent lock must be granted

Facility: SYSTEM, VMS System Services
Explanation: A programming error has occurred because an attempt is made
to create a sublock under a parent lock that is not granted.
User Action: Correct the programming error and retry.
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.

2-174

Messages

P ARSEERR,

internal parsing error

Facility: PATCH, Patch Utility and DEBUG, VMS Debugger
Explanation: This message indicates either an internal PATCH error or an
internal debugger error.
User Action: Submit a Software Performance Report.
P ARSEERR,

unable to parse input name 'name'

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility attempted to interpret the given name as
a file name, but is unable to do so successfully.
User Action: This message is followed by a second message giving more
specific information about why the name is not a valid file name. Take
corrective action based on the additional message.
PARSEFAIL,

error parsing 'filespec'

Facility: Shared by several facilities
Explanation: An error is detected while parsing an input command or source
line.
User Action: Correct the error.
PARSEFAIL,

error parsing 'filespec'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: An error is detected by VMS RMS while parsing a file
specification. This message should be accompanied by a VMS RMS message
explaining the reason for the failure.
User Action: Follow the recovery procedure for the specified VMS RMS
message.
P ARSEOVER,

parser stack overflow

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The program is too complex for VAXTPU to evaluate.
User Action: Simplify the expression.
Parsing stack overflow
Facility: EDT, EDT Editor
Explanation: The command you entered caused the memory space for the
parse data to be filled before the command could be validated.
User Action: Check your command string. If it is valid, reenter the command
in segments.
P ARSTKOVR,

parse stack overflow, simplify expression

Facility: DEBUG, VMS Debugger
Explanation: The expression is too complex for the debugger to evaluate.
User Action: Simplify the expression.

2-175

Messages

PARTCOPIED,

file 'filename' partially copied to 'filespec'

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility had copied part of a file before an error is
discovered.
User Action: This message is followed by another message describing the
specific error which occurred. Take corrective action based on the second
message.

P ARTESCAPE,

partial escape

Facility: SYSTEM, VMS System Services
Explanation: A terminal escape sequence is only partially stored because the
buffer space is exhausted before the sequence is complete. The type-ahead
buffer contains the remainder of the escape sequence unless the terminal line
had the TT$M_NOTYPEAHD characteristic.
User Action: Check for a programming error. Note the condition. Modify
the source program, if necessary, to detect and respond to the condition.

PARTMAPPED,

some file map pointers not permanently resident

Facility: SYSTEM, VMS System Services
Explanation: A call is issued to the $CRMPSC system service to map a
section file; the ACP is unable to make all mapping pointers for the file
permanently resident. The $CRMPSC call can be made directly or can be
issued on the user's behalf when running an image.
User Action: Either reduce the amount of fragmentation in the file (for
example, by copying the file to a disk with a large amount of free space) or
increase the process BYTCNT quota to allow the entire file to be permanently
mapped.

PARTOOBIG,

parameters too large-must be shortened

Facility: SYSMAN, Cluster System Management Utility
Explanation: You attempted to add a startup component file that uses
/PARAM qualifiers to specify a set of qualifiers with a total length that
exceeds the maximum length allowed.
User Action: Reenter the command using a smaller parameter set.

P ASALREXI,

pasteboard already exists for this device

Facility: SMG, Screen Management Facility
Explanation: A user tried to create a pasteboard for a device, when one
is already created. This is normal in a modular environment. The existing
pasteboard id is returned. Make sure you do not delete a pasteboard that you
did not create.
User Action: None.

2-176

Messages

Pass bad status to caller
Facility: EDT, EDT Editor
Explanation: While using callable EDT, the bad status is not passed to the
calling program due to an error in EDT.
User Action: Submit a Software Performance Report.

PATERR,

internal patch coding error

Facility: PATCH, Patch Utility
Explanation: An internal PATCH error has occurred.
User Action: Submit a Software Performance Report.

Path #0. Loopback has gone from BAD to GOOD
Facility: VAXport, VAXport Driver
Explanation: The VAXport driver logs this event.
User Action: None.

Path #0. Has become working but CROSSED to Path #1.-REMOTE PORT 'xxx'
Facility: VAXport, VAXport Driver
Explanation: The Port Driver logs this event.
User Action: Check for crossed-cable pairs.

Path #0. Has gone from BAD to GOOD
Facility: VAXport, VAXport Driver
Explanation: The VAXport driver logs this event.
User Action: None.

Path #0. Has gone from GOOD to BAD
Facility: VAXport, 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 GOOD to BAD
Facility: VAXport, VAXport Driver
Explanation: The VAXport driver logs this event.
User Action: Check for crossed-cable pairs or faulty CI hardware.

Path #1. Loopback has gone from BAD to GOOD
Facility: VAXport, VAXport Driver
Explanation: The VAXport driver logs this event.
User Action: None.

2-177

Messages

Path #1. Loopback has gone from GOOD to BAD
Facility: VAXport, 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, VAXport Driver
Explanation: The Port Driver logs this event.
User Action: Check for crossed-cable pairs.

Path #1. Has gone from BAD to GOOD
Facility: VAXport, VAXport Driver
Explanation: The VAXport driver logs this event.
User Action: None.

Path # 1. Has gone from GOOD to BAD
Facility: VAXport, VAXport Driver
Explanation: The VAXport driver logs this event.
User Action: Check Path B cables for breaks or improper connections.

PATHAMBIG,

line 'line-number': Path 'path-name' is ambiguous

Facility: CDU, Command Definition Utility
Explanation: CDU encountered a DISALLOW clause that referenced an
ambiguous path. All DISALLOW path references must not be defined
ambiguously.
User Action: Edit the CLD file so that all DISALLOW path references are not
ambiguous.

PATHLOST,

path to network partner node lost

Facility: SYSTEM, VMS System Services
Explanation: The path to the remote node is lost due to too much network
activity or communications problems.
User Action: Wait, then check to see if the node is still reachable.

PATHTLONG,

too many qualifiers on name

Facility: PATCH, Patch Utility, and DEBUG, VMS Debugger
Explanation: You entered a path name consisting of more than 15 elements.
User Action: Remove excess elements and retry.

2-178

Messages

PATHUNDEF,

line 'line-number': Path 'path-name' refers to undefined verb or
syntax

Facility: CDU, Command Definition Utility
Explanation: CDU encountered a DISALLOW clause which referenced an
undefined verb or syntax. All DISALLOW references must be previously
defined.
User Action: Edit the CLD file so that all DISALLOW references are defined.
PATHUNRES,

line 'line-number': Path 'path-name' cannot be resolved

Facility: CDU, Command Definition Utility
Explanation: CDU encountered a DISALLOW clause that referenced an
undefined path. All DISALLOW references must be previously defined.
User Action: Edit the CLD file so that all DISALLOW references are defined.
P ATOVER,

pattern stack overflow

Facility: VAXTPU, VAX Text Processing Utility
Explanation: A pattern that is being executed exceeds the maximum number
(30) of active alternates.
User Action: Reduce the number of active alternates.
PBDIN _USE,

operation invalid while pasteboard is buffered

Facility: SMG, Screen Management Facility
Explanation: The operation you have tried to perform is not legal while
output to the pasteboard is being batched. For example, you cannot change
the pasteboard characteristics while the pasteboard is batched.
User Action: Turn off pasteboard batching before attempting the operation.
You may turn batching on again after the operation.
PBF, invalid prompt buffer
Facility: RMS, VMS Record Management Services
Explanation: The prompt buffer address of the RAB specifies an area of
memory that cannot be read by the caller.
User Action: Verify that the call to the VMS RMS service is coded correctly.
Specifically, check the address specified for the prompt buffer.
PCl,

'filespec'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: This message should never be displayed.
User Action: Submit a Software Performance Report.

PC2,

'n' index record[s] written to '.BRN filespec'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: This informational message results from the use of /LOG.
User Action: None.

2-179

Messages

PC3,

'n' table-of-contents records written to '.BRN filespec'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: This informational message results from the use of /LOG.
User Action: None.

PDQUALERR,

more than one display type qualifier specified for PROCESSES
class

Facility: MONITOR, Monitor Utility
Explanation: The MONITOR command specified more than one of the
display type qualifiers (/TOPBIO, /TOPCPU, /TOPDIO, /TOPFAULT) for
the PROCESSES class. Only one of these qualifiers may be specified for each
MONITOR request.
User Action: Reenter the MONITOR command, specifying only one display
type qualifier for the PROCESSES class.
PEAKUTIL,

this product requires 'number' blocks during installation.

Facility: VMSINSTAL, Install Procedures
Explanation: The installation procedure for the product determined that
there are not enough free blocks on the system disk to install the product.
User Action: Do the following:
1

Purge and delete files to make more space on the system disk.

Try to install the product again.

PENDING,

asynchronous operation not yet completed

Facility: PSM, Print Symbiont
Explanation: This status is returned by a print symbiont input routine
indicating the requested function is accepted but not completed.
User Action: None.
PENDING,

asynchronous operation not yet completed

Facility: RMS, VMS Record Management Services
Explanation: The program requested a VMS RMS asynchronous 1/0
operation; the operation is initiated but is not completed. This message is
a success status code.
User Action: None.
PERMSYM,

deletion of permanent symbols not allowed

Facility: CU, Command Language Interpreter (DCL)
Explanation: You are trying to delete or redefine a permanent symbol.
Permanent symbols are $STATUS, $SEVERITY, and $RESTART. Permanent
symbol deletion is invalid.
User Action: Do not try to delete or redefine these symbols.

2-180

Messages

PES,

partial escape sequence
Facility: RMS, VMS Record Management Services
Explanation: The user buffer filled before a complete escape sequence is
entered. The remainder of the escape sequence will be returned with the next
input operation.
User Action: Increase the size of the user record buffer to allow for escape
sequences, or modify the program, if necessary, to recognize and respond to
the condition.

PFMBSY,

page fault monitor is in use

Facility: SYSTEM, VMS System Services
Explanation: The page fault monitor has already been activated for your
process or group.
User Action: Request the page fault monitor only once per image invocation,
or wait until the other user finishes.
PFNLISTCNT,

inconsistent PFN list count

PFN reference count nonzero

2-181

Messages

PGFGBLBAD,

pagefault, global page table entry bad format

pagefault with IPL too high

pagefault, location field has bad value

phase not found

Facility: SMI, System Management Intergator/Server
Explanation: A search for startup components running in a given phase
found no matching entries.
User Action: Reenter the command with a different /PHASE argument.

2-182

Messages

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; perhaps another mode of operation,
such as using the /IMAGE qualifier, is 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 you used the /PHYSICAL command qualifier, you
specified more than a device name as an input-specifier or output-specifier.
The file specification for a volume to be processed with the /PHYSICAL
qualifier must contain only a device name.
User Action: Refer to the VMS Backup Utility Manual for information on the
/PHYSICAL command qualifier and reenter the command.

PHYS ET,

physical save set supplied to nonphysical operation

Facility: BACKUP, Backup Utility
Explanation: You cannot use a save set created with the /PHYSICAL
qualifier 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.

Please answer Y(es), N(o), Q(uit), or A(ll)
Facility: EDT, EDT Editor
Explanation: This prompt occurs when you have selected the QUERY
qualifier and have failed to answer with one of the above in response to the
question mark (?) prompt.
User Action: Respond to the prompt using either Y, N, Q, or A.

PLG,

error detected in file's prolog (reconstruct file)
Facility: RMS, VMS Record Management Services
Explanation: The contents of the file have been corrupted because the file's
prolog has been damaged.
User Action: Reconstruct the file.

PLV,

unsupported prolog version
Facility: RMS, VMS Record Management Services, and CONVERT, Convert
Utility
Explanation: The version number field in the file's prolog read on open
indicates that the file cannot be processed by this version of VMS RMS.
User Action: Verify the version of VMS RMS that you are using; use the
correct version to process the file.

2-183

Messages

PLV,

unsupported prolog version
Facility: CONVERT, Convert/Reclaim Utility
Explanation: You have specified a Prologue 1 or Prologue 2 indexed file;
CONVERT /RECLAIM works only with Prologue 3 indexed files.
User Action: Specify a Prologue 3 file, or else use the CONVERT utility to
reorganize the Prologue 1 or 2 file.

POOLEXPF,

pool expansion failure

Facility: SYSTEM, VMS System Services
Explanation: Pool expansion failure occurs when the system runs out of
nonpaged pool and there are not sufficient free pages for pool expansion.
User Action: Examine the status of the small packet (SRP), 1/0 request
packet (IRP), and large packet (LRP) lookaside lists, as well as pool status.
Use the DCL command SHOW MEMORY /POOL/FULL to display memory
status. You can extend the lists or pool by resetting the appropriate SYSGEN
parameters. If you suspect disk fragmentation, use the Backup Utility to
compress the disk.

Port Error Bits Set-CNF/PMC/PSR 'xxxxxxxx/xxxxxxxx/xxxxxxxx',
Facility: VAXport, VAXport Driver
Explanation: The port driver attempts to reinitialize the port; after 50 failed
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 whether the operator has halted and
continued the system for any reason. If the console log does not show
operator intervention, increase the PAS TIM OUT SYSGEN parameter until the
timeouts no longer occur. For nontimeout errors, call DIGITAL field service to
check the port hardware.

Port has Closed Virtual Circuit
Facility: VAXport, 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, VAXport Driver
Explanation: The port driver has 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 the necessary corrective action and reboot the
system.

2-184

Messages

Port Power Down
Facility: VAXport, VAXport Driver
Explanation: The port driver detected a power down interrupt from the port.
User Action: Call DIGITAL field service to check the port power supply.
Port Power Up
Facility: VAXport, VAXport Driver
Explanation: The port driver logs this event.
User Action: None.
Port timeout
Facility: VAXport, 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 field service to check the port hardware, the CI
cable, and the node number configuration.
Port Transition Failure-CNF /PMC/PSR 'xxxxxxxx/xxxxxxxx/xxxxxxxx'
Facility: VAXport, 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 field service to check the port hardware.
Port ucode not at current rev level. PROM/RAM rev is 'xxxx/xxxx'
Facility: VAXport, 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 field service to
upgrade the port microcode. Prolonged operation of the port with obsolete
microcode is not supported by DIGITAL.
POS, invalid key position (greater than MRS) for key= 'nnn'
Facility: RMS, VMS Record Management Services
Explanation: The position of a key segment specified by a key definition XAB
is greater than the maximum record size specified for the file.
User Action: The status value (STV) field of the FAB provides the key of
reference of the XAB in error. Verify that the call to the VMS RMS service is
coded correctly.

2-185

Messages

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.

POWERFAIL,

power failure occurred

Facility: SYSTEM, VMS System Services
Explanation: A power failure occurred while a request is active or the device
is powered down. If this message is associated with a status code returned by
a request to an LPAll-K driver, a power failure occurred while a request is
active. (Only for the start microprocessor, initialize LP All-K, set clock, and
start data transfer request functions.)
User Action: If appropriate, rerun the program.

PRACCREM,

proxies to 'user name' removed

Facility: AUTHORIZE, Authorize Utility
Explanation: Proxy access records for the specified user have been removed
from the network authorization file. When a user name in the system user
authorization file (SYSUAF.DAT) is removed, any corresponding records in
the network authorization file (NETPROXY.DAT) are automatically removed
at the same time.
User Action: None.

PRACREN,

proxies to 'user name' renamed

Facility: AUTHORIZE, Authorize Utility
Explanation: Proxy access records for the specified user have been renamed
to the new user name. When a user name in the system user authorization
file (SYSUAF.DAT) is renamed, any records in the network authorization file
(NETPROXY.DAT) for the original user name are automatically renamed to
the new user name.
User Action: None.

2-186

Messages

PRCREAT,

error creating process

Facility: JBC, Job Controller
Explanation: The job controller encountered an error in creating a process for
a terminal that is attempting to log in. This failure usually occurs when there
are no more process slots available in the system to create a new process.
User Action: Try again later when fewer users are competing for system
resources. Also, notify the system manager of this situation.

PREDEFREP,

previous key-definition replaced

Facility: SMG, Screen Management Facility
Explanation: A previous key definition is replaced by a new definition.
User Action: None.

PREMATUREEOF,

premature end-of-file detected

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The program parsed correctly until the compilation stopped.
However, the compilation stopped because the end of the program is reached
prematurely (for example, before a closing ENDPROCEDURE statement).
User Action: Correct the program format and then recompile.

PREMEOF,

premature end-of-file encountered in options file 'filename'

Facility: LINK, Linker Utility
Explanation: The options file ended before the end of a continued line is
found.
User Action: Correct the options file and relink.

PREMEOF,

premature end-of-file on /INPUT file

Facility: MONITOR, Monitor Utility
Explanation: The input recording file is either empty or does not contain the
required control information because the MONITOR request that created the
file is canceled prematurely. For example, a MONITOR request with a future
beginning time could cause the process to hibernate and then get canceled.
User Action: Verify that the file specified with the /INPUT qualifier is the
MONITOR recording file you desired. Then, reenter the MONITOR request.

PREMMSG,

record removed from NETPROXY.DAT

Facility: AUTHORIZE, Author~ze Utility
Explanation: The record specifed in the AUTHORIZE command REMOVE
/PROXY has been removed from the netwotk user authorization file.
User Action: None.

2-187

Messages

PRESENT,

entity value is present in command string

Facility: CU, Command Language Interpreter (DCL)
Explanation: This status is returned by the CLI$PRESENT CU interface
routine to indicate that the specified entity is explicitly present in the
command line.
User Action: None.
PREVDUP ACE,

previous ACE will supercede current ACE-not entered

Facility: ACLEDIT, Access Control List Editor
Explanation: An ACE already exists prior to the current position within the
ACL and supercedes the ACE about to be entered, rendering it useless. The
current ACE is not entered.
User action: Modify the current ACE (or delete it), or modify the previous
ACE.
PREVINIT,

patch area has previously been initialized

Facility: PATCH, Patch Utility
Explanation: The patch area descriptor for the specified user-defined patch
area has previously been initialized. PATCH set the patch area to the area
named in the SET PATCH_AREA command, but did not initialize a new
descriptor.
User Action: Continue to enter patches into the user-defined patch area.
To see the current status of the patch area, issue the SHOW PATCH_
AREA command. In the future, do not use the /INITIALIZE qualifier if the
descriptor has already been initialized.
PRIIHDBAD,

invalid primary index file header, RVN 'n'

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the primary index file header on
the specified relative volume is corrupted. The utility refreshes the primary
index file header from the alternate index file header.
User Action: None.
PRIMIN,

error code of 'xx' parsing input file

Facility: PATCH, Patch Utility
Explanation: A command interpreter callback request failed due to the error
represented as 'xx'.
User Action: Correct the error (represented as 'xx') and retry.
PRIMOUT,

error code of 'xx' parsing journal file

Facility: PATCH, Patch Utility
Explanation: A command interpreter callback request failed due to the error
represented as 'xx'.
User Action: Correct the error (represented as 'xx') and retry.

2-188

Messages

Print file could not be closed

Facility: EDT, EDT Editor
Explanation: EDT opened the output file and copied the text specified with
the PRINT command into that file. However, for some reason at the system
level, EDT is unable to close that file.
User Action: Correct the problem indicated by the accompanying message.
Print file could not be created

Facility: EDT, EDT Editor
Explanation: EDT could not create the output file with the file specification
you supplied with the PRINT command. This error can be caused by
problems in the file name itself (either it has too many characters or an invalid
character). Other causes include problems in the directory specification, if you
used one (either the directory does not exist, you do not have access to it, or
the directory specification format is incorrect). This message could also mean
that there is a problem with the file system, such as insufficient disk space.
User Action: Correct the problem indicated by the accompanying message.
PRINT,

printer

Facility: OPCOM, Operator Communication
Explanation: This message is issued when operator status is requested either
explicitly by the REPLY /STATUS command or implicitly as with the REPLY
/ENABLE command. It indicates that the operator's terminal is enabled for
"PRINT" class operations.
User Action: None.
PRISECMAP,

private terminal table used

Facility: SMG, Screen Management Facility
Explanation: The requested terminal definition is found in the caller's private
copy of Termtable.
User Action: None.
PRIV,

privilege error

Facility: CNF, NI Configurator
Explanation: NICONFIG is executing without all the necessary privileges.
User Action: See the accompanying messages for the missing privileges.
Install NICONFIG with all the required privileges or run from an account
with all the required privileges.

2-189

Messages

PRIVINSTALL,

shareable images must be installed to run privileged image

Facility: SYSTEM, VMS System Services
Explanation: Two possible reasons for this error follow:
•

You tried to run a privileged image with uninstalled shareable images.

•

You referenced an uninstalled shareable image when the main program is
installed with the /EXECUTE_ONLY qualifier.

User Action: Ask the system manager to install all shareable images used by
executable images.
PRMEOF,

premature end-of-file

Facility: SUMSLP, SUMSLP Batch Editing Utility
Explanation: A SUMSLP command file terminated unexpectedly. This is
probably due to the absence of a terminator ( /) at the end of the command
file.
User Action: Insert a terminator (/) at the end of the command file and edit
again.
PRMLEN,

parameter too long

Facility: NCP, Network Control Program
Explanation: A parameter string or value has too many characters.
User Action: Reenter the command with appropriate parameter information.
PRMLON,

parameter too long text'

Facility: NCP, Network Control Program
Explanation: A parameter value is too long for the implementation to
handle. The 'text' part of the message identifies the low and high bytes
of the parameter type number.
User Action: Reduce the length of the parameter.
PRMMS,

parameter missing 'text'

Facility: NCP, Network Control Program
Explanation: A required parameter in your command is missing. The 'text'
part of the message identifies which parameter is missing.
User Action: Review the command description and reenter your command
with the correct parameter.

2-190

Messages

PRMNA,

parameter not applicable text

Facility: NCP, Network Control Program
Explanation: Your parameter is not applicable to the component specified in
the message. For example, you may have set a tributary address for pointto-point line or attempted to set a controller to loopback mode when the
controller does not support that function. The text part of the message
identifies the parameter type.
1

User Action: Review the command description and reenter the command
with the correct parameter.
PRMRNG,

parameter value out of range, parameter

Facility: NCP, Network Control Program
Explanation: A numeric parameter value has an invalid range. The
'parameter' part of the message identifies which value is incorrect.
User Action: Reenter the command with an appropriate parameter value.
PRO,

invalid process identification
Facility: NCP, Network Control Program
Explanation: The format of the process identification is incorrect.
User Action: Check the syntax rules for process identifiers and reenter your
command with the correct process identifier.

PROCDONE,

operation completed. Processing finished at 'date-time'

Facility: BACKUP, Backup Utility
Explanation: Standalone BACKUP processing has completed.
User Action: None.
PROCESSEND,

subprocess terminated

Facility: VAXTPU, VAX Text Processing Utility
Explanation: A VMS subprocess that is successfully activated has been
stopped. This condition can be caused by leaving VAXTPU, deleting the
process, entering a LOGOUT command while in the subprocess, or having
the subprocess stopped by another system user.
User Action: None.
PROCFILE, processing file 'filename 1
Facility: DSR, DIGITAL Standard Runoff
Explanation: This informational message indicates that DSR has begun
processing the file.
User Action: None.

2-191

Messages

PROCGONE,

Process not in system

identification of created process is 'process-ID'

Facility: RUN, Run Detached Utility
Explanation: The newly created process has an identification number of
'process-ID'. This is an informational message.
User Action: None.
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.
PROCSUPERSEDED,

definition of procedure 'name' superseded

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The procedure you are defining already had a definition. The
new definition you supplied replaces the old one.
User Action: None.
PRODNOTINS,

optional software product 'name' not installed

Facility: Shared by several facilities
Explanation: The specified optional software product is not installed on your
system.
User Action: Install the requested software.
PRODSKIP,

Products that have not been installed will be skipped.

Facility: VMSINSTAL, Install Procedures
Explanation: You requested that multiple products be installed, but one of
these products requires that the system be rebooted after its installation. To
accomplish this, the remaining uninstalled products must be skipped.
User Action: Install the remaining products after the system is rebooted.

2-192

Messages

PROERR,

error protecting 'filename'

Facility: SET, SET Facility
Explanation: An error occurred when the file's protection was set.
User Action: Take corrective action based on the accompanying message.
PROERR,

prolog checksum error at VBN = 'nnn'

Facility: CONVERT, Convert Utility and CONVERT, Convert/Reclaim
Utility
Explanation: The specified block of the file's pro log has been corrupted. This
message will be accompanied by an RMS error message that explains the
error.
User Action: Correct the error described in the RMS error message and try
again.
PROFRANOT,

proper frame not found on call stack for 'path-name'

Facility: DEBUG, VMS Debugger
Explanation: You attempted to look at a variable in a routine invocation that
does not exist.
User Action: Specify a routine or routine invocation that is currently active.
PROGLOST,

program lost-Sorry

Facility: VAXTPU, VAX Text Processing Utility
Explanation: An internal VAXTPU failure occurred.
User Action: Submit a Software Performance Report.
PROL _WRT,

prolog write error

Facility: CONVERT, Convert Utility, CONVERT, Convert/Reclaim Utility
Explanation: This message will be accompanied by an RMS error message
that explains the error.
User Action: Correct the error described in the RMS error message and try
again.
PRONOTCHG,

protection on 'filename' not changed

Facility: SET, SET Facility
Explanation: The protection on the file is not changed.
User Action: Take corrective action based on the accompanying message.
PROTECTED,

ACE cannot be modified

Facility: ACLEDIT, Access Control List Editor
Explanation: The current ACE is protected against deletion. This is usually
because it is an application ACE or it is marked hidden.
User Action: None.

2-193

Messages

PROTECTED,

'filename' file protection changed to 'protection'

Facility: SET, SET Facility
Explanation: The file protection has been successfully changed. This message
is displayed when a SET FILE/PROTECTION command is entered with the
/LOG qualifier.
User Action: None.
PROTECTED,

protection on 'filespec' changed to 'protection-string'

Facility: Shared by several facilities
Explanation: This message is associated with the execution of a DCL
command SET PROTECTION. The protection of the named file is changed to
the value specified. This is an informational message.
User Action: None.
PROTERR,

internal protocol error

Facility: REM, Set Host Facility
Explanation: A system internal error has occurred.
User Action: Submit a Software Performance Report.
PROTINSTALL,

protected images must be installed

Facility: SYSTEM, VMS System Services
Explanation: Protected images must be installed.
User Action: Use the /PROTECT qualifier to install a shareable image that
contains user-written system services.
PROTMIS,

server and host not running same SMI protocol version

Facility: SMI, System Management Intergator/Server
Explanation: Incompatible versions of SYSMAN and SMISERVER exist in
the environment. Operation continues on the next node in the environment.
User Action: Ensure that all nodes participating in a SYSMAN operation are
running compatible versions of the VMS operating system or SMISERVER, or
both.
PROTOCOL,

remote protocol error-data packet w / o INIT

Facility: SMI, System Management Intergator/Server
Explanation: This message indicates an internal error. SMI is trying to use a
remote link without sending an initialize packet.
User Action: Submit a Software Performance Report showing all SYSMAN
commands leading to this error.

2-194

Messages

PROTOCOL,

network protocol error

Facility: SYSTEM, VMS System Services
Explanation: An error occurred attempting to initiate a DECnet-VAX logical
link connection.
User Action: Notify your software specialist. Refer to the VMS Networking
Manual for additional information.
PROTOOLON,

prompt-string is too long

Facility: DTK, DECtalk Facility
Explanation: The length of a prompt string exceeded 512 characters.
User Action: Shorten the prompt string to 512 characters or fewer.
PROTOOLON,

prompt-string is too long

Facility: SMG, Screen Management Facility
Explanation: The length of a prompt string exceeded 512 characters.
User Action: Shorten the prompt to 512 characters or less.
PRTEXT,

file only partially extended. Volume may be too fragmented.

Facility: SYSGEN, System Generation Utility
Explanation: The SYSGEN command CREATE failed. You have insufficient
disk space.
User Action: Clean up your disk space or specify a smaller /SIZE qualifier.
PRV,

insufficient privilege or file protection violation
Facility: RMS, VMS Record Management Services
Explanation: One of the following has occurred:
•

Your process does not have one or more of the privileges necessary to
perform the requested file access

•

Your process is denied access to the file because of the protection applied
to the file or to the directory in which the file is listed

User Action: Verify the protection applied to the file (using the DIRECTORY
/FULL command), and change the protection if necessary (using the SET
PROTECTION command). If you cannot change the protection, ask the
system manager or the owner of the file to change it.
If the file's current protection should permit the desired access, verify the
protection applied to the directory in which the file is listed.
If the preceding actions do not apply or fail to solve the problem, ask the
system manager for the necessary privileges.

2-195

Messages

PRVNOTFND,

invalid privilege name

Facility: AUTHORIZE, Authorize Utility
Explanation: You specified an invalid privilege name.
User Action: See the VMS Authorize Utility Manual for information on valid
privilege names.
PRVNOTUNQ,

privilege name 'name' is not unique

Facility: INSTALL, Install Utility
Explanation: You entered an abbreviation for a privilege name that is not
unique.
User Action: Specify at least four characters for the privilege name and retry.
PRVNOTUNQ,

privilege name not unique

Facility: AUTHORIZE, Authorize Utility
Explanation: You did not specify enough characters of a privilege name to
make it unique.
User Action: Enter at least the first four characters of a privilege name.
PRVVIO,

privilege violation

Facility: NCP, Network Control Program
Explanation: You do not have the privilege to perform the requested
function. Privileges are required to perform all NCP commands, except
for the following: HELP, CLEAR EXECUTOR NODE, LOOP EXECUTOR,
LOOP LINE, LOOP NODE, SET EXECUTOR NODE, SHOW, and TELL.
To use the PURGE, DEFINE, and LIST commands, you must have system
privilege (SYSPRV) or have access to the files with the system protection. The
remaining NCP commands require the operator privilege (OPER).
User Action: None, unless your system manager gives you the required
privilege.
PSCALI,

psect 'psect-name' alignment ('decimal-number') illegal in module
'module-name' file 'filename'

Facility: LINK, Linker Utility
Explanation: A module specified an illegal alignment for a psect.
User Action: Submit a Software Performance Report on the appropriate
language translator.
PSCNXR,

transfer address is not in executable, relocatable psect in module
'module-name' file 'filename'

Facility: LINK, Linker Utility
Explanation: The transfer address for a module is not in an executable,
relocatable psect.
User Action: Move the transfer address into an executable, relocatable psect.

2-196

Messages

PSECBUFOVF,

PSECT context buffer overflow

Facility: MACRO, VAX MACRO Assembler
Explanation: The .SAVE_PSECT directive attempted to save a program
section context when the program section context buffer is filled. A maximum
of 31 program section contexts can be saved in the buffer.
User Action: Reduce the amount of program section nesting.

PSECBUFUND,

PSECT context buffer underflow

Facility: MACRO, VAX MACRO Assembler
Explanation: The .RESTORE_PSECT directive attempted to restore a
program section context when the program section context buffer is empty.
User Action: Ensure that each .RESTORE_PSECT directive corresponds to a
.SAVE_PSECT directive.

PSECOPCNFL,

conflicting PSECT options

Facility: MACRO, VAX MACRO Assembler
Explanation: The values specified in a .PSECT directive conflicted with each
other or were not the same as the values specified in a preceding .PSECT
directive that specified the same program section name.
User Action: Correct the conflicting values in the .PSECT directives.

PSTFULL,

process section table is full

Facility: SYSTEM, VMS System Services
Explanation: The section table in the process header is full. Additional
sections cannot be created for this process.
User Action: Relink the image, forcing fewer image sections, or reboot,
increasing the SYSGEN parameter PROCSECTCNT.

PTELENVIOL, unexpected page table length violation
Facility: BUGCHECK, System Bugcheck
Explanation: The VMS 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, 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 on the BACKUP command
that produces the save set included with the SPR.)

2-197

Messages

PTRCNT,

ACP block count exceeds retrieval pointer size

purge aborted due to errors

Facility: NCP, Network Control Program
Explanation: The purge requested by the WITH option of the NCP command
COPY is aborted. The local node database is not affected.
User Action: See previous error messages to determine why the purge is
aborted.
PURGEVER,

version numbers not permitted

Facility: Shared by several facilities
Explanation: The command does not allow version numbers in a file
specification.
User Action: Reenter the command; do not specify a version number for the
file specification.
PURGWSSCN,

purge working set scan error

pushdown stack overflow

Facility: LIB, Library Facility
Explanation: The image pushdown stack overflowed.
User Action: Use the debugger to determine whether the procedure stack
does not contain an excessive number of entries, or if an infinite call loop has
caused the stack to grow.

2-198

Messages

PUTERR,

put error

Facility: AUTHORIZE, Authorize Utility
Explanation: This message is issued with other messages.
User Action: Take corrective action based on the accompanying messages.
PUTERR,

put error code of 'xx' on file 'filespec'

Facility: PATCH, Patch Utility
Explanation: An error writing the specified file occurred due to the error code
represented as 'xx'.
User Action: Correct the error code (represented as 'xx') and retry.
PWDLOCKED,

password is locked to prevent change

Facility: SET, SET Facility
Explanation: This message is returned by the command line interpreter for
the DCL command SET PASSWORD. The system manager restricted an
account from changing its password. Typically, this is done for demonstration
accounts which may be accessed by a large number of users.
User Action: If the user requires that the account not be restricted from
changing its password, consult the system manager.
PWDNCH,

password not changed

Facility: AUTHORIZE, Authorize Utility
Explanation: An error occurred using the random password generator to
generate an account password.
User Action: None.
PWDNOL,

password not on list; try again

Facility: AUTHORIZE, Authorize Utility
Explanation: The password you specified is not one of those listed.
User Action: Select another password and try again.
PWDNOTDIF,

new password must be different from current password

Facility: SET, SET Facility
Explanation: The new password that you specified is the same as the old
password.
User Action: Change the password and reenter the command.

2-199

Messages

PWDNOTVAL,

old password validation error-password unchanged

Facility: SET, SET Facility
Explanation: This message is returned by the command line interpreter for
the DCL command SET PASSWORD. An old password validation error is
detected. The user is required to enter the old password to help protect an
unattended process. The old password may have been mistyped.
User Action: Reenter the old password. If the old password has been
forgotten, consult the system manager.
PWDNOTVER,

new password validation error-password unchanged

Facility: SET, SET Facility
Explanation: This message is returned by the command line interpreter for
the DCL command SET PASSWORD. The new password was not entered
the same way twice. Entering the password twice ensures that the password
intended by the user is properly entered.
User Action: Repeat the entire sequence correctly.
PWDSYNTAX,

illegal password syntax

Facility: SET, SET Facility
Explanation: An illegal password is used. Passwords may contain from 1
through 31 characters. The valid characters are the following:
A through Z
a through z
0 through 9
$ (dollar sign)
_ (underscore)
User Action: Reenter the password, using valid characters.
PWDSYNTAX,

invalid password syntax

Facility: AUTHORIZE, Authorize Utility
Explanation: You entered a password using incorrect syntax.
User Action: Enter a password using 1-31 alphanumeric characters, the dollar
sign ( $ ), or the underscore ( _) characters.
PWF,

page number will not fit on title
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: The title (on the first header information line) extends into the
page number field, so that the page number will not fit.
User Action: Reduce the length of the title.

2-200

Messages

QEMPTY,

queue empty

Facility: Shared by several facilities
Explanation: If returned from a DR32 support routine call, the termination
queue is empty but the transfer is still in progress.
User Action: Continue trying to remove a command packet from the
termination queue until you are successful or the transfer completes.

QFACTIVE,

disk quota file is already active

Facility: SYSTEM, VMS System Services
Explanation: The quota file is already active.
User Action: Check the device specified and proceed.

QFNOTACT,

disk quota file is not active

Facility: SYSTEM, VMS System Services
Explanation: The quota file is not active.
User Action: Check the device specified, or check the default device. Turn
quotas on, if appropriate.

QIOBFOVF,

QIO buffer overflow

Facility: MOM, Maintenance Operation Module
Explanation: An internal buffer used to obtain network management
information is sized inadequately. This is a program logic error and should be
reported.
User Action: Submit a Software Performance Report.

QIOERR, internal QIO error
Facility: REM, Set Host Facility
Explanation: A system internal error has occurred.
User Action: Submit a Software Performance Report.

QST,

Quoted string too long: 'string'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: A quoted text value contains too many characters.
User Action: Reduce the number of characters. In some cases, only one
quoted character is allowed (for example, the .DISPLAY ELEMENTS
command). In other cases, up to 150 characters are allowed (for example,
the .REPEAT command).

2-201

Messages

QUALINV,

'class-name-qualifier' qualifier not valid for 'class-name' class

Facility: MONITOR, Monitor Utility
Explanation: An attempt is made to combine a class name with a qualifier
for which it is not valid. Class name qualifiers are valid only for a subset of
MONITOR classes.
User Action: Check the valid combinations of class-names and class-name
qualifiers by entering the DCL command similar to the following:
HELP MONITOR class_name_qualifiers

Then, reenter the MONITOR request.
QUE_CLOSED,

queue closed, jobs not accepted

Facility: JBC, Job Controller
Explanation: You attempted to enter or requeue a job to a queue that is
marked closed. A closed queue cannot accept new jobs, but it will continue
to process jobs already entered.
User Action: Put the queue into an open state by using the /OPEN qualifier
with the SET QUEUE, START /QUEUE, or INITIALIZE/QUEUE commands
and retry your request.
QUEFORMAT,

system job queue file has invalid format

Facility: JBC, Job Controller
Explanation: The job controller detected an error in the format of the system
job queue file. The nature of the queue file corruption is such that the job
controller is not able to repair the damage and continue operation using this
queue file.
User Action: Create a new queue file using the START /QUEUE/MANAGER
/NEW_VERSION command or delete the existing queue file and create a new
file using the START /QUEUE/MANAGER command.
QUEisEMP,

queue is empty

Facility: LIB, Library Facility
Explanation: The queue is empty, and is not modified.
User Action: None.
QUENOTSTOP,

queue must be stopped to perform operation

Facility: JBC, Job Controller
Explanation: A queue management operation that requires the queue to be in
a stopped state was attempted while the queue was in another state. Deleting
a queue is such an operation.
User Action: Enter a STOP /QUEUE/RESET command to stop the queue,
then reenter the original request.

2-202

Messages

QUERESET,

job aborted during execution because queue was reset

Facility: JBC, Job Controller
Explanation: The queue is reset with a STOP /RESET command during
execution of the affected job.
User Action: Resubmit the job.
QUEUEMPTY,

scheduling queue empty

editor quitting

Facility: VAXTPU, VAX Text Processing Utility
Explanation: You are exiting the VAXTPU image editing session. When you
quit an editing session, the edits you made during the session are not saved.
User Action: None.
QUO,

error in quoted string

Facility: RMS, VMS Record Management Services
Explanation: The quoted foreign file specification string or the quoted task
specification string of a file specification does not have the correct syntax.
User Action: Use the DCL command HELP or refer to the VMS DCL
Dictionary, if necessary, for the correct syntax and reenter the file specification.
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,
BACKUP 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
REBUILD function of the DISKQUOTA utility to reconstruct the quota file.

2-203

Messages

Quoted string required
Facility: EDT, EDT Editor
Explanation: A required quoted string is not supplied for the command you
entered. The indicates the position of the required quoted string.
A

User Action: Reenter the command supplying the required quoted string.

RAB,

invalid RAB or RAB not accessible
Facility: RMS, VMS Record Management Services
Explanation: The block identifier field of the record access block for a file
does not indicate that this is a RAB. Or the RAB is not in an area of memory
that can be written by the caller. An attempt may have been made to perform
record operations to a FAB.
User Action: Verify that the control block referred to is a RAB, that the
RAB is properly initialized, and that it is not inadvertently modified during
execution of the program.

RAC,

invalid record access mode
Facility: RMS, VMS Record Management Services
Explanation: The record access mode (RAC) field of the RAB indicates an
invalid record access mode. The field must contain either SEQ, KEY, or RFA.
User Action: Verify that the call to the VMS RMS service is coded correctly.

RADRMOD,

reserved addressing fault at PC 'location', PSL = 'xxxxxxxx'

Facility: SYSTEM, VMS System Services
Explanation: An instruction specifies an addressing mode that is illegal
within the context of its use. This message indicates an exception condition
and is usually followed by a display of the condition arguments, registers,
and stack at the time of the exception.
User Action: Examine the PC and virtual address displayed in the message
to determine the instruction that caused the error.

Range for RESEQUENCE must be contiguous
Facility: EDT, EDT Editor
Explanation: The range specification for the EDT command RESEQUENCE
did not contain contiguous lines.
User Action: Reenter the command specifying contiguous lines for the range.

Range specified by /SEQUENCE would cause duplicate or non-sequential numbers
Facility: EDT, EDT Editor
Explanation: You have range specifications in the EDT command
RESEQUENCE that would cause duplicate or nonsequential numbers.
User Action: Modify the range specifications and reenter the command.

2-204

Messages

RAT,

invalid record attributes
Facility: RMS, VMS Record Management Services
Explanation: The record attributes field of the FAB specified for a $CREATE
or a $OPEN operation contains a value other than BLK, CR, FTN, or PRN, or
an invalid combination is specified.
User Action: Verify that the call to the VMS RMS service is coded correctly.

RAWFMT,

an invalid raw event is seen and ignored

Facility: EVL, Event Logger
Explanation: NETACP obtained an invalid unprocessed event. The size of
the event exceeded the buffer size. This is probably caused by a software
error.
User Action: Submit a Software Performance Report.
RBF,

invalid record buffer
Facility: RMS, VMS Record Management Services
Explanation: The record buffer address of the RAB specifies an area of
memory that cannot be correctly accessed by the caller.
User Action: Verify that the call to the VMS RMS service is coded correctly.

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.
RDBADDERR,

unable to add 'id-name' to RIGHTSLIST.DAT

Facility: AUTHORIZE, Authorize Utility
Explanation: The identifier name you specified could not be added to the
rights database file (RIGHTSLIST.DAT). This message should be accompanied
by a VMS RMS message that identifies the specific reason for the error. Most
likely, the identifier name already exists in the rights database file. Duplicate
identifier names are not allowed in the rights database file.
User Action: Correct the condition identified by the RMS message and
reenter your command. If you want to change the name of an identifier in the
rights database file, use the AUTHORIZE command MODIFY/IDENTIFIER.

2-205

Messages

RDBADDERRU,

unable to add 'id-name' value: '[UIC]' to RIGHTSLIST.DAT

Facility: AUTHORIZE, Authorize Utility
Explanation: The specified identifier name and its corresponding user
identification code (VIC) could not be added to the rights database file
(RIGHTSLIST.DAT). This message should be accompanied by a VMS RMS
message that identifies the specific reason for the error. Most likely, the
identifier name already exists in the rights database file. Duplicate identifier
names are not allowed in the rights database file.
This error also occurs if you copy a record in the system user authorization
file (SYSUAF.DAT) without specifying a new VIC value for the copy. By
default, an identifier name and corresponding UIC value for the new record
are written to the rights database file (RIGHTSLIST.DAT); if the VIC has
not been changed, it will conflict with the VIC of the original record, and a
'duplicate identifier' error results.
User Action: Correct the condition identified by the RMS message and
reenter your command. If you want to change the UIC value of an identifier
in the rights database file, use the /VALUE qualifier with the AUTHORIZE
command MODIFY /IDENTIFIER. If you copy a record in the system user
authorization file, and you want an identifier for the new record to be added
to the rights database file, use the /VIC qualifier with the AUTHORIZE
command COPY.
RDBADDERRV,

unable to add 'id-name' value: 'hex code' to RIGHTSLIST.DAT

Facility: AUTHORIZE, Authorize Utility
Explanation: The specified identifier name and its corresponding integer
value (expressed as an 8-bit hexadecimal code) could not be added to the
rights database file (RIGHTSLIST.DAT). This message should be accompanied
by a VMS RMS message that identifies the specific reason for the error. Most
likely, the identifier name or value already exists in the rights database file.
Duplicate identifier names or values are not allowed in the rights database
file.
User Action: Correct the condition identified by the RMS message and
reenter your command. If you want to change the value of an identifier in
the rights database file, use the /VALUE qualifier with the AUTHORIZE
command MODIFY /IDENTIFIER.
RDBADDMSG,

identifier 'id-name' value: 'hex code' added to RIGHTSLIST.DAT

Facility: AUTHORIZE, Authorize Utility
Explanation: A general identifier with the specified name and value has been
added to the rights database file (RIGHTSLIST.DAT).
User Action: None.
RDBADDMSGU,

identifier 'id-name' value: '[UIC]' added to RIGHTSLIST.DAT

Facility: AUTHORIZE, Authorize Utility
Explanation: A UIC identifier with the specified name and value has been
added to the rights database file (RIGHTSLIST.DAT).
User Action: None.

2-206

Messages

RDBCREERR,

unable to create RIGHTSLIST.DAT

Facility: AUTHORIZE, Authorize Utility
Explanation: The rights database file, named RIGHTSLIST.DAT, could not
be created. This message should be accompanied by a VMS RMS message
that identifies the specific reason for the error. For example, you cannot
create another rights database file if one already exists, unless you first delete
or rename the original file.
User Action: Correct the condition identified by the RMS message and
reenter your command. If you want to create a new rights database file,
either delete or rename the current one (if you have sufficient privilege to
do so). Once the current file has been deleted or renamed, reenter your
command.
RDBDONEMSG,

rights database modified

Facility: AUTHORIZE, Authorize Utility
Explanation: The rights database file (RIGHTSLIST.DAT) has been modified.
User Action: None.
RDBMDFYERR,

unable to modify identifier 'id-name'

Facility: AUTHORIZE, Authorize Utility
Explanation: The specificied identifier could not be modified. This message
should be accompanied by a VMS RMS message that identifies the specific
reason for the error.
User Action: Correct the condition identified by the RMS message and
reenter your command.
RDBMDFYERRU,

unable to modify identifier '[UIC]'

Facility: AUTHORIZE, Authorize Utility
Explanation: The specified UIC identifier could not be modified. This
message should be accompanied by a VMS RMS message that identifies
the specific reason for the error.
User Action: Correct the condition identified by the RMS message and
reenter your command.
RDBMDFYMSG,

identifier 'id-name' modified

Facility: AUTHORIZE, Authorize Utility
Explanation: The record for the specified identifier in the rights database
file has been modified according to the AUTHORIZE command MODIFY
/IDENTIFIER.
User Action: None.
RDBNOMODS,

no modifications made to rights database

Facility: AUTHORIZE, Authorize Utility
Explanation: The rights database file (RIGHTSLIST.DAT) is not modified.
User Action: None.

2-207

Messages

RDBREMERR,

unable to remove 'id-name' from RIGHTSLIST.DAT

Facility: AUTHORIZE, Authorize Utility
Explanation: The specified identifier could not be removed from the rights
database file (RIGHTSLIST.DAT). This message should be accompanied by a
VMS RMS message that identifies the specific reason for the error.
User Action: Correct the condition identified by the RMS message and
reenter your command.
RDBREMMSG,

identifier 'id-name' value: 'hex code' removed from
RIGHTSLIST.DAT

Facility: AUTHORIZE, Authorize Utility
Explanation: The general identifier with the specified name and hexidecimal
value has been removed from the rights database file (RIGHTSLIST.DAT).
User Action: None.
RDBREMMSGU,

identifier 'id-name' value: '[UIC]' removed from
RIGHTSLIST.DAT

Facility: AUTHORIZE, Authorize Utility
Explanation: The UIC identifier with the specified name and user
identification code has been removed from the rights database file
(RIGHTSLIST.DAT).
User Action: None.
RDDELDATA,

read deleted data address mark

Facility: SYSTEM, VMS System Services
Explanation: This message is associated with read operations on RX02 disk
drives. A sector that has a deleted data address mark is successfully read.
User Action: None.
RDSNONRES,

read data substitute page nonresident

2-208

Messages

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.
READBLOCK,

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 bit map 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.
READBOOT,

error reading boot block, RVN 'n'

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility encountered an error during an attempt
to read the bootstrap block from virtual block 1 of the index file,
[OOOOOO]INDEXF.SYS;l, on the specified relative volume. The accompanying
message provides additional information.
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 bootstrap
block during a bootstrap operation.

2-209

Messages

READCHECK,

read error detected during check on volume 'volume-name'

Facility: EXCHANGE, Exchange Utility
Explanation: While rereading a block in order to perform a data check
operation, the Exchange Utility encountered an input error.
User Action: This message is followed by a second message giving more
specific information about the error discovered by the 1/0 system. Take
corrective action based on the additional message.
READCHECKREC,

read check error recovered on volume 'volume-name'

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility encountered an error while checking a
read on the volume, but the operation succeeded on a retry.
User Action: The file is read successfully, but the user should watch the
volume for further signs of deterioration. Discard or reformat the volume if
errors are frequent.
READDIR,

error reading directory 'directory-name'

Facility: BACKUP, Backup Utility and VERIFY, Verify Utility
Explanation: Either the Backup Utility or the Verify Utility encountered an
error during an attempt to read the specified directory file. The 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.
READERR,

error reading 'filename'

Facility: ACCOUNTING, Accounting Utility
Explanation: An input file specified cannot be read. This message is usually
accompanied by a VMS RMS message indicating the reason for the failure.
User Action: Take corrective action based on the associated message.
READERR,

error reading 'filename'

Facility: SET, SET Facility
Explanation: An error occurred while attempting to read the specified file.
An accompanying message explains why the error occurred.
User Action: Correct the problem described in the accompanying message,
and retry the command.
READERR,

error reading 'filespec'

Facility: MACRO, VAX MACRO Assembler
Explanation: The assembler encountered an 1/0 error when reading an input
source or macro library file; filespec is the file specification of the file being
read.
User Action: Retry the assembly, or create a new copy of the input file and
then retry the assembly.

2-210

Messages

READERR,

error reading 'filespec'

Facility: Shared by several facilities
Explanation: An input file specified cannot be read. This message is usually
accompanied by a VMS RMS message indicating the reason for the failure.
User Action: Take corrective action based on the associated message.

READERR,

error reading 'input-filespec'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: An input file cannot be read. This message should be
accompanied by a VMS RMS message indicating the reason for the failure.
User Action: Follow the recovery procedure for the specified VMS RMS
message.

READERR,

1/0 error reading boot file

Facility: VAXCLUSTER, VAXcluster Facility
Explanation: A hardware error occurred on the satellite system disk.
User Action: Check the error log for the disk. Either run diagnostics on it or
call DIGITAL field service.

READERRREC,

read error recovered on volume 'volume-name'

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility encountered an error while reading the
volume, but the operation succeeded on a retry.
User Action: The file is read successfully, but the user should watch the
volume for further signs of deterioration. Discard or reformat the volume if
errors are frequent.

READERRS,

excessive error rate reading 'save-set-spec'

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

READEVT,

error reading processed event record

Facility: EVL, Event Logger
Explanation: An error occurred while the event receiver is reading incoming
event records. As a result, an event is discarded.
User Action: Submit a Software Performance Report.

2-211

Messages

READFILE,

file ('file-id') 'filename' error reading VBN 'n'

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility encountered an error during an attempt
to read the specified virtual block of the specified file while executing the
/READ_CHECK function. The accompanying message provides additional
information.
User Action: Reconstruct the file from back-up media if necessary.
READHEADER,

error reading file header for 'filename'

Facility: DUMP, File Dump Utility
Explanation: The File Dump Utility encountered an error during an attempt
to read the file header for the specified file. The accompanying message
provides additional information. The File Dump Utility does not display the
file header.
User Action: Correct the condition that caused the error and reenter the
command.
READHEADER,

file ('file-id') 'filename' file header read error

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility encountered an error during an attempt to
read the specified file header from the index file, [OOOOOO]INDEXF.SYS;l, on
the specified relative volume. The accompanying message provides additional
information.
User Action: If the specified file header is currently in use, the file can no
longer be accessed by the operating system and must be reconstructed from
back-up media. If the file header is not in use, no action is necessary because
the operating system will not attempt to use it.
READHOME,

error reading home block, VBN 'n RVN 'n'
,

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility encountered an error during an attempt
to read the home block from the specified virtual block of the index file,
[OOOOOO]INDEXF.SYS;l, on the specified relative volume. The accompanying
message provides additional information.
User Action: The volume probably can be mounted by the operating system
using one of the alternate home blocks. If the error persists, the user should
consider copying the volume to fresh media. If the /REPAIR qualifier is
specified, it is possible that the read error will be cleared when the Verify
Utility rewrites the block.
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, [OOOOOO]INDEXF.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.

2-212

Messages

READIBMAP,

error reading index file bitmap, VBN 'n', RVN 'n'

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility encountered an error during an attempt to
read the index file bitmap from the specified virtual block of the index file,
[OOOOOO]INDEXF.SYS;l, on the specified relative volume. The accompanying
message provides additional information.
User Action: The volume probably can be mounted by the operating system.
However, if the error persists, copy the volume to fresh media or reconstruct
the volume from backup media. If -/REP AIR is specified, the Verify Utility
rewrites the specified virtual block. This may clear the error. If the error
cannot be cleared, rewrite the volume.
READJNLACE,

error reading journal ACE for 'filespec' file ID 'file-id'

Facility: BACKUP, Backup Utility
Explanation: BACKUP could not read the journal Access Control Entry for
the specified file.
User Action: Determine if the ACL could not be written. This could be due
to a corrupted ACL or some other hardware or software related error. Correct
the problem, if possible, and retry the BACKUP operation.
READQUEHEADER,

attempt to read queue header of dscb: 'address'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: An internal VAXTPU failure occurred.
User Action: Submit a Software Performance Report.
READQUOTA,

error reading QUOTA.SYS, VBN 'n'

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility encountered an error during an attempt to
read the specified virtual block of the quota file, [OOOOOO]QUOTA.SYS;l,
on relative Volume 1. The accompanying message provides additional
information.
User Action: If necessary, correct the condition that caused the error and
reenter the Verify Utility command line.
READSBMAP,

error reading storage bitmap, VBN 'n' RVN 'n'

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility encountered an error during an attempt
to read the storage bit map from the specified virtual block of the storage
bit map file, [OOOOOO]BITMAP.SYS;l, on the specified relative volume. The
accompanying message provides additional information.
User Action: The volume probably can be mounted by the operating system.
However, if the error persists, copy the volume to fresh media or reconstruct
the volume from back-up media. If the /REP AIR qualifier is specified, the
Verify Utility rewrites the specified virtual block. This may clear the error. If
the error cannot be cleared, rewrite the volume.

2-213

Messages

READSCB,

error reading storage control block, RVN 'n'

Facility: VERIFY, Verify Utility

Explanation: The Verify Utility encountered an error during an attempt to
read the storage control block from virtual block 1 of the storage bit map file,
[OOOOOO]BITMAP.SYS;l, on the specified relative volume. The accompanying
message provides additional information.
User Action: The volume probably can be mounted by the operating system.
However, if the error persists, copy the volume to fresh media or reconstruct
the volume from back-up media. If the /REPAIR qualifier is specified, the
Verify Utility rewrites the specified virtual block. This may clear the error. If
the error cannot be cleared, rewrite the volume.
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.
READZERO,

read of record id 0, dscb: 'address'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: An internal VAXTPU failure occurred.
User Action: Submit a Software Performance Report.
REAJBCMBX,

error reading job controller mailbox

Facility: JBC, Job Controller
Explanation: The job controller encountered an error reading its mailbox.
The accompanying message provides additional information.
User Action: Take action based on the accompanying message.

2-214

Messages

REALLYQUIT,

buffer modifications will not be saved, continue quitting (Y or N)?

Facility: VAXTPU, VAX Text Processing Utility
Explanation: This message prompts you for confirmation that you want to
execute the built-in procedure QUIT rather than the built-in procedure EXIT.
When you execute the QUIT procedure, your modifications to the buffer are
not saved (written into an output file). In other words, your file remains as it
is prior to the editing session.
User Action: Respond with NO if you change your mind and wish to
continue editing. Respond with YES if you want to complete the built-in
procedure QUIT. You must respond with YES or NO.
REALLYRECOVER,

continue recovery (Y or N) ?

Facility: VAXTPU, VAX Text Processing Utility
Explanation: A condition has been detected that might cause a journal
file inconsistency if you continue. The condition is indicated by a warning
message displayed prior to this prompt.
User Action: Do not continue the recovery if your environment is different
from that of the journaled environment.
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.
REBLDWARN,

insufficient number of bad sector files written to 'device-name'

Facility: BAD, Bad Block Locator Utility
Explanation: When BAD attempted to rebuild the Manufacturer's Detected
Bad Sector File (MDBSF) and the Software Detected Bad Sector File (SDBSF)
on a last track device, it is only successful in writing to half of the last track
or less. This implies that the medium may be unreliable.
User Action: Service the medium (and or drive) to ascertain the reliability
and data integrity.
REBOOT,

this product requires that the system be rebooted.

Facility: VMSINSTAL, Install Procedures
Explanation: The product that is just installed requires the system to be
rebooted to complete the installation.
User Action: Reboot the system after it shuts down.

2-215

Messages

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.
RECISDEL,

deleting a record already marked as deleted

Facility: VAXTPU, VAX Text Processing Utility
Explanation: An internal VAXTPU failure occurred.
User Action: Submit a Software Performance Report.
RECLNG,

file 'filename' has a record of illegal length ('decimal-number')

Facility: LINK, Linker Utility
Explanation: A record in a file is of illegal length.
User Action: Submit a Software Performance Report on the appropriate
language translator.
RECLNG,

illegal record length

Facility: LBR, Librarian Subroutine Package
Explanation: The record length exceeds 512 bytes.
User Action: Reformat the module.
RECLNG,

illegal record length 'nnn' in module 'module-name' in 'library filespec'

Facility: LIBRAR, LIBRARY Command
Explanation: The specified module contains records that exceed the
maximum record length of 2048 bytes.
User Action: Correct the record length before inserting the module in the
library.
Record too big, truncated to 255 characters
Facility: EDT, EDT Editor
Explanation: The file you attempted to edit or to include has lines longer
than 255 characters. EDT deleted all characters from position 256 on because
EDT's line length is limited to 255 characters.
User Action: None.

2-216

Messages

RECORDANS,

auto-answer file will be recorded.

Facility: VMSINSTAL, Install Procedures
Explanation: You specified the auto-answer option when you started
VMSINSTAL. An answer file will be recorded for the product about to be
installed.
User Action: Answer the prompts as usual.
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 writeable, and reenter
the BACKUP command.
RECOVER,

'product-name' is being installed when the system failed.

Facility: VMSINSTAL, Install Procedures
Explanation: The specified product is installed when the system failed
because of a power failure or other problem.
User Action: You will receive additional instructions.
RECOVERABORT,

recovery aborted by journal file inconsistency. Journal file
closed

Facility: VAXTPU, VAX Text Processing Utility
Explanation: An inconsistency is found between what the journal file
contained and what the executing procedure expected. The inconsistency
is explained in the next message. The recovery has aborted, and the journal
file has closed.
User Action: VAXTPU has recovered as much as it can from your journal
file. If the recovered information is sufficient, resume editing from this point.
Otherwise, correct any inconsistencies between the initial terminal state and
the terminal state when you recover your file with the journal file.
RECOVEREND,

recovery complete

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The recovery of a VAXTPU session from a journal file has
completed successfully.
User Action: Resume editing as before the interruption.

2-217

Messages

RECOVERFAIL,

recovery terminated abnormally; journal file inconsistency

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The recovery is probably not being performed on exactly the
same text file as the original VAXTPU session, or the keys may have different
definitions than those used in the original editing session.
User Action: Try the recovery again on the same type of terminal, with the
same terminal setup, using the original input file and command qualifiers.
Enter the DCL command SHOW TERMINAL to determine your current
terminal characteristics.
RECTOBIG,

'record-size' byte record too large for MAIL buffer

Facility: MAIL, Mail Utility
Explanation: MAIL encountered an oversized record during a read operation.
The record is in an illegal format.
User Action: Delete the record.
RECTOOBIG,

record too large in 'filename'

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility discovered a record which is too large for
EXCHANGE to handle.
User Action: The file displayed with the message might be corrupted, or it
might not be in the record format being used by EXCHANGE. Reenter the
command using the correct /RECORD_FORMAT qualifier.
RECTOOSML,

data overflows object record in module 'module-name'

record truncated

Facility: LBR, Librarian Subroutine Package
Explanation: The buffer supplied in the routine is too small for the record.
User Action: Supply a sufficiently large buffer to contain the record.
RECTYP,

file 'filename' has a record of illegal type ('decimal-number')

Facility: LINK, Linker Utility
Explanation: An illegal object record type is encountered.
User Action: Submit a Software Performance Report on the appropriate
language trans la tor.

2-218

Messages

RECTYP, illegal record type 'type' in module 'module-name' in 'library filespec'
Facility: LIBRAR, LIBRARY Command
Explanation: The specified object module contains an illegal record type.
User Action: Recompile the module and reenter the command string.
RECURLEARN,

learn sequence reply halted due to recursion

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The key learn sequence is bound within the learn sequence.
This causes an infinite loop.
User Action: Bind the learn sequence to a different key.
REDCACHE,

volume mounted with reduced cache size

Facility: MOUNT, Mount Utility
Explanation: This informational message occurs when the
/PROCESSOR=UNIQUE qualifier is used with the MOUNT command 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.
User Action: The usual reason to use the /PROCESSOR=UNIQUE qualifier
before VMS 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 VMS 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 with specific volumes, instead of all volumes sharing the same
IfO buffer cache, which is the default behavior.
Therefore, the recommended action is to 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.
REDEFSYM,

redefining symbol 'symbol-name' from 'addrl' to 'addr2'

Facility: PATCH, Patch Utility
Explanation: A user-defined symbol is changed to a different value. This
typically occurs when you enter the PATCH command DEFINE and specify
a symbol currently used in the image file, or when PATCH moves a VAX
MACRO instruction that contains a label to a patch area.
User Action: None.

2-219

Messages

REENT,

file could not be renamed and recovery failed; file has been lost

Facility: RMS, VMS Record Management Services
Explanation: A VMS RMS $RENAME operation failed and the attempt to
recover the file's directory entry also failed. The file has become a lost file.
User Action: Either use the ANALYZE/DISK/REPAIR Utility to recover the
lost file, or ask your system manager to recover the file.

REENTER,

please reenter last line as it is ignored

Facility: MAIL, Mail Utility
Explanation: MAIL encountered an illegal escape sequence during a send
operation. The line containing the illegal escape sequence is ignored.
User Action: Reenter the line without illegal escape sequences.

REENTRANCY,

reentrancy detected

Facility: LIB, Library Facility
Explanation: This message indicates reentrant invocation of a routine.
User Action: Begin debugging procedures to verify and correct the problem.
Whenever reentrancy is possible, such as at AST level, it is strongly
recommended that users take appropriate action to ensure that their code
executes properly in the event of reentrancy.

REF, invalid key-of-reference= 'nnn'
Facility: RMS, VMS Record Management Services
Explanation: The key-of-reference number specified in a key definition XAB
is either greater than 254 or not a defined key for the file.
User Action: The status value (STV) field of the FAB provides the key of
reference of the XAB in error. Verify that the call to the VMS RMS service is
coded correctly.

REFCNTNEG,

PFN reference count is negative

Facility: BUGCHECK, System Bugcheck
Explanation: The VMS software detected an 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, 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 on the BACKUP command
that produces the save set included with the SPR.)

2-220

Messages

REFERENCED,

existing references prevent deletion

Facility: JBC, Job Controller
Explanation: The specified form or queue cannot be deleted because of
existing references to the form or queue by other queues or jobs.
User Action: Use the SHOW QUEUE/FULL command to locate all such
references, remove them, and reenter the DELETE/FORM or DELETE
/QUEUE command.
REFRESH_NEEDED,

screen refresh needed

Facility: VAXTPU, VAX Text Processing Utility
Explanation: This is an internal status message, which indicates that the
screen needs to be refreshed.
User Action: None.
REFUSED,

you cannot attach to that process

Facility: CU, Command Language Interpreter (DCL)
Explanation: Either you have attempted to attach to a process that is your
own process or that is not part of your process tree. You cannot perform the
attempted operation.
User Action: None.
REGOPSYNX,

Facility: MACRO, VAX MACRO Assembler
Explanation: The addressing mode syntax contained an error.
User Action: Correct the addressing mode syntax.
REJECT,

connect to network object rejected

Facility: SYSTEM, VMS System Services
Explanation: A request to connect to an object at a remote node failed for
one of the following reasons:
•

The object requested does not exist.

•

The access control information specified is invalid.

•

The partner NSP has no resources.

•

The partner task exited during the connect sequence.

•

The partner task rejected the connect.

User Action: Determine which reason caused the failure and try to correct
the condition.
RELCONCAT,

relative file cannot be concatenated

Facility: Shared by several facilities
Explanation: A relative file may not be concatenated with another file.
User Action: Use a program to load the relative file.

2-221

Messages

RELINK,

file 'filename' contains deferred relocation. Relink 'filename' and all
images linked against it

Facility: LINK, Linker Utility
Explanation: The specified shareable image file is linked under the VMS
Version 2.0 or Version 2.1 linker.
User Action: Relink the specified shareable image.
RELMOVED,

the product's release notes have been successfully moved to
SYS$HELP.

Facility: VMSINSTAL, Install Procedures
Explanation: VMSINSTAL moved the product's release notes file to
SYS$HELP.
User Action: Contact your local DIGITAL sales representative.
REMABO,

remote node not defined

Facility: NCP, Network Control Program
Explanation: The remote node specified in the NCP command COPY is not
defined in the local node database. If the /WITH qualifier is included in the
COPY command, the remote node is not placed in the local database.
User Action: None is required; however, if you have sufficient privilege, you
may want to add the remote node to the local node database.
REMDEF,

the DEFAULT record may not be removed

Facility: AUTHORIZE, Authorize Utility
Explanation: You attempted to remove the DEFAULT record.
User Action: Do not attempt to remove the DEFAULT record.
REMERR,

error removing 'filename'

Facility: SET, SET Facility
Explanation: An error occurred while trying to remove the specified file.
This message is issued with an accompanying message.
User Action: Take corrective action based on the accompanying message.
REMERR,

unable to delete record

Facility: AUTHORIZE, Authorize Utility
Explanation: This message is issued with other messages.
User Action: Take corrective action based on the accompanying messages.
REMMSG,

record removed from SYSUAF.DAT

Facility: AUTHORIZE, Authorize Utility
Explanation: This message is informational.
User Action: None.

2-222

Messages

REMOINSF,

node name specification or /REMOTE missing from command line

Facility: PRINT, PRINT Command and SUBMIT, SUBMIT Command
Explanation: To print or submit a file residing on a remote node for
processing on that node, the /REMOTE qualifier must be included in the
PRINT or SUBMIT command and the file specification must contain the
remote node name. Conversely, to print or submit a file without using the
network, the /REMOTE qualifier cannot be used with the PRINT or SUBMIT
command and the file specification cannot include a node name.
User Action: Correct the error and reenter the command.

REMOTE,

assignment completed on remote node

Facility: SYSTEM, VMS System Services
Explanation: An assignment for a transparent connect on a remote node
completed successfully.
User Action: None.

Remote System Conflicts with Known System
Facility: VAXport, 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 VAXcluster and two systems with
conflicting identity are polling when any other virtual circuit failure takes
place in the VAXcluster, then systems in the VAXcluster may crash with a
CLUEXIT bugcheck.

REMOUVOL,

REMOUNT relative volume nn (volume label) on 'device-name'

Facility: MOUNT, Mount Utility
Explanation: An error has 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.

REMOVE,

file ('file-id') error removing directory entry

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility encountered an error during an attempt to
remove a directory entry referencing the specified file identification. The
accompanying message provides additional information.
User Action: Correct the condition that caused the error and reenter the
Verify Utility command line.

2-223

Messages

REMOVED,

'directory-name' removed

Facility: SET, SET Facility
Explanation: The requested directory is removed successfully.
User Action: None.

REMOVED,

entry for 'filespec' has been removed

Facility: INSTALL, Install Utility
Explanation: The Known File Entry is successfully removed. This is an
informational message.
User Action: None.

REMOVED,

symbol 'symbol-name' removed from 'library-name'

Facility: LIBRAR, LIBRARY Command
Explanation: This success message is generated by the DCL command
LIBRARY.
User Action: None.

REMRSRC,

insufficient system resources at remote node

Facility: SYSTEM, VMS System Services
Explanation: An attempt is made to initiate a DECnet-VAX logical link
connection. The remote process encountered a resource allocation failure
while trying to confirm the logical link.
User Action: This condition is often temporary. If the condition persists
after repeated retries, the remote process should be run under an account
with higher quotas. Refer to the VMS Networking Manual for additional
information.

REMSYS,

the SYSTEM record may not be removed

Facility: AUTHORIZE, Authorize Utility
Explanation: You attempted to remove the SYSTEM record.
User Action: Do not attempt to remove the SYSTEM record.

RENAMED,

'filespec' renamed to 'filespec'

Facility: Shared by several facilities
Explanation: This message is associated with the execution of a DCL
command RENAME. The name of the first file is changed to the name
given in the second file specification.
User Action: None.

RENDEF,

the DEFAULT record may not be renamed

Facility: AUTHORIZE, Authorize Utility
Explanation: You attempted to rename the DEFAULT record.
User Action: Do not attempt to rename the DEFAULT record.

2-224

Messages

RENMSG,

user record renamed

Facility: AUTHORIZE, Authorize Utility
Explanation: This message is informational.
User Action: None.
RENSYS,

the SYSTEM record may not be renamed

Facility: AUTHORIZE, Authorize Utility
Explanation: You attempted to rename the SYSTEM record.
User Action: Do not attempt to rename the SYSTEM record.
REPEAT,

parameter repeated

Facility: NCP, Network Control Program
Explanation: A parameter is repeated in the command. A parameter may
appear only once in a command.
User Action: Reenter the command without repeating parameters.
REPLACED,

module 'module-name' replaced in 'library-name'

Facility: LIBRAR, LIBRARY Command
Explanation: This success message is generated by the DCL command
LIBRARY.
User Action: None.
REPLACED,

'output-filespec' being replaced

Facility: Shared by several facilities
Explanation: An output file is replaced successfully by a new version.
User Action: None.
REPLACEERR,

replacement value too large for location

Facility: PATCH, Patch Utility
Explanation: When you replaced data with the PATCH utility command
REPLACE, the new data contained more bytes than the old data.
User Action: Correct and reenter the command.
REPLACERR,

error replacing 'module-name' in 'library-name'

Facility: LIBRAR, LIBRARY Command
Explanation: An error occurred during a module replacement operation.
Either a VMS RMS error occurred or enough virtual memory is not available.
User Action: Ensure that the new file in the replacement operation is not
corrupt.

2-225

Messages

REPLAYFAIL,

an inconsistency has been discovered, halting execution

Facility: VAXTPU, VAX Text Processing Utility
Explanation: A learn sequence stopped executing. The sequence of
keystrokes that is saved is inconsistent with the current actions. This is
probably because some keys have different definitions now than when the
learn sequence is created.
User Action: None is required. However, if you suspect that the replay of
the learn sequence may have altered parts of your text incorrectly, check the
text for changes.
REPLAYWARNING,

an inconsistency has been discovered, continuing execution

Facility: VAXTPU, VAX Text Processing Utility
Explanation: During the execution of a learn sequence, an inconsistency is
discovered between the original actions and the current ones. It is possible
to continue execution, but the results may not be those expected. This is
probably because some keys have different definitions now than when the
learn sequence is created.
User Action: None is required. However, if you suspect that the learn
sequence did not complete correctly, check the text where the learn sequence
is replayed.
REQDITEMMISS,

required item not in item list for call

Facility: SMI, System Management Intergator/Server
Explanation: This message indicates an internal error. An SMI call specifies
an item list within which an item required for the given object and that
function is not present.
User Action: Submit a Software Performance Report showing the exact
sequence of SYSMAN commands leading to the error.
REQFILMIS,

requested file is missing from input file 'filename'

Facility: MONITOR, Monitor Utility
Explanation: The data describing the file requested with the /FILENAME
qualifier did not exist in the input file.
User Action: Correct the /FILENAME qualifier specification and reenter the
MONITOR command.
REQKEY,

at least one keyword must be specified for type 'type-name'

Facility: CDU, Command Definition Utility
Explanation: CDU encountered a type definition with no keywords.
User Action: Edit the CLD file so that each DEFINE TYPE command includes
at least one keyword.

2-226

Messages

REQPRMABS,

required parameter is absent

Facility: CU, Command Language Interpreter (DCL)
Explanation: You did not enter a required qualifier for a DCL command.
User Action: Refer to the VMS DCL Dictionary for the command and reenter
it using all the required qualifiers.
REQUEST,

service required on queue 'name' for job 'number' user 'name'

Facility: JBC, Job Controller
Explanation: In response to the /OPERATOR qualifier of the PRINT
command, this message is displayed at the operator's terminal. This message
is followed by the text specified with the /OPERATOR qualifier.
User Action: Take the reqested action and enter a START/QUEUE command
to restart the queue.
RER,

file read error

Facility: RMS, VMS Record Management Services
Explanation: Either VMS RMS could not read an input file, or a terminal
read error occurred.
User Action: If VMS RMS could not read the input file, the status value
(STV) field of the RAB contains a system status code that provides more
information about the condition. Take corrective action based on this status
code.
If a terminal read error occurred, reenter the input line.

RESERR,

resource error

Facility: NCP, Network Control Program
Explanation: A resource necessary to complete the command, for example,
the system resource nonpaged pool, is not available.
User Action: Determine why the resource is not available.
RESET,

circuit is reset

Facility: SYSTEM, VMS System Services
Explanation: The virtual circuit is reset while this request is being processed,
or the circuit is in the process of being reset when you issued the request.
User Action: Initialize the circuit and retry the call.
RESETQUE,

error resetting queue 'queue-name'

Facility: JBCUPGRAD, Queue Upgrade Utility
Explanation: An error occurred during a $SNDJBC system service call
attempting to reset the queue.
User Action: The accompanying message gives information about why the
operation failed. Correct the problem and retry the upgrade.

2-227

Messages

RESIGNAL,

resignal condition to next handler

Facility: SYSTEM, VMS System Services
Explanation: A condition handler completed without terminating or
continuing the image. This message is associated with an exit status code
used by condition handling routines to indicate that the exception dispatcher
continued its search for handlers.
User Action: None, this message is not normally displayed.

RESOPCODE,

opcode 'xx' is reserved

Facility: PATCH, Patch Utility, DEBUG, VMS Debugger
Explanation: You specified an opcode that is reserved for DIGITAL use only.
User Action: None.

Response Queue Remove Failure
Facility: VAXport, 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 (11/780), CMI (11/750), or BI (8200,
8300, and 8800) contention.
User Action: Call DIGITAL field service.

RESTARTCOM, Job Controller abort/restart action complete, queue manager
restarted
Facility: JBC, Job Controller
Explanation: This message is signaled to the console terminal to inform
the system manager that the job controller has recovered from a fatal error
condition and has restored the batch/print queue environment. Recovery
entails having the job controller respond to a fatal error by aborting itself,
restarting itself in the context of a new process, and reopening the system
queue file (if the /RESTART qualifier was used initially with the START
/QUEUE/MANAGER command). Look for a "JBC-F-" message preceeding
this message on the console or an operator's terminal to find out what error
condition caused the job controller to voluntarily abort and restart itself.
User Action: None.

RESTORE, restoring product save set 'letter' ...
Facility: VMSINSTAL, Install Procedures
Explanation: The Backup Utility is restoring the product save set that you
specified from the distribution media.
User Action: None.

2-228

Messages

RESTOREFAIL,

error during RESTORE operation

Facility: VAXTPU, VAX Text Processing Utility
Explanation: An error occurred while VAXTPU is restoring a section file.
This message should be accompanied by a VMS RMS message identifying the
reason for the error.
User Action: Check the directory specification, the file protection, or any
other item specified in the accompanying VMS RMS message to make sure
that you are trying to restore a valid section file.

RESTRICT,

UAF restricts access at this time, please log out immediately

Facility: JBC, Job Controller
Explanation: The User Authorization File record for the owner of the
interactive or batch process does not allow access to the system at the current
time. A short time after this warning is issued, the job controller will delete
the process.
User Action: Close your files and logout immediately.

RESULTOVF,

resultant string overflow

Facility: SYSTEM, VMS System Services
Explanation: A user buffer specified to receive data from the system is not
long enough. The system does not truncate the data because the loss of data
will damage its integrity.
User Action: Check for a programming error. Verify that character string
descriptors for output data buffers reflect the correct lengths.

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.

RETURNED,

control returned to process 'process-name'

Facility: CLI, Command Language Interpreter (DCL)
Explanation: This message is output by DCL when you log out of a spawned
process.
User Action: None.

REVERSECASE,

CASE limits were reversed

Facility: VAXTPU, VAX Text Processing Utility
Explanation: A CASE statement is found with the upper and lower label
value reversed. A CASE statement must specify the lower value first.
User Action: Reverse the CASE values and recompile your program.

2-229

Messages

REVOKEERR,

unable to revoke identifier 'id-name' from 'user ID '

Facility: AUTHORIZE, Authorize Utility
Explanation: The specified identifier could not be revoked from the specified
user.
User Action: Make sure that the user has been granted the identifier you
are trying to revoke. Use the AUTHORIZE commands SHOW /IDENTIFIER
/FULL or LIST /IDENTIFIER/FULL to display an identifier and the users who
hold it.
REVOKEMSG,

identifier 'id-name' revoked from 'user-name'

Facility: AUTHORIZE, Authorize Utility
Explanation: The specified identifier has been revoked from the specified
user. The user no longer has the rights associated with the identifier.
User Action: None.
REWIND,

the tape will be rewound to try again.

Facility: VMSINSTAL, Install Procedures
Explanation: VMSINSTAL is attempting to restore a product save set with
the Backup Utility. It could not find the required save set on the distribution
tape that is mounted. VMSINSTAL will rewind the tape in case the save sets
were not recorded in order.
User Action: None. Ignore any accompanying BACKUP messages.
REX,

record already exists

Facility: CONVERT, Convert Utility
Explanation: You have tried to write a record into a relative file cell that
already contains a record.
User Action: Delete the record and try again.
REX,

record already exists

Facility: RMS, VMS Record Management Services
Explanation: A $PUT operation using random record access mode to a
relative file specified an existing record in the target record cell. The new
record is not written.
User Action: Modify the program, if necessary, to detect and respond to the
condition. You may want to include the UIF option in the ROP parameter for
the file.
RFA,

invalid record file address (RFA)

Facility: RMS, VMS Record Management Services
Explanation: The record file address field of the RAB contains a zero value
for RFA access in a $GET or $FIND operation.
User Action: Verify that the call to the VMS RMS service is coded correctly.

2-230

Messages

RFAERR,

RMS error using RF A access: RF A = xxxxxx, xxx

Facility: SEARCH, SEARCH Command
Explanation: SEARCH received an error from VMS RMS when trying to
position to the start of a window. This message is accompanied by other
messages.
User Action: If the file being searched is on another network node, and one
of the additional messages is "network operation not supported", then retry
the command without the /WINDOW qualifier.
Otherwise, if the error is reproducible, notify your system manager to submit
a Software Performance Report. The numbers displayed with the error
message and the file being searched should be included with the Software
Performance Report.
RFAPASTEOF,

VBN in map block request past EOF

Facility: LBR, Librarian Subroutine Package
Explanation: An unexpected internal consistency check occurred. One cause
of this problem is insufficient virtual memory when creating or compressing a
large library. Another cause is a corrupt library file.
User Action: Inform your system manager and submit a Software
Performance Report. If you are inserting or replacing a large number of
modules, you may be successful by performing the operation in several
pieces. If you are compressing a large library, your System Manager may
have to increase your PGFLQUO and/ or increase the SYSGEN parameter
VIRTUALPAGECNT.
RFLOC,

unable to locate related file

Facility: FDL, Create/FDL Utility
Explanation: The file that you specified with the AREA POSITION FILE_
NAME or FILE_ID attribute cannot be found.
User Action: Check on the location of the desired file, or else specify a
different FILE_NAME or FILE_ID.
RFM,

invalid record format
Facility: RMS, VMS Record Management Services
Explanation: The record format field of the FAB does not contain a valid
value. The valid values for this field are FIX, STM, STMCR, STMLF, VAR,
VFC, and UDF.
User Action: Verify that the call to the VMS RMS service is coded correctly.

RHB,

invalid record header buffer
Facility: RMS, VMS Record Management Services
Explanation: The record header buffer address of the RAB specifies an area
of memory that cannot be accessed correctly by the caller.
User Action: Verify that the call to the VMS RMS service is coded correctly.

2-231

Messages

RLF,

invalid related NAM block
Facility: RMS, VMS Record Management Services
Explanation: The address of the NAM block for a related file is nonzero but
it does not point to a valid related file NAM block with a valid resultant name
string. Or, too many related blocks have been chained together or the related
NAM blocks have been chained together.
User Action: Verify that the call to the VMS RMS service is coded correctly.

RLK,

target record currently locked by another stream
Facility: RMS, VMS Record Management Services
Explanation: The target record is locked by another stream.
User Action: Modify the program, if necessary, to detect and respond to the
condition.

RLSTMSG,

listing file RIGHTSLIST.LIS complete

Facility: AUTHORIZE, Authorize Utility
Explanation: The contents of the rights database file (RIGHTSLIST.DAT)
have been written to the listing file named RIGHTLIST.LIS.
User Action: None.

RMS,

record caused RMS severe error
Facility: CONVERT, Convert Utility
Explanation: This message will be accompanied by an RMS error message
that explains the error.
User Action: Correct the error specified by the RMS error message and try
again.

RMSBUG,

RMS has detected an invalid condition

RMSERROR,

RMS service error

Facility: Shared by several facilities
Explanation: An error is encountered during a VMS RMS operation. A
subsequent message explains the reason for the error.
User Action: Retry the operation; refer to the VMS Record Management
Services Manual for more information.

2-232

Messages

RMSFILINI,

error occurred during RMS file initialization 'filename' on node
'nodename'

Facility: MONITOR, Monitor Utility
Explanation: An error occurred while the Monitor Utility tried to set up the
specified file for statistics monitoring. Check the accompanying messages for
more details.
User Action: Correct the problem specified with the accompanying messages
and reenter the MONITOR command.

RMSFILMIS,

1 or more requested RMS files are missing from input file

Facility: MONITOR, Monitor Utility
Explanation: The data describing one or more files requested with the
/FILENAME qualifier did not exist in the input file.
User Action: Correct the /FILENAME qualifier specification and reenter the
MONITOR command.

RMV,

ACP remove function failed

Facility: RMS, VMS Record Management Services
Explanation: A file could not be removed or renamed correctly. This message
is associated with a system status code returned from a file system ACP QIO
request made by RMS.
User Action: The status value (STY) field of the FAB contains a system status
code that provides more information about the condition. Take corrective
action based on this status code.

RNF,

record not found
Facility: RMS, VMS Record Management Services
Explanation: A requested record could not be located in a $FIND or $GET
operation on a relative or indexed file. Either the record is never written or it
has been deleted.
User Action: Modify the program, if necessary, to detect and respond to the
condition.

RNL,

record not locked
Facility: RMS, VMS Record Management Services
Explanation: The record specified for a VMS RMS $FREE or $RELEASE
operation is not locked.
User Action: Modify the program, if necessary, to detect and respond to the
condition.

ROP,

invalid record options
Facility: RMS, VMS Record Management Services
Explanation: An incorrect record option (ROP) is specified.
User Action: Verify that the call to the VMS RMS service is coded correctly.

2-233

Messages

ROPRAND,

reserved operand fault at PC 'location', PSL = 'xxxxxxxx'

Facility: SYSTEM, VMS System Services
Explanation: An instruction contains an operand in a format that is not
acceptable. This message indicates an exception condition and is usually
followed by a display of the condition arguments, registers, and stack at the
time of the exception.
User Action: Check for a programming error. Examine the PC and virtual
address displayed in the message to determine the instruction that caused the
error.
ROPRAND,

utility converted a reserved operand to a valid value

Facility: SORT, Sort/Merge Utility
Explanation: SORT /MERGE has detected decimal data that contains an
invalid sign or digit, or data that contains a floating reserved operand. The
error is corrected, and processing continues.
User Action: None.
ROUTREQ,

line 'line-number': A ROUTINE clause is only valid when generating
an object file

Facility: CDU, Command Definition Utility
Explanation: CDU did not encounter a ROUTINE clause while attempting
to generate an object file. A ROUTINE clause is required for object file
generation.
User Action: Edit the CLD file so that a ROUTINE clause is present if object
file generation is desired.
RPCERR,

an internal interprocess communications error has occurred

Facility: DEBUG, VMS Debugger
Explanation: An internal communications error has occurred. The reason is
given in the message following this message.
User Action: If the error is reproducible, submit a Software Performance
Report and, if possible, enclose both a copy of the program being debugged
and a logged debugging session that reproduces the error.
RPL,

error detected while reading prolog
Facility: RMS, VMS Record Management Services
Explanation: An 1/0 error occurred during an attempt to read the file's
pro log.
User Action: Depending on the operation, the status value (STV) field in
the FAB or RAB contains a system status code that provides additional
information about the condition. Take corrective action based on this status
code.

2-234

Messages

RPTCNTNABS,

repeat count not absolute

Facility: MACRO, VAX MACRO Assembler
Explanation: The repeat count in a .REPEAT, .SIGNED_BYTE, or .SIGNED_
WORD directive contained an undefined symbol or is a relative expression.
User Action: Replace the expression with an absolute expression that does
not contain any undefined symbols.

RQSTABORT,

'request', 'time', request 'number' aborted by operator 'operatorname'

Facility: OPCOM, Operator Communication
Explanation: A request to an operator is denied by the DCL command
REPLY/ ABORT.
User Action: None.

RQSTCAN,

request 'nnn' is canceled

Facility: OPCOM, Operator Communication
Explanation: A request to an operator is successfully canceled.
User Action: None.

RQSTCMPLTE,

request 'nnn' complete by operator 'operator-name'

Facility: OPCOM, Operator Communication
Explanation: An operator has completed a user's request successfully; the
dialog between the user and the operator is complete. This message indicates
success.
User Action: None.

RQSTDONE,

request 'number' is satisfied

Facility: OPCOM, Operator Communication, MOUNT, Mount Utility
Explanation: The request completed successfully and is canceled by the
requestor.
User Action: None.

RQSTPEND,

request 'nnn' pending by operator 'operator-name'

Facility: OPCOM, Operator Communication
Explanation: An operator responded to a user's request with the DCL
command REPLY/PENDING. The operator will respond to the request when
able to do so. This message is informational. If the request must be satisfied
immediately, use CTRL/C to interrupt the request and send another message.
User Action: None.

2-235

Messages

RQSTSTST,

request status for request 'number'

Facility: OPCOM, Operator Communication
Explanation: This message provides the operator with additional, detailed
information about the request.
User Action: None.
RRV,

invalid RRV record encountered

Facility: RMS, VMS Record Management Services
Explanation: An invalid record reference vector (RRV) record is detected.
This indicates either a previous failure to update RRV records (see RVU error
message) or a VMS RMS or system software error.
User Action: Reorganize the file using the CONVERT command. If a
software error is suspected, collect as much information as possible and
submit a Software Performance Report.
RSA,

record stream currently active

Facility: RMS, VMS Record Management Services
Explanation: An attempt is made to issue a VMS RMS record operation to
a record stream that has an outstanding request. The outstanding operation
may be asynchronous; or the failed operation was attempted at an AST level,
or in an inner access mode.
User Action: Note the condition. Modify the source program, if necessary, to
detect and respond to the condition. Enter a $WAIT request before entering
any additional requests.
RSBREFNEG,

RSB reference count negative

tried to deallocate RSB with non-zero ref. count

2-236

Messages

RSK,

record shorter than primary key

Facility: CONVERT, Convert Utility
Explanation: The record does not contain enough data to fill the primary key
field in the indexed output file.
User Action: Compare the layout of the input and output records, and
change one or the other to completely fill the primary key field of the output
records with data.
RSL,

invalid resultant string length

Facility: RMS, VMS Record Management Services
Explanation: The VMS RMS NAM block contains an invalid value in
the resultant string length field for an operation (for example, $ENTER,
$REMOVE, or $SEARCH) in which this field is a required input. This field is
generally filled in by a previous $CREATE, $OPEN, or $SEARCH operation.
User Action: Verify that the call to the VMS RMS service is coded correctly.
RSLOVF,

buffer overflow-specify fewer command elements

Facility: CU, Command Language Interpreter (DCL)
Explanation: The buffer used by the command interpreter to store a
command string during parsing has overflowed.
User Action: Simplify the command.
RSS,

invalid resultant string size

Facility: RMS, VMS Record Management Services
Explanation: The resultant string area size does not define a buffer large
enough to receive the resultant file specification string being returned from a
VMS RMS operation.
User Action: Verify that the call to the VMS RMS service is coded correctly.
RST,

invalid resultant string address

Facility: RMS, VMS Record Management Services
Explanation: The resultant string area address in the NAM block specifies an
address that is in an area of memory that cannot be written by the caller.
User Action: Verify that the call to the VMS RMS service is coded correctly.
RSTERR,

error in symbol table

Facility: DEBUG, VMS Debugger
Explanation: There is a format error in the symbol table.
User Action: If the format error is not caused by a user program error or a
DEPOSIT command, submit a Software Performance Report.

2-237

Messages

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.
RSZ,

invalid record size
Facility: RMS, VMS Record Management Services
Explanation: The record size (RSZ) field of the RAB contains an invalid value
for one of the following reasons:
•

The record size value is greater than the maximum record size specified
for the file.

•

The record size value is not the correct size for fixed length records.

•

The record size value is not large enough to contain the primary key for
an indexed file.

•

The record size value is different than the original record size of a
$UPDATE operation on a sequential file.

The maximum record size value must be in the range of 1 through 32,767 for
the $PUT and $UPDATE services, and in the range of 1 through 65,535 for
the $WRITE service.
User Action: Verify that the call to the VMS RMS service is coded correctly.
RSZ,

invalid record size
Facility: CONVERT, Convert Utility
Explanation: The record is either too long to fit in the specified bucket size
(relative and indexed files), or it is longer than 512 bytes and block spanning
is not allowed.
User Action: Make the bucket size larger or specify block spanning.

RT11_BADDIRECT,

volume 'volume-name' has invalid RT-11 directory

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility has discovered an error in the directory
structure on the specified volume.
User Action: The volume is either not an RT-11 volume, or it is seriously
corrupted.
RT11_BADFILE,

bad block file created to cover bad block 'block'

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility has created a file named FILE.BAD to
cover the listed bad block.
User Action: The user should watch the volume for further signs of
deterioration. Discard or reformat the volume if errors are frequent.

2-238

Messages

RTl l_BIGBADFILE,

directory segment full, file has some good blocks

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility created a larger than necessary bad block
file because the volume directory is full.
User Action: The user should watch the volume for further signs of
deterioration. Discard or reformat the volume if errors are frequent. Look at
the error message for RTl l_OVERFLOW for tips on making space available.
RTl l_DIRSIZE,

volume 'volume-name' has directory showing 'number' blocks
on a 'numeric-string' block device

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility discovered a mismatch between the size
of directory and the size of the device.
User Action: The volume has an error in structure. EXCHANGE will not
write to the volume, but it will read the volume. If another computer system
consistently produces volumes which give this error, it should be possible to
initialize a volume with EXCHANGE and take the EXCHANGE-initialized
volume to the other system. With the EXCHANGE-initialized volume, you
will be able to transfer files between the two systems in both directions.
RTl l_ERRLOCK,

volume will be write-locked to prevent corruption

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility has write-locked a volume because of a
structure error.
User Action: EXCHANGE has discovered a structure error, and is refusing
to write to the volume so that the error will not be made worse. It
should be possible to read some or all of the files on the disk. The
Exchange Utility can be used to save all of the files on the volume, and
then recreate the volume without any errors. Look at the command file
SYS$UPDATE:CONSCOPY.COM to see how VMS uses EXCHANGE to
make copies of the console device for some VAX processors.
RTl l_EXTRA,

extra words set to maximum of 119

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility reduced the value on a /EXTRA_WQRDS
qualifier to the maximum allowed.
User Action: In the future, use a smaller value for extra words.
RTl l_NOEND,

segment end marker is missing from RT-11 directory

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility discovered that an RT-11 directory
segment did not have a proper entry marking the end of the segment.
User Action: EXCHANGE will assume that the last valid entry in the
directory is the end, and will allow you to read the volume.

2-239

Messages

RTl LOVERFLOW,

directory is full, unable to add file

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility is unable to add a file to an RT-11
directory because there is no space.
User Action: Directory space can be made available by deleting files from
the volume. It might also be possible to use the EXCHANGE INITIALIZE
command and the /SEGMENTS qualifier to recreate the volume with more
directory segments. See the command file SYS$UPDATE:CONSCOPY.COM
for an example of how to save a volume as a virtual device, reinitialize the
volume, and copy all the files back to the original volume.

RTl l_STBLOCK,

file start block-segment header inconsistent

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility discovered a mismatch between a stored
block number and the value EXCHANGE computed.
User Action: EXCHANGE will use the stored value as the correct value.
Note that it is possible that there may be missing space or overlapping files
on the volume.

RTl l_TOOMANYBLK,

too many blocks, using maximum allocation of 'xx'

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility has reduced the /ALLOCATION value to
the value shown.
User Action: /ALLOCATION values cannot be larger than the device or
65,535, whichever is smaller.

RTl l_TOOMANYSEG,

too many segments, reducing to 'xx'

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility reduced the value on a /SEGMENTS
qualifier to the maximum allowed.
User Action: In the future, use a smaller value for /SEGMENTS.

RTll_UNKENT,

entry with unknown format in directory

Facility: EXCHANGE, Exchange Utility
Explanation; The Exchange Utility found a directory entry which had an
unexpected format.
User Action: EXCHANGE will refuse to write to the volume, but will attempt
to read the volume and make what sense of the volume that it can. See the
explanation for the RTl l_ERRLOCK for information on how to restore the
volume.

2-240

Messages

RTB,

nnn byte record too large for user's buffer

Facility: RMS, VMS Record Management Services
Explanation: A record returned from a $GET operation is too large for the
user buffer provided. The status value (STV) field of the RAB contains the
size of the record that is too large; the returned record is truncated to the size
of the user buffer.
User Action: Correct the program by providing a larger buffer.
RTL,

input record too long: truncated string

Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: Too many characters were entered on a single input line; the
excess has been discarded.
User Action: Divide the record into several smaller ones.
RTL,

record longer than Maximum Record Length

Facility: CONVERT, Convert Utility
Explanation: The record from the input file is longer than the maximum
record length specified in the output file. This is an exception condition; the
record will not be written to the output file. If the /EXIT qualifier is specified,
processing will stop.
User Action: Specify the /TRUNCATE qualifier.
RTNERROR,

unexpected error status from user-written routine

Facility: SORT, Sort/Merge Utility
Explanation: A user-written comparison or equal-key routine returned an
unexpected error status.
User Action: Correct your comparison or equal-key routine.
RTOUTEOF,

1
,

end-of-file on output filespec insufficient space on volume

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility ran out of space while copying an RT-11
file.
User Action: RT-11 only supports contiguous files, therefore there must be a
free space on the volume as large as the file you are trying to copy. Use the
DIRECTORY/ ALL command to see where the unused areas on the volume
are. By deleting unneeded files that are adjacent to unused areas, it might be
possible to create a large enough space. Also, if you use the COPY command
to copy a file to the same volume, you can move files around and make larger
free areas.
11

2-241

Messages

RTPROTECT,

file is protected against modification

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility rejected a command to modify a protected
file.
User Action: If the file should be modified, use the EXCHANGE RENAME
/NOPROTECT command to remove the protection from the file. Then
reenter the command.

RTS,

record too short for fixed record format file
Facility: CONVERT, Convert Utility
Explanation: The record in the input file is shorter than the fixed-length
specified in the output file. This is an exception condition; the record will not
be written. If the /EXIT qualifier is specified, then processing will stop.
User Action: Specify one of the /PAD qualifier options.

RUCONFLICT,

another facility has active recovery units on file

Facility: SYSTEM, VMS System Services
Explanation: The file cannot be accessed because another facility (such
as RMS) has been updating the file using recovery units, and the file is
potentially in an inconsistent state.
User Action: If the file must be accessed (such as for BACKUP), either the
file must be made consistent or, in an emergency, the recovery units must be
turned off.
If the file is still accessed by another facility, stopping the applications using
the facility should return the file to a consistent state. For RMS files, closing
the file or running down the process restores the file to a consistent state and
turns off recovery units.
If the file is not accessed by another facility, the recovery procedure for the
facility that has recovery units on the file should be invoked to restore the file
to a consistent state. For RMS files, typing the file or opening the file with
RMS recovers the file automatically.
If the file cannot be restored to a consistent state, or if you want to access
the file without regard to consistency, use the SET FILE command with the
/RU_FACILITY and /RU_ACTIVE qualifiers to turn off recovery units. For
example, if RMS has active recovery units on the file EXAMPLE.DAT, and
you wish to turn off recovery units, enter the following command:
$ SET FILE EXAMPLE.DAT/RU_FACILITY=RMS/NORU_ACTIVE

2-242

Messages

RUF,

fatal error detected by Recovery Unit Facility
Facility: BUGCHECK, System Bugcheck
Explanation: The VMS 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, 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 on 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 online; if not,
mount it and reenter the command. Verify the device names and volume
labels specified in the command and retry the operation.
RVU,

error updating RRV's, some paths to data may be lost
Facility: RMS, VMS Record Management Services
Explanation: VMS RMS failed to update all record reference vectors (RRVs)
when a $PUT or $UPDATE service caused a bucket split. This error is usually
caused by a hardware or system software error during VMS RMS RRV
updating. All records are accessible by primary key only. RRV errors may
subsequently occur.
User Action: Reorganize the file with the CONVERT command.

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.

2-243

Messages

SAMEFILE,

files are identical

Facility: DIFF, DIFFERENCES Command
Explanation: This success message is returned by the DIFF facility if the two
files being compared are identical.
User Action: None.
SAVEAMBIGSYM,

saving ambiguous symbol 'symbol-name'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The named symbol could be either an undefined procedure or a
variable; its correct usage has not yet been determined.
User Action: Define the named symbol as either a PROCEDURE or a
VARIABLE and save the section file again.
SAVEERROR,

error during SAVE operation

Facility: VAXTPU, VAX Text Processing Utility
Explanation: An error occurred while VAXTPU is saving a section file. This
message should be accompanied by a VMS RMS message identifying the
reason for the error.
User Action: Check the directory specification, the file protection, or any
other item specified in the accompanying VMS RMS message to make sure
that you are trying to save a valid section file.
SAVEUNDEFPROC,

saving undefined procedure 'procedure-name'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The named procedure is not defined, but it is saved in the
section file as an undefined procedure.
User Action: Define the named procedure and save the section file again.
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.

2-244

Messages

SBIAERROR,

fatal SBIA error

scanner advanced to 'name'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The scanner advanced so that the compiler could continue
compiling after the error occurred.
User Action: None.
SCANDEADPT, scan dead page table error
Facility: BUGCHECK, System Bugcheck
Explanation: The VMS 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, 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 on the BACKUP command
that produces the save set included with the SPR.)
SCBRDERR,

SCB physical read error halt

2-245

Messages

SCHDWK,

failed to schedule wakeup request for process 'process-id'

Facility: RUN, Run Detached Utility
Explanation: The $SCHDWK system service could not schedule a wakeup
call to the created process.
User Action: Determine error returned by the $SCHDWK system service,
and act accordingly. Note that the created process will not be awakened, so it
must be deleted and recreated.
SCRBUFOVF,

screen buffer overflow

Facility: LIB, Library Facility
Explanation: While buffering is in effect, a call to one of the terminalindependent screen procedures created more data than would fit in an entire
buffer.
User Action: Increase the size of the buffer specified in a call to LIB$PUT_
BUFFER.
SCSSYSTEMID has NOT been set to a nonzero value,
Facility: VAXport, 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 VMS installation guide.
SDBSFFULL,

software detected bad sector file is full on 'device-name'

Facility: BAD, Bad Block Locator Utility
Explanation: The Bad Block Locator Utility located the SDBSF; however, it is
already full.
User Action: Reinvoke the Bad Block Locator Utility without specifying any
execution context that would cause the utility to attempt to keep the SDBSF.
For example, the user should specify the /EXERCISE=NOKEEP qualifier.
SDBSFRFAIL,

failed to read the software detected bad sector file on 'device-name'

Facility: BAD, Bad Block Locator Utility
Explanation: The Bad Block Locator Utility could not locate a valid SDBSF.
User Action: Avoid using any execution context that attempts to obtain
or preserve the SDBSF. The following qualifiers would cause the Bad
Block Locator Utility to try to preserve the SDBSF: /BAD_BLOCKS,
/EXERCISE=KEEP, /OUTPUT /SHOW=BEFORE. Use an execution context
that causes the Bad Block Locator Utility to recreate the SDBSF, for example,
/EXERCISE.
Search string cannot be null
Facility: EDT, EDT Editor
Explanation: You asked EDT to search for nothing.
User Action: Reenter the command specifying a search string.

2-246

Messages

SEARCHFAIL,

error searching for 'filename'

Facility: ACCOUNTING, Accounting Utility
Explanation: The specified file could not be found. A subsequent error
message explains why.
User Action: None.

SEARCHFAIL,

error searching for 'filespec'

Facility: Shared by several facilities
Explanation: The specified file could not be found. A subsequent error
message explains why.
User Action: Take corrective action based on the associated message.

SECINTFAI, secondary interlock failure in queue
Facility: LIB, Library Facility
Explanation: Secondary interlock failed (severe error) retry-cnt times in a
row. The queue is not modified. This condition can occur only when the
queue is in memory being shared between two or more processors.
User Action: Wait until the queue is free, then retry the operation.

SECOUT,

error code of 'xx' parsing journal file

Facility: PATCH, Patch Utility
Explanation: A command interpreter callback request failed because of the
error represented as 'xx'.
User Action: Correct the error (represented as xx) and retry.

SECREFNEG,

section reference count went negative

SECTBLFUL,

section table (process/global) is full

Facility: SYSTEM, VMS System Services
Explanation: The system space allocated to maintain information about
sections is full; no more sections can be created.
User Action: If you have created many private sections, you may have to
delete sections when they are no longer needed. If the error occurs while
a global section, in particular a system global section, is being created, this
message may indicate that not enough space is allocated at system generation
for the section tables. Notify the system manager of the deficiency.

2-247

Messages

SECTRESTORED,

'count' procedures, 'count' variables, 'count' keys restored

Facility: VAXT PU, VAX Text Processing Utility
Explanation: The indicated items have been successfully restored from a
section file.
User Action: None.
SECTSAVED,

'count' procedures, 'count' variables, 'count' keys saved

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The indicated items have been saved in a section file.
User Action: None.
SECTUNDEFPROC,

saved 'count' undefined procedures, 'count' ambiguous
symbols

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The saved section file contains one or more undefined
procedures or ambiguous symbols.
User Action: Define the named procedures and symbols and save the section
file again.
See command on input line 'linenumber' of page 'pagenumber' of file 'filename'

Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: This is a standard error message line that specifies the location
of an error-related command in the input file. This message indicates the
name of the input file (filename) in which the command is located, and the
file page number and line number where the error occurs.
User Action: Find and correct the invalid command.
SEG, overlapping segments or segmented key must be string for key= 'nnn'

Facility: RMS, VMS Record Management Services
Explanation: The number of key elements specified by a key definition XAB
is greater than one, and the key data type is not STG. Or, the key segments
overlap and prolog 3 is specified.
User Action: The status value (STV) field of the FAB provides the key of
reference of the XAB in error. Verify that the call to the VMS RMS service is
coded correctly.
Select complete lines only

Facility: EDT, EDT Editor
Explanation: You used the SELECT line range specifier with a line mode
command such as COPY, FILL, MOVE, PRINT, TAB ADJUST, or WRITE.
However, the select range that is active had at least one partial line. The
select range must include only complete lines when it is used with line mode
commands.
User Action: Reenter the command specifying a select range that includes
complete lines.

2-248

Messages

Select range is already active
Facility: EDT, EDT Editor
Explanation: You attempted to establish a select range when one is already
in effect.
User Action: None.

SELRANGEZERO,

select range has 0 length

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The range you selected for the built-in procedure SELECT_
RANGE has a length of O; therefore, no characters were selected.
User Action: None.

SEMALRMAX , semaphore is already at its maximum value
Facility: PPL, Parallel Processing Facility
Explanation: The semaphore value cannot be incremented further.
User Action: Recode the program to ensure that only the correct maximum
number of PPL$INCREMENT_SEMAPHORE requests are entered.

SEMININON ,

semaphore initial value must be non negative

Facility: PPL, Parallel Processing Facility
Explanation: An improper initial value is specified.
User Action: Recode your program to ensure that the correct value is passed.

SENDABORT,

no message sent

Facility: MAIL, Mail Utility
Explanation: You pressed CTRL/C while sending a mail message.
User Action: None.

SENDERR,

error sending to user 'user-name'

Facility: MAIL, Mail Utility
Explanation: An error occurred when you attempted to send mail to the
specified user. This message is usually accompanied by a system error
message indicating the reason for the failure.
User Action: None.

SENDFAIL,

unable to send to subprocess

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The operation to write to the mailbox for the subprocess's input
failed.
User Action: Recreate the subprocess.

2-249

Messages

SEQ,

primary key out of sequence (SEQ access)
Facility: RMS, VMS Record Management Services
Explanation: A VMS RMS $PUT service specified sequential access, but the
primary key value of the record is less than the previous record entered.
$PUT operations in sequential access mode must be in ascending order of
primary key value.
User Action: Modify the program, if necessary, to detect and respond to
the condition. Correct the program and use the $PUT system service to put
records in ascending order of the primary key value.

SEQ,

record not in order
Facility: CONVERT, Convert Utility
Explanation: You have specified /NOSORT, but the primary keys are not in
ascending order.
User Action: Specify /SORT, or specify /NOFAST.

SEQNCE,

illegal record sequence in module 1module-name' file 1filename 1

Facility: LINK, Linker Utility
Explanation: A module contained an illegal sequence of object records.
User Action: Submit a Software Performance Report on the appropriate
language translator.
SEQNCE,

illegal record sequence in module 1module-name 1 in 1library filespec 1

Facility: LIBRAR, LIBRARY Command
Explanation: The object module you want to insert is illegally formatted.
User Action: Recompile the object module before inserting it into the library.
1

SEQUENCE, illegal record sequence in module module

Facility: LIB, Library Facility
Explanation: The Run-Time Library encountered severe format errors in the
shareable image you are trying to call.
User Action: Enter the ANALYZE/IMAGE command specifying the image in
question. If the errors indicate an operating system internal error, submit a
Software Performance Report.
Sequence increment must be less than 65536
Facility: EDT, EDT Editor
Explanation: You specified a number as the :increment specifier for the
/SEQUENCE qualifier that is too large.
User Action: Reenter the command specifying a smaller number.

2-250

Messages

Sequence number must be less than 65536
Facility: EDT, EDT Editor
Explanation: You specified a number as the :integer specifier for the
/SEQUENCE qualifier that is too large.
User Action: Reenter the command specifying a smaller number.
SEQUENCE2, illegal record sequence
Facility: LIB, Library Facility
Explanation: The Run-Time Library encountered severe format errors in the
shareable image you are trying to call.
User Action: Enter the ANALYZE/IMAGE command specifying the image in
question. If the errors indicate an operating system internal error, submit a
Software Performance Report.
SERVE_ERR, error serving device DDcnn: RO status= nnnnnnnn
Facility: STACONFIG, Standalone Configure Process
Explanation: A newly discovered device that fits all the serving parameters
could not be served. If the value in the RO status is 00000084, the device was
not served because the server is not loaded.
User Action: Check to see that the MSCP server has been loaded properly.
Use the SHOW DEV /SERVED command or examine SCS$GL_MSCP. This
global address should be a valid system space address. If the RO status is
other than 84, get the corresponding message (using EXIT nn) and find out
what is wrong with the device.
SERVEXISTS, service name already exists
Facility: LATCP, LAT Control Program
Explanation: You attempted to create a service already created for this node.
User Action: Use the SHOW CHARACTERISTICS command to see the
services on your node. Reenter the CREATE command with a new service
name.
SETIMR, error setting timer
Facility: JBC, Job Controller
Explanation: The job controller encountered an error setting a timer for a job
submitted with the/ AFTER qualifier. The accompanying message provides
additional information.
User Action: Take action based on the accompanying message.
SETKEY, keypad state has been set to 'state'
Facility: CLI, Command Language Interpreter (DCL)
Explanation: The specified keypad state is set.
User Action: None.

2-251

Messages

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: SYSGEN, System Generation Utility
Explanation: The value entered in the SYSGEN command SET parameter is
larger than the maximum allowed. The maximum value is exceeded.
User Action: Verify the number you intend to use.

SETMIN,

value set to minimum for parameter 'name'

Facility: SYSGEN, System Generation Utility
Explanation: The value entered in the SYSGEN command SET parameter is
smaller than the minimum allowed. The minimum value is used.
User Action: Verify the number you intended to use.

SEVINVALD,

illegal severity value

Facility: SMI, System Management Intergator/Server
Explanation: You attempted to add an entry into a loadable image database
that contains an invalid severity value.
User Action: Specify a valid severity value.

SHARCONF,

/SHARED conflicts with facility number

Facility: MESSAGE, Message Utility
Explanation: You have specified the /SHARED qualifier on the facility
definition with a facility number other than zero.
User Action: Remove the /SHARED qualifier from the facility definition.

SHMGSNOTMAP, shared memory global section not mapped during creation
Facility: SYSTEM, VMS System Services
Explanation: A shared memory global section creation request did not specify
a virtual address range into which the section is to be mapped. The section
cannot be initialized unless it is mapped.
User Action: Specify an input address range to map the section. Set RELP AG
to zero.

2-252

Messages

SHMNOTCNCT,

shared memory not connected

Facility: SYSTEM, VMS System Services
Explanation: The shared memory specified, that is, that part of the name to
the left of the colon(:), is not connected to this processor.
This error also occurs when colons are inadvertently placed in common event
flag cluster, mailbox, or global section names.
User Action: Connect the shared memory.
SHOFIL,

unable to open output for SHOW or LIST

Facility: NCP, Network Control Program
Explanation: VMS RMS returned an error when attempting to open the
output file for either a SHOW or LIST command. The VMS RMS error code
describes the error condition.
User Action: Take corrective action based on the accompanying VMS RMS
message.
SHOIO,

error writing output file for SHOW or LIST

Facility: NCP, Network Control Program
Explanation: RMS returned an error when attempting to write to the output
file for either a SHOW or LIST command. The RMS error code describes the
error condition.
User Action: Take corrective action based on the accompanying message.
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 corrupted.
User Action: None. Save set data has been lost.
SHORTDUMP,

the dump only contains 'm' out of 'n' pages of physical memory

Facility: SDA, System Dump Analyzer
Explanation: This message occurs if the system dump file is not large enough
to accommodate all of physical memory. The number of physical pages SDA
can analyze is represented by 'm'.
User Action: Refer to the VMS System Dump Analyzer Utility Manual for
information on changing the size of the system dump file.
SHOW_ERR,

error during show

Facility: AUTHORIZE, Authorize Utility
Explanation: This message is issued with other messages.
User Action: Take corrective action based on the accompanying messages.

2-253

Messages

SHOWERR,

SHOW command error

Facility: MONITOR, Monitor Utility
Explanation: An error occurred during execution of the SHOW command
of the Monitor Utility. More information may be obtained by examining the
accompanying message.
User Action: Correct the error indicated by the accompanying message and
rerun the SHOW command. Most such messages represent status values
returned to MONITOR from the Run-Time Library Screen Management
Procedures.
SHOWERR,

unable to complete show command

Facility: AUTHORIZE, Authorize Utility
Explanation: The AUTHORIZE command SHOW could not be completed.
This message should be accompanied by a VMS RMS message that identifies
the specific reason for the error.
User Action: Correct the condition identified by the RMS message and
reenter your command.
SHR,

invalid file sharing (SHR) options
Facility: RMS, VMS Record Management Services
Explanation: The file sharing field of the FAB contains an invalid value for
the file organization and the specified access.
User Action: Verify that the call to the VMS RMS service is coded correctly.

SHRCNTNEG,

PFN share count negative

COPY value for /SHARE qualifier ignored, using NOCOPY

Facility: LINK, Linker Utility
Explanation: The /SHARE=COPY qualifier may no longer be specified in
order to obtain an image-private copy of a shareable image.
User Action: None.

2-254

Messages

SHRIDMISMAT,

ident mismatch with shareable image

Facility: SYSTEM, VMS System Services
Explanation: The global section match found in a shareable image does not
correspond with the global section match in the executable image.
User Action: Relink the executable image.
SHRINSYS,

shareable images cannot be linked into a system image

Facility: LINK, Linker Utility
Explanation: An attempt is made to link a shareable image with a system
image.
User Action: Do not link a shareable image with a system image.
SHRPSCLNG, Psect 'string' has length 'number' in module 'module name' file
'file name' which exceeds length 'number' in shareable image
'image name'
Facility: LINK, Linker Utility
Explanation: In a linking operation that produces an executable image
including a shareable image as input, the linker now issues an error message
when an input-object module defines a COMMON area to have a greater
length than the COMMON area of the same name defined in the input
shareable image. Previously, the linker did not check multiple definitions of
the same COMMON area for length descrepancies.
User Action: Modify the length of the program section defining COMMON
area (such as those used in VAX BASIC, VAX PL/I, VAX FORTRAN, and
VAX C) to be less than or equal to the length of that program section in the
shareable image.
SHRPSCREF, reference to psect 'psect-name' is not position-independent in
psect 'psect-name' offset 'number' in module 'module-name' file
'filename'
Facility: LINK, Linker Utility
Explanation: A reference to a psect in a shareable image is made without the
use of .ADDRESS or general addressing mode.
User Action: Correct the reference and relink.
SHRSEPCLU,

shareable image being placed in separate cluster

Facility: LINK, Linker Utility
Explanation: A shareable image is put in a cluster with one or more object
modules using the CLUSTER= option.
User Action: Modify the CLUSTER= option so that it specifies either a single
shareable image or one or more object modules.

2-255

Messages

SHRSYMREF,

reference to symbol 'symbol-name' is not position-independent in
psect 'psect-name' offset 'number' in module 'module-name' file
'filename'

Facility: LINK, Linker Utility
Explanation: A reference to a symbol in a shareable image is made without
the use of general addressing mode.
User Action: Correct the reference to use general addressing mode.
SHRSYMTRA,

attempted .TRANSFER of shareable image symbol 'symbolname' illegal in psect 'psect-name' offset 'number' in module
'module-name' file 'filename'

Facility: LINK, Linker Utility
Explanation: A symbol from another shareable image is specified in the
.TRANSFER directive.
User Action: Link with the object modules containing the symbol rather than
the shareable image.
SHUT, local or remote node no longer accepting connects
Facility: SYSTEM, VMS System Services
Explanation: The local or remote node is in a state in which it no longer
accepts connections. (This is not because of a lack of resources.)
User Action: None. Try again later.
SHUTDOWN,

OPCOM shutting down. Requested by operator 'operator-name'

Facility: OPCOM, Operator Communication
Explanation: OPCOM is announcing the orderly shutdown of its activities.
User Action: Be aware that OPCOM will not be available to perform
requests.
SIGNO_ARG,

signal with no arguments

Facility: LIB, Library Facility
Explanation: A call is made to LIB$SIGNAL or LIB$STOP with no
arguments; LIB$_SIGNO_ARL is substituted.
User Action: None.
SIZ,

invalid key size for key= 'nnn'
Facility: RMS, VMS Record Management Services
Explanation: An invalid key size is specified in a key definition XAB. The
size is invalid for one of the following reasons:

2-256

•

It is greater than 255.

•

It is zero for key data type SIG, DSTG, COL, or DCOL.

•

It is greater than 16 for key data type PAC DP AC.

•

It is other than zero or two for key data types BN2, IN2, DBN2, or DIN2.

Messages

•

It is other than zero or four for key data types BN4, IN4, DBN4, or DIN4.

•

It is other than zero or eight for key data types BNS, INS, DBNS, or
DINS.

User Action: The status value (STV) field of the FAB provides the key of
reference of the XAB in error. Verify that the call to the VMS RMS service is
coded correctly.
SIZETRUNC, size field truncated to 32 bits
Facility: DEBUG, VMS Debugger
Explanation: The size of the entry in a VAX BLISS-32 field specification
is larger then 32. The debugger set the entry size to 32 and executed the
command. This message is informational.
User Action: None.
SKC,

.ENDIF /.ELSE not in same file as .IF /.IFNOT: 'string'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: You attempted to use associated conditional commands in
separate files.
User Action: Put the associated conditional commands in the same file.

SKPDAT, image data (records not beginning with"$" ignored)
Facility: CU, Command Language Interpreter (DCL)
Explanation: A command procedure contained lines that were not DCL
commands (that is, the lines did not begin with dollar signs) or an image
terminated without reading input data records.
User Action: Check the command procedure for missing dollar signs before
commands. Or check for the absence of the command that should read the
data records.
SLOWRESP, system failed to respond within one-half second
Facility: SMI, System Management Intergator/Server
Explanation: A clusterwide CONFIGURATION SET TIME command is
entered, and one of the cluster members took longer than one-half second to
respond. The time is set and the operation proceeded with the next cluster
member.
User Action: Verify that the time was set within acceptable tolerances with
a SYSMAN CONFIGURATION SHOW TIME command, and reenter the SET
TIME command if desired.
SMALLPAGE, terminal size (x columns by y lines) is too small
Facility: FDL, Edit/FDL Utility
Explanation: The value for x must be SO or greater, and the value for y must
be 24 or greater on video terminals.
User Action: Set the terminal width to SO or greater, and set the page length
to 24 or greater with video terminals; with nonvideo terminals, any page
length is acceptable.

2-257

Messages

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

SOURCELINE, at source line 'integer'
Facility: VAXTPU, VAX Text Processing Utility
Explanation: This message gives the source line number of the error, which
occurred during compilation.
User Action: None.

SPAWNED,

process 'process-name' spawned

Facility: CLI, Command Language Interpreter (DCL)
Explanation: This message is output by the DCL command SPAWN when it
spawns a subprocess.
User Action: None.

2-258

Messages

SPCIVC,

invalid collating sequence specification at line 'number'

Facility: SORT, Sort/Merge Utility
Explanation: The syntax you specified for your collating sequence is
incorrect.
User Action: Correct the syntax and reenter your specification.
SPCIVD,

invalid data type at line 'number'

Facility: SORT, Sort/Merge Utility
Explanation: In your specification file text, you incorrectly specified a data
type or you specified a data type that is not recognized by SORT /MERGE.
User Action: Correct your specification file text.
SPCIVF,

invalid field specification at the line 'number'

Facility: SORT, Sort/Merge Utility
Explanation: You incorrectly specified the text in the /FIELD clause in your
specification file.
User Action: Correct your specification file text.
SPCIVI,

invalid include or omit specification at line 'number'

Facility: SORT, Sort/Merge Utility
Explanation: You incorrectly specified the text in an /OMIT or /INCLUDE
clause.
User Action: Correct your specification file text.
SPCIVK,

invalid key or data specification at line 'number'

Facility: SORT, Sort/Merge Utility
Explanation: You incorrectly specified the text in a /KEY or a /DATA clause.
User Action: Correct your specification file text.
SPCIVP,

invalid sort process at line 'number'

Facility: SORT, Sort/Merge Utility
Explanation: Two possible explanations exist:
•

The sort process you specified in your specification file is not a record,
tag, address, or indexed sort.

•

You specified a nonrecord sort (tag, address, or index), which is invalid if
you are not using a random access device, if you used the record interface
on input, or if you specified your own comparison or equal-key routine.

User Action: Specify the correct sort process for your sort.

2-259

Messages

SPCIVS,

invalid specification at line 'number'

Facility: SORT, Sort/Merge Utility
Explanation: You specified an invalid keyword in your specification file text.
User Action: Correct your specification file text.

SPCIVX,

invalid condition specification at line 'number'

Facility: SORT, Sort/Merge Utility
Explanation: You incorrectly specified the syntax in a /CONDITION clause
in your specification file.
User Action: Correct your specification file text.

SPCMIS,

invalid merge specification at line 'number'

Facility: SORT, Sort/Merge Utility
Explanation: You incorrectly specified a sort process for a merge operation.
User Action: Correct your specification file text.

SPCOVR,

overridden specification at line number

Facility: SORT, Sort/Merge Utility
Explanation: In combination with specification file instructions, you specified
either SORT /MERGE qualifiers or callable arguments. These qualifiers or
arguments override any corresponding entries in the specification file text.
This message is a warning only and will not halt processing.
User Action: None.
1

SPCSIS, invalid sort specification at line number'
Facility: SORT, Sort/Merge Utility
Explanation: You incorrectly requested sequence checking in a sort operation.
User Action: Correct your specification file text.

SPECDEV,

can't add component-contains device name

Facility: SYSMAN, Cluster System Management Utility
Explanation: You attempted to add a startup component file that specifies a
device name in the file specification.
User Action: Reenter the command without the device specification.

SPECDIR,

can't add component-contains directory name

Facility: SYSMAN, Cluster System Management Utility
Explanation: You attempted to add a startup component file that specifies a
directory name in the file specification.
User Action: Reenter the command without the directory specification.

2-260

Messages

SPECIFY,

specify option (1valid-options')

Facility: BACKUP, Backup Utility
Explanation: The Backup Utility encountered a fatal error. You must select
a recovery action. 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.
SPECNODE,

can't add component-contains node name

Facility: SYSMAN, Cluster System Management Utility
Explanation: You attempted to add a startup component file that specifies a
node name in the file specification.
User Action: Reenter the command without the node specification.
SPECWILD,

can't add component-contains wildcards

Facility: SYSMAN, Cluster System Management Utility
Explanation: You attempted to add a startup component file that contains a
wildcard character in the file specification.
User Action: Reenter the command without the wildcard characters.
SPL,

spool or submit of command file failed on $CLOSE
Facility: RMS, VMS Record Management Services
Explanation: The spool or submit command file option that is specified on a
$CLOSE operation failed. If the IFI field of the FAB is zero, the file is closed
successfully.
User Action: The status value (STV) field of the FAB contains a code that
provides more information about the condition. Take corrective action based
on this status code.

SPLACQERR,

spin locks of higher rank already owned by CPU

Facility: SMP, Symmetric Multiprocessing
Explanation: A processor attempted to acquire a spin lock out of order. That
is, the current spin lock acquisition is being made on a spin lock of lower rank
than one that is already held by the current processor. The multiprocessor
system could deadlock if spin locks are allowed to be acquired out of order.
User Action: Analyze the crash dump, and determine which lock is being
acquired and which locks are already owned by the acquiring processor.
Correct your code so the locks are acquired in the correct order.
One probable situation that can occur is when a processor acquired a
lock many times during a driver's execution, then incorrectly executed a
conditional release of the lock rather than unconditionally releasing it as
might have been intended. This leaves the spin lock still owned by this
processor. If the processor subsequently attempts to acquire a lower-ranked

2-261

Messages

spin lock while still owning the previous lock, the operating system prevents
a potential deadlock by issuing this bugcheck. Correct the driver code to
prevent this, or similar, situations from occurring.
Note that this bugcheck applies only to static spin locks, not to device locks.
Device locks are not subject to the ranking rules that static spin locks (which
include fork locks) are subject to.
SPLRELERR,

spin lock to be released is not owned

Facility: SMP, Symmetric Multiprocessing
Explanation: A processor is attempting to release ownership of a spin lock
that is not currently owned by that processor.
User Action: Analyze the crash dump and determine why that spin lock
wasn't owned when the processor tried to release it. Correct the code to
eliminate the problem.

The following situation is one that would cause this bugcheck. A processor,
while executing a driver, might build up multiple, nested acquisitions of
this spin lock through calling several levels of subroutine, each acquiring
ownership of the spin lock. If one of the called subroutines incorrectly
executes an unconditional release of this spin lock, then a caller of that
subroutine tries to release the spin lock later, believing the spin lock to be
held. The system checks for bugs because the code is trying to release a spin
lock that the processor no longer owns.
SPLRSTERR,

spin lock to be conditionally released is not owned

Facility: SMP, Symmetric Multiprocessing
Explanation: A processor is attempting to release a single level of ownership
(restore) for a spin lock that is not currently owned by that processor.
User Action: Analyze the crash dump and determine why that spin lock
was not owned when the processor tried to release it. Correct the code to
eliminate the problem.

The following situation is one that would cause this bugcheck. A processor,
while executing a driver, might build up multiple, nested acquisitions of
this spin lock through calling several levels of subroutine, each acquiring
ownership of the spin lock. If one of the called subroutines incorrectly
executes an unconditional release of this spin lock, then a caller of that
subroutine will try to release the spin lock later, believing the spin lock to be
held. The system checks for bugs because the code is trying to release a spin
lock that the processor no longer owns.
SPLIPLHIGH,

current IPL exceeds synchronization IPL of desired spin lock

Facility: SMP, Symmetric Multiprocessing
Explanation: A processor is attempting to acquire a spin lock from an IPL
that is higher than the synchronization IPL associated with that spin lock.
User Action: Analyze the crash dump and determine the code sequence that
is trying to acquire the spin lock from the excessively high IPL. It might be,
for instance, a case where driver code previously raised the IPL to accomplish
something else, then failed to lower the IPL again prior to acquiring the lock
that is synchronized by the lower IPL.

2-262

Messages

Note that under no circumstances can a driver lower the IPL below that level
from which it originally raised the IPL, unless it does so by creating a fork
process.
SPLIPLLOW,

IPL has fallen below level of owned spin locks

Facility: SMP, Symmetric Multiprocessing
Explanation: A processor is attempting to release a spin lock while executing
at an IPL that is below the synchronization IPL associated with that spin lock,
indicating that local processor synchronization is compromised.
User Action: Analyze the crash dump and determine the point where your
code has lowered the IPL below the level associated with the spin lock that
is held. Correct the code such that IPL is not lowered before the spin lock is
released.
SPNAMLNG,

PSECT module 'module-name' file 'library filespec' has illegal
length 'nnn'

Facility: LIBRAR, LIBRARY Command
Explanation: The PSECT name length exceeds the maximum length of 31
characters.
User Action: Change the PSECT name length, recompile the module, and
reenter the command line.
SPTERRS,

errors occurred writing the system page table to the dump file·

Facility: SDA, System Dump Analyzer
Explanation: The first block of the dump file contains information indicating
that there were errors while writing the memory associated with the system
page table to the dump file.
User Action: None. The dump file is probably not useful for analysis.
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).
SPTNOTFND, system page table not found in dump file
Facility: SDA, System Dump Analyzer
Explanation: The operating system was unable to copy the system page table
to SYSDUMP.DMP when it failed. As a result, SDA could not examine the
dump file.
User Action: None. The system page table is vital to SDA initialization.

2-263

Messages

SPWNIO, shared input or output files are not allowed-respecify
Facility: CU, Command Language Interpreter (DCL)
Explanation: You used a file that is already opened by DCL as input or
output to SPAWN.
User Action: If input or output to DCL is SYS$INPUT or SYS$0UTPUT, do
not specify the input or output qualifier. See the SP AWN command in the
VMS DCL Dictionary for details on input and output interpretation.

SQO,

operation not sequential (SQO set)

Facility: RMS, VMS Record Management Services
Explanation: An attempt is made to perform random access to a file opened
or created with the SQO file processing option; the file can be processed only
with sequential operations.
User Action: Verify that the call to the VMS RMS service is coded correctly.

SQUALERR, more than one statistic qualifier specified for 'class-name' class
Facility: MONITOR, Monitor Utility
Explanation: The MONITOR request specified more than one of the statistic
qualifiers (/CURRENT, /AVERAGE, /MINIMUM, /MAXIMUM, /ALL) for
the indicated class. Only one of these qualifiers may be specified per class.
User Action: Reenter the MONITOR request, specifying only one statistic
qualifier per class.

SQUROONEG,

square root of negative value user PC 'location'

Facility: MTH, Mathematics Facility
Explanation: A mathematics library procedure is called to evaluate the square
root of a negative number. The result returned is the reserved operand, minus
zero.
User Action: Locate the call to the library procedure that returned the error.
Correct your program making the argument zero or positive.

SRCLIN,

the source input entry is 'string'

Facility: BAD, Bad Block Locator Utility
Explanation: This message is associated with the DUPBLKNUM error
message and displays the portion of the command line that is in error.
The duplicate block is ignored.
User Action: None.

2-264

Messages

SRCLINNOT,

source lines not available for module 'path-name'

Facility: DEBUG, VMS Debugger
Explanation: The source lines from module 'path-name' cannot be displayed
or searched because there is no source line information in the Debug Symbol
Table (DST) for that module. Either the compiler is not able to generate such
information or the /DEBUG qualifier was not used on the compilation or link
command.
User Action: If the language in question supports source line display,
recompile and relink with the /DEBUG qualifier. If the language does not
support source line display, source lines will not be available to the debugger
for modules written in that language.
SRTIWA,

insufficient space; specification file is too complex

Facility: SORT, Sort/Merge Utility
Explanation: The work area is too small for the number of instructions that
you have specified in your specification file.
User Action: Simplify your specification file text by reducing, for example,
the number of /FIELD clauses.
SRVALLOAD,

the MSCP server is already loaded

Facility: SYSGEN, System Generation Utility
Explanation: You attempted 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.
SRVMISMATCH,

monitor server on remote node is an incompatible version

Facility: MONITOR, Monitor Utility
Explanation: You attempted to monitor a node running on an incompatible
version of the Monitor Utility. This can occur in a cluster if all of the nodes
are not running the same Version of the VMS operating system. This is only
a warning and the Monitor request will continue to monitor other requested
nodes running the same version as the node on which the request was
initiated.
User Action: None.
SSCHANGE,

unexpected end of save set on 'device-name'

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

2-265

Messages

SSERROR,

'service-name' system service error

Facility: MONITOR, Monitor Utility
Explanation: The indicated system service returned a failing status code. The
status code appears as a linked message that follows this message.
User Action: Check the description of the failing status code for the indicated
system service in the VMS System Services Reference Manual. Correct the
condition causing the failure, if possible, and reenter the MONITOR request.
Otherwise, submit a Software Performance Report.
SSFAIL,

system service failure exception, status= 'xxxxxxxx', PC= 'location', PSL
= 'xxxxxxxx'

Facility: SYSTEM, VMS System Services
Explanation: A call to a system service returned an error or a severe error
status code. The image has enabled system service failure exception mode.
This mode allows an image to signal a software exception when a failure
occurs in a system service call. The operating system displays the failure
status code, the PC, and the PSL at the time of the exception.
User Action: Examine the PC and virtual address displayed in the message
to determine the instruction that caused the error.
SSR,

restricted character '~\' (octal 34) encountered in text, ignored

Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: DSR encountered a restricted character in the input file.
User Action: Remove the restricted character. You cannot use it in a DSR
input file.
SSRVEXCEPT,

unexpected system service exception

equal-key routine and stable option cannot both be specified

Facility: SORT, Sort/Merge Utility
Explanation: You specified both an equal-key routine and the SOR$M_
STABLE option when only one or the other is allowed.
User Action: Specify either the equal-key routine or the stable option.

2-266

Messages

STACKDUMP,

non-symbolic stack dump follows

Facility: TRACE, Traceback Facility
Explanation: This message precedes a traceback dump. The accompanying
message indicates why the traceback is nonsymbolic. This message is
informational. The nonsymbolic stack dump is displayed following this
message.
User Action: None.
STACKOVER,

stack overflow during compilation

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The program is too complex for VAXTPU to parse. The
program may be written in a language other than VAXTPU.
User Action: If you are compiling a valid VAXTPU program, please submit a
Software Performance Report describing the conditions that lead to the error.
STALITUDF,

stack of undefined literal 'number' in record 'number' in module
'module-name' file 'filename'

Facility: LINK, Linker Utility
Explanation: An attempt is made to stack an undefined literal.
User Action: Submit a Software Performance Report on the appropriate
language processor.
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.
STARTED,

LAT terminal port driver started

Facility: LATCP, LAT Control Program
Explanation: The LAT port driver started successfully. This message is
informational.
User Action: None.
STARTED,

queue already started

Facility: JBC, Job Controller
Explanation: The queue cannot be started because it is already running.
User Action: None.

2-267

Messages

Starting memory dump ... Memory dump complete
Facility: BUGCHECK, System Bugcheck
Explanation: The VMS 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 of physical memory) is written.
User Action: None. However, if the 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.
Starting memory dump ...
Facility: BUGCHECK, System Bugcheck
Explanation: The VMS 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.
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 VMS
operating system to write the memory dump indicates that you should

2-268

Messages

submit a Software Performance Report (SPR), a copy of the dump file 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 you restart the operation using the same
output medium. If it is necessary to restart the operation because of a system
failure, use another volume.

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 Action: Ensure that the device from which standalone BACKUP booted
stays online during the entire BACKUP operation.

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 of physical memory
is written to a system dump file, the system will automatically reboot if the
BUGREBOOT system parameter is set to one.
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.

STATOOLONG,

truncating status line to 'count' characters

Facility: VAXTPU, VAX Text Processing Utility
Explanation: You have defined a window status line that is too long to fit
within the boundaries of the current physical width of the terminal. The text
has been truncated to fit on the screen.
User Action: Redefine the status line to a shorter line of text.

2-269

Messages

STD,

too many nested .NOTEs and/or .LISTs: 'string'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: You attempted to nest more than 20 notes or 20 lists (or more
than 7 within a footnote).
User Action: Reduce the number of nested notes or lists.

STDISPIC,

illegal non-relocatable displacement value in psect 'name' offset
'offset'

Facility: LINK, Linker Utility
Explanation: The linker encountered a nonrelocatable reference while linking
what is intended to be a position-independent shareable image.
User Action: Find the reference using the information in the message, and
make the reference relocatable.
STEPINTO,

cannot step over PC= 'address-value'

Facility: DEBUG, VMS Debugger
Explanation: The debugger was unable to step over the routine and executed
a step into the routine instead. This message is informational.
User Action: None.
STGTRUNC,

string truncated

Facility: PATCH, Patch Utility and DEBUG, VMS Debugger
Explanation: The Patch Utility truncated an ASCII string entry because it
exceeded the current length mode or because the entry is inappropriate for
the context in which it is specified. Or the debugger truncated an ASCII
string because it exceeded the size of the ASCII data type.
User Action: If the Patch Utility generated this message, correct the ASCII
string and retry. If the debugger generated this message, no action is required.
STILLKEYS,

keys still point at data

Facility: LBR, Librarian Subroutine Package
Explanation: This warning message is generated by the Librarian routines.
Keys in other indexes still point to the text. The call to LBR$DELETE_DATA
did not delete the text.
User Action: None. Processing continues.
STKOVF,

command procedures too deeply nested-limit to 32 levels

Facility: CU, Command Language Interpreter (DCL)
Explanation: The maximum level of nesting of command procedures is
exceeded. Too many procedures invoked other procedures.
User Action: Simplify the command procedure hierarchy to reduce the level
of nesting.

2-270

Messages

STKOVFLO,

stack of 'number' pages falls below control region to 'address'

Facility: LINK, Linker Utility
Explanation: The memory allocation for Pl space does not allow enough
room for the stack.
User Action: Correct the allocation to allow enough room for the stack.
STMRECFMT,

illegal stream record format in 'record'

Facility: EXCHANGE, Exchange Utility
Explanation: While processing a file with /RECORD_FORMAT=STREAM,
the EXCHANGE utility found an invalid record.
User Action: The input file might contain a record too large for an output
stream file, or an input file is not a valid stream file. Use the correct
/RECORD_FORMAT type for the file.
STNOTAVAIL,

requested starting block number is not available

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility could not satisfy a /START_BLOCK
request.
User Action: Either the requested block is already contained inside a file,
or it is larger than the largest block on the volume. Use the EXCHANGE
DIRECTORY /FULL /ALL to discover the location and sizes of unused areas
on the volume.
STOPPED,

LAT terminal port driver stopped

Facility: LATCP, LAT Control Program
Explanation: The LAT port driver stopped successfully. This is an
informational message.
User Action: None.
STPCLU,

component file is cluster-wide

Facility: SYSMAN, Cluster System Management Utility
Explanation: A SYSMAN STARTUP command is entered with the
environment set with the /CLUSTER qualifier. The /CLUSTER qualifier
is ignored.
User Action: None.
STPINVALD,

illegal load step value

Facility: SMI, System Management Intergator/Server
Explanation: You attempted to add an entry into a loadable image database
that contains an invalid load step value.
User Action: Specify a valid load step.

2-271

Messages

STRCPYERR,

unexpected error from string copy routine

Facility: DIFF, DIFFERENCES Command
Explanation: An unexpected error occurred during an RTL string copy
operation.
User Action: Submit a Software Performance Report.
String delimiter must be nonalphanumeric

Facility: EDT, EDT Editor
Explanation: You used a letter, digit, or percent sign ( % ) as a string
delimiter.
User Action: Reenter the command using a valid string delimiter.
String is not found

Facility: EDT, EDT Editor
Explanation: The string defined in the range specification cannot be found.
User Action: Verify that EDT is searching in the expected direction and that
you typed the string correctly.
STRIS_INT,

string is interlocked

Facility: LIB, Library Facility, OTS, General Purpose Facility, STR, String
Manipulation Facility
Explanation: Code being executed at AST level attempted writing into a
string that is being written into or whose length is being used for length
computation immediately before the AST.
User Action: Do not write to strings at AST level that are used at non-AST
level or in other AST-level processing. If it is necessary to use the same
strings for interrupt routines, then disable ASTs while string assignments are
in progress.
STRLVL,

illegal object language structure level ('decimal-number') should be
'decimal-number' in module 'module-name' file 'filename'

Facility: LINK, Linker Utility
Explanation: An object module header record specified an illegal object
language structure level.
User Action: Submit a Software Performance Report on the appropriate
language processor.
STRL VL,

illegal object language structure level in module 'module-name'

Facility: LIB, Library Facility
Explanation: The Run-Time Library encountered severe format errors in the
shareable you are trying to call.
User Action: Enter the ANALYZE/IMAGE command specifying the image in
question. If the errors indicate an operating system internal error, submit a
Software Performance Report.

2-272

Messages

STRLVL,

object structure level 'nnn' unsupported in module 'module-name' in
'library-name'

Facility: LIBRAR, LIBRARY Command
Explanation: This error message is generated by the DCL command
LIBRARY. An illegally formatted object file is inserted.
User Action: Recompile the object file and insert it into the library.
STRNGPAD,

string operand lengths do not match, shorter zero extended on right

Facility: DEBUG, VMS Debugger
Explanation: The operands of a string comparison ( 'ABC' < 'AB' ) did not
----------Tiave the same length. Tice shorter one is-zero extended on the tight.
User Action: Use strings of the same length.
STRNOTFOUND,

string not found

Facility: VAXTPU, VAX Text Processing Utility
Explanation: A search for a simple string or a pattern failed.
User Action: None.
STRNOTWCB,

data structure not window block

illegal escape sequence embedded in string

Facility: DTK, DECtalk Facility
Explanation: A DTK$ output routine passed an escape sequence embedded
in the output string.
User Action: Check your output string to determine which escape sequence
is being passed. If you need this escape sequence, most likely a DTK$ routine
has already been defined that provides that feature.
STRTERESC,

illegal escape sequence embedded in strings

Facility: SMG, Screen Management Facility
Explanation: An SMG output routine is passed an escape sequence
embedded in the output string. The output string is written to the virtual
display but the string is terminated at the escape sequence.
User Action: Check your output string to determine what escape sequence is
being passed. If you need the action provided by this escape sequence, there
is most likely an SMG routine that performs that function.

2-273

Messages

STRTNOMULTI,

cannot request /START_BLOCK with multiple input files

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility does not allow the use of the /START_
BLOCK qualifier when more than one input file is specified.
User Action: Leave the /START_BLOCK qualifier off, or copy the files one
at a time with the /START_BLOCK present.
STRTOOLARGE,

string greater than 65535 characters

Facility: VAXTPU, VAX Text Processing Utility
Explanation: A string operation has generated a string that exceeds 65,535
characters in length.
User Action: Use an expression that generates a shorter string.
STRTOOLNG,

string argument is too long-shorten

Facility: CU, Command Language Interpreter (DCL)
Explanation: The specified string argument is too long.
User Action: Shorten the string argument.
STRTOOLON,

string is too long (greater than 65535)

Facility: STR, String Manipulation Facility
Explanation: An attempt is made to create a string that is longer than
allowed by the String Facility or the descriptors in the VMS Procedure Calling
and Condition Handling Standard. The maximum length string supported is
65,535.
User Action: Do not specify string lengths greater than 65,535. Check that a
concatenation operation will not attempt to create a string longer than 65,535.
STRTRU,

string truncated

Facility: LIB, Library Facility
Explanation: A Run-Time Library procedure returned a string that did not
fit into the specified receiving area resulting in lost trailing characters. This
message is associated with a status code returned from the Run-Time Library.
User Action: Correct your program to increase the area specified to receive
the 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.

2-274

Messages

STRUCSIZE,

structure size declared as 'num-units' allocation units, 'num-units'
was given

Facility: DEBUG, VMS Debugger
Explanation: The BLISS-32 structure size was declared to be 'numunits' units but was referenced with 'num-units' units. This message is
informational.
User Action: None.
STRUCT_LEVEL,

system job queue file has incompatible structure level of
'number'

Facility: JBC, Job Controller
Explanation: After opening the system job queue file, the job controller
determined that the internal format of the queue file or revision level is
different from the format currently supported by the system. This situation
usually occurs when an old queue file is used after installing a new release
of VMS or after a maintenance update in which the queue file format has
changed.
User Action: Create a new queue file using the START /QUEUE/MANAGER
/NEW_REVISION command, or delete the existing queue file and create a
new file using the START/QUEUE/MANAGER command.
SUBALREXI,

subprocess already exists for this display

Facility: SMC, Screen Management Facility
Explanation: A user tried to create a subprocess for a virtual display when
one is already created. This is normal in a modular environment.
User Action: None.
SUBLOCKS,

cannot dequeue a lock with sublocks

Facility: SYSTEM, VMS System Services
Explanation: A programming error occurred because an attempt is made to
dequeue a lock that had sublocks under it.
User Action: Correct the programming error and retry. (Note that you may
use the flag bit LCK$M_DEQALL on the $DEQ system service request to
dequeue all the locks for a given access mode.)
SUBMITERR,

error submitting file to queue 'queue-name'

Facility: SUBMIT, SUBMIT Command
Explanation: This message is issued with another message indicating the
problem.
User Action: Take corrective action based on the accompanying message.
SUBOUTBND,

subscript 'subscript-number' is out of bounds value is 'subscriptvalue', bounds are 'low-bound

Facility: DEBUG, VMS Debugger
Explanation: You attempted to use a subscript out of the bounds of an array.
User Action: Change the value of the subscript.

2-275

Messages

SUBRNG,

arithmetic trap, subscript out of range at PC = 'xxxxxxxx',
PSL = 'xxxxxxxx'

Facility: SYSTEM, VMS System Services
Explanation: A subscript out of range caused an arithmetic exception
condition.
User Action: Examine the PC location displayed in the message, and check
the program listing to verify that operands or variables are specified correctly.
SUBSTRING,

invalid substring (start: 'low-bound', end: 'high-bound'), object has
length 'string-size'

Facility: DEBUG, VMS Debugger
Explanation: The substring specification (start: 'low-bound', end: 'highbound' ) is not within the bounds defined for the data type.
User Action: Specify a substring specification within the bounds defined for
the data type.
SUCCDUP ACE,

current ACE will supersede succeeding ACE-not entered

Facility: ACLEDIT, Access Control List Editor
Explanation: An ACE exists after the current position within the ACL, which
would be rendered useless by the current ACE. The current ACE is not
entered.
User Action: Modify or delete the current ACE or the succeeding occurrence
of the ACE.
SUCCESS,

normal successful completion

Facility: CDU, Command Definition Utility
Explanation: Your operation completed successfully.
User Action: None.
SUP,

network operation not supported; DAP code = 'xxxxxxxx'

Facility: RMS, VMS Record Management Services
Explanation: The requested VMS RMS operation failed because either the
specified remote node does not support the function or VMS RMS does not
support the function in a network context at the local node.
User Action: Consult the VMS Networking Manual and the applicable DECnet
manual for the remote node to determine which functions are supported by
both the local and remote nodes. The status value (STV) field of the FAB or
RAB contains a DAP status code. See the appropriate DECnet manual for the
remote node for an interpretation of the DAP status code.
SUPERSEDE,

created file superseded existing version

Facility: RMS, VMS Record Management Services
Explanation: The file created by a VMS RMS $CREATE operation superseded
an existing version of the same file. This message indicates a success status.
User Action: None.

2-276

Messages

SUPERSEDE,

logical name superseded

Facility: SYSTEM, VMS System Services
Explanation: A request to place a logical name in a logical name table
completed successfully by replacing an existing logical name table entry.
(Because this is a success message, it is not normally displayed.)
If this message is returned from a call to an ACP, it indicates that an existing
file with the same file name, type, and version number is deleted as the result
of a CREATE request.

User Action: None. Note the condition and modify the source program, if
necessary, to detect and respond to the condition.
SUPERSEDE,

previous value of 'value' has been superseded

Facility: CLI, Command Language Interpreter (DCL)
Explanation: You redefined the specified logical name.
User Action: None.
SUPPORT,

network operation not supported

Facility: RMS, VMS Record Management Services
Explanation: VMS RMS rejected the request because it is not supported
between two DECnet systems. The STV field contains either another VMS
RMS completion code or a FAL status code, depending on whether VMS RMS
at the local node or FAL at the remote node could not support the request.
User Action: The status value (STV) field contains either an RMS status code
or a $FAC status code that provides more information about the condition.
Take corrective action based on this status code.
SUSPEND,

service routine pausing for other input

Facility: PSM, Print Symbiont
Explanation: This status is returned by a print symbiont format routine
requesting the current input service routine be paused.
User Action: None.
SUSPENDED,

process is suspended

Facility: SYSTEM, VMS System Services
Explanation: The specified process is suspended or placed in miscellaneous
wait state.
User Action: The requested operation cannot be performed when the
specified process is suspended. Resume process or retry the operation.
SWAP AGINS,

second page/swap file 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.

2-277

Messages

SWAPWSLE,

swap working set list entries error

abbreviated symbols not allowed-remove "*" from symbol name

Facility: CLI, Command Language Interpreter (DCL)
Explanation: You abbreviated a symbol using an asterisk ( * ) or in a context
where abbreviated symbol definitions are not valid.
User Action: Remove the asterisk (*)from the symbol name.
SYMCREPRC,

error creating symbiont process for 'device-name'

Facility: JBC, Job Controller
Explanation: The job controller encountered an error creating an input
symbiont process for card reader input on the specified device. The
accompanying message provides additional information.
User Action: Take action based on the accompanying message.
SYMDCLEXTR,

symbol declared external

Facility: MACRO, VAX MACRO Assembler
Explanation: A label definition or direct assignment statement specified a
symbol that is previously declared external in an .EXTERNAL directive.
User Action: Delete the external declaration or change the name of the
internal symbol.
SYMDEFINMO,

symbol is defined in module

Facility: MACRO, VAX MACRO Assembler
Explanation: An .EXTERNAL directive specified a label that is previously
defined in the module.
User Action: Delete the external declaration or rename the internal symbol.
SYMDEL,

invalid symbol or value delimiter-check command syntax

Facility: CLI, Command Language Interpreter (DCL)
Explanation: An illegal character is present on a command line containing a
symbol definition. This error can also indicate that arguments were specified
for a lexical function that does not require arguments.
User Action: The rejected portion of the command is displayed between
backslashes. Reenter the command.

2-278

Messages

SYMDEL,

unexpected symbiont process termination

Facility: JBC, Job Controller
Explanation: A symbiont process exited without having been requested to
do so by the job controller. The accompanying message provides additional
information.
User Action: Take action based on the accompanying message.
SYMDELETE,

error symbol deleted

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The error symbol was deleted in order for the compiler to
continue compiling.
User Action: None.
SYMINSERT,

'name' inserted before error symbol

Facility: VAXTPU, VAX Text Processing Utility
Explanation: In order for the compiler to continue compiling, 'name' was
inserted before the error symbol.
User Action: None.
SYMLNG,

symbol name is too long-shorten the name

Facility: CLI, Command Language Interpreter (DCL)
Explanation: You specified a symbol name that is too long.
User Action: Shorten the symbol name.
SYMNAMLNG,

'module-type' module 'module-name' file 'library-name ' has
illegal length 'nnn'

Facility: LIBRAR, LIBRARY Command
Explanation: The specified module name exceeds the name length limit.
User Action: Make sure that all the symbol names in the module are less
than the library's name length limit or compress the library with a larger key
length.
SYMNOTABS,

symbol is not absolute

Facility: MACRO, VAX MACRO Assembler
Explanation: The argument in a macro string operator is a relative symbol or
is undefined.
User Action: Ensure that the symbol is defined as an absolute symbol.
SYMNOTACT,

nonstatic variable 'symbol-name' is not active

Facility: DEBUG, VMS Debugger
Explanation: The symbol 'symbol-name' is not defined in an active call
frame.
User Action: Check the symbol specified; if correct, ensure that you have
defined the scope correctly.

2-279

Messages

SYMOUTPHAS,

symbol out of phase

Facility: MACRO, VAX MACRO Assembler
Explanation: A label definition specified a label that is defined later in the
module; or a local label definition specified a local label that is defined later
in the same local label block.
User Action: Ensure that the label is defined only once in the module, or that
the local label is defined only once in the local label block.
SYMOVF,

no room for symbol definitions-delete some symbols

Facility: CU, Command Language Interpreter (DCL)
Explanation: The command interpreter cannot hold any more symbol
definitions or labels. Note that this error can occur when a nested procedure
is executed, because the command interpreter defines the symbols Pl through
P8 before executing the procedure.
If an ON condition is not established for warnings in the procedure, the
procedure continues execution. However, the procedure may fail later if you
refer to the symbol that could not be defined.

User Action: If necessary, interrupt the command procedure with CTRL/Y
to stop its execution. Use the DCL commands SHOW SYMBOL and SHOW
KEY to determine how many global symbols and keypad symbols are defined;
delete unused symbols to recover symbol table space. If the error occurs
frequently, simplify the command procedure or procedures, and use local
symbols within procedures whenever possible.
You may also increase the size of the command language interpreter (CU)
symbol table by resetting the SYSGEN parameter CLISYMTBL. The format of
the command is SYSGEN SET CUSYMTBL n, where n is the size of the table
expressed in pages. The SYSGEN SHOW CLISYMTBL command shows you
the default table size, and the range of allowable table sizes. Note that the
SYSGEN SET command sets the new value for the duration of your process
only. It does not change the permanent parameter value.
SYMREPLACE,

error symbol replaced by 'name'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The error symbol was replaced in order for the compiler to
continue compiling.
User Action: None.
SYMTOOLNG,

string too long

Facility: CDU, Command Definition Utility
Explanation: You entered a command string that is too long and therefore
invalid.
User Action: Reenter a shorter command string.

2-280

Messages

SYMTOOLNG,

symbol 'symbol-name' is too long to copy to subprocess

Facility: CLI, Command Language Interpreter (DCL)
Explanation: When you spawned a subprocess, a logical name, a logical
value, a symbol name, or a symbol value is too long to be copied to the
subprocess.
User Action: Break the specified name or value into several parts.
SYMTOOLNG,

symbol name too long

Facility: MESSAGE, Message Utility
Explanation: You have assigned a symbol name with more characters than
are permitted.
User Action: Shorten the symbol name.
SYMTOOLONG, the symbol 'symbol-name' is longer than 31 characters

Facility: CDU, Command Definition Utility
Explanation: CDU encountered a symbol name longer than 31 characters
while reading from a CLD file.
User Action: Edit the CLD file so that symbol names are not greater than 31
chaq1cters in length.
SYMTRUNC,

preceding symbol value has been truncated

Facility: CLI, Command Language Interpreter (DCL)
Explanation: This informational message signifies that the symbol value
displayed through the SHOW SYMBOL command is too large to be fully
displayed. The value is truncated in the display.
User Action: None.
SYN,

file specification syntax error

Facility: RMS, VMS Record Management Services
Explanation: The file specification syntax string contains a syntax error. For
example, invalid characters were used, or required punctuation marks were
omitted.
User Action: Correct the syntax and reenter the command or correct the
program that caused the error.
SYNCH,

synchronous successful completion

Facility: SYSTEM, VMS System Services
Explanation: This alternate success code indicates that the requested
operation completed synchronously and as expected.
User Action: None.

2-281

Messages

SYNERR,

syntax error

Facility: SMG, Screen Management Facility
Explanation: The Termtable compiler encountered invalid syntax. For
instance, there may be a misplaced or missing equals sign.
User Action: Check your terminal definition.
SYNTAX,

command syntax error

Facility: NCP, Network Control Program
Explanation: An element in the command syntax could not be parsed.
User Action: Reenter the command.
SYNTAX,

command syntax error at or near 'DEBUG-command-segment'

Facility: DEBUG, VMS Debugger
Explanation: The debugger encountered a command syntax error near the
element 'DEBUG-command-segment'.
User Action: Reenter the command.
SYNTAX,

command syntax error at or near 'location'

Facility: PATCH, Patch Utility
Explanation: A syntax error in a file name has been discovered in a CREATE
command.
User Action: Reenter the command specifying the correct syntax.
SYNTAX,

error parsing 'xxxx'

Facility: ACCOUNTING, Accounting Utility
Explanation: The command syntax is invalid. The message displays the
rejected portion of the command.
User Action: Use the DCL HELP command or refer to the VMS DCL
Dictionary, for the correct syntax and reenter the command.
SYNTAX,

error parsing 'string'

Facility: Shared by several facilities
Explanation: The command syntax is invalid. The message displays the
rejected portion of the command.
User Action: Use the DCL command HELP or refer to the VMS DCL
Dictionary for the correct syntax and reenter the command.
SYNTAX,

invalid ACE syntax

Facility: ACLEDIT, Access Control List Editor
Explanation: An error was encountered trying to parse the ACE currently
being entered. The portion of the ACE after the point of error is displayed.
User Action: Correct the error and enter the ACE again.

2-282

Messages

SYNTAX,

syntax error in statement 'n'

Facility: FDL, Create/FDL Utility, FDL, Edit/FDL Utility
Explanation: An FDL syntax error is encountered.
User Action: Examine the specified line in the FDL file, determine which
validity rule is violated, and correct the line.
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.
SYNTAXERR,

string syntax error detected by LIB$TP ARSE

Facility: LIB, Library Facility
Explanation: The string passed to the LIB$TPARSE library procedure
contained a syntax error.
User Action: Correct the syntax error in the string.
SYNTAXERROR,

syntax error

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The program being compiled has a syntax error.
User Action: Correct the syntax error and recompile your program.
SYS,

QIO system service request failed
Facility: RMS, VMS Record Management Services
Explanation: VMS RMS encountered an error while trying to issue a $QIO
system service request for an 1/0 operation. This message may occur if calls
to VMS RMS fail because of insufficient resource quotas; for example, if a
process exceeds its AST limit quota.
User Action: The status value (STV) field of the RAB contains a system status
code that provides more information about the condition. Take corrective
action based on this status code. Check for a programming error that causes
the process to exceed a resource quota required for VMS RMS 1/0 operations.

SYSADJWSL,

system service adjust working set limit error

2-283

Messages

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 VMS operating system versions. The images on your
system disk are incompatible.
User Action: Obtain a new copy of the VMS 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 corrupted.
User Action: Attempt to reboot the system or try a different drive. If this
fails, obtain a new copy of the VMS 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 1/0 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-No such parameter

Facility: SYSBOOT, System Bootstrap Facility
Explanation: A parameter name specified in a SYSBOOT command SET or
SHOW is not a recognized parameter name.
User Action: Reenter the command specifying correct parameter names.

2-284

Messages

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-Parameter is not ASCII type
Facility: SYSBOOT, System Bootstrap Facility
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.
SYSBOOT-E-Parameter is not numeric type
Facility: SYSBOOT, System Bootstrap Facility
Explanation: A numeric value is specified in a SET command for a nonnumeric parameter.
User Action: Reenter the command specifying a correct parameter value.
SYSBOOT-E-Specified string is too long
Facility: SYS BOOT, System Bootstrap Facility
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.
SYSBOOT-E-Syntax error
Facility: SYSBOOT, System Bootstrap Facility
Explanation: Your command contained a syntax error.
User Action: Correct the syntax and reenter the command.
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 VMS operating system versions. The images on your
system disk are incompatible.
User Action: Obtain a new copy of the VMS system disk.
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.

2-285

Messages

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: Backup 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-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 your DIGITAL field service representative.
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 VMS system.
User Action: Call your DIGITAL field service representative.
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 pageable system
space and reboot the system. Reduce one or more of the PAGEDYN and
GBLP AGES parameters.
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.

2-286

Messages

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 PHYSICALP AGES) to
contain the PFN bitmap.
User Action: Reboot the system with a larger value for PHYSICALP AGES.
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_P AGING to 1 and reboot.
SYSBOOT-F-Unable to allocate physical memory

Facility: SYSBOOT, System Bootstrap Facility
Explanation: The sum of pages required for the system page table, nonpaged
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, and 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.
SYSBOOT-F-Unable to locate storage bit map file

Facility: SYSBOOT, System Bootstrap Facility
Explanation: SYS BOOT cannot locate the storage bitmap file (BITMAP .SYS)
in directory (000000] on the system disk. The system disk is either defective
or corrupted.
User Action: Obtain a new copy of the VMS system disk.

2-287

Messages

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.
User Action: The system disk is either defective or corrupted, or the disk you
are accessing is not the system disk. Obtain a new copy of the VMS 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 VMS operating system from multiple volumes.
User Action: Attempt to reboot the system; try a different drive or obtain a
new copy of the VMS 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 your local field service representative.
SYSBOOT-F-Unexpected machine check

Facility: SYSBOOT, System Bootstrap Facility
Explanation: An unexpected machine check occurred indicating a probable
hardware error or SYSBOOT logic error.
User Action: Call your local field service representative.
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: Call your local field service representative.
SYSBOOT-W-DMPFRG SYSDUMP.DMP is too fragmented to be used

Facility: SYSBOOT, 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.

2-288

Messages

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 your local field service representative. You may continue
the bootstrap operation 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 your local field service representative. You may continue
the bootstrap operation 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 VMS. 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: SYS BOOT, System Bootstrap Facility
Explanation: The hardware ECO level is below the level required for correct
software operation.
User Action: Call your local field service representative. You may continue
the bootstrap operation 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 your local field service representative. You may continue
the bootstrap operation but the integrity of the software may be compromised.

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.

2-289

Messages

SYSBOOT-W-System 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 your local field service representative. You may continue
the bootstrap operation but the integrity of the software may be compromised.
SYSBOOT-W-Value set to maximum
Facility: SYSBOOT, System Bootstrap Facility
Explanation: You attempted to set a parameter to a value greater than the
maximum allowable value. SYSBOOT set the parameter to the maximum
permissible value.
User Action: None.
SYSBOOT-W-Value set to minimum
Facility: SYSBOOT, System Bootstrap Facility
Explanation: You attempted to set a parameter to a value that is less than
the allowable minimum value. SYSBOOT set the parameter to the minimum
permissible value.
User Action: None.
SYSBOOT-W-WS default and quota raised to PDH+MINWSCNT
Facility: SYSBOOT, System Bootstrap Facility
Explanation: SYSBOOT raised the default working set size you specified to
accommodate the sizes of the process header plus the minimum fluid working
set size.
User Action: None.
SYSDEV,

the system device cannot be dismounted

Facility: DISMOUNT, DISMOUNT Command
Explanation: The device name specified in the DCL command DISMOUNT
is the system volume.
User Action: Verify the device name (or logical name, if a logical name
is specified) in the command and reenter the DCL command DISMOUNT
specifying the correct device.
SYSDIR,

this product creates system directory 'directory-name'

Facility: VMSINSTAL, Install Procedures
Explanation: The product being installed creates the specified system
directory.
User Action: None.

2-290

Messages

SYSDISK,

this product creates system disk directory 'directory-name'

Facility: VMSINSTAL, Install Procedures
Explanation: The product being installed creates a directory on the system
disk.
User Action: None.
SYSERROR,

system service error

Facility: VAXTPU, VAX Text Processing Utility
Explanation: An error occurred while executing one of the VMS system
services. An accompanying message explains which service failed and why it
failed.
User Action: Take action based on the accompanying VMS message.
SYSERROR,

system service error

Facility: Shared by several facilities
Explanation: An error is detected by a system service. A subsequent message
explains the reason for the error.
User Action: Take corrective action based on the associated message.
SYSERROR,

system service error

Facility: VAXTPU, VAX Text Processing Utility
Explanation: An error occurred while VAXTPU is using one of the VMS
system services. An accompanying message from the system service should
explain why the error occurred.
User Action: Follow the recovery procedure for the system service message.
SYSERRORPC,

'name' system service error at PC = 'location'

'testname' system service error [[at PC 'location']]

Facility: UETP, User Environment Test Package
Explanation: This message is no longer used.
User Action: None.
SYSFAIL,

system failed during execution

Facility: JBC, Job Controller
Explanation: The system crashed during execution of the affected job or
queue management command.
User Action: Resubmit the job or reenter the command.

2-291

Messages

SYSFAOERR,

unexpected error from SYS$FAO

Facility: DIFF, DIFFERENCES Command
Explanation: An unexpected error occurred during a call to the $FAO system
service.
User Action: Submit a Software Performance Report.
SYSID,

error while obtaining system ID message

Facility: CNF, NI Configurator
Explanation: An error occurred during the read to the NI device driver.
User Action: See the accompanying message to determine the appropriate
action.
SYSINIT-E-create process error on STARTUP
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
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. Since not enough pool is available to
allocate the storage area, the error log messages cannot be saved.
User Action: Increase the SYSGEN parameter NP AGEDYN 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 you do not have
a running system 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.

2-292

Messages

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

SYSINIT-E-error loading RMS.EXE, status = 'status'
Facility: SYSINIT, System Initialization
Explanation: The VMS RMS 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
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 VMS 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.

2-293

Messages

SYSINIT-E-error opening swap file, status= 'status'

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

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

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

Facility: SYSINIT, System Initialization
Explanation: An error was encountered when acquiring a cluster-wide 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

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 VMS 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 P AGEDYN to a reasonable value
(at least 10,000) and reboot the system.

2-294

Messages

SYSINIT-E-invalid date/time
Facility: SYSINIT, System Initialization
Explanation: A syntax error is detected in the date or time that is typed to
set the system time.
User Action: Enter the date or time in the correct format.

SYSINIT-E-page file or swap file control block initialization error
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:

•

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

•

Do not set P AGFILCNT to zero.

•

You can prevent the complete mapping of a file 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.

2-295

Messages

SYSINIT-I- no dump file-error log buffers not saved
Facility: SYSINIT, System Initialization
Explanation: The system disk does not have either a dump file
SYSDUMP.DMP or a page file PAGEFILE.SYS; therefore, the contents of
the error log buffers at the time of the last shutdown/crash that were saved
in the dump file are not available for recovery from the dump file into the
error log buffer recovery area.
User Action: Create a page file P AGEFILE.SYS or a dump file
SYSDUMP.DMP on the system disk, and reboot the system so that a dump
file is available and error log buffers are saved across a shutdown or system
failure.
SYSINIT-I- PAGEFILE.SYS not found-system initialization continuing ...
Facility: SYSINIT, System Initialization
Explanation: The primary paging file, SYS$SYSTEM:P AGEFILE.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,
you can install one or more secondary page files by editing the
SYS$SPECIFIC:[SYSMGR]SYPAGSWPFILES.COM file.
SYSINIT-W- dump file write errors-error log buffers not saved
Facility: SYSINIT, System Initialization
Explanation: Since the entire dump file contents are suspect, the dump file
write is not successfully completed, and no attempt is made to recover the
saved error log messages from the dump file.
User Action: None.
SYSINIT-W- invalid dump header version-error log buffers not saved
Facility: SYSINIT, System Initialization
Explanation: The dump file contains the contents of a dump written under a
version of the VMS 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.
User Action: None required. This message is primarily to warn users that
some error log messages have been lost.
SYSLOAD,

system loaded from node 'node-name'

Facility: VAXCLUSTER, VAXcluster Facility
Explanation: This message indicates that the NISCS bootstrap is starting
execution. This is an informational message.
User Action: None.

2-296

Messages

SYSMGT,

system specific mangement function not supported

Facility: NCP, Network Control Program
Explanation: The requested function cannot be performed because it is
a system-specific function that is not supported on the system where the
command is executed.
User Action: Examine the provided system-specific error message, if present.
SYSMSG2,

error code 'hex code' not found

Facility: AUTHORIZE, Authorize Utility
Explanation: The $GETMSG system service could not find a corresponding
message for the specified error code, which probably indicates that the code
is incorrect. Since an incorrect error code obviously should not be generated,
this message probably indicates an internal software error.
User Action: Submit a Software Performance Report that describes the
conditions leading to the error.
SYSNAM,

NICONFIG requires SYSNAM privilege

Facility: CNF, NI Configurator
Explanation: NICONFIG must run with SYSNAM privilege in order to
declare itself as a known image to be eligible for multiple connects.
User Action: Install NICONFIG with SYSNAM privilege or run from an
account with SYSNAM privilege.
SYSNOTUPD,

I/O database not updated for volume 'volume'

Facility: SET, SET Facility
Explanation: The attempt to modify the volume's home block is successful,
but the system information about the volume is not updated.
User Action: To ensure that no ambiguities exist in the system I/O database,
the volume should be dismounted and then remounted. Until then, a SHOW
DEVICE of the drive on which the volume is mounted will still show the old
volume characteristics.
SYSPWDMOD,

system password modified

Facility: AUTHORIZE, Authorize Utility
Explanation: The system password has been changed to the password
directed by your command.
User Action: None.

2-297

Messages

SYSTRMERR,

SYSINIT-terminal IO error

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.

SYSVERDIF, privilege removed-system version mismatch-please relink
Facility: SYSTEM, VMS System Services
Explanation: A SYS.SIB, different from that of the currently running system,
is used to link the image being run.
User Action: Relink the image. The image is allowed to run without
CMEXEC or CMKRNL privilege.

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: You have encountered a driver mismatch.
User Action: Reassemble and relink all drivers at each major release of VMS.

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.

2-298

Messages

TAB EXIST,

'table-name' already exists-not superseded

Facility: CLI, Command Language Interpreter (DCL)
Explanation: This informational message signifies that the CREATE/NAME_
TABLE command without the SUPERSEDE attribute specified encountered a
table with the same name as the one it is about to create. A new table is not
created.
User Action: If the existing table is to be replaced by a new table, reenter the
command with the / ATTRIBUTES=SUPERSEDE qualifier.
TABID_MIS,

terminal table id mismatch

Facility: SMG, Screen Management Facility
Explanation: The Termtable internal consistency check failed. The routines
that fetch information from Termtable have a different version number than
the Termtable data.
User Action: The routines that fetch the data may be newer than
your Termtable.EXE. Recompile TERMTABLE.TXT to update your
TERMTABLE.EXE.
TABLEFULL,

element ID table overflow

Facility: MONITOR, Monitor Utility
Explanation: A MONITOR request for a component class is terminated
prematurely because of an overflow of an internal buffer.
User Action: Reexecute the MONITOR request. Please submit an SPR
including a transcription of the exact MONITOR command entered and a
dump of the MONITOR image.
TABNOTFND,

previous table 'table-name' is not found-new table created

Facility: CLI, Command Language Interpreter (DCL)
Explanation: This informational message signifies that the CREATE/NAME_
TABLE/ ATTRIBUTES=SUPERSEDE command could not find an existing table
of the same name. The new table is created.
User Action: None.
TABSUPER,

previous table 'table-name' has been superseded

Facility: CLI, Command Language Interpreter (DCL)
Explanation: This informational message signifies that the CREATE/NAME_
TABLE/ ATTRIBUTES=SUPERSEDE command found an existing table with
the same name and replaced it with a new table.
User Action: None.
TAMPER,

file 'filename' has been tampered with.

Facility: VMSINSTAL, Install Procedures
Explanation: VMSINSTAL is attempting to update a system text file, but the
file has been modified locally. VMSINSTAL cannot update the file.
User Action: DIGITAL software cannot update system text files that you
have modified.

2-299

Messages

TAPECLASS,

fatal error detected by Tape Class driver (TUDRIVER)

'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.
TAPEPOSLOST,

magnetic tape position lost

Facility: SYSTEM, VMS System Services
Explanation: The magnetic tape ACP (ancillary control process) lost the
current position on the tape and cannot continue processing.
User Action: Close all open files. Dismount and remount the tape and
position it to the desired position, if possible. If the error persists, the tape
may be defective.
TAPES,

tapes

no text allowed after .REQUIRE command: 'string'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: You attempted to insert commands or text directly following a
.REQUIRE command file specification.
User Action: Put the commands on a separate line.

2-300

Messages

TBIT,

T-bit pending trap at PC = 'location', PSL = 'xxxxxxxx'
Facility: SYSTEM, VMS System Services
Explanation: This message indicates an exception condition. It is usually
followed by a display of the condition arguments, registers, and stack at the
time of the exception.
User Action: Examine the PC and virtual address displayed in the message
to determine the instruction that caused the error.

TBKBUG,

please report TRACE bug no. 'nnn'

Facility: TRACE, Traceback Facility
Explanation: An internal coding error occurred in the traceback program.
User Action: Collect as much information as possible and submit a Software
Performance Report. Include the bug number displayed in the message in the
report.
TERMDSBL,

terminal disabled, operator 'operator-name'

Facility: OPCOM, Operator Communication
Explanation: A terminal is successfully disabled with the DCL command
REPLY /DISABLE.
User Action: None.
TERMENAB,

terminal enabled, operator 'operator-name'

Facility: OPCOM, Operator Communication
Explanation: A terminal is successfully enabled with the DCL command
REPLY/ENABLE.
User Action: None.
TERMFAIL,

failed to enable terminal

Facility: OPCOM, Operator Communication
Explanation: This message is a response to a REPLY /ENABLE request
indicating that your request to OPCOM is rejected.
User Action: Ask your system manager to give you OPER privilege and try
again.
TERO UT,

error code of 'xx' parsing command file

Facility: PATCH, Patch Utility
Explanation: A command interpreter callback request failed due to the error
code being represented as 'xx'.
User Action: Correct the error code (represented as 'xx') and retry.
TEXT,

'message'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The message text is displayed and should describe the problem.
User Action: Take action based on the content of the message text.

2-301

Messages

TEXT,

'text'

Facility: UETP, User Environment Test Package
Explanation: Some UETP tests use this message to convey information that
is usually self-explanatory. The device tests, for example, use this message to
explain why a device failed its test.
User Action: In most cases no user action is indicated by this message itself.
Take the action implied by the other messages that usually accompany it. In
other cases, the text should explain the nature of the problem.
TEXT,

no input file given

Facility: MACRO, VAX MACRO Assembler
Explanation: The DCL command MACRO did not contain any source files; it
contained only macro library files.
User Action: Specify a source file in the command line.
TEXTD,

'string'

Facility: DSR, DIGITAL Standard Runoff
Explanation: This message accompanies one or more other messages that
describe an error condition. This message displays the text that is being
processed when the error occurred.
User Action: Correct the text by editing the source file.
TEXTD,

entry text: 'string'

Facility: DSR, DIGITAL Standard Runoff
Explanation: The indicated index entry caused this error. This message
accompanies one or more other messages.
User Action: Correct the entry in error by editing the source file.
TFE,

too few end commands
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: An .END command (for example, .END LIST) is missing.
User Action: Insert the missing .END command.

TFRSYS,

transfer address in system image 'image-name' ignored

Facility: LINK, Linker Utility
Explanation: The linker encountered a transfer address in the creation of a
system image. System images cannot have transfer addresses.
User Action: Remove the transfer address.
That key is not definable
Facility: EDT, EDT Editor
Explanation: The key selected for the EDT command DEFINE KEY is not
available for definition.
User Action: Select a different key to define.

2-302

Messages

THIRDP ARTY,

logical link disconnected by a third party

Facility: SYSTEM, VMS System Services
Explanation: A DECnet-VAX logical link is disconnected by a system
manager at some location in the network.
User Action: Reinitiate the connection.

TIMEOUT,

a timeout has occurred

Facility: DTK, DECtalk Facility
Explanation: This is an informational message telling you that the output
device has timed out.
User Action: None.

TIMEOUT,

device timeout

Facility: SYSTEM, VMS System Services
Explanation: An input operation did not complete because the timeout
period specified with the request elapsed before the input was received.
If this message is associated with a status code returned by a request
to an LPAll-K driver, a device timeout occurred. (Only for the start
microprocessor, initialize LPAll-K, set clock, and start data transfer request
functions.) An interrupt is not received within one second after the request is
issued.
If this message is associated with a status code returned by a request to a
DRll-W interface driver, the timeout period specified for this request is
exceeded. A device reset is issued to the DRll-W when the timeout occurs.
If this message is associated with a status code returned by a request to
a terminal driver, the specified terminal could not perform the QIO read
operation because a timeout occurred at the terminal. In other words, an
interrupt is lost, or 10$M_TIMED is specified on a read operation, or a
hardware timeout occurred. IOSB+2 contains the number of bytes transferred
before the timeout occurred. If associated with a DECnet-VAX operation, the
connect request is not completed within the maximum time.

User Action: The action to take depends on the context of the command
or application. For example, if a timeout occurs during the execution of a
DCL command MOUNT, verify that the physical device is ready and that the
volume is properly loaded on the device.

TIMEOUT,

disk boot driver initialization timeout

Facility: VAXCLUSTER, VAXcluster Facility
Explanation: The boot node could not respond to the MSCP messages within
the timeout interval.
User Action: Check for resource deprivation on the boot node or an
overloaded Ethernet.

2-303

Messages

TIPCUFLOW,

NETACP-transmit count underflow

object command data overflows record by 'decimal-number' bytes in
module 'module-name' record 'record-name' file 'filename'

Facility: LINK, Linker Utility
Explanation: The object record is not long enough to contain all required
data.
User Action: Submit a Software Performance Report on the appropriate
language processor.
TIRNYI,

unimplemented TIR command ('decimal-number') encountered in
module 'module-name' record 'record-name' file 'filename'

Facility: LINK, Linker Utility
Explanation: An object module contained an object language command that
is not implemented.
User Action: Submit a Software Performance Report on the appropriate
language processor.
TITLE,

empty ident or title

Facility: FDL, Edit/FDL Utility
Explanation: There is no string value specified for the TITLE primary.
User Action: You can either ignore this message or modify the FDL file and
supply a value for the TITLE primary.
TITLETRUNC,

maximum length of 'n' exceeded, title truncated

Facility: ACCOUNTING, Accounting Utility
Explanation: The length of the title string specified by the /TITLE qualifier is
too long. The title string will be truncated to the maximum length specified
in the error message.
User Action: Reduce the length of the title string.
TKNOVF,

command element is too long-shorten

Facility: CU, Command Language Interpreter (DCL)
Explanation: An element, that is, any string placed between two delimiters,
in the command line exceeded the maximum length of 255 bytes.
User Action: Reenter the command with the element shortened.

2-304

Messages

TLKINUSE,

DECTalk is in use

Facility: DTK, DECtalk Facility
Explanation: A DTK$ routine is called from an AST routine that interrupted
a DTK$ routine with the same voice_id argument.
User Action: Correct the code to call the routine with the correct
synchronization.
TMF,

too many footnotes, excess footnotes merged

Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: You have more than twenty footnotes in a file. All footnotes
after the twentieth are merged into one large footnote and output after the
next page of text. (This large footnote will probably exceed the page length.)
User Action: Use fewer footnotes, shorten them, or spread them out.
TMO,

timeout period expired

Facility: RMS, VMS Record Management Services
Explanation: A VMS RMS operation specified a timeout period and the
timeout period expired before the operation completed. The user buffer
contains the input characters (if any) received before the timeout period
expired.
User Action: If this message occurs during the login procedure, repeat the
procedure. If the request is for a record lock, the lock request is not granted.
Other actions depend on the program issuing the request; user programs
should be coded to detect and respond to IJO timeouts.
TMP,

too many page ranges on /PAGES qualifier

Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: More than five separate page ranges have been specified with
the qualifier.
User Action: Reduce the number of ranges specified.
TMPMBX,

NICONFIG requires TMPMBX

Facility: CNF, NI Configurator
Explanation: NICONFIG must run with TMPMBX privilege.
User Action: Install NICONFIG with TMPMBX privilege or run from an
account with TMPMBX privilege.
TMR,

SETIMR system service request failed

Facility: RMS, VMS Record Management Services
Explanation: A VMS RMS operation specified a timeout period and the
attempt to declare the system timer failed. The operation is aborted.
User Action: Verify that sufficient TQE quota is available by entering the
SHOW PROCESS/QUOTA command. If necessary, increase the TQE quota,
and try the operation again; or modify the program so there are not too many
$SETIMR requests simultaneously.

2-305

Messages

TMS,

too many saves, corresponding .SAVE and .RESTORE ignored
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: You have nested more than 20 .SAVE directives.
User Action: Correct your program to nest fewer than 20 .SAVE directives.

TMT,

too many tab settings; excess ignored: 'string'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: More than 40 separate settings were used with a single .TAB
STOPS command.
User Action: Reduce the number of tab settings.

TMV,

too many /VARIANTs

Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: More than 20 variable names were used with the qualifier.
User Action: Reduce the number of variable names.

TNS,

terminator not seen
Facility: RMS, VMS Record Management Services
Explanation: A VMS RMS $GET service request to a terminal terminated
when the user buffer is filled to capacity. No record terminator is
encountered. Subsequent $GET service requests can retrieve additional
characters from the input line.
User Action: Modify the source program, if necessary, to detect and respond
to the condition or provide a user buffer large enough to contain an entire
input line, including the terminator sequence.

TOODEEP,

maximum subindex depth exceeded

Facility: DSR, DIGITAL Standard Runoff
Explanation: The number of levels of subindex entries has been exceeded.
User Action: Check the subindex entries.

TOOFEW,

too few arguments

Facility: VAXTPU, VAX Text Processing Utility
Explanation: You have not specified all of the arguments required by the
built-in procedure you want to execute.
User Action: Reenter the procedure with all of the required arguments. If
you do not know the correct arguments, check the description of the built-in
procedure in the VAX Text Processing Utility Manual, or use online help.

TOOLONG,

specified parameter is too long (over 255 characters)

Facility: DTK, DECtalk Facility
Explanation: The length of the specified string is too long.
User Action: Correct your program so that it requests a phone number or
dictionary substitution of 255 characters or fewer.

2-306

Messages

TOOMANCLS,

number of classes in text library module greater than allowable
classes

Facility: ERF, Error Log Utility
Explanation: An inconsistency in the text library was encountered.
User Action: Submit a Software Performance Report.
TOOMANDIS,

too many displays

Facility: SMG, Screen Management Facility
Explanation: An internal limit on the number of virtual displays that your
program may have has been exceeded. The limit is currently 255. This
includes any virtual displays that some outer routine may be using. This
includes displays on all pasteboards.
User Action: Use fewer virtual displays. Make sure that your program is not
in a loop creating virtual displays. Be sure that you delete a virtual display
when you are done with it.
TOOMANERR,

too many errors, some errors not reported

Facility: DEBUG, VMS Debugger
Explanation: Too many MISMODBEG or certain other errors occurred. Other
similar errors are not reported. This message is informational.
User Action: None.
TOOMANNOD,

too many nodes in node list-must be shortened

Facility: SMI, System Management Intergator /Server
Explanation: The result of an ENABLE or DISABLE operation would force
the list of nodes for an entry to surpass the maximum length.
User Action: Check if the node list can be shortened by changing the
operation from ENABLE to DISABLE, or from DISABLE to ENABLE.
TOOMANPAS,

too many pasteboards

Facility: SMG, Screen Management Facility
Explanation: An internal limit on the number of pasteboards that your
program may have has been exceeded. The current limit is 31.
User Action: Use fewer pasteboards.
TOOMANY,

too many arguments

Facility: VAXTPU, VAX Text Processing Utility
Explanation: You have specified too many arguments to the built-in
procedure you want to execute.
User Action: Locate and remove the extra argument or arguments. Then
reenter the procedure. If you do not know the correct arguments, check
the description of the built-in procedure in the VAX Text Processing Utility
Manual, or use online help.

2-307

Messages

TOOMANYARGS,

more arguments than defined in routine table

Facility: SMI, System Management lntergator/Server
Explanation: This is an internal error. SMI is trying to send a call to a remote
node, and the argument list is longer than the maximum length defined for
the object.
User Action: Submit a Software Performance Report showing the sequence
of SYSMAN commands leading to the error.
TOOMANYCOL,

too many columns, reduced number to fit listing width

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility encountered a DIRECTORY /COLUMNS
value too large for the display line. EXCHANGE has used the largest number
of columns which will fit on the line.
User Action: None.
TOOMANYLEV,

too many levels of nested input detected in record 'record
number'

Facility: PSM, Print Symbiont
Explanation: This status is returned indicating too many levels of nested
input detected in this record number.
User Action: Please submit a Software Performance Report.
TOOMANYLNAM,

logical name translation exceeded allowed depth

Facility: SYSTEM, VMS System Services
Explanation: Ten translations were performed on the logical name; however,
the name has not been translated.
User Action: Display all logical name tables and remove those entries that
caused the problem.
TOOMANYPARAM,

too many formal parameters/local variables at line 'integer'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: A maximum of 31 formal parameters or local variables is
permitted.
User Action: Reduce the number of formal parameters or local variables to
less than 31.
TOOMANYREDS,

too many redirects

Facility: SYSTEM, VMS System Services
Explanation: This call is redirected more than eight times.
User Action: Modify your program so that it performs fewer levels of call
redirection.

2-308

Messages

TOOMANYVER,

too many higher file versions

Facility: SYSTEM, VMS System Services
Explanation: The maximum number of file versions already exists for the
specified file, and all existing version numbers were greater than the specified
version number.
User Action: Change the version limit of the file or delete some of the
existing versions.

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.

TOOMNYARG,

too many arguments

Facility: LBR, Librarian Subroutine Package
Explanation: A call to a librarian function passed more arguments than were
expected.
User Action: Reduce the number of arguments so that the call is in the
correct format.

TOOMNYARGS,

too many arguments in MACRO call

Facility: MACRO, VAX MACRO Assembler
Explanation: The macro call contained more arguments than were specified
in the .MACRO directive in the macro definition.
User Action: Ensure that the macro call corresponds to the macro definition.

TOOMNYDLM,

more than maximum of 'n' comment delimiters specified

Facility: DIFF, DIFFERENCES Command
Explanation: Too many comment delimiters were specified.
User Action: Reenter the command, specifying one less than 'n' comment
delimiters.

TOOMNYENDR,

too many .ENDR in macro 'macro-name' in 'library-name'

Facility: LIBRAR, LIBRARY Command
Explanation: The specified MACRO contains an unmatched .ENDR.
User Action: Reformat the macro source file.

TOOMNYFIL,

more than two input files specified

Facility: DIFF, DIFFERENCES Command
Explanation: Too many input files were specified.
User Action: Reenter the command; specify no more than two input files.

2-309

Messages

TOOMNYFILES,

too many input files specified

Facility: MONITOR, Monitor Utility
Explanation: More than 5000 input files were specified on the /INPUT
qualifier.
User Action: Reenter the MONITOR request specifying a file specification
list which identifies no more than 5000 files. For performance reasons, it is a
good idea to archive or purge MONITOR recording files which are unlikely to
be used in a multi-file summary request.
TOOMNYGST,

number of symbol records exceeds count in image header

Facility: CDU, Command Definition Utility
Explanation: The input tables have an invalid format or were corrupted.
User Action: Do not use these files again with SET COMMAND.
TOOMNYLIB,

too many libraries open

Facility: LBR, Librarian Subroutine Package
Explanation: Too many libraries are open. Only 16 libraries may be open
simultaneously.
User Action: Use LBR$CLOSE to close any library that you do not need to
access.
TOOMNYOPND,

too many operands for instruction

Facility: MACRO, VAX MACRO Assembler
Explanation: Too many operands were specified for the instruction.
User Action: Reduce the number of operands.
TOOMNYOUT,

too many outputs defined

Facility: CDU, Command Definition Utility
Explanation: There are too many outputs included in the CLD file.
User Action: Reduce the number of outputs specified in the CLD file.
TOOMNYPSEC,

too many PSECTs declared

Facility: MACRO, VAX MACRO Assembler
Explanation: More than 255 user-defined program sections were declared.
User Action: Reduce the number of program sections.

2-310

Messages

TOOMUCHDATA,

too much optional or interrupt message data

Facility: SYSTEM, VMS System Services
Explanation: A network interrupt message is rejected because it contains
more than 16 bytes of data.
On a write request, the DEUNA hardware incorrectly read the value for the
buffer size because the DEUNA device driver previously verified that the
buffer size is correct.

User Action: Repeat the request; do not specify more than 16 bytes of data.
The UNIBUS and UNIBUS Adapter, especially the Data Path board, should
be checked.
TOPLINETRUNC,

calculated new first line 'integer', changed to 1

Facility: VAXTPU, VAX Text Processing Utility
Explanation: You adjusted a window. The new first line, however, would
have been less than 1. Therefore, VAXTPU has truncated it at 1.
User Action: None is required. However, you may reexecute the built-in
procedure ADJUST_WINDOW with arguments that will not result in a first
line less than 1.
TOTAL,

'n-records' selected, 'n-records' rejected, 'n' input files

Facility: ACCOUNTING, Accounting Utility
Explanation: When the /LOG qualifier is used, this informational message
displays the total number of records that were selected and/ or rejected, as
well as the total number of input files processed.
User Action: None.
TOTAL,

'n' selected, 'n' rejected, 'n' skipped, 'n' input files

Facility: ERF, Error Log Utility
Explanation: This message reports the total number of input files processed
and the total number of entries selected, rejected, and skipped across all the
files.
User Action: None.
TRACEBACK,

symbolic stack dump follows

Facility: TRACE, Traceback Facility
Explanation: This message precedes a symbolic traceback dump.
User Action: None.
TRACIGN,

suppression of traceback overridden by DEBUG specification

Facility: LINK, Linker Utility
Explanation: The command line specified both /NOTRACE and /DEBUG.
/NOTRACE is ignored. The link continues as if /NOTRACE were not
specified.
User Action: None.

2-311

Messages

TRE,

error in index tree
Facility: RMS, VMS Record Management Services
Explanation: VMS RMS detected an invalid index pointer in an indexed file.
User Action: Reorganize the file with the CONVERT command.

This error is caused by hardware errors, VMS RMS or system software errors,
or inadvertent modifications of files by non-VMS RMS programs.
TRMMBX,

terminal has associated-terminate image and then SP AWN

Facility: CU, Command Language Interpreter (DCL)
Explanation: A SPAWN command failed because the current image has
associated a mailbox with the terminal.
User Action: Terminate the current image and reenter the SPAWN command.

TRMNOTANS,

terminal is not ANSI compatible

Facility: SMG, Screen Management Facility
Explanation: A call to SMG$GET_PHYSICAL _CURSOR is made specifying
that the terminal is to be queried to determine where the cursor is. This could
not be done because the terminal is not ANSI standard, and this feature is
available only on ANSI terminals.
User Action: Rerun your application on an ANSI terminal such as a VTlOO.

TRU,

truncation
Facility: STR, String Manipulation Facility
Explanation: An attempt is made to place more characters into a string than
it could contain. The value is truncated on the right to fit.
User Action: Do not exceed the maximum string length. This error may be
ignored if right truncation is acceptable.

TRUNC,

data truncated

Facility: DCX, Disk Compression Utility
Explanation: The buffer provided is insufficient to receive the compressed
data record produced by DCX$COMPRESS_DATA or the expanded data
record produced by DCX$EXPAND_DATA. As much data as the buffer could
hold has been returned.
User Action: Provide a larger buffer.

TRUNC,

truncation error in psect 'psect-name' offset 'address' in module 'modulename' file 'filename'

Facility: LINK, Linker Utility
Explanation: A reference using byte or word relative addressing mode is too
far away.
User Action: Correct the reference to use longword relative addressing mode.

2-312

Messages

TRUNCATE,

line truncated to 'count' characters

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The text you tried to add to a line would extend the line
beyond its maximum length. Therefore, the additional text is truncated to the
maximum allowable length of the line.
User Action: None.
TRUNCATE,

records in 'filename' truncated to 'nnn' bytes

Facility: SEARCH, SEARCH Command
Explanation: One or more records in the listed input file were too long
for SEARCH's internal buffers. The records were shortened to the length
specified before the SEARCH is performed. This is an informational message.
The file contains records that exceed SEARCH's capacity. The SEARCH is
successfully performed on the shortened records.
User Action: None.
TRUNCATED,

string too long-truncated

Facility: DSR, DIGITAL Standard Runoff
Explanation: DSR encountered a string that is too long. The string is
truncated.
User Action: Edit the file and shorten the line.
TRUNCDAT,

computed value is 'valuel' value written is 'value2' at location
'address'

Facility: LINK, Linker Utility
Explanation: This message, which is always issued with the message
TRUNC, gives more information about the truncation error. The variable,
'valuel' is the value the linker needed to store; 'value2' is the value the linker
is able to store (a truncated version). This error is usually caused when a
reference using byte or word PC-relative displacement is made to a target
requiring longword relative displacement.
User Action: Correct the reference to use longword relative addressing mode.
TTL,

text too long: 'string'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: The text value for the command (for example, .TITLE,
.CHAPTER, or .NOTE) is too long for the specified margin setting or page
size, or it contains excessive use of underlining, boldface, or overstriking.
User Action: Reduce the length of or simplify the text.

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.

2-313

Messages

TWOWIDTHS,

/WIDTH and /LINE_WIDTH are redundant-/LINE_WIDTH
value ignored, /WIDTH value used

Facility: DIFF, DIFFERENCES Command
Explanation: You specified both /WIDTH and /LINE_WIDTH; /LINE_
WIDTH is unnecessary.
User Action: None.

TYP, error in file type
Facility: RMS, VMS Record Management Services
Explanation: The file type specified in a file specification contains invalid
syntax, for example, more than 39 characters. Or the use of a logical name
resulted in a duplicate file type specification.
User Action: Correct the syntax of the file specification. Reenter the
command or correct the program, as necessary.

TYPMISMCH,

library type mismatch

Facility: LBR, Librarian Subroutine Package
Explanation: This warning message is generated by the Librarian routines.
On a call to LBR$0PEN, the library type you requested conflicts with
the library type you specified in the create options argument. Processing
continues based on the actual library type.
User Action: None.

UAEERR,

invalid username, username already exists

Facility: AUTHORIZE, Authorize Utility
Explanation: You tried to create a user-record that already exists by using the
DCL command COPY, ADD, or RENAME.
User Action: For the new records, enter a user name that does not currently
exist.

UAFGETERR,

error reading user authorization file

Facility: MAIL, Mail Utility
Explanation: An error occurred reading the user authorization file.
User Action: Use the VMS RMS status code that accompanies this message
to determine your action.

UAFOPNERR,

error opening user authorization file

Facility: MAIL, Mail Utility
Explanation: An error occurred opening the user authorization file.
User Action: Use the VMS RMS status code that accompanies this message
to determine your action.

2-314

Messages

UBF,

invalid user buffer
Facility: RMS, VMS Record Management Services
Explanation: The user record buffer address of the RAB specified an area of
memory that cannot be written to by the caller.
User Action: Verify that the call to the VMS RMS service is coded correctly.

UBMAPEXCED,

UNIBUS map register allocation exceeded

fatal error detected by UDA port driver (PUDRIVER)

attempt to reference undefined psect number decimal-number in
module module-name file filename
1

Facility: LINK, Linker Utility
Explanation: A module referenced an undefined psect.
User Action: Submit a Software Performance Report on the appropriate
language processor.
UDF_BKS,

cannot convert UDF records into spanned file

Facility: CONVERT, Convert Utility
Explanation: UDF records cannot span block boundaries.
User Action: Specify no block spanning.
UDF_BLK,

cannot fit UDF records into single block bucket

Facility: CONVERT, Convert Utility
Explanation: The records in the file are longer than 512 bytes (1 block).
User Action: Specify a bucket size that is long enough for the records.

2-315

Messages

UDFENV,

'undefined environment reference'

Facility: LINK, Linker Utility
Explanation: An undefined reference to an environment is encountered after
Pass 1.
User Action: Determine why the reference is undefined and correct the
condition.
UDFSYM,

'symbol-name'

Facility: LINK, Linker Utility
Explanation: There are strong undefined symbol references after Pass 1. This
message is output for each undefined symbol.
User Action: Determine why the symbols are undefined and correct the
condition.
UDS,

undefined symbol: 'string'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: DSR has detected an unrecognizable symbol (for example,
$$name), the name of which is not defined.
User Action: Remove the symbol.

UICERR,

error in UIC specification

Facility: AUTHORIZE, Authorize Utility
Explanation: You specified a User Identification Code (UIC) incorrectly. User
Identification Codes have the format [group,member] where the values for
group and member may be numeric or alphanumeric. The system translates
each code into a 32-bit octal string; the high-order 16 bits are the group
identifier, the low- order 16 bits are the member identifier. The member
identifer must be unique for each system user. In a numeric UIC, the group
identifier may have an octal value between 1 and 37776. The member
identifier may have an octal value between 0 and 177776. You can omit
leading zeros when specifying a numeric identifier. In an alphanumeric UIC,
the group and member identifiers may have between 1 and 31 characters, of
which at least one must be alphabetic. Alphabetic characters are the letters
A-Z, and the underscore and dollar sign symbols.
User Action: Correct the specification of the UIC, according to the syntax
rules explained above.
UKNFACILITY,

unknown facility code specified

Facility: VAXTPU, VAX Text Processing Utility
Explanation: You specified a facility code that does not match any
established action routine.
User Action: Establish the facility's action routine before attempting to use it.

2-316

Messages

UME,

unmatched end command: 'string'

Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: An .END command (for example, .END NOTE) is detected, but
the associated beginning command (.NOTE) is not.
User Action: Insert the associated beginning command.

UNABLCREVA,

unable to create virtual address space

UNABLE,

unable to create file

Facility: SYSGEN, System Generation Utility
Explanation: The file specified in the SYSGEN command CREATE cannot be
created for one of the following reasons:

•

The device or directory does not exist.

•

The volume is write-locked or the user does not have write access to it.

•

The volume is full or has insufficient contiguous space to complete the
request.

User Action: Correct the situation and reenter the command.

UNABLE,

unable to create parameter file

Facility: SYSGEN, System Generation Utility
Explanation: The file specified in the SYSGEN command WRITE cannot be
created for one of the following reasons:

•

The device or directory does not exist.

•

The volume is write-locked or the user does not have write access.

•

The volume is full.

User Action: Correct the situation and reenter the command.

UNABLE,

unable to open file

Facility: SYSGEN, System Generation Utility
Explanation: The file specified in the SYSGEN command USE cannot be
found or opened.
User Action: Reenter the command specifying the correct file specification.

2-317

Messages

UNAOPNHLP,

unable to open help library 'filespec'

Facility: DEBUG, VMS Debugger
Explanation: The help library 'filespec' cannot be opened to look for the help
you requested. The accompanying VMS RMS status message gives you more
information about the reasons for the library not being opened.
User Action: Examine the VMS RMS status message to determine the
reasons for the help library not being opened, and take action based on that
information. Also, verify that the logical name DBG$HELP is either not
defined, or is defined to indicate the proper file.

UNAOPNSRC,

unable to open source file 'filespec'

Facility: DEBUG, VMS Debugger
Explanation: Source lines from the file 'filespec' cannot be displayed because
the debugger was unable to open the source file (represented as 'filespec').
The accompanying VMS RMS status message gives more information about
the reasons for the source file not being opened.
User Action: Examine the VMS RMS status message to determine the reasons
for the source file not being opened, and take the appropriate action based on
that information.

UNAREASRC,

unable to read source file 'filespec'

Facility: DEBUG, VMS Debugger
Explanation: Source lines from the file 'filespec' cannot be displayed because
the debugger was unable to read the source file (represented as 'filespec'). The
accompanying VMS RMS status message gives more information about the
reasons for the source file not being opened.
User Action: Examine the VMS RMS status message to determine the reasons
for the source file not being read, and take the appropriate action based on
that information.

UNARYOPER,

operand combination 'operator' 'data-type' unsupported

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The specified operator does not support the specified data type.
User Action: Use only supported data types with the operator.

UNASEFC,

unassociated event flag cluster

Facility: SYSTEM, VMS System Services
Explanation: An image called a system service specifying an event flag
number in a common cluster with which it is not associated.
User Action: Check for a programming error. Verify the event flag numbers
specified in system service calls, and verify that the required request to
associate with the cluster completed successfully.

2-318

Messages

UNDEFINEDPROC,

undefined procedure call 1name1

Facility: VAXTPU, VAX Text Processing Utility
Explanation: You have called an undefined procedure.
User Action: Check the spelling of the procedure name.
UNDEFLINK, invalid link name
Facility: LATCP, LAT Control Program
Explanation: A link has not been created for the specified link name.
User Action: Reenter the command with a valid link name.
UNDEFOUTPUT,

line line-number Output parameter/qualifier 1name 1 is not
defined
1

Facility: CDU, Command Definition Utility
Explanation: CDU encountered an undefined OUTPUT parameter/qualifier.
All OUTPUT parameters/qualifiers must be previously defined.
User Action: Edit the CLD file so that all OUTPUT parameters/qualifiers are
defined.
UNDEFSYM,

undefined symbol

Facility: MACRO, VAX MACRO Assembler
Explanation: A local label is referred to but not defined in a local label block;
or, if GLOBAL is disabled, a symbol is referred to but not defined in the
module or specified in an .EXTERNAL directive.
User Action: Define the local label or symbol or specify the symbol in an
.EXTERNAL directive.
UNDEFSYNTAX, line 1line-number 1 : Syntax 1syntax-name 1 is not defined
Facility: CDU, Command Definition Utility
Explanation: CDU encountered an undefined syntax name during a SYNTAX
assignment. All syntax names must be previously defined.
User Action: Edit the CLD file so that all names in SYNTAX assignments are
defined.
UNDEFTYPE,

line 1line-number1 : Type 1type-name 1 is not defined

Facility: CDU, Command Definition Utility
Explanation: CDU encountered an undefined type name during a TYPE
assignment. All type names must be previously defined.
User Action: Edit the CLD file so that all names in TYPE assignments are
defined.

2-319

Messages

UNDEFXFRAD,

undefined transfer address

Facility: MACRO, VAX MACRO Assembler
Explanation: The .END directive specified a transfer address that is not
defined in the module or specified in an .EXTERNAL directive.
User Action: Define the transfer address or delete it from the .END directive.
UNDEXP,

undefined exponentiation User PC 'location'

Facility: MTH, Mathematics Facility
Explanation: An expression contained exponentiation that cannot be
mathematically evaluated, for example, O.**O. The result is the reserved
operand, minus zero.
User Action: Use the traceback information or the PC displayed in the
message to locate the error in your program and correct the math expression.
UNDFIL,

file has been not opened by DCL-check logical name

Facility: CLI, Command Language Interpreter (DCL)
Explanation: A DCL command READ, WRITE, or CLOSE specified a file that
is not currently opened or for which no logical name is assigned.
User Action: Reenter the command; specify the name of an opened file. Or
use the DCL command OPEN to open the file before attempting to read or
write it.
UNDKEY,

'state' key 'key-name' is undefined

Facility: CLI, Command Language Interpreter (DCL)
Explanation: You attempted to use the SHOW/KEY or the DELETE/KEY
command to show or delete the definition of a key that is not defined.
User Action: None.
UNDOPTION,

undefined option flag is set

Facility: SORT, Sort/Merge Utility
Explanation: You can set only those option flags used by SORT /MERGE. All
other bits in the longword are reserved and must be zero.
User Action: Correct your specification file.
UNDSYM,

undefined symbol-check validity and spelling

Facility: CLI, Command Language Interpreter (DCL)
Explanation: A character string beginning with an alphabetic character
is encountered in a context where the command interpreter evaluates
expressions and automatically attempts symbol substitution. The character
string is not defined as a local symbol for the current command level or as a
global symbol.
User Action: Verify that the symbol is defined and reenter the command. If
the error occurred in a command procedure, correct the procedure to ensure
that the symbol is defined locally or globally, as required before the statement
that caused the error.

2-320

Messages

UNDTERNAM,

undefined terminal name

Facility: SMG, Screen Management Facility
Explanation: The requested terminal definition is not found in the caller's
private copy of Termtable or the system copy Termtable.
User Action: If you intended to use a private terminal definition, make sure
that TERMTABLE.EXE exists in your private directory and that the logical
name TERM$TABLOC points to it. If you expected your terminal to be
defined in the system Termtable, check with your system manager.
UNDTERNOP,

undefined terminal-couldn't access private terminal table

Facility: SMG, Screen Management Facility
Explanation: The requested terminal definition is not found in the caller's
private copy of Termtable or the system Termtable. The caller's private
Termtable could not be accessed, either because it did not exist or because
RMS could not open the file.
User Action: If you intended to use a definition from your private Termtable,
make sure that TERMTABLE.EXE exists in your private directory and that
the logical name TERM$TABLOC points to it. Make sure that you have read
access to the file.
UNDTERNOS,

undefined terminal-couldn't access system terminal tables

Facility: SMG, Screen Management Facility
Explanation: The requested terminal definition is not found in the caller's
private Termtable or the system Termtable. The system Termtable is
unavailable.
User Action: The system Termtable should be mapped as a global section
and therefore should always be available. Consult your system manager.
UNDTERTYP,

undefined terminal type

Facility: SMG, Screen Management Facility
Explanation: The definition for the requested terminal type is not found in
the caller's private copy of Termtable or the system Termtable.
User Action: If you intended to use a private definition, make sure that
TERMTABLE.EXE exists in your private directory and that the logical name
TERM$TABLOC points to it. If you expected your terminal definition to exist
in the system Termtable, consult your system manager.
UNECLIERR,

unexpected CLI error

Facility: LIB, Library Facility
Explanation: The CLI returned an error status that is not recognized. This
error could be caused by use of a nonstandard CLI.
User Action: If this error occurs while using the DCL Command Language
Interpreter, submit a Software Performance Report.

2-321

Messages

Unexpected characters after end of command
Facility: EDT, EDT Editor
Explanation: The command you entered ends with a string of one or more
characters that is not part of the command. The rest of the command is valid.
User Action: Reenter the command removing the invalid characters from the
end of the command line.

UNEXPECTED,

installation terminated due to unexpected event.

Facility: VMSINSTAL, Install Procedures
Explanation: An unexpected event has ended the installation of
VMSINSTAL. See accompanying messages for more information.
User Action: If you can determine and resolve the problem, reinstall the
product. Otherwise, contact your DIGITAL field service representative.

Unexpected Interrupt-CNF /PMC/PSR 'xxxxxxxx/xxxxxxxx/xxxxxxxx',
Facility: VAXport, 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 field service to check the port hardware.

UNEXPERR,

unexpected exception

Facility: VAXCLUSTER, VAXcluster Facility
Explanation: A hardware exception occurred during bootstrap execution.
User Action: Run diagnostics to check for hardware errors.

UNEXPERR,

unexpected interrupt

Facility: VAXCLUSTER, VAXcluster Facility
Explanation: An unknown interrupt occurred during bootstrap execution.
User Action: Try the operations again. If the problem persists, run
diagnostics to check for hardware errors.

UNEXPERR,

unexpected error

Facility: MONITOR, Monitor Utility
Explanation: An unexpected hardware or software error condition occurred.
To obtain more information, examine the accompanying linked message.
User Action: Correct the condition causing the failure, if possible, and reenter
the MONITOR request. Otherwise, submit a Software Performance Report.

2-322

Messages

UNEXPEXC,

A debugger exception handler is called during program execution
this debugging session may not be reliable

Facility: DEBUG, VMS Debugger
Explanation: This error can occur if the debugger is running and an exception
is signaled in one of the program's exit handlers; either a CTRL/Y EXIT
operation is performed, or a Force Exit system service call ($FORCEX) is
issued on behalf of the process.
User Action: Identify and correct the error in the user program. If the
debugger reports this error under circumstances other than those described,
then submit a Software Performance Report.

UNEXUBAINT,

unexpected UNIBUS adapter interrupt

UNINITVAR,

uninitialized variable

Facility: VAXTPU, VAX Text Processing Utility
Explanation: You have tried to use an unspecified variable.
User Action: Check the spelling of the variable. You may assign a value to
the variable by placing it on the left-hand side of an assignment statement.

UNIVSTAR,

UNIVERSAL=* option is ignored unless /NOEXECUTABLE specified

Facility: LINK, Linker Utility
Explanation: The UNIVERSAL=* option has been specified in the options file
when producing a shareable image output file. This option is no longer valid
when producing image files, although it is accepted when generating only a
symbol table (.STB) output file.
User Action: If you desire a shareable image output file, then you must
specify all universal symbols explicitly. Otherwise, if you only need a symbol
table file, then specify /NOEXECUTABLE to suppress image file output.

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.

2-323

Messages

UNKCLASS,

unknown device class found, 'device-class-value'

Facility: ERF, Error Log Utility
Explanation: An entry with an unknown or unsupported device class is
encountered.
User Action: Use the UNKNOWN_ENTRIES keyword with the /INCLUDE
qualifier to obtain the report.

UNKCPU,

unknown or unsupported processor

Facility: VAXCLUSTER, VAXcluster Facility
Explanation: The system is not supported as a satellite node with this version
of the VMS operating system.
User Action: Refer to the VMS Software Product Description (SPD) for
supported configurations for VAXclusters and check which versions of the
VMS operating system support your processor.

UNKCPU,

unknown CPU type encountered

Facility: SYSGEN, System Generation Utility
Explanation: You specified an unknown CPU type with the SYSGEN
command SHOW/ ADAPTER.
User Action: Retry specifying a different CPU type.

UNKDEV,

unknown device type

Facility: INIT, INITIALIZE Command and 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.

UNKENTRY,

unknown entry type, 'entry-type value'

Facility: ERF, Error Log Utility
Explanation: An entry with an unknown or unsupported entry type is
encountered.
User Action: Use the UNKNOWN _ENTRIES keyword with the /INCLUDE
qualifier to obtain the report.

UNKESCAPE,

unknown escape sequence read

Facility: VAXTPU, VAX Text Processing Utility
Explanation: TPU does not know how to process the escape sequence.
User Action: Use only supported terminals with TPU.

UNKESCSEQ,

unknown escape sequence received from DECtalk

Facility: DTK, DECtalk Facility
Explanation: You passed an escape sequence to a DTK$ input routine that it
is unable to understand.
User Action: Submit a Software Performance Report.

2-324

Messages

UNKKEYWORD,

an unknown keyword has been used as an argument

Facility: VAXTPU, VAX Text Processing Utility
Explanation: You have specified an unrecognizable item in place of a valid
keyword.
User Action: Execute the built-in procedure SHOW (KEYWORDS) for a list
of valid keywords.
UNKMSG,

unknown message header type

Facility: REM, Set Host Facility
Explanation: A system internal error has occurred.
User Action: Submit a Software Performance Report.
UNKNFAIL,

internal VAXTPU failure, unknown reason

Facility: VAXTPU, VAX Text Processing Utility
Explanation: An internal error occurred in the VAXTPU software.
User Action: Submit a Software Performance Report.
UNKNOPR,

unknown operator

Facility: OPCOM, Operator Communication
Explanation: A DCL command REQUEST or REPLY specified an invalid
operator name; the keyword is invalid. No request message is sent.
User Action: Reenter the DCL command REQUEST or REPLY and specify a
valid operator name.
UNKNPRQ,

unknown Inter-processor Request Message

unknown object in SMI call

Facility: SMI, System Management Intergator/Server
Explanation: This message indicates an internal error. The server does not
recognize the object.
User Action: Ensure that all the nodes in the environment contain the correct
versions of SMISERVER and SYSMAN. If no problems are found, submit a
Software Performance Report with the exact sequence of SYSMAN commands
leading to the error.

2-325

Messages

UNKOPCODE,

unknown opcode

Facility: VAXTPU, VAX Text Processing Utility
Explanation: An internal error occurred in the VAXTPU software.
User Action: Submit a Software Performance Report.

UNKPKTFMT,

unknown packet format, entry 'number' ~skipped

Facility: ERF, Error Log Utility
Explanation: An entry with an unknown or unsupported record format was
encountered.
User Action: Submit a Software Performance Report.

UNKREPL Y,

unknown reply received from DEC talk

Facility: DTK, DECtalk Facility
Explanation: You passed an escape sequence to a DTK$ input routine that it
could not parse correctly.
User Action: Submit a Software Performance Report.

UNKRSTRT,

unknown restart code

UNKTYPE,

unknown data type

Facility: VAXTPU, VAX Text Processing Utility
Explanation: An internal error occurred in the VAXTPU software.
User Action: Submit a Software Performance Report.

UNKTYPE,

unknown device type, 'device-type value'

Facility: ERF, Error Log Utility
Explanation: An entry with an unknown or unsupported device type is
encountered.
User Action: Use the UNKNOWN _ENTRIES keyword with the /INCLUDE
qualifier to obtain the report.

2-326

Messages

UNKWNDESC,

unknown descriptor type

Facility: VAXTPU, VAX Text Processing Utility
Explanation: A descriptor in the descriptor array has an unknown data type.
User Action: Use a valid data type.
UNLKVOL,

error unlocking volume set

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility encountered an error during an attempt
to unlock the volume set to allow allocation. The accompanying message
provides additional information.
User Action: Correct the condition that caused the error, then dismount and
remount the volume set.
UNLOCKED,

'filename' unlocked

Facility: SET, SET Facility
Explanation: The file has been successfully unlocked.
User Action: None.
UNLOCKED,

'filespec' unlocked

Facility: Shared by several facilities
Explanation: The file specified by a DCL command UNLOCK is unlocked.
User Action: None.
UNLOCKERR,

error unlocking 'filename'

Facility: SET, SET Facility
Explanation: An error occurred when the file is being unlocked. This
message is issued with an accompanying message.
User Action: Take corrective action based on the accompanying message.
UNMTCHPARN,

unmatched left parenthesis found

Facility: DEBUG, VMS Debugger
Explanation: A left parenthesis ( () does not have a matching right
parenthesis () ).
User Action: Include the right parenthesis ( )).
UNPRIKW,

unrecognized primary keyword in statement

Facility: FDL, Create/FDL Utility, FDL, Edit/FDL Utility
Explanation: You misspelled a keyword.
User Action: Edit the FDL file to correct your spelling and try again.

2-327

Messages

UNPROP ARM,

unprocessed parameters

Facility: CU, Command Language Interpreter (DCL)
Explanation: A command contained more parameters than are currently
supported.
User Action: Reenter the command; specify only the maximum number of
parameters.

UNPROQU AL,

unprocessed qualifiers

Facility: CU, Command Language Interpreter (DCL)
Explanation: The message indicates that qualifiers present with the command
were ignored. The operating system does not normally display this message.
User Action: Note the condition. Modify the source program, if necessary, to
detect and respond to the condition.
If either the /SHOW or the /CROSS_REFERENCE qualifier is specified

without /LIST, reenter the command with the /LIST qualifier.
UNPROQUAL,

unprocessed qualifiers

Facility: CU, Command Language Interpreter (DCL) and MACRO, VAX
MACRO Assembler
Explanation: This message is associated with a status code returned from
the command interpreter's result parse routine. The message indicates that
qualifiers present with the command were ignored. The operating system
does not normally display this message.
If this error occurred as a result of a macro assembler operation, either the

/SHOW or the /CROSS_REFERENCE qualifier is specified without the /LIST
qualifier. The MACRO assembler does not process the source file or produce
an object module.
User Action: Note the condition. Modify the source program, if necessary, to
detect and respond to the condition.
If either the /SHOW or the /CROSS_REFERENCE qualifier is specified

without /LIST, reenter the command with the /LIST qualifier.
UNQUAKW,

unrecognized qualifier keyword in statement

Facility: FDL, Create/FDL Utility, FDL, Edit/FDL Utility
Explanation: You misspelled a keyword.
User Action: Edit the FDL file to correct your spelling and try again.

UNRCMD,

unrecognized command 'command'

Facility: SHOW CLUSTER, Show Cluster Utility
Explanation: The command entered is not a valid SHOW CLUSTER
command.
User Action: Enter a valid command or enter the HELP command for a list
of valid commands.

2-328

Messages

UNRCMP,

unrecognized component 'text'

Facility: NCP, Network Control Program
Explanation: A component is not known to the node. The 'text' part of this
message contains the component identification.
User Action: Review the command description and reenter your command
with the correct component.
UNREACHABLE,

remote node is not currently reachable

Facility: SYSTEM, VMS System Services
Explanation: An attempt is made to initiate a DECnet-VAX logical link
connection. The specified node exceeded routing requirements, that is, the
path to the node contains too many intermediate nodes.
User Action: This condition will persist until there is a change in the network
topology. Notify your system manager. Refer to the VMS Networking Manual
for additional information.
UNREACHABLE,

unreachable code

Facility: VAXTPU, VAX Text Processing Utility
Explanation: This code will never be executed. The compiler might remove
this code to optimize performance.
User Action: Remove the unreachable code.
Unrecognized command,
Facility: EDT, EDT Editor
Explanation: EDT does not recognize or support the command entered. The
command may have been incorrectly specified.
User Action: Check the command syntax and reenter the command.
Unrecognized command option,
Facility: EDT, EDT Editor
Explanation: The command you entered includes an invalid option/qualifier.
User Action: Reenter the command specifying a valid option/qualifier.
Unrecognized SCA Packet
Facility: VAXport, 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, including the error log
file that contains this entry and the crash dumps from both the local and
remote systems.

2-329

Messages

UNRECSTA,

unrecognized statement

Facility: SMG, Screen Management Facility
Explanation: The Termtable compiler encountered a statement that it does
not recognize.
User Action: Check your definition. Make sure you have spelled keywords
correctly and that statements appear only in valid sequences.
UNRECSTMT,

unrecognized statement

Facility: MACRO, VAX MACRO Assembler
Explanation: The operator is not an opcode, directive, user-defined opcode,
previously defined macro, or macro in a library.
User Action: Change the operator to a valid opcode, directive, or macro; or
define the macro.
UNREL VOL,

volume is not part of volume set being mounted

Facility: MOUNT, Mount Utility
Explanation: You specified a volume 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.
UNRFORCOD,

unrecognized format code

Facility: LIB, Library Facility
Explanation: Unrecognized format code
User Action: Examine the format string for invalid format code. The format
string may be supplied in the logical name or it can be hard-coded.
UNRFUN,

unrecognized function or option

Facility: NCP, Network Control Program
Explanation: Either the verb or component requested a feature that is
unsupported or is unrecognized.
User Action: Consult the documentation for the supported functions and
operations.
UNRKEY,

keyword is an unrecognized keyword

Facility: LIB, Library Facility
Explanation: This message is associated with a status code returned from the
Run-Time Library. The indicated keyword is not recognized.
User Action: Correct the program and specify a valid keyword.

2-330

Messages

UNRKEY,

unrecognized field or class name 'class-name'

Facility: SHOW CLUSTER, Show Cluster Utility
Explanation: The field or class name entered is not valid in any report.
User Action: Enter a valid field or class name, or enter the HELP FIELDS or
HELP CLASSES command for a list of valid field or class names.
UNRPTY,

unrecognized parameter type 'text'

Facility: NCP, Network Control Program
Explanation: A parameter type specified in your command is incorrect and
therefore unrecognizable by the network management software. The 'text'
part of the message identifies the unrecognizable parameter.
User Action: Review the command description and reenter your command
with the correct parameter.
UNSAFE,

drive unsafe

Facility: SYSTEM, VMS System Services
Explanation: The drive malfunctioned and cannot be used.
User Action: Check the status of the device and repeat the request. If the
failure persists, notify the system manager.
UNSECKW,

unrecognized secondary keyword in statement

Facility: FDL, Create/FDL Utility, FDL, Edit/FDL Utility
Explanation: You misspelled a keyword.
User Action: Edit the FDL file to correct your spelling and try again.
UNSOLICIT,

response not solicited

Facility: SYSTEM, VMS System Services
Explanation: A message is received that is not requested from a local process.
This may be an information exception or a control message from a remote
user.
User Action: Process the message
UNSTLEV,

/INPUT file has an unsupported MONITOR file structure level

Facility: MONITOR, Monitor Utility
Explanation: The input recording file is a valid MONITOR file with a file
structure that is not supported by the current version of MONITOR.
User Action: Use the monitor convert command to update the recording file
to the current structure level.

2-331

Messages

UNSUPRTCPU,

unsupported CPU

version of listener on executor is not supported

Facility: NCP, Network Control Program
Explanation: The network management listener (NML) did not respond
with a valid version number. The executor cannot be accessed by network
management.
User Action: None. You cannot connect to the node until it is upgraded to a
supported version.
UNTERMARG,

unterminated argument

Facility: MACRO, VAX MACRO Assembler
Explanation: The string argument is missing a delimiter or the macro
argument is missing an angle bracket.
User Action: Add a delimiter or an angle bracket to the string argument.
UNTERMCOND,

unterminated conditional

Facility: MACRO, VAX MACRO Assembler
Explanation: A conditional assembly block is not terminated by the .ENDC
directive. The assembler inserted the .ENDC directive before the .END
directive.
User Action: Add the .ENDC directive to the conditional assembly block.
UNWIND,

unwind currently in progress

Facility: SYSTEM, VMS System Services
Explanation: This status code is used as a call argument for condition
handlers called during the search of the call stack during an unwind
operation. The operating system does not normally display this message.
User Action: Note the condition. Modify the source program, if necessary, to
detect and respond to the condition.

2-332

Messages

UNWINDING,

unwind already in progress

Facility: SYSTEM, VMS System Services
Explanation: A condition handler is called during an unwind operation
and attempted to issue an unwind request. The operating system does not
normally display this message.
User Action: Note the condition. Modify the source program, if necessary, to
detect and respond to the condition.

UNXINTEXC,

unexpected interrupt or exception

UNXPCTSTS,

unexpected status detected. Expected status'. Found:

Facility: Shared by several facilities
Explanation: An error is detected by a system service. A subsequent message
explains the reason for the error.
User Action: See the description of the accompanying VMS RMS message in
this manual.

UNXSIGNAL,

unexpected signal name in ACP

UPDATE,

patch with eco level 'nn' ignored due to update qualifier

Facility: PATCH, Patch Utility
Explanation: The Patch Utility ignored the patch associated with this ECO
level because you used the /UPDATE qualifier and did not include this
particular ECO level in the qualifier's value list.
User Action: Add the ECO level to the qualifier's value list; retry if you want
this ECO to be applied.

2-333

Messages

UPDATED,

file 'filename' is already updated.

Facility: VMSINSTAL, Install Procedures
Explanation: VMSINSTAL is attempting to update a system text file, but the
file has already been updated successfully.
User Action: None.

UPDURTRAV, index update during traverse illegal
Facility: LBR, Librarian Subroutine Package
Explanation: The routine that you specify in the routine-name argument
cannot contain any calls to either LBR$DELETE or LBR$INSERT_KEY.
User Action: Remove any embedded calls to either LBR$DELETE or
LBR$INSERT_KEY before calling the routine.

UPI,

UPI not set when sharing and BIO or BRO set
Facility: RMS, VMS Record Management Services
Explanation: VMS RMS permits file sharing when block IjO access (BIO or
BRO) is specified and the file-sharing option UPI is specified also. The user
program must provide all required interlocks.
User Action: Verify that the call to the VMS RMS service is coded correctly.

URE,

unrecoverable error processing record 'In' on page 'pn' of input file
'filename'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: An irrecoverable 1/0 error occurred, terminating the processing
at the specified edit line (In) and page number (pn) of the input file. This is a
DSR internal error.
User Action: Submit a Software Performance Report.

URR,

unrecognized request: 'n'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: DSR detected an unrecognizable internal failure request. This
indicates DSR internal error.
User Action: Reprocess the file. If the error occurs again, submit a Software
Performance Report.

USCALL,

target of CALL not found-check spelling and presence of label

Facility: CLI, Command Language Interpreter (DCL)
Explanation: The destination label of a CALL statement could not be found.
To be a valid destination, the label must be followed by the SUBROUTINE
statement.
User Action: Make sure that the CALL statement in your command
procedure is using the correct label, or that the subroutine label exists and is
followed by the SUBROUTINE statement.

2-334

Messages

USEANS,

auto-answer file will be used.

Facility: VMSINSTAL, Install Procedures
Explanation: You specified the auto-answer option when you started
VMSINSTAL. The recorded answers will be used for the installation.
User Action: You do not have to answer prompts and questions displayed by
the product. If you want to record new answers, delete the answer file and
install the product with the auto-answer option.

USEFLORES,

use of floating reserved operand

Facility: OTS, General Purpose Facility and LIB, Library Facility
Explanation: A program accessed a reserved floating operand. This message
is associated with a status code returned by the Run-Time Library.
User Action: Use the traceback information to locate the statement that
caused the error and correct your program.

USERDSABL,

user 'username' cannot receive new mail

Facility: MAIL, Mail Utility
Explanation: You have attempted to send mail to a user who has been
disallowed from receiving mail.
User Action: None.

USERQST,

request 'number' from user 'user-name

Facility: OPCOM, Operator Communication
Explanation: This is a user message to the operator; a response is required.
User Action: Wait for the operator response.

USERSPEC,

invalid user specification 'user-name'

Facility: MAIL, Mail Utility
Explanation: While sending a mail message to a list of users, you specified
an invalid user name.
User Action: Ensure that your list contains valid user names and retry the
operation.

USERVAL,

user validation error

Facility: INPSMB, Input Symbiont
Explanation: The user name and password specified in a batch job entered
from a card reader are not authorized on the system according to the user
authorization file.
User Action: Consult your system manager.

2-335

Messages

USEUDFEN2,

undefined environment number 'number' referenced in psect
'string' offset 'hexadecimal-number' in module 'module-name' file
'filename'

Facility: LINK, Linker Utility
Explanation: An undefined environment is referenced in a module.
User Action: Ensure that all referenced environments are defined.
USEUDFENV,

undefined environment 'string' referenced in psect 'string' offset
'hexadecimal-number' in module 'module-name' file 'filename'

Facility: LINK, Linker Utility
Explanation: An undefined environment is referenced in a module.
User Action: Ensure that all referenced environments are defined.
USEUDFLSY,

undefined module-local symbol 'symbol name' referenced in psect
'string' offset 'hexadecimal-number' in module 'module-name' file
'filename'

Facility: LINK, Linker Utility
Explanation: An undefined module-local symbol is referenced in a module.
User Action: Ensure that all referenced module-local symbols are defined.
USEUNDEF,

undefined symbol 'symbol-name' referenced in psect 'psect-name'
offset 'address' in module 'module-name' file 'filename'

Facility: LINK, Linker Utility
Explanation: An undefined symbol is referenced in a module.
User Action: Define the symbol.
USEUNDEF2,

undefined symbol 'symbol-name' referenced in debug or traceback
record in module 'module-name' file 'filename'

Facility: LINK, Linker Utility
Explanation: An undefined symbol is referenced in a debug or traceback
record.
User Action: Define the symbol.
USGOSUB,

target of GOSUB not found-check spelling and presence of label

Facility: CLI, Command Language Interpreter (DCL)
Explanation: The destination label of a GOSUB statement could not be
found.
User Action: Make sure that the GOSUB statement in your command
procedure is using the correct label, or that the subroutine label exists.

2-336

Messages

USGOTO,

target of GOTO not found-check spelling and presence of label

Facility: CU, Command Language Interpreter (DCL)
Explanation: The label of a GOTO command could not be found in the
current command file.
User Action: Correct the command file by ensuring that the correct label
exists.
USRINPERR,

user input routine returned error status

Facility: LBR, Librarian Subroutine Package
Explanation: A user-supplied input routine returned a nonsuccess status to
LBR$0UTPUT_HELP.
User Action: Determine the reason for the failure in the input routine.
USRTFR,

image 'image-name' has no user transfer address

Facility: LINK, Linker Utility
Explanation: An executable image does not contain a transfer address.
User Action: Define a transfer address for the image.
USZ, invalid user buffer size
Facility: RMS, VMS Record Management Services
Explanation: The size specified in the user record buffer size field is invalid.
The buffer size must be in the range of 1 to 65,535.
User Action: Verify that the call to the VMS RMS service is coded correctly.
V2COMP,

parameter not applicable on V2.0 DECnet executor node

Facility: NCP, Network Control Program
Explanation: A given request could not be converted into a Version 2.0 NICE
message when connected to a Version 2.0 network management listener
(NML).
User Action: Remove the invalid parameter from the command line.
VALERR,

specified value is out of legal range

Facility: DSR, DIGITAL Standard Runoff
Explanation: A value is specified that is outside the range for valid values.
User Action: Make sure that the value is within the range.
VALERR,

specified value is out of legal range

Facility: Shared by several facilities
Explanation: A value is specified which is not within legal range.
User Action: Respecify a value within legal range.

2-337

Messages

VALNOTADDR,

value of variable 'symbol-name' not usable as address

Facility: DEBUG, VMS Debugger
Explanation: The value of the specified variable is not usable as an address.
The address must be a longword.
User Action: Modify the address and retry the operation.

VALPRI,

value required on primary in statement 'n'

Facility: FDL, Create/FDL Utility, FDL, Edit/FOL Utility
Explanation: You specified a primary that requires a value, but none is given.
User Action: Supply a value for the primary.

VALREQ,

missing qualifier or keyword value-supply all required values

Facility: CLI, Command Language Interpreter (DCL)
Explanation: A value must be specified for the qualifier or keyword.
User Action: Reenter the command and supply a value to the qualifier or
keyword.

VALTOOBIG,

value too large for field

Facility: AUTHORIZE, Authorize Utility
Explanation: The value you specified for a qualifier is too large.
User Action: See the VMS Authorize Utility Manual for information about
qualifier value sizes. Enter a smaller value for the qualifier.

VALUE,

set to maximum

Facility: SYSGEN, System Generation Utility
Explanation: A SYSGEN command SET is entered to set a parameter to
a value that is greater than the allowable maximum. The SYSGEN utility
reduces the value to the allowable maximum.
User Action: None.

VALUE,

set to minimum

Facility: SYSGEN, System Generation Utility
Explanation: A SYSGEN command SET is entered to set a parameter to a
value that is less than the allowable minimum. The SYSGEN utility increases
the value to the permissible minimum.
User Action: None.

VASFULL,

virtual address space is full

Facility: SYSTEM, VMS System Services
Explanation: The virtual address space is full.
User Action: Reboot and increase the amount of allowable virtual address
space.

2-338

Messages

VAX port is going off line
Facility: VAXport, VAXport Driver
Explanation: The VAXport driver halts port operations.
User Action: Restore power to the port hardware.

VAX port is reinitializing
Facility: VAXport, 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 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.

VBNMAPFAIL,

virtual block map failure

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.

2-339

Messages

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.
VECFULL,

privileged vector limit of 42 exceeded

Facility: SYSTEM, VMS System Services
Explanation: This severe error message is associated with a status code
returned from a system service request. The privileged vector limit of 42 is
exceeded.
User Action: Remove unnecessary vectors and relink.
VECINUSE,

vector 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.
VER,

error in version number

Facility: RMS, VMS Record Management Services
Explanation: The version number specified in a file specification contains
invalid syntax, for example, nonnumeric characters or a value larger than
32,767.
User Action: Correct the syntax of the file specification. Reenter the
command or correct the program, as necessary.
VERBNOTFND,

verb 'verb-name' not found in command tables

Facility: CDU, Command Definition Utility
Explanation: The verb you tried to delete is not defined in the CLD file.
User Action: Ensure that the syntax is correct and try to delete the .CLD file
again.
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 back-up procedure.
User Action: Note that the copies are inconsistent.

2-340

Messages

VERIFY! CF,

'opening/ closing' command procedure 'filespec'

Facility: DEBUG, VMS Debugger
Explanation: The debugger is verifying a command procedure. This message
is displayed before the command procedure is executed and after all the
commands have been displayed. This message is informational.
User Action: None.
VFC,

record too short to fill fixed part of VFC record
Facility: CONVERT, Convert Utility
Explanation: There are fewer bytes in the input record than are required for
the fixed portion of the VFC output record.
User Action: Either make the fixed control portion of the output record
smaller, or do not use the /FIXED_CONTROL option.

Virtual Circuit Timeout
Facility: VAXport, 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.
VMB-F-Bootfile not contiguous
Facility: VMB, Virtual Memory Boot
Explanation: The file [SYSEXE]SYSBOOT.EXE is located but is not
contiguous.
User Action: The disk you are attempting to bootstrap cannot be
bootstrapped. Obtain another copy of the system disk.
VMB-F-Failed to initialize device
Facility: VMB, Virtual Memory Boot
Explanation: Encountered an error in the load path while VMS was trying to
initialize the boot device.
User Action: Try initializing again. If this fails, call Field Service.
VMB-F-1/0 error reading boot file
Facility: VMB, Virtual Memory Boot
Explanation: An uncorrectable read error occurred while the file
[SYSEXE]SYSBOOT.EXE was being read.
User Action: Try rebooting the disk. If subsequent attempts fail, obtain
another copy of the system disk.

2-341

Messages

VMB-F-Nonexistent drive
Facility: VMB, Virtual Memory Boot
Explanation: The specified drive number does not exist.
User Action: Specify an appropriate device unit to the console program, or
use a different console bootstrap command procedure.
VMB-F-Unable to locate BOOT file
Facility: VMB, Virtual Memory Boot
Explanation: The file [SYSEXE]SYSBOOT.EXE could not be found.
User Action: You are attempting to bootstrap a volume that does not contain
a VMS binary system. Attempt to reboot using an appropriate disk volume.
VMB-F-U nexpected exception
Facility: VMB, Virtual Memory Boot
Explanation: An unexpected exception occurred while the primary bootstrap
(VMB.EXE) was being executed. This condition probably indicates a corrupted
SYSBOOT.EXE file or a hardware failure.
User Action: Determine the source of the error, and either obtain a new copy
of the system disk or call your DIGITAL field service representative.
VMB-F-Unexpected machine check
Facility: VMB, Virtual Memory Boot
Explanation: An unexpected machine check occurred while the primary
bootstrap (VMB.EXE) was being executed: This condition probably indicates a
corrupted SYSBOOT.EXE file or a hardware failure.
User Action: Determine the source of the error, and either obtain a new copy
of the system disk or call your DIGITAL field service representative.
VOIALREXI,

voice-ID already exists for this device

Facility: DTK, DECtalk Facility
Explanation: A user tried to create a new voice identifier for a DECtalk
device when one already exists. This is normal in a modular environment.
The existing voice identifier is returned.
User Action: None. Make sure you do not delete a voice identifier that you
did not create.
VOLALRMNT,

another volume of same label already mounted

Facility: MOUNT, Mount Utility
Explanation: Shared, group, and system volumes that are mounted
concurrently must have unique volume labels. The request to mount a
volume that has the same label as a volume already mounted failed.
User Action: Mount the volume as a private volume, if it does not have to
be shared; or wait until the conflicting volume has been dismounted. You can
determine the status and ownership of the conflicting volume with the DCL
command SHOW DEVICES/FULL/MOUNTED.

2-342

Messages

VOLIDENT,

label= 'volume-label', owner= 'user-name', format= 'volumeformat'

Facility: MOUNT, Mount Utility
Explanation: This is an informational message that identifies an incorrectly
specified volume after the INCVOLLABEL and NOHOMEBLK errors in a
MOUNT request.
User Action: None. This message is informational. 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.

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.

VOLINV,

volume is not software enabled

Facility: SYSTEM, VMS System Services
Explanation: The volume valid bit is not set for the volume. All physical and
logical 1/0 operations will be rejected until the bit is set.
User Action: Check for a programming error. Verify that the volume is
mounted and loaded. Check to see that the power is on before retrying the
program.

VOLMOUNT,

the volume 'volume-name' is already mounted

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility ignored a MOUNT command because the
volume is already mounted.
User Action: None.

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.

2-343

Messages

VOLOERR,

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 VMS
and other DIGITAL operating systems.
User Action: Reenter the MOUNT command and include the
/OVERRIDE=OWNER_ID option.
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 corrective action based on the accompanying messages.
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 corrective action based on the accompanying messages.
VOLUME_FULL,

volume is full (insufficient space for the request)

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility is unable to copy a file because the
volume had insufficient space.
User Action: RT-11 only supports contiguous files, therefore there must
be a free space on the volume as large as the file you are trying to copy.
Use the DIRECTORY /ALL command to see where the unused areas on the
volume are. By deleting unneeded files which are adjacent to unused areas, it
might be possible to create a large enough space. Also, if you use the COPY
command to copy a file to the same volume, you can move files around and
make larger free areas.
WACKQEMPTY,

NETACP-ack wait queue empty

2-344

Messages

'WAITERR,

error waiting for RMS operation to complete

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility encountered an error while waiting for
RMS.
User Action: This is only possible if EXCHANGE is interrupted by a
CTRL/Y. Repeat the command and let it complete without interruption.
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.
WANTOSEND,

do you want to send anyway (Y/N, default is N)?

Facility: MAIL, Mail Utility
Explanation: One or more of the addresses were unavailable.
User Action: Type Y if you want to send your message to the available
addresses.
WARNING,

parsed with warnings

Facility: FDL, Create/FDL Utility
Explanation: This message accompanies the other warning-level messages.
User Action: The FDL file parsed successfully; you may either correct the
cause of the warning or continue.
WARNISUE,

completed with warnings

Facility: LINK, Linker Utility
Explanation: The link completed, but warnings were issued.
User Action: None.
WASECC,

successful transfer; no data check

Facility: SYSTEM, VMS System Services
Explanation: This message is associated with a status code returned by
I/O functions. A data check operation is not performed. The function is a
read operation that is completed successfully by applying one or more ECC
corrections. The specified data check, however, is not performed.
User Action: Note the condition. Modify the source program, if necessary, to
detect and respond to the condition.

2-345

Messages

WBE,

error on write behind
Facility: RMS, VMS Record Management Services
Explanation: An error occurred during a VMS RMS operation for which
write behind is specified.
User Action: The status value (STV) field of the RAB contains a system status
code that provides more information about the condition. Take corrective
action based on this status code.

WCBFCBMNG,

WCB/FCB correspondence broken

WCC, invalid wildcard context (WCC) value
Facility: RMS, VMS Record Management Services
Explanation: The wildcard context value in the NAM block (an input fileprocessing option) contains an invalid value.
User Action: Verify that the call to the VMS RMS service is coded correctly
and that the NAM block is not inadvertently modified between VMS RMS
service calls.

WCSCORR,

WCS error correction failed

WDW_MAXPREV,

too many previous records in window

Facility: SEARCH, SEARCH Command
Explanation: SEARCH could not create enough buffer space to hold all the
records in a window. Only records before the match are significant; SEARCH
does not need to store records that follow the match.
User Action: Specify a smaller window, or ask your system manager to have
your paging file quota increased.

2-346

Messages

WDW_MAXPRM,

too many window parameters

Facility: SEARCH, SEARCH Command
Explanation: The /WINDOW parameter is not specified correctly.
User Action: Reenter the command using the correct syntax.

WER,

file write error

Facility: RMS, VMS Record Management Services
Explanation: An error occurred during a VMS RMS write operation.
User Action: The status value (STV) field of the RAB contains a system status
code that provides more information about the condition. Take corrective
action based on this status code.

WFR,

.RESTORE not in same file as .SAVE/.SAVEALL: "additional locational
information"
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: You cannot issue a .RESTORE directive for a .SAVE directive
from within a require file if that .SAVE directive occurred in a higher level file
or another require file.
User Action: Change the order of directives so that the .REQUIRE directive
is issued between the .SAVE and .RESTORE directives.

WILDCONCAT,

wildcard specification cannot be concatenated

Facility: Shared by several facilities
Explanation: A number of files to be concatenated cannot be specified with
wild cards.
User Action: Respecify the files without using wildcards.

WILDOVTVER,

wildcard version required for output file

Facility: Shared by several facilities
Explanation: A wildcard version must be specified on an output file.
User Action: Correct the command specifying the wildcard version.

WILUSERMS,

output will be performed by RMS later

Facility: SMG, Screen Management Facility
Explanation: Normally, the screen is updated at the end of every output
operation. If, however, the 'device-name' is actually a file or an unknown
terminal, then this message is given at the time output would have been sent
to the screen.
User Action: Use the SMG$SNAPSHOT routine to receive your output.

2-347

Messages

WINDNOTMAPPED,

the window is not mapped to a buffer

Facility: VAXTPU, VAX Text Processing Utility
Explanation: You attempted to manipulate a window that is not on the
screen.
User Action: Use the built-in procedure MAP to associate the window with a
buffer on the screen.
WINDNOTVIS,

built-in procedure cannot operate on an invisible window

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The built-in procedure that you are attempting to use (for
example, POSITION) can only use visible windows. The window that you
used as an argument is not visible because it is occluded by other windows.
User Action: Remap the window to the screen to make it visible again.
WINEXISTS,

a viewport has already been associated with the display

Facility: SMG, Screen Management Facility
Explanation: A viewport exists. That is, a viewport has already been
associated with the virtual display.
User Action: Follow these steps:
1

Use the viewport that is already associated with the virtual display.

Delete the existing viewport before you create the new viewport.

Use other viewport routines to change or move the existing viewport.

WINK,

a wink is detected on the phone line

Facility: DTK, DECtalk Facility
Explanation: A wink (a possible timeout) is detected on the phone line. The
caller may have hung up the phone.
User Action: None.
WINTRUNCFIT,

viewport truncated to fit

Facility: SMG, Screen Management Facility
Explanation: The viewport specification will not completely fit within the
virtual display. The viewport is truncated to fit within the virtual display.
User Action: None.
WKQERR,

work queue management routine error

Facility: EVL, Event Logger
Explanation: One of the work queue management routines returned an error.
This indicates a software error or a VMS system configuration problem.
User Action: Check the maximum virtual memory allowed for the process
and the timer element quota. There should be one timer element for each
sink node in use, plus two.

2-348

Messages

WLD,

invalid wildcard operation

Facility: RMS, VMS Record Management Services
Explanation: A call to one of the VMS RMS services $CREATE, $ERASE,
$ENTER, $OPEN, and $RENAME specified a wildcard in one or more
components of a file specification. No wildcards are allowed in these services.
User Action: Correct the source program. Verify that the call to VMS RMS
is coded correctly. To perform a wildcard file delete service, you must code
a loop that searches for files based on wildcard specifications and deletes the
files individually.

WLDNOTALWD,

wildcard user specs not allowed

Facility: AUTHORIZE, Authorize Utility
Explanation: Wildcard characters are not allowed in the user specification for
the command you are using.
User Action: Reenter your command without using wildcard characters.

WLK,

device currently write locked

Facility: RMS, VMS Record Management Services
Explanation: The hardware device specified for a VMS RMS operation is
write-locked for protection, and write-access is attempted.
User Action: Verify the status of the hardware device; reset the writelock switch, if necessary. Notify the system operator if the error cannot be
corrected.

Work file failed to close
Facility: EDT, EDT Editor
Explanation: EDT is unable to close its work file.
User Action: After determining the reason why EDT cannot close its work
file, correct the problem.

Work file failed to open
Facility: EDT, EDT Editor
Explanation: EDT is unable to open its work file.
User Action: After determining the reason why EDT cannot open its work
file, correct the problem.

Work file overflow
Facility: EDT, EDT Editor
Explanation: You exceeded EDT's limit on the size of its work file. The limit
is 65 ,535 blocks.
User Action: Use the CLEAR command to delete a buffer when it is no
longer needed. This precaution will also help to reduce the size of the work
file on systems with small disks.

2-349

Messages

WORK_DEV,

work file 'filespec' must be on random access local device

Facility: SORT, Sort/Merge Utility
Explanation: Work files must be specified for random access devices that are
local to the CPU on which the sort is being performed (that is, not on node
in a network). Random access devices are disk devices.
User Action: Specify the correct device.
Working
Facility: EDT, EDT Editor
Explanation: This message is displayed when the command operation
requires more than a minimum amount of time to complete. EDT is
responding to your command.
User Action: None.
WORKSTACMD,

the command 'DEBUG-command' is only supported on
workstations

Facility: DEBUG, VMS Debugger
Explanation: The debugger supports the command 'DEBUG-command'
only on workstations. This feature of the debugger is not available for your
terminal or machine.
User Action: None.
WPL,

error detected while writing prolog
Facility: RMS, VMS Record Management Services

Explanation: An 1/0 error occurred while VMS RMS is writing a file's prolog
area.
User Action: Depending on the operation, the status value (STV) field in
the FAB or RAB contains a system status code that provides additional
information about the condition. Take corrective action based on this status
code.
WPTTRACE,

nonstatic watchpoint, tracing every instruction

Facility: DEBUG, VMS Debugger
Explanation: Setting a watchpoint on a nonstatic location, such as the stack
or on a register, forces the debugger to trace every instruction that is executed.
This slows down execution of your program considerably.
User Action: If you do not want execution of your program to slow down,
then you must cancel the watchpoint.
WRIRSPMSG,

error writing system service response message

Facility: JBC, Job Controller
Explanation: The job controller encountered an error responding to a
$GETQUI, $SNDACC, $SNDJBC, or $SNDSMB system service. The
accompanying message provides additional information.
User Action: Take action based on the accompanying message.

2-350

Messages

WRISMBMBX,

error writing symbiont mailbox

Facility: JBC, Job Controller
Explanation: The job controller encountered an error communicating
with a symbiont process. The accompanying message provides additional
information.
User Action: Take action based on the accompanying message.
Write file could not be closed
Facility: EDT, EDT Editor
Explanation: EDT opened the output file and copied the text specified with
the WRITE command into that file. However, for some reason at the system
level, EDT cannot close that file.
User Action: Correct the problem indicated by the accompanying message.
Write file could not be created
Facility: EDT, EDT Editor
Explanation: EDT could not create the output file with the file specification
you supplied with the WRITE command. This error can be caused by
problems in the file name itself (either it has too many characters or an invalid
character). Other causes include problems in the directory specification, if you
used one (either the directory does not exist, you do not have access to it, or
the directory specification format is incorrect). This message could also mean
that there is a problem with the file system, such as insufficient disk space.
User Action: After determining the cause of the problem, correct it.
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.

2-351

Messages

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 back-up date of the specified file. The accompanying message
provides additional information. If other file activity is occurring on the
volume, the error is probably caused because another user deleted the file
during the back-up procedure.
User Action: If necessary, correct the condition that caused the error and
reenter the command.
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.
WRITECHECK,

write error detected during check on volume 'volume-name'

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility received an error while checking a write
operation.
User Action: The media has bad areas and should probably be discarded or
reformatted.
WRITECHECKREC,

write check error recovered on volume 'volume-name'

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility encountered an error while checking a
write on the volume, but the operation succeeded on a retry.
User Action: The file is written successfully, but the user should watch the
volume for further signs of deterioration. Discard or reformat the volume if
errors are frequent.
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.
WRITEERR,

error modifying 'file- or directory-name'

Facility: SET, SET Facility
Explanation: A problem has occurred while writing to a file or a directory.
User Action: Take corrective action based on the accompanying message.

2-352

Messages

WRITEERR,

error while writing output

Facility: ACCOUNTING, Accounting Utility
Explanation: During a VMS RMS operation, an error is encountered while
writing a file. Filespec is the file specification of the file being written.
User Action: Determine that the file is open and that you have write
privilege. If the error is reproducible, notify your system manager.
WRITEERR,

error writing 'output-filespec'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: An output file cannot be written. The message should be
accompanied by RMS messages indicating the reason for failure.
User Action: Take action based on the accompanying RMS message.
WRITEERR,

error writing 'filespec'

Facility: Shared by several facilities
Explanation: During a VMS RMS operation, an error is encountered while
writing a file.
If this error occurred during a macro assembly operation, the assembler
encountered an I/O error when writing to the output object module or listing
file; 'filespec' is the file specification of the file being written.

User Action: Determine that the file is open and that you have write
privilege. If this is a macro assembly error, retry the assembly. If the error is
reproducible, notify your system manager.
WRITE_ERR,

error writing 'filespec'

error writing 'output-filespec'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The output file cannot be written. This message should be
accompanied by a VMS RMS message indicating the reason for the error.
User Action: Follow the recovery procedure for the specified VMS RMS
message.
WRITEERR,

error writing library

Facility: LBR, Librarian Subroutine Package
Explanation: An error occurred while writing the cached disk blocks of the
library file.
User Action: If the resulting library file is corrupt, submit a Software
Performance Report.

2-353

Messages

WRITEERRREC,

write error recovered on volume 'volume-name'

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility encountered an error while writing the
volume, but the operation succeeded on a retry.
User Action: The file is written successfully, but the user should watch the
volume for further signs of deterioration. Discard or reformat the volume if
errors are frequent.
WRITE_FAILED,

an attempt to write into a memory location failed

Facility: DEBUG, VMS Debugger
Explanation: This message indicates an internal debugger error.
User Action: Submit a Software Performance Report.
WRITEFILE,

error writing event file 'file-id'

Facility: EVL, Event Logger
Explanation: An error occurred while writing an event record to a file. All
events destined for that sink will be discarded. This message displays the file
name.
User Action: Take corrective action based on the accompanying message.
WRITEHEADER,

file ('file-id') 'filename' file header write error

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility encountered an error during an attempt to
write the specified file header to the index file, [OOOOOO]INDEXF.SYS;l, on
the specified relative volume. The accompanying message provides additional
information.
User Action: If the specified file header is currently in use, the file can
no longer be accessed by the operating system. It must be deleted and
reconstructed from back-up media. If the file header is not in use, no action
is necessary because the operating system will not attempt to use the file
header.
WRITEHOME,

error writing home block, VBN 'n', RVN 'n'

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility encountered an error during an attempt
to write the home block to the specified virtual block of the index file,
[OOOOOO]INDEXF.SYS;l, on the specified relative volume. The accompanying
message provides additional information.
User Action: The volume probably can be mounted by the operating system
using one of the alternate home blocks, but the user should consider copying
the volume to fresh media.

2-354

Messages

error writing index file bitmap, VBN n RVN n

WRITEIBMAP,

1
,

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility encountered an error during an attempt to
write the index file bit map to the specified virtual block of the index file,
[OOOOOO]INDEXF.SYS;l, on the specified relative volume. The accompanying
message provides additional information.
User Action: The volume probably can be mounted by the operating system,
but you should copy the volume to fresh media or reconstruct the volume
from back-up media.

WRITE_INTO_KERNEL,

cannot write into the kernel debugger's address space

Facility: DEBUG, VMS Debugger
Explanation: This message indicates an internal debugger error.
User Action: Submit a Software Performance Report.

WRITE_INTO_KERNEL_STACK,

cannot write into the kernel debugger's stack

Facility: DEBUG, VMS Debugger
Explanation: This message indicates an internal debugger error.
User Action: Submit a Software Performance Report.

WRITEJNLACE,

error writing journal ACE for filespec' file ID 'file-id'

Facility: BACKUP, Backup Utility
Explanation: BACKUP could not write out the journal Access Control Entry
for the specified file.
User Action: Determine why the ACL could not be written. This could be
due to a corrupted ACL or some other hardware or software related error.
Correct the problem if possible and retry the BACKUP operation.

WRITELOCK,

volume is write locked

Facility: MOUNT, Mount Utility
Explanation: This informational 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.

WRITEMON,

error writing event to monitor process 'sink-name'

Facility: EVL, Event Logger
Explanation: An error occurred while writing an event record to a monitor
program. The link will be reestablished to the monitor process. This message
displays the name of the monitor program.
User Action: Take corrective action based on the accompanying message.

2-355

Messages

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.

WRITESBMAP,

error writing storage bitmap, VBN 'n', RVN 'n'

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility encountered an error during an attempt to
write the storage bit map to the specified virtual block of the storage bit
map file, [OOOOOO]BITMAP.SYS;l, on the specified relative volume. The
accompanying message provides additional information.
User Action: The volume probably can be mounted by the operating system,
but you should copy the volume to fresh media or reconstruct the volume
from back-up media.

WRITESCB,

error writing storage control block, RVN 'n'

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility encountered an error during an attempt to
write the storage control block to virtual block 1 of the storage bit map file,
[OOOOOO]BITMAP.SYS;l on the specified relative volume. The accompanying
message provides additional information.
User Action: The volume probably can be mounted by the operating system,
but the user should copy the volume to fresh media or reconstruct the volume
from back-up media.

WRITESCB,

write error on storage control block; volume is write locked

Facility: MOUNT, Mount Utility
Explanation: An I/O error occurred while the volume is being mounted; the
volume has been write-locked to protect its integrity.
User Action: Check the hardware and retry the program.

2-356

Messages

WRITLCK,

volume on 'device-name' is write locked write lock error

Facility: SYSTEM, VMS System Services
Explanation: The volume cannot be written because the hardware write-lock
switch is set on the drive or the device is software write-locked.
User Action: Release the write-lock switch and retry the program.
WRNERS,

compilation warnings in module 'module-name' file 'filename'

Facility: LINK, Linker Utility
Explanation: The specified module has compilation warnings.
User Action: Correct the module and relink.
WRONGACP,

wrong ACP for device

Facility: SYSTEM, VMS System Services
Explanation: This message is associated with a status code returned from the
IO$_MOUNT ACP QIO function. The ACP specified is the wrong one for
the file structure being mounted.
User Action: Check the ACP specified in the DCL command MOUNT
/PROCESSOR; verify what structure you are trying to mount.
WRONGDATASET,

records could not be found in the data set

Facility: VAXTPU, VAX Text Processing Utility
Explanation: An internal error occurred in the VAXTPU software.
User Action: Submit a Software Performance Report.
WRONGOWNER, file ('file-id') 'filename' inconsistent extension file header owner
UIC
Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the file owner UIC recorded in an
extension file header for the specified file did not agree with that recorded in
the primary header.
User Action: Verify corrects the extension file header.
WRONGVOL,

'date and time', Device 'device-name' contains the wrong volume.
Mount verification in progress

Facility: OPCOM, Operator Communication
Explanation: The volume in the drive is not the original volume.
User Action: Replace the original volume in the drive and cancel the mount
verification.
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.

2-357

Messages

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.
WRONUMARG , wrong number of arguments
Facility: PPL, Parallel Processing Facility
Explanation: Too many or too few arguments are specified in the call.
User Action: Recode the program using the correct number of arguments.
WRONUMARG,

wrong number of arguments

Facility: DTK, DECtalk Facility
Explanation: A DTK$ routine is called with too many or too few arguments.
User Action: Change the code to call the routine with the correct number of
arguments.
WRONUMARG,

wrong number of arguments

Facility: Shared by several facilities
Explanation: An STR$ routine is called with an incorrect number of
arguments.
User Action: Check the argument list in the call. High-level language
programmers who have not issued a call directly to an STR$ routine should
submit a Software Performance Report with supporting documentation,
including the system traceback listing.
WRONUMARG,

wrong number of arguments

Facility: SMG, Screen Management Facility
Explanation: An SMG routine is called with less than the number of required
arguments or too many arguments.
User Action: Correct the code to call the routine with the proper number of
arguments.
WRONUMARG,

wrong number of arguments

Facility: STR, String Manipulation Facility
Explanation: A String Facility entry is called with an incorrect number of
arguments.
User Action: A user who calls the String Facility directly should check the
argument list in the call. High-level language programmers who have not
issued a call directly to a String Facility routine should submit a Software
Performance Report with supporting documentation, including the system
traceback listing.

2-358

Messages

WRTEVT,

error writing events to sink node receiver

Facility: EVL, Event Logger
Explanation: An error occurred while writing information over a logical link
to an event receiver. The link will be reopened and the operation will be
retried. This error may be due to a VMS system or network configuration
problem.
User Action: Take corrective action based on the accompanying message.
WRTFIL,

updating image file 'filespec'

Facility: PATCH, Patch Utility
Explanation: The specified image file is updated to include the previous
patch.
User Action: None.
WRTHOMBLK, 1/0 error writing home block
Facility: MOUNT, Mount Utility
Explanation: An 1/0 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

ACP attempted to write an invalid file header

2-359

Messages

WRTPGSBAK,

write pages back-inconsistent database

Facility: BUGCHECK, System Bugcheck
Explanation: The VMS 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, 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 on 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

working set list page count error

2-360

Messages

WSLVANVAL,

working set list virtual adr has nonvalid PTE

working set list entry does not match VA

working set size less than pages in use

invalid XAB or XAB not accessible at location
Facility: RMS, VMS Record Management Services
Explanation: The XAB specified in the XAB field of the FAB, or in the NXT
field of another XAB, pointed to an XAB that either is not writeable by the
caller or contains an invalid block length field.
User Action: The status value (STV) field of the FAB provides the address
of the XAB in error. Verify that the call to the VMS RMS service is coded
correctly.

2-361

Messages

XNF,

required XAB not found
Facility: RMS, VMS Record Management Services
Explanation: A VMS RMS request required an XAB which is not specified.
For example, the ROP option, ETO is specified, but no EABTRM is supplied.
User Action: Verify that the call to the VMS RMS service is coded correctly.

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

yes
Facility: VAXTPU, VAX Text Processing Utility
Explanation: Prototype affirmative response.
User Action: None.

YESNO,

please enter YES or NO.

Facility: VMSINSTAL, Install Procedures
Explanation: VMSINSTAL asked a question that must be answered YES or
NO.
User Action: Answer the question again, specifying YES or NO. You may
abbreviate these answers as Y or N, respectively.
ZEROLEN,

zero length record encountered, entry 'n' skipped

Facility: ERF, Error Log Utility
Explanation: A null entry was encountered.
User Action: Submit a Software Performance Report.

2-362

Messages

ZEROP AGE,

Zero page table entry from swap map

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 on the BACKUP command
that produces the save set included with the SPR.)

2-363

Reader's Comments

VMS System Messages
and Recovery Procedures
Reference Manual: Part II
AA-LA 18A-TE

Please use this postage-paid form to comment on this manual. If you require a written reply to a software
problem and are eligible to receive one under Software Performance Report (SPR) service, submit your
comments on an SPR form.
Thank you for your assistance.

I rate this manual's:
Accuracy (software 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

Good

Fair

Poor

0
0
0
0
0
0
0
0

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:

I am using Version _ _ _ of the software this manual describes.

Name/Title

Dept.

Company

Date

Mailing Address
Phone

· - - Do Not Tear - Fold Here and Tape

-------------------~lllr--------------
No Postage

mnmnamo™

~:~=i~=~y
in the
United States

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

DIGIT AL EQUIPMENT CORPORATION
Corporate User Publications-Spit Brook
ZK01-3/J35 110 SPIT BROOK ROAD
NASHUA, NH 03062-9987

111 ..... 11.11 .... 11 .... 1.11.1 •• 1.1 .. 1•• 1.1 ... 1.11 •• 1
- - Do Not Tear - Fold H e r e - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - !
I
i

Reader's Comments

VMS System Messages
and Recovery Procedures
Reference Manual: Part II
AA-LA 18A-TE

Excellent

Good

Fair

Poor

0
0
0
0
0
0
0
0

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:

I am using Version ___ of the software this manual describes.

Name/Title

Dept.
Date

Company
Mailing Address
Phone

--;;~;;~:d

Here ~d Ta~ ------------------~lllf-------~~~;~--in the
United States

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

DIGIT AL EQUIPMENT CORPORATION
Corporate User Publications-Spit Brook
ZK01-3/J35 110 SPIT BROOK ROAD
NASHUA, NH 03062-9987

111 ..... 11.11 .... 11 .... 1.11.1 .. 1.1 .. 1•• 1.1 ••• 1.11 .. 1
-- Do Not Tear - Fold Here - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -