Digital PDFs

AA-DO17B-TE

March 1980

287 pages

Original

11MB

Document:	VAX/VMS System Messages and Recovery Procedures Manual
Order Number:	AA-DO17B-TE
Revision:	000
Pages:	287
Original Filename:

OCR Text

VAX/VMS
System Messages and
Recovery Procedures Manual
Order No. AA-D017B-TE

March 1980

This document contains a list of system messages. In most cases, an explanation of the message is provided along with suggested recovery procedures.

VAX/VMS
System Messages and
Recovery Procedures Manual
Order No. AA-00178-TE

SUPERSESSION/UPDATE INFORMATION:

This revised document supersedes
the VAX/VMS System Messages
and Recovery Procedures Manual
(Order No. AA-D017 A-TE).

OPERATING SYSTEM AND VERSION:

VAX/VMS V02

SOFTWARE VERSION:

VAX/VMS V02

To order additional copies of this document, contact the Software Distribution
Center, Digital Equipment Corporation, Maynard, Massachusetts 01754

digital equipment corporation . maynard, massachusetts

First Printing, August 1978
Revised, March 1980
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 only be used or copied in accordance with the terms of such
license.
No responsibility is assumed for the use or reliahility of software on
equipment that is not supplied by DIGITAL or its affiliated companies.

@ 1978, 1980 by Digital Equipment Corporation

The postage prepaid READER'S COMMENTS form on the last page of this
document requests the user's critical evaluation to assist us in
preparing future documentation.
The following are trademarks of Digital Equipment Corporation:

DIGITAL
DEC
PDP
DECUS
UNIBUS

COMPUTER LABS
COMTEX
DDT
DEC COMM
ASSIST-11
VAX
DECnet
DATATRIEVE

DECsystem-lo
DECtape
DIBOL
EDUSYSTEM
FLIP CHIP
FOCAL
INDAC
LAB-8
DECSYSTEM-20
RTS-8
VMS
IAS
TRAX

MASSBUS
OMNIBUS
OS/8
PHA
RSTS
RSX
TYPESET-8
TYPESET-11
TMS-11
ITPS-10
SBI
PDT

CONTENTS

Page
v

PREFACE
CHAPTER

INTRODUCTION

1-1

1.1
1.1.1
1.1.2
1.2
1. 2 .1
1.3
1. 3 .1
1. 3. 2
1. 3. 3
1. 3. 4

MESSAGE DISPLAY
Linked Messages
Exception Conditions
FORMAT OF SYSTEM MESSAGES
Severity Levels
RECOVERY PROCEDURES
Recovering from Command Entry Errors
Unavailable Resources
Recovering from Programming Errors
Reporting System Software or Hardware Errors

1-1

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

CHAPTER

MESSAGES

2-1

APPENDIX

ERROR CODES

A-1

1-1

1-2
1-2

TABLES
TABLE

A-1
A-2

RSX-11 File Control Services Error Codes
Directive Error Codes (Standard System Codes)

iii

A-1
A-2

PREFACE

MANUAL OBJECTIVES

This manual lists the messages produced by the VAX/VMS operatinq
system.
The messages are accompanied by explanations and suggested
actions to recover from errors.

INTENDED AUDIENCE

The manual is intended for all users of the VAX/VMS operating system,
including applications programmers, system programmers, operators, and
system managers.

STRUCTURE OF THIS DOCUMENT

This manual has two chapters:
•

Chapter 1 describes the format of the messages
how to locate a message in this manual.

and

•

Chapter 2 lists the messages alphabetically by message code.
Each message is accompanied by explanatory text and, where
applicable, a suggested recovery action.

•

Appendix A lists the RSX-11 File Control Services
Directive error codes.

and

explains

System

Unlike messages issued by VAX/VMS utilities, messages issued by
RSX-llM utility programs invoked by DCL commands do not have message
codes. Messages from RSX-llM utilities are listed together, with the
utility name alphabetized within the VAX/VMS message codes.

ASSOCIATED DOCUMENTS

The manuals listed below provide information on messages issued by the
facilities indicated. Messages for these facilities are not included
in this manual.
Facility

Manual

DEBUG

VAX-11 Symbolic Debugger Reference Manual

DSC

VAX-11 Utilities Reference Manual

LINK

VAX-11 Linker Reference Manual

Facility

Manual

MAIL

VAX-11 Utilities Reference Manual

MAR

VAX-11 MACRO User's Guide

MESSAGE

VAX-11 Utilities Reference Manual

SRT

PDP-11 SORT Reference Manual

UETP

VAX/VMS UETP User's Guide

VFY

VAX-11 Utilities Reference Manual

CONVENTIONS USED IN THIS DOCUMENT

System messages are displayed or printed in lowercase letters
(when
the output device is capable of displaying or printing lowercase
letters). In this document, no attempt is made to distinguish between
the fixed and variable portions of the text of a message; the
distinction is obvious when a message is actually output.
The following conventions
variable data:

are

used

indicate

certain

types

'location'

indicates a virtual address in hexadecimal format

xxxxxxxx

indicates data displayed in hexadecimal format

nnn

indicates data displayed in decimal format

CHAPTER 1
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, and an
error results, the system locates the message associated with the
error and displays it.
Messages are displayed on the current device identified by the logical
name SYS$0UTPUT. For an interactive user, this device is a terminal;
for batch job users, it is the batch job log file.
If the logical
device SYS$ERROR is different from SYS$0UTPUT, the system also 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 specify
as SYS$OUTPUT for the procedure. SYS$ERROR remains assigned to your
current error device.
Then, if any errors occur during the command
procedure's execution, the error messages are displayed on your
terminal, as well as entered in the specified file.
The error message associated with any error code can be retrieved by
issuing the $EXIT command in an indirect file. Create the file
ERROR.COM by typing:
$EXIT %X'Pl
Then, to display the message, type:
@ERROR number
By issuing the command WRITE SYSSOUTPUT "F$MESSAGE(%Xcode)"
can be linked, as described in the following section.
The last error code is always in DCL symbol
this by typing SHOW SYMBOL $STATUS.

1.1.1

$STATUS.

You

messages
can

show

Linked Messages

Frequently, a system message appears with one, and sometimes more,
additional messages.
For example, the TYPE command calls VAX-11
Record Management Services (VAX-11 RMS) to locate and open a file.
If
the file does not exist, the TYPE command displays a message
indicating that it cannot open the file;
a VAX-11 RMS message follows
indicating the reason.
Linked messages usually display the return
status of the different facilities called and provide a detailed
explanation of the error.
1-1

INTRODUCTION

When more than one message is issued, messages after the first are
prefixed with a hyphen {-) rather than a percent sign (%). A series
of messages, then, can help you determine where an error occurred.

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

1.2

FORMAT OF SYSTEM MESSAGES

The general format of messages
system is:

displayed

the

VAX/VMS

operating

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

It has one of the following values:

Code

Meaning

Success
Information
Warning
Error
Fatal, or severe error

w
E
F

Severity levels are described in more detail in Section 1.2.1.
I DENT

An abbreviation of the message text;
the message descriptions in
Chapter 2 are alphabetized by this abbreviation.
TEXT

The explanation of the message.
[-FACILITY-L-IDENT,TEXT]
The next message.

1-2

INTRODUCTION
Severity Levels

1.2.1

The severity level of a message is included in the status message from
the component.
Success and information messages are just that; the
system is informing you that it 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 is
complete.
Warning messages indicate that the command may have performed some,
but not all, of your request, and that you may need to verify command
or program output.
Error messages indicate that the output or program result
incorrect, but the system may attempt to continue execution.

Fatal messages indicate that the system cannot continue
the request.

1.3

execution

RECOVERY PROCEDURES

Error messages generally occur for the following reasons:
•

An error in entering a command occurs: a spelling or syntax
error in the command, or incorrect file specifications.

•

A required resource is currently unavailable.

•

Programming errors are detected during
image.

•

System software or hardware errors occur.

the

execution

Recovering from Command Entry Errors

1.3.1

When an error occurs following interactive command entry, you must
generally reenter the command. Messages from the command interpreter
are generally 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
entered an invalid value for a parameter or qualifier. In these
cases, you can use the HELP command or consult the VAX/VMS Command
Language User's Guide to determine the legal values before you try to
reenter the command.
Errors in file specifications
following reasons:
•

device

names

can

occur

for

the

For a command that has a default file type, you entered only
the file name, but the file name is currently defined as a
logical name. The system translated the logical name and the
resulting file specification is not valid within the context
of the command.

1-3

INTRODUCTION

•

The syntax of the file specification is invalid.
A device
name was not terminated with a colon; a directory name was
not enclosed in brackets; a file name has more than nine
characters, a file type has more than three characters; an
alphabetic version number was specified;
or nodename was
included and had characters other than numerics or uppercase
alphabetics, or the connection to the target node could not be
made.

Unavailable Resources

1.3.2

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 resource wait mode, so that when
such a condition occurs, control returns immediately to the calling
program with an error status.
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.

Recovering from Programming Errors

1.3.3

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 0 to
get information about the exit status.
If it is an abnormal (or
error) exit, the system message associated with the register 0 value
is displayed.
Programming errors are caused by:
•

Incorrect coding of arguments
example, system services)

for

called

procedures

(for

•

Logic errors in proqramming

•

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-11 Symbolic Debugger can help you discover and correct
programming errors.
For details on how to use the debugger, see the
VAX-11 Symbolic q_e~~-gger 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 Guide provides
submit a Software Performance Report (SPR).

1-4

information

how

INTRODUCTION

The VAX/VMS Operator's Guide contains information on how to run
utilities that can verify the status of a mass storage volume or
verify that a hardware device is operational. If the hardware device
is not operational, inform the system manager.

1-5

CHAPTER 2
MESSAGES

ABEND, 'string' aborted
Facility:

Shared by several facilities

Explanation:

A program phase has been prematurely terminated.

User Action:

None.

ABENDD, 'string' aborted at 'system date and time'
Facility:

Shared by several facilities

Explanation:

A program phase has been prematurely terminated.

User Action:

None.

ABENDT, 'string' aborted at 'system time'
Facility:

Shared by several faciliti'es

Explanation:

A program phase has been prematurely terminated.

User Action:

None.

ABFNAM, ambiguous function name
Facility:

VAX/VMS Command Language Interpreter

Explanation: A lexical function name was truncated
characters to make the function name unique.

User Action: Reenter the command;
characters of the function name.

least

specify

too

few
four

ABKEYW, ambiguous keyword
Facility:

VAX/VMS Command Language Interpreter

Explanation: A keyword or qualifier name was truncated to
few characters to make the keyword or qualifier name unique.

too

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.

2-1

MESSAGES

ABORT, abort
Facility:

VAX/VMS System Services

Explanation:

An attempted operation was aborted:

The system returns this status for an I/O
canceled before it was completed.

request

Following a network request, this
logical link was disconnected.

indicates

status

that

was

that

User Action: The operating system does not normally display this
message;
user programs should be coded to detect and respond to
the status return.

ABSYMD, ambiguous symbol definition
Facility:

VAX/VMS Command Language Interpreter

Explanation: A new abbreviated symbol is ambiguous
existing symbol. The new symbol is not entered.
User Action: Display the current symbols
abbreviation of the ambiguous symbols.

and

with

adjust

an
the

ABVERB, ambiguous verb
Facility:

VAX/VMS Command Language Interpreter

Explanation: A command name was truncated to too few
to make the command name unique.
User Action: Reenter the command;
characters of the command name.

specify

characters
least

four

ACC, ACP file access failed
Facility:

VAX-11 RMS

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

ACCERR, non-blank accessibility field in volume lahels on device-name
Facility:

MOUNT

Explanation: The accessibility field on the tape mounted on the
device indicated has a nonblank accessibility field. This field
denies access to the tape.
User Action: Mount the tape with the /OVERRIDE=ACCESSIBILITY
qualifier
(you must be the owner of the volume or have volume
protection privilege).

2-2

MESSAGES

ACCONFLICT, file access conflict
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned by I/O functions. An attempt to access a file failed
because the type of access conflicts with the current file
access.
User Action: Check for a programming error.
Begin debugging
procedures to verify the nature of the problem and to correct it.

ACCQUOTA, ACCOUNT had inadequate quota at remote node
Facility:

VAX/VMS System Services

Explanation: This severe error message is associated with a
status code returned from a system service request. An attempt
was made to initiate a DECnet 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 to
initiate the connection later.
Consult the DECnet-VAX User's
Guide for additional information.

ACCVIO, access violation, reason
PC=location, PSL=xxxxxxxx
Facility:

mask=xx,

virtual

address=location,

VAX/VMS System Services

Explanation: An image attempted to read from or write to a
memory location that is protected against the current mode. This
message indicates an exception condition and is followed by a
register and stack dump to help you to locate the error.
User Action: Examine the PC and virtual address displayed in the
message and check the program listing to verify that instruction
operands or procedure call arguments are correct.

ACCVIO, compatibility mode access violation
Facility:

RSX

Explanation: An RSX-llM image attempted to access an area of
memory outside its virtual address space. The PC contains the
address of the instruction that caused the error.

In RSX-llM, the PC contains the address following the erroneous
instruction. This message corresponds to the RSX-llM termination
message MEMORY PROTECTION VIOLATION.
User Action: Determine the instruction or
error occurred and correct the error.

2-3

statement

where

the

MESSAGES

ACMINVOP, invalid accounting manager request
Facility:

Job controller

Explanation: An accounting manager request contained an invalid
message code;
or, the request itself was not valid. This
message is associated with a status code returned by the system
accounting routine.
The operating system does not normally
display this message.
User Action: Check for a programming error.
See the VAX/VMS
System Services Reference Manual for coding specifications.

ACNTOPN, error opening account file
Facility:

Job controller

Explanation: The system accounting routine could not open the
accounting file.
This message is generally displayed on the
operator's console.
User Action: Examine the accompanying messages to determine the
reason the file could not be opened. Usually, these messages
will indicate how to correct the condition.

ACNTWRT, error writing account file
Facility:

Job controller

Explanation: The system accounting routine could not write
This message is generally
records to the accounting file.
displayed on the operator's console.
User Action: None. When this condition occurs,
routine closes the file and opens a new file.

the

accounting

ACPNAME, ACP file name is too long
Facility:

MOUNT

Explanation: The file name specified for an ACP image
than nine characters.
User Action:
correctly.

Reenter the command;

specify

the

ACP

has

file

name

ACPTIME, ACP does not respond
Facility:

MOUNT

Explanation: The ACP requested in a
initialized.
Either the specified
system error has occurred.

MOUNT
image

command cannot be
is not an ACP, or a

User Action: Verify that the image is an ACP. If
as much information as possible and submit an SPR.

2-4

not,

collect

MESSAGES

ACPVAFUL, MTAACP's virtual address space is full
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from ~ file system ACP QIO request. No more volumes can
be serviced by the ACP because it does not have enough memory to
allocate control information for the new volume.
User Action: Start a different
qualifier in the MOUNT command.

ACP

using

the

/PROCESSOR

ACS, error in access control string
Facility:

VAX-11 RMS

Explanation: The access control string in the file specification
was invalid.
Too many characters or too many control or
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 quotes) and the number of subfields to 3.

ACT, file activity precludes operation
Facility:

VAX-11 RMS

Explanation: An I/O operation was attempted while other file I/O
activity was in progress.
User Action: Note the condition. Modify the source program,
if
necessary, to detect and respond to the condition. Correct the
program logic to avoid conflicting concurrent operations.

ADJARRDIM, adjustable array dimension error
Facility:

FORTRAN (run-time)

Explanation: Upon entry to
a
subprogram,
the
dimensioning information detected an array where:

evaluated

•

An upper dimension bound
bound, or

dimension

•

The dimensions implied an array that exceeded the
memory.

was

less

If execution continues, any attempt to
likely result in an access violation.

than

access

lower

that

addressable
array

User Action: Check the values of the expressions for the
of the array where it is dimensioned.

2-5

will
bounds

MESSAGES

AID, invalid area ID in XAB at 'location'
Facility:

VAX-11 RMS

Explanation: An allocation XAB for a $CREATE, $DISPLAY, $EXTEND
or $OPEN operation contains an invalid area identification number
field.
User Action: The status value (STV) field of the FAB provides
the address of the XAB in error. Verify that the cnll to the
VAX-11 RMS service was coded correctly.

ALIGNXCEED, alignment' exceeds PSECT alignment
Facility:

VAX-11 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 conflicting
alignments.
The
.PSECT
directive should specify the largest alignment required in the
program section.

ALLOCFAIL, index file allocation failure
Facility:

INITIALIZE

Explanation: The INITIALIZE command 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;
the /HEADERS qualifier.

specify a smaller

value

for

ALN, alignment options error in XAB at 'location'
Facility:

VAX-11 RMS

