Digital PDFs

AA-DO17A-TE

August 1978

152 pages

Original

7.5MB

view download

OCR Version

6.9MB

view download

Document:	VAX/VMS System Messages and Recovery Procedures Manual
Order Number:	AA-DO17A-TE
Revision:	0
Pages:	152
Original Filename:

OCR Text

August 1978
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-DO17A-TE

SUPERSESSION/UPDATE INFORMATION:

This is a new document for this release.

OPERATING SYSTEM AND VERSION:

VAX/VMS VO1

SOFTWARE VERSION:

VAX/VMS VO1

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

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 reliability of software on
equipment that is not supplied by DIGITAL or its affiliated companies.

1978 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
paring future documentation.

The following are trademarks of Digital Equipment Corporation:

DIGITAL

DECsystem-10

DEC

DECtape

MASSBUS
OMNIBUS

PDP

DIBOL

0s/8

DECUS

EDUSYSTEM

PHA

UNIBUS
COMPUTER LABS

FLIP CHIP
FOCAL

RSTS
RSX

COMTEX
DDT
DECCOMM
ASSIST-11

INDAC
LAB-8
DECSYSTEM-20
RTS-8

TYPESET-8
TYPESET-11
TMS-11
ITPS-10

VAX

VMS

SBI

DECnet

IAS

in pre-

CONTENTS

Page

PREFACE

CHAPTER

INTRODUCTION

1-1

1.1

1.2
1.2.1
1.2.2

MESSAGE DISPLAY
Linked Messages
Exception Conditions
FORMAT OF SYSTEM MESSAGES
Facilities
Severity Levels

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

1.3

RECOVERY

1-5

l.1.1
1.1.2

1.3.1
1.3.2
1.3.3

PROCEDURES
Recovering from Command Entry Errors
Unavailable Resources
Recovering from Programming Errors

1-5
1-6
1-6

1.3.4

Reporting

1-7

System

Software

Hardware Errors

CHAPTER

MESSAGES

2~-1

APPENDIX

ERROR

A-1

CODES

TABLES

TABLE

1-1

Summary

A-1

File

Facility Names

A-2

Directive Error Codes

Control

Services

iii

1-3

Error Codes

A-1

(Standard

A-2

System Codes)

PREFACE

MANUAL

OBJECTIVES

This manual lists the
messages
produced
by
system.
The
messages
are
accompanied
by
applicable, suggested actions to recover from
INTENDED

for all users of the VAX/VMS operating
system,
programmers, system programmers, operators, and

managers.

STRUCTURE

This

operating
and, where

AUDIENCE

The manual is intended
including applications
system

the
VAX/VMS
explanations
errors.

manual

THIS

has

DOCUMENT

two

chapters:

Chapter 1 describes the
how to locate a message

Chapter 2 lists the messages alphabetically by
message
code.
Each
message
1is accompanied by explanatory text and recovery
action.

Appendix

lists

the

format of the
messages
in this manual.

File

Control

Services

error

Note that messages issued by RSX-11M utility programs
commands
do
not
have message codes, as do messages
utilities.
the utility
ASSOCIATED

and

explains

codes.

invoked
by
DCL
issued by native

Messages from RSX-11M utilities are listed together,
name alphabetized within the VAX/VMS message codes.

with

DOCUMENTS

The manuals listed below provide
facilities
indicated.
Messages
in this manual.
Facility

information on messages issued by the
for these facilities are not included

Manual

Basic2

PDP-11

BASIC-PLUS-2

User's Guide

CBL

PDP-11

COBOL

Guide

DEBUG

VAX-11

Symbolic

DSC

VAX-11

Disk

FORTRAN

VAX-11]

FORTRAN

LINK

VAX-11 Linker Reference Manual

User's

Debugger

Save

and

Reference

Manual

Compress User's Guide

IV-PLUS

User's Guide

Facility

Manual

MAC

PDP-11 MACRO User's Guide

MAR

VAX-11 MACRO User's Guide

SRT

PDP~11 SORT Reference Manual

UETP

VAX/VMS UETP User's Guide

VFY

VAX/VMS Operator's Guide

CONVENTIONS USED IN THIS DOCUMENT

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

The following conventions
variable

are

used

is actually output.

<certain

indicate

data:

location

indicates a virtual address in hexadecimal format

XXXXXXXX

indicates data displayed

in hexadecimal

nnn

indicates data displayed

in decimal format

format

types

CHAPTER

INTRODUCTION

1.1

MESSAGE

VAX/VMS
When

provides

you

error

DISPLAY

type

command

results,

and

centralized

the

displays

error

the

system

message

terminal
locates

facility.

execute

image,

and

the

message

associated

with

the

it.

Messages are always displayed on the current device identified by
logical
name
SYS$SOUTPUT.
For an interactive user, this device
terminal;
for batch job users, it is the batch job log file.
If

the
is a
the

logical device SYSSERROR is different
writes informational, warning, error,
device as well.

also
that

For

example,

specify
as

the

SYSSOUTPUT

current

you

for

error

procedure's

the

The

message

well

issuing
the
ERROR.COM by

command

Then,

the

entered

associated

S$EXIT
typing:

the

procedure.

execution,

qualifier,

device.

terminal,
error

execute

/OUTPUT

from SYSSOUTPUT, the system
and fatal error messages to

procedure

system defines
SYSSERROR

any

interactively

the

remains

errors

messages

are

specified

file.

the

with

any

error

command

indirect

message,

type:

code

you

assigned

occur

error

file

during

the

displayed

can

file.

and

specify
vyour

command

your

retrieved

Create

the

file

SEXIT %X'Pl
Then,

display

the

@ERROR number
Messages

1.1.1

can

Linked

Frequently,

one,

and

command

calls

the
a

linked,

described

the

following

section.

Messages
system
VAX-1l1l

message

more,
Record

does

follows

return

Management

detailed

explanation

appear

alone,

messages.
Services

but

For

the
of

the

reason.

different
the

error.

Linked

followed

example,

(VAX-11

file
does
not exist,
that is cannot open the

indicating

status

not

additional

a
file.
If
the
message indicating

message

display
provide

sometimes

and
open
displays a
RMS

also

RMS)

the
to

TYPE

locate

the TYPE
file;
a

command
VAX-11

messages

usually

facilities

called

and

INTRODUCTION

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

Exception Conditions

1.1.2

error
fatal
a
During the execution of an image, the image can incur
When an exception condition occurs,
known as an exception condition.
the

system takes

special

action.

forces
system
If the image has not declared a condition handler, the
the image to exit and displays a message indicating the reason for the
and
(PC)
the program counter
includes
The message
exception.
This
(PSL) at the time of the exception.
status longword
processor
the system displays the status of
message is followed by a traceback;
frames on the stack so that you can locate the procedure in
the call
which the condition occurred.

1.2

FORMAT OF

SYSTEM MESSAGES

The general format of messages
system

displayed

the

VAX/VMS

operating

is:

TEXT

$FACILITY-L-CODE,

TEXT]

[-FACILITY-L-CODE,
FACILITY

Table 1-1 summarizes the
A VAX/VMS facility, or component, name.
As indicated above in Section
1issue messages.
that
facilities
and
1.1.1, a percent sign (%) prefixes the first message issued,
(-)

a hyphen

prefixes each subsequent message.

It has one of the following values:

A severity level indicator.
Code

Meaning

Success

I
W

Information
Wwarning

Error

Fatal,

severe

error

Severity levels are described in more detail below.
CODE

An abbreviation of the message text;
Chapter

TEXT

the message descriptions in

2 are alphabetized by this code.

The explanation of

[-FACILITY-L-CODE,TEXT]

the message.

in global
always
1is
code
error
(The last
The next message.
This can be shown by typing $SHOW SYMBOLS/GLOBAL
symbol %STATUS.
$STATUS.)

INTRODUCTION

l1.2.1
Table

PFacilities
1-1

lists

the VAX/VMS

facilities

that

issue messages.

Note that the facility name portion of a message can
be
modified
by
system
or application programs.
Any message code can, theoretically,
appear with any facility name, and any character string can appear
as
a facility name.

Table 1-1
of Facility Names

Summary

Name

Facility/Comments

APPEND

command

BTRAN

Back-translator.
The back-translator
interprets
DCL
commands
that
invoke RSX-11 utilities and converts a
DCL command string to an input string for the
RSX-11M

utility.

cBLl

PDP-11 COBOL-74/VAX compiler

COPY

DCL

DEBUGL

VAX-11 Symbolic Debugger

DELETE

DIF2

DIFFERENCES command

DMP2

File Dump utility

pscl

Disk Save and Compress utility

ERF

Error

FORTL

VAX~-11 FORTRAN IV-PLUS compiler

HELP

INIT

INITIALIZE

INPSMB

Card

JBC

Job

LBR

LIBRARY/RSX11l

command

interpreter

command

Log

Format

Process

command
command

reader

input

symbiont

Controller

LIB messages

command.
and

LIB

VAX-11

Run—-Time

LIB2

LIBRARY command

LINKL

VAX-11 Linker

are

LBR messages

therefore

Procedure

not

are

listed

identical

separately.

Library

(continued

next page)

INTRODUCTION

Table

1-1

Summary of

Name

(Cont.)

Facility Names

Facility/Comments

macl

PDP-11 MACRO assembler

MAR

VAX-11

MACRO

MOUNT

command

MTH

Mathematics

Ncpl

DECnet Network Control Program

OPCOM

Operation Communication Manager

PIP2

Peripheral Interchange Program

command

PURGE

command

RMS

VAX-11

Record

RSX

Application

RTL

VAX-11]

RUN

command

SET

command

SHOW

srrl

SORT/RSX11 command

SYSTEM

VAX/VMS

TRACE

Traceback

TYPE

vueTpl

User Environment Test Package

UFD?

User File Directory utility

vFyl

File Structure Verification utility

assembler

Library

Migration

Run-Time

see

Services

Executive

Procedure

Library

command

operating

system

command

Messages issued by this
manual;

Management

the

facility

Preface

for

are
the

not
title

included
of

the

this

manual

consult.

The facility is an RSX-11lM utility invoked by
a
DCL
command;
these
messages
appear
in
a
format
different from messages
issued by VAX/VMS utilities, and
do
not
display
a
severity
level.
All
messages
1issued by the facility appear together,
with the facility name alphabetized as a message code.

INTRODUCTION

1.2.2
The

Severity Levels

severity

of
the
messages
performed

level of a message is included in the
completion
status
component
1issuing
the
message.
Success
and
information
are just that;
the system
is
informing
vyou
that
it
has
your

continues

request.

after

message

issuing
a
indicates that the

Warning

messages

but

not

Oor

program

Error

all,

messages

Fatal

indicate
your

cases,

command

the

message.
is

but

messages

RECOVERY

Errors
®

that

the

command

request,

and

that

may

you

indicate

the

that

system may

indicate

that

the

have

may

output

attempt
the

system

need

the

performed
to

verify

generally
An

program

continue
cannot

error
on

occur
in

for

the

entering

the

command,

following
command
or

some,
command

result

execution.

continue

execution

occurs:

required

resource

currently

Programming

errors

are

detected

software

Recovering

hardware

from Command

file

spelling

syntax

specifications

unavailable
during

image
System

reasons:

incorrect

1.3.1

processing

cases,

PROCEDURES

error

other

complete.

request.

1.3

command

output.

incorrect,

the

some

success

errors

the

execution

occur

Entry Errors

When an error occurs following interactive
command
entry,
you
must
generally
reenter the command.
Messages from the command interpreter
are

generally

followed

that

was
rejected.
reenter the command.
Errors

have

that

cases,

Command
try

occur

entered

you

reenter

in
following

file

while

invalid

need

Language

Errors

may

display

the

Guide

this

command

value

use

User's

the

Correct

the

portion

executing

may

parameter

for
HELP

command

determine

device

names

default

file

the

specifications

command

that

has

the
file
name,
but
the file name
logical name.
The system translated
resulting
of

the

command

line

you

indicate

that

vyou

qualifier.

consult

legal

file

command.

specification

not

can

line

before

the

values

command.

reasons:

For

occur

type,

you

for

these

VAX/VMS

before

you

any

the

entered

is currently defined
the logical name and
valid

within

the

only

a
the

context

INTRODUCTION

The syntax of the file specification

invalid.

device

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

1.3.2

Unavailable Resources

enabled
1is
system service
(SSETRWM)
If the Set Resource Wait Mode
or an
memory
dynamic
as
such
resource,
required
a
and
(default mode)

in a wait
1/0 quota, is unavailable, the process is normally placed
However, under certain
resource becomes available.
the
state until
program conditions the programmer can choose to disable resource wait
so

mode,

that

when

such

condition

occurs,

immediately to the calling program with an error

control

status.

returns

depends
resource
a
of
How a program responds to the unavailability
primarily on the application and the particular service that is being
to continue
the program may be able
1In some instances,
called.
Or, it may be necessary only
retry the service later.
execution and
to note that the program is being required to wait.

1.3.3

Recovering from Programming Errors

you can obtain some
abnormally,
terminates
image
If a program
When a program image
the error from the message.
information about
the current value of general
uses
exits, the command interpreter

If it
0 to obtain information about the status of the exit.
register
is an abnormal (or error) exit, the system message associated with the
register

0 value

is displayed.

Programming errors can be

Incorrect coding

example

caused by:

arguments

for

called

procedures,

for

system services

in programming

Logic errors

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

The VAX-11 Symbolic Debugger can aid you in discovering and correcting
For details on how to use the debugger, see the
programming errors.

VAX-11 Symbolic Debugger Reference Manual.

INTRODUCTION

1.3.4

Reporting

When

has

occurred,

message

System Software

notifies

you

action

1is

VAX/VMS

submit

System Manager's

Software

Guide

Performance

The

VAX/VMS Operator's
Guide
utilities
that
can
verify
verify that a hardware device

not

operational,

inform

Hardware

Errors

that a system software or
hardware
required
by the system operator or

manager.

The

the

provides

Report

contains
the
is

information

(SPR).

status

information
of

operational.

system manager.

mass
If

the

error
system

how

on
how
to
run
storage volume or
hardware

device

CHAPTER

MESSAGES

ABFNAM,

ambiguous

function

name

Explanation:
characters

A lexical function name was truncated
to make the function name unique.

User Action:
Reenter
the
characters of the function

ABKEYW,

ambiguous

command;

specify

least

name.

qualifier

keyword

four

was
truncated
to
gqualifier name unique.

too

displayed

least

four

request

that

was

abort

Explanation:
1.

The

system

canceled
2.

attempted

returns

before

this

it was

operation was
status for
completed.

Following

a network request, this
link was disconnected.

logical
User

Action:

The

message;

user

the

return.

status

ambiguous

make

User

the

command

Action:

characters

operating

programs

I/0

status

system does

should

aborted:

not

coded

indicates

normally
detect

that

display

and

this

respond

verb

Explanation:
to

few

name

User Action:
The rejected portion of the
command
between backslashes.
Reenter the command;
specify
characters of the keyword or qualifier name.

ABVERB,

too

keyword

Explanation:
A keyword or
few characters to make the

ABORT,

Reenter

the

name

the

command

was

truncated

too

unique.

command;

name.

specify

few

characters

least

four

MESSAGES

ACC, ACP could not access file

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

The status value

User Action:
code

(STV)

field of the FAB contains

more information about the condition.

provides

that

Take

corrective action based on this status code.

ACCERR, non-blank accessibility field in volume labels on device-name

Explanation: The accessibility field on the tape mounted on the
This field
device indicated has a nonblank accessibility field.
the

tape.

denies access

User Action:

Mount the

qualifier

(you

must

protection privilege).

ACCONFLICT,

tape

with

the

/OVERRIDE=ACCESSIBILITY

the owner of the volume or have volume

file access conflict

1is associated with a status code
This message
Explanation:
An attempt to access a file failed
returned by I/0 functions.
with the current file
conflicts
access
of
type
because the
access.

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

ACCVIO, access violation, reason
PC=location,

PSL=XXXXXXXX

mask=xx,

virtual

address=location,

to a
from or write
read
Explanation: An image attempted to
in memory that is protected against the current mode.
location
by
This message indicates an exception condition and is followed
a register and stack dump to assist you in locating the error.
User Action:

message

Examine the PC and virtual address displayed in the

and check the ppogram listing to verify that instruction

operands or procedure call arguments are correct.

ACCVIO, compatibility mode access violation

Explanation:

An RSX-11M image attempted to

access

area

that
memory
contains the
In RSX-11M,
instruction.

The PC
space.
address
its virtual
outside
1is
error.
the
caused
address of the instruction that
the PC contains the address following the erroneous
This message corresponds to the RSX-1l1lM termination

User Action:

Determine the instruction or statement at which the

message MEMORY PROTECTION VIOLATION.

error occurred and correct the error.

MESSAGES

ACMINVOP,

invalid

accounting manager

Explanation:
message

code;

accounting manager

request

contained

or,

1itself

was

message is associated
accounting
routine.
display this message.

the

request

with
The

User Action:
Check for a
System Services Reference

ACNTOPN,

error

opening

ACNTWRT,

Examine

writing

the

operator's

the

accompanying

account

The

system

accounting

messages

file

messages

accounting
This

routine

message

cannot write

records

generally

ACP

too

Reenter

does

not

Explanation:
initialized.
system

ACPVAFUL,

Verify
as

Explanation:

This

returned

be serviced by
allocate
for
each

volume

has

sets

cannot

User Action:
qualifier in

name

specified

command;

for

an ACP

specify

requested in
a
the
specified

that

image

has

ACP

file

name

the

MOUNT
image

ACP

because

command
cannot
be
1is not an ACP, or a

page

an ACP.

not

for

assigned

not,

gather

full

with

request.

does

1If

SPR.

associated
QIO

information

virtual

submit

space

system ACP

control
a

image
and

address

message

file

the

possible

virtual

from

accounting

occurred.

information

MTAACP's

the

respond

has

User Action:
much

long

the

The ACP
Either

error

displayed

console.

name

User Action:
correctly.

the

these

file

file.

Explanation:
The file
than nine characters.

ACPTIME,

the
the

determine

opened.
Usually,
condition.

User Action:
None.
When this condition occurs,
routine closes the file and opens a new file.

ACP

This

the
system
not normally

file

could
not be
to correct the

how

Explanation:

ACPNAME,

invalid

system accounting routine could
not
open
This
message
1is
generally displayed on

file

indicate

error

status code returned by
operating
system
does

valid.

console.

User Action:
reason
the
will

not

programming
error.
See
the
VAX/VMS
Manual for coding specifications.

account

Explanation:
The
accounting
file.
operator's

request

have

the
to

status

enough

new

it,

a
more

code

volumes

memory

can

volume.

Because

additional

volume

handled.

Start
a
the MOUNT

different
command.

ACP

using

the

/PROCESSOR

MESSAGES

file activity precludes operation

Explanation:

An I/O operation was attempted while other file I/O

activity was in progress.

if
Modify the source program,
Note the condition.
User Action:
necessary,
to
detect and respond to the condition.
Correct the
program logic to avoid conflicting concurrent operations.
ADJARRDIM,

adjustable array dimension error

Upon entry to a FORTRAN subprogram, the evaluation
Explanation:
of dimensioning information has detected an array in which either

bound
1) an upper dimension bound is less than a lower dimension
2) the dimensions imply an array that exceeds the addressable
or

memory.

program.

displayed
information
traceback
where
the error occurred in your
Check the value of the expressions for
the
bounds
of

the

array

bad

area ID

Using the PC and
User Action:
with
the
message,
determine

AID,

the DIMENSION

in XAB

statements.

location

Explanation:
The allocation XAB on a create, display, extend, or
invalid area identification number
an
contains
operation
open
field.

User Action:

The STV

(status value)

field of

the

FAB

provides

the address of the XAB in error.
Verify that the call to the RMS
service was coded correctly.
Correct the field
and
repeat
the
request.

ALLOCFAIL,

index file allocation failure

Explanation:

The INITIALIZE command

User Action:

Reenter the command;

failed to allocate space

the
volume
for
the index file.
This message usually indicates
that too much space was requested for file headers.

specify a smaller

value

for

the /HEADERS qualifier.

ALN,

alignment options error

in XAB at location

Explanation:

The allocation XAB for a create or extend operation

User Action:

The status value

contains

an invalid

alignment boundary

the address of the XAB
service was coded

(STV)

in error.

correctly.

type.

field of

the

FAB

provides

Verify that the call to the RMS

MESSAGES

ALQ,

invalid

allocation

quantity

Explanation:
An invalid
allocation XAB or FAB.
User Action:
coded

Verify

correctly.

(negative,

SEXTEND)

allocation quantity was

that

the

For

file

call

the VAX-11l

creation

service

operations,

the

value

specified

value.
that the

For
value

file
extension
operations,
the
error
specified was less than or equal to 0.

characters

needed

identify

User Action:
of

AMBKEY,

the

Reenter

the

command;

than

keyword

truncated
to
keyword exists

type

ambiguous

least

Run-Time

four

characters

Procedure

been truncated to too few
context.
This message is
from
the
VAX-11
Common

Library.

User Action:
Correct
the
source
program.
characters in the keyword to make it unique.

ANSI

Specify

enough

format

Explanation:
the

too
few
that begins

keyword

Explanation:
The indicated keyword has
characters to make it unique within its
associated with a status code returned

maximum

keyword.

keyword

not

the

was
error

that

larger

the

indicates

Explanation:
A
command
keyword
was
characters to make it unique;
another
with the same characters.

ANI,

RMS

allowable
indicates

AMBIGKEYW,

specified

ANSI

The

records

standard

for

a magnetic

magnetic

tape

tape
(D

file

not

conform

format).

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

1/0).
AOP,

allocation

options

Explanation:
not

made

User Action:

The

error

create

status

the
address
of
the
VAX-11] RMS service was

APPENDED,
APPENDED,

input-file-spec
input-file-spec

Explanation:
The
message
records

User Action:

based

None.

location

requested
or

value

extend

(STV)

file
the
on

to
to

field

size

The message

the
that

appended to
of
blocks
of

the

input

FAB
the

output-file-spec
output~file-spec

is being
number
the

allocation XAB

could

operation.

XAB in error.
Verify
coded correctly.

appended
appended

An input
displays

appended,

XAB

allocation

during

The

(nnn
(nnn

an
or

the

blocks)
records)

output
file.
the number of

file.

informational.

provides

call

MESSAGES

AQBTIME,

ACP gueue

unstable

Explanation:
The system cannot start up the ACP specified
in
a
MOUNT
command
request.
This
message
indicates
an operating
system

software

User Action:
an

error.

Collect as much information as possible and

submit

SPR.

ARTRES,

reserved arithmetic

trap at PC

location,

PSL=XXXXXXXX

Explanation:

An unknown arithmetic exception occurred.

User Action:

This message should not occur.

inform

ASTFLT,

the

If it

system manager.

AST

fault,

SP=XXXXXXXX

does

param=xXxXxXxXxXxx,

PSL=XXXXXXXX,

target PC=location,

Explanation:
system
trap

The system attempted
(AST)
to
an
image,

occur,

PC=location,

PSL=XXXXXXXX

to
deliver
but the user

an
asynchronous
stack pointed to

garbage or was otherwise inconsistent, 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
and
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,

PC=XXXXXXXX

Explanation:
This
message
generally
indicating a software failure.

User Action:

accompanies

Take corrective action based

the

message

accompanying

message
(s) .

ATR,

attribute

error

read

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

Check

header

this

the status of

status

the

block may be bad.

disk or drive may be bad.

code.

device

and

repeat

the

request.

If the error occurs on many files,

Notify the

system manager.

The

the

MESSAGES

ATTCONSTO,

attempt

Explanation:
A
continue
from
attempted

successful

continue

from

condition
a

<call

continue

handling

from

completion

stop

procedure

LIBS$SSTOP;
a

that

noncontinuable

attempted

1is,

error

to
procedure

the
by

returning

status.

User- Action:

Using the traceback information or PC displayed
in
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
the

errors

the

that

they

have

corrected.

