Digital PDFs

XX-190EF-31

April 1986

632 pages

Original

30MB

Document:	VAX VMS System Messages and P Recovery Procedures Reference Manual
Order Number:	XX-190EF-31
Revision:
Pages:	632
Original Filename:	https://archive.org/download/stx_AA-Z800-B-TE_VMS_4.4_VAX_VMS_System_Messages_and_Recovery_Procedures_Reference_M/AA-Z800-B-TE_VMS_4.4_VAX_VMS_System_Messages_and_Recovery_Procedures_Reference_Manual_Apr86.pdf

OCR Text

VAX/VMS
System Messages
and
Recovery Procedures
Reference Manual

VAX/VMS
System Messages and
Recovery Procedures
Reference Manual
Order Number: AA-Z800B-TE

April 1986
This manual lists messages produced by the VAX/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.0.

Software Version:

VAX/VMS Version 4.4

digital equipment corporation
maynard, massachusetts

April 1986

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 ©1986 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
DECUS
DECwriter

DIBOL
EduSystem
IAS
MASSBUS
PDP
PDT
RSTS
RSX

UNIBUS
VAX
VAXcluster
VMS
VT

□QSDEED
ZK-2828

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 (SDC), Digital Equipment
Corporation, Westminster, Massachusetts 01473.
This document was prepared using an in-house documentation production system. All page
composition and make-up was performed by T^X, the typesetting system developed by
Donald E. Knuth at Stanford University. T\zX is a registered trademark of the American Mathematical
Society.

Contents
PREFACE

SECTION 1

INTRODUCTION

1.1 MESSAGE DISPLAY
1.1.1
Retrieving an Error Message _
1.1.2
Exception Conditions _

1-1
1-1
1-2

1.2 FORMAT OF SYSTEM MESSAGES
1.2.1
Messages Without Idents _
1.2.2
Severity Levels _
1.2.3
Linked Messages _

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

1.3 RECOVERY PROCEDURES
1.3.1
Recovering from Command Entry Errors _
1.3.2
Unavailable Resources _
1.3.3
Recovering from Programming Errors _
1.3.4
Reporting System Software or Hardware Errors _

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

1.4 RETRIEVING IDENT

1-6

SECTION 2 MESSAGES

2-1

Preface
Intended Audience
This manual is intended for all users of the VAX/VMS operating system,
including programmers and system managers.

Structure of This Document
This manual consists of two chapters.
Chapter 1 describes the format of the messages and explains how to locate a
message in this manual.
Chapter 2 lists the messages alphabetically by message code. Each message is
accompanied by explanatory text and, where applicable, a suggested recovery
action.

Associated Documents
This manual documents messages for the facilities listed below. The list
includes an associated document or documents for each facility. You can refer
to the associated documents for detailed information about a facility.
Facility
Abbreviation

Facility Name

Document

ACCOUNTING

Accounting Utility

VAX/VMS
Accounting
Utility Reference
Manual

AUTHORIZE

Authorize Utility

VAX/VMS
Authorize Utility
Reference Manual

BACKUP

Backup Utility

VAX/VMS
Backup Utility
Reference Manual

BAD

Bad Block Locator Utility

VAX/VMS Bad
Block Locator
Utility Reference
Manual

BOOT

System Bootstrap Facility

VAX/VMS
System
Manager's
Reference Manual
Guide to
VAX/VMS
Software
Installation

Preface

Facility
Abbreviation

Facility Name

Document

Guide to
VAXclusters
CDU

Command Definition Utility

VAX/VMS
Command
Definition Utility
Reference Manual

CLI

Command Language Interpreter (DCL)

Guide to
Using DCL
and Command
Procedures on
VAX/VMS

CONVERT

Convert Utility

VAX/VMS
Convert and
Con vert/Reclaim
Utility Reference
Manual

CONVERT

Convert/Reclaim Utility

VAX/VMS
Convert and
Con vert/Reclaim
Utility Reference
Manual

CREF

Cross-Reference Utility

Guide to
Programming
on VAX/VMS

DCL

DIGITAL Command Language

VAX/VMS DCL
Dictionary

DEBUG

VAX Debugger

VAX/VMS
Debugger
Reference Manual

DIFF

DIFFERENCES Command

VAX/VMS DCL
Dictionary

DISKQUOTA

Diskquota Utility

VAX/VMS Disk
Quota Utility
Reference Manual

DISM

DISMOUNT Command

VAX/VMS DCL
Dictionary

DUMP

File Dump Utility

VAX/VMS DCL
Dictionary

EDT

EDT Editor

VAX EDT
Reference Manual

ERF

ANALYZE/Error Log Utility

VAX/VMS
Error Log Utility
Reference Manual

EVL

Event Logger

VAX/VMS
Networking
Manual

Preface

Facility
Abbreviation

Facility Name

Document

EXCHANGE

Exchange Utility

VAX/VMS
Exchange Utility
Reference Manual

FDL

Create/FDL Utility

VAX/VMS
File Definition
Language Facility
Reference Manual

FDL

Edit/FDL Utility

VAX/VMS
File Definition
Language Facility
Reference Manual

INIT

INITIALIZE VOLUME Command

VAX/VMS DCL
Dictionary

INSTALL

Install Utility

VAX/VMS Install
Utility Reference
Manual

JBC

Job Controller

VAX/VMS
System Services
Reference Manual

LATCP

Local Area Transport Control Program

VAX/VMS LAT
Control Program
Reference Manual

LBR

Librarian

VAX/VMS
Librarian
Reference Manual

LIB

RTL General Procedures

VAX/VMS
Run-Time
Library Routines
Reference Manual

LIBRAR

LIBRARY Command

VAX/VMS
Librarian
Reference Manual

LINK

VAX Linker

VAX/VMS Linker
Reference Manual

VAX/VMS DCL
Dictionary
VAX/VMS
System
Manager's
Reference Manual

MACRO

VAX Macro Assembler

VAX MACRO
and Instruction
Set Reference
Volume

MAIL

Personal Mail Utility

VAX/VMS Mail
Utility Reference
Manual

Preface

Facility
Abbreviation

Facility Name

Document

MESSAGE

Message Utility

VAX/VMS
Message Utility
Reference Manual

MONITOR

Monitor Utility

VAX/VMS
Monitor Utility
Reference Manual

MOUNT

MOUNT Command

VAX/VMS DCL
Dictionary

MTH

RTL Math Procedures

VAX/VMS
Run-Time
Library Routines
Reference Manual

NCP

Network Control Program

VAX/VMS
Networking
Manual

NET

DECnet Test Program Protocol

VAX/VMS
Networking
Manual

OPCOM

Operator Communication

VAX/VMS
System
Manager's
Reference Manual

OTS

Language Independent RTL
Support Procedures

VAX/VMS
Run-Time
Library Routines
Reference Manual

PATCH

VAX Image File Patch

VAX/VMS Patch
Utility Reference
Manual

PRINT Command

VAX/VMS DCL
Dictionary

PSI

VAX Packetnet System Interface

VAX/VMS
Networking
Manual

PSM

Print Symbiont

VAX/VMS
Utility Routines
Reference Manual

REM

Set Host Facility

VAX/VMS DCL
Dictionary

RENAME

RENAME Command

VAX/VMS DCL
Dictionary

RMS

VAX RMS Services

VAX Record
Management
Services
Reference Manual

Preface

Facility
Abbreviation

Facility Name

Document

RUNOFF

DIGITAL Standard Runoff Utility

VAX DIGITAL
Standard Runoff
(DSR) Reference
Manual

SDA

System Dump Analyzer

VAX/VMS
System Dump
Analyzer
Reference Manual

SEARCH Command

VAX/VMS DCL
Dictionary

SHR

SET Facility Shared Messages

VAX/VMS DCL
Dictionary

SMB

Symbiont Services

VAX/VMS
Utility Routines
Reference Manual

SMG

RTL Screen Management Procedures

VAX/VMS
Run-Time
Library Routines
Reference Manual

SORT

VAX SORT/MERGE Utility

VAX/VMS Sort
/Merge Utility
Reference Manual

STR

RTL String Procedures

VAX/VMS
Run-Time
Library Routines
Reference Manual

SUBMIT

SUBMIT Command

VAX/VMS DCL
Dictionary

SUMSLP

SUMSLP Batch Editing Utility

VAX/VMS
SUMSLP Utility
Reference Manual

SYSBOOT

System Bootstrap Facility

VAX/VMS
System
Manager's
Reference Manual
Guide to
VAX/VMS
Software
Installation
Guide to
VAXclusters

SYSGEN

System Generation Utility

VAX/VMS
System
Generation Utility
Reference Manual

Preface

Facility
Abbreviation

Facility Name

Document
VAX/VMS
System
Manager's
Reference Manual

SYSINIT

System Initialization

VAX/VMS
System
Manager's
Reference Manual
Guide to
VAX/VMS
Software
Installation

SYSTEM

VAX/VMS System Services

VAX/VMS
System Services
Reference Manual

UETP

User Environment Test Package

Guide to
VAX/VMS
Software
Installation

VAXTPU

VAX Text Processing Utility

VAX Text
Processing Utility
Reference Manual

VERIFY

Verify Utility

VAX/VMS Verify
Utility Reference
Manual

Conventions Used in This Document
Convention

Meaning

[ret]

A symbol with a one- to six-character
abbreviation indicates that you press a key
on the terminal, for example, I ret| .

ICTRL/xl

The phrase CTRL/x indicates that you
must press the key labeled CTRL while you
simultaneously press another key, for example,
CTRL/C, CTRL/Y, CTRL/O.

$ SHOW TIME
05-JUN-1985 11:55:22

Command examples show all output lines or
prompting characters that the system prints
or displays in black letters.

$ TYPE MYFILE.DAT

Vertical series of periods, or ellipsis, mean
either that not all the data that the system
would display in response to the particular
command is shown or that not all the data a
user would enter is shown.

Preface

Convention

Meaning

file-spec,...

Horizontal ellipsis indicates that additional
parameters, values, or information can be
entered.

[logical-name]

Square brackets indicate that the enclosed item
is optional. (Square 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.

Introduction

1.1

Message Display
VAX/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$OUTPUT. 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$OUTPUT, 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$OUTPUT 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.1.1

Retrieving an Error Message
The error message associated with an error code can be retrieved by issuing
the $EXIT command in a command procedure. Create the file ERROR.COM
with the line:
$EXIT 7.X'P1

The last error code is always stored in DCL symbol $STATUS. You can
display this error code, which is an 8-digit hexadecimal number, by entering
the following DCL command:
$ SHOW SYMBOL ISTATUS

Then, to display the message, type the following command using the value
stored in the DCL symbol $STATUS:
$ @ERROR number

i-i

Introduction

1.1.2

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 VAX/VMS Run-Time Library Routines Reference Manual for a more detailed
discussion of condition handling.

1.2

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

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

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

Meaning

Success

Information

Warning

Error

Fatal, or severe error

Severity levels are described in detail in Section 1.2.2.

IDENT
An abbreviation of the message text; the message descriptions in Section 2
are alphabetized by this abbreviation.

TEXT
The explanation of the message.

[- F ACILITY- L-1 DENT,TEXT]
The next message.
An example of this type of message is shown below where LINK is the
facility name, E is the severity level, FATALERROR is the ident, and "Fatal
error message issued" is the message text:
XLINK-E-FATALERROR, Fatal error message issued

1-2

Introduction

1.2.1

Messages Without Idents
The following facilities generate messages without idents:
•

System Bootstrap Utility (BOOT or SYSBOOT)

•

System Initialization (SYSINIT)

Such messages are alphabetized by facility name as shown in the example
below:
B00T--F--I/0 error reading boot file

In this message BOOT is the facility name, F is the severity level, and "I/O
error reading boot file" is the message text.
Three facilities display their messages without idents and facility names as
follows:
•

EDT Editor

•

DIGITAL Standard Runoff

•

Diskquota Utility

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

The entry for this message can be found under "Could" in Section 2 of this
manual.

1.2.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-3

Introduction

1.2.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 VAX Record Management
Services (VAX 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 VAX 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.3

Recovery Procedures
Error messages generally occur for the following reasons:

1.3.1

•

A command was entered incorrectly; it contained 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.

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 was 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 VAX/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-4

•

A device name was not terminated with a colon.

•

A directory name was not enclosed in brackets.

•

A file name has more than thirty-nine characters.

•

A file type has more than thirty-nine characters.

•

An alphabetic version number was specified.

Introduction

•

A node name was included and had characters other than numerics or
alphabetics.

•

A connection to the target node could not be made.

1.3.2 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.3.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:
•

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 VAX/VMS Debugger can help you discover and correct programming
errors. For details on how to use the debugger, refer to the VAX/VMS
Debugger Reference Manual.

1.3.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 VAX/VMS System Manager's Reference Manual 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—5

Introduction

1.4

Retrieving Ident
Most of the messages in this manual are alphabetized according to the
IDENT portion. If you have disabled the IDENT with the SET MESSAGE
/NOIDENTIFICATION command, and if need the IDENT to reference a
message, you can create a command procedure to display the last message
received with its IDENT. The following steps show you how to create this
command procedure:
1

Use your editor to create a file called TELLME.COM.

2 Enter the following lines of text:
$ THE_MESSAGE_WAS == F$MESSAGE($STATUS)
$ SHOW SYMBOL THE.MESSAGE.WAS

3 Exit from the editor.
You can run this command procedure after you receive a message by the
command:
(8TELLME

The last message received will be displayed with its FACILITY, SEVERITY
LEVEL, and IDENT. Use the IDENT to find the message in this manual for
further explanation.
The following example shows the DCL command LINK used with an
incorrect file name:

EXAMPLES
□

$ 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.
0

$ SET MESSAGE/NOIDENTIFICATION

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

$ 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.
Q

$ (DTELLME
THE.MESSAGE.WAS = "'/.LINK-F-OPENIN, error opening !AS as input"
$ SHOW SYMBOL THE.MESSAGE.WAS
THE.MESSAGE.WAS = '"/.LINK-F-OPENIN, ERROR OPENING"

When the TELLME command procedure is executed, the message line is
displayed.

1—6

Messages

'.' required
Facility: EDT, EDT Editor
Explanation: The command required a period (.) or whatever other character
is enclosed in the quotation marks.
User Action: Reenter the command including the required special character.
'AS' required
Facility: EDT, EDT Editor
Explanation: You omitted the word AS from the syntax in the DEFINE KEY
command.
User Action: Reenter the command specifying the correct syntax.
AAA,

'file-spec'

Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: This message should never be displayed.
User Action: Submit a Software Performance Report.
ABEND,

'string' aborted

Facility: Shared by several facilities
Explanation: A program phase has terminated prematurely.
User Action: None.
ABENDD,

'string' aborted at 'date'

Facility: Shared by several facilities
Explanation: A program phase aborted prematurely.
User Action: None.
ABENDT,

'string' aborted at 'time'

Facility: Shared by several facilities
Explanation: A program phase aborted prematurely.
User Action: None.

2-1

ABFNAM,

ambiguous lexical function name - supply more characters

Facility: CLI, Command Language Interpreter (DCL)
Explanation: Too few characters were used to truncate a lexical function
name to make the function name unique.
User Action: Reenter the command; specify at least four characters of the
function name.
ABKEYW,

ambiguous qualifier or keyword - supply more characters

Facility: CLI, Command Language Interpreter (DCL)
Explanation: Too few characters were used to truncate a keyword or qualifier
name to make the keyword or qualifier name unique.
User Action: The rejected portion of the command is displayed between
backslashes (\ \). Reenter the command; specify at least four characters of the
keyword or qualifier name.
ABKW,

ambiguous key word on line

Facility: FDL, Edit/FDL Utility and FDL, Create/FDL Utility
Explanation: You have used an ambiguous abbreviation for an attribute
keyword.
User Action: Enter a more specific abbreviation.
ABORT,

'testname7 aborted at 'date7 time7

Facility: UETP, User Environment Test Package
Explanation: A test ended abnormally.
User Action: Investigate the reason for the abnormal termination of the test.
Take corrective action based on the accompanying message.
ABORT,

abort

Facility: SYSTEM, VAX/VMS System Services
Explanation: An attempted operation was aborted by the $CANCEL system
service.
•

An I/O request was canceled before it was completed.

•

Following a network request, this status indicates that a logical link was
disconnected.

•

A fatal hardware error occurred.

User Action: The operating system does not normally display this message.
User programs should be coded to detect and respond to the status return.
If this message is associated with a status code returned by a request to
a DMP11 interface, examine the device-dependent longword in the IOSB to
determine if the controller is dead; (The controller is dead if the XM$V_ERR_
FATAL bit is set.) If the controller is dead, restart the controller. Next, check
if the tributary is dead. (The tributary is dead if the SM$V_STS_ACTIVE bit
is clear.) If the tributary is dead, restart the tributary.

Messages

ABORT,

abort

Facility: SYSGEN, System Generation Utility
Explanation: This message is issued with other messages to indicate that the
action is aborted.
User Action: Take corrective action based on the accompanying messages.
ABORT,

operator requested abort on fatal error

Facility: BACKUP, Backup Utility
Explanation: In response to a BACKUP-I-SPECIFY prompt, the user or
operator entered the QUIT option; the Backup Utility terminates.
User Action: None.
ABORTC,

'testname' to abort this test, type CTRL/C

Facility: UETP, User Environment Test Package
Explanation: The image displaying this message responds to CTRL/C by
terminating gracefully (deassigning all logical names and deleting all files)
and passing control to the command language interpreter. You cannot restart
the image after pressing CTRL/C. Use CTRL/Y to temporarily interrupt an
image.
User Action: None.
Aborted by CTRL/C
Facility: EDT, EDT Editor
Explanation: You pressed CTRL/C after entering a command in keypad
change-mode. Pressing CTRL/C causes all text to disappear from the screen.
User Action: If the text is not restored to the screen, press RETURN.
ABPRIKW,

ambiguous primary key word on line n

Facility: FDL, Create/FDL Utility
Explanation: You have used an ambiguous abbreviation for an attribute
keyword.
User Action: Provide a more specific abbreviation.
ABSENT,

entity or value absent from command string

Facility: CLI, Command Language Interpreter (DCL)
Explanation: This status is returned by the CLI$PRESENT CLI interface
routine. This indicates that the entity value has not been specified in the
command line.
User Action: None.

2-3

Messages

ABSYMD,

abbreviated symbol definition conflict - rename symbol

Facility: CLI, Command Language Interpreter (DCL)
Explanation: A new abbreviated symbol is ambiguous with an existing
symbol. The new symbol is not entered.
User Action: Display the current symbols and adjust the abbreviation of the
ambiguous symbol.
ABVERB,

ambiguous command verb - supply more characters

Facility: CLI, Command Language Interpreter (DCL)
Explanation: Too few characters were used to truncate a command name to
make the command name unique.
User Action: Reenter the command; specify at least four characters of the
command name.
ACC,

ACP file access failed
Facility: RMS, VAX Record Management Services
Explanation: An error occurred during an attempt to open a file. This
message is associated with a status code returned from a file system ACP QIO
request made by VAX RMS.
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.

ACCADDCOM,

access violation in address computation for xxx

Facility: DEBUG, VAX/VMS Debugger
Explanation: The address computation for the specified variable resulted in
an access violation. This normally means that a register value or a descriptor
needed in the address computation is uninitialized or corrupted.
User Action: If the necessary register or descriptor is not yet initialized, the
variable is not available at this point in the code. If the register or descriptor
is corrupted, the cause of this error should be located and corrected.
ACCCIR,

access control specified with loop circuit

Facility: NCP, Network Control Program
Explanation: Access control with a loop command may be specified only
with a loop node or a loop executor command, not with a loop circuit
command.
User Action: Specify access control with a loop node or a loop executor
command.
ACCDISERR,

accounting disabled due to file errors

Facility: JBC, Job Controller
Explanation: Accounting has been disabled because of previously reported
errors in the accounting file.
User Action: Correct the condition that caused the errors, and reenable
accounting with the SET ACCOUNTING/ENABLE command.

2-4

Messages

ACCERR,

non-blank accessibility field in volume labels on 'device-name'

Facility: MOUNT, MOUNT Command
Explanation: The accessibility field on the magnetic tape, which is mounted
on the device indicated, has a nonblank accessibility field. This field denies
access to the tape.
User Action: Mount the magnetic tape with the
/OVERRIDE=ACCESSIBILITY qualifier. (The user must be the owner of
the volume or have VOLPRO privilege.)
ACCESSFAIL,

access has failed for 'devicename'

Facility: EXCHANGE, Exchange Utility
Explanation: The EXCHANGE utility was unable to access the named
device. A second error message should follow the ACCESSFAIL message,
giving more information.
User Action: Retry the command, after taking corrective action suggested by
the second line of the message.
ACCLIN,

access control specified with loop line

Facility: NCP, Network Control Program
Explanation: Access control information may be specified only with the
LOOP NODE or LOOP EXECUTOR commands, and not with the LOOP
LINE command.
User Action: Reenter the command specifying the correct command.
ACCONFLICT,

'file-name' is open for write by another user

Facility: BACKUP, Backup Utility
Explanation: The Backup Utility opened the specified file while another
user was writing the file because the /IGNORE=INTERLOCK qualifier was
specified in the DCL command BACKUP.
User Action: Note that the saved copy of the file may be inconsistent.
ACCONFLICT,

file access conflict

Facility: SYSTEM, VAX/VMS System Services
Explanation: An attempt to access a file failed because the type of access
requested conflicted with the current file access.
User Action: Two possible actions include:
•

Establishing who has the file open and waiting until it is closed.

•

Checking for a programming error. Begin debugging procedures to verify
the type of problem and to find a method to correct it.

2-5

ACCQUOTA,

ACCOUNT had inadequate quota at remote node

Facility: SYSTEM, VAX/VMS System Services
Explanation: This error message is associated with a status code returned
from a system service request. An attempt was made to initiate a DECnetVAX logical link connection. The target object is already using its quota of
logical links or some other resource.
User Action: This condition is not usually permanent. Try initiating the
connection later. Consult the VAX/VMS Networking Manual for additional
information.
ACCTACTIVE,

PSI accounting to file 'filename7

Facility: PSI, VAX Packetnet System Interface
Explanation: A user has asked for status information and VAX PSI
accounting is in progress.
User Action: None.
ACCTCLERR,

error closing PSI accounting file 'filename'

Facility: PSI, VAX Packetnet System Interface
Explanation: An error occurred during the closing of VAX PSI Accounting
file. This message is caused by errors that occur when the VAX PSI
Accounting file is accessed.
User Action: An accompanying RMS message provides further explanation.
ACCTCLOSE,

PSI accounting file 'filename' closed

Facility: PSI, VAX Packetnet System Interface
Explanation: A user has instructed VAX PSI to close the accounting file.
User Action: None.
ACCTCREAT,

error creating PSI accounting file 'filename'

Facility: PSI, VAX Packetnet System Interface
Explanation: An error occurred when the VAX PSI Accounting file was
created. This message is caused by errors that occur when the VAX PSI
Accounting file is accessed.
User Action: An accompanying RMS message provides further explanation.
ACCTDISABL,

PSI accounting disabled

Facility: PSI, VAX Packetnet System Interface
Explanation: VAX PSI Accounting is disabled; accounting is permanently
turned off until VAX PSI is reloaded.
User Action: Reload VAX PSI.

Messages

ACCTERROR,

error writing to PSI accounting file 'filename7

Facility: PSI, VAX Packetnet System Interface
Explanation: An error occurred in writing a record to the VAX PSI
Accounting file. This message is caused by errors accessing the VAX PSI
accounting file.
User Action: An accompanying RMS message provides further explanation.
ACCTINACT,

PSI accounting off

Facility: PSI, VAX Packetnet System Interface
Explanation: A user has asked for status information and VAX PSI
accounting is off.
User Action: None.
ACCTINITFAIL,

PSI accounting initialization failed

Facility: PSI, VAX Packetnet System Interface
Explanation: VAX PSI Accounting could not initialize (mailbox creation
failed).
User Action: This message is followed by another message giving the reason
for the failure.
ACCTOFF,

PSI accounting has been turned off

Facility: PSI, VAX Packetnet System Interface
Explanation: VAX PSI Accounting has been turned off by the user or VAX
PSI.
User Action: VAX PSI Accounting can be turned on again by the user.
ACCTOPEN,

PSI accounting file 'filename' opened

Facility: PSI, VAX Packetnet System Interface
Explanation: A user has instructed VAX PSI to open a new accounting file.
User Action: None.
ACCVIO,

access violation, reason mask = xx, virtual address = location,
PC = location, PSL = xxxxxxxx

Facility: SYSTEM, VAX/VMS System Services
Explanation: An image attempted to read from or write to a memory location
that is protected from the current mode. This message indicates an exception
condition and is followed by a register and stack dump to help locate the
error. The reason mask is a longword whose lowest three bits, if set, indicate
that the instruction caused a length violation (bit 0), referenced the process
page table (bit 1), and attempted a read/modify operation (bit 2).
This message is also displayed when an attempt has been made to make the
user stack larger than the user's virtual address space permits. For example,
the automatic user stack expansion algorithm reports an access violation with
the following two conditions which should serve as hints that automatic
expansion has failed.

2-7

Messages

•

The reason mask has the low order bit set. This indicates a memory
reference which is not described in any page table.

•

The relatively small PI address space virtual address referenced. In this
case 79F5396C.

User Action: Examine the PC and virtual address displayed in the message.
Check the program listing to verify that instruction operands or procedure call
arguments are correct.
If this message was displayed because of insufficient virtual memory for
automatic user stack expansion, reduce the user stack requirements of the
image or increase the virtual address space available to the process in which
the image is executed.
ACLUPDATED,

ACL successfully updated

Facility: ACLEDIT, Access Control List Editor
Explanation: The object's ACL has been successfully updated.
User Action: None.
ACNTEXC,

you are at maximum allowed processes for your account name

Facility: LOGIN, Login Processor
Explanation: You attempted to log in when the maximum number of
processes logged in to your account had already logged in.
User Action: Wait until someone else logs off or log off another process.
ACPMBFAIL,

ACP failure to read mailbox

ACP file name is too long

Facility: MOUNT, MOUNT Command
Explanation: The file name specified for an ACP image has more than nine
characters.
User Action: Reenter the command and specify the correct ACP file name.

2-8

Messages

ACPRECURS,

Attempted recursion in ACP secondary operation

an error was returned from a NETACP SHOW function

Facility: EVL, Event Logger
Explanation: A network SHOW function used to obtain database information
from the network returned an unexpected error. This could be caused by a
software error.
User Action: Submit a Software Performance Report.
ACPTIME,

ACP does not respond

Facility: MOUNT, MOUNT Command
Explanation: The ACP that was requested in the DCL command MOUNT
cannot be initialized. Either the specified image is not an ACP or a system
error has occurred.
User Action: Verify that the image is an ACP. If it is an ACP, consult with
your system manager to determine what events in the system might prevent
the ACP from starting.
ACPUNSTAK,

Attempted unstack in ACP primary context

2-9

ACPVAFAIL,

ACP failure to return virtual address space

MTAACP's virtual address space is full

Facility: SYSTEM, VAX/VMS System Services
Explanation: Additional volumes cannot be serviced by the ACP because
it does not have enough memory to allocate control information for a new
volume.
User Action: Start a different ACP using the /PROCESSOR qualifier with the
DCL command MOUNT.
ACS,

error in access control string
Facility: RMS, VAX Record Management Services
Explanation: The access control string in the file specification was invalid.
Either too many characters or too many subfields were specified.
User Action: Correct the syntax of the access control string and retry the
operation. Limit the number of characters to 42 (not including quotation
marks) and the number of subfields to 3.

ACSIGN,

access control string ignored

Facility: REM, Set Host Facility
Explanation: The access control string specified on a SET HOST command
was ignored by the remote terminal facility.
User Action: None.
ACT,

file activity precludes operation
Facility: RMS, VAX Record Management Services
Explanation: An I/O operation was attempted while other file I/O activity
was in progress.
User Action: Note the condition. If necessary, modify the source program
to detect and respond to the condition. Correct the program logic to avoid
conflicting concurrent operations.

ACTIVEBCB,

buffer active during reel switch

Facility: BACKUP, Backup Utility
Explanation: A software error occurred in the Backup Utility.
User Action: Submit a Software Performance Report.

Messages

ADDERR,

unable to add user record

Facility: AUTHORIZE, Authorize Utility
Explanation: This message is issued with other messages.
User Action: Take corrective action based on the accompanying messages.
ADDFIL,

error adding file 'file-name' to job

Facility: PRINT, Print Command and SUBMIT, SUBMIT Command
Explanation: The system encountered an error adding the specified file
to a batch or print job. The accompanying message provides additional
information.
User Action: Correct the error and reenter the command.
ADDMSG,

user record successfully added

Facility: AUTHORIZE, Authorize Utility
Explanation: This message is informational.
User Action: No user action is required.
ADDQUOTA,

error adding quota record for ['uic']

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

address range covers more than one module

Facility: DEBUG, VAX/VMS Debugger
Explanation: The address range specified in a DEBUG command EXAMINE
/SOURCE covers more than a single module. This is not allowed. The start
address xxx is in module modi and the end address yyy is in module mod2.
User Action: Reenter the command with a valid address range.
ADRLSTSYNX,

address list syntax error

Facility: MACRO, VAX Macro Assembler
Explanation: The address list in the .ADDRESS directive contains a syntax
error.
User Action: Correct the syntax.

2-11

Messages

ADRWRTDAT,

address data in shareable writeable section in psect 'psect-name7
offset 'number7 in module 'module-name7 file 'file-name7

Facility: LINK, VAX Linker
Explanation: The object language equivalent of the VAX MACRO .ADDRESS
directive was encountered in a COMMON section, such as those found in
VAX BASIC, VAX FORTRAN, or VAX PL/I. This would cause the section to
be nonshareable, so the linker bases the image.
User Action: Remove the address data from the command and initialize it at
run time.
Advance past bottom of buffer
Facility: EDT, EDT Editor
Explanation: You attempted to move the cursor past the end of the buffer
([EOB]).
User Action: Press the up arrow key to move the cursor above the [EOB]
mark.
AGAIN,

another data analysis pass is needed

Facility: DCX, Disk Compression Utility
Explanation: This status, returned by DCX$MAKE_MAP, indicates that DCX
must see all data records again before it can compute a map.
User Action: The application program should again present data to DCX for
analysis.
AID,

invalid area ID = 'nnn7
Facility: RMS, VAX Record Management Services
Explanation: An allocation XAB for a $CREATE, SDISPLAY, $EXTEND or
$OPEN operation contains an invalid area identification number field.
User Action: The status value (STV) field of the FAB provides the area
identification value in error. Verify that the call to the VAX RMS service was
coded correctly.

ALCPHD,

Allocate process header error

2-12

Messages

ALCSMBCLR,

ACP tried to allocate space already allocated

'device-name' contains an alignment cartridge

Facility: BAD, Bad Block Locator Utility
Explanation: The device specified contains an alignment cartridge.
User Action: Replace the cartridge with a data cartridge and reinvoke the
utility.
ALIGNXCEED,

alignment exceeds PSECT alignment

Facility: MACRO, VAX Macro Assembler
Explanation: The .ALIGN directive specified an alignment larger than the
program section alignment. For example, the .PSECT directive specified
byte alignment (the default) and the .ALIGN directive specified a longword
alignment or a .PSECT directive specified an invalid alignment.
User Action: Correct the conflicting alignments. The .PSECT directive should
specify the largest alignment required by the program section.
ALLOC,

'device' allocated

Facility: CLI, Command Language Interpreter (DCL)
Explanation: The specified device was allocated.
User Action: None.
ALLOCCLR,

blocks incorrectly marked allocated 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 marked allocated in the storage bit map but
were not allocated to a file.
User Action: None. The specified blocks were marked free in the storage bit
map. The /CONFIRM qualifier is ignored in this operation.
ALLOCEXT,

blocks allocated to lost extension file header 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 a lost extension file header.
User Action: None. The specified blocks were marked free in the storage bit
map. The /CONFIRM qualifier is ignored in this action.

2-13

ALLOCFAIL,

file structure allocation failure for 'device'

Facility: BACKUP, Backup Utility
Explanation: Insufficient contiguous space was available on the specified
volume to allocate the files necessary to initialize the volume as a Files-11
structured volume. This error may be caused by an excessive number of bad
blocks.
User Action: Retry the operation using another volume.
ALLOCFAIL,

index file allocation failure

Facility: INIT, INITIALIZE Volume Command
Explanation: The DCL command INITIALIZE failed to allocate space on the
volume for the index file. This message usually indicates that too much space
was requested for file headers.
User Action: Reenter the command; specify a smaller value for the
/HEADERS qualifier.
ALLOCMEM,

error allocating virtual memory

Facility: BACKUP, Backup Utility and VERIFY, Verify Utility
Explanation: Either the Backup Utility or the Verify 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. You may need to increase the page file quota of the account or the
SYSGEN parameter VIRTU ALP AGECNT.
ALLOCMEM,

error allocating virtual memory

Facility: JBC, Job Controller
Explanation: The job controller encountered an error allocating virtual
memory. The accompanying message provides additional information.
User Action: Take action based on the accompanying message.
ALLOCSET,

blocks incorrectly marked free 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 marked free in the storage bit map but were
allocated to a file.
User Action: None. The specified blocks are marked allocated in the storage
bit map. The /CONFIRM qualifier is ignored in this action.
ALN,

alignment options error for area id = 'id'
Facility: RMS, VAX Record Management Services
Explanation: The allocation XAB for a $CREATE or $EXTEND operation
contains an invalid alignment boundary type (ALN field).
User Action: The status value (STV) field of the FAB provides the area
identification of the XAB in error. Verify that the call to the VAX RMS service
was coded correctly.

Messages

ALQ,

invalid allocation quantity (negative, or 0 on $EXTEND)
Facility: RMS, VAX Record Management Services
Explanation: An invalid allocation quantity was specified in an allocation
XAB or FAB for a $CREATE or $EXTEND operation.
User Action: Verify that the call to the VAX RMS service was coded correctly.
For file creation operations, the error indicates that the value specified is less
than zero. For file extension operations, the error indicates that the value
specified was less than or equal to zero.

ALREADYINIT,

initialization already done. PSIACP previously started

Facility: PSI, VAX Packetnet System Interface
Explanation: The network device unit was nonzero. This means that PSIACP
must have been started previously.
User Action: None.
ALREDEF,

multiple .TRANSFER for symbol 'symbol-name' illegal psect 'psectname' offset 'number' in module 'module-name' file 'file-name'

Facility: LINK, VAX Linker
Explanation: An attempt was made to use a .TRANSFER directive on a
symbol name more than once.
User Action: Remove all but the first .TRANSFER directive for the symbol.
ALTIHDBAD,

invalid alternate index file header, RVN 'n'

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the alternate index file header on
the specified relative volume was corrupted.
User Action: None. The alternate index file header is refreshed from the
primary index file header.
AMBCMD,

ambiguous command

Facility: NCP, Network Control Program
Explanation: A keyword in the command has not been specified with enough
characters to distinguish it from another keyword acceptable in this context.
User Action: Reenter the command.
AMBIG,

ambiguous field name or class name 'class-name'

Facility: SHOW, SHOW Facility
Explanation: The field or class name entered is not unique.
User Action: Reenter the field or class name with addition characters or type
HELP FIELDS or HELP CLASSES to get a list of available fields or classes.
AMBIG,

ambiguous parameter 'parameter'

Facility: NCP, Network Control Program
Explanation: The command has input that is not unique.
User Action: Reenter the command with a unique parameter.

2-15

Messages

AMBIGNAME,

Variable 'name' cannot be a procedure at line 'integer7

Facility: VAX Text Processing Utility
Explanation: You previously used an identifier as a variable; you are now
attempting to use the same identifier as a procedure.
User Action: Use a different name for the procedure.
Ambiguous command
Facility: DISKQUOTA, Diskquota Utility
Explanation: You specified an ambiguous command.
User Action: Spell the command name completely.
Ambiguous qualifier
Facility: DISKQUOTA, Diskquota Utility
Explanation: You specified an ambiguous qualifier.
User Action: Spell the qualifier name completely.
AMBKEY,

'keyword' is an ambiguous keyword

Facility: LIB, Run-Time Library General Procedures
Explanation: Too few characters were used to truncate the keyword indicated
to make it unique within its context. This message is associated with a status
code returned from the VAX Run-Time Procedure Library.
User Action: Reenter the keyword, specifying enough characters to make it
unique.
AMBSYMDEF,

ambiguous symbol definition

Facility: LIB, Run-Time Library General Procedures
Explanation: The specified symbol name was ambiguous when compared
with existing symbol names. This condition can occur when abbreviated
symbols have been previously defined.
User Action: Refer to the VAX/VMS DCL Dictionary for more information
about abbreviated symbols.
ANI,

not ANSI "D" format
Facility: RMS, VAX Record Management Services
Explanation: The records in a magnetic tape file do not conform to the ANSI
standard for magnetic tape (D format).
User Action: Modify the program that writes the magnetic tape file so that
the file is in the correct format or verify that the tape is an ANSI-labelled
tape. Use an alternative method of reading the file such as mounting the tape
as a foreign tape or using VAX RMS block I/O.

2-16

Messages

AOP,

allocation options error for area id = 'nnn'
Facility: RMS, VAX Record Management Services
Explanation: An allocation XAB for a $CREATE or $EXTEND operation
specifies an invalid allocation option (AOP field).

User Action: The status value (STV) field of the FAB provides the area
identification of the XAB in error. Verify that the call to the VAX RMS service
was coded correctly.
APPENDEDB,

input-file-spec appended to output-file-spec (nnn blocks)

Facility: Shared by several facilities
Explanation: An input file is being appended to an output file. The message
displays the number of blocks or the number of records appended, based on
the size of the input file.
User Action: None. This message is informational.
APTREFHIGH,

Inconsistent active page table reference count

Active page table swap write error

ACP queue is unstable

Facility: MOUNT, MOUNT Command
Explanation: The system cannot start the ACP specified in the DCL
command MOUNT request. This message indicates an error in the operating
system software.
User Action: Consult with the system manager to determine what events in
the system might be preventing ACPs from starting.

2-17

ARGMISMATCH,

Data type of first argument unsupported for built-in

Facility: VAX Text Processing Utility
Explanation: The first argument has a data type that is unsupported by the
built-in procedure being called.
User Action: To find the correct data types for this built-in procedure, refer
to the VAX Text Processing Utility Reference Manual or to online help.
ARGREQ,

missing argument - supply all required arguments

Facility: CLI, Command Language Interpreter (DCL)
Explanation: When you invoked a lexical function, you did not specify all
the required arguments.
User Action: Supply all the required arguments.
ARGTOOLONG,

argument too long

Facility: MACRO, VAX Macro Assembler
Explanation: An argument was more than 1000 characters long.
User Action: Reduce the length of the argument.
ARTRES,

reserved arithmetic trap at PC location, PSL = xxxxxxxx

Facility: SYSTEM, VAX/VMS System Services
Explanation: An unknown arithmetic exception has occurred.
User Action: This message should not occur. If it does occur, inform the
system manager.
ASCTOOLONG,

ASCII string too long

Facility: MACRO, VAX Macro Assembler
Explanation: Either the string in an .ASCIC directive was more than
255 characters or the string in an .ASCID directive was more than 65535
characters.
User Action: Reduce the length of the string.
ASGNMNTSYN,

assignment syntax error

Facility: MACRO, VAX Macro Assembler
Explanation: A direct assignment statement contains a syntax error.
User Action: Refer to the VAX MACRO and Instruction Set Reference Volume
for information on syntax errors and correct the syntax error.
ASSIGN,

error assigning channel to 'device-spec'

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility encountered an error during an attempt to
assign a channel to the volume to be verified. The accompanying message
provides additional information.
User Action: Correct the condition that caused the error and reenter the
Verify Utility command line.

Messages

ASSIGN,

error assigning channel to 'device-name7

Facility: BAD, Bad Block Locator Utility
Explanation: The utility encountered an error while attempting to assign a
channel to the device.
User Action: Examine the associated message for a clue to the problem,
correct the trouble, and reinvoke the utility.
ASSNET,

failed to assign a channel to the X25 network device (NWAO:)

Facility: PSI, VAX Packetnet System Interface
Explanation: VAX PSI failed to assign a channel to the X.25 network device.
This may have occurred because the NW driver was not loaded.
User Action: Load the NW driver and try again.
ASTFLT,

AST fault, SP = xxxxxxxx param = xxxxxxxx, PC = location, PSL =
xxxxxxxx, target PC = location, PSL = xxxxxxxx

Facility: SYSTEM, VAX/VMS System Services
Explanation: The system attempted to deliver an asynchronous system trap
(AST) to an image, but the user stack pointer was either invalid, or did not
have sufficient space for the AST call frame. This message indicates an
exception condition and is usually followed by a display of the condition
arguments, the registers, and the stack at the time of the exception.
User Action: Examine the parameters displayed in the message to determine
the instruction that caused the error. Locate the programming error that
modified the stack.
ASYNCWRTER,

Asynchronous write memory failure

at PC = xxxxxxxx

Facility: Shared by several facilities
Explanation: This message generally accompanies a message indicating a
software failure.
User Action: Take corrective action based on the accompanying message(s).

2-19

Messages

ATR,

file attributes read error
Facility: RMS, VAX Record Management Services
Explanation: A read error occurred on a file header.
User Action: Depending on the operation, the status value (STV) field in the
FAB or RAB contains a status code that provides additional information about
the condition. Take corrective action based on this status code. Check the
status of the device and repeat the request. The header block may be bad.
If the error occurs on many files, the disk or drive may be bad. Notify the
system manager.

ATTACHED,

terminal now attached to process 'process name'

Facility: CLI, Command Language Interpreter (DCL)
Explanation: This message is output by the DCL command ATTACH when it
attaches to a process.
User Action: None.
ATTCONSTO,

attempt to continue from stop

Facility: LIB, Run-Time Library General Procedures
Explanation: A condition handling procedure attempted to continue from a
call to LIB$STOP; that is, the procedure attempted to continue from an error
that was not able to be continued by returning a successful completion status.
User Action: Using the traceback information or PC displayed in the
message, locate the condition handler that incorrectly tried to continue
execution. Condition handlers can return success only for continuable errors
and should return success only for errors that they have corrected. Otherwise,
they should resignal the error.
Attempt to CUT or APPEND to current buffer
Facility: EDT, EDT Editor
Explanation: While trying to perform a CUT or APPEND operation, you
named the current text buffer as the destination text buffer. The default
destination is the PASTE text buffer.
User Action: Copy the text to an intermediate buffer.
Attempt to PASTE the current buffer
Facility: EDT, EDT Editor
Explanation: The EDT command PASTE attempted to paste text into the
same text buffer containing the text to be pasted.
User Action: Copy the text to an intermediate buffer.
Attempt to re-enter EDT
Facility: EDT, EDT Editor
Explanation: While using callable EDT, you attempted to recall EDT without
having exited.
User Action: Exit from EDT before attempting to recall EDT.

2-20

Messages

ATTREQREF,

attach request refused

Facility: LIB, Run-Time Library General Procedures
Explanation: The specified process could not be attached to. Either it was
not detached or did not belong to the caller's job.
User Action: Ensure that the specified process is detached and belongs to the
caller's job.
ATW,

file attributes write error

Facility: RMS, VAX Record Management Services
Explanation: A write error occurred during an attempt by VAX RMS to write
a file header.
User Action: Depending on the operation, the status value (STV) field in the
FAB or RAB contains a status code that provides additional information about
the condition. Take corrective action based on this status code. Check the
status of the device and repeat the request. The header block may be bad.
If the error occurs on many files, the disk or drive may be bad. Notify the
system manager.
BACKLINK,

incorrect directory back link 'file-spec'

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the back link of the specified file
did not contain the file identification of the directory file in which the file is
cataloged. This condition is normal if the file is cataloged in more than one
directory.
User Action: None. Set the back link pointer to point to the directory file.
Backup past top of buffer,

Facility: EDT, EDT Editor
Explanation: You attempted to move the cursor to a position preceding the
first line (top) of the buffer.
User Action: Press any key to move the cursor below the top of the buffer.
BADACP,

invalid syntax on /PROCESSOR qualifier

Facility: MOUNT, MOUNT Command
Explanation: The keyword or file specification value specified for the
/PROCESSOR qualifier is not specified correctly.
User Action: Reenter the command; refer to the VAX/VMS DCL Dictionary
for the correct syntax.
BADACP,

unable to start network acp

Facility: NCP, Network Control Program
Explanation: NCP could not create a process or could not find CCP.EXE.
User Action: Ensure that enough processes can be created and that DECnetVAX has been properly installed.

2-21

Messages

BADALORQSZ,

Bad memory allocation request size

Unrecognized argument to procedure at line 'integer7

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

Target of the assignment at line 'integer7 cannot be a function
/keyword

Facility: VAX Text Processing Utility
Explanation: The left-hand side of an assignment statement must be a
variable. It cannot be a procedure name or a keyword.
User Action: Use a different variable name to the left of the operator : = in
this assignment statement.
BADATTRIB,

bad attribute control list

Facility: SYSTEM, VAX/VMS System Services
Explanation: An invalid code or size was specified in the read or write
attribute list for a file system ACP QIO function.
User Action: Check for a programming error. Begin debugging procedures to
verify the source of the problem and to correct the problem. Note that when
using ANSI magnetic tapes, the blocksize must be 4 bytes greater than the
largest record in a variable record length file and the largest record that can
be written is 2048 bytes.
BADBITMAP,

BITMAP.SYS too small or not contiguous, RVN 'n'

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the storage bit map file,
[000000]BITMAP.SYS;1, on the specified relative volume, was not large
enough to accommodate the volume size and volume cluster factor, or that it
was not contiguous. This error can result from an erroneous volume size in
the storage control block or from an erroneous volume cluster factor in the
home block.
User Action: If the volume can no longer be mounted by the operating
system, it is corrupted and must be reconstructed from back-up media. If the
volume can be mounted, the damage can be repaired by copying the volume
to fresh media.

2—22

Messages

BADBLK,

invalid option block

Facility: CONVERT, Convert Utility
Explanation: You have made an error in constructing the option block used
in the CONV$PASS_OPTIONS routine.
User Action: Refer to the VAX/VMS System Services Reference Manual for
instructions on building an option block.
BADBLKSIZE,

'save-set-spec' has inconsistent block size

Facility: BACKUP, Backup Utility
Explanation: The volume mounted as a continuation volume of a
multivolume save set was not recorded with the same block size as previous
volumes of the save set. This volume is probably not part of the same save
set.
User Action: Locate and mount the correct continuation volume.
BADBLOADR,

bad block address

Facility: LIB, Run-Time Library General Procedures
Explanation: The library procedure LIB$FREE_VM was called with an
invalid virtual storage address.
User Action: Begin debugging procedures to verify the problem and to
correct the problem.
BADBLOCK,

bad blocks on 'device' do not match input

Facility: BACKUP, Backup Utility
Explanation: In a COPY or RESTORE operation with the /PHYSICAL
qualifier, a bad block was present on the output volume in a location where
the input volume had a good block. The backup operation will not result in a
valid Files-11 volume.
User Action: Reevaluate the operation; another mode of operation, such
as the /IMAGE qualifier, may be appropriate. Or retry the operation using
either the original input volume or an error-free output volume as the output
volume.
BADBLOCKS,

invalid syntax in bad block list

Facility: INIT, INITIALIZE Volume Command
Explanation: The command syntax for the /BAD—BLOCKS qualifier is
invalid.
User Action: Reenter the command; use the DCL command HELP or refer
to the VAX /VMS DCL Dictionary for the correct syntax. If the list of blocks is
long, place the command in a command procedure file.

2-23

Messages

BADBLOSIZ,

bad block size

Facility: LIB, Run-Time Library General Procedures
Explanation: Either the library procedure LIB$GET_VM was called with a
request for zero blocks or the requested block size was too large.
User Action: If the requested block size was zero, correct the source
program. If the specified block size was too large, use the DCL command
SET WORKING—SET to increase the current working set limit for your
process and retry the program.
BADBOOTCB,

Corrupted Boot Control Block

ACP buffer address out of range of buffer pool

Bad ACP buffer type code

2-24

Messages

BADBUFWRITE,

Error occurred writing buffer 'buffer name'

Facility: VAX Text Processing Utility
Explanation: An I/O error occurred while writing the the contents of the
buffer to a file. This could be due to operating system or VAX RMS errors.
This message should be accompanied by another message specifying the
reason for the error. The creation of the file stopped at the point of the error.
User Action: Correct the specified problem and reenter your command.
BADBUG,

please report TRACE bug no. 'nnn'

Facility: TRACE, Traceback
Explanation: This message indicates an internal programming error in the
Traceback Facility.
User Action: Collect as much information as possible and submit a Software
Performance Report; include the bug number (nnn) displayed in the message.
BADBYTE,

invalid data 'xx' at 'location'

Facility: Shared by several facilities
Explanation: The specified data is invalid at the given location.
User Action: None.
BADCACHE,

invalid syntax on /CACHE qualifier

Facility: MOUNT, MOUNT Command
Explanation: The options given with the /CACHE qualifier have invalid
syntax.
User Action: Verify the command and reenter the correct syntax.
BADCASE,

Unrecognized CASE constant at line 'integer'

Facility: VAX Text Processing Utility
Explanation: Case constants can only be integers, keywords, or one-character
strings.
User Action: Check your case labels or your FROM...TO limits to ensure that
the case constants follow the stated rules.
BADCASELIMIT,

CASE constant outside of CASE limits at line 'integer'

Facility: VAX Text Processing Utility
Explanation: A case constant used as a case label (inside [...]) does not fall
within the range specified by the FROM...TO limits of your case statement.
User Action: Modify your CASE limits or correct the case labels and
recompile your program.

2-25

Messages

BADCCC,

bad compilation completion code ('decimal-number7) in module
'module-name7 file 'file-name'

Facility: LINK, VAX Linker
Explanation: An illegal compilation completion code was found in the
specified module.
User Action: Recompile the module and relink.
BADCCC,

illegal compilation code 'code' in module 'module-name'

Unrecognized character in input on line 'integer'

Facility: VAX Text Processing Utility
Explanation: A control character or some other character that is not
recognized by the parser exists in the program you are trying to compile.
User Action: Remove the unrecognized character and recompile your
program.
BADCHKSUM,

bad file header checksum

Facility: SYSTEM, VAX/VMS System Services
Explanation: The checksum in the file header is invalid or the file header
may be corrupt.
User Action: Repair the volume with the Verify Utility. Recover the file from
backup medium.
BADCHKSUM,

shared memory data structures corrupted - reinitialization
necessary

Facility: SYSGEN, System Generation Utility
Explanation: A CRC check of the constant fields in the shared memory
datapage has detected an error.
User Action: Reboot all processors using the shared memory.
BADCON,

cannot connect to file 'file-spec'

Facility: NCP, Network Control Program
Explanation: This message indicates a possible disk drive error.
User Action: Check the disk drive for proper functioning.
BADCOPIES,

'nnn' is an invalid number of copies

Facility: Shared by several facilities
Explanation: The number of copies is not within a valid range.
User Action: Reenter the command; specify a different number of copies.

2-26

Messages

BADCSP,

scope setting not module or routine

Facility: PATCH, VAX Image File Patch Utility
Explanation: The symbol specified as the new scope value is not a module
name or routine name.
User Action: Reenter the command using the corrected scope value.
BADCTLMSK,

bad control character enable/disable mask

Facility: CLI, Command Language Interpreter (DCL)
Explanation: You specified something other than CTRL/T or CTRL/Y to
enable or disable.
User Action: Specify CTRL/T or CTRL/Y to enable or disable.
BADDALRQSZ,

Bad memory deallocation request size or address

error in block 'nn' of 'file-spec' detected during save

Facility: BACKUP, Backup Utility
Explanation: A read error for the specified block of the specified file occurred
when the save set was created. Data in this block may be 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.
BADDATCHK,

invalid keyword on /DATACHECK qualifier

Facility: MOUNT, MOUNT Command and INIT, INITIALIZE Volume
Command
Explanation: The keyword specified for the /DATACHECK qualifier was
neither READ nor WRITE.
User Action: Reenter the command; specify either READ or WRITE.
BADDATDAT,

data echoed invalid

Facility: NET, DECnet Test Program Protocol
Explanation: This message indicates a test error.
User Action: Retry the test.

2-27

Messages

BADDATLEN,

not enough data sent/received

Facility: NET, DECnet Test Program Protocol
Explanation: This message indicates a test error.
User Action: Retry the test.
BADDELETE,

Cannot delete static string at the line 'integer7

Facility: VAX Text Processing Utility
Explanation: You are attempting to delete (modify) a string constant that was
passed to a procedure as an argument.
User Action: Check your program for this error and remove the problem
statement.
BADDELIM,

invalid delimiter following 'command'

Facility: Shared by several facilities
Explanation: An invalid character occurred in a command. This message
displays the rejected portion of the command.
User Action: Check the command for a spelling or syntax error; reenter the
command.
BADDENS,

unknown value on /DENSITY qualifier

Facility: MOUNT, MOUNT Command and INIT, INITIALIZE Volume
Command
Explanation: The value specified for a tape density was not 800, 1600, or
6250. The value specified for a floppy was not single or double.
User Action: Reenter the command; specify either 800, 1600, or 6250 for the
density.
BADDIR,

directory 'directory' has invalid format

Facility: BACKUP, Backup Utility and VERIFY, Verify Utility
Explanation: The specified directory file is not in the expected format for a
directory file. The file is corrupted.
User Action: None. Processing of the directory file is terminated. If the
Verify Utility finds lost files, it neither repairs nor reports them until the error
is corrected.
BADDIRENT,

invalid file identification in directory entry 'file-spec'

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the specified directory entry did
not contain a valid file identification. Probably, the file has been deleted.
User Action: None. The directory entry is removed.

2-28

Messages

BADDST,

no symbols in image

Facility: TRACE, Traceback
Explanation: The image header in an executable image file does not contain
symbols required by the Traceback Facility. The message indicates an
operating system problem.
User Action: Collect as much information as possible and submit a Software
Performance Report.
BADDSTMAP,

failure to map symbol table, CREMAPSEC status = xxxxxxxx

Facility: TRACE, Traceback
Explanation: The system could not perform a symbolic traceback because the
system could not map the symbol table. The hexadecimal status code is the
return status from an internal call to the Create and Map Section ($CRMPSC)
system service.
User Action: Determine the reason associated with the indicated status
code. If the reason is anything other than a lack of virtual address space,
assume that the problem is a system problem. Collect as much information
as possible and submit a Software Performance Report.
BaDDSTVBN,

image symbol table VBN = 'nnn'

Facility: TRACE, Traceback
Explanation: The Traceback Facility cannot interpret the image header for an
executable file. This message indicates an internal operating system error or
an error in the linker.
User Action: Collect as much information as possible and submit a Software
Performance Report; include the virtual block number (VBN) number (nnn)
displayed in the message.
BADECO,

illegal eco level of 'nn' in 'file-spec'

Facility: PATCH, VAX Image File Patch Utility
Explanation: An illegal ECO level was specified. The legal ECO level range
is between one and 128, inclusive.
User Action: Retry using a legal ECO level.
BADEFBLK,

file ('file-id') 'file-name' inconsistent EFBLK and map area

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the end-of-file pointer recorded
in the VAX RMS record attributes for the specified file did not lie within the
space actually allocated to the file.
User Action: None. The end of file pointer is set to point to the end of the
allocated space.
BADENTRY,

bad format for .ENTRY statement

Facility: MACRO, VAX Macro Assembler
Explanation: The .ENTRY directive did not specify an entry point name and
a correct entry mask.
User Action: Correct the .ENTRY directive syntax.

2-29

Messages

BADESCAPE,

syntax error in escape sequence

Facility: SYSTEM, VAX/VMS System Services
Explanation: A terminal escape sequence is invalid. This message is
associated with a status code returned by I/O functions.
User Action: Check for a programming error. Correct the escape sequence
syntax.
BADEVTYP,

bad device type. Value' in text library module, 'name'

Facility: ERF, ANALYZE/Error Log Utility
Explanation: A value in the specified library module is out of the required
range.
User Action: Submit a Software Performance Report.
BADEVVAL,

bad device table value, 'value' in text library module, 'name'

Facility: ERF, ANALYZE/Error Log Utility
Explanation: A value in the specified library module is out of the required
range.
User Action: Submit a Software Performance Report.
BADEXCL,

directory or device not allowed in /EXCLUDE = exclude-item

Facility: SEARCH, SEARCH Command
Explanation: The listed exclude item contains a network node name, a device
name, or a directory name.
User Action: Reenter the command, specifying only a file name, a file type,
and a version number
BADEXCLNAM,

invalid filename in /EXCLUDE = exclude-item

Facility: SEARCH, SEARCH Command
Explanation: The listed exclude item is not a valid VAX RMS file
specification.
User Action: Reenter the command with a correct file specification.
BADEXE,

failure to open image file 'file-name'

Facility: TRACE, Traceback
Explanation: The operating system rejected the format of the indicated
executable image file. The file cannot be opened. This message indicates an
internal operating system error.
User Action: Collect as much information as possible and submit a Software
Performance Report.

2-30

Messages

BADEXECLO,

failure to close image file 'file-name'

Facility: TRACE, Traceback
Explanation: The operating system rejected the format of the indicated
executable image file. The file cannot be closed. This message indicates an
internal operating system error.
User Action: Collect as much information as possible and submit a Software
Performance Report.
BADEXERAB,

failure to connect image file 'file-name'

Facility: TRACE, Traceback
Explanation: The operating system rejected the format of the indicated
executable image file. This message indicates an internal operating system
error.
User Action: Collect as much information as possible and submit a Software
Performance Report.
BADEXITIF,

EXITIF occurs outside of a LOOP at line 'integer'

Facility: VAX Text Processing Utility
Explanation: An EXITIF statement must be inside the boundaries of
LOOP...ENDLOOP statements.
User Action: Remove EXITIF statements that do not follow the stated rule.
BADFID,

ACP file number out of range for this volume

'name' field invalid at 'location'

Facility: Shared by several facilities
Explanation: The specified data is invalid at the given location.
User Action: Retry the operation. If the error persists, submit a Software
Performance Report.
BADFIL,

badly formatted file 'file-spec'

Facility: NCP, Network Control Program
Explanation: The file was corrupted.
User Action: Recreate the file.

2—31

Messages

BADFILEHDR,

bad file header

Facility: SYSTEM, VAX/VMS System Services
Explanation: The file header has failed validity checks and is corrupted.
User Action: Repair the volume with the Verify Utility and recover the file
from back-up media.
BADFILENAME,

bad file name syntax

Facility: SYSTEM, VAX/VMS System Services
Explanation: This message is associated with a status code returned from
a file system ACP QIO request. The file name string for a file specification
contains illegal characters or is longer than nine characters.
User Action: Check for a programming error. Verify that file name strings
consist only of the characters A through Z and zero through nine. They must
be no longer than nine characters.
BADFILENAME,

name 'filename' not suitable for 'volume-type' volume

Facility: EXCHANGE, Exchange Utility
Explanation: The EXCHANGE utility was given a filename which is not in
the correct format for the target volume type.
User Action: Reenter the command, using a filename which is valid for the
volume shown in the message.
BADFILEVER,

bad file version number

Facility: SYSTEM, VAX/VMS System Services
Explanation: The message indicates that the file version number in a file
specification is greater than 32767 or contains nonnumeric characters. Or the
file system may have attempted to create a file with a version higher than
32767 through defaulting rules.
User Action: Check for a programming error. Verify that existing file
versions are less than 32767. Rename if necessary.
BADFIRSTLINE,

First line = 'integer', must be between 'integer' and 'integer'

Facility: VAX Text Processing Utility
Explanation: You gave a first line argument to the built-in procedure
CREATE—WINDOW that is outside the physical screen limits.
User Action: Pick a valid first line value (between 1 and pagelength) and
reenter your command.
BAD—FIXUPVEC,

the fixup vector contains inconsistent data

Facility: IMG ACT, Image Activator
Explanation: There are inconsistencies in the structure of the fixup vector in
the image. This usually indicates a corrupted or invalid image.
User Action: Relink the image.

2-32

Messages

BADFORKIPL,

Bad FORK exit interrupt priority level

'form-type' is an invalid form type

Facility: Shared by several facilities
Explanation: The form type specified with the /FORMS qualifier is not one
of the forms defined by:
SYS$SYSROOT:[SYSMGR]FORMSTYPE.DAT.1

User Action: Respecify the form type with a valid form name.
BADFORM,

invalid option for /FORMAT = format-option

Facility: SEARCH, SEARCH Command
Explanation: The option given for /FORMAT is not valid. This message is
issued with an accompanying message providing more information about
why the format option is not acceptable.
User Action: Reenter the command using one of the valid format options.
BADFRMT,

volume is not mounted with Files-11 format

Facility: SET, SET Facility
Explanation: The volume is mounted with the /FOREIGN qualifier; it cannot
be modified.
User Action: None.
BADFUNC,

invalid function type received

Facility: NET, DECnet Test Program Protocol
Explanation: The DECnet-VAX test program has a protocol incompatibility.
User Action: Run the test against a compatible version of DTRECV or an
equivalent.
BADGSD,

unknown type of GSD entry: 'GSD'

Facility: SDA, System Dump Analyzer
Explanation: SDA encountered a type of global symbol that it does not
recognize, either in the SYS.STB file or in a file specified in the SDA
command READ. The type of global symbol definition GSD is represented by
a byte.
User Action: This message can occur during either initialization or operation
of the SDA, and usually means that the file being read has been corrupted.
Check the integrity of the symbol table file.

2-33

Messages

BADHDR,

an error was discovered in the image header

Facility: IMG ACT, Image Activator
Explanation: The image header type word contains an invalid type code.
This usually indicates a corrupted or invalid image.
User Action: Relink the image.
BADHDR,

no symbol table data in image header

Facility: TRACE, Traceback
Explanation: The image header in the executable image file does not contain
expected symbol table data. This message indicates an internal operating
system error.
User Action: Collect as much information as possible and submit a Software
Performance Report.
BADHEADER,

file ('file-id') 'file-name' invalid file header

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the specified file header was
corrupted.
User Action: None. The file header is rewritten with a deleted file header.
BADHIBLK,

file ('file-id') 'file-name' inconsistent HIBLK and map area

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the file size recorded in the VAX
RMS record attributes did not agree with the number of blocks actually
allocated to the file.
User Action: None. The record attributes are corrected by changing the file
size to reflect the correct number of blocks.
BADHOMBLK,

bad home block encountered on volume

Facility: MOUNT, MOUNT Command
Explanation: An I/O error occurred while reading a home block during
/BIND processing. A subsequent message explains the nature of the error.
The first occurrence of this message is a warning; the second is fatal.
User Action: Repair with the Verify Utility or reinitialize the volume and
retry the operation.
BADHOUR,

you are not authorized to login at this time

Facility: LOGIN, Login Processor
Explanation: The information in the user authorization file indicates that you
are not allowed to log in at this time.
User Action: Wait until the time that you are authorized to log in.

Messages

BADIDENT,

unable to patch image with ident of 'nn'

Facility: PATCH, VAX Image File Patch Utility
Explanation: PATCH does not recognize this version of the image file.
User Action: Relink your image file. Ensure that the file being patched is a
native mode image file.
BADIF,

IF statement contains an assignment statement at line 'integer'

Facility: VAX Text Processing Utility
Explanation: The IF expression in an IF...THEN statement must contain
logical operators only. This message is likely to occur if you used the
expression x: = y instead of the the Boolean expression x = y. The IF
expression in an IF...THEN statement makes a logical comparison.
User Action: Change the operator : = to the operator =.
BADIMGHDR,

bad image header

Facility: SYSTEM, VAX/VMS System Services
Explanation: An image to be executed with the DCL command RUN or
within a process is not in the correct format and cannot be executed.
User Action: Verify that the specified file is an executable image. If
necessary, recompile or reassemble and relink the program to ensure that
the image file is in the proper format.
BADIMGHDR,

bad image header in shareable image file 'file-name'

Facility: LINK, VAX Linker
Explanation: A shareable image contains a bad image header, or the file is
not a shareable image.
User Action: Correct and relink.
BADINDEX,

invalid syntax on /INDEX qualifier

Facility: INIT, INITIALIZE Volume Command
Explanation: The command syntax for the /INDEX qualifier is invalid.
User Action: Reenter the command; use the DCL command HELP or refer to
the VAX/VMS DCL Dictionary for the correct syntax.
BADINITSZ,

illegal size value defaulting patch size to XXXXXXXX bytes

Facility: PATCH, VAX Image File Patch Utility
Explanation: The size-expression input argument did not fall within the valid
range. PATCH set the patch area to the address named in the SET PATCHAREA command, and use the default patch area size to build the patch area
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.

2-35

Messages

BADIONAME,

'name7 has not been previously defined

Facility: CDU, Command Definition Utility
Explanation: There is an undefined name in the output list.
User Action: Check the spelling of the name in the output list.
BADIRECTORY,

bad directory file format

Facility: SYSTEM, VAX/VMS System Services
Explanation: The message indicates that the specified directory file is not
valid. Either the file is not a directory or the directory file contains invalid
data.
User Action: Check for a programming error. Verify that the specified file is
a directory. If necessary, repair the volume with the Verify Utility.
BADISD,

illegal image section descriptor

Facility: SYSTEM, VAX/VMS System Services
Explanation: This severe error message is associated with a status code
returned from a system service request. An illegal image section descriptor
was encountered.
User Action: This file may be corrupted or may not be an executable image.
There also may be a problem associated with the linker; in this case, submit a
Software Performance Report.
BADJOBID,

'name7 is a bad job identifier

Facility: Shared by several facilities
Explanation: The job identifier specified by the /ENTRY qualifier is missing
or not valid.
User Action: Respecify a valid job identifier by using the DCL command
SHOW QUEUE.
BADJOBNAME,

'name7 is an invalid job name

Facility: Shared by several facilities
Explanation: The job name specified by the /NAME qualifier is missing or
not valid.
User Action: Respecify the job name with one of the job names listed in the
DCL command SHOW QUEUE.
BADJOUCHAR,

Expected character in journal file

Facility: VAX Text Processing Utility
Explanation: Something other than a character was found in the journal file
when a character was expected.
User Action: If the recovered information is sufficient, resume editing from
this point. VAXTPU has recovered as much as it can from your journal file.

2-36

Messages

BADJOUCOM,

Journaled command file was 'string7, recovering with 'string'

Facility: VAX Text Processing Utility
Explanation: The editing session is being recovered with a different
command file than was used during the original editing session.
User Action: Stop the recovery session and restart it using the correct (the
original) section and command files.
BADJOUEDIT,

Journaled with edit mode 'string', recovering with edit mode
'string'

Facility: VAX Text Processing Utility
Explanation: The editing session is being recovered with a different edit
mode setting than was used during the original editing session.
User Action: Stop the recovery session and reset the terminal characteristics
to those used in the original editing session.
BADJOUEIGHT,

Journaled with eightbit 'string', recovering with eightbit 'string'

Facility: VAX Text Processing Utility
Explanation: The editing session is being recovered with a different eightbit
setting than was used during the original editing session.
User Action: Stop the recovery session and reset the terminal characteristics
to those used in the original editing session.
BADJOUFILE,

Recovery terminated due to error in journal file access

Facility: VAX Text Processing Utility
Explanation: The recovery operation halted because the journal file could not
be accessed.
User Action: Correct the problem preventing access to the journal file and
retry the recovery.
BADJOUINPUT,

Journaled input file was 'string', recovering with 'string'

Facility: VAX Text Processing Utility
Explanation: The editing session is being recovered with a different input file
than was used during the original editing session.
User Action: Stop the recovery session and restart it using the correct
(original) input file.
BADJOUKEY,

Expected key in journal file

Facility: VAX Text Processing Utility
Explanation: Something other than a key was found in the journal file when
a key was expected.
User Action: If the recovered information is sufficient, resume editing from
this point. VAXTPU has recovered as much as it can from your journal file.

2-37

BADJOULINE,

Journaled with line editing 'string', recovering with line editing
'string'

Facility: VAX Text Processing Utility
Explanation: The editing session is being recovered with a different line
editing setting than was used during the original editing session.
User Action: Stop the recovery session and reset the terminal characteristics
to those used in the original editing session.
BADJOUPAGE,

Journaled page length was 'integer', recovering with page length
'integer'

Facility: VAX Text Processing Utility
Explanation: The editing session is being recovered with a different page
length than was used during the original editing session.
User Action: Stop the recovery session and reset the terminal characteristics
to those used in the original editing session.
BADJOUSEC,

Journaled section was 'string', recovering with 'string'

Facility: VAX Text Processing Utility
Explanation: The editing session is being recovered with a different section
file than was used during the original editing session.
User Action: Stop the recovery session and restart it using the correct
(original) section file.
BADJOUSTR,

Expected string in journal file

Facility: VAX Text Processing Utility
Explanation: Something other than a string was found in the journal file
when a string was expected.
User Action: If the recovered information is sufficient for your needs, resume
editing from this point. VAXTPU has recovered as much as it can from your
journal file.
BADJOUTERM,

Journaled terminal type was 'string', recovering on a 'string'

Facility: VAX Text Processing Utility
Explanation: A journal file was created during an editing session on one
type of terminal and the recovery is taking place on another type. This might
result in journal file inconsistencies.
User Action: Stop the recovery session and reset the terminal characteristics
to those used in the original editing session.
BADJOUWIDTH,

Journaled width was 'integer', recovering with width 'integer'

Facility: VAX Text Processing Utility
Explanation: The editing session is being recovered with a different screen
width than was used during the original editing session.
User Action: Stop the recovery session and reset the terminal characteristics
to those used in the original editing session.

Messages

BADJRNL,

invalid syntax on /JOURNAL qualifier

Facility: MOUNT, MOUNT Command
Explanation: You have entered the wrong command line syntax.
User Action: Correct the syntax and reenter.
BADKEY,

'keyword7 is an invalid keyword

Facility: VAX Text Processing Utility
Explanation: An invalid keyword was specified as an argument to a built-in
procedure.
User Action: Correct the keyword and reenter your statement.
BADKEY,

'keyword' is an invalid keyword

Facility: Shared by several facilities
Explanation: An invalid keyword was specified. The message displays the
rejected portion of the command.
User Action: Check the command for a spelling or syntax error. Use the
DCL command HELP or refer to the VAX/VMS DCL Dictionary for the valid
keywords and reenter the command.
BADKEY,

illegal key

Facility: LIBRAR, LIBRARY Command
Explanation: This severe error message is generated by the DCL command
LIBRARY. The specified module is illegal.
User Action: Reenter the command line specifying a legal module.
BAD_KEY,

invalid key specification

Facility: SORT, VAX SORT/MERGE Utility
Explanation: The key field size, position, data type, or order is incorrect
within the key definition. Positions start at one and cannot be greater then
the maximum record size. Record size must be less than or equal to 32,767
for character data; 1, 2, 4, 8, or 16 for binary data; and less than or equal to
31 for decimal.
User Action: Check the command string key specifiers.
BADLABELQ,

invalid keyword on /LABEL qualifier

Facility: INIT, INITIALIZE Volume Command
Explanation: An invalid keyword was specified with the /LABEL qualifier.
The only keyword compatible with the /LABEL qualifier is shown below:
/LABEL=VOLUME_ACCESSIBILITY:"single character"

User Action: Specify the following keyword and retry:
=VOLUME_ACCESSIBILITY:"single character"

2—39

BADLCKWSLE,

Bad locked working set list entry, not a page table

illegal lexical function argument

Facility: MACRO, VAX Macro Assembler
Explanation: The argument to a macro string operator was invalid. String
arguments can be macro arguments or strings delimited by angle brackets
or the circumflex delimiters. Symbol arguments can be absolute symbols or
decimal integers.
User Action: Correct the argument syntax.
BADLEXFORM,

illegal format for lexical function

Facility: MACRO, VAX Macro Assembler
Explanation: The macro string operator contained a syntax error.
User Action: Correct the macro string operator syntax.
BADLOGIC,

Internal logic error detected

Facility: VAX Text Processing Utility
Explanation: An internal software error occurred.
User Action: Submit a Software Performance Report.
BADLOGIC,

internal logic error detected

Facility: DSRINDEX, DIGITAL Standard Runoff Indexing Utility
Explanation: A system internal error has occurred.
User Action: Submit a Software Performance Report.
BADLOGIC,

internal logic error detected, please report error 'errorcode'

Facility: EXCHANGE, Exchange Utility
Explanation: The EXCHANGE utility encountered an unexpected condition,
and has terminated.
User Action: Please submit an SPR, describing the error number and the
commands which resulted in the message. If the error is only reproducible
using a particular piece of media, please send a copy of the media with the
SPR (use BACKUP /PHYSICAL to make the copy).

Messages

BADLOGIC,

internal logic error detected [at PC location]

Facility: Shared by several facilities
Explanation: An internal software error occurred.
User Action: Collect as much information as possible and submit a Software
Performance Report. (See BADLOGICPC message.)
BADLOGICPC,

internal logic error detected at PC = location

Facility: Shared by several facilities
Explanation: An internal error has occurred; location indicates the value of
the PC at the time the error was detected. The assembler does not produce
an object module or listing file.
User Action: Retry the operation. If the error is reproducible, notify your
system manager and submit a Software Performance Report; include the
address displayed with the error message and the source program.
BADLONG,

invalid data 'xxxxxxxx' at location'

Facility: Shared by several facilities
Explanation: The specified data is invalid at the given location.
User Action: None.
BAD—LRL,

record length n greater than specified longest record length

Facility: SORT, VAX SORT/MERGE Utility
Explanation: In reading the input file, SORT encountered a record longer
than the specified LRL (longest record length specified in bytes). The record
will be truncated to the LRL and sorted.
User Action: Reexecute SORT with a larger LRL.
BADMAIL,

unexpected mail received, type is 'mail-type'

Facility: NET, DECnet Test Program Protocol
Explanation: The logical link was broken.
User Action: Retry the operation.
BADMARGINS,

Margins specified incorrectly

Facility: VAX Text Processing Utility
Explanation: The margin arguments passed to FILL or SET (MARGINS,...)
are invalid. The left margin must be less than the right margin and greater
than 0. The right margin must be less than or equal to the maximum record
size for the buffer.
User Action: Correct the margin specifications and reenter your command.

2-41

Messages

BADMATCH,

invalid option for /MATCH = match-option

Facility: SEARCH, SEARCH Command
Explanation: The option specified for /MATCH is not valid. This message
is issued with an accompanying message providing more information about
why the match option is not acceptable.
User Action: Reenter the command using one of the valid match options.
BADMCKCOD,

Bad machine check code

invalid management message

Facility: NCP, Network Control Program
Explanation: The form of the data from NML could not be parsed correctly.
The information accompanying this message explains the reason.
User Action: Use the SET EXECUTOR NODE command to reestablish
a link for the executor because the reception of messages may be out of
synchronization with NML.
BADMSG,

unknown sub-message type

Facility: REM, Set Host Facility
Explanation: A system internal error has occurred.
User Action: Submit a Software Performance Report.
BADOFFSET,

image header offset is invalid

Facility: IMG ACT, Image Activator
Explanation: One of the offsets within the image header to specific parts
of the image header is invalid. This usually indicates a corrupted or invalid
image.
User Action: Relink the image.
BADOPCODE,

opcode 'xx' is unrecognized

Facility: PATCH, VAX Image File Patch Utility
Explanation: You specified an instruction that PATCH did not recognize.
Note: PATCH does not accept abbreviations for instructions. For example,
ADDL cannot be substituted for ADDL2.
User Action: Reenter the corrected command.

2-42

Messages

BADOPCODE,

opcode xxx is unknown

Facility: DEBUG, VAX/VMS Debugger
Explanation: The opcode xxx specified in the deposit command is unknown
to the debugger. If the opcode is a valid VAX MACRO opcode, then it will
have a synonymous opcode. These opcodes, such as MOVAF and MOVAL,
generate the same instruction. The debugger recognizes only one of them.
User Action: Specify a valid opcode or specify an opcode synonym that the
debugger accepts.
BADOPEN,

cannot open file 'file-spec7

Facility: NCP, Network Control Program
Explanation: There is a problem in reading from disk.
User Action: Ensure that the disk drive is operational and that no hardware
problems exist.
BAD—ORDER,

merge input is out of order

Facility: SORT, VAX SORT/MERGE Utility
Explanation: A MERGE input file is not in order on the specified key. In this
message, 'number' refers to the number of the input file in the list of input
files.
User Action: Sort the specified file and resubmit the file to MERGE.
BADOUTBAND,

invalid out of band AST specification

Facility: REM, Set Host Facility
Explanation: A protocol error has occurred.
User Action: Submit a Software Performance Report.
BADOVR,

unknown keyword on /OVERRIDE qualifier

Facility: MOUNT, MOUNT Command and INIT, INITIALIZE Volume
Command
Explanation: The command syntax for the /OVERRIDE qualifier is invalid.
User Action: Use the DCL command HELP or refer to the VAX/VMS DCL
Dictionary for the legal keywords, and reenter the command.
BADPAD,

bad format for PAD keyword on /RECORD-FORMAT qualifier

Facility: EXCHANGE, Exchange Utility
Explanation: The EXCHANGE utility found an invalid value in the PAD
option of the /RECORD-FORMAT qualifier.
User Action: Reenter the command using a correct format for /RECORDL_
FORMAT=PAD, such as /RECORD_FORMAT=PAD=%XFF.

2-43

Messages

BADPAGFILA,

Bad page file address allocated

Bad page file address deallocated

Bad page type

bad parameter

Facility: LBR, Librarian Subroutine Package
Explanation: An illegal value was passed to an LBR routine.
User Action: Check the values being passed and correct the illegal value.

2—44

Messages

BADPARAM,

bad parameter value

Facility: SYSTEM, VAX/VMS System Services
Explanation: A value specified for a system function is not valid. Several
conditions can cause this error:
1

If this message occurs as a result of a call to a file system ACP function, it
indicates that parameter list options are not valid.

2 If this message occurs as a result of a call to the Formatted ASCII Output
($FAO) system service, it indicates that a control string contained an
unknown directive.

3 If this message occurs as a result of a call to a network ACP control
function, it indicates that one of the function parameters is out of range or
has an invalid format.

4 If this message is associated with a status code returned by a request to a
DR32 interface, an attempt was made to set the data rate higher than the
rate allowed by the SYSGEN parameter /XFMAXRATE.

5 If this message is associated with a status code returned by a request
to a DR11-W interface, an odd transfer count was specified by the P2
argument.

6 If this message is associated with a status code returned by a request to
a DMP11 interface, the parameter code that was rejected is given in the
second longword of the IOSB. The parameter could have been rejected
for one of the following reasons: a) the parameter was not recognized, b)
the parameter value was not legal, c) the state was inconsistent with the
parameter value requested.
User Action: Determine the system service call that returned the error, using
the debugger if necessary. Verify that the call to the service was coded
correctly. Refer to the VAX/VMS System Services Reference Manual for coding
specifications.
BADPARAM,

improperly coded NML parameter

Facility: EVL, Event Logger
Explanation: The event receiver detected an improperly coded NML
parameter.
User Action: None. The parameter is not displayed.
BADPARAM,

insufficient shared memory to create specified data structures

Facility: SYSGEN, System Generation Utility
Explanation: The sum of all the data structures specified was more than the
available amount of shared memory.
User Action: Recalculate memory usage and reissue the command.
BADPARS,

unrecognized parameter 'parameter7

Facility: NCP, Network Control Program
Explanation: A syntax error was detected in the command input.
User Action: Reenter the command correctly.

2—45

BADPAT,

invalid data pattern received

Facility: NET, DECnet Test Program Protocol
Explanation: This message indicates a test error.
User Action: Retry the test.
BADPNAME,

illegal parameter name, must be PI through P8

Facility: CDU, Command Definition Utility
Explanation: The specified parameter name was not PI through P8.
User Action: Edit the CLD file to include a legal parameter name.
BADPRO,

invalid syntax on /PROTECTION qualifier

Facility: MOUNT, MOUNT Command and INIT, INITIALIZE Volume
Command
Explanation: The command syntax for the /PROTECTION qualifier is
incorrect.
User Action: Type the DCL command HELP SPECIFY PROTECTION or
refer to the VAX/VMS DCL Dictionary for the correct syntax, and reenter the
command.
BADPROC,

no such process

Facility: SDA, System Dump Analyzer
Explanation: The process name specified in the DCL commands SHOW
PROCESS or SET PROCESS refers to a process that does not exist.
User Action: Specify the correct process.
BADPROCNAME,

Variable used as a procedure at line 'integer'

Facility: VAX Text Processing Utility
Explanation: A variable name is being used in a PROCEDURE statement or
is being used as the name of a procedure being called.
User Action: Change the name of the procedure.
BADPROG,

Procedure definitions must precede statements in a program

Facility: VAX Text Processing Utility
Explanation: In a VAXTPU program, all procedure definitions must precede
the executable program statements.
User Action: Reorder your program so that all procedure definitions appear
before the executable statements.
BADPROGDELETE,

Cannot delete current program at line 'integer'

Facility: VAX Text Processing Utility
Explanation: The currently active program is attempting to delete itself.
User Action: Do not use DELETE 'current—program' from within the current
program.

Messages

BADPRTY,

'priority' is an invalid priority

Facility: Shared by several facilities
Explanation: Priority must be within the range of 0 to 31.
User Action: Respecify the priority within the acceptable range.
BADPSC,

transfer address in unknown psect ('decimal-number') in module
'module-name' file 'file-name'

Facility: LINK, VAX Linker
Explanation: An object module specified a nonexistent psect for the transfer
address.
User Action: Correct the source and relink.
BADQFILE,

invalid disk quota file format

Facility: SYSTEM, VAX/VMS System Services
Explanation: The quota file has an invalid format.
User Action: Delete and recreate the quota file [0,0]QUOTA.SYS with the
Diskquota Utility.
BADQHDR,

Interlocked queue header corrupted

'queue-name' is an invalid queue name

Facility: Shared by several facilities
Explanation: The queue name is not an initialized device or batch queue.
User Action: Respecify with one of the queues listed in the DCL command
SHOW QUEUE.
BADQUEUEHDR,

interlocked queue corrupted

Facility: SYSTEM, VAX/VMS System Services
Explanation: An interlocked queue is corrupted. If this message is associated
with a status code returned by a request to a DR32 interface, an INPTQ or
TERMQ interlock timeout has occurred.
User Action: Determine why the queue became corrupted and correct the
problem.

2-47

BADRANGE,

bad block address not on volume

Facility: INIT, INITIALIZE Volume Command
Explanation: A block number specified for the /BADBLOCKS qualifier is a
nonexistent block.
User Action: Verify the command line with the current bad block data and
reenter the command. If the error persists, run the Bad Block Locator Utility
to obtain the correct data.
BADRANGE,

inconsistent START and END specifications

Facility: DUMP, File Dump Utility
Explanation: In the /BLOCKS or /RECORDS qualifier, the START value was
greater than the END value.
User Action: Reenter the command specifying a valid range.
BADRCT,

Replacement and Caching Table unrecoverable I/O error

Facility: SYSTEM, VAX/VMS System Services
Explanation: The Replacement and Caching Table is unreadable or invalid.
This message applies only to devices governed by the Mass Storage Control
Protocol (MSCP). This message could indicate that the read mechanism on
the disk is defective or that the data on the disk is corrupted.
User Action: Try to copy user data from this volume to a new volume. If
this fails, contact DIGITAL field service.
BADREAD,

Read next or read prev with current record of 0, dscb: 'address7

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

unknown type of operator reply, reply = 'text'

Facility: MOUNT, MOUNT Command
Explanation: An error has occurred in OPCOM.
User Action: Retry the MOUNT request.
BADREQUEST,

Request, 'name', is not understood

Facility: VAX Text Processing Utility
Explanation: The type of information you requested from GET_INFO is not
understood or supported for that particular data type.
User Action: Reenter with a request string that is valid for the data type of
the first parameter.

Messages

BADRETURN,

RETURN occurs outside of a procedure at line 'integer7

Facility: VAX Text Processing Utility
Explanation: A RETURN statement must be inside the boundaries of a
PROCEDURE.. .ENDPROCEDURE combination.
User Action: Either remove the indicated RETURN statement, or place it
within procedural boundaries.
BADRSEIPL,

Bad IPL at entrance to report schedule event

received wrong size nice message

Facility: NCP, Network Control Program
Explanation: This message indicates a NICE protocol incompatibility.
User Action: Run against compatible NICE object or equivalent.
BADRVNWCB,

Inconsistent RVN in window map pointer

ACP tried to reference off end of bitmap

2-49

Messages

BADSCOPE,

invalid pathname xxx, SCOPE not changed

Facility: DEBUG, VAX/VMS Debugger
Explanation: The scope xxx specified in the SET SCOPE command contained
a pathname that does not exist.
User Action: Specify a valid scope.
BADSEQNUM,

invalid data sequence received

Facility: NET, DECnet Test Program Protocol
Explanation: This message indicates a test error.
User Action: Retry the test.
BADSETCNT,

incorrect number of devices in output specification

Facility: BACKUP, Backup Utility
Explanation: The output specification for a copy, restore, or compare
operation with the /IMAGE qualifier must be a list containing the same
number of devices as the number of volumes in the input volume set.
User Action: If the input is a save set, use the DCL command BACKUP/LIST
to determine how the save set was created; reenter the command.
BADSORT,

error trying to sort input file

Facility: CONVERT, Convert Utility
Explanation: This message will be accompanied by a SORT error message
that explains the error.
User Action: Correct the error described in the SORT error message and try
again.
BADSPC,

no user matched specification

Facility: AUTHORIZE, Authorize Utility
Explanation: You entered a user specification that does not match any
existing user account.
User Action: Enter a user specification that matches at least one existing user
account.
BAD—SRL,

record length 'number' is too short to contain keys

Facility: SORT, VAX SORT/MERGE Utility
Explanation: A record passed to SORT/MERGE was too short to contain all
the keys. The record is discarded, and processing continues.
User Action: Check your input records and key specification.

2—50

Messages

BADSTA,

bad stack

Facility: LIB, Run-Time Library General Procedures
Explanation: The user stack has an invalid format or cannot be accessed.
User Action: Recompile your program with the /CHECK=BOUNDS qualifier
to determine whether or not an array reference is out of bounds. If this does
not correct the problem, use the debugger to determine where your program
modifies the stack.
BADSTACK,

bad stack encountered during exception dispatch

Facility: SYSTEM, VAX/VMS System Services
Explanation: An exception condition occurred during the execution of an
image; the exception dispatcher noted an inconsistency in the call stack while
searching for condition handlers.
User Action: Check for a programming error. Locate the error that caused
the stack pointers to be overwritten or modified.
BADSTACK,

stack has been overwritten

Facility: TRACE, Traceback
Explanation: The Traceback Facility cannot display the user stack because it
has determined that the frame pointers are inconsistent.
User Action: Check for the programming error that caused the stack to be
overwritten. Correct the source program.
BADSTART,

starting block beyond maximum legal block 'number'

Facility: DUMP, File Dump Utility
Explanation: You have attempted to dump beyond the maximum block size
of the device.
User Action: Use the $GETDVI System Service to verify that the starting
block is within the legal boundary of the device.
BADSTARTPC,

cannot access start PC = xxx

Facility: DEBUG, VAX/VMS Debugger
Explanation: Location xxx is not an accessible address and therefore cannot
be executed. This is often caused when a GO command with no address
specification is entered after the program has terminated. The debugger tries
to execute an instruction at location 0, which is not accessible.
User Action: Specify a different address specification in the GO command
or, if the program has terminated, you can exit from the debugger and initiate
the program with the DCL command RUN.
BADSTRCNT,

Invalid string count found in journal file

Facility: VAX Text Processing Utility
Explanation: An invalid string was found in the journal file.
User Action: If the recovered information is sufficient, resume editing from
this point. VAXTPU has recovered as much as it can from your journal file.

2-51

Messages

BADSTRLVL,

structure level in command tables not recognized

Facility: CDU, Command Definition Utility
Explanation: Either the input tables file is corrupt or the CLI tables are not
valid.
User Action: If the input tables file is corrupt, it cannot be used again. To
determine whether the CLI tables are valid, check for incompatible versions
of the CLI and SET COMMAND.
BADSTRLVL,

unrecognized structure level for command tables

Facility: CLI, Command Language Interpreter (DCL)
Explanation: Obsolete command tables (DCLTABLES) were used.
User Action: Use the correct version of tables in the
SYS$LIBRARY:DCLTABLES file.
BADSTRUCT,

invalid value on /STRUCTURE qualifier

Facility: INIT, INITIALIZE Volume Command
Explanation: The only legal values for the /STRUCTURE qualifier are one
and two.
User Action: Correct the command.
BADSUBFCN,

invalid subfunction received

Swap VBN specified for non-process page

unknown symbol 'symbol-name'

Facility: SDA, System Dump Analyzer
Explanation: The SDA cannot identify a specified symbol.
User Action: Correct the spelling of the symbol.

2—52

Messages

BADTARGET,

target location protected, cannot perform deposit

Facility: DEBUG, VAX/VMS Debugger
Explanation: The target address of the DEPOSIT command cannot be made
writable. The DEPOSIT command cannot be performed.
User Action: None.
BADTIME,

'time-spec' is an invalid time specification

Facility: Shared by several facilities
Explanation: An invalid time specification was entered.
User Action: Respecify the time specification using the rules listed in the

VAX/VMS DCL Dictionary.
BADTYPE,

invalid sink type 'sink-name', record ignored

Facility: EVL, Event Logger
Explanation: The event receiver received an event record that had an invalid
sink type. The record was ignored.
User Action: None. This message displays the name of the sink.
BAD_TYPE,

invalid sort process specified

Facility: SORT, VAX SORT/MERGE Utility
Explanation: You passed the routine package one of the following sort type
codes:
•

Less than one or greater than four if file I/O

•

Not equal to one if record I/O

•

An invalid key word in command /PROCESS

Legal values are one through four for file I/O; nothing for record I/O; and
RECORD, TAG, INDEX, or ADDRESS for command /PROCESS parameter.
User Action: Specify a different sorting process.
BADUIC,

invalid UIC format

Facility: ACLEDIT, Access Control List Editor
Explanation: An attempt was made to enter an ACE or advance to the next
ACE field without closing off the UIC entered for the identifier. (The closing
angle or square bracket was missing.)
User Action: Enter the closing bracket, and retry the operation.
BADUIC,

invalid UIC syntax

Facility: MOUNT, MOUNT Command and INIT, INITIALIZE Volume
Command
Explanation: The command contains an invalid UIC. The group and member
portions of a UIC must both be specified and separated by a comma.
User Action: Reenter the command; use the DCL command HELP or refer to
the VAX/VMS DCL Dictionary for the correct syntax.

2-53

Messages

BADUSERDESC,

Descriptor from user routine invalid or memory inaccessible

Facility: VAX Text Processing Utility
Explanation: The routine called from CALL—USER incorrectly filled in the
return descriptor. It either is not a valid VAX descriptor or references memory
that is not accessible by your access mode.
User Action: For information on how to use descriptors, refer to the
Introduction to VAX/VMS System Routines.
BADUSRDAT,

connect/disconnect userdata invalid

Facility: NET, DECnet Test Program Protocol
Explanation: This message indicates a test error.
User Action: Retry the test.
BADUSRLEN,

connect/disconnect userdata is wrong length

Facility: NET, DECnet Test Program Protocol
Explanation: This message indicates a test error.
User Action: Retry the test.
BADVALUE,

Value' is an invalid keyword value

Facility: DSRTOC, DIGITAL Standard Runoff Table of Contents Utility
Explanation: DSR encountered an invalid keyword value.
User Action: Specify the correct value and reenter the command.
BADVALUE,

'value' is an invalid keyword value

Facility: Shared by several facilities
Explanation: An invalid value was specified for the indicated command
qualifier.
User Action: Check the command string for a spelling or syntax error. Verify
the values or syntax and reenter the command.
BADVALUE,

error in value specification

Facility: AUTHORIZE, Authorize Utility
Explanation: You specified an incorrect value.
User Action: See the VAX/VMS Authorize Utility Reference Manual for
information on value specifications.
BADVALUE,

illegal qualifier value

Facility: CDU, Command Definition Utility
Explanation: Either the qualifier value in the command string is invalid or
the qualifier value in the CLD file is incorrect.
User Action: Either enter a valid qualifier value in the command string or
modify the qualifier value contained in the CLD file.

2-54

Messages

BAD VALUE,

illegal qualifier value

Facility: MESSAGE, Message Utility
Explanation: An illegal numeric value has been used in one of several
contexts within a MSG file (for example, bad facility numbers, bad base
numbers, or a bad FAO count).
User Action: Replace the illegal value with one within the valid range.
BAD VALUE,

Integer value 'integer' is outside of specified limits

Facility: VAX Text Processing Utility
Explanation: The argument that you supplied is outside of the valid
boundaries.
User Action: Reenter your command with a valid integer value for the
argument.
BADVEC,

invalid change mode or message vector

Facility: SYSTEM, VAX/VMS System Services
Explanation: This severe error message is associated with a status code
returned from a system service request. An invalid change mode or message
vector was encountered.
User Action: Correct the change mode or message vector.
BADVOL1,

bad VOL1 ANS label

Facility: MOUNT, MOUNT Command and INIT, INITIALIZE Volume
Command
Explanation: The protection encoded on a magnetic tape volume label is
invalid or the label itself is invalid; the magnetic tape ACP cannot process the
tape. The tape is defective, it is not an ANSI-labeled tape, or the hardware
device is not reading the tape properly.
User Action: Verify the tape volume. If necessary, mount the tape as a
foreign volume and try to read it.
BADVOLACC,

invalid value on /LABEL:VOLUME—Accessibility qualifier

Facility: INIT, INITIALIZE Volume Command
Explanation: An invalid ANSI "a" character was specified in the volume
accessibility field of the tape volume label. For example, the following
command specifies an invalid ANSI "a" character - a dollar sign ($):
$INITIALIZE/LABEL:VOLUME.ACCESSIBILITY:$

User Action: Specify a valid ANSI "a" character in the single character field
of the command. The set of valid ANSI "a" characters includes: digits 0..9,
uppercase A..Z, space, and !"%&'()* + ,-./:; < = > ?
BADVOLLBL,

invalid value for ANSI tape volume label

Facility: INIT, INITIALIZE Volume Command
Explanation: You used an invalid ANSI "a" character(s) in the volume label.
The set of valid ANSI "a" characters includes: digits 0..9, uppercase A..Z,
space, and !"%&'()* + ,-./:; < = > ?
User Action: Respecify the command with valid ANSI "a" characters.

2-55

Messages

BAD WATCH,

cannot watch protect address xxx

Facility: DEBUG, VAX/VMS Debugger
Explanation: A SET WATCH command specified a protected address. Note
that you cannot place a watchpoint on a dynamically allocated variable
because these variables are stored on the stack.
User Action: Do not use watchpoint on this address.
BADWCBPT,

Bad WCB pointer in IRP

Attempt to make window less than 1 line long, no
adjustment

Facility: VAX Text Processing Utility
Explanation: You have attempted to use the built-in procedure ADJUST..
WINDOW to make a window less than one physical screen line in length.
User Action: Check the integer arguments and reenter the values. Make
the window one or more lines long if there is no status line for the window.
Make the window two or more lines long if there is a status line.
BADWINDLEN,

Window length = 'integer', must be between 'integer' and
'integer'

Facility: VAX Text Processing Utility
Explanation: You specified a window length in an argument to the built-in
procedure CREATE—WINDOW which goes beyond the screen's physical
limits.
User Action: Try your command again with a valid window length.
BAD WORD,

invalid data 'xxxx' at 'location'

Facility: Shared by several facilities
Explanation: The specified data is invalid at the given location.
User Action: Collect as much information as possible and submit a Software
Performance Report.

2-56

Messages

BASDUERRS,

basing image due to errors in relocatable references

Facility: LINK, VAX Linker
Explanation: Failure to use .ADDRESS and general addressing mode in
reference to shareable images. The linker must base the shareable image(s) to
resolve the reference(s).
User Action: The image will execute properly; however, you should correct
the specified references.
BASESYM,

base address symbol 'symbol-name' is undefined or relocatable

Facility: LINK, VAX Linker
Explanation: A symbol used to specify a base address symbolically is not
defined or is relocatable.
User Action: You must use a defined, absolute symbol for specifying
symbolic base addresses.
BASSHRBEL,

shareable image 'image-name' has base of 'address' which is below
image base of 'address'

Facility: LINK, VAX Linker
Explanation: A shareable image specified as input in the creation of a based
shareable image has a lower base address than the address specified in the
BASE= option.
User Action: None; however, note that the linker places the input shareable
image at a lower base address than the address specified in the BASE= option.
BATCHNOOPR,

no operator available to service batch request

Facility: MOUNT, MOUNT Command
Explanation: The MOUNT request aborted because the batch job required
operator assistance and no operator was present.
User Action: Call the operator and retry the request.
BATSTIPRO,

batching is still in progress

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: A user tried to end batching (updating) with a call to
SMG$END_DISPLAY_UPDATE or SMG$END_PASTEBOARD_UPDATE.
This action did not terminate batching because there were more calls to begin
batching than to end batching.
User Action: None. Some outer level routine probably still wants batching
to be in effect.
BATWASOFF,

batching was off

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: A program tried to turn off batching when batching was already
off.
User Action: Probably none. Check that there was one call to turn on
batching for each call to turn it off.

2-57

Messages

BATWAS—ON,

batching was on

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: A program tried to turn on batching when batching was already
on. This is normal in a modular environment.
User Action: None. Check that there was one call to turn on batching for
each call to turn it off.
BBFOVF,

bad block file overflow on 'device-name'

Facility: BAD, Bad Block Locator Utility
Explanation: This message indicates that during the analysis of the medium,
the SDBSF became full. It could be as a result of a large number of bad
blocks specified to the /BAD—BLOCKS qualifier or as a result of unreliable
medium.
User Action: None. The Bad Block Locator Utility terminates analysis and
leaves the SDBSF unchanged on the user's medium.
BBFWRT,

failed to write the bad block file on 'device—name'

Facility: BAD, Bad Block Locator Utility
Explanation: Failed to write an updated SDBSF on the media.
User Action: Examine the associated messages for a clue to the problem and
correct it if possible. An example of this type of error would be updating the
bad block file without exercising the medium, but the device is write locked.
BBLFIEADER,

file ('file-id') 'file-name' contains suspected bad blocks

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the specified file was marked as
containing suspected bad blocks. When the file is deleted, the blocks will be
verified and returned to the bad block file if necessary.
User Action: None.
BDPPURGERR,

Buffered datapath purge incomplete

'string' beginning

Facility: Shared by several facilities
Explanation: A program phase is being started.
User Action: None.

2-58

Messages

BEGIND,

'string' beginning at 'date'

Facility: Shared by several facilities
Explanation: A program phase began.
User Action: None.
BEGINT,

'string' beginning at 'time'

Facility: Shared by several facilities
Explanation: A program phase began.
User Action: None.
BEGNLEND,

beginning time not earlier than ending time

Facility: MONITOR, Monitor Utility
Explanation: Monitoring was requested to begin at a time that is the same
or later than the requested end time. This error occurs most frequently when
specifying a delta time specification for /BEGINNING or /ENDING. Delta
time specifications must always be preceded by a plus or minus sign. If a plus
sign is used, the entire time specification must be enclosed in double quotes.
For live monitoring and playback, delta time specifications are offset from the
current system time.
User Action: Reissue the MONITOR request with the correct time
specification(s) for /BEGINNING and/or /ENDING.
BEGOFBUF,

Attempt to move past the beginning of buffer 'buffer name'

Facility: VAX Text Processing Utility
Explanation: You have attempted to move backward past the first character
in the buffer. VAXTPU makes the first character in the buffer the current
editing position.
User Action: Stop trying to move backward. You are already positioned at
the beginning of the buffer.
BEGOFFILE,

beginning of file

Facility: SYSTEM, VAX/VMS System Services
Explanation: A backspace operation backed up to the beginning of the file.
User Action: If you are reading backwards or backspacing a tape, this
message indicates that the end-of-the-data-area has been reached. Modify the
program to recognize and correct this condition.

2-59

Messages

BEGRAN,

requested beginning time beyond range of /INPUT file

Facility: MONITOR, Monitor Utility
Explanation: Monitoring of an input recording file was requested to begin
at a time later than the ending time indicated in the file. This error occurs
most frequently when a delta time is specified for /BEGINNING. Delta time
specifications must always be preceded by a plus or minus sign. If a plus sign
is used, the entire time specification must be enclosed in double quotes. For
both live monitoring and playback, delta time specifications are offset from
the current system time.
User Action: Reissue the MONITOR request with the correct time
specification(s) for /BEGINNING and/or /ENDING.
User Action: Reissue the MONITOR request with the correct /BEGINNING
time.
BES,

bad escape sequence
Facility: RMS, VAX Record Management Services
Explanation: A terminal escape sequence is invalid.
User Action: The characters read up to the escape sequence are returned
in the user record buffer. Modify the program to detect and recognize the
condition, or reenter the input specifying the correct escape sequence.

BINCHKSUM,

a binary record failed checksum in 'record'

Facility: EXCHANGE, Exchange Utility
Explanation: While reading a formatted-binary record, the EXCHANGE
utility found a record whose computed checksum did not match the actual
checksum stored in the record.
User Action: EXCHANGE will have ignored this error, and copied the file as
if all the checksums were correct. If the output file is a formatted-binary file,
the checksum in the output record will be correct. The user should simply
check to make sure that the output file is usable.
BINRECFMT,

an illegal binary record found in 'filename'

Facility: EXCHANGE, Exchange Utility
Explanation: The EXCHANGE utility found a record in the named file which
is not a valid formatted-binary record.
User Action: Retry the command after checking whether or not the file
is really a PDP-11 formatted binary file. If it is not a binary file, use
the correct /RECORD-FORMAT qualifier. For example, the console file
CI780.BIN is assumed to be a formatted binary file, since it has the file type
.BIN. CI780.BIN is really a fixed-length file, so it should be copied with a
/RECORD_FORMAT=FIXED qualifier.
BITMAPERR,

I/O error on storage bitmap; volume locked

Facility: MOUNT, MOUNT Command
Explanation: An I/O error was encountered during a mount operation.
Existing files on the volume can be accessed but other operations, for
example, CREATE and DELETE, are not possible.
User Action: Repair the volume with the Verify Utility.

2-60

Messages

BITMAPINV,

storage bitmap is invalid, volume locked

Facility: MOUNT, MOUNT Command
Explanation: The volume's storage bit map contains invalid data.
User Action: Use the Verify Utility to repair the bit map.
BITRANGE,

bit range out of limits

Facility: DEBUG, VAX/VMS Debugger
Explanation: The EVALUATE command specified a bit field that is too wide.
User Action: The low limit of the bit field is 0 and the high limit is 31; the
maximum range is 31:0.
BKS,

bucket size too large (FAB)
Facility: RMS, VAX Record Management Services
Explanation: The bucket size specified in the FAB was larger than 63. If the
bucket size was specified as zero, the maximum record size is too large.
User Action: Verify that the call to the VAX RMS service was coded correctly.
Refer to the formulas and rules for calculating bucket size in the VAX Record
Management Services Reference Manual.

BKZ,

inconsistent bucket size for area id = 'nnn'
Facility: RMS, VAX Record Management Services
Explanation: The bucket size field specified in an allocation XAB was larger
than 63 or small for the record size.
User Action: The status value (STV) field of the FAB provides the area
identification of the XAB in error. Verify that the call to the VAX RMS service
was coded correctly. Refer to the formulas and rules for calculating bucket
size in the VAX Record Management Services Reference Manual.

BLKOBAD,

block 0 is bad, do not use 'device-name7 as a system device

Facility: BAD, Bad Block Locator Utility
Explanation: Block zero (0) is defective on the medium.
User Action: None. The device has been analyzed, contains a valid bad
block file, and can be used for data storage.
BLKDIRSYNX,

block directive syntax error

Facility: MACRO, VAX Macro Assembler
Explanation: A conditional block or a repeat block directive contained a
syntax error.
User Action: Correct the directive syntax.

2—61

Messages

BLKEXPNABS,

block expression not absolute

Facility: MACRO, VAX Macro Assembler
Explanation: The expression specifying the amount of storage to be allocated
in a .BLKA, .BLKB, .BLKD, .BLKF. .BLKG, .BLKH, .BLKO, .BLKQ, OR BLKW
directive contained an undefined symbol or was a relative expression.
User Action: Replace the expression with an absolute expression that does
not contain any undefined symbols.
BLKZERO,

block zero is bad; volume not bootable

Facility: INIT, INITIALIZE Volume Command
Explanation: This message is generated by the DCL command INITIALIZE
as a warning message. The volume cannot be bootstrapped on a PDP-11.
The volume is usable on a VAX/VMS system disk.
User Action: Note that the volume probably cannot be used as a system
volume for a VAX-11 processor model that requires access to the boot block
during a bootstrap operation.
BLKZERO,

block zero of 'device' is bad * volume not bootable

Facility: BACKUP, Backup Utility
Explanation: The boot block of the specified volume was not usable.
User Action: Note that the volume probably cannot be used as a system
volume for a VAX-11 processor model that requires access to the boot block
during a bootstrap operation.
BLN,

invalid block length for control block (RAB/FAB)
Facility: RMS, VAX Record Management Services
Explanation: An invalid value was specified in a VAX RMS FAB or RAB
block length field.
User Action: Check for a programming error. Specifically, ensure that the
control block was properly initialized and that the block length field was not
modified after initialization.

BLOCKCHECK,

block check, please report error 'error' and the following: address
= 'number', size (found,expected) = 'size' type = 'type'

Facility: EXCHANGE, Exchange Utility
Explanation: The EXCHANGE utility encountered a control block of an
unexpected format, and has terminated.
User Action: Please submit an SPR, including the error number and other
information, and the commands which resulted in the message. If the error is
only reproducible using a particular piece of media, please send a copy of the
media with the SPR (use BACKUP /PHYSICAL to make the copy).

2-62

Messages

BLOCKCHECKO,

block check, please report error 'error'

Facility: EXCHANGE, Exchange Utility
Explanation: The EXCHANGE utility failed to find a control block when one
was expected, and has terminated.
User Action: Please submit an SPR, describing the error number and the
commands which resulted in the message. If the error is only reproducible
using a particular piece of media, please send a copy of the media with the
SPR (use BACKUP /PHYSICAL to make the copy).
BLOCKCNTERR,

block count error

Facility: SYSTEM, VAX/VMS System Services
Explanation: The message indicates that the number of blocks read differs
from the number of blocks recorded in the trailer labels when a file that was
opened for a read operation was deaccessed.
User Action: This message indicates that either a noise record was read or a
valid record was not read. Either the magnetic tape is defective or a hardware
problem exists. Mount the magnetic tape on another drive/controller and
perform the same operation again. If the problem persists, the magnetic tape
is probably defective.
BLOCKCRC,

software block CRC error

Facility: BACKUP, Backup Utility
Explanation: An incorrect value occurred in the block CRC field of a save set
block. Data in the save set is corrupted.
User Action: None. Save set data has been lost.
BLOCKLOST,

block of 'file-spec' lost due to unrecoverable error

Facility: BACKUP, Backup Utility
Explanation: The Backup Utility encountered an irrecoverable error in
reading the specified save set and cannot correct the error using the
redundancy information.
User Action: None. Save set data has been lost.
BMS,

Bad margin specification: 'string'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: An illegal value has been used for a margin setting.
User Action: Correct the margin setting in the input file.

BOF,

beginning of file detected
Facility: RMS, VAX Record Management Services
Explanation: During a backspace operation, the file was positioned at the
beginning of the file before the specified number of blocks was backspaced.
The status value (STV) field in the FAB or RAB contains the number of blocks
actually spaced.
User Action: This is a warning status. Note the condition. Modify the source
program, if necessary, to detect and respond to the condition.

2—63

Messages

BOOT-F-Boot time files have too many noncontiguous pieces
Facility: BOOT, 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.
BOOT-F-Bootfile not contiguous
Facility: BOOT, System Bootstrap Facility
Explanation: The file [SYSEXEJSYSBOOT.EXE was located but is not
contiguous.
User Action: The disk you are attempting to bootstrap cannot be
bootstrapped. Obtain another copy of the system disk.
BOOT-F-I/O error reading boot file
Facility: BOOT, System Bootstrap Facility
Explanation: An uricorrectable read error occurred while the file
[SYSEXEJSYSBOOT.EXE was being read.
User Action: Try rebooting the disk. If subsequent attempts fail, obtain
another copy of the system disk.
BOOT-F-Nonexistent drive
Facility: BOOT, System Bootstrap Facility
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.
BOOT-F-Unable to locate boot file
Facility: BOOT, System Bootstrap Facility
Explanation: The file [SYSEXEJSYSBOOT.EXE could not be found.
User Action: You are attempting to bootstrap a volume that does not contain
a VAX/VMS binary system. Attempt to reboot using an appropriate disk
volume.
BOOT-F-Unexpected exception
Facility: BOOT, System Bootstrap Facility
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 local field service representative.

2-64

Messages

BOOT-F-Unexpected machine check
Facility: BOOT, System Bootstrap Facility
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 local field service representative.
BOTLINETRUNC,

Calculated new last line 'integer7, changed to 'integer'

Facility: VAX Text Processing Utility
Explanation: You have adjusted a window. The new last line of the window,
however, would have been greater than the actual number of physical screen
lines. Therefore, VAXTPU has calculated the number of available screen lines
and truncated the window accordingly.
User Action: None is required. However, you may reexecute the built-in
procedure ADJUST-WINDOW with different arguments.
BRDCST,

unable to write to console device 'sink-name'

Facility: EVL, Event Logger
Explanation: An error occurred while writing to the console sink. The event
is discarded.
User Action: None. This message displays the name of the console.
BRDESTRANG,

branch destination out of range

Facility: MACRO, VAX Macro Assembler
Explanation: The address specified in the branch instruction was too far from
the current PC. Branch instructions with byte displacements have a range of
-128 bytes to +127 bytes from the current PC. Branch instructions with word
displacements have a range of -32768 bytes to +32767 bytes from the current
PC.
User Action: Use a branch instruction with a word displacement instead
of one with a byte displacement; use a jump (JMP) instruction instead of a
branch instruction; or change the program logic so that the branch destination
is closer to the branch instruction.
BRDMSGLOST,

Broadcast queue pointer has no related entry

2-65

BREAK,

breakpoint fault at PC location, PSL = 'xxxxxxxx'

Facility: SYSTEM, VAX/VMS System Services
Explanation: A breakpoint instruction was encountered. This message
indicates an exception condition that was not handled by the condition
handler 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 correct the instruction that caused the error.
BRKNLIB,

library 'library name' not properly closed, compress or rebuild

Facility: LIBRAR, LIBRARY Command
Explanation: An error occurred during a previous update to the library that
interrupted the write operation, leaving the library in an inconsistent state.
User Action: This library can no longer be modified, but it can be read.
Uncorrupted data can be reclaimed by compressing the library or by
extracting modules and recreating a new library.
BRTOOFAR,

destination 'addr' is too far for branch operand

Facility: PATCH, VAX Image File Patch Utility and DEBUG, VAX/VMS
Debugger
Explanation: If the Patch Utility generated this message, the relative
displacement for the branch instruction is not large enough to reach the
specified destination address. If the debugger generated this message, the
DEBUG command DEPOSIT specified a branch instruction with a destination,
addr, too far from the current PC.
User Action: If the Patch Utility generated this message, correct the
destination address and retry the operation. If the debugger generated
this message, change a BRB instruction to BRW or a BRW to JMP or specify a
closer address.
BUFBLKREQ,

buffer count of block count required

Facility: SET, SET Facility
Explanation: You specified either the /BLOCKS—COUNT or /BUFFERCOUNT qualifier (with the SET RMS command) without specifying numeric
values.
User Action: Reenter the command and qualifier specifying a numeric value
for the qualifier.
BUFBYTALI,

device does not support byte-aligned transfers

Facility: SYSTEM, VAX/VMS System Services
Explanation: Some devices do not support buffers that are not aligned on
word boundaries or byte counts that are not an even number.
User Action: Recode the program using the .ALIGN macro directive or
change the byte count to an even number.

Messages

BUFFEROVF,

output buffer overflow

Facility: SYSTEM, VAX/VMS System Services
Explanation: An output string returned by a system service was larger than
the user buffer provided to receive the string, and the string was truncated.
User Action: Reissue the QIO with a larger buffer or ignore the error if you
have received enough information.
BUFFEROVF,

output buffer overflow

Facility: PSM, Print Symbiont
Explanation: This status is returned by a print symbiont format routine
indicating buffer overflow has been detected.
User Action: None.
BUFFERSLOST,

all buffers are lost

Facility: BACKUP, Backup Utility
Explanation: A software error occurred in the Backup Utility.
User Action: Submit a Software Performance Report.
BUFNOTALIGN,

buffer incorrectly aligned

Facility: SYSTEM, VAX/VMS System Services
Explanation: A table, list, or buffer area is not correctly aligned.
If this message is associated with a status code returned by a request to a
DR32 interface, the command block address in the Data Transfer Command
Table was not quadword aligned (only for start data transfer functions).
If this message is associated with a status code returned by a request to a
LPA11-K driver and this error occurs for an initialize LPA11-K request, the
initialize command table was not word-aligned.
If this error occurs for a start data transfer request, there are several possible
causes:
•

User status word (USW) not word-aligned

•

Buffer area not longword-aligned

•

Random Channel List (RCL) not word-aligned

User Action: Determine which data area is incorrectly aligned and align it on
the appropriate boundary; that is, word, longword, etc.
BUFOVF,

command buffer overflow - shorten expression or command line

Facility: CLI, Command Language Interpreter (DCL)
Explanation: A command string, including continuation lines, is longer than
the buffer used by the command interpreter to store a command.
User Action: Shorten and reenter the command; possibly enter more than
one command.

2—67

Messages

BUG,

internal RMS error condition detected
Facility: RMS, VAX Record Management Services
Explanation: An internal software error occurred in VAX RMS.
User Action: Collect as much information as possible and submit a Software
Performance Report.

BUGCHECK,

internal consistency failure

Facility: SYSTEM, VAX/VMS System Services
Explanation: The operating system noted an internal software failure.
User Action: Collect as much information as possible and submit a Software
Performance Report.
BUG_DAP,

Data Access Protocol error detected; DAP code = 'xxxxxxxx'

Facility: RMS, VAX Record Management Services
Explanation: A Data Access Protocol (DAP) violation was detected either by
VAX RMS or by the File Access Listener (FAL) at the remote node during a
DECnet-VAX file access operation.
User Action: Collect as much information as possible and submit a Software
Performance Report.
BUG—DDI,

invalid default directory

Facility: RMS, VAX Record Management Services
Explanation: An internal software error occurred in VAX RMS.
User Action: Collect as much information as possible and submit a Software
Performance Report.
BUSY,

user structure (FAB/RAB) still in use

Facility: RMS, VAX Record Management Services
Explanation: A VAX RMS operation was executed from an AST routine
while the specified FAB or RAB was still in use from non-AST level or the
user called VAX RMS illegally from executive mode at AST level or from
kernel mode and interrupted another VAX RMS operation.
User Action: Verify that the call to the VAX RMS service was coded correctly.
Use multiple I/O streams or include $WAIT requests as necessary. Because
the control block is still in use, no STS or STV value can be returned and this
status value is returned only in RO.
BVN,

Missing or illegal variable name: 'string'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: The name specification for a DSR command .VARIABLE, .IF,
.IFNOT, .ENDIF, or .ELSE is missing or illegal.
User Action: Supply the missing specification, or check to see that it is typed
correctly.

2-68

Messages

CTRL/C ignored
Facility: EDT, EDT Editor
Explanation: You attempted to use CTRL/C to interrupt an EDT operation
that EDT does not allow you to abort.
User Action: None. You cannot abort the operation.
CACLS,

the 'class-name' class cannot be added to this report

Facility: SHOW, SHOW Facility
Explanation: The class 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 or type HELP CLASSES to get a list of
available classes.
CALLFAIL,

unable to accept incoming call

Facility: PSI, VAX Packetnet System Interface
Explanation: This message indicates that VAX PSI cannot start the
destination required to accept the incoming call.
User Action: Check the parameters in the relevant destination and object
records.
CALLOVER,

Stack overflow at line 'integer'

Facility: VAX Text Processing Utility
Explanation: A nested procedure call has caused the program to exceed the
maximum call depth of 100.
User Action: Recode the program so that the nesting depth is less than 100.
CANCEL,

I/O operation canceled

Facility: SYSTEM, VAX/VMS System Services
Explanation: An input or output operation was canceled by the $CANCEL
system service before it started. Usually, the request is canceled at the image's
request. If this message is associated with a status code returned by a request
to a DR11-W interface and if the $CANCEL system service is requested while
a block mode request is active, then the driver performs a device reset to the
DR11-W.
User Action: None. The operating system does not normally display this
message.
CANCELED,

command was canceled by keyboard action

Facility: EXCHANGE, Exchange Utility
Explanation: The EXCHANGE utility received a CTRL/C character while
processing a command, it has canceled the command and returned to the
prompt.
User Action: No action is necessary.

2-69

CANCELQUIT,

QUIT canceled by request

Facility: VAX Text Processing Utility
Explanation: Execution of the built-in procedure QUIT was canceled when
you responded "no" to the RE ALLYQUIT question.
User Action: None.
Cannot allocate sufficient memory
Facility: DISKQUOTA, Diskquota Utility
Explanation: DISKQUOTA failed to allocate working storage for the
operation.
User Action: Increase the VIRTUALPAGCNT system parameter (with the
SYSGEN Utility) or have your page file quota increased so that the REBUILD
command has sufficient space to build the usage table.
Cannot examine quota file entry
Facility: DISKQUOTA, Diskquota Utility
Explanation: This message is issued with other messages.
User Action: Take corrective action based on the accompanying messages.
Cannot set terminal type from change mode
Facility: EDT, EDT Editor
Explanation: You attempted to issue a SET TERMINAL {VT100IVT52IHCPY)
command while working in a screen mode.
User Action: In order to change the terminal type with the SET TERMINAL
command, you must shift to line mode.
CANTBAL,

can't balance last page

Facility: DSRINDEX, DIGITAL Standard Runoff Indexing Utility
Explanation: An internal error has occurred.
User Action: Submit a Software Performance Report. Please include the file
that caused the error.
CANTLOCMAC,

can't locate macro in macro libraries

Facility: MACRO, VAX Macro Assembler
Explanation: A macro name specified in a .MCALL directive was not defined
in the macro libraries searched.
User Action: Specify, in the DCL command MACRO, the macro library that
defines the macro.

Messages

CAPTIVE,

qualifier not allowed in captive accounts

Facility: LOGIN, Login Processor
Explanation: You attempted to change the default disk, CLI or login
command procedure while logging in to a captive account, which is not
allowed.
User Action: Do not specify the /DISK, /COMMAND, or /CLI qualifiers
while attempting to log in to this account.
CAPTIVE,

this command cannot be executed; Your account is CAPTIVE

Facility: MAIL, Personal Mail Utility
Explanation: User attempted to issue a SPAWN command and the user's
account is CAPTIVE.
User Action: Contact your system manager if you feel your account should
not be CAPTIVE.
CARDS,

cards

CASE limits distance too large at line 'integer'

Facility: VAX Text Processing Utility
Explanation: Your CASE statement contains FROM...TO limits that exceed
the maximum number allowed.
User Action: Break your CASE range into multiple, smaller CASE statements.
CBT,

insufficient contiguous space, file copied non-contiguously
Facility: Shared by several facilities
Explanation: There was insufficient disk space to copy the file contiguously;
the file has been copied but the output file may not be contiguous.
User Action: None.

CCF,

cannot close file
Facility: RMS, VAX Record Management Services
Explanation: The system could not close an output file during a call for I/O
run-down.
User Action: The user-specified buffer contains the device ID, directory ID,
and file ID of the file that could not be closed. Note the condition. Modify
the source program, if necessary, to detect and respond to the condition.

2-71

Messages

CCR,

cannot connect RAB
Facility: RMS, VAX Record Management Services
Explanation: VAX RMS could not connect a record access block (RAB) to the
specified file access block (FAB). This error usually results from one of the
following actions: specifying block I/O (setting the RAB$V_BIO option of the
RAB$L_ROP field) with multistreaming (setting the FAB$V_MSE option of
the FAB$B_SHR field); attempting to connect multiple record access blocks
to a file access block when the multistreaming option (FAB$V_MSE) of the
file sharing field (FAB$B_SHR) has not been set; or attempting a DECnet
operation when the multistreaming option is set. The multistreaming option
is not supported for DECnet operations.
User Action: Note which condition is causing the error and modify your
source program accordingly.

CD A,

cannot deliver AST

Facility: RMS, VAX Record Management Services
Explanation: Either the user program has exceeded its AST quota, or not
enough system dynamic memory is available for VAX RMS to deliver an error
or successful completion AST, and the user program has disabled resource
wait mode.
User Action: The status value (STV) field in the FAB or RAB contains the
status code of the operation that Take corrective action based on this status
code. Raise the process's AST quota and/or modify the source program, if
necessary, to detect and respond to the condition.
CEBREFNEG,

Negative reference count on shared memory CEB

Comma expected, missing: 'string7

Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: A required comma is missing from the command string.
User Action: Supply the missing comma.
CENTRL,

central

2-72

Messages

CHAINW,

chained write status

Facility: SYSTEM, VAX/VMS System Services
Explanation: The block just received by the 3271 Protocol Emulator is part
of a chained write sequence.
User Action: Normally, the information received by the 3271 Protocol
Emulator in a chained write sequence is appended to the information received
in the previous sequence. Your action will vary for each application.
CHAN,

error assigning or deassigning channel

Facility: CNF, NI Configurator
Explanation: An error occurred while assigning or deassigning a channel.
User Action: See the accompanying message to determine the appropriate
action.
Change mode can be entered only from a terminal
Facility: EDT, EDT Editor
Explanation: You cannot enter change mode (keypad, nokeypad, or hardcopy
change mode) from a network, a batch command file, or a startup command
file.
User Action: Use the EDT command SET MODE CHANGE in the startup
file to make EDT enter change mode at the end of the startup file.
CHG,

invalid key change in $UPDATE (CHG not set)

Facility: RMS, VAX Record Management Services
Explanation: A VAX RMS $UPDATE operation specified a record that
contained one or more changed key values for keys that do not have the
'keys may change' attribute set in the XAB key option flag.
User Action: Reorganize the file and specify the 'keys may change' attribute
to be set in the XAB key option flag, if necessary. Or modify the source
program to detect and respond to the condition.
CHK,

bucket format check failed for VBN = 'nnn'
Facility: RMS, VAX Record Management Services
Explanation: VAX RMS detected a corrupted bucket in an indexed file. The
bucket address check or bucket checksum was incorrect.
User Action: Reorganize the file, if possible; otherwise recreate the file. The
status value (STV) field of the FAB or RAB contains the starting virtual block
number of the bucket in error.
This error is caused by hardware errors, VAX RMS or system software errors,
or inadvertent modifications of files by non-RMS programs.

2-73

CHKALTHOME,

invalid alternate home block, VBN 'n', RVN 'n'

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the alternate home block at the
specified virtual block of the index file on the specified relative volume was
corrupted.
User Action: None. The alternate home block is refreshed from the primary
home block.
CHKPRIHOME,

invalid primary home block, VBN 'n', RVN 'n'

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the primary home block at the
specified virtual block of the index file on the specified relative volume was
corrupted.
User Action: None. The Verify Utility reconstructs the block.
CHKSCB,

invalid storage control block, RVN 'n'

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the storage control block on the
specified relative volume was corrupted.
User Action: None. The Verify Utility reconstructs the block.
CHMONIS,

Change mode instruction while on interrupt stack

CHM vector bits <1:0> not 0

Messages

CHN,

assign channel system service request failed

Facility: RMS, VAX Record Management Services
Explanation: VAX RMS failed to assign a channel to a device specified for an
input or output operation. This message is usually accompanied by a system
message that indicates the reason for the failure.
User Action: Take corrective action based on the associated system status
code contained in the status value (STV) field of the FAB.
If the error results from the DCL command OPEN, or following the DCL
command @ (execute procedure) or the DCL command RUN, verify that the
volume containing the specified file is online and mounted.
CINBAD,

connect not accepted/rejected as expected

Facility: NET, DECnet Test Program Protocol
Explanation: This message indicates a test error.
User Action: Ensure that the correct DTRECV or equivalent is available at
the target node.
CINREJ,

connect aborted, nsp reason is 'number7

Facility: NET, DECnet Test Program Protocol
Explanation: The logical link to DTRECV could not be established.
User Action: Interpret the Network Services Protocol (NSP) reason.
CINREJ,

unable to complete network $assign

Facility: NCP, Network Control Program
Explanation: The logical link to the NICE object failed.
User Action: Ensure that the configuration database is consistent with the
User Authorization File and that .LOG files can be written to the default
directory. Also, check that enough processes can be created.
CIPORT,

Fatal error detected by Cl port driver (PADRIVER)

2-75

Messages

CJFERR,

journaling error; volume dismounted to ensure data integrity

Facility: MOUNT, MOUNT Command
Explanation: The attempt to activate the Recovery Unit Journal (RUJ) on the
volume failed. Because the RUJ might contain an active recovery unit, the
volume is dismounted to minimize the danger of corrupting the data on the
volume. This message is usually followed by another message that describes
the error condition that caused RUJ activation to fail.
User Action: Correct the error conditon and reissue the MOUNT command,
or reissue the MOUNT command including the /NOJOURNAL qualifier.
With the latter approach, MOUNT will not attempt to activate the RUJ. This
approach removes the symptom but not the cause of the failure and may
leave the volume in an inconsistent state.
CJL,

Can't output line correctly—margins too narrow. Line will not be justified
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: The text and spacing are greater than the number of character
positions available between the margins.
User Action: Truncate the line or use the Break flag to divide it.

CLASDISAB,

class disabled

Facility: MONITOR, Monitor Utility
Explanation: One or more of the specified class-names is not a valid
MONITOR class.
User Action: Check the list of valid MONITOR classes by issuing the DCL
command HELP MONITOR parameters. Reissue the MONITOR command
requesting only valid classes.
CLASMISS,

requested class record missing from /INPUT file

Facility: MONITOR, Monitor Utility
Explanation: The class data records in the input recording file do not match
information in the header for the file. This can only occur if the input file has
been corrupted in some way.
User Action: If you can demonstrate that a MONITOR recording file can
be created with one MONITOR request, and then, using that file as input,
immediately run a second MONITOR request that produces this message,
please submit a Software Performance Report.
CLASNP,

some requested class(es) not present in /INPUT file

Facility: MONITOR, Monitor Utility
Explanation: One or more of the requested MONITOR classes was not
present in the specified input recording file. This situation may result from
having specified an incorrect /INPUT file.
User Action: The MONITOR request continues execution, monitoring only
those requested classes that are present in the input recording file. If an
incorrect /INPUT file has been specified, reissue the command, specifying the
correct /INPUT file.

2-76

Messages

CLASUNK,

some requested class(es) have file structure levels incompatible with
the current version of MONITOR

Facility: MONITOR, Monitor Utility
Explanation: One or more of the requested MONITOR classes in the
specified input recording file has a structure level incompatible with the
current version of MONITOR. This situation may result from reading a file
that was created by a version of MONITOR newer than the one currently
running.
User Action: No action is required. The MONITOR request will continue to
execute, monitoring only those requested classes that are compatible with the
version of MONITOR currently running.
CLIERR,

CLI error parsing command line

Facility: PATCH, VAX Image File Patch Utility
Explanation: The command line that invokes PATCH was incorrectly
entered.
User Action: Reenter the command line correctly.
CLIFAIL,

error activating command interpreter 'interpreter'

Facility: LOGIN, Login Processor
Explanation: An error occurred while attempting to invoke the command
interpreter for your process. An accompanying message will provide more
information.
User Action: Correct the problem described by the accompanying message,
and try again.
CLIFRCEXT,

CLI forced exit

Facility: SYSTEM, VAX/VMS System Services
Explanation: The command interpreter forced an image to terminate
abnormally. This message is displayed by the debugger when an image
is interrupted by CTRL/Y and another command is entered. The debugger
displays this message indicating the image is terminated.
User Action: None. The message is informational.
CLIMISMATCH,

CLI type of image does not match /CLI qualifier

Facility: CDU, Command Definition Utility
Explanation: CDU returns this message when you try to use the SET
COMMAND/CLI=CLI-type command to modify command tables created
by a CLI-type other than the one you have specified.
CLIPROT,

error protecting command interpreter pages

Facility: LOGIN, Login Processor
Explanation: An error occurred while trying to protect the command
interpreter pages. An accompanying message will provide more information.
User Action: Correct the problem described by the accompanying message,
and try again.

2-77

CLIQUAL,

/CLI qualifier value conflicts with CLI type in tables

Facility: CDU, Command Definition Utility
Explanation: The CDU outputs this message when you try to use the SET
COMM AND/CLI=cli-type command to modify command tables created by a
CLI-type other than the one you have specified.
User Action: Specify different command tables, generated by the appropriate
CLI, or use a different CLI-type in the command.
CLISYMTBL,

error creating space for command interpreter symbol table

Facility: LOGIN, Login Processor
Explanation: An error occurred while trying to create virtual address space
for the command interpreter symbol table. An accompanying message will
provide more information.
User Action: Correct the problem described by the accompanying message,
and try again.
CLOSEDEL,

error deleting 'file-name7

Facility: Shared by several facilities
Explanation: An error occurred while a file was being closed after a delete
operation. This message is usually accompanied by a VAX RMS message
indicating the reason for the failure.
User Action: Take corrective action based on the associated message.
CLOSEERR,

an error occurred closing 'file-name'

Facility: EXCHANGE, Exchange Utility
Explanation: The EXCHANGE utility received an error from RMS while
trying to close a Files-11 file.
User Action: This message will be followed by one or two error messages
reporting the actual condition discovered by RMS. Take corrective action
suggested by the RMS error messages, then retry the command.
CLOSEERR,

error closing 'file-spec'

Facility: SET, SET Facility
Explanation: An error occurred while trying to close a file whose
characteristics have just been set. This message is accompanied by a message
explaining why the file could not be closed.
User Action: Respond to the accompanying message.
CLOSEFILE,

error closing event file 'file-id'

Facility: EVL, Event Logger
Explanation: An error occurred while closing an event file.
User Action: None. This message displays the name of the file.

Messages

CLOSEFOREIGN,

an error occurred closing the volume 'volume'

Facility: EXCHANGE, Exchange Utility
Explanation: The EXCHANGE utility received an error from RMS while
trying to close a connection to a foreign-mounted volume.
User Action: This message will be followed by one or two error messages
reporting the actual condition discovered by RMS. Take corrective action
suggested by the RMS error messages, then retry the command.
CLOSEIN,

error closing input file

Facility: Shared by several facilities
Explanation: During a VAX RMS operation, an error was encountered while
closing an input file. This message is usually accompanied by a VAX RMS
message indicating the reason for the failure.
User Action: Take corrective action based on the associated message.
CLOSEIN,

Error closing input file 'file-spec'

Facility: VAX Text Processing Utility
Explanation: A VAX RMS error occurred while closing the specified input
file. The message should be accompanied by a VAX RMS message indicating
the reason for the error.
User Action: Follow the recovery procedure for the specified VAX RMS
message.
CLOSEIN,

unable to close input

Facility: ACCOUNTING, Accounting Utility
Explanation: During a VAX RMS operation, an error was encountered while
closing an input file. This message is usually accompanied by a VAX RMS
message indicating the reason for the failure.
User Action: Take corrective action based on the associated message.
CLOSEMON,

error disconnecting monitor process 'sink-name'

Facility: EVL, Event Logger
Explanation: An error occurred while disconnecting a monitor process.
User Action: None. This message displays the name of the monitor program.
CLOSEOUT,

Error closing output file 'file-spec'

Facility: VAX Text Processing Utility
Explanation: A VAX RMS error occurred while closing the specified output
file. The message should be accompanied by a VAX RMS message indicating
the reason for error.
User Action: Follow the recovery procedure for the specified VAX RMS
message.

2-79

CLOSEOUT,

error closing output file

Facility: Shared by several facilities
Explanation: During a VAX RMS operation, an error was encountered while
closing an output file. This message is usually accompanied by a VAX RMS
message indicating the reason for the failure.
User Action: Take corrective action based on the accompanying message.
CLOSEOUT,

unable to close output

Facility: ACCOUNTING, Accounting Utility
Explanation: During a VAX RMS operation, an error was encountered while
closing an output file. This message is usually accompanied by a VAX RMS
message indicating the reason for the failure.
User Action: Take corrective action based on the accompanying message.
CLSERR,

close error code of 'xx' on file 'file-spec'

Facility: PATCH, VAX Image File Patch Utility
Explanation: The $CLOSE request failed due to the error represented as xx.
User Action: Correct the error (represented as xx) and retry.
CLSTBLERR,

device class value, 'value' not in class tables

Facility: ERF, ANALYZE/Error Log Utility
Explanation: The specified class value is unsupported.
User Action: Submit a Software Performance Report.
CLUBELBAS,

base address of 'address' for cluster 'cluster-name' is below image
base of 'address'

Facility: LINK, VAX Linker
Explanation: In the creation of a based shareable image, a cluster was
specified with a lower base address than the address specified in the BASE=
option.
User Action: Specify a base address for the cluster that is higher than the
address specified in the BASE= option.
CLUEXIT,

Node Exiting Cluster

Facility: System Bugcheck
Explanation: To avoid partitioning of the VAXcluster, this system exited
the VAXcluster by crashing. Generally, this is a normal condition. If the
condition persists, this processor is most probably configured incorrectly into
two distinct VAXclusters. 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.
Explanation: Insure that the VAXcluster is properly configured.

Messages

CLUSTER,

unsuitable cluster factor

Facility: INIT, INITIALIZE Volume Command
Explanation: The cluster size specified for a DCL command INITIALIZE is
either too small or too large for the volume. The maximum cluster size for
any volume is 1/100 the size of the volume; the minimum size is calculated
with the formula:
disk size
(255 x 4096)

User Action: Recalculate a cluster size for the volume that is within the valid
range and reenter the command.
CLUSTER,

unsuitable cluster factor for 'device'

Facility: BACKUP, Backup Utility
Explanation: During an attempt to initialize an output volume, the Backup
Utility found that the cluster factor was too large or too small for the specified
device.
User Action: If the input is a save set, use the BACKUP/LIST command to
determine the volume initialization parameters of the input volumes. Refer
to the description of the DCL command INITIALIZE, determine a suitable
cluster factor, and initialize the output volumes using the DCL command
INITIALIZE. Then, reenter the command specifying the /NOINITIALIZE
qualifier.
CMDCAN,

command canceled

Facility: NCP, Network Control Program
Explanation: CTRL/Z was typed in response to a prompt. This cancels the
current command and returns you to the NCP> prompt.
User Action: Retry the operation.
CMDERR,

I/O error reading commands

Facility: NCP, Network Control Program
Explanation: RMS returned an error while reading commands from
SYS$INPUT. The RMS error message describes the error condition.
User Action: Take corrective action based on the accompanying RMS
message.
CMDINPUT,

error reading command input

Facility: LOGIN, Login Processor
Explanation: An error occurred while attempting to read the input file. An
accompanying message will provide more information. The most common
cause is a read timeout while trying to obtain the username and/or password.
User Action: Correct the problem described by the accompanying message,
and try again.

2—81

Messages

CMDLIN,

command line segment in error 'error'

Facility: DIFF, DIFFERENCES Command
Explanation: Part of the command line is syntactically incorrect.
User Action: Specify the correct syntax in the command line.
CMDNOTFND,

command not found - use RECALL/ALL to display saved
commands

Facility: CLI, Command Language Interpreter (DCL)
Explanation: The command that you tried to find using RECALL was not
found.
User Action: Use the RECALL/ALL to display all the saved commands and
then modify and reenter your RECALL command.
CMDSYNTAX,

command line syntax error

Facility: LINK, VAX Linker
Explanation: A command syntax error was detected by the command
interpreter.
User Action: Reenter the command correctly.
CMDSYNTAX,

command syntax error

Facility: DIFF, DIFFERENCES Command
Explanation: The syntax of the DIFFERENCES command line is incorrect.
User Action: Use the DCL command HELP or refer to the VAX/VMS
DCL Dictionary to determine the correct command syntax and reenter the
command.
CMDTOOLNG,

command line too long

Facility: INSTALL, Install Utility
Explanation: The command line contains too many characters.
User Action: Shorten the command line, possibly with logical names, and
reenter.
CMDTOOLONG,

command line too long in options file 'file-name'

Facility: LINK, VAX Linker
Explanation: An options file line was too long.
User Action: Shorten the line and relink.

2-82

Messages

CMODSUPR,

change mode to supervisor trap, code = 'nnn', PC = 'location', PSL
= 'xxxxxxxx7

Facility: SYSTEM, VAX/VMS System Services
Explanation: An image attempted to execute a change mode to supervisor
instruction, but the image did not have a change mode handler declared. 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.
The code displayed in the message is the change mode code specified in the
instruction.
User Action: Examine the PC and virtual address displayed in the message
to determine which instruction caused the error.
CMODUSER,

change mode to user trap, code = 'nnn7, PC = 'location7, PSL =
'xxxxxxxx7

Facility: SYSTEM, VAX/VMS System Services
Explanation: An image attempted to execute a change mode to user
instruction, but the image did not have a change mode handler declared.
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 which instruction caused the error.
CMPOUTF11,

/COMPARE requires save set as first input

Facility: BACKUP, Backup Utility
Explanation: In a compare operation between a save set and a disk volume,
you must specify the save set as the first input and the disk volume as the
second input.
User Action: Correct and reenter the command.
CNF,

Character string expected, not found: 'string7
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: A required character string is missing.
User Action: Supply the missing string.

CNFQUAVAL,

conflicting qualifier values for 'qualifier7, 'qualifier7

Facility: ERF, ANALYZE/Error Log Utility
Explanation: Two or more conflicting qualifiers were specified.
User Action: Use the DCL HELP command or refer to the VAX/VMS DCL
Dictionary to determine the qualifiers in conflict and reenter the command.
CNS,

Command not supported: 7n7
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: The command is not supported by this version of DSR; in this
case n is an internal DIGITAL number.
User Action: Remove or replace the command.

2—83

Messages

CNTERR,

connect error code of 'xx' on file 'file-spec7

Facility: PATCH, VAX Image File Patch Utility
Explanation: A VAX RMS $CONNECT request failed due to the error
represented as xx.
User Action: Correct the error (represented as xx) and retry the request.
CNTRLY,

Are you repeating ~Y to abort the remote session on node 'node-name7

Facility: REM, Set Host Facility
Explanation: This message provides an opportunity to terminate the
connection if logging out is not possible on the remote node.
User Action: Enter a YES or NO answer.
CNVRTING,

'library file-spec' is a copy of 'old library file-spec'

Facility: LIBRAR, LIBRARY Command
Explanation: This message is generated by the DCL command LIBRARY.
The specified modification to a Version 1.0 library automatically converts it to
the new library format.
User Action: None. This message is informational.
CNXMGRERR,

Error detected by Connection Manager

Can't open binary output file 'file-spec'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: DSR cannot create the .BRN file required to generate a table of
contents from the titles and header levels.
User Action: Check to see if you have write access to your current default
directory. If the problem continues, notify the system manager.

COD,

invalid or unsupported type field in XAB at 'location'

Facility: RMS, VAX Record Management Services
Explanation: The XAB at the indicated address contains an invalid type code
field, or the XAB is not valid.
User Action: The status value (STV) field of the FAB provides the address
of the XAB in error. Verify that the call to the VAX RMS service was coded
correctly.

2-84

Messages

COF,

Can't open footnote work file 'filename'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: DSR cannot create the temporary file required to process the
footnote information.
User Action: Check to see if you have write access to your current default
directory and enough quota. If the problem continues, notify the system
manager.

COI,

Can't open input file 'filename'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: The input file specification is erroneous, the file is nonexistent,
or you do not have read access to the file.
User Action: Check the file specification for errors, or check to see if you
have read access to the file. If the problem continues, notify the system
manager.

COLLERR,

error during data collection

Facility: MONITOR, Monitor Utility
Explanation: An unexpected error occurred while collecting the requested
MONITOR data. More information can be obtained by examining the linked
message that follows this one.
User Action: Correct the error indicated by the linked message and rerun
the MONITOR command. If the linked message is NOPRIV, it may indicate
that the Monitor Utility was not installed with the required privileges. Please
report such a problem to the system manager.
COMBCLU,

cannot combine multiple classes with the cluster class

Facility: MONITOR, Monitor Utility
Explanation: The CLUSTER class cannot be combined with other classes.
User Action: Reenter your command with only the CLUSTER class listed.
COMCOD,

compilation 'error' in module 'module-name' file 'library file-spec'

Facility: LIBRAR, LIBRARY Command
Explanation: This warning message is generated by the DCL command
LIBRARY. The object module you are inserting contains a compilation error,
warning, or an illegal compilation code.
User Action: Recompile the module before reentering the command line.
COMMA,

requested value is terminated by a comma

Facility: CLI, Command Language Interpreter (DCL)
Explanation: The returned value is terminated by a comma, implying that
additional values are in the list.
User Action: None.

2—85

Messages

Command buffer exhausted
Facility: EDT, EDT Editor
Explanation: The string of change mode commands exceeds 255 characters.
User Action: Divide the string into several lines and reenter the command.
Command buffer exhausted during XLATE command processing
Facility: EDT, EDT Editor
Explanation: You have put too many characters in your XLATE procedure.
EDT can handle only 255 characters per command line.
User Action: Enter fewer characters.
Command file could not be closed
Facility: EDT, EDT Editor
Explanation: The startup command file cannot be closed. The appropriate
system message provides more information on the nature of the problem.
User Action: Correct the problem indicated by the accompanying message.
Command file could not be opened
Facility: EDT, EDT Editor
Explanation: The command file given in the command line cannot be
opened. EDT will display an associated file system message for the error.
User Action: Correct the problem indicated by the file system message.
Command file does not exist
Facility: EDT, EDT Editor
Explanation: The command file parameter in the command line does not
exist in the specified directory.
User Action: Reenter the command specifying a command file parameter that
does exist in the specified directory.
Command syntax error
Facility: DISKQUOTA, Diskquota Utility
Explanation: There is a syntax error in your command line.
User Action: Refer to the VAX/VMS Disk Quota Utility Reference Manual for
syntax information and correct the command syntax error.

2-86

Messages

COMMHARD,

communications hardware error detected

Facility: SYSTEM, VAX/VMS System Services
Explanation: A hardware error has occurred on the DUP11, the local modem,
or the line between the modem and the DUP11, while the 3271 Protocol
Emulator was active.
On a write request, there was a UNIBUS timeout returned by the DEUNA
hardware.
User Action: Check the lines for obvious hardware problems, for example, a
disconnected plug. If the error still occurs, consult a DIGITAL Field Service
representative.
The UNIBUS should be checked to make sure it is not overloaded and that all
devices on the UNIBUS are working properly.
COMPARED,

compared 'file-spec'

Facility: BACKUP, Backup Utility
Explanation: The Backup Utility has successfully completed a compare
operation. This message is displayed only when the /LOG command qualifier
is used.
User Action: None.
COMP AT,

compatibility mode fault (code 'nnn') at PC 'location', PSL = 'xxxxxxxx'

Facility: SYSTEM, VAX/VMS System Services
Explanation: An RSX-11M image attempted to execute an illegal instruction,
indicated by one of the following codes:
Code

Meaning

Reserved instruction execution

BPT instruction executed

IOT instruction executed

EMT instruction executed

TRAP instruction executed

Illegal instruction executed

Odd address fault

TBIT trap

User Action: Check for a programming error and make any necessary
corrections.
COMPILED,

Compilation completed without errors

Facility: VAX Text Processing Utility
Explanation: The execution of the built-in procedure COMPILE has been
successfully completed; that is, a procedure, string, or buffer has been
compiled without warnings or errors.
User Action: None.

2-87

Messages

COMPILEFAIL,

Compilation aborted at line 'integer'

Facility: VAX Text Processing Utility
Explanation: A syntax error exists in the program you are trying to compile.
The compilation of the program was prematurely terminated.
User Action: Correct the syntax error and recompile your program.
COMPLETE,

processing complete 'string'

Facility: DSRTOC, DIGITAL Standard Runoff Table of Contents Utility
Explanation: The DSR Table of Contents Utility has completed processing
the indicated input file.
User Action: None. This message is informational.
COMPLX,

expression too complex - simplify

Facility: CLI, Command Language Interpreter (DCL)
Explanation: The command interpreter cannot analyze an arithmetic
expression in a command, because it contains too many operators and/or
parentheses.
User Action: Shorten the expression and reenter the command. If necessary,
execute more than one command.
COMREMJBC,

error communicating with another job controller

Facility: JBC, Job Controller
Explanation: The job controller encountered an error communicating with
a job controller on another processor in a VAXcluster. The accompanying
message provides additional information.
User Action: Take action based on the accompanying message.
CON ABORT,

connection to node 'node-name' aborted by CTRL/C

Facility: MAIL, Personal Mail Utility
Explanation: The user typed CTRL/C while MAIL was attempting to connect
to the specified node. The transmission of the message is aborted.
User Action: None.
CONCAT,

requested value is terminated by a plus sign

Facility: CLI, Command Language Interpreter (DCL)
Explanation: The returned value is concatenated to the next value with a
plus sign, implying that additional values are in the list.
User Action: None.
CONCEALED,

logical device name concealed physical device name

Facility: SYSTEM, VAX/VMS System Services
Explanation: This alternate success status indicates that the system service
completed successfully, and the device name that was supplied as input to
the service translated to a concealed device.
User Action: None.

2-88

Messages

CONERR,

connect error

Facility: AUTHORIZE, Authorize Utility
Explanation: This message is issued with other messages.
User Action: Take corrective action based on the accompanying messages.
CONFATTR,

conflicting attributes in definition

Facility: CDU, Command Definition Utility
Explanation: The CLD file has conflicting attributes. Attributes are mutually
exclusive (for example, a CLD file can name both an image and a routine).
User Action: Remove one of the mutually exclusive attributes from the CLD
file.
CONFBASADR,

conflicting base address for image 'image-name7 base of 'address'
in file 'file-name' conflicts with base of 'address' in file 'file-name'

Facility: LINK, VAX Linker
Explanation: A shareable image contained in two other based shareable
images, both of which were included in the link, is found to be at two
separate virtual addresses.
User Action: Either (1) correct one or both of the based shareable images
giving the shareable image in question the same base address in both images,
or (2) make both based shareable images position independent.
CONFCON,

CONCATENATE has already been specified

Facility: CDU, Command Definition Utility
Explanation: CDU encountered a NOCONCATENATE clause after
processing a CONCATENATE clause in the same value definition.
NOCONCATENATE and CONCATENATE clauses cannot be specified in
the same value definition.
User Action: Edit the CLD file so that each value definition does not contain
both CONCATENATE and NOCONCATENATE clauses.
CONFDEFREQ,

only one DEFAULT or REQUIRED clause is allowed

Facility: CDU, Command Definition Utility
Explanation: CDU encountered more than one DEFAULT or REQUIRED
clause in a single value definition. Only one DEFAULT or REQUIRED clause
is allowed per value definition.
User Action: Edit the CLD file so that each value definition does not contain
more than one DEFAULT or REQUIRED clause.
CONFDEL,

'file-name', delete? (Y or N):

Facility: Shared by several facilities
Explanation: This message requests interactive confirmation before deleting
the indicated file.
User Action: Type Y if you want the file deleted, and type N if you do not
want it deleted.

2-89

Messages

CONFDIS,

a DISALLOW clause has been specified

Facility: CDU, Command Definition Utility
Explanation: CDU encountered a NODISALLOWS clause after a DISALLOW
clause was processed in a single verb/syntax definition. NODISALLOWS
cannot be specified in a verb/syntax definition in which DISALLOWS was
previously specified.
User Action: Edit the CLD file so that each verb/syntax definition does not
contain both DISALLOW and NODISALLOWS clauses.
CONFFAC,

facility definition conflicts with previous definition

Facility: MESSAGE, Message Utility
Explanation: The same facility name or facility number was specified for two
different facilities.
User Action: Reenter the facility definitions so that each facility name
corresponds to one facility number.
CONFIXMEM,

conflicting virtual memory requirement for fixup section for image
'image-name' Restructure image or eliminate based shareable
images

Facility: LINK, VAX Linker
Explanation: The linker was unable to allocate virtual memory for the fixup
section because a based shareable image was taking up the space.
User Action: Restructure the set of shareable images to be nonbased, or leave
enough space between them for the object modules.
CONFLICT,

illegal combination of command elements - check documentation

Facility: CLI, Command Language Interpreter (DCL)
Explanation: Two or more qualifiers, keywords, or parameters that cannot be
used in combination were used in the same command line.
User Action: Remove the offending element.
CONFMEM,

conflicting virtual memory requirement at 'address' for 'decimalnumber' pages in cluster 'cluster-name'

Facility: LINK, VAX Linker
Explanation: Virtual memory required for a cluster has already been
allocated.
User Action: Correct and relink.
CONFNEG,

NEGATABLE has already been specified

Facility: CDU, Command Definition Utility
Explanation: CDU has encountered a NONNEGATABLE clause after
processing a NEGATABLE clause in the same keyword definition. A
NEGATABLE clause and a NONNEGATABLE clause cannot be specified
in the same keyword definition.
User Action: Edit the CLD file so that each keyword definition does not
contain both NEGATABLE and NONNEGATABLE clauses.

2-90

Messages

CONFNOCON,

NOCONCATENATE has already been specified

Facility: CDU, Command Definition Utility
Explanation: CDU encountered a CONCATENATE clause after processing a
NOCONCATENATE clause in the same value definition. CONCATENATE
and NOCONCATENATE clauses cannot be specified in the same value
definition.
User Action: Edit the CLD file so that each value definition does not contain
both CONCATENATE and NOCONCATENATE clauses.
CONFNODIS,

NODISALLOWS has already been specified

Facility: CDU, Command Definition Utility
Explanation: CDU encountered a DISALLOW clause after a NODISALLOWS
clause was encountered in a single verb/syntax definition. DISALLOW
cannot be specified in a verb/syntax definition in which NODISALLOWS was
previously specified.
User Action: Edit the CLD file so that each verb/syntax definition does not
contain both NODISALLOWS and DISALLOW clauses.
CONFNONNEG,

NONNEGATABLE has already been specified

Facility: CDU, Command Definition Utility
Explanation: CDU has encountered a NEGATABLE clause after a
NONNEGATABLE clause was processed in the same keyword definition.
A NONNEGATABLE clause and the NEGATABLE clause cannot be specified
in the same keyword definition.
User Action: Edit the CLD file so that each keyword definition does not
contain both NEGATABLE and NONNEGATABLE clauses.
CONFNOPARM,

NOPARAMETERS has already been specified

Facility: CDU, Command Definition Utility
Explanation: CDU encountered a PARAMETER clause after a
NOPARAMETERS clause was encountered in a single verb/syntax definition.
A PARAMETER clause cannot be specified in the same verb/syntax definition
as NOPARAMETERS.
User Action: Edit the CLD file so that each verb/syntax definition does not
contain both NOPARAMETERS and PARAMETER clauses.
CONFNOQUAL,

NOQUALIFIERS has already been specified

Facility: CDU, Command Definition Utility
Explanation: CDU has encountered a QUALIFIER clause after a
NOQUALIFIERS clause was processed in the same verb/syntax definition. A
QUALIFIER clause cannot be specified in the same verb/syntax definition as
the NOQUALIFIERS clause.
User Action: Edit the CLD file so that each verb/syntax definition does not
contain both NOQUALIFIERS and QUALIFIER clauses.

2-91

CONFOUTPUTS,

only one OUTPUTS clause is allowed

Facility: CDU, Command Definition Utility
Explanation: CDU encountered more than one OUTPUTS clause in a single
verb/syntax definition. Only one OUTPUTS clause is allowed per verb
/syntax definition.
User Action: Edit the CLD file so that each verb/syntax definition does not
contain more than one OUTPUTS clause.
CONFPARM,

a parameter has already been defined

Facility: CDU, Command Definition Utility
Explanation: CDU encountered a NOPARAMETERS clause after a
PARAMETER clause was processed in a single verb/syntax definition. A
NOPARAMETERS clause cannot be specified in a verb/syntax definition in
which PARAMETER was previously specified.
User Action: Edit the CLD file so that each verb/syntax definition does not
contain both PARAMETER and NOPARAMETERS clauses.
CONFQUAL,

a qualifier has already been defined

Facility: CDU, Command Definition Utility
Explanation: CDU encountered a NOQUALIFIERS clause after a
QUALIFIER clause was encountered in a single verb/syntax definition. A
NOQUALIFIERS clause cannot be specified in a verb/syntax definition in
which the QUALIFIER clause was previously specified.
User Action: Edit the CLD file so that each verb/syntax definition does not
contain both QUALIFIER and NOQUALIFIERS clauses.
CONFQUAL,

conflicting qualifiers

Facility: CONVERT, Convert Utility
Explanation: You have specified qualifiers that are mutually exclusive. For
example, the /MERGE and the /APPEND qualifiers cannot be specified at
the same time since they operate with files of different organization.
User Action: Change the qualifiers and try again.
CONFQUAL,

conflicting qualifiers

Facility: CLI, Command Language Interpreter (DCL), INIT, INITIALIZE
Volume Command, INSTALL, Install Utility, MOUNT, MOUNT Command,
DUMP, File Dump Utility, DIFF, DIFFERENCES Command, LINK, VAX
Linker, MACRO, VAX Macro Assembler, BACKUP, Backup Utility
Explanation: Two or more conflicting qualifiers were specified.
User Action: Use the DCL command HELP or refer to the VAX/VMS DCL
Dictionary to determine the qualifiers in conflict and reenter the command.
CONFQUAL,

conflicting qualifiers

Facility: DSRTOC, DIGITAL Standard Runoff Table of Contents Utility
Explanation: DSR encountered a command that contained conflicting
qualifiers.
User Action: Check the syntax of the command and reenter the command.

Messages

CONFQUAL,

conflicting qualifiers

Facility: Shared by several facilities
Explanation: Two or more conflicting qualifiers were specified.
User Action: Use the DCL command HELP or refer to the VAX/VMS DCL
Dictionary to determine the qualifiers in conflict and reenter the command.
CONFQUAL,

conflicting qualifiers

Facility: SHR, SET Facility Shared Messages
Explanation: Two or more conflicting qualifiers were specified.
User Action: Use the DCL command HELP or refer to the VAX/VMS DCL
Dictionary to determine the qualifiers in conflict and reenter the command.
CONFQUAL,

conflicting qualifiers, request aborted

Facility: SYSGEN, System Generation Utility
Explanation: The SYSGEN command AUTOCONFIGURE was issued
specifying both the /EXCLUDE and /SELECT qualifiers.
User Action: Reissue the command with only one qualifier.
CONFROUTIMG,

only one routine or image clause is allowed

Facility: CDU, Command Definition Utility
Explanation: CDU encountered more than one IMAGE or ROUTINE
clause in a single verb/syntax definition. IMAGE and ROUTINE clauses
are mutually exclusive.
User Action: Edit the CLD file so that each verb/syntax does not contain
more than one IMAGE or ROUTINE clause.
CONNEC,

unable to connect to listener

Facility: NCP, Network Control Program
Explanation: NCP is unable to connect to NML to perform network
operations. Information accompanying this message explains any secondary
reasons for this error. Your network may not be configured correctly, your
access control information may be invalid, or all files may not be present.
User Action: If you receive this message upon issuing the SET EXECUTOR
NODE command, then you should use the command again after correcting
the problem or after supplying valid access control information. You may
then resume issuing NCP commands. Inspect the log file created by NML to
see if it provides additional information as to the cause of the problem.
CONNECFAIL,

connect to network object timed-out or failed

Facility: SYSTEM, VAX/VMS System Services
Explanation: The remote node did not respond to the logical-link request.
User Action: Check to see if the node is reachable and retry.

2—93

Consistency check failed, please check your file
Facility: EDT, EDT Editor
Explanation: There is a discrepancy between the number of lines and
characters present when the editing session ends. This message indicates
an EDT problem.
User Action: Check for possible errors in your output file. Submit a Software
Performance Report.
CONTINUE,

unable to continue processing 'file-spec'

Facility: BACKUP, Backup Utility
Explanation: The specified file, which was being processed at a change
of save set volumes, is no longer accessible. The accompanying message
provides additional information and the Backup Utility terminates processing
of the file. If other file activity is occurring on the volume, the error is
probably caused because another user deleted the file during the back-up
process.
User Action: Note that the file is incompletely processed.
CONTINUED,

'save set spec' contains a continued file - cannot append

Facility: BACKUP, Backup Utility
Explanation: In a save operation with the /NOREWIND qualifier, the
specified volume contained a multivolume file that was continued on another
volume, and therefore a file cannot be appended to the volume.
User Action: Retry the operation using another volume.
CONTRACT,

Contract virtual address space error

Aborted by CTRL/C at line 'count'

Facility: VAX Text Processing Utility
Explanation: The program stopped executing because you pressed CTRL/C.
User Action: None is required. However, if you have kept a journal file, you
may exit from VAXTPU and restart the session.
CONTROLC,

operation completed under CTRL/C

Facility: SYSTEM, VAX/VMS System Services
Explanation: An operation did not complete because CTRL/C was pressed.
User Action: None. The message is success.

Messages

CONTROLC,

operation completed under CTRL/C

Facility: SYSTEM, VAX/VMS System Services; RMS, VAX Record
Management Services

Explanation: An operation did not complete because CTRL/C was pressed.
User Action: None. The operating system does not normally display this
message.
CONTROLO,

operation completed under CTRL/O

Facility: RMS, VAX Record Management Services
Explanation: An operation did not complete because CTRL/O was pressed.
User Action: None. The operating system does not normally display this
message.
CONTROLO,

output completed under CTRL/O

Facility: SYSTEM, VAX/VMS System Services
Explanation: An output operation to the terminal did not complete because
CTRL/O was pressed.

User Action: None. The operating system does not normally display this
message.
CONTROLY,

operation completed under CTRL/Y

Facility: SYSTEM, VAX/VMS System Services and RMS, VAX Record
Management Services

Explanation: An operation did not complete because CTRL/Y was pressed.
User Action: None. The operating system does not normally display this
message.
CONTROLY,

operation completed under CTRL/Y

Facility: SYSTEM, VAX/VMS System Services and RMS, VAX Record
Management Services

Explanation: An operation did not complete because CTRL/Y was pressed.
User Action: None. The operating system does not normally display this
message.
COO,

Can't open output file 'filename7

Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: The output file specification is erroneous, or you do not have
write access to the file.
User Action: Check the file specification for errors, or check to see if you
have write access to the file. If the problem continues, notify the system
manager.

2-95

Messages

COPIED,

copied 'file-spec7

Facility: BACKUP, Backup Utility
Explanation: The Backup Utility successfully completed a save operation.
This message is displayed only if the /LOG qualifier is specified.
User Action: None.
COPIEDB,

input-file-spec copied to output-file-spec (nnn blocks)

Facility: Shared by several facilities
Explanation: The message displays the number of blocks or the number of
records copied, based on the size of the input file(s).
User Action: None. The message is informational.
COPIEDR,

input-file-spec copied to output-file-spec (nnn records)

COPMSG,

user record copied

Facility: AUTHORIZE, Authorize Utility
Explanation: This message is informational.
User Action: No user action is required.
COPY_LOG,

Copy of log from 'log file' follows:

Facility: UETP, User Environment Test Package
Explanation: The current process has been created and is communicating
with other processes in the UETP. To centralize the reporting of information
about the progress of the UETP, this process is copying the log file from the
execution of one of those processes.
User Action: None.
COPY_LOG —ENDED,

End of log file from 'file-spec'

Facility: UETP, User Environment Test Package
Explanation: The current process has finished copying the log file introduced
by the UETP$_COPY_LOG message.
User Action: None.
COP Y_LOG -LINE,

'text'

Facility: UETP, User Environment Test Package
Explanation: The current process is copying a line of the file introduced
by the UETP$—COPY—LOG message. Normally, only the text being copied
appears; the facility, severity, and IDENT fields are not printed.
User Action: None.

2—96

Messages

COR,

Can't open required file 'filename'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: The required file specification is erroneous, or the file is
nonexistent, or you do not have read access to the file.
User Action: Check the file specification for errors, or check to see if you
have read access to the file. If the problem continues, notify the system
manager.

Could not align tabs with cursor
Facility: EDT, EDT Editor
Explanation: The cursor is in a position where it cannot be evenly divisible
by the tab size when the tab compute function was used.
User Action: Change the tab size or cursor position.
CPUCEASED,

CPU ceased execution

network DAP level CRC check failed
Facility: RMS, VAX Record Management Services
Explanation: CRC checksums computed by VAX RMS and the File Access
Listener (FAL) at the remote node did not match when compared during a
VAX RMS close operation.
User Action: The file that was created or modified may be corrupted.
Repeat the file access. If the CRC error on close persists, the communication
hardware is malfunctioning.

CRCLS,

the 'class-name' class cannot be removed from this report

Facility: SHOW, SHOW Facility The class name entered does not apply
to the currently selected report and therefore cannot be removed from the
report. The name is, however, valid in a different report.
User Action: Select a different report or type HELP CLASSES to get a list of
available classes.

2-97

CRE,

ACP file create failed
Facility: RMS, VAX Record Management Services
Explanation: A file could not be created. This message is associated with a
status code returned from a file system ACP QIO request made by VAX RMS.
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.

CRE A _ERR,

error creating work file 'file-spec'

Facility: CONVERT, Convert 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.
CREATE,

error creating output file

Facility: FDL, Create/FDL Utility and FDL, Edit/FDL 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.
CREATED,

'file-name' created

Facility: DSRTOC, DIGITAL Standard Runoff Table of Contents Utility
Explanation: This informational message indicates that an output file has
been created.
User Action: None.
CREATED,

'file-spec' created

Facility: Shared by several facilities
Explanation: This message is displayed when command activity results in a
new file or directory.
User Action: None. The message is informational.
CREATED,

'file-spec' created

Facility: SYSGEN, System Generation Utility
Explanation: This informational message is the result of the SYSGEN
command CREATE and indicates that the specified file has been created.
User Action: No action is required.
CREATED,

file does not exist—was created

Facility: RMS, VAX Record Management Services
Explanation: File was created when the CREATE—IF option was specified.
User Action: None. This is a success code.

Messages

CREATED,

file was created, not opened

Facility: Shared by several facilities
Explanation: A system service, VAX RMS, or file system ACP request to
create a file or directory (if it does not currently exist) completed successfully
with a new file or directory.
User Action: None. The user program should detect and respond, if
necessary, to this condition.
CREATED,

file/section/resource did not exist - was created

Facility: SYSTEM, VAX/VMS System Services
Explanation: This file, section, or resource did not already exist and has just
been created.
If global sections are specified, this status is returned to processes that actually
create a section through use of the $CRMPSC system service. (Omission of
SEC$M_GBL results in the creation of local sections, rather than the creation
of global sections and the return of this status.)
User Action: None. This is a success message.
CREATEDSTM,

'file-spec' has been created in stream format

Facility: Shared by several facilities
Explanation: RMS created the file in stream format with embedded carriage
control because format and carriage control were specified in the RMS
$CREATE call and are not supported by the remote node.
User Action: None. This is informational.
CREATEFAIL,

Unable to activate subprocess

Facility: VAX Text Processing Utility
Explanation: The use of the built-in procedure CREATE—PROCESS has
failed to successfully start a subprocess.
User Action: Recreate the subprocess, and if unsuccessful, check your
ASTLM, PRCLM, or BYTLM quotas.
CREATELOST,

error creating directory [SYSLOST]

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility encountered an error during an attempt to
create the directory [SYSLOST] to enter lost files. The accompanying message
provides additional information.
User Action: Correct the condition that caused the error and reenter the
Verify Utility command line.

2-99

CREATEVIRT,

error creating the virtual volume 'volume'

Facility: EXCHANGE, Exchange Utility
Explanation: The EXCHANGE utility received an error from RMS while
trying to create a Files-11 file to be used as a virtual volume.
User Action: This message will be followed by one or two error messages
reporting the actual condition discovered by RMS. Take corrective action
suggested by the RMS error messages, then retry the command.
CREDIR,

created directory 'directory'

Facility: BACKUP, Backup Utility
Explanation: BACKUP successfully created the directory 'directory'. This
message is displayed only if the /LOG qualifier is specified.
User Action: None.
CREDIRERR,

error creating directory 'directory-spec'

Facility: BACKUP, Backup Utility
Explanation: The Backup Utility encountered an error during an attempt to
create the specified directory. The accompanying message provides additional
information.
User Action: Correct the condition that caused the error and reenter the
command.
CREERR,

unable to create SYSUAF.DAT

Facility: AUTHORIZE, Authorize Utility
Explanation: This message is issued with other messages.
User Action: Take corrective action based on the accompanying messages.
CREJOB,

error creating job

Facility: PRINT, Print Command and SUBMIT, SUBMIT Command
Explanation: The system encountered an error creating a batch or print job.
The accompanying message provides additional information.
User Action: Correct the error and reenter the command.
CRENEWFOLD,

folder 'folder-name' does not exist. Do you want to create it
(Y/N, default is N)?

Facility: MAIL, Personal Mail Utility
Explanation: You have requested MAIL to place a message into a nonexistent
folder.
User Action: Confirm the request by typing Y, or abort with a carriage return.
CREPARFIL,

Unable to create parameter file

Facility: SYSGEN, System Generation Utility
Explanation: An error occurred during a WRITE operation.
User Action: Reissue the command so that you can write to the file.

Messages

CREPRC,

process creation failed

Facility: RUN, Run Detached Utility
Explanation: The creation of the subprocess or detached process failed. For
an explanation of possible reasons for failure see the error codes returned by
the $CREPRC system service.
User Action: Correct problem described by the $CREPRC error message, and
reenter command.
CREPRIJOB,

error creating print job on queue 'queue-name'

Facility: MAIL, Personal Mail Utility
Explanation: An error occurred when you attempted to create a print job
to queue a message for printing. This message is usually accompanied by a
system error message indicating the reason for the failure.
User Action: Resolve the problem and reenter the command.
CRE—STM,

file was created in stream format

Facility: RMS, VAX Record Management Services
Explanation: VAX RMS created the file in stream format with embedded
carriage control instead of using the record format (RFM field) and carriage
control (RAT field) type specified in the VAX RMS $CREATE call. This file
format conversion was performed because the remote DECnet system only
supports stream format files.
User Action: None. This is a success code.
CRF,

Can't read back saved footnotes
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: DSR has successfully written footnote information to the work
file but cannot read it back. One or more OOIRNO.TMP files may already
exist.
User Action: Delete any OOIRNO.TMP files, and reprocess the file. If the
problem continues, notify the system manager.

CRFERR,

error encountered in Cross Reference

Facility: LINK, VAX Linker
Explanation: An error was returned by the Cross-Reference Facility.
User Action: The additional message from Cross-Reference should explain
the problem.
CRMP,

CRMPSC system service failed to map global buffers

Facility: RMS, VAX Record Management Services
Explanation: This message is associated with a status code returned from the
$CRMPSC (Create and Map Section) system service called from VAX RMS to
map global buffers.
User Action: The status value (STV) field of the RAB contains a code that
provides more information about the condition. Take corrective action based
on this status code.

2-101

Messages

CRMPSC,

error code of 'xx' mapping section

Facility: PATCH, VAX Image File Patch Utility
Explanation: The system service $CRMPSC request failed due to the error
represented as xx.
User Action: Correct the error (represented as xx) and retry.
CRP,

Can't recognize page on /PAGES qualifier
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: A page range specification is illegally formatted.
User Action: Correct the page range specification.

CTRLCEXIT,

Exit now to avoid journal file inconsistency

Facility: VAX Text Processing Utility
Explanation: Use of CTRL/C often causes a journal file inconsistency during
recovery.
User Action: Exit immediately after pressing CTRL/C to save your edits.
You can then reenter the editing session.
CTRLCHAR,

the following line contains control characters - ignored

Facility: DSRTOC, DIGITAL Standard Runoff Table of Contents Utility
Explanation: DSR encountered control characters in a line of the input file.
The control characters were ignored, however.
User Action: None.
CTRLCJOU,

CTRL/C may have invalidated the journal file

Facility: VAX Text Processing Utility
Explanation: A CTRL/C character has been detected in the journal file. This
may mean that the rest of the session is invalid.
User Action: If you used CTRL/C during an editing session, exit immediately
and restart VAXTPU.
CTRLERR,

fatal controller error

Facility: SYSTEM, VAX/VMS System Services
Explanation: The exact meaning depends on the device. This message may
indicate a hardware error. If this message is associated with a status code
returned by a request to a disk driver or magtape, it indicates a controllerrelated error. For example, one or more of the following conditions can cause
this error:

2-102

•

Late data

•

Error confirmation

•

Invalid map register

•

Interface timeout

•

Missed transfer

•

Programming error

Messages

•

Read timeout

•

RX01 switch set incorrectly (RX02 only) (disk driver specific)

If this message is associated with a status code returned by a request to a
DR11-W interface, a fatal error that affects all DR11-W activity was set in
the DR11-W CSR on completion of the QIO request. Look at the third and
fourth words of the IOSB (CSR and EIR) for the specific cause of the error.
If the condition indicated in the CSR can be cleared, that is, if the ATTN bit
can be cleared, SS$_DRVERR is returned. If the condition cannot be cleared,
SS$_CTRLERR is returned. In both cases, the driver performs a device reset
to the DR11-W.
If this message is associated with a status code returned by a request to a
DR32 interface, a fatal hardware malfunction occurred that stops all DR32
activity. (Only for start data transfer functions.) The second longword of the
IOSB contains additional information pertaining to this error; the following
bit values are associated with SS$_CTRLERR:
XF$V_IOS_INVPTE
XF$V_IOS_SBIERR
XF$V_JOS_RDSERR
If this message is associated with a status code returned by a request to a
DMC/DMR device, it can occur for one of the following reasons:
•

NAK threshold errors exceeded

•

Time out on response from remote end

•

Buffer not available

•

Maintenance message received in RUN mode

•

Message too long to fit in receiver buffer

•

Modem has disconnected

•

Start message was received in run mode

•

Nonexistent memory error

•

Halt to DMC/DMR is complete

If this message is displayed, restart the DMC/DMR device.
If this message is associated with a status code returned by a LPA11-K driver,
it is a fatal error that affects all LPA11-K activity. The LPA11-K terminates all
active requests. The third and fourth words of the IOSB contain the LPA11-K
Ready-Out Status Register and Maintenance Register contents. In particular,
the high byte of the third word contains the specific LPA11-K error code.
If this message is associated with DEUNA hardware, on a STARTUP request
the startup failed because of bad error return from the DEUNA hardware. On
a read request, the hardware returned a zero-length message.
User Action: Action depends on the type of device to which the I/O request
was directed. If the failure persists, notify the system manager.
If the failure was on STARTUP, then the DEUNA should be checked by
running UETP or if Field Service runs the DEUNA diagnostics. If the failure
was on a read request and the protocol has enabled PADDING, then the
remote software module should be corrected to stop sending zero-length
messages.

2-103

Messages

CUR,

no current record (operation not preceded by $GET/$FIND)
Facility: RMS, VAX Record Management Services
Explanation: A program attempted a VAX RMS $DELETE, $TRUNCATE, or
$UPDATE operation without having performed a successful $GET or $FIND
operation.
User Action: Check for a programming error. Modify the source program, if
necessary, to detect and respond to the condition.

CVTERR,

could not convert entity 'time or number' using 'time or number'

Facility: RUN, Run Detached Utility
Explanation: Time specified with the /DELAY, /INTERVAL, and/or
/SCHEDULE qualifiers was not in the proper format or value entered with
value requiring qualifiers could not be converted to a numeric value.
User Action: Reenter qualifier value (time or number) in the proper form.
CVTERR,

error converting to decimal value, 'value'

Facility: ERF, ANALYZE/Error Log Utility
Explanation: An attempt was made to convert a value to decimal resulting in
an error.
User Action: Submit a Software Performance Report.
CVTUNGRANT,

cannot convert an ungranted lock

Facility: SYSTEM, VAX/VMS System Services
Explanation: An attempt was made to convert a lock that was not granted.
(Only locks that are granted may be converted to another lock mode.)
User Action: See the section on the lock management services in the
VAX/VMS System Services Reference Manual and correct your program.
CWF,

Can't write footnote file (N)

Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: DSR can open the footnote work file but cannot write into it; N
is a system error code.
User Action: Reprocess the file. If the problem continues, notify the system
manager.
DAC,

ACP file deaccess failed during $CLOSE
Facility: RMS, VAX Record Management Services
Explanation: An error occurred when a file was closed. The file was
deaccessed. This message is associated with a status code returned from
a file system ACP QIO request made by VAX RMS.
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.

2-104

Messages

DAN,

invalid data area number for key = 'nnn'

Facility: RMS, VAX Record Management Services
Explanation: The data area number specified in a key definition XAB is not a
defined area 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 VAX RMS service
was coded correctly.
DATACHECK,

write check error

Facility: SYSTEM, VAX/VMS System Services
Explanation: The data in memory did not match the data on disk during a
data check operation. If this message is associated with a status code returned
by a LPA11-K driver, a mismatch between the microcode in memory and the
microcode loaded into the LPA11-K was detected. The second word of the
IOSB contains the number of bytes successfully loaded.
Or, on a write request, the DEUNA hardware detected a late collision.
User Action: Note the condition. If necessary, modify the source program to
detect and respond to the condition. This message may indicate a hardware
error. If the error persists, notify the system manager.
Or, the Ethernet cable and all Ethernet controllers should be checked for
proper operation.
DATADEVERR,

Data error on 'device' byte 'location' good data = 'xx' bad data =
'xx'

Facility: UETP, User Environment Test Package
Explanation: One of the UETP tests detected a difference between the data
that was written from memory and the same data after it was read back into
memory. The 'location' is the offset from the start of the buffer where the
first difference was detected.
User Action: Investigate the device or mechanism that caused the error.
DATAER,

data error on 'device-type' unit 'number' byte 'location' good data = 'xx'
bad data = 'xx'

Facility: UETP, User Environment Test Package
Explanation: One of the UETP tests detected a difference between the data
that was written from memory and the same data after it was read back into
memory. The 'location' is the offset from the start of the buffer where the
first difference was seen.
User Action: Investigate the device or mechanism that caused the error.
DATALSTSYN,

data list syntax error

Facility: MACRO, VAX Macro Assembler
Explanation: The data list in the directive contained a syntax error. For
example, the directive .LONG 3„5 contains a data list syntax error because
there is no data item between the two commas.
User Action: Correct the syntax of the data list.

2—105

Messages

DATALSTSYN,

data list syntax error

Facility: MACRO, VAX Macro Assembler
Explanation: A data list with a repeat count was not terminated.
User Action: Correct the incorrect code.
DATAOVERUN,

data overrun

Facility: SYSTEM, VAX/VMS System Services
Explanation: This message can indicate that:
•

More data was read into the user buffer than the user buffer could hold.

•

More data was written into the user buffer than the user buffer could hold.

•

Card reader data was written into the controller data buffer before the
driver was able to receive the previous data.

If this message is associated with a status code returned by a request to a
magnetic tape driver, the data block read was longer than the assigned buffer.
In the case of a read reverse, the last data on the tape (that is, the data nearest
the end-of-tape at the beginning of the operation) is the first data read. This
data is in the buffer.
User Action: Specify a larger buffer if the data was too much for the existing
buffer. If the problem occurred on a card reader operation, resubmit the
card(s) to the card reader to be reread.
DATAOVFL,

data area overflow in section - please submit SPR

Facility: MESSAGE, Message Utility
Explanation: An internal error in the compiler has been detected.
User Action: Submit a Software Performance Report.
DATATRUNC,

data truncation error

Facility: MACRO, VAX Macro Assembler
Explanation: The specified value did not fit in the given data type. The
assembler truncated the value to make it fit.
User Action: Reduce the value or the number of characters in an ASCII
string or change the data type.
DATMISMCH,

creation date of 'date' in shareable image 'image-name7 differs
from date of 'date' in shareable image library 'library-name'

Facility: LINK, VAX Linker
Explanation: A shareable image extracted from a shareable image library has
a different creation date from the date recorded for that shareable image in
the library.
User Action: Insert the new shareable image into the shareable image library
using the DCL command LIBRARY.

2-106

Messages

DATTOOLNG,

length of new data may not exceed length of old data

Facility: PATCH, VAX Image File Patch Utility
Explanation: This error is returned when patching in absolute mode (PATCH
/ABSOLUTE), and the length of the data being inserted is longer than that of
the data to be replaced in the file.
User Action: Make sure that the data to be inserted is equal to or shorter in
length than the data in the file.
DBGERR,

internal DEBUG coding error

Facility: DEBUG, VAX/VMS Debugger
Explanation: An internal debugger error has been encountered.
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.
DBGTFR,

image 'image-name7 has no Debugger transfer address

Facility: LINK, VAX Linker
Explanation: A debugger was requested with the /DEBUG qualifier, but the
linker could not locate a transfer address within the debugger module.
User Action: If you specified the optional filename parameter with the
/DEBUG[=filename] qualifier, ensure that the specified debugger module
contains a transfer address. If you specified /DEBUG, without the filename
parameter, submit a Software Performance Report.
DBLERR,

Double error halt restart

Facility: System Bugcheck
Explanation: The VAX/VMS software detected an irrecoverable hardware
error. Because of the severity of the error, further operation is impossible,
or if it is possible, it may corrupt user data. After all 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: 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.)

2-107

DEADLOCK,

deadlock detected

Facility: SYSTEM, VAX/VMS System Services, RMS, VAX Record
Management Services
Explanation: The system detected a set of processes waiting for locks in a
circular fashion (deadlock). This lock request was denied in order to break
the deadlock.
User Action: Recovery from a deadlock is application-specific. One common
action is for the program to release all of its locks (performing any necessary
cleanup) and then to retry the operation. See the section on the lock
management services in the VAX/VMS System Services Reference Manual
and rerun the program.
DEBUG,

Break at line 'integer'

Facility: VAX Text Processing Utility
Explanation: A BREAK statement has been executed.
User Action: None.
DEBUG,

command interpreter debugger signal at PC 'location', PSL - 'xxxxxxxx'

Facility: SYSTEM, VAX/VMS System Services
Explanation: The DCL command DEBUG was issued after CTRL/Y
interrupted an image that was not linked with the debugger.
User Action: Link the image with the /DEBUG qualifier to enable use of the
debugger.
DEBUGBUG,

internal DEBUG coding error, please report no. nnn

arithmetic trap, decimal overflow at PC = xxxxxxxx,PSL = xxxxxxxx

Facility: SYSTEM, VAX/VMS System Services
Explanation: A decimal overflow caused an arithmetic overflow 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.
DECOVF,

decimal overflow

Facility: LIB, Run-Time Library General Procedures
Explanation: During an arithmetic operation, a decimal value has exceeded
the largest representable decimal number.
User Action: None. The result of the operation is set to the correctly signed
least significant digit.

Messages

DECPTREF,

Decrement page table reference count error

entity defaulted present in command string

Facility: CLI, Command Language Interpreter (DCL)
Explanation: This status is returned by the CLI$PRESENT CLI interface
routine to indicate that the specified entity is not explicitly present in the
command line, but is present by default.
User Action: None.
DEFAULTLEN,

a default is limited to 'max-length' characters in length, including
commas

Facility: CDU, Command Definition Utility
Explanation: CDU encountered a DEFAULT assignment in the CLD file
that exceeded the maximum allowable length for a DEFAULT assignment.
Currently, the maximum length for a DEFAULT assignment is 94 characters.
User Action: Edit the CLD file so that no DEFAULT assignments are greater
than 94 characters in length.
DEFERR,

unable to obtain DEFAULT record

Facility: AUTHORIZE, Authorize Utility
Explanation: This message is issued with other messages.
User Action: Take corrective action based on the accompanying messages.
DEFKEY,

'state' key 'key name' has been defined

Facility: CLI, Command Language Interpreter (DCL)
Explanation: The specified key was defined.
User Action: None.
DEFOVF,

too many command procedure parameters - limit to eight

Facility: CLI, Command Language Interpreter (DCL)
Explanation: A command procedure was invoked with more than eight
parameters.
User Action: Reenter the command; do not specify more than eight
parameters.

2—109

DEFPPI,

failed to define PPI name to LES

Facility: PSI, VAX Packetnet System Interface
Explanation: The specified PPI was not correctly defined to LES. This
message is qualified by a secondary message in the form: SS$ code.
Typically, this is caused by insufficient memory.
User Action: Increase the size of the nonpaged pool and try again.
DEFPWD,

Warning: copied or renamed records must receive new password

Facility: AUTHORIZE, Authorize Utility
Explanation: You did not explicitly specify a password for the new record.
User Action: You must specify a password for the new record.
DEFSYNTAX,

invalid action definition syntax

Facility: ACLEDIT, Access Control List Editor
Explanation: The syntax for the ACL editor action definition was incorrect.
User Action: Please refer to the default action definition file
SYS$LIBRARY:ACLEDIT.INI for an explanation and examples of the editor
action definition.
DEL,

RFA-accessed record was deleted
Facility: RMS, VAX Record Management Services
Explanation: A record accessed by the record's file address (RFA) was deleted
previously.
User Action: Note the condition. Modify the source program, if necessary, to
detect and respond to the condition.

DELACCESS,

file protection does not allow delete access

Facility: JBC, Job Controller
Explanation: The file protection of the specified file, which was entered with
the delete option, does not allow delete access to the requestor.
User Action: None.
DELCONPFN,

Fatal error in delete contents of PFN

Messages

DELDATERR,

error deleting data from 'library file-spec'

Facility: LIBRAR, LIBRARY Command
Explanation: This error message is generated by the DCL command
LIBRARY. An error occurred during an attempt to delete the text; or a VAX
RMS error occurred; or there was not enough virtual memory available.
User Action: Compress the old library before deleting the specified text.
DELERR,

error deleting file 'file-spec'

Facility: NCP, Network Control Program
Explanation: You attempted to use the NCP command PURGE KNOWN to
a nonexistent database.
User Action: Correct the condition that caused the error and reenter the
command line.
DELETE,

error deleting 'file-name' file ID ('numeric-string')

Facility: BACKUP, Backup Utility
Explanation: An error was encountered during an attempt to delete the file
with the specified file identification in response to the /DELETE qualifier.
The accompanying message provides additional information.
User Action: None.
DELETE,

file ('file-id') 'file-name' error deleting file

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility encountered an error during an attempt to
delete the specified file. The accompanying message provides additional
information.
User Action: Correct the condition that caused the error and reenter the
Verify Utility command line.
DELETED,

'file-name' deleted

Facility: Shared by several facilities
Explanation: The message displays the file specification of a file that was
deleted successfully.
User Action: None. The message is informational.
DELETED,

module 'module name' deleted from 'library file-spec'

Facility: LIBRAR, LIBRARY Command
Explanation: This success message is generated by the DCL command
LIBRARY.
User Action: None. This message is informational.

2-111

Messages

DELETED,

previous Known File Entry has been deleted

Facility: INSTALL, Install Utility
Explanation: This message is displayed as the result of issuing a REPLACE
command in INSTALL. If the REPLACE command failed to create a new
Known File Entry for any reason, this message is displayed to explicitly
declare the fact that the previous Known File Entry has been successfully
removed.
User Action: None. This is a warning explaining why even the old entry no
longer exists in case REPLACE failed to create a new entry.
DELETEFAIL,

Unable to terminate subprocess

Facility: VAX Text Processing Utility
Explanation: The use of the built-in procedure DELETE to delete a
subprocess failed to terminate the subprocess.
User Action: None.
DELETESWL,

'device-name' is write protected - file deletion pass not executed

Facility: BACKUP, Backup Utility
Explanation: The input device is software write locked. The BACKUP Utility
cannot perform the file deletion pass.
User Action: Dismount the input device, remount it writeable, and either
delete the files by hand or reissue the BACKUP command.
DELEXIGBL,

Termtable section already exists

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: The system program which maps Termtable as a global section
was unsuccessful. Before a new global section can be created, the previous
global section must be deleted.
User Action: The system must be rebooted in order to map a new
TERMTABLE.EXE as the new global section.
DELGBLSEC,

Delete global section error

2-112

Messages

DELGBLWCB,

Delete global section window error

file ('file-id') 'file-name' marked for delete

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the specified file was marked for
deletion, but was not deleted.
User Action: None. The file is deleted.
DELKEY,

'state' key 'key name' has been deleted

Facility: CLI, Command Language Interpreter (DCL)
Explanation: The specified key was deleted.
User Action: None.
DELKEYERR,

error deleting 'module-name' from 'library file-spec'

Facility: LIBRAR, LIBRARY Command
Explanation: This error message is generated by the DCL command
LIBRARY. The module you want to delete does not appear in the module
name table (MNT); a VAX RMS error occurred; or there is not enough virtual
memory available.
User Action: List the library to find out whether the module is present.
Then, if the module is present, correct the problem before reentering the
command line.
DELSYM,

'symbol table' symbol 'symbol name' has been deleted

Facility: CLI, Command Language Interpreter (DCL)
Explanation: This informational message verifies that the symbol deletion
requested via the DELETE/SYMBOL command has occurred.
User Action: None.
DELTVA,

error code of 'xx' deleting 'xxx' to 'xxx'

Facility: PATCH, VAX Image File Patch Utility
Explanation: The system service request $DELTVA failed due to the error
code represented as xx.
User Action: Correct the error (represented as xx) and retry.

2-113

Messages

DELVER,

explicit version number or wild card required

Facility: Shared by several facilities
Explanation: The DCL command DELETE requires a version number in each
file specified.
User Action: Reenter the command. Specify either the explicit version
number for the file you want to delete or use a wild card in the version field.
DELWSLEX,

Delete working set list entry index error

'testname' device 'device-type' is not supported

Facility: UETP, User Environment Test Package
Explanation: The device name in this message is unknown to the UETP and
cannot be tested by UETP, for example, a user-written driver.
User Action: The UETP either supports or knows to ignore all devices
supported by VAX/VMS. If another device, which is not a supported layered
product, produces this message, submit a Software Performance Report.
DENSITY,

'saveset-spec' does not support specified density - default used

Facility: BACKUP, Backup Utility
Explanation: The specified tape hardware does not support the density
selected by the /DENSITY qualifier. The Backup Utility uses the default
density.
User Action: Use a different tape device, or specify a different density.
DEQSUBLCKS,

Tried to dequeue lock with sublocks

2-114

Messages

DESSTROVF,

destination string overflow

Facility: LIB, Run-Time Library General Procedures
Explanation: The destination string was overflowed, and the operation did
not justify return of a warning, but a fatal error.
User Action: Increase the length of the destination string, or use dynamic
string for destination.
Destination for MOVE or COPY not found
Facility: EDT, EDT Editor
Explanation: The range specification in the command does not exist.
User Action: Reenter the command specifying an existing range.
DESTP,

'testname' stopped testing 'controller7 unit 'number7 at 'time'

Facility: UETP, User Environment Test Package
Explanation: A device that passed the simple read/write test in the initial
phase of the UETP could not complete its test in the device test phase.
User Action: If you think that the device should be tested by UETP,
investigate and correct the problem; otherwise, ignore the message.
DEUNUS,

'testname' device 'device-name' is unusable, error code = 'xxxxxxxx'

Facility: UETP, User Environment Test Package
Explanation: The specified device failed to pass the simple read/write test in
the initial phase of UETP. Subsequent tests with UETP will not attempt to test
the device. Another message usually follows to explain why the device failed
the test. Possible causes are that the device is down, offline, not mounted,
not initialized, or not write-enabled.
User Action: Either make the device usable or ignore the message. Consult
the Software Installation Support manual.
DEV,

error in device name or inappropriate device type for operation
Facility: RMS, VAX Record Management Services
Explanation: A device name was not specified correctly; the device specified
is not supported by this system, or the type of device specified cannot
perform the requested operation (for example, an attempt was made to create
a random access file on a sequential device).
User Action: If the error occurred while a command was being entered,
verify the syntax and spelling of the device specification or the logical name,
if a logical name was specified. If the error occurred while an image was
being executed, check that the file specification was coded correctly and that
the logical name, if any, was assigned before the image was executed.
If the device name is correctly specified and if the device is valid for the
requested type of operation, verify that the device is available on your
system.

2-115

Messages

DEVACTIVE,

device is active

Facility: SYSTEM, VAX/VMS System Services
Explanation: If this message is associated with a status code returned by a
request to a DR32 interface, the microcode cannot be loaded because there is
an active data transfer request (only for the load microcode function).
If this message is associated with a status code returned by a request to
a LPA11-K driver, the microcode cannot be loaded or the microprocessor
cannot be started because there is an active data transfer request.
If this message is associated with a status code returned by a request to
a DR11-W interface, the DR11-W controller is occupied with a request
from another process. 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.
DEVALLOC,

device already allocated to another user

Facility: SYSTEM, VAX/VMS System Services
Explanation: An attempt to allocate a device failed because the device is
allocated by another user or channels are assigned to it. Only one user at a
time can access an allocated device.
Or, on a startup request, the user attempted to start the protocol as a shared
default user, when a shared default user already exists for that protocol type.
User Action: Wait until the current owner has deallocated the device, or
reenter the request specifying a different device of the same type, or specify a
generic device name in the allocate request.
The user must attempt to bring up two SHARED DEFAULT users until the
first user is stopped.
DEVALRALLOC,

device already allocated to this job

Facility: SYSTEM, VAX/VMS System Services
Explanation: This is a success status message from the Allocate Device
system service. The process has already allocated the device.
User Action: Depending on the program logic, this may not be an error; no
action is necessary.
DEVALSPL,

device already spooled

Facility: CLI, Command Language Interpreter (DCL)
Explanation: A request to set a device spooled was made for a device that
was already set spooled.
User Action: None.

2-116

Messages

DEVASSIGN,

device has channels assigned

Facility: SYSTEM, VAX/VMS System Services
Explanation: A request to deallocate a device failed because the device has
I/O channels assigned to it; that is, it is currently being read or written.
User Action: Verify the device name (or logical name, if a logical name was
specified) and reenter the command with the correct device name. If any
executing subprocesses are using the device, wait until they have terminated
before attempting to deallocate the device.
DEVCLASS,

device class of SYS$INPUT must be terminal

Facility: FDL, Edit/FDL Utility
Explanation: EDIT/FDL cannot interact with a file, only with a terminal.
User Action: Do not invoke EDIT/FDL from a batch job. Also, if invoking
EDIT/FDL from an interactive command file, first include the following line
immediately before the $EDIT/FDL command in the command file.
$ASSIGN/USER 'F$LOGICAL("SYS$OUTPUT")' SYS$INPUT

DEVCMDERR,

device command error

Facility: SYSTEM, VAX/VMS System Services
Explanation: The exact meaning depends on the device. If this message is
associated with a status code returned by a request to a LPA11-K driver (only
for the initialize LPA11-K, set clock, and start data transfer request functions),
it is associated with the issuance of a new LPA11-K command. The third and
fourth words of the IOSB contain the LPA11-K Ready-Out Status Register
and Maintenance Register contents. In particular, the high byte of the third
word contains the specific LPA11-K error code.
User Action: Action depends on the type of device to which the I/O request
was directed.
DEVCOUNT,

number of devices must match number of volumes

Facility: MOUNT, MOUNT Command
Explanation: The number of devices specified in the DCL command
MOUNT, to mount a disk volume set did not match the number of volume
labels specified in the command.
User Action: Check the command line. Verify the names of the devices
and volume labels for the command and then reissue the command with a
matching number of devices and volume labels.
DEVFOREIGN,

device is mounted foreign

Facility: SYSTEM, VAX/VMS System Services
Explanation: A Files-11 operation was attempted on a device which is
mounted foreign.
User Action: Remount the device as Files-11. If the medium is DOS or RT11
format, use FLX; otherwise, write a program.

2-117

DEVICE,

devices

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: No action is required.
device is not a local device
Facility: DISKQUOTA, Diskquota Utility
Explanation: You specified a device name (or logical name that translates to
a device name) that contains a node name.
User Action: Enter a device name (or logical name that translates to a device
name) that does not contain a node name. DISKQUOTA operates only on
local devices.
DEVICEFULL,

device full - allocation failure

Facility: SYSTEM, VAX/VMS System Services
Explanation: It indicates that space cannot be allocated for a file because the
device is full; or a request for contiguous space cannot be satisfied because
the specified number of contiguous blocks is not available.
User Action: Verify the status of the device. If it is a private device, purge
unwanted files with the DCL command PURGE. Otherwise, obtain another
volume to catalog files. If the device is a system device, notify the system
operator or manager that the volume is full.
DEVICES,

only one device allowed

Facility: MOUNT, MOUNT Command
Explanation: More than one device was specified in the DCL command
MOUNT. Only one volume can be mounted at a time for this specified type
of MOUNT.
User Action: Reenter the DCL command MOUNT specifying only one
device.
DEVIN ACT,

device inactive

Facility: SYSTEM, VAX/VMS System Services
Explanation: The device unit involved in the current operation is inactive.
This message indicates that you tried to perform an activity that cannot be
properly performed until the device unit is active. For example, the XE device
has not been started.
User Action: Start the controller before doing any tributary requests. The
user should make sure that the QIO STARTUP has completed successfully or
that the XE device has not shut down the unit due to a hardware failure.

Messages

DEVMOUNT,

device is already mounted

Facility: SYSTEM, VAX/VMS System Services
Explanation: The device specified has a volume mounted and cannot be
allocated, or a volume is already mounted on a device for which a mount
request was previously issued.
User Action: Verify the device name (or logical name, if a logical name was
specified) and reenter the command with the correct device name. If the
device name is correct and if the volume that is mounted can be dismounted,
dismount the volume and reissue the request.
DEVNOTALLOC,

device not allocated

Facility: SYSTEM, VAX/VMS System Services
Explanation: The device specified in a deallocate request is not currently
allocated.
User Action: Verify the device name (or logical name, if a logical name was
specified) and reenter the command with the correct device name.
DEVNOTERM,

illegal source operator device

Facility: OPCOM, Operator Communication
Explanation: The DCL command REPLY requested a device that is not a
terminal be enabled as an operator terminal; for example, the DCL command
REPLY/ENABLE was issued in a batch job.
User Action: Reenter the command from a terminal.
DEVNOTFOR,

'device-name' is not mounted foreign

Facility: BAD, Bad Block Locator Utility
Explanation: The device is not mounted foreign.
User Action: Mount the device /FOREIGN and reinvoke the utility.
DEVNOTFOR,

device not mounted foreign

Facility: CLI, Command Language Interpreter (DCL)
Explanation: An operation was requested for a device that must be mounted
foreign to perform the operation.
User Action: If the device is not mounted, then mount it foreign; if the
device is mounted, dismount it and remount it foreign.
DEVNOTKNWN,

device not known: 'input'

Facility: SYSGEN, System Generation Utility
Explanation: The specific device was unknown when you entered the
SYSGEN command CONFIGURE.
User Action: See Writing a Device Driver for VAX/VMS for the correct
UNIBUS controller name.

2-119

Messages

DEVNOTMBX,

device is not a mailbox

Facility: SYSTEM, VAX/VMS System Services
Explanation: An I/O channel specified in a system service request is not
currently assigned to a mailbox. The service requires that the device be a
mailbox.
User Action: Check for a programming error. Verify that the channel number
specified for the service is valid.
DEVNOTMOUNT,

device is not mounted

Facility: SYSTEM, VAX/VMS System Services
Explanation: This message is displayed when you issue the DCL command
DISMOUNT for a device that is not mounted or when you attempt an
operation that requires a mounted device.
User Action: Reenter the command with the mounted device or mount the
device in question.
DEVNOTSPL,

device not spooled

Facility: CLI, Command Language Interpreter (DCL)
Explanation: A request to set a device not spooled was made for a device
that was already set not spooled.
User Action: None.
DEVNOTSUIT,

the device 'devicename' is not suitable for operations

Facility: EXCHANGE, Exchange Utility
Explanation: An EXCHANGE command was directed at a device for which
the requested operation could not be performed.
User Action: Reenter the command, specifying a suitable device.
DEVOFFLINE,

device is not in configuration or not available

Facility: SYSTEM, VAX/VMS System Services
Explanation: For some device-specific reason, the associated driver is not
available. If this message is associated with a status code returned by a
request to a DMC11 interface, the device protocol was not started (read or
write). The function is inconsistent with the current state of the unit (Set
Mode).
The device is not currently online or the Ethernet protocol has not been
specified.
User Action: Reenable or repair the device and retry the operation.
The XE device should be checked to make sure that it has been configured
as ONLINE. The user should make sure that all parameters in the QIO
STARTUP request are supplied, including NMASC_PCLI_PTY.

2-120

Messages

DEVOFFLINE,

device is offline

Facility: OPCOM, Operator Communication
Explanation: This message is displayed on the operator's console when a
device goes offline in the VAX/VMS system configuration.
User Action: Take appropriate measures to bring the device online.
DEVOFFLINX,

'date and time7. Device 'device7 is offline Mount verification in
progress

Facility: OPCOM, Operator Communication
Explanation: The device is offline and mount verification is progress. All I/O
requests have been stalled.
User Action: Cancel the mount verification or bring the volume back online.
DEVONLINE,

device online

Facility: OPCOM, Operator Communication
Explanation: This message is displayed on the operator's console when a
device becomes online.
User Action: None. The message is informational.
DEVONLY,

using device name only, ignoring parts of 'filespec'

Facility: EXCHANGE, Exchange Utility
Explanation: The EXCHANGE utility has ignored all parts of the file
specification except the device name.
User Action: This command completed successfully, no action is necessary.
In the future, use the device name only in this context.
DEVQUALS,

invalid qualifier for device type

Facility: DUMP, File Dump Utility
Explanation: A qualifier was specified that is invalid if the input medium is
not a disk or tape device or is mounted with the /FOREIGN qualifier.
User Action: Reenter the command.
DEVRCT,

unable to analyze 'device_name', due to revector caching

Facility: BAD, Bad Block Locator Utility
Explanation: The device controller is capable of revectoring bad blocks
dynamically, hence, the device will always appear to be flawless.
User Action: Do not analyze the media.

2-121

DEVREQERR,

device request error

Facility: SYSTEM, VAX/VMS System Services
Explanation: The exact meaning depends on the device. If this message
is associated with a status code returned by a request to a DR32 interface,
a programming error or an error associated with the far end DR-device is
indicated. The second longword of the I/O status block contains additional
information pertaining to the error; the following bit values are associated
with SS$_DEVREQERR:
XF$V_IOS_DDIDIS
XF$V_IOS_RNGERR
XF$V_IOS_UNQERR
XF$V_IOS_INVPKT
XF$V_IOS_FREQMT
XF$V_IOS_INVDDI
XF$V_IOS_LENERR
XF$V_IOS_DDIERR
If this message is associated with a status code returned by a request to
a LPA11-K driver, it indicates a LPA11-K user request error for a start data
transfer request. The third and fourth words of the IOSB contain the LPA11-K
Ready-Out Status Register and Maintenance Register contents. In particular,
the high byte of the third word contains the specific LPA11-K error code.
On a write request, the DEUNA failed to transmit the message after 16
attempts.
User Action: Action depends on the type of device to which the I/O request
was directed.
The Ethernet cable may have short-circuited, or it may have been temporarily
overloaded. In either case, the Ethernet cable should be checked and if it is
operational, the user may wish to send packets again. However, it must be
noted that if these kinds of errors persist, the Ethernet is overloaded.
DEVSELREQ,

device selection required

Facility: ERF, ANALYZE/Error Log Utility
Explanation: A device type or class must be selected.
User Action: Using the appropriate qualifier, select a device type or class.
DEVSPEC,

input specification for non-file-structured dump must contain only
device

Facility: DUMP, File Dump Utility
Explanation: The input file specification can contain only the device
component if the input medium is not a disk or tape device or if it is mounted
with the /FOREIGN qualifier.
User Action: Correct and reenter the command.

Messages

DEVWRTLCK,

'date and time'. Device 'device' has been write locked. Mount
verification in progress

Facility: OPCOM, Operator Communication
Explanation: A write request to a Files-11 disk has failed because the device
was not mounted write-locked.
User Action: Cancel the mount verification, or remove the write lock on the
volume.
DFL,

data bucket fill size larger than bucket size for key = 'nnn'
Facility: RMS, VAX Record Management Services
Explanation: The data bucket fill size specified in a key definition XAB
exceeds the bucket size for the data area.
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 VAX RMS service
was coded correctly.

DGQINCOMP,

datagram queue operation incomplete

Facility: SYSTEM, VAX/VMS System Services
Explanation: A request to remove a certain number of datagrams from a
queue succeeded only partially because there were fewer entries available
than requested.
User Action: None. This warning message should not appear.
DIAGPACK,

disk is a diagnostic pack

Facility: INIT, INITIALIZE Volume Command or BACKUP, Backup Utility
Explanation: Either the DCL command INITIALIZE was entered to initialize
a volume that is identified as a diagnostic volume, or a Backup Utility
operation was attempted using a volume identified as a diagnostic volume. In
either case, the volume cannot be used.
User Action: Retry the operation using another volume.
DIALINNOT,

diagonal line not allowed

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: The vertices specified will result in a diagonal, rather than a
vertical or horizontal line.
User Action: Specify the vertices so that the line drawn will be vertical or
horizontal.
DIFTYP,

expected 'library type' 'library spec.' to be 'library type'

Facility: LIBRAR, LIBRARY Command
Explanation: This warning message is generated by the DCL command
LIBRARY. The referenced library is actually of a different type from that
indicated in the command string. Processing continues based on the actual
library type.
User Action: None. Processing continues based on the actual library type.

2-123

DIFVAL,

memory contains different value than specified

Facility: PATCH, VAX Image File Patch Utility
Explanation: The value specified is not contained within the given memory
location.
User Action: Correct the value and retry.
DIGITAL Standard Runoff Version V2.0: n diagnostic message(s) reported
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: This is a standard error message line that specifies the actual
number of error messages output.
User Action: For more information refer to the specific error messages
accompanying this message.
DIGITAL Standard Runoff Version V2.0: No errors detected
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: This message indicates the successful processing of a file by
DSR.
User Action: None.
DIR,

error in directory name
Facility: RMS, VAX Record Management Services
Explanation: A directory name was specified incorrectly. For example, a
directory or subdirectory name string contained more than 39 characters. Or,
use of a logical name resulted in more than one directory name in the file
specification.
User Action: Verify the syntax of either the directory name in the file
specification or the logical name, if a logical name was specified.

DIRALLOC,

directory allocation failure

Facility: SYSTEM, VAX/VMS System Services
Explanation: The file system failed to allocate space to increase the size of
a directory file. Because directory files must be contiguous, this error may
be caused either by the disk being too full, or, more likely, by the disk's free
space being fragmented.
User Action: Reorganize the disk's free space by copying it with BACKUP, or
restructure your application to use a larger number of smaller directories.
DIRECT,

invalid directory syntax - check brackets and other delimiters

Facility: CLI, Command Language Interpreter (DCL)
Explanation: The directory name in a file specification entered for a
command contains an illegal character. Or, a command that expects a
directory name string did not find square brackets ([ ]) or angle brackets
( < > ) in the specified parameter. Note that this error can occur if a physical
device name is specified without a colon terminating it.
User Action: Verify the directory name (or logical name, if a logical name
was specified) for a spelling error. Correct the directory syntax and reenter
the command.

Messages

DIRE—ERROR,

above error occurred writing directory, volume might be
corrupted

Facility: EXCHANGE, Exchange Utility
Explanation: The EXCHANGE utility encountered an error writing the
directory of the volume. A more specific error message is printed immediately
before this message.
User Action: Since EXCHANGE might have already modified the volume
in some way, it is possible that the directory stored on the volume does not
match the current contents of the volume. It is possible to save all the files
by creating a virtual volume and copying all files from the possibly corrupted
volume. Note that this copy must be made before exiting EXCHANGE.
DIRENTRY,

ACP failed to find same directory entry

directory is full

Facility: SYSTEM, VAX/VMS System Services
Explanation: An error occurred while a disk file was being created because
the directory specified is full and cannot catalog any more entries. The
maximum size of a directory file is 1024 blocks.
If associated with a DECnet-VAX operation, this message indicates that the
directory of declared network names is full.
User Action: Delete or purge unwanted files from the directory and repeat
the request; specify a different directory for the output file; or organize the
directory into subdirectory levels to obtain more cataloging space.
DIRNAME,

directory file 'file-spec' is not named '.DIR;1'

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the specified file was marked with
the DIRECTORY file characteristic, but did not have a file type of DIR and a
version number of one. VAX RMS cannot recognize the file as a directory.
User Action: Use the DCL command RENAME to rename the file.
DIRNOTCRE,

'output file' directory file not created

Facility: SHR, SET Facility Shared Messages
Explanation: A request to create a directory file over the network has failed.
User Action: None. The creation of directory files over the network is
currently unsupported.

2-125

Messages

DIRNOTEMPTY,

directory file is not empty

Facility: SYSTEM, VAX/VMS System Services
Explanation: The directory you attempted to delete cannot be deleted
because it contains files.
User Action: Be certain that you want to delete the directory. Then, delete
all the files in the directory first. If the directory is corrupted, use the DCL
command SET FILE/NODIRECTORY to remove its status as a directory.
DIRSYNX,

directive syntax error

Facility: MACRO, VAX Macro Assembler
Explanation: The directive contained a syntax error.
User Action: Correct the syntax of the directive.
DISCON,

error disconnecting link to listener

Facility: NCP, Network Control Program
Explanation: An error occurred while disconnecting the link to NML.
Information accompanying this message explains any secondary reasons
for this error.
User Action: Take corrective action based on the accompanying information.
DISCONNECT,

process is disconnected from requested interrupt vector

Facility: SYSTEM, VAX/VMS System Services
Explanation: A connection is already outstanding for the device, or the driver
cannot reallocate AST control blocks quickly enough. The latter condition can
occur because insufficient AST control blocks (P6 argument) were specified,
not enough pool space is available for the requested AST control blocks, or
the process ASTCNT quota is exhausted.
On a write request, a loss of carrier signal was detected on the Ethernet cable.
User Action: None.
Check the Ethernet cable for proper operation. Check the DEUNA hardware
for proper operation. Check the H400 or other Ethernet transceiver for proper
operation.
DISKCLASS,

Fatal error detected by Disk Class driver (DUDRIVER)

2-126

Messages

DISKFRAG,

free space on 'device' is too fragmented

Facility: BACKUP, Backup Utility
Explanation: The number of free extents on the specified volume was
unreasonably large. The volume cannot be used as a save set disk.
User Action: Reinitialize the volume or select another volume and retry the
operation.
DISKS,

disks

all of the volumes have been dismounted

Facility: MOUNT, MOUNT Command
Explanation: All of the volumes mounted by this invocation of $MOUNT or
the MOUNT command have been dismounted because of errors that were
detected after the volumes had been mounted. Messages explaining the
nature of the error that forced the dismount usually precede this message.
User Action: Take the corrective measures mandated by the error messages
preceding DISMAL, and reissue the MOUNT request.
DISMOUNTD,

volume 'volume name' of volume set 'volume set name'
dismounted

Facility: MOUNT, MOUNT Command
Explanation: The specified volume of the specified volume set has been
dismounted because of errors encountered in processing the volume after it
was mounted. An error with part of a volume set causes the entire volume
set to be dismounted. This message appears for each member of the volume
set that was dismounted due to the error condition. Only those volumes that
were mounted by this invocation of the MOUNT command are listed. If the
volume set name is not available, the string "name n/a" appears as the name
of the volume set.
A message describing the error that caused the volume to be dismounted
usually precedes this message.
User Action: Correct the error condition specified in the accompanying
message and reissue the MOUNT command.
DISMPART,

some of the volumes have been dismounted

Facility: MOUNT, MOUNT Command
Explanation: Some, but not all, of the volumes that were mounted by this
invocation of $MOUNT or the MOUNT command have been dismounted due
to errors detected after the volumes had been mounted. Preceding messages
explain the nature of the error that forced the dismount. Also preceding this
message is a list of the volumes that were dismounted.
User Action: Take the corrective measures mandated by the error messages
preceding DISMPART, and reissue the MOUNT request.

2-127

Messages

DISPERR,

error during display or summary output

Facility: MONITOR, Monitor Utility
Explanation: An error occurred while displaying the requested MONITOR
data to the SYS$OUTPUT device, or while performing output operations to
the summary file. To obtain more information, examine the accompanying
linked message.
User Action: Correct the error indicated by the linked message and rerun
the MONITOR command. Usually, this message represents a status
value returned to MONITOR from one of the Run-Time Library terminalindependent screen procedures.
DIVBY_ZER,

division by zero

Facility: STR, Run-Time Library String Procedures
Explanation: The string arithmetic routines attempted to take the reciprocal
of a string whose numeric value was zero.
User Action: The user should ensure that any string used as a divisor is not
a null string or any other string whose numeric value is zero.
DIVBYZERO,

Divide by zero

Facility: VAX Text Processing Utility
Explanation: Division by zero is not permitted.
User Action: None is required. However, you may want to check the
program for attempts to divide by zero and correct any occurrences you find.
DIVBYZERO,

division by zero error

Facility: MACRO, VAX Macro Assembler
Explanation: An expression contained a division by zero.
User Action: Change the values in the expression.
DIVZERO,

attempt to divide by zero

Facility: PATCH, VAX Image File Patch Utility and DEBUG, VAX/VMS
Debugger
Explanation: An expression contained a division by zero.
User Action: Correct the value and retry the operation.
DIVZERO,

attempt to divide by zero

Facility: PATCH, VAX Image File Patch Utility and DEBUG, VAX/VMS
Debugger
Explanation: An expression contained a division by zero.
User Action: Correct the value and retry the operation.

2-128

Messages

DME,

dynamic memory exhausted

Facility: RMS, VAX Record Management Services
Explanation: Available memory was exhausted during a VAX RMS operation.
Possibly the related I/O segment in the control region is too full for direct
access to a process permanent file; the program region cannot be used for
I/O buffers; there are too many indirect command levels; or, the program has
reached virtual memory limitations.
User Action: Check that the program has not grown excessively large as the
result of a programming error. Relink the image to allow VAX RMS buffers in
the program region or a larger image I/O section.
DNA,

invalid default file name string address

Facility: RMS, VAX Record Management Services
Explanation: The default file specification string address field in the FAB is
not valid, or is in an area of memory that cannot be read by the caller.
User Action: Check for a programming error. Verify that the call to the VAX
RMS service was coded correctly.
DNF,

directory not found
Facility: RMS, VAX Record Management Services
Explanation: The specified directory name does not exist on the specified
device.
User Action: The status value (STV) field of the FAB contains a system error
code that provides additional information. Verify that both the device and
directory are specified correctly. Create a directory on the device, if necessary,
or specify an existing directory.

DNR,

device not ready, not mounted, or unavailable

Facility: RMS, VAX Record Management Services
Explanation: An input/output operation cannot be performed because the
physical device is not ready, the required volume has not been mounted, the
device has been allocated to another user, or a file header on the volume has
been corrupted.
User Action: Make sure that the volume is physically loaded, the device is
ready, and the DCL command MOUNT has completed successfully. Check
that the correct controller is set on the drive. Then retry the command or
program. If the error reoccurs, and the volume is a structured disk, run the
Verify Utility (the DCL command ANALYZE/DISK_STRUCTURE) on the
volume to check for file header corruption.
DNS,

.NO SPACE illegal in this context
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: A .NO SPACE command has been inserted following a
command that issues a .BREAK.
User Action: Remove the .NO SPACE command, or put it in the correct
place.

2-129

Messages

Do you want to create a new file?
Facility: AUTHORIZE, Authorize Utility
Explanation: The Authorize Utility is prompting you for an answer.
User Action: Respond YES (Y) or NO (N)
DOESNTFIT,

'string7 will not fit at current indentation level

Facility: DSRINDEX, DIGITAL Standard Runoff Indexing Utility
Explanation: The indicated string will not fit on a line with the proper
indentation of the index entry or subentry.
User Action: Hyphenate the word using the .HYPHENATE and .BREAK
flags.
DONEMSG,

system authorization file modified

Facility: AUTHORIZE, Authorize Utility
Explanation: This is an informational message.
User Action: No user action is required.
DOSll—BADLABEL,

volume on 'tapedrive7 has label with invalid format

Facility: EXCHANGE, Exchange Utility
Explanation: The EXCHANGE utility received an error trying to read a
DOS-11 magtape label, or the label did not have a valid format.
User Action: In the case of an input error, a second message will follow the
BADLABEL message. Take corrective action based on the following message.
In the case of invalid format, the tape mounted on the drive is not a valid
DOS-11 volume. Find and mount the correct DOS-11 tape and retry the
operation.
DOSll—BLOCKSIZE,

volume on 'tape7 has block larger than 512 bytes

Facility: EXCHANGE, Exchange Utility
Explanation: While reading a DOS-11 magtape, the EXCHANGE utility has
read a block which is longer than 512 bytes.
User Action: The file containing the long block cannot be processed by
EXCHANGE.
DOSll—IOERROR,

error during I/O on volume 'volume7

Facility: EXCHANGE, Exchange Utility
Explanation: The EXCHANGE utility encountered an error during input or
output on a DOS-11 magtape volume.
User Action: A second message describing the actual error condition will
follow this message. Take corrective action based on the contents of the
second message.

2-130

Messages

DOS 11—POSITION,

rewinding tape to recover correct positioning

Facility: EXCHANGE, Exchange Utility
Explanation: The EXCHANGE utility has lost its position on a DOS-11
magtape, usually due to an input or output error.
User Action: EXCHANGE will rewind the tape and move to the correct
position. Please wait for this to complete.
DOUBLDALOC,

Double deallocation of swap file space

Double deallocation of memory block

device positioning error
Facility: RMS, VAX Record Management Services
Explanation: A magnetic tape file is not positioned properly.
User Action: Depending on the operation, the status value (STV) field in the
FAB or RAB contains a status code that provides additional information about
the condition. Take corrective action based on this status code. Retry the
operation. If the error persists, it may indicate a system software or hardware
failure. Notify your system operator or manager.

DRIVENAM,

driver name is 'driver name'

Facility: SYSGEN, System Generation Utility
Explanation: This message is issued with the message SYSVERDIF to identify
the driver.
User Action: See the SYSGEN message SYSVERDIF for user action
information.

2-131

DRVERR,

fatal drive error

Facility: SYSTEM, VAX/VMS System Services
Explanation: An input or output operation failed because of an error in a
disk or magnetic tape drive. If this message is associated with a status code
returned by a request to a DR11-W interface, a fatal error that affects all
DR11-W activity was set in the DR11-W CSR on completion of the QIO
request. Look at the third and fourth words of the IOSB (CSR and EIR) for
the specific cause of the error. If the condition indicated in the CSR can be
cleared, that is, if the ATTN bit can be cleared, SS$_DRVERR is returned. If
the condition cannot be cleared, SS$_CTRLERR is returned. In both cases,
the driver performs a device reset to the DR11-W.
If this message is returned by a request to a magtape or a disk driver, it is a
drive-related error. One or more of the following conditions can cause this
error:
•

Drive or driver timing error

•

Illegal function

•

Illegal register

•

Operation incomplete

•

Write clock failure (disk driver-specific)

•

Nonexecutable function (magnetic tape-specific)

•

Unrecovered reproducible error (magnetic tape-specific)

User Action: Check the status of the device and reenter the command.
Verify that the drive is on, loaded, and mounted correctly. If the failure
persists, notify the system manager.
DRVRSTRT,

error while issuing startup command to driver

Facility: CNF, NI Configurator
Explanation: An error occurred while attempting to issue the startup
commands to the NI driver in preparation to reading the broadcast system ID
messages.
User Action: See the accompanying message to determine the appropriate
action.
DSAQUOTA,

error disabling quota processing

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility encountered an error during an attempt to
disable quota processing. The accompanying message provides additional
information.
User Action: None. Quota processing remains enabled.

Messages

DSTNESDEP,

DST nesting depth too deep in module xxx

Facility: DEBUG, VAX/VMS Debugger
Explanation: Debug Symbol Table nesting depth is too deep in the specified
module. This occurs if routine nesting or data record nesting is very deep in
the user program.
User Action: Simplify the user program and run again.
DTP,

invalid key data type for key = 'nnn'
Facility: RMS, VAX Record Management Services
Explanation: The key data type specified in a key definition XAB is not a
valid data type code. The valid key data codes are: STG (default), BN2, BN4,
BN8, IN2, IN4, IN8, and PAC.
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 VAX RMS service
was coded correctly.

DUALLOC,

dual allocation on volume V

Facility: MOUNT, MOUNT Command
Explanation: A logical block on the relative volume identified in the message
is allocated to more than one file.
User Action: Use the DCL command ANALYZE/DISK-STRUCTURE with
the /NOREPAIR qualifier (ANALZYE/DISK-STRUCTURE/NOREPAIR)
on the volume. This command invokes the Verify Utility, which issues a
message for each occurrence of dual file allocation. Verify Utility messages
identify the file name, the range of logical block numbers that have been
dually allocated, and the virtual block numbers that the logical blocks map
to. You can examine the messages to determine the files involved in each
case of dual allocation. Then, without allowing other file activity, copy all but
one file involved in each case of dual allocation to a new version. After you
create new versions of the applicable files, delete the versions containing dual
allocation. In this way, blocks that are not actually free are marked as free
blocks in the storage bit map. Next, rerun the Verify Utility on the volume,
using the /REPAIR qualifier (ANALZYZE/DISK_STRUCTURE/REPAIR).
Finally, examine each file and reconstruct from backup media those files that
have been corrupted.
DUMPEMPTY,

dump file contains no valid dump

Facility: SDA, System Dump Analyzer
Explanation: The SDA cannot read the contents of the system dump file.
The system dump file may be unreadable because the data is bad or because
the file is empty.
User Action: None. If the SDA cannot read the dump file, it will not run.

DUP,

duplicate key detected (DUP not set)
Facility: RMS, VAX Record Management Services
Explanation: A VAX RMS $PUT or $UPDATE operation specified a record
that contained one or more key values that duplicated key values in other
records, and the key does not have the DUPLICATES ALLOWED attribute.
User Action: Either reorganize the file and specify that duplicate keys are
allowed, or modify the source program to detect and respond to the condition.

DUP,

duplicate key encountered
Facility: CONVERT, Convert Utility
Explanation: More than one record in the input file has the same value in a
key field, but duplicate keys are not allowed.
User Action: Either allow duplicate keys or change the key values.

DUPBLKNUM,

duplicate block number 'dddddddd', already exists in 'xDBSF'

Facility: BAD, Bad Block Locator Utility
Explanation: The block number specified in the /BAD—BLOCKS list is
already recorded in either the MDBSF or the SDBSF.
User Action: None. The block is ignored, and processing continues.
DUPBUFNAME,

Buffer 'name' already exists

Facility: VAX Text Processing Utility
Explanation: The first argument for the built-in procedure CREATE—BUFFER
must be a unique string. You have specified a name that already exists.
User Action: Reenter the command with a different string as the first
argument.
DUPCOMFIL,

command file 'file-spec' already being written

Facility: PATCH, VAX Image File Patch Utility
Explanation: You have already requested that a command procedure be
written for this PATCH session.
User Action: None.
DUPDEF,

duplicate definition of 'name' encountered

Facility: CDU, Command Definition Utility
Explanation: CDU encountered a DEFINE statement in which there was
already a definition with the same name.
User Action: Edit the CLD file so that all definitions use unique names.
DUPDEVSPC,

duplicate device specified

Facility: MOUNT, MOUNT Command
Explanation: The same tape device was specified more than once in a list of
tape devices for the DCL command MOUNT.
User Action: Reenter the MOUNT command specifying each device only
once.

Messages

DUPDSKQUOTA,

duplicate disk quota file entry

Facility: SYSTEM, VAX/VMS System Services
Explanation: Another quota entry for the specified UIC already exists.
User Action: Check the UIC listed. Correct the UIC or select and reenter
another UIC.
DUPFILENAME,

duplicate file name

Facility: SYSTEM, VAX/VMS System Services
Explanation: The directory specified already contains an entry for the
specified file name, file type, and version number.
User Action: Delete the existing file, or correct the command or program to
change the file name, file type, or version number specified for the output file.
DUPFORM,

duplicate form number

Facility: JBC, Job Controller
Explanation: A DEFINE/FORM command specified a form number that was
already defined. Each form must have a unique number.
User Action: Specify the command so that each form is defined uniquely.
DUPGLOBAL,

global symbol 'symbol name' from file 'library file-spec' already in
library 'library file-spec'

Facility: LIBRAR, LIBRARY Command
Explanation: This error message is generated by the DCL command
LIBRARY. An attempt was made to insert an object module containing a
global symbol that was already in the global symbol table (GST).
User Action: Replace the module instead of inserting it; or remove the global
symbol from the library before inserting the module.
DUPIDENT,

only one IDENT statement is allowed

Facility: CDU, Command Definition Utility
Explanation: More than one IDENT statement was encountered in a single
CLD file. Only one IDENT statement is allowed.
User Action: edit the CLD file so that there is only one IDENT statement.
DUPKEY,

duplicate key in index

Facility: LBR, Librarian Subroutine Package
Explanation: This message is generated by the Librarian routines. On a call
to LBR$INSERT_KEY, the specified key was found to exist already.
User Action: Call LBR$REPLACE__KEY to replace the existing key.

2-135

Messages

DUPKEY,

keyword 'keyword-name' has already been defined

Facility: CDU, Command Definition Utility
Explanation: CDU encountered a KEYWORD definition that conflicts with an
existing KEYWORD definition with the same name. KEYWORD definitions in
the same TYPE definition must be unique.
User Action: Edit the CLD file so that each KEYWORD definition in the same
TYPE definition is unique.
DUPKEYMAP,

Attempt to define a duplicate key map 'key-map-name'

Facility: VAX Text Processing Utility
Explanation: You are trying to create a key map with the same name as a
key map or key-map list that already exists.
User Action: Select another name for the new key map.
DUPKEYMAPLIST,

Attempt to define a duplicate key-map list 'key-map-listname'

Facility: VAX Text Processing Utility
Explanation: You are trying to create a key-map list with the same name as
a key map or key-map list that already exists.
User Action: Select another name for the new key-map list.
DUPLABEL,

only one LABEL clause is allowed

Facility: CDU, Command Definition Utility
Explanation: CDU encountered more than one LABEL clause in a single
qualifier/parameter definition. Only one LABEL clause is allowed per
qualifier/parameter definition.
User Action: Edit the CLD file so that each qualifier/parameter definition
does not contain more than one LABEL clause.
DUPLICATE,

ACE already exists in ACL

Facility: ACLEDIT, Access Control List Editor
Explanation: The ACE being entered already exists in the ACL.
User Action: Either delete the ACE or alter it so that it is no longer a
duplicate.
DUPLNAM,

duplicate process name

Facility: SYSTEM, VAX/VMS System Services
Explanation: A process name specified in a request to create a process
duplicates the name of an existing process executing with the same group
number. Process names must be unique within a group.
User Action: Specify an alternative process name. Check whether the
existing process with that name should be deleted and, if so, use the DCL
command STOP to delete it.

2-136

Messages

DUPMOD,

module 'module name' from file 'library file-spec' already in 'library
file-spec'

Facility: LIBRAR, LIBRARY Command
Explanation: This error message is generated by the DCL command
LIBRARY. The module you are inserting into the library already exists in
the module name table (MNT).
User Action: Change the name of the module or replace the existing module
with a new one.
DUPMODULE,

module 'module-name' from file 'file-name' already in 'name'

Facility: LIBRAR, LIBRARY Command
Explanation: One of the modules being inserted into the library already
exists in the library module name table.
User Action: Change the name of the module being inserted, delete the
module of the same name from the library, or use the LIBRARY/REPLACE
option to replace the module.
DUPMODULE,

only one MODULE statement allowed

Facility: CDU, Command Definition Utility
Explanation: More than one MODULE statement was encountered in a
single CLD file. Only one MODULE statement is allowed.
User Action: Edit the CLD file so that there is only one MODULE statement.
DUPMSG,

message code nn already assigned as ss

Facility: MESSAGE, Message Utility
Explanation: You have assigned the same message code (nn) to more than
one message symbol. The first message symbol (ss) assigned to the message
code is shown.
User Action: Check that you have not assigned twice the same message
number or symbol for the same facility. Reenter the message definition(s) so
a different message symbol is assigned to one message code.
DUP—OUTPUT,

output file has already been specified

Facility: SORT, VAX SORT/MERGE Utility
Explanation: You passed the output file argument in the routine package
more than once.
User Action: Check your file arguments and verify that you specified the
output file only once.
DUPPLACE,

only one PLACEMENT clause is allowed

Facility: CDU, Command Definition Utility
Explanation: CDU encountered more than one PLACEMENT clause in a
single qualifier definition. Only one PLACEMENT clause is allowed per
qualifier definition.
User Action: Edit the CLD file so that each qualifier definition does not
contain more than one PLACEMENT clause.

2-137

DUPPREFIX,

only one PREFIX clause is allowed

Facility: CDU, Command Definition Utility
Explanation: CDU has encountered more than one PREFIX clause in a single
verb/syntax definition. Only one PREFIX clause is allowed per verb/syntax
definition.
User Action: Edit the CLD file so that each verb/syntax definition does not
contain more than one PREFIX clause.
DUPPROMPT,

only one PROMPT clause is allowed

Facility: CDU, Command Definition Utility
Explanation: CDU encountered more than one PROMPT clause in a single
parameter definition. Only one PROMPT clause is allowed per parameter
definition.
User Action: Edit the CLD file so that each parameter definition does not
contain more than one PROMPT clause.
DUPQUAL,

qualifier 'qualifier-name' has already been defined

Facility: CDU, Command Definition Utility
Explanation: CDU has encountered a previously defined qualifier in a
single verb/syntax definition. All qualifiers defined in a single verb/syntax
definition must be unique.
User Action: Edit the CLD file so that all qualifiers defined in a single verb
/syntax definition are unique.
DUPRVN,

duplicate volume number already mounted

Facility: MOUNT, MOUNT Command
Explanation: A volume of the same relative volume number and the same
volume set name is already mounted. You are trying to mount a volume that
belongs to a volume set with the same name as a volume set that is already
mounted.
User Action: Make sure that you have mounted the correct volume. Verify
that you are defining the volume status (/SHARE, /NOSHARE, /GROUP, or
/SYSTEM) consistently with volumes already mounted.
DUPSYM,

'name' is a duplicate symbol definition

Facility: CDU, Command Definition Utility
Explanation: The same name was used twice. For example, this error could
occur because the same syntax list or qualifier name appears twice in the CLD
file.
User Action: Modify the CLD file to correct the duplication.

Messages

DUPSYM,

duplicate symbol definition

Facility: MESSAGE, Message Utility
Explanation: You have assigned the same symbol to represent two values.
This message may refer to symbols defined in a message definition, a facility
definition, or the .LITERAL directive.
User Action: Reenter your source statements with each symbol defined only
once.
DUPSYNTAX,

only one SYNTAX clause is allowed

Facility: CDU, Command Definition Utility
Explanation: CDU encountered more than one SYNTAX clause in a single
qualifier/parameter definition. Only one SYNTAX clause is allowed per
qualifier/parameter definition.
User Action: Edit the CLD file so that each qualifier/parameter definition
does not contain more than one SYNTAX clause.
DUPTYPE,

only one TYPE clause is allowed

Facility: CDU, Command Definition Utility
Explanation: CDU encountered more than one TYPE clause in a single value
definition. Only one TYPE clause is allowed per value definition.
User Action: Edit the CLD file so that each value definition does not contain
more than one TYPE clause.
DUPUNIT,

MSCP Controller - duplicate unit number

Facility: SYSTEM, VAX/VMS System Services
Explanation: On a STARTUP request, the user cannot assign two channels to
an XE unit before the unit is started in SHARED mode. The driver may have
to relink the user's Channel Control Block (CCB) to a different UCB and this
cannot be done if there are two CCBs that must be reset.
User Action: The user must STARTUP the XE unit in SHARED mode, before
assigning any extra channels to the XE unit.
DUPVALUE,

only one VALUE clause is allowed

Facility: CDU, Command Definition Utility
Explanation: CDU encountered more than one VALUE clause in a single
qualifier/parameter definition. Only one VALUE clause is allowed per
qualifier/parameter definition.
User Action: Edit the CLD file so that each qualifier/parameter definition
does not contain more than one SYNTAX clause.

2-139

Messages

DUPVOLNAM,

volume label already present in set

Facility: MOUNT, MOUNT Command
Explanation: During an attempt to add a volume to an existing volume
set, the specified volume set was found to contain a volume with the label
specified.
User Action: Verify the labels on the existing volumes in the set. Choose a
new label for the volume you are adding to the set, reinitialize the volume,
and reenter the DCL command MOUNT/BIND.
DVI,

invalid device ID value in NAM block
Facility: RMS, VAX Record Management Services
Explanation: The device identification field of the VAX RMS NAM block is
not valid.
User Action: Verify that the call to the VAX RMS service was coded correctly.

DVN,

Duplicate variable name: 'string'

Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: An attempt has been made to use a name specification
with a .VARIABLE command that has already been used with a previous
.VARIABLE, .IF, .IFNOT, or .ELSE command.
User Action: Change the name specification.
DX1,

In-core indexing (.DO INDEX/.PRINT INDEX) is no longer supported
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: In-core indexing is no longer supported.
User Action: See accompanying message.

DX2,

Instead, specify RUNOFF/INTERMEDIATE and .REQUIRE 'file.RNX' here.
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: In-core indexing is no longer supported. See accompanying
message.
User Action: Specify RUNOFF/INTERMEDIATE and .REQUIRE 'file.RNX'.

ECONOTSET,

eco level 'nn' not set in 'file-spec'

Facility: PATCH, VAX Image File Patch Utility
Explanation: You specified an ECO level that has not been set in that
particular image file. This typically occurs when you issue the PATCH
command CHECK ECO before issuing the PATCH command UPDATE.
User Action: Issue a SET ECO command to reenable the Patch Utility's
command processing. Specify the correct ECO level and retry the operation.

2-140

Messages

ECOSET,

eco level 'nn' already set in 'file-spec'

Facility: PATCH, VAX Image File Patch Utility
Explanation: You specified an ECO level that has already been set in that
particular image file.
User Action: Issue a SET ECO command to reenable the Patch Utility's
command processing. Specify the correct ECO level and retry.
Editor aborted
Facility: EDT, EDT Editor
Explanation: EDT experienced some difficulties and had to abort the session.
User Action: Use the journal file to recover your editing work.
EDITPROC,

error creating or executing editor subprocess

Facility: MAIL, Personal Mail Utility
Explanation: You entered the SEND/EDIT command and MAIL'S attempt
to create a subprocess failed. This message is issued with an accompanying
message.
User Action: Take corrective action based on the accompanying message.
EDITSCLSH,

edits clash 'editing commands' 'files specifications'

Facility: SUMSLP, SUMSLP Batch Editing Utility
Explanation: Two or more conflicting editing commands have been entered,
that is, more than one edit operation has been specified for one line of
source code. The relevant editing commands and the file specifications of the
SUMSLP command files are listed following the message.
User Action: None. This message is informational.
EDOUTSEQ,

edits out of sequence

Facility: SUM, Source Update Merge Utility and SUMSLP, SUMSLP Batch
Editing Utility
Explanation: The indicated edit command was not in ascending sequence
within the update file. The editing operation has been performed correctly.
User Action: Edit the update file to place the edit in the correct position.
EF—ALRFRE,

event flag already free

Facility: LIB, Run-Time Library General Procedures
Explanation: A call was made to LIB$FREE_EF to free an event flag number
that was not allocated.
User Action: Ensure that you use the correct event flag number in the call to
LIB$FREE_EF.

2-141

EF_ALRRES,

event flag already reserved

Facility: LIB, Run-Time Library General Procedures
Explanation: A call was made to LIB$RESERVE_EF to receive an event flag
number that was already allocated.
User Action: Ensure that you use the correct event flag number in the call to
LIB$RESERVE_EF.
EFD,

.END FOOTNOTE doesn't terminate .FOOTNOTE
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: A .ENDFOOTNOTE command is improperly positioned in the
file; it does not follow associated footnote data.
User Action: Put the .ENDFOOTNOTE command in the correct place, or
remove it.

EF—RESSYS,

event flag reserved to system

Facility: LIB, Run-Time Library General Procedures
Explanation: A call was made to LIB$RESERVE_EF to reserve an invalid
event flag number. The range for valid event flag numbers is 1 through 23
and 32 through 63.
User Action: Retry specifying a valid event flag number.
ELD,

.END LITERAL doesn't follow .LITERAL
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: The .END LITERAL command is improperly positioned in the
file; it does not follow the .LITERAL command.
User Action: Put the .END LITERAL command in the correct place, or
remove it.

EMPTYDEF,

no attributes supplied - DEFINE ignored

Facility: CDU, Command Definition Utility
Explanation: The CLD file does not contain any attributes.
User Action: Add attributes to the CLD file.
EMPTYFILE,

no modules found in file 'file-name'

Facility: LINK, VAX Linker
Explanation: An object file contained no object modules.
User Action: Ensure that the source file compiled properly and that the
output object file is not empty.
EMPTYFILE,

zero-length page or swap file cannot be installed

Facility: SYSGEN, System Generation Utility
Explanation: You attempted to install a zero-length page or swapping file.
User Action: None. You cannot install a zero-length page or swapping file.

Messages

EMPTYHIST,

Library update history is empty

Facility: LBR, Librarian Subroutine Package
Explanation: The library has an update history, but no update history records
are present.
User Action: None.
EMPTYIN,

empty input file 'file-name'

Facility: DSRTOC, DIGITAL Standard Runoff Table of Contents Utility
Explanation: The input file contained no data for processing.
User Action: Edit the input file.
EMPTYJOB,

no files specified in job request

Facility: JBC, Job Controller
Explanation: A batch or print job was requested that did not specify any
files to process. This error condition occurs if the requesting process opened
and closed a job using the SJC$_CREATE_JOB and SJC$__CLOSE_JOB
functions, but did not specify any files with the SJC$_ADD_FILE function
of the $SNDJBC system service. This condition causes the open job to be
removed from the system job queue file.
User Action: None.
EMPTYKMLIST,

Key-map list 'key-map-list-name' does not contain any key
maps

Facility: VAX Text Processing Utility
Explanation: You are referring to a key-map list that has no key maps.
User Action: Enter the built-in procedure SHOW (KEY_MAP_LISTS) on the
command line to obtain the names of the key-map lists and their key maps.
EMPTYLIBRARY,

no modules in library: 'library-filespec'

Facility: LIBRAR, LIBRARY Command
Explanation: The library being compressed contains no modules.
User Action: None.
EMPTYLST,

known file entry list is empty

Facility: INSTALL, Install Utility
Explanation: There are no entries in the known file entry list. Therefore,
LIST, DELETE, REMOVE, and PURGE will have no effect.
User Action: None.
EMSKNOTABS,

entry mask not absolute

Facility: MACRO, VAX Macro Assembler
Explanation: The entry mask expression was not absolute or it contained
undefined symbols.
User Action: Change the values in the expression.

2-143

Messages

ENAQUOTA,

error enabling quota processing

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility encountered an error during an attempt to
enable quota processing. The accompanying message provides additional
information.
User Action: None. The Verify Utility will not reconstruct disk quota
information.
END,

control returned to node 'node-name'

Facility: REM, Set Host Facility
Explanation: This is an information message issued when a remote terminal
session is ended.
User Action: None. This message is informational.
ENDABORT,

'name' compilation aborted

Facility: Shared by several facilities
Explanation: Serious errors prevented the compilation of 'name' from being
completed.
User Action: Correct the errors and recompile.
ENDDIAGS,

'name' completed with 'nnn' diagnostic(s)

Facility: Shared by several facilities
Explanation: The compilation or assembly of 'name' was completed with
diagnostics. Use of the object module produced may give invalid results.
User Action: Correct the conditions which resulted in the diagnostics and
recompile or reassemble.
ENDED,

'name' ended

Facility: Shared by several facilities
Explanation: A program phase has been ended.
User Action: None.
ENDEDD,

'name' ended at 'system date and time'

Facility: Shared by several facilities
Explanation: A program phase has been ended.
User Action: None.
ENDEDT,

'name' ended at 'system time'

Facility: Shared by several facilities
Explanation: A program phase has been ended.
User Action: None.

2—144

Messages

ENDNOOBJ,

'name' completed with 'nnn' diagnostic(s)-object deleted

Facility: Shared by several facilities
Explanation: The compilation or assembly of 'name' was completed with
errors. No object file was produced.
User Action: Correct the source language errors and recompile or reassemble.
ENDOFBUF,

Attempt to move past the end of buffer 'buffer name'

Facility: VAX Text Processing Utility
Explanation: You attempted to move past the end of the current buffer.
VAXTPU makes offset 0 of the end-of-buffer mark the current editing
position.
User Action: Stop trying to move forward. You are already positioned at the
end of the buffer.
ENDOFFILE,

end of file

Facility: SYSTEM, VAX/VMS System Services
Explanation: You received this message because of one or more of the
following conditions:
•

A tape mark indicating end-of-file was encountered during an attempt to
read a tape. For data transfer functions, the byte count is zero; for skip
record functions, the count is the number of blocks skipped.

•

An end-of-file card was encountered during an attempt to read from the
card reader.

•

A mailbox is empty or had an end-of-file (IO$_ENDOFFILE) written to it.

•

No data is available for transfer on the DMC-11, and IO$M_NOW was
specified.

•

The file system ACP encountered the end of the allocated space for a
virtual I/O operation or an attempted truncation.

User Action: Note the condition. If necessary, modify the source program to
detect and respond to the condition.
ENDOFFILE,

End of file on read to terminal or file

Facility: VAX Text Processing Utility
Explanation: Premature end-of-file encountered on read from input device or
file.
User Action: Submit a Software Performance Report.
ENDOFTAPE,

end of tape

Facility: SYSTEM, VAX/VMS System Services
Explanation: The end of tape marker, indicating the physical end of the tape,
was encountered.
User Action: Note the condition. If the tape marker was encountered during
an operation in the forward direction, it may be necessary to modify the
source program to detect and respond to the condition.

2-145

ENDOFVOLUME,

end of volume

Facility: SYSTEM, VAX/VMS System Services
Explanation: Two consecutive tape marks were detected during a skip
file operation to a tape mounted nonfile structured or during a skip record
operation. This return is also used as a logical end-of-tape indicator or nonANSI tapes. If an ANSI standard tape is mounted foreign, this may only
indicate an empty file within the volume and not the end of the volume. The
high word of the first longword in the I/O status block contains the number
of tape marks passed.
User Action: Use a read function to read data located past the double
tape mark. (The first read function returns end-of-file status; a second read
function reads the data.)
ENDPRS,

error code of 'xx' on command line parse end

Facility: PATCH, VAX Image File 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.
ENDTOPIC,

Request LBR$OUTPUT_HELP terminate printing

Facility: LBR, Librarian Subroutine Package
Explanation: When a user-supplied output routine is called by
LBR$OUTPUT_HELP, the output routine returns this status to terminate
the printing of help text.
User Action: None.
ENDWRNGMAC,

.ENDM does not end macro 'macro name' in 'library file-spec'

Facility: LIBRAR, LIBRARY Command
Explanation: This warning message is generated by the DCL command
LIBRARY. The macro name following the .ENDM statement does not match
the name of the macro it should end.
User Action: Reformat the macro source file.
ENDWRNGMAC,

statement ends wrong MACRO

Facility: MACRO, VAX Macro Assembler
Explanation: The .ENDM directive specified a different name from its
corresponding .MACRO directive.
User Action: Correct the name in the .ENDM directive to ensure that the
.ENDM directive and .MACRO directive correspond as required.
ENQ,

ENQ system service request failed

Facility: RMS, VAX Record Management Services
Explanation: An ENQ/DEQ facility service invoked by RMS failed; the
specific failure code is in the status value (STV) field of either the FAB or
RAB.
User Action: Correct the condition described in the STV field.

Messages

ENT,

ACP enter function failed
Facility: RMS, VAX Record Management Services
Explanation: An attempt to enter a file specification in a directory failed.
This message is associated with a status code returned from a file system ACP
QIO request made by VAX RMS.
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.

ENTERED,

'file-spec' entered as 'file-spec'

Facility: SET, SET Facility
Explanation: The file has been entered successfully. This message is
displayed when you specify the /LOG qualifier with the SET FILE/ENTER
command.
User Action: None.
ENTERLOST,

file ('file-id') 'file-name' error entering file in directory [SYSLOST]

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility encountered an error during an attempt to
enter the specified file in directory [SYSLOST]. The accompanying message
provides additional information.
User Action: Correct the condition that caused the error and reenter the
Verify Utility command line.
ENTERR,

error entering 'file-spec' as 'file-spec'

Facility: SET, SET Facility
Explanation: An error occurred while attempting to enter a synonym for a
file. This message is accompanied by another message explaining why the
synonym could not be entered.
User Action: Respond to the accompanying message.
ENTFIL,

error entering file on queue

Facility: INPSMB, Input Symbiont
Explanation: The system encountered an error creating a batch job from card
reader input. The accompanying message provides additional information.
User Action: Correct the error and reenter the job.
ENTIDMTCH,

'string' ident of 'string' for entity 'string' in module 'module name'
file 'file name' does not match ident of 'string' in module 'module
name' file 'file name'

Facility: LINK, VAX Linker
Explanation: The specified modules were not compiled with the same
external files (for example, a library).
User Action: Recompile the modules in error.

2-147

ENTIDMTCHB,

'string' ident of 'number,number' for entity 'string' in module
'module name' file 'file name' does not match ident of
'number,number' in module 'module name' file 'file name'

Facility: LINK, VAX Linker
Explanation: The specified modules were not compiled with the same
external files (for example, a library).
User Action: Recompile the modules in error.
ENTIDMTCHO,

object type of 'string' for entity 'string' in module 'module name'
file 'file name' does not match object type of 'string' in module
'module name' file 'file name'

Facility: LINK, VAX Linker
Explanation: You specified different object types.
User Action: Recompile using the same object types.
ENTIDMTCHT,

ident type for entity 'string' in module 'module name' file 'file
name' differs from ident type in module 'module name' file 'file
name'

Facility: LINK, VAX Linker
Explanation: You specified both a binary and string ident for a single entity.
User Action: Recompile, specifying either a binary or string ident, but not
both the same entity.
Entity must be WORD, SENTENCE, PAGE, or PARAGRAPH
Facility: EDT, EDT Editor
Explanation: The EDT command SET ENTITY was entered without one of
the following four entity options: WORD, SENTENCE, PAGE, PARAGRAPH.
User Action: Reenter the command specifying one of the four entity options
displayed in the message text.
ENTNF,

specified entity not found in command tables

Facility: CLI, Command Language Interpreter (DCL)
Explanation: The parameter, qualifier, or keyword specified as input to one
of the CLI$xxxx routines does not exist in the command tables.
User Action: Check the spelling of the entity and its existence in the
command tables.
ENV,

support for RMS service call or feature not present
Facility: RMS, VAX Record Management Services
Explanation: An image attempted a VAX RMS function that was not included
at system generation or is not supported on this version of VAX RMS.
User Action: Consult the system manager to find out which functions are
supported or to include your desired function.

Messages

EOF,

end of file detected
Facility: RMS, VAX Record Management Services
Explanation: An end-of-file condition occurred on a VAX RMS service.
User Action: Note the condition. If necessary, modify the source program to
detect and respond to the condition.

EOF,

end of input
Facility: PSM, Print Symbiont
Explanation: This status is returned by a print symbiont input routine
indicating the end of input.
User Action: None.

EOF,

end-of-file
Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: End of file condition was detected on input.
User Action: If necessary, modify your program to recognize this conditiion
and respond to it.

EOFMISMATCH,

end of file position mismatch for 'file-spec7

Facility: BACKUP, Backup Utility
Explanation: During a compare or verify operation, the end-of-file pointer
for the specified file did not agree with the input file. If other file activity
is occurring on the volume, the error may be caused because another user
modified the file during the backup operation.
User Action: Note that the copies are inconsistent.
EOMERROR,

compilation errors in module 'module-name'

fatal compilation errors in module 'module-name'

2-149

EOMFTL,

link abort specified in module 'module-name' file 'file-name'

Facility: LINK, VAX Linker
Explanation: An object module specified link abort.
User Action: Correct the source for the module, recompile, and relink.
EOMSTK,

'number' items left on Linker internal stack in module 'module-name'
file 'file-name'

Facility: LINK, VAX Linker
Explanation: An object module did not leave the linker stack empty.
User Action: Submit a Software Performance Report on the appropriate
language compiler.
EOMWARN,

compilation warnings in module 'module'

EOT response to text

Facility: SYSTEM, VAX/VMS System Services
Explanation: The IBM system has sent an EOT instead of an expected
acknowledgment to XKDRIVER after receiving a block of data from
XKDRIVER.
User Action: Either a normal condition exists where the IBM host has
acknowledged the receipt of a block of text with an EOT instead of an ACK,
(In this case, you do not need to provide corrective action.), or an error has
occurred. When an error occurs, you may need to correct and retransmit the
last block of data to the IBM host.
EQV—NOTICE,

equivalent name - device 'controller name' will be output as
'controller name'

Facility: SYSGEN, System Generation Utility
Explanation: An equivalent name for a controller was entered with the
SYSGEN command CONFIGURE.
User Action: None. This is informational.
ERASEBLKS,

blocks reclaimed on relative volume N not completely erased

Facility: MOUNT, MOUNT Command
Explanation: While rebuilding a volume set, some of the blocks being
reclaimed could not be erased.
User Action: The accompanying message provides additional information.

Messages

ERASEFAIL,

volume not completely erased

Facility: INIT, INITIALIZE Volume Command
Explanation: INIT encountered at least one error when it attempted to erase
the volume.
User Action: The accompanying message provides additional information.
ERBOXPROC,

'process-name' Error count = 'nnn'

Facility: UETP, User Environment Test Package
Explanation: This message assigns a sequence number, 'nnn', to an error
found by a particular process. The error is described in a subsequent message.
In order to set off the error from other text being printed, a box of asterisks
surrounds this message.

***********************
*
*

‘program name'
Error count = 'nn'

*
*

***********************
User Action: Take action indicated by the messages that follow.
ERRAT—LIN,

error in line 'line-number' at or near 'line-number'

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: General information message included with many Termtable
compiler messages. Attempts to identify specifically where an error occurred.
User Action: Check the specified line in your definition.
ERRCACHFUL,

Error cache is full

error returning input filename from DCL

Facility: MONITOR, Monitor Utility
Explanation: An error occurred during processing of a MONITOR CONVERT
command. The input file specification could not be obtained. Examine the
accompanying message for more information.
User Action: Correct the input file specification and reenter your command.

2-151

Messages

ERRCVTOPN,

error opening input file for conversion

Facility: MONITOR, Monitor Utility
Explanation: An error occurred during processing of a MONITOR CONVERT
command. The specified input file could not be opened.
User Action: This error may occur if the specified input file is incorrect or
inaccessible. Correct the input file specification and reenter your command.
ERREXECOM,

EXECUTE subcommand is not allowed in execute command file

Facility: MONITOR, Monitor Utility
Explanation: A MONITOR EXECUTE command was encountered in a
MONITOR command file. Any Monitor Utility command may appear in a
MONITOR command file except the EXECUTE command.
User Action: Remove the EXECUTE command from the command file, and
reissue the original request.
ERREXEFIL,

error returning execute command filename from DCL

Facility: MONITOR, Monitor Utility
Explanation: An error occurred during processing of a MONITOR EXECUTE
command. The MONITOR command file specification could not be obtained.
More information may be obtained by examining the accompanying message.
User Action: Correct the error indicated by the accompanying message and
rerun the MONITOR EXECUTE command.
ERREXEOPN,

error opening execute command file

Facility: MONITOR, Monitor Utility
Explanation: An error occurred during processing of a MONITOR EXECUTE
command. The MONITOR command file could not be opened.
User Action: This error can occur if the command file specification was
incorrect, or if the file was inaccessible. Correct the file specification and then
reissue the MONITOR EXECUTE command.
ERREXEREA,

error reading execute command file

Facility: MONITOR, Monitor Utility
Explanation: An error occurred while reading a MONITOR command file.
User Action: Reissue the MONITOR EXECUTE command. If the error
reoccurs, check the command file.
ERREXEREP,

error replacing "(a)" with "EXECUTE"

Facility: MONITOR, Monitor Utility
Explanation: An error occurred during processing of a MONITOR command
file. An attempt to translate the string "@" to "EXECUTE" failed. More
information may be obtained by examining the accompanying message.
User Action: Correct the error indicated by the accompanying message and
reexecute the command file. Most such messages represent status values
returned to MONITOR from the Run-Time Library string manipulation
procedures.

2-152

Messages

ERRHALT,

Halt with error interrupt pending

error processing /INPUT file

Facility: MONITOR, Monitor Utility
Explanation: An error occurred while referencing the input recording file. To
obtain more information, examine the accompanying linked messages.
User Action: Correct the error indicated by the linked messages and rerun
the MONITOR command.
ERRLIN,

error in line 'line-number'

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: General informational message included with many Termtable
compiler messages. Attempts to identify specifically which line contained an
error.
User Action: Check the specified line in your definition.
Error closing quota file
Facility: DISKQUOTA, Diskquota Utility
Explanation: This message is issued with other messages.
User Action: Take corrective action based on the accompanying messages.
Error creating quota file
Facility: DISKQUOTA, Diskquota Utility
Explanation: This message is issued with other messages.
User Action: Take corrective action based on the accompanying messages.
ERROR,

error reading parameter file

Facility: SYSGEN, System Generation Utility
Explanation: An irrecoverable I/O error occurred while SYSGEN was
reading a parameter file.
User Action: Reissue the command.

2-153

Messages

Error in command
Facility: EDT, EDT Editor
Explanation: The command entered was invalid
User Action: Enter a valid command.
Error in command option
Facility: EDT, EDT Editor
Explanation: The command entered included a /name qualifier where name
is not a valid option.
User Action: Reenter the command without specifying /name as a qualifier.
Error in range specification
Facility: EDT, EDT Editor
Explanation: The command requires a complete range specification.
User Action: Reenter the command including a complete range specification.
Error initializing quota file
Facility: DISKQUOTA, Diskquota Utility
Explanation: This message is issued with other messages.
User Action: Take corrective action based on the accompanying message.
Error opening terminal for input
Facility: EDT, EDT Editor
Explanation: EDT could not access the specified terminal for input. This
message appears when you are using EDT from a running program.
User Action: After determining why EDT cannot access the specified
terminal, correct the problem.
Error opening terminal for output
Facility: EDT, EDT Editor
Explanation: EDT could not access the specified terminal for output. This
message appears when you are using EDT from a running program.
User Action: After determining why EDT cannot access the specified
terminal, correct the problem.
Error reading from input file
Facility: EDT, EDT Editor
Explanation: EDT cannot read an input file when it started the editing
session. The problem file could be the main input file, the journal file if you
are using the /RECOVER specifier, or the startup command file if you are
using one.
User Action: Determine why the input file cannot be read.

2-154

Messages

Error reading from terminal
Facility: EDT, EDT Editor
Explanation: EDT cannot process the input it is receiving from the terminal.
The message appears when you are using EDT from a running program.
User Action: After determining why EDT cannot process input from the
specified terminal, correct the problem.
Error writing to output file
Facility: EDT, EDT Editor
Explanation: EDT cannot produce an output file. The problem file could be
the MAIN buffer copy, the journal file, or a file requested with the WRITE
command.
User Action: After determining why EDT cannot produce an output file,
correct the problem.
ERRORISUE,

completed with errors

Facility: LINK, VAX Linker
Explanation: The link completed, but errors were detected.
User Action: Correct the errors and relink.
ERRORS,

compilation errors in module 'module-name' file 'file-name'

Facility: LINK, VAX Linker
Explanation: An object module contains compilation errors.
User Action: Correct the source code, then recompile or reassemble.
ERROUTOPN,

error opening conversion file for output

Facility: MONITOR, Monitor Utility
Explanation: An error occurred during processing of a MONITOR CONVERT
command. The specified output file could not be opened.
User Action: This error may occur if the output file specification is incorrect.
Correct the output file specification and reenter your command.
ERRPARSE,

error parsing command

Facility: MONITOR, Monitor Utility
Explanation: An error was detected while parsing a Monitor Utility
command. More information may be obtained by examining the
accompanying message.
User Action: Correct the error indicated by the accompanying message and
reissue the command. To obtain the correct syntax for utility commands,
issue the HELP command in response to the MONITOR > prompt.

2-155

Messages

ERRPROMPT,

error prompting for input

Facility: MONITOR, Monitor Utility
Explanation: An error was detected while prompting the terminal for input.
More information may be obtained by examining the accompanying message.
User Action: Correct the error indicated by the accompanying message and
reissue the command.
ERRRECFIL,

error processing /RECORD file

Facility: MONITOR, Monitor Utility
Explanation: An error occurred while referencing the output recording file.
To obtain more information, examine the accompanying linked messages.
User Action: Correct the error indicated by the linked messages and rerun
the MONITOR command.
ERRROUCAL,

error in the routine call

Facility: LIB, Run-Time Library General Procedures
Explanation: One or more errors were detected during a call to
LIB$DELETE_FILE or LIB$RENAME_FILE, but a user-specified error routine
was called to handle the conditions. This is an alternate success status.
User Action: None.
ESA,

invalid expanded string address
Facility: RMS, VAX Record Management Services
Explanation: The expanded string area address in the VAX RMS NAM block
is invalid; the address is in an area of memory that cannot be read or written
by the caller, as required; or the expanded string buffer contains an invalid
file specification.
User Action: Verify that the call to the VAX RMS service was coded correctly.
Check the logical name translation.

ESCAPE,

escape sequence detected

Facility: PSM, Print Symbiont
Explanation: This status is returned by a print symbiont format routine
indicating an escape sequence has been detected.
User Action: None.
ESL,

invalid expanded string length
Facility: RMS, VAX Record Management Services
Explanation: The expanded string length field in the VAX RMS NAM block
contains a value of zero; the attempted operation requires the expanded
string.
User Action: Verify that the call to the VAX RMS service was coded correctly.

2-156

Messages

ESS,

expanded string area too small
Facility: RMS, VAX Record Management Services
Explanation: The user buffer provided to receive an expanded file
specification string is too short; the string does not fit.
User Action: Verify that the call to the VAX RMS service was coded correctly.

ESTABCON,

establishing connection to remote node(s)...

Facility: MONITOR, Monitor Utility
Explanation: Connections to one or more remote nodes are being made.
Connections to remote nodes are made when the /NODE qualifier is used or
when the CLUSTER class is requested. All connections to remote nodes are
made before data collection is initiated.
User Action: None.
EVL,

Too many variables: 'string7
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: The maximum of 20 variables has been exceeded with the
inclusion of the specified .VARIABLE or conditional command (.IF, .IFNOT,
.ENDIF, or .ELSE); the command in error has been ignored.
User Action: Reduce the number of variables.

EVTSIZ,

an event was too large to translate to DNA form

Facility: EVL, Event Logger
Explanation: A raw event was too large to format properly into DECnet
standard form. Therefore, it was discarded. This is probably caused by a
network software problem.
User Action: Submit a Software Performance Report.
EXARANGE,

invalid range of addresses

Facility: PATCH, VAX Image File Patch Utility and DEBUG, VAX/VMS
Debugger
Explanation: The range of addresses specified was in the wrong order. The
higher address preceded the lower address.
User Action: Retry using the following format:
lower-boundary-address:upper-boundary-address

EXARANGE,

invalid range of addresses

2-157

Messages

EXASTLM,

exceeded AST quota

Facility: SYSTEM, VAX/VMS System Services
Explanation: An image could not continue executing or a command could
not execute because the process exceeded its AST quota.
User Action: If your program fails consistently because of insufficient quotas,
contact your system manager and request that your quotas be increased.
EXBIOLM,

exceeded buffered I/O quota

Facility: SYSTEM, VAX/VMS System Services
Explanation: An image could not continue to create a subprocess because the
process exceeded its buffered I/O quota.
User Action: If a program fails consistently because of insufficient quotas,
contact your system manager and request that your quotas be increased.
EXBYTLM,

exceeded byte count quota

Facility: SYSTEM, VAX/VMS System Services
Explanation: The requested operation failed because the process' byte count
quota is not large enough.
This can occur if excessive concurrent buffered I/O is outstanding, if a large
number of mailboxes is created, or if a large number of windows needs to be
created to completely map a file.
Failure on window creation can occur on a $CRMPSC system service call,
the DCL command RUN, or an Access or Create of a file. In this case, this
message indicates that the specified file is very fragmented or the process'
byte limit quota should be increased.
Failure can also occur on a disk read or write operation indicating that a prior
extend operation on the file has caused it to become very fragmented.
User Action: Either compress the file by copying the volume with BACKUP,
or ask the system manager to increase your BYTELIM quota.
EXCPSC,

more than 65535 psects defined in module 'module-name' file 'file¬
name'

Facility: LINK, VAX Linker
Explanation: An object module defines more than 65535 psects.
User Action: Reduce the number of psects in the module and relink.
EXCPUTIM,

CPU time limit expired

Facility: SYSTEM, VAX/VMS System Services
Explanation: The user's CPU time limit has expired.
User Action: Request that a larger CPU time quota be assigned from the
system manager and retry the operation.

2-158

Messages

EXDEPTH,

exceeded allowed depth

Facility: SYSTEM, VAX/VMS System Services
Explanation: Either a programming error has occurred or the resource name
tree does not have enough depth. The lock management services allow a
certain depth to the resource name tree that is a function of the interrupt
stack size. If the resource name tree requires more levels, the size of the
interrupt stack must be increased.
User Action: Either correct the programming error or increase the size of the
interrupt stack by increasing the SYSGEN parameter INTSTKPAGES.
EXDIOLM,

exceeded direct I/O quota

Facility: SYSTEM, VAX/VMS System Services
Explanation: An image could not continue executing or a command could
not execute because the process exceeded its direct I/O quota.
User Action: If a program fails consistently because of insufficient quotas,
contact your system manager and request that your quotas be increased.
EXDISKQUOTA,

disk quota exceeded

Facility: SYSTEM, VAX/VMS System Services
Explanation: The disk quota has been exceeded while attempting to create or
extend a file.
User Action: Reduce disk usage by deleting files or have the system manager
increase the quota.
EXEABO,

Executor characteristics not defined

Facility: NCP, Network Control Program
Explanation: There is no executor node defined on the local node from
which the NCP command COPY was issued.
User Action: None.
EXECUTEFAIL,

Execution aborted at line 'integer'

Facility: VAX Text Processing Utility
Explanation: Your program was terminated prematurely because of an error.
User Action: Correct the error in your program and reexecute it.
EXECUTING,

job executing on queue prevents requested operation

Facility: JBC, Job Controller
Explanation: The parameters of the specified job cannot be modified because
the job is currently executing. Or, the specified queue cannot be deleted
because there is a job executing from the queue.
User Action: Reissue the request after the job has completed execution.

2-159

EXENQLM,

exceeded enqueue quota

Facility: SYSTEM, VAX/VMS System Services and RMS, VAX Record
Management Services
Explanation: You have exceeded your ENQLM quota. Since the ENQUEUE
quota is shared by a process and all its subprocesses, any one of these
processes could have used the entire quota.
User Action: You can either increase the ENQLM quota of the process or
modify the program so it uses fewer locks.
EXENQLM,

exceeded enqueue quota

Facility: RMS, VAX Record Management Services
Explanation: An ENQ/DEQ facility service failed because the ENQ quota
was exceeded.
User Action: Increase the ENQLIM quota, logout and login, and retry the
operation.
EXFILLM,

exceeded open file quota

Facility: SYSTEM, VAX/VMS System Services
Explanation: An image could not continue executing or a command could
not execute because the process exceeded its open file quota. Since the
FILLM quota is shared by a process and all its subprocesses, any one of these
processes could have used the entire quota.
User Action: If a program fails consistently because of insufficient quotas,
contact your system manager and request that your quotas be increased.
EXGBLPAGFIL,

exceeded global page file limit

Facility: SYSTEM, VAX/VMS System Services
Explanation: The attempt to allocate a global section with page file backing
store failed because the systemwide limit on these pages is exceeded. No part
of the section is allocated.
User Action: Delete some similar sections or ask the system manager to
increase the SYSGEN parameter GBLPAGFIL. Then, try the operation again.
EXHFUL,

File extension header has no room

Messages

EXISTS,

'file-spec' already exists

Facility: Shared by several facilities
Explanation: The directory specified in the DCL command CREATE/DIR
already exists.
User Action: None. This message is informational.
EXISTS,

known file entry for a version of this file already exists

Facility: INSTALL, Install Utility
Explanation: A known file entry already exists for this file name on the
specified device and directory.
User Action: Contact your system manager.
EXITFAIL,

Attempt to EXIT was unsuccessful

Facility: VAX Text Processing Utility
Explanation: An error occurred during execution of the built-in procedure
EXIT; the procedure did not complete successfully. This usually occurs
because the EXIT procedure could not write the modified buffers. This
message should be accompanied by a message specifying the reason why the
EXIT procedure failed.
User Action: Take corrective action according to the reason for the EXIT
failure, for example, if there was insufficient disk space to create the modified
version of the output file, purge some files to free space on the disk.
EXITSTATUS,

is xxx

Facility: DEBUG, VAX/VMS Debugger
Explanation: The program has exited with the status xxx. See the VAX/VMS
System Services Reference Manual for more information about the VAX/VMS
exit status codes.
User Action: None.
EXLNMQUOTA,

exceeded the job logical name table

Facility: LOGIN, Login Processor
Explanation: The job logical name table is full. You cannot make further job
logical name assignments.
User Action: Deassign logical names you no longer need to free space in the
table. If you have sufficient privilege to modify the user authorization file,
you can increase the size of the logical name table with the AUTHORIZE
command MODIFY. The format of the command is AUTHORIZE MODIFY
username/JTQUOTA=n, where n is the size of the table expressed in bytes.
The default table size is 1024 bytes. The new value takes effect the next time
you log in.

2-161

EXP,

file expiration date not yet reached
Facility: RMS, VAX Record Management Services
Explanation: A call to a VAX RMS service attempted to overwrite a magnetic
tape file that has not expired.
User Action: If the file can be overwritten, remount the volume with the
/OVERRIDE=EXPIRATION qualifier. (You must be the owner of the volume
or have the VOLPRO privilege to override the expiration date.) Otherwise,
use another volume.

EXPAGQUO,

exceeded pagefile quota

Facility: LINK, VAX Linker
Explanation: The linker could not expand its virtual address space sufficiently
due to inadequate pagefile quota. Since the PGFLQUOTA is shared by a
process and all its subprocesses, any one of these processes could have used
all the quota.
User Action: If the link fails consistently because of insufficient quotas,
contact your system manager and request that your quota be increased.
EXPANDPHD,

Expand process header error

One of the following symbols was expected:

Facility: VAX Text Processing Utility
Explanation: You have a syntax error in your program. One of the symbols
listed was expected but not found.
User Action: Correct the syntax error and recompile your program.
EXPGFLQUOTA,

exceeded pagefile quota

Facility: SYSTEM, VAX/VMS System Services
Explanation: An image could not continue executing or a command could
not execute because the process exceeded its pagefile quota. Since the
PGFLQUOTA is shared by a process and all its subprocesses, any one of
these processes could have used the entire quota.
User Action: If a program fails consistently because of insufficient quotas,
contact your system manager and request that your quotas be increased.

Messages

EXPORTQUOTA,

port's quota exceeded

Facility: SYSTEM, VAX/VMS System Services
Explanation: The quota permitted by processes on this port of a multiport
(shared) memory has been exceeded.
User Action: Wait until other processes release the required resource, or
reboot VAX/VMS and reconnect shared memory specifying a larger quota.
EXPOVR32,

expression overflowed 32 bits

Facility: MACRO, VAX Macro Assembler
Explanation: The value of the expression could not be stored in a longword
(32 bits). The assembler truncated the value to 32 bits.
User Action: Change the values in the expression.
EXPRCLM,

exceeded subprocess quota

Facility: SYSTEM, VAX/VMS System Services
Explanation: An image could not continue executing or a command could
not execute because the process exceeded its subprocess limit.
User Action: If a program fails consistently because of insufficient quotas,
contact your system manager and request that your quotas be increased.
EXPREG,

error code of 'xx' expanding program region

Facility: PATCH, VAX Image File Patch Utility
Explanation: The system service $EXPREG request failed due to the error
represented as xx.
User Action: Correct the error (represented as xx) and retry.
EXPSHRPAT,

attempt to expand patch area for shareable image

Facility: PATCH, VAX Image File Patch Utility
Explanation: The patch area cannot be created for shareable images.
User Action: Relink the shareable image instead of patching it.
EXPSTKOVR,

expression exceeds maximum nesting level

Facility: DEBUG, VAX/VMS Debugger
Explanation: The expression is too complex.
User Action: Reduce the nesting of parentheses and simplify the expression.
EXPSTKOVR,

expression too nested, stack overflow

Facility: PATCH, VAX Image File Patch Utility
Explanation: You attempted to evaluate an expression that contained more
than 16 levels of nested arguments.
User Action: Remove levels of nested arguments until you have 16 levels or
less and retry the operation.

2-163

EXPSYN,

invalid expression syntax - check operators and operands

Facility: CLI, Command Language Interpreter (DCL)
Explanation: An arithmetic expression in a DCL command is not syntactically
correct; the command interpreter cannot analyze the expression. An invalid
expression can occur as a result of:
•

Missing operators between values or symbol names

•

Unmatched parentheses

•

Undefined symbol names that are being interpreted as character string
data

User Action: Examine the expression for any of the errors listed above.
Correct the expression and reenter the command.
EXPVIR,

error allocating virtual memory

Facility: FDL, Create/FDL Utility
Explanation: This message will be accompanied by a system error message
that explains the error.
User Action: Correct the error described in the system error message and try
again.
EXQUOTA,

exceeded quota

Facility: SYSTEM, VAX/VMS System Services
Explanation: An image could not continue executing or a command could
not execute because the process exceeded one of its resource quotas or limits.
If this message is associated with a status code returned by a request to a
DR32 interface, a DR11-W interface, or a LPA11-K driver, the AST quota for
the requesting process was exceeded. In the latter case, an AST cannot be
queued for a buffer full/empty AST. Normally, a start data transfer request
can require no more than three AST blocks at a time.
If this message is associated with a status code returned by a request to a
DUP11 interface, a request cannot be queued because the buffered I/O quota
was exceeded.
This message can indicate failure to create a subprocess because deductible
quotas, when subtracted from the current quotas of the creator, would not
leave the minimum required quotas for the creator.
User Action: Use the DCL command SHOW PROCESS/QUOTAS to
determine the current quotas and to determine which quota was exceeded.
Determine whether any subprocesses are hibernating and are no longer
performing useful functions; delete any such subprocesses.
If a program fails consistently because of insufficient quotas, contact your
system manager and request that your quotas be increased.

Messages

EXQUOTA,

maximum number of users exceeded - try again

Facility: LOGIN, Login Processor
Explanation: The maximum number of users allowed to be logged in has
been exceeded.
User Action: Wait until enough users have logged off, then try to log in
again.
EXT,

ACP file extend failed
Facility: RMS, VAX Record Management Services
Explanation: The requested extension of a file cannot be performed. This
message is associated with a status code returned from a file system ACP QIO
request made by VAX RMS.
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.

EXTBIT,

illegal extract bit number - greater than 31

Facility: PATCH, VAX Image File Patch Utility
Explanation: You specified an illegal bit number; legal bit numbers range
from 0 to 31 inclusive.
User Action: Retry the operation specifying a legal bit number.
EXTCACHIV,

Contents of extent cache is garbage

unable to extend work file for needed space

Facility: SORT, VAX SORT/MERGE Utility
Explanation: SORT failed to extend your temporary work file. Either the
device is full or you have reached your disk quota limit.
User Action: Reassign work files to a different device with more space or
have the system manager extend your quota.
EXTENDED,

'file-spec' extended

Facility: SYSGEN, System Generation Utility
Explanation: This informational message is the result of the SYSGEN
command CREATE and indicates that the specified file has been extended.
User Action: No action is required.

2-165

Messages

EXTN—ERR,

unable to extend output file

Facility: CONVERT, Convert Utility
Explanation: The size of the input file exceeded the initial allocation of the
output file, and when CONVERT tried to extend the file, an error occurred.
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.
EXTQELM,

exceeded timer queue entry quota

Facility: SYSTEM, VAX/VMS System Services
Explanation: An image could not continue executing or a command could
not execute because the process exceeded its timer queue entry quota.
Since the TQELM quota is shared by a process and all its subprocesses, any
one of the processes could have used all the quota.
User Action: If a program fails consistently because of insufficient quotas,
contact your system manager and request that your quotas be increased.
EXTRACTED,

module 'module name' extracted from 'library file-spec'

Facility: LIBRAR, LIBRARY Command
Explanation: This success message is generated by the DCL command
LIBRARY.
User Action: None. This message is informational.
EXTRAENDM,

extraneous .ENDM in 'library file-spec'

Facility: LIBRAR, LIBRARY Command
Explanation: This warning message is generated by the DCL command
LIBRARY. The specified library contains a .ENDM line that does not terminate
any macro.
User Action: Reformat the macro source file.
FAB,

File aborted
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: DSR has aborted the file for internal reasons. This is a DSR
internal error.
User Action: Submit a Software Performance Report.

FAB,

invalid FAB or FAB not accessible
Facility: RMS, VAX Record Management Services
Explanation: Either the specified VAX RMS block identifier field does not
indicate that the field is a FAB, or the FAB is not in a portion of memory that
can be written to by the caller.
User Action: Verify that the call to the VAX RMS service was coded correctly.
An attempt may have been made to perform file operations to a RAB. Verify
that the FAB was properly initialized and that the block identifier field was
not overwritten during execution of the program image.

2-166

Messages

FAC,

record operation not permitted by specified file access (FAC)
Facility: RMS, VAX Record Management Services
Explanation: A record operation was attempted that was not indicated in the
file access field of the FAB for the file. For example, to delete a record, the
DEL option must have been specified when the file was opened or created.
If the error results from the DCL command READ or WRITE, this message
indicates either the DCL command WRITE was issued for a file opened for
reading, or the DCL command READ was issued for a file opened for writing.
User Action: If the error occurred during execution of an image, verify that
the FAC parameter in the FAB indicates the requested type of access.
If the error occurred during use of the DCL commands, verify that the correct
qualifier was specified when the DCL command OPEN was issued to open
the file.

FACOVFL,

facility table overflow in section - please submit SPR

Facility: MESSAGE, Message Utility
Explanation: An internal error in the compiler has been detected.
User Action: Submit a Software Performance Report.
FACTBAD,

cannot read factory bad block data

Facility: INIT, INITIALIZE Volume Command and BACKUP, Backup Utility
Explanation: Either the DCL command INITIALIZE or the Backup Utility
encountered an error during an attempt to read the bad block data recorded
on the specified volume. An accompanying message provides additional
information.
User Action: Either correct the condition that caused the error and reenter
the command or notify the system manager. If the volume is under warranty,
it should be returned to the factory. Contact a DIGITAL field service
representative if necessary.
FACTOOLONG,

Facility name, 'name', exceeds maximum length 'integer'

Facility: VAX Text Processing Utility
Explanation: The facility name you want to use is longer than the maximum
allowed length.
User Action: Use a shorter facility name.
FAIL,

failed to 'execute_verb' entry for 'file-spec'

Facility: INSTALL, Install Utility
Explanation: A failure to ADD, CREATE, DELETE, REMOVE, or REPLACE
a known file entry occurred. An accompanying error message explains the
failure.
User Action: Correct the situation indicated by the accompanying error
message and reissue the command.

2-167

Messages

FAILED,

failed to perform 'execute_verb' operation

Facility: INSTALL, Install Utility
Explanation: A PURGE or listing operation failed to execute completely. An
accompanying message explains the failure.
User Action: Correct the situation indicated by the accompanying error
message and reissue the command.
Failed help library index init
Facility: DISKQUOTA, Diskquota Utility
Explanation: This message is issued with other messages.
User Action: Take corrective action based on the accompanying messages.
Failed to access help text
Facility: DISKQUOTA, Diskquota Utility
Explanation: This message is issued with other messages.
User Action: Take corrective action based on the accompanying messages.
Failed to access index file on relative volume 'n'
Facility: DISKQUOTA, Diskquota Utility
Explanation: This message is issued with other messages.
User Action: Take corrective action based on the accompanying messages.
Failed to access quota file
Facility: DISKQUOTA, Diskquota Utility
Explanation: This message is issued with other messages.
User Action: Take corrective action based on the accompanying messages.
Failed to add quota file entry
Facility: DISKQUOTA, Diskquota Utility
Explanation: This message is issued with other messages.
User Action: Take corrective action based on the accompanying messages.
Failed to disable quota file
Facility: DISKQUOTA, Diskquota Utility
Explanation: This message is issued with other messages.
User Action: Take corrective action based on the accompanying messages.
Failed to enable quota file
Facility: DISKQUOTA, Diskquota Utility
Explanation: This message is issued with other messages.
User Action: Take corrective action based on the accompanying messages.

2-168

Messages

Failed to lock volume
Facility: DISKQUOTA, Diskquota Utility
Explanation: This message is issued with other messages.
User Action: Take corrective action based on the accompanying messages.
Failed to open help library
Facility: DISKQUOTA, Diskquota Utility
Explanation: This message is issued with other messages.
User Action: Take corrective action based on the accompanying messages.
Failed to read home block on relative volume 'n'
Facility: DISKQUOTA, Diskquota Utility
Explanation: This message is issued with other messages.
User Action: Take corrective action based on the accompanying messages.
Failed to remove quota file entry
Facility: DISKQUOTA, Diskquota Utility
Explanation: This message is issued with other messages.
User Action: Take corrective action based on the accompanying messages.
Failed to unlock volume
Facility: DISKQUOTA, Diskquota Utility
Explanation: This message is issued with other messages.
User Action: Take corrective action based on the accompanying messages.
FAILFREVM,

failed to deallocate 'number7 bytes of virtual memory

Facility: CNF, NI Configurator
Explanation: An error occurred when NICONFIG attempted to deallocate
virtual memory.
User Action: Check the accompanying error message to determine whether
the virtual address space was exceeded, or whether a program error
was uncovered. An invalid address or size for deallocation indicates a
programming error.
FAILGETVM,

failed to allocate 'nn' bytes of virtual memory

Facility: INSTALL, Install Utility
Explanation: INSTALL failed to allocate sufficient work space for itself.
User Action: Either your PGFLQUO value is too low for your account, or the
system's VIRTUALPAGECNT SYSGEN parameter is too low. Contact your
system manager.

2-169

FAILGETVM,

failed to allocate 'number' bytes of virtual memory

Facility: CNF, NI Configurator
Explanation: An error occurred when NICONFIG attempted to allocate
virtual memory.
User Action: Check the accompanying error message to determine whether
the virtual address space was exceeded, or whether a program error was
uncovered. An invalid address or size for allocation indicates a programming
error.
FAILURE,

Internal VAXTPU failure

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

failed to open file 'file-name'

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: The Termtable compiler could not open the file specified in a
REQUIRE statement.
User Action: Make sure that the specified file exists and that you have read
access to it.
FAO,

error formatting report information
Facility: BAD, Bad Block Locator Utility
Explanation: An error was encountered during an FAO formatting operation.
User Action: Copy all pertinent diagnostic message information and submit
an SPR to DIGITAL.

FAOBUG,

FAO system service failure

Facility: LINK, VAX Linker, CREF, Cross-Reference Utility, LIBRAR,
LIBRARY Command
Explanation: An error was returned by the $FAO system service.
User Action: Submit a Software Performance Report.
FAOFAIL,

fao failure

Facility: CREF, Cross-Reference Utility, LINK, VAX Linker
Explanation: An error was returned by the $FAO system service.
User Action: Ensure that the field descriptor FAO control strings are correct.
FAOFAIL,

FAO system service failure

Facility: LIBRAR, LIBRARY Command
Explanation: An unexpected internal consistency check occurred.
User Action: Submit a Software Performance Report and contact your system
manager.

Messages

FATALERR,

fatal error on 'save-set-spec'

Facility: BACKUP, Backup Utility
Explanation: The Backup Utility encountered an irrecoverable error during
an attempt to read or write the specified save set. The accompanying message
provides additional information.
User Action: Correct the condition that caused the error and reenter the
command.
FATALERROR,

fatal error message issued

Facility: LINK, VAX Linker
Explanation: The linker issued a fatal error message in the link.
User Action: Correct the problem and relink.
FATALEXC,

fatal exception encountered

Facility: CONVERT, Convert Utility
Explanation: This message appears if an exception record is encountered and
if you have specified the /EXIT qualifier.
User Action: Specify either /TRUNCATE or /PAD, or else specify /NOEXIT.
FATALEXCPT,

Fatal executive or kernel mode exception

Facility: System Bugcheck
Explanation: The VAX/VMS software detected an unrecoverable,
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.)
FATERRLIB,

fatal error in library

Facility: LIB, Run-Time Library General Procedures
Explanation: An internal consistency check has failed in the VAX Common
Run-Time Procedure Library. This usually indicates a programming error in
the VAX Common Run-Time Procedure Library.
User Action: Submit a Software Performance Report.
FATERRLIB,

fatal error in library

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: An internal error has occurred within the Screen Management
facility.
User Action: Submit an SPR describing the problem.

2-171

Messages

FATINTERR,

fatal internal error in Run-Time Library

Facility: OTS, Language Independent Run-Time Library Support Procedures,
STR, Run-Time Library String Procedures
Explanation: An explicit or implicit call to the VAX Common Run-Time
Library resulted in the failure of an internal consistency check.
User Action: Rerun your program. Collect as much information as possible,
including the system traceback listing, and submit a Software Performance
Report.
FAU,

Flag character 'character7 already in use
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: You attempted to define a character as a flag character;
however, the character has already been defined.
User Action: Use another character as a flag character.

FCPREADERR,

file processor read error

Facility: SYSTEM, VAX/VMS System Services
Explanation: An I/O error occurred when file structure data, for example, a
directory, was being read.
User Action: Examine the error log and correct the hardware problem if
necessary.
FCPREPSTN,

file processor reposition error

Facility: SYSTEM, VAX/VMS System Services
Explanation: An I/O error occurred during an attempt to reposition a tape
volume after it had gone offline.
User Action: Examine the error log and correct the hardware problem if
necessary.
FCPREWNDERR,

file processor rewind error

Facility: SYSTEM, VAX/VMS System Services
Explanation: An I/O error occurred when a volume was being rewound.
User Action: Examine the error log and correct the hardware problem if
necessary.
FCPSPACERR,

file processor space error

Facility: SYSTEM, VAX/VMS System Services
Explanation: An I/O error occurred while spaces were being skipped within
a file or files. The operating system does not normally display this message.
User Action: Examine the error log and correct the hardware problem if
necessary.

2-172

Messages

FCPWRITERR,

file processor write error

Facility: SYSTEM, VAX/VMS System Services
Explanation: An I/O error occurred when file structure data, for example, a
directory, was being written.
User Action: Examine the error log and correct the hardware problem if
necessary.
FDLERROR,

error parsing FDL file

Facility: FDL, Edit/FDL Utility
Explanation: This message is issued with an accompanying message.
User Action: Take corrective action based on the accompanying message.
FDLPAR,

error parsing FDL file

Facility: FDL, Edit/FDL Utility
Explanation: An error occurred during the parsing of the FDL file. This
message is issued with an accompanying message.
User Action: Take corrective action based on the accompanying message and
try again.
FEL,

'flagname' flag at end of line ignored
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: This flag cannot occur at the end of a line.
User Action: Remove the flag from the end of the line.

FEX,

file already exists, not superseded
Facility: RMS, VAX Record Management Services
Explanation: An attempt was made to create or rename a file with the same
file specification as an existing file in the volume set.
User Action: Choose a different file specification; delete the existing file (if a
new one is to be created); or use the SUP option in the FOP parameter in the
FAB to request that an existing file be superseded.

FIDERROR,

unexpected file change in 'file-spec7

Facility: BACKUP, Backup Utility
Explanation: A file boundary marker was missing from the input save set.
Data in the save set may be corrupted. It is likely that parts of the specified
file and one or more complete files are missing.
User Action: Examine the file for corruption and reconstruct as necessary. If
this error occurs during a disk-to-disk (copy) operation, it indicates a software
error in the Backup Utility; in this case, submit a Software Performance
Report.

2-173

Messages

FIELDLIM,

number of fields in range exceeds limit

Facility: NCP, Network Control Program
Explanation: Channel lists may have eight fields, separated by commas. The
last field cannot be a hyphenated range.
User Action: Correct the channel list.
FILll_NOREC,

ignoring /RECORD-FORMAT for Files-11 output

Facility: EXCHANGE, Exchange Utility
Explanation: The EXCHANGE utility does not support the /RECORD—
FORMAT option on Files-11 output files.
User Action: Leave the qualifier off. If the output file is not in the desired
format, use the VMS CONVERT utility to change the format of the file.
FILACCERR,

magnetic tape file access is nonblank

Facility: SYSTEM, VAX/VMS System Services
Explanation: The accessibility characteristic in the HDR/ label is not blank
and the file cannot be accessed without overriding the field.
User Action: Mount the magnetic tape with the
/OVERRIDE=ACCESSIBILITY qualifier. (The VOLPRO privilege is required
or you must be the owner of the tape.) Otherwise, use another volume.
FILALRACC,

file already accessed on channel

Facility: SYSTEM, VAX/VMS System Services
Explanation: The request failed because the channel over which the $QIO
IO$_ACCESS request was issued already had either a file or logical link
accessed on it.
User Action: Check for a programming error.
FILAREDIF,

files are different

Facility: DIFF, DIFFERENCES Command
Explanation: This informational message is returned by DIFF if the two files
being compared differ.
User Action: None.
FILCNTNONZ,

Open file count nonzero after process rundown

2-174

Messages

File attributes error
Facility: EDT, EDT Editor
Explanation: The file cannot be edited by EDT because of its attributes.
User Action: None. The file cannot be edited.
File specification required
Facility: EDT, EDT Editor
Explanation: You did not specify a file name (or file specification) with an
INCLUDE, PRINT, or WRITE command.
User Action: Reenter the command including the correct file specification.
FILEACC,

error accessing system authorization file

Facility: LOGIN, Login Processor
Explanation: An error occurred while attempting to access the authorization
file. An accompanying message will provide more information.
User Action: Correct the problem described by the accompanying message,
and try again.
FILECONFUSED,

file 'file-name7 is an ISAM file; expected a sequential file; a
higher version exists that is sequential

Facility: MAIL, Personal Mail Utility
Explanation: The user's mail directory contained two versions of MAIL.MAI,
one of which was sequential file organization and the other was indexed
sequential (ISAM).
User Action: Rename the highest version MAIL.MAI to XMAIL.MAI. Enter
MAIL, and issue the following commands:
MAIL SET FILE XMAIL
MAIL COPY /ALL MAIL MAIL

This action puts all the messages in XMAIL.MAI into the folder MAIL in your
default mail file, MAIL.MAI.
FILECONVERTED,

File format is being converted to supported type

Facility: VAX Text Processing Utility
Explanation: The buffer being written was created from a file that had
nonstandard attributes. The output file being created does not have the
attributes of the input file; it is created with standard attributes (VARIABLE
with CR record attributes).
User Action: None.
FILEIN,

'count7 line(s) read from file 'name'

Facility: VAX Text Processing Utility
Explanation: VAXTPU opened the named file and read the indicated number
of lines from that file into a buffer.
User Action: None.

2-175

Messages

FILELOCKED,

file is deaccess locked

Facility: SYSTEM, VAX/VMS System Services
Explanation: The program attempted to access a locked file. A file becomes
locked when it is accessed with FIB$M_DLOCK (bit) set and then deaccessed
without writing attributes.
User Action: Unlock the file with the DCL command UNLOCK and examine
it for inconsistency.
FILEMPTY,

file 'file-name' has no folders

Facility: MAIL, Personal Mail Utility
Explanation: A DIR/FOLDER command was issued, but the current mail file
has no folders and, therefore, no messages.
User Action: None.
FILENOTFOUND,

unable to locate file 'filename'

Facility: EXCHANGE, Exchange Utility
Explanation: The EXCHANGE utility could not find the listed input file.
User Action: Check the command for a misspelling error, or reenter the
command specifying the correct location for the input file(s).
FILENUMCHK,

file identification number check

Facility: SYSTEM, VAX/VMS System Services
Explanation: The volume index file may be corrupted.
The file number in the file header that was read is invalid. The disk's file
structure is damaged.
User Action: Repair the volume with the Verify Utility.
FILEOUT,

'count' line(s) written to file 'name'

Facility: VAX Text Processing Utility
Explanation: VAXTPU wrote the indicated number of lines from a buffer into
the named file.
User Action: None.
FILEPURGED,

oldest file version purged

Facility: SYSTEM, VAX/VMS System Services
Explanation: The newly created file version exceeded the maximum number
of versions of that file; the oldest file version has been deleted.
User Action: None. This message is informational.

2-176

Messages

FILESEQCHK,

file identification sequence number check

Facility: SYSTEM, VAX/VMS System Services
Explanation: The file sequence number in the file header is not the one
expected. A directory entry points to a file that has been deleted.
User Action: Remove the directory entry with the following command line:
$ DELETE file-spec

FILESTRUCT,

unsupported file structure level

Facility: SYSTEM, VAX/VMS System Services
Explanation: The file structure on the accessed volume is not compatible
with the ACP, or the file structure may be corrupt.
User Action: Verify that the correct physical volume is mounted. Or repair
the volume with the Verify Utility. If the volume is new and does not contain
data, use the DCL command INITIALIZE to initialize the volume in the
correct format.
FILLIM,

exceeded open file limit

Facility: CONVERT, Convert Utility
Explanation: SORT exceeded the process open file limit.
User Action: Increase the FILLM parameter in the user authorization record.
FILNOTACC,

file not accessed on channel

Facility: SYSTEM, VAX/VMS System Services
Explanation: The process is trying to read or write to a channel that does not
have a file accessed on it.
User Action: Modify the source program to correct the problem.
FILNOTCNTG,

file is not contiguous as required

Facility: SYSTEM, VAX/VMS System Services
Explanation: A system file that must be in contiguous disk format is not
contiguous.
User Action: Use the DCL command COPY/CONTIGUOUS to make a new
contiguous version of the file.
FILNOTDEL,

error deleting 'file-spec'

Facility: Shared by several facilities
Explanation: A file could not be deleted. This message is usually
accompanied by a VAX RMS message indicating the reason for the failure.
User Action: Take appropriate action based on the associated VAX RMS
message.

2-177

Messages

FILNOTEXP,

file is not expired

Facility: MOUNT, MOUNT Command and SYSTEM, VAX/VMS System
Services
Explanation: A tape file cannot be overwritten because it has not reached its
expiration date.
User Action: To overwrite or delete the file, mount the volume with the
/OVERRIDE=EXPIRATION qualifier. You must be the owner of the volume
or have volume protection (VOLPRO) privilege.
FILNOTPUR,

error deleting 'file-spec'

Facility: Shared by several facilities
Explanation: An error was detected during an attempt to delete the specified
file. A subsequent message explains the reason for the error.
User Action: Take corrective action based on the accompanying message.
FILPURGED,

'file-spec' deleted

Facility: Shared by several facilities
Explanation: The DCL command PURGE displays the file specification of a
file it is deleting.
User Action: None. This message is informational.
FINDHOME,

no valid home block, RVN 'n'

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility could not locate a valid home block on the
specified relative volume.
User Action: If the volume can no longer be mounted by the operating
system, it is corrupted and must be reconstructed from backup media. If the
volume can be mounted, this message indicates a software error in the Verify
Utility. In this case, submit a Software Performance Report.
FINDIHD,

no valid index file header, RVN 'n'

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that both the primary and alternate
index file headers were corrupted.
User Action: If the volume can no longer be mounted by the operating
system, it is corrupted and must be reconstructed from backup media. If the
volume can be mounted, this message indicates a software error in the Verify
Utility. In this case, submit a Software Performance Report.
FINISHED,

Task completed

Facility: UETP, User Environment Test Package
Explanation: A module in the UETP completed, but errors may have
occurred during its execution.
User Action: None.

2-178

Messages

FIRSTMOD,

first input file being a library requires module extraction

Facility: LINK, VAX Linker
Explanation: No input files were specified, and the first file was a library file
with no explicit module extraction.
User Action: Reenter the command, specifying an input file, or use the
/INCLUDE qualifier on the library file.
FLAGTRUNC,

Value of message flags exceeds maximum value 15, truncated

Facility: VAX Text Processing Utility
Explanation: The message flags value should be less than or equal to 15.
The procedure for writing the messages uses only the low 4 bits of the value.
User Action: Refer to the material on SET (MESSAGE—FLAGS,...) in the
VAX Text Processing Utility Reference Manual for the proper values to specify.
FLG,

invalid key definition flags for key = 'nnn'
Facility: RMS, VAX Record Management Services
Explanation: Either XAB$V_CHG or XAB$V_NUL was incorrectly specified
for the primary key definition XAB, or a reserved key definition flag was
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 VAX RMS service
was coded correctly.

FLK,

file currently locked by another user
Facility: RMS, VAX Record Management Services
Explanation: An attempt was made to open or create a file that has been
locked as the result of another user's access; the file was not opened for
sharing.
User Action: Wait until the other user has unlocked the file. If the file is to
be shared, verify that the SHR option is selected in the FAB. If the file cannot
be shared, modify the program to detect and respond to the condition by
waiting.

FLOOVEMAT,

floating overflow in math library - user PC location

Facility: MTH, Run-Time Library Math Procedures
Explanation: An overflow condition occurred during execution of a math
library procedure. This message results from an incorrect call to the math
library, and usually indicates that an argument is too small or too large.
User Action: Use the traceback information and PC displayed in the message
to locate where your program called the math library.

2-179

Messages

FLOUNDMAT,

floating underflow in math library - user PC location

Facility: MTH, Run-Time Library Math Procedures
Explanation: An underflow condition occurred during execution of a math
library procedure and the caller was enabled for floating underflow traps.
This message results from an incorrect call to the math library. Refer to the
discussion of the LIB$FLT_UNDER procedure in the VAX/VMS Run-Time
Library Routines Reference Manual.
User Action: Locate the statement in your program where you called the
math library causing the underflow condition to occur.
FLTDIV,

arithmetic trap, floating/decimal divide by zero at PC = 'xxxxxxxx', PSL
= 'xxxxxxxx'

Facility: SYSTEM, VAX/VMS System Services
Explanation: An arithmetic exception condition occurred as a result of an
attempt to divide a floating point/decimal number by zero.
User Action: Examine the PC location displayed in the message; check the
program listing to verify that operands or variables are specified correctly.
FLTDIV_F,

arithmetic fault, floating divide by zero at PC = 'xxxxxxxx', PSL =
'xxxxxxxx'

Facility: SYSTEM, VAX/VMS System Services
Explanation: During a floating-point operation, an attempt was made to
divide by zero.
User Action: Examine the PC location displayed in the message; check the
program listing to verify that operands or variables are specified correctly.
FLTOVF,

arithmetic trap, floating overflow at PC = 'xxxxxxxx', PSL = 'xxxxxxxx'

Facility: SYSTEM, VAX/VMS System Services
Explanation: An arithmetic exception condition occurred as a result of a
floating-point overflow.
User Action: Examine the PC location displayed in the message; check the
program listing to verify that operands or variables are specified correctly.
FLTOVF__F,

arithmetic fault, floating overflow at PC = 'xxxxxxxx', PSL = 'xxxxxxxx'

Facility: SYSTEM, VAX/VMS System Services
Explanation: During an arithmetic operation, a floating-point value exceeded
the largest representable value for that data type.
User Action: Examine the PC location displayed in the message; check the
program listing to verify that operands or variables are specified correctly.
FLTPNTSYNX,

floating point syntax error

Facility: MACRO, VAX Macro Assembler
Explanation: A floating-point constant contained a syntax error.
User Action: Correct the syntax of the constant.

2-180

Messages

FLTUND,

arithmetic trap, floating underflow at PC = 'xxxxxxxx', PSL = 'xxxxxxxx'

Facility: SYSTEM, VAX/VMS System Services, LIB, Run-Time Library
General Procedures
Explanation: An arithmetic exception condition occurred as a result of
floating-point underflow.
User Action: Examine the PC location displayed in the message; check the
program listing to verify that operands or variables are specified correctly.
FLTUND—F,

arithmetic fault, floating underflow at PC = 'xxxxxxxx', PSL =
'xxxxxxxx'

Facility: SYSTEM, VAX/VMS System Services
Explanation: During an arithmetic operation, a floating-point value became
less than the smallest representable value for that data type.
User Action: Examine the PC location displayed in the message; check the
program listing to verify that operands or variables are specified correctly.
FLUSH,

output stream flush requested

Facility: PSM, Print Symbiont
Explanation: This status is returned by a print symbiont output routine
requesting the output stream be flushed.
User Action: None.
FNA,

Flag not allowed in this context: 'string'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: (1) A flag has been used that requires that text directly precede
or follow it; or (2) a flag character has been replaced by another character (by
means of a .FLAGS command) and the previous function of the replacement
has not been disabled (by means of a .NO FLAGS command).
User Action: Check your usage of the flag, and make the appropriate
correction.

FNA,

invalid file name string address
Facility: RMS, VAX Record Management Services
Explanation: Either the file specification string address field in the FAB is
incorrect, or is in a portion of memory that cannot be read by the caller.
User Action: Verify that the call to the VAX RMS service was coded correctly.
Specifically, check that the symbolic address specified points to the correct
string.

FND,

ACP file or directory lookup failed
Facility: RMS, VAX Record Management Services
Explanation: An error occurred during a directory search. This message is
associated with a status code returned from a file system ACP QIO request
made by VAX RMS.
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.
2-181

FNF,

file not found
Facility: RMS, VAX Record Management Services
Explanation: The specified file does not exist.
User Action: Check the file specification and verify that the device, directory,
file name, and file type were all specified correctly. If a logical name was
specified, verify the current equivalence assigned to the logical name. If
the equivalence is correct, verify that the correct volume is mounted on the
specified device and that the file was not inadvertently deleted.

FNF,

file not found
Facility: SYSGEN, System Generation Utility
Explanation: SYSGEN was unable to locate the driver image file. The default
directory and disk device for driver images is SYS$SYSTEM. This message is
also produced during an AUTOCONFIGURE operation if a UNIBUS device
does not have a corresponding driver in SYS$SYSTEM.
User Action: Restore the image file to the system disk from a backup disk.

FNM,

error in file name

Facility: RMS, VAX Record Management Services
Explanation: The file name portion of a file specification is specified
incorrectly. For example, the file name contains more than 39 characters.
Or the use of a logical name resulted in more than one file name in the file
specification.
User Action: Verify the syntax of the file name in the file specification or in
the logical name, if a logical name was specified.
FOP,

invalid file options
Facility: RMS, VAX Record Management Services
Explanation: The file options parameter in the FAB contains conflicting
options. In particular, the UFO or NFS options were specified on an indirect
open of a process permanent file.
User Action: Verify that the call to the VAX RMS service was coded correctly.

FORCEDERROR,

forced error flagged in last sector read

Facility: SYSTEM, VAX/VMS System Services
Explanation: The data in this sector was copied from another sector that had
unrecoverable read errors. This message only applies to devices governed by
the Mass Storage Control Protocol (MSCP). This data was written with the
Forced Error Indicator set to show that the data is questionable to subsequent
readers.
User Action: Be aware that the contents of the sector are only a close
approximation of the data.

Messages

FORCEDEXIT,

forced exit of image or process by Job Controller

Facility: SYSTEM, VAX/VMS System Services
Explanation: When the job controller detects a violation of the login hour
restrictions specified in the authorization record for a user, the job controller
forces the process to terminate.
User Action: See the system manager.
FORMAT,

file has illegal format

Facility: LINK, VAX Linker
Explanation: This is a secondary message indicating the object file in
question has an illegal format.
User Action: Correct the source, recompile, and relink.
FORMAT,

invalid media format

Facility: SYSTEM, VAX/VMS System Services
Explanation: An I/O operation failed because the data medium is not in a
format that the device driver expected. If this message is associated with a
status code returned by a request to a magtape, the format specified by last
set tape characteristics function is not implemented in the slave controller.
User Action: Verify the physical data pack, reel, or cartridge to ensure
that the correct data medium is mounted. Contact a DIGITAL field service
representative if necessary.
FORWLOOP,

infinite forwarding detected sending to user 'username'

Facility: MAIL, Personal Mail Utility
Explanation: A forwarding loop has been created. This message is generated
after the Mail Utility has gone through the loop ten times.
User Action: Determine what caused the loop.
FREEBADBUF,

attempted to free busy (or free) buffer

Facility: BACKUP, Backup Utility
Explanation: A software error occurred in BACKUP.
User Action: Submit a Software Performance Report.
FREEMEM,

error freeing virtual memory

Facility: BACKUP, Backup Utility and VERIFY, Verify Utility
Explanation: Either the Backup Utility or the Verify Utility encountered an
error during an attempt to free dynamic virtual memory. The accompanying
message provides additional information. This message indicates a software
error in either the Backup Utility or the Verify Utility.
User Action: Submit a Software Performance Report.

2-183

FREEMEM,

Memory deallocation failure

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

Free page reference count is nonzero

Deallocated 'number' bytes of virtual memory leaving 'number'

Facility: CNF, NI Configurator
Explanation: The VM bit is set in NICONFIG$LOG. Every time virtual
memory is deallocated, the amount is tallied and the tally is signaled.
User Action: None.
FRERANGE,

storage package range error

Facility: PATCH, VAX Image File Patch Utility, DEBUG, VAX/VMS
Debugger
Explanation: An internal error has occurred.
User Action: Submit a Software Performance Report.
FRESIZE,

storage package size error

Facility: PATCH, VAX Image File Patch Utility
Explanation: An internal PATCH error has occurred.
User Action: Submit a Software Performance Report.
FREWSLX,

Free working set list index, resource wait

Messages

FSZ,

invalid fixed control header size
Facility: RMS, VAX Record Management Services
Explanation: The fixed control area size of the FAB for the file does not
contain the correct value. Files that have the print file record format must
have an FSZ value of 2.
User Action: Verify that the call to the VAX RMS service was coded correctly.

FTM,

network file transfer mode precludes operation (SQO set)
Facility: RMS, VAX Record Management Services
Explanation: For network file access, the FAB file option SQO selects DAP
(Data Access Protocol) file transfer mode. In this mode of operation, data
records are blocked together for transmission over the network to increase
data throughput and reduce CPU overhead. Selection of DAP file transfer
mode limits data transfers to one direction (either transmit using $PUT
/$WRITE or receive using $GET/$READ). Other VAX RMS services are
disallowed except for $DISCONNECT and $CLOSE which terminate file
transfer mode.
User Action: Verify that the call to the VAX RMS service was coded correctly.
Modify the source program to either not request the prohibited services or not
specify the SQO FOP option in the FAB.

FUL,

device full (insufficient space for allocation)
Facility: RMS, VAX Record Management Services
Explanation: A $CREATE, $EXTEND, or $PUT operation for a file failed
because there was not enough space on the volume.
User Action: Delete or purge as many files as possible to provide usable
space on the volume, or request the system operator to do so. If the volume
is private and files cannot be deleted, obtain a new volume.

FUNNOTSUP,

function not supported

Facility: PSM, Print Symbiont
Explanation: This status is returned indicating the current function is not
supported by the user service. For future compatibility, user services should
return this status for any unrecognized function code.
User Action: None.
FUTBAKDAT,

file ('file-id') 'file-name' backup date is in the future

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the date of the last backup
recorded for the file was later than the current date.
User Action: None. The backup date is set to the current date.
FUTCREDAT,

file ('file-id') 'file-name' creation date is in the future

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the creation date recorded for the
file was later than the current date.
User Action: None. The creation date is set to the current date.

2-185

Messages

FUTREVDAT,

file ('file-id') 'file-name' revision date is in the future

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the date of the last modification
recorded for the file was later than the current date.
User Action: None. The revision date is set to the current date.
FWF,

Footnotes won't fit on page
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: There are too many footnotes in the input file, or there are too
many lines in a footnote.
User Action: Reduce the number or size of the footnotes.

GBC,

invalid global buffer count
Facility: RMS, VAX Record Management Services
Explanation: An incorrect global buffer count value was specified. The global
buffer count value must be in the range of 0 to 32,767.
User Action: Verify that the call to the VAX RMS service was coded correctly.

GBLNOTCRE,

global section not created

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: The system program that maps TERMTABLE.EXE as a global
section was unsuccessful.
User Action: This message should be handled only by system managers. If
there is already an existing global section for Termtable, the system must be
rebooted in order to create a new global section.
GBLONLY,

cannot obtain global copy of image section 'image-section'

Facility: PATCH, VAX Image File Patch Utility
Explanation: The image being patched references a global copy of an image
section. There is no local copy of this section within the image file.
User Action: To patch such a section, you must patch the shareable image
file in which it is contained.
GBLPAGSZRO,

Global page share count is zero

2-186

Messages

GBLSECMAP,

system terminal table used

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: The requested terminal definition was found in the system
Termtable. The requested terminal definition did not exist in the caller's
private Termtable.
User Action: None.
GBLWARN,

patching local copy of global image section 'image-section'

Facility: PATCH, VAX Image File Patch Utility
Explanation: The image being patched: (1) references a global image section,
(2) contained a local copy of the global image section (only the local copy is
being patched), (3) is no longer allowed to use the shared global section.
User Action: Patch the shareable image instead of the executable image,
if you want to continue sharing the global section. You must reinstall the
shareable image after it is patched.
GBLWSLXERR,

Global working set list entry not found

generated ERROR: 'xxxxx' message

Facility: MACRO, VAX Macro Assembler
Explanation: A .ERROR directive was assembled; 'xxxxx' is the value of the
expression specified in the directive; and message is the text specified in the
directive.
User Action: Follow the instructions in the message.
GENWRN,

generated WARNING: 'xxxxx' message

Facility: MACRO, VAX Macro Assembler
Explanation: A .WARN directive was assembled; 'xxxxx' is the value of the
expression specified in the directive; and message is the text specified in the
directive.
User Action: Follow the instructions in the message.

2-187

Messages

GETCHN,

error getting device characteristics

Facility: DUMP, File Dump Utility
Explanation: The File Dump Utility encountered an error during an attempt
to obtain the device characteristics of the input device. The accompanying
message provides additional information.
User Action: Correct the condition that caused the error and reenter the
command.
GETCHN,

error getting device characteristics for 'device7

Facility: BACKUP, Backup Utility
Explanation: The Backup Utility encountered an error during an attempt
to obtain the device characteristics of the input device. The accompanying
message provides additional information.
User Action: Correct the condition that caused the error and reenter the
command.
GETDVI,

error getting device characteristics, RVN 'n'

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility encountered an error in an attempt to get
the device characteristics of 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.
GETDVI,

error obtaining device information for 'device-name'

Facility: BAD, Bad Block Locator Utility
Explanation: An error was encountered while attempting to obtain
information regarding the device.
User Action: Examine the associated diagnostic messages, making corrections
where appropriate.
GETERR,

get error

Facility: AUTHORIZE, Authorize Utility
Explanation: This message is issued with other messages.
User Action: Take corrective action based on the accompanying messages.
GETERR,

read error code of 'xx' on file 'file-spec'

Facility: PATCH, VAX Image File Patch Utility
Explanation: A VAX RMS $GET read request failed due to the error
represented as xx.
User Action: Correct the error (represented as xx) and retry.

2-188

Messages

GETJPI,

failed to obtain default job and process information

Facility: RUN, Run Detached Utility
Explanation: The system service $GETJPI failed to get process and job
information used to create new subprocess or detached process.
User Action: See error codes returned by the $GETJPI system service to
determine action.
GETMEM,

Memory allocation failure

Facility: VAX Text Processing Utility
Explanation: VAXTPU is attempting to allocate memory for its data
structures, but there is not sufficient free memory for it to do so. This error
may occur if you are using an extremely complex editing environment.
User Action: First, delete unneeded strings, ranges, markers, windows and
buffers, then reenter your command. If the error reoccurs, 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.
GETMSG,

error obtaining message text

Facility: BAD, Bad Block Locator Utility
Explanation: An error was encountered while attempting to obtain message
text.
User Action: Copy all pertinent diagnostic message information and submit
an SPR to DIGITAL.
GETPTIERR,

error from $GETPTI, buffer 'number:number', image VPN 'decimalnumber' for 'decimal-number' pages

Facility: LINK, VAX Linker
Explanation: An error was returned from the $GETPTI system service.
User Action: Submit a Software Performance Report with all relevant
programs, listings, object and library files.
GETTIM,

error code of 'xx' on $GETTIM

Facility: PATCH, VAX Image File Patch Utility
Explanation: The $GETTIM system service request failed due to the error
represented as xx.
User Action: Correct the error (represented as xx) and retry.
GETVM,

allocated 'number' bytes of virtual memory, total of 'number'

Facility: CNF, NI Configurator
Explanation: The VM bit is set in NICONFIG$LOG. Every time virtual
memory is allocated, the amount is tallied and the tally is signaled.
User Action: None.

2-189

Messages

GFC,

Given footnote count incorrect. Correct value is n
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: The actual number of lines generated for the footnote is greater
or less than the count specified with the .FOOTNOTE n command.
User Action: None; this is an informational message. If you do not want the
message to appear, remove the number from the .FOOTNOTE command.

GPGNULPGFL,

Global page has null page file address

global page table is full

Facility: SYSTEM, VAX/VMS System Services
Explanation: Not enough space is available in system memory to maintain
information about global sections. This message indicates a system error
resulting from insufficient allocated global page table space.
User Action: Notify your system operator or system manager.
GROUPOPER,

group

Facility: OPCOM, Operator Communication
Explanation: This message is issued optionally with the OPERSTS message.
It describes the class of the operator issuing the DCL command REPLY
/STATUS command.
User Action: No action is required.
GSDFULL,

global section descriptor table is full

Facility: SYSTEM, VAX/VMS System Services
Explanation: The system cannot create or map a global section because the
system space allocated for global section data is full. This message usually
indicates that the system was not generated with sufficient space for global
section descriptors.
User Action: Wait and retry the request. If the failure persists, notify the
system manager.

2-190

Messages

GSDTYP,

illegal GSD record type ('number') in module 'module-name' file
'file-name'

Facility: LINK, VAX Linker
Explanation: An illegal GSD Record type was found in the specified object
module.
User Action: Submit a Software Performance Report on the appropriate
language compiler.
GSDTYP,

illegal GSD record type 'type' in module 'module-name'

module 'module name' file 'library file-spec' has an illegal GSD record
'record type'

Facility: LIBRAR, LIBRARY Command
Explanation: This error message is generated by the DCL command
LIBRARY. The specified object module is illegally formatted.
User Action: Recompile the object module before inserting it into the library.
HALT,

Halt instruction restart

transfer has been halted

Facility: Shared by several facilities
Explanation: If this message is returned from a DR32 support routine call,
the DR32 transfer is complete.
User Action: If the DR32 transfer halted unexpectedly, determine the cause
of the error.
HANGUP,

data set hang-up

Facility: SYSTEM, VAX/VMS System Services
Explanation: The associated terminal data set has been hung up. A CTRL/Y
or unsolicited data AST was delivered.
User Action: None.

2-191

Messages

HBREAD,

error reading home block of

Facility: SET, SET Facility
Explanation: An error occurred while trying to read the home block of a
volume. This message is issued with an accompanying message.
User Action: Take corrective action based on the accompanying message.
HBWRITE,

error writing home block of

Facility: SET, SET Facility
Explanation: An error occurred while trying to write to the home block of a
volume. This message is issued with an accompanying message.
User Action: Take corrective action based on the accompanying message.
HDRBLK,

too many ISDs for image header blocks

Facility: PATCH, VAX Image File Patch Utility
Explanation: You requested too many image section descriptors; PATCH is
unable to create this patch area.
User Action: Relink your image file.
HDRCRC,

software header CRC error

Facility: BACKUP, Backup Utility
Explanation: An incorrect value occurred in the header CRC field (BBH$W_
CHECKSUM) of a save set block. Data in the save set is corrupted.
User Action: None. Save set data has been lost.
HDRNOTMAP,

Allocated file header not mapped

unable to make image header resident

Facility: INSTALL, Install Utility
Explanation: Insufficient pool was available to make the header resident, or
the file has an image header larger than one block.
User Action: Use the SYSGEN parameter PAGEDYN to increase the pool.
Only files with one block image headers may be made resident.

2-192

Messages

HDRTRUNC,

header truncated

Facility: LBR, Librarian Subroutine Package
Explanation: This warning message is generated by the Librarian routines.
The buffer supplied to LBR$SET_MODULE is smaller than the header.
User Action: Supply a larger buffer to LBR$ SET-MODULE.
HEADCOPIED,

copied 'file-header' header

Facility: BACKUP, Backup Utility
Explanation: The /LOG message indicating that a file header only was
copied. The file is marked NOBACKUP; therefore, no data is saved.
User Action: None.
HEADERFULL,

file header is full

Facility: SYSTEM, VAX/VMS System Services
Explanation: The file header map area on the volume is full and cannot be
extended. This error occurs only when the file header extension is inhibited,
for example, when the index file is being extended.
User Action: Compress the volume by copying it with BACKUP.
HELP,

enter HELP for INSTALL help

Facility: INSTALL, Install Utility
Explanation: This is an informational message.
User Action: Enter HELP for INSTALL help.
Help file could not be closed
Facility: EDT, EDT Editor
Explanation: You specified the name of a HELP file that EDT was unable
to close. Some problem exists at the system level that prevents EDT from
closing the file.
User Action: After determining the cause of the system problem, correct it.
Help file could not be opened
Facility: EDT, EDT Editor
Explanation: The requested EDT HELP file cannot be accessed. An error
in system storage has occurred (for example, improper installation of the
operating system).
User Action: Verify that the logical name EDTHELP (with a default of
SYS$HELP:.HLB) designates the EDT HELP file, and that the file has not
been damaged.

2-193

Help File Index could not be initialized
Facility: EDT, EDT Editor
Explanation: You created a new EDT HELP file or modified an existing EDT
HELP file, but either you neglected to include an index number or you placed
an indexed entry out of the proper nested order.
User Action: Include the omitted index number or place the indexed entry in
the proper nested order.
HELPERR,

HELP command error

Facility: MONITOR, Monitor Utility
Explanation: An error occurred during execution of the HELP 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 HELP command. This error can occur when the MONITOR help
library (SYS$HELP:MNRHELP.HLB) cannot be located or accessed.
HIB,

hibernating until requested beginning time ...
Facility: MONITOR, Monitor Utility
Explanation: Monitoring of the running system was requested, beginning at
a future time. The process that issued the MONITOR request is placed in the
hibernate state until the requested beginning time, at which time monitoring
will begin. This is an informational message.
User Action: If monitoring at a future time was desired, no user action is
required. If, however, the /BEGINNING qualifier was incorrectly specified
and if future monitoring was not desired, cancel the MONITOR request and
reissue it.

HIBER,

hibernating until 'time'

Facility: SHOW, SHOW Facility
Explanation: This is an informational message that is returned when the
SHOW CLUSTER command is invoked with the /BEGINNING=beginningtime qualifier. The message simply indicates that the current process will be
suspended until the time indicated.
User Action: None.
HIGHVER,

higher version of 'output file' already exists

Facility: Shared by several facilities
Explanation: An explicit version number was requested for an output file; the
directory already contains an entry for the same file name and file type with
a higher version number.
User Action: None. The message is informational. Note that if the file is
subsequently specified in a command, the system will locate the previously
existing version if no version number is specified. The newly created output
file will not be used.

Messages

HISTERR,

error accessing library update history in 'name7

Facility: LIBRAR, LIBRARY Command
Explanation: An error occurred while accessing the library update history
records. This message is issued with an accompanying message.
User Action: Take corrective action based on the accompanying message.
HOMBLKBAD,

primary home block is bad; backup used

Facility: MOUNT, MOUNT Command
Explanation: The primary home block of a disk is corrupted or unreadable;
the backup volume was used to mount the volume.
User Action: Repair the disk with the Verify Utility.
HOMBLKCHK,

home block software consistency check

Facility: MOUNT, MOUNT Command
Explanation: The home block in the volume has failed the software
consistency check during /BIND processing. The first occurrence of this
message is a warning; the second is fatal.
User Action: Repair or reinitialize the volume and retry the operation.
I/O error on work file
Facility: EDT, EDT Editor
Explanation: EDT is unable to access its text storage area for the file. An
additional message will explain the error further, such as "Device full" or
"Device write locked".
User Action: Correct the problem described in the file system message.
I/O error reading commands
Facility: DISKQUOTA, Diskquota Utility
Explanation: This message is issued with other messages.
User Action: Take corrective action based on the accompanying messages.
I/O error reading file header 7k7 on relative volume 7n7
Facility: DISKQUOTA, Diskquota Utility
Explanation: This message is issued with other messages.
User Action: Take corrective action based on the accompanying messages.
(The value of k is the file number of the file in error.)
I/O error reading index file bitmap on relative volume 'n'
Facility: DISKQUOTA, Diskquota Utility
Explanation: This message is issued with other messages.
User Action: Take corrective action based on the accompanying messages.

2-195

Messages

I/O error reading quota file
Facility: DISKQUOTA, Diskquota Utility
Explanation: This message is issued with other messages.
User Action: Take corrective action based on the accompanying messages.
IAL,

invalid argument list
Facility: RMS, VAX Record Management Services
Explanation: The argument list on a call to SYS$RMSRUNDWN,
SYS$SETDDIR, or SYS$SETDFPROT control routines either cannot be
accessed or contains invalid data.
User Action: Verify that the call to the VAX RMS service was coded correctly.

IAN,

invalid index area number for key = 'nnn'
Facility: RMS, VAX Record Management Services
Explanation: The index area number specified in a key definition XAB is not
a defined area 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 VAX RMS service
was coded correctly.

IBF,

illegal bucket format in VBN = 'nnn'
Facility: RMS, VAX Record Management Services
Explanation: VAX RMS detected a corrupted bucket in an indexed file.
Incorrect bucket control flags or an incorrect bucket freespace value was
detected.
User Action: Reorganize or recreate the file. The status value (STV) field of
the FAB or RAB contains the starting virtual block number of the bucket in
error.
This error is caused by hardware errors, VAX RMS or system software errors,
or inadvertent modifications of files by non-RMS programs.

IBK,

LAN bucket size not equal IAN bucket size for key = 'nnn7
Facility: RMS, VAX Record Management Services
Explanation: The bucket size for the index area specified by IAN must be the
same as the bucket size of the lowest-level index area specified by LAN.
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 VAX RMS service
was coded correctly. In particular, determine that the correct area numbers
and sizes were specified for the index and lowest-level index areas.

IBO,

Input buffer overflow: 'string'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: A character string that is too long has been entered in an
internal line buffer. This is a DSR internal error message.
User Action: Submit a Software Performance Report.

2-196

Messages

ICONCLUDAT,

Inconsistent cluster database

Inconsistent PFN database

Inconsistent page location

Invalid display descriptor: "text in error"
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: You specified a incorrect descriptor in a .DISPLAY directive.
User Action: Correct the specified descriptor.

IDENT,

DSRTOC version Version-number7

Facility: DSRTOC, DIGITAL Standard Runoff Table of Contents Utility
Explanation: This message is displayed when the /IDENTIFICATION
qualifier is specified. It shows the version number of the DSR Table of
Contents Utility.
User Action: None. This message is informational.

2-197

Messages

IDENT,

standalone BACKUP 'string7; the date is 'date-and-time7

Facility: BACKUP, Backup Utility
Explanation: This is a standalone BACKUP identification message.
User Action: Make sure that the displayed data is correct.
IDMISMATCH,

ident mismatch with global section or shareable image

Facility: SYSTEM, VAX/VMS System Services
Explanation: The ident is part of the global section name. An attempt was
made to create a shared memory global section using a different ident with a
name that was the same as an existing shared memory section.
This error occurs when an attempt is made to install an image in shared
memory (MA780) from two processors that do not have identical image files.
User Action: Copy the file from one processor to the other and retry the
operation.
IDMISMATCH,

Section NOT restored, section file must be rebuilt

Facility: VAX Text Processing Utility
Explanation: This version of VAXTPU is not compatible with the section file
that you are trying to access.
User Action: Save the section file again by running the source file through
the version of VAXTPU you are trying to use.
IDMISMCH,

GSMATCH of 7number,number7 in shareable image 7image-name7
differs from GSMATCH of 7number,number7 in shareable image
library 'library-name7

Facility: LINK, VAX Linker
Explanation: A shareable image extracted from a shareable image library has
a different GSMATCH than the GSMATCH recorded for that shareable image
in the library.
User Action: Insert the new shareable image into the shareable image library
using the DCL command LIBRARY.
IDR,

invalid directory rename operation
Facility: RMS, VAX Record Management Services
Explanation: A VAX RMS $RENAME service was requested that would
rename a directory file into a directory tree that contained the directory file.
The directory would then be inaccessible. An example of incorrect usage is:
$RENAME [A]B.DIR [A.B]

User Action: Modify the source program or reenter the command specifying
the correct old and new file specifications for the $RENAME service.

2-198

Messages

IDX,

index not initialized
Facility: RMS, VAX Record Management Services
Explanation: The index of an indexed file could not be properly initialized
when inserting the first record.
User Action: Recreate the file. Collect as much information as possible and
submit a Software Performance Report.

IDXCONCAT,

index file cannot be concatenated

Facility: Shared by several facilities
Explanation: An index file may not be concatenated with another file.
User Action: Use an indexed file load program to load the indexed file.
IDXFILEFULL,

index file is full

Facility: SYSTEM, VAX/VMS System Services
Explanation: No more files can be written on the volume, because the
maximum size of the index file specified was reached when the volume was
initialized.
User Action: If the volume is a private volume, delete the unwanted files on
the volume. If the volume is a system volume, notify the system operator or
system manager.
IDXHDRBAD,

index file header is bad; backup used

Facility: MOUNT, MOUNT Command
Explanation: This message is generated by the DCL command MOUNT. The
primary index file header is corrupted or unreadable; the backup volume was
used to mount the volume.
User Action: Repair the volume with the Verify Utility.
IDX—LIM,

exceeded maximum index level

Facility: CONVERT, Convert Utility
Explanation: The index tree depth exceeded 32 levels.
User Action: Redesign the file to make it more shallow.
IDXMAPERR,

I/O error on index file bitmap; volume locked

Facility: MOUNT, MOUNT Command
Explanation: I/O error encountered during a mount operation. Existing files
in the volume can be accessed but other operations, for example, create and
delete, are not possible.
User Action: Repair the volume with the Verify Utility.

2-199

Messages

IFA,

illegal file attributes detected (file header corrupted)
Facility: RMS, VAX Record Management Services
Explanation: The content of the file header has been corrupted; the data is
inconsistent and cannot be read.
User Action: Depending on the operation, the status value (STV) field in
the FAB or RAB contains a status code that provides additional information
about the condition. Take corrective action based on this status code. If the
error persists, collect as much information as possible and submit a Software
Performance Report.

IFDIRSYNX,

IF directive syntax error

Facility: MACRO, VAX Macro Assembler
Explanation: A conditional assembly directive contained a syntax error.
User Action: Correct the syntax of the directive.
IFEXPRNABS,

IF expression not absolute

Facility: MACRO, VAX Macro Assembler
Explanation: The expression in an .IF directive was not an absolute
expression or contained undefined symbols.
User Action: Change the values in the expression.
IFF,

invalid file attributes for requested file access
Facility: RMS, VAX Record Management Services
Explanation: The attributes of the file do not permit the type of file access
requested. For example, usually this means that the user attempted to open
an ANSI magnetic tape file for write access, and the file has a nonzero value
for buffer offset. VAX RMS will not allow you to create a magnetic tape file
with nonzero buffer offset. However, you may access the file for input and
output if you specify block I/O.
User Action: Correct the type of access requested or change the attributes of
the file.

IFI,

invalid internal file identifier (IFI) value
Facility: RMS, VAX Record Management Services
Explanation: The internal file identifier field of the FAB is invalid. This
error usually indicates that the file has not been opened for an operation
that requires the file to be opened, or that the file is already opened for an
operation that requires the file not to be opened.
User Action: Check for a programming error. Verify the logic of the program
to see that the file is opened or closed as required for the attempted operation.

2-200

Messages

IFL,

index bucket fill size larger than bucket size for key = 'nnn'
Facility: RMS, VAX Record Management Services
Explanation: The index bucket fill specified in a key definition XAB exceeds
the bucket size for the data area.
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 VAX RMS service
was coded correctly.

IFLEVLXCED,

IF nesting level exceeded

Facility: MACRO, VAX Macro Assembler
Explanation: The assembler encountered more than 31 levels of nested
conditional assembly blocks.
User Action: Restructure the program to decrease nesting of conditional
assembly blocks.
IFREPAGCNT,

Inconsistent free page count

Illegal in footnote: 'string'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: You attempted to use an illegal command between the DSR
command .FOOTNOTE and .ENDFOOTNOTE.
User Action: Remove the command.

IGNCLIFLAG,

line 'line-number': CLI flag ignored in this context

Facility: CDU, Command Definition Utility
Explanation: CDU encountered an illegal argument for CLI flags for the
current context.
User Action: Edit the .CLI file so that all CLI flags are valid in the context in
which they are used. Refer to VAX/VMS Command Definition Utility Reference
Manual for more information on the use of control flags in the Command
Definition Utility.

2-201

IGNFIL,

ignoring input file: 'file-specification7

Facility: MONITOR, Monitor Utility
Explanation: An input file specified in an /INPUT list has been excluded
from inclusion in a multi-file summary. The linked error message
accompanying this message provides an explanation for the exclusion.
User Action: If the ignored file was one which should be included in the
multi-file summary, then examine the linked error message, correct the
situation described therein, and reissue the MONITOR request.
IGNORED,

'string7 ignored

Facility: DSRTOC, DIGITAL Standard Runoff Table of Contents Utility
Explanation: DSR ignored a character string during processing.
User Action: None.
IGNORE _DIRE,

directory name ignored, not used for this volume type

Facility: EXCHANGE, Exchange Utility
Explanation: The EXCHANGE utility ignored the directory name field of a
filename.
User Action: Leave the directory off; it is not needed.
IGNORE—VERS,

file version ignored, not used for this volume type

Facility: EXCHANGE, Exchange Utility
Explanation: The EXCHANGE utility ignored the version number field of a
filename.
User Action: Leave the version number off; it is not needed.
IGNQUAL,

qualifiers apppearing before this item were ignored

Facility: CLI, Command Language Interpreter (DCL)
Explanation: This informational message signifies that the qualifiers
appearing before the displayed item were ignored.
User Action: None.
IIF,

"X ignored
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: A control character code fX) has been illegally entered in the
input file and has not been accepted.
User Action: In order to legalize the entry of such codes, you must issue the
.CONTROL CHARACTERS command.

ILC,

Illegal command: 'string'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: This command is illegal. Command or values you specify for it
are unrecognizable.
User Action: Check for spelling errors in the command keyword(s).

Messages

ILE,

Internal logic error 'string'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: DSR has detected an internal failure at the location specified by
the indicated string. This is a DSR internal error.
User Action: Submit a Software Performance Report.

ILLANSIBS,

ANS magnetic tape block size must be at least 18 characters

Facility: MOUNT, MOUNT Command
Explanation: The label specified for a magnetic tape contains less than 18
characters.
User Action: Reenter the command; specify a minimum value of 18 for the
block size.
ILL—ARG,

wrong number of arguments

Facility: FDL, Create/FDL Utility
Explanation: You specified too many files in the FDL$CREATE call.
User Action: Specify the correct number of files.
ILLARGDESC,

illegal operand argument descriptor

Facility: MACRO, VAX Macro Assembler
Explanation: The operand descriptor in an .OPDEF directive was invalid.
User Action: Use one of the valid operand descriptors.
ILLASCARG,

illegal ASCII argument

Facility: MACRO, VAX Macro Assembler
Explanation: Either the argument to a .ASCIx directive did not have
enclosing delimiters or an expression was not enclosed in angle brackets.
User Action: Correct the syntax of the argument.
ILLBATFNC,

operation not permitted while display is batched

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: An attempt was made to perform an operation that is not
permitted while a virtual display is being batched; for example, when
performing input or moving the virtual display.
User Action: Terminate batch processing first by calling SMG$END_
DISPLAY_UPDATE.
ILLBLKNUM,

illegal logical block number

Facility: SYSTEM, VAX/VMS System Services
Explanation: The logical block number specified does not exist on the disk. If
this error results from a Files-11 I/O operation, the file structure is damaged.
User Action: Check for a programming error. If this error results from a
Files-11 I/O operation, repair the volume with the Verify Utility.

2-203

Messages

ILLBRDEST,

illegal branch destination

Facility: MACRO, VAX Macro Assembler
Explanation: The destination of a branch instruction was not an address, for
example, BRB 10(R9).
User Action: Change the destination of the branch instruction or use a jump
(JMP) instruction.
ILLCDTST,

illegal connection descriptor table state

Facility: SYSTEM, VAX/VMS System Services
Explanation: A system facility attempted an operation on a connection that
was illegal for the current state of that connection.
User Action: Submit a Software Performance Report.
ILLCHR,

illegal character

Facility: MACRO, VAX Macro Assembler
Explanation: The source line contained a character that was illegal in its
context.
User Action: Delete the illegal character.
ILLCNTRFUNC,

illegal ACP control function

Facility: SYSTEM, VAX/VMS System Services
Explanation: The control function specified in an IO$_ACPCONTROL QIO
request is not a valid function.
User Action: Check for a programming error. Consult the documentation for
the correct function codes and coding specifications.
ILLCREOPT,

illegal create options

Facility: LBR, Librarian Subroutine Package
Explanation: This error message is generated by the Librarian routines.
Either the create options you specified for LBR$OPEN are illegal or no
options were specified.
User Action: Correct the create options before calling the routine.
ILLCTL,

illegal control index

Facility: LBR, Librarian Subroutine Package
Explanation: This error message is generated by the Librarian routines.
Either the library is not open or you have specified an illegal library index.
User Action: Determine that the library is open and that the library index is
correct.
ILLDESQUE,

illegal destination queue name

Facility: SYSTEM, VAX/VMS System Services
Explanation: In a request to the symbiont manager, the specified destination
queue is invalid.
User Action: Reenter the command, specifying a valid destination queue.

2-204

Messages

ILLDFLTARG,

illegal argument for .DEFAULT directive

Facility: MACRO, VAX Macro Assembler
Explanation: A .DEFAULT directive did not specify DISPLACEMENT or the
displacement specified was not one of the three keywords—BYTE, WORD, or
LONGWORD.
User Action: Correct the .DEFAULT directive.
ILLEFC,

illegal event flag cluster

Facility: SYSTEM, VAX/VMS System Services
Explanation: An event flag number specified in a system service call is
greater than 127.
User Action: Correct the source program. Verify that the event flag number
is correctly coded, and that it was not modified during the execution of the
image.
ILLEVTNUM,

Illegal event number

illegal expression

Facility: MACRO, VAX Macro Assembler
Explanation: A radix unary operator was not followed by a number, or left
and right angle brackets did not match in an expression.
User Action: Correct the syntax of the expression.
ILLFMLCN,

Minimum argument count ('decimal-number') exceeds maximum
('decimal-number') in formal specification of symbol 'symbol-name'
in module 'module-name' file 'file-name'

Facility: LINK, VAX Linker
Explanation: A procedure definition subrecord has an illegal format.
User Action: Submit a Software Performance Report on the appropriate
language compiler.

2-205

Messages

ILLFMLCNT,

minimum argument count exceeds maximum for procedure
'procedure7 in module 'module'

illegal library format

Facility: LBR, Librarian Subroutine Package
Explanation: This error message is generated by the Librarian routines. The
file you specified calling LBR$OPEN is not a library.
User Action: Specify the correct library.
ILLFUNC,

illegal library function

Facility: LBR, Librarian Subroutine Package
Explanation: This error message is generated by the Librarian routines. The
library function you specified in LBR$OPEN is illegal.
User Action: Correct the library function before calling the routine.
ILLIDXNUM,

illegal index number

Facility: LBR, Librarian Subroutine Package
Explanation: This error message is generated by the Librarian routines. The
index number you specified is illegal.
User Action: Correct the index number before calling the routine.
ILLIFCOND,

illegal IF condition

Facility: MACRO, VAX Macro Assembler
Explanation: The condition specified in a conditional assembly was not a
valid condition, or there were no symbols after a DIFFERENT or IDENTICAL
condition.
User Action: Correct the syntax of the conditional assembly directive.
ILLINDTYPE,

index type must be scalar or subrange

Facility: DEBUG, VAX/VMS Debugger
Explanation: An index for an array must be a scalar variable, constant, or
variable of a scalar subrange type.
User Action: Change the index to a scalar variable or a scalar subrange.

2-206

Messages

ILLINDXREG,

invalid index register

Facility: MACRO, VAX Macro Assembler
Explanation: The base mode changed the value of the register, and the index
register was the same as the register in the base mode; the base mode was
literal or immediate mode; or PC was used as the index register.
User Action: Correct the addressing mode.
ILLINROU,

input routine improperly specified or missing

Facility: LBR, Librarian Subroutine Package
Explanation: A librarian function was called with a missing or invalid input
routine parameter.
User Action: If no input routine was passed to the librarian function, then
supply one; or check the values of the other arguments that were passed to
ensure that none of the arguments specify that the input routine parameter
is required. If a routine value was supplied, then check that it is a valid
address,(for example, nonzero).
ILLIOFUNC,

illegal I/O function code

Facility: SYSTEM, VAX/VMS System Services
Explanation: A function code in an explicit input/output request was invalid.
Or if the errors occurred during a DECnet-VAX operation, the user attempted
a synchronous disconnect with outstanding transmits.
User Action: Check for a programming error. Locate the invalid function
code and correct it.
ILL _KEY,

illegal key or value out of range

Facility: CONVERT, Convert Utility
Explanation: You have specified /KEY with a nonnumeric value, or with a
numeric value that is outside the range of 0 to 254.
User Action: Specify a legal value with /KEY.
ILLKEYLVL,

illegal key level 'number7 key 'keyname' in 'library file-spec'
expected 'key number'

Facility: LIBRAR, LIBRARY Command
Explanation: This error message is generated by the DCL command
LIBRARY. The help module you want to insert into the library is formatted
incorrectly.
User Action: Reformat the module before inserting it into the library.
ILLMACARGN,

illegal MACRO argument name

Facility: MACRO, VAX Macro Assembler
Explanation: The name in the .MACRO directive contained an illegal
character.
User Action: Delete the illegal character.

2-207

ILLMACNAM,

illegal MACRO name

Facility: MACRO, VAX Macro Assembler
Explanation: No MACRO name was specified in the .MACRO directive.
User Action: Specify the MACRO name in the .MACRO directive.
ILLMASKBIT,

reserved bits set in ENTRY mask

Facility: MACRO, VAX Macro Assembler
Explanation: The register save mask in an .ENTRY or .MASK directive
specified RO, Rl, AP, or FP registers (corresponding to bits 0, 1, 12, and 13).
User Action: Remove these registers from the register save mask.
ILLMODE,

illegal mode

Facility: MACRO, VAX Macro Assembler
Explanation: An invalid addressing mode for the instruction was specified.
User Action: Specify a legal addressing mode.
ILLMODNAM,

illegal module name length 'length' for module 'module'

cannot specify same magtape for both input and output

Facility: EXCHANGE, Exchange Utility
Explanation: The EXCHANGE utility detected an attempt to use a single
DOS-11 magtape for both input and output.
User Action: Specify different magtapes for input and output, or copy the file
onto disk before copying it back out to tape.
ILLNAMELEN,

'name' 'name' name length ('decimal-number') is illegal - not 1 to
'decimal-number' in module 'module-name' file 'file-name'

Facility: LINK, VAX Linker
Explanation: The length of a psect, module, or symbol name is illegal.
User Action: Correct the length and relink.
ILLOP,

illegal operation for access requested

Facility: LBR, Librarian Subroutine Package
Explanation: This error message is generated by the Librarian routines. You
have attempted to modify a Version 1.0 library or a read-only library.
User Action: Compress the library into the current format or change the
access privileges to the library file.

Messages

ILLOPDEF,

illegal format for .OPDEF

Facility: MACRO, VAX Macro Assembler
Explanation: The .OPDEF directive had incorrect syntax.
User Action: Correct the .OPDEF directive syntax.
ILLOPDEFVL,

illegal value for opcode definition

Facility: MACRO, VAX Macro Assembler
Explanation: The value specified in the .OPDEF directive does not fit in two
bytes.
User Action: Correct the value in the directive.
ILLOPT,

qualifier(s) not appropriate to this device

Facility: MOUNT, MOUNT Command and INIT, INITIALIZE Volume
Command
Explanation: A DCL command MOUNT or INITIALIZE specified qualifiers
that apply only to disk devices for a tape device, or qualifiers that apply only
to tape devices for a disk device.
User Action: Use the DCL command HELP or refer to the VAX/VMS
DCL Dictionary for a list of qualifiers, and reenter the command with the
appropriate qualifier(s).
ILLOUTROU,

output routine improperly specified or missing

Facility: LBR, Librarian Subroutine Package
Explanation: A librarian function was called with a missing or invalid output
routine parameter.
User Action: If no output routine was passed to the librarian function, either
supply one or check the values of the other arguments that were passed. This
ensures that none of the arguments specify that an output routine parameter
is required. If a routine value was supplied, check to see that it is a valid
address, for example, nonzero.
ILLPAGCNT,

illegal page count parameter

Facility: SYSTEM, VAX/VMS System Services
Explanation: The number of pages specified for an expand or delete region
request was less than one.
User Action: Check for a programming error; verify the number of pages
specified for the service call.
ILLPSCLEN,

psect 'psect' has illegal length 'length7 for module 'module7

2-209

ILLQUAL,

invalid qualifier

Facility: MOUNT, MOUNT Command
Explanation: An invalid qualifier was given in the command.
User Action: Replace the qualifier and reenter the command.
ILLQUALVAL,

illegal qualifier value

Facility: LINK, VAX Linker
Explanation: The command line contained an illegal value for a qualifier.
User Action: Reenter the command correctly.
ILLRECLEN,

illegal record length length' in module 'module'

Facility: LIB, Run-Time Library General Procedures
Explanation: The Run-Time Library encountered severe format errors in the
shareable image you trying to call.
User Action: Issue the ANALYZE/IMAGE command specifying the image in
question. If the errors indicate an operating system internal error, submit a
Software Performance Report.
ILLRECLEN,

illegal record length ('decimal-number') in module 'module-name'
file 'file-name'

Facility: LINK, VAX Linker
Explanation: A module contains a record of illegal length.
User Action: Submit a Software Performance Report on the appropriate
language compiler.
ILLRECLN2,

illegal record length 'length'

illegal record type 'record-type'

Messages

ILLRECTYP,

illegal record type ('decimal-number') in module 'module-name'
record 'record-name' file 'file-name'

Facility: LINK, VAX Linker
Explanation: A module contains an illegal object record type.
User Action: Submit a Software Performance Report on the appropriate
language compiler.
ILLRECTYP,

illegal record type 'type' in module 'module'

this register may not be used here

Facility: MACRO, VAX Macro Assembler
Explanation: The PC register cannot be used in the following addressing
modes: register, register deferred, autodecrement, autoincrement, and
autoincrement deferred.
User Action: Use another register.
ILLREGNUM,

illegal register number

Facility: MACRO, VAX Macro Assembler
Explanation: A register name was not the AP, FP, SP, or PC register name.
Or it was not in the range RO through R12.
User Action: Correct the illegal register name.
ILLRQST,

illegal operator request

Facility: OPCOM, Operator Communication
Explanation: A DCL command REPLY was issued with no qualifiers. Or, a
DCL command REQUEST specified an incorrect value.
User Action: Verify the command line and reenter the command.
ILLSELF,

illegal self reference

Facility: SYSTEM, VAX/VMS System Services
Explanation: You have unsuccessfully attempted to suspend all action on
your own job.
User Action: None. Your job is not suspended.

2-211

Messages

ILLSEQOP,

illegal sequential operation

Facility: SYSTEM, VAX/VMS System Services
Explanation: When a sequential access device is used, such as a magnetic
tape, certain operations can be performed only at the appropriate time. For
example, the control function NEXT VOLUME can be executed only when
the tape is positioned within the data section.
User Action: Examine the source program to determine the logic problem.
ILLSER,

illegal service call number

Facility: SYSTEM, VAX/VMS System Services
Explanation: An image specified a call to a procedure whose name is entered
in the system service vector table, but the procedure is not a valid service.
User Action: Check for a programming error. Locate the illegal call and
correct it.
ILLSHROPR,

illegal shareable image reference expression operator in module
'module-name7 record 'record-name7 file 'file-name'

Facility: LINK, VAX Linker
Explanation: An attempt was made to perform an operation, other than
addition or subtraction, in an expression that contained a symbol from a
shareable image.
User Action: Correct the expression and relink.
ILLSHRXPR,

illegal shareable image reference expression in module 'modulename' record 'record-name' file 'file-name'

Facility: LINK, VAX Linker
Explanation: An expression contains two symbols externally defined in a
shareable image. The linker can resolve expressions that contain only one
externally defined symbol.
User Action: Correct the expression and relink.
ILLSIGEXT,

illegal sign extension field value xxx

Facility: DEBUG, VAX/VMS Debugger
Explanation: An illegal value has been entered for the sign extension field in
a field reference.
User Action: Reenter the command using a valid sign extension field value.
ILLSTRCLA,

illegal string class

Facility: STR, Run-Time Library String Procedures
Explanation: The class code found in the class field of a descriptor is not
a string class code supported by the VAX/VMS Procedure Calling and
Condition Handling Standard.
User Action: If you are programming in a high-level language and using the
string data types and functions that are supplied by the language, check that
there are no logic errors where data is written outside array bounds or other
errors where data is written incorrectly. If you are creating descriptors, check
that all string descriptors are initialized before using them.

2-212

Messages

ILLSTROPS,

illegal string position

Facility: STR, Run-Time Library String Procedures
Explanation: Successful completion. However, one of the character-position
parameters to a string routine pointed to a character-position that was before
the beginning of the input string or that was after the end of the input string.
User Action: Ensure that any parameter that is a character-position is greater
than zero and less than or equal to the length of the input string.
ILLSTRSPE,

illegal string specification

Facility: STR, Run-Time Library String Procedures
Explanation: Successful completion except that the character-position
parameters specifying a substring of a string parameter were inconsistent
because the ending character-position was less than the starting characterposition. A null string was used for the substring.
User Action: The user program should verify that starting character-positions
are less than or equal to ending character-position.
ILLSYMLEN,

symbol 'symbol' has illegal length 'length' in module 'module'

symbol exceeds 31 characters

Facility: MACRO, VAX Macro Assembler
Explanation: The symbol name was longer than 31 characters. The
assembler truncated the name to 31 characters.
User Action: Specify a symbol name that has no more than 31 characters.
ILLTIR,

illegal relocation command 'command-name' in module 'module-name'
record 'record-name' file 'file-name'

Facility: LINK, VAX Linker
Explanation: A module contains an illegal object language command.
User Action: Submit a Software Performance Report on the appropriate
language compiler.
ILLTYP,

illegal library type

Facility: LBR, Librarian Subroutine Package
Explanation: This error message is generated by the Librarian routines. The
type of library specified in LBR$INI_CONTROL is illegal.
User Action: Correct the library type before calling the routine.

2—213

ILLTYPE,

illegal type of operand(s)

Facility: DEBUG, VAX/VMS Debugger
Explanation: The type of the operand is illegal for the operator specified.
User Action: Change the operand.
ILLVAL,

boolean value must be 0 or 1

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: A Boolean capability was given a value other than 0 or 1.
User Action: Check your terminal definitions. Boolean capabilities must be 0
or 1; on or off respectively.
ILLVAL,

illegal CPU time

Facility: RUN, Run Detached Utility
Explanation: The CPU time limit entered with the /TIME —LIMIT qualifier
value was too large.
User Action: Reenter the RUN command with a valid CPU time limit
ILLVAL,

illegal value is present

Facility: CLI, Command Language Interpreter (DCL)
Explanation: A value is not within the legal range of values.
User Action: Use the DCL command HELP or refer to the VAX/VMS DCL
Dictionary if necessary, for the legal values and reenter the command.
ILL—VALUE,

illegal parameter value

Facility: CONVERT, Convert Utility
Explanation: You have specified an illegal or out-of-range value on a
qualifier.
User Action: Specify a valid value and try again.
ILLVEC,

Illegal interrupt or exception vector restart

Messages

ILLVPS,

illegal position ('decimal-number7) or size ('decimal-number7) in STO_
VPS command 'command-name' in module 'module-name' file 'file¬
name'

Facility: LINK, VAX Linker
Explanation: The STO—VPS object language command has illegal arguments.
User Action: Submit a Software Performance Report on the appropriate
language compiler.
IMAGEFMT,

command tables image has illegal format

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

image file not found 'file-name'

Facility: CLI, Command Language Interpreter (DCL)
Explanation: You attempted to run a nonexistent image.
User Action: Check for typing errors and retry.
IMAGELEN,

an image spec is limited to 'max-length' characters in length

Facility: CDU, Command Definition Utility
Explanation: CDU encountered a image specification in the CLD file which
exceeded the maximum allowable file specification character count. Currently
file specification strings are limited to 63 characters in length.
User Action: Rename the image and/or use logical names to specify the
directory of the image.
IMAGE—NOT—FOUND,

this image has not yet been mapped

Facility: IMG ACT, Image Activator
Explanation: An inconsistency exists between the shared image list stored in
the image fixup vector and the list of global ISDs stored in the image header.
This can possibly occur when images linked on older versions of VAX/VMS
are run on newer versions where new copies of shareable images are being
referenced by the old executable image.
User Action: Relink the executable images to achieve a consistent shareable
image linkage mechanism within the image header of your image.
IMGBASED,

shareable image 'image-name' is already based

Facility: LINK, VAX Linker
Explanation: You specified a base address in an options file for a shareable
image that is already based.
User Action: Make the image position-independent so it can be based
anywhere; or remove the cluster option from the options file that tries to base
it.

2-215

IMGFILSPE,

/IMAGE specification must have only device name

Facility: BACKUP, Backup Utility
Explanation: The file specification for a volume to be processed with the
/IMAGE qualifier must contain only a device name.
User Action: Reenter the command using the device name only.
IMGHDR,

error while accessing the image header

Facility: INSTALL, Install Utility
Explanation: INSTALL encountered an error when trying to access the image
header. An accompanying error message explains the failure.
User Action: Correct the situation indicated by the accompanying error
message and reissue the command.
IMGNAME,

image file 'file-name'

Facility: CLI, Command Language Interpreter (DCL)
Explanation: This message is issued with an associated message indicating
the problem.
User Action: Take corrective action based on the associated message.
IMG—SIZ,

image header descriptor length is invalid

Facility: IMG ACT, Image Activator
Explanation: The length of the fixed part of the image header is invalid. This
usually indicates a corrupted or invalid image.
User Action: Relink the image.
IMGTRACED,

TRACEBACK image cannot be privileged or execute_only

Facility: INSTALL, Install Utility
Explanation: This message indicates that an attempt was made to CREATE or
REPLACE a known file image with either the /PRIVILEGE or /EXECUTE—
ONLY qualifiers, and that the image had been linked with the /TRACEBACK
qualifier.
User Action: Relink the image using the /NOTRACEBACK qualifier and
retry the image installation.
IMX,

invalid duplicate XAB or non-dense XAB at 'location'
Facility: RMS, VAX Record Management Services
Explanation: More than one XAB of the same type exists for the operation;
or another XAB type occurs within a subchain of allocation or key definition
XABs.
User Action: The status value (STV) field of the FAB provides the address
of the XAB in error. Verify that the call to the VAX RMS service was coded
correctly.

Messages

INCBADDIR,

saved directory 'directory-name7 has invalid format

Facility: BACKUP, Backup Utility
Explanation: In response to the /INCREMENTAL qualifier, the saved copy
(in the input save set) of the specified directory was not in the expected
format for a directory file. The file may have been corrupted when it was
saved, or save set data may have been lost.
User Action: After you complete the incremental restoration, check the files
for correct format.
INCDELERR,

error deleting 'file-name'

Facility: BACKUP, Backup Utility
Explanation: An error was encountered during an attempt to delete
the specified file in response to the /INCREMENTAL qualifier. The
accompanying message provides additional information.
User Action: Correct the condition that caused the error and reenter the
command.
INCDELETE,

deleted 'file-name'

Facility: BACKUP, Backup Utility
Explanation: The Backup Utility deleted the specified file in response to the
/INCREMENTAL qualifier. This message appears if you specify the /LOG
qualifier.
User Action: None.
INCDEVLIS,

disk and tape devices mixed in list

Facility: BACKUP, Backup Utility
Explanation: Disk and tape devices were mixed in a list of file specifications.
User Action: Reenter the command ensuring that if a list is used, the devices
in a list are the same type.
INCDSTNES,

incorrect DST nesting in module xxx, compiler error

Facility: DEBUG, VAX/VMS Debugger
Explanation: Incorrect Debug Symbol Table nesting occurred, such as
improper routine or data record nesting in the specified module. This message
normally indicates a compiler error.
User Action: Submit a Software Performance Report.
INCDSTQUE,

inconsistent destination queue type

Facility: JBC, Job Controller
Explanation: The type of the specified destination queue is inconsistent with
the requested operation.
User Action: Specify an appropriate type of destination queue for the
operation.

2-217

INCENTERR,

error creating directory entry for 'file-name'

Facility: BACKUP, Backup Utility
Explanation: The Backup Utility encountered an error during an attempt
to create a directory entry for the specified file in response to the
/INCREMENTAL qualifier.
User Action: Correct the condition that caused the error and reenter the
command.
INCENTRY,

incomplete entry type, 'entry type value'

Facility: ERF, ANALYZE/Error Log Utility
Explanation: While an error log entry was being made, only a portion of the
entry was logged.
User Action: This is an irrecoverable error.
INCFILSPE,

/INCREMENTAL specification must have only device name

Facility: BACKUP, Backup Utility
Explanation: The file specification for a volume to be processed with the
/INCREMENTAL qualifier must contain only a device name.
User Action: Reenter the command using only the device name.
INCFORMPAR,

inconsistent form parameters

Facility: JBC, Job Controller
Explanation: The specified length, width, and margin parameters are
inconsistent. The sum of the top and bottom margins must be less than
the length, and the sum of the left and right margins must be less than the
width.
User Action: Correct the incorrect form parameter(s).
INCHMK,

inhibited CHMKemel trap

Facility: SYSTEM, VAX/VMS System Services
Explanation: A user program attempted a system service that was inhibited
to it.
User Action: Ask the system manager which system services are currently
inhibited and remove them from the program.
Include file could not be closed
Facility: EDT, EDT Editor
Explanation: You specified the name of a file that EDT could not close while
using the INCLUDE command. Some problem exists at the system level that
prevents EDT from closing the file.
User Action: After determining what system problem prevents EDT from
closing the file, correct it.

Messages

Include file could not be opened
Facility: EDT, EDT Editor
Explanation: You specified the name of a file that EDT could not open while
using the INCLUDE command. Some problem exists at the system level that
prevents EDT from opening the file.
User Action: After determining what system problem prevents EDT from
opening the file, correct it.
Include file does not exist
Facility: EDT, EDT Editor
Explanation: You typed a file specification with the INCLUDE command for
a file that does not exist. The file might exist in a directory other than the
one you specified or implied with the command. Or you might have made a
typographical error in the file specification.
User Action: Enter the correct include file specification.
Include file input record too large, truncated to 255 characters
Facility: EDT, EDT Editor
Explanation: EDT can handle only 255 characters on a line. The file you
want to include has one or more lines in it that exceed 255 characters. EDT
truncates the line to be only 255 characters long.
User Action: None.
INCMEMNAM,

specified shared memory name does not match

Facility: SYSGEN, System Generation Utility
Explanation: The logical name assigned to the shared memory by the
SYSGEN command SHARE does not match the name in the database of
shared memory that was specified previously.
User Action: Reissue the command with the correct name.
INCOMPACP,

indicated ACP is incompatible with 'volume'

Facility: MOUNT, MOUNT Command
Explanation: The ACP specified is not an ACP for the requested device.
User Action: Reenter the command; specify an ACP that is appropriate for
the particular device type.
INCOMP AT,

'input-file' (input) and 'output-file' (output) have incompatible
attributes

Facility: Shared by several facilities
Explanation: This warning message indicates that file incompatibility may
exist between files that have been appended or concatenated. This message
can occur if files created by different methods are concatenated, for example,
files created with the DCL command WRITE and files created by the DCL
command SORT/RSX11. The command continues execution.
User Action: Determine whether the incompatibility presents a problem and
if it does, delete the output file(s), modify the format of one or more input
files, and reenter the command.

2-219

The format of a file can be modified by editing the file with the SOS or SLP
editors and creating a new version of the file.
INCOMPAT,

Feature incompatible with previous system version

Facility: SYSTEM, VAX/VMS System Services
Explanation: This alternate success status indicates that the function
requested is not compatible with the version of the I/O driver in use. This
error message typically occurs when a remote terminal link is used between
different versions of VAX/VMS. For example, it could indicate that the
function requested by the newest VAX/VMS Version 3.0 is not implemented
on the previous VAX/VMS Version 2.5.
User Action: Upgrade systems using remote terminals so that they use the
same version of the operating system.
INCOMPAT,

qualifiers incompatible with already mounted volume

Facility: MOUNT, MOUNT Command
Explanation: A DCL command MOUNT was issued to mount a shareable
volume that is already mounted; the characteristics of the volume are already
established and cannot be changed.
User Action: Use the DCL command SHOW DEVICE to determine how the
volume is mounted. Reenter the DCL command MOUNT/SHARE without
qualifiers.
INCOMPLETE,

previous incomplete operation prevents execution

Facility: JBC, Job Controller
Explanation: The requested queue management operation cannot be executed
because a previously requested queue management operation had not yet
completed.
User Action: It may be necessary to use the STOP/RESET command to gain
control of the queue.
INCONISD,

inconsistent ISD structures detected

Facility: IMG ACT, Image Activator
Explanation: Either an image section descriptor was found to cross an image
header block boundary, or there was an indication that an ISD would be
found in the next header block and there was no such ISD. This usually
indicates a corrupted or invalid image.
User Action: Relink the image.
INCONSDEV,

inconsistent device types

Facility: MOUNT, MOUNT Command
Explanation: Both disks and magnetic tapes appear in the list of devices to
be mounted.
User Action: Specify one or the other and reenter the command; check the
logical name assignments.

Messages

INCONSTATE,

Inconsistent UBA database

Increment page table reference count error

inconsistent queue type

Facility: JBC, Job Controller
Explanation: The type of the specified queue is inconsistent with the
requested operation.
User Action: Specify an appropriate type of queue for the operation.
INCQUOTA,

QUOTA.SYS indicates 'n' blocks used, actual use is 'n' blocks for
['uic']

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the disk usage for the specified
UIC, as recorded in the quota file, did not agree with the actual disk usage.
User Action: None. The quota file is corrected.
INCRVN,

incorrect relative volume mounted on 'device'

Facility: BACKUP, Backup Utility
Explanation: Either the wrong volume of a multivolume disk save-set has
been mounted, or the positional order of the devices in the input specification
does not agree with the relative volume numbers recorded on the volumes.
User Action: Locate and mount the correct volume.

2-221

Messages

INCSEGTRA,

incomplete segmented transfer request posted

Facility: SYSTEM, VAX/VMS System Services
Explanation: A driver returned a success status but failed to complete the
current segment of a segmented transfer.
User Action: If this error can be reliably reproduced, the media and program
producing the error should be submitted with a Software Performance Report.
INCSETCNT,

incorrect number of devices in input specification

Facility: BACKUP, Backup Utility
Explanation: The number of devices in the input specification does not agree
with the volume set count recorded on relative volume 1.
User Action: Reenter the command with the correct number of devices.
INCVOLLABEL,

incorrect volume label

Facility: SYSTEM, VAX/VMS System Services
Explanation: The label specified does not match the label on the volume.
User Action: Verify that the correct volume is mounted; verify the label
entered. Repeat the request specifying the correct volume label or specifying
OVERRIDE:ID, which requires either that you have the volume protection
privilege or that you are the volume owner.
INDEX,

invalid index file position

Facility: INIT, INITIALIZE Volume Command
Explanation: The block specified for the position of the index file for a disk
volume is larger than the number of blocks on the disk. The DCL command
INITIALIZE cannot write the index file.
User Action: Reenter the command; specify a position for the index file that
is within the range of blocks on the volume.
INDEXERR,

index error in 'library file-spec'

Facility: LIBRAR, LIBRARY Command
Explanation: Possible causes of the error are:
•

An error occurred while searching or traversing the index

•

A VAX RMS error occurred

•

Not enough virtual memory is available

User Action: Compress the library before reentering the command string.
INDEXOVFL,

index area overflow in section - please submit SPR

Facility: MESSAGE, Message Utility
Explanation: An internal error in the compiler has been detected.
User Action: Submit a Software Performance Report.

2-222

Messages

IND—OVR,

indexed output file must already exist

Facility: SORT, VAX SORT/MERGE Utility
Explanation: You specified indexed output file organization, but the file did
not already exist.
User Action: First create the indexed file with the RMS Define Utility. The
primary key of the file should be the same as the sort key for efficiency, but
is not required.
INHCHME,

inhibited CHME executive trap

improperly nested: 'string'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: Your conditional DSR commands (.IF/.IFNOT and .ELSE
/.ENDIF) are improperly matched.
User Action: Correct the DSR commands so they match.

INICLOSIN,

error closing input initialization file

Facility: ACLEDIT, Access Control List Editor
Explanation: The ACL editor encountered an error closing the initialization
file.
User Action: Examine the secondary error status to determine exactly why
the initialization file closing failed (privilege violation, device write locked,
etc.)
INIOPENIN,

error opening 'file-name' as input initialization file

Facility: ACLEDIT, Access Control List Editor
Explanation: The ACL editor was unable to open the initialization file
indicated by the logical name ACLEDIT$INIT.
User Action: Examine the secondary error status to determine exactly why
the open failed (privilege violation, nonexistent file, etc.)
INIREADERR,

error reading 'file-name' as input initialization file

Facility: ACLEDIT, Access Control List Editor
Explanation: The ACL editor encountered an error while reading the
initialization file (indicated by the logical name ACLEDIT$INIT).
User Action: The file is most likely corrupted. It should be restored from a
recent backup.

2—223

Messages

INITERR,

error initializing 'library file-spec'

Facility: LIBRAR, LIBRARY Command
Explanation: There is insufficient virtual memory available.
User Action: Ask the system manager to increase your page file quota or
VIRTU ALP AGECNT.
INITERR,

error initializing 'library name'

Facility: LIBRAR, LIBRARY Command
Explanation: An error occurred initializing the specified library. This
message is issued with an accompanying message.
User Action: Take corrective action based on the accompanying message.
INITIAL,

language is xxx, module set to yyy

Facility: DEBUG, VAX/VMS Debugger
Explanation: This message is displayed when the debugger is invoked by the
image activator. The language is set to xxx, and the module to yyy. Module
yyy is the first module specified in the LINK command, and language xxx is
the language used in that module.
User Action: None.
INITLES,

failed to initialize LES

Facility: PSI, VAX Packetnet System Interface
Explanation: LES did not initialize correctly. This message is qualified by a
secondary message in the form SS$_code. Typically, this message is caused
by insufficient memory.
User Action: Increase the size of the nonpaged pool and try again.
INITNW,

failed to initialize NW after successfully loading PSI

Facility: PSI, VAX Packetnet System Interface
Explanation: The QIO issued to initialize NW failed. This message is
qualified by a secondary message in the form SS$_code. Typically, this
message is caused by insufficient memory.
User Action: Increase the size of the nonpaged pool and try again.
INITPRS,

error code of 'xx' on command line parse init

Facility: PATCH, VAX Image File Patch Utility
Explanation: A CLI callback failure occurred due to the error represented as
xx.
User Action: Submit a Software Performance Report.
INM,

Illegal number value: 'string'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: The parameter value is too large, too small, illegal, or not a
number.
User Action: Check to see that the value is formatted properly.

2-224

Messages

INPCONERR,

input conversion error

Facility: OTS, Language Independent Run-Time Library Support Procedures
Explanation: There is an invalid character in the input string. Or the output
value is not within the range of destination data type.
User Action: Correct the input string or change the destination data type.
INP—FILES,

too many input files

Facility: CONVERT, Convert Utility
Explanation: You listed more than 10 input files.
User Action: Reduce the number of input files or combine them so that you
list no more than 10.
INP—FILES,

too many input files specified

Facility: SORT, VAX SORT/MERGE Utility
Explanation: You listed more than 10 input files.
User Action: Reduce the number of input files or combine them so that you
list no more than 10.
INPSTRTRU,

input string truncated

Facility: LIB, Run-Time Library General Procedures
Explanation: An input string accepted by LIB$GET—INPUT has been
truncated to fit the string descriptor passed to it. This message is associated
with a status code returned from a Run-Time Library procedure and is not
normally displayed by the operating system.
User Action: Correct your program by increasing the field length in the
descriptor.
INPUT,

'file-name', 'n' selected, 'n' rejected

Facility: ERF, ANALYZE/Error Log Utility
Explanation: This message reports the input file name and the number of
entries selected or rejected from the input file.
User Action: None.
INPUT,

'file-spec', 'n-records' selected, 'n-records ' rejected

Facility: ACCOUNTING, Accounting Utility
Explanation: This informational message is displayed when the /LOG
qualifier is used. It describes how many records were selected and/or rejected
for each input file.
User Action: None.

2-225

Messages

Input file could not be closed
Facility: EDT, EDT Editor
Explanation: EDT could not close the input file that you named in your EDIT
/EDT command line or in the line mode INCLUDE command line. Some
problem exists at the system level that prevents EDT from closing the file.
User Action: After determining what system problem prevents EDT from
closing the file, correct it.
Input file could not be opened
Facility: EDT, EDT Editor
Explanation: Either the command contains faulty syntax or a nonexistent
directory was specified.
User Action: Check your command syntax. Ensure that any directory
specified exists. Reenter the command issuing the correct syntax.
Input file does not exist
Facility: EDT, EDT Editor
Explanation: The input file is not contained in the specified directory. When
you are creating a new file using the EDT editor, this message is displayed
indicating the creation of a new file.
User Action: No action is necessary if you are creating a file. If you are
editing an existing file, ensure that you have typed the file specification
correctly and reenter the command.
Input file does not have standard text file format
Facility: EDT, EDT Editor
Explanation: You edited a file that does not have standard file attributes (for
example, a file that does not have carriage returns at the ends of lines).
User Action: This message is only a warning. EDT allows you to edit the file,
but be aware that difficulties can arise if you attempt to edit the nonstandard
elements.
Input record too large, truncated to 255 characters
Facility: EDT, EDT Editor
Explanation: A record in the input file exceeds 255 characters.
User Action: Modify the record in the input file to contain 255 characters or
less. This message can also occur due to an attempt to edit a file that does
not contain ASCII text.
INPUTERR,

error opening primary input file SYS$INPUT

Facility: LOGIN, Login Processor
Explanation: An error occurred while trying to open SYS$INPUT. An
accompanying message will provide more information.
User Action: Correct the problem described by the accompanying message,
and try again.

2-226

Messages

INSCLIMEM,

insufficient CLI memory

Facility: LIB, Run-Time Library General Procedures
Explanation: The CLI could not obtain enough virtual memory to perform
the function. This may be caused by having too many symbols defined.
User Action: Delete some symbol definitions. Then retry the operation.
INSCOLL,

not enough collections for summary processing

Facility: MONITOR, Monitor Utility
Explanation: An error occurred during summary processing. For summary
processing to take place, at least two collections must be completed.
User Action: This error may occur if you interrupt (by typing CTRL/C) a
summary request before the second collection has been completed. Reenter
your command and allow at least two collections to be completed.
INSEF,

insufficient event flag

Facility: LIB, Run-Time Library General Procedures
Explanation: A call was made to LIB$GET_EF to allocate an event flag
number, but all event flag numbers were unavailable.
User Action: Use LIB$FREE_-EF to free previously allocated event flag
numbers if they are no longer being used.
INSERTED,

module 'module name' inserted in 'library file-spec'

Facility: LIBRAR, LIBRARY Command
Explanation: This success message is generated by the DCL command
LIBRARY.
User Action: None. This message is informational.
INSERTERR,

error inserting 'module name' in 'library file-spec'

Facility: LIBRAR, LIBRARY Command
Explanation: This error message is generated by the DCL command
LIBRARY. One of the following conditions prevented the DCL command
LIBRARY from inserting the specified modules into the library:
•

The modules are not formatted correctly.

•

The organization of the input file is incorrect.

•

A VAX RMS error has occurred.

•

There was not enough virtual memory.

User Action: Correct the error and insert the file.

2-227

Messages

INSFANL,

insufficient data in Definition and/or Analysis files

Facility: FDL, Edit/FDL Utility
Explanation: EDIT/FDL is executing an optimize script invoked by the
/NOINTERACTIVE qualifier. Certain information about the file is missing
from the definition or the analysis file.
User Action: Supply the missing information by reexecuting the ANALYZE
/RMS—FILE/FDL command to produce another analysis file and/or use the
analysis file as the definition file.
INSFARG,

insufficient call arguments

Facility: SYSTEM, VAX/VMS System Services
Explanation: A system service argument list contained fewer than the
required number of arguments for the service.
User Action: Check for a programming error. Refer to the VAX/VMS System
Services Reference Manual for coding specifications.
INSFBUFDP,

unable to allocate a buffered datapath

Facility: SYSTEM, VAX/VMS System Services
Explanation: This message is associated with a status code returned from a
request to an LPA11-K interface device. A UBA-buffered data path was not
available for allocation.
User Action: Rerun the program.
INSFCDT,

insufficient CDT entries

Facility: SYSTEM, VAX/VMS System Services
Explanation: There are currently insufficient connection descriptor table
entries for completing a request.
User Action: Attempt your request at a later time.
INSFMAPREG,

insufficient map registers

Facility: SYSTEM, VAX/VMS System Services
Explanation: This message is associated with a status code returned from a
request to an LPA11-K interface device to initialize the LPA11-K or start data
transfer. Insufficient UNIBUS adapter (UBA) map registers are available to
map the command table or buffer areas.
User Action: If the map registers were preallocated when the drive was
loaded, increase the preallocation.
INSFMEM,

insufficient dynamic memory

Facility: SYSTEM, VAX/VMS System Services
Explanation: A command or image exhausted the system pool of available
dynamic memory and the system cannot complete the request.
Or, the system manager did not allocate enough dynamic memory.
User Action: Check for a programming error; this status code can be returned
from a system service request when the image has disabled resource wait
mode. Notify the system manager if insufficient memory is allocated.

2-228

Messages

INSFMEM,

insufficient dynamic memory

Facility: SYSGEN, System Generation Utility
Explanation: There is not enough room in the nonpaged pool to load a driver
or create a control block for it.
User Action: Reboot the system, stopping in SYSBOOT, and increase the
value of the parameter NPAGEDYN.
INSFMEM,

insufficient nonpaged memory to run PSI

Facility: PSI, VAX Packetnet System Interface
Explanation: You have tried to start PSIACP without sufficient memory for it
to run.
User Action: Increase the size of the nonpaged pool to 80K bytes at least.
INSFPRM,

missing command parameters - supply all required parameters

Facility: CLI, Command Language Interpreter (DCL)
Explanation: A command cannot be executed because one or more required
parameters are missing from the command. With the DCL command
interpreter, this message occurs only during the execution of command
procedures; at the interactive level, the command interpreter continues to
prompt until all required parameters are entered.
User Action: Correct the command procedure.
INSFRAME,

insufficient call frames to unwind

Facility: SYSTEM, VAX/VMS System Services
Explanation: An unwind request specified a depth that is greater than the
number of call frames on the stack.
User Action: Check for a programming error.
INSFSPTS,

insufficient SPTs to map process buffer to system

Facility: SYSTEM, VAX/VMS System Services
Explanation: There are insufficient system page table entries to map a
process buffer to the system.
User Action: Reboot the system and increase the SYSGEN parameter
SPTREQ.
INSFVM,

unable to obtain virtual memory

Facility: EVL, Event Logger
Explanation: A program or system configuration problem exhausted virtual
memory.
User Action: Check the value of the VIRTUALPAGECNT using SYSGEN. If
the value is 2048 or greater, then this message indicates a program problem.

2-229

INSFWSL,

insufficient working set limit

Facility: SYSTEM, VAX/VMS System Services
Explanation: A command or image cannot execute because the current
working set limit for the process is less than the number of pages that must
be resident in memory at the same time for an image to execute. For example,
a global or private section cannot be mapped if the number of pages to be
mapped exceeds the working set limit.
User Action: Check for a programming error; verify that the number of
pages requested in a system service request is accurate. If the number of
pages is accurate, try to increase the size of the working set limit with the
DCL command SET WORKING-SET and retry the program.
INSKIPPED,

unreasonable instruction stream - n bytes skipped

Facility: SDA, System Dump Analyzer
Explanation: SDA cannot decode a range of memory locations into VAX
MACRO instruction format because the locations do not begin on an
instruction boundary.
User Action: None. SDA ignores the bytes it cannot translate.
INSLUN,

insufficient logical unit numbers

Facility: LIB, Run-Time Library General Procedures
Explanation: A call was made to LIB$GET_LUN to allocate a logical unit
number, but all logical unit numbers were unavailable.
User Action: Use LIB$FREE_LUN to free previously allocated logical unit
numbers if they are no longer used.
INSNFREPAG,

insufficient nonfree pages

missing instruction operand

Facility: PATCH, VAX Image File Patch Utility
Explanation: One or more operands were omitted from the instruction.
User Action: Add the required number of operands and retry the operation.

Messages

INSSWPFIL,

Insufficient swap file space

'nn' bytes requested, patch area at 'addr' contains 'nn' bytes

Facility: PATCH, VAX Image File Patch Utility
Explanation: The user-defined patch area is not large enough to
accommodate the specified code.
User Action: Use an alternate patch area, for example, the default patch area.
Generally, the default patch area is expandable.
INSVIRMEM,

Insufficient virtual memory

Facility: VAX Text Processing Utility
Explanation: An attempt to allocate additional memory for working storage
failed.
User Action: Purge or delete files to free space in memory.
INSVIRMEM,

insufficient virtual memory

Facility: STR, Run-Time Library String Procedures
Explanation: An attempt was made to allocate heap storage for use as
dynamic strings, or string temporaries failed.
User Action: If you allocate space by calling STR$GET1_DX or
LIB$GET_VM, verify, when you finish using the storage, that the storage is
released by calling STR$FREE1_DX or LIB$FREE_VM, respectively. If you
are using a high-level language and have not directly allocated space, you can
cause this error by having a large number of long strings. In this case, make
sure to reduce strings to zero length when they are not in use.

2-231

Messages

INSVIRMEM,

insufficient virtual memory

Facility: SORT, VAX SORT/MERGE Utility
Explanation: SORT was unable to allocate the minimum amount of dynamic
memory required to sort the data. At the program level, this error may be
cause by either the use of dynamic strings by user-written code, or to a sort
of very large records with insufficient quotas.
This error could result when the process exceeds its paging file quota
(PGFLQUOTA), when the process's working set limit (WSQUOTA) is not
large enough to accommodate the increased virtual address space, or when
the process's virtual address space is full.
User Action: Consider changing your sort process to a tag sort. You
may need to adjust appropriate SYSGEN parameters, particularly
VIRTUALPAGECNT. Or you may need to extend the system page and
/or swap files.
INSVIRMEM,

insufficient virtual memory (See also the following messages)

Facility: MACRO, VAX Macro Assembler
Explanation: The module being assembled has too many symbols and macro
definitions for the virtual memory available or a macro definition called itself
(a recursive definition). The assembler terminated the assembly.
User Action: Increase the virtual memory available by contacting the system
manager; reduce the level of macro nesting; split the module into several
smaller modules; or eliminate the recursive macro definition.
INSVIRMEM,

insufficient virtual memory - DIF aborted

Facility: DIFF, DIFFERENCES Command
Explanation: The Differences Utility has run out of virtual memory for one
of the following reasons: (1) the Differences Utility encountered a difference
section that contains more records than can be stored in virtual memory, or
(2) the Differences Utility ran out of virtual memory while storing records
away to be used while generating additional listings.
User Action: In the first case, cut down the size of the offending difference
section; the listing will have terminated in the middle of the section. You can
do this by increasing the value of the /WINDOW parameter if it is not being
defaulted.
In the second case, rerun the Differences Utility and generate one listing at a
time.
INSVIRMEM,

insufficient virtual memory for 'number7 pages for cluster 'clustername'

Facility: LINK, VAX Linker
Explanation: The linker could not allocate enough virtual memory in the
resulting image to contain a cluster.
User Action: Determine why the linker ran out of virtual memory by
consulting a /FULL map, correct, and relink.

2-232

Messages

INSVIRMEM,

PSI exiting due to virtual memory allocation failure

Facility: PSI, VAX Packetnet System Interface
Explanation: PSICACP has insufficient virtual address space.
User Action: Increase the SYSGEN VIRTU ALP AGECNT parameter.
INSWAPERR,

Inswap read error

internal data corrupted in run-time library

Facility: OTS, Language Independent Run-Time Library Support Procedures
Explanation: On a call to the Run-Time Library, a database consistency
check failed. A user program can cause this by referring to a location outside
a dimensioned array, or by requesting input from an address outside the
program.
User Action: Recompile any module that you think may refer outside a
dimensioned array with the /CHECK=BOUNDS qualifier. Relink and rerun
your program.
INTDIV,

arithmetic trap, integer divide by zero at PC = 'xxxxxxxx', PSL =
'xxxxxxxx'

Facility: SYSTEM, VAX/VMS System Services
Explanation: An arithmetic exception condition occurred as a result of an
attempt to divide by zero.
User Action: Examine the PC location displayed in the message and check
the program listing to verify that operands or variables are specified correctly.
INTERLOCK,

unable to acquire system data structure interlock

Facility: SYSTEM, VAX/VMS System Services
Explanation: The system data structure interlock cannot be acquired.
Another processor has probably crashed while holding a data structure
lock.
User Action: Retry the operation, or reboot the system and reinitialize shared
memory. Refer to the VAX/VMS System Manager's Reference Manual.

2-233

Messages

Internal software error - please submit an SPR
Facility: Shared by several facilities
Explanation: You are experiencing a problem with the EDT software as
installed on your system.
User Action: Submit a Software Performance Report.
INTHCHAR,

internal error: encountered character of class h-string

Facility: CDU, Command Definition Utility
Explanation: CDU encountered a corrupted internal data structure.
User Action: Submit an SPR including the CLD file.
INTINVNODE,

internal error: invalid node encountered

Facility: CDU, Command Definition Utility
Explanation: CDU encountered a corrupted internal data structure.
User Action: Submit a Software Performance Report and include the CLD
file in the report.
INTLOGERR,

internal logic error

Facility: LIB, Run-Time Library General Procedures
Explanation: A general library procedure detected an internal logic error.
This message is associated with a status code returned from the Run-Time
Library.
User Action: Submit a Software Performance Report.
INTMEMERR,

internal memory-pool error at location xxx

Facility: DEBUG, VAX/VMS Debugger
Explanation: The debugger's internal memory area has been corrupted or is
inconsistent at the specified location. This can be caused by an internal debug
error or by random stores by the user program.
User Action: Correct the user program or submit a Software Performance
Report.
INTNODESPACE,

internal error: node space exhausted

Facility: CDU, Command Definition Utility
Explanation: CDU exhausted internal memory.
User Action: Submit an SPR including the CLD file.
INTOVF,

arithmetic trap, integer overflow at PC = 'xxxxxxxx', PSL = 'xxxxxxxx'

Facility: SYSTEM, VAX/VMS System Services
Explanation: An exception condition occurred as a result of an integer
overflow.
User Action: Examine the PC location displayed in the message and check
the program listing to verify that operands or variables are specified correctly.

2-234

Messages

INTOVF,

integer overflow

Facility: LIB, Run-Time Library General Procedures
Explanation: Either the library routine or the hardware detected an integer
overflow.
User Action: Choose a destination data type with a larger range.
INTPATHSTKOV,

internal error: path stack overflow

Facility: CDU, Command Definition Utility
Explanation: CDU exhausted internal memory.
User Action: Submit an SPR including the CLD file.
INTRNLERR,

internal error: 'code7

Facility: INSTALL, Install Utility
Explanation: INSTALL encountered an internal error.
User Action: Submit a Software Performance Report.
INTRNLERR,

LBR internal error. Please submit SPR.

Facility: LBR, Librarian Subroutine Package
Explanation: This is an internal consistency check.
User Action: Submit a Software Performance Report that includes relevant
files wherever possible.
INTSTKOV,

Linker internal stack of 'number7 overflowed in module 'modulename7 file 'file-name7

Facility: LINK, VAX Linker
Explanation: The linker's internal stack overflowed because of a complex
calculation.
User Action: Submit a Software Performance Report.
INTSTKUN,

Linker internal stack of 'number7 underflowed in module 'modulename7 file 'file-name7

Facility: LINK, VAX Linker
Explanation: An object module attempted to remove more items from the
stack than it pushed on it.
User Action: Submit a Software Performance Report on the appropriate
language compiler.
INVACC,

invalid access control specified for the executor

Facility: NCP, Network Control Program
Explanation: You specified invalid or conflicting access control information
for connecting to an executor node.
User Action: Use either the standard VAX/VMS access control format (nodespec) or the NCP-specific format (USER, ACCOUNT, PASSWORD), but not
both.

2-235

Messages

INVACCESS,

Invalid file access specified

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

record 'record' has invalid or unrecognized format

Facility: ACCOUNTING, Accounting Utility
Explanation: A record in the accounting file has an invalid or unrecognized
format. The ACCOUNTING Utility will attempt to continue processing
records.
User Action: Examine the accounting file and verify that it is a valid
VMS accounting file. Check for hardware errors. Submit an SPR with
the accounting file in question, if the problem persists.
INVACCTMSG,

invalid PSI accounting control message received

Facility: PSI, VAX Packetnet System Interface
Explanation: An unrecognized or invalid accounting control message was
received in the VAX PSI Accounting control mailbox.
User Action: Use only the supplied utilities to control accounting.
INVADAP,

invalid adapter name specified

Facility: SYSGEN, System Generation Utility
Explanation: The specified adapter number was found to be invalid after
bootstrap.
User Action: Reissue the command using the correct adapter number.
Invalid buffer name
Facility: EDT, EDT Editor
Explanation: Invalid syntax was used for the buffer name in the EDT
command.
User Action: Reenter the EDT command specifying valid syntax for the
buffer name.
Invalid character
Facility: EDT, EDT Editor
Explanation: You attempted to insert a character by using the SPECINS
function or ASC command, but did not supply a valid decimal equivalent for
the character.
User Action: Reenter the command specifying a valid decimal equivalent for
the character.

2-236

Messages

Invalid entity
Facility: EDT, EDT Editor
Explanation: The entity portion of the EDT change mode command is not
recognized.
User Action: Reenter the EDT change mode command specifying a valid
entity.
Invalid option for that command
Facility: EDT, EDT Editor
Explanation: The /OPTION qualifier was specified for an EDT command
that does not accept the /OPTION qualifier.
User Action: Reenter the EDT command without specifying the /OPTION
qualifier.
Invalid parameter for SET or SHOW
Facility: EDT, EDT Editor
Explanation: The EDT commands SET and SHOW do not accept one of the
parameters you specified.
User Action: Reenter the EDT command specifying a valid parameter.
Invalid string
Facility: EDT, EDT Editor
Explanation: You specified a string that EDT could not handle. For example,
this message occurs when you use a search string longer than 64 characters.
User Action: Reenter the command specifying a valid string.
Invalid subcommand
Facility: EDT, EDT Editor
Explanation: You have used an improper name for an EDT change mode
subcommand.
User Action: Use a valid name. For a list of the EDT change mode
subcommands, type HELP CHANGE SUBCOMMANDS in line mode.
Invalid UIC
Facility: DISKQUOTA, Diskquota Utility
Explanation: You specified a UIC using an incorrect format.
User Action: Enter a correctly formatted UIC.
Invalid value in SET command
Facility: EDT, EDT Editor
Explanation: The EDT command SET has an invalid keyword.
User Action: Reenter the command specifying a valid keyword.

2-237

Messages

INVALIGN,

invalid alignment

Facility: MACRO, VAX Macro Assembler
Explanation: An unrecognized keyword or no integer or no keyword
followed the .ALIGN directive.
User Action: Correct the syntax of the .ALIGN directive.
INVALQUAL,

the 'qualifier-name' is an invalid qualifier in this context

Facility: BAD, Bad Block Locator Utility
Explanation: The qualifier indicated was issued in an invalid context.
User Action: Consult the documentation for the list of valid, nonconflicting
qualifier specifications and usage in various analysis contexts.
INVARG,

invalid argument

Facility: DCX, Disk Compression Utility
Explanation: A DCX procedure has been called with an incorrect argument.
User Action: Correct the application program.
INVARG,

invalid argument

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: The value of some argument is not in the correct range.
User Action: Examine each argument. Determine which one is out of range
and correct your program.
INVARG,

invalid argument(s)

Facility: LIB, Run-Time Library General Procedures
Explanation: This message is associated with a status code returned from the
Run-Time Library. A calling program passed one or more invalid arguments
to a general library procedure.
User Action: Verify the arguments for the call to the Run-Time Library and
correct the program.
INVARGMAT,

invalid argument to math library user PC location

Facility: MTH, Run-Time Library Math Procedures
Explanation: One of the math procedures was called with an invalid
argument.
User Action: Locate the math procedure call that caused the error and correct
the argument.

2-238

Messages

INVARRDSC,

invalid array descriptor

Facility: DEBUG, VAX/VMS Debugger
Explanation: An array descriptor in the image does not have the correct
format. This can be caused by a reference to a VAX BASIC array when the
first line of the program has not been executed. The array is not set up
correctly until the BASIC program initialization is done. This message can
also be caused by a user program or DEPOSIT commands altering a compiler
generated array descriptor.
User Action: If the reference is to a VAX BASIC array, enter a STEP or GO
command to ensure that the BASIC program initialization is done and then
repeat the reference. Otherwise, if an array descriptor has not been altered,
submit a Software Performance Report.
INVARRDSC,

invalid array descriptor

Facility: PATCH, VAX Image File Patch Utility
Explanation: The expression contained an array descriptor that PATCH did
not recognize.
User Action: Correct the array descriptor and retry.
INVATTSIZ,

invalid attribute record size in save set

Facility: BACKUP, Backup Utility
Explanation: An incorrect value occurred in the attribute size field of a save
set record. Data in the save set is corrupted.
User Action: None. Save set data has been lost.
INVATTSTR,

invalid attribute record structure level in save set

Facility: BACKUP, Backup Utility
Explanation: An incorrect value occurred in the structure level field of a save
set record. Data in the save set is corrupted.
User Action: None. Save set data has been lost.
INVATTVAL,

invalid attribute record value in save set

Facility: BACKUP, Backup Utility
Explanation: An incorrect value occurred in a save set attribute record. Data
in the save set is corrupted.
User Action: None. Save set data has been lost.
INVBJLEOF,

invalid end of file position in BACKUP journal

Facility: BACKUP, Backup Utility
Explanation: The end-of-file pointer recorded for the journal file specified by
the /JOURNAL qualifier was invalid. The journal file is corrupted and cannot
be used.
User Action: Reconstruct the journal file from backup media.

2-239

Messages

INVBJLSIZ,

invalid record size in BACKUP journal

Facility: BACKUP, Backup Utility
Explanation: An invalid record size occurred in the journal file specified by
the /JOURNAL qualifier. The journal file is corrupted and cannot be used.
User Action: Reconstruct the journal file from backup media.
INVBJLSTR,

invalid structure level in BACKUP journal

Facility: BACKUP, Backup Utility
Explanation: The structure level recorded in the journal file specified by the
/JOURNAL qualifier was invalid. The journal file is corrupted and cannot be
used.
User Action: Reconstruct the journal file from backup media.
INVBJLTYP,

invalid record type in BACKUP journal

Facility: BACKUP, Backup Utility
Explanation: An invalid record type occurred in the journal file specified by
the /JOURNAL qualifier. The journal file is corrupted and cannot be used.
User Action: Reconstruct the journal file from backup media.
INVBKT,

invalid bucket at VBN 'number'

Facility: CONVERT, Convert Utility
Explanation: The Convert/Reclaim Utility has detected a structure error in
the bucket specified by 'number'.
User Action: Use the ANALYZE/RMS—FILE command to determine the
cause of the structure error.
INVBLK,

invalid RMS control block at virtual address nnnn

Facility: FDL, Create/FDL Utility
Explanation: FDL$GENERATE or FDL$RELEASE was passed an address that
is not a legal RMS control block.
User Action: Correct the invalid address.
INVBLK,

invalid RMS control block at virtual address XXXXXXXX

Facility: FDL, Edit/FDL Utility
Explanation: The FDL parsing facility checks the validity of RMS blocks
before deallocating them, and returns this error if a bad control block is
found.
User Action: Ascertain that the RMS control blocks passed to the
FDL$RELEASE routine are in the same state as when they were created
by the FDL$PARSE routine.

2-240

Messages

INVBLKHDR,

invalid block header encountered in save set

Facility: BACKUP, Backup Utility
Explanation: An incorrect value occurred in the block header of a save set
block. Data in the save set is corrupted.
User Action: None. Save set data has been lost.
INVBLKSIZE,

invalid block size in save set

Facility: BACKUP, Backup Utility
Explanation: An incorrect value occurred in the block size field of a save set
block. Data in the save set is corrupted.
User Action: None. Save set data has been lost.
INVBLKTYP,

invalid block type in specified block

Facility: SDA, System Dump Analyzer
Explanation: SDA is unable to identify the block type of a particular block.
The invalid block type message usually occurs when the SDA command
FORMAT tries to identify a block type using a byte offset.
User Action: None.
INVBLOCK,

invalid operation on queue block n

Facility: JBC, Job Controller
Explanation: This message indicates a logic error in the job controller.
User Action: None.
INVBTIMSP,

invalid /BEGINNING time specification

Facility: MONITOR, Monitor Utility
Explanation: The value of the /BEGINNING qualifier was specified
incorrectly. You must specify the time as an absolute time, plus or minus
a delta time. You can omit either the absolute or the delta time; however, the
delta time must always be preceded by the plus or minus sign. Whenever
you use a plus sign, enclose the entire time specification in double quotes.
See the VAX/VMS DCL Dictionary for more information on specifying time
values.
User Action: Reissue the MONITOR request with a correct value for the
/BEGINNING qualifier.
INVBUFDELETE,

Cannot delete a permanent buffer

Facility: VAX Text Processing Utility
Explanation: You attempted to delete a buffer that has been set as a
permanent buffer.
User Action: None.

2-241

Messages

INVCHA,

invalid character

Facility: LIB, Run-Time Library General Procedures
Explanation: A character was unable to be translated when converting either
from ASCII to EBCDIC or from EBCDIC to ASCII.
User Action: Ensure that translatable characters are used.
INVCHAN,

Invalid ACP channel number

'name' is an invalid characteristic name

Facility: QUEMAN, Queue Manager
Explanation: The specified characteristic name is syntactically invalid.
User Action: Correct the error and reenter the command.
INVCHANAM,

invalid characteristic name

Facility: JBC, Job Controller
Explanation: The characteristic name specified is not syntactically valid.
After logical name translation, the characteristic name must be a character
string in the range of 1 to 31 characters. The character string must consist of
alphanumeric characters, dollar signs, or underscore (_) characters.
User Action: Correctly specify the characteristic name.
INVCHANUM,

'name' is an invalid characteristic number

Facility: QUEMAN, Queue Manager
Explanation: The specified characteristic number is syntactically invalid.
User Action: Correct the error and reenter the command.
INVCHAR,

invalid character

Facility: PATCH, VAX Image File Patch Utility and DEBUG, VAX/VMS
Debugger
Explanation: The command contained an invalid character.
User Action: Correct the character and reenter the command.

2-242

Messages

INVCHAR,

invalid character encountered in position 'position7. It is ignored

Facility: CDU, Command Definition Utility
Explanation: CDU encountered an illegal character while reading from a
CLD file. The illegal character was ignored.
User Action: Edit the CLD file such that there are no illegal characters.
INVCHDABS,

invalid command in /ABSOLUTE context

Facility: PATCH, VAX Image File Patch Utility
Explanation: The command entered is invalid when patching a file in
absolute context. Use of symbol names, patch area, or ECOs is invalid
when invoking PATCH with the /ABSOLUTE qualifier.
User Action: Enter a valid command. If you are patching an image, invoke
the Patch Utility without the /ABSOLUTE qualifier.
INVCJFIOD,

Invalid IO database structure (journaling)

invalid class in descriptor

Facility: LIB, Run-Time Library General Procedures
Explanation: An unsupported class of descriptor was specified.
User Action: Retry the operation specifying a supported class of descriptor.
INVCLADTY,

invalid class data type combination in descriptor

Facility: LIB, Run-Time Library General Procedures
Explanation: An unsupported class and data type combination was specified.
User Action: Ensure that both the class and data type specified are
supported.
INVCLIFLAG,

invalid CLI flag 'flag-name' encountered

Facility: CDU, Command Definition Utility
Explanation: CDU encountered an invalid CLI flag name while reading from
a .CLD file.
User Action: Edit the CLD file so that all CLI flag names are valid.

2-243

Messages

INVCLSNM,

class-name 'class-name' is invalid or not uniquely identified

Facility: MONITOR, Monitor Utility
Explanation: The specified class name is not a valid MONITOR class. This
message can result from specifying a class name with too few characters to
uniquely identify it.
User Action: Check the list of valid MONITOR classes by issuing the DCL
command, HELP MONITOR parameters. Reissue the MONITOR command
requesting only valid classes.
INVCMD,

invalid command

Facility: PATCH, VAX Image File Patch Utility
Explanation: You issued a command and either omitted or incorrectly
entered required punctuation.
User Action: Reenter the corrected command.
INVCMD,

unrecognized command

Facility: NCP, Network Control Program
Explanation: The command verb specified is invalid.
User Action: Reenter the command with the correct verb.
INVCMD,

unrecognized command 'command'

Facility: MAIL, Personal Mail Utility
Explanation: You entered an invalid MAIL command.
User Action: Retry using a valid MAIL command.
INVCOD,

invalid line device code received

Facility: NCP, Network Control Program
Explanation: This message indicates a NICE protocol incompatibility.
User Action: None.
INVCOL,

invalid column

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: An invalid column number was specified. It was either less
than 0 or larger than the number of columns in the virtual display.
User Action: Specify a valid column. Columns are numbered beginning with
1.
INVCOLARG,

unknown color specified

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: An attempt was made to change the characteristics of the
terminal, changing its background color to a value that is not legal.
User Action: Check the symbolic name for the background color desired.
Specify it correctly.

2—244

Messages

INVCONT,

invalid line continuation

Facility: INPSMB, Input Symbiont
Explanation: In a batch job entered from a card reader, a continued line is
followed by a line beginning with a dollar sign.
User Action: Correct the error and reenter the job.
INVCTX,

invalid context block

Facility: DCX, Disk Compression Utility
Explanation: A DCX procedure has been called with a context variable that
is invalid or with an invalid or corrupted context area. This problem may
be caused by failure to call the appropriate routine to initialize the context
variable or by an application program error.
User Action: Correct the application program.
INVCVT,

invalid conversion

Facility: LIB, Run-Time Library General Procedures
Explanation: The source value is negative and the destination data type is
unsigned.
User Action: Ensure that the source value is positive and the destination data
type is signed.
INVDATA,

invalid data presented for expansion or bounded compression

Facility: DCX, Disk Compression Utility
Explanation: Two possible causes exist:
•

DCX$COMPRESS_DATA was called to compress a data record that was
not presented to DCX$ANALYZE _DATA when a bounded compression
function had been requested.

•

DCX$EXPAND—DATA was called to expand a compressed data record
that was truncated or corrupted in some fashion.

User Action: Correct the application program.
INVDATIM,

invalid date/time in statement 'number7

Facility: FDL, Create/FDL Utility
Explanation: An invalid date/time was included in the specified statement.
User Action: Correct the invalid date/time in the specified statement in the
FDL file.
INVDATIM,

invalid date/time in statement XXX

Facility: FDL, Edit/FDL Utility
Explanation: The date and/or time specified to the FDL parser was
incorrectly formed.
User Action: Ascertain that the syntax of the date/time is correct. The legal
format is that of the SYS$BINTIM system service.

2-245

INVDBK,

improper dialogue message received

Facility: NCP, Network Control Program
Explanation: This program indicates a NICE protocol incompatibility.
User Action: None.
INVDEFATT,

invalid key-definition attributes

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: When a key is defined, attributes such as NOECHO may be
specified with the definition. An attempt was made to specify an unknown
attribute.
User Action: Check the list of valid attributes and correct your program.
INVDEFINE,

invalid DEFINE statement

Facility: CDU, Command Definition Utility
Explanation: CDU encountered an invalid DEFINE statement in a CLD file.
Valid keywords for the DEFINE statement are: VERB, SYNTAX, and TYPE.
User Action: Edit the CLD file so that the DEFINE commands contain proper
syntax.
INVDEV,

device is invalid for requested operation

Facility: SET, SET Facility
Explanation: The device type that is specified for the operation is not allowed
in the particular operation. For example, the user issues the command SET
DEVICE/SERVED CSA1 to serve the console floppy which is not allowed.
User Action: Make sure that the device meets all of the requirements for the
operation.
INVDEV,

device name too long to add trailing

Facility: AUTHORIZE, Authorize Utility
Explanation: You specified a device name with more than 15 characters.
User Action: Limit the device name to 15 characters.
INVDEVICE,

invalid device 'device-spec'

Facility: VERIFY, Verify Utility
Explanation: An invalid device was specified in the command.
User Action: Reenter the command specifying a valid device. The
specification must reference a disk device and must not contain any file
specification components other than a device name.
INVDEVICE,

invalid or unsupported device 'device-name'

Facility: ERF, ANALYZE/Error Log Utility
Explanation: An invalid or unsupported device name was specified.
User Action: Use the DCL HELP command or refer to the VAX/VMS DCL
Dictionary, if necessary, for the valid keywords and reenter the command.

Messages

INVDEVTYP,

invalid backup device type 'file-spec'

Facility: BACKUP, Backup Utility
Explanation: The specified device must be a disk or tape device.
User Action: Reenter the command.
INVDIR,

invalid directive

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: The Termtable compiler accepts only a few FAO directives. It
encountered one that it does not process.
User Action: Check your terminal definition. Make sure that you use only
valid FAO directives.
INVDIRNAM,

invalid directory name 'xxx'

Facility: DEBUG, VAX/VMS Debugger
Explanation: The directory name 'xxx' given in a DEBUG command SET
SOURCE is not valid. Either the directory syntax is incorrect or the directory
does not exist.
User Action: Ensure that the directory exists and that the syntax is correct.
INVDIS—ID,

invalid display-id

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: An invalid display id was specified.
User Action: Make sure you are passing the display id by reference, not
by value. Ensure that the display id was previously set up by a call to
SMG$CRE ATE-VIRTUAL -DISPLAY.
INVDPT,

invalid driver image - DPT$_TYPE, VBN 2 .NEQ. DYN$C_DPT

Facility: SYSGEN, System Generation Utility
Explanation: The driver image file specified in a SYSGEN command LOAD,
RELOAD, or CONNECT did not pass a basic validity check. This error can
be caused by one of the following conditions:
•

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

•

Not linking the driver as an executable image based at zero

•

Having PSECT statements in the driver program

•

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

User Action: Correct the driver code and reissue the command.

2-247

Messages

INVDPTINI,

invalid driver prologue init table value

Facility: SYSGEN, System Generation Utility
Explanation: One of the following conditions exists:
•

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

•

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

User Action: Correct the DPT—STORE macro in the driver prologue table.
INVDSTQUE,

invalid destination queue

Facility: JBC, Job Controller
Explanation: The destination queue name specified is not syntactically
valid. After logical name translation, the destination queue name must be
a character string in the range of 1 to 31 characters. The character string
must consist of alphanumeric characters, dollar signs, and underscore (_)
characters.
User Action: Correctly specify the destination queue.
INVDSTREC,

invalid DST record

Facility: PATCH, VAX Image File Patch Utility and DEBUG, VAX/VMS
Debugger
Explanation: An invalid Debug Symbol Table record was encountered. This
can be caused by a DEPOSIT to a random location or it may be a compiler
error.
User Action: Submit a Software Performance Report unless the user program
or a DEPOSIT command has altered a Debug Symbol Table record.
INVDSTREC,

unimplemented delta-PC command in symbol table

Facility: TRACE, Traceback
Explanation: A language processor has created a PC-to-line-number record
that the traceback facility has not implemented. The symbol table information
is either incorrect or is not known to the traceback facility.
User Action: Submit a Software Performance Report.
INVDTYDSC,

invalid data type in descriptor

Facility: LIB, Run-Time Library General Procedures
Explanation: An unsupported data type was specified.
User Action: Retry the operation specifying a supported data type.

2-248

Messages

INVETIMSP,

invalid /ENDING time specification

Facility: MONITOR, Monitor Utility
Explanation: The value of the /ENDING qualifier was specified incorrectly.
You must specify the time as an absolute time plus or minus a delta time.
You can omit either the absolute or the delta time; however, the delta time
must always be preceded by the plus or minus sign. Whenever you use a
plus sign, enclose the entire time specification in double quotes. See the
VAX/VMS DCL Dictionary for more information on specifying time values.
User Action: Reissue the MONITOR request with a correct value for the
/ENDING qualifier.
INVEVE,

invalid event range

Facility: NCP, Network Control Program
Explanation: The range of event types is invalid.
User Action: Reenter the valid event list.
INVEXCEPTN,

Exception while above ASTDEL or on interrupt stack

termination handler control block list is corrupted

Facility: SYSTEM, VAX/VMS System Services
Explanation: The list of exit handler control blocks is in an inconsistent state,
either because the same exit handler was declared more than once or because
user code has minpulated one of the list pointers.
User Action: The program is in error. Change the source code that is
incorrectly manipulating the termination handler control block list.
INVEXP,

invalid expression

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: The Termtable compiler encountered an invalid arithmetic
expression.
User Action: Check your definition. Make sure that you have used only
valid operators and operands in your expressions.

2-249

INVEXTBACK,

file ('file-id') 'file-name' invalid extension file header back link

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility has found that the back link in an extension
file header for the specified file does not point to the primary file header.
User Action: None. The back link is changed to point to the primary file
header.
INVEXTFID,

file ('file-id') 'file-name' invalid extension file header forward link

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility has found that the forward link in a file
header to the next extension file header does not point to a valid file header.
User Action: None. The link is cleared. Part of the file cannot be accessed
by the operating system.
INVEXTHDR,

file ('file-id') 'file-name' invalid extension file header sequence

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility has found that the sequence numbers in
the extension file headers for the specified file are not correct. The sequence
number should increase by one in each extension file header.
User Action: None. The link that points to the erroneous extension file
header is cleared. Part of the file cannot be accessed by the operating system.
INVFAOPARAM,

Parameter 'integer' must be string or integer

Facility: VAX Text Processing Utility
Explanation: The FAO built-in procedure allows only string and integer
arguments.
User Action: Specify string and integer arguments only to the FAO built-in
procedure.
INVFCBDESC,

Descriptor in $FCB for 'address' improperly initialized

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

invalid file id in save set - cannot restore /IMAGE

Facility: BACKUP, Backup Utility
Explanation: An attempt was made to restore a file with a zero file
identification in /IMAGE mode. This may occur if the save set was written
by a non-VAX/VMS system.
User Action: Use a non-/IMAGE mode to restore the file.

Messages

INVFILEXT,

invalid file extension linkage in 'file-spec'

Facility: BACKUP, Backup Utility
Explanation: The specified save set file has an invalid pointer to a following
segment of the file. The remainder of the file is not accessible.
User Action: Attempt to recover data by beginning a restore operation with
the first unprocessed file segment.
INVFILSPE,

input or output file specification too long - shorten

Facility: CLI, Command Language Interpreter (DCL)
Explanation: A file specification was invalid.
User Action: Reenter the command, specifying a valid file specification.
INVFILSPE,

invalid file specification

Facility: LIB, Run-Time Library General Procedures
Explanation: An invalid file specification was specified in a CREATE
/DIRECTORY, SET PROTECTION, RENAME, or UNLOCK command.
User Action: Refer to the VAX/VMS DCL Dictionary and reenter the
command.
INVFILSPE,

invalid file specification 'file-spec'

Facility: PRINT, Print Command and SUBMIT, SUBMIT Command
Explanation: The specified file specification was invalid. Files to be
submitted to a batch or print job must be disk files, and may contain a
node name if and only if the /REMOTE qualifier is specified.
User Action: Correct the error and reenter the command.
INVFLUSHSP,

invalid /FLUSH—INTERVAL specification

Facility: MONITOR, Monitor Utility
Explanation: The value of /FLUSH—INTERVAL must be an unsigned
contiguous string of decimal digits forming a value in the range of 1 to
9,999,999, inclusive.
User Action: Reissue the MONITOR request and specify a valid value for
/FLUSH-INTERVAL.
INVFORNAM,

'name' is an invalid form name

Facility: QUEMAN, Queue Manager
Explanation: The specified form name is syntactically invalid.
User Action: Correct the error and reenter the command.

2-251

INVFORNAM,

invalid form name

Facility: JBC, Job Controller
Explanation: The form name specified is not syntactically valid. After logical
name translation, the form name must be a character string whose length
is in the range of 1 to 31 characters. The character string must consist of
alphanumeric characters, dollar signs, and underscore (_) characters.
User Action: Correctly specify the form name.
INVFORNUM,

n is an invalid form number

Facility: QUEMAN, Queue Manager
Explanation: The specified form number is syntactically invalid.
User Action: Correct the error and reenter the command.
INVFUNCOD,

invalid function code

Facility: JBC, Job Controller
Explanation: The $SNDACC, $SNDSMB, or $SNDJBC function code is
invalid.
User Action: Identify and correct the incorrect fuction code.
INVHOMBLK,

'device7 has invalid home block

Facility: BACKUP, Backup Utility
Explanation: The specified volume has an invalid Files-11 home block.
User Action: Repair the volume with the Verify Utility.
INVIMGHDR,

inconsistent debug and symbol data in image header

Facility: PATCH, VAX Image File Patch Utility
Explanation: The image header inconsistently describes the symbol
information causing the absence of symbol information at PATCH time.
User Action: Relink the image. If the problem persists, submit a Software
Performance Report.
INVINPFIL,

/INPUT file is not a valid MONITOR recording file

Facility: MONITOR, Monitor Utility
Explanation: The file specified with the /INPUT qualifier is not a MONITOR
recording file. When MONITOR creates a recording file, identification
information is stored in the header record; this information is then verified
when the file is used for input. The file specified on this MONITOR request
failed the verification.
User Action: Reissue the MONITOR request, specifying a valid MONITOR
recording file for /INPUT.
INVINPUT,

invalid input format in file 'file-name'

Facility: DSRTOC, DIGITAL Standard Runoff Table of Contents Utility
Explanation: The format of the input file is incorrect.
User Action: Correct the format of the input file.

Messages

INVINTSP,

invalid /INTERVAL specification

Facility: MONITOR, Monitor Utility
Explanation: The /INTERVAL qualifier value must be an unsigned
contiguous string of decimal digits forming a value in the range of 1 to
9,999,999 inclusive.
User Action: Reissue the MONITOR request, specifying a valid /INTERVAL
qualifier value.
INVIOCODE,

Invalid operation code passed to TPU$FILEIO

Facility: VAX Text Processing Utility
Explanation: An invalid request was passed to the file operation routine
provided by VAXTPU. This should only happen if you are using the callable
interface and referencing the TPU$FILEIO routine.
User Action: If you are using the callable interface, correct your program.
If you are not using the callable interface, a software error has occurred. In
such a case, please submit a Software Performance Report describing the
conditions that lead to the error.
INVITEM,

invalid item 'item-name' encountered. Some text will be skipped

Facility: CDU, Command Definition Utility
Explanation: CDU encountered an unexpected item while reading from a
CLD file. The unexpected item was ignored.
User Action: Make sure that all commands in the CLD file contain correct
syntax.
INVITEM,

invalid item code or list

Facility: DCX, Disk Compression Utility
Explanation: DCX$ANALYZE_INIT was called with either an incorrect
number of arguments (the number must be odd) or an unknown item code
argument.
User Action: Correct the application program.
INVITEMCODE,

Invalid item code specified in list

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

/ITEM name 'item-name' is invalid or not uniquely identified

Facility: MONITOR, Monitor Utility
Explanation: The specified item name is not defined for the class with which
it is specified. This message can result from specifying an item name with too
few characters to uniquely identify it.
User Action: Check the list of items defined for the requested class by
issuing: HELP MONITOR /ITEM. Reissue the MONITOR command
requesting only valid items.

2-253

Messages

INVITMCOD,

invalid item code, item code = 'item code (hex)'

Facility: PSM, Print Symbiont
Explanation: An invalid item code was detected.
User Action: Specify a valid item code.
INVITMCOD,

invalid item code or option code

Facility: JBC, Job Controller
Explanation: The $SNDJBC item list contains an invalid item code, or the
SSNDSMB or $SNDACC option list contains an invalid option code.
User Action: Correct the invalid item code or option code.
INVKBD—ID,

invalid keyboard-id

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: An invalid keyboard id was passed.
User Action: Make sure you are passing the keyboard id by reference not
by value. Ensure that the keyboard id was previously set up by a call to
SMG$CRE ATE-VIRTUAL -KEYBOARD.
INVKEY,

invalid key

Facility: LBR, Librarian Subroutine Package
Explanation: This error message is generated by the Librarian routines.
The specified key is either of zero length or it is greater than the maximum
allowable length.
User Action: Either change the module name or change the name length
limit of the library.
INVKEY,

unrecognized keyword

Facility: NCP, Network Control Program
Explanation: NCP could not recognize a keyword in the command string.
This error is returned from a prompt.
User Action: Reenter the requested information.
INVKEYCHAR,

key not inserted; 'ASCII-character' (%X'hexadecimal-byte') is not
a valid key character

Facility: LIBRAR, LIBRARY Command
Explanation: The flagged character is not permitted in a HELP key. If the
HELP key is a level one key (topic), the module will not be inserted into the
HELP library.
User Action: Edit the module in the HELP file to remove the invalid
character from the key.

2-254

Messages

INVKEYNAM,

invalid key name

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: The specified key name was less than 1 character or more than
31 characters.
User Action: Choose a key name with 1 to 31 characters.
INVKEYWRD,

invalid keyword 'string'

Facility: ERF, ANALYZE/Error Log Utility
Explanation: An invalid keyword was specified for a qualifier value.
User Action: Use the DCL HELP command or refer to the VAX/VMS DCL
Dictionary, if necessary, for the valid keywords and reenter the command.
INVKTB_ID,

invalid key-table-id

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: An invalid key table id was passed.
User Action: Make sure you are passing the key table id by reference not
by value. Ensure that the key table id was previously set up by a call to
SMGSCRE ATE _KE Y—TABLE.
INVLDRESP,

invalid operator response

Facility: MOUNT, MOUNT Command
Explanation: The operator responded to a request with an invalid reply.
User Action: None. The request is automatically reissued.
INVLID,

improper line-id received from nice object

Facility: NCP, Network Control Program
Explanation: This message indicates an incompatible NICE object at target.
User Action: None.
INVLOCKID,

Invalid lock id

2-255

INVLOGFIL,

invalid log file specification

Facility: CLI, Command Language Interpreter (DCL)
Explanation: In a SUBMIT command, the log file specification was invalid.
This message is issued with an accompanying message providing more
information.
User Action: Refer to the VAX/VMS DCL Dictionary and reenter the
command specifying a valid file specification.
INVLOGFIL,

invalid log file specification

Facility: INPSMB, Input Symbiont, QUEMAN, Queue Manager, SUBMIT,
SUBMIT Command
Explanation: The specified log file specification is syntactically invalid. The
accompanying message provides additional information.
User Action: Take corrective action based on the accompanying message.
INVLOGFIL,

invalid log file specification

Facility: Shared by several facilities
Explanation: The batch log file specification supplied with the /LOG—FILE
qualifier is invalid. The file specification must reference a disk file and must
not contain a node name or wildcards.
User Action: Respecify the batch log file specification using the correct
syntax.
INVLOGIN,

Facility: SYSTEM, VAX/VMS System Services
Explanation: An attempt was made to initiate a DECnet logical link
connection.
User Action: The access control string specified was incorrect. If default
access control was used, notify the system manager that the DECnet
configuration database needs to be updated.
This error can be returned if the specified access control string was not
recognized (for example, no record in the UAF), or was too long, or contained
illegal characters.
INVMAP,

invalid map

Facility: DCX, Disk Compression Utility
Explanation: A DCX procedure was called with an incorrectly formed map
argument or with an invalid context area.
User Action: Correct the application program.
INVMAR,

right margin must be greater than left

Facility: DEBUG, VAX/VMS Debugger
Explanation: You specified a right margin that was less than the left margin
in the DEBUG command SET MARGIN. The right margin must be greater
than the left margin.
User Action: Reenter the command specifying a valid margin range.

Messages

INVMAXLEN,

invalid maximum length (greater than 512)

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: The maximum length specified for an input string was too long.
User Action: Correct your program so that it requests an input string of 512
characters or less.
INVMSG,

invalid mailbox message received

Facility: JBC, Job Controller
Explanation: The job controller received an invalid mailbox message. This
message indicates a logic error in the system or in the job controller interface
of a user-written symbiont.
User Action: Identify the cause of the problem.
INVMSGBUF,

invalid message buffer

Facility: JBC, Job Controller
Explanation: The $SNDSMB or $SNDACC message buffer is invalid because
it is not long enough to contain all required fields or an option extends
beyond the end of the message buffer.
User Action: Correct the message buffer format and retry the system service
call.
INVNAM,

invalid NAM block

Facility: LBR, Librarian Subroutine Package
Explanation: This error message is generated by the Librarian routines. The
NAM block passed to LBR$INI-CONTROL is illegal.
User Action: Correct the NAM block before calling the routine.
INVNBDS,

invalid Numeric Byte Data String

Facility: LIB, Run-Time Library General Procedures
Explanation: The string of bytes specified as NBDS is not NBDS. Numeric
Byte Data Strings are explained in LIB$CVT_DX_DX routine documentation.
User Action: Check the NBDS descriptor against LIB$CVT—DX_DX
documentation.
INVNUMBER,

invalid numeric string

Facility: PATCH, VAX Image File Patch Utility, DEBUG, VAX/VMS
Debugger
Explanation: You specified a numeric data string that is illegal in the current
context.
User Action: Specify the value in another numeric format or set the language
to one that accepts this type of numeric string.

2-257

INVNUMBER,

invalid numeric string

invalid number of source files

Facility: DEBUG, VAX/VMS Debugger
Explanation: An invalid number of source files was specified on the DEBUGs
command SET MAC_SOURCE—FILES. The maximum number of source files
that DEBUG will keep open simultaneously must be in the range of 1 through

20.
User Action: Reenter the command specifying a valid number within the
range.
INVOPCODE,

Opcode in delayed work queue is invalid

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

unrecognized operator in expression

Facility: PATCH, VAX Image File Patch Utility and DEBUG, VAX/VMS
Debugger
Explanation: The expression contained a character in place of a valid
operator that PATCH or DEBUG does not recognize.
User Action: Reenter the command with a valid expression.
INVOPRND,

unable to resolve operand 'xx'

Facility: PATCH, VAX Image File Patch Utility
Explanation: You specified an operand that PATCH does not recognize.
Operands such as 4(R0) must be preceded by B~, for example, B/'4(R0).
User Action: Retry the operation specifying a legal operand.
INVOPTION,

non-supported flow control parameter received

Facility: NET, DECnet Test Program Protocol
Explanation: This message indicates a DECnet test program protocol
incompatibility.
User Action: Run with a compatible version of DTRECV or equivalent.

Messages

INVPAGARG,

height of 0 is not permitted

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: An attempt was made to change the characteristics of the
terminal, setting the height (page size) to 0.
User Action: Correct the code. A height of 0 is illegal.
INVPARAM,

Parameter 'count7 at line 'count' illegal, expected 'type' actual 'type'

Facility: VAX Text Processing Utility
Explanation: A built-in procedure was invoked with an invalid data type as
one of its parameters.
User Action: Specify a valid data type.
INVPARFIL,

invalid parameter file

Facility: SYSGEN, System Generation Utility
Explanation: An error occurred accessing the file specified in a USE or
WRITE operation.
User Action: Check that the file is not protected against read or write access
and then reissue your command. If the error reoccurs, but the file can be read
or written by other utilities, submit a Software Performance Report (SPR).
Include a copy of the invalid parameter file with the SPR.
INVPARLEN,

invalid parameter length

Facility: JBC, Job Controller
Explanation: The buffer length specified for a $SNDJBC item, or the length
of a string specified with a $SNDSMB option, is outside the valid range for
that item.
User Action: Specify a valid buffer length and retry the system service call.
INVPARM,

parameter identifiers must be in the form Pn

Facility: CDU, Command Definition Utility
Explanation: CDU encountered a parameter definition in which the
parameter being defined was not in the form Pn. All parameters must be
in the form Pn.
User Action: Edit the CLD file so that all defined parameters are in the form
Pn.
INVPARVAL,

invalid parameter value

Facility: JBC, Job Controller
Explanation: The parameter value specified for a $SNDJBC item, or a
$SNDACC or $SNDSMB option, is outside the valid range for that item.
User Action: Specify a valid value for the specified item and retry the system
service call.

2—259

Messages

INVPAS—ID,

invalid pasteboard-id

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: An invalid pasteboard id was specified.
User Action: Make sure that you are passing the pasteboard id by reference
not by value. A reference to a 0 is valid, since 0 is a legal pasteboard id.
Make sure the pasteboard was previously set up by a call to SMG$CREATE__
PASTEBOARD and that the pasteboard has not been deleted.
INVPASS,

invalid password 'password7

Facility: INPSMB, Input Symbiont
Explanation: The specified password is syntactically invalid.
User Action: Correct the error and reenter the job.
INVPATH,

invalid pathname started by 'string'

Facility: PATCH, VAX Image File Patch Utility
Explanation: This message indicates an incorrect use of pathname rules.
User Action: Correct the pathname according to pathname rules and retry.
INVPLACE,

placement must be GLOBAL, LOCAL, or POSITIONAL

Facility: CDU, Command Definition Utility
Explanation: An invalid keyword value was specified for the PLACEMENT
qualifier. Valid keyword values for the PLACEMENT qualifier are GLOBAL,
LOCAL, and POSITIONAL.
User Action: Edit the CLD file so that each PLACEMENT keyword value is
one of the following: GLOBAL, LOCAL, or POSITIONAL.
INVPRVNAM,

'privilege' is not a valid privilege

Facility: INSTALL, Install Utility
Explanation: An invalid privilege name was specified.
User Action: Correct the privilege name and reenter the command.
INVPTEFMT,

Invalid page table entry format

2-260

Messages

INVPWDLEN,

invalid password length - password not changed

Facility: SET, SET Facility
Explanation: A password was specified that was outside the range
established for valid passwords.
User Action: Make sure the password is the correct length and, if necessary,
change the password and reenter the command.
INVQUAVAL,

value 'nn' invalid for /'qualifier' qualifier

Facility: BACKUP, Backup Utility
Explanation: The specified value is not valid for the specified qualifier.
User Action: Check the range of valid values for the qualifier and reenter the
command.
INVQUENAM,

invalid queue name

Facility: JBC, Job Controller
Explanation: The queue name specified is not syntactically valid. After
logical name translation, the queue name must be a character string whose
length must be in the range of 1 to 31 characters. The character string
must consist of alphanumeric characters, dollar signs, and underscore (_)
characters.
User Action: Specify a syntactically valid queue name.
INVQUO,

quoted argument not allowed in current mode

Facility: PATCH, VAX Image File Patch Utility
Explanation: You attempted to enter an argument enclosed in quotation
marks or apostrophes when you were not in INSTRUCTION or ASCII mode.
User Action: Remove the quotation marks or apostrophes and retry the
operation. Or if you are entering instructions or ASCII data, indicate this in
the command.
INVRANGE,

field specification is out of bounds - check sign and size

Facility: CLI, Command Language Interpreter (DCL)
Explanation: The offset and/or length arguments specify a location that is
out of the valid range of this operation.
User Action: Check the offset and length; also check the size of the item on
which you are operating.

2-261

INVRECFMT,

record format specified inconsistent with volume format

Facility: EXCHANGE, Exchange Utility
Explanation: The EXCHANGE utility found that the format option on the
/RECORD_FORMAT qualifier was not valid for the volume against which it
was applied.
User Action: It is very seldom necessary to use a /RECORD-FORMAT
qualifier, since the defaults taken by EXCHANGE are usually correct. If it
is necessary to use a /RECORD-FORMAT qualifier, make sure it is on the
correction file specification. It is possible to put /RECORD-FORMAT on
either input or output specifications (or even on both), depending on the
command.
INVRECORD,

invalid record type in file ,file-name,

Facility: DSRTOC, DIGITAL Standard Runoff Table of Contents Utility
Explanation: An invalid record type was encountered in the file.
User Action: Make sure that the file contains the correct record type.
INVRECSIZ,

invalid record size in save set

Facility: BACKUP, Backup Utility
Explanation: An incorrect value occurred in the record size field (BRH$W_
RSIZE) of a save set record. Data in the save set is corrupted.
User Action: None. Save set data has been lost.
INVRECTYP,

invalid record type in save set

Facility: BACKUP, Backup Utility
Explanation: An incorrect value occurred in the record type field of a save
set record. Data in the save set is corrupted.
User Action: None. Save set data has been lost.
INVREPTYP,

invalid report type

Facility: ERF, ANALYZE/Error Log Utility
Explanation: A bad report type was specified.
User Action: Use the DCL HELP command or refer to the VAX/VMS DCL
Dictionary, if necessary, for the valid report types and reenter the command.
INVREQCOD,

not a valid request code

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: Data is requested from Termtable through request codes that
are available as symbolic names. The code you have specified is invalid.
User Action: Check the spelling of the symbolic name you are using.

Messages

INVREQPARM,

line 'line-number7: All required parameters must precede optional
ones

Facility: CDU, Command Definition Utility
Explanation: CDU encountered a REQUIRED parameter specification after an
OPTIONAL parameter was specified. All REQUIRED parameter specifications
must precede OPTIONAL parameter specifications.
INVREQTYP,

invalid request type

Facility: CLI, Command Language Interpreter (DCL)
Explanation: This message is associated with an internal status code returned
from the command interpreter result parse routine; it indicates a request to
perform an unimplemented function.
User Action: Submit a Software Performance Report.
INVRFA,

invalid RFA

Facility: LBR, Librarian Subroutine Package
Explanation: This error message is generated by the Librarian routines. The
specified RFA is invalid.
User Action: Correct the RFA before calling the routine.
INVRFM,

invalid record format for record I/O - file not opened

Facility: CLI, Command Language Interpreter (DCL)
Explanation: This message is returned by the DCL command OPEN if the
file you are trying to open has a record format that is incompatible with
record I/O.
User Action: You cannot use DCL to read or write to this file.
INVROUT,

invalid routine specified in command tables - check .CLD file

Facility: CLI, Command Language Interpreter (DCL)
Explanation: A user-defined command attempted to invoke a routine that
DCL could not find.
User Action: Correct the command definition file.
INVROUT,

line 'line-number': A ROUTINE clause is only valid when generating
an object file

Facility: CDU, Command Definition Utility
Explanation: CDU encountered a ROUTINE clause while not generating an
object file. The ROUTINE clause is only valid when object file generation is
requested.
User Action: Edit the CLD file to remove the ROUTINE clause or specify the
/OBJECT qualifier in the SET COMMAND.

2-263

Messages

INVROW,

invalid row

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: An invalid row number was specified. It was either less than 0
or larger than the number of rows in the virtual display.
User Action: Specify a valid row number. Rows are numbered beginning
with 1.
INVRSP,

invalid management response

Facility: NCP, Network Control Program
Explanation: Either NCP could not recognize the form of the response from
the network management listener (NML) or the response was inappropriate.
User Action: Submit a Software Performance Report.
INVRSP,

invalid response

Facility: AUTHORIZE, Authorize Utility
Explanation: Your response is invalid.
User Action: Respond to the "Do you..." message that follows this message.
INVRSPID,

RSPID not valid

invalid screen position

Facility: LIB, Run-Time Library General Procedures
Explanation: Zero was specified for either the line number or the column
number.
User Action: Do not specify zero for either the line number or the column
number.
INVSRCLIN,

invalid source line range

Facility: DEBUG, VAX/VMS Debugger
Explanation: An invalid source line range was entered in the DEBUG
command TYPE. The first line number of the range must be nonnegative
and less than or equal to the second number in the range.
User Action: Reenter the command specifying a valid line number range.

2-264

Messages

INVSTA,

invalid state received from NICE object

Facility: NCP, Network Control Program
Explanation: This message indicates a NICE protocol incompatibility.
User Action: None.
INVSTANAM,

invalid state name

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: The specified state name was less than 1 character or more than
31 characters.
User Action: Choose a state name with 1 to 31 characters.
INVSTLEVEL,

structure level is invalid or already up to current structure level

Facility: MONITOR, Monitor Utility
Explanation: An error occurred while TPU was executing a MONITOR
CONVERT command. The structure level of the input file is either unknown
or already up to the current MONITOR structure level.
User Action: Try to play back the MONITOR recording file. If it plays back
properly, it is already up to the current structure level. If it still does not play
back, the structure level is unknown to this version of MONITOR.
INVSTMNBR,

invalid stream number

Facility: SMB, Symbiont Services
Explanation: An invalid stream number was detected. This is a fatal return
status.
User Action: Please submit an SPR.
INVSTR,

string too long for field

Facility: AUTHORIZE, Authorize Utility
Explanation: The character string you specified is too long.
User Action: See the VAX/VMS Authorize Utility Reference Manual for
information on character string length restrictions.
INVSTRDES,

invalid string descriptor

Facility: LIB, Run-Time Library General Procedures and OTS, Language
Independent Run-Time Library Support Procedures
Explanation: A string descriptor passed to a general library procedure did
not contain a valid DSC$B_CLASS field.
User Action: Locate the call to the library that caused the error, and initialize
the field to the proper class of descriptor. Refer to the VAX/VMS Run¬
Time Library Routines Reference Manual for a description of the classes of
descriptors.

2-265

Messages

INVSTRLEV,

invalid structure level

Facility: SMB, Symbiont Services
Explanation: An invalid structure level was returned by the
SMB$INITIALIZE routine. This is a fatal return status.
User Action: Specify a valid structure level not greater than SMBMSG$K_
STRUCTURE-LEVEL.
INVSTRUCT,

invalid structure level in save set

Facility: BACKUP, Backup Utility
Explanation: An incorrect value occurred in the structure level field of a save
set block. Data in the save set is corrupted.
User Action: None. Save set data has been lost.
INVSYMNAM,

invalid symbol name

Facility: LIB, Run-Time Library General Procedures
Explanation: The length of the specified symbol was greater than 255
characters or the symbol did not begin with a letter.
User Action: Do not specify a symbol name with more than 255 characters.
Ensure that all symbol names begin with letters.
INVTAB,

command tables have invalid format - see documentation

Facility: CLI, Command Language Interpreter (DCL)
Explanation: An unrecognizable command table format was encountered
while attempting to automatically upgrade old command tables to the current
format.
User Action: Use the Command Definition Utility command SET
COMMAND to recreate the tables.
INVTABSPEC,

Tabs specification incorrect, not changed

Facility: VAX Text Processing Utility
Explanation: Your argument to the built-in procedure SET (TAB—STOPS)
was invalid. You must specify an integer value between 1 and 65535, or a
string consisting of only spaces and integers. If you specify a string, then the
integers must be given in ascending order to achieve predictable behavior.
User Action: Correct your argument to the built-in procedure SET (TABSTOPS).
INVTERTAB,

invalid terminal table

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: An invalid terminal table address was specified.
User Action: Make sure you are passing the terminal table argument by
reference and not by value. Make sure the terminal table address was
acquired by calling SMG$INIT_TERM—TABLE.

2-266

Messages

INVTOKEN,

unrecognized token 'symbol-name7

Facility: PATCH, VAX Image File Patch Utility
Explanation: The symbol you specified is not recognized as a valid PATCH
command name or qualifier.
User Action: Specify valid symbol and retry.
INVTQEFMT,

Invalid time queue entry format

builtin type 'type-name' is not defined

Facility: CDU, Command Definition Utility
Explanation: CDU encountered an illegal keyword in a BUILTIN definition
while reading from a CLD file.
User Action: Edit the CLD file so that all BUILTIN keywords are defined.
INVTYPE,

invalid LIB$TPARSE state table entry

Facility: LIB, Run-Time Library General Procedures
Explanation: The state table passed to the LIB$TPARSE procedure was
invalid and could not be processed.
User Action: Correct the format of the state table in your program. Refer
to the VAX/VMS Run-Time Library Routines Reference Manual for the correct
format.
INVUIC,

'uic' is an invalid UIC specification

Facility: RUN, Run Detached Utility
Explanation: UIC value specified with the /UIC qualifier is invalid.
User Action: Reenter uic using valid format.
INVUIC,

invalid UIC - must be of the form [group,member]

Facility: CLI, Command Language Interpreter (DCL)
Explanation: The command contains an invalid UIC. The group and member
portions of a UIC must be specified within square brackets [] and must be
separated by a comma.
User Action: Correct the UIC and reenter the command.

2-267

INVUSER,

invalid username 'name'

Facility: INPSMB, Input Symbiont
Explanation: The specified user name is syntactically invalid.
User Action: Correct the error and reenter the job.
INVUSERNAME,

username syntax error

Facility: AUTHORIZE, Authorize Utility
Explanation: The user name you specified contains a syntax error.
User Action: Enter alphanumeric, underscore, and dollar sign characters only
when you specify user names.
INVUSERSPEC,

error in user specification

Facility: AUTHORIZE, Authorize Utility
Explanation: You specified an incorrect user name.
User Action: Enter a user name specifying a string of 1 through 12
alphanumeric characters, underscores, wildcard characters (dollar signs are
permissible, but usually reserved for system names) or a UIC.
INWAL,

unrecognized value

Facility: NCP, Network Control Program
Explanation: A value entered for a prompt was invalid.
User Action: Reenter the value.
INWALCLAUSE,

invalid value clause encountered

Facility: CDU, Command Definition Utility
Explanation: CDU encountered a invalid VALUE keyword while reading
from a .CLD file.
User Action: Edit the CLD file so that all VALUE keywords are legal.
INWEC,

invalid or unspecified interrupt vector

Facility: SYSGEN, System Generation Utility
Explanation: Either no interrupt vector was specified in a SYSGEN command
CONNECT, or the one that was specified is not within the UNIBUS interrupt
vector address range.
User Action: Reissue the command specifying a valid vector number.
INWIEWSP,

invalid /VIEWING_TIME specification

Facility: MONITOR, Monitor Utility
Explanation: The /VIEWING—TIME value must be an unsigned contiguous
string of decimal digits forming a value in the range of 1 to 9,999,999
inclusive.
User Action: Reissue the MONITOR request, specifying a valid /VIEWING—
TIME value.

Messages

INWMSOSC,

invalid VMS operating system command in record "record
number"

Facility: PSM, Print Symbiont
Explanation: This status is returned by a print symbiont format routine
indicating invalid VMS operating system command in record.
User Action: Please submit an SPR.
INWOLFMT,

volume format specified is not consistent with file spec

Facility: EXCHANGE, Exchange Utility
Explanation: The EXCHANGE utility encountered a /VOLUME—FORMAT
qualifier which did not make sense for the volume type implied by the file
specification.
User Action: It is very seldom necessary to use a /VOLUME—FORMAT
qualifier, since the defaults taken by EXCHANGE are usually correct. Either
leave the /VOLUME—FORMAT off, or use the correct option.
INVWIDARG,

width of 0 is not permitted

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: An attempt was made to change the characteristics of terminal,
setting its width to 0.
User Action: Correct the code. A width of 0 is illegal.
IO_CONCLO,

I/O continued to closed file

Facility: OTS, Language Independent Run-Time Library Support Procedures
Explanation: An attempt was made to perform I/O to a file being closed.
This error can occur only at AST level.
User Action: Correct the program so that AST level routines do not perform
I/O on files which may be closing.
IOERR,

NCP/NICE I/O error

Facility: NCP, Network Control Program
Explanation: A communications error occurred.
User Action: Check the quality of the line.
IOERROR,

I/O error initializing volume on 'device-name7

Facility: INIT, INITIALIZE Volume Command
Explanation: The operator requested a volume initialization. An I/O error
occurred during the write process.
User Action: Attempt to perform the operation again using another volume.
Dump the error log to determine whether a hardware error occurred.

2-269

IOP,

operation invalid for file organization or device
Facility: RMS, VAX Record Management Services
Explanation: An invalid VAX RMS operation was attempted. This error can
be caused by any of the following conditions:
•

An attempt to perform block I/O when block I/O access was not specified.

•

An attempt to perform record I/O when record I/O access was not
specified.

•

An attempt to rewind a process-permanent file.

•

An operation not valid for the device type (for example, a rewind request
on a line printer) or the file organization (for example, an erase or extend
request for a magnetic tape file).

User Action: Verify that the call to the VAX RMS service was coded correctly.
If necessary, modify your program to detect and respond to the condition.
IRC,

illegal record encountered; VBN or record number STV = 'nnn7
Facility: RMS, VAX Record Management Services
Explanation: The byte count field or the control byte for a record in a file is
invalid. For sequential and indexed files, the status value (STV) field contains
the virtual block number of the block containing the record. For relative
files, the status value (STV) field contains the record number of the corrupted
record.
User Action: For sequential and indexed files, try to recreate the rest of the
file. For relative files, reinsert the bad record with the $PUT service using the
UIF option in the ROP parameter.
This error is caused by hardware errors, VAX RMS or system software errors,
or inadvertent modification of files by non-RMS programs.

ISD—OFF,

image section descriptor offset is invalid

Facility: IMG ACT, Image Activator
Explanation: The offset in an image header block points beyond the end of
that block. This usually indicates a corrupted or invalid image.
User Action: Relink the image.
ISD—SIZ,

image section descriptor length is invalid

Facility: IMG ACT, Image Activator
Explanation: The length field of an ISD is invalid. This usually indicates a
corrupted or invalid image.
User Action: Relink the image.
ISD—VBN,

ISD VBN greater than header block count

Facility: IMG ACT, Image Activator
Explanation: The list of ISDs has extended to a block beyond the maximum
number of blocks allocated to the image header. This usually indicates a
corrupted or invalid image.
User Action: Relink the image.

Messages

ISI,

invalid internal stream identifier (ISI) value
Facility: RMS, VAX Record Management Services
Explanation: The internal stream identifier of the RAB does not specify a
valid stream.
User Action: This error usually indicates that the stream has not been
connected; or that the RAB has been inadvertently altered.

ITC,

Index entry too complicated or long
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: The entry exceeds the limit of the index buffer for a single item.
User Action: Reduce the length of the index entry.

ITD,

.IF commands nested too deep: 'string7
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: The number of nested conditional commands (.IF, .IFNOT)
exceeds the maximum limit of 10.
User Action: Reduce the number of conditional commands.

ITMNOTDEF,

item requested with the /ITEM qualifier not defined for this
revision level

Facility: MONITOR, Monitor Utility
Explanation: At least one of the items requested with the /ITEM qualifier is
not defined. For a playback request, this situation can occur if the file being
played back was recorded by MONITOR in a previous version of VAX/VMS.
For that version, the item may not have been defined. For a live request, the
item may no longer be defined for the current revision of VAX/VMS.
User Action: Reissue the MONITOR command, requesting only those items
that were defined when the input file was recorded or, for a live request, are
currently defined. As an alternative, specify /ITEM=ALL to obtain all items
available in the file for the requested class.
IVADDID,

system # 'id-number7 cannot be added to the display

Facility: SHOW, SHOW Facility
Explanation: Information for the system identified by the system ID number
entered is not available, or the system ID number entered is not the system
ID of a node which was previously removed from the display using the
REMOVE SYSTEM/ID=sy stem-id command.
It should be noted that the system ID number must match the ID number in
the SYS—ID field and that it must be entered in the same radix as that of the
SYS—ID field. For more information about changing the radix of a field, enter
the HELP SET field/FORMAT.
User Action: Verify that the system ID entered is correct and reenter the
command with the correct system ID, or type INIT to initialize the display
and restore all nodes to the display. If the system ID is correct, then be
sure to remove the node from the display before attempting to add it to the
display.

2-271

IVADDNODE,

node 'node-name' cannot be added to the display

Facility: SHOW, SHOW Facility
Explanation: Information for the system identified by the node name entered
is not available, or the node name entered is not the name of a node which
was previously removed from the display using the REMOVE
SYSTEM/NODE=node-name command.
User Action: Verify that the node name entered is correct and reenter the
command with the correct nodename, or type INIT to initialize the display
and restore all nodes to the display. If the node name is correct, then be
sure to remove the node from the display before attempting to add it to the
display.
IVADDR,

invalid media address

Facility: SYSTEM, VAX/VMS System Services
Explanation: A disk address specified in a physical disk read or write
operation was not valid. This error occurs for physical read and write
operations or as a result of a hardware error.
User Action: Verify the disk address specified and update the program.
IVATIME,

invalid absolute time - use DD-MMM-YYYY:HH:MM:SS.CC format

Facility: CLI, Command Language Interpreter (DCL)
Explanation: The specified absolute time is in an incorrect format.
User Action: Reenter the time in the format shown in the error message.
IVBAKADIO,

Invalid backing store address for I/O

invalid bad block specifier in string 'string'

Facility: BAD, Bad Block Locator Utility
Explanation: The block, as specified, contains an illegal character.
User Action: None. If the utility is in prompting mode, then the user is
prompted for the next block. If it is processing the values entered in the
command line, the next entity is processed.

Messages

IVBLKNUM,

'string7 is an invalid block number, 'position' value 'dddddddd' is
out of range

Facility: BAD, Bad Block Locator Utility
Explanation: The block number as specified is invalid due to the value in the
'position' field.
User Action: None. If the utility is in prompting mode, then the user is
prompted for the next block. If it is processing the values entered in the
command line, the next entity is processed.
IVBUFLEN,

invalid buffer length

Facility: SYSTEM, VAX/VMS System Services
Explanation: The exact meaning of this message depends on the device.
If the device is an LPA11-K and if this error occurs for an initialize LPA11-K
request, the initialize command table length is not the required 278 bytes. If
this error occurs for a start data transfer request, there are several possible
causes:
•

Command table length is not the required 40 bytes.

•

Buffer area size is not evenly divisible by the number of buffers assigned.

•

Individual buffer size is 0.

•

Individual buffer size is not a multiple of 2 for a multirequest mode
request, or is not 4 for a dedicated mode request.

•

Random Channel List length is 0 or not a multiple of 2.

•

Bit 15 in the last word of the Random Channel List is not set.

If the device is a DR32 interface, the command block size or the buffer block
size is zero or equal to or greater than 2**29, or the command table length is
not XF$K_CMT_LENGTH.
User Action: Action depends on the type of device to which the I/O request
was directed. Refer to the VAX/VMS I/O User's Reference Manual: Part II for
additional information.
IVCITAN,

invalid I/O channel

Facility: SYSTEM, VAX/VMS System Services
Explanation: The channel number specified in an input or output request is
not a valid channel number; the I/O operation cannot be performed.
User Action: Check for a programming error. Verify that the request to
assign the I/O channel completed successfully and returned a valid channel
number.

2—273

IVCHAR,

invalid numeric value - check for invalid digits

Facility: CLI, Command Language Interpreter (DCL)
Explanation: The command interpreter encountered a character string in a
context where it expected a numeric value (as the object of an arithmetic
operation in an expression, or following a qualifier that requires a numeric
value.)
User Action: Examine the command string for an undefined or incorrectly
spelled symbol name, a missing radix operator (for example, %X) preceding
a hexadecimal or octal value, an illegal value following a radix operator (for
example, %09), or for a syntax error. Reenter the command.
IVCHNLSEC,

invalid channel for create and map section

Facility: SYSTEM, VAX/VMS System Services
Explanation: The channel number specified in a request to create and/or
map a section file is busy; the section cannot be mapped.
User Action: Verify that the $OPEN request (to open the section file)
completed successfully and returned a valid channel number.
IVCMD,

invalid command

Facility: LATCP, Local Area Transport Control Program
Explanation: The command that was entered was not legal.
User Action: Make sure you are using the correct command. Reenter the
command.
IVDEVNAM,

invalid device name

Facility: SYSTEM, VAX/VMS System Services
Explanation: A device name contains invalid characters, no device is
specified, or a command or program accepts only certain types of devices
in a particular context.
User Action: Verify that the device name is specified correctly and is suitable
for the requested operation. If a logical name is used, verify that it has been
assigned a proper equivalence name.
IVDTIME,

invalid delta time - use DDDD-HH:MM:SS.CC

Facility: CLI, Command Language Interpreter (DCL)
Explanation: The specified delta time is in an incorrect format.
User Action: Reenter the delta time in the format shown in the error
message.
IVFNAM,

invalid lexical function name - check validity and spelling

Facility: CLI, Command Language Interpreter (DCL)
Explanation: A command contains the character string F$name() where
name is not a valid function.
User Action: Verify the spelling of the lexical function. Use the DCL
command HELP or refer to the VAX/VMS DCL Dictionary for a list of lexical
functions.

Messages

IVGBLTYP,

Invalid global master PTE type

invalid global section name

Facility: SYSTEM, VAX/VMS System Services
Explanation: An illegal global section name was specified.
User Action: Refer to the VAX/VMS System Services Reference Manual for
global section name requirements.
IVKEYNAM,

unrecognized key name - check validity and spelling

Facility: CLI, Command Language Interpreter (DCL)
Explanation: You specified a key name incorrectly.
User Action: Correct the spelling of the key name.
IVKEYW,

unrecognized keyword - check validity and spelling

Facility: CLI, Command Language Interpreter (DCL)
Explanation: A keyword specified in a command is not valid for the
command.
User Action: The rejected portion of the command is displayed between
backslashes. Use the DCL command HELP or refer to the VAX/VMS DCL
Dictionary for a list of valid keywords.
IVLISTK,

Interrupt stack invalid restart

2-275

IVLOCKID,

invalid lock id

Facility: SYSTEM, VAX/VMS System Services
Explanation: The lock identification specified in a system service request (for
example, $ENQ or $DEQ) is not a valid lock identification for that process.
User Action: Check for a programming error. Verify that the $ENQ system
service request, which returned the lock identification, completed successfully.
IVLOGNAM,

invalid logical name

Facility: SYSTEM, VAX/VMS System Services
Explanation: A name string exceeds the maximum length required, or has
a length of zero. Logical names are limited to a length of 63 characters;
process names, global section names, and common event flag cluster names
are limited to 15 characters.
User Action: If the error occurs during command processing, verify the
command. If the error occurs during execution of a program, check that
the character string descriptors pointing to name strings indicate the correct
lengths.
IVLOGTAB,

invalid logical name table number

Facility: SYSTEM, VAX/VMS System Services
Explanation: A create or delete logical name system service request specified
a logical name table number that was not 0 (system), 1 (group), or 2 (process).
User Action: Check for a programming error. Verify that the logical name
table number is 0, 1, or 2.
IVLVEC,

section not installed with privilege

Facility: SYSTEM, VAX/VMS System Services
Explanation: A shareable image has not been installed with privilege.
User Action: All privileged, shareable images, that is, those images that
contain user-written system service vectors, must be installed using the
/PROTECT qualifier.
IVMODE,

invalid mode for requested function

Facility: SYSTEM, VAX/VMS System Services
Explanation: This message is associated with a status code returned by an
initialize LPA11-K request. The first 3 bits (2:0) of the first word (mode word)
in the command table are not 0.
User Action: Correct the LPA11-K command table.

Messages

IVOPER,

unrecognized operator in expression - check spelling and syntax

Facility: CLI, Command Language Interpreter (DCL)
Explanation: An arithmetic expression contains a period (.), indicating a
logical, arithmetic, or string operator, but the operator is not a recognized
operator. The rejected portion of the command is displayed between
backslashes.
User Action: Correct the command. Type the DCL command HELP
EXPRESSIONS for a list of valid operators or refer to the VAX/VMS DCL
Dictionary.
IVORDER,

order of ACEs being modified is incorrect for object

Facility: SET, SET Facility
Explanation: The order of the ACEs being replaced is incorrect.
User Action: Verify the order of the ACES being replaced with the
DIRECTORY/ACL command or the DCL SHOW ACL command.
IVPROT,

invalid protection code only use combinations of R,W,E, and D

Facility: CLI, Command Language Interpreter (DCL)
Explanation: The protection code specified for a file or volume is not in the
correct syntax.
User Action: Use the DCL command HELP or refer to the VAX/VMS DCL
Dictionary, if necessary, for the correct syntax and reenter the command.
IVPROTECT,

invalid page protection code

Facility: SYSTEM, VAX/VMS System Services
Explanation: A page protection code is specified as one or is greater than 15.
User Action: Check for a programming error.
IVQLOC,

invalid qualifier location - place after a parameter

Facility: CLI, Command Language Interpreter (DCL)
Explanation: A qualifier that can be used only to qualify a parameter value
in a command was placed following the command name.
User Action: Reenter the command; place the qualifier following the
parameter value it actually qualifies. Use the DCL command HELP or refer to
the VAX/VMS DCL Dictionary to determine the meaning and placement of the
qualifier.
IVQUAL,

invalid qualifier name

Facility: INSTALL, Install Utility
Explanation: An invalid qualifier was specified.
User Action: Reenter the command line.

2-277

Messages

IVQUAL,

unrecognized qualifier - check validity, spelling, and placement

Facility: CLI, Command Language Interpreter (DCL)
Explanation: The qualifier was spelled incorrectly or improperly placed in
the command line.
User Action: Correct the command line.
IVQUAL,

value for qualifier 'qualifier' is invalid as 'value'

Facility: LATCP, Local Area Transport Control Program
Explanation: The qualifier passed to LATCP was not correct as given.
User Action: Please check the value specified for the qualifier and reenter the
command.
IVQUOTAL,

invalid quota list

Facility: SYSTEM, VAX/VMS System Services
Explanation: The quota list specified for a Create Process system service was
not in the proper format, or it contained illegal quota names.
User Action: Check for a programming error. Verify that the call to the
service was programmed correctly. Refer to the VAX/VMS System Services
Reference Manual for programming specifications.
IVREMID,

system # 'id-number' cannot be removed from the display

Facility: SHOW, SHOW Facility
Explanation: The system ID number entered is not the system ID number of
a node which is currently being displayed.
User Action: Verify that the SYS_ID field in the SYSTEMS class is being
displayed and if not, display the SYS—ID field by entering in the command
ADD SYS—ID.
Verify that the system ID entered is one of the system IDs being displayed in
the SYS—ID field.
IVREMNODE,

node 'node-name' cannot be removed from the display

Facility: SHOW, SHOW Facility
Explanation: The node name entered is not the name of a node which is
currently being displayed.
User Action: Verify that the NODE field in the SYSTEMS class is being
displayed and if not, display the NODE field by entering in the command
ADD NODE. Verify that the node name entered is one of the node names
being displayed in the NODE field.
I VS,

illegal /VARIANT qualifier
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: The name specification for conditional commands is illegal.
User Action: Correct the name specification.

2-278

Messages

IVSECFLG,

invalid process/global section flags

Facility: SYSTEM, VAX/VMS System Services
Explanation: Flags specified as input arguments to a system service were not
valid.
User Action: Verify that the call to the service was coded correctly. See the
VAX/VMS System Services Reference Manual for coding specifications.
IVSECIDCTL,

invalid section identification match control

Facility: SYSTEM, VAX/VMS System Services
Explanation: The match control field in the section identification argument to
identify a global section contains an invalid number.
User Action: Verify that the call to the service was coded correctly. See the
VAX/VMS System Services Reference Manual for coding specifications.
IVSSRQ,

invalid system service request

Facility: SYSTEM, VAX/VMS System Services
Explanation: A call was made to a service that does not exist.
User Action: Check for a programming error.
IVSSRVRQST,

invalid system service request

invalid status flag

Facility: SYSTEM, VAX/VMS System Services
Explanation: If the Create Process system service ($CREPRC) was called, this
message indicates that a reserved bit was set in a status flag argument. If the
Create Mailbox and Assign Channel system service ($CRIiMBX) was called,
this message indicates that the prmflg byte is not set correctly.
User Action: If $CREPRC was called, verify that the call was coded
correctly. Refer to the VAX/VMS System Services Reference Manual for coding
specifications. If $CREMBX was called, set the prmflg argument to either
1 or 0.

2-279

Messages

IVSYMB,

invalid symbol name - start with an alphabetic character

Facility: CLI, Command Language Interpreter (DCL)
Explanation: An assignment statement specified a symbol name that does
not begin with an alphabetic character.
User Action: Choose a name for the symbol that begins with one of the
letters A through Z and reenter the command.
IVTIME,

invalid time

Facility: SYSTEM, VAX/VMS System Services
Explanation: A time value specified in a system service call is invalid. Either
a delta time is greater than 10,000 days, or a calculated absolute time is less
than the system date and time.
User Action: Check for a programming error. Verify that the call to the
service was coded correctly.
IVTYPE,

invalid system type 'system-type7, - must match HW_TYPE field or ALL

Facility: SHOW, SHOW Facility
Explanation: The hardware type entered is not a valid hardware type or
information for systems of the type entered is not available.
User Action: Verify that the HW—TYPE field in the SYSTEMS class is being
displayed and if not, display the HW—TYPE field by entering in the command
ADD HW-TYPE. If using the REMOVE SYSTEMS/TYPE=hardware-type
command, then verify that the hardware type entered is one of the hardware
type being displayed in the HW—TYPE field. If using the ADD SYSTEMS
/TYPE=hardware-type command, then verify that the hardware type entered
is one of V785, V780, V750, or HS50, or simply use the command ADD
SYSTEM/TYPE=ALL
IWALU,

invalid value syntax - see command documentaion

Facility: CLI, Command Language Interpreter (DCL)
Explanation: A value for a command qualifier is not specified correctly, or a
command is not being used in its proper context. The rejected portion of the
command is displayed between backslashes.
User Action: Use the DCL command HELP or refer to the VAX/VMS DCL
Dictionary to determine the proper syntax or use of the command.
IWERB,

unrecognized command verb - check validity and spelling

Facility: CLI, Command Language Interpreter (DCL)
Explanation: The first word on the command is not a valid DCL command
or a symbol name equated with a command. The rejected portion of the
command is displayed between backslashes.
User Action: Check the spelling of the command name or symbol name and
reenter the command.

2-280

Messages

IVWSETLIST,

Invalid working set list entry

error communicating with job controller

Facility: SYSTEM, VAX/VMS System Services
Explanation: An error occurred in communicating with the job controller
while handling an implicitly spooled file.
User Action: The file may or may not be printed. If it is not printed, a lost
file results. The system manager should ensure that the job controller is
functioning properly.
JEC,

Unexpected text at end of command: 'string'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: Extraneous text (not a valid terminator) follows this command.
User Action: Insert a valid terminator after the command.

JNLACP,

Fatal error detected by journal ACP

Fatal error detected by journal driver

JNLPUT,

error writing to journal file

Facility: PATCH, VAX Image File Patch Utility
Explanation: An output error occurred while PATCH was writing to the
journal file.
User Action: This message is issued with accompanying messages. Take
corrective action based on the accompanying messages.
Job 'name' (queue 'name7, entry 7n7) completed
Facility: JBC, Job Controller
Explanation: This message is issued in response to the /NOTIFY qualifier
of the PRINT or SUBMIT command to indicate that the specified job has
completed. If the job completed unsuccessfully, this message is followed by
the completion status of the job.
User Action: The message is informational.
Job 'name7 (queue 'name7, entry 7n7) holding
Job 'name7 (queue 'name7, entry 7n7) holding until 'time7
Job 'name7 (queue 'name7, entry 7n7) pending
Job 'name7 (queue 'name7, entry 7n7) started on 'name7
Facility: JBC, Job Controller
Explanation: These messages are issued in response to the /IDENTIFY
qualifier of the PRINT or SUBMIT command to indicate that the specified
job has been successfully entered on the queue listed. By default, this
information is displayed on the current output device for the PRINT and
SUBMIT commands.
User Action: This message is informational.
JOB ABORT,

job aborted during execution

Facility: JBC, Job Controller
Explanation: The execution of the affected job was aborted by a
STOP/ABORT, STOP/ENTRY, or DELETE/ENTRY command.
User Action: If necessary, resubmit the job.
JOBCARD,

job beginning 'command7

Facility: INPSMB, Input Symbiont
Explanation: The system encountered an error in a batch job entered from
a card reader. This message displays the text of the JOB command; it is
followed by the error messages for the batch job.
User Action: None.

Messages

JOBDELETE,

job deleted before execution

Facility: JBC, Job Controller
Explanation: The affected job was deleted by a DELETE/ENTRY or DELETE
/QUEUE command before it executed.
User Action: If necessary, resubmit the job.
JOBQUEDIS,

system job queue manager is not running

Facility: JBC, Job Controller
Explanation: The requested operation cannot be executed because the system
job queue manager has not been started. This error is returned on queue
operations before the START/QUEUE/MANAGER command has been
executed.
User Action: Consult the system manager.
JOBQUEENA,

system job queue manager is already running

Facility: JBC, Job Controller
Explanation: The system job queue manager cannot be started because it is
already running. This error is returned in response to the START/QUEUE
/MANAGER command when the queue manager has been previously started.
User Action: If the system job queue manager must be restarted to specify
different queue file parameters, first issue the STOP/QUEUE/MANAGER
command. Otherwise, no action is necessary.
JOBREQUEUE,

job requeued during execution

Facility: JBC, Job Controller
Explanation: The execution of the affected job was aborted by a STOP
/REQUEUE command.
User Action: None. The job was requeued and will be executed again.
JOUCLOSOUT,

error closing output journal file

Facility: ACLEDIT, Access Control List Editor
Explanation: The ACL editor encountered an error closing the journal file.
User Action: Examine the secondary error status to determine exactly why
the journal file closing failed (privilege violation, device write locked, etc.)
JOUOPENOUT,

error opening 'file-name' as output journal file

Explanation: The ACL editor was unable to create the journal file.
User Action: Examine the secondary error status to determine exactly why
the journal file creation failed (privilege violation, device write locked, etc.)
Journal file could not be closed
Facility: EDT, EDT Editor
Explanation: You used the /RECOVER qualifier in your EDIT/EDT
command line, but EDT was unable to close the journal file after processing
the commands in it. Some problem exists at the system level with that file.
User Action: Correct the problem indicated by the file system message.

2-283

Journal file could not be opened
Facility: EDT, EDT Editor
Explanation: The journal file given in the command line cannot be opened.
EDT will display an associated file system message for the error.
User Action: Correct the problem indicated by the file system message.
JOURNAL,

journaling to 'file-spec'

Facility: BACKUP, Backup Utility
Explanation: The Backup Utility is writing journal records to the specified file
in response to the /JOURNAL qualifier. This message is displayed only if the
/LOG qualifier is specified.
User Action: None.
JOURNALBEG,

Journal of edit session started

Facility: VAX Text Processing Utility
Explanation: The journaling of your VAXTPU session has begun.
User Action: None is required. However, you may execute the built-in
procedure JOURNAL—CLOSE if you want to close the journal file.
JOURNALCLOSE,

Journal file successfully closed, journaling stopped

Facility: VAX Text Processing Utility
Explanation: The built-in procedure JOURNAL—CLOSE has closed the
journal file. Your subsequent commands will not be written to the journal
file.
User Action: None.
JOURNALEOF,

End of journal file found unexpectedly

Facility: VAX Text Processing Utility
Explanation: Journal recovery was aborted due to an unexpected end of file.
User Action: If the recovered information is sufficient, resume editing from
this point. VAXTPU has recovered as much as it can from your journal file.
JOUWRITERR,

error writing 'file-name' journal file

Facility: ACLEDIT, Access Control List Editor
Explanation: An error occurred while trying to write the ACL editor's journal
file.
User Action: Examine the secondary error status to determine exactly what
caused the write to fail. This will not affect the functioning of the ACL
editor (unless the system crashes during the editing session, and a recovery is
attempted).

Messages

KBF,

invalid key buffer
Facility: RMS, VAX Record Management Services
Explanation: The specified key buffer is in an area of memory that cannot be
correctly accessed by the caller.
User Action: Verify that the call to the VAX RMS service was programmed
correctly. Specifically, check that the key buffer address is correctly specified.

KEY,

invalid record key
Facility: CONVERT, Convert Utility
Explanation: You have specified a key of the wrong data type.
User Action: Supply a key with the correct data type.

KEY,

invalid record number key or key value
Facility: RMS, VAX Record Management Services
Explanation: An invalid key value was specified in one of the following
ways:
•

A negative or zero record number was specified for a random operation
on a sequential or relative file.

•

A packed decimal key value specified for an indexed value contained an
invalid nibble.

User Action: Note the condition. Modify the source program, if necessary, to
detect and respond to the condition.
KEYALRINS,

key already inserted in tree

Facility: LIB, Run-Time Library General Procedures
Explanation: A key was found in the tree, so a new key was not inserted.
User Action: None. The operation was successful.
KEYAMBINC,

key specification is ambiguous or inconsistent

Facility: SORT, VAX SORT/MERGE Utility
Explanation: You specified duplicate key parameters for a single /KEY
qualifier.
User Action: Specify each key parameter only once. For multiple keys, use a
/KEY qualifier for each key.
KEYCNV,

synonym 'key name7 has been converted to 'key name'

Facility: CLI, Command Language Interpreter (DCL)
Explanation: This informational message signifies that the key name specified
in the DEFINE/KEY command is a synonym for a definable key name. The
synonym name is converted to the actual key name prior to defining the key.
User Action: None.

2-285

Messages

KEYDEFPRO,

key definition is protected - cannot be changed or deleted

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: The specified key is already defined, and since its definition is
protected, it cannot be changed or redefined.
User Action: None.
KEYED,

mismatch between sort/merge keys and primary file key

Facility: SORT, VAX SORT/MERGE Utility
Explanation: You created an empty indexed file with a primary key that does
not match the sort key. The sort operation is less efficient than it is when the
two keys match.
User Action: For greater efficiency, create a new indexed file and/or change
your sort key.
KEY—LEN,

invalid key length, key number n, length n

Facility: SORT, VAX SORT/MERGE Utility
Explanation: The key size is incorrect for the data type, or the total key size
is greater than 32,767.
User Action: Specify correct key field size. Size must be less than or equal
to 32,767 for character data; 1, 2, 4, 8, or 16 for binary data; and less than or
equal to 31 for decimal. Also, only ascending or descending order is allowed.
KEYMAPNOTFND,

Key map 'key-map-name' not found in key-map list 'keymap-list-name'

Facility: VAX Text Processing Utility
Explanation: You are trying to remove a key map that is not in the key-map
list.
User Action: Enter the built-in procedure SHOW (KEY_MAP_LISTS) on the
command line to obtain the names of the key maps in your key-map list.
KEYNAMLNG,

key 'key-name' name length illegal in library 'file-spec'

Facility: LIBRAR, LIBRARY Command
Explanation: The name of the module you are inserting exceeds the name
length limit for the library.
User Action: Rename the module before inserting it into the library.
KEYNOTDEF,

key is not defined

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: An attempt was made to perform an operaton, such as
SMG$GET_KEY_DEF, on a key which was not defined.
User Action: Check your program to see if this key should have been
defined.

2—286

Messages

KEYNOTFND,

key not found

Facility: LBR, Librarian Subroutine Package
Explanation: This error message is generated by the Librarian routines. The
Librarian could not find the key you specified in the key name argument to
the LBR$LOOKUP_KEY routine.
User Action: Correct the key name argument before calling the routine.
KEYNOTFOU,

key not found in tree

Facility: LIB, Run-Time Library General Procedures
Explanation: The specified key was not found in the tree.
User Action: Take appropriate action.
Keys cannot be defined in Nokeypad mode
Facility: EDT, EDT Editor
Explanation: The nokeypad DEFK command can reassign the key definition
function only in keypad mode to a key other than CTRL/K. It cannot be used
to redefine keys.
User Action: None. The attempted operation cannot be performed.
KEYWORDPARAM,

Reserved word not appropriate in the context

Facility: VAX Text Processing Utility
Explanation: Either a keyword or the name of a built-in procedure is being
used as a parameter.
User Action: Change the parameter and recompile your program.
KFF,

known file found
Facility: RMS, VAX Record Management Services
Explanation: A VAX RMS request to search the known file list completed
successfully, and the RMS file open is not required.
User Action: None. This message is provided for DIGITAL-supplied
component usage.

KMS—ASSFAIL,

KMS11 reload for /devicename-controller-unit,/ failed to assign
channel to device

Facility: PSI, VAX Packetnet System Interface
Explanation: VAX PSI failed to assign a channel to the specified device when
trying to load the microcode for the specified line. This message returns the
unit number optionally.
User Action: Make sure the device is loaded.

2—287

Messages

KMS—BADPARAM,

KMS11 reload for 'devicename-controller-unit', error in
internal data structure

Facility: PSI, VAX Packetnet System Interface
Explanation: A bad parameter has been detected in the item list requesting
VAX PSI to load the microcode for the specified line. This is an internal error.
User Action: Submit a Software Performance Report.
KMS—INSFMEM,

KMS11 reload, insufficient memory to load micro-code

Facility: PSI, VAX Packetnet System Interface
Explanation: VAX PSI failed to load the KMS11 microcode because there was
not enough memory available to construct the required data structures.
User Action: Increase the size of the nonpaged pool and try again.
KMS—MICLOAD,

PSI KMS11 reload for 'device-controller-unit', micro-code
reloaded

Facility: PSI, VAX Packetnet System Interface
Explanation: The microcode for the specified KMS line has been reloaded
successfully. You can now use this line. This message returns the unit
number optionally.
User Action: None.
KMS—NOSUCHLINE,

KMS11 reload for 'device-controller-unit' line does not
exist

Facility: PSI, VAX Packetnet System Interface
Explanation: No line database can be found for this line so the line has not
been declared. Typically, a user may have deleted the line when attempting
to reload the KMS 11 microcode. This message returns the unit number
optionally.
User Action: Redefine the line using the command SET LINE STATE ON
and try again.
KMS—QIOFAIL,

KMS 11 reload line 'device-controller-unit', QIO to text 'text'
failed

Facility: PSI, VAX Packetnet System Interface
Explanation: The QIO to perform the action specified by text on the specified
line failed. Typically, this is caused by hardware errors. This message returns
the unit number optionally.
User Action: Check the hardware, then retry the operation.
KNM,

key name buffer not accessible for key = 'nnn'

Facility: RMS, VAX Record Management Services
Explanation: The key name buffer address in a key definition XAB specifies
an area of memory that cannot be correctly accessed by the caller.
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 VAX RMS service
was coded correctly; in particular, verify that the buffer is readable for a
$CREATE operation, and writeable for a $DISPLAY or $OPEN operation.

2—288

Messages

KRF,

invalid key-of-reference for $GET/$FIND
Facility: RMS, VAX Record Management Services
Explanation: The key-of-reference value specified in the RAB is greater than
the number of keys defined for the file.
User Action: Verify that the call to the VAX RMS service was coded correctly.

KRNLSTAKNV,

Kernel stack not valid

index bucket will not hold two keys for key-of-reference = 'nnn'
Facility: RMS, VAX Record Management Services
Explanation: The size of the index buckets specified for the key must be
large enough to hold at least two key values.
User Action: The status code (STV) field of the FNB provides the key of
reference of the XAB in error. Verify that the VAX RMS service was coded
correctly.

KSZ,

invalid key size for $GET/$FIND
Facility: RMS, VAX Record Management Services
Explanation: The key size specified for a relative or sequential file does not
specify a length of four bytes. Or the key size specified for an indexed file is
greater than the key length or is zero for a string key.
User Action: Verify that the VAX RMS service was coded correctly.

LABELERR,

error in tape label processing on 'save-set-spec'

Facility: BACKUP, Backup Utility
Explanation: The Backup Utility encountered an error during an attempt to
process the file labels on the specified volume. The accompanying message
provides additional information.
User Action: Correct the condition that caused the error and reenter the
command.

2-289

LAN,

invalid lowest-level-index area number for key = 'nnn'
Facility: RMS, VAX Record Management Services
Explanation: The lowest-level-index area number specified in a key definition
XAB is not a defined area 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 VAX RMS service
was coded correctly.

LARGECNT,

'device7 is too large to be processed

Facility: BACKUP, Backup Utility
Explanation: The specified volume is too large to be processed by the Backup
Utility. The error may be caused because the specified cluster factor is too
small.
User Action: Retry the operation using a larger volume cluster factor.
LARGECNT,

disk too large to be supported

Facility: INIT, INITIALIZE Volume Command
Explanation: This version of Files-11 does not support a disk of this size.
User Action: Check the device driver to determine if it is initializing the
device database correctly. You may have a need for DIGITAL-supplied
custom software.
LASTCHANCE,

stack exception handlers lost, reinitializing stack

Facility: DEBUG, VAX/VMS Debugger
Explanation: The user's program contained an error that caused the exception
handling mechanism to fail. This error occurs when the stack is overwitten
by the user program or by deposit commands.
User Action: Identify and correct the error in the user program.
LCKPAGFUL,

no more pages may be locked in memory

Facility: SYSTEM, VAX/VMS System Services
Explanation: An attempt to lock pages in memory failed because the system
limit for the number of locked pages was reached.
User Action: The user program should be able to detect and respond to this
condition. If some pages were successfully locked, unload them and attempt
to load the new pages.
LDE,

Literal doesn't end with .END LITERAL: 'STRING'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: A DSR command .END LITERAL does not immediately follow
the final line of a DSR command .LITERAL n (where n is the number of lines
to be produced).
User Action: Put the DSR command .LITERAL on the correct line, recount
the number of lines of literal text and reset n, or remove the n value.

Messages

LENVIO,

address space length violation

Facility: SYSTEM, VAX/VMS System Services
Explanation: A virtual address specified in a system service call is beyond
the end of the process' program or control region.
User Action: Check for a programming error. Verify that the call to the
service was coded correctly.
LEX,

invalid $EXTEND for area 'nnn' containing an unused extent
Facility: RMS, VAX Record Management Services
Explanation: A VAX RMS $EXTEND operation attempted to extend the
specified area, and an unused extent was already allocated. Each area has, at
most, one current extent and one unused next extent.
User Action: The status value (STV) field of the FAB contains the area
number in error. Verify that the call to the VAX RMS service was coded
correctly.

LIBFIND,

failed to find valid module or STB at RFA 'number:number7 for module
'module-name' file 'file-name'

Facility: LINK, VAX Linker
Explanation: The linker tried to read the stated object module at the specified
Record File Address, but did not find a valid module. This is generally due to
someone deleting a module out of a library between Pass 1 and Pass 2.
User Action: Retry the link operation. If it continues to fail with the same
error, try rebuilding the library.
LIBNAMLNG,

library module name 'module-name' has illegal length ('decimalnumber')

Facility: LINK, VAX Linker
Explanation: A library module name specified in the /INCLUDE qualifier
has illegal length.
User Action: Reenter the command correctly.
LIBNOTOPN,

library not open

Facility: LBR, Librarian Subroutine Package
Explanation: This error message is generated by the Librarian routines.
Except for LBR$INI—CONTROL and LBR$OPEN, all routines require that the
library be open.
User Action: Open the library before calling the routine.
LIBOPN,

library already open

Facility: LBR, Librarian Subroutine Package
Explanation: This warning message is generated by the Librarian routines.
The library you attempted to open is already open.
User Action: None. Processing continues.

2—291

Messages

Line exceeded 255 characters, truncated
Facility: EDT, EDT Editor
Explanation: The input for the line exceeds 255 characters; the excess is
deleted.
User Action: None.
LINEABRT,

host aborted transmission or failed to respond

Facility: SYSTEM, VAX/VMS System Services
Explanation: The IBM host either aborted the current transmission with a
protocol sequence (EOT) or failed to respond to an emulator-generated ENQ.
In the latter case, the emulator sent the number of ENQ sequences specified
by the ENQ count in IO$_SETCHAR, and the IBM host did not issue an
appropriate response.
User Action: Retry the transmission. If you continue to receive this message
after several attempts, the line is probably defective and/or unusable.
LINERR,

command line segment in error _
Text7-

Facility: LINK, VAX Linker
Explanation: Errors were found during command line processing. The given
segment of the command line is in error.
User Action: Correct the error and retry the operation.
LINETOOLONG,

Line is maximum length, cannot add text to it

Facility: VAX Text Processing Utility
Explanation: The line in the text buffer is already at the maximum length
allowed.
User Action: Use the built-in procedure SHOW to find the maximum length
and then shorten the line.
LINETYP,

invalid line type

Facility: NCP, Network Control Program
Explanation: The line type referred to is not supported.
User Action: Enter a valid line type.
LINK,

error on logical link

Facility: CNF, NI Configurator
Explanation: An error occurred on a logical link.
User Action: See the accompanying message to determine the appropriate
action.

2-292

Messages

LINKABORT,

network partner aborted logical link

Facility: SYSTEM, VAX/VMS System Services
Explanation: The remote process disconnected the logical link either because
the process exited prematurely or because it was the normal way for the
process to disconnect the link.
User Action: Check to see if the node is reachable and retry.
LINKDISCON,

network partner disconnected logical link

Facility: SYSTEM, VAX/VMS System Services
Explanation: The remote process disconnected the logical link. This is an
expected action.
User Action: None.
LINKEXIT,

network partner exited

Facility: SYSTEM, VAX/VMS System Services
Explanation: The remote process exited before confirming the logical link for
one of the following reasons:
•

A problem with the log file on the remote node

•

An unopened remote log file because of a write-locked disk (on the remote
node)

•

A premature exit of the process

User Action: Refer to the VAX/VMS Networking Manual. Then either read
the remote log or retry the operation.
LINTOOLNG,

line too long

Facility: MACRO, VAX Macro Assembler
Explanation: A source line in a macro definition was longer than 1000
characters.
User Action: Restructure the source code so that the line is shorter.
LINWNGSTA,

line in wrong state

Facility: NIC, Network Information and Control Exchange
Explanation: A SET STATE operation is not valid.
User Action: Perform a valid operation.
LISINPSAV,

/LIST requires save set as input

Facility: BACKUP, Backup Utility
Explanation: The input specification for a listing operation must reference a
save set.
User Action: Correct the specification and reenter the command.

2-293

Messages

LISTNOTFND,

attribute name not previously defined

Facility: CDU, Command Definition Utility
Explanation: There is an undefined symbol reference in the syntax of the
.CLD file.
User Action: Define the syntax list in the CLD file.
LKBGRANTED,

LKB is granted, but shouldn't be

LKB reference count negative

lookup has not been done

Facility: LBR, Librarian Subroutine Package
Explanation: This error message is generated by the Librarian routines.
LBR$LOOKUP_KEY was not called before calling up LBR$GET_RECORD.
User Action: Call LBR$LOOKUP_KEY before calling LBR$GET_RECORD.
LKWSETFUL,

locked portion of working set is full

Facility: SYSTEM, VAX/VMS System Services
Explanation: No more pages can be locked in the working set because there
would not be enough remaining pages available dynamically for the image to
continue execution.
User Action: Use the DCL command SET WORKING _SET to increase the
working set limit, if the limit is not already set at the maximum allowed. If
the working set limit is already at the maximum allowed, correct the program
that attempted to lock too many pages in the working set.

2-294

Messages

LKWSTFAIL,

failed to lock pages into PSIACP working set memory

Facility: PSI, VAX Packetnet System Interface
Explanation: An attempt was made to lock some pages of memory into the
working set of PSIACP. This attempt failed because the working set was too
small.
User Action: Increase the size of the working set.
LNE,

logical name translation count exceeded
Facility: RMS, VAX Record Management Services
Explanation: VAX RMS encountered an error while translating a logical
name. The limit of 10 levels of logical name translation has been exceeded; a
logical name is recursively entered in a logical name table; or a logical name
translates to an invalid process permanent file name equivalence string.
User Action: Use the DCL command SHOW LOGICAL to verify the current
result of translation on the specified logical name. Verify that the call to the
VAX RMS service was coded correctly.

LOADERR,

error loading image, 'image-name'

Facility: ERF, ANALYZE/Error Log Utility
Explanation: An error occurred during an attempt to load the specified
image.
User Action: Obtain the specified image from your distribution kit. If
the specified image is not part of your distribution kit, submit a Software
Performance Report (SPR).
LOADFAIL,

failed to load filename

Facility: PSI, VAX Packetnet System Interface
Explanation: VAX PSI failed to load the specified file. This message is
qualified by an RMS error code. Typically, the file specified may be missing.
User Action: Take corrective action based on the accompanying RMS
message.
LOADIDX,

error loading secondary index n

Facility: CONVERT, Convert Utility
Explanation: Some error occurred during the load of the specified key of
reference on the output file. This message will be accompanied by another
message that will describe the error. NOTE: Indexes 0 through n-1 are intact.
User Action: Correct the error described by the other message and try again.
LOCKHEADER,

file ('file-id') 'file-name' deaccess locked

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the specified file was marked as
deaccess locked.
User Action: None. The file is unlocked. Optionally, if the user responded
to the /CONFIRM qualifier prompt by typing D, the file is deleted.

2-295

LOCKMGRERR,

Error detected by Lock Manager

error locking volume set - /REPAIR canceled

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility encountered an error during an attempt to
lock the volume set to execute a /REPAIR operation. The accompanying
message provides additional information.
User Action: Correct the condition that caused the error and reenter the
Verify Utility command line. The /REPAIR qualifier requires a system UIC or
SYSPRV privilege, or that the user be the owner of the volume.
LOCNEG,

entity explicitly and locally negated in command string

Facility: CLI, Command Language Interpreter (DCL)
Explanation: The specified qualifier was present in its negated form (with
/NO) and was used as a local qualifier.
User Action: None.
LOCPRES,

entity value is locally present in command string

Facility: CLI, Command Language Interpreter (DCL)
Explanation: The specified qualifier was present and was used as a local
qualifier.
User Action: None.
LOGCLOS,

logfile closed by operator 'file-spec7 logfile was 'file-spec'

Facility: OPCOM, Operator Communication
Explanation: This message indicates that OPCOM has closed the operator's
log file.
User Action: None.
LOGDBUR,

event receiver database update at 'dd-mm-yy hh:mm:ss.ms'

Facility: EVL, Event Logger
Explanation: The event receiver updated its internal database as a result of a
startup or notification from NETACP. This message displays the time stamp
for the update.
User Action: None. This is an informational message.

Messages

LOGDBUT,

event transmitter database update at 'dd-mm-yy hh:mm:ss.ms'

Facility: EVL, Event Logger
Explanation: The event transmitter updated its internal database as a result
of EVL startup or notification from NETACP. This message displays the time
stamp for the update.
User Action: None. This is an informational message.
LOGDISABL,

logins are currently disabled - try again later

Facility: LOGIN, Login Processor
Explanation: Interactive logins have been disabled by the system manager.
User Action: Wait until the system manager reenables logins.
LOGFAIL,

failed logfile operation on file 'file-spec7

Facility: OPCOM, Operator Communication
Explanation: The DCL command REPLY/INIT failed to create a new
operator communication log file. This message generally indicates a file
system failure.
User Action: Accompanying messages indicate the reason for the failure.
LOGIC,

logic error in NCP

Facility: NCP, Network Control Program
Explanation: A logic error occurred in NCP.
User Action: Submit a Software Performance Report.
LOGIC,

program logic error or unexpected condition

Facility: CNF, NI Configurator
Explanation: A condition or circumstance was encountered which
NICONFIG logic was unprepared to handle.
User Action: This is a programming error and should be reported.
LOGIN - account is auto-login only
Facility: LOGIN, Login Processor
Explanation: The automatic login feature permits users to log in to the
system without specifying a user name. An automatic login account cannot
be accessed by a normal interactive login or by an explicit DECnet access
control string. This message is not displayed to the user; it is written to the
system accounting and security audit records. The message displayed to the
user is "User authorization failure."
User Action: None.

2—297

Messages

LOGIN - account is disabled
Facility: LOGIN, Login Processor
Explanation: An attempt was made to log in to an account when the account
was disabled. An account's system access can be restricted by setting the
DISUSER flag in the user authorization file. This message is not displayed
to the user; it is written to the system accounting and security audit records.
The message displayed to the user is "User authorization failure."
User Action: None.
LOGIN - breakin evasion in effect
Facility: LOGIN, Login Processor
Explanation: Access to an account was denied because break-in evasion
was in effect for that account. This message is not displayed to the user; it
is written to the system accounting and security audit records. The message
displayed to the user is "User authorization failure."
User Action: None.
LOGIN - error accessing authorization record
Facility: LOGIN, Login Processor
Explanation: The Login Processor could not read the specific user record for
this user.
User Action: Try the operation again later.
LOGIN - error accessing network authorization file
Facility: LOGIN, Login Processor
Explanation: LOGIN could not read the SYS$SYSTEM:NETUAF.DAT
network user authorization file.
User Action: Determine whether the file SYS$SYSTEM:NETUAF.DAT exists
and, if it does, make sure it is not protected against system read access.
LOGIN - error accessing system authorization file
Facility: LOGIN, Login Processor
Explanation: LOGIN could not read SYS$SYSTEM:SYSUAF.DAT.
User Action: Check to see that the file exists and that it has system read
access.
LOGIN - error activating command interpreter 'CLI name7
Facility: LOGIN, Login Processor
Explanation: An error occurred when you tried to activate the specified
command interpreter.
User Action: Ensure that the command interpreter image exists and that the
image file has read access.

2-298

Messages

LOGIN - error activating command interpreter tables 'table name'
Facility: LOGIN, Login Processor
Explanation: LOGIN cannot access the specified command language
interpreter tables.
User Action: Determine whether the specified tables exist and, if they do,
make sure they are not protected against system read access.
LOGIN - error connecting to 'terminal name'
Facility: LOGIN, Login Processor
Explanation: An error occurred when the system attempted to reconnect to
the specified disconnected terminal.
User Action: Try again. If the error reoccurs, report it to your system
manager.
LOGIN - error creating space for command interpreter symbol table
Facility: LOGIN, Login Processor
Explanation: There was not enough virtual address space available to create
the command interpreter symbol table.
User Action: Check that the system is set up with the value of
VIRTUALPAGECOUNT large enough to allow the CLI to be mapped.
LOGIN - error opening 'filename' as input
Facility: LOGIN, Login Processor
Explanation: A file to be read by LOGINOUT (for example, a file containing
the announcement message) cannot be opened.
User Action: Ensure that the file exists and that it has read access.
LOGIN - error opening primary input file SYS$INPUT
Facility: LOGIN, Login Processor
Explanation: The system cannot open the current input device and cannot
perform the login. This message is usually accompanied by a VAX RMS
message indicating the reason for the failure.
User Action: Take corrective action based on the VAX RMS message, and
repeat the login procedure, if possible.
LOGIN - error opening primary output file SYS$OUTPUT
Facility: LOGIN, Login Processor
Explanation: The system cannot open the current output device and cannot
perform the login. This message is usually accompanied by a VAX RMS
message indicating the reason for the failure.
User Action: Take corrective action based on the VAX RMS message, and
repeat the login procedure, if possible.

2-299

Messages

LOGIN - error protecting command interpreter pages
Facility: LOGIN, Login Processor
Explanation: An error occurred when you tried to write-protect the CLI code.
User Action: Try the operation again later.
LOGIN - error protecting command interpreter tables pages
Facility: LOGIN, Login Processor
Explanation: An error occurred when the system tried to write-protect the
command interpreter table pages.
User Action: Try again. If the error reoccurs, report it to your system
manager.
LOGIN - error reading command input
Facility: LOGIN, Login Processor
Explanation: An error occurred during the entry of the command; for
example, the timeout period following the prompt for user name or password
expired before you entered the responses.
User Action: Repeat the login procedure.
LOGIN - fatal job controller interaction problem
Facility: LOGIN, Login Processor
Explanation: An internal error occurred in the job controller during the login;
the login cannot be performed.
User Action: Repeat the login procedure. If the failure persists, notify the
system operator or manager of the problem.
LOGIN - invalid password
Facility: LOGIN, Login Processor
Explanation: The specified password is incorrect. This message is not
displayed to the user; it is written to the system accounting and security
audit records. The message displayed to the user is: "User authorization
failure."
User Action: None.
LOGIN - invalid SYS$INPUT for interactive login
Facility: LOGIN, Login Processor
Explanation: SYS$INPUT is a logical name for the input from a process to
the system. When you use the system interactively, SYS$INPUT is assigned
to your terminal by default. The system then acts upon the input it receives
from your terminal. During your process, you can redefine SYS$INPUT to a
data file; the system will then read input from the file. However, you cannot
initiate an interactive process while SYS$INPUT is defined as a file. Filestructured storage devices are not permitted as SYS$INPUT for interactive
processes. The purpose of this restriction is to prevent LOGIN from reading a
username and password from a file.
User Action: Use a non-file-structured device as SYS$INPUT for an
interactive process.

2-300

Messages

LOGIN - licensed number of system users exceeded
Facility: LOGIN, Login Processor
Explanation: The maximum number of interactive users for which your
system is licensed have already logged in. Further logins are currently
disabled.
User Action: Log in after another user has logged off. If the maximum
number of users is exceeded frequently, ask your system manager whether
the system's license can be upgraded.
LOGIN - logins are currently disabled - try again later
Facility: LOGIN, Login Processor
Explanation: Logins are currently disabled.
User Action: Do not attempt to log in at this time. Try again later.
LOGIN - maximum number of users exceeded - try again later
Facility: LOGIN, Login Processor
Explanation: The installation-defined maximum number of users has been
reached.
User Action: Wait and try to log in later, after other users have logged out.
LOGIN - network user validation error
Facility: LOGIN, Login Processor
Explanation: A network login request was not validated.
User Action: This message is written to the system accounting log file, and is
not displayed on the terminal.
LOGIN - no such user
Facility: LOGIN, Login Processor
Explanation: The specified username does not exist. This message is not
displayed to the user; it is written to the system accounting and security audit
records. The message displayed to the user is: "User authorization failure."
User Action: None.
LOGIN - protocol error with job controller
Facility: LOGIN, Login Processor
Explanation: A system error occurred during the login procedure.
User Action: Submit a Software Performance Report.
LOGIN - qualifier not allowed in captive accounts
Facility: LOGIN, Login Processor
Explanation: You attempted to use qualifiers (for example, /CLI or /DISK)
on an account logging in that is a captive account. If the account logging in is
a captive account, no qualifiers may be changed.
User Action: Retry without specifying qualifiers.

2-301

Messages

LOGIN - system password timeout
Facility: LOGIN, Login Processor
Explanation: A user failed to correctly enter the system password within
the allotted time period (as defined by the SYSGEN parameter LGI_PWD_
TMO). This message is not displayed to the user; it is written to the system
accounting and security audit records. The user does not receive a message
display when this error occurs.
User Action: None.
LOGIN - unrecognized qualifier keyword
Facility: LOGIN, Login Processor
Explanation: An invalid qualifier was specified on the LOGIN command line.
User Action: Verify the command line you entered and repeat the login
procedure.
LOGIN - user authorization failure
Facility: LOGIN, Login Processor
Explanation: You incorrectly entered your user name, your password, or
both.
User Action: Repeat the login procedure.
LOGIN - value required on qualifier
Facility: LOGIN, Login Processor
Explanation: You specified a qualifier without a value.
User Action: Verify the command line you entered; specify a value and
repeat the login procedure.
LOGIN - you are at maximum allowed processes for your account name
Facility: LOGIN, Login Processor
Explanation: No more processes may be logged in under this account.
User Action: Wait until another process logged in under this account has
logged out.
LOGIN - you are at maximum processes for your user name
Facility: LOGIN, Login Processor
Explanation: No more processes may be logged in under this user name.
User Action: Wait until another process using this user name has logged out
and retry.
LOGIN - you are not authorized to do reconnections
Facility: LOGIN, Login Processor
Explanation: You are not authorized to reconnect to disconnected processes.
User Action: Log in again without specifying the /CONNECT qualifier after
your username.

2-302

Messages

LOGIN - you are not authorized to log in at this time
Facility: LOGIN, Login Processor
Explanation: At the present time, you are restricted from the class of login
you are attempting. The login classes are: LOCAL, DIALUP, REMOTE,
NETWORK, and BATCH. The system manager can restrict your use of each
login class at specific times.
User Action: If possible, try a different login class. For example, if you are
currently restricted from BATCH logins, try an interactive class (LOCAL,
REMOTE, or DIALUP). If you are currently restricted from all login classes,
you cannot log in until you are permitted to use the system. You may
also want to ask your system manager about the login restrictions for your
account.
LOGIN - you are not authorized to log in from this source
Facility: LOGIN, Login Processor
Explanation: You do not have authorization for the login class you are
attempting from the current source. The login classes are: LOCAL, DIALUP,
REMOTE, NETWORK and BATCH. The system manager can restrict your use
of each login class at specific times.
User Action: If possible, try a different login class. For example, if you are
currently restricted from BATCH logins, try an interactive class (LOCAL,
REMOTE, or DIALUP). If you are currently restricted from all login classes,
you cannot log in until you are permitted to use the system. You may
also want to ask your system manager about the login restrictions for your
account.
LOGIN - you are not authorized to log in today
Facility: LOGIN, Login Processor
Explanation: You are restricted from the class of login you have attempted
today. The system manager can restrict your use of a login class on specific
days.
User Action: If possible, try a different login class. For example, if you
are restricted from BATCH logins today, try an interactive class (LOCAL,
REMOTE, or DIALUP). If you are restricted from all classes of logins today,
you cannot log in until you are permitted to use the system. You may
also want to ask your system manager about the login restrictions for your
account.
LOGIN - you are not authorized to login at this time
Facility: LOGIN, Login Processor
Explanation: You do not have authorization to log in at this time.
User Action: Wait and retry later.
LOGIN - you are not authorized to login on a dial in line today
Facility: LOGIN, Login Processor
Explanation: You are allowed to log in only on a terminal that is not using a
dial in line.
User Action: Log in on a terminal that is not using a dial in line.

2—303

Messages

LOGIN - you are not authorized to login via set host today
Facility: LOGIN, Login Processor
Explanation: You may not use the DCL command SET HOST to access this
node today.
User Action: You must log in directly on that machine.
LOGIN - you are not authorized to specify CLI parameters
Facility: LOGIN, Login Processor
Explanation: You do not have authorization to specify an alternate command
language interpreter (CLI), or alternate CLI tables.
User Action: Log in again without specifying the /CLI or /TABLES qualifiers
after your username.
LOGIN - your account has expired - contact your system manager
Facility: LOGIN, Login Processor
Explanation: When creating an account, the system manager can limit it to a
specific time period, after which the account becomes invalid. Your account
has exceeded its time limit.
User Action: Ask your system manager to renew your account.
LOGIN - your password has expired - contact your system manager
Facility: LOGIN, Login Processor
Explanation: Your password is valid for a specific length of time as
determined by your system manager. When a password reaches the end
of its specified time period, it expires and can no longer be used to gain access
to the system. This is a system security feature that forces users to change
their passwords on a regular basis. You should have been receiving advance
messages notifying you when your password would expire.
User Action: Ask your system manager for a new password.
LOGINIT,

logfile initialized by operator 'file-spec7 logfile is 'file-spec'

Facility: OPCOM, Operator Communication
Explanation: A DCL command REPLY/INIT successfully initialized a new
operator communication log file.
User Action: None. This message is informational.
LOGIO,

NICONFIG requires LOG—IO privilege

Facility: CNF, NI Configurator
Explanation: NICONFIG must run with LOG—IO privilege.
User Action: Install NICONFIG with LOG—IO privilege.

2-304

Messages

LOGLINK,

network error creating link to node 'node-name::'

Facility: MAIL, Personal Mail Utility
Explanation: An error occurred when MAIL attempted to use DECnet-VAX
to communicate with another system. This message is usually accompanied
by a system error message indicating the reason for the error.
User Action: Resolve the problem and reenter the command.
LOGNAME,

logical name is too long

Facility: MOUNT, MOUNT Command
Explanation: A logical name contains more than 63 characters.
User Action: Reenter the command; specify a logical name that has fewer
than 63 characters.
LOGOPNM,

open link to event monitor 'sink-name' at 'dd-mm-yy hh:mm:ss.ms'

Facility: EVL, Event Logger
Explanation: The event receiver opened a logical link to the specified event
monitor program. This message displays the name of the program and the
time stamp for the operation.
User Action: None. This is an informational message.
LOGOPNR,

connect accepted by event receiver from node 'node-id' at 'dd-mm-yy
hh:mm:ss.ms'

Facility: EVL, Event Logger
Explanation: The event receiver accepted a link from an event transmitter on
the specified node. This message displays the identification of the node and
the time stamp for the operation.
User Action: None. This is an informational message.
LOGOPNT,

open link to event receiver on node 'node-id' at 'dd-mm-yy
hh:mm:ss.ms'

Facility: EVL, Event Logger
Explanation: The event transmitter attempted to open a logical link to the
event receiver on the specified node. This message displays the identification
of the node and the time stamp for the operation.
User Action: None. This is an informational message.
LOGTIME,

logfile time stamp

Facility: OPCOM, Operator Communication
Explanation: This message, written periodically in the operator's log file,
indicates that the system is functioning properly at the time specified.
User Action: None.

2-305

LOGZERNEG,

logarithm of zero or negative value
user PC location

Facility: MTH, Run-Time Library Math Procedures
Explanation: The LOG or DLOG math procedure was called with a zero or a
negative number. The result returned is the reserved operand, minus zero.
User Action: Locate the call to the library procedure that caused the error,
and correct the argument that was zero or negative.
LONGDST,

unable to include all module names in symbol table

Facility: PATCH, VAX Image File Patch Utility
Explanation: When you initialized its symbol, the image table could not
accommodate all the module names it found.
User Action: To determine which modules were placed in the symbol table,
issue the PATCH command SHOW MODULE. To make room for the new
modules, issue the PATCH command CANCEL MODULE specifying the
module names whose symbols are no longer required. Then reissue the
PATCH command SET MODULE.
LOOKUPERR,

error looking up 'module name' in 'library file-spec'

Facility: LIBRAR, LIBRARY Command
Explanation: The Librarian could not find the requested module in the
MNT, a VAX RMS error occurred, or there was not enough virtual memory
available.
User Action: Reenter the command line specifying an existing module name.
LOSTEXTHDR,

file ('file-id') 'file-name' lost extension file header

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that an extension file header is not in
the extension file header chain of any file.
User Action: None. The file header is rewritten with a deleted header, and
the blocks allocated to the file header are marked free. The /CONFIRM
qualifier is ignored in this action.
LOSTHEADER,

file ('file-id') 'file-name' not found in a directory

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the specified file was not cataloged
in a directory. This error is neither reported nor repaired if any errors
occurred in processing the directories on the volume set.
User Action: None. The file is cataloged in directory [001003]. Optionally, if
the user responded to the /CONFIRM qualifier prompt by typing D, the file
is deleted.

Messages

LOSTSCAN,

due to directory errors, lost files will not be entered

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility encountered errors during the directory scan
that were reported by previous messages. Therefore, lost files will not be
entered in directory [SYSLOST].
User Action: Refer to the suggested user actions for the previously reported
errors, correct the errors, and reenter the Verify Utility command line.
LRL—MISS,

LRL must be specified

Facility: SORT, VAX SORT/MERGE Utility
Explanation: If a record I/O interface subroutine package is selected, the
longest record length (LRL) must be passed to SORT in the call.
User Action: Specify the LRL.
LSTERR,

error generating listing file

Facility: AUTHORIZE, Authorize Utility
Explanation: This message is issued with other messages.
User Action: Take corrective action based on the accompanying messages.
LSTMSG1,

writing listing file

Facility: AUTHORIZE, Authorize Utility
Explanation: This message is informational.
User Action: No user action is required.
LSTMSG2,

listing file SYSUAF.LIS complete

Facility: AUTHORIZE, Authorize Utility
Explanation: This is an informational message.
User Action: No user action is required.
LSTTOTBK,

device 'device' contains a total of 'number' blocks; 'number' defective
block(s) detected

Facility: BAD, Bad Block Locator Utility
Explanation: This informational message details the number of bad blocks.
User Action: None.
LTC,

Line too complicated: 'string'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: There is excessive use of boldface, underlining, overstriking,
and hyphenation on the line.
User Action: Simplify the line.

2-307

Messages

LUNALRFRE,

logical unit number already free

Facility: LIB, Run-Time Library General Procedures
Explanation: A call was made to LIB$GET_LUN to free a logical unit number
that was not allocated.
User Action: Ensure that you use the correct logical unit number in the call
to LIG$GET_LUN.
LUNRESSYS,

logical unit number reserved to system

Facility: LIB, Run-Time Library General Procedures
Explanation: A call was made to LIB$GET_LUN to reserve an invalid logical
unit number. The range for logical unit numbers is 100 to 119.
User Action: Retry the operation specifying a valid logical unit number.
MACHINECHK,

Machine check while in kernel mode

Facility: System Bugcheck
Explanation: The VAX/VMS software detected an irrecoverable hardware
error. Because of the severity of the error, further operation is impossible,
or if it is possible , it may corrupt user data. After all 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: 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 VAX/VMS DCL Dictionary) to recreate the library
from the source code.
MACNAMLNG,

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

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.

2-308

Messages

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

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') 'file-name' invalid map area

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the specified file has a corrupted
map area.
User Action: None.

2-309

MAPCNTZER,

Attempted to generate zero length map pointer

storage map header is bad; volume locked

Facility: MOUNT, MOUNT Command
Explanation: An I/O error was 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, Run-Time Library String Procedures
Explanation: A match was found for the input string that was passed to the
routine.
User Action: None. This is a success status.
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.
User Action: None. This message is informational.
MATQUOMIS,

matching quote is missing

Facility: DEBUG, VAX/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.
User Action: None. EDT stops accepting additional lines when it reaches its
limit.

Messages

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

bad block table overflow

Facility: INIT, INITIALIZE Volume 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 Command 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 - DIF aborted

Facility: DIFF, DIFFERENCES Command
Explanation: The number of differences that have been found exceed 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 was reached.
User Action: None.
MAXDIFEXC,

maximum differences count of 'number' exceeded

Facility: DIFF, DIFFERENCES Command
Explanation: The number of differences that you specified has been found.
User Action: None.

2-311

MAXLAB,

too many volume labels

Facility: MOUNT, MOUNT Command
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.
MAXMAPPEDBUF,

A single buffer can be mapped to at most 'count' window(s)

Facility: 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.
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 VAX/VMS DCL
Dictionary to determine the correct number of parameters for the command.
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 was calculated.
User Action: Reissue 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 was encountered in creating the I/O database
that was larger than the maximum number of units allowed (default = 8).
User Action: Retry the operation using the /MAXUNITS qualifier on the
SYSGEN command CONNECT.

Messages

MAXVALUE,

Maximum value is 'integer'

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

too many volumes in volume set 'device'

Facility: BACKUP, Backup Utility and VERIFY, Verify Utility
Explanation: The volume set count recorded in the home block of relative
volume 1 of an input volume set was 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 back-up media.
MAYNOTINDX,

this mode may not be indexed

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

MBA CBHUNG bit set

invalid multi-block count

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

mailbox is full

Facility: SYSTEM, VAX/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-313

MBTOOSML,

mailbox is too small for request

Facility: SYSTEM, VAX/VMS System Services
Explanation: A write request to a mailbox failed because the message was
larger than the maximum message size specified when the mailbox was
created.
User Action: Verify that the call to the service was 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 Command
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 Command
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, VAX/VMS System Services
Explanation: A hardware machine check has occurred.
User Action: Notify the system manager.
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, VAX/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
LPA11-K, set clock, and start data transfer request.
User Action: Contact a DIGITAL field service representative.
MDBSFCRUPT,

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

Facility: BAD, Bad Block Locator Utility
Explanation: The header information in the redundant MDBSF was
corrupted.
User Action: None. The Bad Block Locator Utility terminates the analysis.

Messages

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 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: None. The Bad Block Locator Utility will attempt to recover
and or rebuild the old MDBSF and SDBSF if the execution context will allow
it. If the context mentioned above precludes that operation, the Bad Block
Locator Utility terminates the analysis.
MDFYERR,

unable to update record

Facility: AUTHORIZE, Authorize Utility
Explanation: This message is issued with other messages.
User Action: Take corrective action based on the accompanying messages.
MDFYMSG,

user record(s) updated

Facility: AUTHORIZE, Authorize Utility
Explanation: This message is informational.
User Action: No user action is required.
MEDOFL,

medium is offline

Facility: SYSTEM, VAX/VMS System Services
Explanation: An I/O request cannot be satisfied because the device specified
is not online 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 was 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 was detected and at least one conditional DSR
command (.IF/.IFNOT) is not legally terminated.
User Action: Insert the missing conditional command(s). Check to see that
DSR commands .IF/.ENDIF are matched within .REQUIRE files.

2-315

Messages

MEMBUG,

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

Facility: PATCH, VAX Image File 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 'number7, 'address7, 'number'

Facility: LINK, VAX Linker
Explanation: There is a problem with the linker.
User Action: Submit a Software Performance Report.
MEMFUL,

insufficient virtual address space to complete this link

Facility: LINK, VAX Linker
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.
MERGE,

'n' record(s) to be merged

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

Number illegal or malformed: 'string'

Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: A plus sign ( + ) or a minus sign (-) was used alone, instead of
+n or -n.
User Action: Insert the n value.
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.

2-316

Messages

MFYNULPGFL,

FREWSLE - no backing store, page not modified

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

Facility: LIBRAR, LIBRARY Command
Explanation: The specified module has an illegally formatted header.
User Action: Compress the library before reentering the command line.
MINVALUE,

Minimum value is 'integer'

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

missing END statement

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: The Termtable compiler expected an END statement to
terminate the current terminal definition and this END statement was missing.
User Action: Check your terminal definitions.
MISFILSPE,

missing file specification in REQUIRE statement

Facility: SMG, Run-Time Library Screen Management Procedures
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 xxx

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

2-317

Messages

MISMODBEG,

missing Module-Begin record in DST, compiler error

Facility: DEBUG, VAX/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 xxx, compiler error

Facility: DEBUG, VAX/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, Run-Time Library Screen Management Procedures
Explanation: The Termtable compiler expected TERMTABLE.TXT to begin
with a terminal definition NAME statement or a REQUIRE statement.
Something else was encountered.
User Action: Check your TERMTABLE.TXT.
MISREQPAR,

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 was 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.
MISSINGQUOTE,

Missing quote on line 'integer'

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

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 PI, P2,_
User Action: Rename the parameters consecutively.

2-318

Messages

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, VAX SORT/MERGE Utility
Explanation: You have omitted a required argument.
User Action: Identify which argument is missing and specify it.
MISSPASS,

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, VAX Image File Patch Utility
Explanation: You did not use matching quotation marks or apostrophes to
enclose an argument.
User Action: None. 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.
MISTERNAM,

definition must begin with a terminal name

Facility: SMG, Run-Time Library Screen Management Procedures
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,

Expression involves mixed data types

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

2-319

Messages

MKD,

ACP could not mark file for deletion

Facility: RMS, VAX Record Management Services
Explanation: The file system ACP cannot delete the file. This message is
associated with a status code returned from a file system ACP QIO requests
made by VAX RMS.
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.
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 was modified. This
message is displayed when you specify the /LOG qualifier.
User Action: None. The operation was successful.
MODIFYERR,

modify error code of 'xx' on file 'file-spec'

Facility: PATCH, VAX Image File Patch Utility
Explanation: A VAX RMS $MODIFY request failed because of the error code,
represented as 'xx'.
User Action: Correct the error (represented as xx) and retry the request.
MODNAM,

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

Facility: LINK, VAX Linker
Explanation: A module contained a header record with an illegal module
name.
User Action: Submit a Software Performance Report on the appropriate
language processor.

2-320

Messages

MODNAMLNG,

illegal module name 'module name' of 'nnn' characters in
'library file-spec'

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

insufficient symbol table space to add module 'module-name'

Facility: PATCH, VAX Image File 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, issue 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 'module name' not found in record
'record number', 0
Facility: PSM, Print Symbiont
Explanation: This status is returned by a print symbiont library input routine
indicating the specified library module was 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.
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.

Messages

MODRELNBAK,

No backing store address for modified page

MOUNT new relative volume nn (volume label) on 'devicename'

Facility: MOUNT, MOUNT Command
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 Command
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 Command
Explanation: This is an informational message that verifies a request.
User Action: No action is necessary.
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.
MOUNTF11,

'file-spec' must be mounted Files-11

Facility: BACKUP, Backup Utility
Explanation: The specified volume was mounted with the /FOREIGN
qualifier. However, for the given operation, the volume must be mounted
without the /FOREIGN qualifier.
User Action: Reevaluate the operation, checking that the correct I/O devices
have been specified and that the /SAVE—SET, /PHYSICAL, and /IMAGE
qualifiers are properly used. Then, if appropriate, mount the specified volume
without the /FOREIGN qualifier, and reenter the command.

2—322

Messages

MOUNTFOR,

'file-spec7 must be mounted foreign

Facility: BACKUP, Backup Utility
Explanation: The specified volume was mounted without the /FOREIGN
qualifier. However, for the given operation, the volume must be mounted
with the /FOREIGN qualifier.
User Action: Reevaluate the operation, checking that the correct I/O devices
have been specified and that the /SAVE_SET, /PHYSICAL, and /IMAGE
qualifiers are properly used. Then, if appropriate, mount the specified volume
with the /FOREIGN qualifier, and reenter the command.
MOUVOL,

MOUNT relative volume 'nn' on 'device-name'

Facility: MOUNT, MOUNT Command
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.
MPASYNCWRT,

Secondary detected asynchronous write memory failure

Secondary detected bad machine check code

2-323

Messages

MPCHMONIS,

Secondary detected change mode instruction while on interrupt
stack

Secondary detected CHM vector bits 1:0 not 0

Secondary detected double error halt restart

Facility: System Bugcheck
Explanation: The VAX/VMS software detected an irrecoverable hardware
error in the VAX-11/782 attached processor. Because of the severity of the
error, further operation is impossible, or if it is possible, it may 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 1.
User Action: Thoroughly test all system hardware components. If no
hardware errors are located and if the problem persists, submit a Software
Performance Report. The SPR should describe the conditions leading to
this 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 that produces
the save set included with the SPR.)

2-324

Messages

MPERRHALT,

Secondary detected halt with error interrupt pending

Secondary detected halt instruction restart

Secondary detected illegal interrupt or exception vector restart

Secondary detected interrupt stack invalid restart

2—325

MPKNLSTKNV,

Secondary detected kernel stack not valid

Secondary machine check while in kernel mode

Secondary detected no user WCS halt restart

Secondary detected SCB physical read error halt

Messages

MPUNEXPINT,

Secondary detected unexpected interrupt or exception

Secondary detected unknown restart code

Modified page writer failed to allocate I/O Packet

Missing or improperly delimited quoted strings: 'string7

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.

Messages

MRC,

Another n crossed margin or bad right indent attempt(s) 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:
MRG,

Check the margin and indent settings.

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 illegal indent has been specified.
User Action: Check the margin and indent settings.

MRGGTMTCH,

value of V 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.
MRN,

invalid maximum record number or record number exceeds MRN

Facility: RMS, VAX Record Management Services
Explanation: An incorrect record number was specified in one of the
following ways:
1

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

2 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
was created.
User Action: Verify that the call to the VAX RMS service was coded correctly.
Note the condition. Modify the source program, if necessary, to detect and
respond to the condition.
MRS,

invalid maximum record size
Facility: RMS, VAX 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 was less than 18.
User Action: Verify that the call to the VAX RMS service was coded correctly.

2-328

Messages

MRS,

Missing one or more .RESTORE command(s) 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 Facility
Explanation: The code for the MSCP Server was not loaded at system
generation.
User Action: Make sure the MSCP Server code is loaded before trying to
issue the SET DEVICE command or the SHOW DEVICE command.
MSGCMAIIF,

missing comma in .IIF statement

Facility: MACRO, VAX Macro Assembler
Explanation: The condition was 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, VAX/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.
MTLBLLONG,

label specified for 'device' is longer than 6 characters

Facility: INIT, INITIALIZE Volume 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, VAX/VMS System Services
Explanation: The label specified for a magnetic tape volume has more than
six characters.
MTLBLNONA,

label specified for 'device' contains non-ANSI "a" characters

Facility: INIT, INITIALIZE Volume Command
Explanation: The operator used invalid ANSI "a" character(s) 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—329

MTXCNTNONZ,

Mutex count nonzero at system service exit

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

Facility: LINK, VAX Linker
Explanation: A cluster was 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
'file-name'

Facility: LINK, VAX Linker
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 was 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
'file-name'

Facility: LINK, VAX Linker
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, 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.

Messages

MULPSC,

conflicting attributes for psect 'psect-name7 in module 'module-name7
file 'file-name7

Facility: LINK, VAX Linker
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, 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 'string7 defined in shareable image 'image name7 is multiply
defined in shareable image 'image name7

Facility: LINK, VAX Linker
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 Sharable Images, refer to the
Linker Utility in the VAX/VMS Linker Reference Manual which explains how
to link COMMON areas.
MULTALLOC,

file (7file-id7) 'file-name7 multiply allocated blocks VBN 7n7 to 7n7
LBN 7n7 to 7n7, RVN 7n7

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:
•

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

•

Delete the version of each file that was 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.

2—331

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, VAX Image File 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, issue the PATCH Utility command
UPDATE.
MULTEXTHDR,

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

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the specified extension file header
was in the extension header chain of more than one file.
User Action: None.
MULTFR,

multiply defined transfer address in module 'module-name7 file 'file¬
name'

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

There is more than one name matching, all are returned

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

multiple successive operators in expression

Facility: PATCH, VAX Image File Patch Utility or DEBUG, VAX/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.

Messages

MULTRMS,

multiple RMS vectors specified

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

String must be 1 character long

Facility: 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, VAX/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 and time'. Mount verification aborted for device 'devname'

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

'date and time'. Mount verification completed for device
'devname'

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

connect error on NETUAF.DAT

Facility: AUTHORIZE, Authorize Utility
Explanation: This message is issued with other messages.
User Action: Take corrective action based on the accompanying messages.
NAM,

invalid NAM block or NAM block not accessible

Facility: RMS, VAX Record Management Services
Explanation: The VAX 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 VAX RMS service was coded correctly
and that the NAM block inadvertently modified during execution of the
program.

2-333

Messages

NAMETOOBIG,

username too long

Facility: AUTHORIZE, Authorize Utility
Explanation: The user name you specified was longer than 12 characters.
User Action: Enter a user name no longer than 12 characters.
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 VAX 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 reissue 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.
NARG,

wrong number of arguments

Facility: CONVERT, Convert Utility
Explanation: You specified an incorrect number of arguments in a call to
CONV$PASS—FILES, CONV$PASS_OPTIONS, or CONV$CONVERT.
User Action: Refer to the VAX/VMS System Services Reference Manual for
details about calling these routines.
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.

NEEDFILENAME,

Enter a file name to write buffer 'buffer name'; else press
RETURN:

Facility: VAX Text Processing Utility
Explanation: You have 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, VAX/VMS Debugger
Explanation: The command entered was not complete. A required part of
the command was omitted.
User Action: Reenter the complete command.

2-334

Messages

NEEDTERMS,

You must specify some word terminators for FILL

Facility: 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 be an RHS of assignment statement at line
'integer'

Facility: 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 (RHS) 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, VAX Record Management Services
Explanation: A VAX RMS $PUT request was attempted for a sequential file
that was not currently positioned at the end of the file.
User Action: Verify that the call to the VAX RMS service was programmed
correctly. Modify your program, if necessary, to detect and respond to the
condition.

NEGATED,

entity explicitly negated in command string

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

Shared memory control block negative refcnt

2-335

NEGSTRLEN,

negative string length

Facility: STR, Run-Time Library String Procedures
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 was used.
User Action: The user should verify that all parameters containing string
lengths do not contain negative numbers.
NESTERROR,

Nesting level exceeded at line 'integer'

Facility: 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 file-spec'

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

network operation failed at remote node; DAP code = 'xxxxxxxx'
Facility: RMS, VAX Record Management Services
Explanation: The file system of the target node could not perform the
requested operation, and VAX RMS was unable to map the Data Access
Protocol status code into a more specific VAX 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 VAX/VMS System Services Reference Manual for the
meaning of this system service error, and correct the problem.

Messages

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 VAX/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.
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 was 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 issued 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, VAX 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 of some form occurred. Information
accompanying this message explains the reason for this error.
User Action: When you enter the next command, DECnet-VAX automatically
creates a new link to NML.
NETIOERR,

network I/O error

Facility: MAIL, Personal Mail Utility
Explanation: An I/O error occurred while transmitting a MAIL message with
DECnet-VAX. This message is issued with an accompanying message.
User Action: Take corrective action based on the accompanying message.

2-337

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 in order to
declare itself as a known image to be eligible for multiple connects.
User Action: Install NICONFIG with NETMBX privilege.
NETNOBUF,

NETACP - buffer allocation failure

NETACP - no state transition

NETACP - no receive I/O packet

2-338

Messages

NETSYSSRV,

NETACP - unexpected system service failure

NETACP - transaction count zero

failed to get UCB for network device

Facility: PSI, VAX Packetnet System Interface
Explanation: VAX PSI could not find the UCB for NWAO:.
User Action: Submit a Software Performance Report.
NEWFILES,

'nnn' files created

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

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 'file-spec' 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 newly created queue file.

2-339

Messages

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.
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 was specified.
User Action: Reissue the command with a valid UNIBUS adapter.
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.

NIC,

Another n negative indent(s) detected and accumulated. Now being
reported.
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: A specific number (n) of negative indents (to the left of .LMO)
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: Correct the indent or left margin setting.

NMF,

no more files found

Facility: RMS, VAX 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 VAX RMS $SEARCH or $ REMOVE operation.
User Action: Note the condition. Modify the source program, if necessary, to
detect and respond to the condition.
NMLRSP,

listener response - 'text'

Facility: NCP, Network Control Program
Explanation: The message line above 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

2-340

Messages

in the response). The third line contains additional error text (if there is text
in the response). Some of the specific NML responses are shown below.
User Action: Take corrective action based on the first line of the message.
NMLRSP,

listener response - Component in wrong state

Facility: NCP, Network Control Program
Explanation: A component was in an unacceptable state. For example, a
down-line load was attempted over a line with OFF status.
User Action: Check the status of the component and reenter your command.
NMLRSP,

listener response - File I/O error, 'name of file'

Facility: NCP, Network Control Program
Explanation: An error has occurred during file input or output, for example,
a system image file could not be read. The message should be accompanied
by a VAX RMS message identifying the reason for the error (such as a
protection violation if the file is protected against read access). The 'name of
file' identifies the file that caused the error.
User Action: Take corrective action based on the RMS message.
NMLRSP,

listener response - File open error, 'name of file'

Facility: NCP, Network Control Program
Explanation: The file to be accessed as a result of your command could not
be opened. The message should be accompanied by a VAX RMS message
specifying why the file could not be opened. (For example, the file could not
be found). The 'name of file ' identifies the file that could not be opened, for
example, the permanent or volatile database file.
User Action: Take corrective action based on the RMS message. For instance,
if a file cannot be found determine whether it exists and whether it is located
in the proper directory.
NMLRSP,

listener response - Incompatible management version

Facility: NCP, Network Control Program
Explanation: The requested function cannot be performed because of
incompatibility between the software versions at the command source and
command destination.
User Action: None.
NMLRSP,

listener response - Invalid file contents, 'name of file'

Facility: NCP, Network Control Program
Explanation: The contents of the file to be accessed by your command
are invalid. The message should be accompanied by a VAX RMS message
identifying the reason why the file contents are invalid. The 'name of file'
identifies which file has invalid contents.
User Action: Determine why the file contents are invalid and take corrective
action based on the RMS message.

2-341

NMLRSP,

listener response - Invalid identification

Facility: NCP, Network Control Program
Explanation: The format of a component identifier was incorrect, or you used
the KNOWN component keyword incorrectly.
User Action: Check the syntax rules for component identifiers and reenter
your command with the correct identifier.
NMLRSP,

listener response - Invalid parameter value

Facility: NCP, Network Control Program
Explanation: The specified value for a parameter is invalid; for example, a
line identifier or a load address is incorrect.
User Action: Check the rules for specifying the parameter value and reenter
your command.
NMLRSP,

listener response - Line communication error

Facility: NCP, Network Control Program
Explanation: The requested line is unavailable, or an error occurred during
transmission to the line. For example, this error occurs if the line identifier is
incorrect.
User Action: Make sure that you are correctly identifying the line, and that
the line characteristics are set properly.
NMLRSP,

listener response - Line protocol error

Facility: NCP, Network Control Program
Explanation: Indicates an invalid line protocol message or operation during
direct line access. In the case of a line loop test, an error was detected during
message comparison that should have been detected by the line protocol.
User Action: Make sure that the line protocol and line characteristics are set
properly.
NMLRSP,

listener response - 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.
NMLRSP,

listener response - Mirror 'error'

Facility: NCP, Network Control Program
Explanation: This error occurs if the connection to a mirror loopback fails
or if the connection is made but is subsequently disconnected. 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
failure of the connection. Some possible reasons for connection failure are an
invalid or unrecognizable node name, a lack of network resources, or a busy
or unreachable node.
User Action: If the error occurred because of an incorrect node identifier,
correct the identifier and reenter your command. If network resources are

Messages

currently insufficient or if the node is inaccessible, reenter your command
when the network and node become available.
NMLRSP,

listener response - Oversized management command message

Facility: NCP, Network Control Program
Explanation: A message from the network information and control exchange
(NICE) was too long for the network management listener to receive.
User Action: Check the NICE protocol governing message size. The NICE
protocol is described in the Network Management Functional Specification.
NMLRSP,

listener response - Parameter 'error7

Facility: NCP, Network Control Program
Explanation: A parameter in your command was inapplicable, missing, or
had too long a value. The 'error' part of the message identifies the type of
error and the type of parameter.
User Action: Review the command description to determine the correct
parameters for the specified component and reenter your command.
NMLRSP,

listener response - Privilege violation

Facility: NCP, Network Control Program
Explanation: You do not have the privilege required 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, LIST and SET ALL commands, you must have system
privilege (SYSPRV), or you must be able to access files with system protection
in some other way. The remaining NCP commands require the operator
privilege (OPER).
User Action: None, unless the network manager can grant you the required
privilege.
NMLRSP,

listener response - Unrecognized 'text'

Facility: NCP, Network Control Program
Explanation: A parameter or component that you specified in your command
is incorrect and therefore unrecognizable by the network management
software. The 'text' part of the message identifies the unrecognizable
parameter or component.
User Action: Check the command description and reenter your command
with the correct parameter or component.
NMLRSP,

listener response - Unrecognized function or option

Facility: NCP, Network Control Program
Explanation: Either the function code or the option field requested a
capability that was unrecognized by the local network management function.
User Action: Make sure you are using the correct code for the function you
are requesting, or that you are specifying a valid option.

2-343

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 device currently selected
Facility: DISKQUOTA, Diskquota Utility
Explanation: This message is issued with other messages.
User Action: Enter another USE command specifying valid device name.
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: None. 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.
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 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 type 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 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.

Messages

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

no write access to virtual address nnn

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

cannot access image section

Facility: PATCH, VAX Image File 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, VAX/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.
NOACPCHAN,

Failure to assign ACP channel

2—345

NOACPDEV,

device named by /PROCESSOR:SAME has no ACP

Facility: MOUNT, MOUNT Command
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

no adapter (nexus) number specified

Facility: SYSGEN, System Generation Utility
Explanation: The /ADAPTER qualifier must be specified in the SYSGEN
command CONNECT.
User Action: Reissue the command specifying the /ADAPTER qualifier.
NOALLOC,

ignoring /ALLOCATION, not valid for output volume

Facility: EXCHANGE, Exchange Utility
Explanation: The EXCHANGE utility ignored a /ALLOCATION qualifier
which was not meaningful.
User Action: Leave the allocation off, it is not needed.
NO ALLSPOOL,

operation requires ALLSPOOL privilege

Facility: SYSTEM, VAX/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.

Messages

NOALTPRI,

operation requires ALTPRI privilege

Facility: SYSTEM, VAX/VMS System Services
Explanation: A command or program requested a system function that
requires ALTPRI 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.
NO ANGLE,

unmatched angle brackets in expression

Facility: PATCH, VAX Image File Patch Utility and DEBUG, VAX/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.
NO ANGLE,

unmatched angle brackets in expression

ACP queue header not found

Facility: SYSTEM, VAX/VMS System Services
Explanation: When an ACP file started, it was 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.

2-347

NOAQBACP,

No AQB for ACP

missing arguments for substitution

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: You requested a capability that requires user arguments such as
a 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.
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 reissue the command.
NO AVAIL,

field 'field-name' not available in this report

Facility: SHOW, SHOW Facility
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 was performed on a file marked NOBACKUP.
Therefore, the file header only is saved, no data is transferred to the save set.
User Action: Set file so that it can be backed up with SET FILE/BACKUP
command or add the /IGNORE=NOBACKUP qualifier to the BACKUP
command line.
NOBADDATA,

bad block data not found on volume

Facility: INIT, INITIALIZE Volume Command
Explanation: No bad block information recorded in the Software or
Manufacturer's Bad Block areas.
User Action: None. You have a good disk.

Messages

NOBADDATA,

bad data block not found on 'device'

Facility: INIT, INITIALIZE Volume 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.
User Action: None. The utility will create a new SDBSF in nonlast track
format.
NOBITMAP,

no valid storage bit map found on 'device'

Facility: BACKUP, Backup Utility
Explanation: The Backup Utility encountered an error during an attempt to
search for the storage bit map file, [000000]BITMAP.SYS;1, 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.
NOBRANCH,

instruction requires branch-type operand

Facility: PATCH, VAX Image File Patch Utility and DEBUG, VAX/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.
NOBREAKS,

no breakpoints are set

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

2-349

NOBUFPCKT,

Required buffer packet not present

operation requires BUGCHK privilege

Facility: SYSTEM, VAX/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

operation requires BYPASS privilege

Facility: SYSTEM, VAX/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.

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

Insufficient virtual memory to allocate a new cache

Facility: 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 reoccurs, 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 and DEBUG, VAX/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.
User Action: None. This message is informational.
NOCALLUSER,

Could not find a routine for CALL—USER to invoke

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

2-351

Messages

NO—CHADIS,

no change in virtual display

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: The requested number of columns to change was 0, so nothing
in the virtual display was changed.
User Action: None.
NOCHANGE,

any modifications to ACL ignored

Facility: ACLEDIT, Access Control List Editor
Explanation: The editing session was aborted, with no changes made to the
object's ACL.
User Action: None.
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: Reissue the MONITOR request, specifying only class(es) 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 was executed with the Monitor Utility
command, but no information was provided to identify which classes to
monitor.
User Action: Reissue the Monitor Utility command, specifying at least one
class name parameter.
NOCLI,

no CLI present to perform function

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

2-352

Messages

NOCLI,

no command interpreter

Facility: OPCOM, Operator Communication
Explanation: A system image was requested for execution in a process that
does not have a command interpreter. This message is associated with a
status code returned from a system service 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.
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
was entered or a valid file was entered but then became corrupted.
User Action: Do not use this file again with the SET Command.
NOCMDMEM,

no command memory has been allocated

Facility: Shared by several facilities
Explanation: If returned from a DR32 support routine call, either command
memory was 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 was never allocated, make sure the XF$SETUP
support routine was called before trying to access command packets.
NOCMDPROC,

error opening captive command procedure - access denied

Facility: CLI, Command Language Interpreter (DCL)
Explanation: When you attempted to log in, you were logged out because
you have a captive account and DCL could not find your login.com file.
User Action: See your system manager.
NOCMEXEC,

operation requires CMEXEC privilege

Facility: SYSTEM, VAX/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.

2-353

Messages

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, VAX/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.
NOCOMBINE,

cannot combine lines across ACE boundaries

Facility: ACLEDIT, Access Control List Editor
Explanation: An attempt was made to combine two ACEs into a single ACE,
for example, by issuing a rubout character when at the first character of an
ACE.
NOCOMD,

no command on line - reenter with alphabetic first character

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

/INPUT files do not have a common file structure level

Facility: MONITOR, Monitor Utility
Explanation: A list of files was 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 multi-file 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: Reissue the MONITOR request specifying an /INPUT file list
consisting of files that have the same file structure level.

2-354

Messages

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

non-contiguous image file being written

Facility: PATCH, VAX Image File 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 following DCL command:
$ COPY/CONTIGUOUS input-file-spec output-file-spec

NOCOPBAD,

cannot create .BAD file with wildcard names

Facility: EXCHANGE, Exchange Utility
Explanation: The EXCHANGE utility could not create an RT-11 file with an
file type of .BAD because the input or output filenames contained a wildcard.
User Action: Since the file type of .BAD is given special meaning by RT-11,
you probably want to chose 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 an
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 chose 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 was write-locked.
User Action: Remount the output volume with write access, then reenter the
command.

2—355

Messages

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 was 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 was 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.
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 filetype 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: 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.

2-356

Messages

NOCURLOC,

current location not defined

Facility: DEBUG, VAX/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: VAX Text Processing Utility
Explanation: You tried to type or 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, VAX 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 VAX RMS service was coded correctly.
NODECODE,

cannot decode instruction

Facility: PATCH, VAX Image File Patch Utility, DEBUG, VAX/VMS
Debugger
Explanation: Either the Patch Utility or the VAX/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.
NODEFAULT,

directory default ACEs not allowed

Facility: ACLEDIT, Access Control List Editor
Explanation: The ACE currently being entered has the DEFAULT option set,
and the object whose ACL is being edited is not a directory file.
User Action: Remove the DEFAULT option before entering the ACE.
NODEFINITION,

Key 'keyname' currently has no definition

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

2-357

Messages

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: No user action is required.
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.
NODELETE,

ACE cannot be deleted

Facility: ACLEDIT, Access Control List Editor
Explanation: An attempt was made to delete an ACE that cannnot be deleted
by the ACL editor.
User Action: This is usually caused by attempting to delete an ACE of
an unknown format, one that is application dependent (indicated by the
HIDDEN option), or an unsupported ACE type.
NODELIMTR,

missing or invalid instruction operand delimiter

Facility: DEBUG, VAX/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 was write-locked.
User Action: Remount the output volume with write access, then reenter the
command.
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.

2—358

Messages

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: Issue 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.
NODESTQUE,

no such destination queue

Facility: SYSTEM, VAX/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.
NODETACH,

operation requires DETACH privilege

Facility: SYSTEM, VAX/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.
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.
NODEVADAP,

no devices on adapter 'n'

Facility: SYSGEN, System Generation Utility
Explanation: A SHOW/CONFIGURATION operation was tried on an
adapter that has no devices.
User Action: Reissue the command specifying an adapter that has devices.

2-359

Messages

NODEVAVL,

device 'device' is not available for mounting, [optional comment]

Facility: MOUNT, MOUNT Command
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, VAX/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'

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 was broken. This error can
occur if the remote node shuts down.
User Action: Determine why the remote node was removed from the
network. When the remote node is accessible again, reenter the MONITOR
command.
NODIAGNOSE,

operation requires DIAGNOSE privilege

Facility: SYSTEM, VAX/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.
NODI ALIN,

you are not authorized to login on a dial in line today

Facility: LOGIN, Login Processor
Explanation: The information in the user authorization file indicates that you
are not allowed to log in from a dial-in terminal.
User Action: Do not use a dial-in terminal.

2-360

Messages

NODIRLISM,

no source directory list in effect

Facility: DEBUG, VAX/VMS Debugger
Explanation: The DEBUG command CANCEL SOURCE/MODULE=mmm
failed because there is no source directory search list in effect for module
mmm.
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, VAX/VMS Debugger
Explanation: The DEBUG command CANCEL SOURCE had no effect
because no source directory search list is currently in effect.
User Action: None. This message is informational.
NODISKQUOTA,

no disk quota entry for this UIC

Facility: SYSTEM, VAX/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.
NODSTQUE,

no such destination queue

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

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

Facility: SORT, VAX 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.
NOENCODE,

cannot encode instruction 'instr'

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

2-361

Messages

NOENCODE,

cannot encode instruction 7n7

Facility: PATCH, VAX Image File 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.
NOEND,

string beginning with xxx is missing and delimiter y

Facility: DEBUG, VAX/VMS Debugger
Explanation: A DEPOSIT command specified an ASCII string or
INSTRUCTION string beginning with characters xxx 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: 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: VAX Text Processing Utility
Explanation: The built-in procedures CURRENT-LINE and CURRENTCHARACTER 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 'module name7 is not terminated with EOM record in 'library
file-spec7

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,

module 'module7 does not contain end of module records

Facility: LIB, Run-Time Library General Procedures
Explanation: The Run-Time Library encountered severe format errors in the
shareable you are trying to call.
User Action: Issue the ANALYZE/IMAGE command specifying the image in
question. If the errors indicate an operating system internal error, submit a
Software Performance Report.

2-362

Messages

NOEOM,

no end of module record found in module 'module-name' file 'file¬
name'

Facility: LINK, VAX Linker
Explanation: A module did not contain an end-of-module record.
User Action: Submit a Software Performance Report on the appropriate
language compiler.
NOEPM,

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

Facility: LINK, VAX Linker
Explanation: An entry mask of an undefined symbol was 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, VAX/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.
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.
NOFIELD,

xxx is not a field in this record

Facility: DEBUG, VAX/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: SEARCF1, SEARCH Command
Explanation: The DCL command SEARCH was 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.

2-363

Messages

NOFILEACCESS,

Unable to access file 'name7

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

no file identification was specified

Facility: PSM, Print Symbiont
Explanation: This status is returned indicating no file identification number
was 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 I/O

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

no files selected from 'file-spec'

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$OPEN routine, the FNS argument was invalid or
not provided or the NAM block was not filled in.
User Action: Correct the problem before calling the routine.
NOFILPURG,

no files purged for 'file-spec'

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-364

Messages

NOFREE,

no free storage available

Facility: PATCH, VAX Image File Patch Utility or DEBUG, VAX/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.
NOFREE,

no free storage available

some or all global symbols not accessible

Facility: PATCH, VAX Image File Patch Utility
Explanation: When you initialized PATCH, either no global symbol
information was available to PATCH or the symbol table was 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 'file-spec'

Facility: INSTALL, Install Utility
Explanation: When creating a known file entry for a shareable image,
INSTALL was not able to create global sections for that image. The image
was not shareable.
NOGLOBALS,

some or all global symbols not accessible

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

2-365

Messages

NOGROUP,

operation requires GROUP privilege

Facility: SYSTEM, VAX/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.
NOGRPNAM,

operation requires GRPNAM privilege

Facility: SYSTEM, VAX/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.
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.
NOGSDREF,

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

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

no condition handler found

Facility: SYSTEM, VAX/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-366

Messages

NOHDJMT,

No Head-JMT in JMT list (journaling)

compatibility mode image, 'file-spec7, cannot be header resident

Facility: INSTALL, Install Utility
Explanation: The /HEADER qualifier was ignored. Resident headers are not
used with compatibility mode images.
User Action: None. The known file entry was successfully created.
NOHIDDEN,

cannot enter hidden ACEs

Facility: ACLEDIT, Access Control List Editor
Explanation: The ACE currently being entered has the HIDDEN option set.
User Action: Remove the HIDDEN option before attempting to enter the
ACE.
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 was 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$OUTPUT_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.

2-367

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

no level 1 help text found in 'input file-spec'

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, VAX/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'

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

image file not created

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

no index information in file 'file-name'

Facility: DSRINDEX, DIGITAL Standard Runoff Indexing Utility
Explanation: The indicated file does not contain any index entries.
User Action: Check the corresponding input file to be sure there are index
entries.

Messages

NOINDEXF,

no valid index file header found on 'device7

Facility: BACKUP, Backup Utility
Explanation: The Backup Utility encountered an error during an attempt to
search for the index file, [000000]INDEXF.SYS;1, 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.
NOINPFILES,

no useable input files

Facility: MONITOR, Monitor Utility
Explanation: A multi-file summary was 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 was ignored, and provides an accompanying
message explaining why the file could not be used. Reissue 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.
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 xxx

Facility: DEBUG, VAX/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.

2-369

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
Explanation: This message is associated with a traceback internal consistency
check.
User Action: Submit a Software Performance Report.
NOIOCHAN,

no I/O channel available

Facility: SYSTEM, VAX/VMS System Services
Explanation: The process has exceeded 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.
NOITEMSEL,

item selection not allowed on existing ACE

Facility: ACLEDIT, Access Control List Editor
Explanation: The item selection key cannot be used on existing ACEs.
User Action: The item must be changed by deleting the current item, and
inserting the new item.
NOJOBID,

job 'nnn' not found in 'queue-name7 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 was
entered correctly. If it was 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.

Messages

NOJOBNAME,

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

Editing session is not being journaled

Facility: VAX Text Processing Utility
Explanation: VAXTPU was 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: 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 valid key maps.
NOKEYMAPLIST,

Attempt to access an undefined key-map list 'key-map-listname'

Facility: 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 (/) was present on a command but was not
followed by a qualifier keyword name.
User Action: Reenter the command specifying the qualifier or removing the
slash.

2-371

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, VAX/VMS Debugger
Explanation: '\' is not currently defined.
User Action: Do not reference #\# until a DEPOSIT or EVALUATE command
has been performed.
NOLBLS,

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.
User Action: None. Any command that follows the label will be executed.
NOLCL,

image does not contain local symbols

Facility: PATCH, VAX Image File Patch Utility
Explanation: When you initialized PATCH, no local symbol information was
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.
NOLICENSE,

operation requires software license

Facility: SYSTEM, VAX/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.
NOLINKS,

no slots in logical link vector

Facility: SYSTEM, VAX/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.

Messages

NOLINXXX,

lines 'xxx:yyy' do not exist

Facility: DEBUG, VAX/VMS Debugger
Explanation: The line number range xxxiyyy 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: CLI, 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, issue
the command once for each file specified.
NOLIST,

parameter list not allowed

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

there is no known file entry List

Facility: INSTALL, Install Utility
Explanation: The known file entry List was 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, VAX/VMS System Services
Explanation: A system facility attempted to connect to a remote process that
was not enabled for connections.
User Action: Ensure that the remote process is receiving connections.
NOLITERAL,

no LITERAL translation exists for 'xx'

Facility: PATCH, VAX Image File Patch Utility, or DEBUG, VAX/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.

2—373

Messages

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, VAX/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, VAX/VMS System Services
Explanation: The system's lock identification table was full when an $ENQ
system service request was 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.
NOLOGNAM,

no logical name match

Facility: SYSTEM, VAX/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.
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: Reenter the command, explicitly specifying the revision file
specification.
NOMACFOUND,

no .MACRO found in 'input file-spec'

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

2-374

Messages

NOMATCH,

'file-specification' - xxx records

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

no match found against input string

Facility: STR, Run-Time Library String Procedures
Explanation: There was no match found for the input string that was passed
to the routine.
User Action: None.
NOMATCHES,

no strings matched

Facility: SEARCH, SEARCH Command
Explanation: The search operation was able to open and search one or more
files, but the file(s) did not contain the search strings.
User Action: None. This message is informational.
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, VAX/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.
NOMODIFY,

ACE cannot be modified

Facility: ACLEDIT, Access Control List Editor
Explanation: An attempt was made to modify an ACE that cannnot be
modified by the ACL editor.
User Action: This is usually caused by attempting to modify an ACE of
an unknown format, one that is application dependent (indicated by the
HIDDEN option), or an unsupported ACE type.
NOMODNAM,

no module name found for 'input file-spec'

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

2-375

Messages

NOMODS,

no input modules specified (or found)

Facility: LINK, VAX Linker
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 was
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: No user action is required.
NOMOREFILES,

no more files

Facility: SYSTEM, VAX/VMS System Services
Explanation: No more files exist that match a wild card in a file specification
string. At least one match was found.
User Action: Note the condition. Modify the source program, if necessary, 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.
NOMOREKEYS,

no more keys defined

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: SMG$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.
NOMOREMSG,

no more messages

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

2-376

Messages

NOMOREPROC,

no more processes

Facility: SYSTEM, VAX/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.
NO—MORMSG,

no more broadcast messages are available

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: A call to SMG$GET_BROADCAST_MESSAGE found that there
no more messages to be obtained.
User Action: None.
NOMSGS,

no messages

Facility: MAIL, Personal Mail Utility
Explanation: There are no mail messages.
User Action: None.
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
file-spec'

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 'library
file-spec'

Facility: LIBRAR, LIBRARY Command
Explanation: The Librarian 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.

2-377

Messages

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

ACP multiple block buffering not supported yet

There are no names matching the one requested

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

SYS$INPUT must be an ANSI CRT

Facility: VAX Text Processing Utility
Explanation: You ran VAXTPU while the logical name SYS$INPUT was
associated with a terminal that does not have the ANSI CRT characteristic, 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.
NONCONTIG,

'file-name' is not contiguous due to insufficient contiguous space

Facility: BACKUP, Backup Utility, PATCH, VAX Image File Patch Utility
Explanation: The specified file was 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,

non-contiguous image file being written

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

2-378

Messages

NONEFOUND,

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

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

network unavailable

Facility: SHOW, SHOW Facility
Explanation: The network is unavailable for some reason.
User Action: None.
NONETMBX,

operation requires NETMBX privilege

Facility: SYSTEM, VAX/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.
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.
NONEWCUR,

cannot retain new address, '.' lost

Facility: DEBUG, VAX/VMS Debugger
Explanation: Current address expression cannot be retained as V.
User Action: '.' is not defined.
NONEWMAIL,

no new messages

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

cannot retain new value, '\' lost

Facility: DEBUG, VAX/VMS Debugger
Explanation: The value of the current expression cannot be saved as the last
value.
User Action: '\' cannot be used until a value has been saved.

2-379

Messages

NONEXDRV,

nonexistent drive

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

Buffer 'name7 does not exist

Facility: 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: SYSTEM, VAX/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 was not already deleted. If a process name was entered, the
process must be in the same group.
NONEXSTACP,

Nonexistent ACP process

device is not a local device

Facility: SYSTEM, VAX/VMS System Services, MOUNT, MOUNT
Command and INIT, INITIALIZE Volume 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.
NONPHYSET,

nonphysical save set supplied to physical operation

Facility: BACKUP, Backup Utility
Explanation: A save set created without the /PHYSICAL qualifier was used
as input to an operation with the /PHYSICAL qualifier.
User Action: Use the BACKUP/LIST command to determine how the save
set was created. Reevaluate the operation and reenter the command.

2-380

Messages

NONPICDAT,

'number7 relocatable address reference(s) in 'module-name7 file
'file-name'

Facility: LINK, VAX Linker
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.
NONPICIMG,

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

Facility: LINK, VAX Linker
Explanation: While building a position-independent shareable image, a
shareable image was input that is not position-independent. The shareable
image being created is also built non-position-independent.
User Action: None required. If possible, rebuild the non-positionindependent 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 'file-name'

Facility: LINK, VAX Linker
Explanation: A reference was 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.
NONXTLIN,

next line for source display not defined

Facility: DEBUG, VAX/VMS Debugger
Explanation: The DEBUG command TYPE or SEARCH was 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.
NOOPENJOB,

no open job 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 or $SNDSMB
request.
User Action: Modify the program to open a job first.

2-381

NOOPER,

operation requires OPER privilege

Facility: SYSTEM, VAX/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
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.
NOOPR,

no operator available to service request

Facility: MOUNT, MOUNT Command
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, VAX Image File Patch Utility and DEBUG, VAX/VMS
Debugger
Explanation: One or more operands were omitted from the expression.
User Action: Add the correct number of operands and retry.
NOOPRTR,

missing operator in expression

Facility: DEBUG, VAX/VMS Debugger
Explanation: The expression specified does not contain an operator.
User Action: Add an operator to the expression.
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: Reissue the MONITOR request, specifying any combination of
the qualifiers: /DISPLAY, /RECORD, /SUMMARY.
NOOUTQUAL,

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

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

Messages

NOP1VA,

PI space not supported in shareable images

Facility: SYSTEM, VAX/VMS System Services
Explanation: PI space is not supported in shareable images.
User Action: Relink the image, positioning all binary data in PO space.
NOP AGED YN,

unable to allocate enough paged dynamic memory

Facility: INSTALL, Install Utility
Explanation: INSTALL cannot complete the operation because paged
dynamic memory is not inaccessible.
User Action: Contact your system manager.
NOPARAM,

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: Reissue the command specifying a valid parameter name.
NOP AREN,

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

There is no parent process to attach to at line 'integer'

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

there is no parent to which to attach

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

no parameters

Facility: NCP, Network Control Program
Explanation: You did not specify parameters for a command.
User Action: Reenter the command with parameters.

2—383

Messages

NOPATAREA,

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

Facility: PATCH, VAX Image File Patch Utility
Explanation: The current user-defined patch area was 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.
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, VAX/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, VAX/VMS Debugger
Explanation: The logical predecessor of the identifier or instruction
referenced is not defined.
User Action: None. This message is informational.
NOPREV,

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

Facility: INSTALL, Install Utility
Explanation: A Known File Entry was created via the REPLACE command,
and there was no previous entry that had to be deleted first.
User Action: None. The use of REPLACE implies that an old entry was
expected to exist, but didn't.

2-384

Messages

NOPRIV,

diagnostic and operator privileges required

Facility: NCP, Network Control Program
Explanation: The DIAGNOSE and OPER privileges are required.
User Action: Run the NCP under account with DIAGNOSE and OPER
privileges.
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,

insufficient privilege to start PSIACP

Facility: PSI, VAX Packetnet System Interface
Explanation: PSIACP has been started without the privileges it needs to start
VAX PSI.
User Action: Use STARTPSI.COM from the SYSTEM account to start PSI.
NOPRIV,

no privilege for attempted operation

Facility: SYSTEM, VAX/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 was 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.
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 VAX
RMS or system-owned data area or memory page.
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.
Verify the file or volume name. Have the owner of the file or volume change
the protection value.

2-385

NOPRIV,

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

Facility: MOUNT, MOUNT Command
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, VAX/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.
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.
NOPRMGBL,

operation requires PRMGBL privilege

Facility: SYSTEM, VAX/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.
NOPRMMBX,

operation requires PRMMBX privilege

Facility: SYSTEM, VAX/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.

Messages

No subprocess to interact with

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

protocol not supported on remote node

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

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

Facility: LINK, VAX Linker
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.
NOPSWAPM,

operation requires PSWAPM privilege

Facility: SYSTEM, VAX/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, VAX/VMS System Services
Explanation: The quota file does not exist.
User Action: Verify that you are using the correct device. Create the quota
file.

2-387

Messages

NOQUAL,

no qualifier in statement

Facility: FDL, Edit/FDL Utility
Explanation: You specified a secondary that requires a qualifier, but none
was 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: CLI, Command Language Interpreter (DCL)
Explanation: A command that has no qualifiers was specified with a qualifier.
User Action: Reenter the command; do not specify any qualifiers.
NOQUESPACE,

no space in system job queue file

Facility: JBC, Job Controller
Explanation: The system job queue file is full and cannot not 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 reissue 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.

2-388

Messages

NORCP,

RCP not active

NETACP - no receive buffer available

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

no entry in database

Facility: NCP, Network Control Program
Explanation: A reference was made to nonexistent data.
User Action: Refer to existing data.
NOREDEFINE,

Built-in procedure 'name' cannot be redefined at line 'integer'

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

2-389

Messages

NOREF,

page reference not found

Facility: DSRINDEX, DIGITAL Standard Runoff Indexing Utility
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.
NORELOC,

relocation of CASE instructions not supported

Facility: PATCH, VAX Image File 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 redo the EXCHANGE command on that node.
NOREMOTE,

you are not authorized to login set host today

Facility: LOGIN, Login Processor
Explanation: The information in the user authorization file indicates that you
are not allowed to log in through a remote terminal (SET HOST).
User Action: Do not use a remote terminal.
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.

2-390

Messages

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 was write-locked.
User Action: Remount the output volume with write access, then reenter the
command.
NOREPAIR,

one or more volumes write locked - /REPAIR 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 /REPAIR 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.
NORESTART,

job not restartable

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

normal successful completion

Facility: MACRO, VAX Macro Assembler, RMS, VAX Record Management
Services, SYSTEM, VAX/VMS System Services, SUM, Source Update Merge
Utility, UETP, User Environment Test Package
Explanation: This success message is associated with a status code returned
from a system service request, or with the Macro Assembler.
User Action: None. This message is informational. It is not normally
displayed by the operating system.
NORMAL,

Normal successful completion

Facility: UETP, User Environment Test Package
Explanation: A module in the UETP completed successfully.
User Action: None.

2-391

Messages

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.
User Action: None. This is a successful status code. The operating system
does not normally display this message.
NORMAL,

successful completion

Facility: STR, Run-Time Library String Procedures
Explanation: This success message is associated with the Run-Time Library
string procedures.
User Action: None.
NORSTBLD,

cannot build symbol table

Facility: DEBUG, VAX/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 was created.
NORSTBLD,

cannot build symbol table

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

no scope exists to look up line 'line number'

Facility: DEBUG, VAX/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-392

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

No select active

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

operation requires SETPRV privilege

Facility: SYSTEM, VAX/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.
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.
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.

2-393

Messages

NOSHMBLOCK,

no free shared memory block available for creation

Facility: SYSTEM, VAX/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.
NOSHMEM,

operation requires SHMEM privilege

Facility: SYSTEM, VAX/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: 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-394

Messages

NOSIGNAL,

no signal currently active

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

no pcb available

Facility: SYSTEM, VAX/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 and/or the size of the swap file.
NOSOLICIT,

interrupt message not solicited

Facility: SYSTEM, VAX/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.
NOSPACE,

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

Facility: TRACE, Traceback
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.
NOSRCHSTR,

search string not set

Facility: DEBUG, VAX/VMS Debugger
Explanation: No current search string is defined for the DEBUG command
SEARCH. The SEARCH command was 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 xx

Facility: DEBUG, VAX/VMS Debugger
Explanation: No source line corresponds to the address xxx specified on the
DEBUG command EXAMINE/SOURCE.
User Action: None. This message is informational.

2-395

Messages

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 at line 'integer'

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

logical successor not defined

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

ACE for object 'file-name' 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, VAX/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.
User Action: None.
NOSUCHDEV,

no such device available

Facility: SYSTEM, VAX/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 was coded as a logical name, verify that it was assigned a valid
equivalence name.

2-396

Messages

NOSUCHFILE,

no such file

Facility: SYSTEM, VAX/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
was 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.
User Action: None.
NOSUCHFORM,

no such form

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

no such job

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

no shared memory found at specified NEXUS

Facility: SYSGEN, System Generation Utility
Explanation: The desired shared memory unit number was not found in a
search of the backplane interconnect adapter list.
User Action: Reissue the command with the proper device unit number.
NOSUCHMOD,

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

Facility: LINK, VAX Linker
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 xxx is not in module chain

Facility: DEBUG, VAX/VMS Debugger
Explanation: The module xxx, 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.

2-397

Messages

NOSUCHMODU,

no such module name 'module-name7

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

specified node does not exist

Facility: SYSTEM, VAX/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, VAX/VMS System Services
Explanation: An attempt was 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 was 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
VAX/VMS Networking Manual for additional information.
NOSUCHQUE,

no such queue

Facility: JBC, Job Controller
Explanation: The specified queue does not exist.
User Action: None.
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 was canceled by the user who issued it, no action is necessary.
NOSUCHRTN,

unknown CLI 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.

2-398

Messages

NOSUCHRVN,

/VOLUME = 'number7 invalid, volume set contains 'number7
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, VAX/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.
NOSUCHSYM,

no such symbol

Facility: LIB, Run-Time Library General Procedures
Explanation: You specified an undefined symbol.
User Action: Retry the operation specifying a defined symbol.
NOSUCHSYM,

no such symbol

Facility: PATCH, VAX Image File Patch Utility
Explanation: A symbol was specified that was 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, VAX/VMS Debugger
Explanation: The CANCEL TRACE command specified an address that was
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, VAX/VMS System Services
Explanation: An attempt was made to initiate a DECnet-VAX logical link
connection. The supplied access control string was not recognized at the
remote node. In particular, the user-name, password, or account field was not
recognized.
User Action: The access control string specified was incorrect. If default
access control was specified, notify the system manager that the DECnet
configuration database needs to be updated.

2—399

Messages

This error can be returned if the specified access control string was not
recognized (for example, no record in the UAF), was too long, or contained
illegal characters.
Refer to the VAX/VMS Networking Manual for additional information.
NOSUCHUSER,

user 'name7 not currently logged in

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

no such user 'user-name'

Facility: MAIL, Personal 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 was 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 user name. If you are
asked if you want to send the message anyway, respond Y (yes) or N (no).
NOSUCHVERB,

the CLI 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 CLI
table.
User Action: Make sure that the syntax is correct and try to delete the verb
again.
NOSUCHWPT,

no such watchpoint

Facility: DEBUG, VAX/VMS Debugger
Explanation: The CANCEL WATCH command specified an address that was
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 was specified on the /INPUT qualifier, indicating
a multi-file summary request, but the /NOSUMMARY qualifier was also
present, explicitly or implicitly. A list of files may be specified only for a
multi-file summary request.
User Action: If a multi-file summary was desired, reissue the MONITOR
request, specifying the /SUMMARY qualifier. If a multi-file summary was not
desired, reissue the MONITOR request specifying /INPUT with a single file.

2-400

Messages

NOSYMBOL,

symbol xxx is not in the symbol table

Facility: DEBUG, VAX/VMS Debugger, PATCH, VAX Image File Patch
Utility
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.
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 file(s)

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

operation requires SYSGBL privilege

Facility: SYSTEM, VAX/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.
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-401

NOSYSLCK,

operation requires SYSLCK privilege

Facility: SYSTEM, VAX/VMS System Services
Explanation: You tried to lock a system-wide resource when you did not
have SYSLCK privilege.
User Action: Ask the system manager for SYSLCK privilege; or remove the
LCK$M_SYSTEM flag; or run the program in EXEC mode as a privileged
shareable image.
NOSYSNAM,

operation requires SYSNAM privilege

Facility: SYSTEM, VAX/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, VAX/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.
NOT1STVOL,

'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 was 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.

Messages

NOT1STVOL,

tape 'name7 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, VAX/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, VAX Image File 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, issue the PATCH
command SHOW MODULE to determine which modules are in the symbol
table, then issue the PATCH command CANCEL MODULE specifying the
module names whose symbols are no longer required. Then reissue the
PATCH command SET MODULE.
NOTANSI,

not ANSI volume on 'device-name'

Facility: MOUNT, MOUNT Command
Explanation: The volume on the specified device is not an ANSI-formatted
magnetic tape.
User Action: Initialize the tape and reissue 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.
NOTAPEOP,

no tape operator

Facility: SYSTEM, VAX/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.

2-403

Messages

NOTARRAY,

type of variable is not array

Facility: DEBUG, VAX/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,

xxx was not declared as a structure

Facility: DEBUG, VAX/VMS Debugger
Explanation: A VAX BLISS-32 structure reference specified a symbol xxx 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, Run-Time Library Screen Management Procedures
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.
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.
User Action: None. Save set data has been lost.
NOTBOOCAP,

not a boolean capability

Facility: SMG, Run-Time Library Screen Management Procedures
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.
NOTCALEDT,

this command cannot be executed; MAIL$EDIT does not specify a
callable editor

Facility: MAIL, Personal Mail Utility
Explanation: User attempted to use the /EDIT qualifier in MAIL with
MAIL$EDIT defined such that it would create a subprocess.
User Action: Deassign the logical name for MAIL$EDIT to allow MAIL to
use callable EDT.

2-404

Messages

NOTCLASS,

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

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

'input-file-spec' not completely copied

Facility: Shared by several facilities
Explanation: A copy operation began but did not finish. This message is
accompanied by a VAX 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.
NOTCOPIED,

'input-file-spec' not copied

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

file 'file-name' 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, VAX/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: Issue 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.

2-405

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: 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 Reference
Manual.
NOTDELETED,

file 'filename7 not deleted

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: 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-406

Messages

NOTDISCON,

terminal is not disconnectable - explicitly specify LOGOUT

Facility: CLI, 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 issue the SET VOLUME
command to a tape or terminal. The SET VOLUME commands 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, VAX Image File Patch Utility and DEBUG, VAX/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
more complete.
NOTENABOPT,

not a legal ENABLE option

Facility: MACRO, VAX Macro Assembler
Explanation: An argument to an .ENABLE or .DISABLE directive was 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-407

Messages

NOTERM,

command device is not a terminal

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

FCB linkage broken

Bad FCB pointer in window

Not FCP window in IRP

2—408

Messages

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 was used for an I/O 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 was specified, ensure that the correct equivalence name is assigned.
Correct the source program or reenter the command, as applicable.
NOTFOU,

not found

Facility: LIB, Run-Time Library General Procedures
Explanation: It indicates that a request to find the first set or clear bit
returned with no bit set or cleared.
User Action: Note the condition. Modify the source program, if necessary, to
detect and respond to the condition.
NOTFOUND,

no messages containing 'text' found

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

specified search string not found

Facility: ACLEDIT, Access Control List Editor
Explanation: The specified search string was not found.
User Action: None.
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.
NOTFROMLAT,

unable to shut down LAT from a LAT terminal

Facility: LATCP, Local Area Transport Control Program
Explanation: The LAT software cannot be stopped from a LAT terminal.
User Action: Login to another terminal (not from LAT) to stop the LAT
software.
NOTGENDEV,

not a generic device

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

2-409

Messages

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 and 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.
NOTIDENT,

identifier expected instead of xxx

Facility: DEBUG, VAX/VMS Debugger
Explanation: An identifier was expected but the value xxx was found instead.
User Action: Change the expression to contain an identifier.
NOTIDFMT,

id name parameter does not translate to ID format

Facility: AUTHORIZE, Authorize Utility
Explanation: The Authorize Utility does not grant resource rights for a UIC
identifier to another UIC identifier.
User Action: Reissue the AUTHORIZE command GRANT/IDENTIFIER,
making sure that the id-name parameter is in identifier ID format, not UIC
format.
NOTIDX,

file is not an index file

Facility: CONVERT, Convert/Reclaim Utility
Explanation: You have specified a sequential or relative file for reclamation;
CONVERT/RECLAIM works only with Prologue 3 indexed files.
User Action: Specify a Prologue 3 indexed file.
NOTIDX,

output file is not an indexed file

Facility: CONVERT, Convert Utility
Explanation: You specified the /MERGE qualifier and the output file is not
an indexed file.
User Action: Specify /NOMERGE and try again.
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 SPAWN command is executed from within a
noninteractive process.
User Action: Do not use /NOTIFY.

2-410

Messages

NOTIMGLIB,

file 'file-name' is not a shareable image symbol table library

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

xxx is not implemented at command level

Facility: DEBUG, VAX/VMS Debugger
Explanation: The SET LANGUAGE command specified a language that the
debugger recognizes but does not support at this time.
User Action: Specify a language that the debugger supports.
NOTIMPOPCODE,

Opcode in delayed work queue not implemented

Facility: 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 .IF_FALSE, .IF_TRUE, .IF_TRUE—FALSE, .IFF, .IFT, or .IFTF
subconditional directive was not in a conditional assembly block.
User Action: Replace the subconditional directive with a conditional directive
or delete the subconditional directive.
NOTINITED,

LAT terminal port driver controller init not called

Facility: LATCP, Local Area Transport Control Program
Explanation: The Local Area Transport Control Program (LATCP) Utility did
not attempt to initialize the LTDRIVER PORT interface because of a previous
error.
User Action: Correct the error condition that prevented the LTDRIVER PORT
interface from being initialized.
NOTINMACRO,

statement not in MACRO body

Facility: MACRO, VAX Macro Assembler
Explanation: The .NARG directive was not in a macro definition or
expansion.
User Action: Delete or move the line containing the .NARG directive.
NOTINMACRO,

statement not in MACRO body

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

2—411

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 was 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, VAX/VMS System Services
Explanation: Writeable shareable images must be installed.
User Action: Install the shareable image specifying /SHARE/WRITE.
NOTINTBLSZ,

block size is greater than 2048

Facility: SYSTEM, VAX/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/BL0CK=n

NOTIRPAQB,

Not IRP pointer in AQB

'file-spec' 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,

" not on 'device-name'

Facility: MOUNT, MOUNT Command
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 online.

Messages

NOTLABELMT,

tape is not labeled

Facility: SYSTEM, VAX/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: 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 was not a legal option.
User Action: Delete the illegal option or replace it with a legal option.
NOTLINBND,

program is not at a line boundary

Facility: DEBUG, VAX/VMS Debugger
Explanation: The GO command specified an address that contains threaded
code data. The debugger cannot start executing from this address.
User Action: Specify an address that contains executable instructions.
NOTLKB,

Structure is not an LKB

LAT terminal port driver (LTDRIVER) is not loaded

Facility: LATCP, Local Area Transport Control Program
Explanation: The LTDRIVER was not loaded when a command was passed
to the Local Area Transport Control Program (LATCP).
User Action: Load the LTDRIVER using the following command at the
SYSGEN> prompt:
SYSGEN> LOAD LTDRIVER/NOADAPTER

2-413

NOTLOCKED,

'file-name' not locked

Facility: SET, SET Facility
Explanation: The file that you want to lock is already locked.
User Action: None.
NOTLOCKED,

'file-spec' was not locked

Facility: Shared by several facilities
Explanation: The file specified by a DCL command UNLOCK was not
locked.
User Action: None. This message is informational.
NOTMOD,

volume 'volume-name' not modified

Facility: SET, SET Facility
Explanation: The volume was not modified. This message is accompanied
by another message.
User Action: Take corrective action based on the accompanying message.
NOTMODIFIED,

no pages in the section were modified

Facility: SYSTEM, VAX/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 was not mounted.
User Action: Check the command for a misspelled device name.
NOTMPMBX,

operation requires TMPMBX privilege

Facility: SYSTEM, VAX/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.

Messages

NOTMTLMTL,

Corrupted mounted volume list

qualifier or keyword not negatable - remove "NO" or omit

Facility: CLI, 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 VAX/VMS DCL
Dictionary for a list of negatable qualifiers and keywords.
NOTNETDEV,

not a network communication device

Facility: SYSTEM, VAX/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 I/O request is a valid communications device.
NOTNUMCAP,

not a numeric capability

Facility: SMG, Run-Time Library Screen Management Procedures
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 STRING or
BOOLEAN which would have terminated numeric capabilities.
NOTOBJLIB,

file 'file-name7 is not an object library

Facility: LINK, VAX Linker
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 was 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.

2-415

Messages

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: 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.
NOTORIGSRC,

original version of source file not found; file used is 'xxx'

Facility: DEBUG, VAX/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 DEBUG command SET SOURCE to indicate the location of the source to
DEBUG.
NOTPARAM,

not a parameter file

Facility: SYSGEN, System Generation Utility
Explanation: The file specified in the SYSGEN command USE is not a valid
parameter file.
User Action: Use a valid parameter file that is either provided by VAX/VMS
or created by the SYSGEN command WRITE in SYSGEN.
NOTPASTED,

given display is not pasted to given pasteboard

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: An attempt was made to unpaste or move a display that was
not pasted to the specified pasteboard.
User Action: Check that you referencing the correct virtual display. Verify
that the display has not been unpasted or that you forgot paste it.
NOTPATADR,

patch address is 'addrl' not 'addr2'

Facility: PATCH, VAX Image File Patch Utility
Explanation: You typed the incorrect starting address of the patch area.
User Action: To determine the correct starting address, issue either the
PATCH command SHOW PATCH —AREA or the PATCH command
ALIGN/BYTE. When you issue the PATCH command ALIGN/BYTE, PATCH
defines a symbol as the current starting address.

2—416

Messages

NOTPCB,

Structure not PCB

failed to queue spool file for print

Facility: SYSTEM, VAX/VMS System Services
Explanation: An error occurred while an implicitly spooled file was 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 was 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 'file-name'

Facility: LINK, VAX Linker
Explanation: An object module specified other than a psect base in a set
relocation base command.
User Action: Submit a Software Performance Report on the appropriate
language compiler.
NOTPTR,

variable must be of pointer or file type

Facility: DEBUG, VAX/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, VAX/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.

2—417

NOTQUO,

unquoted argument not allowed in ASCII or INSTRUCTION modes

Facility: PATCH, VAX Image File 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, VAX/VMS Debugger
Explanation: There are no tracepoints or opcode tracing set.
User Action: None. This message is informational.
NOTRAN,

logical name cannot be translated

Facility: INIT, INITIALIZE Volume Command and MOUNT, MOUNT
Command
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, VAX/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 'name7

Facility: SHOW, SHOW Facility
Explanation: There is no translation for the specified logical name.
User Action: None.
NOTREADIN,

you are not reading a message

Facility: MAIL, Personal 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 type the appropriate command in response to the prompt MAIL> .

Messages

NOTRELVOL,

relative volume ,nnn/ not on device

Facility: MOUNT, MOUNT Command
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,

'file name' not renamed

Facility: RENAME, RENAME Command
Explanation: The specified file was not renamed.
User Action: Correct the error according to the accompanying message.
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 was swapped
out of the balance set when the system failed.
User Action: None.
NOTRMSOUT,

RMS is not being used to perform output

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: SMG$SNAPSHOT is used with files and unknown devices to
capture the contents of the pasteboard as 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)

2—419

Messages

NOTRVTVCB,

Not RVT pointer in VCB

The markers are not in the same buffer

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

cannot RENAME to a different device

Facility: RENAME, RENAME Command
Explanation: An attempt was 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.
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.

2—420

Messages

NOTSET,

LAT terminal port driver multicast data not set

Facility: LATCP, Local Area Transport 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
LTDRIVER from being initialized.
NOTSHRIMG,

file 'file name' 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.
NOTSQDEV,

not a sequential device

Facility: SYSTEM, VAX/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 dirver not started

Facility: LATCP, Local Area Transport Control Program
Explanation: The LATCP Utility did not attempt to start the LTDRIVER
because of a previous error.
User Action: Correct the condition that prevented the LTDRIVER from being
started.
NOTSTOPPED,

LAT terminal port driver not stopped

Facility: LATCP, Local Area Transport Control Program
Explanation: The LATCP Utility could not stop the LTDRIVER because of a
previous error.
User Action: Correct the error condition that prevented the LTDRIVER from
being stopped.
NOTSTRCAP,

not a string capability

Facility: SMG, Run-Time Library Screen Management Procedures
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-421

Messages

NOTSTRUCTl,

qualifier(s) not available with structure level 1

Facility: INIT, INITIALIZE Volume 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.
NOTUCBIRP,

Not UCB pointer in IRP

Not UCB pointer in RVT

Corrupted UCB list

2-422

Messages

NOTUCBWCB,

Bad UCB pointer in window

device not connected to a UNIBUS/Q-bus port

Facility: SET, SET Facility
Explanation: You issued the DCL command SET DEVICE/DFAG for a device
other than a UDA50 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.
NOT VALID,

information not in physical memory

Facility: SDA, System Dump Analyzer
Explanation: The virtual address you specified is not currently in physical
memory or was not in physical memory at the time of the dump.
User Action: None. You are not able to examine the address.
NOT VALID,

user authorization failure

Facility: LOGIN, Login Processor
Explanation: A user authorization failure has occurred. Either the username
or the password is incorrect.
User Action: Check the spelling of the username and password, and try
again.
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 was too large.
User Action: Reenter the command with a smaller record length.

2-423

Messages

NOTVCBUCB,

Not VCB pointer in UCB

volume is not part of a volume set

Facility: SYSTEM, VAX/VMS System Services
Explanation: An attempt was 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 was specified or remove the
volume-specific reference.
NOTVOLSET,

volume on 'device-name' not in volume set "

Facility: MOUNT, MOUNT Command
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—424

Messages

NOTWCBIRP,

Not WCB Pointer in IRP

Corrupted WCB list

symbol xxx is not unique

Facility: DEBUG, VAX/VMS Debugger
Explanation: The symbol specified was not in a default scope and was
defined in more than one scope.
User Action: Specify the scope of the symbol in a pathname or change the
default scope.
NOUNLOAD,

driver is not unloadable

Facility: SYSGEN, System Generation Utility
Explanation: Either an attempt was 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.
NOUPDATE,

no patch for update qualifier ECO level 'nn'

Facility: PATCH, VAX Image File Patch Utility
Explanation: When a command procedure was submitted for interactive or
batch execution (by typing PATCH/UPDATE = (eco-level,...)), an ECO level
was specified that was not included in the command procedure.
User Action: Check your command procedure for correct ECO levels and
retry.

2-425

Messages

NOUSRWCS,

No user WCS halt restart

$SEARCH operation not preceded by valid SPARSE

Facility: RMS, VAX Record Management Services
Explanation: A VAX RMS wildcard SSEARCH operation was expected and
no preceding valid SPARSE had been expected.
User Action: Verify that the sequence of VAX RMS service calls was coded
correctly and that the NAM block was 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 was
specified with a value.
User Action: Use the DCL command HELP or refer to the VAX/VMS DCL
Dictionary for the correct syntax and reenter the command.
NO VALUE,

'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.
NO VALUE,

reference does not have a value

Facility: DEBUG, VAX/VMS Debugger
Explanation: The command specified a reference that has no value.
User Action: Change the reference.
NOVER,

no file version obtained for 'file-spec'

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.

2-426

Messages

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
VIRTU ALP AGECNT may need to be increased.
NOVOLDATA,

volume summary data for 'device' 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 was 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, VAX/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.
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.
NOVOLUMES,

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

no watchpoints are set

Facility: DEBUG, VAX/VMS Debugger
Explanation: No watchpoints are set.
User Action: None. This message is informational.

2-427

Messages

NOWATTAR,

cannot watch-protect target

Facility: DEBUG, VAX/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 (PI space). These two kinds of
locations cannot be watchpointed.
User Action: None, unless you specified the wrong location.
NOWBPT,

cannot insert breakpoint

Facility: DEBUG, VAX/VMS Debugger
Explanation: This message indicates an internal debugger error.
User Action: Submit a Software Performance Report.
NO WILD,

no wildcard permitted

Facility: Shared by several facilities
Explanation: Wild cards are not permitted in this context.
User Action: Respecify using exact file specifications.
NOWOPCO,

cannot replace breakpoint with opcode

Facility: DEBUG, VAX/VMS Debugger
Explanation: This message indicates an internal debugger error.
User Action: Submit a Software Performance Report.
NOWORLD,

operation requires WORLD privilege

Facility: SYSTEM, VAX/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.
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.
NOWPROT,

cannot set protection

Facility: DEBUG, VAX/VMS Debugger
Explanation: This message indicates an internal debugger error.
User Action: Submit a Software Performance Report.

2-428

Messages

NO—WRK,

work files required, cannot do sort in memory as requested

Facility: SORT, VAX SORT/MERGE Utility
Explanation: The /WORK-FILES=0 qualifier was specified indicating the data
would fit in memory, but the data was 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, VAX/VMS System Services
Explanation: An image file that was 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, VAX Record Management Services
Explanation: A VAX RMS $CREATE service was executed for an indexed file
and no primary key XAB definition was provided.
User Action: Verify that the VAX RMS service was coded correctly.

NSADDR,

address 'addr' is not within image

Facility: PATCH, VAX Image File Patch Utility
Explanation: You specified an address outside the address range of the image
file.
User Action: Retry the operation specifying the correct address.
NSF,

.END LIST/.END NOTE not in same file as .LIST/.NOTE: 'string7
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.
NTWORK,

Network

2—429

NUDFENVS,

'number' undefined environment(s):

Facility: LINK, VAX Linker
Explanation: Undefined environments were encountered by the linker at the
end of Pass 1.
User Action: Ensure that all referenced environmemts are defined.
NUDFLSYMS,

'number' undefined module-local symbol(s):

Facility: LINK, VAX Linker
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 symbol(s):

Facility: LINK, VAX Linker
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: CLI, 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 was 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 was found empty on a call to
LBR$GET_INDEX.
User Action: None. Processing continues.
NULLFILE,

file 'file-spec' 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.
User Action: None. This message is informational.
NULLPRI,

null primary block

Facility: FDL, Create/FDL Utility, FDL, Edit/FDL Utility
Explanation: You specified a primary that requires secondaries, but none
were given.
User Action: Specify secondaries for the primary.

Messages

NUMBER,

invalid numeric value - supply an integer

Facility: CLI, Command Language Interpreter (DCL)
Explanation: A numeric value was specified for a DCL command that expects
values in certain radices, or interprets values within a particular context. For
example, the number 999 was entered when an octal value was required. Or
an alphabetic value was 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 VAX/VMS DCL
Dictionary for the legal values and reenter the command.
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, VAX 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, VAX Image File Patch Utility and DEBUG, VAX/VMS
Debugger
Explanation: An operand was omitted from the MACRO-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: Reissue the command with the correct number of operands.
NUMOPRNDS,

'xx' instructions must have ;nn' operands

2-431

NUMTRUNC,

number truncated

Facility: PATCH, VAX Image File Patch Utility and DEBUG, VAX/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.
NUMVAL,

error code of 'xx' requesting update value

Facility: PATCH, VAX Image File 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').
OBJFAIL,

unable to obtain object information for name

Facility: PSI, VAX Packetnet System Interface
Explanation: VAX PSI could not get the DECnet object information for
the object 'name7. This message may also occur if the SYSGEN MAXBUF
parameter is too small.
User Action: Make sure the object is in the DECnet database by issuing the
following command:
NCP> SET OBJECT name

If the SYSGEN MAXBUF parameter is too small, increase the size of this
buffer to at least 2048 bytes.
OBJLOCKED,

object currently locked by another user

Facility: SET, SET Facility
Explanation: An attempt was to modify the access control list (ACL) of an
object while another user was modifying the object's ACL.
User Action: Repeat the operation at a later time.
OBJLOCKED,

object currently locked by another user

Facility: SHOW, SHOW Facility
Explanation: An unsuccessful attempt was made to modify the ACL of an
object while another user was modifying the object's Access Control List
(ACL).
User Action: Try again at a later time.
OBJLOCKED,

object currently locked by another user

Facility: ACLEDIT, Access Control List Editor
Explanation: An attempt was made to modify the ACL of an object while
another user was modifying the object's ACL.
User Action: Try again at a later time.

Messages

OBTEVT,

error when reading raw events

Facility: EVL, Event Logger
Explanation: NETACP returned an error while EVL was 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 VAX/VMS
system is configured properly. The account under which EVL runs is specified
in the network Configuration Data Base.
ODS2SAVE,

save set disk on 'device' must be structure level 2

Facility: BACKUP, Backup Utility
Explanation: The specified volume was not a Files-11 Structure Level 2
volume. The volume cannot be used as a save set disk.
User Action: Retry the operation using a properly initialized Files-11
Structure Level 2 volume.
OFFLINE,

'device-name' : offline

Facility: MOUNT, MOUNT Command
Explanation: The given device is offline. 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, VAX Record Management Services
Explanation: A VAX RMS request to lock a record returns this success status
code when the specified record is already locked.
User Action: None.
OK _DEL,

deleted record successfully accessed

Facility: RMS, VAX Record Management Services
Explanation: A VAX RMS request to access a deleted record returns this
success status code when the specified record is accessed.
User Action: None.
OK—DUP,

record inserted had duplicate key

Facility: RMS, VAX Record Management Services
Explanation: A VAX RMS $PUT or SUPDATE service completed successfully.
The record inserted or updated had one or more key values that duplicated
the values of other records.
User Action: None.

2-433

Messages

OK_IDX,

index update error occurred

Facility: RMS, VAX Record Management Services
Explanation: A VAX RMS $PUT or $UPDATE service completed successfully.
However, the index could not be completely updated. No access paths to the
record have been lost.
User Action: The status value (STV) field of the RAB contains the VAX RMS
error that occurred during index update. Take corrective action based on that
value. File reorganization is recommended.
OK_LIM,

retrieved record exceeds specified key value

Facility: RMS, VAX Record Management Services
Explanation: A VAX 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.
User Action: None.
OK_NOP,

XAB not filled in for block I/O

Facility: RMS, VAX Record Management Services
Explanation: A VAX RMS $OPEN or $DISPLAY service that specified
block I/O access (BIO) completed successfully. However, one or more key
definition or allocation XABs were not filled in.
User Action: None.
OK—RLK,

record locked but read anyway

Facility: RMS, VAX Record Management Services
Explanation: A VAX RMS request to read a locked record completed
successfully.
User Action: None.
OK_RNF,

nonexistent record successfully accessed

Facility: RMS, VAX Record Management Services
Explanation: A VAX RMS request to access a nonexistent record completed
successfully.
User Action: None.
OK—RRL,

record locked against read but read anyway

Facility: RMS, VAX Record Management Services
Explanation: A VAX RMS request to read a record locked against read was
completed successfully.
User Action: None.

2-434

Messages

OK_WAT,

record locked after wait

Facility: RMS, VAX Record Management Services
Explanation: A VAX RMS request to access a record locked after wait
completed successfully.
User Action: None.
OLDINSCHK,

memory location 7addr7 not equal to 7xx7

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.
User Action: None. Processing continues based on the actual library type.
OLDTAB,

command tables have obsolete format - use SET COMMAND to
recreate

Facility: CLI, Command Language Interpreter (DCL)
Explanation: CLI encountered a command table with an obsolete format
while trying to automatically update it to the current format. The obsolete
command table must manually updated.
User Action: Use Command Definition Utility command SET COMMAND to
recreate the tables.
OLDVALCHK,

memory location 7addr7 not equal to 7xx7

Facility: PATCH, VAX Image File Patch Utility
Explanation: The verification of the contents of the given address failed.
User Action: Reissue the PATCH command specifying the correct value.
on output page pn; on input line 'In' of page 7pn7 of file 'filename7
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 (In) in which the error
occurred.
User Action: Find and correct the error string.

2—435

Messages

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 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: VAX Text Processing Utility
Explanation: An internal VAXTPU failure occurred.
User Action: Submit a Software Performance Report.
ONEENTQUE,

one entry in queue

Facility: LIB, Run-Time Library General Procedures
Explanation: The procedure successfully completed. An entry was added to
the front of the queue. As a result, the queue contains one entry.
User Action: None.
ONEF11DEV,

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

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 was 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 was 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: 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.

2-436

Messages

ONEPHYDEV,

/PHYSICAL specification must not be a list

Facility: BACKUP, Backup Utility
Explanation: The specification for a physical volume was 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: CLI, 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: 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.
ONEVAL,

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

Facility: CLI, Command Language Interpreter (DCL)
Explanation: A qualifier, keyword, or parameter that accepts only a single
value was specified with multiple values.
User Action: Reenter the command specifying only one value.
ONLEVL,

invalid ON context - use only within command procedures

Facility: CLI, Command Language Interpreter (DCL)
Explanation: An ON command was 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: CLI, 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.

2-437

Messages

OPCCUS,

opcode reserved to customer fault at PC = 'location', PSL ■ 'xxxxxxxx'

Facility: SYSTEM, VAX/VMS System Services
Explanation: An operation code beginning with "XFC was 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, VAX/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.
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, [000000]BITMAP.SYS;1, 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-spec'

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: None. If the Verify Utility finds lost files, it neither repairs nor
reports them until the error is corrected.
OPENDIR,

error opening parent directory for 'directory'

Facility: SET, SET Facility
Explanation: A parent directory could not be opened. This message is issued
with an accompanying message.
User Action: Take corrective action based on the accompanying message.

2-438

Messages

OPENEXC,

error opening exception file 'file-spec'

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.
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') 'file-name' 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 'devicename' 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-file' 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 speciifed directory does not exist.

•

The specified file does not exist.

2—439

•

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

error opening 'file-spec' as input

Facility: MACRO, VAX Macro Assembler
Explanation: The assembler encountered an I/O error when opening an
input source or macro library file; file-spec 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 'file' as input

Facility: LOGIN, Login Processor
Explanation: An error occurred while attempting to open the file containing
the system announcement message. An accompanying message will provide
more information.
User Action: Correct the problem described by the accompanying message,
and try again.
OPENIN,

Error opening 'input-file' as input

Facility: VAX Text Processing Utility
Explanation: The file could not be opened for input. The message should be
accompanied by a VAX RMS message indicating why the error occurred.
User Action: Follow the recovery procedure for the specified VAX RMS
message.
OPENIN,

error opening 'input-file' as input

Facility: Shared by several facilities
Explanation: An input file cannot be opened. This message is usually
accompanied by a VAX RMS message indicating the reason for the failure.
User Action: Take corrective action based on the associated message.
OPENIN,

unable to open or connect to input

Facility: ACCOUNTING, Accounting Utility
Explanation: An input file cannot be opened. This message is usually
accompanied by a VAX 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, [000000]INDEXF.SYS;1, 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.

Messages

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-file-spec' as output

Facility: Shared by several facilities
Explanation: An output file cannot be opened. This message is usually
accompanied by a VAX RMS message indicating the reason for the failure.
User Action: Take corrective action based on the associated message.
OPENOUT,

error opening 'file-spec' as output

Facility: MACRO, VAX Macro Assembler
Explanation: The assembler encoutered an I/O error when opening an
output object module or listing file; file-spec 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-file'

Facility: LIBRAR, LIBRARY Command
Explanation: During a VAX RMS operation, an error was 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-file' as output

Facility: VAX Text Processing Utility
Explanation: The file could not be opened for output. The message should
be accompanied by a VAX RMS message indicating the reason for error.
User Action: Follow the recovery procedure for the specified VAX 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 VAX RMS message indicating the reason for the failure.
User Action: Take corrective action based on the associated message.

2-441

Messages

OPENQUOTA,

error opening QUOTA.SYS

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility encountered an error during an attempt
to open the quota file, [000000]QUOTA.SYS;1, 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: Correct the error and reenter the job.
OPENVIRTUAL,

unable to open 'filename' as a virtual volume

Facility: EXCHANGE, Exchange Utility
Explanation: The EXCHANGE utility encounted 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.
OPER1,

OPER1

OPERIO

OPER11

2-442

Messages

OPER12,

OPER12

OPER2

OPER3

OPER4

OPER5

OPER6

2-443

Messages

OPER7,

OPER7

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: No action is required.
OPER8,

OPER8

OPER9

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

operator status for operator 'operator-name'

Facility: OPCOM, Operator Communication
Explanation: This message displays information in response to the DCL
command REPLY/STATUS issued by an operator.
User Action: No action is required.

2-444

Messages

OPINCOMPL,

operation is incomplete

Facility: SYSTEM, VAX/VMS System Services
Explanation: This message is associated with a status code returned from
a DR11-W interface operation. A block mode transfer operation completed
without transferring the requested number of bytes. The DR11-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.
User Action: Check for a hardware error. Wait a few seconds before issuing
another WRITE request.
OPNERR,

open error code of 'xx' on file 'file-spec7

Facility: PATCH, VAX Image File Patch Utility
Explanation: A VAX RMS $OPEN request failed due to the error code
represented as 7xx7.
User Action: Correct the error code (representing as xx) and retry.
OPNOTPERDOS,

operation not permitted on DOS-11 volume 'volume-name7

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

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.
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 VAX/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 Command
Explanation: This is the final message in a series of messages issued from
MOUNT to the operator.
User Action: None. The operator has refused your request.

2—445

Messages

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-text'

Facility: MOUNT, MOUNT Command
Explanation: An operator's response to the DCL command REQUEST is
displayed on the terminal.
User Action: None. This message is informational.
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

Facility: PATCH, VAX Image File Patch Utility
Explanation: An internal PATCH error has occurred.
User Action: Submit a Software Performance Report.
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 was issued with the /REPLY
qualifier; the request has been sent and displayed on the operator's terminal.
You cannot issue 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 Command
Explanation: This message announces an operator request.
User Action: None. This message is informational.

2-446

Messages

OPRQSTCAN,

operator request canceled

Facility: MOUNT, MOUNT Command
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 Command
Explanation: The operator request was canceled because the request was
completed.
User Action: No action is required.
OPRSNDERR,

error sending request to operator

Facility: MOUNT, MOUNT Command
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, VAX Image File Patch Utility or DEBUG, VAX/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.
OPTARGMIS,

missing argument in options file 'file-name'

Facility: LINK, VAX Linker
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, VAX Linker
Explanation: An option that does not apply to a shareable image was
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, VAX Linker
Explanation: You specified an option in an options file that is ignored for
system images.
User Action: Remove the option.

2—447

Messages

OPTLIN,

options line in error 'text' 'text7 'text7

Facility: LINK, VAX Linker
Explanation: Errors were found on the command line during options file
processing.
User Action: None.
OPTSYNERR,

syntax error in options file 7file-name7

Facility: LINK, VAX Linker
Explanation: A syntax error was 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,

'name7 option value 'decimal-number7 is out of range ('decimalnumber7 to 'decimal-number') in options file 'file-name7

Facility: LINK, VAX Linker
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$PASS_FILES, CONV$PASS_OPTIONS, and
CONV$CONVERT.
User Action: Fix the order and try again.
ORG,

invalid file organization value

Facility: RMS, VAX Record Management Services
Explanation: An invalid file organization was encountered on an open
service or specified for a $ CREATE service. Files must be either sequential,
relative, or indexed, unless block I/O processing is requested.
User Action: Verify that the call to the VAX RMS service was 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 'record
number'

Facility: PSM, Print Symbiont
Explanation: This status is returned indicating operating system command
string was longer than allowed in this record number.
User Action: None.

2-448

Messages

OUTCMDLNG,

output command line too long for buffer

Facility: PATCH, VAX Image File Patch Utility
Explanation: An internal PATCH error has occurred.
User Action: Submit a Software Performance Report.
OUTCONERR,

output conversion error

Facility: OTS, Language Independent Run-Time Library Support Procedures
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.
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.

2-449

Messages

OUTPUTERR,

error opening primary output filq SYS$OUTPUT

Facility: LOGIN, Login Processor
Explanation: An error occurred while trying to open SYS$OUTPUT. An
accompanying message will provide more information.
User Action: Correct the problem described by the accompanying message,
and try again.
OUTPUTLOST,

output being lost, both NOTERMINAL and NOLOG are in effect

Facility: DEBUG, VAX/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 was either too small or too large.
User Action: Reissue the command specifying a number within the range of
1 to 127
OUTSIMG,

attempted store location 'address' is outside 'name'
('address' to 'address') in module 'module-name' file 'file-name'

Facility: LINK, VAX Linker
Explanation: An attempt was 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 'file-name'

Facility: LINK, VAX Linker
Explanation: An attempt was 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.

2-450

Messages

OUTSTRTRU,

output string truncated

Facility: LIB, Run-Time Library General Procedures
Explanation: The source and destination strings are character coded text
datum, and the destination string cannot contain all of the output string.
User Action: None. The output string is truncated.
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: Reissue the SYSGEN command CONFIGURE with the correct
number of controllers.
OVERLAY,

'file-spec' being overwritten

Facility: Shared by several facilities
Explanation: A file is being successfully overwritten.
User Action: None. This message is a success return.
OVRALI,

conflicting alignment on overlayed psect 'psect-name' in module
'module-name' file 'file-name'

Facility: LINK, VAX Linker
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, VAX/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. This message is a success return.

2-451

Messages

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
a byte be deposited in a byte.
User Action: Verify the value and the area to receive it; correct the value or
the receiving area and reenter the command.
PACTOOLONG,

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.

page(s) 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.
PAGECRIT,

page file space critical, system trying to continue

Facility: SYSTEM, VAX/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 VAX/VMS
System Manager's Reference Manual.
PAGEFRAG,

page file badly fragmented, system continuing

Facility: SYSTEM, VAX/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 VAX/VMS
System Manager's Reference Manual.

2—452

Messages

PAGEREDERR,

Page read error

Page write error

Page not in transition or valid

page owner violation

Facility: SYSTEM, VAX/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-453

Messages

PAGRDERR,

page read error, reason mask = 7xx7, virtual address = 'location7, PC
= 'location7, PSL = 'xxxxxxxx7

Facility: SYSTEM, VAX/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. If the
failure persists, notify the system manager.
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 7x7 for /PARALLEL is greater than /MATCH value of 7y7,
/PARALLEL set to 7y7

Facility: DIFF, DIFFERENCES Command
Explanation: A /PARALLEL value was specified that was 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.
PARITY,

parity error

Facility: SYSTEM, VAX/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
DR11-W interface, a parity error was detected in a block mode transfer when
the Buffered Data Path of the UNIBUS adapter was purged.
If this message is associated with a status code returned by a request to a
DR32 interface, either the microcode was not loaded successfully or the DR32
controller detected a parity error and a hardware malfunction is indicated.
The second longword of the I/O status block contains additional information
pertaining to this malfunction for the DR32; the following bit values are
associated with SS$_PARITY:
XF$V_IOS_WCSPE
XF$V_IOS_CIPE
XF$V_IOS_DIPE
XF$V_IOS_PARERR
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:

2-454

•

Drive parity error

•

ECC hard error

•

Header compare error

Messages

•

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:
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
LPA11-K driver, a parity error occurred in a UBA-buffered datapath.
If this message is associated with a status code returned by a request to a
terminal driver, a parity bit mismatch was detected by the device interface
during a read operation. The I/O operation stopped when the mismatch was
detected. (Data was 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 I/O request
was directed.
PARMDEL,

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, VAX/VMS System Services
Explanation: A programming error has occurred because an attempt was
made to create a sublock under a parent lock that was not granted.
User Action: Correct the programming error and retry.

2-455

Messages

PARSE,

error opening 'file-spec'

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

internal parsing error

Facility: PATCH, VAX Image File Patch Utility and DEBUG, VAX/VMS
Debugger
Explanation: This message indicates either an internal PATCH error or an
internal debugger error.
User Action: Submit a Software Performance Report.
PARSEERR,

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 was 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 'file-spec'

Facility: VAX Text Processing Utility
Explanation: An error was detected by VAX RMS while parsing a file
specification. This message should be accompanied by a VAX RMS message
explaining the reason for the failure.
User Action: Follow the recovery procedure for the specified VAX RMS
message.
PARSEFAIL,

error parsing 'file-spec'

Facility: Shared by several facilities
Explanation: An error was detected while parsing an input command or
source line.
User Action: Correct the error.
PARSEOVER,

Parser stack overflow

Facility: VAX Text Processing Utility
Explanation: The program is too complex for VAXTPU to evaluate.
User Action: Simplify the expression.

2-456

Messages

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

parse stack overflow, simplify expression

Facility: DEBUG, VAX/VMS Debugger
Explanation: The expression was too complex for the debugger to evaluate.
User Action: Simplify the expression.
PARTCOPIED,

file 'filename' partially copied to 'filespec'

Facility: EXCHANGE, Exchange Utility
Explanation: The EXCHANGE utility had copied part of a file before an error
was discovered.
User Action: This message is followed by another message describing the
specific error which occurred. Take corrective action based on the second
message.
PARTESCAPE,

partial escape

Facility: SYSTEM, VAX/VMS System Services
Explanation: A terminal escape sequence was only partially stored because
the buffer space was exhausted before the sequence was 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, VAX/VMS System Services
Explanation: A call was issued to the $CRMPSC system service to map a
section file; the ACP was 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.
PASALREXI,

pasteboard already exists for this device

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: A user tried to create a pasteboard for a device, when one
was already created. This is normal in a modular environment. The existing
pasteboard id is returned.
User Action: None. Make sure you don't delete a pasteboard that you
actually did not create.

2-457

Pass bad status to caller
Facility: EDT, EDT Editor
Explanation: While using callable EDT, the bad status was 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, VAX Image File Patch Utility
Explanation: An internal PATCH error has occurred.
User Action: Submit a Software Performance Report.
PATHAMBIG,

line line-number7: Path 'path-name7 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, VAX/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, VAX Image File Patch Utility, DEBUG, VAX/VMS
Debugger
Explanation: You entered a pathname consisting of more than 15 elements.
User Action: Remove excess elements and retry.
PATHUNDEF,

line 7line-number7: Path 7path-name7 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-number7: Path 'path-name7 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.

Messages

PATOVER,

Pattern stack overflow

Facility: 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, Run-Time Library Screen Management Procedures
Explanation: The operation you have tried to perform is not legal while
output to the pasteboard is being batched. For example, you can't 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, VAX 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 VAX RMS service was coded correctly.
Specifically, check the address specified for the prompt buffer.

PCI,

'file-spec'
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.

PC3,

'n' table-of-contents record[s] 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 request 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: Reissue the MONITOR request, specifying only one display
type qualifier for the PROCESSES class.

2—459

Messages

PENDING,

asynchronous operation not yet completed

Facility: RMS, VAX Record Management Services
Explanation: The program requested a VAX RMS asynchronous I/O
operation; the operation was initiated but was not completed.
User Action: None. The message is a success status code.
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 was accepted but not completed.
User Action: None.
PES,

partial escape sequence
Facility: RMS, VAX Record Management Services
Explanation: The user buffer filled before a complete escape sequence was
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, VAX/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

2-460

Messages

PFNREFNZRO,

PFN reference count nonzero

Pagefault, global page table entry bad format

Pagefault with IPL too high

Pagefault, location field has bad value

2-461

Messages

PH2INV,

function is invalid for phase II executor node

Facility: NCP, Network Control Program
Explanation: The NCP command cannot be performed by a phase II executor
node. Either the command, an option, or a parameter was invalid.
User Action: None. Remove the invalid command, option, or parameter.
PHYDEVGEO,

device type of 'device' 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 VAX/VMS Backup Utility Reference Manual for
information on the /PHYSICAL command qualifier and reenter the command.
PHYSET,

physical save set supplied to nonphysical operation

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

2-462

Messages

PLV,

unsupported prolog version
Facility: RMS, VAX Record Management Services, 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 VAX RMS.
User Action: Verify the version of VAX RMS that you are using; use the
correct version to process the file.

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, VAX/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.
This condition can result from a fragmented disk or from an unusually large
number of open files.
User Action: Examine the status of the small packet (SRP), I/O 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. You may also want to consider adding memory to the
system.
POS,

invalid key position (greater than MRS) for key = 7nnn7
Facility: RMS, VAX 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 VAX RMS service
was coded correctly.

POSERROR,

error positioning 'file-spec7

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.

2-463

Messages

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, VAX/VMS System Services
Explanation: A power failure occurred while a request was active or the
device is powered down. If this message is associated with a status code
returned by a request to an LPA11-K driver, a power failure occurred while a
request was active. (Only for the start microprocessor, initialize LPA11-K, set
clock, and start data transfer request functions.)
User Action: If appropriate, rerun the program.
PRCREAT,

error creating process

Facility: JBC, Job Controller
Explanation: The job controller encountered an error in creating a process
for a terminal that was 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, Run-Time Library Screen Management Procedures
Explanation: A previous key definition was replaced by a new definition.
User Action: None.
PREMATUREEOF,

Premature end-of-file detected

Facility: VAX Text Processing Utility
Explanation: The program parsed correctly until the compilation stopped.
However, the compilation stopped because the end of the program was
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 'file-name'

Facility: LINK, VAX Linker
Explanation: The options file ended before the end of a continued line was
found.
User Action: Correct the options file and relink.

2-464

Messages

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 was 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 was
the MONITOR recording file you desired. Then, reissue the MONITOR
request.
PRESENT,

entity value is present in command string

Facility: CLI, Command Language Interpreter (DCL)
Explanation: This status is returned by the CLI$PRESENT CLI interface
routine to indicate that the specified entity is explicitly present in the
command line.
User Action: None.
PREVINIT,

patch area has previously been initialized

Facility: PATCFI, VAX Image File 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 7n7

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the primary index file header on
the specified relative volume was corrupted.
User Action: None. The primary index file header is refreshed from the
alternate index file header.
PRIMIN,

error code of 7xx7 parsing input file

Facility: PATCH, VAX Image File Patch Utility
Explanation: A command interpreter callback request failed due to the error
represented as 7xx7.
User Action: Correct the error (represented as xx) and retry.
PRIMOUT,

error code of 7xx7 parsing journal file

2-465

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

private terminal table used

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: The requested terminal definition was found in the caller's
private copy of Termtable.
User Action: None.
PRIV,

privilege error

Facility: CNF, NI Configurator
Explanation: NICONFIG was executing without all the necessary privileges.
User Action: See the accompanying message(s) for the missing privileges;
install NICONFIG with all the required privileges.
PRIVINSTALL,

shareable images must be installed to run privileged image

Facility: SYSTEM, VAX/VMS System Services
Explanation: Shareable images must be installed to run a privileged image.
User Action: Ask the system manager to install all shareable images used by
executable images installed with privileges.

2-466

Messages

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

parameter value out of range

Facility: NCP, Network Control Program
Explanation: A numeric parameter value has an invalid range.
User Action: Reenter the command with an appropriate parameter value.
PROCESSEND,

Subprocess terminated

Facility: VAX Text Processing Utility
Explanation: A VAX/VMS subprocess that was 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 'file-name'

Facility: DSRTOC, DIGITAL Standard Runoff Table of Contents Utility
Explanation: This informational message indicates that DSR has begun
processing the file.
User Action: None.
PROCGONE,

Process not in system

2-467

PROC—ID,

identification of created process is 'process-id7

Facility: RUN, Run Detached Utility
Explanation: The newly created process has an identification number of
'process-id7.
User Action: None. This is an informational message.
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, [000000]INDEXF.SYS;1, 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.
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: None.
PROERR,

error protecting 'filename'

Facility: SET, SET Facility
Explanation: An error occurred when the file's protection was being set. This
message is issued with an accompanying message.
User Action: Take corrective action based on the accompanying message.
PROERR,

error reading prologue

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

prolog checksum error at VBN = 'nnn'

Facility: CONVERT, Convert Utility, CONVERT, Convert/Reclaim Utility
Explanation: The specified block of the file's prolog 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.

Messages

PROFRANOT,

proper frame not found on call stack for 'variable'

Facility: DEBUG, VAX/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: VAX Text Processing Utility
Explanation: An internal VAXTPU failure occurred.
User Action: Submit a Software Performance Report.
PROL—WRT,

prolog write error

protection on 'file' not changed

Facility: SET, SET Facility
Explanation: The protection on the file was not changed. This message is
issued with an accompanying message.
User Action: Take corrective action based on the accompanying message.
PROTECTED,

'file-name' file protection changed to 'protection'
SET FILE/PROTECTION

Facility: SET, SET Facility
Explanation: The file protection has been successfully changed with the
/LOG qualifier.
User Action: None.
PROTECTED,

protection on 'file-spec' 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 was changed
to the value specified.
User Action: None. This message is informational.
PROTERR,

internal protocol error

Facility: REM, Set Host Facility
Explanation: A system internal error has occurred.
User Action: Submit a Software Performance Report.

2—469

Messages

PROTINSTALL,

protected images must be installed

Facility: SYSTEM, VAX/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.
PROTOCOL,

network protocol error

Facility: SYSTEM, VAX/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 VAX/VMS
Networking Manual for additional information.
PROTOOLON,

prompt-string is too long

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: The length of a prompt string exceeded 512 characters.
User Action: Shorten the prompt to 512 characters or less.
PRV,

insufficient privilege or file protection violation
Facility: RMS, VAX 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 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.
PRVNOTFND,

invalid privilege name

Facility: AUTHORIZE, Authorize Utility
Explanation: You specified an invalid privilege name.
User Action: See the VAX/VMS Authorize Utility Reference Manual for
information on valid privilege name.

2—470

Messages

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 for a privilege name to
make it unique.
User Action: Enter at least the first four characters of a privilege name.
PSCALI,

psect 'psect-name' alignment ('decimal-number') illegal in module
'module-name' file 'file-name'

Facility: LINK, VAX Linker
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 'file-name'

Facility: LINK, VAX Linker
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.
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 was 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 was empty.
User Action: Ensure that each .RESTORE_PSECT directive corresponds to a
.SAVE_PSECT directive.

2-471

Messages

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 directive(s).
PSTFULL,

process section table is full

Facility: SYSTEM, VAX/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

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 was aborted. The local node database was not affected.
User Action: None.

2-472

Messages

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, Run-Time Library General Procedures
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.
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 'file-spec'

Facility: PATCH, VAX Image File 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 was 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.

2-473

Messages

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.
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 was
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: Retype 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 entered
incorrectly 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 was used. Passwords may contain from 1
through 31 characters. The valid characters are:
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, a dollar
sign ($), or 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-474

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, VAX/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, VAX/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.
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).

QUALINV,

'class-name-qualifier' qualifier not valid for 'class-name' class

Facility: MONITOR, Monitor Utility
Explanation: An attempt was 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 issuing the following DCL command:
HELP MONITOR class_name_qualifiers

Then, reissue the MONITOR request.

2-475

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 was 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/QUEU/MANAGER command
QUERESET,

queue was reset during execution

Facility: JBC, Job Controller
Explanation: The queue was reset with a STOP/RESET command during
execution of the affected job.
User Action: Resubmit the job.
QUEUEMPTY,

Scheduling queue empty

queue was empty

Facility: LIB, Run-Time Library General Procedures
Explanation: The queue was empty, and is not modified.
User Action: None.
QUITTING
Editor successfully quitting
Facility: VAX Text Processing Utility
Explanation: You are quitting the VAXTPU 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, VAX Record Management Services
Explanation: The quoted foreign-filespec-string or the quoted task-spec-string
of a file specification does not have the correct syntax.
User Action: Use the DCL command HELP or refer to the VAX/VMS DCL
Dictionary, if necessary, for the correct syntax and reenter the file specification.

Messages

QUOTAFAIL,

failed to activate quota file; volume locked

Facility: MOUNT, MOUNT Command
Explanation: An error occurred that enabled the volume's quota file; the
volume was 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, [OOOOOOjQUOTA.SYS;l, on the output
volume was 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.
Quoted string required
Facility: EDT, EDT Editor
Explanation: A required quoted string was not supplied for the command
you entered. The * indicates the position of the required quoted string.
User Action: Reenter the command supplying the required quoted string.
RAB,

invalid RAB or RAB not accessible
Facility: RMS, VAX 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
was properly initialized, and that it was not inadvertently modified during
execution of the program.

RAC,

invalid record access mode
Facility: RMS, VAX 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 VAX RMS service was coded correctly.

RADRMOD,

reserved addressing fault at PC 'location', PSL = 'xxxxxxxx'

Facility: SYSTEM, VAX/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.

2-477

Messages

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,

numeric not within required range

Facility: NCP, Network Control Program
Explanation: A syntax error was detected.
User Action: Reenter the information correctly.
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.
RAT,

invalid record attributes
Facility: RMS, VAX Record Management Services
Explanation: The record attributes field of the FAB specified for a CREATE
or OPEN operation contains a value other than BLK, CR, FTN, or PRN, or an
invalid combination was specified.
User Action: Verify that the call to the VAX RMS service was coded correctly.

RAWFMT,

an invalid raw event was 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, VAX 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 VAX RMS service was coded correctly.

RDDELDATA,

read deleted data address mark

Facility: SYSTEM, VAX/VMS System Services
Explanation: This message is associated with read operations on RX02 disk
drives. A sector that has a deleted data address mark was successfully read.
User Action: None.

2-478

Messages

RDSNONRES,

Read data substitute page nonresident

error reading attributes for 'file-spec'

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'

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 'file-spec'

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'

Facility: BACKUP, Backup Utility
Explanation: The Backup Utility encountered an error during an attempt
to read the storage bit map file, [000000]BITMAP.SYS;1, 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-479

Messages

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,
[000000]INDEXF.SYS;1, 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.
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 i/o 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 was 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-spec'

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: None. If the Verify Utility finds lost files, it neither repairs nor
reports them until the error is corrected.
READERR,

error reading 'file-name'

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.

2-480

Messages

READERR,

error reading 'file-spec7

Facility: MACRO, VAX Macro Assembler
Explanation: The assembler encountered an I/O error when reading an input
source or macro library file; file-spec 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.
READERR,

error reading 'file-spec'

Facility: Shared by several facilities
Explanation: An input file specified cannot be read. This message is usually
accompanied by a VAX RMS message indicating the reason for the failure.
User Action: Take corrective action based on the associated message.
READERR,

Error reading 'input-file-spec'

Facility: VAX Text Processing Utility
Explanation: An input file cannot be read. This message should be
accompanied by a VAX RMS message indicating the reason for the failure.
User Action: Follow the recovery procedure for the specified VAX RMS
message.
READERR,

error while reading input

Facility: ACCOUNTING, Accounting Utility
Explanation: An input file specified cannot be read. This message is usually
accompanied by a VAX RMS message indicating the reason for the failure.
User Action: Take corrective action based on the associated message.
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 was 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.

2—481

Messages

READEVT,

error reading processed event record

Facility: EVL, Event Logger
Explanation: An error occurred while the event receiver was reading
incoming event records. As a result, an event was discarded.
User Action: Submit a Software Performance Report.
READFILE,

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

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') 'file-name' 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, [000000]INDEXF.SYS;1, on
the specified relative volume. The accompanying message provides additional
information.
User Action: None. The file header is rewritten with a deleted file header.
The /CONFIRM qualifier is ignored in this action.
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,
[000000]INDEXF.SYS;1, on the specified relative volume. The accompanying
message provides additional information.
User Action: None. The Verify Utility reconstructs the block.
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,
[000000]INDEXF.SYS;1, on the specified relative volume. The accompanying
message provides additional information.
User Action: None. The Verify Utility accepts the data as read.

2-482

Messages

READIMAP,

error reading index file bitmap on 'device'

Facility: BACKUP, Backup Utility
Explanation: The Backup Utility encountered an error during an attempt to
read the index file, [000000]INDEXF.SYS;1, 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.
READQUEHEADER,

Attempt to read queue header of dscb: 'address'

Facility: 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, [000000]QUOTA.SYS;1,
on relative Volume 1. The accompanying message provides additional
information.
User Action: None. The Verify Utility disregards quota information in the
block.
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, [000000]BITMAP.SYS;1, 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.
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,
[000000]BITMAP.SYS;1, 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.

2-483

Messages

READYREAD,

mount volume V on 'device' 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' 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: 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.
REALLYQUIT,

Buffer modifications will not be saved, continue quitting (Y or N)?

Facility: 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
was 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.

2—484

Messages

REALLYRECOVER,

Continue recovery (Y or N) ?

Facility: 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 Command
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 was 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 issuing 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 was only successful in writing to half of the last track
or less. This implies that the medium may be unreliable.
User Action: None. Continues to analyze the medium for surface defects.
REBUILD,

volume was improperly dismounted; rebuild in progress

Facility: MOUNT, MOUNT Command
Explanation: A disk was improperly dismounted and information was lost.
User Action: None. REBUILD will reconstruct the file structure on the
volume.
RECADD,

new database record added

Facility: NCP, Network Control Program
Explanation: The addition was completed successfully.
User Action: None.
RECGTRBL,

record size is greater than block size

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

2-485

RECISDEL,

Deleting a record already marked as deleted

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

file 'file-name7 has a record of illegal length ('decimal-number')

Facility: LINK, VAX Linker
Explanation: A record in a file was 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.
RECLOSEIN,

error closing input recovery file

Facility: ACLEDIT, Access Control List Editor
Explanation: The ACL editor encountered an error closing the recovery
journal file.
User Action: Examine the secondary error status to determine exactly why
the recovery journal file closing failed (privilege violation, device write locked,
etc.)
RECOPENIN,

error opening 'file-name' as input recovery file

Facility: ACLEDIT, Access Control List Editor
Explanation: The ACL editor was unable to open the specified recovery
journal file.
User Action: Examine the secondary error status to determine exactly why
the journal file creation failed (privilege violation, device write locked, etc.)
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.

Messages

RECORDSWL,

'device-name7 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 reissue
the BACKUP command.
RECOVER ABORT,

Recovery aborted by journal file inconsistency. Journal file
closed

Facility: VAX Text Processing Utility
Explanation: An inconsistency was 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: 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.
RECOVERFAIL,

Recovery terminated abnormally; journal file inconsistency

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

error reading 'file-name' recovery file

Facility: ACLEDIT, Access Control List Editor
Explanation: The ACL editor encountered an error trying to read the
recovery journal file.
User Action: Examine the secondary error status to determine exactly what
caused the read failure.
RECTOBIG,

'record-size' byte record too large for MAIL buffer

Facility: MAIL, Personal Mail Utility
Explanation: MAIL encountered an oversized record during a read operation.
User Action: The message is in an illegal format and should be deleted.

2—487

Messages

RECTOOBIG,

record too large in 'filename'

Facility: EXCHANGE, Exchange Utility
Explanation: The EXCHANGE utility discovered a record which was 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'

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 'file-name' has a record of illegal type ('decimal-number')

Facility: LINK, VAX Linker
Explanation: An illegal object record type was encountered.
User Action: Submit a Software Performance Report on the appropriate
language translator.
RECTYP,

illegal record type 'type' in module 'module-name' in 'library file-spec'

Facility: LIBRAR, LIBRARY Command
Explanation: The specified object module contains an illegal record type.
User Action: Recompile the module and reenter the command string.
RECUPD,

current database record updated

Facility: NCP, Network Control Program
Explanation: The update operation completed successfully.
User Action: None.
RECURLEARN,

The key defined cannot be part of the learn sequence

Facility: VAX Text Processing Utility
Explanation: The key definition that you passed to the built-in procedure
DEFINE _KEY was used as a part of a learn sequence. This causes a recursive
action in the learn sequence and the sequence loops infinitely. Therefore, the
key definition cannot be used in this context.
User Action: Assign the learn sequence to a different key.

2-488

Messages

REDCACHE,

Volume mounted with reduced cache size

Facility: MOUNT, MOUNT Command
Explanation: There is insufficient dynamic memory to allocate the file system
buffer caches from paged pool. The amount of paged pool used is controlled
by the SYSGEN parameters ACP—HDRCACHE, ACP_MAPCACHE,
ACP—DIRCACHE, and ACP—DINDXCACHE. If the reduced cache size does
not compromise the performance of the file system, you can treat this as an
informational message that does not require any action on your part.
User Action: Increase the value of the SYSGEN parameter PAGEDYN, or
reduce the values of ACP—HDRCACHE, ACP-MAPCACHE,
ACP—DIRCACHE, and ACP—DINDXCACHE. Then reboot the system. Also,
if the /PROCESSOR qualifier was used with the MOUNT command that
mounted the volume, set the value of the SYSGEN parameter
ACP—MULTIPLE to zero. Then remount the volume without the
/PROCESSOR qualifier. In this way, shared file system block cache will
be used instead of dedicated file system cache.
REDCACHE,

volume mounted with reduced cache size

Facility: MOUNT, MOUNT Command
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 VAX/VMS Version 4.0 was to avoid the problem of file system activity
on one volume degrading file system performance on other volumes. This
degradation was caused by the single-threaded nature of the file system ACP.
In VAX/VMS Version 4.0, the procedure-based file system XQP provides a
higher level of concurrency than was previously possible even with multiple
ACPs. The /PROCESSOR qualifier was retained to allow discrete I/O buffer
caches to be associated with specific volumes, instead of all volumes sharing
the same I/O 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, VAX Image File Patch Utility
Explanation: A user-defined symbol was changed to a different value. This
typically occurs when you issue 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-489

Messages

REENT,

file could not be renamed and recovery failed; file has been lost

Facility: RMS, VAX Record Management Services
Explanation: A VAX 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: Use the ANALYZE/DISK/REPAIR utility to recover the lost
file.
REENTER,

please reenter last line as it was ignored

Facility: MAIL, Personal Mail Utility
Explanation: MAIL encountered an illegal escape sequence during a send
operation. The line containing the ilegal escape sequence is ignored.
User Action: Reenter the line without illegal escape sequences.
REF,

invalid key-of-reference = 'nnn'
Facility: RMS, VAX 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 VAX RMS service
was coded correctly.

REFCNTNEG,

PFN reference count is negative

Facility: System Bugcheck
Explanation: The VAX/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.)
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 reissue the DELETE/FORM or
DELETE/QUEUE command.
REFUSED,

you cannot attach to that process

Facility: CLI, 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.
User Action: None. You cannot perform the attempted operation.

2-490

Messages

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, VAX/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.
RELINK,

file 'file-name' contains deferred relocation. Relink 'file-name' and all
images linked against it

Facility: LINK, VAX Linker
Explanation: The specified shareable image file was linked under the
VAX/VMS V2.0 or V2.1 linker.
User Action: Relink the specified shareable image.
RELINK,

obsolete image header - please relink

Facility: SYSTEM, VAX/VMS System Services
Explanation: An obsolete image header was detected. Also, a restriction on
shareable images can cause this error. When an executable image is linked,
all sharable images referenced by this image are recorded in its image header.
If some shareable image is later relinked so that it references a shareable
image not already recorded in the image header of the executable image, this
error occurs when you run the executable image.
User Action: Relink the image.

2-491

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 was included in the
COPY command, the remote node will not be 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 'file'

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: No user action is required.
REMOINSF,

node name specification or /RENAME missing from command line

Facility: PRINT, Print 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, VAX/VMS System Services
Explanation: An assignment for a transparent connect on a remote node
completed successfully.
User Action: None.

Messages

REMOUVOL,

REMOUNT relative volume nn (volume label) on 'device-name'

Facility: MOUNT, MOUNT Command
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.
REMOVED,

'directory' removed

Facility: SET, SET Facility
Explanation: The requested directory was removed successfully.
User Action: None.
REMOVED,

entry for 'file spec' has been removed

Facility: INSTALL, Install Utility
Explanation: The Known File Entry was successfully removed.
User Action: None. This is an informational message.
REMOVED,

symbol 'symbol name' removed from 'library file-spec'

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, VAX/VMS System Services
Explanation: An attempt was 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 VAX/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.

2-493

Messages

RENAMED,

'file-spec' renamed to 'file-spec'

Facility: Shared by several facilities
Explanation: This message is associated with the execution of a DCL
command RENAME. The name of the first file was 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.
RENMSG,

user record renamed

Facility: AUTHORIZE, Authorize Utility
Explanation: This message is informational.
User Action: No user action is required.
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 may appear only once in a command.
User Action: Reenter the command.
REPLACED,

'output-file-spec' being replaced

Facility: Shared by several facilities
Explanation: An output file is replaced successfully by a new version.
User Action: None.
REPLACED,

module 'module name' replaced in 'library file-spec'

Facility: LIBRAR, LIBRARY Command
Explanation: This success message is generated by the DCL command
LIBRARY.
User Action: None.
REPLACEERR,

replacement value too large for location

Facility: PATCH, VAX Image File 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.

2-494

Messages

REPLACERR,

error replacing 'module name' in 'library file-spec'

Facility: LIBRAR, LIBRARY Command
Explanation: An error occurred during a module replacement operation.
Either a VAX RMS error occurred or enough virtual memory is not available.
User Action: Ensure that the new file in the replacement operation is not
corrupt.
REPLAYFAIL,

An inconsistency has been discovered, halting execution

Facility: VAX Text Processing Utility
Explanation: A learn sequence stopped executing. The sequence of
keystrokes that was saved is inconsistent with the current actions. This is
probably because some keys have different definitions now than when the
learn sequence was 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: VAX Text Processing Utility
Explanation: During the execution of a learn sequence, an inconsistency was
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 was 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
was replayed.
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 keyword.
REQUEST,

service required on queue 'name' for job n user 'name'

Facility: JBC, Job Controller
Explanation: In response to the /OPERATOR qualifier of the PRINT
command, this message is desplayed at the operator's terminal. This message
is followed by the text specified with the /OPERATOR qualifier.
User Action: Take the reqested action and issue a START/QUEUE command
to restart the queue.

2-495

Messages

RER,

file read error
Facility: RMS, VAX Record Management Services
Explanation: Either VAX RMS could not read an input file, or a terminal read
error occurred.
User Action: If VAX RMS could not read the input file, the status value (STV)
field of the RAB contains a code that provides more information about the
condition. Take corrective action based on this status code.
If a terminal read error occurred, retype the input line.

RESET,

circuit was reset

Facility: SYSTEM, VAX/VMS System Services
Explanation: The virtual circuit was reset while this request was being
processed, or the circuit was in the process of being reset when you issued
the request.
User Action: Initialize the circuit and retry the call.
RESIGNAL,

resignal condition to next handler

Facility: SYSTEM, VAX/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, VAX Image File Patch Utility, and DEBUG, VAX/VMS
Debugger
Explanation: You specified an opcode that is reserved for DIGITAL use only.
User Action: None.
RESTOREFAIL,

Error during RESTORE operation

Facility: VAX Text Processing Utility
Explanation: An error occurred while VAXTPU was restoring a section file.
This message should be accompanied by a VAX 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 VAX RMS message to make sure
that you are trying to restore a valid section file.
RESULTOVF,

resultant string overflow

Facility: SYSTEM, VAX/VMS System Services
Explanation: A user buffer specified to receive data from the system was 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.

2-496

Messages

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 at line 'integer'

Facility: VAX Text Processing Utility
Explanation: A CASE statement was 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.
REX,

record already exists
Facility: RMS, VAX 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 was not written.
User Action: Note the condition. Modify the source 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.

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.

RFA,

invalid record's file address (RFA)
Facility: RMS, VAX Record Management Services
Explanation: The record's 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 VAX RMS service was coded correctly.

2—497

Messages

RFAERR,

RMS error using RFA access: RFA = xxxxxx, xxx

Facility: SEARCH, SEARCH Command
Explanation: SEARCH received an error from VAX 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 was on another network node, and
one of the additional messages was "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. Antoher 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
VIRTU ALP AGECNT.
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, VAX Record Management Services
Explanation: The record format field of the FAB does not contain a valid
value.
User Action: Verify that the call to the VAX RMS service was coded correctly.
The valid values for this field are FIX, STM, STMCR, STMLF, VAR, VFC, and
UDF.

RHB,

invalid record header buffer
Facility: RMS, VAX 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 VAX RMS service was coded correctly.

2-498

Messages

RLF,

invalid related NAM block
Facility: RMS, VAX 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 VAX RMS service was coded correctly.

RLK,

target record currently locked by another stream
Facility: RMS, VAX Record Management Services
Explanation: The target record is locked by another stream.
User Action: Note the condition. Modify the source program, if necessary, to
detect and respond to the condition.

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

record IO error on file 'file-spec'

Facility: NCP, Network Control Program
Explanation: A read or a write to file failed.
User Action: Ensure that the disk drive is functioning properly.
RMSERROR,

RMS service error

Facility: Shared by several facilities
Explanation: An error was encountered during a VAX RMS operation. A
subsequent message explains the reason for the error.
User Action: Retry the operation; refer to the VAX Record Management
Services Reference Manual for more information.

2-499

RMV,

ACP remove function failed

Facility: RMS, VAX Record Management Services
Explanation: A file could not be removed or renamed correctly.
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.
RNF,

record not found
Facility: RMS, VAX 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 was never written or
it has been deleted.
User Action: Note the condition. Modify the source program, if necessary, to
detect and respond to the condition.

RNL,

record not locked
Facility: RMS, VAX Record Management Services
Explanation: The record specified for a VAX RMS $FREE or $RELEASE
operation was not locked.
User Action: Note the condition. Modify the source program, if necessary, to
detect and respond to the condition.

ROP,

invalid record options
Facility: RMS, VAX Record Management Services
Explanation: An incorrect record option was specified.
User Action: Verify that the call to the VAX RMS service was coded correctly.

ROPRAND,

reserved operand fault at PC location7, PSL = 'xxxxxxxx'

Facility: SYSTEM, VAX/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, VAX 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.

Messages

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

unmatched right parenthesis found

Facility: DEBUG, VAX/VMS Debugger
Explanation: A right parenthesis ()) was found but the left parenthesis (()
was missing.
User Action: Include the left parenthesis (().
RPL,

error detected while reading prolog
Facility: RMS, VAX Record Management Services
Explanation: An I/O error occurred during an attempt to read the file's
prolog.
User Action: Depending on the operation, the status value (STV) field in the
FAB or RAB contains a status code that provides additional information about
the condition. Take corrective action based on this status code.

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 was 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 'oper-name'

Facility: OPCOM, Operator Communication
Explanation: An operator request was denied by the DCL command
REPLY/ABORT.
User Action: None.
RQSTCAN,

request 'nnn' was canceled

Facility: OPCOM, Operator Communication
Explanation: An operator request was successfully canceled.
User Action: None.

2—501

Messages

RQSTCMPLTE,

request ,nnn/ complete by operator 'oper-name7

Facility: OPCOM, Operator Communication
Explanation: An operator has completed a user's request successfully; the
dialog between the user and the operator is complete.
User Action: None. This message is success.
RQSTDONE,

request 'number7 was satisfied

Facility: OPCOM, Operator Communication, MOUNT, MOUNT Command
Explanation: The request completed successfully and was canceled by the
requestor.
User Action: No action is required.
RQSTPEND,

request 'nnn' pending by operator 'oper-name7

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.
User Action: None. This message is informational. If the request must be
satisfied immediately, use CTRL/C to interrupt the request and send another
message.
RQSTSTST,

request status for request 'number7

Facility: OPCOM, Operator Communication
Explanation: This message provides the operator with additional, detailed
information about the request.
User Action: No action is required.
RRV,

invalid RRV record encountered
Facility: RMS, VAX Record Management Services
Explanation: An invalid record reference vector (RRV) record was detected.
This indicates either a previous failure to update RRV records (see RVU error
message) or a VAX RMS or system software error.
User Action: Reorganize the file. 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, VAX Record Management Services
Explanation: An attempt was made to issue a VAX RMS record operation to
a record stream that has an outstanding asynchronous request.
User Action: Note the condition. Modify the source program, if necessary, to
detect and respond to the condition. Include a $WAIT request before issuing
any additional requests.

2-502

Messages

RSBREFNEG,

RSB reference count negative

Tried to deallocate RSB with non-zero ref. count

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, VAX Record Management Services
Explanation: The VAX 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 VAX RMS service was coded correctly.

RSLOVF,

buffer overflow - specify fewer command elements

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

2-503

Messages

RSRVDOPRAND,

illegal variable value (Reserved Operand)

Facility: DEBUG, VAX/VMS Debugger
Explanation: A variable has an illegal value that causes a Reserved Operand
fault when used in a conversion or other operation. For example, a packed
decimal variable containing a bit pattern that is not a valid packed decimal
value could indicate that the variable has not been initialized or that it has
been destroyed.
User Action: Use the DEBUG command EXAMINE/HEX to examine the
variable in hexadecimal in order to identify the incorrect value.
RSS,

invalid resultant string size
Facility: RMS, VAX 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
VAX RMS operation.
User Action: Verify that the call to the VAX RMS service was coded correctly.

RST,

invalid resultant string address
Facility: RMS, VAX 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 VAX RMS service was coded correctly.

RSTERR,

error in symbol table

Facility: DEBUG, VAX/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.
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, VAX Record Management Services
Explanation: The record size (RSZ) field of the RAB contains an invalid value
for one of the following reasons:

2-504

•

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.

Messages

•

The record size value was 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 32767 for
the $PUT and $UPDATE services, and in the range of 1 through 65535 for
the $WRITE service.
User Action: Verify that the call to the VAX RMS service was 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.

RTll—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.
RTll—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 was 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 RT11—OVERFLOW for tips on making space available.
RTll—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.

2-505

RTll—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.
RTll—EXTRA,

extra words set to maximum of 119

Facility: EXCHANGE, Exchange Utility
Explanation: The EXCHANGE utility reduced the value on
a /EXTRA_WORDS qualifier to the maximum allowed.
User Action: In the future, use a smaller value for extra words.
RTll_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.
RTll_OVERFLOW,

directory is full, unable to add file

Facility: EXCHANGE, Exchange Utility
Explanation: The EXCHANGE utility was unable to add a file to an RT-11
directory because there was 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.
RTll_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.

Messages

RTll_TOOMANYBLK,

too many blocks, using maximum allocation of !UL

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
65535, whichever is smaller.
RTll__TOOMANYSEG,

too many segments, reducing to !UL

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 RTll_ERRLOCK for information on how to restore the
volume.
RTB,

'nnn' byte record too large for user's buffer
Facility: RMS, VAX 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 was 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 'string7
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 was
specified, processing will stop.
User Action: Specify the /TRUNCATE qualifier.

2-507

Messages

RTNERROR,

unexpected error status from user-written routine

Facility: SORT, VAX 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,

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 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.
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 was specified, then processing will stop.
User Action: Specify one of the /PAD qualifier options.

RUF,

Fatal error detected by Recovery Unit Facility
Facility: System Bugcheck
Explanation: The VAX/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-508

Messages

RVN1NOTMT,

root volume is not mounted

Facility: MOUNT, MOUNT Command
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 reissue 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, VAX Record Management Services
Explanation: VAX 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 VAX RMS RRV
updating. All records are accessible by primary key only. RRV errors may
subsequently occur.
User Action: Reorganize the file.

SAMEFILE,

files are identical

Facility: DIFF, DIFFERENCES Command
Explanation: This successful message is returned by DIFF if the two files
being compared are identical.
User Action: None.
SAVEERROR,

Error during SAVE operation

Facility: VAX Text Processing Utility
Explanation: An error occurred while VAXTPU was saving a section file.
This message should be accompanied by a VAX 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 VAX RMS message to make sure
that you are trying to save a valid section file.
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-509

SBIAERROR,

Fatal SBIA error

Scan dead page table error

SCB physical read error halt

failed to schedule wakeup request for process 'process id'

Facility: RUN, Run Detached Utility
Explanation: The system service $SCHDWK 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 waked up, so it
must be deleted and recreated.

Messages

SCRBUFOVF,

screen buffer overflow

Facility: LIB, Run-Time Library General Procedures
Explanation: While buffering was 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.
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
was already full.
User Action: None. The Bad Block Locator Utility, upon determining that
the SDBSF is full, will terminate the analysis.
SDBSFRFAIL,

failed to read the software detected bad sector file on 'devicename7

Facility: BAD, Bad Block Locator Utility
Explanation: The Bad Block Locator Utility could not locate a valid SDBSF.
User Action: None. The Bad Block Locator Utility, upon determining that no
SDBSF exists, will terminate the analysis.
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.
SEARCHFAIL,

Error searching for 'file-spec7

Facility: VAX Text Processing Utility
Explanation: The specified file could not be found. An accompanying VAX
RMS message should explain why.
User Action: Follow the recovery procedure for the specified VAX RMS
message.
SEARCHFAIL,

error searching for 'file-spec'

Facility: Shared by several facilities
Explanation: The specified file could not be found. A subsequent error
message explains why.
User Action: None.
SEARCHFAIL,

error while searching for file

Facility: ACCOUNTING, Accounting Utility
Explanation: The specified file could not be found. A subsequent error
message explains why.
User Action: None.

2-511

Messages

SECINTFAI,

secondary interlock failure in queue

Facility: LIB, Run-Time Library General Procedures
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, VAX Image File 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

section table (process/global) is full

Facility: SYSTEM, VAX/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 was allocated at system
generation for the section tables. Notify the system manager of the deficiency.
SECTRESTORED,

'count7 procedure(s), 'count7 variable(s), 'count' key(s) restored

Facility: VAX Text Processing Utility
Explanation: The indicated items have been successfully restored from a
section file.
User Action: None.
SECTSAVED,

'count' procedure(s), 'count' variable(s), 'count' key(s) saved

Facility: VAX Text Processing Utility
Explanation: The indicated items have been saved in a section file.
User Action: None.

2-512

Messages

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, VAX 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 a prolog 3 was 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 VAX RMS service
was 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 was 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.
Select range is already active
Facility: EDT, EDT Editor
Explanation: You attempted to establish a select range when one was already
in effect.
User Action: None.
SELRANGEZERO,

Select range has 0 length

Facility: VAX Text Processing Utility
Explanation: The range you selected for the built-in procedure
SELECT_ RANGE has a length of 0; therefore, no characters were selected.
User Action: None.
SEND ABORT,

no message sent

Facility: MAIL, Personal Mail Utility
Explanation: You pressed CTRL/C while sending a mail message.
User Action: None.

2-513

Messages

SENDERR,

error sending to user 'user-name'

Facility: MAIL, Personal 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: VAX Text Processing Utility
Explanation: The operation to write to the mailbox for the subprocess's input
failed.
User Action: Recreate the subprocess.
SEQ,

primary key out of sequence (SEQ access)
Facility: RMS, VAX Record Management Services
Explanation: A VAX RMS $PUT service specified sequential access, and the
primary key value of the record was less than the previous record entered.
$PUT operations in sequential access mode must be in ascending order of
primary key value.
User Action: Note the condition. Modify the source program, if necessary, to
detect and respond to the condition.

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 'module-name' file 'file-name'

Facility: LINK, VAX Linker
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 'module-name' in 'library file-spec'

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.

2-514

Messages

SEQUENCE,

illegal record sequence in module 'module'

Facility: LIB, Run-Time Library General Procedures
Explanation: The Run-Time Library encountered severe format errors in the
shareable image you are trying to call.
User Action: Issue 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 was too large.
User Action: Reenter the command specifying a smaller number.
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 was too large.
User Action: Reenter the command specifying a smaller number.
SEQUENCE2,

illegal record sequence

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 was set.
User Action: None.
SETLIMIT,

too many volumes on volume set

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

2-515

Messages

SETMAX,

value set to maximum for parameter 'name7

Facility: SYSGEN, System Generation Utility
Explanation: The value entered in the SYSGEN command SET parameter
was larger than the maximum allowed. The maximum value was exceeded.
User Action: Verify the number you intend to use.
SETMIN,

value set to minimum for parameter 'name7

Facility: SYSGEN, System Generation Utility
Explanation: The value entered in the SYSGEN command SET parameter
was smaller than the minimum allowed. The minimum value was used.
User Action: Verify the number you intended to use.
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.
SHARTOOBIG,

new version of shareable image too big - relink all images

Facility: SYSTEM, VAX/VMS System Services
Explanation: The new version of a shareable image is too big.
User Action: Relink all images.
SHMGSNOTMAP,

shared memory global section not mapped during creation

Facility: SYSTEM, VAX/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 RELPAG
to zero.
SHMNOTCNCT,

shared memory not connected

Facility: SYSTEM, VAX/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.

2-516

Messages

SHOFIL,

unable to open output for SHOW or LIST

Facility: NCP, Network Control Program
Explanation: VAX RMS returned an error when attempting to open the
output file for either a SHOW or LIST command. The VAX RMS error code
describes the error condition.
User Action: Take corrective action based on the accompanying VAX 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: DUMP, DUMP Command
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 VAX/VMS System Dump Analyzer Reference 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.
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.

2-517

Messages

SHR,

invalid file sharing (SHR) options
Facility: RMS, VAX 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 VAX RMS service was coded correctly.

SHRCNTNEG,

PFN share count negative

COPY value for /SHARE qualifier ignored, using NOCOPY

Facility: LINK, VAX Linker
Explanation: /SHARE=COPY may no longer be specified in order to obtain
an image-private copy of a shareable image.
User Action: None.
SHRIDMISMAT,

ident mismatch with shareable image

Facility: SYSTEM, VAX/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 image(s) cannot be linked into a system image

Facility: LINK, VAX Linker
Explanation: An attempt was 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, VAX Linker
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

2-518

Messages

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
'file-name'

Facility: LINK, VAX Linker
Explanation: A reference to a psect in a shareable image was 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, VAX Linker
Explanation: A shareable image was 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.
SHRSYMREF,

reference to symbol 'symbol-name' is not position-independent in
psect 'psect-name' offset 'number' in module 'module-name' file
'file-name'

Facility: LINK, VAX Linker
Explanation: A reference to a symbol in a shareable image was 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 'file-name'

Facility: LINK, VAX Linker
Explanation: A symbol from another shareable image was specified in the
.TRANSFER directive.
User Action: Link with the object module(s) containing the symbol rather
than the shareable image.
SHUT,

local or remote node no longer accepting connects

Facility: SYSTEM, VAX/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.

2-519

Messages

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, Run-Time Library General Procedures
Explanation: A call was made to LIB$SIGNAL or LIB$STOP with no
arguments; LIB$_SIGNO_ARL was substituted.
User Action: None.
SIZ,

invalid key size for key = 'nnn'
Facility: RMS, VAX Record Management Services
Explanation: An invalid key size was specified in a key definition XAB. The
size is invalid for one of the following reasons:
•

It is greater than 255.

•

It is zero for a key data type STG.

•

It is greater than 16 for a key data type PAC.

•

It is other than zero or two for key data types BN2 and IN2.

•

It is other than zero or four for key data types BN4 and IN4.

•

It is other than zero or eight for key data types BN8 or IN8.

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 VAX RMS service
was coded correctly.
SIZETRUNC,

size field truncated to 32 bits

Facility: DEBUG, VAX/VMS Debugger
Explanation: The size of the entry in a VAX BLISS-32 field specification
was larger then 32. The debugger set the entry size to 32 and executed the
command.
User Action: None. This message is informational.
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.

2-520

Messages

SKPDAT,

image data records not beginning with $ ignored

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

terminal size (x columns by y lines) is too small

Facility: FDL, Edit/FDL Utility
Explanation: The value for x must be 80 or greater, and the value for y must
be 24 or greater on video terminals.
User Action: Set the terminal width to 80 or greater, and set the page length
to 24 or greater with video terminals; with nonvideo terminals, any page
length is acceptable.
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.
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.
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.
SPCIVC,

invalid collating sequence specification at line 'number'

Facility: SORT, VAX SORT/MERGE Utility
Explanation: The syntax you specified for your collating sequence is
incorrect.
User Action: Correct the syntax and reenter your specification.

2-521

SPCIVD,

invalid data type at line 'number'

Facility: SORT, VAX 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, VAX 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, VAX 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, VAX 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, VAX SORT/MERGE Utility
Explanation: Two possible explanations exist:
•

The sort process you specified in your specification file was 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.
SPCIVS,

invalid specification at line 'number'

Facility: SORT, VAX 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, VAX SORT/MERGE Utility
Explanation: You incorrectly specified the syntax in a /CONDITION clause
in your specification file.
User Action: Correct your specification file text.

Messages

SPCMIS,

invalid merge specification at line 'number'

Facility: SORT, VAX 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, VAX 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.
User Action: None; this message is a warning only and will not halt
processing.
SPCSIS,

invalid sort specification at line 'number'

Facility: SORT, VAX SORT/MERGE Utility
Explanation: You incorrectly requested sequence checking in a sort operation.
User Action: Correct your specification file text.
SPECIFY,

specify option ('valid-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.
SPL,

spool or submit of command file failed on $CLOSE
Facility: RMS, VAX Record Management Services
Explanation: The spool or submit command file option that was specified on
a $CLOSE operation failed. If the IFI field of the FAB is zero, the file was
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.

SPNAMLNG,

PSECT module 'module-name' file 'library file-spec' 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.

2-523

Messages

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

shared input or output files are not allowed - respecify

Facility: CLI, Command Language Interpreter (DCL)
Explanation: You used a file that was already opened by DCL as input or
output to SPAWN.
User Action: If input or output to DCL is SYS$INPUT or SYS$OUTPUT, do
not specify the input or output qualifier. See the SPAWN command in the
VAX/VMS DCL Dictionary for details on input and output interpretation.
SQO,

operation not sequential (SQO set)
Facility: RMS, VAX Record Management Services
Explanation: An attempt was 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 VAX RMS service was coded correctly.

SQUALERR,

more than one statistic qualifier specified for 'class-name7 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: Reissue the MONITOR request, specifying only one statistic
qualifier per class.
SQUROONEG,

square root of negative value user PC 'location7

Facility: MTH, Run-Time Library Math Procedures
Explanation: A mathematics library procedure was 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.

2-524

Messages

SRCLIN,

the source input entry was 'string7

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 was in error.
User Action: None. The duplicate block is ignored.
SRCLINNOT,

source lines not available for module 7xxx7

Facility: DEBUG, VAX/VMS Debugger
Explanation: The source lines from module xxx 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 DEBUG
for modules written in that language.
SRTIWA,

insufficient space; specification file is too complex

Facility: SORT, VAX 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.
SSCHANGE,

unexpected end of save set on 'device7

Facility: 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.
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 VAX/VMS System Services Reference Manual. Correct the
condition causing the failure, if possible, and reissue the MONITOR request.
Otherwise, submit a Software Performance Report.

2—525

SSFAIL,

system service failure exception, status = 'xxxxxxxx', PC = 'location', PSL
= 'xxxxxxxx'

Facility: SYSTEM, VAX/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 "Y (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, VAX 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.
STACKDUMP,

non-symbolic stack dump follows

Facility: TRACE, Traceback
Explanation: This message precedes a traceback dump. The accompanying
message indicates why the traceback is nonsymbolic.
User Action: None. This message is informational. The nonsymbolic stack
dump is displayed following this message.

Messages

STACKOVER,

Stack overflow during compilation

Facility: 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 'number7 in record 'number' in module
'module-name' file 'file-name'

Facility: LINK, VAX Linker
Explanation: An attempt was 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,

queue already started

Facility: JBC, Job Controller
Explanation: The queue cannot be started because it is already running.
User Action: None.
STARTED,

VAX PSI V 'version-number' ('mode'), network device 'device-name'
mounted

Facility: PSI, VAX Packetnet System Interface
Explanation: PSIACP has been started successfully. The version is n.n; the
mode is PSI mode and can be one or more of the following: native, multihost,
or access; and the network device is either NWAO: or NVAO:.
User Action: None.
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.

2-527

Messages

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

Software state not saved during powerfail

Facility: System Bugcheck
Explanation: Before power was lost, the volatile software state of the VAX
processor was 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: 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.
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, VAX Linker
Explanation: The linker encountered a nonrelocatable reference while linking
what was intended to be a position-independent shareable image.
User Action: Find the reference using the information in the message, and
make the reference relocatable.

2—528

Messages

STEFROEXC,

step from exception break is not allowed.

Facility: DEBUG, VAX/VMS Debugger
Explanation: An EXCEPTION BREAK occurred causing DEBUG to gain
control and then the DEBUG command STEP was entered. This is not
allowed because DEBUG does not know where control will go next,
resulting in an unknown number of condition handlers being invoked by
the VAX/VMS exception handling mechanism. These handlers may or may
not return control to the interrupted code.
User Action: Set a breakpoint where DEBUG should stop in a condition
handler, the interrupted code, or some other appropriate place. Then enter
GO (which will invoke all the condition handlers) or GO address (which
will cause execution to continue at "address" without invoking the condition
handlers).
STEPINTO,

cannot step over PC = xxx

Facility: DEBUG, VAX/VMS Debugger
Explanation: The debugger was unable to step over the routine and executed
a step into the routine instead.
User Action: None. This message is informational.
STGTRUNC,

string truncated

Facility: PATCH, VAX Image File Patch Utility and DEBUG, VAX/VMS
Debugger
Explanation: The Patch Utility truncated an ASCII string entry because it
exceeded the current length mode or because the entry was inappropriate for
the context in which it was 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 16 levels

Facility: CLI, Command Language Interpreter (DCL)
Explanation: The maximum level of nesting of command procedures was
exceeded. Too many procedures invoked other procedures.
User Action: Simplify the command procedure hierarchy to reduce the level
of nesting.

2-529

Messages

STKOVFLO,

stack of 'number' pages falls below control region to 'address'

Facility: LINK, VAX Linker
Explanation: The memory allocation for PI 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,

VAX PSI V 'version-number' ('mode'), network device _NWA0:
dismounted

Facility: PSI, VAX Packetnet System Interface
Explanation: The VAX PSI software has been unloaded. PSIACP has stopped
successfully. The version number is n.n, the mode can be one or more of the
following: native, multihost, or access.
User Action: None.
STR,

user structure (FAB/RAB) became invalid during operation
Facility: RMS, VAX Record Management Services
Explanation: During execution of a VAX RMS service, the control block
(FAB/RAB) became invalid. Either the address space containing the control
block was deleted or the control block was inadvertently overwritten by the
user or by VAX RMS. For example, the user record buffer overlaps the RAB
during a $GET service.
User Action: Verify that the call to the VAX RMS service was coded correctly.
Because the control block is not valid, no STS or STV value can be returned,
and this status value is returned only in RO.

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.

Messages

String delimiter must be non-alphanumeric
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 was 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, Run-Time Library General Procedures, OTS, Language
Independent Run-Time Library Support Procedures, STR, Run-Time Library
String Procedures
Explanation: Code being executed at AST level attempted writing into a
string that was being written into or whose length was 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-number7) should be
'decimal-number7 in module 'module-name' file 'file-name'

Facility: LINK, VAX Linker
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.
STRLVL,

illegal object language structure level in module 'module'

object structure level nnn unsupported in module 'module-name' in
'library file-spec'

Facility: LIBRAR, LIBRARY Command
Explanation: This error message is generated by the DCL command
LIBRARY. An illegally formatted object file was inserted.
User Action: Recompile the object file and insert it into the library.

2-531

Messages

STRNGPAD,

string operand lengths do not match, shorter zero extended on right

Facility: DEBUG, VAX/VMS Debugger
Explanation: The operands of a string comparison ( 'ABC7 < 7AB7 ) did not
have the same length. The shorter one is zero extended on the right.
User Action: Use strings of the same length.
STRNOTFOUND,

String not found

Facility: 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 strings

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: An SMG output routine was passed an escape sequence
embedded in the output string. The output string was written to the virtual
display but the string was terminated at the escape sequence.
User Action: Check your output string to determine what escape sequence
was being passed. If you need the action provided by this escape sequence,
there is most likely an SMG routine that performs that function.
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 at line 'integer7

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

2-532

Messages

STRTOOLNG,

string argument is too long - shorten

Facility: CLI, 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, Run-Time Library String Procedures
Explanation: An attempt was made to create a string that was longer than
allowed by the String Facility or the descriptors in the VAX/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, Run-Time Library General Procedures
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 'device7

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

structure size declared as xxx units, yyy was given

Facility: DEBUG, VAX/VMS Debugger
Explanation: The VAX BLISS-32 structure size was declared to be xxx units
but was referenced with yyy units.
User Action: None. This message is informational.
STRUCT—LEVEL,

system job queue file has incompatible structure level of n

Facility: JBC, Job Controller
Explanation: After opening the system job queeu file, the job controller
determined that the internal format of the queue file or revision level was
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 VAX /VMS or a 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.

2-533

Messages

SUBLOCKS,

cannot dequeue a lock with sublocks

Facility: SYSTEM, VAX/VMS System Services
Explanation: A programming error occurred because an attempt was 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 or 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 associated message.
SUBOUTVAL,

value xxx of subscript yyy out of bounds

Facility: DEBUG, VAX/VMS Debugger
Explanation: An attempt to subscript out of the bounds of an array was
made.
User Action: Change the value of the subscript.
SUBRNG,

arithmetic trap, subscript out of range at PC = 'xxxxxxxx', PSL 'xxxxxxxx'

Facility: SYSTEM, VAX/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 (nnn:mmm), was declared CHARACTER*ppp

Facility: DEBUG, VAX/VMS Debugger
Explanation: The substring specification (nnmmmm) is not within the bounds
defined for the CHARACTER data type.
User Action: Specify a substring specification within the bounds defined for
the data type.
SUC,

normal successful completion
Facility: RMS, VAX Record Management Services
Explanation: This success message indicates that the operation completed
normally.
User Action: None. This message is informational. It is not normally
displayed by the operating system.

2-534

Messages

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, VAX Record Management Services
Explanation: The requested VAX RMS operation failed because either the
specified remote node does not support the function or VAX RMS does not
support the function in a network context at the local node.
User Action: Consult the VAX/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, VAX Record Management Services
Explanation: The file created by a VAX RMS $CREATE operation superseded
an existing version of the same file.
User Action: None.
SUPERSEDE,

logical name superseded

Facility: SYSTEM, VAX/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 was deleted as the
result of a CREATE request.
User Action: None. This message is success. 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.
SUPERSEDED,

Definition of 'name' superseded at line 'integer'

Facility: VAX Text Processing Utility
Explanation: The key or procedure you are defining already had a definition.
The new definition you supplied replaces the old one.
User Action: None.

2-535

SUPPORT,

network operation not supported

Facility: RMS, VAX Record Management Services
Explanation: VAX RMS rejected the request because it is not supported
between two DECnet systems. The STV field contains either another VAX
RMS completion code or a FAL status code, depending on whether VAX RMS
at the local node or FAL at the remote node could not support the request.
User Action: The status value (STV) field contains a code that provides more
information about the condition. Take 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, VAX/VMS System Services
Explanation: The specified process was 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.
SWAPAGINS,

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.
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 allowed.
User Action: Remove the asterisk (*) from the symbol name.

Messages

SYMCREPRC,

error creating symbiont process for 'device7

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 was 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 was 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 was 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. Retype the command.
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.
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.

2-537

Messages

SYMNAMLNG,

'module type' module 'module-name' file 'library file-spec' 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 was a relative symbol
or was undefined.
User Action: Ensure that the symbol is defined as an absolute symbol.
SYMNOTACT,

symbol xxx not active or not in active scope

Facility: DEBUG, VAX/VMS Debugger
Explanation: The symbol xxx is not defined in an active call frame.
User Action: Check the symbol specified; if correct, ensure that you have
defined the scope correctly.
SYMOUTPHAS,

symbol out of phase

Facility: MACRO, VAX Macro Assembler
Explanation: A label definition specified a label that was defined later in the
module; or a local label definition specified a local label that was 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: CLI, 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 PI 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 (CLI)
symbol table by resetting the SYSGEN parameter CLISYMTBL. The format of
the command is SYSGEN SET CLISYMTBL 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

2—538

Messages

SYSGEN SET command sets the new value for the duration of your process
only. It does not change the permanent parameter value.
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.
SYMTOOLNG,

symbol 'symbol' 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 was 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
characters 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, VAX 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.

2-539

Messages

SYNCH,

synchronous successful completion

Facility: SYSTEM, VAX/VMS System Services
Explanation: This alternate success code indicates that the requested
operation completed synchronously and as expected.
User Action: None. The operation has completed successfully.
SYNERR,

syntax error

Facility: SMG, Run-Time Library Screen Management Procedures
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 'location7

Facility: PATCH, VAX Image File 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,

command syntax error at or near xxx

Facility: DEBUG, VAX/VMS Debugger
Explanation: The debugger encountered a command syntax error near the
element xxx.
User Action: 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 VAX/VMS DCL
Dictionary for the correct syntax and reenter the command.
SYNTAX,

invalid ACE syntax

Facility: ACLEDIT, Access Control List Editor
Explanation: The syntax of the ACE currently being entered is incorrect.
User Action: Please refer to the VAX/VMS Access Control List Editor Reference
Manual for a description of the proper ACE syntax.

2-540

Messages

SYNTAX,

parse failure

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 VAX/VMS DCL
Dictionary, for the correct syntax and reenter the command.
SYNTAX,

syntax error in statement n

Facility: FDL, Create/FDL Utility, FDL, Edit/FDL Utility
Explanation: An FDL syntax error was encountered.
User Action: Examine the specified line in the FDL file, determine which
validity rule was violated, and correct the line.
SYNTAX,

syntax error: 'string'

Facility: SYSGEN, System Generation Utility
Explanation: A syntax error was detected, 'string' displays the nonparsed
input.
User Action: Reissue the command with the correct syntax.
SYNTAXERR,

string syntax error detected by LIB$TPARSE

Facility: LIB, Run-Time Library General Procedures
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 on line 'count'

Facility: 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, VAX Record Management Services
Explanation: VAX RMS encountered an error while trying to issue a $QIO
system service request for an I/O operation. This message may occur if calls
to VAX 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 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 VAX RMS I/O operations.

2-541

Messages

SYSADJWSL,

System service adjust working set limit error

Facility: System Bugcheck
Explanation: The VAX/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.)
SYSBOOT-E-File not contiguous
Facility: SYSBOOT, System Bootstrap Facility
Explanation: The file specified by a USE command is not contiguous.
User Action: Create a contiguous parameter file.
SYSBOOT-E-I/O error reading file
Facility: SYSBOOT, System Bootstrap Facility
Explanation: An irrecoverable I/O error occurred while SYSBOOT was
reading a parameter file or the system image. If the error occurred while a
parameter file was being read, SYSBOOT does not perform the requested
action. If the error occurred while the system 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: Reissue the command specifying correct parameter names.
SYSBOOT-E-Syntax error
Facility: SYSBOOT, System Bootstrap Facility
Explanation: Your command contained a syntax error.
User Action: Correct the syntax and reissue the command.
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: Reissue the command specifying the correct file name or mount
the correct medium in the console drive.

2—542

Messages

SYSBOOT-F-Boot time files have too many non-contiguous pieces
Facility: SYSBOOT, System Bootstrap Facility
Explanation: The system dump, page, or swap file is severely fragmented.
User Action: Backup the system disk and then use the backup disk as the
new system disk.
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 SPT and PHD and 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 SYS.EXE
Facility: SYSBOOT, System Bootstrap Facility
Explanation: SYSBOOT cannot locate the system image file in directory
[SYSEXE] 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 VAX/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.

2-543

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-Continue from halt to proceed with boot if desired
Facility: SYSBOOT, System Bootstrap Facility
Explanation: A potentially serious condition (for example, a missing
hardware ECO) was detected, causing the processor to halt. This message
is usually issued with another message explaining the condition.
User Action: Call your local field service representative.
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 VAX/VMS. To
execute, every process requires a minimum fluid working set (MINWSCNT)
plus space for its process header (PHD).
User Action: None.
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 mimimum
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.

Messages

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
was specified) in the command and reenter the DCL command DISMOUNT
specifying the correct device.
SYSERROR,

System service error

Facility: VAX Text Processing Utility
Explanation: An error occurred while VAXTPU was using one of the
VAX/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.
SYSERROR,

system service error

Facility: Shared by several facilities
Explanation: An error was detected by a system service. A subsequent
message explains the reason for the error.
User Action: None.
SYSERRORPC,

'name7 system service error at PC = 'location7

Facility: Shared by several facilities
Explanation: An error was detected by a system service. A subsequent
message explains the reason for the error.
User Action: None.
SYSERROR[[PC]],

'testname7 system service error [[at PC 'location7]]

Facility: UETP, User Environment Test Package
Explanation: This message is a obsolete and 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 reissue the command.

2-545

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 initing a WCB
Facility: SYSINIT, System Initialization
Explanation: There is not enough nonpaged pool to create a window control
block that contains the virtual-to-logical block mapping information for a file.
User Action: Increase the amount of nonpaged pool by following the general
prescription for nonpaged pool and the bootstrap operation, and reboot the
system.
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-F11ACP initialization error
Facility: SYSINIT, System Initialization
Explanation: An error occurred while attempting to create the ACP for the
system disk. This error could be caused by one of the problems listed above
in connection with mounting the system volume, or could be specific to
process creation (such as insufficient nonpaged pool).
User Action: Correct the specific error that is preventing the ACP from being
created and reboot the system.

2-546

Messages

SYSINIT-E-failed to create system logical names
Facility: SYSINIT, System Initialization
Explanation: An error occurred while attempting to create one of the logical
names needed by SYSINIT (SYSSSYSTEM, SYS$SHARE, SYS$MESSAGE).
The complete list of errors that can occur when creating logical names is
given in the VAX/VMS System Services Reference Manual
User Action: The error that occurred while SYSINIT was executing (assuming
that the SYSINIT image is not corrupted) is insufficient paged dynamic
memory. Set the SYSGEN parameter PAGEDYN to a reasonable value (at
least 10000) and reboot the system.
SYSINIT-E-insufficient nonpaged dynamic memory
Facility: SYSINIT, System Initialization
Explanation: Because nonpaged pool automatically expands to fit its need,
this error is rare and occurs only when some condition prevents pool
expansion.
User Action: Increase the SYSGEN parameter NPAGEVIR in increments of
100000 until the system boots successfully. It is possible that insufficient
physical memory can prevent automatic pool expansion, even when
NPAGEVIR is set sufficiently large. In that case, increase the amount of
physical memory available for pool expansion.
You can also increase the value of NPAGEDYN to reflect the real pool
needs of the system. Or you can lower the parameters, BALSETCNT and
VIRTUALPAGECNT, to make the system page table smaller. Refer to the
VAX /VMS System Manager's Reference Manual for more information about
techniques for making enough nonpaged pool available for running the
system.
SYSINIT-E-invalid date/time
Facility: SYSINIT, System Initialization
Explanation: A syntax error was detected in the date or time that was typed
to set the system time.
User Action: Enter the date or time in the correct format.
SYSINIT-E-known file list initialization error
Facility: SYSINIT, System Initialization
Explanation: There was not enough nonpaged pool to allocate the known
file list head.
User Action: Increase the amount of nonpaged pool by following the general
prescription for nonpaged pool and the bootstrap operation, and reboot the
system.

2-547

SYSINIT-E-lookup failure on paging file
Facility: SYSINIT, System Initialization
Explanation: The primary paging file, SYS$SYSTEM:PAGEFILE.SYS, could
not be found.
User Action: Use the command file SYS$UPDATE:SWAPFILES.COM to
place a paging file in the system directory SYS$SYSTEM. Note that a missing
swap file does not generate an error message. The system runs with a single
file used for both paging and swapping until other paging or swap files are
installed.
SYSINIT-E-message file not found, or insufficient SPT to map it
Facility: SYSINIT, System Initialization
Explanation: The system message file, SYS$MESSAGE:SYSMSG.EXE, does
not exist. Or if the file exists, there are not enough system page table entries
(SPTs) to map it.
User Action: If the system message file is missing, take the necessary steps to
replace the message file. If the file is present, increase the SYSGEN parameter
SPTREQ by the size of the message file and reboot the system.
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, SYSINIT-Einsufficient nonpaged dynamic memory, for information about making
enough nonpaged pool available for booting the system.

•

Do not set PAGFILCNT 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-RMS.EXE not found or insufficient SPT to map it
Facility: SYSINIT, System Initialization
Explanation: The VAX RMS image, SYS$SYSTEM:RMS.EXE, does not exist.
Or if the file exists, there are not enough system page table entries (SPTs) to
map it.
User Action: If the VAX RMS image file is missing, take the necessary steps
to replace the file. If the file is present, increase the SYSGEN parameter
SPTREQ by the size of the VAX RMS image plus the size of the message file,
and reboot the system.

Messages

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

I/O database not updated for volume 'volume7

Facility: SET, SET Facility
Explanation: The attempt to modify the volume's home block was successful,
but the system information about the volume was not updated.
User Action: To insure 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.
SYSTEMOPER,

system

SYSINIT-terminal IO error

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: Reissue the command with the proper version of SYSGEN.EXE.
SYSVERDIF,

privilege removed - system version mismatch - please relink

Facility: SYSTEM, VAX/VMS System Services
Explanation: A SYS.STB, different from that of the currently running system,
was used to link the image being run.
User Action: Relink the image. The image is allowed to run without
CMEXEC or CMKRNL privilege.

2-549

SYSVERDIF,

system version mismatch - please relink

Facility: INSTALL, Install Utility
Explanation: The image being installed was 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
VAX/VMS.
SZTOOBIG,

record size or block size greater than 65534

Facility: MOUNT, MOUNT Command
Explanation: The record size or block size specified by /RECORDSIZE or
/BLOCKSIZE is greater than 65534.
User Action: Check the source program and make the necessary correction.
TABEXIST,

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 was 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, Run-Time Library Screen Management Procedures
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: Probably the routines that fetch the data are 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 was 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 issued and a
dump of the MONITOR image.

Messages

TABNOTFND,

previous table 'table name' was 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.
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, VAX/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

Facility: OPCOM, Operator Communication
Explanation: This message, issued optionally with the OPERSTS message,
describes the classes of operator requests that the current operator is enabled
to act upon.
User Action: No action is required.

2-551

Messages

TAR,

No text allowed after .REQUIRE command: 'string7
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.

TBIT,

T-bit pending trap at PC = 'location7, PSL = 'xxxxxxxx'
Facility: SYSTEM, VAX/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
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 'oper-name'

Facility: OPCOM, Operator Communication
Explanation: A terminal was successfully disabled with the DCL command
REPLY/DISABLE.
User Action: None.
TERMENAB,

terminal enabled, operator 'oper-name'

Facility: OPCOM, Operator Communication
Explanation: A terminal was 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 was rejected.
User Action: Give yourself OPER privilege and try again.
TEROUT,

error code of 'xx' parsing command file

Facility: PATCH, VAX Image File 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.

2-552

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,

'string7

Facility: DSRTOC, DIGITAL Standard Runoff Table of Contents Utility
Explanation: This message accompanies one or more other messages that
describe an error condition. This message displays the text that was being
processed when the error occurred.
User Action: Correct the text by editing the source file.
TEXTD,

entry text: 'string'

Facility: DSRINDEX, DIGITAL Standard Runoff Indexing Utility
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, VAX Linker
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-553

Messages

THIRDPARTY,

logical link disconnected by a third party

Facility: SYSTEM, VAX/VMS System Services
Explanation: A DECnet-VAX logical link was disconnected by a system
manager at some location in the network.
User Action: Reinitiate the connection.
TIMEOUT,

device timeout

Facility: SYSTEM, VAX/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
LPA11-K driver a device timeout occurred. (Only for the start microprocessor,
initialize LPA11-K, set clock, and start data transfer request functions.) An
interrupt was not received within one second after the request was issued.
If this message is associated with a status code returned by a request to a
DR11-W interface driver, the timeout period specified for this request was
exceeded. A device reset is issued to the DR11-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 was lost, or IO$M—TIMED was 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 was 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 was properly loaded on the device.
TIPCUFLOW,

NETACP - transmit count underflow

object command data overflows record by 'decimal-number' bytes in
module 'module-name' record 'record-name' file 'file-name'

Facility: LINK, VAX Linker
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.

2-554

Messages

TIRNYI,

unimplemented TIR command ('decimal-number7) encountered in
module 'module-name' record 'record-name' file 'file-name'

Facility: LINK, VAX Linker
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: CLI, 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.
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, VAX Record Management Services
Explanation: A VAX RMS operation specified a timeout period and the
timeout period expired before the operation completed.
User Action: The user buffer contains the input characters (if any) received
before the timeout period expired. If this message occurs during the login
procedure, repeat the procedure. If the request was for a record lock, the
lock request was not granted. Other actions depend on the program issuing
the request; user programs should be coded to detect and respond to I/O
timeouts.

2-555

Messages

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 in order to
declare itself as a known image to be eligible for multiple connects.
User Action: Install NICONFIG with TMPMBX privilege.
TMR,

SETIMR system service request failed

Facility: RMS, VAX Record Management Services
Explanation: A VAX RMS operation specified a timeout period and the
attempt to declare the system timer failed. The operation was aborted.
User Action: Verify that sufficient TQE quota is available and try the
operation again.
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: None. You cannot nest more than 20 .SAVE directives.

TMT,

Too many tab settings; excess ignored: 'string7
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, VAX Record Management Services
Explanation: A VAX RMS $GET service request to a terminal terminated
when the user buffer was filled to capacity. No record terminator was
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.

2-556

Messages

TOODEEP,

maximum subindex depth exceeded

Facility: DSRINDEX, DIGITAL Standard Runoff Indexing Utility
Explanation: The number of levels of subindex entries has been exceeded.
User Action: Check the subindex entries.
TOOFEW,

Too few arguments at line 'integer7

Facility: 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 Reference Manual, or use online
help.
TOOLONG,

text wrong length

Facility: NCP, Network Control Program
Explanation: The input did not meet syntactic requirements.
User Action: Reenter the text with the correct syntax.
TOOMANDIS,

too many displays

Facility: SMG, Run-Time Library Screen Management Procedures
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, VAX/VMS Debugger
Explanation: Too many MISMODBEG or certain other errors occurred. Other
similar errors are not reported.
User Action: None. This message is informational.
TOOMANPAS,

too many pasteboards

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: An internal limit on the number of pasteboards that your
program may have has been exceeded. The current limit is 16.
User Action: Use fewer pasteboards.

2-557

TOOMANY,

Too many arguments at line 'integer'

Facility: 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
Reference Manual, or use online help.
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.
User Action: No action is necessary, EXCHANGE has used the largest
number of columns which will fit on the line.
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 an SPR.
TOOMANYLNAM,

logical name translation exceeded allowed depth

Facility: SYSTEM, VAX/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: VAX Text Processing Utility
Explanation: A maximum of 31 formal parameters and/or local variables is
permitted.
User Action: Reduce the number of formal parameters or local variables until
there are no more than 31.
TOOMANYREDS,

too many redirects

Facility: SYSTEM, VAX/VMS System Services
Explanation: This call was redirected more than eight times.
User Action: Modify your program so that it performs fewer levels of call
redirection.

Messages

TOOMANYVER,

too many higher file versions

Facility: SYSTEM, VAX/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 was issued with too
many controllers specified for a given type.
User Action: Reissue 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 fewer than 'n+1' comment
delimiters.
TOOMNYENDR,

too many .ENDR in macro 'macro name' in 'library file-spec'

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-559

Messages

TOOMNYFILES,

too many input files specified

Facility: MONITOR, Monitor Utility
Explanation: More than 125 input files were specified on the /INPUT
qualifier.
User Action: Reissue the MONITOR request specifying a file specification list
which identifies no more than 125 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-560

Messages

TOOMUCHDATA,

too much optional or interrupt message data

Facility: SYSTEM, VAX/VMS System Services
Explanation: A network interrupt message was 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 was 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: 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' input files

Facility: ERF, ANALYZE/Error Log Utility
Explanation: This messages reports the total number of input files processed
and the total number of selected and rejected error log entries processed.
User Action: None.
TPSS,

TPSS

symbolic stack dump follows

Facility: TRACE, Traceback
Explanation: This message precedes a symbolic traceback dump.
User Action: None.

2-561

Messages

TRACIGN,

suppression of traceback overridden by DEBUG specification

Facility: LINK, VAX Linker
Explanation: The command line specified both /NOTRACE and /DEBUG.
/NOTRACE is ignored.
User Action: None. The link continues as if /NOTRACE were not specified.
TRE,

error in index tree
Facility: RMS, VAX Record Management Services
Explanation: VAX RMS detected an invalid index pointer in an indexed file.
User Action: Reorganize the file.
This error is caused by hardware errors, VAX RMS or system software errors,
or inadvertent modifications of files by non-VAX RMS programs.

TRMMBX,

terminal has associated - terminate image and then SPAWN

Facility: CLI, 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 reissue the SPAWN command.
TRMNOTANS,

terminal is not ANSI compatible

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: A call to SMG$GET_PHYSICAL —CURSOR was made
specifying that the terminal is to be queried to determine where the cursor is.
This could not be done because the terminal was not ANSI standard, and this
feature is available only on ANSI terminals.
User Action: Rerun your application on an ANSI terminal such as a VT100.
TRPTOFF,

trace point name has been turned off

Facility: PSI, VAX Packetnet System Interface
Explanation: This message is used to report events where trace points are
turned off.
User Action: The trace point that has been turned off is named. If you want
to use the tracepoint, turn it on again.
TRU,

truncation
Facility: STR, Run-Time Library String Procedures
Explanation: An attempt was made to place more characters into a string
than it could contain. The value was 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.

2-562

Messages

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 'file-name'

Facility: LINK, VAX Linker
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.
TRUNCATE,

Line truncated to 'count' characters

Facility: 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 was truncated to
the maximum allowable length of the line.
User Action: None.
TRUNCATE,

record(s) 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 was performed. This is an informational
message.
User Action: None. The file contains records that exceed SEARCH'S capacity.
The SEARCH was successfully performed on the shortened records.
TRUNCATED,

string too long - truncated

Facility: DSRINDEX, DIGITAL Standard Runoff Indexing Utility
Explanation: DSR encountered a string that was too long. The string was
truncated.
User Action: Edit the file and shorten the line.
TRUNCDAT,

computed value is 'valuel' value written is 'value2' at location
'address'

Facility: LINK, VAX Linker
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
was 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.

2-563

Messages

TTL,

Text too long: 'string7
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 was specified twice for a given SYSGEN
command CONFIGURE.
User Action: Verify the value you intend to use.
TWO WIDTHS,

/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, VAX 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$OPEN, the library type you requested conflicts with the
library type you specified in the create options argument.
User Action: None. Processing continues based on the actual library type.
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.

2-564

Messages

UAFGETERR,

error reading user authorization file

Facility: MAIL, Personal Mail Utility
Explanation: An error occurred reading the user authorization file.
User Action: Use the VAX RMS status code that accompanies this message to
determine your action.
UAFOPNERR,

error opening user authorization file

Facility: MAIL, Personal Mail Utility
Explanation: An error occurred opening the user authorization file.
User Action: Use the VAX RMS status code that accompanies this message to
determine your action.
UBF,

invalid user buffer
Facility: RMS, VAX 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 VAX RMS service was coded correctly.

UBMAPEXCED,

UNIBUS map register allocation exceeded

Fatal error detected by UDA port driver (PUDRIVER)

2-565

UDEFPSC,

attempt to reference undefined psect number 'decimal-number' in
module 'module-name' file 'file-name'

Facility: LINK, VAX Linker
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.
UDFENV,

'undefined environment reference'

Facility: LINK, VAX Linker
Explanation: An undefined reference to an environment was encountered
after Pass 1.
User Action: Determine why the reference is undefined and correct the
condition.
UDFSYM,

'symbol-name'

Facility: LINK, VAX Linker
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.

UIC has 'n' blocks in use
Facility: DISKQUOTA, Diskquota Utility
Explanation: The specified UIC is over quota due to the MODIFY or DELETE
operation just performed.
User Action: None. This is an informational message.

Messages

UICERR,

error in UIC specification

Facility: AUTHORIZE, Authorize Utility
Explanation: You specified an incorrect UIC.
User Action: Enter as [group,member] where group and member are octal
values in range 000-377 inclusive, or the wild card character (*).
UME,

Unmatched end command: 'string'

Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: An .END command (for example, .END NOTE) was detected,
but the associated beginning command (.NOTE) was not.
User Action: Insert the associated beginning command.
UNABLCREVA,

Unable to create virtual address space

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 reissue 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 reissue the command.

2-567

Messages

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: Reissue the command specifying the correct file specification.
UNAOPNSRC,

unable to open source file 'xxx'

Facility: DEBUG, VAX/VMS Debugger
Explanation: Source lines from the file xxx cannot be displayed because
DEBUG was unable to open the source file (represented as xxx). The
accompanying VAX RMS status message gives more information about
the reasons for the source file not being opened.
User Action: Examine the VAX 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 'xxx'

Facility: DEBUG, VAX/VMS Debugger
Explanation: Source lines from the file xxx cannot be displayed because
DEBUG was unable to read the source file (represented as xxx). The
accompanying VAX RMS status message gives more information about
the reasons for the source file not being opened.
User Action: Examine the VAX RMS status message to determine the reasons
for the source file not being read, and take the appropriate action based on
that information.
UNASEFC,

unassociated event flag cluster

Facility: SYSTEM, VAX/VMS System Services
Explanation: An image called a system service specifying an event flag
number in a common cluster with which it was 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.
UNDEFINEDPROC,

Undefined procedure call 'name' at line 'integer'

Facility: VAX Text Processing Utility
Explanation: You have called an undefined procedure.
User Action: Check the spelling of the procedure name.
UNDEFOUTPUT,

line 'line-number': Output parameter/qualifier 'name' is not
defined

Facility: CDU, Command Definition Utility
Explanation: CDU encountered a 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.

2—568

Messages

UNDEFSYM,

undefined symbol

Facility: MACRO, VAX Macro Assembler
Explanation: A local label was referred to but not defined in a local label
block; or, if GLOBAL was disabled, a symbol was 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 'line-number7: Syntax 'syntax-name7 is not defined

Facility: CDU, Command Definition Utility
Explanation: CDU encountered an undefined syntax name during a SYNTAX
assignment. All syntax names must previously defined.
User Action: Edit the CLD file so that all names in SYNTAX assignments are
defined.
UNDEFTYPE,

line 'line-number': Type 'type-name' 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.
UNDEFXFRAD,

undefined transfer address

Facility: MACRO, VAX Macro Assembler
Explanation: The .END directive specified a transfer address that was 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, Run-Time Library Math Procedures
Explanation: An expression contained exponentiation that cannot be
mathematically evaluated, for example, 0.**0. 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.

2-569

Messages

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 was set

Facility: SORT, VAX 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
was 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.
UNDTERNAM,

undefined terminal name

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: The requested terminal definition was 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, Run-Time Library Screen Management Procedures
Explanation: The requested terminal definition was not found in the caller's
private copy of Termtable or the system Termtable. The caller's private
Termtable couldn't be accessed, either because it didn't 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.

2-570

Messages

UNDTERNOS,

undefined terminal - couldn't access system terminal tables

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: The requested terminal definition was not found in the caller's
private Termtable or the system Termtable. The system Termtable was
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, Run-Time Library Screen Management Procedures
Explanation: The definition for the requested terminal type was 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, Run-Time Library General Procedures
Explanation: The CLI returned an error status that was 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.
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 character(s) from
the end of the command line.
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 reissue
the MONITOR request. Otherwise, submit a Software Performance Report.

2-571

Messages

UNEXUBAINT,

Unexpected UNIBUS adapter interrupt

Uninitialized variable

Facility: 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, VAX Linker
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.
UNKCLASS,

unknown device class found, 'device class value'

Facility: ERF, ANALYZE/Error Log Utility
Explanation: An entry with an unknown or unsupported device class was
encountered.
User Action: Use the UNKNOWN-ENTRIES keyword with the /INCLUDE
qualifier to obtain the report.
UNKCPU,

unknown CPU type, 'CPU-type value'

Facility: ERF, AN ALYZE/Error Log Utility
Explanation: An entry with an unknown or unsupported CPU type was
encountered.
User Action: Use the UNKNOW_ENTRIES keyword with the /INCLUDE
qualifier to obtain the report.

2-572

Messages

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 Volume Command and MOUNT, MOUNT
Command
Explanation: The device type specified is unknown or invalid.
User Action: Verify the device name (or logical name if a logical name was
specified), and reenter the command with the correct device name.
UNKENTRY,

unknown entry type, 'entry-type value'

Facility: ERF, ANALYZE/Error Log Utility
Explanation: An entry with an unknown or unsupported entry type was
encountered.
User Action: Use the UNKNOWN-ENTRIES keyword with the /INCLUDE
qualifier to obtain the report.
UNKKEYWORD,

An unknown keyword has been used as an argument

Facility: 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: 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 was sent.
User Action: Reenter the DCL command REQUEST or REPLY and specify a
valid operator name.

2-573

Messages

UNKNPRQ,

Unknown Inter-processor Request Message

Unknown opcode at line 'integer'

Facility: VAX Text Processing Utility
Explanation: An internal error occurred in the VAXTPU software.
User Action: Submit a Software Performance Report.
UNKRSTRT,

Unknown restart code

Unknown data type at line 'integer'

Facility: 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, ANALYZE/Error Log Utility
Explanation: An entry with an unknown or unsupported device type was
encountered.
User Action: Use the UNKNOWN—ENTRIES keyword with the /INCLUDE
qualifier to obtain the report.
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: None. The volume set remains locked.

2-574

Messages

UNLOCKED,

'file-name' unlocked

Facility: SET, SET Facility
Explanation: The file has been successfully unlocked.
User Action: None.
UNLOCKED,

'file-spec' unlocked

Facility: Shared by several facilities
Explanation: The file specified by a DCL command UNLOCK was unlocked.
User Action: None.
UNLOCKERR,

error unlocking 'file-name'

Facility: SET, SET Facility
Explanation: An error occurred when the file was 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, VAX/VMS Debugger
Explanation: A left parenthesis (() was found, but the matching
right parenthesis ( )) is missing.
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.
UNPROPARM,

unprocessed parameters

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

unprocessed qualifiers

Facility: CLI, 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 was specified
without /LIST, reenter the command with the /LIST qualifier.

2-575

UNPROQUAL,

unprocessed qualifiers

Facility: CLI, 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 was 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 was 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, SHOW Facility
Explanation: The command entered is not a valid SHOW CLUSTER
command.
User Action: Enter a valid command or type HELP for a list of valid
commands.
UNREACHABLE,

remote node is not currently reachable

Facility: SYSTEM, VAX/VMS System Services
Explanation: An attempt was 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 VAX/VMS Networking
Manual for additional information.
Unrecognized command
Facility: DISKQUOTA, Diskquota Utility
Explanation: An invalid command was entered.
User Action: Enter a valid command.

Messages

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 qualifier
Facility: DISKQUOTA, Diskquota Utility
Explanation: An invalid qualifier was entered.
User Action: Enter a valid qualifier.
UNRECSTA,

unrecognized statement

Facility: SMG, Run-Time Library Screen Management Procedures
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 was 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.
UNRELVOL,

volume is not part of volume set being mounted

Facility: MOUNT, MOUNT Command
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.
UNRKEY,

keyword is an unrecognized keyword

Facility: LIB, Run-Time Library General Procedures
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—577

UNRKEY,

unrecognized field or class name 'class-name7

Facility: SHOW, SHOW Facility
Explanation: The field or class name entered is not valid in any report.
User Action: Enter a valid field or class name, or type HELP FIELDS or
HELP CLASSES for a list of valid names.
UNSAFE,

drive unsafe

Facility: SYSTEM, VAX/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, VAX/VMS System Services
Explanation: A message was received that was 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: The recording file may be read only by the version of
MONITOR that created it, or by a later version of MONITOR that supports
the earlier file structure level.
UNSUPRTCPU,

Unsupported CPU

Messages

UNSVRS,

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 are unable to connect to the node.
UNTERMARG,

unterminated argument

Facility: MACRO, VAX Macro Assembler
Explanation: The string argument was missing a delimiter or the macro
argument was 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 was 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, VAX/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.
UNWINDING,

unwind already in progress

Facility: SYSTEM, VAX/VMS System Services
Explanation: A condition handler was 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

2-579

UNXPCTSTS,

unexpected status detected. Expected 'status'. Found:

Facility: Shared by several facilities
Explanation: An error was detected by a system service. A subsequent
message explains the reason for the error.
User Action: See the description of the accompanying VAX RMS message in
this manual.
UNXSIGNAL,

Unexpected signal name in ACP

patch with eco level 'nn' ignored due to update qualifier

Facility: PATCH, VAX Image File 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.
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, VAX Record Management Services
Explanation: VAX RMS permits file sharing when block I/O 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 VAX RMS service was coded correctly.

Messages

URE,

Unrecoverable error processing record 'In' on page 'pn' of input file 'file¬
name'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: An irrecoverable I/O 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 request: internal failure. This
is a DSR internal error.
User Action: Reprocess the file. If the error reoccurs, submit a Software
Performance Report.

USEFLORES,

use of floating reserved operand

Facility: OTS, Language Independent Run-Time Library Support Procedures
and LIB, Run-Time Library General Procedures
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.
USERAUTH,

error accessing authorization record

Facility: LOGIN, Login Processor
Explanation: An error occurred while trying to access a particular record
of the user authorization file. An accompanying message will provide more
information.
User Action: Correct the problem described by the accompanying message,
and try again.
USERDSABL,

user 'username' cannot receive new mail

Facility: MAIL, Personal Mail Utility
Explanation: You have attempted to send mail to a user who has been
disallowed from receiving mail.
User Action: None.
USEREXC,

you are at maximum allowed processes for your user name

Facility: LOGIN, Login Processor
Explanation: You tried to log in when the maximum number of processes
logged in to your user name already had logged in.
User Action: Wait until someone else logs off, or log off another process.

2-581

Messages

USERMSG,

message from user 'user-name7

Facility: OPCOM, Operator Communication
Explanation: This is a user message to the operator; a reply is not expected.
User Action: No action is required.
USEROPER,

user

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, Personal 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: None.
USEUDFEN2,

undefined environment number 'number' referenced in psect
'string' offset 'hexadecimal number' in module 'module name' file
'file name'

Facility: LINK, VAX Linker
Explanation: An undefined environment was 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 'file name'

Facility: LINK, VAX Linker
Explanation: An undefined environment was referenced in a module.
User Action: Ensure that all referenced environments are defined.

2-582

Messages

USEUDFLSY,

undefined module-local symbol 'symbol name' referenced in psect
'string' offset 'hexadecimal number' in module 'module name' file
'file name'

Facility: LINK, VAX Linker
Explanation: An undefined module-local symbol was 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 'file-name'

Facility: LINK, VAX Linker
Explanation: An undefined symbol was 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 'file-name'

Facility: LINK, VAX Linker
Explanation: An undefined symbol was referenced in a debug or traceback
record.
User Action: Define the symbol.
USGOTO,

target of GOTO not found - check spelling and presence of label

Facility: CLI, 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$OUTPUT__HELP.
User Action: Determine the reason for the failure in the input routine.
USRTFR,

image 'image-name' has no user transfer address

Facility: LINK, VAX Linker
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, VAX 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 65535.
User Action: Verify that the call to the VAX RMS service was coded correctly.

2-583

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 V2.0 NICE
message when connected to a V2.0 network management listener (NML).
User Action: None. Remove the invalid parameter.
VALERR,

specified value is out of legal range

Facility: DSRTOC, DIGITAL Standard Runoff Table of Contents Utility
Explanation: A value was 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 was specified which is not within legal range.
User Action: Respecify a value within legal range.
VALNOTADDR,

value of variable Variable' not usable as address

Facility: DEBUG, VAX/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/FDL Utility
Explanation: You specified a primary that requires a value, but none was
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: Retype 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 VAX/VMS Authorize Utility Reference Manual for
information about qualifier value sizes. Enter a smaller value for the qualifier.

Messages

VALUE,

set to maximum

Facility: SYSGEN, System Generation Utility
Explanation: A SYSGEN command SET was issued 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 was issued 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, VAX/VMS System Services
Explanation: The virtual address space is full.
User Action: Reboot and increase the amount of allowable virtual address
space.
VBNERROR,

'file-spec' 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

2-585

Messages

VBNMISSING,

'file-spec' 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.
VBNPASTEOF,

'file-spec' 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, VAX/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 was
exceeded.
User Action: Remove unnecessary vectors and relink.
VECINUSE,

vector in use

Facility: SYSGEN, System Generation Utility
Explanation: The interrupt vector address that was specified in a SYSGEN
command CONNECT is being used by another device.
User Action: Change the vector address in the device driver and reissue the
SYSGEN command CONNECT.
VER,

error in version number
Facility: RMS, VAX Record Management Services
Explanation: The version number specified in a file specification contains
invalid syntax, for example, nonnumeric characters or a value larger than
32767.
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.

2-586

Messages

VERIFYERR,

verification error for block 'n' of 'file-spec7

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

xxx indirect command file yyy

Facility: DEBUG, VAX/VMS Debugger
Explanation: The debugger is verifying an indirect command file. This
message is displayed before the command file is executed and after all the
commands have been displayed.
User Action: None. This message is informational.
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.

VM—FAIL,

failed to get required virtual memory 'number'

Facility: SORT, VAX SORT/MERGE Utility
Explanation: The SORT/MERGE Utility could not get the amount of virtual
memory required for the sort, 'number' indicates the number of bytes needed.
User Action: If the Sort Utility is being run, decrease the working set quota.
If the SORT subroutine package is being run, either decrease the quota or
return some memory to the system inside the user's program before calling
the Sort Utility.
VOLALRMNT,

another volume of same label already mounted

Facility: MOUNT, MOUNT Command
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-587

VOLIDENT,

label = 'volume-label', owner = 'user-name', format = 'volumeformat'

Facility: MOUNT, MOUNT Command
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, reissue the DCL command MOUNT.
VOLINSET,

'device' is already part of a volume set

Facility: BACKUP, Backup Utility
Explanation: The specified volume was 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 Command
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, VAX/VMS System Services
Explanation: The volume valid bit is not set for the volume. All physical and
logical I/O 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: No action is necessary.
VOLNAME,

volume 'volume name' in

Facility: MOUNT, MOUNT Command
Explanation: This message is optionally issued with the MOUNTDEV
message. It includes the volume name of the volume being mounted.
User Action: No action is required.

Messages

VOLOERR,

must override owner identifier field in VOL1 label on 'device-name'

Facility: MOUNT, MOUNT Command
Explanation: The owner identifier field of the VOL1 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 VAX/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 Command
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 Command
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 set has too many volumes to handle
Facility: DISKQUOTA, Diskquota Utility
Explanation: The volume set could be corrupted.
User Action: Use the Verify Utility to repair the volume set or reconstruct
the volume set from back-up volumes.
VOLUME _FULL,

volume is full (insufficient space for the request)

Facility: EXCHANGE, Exchange Utility
Explanation: The EXCHANGE utility was 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.

2-589

Messages

WACKQEMPTY,

NETACP - ack wait queue empty

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, Personal Mail Utility
Explanation: One or more of the addresses were unavailable.
User Action: Type Y if you want to send the 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, VAX Linker
Explanation: The link completed, but warnings were issued.
User Action: None.

2—590

Messages

WASECC,

successful transfer; no data check

Facility: SYSTEM, VAX/VMS System Services
Explanation: This message is associated with a status code returned by I/O
functions. A data check operation was not performed. The function was a
read data that was completed successfully by applying one or more ECC
corrections. The specified data check, however, was not performed.
User Action: Note the condition. Modify the source program, if necessary, to
detect and respond to the condition.
WBE,

error on write behind
Facility: RMS, VAX Record Management Services
Explanation: An error occurred during a VAX RMS operation for which write
behind was specified.
User Action: The status value (STV) field of the RAB contains a code that
provides more information about the condition. Take corrective action based
on this status code.

WCBFCBMNG,

WCB/FCB correspondence broken

invalid wild card context (WCC) value

Facility: RMS, VAX Record Management Services
Explanation: The wild card context value in the NAM block (an input
file-processing option) contains an invalid value.
User Action: Verify that the call to the VAX RMS service was coded correctly
and that the NAM block was not inadvertently modified between VAX RMS
service calls.
WCSCORR,

WCS error correction failed

2—591

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.
WDW—MAXPRM,

too many window parameters

Facility: SEARCH, SEARCH Command
Explanation: The /WINDOW parameter was not specified correctly.
User Action: Reenter the command using the correct syntax.
WER,

file write error

Facility: RMS, VAX Record Management Services
Explanation: An error occurred during a VAX RMS write operation.
User Action: The status value (STV) field of the RAB contains a code that
provides more information about the condition. Take corrective action based
on this status code.
WFR,

.RESTORE not in same file as .SAVE/. SAVE ALL: "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 occured 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
wildcards.
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.

Messages

WILUSERMS,

output will be performed by RMS later

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: Normally the screen is updated at the end of every output
operation. If, however, the 'device' 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: None.
WINDNOTMAPPED,

The window is not mapped to a buffer

Facility: 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: 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.
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 VAX/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.
WLD,

invalid wildcard operation

Facility: RMS, VAX Record Management Services
Explanation: A call to the VAX RMS services $ CREATE, $ERASE, $ENTER,
$OPEN, and $RENAME specified a wild card in one or more components of
a file specification. No wild cards are allowed.
User Action: Correct the source program. Verify that the call to VAX RMS
was coded correctly. To perform a wild card file delete service, you must code
a loop that searches for files based on wildcard specifications and deletes the
files individually.
WLK,

device currently write locked

Facility: RMS, VAX Record Management Services
Explanation: The hardware device specified for a VAX RMS operation is
write-locked for protection, and write-access was 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.

2-593

Messages

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 65535 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.
WORK_DEV,

work file 'filespec' must be on random access local device

Facility: SORT, VAX 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.
User Action: None. EDT is responding to your command.
WPL,

error detected while writing prolog
Facility: RMS, VAX Record Management Services
Explanation: An I/O error occurred while VAX RMS was writing a file's
prolog area.
User Action: Depending on the operation, the status value (STV) field in the
FAB or RAB contains a status code that provides additional information about
the condition. Take corrective action based on this status code.

2-594

Messages

WRIRSPMSG,

error writing system service response message

Facility: JBC, Job Controller
Explanation: The job controller encountered an error responding to a
$SNDACC, SSNDSMB, or $SNDJBC service. The accompanying message
provides additional information.
User Action: Take action based on the accompanying message.
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.
User Action: None. This message is a monitoring aid for the system
manager.
WRITEATTR,

error writing attributes for 'file-spec'

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-595

WRITEBACK,

error writing backup date for 'device7 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 'file-spec'

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 was 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
'file spec'

Facility: SYSGEN, System Generation Utility
Explanation: This message is written to the operator's console when a
WRITE CURRENT operation is done from SYSGEN.
User Action: None. This message is a monitoring aid for the system
manager.
WRITEERR,

error modifying 'file/directory'

Facility: SET, SET Facility
Explanation: A problem has occurred while writing to a file or a directory.
This message is issued with an accompanying message.
User Action: Take corrective action based on the accompanying message.

Messages

WRITEERR,

error while writing output

Facility: ACCOUNTING, Accounting Utility
Explanation: During a VAX RMS operation, an error was 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; file-spec 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.
WRITEERR,

error writing 'file-spec'

Facility: Shared by several facilities
Explanation: During a VAX RMS operation, an error was 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; 'file-spec' 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 'file-spec'

Error writing 'output-file-spec'

Facility: VAX Text Processing Utility
Explanation: The output file cannot be written. This message should be
accompanied by a VAX RMS message indicating the reason for the error.
User Action: Follow the recovery procedure for the specified VAX 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-597

WRITEERRREC,

write error recovered on volume 'volume-name7

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 was written successfully, but the user should watch the
volume for further signs of deterioration. Discard or reformat the volume if
errors are frequent.
WRITEFILE,

error writing event file 'file-id7

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') 'file-name' 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, [000000]INDEXF.SYS;1, 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,
[000000]INDEXF.SYS;1, 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.
WRITEIBMAP,

error writing index file bitmap, VBN 'n', RVN 'n'

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,
[000000]INDEXF.SYS;1, 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.

Messages

WRITELOCK,

volume is write locked

Facility: MOUNT, MOUNT Command
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-name7

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

write enable volume 7n7 on 'device7

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, [000000]BITMAP.SYS;1, 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.

2-599

Messages

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,
[000000]BITMAP.SYS;1 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 Command
Explanation: An I/O error occurred while the volume was being mounted;
the volume has been write-locked to protect its integrity.
User Action: Check the hardware and retry the program.
WRITLCK,

volume on 'device' is write locked write lock error

Facility: SYSTEM, VAX/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 'file-name'

Facility: LINK, VAX Linker
Explanation: The specified module has compilation warnings.
User Action: Correct the module and relink.
WRONGACP,

wrong ACP for device

Facility: SYSTEM, VAX/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: VAX Text Processing Utility
Explanation: An internal error occurred in the VAXTPU software.
User Action: Submit a Software Performance Report.

2-600

Messages

WRONGLANG,

language is not xxx

Facility: DEBUG, VAX/VMS Debugger
Explanation: The language used to evaluate the last expression or variable
reference is not the current language.
User Action: Do not change languages between the definitions of last value
(\), logical predecessor (*), current location (.), logical successor (RETURN),
and their use.
WRONGOWNER,

file ('file-id') 'file-name' 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: None. The extension file header is corrected.
WRONG VAR,

field xxx is not in current variant yyy associated with tag field zzz.

Facility: DEBUG, VAX/VMS Debugger
Explanation: The field xxx is not in the current variant.
User Action: Check your program to verify the expected results.
WRONGVOL,

'date and time'. Device 'devname' 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 mount
verification.
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 was 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.
WRONGVOL,

device 'device name' contains the wrong volume

Facility: MOUNT, MOUNT Command
Explanation: The specified volume does not match the volume in the drive.
User Action: Correct the volume name and retry the operation.

2-601

Messages

WRONGVOL,

device 'device-name' contains the wrong volume
Correct the situation or dismount the volume

Facility: OPCOM, Operator Communication
Explanation: An operator spun up a volume undergoing mount verification
and discovered that this volume does not match the original volume.
User Action: Either place the correct volume in the drive and bring it online
or terminate mount verification. See the VAX/VMS System Manager's Reference
Manual for information about terminating mount verification.
WRONUMARG,

wrong number of arguments

Facility: SMG, Run-Time Library Screen Management Procedures
Explanation: An SMG routine was 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, Run-Time Library String Procedures
Explanation: A String Facility entry was 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.
WRONUMARG,

wrong number of arguments user PC 'location'

Facility: MTH, Run-Time Library Math Procedures
Explanation: A math library procedure was called with the wrong number of
arguments.
User Action: Locate the call that returned the error and correct the call. See
the VAX/VMS Run-Time Library Routines Reference Manual for a description of
the required arguments.
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 VAX/VMS system or network
configuration problem.
User Action: Take corrective action based on the accompanying message.
WRTFIL,

updating image file 'file-spec'

Facility: PATCH, VAX Image File Patch Utility
Explanation: The specified image file was updated to include the previous
patch.
User Action: None.

2-602

Messages

WRTHOMBLK,

I/O error writing home block

Facility: MOUNT, MOUNT Command
Explanation: An I/O error occurred writing the home block of a volume
during the MOUNT/BIND operation.
User Action: Check that the hardware is functioning properly. Reinitialize
the disks and retry the operation.
WRTINVBUF,

ACP attempted to write an invalid buffer

ACP attempted to write an invalid file header

Write pages back - inconsistent database

2-603

Messages

WSLENOVAL,

Working set list entry not valid

Working set list page count error

Working set list virtual adr has non-valid PTE

Working set list entry does not match VA

2-604

Messages

WSSIZEERR,

Working set size less than pages in use

invalid XAB or XAB not accessible at location
Facility: RMS, VAX 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 VAX RMS service was coded
correctly.

XMTERR,

loop failed, 'nnn' messages not sent

Facility: NCP, Network Control Program
Explanation: An error occurred during the loopback test.
User Action: Check the quality of the communications line.
XNF,

required XAB not found
Facility: RMS, VAX Record Management Services
Explanation: A VAX RMS request required an XAB which was not specified.
For example, the ROP option, ETO was specified, but no EABTRM was
supplied.
User Action: Verify that the call to the VAX RMS service was 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.

2-605

XQPERR,

Error detected by file system XQP

/PASSWORD and /GENERATE-PASSWORD are mutually
exclusive

Facility: AUTHORIZE, Authorize Utility
Explanation: The /PASSWORD qualifier and the /GENERATE—
PASSWORD qualifier are mutually exclusive.
User Action: Re-enter the command with one or the other, but not both
qualifiers.
ZEROPAGE,

Zero page table entry from swap map

qualifier required; not found

Facility: AUTHORIZE, Authorize Utility
Explanation: The CREATE, GRANT or REVOKE command was given
without its required qualifier.
User Action: Respecify the command with the required qualifier, for example,
GRANT/IDENTIFIER.

VAX/VMS System Messages and
Recovery Procedures Reference Manual
AA-Z800B-TE

READERS
COMMENTS

Note: This form is for document comments only. DIGITAL will use comments
submitted on this form at the company's discretion. If you require a written reply
and are eligible to receive one under Software Performance Report (SPR) service,
submit your comments on an SPR form.

Did you find this manual understandable, usable, and well organized? Please make suggestions for
improvement.

Did you find errors in this manual? If so, specify the error and the page number.

Please indicate the type of user/reader that you most nearly represent:
□
□
□
□
□
□

Assembly language programmer
Higher-level language programmer
Occasional programmer (experienced)
User with little programming experience
Student programmer
Other (please specify) _

Name _Date_
Organization Street City __State_Zip Code_
or Country

—

Do Not Tear - Fold Here and Tape

mma

No Postage
Necessary
if Mailed in the
United States

BUSINESS REPLY MAIL
FIRST CLASS PERMIT N0.33 MAYNARD MASS.

POSTAGE WILL BE PAID BY ADDRESSEE

SSG PUBLICATIONS ZK1-3/J35
DIGITAL EQUIPMENT CORPORATION
110 SPIT BROOK ROAD
NASHUA, NEW HAMPSHIRE 03062-2698

Do Not Tear - Fold Here

Cut Along Dotted Line

— —

VAX/VMS System Messages and
Recovery Procedures Reference Manual
AA-Z800B-TE

READER'S
COMMENTS

Did you find this manual understandable, usable, and well organized? Please make suggestions for
improvement.

Did you find errors in this manual? If so, specify the error and the page number.

Please indicate the type of user/reader that you most nearly represent:
□
□
□
□
□
□

Assembly language programmer
Higher-level language programmer
Occasional programmer (experienced)
User with little programming experience
Student programmer
Other (please specify) _

Name _Date_
Organization _
Street _
City _State_Zip Code_
or Country

Do Not Tear - Fold Here and Tape

No Postage

HSflDBD

Necessary
if Mailed in the
United States

BUSINESS REPLY MAIL
FIRST CLASS PERMIT N0.33 MAYNARD MASS.

POSTAGE WILL BE PAID BY ADDRESSEE

SSG PUBLICATIONS ZK1-3/J35
DIGITAL EQUIPMENT CORPORATION
110 SPIT BROOK ROAD
NASHUA, NEW HAMPSHIRE 03062-2698

—

Do Not Tear - Fold Here

Cut Along Dotted Line