$EXTEND
Explanation: The allocation XAB for a $CREATE or
(ALN
operation contains an invalid alignment boundary type
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-11 RMS service was coded correctly.

ALQ, invalid allocation quantity (negative, or 0 on $EXTEND)
Facility:

VAX-11 RMS

Explanation: An invalid allocation quantity was specified in
allocation XAB or FAB for a $CREATE or $EXTEND operation.

User Action: Verify that the call to the VAX-11 RMS service was
coded
correctly.
For file creation operations, the error
indicates that the value specified is larger than the maximum
allowabl~
value.
For file extension operations, the error
indicates that the value specified was less than or equal to O.
2-0

MESSAGES
AMBIG, ambiguous parameter 'parameter'
Facility:

NCP

Explanation:

The command has a nonunique input.

User Action:

Reenter the command with a unique parameter.

AMBIGKEYW, more characters needed to identify keyword
Facility:

Back translator

Explanation: A command keyword was truncated to
too
few
characters to make it unique; another keyword exists that begins
with the same characters.
User Action: Reenter the command;
of the keyword.

type at least four characters

AMBKEY, 'keyword' is an ambiguous keyword
Facility:

VAX-11 Run-Time Procedure Library

Explanation: The indicated keyword was truncated to too few
characters to make it unique within its context. This message is
associated with a status code returned from the VAX-11 Run-Time
Procedure Library.
User Action: Correct the source
program.
characters in the keyword to make it unique.

Specify

enough

AMBQUAL, ambiguous qualifier or privilege name
Facility:

INS

Explanation: The keyword was truncated to too few characters
make it unique.

User Action: Reenter the command line;
more characters.

expand

the

keyword

ANI, not ANSI "D" format
Facility:

VAX-11 RMS

Explanation: The records in a magnetic tape file do not
to the ANS standard for magnetic tape (D format).

conform

User Action: Modify the program that writes the tape file so
that the file is in the correct format. Or, use an alternative
method of reading the file (for example, use VAX-11 RMS block
I/O).

2-7

MESSAGES

AOP, allocation options error in XAB at 'location'
Facility:

VAX-11 RMS

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 address of the XAB in error. Verify that the call to the
VAX-11 RMS service was coded correctly.

APPENDED, input-file-spec appended to output-file-spec (nnn blocks)
APPENDED, input-file-spec appended to output-file-spec (nnn records)
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.

The message is informational.

AQBTIME, ACP queue is unstable
Facility:

MOUNT

Explanation: The system cannot start the ACP specified in a
MOUNT command request.
This message indicates an operating
system·software error.
User Action:
an SPR.

Collect as much information as possible and

submit

ARGDONMAT, Arguments don't match
Facility:

BASIC (run-time)

Explanation: The arguments in a function call do not match the
arguments defined for the function, either in number or in type.
This is a fatal error.
User Action: Change the arguments in the function call to
those in the DEF, or change the arguments in the DEF.

match

ARGTOOLAR, Argument too large in EXP
Facility:

BASIC (run-time)

Explanation: The program contains either an argument larqer than
88 to the EXP function, or an exponentiation operation that
results in a number greater than 1E38. This is a fatal error.
User Action: Change the EXP argument to one in the valid
or reduce the size of the exponent.

2-8

range,

MESSAGES

ARGTOOLONG, argument too long
Facility:

VAX-11 MACRO assembler

Explanation:

An argument was more than 512 characters long.

User Action:

Reduce the length of the argument.

ARRMUSSAM, Arrays must be same dimension
Facility:

BASIC (run-time)

Explanation: The program attempted to perform matrix addition or
subtraction on input arrays with different dimensions. This is a
fatal error.
User Action: Redimension the arrays so
have identical dimensions.

that

the

input

arrays

ARRMUSSQU, Arrays must be square
Facility:

BASIC (run-time)

Explanation: The program attempted matrix inversion (MAT INV) on
an array that is not square. This is a fatal error.
User Action: Redimension
performing MAT INV.

the

array

before

square

ARTRES, reserved arithmetic trap at PC location, PSL=xxxxxxxx
Facility:

VAX/VMS System Services

Explanation:

An unknown arithmetic exception occurred.

User Action: This message should not occur.
inform the system manager.

If it

does

occur,

ASCTOOLONG, ASCII string too long
Facility:

VAX-11 MACRO assembler

Explanation: The string in an .ASCIC directive was more than 255
characters or the string in an .ASCID directive was more than
05535 characters.
User Action:

Reduce the length of the string.

ASGNMNTSYN, assignment syntax error
Facility:

VAX-11 MACRO assembler

Explanation:
error.

A direct assignment statement

User Action:

Correct the syntax.

2-9

contained

syntax

MESSAGES

ASTFLT,
AST
fault,
SP=xxxxxxxx
param=xxxxxxxx,
PSL=xxxxxxxx, target PC=location, PSL=xxxxxxxx
Facility:

PC=location,

VAX/VMS System Services

Explanation: The system attempted to deliver an asynchronous
system trap (AST)
to an image, but the user stack pointer was
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, 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.
Locate the programming error that modified the stack.

ATPC, at PC=xxxxxxxx
Facility:

Shared by several facilities

Explanation: This message generally
indicating a software failure.
User Action:
message(s).

accompanies

Take corrective action based

the

message

accompanying

ATR, file attributes read error
Facility:

VAX-11 RMS

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.

ATTACCNON, attempt to access non-existent record
Facility:

FORTRAN (run-time)

Explanation:

One of the following conditions occurred:

•

An attempt was made using direct access to READ, FIND or
DELETE a nonexistent record from a relative organization file.

•

An attempt was made to access beyond the end of the file with
a direct-access READ, or FIND to a sequential organization
file.

•

An attempt was made with a keyed access READ statement to read
a nonexistent record of an indexed organization file.

User Action: Correct the given record number. Or, correct the
program to include an ERR= or IOSTAT= specification to detect and
respond to a non-existent record condition.

2-10

MESSAGES

ATTCONSTO, attempt to continue from stop
Facility:

VAX-11 Run-Time Procedure Library

Explanation: A condition handling
procedure
attempted
to
continue from a call to LIB$STOP;
that is, the procedure
attempted to continue from a noncontinuable error by returning a
successful completion status.
Usef 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.

ATW, file attributes write error
Facility:

VAX-11 RMS

Explanation: A write error occurred during a VAX-11 RMS
to write a file header.

attempt

BACERR, BACKSPACE error
Facility:

FORTRAN (run-time)

Explanation:

One of the following conditions occurred:

•

The file was not a sequential organization file.

•

The file was not opened for sequential access.
(A unit opened
for append access may not be backspaced until a REWIND
statement is executed for that unit.)

•

RMS detected an error
BACKSPACE statement.

condition

during

execution

User Action: If a VAX-11 RMS error message accompanies the
message, use the VAX-11 RMS message to determine the cause of the
error. Ensure that the BACKSPACE statement specifies a logical
unit connected to a sequential organization file opened for
sequential access.

BADACP, invalid syntax on /PROCESSOR qualifier
Facility:

MOUNT

Explanation: The keyword or file specification value specified
for the /PROCESSOR qualifier is not correctly specified.
User Action: Reenter the command;
refer to the VAX/VMS Command
Language User's Guide, if necessary, for the correct syntax.

2-11

MESSAGES

BADACP, unable to start network acp
Facility:

NCP

Explanation:
CCP.EXE.

NCP could not create a process or

User Action: Ensure that enough processes
that DECnet has been properly installed.

can

could
be

not

find

created

and

BADATTRIB, bad attribute control list
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned by I/O functions. An invalid code or size was specified
in the read or write attribute list for a file system ACP QIO
function.
User Action: Check far a programming error.
Begin debugging
procedures to verify the source of the problem and to correct it.

BADBLK, END issued without corresponding BEGIN
Facility:

VAX/VMS Command Language Interpreter

Explanation: A .END was encountered within a command file when
no blocks were currently defined.
This message is issued,
instead of BLKUNDFLOW, when blocks have been defined in an outer
level command file.

the

block

Explanation: The library procedure LIB$FREE VM was
an invalid virtual storage address.
-

called

with

User Action: Begin debugging procedures to
and to correct it.

the

User Action:
structure.

Examine the command

file

and

correct

BADBLOADR, bad block address
Facility:

VAX-11 Run-Time Procedure Library

verify

problem

BADBLOCKS, invalid syntax in bad block list
Facility:

INITIALIZE

Explanation:
invalid.

The command syntax for the /BAD_BLOCKS qualifier is

User Action: Reenter the command; use the HELP command or refer
to the VAX/VMS Command Language User's Guide, if necessary, for
the correct syntax. If the list of blocks is long, place the
command in a command procedure.

2-12

MESSAGES

BADBLOSIZ, bad block size
Facility:

VAX-11 Run-Time Procedure Library

Explanation:
request for
large.

The library procedure LIB$GET VM was called with a
zero blocks or the block size specified was too

User Action:
If the block size requested was zero, correct the
source program.
If the block size specified was too large, use
the SET WORKING SET command to increase the current working set
limit for your process and retry the program.

BADBUG, please report TRACE bug no.
Facilty:

nnn

Traceback

Explanation: This message indicates
error in the traceback facility.

internal

programming

User Action: Collect as much information as possible and submit
an SPR. Include in the SPR the bug number (nnn) displayed in the
message.

BADBYTE, invalid data (xx) at 'location'
Facility:

Shared by several facilities

Explanation:
location.

The

User Action:

None.

specified

data

invalid

the

given

qualifier

have

BADCACHE, invalid syntax on /CACHE qualifier
Facility:

MOUNT

Explanation: The options given with the
invalid syntax.
User Action:

/CACHE

Verify the command and reenter the correct syntax.

BADCHKSUM, bad file header checksum
Facility:

VAX/VMS System Services

Explanation:
returned by
invalid.

This message is associated with a status code
I/O functions. The checksum in the file header is

User Action: Check for a programming error.
Begin
procedures to verify the problem and to correct it.

BADCON, cannot connect to file 'file-spec'
Facility:

NCP

Explanation:

Possible disk drive error.

User Action:

Check the drive for proper functioning.
2-13

debugging

MESSAGES

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:
copies.

Reenter the command;

specify a different number of

BADDATCHK, invalid keyword -0n /DATACHECK qualifier
Facility:

MOUNT and INITIALIZE

Explanation: The keyword specified for the /DATACHECK
was neither READ nor WRITE.
User Action:

Reenter the command;

qualifier

specify either READ or WRITE.

BADDATDAT, data echoed invalid
Facility:

DTSEND

Explanation:

Test error.

User Action:

Retry the test.

BADDATLEN, not enough data sent/received
Facility:

DTSEND

Explanation:

Test error.

User Action:

Retry the test.

BADDELIM, invalid delimiter following 'command'
Facility:

Shared by several facilities

Explanation: An invalid character occurred in a command.
message displays the rejected portion of the command.
User Action: Check the command for a spelling or
Reenter the command.

The

syntax

error.

Explanation: The value specified for a tape density was
800 nor 1600.

neither

User Action: Reenter the command;
for the density.

BADDENS, unknown value on /DENSITY qualifier
Facility:

MOUNT and INITIALIZE

2-14

specify either

800

lnOO

MESSAGES

BADDIRDEV, Bad directory for device
Facility:

BASIC (run-time)

Explanation: The device directory
unreadable. This is a fatal error.
User Action:

does

not

exist

Supply a valid directory.

BADDST, no symbols in image
Facility:

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:
an SPR.

Collect as much information as possible and

BADDSTMAP, failure to map symbol table, CREMAPSEC status
Facility:

submit

xxxxxxxx

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
status code.
If the reason is anything other than
virtual address space, assume that the problem is
problem.
Collect as much information as possible and
SPR.

BADDSTVBN, image symbol table VBN
Facility:

indicated
a lack of
a system
submit an

nnn

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
an SPR. Include in the SPR the virtual block number (VBN) number
(nnn) displayed in the message.

BADENTRY, bad format for .ENTRY statement
Facility:

VAX-11 MACRO assembler

Explanation: The .ENTRY directives
point name and an entry mask.
User Action:

did

not

specify

Correct the .ENTRY directive syntax.

2-15

entry

MESSAGES

BADESCAPE, syntax error in escape sequence
Facility:

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. Check the required
syntax for the escape sequence you are attempting to use.

BADEXE, failure to open image file 'file-name'
Facility:

Traceback

Explanation: The format of the indicated executable image file
is inconsistent with that expected by the operating system. The
file cannot be opened.
This message indicates an internal
operating system error.
User Action:
an SPR.

Collect as much information as possible and

submit

BADEXECLO, failure to close image file 'file-name'
Facility:

Traceback

Explanation: The format of the indicated executable image file
is inconsistent with that expected by the operating system. The
file cannot be closed.
This message indicates an internal
operating system error.
User Action:
an SPR.

Collect as much information as possible and

submit

BADEXERAB, failure to connect image file 'file-name'
Facility:

Traceback

Explanation: The format of the indicated executed image file is
inconsistent with that expected by the operating system. This
message indicates an internal operating system error.
User Action:
an SPR.

Collect as much information as possible and

submit

BADFIELD, 'name' field invalid at 'location'
Facility:

Shared by several facilities

Explanation:
location.

The

User Action:

None.

specified

data

2-16

invalid

the

given

MESSAGES

BADFIL, badly formatted file 'file-spec'
Facility:

NCP

Explanation:

The file was corrupted.

User Action:

Recreate the file.

BADFILEHDR, bad file header
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a file system ACP QIO request.
The message
indicates that the file header format is invalid;
for example,
the structure is not consistent or the storage map indicates free
blocks.
User Action: Check for a programming error.
Determine the
instruction or statement at which the error occurred, using the
debugger if necessary, and correct the error.

BADFILENAME, bad file name syntax
Facility:

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 O
through 9 and that they are no longer than nine characters.

BADFILEVER, bad file version number
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a file system ACP QIO request.
The message
indicates that the file version number in a file specification is
greater than 32727.
User Action: Check for a programming error.
Verify that
version numbers are specified that are greater than 32727.

BADFORM, 'form-type' is an invalid form type
Facility:

Shared by several facilities

Explanation: The form type specified with /FORMS is not
the forms defined by SYS$SYSDISK: [SYSMGR) :FORMSTYPE.DAT.
User Action:

Respecify with a valid form name.

2-17

one

MESSAGES

BADFUNC, invalid function type received
Facility:

DTSEND

Explanation:

DECnet test program protocol incompatibility.

User Action:
equivalent.

Run

against

compatible

version

DTRECV

BADHDR, no symbol table data in image header
Facility:

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:
an SPR.

BADHOMBLK,

~ad

Facility:

Collect as much information as possible and

submit

home block encountered on volume
MOUNT

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:
operation.

Repair or reinitialize the

volume

and

retry

the

BADIMGHDR, bad image header
Facility:

VAX/VMS System Services

Explanation: An image to be executed with the RUN command 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.

BADINDEX, invalid syntax on /INDEX qualifier
Facility:

INITIALIZE

Explanation:
invalid.

The command syntax

for

the

/INDEX

qualifier

User Action: Reenter the command; use the HELP command or refer
to the VAX/VMS Command Language User'~_Q~ide, if necessary, for
the correct syntax.

2-18

MESSAGES

BADIRECTORY, bad directory file format
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a file system ACP QIO request.
The message
indicates that the directory file specified is not valid. Either
the file is not a directory or the directory file contains bad
data.
User Action: Check for a programming error.
Verify that the
file specified is a directory. If so, use the DUMP command to
determine whether the file is in a valid state.

BADISD, illegal image section descriptor
Facility:

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: The file may be corrupted or not an executable
image.
There also may be a problem associated with the LINKER.
If this is suspected, submit an SPR.

BADJOBID, 'name' is a bad job identifier
Facility:

Shared by several facilities

Explanation: The job identifier specified by /ENTRY
or not valid.
User Action: Respecify a valid job identifier
the DCL SHOW QUEUE command.

missing

obtained

through

BADJOBNAME, 'name' is an invalid job name
Facility:

Shared by several facilities

Explanation:
va 1 id.

The job name specified by /NAME is missing

not

User Action: Respecify a valid job name obtained through the DCL
SHOW QUEUE command.

BADKEY, illegal key
Facility:

LIBRARY

Explanation: This severe error message is generated
LIBRARY command. The specified module is illegal.
User Action:

the

Reenter the command line specifying a legal module.

2-19

MESSAGES

BADKEY, 'keyword' is an invalid keyword
Facility:

Shared by several facilities

Explanation: The command did not recognize a word in a position
where it expects only certain values. The message displays the
rejected portion of the command.
User Action: Check the command for a spelling or syntax error.
Use the HELP command or refer to the VAX/VMS Command Language
User's Guide, if necessary, for the valid keywords and reenter
the command:·

BADLEXARG, illegal lexical function argument
Facility:

VAX-11 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:

VAX-11 MACRO assembler

Explanation:

The MACRO string operator contained a syntax error.

User Action:

Correct the MACRO string operator syntax.

BADLIBREF, invalid library/common reference,
Facility:

'library-name'

RSX

Explanation: An RSX-llM image referred to a library or common
area that has been altered since the image was built and that is
now inconsistent with the image.

common

User Action: Collect as much information as possible and
an SPR.
(See BADLOGICPC message.)

submit

User Action:
area.

Rebuild the image with the new

library

BADLOGIC, internal logic error detected [at PC location]
Facility:

Shared by several facilities

Explanation:

An internal software error occurred.

2-20

MESSAGES
BADLOGICPC, internal logic error detected at PC
Facility:

location

Shared by several facilities

Explanation: There was an internal error in the VAX-11 MACRO
assembler;
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 assembly. If the error is reproducible,
notify your system manager to submit an SPR.
The address
displayed with the error message and the source program should be
included in the SPR.
BADLONG, invalid data (xxxxxxxx) at 'location'
Facility:

Shared by several facilities

Explanation:
location.

The

User Action:

None.

specified

data

invalid

the

qiven

BADMAIL, unexpected mail received, type is 'mail-type'
Facility:

DTSEND

Explanation:

The logical link was broken.

User Action:

Retry the operation.

BADOPEN, cannot open file 'file-spec'
Facility:

NCP

Explanation:

There is a problem in reading from disk.

User Action: Ensure that the disk drive is operational and
no hardware problems exist.

that

BADOVR, unknown keyword on /OVERRIDE qualifier
Facility:

MOUNT and INITIALIZE

Explanation:
invalid.

The command syntax for the /OVERRIDE

qualifier

User Action: Use the HELP command or ref er to the VAX/VMS
Command Language User's Guide,
if necessary, for the legal
keywords, and reenter the command.

2-21

MESSAGES
BADPARAM, bad parameter value
Facility:

VAX/VMS System Services

Explanation: A value specified for a system function
valid. Several conditions can cause this error:

not

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.

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

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 a bad
format.

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.

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

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. See the VAX/VMS System Services
Reference Manual for coding specifications.
··------·-·-----~···~
BADPARS, unrecognized parameter 'parameter'
Facility:

NCP

Explanation:

A syntax error was detected in the command input.

User Action:

Reenter the command correctly.

BADPARVAL, invalid parameter value
Facility:

NIC

Explanation: One of the downline load parameters stored in the
RSX-11 file image of the system to be loaded was unacceptable.
User Action:

Use VNP to modify the RSX-11 system image.

BADPAT, invalid data pattern received
Facility:

DTSEND

Explanation:

Test error.

User Action:

Retry the test.

2-22

MESSAGES
BADPRO, invalid syntax on /PROTECTION qualifier
Facility:

MOUNT and INITIALIZE

Explanation:
incorrect.

The command syntax for the /PROTECTION qualifier is

User Action: Type HELP SPECIFY PROTECTION or refer to the
VAX/VMS Command Language User's Guide,
if necessary, for the
correct syntax, and reenter the command.
BADPRTY, 'priority' is an invalid priority
Facility:

Shared by several facilities

Explanation:

Priority must be within the range 0 through 31.

User Action:

Respecify with a valid priority.

BADQFILE, invalid disk quota file format
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a file system ACP QIO request. The quota file has
an invalid format.
User Action:
BADQNAME,

Delete and recreate the quota file [O,O]QUOTA.SYS.

'queue-name' is an invalid queue name

Facility:

Shared by several facilities

Explanation:
batch queue.

The queue name is

not

initialized

device

User Action: Respecify with one of the queues listed in the SHOW
QUEUE command.
BADQUEUEHDR, interlocked queue corrupted
Facility:

VAX/VMS System Services

Explanation: This severe error message is associated with a
An
status
code
returned from a system service request.
interlocked queue is corrupted.
User Action: Determine
correcof the problem.

why

the

queue

became

corrupted

and

BADRANGE, bad block address not on volume
Facility:

INITIALIZE

Explanation: A block number specified
qualifier is a nonexistent block.

for

the

/BAD BLOCKS

User Action: Verify the command line with the current bad block
data and reenter the command. If the error persists, run the BAD
utility to obtain the correct data.
2-23

MESSAGES
BADRECIDE, Bad record identifier
Facility:

BASIC (run-time)

Explanation: The program attempted a
record
access
that
specified either a zero or negative record number on a RELATIVE
file, or a null key value on an INDEXED file. This is a fatal
error.
User Action:
valid value.

Change the record number or key specification to

BADRECVAL, Bad RECORDSIZE value on OPEN
Facility:

BASIC (run-time)

Explanation: The value in the RECORDSIZE clause in the OPEN
statement is zero or greater than ln384. This is a fatal error.
User Action:

Change the value in the RECORDSIZE clause.

BADRET, RETURN was issued without a subroutine
Facility:

VAX/VMS Command Language Interpreter

Explanation: An MCR indirect command file attempted to execute a
.RETURN directive that was not preceded with an associated .GOSUB
directive; that is, the indirect command file attempted to
return from a subroutine that it entered as a result of some
directive other than .GOSUB.
User Action: Check the logic flow in the indirect command
Correct the indirect command file and reexecute it.

file.

BADRSP, received wrong size nice message
Facility:

NCP

Explanation:

NICE protocol incompatibility.

User Action:

Run aqainst compatible NICE object or equivalent.

BADSEQNUM, invalid data sequence received
Facility:

DTSEND

Explanation:

Test error.

User Action:

Retry the test.

BADSTA, bad stack
Facility:

VAX-11 Run-Time Procedure Library

Explanation:
accessed.

The user stack has an invalid format or

cannot

User Action: Recompile your program with the /CHECK=BOUNDS
qualifier
to
determine
whether
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.
2-24

MESSAGES
BADSTACK, bad stack encountered during exception dispatch
Facility:

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, invalid compatibility mode stack pointer
Facility:

RSX

Explanation: An RSX-llM image's SP points to an area of memory
outside
the
image's virtual address space.
This message
corresponds to the RSX-llM termination message BAD STACK.
User Action: Determine the instruction or statement at which the
error occurred and correct the error.
BADSTACK, stack has been overwritten
Facility:

Traceback

Explanation: The traceback facility cannot display the user
stack because it has determined that the frnme pointers are
inconsistent.
User Action: Check for the programming error that caused
stack to be overwritten. Correct the source program.

the

BADSTRUCT, invalid value on /STRUCTURE qualifier
Facility:

INITIALIZE

Explanation:
are l and 2.

The only legal values for the /STRUCTURE

User Action:

Correct the program.

qualifier

BADSUBFCN, invalid subfunction received
Facility:

DTSEND

Explanation:

DECnet test program protocol incompatibility.

User Action:
equivalent.

Run against

compatible

2-25

version

DTRECV

MESSAGES

BADTEXT, \

'text' \'text'

Facility:

VAX/VMS Command Language Interpreter

Explanation: An image request to a command language interpreter
(CL!)
resulted in an error.
The text supplies additional
information for tracing the problem.
User Action: Examine the requests your image makes to a CL!. In
particular, check that qualifier lists include all qualifiers
that the CL! will allow to be typed with a command.

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 usinq the rules
listed in the VAX/VMS Command Language User's Guide under "Rules
for Entering Dates and Times." ----·--------·-·---···-

BADUIC, invalid UIC syntax
Facility:

MOUNT and INITIALIZE

Explanation: The command contains an invalid UIC. The group and
member portions of a UIC must both be specified and must be
separated by a comma.
User Action: Reenter the command;
use the HELP command or refer
to the VAX/VMS Command Language User's Guide, if necessary, Eor
the correct syntax.
·

BADUSRDAT, connect/disconnect userdata invalid
Facility:

DTSEND

Explanation:

Test error.

User Action:

Retry the test.

BADUSRLEN, connect/disconnect userdata is wrong length
Facility:

DTSEND

Explanation:

Test error.

User Action:

Retry the test.

BADVALUE, 'value' is an invalid keyword value
Facility:

Shared by several facilities

Explanation: An invalid value was specified
command qualifier.

for

the

indicated

User Action: Check the command strinq for a spelling or syntax
error. Verify the values or syntax and reenter the command.

2-26

MESSAGES

BADVEC, invalid change mode or message vector
Facility:

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
to the VAX/VMS Real-Time User's Guide.

vector.

Ref er

BADVOLl, bad VOLl ANS label
Facility:

MOUNT and INITIALIZE

Explanation: The protection encoded on a tape volume label is
invalid or the label itself is invalid; the magnetic tape ACP
cannot process the tape. Either the tape is bad or is not an
ANS-labeled tape, or the hardware device is not reading the tape
properly.
User Action: Verify the tape volume. If necessary,
tape as a foreign volume and try to read it.

mount

the

BADWORD, invalid data (xxxx) at 'location'
Facility:

Shared by several facilities

Explanation:
location.

The

User Action:

None.

specified

data

invalid

the

BEGIN, 'string' beginning
Facility:

Shared by several facilities

Explanation:

Indicates a program phase is being started.

User Action:

None.

BEGIND, 'string' beginning at 'system date and time'
Facility:

Shared by several facilities

Explanation:

Indicates a program phase is being started.

User Action

None.

BEGINT,

'string' beginning at 'system time'

Facility:

Shared by several facilities

Explanation:

Indicates a program phase is being started.

User Action:

None.

2-27

given

MESSAGES
BEGOFFILE, beginning of file
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code from
the file system ACP.
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.
BES, bad escape sequence
Facility:

VAX-11 RMS

Explanation:

A terminal escape sequence is invalid.

User Action: The record is returned in the user record buffer.
Modify the program to detect and recognize the condition, or
reenter the input specifying a correct escape sequence.
BITMAPERR, I/O error on storage bitmap;
Facility:

volume locked

MOUNT

mount
Explanation: An I/O error was encountered during a
operation.
Existing files on the volume can be accessed hut
other operations, for example, create and delete, are not
possible.
User Action: If possible,
them. Submit an SPR.

remove

the

files

and

reinitialize

BITMAPINV, storage bitmap is invalid, volume ·locked
Facility:

MOUNT

Explanatio~:

The volume's storage bitmap contains invalid data.

User Action:
bitmap.

Use the DISKQUOTA REBUILD

command

repair

the

BKS, bucket size too large (FAB)
Facility:

VAX-11 RMS

Explanation: The bucket size specified in the FAB was larger
than 32.
If the bucket size was specified as zero, the maximum
record size is too large.
User Action: Verify that the call to the VAX-11 RMS service was
coded correctly.
See the formulas and rules for calculating
bucket size in the VAX-11 Record Management S~rvices Reference
Manual.

2-28

MESSAGES

BKZ, bucket size too large in XAB at 'location'
Facility:

VAX-11 RMS

Explanation: The bucket size field specified
XAB was larger than 32.

allocation

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-11 RMS service was coded correctly.
See the formulas and
rules for calculating bucket size in the VAX-11 Record Management
Services Reference Manual.

BLKDIRSYNX, block directive syntax error
Facility:

VAX-11 MACRO assembler

Explanation: A conditional block or
contained a syntax error.
User Action:

repeat

block

directive

Correct the directive syntax.

BLKOVRFLOW, block overflow
Facility:

VAX/VMS Command Language Interpreter

Explanation: An attempt was made to define more than 127
of blocks in an MCR indirect command file.
User Action:
file.

Reduce the number of block levels

the

levels
command

BLKUNDFLOW, block underflow
Facility:

VAX/VMS Command Language Interpreter

Explanation: An attempt was made to end a block when no blocks
have been defined;
that is, a .END was encountered before a
.BEGIN.
User Action:
structure.

Examine the command

BLKZERO, block zero is bad;
Facility:

file

and

correct

the

block

volume not bootable

INITIALIZE

Explanation: This message is generated by !NIT as a warning
message. The volume cannot be booted on a PDP-11. The volume is
usable on a VAX/VMS system disk.
User Action: The volume can still be mounted.
If the volume
must be booted on a PDP-11, use another disk. Otherwise, ignore
this message.

2-29

MESSAGES
BLN, invalid block length for control block (RAB/FAB)
Facility:

VAX-11 RMS

Explanation: An invalid value was specified in a VAX-11 RMS
or RAB block length field.

FAB

User Action: Check for a programming error.
Specifically,
ensure that the control block was properly initialized and not
modified after initialization.
BLOCKCNTERR, block count error
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a file system ACP QIO request.
The message
indicates that the number of blocks read differs from the number
of blocks recorded in the trailer labels when a file 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 tape is bad
or a hardware problem exists.
Mount the tape on another
drive/controller and perform the same operation again. If the
problem persists, the tape is probably bad.
BOF, beginning of file detected
Facility:

VAX-11 RMS

Explanation: During a backspace operation,
the
file
was
positioned at the beginning of the file before the specified
number of blocks were backspaced. The status value
(STV)
field
in the FAB or RAB contains the number of blocks actually spaced.
User Action: Note the condition. Modify the source program,
necessary, to detect and respond to the condition.

BRDESTRANG, branch destination out of range
Facility:

VAX-11 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 -128 bytes to +127 bytes from the
current PC.
Branch instruction with word displacements have a
range -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.

2-30

MESSAGES
BREAK, breakpoint fault at PC location, PSL=xxxxxxxx
Facility:

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.
BREAK, compatibility mode breakpoint trap
Facility:

RSX

This
Explanation: An RSX-llM image executed a BPT instruction.
message corresponds to the RSX-llM termination message BPT
EXECUTION.
User Action: Determine the instruction or statement at which the
error occurred and correct the error.
BUFBYTALI, device does not support byte-aligned transfers
Facility:

VAX/VMS System Services

Explanation: This severe error message is associated with a
status code returned from a system I/O request. 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.
BUFFEROVF, output buffer overflow
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a system service request.
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: None;
this is a success status
code.
operating system does not normally display this message.

The

BUFNOTALIGN, buffer incorrectly aligned
Facility:

VAX/VMS System Services

Explanation: This message
returned by I/O functions.
correctly aligned.

is associated with a status code
A table, list, or buffer area is not

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

2-31

MESSAGES
BUFOVF, command buffer overflow
Facility:

VAX/VMS Command Language Interpreter

Explanation: A command string, including continuation lines,
is
longer than the buffer used by the command interpreter to store a
command.
User Action: Shorten the command
entering more than one command.

and

reenter

it,

possibly

BUG, internal RMS error condition detected
Facility:

VAX-11 RMS

Explanation:

An internal software error occurred in VAX-11 RMS.

User Action:
an SPR.

Collect as much information as possible and

submit

BUGCHECK, internal consistency failure
Facility:

VAX/VMS System Services

Explanation:
failure.

The operating system

noted

User Action:
an SPR.

Collect as much information as possible and

BUG_DAP, internal network error condition detected;
Facility:

internal

software
submit

DAP code=xxxxxxxx

VAX-11 RMS

Explanation: A Data Access Protocol violation was detected by
VAX-11 RMS while attempting to communicate with the Remote Access
Listener.
User Action: Collect as much information as possible and submit
an SPR. The status value (STV) field of the FAB or RAB contains
the DAP status code. Consult the DECnet-VAX User's Guide to
interpret the status code. Note, however, that the explanation
is intended for users who are familiar with DAP.
BUG_DDI, invalid default directory
Facility:

VAX-11 RMS

Explanation:

An internal software error occurred in VAX-11 RMS.

User Action:
an SPR.

Collect as much information as possible and

2-32

submit

MESSAGES
CALFAI, CALL failed on routine
Facility:

COBOL (run-time)

Explanation: Failure to CALL the specified routine.
due to one of the following conditions:

This may be

•

The routine name is too long (greater than 31 characters).

•

The routine name is too short, for example, all blanks.

•

The routine name contains invalid characters.

•

The named routine is not in the linked image.

User Action: The user should either code the routine name to
conform to the syntax rules for proper routine name formation or
relink the image to include the missing routine.
CANCEL, I/O operation canceled
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned by I/O functions.
An input or output operation was
canceled before it completed. Usually, the request is canceled
at the image's request.
User Action: None.
The
display this message.

operating

system

does

not

normally

CANCHAARR, Cannot change array dimensions
Facility:

BASIC (run-time)

Explanation: The
program
attempts
to
one-dimensional array to two dimensions or vice
fatal error.
User Action:

redimension
a
This is a

versa~

Change the array dimensions in the DIM statement.

CANFAIL, CANCEL failed on routine
Facility:

COBOL (run-time)

Explanation: Failure to CANCEL the specified routine.
be due to a number of problems including:

This

•

The routine name is too long (greater than 31 characters).

•

The routine name is too short, for example, all blanks.

•

The routine name contains invalid characters.

•

The named routine is not in the linked image.

may

User Action: The user either should code the routine name to
conform to the syntax rules for proper routine name formation or
relink the image to include the missina routine.

2-33

MESSAGES
CANFINFIL, can't find file or account
Facility:

BASIC (run-time)

Explanation: The specified file
device. This is a fatal error.
User Action:

directory

entry

with

the

following

$MCR PIP filespec/RM
FILESTRUCT, unsupported file structure level
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a file control primitive (FCP) request. The file
structure on the accessed volume is not compatible with the ACP.
The operating system does not normally display this message.
User Action: Verify that the correct physical volume is mounted.
If the volume is new and does not contain data, use the
INITIALIZE command to initialize it in the correct format.
FILEXPDAT, file expiration date not yet reached
Facility:

BASIC (run-time)

Explanation: The program attempted to delete a file before
file's expiration date was reached. This is a fatal error.
User Action:

Change the file's expiration date.

2-81

the

MESSAGES
FILIS_LOC, file is locked
Facility:

BASIC (run-time)

Explanation: Although the program does not allow shared access,
it attempted to access a file that has been locked by another
user, or by the system. This is a fatal error.
User Action: Change the OPEN statement to allow shared access or
wait until the file is released by other user(s).
FILNAMSPE, file name specification error
Facility:

FORTRAN (run-time)

Explanation: A file name specification given to
or CALL ASSIGN was not acceptable to RMS.

OPEN,

INQUIRE,

User Action: Check the file name string displayed in the message
for illegal characters and correct the source program. If the
file name string was referred to by a variable name, check that
the variable was correctly initialized. If the file name string
is a logial name, verify that the logical name translates to a
valid file specification.
FILNOTACC, file not accessed on channel
Facility:

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:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a system service request. A system file that must
be in contiguous disk format is not contiguous.
User Action: Use the COPY/CONTIGUOUS
contiguous version of the file.

command

make

new

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-11 RMS message indicating the reason
for the failure.
User Action: Take appropriate action
VAX-11 RMS message.

2-82

based

the

associated

MESSAGES

FILNOTEXP, file is not expired [on volume on device name]
FILNOTEXP, file is not expired
Facility:

MOUNT and VAX/VMS System Services

Explanation: A file cannot be written or deleted because it
not reached its expiration date.

has

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

FILNOTFOU, file not found
Facility:

FORTRAN (run-time)

Explanation: A file with the specified name could not
during an open operation.

found

User Action: Use the full file specification displayed in the
message to determine whether the resulting specification is as
you intended it. Verify your current default disk and directory,
the disk and directory containing the required file and current
logical name assignments.

FILNOTFOU, file not found on OPEN
Facility:

COBOL (run-time)

Explanation: The named file was not found during the execution
of the OPEN statement. The file status variable, if present, has
been set to 97. No applicable USE procedure has been found.

A mistake in spelling the file specification
also cause this error.

for

the

file·

can

User Action: The user should examine the referenced directory to
check for the existence of the named file. Check the spelling of
the file specification.

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:

None.

FILOPN, file is already open
Facility:

VAX/VMS Command Language Interpreter

Explanation: An MCR indirect command file
directive for a file that is already open.
User Action:

Correct the command file.

2-83

contains

.OPEN

MESSAGES

FILPURGED, file-spec deleted
Facility:

Shared by several facilities

Explanation: The PURGE command displays the
of a file it is deleting.
User Action:

None.

file

specification

This message is informational.

FINERR, FIND error
Facility:

FORTRAN (run-time)

Explanation: RMS detected an error condition during execution of
a FIND statement.
User Action: Take corrective action based
VAX-11 RMS error message.

the

accompanying

FLG, invalid key definition flags in XAB at 'location'
Facility:

VAX-11 RMS

incorrectly
Explanation: Either XAB$M CHG or XAB$M NUL was
specified for the primary key definition XAB at the specified
address.
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-11 RMS service was coded correctly.

FLK, file currently locked by another user
Facility:

VAX-11 RMS

Explanation: An attempt was made to open or create a file that
has been locked as the result of another user's access, and 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:

Math Library

Explanation: An overflow condition occurred during execution of
a mathematics library procedure. This message results from an
incorrect call to the mathematics library, and usually indicates
that an argument is too small or too large.
User Action:
the message
library.

Use the traceback information and PC displayed in
to locate where your program called the mathematics

2-84

MESSAGES
FLOPOIERR, floating point error
Facility:

BASIC (run-time)

Explanation: A program operation resulted in a floating-point
number with absolute value outside the range lOE-38 to lOE38.
This is a fatal error.
User Action: Trap the error in an error handler.
is trapped, the number returned is zero.

If this

error

FLOUNDMAT, floating underflow in math library
user PC location
Facility:

Math Library

Explanation: An underflow
condition
occurred
during
the
execution of a mathematics library procedure and the caller was
enabled for floating underflow traps. This message results from
an incorrect call to the mathematics library. See the discussion
of the LIB$FLT UNDER procedure in the VAX-11 Run-Time Library
Reference Manual.
User Action: Locate the statement in
called the mathematics library and
occurred.
FLTDIV, arithmetic trap, floating/decimal
PC=xxxxxxxx,PSL=xxxxxxxx
Facility:

your program where you
the underflow condition

divide

zero

VAX/VMS System Services

Explanation: An arithmetic exception condition occurred as a
result of an attempt to divide a floating point/decimal number hy
zero.
User Action: Examine the PC location displayed in
and check the program listing to verify that
variables are specified correctly.
FLTDIV F,
arithmetic
fault,
PC=xxxxxxxx,PSL=xxxxxxxx

zero

Explanation: During a floatinq point operation, an
made to divide by zero.

attempt

was

User Action: Examine the PC location displayed in
and check the program listing to verify that
variables are specified correctly.

the messaqe
operands or

Facility:

floating

divide

the message
operands or

VAX/VMS System Services

2-85

MESSAGES
FLTOVF,
arithmetic
PSL=xxxxxxxx
Facility:

trap,

floating

overflow

PC=xxxxxxxx,

VAX/VMS System Services

Explanation: An arithmetic exception
result of a floating point overflow.

condition

occurred

User Action: Examine the PC location displayed in
and check the program listing to verify that
variables are specified correctly.
FLTOVF F,
arithmetic
fault,
PC=xxxxxxxxPSL=xxxxxxxx
Facility:

floating

the message
operands or

overflow

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
and check the program listing to verify that
variables are specified correctly.

the message
operands or

FLTPNTSYNX, floating point syntax error
Facility:

VAX-11 MACRO assembler

Explanation:

A floating-point constant contained a syntax error.

User Action:

Correct the syntax of the constant.

FLTUND, arithmetic
PSL=xxxxxxxx
Facility:

trap,

floating

underflow

PC=xxxxxxxx,

VAX/VMS System Services

Explanation: An arithmetic exception
result of floating point underflow.

condition

occurred

User Action: Examine the PC location displayed in
and check the program listing to verify that
variables are specified correctly.
FLTUND F,
arithmetic
fault,
PC=xxxxxxxx,PSL=xxxxxxxx
Facility:

floating

the message
operands or

underflow

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
and check the program listing to verify that
variables are specified correctly.

2-86

the message
operands or

MESSAGES
FNA, invalid file name string address
Facility:

VAX-11 RMS

Explanation: The file specification string address field in the
FAB is incorrect, or is in memory that cannot be read by the
caller.
User Action: Verify that the call to the VAX-11 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:

VAX-11 RMS

Explanation: This message is associated with a status code
returned from a file system ACP QIO request made by VAX-11 RMS.
An error occurred during a directory search.
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.
FNEWITFUN, FNEND without function call
Facility:

BASIC (run-time)

Explanation: The program
executing a function call.

executed a FNEND statement
This is a fatal error.

before

User Action: Check program logic to make sure that FNEND
statements are executed only in multi-line DEFs, or remove the
FNEND statement.
FNF, file not found
Facility:

VAX-11 RMS

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.
FNM, error in file name
Facility:

VAX-11 RMS

Explanation: The file name portion of a file specification is
incorrectly specified. For example, the file name contains more
than nine characters. Or, 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.

2-87

MESSAGES

FOP, invalid file options
Facility:

VAX-11 RMS

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-11 RMS service
coded correctly.

was

FORMAT, invalid media format
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned by I/O functions. An I/O operation failed because the
data medium is not in a format that the device driver expected.
User Action: Verify the physical data pack, reel,
to ensure that the correct data medium is mounted.

cartridge

FORVARMIS, format/variable-type mismatch
Facility:

FORTRAN (run-time)

Explanation: An attempt was made either to read or write a real
variable with an integer field descriptor (I or L), or to read or
write an integer or logical variable with a real field descriptor
(D, E, F, or G). If execution continued, the following actions
occurred:

Format

Action

I,L
D,E,F,G

convert as if INTEGER*4
convert as if REAL*4

User Action:
Either change the variable declaration
the FORMAT statement to correct the specification.

modify

FSZ, invalid fixed control header size
Facility:

VAX-11 RMS

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-11 RMS service
coded correctly.

was

FTM, network file transfer mode precludes operation (SQO set)
Facility:

VAX-11 RMS

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 this mode limits
data

2-88

MESSAGES
transfers to one direction (either transmit using $PUT/$WRITE or
receive using $GET/$READ);
other VAX-11 RMS services
are
disallowed.
User Action: Verify that the call to the VAX-11 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
Facility:

(insufficient space for allocation)
VAX-11 RMS

Explanation: A $CREATE or $EXTEND operation for
because there is not enough space on the volume.

file

failed

User Action: Delete or purge as many files as possible to free
up room on the volume, or request the system operator to do so.
If the volume is a private volume and no files can be deleted,
obtain a new volume.
GBLSECFAIL, failed to create global section
Facility:

INS

Explanation:

The image file was not fully installed.

User Action:

Retry the operation using /REPLACE.

GENERR, generated ERROR:
Facility:

Submit an SPR.

xxxxx message

VAX-11 MACRO assembler

Explanation: A .8RROR 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:
Facility:

xxxxx message

VAX-11 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.

GOTO_ALT, GO TO with no preceding ALTER
Facility:

COBOL (run-time)

Explanation: An attempt was made to perform a GO
there is no preceding ALTER.

for

which

User Action: The user should examine the logic of the program to
ensure that the execution of an ALTER statement precedes the
execution of the referenced GO TO statement.

?.-89

MESSAGES

GPTFULL, global page table is full
Facility:

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.

GSDFULL, global section descriptor table is full
Facility:

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.

the

failure

GSDTYP, module 'module name' file 'library file-spec' has
GSD record 'record type'

illegal

User Action: Wait and retry the
persists, notify the system manager.

Facility:

request.

LIBRARY

Explanation: This error message is generated by the LIBRARY
command. The specified object module is illegally formatted.
User Action: Recompile the object
into the library.

module

before

inserting

HALTED, transfer has been halted
Facility:

Shared by several facilities

Explanation:
If returned from a DR32 support routine
DR32 transfer is complete.

call,

the

User Action:
If the transfer halted unexpectedly, determine
cause of the error.

the

HANGUP, data set hang-up
Facility:

VAX/VMS System Services

Explanation: The associated terminal data-set has been
A CTRL/Y or unsolicited data AST was delivered.
User Action:

None.

2-90

hung-up.

MESSAGES

HDRNOTRES, unable to make image header resident
Facility:

INS

Explanation: Insufficient pool was available to make the header
resident, or the file has an image header larger than one block.
User Action:
pool.
Only
resident.

Use the SYSGEN parameter PAGEDYN to increase the
files with one block image headers may be made

HDRTRUNC, header truncated
Facility:

Librarian

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.

HEADERFULL, file header is full
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a file system ACP QIO request. The file header map
area on the volume is full and cannot be extended.
This error
occurs only when the file header extension is inhihited, for
example, when the user file is being extended.
User Action:

Compress the volume with DSC.

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.

HOMBLKBAD, primary home block is bad;
Facility:

backup used

MOUNT

Explanation: The primary home block of a disk is corrupted
unreadable; the back-up volume was used to mount the volume.
User Action:

Submit an SPR.

2-91

MESSAGES
HOMBLKCHK, home block software consistency check

Facility:

MOUNT

Explanation: A volume's home block has failed the software
consistency check during /BIND processing. The first occurrence
of this message is a warning;
the second is fatal.
User Action:
operation.

Repair or reinitialize the

volume

and

retry

the

IAL, invalid argument list

Facility:

VAX-11 RMS

Explanation:

The argument list on a call to SYS$RMSRUNDWN,
or SYS$SETDFPROT control routines either cannot he
accessed or contains invalid data.
SYS~SETDDIR,

User Action: Verify that the call to the VAX-11 RMS service
coded correctly.

was

IAN, invalid index area number in XAB at 'location'

Facility:

VAX-11 RMS

Explanation: The index area number specified in
the
key
definition XAB at the specified address is not a defined area for
the file.
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-11 RMS service was coded correctly.
IBF, illegal bucket format;

Facility:

STV

nnn

VAX-11 RMS

Explanation: VAX-11 RMS detected a corrupted bucket in an
indexed file.
Incorrect bucket control flaqs or an incorrect
bucket freespace value was detected.
User Action: Reorganize the file, if possible, or else 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-11 RMS or system
software errors, or inadvertent modifications of files by non-RMS
programs. Collect as much information as possible and submit an
SPR.
IBK, LAN bucket size not equal IAN bucket size in XAB at location

Facility:

VAX-11 RMS

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.

2-92

MESSAGES
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-11 RMS service was coded correctly. In particulnr, determine
that the correct area numbers and sizes were specified for the
index and lowest-level-index areas.
IDMISMATCH, ident mismatch with global section or shareable image
Facility:

VAX/VMS S¥stem 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
from two processors that do not have identical image files.
User Action: Copy the file from one processor to the
retry the operation.

other

and

!DR, invalid directory rename operation
Facility:

VAX-11 RMS

Explanation: A VAX-11 RMS $RENAME service was requested that
would rename a directory file into a directory tree that
contained the directory file.
The directory would then he
inaccessible. An example of incorrect usage is:
$RENAME [A]B.DIR [A.BJ
User Action: Modify the source program or reenter the command
specifying the correct old and new file specifications for the
$RENAME service.
IDX, index not initialized
Facility:

VAX-11 RMS

Explanation: The index of an indexed file could not be
initialized when inserting the first record.
User Action: Recreate the file.
possible and submit an SPR.

properly

Collect as much information

IDXCONCAT, index file cannot be concatenated
Facility:

Shared by several facilities

Explanation:
file.

An index file may not be concatenated with

User Action: Use an
indexed file.

indexed

file

2-93

load

program

another
load

the

MESSAGES
IDXFILEFULL, index file is full
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a file system ACP QIO request. No more files can
be written on the volume, because the maximum size of the index
file specified when the volume was initialized has been reached.
User Action: If the volume is a private volume, delete 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;
Facility:

backup used

MOUNT

Explanation: This message is generated by the MOUNT command.
The primary index file header is corrupted or unreadable;
the
back-up volume was used to mount the volume.
User Action:

Submit an SPR.

IDXMAPERR, I/O error on index file bitmap;
Facility:

volume locked

MOUNT

Explanation: I/O error encountered during a mount operation.
Existing
files
in the volume can be accessed hut other
operations, for example, create and delete, are not possible.
User Action: If possible,
them. Submit an SPR.

remove

the

files

and

reinitialize

IFA, illegal file attributes detected (file header corrupted)
Facility:

VAX-11 RMS

Explanation: The contents of the file
header
have
corrupted; the data is inconsistent and cannot be read.

been

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 an SPR.
IFDIRSYNX, IF directive syntax error
Facility:

VAX-11 MACRO assembler

Explanation:
error.

A conditional assembly directive contained a syntax

User Action:

Correct the syntax of the directive.

2-94

MESSAGES
IFEXPRNABS, IF expression not absolute
Facility:

VAX-11 MACRO assembler

Explanation: The expression in a .IF directive
absolute expression or contained undefined symbols.
User Action:

was

not

Change the values in the expression.

!FI, invalid internal file identifier (IFI) value
Facility:

VAX-11 RMS

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 opene<l, 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.
!FL, index bucket
'location'
Facility:

fill

size

larger

than

bucket

size

XAB

VAX-11 RMS

Explanation: The index bucket fill specified in
the
key
definition XAB at the specified address exceeds the bucket size
for the data area.
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-11 RMS service was coded correctly.
IFLEVLXCED, IF nesting level exceeded
Facility:

VAX-11 MACRO assembler

Explanation: The assembler encountered more than
nested conditional assembly hlocks.
User Action: Restructure the
conditional assembly blocks.

program

levels

decrease

nesting

ILLALLCLA, illegal ALLOW clause
Facility:

BASIC (run-time)

Explanation: The value specified for the ALLOW clause
(sharinq)
is illegal for the type of file organization. This is a fatal
error.
User Action:

Change the ALLOW clause value.

2-95

MESSAGES
ILLANSIBS, ANS magnetic tape block size must be at least 18
characters
Facility:

MOUNT

Explanation: The label specified for a tape contains
18 characters.
User Action: Reenter the command;
for the block size.

less

than

specify a minimum value of 18

ILLARGDESC, illegal operand argument descriptor
Facility:

VAX-11 MACRO assembler

Explanation:
invalid.

The operand descriptor in an .OPDEF

directive

User Action:

Use one of the valid operand descriptors.

was

ILLARGLOG, illegal argument in LOG
Facility:

BASIC (run-time)

Explanation: The program contains a negative or zero argument to
the LOG or LOGlO function. This is a fatal error.
User Action:

Supply an argument in the valid range.

ILLASCARG, illegal ASCII argument
Facility:

VAX-11 MACRO assembler

Explanation: The argument to an .ASCix directive did not have
enclosing delimiters or an expression was not enclosed in angle
brackets.
User Action:

Correct the syntax of the argument.

ILLBLKNUM, illegal logical block number
Facility:

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.

Submit an SPR.

ILLBLKSIZE, internal CRF error -- illegal deallocate block size
Facility:

CREF

Explanation:

Cross reference has detected an internal error.

User Action:
an SPR.

Collect as much information as possible and

submit

MESSAGES

ILLBRDEST, illegal branch destination
Facility:

VAX-11 MACRO assembler

Explanation: The destination of a branch instruction was not
address, for example, BRB 10(R9).

User Action: Change the destination of the hranch instruction or
use a jump (JMP) instruction.

ILLBYTCOU, illegal byte count for I/O
Facility:

BASIC (run-time)

Explanation: A PRINT or INPUT list invoked
closed an I/O channel. This is a fatal error.
User Action:
I/O channel.

function

Change the function so that it does not

that

the

that

was

ILLCHR, illegal character
Facility:

VAX-11 MACRO assembler

Explanation: The source line
illegal in its context.
User Action:

contained

character

Delete the illegal character.

ILLCNTRFUNC, illegal ACP control function
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
The control
returned from a file system ACP QIO request.
function specified in an IO$ ACPCONTROL QIO request is not a
valid function.
User Action: Check for a programming error. See the VAX/VMS I/O
User's
Guide
for
the correct function codes and coding
specifications.
If the error is associated with a DECnet
operation, see the DECnet-VAX System Manager's Guide.

ILLCREOPT, illegal create options
Facility:

Librarian

Explanation: This error message is generated by the Librarian
routines.
The create options you specified for LBR$0PEN are
illegal, or no options were specified.
User Action:
routine.

Correct

the

create

2-97

options

before

calling

the

MESSAGES
ILLCTL, illegal control index
Facility:

Librarian

Explanation: This error message is generated hy the Librarian
routines.
Either the library is not open, or you have specifie<l
an illegal library index.
User Action: Determine that the library is open and the
index is correct.

library

ILLDEVNAM, illegal device name
Facility:

Job controller

Explanation: A device name specified
request has more than 15 characters.

symbiont

manager

User Action: Check for a programming error.
Verify that the
call to the service was coded correctly. See the VAX/VMS Syste~
Services Reference Manual for coding specifications.
ILLDEVTYP, illegal device type for queue
Facility:

Job controller

Explanation: The device type specified in a request to start a
job queue is not a device to which jobs can be queued, for
example, a card reader. This message is associated with a status
code returned by the job controller. The operating system does
not normally display this message.
User Action: Check for a programming error.
Verify that the
call to the service was coded correctly. See the VAX/VMS System
Services Reference Manual for coding specifications.
ILLDFLTARG, illegal argument for .DEFAULT directive
Facility:

VAX-11 MACRO assembler

Explanation: A .DEFAULT directive did not specify DISPLACEMENT
or the displacement specified was not BYTE, WORD, or LONGWORD.
User Action:

Correct the .DEFAULT directive.

ILLEFC, illegal event flag cluster
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a system service request. 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.

2-98

MESSAGES
ILLEGOPT, option supported by another program
Facility:

BTRAN

Explanation: The image invoked by a DCL command can invoke
different images based on the qualifiers specified. This error
occurs when a command was entered with a qualifier that is legal
only when other qualifiers are entered.
For example, the
/OWNER UIC qualifier for the CREATE command applies only to the
creation of a directory;
if you specify this qualifier when you
create a file, this message is issued.
User Action: Use the HELP command or refer to the VAX/VMS
Command Language User's Guide,
if necessary, to determine the
qual1f1ers that are related and reenter the command.
ILLEXIDEF, illegal exit from DEF*
Facility:

BASIC (run-time)

Explanation: A multi-line DEF* contains a branch to an
SUBEND or FUNCTIONEND statement. This is a fatal error.

END,

User Action: Change the program logic so that the program
executes the multi-line DEF's FNEND statement before executinq
the END, SUBEND or FUNCTIONEND statement.
ILLEXPR, illegal expression
Facility:

VAX-11 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.

ILLFIEVAR, illegal FIELD variable
Facility:

BASIC (run-time)

Explanation: A FIELD statement contains a variable that is also
named in a COMMON, MAP, SUB, FUNCTION, CALL, or MOVE statement.
This is a fatal error.
User Action: Remove the variable from the FIELD statement,
from the COMMON, MAP, SUB, FUNCTION, CALL, or MOVE statement.

2-99

MESSAGES
ILLFILNAM, illegal file name
Facility:

Job controller

Explanation: The file name specified in a symbiont manager
request
has
more than nine characters.
This message is
associated with a status code returned by the job controller.
The operating system does not normally display this message.
User Action: Check for a programming error.
Verify that the
call to the service was coded correctly. See the VAX/VMS Syste~
Services Reference Manual for coding specifications.
ILLFILNAM, illegal file name
Facility:

BASIC (run-time)

Explanation: A file name is:
(1)
too long,
(2)
incorrectly
formatted, or (3) contains embedded blanks or invalid characters.
This is a fatal error.
User Action:

Supply a valid file specification.

ILLFMT, illegal library format
Facility:

Librarian

Explanation: This error message is generated by the Librarian
routines.
The file you specified calling LBR$0PEN is not an
actual library.
User Action:

Specify the actual library.

ILLFUNC, illegal library function
Facility:

Librarian

Explanation: This error message is generated by the Librarian
routines.
The library function you specified in LBR$0PEN is
i llega 1.
User Action:
routine.

Correct the library

function

before

calling

the

ILL_FUNC, invalid function or option
Facility:

NIC

Explanation:

Function not supported by target node.

User Action:

None.

ILLIDXNUM, illegal index number
Facility:

Librarian

Explanation: This error message is generated by the
routines. The index number you specified is illegal.
User Action:
routine.

Correct

the

index
2-100

number

before

Librarian

calling

the

MESSAGES
ILLIFCOND, illegal IF condition
Facility:

VAX-11 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:
directive.

Correct the

syntax

the

conditional

assembly

ILLILLACC, illegal or illogical access
Facility:

BASIC (run-time)

Explanation:

The requested access is not possible because:

•

The attempted record operation and the ACCESS
OPEN statement are incompatible.

clause

the

•

The ACCESS clause is inconsistent with the file organization.

•

ACCESS READ or APPEND was specified when the file was created.

This is a fatal error.
User Action:

Change the ACCESS clause.

ILLINDXREG, invalid index register
Facility:

VAX-11 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.

ILLINST, compatibility mode illegal instruction
Facility:

RSX

Explanation: An RSX-llM image attempted to execute either a JMP
or JSR instruction with a register destination. The PC contains
the address of the instruction that caused the error.
In
RSX-llM, the PC contains the address following the erroneous
instruction. This message corresponds to the RSX-llM termination
message ILLEGAL INSTRUCTION.
User Action: Determine the instruction or statement at which the
error occurred and correct the error.
ILLIOFUNC, illegal I/O function code
Facility:

VAX/VMS System Services

Explanation: This message is associated
returned from a system service request.
explicit input/output request was invalid.

2-101

with a status code
A function code in an
Or,
if the errors

MESSAGES
occurred
during a DECnet operation, the user
synchronous disconnect with outstanding transmits.
User Action: Check for a programming error.
function code and correct it.

attempted

Locate the

invalid

ILLIO_CHA, illegal I/O channel
Facility:

BASIC (run-time)

Explanation:
legal range.

The program specified an I/O
This is a fatal error.

channel

User Action:
inclusive.

Specify

the

I/O

channels

outside

the

99,

characteristics

range

ILLKEYATT, illegal key attributes
Facility:

BASIC (run-time)

Explanation: An invalid combination of
specified, either:

key

NODUPLICATES and CHANGES, or
CHANGES, without DUPLICATES
This is a fatal error.
User Action:

Change the invalid key characteristics.

ILLKEYLVL, illegal key ·level
'number'
file-spec' expected 'key number'
Facility:

key

'keyname'

'library

LIBRARY

Explanation: This error message is generated by the LIBRARY
command.
The help module you want to insert into the library is
formatted incorrectly.
User Action:
library.

Reformat the module before inserting

into

the

contained

ILLMACARGN, illegal MACRO argument name
Facility:

VAX-11 MACRO assembler

Explanation: The name
illegal character.
User Action:

the

.MACRO

directive

Delete the illegal character.

ILLMACNAM, illegal MACRO name
Facility:

VAX-11 MACRO assembler
MACRO

name

was

the

.MACRO

User Action:

Specify the MACRO name in the .MACRO directive.
2-102

specified

Explanation:
directive.

MESSAGES
ILLMASKBIT, reserved bits set in ENTRY mask
Facility:

VAX-11 MACRO assembler

Explanation: The register save mask in an .ENTRY or .MASK
directive specified RO, Rl, AP, or PC registers (corresponding to
bits O, 1, 12, and 13).
User Action:

Remove these registers from the register save mask.

ILLMODE, illegal mode
Facility:

VAX-11 MACRO assembler

Explanation:
specified.

An invalid addressing mode for the instruction

User Action:

Specify a legal addressing mode.

was

ILLNUM, illegal number
Facility:

BASIC (run-time)

Explanation: A value supplied
incorrect;
for example "ABC"
This is a fatal error.
User Action:

to a
numeric
variable
is
and "1 •• 2" are illegal numbers.

Supply numeric values of the correct form.

ILLOP, illegal operation for access requested
Facility:

Librarian

Explanation: This error message is generated by the Lihrarian
routines.
You have attempted to modify a Version 1.0 library or
a read-only library.
User Action: Compress the library into the current
change the access privileges to the library file.

format,

ILLOPDEF, illegal format for .OPDEF
Facility:

VAX-11 MACRO assembler

Explanation:

The .OPDEF directive had incorrect syntax.

User Action:

Correct the .OPDEF directive syntax.

ILLOPDEFVL, illegal value for opcode definition
Facility:

VAX-11 MACRO assembler

Explanation: The value specified in the .OPDEF directive did not
fit in two bytes.
User Action:

Correct the value in the directive.

2-103

MESSAGES

ILLOPE, illegal operation
Facility:

BASIC (run-time)

Explanation:

The program attempted one of the following:

•

Perform a DELETE operation on a record in a sequential file.

•

Perform an UPDATE operation on a record on a magtape file.

•

Transpose a matrix, or perform a matrix multiplication,
the same array as source and destination.

•

Rewind a process-permanent file.

•

Perform a DELETE operation on a record in a read-only file.

•

Assign a value to a virtual array element in a read-only file.

•

Perform a MARGIN operation on a virtual file.

•

Perform an invalid operation on a virtual file,
f~r
example,
using GET and PUT on a virtual file, then attemptinq to
reference a virtual array dimensioned on that file.

with

This is a fatal error.
User Action:

Change the illegal operation.

ILLOPT, qualifier(s) not appropriate to this device
Facility:

MOUNT and INITIALIZE

Explanation: A MOUNT or INITIALIZE command specified qualifiers
that apply only to disk devices for a tape device, or qualifiers
that apply only to tape devices for a disk device.
User Action: Use the HELP command or i:ef er to the VAX/VMS
Command Language User's Guide for a list of qualifiers, if
necessary' and ·--ree-n-te_r_____the_command
the
appropriate
with
qualifier(s).

ILLPAGCNT, illegal page count parameter
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a system service request. The number of pages
specified for an expand or delete region request was less than 1.
User Action: Check for a programming error;
of pages specified for the service call.

verify

the

number

ILLQUAL, invalid qualifier
Facility:

MOUNT

Explanation:

An invalid qualifier was given in the command.

User Action:

Check the command and reenter it.

2-104

MESSAGES
ILLQUENAM, illegal queue name
Facility:

Job controller

Explanation: The queue name specified in a symbiont manager
request has more than 15 characters. This message is associated
with a status code returned by the job controller. The operating
sy$tem does not normally display this message.
This message is also issued by the job controll~r if the queue
name specified in a SYNCHRONIZE command is not a batch queue.
User Action: Check for a programming error.
Verify that the
call to the service was coded correctly. Verify that the queue
name is the name of the batch queue and reissue the command. See
the
VAX/VMS
System
Services Reference Manual for coding
specifications.
ILLRECACC, illogical record accessing
Facility:

BASIC (run-time)

Explanation: The program attempted to perform an operation that
is invalid for the specified file type, for example, a random
access on a sequential file. This is a fatal error.
User Action: Supply a valid operation
change the file type.

for

that

file

type

invalid

byte

count

ILLRECFIL, illegal record on file
Facility:

BASIC (run-time)

Explanation: A record contains
This is a fatal error.

User Action: Use the DCL DUMP command
possible bad data.

field.

check

the

file

for

here,

for

example,

ILLREGHERE, this register may not he used here
Facility:

VAX-11 MACRO assembler

Explanation:
PUSHL (PC).

This register cannot he

User Action:

Use another register.

used

ILLREGNUM, illegal register number
Facility:

VAX-11 MACRO assembler

Explanation: A register name was not in the range RO through Rl2
or was not the AP, FP, SP, OR PC register name.
User Action:

Correct the illegal register name.

2-105

MESSAGES

ILLRESSUB, illegal RESUME to subroutine
Facility:

BASIC (run-time)

Explanation: While in an error handler activated by an ON ERROR
GO BACK, the error handler attempted to RESUME without a line
number. This is a fatal error.
User Action: None; you cannot RESUME to a line in
module except the one containing the error handler.

any

program

ILLRQST, illegal operator request
Facility:

OPCOM

Explanation: A REPLY command was issued with no qualifiers.
a REQUEST command specified a bad value.
User Action:

Or,

Verify the command line and reenter the command.

ILLSEQOP, illegal sequential operation
Facility:

VAX/VMS System Services

Explanation: When a sequential access device is used, such as a
magnetic tape, certain operations can only be performed 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:
problem.

Examine the source program to determine

the

loqic

ILLSER, illegal service call number
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a system service request. An image specified a
call to a procedure whose name is entered in the system service
vector table, but which is not a valid service.
User Action: Check for a programming error.
call and correct it.

Locate the

illegal

ILLSTRCLA, illegal string class
Facility:

STRING (Run-Time)

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, Appendix C in
the VAX-11 Architecture Handbook.
User Action: If 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 the user is creating desriptors, check
that all string descriptors are initialized before using them.

2-106

MESSAGES

ILLSTROPS, illegal string position
Facility:

STRING {run-time)

Explanation:
Successful completion except that one of the
character-position parameters to a string routine pointed to a
character-position before the beginning of the input string
(was
less than 1 but 1 was used) or after the end of the input strinq
{was greater than the length of the input sring but the length of
the input string was used).
User Action: The user should make sure that any parameter that
is a character-position is greater than 0 and less than or equal
to the length of the input string.

ILLSTRSPE, illegal string specification
Facility:

STRING {run-time)

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 character-position. A null string was
used for the substring.
User Action:
The user program
character-positions
are
less
character-position.

should verify that starting
or
equal
to ending
than

ILLSWIUSA, illegal switch usage
Facility:

BASIC {run-time)

Explanation: The program attempted an illegal SYS call.
a fatal error.
User Action:

This is

See the appropriate RSTS/E SYS call documentation.

ILLSYMLEN, symbol exceeds 31 characters
Facility:

VAX-11 MACRO assembler

Explanation: The symbol name was longer than 31 characters.
assembler truncated the name to 31 characters.
User Action:
characters.

Specify a symbol name that

has

than

The
31

ILLSYSUSA, illegal SYS{O) usage,
Facility:

BASIC (run-time)

Explanation: The program attempted an illegal SYS call.
a fatal error.
User Action:

This is

See the appropriate RSTS/E SYS call documentation.

2-107

MESSAGES
ILLTYP, illegal library type
Facility:

Librarian

Explanation: This error messaqe is generated by the Librarian
routines.
The type of library specified in LBR$INI CONTROL is
illegal.
User Action:
routine.

Correct

the

library

type

before

calling

the

ILLUSADEV, illeqal usage for device
Facility:

BASIC (run-time)

Explanation: The requested operation cannot be performed for one
of the following reasons:
•

The device specification contains illegal syntax.

•

The ~pecified device does not exist on your system.

•

The specified device is inappropriate for the requested
operation (for example, an indexed file access on magtape).

This is a fatal error.
User Action:

Supply the correct device type.

ILLVAL, illegal value is present
Facility:

VAX/VMS Command Language Interpreter

Explanation: A qualifier or parameter value is
legal range of values.

not

within

the

User Action: Use the HELP command or ref er to the VAX/VMS
Command Language User's Guide, if necessary, for the legal values
and reenter the command.
IMAGETERM,

'image name' terminated,

Facility:

'system date and time'

RSX

Explanation:
abnormally.

The

User Action:

None.

compatibility

mode

image

has

terminated

IMASQUROO, imaginary square roots
Facility:

BASIC (run-time)

Explanation: An argument to the SQR function is negative.
is a fatal error.

This

User Action: Supply arguments
greater than or equal to zero.

are

2-108

the

SOR

function

that

MESSAGES
IMCHNG, two images requested in one command
Facility:

VAX/VMS Command Language Interpreter

Explanation: A command that can potentially request different
operating
system
functions
was specified with qualifiers
requesting that two different images be executed.
User Action: Use the HELP command or refer to the VAX/VMS
Command Language User's Guide to verify the qualifiers and/or
functions requested and reenter the command.
IMGFNF, image file not found
Facility:

CL! and BTRAN

Explanation: An attempt to execute an image failed
image file could not be found.
User Action:
does exist.

Use the DIRECTORY command to check

because

that

the

the
file

IMX, invalid duplicate XAB or non-dense XAB at location
Facility:

VAX-11 RMS

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-11 RMS service was coded correctly.
INCFILORG, inconsistent file organization
Facility:

FORTRAN (run-time)

-Explanation:

One of the following conditions occurred:

•

The file organization specified in an OPEN statement
match the organization of the existing file.

did

not

•

The file organization of the existing file was inconsistent
with the specified access mode;
that is, direct access was
specified with an indexed organization file or keyed access
was specified with a sequential or relative organization file.

User Action: Verify that the file referred to in the OPEN
statement has the correct organization, change the ORGANIZATION
keyword specification in the OPEN statement to match the file, or
resolve the inconsistency between the file organization and the
access type specified.

2-109

MESSAGES

INCKEYCHG, inconsistent key change or duplicate key
Facility:

FORTRAN (run-time)

Explanation: A WRITE or REWRITE to an indexed organization file
caused a key field to change or be duplicated. This condition
was not specified in the attributes of the file, established when
the file was created.
User Action: Verify that the key being changed is the one
desired.
Or, correct the program to include an ERR= or IOSTAT=
specifier to detect and respond to a key change or duplication
condition.

INCOMPACP, indicated ACP is incompatible with 'volume'
Facility:

MOUNT

Explanation:
device.

The ACP specified is not an ACP for

User Action: Reenter the command;
specify
appropriate for the particular device type.

INCOMPAT,
input-file
(input)
incompatible attributes
Facility:

and

output-file

the

requested

ACP

that

(output)

have

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 SORT/RSX
command. The command continues execution.
User Action: Determine whether the incompatibility presents a
problem and, if so, delete the output file(s), modify the format
of one or more input files, and reenter the command.

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, qualifiers incompatible with already mounted volume
Facility:

MOUNT

Explanation: A MOUNT command 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 SHOW DEV to determine how the volume
mounted. Reenter the MOUNT/SHARE command without qualifiers.

2-110

MESSAGES
INCONSDEV, inconsistent device types
Facility:

MOUNT

Explanation: Both disks and tapes appear in the list of
to be mounted.

devices

User Action: Specify one or the other and reenter
check the logical name assignments.

command;

the

INCOPECLO, inconsistent OPEN/CLOSE parameters
Facility:

FORTRAN (run-time)

Explanation: Specifications in an OPEN or CLOSE statement
inconsistent. Some of the invalid combinations are:
•

READONLY with STATUS='NEW', or STATUS='SCRATCH'.

ACCESS='APPEND'
STATUS='SCRATCH'.

DISPOSE='SAVE', DISPOSE='PRINT',
STATUS='SCRATCH'.

•

DISPOSE='DELETE' with READONLY.

User Action:
file.

with

READONLY,
or

were

STATUS='NEW',

DISPOSE='SUBMIT'

with

Correct either the OPEN or CLOSE statement for

the

INCRECLEN, inconsistent record length
Facility:

FORTRAN (run-time)

Explanation:

One of the following conditions occurred:

•

An attempt was made to create a new relative,
indexed,
direct access file without specifying a record length.

•

An existing file was opened in which the record length did not
match the record size given in an OPEN or DEFINE FILE
statement.

User Action: Locate the statement in your program that caused
the error and check the record size specification. Remember that
formatted records are specified in units of bytes and unformatted
records are specified in units of longwords.
INCRECTYP, inconsistent record type
Factility:

FORTRAN (run-time)

Explanation: The RECORDTYPE value in an OPEN statement did not
match the record type attribute of the existing file which was
opened.
User Action: Verify that the RECORDTYPE=
OPEN statement is correct.

2-111

specification

the

MESSAGES
INCVOLLABEL, incorrect volume label
Facility:

VAX/VMS System Services

Explanation:
volume.

_The label specified does not match the label on the

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:

INITIALIZE

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 INITIALIZE command cannot write the index file.
User Action: Reenter the command; specify a position for
index file that is within the range of blocks on the volume.

the

INDEXERR, index error in 'library file-spec'
Facility:

LIBRARY

Explanation: This error message is generated by the LIBRARY
command.
An error occurred while searchinq or traversing the
index; a VAX-11 RMS error occurred;
or there is not enough
virtual memory available.
User Action:
string.

Compress the library before reentering the

command

INDNOTFUL, index not fully optimized
Facility:

BASIC (run-time)

Explanation: A record was successfully written to an INDEXED
file;
however, the alternate key path was not optimized. This
slows record access. This is a warning message.
User Action:

Delete the record and rewrite it.

INFFORLOO, infinite format loop
Facility:

FORTRAN (run-time)

Explanation: The format associated with an I/O statement that
included an I/O list had no field descriptors to use in
transferring those values.
User Action: Locate the statement in your program that caused
the error and check the format associated with the I/O statement.
There must be a format field descriptor that transmits an element
to or from the I/O list.

2-112

MESSAGES
INITERR, error initializing 'library file-spec'
Facility:

LIBRARY

Explanation: This severe error message is generated by the
LIBRARY command. There is insufficient virtual memory available.
User Action:

Increase your working set limit.

INPASGN, error assigning input channel
Facility:

Job controller

Explanation: The input card reader symbiont could not assign a
channel to the card reader to read a user's job. This message
indicates an internal operating system error.
User Action:
an SPR.

Collect as much information as possible and

submit

INPCONERR, input conversion error
Facility:

FORTRAN (run-time)

Explanation: During a formatted input operation an invalid
character was detected in an input field, or the input value
overflowed the range represented in the input variable.
The
value of the variable is set to zero.
User Action: Check that the format associated with the I/O
statement is correct and verify the field width of each field
specified against the data record being read.
INPREAD, error reading input
Facility:

Job controller

Explanation: Input records in a card
cannot be read.

reader

batch

job

stream

User Action: Verify that no bad cards are in the deck;
this
error is most frequently caused by torn or folded cards. If
necessary, repunch any cards that are in bad condition.
INPRECTOO, input record too long
Facility:

FORTRAN (run-time)

Explanation: A record was read that exceeded the explicit or the
default RECORDSIZE specification specified at OPEN (or default
OPEN).
User Action: Locate the READ or ACCEPT statement in your program
that caused the error and check the associated OPEN statement.
Correct the record size specification in the OPEN statement,
if
necessary.
Remember that the record size specification is in
units of bytes for formatted files and in units of longwords for
unformatted files.

2-113

MESSAGES

INPSTAREQ, input statement requires too much data
Facility:

FORTRAN (run-time)

Explanation: An unformatted READ statement attempted
more data than existed in the record being read.

read

User Action: Locate the READ statement in your program that
caused the error, and check the number of elements specified.
Check that the data type of each element is properly declared;
an omitted declaration results in four bytes of data input by
default.

INPSTRTRU, input string truncated
Facility:

VAX-11 Run-Time Procedure Library

Explanation: An input string accepted by LIBSGET 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.

INSERTED, module 'module name' inserted in 'library file-spec'
Facility:

LIBRARY

Explanation:
command.

This success message is generated

User Action:

None.

the

LIBRARY

This message is informational.

INSERTERR, error inserting 'module name' in 'library file-spec'
Facility:

LIBRARY

Explanation: This error message is generated by the LIBRARY
command.
One of the following conditions prevented the LIBRARY
command from inserting the specified modules into the library:

•

The modules are not formatted correctly.

•

The organization of the input file is incorrect.

•

A VAX-11 RMS error occurred.

•

There was not enough virtual memory.

User Action:

Correct the error and insert the file.

INSFARG, insufficient call arguments
Facility:

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.
See the VAX/VMS
System Services Reference Manual for coding specifications.
2-114

MESSAGES
INSFBUFDP, unable to allocate a buffered datapath
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a request to an LPAll-K interface device. A
USA-buffered datapath was not available for allocation.
User Action:

Rerun the program.

INSFDYNMEM, insufficient virtual address space
Facility:

RSX

Explanation: VAX/VMS required more virtual address space to
emulate a requested RSX-llM service than a process is allowed.
User Action: Check for a programming error.
in a loop. Correct the source program.

The image is likely

INSFMAPREG, insufficient map registers
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned
from
a request to an LPAll-K interface device.
Insufficient UBA map registers are available to map the command
table or buffer areas.
User Action: If the map registers were preallocated
drive was loaded, increase the preallocation.

when

the

INSFMEM, insufficient dynamic memory
Facility:

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.
INSFPRM, insufficient parameters
Facility:

VAX/VMS Command Language Interpreter

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.

2-115

MESSAGES
INSFRAME, insufficient call frames to unwind
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a system service request.
An unwind request
specified a depth that is greater than the number of call frames
on the stack. No unwind occurs.
User Action:

Check for a programming error.

INSFSPTS, insufficient SPTs to map process buffer to system
Facility:

VAX/VMS System Services

Explanation: This severe error message is associated with a
status code returned from a system service request. There are
insufficient system page table entries to map a process buffer to
the system.
User Action:

Reboot and increase the SYSGEN parameter SPT.

INSFWSL, insufficient working set limit
Facility:

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 SET WORKING SET
command and retry the program.
INSVIRMEM, insufficient virtual memory
(See also the following messages)
Facility:

VAX-11 MACRO assembler

Explanation: The module beinq 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.

2-11n

MESSAGES
INSVIRMEM, insufficient virtual memory
Facility:

FORTRAN (run-time)

Explanation: The FORTRAN Run-Time Library attempted to exceed
its virtual page limit while dynamically allocating space.
User Action: Determine the current working set limit by using
the SHOW WORKING SET command.
Then, increase the size of the
working set limit and rerun your program.
INSVIRMEM, insufficient virtual memory
Facility:

STRING (run-time)

Explanation: An attempt was made to allocate heap storage
use as dynamic strings or string temporaries failed.

for

User Action: The user who allocates space by calling STR$GET1 DX
or LIB$GET VM should verify that when finished using the storaqe,
it is released by
calling
STR$FREE1 DX
or
LIB$FREE VM,
respectively.
The high level language user who has not directly
allocated space can cause this error hy having a large number of
long strings.
In this case, make sure to reduce strings to 0
length when they are not in use.
INTDATCOR, internal data corrupted in run-time library
Facility:

OTS

Explanation: On a call to the Run-Time Library, a database
consistency check failed.
A user program can cause this hy
referring to a location outside of a dimensioned array, or by
requesting input from an address outside of the program.
User Action: Recompile any module that you think may refer
outside of a dimensioned array with the /CHECK=BOUNDS qualifier.
Relink and rerun your program.
INTDIV, arithmetic
PSL=xxxxxxxx
Facility:

trap,

integer

divide

zero

PC=xxxxxxxx,

VAX/VMS System Services

Explanation: An arithmetic exception condition
result of an attempt to divide by zero.

occurre0

User Action: Examine the PC location displayed in
and check the program listing to verify that
variables are specified correctly.

the message
operands or

INTDIVZER, intermediate divide by zero
Facility:

COBOL (run-time)

Explanation: An attempt was made to divide hy COBOL Intermediate
Temporary which has a value of zero.
User Action: The user should examine the
in which a division operation occurs
divisor has a zero value.
2-117

referenced expression
and determine why the

MESSAGES

INTERLOCK, unable to acquire system data structure interlock
Facility:

VAX/VMS System Services

Explanation: This severe error message is associated with a
status code returned from a system service request. The system
data structure interlock cannot be acquired.
Another processor
has probably crashed while holding a data structure lock.
User Action:
reinitialize
Guide.

the system and
System Manager's

Retry the operation, or reboot
Ref er to the VAX/VMS
memory.

INTERR, integer error
Facility:

BASIC (run-time)

Explanation: The program contains an integer
value is greater than 32767 in WORD mode,
2147483647 in LONG mode. This is a fatal error.
User Action:

whose absolute
or greater than

Use only integers in the valid range.

INTEXPOVE, intermediate exponent overflow
Facility:

COBOL (Run-time)

Explanation: A COBOL Intermediate Temporary is created which has
an exponent that is greater than +99.
User Action: The user should examine the referenced line of the
source program containing an arithmetic operation and determine
what is causing a COBOL Intermediate Temproary to be created with
too large an exponent.

INTEXPUND, intermediate exponent underflow
Facility:

COBOL (run-time)

Explanation: A COBOL Intermediate Temporary is created which has
an exponent that is less than -99.
User Action: The user should examine the referenced line of the
source program containing an arithmetic operation and determine
what is causing a COBOL Intermediate Temporary to be created with
too small an exponent.

INTFAIL, internal consistency check
Facility:

BTRAN

Explanation:
error.

A command failed because of

User Action:
an SPR.

Collect as much information as possible and

2-118

internal

software
submit

MESSAGES
INTLOGERR, internal logic error
Facility:

VAX-11 Run-Time Procedure Library

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:
an SPR.

Collect as much information as possible and

submit

INTOVF, arithmetic trap, integer overflow at PC=xxxxxxxx, PSL=xxxxxxxx
Facility:

VAX/VMS System Services

Explanation: An exception condition occurred as a result
integer overflow.
User Action: Examine the PC location displayed in
and check the program listing to verify that
variables are specified correctly.

the message
operands or

INTRESOPE, intermediate reserved operand
Facility:

COBOL (run-time)

Explanation:
A reference to a
previously
created
COBOL
Intermediate Temporary whose exponent is greater than +99 or less
than -99 has been encountered.
User Action: The user should examine the referenced line of the
source program containing an arithmetic operation and determine
what is causing a COBOL Intermediate Temporary to be created with
too large or too small an exponent in a previously executed
statement.
INVALIGN, invalid alignment
Facility:

VAX-11 MACRO assembler

Explanation:
directive.

integer

User Action:

Correct the syntax of the .ALIGN directive.

keyword

followed

the

.ALIGN

INVALKEYW, keyword not recognized
Facility:

BTRAN

Explanation: A keyword specified as a qualifier value is not
valid;
or a numeric value was specified where a keyword was
required.
User Action: Use the HELP command or ref er to the VAX/VMS
Command Language User's Guide,
if necessary, for the legal
keywords and reenter the command.

2-119

MESSAGES
INVARG, invalid argument
Facility:

COBOL (run-time)

Explanation:
Internal consistency checking has detected an
invalid argument being passed to a routine in the COBOL Run-Time
Library.
User Action:
The user
appropriate
supporting
traceback listing.

is advised to submit an SPR with
including the system
documentation

INVARG, invalid argument(s)
Facility:

VAX-11 Run-Time Procedure Library

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
Library and correct the progrnm.

the

Run-Time

INVARGFOR, invalid argument to FORTRAN Run-Time Library
Facility:

FORTRAN (run-time)

Explanation:

One of the following conditions occurred:
a

PDP-11

FORTRAN

•

An invalid argument was
given
to
compatibility subroutine such as ERRSET.

•

The FORTRAN compiler passed an invalid coded argument to the
Run-Time Library.
This can occur if the compiler is newer
than the Run-Time Library in use.

User Action: Locate the call to the library in your program. If
the procedure is a compatibility procedure, see the VAX-11
FORTRAN User's Guide.
Otherwise, verify the version of the
compiler with the version of the library and recompile or relink
your program, as necessary.
INVARGMAT, invalid argument to math library user PC location
Facility:

Math Library

Explanation: One of the mathematics procedures was
an invalid argument.

called

User Action: Locate the mathematics procedure call that
the error and correct the argument.
INVCOD, invalid line device code received
Facility:

NCP

Explanation:

NICE protocol incompatibility.

User Action:

None.

2-120

with

caused

MESSAGES
INVDBK, improper dialogue message received
Facility:

NCP

Explanation:

NICE protocol incompatibility.

User Action:

None.

INVDSTREC, unimplemented delta-PC command in symbol table
Facility:

TRACE

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:
an SPR.

Collect as much information as possible and

submit

INVDECDAT, invalid decimal data
Facility:

COBOL (run-time)

Explanation: Invalid decimal data has been encountered in the
course of converting a numeric DISPLAY data item into a packed
number. One or more of the following problems may exist:
1.

The length of the source string is outside of the
0 through 31.

The length of the destination packed decimal
outside of the range 0 through 31.

string

The source string contains an invalid byte.
byte is:

range
is

invalid

Any character other than ASCII "O" through "9" in a
digit byte or an ASCII "+", "<space>", or "-" in
the sign byte of a leading separate nuMeric data
item.

Any character other than ASCII "O" through "9" in
any high order byte
(i.e., any byte except the
least significant byte) in a trailing numeric data
item.

In the case of a trailing numeric input, the translation
of the least significant digit produces an invalid
decimal digit or sign nibble.

User Action:
This error most commonly occurs when
space
characters are used in lieu of insignificant, leading, zero digit
positions for numeric fields. These fields are commonly found
within records on a file. The user should examine such numeric
fields on the file and replace all insignificant leading spaces
in these fields with numeric zero characters. Alternatively,
before referencing these fields in arithmetic operations the user
can use the INSPECT statement to change insignificant space
characters to zeroes in these fields.
Another alternative is the

2-121

MESSAGES

NUMERIC class test to determine if numeric data-items contain
only numeric characters. This class test should be executed
before these numeric data-items are referenced in arithmetic
operations.
INVDECDIG, invalid decimal digit
Facility:

COBOL (run-time)

Explanation: An invalid decimal digit has been encountered
the course of converting a packed decimal number.

User Action: The user should examine the logic of the program to
determine why illegal data is being discovered in converting the
packed decimal number.

INVERRCOD, invalid error code
Facility:

NIC

Explanation:

NICE protocol incompatibility.

User Action:

None.

INV FILE, invalid file
Facility:

NIC

Explanation: This message originates
non-VMS node.
User Action:

NICE

object

options

Consult the remote node's documentation.

INVFILOPT, invalid file options
Facility:

BASIC (run-time)

Explanation: The program has specified invalid file
the OPEN statement. This is a fatal error.
User Action:

Change the invalid file options.

INVKEY, invalid key
Facility:

Librarian

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
library's name length limit.

the

2-122

module

name,

change

the

MESSAGES

INVKEY, invalid keyword
Facility:

VAX/VMS Command Language Interpreter

Explanation: An unknown keyword was specified
value or parameter.

for

qualifier

User Action: Use the HELP command or ref er to the VAX/VMS
Command Language User's Guide,
if necessary, for the legal
keywords and reenter the command.

INVKEYREF, invalid key of reference
Facility:

BASIC (run-time)

Explanation: The program attempted to perform a GET, FIND, or
RESTORE on an INDEXED file using an invalid KEY, for example, an
alternate KEY that has not been defined. This is a fatal error.
User Action:
statement.

Use a valid

KEY

the

GET,

FIND,

RESTORE

INVKEYSPE, invalid key specification
Facility:

FORTRAN (run-time)

Explanation: A key specification in an OPEN statement or in a
keyed access READ statement was invalid. For example, the key
length may have been zero or greater than 255 bytes or the key
length may not have conformed to the key specification of the
existing file.
User Action: Verify that the key specification is valid and that
it matches the existing file, if any.

INVLID, improper line-id received from nice object
Facility:

NCP

Explanation:

Incompatible NICE object at target.

User Action:

None.

INVLINVAL, invalid LINAGE value on file
Facility:

COBOL (run-time)

Explanation: An invalid value has been encountered in one of the
data names associated with the LINAGE clause for this file.
User Action: The user should examine the logic of the program to
determine why a data name value associated with the LINAGE clause
does not fall within the range of values as prescribed in the
COBOL rules for the LINAGE clause.

2-123

MESSAGES

INVLOGIN, login information invalid at remote node
Facility:

VAX/VMS System Services

Explanation: This severe error message is associated with a
status code returned from a system service request. 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 data base needs to he 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.
Refer to the DECnet-VAX User's Guide for additional information.
INVLOGUNI, invalid logical unit number
Facility:

FORTRAN (run-time)

Explanation: A logical unit number greater than 99 or less than
0 was used in an I/O statement. The logical unit number which
was in error is displayed in the message.
User Action: Verify that the variable containing the
unit number in an I/O statement has been set properly.

logical

INVMSG, invalid message code received
Facility:

Job controller

Explanation: The message code specified in a job controller
message is not a valid request code. This message is associated
with a status code returned by the job controller. The operating
system does not normally display this message.
User Action: Check for a programming error.
Verify that the
call to the service was coded correctly. See the VAX/VMS System
Services Reference Manual for coding specifications.

INVMSGFMT, invalid message format
Facility:

NIC

Explanation:

Incompatible NICE object at target.

User Action:

None.

INVNAM, invalid NAM block
Facility:

Librarian

Explanation: This error message is generated by the Librarian
routines. The NAM block passed LBR$INI_CONTROLL is illegal.
User Action:

Correct NAM block before calling the routine.

2-124

MESSAGES
INVNODNAM, invalid node identification
Facility:

NIC

Explanation: The specified node
name
either
exceeded
characters or contained a non-alphanumeric character.
User Action:

Correct the node name specification.

INVOPTION, non-supported flow control parameter received
Facility:

DTSEND

Explanation:

DECnet test program protocol incompatibility.

User Action:
equivalent.

Run

with

compatible

DTRECV

version

INVQUAL, invalid qualifier
Facility:

VAX/VMS Command Language Interpreter

Explanation: The image requested qualifier information from a
CL! but the images qualifier list did not contain an entry for
one of the qualifiers typed in the command line.
User Action: Examine the qualifier list in the image
to
determine if the qualifier specified is one that the CL! allows.
INVQUALNUM, invalid qualifier number
Facility:

VAX/VMS Command Language Interpreter

Explanation: This message is associated with an internal status
code returned from the command interpreter result parse routine;
the message indicates an erroneous qualifier.
User Action:
an SPR.

Collect as much information as possible and

submit

INVREQTYP, invalid request type
Facility:

VAX/VMS Command Language Interpreter

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:
an SPR.

Collect as much information as possible and

submit

INVRFA, invalid RFA
Facility:

Librarian

Explanation: This error message is generated
routines. The specified RFA is invalid.
User Action:

the

Librarian

Correct the RFA before calling the routine.

2-125

MESSAGES
INVRFAFIE, invalid RFA field
Facility:

BASIC (run-time)

Explanation: During a FIND or GET by RFA, an invalid record's
file address was contained in the RAB. This is a fatal error.
User Action:

Supply a correct RFA field.

INVRSP, invalid response
Facility:

VAX/VMS Command Language Interpreter

Explanation: An invalid response was entered for a .ASKN or
.ASKS query in an MCR indirect command file.
For .ASKN, the
value entered was not in the acceptable range;
for .ASKS, the
string entered contained too many or too few characters.
User Action: Check the range displayed as part of
and enter a valid response.

the

request,

INVSCT, invalid SCT state
Facility:

Job controller

Explanation: The job controller's symbiont control table is
faulty.
This message indicates an internal error in the job
controller.
User Action:
an SPR.

Collect as much information as possible and

submit

INVSRVNAM, invalid server identification
Facility:

NIC

Explanation: The server node designated
target node is inaccessible.

downline

load

the

User Action: Bring the server node online or modify
configuration database to specify a different server.

the

INVSTA, invalid state received from nice object
Facility:

NCP

Explanation:

NICE protocol incompatibility.

User Action:

None.

INVSTRDES, invalid string descriptor
Facility:

VAX-11 Run-Time Procedure Library and OTS

Explanation: A string descriptor passed to a general
procedure did not contain a valid DSCSB CLASS field.

library

User Action: Locate the call to the library that caused the
error and initialize the field to the proper class of descriptor.
See the VAX-11 Run-Time Library Refer_~~~!:____ Manual
for
a
description of the classes of descriptors.
2-12fi

MESSAGES
INVTYPE, invalid LIB$TPARSE state table entry
Facility:

VAX-11 Run-Time Procedure Library

Explanation: The state table passed to the LIB$TPARSE
was invalid and could not be processed.

procedure

User Action: Correct the format of the state table in your
program.
See the VAX-11 Run-Time Library Reference Manual for
the correct format.
INVUIC, invalid UIC
Facility:

VAX/VMS Command Language Interpreter

Explanation: The command contains an invalid UIC. The group and
member portions of a UIC must both be specified and must be
separated by a comma.
User Action:

Correct the UIC and reenter the command.

IO_CHAALR, I/O channel already open
Facility:

BASIC (run-time)

Explanation: An RSX-llM termination message !OT instruction.
This message corresponds to the RSX-llM termination message !OT
EXECUTION.
User Action:
open.

Remove the OPEN statement:

channel zero is

always

IO_CHANOT, I/O channel not open
Facility:

BASIC (run-time)

Explanation: The program attempted to perform an I/O
before OPENing the channel. This is a fatal error.
User Action:
to it.

operation

OPEN the channel before attempting an I/O operation

IO_CONCLO, I/O continued to closed file
Facility:

OTS

Explanation: An attempt was made to perform I/O to a file
closed. This error can only occur at AST level.
User Action: Correct the program so that AST level
not perform I/O on files which may be closing.
IOERR, ncp/nice io error
Facility:

NCP

Explanation:

A communications error occurred.

User Action:

Check the quality of the line.

2-127

being

routines

MESSAGES

IOERROR, I/O error initializing volume on device-name
Facility:

MOUNT

Explanation: The operator requested a volume initialization.
I/O error occurred during the write process.

User Action: Attempt to perform the operation again.
Use
another volume.
Dump the error log to determine whether a
hardware error occurred.

IOP, operation invalid for file organization or device
Facility:

VAX-11 RMS

Explanation: An invalid VAX-11 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
specified.

not

•

An attempt to perform record I/O when record
not specified.

was

•

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

I/O

access

User Action: Verify that the call to the VAX-11 RMS service was
coded correctly. If necessary, modify your program to detect and
respond to the condition.

IOT, compatibility mode IOT
Facility:

RSX

Explanation: An RSX-llM termination message IOT instruction.
This message corresponds to the RSX-llM termination message IOT
EXECUTION.
User Action: Determine the instruction or statement at which the
error occurred and correct the error.

IRC, illegal record encountered;
Facility:

STV

nnn

VAX-11 RMS

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

2-128

MESSAGES
This error is caused by hardware errors, VAX-11 RMS or system
software errors, or inadvertent modification of files by non-RMS
programs. Collect as much information as possible and submit an
SPR.
!SI, invalid internal stream identifier (ISI) value
Facility:

VAX-11 RMS

Explanation: The internal stream identifier of the RAB does
specify a valid stream.

not

User Action: This error usually indicates that the stream has
not been connected;
or that the RAB has been inadvertently
altered.
IVADDR, invalid media address
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned by I/O functions.
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:
program.

Verify the disk address specified

and

update

the

IVBUFLEN, invalid buffer length
Facility:

VAX/VMS System Services

Explanation:
returned by
device.

This message is associated with a status code
an I/O request. The exact meaning depends on the

If the device is an LPAll-K, the initialize command table
is not the required 278 bytes.

length

If the device is a DR32 interface, the command block size or the
buffer block size is 0 or equal or greater than 2**29, or the
command table length is incorrect.
User Action: Action depends on the type of device to which
I/O request was directed. See the VAX/VMS I/O User's Guide.

the

IVCHAN, invalid I/O channel
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a system service request.
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-129

MESSAGES

IVCHAR, non-numeric character in value string
Facility:

VAX/VMS Command Language Interpreter

Explanation: The command interpreter encountered a character
string in a context where it expected a numeric value -- for
example, on the right-hand side of an arithmetic assignment
statement -- 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 op~rator (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:

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.

IVDEVNAM, invalid device name
Facility:

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.

IVDEVTYPE, invalid device type
Facility:

VAX/VMS Command Language Interpreter

Explanation:
operation.

The specified device is invalid for

User Action:
type.

Reenter the command;

the

requested

specify an appropriate device

IVFNAM, invalid function name
Facility:

VAX/VMS Command Language Interpreter

Explanation: A command contains the character string
'F$name()
where name is not a valid function name and F$name is not a
defined symbol.
User Action: Verify the spelling of the lexical function.
Use
the HELP command or refer to the VAX/VMS Command Language User's
Guide for a list of lexical functions.
2-130

MESSAGES
IVGSDNAM, invalid global section name
Facility:

VAX/VMS System Services

Explanation:

An illegal global section name was specified.

User Action: Refer to the VAX/VMS System
Manual for global section name requirements.

Services

Reference

IVKEYW, unrecognized qualifier keyword
Facility:

VAX/VMS Command Lanquage Interpreter

Explanation: A qualifier or keyword parameter
command is not valid for the command.

specified

User Action: The rejected portion of the command is displayed
between backslashes.
Use the HELP command or ref er to the
VAX/VMS Command Language User's Guide for a list of valid
qualifiers.
IVLOGNAM, invalid logical name
Facility:

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 lenqth
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:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a system service request.
A create or delete
logical name system service request specified a logical name
table number that was not 0 (system), l (group), or 2 (process).
User Action: Check for a programming error.
logical name table number is O, 1, or 2.

Verify

that

the

IVLVEC, section not installed with privilege
Facility:

VAX/VMS System Services

Explanation: This severe error message is associated with a
status code returned from a system service request. A section
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.

2-131

MESSAGES
IVMODE, invalid mode for requested function
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned by an initialize LPAll-K request. The mode word in the
command table is not O.
User Action:

Correct the LPAll-K command table.

IVOPER, unrecognized operator
Facility:

VAX/VMS Command Language Interpreter

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.
list of valid operators.

Type HELP EXPRESSIONS

for

IVPROT, invalid protection code
Facility:

VAX/VMS Command Language Interpreter

Explanation: The protection code specified for a file
is not in the correct syntax.

volume

User Action: Use the HELP command or refer to the VAX/VMS
Command Language User's Guide,
if necessary, for the correct
syntax and reenter the command.
IVPROTECT, invalid page protection code
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a system service request. A page protection code
is specified as 1 or is greater than 15.
User Action:

Check for a programming error.

IVQLOC, invalid qualifier location
Facility:

VAX/VMS Command Language Interpreter

Explanation: A qualifier that can be used only to qualify a file
specification in a command was placed following the command name.
User Action: Reenter the command; place the qualifier following
the specification of the file it actually qualifies. Use the
HELP command or refer to the VAX/VMS Command Language User's
Guide to determine the meaning and placement of the qualifier.

2-132

MESSAGES
IVQUAL, invalid qualifier or privilege name
Facility:

INS

Explanation:

Invalid qualifier or privilege was specified.

User Action:

Reenter the command line.

IVQUOTAL, invalid quota list
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a system service request. 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 coded correctly. See the VAX/VMS System
Services Reference Manual for coding specifications.
IVSECFLG, invalid process/global section flags
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a system service request. Flags specifieo 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:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a system service request. 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:

VAX/VMS System Services

Explanation:

A call was made to a service that does not exist.

User Action:

Check for a programming error.

2-133

MESSAGES

IVSTSFLG, invalid status flag
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a system service request. A reserved bit was set
in a status flag argument to the Create Process ($CREPRC) system
service.
User Action: Verify that the call to the service was coded
correctly.
See the VAX/VMS System Services Reference Manual for
coding specifications.

IVSYMB, symbol must start with alphabetic
Facility:

VAX/VMS Command Language Interpreter

Explanation: An assignment statement specified
that does not begin with an alphabetic letter.

symbol

User Action: Choose a name for the symbol that begins
of the letters A through Z and reenter the command.

name

with

one

IVTIME, invalid time
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a system service request. 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.
call to the service was coded correctly.

Verify

that

the

IVVALU, invalid syntax for value specification
Facility:

VAX/VMS Command Language Interpreter

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 HELP command or refer to the VAX/VMS
Command Language User's Guide to determine the proper syntax or
use 0 f the c omma-na:---·

IVVERB, unrecognized command
Facility:

VAX/VMS Command Language Interpreter

Explanation: The first word on the command is not a valid DCL or
MCR 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 and reenter the command.

2-134

name

symbol

MESSAGES
JOBABORT, job aborted
Facility:

Job controller

Explanation: A batch job was
processed or during processing.
User Action: The message
SYNCHRONIZE command has
that command to fail.

deleted

either

before

was

is informational;
however,
if the
requested this job, this error causes

JOBCRD, job card syntax error 'String'
Facility:

Job controller

Explanation: There is a syntax error in the job card submitted
through the system card reader. The portion of the job card that
was rejected is displayed in the message.
User Action:

Correct the job card and resubmit the job.

KBF, invalid key buffer
Facility:

VAX-11 RMS

Explanation: The specified key buffer is in an
that cannot be read by the caller.

area

memory

User Action: Verify that the call to the VAX-11 RMS service was
coded correctly. Specifically, check that the key buffer address
is correctly specified.
KEY, invalid record number key or key value
Facility:

VAX-11 RMS

Explanation: An invalid key value was specified in
following ways:

one

the

•

A negative or zero record number was specified
operation on a sequential or relative file.

for

random

•

A packed decimal key value specified
contained an invalid nibble.

indexed

value

for

User Action: Note the condition. Modify the source program,
necessary, to detect and respond to the condition.

KEYlSTENTR, first time key entered in table
Facility:

CREF

Explanation:
time.

The key was entered into the table

User Action:

None.

2-135

for

the

first

MESSAGES

KEYFIEBEY, key field beyond end of record
Facility:

BASIC (run-time)

Explanation: The position given for the key field
maximum size of the record. This is a fatal error.
User Action:

exceeds

the

Specify a key field within the record.

KEYLARTHA, key larger than record
Facility:

BASIC (run-time)

Explanation: The key specification exceeds
size. This is a fatal error.
User Action:

the

maximum

record

Reduce the size of the key specification.

KEYNOTCHA, key not changeable
Facility:

BASIC (run-time)

Explanation: An UPDATE statement attempted to change a KEY field
that did not have CHANGES specified in the OPEN statement. This
is a fatal error.
User Action: Remove the changed key field
in the
UPDATE
statement, or specify CHANGES for that key field in the OPEN
statement. Note that the primary key cannot be changed.

KEYNOTFND, key not found
Facility:

Librarian

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:
routine.

Correct the key name argument

before

calling

the

for

key

KEYPRVENTR, key previously entered in table
Facility:

CREF

Explanation: A call to
already in the table.
User Action:

LIB$CRF INS KEY

was

made

None.

KEYSIZTOO, key size too large
Facility:

BASIC (run-time)

Explanation:
The key length on a GET or FIND is either zero or
larger than the key length defined for the target record. This
is a fatal error.
User Action:
statement.

Change the key specification in

2-130

the

GET

FIND

MESSAGES
KEYVALERR, keyword value error in OPEN statement
Facility:

FORTRAN (run-time)

Explanation: An OPEN or CLOSE statement keyword that requires
value had an improper value.

User Action: Locate the OPEN or CLOSE statement that caused the
error and change the value to one within the acceptable limits.
See the VAX-11 FORTRAN Language Reference Manual for
the
allowable values.
KEYVALOVR, too many characters in qualifier keyword value
Facility:

BTRAN

Explanation:
too long.

The value specified for a keyword in a qualifier is

User Action: Use the HELP command or ref er to the VAX/VMS
for the valid
Command Language User's Guioe,
if necessary,
keywords and reenter the command.
KEYWAIEXH, keyhonrd wait exhausted
Facility:

BASIC (run-time)

Explanation: No input was received during the execution of an
INPUT, LINPUT, or INPUT LINE statement that was preceded by a
WAIT statement. This is a fatal error.
User Action:
time.

None;

you must supply input within

the

specified

KFF, known file found
Facility:

VAX-11 RMS

Explanation: A VAX-11 RMS request to search the known file list
completed successfully, and the RMS file open is not required.
User
Action: None.
This
message
DIGITAL-supplied component usage.

provided

for

KFIFULL, no room to add a new known file list
Facility:

INS

Explanation:

All known file list heads are in use.

User Action:

Reboot and use the SYSGEN parameter KFILSTCNT.

KFINOTFND, known file not found
Facility:

INS

Explanation: The file specified is
there is no known file entry for it.

not

installed;

User Action: Reenter
file-specification.

line

giving

the

command
2-137

the

that

is,

correct

MESSAGES
KNM, key name buffer not accessible in XAB at 'location'
Facility:

VAX-11 RMS

Explanation: The key name buffer address in the key definition
XAB at the specified address 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 address of the XAB in error. Verify that the call to the
VAX-11 RMS service was coded correctly;
in particular, that the
buffer is readable for a $CREATE operation, and writeable for a
$DISPLAY or $OPEN operation.
KRF, invalid key-of-reference for $GET/$FIND
Facility:

VAX-11 RMS

Explanation: The key-of-reference value specified in the RAB
greater than the number of keys defined for the file.

User Action: Verify that the call to the VAX-11 RMS service
coded correctly.

was

KSI, index bucket will not hold two keys for key-of-reference
Facility:

nnn

VAX-11 RMS

Explanation: The size of the index buckets specified for the key
must be large enough to hold at least two key values.
User Action:
correctly.

Verify

that

the

VAX-11

RMS

service

was

coded

KSZ, invalid key size for $GET/$FIND
Facility:

VAX-11 RMS

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:
correctly.

Verify

that

the

VAX-11

RMS

service

was

coded

LAN, invalid lowest-level-index area number in XAB at 'location'
Facility:

VAX-11 RMS

Explanation: The lowest-level-index area number specified in the
key definition XAB at the specified address is not a defined area
for the file.
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-11 RMS service was coded correctly.

2-138

MESSAGES

LARGECNT, disk too large to be supported
Facility:

INITIALIZE

Explanation:
this size.

This version of Files-11 does not support a disk of

User Action: Check the device driver to determine if it is
initializing the device database correctly. You may have need
for DIGITAL-supplied custom software.

LCKPAGFUL, no more pages may be locked in memory
Facility:

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.

LENVIO, address space length violation
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a system service request.
A virtual address
specified in a system service call is beyond the end of the
process's program or control region.
User Action: Check for a programming error.
call to the service was coded correctly.

Verify

that

the

LEX, invalid $EXTEND for area nnn containing an unused extent
Facility:

VAX-11 RMS

Explanation: A VAX-11 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-11 RMS
service was coded correctly.

LIBNOTFND, open failure on library/common file,
Facility:

'library-name'

RSX

Explanation: An RSX-llM library or common area requested is
present in SYS$LIBRARY or does not have a file type of EXE.

not

User Action: Depending on the cause of the error, move the
library to the device and directory identified as SYS$LIBRARY,
rename the file type to EXE, or both.

2-139

MESSAGES
LIBNOTOPN, library not open
Facility:

Librarian

Explanation: This error message is generated by the Librarian
routines.
Except for LBR$INI CONTROL and LBR$0PEN, all routines
require that the library be open.
User Action:

Open the library before calling the routine.

LIBOPN, library already open
Facility:

Librarian

Explanation: This warning message is generated by the Librarian
routines. The library you attempted to open is already open.
User Action:

None.

Processing continues.

LIN_COMM, line communications error
Facility:

NIC

Explanation:

Line protocol error.

User Action:
validity.

Check the line

and

all

associated

hardware

too

small

all

for

LINELNG, illegal output line length
Facility:

CREF

Explanation:
fields.

Line width is

hold

requested

User Action:

Increase the line size or decrease field widths.

LINETYP, invalid line type
Facility:

NCP

Explanation:

The line type referred to is not supported.

User Action:

Enter a valid line type.

LIN_PROT, line protocol error
Facility:

NIC

Explanation:

A down-line load device caused an error(s).

User Action:

Check the device for proper functioning.

2-140

MESSAGES
LINTOOLNG, line too long
Facility:

VAX-11 MACRO assembler

Explanation: A source line in a macro definition was longer than
500 characters.
User Action:
shorter.

Restructure the source code so

that

the

line

LINWNGSTA, line in wrong state
Facility:

NIC

Explanation:

SET STATE operation not valid.

User Action:

Perform a valid operation.

LISIOSYN, list-directed I/O syntax error
Facility:

FORTRAN (run-time)

Explanation: The data in a list-directed input record had an
invalid format or the type of constant was incompatible with the
corresponding variable. The value of the variable was unchanged.
User Action: Locate the READ or ACCEPT statement that caused the
error.
Check the data in the record for an invalid format by
printing the file or examining the terminal input.
Also, check
the data type declarations of each variable in the I/O list.
LKPNOTDON, lookup has not been done
Facility:

Librarian

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:

VAX/VMS System

Explanation: This message is associated with a status code
returned from a system service request. 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 SET WORKING SET command 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-141

MESSAGES

LNE, logical name translation count exceeded
Facility:

VAX-11 RMS

Explanation: VAX-11 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 SHOW LOGICAL command to verify the current
result of translation on the specified logical name. Verify that
the call to the VAX-11 RMS servie was coded correctly.

LOADERROR, image load error, image-name
Facility:

RMS

Explanation: An error occurred during an attempt to load the
RSX-llM image into memory. Normally, this error is the result of
a disk failure or a library error. In the case of a library
error, an accompanying message indicates the reason for the
error.
User Action: Check the status of the device and reenter the
command.
Attempt to recreate the image in another file.
If the
failure persists, notify the system manager.

LOADFAIL, DECnet line 'line':
Facility:

downline load failure

DLE

Explanation:

Down-line load failed.

User Action:

Refer to the accompanying message.

LOGCLOS, logfile closed
Facility:

OPCOM

Explanation: This message indicates that OPCOM
operator's log file.
User Action:

has

closed

the

None.

LOGFAIL, failed to initialize logfile
Facility:

OPCOM

Explanation: A REPLY/INIT command failed to create a
new
operator
communication
log
file.
This message generally
indicates a file system failure.
User Action:
failure.

Accompanying messages indicate the reason

2-142

for

the

MESSAGES

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.

Explanation: An invalid character was present on the
or password response to login prompting messages.
User Action:

user

name

Repeat the login procedure.

Explanation: The value specified for a login qualifier was not
in the correct format, no value was specified for the qualifier,
or the qualifier was separated from its value with an invalid
character.
User Action: Verify the command line you entered and repeat
login procedure.

the

Explanation: An invalid character separated
from its associated value.

qualifier

User Action: Verify the command line and repeat the login
procedure. Qualifiers can be separated from values only by equal
signs {=)or colons (:).

Explanation: An internal error occurred in the job
during the login; the login cannot be performed.

controller

User Action: Try to repeat the login procedure. If the failure
persists, notify the system operator or manager of the problem.

Explanation:

Logins are currently disabled.

User Action:
later.

Do not attempt to log in at this time.

2-143

Try

again

MESSAGES
LOGIN - maximum number of users exceeded - try again later
Explanation: The installation-defined maximum
has been reached.

number

users

User Action: Wait and try to log in at a later time, after other
users have logged out.
LOGIN - network user validation error
Facility:

Explanation:

A network login request was not validated.

User Action: This message is written to the system
log file, and is not displayed on the terminal.

accounting

Explanation: The /DELETE qualifier was present and you do not
have the user privilege PRMGBL, that is, the privilege to delete
the command interpreter global section.
This qualifier is
reserved for privileged users who can replace the command
interpreter online.
User Action:
/DELETE.

Repeat

the

procedure;

not

specify

Explanation:

A system error occurred during the login procedure.

User Action:

Submit an SPR.

Explanation: The job controller encountered an error while
attempting to allocate a database for the command interpreter and
cannot perform the login.
User Action: Repeat the login procedure.
notify the system operator or manager.

If the error persists,

Explanation: The system cannot open the current input device and
cannot perform the login. This message is usually accompanied by
a VAX-11 RMS message indicating the reason for the failure.
User Action: Take corrective action based on the VAX-11
message, and repeat the login procedure, if possible.

2-144

RMS

MESSAGES
LOGIN - SYS$0UTPUT open error
Facility:

Explanation: The system cannot open the current output device
and
cannot
perform
the login.
This message is usually
accompanied by a VAX-11 RMS message indicating the reason for the
failure.
User Action: Take corrective action based on the VAX-11
message, and repeat the login procedure, if possible.

RMS

Explanation: The login procedure failed
error.
This
message is accompanied
indicating the reason for the failure.

because of a system
by a system message

User Action: Try to repeat the login procedure.
persists, notify the system operator or manager.

the

error

Explanation:

The login procedure does not recognize a qualifier.

User Action: Verify the spelling of the
the login procedure.

qualifiers

and

repeat

Explanation: You entered either your user name or your
incorrectly, or both.
User Action:

password

Repeat the login procedure.

LOGINIT, logfile initialized
Facility:

OPCOM

Explanation: A REPLY/INIT command successfully initialized a new
operator communication log file.
User Action:

None.

This message is informational.

LOGNAME, logical name is too long
Facility:

MOUNT

Explanation:

A logical name contains more than 63 characters.

User Action: Reenter the command;
has fewer than 63 characters.

2-145

specify a logical

name

that

MESSAGES

LOGTIME, logfile time stamp
Facility:

OPCOM

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.

LOGZERNEG, logarithm of zero or negative value
user PC location
Facility:

Math library

Explanation: The LOG or DLOG mathematics 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.

LOOKUPERR, error looking up 'module name' in 'library file-spec'
Facility:

LIBRARY

Explanation: This error message is generated by the LIBRARY
command.
The Librarian could not find the requested module in
the MNT, a VAX-11 RMS error occurred, or there was not enough
virtual memory available.
User Action:
module name.

Reenter the command

line

specifying

existing

LOSTREC, queue record lost
Facility:

Job controller

Explanation:
controller.

This message indicates an internal error in the job

User Action:
an SPR.

Collect as much information as possible and

submit

MACLBFMTER, macro library format error
Facility:

VAX-11 MACRO assembler

Explanation:

A format error occurred in the MACRO library.

User Action: Retry the assembly and, if the error still occurs,
use the LIBRARY command (see the VAX/VMS Command Language User's
Guide) to re-create the library from the source code.

2-146

MESSAGES

MACNAMLNG, macro 'macro name' name is too long in 'library file-spec'
Facility:

LIBRARY

Explanation: This error message is generated by the LIBRARY
command.
The name of the macro you attempted to insert into the
library exceeds the name-length limit.
User Action: Either rename the macro
name-length limit.

MAPHDRBAD, storage map header is bad;
Facility:

extend

the

library's

volume locked

MOUNT

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:
If possible,
them. Submit an SPR.

remove

the

files

and

reinitialize

MATDIMERR, matrix dimension error
Facility:

BASIC (run-time)

Explanation:

The program attempted one of the following:

•

To assign more than two dimensions to an array

•

To reference a one-dimensional array with two subscripts

•

To reference a two-dimensional array with one subscript

This is a fatal

e~ror.

User Action: Reduce the number of subscripts to one or two,
reference the array using the correct number of di~ensions.

MAXBAD, bad block table overflow
Facility:

INITIALIZE

Explanation: The disk has too many unusable blocks;
the
INITIALIZE command cannot initialize it. 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 and DISMOUNT

Explanation: More than 16 tape devices were specified in a MOUNT
or DISMOUNT command.
User Action: Reenter the MOUNT
fewer than 16 devices.
2-147

DISMOUNT

command;

specify

MESSAGES
MAXLAB, too many volume labels
Facility:

MOUNT

Explanation:
command.

More than 16 tape labels were specified in a

User Action: Reenter the MOUNT command;
volume labels.

specify fewer

MOUNT

than

MAXMEMEXC, maximum memory exceeded
Facility:

BASIC (run-time)

Explanation: The program has insufficient string and I/O buffer
space because the allowable memory size has been exceeded, or the
system's maximum memory capacity has been reached.
This is a
fatal error.
User Action: Reduce the amount of string or I/O buffer space, or
split the program into two or more modules.
MAXPARM, maximum parameter count exceeded
Facility:

VAX/VMS Command Language Interpreter

Explanation: A command contained more than the maximum number of
parameters alowed. This error can be caused by:
•

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

character,

•

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

•

Failure to place quotation marks around a character string

User Action: Determine the reason for the error and correct the
syntax of the command.
Use the HELP command or refer to the
VAX/VMS Command Language User's Guide, if necessary, to determine
the correct number of parameters for the command.
MAXSYMEXD, max.
Facility:

system symbiont count exceeded
Job controller

Explanation: The SYSGEN parameter MAXPRINTSYMB specifies the
number of print symbionts allowed. This message is issued if, as
a result of a START/QUEUE command, more symbionts exist than
MAXPRINTSYMB specifies.
User Action:
If sharing of print symbionts is not required,
the SYSGEN utility to increase the value of MAXPRINTSYMB.

use

MAYNOTINDX, this mode may not be indexed
Facility:

VAX-11 MACRO assembler

Explanation:
mode.

The base mode was register, immediate,

User Action:

Change the addressing mode.
2-148

literal

MESSAGES

MBASGN, error assigning mailbox
Facility:

Job controller

Explanation: This message indicates an internal error in the job
controller.
The symbiont manager cannot assign a channel to a
mailbox required for responding to requests.
User Action:
an SPR.

Collect as much information as possible and

submit

MBC, invalid multi-buffer count
Facility:

VAX-11 RMS

Explanation: The multi-block count field of the RAB contains
invalid value.

User Action: Verify that the call to the VAX-11 RMS service was
coded correctly. The multi-block count must be in the range of 0
through 127.

MBDEAS, error deassigning mailbox
Facility:

Job controller

Explanation:
controller.
channel.

This message indicates an internal error in the job
The symbiont manager cannot deassign a mailbox

User Action: Accompanying messages indicate the reason for the
failure.
Collect as much information as possible and submit an
SPR.

MBFULL, mailbox is full
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned by I/O functions.
A write request to a mailbox failed
because the mailbox is full.
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 he written before
any are read.

MBREAD, error reading mailbox
Facility:

Job controller

Explanation: This message indicates an internal error in the job
controller. The symbiont manaqer cannot read a request.
User Action: Accompanying messages indicate the reason for the
failure.
Collect as much information as possible and submit an
SPR.

2-149

MESSAGES
MBSETAST, error setting unsolicited mailbox message AST
Facility:

Job controller

Explanation: The print symbiont's set attention AST QIO (on its
mailbox)
failed.
The contents of the I/O status block follow
this message.
User Action: Depends on the status returned.
information as possible and submit an SPR.

Collect

much

MBTOOSML, mailbox is too small for request
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned by I/O functions. 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.
MBWRITE, error writing mailbox
Facility:

Job controller

Explanation: The print symbiont received an error writing to the
job controller's mailbox.
User Action:
an SPR.

Collect as much information as possible and

submit

MCHECK, detected hardware error
Facility:

VAX/VMS System Services

Explanation:

A hardware machine check has occurred.

User Action:

Notify the system manager.

MCHINSTSYN, machine instruction syntax error
Facility:

VAX-11 MACRO assembler

Explanation: A syntax
example, MOVL, A.
User Action:

error

occured

instruction,

for

Correct the instruction syntax.

MCNOTVALID, device microcode is not valid
Facility:

VAX/VMS System Services

Explanation: This message is associated with a
returned by I/O functions.
The microcode has
successfully loaded or has become invalid.
User Action:

Run the appropriate microcode loader.
2-150

status code
not yet been

MESSAGES
MEDOFL, medium is offline
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned by I/O functions.
An I/O request cannot be satisfied
because the device specified is not online and does not have a
physical volume mounted on it.
User Action:
the request.

Mount the required volume on the device and

repeat

MEMMANVIO, memory management violation
Facility:

BASIC (run-time)

Explanation:
location to
error.

The program attempted to read or write to a memory
which it was not allowed access. This is a fatal

User Action: If the program was compiled with /NOCHECK,
it may
be exceeding an array bound;
recompile with /CHECK. Otherwise,
check program logic.
MHDERR, module header error for 'module name' in 'library file-spec'
Facility:

LIBRARY

Explanation: This severe error message is generated by the
LIBRARY command. The specified module has an illegally formatted
header.
User Action:
line.

Compress the library before reentering the

command

MISSINGEND, missing .END statement
Facility:

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 a .END directive.

MISSNGVAL, value required on qualifier
Facility:

BTRAN

Explanation:

A qualifier lacks a value.

User Action:
qualifier.

Retype the command and

2-151

provide

value

for

the

MESSACES
MISSPEFEA, missing special feature
Facility:

BASIC (run-time)

Explanation: The program attempted to
call. This is a fatal error.
User Action: Ref er
documentation.

the

use

appropriate

unavailable
SYS

RSTS/E

SYS
call

MIXFILACC, mixed file access modes
Facility:

FORTRAN (run-time)

Explanation:

One of the following conditions occurred:

•

An attempt was made to use both
operations on the same unit.

formatted

and

unformatted

•

An attempt was made to use an invalid combination of access
modes on a unit, i.e., direct and sequential. The only valid
combination is sequential and keyed on a unit opened with
ACCESS='KEYED'.

•

An attempt was made to execute a FORTRAN I/O statement on a
logical unit that was opened by a language other than FORTRAN.

User Action: Locate the I/O statement in your program that
caused the error, and any explicit OPEN associated with the unit.
Verify that I/O to the unit is consistent iwht the attributes of
previous I/O statements.
MKD, ACP could not mark file for deletion
Facility:

VAX-11 RMS

Explanation: This message is associated with a status code
returned from a file system ACP QIO·request made by VAX-11 RMS.
The Files-11 ACP cannot delete the file.
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.
MODNAMLNG, illegal module name 'module
'library file-spec'
Facility:

name'

nnn

characters

LIBRARY

Explanation: This error message is generated by the LIBRARY
command.
The name of the object module you attempted to insert
into the library exceeds the name-length limit.
User Action:
library.

Rename the module

2-152

before

inserting

into

the

MESSAGES
MOUNTED, volume-label mounted on device name
Facility:

MOUNT

Explanation:
request.

This is an informational message

User Action:

No action is necessary.

that

verifies

MOUVOL, MOUNT relative volume nn (volume label) on device-name
Facility:

MOUNT

Explanation: This message requests an operator to mount the next
relative volume in a multivolume file.
User Action:

Mount the indicated volume on the device specified.

MOVOVEBUF, move overflows buffer
Facility:

BASIC (run-time)

Explanation: In a MOVE statement, the combined length
of
elements in the I/O list exceeds the RECORDSIZE defined for the
file. This is a fatal error.
User Action: Reduce the size of the I/O list,
file's RECORDSIZE.

increase

the

MRN, invalid maximum record number or record number exceeds MRN
Facility:

VAX-11 RMS

Explanation: An incorrect record number was specified in one
the following ways:

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

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

User Action:
1.

Verify that the call to the
correctly.

VAX-11

RMS

service

was

coded

Note the condition. Modify the source program, if necessary,
to detect and respond to the condition.

MRS, invalid maximum record size
Facility:

VAX-11 RMS

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-11 RMS service
coded correctly.
2-153

was

MESSAGES
MSGCMAIIF, missing comma in .IIF statement
Facility:

VAX-11 MACRO assembler

Explanation: The condition was not separated from the
in an .IIF directive.
User Action:

statement

Insert a comma in the directive.

MSGNOTFND, message not in system message file
Facility:

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.

MSGSEQERR, dialogue message out of order
Facility:

NIC

Explanation:

Incompatible NICE object at target node.

User Action:

None.

MTLBLLONG, magnetic
characters

volume

than

six

Explanation: The label specified for a magnetic tape volume
more than six characters.

has

User Action:
characters.

six

Facility:

tape

label

can

VAX/VMS System Services

Repeat the request;

do not specify more

than

MULDEFLBL, multiple definition of label
Facility:

VAX-11 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.
MULTREC, queue record multiply allocated
Facility:

Job controller

Explanation: This message indicates an internal error in the job
controller. The queue contains bad information.
User Action:
an SPR.

Collect as much information as possible and

2-154

submit

MESSAGES
MULTRMS, multiple RMS vectors specified
Facility:

VAX/VMS System Services

Explanation: This severe error message is associated with a
status code returned from a system service request. Multiple RMS
vectors have been specified for privileged shareable images.
User Action: Only
executable image.
and relink.

one RMS vector can be specified for an
Remove the vector associated with the problem

MUSTCLOSEFL, must close file
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a file system ACP request. 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: The operating system does not normally display this
message.
If it occurs, note the condition and modify your
program, if necessary, to detect the condition and close the file
when the condition occurs.
NAM, invalid NAM block or NAM block not accessible
Facility:

VAX-11 RMS

Explanation: The VAX-11 RMS NAM block is not in the correct
format, or is not in an area of memory that can be written by the
caller.
User Action: Verify that the call to the VAX-11 RMS service
coded correctly.

was

NAMACCNOW, name or account now exists
Facility:

BASIC (run-time)

Explanation: The program attempted to rename a file and
with that name already exists. This is a fatal error.

file

User Action: Specify a different name or use the KILL statement
to erase the old file before using the RENAME command to name the
new file.
NEF, not positioned to EOF on $PUT (sequential organization only)
Facility:

VAX-11 RMS

Explanation: A VAX-11 RMS $PUT request was attempted for a
that was not currently positioned at the end of the file.

file

User Action: Verify that the call to the VAX-11 RMS service was
coded correctly.
Modify your program, if necessary, to detect
and respond to the condition.

2-155

MESSAGES
NEGFILSTR, negative fill or string length
Facility:

BASIC (run-time)

Explanation: A MOVE statement I/O list contains a FILL item
string length with a negative value. This is a fatal error.

User Action: Change the FILL item or string length value
greater than or equal to zero.

NEGSTRLEN, negative string length
Facility:

STRING (Run-time)
a
length
lengths of

Explanation:
Successful completion except
that
parameter to a string routine had a negative value;
strings must always be positive or O. 0 was used.

User Action:
The user should verify that all
parameters
containing string lengths do not contain negative numbers.
NESERRPER, nesting error for PERFORM
Facility:

COBOL (run-time)

Explanation: A logic error has been encountered in the order
which the nesting of PERFORM ranges are exited.

User Action: PERFORM ranges must be exited in reverse order from
which the ranges are activated.
The user should examine the
logic of the PERFORM range nesting to discover why the ranges are
not exited in reverse order of their activation.
NESTLEVEL, nesting level exceeded in macro 'macro name' file
file-spec'
Facility:

'library

LIBRARY

Explanation: This error message is generated hy the LIBRARY
command.
The specified macro has exceeded the nesting limit of
63.
User Action:
library.

before

inserting

NET, network operation failed at remote node;

DAP code

xxxxxxxx

Facility:

Change the

macro

into

the

VAX-11 RMS

Explanation: The file system of the target node could not
perform the requested operation and VAX-11 RMS was unable to map
the Data Access Protocol status code into a more specific VAX-11
RMS completion code.
User Action: The status value (STV) field of the FAB or RAB
contains the DAP status code.
Consult the DECnet-VAX User's
Guide to interpret the status code and take corrective action.

2-1sn

MESSAGES
NEWFILES, nnn files created
Facility:

Shared by several facilities

Explanation: The command
successfully created.
User Action:

None.

displays

the

number

new

files

This message is informational.

NMF, no more files found
Facility:

VAX-11 RMS

Explanation: The directory or volume set does not contain any
more
files
that
meet the file specification (wild card
operation); this status code is returned on a VAX-11 RMS $SEARCH
or $REMOVE operation.
User Action: Note the condition. Modify the source program,
necessary, to detect and respond to the condition.

NOACPDEV, device named by /PROCESSOR:SAME has no ACP
Facility:

MOUNT

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, or specify the file name of the desired
ACP, if known.
NOAQB, ACP queue header not found
Facility:

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 RUN command.
User Action: ACPs can only be started with the MOUNT command.
If this message results from a MOUNT command, gather as much
information as possible and submit an SPR.
NOBADDATA, bad data block not found on volume
Facility:

INITIALIZE

Explanation: This is a warning message generated
by
the
INITIALIZE command;
software bad block data is not present on
the volume. The volume has been initialized with no bad blocks.
User Action:

Run BAD before initializing.

2-157

MESSAGES
NOCALLS, no active call frames
Facility:

TRACE

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.
User Action:

None.

The message is informational.

NOCCAT, no concatenation allowed in parameter
Facility:

VAX/VMS Command Language Interpreter

Explanation: A command that accepts only a single input
specification
for
a
parameter
contained
multiple
specifications separated by plus signs (+).
command
User Action: Reenter
the
specification.
If necessary, enter
file.

file
file

with
a
single
file
the command once for each

NOCLI, no command interpreter
Facilityi

OPCOM

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,
necessary, to detect and respond to the condition.

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 a~cess command packets.
NOCOMD, no command on line
Facility:

VAX/VMS Command Language Interpreter

Explanation: A
command
string
contains
one
or
more
nonalphanumeric characters, but no alphanumeric characters that
can be evaluated. Or, a command continued on more than one line
did not contain a blank space or tab required to delimit
parameters.

2-158

MESSAGES
User Action: If you entered a symbol name, verify that the
symbol is defined by using the SHOW SYMBOL command, and reenter
the command.
If the error occurred in a command procedure, verify
of the command lines and check for continued lines.

the

syntax

NOCOMM, unable to initialize process mailbox or common efn's
Facility:

RSX

Explanation: An error was encountered attempting to set up
process
receive
mailbox
or common event flags used
communication with other processes.

the
for

User Action: Ensure that the duplicate process name does not
exist, and that you have a quota large enough to create a mailbox
and common event flag cluster.
NO_CURREC, no current record
Facility:

BASIC (run-time)

Explanation: The program attempted a DELETE or UPDATE when the
previous GET or FIND failed, or no previous GET or FIND was done.
This is a fatal error.
User Action: Correct the cause of failure for the previous GET
or FIND, or make sure a GET or FIND was done, then retry the
operation.
NOCURREC, no current record
Facility:

FORTRAN (run-time)

Explanation: A REWRITE or current record
when no current record was defined.

DELETE

was

attempted

User Action: Correct the program so that a current record is
defined when a REWRITE or DELETE is attempted. See the VAX-11
FORTRAN User's Guide for information.
NOD, error in node name
Facility:

VAX-11 RMS

Explanation: The node name portion of a
not in the correct syntax.

file

specification

User Action: Check the syntax of the node name specification and
retry the operation.
Verify that the call to the VAX-11 RMS
service was coded correctly.

2-159

MESSAGES
NODISKQUOTA, no disk quota entry for this UIC

Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a file system ACP QIO request. The specified quota
file entry does not exist.
User Action: Check the UIC given.
for it or use another UIC.

Either add a quota file entry

NODNAMERR, node name error

Facility:

BASIC {run-time)

Explanation: A file specification's node name contains a
error. This is a fatal error.
User Action:

Supply a valid node name.

NOEOM, module 'module name' is
'library file-spec'

Facility:

syntax

not

terminated

with

EOM

record

LIBRARY

Explanation: This error message is generated by the LIBRARY
command.
The module you attempted to insert into the library
does not contain a legal EOM record.
User Action:

Recompile the object module.

NOFILNAM, no file specification found

Facility:

Librarian

Explanation: This error message is generated by the Librarian
routines.
In the LBR$0PEN routine,·either the FNS argument was
not provided, or the NAM block was not filled-in.
User Action:

Correct the problem before callinq 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.

Directory is already purged.

NOFORMLARG, no formal argument for .IRP/.IRPC

Facility:

VAX-11 MACRO assembler

Explanation:
directive.

There were no formal arguments in an .IRP or

User Action:

Correct the syntax of .IRP or .IRPC directive.

2-lnO

.IRPC

MESSAGES
NOHANDLER, no condition handler found
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a system service request. 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.

NOHLPTXT, help text not found
Facility:

Librarian

Explanation: This error message is generated by the Librarian
routines.
There is no help text associated with the specified
key path.
User Action:

Check that the help module is properly formatted.

NOHLPTXT, no level l help text found in 'input file-spec'
Facility:

LIBRARY

Explanation: This warning message is generated by the LIBRARY
command.
The specified input file does not contain a properly
formatted help file.
User Action:
command line.

Reformat

the

help

file

before

reentering

the

NOHOMEBLK, Files-11 home block not found on volume
Facility:

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
the volume as foreign.

mounted.

Mount

NOIOCHAN, cannot piggyback I/O channel with PUTMSG
Facility:

TRACE

Explanation: This message
internal consistency check.
User Action:
an SPR.

associated

with

traceback

Collect as much information as possible and

2-1n1

submit

MESSAGES
NOIOCHAN, no I/O channel available
Facility:

VAX/VMS System Services

Explanation: This severe error message is associated with a
status code returned from a system service request. 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.
NOJOBID, job nnn not found in 'queue-name' queue
NOJOBNAME, job 'name' not found in 'queue-name' queue
Facility:

Shared by several facilities

Explanation: A request to modify or delete a job failed because
the job does not exist. The message identifies the job by job
name or job identification number, depending on the command
specification.
User Action: Verify that the job identification number or job
name 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.
NOKEYW, no keyword in qualifier
Facility:

VAX/VMS Command Language Interpreter

Explanation: A slash character (/) was present on a command
was not followed by a qualifier keyword name.
User Action:

Reenter the command;

but

specify the qualifier.

NOLINKS, no slots in logical link vector
Facility:

VAX/VMS System Services

Explanation: The maximum number of allowable logical network
links exist and no more slots are available to establish another
link.
User Action:

Wait and retry the request later.

NOLIST, parameter list not allowed
Facility:

VAX/VMS Command Language Interpreter

Explanation: A command that accepts only a single input
specification
for
a
parameter
contains
multiple
specifications separated by commas (,).

file
file

User Action: Reenter the command; specify only one file.
necessary, issue the command once for each file specified.

2-162

MESSAGES
NOLOGNAM, no logical name match
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a system service request. A specified logical name
does not exist or cannot be deleted by the current access mode.
User Action: Check for a programming error.
of the logical name.

Verify the spelling

NOMACFOUND, no .MACRO found in 'input file-spec'
Facility:

LIBRARY

Explanation: This warning message is generated by the LIBRARY
command.
The specified input file does not contain a properly
formatted macro.
User Action:

Reformat the macro source file.

NOMBX, no associated mailbox for inbound connects
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status return
from a network ACP control function. 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.
NOMODNAM, no module name found for 'input file-spec'
Facility:

LIBRARY

Explanation: This error message is generated by the LIBRARY
command. An attempt was made to insert unnamed text modules into
a text library.
User Action:

Use the /MODULE qualifier to name the text modules.

NOMOREFILES, no more files
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a file system ACP QIO request. 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,
necessary, to detect and respond to the condition.

2-163

MESSAGES
NOMOREPROC, no more processes
Facility:

VAX/VMS System Services

Explanation: This warning message is associated with a status
code returned from a system service request. The search for
processes is complete.
User Action:

None required.

NOMTCHENDM, no matching .ENDM
'library file-spec'
Facility:

for

macro

'macro

name'

library

LIBRARY

Explanation: This warning message is generated by the LIBRARY
command.
The specified macro does not contain a matching .ENDM
line.
User Action:

Reformat the macro source file.

NOMTCHENDR,
'location' missing
'library file-spec'
Facility:

.ENDR

for

macro

'macro

name'

LIBRARY

Explanation: This warning message is generated by the LIBRARY
command.
The Librarian found a matching .ENDM before the
required .ENDR.
User Action:

Correct the macro source file.

NOMTCHFOU, no matches found for 'module-name'
Facility:

LIBRARY

Explanation: This warning message is' generated by the LIBRARY
command. The module specified with the /ONLY qualifier is not in
the MNT.
User Action:

Make sure that the specified module exists.

NOMTCHFOU, no match found
Facility:

Librarian

Explanation: This warning message is generated by the Librarian
routines. The specified module does not appear in the MNT.
User Action:
library.

Make sure that the module

2-1~4

exists

the

current

MESSAGES
NONEXDRV, nonexistent drive
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned
by
I/O
functions.
The drive specified in an
input/output request either does not exist or the drive select
plug has been removed.
User Action: Verify the availability and status of
Also, check the source program for errors.

the

device.

NONEXPR, nonexistent process
Facility:

VAX/VMS System Services

Explanation: A process name or process identification
in a command or system service request is not valid.

specified

User Action: Verify that the process name or identification is
correct and that the process has not already been deleted.
If a
process name was entered, the process must be in the same group.
NONLOCAL, device is not a local device
Facility:

VAX/VMS System Services, MOUNT, and INITIALIZE

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.
NONRSXEMT, non-RSX-llM EMT execution
Facility:

RSX

Explanation: An RSX-llM image attempted to execute an EMT
instruction that is not a valid RSX-llM EMT. This message
corresponds to the RSX-llM termination message NON-RSX EMT
EXECUTION.
User Action: Determine the instruction or statement at which the
error occurred and correct the error.
NOOPENJOB, user job not open
Facility:

Job controller

Explanation: A request to the symbiont manager failed because no
open jobs in the queue owned by the current process are open and
the process attempted to add a file to the job. This message is
associated with a status code returned by the job controller.
The operating system does not normally display this message.
User Action: Note the condition. Modify the sourc~ program,
necessary, to detect and respond to the condition.

2-lnS

MESSAGES
NOOPTPRS, no option present on command
Facility:

VAX/VMS Command Language Interpreter

Explanation: This message is associated with an internal status
code returned by the command interpreter result parse routine.
The operating system does not normally display this message.
User Action: Note the condition. Modify the source program,
necessary, to detect and respond to the condition.

NO_OUTRTN, no output routine address provided
Facility:

CREF

Explanation:

No output routine was provided for LIB$CRF OUTPUT.

User Action:

Provide an output routine.

NOPlVA, Pl space not supported in shareable images
Facility:

VAX/VMS System Services

Explanation: This severe error message is associated with a
status code returned from a system service request. Pl space is
not supported in shareable images.
User Action:
space.

Relink the image, positioning all binary nata in PO

NOPERATOR, no operator coverage
Facility:

OPCOM

Explanation: A REQUEST command specified a nonexistent operator.
No terminals are currently enabled for that operator name.
User Action: Reenter
alternative operator.

the

REQUEST

command

specifying

NOPMD, post-mortem dump failure, file-name
Facility:

RSX

Explanation: VAX/VMS could not perform a post mortem dump as
requested;
that is, it could not create the indicated dump file
in the current default directory.
User Action: Verify the current default directory and protection
with
the
SHOW DEFAULT and SHOW PROTECTION commands.
If
necessary, use the SET DEFAULT or SET PROTECTION command to set
the correct directory and protection;
retry the post-mortem
dump.

2-1n~

MESSAGES
NO_PRIKEY, no primary key specified
Facility:

BASIC (run-time)

Explanation: The program attempted to create an INDEXED file
without specifying a PRIMARY KEY value. This is a fatal error.
User Action:

Specify a PRIMARY KEY value.

NOPRIV, diagnostic and operator privileges required
Facility:

NCP

Explanation:

DIAGNOSE and OPER privileges required.

User Action:
privileges.

Run

NCP

under

account

with

DIAGNOSE

and

OPER

NOPRIV, insufficient status
Facility:

NIC

Explanation: A NICE object is running under an account that does
not have DIAGNOSE or OPER privilege.
User Action: Modify privileges of the default privileged account
on the node where the operation failed.
NOPRIV, no privilege for attempted operation
Facility:

VAX/VMS System Services and Job controller

Explanation: A command or program requested
that requires a specific user privilege;
does not have the requisite privilege.

a system function
the current process

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
was denied.

volume

access

which

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. Or, verify that you are not attempting to modify a VAX-11
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
volume change the protection value.
2-167

the

file

MESSAGES

NOPRIV, user denied privilege to write to volume on device-name
Facility:

MOUNT

Explanation: The user has requested initialization of
and does not have the privilege to write to it.

volume

User Action: Mount either a tape which the user has the
privilege to write to or a blank tape. Request initialization of
this tape when replying to the next mount request.

NOQFILE, no disk quota file available
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a file system ACP QIO request. The quota file does
not exist.
User Action: Verify that
Create the quota file.

you

are

using

the

correct

device.

NOQUAL, qualifier not allowed on this command
Facility:

VAX/VMS Command Language Interpreter

Explanation:
a qualifier.

A command that has no qualifiers was specified with

User Action:
qualifiers.

Reenter

the

command;

not

specify

any

NOQUEHDR, queue header space full
Facility:

Job controller

Explanation: A request to the symbiont manager failed because
not enough space is available to allocate queue headers. An
existing queue must be deleted before a new one can be created.
In
general,
this message indicates that the queue space
allocation for the job controller should be made bigger.
User Action:
programmer.

Notify

the

installation

system

manager

NOQUESPACE, no space to queue files
Facility:

Job controller

Explanation: A device queue specified in a symbiont manager
request is full and cannot hold any more jobs. This message is
associated with a status code returned by the job controller.
The operating system does not normally display this message.
User Action: Wait for the queue to empty and retry the program.
If the error occurs frequently, request the system manager to
increase the amount of queue space available to the
job
controller.

2-168

MESSAGES
NOQUEUE, queue-name queue does not exist
Facility:

Shared by several facilities

Explanation: A request to enter or change a queued
because the queue does not exist.

file

failed

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 SHOW QUEUE/DEVICES/BATCH command.
Note that the SET QUEUE and SHOW QUEUE commands do not translate
logical names.
If you specified a logical name, reenter the
command with the physical queue name.
NOREC, no entry in database
Facility:

NCP

Explanation:

A reference was made to nonexistent data.

User Action:

Refer to data properly.

NO_REMOTE, remote NICE process not available
Facility:

NIC

Explanation:

Attempt at loopback failed.

User Action:

Ensure that the NICE object can run at remote node.

NORESOURCE, resource error
Facility:

NIC

Explanation: A resource error, such as a system service failure,
occurred during an attempt to complete the specified command.
User Action: Repeat the command. If the error persists, ensure
that the system pool is adequate and that the confiquration data
base is consistent.
NORMAL, success
Facility:

LIBRARY and librarian

Explanation: This success message is associated with a code
returned by the librarian, or generated by the LIBRARY command.
User Action: None. This is a successful status code.
operating system does not normally display this message.

2-169

The

MESSAGES

NORMAL, normal successful completion
Facility:

VAX-11 MACRO assembler and VAX/VMS System Services

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.
normally displayed by the operating system.

not

NO_ROOM, no room for new entry
Facility:

NIC

Explanation:

No room for new entry in database.

User Action:

Delete unwanted items from database.

NO_ROOUSE, no room for user on device
Facility:

BASIC (run-time)

Explanation: No user storage space
device. This is a fatal error.
User Action:

exists

the

specified

Delete files that are no longer needed.

NOSHMBLOCK, no free shared memory block available for creation
Facility:

VAX/VMS System Services

Explanation: This severe error message is associated with a
status code returned from a system service request. 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.

NOSIGNAL, no signal currently active
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a system service request. 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 proqrammming error.

2-170

MESSAGES
NOSLOT, no pcb or swap slot available
Facility:

VAX/VMS System Services

Explanation: This warning message is associated with a status
code returned from a system service request. 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:

VAX/VMS System Services

Explanation: The program attempted to send an interrupt message
to a partner on a remote node but the DECnet implementation on
that node has not solicited a message.
User Action:

Wait and retry the request.

NOSPACE, failure to map symbol table, EXPREG status
Facility:

xxxxxxxx

TRACE

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:
an SPR.

Collect as much information as possible and

submit

NO_SPACE, no filespace on device for file
Facility:

COBOL (run-time)

Explanation: During the course of an OPEN operation, a failure
to find additional space on a particular device was detected.
The file status variable, if present, has been set to 95.
No
applicable USE procedure has been found.
User Action: The user most likely has many out-dated and/or
transient files on the device. The user is advised to examine
the directories on the particular device and to free sufficient
space by purging or deleting unused files and resubmit the
program for execution.
NOSUCDEV, no such device
Facility:

FORTRAN (run-time)

Explanation: A file name specification included an invalid
unknown device name when an open operation was attempted.

User Action Locate the explicit OPEN statement that caused the
error or the I/O statement that caused the implicit open. The
message displays the complete file specification of the file.
If
the specification contains a logical name, verify that the
logical name was assigned a proper equivalence name. Correct the
OPEN statement, or assign a proper logical name, as required.
2-171

MESSAGES
NOSUCHDEV, no such device available
Facility:

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 SHOW DEVICES command to determine whether such a device
exists.
If the device was coded as a logical name,
assigned a valid equivalence name.
NOSUCHDEV,
TKB-assigned
lun=logical-unit
Facility:

device

not

verify

found,

that

was

device-name,

RSX

Explanation: VAX/VMS cannot perform the preassignment of a
device specified at task build time. The indicated device does
not map to a VAX/VMS physical device. The message indicates the
device name causing the error and its LUN.
User Action: Either rebuild the image specifying a VAX/VMS
physical or logical device name, or assign the indicated device
name as the logical name for a VAX/VMS device prior to running
the image.
NOSUCHFILE, no such file
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a file system ACP QIO request.
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,
necessary, to detect and respond to the condition.

NOSUCHJOB, no job as specified
Facility:

Job controller

Explanation: The job specified in a request to modify or delete
a job from a queue does not exist. A network object is unknown
at remote node.
User Action: Verify that the job identification number was
entered correctly. If not, reenter the command with the correct
job identification. Otherwise, the message indicates that the
job is no longer in the queue;
that is, that the job has already
been processed or is currently being processed.

2-172

MESSAGES
NOSUCHNODE, specified node does not exist
Facility:

VAX/VMS System Services

Explanation: The node name portion of
a
file
or
task
specification refers to a node that is not known to the network
ACP.
User Action: Check the node name specification.
Verify the
status of the network and available nodes with the SHOW NETWORK
command.
NOSUCHOBJ, network object is unknown at remote node
Facility:

VAX/VMS System Services

Explanation: An attempt was made to initiate a DECnet logical
link connection.
The target object of the connect could not be
found on the specified node. Either 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 DECnet-VAX User's Guide for additional information.
NOSUCHQUE, no such queue exists
Facility:

Job controller

Explanation: The device name specified in a command to queue a
job or alter or delete a job from a queue is not the name of a
queue.
User Action: Verify the device name
(or logical name,
if a
logical name was specified), and reenter the command with a valid
device name. If the device name was valid, verify that it is
available for queueing jobs by issuing the SHOW QUEUE/DEVICE
command.
NOSUCHRQST, no such request
Facility:

OPCOM

Explanation: A REPLY command
identification number.

specified

nonexistent

message

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.

2-173

MESSAGES
NOSUCHSEC, no such (global) section
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a system service request. The global section name
specified in a request to map a global section does not exist.
User Action: Check for a programming error.
Verify that the
program that creates the global section successfully created the
section, and that the section has not been deleted. Also, check
that the logical name strings specifying the global section name
match.
NOSUCHUSER, login information not recognized at remote node
Facility:

VAX/VMS System Services

Explanation: This severe error message is associated with a
status code returned from a system service request. An attempt
was made to initiate a DECnet 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 sytem 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), was too
long, or contained illegal characters.
Refer to the DECnet-VAX User's Guide for additional information.
NOTANSI, not ANSI volume on device-name
Facility:

MOUNT

Explanation: The volume on
ANS-formatted magnetic tape.

the

specified

device

User Action:
Initialize the tape and reissue the
or mount the tape foreign.

mount

not

request

NOTAPEOP, no tape operator
Facility:

VAX/VMS System Services

Explanation: This message is associated with a file system ACP
request.
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: Note the condition.
Make sure the tapes were
mounted on the original mount request or run the job when an
operator is present.

2-174

MESSAGES
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-11 RMS message indicating the
reason for the failure.
User Action: Take corrective action based on the accompanying
message.
Use the TYPE or DUMP command 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-11 RMS message indicating
the reason for the failure.
User Action:
message.

Take corrective action based

the

accompanying

NOTCREATOR, request denied, user is not on creator port
Facility:

VAX/VMS System Services

Explanation: A shared memory global section may only be deleted
or updated 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.
NOTDECSTRG, illegal character in decimal string
Facility:

VAX-11 MACRO assembler

Explanation: A decimal string contained a character other
the digits 0 through 9 and a leading plus or minus sign.
User Action:

than

Correct the syntax of the decimal string.

NOTENABOPT, not a legal ENABLE option
Facility:

VAX-11 MACRO assembler

Explanation: An argument to a .ENABLE or .DISABLE directive
not a legal option.
User Action:
option.

Delete the

option

2-175

replace

with

was
legal

MESSAGES
NOTENDFIL, not at end of file
Facility:

BASIC (run-time)

Explanation: The program attempted a PUT operation
on
a
sequential file before the last record, without opening the file,
or without WRITE access. This is a fatal error.
User Action: OPEN a sequential file with ACCESS APPEND, or
the file with ACCESS WRITE.

OPEN

NOTENODAT, not enough data in record
Facility:

BASIC (run-time)

Explanation: An INPUT statement did not find enough data in one
line to satisfy all the specified variables. This is a fatal
error.
User Action: Supply enough data in the
number of specified variables.

record,

reduce

the

operands

than

were

NOTENUFOPR, not enough operands supplied

Facility:

VAX-11 MACRO assembler

Explanation: The instruction requires more
specified in the statement.
User Action:

Add the operands or change the instruction.

NOTFILEDEV, device is not file structured
Facility:

Shared by several facilities

Explanation: This message is associated with a status code
returned from a system service request. 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.
NOTFORSPE, not a FORTRAN-specific error
Facility:

FORTRAN (run-time)

Explanation: An error occurred in the user program or
Run-Time Library that was not a FORTRAN-specific error.
User Action:
error.

Take corrective

action

2-176

based

the

associated

MESSAGES
NOTFOU, not found
Facility:

VAX-11 Run-Time Procedure Library

Explanation: This message is associated with a status code
returned from the Run-Time Library. 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,
necessary, to detect and respond to the condition.

NOTFR, no transfer address
Facility:

VAX/VMS Command Language Interpreter

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.
NOTHLPLIB, not a HELP library
Facility:

Librarian

Explanation: This error message is generated by the Librarian
routines.
The library type specified in LBR$GET HELP is not a
help library.
User Action: Determine that the library is a help library before
calling the routine.
NOTIMP, not implemented
Facility:

BASIC (run-time)

Explanation: The program attempted to use a feature that does
not exist in this version of BASIC, for example, CHAIN with line
number. This is a fatal error.
User Action:

None.

This message is informational.

NOTIMPLEM, not implemented
Facility:

BTRAN

Explanation:
program.

An internal error was

detected

the

BACKTRANS

User Action: Collect as much information as possible and submit
an SPR.
Give examples of the command line. Notify the system
manager.

2-177

MESSAGES
NOTINANIF, statement outside condition body
Facility:

VAX-11 MACRO assembler

Explanation: A .IF FALSE,
.IF TRUE,
.IF TRUE FALSE,
.IFT, or
.IFTF subconditional directive-was not in-a conditional assembly
block.
User Action: Replace the subconditional directive
with
conditional directive or delete the subconditional directive.

NOTINMACRO, statement not in MACRO body
Facility:

VAX-11 MACRO assembler

Explanation: The .NARG directive was not in a
or expansion.
User Action:
directive.

Delete

move

the

line

macro

containing

definition
the

.NARG

NOTINSTALL, writable shareable images must be installed
Facility:

VAX/VMS System Services

Explanation: This severe error message is associated with a
status code returned from a system service request. Writable
shareable images must be installed.
User
Action:
/SHARE/WRITE.

Install

the

shareable

image

specifying

NOTLABEL, (volume-label) not on device-name
Facility:

MOUNT

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 hy the original MOUNT
command, or the reply to an operator mount request, does not
match the label of the volume 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 MOUNT command. Verify that the device
is online.
NOTLABELMT, tape is not labeled
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a file system ACP QIO request. 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.

2-178

MESSAGES
NOTLGLISOP, not a legal listing option
Facility:

VAX-11 MACRO assembler

Explanation: The argument to a .SHOW, .NOSHOW, .LIST, or
directive was not a legal option.

.NLIST

User Action: Delete the illegal option
legal option.

with

replace

NOTLOCKED, file-spec was not locked
Facility:

Shared by several facilities

Explanation:
locked.

The file specified by an

User Action:

None.

UNLOCK

command

was

not

This message is informational.

NOTMODIFIED, no pages in the section were modified
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a system service request:
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.
NOTNEG, qualifier has no negative form
Facility:

VAX/VMS Command Language Interpreter

Explanation: The word "NO" preceded a qualifier,
qualifier cannot be specified as a negative.

but

the

User Action: Use the HELP command or ref er to the VAX/VMS
Command Language User's Guide for a list of valid qualifiers.
NOTNETDEV, not a network communication device
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from network ACP control function. The device specified
is not a network communications device, and the control function
cannot be performed.
User Action: Check for a programming
device
specified
in
the
queue
communications device.

2-179

error.
Verify that the
I/O request is a valid

MESSAGES

NOTOBJLIB, not an object library
Facility:

LIBRARY

Explanation: This error message is generated by the LiBRARY
command.
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
library that contains the requested symbol.

object

NOTPSECOPT, not a valid PSECT option
Facility:

VAX-11 MACRO assembler

Explanation:
invalid.

The attribute specified in the .PSECT directive was

User Action:
valid one.

Delete the invalid attribute or replace it

with

NOTRAN, logical name cannot be translated
Facility:

INITIALIZE and MOUNT

Explanation: The MOUNT or INITIALIZE command 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 too deeply nested or if a logical name is
assigned to itself.
User Action: Use the SHOW LOGICAL command to verify
the
translation of the device name or logical name. If necessary,
reassign the logical name before reentering the MOUNT
or
INITIALIZE command.

NOTRAN, no string translation performed
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a system service request. 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,
necessary, to detect and respond to the condition.

NOTRANACC, not a random access device
Facility:

BASIC (run-time)

Explanation: The program attempted a random access on a device
that does not allow such access;
for example, a PUT with a
record number to a magtape file. This is a fatal error.
User Action: Make the access sequential instead of random or use
a suitable I/O device.

2-180

MESSAGES
NOTRELVOL, relative volume nnn not on device
Facility:

MOUNT

Explanation: Each volume in a volume set has a relative number
beginning with 1.
The volume mounted on the device is not the
relative volume requested in the previous mount request.
User Action: Mount the correct volume on the device or abort the
.mount request if you do not have the correct volume.
NOTSKIMG, file is not RSX-llM task image, image-name
Facility:

RSX

Explanation: An RSX-llM task requested for execution
built using the RSX-llM Version 3.1 Task Builder.

was

not

User Action: Rebuild the image using the correct task
VAX/VMS provides the 3.1 Task Builder with the system.

builder.

NOTSTRUCTl, qualifier(s) not available with structure level l
Facility:

INITIALIZE

Explanation: This message is generated by the INIT command.
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.

NOTVOLSET, volume is not part of a volume set
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from an ACP QIO request.
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
or remove the volume-specific reference.

was

specified

NOTVOLSET, volume on device-name not in volume set (volume-label)
Facility:

MOUNT

Explanation: The label of the first volume 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.

2-181

MESSAGES

NOVALU, no value allowed on qualifier
Facility:

VAX/VMS Command Language Interpreter

Explanation: A qualifier that
specified · with
a
keyword,
specification.

does not accept a value was
a numeric value, or a file

User Action: Use the HELP command or ref er to the VAX/VMS
Command Language User's Guide,
if necessary, for the correct
syntax and -r-eeiite··r- -Eh_e ___Commana:-

NOVALUE,

'keyword' keyword requires a value

Facility:

Shared by several facilities

Explanation:
value.

The keyword indicated

User Action: Reenter the
indicated keyword.

command;

must

specify

specified

with

for

value

a
the

NOVALUE, value not present
Facility:

VAX/VMS Command Language Interpreter

Explanation: This message is associated with an internal status
code returned by the command interpreter's result parse routine.
The operating system does not normally display this message.
User Action: Note the condition. Modify the source program,
necessary, to detect and respond to the condition.

NOWILD, no wildcard permitted
Facility:

Shared by several facilities

Explanation:

Wild cards are not permitted in this context.

User Action:

Respecify using exact file specifications.

NOWRT, cannot create writable section to read-only file
Facility:

VAX/VMS System Services

Explanation: This severe error message is associated with a
status code returned from a system service request. An image
file that was opened read-only contains a writable section.
You
cannot create a writable section to a read-only file.
User Action: Close and open the file correctly.
If INSTALL
gives this error, use the /WRITE qualifier in addition to /SHARE.

2-18 2

MESSAGES
NPK, no primary key defined for indexed file
Facility:

VAX-11 RMS

Explanation: A VAX-11 RMS $CREATE service was
primary key XAB definition was provided.
User Action:
correctly.

Verify

that

the

VAX-11

RMS

executed
service

was

and

coded

NULFIL, null file specification
Facility:

VAX/VMS Command Language Interpreter

Explanation: The
command
interpreter
expected
a
file
specification following an at symbol (@.) (execute procedure), a
prompting message, a plus sign (+), or a comma (,), but no file
specification was entered.
User
Action: Reenter
the
command;
specification in the proper position.

specify

the

file

NULIDX, index is empty
Facility:

Librarian

Explanation: This warning message is generated by the Librarian
routines.
The specified index was found empty on a call to
LBR$GET INDEX.
User Action:

None.

Processing continues.

NUMBER, invalid numeric field
Facility:

VAX/VMS Command Language Interpreter

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 HELP command or ref er to the VAX/VMS
Command Language User's Guide, if necessary, for the legal values
and reenter the command.
OCCDEPOVE, OCCURS DEPENDING value overflows longword
Facility:

COBOL (run-time)

Explanation: The value of the data name associated with
OCCURS DEPENDING phrase cannot be contained in a longword.

User Action: The user should examine the referenced line in the
source program containing an implicit reference to the data name
associated with an OCCURS DEPENDING phrase to determine why this
value has overflowed a longword value.

2-183

MESSAGES

ODDADDR, compatibility mode odd address
Facility:

RSX

Explanation: An RSX-llM image attempted a word reference on a
byte boundary.
The PC contains the address of the instruction
that caused the error. In RSX-llM, the PC contains the address
of the instruction followinq the erroneous instruction. This
message corresponds to the RSX-llM termination message ODD
ADDRESS ERROR.
User Action: Determine the instruction or statement at which the
error occurred and correct the error.

OFFLINE,

'device-name'

Facility:

offline

MOUNT

Explanation: The given device is offline.
cannot be completed.
User Action:

The requested

action

Place the device on line and reenter the command.

OK_ALK, record is already locked
Facility:

VAX-11 RMS

Explanation: A VAX-11 RMS request to lock a record returns this
success status code when the specified record is already locked.
User Action:

None.

This message is informational.

OK_DEL, deleted record successfully accessed
Facility:

VAX-11 RMS

Explanation: A VAX-11 RMS request to · access a deleted record
returns this success status code when the specified record is
accessed.
User Action:

None.

The message is informational.

OK_DUP, record inserted had duplicate key
Facility:

VAX-11 RMS

Explanation: A VAX-11 RMS $PUT or $UPDATE service completed
successfully. The record inserted or updated had one or more key
values that duplicated the values of other records.
User Action:

None.

This message is informational.

2-184

MESSAGES
OK_IDX,

index update error occurred

Facility:

VAX-11 RMS

Explanation:

A VAX-11 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-11
RMS error
that occurred during ind
update.
Take
corrective action based on that value.
File
reorganization
is
recommended.

OK_LIM,

retrieved record exceeds specified key value

Facility:

VAX-11 RMS

Explanation:

A VAX-11 RMS $GET request returns this success code
if
the
retrieved record exceeds the specified key value and the
RAB$M_LIM option is specified.

User Action:

None.

This message is informational.

OK_NOP, XAB not filled in for block I/O

Facility:

VAX-11 RMS

Explanation:

A VAX-11
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:
OK_RLK,

None.

This message is informational.

record locked but read anyway

Facility:

VAX-11 RMS

Explanation: A VAX-11 RMS
completed successfully.
User Action:

None.

request

read

locked

record

This message is informational.

OK_RNF, nonexistent record successfully accessed

Facility:

VAX-11 RMS

Explanation:

A VAX-11 RMS request to access a nonexistent record
completed successfully.

User Action:

None.

This message is informational.

OLDLIBRARY, old format library opened

Facility:

Librarian

Explanation:

This success message is generated by the

routines.

User Action:

None.

This message is informational.

2-185

Librarian

MESSAGES
OLDMISMCH, old format library type mismatch
Facility:

Librarian

Explanation: This warning message is generated by the Librarian
routines.
The requested Version 1.0 library is of a different
type from that expected.
User Action: None.
library type.

Processing continues

based

the

actual

Explanation: The command action for an ON command in
procedure is too complex to be evaluated.

command

ONCOMD, ON command too complex
Facility:

VAX/VMS Command Language Interpreter

User Action: Correct the command
command action.

simplify

procedure;

the

ONEOR_TWO, one or two dimensions only
Facility:

BASIC (run-time)

Explanation: The program contains a DIM or MAT statement that
attempts to assign more than two dimensions to an array. This is
a fatal error.
User Action: Change the number of dimensions in the DIM
statement to one or two.

MAT

ONERR, invalid ON error level specified
Facility:

VAX/VMS Command Language Interpreter

Explanation: The keyword specified in the ON command to indicate
the severity level is not recognized.
User Action: Correct the ON command, using one of
WARNING, ERROR, or SEVERE ERROR.

the

keywords

ONEVAL, multiple values are not permitted
Facility:

VAX/VMS Command Language Interpreter

Explanation: A qualifier that accepts only a
specified with multiple values.
User Action: Reenter the command;
the qualifier.

single

specify only

one

value

was

value

for

can

ONLEVL, ON condition not legal at current level
Facility:

VAX/VMS Command Language Interpreter

Explanation: An ON command was issued interactively.
only be issued from a command procedure.
User Action:

None.
2-186

MESSAGES
ONOVF, no room for ON condition command text
Facility:

VAX/VMS Command Language Interpreter

Explanation: Nested command
command interpreter's space
text for each command level.

procedures have
exhausted
the
for maintaining the action command

User Action: Simplify the command procedure hierarchy,
shorten the action command text for ON conditions.

ON_STAOUT, ON statement out of range
Facility:

BASIC (run-time)

Explanation: The index value in an ON GOTO or ON GOSUB statement
is less than one or greater than the number of line numbers in
the list. This is a fatal error.
User Action: Check program logic to make sure that the index
value is greater than or equal to one, and less than or equal to
the number of line numbers in the ON GOTO or ON GOSUB statement.
OPCCUS, opcode reserved to customer fault at PC location, PSL=xxxxxxxx
Facility:

VAX/VMS System Services

Explanation: An operation code
beginning
with
AXFC
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:

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.
OPEDEFREQ, OPEN or DEFINE FILE required for keyed or direct access
Facility:

FORTRAN (run-time)

Explanation:

One of the following conditions occurred:

•

A direct access READ, WRITE, FIND or DELETE statement was
attempted for a file when no DEFINE FILE or OPEN statement
with ACCESS='DIRECT' was performed for that file.

•

A keyed access READ statement was attempted for a file when no
OPEN statement with ACCESS='KEYED' was performed for that
file.
2-187

MESSAGES
User Action: Locate the I/O statement that caused the error and
verify that the OPEN or DEFINE FILE statement for the specified
logical unit specified the correct access.

OPEFAI, open failure
Facility:

FORTRAN (run-time)

Explanation: RMS detected an error during an attempt to open a
file in an OPEN, INQUIRE or other I/O statement. This message is
used when the error condition is not one of the more common
conditions for which specific error messages are provided.
User Action: Use the associated VAX-11 RMS message to
the reason for the error and correct it.

determine

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-11 RMS message indicating the reason
for the failure.
User Action:
message.

Take corrective

action

based

the

associated

OPENIN, input file open error
Facility:

LIBRARY

Explanation: This error message is qenerated by the LIBRARY
command.
One of the following conditions prevented the LIBRARY
command from opening the input file:

•

The user directory is protected against read operations.

•

A physical device problem occurred;
is not mounted.

•

The speciifed directory does not exist.

•

The specified file does not exist.

•

On create or compress operations, there is not enough room
quota to allocate the new library file.

User Action:

for example,

the

volume

Correct the problem and reenter the command line.

OPENOUT, error opening output file
Facility:

LIBRARY

Explanation: This severe error message is generated by the
LIBRARY command.
During a VAX-11 RMS operation, an error was
encountered while opening an output file.
User Action: Determine that the file is open and that
write privilege to it.

2-188

you

have

MESSAGES
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-11 RMS message indicating the reason
for the failure.
User Action:
message.

Take corrective

action

based

the

associated

OPINCOMPL, operation is incomplete
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
A
block mode
returned from a DRll-W interface operation.
transfer operation completed without transferring the requested
The DR-llW generated an end-of-transfer
number
of bytes.
This message
interrupt without transferring all the data.
results from a hardware error.
Some disk devices can also return this message.
User Action:

Check for a hardware error.

OPREPLY, message-text
Facility:

OPCOM

Explanation: An operator's response
displayed on the terminal.
User Action:

None.

REQUEST

command

This message is informational.

OPREPLY 'reply'
Facility:

OPCOM

Explanation:
question.

This is the operator's reply to a user's request or

User Action:

Determined by the operator's reply.

OPRNDSYNX, operand syntax error
Facility:

VAX-11 MACRO assembler

Explanation:

An operand contained a syntax error.

User Action:

Correct the operand syntax.

2-189

MESSAGES

OPRNOTIF, operator notified, waiting ••
Facility:

'system time'

OPCOM

Explanation: A REQUEST command 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
and enter another message to the operator or press tTRL/Z)
cancel the request.