Otherwise,

read

nonexistent

record

error.

ATTREANON,

unit

nnn

user

attempt

file

they

should

resignal

file-name

location

Explanation:
READ

One

statement:

record

from

existed

following

relative

was

end-of-file

the

file

direct

file.

was

occurred

made

(the

specified

attempt

read

deleted),

errors

attempt

access

read

record

FORTRAN

nonexistent

either

read

relative

never

beyond

the

sequential

User Action:
Use the traceback information or the
PC,
together
with
the
1logical
wunit
number
and file name in the message to
determine
where
your
program
performed
the
READ
statement.

Verify

the

attempted,

ATW,

READ

and

statement,

that

statement

for

attribute

write

the

READ

additional
and

the

occurs

many

BACKSPACE

unit

nnn

file

user

RMS

attempt

The

files,

condition.
Take
Check the status of

header

the

block

disk

may

drive

may

corrective
the device

bad.

the

bad.

Notify

FORTRAN

error

file-spec

location

Explanation:
REWIND

for

a VAX-11

on the operation, the status value
(STV)
RAB contains a status code that provides

request.

during

system manager.

BACERR,

occurred

information
about
the
based on this status code.

repeat

access was
the
OPEN

error

User Action:
Depending
field
in
the
FAB
or

action

which
with

file.

Explanation:
A write error
to write a file header.

error

record number to
statement
agrees

One

appending;

rewind

while

statement:

following
BACKSPACE

VAX-11l

operation;

reading

the
1)

forward

RMS

occurred
was

detected

VAX-11

RMS

requested

during

attempted

error

detected

file

condition

error

opened

during

condition

record.

User Action:
If a VAX-11l RMS message
accompanies
the
message,
use
the
VAX-11l RMS message to determine the cause of the error.
Otherwise, use the traceback information or PC displayed with the
message

Check

that

was

locate

the

REWIND

opened

with

the

REWIND

statement

does

ACCESS=APPEND.

not

that

specify

caused

the

logical

error.

unit

MESSAGES

BADACP,

invalid syntax on /PROCESSOR qualifier

The keyword or file specification value specified
Explanation:
qualifier is not correctly specified.
/PROCESSOR
for the

Reenter the command;

User Action:

Language User's Guide,

refer to the VAX/VMS

Command

if necessary, for the correct syntax.

BADATTRIB, bad attribute control 1list

1is associated with a status code
This message
Explanation:
invalid code or size was specified
An
functions.
I/0
by
returned
file system ACP QIO
in the read or write attribute list for a
function.

Begin debugging
User Action: Check for a programming error.
procedures to verify the nature of the problem and to correct it.
BADBLOADR,

bad block address

with

called

Explanation:

The library procedure LIBSFREE_VM was

User Action:

Begin debugging procedures to verify the nature

an invalid virtual storage address.

the problem and to correct it.

BADBLOCKS,

invalid syntax in bad block list

Explanation:

The command syntax for the /BAD_BLOCKS qualifier is

invalid.

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

BADBLOSIZ,

in a command procedure.

bad block

Explanation:
request

for

size

The library procedure LIB$GET_VM was called with
zero

blocks

the

block size specified was too

large.

User Action:

If the block size requested was zero,

correct

the

If the size was correct, use the SET WORKING_SET
source program.
your
for
1limit
set
«current working
the
command to increase

process and retry the program.

BADBUG,

please report TRACE bug no.

message

nnn

indicates

internal

programming

Explanation:

This

User Action:

Collect as much information as possible and

error

in the traceback

SPR.

displayed

Include

facility.

the

in the message.

problem

report the bug number

submit
(nnn)

MESSAGES

BADCHKSUM,

bad

file

header

checksum

Explanation:
returned
by
invalid.

This
I/0

User Action:

Check

procedures

verify

the

keyword

BADDATCHK,

invalid

message
1is
functions.

for

associated
with
a
status
code
checksum in the file header is

The

programming
nature

error.

the

/DATACHECK

for

User Action:

specify

BADDELIM,

invalid

delimiter

Explanation:
message

User Action:

BADDENS,

the

Check

Reenter

unknown

value

Explanation:

The

800

nor

debugging
correct

/DATACHECK

qualifier

either

READ

WRITE.

for

command.

The

the

command.

spelling

grammatical

/DENSITY

value

qualifier

specified

for

tape

density was

neither

1600.

symbols

the

command;

specify

either

800

1600

image

Explanation:
The image header in an executable image
file
not
contain
symbols
required
by
the traceback facility.
message indicates an operating system problem.
User Action:
an

it.

command.

User Action:
Reenter
for the density.

BADDST,

the

occurred

portion

command

'string'

character

rejected

the

command;

following

invalid

displays

error.

the

and

qualifier

Explanation:
The keyword specified
was neither READ nor WRITE.
Reenter

Begin

problem

Collect

much

information

possible

and

does
The

submit

SPR.

BADDSTMAP,

failure

Explanation:
because
the

map

symbol

status

code

and

Map

User Action:

the

return

Section

Determine

status

code.

virtual

address

space,

SPR.

CREMAPSEC

The system
cannot
perform
system cannot map the symbol

Create

problem.

table,

Collect

the

status

(SCRMPSC)

the

reason

assume
much

from

system

status

XXXXXXXX

a
symbolic
traceback
table.
The hexadecimal
internal

<call

the

service.

associated

with

the

indicated

1is

anything

other

than

that

the

problem

possible

and

submit

information

lack

system
an

MESSAGES

BADDSTVBN,

symbol table VBN = nnn

image

image
The traceback facility cannot interpret the
Explanation:
indicates an
This message
for an executable file.
header
internal operating system error or an error in the linker.

Collect as much information as possible and

User Action:
an

Include

SPR.

BADESCAPE,

the report the virtual block number

submit
(VBN)

displayed in the message.

(nnn)

number

syntax error

in escape sequence

This
invalid.
Explanation: A terminal escape sequence is
message 1is associated with a status code returned by I/O
functions.

User Action:

Check the

Check for a programming error.

syntax for the escape sequence you are attempting to use.

BADEXE,

required

failure to open image file file-name

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

system error.

User Action:
an

Collect as much information as possible and

submit

SPR.

BADEXECLO,

failure to close image file file-name

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

operating

User Action:
an

Collect as much information as possible and

submit

SPR.

BADEXERAB,

failure to connect image file file-name

Explanation:
inconsistent

is
The format of the indicated executed image file
This
with that expected by the operating system.

User Action:

Collect as much information as possible and

message indicates an internal operating system error.

submit

SPR.

BADFILEHDR,

bad

file header

Explanation:

This message

associated

with

status

code

The message
request.
QIO
system ACP
file
from a
returned
example,
for
indicates that the file header format is invalid;
the structure is not consistent or the storage map indicates free
blocks.

the
Determine
a programming error.
for
Check
User Action:
statement at which the error occurred, using the
instruction or
debugger

if necessary,

and correct the error.

MESSAGES

BADFILENAME,

bad

file

Explanation:

name

This message

returned
from
a
string for a file
longer

than

syntax

nine

1is

associated

file
system
specification

with

status

code

ACP
QIO request.
The file name
contains illegal characters or is

characters.

User.-Action:
Check for a programming error.
Verify
that
file
name
strings
consist
only
of the characters A through Z and 0
through nine and that they are no longer than nine characters.

BADFILEVER,

bad

file

Explanation:
returned
indicates
greater

version number

This message

from
that

a
the

file
file

than

32727.

User Action:

Check

version

BADHDR,

numbers

symbol

for

are

table

associated

system
version

programming

specified

data

ACP
QIO
number in

that

with

error.

are

status

code

request.
The message
a file specification is

greater

Verify
than

that

32727.

image header

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

Collect

much

information

possible

and

submit

SPR.

BADIMGHDR,

bad

image

header

Explanation:
An image
within
a
process
1is

to be
not

executed with
the
RUN
command
in
the correct format and cannot

or
be

executed.

User Action:
image.
If
program

BADINDEX,

Verify that the specified
necessary,
recompile
or

ensure

invalid

that

syntax

Explanation:
invalid.

The

the

image

/INDEX

command

file

file
is
reassemble

an
and

the proper

executable
relink the
format.

qualifier

syntax

for

the

/INDEX

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

BADIRECTORY,

syntax

bad

directory

Explanation:
returned
indicates

the

file

and

reenter

file

This message

the

command.

format

1is

associated

with

status

from
that

a
the

file
system
ACP
QIO
request.
The
directory file specified is not valid.

1is

not

directory

the

directory

file

code

message
Either

contains

bad

User Action:
Check for a programming
error.
Verify
that
file specified is a directory.
1If so, verify the contents of
directory file using the DUMP command to
determine
whether

the
the
the

data.

file

valid

state.
2-11

MESSAGES

BADKEY,

'keyword'

invalid

keyword

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
error.
Use
the
HELP
command
or
Language User's Guide, if necessary,
reenter the command.

BADLIBREF,

invalid

library/common

a
spelling
or
grammatical
refer to the VAX/VMS Command
for the valid
keywords
and

reference,

library-name

Explanation:
An RSX-11lM image referred to a
library
area
that has been altered since the image was built
now inconsistent with the image.
User Action:

Rebuild

the

image

with

the

new

or
and

common
that is

common

library

area.

BADLOGIC,

internal

logic

error

detected

Explanation:

An unexpected

User Action:

Collect

BADOVR,

[at

internal

as much

location]

software

information

error

occurred.

as possible

and

submit

SPR.

unknown keyword

Explanation:
invalid.

The

command

User Action:
Use
Command
Language
keywords,

BADPARAM,

bad

and

on /OVERRIDE

for

the /OVERRIDE

reenter

A value

the

command.

specified

for

as a result of
that parameter

If this message occurs as a result of
ASCII
Output
(SFAO) system service,
contained

1is

value

If this message occurs
function, it indicates

string

qualifier

the
HELP
command
or
refer
to
the
VAX/VMS
User's
Guide,
1if
necessary,
for
the legal

parameter

Explanation:
valid.

syntax

qualifier

system

function

a call to a file
list options are
a
it

call
to
indicates

the
that

1is

not

system ACP
not valid.
Formatted
a control

unknown directive.

If this message occurs as a result of a call
to
a
control
function,
it
indicates
that
one
of
parameters is out of range or has a bad format.

network
ACP
the
function

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.

MESSAGES

BADPRO,

invalid

syntax

Explanation:
incorrect.

The

/PROTECTION

command

qualifier

syntax

for

User Action:
Type
HELP
SPECIFY
VAX/VMS
Command
Language
User's
correct

BADRANGE,

syntax,

bad

block

Explanation:
qualifier is

reenter

address

A
a

and

not

the

/PROTECTION

PROTECTION
Guide,
if

qualifier

or
refer
necessary,

to
for

the
the

command.

volume

block
number
specified
nonexistent block.

for

the

/BADBLOCKS

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

BADRET,

RETURN

was

issued

without

subroutine

Explanation:
A 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 flow of logic
in
the
indirect
file.
It probably contains a logic error.
Correct the
command file and reexecute it.

BADSTA,

bad

command
indirect

stack

Explanation:

The

user

stack

has

invalid

format

cannot

accessed.

User
Action:
Recompile
vyour
qualifier
to determine whether
of bounds.
debugger to

BADSTACK,

bad

If
this
does
determine where

stack

encountered

program
with
the
/CHECK=BOUNDS
an array is being referred to out

not
your

correct
the
problem,
use
program modifies the stack.

during

exception

the

dispatch

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

Explanation:
An RSX-11M image's SP points to an area
of
memory
that
1is outside the image's virtual address space.
This message
corresponds to the RSX-11M termination message BAD STACK.
User Action:
error

occurred

Determine
and

the

correct

instruction
the

error.

statement

which

the

MESSAGES

BADSTACK,

stack

has

been

overwritten

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

BADSTRUCT,

invalid

value

Explanation:
are

and

The

invalid

Check

UIC

legal

gualifier

values

for

the

/STRUCTURE

qualifier

the

program

and

make

the

necessary

syntax

Explanation:
The
member
portions
separated

only

the

User Action:
corrections.

BADUIC,

on /STRUCTURE

caused

by a

command contains
of
a
UIC
must

an invalid UIC.
The group and
both be specified and must be

comma.

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

BADVALUE,

nnn

syntax.

invalid

specification

Explanation:
An invalid
command qualifier value.

User Action:
grammatical
reenter

BADVOL1,

the

bad VOL1l

Explanation:
invalid

Check
error.
command.

ANSI

value

was

specified

the
command
Verify
the

string
correct

label

cannot process the
ANSI-labeled tape,

the

for
a
values

1indicated

spelling
or syntax

or
and

label

The protection encoded on a
the

for

itself

tape.
or the

tape

invalid;

Either the tape
hardware device

volume

the

is
is

bad
not

magnetic

or
1is
reading

1label

tape

ACP

not
an
the tape

properly.

User Action:
tape

BEGOFFILE,

Verify

foreign

beginning

Explanation:

the
file
beginning

This

the

volume

tape volume.
and

try

read

necessary,

mount

the

code

from

it.

file
message

system
ACP.
of the file.

1is

associated

backspace

with

operation

status

backed

the

User Action:
If you are reading backwards or backspacing a tape,
this
message
1indicates
that
the end of the data area has been
reached.
Modify the program to correct this condition.

MESSAGES

BITMAPERR,

BKES,

I/O

error

storage

bitmap;

volume

locked

Explanation:
I/0 error encountered
Existing
files
on
the
volume
operations, for example, create and

during
<can
be
delete,

User

the

Action:

them.

Submit

bucket

size

possible,

SPR.

too

large

remove

a
mount
accessed
are

files

Verify

coded

«correctly.

bucket

size

too

that
See

the

call

the

VAX-11

bucket

Explanation:
than

large

Record

XAB

The bucket

block

zero

This

message.

The

volume

usable

a VAX/VMS

User

Action:

must

The

booted

call

volume

not

cannot

system

volume
a

invalid

length

for
An

can

User Action:

Check

ensure

the

that

modified

BLOCKCNTERR,

after

block

number

that

the

INIT

service

mounted.

another

This
a

file

was

disk.

specified

programming
was

1is

The

warning
volume

the

ACP

blocks

ignore

block

error.

length

Specifically,

initialized

and

problem

the

was

exists.

perform
tape

not

the

read

that

and

differs
when

from
file

either

Either

Mount

the

same

status

request.

read.

probably

2-15

with

QIO

labels

indicates

record

problem

drive/controller
persists,

volume

Otherwise,

properly

associated

system

message

valid

hardware

was

(RAB/FAB)

blocks recorded in the trailer
read operation is deaccessed.

larger

not

error

indicates

Action:

bootable

PDP-11.

block

read,

Reference

initialization.

message

was

RMS

use

Explanation:
This
returned
from
a

User

the VAX-11

block

control

count

was

calculating

cannot

booted

value

for

service

for

Services

in the XAB

still

PDP-11,

invalid

RMS

rules

greater
maximum

disk.

control

Explanation:
field.

and

generated

this message.

BLN,

FAB
was
zero, the

location

the

message

field

that

bad;

Explanation:

reinitialize

the VAX-11

Management

size

32.

User Action:
Verify
coded correctly.

BLKZERO,

formulas

Manual.

BKZ,

and

(FAB)

Explanation:
The bucket size specified in the
than
32.
If the bucket size was specified as
record size is too large.

User Action:

not

operation.
but
other
possible.

tape

operation

bad.

message

the

number

opened

for

noise
the

code

The

tape
on

again.

record
is

bad

another

the

MESSAGES

BOF,

beginning of file detected

was
file
the
operation,
backspace
a
During
Explanation:
the file before the specified
at the beginning of
positioned
field
(STV)
The status value
number of blocks were backspaced.
in the FAB or RAB contains the number of blocks actually spaced.

User Action:
necessary,

Note the condition.

Modify the source program,

to detect and respond to the condition.

breakpoint fault at PC location, PSL=XXXXXXXX

BREAK,

Explanation:

instruction

A breakpoint

was

This

encountered.

indicates an exception condition that was not handled by
message
the condition handler and is usually followed by a display of the
at the time of the
stack
and
registers,
arguments,
condition
exception.

User Action:

Examine the PC and virtual address displayed in the

message to determine the instruction that caused the error.

BREAK,

compatibility mode breakpoint trap

Explanation:
message

An RSX-11M image executed a BPT instruction.

corresponds

RSX-11M

the

termination

message

This

BPT

EXECUTION.

User Action:

Determine the instruction or statement at which the

error occurred and correct the

BUFFEROVF,

error.

output buffer overflow

associated with a status code
1is
This message
Explanation:
An output string
returned from a system service request.
buffer
than the wuser
larger
returned by a system service was
provided to receive the string, and the string was truncated.
The

code.
status
a success
1s
this
None;
User Action:
operating system does not normally display this message.
BUFOVF,

command buffer overflow

Explanation:

A command string, including continuation lines,

longer than the buffer used by the command interpreter to store a

command before

User Action:

it parses

Simplify

it.

the

command

entering more than one command.

BUG,

and

reenter

it,

possibly

internal RMS error condition detected

Explanation:

An internal software error occurred.

User Action:

Collect as much information as possible and

SPR.

submit

MESSAGES

BUGCHECK,

internal

consistency

Explanation:

The

operating

failure.
User
an

Action:

failure

Collect

system

much

internal

network

Explanation:
VAX-11

RMS

error

A Data Access

while

attempting

Listener.
User Action:

Collect

status

SPR.

(The

internal

possible

condition

detected,

Protocol

violation

as much
value

information

SPR.

BUG_DAP,

noted

communicate

information

(STV)

field

the

default

Explanation:

User

Collect

CANCEL,

Action:

I/O

error
much

This

message

returned

I/0

functions.

the

before

image's

the

cannot

file

User

None.

Modify
the

the

The

information

Explanation:
specified.
attempted

file,
a

system

could

Action:

source

condition.

not

user-specified

file

that

and
RAB

Access

submit
contains

User's
Guide
the explanation

RMS.

possible

and

submit

with
or

could

program,

not

status

code

operation

was

the

request

1is

canceled

system

does

not

normally

output

file

buffer
be

output

contains

closed.

necessary,

during

information

Note

the

condition.

detect

and

respond

RAB

VAX-11 RMS could not
This
error
wusually
connect

nonsequential

the

Usually,

The

nonsequential

User

input

down.

source

connect

FAB

VAX-11

associated
An

operating

condition.

cannot

The
run

Action:

regarding

request.

message.

Explanation:
call for I/0

occurred

completed.

User Action:
display this

Remote

canceled

Explanation:

CCR,

internal

operation

detected

the

as possible

submit

invalid

SPR.

canceled

CCF,

directory

and

code=nnnn

was

with

DAP status code.
Consult
the
DECnet-VAX
interpret the status code; note, however, that
intended for users who are familiar with DAP) .

BUG_DDI,

DAP

software

file

than

file
for

one

connect
a
indicates
record

which

MSE

stream

block
was

Check for an error.
Note
program,
if necessary, to

RAB
that

I/0

not

the

detect

to
the

the
FARB
program

performed,

sequential

set.

condition.

and

respond

Modify

the

MESSAGES

CDA,

cannot deliver AST

Explanation: Not enough system dynamic memory is available for
VAX-11 RMS to deliver an error or successful completion AST and
the user program has disabled resource wait mode.

(STV)
User Action: Depending on the operation, the status value
field in the FAB or RAB contains a status code that provides
Take corrective
additional information about the condition.
action based on this status code. Modify the source program, if
necessary, to detect and respond to the condition.

CHN, channel assignment failed

Explanation:

VAX-11 RMS failed to assign a channel to

device

specified for an input or output operation. This message is
usually accompanied by a system message indicating the reason for
the

failure.

User Action: Take corrective action based on the associated
This message is based on the status value (STV) field
message.
of

the

FAB.

If the error results from an OPEN command, or following an @
command or RUN command, verify that the
(execute procedure)
volume containing the specified file is online and mounted.
forced exit

CLIFRCEXT, CLI

to
image
an
Explanation: The command interpreter forced
debugger
the
by
displayed
is
message
This
.
terminate abnormally

and another command is
when an image is interrupted by
indicating the image
message
this
entered. The debugger displays
is

terminated.

User Action:
CLOERR,

None.

The message is informational.

error

unit nnn file file-spec
user PC location

Explanation:
close

VAX-11

file

FORTRAN

User Action:

VAX-11

RMS

An error occurred
as

the

when

VAX-11l

RMS

action

based

attempted

result of a CLOSE or DELETE statement on

IV-PLUS.

Take corrective

the

associated

message.

CLOSEDEL, error deleting file-name

Explanation: An error occurred while a file was being closed
after a delete operation. 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

MESSAGES

CLOSEIN,

error

closing

Explanation:

input

error occurred while
message
is
wusually
indicating the reason for the

opened.

This

message

User

input-file-spec

Action:

Take

corrective

input

file

accompanied

was
a

being

VAX-11

RMS

failure.

action

based

the

associated

message.

CLOSEOUT,

error

closing

Explanation:
closed.

message

User

This

error

occurred

message

indicating

Action:

input-file-spec

Take

the

output

while

wusually

reason

for

corrective

the

action

output

file

accompanied

was
a

being

VAX-11

RMS

failure.

based

the

accompanying

message.

CLUSTER,

unsuitable

Explanation:
command

1is

cluster

The

cluster

either

too

maximum cluster size
volume;
the minimum
disk

factor

size
small

for any
size is

size
+ (255

specified
or

too

large

for

the

change

mode

The

the

that

volume is
1/100
the
size
calculated with the formula:

4096)

User Action:
Recalculate a cluster size for the
within the valid range and reenter the command.

CMODSUPR,

INITIALIZE
volume.

supervisor

trap,

volume

code=nnn,

PC=location,

PSL=XXXXXXXX

Explanation:
An image attempted to
execute
supervisor
instruction
and
does not have a
declared.

change

mode

change

mode
condition

handler

This message indicates an exception
and
is
usually
followed
by
a
display
of the condition arguments and
registers and stack at the
time
of
the
exception.
The
code
displayed in the message is the change mode code specified in the
instruction.

User

Action:

message

CMODUSER,

Examine

determine

change

mode

the
the

and

virtual

instruction

user

address

that

trap,

This

message

followed
stack

User

by
the

Action:

message

An
and

image
does

attempted to
not
have a

indicates

display

time

Examine

determine

the

the
the

exception
the

displayed
the

code=nnn,

PSL=XXXXXXXX

Explanation:
instruction

caused

PC=location,

execute a change mode to user
change mode handler declared.

condition

and

arguments,

usually

registers,

exception.

and

virtual

instruction

the

error.

that

address
caused

displayed
the

error.

and

the

MESSAGES

CoOD, invalid or unsupported type field in XAB at location

Explanation: The XAB at the indicated address contains an
invalid type code field, or the XAB at the specified address is
field of the FAB
(STV)
The status value
not a valid XAB.
provides the address of the XAB

User Action:

in error.

Verify that the call to the VAX-11l RMS service

was

coded correctly.

COMPAT,

compatibility

mode

(code

fault

location,

nnn)

PSL=XXXXXXXX

Explanation:

instruction,

illegal

Meaning

Code
SNonodkdWNhhEHO

execute

An RSX-11lM image attempted to

indicated by one of the following codes:

Reserved instruction execution
BPT instruction executed
IOT instruction executed
EMT instruction executed
TRAP instruction executed
Illegal instruction executed
0dd address fault
TBIT

User Action:

trap

Check

for

programming

make

and

error

any

necessary corrections.

COMPLX, expression too complex - simplify
an
analyze
cannot
interpreter
command
The
Explanation:
many
too
contains
it
because
command
a
in
expression
arithmetic

operators and/or parentheses.

User Action:

Simplify the expression and

reenter

If necessary, execute more than one command.

the

command.

CONCAT, type-of-input-file file cannot be concatenated
CONCAT, wildcard specification cannot be concatenated

Explanation: A COPY or APPEND command requested that input files
Only sequentially
of an wunsuitable format be concatenated.
organized files can be concatenated.

Or, a wild card was specified in an output file specification
indicate multiple output files and /CONCATENATE was specified.
User Action:

Reenter the command;

specify only files that

have

sequential organization.

Do not specify a wild card in the output
omit the /CONCATENATE qualifier,

CONFDEL,

file-name,

DELETE?

file

as required.

specification

(Y or N):

message

requests

interactive

confirmation

Explanation:

This

User Action:

Respond Y if you want the file deleted, N if not.

before deleting the

indicated file.

2-20

MESSAGES

CONFQUAL,

conflicting

qualifiers

Explanation:

Qualifiers

meanings

entered.

were

User Action:
Use
Command
Language

qualifiers

CONTROLC,

Explanation:
returned

I/O

under

message

complete

because

User

Action:

None.

output

completed

This

message

1I/0

functions.

not

complete

User Action:
display this

CONTROLY,

operation

Explanation:

completed

This
I/0

not

because

by
complete

User Action:
display this

COPIED,

input-file-spec
input-file-spec

COPIED,

Explanation:
The
number of records
User

ACP

Action:

could

not

Explanation:
returned

file

to
to

file

This
a

code

terminal

did

with

operation

system

status

the

does

with

operation

code

terminal

not

normally

message

status

the

terminal

code
did

pressed.

system

output-file-spec
output-file-spec

system

pressed.

I/O

displays
based on

message
file

output

associated

copied

create

not

1is

copied

The

status

the

informational.

operating

message
copied,

CTRL/Y

was

None.

from

could

under

The

with

associated
An

functions.

None.
message.

operating

message

returned

the
VAX/VMS
determine the

command.

operation

was

The

to
to

pressed.

1is

because

None.
message.

incompatible

CTRL/O

returned

the

I/O

message

under

or
refer
necessary,

associated

An
was

The

CTRL/C

1is

Explanation:

did

CRE,

reenter

functions.

not

CONTROLO,

and

completed

This

contradictory

the
HELP
command
User's
Guide,
if

conflict

operation

with

the
the

not

normally

(nnn

blocks)

(nnn

records)

number or
blocks
size of the input

or
the
file(s).

informational.

associated
ACP

does

QIO

with

request

made

created.

status
by

VAX-11

code
RMS.

User Action:
The status value (STV) field of the FAB contains
a
code
that
provides
more information about the condition.
Take
corrective action based on this status code.

CREATED,

output-file-spec

Explanation:

results

the

User Action:

This

created

message

creation

None.

The

displayed

new

message

2-21

when

command

file.

informational.

activity

MESSAGES

CREATED,

file did not exist - was created

system ACP
file
A system service, VAX-11] RMS, or
Explanation:
it currently exists) completed
(if
request to create a file
successfully with the creation of a new file.

User Action:

and respond,

CREQUEJOB,

The user program should be

None.

if necessary,

to this condition.

able

detect

error creating job on gueue queue-name

a
enter
to
failed
SUBMIT command
A PRINT or
Explanation:
The accompanying message
in the indicated queue.
job
requested
This message usually
failure.
the
indicates the reason for

indicates that the queue specified has not been set up for users'

jobs.

User Action:

Display the status of available queues

the command.

CTRLERR,

issuing

If the
reenter
If the error persists, notify the system operator.

the SHOW QUEUE/BATCH or SHOW QUEUE/DEVICES
1is
response indicates that the specified queue

fatal controller

command.
active,

error

This message
Explanation:
returned by I/O functions.

is associated with a status code
The hardware controller failed during

an input or output operation.

User Action:
command.

Check the status of

If the failure persists,

CUR, no current record

the

device

and

reenter

notify the system manager.

the

(operation not preceded by $GET/SFIND)

truncate,
A program attempted a VAX-1ll RMS delete,
Explanation:
update operation without having performed a successful get or
or
find

operation.

source
the
Modify
Check for a programming error.
User Action:
program, if necessary, to detect and respond to the condition.
DAC, ACP file deaccess error during CLOSE

is associated with a status code
This message
Explanation:
returned from a file system ACP QIO request made by VAX-1ll RMS.
The file was deaccessed.
An error occurred closing a file.

User Action: The status value (STV) field of the FAB contains a
Take
that provides more information about the condition.
code
corrective action based on this status code.

DATACHECK,

write check error

This message
Explanation:
by I/O functions.
returned

1is associated with a status code
The data in memory did not match the

data on disk during a data check operation.

User Action:

Note the condition.

Modify the source program,

This message
to detect and respond to the condition.
necessary,
If the error persists, notify the
may indicate a hardware error.
system

manager.

MESSAGES

DATAQOVERUN,

data

overrun

Explanation:
returned
®

I/0

data

could
@

This

message

1is

functions.

can

indicate

the

user

buffer

was

read

into

associated

reader data was written in
the
before the driver was able to receive

User Action:
the

reader

Specify

existing

operation,

larger

buffer.
resubmit

buffer
If

the

command

interpreter

debugger

buffer

controller

data

buffer

the

data

the

signal

User
use

DECOVF,

Action:
of

the

Link

the

symbolic

arithmetic

Explanation:
condition.

command
was not

image

was
listed

with

the

was

reader

decimal

A decimal

overflow

DEFOVF,

too

many

symbols

User Action:
Reenter
eight parameters.

RFA-accessed

Explanation:
previously

User

DELETED,

procedure

the

was

record

file-name

Note

qualifier

arithmetic

the

detect

invoked

enable

overflow

the
message
operands
or

not

with

than

specify

than

file

address

was

source

program,

deleted

accessed

condition.

and

respond

record's

Modify
to

the

condition.

deleted

Explanation:
file that was

The message displays the
successfully deleted.

User

None.

Action:

after
debugger.

displayed
in
verify
that

was

command;

deleted.

Action:

necessary,

record

defined

Explanation:
A command
eight parameters.

DEL,

card

PC=XXXXXXXX,PSL=XXXXXXXX

caused

User Action:
Examine the PC location
and
check
the
program
1listing
to
variables are specified correctly.

long
a

location,

debugger.

trap,

too
on

card

issued
with the

/DEBUG

data

occurred

PSL=XXXXXXXX

Explanation:
The
DEBUG
interrupted an image that

code

user

reread.

DEBUG,

status

the

problem

card(s)

that:
than

hold

Card

for

with

The

message

file

specification

informational.

MESSAGES

DELINTERR,

internal error in DELETE/PURGE utility

Explanation:

An unexpected error occurred during DELETE or PURGE

User Action:

Submit an SPR.

command processing.

DELVER, explicit version number of wild card required

The DELETE command requires

Explanation:
file

each

version

number

specified.

the explicit
Specify either
Reenter the command.
User Action:
version number for the file you want to delete or use a wild card
in the version field.

DEV,

bad device, or

inappropriate device type

the
correctly;
specified
not
A device name was
Explanation:
specified is not supported by this system, or the type of
device
(for
operation
requested
the
perform
device specified cannot
an attempt was made to create a random access file on a
example,
sequential device).

If the error occurred while a command was being
User Action:
the device
and spelling of
syntax
the
verify
entered,
1logical
a
if
name,
logical
the
or
specification
1image
occurred while an
the error
If
specified.
coded
executed, check that the file specification was
that the logical name, if any, was assigned before
and

was
name
was being
correctly
the image

executed.

was

Iis
the device
and
If the device name is correctly specified,
valid for the requested type of operation, verify that the device
is

available

DEVACTIVE,

device

in your

system.

is active

code
status
a
associated with
is
This message
Explanation:
A set mode function is inconsistent
returned by I/0 functions.
system does
The operating
with the active state of the device.
not normally display this message.

User Action:
necessary,

DEVALLOC,

Note the condition.

Modify the source program,

to detect and respond to the condition.

device already allocated

to another

user

the
An attempt to allocate a device failed because
Explanation:
allocated by another user or channels are assigned to
is
device
it.
Only one user can access an allocated device at a time.

the
deallocated
has
Wait until the current owner
User Action:
reenter the request specifying a different device of
or
device,
allocate
the
the same type, or specify a generic device name in
request.

MESSAGES

DEVALRALLOC,

device

already

allocated

this

job

Explanation:
The process has already allocated the device
(this
message
1s
a
success
status
message from the Allocate Device
System Service).
User Action:
error;

DEVASSIGN,

Depending

action

device

has

the

program

logic,

this

may

not

because

the

necessary.

channels

Explanation:
A request
device has I/O channels
being read or written.

assigned

deallocate

assigned

device

it;

that

failed

is,

currently

User

Action:
Verify the device
name
(or
1logical
name,
if
a
logical
name
was
specified)
and
reenter the command with the
correct device name.
If any executing subprocesses are using the

device,

wait

deallocate

DEVFOREIGN,

wuntil

the

they

have

terminated

before

device

mounted

was

User

Files-11l.

Action:
or

DEVICEFULL,

RT1l

Remount
format,

device

full

Explanation:
returned

specified

the

use

This

from

space cannot
or a request

foreign

Explanation:
A Files-11 operation
which is mounted foreign.

DOS

attempting

device.

device

FLX;

otherwise,

allocation

message
file

attempted

write

If
a

the

device

medium

program.

failure

1is

associated

system ACP

QIO

with

request.

a
It

status
indicates

code
that

be allocated for a file because the device is
full;
for contiguous space cannot be satisfied because the

number

contiguous

User Action:
Verify the
private
device,
purge

blocks

are

status
of
the
unwanted
files

not

available.

device.
with the

If
it
is
a
PURGE command.

Otherwise, obtain another volume to catalog files.
If the device
is
a
system
device, notify the system operator or manager that

the

DEVICES,

volume

only

one

full.

device

Explanation:
command.

Only

User Action:
device.

allowed

than

one

disk

volume

Reenter

the

disk

MOUNT

device

can

was

specified

mounted

command

time.

specifying

only

MOUNT

one

disk

MESSAGES

DEVMOUNT,

device

1is already mounted

Explanation:
The device specified has a volume mounted on it and
cannot
be
allocated, or a volume is already mounted on a device
for which a mount request was

issued.

User Action:
Verify the device
name
(or
1logical
name,
if
a
logical
name
was
specified)
and
reenter the command with the
correct device name.
If the device
name
is
correct,
and
the
volume that is mounted can be dismounted, dismount the volume and
reissue

DEVNOTALLOC,

the

request.

device

Explanation:
currently

not allocated

A device specified in a deallocate request

allocated.

not

User Action:
Verify the device
name
(or
1logical
name,
1if
a
logical
name
was
specified)
and
reenter the command with the
correct device

DEVNOTERM,

name.

illegal

source operator

device

Explanation:

A REPLY command requested that a device that is not

User Action:

Reenter

a
terminal be enabled as an operator terminal;
REPLY/ENABLE command was issued in a batch job.

DEVNOTMBX,

device

the command

for

example,

the

from a terminal.

not a mailbox

Explanation:
This message
is
associated
with
a
status
code
returned from a system service request.
An I/O channel specified
in a system service
request
1is
not
currently
assigned
to
a
mailbox.
The service requires that the device be a mailbox.

User Action:
Check for a programming
error.
Verify
channel number specified for the service is valid.
DEVNOTMOUNT,

device

DEVOFFLINE,

device

Reenter
is

the

not mounted

Explanation:
This message is displayed if you
command for a device that is not mounted.

User Action:

that

issue

DISMOUNT

the command with the correct device.

offline

Explanation:
This message is displayed on the operator's console
when a device in the VAX/VMS system configuration goes offline.

User Action:
online,

Take

appropriate

necessary.

measures

bring

the

device

MESSAGES

DEVONLINE,

device

online

Explanation:
when a device

This message is
becomes online.

User Action:

None.

DIAGPACK,

disk

Explanation:
volume
that
cannot

another

DIF

—~

Do not

volume

from

NOT

DIF

—=~

must

use

ASTERISKS

wild

The

User Action:

DIF

-=—

must

use

DIF

-—

Action:

must

use

EOF ON

file

—-—-

ILLEGAL

wildcard

(*)

appears

the

file

the

FILE

command

file

supplied

SPECIFICATION

the

input

explicitly

file

supplied

line.

FILE

1in

specification must
Reenter

compare

explicitly

OUTPUT

appears

SPECIFICATION

the

command

PART

request

line.

INPUT

appears

the

FILE

command

PART

necessary,

SPECIFICATION

the

output

explicitly

file

supplied

line.

file-name

Submit

STATUS

The

error

console

manager.

COMPARE

specification must
Reenter

ACCEPTABLE

Explanation:
code

If
or

specification must

Explanation:
An internal
the DIFFERENCES command.

DIF

(*)

The

User Action:

PART

Reenter

defaults.

FILE

wildcard

Explanation:
A
specification.
User

volume.
operator

The

NOT

the

card

defaults.

ASTERISKS

operator's

informational.

system

ACCEPTABLE

Explanation:
A
specification.

wuse
the

defaults.

NOT

the

pack

ACCEPTABLE

Explanation:
A
specification.

User Action:

INITIALIZE command was entered to
initialize
a
identified
as a diagnostic volume.
The volume

used.

ASTERISKS

message

diagnostic

An
is

User Action:

The

displayed

file
when

failure

occurred

during

execution

SPR.

FOR

system

returned

attempting

User Action:
No user action is required;
meaning of the error code, see Appendix A.

File
the

Control

Services

file.

however,

find

the

MESSAGES

DIF

I/0

STATUS

BLOCK

Explanation:

File

A read or write operation incurred an

Control

status

ERROR CODE

Services

status

error.

The

status

code,

code of nn was placed in the I/0

block.

I/0

To determine the meaning of the

User Action:

see Appendix A.

DIF

-—- NO COMPARE

FILENAME OR DEFAULT NAME

SPECIFIED

Explanation:

The file specification for the

User Action:

Reenter the command line supplying an explicit file

not contain an explicit

name
and
file
use, by default,

compare

file name.

file

does

type, or omit the compare file specification and
the next lower version of the input file.

DIF -- NO COMPARE FILENAME OR DEFAULT NAME SPECIFIED ON OPNFIL CALL

DIF

Explanation:

User Action:

Submit an

internal failure occurred in DIFFERENCES.

NO COMPARE FILE

Explanation:
explicit

file

SPR.

TYPE OR DEFAULT TYPE

SPECIFIED

The compare file specification does not contain
type.

User Action:
Reenter the command
specifying
an
explicit
file
name
and
file
type, or omit the compare file specification and
use, by default, the next lower version of the input file.
DIF --

INPUT

FILENAME

Explanation:

The

User Action:

Reenter the command

explicit

name

DIF -- NO

and

file

INPUT

SPECIFIED

input file specification does

type.

FILE NAME

specifying

OR DEFAULT NAME

An internal failure occurred

User Action:

Submit an SPR.

INPUT

FILE

command.

TYPE

Explanation:

The

explicit

type.

file

User Action:
type.

OR DEFAULT

FILE

the command

explicit

during

file

execution

contain

TYPE

input file specification does

Reenter

contain

SPECIFIED ON OPNFIL CALL

Explanation:

not

name.

the DIFFERENCES

DIF

OR DEFAULT NAME

specifying

not

explicit

file

MESSAGES

DIF

OUTPUT

FILENAME

Explanation:
explicit file

DEFAULT

The output
name.

file

SPECIFIED

specification does

not

contain

User Action:
Reenter the command
wusing
the
/OUTPUT
qualifier
followed
by
a file specification with an explicit file name and
type, or omit the /OUTPUT qualifier and, by
default,
write
the
output
to a file with the same file name as the input file and a
file type of DIF.

DIF

OUTPUT

FILENAME

Explanation:
the

DIFFERENCES

User Action:

DIF

OUTPUT

internal

NAME

failure

SPECIFIED

occurred

OPNFIL

during

CALL

execution

contain

command.

Submit

FILE

Explanation:
explicit file

DEFAULT

an SPR.

TYPE

DEFAULT

The output
type.

file

TYPE

SPECIFIED

specification does

not

User Action:
Reenter the command
wusing
the
/OUTPUT
qualifier
followed
by
a file specification with an explicit file name and
type, or omit the /OUTPUT qualifier and, by
default,
write
the
output
to
a
file with the same file name and as the input file
and a file type of DIF.

DIF

VERSION

FILE

filename

Explanation:
The command
1line
does
not
contain
compare
file specification, and no previous version
file exists to use as the default compare file.
User Action:

DIF

RECORD

Reenter

SIZE

Explanation:
large

for

message
was

command

LARGE

that

compare

the

BUFFER

the

input

command

file

files

is
on

explicit
the input

line.

FOR

either

DIFFERENCES

indicates
to

TOO

record

the

made

the

an
of

compare

handle.

corrupted

magnetic

tape,

that

file

Usually,

too
this

attempt

which

1is

not

possible.
User Action:
reenter

DIF

the

STANDARD

Determine

whether

the

file

1is

corrupted,

SYSTEM

OPEN

ERROR

CODE

FILE

filename

Explanation:
During an attempt to open the designated
RSX-11M
directive
failure
occurred.
The value of nn
the

cause

and

command.

the

file,
an
indicates

error,

User Action:
Determine whether the
file
exists.
exist, look up the error code in Appendix A.

does

MESSAGES

DIF

—--

UNABLE TO CLOSE

FILE

filename

Explanation:
The file system is unable to close
the
designated
file.
Probably
an
open error occurred;
the file could not be
closed because it never was opened.
The system
will
close
the
file when the DIFFERENCES command terminates.
User Action:

DIF

-—

UNABLE

None.

Explanation:
The
designated
file.
DIFFERENCES

AND

DELETE

FILE

filename

file system is unable to close and
delete
The
system
will
close
the
file
when

command

terminates.

User Action:
Change the protection on the
file,
and use the DELETE command to delete the file.

DIF

——-

UNABLE TO CLOSE

Explanation:
The
designated file.

AND SAVE

-—-

UNABLE

TO OPEN

Explanation:
file.

The

the

FILE

The

file

FILE

file system
Probably an

User Action:
Reenter
specifications.

DIF

——-

UNABLE

Explanation:
The file may

READ

is unable to
close
and
input file did not exist.

command

system

not

FILE

specifying

correct

exist or

unable

may

locked.

file

open

—-—

UNABLE

Explanation:

The

User Action:

TERMINAL

output

file
could
not
be
closes the file when
None.

input

the

file

the

designated

use

filename

The file system cannot read
the
be read protected or a read error

RELEASE

save

specification or

designated
file.
may have occurred.

User Action:
Change the protection on the
file
access, if necessary, and reenter the command.

DIF

necessary,

filename

User Action:
Either enter the correct
the UNLOCK command to unlock the file.

DIF

filename

file

may

the
the

file

allow

read

terminal.

The

CHANNEL

was

assigned

closed.
The system releases the channel
the DIFFERENCES command terminates.

and

MESSAGES

DIF

UNABLE

WRITE

FILE

filename

Explanation:
The file system is
The
device may be write-locked,
user

may

not

have

the

disk

may

User Action:
corrupted,

error

Either

are

the

VFY2

the

output

privileged

directory

example,

remove

VFYl

Change

Explanation:

write

the

output

directory,

full.

run

corruption.
to which you

DIR,

privileges

unable to write the output file.
the volume may be corrupted, the

write-lock
to

file

or,

determine

the

specification

volume

extent

directory

than

characters.

one

directory

write.

name

Or,

use

name

was

specified

subdirectory

the

name

logical

file

incorrectly.

string

name

directory

Explanation:
for

DCL

that

expects

The

resulted

specification.

name
name

in
was

syntax

directory

command

For

contained

User Action:
Verify the syntax of either the directory
the file specification or the logical name, if a logical
specified.

invalid

is
the

name

than

DIRECT,

name

contains

directory

name

file

illegal

string

specification

character.

did

not

find

Or,

entered
a

square

command
brackets

([
1)
or angle brackets (< >)
in the specified parameter.
Note
that this error can occur if a physical device name is
specified
without a colon terminating it.

User Action:
Verify the directory name (or logical
logical
name
was
specified) for a spelling error.
directory syntax and reenter the command.

DIRFULL,

directory

Explanation:
returned

indicates

This

associated

system

that

error

occurred

1024

blocks.

associated

repeat

with

a DECnet
of

Delete
the

ACP

QIO

while

with

operation,

declared

purge

request;

network

unwanted

specify

disk
is
of a

status

code

file

was

being

this

message
is

files

from

different

into

The

message

full
and cannot
directory
file

names

output file;
or, organize the directory
to obtain more cataloging space.

request.

the
directory
specified
entries.
The maximum size

directory

User Action:
and

1is

file

the

message

because
any more

that

full

from

created
catalog

name,
if
a
Correct the

indicates

full.

the

directory

subdirectory

for

the

levels

MESSAGES

DIRTOOBUS, directory is presently too active to be purged

the directory
A purge operation can only occur if
Explanation:
for example, if
is being extensively modified at the same time;
an application program is transferring files in and out of memory
at

rate.

fast

directory

Perform the purge operation when the

User Action:
idle.

DME,

dynamic memory exhausted

RMS
Available memory was exhausted during a VAX-11l
Explanation:
Either the related I/O segment in the control region
operation.
the
file;
is too full for direct access to a process permanent
region

program

many indirect

cannot

command

wused for

levels;

or,

I/0 buffers;

the

program

too

there are

has

reached

virtual memory limitations.

excessively
not grown
Check that the program has
User Action:
Relink the image to
as the result of a programming error.
large
image
allow VAX-11 RMS buffers in the program region or a larger
I1/0 section.

DMP

—--

See the VAX-11 Linker Reference Manual.

bad device name

A file specification contained

Explanation:

invalid

device

name.

Check the

User Action:

device

logical name was specified),

DMP

—- cannot

find

Explanation:

name

(or

and reenter

1logical

the command.

1if

name,

input file

The requested input file cannot be located

specified directory.

the

User Action:
Check the device and
directory
name
(or
logical
name, if a logical name was specified), and reenter the command.

DMP

failed

to assign LUN

file
a
in
specified
was
An illegal device name
Explanation:
VAX/VMS could not assign a channel to the device.
specification.
name,
logical
(or
name
device
Check the
User Action:
logical name was specified), and reenter the command.
DMP

-—

failed

Explanation:
access

read

the

1if

attributes

The file's protection code does not allow you
file,

read

SET
the
wuse
file,
the
of
If you are the owner
User Action:
Or, reguest
<change the protection code.
to
command
PROTECTION
read
the owner of the file to change the protection to allow you
access.

MESSAGES

DMP

I/O
I/O

error
error

input file
output file

Explanation:

One

the

output

file

The

physical

device

The

file

been

The

output

User

has

the

from

Reenter

wild

the

User Action:
to be dumped.

Enter

file

DUMP

file

open

failure

input

open

failure

output

file

The

named

file

®¢

The

volume

The

specified

The

physical

User Action:
correct it.

the

read

User
call

DNF,

FAB
by

does
not

the

bad

caused

the

message

contained

command

once

for

wildcard.

each

file

you

want

following

against

not

conditions

prevented

the

file

access

exist

the

specified

directory

does

not

file

not

ready

condition
command.

specification

default

file

valid,

exist

caused

the

message

not

specification
is

caller.

string address field
area of memory that cannot

specified

directory

User Action:
Verify that
both
specified
correctly.
Create
or

that

the

exist on

the

found

Explanation:
The
specified device.

necessary,

and

string

Action:
Check for a programming
error.
Verify
to the VAX-11 RMS service was coded correctly.

directory

and

mounted

device

not

format

file

directory

The
is

its

condition

Determine which
Reenter the DUMP

Explanation:
in

the

protected

default

input

malfunctioning

command.

the

The

the

allowed

DMP

ready

specification

Explanation:
One of
from being opened:

prevented

opened:

full

cards

Explanation:

invalid

not

conditions

properly

corrupted

DMP

DNA,

following
being

Determine which

it.

lists

volume

Action:

correct

DMP

on
on

specify

name

does

the
device
directory

existing

directory.

not

and
on

directory
are
device, if

the

MESSAGES

DNR,

device not ready or

Explanation:
the
because
volume

not mounted

input/output
An
device
physical

performed
be
cannot
operation
not yet ready or the required
1is

has not been mounted.

Make sure that the volume is physically loaded, the
User Action:
command for the device
MOUNT
the
that
and
ready,
1is
device
Check that the correct controller is set
completed successfully.
on the drive.

DPE,

Retry the command or program.

device positioning error

code
status
a
with
associated
is
This message
Explanation:
returned
from
a file system ACP QIO request made by VAX-1ll RMS.

A magnetic

tape

file

is not positioned properly.

User Action:
Depending on the operation, the status value
(STV)
field
in
the
FAB
or
RAB contains a status code that provides
corrective
Take
condition.
the
about
additional information
If the
Retry the operation.
on this status code.
based
action
error persists, it may indicate a
system
software
or
hardware
failure.

DRVERR,

Notify your

system operator

manager.

fatal drive error

code
status
a
with
associated
1is
This message
Explanation:
An input or output operation failed
by 1I/0 functions.
returned
because of an error in the device driver,
the
reenter
and
device
the
Check the status of
User Action:
on and loaded or mounted
1is
drive
the
that
Verify
command.
correctly.
If the failure persists, notify the system manager.
DUPDEVSPC,

duplicate device specified

Explanation:
The same tape device was specified more
in a list of tape devices for the MOUNT command.

User Action:
only

Reenter the MOUNT command

specifying

than

each

once

device

once.

DUPFILENAME,

duplicate

file

name

Explanation:
This message
1is
associated
with
a
status
code
returned
from
a
file
system
ACP
QIO request.
The directory
specified already contains an entry for the specified file
name,
file

type,

and version number.

User Action:
program
to
specified

for

Delete the existing file, or correct the command or
change
the
file name, file type, or version number
the output

file.

MESSAGES

DUPFILSPE, duplicate file
unit nnn file file-spec
user PC location

specifications

Explanation:
A DEFINEFILE statement (in VAX-11] FORTRAN
IV-PLUS)
was
followed
by another DEFINEFILE or an OPEN statement for the
same file without an intervening CLOSE statement.

User Action:
the
message
where

your

©Use
and

the
the

program

traceback information or
PC
logical unit number and file
performed

the

second

displayed
in
name to locate

DEFINEFILE

OPEN

statement.
Verify the logical unit numbers;
if the same file is
required, either delete the statement in error or insert a
CLOSE
statement.

DUPLNAM,

duplicate

process

name

Explanation:
A process name specified in a request to
create
a
process duplicates the name of an existing process executing with
the same group number.
Process names must
be
unique
within
a
group.

User Action:
the existing
use the STOP

DVI,

invalid

device

Explanation:
NAM block is

User Action:
coded

Specify an alternative process name.
Check whether
process with that name should be deleted and, if so,
command to delete it.

field

in NAM

The device
not valid.

Verify

that

block

identification

the

call

field

the

VAX-11

RMS

the VAX-1l1l

RMS

service

was

correctly.

ENDDURREA, end-of-file during
unit nnn file file-spec
user PC location

read

Explanation:
Either an end-of-file record produced by an ENDFILE
statement (in VAX-11l FORTRAN IV-PLUS) or a VAX-11l RMS end-of-file
condition occurred during a READ statement and
neither
an
ERR=
nor an END= transfer specification was included.
User Action:

Correct

the

program

include

ERR=

END=

specification
to detect and respond to an end-of-file condition.
Or, check the program that created the file to determine that all
expected

ENDFILERR,

unit

nnn

user

records

ENDFILE

file

were

created.

error

file-spec

location

Explanation:
An
end-of-file
record
produced
by
an
ENDFILE
statement
(in
VAX-11]
FORTRAN
IV-PLUS)
cannot be written to a
direct access
file,
to
an
unformatted
sequential
file
that
contains
fixed
or
variable
1length
records, or to a file with
relative organization.