mRL~J

OPTVALOVR, too many characters in qualifier value
Facility:

BTRAN

Explanation: Too many characters were entered in a numeric value
specified for a qualifier value.
User Action: Use the HELP command or ref er to the VAX/VMS
Command Language _User._.~l]id~, if necessary, for the legal values
and reenter the command.

ORD, XABs not in correct order at 'location'
Facility:

VAX-11 RMS

Explanation: A sequence of allocation or key definition XABs is
not specified in ascending order of area IDs or key-of-reference
numbers.
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-11 RMS service was coded correctly.

ORG, invalid file organization value
Facility:

VAX-11 RMS

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-11 RMS service
coded correctly.

ORGNOTMAT, attemping to open file whose actual organization
match that declared
Facility:

does

was

not

COBOL (run-time}

Explanation: There is a mismatch between the organization of the
file as declared in the program and the organization of the file
as it was created. This mismatch was encountered on the OPEN
operation. The file status variable, if present, has been set to
94. No applicable USE procedure has been found.

2-190

MESSAGES
User Action: The user should examine the program and change the
declaration
of the file's organization to match the file
organization attributes (sequential, relative or indexed) when
the file was initially created.
OUTCONERR, output conversion error
Facility:

FORTRAN (run-time)

Explanation: During a formatted output operation the value of a
particular number could not be output in the specified field
length without loss of significant digits. The field is filled
with asterisks.
User Action: Check the program output to determine the field
that could not be properly converted for output and check the
field widths in the associated format or the value of the 1/0
list expression to determine which was in error.
OUTOF_DAT, out of data
Facility:

BASIC (run-time)

Explanation: A READ statement requested additional data from
exhausted DATA list. This is a fatal error.

User Action: Remove the READ statement,
reduce the number
variables in the READ statement, or supply more DATA items.

OUTSTAOVE, output statement overflows record
Facility:

FORTRAN (run-time)

Explanation: An output statement attempted to transfer more data
than would fit in the maximum record size.
User Action: Either reduce the width of the fields in the
associated format,
break the record in two with the format
specification, or change the record size specification in the
OPEN statement or internal file variable declaration.
OVERLAY, file-spec being overwritten
Facility:

Shared by several facilities

Explanation:

A file is being successfully overwritten.

User Action:

None.

This message is informational.

OVRDSKQUOTA, disk usaqe exceeds disk quota
Facility:

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

2-191

MESSAGES
OVRFLW, value overflow
Facility:

VAX/VMS Command Language Interpreter

Explanation: A data value specified is larger than the area
defined to receive it;
for example, a DEPOSIT command requested
that a value larger than a byte be deposited in a byte.
User Action: Verify the value and the area to
correct one or the other and reenter the command.

receive

it;

Explanation: The numeric string in a .PACKED directive had
than 31 digits.

PACTOOLONG, packed decimal string too long
Facility:

VAX-11 MACRO assembler