User Action:
Locate the statement in your program that performed
the
ENDFILE
statement.
Either delete the ENDFILE statement or
correct the OPEN statement for the file in question so
that
the
organization 1is sequential and the record type is segmented.
2-35

MESSAGES

ENDOFFILE,

end

file

Explanation:
returned
by
conditions:

This message
1is
I/0
functions.

tape mark

attempt

status
code
the
following

No data

The

file

for

a virtual

empty

available

system ACP

I/O

during

tape

An end-of-file card was
from the card reader

with
under

indicating end-of-file was encountered
read

mailbox

associated
It
occurs

encountered

had

for

during

end-of-file

transfer

encountered

the

attempt

read

allocated

space

written

the DMC-1l1
end

the

operation

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

ENDOFTAPE,

end

tape

Explanation:

This message
by I/0 functions.

returned
end

the

input

tape

were

1is
associated
with
a
status
code
A series of tape marks indicating the
encountered.

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

ENT,

ACP

enter

1if

function

program,

failed

Explanation:
This message
is
associated
with
a
status
code
returned
from
a file system ACP QIO request made by VAX-11l RMS.
An attempt to enter a file specification in a directory failed.
User

Action:

The

code

that

provides

corrective

ENTQUE,

error

action

entering

Explanation:
batch job in
User Action:
failure.

ENV,

support

for

status value
more

based

job

(STV)

this

code.

status

the
the

FAB

contains

condition.

Take

gueue-name

The input card reader
the indicated queue.

organization

about

queue

Accompanying

field

information

messages

feature

symbiont

could

indicate

not

the

included

enter

reason

build

for

this

that

was

RMS

Explanation:
not included

An image attempted a VAX-11l
in the current system.

User Action:
Consult
the
functions are supported.

system

RMS

manager

function

find

out

which

MESSAGES

EOF,

end

file

Explanation:

end-of-file

condition

occurred

VAX-11

RMS

program,

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

ERRDURREA, error during read
unit nnn file file-spec
user PC location

Explanation:
A VAX-11 RMS error occurred
operation (in VAX-11 FORTRAN IV-PLUS).
User

Action:

VAX-11

ERRDURWRI,

Take

corrective

RMS

message.

error

during

action

based

during

READ

the

or ACCEPT

accompanying

write

unit nnn file file-spec
user PC location
Explanation:
WRITE,

User

TYPE,

Action:

VAX-11

ESA,

VAX-11
or

RMS

invalid

Take

expanded

block

cannot

coded

ESL,

ESS,

The
is

fatal

the

Action:

action

based

expanded

string

the

Verify

The

that

area

address

the

IV-PLUS).

the

accompanying

call

name

string

length

expanded
Verify

string

value

the VAX-11

area

memory

as
required;
specification.

logical

expanded

caller,

Check

contains

address

the

VAX-1ll

RMS
that

the

service

was

the VAX-11

RMS

translation.

length

field

zero;

the

operation

attempted

string.
that

the

too

short

call

the VAX-1l

string

area

Explanation:
The user buffer provided
file specification string is too short;

coded

condition

FORTRAN

RMS

service

was

correctly.

expanded

User

error

VAX-1l

address

invalid;

expanded

Dblock

requires

coded

string

correctly.

Explanation:

User

corrective

(in

read or written by the
contains an invalid file

Action:

invalid

NAM

detected

statement

address
User

RMS

message.

Explanation:
NAM

Action:

Verify

correctly.

that

the

call

to
receive
the string

the VAX-1l1

RMS

an
does

expanded
not fit.

service

was

‘

MESSAGES

EXITSTATUS,

RSX-11M exit with

status

Explanation:
An RSX-11M image terminated by issuing an EXIT WITH
STATUS
directive
specifying
an exit status of normal, warning,
error, or severe error
termination.
The
symbols
$STATUS
and
$SEVERITY
contain
the
termination
status
and
severity code,
respectively.
User Action:
This
message
does
not
necessarily
indicate
an
abnormal
termination
of
the image.
You can display the status
with the DCL command SHOW SYMBOL/GLOBAL, or you can test
$STATUS
or S$SEVERITY with the DCL command IF or the MCR directive .IF.

EXP,

file

expiration date

Explanation:
attempt
was
expired.

This
made

User Action:

If the

not

yet

reached

message
1is
returned
by
VAX-11],
RMS.
An
to overwrite a magnetic tape file that has not

file can be overwritten,

remount the

with the /OVERRIDE=EXPIRATION qualifier (you must
the
volume
or
have
the
VOLPRO
privilege
to
expiration date).
Otherwise, use another volume.

EXPSYN,

invalid expression

volume

be the owner of
override
the

syntax

Explanation:
An arithmetic expression in a DCL
command
1is
not
syntactically
correct;
the
command interpreter cannot analyze
the expression.
An invalid expression can occur as a result of:
@

Missing

operators

Unmatched

Undefined symbol
string data

between values

symbol

names

parentheses

names

that

are being

interpreted

character

User Action:
Examine the expression for any of the errors
above.
Correct the expression and reenter the command.

EXQUOTA,

listed

exceeded quota

Explanation:
An image could not continue executing or a
command
could
not
execute
because
the process has exceeded one of its
resource quotas or limits.
This message can indicate the
failure
to
«create
a
subprocess
because
deductible
quotas,
when
subtracted
from
the current
quotas of the creator,
would
not
leave
the
minimum
required
quotas for the creator.

User Action:
Use
the
DCL
command
SHOW
PROCESS/QUOTAS
to
determine
the
current
quotas
and to determine which quota was
exceeded.
Determine whether any subprocesses are hibernating and
no
longer
performing
useful
functions;
delete
any
such
subprocesses.

If a program fails consistently
contact
your
system
manager
increased.

because of
insufficient
gquotas,
and
request
that your quotas be

MESSAGES

EXT,

file

extend

failure

Explanation:
This message
1is
associated
with
a
status
returned
from
a file system ACP QIO request made by VAX-11
The requested extension of a file cannot be performed.

code
RMS.

User Action:
The status value (STV) field of the FAB contains
a
code
that
provides
more information about the condition.
Take
corrective action based on this status code.

EXTERNABRT,

external

Explanation:
An RSX-11lM image was
aborted
by
issuing
either
a
Force Exit ($FORCEX) system

another
service,

directive,

MCR.

User Action:

FAB,

abort

invalid

FAB

STOP

command

None.

(block

from

The message

identifier

either

DCL

informational.

not=FAB$SC_BID

FAB

Explanation:
The specified VAX-11l
RMS
block
does
not
1indicate that the field is a FAB, or
memory that can be written by the caller.
User Action:
correctly.
operations

Verify
An
to

initialized
and
overwritten during

FAC,

record

that

attempt
an
RAB.

operation

the

call

that

opened
the

error

message
reading,
writing.

not permitted

results

error

parameter

occurred

the

<correct

was

issued

to open

FACTBAD,

cannot

read

Explanation:

specified

warranty.

was

coded

file

was

access

not

(FAC)

attempted
that
was
the FAB for the file.
specified
when
the

during

the

not
For
file

Notify

READ

WRITE,

this

bad

the

was

during

the

use

FAB

the

specified

bad

block

the

image,

requested

DCL

commands,

verify

when

the OPEN

command

data

command
data

cannot

encoded

not generally possible

the

execution of
indicates

for
for

file.

INITIALIZE

the

Return

commands

occurrea

gqualifier

factory

The

because

error.

DCL

the

that

User Action:

the

FAC

access.

volume

from

1If

type

error

field
not in

that a WRITE was issued for a file opened
READ command was issued for a file opened

the

that

the

service

that
the
block
identifier
field
the execution of the program image.

1indicates
or that a

verify

identifier
the FAB is

created.

User Action:
of

RMS

not writeable)

may
have
been
made
to
perform file
Verify
that
the
FAB
was
properly

Explanation:
A record
operation
was
indicated
1in the file access field of
example, the DEL option must have been
was

process
an ABORT

volume

the

system manager.

initialize

the

recover

factory,

the

factory

disk
bad.

from

this

under

MESSAGES

FATERRLIB,

fatal error

in library

Explanation:
An internal consistency check
has
failed
in
the
VAX-11 Common Run-Time Procedure Library.
This usually indicates
a programming error
in
the
VAX-11
Common
Run-Time
Procedure
Library.

User Action:
an

Collect as much

information as possible and

submit

SPR.

FATINTERR,

fatal internal errer

in run-time library

Explanation:
An explicit or implicit call to the
VAX-1l1l
Common
Run—-Time
Library
resulted
in
the
failure
of
an
internal
consistency check.

User Action:
possible

and

Rerun your program.

read error

file processor

FCPREADERR,

Collect as much information as

submit an SPR.

Explanation:
This message
is
associated
with
a
status
code
returned
from
a
file
control primitive (FCP) request.
An I/O
error
occurred
when
file
structure
data,
for
example,
a
directory,

was

read.

User Action:
The operating system does not normally display this
message;
the
wuser program should be able to detect and respond
to

this

FCPREPSTN,

condition.

file processor

reposition error

Explanation:
This message
is
associated
with
a
status
code
returned
from
a
file
control primitive (FCP) request.
An I/O
error occurred while attempting to reposition a tape volume after
it

has

gone

offline.

User Action:
The operating system does not normally display this
message;
the
wuser program should be able to detect and respond
to this condition.

FCPREWNDERR,

file processor

rewind error

associated
1is
This message
Explanation:
returned
from
a
file
control primitive
error occurred when a volume was being

User Action:

code
status
a
with
(FCP) request.
An I/O

rewound.

The operating system does not normally display this

message.
If
the message was issued by a user program, note the
condition and modify the source program, if necessary, to
detect
and respond to the condition.

MESSAGES

FCPSPACERR,

file

processor

Explanation:
returned

space

This message

from

error

occurred

files.

The

file

while

1is

associated

with

control

primitive

(FCP)

spaces

operating

error

were

system

being

skipped

does

not

status

request.

within

normally

code
An

I/0

file

display

this

program,

message.

User Action:

Note

necessary,

detect

FCPWRITERR,

file

the

processor

Explanation:
This
returned
from
a
error

occurred

directory
User

FEX,

was

Action:

necessary,

file

already

write

while

The

Note

Modify

respond

the

source

condition.

error

message
1is
associated
file
control primitive

being

message.

condition.

and

file

with

status

(FCP) request.
An
data,
for
example,

structure

code
I/O
a

written.

operating
the

system does

condition.

not

Modify

detect

and

respond

exists,

not

superseded

Explanation:
An attempt was made
file specification as an existing

the

normally display
the

source

this

program,

to create a
file in the

file with the
volume set.

same

User Action:
Choose a different file specification;
delete
existing
file
(if
a new one is to be created);
or use the
option in the FOP
parameter
in
the
RAB
to
regquest
that
existing

FILACCERR,

file

magnetic

Explanation:
returned

tape

file

access

This message
the

owner

FILALRACC,

Mount

(the
the

file

1is

associated

magnetic

the

VOLPRO

tape).

already

tape

with

privilege

Otherwise,

accessed

Explanation:
This message is
logical link already exists

with

ACP.

FILELOCKED,

file

Check

Explanation:
from

attempted

User Action:

deaccess
This

returned

for

file

access

The

message.

Note

necessary,

detect

code

the

file

cannot

/OVERRIDE=ACCESSIBILITY

required

another

you

must

the

volume.

channel
a

DECnet

with

operation.

1is

system

locked

error.

associated
ACP

QIO

request.

status
The

code

program

file.

system does

condition.
and

and

status

accessibility

locked

operating
the

use

a programming

message

the
is

The

associated with
is pending.

User Action:

nonblank

characteristic in the HDR/ label is not blank
be accessed without overriding the field.

qualifier

the
SUP

superseded.

from

User Action:

condition.

respond

not

Modify
to

the

normally display
the

source

condition.

this

program,

MESSAGES

FILENUMCHK,

file

identification number

check

Explanation:
This message
is
associated
with
a
status
returned
from
a
file system ACP QIO request.
The volume
file

contains bad data.

The file number in the file header that was read is not
should be.
The disk's file structure is damaged.
User Action:
FILESEQCHK,

file

The file

is beyond repair.

code
index

what

Submit an SPR.

identification sequence number check

Explanation:
This message
is
associated
with
a
status
code
returned
from
a file system ACP QIO request.
The file sequence
number in the file header is not the one expected.
A
directory
entry points to a file that is obsolete and has been deleted.
User Action:

line;

command

SMCR PIP

FILESTRUCT,

Remove

the

directory

entry

with

the

following

filespec/RM

unsupported

file

structure

level

Explanation:
This message
1is
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
1is
new
and
does
not
contain
data,
use the
INITIALIZE

command

initialize

in the correct

format.

FILNAMSPE, file name specification error
unit nnn file file-spec
user PC location

Explanation:
The file name string used in an OPEN statement
(in
VAX-11 FORTRAN IV-PLUS) is syntactically .invalid, or has a length
of zero.
A length of zero occurs if no single
gquotes
delimited
the

file

name

string

the OPEN

statement.

User Action:
Check the file name string displayed in the message
for
1illegal
characters
and
correct the source program.
If no
file name is displayed, locate the OPEN statement that caused the
error
and
check
the file name string.
If the file name string
was referred to by a variable
name,
check
that
the
CHARACTER
variable was correctly initialized.

FILNOTACC,

file

not

accessed

channel

Explanation:
The process is trying to read or write to a channel
that does not have a file accessed on 1it.
User Action:

Modify the source program to correct

the problem.

MESSAGES

FILNOTCNTG,

file

not

Explanation:
returned

contiguous

This message

from

system

contiguous

disk

FILNOTDEL,

error

deleting

Explanation:

accompanied

for

failure.

the

associated

file

not

Explanation:
A
not reached its

request.

not

with
A

system

status
file

command

make

could
by

not

a VAX-11

RMS

expired

[on

deleted.
message

action

volume

based

device

file cannot be written or
expiration date.

This

the

FILNOTFOU,
unit nnn
user

volume

file
file

must

new

message

indicating

have

volume

the

reason

associated

name]

deleted

because

User Action:
To overwrite or delete the file, mount
with
the
/OVERRIDE=EXPIRATION qualifier.
You must
of

code

that

contiguous.

COPY/CONTIGUOUS
the file.

User Action:
Take appropriate
VAX-11 RMS message.

FILNOTEXP,

required

file-spec

file

usually

1is

service

format

User Action:
Use the
contiguous version of

the
be

protection privilege.

has

volume

the

owner

not found
file-~gpec

location

Explanation:
located.

User Action:
message

The

file

Use

the

specified

full

determine

file

whether

open

specification
the

resulting

request

cannot

displayed

specification

the
is

you intended it.
Verify your current default disk and directory,
the
disk and directory containing the required file, and current
logical name assignments.

FILOPN,

file

already

open

Explanation:
directive for

An MCR
a file

User

Correct

FILPURGED,

Action:

file-spec

Explanation:
of a file it
User

Action:

indirect
command
file
that is already open.
the

command

contains

.OPEN

file.

deleted

The PURGE command
is deleting.
None.

This

displays

message

the

file

informational.

specification

MESSAGES

FLK,

file

locked

by another

user

Explanation:
An attempt was made to open or create a
file
that
has
been
1locked 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

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

argument

User Action:
the
message

too

small

too

large.

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

library.

FLOUNDMAT, floating underflow in math library
user PC location

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 LIBSFLT UNDER procedure
in
the
VAX-1l1
Common
Run-Time
Procedure Library Reference Manual.

User Action:
Locate the statement
in
called
the
mathematics
library
and

your
the

program
where
you
underflow
condition

occurred.

FLTDIV,

arithmetic

trap,

floating/decimal

divide

Zero

PC=XXXXXXXX,PSL=XXXXXXXX

Explanation:
An arithmetic exception
condition
occurred
as
a
result of an attempt to divide a floating point/decimal number by
zZero.

User Action: Examine the PC location displayed

1in

the

message

and check the program listing
to verify that operands or variables
are

FLTOVF,

specified

correctly.

arithmetic

trap,

floating

overflow

PC=XXXXXXXX,

PSL=XXXXXXXX

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

condition

occurred

User Action:
Examine the PC location displayed
1in
and
check
the
program
listing
to
verify
that
variables

are

specified

correctly.

the
message
operands
or

MESSAGES

FLTUND,

arithmetic

trap,

floating

underflow

PC=XXXXXXXX,

PSL=XXXXXXXX

Explanation:
An arithmetic exception
result of floating point underflow.
User Action:
and

check

variables

FNA,

invalid

Examine
the

are

file

the

program

specified

name

condition

occurred

location displayed

1listing

verify

the

that

message

operands

address field in
cannot be read by

the
the

correctly.

string

Explanation:
The file specification string
FAB
1is
incorrect,
or
1is
in memory that

caller.

User Action:
coded

specified

FND,

Verify

correctly.

F11ACP

points

FIND

This

from

error

that

file

not

call

The

action

correct

the VAX-11

check

that

RMS

the

service

symbolic

was

address

string.

failed

message
file

1is

system

status

value

QIO

directory

based

associated
ACP

during

Explanation:

The

User Action:

Check

with

request

made

status

code

by VAX-11

RMS.

search.

(STV)

field

information

about

this

code.

specified
the

directory,

correctly.

equivalence
correct,

status

device

file

Explanation:
incorrectly
than

nine

than

one

logical

that

and

does

name

the

that

not

the
the

FAB

contains

condition.

Take

exist.

specification

name,

the

and

was

file

specified,

logical

name.

correct

the

and
type

file

not

all

verify

volume

was

verify
were

the

that

the

specified

the

current

equivalence

mounted

inadvertently

is
the

deleted.

name
The file name portion of a
specified.
For example, the

characters.

file

assigned

verify

specified

error

the

found

device,

FNM,

the

provides

corrective

FNF,

occurred

User Action:
code

function

Explanation:
returned

that

Specifically,

name

Or,

the

use

file

file
file

logical

specification
is
name contains more

name

resulted

specification.

User Action:
Verify the syntax of the
file
name
in
the
file
specification
or
in
the
1logical
name,
if a logical name was
specified.

FOP,

invalid

file

options

Explanation:
The file
conflicting options.
User Action:
Verify
coded correctly.

options

that

the

parameter

call

the

the VAX-1l

RMS

FAB

contains

service

was

MESSAGES

FORMAT,

invalid media

format

code
status
a
with
associated
1is
This message
Explanation:
An I/0 operation failed because the
I/O functions.
by
returned
data medium is not in a format that the device driver expected.

cartridge

Verify the physical data pack, reel,

User Action:

to ensure that the correct data medium is mounted.

FORVARMIS, format/variable~type mismatch
unit nnn file file-spec
user PC location

Explanation:
An attempt was made in a FORTRAN I/O
statement
to
input
or output a real variable with an integer field descriptor
(I, L, O, or Z), or an integer or logical variable
with
a
real
field descriptor

(D,

or G).

the
locate
Use the traceback information or PC to
User Action:
statement that caused the error and
output
or
input
formatted
correct it.
Either change the variable declaration or modify the
FORMAT statement to correct the specification.

FSZ,

fixed control header size field invalid

Explanation:

The fixed control area size of the FAB for the file

User Action:

Verify that the call to the VAX-1ll RMS service

does not contain

coded

FUL,

(= 1 for print file)

the correct value.

correctly.

was

device/file lacks sufficient space for requested allocation

Explanation:

because there

An operation to create

extend

file

failed

is not enough space on the volume.

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

GPTFULL,

new volume.

global page

Explanation:

table

full

Not enough space

is available

in system

memory

maintain
information
about
global
sections.
This
message
indicates a system error resulting
from
insufficient
allocated
global

page

table

User Action:

space.

Notify

installation

your

operator

system

manager.

GSDFULL,

global

section descriptor

Explanation:
because
the
full.

table

full

The system cannot create or map
a
global
section
system
space
allocated for global section data is

This message

usually

indicates

that

the

system

was

not

generated with sufficient space for global section descriptors.

User

Action:

persists,

Wait

notify

the

and

retry

the

system manager.

2-46

request.

the

failure

MESSAGES

HEADERFULL,

file

header

Explanation:

This

returned

area

occurs

from

the

User

HIGHVER,

the

Action:

higher

same

file;

file

the

QIO

header

being

volume

explicit

version

number

type

already

with

code

header

This

map

error

inhibited,

for

with DSC.

exists

file

status

file

extended.

extension

already

and

The

extended.

!AS

directory

with

request.

cannot

file

the

name

associated

and

file

Compress

Explanation:
output

full

user

version

system ACP

when

full

message

file

volume

only

example,

was

requested

contains

higher

version

entry

for

the

number.

User
the

Action:
None.
The message is informational.
Note that
if
file is subsequently specified in a command, the system will
locate the previously existing version if no
version
number
is
specified.

HOMBLKBAD,

The

primary

Explanation:
unreadable;

invalid

accessed

User

block

The

primary

argument

The
or

contains

index

Explanation:

file

specified

home

block

was

used

index

that

the

used.

used

disk
to

mount

corrupted
the

volume.

call
to
SYS$SRMSRUNDWN,
routines either cannot be

call

the

VAX-11

1is

associated

the

volume

header

QIO

Submit

RMS

service

was

status

code

the

was

with

request.
No
maximum size

initialized

has

been

files can
the
index

reached.

is a private volume, delete
unwanted
the volume is a system volume, notify

system manager.

bad;

backup

used

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

full

message

when

file

not

data.

file system ACP
volume, because

system operator

IDXHDRBAD,

will

SPR.

User Action:
If the volume
files
on
the
volume.
If
the

backup

volume

invalid

This

returned
from
a
be written on the

bad;

file

argument
1list
on
a
SYS$SSETDRPROT control

Verify
correctly.

IDXFILEFULL,

output

list

Action:

coded

back-up

Submit

Explanation:
SYSSSETDDIR,

created

home

the

User Action:

IAL,

newly

SPR.

MOUNT
command.
unreadable;
the

MESSAGES

volume locked

IDXMAPERR, I/0 error on index file bitmap;

I/0 error encountered during a mount operation.
Explanation:
in the volume can be accessed but other
files
Existing
operations, for example, create and delete, are not possible.
If possible,

User Action:

Submit an SPR.

them.

IFA,

illegal file attributes

The

Explanation:

remove

files

the

and

reinitialize

(corrupt file header)

contents

file

the

header

been

have

the data is inconsistent and cannot be read.

corrupted;

(STV)
User Action: Depending on the operation, the status value
the FAB or RAB contains a status code that provides
in
field
Take corrective
additional information about the condition.
1If the error persists, collect
action based on this status code.
as much information as possible and submit an SPR.

IFI,

invalid internal file identifier

(IFI)

value

is
Explanation: The internal file identifier field of the FAB
This error usually indicates that the file has not been
invalid.

or
opened for an operation that requires the file to be opened,
1is already opened for an operation that requires
file
that the
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.

ILLANSIBS, ANSI magnetic tape block size must be at least 18
characters

Explanation:
18

User Action:
for

The label specified for a tape contains

than

1less

characters.

the block

ILLBLKNUM,

Reenter the command;
size.

specify a minimum value of 18

illegal logical block number

Explanation: The logical block number specified does not exist
If this error results from a Files-1l1 1I/0
on the disk.
operation,

the file structure is damaged.

User Action:
ILLCNTRFUNC,

Check for a programming error.

Submit an SPR.

illegal ACP control function

is associated with a
This message
Explanation:
request.
system ACP QIO
from a file
returned
function specified in an IO$_ACPCONTROL

valid

QIO

request

status code
The control
is

not

function.

See the VAX/VMS I/0
User Action: Check for a programming error.
the correct function codes and coding
for
Guide
User's
a DECnet
associated with
is
the error
If
specifications.
operation, see the DECnet-VAX System Manager's Guide.
2-48

MESSAGES

ILLDEVNAM,

illegal

device

Explanation:
request

has

User

Action:

call

the

device

than

illegal

device

Explanation:

job

The

gqueue

example,
code
not

card

normally

returned
specified

event

Action:

flag

number

the

occurs

when

/OWNER_UIC
creation
create

User

User
call

request

jobs

can

associated
The

start

queued,

with

operating

for

error.

correctly.

coding

status

system

does

that

the

Verify

See

the

for

VAX/VMS

System

specifications.

cluster

1is

associated

with

request.

status

greater

event flag
than 127.

code
number

has

was

for

the

file

The

with

qualifier

CREATE

command

you

specify

that

For

applies

this

can
invoke
This error
is

legal

example,

the

only

the

when

you

qualifier

issued.

command
Guide,

entered.

HELP

User's

are

by
a
DCL
command
qualifiers specified.
are

message

the

program

entered

qualifiers

this

Use

image.

another

directory;

that

illegal

command

the

image invoked
based on the

Language

associated

Manual

qualifier
of

request

a programming

message

other

Explanation:

The

manager

the source program.
Verify that the
event
correctly
coded,
and that it was not modified

file,

qualifiers

ILLFILNAM,

symbiont

Correct

Action:

Command

message.

coded

supported

when

message

which

controller.

a
system
service
system service call

Explanation:
The
different
images
only

This

was

execution

option

specified

job

for

flag

This

from

User

ILLEGOPT,

gueue

type

this

service

Explanation:

during

the

for

device

reader.
by

Reference

illegal

Check

the

Services

device

display

User Action:

ILLEFC,

specified

characters.

type

not

returned

call

name
15

Check for a programming
error.
Verify
that
the
service was coded correctly.
See the VAX/VMS System
Reference Manual for coding specifications’

to
Services

ILLDEVTYP,

name

and

refer

necessary,

reenter

the

specified

to
to

the

VAX/VMS

determine

the

command.

name

file

name
than

nine

with a status code
operating system does not

characters.

returned
normally

symbiont
This

manager

message

by
the
job
controller.
display this message.

Action:
Check for a programming
error.
Verify
that
the
to the service was coded correctly.
See the VAX/VMS System
Services Reference Manual for coding specifications?

MESSAGES

ILLINST, compatibility mode illegal instruction

Explanation: An RSX-11M image attempted to execute either a JMP
or JSR instruction with a register destination. The PC contains

In
error.
the
caused
that
instruction
the
of
the address
erroneous
the
following
address
the
contains
PC
the
RSX-11M,

instruction.

This message corresponds to the RSX-11M termination

User Action:

Determine the instruction or statement at which the

message ILLEGAL

INSTRUCTION.

error occurred and correct the error.

ILLIOFUNC,

illegal I/0 function code

is associated with a status code
Explanation: This message
A function code in an
returned from a system service request.
the errors
if
Or,
explicit input/output request was invalid.
the user attempted a
during a DECnet operation,
occurred
synchronous disconnect with outstanding transmits.

User Action:

Locate the

Check for a programming error.

function code and correct it.

ILLOPT, qualifier(s)

invalid

not appropriate to this device

Explanation: A MOUNT or INITIALIZE command specified qualifiers
that apply only to disk devices for a tape device, or gqualifiers
that apply only to tape devices for a disk device.

User Action: Use the HELP command or refer to the VAX/VMS
Command Language User's Guide for a 1list of qualifiers, if
necessary, and reenter the command without the inappropriate
qualifier (s).

ILLPAGCNT,

illegal page count parameter

associated

Explanation:

This message

User Action:

Check for a programming error;

with

status

code

the

number

symbiont

manager

The number of pages
request.
service
system
from a
returned
specified for an expand or delete region request was less than 1.

verify

of pages specified for the service call.

ILLQUENAM,

illegal gueue name

Explanation:

The queue name

specified

request has more than 15 characters. This message is associated
with a status code returned by the job controller. The operating
system does not normally display this message.

the
Verify that
Check for a programming error.
User Action:
See the VAX/VMS System
to the service was coded correctly.
call
Services Reference Manual for coding specifications.

MESSAGES

ILLRQST,

illegal

operator

Explanation:
a

REQUEST

A REPLY

command

User

Action:

ILLSEQOP,

illegal

request

command

specified

Verify

the

sequential

was

issued with

bad

value.

command

line

and

no qualifiers.

reenter

the

Or,

command.

operation

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

User

section.

Action:

Examine

the

source

program

problem.

ILLSER,

illegal

service

Explanation:
returned

call

message

system

1is

User Action:
Check for
call and correct it.

illegal

value

Action:

Command
and

IMCHNG,

reenter

two

Use

Language
the

images

operating

requesting

the

image

entered
valid

the
service.

error.

invalid

parameter

command

value

Guide,

command

address
User
coded

for

one

that can
functions

different

images

potentially
was

Action:

XAB

Verify

correctly.

a
service

the

illegal

within

the

legal

the

VAX/VMS
values

request

different

with

gqualifiers

specified

executed.

to
the
VAX/VMS
qualifiers and/or

location

More than one XAB of the same type
The status value (STV) field of the

the

code

specified

not

refer

necessary,

command

duplicate

Explanation:
operation.

status

system

Locate

User Action:
Use the
HELP
command
or
refer
Command
Language
User's
Guide
to verify the
functions requested and reenter the command.

IMX,

logic

command.

system

that

with

request.

programming

HELP

User's

requested

Explanation:

the

present

Explanation:
A qualifier
legal range of values.
User

associated

service

call to a procedure whose name
vector table, but which is not

ILLVAL,

determine

number

This

from

exists

for

the

FAB

provides

the

RMS

service

was

error.
that

the

call

the

VAX-11

MESSAGES

INCOMPAT,

input-file

(input)

and

incompatible attributes

Explanation:
This
incompatibility
may

output-file

(output)

have

warning
message
indicates
that
file
exist between files that have been appended

or concatenated.
This message can
occur
if
files
<created
Dby
different
methods
are
concatenated,
for example,files created

with the DCL command WRITE and
command.

files

created

The command continues execution.

the

SORT/RSX

a
presents
incompatibility
Determine whether the
User Action:
and, if so, delete the output file(s), modify the format
problem
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

Explanation:
A MOUNT command was issued
to
mount
a
shareable
volume
that
1is
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 gualifiers.
INCOMPACP,

indicated ACP

Explanation:

incompatible with volume

The ACP specified is not an ACP for

the

Reenter

ACP

requested

device.

User Action:

appropriate for

the

command;

the particular device

INCOPECLO, inconsistent OPEN/CLOSE
unit nnn file file-spec
user PC location

specify

type.

that

parameters

Explanation:
The specifications in a CLOSE statement (in
VAX-11l
FORTRAN
IV-PLUS) contradict specifications in the OPEN statement
for the file.
Specifically, one of the following inconsistencies
occurred:
1)
NEW or SCRATCH was specified for a READONLY file;
2) APPEND was specified for a NEW, SCRATCH, or READONLY file;
3)
SAVE
or PRINT was specified for a SCRATCH file;
or 4) DELETE or
PRINT was specified for a READONLY file.
User Action:

Correct either

the OPEN

statement

for

the

file.

INCRECLEN, inconsistent record
unit nnn file file-spec
user PC location

length

Explanation:
An existing VAX-11 FORTRAN
1IV-PLUS
direct
access
file
was opened whose record length attribute is not the same as
specified in the DEFINEFILE or OPEN statement.
It
1is
possible
that the file was not created as a direct access file.
User Action:
Locate the statement in your
program
that
caused
the
error and check the RECORDSIZE specification.
Remember that
formatted records are specified in units of bytes and unformatted
records are specified in units of longwords.
2-52

MESSAGES

INCVOLLABEL,

incorrect

Explanation:
volume.

The

volume

label

specified

the

label

the

Verify
correct

that

are

INDEX,

you

have

the

volume

protection

invalid

index

file for a
disk.
The

file

that

you

either
the

The

position

block

specified

for

the

position of

the

disk volume is larger than the number of blocks
INITIALIZE command cannot write the index file.

User Action:
Reenter the
index file that is within

INFFORLOO,

privilege

owner.,

Explanation:

infinite

format

command;
the range

specify a
of blocks

index
on

the

position
for
on the volume.

the

loop

nnn file file-spec
PC location
Explanation:
The format associated
I/0
statement that includes an I/0
to

use

transferring

User Action:
the

error

transmits

INPASGN,

error

statement

the

FORMAT

element

assigning

Explanation:
channel
to
indicates an

User Action:
an

the
must

The
the

input

with
list

a VAX-11 FORTRAN IV-PLUS
has no field descriptors

variables.

check

There

these

Locate

and

statement.

from

in your

statement
format

the

I/O

program

that

associated

with

field

descriptor

caused
the

I/0
that

list.

channel

input card reader symbiont could not
assign
a
card reader to read a user's job.
This message

internal

operating

Collect

as much

system error.

information

possible

and

submit

SPR.

INPCONERR,
unit
user

not match

User Action:
Verify that the correct volume is mounted.
the
1label
entered.
Repeat the request, specifying the
volume label or specifying
OVERRIDE:ID,
which
requires
volume

unit
user

does

input

conversion error

nnn file file-spec
PC location

Explanation:
During a VAX-11 FORTRAN IV-PLUS input operation
an
illegal
character
was
detected
1in an input field or the input
value overflowed the range specified for the input variable.
The
value of the variable is set to zero.
User Action:
that

caused

correct

and

Locate
the

the

error.

verify

the

READ
Check

width

that

the

each

statement
FORMAT

field

in your

statement

specified.

program

number

MESSAGES

INPREAD,

error

reading

Explanation:
cannot

input

Input records

in a card

reader

batch

job

stream

read.

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

INPRECTOO, input record too
unit nnn file file-~spec
user PC location

long

Explanation:
VAX-1ll RMS has
read
a
record
that
exceeds
the
explicit
or
default
RECORDSIZE specified in the OPEN statement
(in VAX-11 FORTRAN IV-PLUS).
The
VAX-11l
RMS
portion
of
the
message indicates the size of the record that caused the error.
User Action:
Locate the READ or ACCEPT statement in your program
that
caused
the
error and check the associated OPEN statement.
Correct the RECORDSIZE specification in the
OPEN
statement,
1if
necessary.
Remember
that
the
RECORDSIZE
specification is in
units of bytes for formatted files and in units of longwords
for
unformatted files.

INPSTAREQ, input statement
unit nnn file file-spec
user PC location

requires

too much

data

Explanation:
A VAX-11l FORTRAN IV-PLUS unformatted READ statement
attempted
to
input
more
data than existed in the record being
read;
for example, the I/0 list contained too many elements.

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
1is
properly
declared;
an
omitted
declaration
results
in four bytes of data input by
default.

INPSTRTRU,

input

string

truncated

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
in the descriptor.

INSFARG,

insufficient

call

program by

increasing

the

field

arguments

Explanation:
A system service argument list contained
the required number of arguments for the service.

User Action:

Check

System Services

length

for

a programming

Reference

Manual

for

error.

coding

See

fewer

the

than

VAX/VMS

specifications.

MESSAGES

INSFDYNMEM,

insufficient

Explanation:
emulate

virtual

VAX/VMS

requested

address

requires

RSX-11M

space

service

virtual
than

User Action:
Check for a programming
likely in a loop.
Correct the source

INSFMEM,

insufficient

dynamic

image
and

system manager

User Action:
can

Check

returned

did

for

from

error.
The
program.

not

allocate

programming

system

insufficient

enough

space

allowed.

image

dynamic

error;

service

disabled resource
wait
mode.
Notify
insufficient memory is allocated.

INSFPRM,

very

exhausted
the
system
pool
the
system
cannot complete

request.

the

address

process

memory

Explanation:
A command or
available
dynamic
memory

Or,

this

memory.

status

request

when

the

system

of
the

the

code

image

has

manager

parameters

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

User

are

Action:

INSFRAME,

Correct

insufficient

Explanation:
returned

from

specified

the

call

command

frames

This

message

system

depth

stack.

User Action:

INSFWSL,

entered.

that

Check

insufficient

unwind

for

unwind

associated

service

greater

with

request.

than

the

number

status
unwind

call

code

reguest

frames

occurs.

working

procedure.

programming

set

error.

limit

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
in
order

for

section

cannot

exceeds

the

image

execute.

mapped if the
working set limit.

For

example,

number

global

pages

private

mapped

User Action:
Check for a programming
error;
verify
that
number
of
pages
requested
in
a
system
service
request
accurate.

the

size

command

and

the

retry

number

working
the

pages

set

program.

accurate,

1limit

with

try

the

SET

the
is

increase

WORKING SET

MESSAGES

INSVIRMEM, insufficient virtual memory for buffer
unit nnn file file-spec
user

space

location

Explanation:
The FORTRAN I/O library exceeded the
virtual
page
limit for the image while dynamically allocating space for an I/0
statement.

using
by
1limit
Determine the current working set
User Action:
Then, increase the size of the
command.
SHOW WORKING_SET
the
working

INTDATCOR,

set limit and

rerun your

program.

internal data corrupted in run-time library

Explanation:
On a call to the
Run-Time
Library,
a
data
base
consistency
check
failed.
A
user
program
can cause this by
referring to a location outside of a
dimensioned
array,
or
by
requesting input from an address outside of the program.

be
may
think
you
that
module
any
Recompile
User Action:
of a dimensioned array with the /CHECK=BOUNDS
outside
referring
qualifier.

INTDIV,

Relink

and

trap,

arithmetic

rerun your

integer

program.

divide

2zero

PC=XXXXXXXX,

PSL=XXXXXXXX

Explanation:

An arithmetic exception

result of an attempt to divide by zero.

condition

occurred

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

INTFAIL,

internal

the
message
operands
or

consistency check

Explanation:

A command failed because of

internal

software

error.,

User Action:
an

Collect as much information as possible and

submit

SPR.

INTLOGERR,

internal

logic

error

Explanation:
A general library procedure
detected
an
internal
logic
error.
This
message
1is
associated
with a status code
returned from the Run-Time Library.

User Action:
an

INTOVF,

Collect as much information as possible and

submit

SPR.

arithmetic

Explanation:
integer

trap,

integer

overflow at PC=XXXXXXXX,

PSLTXXXXXXXX

An exception condition occurred as a result

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

MESSAGES

INVALKEYW,

keyword

Explanation:
valid;
or
required.

A
a

User Action:

Use

Language

keywords

and

invalid

recognized

keyword
numeric

Command

INVARG,

the

specified as a
qualifier
value
1is
value
was specified where a keyword

HELP

User's

reenter

the

command
Guide,

refer

necessary,

the
for

VAX/VMS
the

legal

status

code

command.

This message

associated

with

returned from the Run-Time Library.
A
or more invalid arguments to a general

calling program passed
library procedure.

User Action:

the

Library

INVARGFOR,

not
was

argument(s)

Explanation:

user

not

and

Verify
correct

invalid

the
the

argument

arguments

for

call

the

one

Run-Time

program.

FORTRAN

run-time

library

location

Explanation:
codes

call

coded
to

argument

the

VAX-11l

not one

FORTRAN

the

IV-PLUS

defined

specific

set

procedures

of the Run-Time Library.
This error cannot occur
in
a
FORTRAN
I/0
statement
unless
the version of the compiler is newer than
the version of the Run-Time Library.
This error can occur
1in
a
call
or

the

PDP-11

FORTRAN

compatibility

routines

ERRSET,

ERRTST,

CLOSE.

User Action:

Locate the call to the library in your program.
1If
the procedure is a compatibility procedure, see the VAX-11] Common
Run-Time Procedure Library Reference Manual.
Otherwise,
verify
the
version
of the compiler with the version of the library and
recompile or relink your program, as hecessary.

INVARGMAT, invalid
user PC location

argument

math

library

Explanation:
One of
an invalid argument.

the

mathematics

procedures was

called

User Action:

Locate

the

mathematics

procedure

call

that

the

correct

table

error

INVDSTREC,

and

unimplemented

the

with

caused

argument.

delta-PC

command

symbol

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

much

information

possible

and

submit

MESSAGES

INVKEY,

invalid

keyword

Explanation:
value

An unknown keyword was

User Action:
Use
Command
Language
keywords

specified

for

and

the
HELP
command
User's
Guide,
if

reenter

INVLOGUNI, invalid logical
unit nnn file file-spec
user PC location

the

or
refer
to
the
VAX/VMS
necessary,
for
the legal

command.

unit

number

Explanation:
greater than

A
VAX-1l1l]
99 or less

User Action:
logical unit

Locate the I/0 statement that specified
number and correct your program.

INVMSG,

qualifier

parameter.

invalid message

code

FORTRAN
IV-PLUS
logical
than 0 was specified in an

unit
number
I/0 statement.

the

invalid

received

Explanation:
The message code
specified
in
a
job
controller
message
1is 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.

INVQUALNUM,

invalid qualifier

number

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

INVREQTYP,

invalid

Explanation:
code
returned
it indicates a

User Action:
an

INVRSP,

Collect

as much

request

type

information as possible

and

submit

internal

status

SPR.

This message

associated with

from the command interpreter result
request to perform an unimplemented

Collect

much

information

parse routine;
function.

possible

and

submit

SPR.

invalid

response

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

displayed

part of

the

or
the
the

request,

MESSAGES

INVSCT,

invalid

SCT

state

Explanation:
The job
<controller's
faulty.
This
message
indicates

symbiont
an

controller.

User
an

Action:

Collect

much

control

internal

information

possible

invalid

string

Explanation:

procedure

not

did

User Action:

the

and

is
job

submit

descriptor

string

descriptor

contain

passed

valid

Locate

the

call

initialize

the

field

DSC$B_CLASS

the

1library

that

and

See

the

for

VAX-11 Common Run-Time Procedure Library
description of the classes of descriptors.

INVITYPE,

invalid

LIBSTPARSE

state

the

table

proper

Action:

Correct

the

VAX-11

program.

See

Reference

Manual

invalid

The
portions

separated

User

Action:

I/0

the

Common

correct

class

caused

the

descriptor.

Reference

Manual

the

LIBSTPARSE

state

Run-Time

procedure

table

Procedure

vyour

Library

format.

UIC

Explanation:
member

for

format

library

entry

Explanation:
The state table passed to
was invalid and could not be processed.

User

general

field.

error

IOERROR,

SPR.

INVSTRDES,

INVUIC,

table

error

command contains
a
UIC
must

an invalid UIC.
The group and
both be specified and must be

comma.

Correct

the

UIC

initializing

and

volume

reenter

the

on device-name

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

User Action:

Attempt

another

volume.

hardware

error

Dump

occurred.

perform
the

command.

error

the
1log

initialization.

operation
to

again.

determine

Use

whether

MESSAGES

I0pP,

operation

illegal or

Explanation:
error

can

invalid for

file organization or device

An invalid VAX-11 RM operation was attempted.

This

indicate:

An attempt to perform block I/0 when block

I/O access was not

specified

An attempt to perform record
not

I/O when record

I/0

access

was

specified

An attempt to rewind a process-permanent file

An operation not valid for the device type
(for
example,
a
rewind
request
on
a line printer) or the file organization
(for example, an erase or extend request for a magnetic
tape
file)

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

I0T,

the

condition.

compatibility mode

IOT

Explanation:
An RSX-11M
termination
message
IOT
instruction.
This
message
corresponds to the RSX-11lM termination message IOT
EXECUTION.

User Action:
error

IRC,

occurred

illegal

Determine the
and

correct

instruction or
the

record encountered -

statement at which

the

error.

STV =

nnn

(10)

Explanation:
The byte count field or
the
control
byte
for
a
record
in
a file is invalid.
For sequential files, the message
displays the virtual block number of
the
block
containing
the
record.
For
relative
files,
the
message displays the record
number

the

User Action:
an

illegal

record.

Collect as much information as possible and

submit

SPR.

For sequential files, check the record's file address, if you are
using
RFA
access;
otherwise,
try to recreate the rest of the
file.
For relative files, reinsert the bad record using the
UIF
option in the ROP parameter if necessary.

IsT,

invalid

internal

stream

identifier

(ISI)

value

Explanation:
The internal stream identifier
file does not specify a valid stream.

the

RAB

for

User Action:
Determine the instruction or statement at which
error
occurred, using the debugger if necessary, and correct
error.
The ISI field may have been inadvertently altered, or
RAB was

never

connected before

the

operation was

attempted.

the
the
the

MESSAGES

IVADDR,

invalid media

address

Explanation:
This message
1is
associated
with
a
status
returned
by
I/0
functions.
A
disk
address
specified
physical disk read or write operation was not valid.