User Action:

Reduce the length of the decimal string.

PAGOWNVIO, page owner violation
Facility:

VAX/VMS system services

Explanation: This message is associated with a status code
returned from a system service request. An image attempted to
change a page in memory that is owned by a more privileged access
mode.
For example, an image executinq in user mode attempted to
delete a page owned by supervisor mode.
User Action:
ref erred to
access mode.

Check for a programming error. Verify that pages
in system service calls are owned by the calling

PAGRDERR, page read error, reason mask=xx,
PC=location, PSL=xxxxxxxx
Facility:

virtual

address=location,

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.
PARITY, parity error
Facility:

VAX/VMS System services

Explanation:
returned by
device.

This message is
I/O functions.

associated with a status code
The exact meaning depends on the

User Action: Action depends on the type of device to which the
I/O request was directed. For a list of parity errors associated
with individual device types, see the VAX/VMS I/O User's Guide.

2-192

MESSAGES
PARLENEXD, parameter block length exceeded
Facility:

Job controller

Explanation: This message is issued by the job controller if the
total number of characters enclosed in parentheses to specify the
parameters exceeds 95 characters.
User Action: Modify your program so that the total number of
characters
(including commas) enclosed in parentheses does not
exceed 95 characters.
PARMDEL, invalid parameter delimiter
Facility:

VAX/VMS Command Language Interpreter

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
grammatical error. Reenter the command.

for

spelling

PARSEFAIL, error parsing 'file-spec'
Facility:

Shared by several facilities

Explanation: An error
command or source line.
User Action:

was

detected

while

parsing

input

Correct the error.

PARTESCAPE, partial escape
Facility:

VAX/VMS system services

Explanation: This message is associated with a status code
returned by I/O functions.
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.
User Action: Check for a proqramming error. Note the condition.
Modify the source program, if necessary, to detect and respond to
the condition.
PASSCRD, password card syntax error 'string'
Facility:

Job controller

Explanation: A syntax of a PASSWORD card submitted in a card
reader batch job is invalid. The rejected portion of the card is
displayed in the message.
User Action:

Correct the PASSWORD card and resubmit the job.

2-193

MESSAGES

PBF, invalid prompt buffer
Facility:

VAX-11 RMS

Explanation: The prompt buffer address of the RAB
area of memory that cannot be read by the caller.

specifies

User Action: Verify that the call to the VAX-11 RMS service was
coded correctly.
Specifically, check the address specified for
the prompt buffer.

PENDING, asynchronous operation pending completion
Facility:

VAX-11 RMS

Explanation: The program requested a VAX-11 RMS asynchronous I/O
operation;
the operation has been initiated but has not yet
completed.
User Action:

None.

The message is informational.

PIP -- allocation failure on output file
Facility:

Peripheral Interchange Program

Explanation: The output volume does not contain sufficient space
for the file being copied.
User Action: Delete any files that are no longer needed on the
output volume, and reenter the command. Also, use DSCl or DSC2
to compress the files on the volume, if necessary.

PIP -- allocation failure - no contiguous space
Facility:

Peripheral Interchange Program

Explanation: The output volume does not contain sufficient space
for the file being copied.
User Action: Delete any files that are no longer needed on the
output volume, and reenter the command line. Also, use DSCl or
DSC2 to compress files on the volume, if necessary.

PIP -- allocation failure - no space available
Facility:

Peripheral Interchange Program

2-194

MESSAGES
PIP -- bad use of wild cards in destination file name
Facility:

Peripheral Interchange Program

Explanation:
name.

A wild card (*) was specified for

User Action: Reenter the command line
file explicitly specified.

with

the

output
proper

file
output

PIP -- cannot find directory file
Facility:

Peripheral Interchange Program

Explanation:
volume.

The directory name specified does not exist on this

User Action: Reenter the
command
directory name or the correct volume.

the

specifying

correct

PIP -- cannot rename from one device to another
Facility:

Peripheral Interchange Program

Explanation: You attempted to
renamed file on another device.

rename

file

and

place

the

User Action: Reenter the command line, renaming the file on the
input volume.
Then, enter another command to transfer the file
to the intended volume.
PIP -- close failure on input file
Facility:

Peripheral Interchange Program

Explanation: The input file could not be properly
file is locked to indicate possible corruption.

closed.

The

User Action: Reenter the command line. If the error recurs, run
a validity check on the file structure using VFYl or VFY2.
PIP -- close failure on output file
Facility:

Peripheral Interchange Program

Explanation: The output file could not be properly closed.
file is locked to indicate possible corruption.

The

User Action: Reenter the command line. If the error recurs, run
a validity check on the file structure using VFYl or VFY2.
PIP -- command syntax error
Facility:

Peripheral Interchange Program

Explanation:

There is an error in the command line.

User Action: Reenter the command. For further information about
the command syntax, refer to the VAX/VMS Command Language User's
Guide.
2-195

MESSAGES
PIP -- device not mounted
Facility:

Peripheral Interchange Program

Explanation: The device is not mounted, or another
mounted the device to contain a private volume.
User Action:

user

has

Mount the device, and reenter the command.

PIP -- directory write protected
Facility:

Peripheral Interchange Program

Explanation: The command could not remove an entry from a
directory because the device is write-protected or because of a
privilege violation.
User Action: Enable the unit for write operations, or
owner of the directory change its protection.

have

the

PIP -- error from parse
Facility:

Peripheral Interchange Program

Explanation:

The specified directory does not exist.

User Action: Reenter
directory name.

the

command

specifying

the

correct

PIP -- failed to attach output device
Facility:

Peripheral Interchange Program

Explanation: An attempt to attach a record-oriented output
device has failed. This error usually is caused by the device's
being of fline.
User Action: Ensure that the device is online
command line.

and

reenter

the

PIP -- failed to delete file
Facility:

Peripheral Interchange Program

Explanation:

You attempted to delete a protected file.

User Action:
the file.

Request the file owner to change the protection

PIP -- failed to delete storage bitmap
Facility:

Peripheral Interchange Program

Explanation:
storage bit
violation.

The command could not read the specified volume's
map.
This error usually is caused by a privilege

User Action: Request the volume owner to change
on the volume.

2-19n

the

protection

MESSAGES
PIP -- failed to detach output device
Facility:

Peripheral Interchange Program

Explanation: An attempt to detach an output device has failed.
This error usually is caused by the device's being offline.
User Action: Ensure that the device is online
command line.

and

reenter

the

PIP -- failed to enter new file name
Facility:

Peripheral Interchange Program

Explanation: You have specified a file that already exists in
the directory file,
or you do not have access to the specified
directory file.
User Action: Reenter the command line specifying the correct
file name and directory name, or request the directory owner to
change its protection.
PIP -- failed to find files
Facility:

PIP

Peripheral Interchange Program

Explanation: The file(s) specified in the command line were
found in the designated directory.

not

User Action: Reenter the command
specification and directory name.

file

specifying

the

correct

failed to mark file for delete
Facility:

Peripheral Interchange Program

Explanation:

You attempted to delete a protected or locked file.

User Action: Request the owner
protection or unlock the file.

the

file

change

its

you

not

PIP -- failed to read attributes
Facility:

Peripheral Interchange Program

Explanation: The volume specified is corrupted, or
have access to the file.

User Action: Ensure that you are allowed access to the file.
If
you do have access to it, use VFYl or VFY2 to determine whether
the volume is corrupted.

2-197

MESSAGES
PIP -- failed to remove directory entry
Facility:

Peripheral Interchange Program

Explanation: The command could not remove an entry from a
directory because the unit was write-protected, or a privilege
violation was detected.
User Action: Enable the unit for write operations,
the owner of the directory to change its protection.

request

PIP -- failed to restore original directory entry - file is lost
Facility:

Peripheral Interchange Program

Explanation: The command has removed a file from a directory,
failed to enter it in another directory, and failed to replace
the original directory entry.
User Action: Use the lost check
recover the file.

feature

VFYl

VFY2

PIP -- failed to write attributes
Facility:

Peripheral Interchange Program

Explanation: The volume is corrupted or you do
access to the volume.

not

have

writs

User Action: Determine whether you are allowed access to the
file.
If you are allowed access to the file, run VFYl or VFY2 to
verify the volume in question and determine the extent of the
corruption.
PIP -- file is lost
Facility:

Peripheral Interchange Program

Explanation: The command has removed
directory, failed to delete it, and
directory entry.

the
file
failed to

from
its
restore the

User Action: Run the lost
recover the file.

check

option

VFYl

VFY2

PLP -- file not locked
Facility:

Peripheral Interchange Program

Explanation:

You attempted to unlock a file that is not locked.

User Action:
name.

Reenter the command

2-198

specifying

the

correct

file

MESSAGES
PIP -- illegal
Facility:

* copy to same device and directory
Peripheral Interchange Program

Explanation: You attempted to copy all versions of a file
the same directory that is being scanned for input files.
operation results in an infinite number of copies of the
file;
therefore, it is not allowed.
User Action: Rename the files, or copy
directory, and reenter the command.

them

into

into
This
same

different

PIP -- illegal use of wild card version
Facility:

Peripheral Interchange Program

Explanation: The use of a wild
attempted operation results in
output.

card version number in the
inconsistent or unpredictable

User Action: Reenter the command line with different options
with an explicit or default version number.

PIP -- I/O error on input file
Facility:

Peripheral Interchange Program

Explanation:

One of the following conditions may exist:

•

The device is not online.

•

The volume is not mounted.

•

The hardware has failed.

•

The input file is corrupted.

User Action: Determine the condition that caused the message and
correct it. Reenter the command line.
PIP -- I/O error on output file
Facility:

Peripheral Interchange Program

Explanation:

One of the following conditions may exist:

•

The device is not online.

•

The device is not mounted.

•

The hardware has failed.

•

The volume is full.

•

The input file is corrupted.

User Action: Determine the condition that caused the message and
correct it. Reenter the command line.

2-199

MESSAGES
PIP -- no such file(s)
Facility:

Peripheral Interchange Program

Explanation: The file(s) specified in the command were not found
in the designated directory.
User Action:
command.

Check

the

file

specification,

and

reenter

the

PIP -- not a directory device
Facility:

Peripheral Interchange Program

Explanation: A directory-oriented command was issued to a device
that does not have directories, for example, a printer.
User Action: Reenter
directory name.

the

command

line

without

specifying

PIP -- only [*,*] is legal as destination uic
Facility:

Peripheral Interchange Program

Explanation: A directory name contains explicitly
portions where only wild cards are allowed.

specified

User Action: Reenter the command specifying only wild
the directory name.

cards

PIP -- open failure on input file
Facility:

Peripheral Interchange Program

Explanation: The specified file could not be opened.
following conditions may exist:

One of the

•

The file is protected against access.

•

The physical device has a problem, for example, the device
cycled down.

•

The volume is not mounted.

•

The specified directory does not exist.

•

The named file does not exist in the specified directory.

User Action: Determine the condition that caused the message and
correct it. Reenter the command.
PIP -- open failure on output file
Facility:

Peripheral Interchange Program

Explanation: The specified file could not be opened.
following conditions may exist:
•

The file is protected against access.

2-200

One of the

MESSAGES
•

The physical device has a problem, for example, the device
cycled down.

•

The volume is not mounted.

•

The specified directory does not exist.

•

The named file does not exist in the specified directory.

User Action: Determine the condition that caused the message and
correct it. Reenter the command.
PIP -- output file already exists -- not superseded
Facility:

PIP

Peripheral Interchange Program

Explanation: An output file of the same name,
version as the specified file already exists.

file

User Action:
number.

default

Retry the command with a

version must be explicit or
Facility:

new

type,

and

version

Peripheral Interchange Program

Explanation: The version number of the specified
expressed explicitly or as a wild card (*).

file

User Action: Reenter the command line with
correctly expressed.

version

the

must

number

PES, partial escape sequence
Facility:

VAX-11 RMS

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:

VAX/VMS System Services

Explanation: The page fault monitor has already
for your process or group.

been

activated

User Action: Request the page fault monitor only once per
invocation, or wait until the other user finishes.

2-201

image

MESSAGES
PLG, error detected in file's prologue (reconstruct file)
Facility:

VAX-11 RMS

Explanation: The contents of the file have
because the file's prologue has been damaged.
User Action:

been

corrupted

Reconstruct the file.

PLV, unsupported prologue version
Facility:

VAX-11 RMS

Explanation: The version number field in the file's prologue
read on open indicates that the file cannot be processed by this
version of VAX-11 RMS.
User Action: Verify the version of VAX-11 RMS that
using, and use the correct version to process the fila.

you

are

file,

PMD, post-mortem dump, file-name
Facility:

RSX

Explanation:
requested.

VAX/VMS

User Action:

None.

created

post-mortem

dump

The message is informational.

POS, invalid key position (greater than MRS) in XAB at 'location'
Facility:

VAX-11 RMS

Explanation: The position of a key segment specified by the key
definition XAB at the specified address is greater than the
maximum record size specified for the file.
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-11 RMS service was coded correctly.
POWERFAIL, power failure occured
Facility:

VAX/VMS system services

Explanation: This message is associated with a status code
returned by I/O functions.
A power failure occurred while a
request was active or the device is powered down.
User Action:

If appropriate, rerun the program.

2-202

MESSAGES
PRCREAT, error creating process
Facility:

Job controller

Explanation: This message indicates an internal error in the job
controller.
The message can also indicate that the system was
overloaded when you attempted to log on.
User Action: If an internal error in the job controller is
suspected, collect as much information as possible and submit an
SPR. If the system was overloaded when you attempted to log on,
wait and log on when the system is not overloaded.
PRGERR, NICE process program error
Facility:

NIC

Explanation:

A software error occurred.

User Action:
an SPR.

Collect as much information as possible and

submit

PRIKEYOUT, primary key out of sequence
Facility:

BASIC (run-time)

Explanation: A sequential $PUT to an INDEXED file specifies a
PRIMARY KEY value lower than that of the preceding record. This
is a fatal error.
User Action:
file.

Sort the records before using

PUT

indexed

PRINTOUT, printer I/O error
Facility:

Job controller

Explanation: The device printing the print symbiont's
failed. The reason for the failure follows this message.
User Action:

QIO

Depends on the reason for the failure.

PRIUSIFOR, PRINT-USING format error
Facility:

BASIC (run-time)

Explanation: The program contains a PRINT USING statement
an invalid format string. This is a fatal error.
User Action:

Change the PRINT USING format string.

2-203

with

MESSAGES
PRIVINSTALL, shareable images must
image
Facility:

installed

run

privileged

VAX/VMS System Services

Explanation: This severe error message is associated with a
status code returned from a system service request. Shareable
images must be installed to run a privileged image.
User Action: Install all shareable
images installed with privileges.

images

used

executable

PROC_ID, identification of created process is process-id
Facility:

VAX/VMS Command Language Interpreter

Explanation: The RUN command successfully created a process.
This message does not indicate whether, when the process began
executing, the requested image was
started
or
completed
successfully.
The message displays the process
created process.
User Action:

None.

identification

number

the

The message is informational.

PROC_TRA, Programmable AC trap

Facility:

BASIC (run-time)

Explanation: A CTRL/C was typed
This is a fatal error.
User Action: None;
error handler.

the

however, you can trap

controlling

terminal.

this

error

with

your

program

PROLOSSOR, program lost-Sorry
Facility:

BASIC (run-time)

Explanation:
lost.

A fatal system error

caused

User Action:
an SPR.

Collect as much information as possible and

submit

PROTECTED, protection on file-spec changed to protection-string
Facility:

Shared by several facilities

Explanation: This message is associated with the execution of a
SET PROTECTION command.
The protection of the named file has
been changed to the value specified.
User Action:

None.

This message is informational.

2-204

MESSAGES
PROTINSTALL, protected images must be installed
Facility:

VAX/VMS System Services

Explanation: This severe error message is associated with a
status code returned from a system service request. Protected
images must be installed.
User Action: Use the /PROTECT qualifier to install
image that contains user-written system services.

shareable

PROTOCOL, network protocol error
Facility:

VAX/VMS System Services

Explanation: This severe error message is associated with a
status code returned from the system service request. An attempt
was made to initiate a DECnet logical link connection.
User Action: Notify your software specialist.
Refer
DECnet-VAX User's Guide for additional information.

the

PROVIO, protection violation
Facility:

BASIC (run-time)

Explanation: The program attempted to read or write to a file
whose protection code did not allow the operation. This is a
fatal error.
User Action: Use a different file, or
protection code or the attempted operation.

change

the

file's

PRV, insufficient privilege or file protection violation
Facility:

VAX-11 RMS

Explanation: The operating system protection applied to the file
restricts access to the file. The current process is denied the
type of privilege that was requested.
User Action: Verify the protection applied to the file,
and
change it if necessary.
If you are not the owner of the file,
request the file's owner to change the
protection.
The
DIRECTORY/FULL command displays a file's current protection. The
SET PROTECTION command can be used to change the protection.
PSECBUFOVF, PSECT context buffer overflow
Facility:

VAX-11 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.

2-205

MESSAGES

PSECBUFUND, PSECT context buffer underflow
Facility:

VAX-11 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
corresponds to a .SAVE PSECT directive.

directive

PSECOPCNFL, conflicting PSECT options
Facility:

VAX-11 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:
directive(s).

Correct

the

conflicting

values

the

.PSECT

full.

PSTFULL, process section table is full
Facility:

VAX/VMS System Services

Explanation: The section table in the process header
No more sections can be created for this process.

User Action: Relink the image, forcing fewer image sections,
reboot, increasing the SYSGEN parameter PROCSECTCNT.

PURGEVER, version numbers not permitted
Facility:

Shared by several facilities

Explanation: The command does not allow
file specification.
User Action: Reenter the command;
number for the file specification.

version
not

numbers

specify

version

PUSSTAOVE, pushdown stack overflow
Facility:

VAX-11 Run-Time Procedure Library

Explanation: This message is associated with a status code
returned from the Run-Time Library. The image pushdown stack
overflowed.
User Action: Use the debugger to determine whether the procedure
stack does not contain an excessive number of entries, or if an
infinite call loop has caused the stack to grow.

2-206

MESSAGES
PWDLOCKED, password was locked to prevent change
Facility:

VAX/VMS Command Language Interpreter

Explanation: This message is returned by the command line
interpreter for the SET PASSWORD command. The system manager has
restricted an account from changing its name. 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.
PWDNOTVAL, old password validation error - password unchanged
Facility:

VAX/VMS Command Language Interpreter

Explanation: This message is returned by the command line
interpreter for the SET PASSWORD command.
An old password
validation error has been 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
been forgotten, consult the system manager.

password

has

PWDNOTVER, new password validation error - password unchanged
Facility:

VAX/VMS Command Language Interpreter

Explanation: This message is returned by the command line
interpreter for the SET PASSWORD command. The new password was
not entered correctly 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:

VAX/VMS Command Language Interpreter

Explanation: An illegal password was used.
Legal passwords
consist of ASCII characters space (SP) through underscore ( ) ,
that is, 20 through SF (hexidecimal). Passwords must not exceed
31 characters in length.
Lowercase alphabetic characters are
connected to their uppercase equivalents within the legal range.
User Action: Reenter the password, using characters in the range
20 through SF (hexadecimal).
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 successful or the transfer completes.

2-207

MESSAGES
QFACTIVE, disk quota file is already active
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from an ACP QIO request. The quota file is already
active.
User Action:

Check the device specified and proceed.

QFNOTACT, disk quota file is not active
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a file system ACP QIO request. The quota file is
not active.
User Action: Check the device specified, or
device. Turn quotas on, if appropriate.

check

the

default

QUECNT, queue count is incorrect
Facility:

Job controller

Explanation:
controller.

This message indicates an internal error in the job

User Action:
an SPR.

Collect as much information as possiblB and

submit

QUEERR, create/map queue error
Facility:

Job controller

Explanation: This message indicates an internal error in the job
controller or a system failure.
User Action:
an SPR.

Collect as much information as possible and

submit

QUEJOBCRE, Job nnn entered on queue 'queue-name'
Facility:

VAX/VMS Command Language Interpreter

Explanation: The job controller successfully entered a job in a
system printer or batch job queue.
This message is usually
displayed without its message code.
User Action:

None.

The message is informational.

QUENOSTOP, queue not stopped for operation
Facility:

Job controller

Explanation: A device queue was not stopped before a
INITIALIZE request was issued f~r the queue.
User Action: Stop the queue or issue the STOP/NEXT
wait for the current job to complete.
2-208

DELETE

command

and

MESSAGES
QUEUPD, error updating queue file
Facility:

Job controller

Explanation: The $UPDSEC system service, used by the
job
controller to update the queue file to disk, returned an error
status.
User Action:
an SPR.

Collect as much information as possible and

submit

QUO, error in quoted string
Facility:

VAX-11 RMS

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 HELP command or refer to the VAX/VMS
Command Language User's Guide,
if necessary, for the correct
syntax and reenter the file specification.
QUOTAFAIL, failed to activate quota file;
Facility:

volume locked

MOUNT

Explanation: An error occurred that enabled the volume's quota
file;
the volume has been locked against allocation.
A
subsequent message describes the nature of the error.
User Action: Correct the problem
dismount and remount the volume.

with

the

quota

file.

Then

RAB, invalid RAB or RAB not accessible
Facility:

VAX-11 RMS

Explanation:
block for a
RAB is not in
caller.
An
operations to

The block identifier field of the record access
file does not indicate that this is a RAB. Or, the
an area of memory that can be written by the
attempt may have been made to perform record
a FAB.

User Action: Verify that the control block referred to is a RAB,
that the RAB was properly initialized, and that it has not been
inadvertently modified during the execution of the program.
RAC, invalid record access mode
Facility:

VAX-11 RMS

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-11 RMS service
coded correctly.

2-209

was

MESSAGES

RADRMOD, reserved addressing fault at PC location, PSL=xxxxxxxx
Facility:

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.

RANGE,

numeri~

Facility:

not within required range
NCP

Explanation:

A syntax error was detected.

User Action:

Reenter the information correctly.

RAT, invalid record attributes
Facility:

VAX-11 RMS

Explanation: The record attributes field of the FAB specified
for a create 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-11 RMS service
coded correctly.

was

RBF, invalid record buffer
Facility:

VAX-11 RMS

Explanation: The record buffer address of the RAB
area of memory that cannot be read by the caller.

specifies

User Action: Verify that the call to the VAX-11 RMS service
coded correctly.

was

RDDELDATA, read deleted data address mark
Facility:

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.

This message is informational.

2-210

MESSAGES
READERR, error reading input-file-spec
Facility:

Shared by several facilities

Explanation: An input file specified cannot be read.
This
message is usually accompanied by a VAX-11 RMS message indicating
the reason for the failure.
User Action: Take corrective action based on the associated
message.
Check that the file exists and that you have privilege
to read it.
REAINCOPE, READ on file incompatible with OPEN mode
Facility:

COBOL (run-time)

Explanation: The file was opened in a mode which is not
compatible with a READ operation (that is, an open mode for which
read operations are disallowed). This error usually represents
bad logic in the user program. The file status variable, if
present, has been set to 94. No applicable USE procedure has
been found.
User Action: The user should examine the logic of the program to
determine why a READ operation that is incompatible with the open
mode is being attempted. The user is advised to change the open
mode to allow the READ operation or to eliminate the READ
operation.
REASMAMIN, attempting READ of variable
allowed from file
Facility:

length

smaller

than

minimum

COBOL (run-time)

Explanation: An attempt was made to READ a record that is
smaller than the minimum length record declared in the program
for this file. The file status variable, if present, has been
set to 94. No applicable USE procedure has been found.
User Action: The user should examine the length of the record on
the file being read and subsequently change the minimum record
length declared in the program for this file to allow a
successful READ operation on this record.
REAUNOFIL, attempting READ on unopened file
Facility:

COBOL (run-time)

Explanation: A READ operation was attempted on a file that is
not open at this time. This error usually represents a logic
error in the user program. The file status variable, if present,
has been set to 94. No applicable USE procedure has been found.
User Action: The user should examine the logic of the program to
determine why a READ operation is attempted on an unopened file.
The user may wish to change the logic of the program by opening
the file or by eliminating the READ operation.

2-211

MESSAGES

RECACTPER, recursive activation of PERFORM
Facility:

COBOL (run-time)

Explanation: An attempt was made to PERFORM a paragraph or
section that is already activated due to a previous PERFORM
statement. This constitutes an attempted recursive activation of
the paragraph or section and is illegal in the COBOL language.
The program must execute an EXIT statement from the paragraph or
section before this paragraph or section can be the subject of a
subsequent PERFORM.
User Action: The user should examine the logic of the program to
determine why an EXIT from the paragraph or section is not being
executed before the subsequent PERFORM of the same paragraph or
section.

RECACTUSE, recursive activation of USE procedure
Facility:

COBOL (run-time)

Explanation: An attempt was made to activate, that is, enter a
USE procedure while that USE procedure is already active. USE
procedures are activated in response to an error or condition
associated with an I/O operation. Another I/O operation has been
attempted within the USE procedure. This I/O operation caused
the USE procedure to be recursively entered again before exiting
from the initial entry to the procedure.
This
recursive
activation of the USE procedure is illegal in the COBOL language.
User Action: The user should examine the logic of the program to
determine the condition that causes the recursive activation of
the USE procedure and then eliminate that condition.

RECADD, new database record added
Facility:

NCP

Explanation:

The addition was completed successfully.

User Action:

None.

RECALREXI, record already exists
Facility:

BASIC (run-time)

Explanation: An attempted random access PUT on a relative file
has encountered a pre-existing record. This is a fatal error.
User Action: Specify a different record number for
delete the record.

the

PUT

RECATTNOT, record attributes not matched
Facility:

BASIC (run-time)

Explanation: A RECORDTYPE clause specifies file attributes
do not match those of the file. This is a fatal error.
User Action:
the file.

Change the RECORDTYPE attribute to

2-212

match

that

that
of

MESSAGES
RECBUCLOC, record/bucket locked
Facility:

BASIC (run-time)

Explanation: The program attempts to access a record or bucket
that has been locked by another program. This is a fatal error.
user Action:

Retry the operation.

RECFILTOO, record on file too big
Facility:

BASIC (run-time)

Explanation: The specified record
buffer. This is a fatal error.
User Action:

longer

than

the

input

Increase the input buffer's size.

RECGTRBL, record size is greater than block size
Facility:

MOUNT

Explanation: The record size specified is greater than the block
size (specified or defaulted).
User Action:
size.

larger

block

Explanation: A record previously located by its Record
Address (RFA) has been deleted. This is a fatal error.

File

RECHAS~EE,

Specify a smaller record size

record has been deleted

Facility:

BASIC (run-time)

User Action:

None.

RECIOOPE, recursive I/O operation
Facility:

FORTRAN (run-time)

Explanation: While processing an I/O statement for a logical
unit, another I/O operation on the same logical unit was
attempted. One of the following conditions may have occurred:
•

A function subroutine that performs I/O to the same logical
unit is referenced in an expression in an I/O list or variable
format expression.

•

An I/O statement was
logical unit.

•

An exception handler (or a procedure it called) executed an
I/O statement in response to a SIGNAL from an I/0 statement
for the same logical unit.

execuied

AST

level

for

the

same

User Action: Locate the statement in your program that caused
the recursive I/O operation and correct the program logic or
specify a different logical unit number for one
of
the
operations.

2-213

MESSAGES

RECLNG, illegal record length
Facility:

Librarian

Explanation: This error message is generated by
routines. The record length exceeds 512 bytes.

the

Librarian

RECLNG, illegal record length nnn in module 'module-name' in
file-spec'

'library

User Action:

Facility:

Reformat the module.

LIBRARY

Explanation: This error message is 9enerated by the LIBRARY
command.
The specified module contains records that exceed the
maximum record length of 512 bytes.
User Action: Correct the
module in the library.

record

length

before

inserting

the

RECLOCDEL, record on file is already locked (DELETE attempt)
Facility:

COBOL (run-time)

Explanation: In the file sharing environment, an attempt was
made to DELETE a record already locked by another, contending
process. The file status variable, if present, has been set to
92. No applicable USE procedure has been found.
User Action: The user should code an applicable USE procedure in
which the problem of record contention may be handled properly by
the user's own program. The utilization of USE procedures is
important in the file sharing environment.

RECLOCREA, record on file is already locked (READ attempt)
Facility:

COBOL (run-time)

Explanation: In the file sharing environment, an attempt was
made to READ a record already locked by another, contending
process. The file status variable, if present, has been set to
92. No applicable USE procedure has been found.
User Action: The user should code an applicable USE procedure in
which the problem of record contention may be handled properly by
the user's own program. The utilization of USE procedures is
important in the file sharing environment.

RECLOCREW, record on file is already locked (REWRITE attempt)
Facility:

COBOL (run-time)

Explanation: In the file sharing environment, an attempt was
made to REWRITE a record already locked by another, contending
process. The file status variable, if present, has been set to
92. No applicable USE procedure has been found.

2-214

MESSAGES
User Action: The user should code an applicable USE procedure in
which the problem of record contention may be handled properly by
the user's own program. The utilization of USE procedures is
important in the file sharing environment.
RECLOCSTA, record on file is already locked (START attempt}
Facility:

COBOL (run-time}

Explanation: In the file sharing environment, an attempt was
made to perform a START operation on a record already locked by
another, contending process.
The file status variable, if
present, has been set to 92. No applicable USE procedure has
been found.
User Action: The user should code an applicable USE procedure in
which the problem of record contention may be handled properly by
the user's own program. The utilization of USE procedures is
important in the file sharing environment.
RECLOCWRI, record on file is already locked (WRITE attempt}
Facility:

COBOL (run-time}

Explanation: In the file sharing environment, an attempt was
made to WRITE a record already locked by another, contending
process. The file status variable, if present, has been set to
92. No applicable USE procedure has been found.
User Action: The user should code an applicable USE procedure in
which the problem of record contention may be handled properly by
the user's own program. The utilization of USE procedures is
important in the file sharing environment.
RECNOTFOU, record not found
Facility:

BASIC (run-time}

Explanation: A random access GET or FIND was attempted
deleted or nonexistent record. This is a fatal error.
User Action:

None.

This message is informational.

RECNUMEXC, RECORD number exceeds maximum
Facility:

BASIC (run-time}

Explanation: The specified record number exceeds
specified for this file. This is a fatal error.

the

maximum

User Action: Reduce the specified record number.
The maximum
record number cannot be specified in BASIC;
it is either a
default, or it was specified by a non-BASIC program when the file
was created.

2-215

MESSAGES

RECNUMOUT, record number outside range
Facility:

FORTRAN (run-time)

Explanation: A direct access READ, WRITE, or FIND statement
specified a rec~rd number outside the range specified when the
file was created.
User Action: Check that the direct access operation specified
the correct record number and check that the logical unit number
specified in the I/O statement agrees with the logical unit
number in the OPEN statement.

RECTRUNC, record truncated
Facility:

Librarian

Explanation: This warning message is generated for a librarian
routine. The buffer supplied in the routine is too small for the
record.
User Action:
record.

Supply a sufficiently large buffer to

contain

the

RECTYP, illegal record type 'type' in module 'module-name' in 'library
file-spec'
Facility:

LIBRARY

Explanation: This error message is generated by the LIBRARY
command.
The specified object module contains an illegal record
type.
User Action:
string.

Recompile

the

module

and

reenter

the

command

RECUPD, current database record updated
Facility:

NCP

Explanation:

The update operation completed successfully.

User Action:

None.

REDARR, redimensioned array
Facility:

BASIC (run-time)

Explanation: The program attempted to redimension an
have more elements than were originally dimensioned.
fatal error.

array to
This is a

User Action: Change the statement that attempts the
or increase the original number elements.

redimension

2-216

MESSAGES
REF, invalid key-of-reference in XAB at 'location'
Facility:

VAX-11 RMS

Explanation: The key-of-reference number specified in the key
definition XAB at the specified address 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 address of the XAB in error. Verify that the call to the
VAX-11 RMS service was coded correctly.
REFPRVENTR, reference previously entered in table
Facility:

CREF

Explanation: A call to LIB$CRF_INS_REF
previously inserted reference.
User Action:

None.

was

performed

with

The new reference is ignored.

REGMSG, 'string'
Facility:

RSX

Explanation:

The register contents at termination are printed.

User Action:

None.

REGOPSYNX, register operand syntax error
Facility:

VAX-11 MACRO assembler

Explanation:

The addressing mode syntax contained an error.

User Action:

Correct the addressing mode syntax.

REJECT, network connect rejected
Facility:

VAX/VMS System Services

Explanation: A request to connect to an object at a remote
failed for one of the following reasons:
1.

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
to correct the condition.

~-217

and

node

try

MESSAGES

RELCONCAT, relative file cannot be concatenated
Facility:

Shared by several facilities

Explanation: A
another file.
User Action:

relative

file

may

not

concatenated

with

Use a program to load the relative file.

RELINK, obsolete image header - please relink
Facility:

VAX/VMS System Services

Explanation: This severe error message is associated with a
status code returned from a system service request. An obsolete
image header was detected.
User Action:

Relink the image.

REMOTE, assignment completed on remote node
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a system service request. An assignment for a
transparent connect on a remote node completed successfully.
user Action:

None.

This message is informational.

REMOVED, symbol 'symbol name' removed from 'library file-spec'
Facility:

LIBRARY

Explanation:
command.

This success message is generated

User Action:

None.

the

LIBRARY

This message is informational.

REMRSRC, resource error at remote node
Facility:

VAX/VMS System Services

Explanation: This severe error message is associated with a
status code returned from a system service request. An attempt
was made to initiate a DECnet 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
DECnet-VAX User's Guide for additional information.

2-218

MESSAGES

RENAMED, 'file-spec' renamed to 'file-spec'
Facility:

Shared by several facilities

Explanation: This message is associated with the execution of a
RENAME command.
The name of the first file was changed to the
name given in the second file specification.
User Action:

None.

This message is informational.

REPLACED, module 'module name' replaced in 'library file-spec'
Facility:

LIBRARY

Explanation:
command.

This success message is generated

User Action:

None.

the

LIBRARY

This message is informational.

REPLACED, output-file-spec being replaced
Facility:

Shared by several facilities

Explanation:
version.

An output file is successfully replaced

User Action:

None.

new

This message is informational.

REQPRMABS, required parameter is absent
Facility:

VAX/VMS Command Language Interpreter

Explanation: This message is associated with an internal status
code returned by the command interpreter's result parse routine.
It indicates to the caller that not all parameters are present.
The operating system does not normally display this message.
User Action: Note the condition. Mod.ify your source program, if
necessary, to detect and respond to the condition.

RER, file read error
Facility:

VAX-11 RMS

Explanation: Either VAX-11 RMS could not read an input file,
a terminal read error occurred.

User Action:
If VAX-11 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.

2-219

MESSAGES
RESERVED, compatibility mode reserved instruction
Facility:

RSX

Explanation: An RSX-llM image attempted to execute one of the
following instructions that are not allowed in compatibility
mode:
HALT, WAIT, RESET, SPL, MARK
The PC contains the address of the instruction that caused the
error.
In
RSX-llM, the PC contains the address of the
instruction following the erroneous instruction.
This message
corresponds
to
the
RSX-llM
termination message RESERVED
INSTRUCTION.
User Action: Determine the instruction or statement at which the
error occurred and correct the error.
RESIGNAL, resignal condition to next handler
Facility:

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.

The message is informational.

RESNO_ERR, RESUME and no error
Facility:

BASIC (run-time)

Explanation: The program executed a RESUME statement outside
the error handling routine. This is a fatal error.
User Action: Check program logic to make sure that
statement is executed only in the error handler.

the

RESUME

RESULTOVF, resultant string overflow
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a system service request. 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-220

MESSAGES
RETWITGOS, RETURN without GOSUB
Facility:

BASIC (run-time)

Explanation: The program executes a RETURN
GOSUB. This is a fatal error.

statement

before

User Action: Check program logic to make sure that RETURN
statements are executed only in subroutines, or remove the RETURN
statement.
REWERR, REWIND error
Facility:

FORTRAN (run-time)

Explanation:

One of the following conditions occurred:

•

The file was not a sequential organization file.

•

The file was not opened for sequential or append access.

•

RMS detected an error condition during execution of
statement.

REWIND

User Action: Verify that the file specified is sequential
organization and that it is open for sequential access. Or, take
corrective action based on the VAX-11 RMS message.
REWINCOPE, REWRITE on file incompatible with OPEN mode
Facility:

COBOL (run-time)

Explanation: The REWRITE operation is not compatible with the
open mode of the file. The file status variable, if present, has
been set to 94. No applicable USE procedure has been found.
User Action: The user should examine the mode in which the file
was opened prior to the attempted REWRITE operation and change
the open mode to allow the successful completion of the REWRITE
operation.
Alternatively, the user may change the logic of the
program to bypass the attempted REWRITE operation.
REWNO_R_S, attempting REWRITE on file with no previous READ or START
Facility:

COBOL (run-time)

Explanation: An attempt was made to perform a REWRITE on this
file
without having previously performed a READ or START
operation. The file status variable, if present, has been set to
93. No applicable USE procedure has been found.
User Action: The user program must execute a READ or START
operation (that is, in sequential access mode) immediately before
executing the REWRITE operation.
This must occur for each
execution of the REWRITE operation.

2-221

MESSAGES

REWRITERR, REWRITE error
Facility:

FORTRAN (run-time)

Explanation: RMS detected an error condition during execution of
a REWRITE statement.
user Action: Take corrective
VAX-11 RMS message.

action

based

the

associated

REWSMAMIN, attempting REWRITE of variable length smaller than
allowed on file
Facility:

minimum

COBOL (run-time)

Explanation: An attempt was made to REWRITE a record that is
smaller than the minimum record length declared in the program
for this file. The file status variable, if present, has been
set to 94. No applicable USE procedure has been found.
User Action: The user should examine the length of the record on
the file being rewritten and subsequently change the minimum
record length attribute in the program for the file to allow the
successful REWRITE operation for this record.

REWUNOFIL, attempting REWRITE on unopened file
Facility:

COBOL (run-time)

Explanation: An attempt was made to perform a REWRITE operation
on this file before the file is opened.
The file status
variable, if present, has been set to 94.
No applicable USE
procedure has been found.
User Action: The user should examine the logic of the program to
determine why a REWRITE operation is attempted before the file is
opened. The user may wish to change the logic of the program to
open the file or, alternatively, to eliminate the REWRITE
operation.

REX, record already exists
Facility:

VAX-11 RMS

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.

RFA, invalid record's file address (RFA)
Facility:

VAX-11 RMS

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-11 RMS service
coded correctly.
2-222

was

MESSAGES

RFAPASTEOF, VBN in map block request past EOF
Facility:

Librarian

Explanation: This error message is generated by the Librarian
routines. An unexpected internal consistency check occurred.
User Action:

Inform your system manager and submit an SPR.

RFM, invalid record format
Facility:

VAX-11 RMS

Explanation: The record format field of the FAB does not contain
a valid value.
User Action: Verify that the call to the VAX-11 RMS service was
coded correctly.
The valid values for this field are FIX, VAR,
VFC, and UDF.

RHB, invalid record header buffer
Facility:

VAX-11 RMS

Explanation: The record header buffer address of the
RAB
specifies an area of memory that cannot be accessed by the
caller.
User Action: Verify that the call to the VAX-11 RMS service
coded correctly.

was

RLF, invalid related NAM block
Facility:

VAX-11 RMS

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.
User Action: Verify that the call to the VAX-11 RMS service
coded correctly.

was

RLK, target record currently locked by another stream
Facility:

VAX-11 RMS

Explanation:

The target record is locked by another stream.

User Action: Note the condition. Modify the source program,
necessary, to detect and respond to the condition.

RMSERR, record io error on file 'file-spec'
Facility:

NCP

Explanation:

A read or a write to file failed.

User Action:

Ensure that the disk drive is functioning properly.

2-223

MESSAGES

RMSERROR, RMS service error
Facility:

Shared by several facilities

Explanation: An error was encountered during a VAX-11 RMS
operation.
A
subsequent message explains the reason for the
error.
User Action: Retry the operation;
consult the VAX-11 Record
Management Services Reference Manual for more information.

RMV, ACP remove function failed
Facility:

VAX-11 RMS

Explanation: This message is associated with a status code
returned from a file system ACP QIO request made by VAX-11 RMS.
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:

VAX-11 RMS

Explanation: A requested record could not be located in a $FIND
Either the
or $GET operation on a relative or indexed file.
record was never written or has been deleted.
User Action: Note the condition. Modify the source program,
necessary, to detect and respond to the conditiqn.

RNL, record not locked
Facility:

VAX-11 RMS

Explanation: The record specified for
$RELEASE operation was not locked.

VAX-11

RMS

$FREE

User Action: Note the condition. Modify the source program,
necessary, to detect and respond to the condition.

ROP, invalid record options
Facility:

VAX-11 RMS

Explanation: An illegal record option was specified;
for
example, EOF was specified for a connect operation for a relative
file.
User Action: Verify that the call to the VAX-11 RMS service
coded correctly.

2-224

was

MESSAGES
ROPRAND, reserved operand fault at PC location, PSL=xxxxxxxx
Facility:

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
virtual address displayed in the message to determine
instruction that caused the error.

and
the

RPL, error detected while reading prologue
Facility:

VAX-11 RMS

Explanation: An I/O error occurred during an attempt to read the
file's prologue.
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:

VAX-11 MACRO assembler

Explanation: The repeat count in a .BYTE,
.WORD,
.LONG,
.SIGNED BYTE, or .SIGNED WORD directive contained an undefined
symbol or was a relative expression.
User Action: Replace the expression with an absolute
that does not contain any undefined symbols.

expression

RQSTABORT, request aborted
Facility:

OPCOM

Explanation:
command.

An operator request was denied by

User Action:

None.

the

REPLY/ABORT

This message is informational.

RQSTCAN, request was canceled
Facility:

OPCOM

Explanation:

An operator request was successfully canceled.

User Action:

None.

This message is informational.

RQSTCMPLTE, request complete
Facility:

OPCOM

a
user's
Explanation: An operator has completed
successfully;
the user/operator dialogue is complete.
User Action:

None.

This message is informational.
2-225

request

MESSAGES

RQSTPEND, request pending
Facility:

OPCOM

Explanation: An operator responded to a user's request with the
REPLY/PENDING command. 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.

RRV, invalid RRV record encountered
Facility:

VAX-11 RMS

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-11 RMS or system
software error.
User Action: Reorganize the file.
If a software error is
suspected, collect as much information as possible and submit an
SPR.

RRVNOTFUL, RRV not fully updated
Facility:

BASIC (run-time)

Explanation: RMS wrote successfully, but did not update one or
more Record Retrieval Vectors. Therefore, you cannot retrieve
any records associated with those vectors.
This is a fatal
error.
User Action:

Delete the record and rewrite it.

RSA, record stream currently active
Facility:

VAX-11 RMS

Explanation: An attempt was made to issue a VAX-11 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.

RSL, invalid resultant string length
Facility:

VAX-11 RMS

Explanation: The VAX-11 RMS NAM block contains an invalid value
in the result string length field for an operation in which this
field is a required input. This field is generally filled in on
return from a $CREATE, $OPEN, or $SEARCH operation.
User Action: Verify that the call to the VAX-11 RMS service
coded correctly.

2-22n

was

MESSAGES
RSLOVF, result parse buffer overflow
Facility:

VAX/VMS Command Language Interpreter

Explanation: The buffer used by the command interpreter to store
a command string during parsing has overflowed.
User Action:

Simplify the command.

RSS, invalid resultant string size
Facility:

VAX-11 RMS

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-11 RMS operation.
User Action: Verify that the call to the VAX-11 RMS service
coded correctly.

was

RST, invalid resultant string address
Facility:

VAX-11 RMS

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-11 RMS service
coded correctly.

was

RSZ, invalid record size
Facility:

VAX-11 RMS

Explanation: The record size (RSZ) field of the RAB contains
invalid value for one of the following reasons:

•

The record size value is greater than the maximum record
specified for the file.

•

The record size value is not the correct size for fixed length
records.

•

The record size value is not large
primary key for an indexed file.

•

The record size value was different than the original
size of a $UPDATE operation on a sequential file.

enough

size

contain

the

record

The maximum record size value must be in the range of 1 through
327n7
for the $PUT and $UPDATE services, and in the range of 1
through n5535 for the $WRITE service.
User Action: Verify that the call to the VAX-11 RMS service
coded correctly.

2-227

was

MESSAGES
RTB, nnn byte record too large for user's buffer
Facility:

VAX-11 RMS

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.

RVNlNOTMT, root volume is not mounted
Facility:

MOUNT

Explanation: The root volume for the volume set specified in the
MOUNT/BIND command 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:

VAX-11 RMS

Explanation: VAX-11 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-11 RMS RRV updating. All records are
accessible by primary key only.
RRV errors may subsequently
occur.
User Action:

Reorganize the file.

SCAFACINT, SCALE factor interlock
Facility:

BASIC (run-time}

Explanation: A subprogram was compiled with a different
factor than the calling program. This is a fatal error.

SCALE

User Action: Recompile one of the programs with a
that matches the other.

factor

scale

SCTERR, error searching SCT
Facility:

Job controller

Explanation:
controller.

This message indicates an internal error in the job

User Action:
an SPR.

Collect as much information as possible and

2-228

submit

MESSAGES
SEARCHFAIL, error searching for 'file-spec'
Facility:

Shared by several facilities

Explanation: The specified file could
subsequent error message explains why.
User Action:

not

found.

None.

SECTBLFUL, section table (process/global) is full
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a system service request.
The system space
no
allocated to maintain information about sections is full;
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.
SEG, data types other than string limited to one
'location'
Facility:

segment

XAB

VAX-11 RMS

Explanation: The number of key elements specified by the key
definition XAB at the specified address is greater than one and
the key data type is not STG.
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-11 RMS service was coded correctly.
SEGRECFOR, segmented record format error
Facility:

FORTRAN (run-time)

Explanation: An invalid segmented record control data word was
detected in an unformatted sequential file.
The file was
probably created with RECORDTYPE='FIXED' or 'VARIABLE' in effect,
or was written by a language other than FORTRAN.
User Action: Locate the I/O statement that caused the error and
check that the correct logical unit number was specified. If no
RECORDTYPE is specified for an unformatted sequential file,
segmented records are assumed.

2-229

MESSAGES

SEQ, primary key out of sequence (SEQ access)
Facility:

VAX-11 RMS

Explanation: A VAX-11 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,
necessary, to detect and respond to the condition.

SEQNCE, illegal record sequence in module
file-spec'
Facility:

'module-name'

'library

LIBRARY

Explanation: This error message is generated by the LIBRARY
command.
The object module you want to insert is illegally
formatted.
User Action: Recompile the object
into the library.

module

before

inserting

SETLIMIT, too many volumes on volume set
Facility:

MOUNT

Explanation: The maximum permissible
volume set (255) has been reached.
User Action:
first.

Find the other volumes in

number

volumes

the

set

and

them

use

SHARTOOBIG, new version of shareable image too big - relink all images
Facility:

VAX/VMS System Services

Explanation: This severe error message is associated
status code returned from a system service request.
version of a shareable image is too big.
User Action:

with a
The new

Relink all images.

SHMGSNOTMAP, shared memory global section not mapped during creation
Facility:

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
Set RELPAG to zero.

2-230

section.

MESSAGES
SHMNOTCNCT, shared memory not connected
Facility:

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
common event flag cluster, mailbox, or global section names.
User Action:

Connect the shared memory.

SHR, invalid file sharing (SHR) options
Facility:

VAX-11 RMS

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-11 RMS service
coded correctly.

was

SHRIDMISMAT, ident mismatch with shareable image
Facility:

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.

SIZ, invalid key size in XAB at 'location'
Facility:

VAX-11 RMS

Explanation: An invalid key size was specified in the key
definition XAB at the specified location. The size is invalid
for one of the following reasons:

• I t is greater than 255.
• I t is 0 for a key data type STG.
• I t is greater than lh for a key data type PAC.
• It is other than 0 or 2 for key data types BN2 and IN2.
• It is other than 0 or 4 for key data types BN4 and IN4.
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-11 RMS service was coded correctly.

2-231

MESSAGES
SIZRECINV, size of record invalid
Facility:

BASIC (run-time)

Explanation: The program contains a COUNT specification that
invalid because:

•

COUNT equals zero.

•

COUNT exceeds the maximum size of the record.

•

COUNT conflicts with the actual size of
during a sequential file UPDATE on disk.

current

record

•

COUNT does not equal the maximum record size for fixed
records.

format

the

This is a fatal error.
User Action:

Supply a valid COUNT value.

SKPDAT, data records encountered by system were ignored
Facility:

VAX/VMS Command Language Interpreter

Explanation: A command procedure contained lines that were not
DCL commands (that is, the lines did not begin with dollar signs)
and that were not preceded by commands requiring input data. 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.
SMINVOPR, operation not properly requested
Facility:

Job controller

Explanation: A symbiont manager request is not in the proper
format.
This message is associated with a status code returned
by the job controller. The operating system does not normally
display this message.
User Action: Check for a programming error.
Verify that the
call to the service was coded correctly. See the VAX/VMS System
Services Reference Manual for coding specifications.
SMINVOPT, invalid option code
Facility:

Job controller

Explanation: A symbiont manager request specified an invalid
option.
This message is associated with a status code returned
by the job controller. The operating system does not normally
display this message.
User Action: Check for a programming error.
Verify that the
call to the service was coded correctly. See the VAX/VMS System
Services Reference Manual for coding specifications.

2-232

MESSAGES
SMINVREQ, invalid symbiont manager request
Facility:

Job controller

Explanation: A symbiont manager request contained an invalid
request code.
This message is associated with a status code
returned by the job controller. The operating system does not
normally display this message.
User Action: Check for a programming error.
call to the service was coded correctly.

Verify

that

the

SMZEROJOB, zero length job released
Facility:

Job controller

Explanation: The job controller released a job that had no files
in it. This message is associated with a status code returned by
the job controller.
The operating system does not normally
display this message.
User Action: Note the condition. Modify the source program,
necessary, to detect and respond to the condition.

SNDRESP, error sending response
Facility:

Job controller

Explanation: The symbiont manager encountered an error while
trying to write a response to a user. This message indicates an
internal error in the job controller or a system failure.
User Action: Accompanying messages usually indicate the reason
for the failure.
Collect as much information as possible and
submit an SPR.
SNE, file sharing not enabled
Facility:

VAX-11 RMS

Explanation:

VAX-11 RMS file sharing has not been enabled.

User Action: Request the system manager to run the VAX-11 file
sharing initialization program RMSSHARE to enable VAX-11 RMS file
sharing.
SPE, file sharing pagecount exceeded
Facility:

VAX-11 RMS

Explanation: VAX-11 RMS file sharing has used
system memory for file sharing control blocks.

all

allowable

User Action: Request the system manager to run the VAX-11 file
sharing initialization program RMSSHARE to increase the allowable
memory. Additionally, the system's paged dynamic memory limit
may need to be increased, since VAX-11 RMS file sharing is
limited to one half of the system paged dynamic memory.

7.-233

MESSAGES
SPERECLOC, specified record locked
Facility:

FORTRAN (run-time)

Explanation: A READ or direct access WRITE, FIND or DELETE
attempted on a record which was locked by another user.

was

User Action: Correct the program logic so that I/O attempted on
locked records can be retried. This condition can be detected by
using the ERR= and/or IOSTAT= I/O statement keywords.
See the
VAX-11 FORTRAN User's Guide for more information.
SPL, spool or submit of command file failed on $CLOSE
Facility:

VAX-11 RMS

Explanation: The spool or submit command file
on a $CLOSE operation failed.

option

specified

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'
illegal length nnn
Facility:

file

ilibrary

file-spec'

has

LIBRARY

Explanation: This error message is generated by the LIBRARY
command.
The PSECT name length exceeds the maximum length of 31
characters.
User Action:

Change the PSECT name length.

SQO, operation not sequential (SQO set)
Facility:

VAX-11 RMS

Explanation: An attempt was made to perform random access to a
the
file opened or created with the SQO file processing option;
file can only be processed with sequential operations.
User Action: Verify that the call to the VAX-11 RMS service
coded correctly.

was

SQUROONEG, square root of negative value
user PC location
Facility:

Math Library

Explanation: A mathematics library procedure was
evaluate the square root of a negative number.
returned is the reserved operand, minus zero.

called to
The result

User Action: Locate the call to the library procedure that
returned the error. Correct your program so that the argument is
zero or positive.

2-234

MESSAGES
SSFAIL,
system
service
failure
PC=location, PSL=xxxxxxxx
Facility:

exception,

status=xxxxxxxx,

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.
STACKDUMP, non-symbolic stack dump follows
Facility:

TRACE

Explanation: This message precedes a traceback dump.
The
accompanying message indicates why the traceback is nonsymbolic.
User Action: None.
This message
is
informational.
nonsymbolic stack dump is displayed following this message.

The

STAINCOPE, START on file incompatible with OPEN mode
Facility:

COBOL (run-time)

Explanation: The START operation is not compatible with the
current open mode of the file. The file status variable, if
present, has been set to 94. No applicable USE procedure has
been found.
User Action: The user should examine the mode in which the file
was opened prior to the attempted· START operation and change the
open mode to allow the successful completion of start operation.
STARTING, DECnet line 'line-number' starting downline load
Facility:

DLE

Explanation:
system.

A boot

user Action:

None.

request

was

initiated

the

satellite

STAUNOFIL, attempting START on unopened file
Facility:

COBOL (run-time)

Explanation: An attempt was made to perform a START operation on
a file before the file is opened. The file status variable, if
present, has been set to 94. No applicable USE procedure has
been found.
User Action: The user should examine the logic of the program to
determine why a START operation is attempted before the file is
opened. The user may wish to change the logic of the program to
open the file or, alternatively, to eliminate the START operation
before executing the OPEN.
2-235

MESSAGES
STILLKEYS, keys still point at data
Facility:

Librarian

Explanation: This warning message is generated by the Librarian
routines.
Keys in other indexes still point at the text. The
call to LBR$DELETE DATA did not delete the text.
User Action:

None.

Processing continues.

STKOVF, command procedures are too deeply nested
Facility:

VAX/VMS Command Language Interpreter

Explanation: The maximum level of nesting of command procedures
has been exceeded. Too many procedures invoked other procedures.
User Action: Simplify the command procedure hierarchy to
the level of nesting.

reduce

STO, stop
Facility:

BASIC (run-time)

Explanation:

The program executed a STOP statement.

User Action:
execution by
EXIT.

This is an informational
message.
Continue
typing CONTINUE or terminate execution by typing

STR, user structure (FAB/RAB) became invalid during operation
Facility:

VAX-11 RMS

Explanation: During execution of a VAX-11 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 either by the user or by VAX-11 RMS.
For example, the user record buffer overlaps the RAB during a
$GET service.
User Action: Verify that the call to the VAX-11 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.
STRINGOVR, result string
Facility:

BTRAN

Explanation: The command string was backtranslated to an RSX-llM
MCR command and the resulting string was greater than 80
characters, the maximum command string length for MCR.
User Action: Recast and reenter the command.
If the command
contained
many
file specifications, reorder them to take
advantage of temporary file specification defaults.
Or, if
possible, issue several commands to process all the files.
In
some cases, for example, a MACRO command that requires one or
more library specifications, it may be necessary to shorten the
file names of the input source files.
2-23n

MESSAGES
STRIS_INT, string is interlocked
Facility:

STRING (run-time)

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: The user should 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 the user should disable ASTs while string
assignments are in progress.
STRLVL, object structure level nnn unsupported in module 'module-name'
in 'library file-spec'
Facility:

LIBRARY

Explanation: This error message is generated by the LIBRARY
command.
You attempted to insert an illegally formatted object
file.
User Action:
library.

Recompile the object file and insert

into

the

STRTOOLON, string too long
Facility:

BASIC (run-time)

Explanation: The program contains a
bytes. This is a fatal error.
User Action:

string

longer

than

n5535

Reduce the length of the string.

STRTOOLON, string is too long (greater than n5535)
Facility:

STRING (run-time)

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,
Appendix C in the VAX-11 Architecture Handbook. The Maximum
length string supported is 05,535.
User Action: The user should never specify string lengths
greater
than n5,535.
The user should also check that a
concatenation operation will not attempt to create a string
longer than 05,535.
STRTRU, string truncated
Facility:

VAX-11 Run-Time Procedure Library

Explanation: A Run-Time Library procedure returned a string that
did not fit in the area specified to receive it. Trailing
characters were lost. 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.
2-237

MESSAGES

SUBOUTRAN, subscript out of range
Facility:

BASIC (run-time)

Explanation: The program attempts to reference an array element
outside of the array's DIMENSIONed bounds.
This is a fatal
error.
User Action: Check program logic to make sure that all
references are to elements within the array boundaries.

array

SUBOVELON, subscript or reference modifier overflows longword
·Facility:

COBOL (run-time)

Explanation: The evaluation of a subscript or reference modifier
has produced a value that cannot be contained in a longword
quantity.
User Action: The user should examine the referenced line of the
source program containing the subscripting operation or reference
modifier to determine why the value produced overflows a longword
quantity.

SUBRNG, arithmetic
PSL=xxxxxxxx
Facility:

trap,

subscript

out

range

VAX/VMS System Services

Explanation: A subscript
exception condition.

out

range

caused

User Action: Examine the PC location displayed in
and check the program listing to verify that
variables are specified correctly.

SUP, operation not supported over network;
Facility:

PC=xxxxxxxx,

DAP code

arithmetic
the message
operands or

xxxxxxxx

VAX-11 RMS

Explanation: The requested VAX-11 RMS operation failed because
either the specified remote node does not support the function or
VAX-11 RMS at the local node does not support the function in a
network context.
User Action: Consult the DECnet-VAX User's Guide and
the
applicable DECnet manual f~r 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 DECnet-VAX User's Guide for an interpretation of
the DAP status code.
(Note, however, that the explanation is
intended for users who are familiar with DAP.)

SUPERSEDE, created file superseded existing version
Facility:

VAX-11 RMS

Explanation: The file created by a VAX-11 RMS $CREATE
superseded an existing version of the same file.
User Action:

None.

This message is informational.
2-238

operation

MESSAGES
SUPERSEDE, logical name superseded
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a system service request. A request to place a
logical name in a logical name table successfully completed 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 informational.
Note the
condition.
Modify the source program, if necessary, to detect
and respond to the condition.
SUSP~NDED,

process is suspended

Facility:

VAX/VMS System Services

Explanation: This severe error message is associated with a
status
code returned from a system service request.
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.
SYMBASN, error assigning symbiont mailbox
Facility:

Job controller

Explanation: This message indicates an internal error in the job
controller or a system failure.
user Action: Accompanying messages usually indicate the reason
for the failure.
Collect as much information as possible and
submit an SPR.
SYMBCRE, error creating symbiont mail box
Facility:

Job controller

Explanation: This message indicates an internal error in the job
controller or print symbiont, or a system failure.
User Action:
an SPR.

Collect as much information as possible and

2-239

submit

MESSAGES
SYMBDSAB, symbiont manager is disabled
Facility:

Job controller

Explanation: A symbiont manager request failed because the
symbiont manager is not currently active.
This message is
associated with a status code returned by the job controller.
The operating system does not normally display this message.
User Action: Wait and retry the program;
if the error persists,
notify the system operator that there is an error in the symbiont
manager.
SYMBWRT, error writing symbiont mailbox
Facility:

Job controller

Explanation: This message indicates an internal error in the job
controller or a system failure.
User Action:
an SPR.

Collect as much information as possible and

submit

SYMDCLEXTR, symbol declared external
Facility:

VAX-11 MACRO assembler

Explanation: A label definition or direct assignment statement
specified a symbol that was previously declared external in a
.EXTERNAL directive.
User Action: Delete the external declaration or change the
of the internal symbol.

name

SYMDEFINMO, symbol is defined in module
Facility:

VAX-11 MACRO assembler

Explanation: A .EXTERNAL directive specified a
previously defined in the module.

label

that

was

User Action: Delete
internal symbol.

rename

the

external

declaration

SYMDEL, invalid symbol delimiter
Facility:

VAX/VMS Command Language Interpreter

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
between backslashes.

2-240

command

displayed

MESSAGES

SYMDEL, symbiont delete error
Facility:

Job controller

Explanation: This message indicates an internal error in the job
controller or a system failure.
User Action:
an SPR.

Collect as much information as possible and

submit

SYMNAMLNG, 'module type' module 'module-name' file 'library file-spec'
has illegal length nnn
Facility:

LIBRARY

Explanation: This error message is generated by the LIBRARY
command.
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:

VAX-11 MACRO assembler

Explanation: The argument in a macro
relative symbol or was undefined.
User Action:
symbol.

Ensure

that

symbol

string

operator

defined

was

absolute

SYMOUTPHAS, symbol out of phase
Facility:

VAX-11 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
Facility:

VAX/VMS Command Language Interpreter

Explanation: The command interpreter cannot hold any more symbol
definitions or labels.
Note that this error can occur when a
nested procedure is executed, because the command interpreter
defines the symbols Pl through PB before executing the procedure.

If no ON condition is established for warnings in the procedure,
the procedure continues execution. However, the procedure may
fail later if the symbol that could not be defined is referred
to.

2-241

MESSAGES

This error is also issued if an attempt is
explicit value for the reserved global
$SEVERTM.

made to define an
symbols $STATUS and

User Action: If necessary, interrupt the command procedure with
CTRL/C and stop its execution. Use the SHOW SYMBOL command to
determine how many global symbols are defined;
redefine unused
symbols to null strings to recover symbol table space.

If the error occurs frequently, simplify the command procedure or
procedures.
Use
local symbols within procedures whenever
possible.
SYN, file specification syntax error
Facility:

VAX-11 RMS

Explanation: The file specification
syntax error.

syntax

string

User Action: Correct the syntax and reenter
correct the program that caused the error.

the

contains

command

SYNERR, syntax error
Facility:

BASIC (run-time)

Explanation: A program statement is incorrectly formatted. This
is
a fatal error.
It should not occur in the run-time
environment.
User Action:
an SPR.

Collect as much information as possible and

submit

SYNERRFOR, syntax error in format
Facility:

FORTRAN (run-time)

Explanation:
Library was
variable.

A syntax error was encountered while the Run-Time
processing a format stored in an array or character

User Action: Locate the I/O statement in your program in which
the format specification was a variable or expression instead of
a statement number or character constant.
Check that the
resulting expression is a valid format specification, including
left and right parentheses.

SYNTAX, error parsing 'string'
Facility:

Shared by several facilities

Explanation: The command syntax is invalid.
displays the rejected portion of the command.

The

message

User Action: use the HELP command or refer to the VAX/VMS
Command Language user's Guide,
if necessary, for the correct
syntax and reenter the comm~ina.---

2-242

MESSAGES

SYNTAX, syntax error
Facility:

INS

Explanation: An invalid file specification or other syntax error
was detected.
User Action:

Reenter the command line.

SYNTAXERR, string syntax error detected by LIBSTPARSE
Facility:

VAX-11 Run-Time Procedure Library

Explanation: The string passed to
procedure contained a syntax error.
User Action:

the

LIB$TPARSE

library

Correct the string.

SYS, QIO system service request failed
Facility:

VAX-11 RMS

Explanation: VAX-11 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-11 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-11 RMS I/O operations.

SYSDEV, the system device cannot be dismounted
Facility:

DISMOUNT

Explanation: The device name specified in the
is the system volume.

DISMOUNT

command

User Action: Verify the device name
(or logical name, if a
logical name was specified)
in the command and reenter the
DISMOUNT command specifying the correct device.

SYSERROR, system service error
Facility:

Shared by several facilities

Explanation: An error has been detected by a system service.
subsequent message explains the reason for the error.
User Action:

None.

2-243

MESSAGES
SYSERRORPC, 'name' system service error at PC
Facility:

location

Shared by several facilities

Explanation: An error has been detected by a system service.
subsequent message explains the reason for the error.
User Action:

None.

SYSVERDIF, privilege removed - system version mismatch - please relink
Facility:

VAX/VMS System Services

Explanation: This success message is associated with a status
code returned from a system service request. Privilege has been
removed. There is a system version mismatch.
User Action: A SYS.STB, different than that of the currently
running system, was used to link the image being run. Relink the
image.
SZTOOBIG, record size or block size greater than 05534
Facility:

MOUNT

Explanation: The record size or block size specified by /REC
/BLOCK is greater than h5534.
User action:
correction.

Check the source program

and

make

the

necessary

TAPBOTDET, tape BOT detected
Facility:

BASIC (run-time)

Explanation: The program attempted. a rewind
or
backspace
operation on a magtape that was already at the beginning of the
of the file. This is a fatal error.
User Action: Check program logic; do not rewind or backspace if
the magtape is at the beginning of the file.
TAPEPOSLOST, magnetic tape position lost
Facility:

VAX/VMS System Services