User Action:

Verify the disk

address

specified

and

update

code
1in a

the

program.

IVCHAN,

invalid

I/0

channel

Explanation:
This message
1is
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/0 operation cannot be performed.
User Action:
Check for a programming
error.
Verify
that
the
request
to
assign
the
1I/0
channel completed successfully and
returned a valid channel number.

IVCHAR,

non-numeric

character

in value

string

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

Examine
spelled

the

command

symbol

string

name,

example, %X) preceding a hexadecimal
value
following
a
radix
operator
syntax error.
Reenter the command.

IVCHNLSEC,

invalid

Explanation:
and/or map a

channel

for

The channel
section file

create

for

a missing

undefined

radix

operator

or octal value,
an
(for example, %09),

invalid

device

illegal
or for a

and map section

number specified in a request to create
is busy;
the section cannot be mapped.

User Action:
Verify that the OPEN request to
open
the
file completed successfully and returned a valid channel

IVDEVNAM,

or
(for

section
number.

name

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
1is
suitable for the requested operation.
If a logical name
is used, verify that it has been assigned
a
proper
equivalence
name.

MESSAGES

IVDEVTYPE,

invalid device

type

Explanation:
operation.

The

specified device

User Action:

Reenter

the

command;

invalid

for

the

requested

specify an appropriate device

type.

IVFNAM,

invalid

function

name

Explanation:
A command contains the character
string
'F$name
()
where
name
1is
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.

IVKEYW,

unrecognized

qualifier

keyword

Explanation:
A qualifier or
command is not valid for the

keyword

parameter

specified

1in

command.

User Action:
The rejected portion of the
command
is
displayed
between
backslashes.
Use
the
HELP
command
or
refer to the
VAX/VMS Command
Language
User's
Guide
for
a
1list
of
wvalid
qualifiers.

IVLOGNAM,

invalid

logical

name

Explanation:
A name string exceeds
or
has
a length of zero.
Logical
of 63 characters;
process
names,
common event flag cluster names are

the maximum length
required,
names are limited to a length
global
section
names,
and
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 character string descriptors pointing to name
strings indicate the correct lengths.

IVLOGTAB,

invalid

logical

name

table

number

Explanation:
This message
1is
associated
with
returned
from
a
system
service
request.
A
logical name system service
request
specified
table number that was not 0 (system), 1 (group),

User Action:
logical name

IVOPER,

Check
table

unrecognized

for

a programming
is 0, 1, or

number

error.

a
status
code
create or delete
a
1logical
name
or 2 (process).

Verify

that

the

operator

Explanation:
An arithmetic expression
contains
a
period
(.),
indicating
a
1logical,
arithmetic,
or string operator, b.t the
operator is not a recognized operator.
The rejected
portion
of
the command is displayed between backslashes.
User Action:
Correct the
list of valid operators.

command.

Type HELP EXPRESSIONS

for

MESSAGES

IVPROT,

invalid

protection

Explanation:
is not in the

The protection code
correct syntax.

User Action:
Use
Command
Language
syntax

IVPROTECT,

and

specified

invalid

protection

system

Check

file

volume

or
refer
to
the
VAX/VMS
necessary, for the correct

code

1is

associated

service

request.

greater

for

qualifier

for

command.

This message

from

User Action:

IVQLOC,

the

page

Explanation:

specified

the
HELP
command
User's
Guide,
1if

reenter

invalid

returned

code

than

with
A

page

status

code

protection

code

15.

programming

error.

location

Explanation:
A qualifier that can be
specification in a command was placed

used only
following

to qualify a file
the command name.

User Action:
Reenter the command;
place the qualifier following
the
specification
of
the
file it actually qualifies.
Use the

HELP

command

Guide

IVQUOTAL,

refer

determine

invalid quota

Explanation:

This

returned

for

from

create

VAX/VMS

and

Command

placement

Language

the

User's

qualifier.

list
message

system

process

contained

the

the meaning

1is

associated

service

system

illegal

request.

service

quota

with

The

was

not

quota
in

status
list

the

code

specified

proper

format,

names.

User
call

Action:
Check for a programming
error.
Verify
that
the
to the service was coded correctly.
See the VAX/VMS System
Services Reference Manual for coding specifications.

IVSECFLG,

invalid

process/global

Explanation:

This

returned

from

arguments

User Action:
correctly.

coding

IVSECIDCTL,

message

system
system

Verify
See

the

section

1is

associated

service
service

that

request.
were

the

VAX/VMS

flags

not

call
System

with

Flags

Explanation:

section

the

service

Services

This

identification

message

1is

status
as

code
input

valid.

match

associated

was

Reference

specifications.

invalid

specified

coded

Manual

for

control

with

status

code

The

match

control

field

identify

User Action:
Verify that the
call
to
the
correctly.
See the VAX/VMS System Services
coding specifications.

service
Reference

returned

from

system

service

request.

in the section
identification
argument
section contains an invalid number.

global

was
coded
Manual for

MESSAGES

IVSSRQ,

invalid

system service

request

Explanation:

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

User Action:

Check

IVSTSFLG,

for

invalid status

a programming error.

flag

Explanation:
This message
1is
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 ($SCREPRC)
system
service.

User Action:
correctly.
coding

IVSYMB,

Verify that the
call
to
the
service
was
coded
See the VAX/VMS System Services Reference Manual for

specifications,

symbol must start with alphabetic

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

User Action:

invalid

symbol

Choose a name for the symbol that begins

of the letters A through Z

IVTIME,

and reenter

name

with

one

the command.

time

Explanation:
This message
1is
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

User Action:
call

IVVALU,

the

invalid

and

time.

Check for a programming

service was

syntax

error.

Verify

coded correctly.

for value

that

the

specification

Explanation:
A value for a command qualifier
is
not
specified
correctly;
or,
a
command
is
not
being
wused
in its proper
context.
The
rejected
portion
of
the
command
is
displayed
between

backslashes.

User Action:
Command
usage

IVVERB,

Use the

Language

HELP

command

User's Guide

the command.

refer

to determine

the

the proper

VAX/VMS

syntax or

unrecognized command

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

and

Check

reenter

the

the spelling of the command
command.

2-64

name

symbol

MESSAGES

JOBABORT,

job

aborted

Explanation:
processed
User

batch

during

Action:

The

command

that

JOBCRD,

job

card

was

message

SYNCHRONIZE

command

job

deleted

either

1is

has

informational;

requested

this

job,

syntax

KBF,

Action:

invalid

key

error

Correct

KEY,

Verify

correctly.

correctly

invalid

key

however,

the

this

error

causes

the

job

card

and

job

card
job

the

resubmit

the

submitted
that

card

job.

buffer

User Action:
is

was

'string'

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

coded

fail.

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

before

processing.

that

the

call

Specifically,

check

the VAX-11
that

the

area

RMS

service

key

buffer

memory

was

address

specified.

field(key=0/negqg)

Explanation:
An
operation
on
a

invalid record key was specified
for
a
random
relative
file.
The key was either negative or

zZero.

User Action:
Verify
coded correctly.

KEYVALERR,

keyword

value

that

the

error

call

OPEN

unit nnn file file-spec
user PC location
Explanation:
IV-PLUS)

that

accepted

change

the

VAX-11

KEYVALOVR,

many

Explanation:
too

Locate
value

FORTRAN

too

FORTRAN

IV-PLUS

value

Use

the

RMS

service

was

(in

exceeds

VAX-11

the

FORTRAN

prescribed

limits

procedures.

one

statement

within

User's

characters

The

keyword

value

the OPEN
to

the VAX-11l

statement

requires

the

User Action:

OPEN

the

Guide

for

qualifier

specified

that

for

caused

acceptable
the

valid

keyword

the

error

and

See

the

limits.
limits.

value

qualifier

long.

User Action:
Command

Language

keywords

and

HELP

User's

reenter

the

command
Guide,

command.

refer

necessary,

the
for

VAX/VMS
the

valid

MESSAGES

KSZ,

key

size

too

large(idx)/not=4(rel)

Explanation:
specify a

User Action:

LBR

The key size

length

four

Correct

specified for

relative file does

not

bytes.

the

source program.

=--

All LBR messages are identical to the
messages
locate the message in the list alphabetized with

LCKPAGFUL,

no more pages may be

Explanation:
the
system

locked

issued
by
LIB;
the keyword LIB.

in memory

An attempt to lock pages in memory
failed
because
1limit
on the number of pages that can be locked 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

Explanation:
This message
1is
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.

LIB

BAD

LIBRARY

HEADER

Explanation:
library file,

Either
or the

the specified
file has been

Verify

library
procedure
corrupted.

that

not

the

User Action:
Reenter the command specifying the correct
library
procedure
name.
Or,
if
the
specified
file
1is
a
library
procedure, run VFYl or VFY2 to determine whether
the
volume
is
corrupted.
Also,
ensure that the library file is not specified
as
a
logical
name
that
translates
to
an
incorrect
or
inappropriate
file specification, for example, an incorrect file
type.

LIB

COMMAND

SYNTAX

Explanation:

ERROR

You made an error

the command

line,

User Action:
Reenter the command line.
If
necessary,
consult
the
command
description
in the VAX/VMS Command Language User's
Guide for a detailed explanation of the command syntax.

2-66

MESSAGES

LIB

GLOBAL

SYMBOL

Explanation:
in the global

NAMED

symbol-name

You have attempted
symbol table.

put a

duplicate

symbol

name

User Action:

Modify the module so that its global
symbol
names
are
unique
within the current library, or place the module in a
different
1library.
You
<can
insert
the
module
specifying
/NOGLOBALS;
in this case, however, the linker cannot extract the
module by resolving symbols contained in the module.

LIB --

DUPLICATE

MODULE

Explanation:
same name as

LIB

ERROR

Either

replace

module-name

filename

You are attempting to insert a module
an existing module in the library.

User Action:
name,

NAME

the

LIBRARY

rename

the module

existing

TABLE

FILE

Explanation:
The specified
file is corrupted.

that has

recompiling

with

the

new

the

module.

filename

file

not a library

file,

User Action:
1If the file is not
a
1library
file,
reenter
the
command
with the correct library file specified.
If the file is
corrupted, reconstruct the library.

LIB

FATAL

COMPRESS

Explanation:
compressing

The LIBRARY
the

User Action:

LIB

EXCEEDED

Explanation:
global

for

the

command

encountered

fatal

error

when

library.

Reconstruct

GST OR MNT

ERROR

You
symbol

library.

are

library.

library-name

attempting

table

This

the

(GST)

number

exceed

module

the

name

allowable
table

specified when

(MNT)

the

number
entries

1library

Iis

created.

User Action:
the /COMPRESS

LIB

GST

MNT

Copy the library
qualifier.

SPACE

EXCEEDED

and

increase

values,

Reenter

delete

the

table

space

using

COMPRESS

Explanation:
The global symbol table
(MNT)
space specified on a /COMPRESS
during the compress operation.

User Action:

the

command

(GST) or module name
table
qualifier has been exceeded

specifying

unnecessary modules

from

larger

the

GST

library.

MNT

MESSAGES

LIB -- ILLEGAL DEVICE/VOLUME name

Explanation:

entered

You have

syntax

conform to VAX/VMS

rules.

device

name

that

does

not

a
dev is
Reenter a device name in the form devcu:
User Action:
device type, c¢ is the controller designator, and u
two-character
is

LIB

the unit number.

ILLEGAL

directory

Explanation:

The

line

with

the

proper

output

file

directory

name

specified

does

not

exist

this

the

correct

volume.

User Action:
directory

PIP

cannot

rename

Explanation:
renamed file

PIP

Reenter

name

the

from

command

correct

one

specifying

volume.

device

another

place

the

User Action:
Reenter the command line, renaming the file on
input
volume.
Then, enter another command to transfer the
to the intended volume.

the
file

You attempted
to
on another device.

failure

Explanation:
The
file is locked to

input

rename

file

and

file

input file could not be properly
indicate possible corruption.

closed.

User Action:
Reenter the command line.
If the error recurs,
a validity check on the file structure using VFYl or VFY2.

PIP

failure

Explanation:
The
file is locked to

output

command

syntax

Explanation:
User
the

Action:
command

Guide.

run

file

output file could
indicate possible

not be properly
corruption.

closed.

User Action:
Reenter the command line.
If the error recurs,
a validity check on the file structure using VFYl or VFY2.

PIP

The

run

error

There

error

the

command

line.

Reenter the command.
For further information about
syntax, refer to the VAX/VMS Command Language User's

MESSAGES

PIP --

device

not mounted

Explanation:
The device is not
mounted,
or
another
mounted the device to contain a private volume.
User Action:

Mount

the device,

and

reenter

wuser

has

the command.

PIP -- directory write protected

Explanation:
directory

The command
the

Dbecause

could

device

not

remove

write-protected

entry

from

because

a
a

privilege violation.

User Action:
Enable the unit for write operations,
owner of the directory change its protection.
PIP

error

have

the

from parse

Explanation:

The

User Action:

Reenter

directory

PIP --

failed

specified directory does not exist.
the

command

specifying

the

correct

name.

attach output device

Explanation:
An
attempt
to
attach
a
record-oriented
output
device
has failed.
This error usually is caused by the device's
being offline.

User Action:

line.

command

PIP --

failed

Ensure that the device

to delete

You attempted

User Action:

Request

PIP --

and

reenter

the

file

Explanation:

the

is online

the

to delete a protected

file owner

to change

file.

the protection

file.

failed

to detach

output device

Explanation:
An attempt to detach an output device
has
failed.
This error usually is caused by the device's being offline.
User Action:
command

PIP --

line.

Ensure

failed to enter

that the device

is online

and

reenter

the

new file name

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

change

Reenter

the

command

and directory name,
its protection.

name

2-100

line
specifying
the
request the directory

correct
owner to

MESSAGES

PIP

failed

find

Explanation:
found in the

files

The file(s) specified
designated directory.

User Action:
Reenter the command
specification and directory name.

PIP

failed

to mark

file

You

User Action:
protection or

Request
the
owner
unlock the file.

failed

attempted

delete

storage

The command
map.
This

User Action:
Request
on the volume.

failed

read

failed

PIP

failed

the

owner

it,

are

use

file

locked

file.

file

change

the

recover

the

its

volume's
privilege

protection

corrupted,

access

VFY2

you

the

not

file.

determine

whether

corrupted.

remove

directory

entry

Enable the unit
the directory to

restore

original

not
remove
an
write-protected,

for write
change its

directory

entry
from
a
or a privilege

operations,
protection.

entry -

file

Explanation:
The command has removed a file
from
a
failed
to
enter
it in another directory, and failed
the original directory entry.
User Action:

not

correct

the
specified
is caused by a

allowed

VFYl

Explanation:
The command
could
directory
because
the
unit was
violation was detected.

User Action:
the owner of

a protected

specified

that you

the

were

attributes

access

delete

volume

Ensure

volume

line

bitmap

you

the

PIP

User Action:
have

command

specifying

could not read
error usually

the

Explanation:
The volume
have access to the file.

the

delete

Explanation:

Explanation:
storage
bit
violation.

PIP

for

Use

the

lost

check

file.

2-101

feature

VFYl

request

lost

directory,
to replace

VFY2

MESSAGES

PIP

~-~

failed

write

Explanation:

The

access

volume,

the

attributes

volume

corrupted

you

not

have

User Action:
Determine whether you are
allowed
access
file.
If you are allowed access to the file, run VFY1l or
verify the volume in question and determine
the
extent
corruption.

PIP

file

User Action:
Run
recover the file.

file

the

VFY2

the

lost

Explanation:
The
directory,
failed
directory entry.

PIP

write

not

command
has
to
delete

the

lost

removed
it,
and

check

the
file
fai led
to

option

from
restore

VFYl

its
the

VFY2

not

locked.

locked

Explanation:

You

attempted

User Action:

Reenter

the

unlock

command

file

that

specifying

the

correct

file

name.

PIP

illegal

copy

Explanation:
the

same

You

same

attempted

directory

operation results
file;
therefore,

device

that

in
it

an
is

and

copy

being

illegal

use

wild

Explanation:
The use
attempted
operation

all

card

versions

scanned

infinite number
not allowed.

User Action:
Reenter the command
into a different directory.

PIP

directory

renaming

fo r

input

copies

fi les

file

1into

files.

This

the

same

copying

them

version

of
a
wild
results
1in

number
in
the
card
vers ion
inconsistent
or unpredictable

output.

User Action:
Reenter the command line with
with an explicit or default version number.

PIP

I/0

error

input
One

The

device

not

The

volume

not mounted

The

hardware

The

input

User Action:
correct it.

file

Explanation:

has

d ifferent options

the

following

conditions

may

exist:

online

failed
corrupted

Determine the condition that
Reenter the command line.

2-102

caused

the message

and

MESSAGES

PIP

I/0

error

file

Explanation:

One

The

device

not

online

The

device

not

mounted

The

hardware

®¢

The

volume

full

The

input

file

User Action:
correct

PIP

output

not

Reenter

that

have

does

not

such

the

User

the

condition

command

that

caused

directories,

the

command

for

was

example,

command

line

-—-

The
designated

file(s) specified
directory.

Check

[*,*]

Explanation:

portions where

the

legal

file

the

command

specification,

-—-

open

destination

directory

only wild

User Action:
Reenter
the directory name.

PIP

failure

the

input

name

cards

contains

are

device

specifying

command

access

The

volume

The

specified

The

named

protected

physical
cycled down

Action:

it.

device

file

not

against

has

found

reenter

the

specified

only wild

cards

problem,

not

for

opened.

example,

the

One

the

device

mounted

directory

does

not

Determine

Reenter

not

file

The

and

explicitly

specifying

file

were

allowed.

could

correct

uic

Explanation:
The specified file
following conditions may exist:

User

issued

file(s)

Action:

only

and

printer.

without

command.

PIP

the message

line.

directory~oriented

Explanation:

exist:

directory device

Explanation:

conditions may

corrupted

User Action:
Reenter
directory name.

PIP

following

failed

Determine

it.

has

the

does

not

exist

the

condition

command.

2-103

specified

that

caused

directory

the

message

and

MESSAGES

PIP -- open failure on output

file

The specified file could not be opened.

Explanation:

One of the

following conditions may exist:

is protected against access

The file

The physical device has a problem, for example, the device

The volume

The specified directory does not exist

The named file does not exist in the specified directory

cycled

User Action:
correct

down

it.

is not mounted

Determine the condition that caused the message and

Reenter

the command.

PIP -- output file already exists -- not superseded

Explanation:

An output file of the same

User Action:

Retry the command with a

file

name,

version as the specified file already exists.

and

version

default

new

type,

number.

PIP ~-- version must be explicit or

Explanation:

The version number of the specified

User Action:

Reenter the command line with

expressed explicitly or

as a wild card

(*).

file

must

version

the

number

correctly expressed.

PLG, error in file's prologue

(reconstruct file)

The

User Action:

Reconstruct

the

contents

Explanation:

file

been

have

because the file's prologue has been damaged.

PLV,

the

corrupted

file.

unsupported prologue version

prologue
file's
the
in
The version number field
Explanation:
on open indicates that the file cannot be processed by this
read
version of VAX-11

RMS.

that
RMS
VAX-1l1
of
Verify the version
User Action:
using, and use the correct version to process the file.
PMD,

post-mortem dump,

Explanation:

are

file,

file-name

VAX/VMS

created

post-mortem

dump

requested.

User Action:

you

None.

The message

2-104

informational.

MESSAGES

PRCREAT,

error

creating

process

Explanation:
controller.

This

User Action:

Collect

message

indicates

much

internal

information

error

possible

the

and

job

submit

SPR.

PROC_ID,

identification

created

process

process-id

Explanation:
The RUN command
successfully
created
a
process.
This
message
does
not indicate whether, when the process began
executing,
the
requested
1image
was
started
or
completed
successfully.
The

message

created

displays

User Action:

PRV,

the

process

The

message

identification

number

the

process.

privilege

None.

violation

(operating

informational.

system

denies

access)

Explanation:
The
restricts
access

operating system protection applied to the file
to the file.
The current process is denied the

type

that was

privilege

User Action:
change

Verify
if

the

requested.

protection

necessary.

1If

you

request
the
file's
owner
to
DIRECTORY/FULL command displays
SET

PROTECTION

PURGEVER,

version

command

numbers

can

not

used

User Action:

command;

PUSSTAOVE,

the

pushdown

Explanation:
returned

from

Reenter
file

the

owner

file,
of

the

and
file,

the
protection.
current protection.

change

the

The
The

protection.

the

not

allow

version

not

numbers

specify

version

specification.

stack

This

the

permitted

does

for

not

change
file's

Explanation:
The command
file specification.

number

applied
are

overflow

message

the

1is

Run-Time

associated
Library.

with

The

image

status

code

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.

QUECNT,

queue

count

Explanation:

1is

incorrect

This

message

indicates

internal

error

the

job

controller.

User
an

Action:

Collect

much

information

SPR.

2-105

possible

and

submit

MESSAGES

QUEERR,

create/map queue error

Explanation:

This message

User Action:

Collect as much information as possible and

controller

indicates an internal error

a system failure.

in the job
submit

SPR.

QUEJOBCRE,

Job nnn entered on queue

gqueue-~name

Explanation:
The job controller successfully entered a job in
a
system
printer
or
Dbatch
job
queue.
This message is usually
displayed without

User Action:
QUENOSTOP,

its message

None.

code.

The message

informational.

queue not stopped for operation

Explanation:
A device queue was not stopped before a
INITIALIZE request was issued for the queue.

User Action:
wait

Quo,

for

Stop the queue or

the current

string

quoted

job

issue the STOP/NEXT

The quoted string portion of a
the

User Action:

correct

invalid RAB

and

Use the

file

(block

specification

syntax.

HELP

command

refer

Command
Language
User's
Guide,
1if
necessary,
syntax and reenter the file specification.

RAB,

error

does

have

command

complete.

Explanation:
not

DELETE

identifier

for

the

VAX/VMS

the correct

not=RABSC_BID or RAB not writeable)

Explanation:
block
for
a
RAB is not in
caller.
An

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

operations

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,

illegal

record

access mode

Explanation:
The record access
mode
(RAC)
field
of
the
RAB
indicates
an illegal record access mode.
The field must contain
either

SEQ,

User Action:
coded

KEY,

RFA.

Verify that the call to the VAX-11 RMS

correctly.

2-106

service

was

MESSAGES

RADRMOD,

reserved

addressing

fault

location,

PSL=XXXXXXXX

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:

RAT,

Examine

message

determine

illegal

record

Explanation:
for
a create
or

PRN,

invalid

the

illegal

record

The

virtual

address

that

combination

displayed

caused

that

the

was

specified.

the VAX-11

call

the

error.

RMS

service

was

buffer

The

record
address
field
symbolic address of

correct

buffer

and

The record attributes field of
the
FAB
specified
operation contains a value other than BLK, CR, FTN,

Explanation:
contain
the

instruction

attributes

User Action:
Verify
coded correctly.

RBF,

the
the

be
1is

output

for

area

put,
of

the

buffer

update,

memory

that

RAB
does
not
that contains

write

cannot

operation.

read

the

caller.
User Action:
Verify
coded correctly.

READERR,

error

reading

that

the

call

the VAX-11

RMS

service

was

input-file-spec

Explanation:
An input
file
specified
cannot
be
read.
This
message is usually accompanied by a VAX-11 RMS message indicating
the

reason

User

for

Action:

the

Take

failure.

corrective

action

based

the

associated

message.

RECIO_OPE,

recursive

I/O

operation

unit nnn file file-spec
user PC location
Explanation:
During the
I/0
operation,
another

processing
operation

User

Action:

statement

the

recursive

of a VAX-11
FORTRAN
IV~-PLUS
was
requested
to
the same
logical unit.
This error can occur because 1) an
expression
in
an
I/0
1list contains a function that refers to the same logical
unit;
2) an AST routine performs I/O to the same unit;
or 3)
a
condition
handler
executes
I/0 in response to a signal from an
I/0 statement.

specify
a
operations.