Explanation: The magnetic tape ACP has 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 bad.

2-244

MESSAGES
TAPNOTANS, tape not ANSI labelled
Facility:

BASIC (run-time)

Explanation: The program attempted to access a file-structured
magtape that does not have an ANS label. This is a fatal error.
User Action: Determine the magtape's format by mounting it with
the /FOREIGN qualifier and using the DCL DUMP command. You can
then access it as a non-file-structured magtape.
TAPRECNOT, tape records not ANSI
Facility:

BASIC (run-time)

Explanation: The records in the magtape you accessed are neither
ANSI D nor ANSI F format. This is a fatal error.
User Action: Determine the magtape's format by mounting it
the /FOREIGN qualifier and using the DUMP DCL command.

with

TBIT, compatibility mode T-bit
Facility:

RSX

Explanation: An RSX-llM image executed an instruction requesting
a
T-bit
trap.
This message corresponds to the RSX-llM
termination message T-BIT EXECUTION.
User Action: Determine the instruction or statement at which the
error occurred and correct the error.
TBIT, T-bit pending trap at PC = location, PSL=xxxxxxxx
Facility:

VAX/VMS System Services

Explanation: This message indicates an exception condition and
1s 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.
Facility:

nnn

TRACE

Explanation:
program.

An internal coding error occurred in the

traceback

user Action: Collect as much information as possible and submit
an SPR.
Include the bug number displayed in the message in the
report.

?.-245

MESSAGES
TERFORFIL, terminal format file required

Facility:

BASIC (run-time)

Explanation: The program attempted to use PRINT #, INPUT # or
LINPUT # to access a RELATIVE, INDEXED, or VIRTUAL file. This is
a fatal error.
User Action: Supply a terminal-format
INPUT #, or LINPUT # statement.

file

for

the

disabled

with

the

with

the

TERMDSBL, terminal disabled

Facility:

OPCOM

Explanation: A terminal
REPLY/DISABLE c-0mmand.
User Action:

None.

was

successfully

This message is informational.

TERMENAB, terminal enabled

Facility:

OPCOM

Explanation: A terminal
REPLY/ENABLE command.
User Action:

None.

was

successfully

enabled

This message is informational.

THIRDPARTY, logical link disconnected by a third party

Facility:

VAX/VMS System Services

Explanation: This severe error message is associated with a
status code returned from a system service request. A DECnet
logical link was disconnected by a system manager somewhere in
the network.
user Action:

Reinitiate the connection.

TIMEOUT, device timeout

Facility:

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 associated with a DECnet 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 MOUNT command, verify that the physical device
is ready and that the volume was properly loaded on the device.

2-24n

MESSAGES

TIMOVELON, TIMES value overflows longword
Facility:

COBOL (run-time}

Explanation: The evaluation of the TIMES operand associated with
the PERFORM statement has produced a value which cannot be
contained in a longword quantity.
User Action: The user should examine the referenced line of the
source program to determine why the evaluation of the TIMES
operand produces a value which overflows a longword quantity.

TMO, timeout period expired
Facility:

VAX-11 RMS

Explanation: A VAX-11 RMS operation specified a timeout period
and the timeout period expired before the operation completed.
The operation did not complete.
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.
Other
actions depend on the program issuing the request; user programs
should be coded to detect and respond to I/O timeouts.

TNS, terminator not seen
Facility:

VAX-11 RMS

Explanation: A ~AX-11 RMS $GET service to a terminal terminated
when the user buffer was filled.
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.

TOOFEWARG, too few arguments
Facility:

BASIC (run-time}

Explanation: A function call or SUB or FUNCTION statement passed
fewer arguments than were defined in the DEF or subprogram. This
is a fatal ertor.
User Action: Change the number of arguments to match the
defined in the DEF or subprogram.

number

TOOLONG, text wrong length
Facility:

NCP

Explanation:

The input did not meet syntactic requirements.

User Action:

Reenter with the correct input.

2-247

MESSAGES

TOOMANARG, too many arguments
Facility:

BASIC (run-time)

Explanation: A function call or a SUB or FUNCTION statement
passed more arguments than were expected. This is a fatal error.
User Action: Reduce the number of arguments. A SUB or FUNCTION
statement can pass a maximum of 32 arguments; a function call
can pass a maximum of eight arguments.

TOOMANREC, too many records in I/O statement
Facility:

FORTRAN (run-time)

Explanation:

One of the following conditions occurred:

•

An attempt was made to read or write more than one record with
an ENCODE or DECODE statement.

•

An attempt was made to write more records than existed
internal file character variable or arrray.

User Action: Correct the program logic or
correct number of records are written.

that

the

specifications

than

format

TOOMANY, too many file specifications
Facility:

BTRAN

Explanation:
are allowed.

A command contained more file

User Action:

Reenter the command.

TOOMANYLNAM, logical name translation exceeded allowed depth
Facility:

VAX/VMS System Services

Explanation: Ten translations were
name;
it remains to be translated.

performed

User Action: Display all logical name tables
entries that caused the problem.

on
and

the

logical

remove

those

TOOMANYVER, too many higher file versions
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a file system ACP QIO request. The maximum number
of file versions already exists for the specified file and all
the
version
numb~rs
are greater than the version number
specified.
User Action: Check for a programming error.
numb~r specified in the I/O request.

2-248

Verify the

version

MESSAGES
TOOMNYARGS, too many arguments in MACRO call
Facility:

VAX-11 MACRO assembler

Explanation: The macro call contained more arguments than
specified in the .MACRO directive in the macro definition.
User Action:
definition.
TOOMNYENDR, too
file-spec'
Facility:

were

Ensure that the macro call corresponds to the macro

many

.ENDR

macro

'macro

name'

'library

LIBRARY

Explanation: This warning message is generated by the LIBRARY
command. The specified macro contains an unmatched .ENDR.
User Action:

Reformat the macro source file.

TOOMNYLIB, too many libraries open
Facility:

Librarian

Explanation: This error message is generated
routines. Too many libraries are open. Only
open at a time.

by
l~

the Librarian
libraries may be

User Action: use LBR$CLOSE to close any library that you do
need to access.

not

TOOMNYOPND, too many operands for instruction
Facility:

VAX-11 MACRO assembler
many

operands

specified

Explanation:
instruction.

Too

User Action:

Reduce the number of operands.

were

for

the

sections

were

TOOMNYPSEC, too many PSECTs declared
Facility:

VAX-11 MACRO assembler

Explanation:
declared.

More than 255 user-defined

program

User Action:

Reduce the number of program sections.

TOOMUCHDATA, too much optional or interrupt message data
Facility:

VAX/VMS System Services

Explanation: A network interrupt message was rejected because it
contains more than lo bytes of data.
User Action: Repeat the request;
bytes of data.

2-249

do not specify

than

MESSAGES
TRACEBACK, symbolic stack dump follows
Facility:

TRACE

Explanation:

This message precedes a symbolic traceback dump.

User Action:

None.

This message is informational.

TRAP, compatibility mode TRAP execution
Facility:

RSX

Explanation: The RSX-llM image executed a TRAP instruction.
This message corresponds to the RSX-llM termination message TRAP
EXECUTION.
User Action: Determine the instruction or statement at which the
error occurred and correct the error.
TRE, error in index tree
Facility:

VAX-11 RMS

Explanation: VAX-11 RMS detected an invalid index pointer in
indexed file.
User Action

Reorganize the file.

This error is caused by hardware errors, VAX-11 RMS or system
software errors, or inadvertent modifications of files by non-RMS
programs. Collect as much information as possible and submit an
SPR.
TRMMBXUSE, termination mailbox already in use
Facility:

Job controller

Explanation: This message is issued by the job controller if
another process has already issued a SYNCH command that specifies
JOBNAME or /ENTRY=nnn.
User Action: None possible.
with the same jo~.

Two

processes

cannot

synchronize

TRU, truncation
Facility:

STRING (run-time)

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: The user should not put more characters into a
string than its maximum length. This error may be ignored if
right truncation is acceptable.

2-250

MESSAGES

TYP, error in file type
Facility:

VAX-11 RMS

Explanation: The file type specified in a file specification
contains invalid syntax, for example, more than three 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:

Librarian

Explanation: This warning message is generated by the Librarian
routines.
on a call to LBRSOPEN, the library type you requested
conflicts with the library type you specified in the create
options argument.
User Action: None.
library type.

Processing continues

based

the

actual

UAFOPN, user authorization file open error
Facility:

Job controller

Explanation: The input card reader symbiont could not read the
user authorization file.
This message indicates an internal
operating system error.
User Action:
an SPR.

Collect as much information as possible and

submit

UBF, invalid user buffer
Facility:

VAX-11 RMS

Explanation: The user record buffer address of the RAB specified
an area of memory that cannot be written by the caller.
User Action: Verify that the call to the VAX-11 RMS service
coded correctly.

UFD
UFD

was

access failure on existing directory
reason for failure
Facility:

user File Directory Utility

Explanation: VAX/VMS was not able to access the directory.
second message provides the reason for failure.

The

User Action: Take the required corrective action, based
indicated reason, and reissue the command.

the

2-251

MESSAGES
UFO
UFO

close failure on directory
reason for failure
Facility:

User File Directory Utility

Explanation: VAX/VMS was not able to close the directory
The second message provides the reason for the failure.
User Action: Take the required action, based
reason, and reenter the command.

the

file.

indicated

UFO -- device not in system
Facility:

user File Directory Utility

Explanation: The device specified in
the
command does not exist in the host system.
User Action:

CREATE/DIRECTORY

Reenter the command specifying a valid device name.

UFO -- directory already exists
Facility:

User File Directory Utility

Explanation: A directory with the specified name already
on the volume.

exists

User Action: Reenter the CREATE/DIRECTORY command specifying
different directory name, or use the existing directory.
UFO
UFO

failed to create directory
reason for failure
Facility:

User File Directory Utility

Explanation: No space exists on the volume, or an I/O error
occurred.
The second message provides the reason for the
failure.
User Action: If no space exists, delete any unnecessary files or
compress the volume using DSCl or DSC2; disk compression may
require operator intervention.
If an I/O error occurred, ensure that the device
the volume is mounted;
then retry the command.
UFO
UFO

online

and

failed to initialize directory
reason for failure
Facility:

user File Directory Utility

Explanation: VAX/VMS was not able to initialize the directory
file. The second message provides the reason for the failure.
User Action: Take the required corrective action, based
reason indicated, and reenter the command.

2-252

the

MESSAGES
UFD -- not Files-11 device
Facility:

User File Directory Utility

Explanation: The volume on which the directory was to be created
is not a Files-11 structured volume.
You cannot create a
directory on a foreign volume with the CREATE/DIRECTORY command.
User Action: Reenter the command specifying a valid Files-11
volume.
If necessary, initialize the volume with the INITIALIZE
command.
UFD -- syntax error
Facility:

User File Directory Utility

Explanation:

The command line is not in the correct format.

User Action:

Correct the command line and reenter the command.

UFD -- too many subdirectory levels
Facility:

User File Directory Utility

Explanation: You are attempting to exceed
subdirectory levels for a directory.

the

limit

User Action: Reenter the command specifying no more
directory levels.

eight

than

eight

UFD -- volume not mounted
Facility:

user File Directory Utility

Explanation: The target volume for a CREATE/DIRECTORY command is
not mounted.
The volume must be mounted before the file
structure can be accessed.
User Action: Ensure that the volume is physically mounted and
use the MOUNT command to access the file structure. Then,
reenter the CREATE/DIRECTORY command.
UNASEFC, unassociated event flag cluster
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a system service request. 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.

2-253

MESSAGES

UNDEF EXP, attempting undefined exponentiation -- negative base raised
to fractional exponent
Facility:

COBOL (run-time)

Explanation: An illegal exponentiation operation in COBOL
attempted. A negative base is taken to a fractional power.

was

User Action: The user should examine the logic of the source
program to determine why this illegal operation was attempted.

UNDEFSYM, undefined symbol
Facility:

VAX-11 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 a
.EXTERNAL directive.
User Action: Define the local label or symbol,
symbol in a .EXTERNAL directive.

specify

the

UNDEFXFRAD, undefined transfer address
Facility:

VAX-11 MACRO assembler

Explanation: The .END directive specified a transfer address
that was not defined in the module or specified in a .EXTERNAL
directive.
User Action: Define the transfer address or delete it
.END directive.

from

the

UNDEXP, undefined exponentiation
User PC location
Facility:

Math Library

Explanation: An expression contained exponentiation that cannot
be mathematically evaluated, for example O.**O. The result is
the reserved operand, minus zero.
User Action: use the traceback information or the PC displayed
in the message to locate the error in your program and correct
the mathematical expression.

UNDFIL, file not open
Facility:

VAX/VMS Command Language Interpreter

Explanation: A READ or WRITE command 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 OPEN command to open the file before
attempting to read or write it.

2-254

MESSAGES

UNDSYM, undefined symbol
Facility:

VAX/VMS Command Language Interpreter

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.

UNEINSCON, INSPECT CONVERTING lengths unequal
Facility:

COBOL (run-time)

Explanation: The lengths of the search and replacement
are not equal in the INSPECT CONVERTING statement.

strings

User Action: The user should examine the referenced INSPECT
CONVERTING statement to determine why the lengths of the search
and replacement strings are not equal. These lengths must be the
same according to the rules of the COBOL language.

UNESYMMSG, unexpected message from symbiont manager
Facility:

Job controller

Explanation: This message indicates an
print symbiont.
User Action:
an SPR.

internal

error

Collect as much information as possible and

the

submit

UNEXPLIST, qualifier only takes a single value
Facility:

BTRAN

Explanation: A list of values was specified for a qualifier that
accepts only a single value.
User Action: use the HELP command or refer to the VAX/VMS
Command Language user's Guide,
if necessary, for the correct
syntax and reenter the command.

UNIALROPE, unit already open
Facility:

FORTRAN (run-time)

Explanation: A DEFINE FILE statement specified
that was already opened.

logical

unit

User Action: Verify that the logical unit number in the DEFINE
FILE statement is correct.
If it is correct, insert a CLOSE
statement before the DEFINE FILE or remove the DEFINE FILE.

2-255

MESSAGES
UNKDEV, unknown device type
Facility:

INITIALIZE and MOUNT

Explanation:

The device type specified is unknown or invalid.

User Action: Verify the device
logical name was specified),
correct device name.

name
(or logical name, if a
and reenter the command with the

UNKNOPR, unknown operator
Facility:

OPCOM

Explanation: A REQUEST or REPLY command
operator name;
the keyword is invalid.
sent.

specified an invalid
No request message was

User Action: Reenter the REQUEST or REPLY
valid operator name.

command;

specify

UNLERR, UNLOCK error
Facility:

FORTRAN (run-time)

Explanation: RMS detected an error condition during execution of
an UNLOCK statement.
User Action: Take corrective
VAX-11 RMS message.

action

based

UNLOCK

the

associated

UNLOCKED, file-spec unlocked
Facility:

Shared by several facilities

Explanation:
unlocked.

The

User Action:

None.

file

specified

command

was

This message is informational.

UNPROPARM, unprocessed parameters
Facility:

VAX/VMS Command Language Interpreter

Explanation: A command
currently supported.

contained

parameters

User Action: Reenter the
number of parameters.

command;

specify

only

than
the

are

maximum

UNPROQUAL, unprocessed qualifiers
Facility:

CL! and VAX-11 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 on the command were
ignored.
The operating system does not normally display this
message.

2-256

MESSAGES
If this error occurred as a result of a macro assembler
operation;
either the /SHOW or the /CROSS qualifier was
specified without the /LIST qualifier. The assembler does not
process the source file or produce an object module.
User Action: Note the condition. Modify the source program,
necessary, to detect and respond to the condition.

If either the /SHOW or the /CROSS qualifier was specified without
/LIST, reenter the command with the /LIST qualifier.
UNREACHABLE, node is known but unreachable
Facility:

VAX/VMS System Services

Explanation: This severe error message is associated with a
status code returned from a system service request. An attempt
was made to initiate a DECnet logical link connection.
The
specified node has 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 DECnet-VAX User's Guide for additional information.
UNRECSTMT, unrecognized statement
Facility:

VAX-11 MACRO assembler

Explanation:
user-defined
library.

The operator was not
an
opcode, previously defined

User Action: Change the operator to a valid
or macro; or define the macro.

opcode,
directive,
macro, or macro in a
opcode,

directive,

UNRKEY, keyword is an unrecognized keyword
Facility:

VAX-11 Run-Time Procedure Library

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.

UNSAFE, drive unsafe
Facility:

VAX/VMS System Services

Explanation: This message
returned by I/O functions.

is associated with a status
The drive cannot be used.

code

User Action: Check the status of the device and repeat the
request.
If the failure persists, notify the system manager.

2-257

MESSAGES
UNTERMARG, unterminated argument
Facility:

VAX-11 MACRO assembler

Explanation: The string argument was missing a delimiter or
macro argument was missing an angle bracket.
User Action:

Add the delimiter or angle

the

brac~et.

UNTERMCOND, unterminated conditional
Facility:

VAX-11 MACRO assembler

Explanation: A conditional assembly block was not terminated by
a .ENDC directive.
The assembler inserted a .ENDC directive
before the .END directive.
User Action:

Add the .ENDC directive.

UNWIND, unwind currently in progress
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a system service request. 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,
necessary, to detect and respond to the condition.

UNWINDING, unwind already in progress
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned from a system service request. 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,
necessary, to detect and respond to the condition.
UNXPCTSTS, unexpected status detected.
Facility:

Expected 'status'.

Found:

Shared by several facilities

Explanation: An error has been detected by a system service.
subsequent message explains. the reason for the error.
User Action:

None.

2-258

MESSAGES

UPDUTRAV, index update during traverse illegal
Facility:

Librarian

Explanation: This error message is generated by the Librarian
routines.
The routine that you specify in the routine name
argument cannot contain any calls to either LBRSDELETE or
LBR$INSERT KEY.
User Action: Remove any embedded calls to either
LBR$INSERT_KEY before calling the routine.

LBRSDELETE

UPI, UPI not set when sharing and BIO or BRO set
Facility:

VAX-11 RMS

Explanation: VAX-11 RMS permits file sharing when block I/O
access (BIO or BRO) is specified and UPI is specified as well.
The user program must provide all required interlocks.
User Action: Verify that the call to the VAX-11 RMS service
coded correctly.

was

USEFLORES, use of floating reserved operand
Facility:

OTS and VAX-11 Run-Time Procedure Library

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
statement that caused the error and correct your program.

the

USGOTO, unsatisfied GOTO command
Facility:

VAX/VMS Command Language Interpreter

Explanation: The label of a GOTO (DCL), .GOTO (MCR),
(MCR) could not be found in the current command file.
User Action:
exists.

.GOSUB

Correct the command file by ensuring that the label

USZ, invalid user buffer size
Facility:

VAX-11 RMS

Explanation: The size specified in the user record buffer size
field is invalid.
The buffer size must be in the range of 1
through 65535.
User Action: Verify that the call to the VAX-11 RMS service
coded correctly.

2-259

was

MESSAGES

VALCNVERR, error converting value
Facility:

VAX/VMS Command Language Interpreter

Explanation: A keyword or qualifier value was not converted
correctly because, for example, a string was supplied when only a
number is valid.
User Action:

Retype the command and give the correct value.

VALERR, specified value is out of legal range
Facility:

Shared by several facilities

Explanation:
legal range.

A value has been

specified

which

User Action:

Respecify using a valid value.

not

within

VALREQ, value required on qualifier
Facility:

VAX/VMS Command Language Interpreter

Explanation:

The qualifier must have a value.

User Action:
qualifier.

Retype the

command

and

supply

value

the

VASFULL, virtual address space is full
Facility:

VAX/VMS System Services

Explanation:

The virtual address space is full.

User Action: Reboot and increase the amount of
space allowed.

virtual

address

VECFULL, privileged vector limit of 42 exceeded
Facility:

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 has been exceeded.
User Action:

Remove vectors not needed and relink.

VER, error in version number
Facility:

VAX-11 RMS

Explanation: The
version
number
specified
in
a
file
specification contains invalid syntax, for example, nonnumeric
characters, or a value larger than 327n7.
User Action: Correct the syntax of the file specification.
Reenter the command or correct the program, as necessary.

~-200

MESSAGES
VERIFYCMD, MCR 'command'
Facility:

RSX

Explanation: This message is used to echo the input command line
on the MCR command.
User Action:

None.

VFEVALERR, variable format expression value error
Facility:

FORTRAN (run-time)

Explanation: The value of a variable format expression was not
within the range acceptable for its intended use; for example, a
field width was less than or equal to zero. A value of 1 was
assumed except for a "P" edit descriptor, for which a value of 0
was assumed.
User Action:
program.

Check the value of the expression and

correct

the

VIRARRDIS, virtual array not on disk
Facility:

BASIC (run-time)

Explanation: The program attempted to reference a virtual
on a nondisk device. This is a fatal error.

array

User Action: Virtual arrays must be on disk;
change
specification in the OPEN statement for this array.

file

the

VIRARROPE, virtual array not yet open
Facility:

BASIC (run-time)

Explanation: The program attempted to reference a virtual array
before OPENing the associated disk file. This is a fatal error.
User Action: OPEN the disk file
before referencing the array.

containing

the

virtual

array

VIRBUFTOO, virtual buffer too large
Facility:

BASIC (run-time)

Explanation: The program attempted to access a VIRTUAL file
the buffer was not 512 bytes long. This is a fatal error.
User Action:

and

Change the I/O buffer to be exactly 512 bytes long.

2-261

MESSAGES
VOLALRMNT, another volume of same label already mounted
Facility:

MOUNT

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 SHOW DEVICES/FULL/MOUNTED
command.
VOLIDENT, label
'volume-label',
'volume-format'
Facility:

owner

'user-name',

format

MOUNT

Explanation: This is an informational message that identifies an
incorrectly specified volume after the INCVOLLABEL and NOHOMEBLK
errors in a MOUNT request.
User Action: No
action
is
necessary.
The
message
is
informational.
If the volume protection allows access to the
volume, reissue the MOUNT command.
VOLINSET, volume is already part of another volume set
Facility:

MOUNT

Explanation: A volume specified in a MOUNT/BIND command is
of another volume set.
User Action: Check the device
volume, or initialize this one.

name

specified.

use

part

another

VOLINV, volume is invalid
Facility:

VAX/VMS System Services

Explanation: This message is associated with a status code
returned by I/O functions. 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 and that the power is on before
retrying the program.
WASECC, successful transfer;
Facility:

no data check

VAX/VMS System Services

Explanation:
returned by
request would
performed and

This message is associated with a status code
I/O functions.
A data check operation on a read
fail; however, one or more ECC corrections were
the operation completed successfully.

User Action: Note the condition. Modify the source program,
necessary, to detect and respond to the condition.
2-202

MESSAGES

WBE, error on write behind
Facility:

VAX-11 RMS

Explanation: An error occurred during a VAX-11 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.

wee, invalid wild card context
Facility:

(WCC) value

VAX-11 RMS

Explanation: The wild card
contains an invalid value.

context

value

the

NAM

block

User Action: Verify that the call to the VAX-11 RMS service was
coded correctly and the NAM block has not been inadvertently
modified between VAX-11 RMS service calls.

WER, file write error
Facility:

VAX-11 RMS

Explanation:
operation.

error

occurred

during

VAX-11

RMS

write

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.

WHA, What?
Facility:

BASIC (run-time)

Explanation: A command or immediate mode statement could not
processed. This is a fatal error.
User Action:

Check for illegal verbs or improper formats.

WILDCONCAT, wildcard specification cannot be concatenated
Facility:

Shared by several facilities

Explanation: A number of files
specified with wild cards.
User Action:

concatenated

cannot

Respecify without using wild cards.

WILDOVTVER, wild card version required for output file
Facility:

Shared by several facilities

Explanation:
output file.

A wild card (*) version must

User Action:

Correct the command.

2-2n3

specified

MESSAGES
WLD, invalid wildcard operation
Facility:

VAX-11 RMS

Explanation: A call to the VAX-11 RMS $ERASE service 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-11 RMS was coded correctly. To perform a wild card file
delete service, you must code a loop that searches for files
based
on
wild card specifications and deletes the files
individually.
WLK, device currently write locked
Facility:

VAX-11 RMS

Explanation: The hardware device specified for a VAX-11 RMS
operation is write locked for protection,_and write access was
attempted.
reset
User Action: Verify the status of the hardware device;
the write lock switch, if necessary. Notify the system operator
if the error cannot be corrected.
WPL, error detected while writing prologue
Facility:

VAX-11 RMS

Explanation: An I/O error occurred while VAX-11 RMS was
a file's prologue area.

writing

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.
WRIBEYBOU, attempting WRITE beyond boundaries of file
Facility:

COBOL (run-time)

Explanation: An attempt was made to WRITE a record at a logical
position which is outside of the bounds of this file.
If a
sequential WRITE was attempted on a sequentially organized file,
the file status variable has been set to 34. No applicable USE
procedure was found.
User Action: This error usually occurs when the user program
attempts to write records to a volume which does not have
sufficient free space to contain the file.
The user should
delete or purge as many files as possible to free sufficient
space to contain the file being written.

2-204

MESSAGES

WRIINCOPE, WRITE on file incompatible with OPEN mode
Facility:

COBOL (run-time)

Explanation: The WRITE operation is not compatible with the
current open mode of the file. The file status variabler if
present, has been set to 94. No applicable USE procedure has
been found.
User Action: The user should examine the mode in which the file
was
opened
prior
to
the
attempted
WRITE
operation.
Alternatively, the user may change the logic of the program to
bypass the attempted WRITE operation.

WRINOTASC, attempting to WRITE non-ascending ISAM key on file
Facility:

COBOL (run-time)

Explanation: An attempt was made to perform a sequential WRITE
operation to an indexed file in which the primary key value is
not in ascending order. The file status variable, if present,
has been set to 21.
No applicable exception label or USE
procedure was found.
User Action: The user should examine the program logic to
determine why the primary key values are not written in ascending
order.

WRIREAFIL, write to READONLY file
Facility:

FORTRAN (run-time)

Explanation: A write operation was attempted to a file that
declared READONLY by the currently active OPEN.

was

User Action: Locate the statement that caused the error
verify
the
logical unit number.
If correct, verify
parameters on the OPEN statement.

and
the

WRISMAMIN, attempting WRITE of variable length
allowed on file
Facility:

smaller

than

minimum

COBOL (run-time)

Explanation: An attempt was made to WRITE a record that is
shorter than the minimum length record declared in the program
for this file. The file status variable, if present, has been
set to 94. No applicable USE procedure has been found.
User Action: The user should examine
determine why the record is shorter
declared for this file in the program.

the program logic to
than the minimum length

WRITEERR, error writing 'file-spec'
Facility:

Shared by several facilities

Explanation: This error message can be generated by the LIBRARY
command. During a VAX-11 RMS operation, an error was encountered
while writing a file.

2-2ns

MESSAGES

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
privilege to write to it.

you

have

If a macro assembly error, retry the assembly.
reproducible, notify your system manager.

error

If the

WRITELOCK, volume is write locked
Facility:

MOUNT

Explanation: This informational message
found the volume to be write locked.

indicates

that

MOUNT

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.

WRITESCB, write error on
locked
Facility:

storage

control

block;

volume

write

MOUNT

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, write lock error
WRITLCK, volume on 'device' is write locked
Facility:

VAX/VMS System Services and MOUNT

Explanation: The volume cannot be written because
write lock switch is set on the drive.
User Action:
program.

Release

the

write

lock

switch

and

the

hardware

retry

the

WRIUNOFIL, attempting WRITE on unopened file
Facility:

COBOL (run-time)

Explanation: An attempt was made to perform a WRITE operation on
a file before the file was opened. The file status variable, if
present, has been set to 94. No applicable USE procedure has
been found.
User Action: The user should examine the program logic to
determine why an attempt was made to perform a WRITE operation
before the file was opened. The user may wish to change the
program logic to open the file before executing the WRITE.
the
Alternatively, the user may wish to eliminate
WRITE
operation.

2-206

MESSAGES
WRONGACP, wrong ACP for device
Facility:

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 tne file structure being mounted.
User Action: Check the ACP specified in the MOUNT/PROC= command;
verify what structure you are trying to mount.
WRONUMARG, wrong number of arguments
Facility:

STRING {run-time)

Explanation: A String facility
incorrect number of arguments.

entry

was

called

with

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 to a String facility
routine
directly
should
submit
an
SPR with supporting
documentation including the system traceback listing.
WRONUMARG, wrong number of arguments
use r .Pc 1 o cat ion
Facility:

Math Library

Explanation: A mathematics 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-11 Run-Time Library Reference Manual for a
description of the required arguments.
WRTHOMBLK, I/O error writing home block
Facility:

MOUNT

Explanation: An I/O error has occurred writing the home block of
a volume during MOUNT/BIND.
User Action: Check that the hardware is functioning
Reinitialize the disks and retry the operation.

properly.

XAB, invalid XAB or XAB not accessible at location
Facility:

VAX-11 RMS

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-11 RMS service was coded correctly.

2-2r.7

MESSAGES

XMTERR, loop failed, nnn messages not sent
Facility:

NCP

Explanation:

An error occurred during the loopback test.

User Action:

Check the quality of the communications line.

2-268

APPENDIX A
ERROR CODES

Table A-1
RSX-11 File Control Services Error Codes
Error
Number

Code
Name

-01.
-02.
-03.
-04.
-05.
-06.
-07.
-08.
-09.
-10.
-11.
-12.
-13.
-15.
-16.
-17.
-18.
-19.
-20.
-21.
-22.
-23.
-24.
-25.
-26.
-27.
-28.
-30.
-31.
-32.
-33.
-34.
-35.
-36.
-37.
-38.
-39.
-40.
-41.
-42.

IE. BAD
IE. IFC
IE .DNR
IE.VEH
IE .ONP
IE.SPC
IE.DNA
IE.DAA
IE.DUN
IE. EOF
IE. EOV
IE. WLK
IE.DAO
IE.ABO
IE. PR!
IE. RSU
IE.OVR
IE.BYT
IE.BLK
IE.MOD
IE.CON
IE .NOD
IE .DFU
IE. !FU
IE.NSF
IE. LCK
IE. HFU
IE.CKS
IE. WAT
IE.RER
IE. WER
IE.ALN
IE .. SNC
IE. SQC
IE.NLN
IE. CLO
IE .NBF
IE .RBG
IE.NBK
IE. I LL

Meaning

Bad parameter
Invalid function code
Device not ready
Parity error on device
Hardware option not present
Illegal user buffer
Device not attached
Device already attached
Device not attachable
End of file detected
End of volume detected
Write attempted to locked unit
Data overrun
Request terminated
Privilege violation
Shareable resource in use
Illegal overlay request
Odd byte count (or virtual address)
Logical block number too large
Invalid UDC module
UDC connect error
Caller's nodes exhausted
Device full
Index file full
No such file
Locked from read/write access
File header full
File header checksum failure
Attribute control list format error
File processor device read error
File processor device write error
File already accessed on LUN
File ID, file number check
File ID, sequence number check
No file accessed on LUN
File not properly closed
Open - no buffer space available for file
Illegal record size
File exceeds space allocated, no blocks
Illegal operation on file descriptor block
(continued on next page)
A-1

ERROR CODES

Table A-1 (Cont.)
RSX-11 File Control Services Error Codes
Error
Number

Code
Name

-43.
-44.
-45.
-46.
-48.
-49.

IE.BTP
IE .RAC
IE.RAT
IE. RCN
IE. 2DV
IE. FEX
IE. BDR
IE. RNM
IE.SDI
IE. FOP
IE.BNM
IE. BDV
IE. BBE
IE.DUP
IE. FHE
IE.NF!
IE. ISQ
IE. EOT
IE .BVR
IE.BHD
IE.OFL
IE.BCC
IE. EXP
IE.BTF
IE .NNC
IE. !ES
IE.PES
IE.ALC
IE. ULK
IE.WCK

-so.

-51.
-52.
-53.
-54.
-55.
-56.
-57.
-59.
-60.
-61.
-62.
-63.

-64.
-65.
-66.
-75.
-7 fi.
-77.

-82.
-83.
-84.
-85.
-86.

Meaning

Bad record type
Illegal record access bits set
Illegal record attribute bits set
Illegal record number - too large
Rename - two different devices
Rename - new file name already in use
Bad directory file
Cannot rename old file system
Bad directory syntax
File already open
Bad file name
Bad device name
Bad block on device
Enter - duplicate entry in directory
Fatal hardware e~ror on device
File ID was not specified
Illegal sequential operation
End of tape detected
Bad version number
Bad file header
Device off line
Block check, CRC, or framing error
File expiration date not reached
Bad tape format
Not ANSI 'D' format byte count
Invalid escape sequence
Partial escape sequence
Allocation failure
Unlock error
Write check failure
..

~----~----~-·------·---------------- ~~ =·~---

_ _ _ _ _ _ _ __....

Table A-2
Directive Error Codes (Standard System Codes)
....------- ····---····---··-- - - - . - - - - - - - · · - - · - - - - - - - - - - - - - - - - - - - - - - ,

Error
Number

Code
Name

-01.
-02.
-03.
-04.
-05.
-06.
-07.
-08.
-09.
-10.
-11.
-15.

IE.UPN
IE. INS
IE. PTS
IE. UNS
IE. ULN
IE.HWR
IE .ACT
IE.ITS
IE. FIX
IE. CKP
IE. TCH
IE. RBS
IE. PR!
IE.RSU

-16.

-17.

Meaning

Insufficient dynamic storage
Specified task not installed
Partition too small for task
Insufficient dynamic storage for send
Unassigned LUN
Device handler not resident
Task not active
Directive inconsistent with task state
Task already fixed/unfixed
Issuing task not checkpointable
Task is checkpointable
Receive buffer is too small
Privilege violation
Resource in use
(continued on next page)

A-2

ERROR CODES

Table A-2 (Cont.)
Directive Error Codes (Standard System Codes)
Error
Number

Code
Name

-18.
-19.
-80.
-81.
-83.

IE .NSW
IE.ILV
IE.AST
IE.MAP
IE. !OP
IE .ALG
IE.WOV
IE.NVR
IE.NVW
IE.ITP
IE. !BS
IE. LNL
IE. IUI
IE. mu
IE.IT!
IE. PNS
IE.IPR
IE.ILU
IE. IEF
IE .ADP
IE. SDP

-84.

-85.
-86.
-87.
-88.
-89.
-90.

-91.
-92.
-93.
-94.
-95.
-96.
-97.
-98.
-99.

Meaning

No swap space available
Illegal vector specified
Directive issued/not issued from AST
Illegal mapping specified
Window has I/O in progress
Alignment error
Address window allocation overflow
Invalid region ID
Invalid address window I/O
Invalid TI parameter
Invalid send buffer size (greater than 255.)
LUN locked in use
Invalid UIC
Invalid device or unit
Invalid time parameters
Partition/region not in system
Invalid priority (greater than 250.)
Invalid LUN
Invalid event flag (greater than n4.)
Part of DPB out of user's space
DIC or DPB size invalid

A-3

VAX/VMS System Messages and
Recovery Procedures Manual
AA-D017B-TE
READER'S 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?
page number .

If so, specify the error and the

::>

Q)
II)

cQ)

Please indicate the type of 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>-----------~-----~~--

City_ _ _ _ _ _ _ _ _ _ _ _ _ _ S t a t e - - - - - - - Zip Code _ _ _ _ _ __
or
Country

Do Not Tear - Fold Here and Tape -

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

BSSG PUBLICATIONS TW/A14
DIGITAL EQUIPMENT CORPORATION
1925 ANDOVER STREET
TEWKSBURY, MASSACHUSETTS

01876

Do Not Tear - Fold Here

....