Locate
1I/0

different

the

operation

1logical

program

that

and

correct

the

program

wunit

number

for

one

2-107

in your

caused
of

logic;

the

MESSAGES

RECNUMOUT, record number outside range
unit nnn file file-spec
user

location

Explanation:
A VAX-11 FORTRAN IV-PLUS direct access READ, WRITE,
or
FIND
statement
specified
a record number outside the range

from one to the value specified in the DEFINEFILE statement or
the MAXREC

keyword

the OPEN

statement.

caused
that
program
Locate the statement in your
User Action:
the
error by using the traceback information or the PC displayed
in the message.
Check that the direct access operation specified
the correct record number, and check that the logical unit number
specified in the I/0O
statement
agrees
with
the
1logical
wunit
number

the OPEN

statement.

RECSPEERR, record specification error
unit nnn file file-spec
user

location

Explanation:
The RECORDSIZE value in a
VAX-1l1
FORTRAN
1IV-PLUS
OPEN
statement
or
the
record
size
parameter in a DEFINEFILE
statement is an illegal value (0 or negative);
or is missing
on
a direct

access OPEN

User Action:

statement.

Locate

the

1I/0

statement

your

program

that

A request to connect to an object at a remote

node

caused
the
error
and
check
that
the RECORDSIZE parameter is
present on the OPEN or DEFINEFILE statement and
that
the
value
specified

REJECT,

network

is legal.

Explanation:
failed

for

rejected

connect

one of

the

following

reasons:

The object requested does not exist

The access control

The partner NSP

4.,

The partner

task exited during

The partner

task

User Action:
to correct

REMOTE,

information specified is

has no

invalid

resources

the connect sequence

rejected the connect

Determine which reason caused the failure

and

try

the condition.

assignment completed on remote node

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

2-108

informational.

MESSAGES

REPLACED,

output-file-spec

Explanation:
version.

User

None.

Action:

REQPRMABS,

required

Explanation:
code

being

output

file

This

parameter
This

returned

successfully

message

message
the

replaced

Action:

necessary,

RER,

file

read

Note

associated

with

interpreter's

internal

result

read

User
more

This
input

(STV)

this

terminal

RESERVED,

message
file,

about

status
read

compatibility

HALT,

error.

WAIT,

contains
In

the

your

status
routine.

are
present.
message.

source

program,
'if

condition.

instruction

error

mode

not

RAB

either

read

error

read

the

contains

condition.

occurred,

reserved

image
that

SPL,

address

following
to

the

RSX-11M,

corresponds

could

that

terminal

VAX-11

input

code

Take

RMS

could

occurred.

file,

that

the

provides

corrective

action

code.

RESET,

the

RMS

field

Explanation:
An RSX-11M
following
instructions
mode:

The

Modify
to

indicates

If VAX-11

value

information

based
If

Action:

status

respond

parse

error

Explanation:
not

condition.

and

new

absent

command

the

detect

informational.

It indicates to the caller that not all parameters
The operating system does not normally display this
User

the

input

line.

instruction

attempted
are
not

to execute
allowed in

one
of
the
compatibility

MARK

the

retype

the
PC

instruction
contains

erroneous
RSX-11M

that

the

instruction.
termination

caused

address

This

message

the
the

message
RESERVED

INSTRUCTION.

User Action:
error

RESIGNAL,

Determine

occurred

resignal

and

the

correct

condition

instruction or
the

statement

status

code

used

exception

User Action:

condition

handling

dispatcher

continued

None.

message

The

the

handler

Explanation:
A condition handler completed
without
or continuing the image.
This message is associated
the

at which

error.

2-109

its

routines

for

informational.

terminating
with an exit

indicate

handlers.

that

MESSAGES

RESULTOVF,

resultant string overflow

code
status
a
with
associated
1is
This message
Explanation:
A user buffer specified
from a system service request.
returned

system
The
to receive data from the system was not long enough.
does
not
truncate the data because the loss of data will damage
its

integrity.

that
Verify
error.
a programming
for
Check
User Action:
string descriptors for output data buffers reflect the
character
correct

REWERR,

lengths.

REWIND

error

unit nnn file file-spec
user PC location

while

condition
error
an
returned
RMS
VAX-11
Explanation:
performing a VAX-11 FORTRAN IV-PLUS REWIND operation.

User Action:
Take corrective
action
based
on
the
associated
If possible, run the program again to try to
VAX-11 RMS message.
reproduce

REX,

the

error.

record already exists

to
A put operation using random record access mode
Explanation:
a relative file specified an existing record in the target record
cell.
The new record was not written.

if
Modify the source program,
Note the condition.
User Action:
You may want
to detect and respond to the condition.
necessary,
to include the UIF option in the ROP parameter for the file.

RFA,

invalid

record's

Explanation:
contain
an
expects

address

(RFA=0)

The record's file address field of the RAB does not
address
for a find or get operation when VAX-11l RMS

RFA,

User Action:

Verify that the call to the, VAX-11l RMS service

was

correctly.

coded

RFM,

file

invalid

record

format

contain

Explanation:

The record format field does not

User Action:

Verify that the call to the VAX-1l RMS service

valid

value.

coded

VFC,

<correctly.

and

The valid values for

UDF.

2-110

was

this field are FIX, VAR,

MESSAGES

MESSAGESRHB,

invalid

record

header

buffer

Explanation:

The record header buffer field does not refer to
a
valid
symbolic address for the buffer.
On a get operation, this
message indicates that
the
buffer
cannot
be
written
by
the

caller.

buffer

cannot

put

read

User Action:
Verify
coded correctly.

RLF,

invalid

Explanation:

The

nonzero

with

RLK,

RMV,

related NAM

but

a valid

update operation,

the

that

address
does

not

that

target

locked

The

target

User

Note

the

Action:
to

ACP

function

detect

Explanation:
returned

file

This

from

could

call

the NAM

point

not

the

VAX-1l

block

for

valid

RMS

the

call

that

service

the

was

related
file

the VAX-11

file
NAM

block

RMS

service

was

stream

record

condition.

and

string.

another

Explanation:

necessary,

indicates

block

User Action:
Verify
coded correctly.

remove

the

resultant name

record

caller.

respond

locked

another

stream.

Modify

the

source

program,

the

condition.

failed

message
file

1is

associated

system ACP

removed

QIO

with

request

renamed

made

status
by

code

VAX-11

RMS.

correctly.

User
code

Action:
The status value (STV) field of the FAB contains
a
that
provides
more information about the condition.
Take
corrective action based on this status code.

RNF,

record

not

found

Explanation:
A requested record could not be located in
a
or get operation on a relative file.
Either the record was

written
User

RNL,

has

Action:

been

Note

necessary,

record

locked

not

deleted.

the

detect

Explanation:

This

returned

from

SFREE

a VAX-11

SRELEASE

User

Action:

necessary,

Note

condition.

and

respond

message
RMS

1is

the

not

respond

2-111

with

The

record

the

program,

the

source

condition.

status

specified

locked.
Modify

source

condition.

associated

condition.

and

the

operation.

operation was

detect

Modify
to

find
never

code
for

program,

MESSAGES

ROP,

invalid record options

1illegal

Explanation:

record

option

was

for

specified;

example, EOF was specified for a connect operation for a relative
file.

Verify that the call to the VAX-1ll RMS service

User Action:

was

coded correctly.

ROPRAND, reserved operand fault at PC location, PSL=XXXXXXXX

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
registers, and stack at the time of the exception.

arguments,

User Action: Check for a programming error. Examine the PC
virtual address displayed in the message to determine

RPL,

instruction

that caused the error.

error while

reading prologue

Explanation:
file's

and
the

An I/O error occurred during an attempt to read the

prologue.

(STV)
User Action: Depending on the operation, the status value
provides
that
code
status
a
contains
RAB
or
FAB
the
in
field
Take corrective
additional information about the condition.
action based on this status code.
request aborted

RQSTABORT,

Explanation:

An operator request was denied by

User Action:

None.

the

REPLY/ABORT

command.

RQSTCAN,

This message is informational.

request was canceled

Explanation:

An operator request was successfully canceled.

User Action:

None.

RQSTCMPLTE,

This message is informational.

request complete

user's
a
Explanation: An operator has completed
the user/operator dialogue is complete.
successfully;
User Action:
RQSTPEND,

This message is informational.

request pending

Explanation:

REPLY/PENDING
when

None.

request

able

An operator responded to a user's request with

to do

command.

the

The operator will respond to the request

so.

If the
This message 1is informational.
User Action: None.
interrupt
to
use
,
immediately
satisfied
request must be
the request and send another message.
2-112

MESSAGES

RSA,

record

stream

currently

Explanation:

operation

active

attempt

record

was

made

issue

stream

that

has

request.

User

Action:

necessary,

SWAIT

RSL,

Note
to

request

invalid

before

resultant

Explanation:

the

condition.

detect

The

and

Modify

respond

issuing

any

string

length

VAX-11

RMS

NAM

the

additional

block

VAX-11

outstanding

source

RMS

record

asynchronous

program,

condition.

Include

requests.

contains

invalid

value

in
the
result
string
length field or in 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
coded correctly.

RSLOVF,

result

parse

Explanation:
a

command

User

RSS,

invalid

The

being

buffer

invalid

call

used

parsing

the

string

the VAX~11

RMS

service

was

the
has

command

interpreter

store

overflowed.

command.

size

The resultant string area size does
not
define
a
enough to receive the resultant file specification

returned

User Action:
Verify
coded correctly.

RST,

the

overflow

during

Simplify

resultant

Explanation:
buffer
1large

string

buffer

string

Action:

that

resultant

from

that

string

a VAX-11

the

call

RMS

operation.

the VAX-11

RMS

service

was

address

Explanation:
The resultant string area address in the NAM
block
does
not
define
a
valid symbolic address for the buffer.
The
buffer is in an area of memory that
cannot
be
written
by
the

caller.

User Action:
Verify
coded correctly.

that

the

call

2-113

the

VAX-11

RMS

service

was

MESSAGES

RSZ,

bad record size (RSZ greater than MRS, or not=MRS if fixed length
records)

Explanation:

The record size field of the RAB does not contain a

the record size is greater than that
legal size because either:
the
specified in the maximum record size field of the FAB;

record

size is not the same as the maximum record size specified

for fixed length records;

the

change

or an attempt was made to

record size during an update operation.

The maximum record size value must be in the range of 1 through
32767 for put operations and in the range of 1 through 65535 for
write operations.

User Action:

was

Verify that the call to the VAX-1ll RMS service

coded correctly.

RTB,

nnn byte record too big for user's buffer

Explanation: A record returned from a get operation is too large
for the wuser buffer provided. The message displays the size of
the returned record is truncated
the record that was too large;
to the size of the user buffer.

User Action:
SCTERR,

Correct the program, providing a larger buffer.

error searching SCT

Explanation:

This message indicates an internal error in the job

User Action:

Collect as much information as possible and

controller.

submit

SPR.

SECTBLFUL, section table (process/global)

Explanation:
returned

from

This message
a

system

is full

associated

service

request.

allocated to maintain information about

more sections can be created.

with

The

sections

status

system

1is

full;

code

space

If you have created many private sections, you may
User Action:
1If the
sections when they are no longer needed.
delete
to
have
system
a
1in particular
section,
error occurs while a global
that
indicate
may
message
this
created,
being
global section, is

not enough space was
section tables.

allocated

system

generation

for

Notify the system manager of the deficiency.

2-114

the

MESSAGES

SEGRECFOR,

segmented

record

format

error

unit nnn file file-spec
user PC location
Explanation:
A VAX-11l FORTRAN IV-PLUS unformatted I/0O
operation
failed
because invalid segmented record control data was present
in an unformatted sequential file.
Either the
file
was
opened
with
RECORDTYPE='SEGMENTED'
or
no
RECORDTYPE
parameter
was
specified.
The file may have been created with FIXED
specified or may not have been created by FORTRAN.

VARIABLE

User Action:
Locate the I/0 statement that caused the error
and
check
that the correct logical unit number was specified.
If no
RECORDTYPE is
specified
for
an
unformatted
sequential
OPEN,
segmented
following

records are
record flags

assumed.
in
the

Segmented
first
two

files must contain the
data
bytes
of
each

record:

0
1
2
3
Any

SHR,

middle record
first record
last

record

first

and

other

file

values

sharing

last

results

(SHR)

Explanation:
The
invalid value for
User

Action:

coded

record
in

field

this error.

invalid

for

file

file sharing
field
of
the
the file organization and the

Verify

that

the

call

the

VAX-11

RMS

signal

with

was

arguments

Explanation:
A program called
LIBSSIGNAL or LIBS$STOP with no

the
Run-Time
arguments.

User Action:
Locate the call in
vyour
argument to indicate which condition is

SINCOSSIG, sine or
user PC location
Explanation:
greater

than

all

reserved

cosine

significance

The magnitude
2**31

significance
operand,

1is

minus

DSIN

1lost.

returned

the

error.

wvalid

range.

procedure

program
and
include
to be signaled.

lost

the
or

Library

argument

DCOS
The

was

SIN

greaer

result

than

COS

was

2**63,

such

returned

1is

the

zero.

User Action:
Use the traceback information or the
in
the
message to locate the call to the library

service

correctly.

SIGNO_ARG,

that

FAB
contains
an
specified access.

Correct

your

2-115

program

that

PC
displayed
procedure that
the

argument

MESSAGES

SKPDAT,

data

records

encountered

system were

ignored

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,
are image terminated without reading input data records.

User Action:
Check the
signs
before commands.
that

SMINVOPR,

should

read

the

command
procedure
for
missing
Or, check for the absence of the
data records.

operation not properly

dollar
command

requested

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

Explanation:
option.

This

code

symbiont manager
message

by the job controller.
display this message.

request

associated

The

operating

with

specified
a

system

invalid

status

code

returned

does

not

normally

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.

SMINVREQ,

invalid

symbiont manager

request

Explanation:
A symbiont manager
request
contained
an
invalid
request
code.
This
message
1s
associated with a status code
returned by the job controller.
The operating
system
does
not
normally display this message.
User Action:
call

SMZEROJOB,

the

zero

Check

for

a programming

service

was

coded

length

job

error.

Verify

that

the

correctly.

released

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.

2-116

MESSAGES

SNDRESP,

error

sending

response

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
for
the
failure.
Collect
as much information as
submit an SPR.

SPL,

spool

submit

Explanation:
on

The

that

operation

action

not

file

reason
and

failure

submit

command

file

option

specified

failed.

status

provides

corrective

SQO,

spool

operation

User Action:
code

command

the

possible

value

based

(STV)

field

information

about

this

code.

status

the
the

FAB

contains

condition.

Take

sequential

Explanation:
An attempt was made to perform random access
to
a
file
opened or created with the SQO file processing option;
the
file can only be processed with sequential operations.
User Action:
coded

SQUROONEG,

user

Verify

correctly.

square

root

that

call

negative

the VAX-11l

RMS

service

was

value

location

Explanation:
evaluate
the

returned

User

the

Action:

mathematics
square
root

reserved

Locate

returned the error.
zero or positive.

SSFAIL,

system

the

call

error

failure

exception mode.

STACKDUMP,

your

PSL

system
The

the

1library

program

This
a

service

mode

the

enabled

occurs

Examine

the PC

stack

Explanation:
This
accompanying message

and

virtual

instruction

dump

that

address
caused

error

system

image

system displays the failure
time of the exception.

the

that

argument

status=xxXXXXxXxx,

returned

has

allows

failure

procedure

that

exception,

image

called
to
The result

zero.

status

service

code,

displayed
the

service

signal

system

the

determine

non-symbolic

code.

when

operating

the

User Action:
message

status

exception

The

and

call

minus

failure

severe

call.

operand,

PSL=XXXXXXXX

Explanation:

software

library
procedure
was
of
a
negative
number.

Correct

service

PC=location,

PC,

the

error.

follows

message
precedes
indicates why the

a
traceback
dump.
The
traceback is nonsymbolic.

User
Action:
None.
This
message
is
informational.
nonsymbolic stack dump is displayed following this message.

2-117

The

MESSAGES

STKOVF,

command procedures

are

too deeply nested

Explanation:
The maximum level of nesting of command
procedures
has been exceeded.
Too many procedures invoked other procedures.
User Action:
Simplify the
the level of nesting.

STRINGOVR,

command

procedure hierarchy

reduce

result string

Explanation:
The command string was backtranslated to an RSX-11M
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.
Oor,
if
possible,
issue
several
commands to process all the files.
1In
some cases, for example, a MACRO command
that
requires
one
or
more
library
specifications, it may be necessary to shorten the
file

STRTRU,

names

string

the

input

source

files.

truncated

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

SUBRNG,

receive

the

arithmetic

Correct your program to

increase

the area specified

string.

trap,

subscript

out

range

PC=XXXXXXXX,

PSL=XXXXXXXX

Explanation:
A subscript
exception condition.

out

range

caused

User Action:
Examine the PC location displayed
in
and
check
the
program
1listing
to
verify
that

sup,

variables

are

specified

correctly.

operation

not

supported

over

network,

DAP

code

arithmetic

the
message
operands
or

nnn

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
1in
a
network

context.

User
Action:
Consult
the
DECnet-VAX
User's
Guide
and
the
applicable
DECnet
manual for the remote node to determine which
functions are supported by both the local and remode nodes.
The
status
value (STV) field of the FAB or RAB contains a DAP status
code if the value is nonzero.
See the
DECnet-VAX
User's
Guide
for
an
interpretation of the status code.
(Note, however, that
the explanation is intended for users who are familiar with DAP.)

2-118

MESSAGES

SUPERSEDE,

logical

name

Explanation:
returned

superseded

This message

from

1is

system

associated

service

with

request.

status

request

code

place

logical name in a logical name table
successfully
completed
by
replacing an existing logical name table entry.
(Since this is a
success message, it is not normally displayed.)

This status code
indicates
that
and

version

can also be returned from a call to an ACP;
it
an
existing file with the same file name, type,

number

was

deleted

User Action:

Note

the

condition.

necessary,

detect

SYMBASN,

error

assigning

Explanation:

This

controller

and

respond

symbiont

message

system

the

result

Modify
to

the

CREATE

source

program,

symbiont manager

condition.

mailbox

indicates

internal

error

the

job

failure.

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

SYMBDSAB,

request.

the
reason
possible and

disabled

Explanation:
A
symbiont
manager
request
failed
because
the
symbiont
manager
1is
not
currently
active.
This
message is
associated with a status code returned
by
the
job
controller.

The

operating

system

does

not

normally

display

this

User Action:
Wait and retry the program;
if the
notify the system operator that there is an error

message.

error persists,
in the symbiont

manager.

SYMBWRT,

error

writing

symbiont

Explanation:

This message

controller

User
an

SYMDEL,

Action:

system

Collect

mailbox

indicates

invalid

symbol

containing

as much

error

the

job

information

possible

and

submit

delimiter

An illegal character
symbol
definition.

that arguments were specified
not require arguments.

User Action:
The rejected
between backslashes.

symbiont

delete

This

User Action:

Collect

for

portion

was present on a
This error can
a

lexical

the

command
1line
also indicate

function

command

that

does

displayed

error

Explanation:
controller or

internal

SPR.

Explanation:

SYMDEL,

failure.

message

system

indicates

internal

error

the

job

failure.

much

information

SPR.

2-119

possible

and

submit

MESSAGES

SYMOVF,

room for

symbol definitions

Explanation:
The command interpreter cannot hold any more symbol
definitions
or
1labels.
Note
that this error can occur when a
nested procedure is executed,
because
the
command
interpreter
defines the symbols P1 through P8 before executing the procedure.
If

no ON

the
fail

condition

established

for

warnings

the

procedure,

procedure
continues
execution.
However, the procedure may
later if the symbol that could not be
defined
1is
referred

to.

This error is also issued
explicit
value
for
the
$SSEVERTM.

if an attempt
is
reserved
global

made
to
symbols

define
$STATUS

an
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
procedures.
possible.

SYN,

file

occurs
Use

specification

Explanation:
syntax

The

frequently, simplify the
local
symbols
within

syntax

command procedure or
procedures
whenever

error

file specification

syntax

string

contains

command

error.

User Action:
correct

Correct

the program

the

that

SYNERRFOR, syntax error in
unit nnn file file-spec
user PC location

syntax
caused

and

the

reenter

the

error.

format

Explanation:
A FORTRAN syntax
error
occurred
while
a
VAX-1l1
FORTRAN
IV-PLUS
specific
procedure of the Run-Time Library was
compiling a format stored in an array or
character
variable
at
program run time.

User Action:
Locate the I/0O statement in your program
in
which
the
format specification was a variable or expression instead of
a statement number.
Check that the
resulting
expression
1is
a
valid FORMAT

SYNTAX,

error

specification,

parsing

Explanation:
displays the

User Action:

including

left and

right parentheses.

'string’

The
command
syntax
1is
1invalid.
rejected portion of the command.

Use the

Command
Language
syntax and reenter

HELP

command

User's
Guide,
the command.

2-120

1if

refer

necessary,

The

for

the

message

VAX/VMS

correct

MESSAGES

SYNTAXERR,

string

syntax

error

detected

The

string

passed

Explanation:
procedure

contained

User Action:

SYS,

system

(QIO)

message

syntax

Correct

the

directive

Explanation:

issue

VAX-11

$QIO
may

occur

insufficient
its AST limit

the

LIB STPARSE

library

error.

string.

error

RMS

system

LIBSTPARSE

encountered

service

request

calls

resource quotas;
quota.

error

for

VAX-1l1l

for

I/0

RMS

example,

while
trying
to
operation.
This
fail
because
of
a

process

exceeds

User Action:
The status value (STV) field of th e 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/0O operations.

SYSDEV,

the

system

device

cannot

Explanation:
The device
is the system volume.
User Action:
logical
name
DISMOUNT

SZTOOBIG,

specifying

size

Explanation:
The
/BLOCK is greater
User action:
correction.

TAPEPOSLOST,

the

magnetic

tape

TBIT,

the

all
it

error

persists,

the

mode

correct

greater

tape

device.

size

spec ified

program

and

mak e

the

necessary

lost

the

current

position

/REC

lost

ACP

has

processing.

files.

the

command

block

tape

DISMOUNT

6553 4

continue

open

the

than

source

magnetic

cannot

position

compatibility

size

name
(or
1logi cal
name,
if
a
in
the
command
and reenter the

the

position

and

tape

the

block

tape

The
and

User Action:

specified

record size
than 65534.

Check

Explanation:

name

dismounted

Verify the device
was
specified)

command

record

Dismount

desired

may

position,

and

remount

the

if possible.

1If

bad.

T-bit

Explanation:
An RSX-11lM image executed an instr uction requesting
a
T-bit
trap.
This
message
corresponds
to
the
RSX-11M
termination message

User
error

Action:
occurred

T-BIT

Determine
and

EXECUTION.

the

correct

instruction
the

error.

2-121

statement

at which

the

MESSAGES

TBIT, T-bit pending trap at PC

location,

PSL=XXXXXXXX

Explanation:
is
usually

This message indicates an exception
condition
and
followed
by
a
display of the condition arguments,
and stack at the time of the exception.

registers,

User Action:
message

TBKBUG,

Examine the PC and virtual address displayed in the

to determine

please

the

report TRACE

Explanation:

instruction that caused

bug no.

the error.

nnn

An internal coding error occurred in the

traceback

program.

User Action:
an

SPR.

Collect as much information as possible and

Include the bug number displayed

in the message

submit
in the

report.

TERMDSBL,

terminal disabled

Explanation:

User Action:

None.

REPLY/DISABLE

TERMENAB,

terminal

Explanation:

terminal

command.

This message

terminal

command.

User Action:

None.

device

successfully
is

disabled

with

the

with

the

informational.

enabled

REPLY/ENABLE

TIMEOUT,

was

successfully

This message

enabled

informational.

timeout

Explanation:
An input operation did
not
complete
because
the
timeout
period
specified
with
the
request elapsed before the
input was received.
1If 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.

TMO,

timeout period

expired

Explanation:
A VAX-11 RMS operation specified a
timeout
period
and
the
timeout
period expired before the operation completed.
The operation did not complete.

procedure,
If this message occurs during the login
User Action:
the program
on
depend
actions
Other
procedure.
the
repeat
issuing the request;
user programs should be coded to detect and
respond

I/0

timeouts.

2-122

MESSAGES

TOOMANY,

too many

file

specifications

Explanation:
are allowed.

User Action:

Reenter

TOOMANYVER,

command

contained more

the

too many higher

file

specifications

than

command.

file versions

Explanation:
This message
1is
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
numbers
are
greater
than
the
version
number
specified.
User Action:
Check
number specified in

TOOMUCHDATA,

too much

for
the

a programming
I/0 request.

optional

error.

Verify

interrupt message

Explanation:
A network interrupt message was
contains more than 16 bytes of data.

User Action:
bytes

TRACEBACK,

TRAP,

Repeat

the

request;

stack

dump

follows

not

the

wversion

data
rejected

specify

because

than

data.

symbolic

Explanation:

This message

User Action:

None.

compatibility mode
Explanation:
This
message

precedes

This message

TRAP

symbolic

traceback

dump.

informational.

execution

The RSX-11M
corresponds

image
to the

executed
a
TRAP
instruction.
RSX-11lM termination message TRAP

EXECUTION.

User Action:

TYP,

Determine

error

occurred

error

file

and

the

correct

instruction or
the

Reenter

UAFOPN,

user

the

at which

the

type

Explanation:
The file type specified
in
contains invalid syntax, for example, more
Or, the use of a
1logical
name
resulted
specification.
User Action:

statement

error.

Correct
command

authorization

the

syntax

correct

file

the

open

the

program,

a
file
specification
than three characters.
1in
a
duplicate
file

file
as

specification.

necessary.

error

Explanation:
The input card reader symbiont could not
read
the
user
authorization
file.
This
message
1indicates an internal
operating system error.

User Action:
an

Collect

as much

information as possible

SPR.

2-123

and

submit

MESSAGES

UBF,

UFD

invalid

user

buffer

Explanation:
The user record
valid
buffer;
the buffer is
written by the caller.

area address
in an area of

User Action:
Verify
coded correctly.

call

—~-—

access
reason

indicated

UFD

-~—-

second

reason,

and

device

not

Explanation:
command does

User Action:

—-

VAX/VMS

message

User Action:

UFD

the
and

required
reissue

directory

Take
reenter

--—-

RMS

service

was

access

for

corrective

the

the directory.

The

failure.

action,

based

the

command.

not

the
the

failed
reason

reason

for

required

action,

the
the

based

directory

file.

failure.

the

indicated

command.

device
in

specified
in
host system.

exist

Reenter

already

the

CREATE/DIRECTORY

the

command

specifying

valid

device

name.

exists

the

specified

name

already

exists

CREATE/DIRECTORY command
specifying
or use the existing directory.

to create directory
for failure

Explanation:
occurred.

able

the

system

The
not

was

provides

User Action:
Reenter the
different directory name,

UFD

able

reason

Explanation:
A directory with
on the volume.

UFD

the VAX~1l1l

close failure on directory
reason for failure

The

—-

Take

the

a
be

directory

was not

provides

reason,

Explanation:

UFD

VAX/VMS

message

User Action:

UFD

the

failure on existing
for failure

Explanation:
second

that

does
not
specify
memory that cannot

No
The

space
second

exists

message

the

volume,

provides

the

I/0

reason

for

error
the

failure.
User Action:
If no space exists, delete any unnecessary files or
compress
the
volume
wusing
DSCl or DSC2;
disk compression may
require operator intervention.
If an I/0 error occurred, ensure that the device
the volume is mounted;
then retry the command.

2-124

1is

online

and

MESSAGES

UFD
UFD

---

failed
reason

to initialize
for failure

directory

Explanation:
VAX/VMS was
file.
The second message

not able
provides

to
the

1initialize
reason for

User Action:
Take the required corrective
reason indicated, and reenter the command.

UFD

not

Files-1l1

Explanation:

the
directory
the failure.

action,

based

The

Action:
volume.
If

the

device

volume

on which

the

directory was

is
not
a
Files-11
structured
volume.
You
cannot
directory on a foreign volume with the CREATE/DIRECTORY
User

Reenter the command
necessary, initialize

specifying
the volume

created

create a
command.

a
wvalid
Files-11
with the INITIALIZE

command.

UFD

syntax

error

Explanation:

The

User Action:

Correct

too

many

command

the

subdirectory

Explanation:
subdirectory

volume

not

can

User

Action:

use

the

reenter

UNASEFC,

The

mounted.

structure

command

the

command

volume

Ensure

that

command

and

correct

reenter

the

specifying

unassociated

event

This
a

from

for

must

format.

the

command.

1limit

the

volume
access

eight

than

eight

numbers

mounted

command

before

the

file

flag

message

system

Check

for

the required request
successfully.

1is

file

associated
request.

number

programming
in

physically

the

mounted

structure.

and
Then,

cluster

service

specified

command.

service specifying an event flag
which it was not associated.
Action:

a CREATE/DIRECTORY
be

CREATE/DIRECTORY

returned

flag

line

the

accessed.

Explanation:

User

levels

target

The

MOUNT

the

not

mounted

Explanation:
not

You are attempting to exceed
levels for a directory.

User Action:
Reenter
directory levels.

UFD

line

system

associate

2-125

with

image

called

common

error.

service

with

status

the

code
system

cluster

Verify
calls

and

<cluster

the
verify

with

event

that
completed

MESSAGES

UNDEXP, undefined exponentiation
user PC location

Explanation:
An expression contained exponentiation that
cannot
be
mathematically
evaluated,
for example 0.**0.
The result is
the

reserved operand,

minus

zero.

User. Action:
Use the traceback information or the
PC
displayed
in
the
message
to locate the error in your program and correct
the mathematical expression.

UNDFIL,

file not open

Explanation:
A READ or WRITE command specified a
not currently opened or for which no logical name

file
that
is assigned.

User Action:
Reenter the command;
specify the name
file.
Or,
use
the
OPEN
command
to
open
the
attempting to read or write it.

UNDSYM,

1is

of an opened
file
before

undefined symbol

Explanation:
A character string
character
was
encountered
in

beginning
with
an
alphabetic
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
1is
defined
1locally
or
globally as required before the statement that caused the error.

UNEXPLIST,

qualifier

only

takes

single value

Explanation:
A list of values was
accepts only a single value.

User Action:
Use
Command
Language
syntax

and

specified

for

a qualifier

that

the
HELP
command
or
refer
to
the
VAX/VMS
User's
Guide,
1if
necessary, for the correct

reenter

the

command.

UNIALROPE, unit already open
unit nnn file file-spec
user PC location
Explanation:

DEFINEFILE

VAX-1ll1

FORTRAN

IV-PLUS

OPEN

statement

statement was attempted which specified a logical unit

already opened

for

input or

output.

User Action:
Locate the OPEN or DEFINEFILE statement that caused
the
error.
Verify
the logical unit numbers in the conflicting
statements;
if
they
are
to
be
the
same,
insert
a
CLOSE
statement, delete the second OPEN statement, or change one of the
logical unit numbers.

2-126

MESSAGES

UNKDEV,

unknown

device

Explanation:

type

The

device

type

specified,

User Action:
Verify the device
logical
name
was
specified),
correct device name.

UNKNOPR,

unknown

unknown or

name
(or
logical
name,
if
a
and reenter the command with the

A REQUEST

name;

the

keyword

command

invalid.

specified

message

sent.

User Action:
Reenter
valid operator name.

UNPROPARM,

unprocessed

Explanation:
currently

UNPROQUAL,

REQUEST

command;

parameters

command

Reenter

unprocessed

returned

message

ignored.

contained

the

command;

message

the

1is

command

indicates

The

was

specify

only

than

the

are

maximum

qualifiers

This

from

invalid

parameters

parameters.

Explanation:
The

the

request

supported.

User Action:
number

invalid.

operator

Explanation:
operator

that

operating

associated

with

interpreter's

qualifiers

system

present

does not

result
on

status
parse

code

routine.

the

command

were

normally

display

this

program,

message.

User Action:

Note

necessary,

detect

UNRKEY,

keyword

the

condition.

and

respond

unrecognized

Explanation:

This

message

returned

the

Run-Time

from

Modify
to

the

UNSAFE,

drive

1is

associated

Library.

The

User

Action:

request.

the

program

and

with

indicated

specify

status
keyword

valid

code
is

not

keyword.

unsafe

Explanation:
returned

Correct

source

keyword

recognized.

User Action:

the

condition.

This
I/O

Check
the

message

functions.

the

failure

1is

associated

The

drive

status

persists,

2-127

with

used.

cannot

the

device

notify

the

and

system

status

repeat
manager.

code

the

MESSAGES

UNWIND,

in progress

unwind currently

Explanation:
This message
1is
associated
with
a
status
code
This status code is used
returned from a system service request.
the
during
called
handlers
condition
for
as a call argument
The
operation.
unwind
an
during
stack
<call
the
of
search
operating system does not normally display this message.

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

unwind already

in progress

code
status
a
with
associated
1is
This message
Explanation:
A condition handler was
from a system service request.
returned
an
1issue
to
attempted
and
operation
called during an unwind
display
normally
not
does
system
operating
The
request.
unwind
this message.

User Action:
necessary,

USEFLORES,

Note the condition.

to detect and respond

use of floating

Modify the source program,

1if

to the condition.

reserved operand

Explanation:
A program accessed
a
reserved
floating
operand.
This
message
1is
associated
with a status code returned by the
Run-Time

Library.

User Action:

Use

the

statement that caused

traceback

the error

information

locate

the

and correct your program.

user validation error

USERVAL,

reader
card
the
through
submitted
3job
A batch
Explanation:
failed;
the
user name or password did not match entries in the
user

authorization file.

User Action:
and

USGOTO,

The job

is deleted.

Correct the JOB or PASSWORD card,

resubmit the

job.

appropriate,

unsatisfied GOTO command

be
A GOTO command in a command procedure could not
Explanation:
because the label does not exist in the current command
executed
procedure.

the
because
This error causes a command procedure to terminate,
command interpreter has read to the end of the procedure and does
not

know where

return.

the
that
verify
procedure;
Correct the command
User Action:
spelled correctly, that it is terminated with a colon,
1is
label
the
If
colon.
the
and that the GOTO command does not specify
1is referred to using a symbol name, verify that the symbol
label
name is preceded with the substitution operator (').

2-128

MESSAGES

usz,

invalid

user

buffer

Explanation:
field
range

User
coded

VALCNVERR,

for
of

The

size specified in the
user
buffer is invalid.
The buffer

the

through

error

non-numeric

numeric
between

User Action:

VALREQ,

incorrect

value

the

call

specified

rejected

the

HELP

User's

for

portion

command

Guide,

Action:

Command

the

Use

Language

the

HELP

User's

that

command

Guide,

refer

VASFULL,

virtual

address

space

This

message

system

service

process's

request.

virtual

address

the

size

there

1is

qualifier
example,

that

requires

displayed

the

legal

space

Action:

necessary,

Note
to

the

legal

with

status

the

detect

error

version

Explanation:

invalid.
User

Action:

reenter

the

The

was

VAX/VMS
values

full

associated

available

request

space

1in

increase

failed

because

the

page

source

tables

condition.

Modify

the

condition.

respond

the

pages

space

code

and

the image deletes dynamically
obtained
longer needed to ensure that there will

VER,

values

value

process.

User

VAX/VMS

for

command.

the
no

for

necessary,

the

from

For

requires

reenter

returned

was

qualifier

and

Explanation:

service

command

refer

command.

required

RMS

for

qualifier

necessary,

Explanation:
A command
qualifier
specified without a value.
User

the VAX-11l

value was specified
a
certain
format.

1in

was

Use

Language

reenter

the

value

data

value.
The
backslashes.

Command

that

converting

value

record
area
size
size must be in the

65535,

Action:
Verify
correctly.

Explanation:
An
that
expects

and

size

for

program,
Verify

the

if
that

they
are
available.

specification

number
version

Correct
command

the

number

syntax

correct

the

2-129

the

file

program,

specification
necessary.

and

MESSAGES

VFEVALERR, variable format expression value error
unit nnn file file-spec
user PC location

The value of

Explanation:

enclosed

expression

format

VAX-1ll

FORTRAN

in angle brackets

IV-PLUS

variable

in a FORMAT

(< >)

its intended
statement is not within the range acceptable for
For example, a field width is less than or equal to zero.
use.

User Action: Use the traceback information or the PC displayed
in the message to locate the I/O statement that contained an
Check the wvalue of the
invalid variable format expression.
expression and correct your program.

VOLALRMNT, another volume of same label already mounted

Explanation:

Shared, group, and system volumes that are

mounted

volume

already

have

must

concurrently

mount a volume that has
failed.

mounted

unique

same

the

volume

label

labels.

The request to

if it does
User Action: Mount the volume as a private volume,
or wait until the conflicting volume has
not have to be shared;
been dismounted. You can determine the status and ownership of
volume with the SHOW DEVICES/FULL/MOUNTED
conflicting
the
command.

VOLIDENT, label

'volume-format'

‘'volume-label',

owner

‘'user-name',

format

Explanation: This is an informational message that identifies an
incorrectly specified volume after the INCVOLLABEL and NOHOMEBLK
errors

in a MOUNT

request.

is
message
The
necessary.
is
action
No
User Action:
If the volume protection allows access to the
informational.

volume,

VOLINV,

reissue the MOUNT command.
is invalid

volume

Explanation:

This message

1is

associated

with

status

code

returned by I/0 functions. The volume valid bit is not set for
the volume. All physical and logical 1I/0 operations will be

rejected until the bit is set.

User Action:
volume

retrying

WASECC,

Check for a programming

mounted

error.

Verify

that

the

and that the power is on before

loaded

and

the program.

successful transfer;

Explanation:

no data check

This message

associated

with

status

code

A data check operation on a read
returned by I/0 functions.
request would fail; however, one or more ECC corrections were

performed and the operation completed successfully.

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

2-130

MESSAGES

WBE,

write

behind

error

Explanation:
An error occurred during
which write behind was specified.

a VAX-11]

RMS

operation

for

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.

WER,

file

write

error

Explanation:

error

occurred

The

status value

during

VAX-1ll

RMS

write

the

contains

operation.

User Action:
code

that

provides

corrective

WLD,

invalid

action

wildcard

based

(STV)

field

information

about

this

code.

status

the

RAB

condition.

Take

operation

Explanation:
A call to the VAX-11 RMS delete service specified a
wild
card in one or more components of a file specification.
No
wild cards are allowed.

User Action:

Correct

was

VAX-11l

service,
wild

WLK,

RMS

you must

card

device

the

coded

code

specifications

write

source program.

correctly.

loop

that

and

deletes

Verify

perform

searches
the

for

files

that
wild

the
card

files

call
delete

based

individually.

locked

Explanation:
The hardware device
specified
operation
1is
write
1locked for protection,

for
a
VAX-1l1
and write access

RMS
was

attempted.
User

Action:

Verify

the

status

the

hardware

the
write lock switch, if necessary.
if the error cannot be corrected.

WPL,

error

while

writing

occurred

User Action:

the

Depending on

the

FAB

RAB

WRIREAFIL, write to READONLY
unit nnn file file-spec
user PC location

while VAX-11]

operation,

contains

additional information
about
the
action based on this status code.

device;

reset

system operator

RMS

was

writing

status value
code

that

Take

(STV)

provides

corrective

file

User Action:
and
verify

Locate the WRITE statement
the
1logical
wunit
number.

the

status

condition.

Explanation:
attempted to

parameters

the

prologue

Explanation:
An I/0 error
a file's prologue area.

field

Notify

VAX-11
FORTRAN
1IV-PLUS
WRITE
operation
was
that was opened with the READONLY parameter.

file

the

OPEN

statement.

2-131

that
If

caused
correct,

the
error
verify the

MESSAGES

WRITLCK,

[write

lock

error]

[volume

on device

is write

locked]

Explanation:
The volume cannot be written because
write lock switch is set on the drive.

User Action:

Release

the

write

1lock

switch

the

and

hardware

retry

the

program.

WRONUMARG, wrong number
user PC location

Explanation:
wrong

number

arguments

A mathematics library procedure was called with
of

the

arguments.

User Action:
Locate the call that returned the error and correct
the
call.
See
the
VAX-1l1l
Common
Run-Time Procedure Library
Reference Manual for a description of the required arguments.

WSF,

working

set full

(cannot lock

buffers

in working

set)

Explanation:
A VAX-11l RMS connect request specified
a
positive
multibuffer count but the buffers cannot be locked in the working
set of the process.
The working set is full.

User Action:

XAB,

Specify fewer

Specify a negative value for the multibuffer
count
the buffers are not locked in the working set

Use the SET WORKING*SET command to increase the size
of
the
working set (if it 1s not already at its authorized limit)

not a valid XAB

buffers

location

the multibuffer

(bad

length or

count

that

not writeable)

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
1length
field.
The
status
value
(STV)
field of the FAB provides the
address

the

User Action:
coded

XAB

error.

Verify that the call

correctly.

2-132

the VAX-1ll

RMS

service

was

APPENDIX

ERROR CODES

File

Error

Code

Number

Name

-01.
-02.
-03.
-04.

Control

Table A-1
Services

Error

Codes

Meaning

IE.BAD

Bad

IE.IFC

IE.DNR

Invalid function
Device not ready

parameter
code

IE.VER

Parity

-05.

IE.ONP

Hardware

-06.
-07.
-08.
-09.

IE.SPC
IE.DNA
IE.DAA
IE.DUN

Illegal user buffer
Device not attached

-10.
-11.
-12,
-13.
-15.
-16.

IE.EOF
IE.EOV
IE.WLK
IE.DAO
IE.ABO
IE.PRI

End of file detected
End of volume detected
Write attempted to locked
Data overrun
Request terminated
Privilege violation

error

option

Device

already

Device

not

device
not

present

attached
attachable

unit

-17.

IE.RSU

Shareable

~-18.

IE.QVR

-19.
-20.

Illegal

IE.BYT
IE.BLK

-21.
-22.

0dd byte count (or virtual address)
Logical block number too large

IE.MOD
IE.CON

-23.

resource

overlay

use

request

IE.NOD

~24 .

Invalid UDC module
UDC connect error
Caller's nodes exhausted

IE.DFU

Device

-25.
-26.
-27.

IE.IFU

Index

IE.NSF

IE.LCK

Locked

-28.

IE.HFU

File

header

-30.

IE.CKS

File

header

-31.

IE.WAT

Attribute
File

full

file

such

-32.

IE.RER

-33.

IE.WER

File

-34.

IE.ALN

File

full

file

from

read/write

access

full

checksum failure
control list format error
processor device read error
processor device write error
already accessed on LUN
ID, file number check

-35.

IE.SNC

File

-36.
-37.
-38.

IE.SQC
IE.NLN
IE.CLO

-39.

File ID, sequence number
No file accessed on LUN
File not properly closed

IE.NBF

Open

-40.
-41.

IE.RBG
IE.NBK

Illegal record size
File exceeds space allocated,

buffer

space

check

available
no

for

file

blocks

(continued

next page)

ERROR CODES

Table A-1

(Cont.)

File Control Services Error Codes

Error

Code

Number

Name

-42.

IE.ILL

-45,
-46.
-48.
-49.
-50.

IE.RAT
IE.RCN
IE.2DV
IE.FEX

-43,
-44,

-51.
-52.
-53.
-54,
-55,
-56.

-57.
-59.
-60.
-61.

-62.
-63.
-64.
-65.

-66.
-75.

-76.

-77.
-82.
-83.
-84.
-85.
-86.

IE.BTP
IE.RAC

Meaning

Illegal operation on file descriptor block

Bad record type
Illegal record access bits set

Illegal record attributes bits set
Illegal record number - too large
Rename ~ two different devices
Rename - new file name already in use

IE.BBE

Bad directory file
Cannot rename old file system
Bad directory syntax
File already open
Bad file name
Bad device name
Bad block on device

IE.EOT
IE.BVR
IE.BHD
IE.OFL

End of tape detected
Bad version number
Bad file header
Device off line

IE.BDR
IE.RNM
IE.BDI
IE.FOP

IE.BNM
IE.BDV

IE.DUP
IE.FHE
IE.NFI
IE.ISQ

IE.BCC
IE.EXP

IE.BTF

IE.NNC
IE.IES
IE.PED
IE.ALC
IE.ULK
IE.WCK

Enter - duplicate entry in directory
Fatal hardware error on device
File ID was not specified
Illegal sequential operation

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

Error

Code

(Standard System Codes)

Meaning

Number

Name

-01.
-02.

IE.UPN
IE.INS

Insufficient dynamic storage
Specified task not installed
Partition too small for task

-05.

IE.ULN

Unassigned LUN

IE.ACT

Task not active

-03.
-04.
-06.

-07.

-08.
-09.
-10.
-11.
-15.
-16.

IE.PTS
IE.UNS

IE.HWR
IE.ITS
IE.FIX
IE.CKP

IE.TCH
IE.RBS
IE.PRI

Insufficient dynamic storage for send

Device handler not resident
Directive inconsistent with task state
Task already fixed/unfixed
Issuing task not checkpointable
Task is checkpointable
Receive buffer is too small
Privilege violation

(continued on next page)

ERROR CODES

Directive

Error

Code

Number

Name

Table A-2 (Cont.)
Error Codes (Standard System Codes)

Meaning

-17.

IE.RSU

Resource

-18.

IE.NSW

Illegal vector specified
Directive issued/not issued
Illegal mapping specified

-19.

IE.ILV

-80.

IE.AST

-81.

IE.MAP

-83.

IE.IOP

-84.

IE.ALG

-85.

IE.WOV

-86.

IE.NVR

swap

in use
space available

Window

has I/O in
Alignment error

Address
Invalid

window
region

progress

allocation

IE.NVW

-88.
-89,

IE.ITP
IE.IBS
IE.LNL
IE.IUI
IE.IDU
IE.ITI

-94,

Invalid TI parameter
Invalid send buffer size
LUN locked in use
Invalid UIC
Invalid device or unit
Invalid time parameters

IE.PNS

-95.

Partition/region

IE.IPR

-96.

IE.ILU

Invalid
Invalid

-91.
-92.

-93.

overflow

~-87.

-90.

from AST

Invalid address window I/O

priority
LUN

-97.

IE.IEF

Invalid

-98.

event

IE.ADP

Part

-99,

DPB

IE.SDP

DIC

DPB

(greater

than

not

in system
(greater than

250.)

flag (greater than
out of user's space
size invalid

64.)

255.)

VAX/VMS
System Messages
Recovery

and

Procedures

Manual

AA-D017A-TE
READER'S

NOTE:

This
use

form

comments

discretion.
eligible
Report
form.

Did you

you

Please

comments

this

find errors

indicate

the

Assembly

receive

one

service,

under

User with

for

type of

language

Occasional

DIGITAL will

company's

the

Software Performance

submit your

comments

usable,

improvement.

in this manual?

Higher-level

only.

form

1If you require a written reply and are

suggestions

number.

Oo0OOooO

Please cut along this line.

Did

document

submitted

find this manual understandable,

Please make

page

(SPR)

for

COMMENTS

reader

1If

so,

little

specify

the

that you most nearly

programmer

(experienced)

programming

experience

Student programmer

Other

(please

specify)

Name

Date

Organization
Street

City

State

SPR

and well-organized?

language programmer

programmer

Zip Code
or

Country

error

and

represent.

the

Fold Here

Do Not Tear - Fold Here and Staple

FIRST CLASS

PERMIT NO. 33
MAYNARD, MASS.
BUSINESS REPLY MAIL

‘

NO POSTAGE STAMP NECESSARY IF MAILED IN THE UNITED STATES

Postage will be paid by:

Software Documentation
ML5-5/E39
146 Main Street
01754
Maynard, Massachusetts