Digital PDFs

AA-LA17A-TE

December 1988

382 pages

Original

15MB

Document:	VMS System Messages and Recovery Procedures Reference Manual: Partl
Order Number:	AA-LA17A-TE
Revision:
Pages:	382
Original Filename:	http://bitsavers.org/pdf/dec/vax/vms/5.0/AA-LA17A-TE_VMS_5.0_System_Messages_and_Recovery_Procedures_Reference_Manual_Part_1_198804.pdf

OCR Text

VMS System Messages
and Recovery Procedures
Reference Manual: Part I
Order Number: AA-LA 17 A-TE

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

Revision/Update Information:

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

Software Version:

VMS Version 5.0

digital equipment c~rporation
maynard, massachusetts

April 1988
The information in this document is subject to change without notice and should
not be construed as a commitment by Digital Equipment Corporation. Digital
Equipment Corporation assumes no responsibility for any errors that may appear
in this document.
The software described in this document is furnished under a license and may be
used or copied only in accordance with the terms of such license.
No responsibility is assumed for the use or reliability of software on equipment
that is not supplied by Digital Equipment Corporation or its affiliated companies.
Copyright © 1988 by Digital Equipment Corporation
All Rights Reserved.
Printed in U.S.A.
The postpaid READER'S COMMENTS form on the last page of this document
requests the user's critical evaluation to assist in preparing future documentation.
The following are trademarks of Digital Equipment Corporation:
DEC
DEC/CMS
DEC/MMS
DECnet
DECsystem-10
DECSYSTEM-20
DECUS
DECwriter

DIBOL
EduSystem
IAS
MASS BUS
PDP
PDT
RSTS
RSX

UNIBUS
VAX
VAXcluster
VMS
VT

~U~Ull~D™
ZK4517

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

CANADA

INTERNATIONAL

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

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

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

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

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

PostScript is a trademark of Adobe Systems, Inc.

Contents
PREFACE

vii

NEW AND CHANGED FEATURES

xiii

CHAPTER 1 INTRODUCTION

1-1

1.1

MESSAGE DISPLAY

1-1

1.2

RETRIEVING A SYSTEM MESSAGE

1-1

1.3

EXCEPTION CONDITIONS

1-2

1.4
1.4.1
1.4.2
1.4.3

FORMAT OF SYSTEM MESSAGES
Messages Without I DENTS
Severity Levels
Linked Messages

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

1.5
1.5.1
1.5.2
1.5.3
1.5.4

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

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

1.6

EXAMPLES

1-6

CHAPTER 2 MESSAGES

2-1

TABLES
1

Facility Abbreviations

vii

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

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

Associated Documents
The VMS System Messages and Recovery Procedures Reference Manual: Part I
is the first part of the VMS System Messages and Recovery Procedures Refere nee
Volume. You can find messages MACHINECHK through ZEROPAGE in the

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

Facility Abbreviations

Facility
Abbreviation

Facility Name

Document

ACCOUNTING

Accounting Utility

VMS Accounting Utility
Manual

ACLEDIT

Access Control List Editor

VMS Access Control
List Editor Manual

AUTHORIZE

Authorize Utility

VMS Authorize Utility
Manual

BACKUP

Backup Utility

VMS Backup Utility
Manual

BAD

Bad Block Locator Utility

VMS Bad Block Locator
Utility Manual

CDU

Command Definition Utility

VMS Command
Definition Utility Manual

CLI

Command Language Interpreter
(DCL)

Guide to Using VMS
Command Procedures

vii

Preface

viii

Table 1 (Cont.)

Facility Abbreviations

Facility
Abbreviation

Facility Name

Document

CONVERT

Convert Utility

VMS Convert and
Convert/Reclaim Utility
Manual

CONVERT_R

Convert/Reclaim Utility

VMS Convert and
Convert/Reclaim Utility
Manual

CREF

Cross-Reference Utility

Guide to VMS
Programming Resources

DCL

DIGIT AL Command Language

VMS DCL Dictionary

DCX

Disk Compression Facility

VMS Utility Routines
Manual

DEBUG

VMS Debugger

VMS Debugger Manual

DIFF

DIFFERENCES Command

VMS DCL Dictionary

DISMOUNT

DISMOUNT Command

VMS DCL Dictionary

DSR

VAX DIGIT AL Standard Runoff

VAX DIGITAL Standard
Runoff Reference Manual

DTR

DECnet Program Protocol

VMS DECnet Test
Sender/DECnet Test
Receiver Utility Manual

DTK

VMS RTL DECtalk (DTK$) Facility

VMS RTL DECtalk
(DTK$) Manual

DUMP

File Dump Utility

VMS DCL Dictionary

EDT

EDT Editor

VAX EDT Reference
Manual

ERF

Error Log Utility

VMS Error Log Utility
Manual

EVL

Event Logger

VMS Networking
Manual

EXCHANGE

Exchange Utility

VMS Exchange Utility
Manual

FOL

Create/FOL Utility

VMS File Definition
Language Facility Manual

FOL

Edit/FOL Utility

VMS File Definition
Language Facility Manual

IMPSMB

Input Symbiont

Guide to Maintaining a
VMS System

INIT

INITIALIZE Command

VMS DCL Dictionary

INSTALL

Install Utility

VMS Install Utility
Manual

JBC

Job Controller

VMS System Services
Reference Manual

Preface

Table 1 (Cont.)

Facility Abbreviations

Facility
Abbreviation

Facility Name

Document

LATCP

LAT Control Program

VMS LAT Control
Program (LA TCP)
Manual

LBR

Librarian Utility

VMS Librarian Utility
Manual

LIB

VMS RTL Library (LIB$) Facility

VMS RTL Library (L/8$)
Manual

LIBRAR

LIBRARY Command

VMS Librarian Utility
Manual

LINK

Linker Utility

VMS Linker Utility
Manual

VMS DCL Dictionary

MACRO

VAX Macro Assembler

VAX MACRO and
Instruction Set
Reference Manual

MAIL

Mail Utility

VMS Mail Utility Manual

MESSAGE

Message Utility

VMS Message Utility
Manual

MOM

Maintenance Operation Module

VMS Networking
Manual

MONITOR

Monitor Utility

VMS Monitor Utility
Manual

MOUNT

MOUNT Command

VMS DCL Dictionary

MTH

VMS RTL Mathematics (MTH$)
Facility

VMS RTL Mathematics
(MTH$) Manual

NCP

Network Control Program

VMS Networking
Manual

NET

DECnet Test Program Protocol

VMS Networking
Manual

NICE

Network Information and Control
Exchange

VMS Networking
Manual

OPCOM

Operator Communication

Guide to Maintaining a
VMS System

OTS

VMS RTL General Purpose (OTS$)
Facility

VMS RTL General
Purpose (0TS$) Manual

PATCH

Patch Utility

VMS Patch Utility
Manual

PPL

VMS RTL Parallel Processing
(PPL$)
Facility

VMS RTL Parallel
Processing (PPL$)
Manual

PRINT Command

VMS DCL Dictionary

PSI

Packetnet System Interface

VMS Networking
Manual

Preface

Table 1 (Cont.)

Facility Abbreviations

Facility
Abbreviation

Facility Name

Document

PSM

Print Symbiont

VMS Utility Routines
Manual

OUEMAN

Queue Manager

Guide to Maintaining a
VMS System

REM

Set Host Facility

VMS DCL Dictionary

RENAME

RENAME Command

VMS DCL Dictionary

RMS

VMS Record Management Services

VMS Record
Management Services
Manual

RUNOFF

DIGIT AL Standard Runoff

VAX DIGITAL Standard
Runoff Reference Manual

SDA

System Dump Analyzer

VMS System Dump
Analyzer Utility Manual

SEARCH Command

VMS DCL Dictionary

SET

SET Command

VMS DCL Dictionary

SHOW

SHOW Command

VMS DCL Dictionary

SMB

Symbiont Services

VMS Utility Routines
Manual

SMG

VMS RTL Screen Management
(SMG$) Facility

VMS RTL Screen
Management (SMG$)
Manual

SMI

System Management lntergator
/Server

Guide to Maintaining a
VMS System

SORT

Sort/Merge Utility

VMS Sort/Merge Utility
Manual

STR

VMS RTL String Manipulation
(STR$) Facility

VMS RTL String
Manipulation (STR$)
Manual

SUBMIT

SUBMIT Command

VMS DCL Dictionary

SUM

Source Update Merge Utility

VMS SUMSLP Utility
Manual

SYSBOOT

System Bootstrap Facility

Guide to Maintaining a
VMS System

SYSGEN

System Generation Utility

VMS System Generation
Utility Manual

SYSMAN

Cluster System Management
Utility

Guide to Maintaining a
VMS System

SYSTEM

VMS System Services

VMS System Services
Reference Manual

TRACE

Traceback Facility

VMS Linker Utility
Manual

VAXCLUSTER

V AXcluster Facility

VMS VAXcluster
Manual

Preface

Table 1 (Cont.)

Facility Abbreviations

Facility
Abbreviation

Facility Name

Document

VAXport

VAX port Driver

VMS VAXcluster
Manual

VAXTPU

VAX Text Processing Utility

VAX Text Processing
Utility Manual

VERIFY

Verify Utility

VMS Analyze/Disk_
Structure Utility Manual

VMSINSTAL

VMSINST AL Procedures

VMS Developer's Guide
to VMSINSTAL

Convention

Meaning

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

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

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

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

$ TYPE MYFILE.DAT

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

input-file, ...

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

Preface

xii

Convention

Meaning

[logical-name]

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

quotation marks
apostrophes

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

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

xiii

Introduction

1 .1

Message Display
VMS provides a centralized error message facility. When you type a
command at the terminal or execute an image that results in an error, the
system locates the message associated with the error and displays it. Also,
the system sometimes generates messages when a command has completed
successfully.
Messages are displayed on the current device and are identified by the
logical name SYS$0UTPUT. For an interactive user, this device is normally a
terminal; for batch job users, it is the batch job log file. If the logical device
SYS$ERROR is different from SYS$0UTPUT, the system writes informational,
warning, error, and fatal error messages to that device as well.
For example, if you execute a command procedure interactively and
specify the /OUTPUT qualifier, the system defines the file you specified
as SYS$0UTPUT for the procedure. SYS$ERROR remains assigned to your
current error device. Then, if any errors occur during the execution of the
command procedure, the error messages are displayed on your terminal and
entered in the specified file.

1.2

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

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

•

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

•

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

•

Bits 28-31 contain internal control flags.

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

The lexical function F$MESSAGE returns the message associated with a
condition code. To display the message for the current code on the default

1-1

Introduction
1 .2 Retrieving a System Message

output device, use the following command:
$ WRITE SYS$0UTPUT F$MESSAGE($STATUS)
%SYSTEM-F-POWERFAIL, power failure occurred

Most of the messages in Chapter 2 of this manual are alphabetized by IDENT,
which is a short character string that uniquely identifies each message. If you
know the condition code for a message and you want to find its IDENT and
message text, use F$MESSAGE to translate the code to its associated message.
For example:
$ WRITE SYS$0UTPUT F$MESSAGE(%X00000001)
%SYSTEM-S-NORMAL, normal successful completion

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

1.3

Exception Conditions
During the execution of an image, the image can incur a fatal error known
as an exception condition. When an exception condition occurs, the system
takes special action.
If the image has not declared a condition handler, the system forces the image
to exit and displays a message indicating the reason for the exception. The
message includes the contents of the Program Counter (PC) and Processor
Status Longword (PSL) at the time of the exception. This message is followed
by a traceback; the system displays the status of the call frames on the stack
so that you can locate the procedure where the condition occurred. Refer to
the VMS RTL Library (LIB$) Manual for a more detailed discussion of condition
handling.

1 .4

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

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

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

Meaning

Success
Information

1-2

Warning

Error

Fatal, or severe error

Introduction
1 .4 Format of System Messages

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

1.4.1

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

System Bootstrap Utility (SYSBOOT)

•

System Initialization (SYSINIT)

•

Virtual Memory Boot (VMB)

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

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

EDT Editor

•

DIGITAL Standard Runoff

•

System Management Utility

•

VAXport

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

The entry for this message can be found under "Could" in Chapter 2 of the
VMS System Messages and Recovery Procedures Reference Manual: Part I.

1-3

Introduction
1 .4 Format of System Messages

1.4.2

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

1.4.3

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

1.5

Recovery Procedures
Error messages generally occur for the following reasons:

1-4

•

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

•

A required resource is currently unavailable.

•

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

•

A system software or hardware problem exists.

Introduction
1 .5 Recovery Procedures

1.5.1

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

1.5.2

•

A device name is not terminated with a colon.

•

A directory name is not enclosed in brackets.

•

A file name has more than 39 characters.

•

A file type has more than 39 characters.

•

An alphabetic version number is specified.

•

A node name is included and contains characters other than numerics or
alphabetics.

•

A connection to the target node could not be made.

Unavailable Resources
If the Set Resource Wait Mode ($SETRWM) system service is enabled (default

mode) and a required resource, such as dynamic memory, is unavailable, the
process is normally placed in a wait state until the resource becomes available.
However, under certain program conditions the programmer can choose to
disable the resource wait mode, so that when such a condition occurs, control
returns immediately to the calling program with an error status.
Other resources, such as files, privileges, or devices, are not subject to
resource wait mode, and their unavailability or absence always causes an
error.
How a program responds to the unavailability of a resource depends primarily
on the application and the particular service called. In some instances, the
program may be able to continue execution and retry the service later. Or, it
may be necessary only to note that the program is required to wait.

1-5

Introduction
1.5 Recovery Procedures

1.5.3

Recovering from Programming Errors
If a program image terminates abnormally, you can get some information

about the error from the message. When a program image exits, the
command interpreter uses the current value of general register zero to obtain
information about the exit status. If it is an abnormal (or error) exit, the
system message associated with the register zero value is displayed.
Programming errors are caused by the following conditions:
•

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

•

Logic errors in programming

•

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

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

1.5.4

Reporting System Software or Hardware Errors
When a message notifies you that a system software or hardware error has
occurred, action is required by the system operator or system manager.
The Introduction to VMS System Management provides information on how
to submit a Software Performance Report (SPR) to DIGITAL when you
encounter a software error. This guide also contains information on how
to run utilities that can verify that a hardware device is operational. If the
hardware device is not operational, inform the system manager.

1 .6

Examples

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

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

$ SET MESSAGE/NOIDENTIFICATION

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

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

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

1-6

Introduction
1.6 Examples

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

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

1-7

Messages

AAA,

filespec

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

string aborted
1

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

string aborted at date
1

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

string1 aborted at time
1

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

ambiguous lexical function name-supply more characters

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

ambiguous qualifier or keyword-supply more characters

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

2-1

Messages

ABKW,

ambiguous key word on line

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

abnormal exit

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

'testname' aborted at 'date' or 'time'

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

abort

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

An 1/0 request is canceled before it is completed.

•

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

•

A fatal hardware error occurred.

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

abort

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

2-2

Messages

ABORT,

operator requested abort on fatal error

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

ABORTC,

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

Facility: UETP, User Environment Test Package
Explanation: The image displaying this message responds to CTRL/C by
terminating gracefully (deassigning all logical names and deleting all files)
and passing control to the command language interpreter. You cannot restart
the image after pressing CTRL/C. Use CTRL/Y to temporarily interrupt an
image.
User Action: None.

Aborted by CTRL/C
Facility: EDT, EDT Editor
Explanation: You pressed CTRL/C after entering a command in keypad
change-mode. Pressing CTRL/C causes all text to disappear from the screen.
User Action: If the text is not restored to the screen, press RETURN.

ABPRIKW,

ambiguous primary key word on line 'line-number'

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

ABSENT,

entity or value absent from command string

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

ABSTIMREQ,

absolute time required, delta time supplied

Facility: LIB, Library Facility
Explanation: A delta time is passed to the routine when an absolute time is
required.
User Action: Examine each argument and change the delta time to an
absolute time.

2-3

Messages

ABSYMD,

abbreviated symbol definition conflict-rename symbol

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

ABVERB,

ambiguous command verb-supply more characters

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

ACC,

ACP file access failed
Facility: RMS, VMS Record Management Services
Explanation: An error occurred during an attempt to open a file. This
message is associated with a status code returned from a file system ACP QIO
request made by VMS RMS.
User Action: The status value (STV) field of the FAB contains a system status
code that provides more information about the condition. Take corrective
action based on this status code.

ACCADDCOM,

access violation in address computation for 'address-value'

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

ACCCIR,

access control specified with loop circuit

Facility: NCP, Network Control Program
Explanation: Access control with a LOOP command may be specified only
with a LOOP NODE or with a LOOP EXECUTOR command, not with a
LOOP CIRCUIT command.
User Action: Reenter the LOOP CIRCUIT command without the access
control.

ACCDISERR,

accounting disabled due to file errors

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

2-4

Messages

ACCERR,

nonblank accessibility field in volume labels on 'device-name'

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

access has failed for 'device-name'

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

access control specified with loop line

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

'filename' is open for write by another user

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

file access conflict

Facility: SYSTEM, VMS System Services
Explanation: An attempt to access a file failed because the type of access
requested conflicted with the current file access. This message is also returned
when an execute-only shareable image is referenced in the context of a main
program that is not installed with the /EXECUTE_ONLY qualifier.
User Action: Possible actions include the following:
•

Establish who opened the file and wait until it is closed.

•

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

•

Install the main program with the /EXECUTE_ONLY qualifier.

2-5

Messages

ACCOUNT,

this installation creates an account named 'account-name'

Facility: VMSINSTAL, Install Procedures
Explanation: The product being installed (or updated) has created an account
with the specified name. The user authorization file (SYSUAF) has been
updated accordingly.
User Action: None.
ACCQUOTA,

ACCOUNT had inadequate quota at remote node

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

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

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

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

•

The relatively small Pl address space virtual address is referenced.

User Action: Examine the PC and virtual address displayed in the message.
Check the program listing to verify that instruction operands or procedure call
arguments are correct.
If this message is displayed because of insufficient virtual memory for

automatic user stack expansion, reduce the user stack requirements of the
image or increase the virtual address space available to the process in which
the image is executed.
ACCVIO,

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

Facility: VAXTPU, VAX Text Processing Utility
Explanation: Internal VAXTPU failure.
User Action: Please submit a Software Performance Report.

2-6

Messages

ACPMBFAIL,

ACP failure to read mailbox

ACPNAME,

ACP file name is too long

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

ACPRECURS,

attempted recursion in ACP secondary operation

ACPSHO,

an error is returned from a NETACP SHOW function

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

ACPTIME,

ACP does not respond

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

2-7

Messages

ACPUNSTAK,

attempted unstack in ACP primary context

ACP failure to return virtual address space

MTAACP's virtual address space is full

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

error in access control string

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

access control string ignored

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

2-8

Messages

ACT,

file activity precludes operation
Facility: RMS, VMS Record Management Services
Explanation: An RMS operation is attempted while other RMS activity is in
progress. This can occur when a record or file operation is attempted while
that record stream or file has an operation in progress. It may also indicate
that a record operation was attempted while a file operation was active, or a
file operation was attempted while a record operation was active.
User Action: Correct the program logic to avoid conflicting concurrent
operations.

ACTIVE,

the following processes are still active:

Facility: VMSINSTAL, Install Procedures
Explanation: When VMSINSTAL begins an installation, it makes sure that
no user processes are active. This check has failed. VMSINSTAL lists active
processes.
User Action: The Install Utility asks you if you want to continue the
installation. DIGITAL recommends that you correct this situation before
continuing.
ACTIVEBCB,

buffer active during reel switch

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

unable to add user record

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

error adding file 'filename' to job

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

error adding file 'file-name' to job 'job-name' for user 'user-name' in
queue 'queue-name'

Facility: JBCUPGRAD, Queue Upgrade Utility
Explanation: An error occurred during a $SNDJBC system service call
attempting to add a file to the job The file was not restored to the job list
during the upgrade.
User Action: The accompanying message gives information why the
operation failed. Correct the problem and retry the upgrade, or after the
upgrade has completed, print or submit the fi]e as originally desired using the
DCL command PRINT or SUBMIT.

2-9

Messages

ADDMSG,

user record successfully added

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

ADDQUOTA,

error adding quota record for ['uic']

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

ADDRANCOV,

address range covers more than one module 'address-value' is in
'path-name' 'address-value' is in 'path-name'

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

ADJSCROLLREG,

scrolling parameters altered to top: 'top', bottom: 'bottom',
amount: 'amount'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The window you have just adjusted is not big enough to handle
the current scrolling region, so the scrolling region has been altered.
User Action: None.

ADRLSTSYNX,

address list syntax error

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

ADRWRTDAT,

address data in shareable writeable section in psect 'psect-name'
offset 'number' in module 'module-name' file 'filename'

Facility: LINK, Linker Utility
Explanation: The object language equivalent of the VAX MACRO .ADDRESS
directive is encountered in a COMMON section, such as those found in VAX
BASIC, VAX FORTRAN, or VAX PL/I. This would cause the section to be
nonshareable; so the linker bases the image.
User Action: Remove the address data from the command and initialize it at
run time.

2-10

Messages

Advance past bottom of buffer,
Facility: EDT, EDT Editor
Explanation: You attempted to move the cursor past the end of the buffer
([EOB]).
User Action: Press the up arrow key to move the cursor above the [EOB]
mark.

AGAIN,

another data analysis pass is needed

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

AID,

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

ALCPHD, allocate process header error
Facility: BUGCHECK, System Bugcheck
Explanation: The VMS software detected an irrecoverable, inconsistent
condition. After all of physical memory is written to a system dump file, the
system will automatically reboot if the BUGREBOOT system parameter is set
to 1.
User Action: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error, and that includes a BACKUP save set
containing the system dump file and the error log file active at the time of the
error. (Use the /IGNORE=NOBACKUP qualifier on the BACKUP command
that produces the save set included with the SPR.)

ALCSMBCLR,

ACP tried to allocate space already allocated

2-11

Messages

ALI,

invalid alias identification
Facility: NCP, Network Control Program
Explanation: The format of the alias indentifier is incorrect.
User Action: Check the syntax rules for alias identifiers and reenter your
command with the correct alias identifier.

ALIGNDISK,

'device-name' contains an alignment cartridge

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

ALIGNXCEED,

alignment exceeds PSECT alignment

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

ALLOC,

'device-name' allocated

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

ALLOCCLR,

blocks incorrectly marked allocated LBN 'n' to 'n', RVN 'n'

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the specified logical blocks on the
specified relative volume were marked allocated in the storage bit map but
were not allocated to a file.
User Action: None. The specified blocks were marked free in the storage bit
map. The /CONFIRM qualifier is ignored in this operation.

ALLOCEXT,

blocks allocated to lost extension file header LBN 'n' to 'n', RVN 'n'

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the specified logical blocks on the
specified relative volume were allocated to a lost extension file header. The
specified blocks were marked free in the storage bit map. The /CONFIRM
qualifier is ignored in this action.
User Action: None.

2-12

Messages

ALLOCFAIL,

file structure allocation failure for 1device-name 1

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

index file allocation failure

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

error allocating virtual memory

Facility: BACKUP, Backup Utility and VERIFY, Verify Utility
Explanation: Either the Backup Utility or the Verify Utility encountered
an error during an attempt to allocate dynamic virtual memory. The
accompanying message provides additional information.
User Action: Correct the condition that caused the error and reenter the
command. You may need to increase the page file quota of the account or the
SYSGEN parameter VIRTUALP AGECNT.
ALLOCMEM,

error allocating virtual memory

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

blocks incorrectly marked free LBN n' to n RVN n
1

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the specified logical blocks on the
specified relative volume were marked free in the storage bit map but were
allocated to a file.The specified blocks are marked allocated in the storage bit
map. The /CONFIRM qualifier is ignored in this action.
User Action: None.
ALN,

alignment options error for area id= nnn

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

2-13

Messages

ALPBFOVF,

active looper buffer exceeded

Facility: MOM, Maintenance Operation Module
Explanation: An attempt to allocate a buffer to be used for a LOOP
CIRCUIT command has failed. This may be because virtual memory has
been exhausted.
User Action: Take steps to increase the amount of virtual memory available
for the process.

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

ALREDEF,

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

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

ALTIHDBAD,

invalid alternate index file header, RVN 'n'

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

AMBCMD,

ambiguous command

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

AMBDATTIM, ambiguous date-time
Facility: LIB, Library Facility
Explanation: The date-time input string did not match the specified input
format.
User Action: Examine the date-time input string and input format.

2-14

Messages

AMBIG,

ambiguous field name or class name 'class-name'

Facility: SHOW CLUSTER, Show Cluster Utility
Explanation: The field or class name entered is not unique.
User Action: Reenter the field or class name with additional characters
or enter the HELP FIELDS or HELP CLASSES commands to get a list of
available fields or classes.

AMBIGNAME,

variable 'name' cannot be a procedure

Facility: VAXTPU, VAX Text Processing Utility
Explanation: You previously used an identifier as a variable; you are now
attempting to use the same identifier as a procedure.
User Action: Use a different name for the procedure.

AMBIGSYMUSED,

ambiguous symbol 'name' used as procedure parameter

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The named symbol could be either an undefined procedure or a
variable; its correct usage has not yet been determined. When an ambiguous
symbol is used as a parameter in a call, the compiler is forced to generate
nonoptimal code.
User Action: Define the named symbol as either a procedure or a variable
before using it as a call parameter.

AMBKEY,

'keyword' is an ambiguous keyword

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

AMBSYMDEF,

ambiguous symbol definition

Facility: LIB, Library Facility
Explanation: The specified symbol name is ambiguous when compared with
existing symbol names. This condition can occur when abbreviated symbols
have been previously defined.
User Action: Refer to the VMS DCL Dictionary for more information about
abbreviated symbols.

2-15

Messages

not ANSI D format
11

ANI,

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

allocation options error for area id= 'nnn'
Facility: RMS, VMS Record Management Services

Explanation: An allocation XAB for a $CREATE or $EXTEND operation
specifies an invalid allocation option (AOP field).
User Action: The status value (STY) field of the FAB provides the area
identification of the XAB in error. Verify that the call to the VMS RMS service
is coded correctly.
APPENDEDB,

'input-filespec' appended to 'output-filespec' (nnn blocks)

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

inconsistent active page table reference count

active page table swap write error

2-16

Messages

AQBTIME,

ACP queue is unstable

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

ARGMISMATCH,

parameter 'numbers', 'data-type', and 'type' are unsupported

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The data type of the indicated parameter is not supported by
the built-in procedure that is being called.
User Action: To find the correct data types for this built-in procedure, refer
to the VAX Text Processing Utility Manual or to online help.

ARGREQ,

missing argument-supply all required arguments

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

ARGTOOLONG,

argument too long

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

ARTRES,

reserved arithmetic trap at PC location, PSL = xxxxxxxx

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

'AS' required,
Facility: EDT, EDT Editor
Explanation: You omitted the word as from the syntax in the DEFINE KEY
command.
User Action: Reenter the command specifying the correct syntax.

ASCTOOLONG,

ASCII string too long

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

2-17

Messages

ASGNMNTSYN,

assignment syntax error

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

could not assign logical queue 'queue-name' to execution queue
'queue-name'

Facility: JBCUPGRAD, Queue Upgrade Utility
Explanation: An error occurred during a $SNDJBC system service call
attempting to assign the queue to another executor queue. This error changes
the first queue into a logical queue.
User Action: The accompanying message gives information about why the
operation failed. Correct the problem and retry the upgrade, or after the
upgrade has completed, assign the logical queue to the execution queue using
the DCL command ASSIGN.
ASSIGN,

error assigning channel to 'device-name'

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

error assigning channel to 'device-name'

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

could not assign 'device' as system disk

Facility: BACKUP, Backup Utility
Explanation: Standalone BACKUP could not assign a channel to the disk
from which it was booted.
User Action: Determine why the channel assign failed. If possible, correct
the problem and retry the BACKUP operation. Otherwise, submit a Software
Performance Report including full configuration details and a log of the
output.

2-18

Messages

ASTFLT,

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

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

journal file prohibited with asynchronous handlers declared

Facility: VAXTPU, VAX Text Processing Utility
Explanation: Creating a journal file is prohibited. Asynchronous action
routine handlers have been declared.
User Action: You must choose between journaling and action routines.
ASYNCWRTER,

asynchronous write memory failure

at line 'integer'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: This message indicates the line number of the error.
User Action: None.
ATPC, at PC = 'xxxxxxxx'
Facility: Shared by several facilities
Explanation: This message generally accompanies a message indicating a
software failure.
User Action: Take corrective action based on the accompanying messages.
ATPROCLINE,

at line 'integer' of procedure 'name'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: Line number of error in the procedure.
User Action: None.

2-19

Messages

ATR,

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

ATTACHED,

terminal now attached to process 'process-name'

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

attempt to continue from stop

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

2-20

Messages

ATTREQREF,

attach request refused

Facility: DEBUG, VMS Debugger
Explanation: The specified process could not be attached to. Either it is not
detached or it did not belong to the caller's job.
User Action: Ensure that the specified process is detached and belongs to the
caller's job.
ATTREQREF,

attach request refused

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

file attributes write error

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

auto-answer file is not synchronized to the current question

Facility: VMSINSTAL, Install Procedures
Explanation: You have specified the auto-answer option, and VMSINSTAL is
using the answers from an existing answer file. The question being asked by
the installation procedure does not match the next question and answer in the
answer file.
User Action: The installation procedure has changed. Delete the existing
answer file and begin the installation again.
BACKLINK,

incorrect directory back link 'filespec'

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the back link of the specified file
did not contain the file identification of the directory file in which the file is
cataloged. This condition is normal if the file is cataloged in more than one
directory.
User Action: Set the back link pointer to point to the directory file. If the file
is cataloged in more than one directory, you may want to use the /CONFIRM
qualifier to direct the Verify Utility not to repair the back link.

2-21

Messages

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

an error has occurred in recreating the save set

Facility: VMSINSTAL, Install Procedures
Explanation: A BACKUP error occurred while re-creating the save sets in the
processing of the GET option. The operation is aborted.
User Action: Make sure the specified output device holds media that is not
write protected.
BADACC,

unable to CREATE/UPDATE account named 11 name 11 •

Facility: VMSINSTAL, Install Procedures
Explanation: The product being installed has tried to either create an account
that already exists or modify a nonexistent account.
User Action: If you can determine and resolve the problem, reinstall the
product. Otherwise, contact your DIGITAL field service representative.
BADACP,

invalid syntax on /PROCESSOR qualifier

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

remote access control info invalid

Facility: SMI, System Management Intergator/Server
Explanation: The SYSMAN user cannot be validated on the indicated node
due to one or more of the following reasons:
•

The password is invalid.

•

The user name (current or as overidden with a /USERNAME qualifer)
cannot be found in the remote system UAF.

•

The remote system UAF cannot be accessed.

•

The remote UAF record does not have either SETPRV or OPER privileges
authorized.

•

The account is disabled.

User Action: Determine why the account is invalid on the remote system by
trying to log in directly with a DCL SET HOST command.

2-22

Messages

BADALORQSZ, bad memory allocation request size
Facility: BUGCHECK, System Bugcheck
Explanation: The VMS software detected an irrecoverable, inconsistent
condition. After all of physical memory is written to a system dump file, the
system will automatically reboot if the BUGREBOOT system parameter is set
to 1.
User Action: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error, and that includes a BACKUP save set
containing the system dump file and the error log file active at the time of the
error. (Use the /IGNORE=NOBACKUP qualifier on the BACKUP command
that produces the save set included with the SPR.)
BADARGS,

unrecognized argument to procedure

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

target of the assignment cannot be a function/keyword

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The left-hand side of an assignment statement must be a
variable. It cannot be a procedure name or a keyword.
User Action: Use a different variable name to the left of the operator: =in
this assignment statement.
BADATTRIB, bad attribute control list
Facility: SYSTEM, VMS System Services
Explanation: An invalid code or size is specified in the read or write attribute
list for a file system ACP QIO function.
User Action: Check for a programming error. Begin debugging procedures to
verify the source of the problem and to correct the problem. Note that when
using ANSI magnetic tapes, the block size must be 4 bytes larger than the
largest record in a variable record length file, and the largest record that can
be written is 2048 bytes.
BADBITMAP,

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

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

2-23

Messages

BADBLK,

invalid option block

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

'save-set-spec' has inconsistent block size

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

bad block address

Facility: LIB, Library Facility
Explanation: The library routine LIB$FREE_VM is called with an invalid
virtual storage address.
User Action: Begin debugging procedures to verify the problem and to
correct the problem.
BADBLOCK, bad blocks on 'device-name' do not match input
Facility: BACKUP, Backup Utility
Explanation: In a COPY or RESTORE operation with the /PHYSICAL
qualifier, a bad block is present on the output volume in a location where the
input volume had a good block. The backup operation will not result in a
valid Files-11 volume.
User Action: Reevaluate the operation; another mode of operation, such
as the /IMAGE qualifier, may be appropriate. Or retry the operation using
either the original input volume or an error-free output volume.
BADBLOCKS, invalid syntax in bad block list
Facility: INIT, INITIALIZE Command
Explanation: The command syntax for the /BAD_BLOCKS qualifier is
invalid.
User Action: Reenter the command; use the DCL command HELP or refer
to the VMS DCL Dictionary for the correct syntax. If the list of blocks is long,
place the command in a command procedure file.

2-24

Messages

BADBLOSIZ, bad block size
Facility: LIB, Library Facility
Explanation: Either the library routine LIB$GET_VM is called with a request
for zero blocks or the requested block size is too large.
User Action: If the requested block size is zero, correct the source program. If
the specified block size is too large, use the DCL command SET WORKING_
SET to increase the current working set limit for your process and retry the
program.
BADBOOTCB,

corrupted Boot Control Block

ACP buffer address out of range of buffer pool

Facility: BUGCHECK, System Bugcheck
Explanation: The VMS software detected an irrecoverable, inconsistent
condition. After all physical memory is written to a system dump file, the
system will automatically reboot if the BUGREBOOT system parameter is set
to 1.
User Action: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error, and that includes a BACKUP save set
containing the system dump file and the error log file active at the time of the
error. (Use the /IGNORE=NOBACKUP qualifier on the BACKUP command
that produces the save set included with the SPR.)
BADBUFTYP, bad ACP buffer type code
Facility: BUGCHECK, System Bugcheck
Explanation: The VMS software detected an irrecoverable, inconsistent
condition. After all physical memory is written to a system dump file, the
system will automatically reboot if the BUGREBOOT system parameter is set
to 1.
User Action: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error, and that includes a BACKUP save set
containing the system dump file and the error log file active at the time of the
error. (Use the /IGNORE=NOBACKUP qualifier on the BACKUP command
that produces the save set included with the SPR.)

2-25

Messages

BADBUFWRITE,

error occurred writing buffer 'buffer name'

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

please report TRACE bug no. 'nnn'

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

invalid data 'xx' at 'location'

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

invalid syntax on /CACHE qualifier

Facility: MOUNT, Mount Utility
Explanation: The options given with the /CACHE qualifier have invalid
syntax.
User Action: Verify the command and reenter the correct syntax.
BADCASE, unrecognized CASE constant
Facility: VAXTPU, VAX Text Processing Utility
Explanation: Case constants can only be integers, keywords, or I-character
strings.
User Action: Check your case labels or your FROM ... TO limits to ensure
that the case constants follow the stated rules.
BADCASELIMIT,

CASE constant outside of CASE limits

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

2-26

Messages

BADCASERANGE,

invalid CASE range

Facility: VAXTPU, VAX Text Processing Utility
Explanation: Either the case range or at least one case selector other than
INRANGE or OUTRANGE must be specified.
User Action: Specify a case range or specify at least one case selector other
than INRANGE or OUTRANGE.

BADCCC,

bad compilation completion code ('decimal-number') in module
'module-name' file 'filename'

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

BADCCC,

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

BADCHAR,

unrecognized character in input

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

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

BADCHKSUM, shared memory data structures corrupted-reinitialization
necessary
Facility: SYSGEN, System Generation Utility
Explanation: A CRC check of the constant fields in the shared memory
datapage has detected an error.
_User Action: Reboot all processors using the shared memory.

2-27

Messages

BADCONDEV,

please specify an existing console device.

Facility: VMSINSTAL, Install Procedures
Explanation: The device you specified is not a console device.
User Action: Specify a valid console device.
BADCOPIES,

'nnn' is an invalid number of copies

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

scope setting not module or routine

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

bad control character enable/disable mask

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

bad memory deallocation request size or address

error in block 'nn' of 'filespec' detected during save

Facility: BACKUP, Backup Utility
Explanation: A read error for the specified block of the specified file occurred
when the save set is created. Data in this block may be corrupted.
User Action: Examine the file for corruption and reconstruct as necessary. If
this error occurs during a disk-to-disk (copy) operation, it indicates a software
error in the Backup Utility. In this case, submit a Software Performance
Report.

2-28

Messages

BADDATCHK,

invalid keyword on /DATACHECK qualifier

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

BADDATDAT,

data echoed invalid

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

BADDATLEN,

not enough data sent/received

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

BADDELETE,

cannot modify constant integer, keyword or string

Facility: VAXTPU, VAX Text Processing Utility
Explanation: You are attempting to modify an integer, keyword, or string
constant.
User Action: Check your program for this error and remove the problem
statement.

BADDELIM,

invalid delimiter following 'command'

Facility: Shared by several facilities
Explanation: An invalid character was entered as part of a command. This
message displays the rejected portion of the command.
User Action: Check the command for a spelling or syntax error; reenter the
command.

BADDENS,

unknown value on /DENSITY qualifier

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

BADDIR, bad directory spec-should be dev:[dir]
Facility: SMI, System Management Intergator /Server
Explanation: A SYSMAN SET PROFILE/DEFAULT command specified an
invalid device or directory, or both.
User Action: Correct the directory specification according to the VMS DCL

Concepts Manual.
2-29

Messages

BADDIR,

directory 'directory' has invalid format

Facility: BACKUP, Backup Utility and VERIFY, Verify Utility
Explanation: The specified directory file is not in the expected format for a
directory file. The file is corrupted.
User Action: Use the DCL command SET FILE/NODIRECTORY to delete
the corrupted directory file. Then use the DCL command ANALYZE/DISK_
STRUCTURE /REPAIR to place the lost files in the [SYSLOST] directory. You
can then copy the lost files to a new directory.

BADDIRENT,

invalid file identification in directory entry 'filespec'

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

BADDISDEV,

please specify a disk or tape device

Facility: VMSINSTAL, Install Procedures
Explanation: You specified a device on which the distribution media is to be
mounted that is neither a disk nor a tape.
User Action: Specify a disk or tape device.

BADDISDIR,

directory "directory-name" does not exist

Facility: VMSINSTAL, Install Procedures
Explanation: You are trying to restore the distribution kit from a nonexistent
directory.
User Action: Specify the correct directory when you start VMSINSTAL.

BADDST,

no symbols in image

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

BADDSTMAP,

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

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

2-30

Messages

BADDSTVBN,

image symbol table VBN = 'nnn'

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

BADECO, illegal eco level of 'nn' in 'filespec'
Facility: PATCH, Patch Utility
Explanation: An illegal ECO level is specified. The legal ECO level range is
between 1 and 128, inclusive.
User Action: Retry using a legal ECO level.

BADEFBLK, file ('file-id') 'filename' inconsistent EFBLK and map area
Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the end-of-file pointer recorded
in the VMS RMS record attributes for the specified file did not lie within the
space actually allocated to the file.
User Action: None. The end of file pointer is set to point to the end of the
allocated space.

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

BADESCAPE,

syntax error in escape sequence

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

BADEVTYP, bad device type, 'value' in text library module, 'module-name'
Facility: ERF, Error Log Utility
Explanation: A value in the specified library module is out of the required
range.
User Action: Submit a Software Performance Report.

2-31

Messages

BADEVVAL, bad device table value, 'value' in text library module, 'module-name'
Facility: ERF, Error Log Utility
Explanation: A value in the specified library module is out of the required
range.
User Action: Submit a Software Performance Report.
BADEXCL,

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

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

invalid filename in /EXCLUDE = exclude-item

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

failure to open image file 'filename'

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

failure to close image file 'filename'

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

failure to connect image file 'filename'

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

2-32

Messages

BADEXH,

the user-mode exit handler list is corrupt

Facility: DEBUG, VMS Debugger
Explanation: While waking the list of user-mode exit handlers, the debugger
detected a forward link that pointed to an inaccessible exit control block.
User Action: Check for a call to the SYS$DCLEXH system service that
specifies an illegal exit control block argument. Also verify that exit control
blocks are not getting corrupted later in the program.
BADEXITIF,

EXITIF occurs outside of a LOOP

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

ACP file number out of range for this volume

'name' field invalid at 'location'

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

invalid startup file name

Facility: START, System Startup Driver
Explanation: The named startup component file name is invalid. The specific
reason for the error is printed before this message.
User Action: Use the STARTUP MODIFY FILE command at the SYSMAN>
prompt to correct the file name.
BADFILEHDR, bad file header
Facility: SYSTEM, VMS System Services
Explanation: The file header has failed validity checks and is corrupted.
User Action: Repair the volume with the Verify Utility and recover the file
from back-up media.

2-33

Messages

BADFILENAME,

bad file name syntax

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

BADFILENAME,

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

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility is given a file name that is not in the
correct format for the target volume type.
User Action: Reenter the command, using a valid file name for the volume
shown in the message.

BADFILEVER,

bad file version number

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

BADFIRSTLINE,

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

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

BAD_FJXUPVEC, the fixup vector contains inconsistent data
Facility: IMGACT, Image Activator
Explanation: There are inconsistencies in the structure of the fixup vector in
the image. This usually indicates a corrupted or invalid image.
User Action: Relink the image.

BADFLAG,

bad enable/disable flag

Facility: START, System Startup Driver
Explanation: The enable/ disable flag describing how the list of nodes
associated with a startup component file should be used is invalid.
User Action: Use the SYSMAN command STARTUP ENABLE/DISABLE to
modify this entry in the startup component file.

2-34

Messages

BADFORKIPL,

bad FORK exit interrupt priority level

'form-type' is an invalid form type

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

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

invalid option for /FORMAT = 'format-option'

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

bad FP or bad saved FP at 'pointer-addr' in call stack, cannot read
frame near 'frame-addr'

Facility: DEBUG, VMS Debugger
Explanation: The debugger is trying to chain down the call stack, following
frame pointers. The FP register (if 'pointer-addr' is "FFFFFFFF") or the saved
frame pointer at location 'pointer-addr points to a frame at least part of which
is not read accessible near the location of 'frame-addr'.
1

User Action: Determine what part of your code is writing into the FP register
or overwriting the saved frame pointer on the call stack (or a preceding saved
frame pointer) and correct it. Since the debugger looks at the call stack to
symbolize addresses, you may suppress some of these messages by typing the
command SET MODE NOSYMBOLIC.
BADFRMT,

volume is not mounted with Files-11 format

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

2-35

Messages

BADFUNC,

invalid function type received

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

directory 'directory-name' does not exist.

Facility: VMSINSTAL, Install Procedures
Explanation: You are trying to copy the specified product save set to a
nonexistent directory.
User Action: Specify the correct directory when you start VMSINSTAL.
BADGSD, unknown type of GSD entry: 'GSD'
Facility: SDA, System Dump Analyzer
Explanation: SDA encountered a type of global symbol that it does not
recognize, either in the SYS.SIB file or in a file specified in the SDA
command READ. The type of global symbol definition GSD is represented by
a byte.
User Action: This message can occur during either initialization or operation
of the SDA and usually means that the file being read has been corrupted.
Check the integrity of the symbol table file.
BADHDR,

an error is discovered in the image header

Facility: IMGACT, Image Activator
Explanation: The image header type word contains an invalid type code.
This usually indicates a corrupted or invalid image.
User Action: Relink the image.
BADHDR, no symbol table data in image header
Facility: TRACE, Traceback Facility
Explanation: The image header in the executable image file does not contain
expected symbol table data. This message indicates an internal operating
system error.
User Action: Collect as much information as possible and submit a Software
Performance Report.
BADHEADER, file ('file-id') 'filename' invalid file header
Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the specified file header is corrupt.
User Action: None. The file is rewritten with a deleted file header. If the
specified file header is currently in use, the file can no longer be accessed by
the operating system and must be reconstructed from backup media. If the
file header is not in use, no action is necessary.

2-36

Messages

BADHIBLK,

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

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the file size recorded in the VMS
RMS record attributes did not agree with the number of blocks actually
allocated to the file.
User Action: None. The record attributes are corrected by changing the file
size to reflect the correct number of blocks.
BADHOMBLK, bad home block encountered on volume
Facility: MOUNT, Mount Utility
Explanation: An I/O error occurred while reading a home block during
/BIND processing. A subsequent message explains the nature of the error.
The first occurrence of this message is a warning; the second is fatal.
User Action: Repair with the Verify Utility or reinitialize the volume and
retry the operation.
BADIDENT, unable to patch image with ident of 'nn'
Facility: PATCH, Patch Utility
Explanation: PATCH does not recognize this version of the image file.
User Action: Relink your image file. Ensure that the file being patched is a
native mode image file.
BADIF,

IF statement contains an assignment statement

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The IF expression in an IF ... THEN statement must contain
logical operators only. This message is likely to occur if you used the
expression x: = y instead of the the Boolean expression x = y. The IF
expression in an IF ... THEN statement makes a logical comparison.
User Action: Change the operator: =to the operator=.
BADIMGHDR, bad image header
Facility: SYSTEM, VMS System Services
Explanation: An image to be executed with the DCL command RUN or
within a process is not in the correct format and cannot be executed.
User Action: Verify that the specified file is an executable image. If
necessary, recompile or reassemble and relink the program to ensure that
the image file is in the proper format.
BADIMGHDR, bad image header in shareable image file 'filename'
Facility: LINK, Linker Utility
Explanation: A shareable image contains a bad image header, or the file is
not a shareable image.
User Action: Correct and relink.

2-37

Messages

BADINDEX,

invalid syntax on /INDEX qualifier

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

BADINITSZ,

illegal size value defaulting patch size to 'xxxxxxxx' bytes

Facility: PATCH, Patch Utility
Explanation: The size-expression input argument did not fall within the valid
range. PATCH set the patch area to the address named in the SET PATCH_
AREA command, and use the default patch area size to build the patch area
descriptor.
User Action: Continue to enter patches into the user-defined patch area. To
see the current status of the patch area, enter the SHOW P ATCH__AREA
command.

BADIONAME,

'name' has not been previously defined

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

BADIRECTORY,

bad directory file format

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

BADISD,

illegal image section descriptor

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

BADJOBID,

'job-id' is a bad job identifier

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

2-38

Messages

BADJOBNAME,

'job-name' is an invalid job name

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

expected character in journal file

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

journaled command file is 'filename', recovering with 'filename'

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

journaled starting character was 'character number', recovering
with 'original character number'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The editing session is being recovered with a different starting
character number than was used during the original editing session.
User Action: Stop the recovery session, and restart it using the original
starting character number.
BADJOUEDIT,

journaled edit mode was 'mode-setting', recovering with 'original
mode-setting'

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

journaled eightbit was 'eightbit setting', recovering with 'original
eightbit setting'

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

2-39

Messages

BADJOUFILE,

operation terminated due to error in journal file access

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The journal file operation stopped because the journal file could
not be accessed.
User Action: Correct the problem preventing access to the journal file and
try again.

BADJOUINIT,

journaled init file was 'init-filename', recovering with 'original-initfilename'

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

BADJOUINPUT, journaled input file was 'input-filename', recovering with
'original-input-filename'
Facility: VAXTPU, VAX Text Processing Utility
Explanation: The editing session is being recovered with a different input file
than was used during the original editing session.
User Action: Stop the recovery session, and restart it using the original input
file.

BADJOUKEY,

expected key in journal file

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

BADJOULINE,

journaled with line editing 'string', recovering with line editing
'string'

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

BADJOULPOS,

journaled starting line was 'line-number', recovering with
'original-line-number'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The editing session is being recovered with a different starting
line number than was used during the original editing session.
User Action: Stop the recovery session, and restart it using the original
starting line number.

2-40

Messages

BADJOUPAGE,

journaled page length is 'integer', recovering with page length
'integer'

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

BADJOUSEC,

journaled section is 'string', recovering with 'string'

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

BADJOUSTR,

expected string in journal file

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

BADJOUTERM,

journaled terminal type was 'string', recovering with a 'string'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The editing session is being recovered with a terminal different
from that used in the original editing session. This might result in journal file
inconsistencies.
User Action: Stop the recovery session and reset the terminal characteristics
to those used in the original editing session.

BADJOUWIDTH,

journaled width is 'integer', recovering with width 'integer'

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

BADJRNL, invalid syntax on /JOURNAL qualifier
Facility: MOUNT, Mount Utility
Explanation: You have entered the wrong command line syntax.
User Action: Correct the syntax and reenter.

2-41

Messages

BADKEY,

'keyword' is an invalid keyword

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

'keyword' is an invalid keyword

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

illegal key

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

invalid key specification

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

invalid keyword on /LABEL qualifier

Facility: INIT, INITIALIZE Command
Explanation: An invalid keyword is specified with the /LABEL qualifier. The
only keyword compatible with the /LABEL qualifier is shown as follows:
/LABEL=VOLUME _ACCESSIBILITY:" single-character"

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

2-42

Messages

BADLCKWSLE, bad locked working set list entry, not a page table
Facility: BUGCHECK, System Bugcheck
Explanation: The VMS software detected an irrecoverable, inconsistent
condition. After all of physical memory is written to a system dump file, the
system will automatically reboot if the BUGREBOOT system parameter is set
to 1.
User Action: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error, and that includes a BACKUP save set
containing the system dump file and the error log file active at the time of the
error. (Use the /IGNORE=NOBACKUP qualifier on the BACKUP command
that produces the save set included with the SPR.)
BADLEXARG,

illegal lexical function argument

Facility: MACRO, VAX MACRO Assembler
Explanation: The argument to a macro string operator is invalid. String
arguments can be macro arguments or strings delimited by angle brackets
or the circumflex delimiters. Symbol arguments can be absolute symbols or
decimal integers.
User Action: Correct the argument syntax.
BADLEXFORM, illegal format for lexical function
Facility: MACRO, VAX MACRO Assembler
Explanation: The macro string operator contained a syntax error.
User Action: Correct the macro string operator syntax.
BADLOGIC,

internal logic error detected [at PC location]

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

internal logic error detected, please report error 'errorcode'

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

2-43

Messages

BADLOGICPC,

internal logic error detected at PC = location

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

invalid data 'xxxxxxxx' at 'location'

Facility: Shared by several facilities
Explanation: The specified data is invalid at the given location.
User Action: None.
BAD_LRL, record length n greater than specified longest record length

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

margins specified incorrectly

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

invalid option for /MATCH= match-option

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

2-44

Messages

BADMCKCOD,

bad machine check code

invalid mode for startup file

Facility: START, System Startup Driver
Explanation: A startup component file in the startup component database
has an execution mode that is not DIRECT, BATCH, CALLED, SPAWN, or
ANY.
User Action: To correct the component execution mode, use the STARTUP
MODIFY FILE command at the SYSMAN> prompt.
BADMODNAM,

bad module name key 'key-name'

Facility: ERF, Error Log Utility
Explanation: The specified library module was not found.
User Action: Submit a Software Performance Report.
BADMOPFCT,

bad MOP function received from target

Facility: MOM, Maintenance Operation Module
Explanation: A MOP message is rejected because the MOP Code field
contains an invalid value.
User Action: Correct the MOP Code field in the device transmitting the MOP
message.
BADMOPPGM ,

bad MOP program type received from target

Facility: MOM, Maintenance Operation Module
Explanation: A MOP message is rejected because the MOP Program Type
field contains an invalid value.
User Action: Correct the MOP Program Type field in the device transmitting
the MOP message.
BADMOPPROC,

bad MOP processor type received from target

Facility: MOM, Maintenance Operation Module
Explanation: A MOP message is rejected because the MOP Processor field
contains an invalid value.
User Action: Correct the MOP Processor field in the device transmitting the
MOP message.

2-45

Messages

BADMOPSID , bad MOP software ID received from target
Facility: MOM, Maintenance Operation Module
Explanation: A MOP message is rejected because the MOP Software ID field
contains an invalid value.
User Action: Correct the MOP Software ID field in the device transmitting
the MOP message.
BADMOPVER , incompatible MOP version
Facility: MOM, Maintenance Operation Module
Explanation: A MOP message is rejected because the MOP Format Version
field contains an invalid value.
User Action: Correct the MOP Format VBersion field in the device
transmitting the MOP message.
BADMSG,

invalid management message

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

unknown sub-message type

Facility: REM, Set Host Facility
Explanation: This message indicates an internal software error.
User Action: Submit a Software Performance Report.
BADNODFORM,

improper node::remoteuser format

Facility: AUTHORIZE, Authorize Utility
Explanation: You specified the format for the remote node and user
incorrectly. The correct format consists of a node name, a pair of colons
( :: ), and the user name of the remote user. A node name may consist of
one to six alphanumeric characters and must contain at least one alphabetic
character. If you use a wildcard character for either the node or user, you
must still include the pair of colons.
User Action: Reenter your command with the correct format.
BADOFFSET,

image header offset is invalid

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

2-46

Messages

BADOPCODE,

opcode 'opcode-name' is unknown

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

opcode 'xx' is unrecognized

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

unable to locate BOOT file

Facility: VAXCLUSTER, VAXcluster Facility
Explanation: SYS BOOT .EXE is not found or is not accessible in the specified
satellite system root directory.
User Action: Check the satellite system root for the file and verify that it has
the proper protection.
BAD_ORDER,

merge input is out of order

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

invalid out of band AST specification

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

unknown keyword on /OVERRIDE qualifier

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

2-47

Messages

BADPAD,

bad format for PAD keyword on /RECORD_FORMAT qualifier

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

bad page file address allocated

bad page file address deallocated

bad page type

2-48

Messages

BADP ARAM,

unable to find load assist parameter

Facility: VAXCLUSTER, VAXcluster Facility
Explanation: Parameters defined in the MOP downline load database or the
satellite's SYSGEN parameter file, VAXVMSSYS.PAR, were not set properly.
User Action: Check the MOP database using the NCP command SHOW
NODE 'node-name' CHAR and check the SYSGEN parameters for the
satellite with the SYSGEN command SHOW/CLUSTER.
BADP ARAM,

bad parameter

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

bad parameter value

Facility: DEBUG, VMS Debugger
Explanation: This message indicates an internal debugger error.
User Action: Submit a Software Performance Report.
BADP ARAM, bad parameter value
Facility: SYSTEM, VMS System Services
Explanation: A value specified for a system function is not valid. Several
conditions can cause this error:
1

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

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

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

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

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

If this message is associated with a status code returned by a request to
a DMP11 interface, the parameter code that is rejected is given in the
second longword of the IOSB. The parameter could have been rejected
for one of the following reasons: (a) the parameter is not recognized, (b)
the parameter value is not legal, or (c) the state is inconsistent with the
parameter value requested.

If this message is associated with turning on fallback, fallback may not be
loaded or the virtual terminal may be disconnected. Reconnect the virtual
terminal and enter the request again. If the FB driver is not loaded, ask
your system manager to enable fallback.

2-49

Messages

User Action: Using the debugger if necessary, determine the system service
call that returned the error. Verify that the call to the service is coded
correctly. Refer to the VMS System Services Reference Manual for coding
specifications.

BADP ARAM,

improperly coded NML parameter

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

BADP ARAM,

insufficient shared memory to create specified data structures

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

BADP ARSETBL, internal error-invalid parsing table detected
Facility: MOM, Maintenance Operation Module
Explanation: An internal table is invalid. This is a program logic error and
should be reported.
User Action: Submit a Software Performance Report.

BADPAT,

invalid data pattern received

Facility: DTR, DECnet Test Program Protocol
Explanation: This message indicates a test error.
User Action: Retry the test and submit a Software Performance Report.

BADPKT,

internal error-Remote packet format bad

Facility: SMI, System Management Intergator/Server
Explanation: The packet received by SMISERVER is invalid for one of the
following reasons:

•

The packet format is too short.

•

The object or function code is out of range.

•

The originator PID is zero.

User Action: Submit a Software Performance Report showing all SYSMAN
commands leading to this error.

BADPNAME,

illegal parameter name, must be Pl through P8

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

2-50

Messages

BADPRO,

invalid syntax on /PROTECTION qualifier

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

no such process

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

variable used as a procedure

Facility: VAXTPU, VAX Text Processing Utility
Explanation: A variable name is being used in a PROCEDURE statement or
is being used as the name of a procedure being called.
User Action: Change the name of the procedure.
BADPROG, procedure definitions must precede statements in a program
Facility: VAXTPU, VAX Text Processing Utility
Explanation: In a VAXTPU program, all procedure definitions must precede
the executable program statements.
User Action: Reorder your program so that all procedure definitions appear
before the executable statements.
BADPROGDELETE,

cannot delete current program

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

Prompt area length= 'integer', must be between 'integer' and
'integer'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The length argument you specified to the SET PROMPT_AREA
built-in goes beyond the screen's physical limits.
User Action: Use valid arguments and reenter the command.
BADPRTY,

'priority' is an invalid priority

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

2-51

Messages

BADPSC,

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

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

invalid disk quota file format

Facility: SYSTEM, VMS System Services
Explanation: The quota file has an invalid format.
User Action: Delete and re-create the quota file [O,O]QUOTA.SYS with the
Diskquota Utility.
BADQHDR,

interlocked queue header corrupted

'queue-name' is an invalid queue name

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

qualifier /qualifier' is inconsistent with the operation type

Facility: BACKUP, Backup Utility
Explanation: The specified qualifier cannot be used with the type of BACKUP
operation indicated by the BACKUP command.
User Action: Reenter the BACKUP command without the specified qualifier
or select a different operation type. For more information on how qualifiers
affect the BACKUP command, see the VMS Backup Utility Manual.
BADQUEUEHDR, interlocked queue corrupted
Facility: SYSTEM, VMS System Services
Explanation: An interlocked queue is corrupted. If this message is associated
with a status code returned by a request to a DR32 interface, an INPTQ or
TERMQ interlock timeout has occurred.
User Action: Determine why the queue became corrupted and correct the
problem.

2-52

Messages

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

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

BADRCT,

Replacement and Caching Table unrecoverable I/O error

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

BADREAD,

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

Facility: VAXTPU, VAX Text Processing Utility
Explanation: This message indicates an internal VAXTPU failure.
User Action: Submit a Software Performance Report.

BADREPLY, unknown type of operator reply, reply is 'reply'
Facility: BACKUP, Backup Utility
Explanation: The operator's reply indicated in the message is an unknown
type and cannot be processed.
User Action: See the operator or your system manager for an indication of
the problem.

BADREPLY, unknown type of operator reply, reply= 'text'
Facility: MOUNT, Mount Utility
Explanation: An error has occurred in OPCOM.
User Action: Retry the MOUNT request.

2-53

Messages

BADREQUEST,

request 'name' is not understood

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

BADRETURN,

RETURN occurs outside of a procedure

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

BADRSEIPL,

bad IPL at entrance to report schedule event

BADRVNWCB,

inconsistent RVN in window map pointer

2-54

Messages

BADSBMBLK,

ACP tried to reference off end of bitmap

invalid path name 'path-name', SCOPE not changed

Facility: DEBUG, VMS Debugger
Explanation: The scope 'path-name' specified in the SET SCOPE command
contained a path name that does not exist.
User Action: Specify a valid scope.
BADSECTION,

bad section file

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The section file is invalid.
User Action: Use a valid section file.
BADSEQNUM,

invalid data sequence received

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

attempt to set process affinity to primary CPU failed

Facility: SYSGEN, System Generation Utility
Explanation: SYSGEN cannot set process affinity to the primary CPU.
User Action: Submit a Software Performance Report.
BADSETCNT,

incorrect number of devices in output specification

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

2-55

Messages

BADSIGARG, bad sigarg pointer at 'pointer-addr' or bad sigarg vector, cannot
read sigarg vector near 'sigarg-addr'
Facility: DEBUG, VMS Debugger
Explanation: The debugger is trying to chain down the call stack (following
frame pointers) and has encountered an exception handler. The signal
argument pointer at location 'pointer-addr' points to a signal argument vector
at least part of which is not READ accessible near location 'sigarg-addr'.
User Action: Determine what part of your code is overwriting the stored
signal argument pointer on the call stack, or part of the signal argument
vector itself, and correct it. Since the debugger looks at the call stack to
symbolize addresses, you may suppress some of these messages by typing the
command SET MODE NOSYMBOLIC.

BADSORT,

error trying to sort input file

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

BADSPC,

no user matched specification

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

BADSPEC,

file specification cannot be parsed using default specification.

Facility: VMSINSTAL, Install Procedures
Explanation: VMSINSTAL cannot locate the file because of an invalid file
specification.
User Action: Resolve the problem, and reinstall the product. Otherwise,
contact your DIGITAL field service representative.

BADSPLINDEX,

invalid spin lock index

Facility: SDA, System Dump Analyzer
Explanation: You specified an invalid spin lock index to the SDA command
SHOW SPIN LOCKS. The index specified does not correspond to any spin
lock in the system.
User Action: Reenter the command. Specify a valid spin lock index or a spin
lock name.

2-56

Messages

BADSPLNAME, no spin lock could be found by that name
Facility: SDA, System Dump Analyzer
Explanation: You specified an incorrect name to the SDA command SHOW
SPIN LOCKS.
User Action: Reenter the command. Specify a valid spin lock name or a spin
lock index.

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

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

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

BADSTACK, stack corrupted-no further data available
Facility: DEBUG, VMS Debugger
Explanation: While displaying part of the call stack, the debugger determined
that the stack is corrupted and cannot continue executing the command.
User Action: See the accompanying message for more information.

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

2-57

Messages

BADSTART,

starting block beyond maximum legal block 'number'

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

cannot access start PC= 'address-value'

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

bad status returned from 'routine-name'

Facility: DEBUG, VMS Debugger
Explanation: The debugger got an unexpected error status from the system
service or RTL routine 'routine-name'.
User Action: Examine the error message to determine if the problem is
related to a lack of quota or otherwise related to your program. If so, then
take corrective action. If, after this evaluation, you believe that the problem
lies in the debugger, then submit a Software Performance Report.
BADSTATUS,

return status 'xxxxxxxx' different than last signal 'xxxxxxxx'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: This message indicates an internal VAXTPU error.
User Action: Submit a Software Performance Report.
BADSTRCNT,

invalid string count found in journal file

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

structure level in command tables not recognized

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

2-58

Messages

BADSTRLVL,

unrecognized structure level for command tables

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

invalid value on /STRUCTURE qualifier

Facility: INIT, INITIALIZE Command
Explanation: The only legal values for the /STRUCTURE qualifier are 1
and 2.
User Action: Correct the command. Specify either 1 or 2 for the
/STRUCTURE qualifier.
BADSUBFCN,

invalid subfunction received

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

swap VBN specified for non-process page

unknown symbol 'symbol-name'

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

bad symbol table

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The symbol table is invalid.
User Action: Correct the symbol table.

2-59

Messages

BADTARGET,

target location protected, cannot perform deposit

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

BADTIME,

'time-spec' is an invalid time specification

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

BADTYPE, invalid file type in startup file
Facility: START, System Startup Driver
Explanation: A startup component file in the startup component database
has a file type which is not COM or EXE.
User Action: Use the SYSMAN command STARTUP MODIFY FILE to correct
the file name.

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

BAD_TYPE,

invalid sort process specified

Facility: SORT, Sort/Merge Utility
Explanation: You passed one of the following sort type codes to the routine
package:

•

Less than 1 or greater than 4 if file 1/0

•

Not equal to 1 if record 1/0

•

An invalid key word in command /PROCESS

Legal values are 1 through 4 for file 1/0; 0 for record 1/0; and RECORD,
TAG, INDEX, or ADDRESS for the /PROCESS command parameter.
User Action: Specify a different sorting process.

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

2-60

Messages

- BADUSERDESC,

descriptor from user routine invalid or memory inaccessible

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

Introduction to VMS System Routines.
BADUSR,

username does not exist

Facility: AUTHORIZE, Authorize Utility
Explanation: The user name you specified does not exist in the system user
authorization file (SYSUAF.DAT).
User Action: Correct the user name and reenter your command. You can
display the records in the user authorization file by using the AUTHORIZE
command SHOW.
BADUSRDAT,

connect/disconnect userdata invalid

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

connect/ disconnect userdata is wrong length

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

error in value specification

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

illegal qualifier value

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

2-61

Messages

BADVALUE, illegal qualifier value
Facility: MESSAGE, Message Utility
Explanation: An illegal numeric value has been used in one of several
contexts within a MSG file (for example, bad facility numbers, bad base
numbers, or a bad FAO count).
User Action: Replace the illegal value with one within the valid range.
BADVALUE, integer value 'integer' is outside of specified limits
Facility: VAXTPU, VAX Text Processing Utility
Explanation: The argument that you supplied is outside of the valid
boundaries.
User Action: Reenter your command with a valid integer value for the
argument.
BADVALUE,

'value' is an invalid keyword value

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

'value' is an invalid keyword value

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

invalid change mode or message vector

Facility: SYSTEM, VMS System Services
Explanation: This severe error message is associated with a status code
returned from a system service request. An invalid change mode or message
vector is encountered.
User Action: Correct the change mode or message vector.
BADVOLl, bad VOLl ANS label
Facility: MOUNT, Mount Utility and INIT, INITIALIZE Command
Explanation: The protection encoded on a magnetic tape volume label is
invalid or the label itself is invalid; the magnetic tape ACP cannot process the
tape. The tape is defective, it is not an ANSI-labeled tape, or the hardware
device is not reading the tape properly.
User Action: Verify the tape volume. If necessary, mount the tape as a
foreign volume and try to read it.

2-62

Messages

BADVOLACC, invalid value on /LABEL:VOLUME_Accessibility qualifier
Facility: INIT, INITIALIZE Command
Explanation: An invalid ANSI "a" character is specified in the volume
accessibility field of the tape volume label. For example, the following
command specifies an invalid ANSI "a" character-a dollar sign ( $ ):
$ INITIALIZE/LABEL:VOLUME_ACCESSIBILITY:$

User Action: Specify a valid ANSI "a" character in the single-character field
of the command. The set of valid ANSI "a" characters includes: digits 0 .. 9,
uppercase A .. Z, space, and! " % & ' () * + ,-. / : ; < => ?
BADVOLLBL, invalid value for ANSI tape volume label
Facility: INIT, INITIALIZE Command
Explanation: You used one or more invalid ANSI "a" characters in the
volume label. The set of valid ANSI "a" characters includes: digits 0 .. 9,
uppercase A .. Z, space, and ! " % & / () * + ,-. / : ; < => ?
User Action: Respecify the command with valid ANSI "a" characters.
BADWATCH,

cannot watch protect address 'address-value'

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

bad WCB pointer in IRP

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

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

2-63

Messages

BADWINDLEN,

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

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

invalid data 'xxxx' at 'location'

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

bad zone

Facility: LIB, Library Facility
Explanation: LIB$SHOW_VM-20NE, LIB$STAT_VM-20NE, or
LIB$VERIFY_VM-20NE is called with a zone identifier that does not
represent a valid VM zone. Either the zone or one of its associated data
structures is invalid.
User Action: Begin debugging procedures to verify and correct the problem.
BASDUERRS,

basing image due to errors in relocatable references

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

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

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

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

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

2-64

Messages

BATCHNOOPR,

no operator available to service batch request

Facility: MOUNT, Mount Utility
Explanation: The MOUNT request is aborted because the batch job requires
operator assistance and no operator is present.
User Action: Call the operator and retry the request.
BATIS_OFF,

batching is off

Facility: SMG, Screen Management Facility
Explanation: A program tried to turn off batching when batching is already
off.
User Action: Make sure that there is one call to turn on batching for each
call to turn it off.
BATIS_ON,

batching is on

Facility: SMG, Screen Management Facility
Explanation: A program tried to turn on batching when batching is already
on. This is normal in a modular environment.
User Action: Make sure that there is one call to turn off batching for each
call to turn it on.
BATSTIPRO,

batching is still in progress

Facility: SMG, Screen Management Facility
Explanation: A user tried to end batching (updating) with a call to
SMG$END_DISPLAY_UPDATE or SMG$END_pASTEBOARD_UPDATE.
This action did not terminate batching because there were more calls to begin
batching than to end batching.
User Action: None. An outer level routine probably still needs batching to
be in effect.
BBFOVF,

bad block file overflow on 'device-name'

Facility: BAD, Bad Block Locator Utility
Explanation: This message indicates that during the analysis of the medium,
the SDBSF became full. It could be as a result of a large number of bad
blocks specified to the /BAD_BLOCKS qualifier or as a result of an unreliable
medium.
User Action: Rerun the ANALYZE/MEDIA command without as many bad
blocks entered to the /BAD_BLOCKS qualifier, or in the default mode of the
/NOKEEP qualifier, which will re-create the SDBSF.
BBFWRT, failed to write the bad block file on 'device-name'

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

2-65

Messages

BBLHEADER, file ('file-id') 'filename' contains suspected bad blocks

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the specified file is marked as
containing suspected bad blocks. When the file is deleted, the blocks will be
verified and returned to the bad block file if necessary.
User Action: If desired, examine the contents of the file and reconstruct from
backup media as necessary.
BDPPURGERR,

buffered datapath purge incomplete

'string' beginning

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

'string' beginning at 'date'

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

'string' beginning at 'time'

Facility: Shared by several facilities
Explanation: A program phase began.
User Action: None.
BEGNLEND, beginning time not earlier than ending time

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

2-66

Messages

BEGOFBUF,

attempt to move past the beginning of buffer 'buffer-name'

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

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

BEGRAN,

requested beginning time beyond range of input file

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

BES,

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

BIIC failure-BI CSR/BER/CNF 'xxxxxxxx/xxxxxxxx/xxxxxxxx',
Facility: VAXport, VAXport Driver
Explanation: The port driver attempts to reinitialize the port; after 50 failed
attempts it marks the device off line.
User Action: Call DIGITAL field service to check the port hardware.

BINARYOPER,

operand combination 'type' 'aper' 'type' unsupported

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The specified operator does not support the specified data type
combination.
User Action: Use only supported data types with the operator.

2-67

Messages

BINCHKSUM,

a binary record failed checksum in 'record'

Facility: EXCHANGE, Exchange Utility
Explanation: While reading a formatted-binary record, the Exchange Utility
found a record whose computed checksum did not match the actual checksum
stored in the record.
User Action: EXCHANGE ignores this error and copies the file as if all
the checksums are correct. If the output file is a formatted-binary file, the
checksum in the output record is correct. Make sure that the output file is
usable.

BINRECFMT,

an illegal binary record found in 'filename'

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

BITMAPERR, 1/0 error on storage bitmap; volume locked
Facility: MOUNT, Mount Utility
Explanation: An 1/0 error is encountered during a mount operation. Existing
files on the volume can be accessed but other operations, for example,
CREATE and DELETE, are not possible.
User Action: Repair the volume with the Verify Utility.

BITMAPINV,

storage bitmap is invalid, volume locked

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

BITRANGE,

bit range out of limits

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

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

Management Services Manual.
2-68

Messages

BKZ,

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

BLKOBAD, block 0 is bad, do not use 'device-name' as a system device
Facility: BAD, Bad Block Locator Utility
Explanation: Block zero (0) is defective on the medium.
User Action: Do not use the medium as a system device, because block zero
is used to contain the boot strap.
BLKDIRSYNX,

block directive syntax error

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

block expression not absolute

Facility: MACRO, VAX MACRO Assembler
Explanation: The expression specifying the amount of storage to be allocated
in a .BLKA, .BLKB, .BLKD, .BLKF .. BLKG, .BLKH, .BLKO, .BLKQ, OR BLKW
directive contained an undefined symbol or is a relative expression.
User Action: Replace the expression with an absolute expression that does
not contain any undefined symbols.
BLKZERO, block zero is bad; volume not bootable
Facility: INIT, INITIALIZE Command
Explanation: This message is generated by the DCL command INITIALIZE
as a warning message. The volume cannot be bootstrapped on a PDP-11.
The volume is usable on a VMS system disk.
User Action: Note that the volume probably cannot be used as a system
volume for a VAX-11 processor model that requires access to the boot block
during a bootstrap operation.
BLKZERO, block zero of 'device-name' is bad-volume not bootable
Facility: BACKUP, Backup Utility
Explanation: The boot block of the specified volume is not usable.
User Action: Note that the volume probably cannot be used as a system
volume for a VAX-11 processor model that requires access to the boot block
during a bootstrap operation.

2-69

Messages

BLN,

invalid block length for control block (RAB/FAB)
Facility: RMS, VMS Record Management Services
Explanation: An invalid value is specified in a VMS RMS FAB or RAB block
length field.
User Action: Verify that the call to the VMS RMS service is coded correctly.
Specifically, ensure that the control block is properly initialized and that the
block length field is not modified after initialization.
1

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

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

BLOCKCHECKO, block check, please report error error

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

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

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

2-70

Messages

BLOCKLOST, block of filespec lost due to unrecoverable error
Facility: BACKUP, Backup Utility
Explanation: The Backup Utility encountered an irrecoverable error in
reading the specified save set and cannot correct the error using the
redundancy information.
User Action: None. Save set data has been lost.
BLPRSP, bad loopback response
Facility: NCP, Network Control Program
Explanation: A loopback message did not match either the length or content
that the system expected.
User Action: Use another form of testing to determine why the loopback
failed.
BMS,

bad margin specification: 1string 1
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: An illegal value is used for a margin setting.
User Action: Correct the margin setting in the input file.

BOF, beginning of file detected
Facility: RMS, VMS Record Management Services
Explanation: During a backspace operation, the file is positioned at the
beginning of the file before the specified number of blocks is backspaced. The
status value (STV) field in the FAB or RAB contains the number of blocks
actually spaced.
User Action: This is a warning status. Modify the source program, if
necessary, to detect and respond to the condition.
BOOT-F-Bootfile not contiguous
Facility: VMB, Virtual Memory Boot
Explanation: The file (SYSEXE]SYSBOOT.EXE is located but is not
contiguous.
User Action: The disk you are attempting to bootstrap cannot be
bootstrapped. Obtain another copy of the system disk.
BOOT-F-Failed to initialize device
Facility: VMB, Virtual Memory Boot
Explanation: Encountered an error in the load path while VMS was trying to
initialize the boot device,
User Action: Try initializing again. If this fails, call DIGITAL field service.

2-71

Messages

BOOT-F-1/0 error reading boot file
Facility: VMB, Virtual Memory Boot
Explanation: An uncorrectable read error occurred while the file
[SYSEXE]SYSBOOT .EXE is being read.
User Action: Try rebooting the disk. If subsequent attempts fail, obtain
another copy of the system disk.

BOOT-F-Nonexistent drive
Facility: VMB, Virtual Memory Boot
Explanation: The specified drive number does not exist.
User Action: Specify an appropriate device unit to the console program, or
use a different console bootstrap command procedure.

BOOT-F-Unable to locate BOOT file
Facility: VMB, Virtual Memory Boot
Explanation: The file [SYSEXE]SYSBOOT.EXE could not be found.
User Action: You are attempting to bootstrap a volume that does not contain
a VMS binary system. Attempt to reboot using an appropriate disk volume.

BOOT-F-Unexpected exception
Facility: VMB, Virtual Memory Boot
Explanation: An unexpected exception occurred while the primary bootstrap
(VMB.EXE) is being executed. This condition probably indicates a corrupted
SYSBOOT.EXE file or a hardware failure.
User Action: Determine the source of the error, and either obtain a new copy
of the system disk or call your local field service representative.

BOOT-F-Unexpected machine check
Facility: VMB, Virtual Memory Boot
Explanation: An unexpected machine check occurred while the primary
bootstrap (VMB.EXE) is being executed. This condition probably indicates a
corrupted SYSBOOT.EXE file or a hardware failure.
User Action: Determine the source of the error, and either obtain a new copy
of the system disk or call your local field service representative.

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

2-72

Messages

BRDCST,

unable to write to console device 'sink-name'

Facility: EVL, Event Logger
Explanation: An error occurred while writing to the console sink. The event
is discarded. This message displays the name of the console.
User Action: None.
BRDESTRANG, branch destination out of range
Facility: MACRO, VAX MACRO Assembler
Explanation: The address specified in the branch instruction is too far from
the current PC. Branch instructions with byte displacements have a range of
-128 bytes to +127 bytes from the current PC. Branch instructions with word
displacements have a range of -32768 bytes to +32767 bytes from the current
PC.
User Action: Use a branch instruction with a word displacement instead
of one with a byte displacement; use a jump (JMP) instruction instead of a
branch instruction; or change the program logic so that the branch destination
is closer to the branch instruction.
BRDMSGLOST,

broadcast queue pointer has no related entry

breakpoint fault at PC location, PSL = 'xxxxxxxx'

Facility: SYSTEM, VMS System Services
Explanation: A breakpoint instruction is encountered. This message indicates
an exception condition that is not handled by the condition handler and is
usually followed by a display of the condition arguments, registers, and stack
at the time of the exception.
User Action: Examine the PC and virtual address displayed in the message
to correct the instruction that caused the error.
BRKNLIB, library 'library-name' not properly closed, compress or rebuild
Facility: LIBRAR, LIBRARY Command
Explanation: An error occurred during a previous update to the library that
interrupted the write operation, leaving the library in an inconsistent state.
User Action: This library can no longer be modified, but it can be read.
Uncorrupted data can be reclaimed by compressing the library or by
extracting modules and re-creating a new library.

2-73

Messages

BRTOOFAR,

destination 'addr' is too far for branch operand

Facility: PATCH, Patch Utility and DEBUG, VMS Debugger
Explanation: If the Patch Utility generated this message, the relative
displacement for the branch instruction is not large enough to reach the
specified destination address. If the debugger generated this message, the
DEBUG command DEPOSIT specified a branch instruction with a destination,
addr, too far from the current PC.
User Action: If the Patch Utility generated this message, correct the
destination address and retry the operation. If the debugger generated
this message, change a BRB instruction to BRW or a BRW to JMP or specify a
closer address.
BUFBLKREQ, buffer count or block count required
Facility: SET, SET Facility
Explanation: You specified either the /BLOCKS_COUNT or
/BUFFER_COUNT qualifier (with the SET RMS command) without
specifying numeric values.
User Action: Reenter the command and qualifier specifying a numeric value
for the qualifier.
BUFBYTALI,

device does not support byte-aligned transfers

Facility: SYSTEM, VMS System Services
Explanation: Some devices do not support buffers that are not aligned on
word boundaries or byte counts that are not an even number.
User Action: Recode the program using the .ALIGN macro directive or
change the byte count to an even number.
BUFFEROVF, buffer overflow
Facility: DEBUG, VMS Debugger
Explanation: This message indicates an internal debugger error.
User Action: Submit a Software Performance Report.
BUFFEROVF,

output buffer overflow

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

output buffer overflow

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

2-74

Messages

BUFFERSLOST,

all buffers are lost

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

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

•

User status word (USW) not word-aligned

•

Buffer area not longword-aligned

•

Random Channel List (RCL) not word-aligned

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

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

BUFOVFL, buffer overflow for output file name string
Facility: PPL, Parallel Processing Facility
Explanation: Buffer could not contain the complete output string.
User Action: Recode to pass a larger buffer.

BUFOVR, internal error-Packet has overflowed buffer
Facility: SMI, System Management Intergator/Server
Explanation: The packetizer has produced a buffer larger than 4096 bytes.
User Action: Submit a Software Performance Report showing all SYSMAN
commands leading to this error. Also submit the output of a SHOW
CLUSTER command.

2-75

Messages

BUG,

internal RMS error condition detected
Facility: RMS, VMS Record Management Services

Explanation: This message indicates an internal software error occurred in
VMS RMS.
User Action: Collect as much information as possible and submit a Software
Performance Report.

BUGCHECK,

internal consistency failure

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

BUG_DAP,

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

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

BUG _DDI,

invalid default directory

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

BUSY,

a busy signal is detected on the phone line

Facility: DTK, DECtalk Facility
Explanation: The routine DTK$DIAL_PHONE is called to dial a phone
number and the line is busy.
User Action: Try calling again.

BUSY,

user structure (FAB/RAB) still in use

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

2-76

Messages

BVN,

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

BVP failure-Status /Error /Data 'xxxxxxxx/xxxxxxxx/xxxxxxxx',
Facility: VAXport, VAXport Driver
Explanation: The port driver attempts to reinitialize the port; after 50 failed
attempts, it marks the device off line.
User Action: Call DIGITAL field service to check the port hardware.

BVP timeout-Status /Error /Data 'xxxxxxxx/xxxxxxxx/xxxxxxxx',
Facility: VAXport, VAXport Driver
Explanation: The port driver attempts to reinitialize the port; after 50 failed
attempts, it marks the device off line.
User Action: Call DIGITAL field service to check the port hardware.

Cables have gone from CROSSED to UNCROSSED
Facility: VAXport, VAXport Driver
Explanation: The VAXport driver logs this event.
User Action: None.

Cables have gone from UNCROSSED to CROSSED
Facility: VAXport, VAXport Driver
Explanation: The VAXport driver logs this event.
User Action: Check for crossed-cable pairs.

CACLS,

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

Facility: SHOW CLUSTER, Show Cluster Utility
Explanation: The class name entered does not apply to the currently selected
report and, therefore, cannot be added to the report. The name is, however,
valid in a different report.
User Action: Select a different report or enter the HELP CLASSES command
to get a list of available classes.

CAFINVGROUP, group number is invalid or out of range
Facility: SYSMAN, Cluster System Management Utility
Explanation: A CONFIGURATION SET CLUSTER_AUTHORIZATION
command specified an invalid group number.
User Action: Reenter the command with a numeric group number between 1
and 65535.

2-77

Messages

CAFNEITHER,

neither GROUP nor PASSWORD given-no action taken

Facility: SYSMAN, Cluster System Management Utility
Explanation: A CONFIGURATION SET CLUSTER_AUTHORIZATION
command supplied neither a group number nor a password.
User Action: Reenter the command with the /GROUP or /PASS WORD
qualifiers, or both, as necessary.

CAFNOTCLU,

*Warning*-Environment not CLUSTER- check all system disks
for consistency

Facility: SYSMAN, Cluster System Management Utility
Explanation: A CONFIGURATION SET /SHOW CLUSTER_
AUTHORIZATION command is entered in a non-CLUSTER environment.
To ensure consistency of the CAF database throughout the cluster, these
commands should normally be entered from a CLUSTER environment.
User Action: Change the environment and reenter the command, if desired.

CAFOLDGROUP,

existing group will not be changed

Facility: SYSMAN, Cluster System Management Utility
Explanation: A CONFIGURATION SET CLUSTER_AUTHORIZATION
command specified a new password but did not specify a new group number.
The old group number is retained.
User Action: None, if the group number is correct.

CAFOLDP ASS,

existing password will not be changed

Facility: SYSMAN, Cluster System Management Utility
Explanation: A CONFIGURATION SET CLUSTER_AUTHORIZATION
command specified a new group number but did not specify a new password.
The old password is retained.
User Action: None, if the password is correct.

CAFPASSLEN,

password is null or too long

Facility: SYSMAN, Cluster System Management Utility and CAF, Cluster
Authorization File Service
Explanation: A CONFIGURATION SET CLUSTER_AUTHORIZATION
command specified an invalid password.
User Action: Reenter the command with a valid password.

CAFREBOOT,

cluster authorization file updated. The entire cluster should be
rebooted.

Facility: SYSMAN, Cluster System Management Utility
Explanation: When you update the CAF, you must reboot the cluster.
User Action: Reboot the cluster.

2-78

Messages

CALLOVER,

stack overflow

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

CALL_USER routine failed with status %X 'status'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The CALL _USER routine returned the indicated failure status.
User Action: Your action depends on the routine returned.
CANCEL,

I/O operation canceled

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

command is canceled by keyboard action

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility received a CTRL/C key sequence while
processing a command; it canceled the command and returned to the prompt.
User Action: None.
CANCELQUIT,

QUIT canceled by request

Facility: VAXTPU, VAX Text Processing Utility
Explanation: Execution of the built-in procedure QUIT is canceled when you
respond "no" to the REALLYQUIT question.
User Action: None.
Cannot set terminal type from change mode,
Facility: EDT, EDT Editor
Explanation: You attempted to enter a SET TERMINAL
{VT1001VT521HCPY} command while working in a screen mode.
User Action: To change the terminal type with the SET TERMINAL
command, you must shift to line mode.
CANT BIND,

can't initialize device

Facility: LATCP, LAT Control Program
Explanation: The LAT device cannot be initialized.
User Action: Specify an appropriate application or a dedicated port.

2-79

Messages

CANTACCESSMAIN,

cannot access the main debugger

Facility: DEBUG, VMS Debugger
Explanation: The kernel debugger (DEBUG.EXE) cannot access the main
debugger (DEBUGSHR.EXE). The reason is given in the message following
this message.
User Action: Correct the problem given by the messages following this
message. If you cannot solve the problem, submit a Software Performance
Report.
CANTBAL,

can't balance last page

Facility: DSR, DIGITAL Standard Runoff
Explanation: An internal error has occurred.
User Action: Submit a Software Performance Report. Please include the file
that caused the error.
CANTEXPREG, cannot expand virtual address space
Facility: BACKUP, Backup Utility
Explanation: Standalone BACKUP attempted unsuccessfully to expand its
virtual address space.
User Action: If this error can be reliably reproduced, the BACKUP command
used and a description of the circumstances should be submitted along with a
Software Performance Report.
CANTGETFID,

cannot get file-id for image file opened on channel 'channelnumber'

Facility: DEBUG, VMS Debugger
Explanation: An error occurred while trying to get the file identification of
the image file opened on channel 'channel-number'. The message following
this message states the reason for this error.
User Action: Correct the problem given by the messages following this
message. If you cannot solve the problem, submit a Software Performance
Report.
CANTLOCK,

cannot lock pages into memory. If the system disk goes off line,
reboot

Facility: BACKUP, Backup Utility
Explanation: Standalone BACKUP could not lock the required pages into the
working set.
User Action: Normally, no action is necessary. However, if the system disk
goes off line, it will be necessary to reboot the systef!l. The operation of
standalone BACKUP is likely to be very slow because there is insufficient
memory to lock down a small portion of the working set.

2-80

Messages

CANTLOCMAC,

can't locate macro in macro libraries

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

CAPTIVE,

this command cannot be executed; Your account is CAPTIVE

Facility: MAIL, Mail Utility
Explanation: You attempted to enter a SPAWN command, and your account
is CAPTIVE.
User Action: Contact your system manager if you feel your account should
not be CAPTIVE.

CAPTIVE, unable to create a subprocess in a captive account
Facility: VAXTPU, VAX Text Processing Utility
Explanation: Captive accounts are not allowed unrestricted access to CLis,
which the SPAWN or CREATE_PROCESS built-ins would allow.
User Action: Don't try to use the SPAWN or CREATE_PROCESS built-ins
from a captive account.

CARDS,

cards

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

CASETOOLARGE,

CASE limits distance too large

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

CBT,

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

2-81

Messages

CCF,

cannot close file

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

cannot connect RAB

Facility: RMS, VMS Record Management Services
Explanation: VMS RMS could not connect a record access block (RAB) to the
specified file access block (FAB). This error usually results from one of the
following actions:
•

Specifying block 1/0 (setting the RAB$V_BIO option of the RAB$L_ROP
field) with multistreaming (setting the FAB$V__MSE option of the
FAB$B_SHR field)

•

Attempting to connect multiple RABs to a FAB when the multistreaming
option (FAB$V_MSE) of the file sharing field (FAB$B_SHR) has not been
set

•

Attempting a DECnet operation when the multistreaming option is set

The multistreaming option is not supported for DECnet operations.

User Action: Modify the program. Do not attempt to use unsupported
operations.
CDA,

cannot deliver AST

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

negative reference count on shared memory CEB

2-82

Messages

CEM,

comma expected, missing: 'string'

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

central

chained write status

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

error assigning or deassigning channel

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

2-83

Messages

CHG,

invalid key change in $UPDATE (CHG not set)

Facility: RMS, VMS Record Management Services
Explanation: A VMS RMS $UPDATE operation specified a record that
contained one or more changed key values for keys that do not have the
'keys may change' attribute set in the XAB key option flag.
User Action: Either reorganize the file and specify the 'keys may change'
attribute to be set in the XAB key option flag, if necessary, or modify the
source program to detect and respond to the condition.
CHK, bucket format check failed for VBN = 'nnn'
Facility: RMS, VMS Record Management Services
Explanation: VMS RMS detected a corrupted bucket in an indexed file. The
bucket address check or bucket checksum is incorrect.
User Action: Reorganize the file, if possible; otherwise, re-create the file. The
status value (STV) field of the FAB or RAB contains the starting virtual block
number of the bucket in error.
This error can be caused by hardware errors, VMS RMS or system software
errors, or modifications of files by non-RMS programs. If RMS errors are
suspected, submit a Software Performance Report.
CHKAL THOME,

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

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

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

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the primary home block at the
specified virtual block of the index file on the specified relative volume
is corrupted. The Verify Utility reconstructs the block. If the volume can
no longer be mounted by the operating system, it is corrupted and must
be reconstructed from back-up media. If the volume can be mounted, the
damage can be repaired by copying the volume to fresh media.
User Action: None.
CHKSCB,

invalid storage control block, RVN 'n'

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the storage control block on the
specified relative volume is corrupted. The Verify Utility reconstructs the
block. If the volume can no longer be mounted by the operating system, it
is corrupted and must be reconstructed from back-up media. If the volume
can be mounted, the damage can be repaired by copying the volume to fresh
media.
User Action: None.

2-84

Messages

CHMONIS,

change mode instruction while on interrupt stack

CHMVEC,

CHM vector bits <l:O> not 0

FaciUty: BUGCHECK, System Bugcheck
Explanation: The VMS software detected an irrecoverable, inconsistent
condition. After all of physical memory is written to a system dump file, the
system will automatically reboot if the BUGREBOOT system parameter is set
to 1.
User Action: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error, and that includes a BACKUP save set
containing the system dump file and the error log file active at the time of the
error. (Use the /IGNORE=NOBACKUP qualifier on the BACKUP command
that produces the save set included with the SPR.)

CHN,

assign channel system service request failed

Facility: RMS, VMS Record Management Services
Explanation: VMS RMS failed to assign a channel to a device specified for an
input or output operation. This message is usually accompanied by a system
message that indicates the reason for the failure.
User Action: The status value (STV) field in the FAB contains the system
status code that indicates the reason for the failure. Take corrective action
based on these codes.

If the error results from the DCL command OPEN, or following the DCL
command@ (execute procedure) or the DCL command RUN, verify that the
volume containing the specified file is on line and mounted.
CINBAD,

connect not accepted/rejected as expected

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

CINREJ,

connect aborted, nsp reason is 'number'

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

2-85

Messages

CIPORT,

fatal error detected by VAXport driver (PADRIVER)

CIREXLST,

command aborted after 'number_oLhandlers' exit handlers displayed
circular exit handler list suspected

Facility: DEBUG, VMS Debugger
Explanation: After displaying information about 100 exit handlers, the
debugger suspects that a circular exit handler list exists.
User Action: If a circular exit handler list exists, then identify and correct the
error in your program.

CJFERR,

journaling error; volume dismounted to ensure data integrity

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

CJL,

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

CLASDISAB,

class disabled

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

2-86

Messages

CLASMISS,

requested class record missing from input file

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

some requested classes not present in input file

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

some requested classes have file structure levels incompatible with
the current version of MONITOR

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

CLI error parsing command line

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

error activating command interpreter 'interpreter'

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

2-87

Messages

CUFRCEXT,

CU forced exit

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

CUMISMATCH,

CU type of image does not match /CU qualifier

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

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

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

CUSYMTBL,

error creating space for command interpreter symbol table

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

2-88

Messages

CLIWARNMSG, Warning: /CLITABLES field may need to reflect changes to
/CLI field
Facility: AUTHORIZE, Authorize Utility
Explanation: If you modify the command language interpreter (CLI) field of
a record in the system user authorization file, you may have to modify the
CLITABLES field to reflect the change. If you have set the CLI field to DCL
or MCR, however, the CLITABLES field defaults to the correct value.
User Action: If you have changed the CLI field to a value other than DCL
or MCR, use the AUTHORIZE command MODIFY/CLITABLES to set the
CLITABLES field to the corresponding tables. Refer to the description of the
LOGIN Procedure in the VMS DCL Dictionary for further information about
specifying CLI tables.
CLOSEDEL, error deleting 'filename'
Facility: Shared by several facilities
Explanation: An error occurred while a file is being closed after a delete
operation. This message is usually accompanied by a VMS RMS message
indicating the reason for the failure.
User Action: Take corrective action based on the associated message.
CLOSEERR,

an error occurred closing 'filename'

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility received an error from RMS while trying
to close a Files-11 file.
User Action: This message will be followed by one or two error messages
reporting the actual condition discovered by RMS. Take corrective action
suggested by the RMS error messages, then retry the command.
CLOSEERR, error closing 'filespec'
Facility: SET, SET Facility
Explanation: An error occurred while trying to close a file whose
characteristics have just been set. This message is accompanied by a message
explaining why the file could not be closed.
User Action: Respond to the accompanying message.
CLOSEFILE, error closing event file 'file-id'
Facility: EVL, Event Logger
Explanation: An error occurred while closing an event file.
User Action: None. This message displays the name of the file.

2-89

Messages

CLOSEFOREIGN,

an error occurred closing the volume 'volume'

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

error closing input file

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

error closing input file 'filespec'

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

unable to close input

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

error closing job 'job-name' for user 'user-name' in queue 'queuename'

Facility: JBCUPGRAD, Queue Upgrade Utility
Explanation: An error occurred during a $SNDJBC system service call
attempt to close the job.
User Action: The accompanying message gives information about the failed
operation. Correct the problem and retry the upgrade.
CLOSEMON,

error disconnecting monitor process 'sink-name'

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

2-90

Messages

CLOSEOUT,

error closing output file 'filespec'

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

CLOSEOUT,

error closing output file

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

CLOSEOUT,

unable to close output

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

CLSERR,

close error code of 'xx' on file 'filespec'

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

CLSTBLERR,

device class value, 'value' not in class tables

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

CLUBELBAS,

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

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

2-91

Messages

CLUEXIT,

node Exiting Cluster

Facility: BUGCHECK, System Bugcheck
Explanation: To avoid partitioning of the VAXcluster, this system exited
the VAXcluster by crashing. Generally, this is a normal condition. If the
condition persists, this processor is most probably configured incorrectly into
two distinct VAXclusters. After all of physical memory is written to a system
dump file, the system will automatically reboot if the BUGREBOOT system
parameter is set to 1.
Explanation: Ensure that the VAXcluster is properly configured.

CLUGDIFF,

*Warning*-CAF for node 'nnnnnn' has group 'm'

Facility: SYSMAN, Cluster System Management Utility
Explanation: A CONFIGURATION SHOW CLUSTER_AUTHORIZATION
command is entered in a CLUSTER environment, and not all nodes in the
cluster have the same group number.
User Action: Enter a CONFIGURATION SET CLUSTER_AUTHORIZATION
command to ensure that system disks for all members indicate the same
group number and password.

CLULIST,

CLUSTER is invalid with a list of nodes

Facility: SYSMAN, Cluster System Management Utility
Explanation: In a SET ENVIRONMENT command, a /CLUSTER qualifier
cannot be specified if a /NODE qualifier includes more than one node.
SYSMAN cannot perform clusterwide operations on more than one cluster at
a time.
User Action: If a clusterwide environment is desired, it is only necessary to
specify one node in the cluster, or omit the NODE qualifier if the local cluster
is desired.

CLUPDIFF,

*Warning*-CAF for node 'nnnnnn' has different password

Facility: SYSMAN, Cluster System Management Utility
Explanation: A CONFIGURATION SHOW CLUSTER_AUTHORIZATION
command is entered in a CLUSTER environment, and not all nodes in the
cluster have the same password.
User Action: Enter a CONFIGURATION SET CLUSTER_AUTHORIZATION
command to ensure that system disks for all members indicate the same
group number and password.

CLUSTER,

unsuitable cluster factor

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

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

2-92

Messages

CLUSTER,

unsuitable cluster factor for 'device-name'

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

command canceled

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

1/0 error reading commands

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

error reading command input

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

command line segment in error 'error'

Facility: DIFF, DIFFERENCES Command
Explanation: Part of the command line is syntactically incorrect.
User Action: Specify the correct syntax in the command line.
CMDNOTFND, command not found-use RECALL/ ALL to display saved
commands
Facility: CU, Command Language Interpreter (DCL)
Explanation: The command that you tried to find using RECALL is not
found.
User Action: Use the RECALL/ ALL to display all the saved commands and
then modify and reenter your RECALL command.

2-93

Messages

CMDNOTVLD,

command not valid on the running system

Facility: SDA, System Dump Analyzer
Explanation: You entered an SDA command while analyzing the running
system. The command is valid only when analyzing a dump file.
User Action: None. The command is not valid while analyzing the running
system.
CMDOBS,

MSCP server must be loaded by setting SYSBOOT parameter
MSCP_LOAD

Facility: SYSGEN, System Generation Utility
Explanation: The MSCP command within SYSGEN is now obsolete. The
proper way for loading the MSCP server is to set the SYSGEN parameter
MSCP_LOAD. This will load the MSCP server during SYSBOOT.
User Action: Setting the SYSGEN parameter to load the MSCP server
during SYSBOOT will result in a warning when the MSCP command within
SYSGEN is entered. If this error is printed as the result of a startup command
procedure, changing the parameter to load the server earlier will enable
the old command procedure to complete successfully with only a warning
message.
CMDSYNTAX,

command line syntax error

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

command syntax error

Facility: DIFF, DIFFERENCES Command
Explanation: The syntax of the DIFFERENCES command line is incorrect.
User Action: Use the DCL command HELP or refer to the VMS DCL

Dictionary to determine the correct command syntax and reenter the
command.
CMDTOOLONG,

command line exceeds maximum length

Facility: AUTHORIZE, Authorize Utility
Explanation: The length of your command, after any symbols and logical
names have been expanded, exceeds the maximum allowable length.
User Action: Reenter a shorter form of the command.
CMDTOOLONG,

command line too long in options file 'filename'

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

2-94

Messages

CMODSUPR,

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

Facility: SYSTEM, VMS System Services
Explanation: An image attempted to execute a change mode to supervisor
instruction, but the image did not have a change mode handler declared. This
message indicates an exception condition and is usually followed by a display
of the condition arguments, registers, and stack at the time of the exception.
The code displayed in the message is the change mode code specified in the
instruction.
User Action: Examine the PC and virtual address displayed in the message
to determine which instruction caused the error.
CMODUSER,

change mode to user trap, code= 'nnn 1, PC= 'location 1, PSL =
1
xxxxxxxx 1

Facility: SYSTEM, VMS System Services
Explanation: An image attempted to execute a change mode to user
instruction, but the image did not have a change mode handler declared.
This message indicates an exception condition and is usually followed by a
display of the condition arguments, registers, and stack at the time of the
exception.
User Action: Examine the PC and virtual address displayed in the message
to determine which instruction caused the error.
CMPOUTFl 1, /COMPARE requires save set as first input
Facility: BACKUP, Backup Utility
Explanation: In a compare operation between a save set and a disk volume,
you must specify the save set as the first input and the disk volume as the
second input.
User Action: Correct and reenter the command.
CNF,

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

CNFOVR, internal error-Too many cluster members
Facility: SMI, System Management Intergator/Server
Explanation: The configuration table in SMIREMOTE has overflowed.
User Action: Submit a Software Performance Report showing all SYSMAN
commands leading to this error. Also, submit the output of the SHOW
CLUSTER command.

2-95

Messages

CNFQUAVAL,

conflicting qualifier values for 'qualifier', 'qualifier'

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

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

CNTERR,

connect error code of 'xx' on file 'filespec'

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

Are you repeating Ay to abort the remote session on node 'node-name'?

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

'library filespec' is a copy of 'old library filespec'

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

error detected by Connection Manager

2-96

Messages

COB,

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

COD,

invalid or unsupported type field in XAB at 'address'

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

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

COI,

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

COLLERR,

error during data collection

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

cannot combine multiple classes with the cluster class

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

2-97

Messages

COMCOD,

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

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

COMFAIL,

a communication failure is detected

Facility: DTK, DECtalk Facility
Explanation: A communications malfunction occurred since the DECtalk
device was turned on.
User Action: Check the DECtalk hardware.

COMFIL,

contents of component database

Facility: SYSMAN, Cluster System Management Utility
Explanation: The following output is being generated from the startup
component file on the named system.
User Action: None.

COMFILEMTY,

startup component database is empty

Facility: SMI, System Management Intergator/Server
Explanation: The current startup component entry does not have any entries.
User Action: Use the SYSMAN command STARTUP ADD FILE to add
entries to this database before using commands to examine or modify entries.

COMMA,

requested value is terminated by a comma

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

Command buffer exhausted
Facility: EDT, EDT Editor
Explanation: The string of change mode commands exceeds 255 characters.
User Action: Divide the string into several lines and reenter the command.

Command buffer exhausted during XLATE command processing
Facility: EDT, EDT Editor
Explanation: You have put too many characters in your XLATE procedure.
EDT can handle only 255 characters per command line.
User Action: Enter fewer characters.

2-98

Messages

Command file could not be closed
Facility: EDT, EDT Editor
Explanation: The startup command file cannot be closed. The appropriate
system message provides more information on the nature of the problem.
User Action: Correct the problem indicated by the accompanying message.
Command file could not be opened
Facility: EDT, EDT Editor
Explanation: The command file given in the command line cannot be
opened. EDT will display an associated file system message for the error.
User Action: Correct the problem indicated by the file system message.
Command file does not exist
Facility: EDT, EDT Editor
Explanation: The command file parameter in the command line does not
exist in the specified directory.
User Action: Reenter the command specifying a command file parameter that
does exist in the specified directory.
COMMHARD,

communications hardware error detected

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

filename not of type COM or EXE

Facility: SYSMAN, Cluster System Management Utility
Explanation: A startup component file name contains a file type other than
COM or EXE.
User Action: Use STARTUP MODIFY to correct the file name.
COMPARED,

compared 'filespec'

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

2-99

Messages

COMPAT,

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

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

Meaning

Reserved instruction execution

BPT instruction executed

IOT instruction executed

EMT instruction executed

TRAP instruction executed

Illegal instruction executed

Odd address fault

TBIT trap

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

comparing queue file 'filespec' to queue file 'filespec' beginning at
'date-and-time'

Facility: JBCUPGRAD, Queue Upgrade Utility
Explanation: This is an informational message that indicates the specified
queue files are being compared.
User Action: None.
COMPEND,

comparing queue file 'filespec' to queue file 'filespec' ended at
'date-and-time'

Facility: JBCUPGRAD, Queue Upgrade Utility
Explanation: This is an informational message that indicates the comparison
of the specified queue files has finished.
User Action: None.
COMPFAIL,

comparison found differing values for field 'type-of-field'

Facility: JBCUPGRAD, Queue Upgrade Utility
Explanation: Different values for the specified field in the two queue files are
being compared. This message is followed by a message that specifies the
two different values for the field.
User Action: If the specified difference is undesirable, attempt to make
appropriate changes according to the accompanying message.

2-100

Messages

COMPILED,

compilation completed without errors

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

compilation aborted

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

processing complete 'string'

Facility: DSR, DIGITAL Standard Runoff
Explanation: The DSR Table of Contents Utility has completed processing
the indicated input file. This message is informational.
User Action: None.
COMPLX, _expression too complex-simplify
Facility: CLI, Command Language Interpreter (DCL)
Explanation: The command interpreter cannot analyze an arithmetic
expression in a command, because it contains too many operators and/or
parentheses.
User Action: Shorten the expression and reenter the command. If necessary,
execute more than one command.
COMPSYNC,

queue file 'filespec' is missing 'type-of-data' 'name-of-item'

Facility: JBCUPGRAD, Queue Upgrade Utility
Explanation: The specified queue file is missing the specified item. The item
is skipped over in an attempt to resynchronize comparison of the remaining
data in the two queue files.
User Action: Specify the item in both queue file descriptions, retry the
upgrade, or attempt to make appropriate changes at the DCL level.
COMREMJBC,

error communicating with another job controller

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

2-101

Messages

COMSTA,

component in wrong state

Facility: NCP, Network Control Program
Explanation: A component is in a state inconsistent with the request; for
example, a down-line load is attempted over a line with OFF status.
User Action: Check the status of the component and reenter your command.

CONABORT,

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

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

CONCAT,

requested value is terminated by a plus sign

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

CONCEALED,

logical device name concealed physical device name

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

CONERR,

connect error

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

CONFATTR,

conflicting attributes in definition

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

2-102

Messages

CONFBASADR,

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

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

CONCATENATE has already been specified

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

only one DEFAULT or REQUIRED clause is allowed

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

'filename', delete? (Y or N):

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

a DISALLOW clause has been specified

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

2-103

Messages

CONFFAC,

facility definition conflicts with previous definition

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

CONFIXMEM,

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

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

CONFLICT,

illegal combination of command elements-check documentation

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

CONFLICT,

/PASSWORD and /GENERATE_PASSWORD are mutually
exclusive

Facility: AUTHORIZE, Authorize Utility
Explanation: The /PASSWORD qualifier and the /GENERATE_
PASSWORD qualifier are mutually exclusive.
User Action: Reenter the command with one qualifier.

CONFMEM,

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

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

CONFNEG,

NEGATABLE has already been specified

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

2-104

Messages

CONFNOCON,

NOCONCATENATE has already been specified

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

NODISALLOWS has already been specified

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

NONNEGATABLE has already been specified

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

NOP ARAMETERS has already been specified

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

NOQUALIFIERS has already been specified

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

2-105

Messages

CONFOUTPUTS,

only one OUTPUTS clause is allowed

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

a parameter has already been defined

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

a qualifier has already been defined

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

conflicting qualifiers

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

conflicting qualifiers

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

conflicting qualifiers, request aborted

Facility: SYSGEN, System Generation Utility
Explanation: The SYSGEN command AUTOCONFIGURE is entered
specifying both the /EXCLUDE and /SELECT qualifiers.
User Action: Reenter the command with only one qualifier.

2-106

Messages

CONFROUTIMG,

only one routine or image clause is allowed

Facility: CDU, Command Definition Utility
Explanation: CDU encountered more than one IMAGE or ROUTINE
clause in a single verb/syntax definition. IMAGE and ROUTINE clauses
are mutually exclusive.
User Action: Edit the CLD file so that each verb/syntax does not contain
more than one IMAGE or ROUTINE clause.
CONNEC, unable to connect to listener
Facility: NCP, Network Control Program
Explanation: NCP is unable to connect to NML to perform network
operations. Information accompanying this message explains any secondary
reasons for this error. Your network may not be configured correctly, your
access control information may be invalid, or all files may not be present.
User Action: If you receive this message upon entering the SET EXECUTOR
NODE command, then you should try the command again after correcting
the problem or after supplying valid access control information. You may
then resume entering NCP commands. Inspect the log file created by NML
on the destination node to see if it provides additional information as to the
cause of the problem.
CONNECFAIL,

connect to network object timed-out or failed

Facility: SYSTEM, VMS System Services
Explanation: The remote node did not respond to the logical-link request.
User Action: Check to see if the node is reachable and retry.
CONSEQERR , a control sequence malfunction is detected
Facility: DTK, DECtalk Facility
Explanation: A DECtalk private control sequence malfunction occurred since
the DECtalk device was turned on.
User Action: Check the DECtalk hardware.
Consistency check failed, please check your file
Facility: EDT, EDT Editor
Explanation: There is a discrepancy between the number of lines and
characters present when the editing session ends. This message indicates
an EDT problem.
User Action: Check for possible errors in your output file. Submit a Software
Performance Report.
CONSTRTOOLARGE,

constant string too large

Facility: VAXTPU, VAX Text Processing Utility
Explanation: A constant declaration includes a constant expression that
exceeds the internal tables of the compiler.
User Action: Use an expression that generates a shorter string.

2-107

Messages

CONTINUE,

unable to continue processing filespec

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

CONTINUED,

save set spec contains a continued file-cannot append

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

CONTRACT,

contract virtual address space error

CONTRADEF,

contradictory definition for variable or constant name

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The variable or constant definition contradicts its previous
definition.
User Action: Rename the variable or constant to a unique name, or change
the definition to match its previous definition.

CONTROLC,

operation aborted by CTRL/C

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

2-108

Messages

CONTROLC,

operation completed under CTRL/C

Facility: SYSTEM, VMS System Services
Explanation: An operation did not finish because CTRL/C is pressed. This
message indicates success.
User Action: None.
CONTROLC,

operation completed under CTRL/C

Facility: RMS, VMS Record Management Services
Explanation: An operation did not finish because CTRL/C is pressed. The
operating system does not normally display this message.
User Action: None.
CONTROLO,

output completed under CTRL/O

Facility: SYSTEM, VMS System Services
Explanation: An output operation to the terminal did not finish because
CTRL/O is pressed. The operating system does not normally display this
message.
User Action: None.
CONTROLO,

operation completed under CTRL/O

Facility: RMS, VMS Record Management Services
Explanation: An operation did not finish because CTRL/O is pressed. The
operating system does not normally display this message.
User Action: None.
CONTROLY,

operation completed under CTRL/Y

Facility: SYSTEM, VMS System Services and RMS, VMS Record
Management Services
Explanation: An operation did not finish because CTRL/Y is pressed. The
operating system does not normally display this message.
User Action: None.
COO,

can't open output file 'filename

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

2-109

Messages

COPIED,

copied 'filespec'

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

input-filespec copied to output-filespec ('nnn' blocks)

Facility: Shared by several facilities
Explanation: The message displays the number of blocks or the number
of blocks copied, based on the size of the input files. This message is
informational.
User Action: None.
COPIEDR, input-filespec copied to output-filespec ('nnn' records)
Facility: Shared by several facilities
Explanation: The message displays the number of records or the number
of records copied, based on the size of the input files. This message is
informational.
User Action: None.
COPMSG,

user record copied

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

copy of log from 'log-filename' follows:

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

end of log file from 'filespec'

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

2-110

Messages

COPY_LOG_LINE,

'text1

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

can't open required file 'filename'

Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: The required file specification is erroneous, or the file is
nonexistent, or you do not have read access to the file.
User Action: Check the file specification for errors, or check to see if you
have read access to the file. If the problem continues, notify the system
manager.
Could not align tabs with cursor
Facility: EDT, EDT Editor
Explanation: The cursor is in a position where it cannot be evenly divisible
by the tab size when the tab compute function is used.
User Action: Change the tab size or cursor position.
CPU ucode not at required rev level for port activity
Facility: VAXport, VAXport Driver
Explanation: The port driver will not attempt to start the port.
User Action: On an 11/750, make sure that the console TU58 is present and
up-to-date. Otherwise, call DIGITAL field service to check the port hardware.
CPUCEASED,

CPU ceased execution

shutdown requested by another CPU

Facility: SMP, Symmetric Multiprocessing
Explanation: The current processor was requested to perform a bugcheck by
another processor in the multiprocessor system.
User Action: This bugcheck occurs as a direct result of a request by another
processor only. Analyze the crash dump to determine which CPU is the
'crash CPU' and the reason why that CPU crashed.

2-111

Messages

CPUNOTVLD,

CPU not booted or CPU ID out of range

Facility: SDA, System Dump Analyzer
Explanation: You specified an invalid CPU ID for the SDA command SET
CPU or SHOW CPU. The CPU ID is invalid either because there is no CPU in
the system with the specified CPU ID, or because the CPU with the specified
CPU ID was never booted and was not active at the time of the system
failure.
User Action: Reenter the command with a valid CPU ID.
CPUSANITY,

CPU sanity timer expired

Facility: SMP, Symmetric Multiprocessing
Explanation: One of the processors in a multiprocessor configuration detected
that another processor that is participating in the SMP environment is no
longer responding to hardware clock interrupts.
User Action: After the system reboots, determine which processor stopped
responding to hardware clock interrupts by analyzing the crash dump
generated by this bugcheck. Further analysis of the crash dump might
show the reason why that CPU was not responding to clock interrupts, for
example, it was looping in a driver at an IPL high enough to block its clock
interrupts. Correct the code that stayed at high IPL for too long.
CPUSPINWAIT,

CPU spinwait timer expired

Facility: SMP, Symmetric Multiprocessing
Explanation: One of the processors in a multiprocessor configuration held
onto a spin lock longer than the permissible period of time. This is detected
by another processor, which is trying to acquire that spin lock during that
time.
User Action: Analysis of the crash dump will show the spin lock that was
held too long and should show the reason that the owning CPU did not
release the spin lock when it should. For example, if the owning CPU had
acquired the spin lock multiple times and subsequently released the spin lock
using the conditional release option of the spin lock unlock macro when it
should have executed a 'total' release of that spin lock, then the owning CPU
will proceed with execution while it is unaware that it still owns the spin
lock. Meanwhile, another CPU that attempts to acquire that spin lock will
eventually time out and generate this bugcheck.
CRC,

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

2-112

Messages

CRCLS,

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

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

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

CREA_ERR,

error creating work file 'filespec'

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

creating temporary directory "dir-name".

Facility: VMSINSTAL, Install Procedures
Explanation: VMSINSTAL creates a temporary directory if you specify the
Get Save Set option. This message is informational.
User Action: None.
CREATE,

error creating output file

Facility: FDL, Create/FDL Utility and FDL, Edit/FDL Utility
Explanation: This message will be accompanied by a VMS RMS error
message that explains the error.
User Action: Correct the error described in the VMS RMS error message and
try again to create an output file.
CREATED,

file does not exist-is created

Facility: RMS, VMS Record Management Services
Explanation: File is created when the CREATE_JF option is specified. This
message indicates success.
User Action: None.

2-113

Messages

CREATED,

file is created, not opened

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

'filename' created

Facility: DSR, DIGITAL Standard Runoff
Explanation: Indicates that an output file has been created.
User Action: None.
CREATED,

'filespec' created

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The file was successfully created.
User Action: None.
CREATED,

'filespec' created

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

file/section/resource did not exist-is created

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

User Action: None.
CREATED,

requested item is created

Facility: PPL, Parallel Processing Facility
Explanation: The requested item is created. An alternate success status
indicates that the item is not found.
User Action: Continue normally.

2-114

Messages

CREATED_SOME , created some of those requested-partial success
Facility: PPL, Parallel Processing Facility
Explanation: Some, but not all, of the requested items were created.
User Action: If processing can continue with fewer items than those
requested, then continue normally.
CREATEDSTM,

'filespec' has been created in stream format

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

unable to activate subprocess

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

error creating directory [SYSLOST]

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

error creating the virtual volume 'volume'

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

created directory 'directory-name'

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

2-115

Messages

CREDIRERR,

error creating directory 'directory-name'

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

CREERR,

unable to create SYSUAF.DAT

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

CREJOB,

error opening job 'job-name' for user 'user-name' in queue 'queue-name'

Facility: JBCUPGRAD, Queue Upgrade Utility
Explanation: An error occurred during a $SNDJBC system service call
attempting to create a job. This job and the information about its files are not
restored during the upgrade.
User Action: The accompanying message gives information about why the
operation failed. Attempt to correct the problem and retry the upgrade, or,
after the upgrade, print or submit the job as originally desired using the DCL
command PRINT or SUBMIT.

CREJOB,

error creating job

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

CRENEWFOLD,

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

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

CREP ARFIL,

unable to create parameter file

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

2-116

Messages

CREPRC,

process creation failed

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

error creating process for batch job

Facility: JBC, Job Controller
Explanation: The job controller was unable to create a process for the
execution of a batch job. Usually, this indicates a lack of system resources,
such as process slots, needed to complete the $CREPRC system service
request.
User Action: Resubmit the batch job. If the condition persists, contact your
system manager.
CREPRIJOB,

error creating print job on queue 'queue-name'

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

error creating queue 'queue-name'

Facility: JBCUPGRAD, Queue Upgrade Utility
Explanation: An error occurred during a $SNDJBC system service call
attempting to create a queue. This queue, its jobs, and information about its
files are not restored during the upgrade.
User Action: The accompanying message gives information about why the
operation failed. Attempt to correct the problem and retry the upgrade,
or after the upgrade has completed, enter the DCL command INITIALIZE
/QUEUE as originally desired. If the queue contained jobs waiting for
execution, the CREJOB message should also appear during the upgrade.
CRE_STM, file is created in stream format
Facility: RMS, VMS Record Management Services
Explanation: VMS RMS created the file in stream format with embedded
carriage control instead of using the record format (RFM field) and carriage
control (RAT field) type specified in the VMS RMS $CREATE call. This file
format conversion is performed because the remote DECnet system only
supports stream format files. This message indicates success.
User Action: None.

2-117

Messages

CRF,

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

CRFERR,

error encountered in Cross Reference

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

CRMPSC system service failed to map global buffers

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

error code of 'xx' mapping section

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

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

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

2-118

Messages

CTRLCEXIT,

exit now to avoid journal file inconsistency

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

CTRLCHAR,

the following line contains control characters-ignored

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

CTRLCJOU,

CTRL/C may have invalidated the journal file

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

CTRLERR,

disk boot driver virtual circuit failure

Facility: VAXCLUSTER, VAXcluster Facility
Explanation: The satellite could not establish a virtual circuit to the MSCP
server on the boot node or received a hardware error during communications.
User Action: Check that the MSCP server is loaded on the boot node, verify
the CLUSTER_AUTHORIZE.DAT file, and look for hardware errors on the
boot node's system disk and PE/Ethernet port.

CTRLERR,

fatal controller error

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

•
•
•
•
•
•
•
•

Late data
Error confirmation
Invalid map register
Interface timeout
Missed transfer
Programming error
Read timeout
RXOl switch set incorrectly (RX02 only) (disk driver specific)

2-119

Messages

If this message is associated with a status code returned by a request to a
DRll-W interface, a fatal error that affects all DRll-W activity is set in the
DRl 1-W CSR on completion of the QIO request. Look at the third and fourth
words of the IOSB (CSR and EIR) for the specific cause of the error. If the
condition indicated in the CSR can be cleared, that is, if the ATTN bit can
be cleared, SS$_DRVERR is returned. If the condition cannot be cleared,
SS$_CTRLERR is returned. In both cases, the driver performs a device reset
to the DRl 1-W.
If this message is associated with a status code returned by a request to a

DR32 interface, a fatal hardware malfunction occurred that stops all DR32
activity. (Only for start data transfer functions.) The second longword of the
IOSB contains additional information pertaining to this error; the following
bit values are associated with SS$_CTRLERR:
XF$V_IOS_INVPTE
XF$V_IOS_SBIERR
XF$V_IOS_RDSERR
If this message is associated with a status code returned by a request to a

DMC/DMR device, it can occur for one of the following reasons:
•

NAK threshold errors exceeded

•

Time out on response from remote end

•

Buffer not available

•

·Maintenance message received in RUN mode

•

Message too long to fit in receiver buffer

•

Modem has disconnected

•

Start message is received in run mode

•

Nonexistent memory error

•

Halt to DMC/DMR is complete

If this message is displayed, restart the DMC/DMR device.
If this message is associated with a status code returned by a LPAll-K driver,

it is a fatal error that affects all LP A 11-K activity. The LP A 11-K terminates all
active requests. The third and fourth words of the IOSB contain the LPAl 1-K
Ready-Out Status Register and Maintenance Register contents. In particular,
the high byte of the third word contains the specific LPAl 1-K error code.
If this message is associated with DEUNA hardware, on a STARTUP request

the startup failed because of bad error return from the DEUNA hardware. On
a read request, the hardware returned a zero-length message.
User Action: Action depends on the type of device to which the I/O request
is directed. If the failure is on STARTUP, then the DEUNA should be
checked by running UETP or DIGITAL field service should run the DEUNA
diagnostics. If the failure is on a read request and the protocol has enabled
PADDING, then the remote software module should be corrected to stop
sending zero-length messages.
If the failure persists, notify the system manager.

2-120

Messages

CTRLY, installation cancelled via CTRL/Y.
Facility: VMSINSTAL, Install Procedures
Explanation: You canceled the installation by entering CTRL/Y. This
message is informational.
User Action: None.

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

CUREXEC, current executor node name 'node-name'
Facility: NCP, Network Control Program
Explanation: This message is output after an NCP SET EXECUTOR NODE
command is entered, and the command failed, or if an established link
to another executor failed. It indicates the name of the node that NML is
treating as the executor. This message is informational.
User Action: None.

CVTERR,

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

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

CVTERR, error converting to decimal value, 1value 1
Facility: ERF, Error Log Utility
Explanation: An attempt is made to convert a value to decimal resulting in
an error.
User Action: Submit a Software Performance Report.

CVTUNGRANT,

cannot convert an ungranted lock

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

2-121

Messages

CWF,

can't write footnote file (N)

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

DAC,

ACP file deaccess failed during $CLOSE

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

DAN,

invalid data area number for key = 'nnn'

Facility: RMS, VMS Record Management Services
Explanation: The data area number specified in a key definition XAB is not a
defined area for the file.
User Action: The status value (STV) field of the FAB provides the key of
reference of the XAB in error. Verify that the call to the VMS RMS service is
coded correctly.

DATACHECK, write check error
Facility: SYSTEM, VMS System Services
Explanation: The data in memory did not match the data on disk during a
data check operation. If this message is associated with a status code returned
by a LPAll-K driver, a mismatch between the microcode in memory and
the microcode loaded into the LPAll-K is detected. The second word of the
IOSB contains the number of bytes successfully loaded.

Another possible explanation is that the DEUNA hardware detected a late
collision on a write request.
User Action: Note the condition. If necessary, modify the source program to
detect and respond to the condition. This message may indicate a hardware
error. Check the Ethernet cable and all Ethernet controllers for proper
operation. If the error persists, notify the system manager.

DATADEVERR,

data error on 'device-name' byte 'location' good data= 'xx' bad
data= 'xx'

2-122

Messages

DATAER,

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

Facility: UETP, User Environment Test Package
Explanation: One of the UETP tests detected a difference between the data
that is written from memory and the same data after it is read back into
memory. The 'location' is the offset from the start of the buffer where the
first difference is seen.
User Action: Investigate the device or mechanism that caused the error.
Datagram Free Queue Insert Failure
Facility: VAXport, VAXport Driver
Explanation: The VAXport driver attempts to reinitialize the port; after 50
failed attempts, it marks the device off line. This error is caused by a failure
to obtain access to an interlocked queue. Possible sources of the problem are
CI hardware failures or memory, SBI (11/780), CMI (11/750), or BI (8200,
8300, and 8800) contention.
User Action: Call DIGITAL Field Service.
Datagram Free Queue Remove Failure
Facility: VAXport, VAXport Driver
Explanation: The VAXport driver attempts to reinitialize the port; after 50
failed attempts, it marks the device off line. This error is caused by a failure
to obtain access to an interlocked queue. Possible sources of the problem are
CI hardware failures or memory, SBI (11/780), CMI (11/750), or BI (8200,
8300, and 8800) contention.
User Action: Call DIGITAL Field Service.
DATALSTSYN,

data list syntax error

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

data overrun

Facility: SYSTEM, VMS System Services
Explanation: This message can indicate the following:
•

More data is read into the user buffer than the user buffer can hold.

•

More data is written into the user buffer than the user buffer can hold.

•

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

If this message is associated with a status code returned by a request to a
magnetic tape driver, the data block read is longer than the assigned buffer.
In the case of a read reverse .operation, the last data on the tape (that is, the

2-123

Messages

data nearest the end-of-tape at the beginning of the operation) is the first data
read. This data is in the buffer.
User Action: Specify a larger buffer if the data is too much for the existing
buffer. If the problem occurred on a card reader operation, resubmit the cards
to the card reader. You can also use the DCL command SET TERMINALE
/ALT to turn on the alternate typeahead buffer. Then increase the typeahead
buffer size or the alternate typeahead buffer size, or both, by modifying the
TTY SYSGEN parameters.
DATAOVFL,

data area overflow in section-please submit SPR

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

data truncation error

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

component database created

Facility: SYSMAN, Cluster System Management Utility
Explanation: The specified STARTUP component database is created.
User Action: None.
DATMISMCH,

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

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

length of new data may not exceed length of old data

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

2-124

Messages

DBCORRUPT,

component database is corrupt

Facility: SMI, System Management Intergator/Server
Explanation: The startup component database is corrupt.
User Action: Verify that the file being used is a component database and that
the file has not been edited or otherwise modified. If the problem still exists,
submit a Software Performance Report and include the component database.
DBGERR, internal debugger coding error; DEBUG base address: 'address_value'
DEBUGSHR base address: 'address_value'
Facility: DEBUG, VMS Debugger
Explanation: An internal debugger coding error has been encountered.
User Action: If the error is reproducible, submit a Software Performance
Report and, if possible, enclose both a copy of the program being debugged
and a logged debugging session that reproduces the error.
DBGTFR,

image 'image-name' has no Debugger transfer address

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

double error halt restart

Facility: BUGCHECK, System Bugcheck
Explanation: The VMS software detected an irrecoverable hardware error.
Because of the severity of the error, further operation is impossible; or if it is
possible, it may corrupt user data. After all of physical memory is written to
a system dump file, the system will automatically reboot if the BUGREBOOT
system parameter is set to 1.
User Action: Thoroughly test all system hardware components. If no
hardware errors are located and if the problem persists, submit a Software
Performance Report. The SPR should describe the conditions at the time
of the error, and should include a BACKUP save set containing the system
dump file and the error log file active at the time of the error. (Use the
/IGNORE=NOBACKUP qualifier on the BACKUP command to produce the
save set.)
DDIFIN,

'count' line(s), 'count' frame(s) read from file 'filename'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: VAXTPU opened the named DDIF file and read the indicated
number of lines and frames from that file into a buffer.
User Action: None.

2-125

Messages

DDIFOUT,

'count' line(s), 'count' frame(s) written to file 'filename'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: VAXTPU wrote the indicated number of lines and frames from
a buffer into the named DDIF file.
User Action: None.
DEADLOCK,

deadlock detected

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

breakpoint at line 'integer'

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

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

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

your DECnet network is up and running.

Facility: VMSINSTAL, Install Procedures
Explanation: When VMSINSTAL begins an installation, it makes sure that
your DECnet network has been shut down. This check failed. VMSINSTAL
asks if you want to continue the installation.
User Action: DIGITAL recommends that you correct this situation before
continuing.
DECOVF, arithmetic trap, decimal overflow at PC= 'xxxxxxxx', PSL = 'xxxxxxxx'
Facility: SYSTEM, VMS System Services
Explanation: A decimal overflow caused an arithmetic overflow condition.
User Action: Examine the PC location displayed in the message and check
the program listing to verify that operands or variables are specified correctly.

2-126

Messages

DECOVF,

decimal overflow

Facility: LIB, Library Facility
Explanation: During an arithmetic operation, a decimal value exceeds the
largest representable decimal number. The result of the operation is set to the
correctly signed least significant digit.
User Action: None.
DECPTREF,

decrement page table reference count error

entity defaulted present in command string

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

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

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

2-127

Messages

DEFCHARSTIC,

error defining characteristic: name 'characteristic-name', number
'characteristic-number'

Facility: JBCUPGRAD, Queue Upgrade Utility
Explanation: An error occurred during a $SNDJBC system service call
attempting to define characteristics. The definition for this characteristic is not
restored during the upgrade.
User Action: The accompanying message gives information about why the
operation failed. Attempt to correct the problem and retry the upgrade, or
after the upgrade, enter the DCL command DEFINE/CHARACTERISTIC as
originally desired.

DEFERR, unable to obtain DEFAULT record
Facility: AUTHORIZE, Authorize Utility
Explanation: This message is issued with other messages.
User Action: Take corrective action based on the accompanying messages.

DEFFORM,

error defining form: name 'form-name', number 'form-number'

Facility: JBCUPGRAD, Queue Upgrade Utility
Explanation: An error occurred during a $SNDJBC system service call
attempting to define a form. The definition for this form was not restored
during the upgrade.
User Action: The accompanying message gives information about why the
operation failed. Attempt to correct the problem and retry the upgrade, or
after the upgrade, enter the DCL command DEFINE/FORM as originally
desired.

DEFFORUSE,

default format used, could not determine user's preference

Facility: LIB, Library Facility
Explanation: Translation of LIB$DTJORMAT failed and the VMS standard
representation is used.
User Action: Examine and make corrections to the logical LIB$DT_FORMAT.

DEFKEY,

'state' key 'key-name' has been defined

Facility: CU, Command Language Interpreter (DCL)
Explanation: The specified key is defined.
User Action: None.

DEFOVF, too many command procedure parameters-limit to eight
Facility: CU, Command Language Interpreter (DCL)
Explanation: A command procedure is invoked with more than eight
parameters.
User Action: Reenter the command; do not specify more than eight
parameters.

2-128

Messages

DEFPWD,

Warning: copied or renamed records must receive new password

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

RF A-accessed record is deleted

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

file protection does not allow delete access

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

fatal error in delete contents of PFN

error deleting data from 'library-filespec'

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

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

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

2-129

Messages

DELETE,

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

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

'filename' deleted

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

module 'module name' deleted from 'library filespec'

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

previous Known File Entry has been deleted

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

unable to terminate subprocess

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

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

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

2-130

Messages

DELEXIGBL,

termtable section already exists

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

delete global section error

delete global section window error

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

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

'state' key 'key name' has been deleted

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

2-131

Messages

DELKEYERR,

error deleting 'module-name' from 'library filespec'

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

DELSYM,

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

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

DEL TIMREQ,

delta time required, absolute time supplied

Facility: LIB, Library Facility
Explanation: An absolute time is passed to the routine when a delta time is
required.
User Action: Examine each argument and change the delta time to absolute
time.

DEL TVA,

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

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

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

DELWSLEX,

delete working set list entry index error

2-132

Messages

DENOSU,

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

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

DENSITY,

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

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

DEQSUBLCKS,

tried to dequeue lock with sublocks

DESSTROVF,

destination string overflow

Facility:- LIB, Library Facility
Explanation: The destination string is overflowed, and the operation did not
justify return of a warning, but a fatal error.
User Action: Increase the length of the destination string, or use dynamic
string for destination.

Destination for MOVE or COPY not found
Facility: EDT, EDT Editor
Explanation: The range specification in the command does not exist.
User Action: Reenter the command specifying an existing range.

DESTP,

'testname' stopped testing 'controller' unit 'number' at 'time'

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

2-133

Messages

DEUNUS,

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

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

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

DEVACTIVE,

device is active

Facility: SYSTEM, VMS System Services
Explanation: If this message is associated with a status code returned by a
request to a DR32 interface, the microcode cannot be loaded because there is
an active data transfer request (only for the load microcode function).
If this message is associated with a status code returned by a request to
an LP All-K driver, the microcode cannot be loaded or the microprocessor
cannot be started because there is an active data transfer request.
If this message is associated with a status code returned by a request to
a DRll-W interface, the DRll-W controller is occupied with a request
from another process. The operating system does not normally display this
message.
User Action: Note the condition. Modify the source program, if necessary, to
detect and respond to the condition.

2-134

Messages

DEVALLOC,

device already allocated to another user

Facility: SYSTEM, VMS System Services
Explanation: An attempt to allocate a device failed because the device is
allocated by another user or channels are assigned to it. Only one user at a
time can access an allocated device.
Or, on a startup request, the user attempted to start the protocol as a shared
default user, when a shared default user already exists for that protocol type.

User Action: Wait until the current owner has deallocated the device, or
reenter the request specifying a different device of the same type, or specify a
generic device name in the allocate request.
The user must not attempt to bring up two SHARED DEFAULT users until
the first user is stopped.
DEVALLOC,

device 'device-name' already allocated to another user.

Facility: VMSINSTAL, Install Procedures
Explanation: In response to the prompt Where will the distribution volumes
be mounted? you specified a device that is allocated to another user. You will
be asked to specify another device.
User Action: Specify a device name that is not allocated to another user.
DEVALRALLOC,

device already allocated to this job

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

device already spooled

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

device has channels assigned

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

2-135

Messages

DEVCLASS,

device class of SYS$INPUT must be terminal

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

DEVCMDERR,

device command error

Facility: SYSTEM, VMS System Services
Explanation: The exact meaning depends on the device. If this message is
associated with a status code returned by a request to an LPAll-K driver
(only for the initialize LPAll-K, set clock, and start data transfer request
functions), it is associated with the issuance of a new LPAll-K command.
The third and fourth words of the IOSB contain the LPAll-K Ready-Out
Status Register and Maintenance Register contents. In particular, the high
byte of the third word contains the specific LPAll-K error code.
User Action: Action depends on the type of device to which the IjO request
is directed.
DEVCOUNT, number of devices must match number of volumes
Facility: MOUNT, Mount Utility
Explanation: The number of devices specified in the DCL command MOUNT
to mount a disk volume set did not match the number of volume labels
specified in the command.
User Action: Check the command line. Verify the names of the devices
and volume labels for the command and then reenter the command with a
matching number of devices and volume labels.
DEVFOREIGN,

device is mounted foreign

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

devices

2-136

Messages

DEVICEFULL,

device full-allocation failure

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

only one device allowed

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

device inactive

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

device device-name will be mount-status

Facility: VMSINSTAL, Install Procedures
Explanation: The device that you specified for the output of the Get Save Set
option is initialized (if it is a disk) and mounted. This message appears only if
the output device you specified is not mounted when VMSINSTAL is started.
This message is informational.
User Action: None.
DEVMOUNT,

device is already mounted

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

2-137

Messages

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

'device' is not a block structured device

Facility: BAD, Bad Block Locator Utility
Explanation: This message indicates a fatal error. You attempted to perform
an analysis of media that is not block structured.
User Action: Do not use the ANALYZE/BAD command with this device.
DEVNOTERM,

illegal source operator device

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

device 'device-name' does not exist.

Facility: VMSINSTAL, Install Procedures
Explanation: The device you specified for the output of the Get save set
option does not exist.
User Action: Specify a valid device name.
DEVNOTFOR,

'device-name' is not mounted foreign

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

device not mounted foreign

Facility: CLI, Command Language Interpreter (DCL)
Explanation: An operation is requested for a device that must be mounted
foreign to perform the operation.
User Action: If the device is not mounted, then mount it foreign; if the
device is mounted, dismount it and remount it foreign.
DEVNOTKNWN, unable to locate datalink driver
Facility: VAXCLUSTER, VAXcluster Facility
Explanation: You are attempting to boot a satellite using an unsupported
ethernet adapter.
User Action: Check for an unsupported Ethernet adapter on the satellite.

2-138

Messages

DEVNOTKNWN,

unable to locate disk boot driver

Facility: VAXCLUSTER, VAXcluster Facility
Explanation: This message indicates an internal error in the NISCS bootstrap.
User Action: Submit a Software Performance Report or contact the
Telephone Support Center.
DEVNOTKNWN,

device not known: 'input'

Facility: SYSGEN, System Generation Utility
Explanation: The specific device is unknown when you entered the SYSGEN
command CONFIGURE.
User Action: See VMS Device Support Manual for the correct UNIBUS
controller name.
DEVNOTMBX,

device is not a mailbox

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

device is not mounted

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

device not spooled

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

the device 'device-name' is not suitable for operations

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

2-139

Messages

DEVOFFLINE,

device is not in configuration or not available

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

device is off line

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

'date and time', Device 'device-name' is off line Mount verification
in progress

Facility: OPCOM, Operator Communication
Explanation: The device is off line and mount verification is in progress. All
1/0 requests are stalled.
User Action: Cancel the mount verification or bring the volume back on line.
DEVONLINE,

device on line

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

using device name only, ignoring parts of 'filespec'

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

invalid qualifier for device type

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

2-140

Messages

DEVRCT,

unable to analyze 'device-name', due to revector caching

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

DEVREQERR, device request error
Facility: SYSTEM, VMS System Services
Explanation: The exact meaning depends on the device. If this message
is associated with a status code returned by a request to a DR32 interface,
a programming error or an error associated with the far end DR-device is
indicated. The second longword of the 1/0 status block contains additional
information pertaining to the error; the following bit values are associated
with SS$_DEVREQERR:

XF$V_IQS_DDIDIS
XF$V_IOS_RNGERR
XF$V__IOS_UNQERR
XF$V__IOS__INVPKT
XF$V__IOSJREQMT
XF$V__IOS_INVDDI
XF$V_IOS_LENERR
XF$V_IOS_DDIERR
If this message is associated with a status code returned by a request to
an LPAll-K driver, it indicates an LPAll-K user request error for a start
data transfer request. The third and fourth words of the IOSB contain the
LP A 11-K Ready-Out Status Register and Maintenance Register contents. In
particular, the high byte of the third word contains the specific LPAll-K error
code.

On a write request, the DEUNA failed to transmit the message after 16
attempts.
User Action: Action depends on the type of device to which the I/O request
is directed.

The Ethernet cable may have short-circuited, or it may have been temporarily
overloaded. In either case, the Ethernet cable should be checked and if it is
operational, the user may wish to send packets again. However, it must be
noted that if these kinds of errors persist, the Ethernet is overloaded.
DEVSELREQ, device selection required
Facility: ERF, Error Log Utility
Explanation: A device type or class must be selected.
User Action: Use the DCL command HELP or refer to the VMS DCL
Dictionary to determine the appropriate qualifier for selecting a device type or
class. Then reenter the command.

2-141

Messages

DEVSPEC,

input specification for non-file-structured dump must contain only
device

Facility: DUMP, File Dump Utility
Explanation: The input file specification can contain only the device
component if the input medium is not a disk or tape device or if it is mounted
with the /FOREIGN qualifier.
User Action: Correct and reenter the command.
DEVWRTLCK,

'date and time', Device 'device-name' has been write locked.
Mount verification in progress

Facility: OPCOM, Operator Communication
Explanation: A write request to a Files-11 disk has failed because the device
is not mounted write-locked.
User Action: Cancel the mount verification, or remove the write lock on the
volume.
DFL,

data bucket fill size larger than bucket size for key= 'nnn'
Facility: RMS, VMS Record Management Services
Explanation: The data bucket fill size specified in a key definition XAB
exceeds the bucket size for the data area.
User Action: The status value (STV) field of the FAB provides the key of
reference of the XAB in error. Verify that the call to the VMS RMS service is
coded correct! y.

DGQINCOMP,

datagram queue operation incomplete

Facility: SYSTEM, VMS System Services
Explanation: A request to remove a certain number of datagrams from a
queue succeeded only partially because there were fewer entries available
than requested. This warning message should not appear.
User Action: None.
DIAGNOSTIC,

job controller read record limit exceeded

Facility: JBC, Job Controller
Explanation: The job controller keeps count of the number of read operations
required to process a request. If the number exceeds a maximum value, the
job controller considers this to be a looping condition and proceeds to abort
and restart itself. This message is displayed on the operator's terminal. The
event is usually caused by a corrupted queue file, though it may indicate an
internal job controller error.
User Action: Enter a STOP /QUEUE/MANAGER command to close the
queue file. If you have a cluster, do this on all nodes. Next, enter a START
/QUEUE/ MANAGER command on one node. This will open the queue
file and cause the job controller to perform a "cold start validation" of the
file. If the queue file fails the test, create a new queue file before enabling
Batch/Print facilities on the system.

2-142

Messages

DIAGP ACK,

disk is a diagnostic pack

Facility: INIT, INITIALIZE Command,BACKUP, Backup Utility
Explanation: Either the DCL command INITIALIZE is entered to initialize a
volume that is identified as a diagnostic volume, or a Backup Utility operation
is attempted using a volume identified as a diagnostic volume. In either case,
the volume cannot be used.
User Action: Retry the operation using another volume.
DIALINNOT,

diagonal line not allowed

Facility: SMG, Screen Management Facility
Explanation: The vertices specified will result in a diagonal, rather than
vertical or horizontal, line.
User Action: Specify the vertices so that the line drawn will be vertical or
horizontal.
DIFACCTS,

values are 'account-name' and 'account-name'

Facility: JBCUPGRAD, Queue Upgrade Utility
Explanation: This message follows the COMPFAIL message and specifies the
values (for the 'account-name' field of the job) in each of the two queue files
being compared.
User Action: If the specified difference is undesirable, make appropriate
changes.
DIFCHARS,

values are 'number', 'number', 'number', 'number' and 'number',
'number', 'number', 'number'

Facility: JBCUPGRAD, Queue Upgrade Utility
Explanation: This message follows the COMPFAIL message and specifies
octaword values for the 'characteristics' field of the queue or job in each of
the two queue files being compared.
User Action: If the specified difference is undesirable, make appropriate
changes.
DIFLWDS, values are 'longword' and 'longword'
Facility: JBCUPGRAD, Queue Upgrade Utility
Explanation: This message specifies the longword values for the field
identified by the 'type-of-field' in the COMPFAIL message that precedes
this message.
User Action: If the specified difference is undesirable, make appropriate
changes.

2-143

Messages

DIFSTRINGS,

values are 'character-string' and 'character-string'

Facility: JBCUPGRAD, Queue Upgrade Utility
Explanation: This message specifies the different character string values for
the field identified by 'type-of-field' in the COMPFAIL message that precedes
this text.
User Action: If the specified difference is undesirable, make appropriate
changes.
DIFTIMES,

times are 'date-and-time' and 'date-and-time'

Facility: JBCUPGRAD, Queue Upgrade Utility
Explanation: This message follows the COMPFAIL message and specifies the
different values for the 'after-time' field of the job in each of the two queue
files being compared.
User Action: If the specified difference is undesirable, make appropriate
changes.
DIFTYP,

expected 'library-type' 'library-spec.' to be 'library-type'

Facility: LIBRAR, LIBRARY Command
Explanation: This warning message is generated by the DCL command
LIBRARY. The referenced library is actually of a different type from that
indicated in the command string. Processing continues based on the actual
library type.
User Action: None.
DIFVAL,

memory contains different value than specified

Facility: PATCH, Patch Utility
Explanation: The value specified is not contained within the given memory
location.
User Action: Correct the value and retry the operation.
DIGITAL Standard Runoff Version V3.0: 'number' diagnostic messages reported

Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: This is a standard error message line that specifies the actual
number of error messages output.
User Action: For more information refer to the specific error messages
accompanying this message.
DIGITAL Standard Runoff Version V3.0: No errors detected

Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: This message indicates the successful processing of a file by
DSR.
User Action: None.

2-144

Messages

DIR,

error in directory name
Facility: RMS, VMS Record Management Services
Explanation: A directory name is specified incorrectly. For example, a
directory or subdirectory name string contained more than 39 characters. Or,
use of a logical name resulted in more than one directory name in the file
specification.
User Action: Verify the syntax of either the directory name in the file
specification or the logical name, if a logical name is specified.

DIRALLOC, directory allocation failure
Facility: SYSTEM, VMS System Services
Explanation: The file system failed to allocate space to increase the size of
a directory file. Because directory files must be contiguous, this error might
be caused by the disk being full. More likely, there is not enough contiguous
space on the disk for the directory, so the free disk space is being fragmented.
User Action: Reorganize the free disk space by copying it with the Backup
Utility, or restructure your application to use a larger number of smaller
directories.

DIRECT, invalid directory syntax-check brackets and other delimiters
Facility: CU, Command Language Interpreter (DCL)
Explanation: The directory name in a file specification entered for a
command contains an illegal character; or a command that expects a directory
name string did not find square brackets ([ ]) or angle brackets ( < > ) in
the specified parameter. Note that this error can occur if a physical device
name is specified without a colon following it. This error can also occur
with VMS Version 4.4 or higher if you use Version 3.7 syntax to specify a
concealed device (for example, using DUAO: instead of /TRANSLATION_
CONCEALED).
User Action: Examine the directory name (or logical name, if a logical name
is specified). Correct the directory syntax and reenter the command.

DIRE_ERROR,

above error occurred writing directory, volume might be
corrupted

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility encountered an error writing the directory
of the volume. A more specific error message is printed immediately before
this message.
User Action: Since EXCHANGE might have already modified the volume
in some way, it is possible that the directory stored on the volume does not
match the current contents of the volume. It is possible to save all the files
by creating a virtual volume and copying all files from the possibly corrupted
volume. Note that this copy must be made before exiting EXCHANGE.

2-145

Messages

DIRENTRY,

ACP failed to find same directory entry

directory is full

Facility: SYSTEM, VMS System Services
Explanation: An error occurred while a disk file is being created because the
directory specified is full and cannot catalog any more entries. The maximum
size of a directory file is 1024 blocks.
If associated with a DECnet-VAX operation, this message indicates that the
directory of declared network names is full.

User Action: Delete or purge unwanted files from the directory and repeat
the request; specify a different directory for the output file; or organize the
directory into subdirectory levels to obtain more cataloging space. You can
also use the BACKUP and RESTORE commands on the directory tree.
DIRNAME,

directory file 'filespec' is not named '.DIR;l'

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the specified file is marked with
the DIRECTORY file characteristic, but it did not have a file type of DIR and
a version number of 1. VMS RMS cannot recognize the file as a directory.
User Action: Use the DCL command RENAME to rename the file.
DIRNOTCRE,

'output file' directory file not created

Facility: Shared by several facilities
Explanation: A request to create a directory file over the network has failed.
The creation of directory files over the network is currently unsupported.
User Action: None.
DIRNOTEMPTY,

directory file is not empty

Facility: SYSTEM, VMS System Services
Explanation: The directory you attempted to delete cannot be deleted
because it contains files.
User Action: Be certain that you want to delete the directory. Then, delete
all the files in the directory first. If the directory is corrupted, use the DCL
command SET FILE/NODIRECTORY to remove its status as a directory.

2-146

Messages

DIRSYNX, directive syntax error
Facility: MACRO, VAX MACRO Assembler
Explanation: The directive contained a syntax error.
User Action: Correct the syntax of the directive.
DISCON,

error disconnecting link to listener

Facility: NCP, Network Control Program
Explanation: An error occurred while disconnecting the link to NML.
Information accompanying this message explains any secondary reasons
for this error.
User Action: Take corrective action based on the accompanying information.
DISCONNECT,

process is disconnected from requested interrupt vector

Facility: SYSTEM, VMS System Services
Explanation: A connection is already outstanding for the device, or the driver
cannot reallocate AST control blocks quickly enough. The latter condition can
occur because insufficient AST control blocks (P6 argument) were specified,
not enough pool space is available for the requested AST control blocks, or
the process ASTCNT quota is exhausted.
On a write request, a loss of carrier signal is detected on the Ethernet cable.
User Action: Check the Ethernet cable for proper operation. Check the
DEUNA hardware for proper operation. Check the H400 or other Ethernet
transceiver for proper operation.
DISKCLASS,

fatal error detected by Disk Class driver (DUDRIVER)

free space on 'device-name' is too fragmented

Facility: BACKUP, Backup Utility
Explanation: The number of free extents on the specified volume is
unreasonably large. The volume cannot be used as a save set disk.
User Action: Reinitialize the volume or select another volume and retry the
operation.

2-147

Messages

DISKS,

disks

all of the volumes have been dismounted

Facility: MOUNT, Mount Utility
Explanation: All of the volumes mounted by this invocation of $MOUNT or
the MOUNT command have been dismounted because of errors that were
detected after the volumes had been mounted. Messages explaining the
nature of the error that forced the dismount usually precede this message.
User Action: Take the corrective measures mandated by the error messages
preceding DISMAL, and reenter the MOUNT request.
DISMOUNTD,

volume 'volume-name' of volume-set 'volume-set-name'
dismounted

Facility: MOUNT, Mount Utility
Explanation: The specified volume of the specified volume set has been
dismounted because of errors encountered in processing the volume after it
is mounted. An error with part of a volume set causes the entire volume set
to be dismounted. This message appears for each member of the volume
set that is dismounted due to the error condition. Only those volumes that
were mounted by this invocation of the MOUNT command are listed. If the
volume set name is not available, the string "name n/ a" appears as the name
of the volume set.
A message describing the error that caused the volume to be dismounted
usually precedes this message.
User Action: Correct the error condition specified in the accompanying
message and reenter the MOUNT command.
DISMPART,

some of the volumes have been dismounted

Facility: MOUNT, Mount Utility
Explanation: Some, but not all, of the volumes that were mounted by
this invocation of the Mount Utility or the MOUNT command have been
dismounted due to errors detected after the volumes had been mounted.
Preceding messages explain the nature of the error that forced the dismount.
Also preceding this message is a list of the volumes that were dismounted.
User Action: Take the corrective measures mandated by the error messages
preceding DISMPART, and reenter the MOUNT request.

2-148

Messages

DISPCHARSTIC, error obtaining information about definition for characteristic:
name 'characteristic-name', number 'characteristic-number'
Facility: JBCUPGRAD, Queue Upgrade Utility
Explanation: This message was encountered during a wildcard $GETQUI
system service call attempt to display characteristics information. The
information for this characteristic is not stored during the upgrade, hence
it is lost after the upgrade.
User Action: The accompanying message gives information about why the
operation failed. Correct the problem and retry the upgrade.

DISPERR,

error during display or summary output

Facility: MONITOR, Monitor Utility
Explanation: An error occurred while displaying the requested MONITOR
data to the SYS$0UTPUT device, or while performing output operations to
the summary file. To obtain more information, examine the accompanying
linked message.
User Action: Correct the error indicated by the linked message and rerun
the MONITOR command. Usually, this message represents a status
value returned to MONITOR from one of the Run-Time Library terminalindependent screen procedures.

DISPFILE, error obtaining information about file 'filespec' in job 'job-name' for
user 'user-name' in queue 'queue-name'
Facility: JBCUPGRAD, Queue Upgrade Utility
Explanation: An error was encountered during a wildcard $GETQUI system
service call attempting to display file information. The information for this
file is not stored during the upgrade, hence it is lost after the upgrade.
User Action: The accompanying message gives information as to why the
operation failed. Correct the problem and retry the upgrade.

DISPFORM,

error obtaining information about definition for form: name 'formname', number 'form-number'

Facility: JBCUPGRAD, Queue Upgrade Utility
Explanation: An error was encountered during a wildcard $GETQUI system
service call attempt to display form information. The information for this
form is not stored during the upgrade, hence it is lost after the upgrade.
User Action: The accompanying message gives information about why the
operation failed. Correct the problem and retry the upgrade.

DISPJOB, error obtaining information about job 'job-name' for user 'user-name'
in queue 'queue-name'
Facility: JBCUPGRAD, Queue Upgrade Utility
Explanation: An error was encountered during a wildcard $GETQUI system
service call attempt to display job information. The information for this
job and its files are not stored during the upgrade, hence it is lost after the
upgrade.
User Action: The accompanying message gives information about why the
operation failed. Correct the problem and retry the upgrade.

2-149

Messages

DISPQUE,

error obtaining information about definition for queue 'queue-name'

Facility: JBCUPGRAD, Queue Upgrade Utility
Explanation: An error was encountered during a wildcard $GETQUI system
service call attempt to display queue information. The information for this
queue, its jobs and their files are not stored during the upgrade and are lost
after the upgrade.
User Action: The accompanying message gives information about why the
operation failed. Correct the problem and retry the upgrade.
DISREQ,

DISPLAY_ID parameter must be specified.

Facility: SMG, Screen Management Facility
Explanation: A call to SMG$READ_VERIFY is made specifying rightjustification, no DISPLAY_ID is specified, and the SCROLL-REVERSE
sequence is not found for this terminal in TERMTABLE.EXE. Since rightjustification requires a cursor positioning sequence to work properly, either
the DISPLAY_ID parameter must be specified or the SCROLL_REVERSE
sequence must be added to TERMTABLE.EXE.
User Action: Add the DISPLAY_ID parameter to the SMG$READ_VERIFY
call or add the SCROLL _REVERSE sequence to TERMTABLE.EXE.
DIVBY-2ER,

division by zero

Facility: STR, String Manipulation Facility
Explanation: The string arithmetic routines attempted to take the reciprocal
of a string whose numeric value is 0.
User Action: The user should ensure that any string used as a divisor is not
a null string or any other string whose numeric value is 0.
DIVBYZERO,

divide by zero

Facility: VAXTPU, VAX Text Processing Utility
Explanation: Division by zero is not permitted.
User Action: None is required. However, you may want to check the
program for attempts to divide by zero and correct any occurrences you find.
DIVBYZERO,

division by zero error

Facility: MACRO, VAX MACRO Assembler
Explanation: An expression contained a division by zero.
User Action: Change the values in the expression.
DIVZERO,

attempt to divide by zero

Facility: PATCH, Patch Utility and DEBUG, VMS Debugger
Explanation: An expression contained a division by zero.
User Action: Correct the value and retry the operation.

2-150

Messages

DNA,

invalid default file name string address

Facility: RMS, VMS Record Management Services
Explanation: The default file specification string address field in the FAB is
not valid, or is in an area of memory that cannot be read by the caller.
User Action: Check for a programming error. Verify that the call to the VMS
RMS service is coded correctly.
DNF,

directory not found
Facility: RMS, VMS Record Management Services
Explanation: The specified directory name does not exist on the specified
device.
User Action: The status value (STV) field of the FAB contains a system status
code that provides additional information. Verify that both the device and
directory are specified correctly. Create a directory on the device, if necessary,
or specify an existing directory.

DNR,

device not ready, not mounted, or unavailable

Facility: RMS, VMS Record Management Services
Explanation: An input/output operation cannot be performed because the
physical device is not ready, the required volume has not been mounted, the
device has been allocated to another user, or a file header on the volume has
been corrupted.
User Action: Make sure that the volume is physically loaded, the device is
ready, and the DCL command MOUNT has completed successfully. Check
that the correct controller is set on the drive. Then retry the command or
program. If the error reoccurs, and the volume is a structured disk, run the
Verify Utility (the DCL command ANALYZE/DISK_STRUCTURE) on the
volume to check for file header corruption.
DNS,

.NO SP ACE illegal in this context
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: A .NO SP ACE command has been inserted following a
command that issues a .BREAK.
User Action: Remove the .NO SPACE command, or put it in the correct
place.

Do you want to create a new file?
Facility: AUTHORIZE, Authorize Utility
Explanation: The Authorize Utility is prompting you for an answer.
User Action: Respond YES (Y) or NO (N).

2-151

Messages

DOESNTFIT,

'string' will not fit at current indentation level

Facility: DSR, DIGITAL Standard Runoff
Explanation: The indicated string will not fit on a line with the proper
indentation of the index entry or subentry.
User Action: Hyphenate the word using the .HYPHENATE and .BREAK
flags.

DONEMSG,

system authorization file modified

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

DOSl l_BADLABEL,

volume on 'tapedrive' has label with invalid format

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility received an error trying to read a DOS-11
magtape label, or the label did not have a valid format.
User Action: In the case of an input error, a second message will follow the
BADLABEL message. Take corrective action based on the following message.
In the case of invalid format, the tape mounted on the drive is not a valid
DOS-11 volume. Find and mount the correct DOS-11 tape and retry the
operation.

DOSll_BLOCKSIZE,

volume on 'tape' has block larger than 512 bytes

Facility: EXCHANGE, Exchange Utility
Explanation: While reading a DOS-11 magtape, the Exchange Utility has
read a block which is longer than 512 bytes.
User Action: The file containing the long block cannot be processed by
EXCHANGE.

DOSl l_IOERROR,

error during I/O on volume 'volume'

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility encountered an error during input or
output on a DOS-11 magtape volume.
User Action: A second message describing the actual error condition will
follow this message. Take corrective action based on the contents of the
second message.

DOSll_PQSITION, rewinding tape to recover correct positioning
Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility has lost its position on a DOS-11
magtape, usually due to an input or output error.
User Action: EXCHANGE will rewind the tape and move to the correct
position. Please wait for this to complete.

2-152

Messages

DOUBLDALOC,

double deallocation of swap file space

double deallocation of memory block

device positioning error
Facility: RMS, VMS Record Management Services
Explanation: A magnetic tape file is not positioned properly.
User Action: Depending on the operation, the status value (STV) field in
the FAB or RAB contains a system status code that provides additional
information about the condition. Take corrective action based on this status
code. Retry the operation. If the error persists, it may indicate a system
software or hardware failure. Notify your system operator or manager.

DQCLUS,

device is mounted clusterwide, CLUSTER environment ignored

Facility: SMI, System Management Intergator/Server
Explanation: Disk quota functions are already operating in a cluster
environment. To avoid duplicate efforts, the command is only executed
on the first node in the cluster.
User Action: Do not specify the /CLUSTER qualifier with the SET
ENVIRONMENT command.
DRIVENAM, driver name is 'driver-name'
Facility: SYSGEN, System Generation Utility
Explanation: This message is issued with the message SYSVERDIF to identify
the driver.
User Action: See the SYSGEN message SYSVERDIF for user action
information.

2-153

Messages

DRVERR,

fatal drive error

Facility: SYSTEM, VMS System Services
Explanation: An input or output operation failed because of an error in
a disk or magnetic tape drive. If this message is associated with a status
code returned by a request to a DRll-W interface, a fatal error that affects
all DRll-W activity is set in the DRll-W CSR on completion of the QIO
request. Look at the third and fourth words of the IOSB (CSR and EIR) for
the specific cause of the error. If the condition indicated in the CSR can be
cleared, that is, if the ATTN bit can be cleared, SS$_DRVERR is returned. If
the condition cannot be cleared, SS$_CTRLERR is returned. In both cases,
the driver performs a device reset to the DRll-W.
If this message is returned by a request to a magtape or a disk driver, it is a
drive-related error. One or more of the following conditions can cause this
error:

•

Drive or driver timing error

•

Illegal function

•

Illegal register

•

Operation incomplete

•

Write clock failure (disk driver-specific)

•

Nonexecutable function (magnetic tape-specific)

•

Unrecovered reproducible error (magnetic tape-specific)

User Action: Check the status of the device and reenter the command.
Verify that the drive is on, loaded, and mounted correctly. If the failure
persists, notify the system manager.
DRVRSTRT,

error while issuing startup command to driver

Facility: CNF, NI Configurator
Explanation: An error occurred while attempting to issue the startup
commands to the NI driver in preparation to reading the broadcast system ID
messages.
User Action: See the accompanying message to determine the appropriate
action.
DSAQUOTA,

error disabling quota processing

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility encountered an error during an attempt to
disable quota processing. The accompanying message provides additional
information.
User Action: Correct the condition that caused the error and use the
Diskquota Utility to disable quota processing.

2-154

Messages

DSTNESDEP,

DST nesting depth too deep in module 'path-name'

Facility: DEBUG, VMS Debugger
Explanation: Debug Symbol Table nesting is too deep in the specified
module. This occurs if routine nesting or data record nesting is very deep in
the application program.
User Action: Simplify the program and run again.

DTP,

invalid key data type for key = 'nnn'
Facility: RMS, VMS Record Management Services
Explanation: The key data type specified in a key definition XAB is not a
valid data type code. The valid key data codes are: STG (default), BN2, BN4,
BN8, IN2, IN4, INS, PAC, COL, DSTG, DBN2, DBN4, DBNS, DIN2, DIN4,
DINS, DP AC, and DCOL.
User Action: The status value (STV) field of the FAB provides the key of
reference of the XAB in error. Verify that the call to the VMS RMS service is
coded correctly.

DTRBADMAIL,

unexpected mail received, type is 'mail-type'

Facility: DTR, DECnet Test Program Protocol
Explanation: The logical link is broken.
User Action: Retry the operation.

DTSBADMAIL, unexpected mail received, type is 'mail-type'
Facility: DTS, DECnet Test Program Protocol
Explanation: The logical link is broken.
User Action: Retry the operation.

DUALLOC,

dual allocation on volume 'n'

Facility: MOUNT, Mount Utility
Explanation: A logical block on the relative volume identified in the message
is allocated to more than one file.
User Action: Use the DCL command ANALYZE/DISK_STRUCTURE with
the /NOREPAIR qualifier (ANALZYE/DISK_STRUCTURE/NOREPAIR)
on the volume. This command invokes the Verify Utility, which issues a
message for each occurrence of dual file allocation. Verify Utility messages
identify the file name, the range of logical block numbers that have been
dually allocated, and the virtual block numbers that the logical blocks map
to. You can examine the messages to determine the files involved in each
case of dual allocation. Then, without allowing other file activity, copy all but
one file involved in each case of dual allocation to a new version. After you
create new versions of the applicable files, delete the versions containing dual
allocation. In this way, blocks that are not actually free are marked as free
blocks in the storage bit map. Next, rerun the Verify Utility on the volume,
using the /REP AIR qualifier (ANALZYZE/DISK_STRUCTURE/REPAIR).
Finally, examine each file and reconstruct from backup media those files that
have been corrupted.

2-155

Messages

Dump aborted, page tables may be corrupted
Facility: BUGCHECK, System Bugcheck
Explanation: When writing a selective dump (SYSGEN parameter
DUMPSTYLE set to 1), the VMS operating system relies heavily on the
integrity of the various system and process page tables. This message
indicates that the system might have detected corruption in these page
tables, and it will abort further dumping. You might not be able to analyze
the dump.
User Action: Submit a Software Performance Report.
DUMPEMPTY,

dump file contains no valid dump

Facility: SDA, System Dump Analyzer
Explanation: The SDA cannot read the contents of the system dump file.
The system dump file may be unreadable because the data is bad or because
the file is empty. If the SDA cannot read the dump file, it will not run.
User Action: None.
DUMPERRORS,

'number' errors occurred while writing the dump file

Facility: SDA, System Dump Analyzer
Explanation: The first block of the dump file contains information indicating
that there were 'number' errors while writing out the information to the dump
file.
User Action: None. The dump file might not be useful for analysis.
DUMPINCOMPL,

the dump file write was not completed

Facility: SDA, System Dump Analyzer
Explanation: The process of writing out the dump file was aborted. The
dump file is not complete, and it is not useful for dump analysis.
User Action: None. The dump file is not useful for analysis.
DUP,

duplicate key detected (DUP not set)
Facility: RMS, VMS Record Management Services
Explanation: A VMS RMS $PUT or $UPDATE operation specified a record
that contained one or more key values that duplicated key values in other
records stored in the file, and the key does not have the DUPLICATES
ALLOWED attribute.
User Action: Either reorganize the file and specify that duplicate keys are
allowed, or modify the source program to detect and respond to the condition.

DUP,

duplicate key encountered
Facility: CONVERT, Convert Utility

Explanation: More than one record in the input file has the same value in a
key field, but duplicate keys are not allowed.
User Action: Either allow duplicate keys or change the key values.

2-156

Messages

DUPBLKNUM,

duplicate block number 'nnnnnnnn', already exists in 'xDBSF'

Facility: BAD, Bad Block Locator Utility
Explanation: The block number specified in the /BAD_BLOCKS list is
already recorded in either the MDBSF or the SDBSF. The block is ignored,
and processing continues.
User Action: None.

DUPBUFNAME, buffer 'name' already exists
Facility: VAXTPU, VAX Text Processing Utility
Explanation: The first argument for the built-in procedure CREATE_BUFFER
must be a unique string. You have specified a name that already exists.
User Action: Reenter the command with a different string as the first
argument.

DUPCOMFIL,

command file 'filespec' already being written

Facility: PATCH, Patch Utility
Explanation: You have already requested that a command procedure be
written for this PATCH session.
User Action: None.

DUPDEF,

duplicate definition of 'name' encountered

Facility: CDU, Command Definition Utility
Explanation: CDU encountered a DEFINE statement in which there is
already a definition with the same name.
User Action: Edit the CLD file so that all definitions use unique names.

DUPDEVSPC,

duplicate device specified

Facility: MOUNT, Mount Utility
Explanation: The same tape device is specified more than once in a list of
tape devices for the DCL command MOUNT.
User Action: Reenter the MOUNT command specifying each device only
once.

DUPDSKQUOTA,

duplicate disk quota file entry

Facility: SYSTEM, VMS System Services
Explanation: Another quota entry for the specified UIC already exists.
User Action: Check the UIC listed. Correct the UIC or select and reenter
another UI C.

2-157

Messages

DUPFILENAME, duplicate file name
Facility: SYSTEM, VMS System Services
Explanation: The directory specified already contains an entry for the
specified file name, file type, and version number.
User Action: Delete the existing file, or correct the command or program to
change the file name, file type, or version number specified for the output file.
DUPFORM,

duplicate form number

Facility: JBC, Job Controller
Explanation: A DEFINE/FORM command specified a form number that is
already defined. Each form must have a unique number.
User Action: Specify the command so that each form is defined uniquely.
DUPGLOBAL,

global symbol 'symbol-name' from file 'library-filespec' already in
library 'library-filespec'

Facility: LIBRAR, LIBRARY Command
Explanation: This error message is generated by the DCL command
LIBRARY. An attempt is made to insert an object module containing a global
symbol that is already in the global symbol table (GST).
User Action: Replace the module instead of inserting it; or remove the global
symbol from the library before inserting the module.
DUPIDENT,

only one IDENT statement is allowed

Facility: CDU, Command Definition Utility
Explanation: More than one IDENT statement is encountered in a single
CLO file. Only one IDENT statement is allowed.
User Action: Edit the CLO file so that there is only one IDENT statement.
DUPINVALID,

component file already in STARTUP table

Facility: SMI, System Management Intergator/Server
Explanation: An attempt is made to add a startup component file to the
component database which already contains that entry.
User Action: Either use the STARTUP MODIFY FILE command at the
SYSMAN> prompt to change the existing entry, or reenter the command
with a new component file name.
DUPKEY,

duplicate key in index

Facility: LBR, Librarian Subroutine Package
Explanation: This message is generated by the Librarian routines. On a call
to LBR$INSERT_KEY, the specified key is found to exist already.
User Action: Call LBR$REPLACE_KEY to replace the existing key.

2-158

Messages

DUPKEY,

keyword 'keyword-name' has already been defined

Facility: CDU, Command Definition Utility
Explanation: CDU encountered a KEYWORD definition that conflicts with an
existing KEYWORD definition with the same name. KEYWORD definitions in
the same TYPE definition must be unique.
User Action: Edit the CLD file so that each KEYWORD definition in the same
TYPE definition is unique.

DUPKEYMAP,

attempt to define a duplicate key map 'key-map-name'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: You are trying to create a key map with the same name as a
key map or key-map list that already exists.
User Action: Select another name for the new key map.

DUPKEYMAPLIST,

attempt to define a duplicate key-map list 'key-map-listname'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: You are trying to create a key-map list with the same name as
a key map or key-map list that already exists.
User Action: Select another name for the new key-map list.

DUPLABEL,

only one LABEL clause is allowed

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

DUPLNAM,

duplicate name

Facility: SYSTEM, VMS System Services
Explanation: A process name specified in a request to create a process
duplicates the name of an existing process executing with the same group
number. Process names must be unique within a group.
User Action: Specify an alternative process name. Check whether the
existing process with that name should be deleted and, if so, use the DCL
command STOP to delete it.

DUPMOD,

module 'module-name' from file 'library-filespec' already in 'libraryfilespec'

Facility: LIBRAR, LIBRARY Command
Explanation: This error message is generated by the DCL command
LIBRARY. The module you are inserting into the library already exists in
the module name table (MNT).
User Action: Change the name of the module or replace the existing module
with a new one.

2-159

Messages

DUPMODULE, module 'module-name' from file 'filename' already in 'name'
Facility: LIBRAR, LIBRARY Command
Explanation: One of the modules being inserted into the library already
exists in the library module name table.
User Action: Change the name of the module being inserted, delete the
module of the same name from the library, or use the LIBRARY/REPLACE
option to replace the module.

DUPMODULE, only one MODULE statement allowed
Facility: CDU, Command Definition Utility
Explanation: More than one MODULE statement is encountered in a single
CLO file. Only one MODULE statement is allowed.
User Action: Edit the CLD file so that there is only one MODULE statement.

DUPMSG, message code nn already assigned as ss
Facility: MESSAGE, Message Utility
Explanation: You have assigned the same message code (nn) to more than
one message symbol. The first message symbol (ss) assigned to the message
code is shown.
User Action: Check that you have not assigned twice the same message
number or symbol for the same facility. Reenter the message definitions so a
different message symbol is assigned to one message code.

DUP_OUTPUT, output file has already been specified
Facility: SORT, Sort/Merge Utility
Explanation: You passed the output file argument in the routine package
more than once.
User Action: Check your file arguments and verify that you specified the
output file only once.

DUPPLACE, only one PLACEMENT clause is allowed
Facility: CDU, Command Definition Utility
Explanation: CDU encountered more than one PLACEMENT clause in a
single qualifier definition. Only one PLACEMENT clause is allowed per
qualifier definition.
User Action: Edit the CLO file so that each qualifier definition does not
contain more than one PLACEMENT clause.

DUPPREFIX,

only one PREFIX clause is allowed

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

2-160

Messages

DUPPROMPT, only one PROMPT clause is allowed
Facility: CDU, Command Definition Utility
Explanation: CDU encountered more than one PROMPT clause in a single
parameter definition. Only one PROMPT clause is allowed per parameter
definition.
User Action: Edit the CLD file so that each parameter definition does not
contain more than one PROMPT clause.

qualifier 1qualifier-name 1 has already been defined

DUPQUAL,

Facility: CDU, Command Definition Utility
Explanation: CDU has encountered a previously defined qualifier in a
single verb/syntax definition. All qualifiers defined in a single verb/syntax
definition must be unique.
User Action: Edit the CLD file so that all qualifiers defined in a single verb
/syntax definition are unique.

DUPRVN, duplicate volume number already mounted
Facility: MOUNT, Mount Utility
Explanation: A volume of the same relative volume number and the same
volume set name is already mounted. You are trying to mount a volume that
belongs to a volume set with the same name as a volume set that is already
mounted.
User Action: Make sure that you have mounted the correct volume. Verify
that you are defining the volume status (/SHARE, /NOSHARE, /GROUP, or
/SYSTEM) consistently with volumes already mounted.

DUPSYM,

name 1 is a duplicate symbol definition

Facility: CDU, Command Definition Utility
Explanation: The same name is used twice. For example, this error could
occur because the same syntax list or qualifier name appears twice in the CLD
file.
User Action: Modify the CLD file to correct the duplication.

DUPSYM, duplicate symbol definition
Facility: MESSAGE, Message Utility
Explanation: You have assigned the same symbol to represent two values.
This message may refer to symbols defined in a message definition, a facility
definition, or the .LITERAL directive.
User Action: Reenter your source statements with each symbol defined only
once.

2-161

Messages

DUPSYNTAX,

only one SYNTAX clause is allowed

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

DUPTYPE,

only one TYPE clause is allowed

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

DUPUNIT,

MSCP Controller-duplicate unit number

Facility: SYSTEM, VMS System Services
Explanation: On a STARTUP request, the user cannot assign two channels to
an XE unit before the unit is started in SHARED mode. The driver may have
to relink the user's Channel Control Block (CCB) to a different UCB and this
cannot be done if there are two CCBs that must be reset.
User Action: The user must STARTUP the XE unit in SHARED mode before
assigning any extra channels to the XE unit.

DUPVALUE,

only one VALUE clause is allowed

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

DUPVOLNAM,

volume label already present in set

Facility: MOUNT, Mount Utility
Explanation: During an attempt to add a volume to an existing volume set,
the specified volume set is found to contain a volume with the label specified.
User Action: Verify the labels on the existing volumes in the set. Choose a
new label for the volume you are adding to the set, reinitialize the volume,
and reenter the DCL command MOUNT/BIND.

DVI, invalid device ID value in NAM block
Facility: RMS, VMS Record Management Services
Explanation: The device identification field of the VMS RMS NAM block is
not valid.
User Action: Verify that the call to the VMS RMS service is coded correctly.

2-162

Messages

DVN,

duplicate variable name: 'string'

Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: An attempt has been made to use a name specification
with a .VARIABLE command that has already been used with a previous
.VARIABLE, .IF, .IFNOT, or .ELSE command.
User Action: Change the name specification.
DXl,

in-core indexing (.DO INDEX/.PRINT INDEX) is no longer supported

Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: In-core indexing is no longer supported.
User Action: See accompanying message.
DX2,

instead, specify RUNOFF /INTERMEDIATE and .REQUIRE 'file.RNX' here.

Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: In-core indexing is no longer supported. See accompanying
message.
User Action: Specify RUNOFF /INTERMEDIATE and .REQUIRE 'file.RNX'.
ECONOTSET,

eco level 'nn' not set in 'filespec'

Facility: PATCH, Patch Utility
Explanation: You specified an ECO level that is not set in that particular
image file. This typically occurs when you enter the PATCH command
CHECK ECO before entering the PATCH command UPDATE.
User Action: Enter a SET ECO command to reenable the Patch Utility
command processing. Specify the correct ECO level and retry the operation.
ECOSET,

eco level 'nn' already set in 'filespec'

Facility: PATCH, Patch Utility
Explanation: You specified an ECO level that has already been set in that
particular image file.
User Action: Enter a SET ECO command to reenable the Patch Utility
command processing. Specify the correct ECO level and retry.
Editor aborted

Facility: EDT, EDT Editor
Explanation: EDT experienced some difficulties and had to abort the session.
User Action: Use the journal file to recover your editing work.
EDITPROC,

error creating or executing editor subprocess

Facility: MAIL, Mail Utility
Explanation: You entered the SEND/EDIT command and MAIL's attempt
to create a subprocess failed. This message is issued with an accompanying
message.
User Action: Take corrective action based on the accompanying message.

2-163

Messages

EDITSCLSH,

edits clash 'editing-commands' 'filespecs'

Facility: SUMSLP, SUMSLP Batch Editing Utility
Explanation: Two or more conflicting editing commands have been entered,
that is, more than one edit operation has been specified for one line of
source code. The relevant editing commands and the file specifications
of the S UMSLP command files are listed following the message, which is
informational.
User Action: None.
EDOUTSEQ,

edits out of sequence

Facility: SUM, Source Update Merge Utility and SUMSLP, SUMSLP Batch
Editing Utility
Explanation: The indicated edit command is not in ascending sequence
within the update file. The editing operation has been performed correctly.
User Action: Edit the update file to place the edit in the correct position.
EF_ALRFRE,

event flag already free

Facility: LIB, Library Facility
Explanation: A call is made to LIB$FREE_EF to free an event flag number
that is not allocated.
User Action: Ensure that you use the correct event flag number in the call to
LIB$FREE_EF.
EF_ALRRES,

event flag already reserved

Facility: LIB, Library Facility
Explanation: A call is made to LIB$RESERVE_EF to receive an event flag
number that is already allocated.
User Action: Ensure that you use the correct event flag number in the call to
LIB$RESERVE_EF.
EFD,

.END FOOTNOTE doesn't terminate .FOOTNOTE
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: The .ENDFOOTNOTE command is improperly positioned in
the file; it does not follow associated footnote data.
User Action: Put the .ENDFOOTNOTE command in the correct place, or
remove it.

EF_RESSYS,

event flag reserved to system

Facility: LIB, Library Facility
Explanation: A call is made to LIB$RESERVE_EF to reserve an invalid event
flag number. Ranges for valid event flag numbers are 1 through 23 and 32
through 63.
User Action: Retry specifying a valid event flag number.

2-164

Messages

ELD,

.END LITERAL doesn't follow .LITERAL
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: The .END LITERAL command is improperly positioned in the
file; it does not follow the .LITERAL command.
User Action: Put the .END LITERAL command in the correct place, or
remove it.

ELEALREXI , an element of the same name already exists
Facility: PPL, Parallel Processing Facility
Explanation: An element by this name already exists, and its ID is returned.
User Action: Continue normally if you expect the name to exist.

ELETOOLON, element too long, maximum 255 characters
Facility: LIB, Library Facility
Explanation: The initialization string element passed to LIB$INIT_DATE_
TIME_CONTEXT is too long; the maximum length allowed is 255 characters.
User Action: Begin debugging procedures to verify and correct the problem.

EMPTYDEF, no attributes supplied-DEFINE ignored
Facility: CDU, Command Definition Utility
Explanation: The CLD file does not contain any attributes.
User Action: Add attributes to the CLD file.

EMPTYFILE, no modules found in file 'filename'
Facility: LINK, Linker Utility
Explanation: An object file contained no object modules.
User Action: Ensure that the source file compiled properly and that the
output object file is not empty.

EMPTYFILE, zero-length page or swap file cannot be installed
Facility: SYSGEN, System Generation Utility
Explanation: You attempted to install a zero-length page or swapping file.
User Action: None. You cannot install a zero-length page or swapping file.

EMPTYHIST, library update history is empty
Facility: LBR, Librarian Subroutine Package
Explanation: The library has an update history, but no update history records
are present.
User Action: None.

2-165

Messages

EMPTYIN,

empty input file 'filename'

Facility: DSR, DIGITAL Standard Runoff
Explanation: The input file contained no data for processing.
User Action: Edit the input file.
EMPTYJOB,

no files specified in job request

Facility: JBC, Job Controller
Explanation: A batch or print job is requested that did not specify any files
to process. This error condition occurs if the requesting process opened and
closed a job using the SJC$_CREATE_JOB and SJC$_CLOSE_JOB function
codes, but did not specify any files with the SJC$_ADD_FILE function of the
$SNDJBC system service. This condition causes the open job to be removed
from the system job queue file.
User Action: None.
EMPTYKMLIST,

key-map list 'key-map-list-name' does not contain any key maps

Facility: VAXTPU, VAX Text Processing Utility
Explanation: You are referring to a key-map list that has no key maps.
User Action: Enter the built-in procedure SHOW (KEY_MAP_LISTS) on the
command line to obtain the names of the key-map lists and their key maps.
EMPTYLIBRARY,

no modules in library: 'library-filespec'

Facility: LIBRAR, LIBRARY Command
Explanation: The library being compressed contains no modules.
User Action: None.
EMPTYLST,

known file entry list is empty

Facility: INSTALL, Install Utility
Explanation: There are no entries in the known file entry list. Therefore,
LIST, DELETE, REMOVE, and PURGE will have no effect.
User Action: None.
EMSKNOTABS,

entry mask not absolute

Facility: MACRO, VAX MACRO Assembler
Explanation: The entry mask expression is not absolute or it contained
undefined symbols.
User Action: Change the values in the expression.

2-166

Messages

ENAQUOTA,

error enabling quota processing

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility encountered an error during an attempt to
enable quota processing. The accompanying message provides additional
information.
User Action: The Verify Utility will not reconstruct disk quota information.
Try to correct the condition that caused the error and then reenter the Verify
Utility command line.
END,

control returned to node 1node-name 1

Facility: REM, Set Host Facility
Explanation: This is an information message issued when a remote terminal
session is ended. This message is informational.
User Action: None.
1

ENDABORT,

name compilation aborted
1

Facility: Shared by several facilities
Explanation: Serious errors prevented the compilation of name from being
completed.
1

User Action: Correct the errors and recompile the program.

name completed with nnn' diagnostics

ENDDIAGS,

Facility: Shared by several facilities
Explanation: The compilation or assembly of name is completed with
diagnostics. Use of the object module produced may give invalid results.
1

User Action: Correct the conditions which resulted in the diagnostics and
recompile or reassemble the program.
ENDED,

name' ended

Facility: Shared by several facilities
Explanation: A program phase has been ended.
User Action: None.
ENDEDD,

'name' ended at system date and time'
1

Facility: Shared by several facilities
Explanation: A program phase has been ended.
User Action: None.
ENDEDT,

name' ended at 'system time

Facility: Shared by several facilities
Explanation: A program phase has been ended.
User Action: None.

2-167

Messages

ENDNOOBJ,

'name' completed with 'nnn' diagnostics-object deleted

Facility: Shared by several facilities
Explanation: The compilation or assembly of 'name' is completed with
errors. No object file is produced.
User Action: Correct the source language errors and recompile or reassemble.
ENDOFBUF,

attempt to move past the end of buffer 'buffer-name'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: You attempted to move past the end of the current buffer.
VAXTPU makes offset 0 of the end-of-buffer mark the current editing
position.
User Action: Stop trying to move forward. You are already positioned at the
end of the buffer.
ENDOFFILE,

end of file

Facility: SYSTEM, VMS System Services
Explanation: You received this message because of one or more of the
following conditions:
•

A tape mark indicating end-of-file is encountered during an attempt to
read a tape. For data transfer functions, the byte count is zero; for skip
record functions, the count is the number of blocks skipped.

•

An end-of-file card is encountered during an attempt to read from the
card reader.

•

A mailbox is empty or had an end-of-file (10$_ENDOFFILE) written to it.

•

No data is available for transfer on the DMC-11, and 10$M_NOW is
specified.

•

The file system ACP encountered the end of the allocated space for a
virtual 1/0 operation or an attempted truncation.

User Action: Note the condition. If necessary, modify the source program to
detect and respond to the condition.
ENDOFFILE,

end of file on read to terminal or file

Facility: VAXTPU, VAX Text Processing Utility
Explanation: Premature end-of-file encountered on read from input device or
file.
User Action: Submit a Software Performance Report.
ENDOFTAPE,

end of tape

Facility: SYSTEM, VMS System Services
Explanation: The end of tape marker, indicating the physical end of the tape,
is encountered.
User Action: Note the condition. If the tape marker is encountered during an
operation in the forward direction, it may be necessary to modify the source
program to detect and respond to the condition.

2-168

Messages

ENDOFVOLUME,

end of volume

Facility: SYSTEM, VMS System Services
Explanation: Two consecutive tape marks were detected during a skip file
operation to a tape mounted non-file-structured or during a skip record
operation. This return is also used as a logical end-of-tape indicator for nonANSI tapes. If an ANSI standard tape is mounted foreign, this may only
indicate an empty file within the volume and not the end of the volume. The
high word of the first longword in the 1/0 status block contains the number
of tape marks passed.
User Action: Use a read function to read data located past the double
tape mark. (The first read function returns end-of-file status; a second read
function reads the data.)
ENDPRS,

error code of 'xx' on command line parse end

Facility: PATCH, Patch Utility
Explanation: A command interpreter callback request failed due to the error
represented as 'xx'.
User Action: Correct the error (represented as 'xx') and retry.
ENDTOPIC,

request LBR$0UTPUT_HELP terminate printing

Facility: LBR, Librarian Subroutine Package
Explanation: When a user-supplied output routine is called by
LBR$0UTPUT--8ELP, the output routine returns this status to terminate
the printing of help text.
User Action: None.
ENDWRNGMAC,

.ENDM does not end macro 'macro-name' in 'library-filespec'

Facility: LIBRAR, LIBRARY Command
Explanation: This warning message is generated by the DCL command
LIBRARY. The macro name following the .ENDM statement does not match
the name of the macro it should end.
User Action: Reformat the macro source file.
ENDWRNGMAC, statement ends wrong MACRO
Facility: MACRO, VAX MACRO Assembler
Explanation: The .ENDM directive specified a different name from its
corresponding .MACRO directive.
User Action: Correct the name in the .ENDM directive to ensure that the
.ENDM directive and .MACRO directive correspond as required.

2-169

Messages

ENGLUSED,

English used, could not determine user's language

Facility: LIB, Library Facility
Explanation: Translation of the logical SYS$LANGUAGE (or any logicals
depending on the specified language) failed, or the tables supporting the
selected language were not chosen by your system manager. English is being
used.
User Action: Examine SYS$LANGUAGE. Verify that the logical name table
for the language is built and that all logicals depending on SYS$LANGUAGE
(for example, logicals to supply spellings of months and days of the week) are
correct.
ENQ, ENQ system service request failed
Facility: RMS, VMS Record Management Services
Explanation: A $ENQ or $DEQ system service invoked by RMS failed.
The status value (STV) field of the FAB contains a code that provides more
information about the condition.
User Action: Correct the condition described in the STV field. Take
corrective action based on this system status code.
ENT,

ACP enter function failed
Facility: RMS, VMS Record Management Services
Explanation: An attempt to enter a file specification in a directory failed.
This message is associated with a status code returned from a file system ACP
QIO request made by VMS RMS.
User Action: The status value (STV) field of the FAB contains a system status
code that provides more information about the condition. Take corrective
action based on this status code.

ENTERED,

'filespec' entered as 'filespec'

Facility: SET, SET Facility
Explanation: The file has been entered successfully. This message is
displayed when you specify the /LOG qualifier with the SET FILE/ENTER
command.
User Action: None.
ENTERLOST,

file ('file-id') 'filename' error entering file in directory [SYSLOST]

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

2-170

Messages

ENTERR,

error entering 'filespec' as 'filespec'

Facility: SET, SET Facility
Explanation: An error occurred while attempting to enter a synonym for a
file. This message is accompanied by another message explaining why the
synonym could not be entered.
User Action: Respond to the accompanying message.

ENTFIL,

error entering file on queue

Facility: INPSMB, Input Symbiont
Explanation: The system encountered an error creating a batch job from card
reader input. The accompanying message provides additional information.
User Action: Correct the error and reenter the job.

ENTIDMTCH,

'string' ident of 'string' for entity 'string' in module 'modulename' file 'file-name' does not match ident of 'string' in module
'module-name' file 'filename'

Facility: LINK, Linker Utility
Explanation: The specified modules were not compiled with the same
external files (for example, a library).
User Action: Recompile the modules in error.

ENTIDMTCHB,

'string' ident of number 'number' for entity 'string' in module
'module-name' file 'file-name' does not match ident of number
'number' in module 'module-name' file 'filename'

Facility: LINK, Linker Utility
Explanation: The specified modules were not compiled with the same
external files (for example, a library).
User Action: Recompile the modules in error.

ENTIDMTCHO,

object type of 'string' for entity 'string' in module 'module-name'
file 'filename' does not match object type of 'string' in module
'module-name' file 'filename'

Facility: LINK, Linker Utility
Explanation: You specified different object types.
User Action: Recompile using the same object types.

ENTIDMTCHT,

ident type for entity 'string' in module 'module-name' file 'filename' differs from ident type in module 'module-name' file
'file-name'

Facility: LINK, Linker Utility
Explanation: You specified both a binary and string ident for a single entity.
User Action: Recompile, specifying either a binary or string ident, but not
both the same entity.

2-17!

Messages

Entity must be WORD, SENTENCE, PAGE, or PARAGRAPH
Facility: EDT, EDT Editor
Explanation: The EDT command SET ENTITY is entered without one of the
following four entity options: WORD, SENTENCE, PAGE, PARAGRAPH.
User Action: Reenter the command specifying one of the four entity options
displayed in the message text.

ENTNF,

specified entity not found in command tables

Facility: CLI, Command Language Interpreter (DCL)
Explanation: The parameter, qualifier, or keyword specified as input to one
of the CLI$xxxx routines does not exist in the command tables.
User Action: Check the spelling of the entity and its existence in the
command tables.

ENV,

current Command Environment
Facility: SYSMAN, Cluster System Management Utility
Explanation: The current environment is changed with the SET
ENVIRONMENT command.
User Action: Verify that the listed environment is correct.

ENV,

support for RMS service call or feature not present
Facility: RMS, VMS Record Management Services
Explanation: An image attempted a VMS RMS function that is not supported
in this version of VMS RMS.
User Action: Consult the system manager to find out which functions are
supported or to include your desired function.

ENVNOTSET,

environment not changed

Facility: SYSMAN, Cluster System Management Utility
Explanation: An error occurred in processing a SET ENVIRONMENT
command. The previous environment is still in effect.
User Action: Take action according to the specific error message
accompanying this message.

EOF,

end of file detected
Facility: RMS, VMS Record Management Services
Explanation: An end-of-file condition occurred on a VMS RMS service.
User Action: If necessary, modify the source program to detect and respond
to the condition.

2-172

Messages

EOF,

end of input
Facility: PSM, Print Symbiont
Explanation: This status is returned by a print symbiont input routine
indicating the end of input.
User Action: None.

EOF,

end-of-file
Facility: SMG, Screen Management Facility
Explanation: End of file condition is detected on input.
User Action: If necessary, modify your program to recognize this condition
and respond to it.

EOFMISMATCH,

end of file position mismatch for 'filespec'

Facility: BACKUP, Backup Utility
Explanation: During a compare or verify operation, the end-of-file pointer
for the specified file did not agree with the input file. If other file activity
is occurring on the volume, the error may be caused because another user
modified the file during the backup operation.
User Action: Note that the copies are inconsistent.
EOMERROR,

compilation errors in module 'module-name'

fatal compilation errors in module 'module-name'

2-173

Messages

EOMSTK,

'number' items left on Linker internal stack in module 'module-name'
file 'filename'

Facility: LINK, Linker Utility
Explanation: An object module did not leave the linker stack empty.
User Action: Submit a Software Performance Report on the appropriate
language compiler.

EOMWARN,

compilation warnings in module 'module'

EOTIN,

EOT response to text

Facility: SYSTEM, VMS System Services
Explanation: The IBM system has sent an EOT instead of an expected
acknowledgment to XKDRIVER after receiving a block of data from
XKDRIVER.
User Action: Either a normal condition exists where the IBM host has
acknowledged the receipt of a block of text with an EOT instead of an ACK
(in this case, you do not need to provide corrective action), or an error has
occurred. When an error occurs, you may need to correct and retransmit the
last block of data to the IBM host.

EQV_NOTICE,

equivalent name-device 'controller name' will be output as
'controller-name'

Facility: SYSGEN, System Generation Utility
Explanation: An equivalent name for a controller is entered with the
SYSGEN command CONFIGURE.
User Action: None. This is informational.

ERACTED,

error activating editor 'editor-name'

Facility: MAIL, Mail Utility
Explanation: MAIL could not activate the editor specified by your last SET
EDITOR command.
User Action: Check the validity of your editor specification by using the
SHOW EDITOR command. Check with your system manager to make sure
the specified editor is available on your system.

ERASEBLKS,

blocks reclaimed on relative volume N not completely erased

Facility: MOUNT, Mount Utility
Explanation: While rebuilding a volume set, some of the blocks being
reclaimed could not be erased.
User Action: The accompanying message provides additional information.

2-174

Messages

ERASEFAIL,

volume not completely erased

Facility: INIT, INITIALIZE Command
Explanation: INIT encountered at least one error when it attempted to erase
the volume.
User Action: The accompanying message provides additional information.
ERBOXPROC,

'process-name' Error count= 'nnn'

Facility: UETP, User Environment Test Package
Explanation: This message assigns a sequence number, 'nnn', to an error
found by a particular process. The error is described in a subsequent message.
In order to set off the error from other text being printed, a box of asterisks
surrounds this message.

***********************

*
*

'program name'
Error count = 'nn'

*
*

***********************
User Action: Take action indicated by the messages that follow.
ERRASSIGN,

the attempt to acquire an I/O channel for the debugger failed

Facility: DEBUG, VMS Debugger
Explanation: A bad status is returned from a $ASSIGN type of call. This
message is issued in the $DBG_INFO context. The debugger needs to
acquire I/O channels to perform I/O operations. In this case, the debugger
failed to acquire such a channel.
User Action: Check your process quotas.
ERRAT_LIN,

error in line 'line-number' at or near 'line-number'

Facility: SMG, Screen Management Facility
Explanation: This is a general information message included with many
termtable compiler messages. This message attempts to identify specifically
where an error occurred.
User Action: Check the specified line in your definition.
ERRCACHFUL,

error cache is full

2-175

Messages

ERRCLSFILE,

unable to close file

Facility: DEBUG, VMS Debugger
Explanation: A bad status is from a call to close a file. This message is issued
in the $DBG-1NFO context. The debugger failed to close a file.
User Action: Identify the opened file with the DCL command SHOW
DEVICE/FILES, then close the file with the DCL command CLOSE. Unless
the reason for this message is apparent, submit a Software Performance
Report.
ERRCRELNM,

unable to create a logical name

Facility: DEBUG, VMS Debugger
Explanation: The debugger creates logical names for input and output
redirection. This message is issued in the $DBG_INFO context.
User Action: Submit a Software Performance Report.
ERRCVTFIL,

error returning input filename from DCL

Facility: MONITOR, Monitor Utility
Explanation: An error occurred during processing of a MONITOR CONVERT
command. The input file specification could not be obtained. Examine the
accompanying message for more information.
User Action: Correct the input file specification and reenter your command.
ERRCVTOPN,

error opening input file for conversion

Facility: MONITOR, Monitor Utility
Explanation: An error occurred during processing of a MONITOR CONVERT
command. The specified input file could not be opened.
User Action: This error may occur if the specified input file is incorrect or
inaccessible. Correct the input file specification and reenter your command.
ERRDEASSIGN,

attempt to deassign an I/O channel acquired by the debugger
failed

Facility: DEBUG, VMS Debugger
Explanation: The debugger tried to deassign an I/O channel that is required
for internal purposes. This error notes the failure of the SYS$DASSGN
system service, probably due to an invalid channel.
User Action: Submit a Software Performance Report.
ERREXECOM, EXECUTE subcommand is not allowed in execute command file
Facility: MONITOR, Monitor Utility
Explanation: A MONITOR EXECUTE command is encountered in a
MONITOR command file. Any Monitor Utility command may appear in
a MONITOR command file except the EXECUTE command.
User Action: Remove the EXECUTE command from the command file, and
reenter the original request.

2-176

Messages

ERREXEFIL,

error returning execute command filename from DCL

Facility: MONITOR, Monitor Utility
Explanation: An error occurred during processing of a MONITOR EXECUTE
command. The MONITOR command file specification could not be obtained.
More information may be obtained by examining the accompanying message.
User Action: Correct the error indicated by the accompanying message and
rerun the MONITOR EXECUTE command.
ERREXEOPN,

error opening execute command file

Facility: MONITOR, Monitor Utility
Explanation: An error occurred during processing of a MONITOR EXECUTE
command. The MONITOR command file could not be opened.
User Action: This error can occur if the command file specification is
incorrect, or if the file is inaccessible. Correct the file specification and then
reenter the MONITOR EXECUTE command.
ERREXEREA,

error reading execute command file

Facility: MONITOR, Monitor Utility
Explanation: An error occurred while reading a MONITOR command file.
User Action: Reenter the MONITOR EXECUTE command. If the error
reoccurs, check the command file.
ERREXEREP,

error replacing"@" with "EXECUTE"

Facility: MONITOR, Monitor Utility
Explanation: An error occurred during processing of a MONITOR command
file. An attempt to translate the string "@" to "EXECUTE" failed. More
information may be obtained by examining the accompanying message.
User Action: Correct the error indicated by the accompanying message and
reexecute the command file. Most such messages represent status values
returned to MONITOR from the Run-Time Library string manipulation
procedures.
ERRFAO,

unable to format output string

Facility: DEBUG, VMS Debugger
Explanation: An error is returned from a call to $FAO.
User Action: Submit a Software Performance Report.
ERRFREDYN,

error freeing dynamic string when returned to LIB$FREE_VM

Facility: STR, String Manipulation Facility
Explanation: Unable to free space allocated to the string; this usually occurs
when a dynamic string descriptor points to static storage.
User Action: Begin debugging procedures to verify and correct the problem.

2-177

Messages

ERRGETDVI,

unable to get device information

Facility: DEBUG, VMS Debugger
Explanation: The debugger requires some information from the $GETDVI
routine, and the call failed.
User Action: Submit a Software Performance Report.
ERRGETEF,

attempt to allocate an event flag failed

Facility: DEBUG, VMS Debugger
Explanation: The debugger tried to allocate a local event tlag for its own use,
but the routine that is called to allocate the event flag failed. This message is
usually issued with the $DBG-1NFO routine.
User Action: The debugger needs event flags to operate. Check the program
being debugged for excessive allocation of event flags.
ERRHALT,

halt with error interrupt pending

error processing /INPUT file

Facility: MONITOR, Monitor Utility
Explanation: An error occurred while referencing the input recording file. To
obtain more information, examine the accompanying linked messages.
User Action: Correct the error indicated by the linked messages and rerun
the MONITOR command.
ERRINVEDIT,

error invoking editor

Facility: DEBUG, VMS Debugger
Explanation: While the system tried to invoke an editor, an invalid status is
returned.
User Action: Find out if the requested editor is available. If so, submit a
Software Performance Report.
ERRLIN,

error in line 'line-number'

Facility: SMG, Screen Management Facility
Explanation: This is a general informational message included with many
Termtable compiler messages. This message attempts to identify specifically
which line contained an error.
User Action: Check the specified line in your definition.

2-178

Messages

ERROR,

error reading parameter file

Facility: SYSGEN, System Generation Utility
Explanation: An irrecoverable 1/0 error occurred while SYSGEN was
reading a parameter file.
User Action: Reenter the command.
Error in command
Facility: EDT, EDT Editor
Explanation: The command entered is invalid
User Action: Enter a valid command.
Error in command option
Facility: EDT, EDT Editor
Explanation: The command entered included a /NAME qualifier where
name is not a valid option.
User Action: Reenter the command without specifying /NAME as a qualifier.
Error in range specification
Facility: EDT, EDT Editor
Explanation: The command requires a complete range specification.
User Action: Reenter the command including a complete range specification.
ERROR,

internal debugger error detected

Facility: DEBUG, VMS Debugger
Explanation: This message indicates an internal debugger error.
User Action: Correct the problem given by the messages following this
message. If you cannot solve the problem, submit a Software Performance
Report.
Error opening terminal for input,
Facility: EDT, EDT Editor
Explanation: EDT could not access the specified terminal for input. This
message appears when you are using EDT from a running program.
User Action: After determining why EDT cannot access the specified
terminal, correct the problem.
Error opening terminal for output,
Facility: EDT, EDT Editor
Explanation: EDT could not access the specified terminal for output. This
message appears when you are using EDT from a running program.
User Action: After determining why EDT cannot access the specified
terminal, correct the problem.

2-179

Messages

Error reading from input file,
Facility: EDT, EDT Editor
Explanation: EDT cannot read an input file when it started the editing
session. The problem file could be the main input file, the journal file if you
are using the /RECOVER specifier, or the startup command file if you are
using one.
User Action: Determine why the input file cannot be read.
Error reading from terminal,
Facility: EDT, EDT Editor
Explanation: EDT cannot process the input it is receiving from the terminal.
The message appears when you are using EDT from a running program.
User Action: After determining why EDT cannot process input from the
specified terminal, correct the problem.
Error reporting suppressed, memory dump continuing
Facility: BUGCHECK, System Bugcheck
Explanation: This message indicates that too many errors occurred while
writing a dump to the disk; it is no longer appropriate to continue to send
messages for each error, and error reporting is suppressed. The system
continues to attempt to write the dump.
User Action: When the system reboots, copy the dump to another file. You
can determine the text associated with the hexadecimal statuses of previous
messages by using the F$MESSAGE lexical function or its equivalent. If
the status indicates a possible disk problem, see the user action for the
accompanying message.
Error writing 'nn' block(s), starting at vbn 'vv' - status= 'ss'
Facility: BUGCHECK, System Bugcheck
Explanation: An error occurred while writing a dump to the disk. The status
is the error returned by the QIO$ system service that attempted the write
operation. The system continues to attempt to write the dump.
User Action: When the VMS operating system reboots, copy the dump
to another file. You can determine the text associated with the hexadecimal
status by using the F$MESSAGE lexical function or its equivalent. If the status
indicates a possible disk problem, see the user action for the accompanying
message.
ERROR,

unable to initialize disk boot driver

Facility: VAXCLUSTER, VAXcluster Facility
Explanation: This is a catchall error in the bootstrap.
User Action: Check for communication and hardware failures.

2-180

Messages

Error writing to output file
Facility: EDT, EDT Editor
Explanation: EDT cannot produce an output file. The problem file could be
the MAIN buffer copy, the journal file, or a file requested with the WRITE
command.
User Action: After determining why EDT cannot produce an output file,
correct the problem.
ERROR_HALT,

failed to load MSCP server

Facility: STACONFIG, Stand-alone Configure Process
Explanation: The call to load the MSCP server from STACONFIG_MSCP
failed. Most likely there is not enough nonpaged memory available to allocate
the server data structures and local buffer area.
User Action: Check the values in the sysgen parameter NP AGDYN to ensure
the amount of nonpaged memory allocated to the system is reasonable. Also
check MSCP_BUFFER to make sure that value is not too large compared to
the value in NP AGDYN.
ERRORISUE,

completed with errors

Facility: LINK, Linker Utility
Explanation: The link completed, but errors were detected.
User Action: Correct the errors and relink.
ERRORS,

compilation errors in module 'module-name' file 'filename'

Facility: LINK, Linker Utility
Explanation: An object module contains compilation errors.
User Action: Correct the source code, then recompile or reassemble.
ERROUTOPN, error opening conversion file for output
Facility: MONITOR, Monitor Utility
Explanation: An error occurred during processing of a MONITOR CONVERT
command. The specified output file could not be opened.
User Action: This error may occur if the output file specification is incorrect.
Correct the output file specification and reenter your command.
ERRP ARSE,

error parsing command

Facility: MONITOR, Monitor Utility
Explanation: An error is detected while parsing a Monitor Utility command.
More information may be obtained by examining the accompanying message.
User Action: Correct the error indicated by the accompanying message and
reenter the command. To obtain the correct syntax for utility commands,
enter the HELP command in response to the MONITOR> prompt.

2-181

Messages

ERRPHOTRA , phonemic transcription error is detected
Facility: DTK, DECtalk Facility
Explanation: A phonemic transcription malfunction occurred after DECtalk
device was turned on.
User Action: Check the DECtalk hardware.
ERRPROMPT,

error prompting for input

Facility: MONITOR, Monitor Utility
Explanation: An error is detected while prompting the terminal for input.
More information may be obtained by examining the accompanying message.
User Action: Correct the error indicated by the accompanying message and
reenter the command.
ERRQIOW,

error from $QIOW

Facility: DEBUG, VMS Debugger
Explanation: A bad status is returned from a call to $QIOW.
User Action: Submit a Software Performance Report.
ERRRECFIL,

error processing /RECORD file

Facility: MONITOR, Monitor Utility
Explanation: An error occurred while referencing the output recording file.
To obtain more information, examine the accompanying linked messages.
User Action: Correct the error indicated by the linked messages and rerun
the MONITOR command.
ERRROUCAL,

error in the routine call

Facility: LIB, Library Facility
Explanation: One or more errors were detected during a call to
LIB$DELETE_FILE or LIB$RENAME_FILE, but a user-specified error routine
is called to handle the conditions. This is an alternate success status.
User Action: None.
ERRSMG,

error returned from a call to the Screen Management Facility (SMG)

Facility: DEBUG, VMS Debugger
Explanation: An invalid status is returned from a call to the Screen
Management Facility. This message may or may not be invoked by the
debugger.
User Action: Check the application program for potential interactions
between it and the debugger, such as pasteboard sharing. Also, check
the setup of the terminal, which might cause a problem for the Screen
Management Facility. If you still do not know why the error occurred, submit
a Software Performance Report.

2-182

Messages

ERRSYMACTIVE,

special error symbol already active

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The special error symbol can only be set once, and it has
already been set.
User Action: Be sure you are the first to set the special error symbol.

ERRSYSINFO,

failed to collect system information on node 'node-name'

Facility: MONITOR, Monitor Utility
Explanation: The Monitor Utility encountered a problem when it attempted
to collect system-specific information from the remote node. This is generally
a network problem.
User Action: Check to make sure that DECNET is up and running on the
remote node. Reenter the MONITOR request.

ERRSYSSERV,

error returned from an internal debugger system service call

Facility: DEBUG, VMS Debugger
Explanation: A bad status is returned from a call to a system service. This
message is displayed in the context of the $DBG-1NFO macro, which lists
the particular system service.
User Action: Submit a Software Performance Report.

ESA,

invalid expanded string address
Facility: RMS, VMS Record Management Services
Explanation: The expanded string area address in the VMS RMS NAM block
is invalid; or the address is in an area of memory that cannot be read or
written by the caller, as required; or the expanded string buffer contains an
invalid file specification.
User Action: Verify that the call to the VMS RMS service is coded correctly.
Check the logical name translation.

ESCAPE,

escape sequence detected

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

ESL,

invalid expanded string length
Facility: RMS, VMS Record Management Services
Explanation: The expanded string length field in the VMS RMS NAM block
contains a value of zero; the attempted operation requires the expanded
string.
User Action: Verify that the call to the VMS RMS service is coded correctly.

2-183

Messages

ESS,

expanded string area too small
Facility: RMS, VMS Record Management Services
Explanation: The user buffer provided to receive an expanded file
specification string is too short; the string does not fit.
User Action: Verify that the call to the VMS RMS service is coded correctly.

ESTABCON,

establishing connection to remote nodes ...

Facility: MONITOR, Monitor Utility
Explanation: Connections to one or more remote nodes are being made.
Connections to remote nodes are made when the /NODE qualifier is used or
when the CLUSTER class is requested. All connections to remote nodes are
made before data collection is initiated.
User Action: None.
EVENT_OCCURRED , event XL occurred with param
Facility: PPL, Parallel Processing Facility
Explanation: This code indicates the occurrence of an event for which
notification has been requested by the user.
User Action: Since the application requested this notification, response is
application-dependent.
EVL,

too many variables: 'string'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: The maximum of 20 variables has been exceeded with the
inclusion of the specified .VARIABLE or conditional command (.IF, .IFNOT,
.ENDIF, or .ELSE); the command in error has been ignored.
User Action: Reduce the number of variables.

EVTSIZ,

an event is too large to translate to DNA form

Facility: EVL, Event Logger
Explanation: A raw event is too large to format properly into DECnet
standard form. Therefore, it is discarded. This is probably caused by a
network software problem.
User Action: Submit a Software Performance Report.
EXARANGE,

invalid range of addresses

Facility: PATCH, Patch Utility and DEBUG, VMS Debugger
Explanation: The range of addresses specified is in the wrong order. The
higher address preceded the lower address.
User Action: Retry using the following format:
lower-boundary-address:upper-boundary-address

2-184

Messages

EXARANGE,

invalid range of addresses

EXASTLM,

exceeded AST quota

Facility: SYSTEM, VMS System Services
Explanation: An image could not continue executing or a command could
not execute because the process exceeded its AST quota.
User Action: If your program fails consistently because of insufficient quotas,
contact your system manager and request that your quotas be increased.

EXBIOLM,

exceeded buffered 1/0 quota

Facility: SYSTEM, VMS System Services
Explanation: An image could not continue to create a subprocess because the
process exceeded its buffered I/O quota.
User Action: If a program fails consistently because of insufficient quotas,
contact your system manager and request that your quotas be increased.

EXBYTLM,

exceeded byte count quota

Facility: SYSTEM, VMS System Services
Explanation: The requested operation failed because the process's byte count
quota is not large enough.

This can occur if excessive concurrent buffered 1/0 is outstanding, if a large
number of mailboxes is created, or if a large number of windows needs to be
created to completely map a file.
Failure on window creation can occur on a $CRMPSC system service call,
the DCL command RUN, or an Access or Create of a file. In this case, this
message indicates that the specified file is very fragmented or the process's
byte limit quota should be increased.
Failure can also occur on a disk read or write operation indicating that a prior
extend operation on the file has caused it to become very fragmented.
User Action: Either compress the file by copying the volume with BACKUP,
or ask the system manager to increase your BYTELIM quota.

2-185

Messages

EXCDURCAL,

error occurred while executing routine called from exception break

Facility: DEBUG, VMS Debugger
Explanation: While executing a routine called from an exception break
using the CALL command, an exception occurred. Any exceptions from
routines called from an exception break cause this message to be displayed,
followed by the text of the exception. Execution of the called routine is then
terminated.
User Action: Either correct the CALL command if it is in error, or correct the
routine that caused the exception. To use the debugger to help find the cause
of the exception, try calling the routine while it is not at an exception break.
EXCPSC,

more than 65535 psects defined in module 'module-name' file 'filename'

Facility: LINK, Linker Utility
Explanation: An object module defines more than 65535 psects.
User Action: Reduce the number of psects in the module and relink.
EXCPUTIM,

CPU time limit expired

Facility: SYSTEM, VMS System Services
Explanation: The user's CPU time limit has expired.
User Action: Request that a larger CPU time quota be assigned from the
system manager and retry the operation.
EXDEPTH,

exceeded allowed depth

Facility: SYSTEM, VMS System Services
Explanation: Either a programming error has occurred or the resource name
tree does not have enough depth. The lock management services allow a
certain depth to the resource name tree that is a function of the interrupt
stack size. If the resource name tree requires more levels, the size of the
interrupt stack must be increased.
User Action: Either correct the programming error or increase the size of the
interrupt stack by increasing the SYSGEN parameter INTSTKP AGES.
EXDIOLM,

exceeded direct I/O quota

Facility: SYSTEM, VMS System Services
Explanation: An image could not continue executing or a command could
not execute because the process exceeded its direct I/O quota.
User Action: If a program fails consistently because of insufficient quotas,
contact your system manager and request that your quotas be increased.
EXDISKQUOTA,

disk quota exceeded

Facility: SYSTEM, VMS System Services
Explanation: The disk quota has been exceeded while attempting to create or
extend a file.
User Action: Reduce disk usage by deleting files or have the system manager
increase the quota.

2-186

Messages

EXEABO,

executor characteristics not defined

Facility: NCP, Network Control Program
Explanation: There is no executor node defined on the local node from
which the NCP command COPY is entered.
User Action: None. This error will not affect the operation of the COPY
command.

EXECUTEFAIL,

execution aborted

Facility: VAXTPU, VAX Text Processing Utility
Explanation: Your program is terminated prematurely because of an error.
User Action: Correct the error in your program and reexecute it.

EXECUTING,

job executing on queue prevents requested operation

Facility: JBC, Job Controller
Explanation: The parameters of the specified job cannot be modified because
the job is currently executing. Or, the specified queue cannot be deleted
because there is a job executing from the queue.
User Action: Reenter the request after the job has completed execution.

EXENQLM,

exceeded enqueue quota

Facility: SYSTEM, VMS System Services and RMS, VMS Record
Management Services
Explanation: You exceeded your ENQLM quota. Since the ENQUEUE quota
is shared by a process and all its subprocesses, any of these processes could
have used the entire quota. Also, the higher the SYSGEN parameter
RMS_DFMBFSUR, the higher the UAF parameter ENQLM must be.
User Action: Either increase the ENQLM quota for your account, log out and
then log in again, and retry the operation; or modify the program to release
locks (RMS record locks or other uses of the $ENQ system service), which
may no longer be required.

EXFILLM, exceeded open file quota
Facility: SYSTEM, VMS System Services
Explanation: An image could not continue executing or a command could
not execute because the process exceeded its open file quota. Since the
FILLM quota is shared by a process and all its subprocesses, any one of these
processes could have used the entire quota.
User Action: If a program fails consistently because of insufficient quotas,
contact your system manager and request that your quotas be increased.

2-187

Messages

EXGBLP AGFIL,

exceeded global page file limit

Facility: SYSTEM, VMS System Services
Explanation: The attempt to allocate a global section with page file backing
store failed because the systemwide limit on these pages is exceeded. No part
of the section is allocated.
User Action: Delete some similar sections or ask the system manager to
increase the SYSGEN parameter GBLP AGFIL. Then, try the operation again.
EXHFUL,

file extension header has no room

process exit handler was not called

Facility: PPL, Parallel Processing Facility
Explanation: An application stopped without executing its PPL$ exit handler.
User Action: The application may require an application-specific recovery
procedure.
EXISTS,

'filespec' already exists

Facility: Shared by several facilities
Explanation: The directory specified in the DCL command CREATE/DIR
already exists. This message is informational.
User Action: None.
EXISTS,

known file entry for a version of this file already exists

Facility: INSTALL, Install Utility
Explanation: A known file entry already exists for this file name on the
specified device and directory.
User Action: Contact your system manager.

2-188

Messages

EXITFAIL,

attempt to EXIT is unsuccessful

Facility: VAXTPU, VAX Text Processing Utility
Explanation: An error occurred during execution of the built-in procedure
EXIT; the procedure did not complete successfully. This usually occurs
because the EXIT procedure could not write the modified buffers. This
message should be accompanied by a message specifying the reason why the
EXIT procedure failed.
User Action: Take corrective action according to the reason for the EXIT
failure; for example, if there is insufficient disk space to create the modified
version of the output file, purge some files to free space on the disk.
EXITING,

editor exiting

Facility: VAXTPU, VAX Text Processing Utility
Explanation: Your program exited from the VAXTPU image.
User Action: None.
EXITSTATUS,

is 'AS'

Facility: PPL, Parallel Processing Facility
Explanation: An application participant exited with this status code.
User Action: Determine the cause of the termination by examining the status
code.
EXITSTATUS,

is 'status_value'

Facility: DEBUG, VMS Debugger
Explanation: The program has exited with the status 'status_value'. See the
VMS System Services Reference Manual for more information about the VMS
exit status codes.
User Action: None.
EXLNMQUOTA,

exceeded the job logical name table

Facility: LOGIN, Login Processor
Explanation: The job logical name table is full. You cannot make further job
logical name assignments.
User Action: Deassign logical names you no longer need to free space in the
table.
If you have sufficient privilege to modify the user authorization file, you can

increase the size of the logical name table with the AUTHORIZE command
MODIFY. The format of the command is:
AUTHORIZE MODIFY username/JTQUOTA=n

The variable n is the size of the job logical name table in bytes. The default
for the job logical name table size is 1024 bytes. The new value takes effect
the next time you log in.
For a detached process, increase the SYSGEN parameter PQL$JTQUOTA.

2-189

Messages

EXP,

file expiration date not yet reached
Facility: RMS, VMS Record Management Services
Explanation: A call to a VMS RMS service attempted to overwrite a magnetic
tape file that is not expired.
User Action: If the file can be overwritten, remount the volume with the
/OVERRIDE=EXPIRATION qualifier. (You must be the owner of the volume
or have the VOLPRO privilege to override the expiration date.) Otherwise,
use another volume.

EXP AGQUO,

exceeded pagefile quota

Facility: LINK, Linker Utility
Explanation: The linker could not expand its virtual address space sufficiently
due to inadequate pagefile quota. Since the PGFLQUOTA is shared by a
process and all its subprocesses, any one of these processes could have used
all the quota.
User Action: If the link fails consistently because of insufficient quotas,
contact your system manager and request that your quota be increased.
EXP ANDPHD,

expand process header error

expression too complex

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The expression is too complex.
User Action: Break up the expression into simpler expressions.
EXPECTED,

one of the following symbols is expected:

Facility: VAXTPU, VAX Text Processing Utility
Explanation: You have a syntax error in your program. One of the symbols
listed is expected but not found.
User Action: Correct the syntax error and recompile your program.

2-190

Messages

EXPGFLQUOTA, exceeded pagefile quota
Facility: SYSTEM, VMS System Services
Explanation: An image could not continue executing or a command could
not execute because the process exceeded its pagefile quota. Since the
PGFLQUOTA is shared by a process and all its subprocesses, any one of
these processes could have used the entire quota.
User Action: If a program fails consistently because of insufficient quotas,
contact your system manager and request that your quotas be increased.
EXPIRED,

this product has expired after VMS Version nnn. Please contact your
local DIGITAL sales representative.

Facility: VMSINSTAL, Install Procedures
Explanation: The product cannot be installed on the current version of the
VMS operating system. The product has been restricted to versions lower
than the version specified in the message.
User Action: Contact your local DIGITAL sales representative.
EXPORTQUOTA,

port's quota exceeded

Facility: SYSTEM, VMS System Services
Explanation: The quota permitted by processes on this port of a multiport
(shared) memory has been exceeded.
User Action: Wait until other processes release the required resource, or
reboot VMS and reconnect shared memory specifying a larger quota.
EXPOVR32,

expression overflowed 32 bits

Facility: MACRO, VAX MACRO Assembler
Explanation: The value of the expression could not be stored in a longword
(32 bits). The assembler truncated the value to 32 bits.
User Action: Change the values in the expression.
EXPRCLM,

exceeded subprocess quota

Facility: SYSTEM, VMS System Services
Explanation: An image could not continue executing or a command could
not execute because the process exceeded its subprocess limit.
User Action: If a program fails consistently because of insufficient quotas,
contact your system manager and request that your quotas be increased.
EXPREG,

error code of 'xx' expanding program region

Facility: PATCH, Patch Utility
Explanation: The system service $EXPREG request failed due to the error
represented as 'xx'.
1

User Action: Correct the error (represented as 'xx and retry.
)

2-191

Messages

EXPSHRPAT,

attempt to expand patch area for shareable image

Facility: PATCH, Patch Utility
Explanation: The patch area cannot be created for shareable images.
User Action: Relink the shareable image instead of patching it.

EXPSTKOVR,

expression too nested, stack overflow

Facility: PATCH, Patch Utility
Explanation: You attempted to evaluate an expression that contained more

than 16 levels of nested arguments.
User Action: Remove levels of nested arguments until you have 16 levels or
less and retry the operation.

EXPSYN,

invalid expression syntax-check operators and operands

Facility: CLI, Command Language Interpreter (DCL)
Explanation: An arithmetic expression in a DCL command is not syntactically
correct; the command interpreter cannot analyze the expression. An invalid
expression can occur as a result of:

•

Missing operators between values or symbol names

•

Unmatched parentheses

•

Undefined symbol names that are being interpreted as character string
data

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

EXPTOOCOM,

expression is too complex

Facility: SMG, Screen Management Facility
Explanation: The expression is too complex for the termtable compiler to

parse.
User Action: Modify the expression so that it is less complex.

EXPVIR,

error allocating virtual memory

Facility: FDL, Create/FDL Utility
Explanation: This message will be accompanied by a system error message

that explains the error.
User Action: Correct the error described in the system error message and try
again.

2-192

Messages

EXQUOTA,

exceeded quota

Facility: SYSTEM, VMS System Services
Explanation: An image could not continue executing or a command could
not execute because the process exceeded one of its resource quotas or limits.
If this message is associated with a status code returned by a request to a

DR32 interface, a DRll-W interface, or an LPAll-K driver, the AST quota
for the requesting process is exceeded. In the latter case, an AST cannot be
queued for a buffer full/empty AST. Normally, a start data transfer request
can require no more than three AST blocks at a time.
If this message is associated with a status code returned by a request to a

DUPl 1 interface, a request cannot be queued because the buffered 1/0 quota
is exceeded.
This message can indicate failure to create a subprocess because deductible
quotas, when subtracted from the current quotas of the creator, would not
leave the minimum required quotas for the creator.
This message may also occur if the size of a buffered 1/0 request exceeds the
value of the SYSGEN parameter MAXBUF.
User Action: Use the DCL command SHOW PROCESS /QUOTAS to
determine the current quotas and to determine which quota is exceeded.
Determine whether any subprocesses are hibernating and are no longer
performing useful functions; delete any such subprocesses.
If a program fails consistently because of insufficient quotas, contact your

system manager and request that your quotas be increased.
EXT,

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

EXTBIT, illegal extract bit number-greater than 31
Facility: PATCH, Patch Utility
Explanation: You specified an illegal bit number; legal bit numbers range
from 0 to 31 inclusive.
User Action: Retry the operation specifying a legal bit number.

2-193

Messages

EXTCACHIV,

contents of extent cache is garbage

unable to extend work file for needed space

Facility: SORT, Sort/Merge Utility
Explanation: SORT failed to extend your temporary work file. Either the
device is full or you have reached your disk quota limit.
User Action: Reassign work files to a different device with more space or
have the system manager extend your quota.
EXTENDED,

'filespec' extended

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

unable to extend output file

Facility: CONVERT, Convert Utility
Explanation: The size of the input file exceeded the initial allocation of the
output file, and when CONVERT tried to extend the file, an error occurred.
This message will be accompanied by an RMS error message that explains the
error.
User Action: Correct the error described in the RMS error message and try
again.
EXTNOTFOUND,

extension 'extension-name' not found

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The named extension to VAXTPU cannot be located.
User Action: Install the named extension before trying to use it.

2-194

Messages

EXTQELM, exceeded timer queue entry quota

Facility: SYSTEM, VMS System Services
Explanation: An image could not continue executing or a command could
not execute because the process exceeded its timer queue entry quota.
Since the TQELM quota is shared by a process and all its subprocesses, any
one of the processes could have used all the quota.
User Action: If a program fails consistently because of insufficient quotas,
contact your system manager and request that your quotas be increased.
EXTRACTED,

module 'module-name' extracted from 'library-filespec'

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

extraneous .ENDM in 'library-filespec'

Facility: LIBRAR, LIBRARY Command
Explanation: This warning message is generated by the DCL command
LIBRARY. The specified library contains a .ENDM line that does not terminate
any macro.
User Action: Reformat the macro source file.
EXTRAP ARM,

superfluous parameter detected

Facility: AUTHORIZE, Authorize Utility
Explanation: You have specified too many parameters in the command line.
The extra parameter is identified in the message.
User Action: Reenter your command without the excess parameter.
FAB,

file aborted

Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: DSR has aborted the file for internal reasons. This is a DSR
internal error.
User Action: Submit a Software Performance Report.
FAB, invalid FAB or FAB not accessible

Facility: RMS, VMS Record Management Services
Explanation: Either the specified VMS RMS block identifier field does not
indicate that the field is a FAB, or the FAB is not in a portion of memory that
can be written to by the caller.
User Action: Verify that the call to the VMS RMS service is coded correctly.
An attempt may have been made to perform file operations with a RAB.
Verify that the FAB is properly initialized and that the block identifier field is
not overwritten during execution of the program image.

2-195

Messages

FAC,

record operation not permitted by specified file access (FAC)
Facility: RMS, VMS Record Management Services
Explanation: A record operation is attempted that is not indicated in the file
access field of the FAB for the file. For example, to delete a record, the DEL
option must have been specified in the FAC field when the file is opened or
created.
If the error results from the DCL command READ or WRITE, this message
indicates either the DCL command WRITE is entered for a file opened for
reading, or the DCL command READ is entered for a file opened for writing.

User Action: If the error occurred during execution of an image, verify that
the FAC parameter in the FAB indicates the requested type of access.
If the error occurred during use of the DCL commands, verify that the correct
qualifier is specified when the DCL command OPEN is entered to open the
file.

FACOVFL,

facility table overflow in section-please submit SPR

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

FACTBAD,

cannot read factory bad block data

Facility: INIT, INITIALIZE Command and BACKUP, Backup Utility
Explanation: Either the DCL command INITIALIZE or the Backup Utility
encountered an error during an attempt to read the bad block data recorded
on the specified volume. An accompanying message provides additional
information.
User Action: Either correct the condition that caused the error and reenter
the command or notify the system manager. If the volume is under warranty,
it should be returned to the factory. Contact a DIGITAL field service
representative if necessary.

FACTOOLONG,

facility name, 'name', exceeds maximum length 'integer'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The facility name you want to use is longer than the maximum
allowed length.
User Action: Use a shorter facility name.

FAIL,

failed to 'execute-verb' entry for 'filespec'

Facility: INSTALL, Install Utility
Explanation: A failure to ADD, CREATE, DELETE, REMOVE, or REPLACE
a known file entry occurred. An accompanying error message explains the
failure.
User Action: Correct the situation indicated by the accompanying error
message and reenter the command.

2-196

Messages

FAILED,

failed to perform 'execute-verb' operation

Facility: INSTALL, Install Utility
Explanation: A PURGE or listing operation failed to execute completely. An
accompanying message explains the failure.
User Action: Correct the situation indicated by the accompanying error
message and reenter the command.

Failed to Locate Port Micro-code Image
Facility: VAXport, VAXport Driver
Explanation: The port driver will not start the port.
User Action: Make sure that the console load media is present in the console
drive, and reboot the system.

FAILFREVM,

failed to deallocate 'number' bytes of virtual memory

Facility: CNF, NI Configurator
Explanation: An error occurred when NICONFIG attempted to deallocate
virtual memory.
User Action: Check the accompanying error message to determine
whether the virtual address space is exceeded, or whether a program
error is uncovered. An invalid address or size for deallocation indicates a
programming error.

FAILGETVM,

failed to allocate 'nn' bytes of virtual memory

Facility: INSTALL, Install Utility
Explanation: INSTALL failed to allocate sufficient work space for itself.
User Action: Either your PGFLQUO value is too low for your account, or the
system's VIRTUALPAGECNT SYSGEN parameter is too low. Contact your
system manager.

FAILGETVM,

failed to allocate 'number' bytes of virtual memory

Facility: CNF, NI Configurator
Explanation: An error occurred when NICONFIG attempted to allocate
virtual memory.
User Action: Check the accompanying error message to determine whether
the virtual address space is exceeded, or whether a program error is
uncovered. An invalid address or size for allocation indicates a programming
error.

FAILURE,

internal VAXTPU failure detected at PC 'address'

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

2-197

Messages

FAIQPEFIL,

failed to open file 'filename'

Facility: SMG, Screen Management Facility
Explanation: The Termtable compiler could not open the file specified in a
REQUIRE statement.
User Action: Make sure that the specified file exists and that you have read
access to it.
FAQ,

error formatting report information
Facility: BAD, Bad Block Locator Utility
Explanation: An error is encountered during an FAQ formatting operation.
User Action: Copy all pertinent diagnostic message information and submit a
Software Performance Report.

FAQBUG,

FAQ system service failure

Facility: LINK, Linker Utility, CREF, Cross-Reference Utility, LIBRAR,
LIBRARY Command
Explanation: An error is returned by the $FAQ system service.
User Action: Submit a Software Performance Report.
FAQFAIL,

FAQ failure

Facility: CREF, Cross-Reference Utility, and LINK, Linker Utility
Explanation: An error is returned by the $FAQ system service.
User Action: Ensure that the field descriptor FAQ control strings are correct.
FAQFAIL,

FAQ system service failure

Facility: LIBRAR, LIBRARY Command
Explanation: An unexpected internal consistency check occurred.
User Action: Contact your system manager and submit a Software
Performance Report.
FATALERR, fatal error on 'save-set-spec'
Facility: BACKUP, Backup Utility
Explanation: The Backup Utility encountered an irrecoverable error during
an attempt to read or write the specified save set. The accompanying message
provides additional information.
User Action: Correct the condition that caused the error and reenter the
command.
FATALERRQR,

fatal error message issued

Facility: LINK, Linker Utility
Explanation: The linker issued a fatal error message in the link.
User Action: Correct the problem and relink.

2-198

Messages

FATALEXC,

fatal exception encountered

Facility: CONVERT, Convert Utility
Explanation: This message appears if an exception record is encountered and
if you have specified the /EXIT qualifier.
User Action: Specify either /TRUNCATE or /PAD, or else specify /NOEXIT.

FATALEXCPT,

fatal executive or kernel mode exception

Facility: BUGCHECK, System Bugcheck
Explanation: The VMS software detected an unrecoverable, inconsistent
condition. After all of physical memory is written to a system dump file, the
system will automatically reboot if the BUGREBOOT system parameter is set
to 1.
User Action: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error, and that includes a BACKUP save set
containing the system dump file and the error log file active at the time of the
error. (Use the /IGNORE=NOBACKUP qualifier on the BACKUP command
that produces the save set included with the SPR.)

FATERRLIB, fatal error in library
Facility: DTK, DECtalk Facility
Explanation: An internal error occured in the DECtalk device.
User Action: Submit a Software Performance Report describing the problem.

FATERRLIB, fatal error in library
Facility: LIB, Library Facility
Explanation: An internal consistency check failed in the VMS Run-Time
Library. This usually indicates a programming error in the Run-Time Library.
User Action: Submit a Software Performance Report.

FATERRLIB, fatal error in library
Facility: SMG, Screen Management Facility
Explanation: An internal error has occurred within the Screen Management
Facility.
User Action: Submit a Software Performance Report describing the problem.

FATINTERR, fatal internal error in Run-Time Library
Facility: OTS, General Purpose Facility, and STR, String Manipulation
Facility
Explanation: An explicit or implicit call to the VMS Run-Time Library
resulted in the failure of an internal consistency check.
User Action: Rerun your program. Collect as much information as possible,
including the system traceback listing, and submit a Software Performance
Report.

2-199

Messages

FAU,

flag character 'character' already in use
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: You attempted to define a character as a flag character;
however, the character has already been defined.
User Action: Use another character as a flag character.

FCPREADERR,

file processor read error

Facility: SYSTEM, VMS System Services
Explanation: An I/O error occurred when file structure data, for example, a
directory, is being read.
User Action: Examine the error log and correct the hardware problem if
necessary.
FCPREPSTN,

file processor reposition error

Facility: SYSTEM, VMS System Services
Explanation: An I/O error occurred during an attempt to reposition a tape
volume after it had gone off line.
User Action: Examine the error log and correct the hardware problem if
necessary.
FCPREWNOERR,

file processor rewind error

Facility: SYSTEM, VMS System Services
Explanation: An I/O error occurred when a volume is being rewound.
User Action: Examine the error log and correct the hardware problem if
necessary.
FCPSP ACERR,

file processor space error

Facility: SYSTEM, VMS System Services
Explanation: An I/O error occurred while spaces were being skipped within
a file or files. The operating system does not normally display this message.
User Action: Examine the error log and correct the hardware problem if
necessary.
FCPWRITERR,

file processor write error

Facility: SYSTEM, VMS System Services
Explanation: An I/O error occurred when file structure data, for example, a
directory, is being written.
User Action: Examine the error log and correct the hardware problem if
necessary.
FDLERROR,

error parsing FOL file

Facility: FOL, Edit/FOL Utility
Explanation: This message is issued with an accompanying message.
User Action: Take corrective action based on the accompanying message.

2-200

Messages

FDLP AR,

error parsing FDL file

Facility: FDL, Edit/FDL Utility
Explanation: An error occurred during the parsing of the FDL file. This
message is issued with an accompanying message.
User Action: Take corrective action based on the accompanying message and
try again.
FEL,

'flag-name' flag at end of line ignored
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: This flag cannot occur at the end of a line.
User Action: Remove the flag from the end of the line.

FEX,

file already exists, not superseded
Facility: RMS, VMS Record Management Services
Explanation: An attempt is made to create or rename a file with the same file
specification as an existing file in the volume set.
User Action: Choose a different file specification; delete the existing file (if a
new one is to be created); or use the SUP option in the FOP parameter in the
FAB to request that an existing file be superseded.

FIDERROR,

unexpected file change in 'filespec'

Facility: BACKUP, Backup Utility
Explanation: A file boundary marker is missing from the input save set. Data
in the save set may be corrupted. It is likely that parts of the specified file
and one or more complete files are missing.
User Action: Examine the file for corruption and reconstruct as necessary. If
this error occurs during a disk-to-disk (copy) operation, it indicates a software
error in the Backup Utility; in this case, submit a Software Performance
Report.
FIDNOTFND, internal error. File to be processed not found on process list
Facility: BACKUP, Backup Utility
Explanation: The file context has been lost. This is an internal error.
User Action: If this error can be reliably reproduced, the BACKUP command
used and a description of the circumstances should be submitted along with a
Software Performance Report.
FIELDLIM,

number of fields in range exceeds limit

Facility: NCP, Network Control Program
Explanation: The channel list supplied in the command is invalid. Channel
lists may have eight fields, separated by commas. The last field cannot be a
hyphenated range.
User Action: Correct the channel list.

2-201

Messages

FILl l_NOREC,

ignoring /RECORD_FORMAT for Files-11 output

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility does not support the /RECORD_
FORMAT option on Files-11 output files.
User Action: Leave the qualifier off. If the output file is not in the desired
format, use the VMS CONVERT utility to change the format of the file.
FILACCERR, magnetic tape file access is nonblank
Facility: SYSTEM, VMS System Services
Explanation: The accessibility characteristic in the HDRl label is not blank
and the file cannot be accessed without overriding the field.
User Action: Mount the magnetic tape with the
/OVERRIDE=ACCESSIBILITY qualifier. (The VOLPRO privilege is required
or you must be the owner of the tape.) Otherwise, use another volume.
FILADDED,

added component file to phase

Facility: SYSMAN, Cluster System Management Utility
Explanation: The named startup component file is added to the named
phase.
User Action: Verify that the listed file name and phase are correct.
FILALRACC,

file already accessed on channel

Facility: SYSTEM, VMS System Services
Explanation: The request failed because the channel over which the $QIO
10$_ACCESS request is issued already had either a file or logical link
accessed on it.
User Action: Check for a programming error.
FILAREDIF,

files are different

Facility: DIFF, DIFFERENCES Command
Explanation: The two files being compared are different. This is an
informational message.
User Action: None.
FILCNTNONZ,

open file count nonzero after process rundown

2-202

Messages

FILDISABL,

component file updated

Facility: SYSMAN, Cluster System Management Utility
Explanation: The named startup component file is disabled on the specified
node.
User Action: Verify that the listed file name is correct.
File attributes error
Facility: EDT, EDT Editor
Explanation: The file cannot be edited by EDT because of its attributes.
User Action: None. The file cannot be edited.
File specification required
Facility: EDT, EDT Editor
Explanation: You did not specify a file name (or file specification) with an
INCLUDE, PRINT, or WRITE command.
User Action: Reenter the command including the correct file specification.
FILEACC,

error accessing system authorization file

Facility: LOGIN, Login Processor
Explanation: An error occurred while attempting to access the authorization
file. An accompanying message will provide more information.
User Action: Correct the problem described by the accompanying message,
and try again.
FILECONVERTED, file format is being converted to a supported type
Facility: VAXTPU, VAX Text Processing Utility
Explanation: The buffer being written is created from a file that had
nonstandard attributes. The output file being created does not have the
attributes of th~ input file; it is created with standard attributes (VARIABLE
with CR record attributes).
User Action: None.
FILEGONE,

startup component database is missing

Facility: SMI, System Management Intergator/Server
Explanation: The current startup component database does not exist.
User Action: To create a new database, use the STARTUP CREATE
command at the SYSMAN> prompt.
To select a different component database, use the STARTUP SET DATABASE
command at the SYSMAN> prompt.

2-203

Messages

FILEIN,

'count' lines read from file 'filename'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: VAXTPU opened the named file and read the indicated number
of lines from that file into a buffer.
User Action: None.

FILEIO,

file 1/0 error 'filename'

Facility: NCP, Network Control Program
Explanation: An error occurred during file input or output; for example, a
system image file could not be read. An accompanying VMS RMS message
should identify the reason for the error (such as a protection violation if the
file is protected against read access).
User Action: Take corrective action based on the VMS RMS message.

FILE LOCKED,

file is deaccess locked

Facility: SYSTEM, VMS System Services
Explanation: The program attempted to access a locked file. A file becomes
locked when it is accessed with FIB$M_DLOCK (bit) set and then deaccessed
without writing attributes.
User Action: Unlock the file with the DCL command UNLOCK and examine
it for inconsistency.

FILEMPTY,

file 'filename' has no folders

Facility: MAIL, Mail Utility
Explanation: A DIR/FOLDER command is entered, but the current mail file
has no folders and, therefore, no messages.
User Action: None.

FILENABL,

component 'filename' updated

Facility: SYSMAN, Cluster System Management Utility
Explanation: The named startup component file is enabled on the specified
node.
User Action: Verify that the listed file name is correct.

FILENOTFOUND,

unable to locate file 'filename'

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility could not find the listed input file.
User Action: Check the command for a misspelling error, or reenter the
command specifying the correct location for the input files.

2-204

Messages

FILENUMCHK,

file identification number check

Facility: SYSTEM, VMS System Services
Explanation: The volume index file may be corrupted.
The file number in the file header that is read is invalid. The disk's file
structure is damaged.
User Action: Repair the volume with the Verify Utility.
FILEOUT,

'count' lines written to file 'filename'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: VAXTPU wrote the indicated number of lines from a buffer into
the named file.
User Action: None.
FILEPURGED,

oldest file version purged

Facility: SYSTEM, VMS System Services
Explanation: The newly created file version exceeded the maximum number
of versions of that file; the oldest file version is deleted. This message is
informational.
User Action: None.
FILESEQCHK,

file identification sequence number check

Facility: SYSTEM, VMS System Services
Explanation: The file sequence number in the file header is not the one
expected. A directory entry points to a file that is deleted.
User Action: Remove the directory entry with the following command line:
DELETE filespec

FILESTRUCT,

unsupported file structure level

Facility: SYSTEM, VMS System Services
Explanation: The file structure on the accessed volume is not compatible
with the ACP, or the file structure may be corrupt.
User Action: Verify that the correct physical volume is mounted. Or repair
the volume with the Verify Utility. If the volume is new and does not contain
data, use the DCL command INITIALIZE to initialize the volume in the
correct format.
FILETOOLONG,

file only partially installed

Facility: SYSGEN, System Generation Utility
Explanation: The SYSGEN command INSTALL failed. The /SIZE qualifier
specified with the SYSGEN command CREATE is larger than the maximum
allowed.
User Action: Specify a smaller /SIZE qualifier with the CREATE command.

2-205

Messages

FILLIM, exceeded open file limit
Facility: CONVERT, Convert Utility
Explanation: SORT exceeded the process open file limit.
User Action: Increase the FILLM parameter in the user authorization record.

FILMODIFD,

component 'filename' modified

Facility: SYSMAN, Cluster System Management Utility
Explanation: The named startup component file is modified as directed by
user.
User Action: Verify that the listed file name is correct.

FILNOPOST,

file will not be subject to date-recording or deletion

Facility: BACKUP, Backup Utility
Explanation: This is a warning message indicating that BACKUP will not
post-process the file because its contents were not successfully verified.
User Action: Determine why the file could not be successfully verified and
retry the BACKUP operation.

FILNOTACC,

file not accessed on channel

Facility: SYSTEM, VMS System Services
Explanation: The process is trying to read or write to a channel that does not
have a file accessed on it.
User Action: Modify the source program to correct the problem.

FILNOTCNTG,

file is not contiguous as required

Facility: SYSTEM, VMS System Services
Explanation: A system file that must be in contiguous disk format is not
contiguous.
User Action: Use the DCL command COPY /CONTIGUOUS to make a new
contiguous version of the file.

FILNOTDEL,

error deleting 'filespec'

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

2-206

Messages

FILNOTEXP,

file is not expired

Facility: MOUNT, Mount Utility and SYSTEM, VMS System Services
Explanation: A tape file cannot be overwritten because it has not reached its
expiration date.
User Action: To overwrite or delete the file, mount the volume with the
/OVERRIDE=EXPIRATION qualifier. You must be the owner of the volume
or have volume protection (VOLPRO) privilege.
FILNOTFND,

component file not found

Facility: SMI, System Management Intergator/Server
Explanation: A search for startup component files matching a given search
string found no matching entries.
User Action: Reenter the command with a different file parameter.
FILNOTPUR,

error deleting 'filespec'

Facility: Shared by several facilities
Explanation: An error is detected during an attempt to delete the specified
file. A subsequent message explains the reason for the error.
User Action: Take corrective action based on the accompanying message.
FILOPE,

file open error, 'name of file'

Facility: NCP, Network Control Program
Explanation: Your command could not open the specified file. An
accompanying VMS RMS message should specify why the file could not be
opened; for example, the file could not be found. The 'name of file' identifies
the file that could not be opened, for example, the permanent database file.
User Action: Take corrective action based on the RMS message. For instance,
if a file cannot be found, determine whether it exists and whether it is located
in the proper directory.
FILPURGED,

'filespec' deleted

Facility: Shared by several facilities
Explanation: The DCL command PURGE displays the file specification of a
file it is deleting. This message is informational.
User Action: None.
FILREMOVED,

component file removed from phase

Facility: SYSMAN, Cluster System Management Utility
Explanation: The named startup component file is removed from the
specified phase.
User Action: Verify that the listed file name is correct.

2-207

Messages

FILREQD,

/FILENAME is required with the RMS class

Facility: MONITOR, Monitor Utility
Explanation: The RMS class requires a file specification for live monitoring.
User Action: Reenter the MONITOR command with a file specified with the
/FILENAME qualifier.
FILTOOLON,

file specification is too long (over 255 characters)

Facility: DTK, DECtalk Facility
Explanation: The file specification is too long.
User Action: Correct your program so that it requests a file name of 255
characters or fewer.
FILTRNERR,

input RMS file name is not unique across the CLUSTER

Facility: MONITOR, Monitor Utility
Explanation: A single file name specified with the /FILENAME qualifier for
the RMS class translated to a different file on one or more requested nodes.
A single file specification must locate the same file on all nodes requested.
User Action: Reenter the MONITOR command with a file specification which
is unique across the cluster.
FINDHOME,

no valid home block, RVN 'n'

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility could not locate a valid home block on the
specified relative volume.
User Action: If the volume can no longer be mounted by the operating
system, it is corrupted and must be reconstructed from backup media. If the
volume can be mounted, this message indicates a software error in the Verify
Utility. In this case, submit a Software Performance Report.
FINDIHD,

no valid index file header, RVN 'n'

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that both the primary and alternate
index file headers were corrupted.
User Action: If the volume can no longer be mounted by the operating
system, it is corrupted and must be reconstructed from backup media. If the
volume can be mounted, this message indicates a software error in the Verify
Utility. In this case, submit a Software Performance Report.
FINISHED,

task completed

Facility: UETP, User Environment Test Package
Explanation: A module in the UETP completed, but errors may have
occurred during its execution.
User Action: None.

2-208

Messages

FIRSTM OD,

first input file being a library requires module extraction

Facility: LINK, Linker Utility
Explanation: No input files were specified, and the first file is a library file
with no explicit module extraction.
User Action: Reenter the command, specifying an input file, or use the
/INCLUDE qualifier on the library file.
FLAGTRUNC,

value of message flags exceeds maximum value 15, truncated

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The message flags value should be less than or equal to 15.
The procedure for writing the messages uses only the low four bits of the
value.
User Action: Refer to the material on SET (MESSAGE_FLAGS, ... ) in the
VAX Text Processing Utility Manual for the proper values to specify.
FLG,

invalid key definition flags for key= 'nnn'
Facility: RMS, VMS Record Management Services
Explanation: Either XAB$V_CHG or XAB$V__NUL is incorrectly specified for
the primary key definition XAB, or a reserved key definition flag is specified.
User Action: The status value (STV) field of the FAB provides the key of
reference of the XAB in error. Verify that the call to the VMS RMS service is
coded correctly.

FLK,

file currently locked by another user
Facility: RMS, VMS Record Management Services
Explanation: An attempt to open or create a file failed. Another user has the
file open in a mode incompatible with the attempted access.
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 for all users that
need to access the file. If the file cannot be shared, modify the program to
detect and respond to the condition by waiting.

FLOOVEMAT,

floating overflow in math library-user PC location

Facility: MTH, Mathematics Facility
Explanation: An overflow condition occurred during execution of a math
library procedure. This message results from an incorrect call to the math
library, and usually indicates that an argument is too small or too large.
User Action: Use the traceback information and PC displayed in the message
to locate where your program called the math library.

2-209

Messages

FLOUNDMAT, floating underflow in math library-user PC location
Facility: MTH, Mathematics Facility
Explanation: An underflow condition occurred during execution of a math
library procedure and the caller is enabled for floating underflow traps.
This message results from an incorrect call to the math library. Refer to the
discussion of the LIB$FL T_UNDER procedure in the VMS Run-Time Library
Routines Volume.
User Action: Locate the statement in your program where you called the
math library causing the underflow condition to occur.
FLTDIV,

arithmetic trap, floating/decimal divide by zero at PC= 'xxxxxxxx', PSL
= 'xxxxxxxx'

Facility: SYSTEM, VMS System Services
Explanation: An arithmetic exception condition occurred as a result of an
attempt to divide a floating point/ decimal number by zero.
User Action: Examine the PC location displayed in the message; check the
program listing to verify that operands or variables are specified correctly.
FLTDIV_F,

arithmetic fault, floating divide by zero at PC = 'xxxxxxxx', PSL =
'xxxxxxxx'

Facility: SYSTEM, VMS System Services
Explanation: During a floating-point operation, an attempt is made to divide
by zero.
User Action: Examine the PC location displayed in the message; check the
program listing to verify that operands or variables are specified correctly.
FLTOVF,

arithmetic trap, floating overflow at PC= 'xxxxxxxx', PSL = 'xxxxxxxx'

Facility: SYSTEM, VMS System Services
Explanation: An arithmetic exception condition occurred as a result of a
floating-point overflow.
User Action: Examine the PC location displayed in the message; check the
program listing to verify that operands or variables are specified correctly.
FLTOVF_F,

arithmetic fault, floating overflow at PC= 'xxxxxxxx', PSL = 'xxxxxxxx'

Facility: SYSTEM, VMS System Services
Explanation: During an arithmetic operation, a floating-point value exceeded
the largest representable value for that data type.
User Action: Examine the PC location displayed in the message; check the
program listing to verify that operands or variables are specified correctly.
FL TPNTSYNX,

floating point syntax error

Facility: MACRO, VAX MACRO Assembler
Explanation: A floating-point constant contained a syntax error.
User Action: Correct the syntax of the constant.

2-210

Messages

FLTUND,

arithmetic trap, floating underflow at PC= 1xxxxxxxx 1, PSL = 1xxxxxxxx 1

Facility: SYSTEM, VMS System Services, LIB, Library Facility
Explanation: An arithmetic exception condition occurred as a result of
floating-point underflow.
User Action: Examine the PC location displayed in the message; check the
program listing to verify that operands or variables are specified correctly.

FLTUND_F, arithmetic fault, floating underflow at PC= xxxxxxxx PSL =
xxxxxxxx
1

Facility: SYSTEM, VMS System Services
Explanation: During an arithmetic operation, a floating-point value became
less than the smallest representable value for that data type.
User Action: Examine the PC location displayed in the message; check the
program listing to verify that operands or variables are specified correctly.

FLUSH,

output stream flush requested

Facility: PSM, Print Symbiont
Explanation: This status is returned by a print symbiont output routine
requesting the output stream be flushed.
User Action: None.

FNA,

flag not allowed in this context: 1string 1
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: (1) A flag is used that requires that text directly precede or
follow it; or (2) a flag character is replaced by another character (by means of
a .FLAGS command) and the previous function of the replacement has not
been disabled (by means of a .NO FLAGS command).
User Action: Check your usage of the flag, and make the appropriate
correction.

FNA,

invalid file name string address
Facility: RMS, VMS Record Management Services
Explanation: Either the file specification string address field in the FAB is
incorrect, or is in a portion of memory that cannot be read by the caller.
User Action: Verify that the call to the VMS RMS service is coded correctly.
Specifically, check that the address specified points to the correct string.

FND,

ACP file or directory lookup failed
Facility: RMS, VMS Record Management Services
Explanation: An error occurred during a directory search. This message is
associated with a system status code returned from a file system ACP QIO
request made by VMS RMS.
User Action: The status value (STV) field of the FAB contains a system status
code that provides more information about the condition. Take corrective
action based on this status code.

2-211

Messages

FNF,

file not found

Facility: RMS, VMS Record Management Services
Explanation: The specified file does not exist.
User Action: Check the file specification and verify that the device, directory,
file name, and file type were all specified correctly. If a logical name is
specified, verify the current equivalence assigned to the logical name. If
the equivalence is correct, verify that the correct volume is mounted on the
specified device and that the file is not inadvertently deleted. Specify the
existing file.
FNF,

file not found

Facility: SYSGEN, System Generation Utility
Explanation: SYSGEN is unable to locate the driver image file. The default
directory and disk device for driver images is SYS$SYSTEM. This message is
also produced during an AUTOCONFIGURE operation if a UNIBUS device
does not have a corresponding driver in SYS$SYSTEM.
User Action: Restore the image file to the system disk from a backup disk.
FNM,

error in file name

Facility: RMS, VMS Record Management Services
Explanation: The file name portion of a file specification is specified
incorrectly. For example, the file name contains more than 39 characters.
Or the use of a logical name resulted in more than one file name in the file
specification.
User Action: Verify the syntax of the file name in the file specification or in
the logical name, if a logical name is specified.
FOP,

invalid file options

Facility: RMS, VMS Record Management Services
Explanation: The file options parameter in the FAB contains conflicting
options. In particular, the UFO or NFS options were specified on an indirect
open of a process permanent file.
User Action: Verify that the call to the VMS RMS service is coded correctly.
FORCEDERROR,

forced error flagged in last sector read

Facility: SYSTEM, VMS System Services
Explanation: This message applies only to devices governed by the Mass
Storage Control Protocol (MSCP). The data in this sector is copied from
another sector that had unrecoverable read errors. This data is written with
the Forced Error Indicator set to show to subsequent readers that the data is
questionable.
User Action: Be aware that the contents of the sector are only a close
approximation of the data. Use the Backup Utility to make a copy of the
original file and recover its contents.

2-212

Messages

FORCEDEXIT,

forced exit of image or process by Job Controller

Facility: SYSTEM, VMS System Services
Explanation: When the job controller detects a violation of the login hour
restrictions specified in the authorization record for a user, the job controller
forces the process to terminate.
User Action: See your system manager.
FORMAT,

file has illegal format

Facility: LINK, Linker Utility
Explanation: This is a secondary message indicating the object file in
question has an illegal format.
User Action: Correct the source, recompile, and relink.
FORMAT,

invalid media format

Facility: SYSTEM, VMS System Services
Explanation: An I/O operation failed because the data medium is not in a
format that the device driver expected. If this message is associated with a
status code returned by a request to a magtape, the format specified by the
last set tape characteristics function is not implemented in the slave controller.
User Action: Verify the physical data pack, reel, or cartridge to ensure
that the correct data medium is mounted. Contact a DIGITAL field service
representative if necessary.
FORWLOOP,

infinite forwarding detected sending to user 'username'

Facility: MAIL, Mail Utility
Explanation: A forwarding loop is created. This message is generated after
the Mail Utility has gone through the loop ten times.
User Action: Determine what caused the loop.
FREEBADBUF,

attempted to free busy (or free) buffer

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

error freeing virtual memory

Facility: BACKUP, Backup Utility and VERIFY, Verify Utility
Explanation: Either the Backup Utility or the Verify Utility encountered an
error during an attempt to free dynamic virtual memory. The accompanying
message provides additional information. This message indicates a software
error in either the Backup Utility or the Verify Utility.
User Action: Submit a Software Performance Report.

2-213

Messages

FREEMEM,

memory deallocation failure

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

free page reference count is nonzero

deallocated 'number' bytes of virtual memory leaving 'number'

Facility: CNF, NI Configurator
Explanation: The VM bit is set in NICONFIG$LOG. Virtual memory has
been deallocated and the amount is tallied.
User Action: None.
FRERANGE,

storage package range error

Facility: PATCH, Patch Utility
Explanation: An internal error has occurred.
User Action: Submit a Software Performance Report.
FRESIZE,

storage package size error

Facility: PATCH, Patch Utility
Explanation: An internal PATCH error has occurred.
User Action: Submit a Software Performance Report.
FREWSLX,

free working set list index, resource wait

2-214

Messages

FROMBUILTIN,

called from built-in 'built-in-name'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: This message shows the name of the built-in calling the code
that generated the error.
User Action: None.

FROMLINE,

called from line 'integer'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: This message shows the line number where the error occurred.
User Action: None.

FROMPROCLINE,

called from line 'integer' of procedure 'name'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: This message shows the line number within procedure of the
caller where the error occurred.
User Action: None.

FSZ, invalid fixed control header size
Facility: RMS, VMS Record Management Services
Explanation: The fixed control area size of the FAB for the file does not
contain the correct value. Files that have the print file record format must
have an FSZ value of 2.
User Action: Verify that the call to the VMS RMS service is coded correctly.

FTM,

network file transfer mode precludes operation (SQO set)
Facility: RMS, VMS Record Management Services
Explanation: For network file access, the FAB file option SQO selects DAP
(Data Access Protocol) file transfer mode. In this mode of operation, data
records are blocked together for transmission over the network to increase
data throughput and reduce CPU overhead. Selection of DAP file transfer
mode limits data transfers to one direction (either transmit using $PUT
/$WRITE or receive using $GET/$READ). Other VMS RMS services are
disallowed except for $DISCONNECT and $CLOSE, which terminate file
transfer mode.
User Action: Verify that the call to the VMS RMS service is coded correctly.
Modify the source program to either not request the prohibited services or not
specify the SQO FOP option in the FAB.

FUL,

device full (insufficient space for allocation)
Facility: RMS, VMS Record Management Services
Explanation: A $CREATE, $EXTEND, or $PUT operation for a file failed
because there is not enough space on the volume.
User Action: Delete or purge as many files as possible to provide usable
space on the volume, or request the system operator to do so. If the volume
is private and files cannot be deleted, obtain a new volume.

2-215

Messages

FUNNOTSUP,

function not supported

Facility: PSM, Print Symbiont
Explanation: This status is returned indicating the current function is not
supported by the user service. For future compatibility, user services should
return this status for any unrecognized function code.
User Action: None.
FUTBAKDAT,

file ('file-id') 'filename' backup date is in the future

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the date of the last backup
recorded for the file is later than the current date. The utility sets the backup
date to the current date.
User Action: None.
FUTCREDAT,

file ('file-id') 'filename' creation date is in the future

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the creation date recorded for
the file is later than the current date. The utility sets the creation date to the
current date.
User Action: None.
FUTREVDAT,

file ('file-id') 'filename' revision date is in the future

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the date of the last modification
recorded for the file is later than the current date. The utility sets the revision
date to the current date.
User Action: None.
FWF,

footnotes won't fit on page
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: There are too many footnotes in the input file, or there are too
many lines in a footnote.
User Action: Reduce the number or size of the footnotes.

GBC,

invalid global buffer count
Facility: RMS, VMS Record Management Services
Explanation: An incorrect global buffer count value is specified. The global
buffer count value must be in the range of 0 to 32,767.
User Action: Verify that the call to the VMS RMS service is coded correctly.

2-216

Messages

GBLNDF,

cannot define symbol-global symbol scoping is enabled

Facility: CU, Command Language Interpreter (DCL)
Explanation: You are trying to define a global symbol after using the SET
SYMBOL /SCOPE=NOGLOBAL command. Global symbols cannot be
accessed or defined while symbol scoping is set to be NOGLOBAL. This can
be reset with the SET SYMBOL /SCOPE=GLOBAL command.
User Action: Check your command procedure. Either change the symbol
scoping to GLOBAL, or use local symbols.

GBLNOTCRE,

global section not created

Facility: SMG, Screen Management Facility
Explanation: The system program that maps TERMTABLE.EXE as a global
section is unsuccessful.
User Action: This message should be handled only by system managers. If
there is already an existing global section for Termtable, the system must be
rebooted in order to create a new global section.

GBLONLY,

cannot obtain global copy of image section 'image-section

Facility: PATCH, Patch Utility
Explanation: The image being patched references a global copy of an image
section. There is no local copy of this section within the image file.
User Action: To patch such a section, you must patch the shareable image
file in which it is contained.

GBLPAGSZRO,

Global page share count is zero

GBLSECMAP, system terminal table used
Facility: SMG, Screen Management Facility
Explanation: The requested terminal definition is found in the system
Termtable. The requested terminal definition did not exist in the caller's
private Termtable.
User Action: None.

2-217

Messages

GBLWARN,

patching local copy of global image section 'image-section'

Facility: PATCH, Patch Utility
Explanation: The image being patched: (1) references a global image section,
(2) contained a local copy of the global image section (only the local copy is
being patched), (3) is no longer allowed to use the shared global section.
User Action: Patch the shareable image instead of the executable image,
if you want to continue sharing the global section. You must reinstall the
shareable image after it is patched.
GBLWSLXERR,

Global working set list entry not found

generated ERROR: 'xxxxx' message

Facility: MACRO, VAX MACRO Assembler
Explanation: A .ERROR directive is assembled; 'xxxxx' is the value of the
expression specified in the directive; and message is the text specified in the
directive.
User Action: Follow the instructions in the message.
GEN _MAX,

generic queue limit reached

Facility: JBC, Job Controller
Explanation: A maximum of eight generic queues can feed a specific
execution queue. This message indicates that you attempted to make an
execution queue the target of too many generic queues.
User Action: None. This is a restriction.
GENMINUSl,

shadow set virtual unit generation number invalid on 'device'

Facility: BACKUP, Backup Utility
Explanation: An attempt has been made to use BACKUP on a member of a
shadow set which has not yet been fully formed.
User Action: Wait for the shadow set to be fully formed and retry the
BACKUP operation.

2-218

Messages

GENWRN,

generated WARNING: 'xxxxx' message

Facility: MACRO, VAX MACRO Assembler
Explanation: A .WARN directive is assembled; 'xxxxx' is the value of the
expression specified in the directive; and message is the text specified in the
directive.
User Action: Follow the instructions in the message.
GETCHN, error getting device characteristics
Facility: DUMP, File Dump Utility
Explanation: The File Dump Utility encountered an error during an attempt
to obtain the device characteristics of the input device. The accompanying
message provides additional information.
User Action: Correct the condition that caused the error and reenter the
command.
GETCHN,

error getting device characteristics for 'device-name'

Facility: BACKUP, Backup Utility
Explanation: The Backup Utility encountered an error during an attempt
to obtain the device characteristics of the input device. The accompanying
message provides additional information.
User Action: Correct the condition that caused the error and reenter the
command.
GETDVI,

error getting device characteristics, RVN 'n'

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility encountered an error in an attempt to get
the device characteristics of the specified relative volume. The accompanying
message provides additional information.
User Action: Correct the condition that caused the error and reenter the
Verify Utility command line.
GETDVI,

error obtaining device information for 'device-name'

Facility: BAD, Bad Block Locator Utility
Explanation: An error is encountered while attempting to obtain information
regarding the device.
User Action: Examine the associated diagnostic messages, making corrections
where appropriate.
GETERR,

get error

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

2-219

Messages

GETERR,

read error code of 'xx' on file 'filespec

Facility: PATCH, Patch Utility
Explanation: A VMS RMS $GET read request failed due to the error
represented as 'xx
1

•

User Action: Correct the error (represented as 'xx') and retry.
GETJPI,

failed to obtain default job and process information

Facility: RUN, Run Detached Utility
Explanation: The system service $GETJPI failed to get process and job
information used to create new subprocess or detached process.
User Action: See error codes returned by the $GETJPI system service to
determine action.
GETJPIERR,

error from SYS$GETJPI

Facility: ERF, Error Log Utility
Explanation: This message indicates an internal consistency error.
User Action: Submit a Software Performance Report.
GETMEM,

Memory allocation failure

Facility: VAXTPU, VAX Text Processing Utility
Explanation: VAXTPU is attempting to allocate memory for its data
structures, but there is not sufficient free memory for it to do so. This error
may occur if you are using an extremely complex editing environment.
User Action: First, delete unneeded strings, ranges, markers, windows, and
buffers, then reenter your command. If the error reoccurs, increase the value
of the SYSGEN parameter VIRTUALP AGECNT. If the available memory is
still insufficient for your editing environment, try to increase your account's
page file quota. Finally, if the error persists, ask your system manager to
increase available memory.
GETMSG,

error obtaining message text

Facility: BAD, Bad Block Locator Utility
Explanation: An error is encountered while attempting to obtain message
text.
User Action: Copy all pertinent diagnostic message information and submit
an SPR to DIGITAL.
GETPTIERR,

error from $GETPTI, buffer 'number', image VPN 'decimal-number'
for 'decimal-number' pages

Facility: LINK, Linker Utility
Explanation: An error is returned from the $GETPTI system service.
User Action: Submit a Software Performance Report with all relevant
programs, listings, object files, and library files.

2-220

Messages

GETTIM,

error code of 'xx' on $GETTIM

Facility: PATCH, Patch Utility
Explanation: The $GETTIM system service request failed due to the error
represented as 'xx'.
User Action: Correct the error and retry.
GETVM, allocated 'number' bytes of virtual memory, total of 'number'
Facility: CNF, NI Configurator
Explanation: The VM bit is set in NICONFIG$LOG. Virtual memory has
been allocated and the amount is tallied.
User Action: None.
GFC,

given footnote count incorrect, correct value is n
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: The actual number of lines generated for the footnote is greater
or less than the count specified with the .FOOTNOTE n command.
User Action: None. This is an informational message. If you do not want
the message to appear, remove the number from the .FOOTNOTE command.

GOSUBMAX,

GOSUB procedures too deeply nested-limit to 16 levels

Facility: CLI, Command Language Interpreter (DCL)
Explanation: You are nested at the maximum level of subroutines and tried
to transfer control to another lower level.
User Action: Modify your command procedure so that it does not nest so
deeply. Also ensure that you have a RETURN statement at the end of each
subroutine.
GPGNULPGFL,

global page has null page file address

global page table is full

Facility: SYSTEM, VMS System Services
Explanation: Not enough space is available in system memory to maintain
information about global sections. This message indicates a system error
resulting from insufficient allocated space in the global page table.
User Action: Notify your system operator or system manager to increase the
SYSGEN parameter GBLP AGES.

2-221

Messages

GRANTERR,

unable to grant identifier 'id-name' to 'user-id'

Facility: AUTHORIZE, Authorize Utility
Explanation: The specified resource identifier cannot be granted to the
specified user ID. This message should be accompanied by a second message
showing the specific reason why the identifier could not be granted.

Resource identifiers are granted to VIC-format identifiers. Typically, this
error occurs either because the specified resource identifier does not exist or
because the target user ID is not a VIC-format identifier. The latter can occur
when multiple accounts have the same UIC.
User Action: Correct the condition identified by the second message and
reenter your command.

GRANTMSG,

identifier 'id-name'.granted to 'user-id'

Facility: AUTHORIZE, Authorize Utility
Explanation: The specified general identifier has been granted to the specified
us-er. The user has access to all of the rights associated with the identifier.
User Action: None.

GSDFULL,

global section descriptor table is full

Facility: SYSTEM, VMS System Services
Explanation: The system cannot create or map a global section because the
system space allocated for global section data is full. This message usually
indicates that the system is not generated with sufficient space for global
section descriptors.
User Action: Wait and retry the request. If the failure persists, notify the
system manager.

GSDTYP,

illegal GSD record type ('number') in module 'module-name' file
'filename'

Facility: LINK, Linker Utility
Explanation: An illegal GSD Record type is found in the specified object
module.
User Action: Submit a Software Performance Report on the appropriate
language compiler.

GSDTYP, illegal GSD record type 'record-type' in module 'module-name'
Facility: LIB, Library Facility
Explanation: The Run-Time Library encountered severe format errors in the
shareable image you are trying to call.
User Action: Enter the ANALYZE/IMAGE command specifying the image in
question. If the errors indicate an operating system internal error, submit a
Software Performance Report.

2-222

Messages

GSDTYP,

module 'module-name' file 'library-filespec' has an illegal GSD record
'record-type'

Facility: LIBRAR, LIBRARY Command
Explanation: This error message is generated by the DCL command
LIBRARY. The specified object module is illegally formatted.
User Action: Recompile the object module before inserting it into the library.
HALT,

halt instruction restart

transfer has been halted

Facility: Shared by several facilities
Explanation: If this message is returned from a DR32 support routine call,
the DR32 transfer is complete.
User Action: If the DR32 transfer halted unexpectedly, determine the cause
of the error.
HANGUP,

data set hang-up

Facility: SYSTEM, VMS System Services
Explanation: The associated terminal data set has been hung up. A CTRL/Y
or unsolicited data AST is delivered.
User Action: None.
HBREAD,

error reading home block of 'volume-name'

Facility: SET, SET Facility
Explanation: An error occurred while trying to read the home block of a
volume. This message is issued with an accompanying message.
User Action: Take corrective action based on the accompanying message.
HBWRITE,

error writing home block of 'volume-name'

Facility: SET, SET Facility
Explanation: An error occurred while trying to write to the home block of a
volume. This message is issued with an accompanying message.
User Action: Take corrective action based on the accompanying message.

2-223

Messages

HDRBLK,

too many ISDs for image header blocks

Facility: PATCH, Patch Utility
Explanation: You requested too many image section descriptors; PATCH is
unable to create this patch area.
User Action: Relink your image file.
HDRCRC,

software header CRC error

Facility: BACKUP, Backup Utility
Explanation: An incorrect value occurred in the header CRC field
(BBH$W_CHECKSUM) of a save set block. Data in the save set is corrupted.
User Action: None. The save set data is lost.
HDRERRS,

errors occurred writing the dump file header blocks

Facility: SDA, System Dump Analyzer
Explanation: The first block of the dump file contains information indicating
that there were errors while writing out the dump header.
User Action: None. The dump file might not be useful for analysis.
HDRNOTMAP,

allocated file header not mapped

unable to make image header resident

Facility: INSTALL, Install Utility
Explanation: Insufficient pool is available to make the header resident, or the
file has an image header larger than one block.
User Action: Use the SYSGEN parameter PAGEDYN to increase the pool.
Only files with one block image headers may be made resident.
HDRTRUNC,

header truncated

Facility: LBR, Librarian Subroutine Package
Explanation: This warning message is generated by the Librarian routines.
The buffer supplied to LBR$SET_MODULE is smaller than the header.
User Action: Supply a larger buffer to LBR$SET_MODULE.

2-224

Messages

HEADCOPIED,

copied 'file-header' header

Facility: BACKUP, Backup Utility
Explanation: The /LOG message indicating that a file header only is copied.
The file is marked NOBACKUP; therefore, no data is saved.
User Action: None.

HEADERFULL,

file header is full

Facility: SYSTEM, VMS System Services
Explanation: The file header map area on the volume is full and cannot be
extended. This error occurs only when the file header extension is inhibited,
for example, when the index file is being extended.
User Action: Compress the volume by copying it with BACKUP.

HELP,

enter HELP for INSTALL help

Facility: INSTALL, Install Utility
Explanation: This is an informational message.
User Action: Enter HELP for INSTALL help.

Help file could not be closed
Facility: EDT, EDT Editor
Explanation: You specified the name of a HELP file that EDT is unable
to close. Some problem exists at the system level that prevents EDT from
closing the file.
User Action: After determining the cause of the system problem, correct it.

Help file could not be opened
Facility: EDT, EDT Editor
Explanation: The requested EDT HELP file cannot be accessed. An error
in system storage has occurred (for example, improper installation of the
operating system).
User Action: Verify that the logical name EDTHELP (with a default of
SYS$HELP:.HLB) designates the EDT HELP file, and that the file has not
been damaged.

Help File Index could not be initialized
Facility: EDT, EDT Editor
Explanation: You created a new EDT HELP file or modified an existing EDT
HELP file, but either you neglected to include an index number or you placed
an indexed entry out of the proper nested order.
User Action: Include the omitted index number or place the indexed entry in
the proper nested order.

2-225

Messages

HELPERR,

error finding or outputting HELP information

Facility: AUTHORIZE, Authorize Utility
Explanation: An error occurred trying to access the AUTHORIZE HELP file.
User Action: Check that the AUTHORIZE HELP file, by default named
UAFHLP.HLB, is located in the proper directory and is not protected against
read access.

HELPERR,

HELP command error

Facility: MONITOR, Monitor Utility
Explanation: An error occurred during execution of the HELP command of
the Monitor Utility. More information may be obtained by examining the
accompanying message.
User Action: Correct the error indicated by the accompanying message and
rerun the HELP command. This error can occur when the MONITOR help
library (SYS$HELP:MNRHELP .HLB) cannot be located or accessed.

HIB,

hibernating until requested beginning time ...
Facility: MONITOR, Monitor Utility
Explanation: Monitoring of the running system is requested, beginning at a
future time. The process that issued the MONITOR request is placed in the
hibernate state until the requested beginning time, at which time monitoring
will begin. This is an informational message.
User Action: If monitoring at a future time is desired, no user action is
required. If, however, the /BEGINNING qualifier is incorrectly specified and
if future monitoring is not desired, cancel the MONITOR request and reenter
it.

HIBER,

hibernating until 'time'

Facility: SHOW CLUSTER, Show Cluster Utility
Explanation: This is an informational message that is returned when the
SHOW CLUSTER command is invoked with the /BEGINNING=beginningtime qualifier. The message indicates that the current process will be
suspended until the time indicated.
User Action: None.

HIDDEN,

global variable 'name' by declaration

Facility: VAXTPU, VAX Text Processing Utility
Explanation: You have declared a parameter, local, or constant that has the
same name as a global variable. Your declarat.ion hides the global variable.
User Action: None.

2-226

Messages

High Priority Command Queue Insert Failure
Facility: VAXport, VAXport Driver
Explanation: The VAXport driver attempts to reinitialize the port; after 50
failed attempts it marks the device off line.
User Action: Call DIGITAL Field Service. This error is caused by a failure to
obtain access to an interlocked queue. Possible sources of the problem are CI
hardware failures or memory, SBI (11/780), CMI (11/750), or BI (8200, 8300,
and 8800) contention.

HIGHVER,

higher version of 'output-filespec' already exists

Facility: Shared by several facilities
Explanation: An explicit version number is requested for an output file; the
directory already contains an entry for the same file name and file type with
a higher version number.
User Action: None. The message is informational. Note that if the file is
subsequently specified in a command, the system will locate the previously
existing version if no version number is specified. The newly created output
file will not be used.

HISTERR,

error accessing library update history in 'library-name'

Facility: LIBRAR, LIBRARY Command
Explanation: An error occurred while accessing the library update history
records. This message is issued with an accompanying message.
User Action: Take corrective action based on the accompanying message.

HOMBLKBAD,

primary home block is bad; backup used

Facility: MOUNT, Mount Utility
Explanation: The primary home block of a disk is corrupted or unreadable;
the backup volume is used to mount the volume.
User Action: Repair the disk with the Verify Utility.

HOMBLKCHK,

home block software consistency check

Facility: MOUNT, Mount Utility
Explanation: The home block in the volume has failed the software
consistency check during /BIND processing. The first occurrence of this
message is a warning; the second is fatal.
User Action: Repair or reinitialize the volume and retry the operation.

HRDFAI,

hardware failure

Facility: NCP, Network Control Program
Explanation: The hardware associated with the request could not perform
the function required.
User Action: Contact your system manager or a DIGITAL field service
representative.

2-227

Messages

HSC Error Logging Datagram Received
Facility: VAXport, VAXport Driver
Explanation: Upon receiving an error message from the HSC, the CI port
driver logs the error and takes no other action. Since HSC informational error
log datagrams are also recorded on the HSC console, it is useful to read them
only if the HSC console does not record them for some reason (if it runs out
of paper, for example).
User Action: You should disable the sending of HSC informational error
log datagrams with the appropriate HSC console command, since HSC
informational error log datagrams take up considerable space in the error log
data file.
1/0 error on work file
Facility: EDT, EDT Editor
Explanation: EDT is unable to access its text storage area for the file. An
additional message will explain the error further, such as "Device full" or
"Device write locked".
User Action: Correct the problem described in the file system message.
JAL,

invalid argument list
Facility: RMS, VMS Record Management Services
Explanation: The argument list in a call to SYS$RMSRUNDWN,
SYS$SETDDIR, or SYS$SETDFPROT control routines either cannot be
accessed or contains invalid data.
User Action: Verify that the call to the VMS RMS service is coded correctly.

IAN, invalid index area number for key= 'nnn'
Facility: RMS, VMS Record Management Services
Explanation: The index area number specified in a key definition XAB is not
a defined area for the file.
User Action: The status value (STV) field of the FAB provides the key of
reference of the XAB in error. Verify that the call to the VMS RMS service is
coded correctly.
IBF,

illegal bucket format in VBN = 'nnn'
Facility: RMS, VMS Record Management Services
Explanation: VMS RMS detected a corrupted bucket in an indexed file.
Incorrect bucket control flags or an incorrect bucket freespace value is
detected.
User Action: Reorganize the file with the CONVERT command, or re-create
the file. The status value (STV) field of the FAB or RAB contains the starting
virtual block number of the bucket in error.
This error is caused by hardware errors, VMS RMS or system software errors,
or inadvertent modifications of files by non-RMS programs.

2-228

Messages

IBK,

LAN bucket size not equal IAN bucket size for key = 'nnn'
Facility: RMS, VMS Record Management Services
Explanation: The bucket size for the index area specified by IAN must be the
same as the bucket size of the lowest-level index area specified by LAN.
User Action: The status value (STV) field of the FAB provides the key of
reference of the XAB in error. Verify that the call to the VMS RMS service is
coded correctly. In particular, determine that the correct area numbers and
sizes were specified for the index and lowest-level index areas.

IBO,

input buffer overflow: 'string'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: A character string that is too long was entered in an internal
line buffer. This is a DSR internal error message.
User Action: Submit a Software Performance Report.

ICONCLUDAT,

inconsistent cluster database

Facility: BUGCHECK, System Bugcheck
Explanation: The VMS software detected an irrecoverable, inconsistent
condition. After all of physical memory is written to a system dump file, the
system will automatically reboot if the BUGREBOOT system parameter is set
to 1.
User Action: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error, and that includes a BACKUP save set
containing the system dump file and the error log file active at the time of the
error. (Use the /IGNORE=NOBACKUP qualifier on the BACKUP command
that produces the save set included with the SPR.)
ICONPFNDAT, inconsistent PFN database
Facility: BUGCHECK, System Bugcheck
Explanation: The VMS software detected an irrecoverable, inconsistent
condition. After all of physical memory is written to a system dump file, the
system will automatically reboot if the BUGREBOOT system parameter is set
to 1.
User Action: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error, and that includes a BACKUP save set
containing the system dump file and the error log file active at the time of the
error. (Use the /IGNORE=NOBACKUP qualifier on the BACKUP command
that produces the save set included with the SPR.)

2-229

Messages

ICP AGELOC,

inconsistent page location

invalid display descriptor: "text in error"

Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: You specified an incorrect descriptor in a .DISPLAY directive.
User Action: Correct the specified descriptor.
IDENT,

DSRTOC version 'version-number'

Facility: DSR, DIGITAL Standard Runoff
Explanation: This message is displayed when the /IDENTIFICATION
qualifier is specified. It shows the version number of the DSR Table of
Contents Utility. This message is informational.
User Action: None.
IDENT,

standalone BACKUP 'string'; the date is 'date and time'

Facility: BACKUP, Backup Utility
Explanation: This is a standalone BACKUP identification message.
User Action: Make sure that the displayed data is correct.
IDMISMATCH,

ident mismatch with global section or shareable image

Facility: SYSTEM, VMS System Services
Explanation: The ident is part of the global section name. An attempt is
made to create a shared memory global section using a different ident with a
name that is the same as that of an existing shared memory section.
This error occurs when an attempt is made to install an image in shared
memory (MA780) from two processors that do not have identical image files.

User Action: Copy the file from one processor to the other and retry the
operation.
IDMISMATCH,

section NOT restored, section file must be rebuilt

Facility: VAXTPU, VAX Text Processing Utility
Explanation: This version of VAXTPU is not compatible with the section file
that you are trying to access.
User Action: Save the section file again by running the source file through
the version of VAXTPU you are trying to use.

2-230

Messages

IDMISMCH,

GSMATCH of number,number in shareable image image-name
differs from GSMATCH of number,number in shareable image
library library-name'
1

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

IDOUTRNG,

identifier value is not within legal range

Facility: AUTHORIZE, Authorize Utility
Explanation: The value you specified for an identifier is not within the
permissible range. A general identifier may have an integer value between
32,768 and 268,435,455. A UIC identifier takes a value in standard UIC
format.
User Action: Reenter your command with an identifier value that is within
the permissible range.

IDR,

invalid directory rename operation
Facility:- RMS, VMS Record Management Services
Explanation: A VMS RMS $RENAME service is requested that would rename
a directory file into a directory tree that contained the directory file. The
directory would then be inaccessible. An example of incorrect usage is:
$RENAME [A]B.DIR [A.B]

User Action: Modify the program or reenter the command specifying the
correct old and new file specifications for the $RENAME service.

IDX,

index not initialized
Facility: RMS, VMS Record Management Services
Explanation: The index of an indexed file could not be properly initialized
when inserting the first record.
User Action: Re-create the file. Collect as much information as possible and
submit a Software Performance Report.

IDXCONCAT, index file cannot be concatenated
Facility: Shared by several facilities
Explanation: An index file may not be concatenated with another file.
User Action: Use an indexed file load program to load the indexed file.

2-231

Messages

IDXFILEFULL,

index file is full

Facility: SYSTEM, VMS System Services
Explanation: No more files can be written on the volume, because the
maximum size of the index file specified is reached when the volume is
initialized.
User Action: If the volume is a private volume, delete the unwanted files on
the volume. If the volume is a system volume, notify the system operator or
system manager.
IDXHDRBAD,

index file header is bad; backup used

Facility: MOUNT, Mount Utility
Explanation: This message is generated by the DCL command MOUNT. The
primary index file header is corrupted or unreadable; the backup volume is
used to mount the volume.
User Action: Repair the volume with the Verify Utility.
IDX_LIM,

exceeded maximum index level

Facility: CONVERT, Convert Utility
Explanation: The index tree depth exceeded 32 levels.
User Action: Redesign the file to make it more shallow.
IDXMAPERR,

I/O error on index file bitmap; volume locked

Facility: MOUNT, Mount Utility
Explanation: I/O error encountered during a mount operation. Existing files
in the volume can be accessed but other operations, for example, create and
delete, are not possible.
User Action: Repair the volume with the Verify Utility.
IFA,

illegal file attributes detected (file header corrupted)
Facility: RMS, VMS Record Management Services
Explanation: The content of the file header was corrupted; the data is
inconsistent and cannot be read.
User Action: Depending on the operation, the status value (STV) field in
the FAB or RAB contains a system status code that provides additional
information about the condition. Take corrective action based on this status
code. If the error persists, collect as much information as possible and submit
a Software Performance Report.

IFDIRSYNX,

IF directive syntax error

Facility: MACRO, VAX MACRO Assembler
Explanation: A conditional assembly directive contained a syntax error.
User Action: Correct the syntax of the directive.

2-232

Messages

IFEXPRNABS,

IF expression not absolute

Facility: MACRO, VAX MACRO Assembler
Explanation: The expression in an .IF directive is not an absolute expression
or contained undefined symbols.
User Action: Change the values in the expression.
IFF,

invalid file attributes for requested file access
Facility: RMS, VMS Record Management Services
Explanation: The attributes of the file do not permit the type of file access
requested. For example, usually this means that the user attempted to open
an ANSI magnetic tape file for write access, and the file has a nonzero value
for buffer offset. VMS RMS will not allow you to create a magnetic tape file
with nonzero buffer offset. However, you may access the file for input and
output if you specify block I/O.
User Action: Correct the type of access requested or change the attributes of
the file.

IFI,

invalid internal file identifier (IFI) value
Facility: RMS, VMS Record Management Services
Explanation: The internal file identifier field of the FAB is invalid. This
error usually indicates that the file has not been opened for an operation
that requires the file to be opened, or that the file is already opened for an
operation that requires the file not to be opened.
User Action: Check for a programming error. Verify the logic of the program
to see that the file is opened or closed as required for the attempted operation.

IFL,

index bucket fill size larger than bucket size for key= 'nnn'
Facility: RMS, VMS Record Management Services
Explanation: The index bucket fill specified in a key definition XAB exceeds
the bucket size for the data area.
User Action: The status value (STV) field of the FAB provides the key of
reference of the XAB in error. Verify that the call to the VMS RMS service is
coded correctly.

IFLEVLXCED,

IF nesting level exceeded

Facility: MACRO, VAX MACRO Assembler
Explanation: The assembler encountered more than 31 levels of nested
conditional assembly blocks.
User Action: Restructure the program to decrease nesting of conditional
assembly blocks.

2-233

Messages

IFREPAGCNT,

inconsistent free page count

IFT,

illegal in footnote: 'string'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: You attempted to use an illegal command between the DSR
commands .FOOTNOTE and .ENDFOOTNOTE.
User Action: Remove the command.

IGNCLIFLAG, line 'line-number': CLI flag ignored in this context
Facility: CDU, Command Definition Utility
Explanation: CDU encountered an illegal argument for CLI flags for the
current context.
User Action: Edit the .CLI file so that all CLI flags are valid in the context
in which they are used. Refer to the VMS Command Definition Utility Manual
for more information on the use of control flags in the Command Definition
Utility.

IGNFIL,

ignoring input file: 'filespec'

Facility: MONITOR, Monitor Utility
Explanation: An input file specified in an /INPUT list was excluded from
inclusion in a multi-file summary. The linked error message accompanying
this message provides an explanation for the exclusion.
User Action: If the ignored file is one which should be included in the multifile summary, then examine the linked error message, correct the situation
described therein, and reenter the MONITOR request.

IGNORED,

'string' ignored

Facility: DSR, DIGITAL Standard Runoff
Explanation: DSR ignored a character string during processing.
User Action: None.

IGNORE_DIRE,

directory name ignored, not used for this volume type

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility ignored the directory name field of a
filename.
User Action: Do not enter the directory name; it is not needed.

2-234

Messages

IGNORE_VERS,

file version ignored, not used for this volume type

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility ignored the version number field of a
filename.
User Action: Leave the version number off; it is not needed.
IGNQUAL,

qualifiers apppearing before this item were ignored

Facility: CLI, Command Language Interpreter (DCL)
Explanation: This informational message signifies that the qualifiers
appearing before the displayed item were ignored.
User Action: None.
IIF,

AX ignored
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: A control character code CX) was illegally entered in the input
file and has not been accepted.
User Action: In order to legalize the entry of such codes, you must enter the
.CONTROL CHARACTERS command.

ILC, illegal command: 'string'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: This command is illegal. Command or values you specify for it
are unrecognizable.
User Action: Check for spelling errors in the command keywords.
ILE,

internal logic error 'string'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: DSR has detected an internal failure at the location specified by
the indicated string. This is a DSR internal error.
User Action: Submit a Software Performance Report.

ILLANSIBS,

ANS magnetic tape block size must be at least 18 characters

Facility: MOUNT, Mount Utility
Explanation: The label specified for a magnetic tape contains less than 18
characters.
User Action: Reenter the command; specify a minimum value of 18 for the
block size.
ILL_ARG,

wrong number of arguments

Facility: FDL, Create/FOL Utility
Explanation: You specified too many files in the FDL$CREATE call.
User Action: Specify the correct number of files.

2-235

Messages

ILLARGDESC,

illegal operand argument descriptor

Facility: MACRO, VAX MACRO Assembler
Explanation: The operand descriptor in an .OPDEF directive is invalid.
User Action: Use one of the valid operand descriptors.
ILLASCARG,

illegal ASCII argument

Facility: MACRO, VAX MACRO Assembler
Explanation: Either the argument to a .ASCix directive did not have
enclosing delimiters or an expression is not enclosed in angle brackets.
User Action: Correct the syntax of the argument.
ILLBATFNC,

operation not permitted while display is batched

Facility: SMG, Screen Management Facility
Explanation: An attempt is made to perform an operation that is not
permitted while a virtual display is being batched-for example, when
performing input or moving the virtual display.
User Action: Terminate batching first by calling SMG$END_DISPLAY_
UPDATE.
ILLBLKNUM,

illegal logical block number

Facility: SYSTEM, VMS System Services
Explanation: The logical block number specified does not exist on the disk. If
this error results from a Files-11 1/0 operation, the file structure is damaged.
User Action: Check for a programming error. If this error results from a
Files-11 ljO operation, repair the volume with the Verify Utility.
ILLBRDEST,

illegal branch destination

Facility: MACRO, VAX MACRO Assembler
Explanation: The destination of a branch instruction is not an address, for
example, BRB 10(R9).
User Action: Change the destination of the branch instruction or use a jump
(JMP) instruction.
ILLCDTST, illegal connection descriptor table state
Facility: SYSTEM, VMS System Services
Explanation: A system facility attempted an operation on a connection that
is illegal for the current state of that connection.
User Action: Submit a Software Performance Report.
ILLCHR, illegal character
Facility: MACRO, VAX MACRO Assembler
Explanation: The source line contained a character that is illegal in its
context.
User Action: Delete the illegal character.

2-236

Messages

ILLCNTRFUNC,

illegal ACP control function

Facility: SYSTEM, VMS System Services
Explanation: The control function specified in an 10$--ACPCONTROL QIO
request is not a valid function.
User Action: Check for a programming error. Consult the documentation for
the correct function codes and coding specifications.
ILLCOMPONENT,

illegal initialization component

Facility: LIB, Library Facility
Explanation: An illegal component value is passed to LIB$INIT_DATE_
TIME_CONTEXT.
User Action: Examine the component value and correct it, if necessary.
ILLCREOPT,

illegal create options

Facility: LBR, Librarian Subroutine Package
Explanation: This error message is generated by the Librarian routines.
Either the create options you specified for LBR$0PEN are illegal or no
options were specified.
User Action: Correct the create options before calling the routine.
ILLCTL,

illegal control index

Facility: LBR, Librarian Subroutine Package
Explanation: This error message is generated by the Librarian routines.
Either the library is not open or you have specified an illegal library index.
User Action: Determine that the library is open and that the library index is
correct.
ILLDESQUE,

illegal destination queue name

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

illegal argument for .DEFAULT directive

Facility: MACRO, VAX MACRO Assembler
Explanation: A .DEFAULT directive did not specify DISPLACEMENT or the
displacement specified is not one of the three keywords - BYTE, WORD, or
LONGWORD.
User Action: Correct the .DEFAULT directive.

2-237

Messages

ILLEFC,

illegal event flag cluster

Facility: SYSTEM, VMS System Services
Explanation: An event flag number specified in a system service call is
greater than 127.
User Action: Correct the source program. Verify that the event flag number
is correctly coded, and that it is not modified during the execution of the
image.
ILLEGALTYPE,

illegal data type

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The expression or operator contains an invalid data type.
User Action: Check the data type being used and make sure that the
expression or operator supports this data type.
ILLEVTNUM,

illegal event number

illegal expression

Facility: MACRO, VAX MACRO Assembler
Explanation: A radix unary operator is not followed by a number, or left and
right angle brackets did not match in an expression.
User Action: Correct the syntax of the expression.
ILLFMLCN,

minimum argument count ('decimal-number') exceeds maximum
('decimal-number') in formal specification of symbol 'symbol-name'
in module 'module-name' file 'filename'

Facility: LINK, Linker Utility
Explanation: A procedure definition subrecord has an illegal format.
User Action: Submit a Software Performance Report on the appropriate
language compiler.

2-238

Messages

ILLFMLCNT, minimum argument count exceeds maximum for procedure
'procedure' in module 'module-name'

Facility: LBR, Librarian Subroutine Package
Explanation: This error message is generated by the Librarian routines. The
file you specified calling LBR$0PEN is not a library.
User Action: Specify the correct library.
ILLFORMAT,

illegal format, too many or not enough fields

Facility: LIB, Library Facility
Explanation: You entered an invalid format string.
User Action: Examine the date/time string and correct it.
ILLFUNC, illegal library function

Facility: LBR, Librarian Subroutine Package
Explanation: This error message is generated by the Librarian routines. The
library function you specified in LBR$0PEN is illegal.
User Action: Correct the library function before calling the routine.
ILLIDXNUM, illegal index number

Facility: LBR, Librarian Subroutine Package
Explanation: This error message is generated by the Librarian routines. The
index number you specified is illegal.
User Action: Correct the index number before calling the routine.
ILLIFCOND, illegal IF condition

Facility: MACRO, VAX MACRO Assembler
Explanation: The condition specified in a conditional assembly is not a valid
condition, or there were no symbols after a DIFFERENT or IDENTICAL
condition.
User Action: Correct the syntax of the conditional assembly directive.

2-239

Messages

ILLINDXREG,

invalid index register

Facility: MACRO, VAX MACRO Assembler
Explanation: The base mode changed the value of the register, and the index
register is the same as the register in the base mode; the base mode is literal
or immediate mode; or PC is used as the index register.
User Action: Correct the addressing mode.
ILLINISTR,

illegal initialization string

Facility: LIB, Library Facility
Explanation: An incorrect initialization string is passed to LIB$INIT_DATE_
TIME_CONTEXT.
User Action: Verify that the initialization string begins and ends with the
same delimiter character.
ILLINROU,

input routine improperly specified or missing

Facility: LBR, Librarian Subroutine Package
Explanation: A librarian function is called with a missing or invalid input
routine parameter.
User Action: If no input routine is passed to the librarian function, then
supply one; or check the values of the other arguments that were passed to
ensure that none of the arguments specify that the input routine parameter is
required. If a routine value is supplied, then check that it is a valid address
(for example, nonzero).
ILLIOFUNC, illegal 1/0 function code
Facility: SYSTEM, VMS System Services
Explanation: A function code in an explicit input/ output request is invalid.
Or if the errors occurred during a DECnet-VAX operation, the user attempted
a synchronous disconnect with outstanding transmits.
User Action: Check for a programming error. Locate the invalid function
code and correct it.
ILL__KEY,

illegal key or value out of range

Facility: CONVERT, Convert Utility
Explanation: You have specified /KEY with a nonnumeric value, or with a
numeric value that is outside the range of 0 to 254.
User Action: Specify a legal value with /KEY.
ILLKEYLVL, illegal key level 'number' key 'keyname' in 'library-name' expected
'key number'
Facility: LIBRAR, LIBRARY Command
Explanation: This error message is generated by the DCL command
LIBRARY. The help module you want to insert into the library is formatted
incorrectly.
User Action: Reformat the module before inserting it into the library.

2-240

Messages

ILLMACARGN,

illegal MACRO argument name

Facility: MACRO, VAX MACRO Assembler
Explanation: The name in the .MACRO directive contained an illegal
character.
User Action: Delete the illegal character.
ILLMACNAM,

illegal MACRO name

Facility: MACRO, VAX MACRO Assembler
Explanation: No MACRO name is specified in the .MACRO directive.
User Action: Specify the MACRO name in the .MACRO directive.
ILLMASKBIT, reserved bits set in ENTRY mask
Facility: MACRO, VAX MACRO Assembler
Explanation: The register save mask in an .ENTRY or .MASK directive
specified RO, Rl, AP, or FP registers (corresponding to bits 0, 1, 12, and 13).
User Action: Remove these registers from the register save mask.
ILLMODE, illegal mode
Facility: MACRO, VAX MACRO Assembler
Explanation: An invalid addressing mode for the instruction is specified.
User Action: Specify a legal addressing mode.
ILLMODNAM, illegal module name length 'length' for module 'module-name'
Facility: LIB, Library Facility
Explanation: The Run-Time Library encountered severe format errors in the
shareable image you are trying to call.
User Action: Enter the ANALYZE/IMAGE command specifying the image in
question. If the errors indicate an operating system internal error, submit a
Software Performance Report.
ILLMTCOPY,

cannot specify same magtape for both input and output

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility detected an attempt to use a single
DOS-11 magtape for both input and output.
User Action: Specify different magtapes for input and output, or copy the file
onto disk before copying it back out to tape.
ILLNAMELEN,

'name' 'name' name length ('decimal-number') is illegal - not 1 to
'decimal-number' in module 'module-name' file 'filename'

Facility: LINK, Linker Utility
Explanation: The length of a psect, module, or symbol name is illegal.
User Action: Correct the length and relink.

2-241

Messages

ILLOP,

illegal operation for access requested

Facility: LBR, Librarian Subroutine Package
Explanation: This error message is generated by the Librarian routines. You
have attempted to modify a Version 1.0 library or a read-only library.
User Action: Compress the library into the current format or change the
access privileges to the library file.
ILLOPDEF,

illegal format for .OPDEF

Facility: MACRO, VAX MACRO Assembler
Explanation: The .OPDEF directive had incorrect syntax.
User Action: Correct the .OPDEF directive syntax.
ILLOPDEFVL, illegal value for opcode definition
Facility: MACRO, VAX MACRO Assembler
Explanation: The value specified in the .OPDEF directive does not fit in two
bytes.
User Action: Correct the value in the directive.
ILLOPT,

qualifiers not appropriate to this device

Facility: MOUNT, Mount Utility and INIT, INITIALIZE Command
Explanation: A DCL command MOUNT or INITIALIZE specified qualifiers
that apply only to disk devices for a tape device, or qualifiers that apply only
to tape devices for a disk device.
User Action: Use the DCL command HELP or refer to the VMS DCL
Dictionary for a list of qualifiers, and reenter the command with the
appropriate qualifiers.
ILLOUTROU,

output routine improperly specified or missing

Facility: LBR, Librarian Subroutine Package
Explanation: A librarian function is called with a missing or invalid output
routine parameter.
User Action: If no output routine is passed to the librarian function, either
supply one or check the values of the other arguments that were passed. This
ensures that none of the arguments specify that an output routine parameter
is required. If a routine value is supplied, check to see that it is a valid
address, for example, nonzero.
ILLP AGCNT,

illegal page count parameter

Facility: SYSTEM, VMS System Services
Explanation: The number of pages specified for an expand or contract region
request is less than one.
User Action: Check for a programming error; verify the number of pages
specified for the service call.

2-242

Messages

ILLPATAS,

pattern assignment target only valid in procedure 'name'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The target of a partial pattern assignment, the@ operator, was
defined in, and is only valid in, the named procedure.
User Action: Use a global variable for the partial pattern assignment or use
this pattern only from within the named procedure.
ILLPSCLEN,

psect 'psect-name' has illegal length 'length' for module 'modulename'

Facility: LIB, Library Facility
Explanation: The Run-Time Library encountered severe format errors in the
shareable image you are trying to call.
User Action: Enter the ANALYZE/IMAGE command specifying the image in
question. If the errors indicate an operating system internal error, submit a
Software Performance Report.
ILLQUAL, invalid qualifier
Facility: MOUNT, Mount Utility
Explanation: An invalid qualifier is given in the command.
User Action: Replace the qualifier and reenter the command.
ILLQUALVAL, illegal qualifier value
Facility: LINK, Linker Utility
Explanation: The command line contained an illegal value for a qualifier.
User Action: Reenter the command correctly.
ILLRECLEN,

illegal record length ('decimal-number') in module 'module-name'
file 'filename'

Facility: LINK, Linker Utility
Explanation: A module contains a record of illegal length.
User Action: Submit a Software Performance Report on the appropriate
language compiler.
ILLRECLEN,

illegal record length 'length' in module 'module-name'

Facility: LIB, Library Facility
Explanation: The Run-Time Library encountered severe format errors in the
shareable image you trying to call.
User Action: Enter the ANALYZE/IMAGE command specifying the image in
question. If the errors indicate an operating system internal error, submit a
Software Performance Report.

2-243

Messages

ILLRECLN2,

illegal record length 'length'

illegal record type 'record-type'

Facility: LIB, Library Facility
Explanation: The Run-Time Library encountered severe format errors in the
shareable image you are trying to call.
User Action: En~er the ANALYZE/IMAGE command specifying the image in
question. If the errors indicate an operating system internal error, submit a
Software Performance Report.
ILLRECTYP,

illegal record type ('decimal-number') in module 'module-name'
record 'record-name' file 'filename'

Facility: LINK, Linker Utility
Explanation: A module contains an illegal object record type.
User Action: Submit a Software Performance Report on the appropriate
language compiler.
ILLRECTYP,

illegal record type 'type' in module 'module-name'

this register may not be used here

Facility: MACRO, VAX MACRO Assembler
Explanation: The PC register cannot be used in the following addressing
modes: register, register deferred, autodecrement, autoincrement, and
autoincrement deferred.
User Action: Use another register.
ILLREGNUM,

illegal register number

Facility: MACRO, VAX MACRO Assembler
Explanation: A register name is not the AP, FP, SP, or PC register name. Or
it is not in the range RO through Rl2.
User Action: Correct the illegal register name.

2-244

Messages

ILLREQUEST, request 'name' is invalid
Facility: VAXTPU, VAX Text Processing Utility
Explanation: The specified request is not valid for this built-in.
User Action: Reenter the command with a valid request string.

ILLRQST, illegal operator request
Facility: OPCOM, Operator Communication
Explanation: A DCL command REPLY is entered with no qualifiers. Or, a
DCL command REQUEST specified an incorrect value.
User Action: Verify the command line and reenter the command.

ILLSAVESET, illegal save set name specified to RESTORE _SAVESET.
Facility: VMSINSTAL, Install Procedures
Explanation: The product installation procedure contains an incorrect call to
RESTORE_SAVESET.
User Action: Contact your DIGITAL field service representative.

ILLSELF,

illegal self reference

Facility: SYSTEM, VMS System Services
Explanation: You have unsuccessfully attempted to suspend all action on
your own job.
User Action: None. Your job is not suspended.

ILLSEQOP,

illegal sequential operation

Facility: SYSTEM, VMS System Services
Explanation: When a sequential access device is used, such as a magnetic
tape, certain operations can be performed only at the appropriate time. For
example, the control function NEXT VOLUME can be executed only when
the tape is positioned within the data section.
User Action: Examine the source program to determine the logic problem.

ILLSER,

illegal service call number

Facility: SYSTEM, VMS System Services
Explanation: An image specified an invalid change mode to executive or
kernel service number.
User Action: Check for a programming error. Locate the invalid call and
correct it.

ILLSEVERITY, illegal severity of 'value' specified, error severity used
Facility: VAXTPU, VAX Text Processing Utility
Explanation: Severities must be between 0 and 3, inclusive.
User Action: Specify a valid severity.

2-245

Messages

ILLSHROPR, illegal shareable image reference expression operator in module
'module-name' record 'record-name' file 'filename'
Facility: LINK, Linker Utility
Explanation: An attempt is made to perform an operation, other than
addition or subtraction, in an expression that contained a symbol from a
shareable image.
User Action: Correct the expression and relink.

ILLSHRXPR,

illegal shareable image reference expression in module 'modulename' record 'record-name' file 'filename'

Facility: LINK, Linker Utility
Explanation: An expression contains two symbols externally defined in a
shareable image. The linker can resolve expressions that contain only one
externally defined symbol.
User Action: Correct the expression and relink.

ILLSIGEXT,

illegal sign extension field value 'extension-value'

Facility: DEBUG, VMS Debugger
Explanation: An invalid value was entered for the sign extension field in a
field reference.
User Action: Reenter the command using a valid sign extension field value.

ILLSTRCLA,

illegal string class

Facility: STR, String Manipulation Facility
Explanation: The class code found in the class field of a descriptor is not
a string class code supported by the VMS Procedure Calling and Condition
Handling Standard.
User Action: If you are programming in a high-level language and using the
string data types and functions that are supplied by the language, check that
there are no logic errors where data is written outside array bounds or other
errors where data is written incorrectly. If you are creating descriptors, check
that all string descriptors are initialized before using them.

ILLSTROPS,

illegal string position

Facility: STR, String Manipulation Facility
Explanation: Successful completion. However, one of the character-position
parameters to a string routine pointed to a character-position that is before
the beginning of the input string or that is after the end of the input string.
User Action: Ensure that any parameter that is a character-position is greater
than zero and less than or equal to the length of the input string.

2-246

Messages

ILLSTRSPE, illegal string specification
Facility: STR, String Manipulation Facility
Explanation: Successful completion except that the character-position
parameters specifying a substring of a string parameter were inconsistent
because the ending character-position is less than the starting characterposition. A null string is used for the substring.
User Action: The applications program should verify that starting characterpositions are less than or equal to ending character-positions.
ILLSYMLEN,

symbol 'symbol' has illegal length 'length' in module 'modulename'

Facility: LIB, Library Facility
Explanation: The Run-Time Library encountered severe format errors in the
shareable image you are trying to call.
User Action: Enter the ANALYZE/IMAGE command specifying the image in
question. If the errors indicate an operating system internal error, submit a
Software Performance Report.
ILLSYMLEN, symbol exceeds 31 characters
Facility: MACRO, VAX MACRO Assembler
Explanation: The symbol name is longer than 31 characters. The assembler
truncated the name to 31 characters.
User Action: Specify a symbol name that has no more than 31 characters.
ILLTIR, illegal relocation command 'command-name' in module 'module-name'
record 'record-name' file 'filename'
Facility: LINK, Linker Utility
Explanation: A module contains an invalid object language command.
User Action: Submit a Software Performance Report on the appropriate
language compiler.
ILLTYP,

illegal library type

Facility: LBR, Librarian Subroutine Package
Explanation: This error message is generated by the Librarian routines. The
type of library specified in LBR$INI_CONTROL is invalid.
User Action: Correct the library type before calling the routine.
ILLTYPE,

illegal type of operands

Facility: DEBUG, VMS Debugger
Explanation: The type of the operand is invalid for the operator specified.
User Action: Use a valid operand.

2-247

Messages

ILLVAL,

boolean value must be 0 or 1

Facility: SMG, Screen Management Facility
Explanation: A Boolean capability is given a value other than 0 or 1.
User Action: Check your terminal definitions. Boolean capabilities must be 0
or 1: on or off, respectively.
ILLVAL,

illegal CPU time

Facility: RUN, Run Detached Utility
Explanation: The CPU time limit entered with the /TIME _LIMIT qualifier
value is too large.
User Action: Reenter the RUN command with a valid CPU time limit.
ILLVAL,

illegal value is present

Facility: CLI, Command Language Interpreter (DCL)
Explanation: A value is not within the valid range of values.
User Action: Use the DCL command HELP or refer to the VMS DCL

Dictionary, if necessary, for the valid values and reenter the command.
ILL_VALUE,

illegal parameter value

Facility: CONVERT, Convert Utility
Explanation: You have specified an invalid or out-of-range value on a
qualifier.
User Action: Specify a valid value and try again.
ILLVEC,

illegal interrupt or exception vector restart

illegal position ('decimal-number') or size ('decimal-number') in STO_
VPS command 'command-name' in module 'module-name' file 'filename'

Facility: LINK, Linker Utility
Explanation: The STO_VPS object language command has invalid
arguments.
User Action: Submit a Software Performance Report on the appropriate
language compiler.

2-248

Messages

IMAGEFMT,

command tables image has illegal format

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

IMAGEFNF, image file not found 'filename'
Facility: CU, Command Language Interpreter (DCL)
Explanation: You attempted to run a nonexistent image.
User Action: Check for typing errors and retry.

IMAGELEN,

an image spec is limited to 'max-length' characters in length

Facility: CDU, Command Definition Utility
Explanation: CDU encountered a image specification in the CLD file which
exceeded the maximum allowable file specification character count. Currently
file specification strings are limited to 63 characters in length.
User Action: Rename the image and/or use logical names to specify the
directory of the image.

IMAGE__NOT_FOUND,

this image has not yet been mapped

Facility: IMGACT, Image Activator
Explanation: An inconsistency exists between the shared image list stored in
the image fixup vector and the list of global ISDs stored in the image header.
This can possibly occur when images linked on older versions of VMS are run
on newer versions where new copies of shareable images are being referenced
by the old executable image.
User Action: Relink the executable images to achieve a consistent shareable
image linkage mechanism within the image header of your image.

IMGADDED,

added image for product

Facility: SYSMAN, Cluster System Management Utility
Explanation: The named image file was added to the loadable image
database for the named product.
User Action: Verify that the named image and product are correct.

IMGBASED, shareable image 'image-name' is already based
Facility: LINK, Linker Utility
Explanation: You specified a base address in an options file for a shareable
image that is already based.
User Action: Make the image position-independent so it can be based
anywhere; or remove the cluster option from the options file that tries to base
it.

2-249

Messages

IMGDUPINV,

image already in images table

Facility: SMI, System Management Intergator /Server
Explanation: The specified image name/product name pair already exists in
the loadable image file.
User Action: Select a different image name or product name.
IMGFILGON,

loadable image file is missing

Facility: SMI, System Management Intergator/Server
Explanation: The loadable image database currently in use is no longer
available.
User Action: Check for accidental deletion of the file.
IMGFILSPE,

/IMAGE specification must have only device name

Facility: BACKUP, Backup Utility
Explanation: The file specification for a volume to be processed with the
/IMAGE qualifier must contain only a device name.
User Action: Reenter the command using the device name only.
IMGHDR,

error while accessing the image header

Facility: INSTALL, Install Utility
Explanation: INSTALL encountered an error when trying to access the image
header. An accompanying error message explains the failure.
User Action: Correct the situation indicated by the accompanying error
message and reenter the command.
IMGINV,

image name invalid-must contain valid file name only

Facility: SYSMAN, Cluster System Management Utility
Explanation: The image name's file specification contains more than just a
file name.
User Action: Reenter the command with a valid image file name.
IMGNAME, image file 'filename'
Facility: CU, Command Language Interpreter (DCL)
Explanation: This message is issued with an associated message indicating
the problem.
User Action: Take corrective action based on the associated message.
IMGNOTFND,

image not found for product

Facility: SMI, System Management Intergator/Server
Explanation: The specified image file is not found in the loadable image
database for the given product.
User Action: Specify a product name contained in the database.

2-250

Messages

IMGRECSIZ , invalid image record size
Facility: MOM, Maintenance Operation Module
Explanation: The image that is being accessed to downline load is
unsupported.
User Action: Use a supported image type to downline load.

IMGREMOVED,

removed image for product

Facility: SYSMAN, Cluster System Management Utility
Explanation: The named image file was removed from the loadable image
database for the named product.
User Action: Verify that the named image and product are correct.

IMG _SIZ,

image header descriptor length is invalid

Facility: IMGACT, Image Activator
Explanation: The length of the fixed part of the image header is invalid. This
usually indicates a corrupted or invalid image.
User Action: Relink the image.

IMGTRACED,

TRACEBACK image cannot be privileged or execute_only

Facility: INSTALL, Install Utility
Explanation: This message indicates that an attempt is made to CREATE or
REPLACE a known file image with either the /PRIVILEGE or /EXECUTE_
ONLY qualifiers, and that the image had been linked with the /TRACEBACK
qualifier.
User Action: Relink the image using the /NOTRACEBACK qualifier and
retry the image installation.
1

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

Facility: RMS, VMS Record Management Services
Explanation: More than one XAB of the same type exists for the operation;
or another XAB type occurs within a subchain of allocation or key definition
XABs.
User Action: The status value (STV) field of the FAB provides the address
of the XAB in error. Verify that the call to the VMS RMS service is coded
correctly.

Inappropriate SCA Control Message
Facility: VAXport, VAXport Driver
Explanation: The VAXport driver closes the port-to-port virtual circuit to the
remote port.
User Action: Submit a Software Performance Report, including the error logs
and the crash dumps from the local and remote systems.

2-251

Messages

IN _BARRIER_WAIT , barrier in wait state, quorum not modified
Facility: PPL, Parallel Processing Facility
Explanation: The barrier is already in effect at the time of this call.
User Action: Recode the program to ensure that the barrier quorum is
established before anyone attempts to wait on the barrier.

INBUILTIN,

occured in built-in 'name'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: This message specifies the name of the built-in that generated
the error.
User Action: None.

INCBADDIR,

saved directory 'directory-name' has invalid format

Facility: BACKUP, Backup Utility
Explanation: In response to the /INCREMENTAL qualifier, the saved copy
(in the input save set) of the specified directory is not in the expected format
for a directory file. The file may have been corrupted when it is saved, or
save set data may have been lost.
User Action: After you complete the incremental restoration, check the files
for correct format.

INCCTXT,

incomplete crash context available

Facility: SDA, System Dump Analyzer
Explanation: A CPU that participated in the system BUGCHECK did not
save its context information correctly. Some CPU context information might
not be available for analysis.
User Action: None.

INCDATTIM,

incomplete date_time, missing fields with no defaults

Facility: LIB, Library Facility
Explanation: An incomplete date or time parameter is supplied.
User Action: Examine the date/time string.

INCDELERR,

error deleting 'filename'

Facility: BACKUP, Backup Utility
Explanation: An error is encountered during an attempt to delete
the specified file in response to the /INCREMENTAL qualifier. The
accompanying message provides additional information.
User Action: Correct the condition that caused the error and reenter the
command.

2-252

Messages

INCDELETE,

deleted 'filename'

Facility: BACKUP, Backup Utility
Explanation: The Backup Utility deleted the specified file in response to the
/INCREMENTAL qualifier. This message appears if you specify the /LOG
qualifier.
User Action: None.

INCDEVLIS,

disk and tape devices mixed in list

Facility: BACKUP, Backup Utility
Explanation: Disk and tape devices were mixed in a list of file specifications.
User Action: Reenter the command ensuring that if a list is used, the devices
in a list are the same type.

INCDSTNES,

incorrect DST nesting in module 'path-name', compiler error

Facility: DEBUG, VMS Debugger
Explanation: Incorrect Debug Symbol Table nesting occurred, such as an
invalid routine or data record nesting in the specified module. This message
normally indicates a compiler error.
User Action: Submit a Software Performance Report.

INCDSTQUE,

inconsistent destination queue type

Facility: JBC, Job Controller
Explanation: The type of the specified destination queue is inconsistent with
the requested operation.
User Action: Specify an appropriate type of destination queue for the
operation.

INCDUMPFORM,

dump file format incompatible with this version of SDA

Facility: SDA, System Dump Analyzer
Explanation: You attempted to analyze a dump file taken under one version
of the VMS operating system with an SDA image built against another
version. The format of the dump file has changed between the two versions
of the VMS operating system, making analysis impossible.
User Action: Analyze the dump file with an SDA image built against the
version of the VMS operating system that was running when the dump file
was taken.

INCENTERR,

error creating directory entry for 'filename'

Facility: BACKUP, Backup Utility
Explanation: The Backup Utility encountered an error during an attempt
to create a directory entry for the specified file in response to the
/INCREMENTAL qualifier.
User Action: Correct the condition that caused the error and reenter the
command.

2-253

Messages

INCFILATR,

incomplete file attribute data for 'filename'

Facility: BACKUP, Backup Utility
Explanation: There is an unexpected change in the file identifier and the file
attribute data is incomplete for the specified file. BACKUP tried to restore
a selected file from a save set, but the mounted volume did not contain the
beginning of the file.
User Action: Retry the BACKUP operation using the volume which contains
the beginning of the selected file as input.
INCFILSPE,

/INCREMENTAL specification must have only device name

Facility: BACKUP, Backup Utility
Explanation: The file specification for a volume to be processed with the
/INCREMENTAL qualifier must contain only a device name.
User Action: Reenter the command using only the device name.
INCFORMPAR, inconsistent form parameters
Facility: JBC, Job Controller
Explanation: The specified length, width, and margin parameters are
inconsistent. The sum of the top and bottom margins must be less than
the length, and the sum of the left and right margins must be less than the
width.
User Action: Correct the incorrect form parameters.
INCHMK,

inhibited CHMKernel trap

Facility: SYSTEM, VMS System Services
Explanation: An applications program attempted a system service that is
inhibited to it.
User Action: Ask the system manager which system services are currently
inhibited and remove them from the program.
INCKWDCOM, inconsistent keyword combination
Facility: VAXTPU, VAX Text Processing Utility
Explanation: The specified keyword combination is inconsistent.
User Action: Specify a consistent set of keywords.
Include file could not be closed
Facility: EDT, EDT Editor
Explanation: You specified the name of a file that EDT could not close while
using the INCLUDE command. Some problem exists at the system level that
prevents EDT from closing the file.
User Action: After determining what system problem prevents EDT from
closing the file, correct it.

2-254

Messages

Include file could not be opened
Facility: EDT, EDT Editor
Explanation: You specified the name of a file that EDT could not open while
using the INCLUDE command. Some problem exists at the system level that
prevents EDT from opening the file.
User Action: After determining what system problem prevents EDT from
opening the file, correct it.
Include file does not exist
Facility: EDT, EDT Editor
Explanation: You typed a file specification with the INCLUDE command for
a file that does not exist. The file might exist in a directory other than the
one you specified or implied with the command. Or you might have made a
typographical error in the file specification.
User Action: Enter the correct include file specification.
Include file input record too large, truncated to 255 characters
Facility: EDT, EDT Editor
Explanation: EDT can handle only 255 characters on a line. The file you
want to include has one or more lines in it that exceed 255 characters. EDT
truncates the line to be only 255 characters long.
User Action: None.
INCMEMNAM, specified shared memory name does not match
Facility: SYSGEN, System Generation Utility
Explanation: The logical name assigned to the shared memory by the
SYSGEN command SHARE does not match the name in the database of
shared memory that is specified previously.
User Action: Reenter the command with the correct name.
INCMVE,

incompatible management version

Facility: NCP, Network Control Program
Explanation: The requested function cannot be performed because the
software versions at the command source and command destination are
incompatible.
User Action: None. The software at the command destination must be
updated for the command to succeed.
INCOMPACP,

indicated ACP is incompatible with 'volume'

Facility: MOUNT, Mount Utility
Explanation: The ACP specified is not an ACP for the requested device.
User Action: Reenter the command; specify an ACP that is appropriate for
the particular device type.

2-255

Messages

INCOMPAT,

'input-filespec' (input) and 'output-filespec' (output) have
incompatible attributes

Facility: Shared by several facilities
Explanation: This warning message indicates that file incompatibility may
exist between files that have been appended or concatenated. This message
can occur if files created by different methods are concatenated, for example,
files created with the DCL command WRITE and files created by the DCL
command SORT /RSXl l. The command continues execution.
User Action: Determine whether the incompatibility presents a problem and
if it does, delete the output files, modify the format of one or more input files,
and reenter the command.
The format of a file can be modified by editing the file with the SOS or SLP
editors and creating a new version of the file.
INCOMPAT,

feature incompatible with previous system version

Facility: SYSTEM, VMS System Services
Explanation: This alternate success status indicates that the function
requested is not compatible with the version of the 1/0 driver in use. This
error message typically occurs when a remote terminal link is used between
different versions of VMS. For example, it could indicate that the function
requested by the newest VMS Version 3.0 is not implemented on the previous
VMS Version 2.5.
User Action: Upgrade systems using remote terminals so that they use the
same version of the operating system.
INCOMPAT,

qualifiers incompatible with already mounted volume

Facility: MOUNT, Mount Utility
Explanation: A DCL command MOUNT is entered to mount a shareable
volume that is already mounted; the characteristics of the volume are already
established and cannot be changed.
User Action: Use the DCL command SHOW DEVICE to determine how the
volume is mounted. Reenter the DCL command MOUNT /SHARE without
qualifiers.
INCOMPEXI,

incompatible element with the same name already exists

Facility: PPL, Parallel Processing Facility
Explanation: All PPL objects must have unique names.
User Action: Recode the call to specify a unique name.
INCOMPL,

'LMB-name' not completely written in the dump file

Facility: SDA, System Dump Analyzer
Explanation: Information corresponding to a Logical Memory Block (LMB)
is saved only partially in this subsetted dump file. The dump file may or
may not be useful for analysis, depending on which LMB was only partially
saved. If the SDA image retains control after the error, then some analysis is
possible, but some information may not be available in the dump file.
User Action: None. The dump file might not be useful for analysis.

2-256

Messages

INCOMPLETE,

previous incomplete operation prevents execution

Facility: JBC, Job Controller
Explanation: The requested queue management operation cannot be executed
because a previously requested queue management operation has not yet
completed.
User Action: Retry the operation at a later time. For a queue-related
operation, it may be necessary to enter the STOP /QUEUE/RESET command
if this error condition persists. However, for a STOP /QUEUE/MANAGER
request (which may take a long time to complete), you need to wait until the
request is completed.
INCONISD,

inconsistent ISD structures detected

Facility: IMGACT, Image Activator
Explanation: Either an image section descriptor is found to cross an image
header block boundary, or there is an indication that an ISD would be found
in the next header block and there is no such ISD. This usually indicates a
corrupted or invalid image.
User Action: Relink the image.
INCONQUALS,

qualifier /'qualifier' contradicts qualifier /qualifier'

Facility: BACKUP, Backup Utility
Explanation: The two qualifiers specified are in conflict with one another and
cannot be used together in the BACKUP command.
User Action: Reenter the BACKUP command with only one of the two
qualifiers. For more information on how qualifiers affect the BACKUP
command, see the VMS Backup Utility Manual.
INCONSDEV,

inconsistent device types

Facility: MOUNT, Mount Utility
Explanation: Both disks and magnetic tapes appear in the list of devices to
be mounted.
User Action: Specify one or the other and reenter the command; check the
logical name assignments.
INCONSTATE,

inconsistent UBA database

2-257

Messages

INCPTREF,

increment page table reference count error

inconsistent queue type

Facility: JBC, Job Controller
Explanation: The type of the specified queue is inconsistent with the
requested operation.
User Action: Specify an appropriate type of queue for the operation.
INCQUOTA,

QUOTA.SYS indicates 'n' blocks used, actual use is 'n' blocks for
['uic']

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the disk usage for the specified
UIC, as recorded in the quota file, did not agree with the actual disk usage.
User Action: None. The utility corrects the quota file.
INCRVN,

incorrect relative volume mounted on 'device-name'

Facility: BACKUP, Backup Utility
Explanation: Either the wrong volume of a multivolume disk save-set was
mounted, or the positional order of the devices in the input specification does
not agree with the relative volume numbers recorded on the volumes.
User Action: Locate and mount the correct volume.
INCSEGTRA,

incomplete segmented transfer request posted

Facility: SYSTEM, VMS System Services
Explanation: A driver returned a success status but failed to complete the
current segment of a segmented transfer.
User Action: If this error can be reliably reproduced, the media and program
producing the error should be submitted with a Software Performance Report.
INCSETCNT,

incorrect number of devices in input specification

Facility: BACKUP, Backup Utility
Explanation: The number of devices in the input specification does not agree
with the volume set count recorded on relative volume 1.
User Action: Reenter the command with the correct number of devices.

2-258

Messages

INCVOLLABEL,

incorrect volume label

Facility: SYSTEM, VMS System Services
Explanation: The label specified does not match the label on the volume.
User Action: Verify that the correct volume is mounted; verify the label
entered. Repeat the request specifying the correct volume label or specifying
OVERRIDE:ID, which requires either that you have the volume protection
privilege or that you are the volume owner.
INDEX,

invalid index file position

Facility: INIT, INITIALIZE Command
Explanation: The block specified for the position of the index file for a disk
volume is larger than the number of blocks on the disk. The DCL command
INITIALIZE cannot write the index file.
User Action: Reenter the command; specify a position for the index file that
is within the range of blocks on the volume.
INDEXERR, index error in 'library-name'
Facility: LIBRAR, LIBRARY Command
Explanation: Possible causes of the error are:
•

An error occurred while searching or traversing the index

•

A VMS RMS error occurred

•

Not enough virtual memory is available

User Action: Compress the library before reentering the command string.
INDEXOVFL,

index area overflow in section-please submit SPR

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

array index data type, 'type', unsupported

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The data type of the array index is not supported.
User Action: Use only integers for array indexing.
IND_OVR, indexed output file must already exist
Facility: SORT, Sort/Merge Utility
Explanation: You specified indexed output file organization, but the file did
not already exist.
User Action: First create the indexed file with the RMS Define Utility. The
primary key of the file should be the same as the sort key for efficiency, but
is not required.

2-259

Messages

INHCHME,

inhibited CHMExecutive trap

INI,

improperly nested: 'string'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: Your conditional DSR commands (.IF /.IFNOT and .ELSE
j.ENDIF) are improperly matched.
User Action: Correct the DSR commands so they match.

INITERR,

error initializing 'library-name'

Facility: LIBRAR, LIBRARY Command
Explanation: An error occurred initializing the specified library. This
message is issued with an accompanying message.
User Action: Take corrective action based on the accompanying message.

INITERR,

error initializing 'library-name'

Facility: LIBRAR, LIBRARY Command
Explanation: There is insufficient virtual memory available.
User Action: Ask the system manager to increase your page file quota or
VIRTUALP AGECNT.

INITIAL,

language is 'language-name', module set to 'path-name'

Facility: DEBUG, VMS Debugger
Explanation: This message is displayed when the debugger is invoked by
the image activator. The language is set to 'language-name', and the module
to 'path-name'. Module 'path-name' is the first module specified in the
LINK command, and language 'language-name' is the language used in that
module.
User Action: None.

INITPRS,

error code of 'xx' on command line parse init

Facility: PATCH, Patch Utility
Explanation: A CLI callback failure occurred due to the error represented as
xx.
User Action: Submit a Software Performance Report.

2-260

Messages

INM, illegal number value: 'string'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: The parameter value is too large, too small, invalid, or not a
number.
User Action: Check to see that the value is formatted properly.

INPBUFOVR,

input buffer overflow is detected

Facility: DTK, DECtalk Facility
Explanation: An input buffer overflow malfunction occurred after the
DECtalk device was turned on.
User Action: Check the DECtalk hardware.

INPCONERR,

input conversion error

Facility: OTS, General Purpose Facility
Explanation: There is an invalid character in the input string. Or the output
value is not within the range of destination data type.
User Action: Correct the input string or change the destination data type.

INPJILES,

too many input files

Facility: CONVERT, Convert Utility
Explanation: You listed more than 10 input files.
User Action: Reduce the number of input files or combine them so that you
list no more than 10.

INPJILES,

too many input files specified

Facility: SORT, Sort/Merge Utility
Explanation: You listed more than 10 input files.
User Action: Reduce the number of input files or combine them so that you
list no more than 10.

INPSTRTRU, input string truncated
Facility: LIB, Library Facility
Explanation: An input string accepted by LIB$GET_INPUT was truncated
to fit the string descriptor passed to it. This message is associated with a
status code returned from a Run-Time Library procedure and is not normally
displayed by the operating system.
User Action: Correct your program by increasing the field length in the
descriptor.

INPTOOLON,

input string is too long

Facility: SMG, Screen Management Facility
Explanation: The length of an input string exceeded 255 characters.
User Action: Shorten the string to fewer than 255 characters.

2-261

Messages

INPUT,

'filename', 'n' selected, 'n' rejected, 'n' skipped

Facility: ERF, Error Log Utility
Explanation: This message reports the input file name and the number of
entries selected, rejected, or skipped from the input file.
User Action: None.
INPUT,

'filespec', 'n-records' selected, 'n-records 'rejected

Facility: ACCOUNTING, Accounting Utility
Explanation: This informational message is displayed when the /LOG
qualifier is used. It describes how many records were selected and/or rejected
for each input file.
User Action: None.
Input file could not be closed
Facility: EDT, EDT Editor
Explanation: EDT could not close the input file that you named in your EDIT
/EDT command line or in the line mode INCLUDE command line. Some
problem exists at the system level that prevents EDT from closing the file.
User Action: After determining what system problem prevents EDT from
closing the file, correct it.
Input file could not be opened
Facility: EDT, EDT Editor
Explanation: Either the command contains faulty syntax or a nonexistent
directory is specified.
User Action: Check your command syntax. Ensure that any directory
specified exists. Reenter the command using the correct syntax.
Input file does not exist
Facility: EDT, EDT Editor
Explanation: The input file is not contained in the specified directory. When
you are creating a new file using the EDT editor, this message is displayed
indicating the creation of a new file.
User Action: No action is necessary if you are creating a file. If you are
editing an existing file, ensure that you have typed the file specification
correctly and reenter the command.
Input file does not have standard text file format
Facility: EDT, EDT Editor
Explanation: You edited a file that does not have standard file attributes (for
example, a file that does not have carriage returns at the ends of lines).
User Action: This message is only a warning. EDT allows you to edit the file,
but be aware that difficulties can arise if you attempt to edit the nonstandard
elements.

2-262

Messages

Input record too large, truncated to 255 characters
Facility: EDT, EDT Editor
Explanation: A record in the input file exceeds 255 characters.
User Action: Modify the record in the input file to contain 255 characters or
less. This message can also occur due to an attempt to edit a file that does
not contain ASCII text.

INPUT_CANCELED,

input request canceled

Facility: VAXTPU, VAX Text Processing Utility
Explanation: Terminal input indicates that the input request was canceled.
User Action: None. This is an internal status.

INPUTERR,

error opening primary input file SYS$INPUT

Facility: LOGIN, Login Processor
Explanation: An error occurred while trying to open SYS$INPUT. An
accompanying message will provide more information.
User Action: Correct the problem described by the accompanying message,
and try again.

INSCLIMEM,

insufficient CLI memory

Facility: LIB, Library Facility
Explanation: The CLI could not obtain enough virtual memory to perform
the function. This may be caused by having too many symbols defined.
User Action: Delete some symbol definitions. Then retry the operation.

INSCOLL,

not enough collections for summary processing

Facility: MONITOR, Monitor Utility
Explanation: An error occurred during summary processing. For summary
processing to take place, at least two collections must be completed.
User Action: This error may occur if you interrupt (by typing CTRL/C) a
summary request before the second collection has been completed. Reenter
your command and allow at least two collections to be completed.

INSDFAIL,

the installation of a product has failed.

Facility: VMSINSTAL, Install Procedures
Explanation: An error occurred in an attempt to defer callbacks during the
installation.
User Action: Examine the console output to determine the cause of the error.
If you are unable to resolve the problem, contact your DIGITAL field service

representative.

2-263

Messages

INSEF,

insufficient event flag

Facility: LIB, Library Facility
Explanation: A call is made to LIB$GET_EF to allocate an event flag number,
but all event flag numbers were unavailable.
User Action: Use LIB$FREE_EF to free previously allocated event flag
numbers if they are no longer being used.
INSERTED, module 'module-name' inserted in 'library-name'
Facility: LIBRAR, LIBRARY Command
Explanation: This success message is generated by the DCL command
LIBRARY. This message is informational.
User Action: None.
INSERTERR,

error inserting 'module-name' in 'library-name'

Facility: LIBRAR, LIBRARY Command
Explanation: This error message is generated by the DCL command
LIBRARY. One of the following conditions prevented the DCL command
LIBRARY from inserting the specified modules into the library:
•

The modules are not formatted correctly.

•

The organization of the input file is incorrect.

•

A VMS RMS error has occurred.

•

There is not enough virtual memory.

User Action: Correct the error and insert the file.
INSFAIL,

the installation of 'product-name' has failed.

Facility: VMSINSTAL, Install Procedures
Explanation: The installation failed.
User Action: Examine the console output to determine the cause of the error.
If you are unable to resolve the problem, contact your DIGITAL field service
representative.
INSFANL,

insufficient data in Definition and/or Analysis files

Facility: FDL, Edit/FDL Utility
Explanation: EDIT /FDL is executing an optimize script invoked by the
/NOINTERACTIVE qualifier. Certain information about the file is missing
from the definition or the analysis file.
User Action: Supply the missing information by reexecuting the ANALYZE
/RMS_FILE/FDL command to produce another analysis file and/ or use the
analysis file as the definition file.

2-264

Messages

INSFARG,

insufficient call arguments

Facility: SYSTEM, VMS System Services
Explanation: A system service argument list contained fewer than the
required number of arguments for the service.
User Action: Check for a programming error. Refer to the VMS System
Services Reference Manual for coding specifications.
INSFBUFDP,

unable to allocate a buffered datapath

Facility: SYSTEM, VMS System Services
Explanation: This message is associated with a status code returned from
a request to an LPAll-K interface device. A USA-buffered data path is not
available for allocation.
User Action: Rerun the program.
INSFCDT,

insufficient CDT entries

Facility: SYSTEM, VMS System Services
Explanation: There is currently an insufficient number of connection
descriptor table entries for completing a request.
User Action: Attempt your request at a later time.
INSFMAPREG, insufficient map registers
Facility: SYSTEM, VMS System Services
Explanation: This message is associated with a status code returned from a
request to an LPAll-K interface device to initialize the LPAll-K or start data
transfer. Insufficient UNIBUS adapter (UBA) map registers are available to
map the command table or buffer areas.
User Action: If the map registers were preallocated when the drive is loaded,
increase the preallocation.
INSFMEM,

insufficient dynamic memory

Facility: SYSGEN, System Generation Utility
Explanation: There is not enough room in the nonpaged pool to load a driver
or create a control block for it.
User Action: Reboot the system, stopping in SYSBOOT, and increase the
value of the parameter NPAGEDYN.
INSFMEM,

insufficient dynamic memory

Facility: SYSTEM, VMS System Services
Explanation: A command or image exhausted the system pool of available
dynamic memory and the system cannot complete the request.
Or, the system manager did not allocate enough dynamic memory.
User Action: Check for a programming error; this status code can be returned
from a system service request when the image has disabled resource wait
mode. Notify the system manager if insufficient memory is allocated.

2-265

Messages

INSFMEM, insufficient good memory to continue
Facility: VAXCLUSTER, VAXcluster Facility
Explanation: Too little memory on the satellite is available for bootstrap
execution.
User Action: Check that the configuration matches the minimum guidelines
in the Software Product Description (SPD). If they do not match, add more
memory. Run diagnostics on memory to verify that all the system memory is
functional.

INSFPRM,

missing command parameters-supply all required parameters

Facility: CLI, Command Language Interpreter (DCL)
Explanation: A command cannot be executed because one or more required
parameters are missing from the command. With the DCL command
interpreter, this message occurs only during the execution of command
procedures; at the interactive level, the command interpreter continues to
prompt until all required parameters are entered.
User Action: Correct the command procedure.

INSFRAME,

insufficient call frames to unwind

Facility: SYSTEM, VMS System Services
Explanation: An unwind request specified a depth that is greater than the
number of call frames on the stack.
User Action: Check for a programming error.

INSFSPTS,

insufficient SPTs to map process buffer to system

Facility: SYSTEM, VMS System Services
Explanation: There are insufficient system page table entries to map a
process buffer to the system.
User Action: Reboot the system and increase the SYSGEN parameter
SPTREQ.

INSFVM,

unable to obtain virtual memory

Facility: EVL, Event Logger
Explanation: A program or system configuration problem exhausted virtual
memory.
User Action: Check the value of the VIRTUALPAGECNT using SYSGEN. If
the value is 2048 or greater, then this message indicates a program problem.

2-266

Messages

INSFWSL,

insufficient working set limit

Facility: SYSTEM, VMS System Services
Explanation: A command or image cannot execute because the current
working set limit for the process is less than the number of pages that must
be resident in memory at the same time for an image to execute.
User Action: Check for a programming error; verify that the number of
pages requested in a system service request is accurate. If the number of
pages is accurate, try to increase the size of the working set limit with the
DCL command SET WORKING_SET and retry the program.

INSKIPPED,

unreasonable instruction stream- n bytes skipped
1

Facility: SDA, System Dump Analyzer
Explanation: SDA cannot decode a range of memory locations into VAX
MACRO instruction format because the locations do not begin on an
instruction boundary.
User Action: None. SDA ignores the bytes it cannot translate.

INSLUN,

insufficient logical unit numbers

Facility: LIB, Library Facility
Explanation: A call is made to LIB$GET_LUN to allocate a logical unit
number, but all logical unit numbers were unavailable.
User Action: Use LIB$FREE_LUN to free previously allocated logical unit
numbers if they are no longer used.

INSNFREP AG,

insufficient nonfree pages

INSOPRND,

missing instruction operand

Facility: PATCH, Patch Utility
Explanation: One or more operands were omitted from the instruction.
User Action: Add the required number of operands and retry the operation.

INSQUOCRE , insufficient quota to create a subprocess
Facility: SMG, Screen Management Facility
Explanation: The current BYTLM or PRCLM quota value is too small to
create a subprocess.
User Action: Increase the BYTLM or the PRCLM quota value, or both.

2-267

Messages

INSSWPFIL,

insufficient swap file space

Facility: BUGCHECK, System Bugcheck
Explanation: The VMS software detected an irrecoverable, inconsistent
condition. After all of physical memory is written to a system dump file, the
system will automatically reboot if the BUGREBOOT system parameter is set
to 1.
User Action: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error, and that includes a BACKUP save set
containing the system dump file and the error log file active at the time of the
error. (Use the /IGNORE=NOBACKUP qualifier on the BACKUP command
that produces the save set included with the SPR.)
Insufficient memory
Facility: EDT, EDT Editor
Explanation: There is insufficient memory to complete the last command.
This message can occur when you define a new text buffer or use the EDT
command DEFINE KEY.
User Action: Exit from EDT and restart your editing session. To avoid this
problem in the future, define fewer keys and text buffers or decrease the size
of the text buffers.
Insufficient Non-paged Pool for Initialization
Facility: VAXport, VAXport Driver
Explanation: The port driver will not attempt to start the port.
User Action: Increase the NP AGEDYN pool SYSGEN parameter and reboot
the system.
Insufficient Non-paged Pool for Virtual Circuits
Facility: VAXport, VAXport Driver
Explanation: After finding that insufficient memory resources are available
for normal communication, the port driver breaks a virtual circuit.
User Action: Increase the NP AGEDYN pool SYSGEN parameter and reboot
the system.
INSUFFMEM,

dump file contains less than 512K of memory

Facility: SDA, System Dump Analyzer
Explanation: The information in the first block of the dump file indicates
that less than 512K of memory information was saved in the dump file. The
dump file contents are assumed to be invalid, since all the VMS operating
systems require more than 512K of memory to boot.
User Action: None. The dump file is not useful for analysis.

2-268

Messages

INSUFPAT,

'nn' bytes requested, patch area at 'addr' contains 'nn' bytes

Facility: PATCH, Patch Utility
Explanation: The user-defined patch area is not large enough to
accommodate the specified code.
User Action: Use an alternate patch area, for example, the default patch area.
Generally, the default patch area is expandable.
INSVIRMEM,

insufficient virtual memory

Facility: STR, String Manipulation Facility
Explanation: An attempt is made to allocate heap storage for use as dynamic
strings, or string temporaries failed.
User Action: If you allocate space by calling STR$GET1_DX or LIB$GET_
VM, verify, when you finish using the storage, that the storage is released
by calling STR$FREEl_DX or LIB$FREE_VM, respectively. If you are using
a high-level language and have not directly allocated space, you can cause
this error by having a large number of long strings. In this case, make sure to
reduce strings to zero length when they are not in use.
INSVIRMEM, insufficient virtual memory
Facility: VAXTPU, VAX Text Processing Utility
Explanation: An attempt to allocate additional memory for working storage
failed.
User Action: Purge or delete files to free space in memory.
INSVIRMEM, insufficient virtual memory available
Facility: PPL, Parallel Processing Facility
Explanation: The calling service does not have sufficient available space to
complete the request.
User Action: If you use extensive PPL services, try specifying a larger value
to PPL$INITIALIZE. Otherwise, check your system quotas to see if more
space is needed.
INSVIRMEM, insufficient virtual memory-DIF aborted
Facility: DIFF, DIFFERENCES Command
Explanation: The Differences Utility has run out of virtual memory for one
of the following reasons: (1) the Differences Utility encountered a difference
section that contains more records than can be stored in virtual memory, or
(2) the Differences Utility ran out of virtual memory while storing records
away to be used while generating additional listings.
User Action: In the first case, cut down the size of the offending difference
section; the listing will have terminated in the middle of the section. You can
do this by increasing the value of the /WINDOW parameter if it is not being
defaulted.
In the second case, rerun the Differences Utility and generate one listing at a
time.

2-269

Messages

INSVIRMEM,

insufficient virtual memory for 'number' pages for cluster 'clustername'

Facility: LINK, Linker Utility
Explanation: The linker could not allocate enough virtual memory in the
resulting image to contain a cluster.
User Action: Determine why the linker ran out of virtual memory by
consulting a /FULL map, correct, and relink.
INSVIRMEM,

insufficient virtual memory (See also the following messages)

Facility: MACRO, VAX MACRO Assembler
Explanation: The module being assembled has too many symbols and macro
definitions for the virtual memory available or a macro definition called itself
(a recursive definition). The assembler terminated the assembly.
User Action: Increase the virtual memory available by contacting the system
manager; reduce the level of macro nesting; split the module into several
smaller modules; or eliminate the recursive macro definition.
INSWAPERR,

inswap read error

internal data corrupted in run-time library

Facility: OTS, General Purpose Facility
Explanation: In a call to the Run-Time Library, a database consistency check
failed. An applications program can cause this by referring to a location
outside a dimensioned array, or by requesting input from an address outside
the program.
User Action: Recompile any module that you think may refer outside a
dimensioned array with the /CHECK=BOUNDS qualifier. Relink and rerun
your program.
INTDELPRC,

participant stopped by PPL$STOP

Facility: PPL, Parallel Processing Facility
Explanation: An application call to PPL$STOP forced the termination of this
participant.
User Action: Since the application itself terminated this party, any actions
are application-dependent.

2-270

Messages

INTDIV,

arithmetic trap, integer divide by zero at PC= xxxxxxxx', PSL =
xxxxxxxx
1

Facility: SYSTEM, VMS System Services
Explanation: An arithmetic exception condition occurred as a result of an
attempt to divide by zero.
User Action: Examine the PC location displayed in the message and check
the program listing to verify that operands and variables are specified
correctly.
INTEGER, please enter an integer value.
Facility: VMSINSTAL, Install Procedures
Explanation: VMSINSTAL is prompting you for an integer.
User Action: Specify an integer.
INTERLOCK,

unable to acquire system data structure interlock

Facility: SYSTEM, VMS System Services
Explanation: The system data structure interlock cannot be acquired.
Another processor probably crashed while holding a data structure lock.
User Action: Retry the operation, or reboot the system and reinitialize shared
memory. Refer to the Guide to Maintaining a VMS System.
INTERNAL,

LATCP internal error

Facility: LATCP, LAT Control Program
Explanation: LATCP or the LAT port driver has insufficient buffer space or
has detected an internal error.
User Action: Verify that you entered the correct command. If the problem
persists, submit a Software Performance Report.
Internal software error-please submit a Software Performance Report
Facility: Shared by several facilities
Explanation: A problem exists with the software as installed on your system.
User Action: Submit a Software Performance Report.
INTERR,

internal debugger error in 1debug-routine-name 1

Facility: DEBUG, VMS Debugger
Explanation: An internal debugger error has been encountered.
User Action: If the error is reproducible, submit a Software Performance
Report and, if possible, enclose both a copy of the program being debugged
and a logged debugging session that reproduces the error.

2-271

Messages

INTHCHAR,

internal error: encountered character of class h-string

Facility: CDU, Command Definition Utility
Explanation: CDU encountered a corrupted internal data structure.
User Action: Submit a Software Performance Report. Include the CLD file in
the report.
INTINVNODE, internal error: invalid node encountered
Facility: CDU, Command Definition Utility
Explanation: CDU encountered a corrupted internal data structure.
User Action: Submit a Software Performance Report. Include the CLO file in
the report.
INTLOGERR,

internal logic error

Facility: LIB, Library Facility
Explanation: A LIB$ routine detected an internal logic error. This message is
associated with a status code returned from the Run-Time Library.
User Action: Submit a Software Performance Report.
INTMEMERR,

internal memory-pool error

Facility: DEBUG, VMS Debugger
Explanation: The debugger's internal memory area is corrupted or is
inconsistent. This can be caused by an internal debugger error or by random
stores by the application program.
User Action: Remove random stores from the application program or submit
a Software Performance Report.
INTNODESP ACE,

internal error: node space exhausted

Facility: CDU, Command Definition Utility
Explanation: CDU exhausted internal memory.
User Action: Submit a Software Performance Report including the CLD file.
INTOVF,

arithmetic trap, integer overflow at PC = xxxxxxxx PSL = xxxxxxxx
1

1
,

Facility: SYSTEM, VMS System Services
Explanation: An exception condition occurred as a result of an integer
overflow.
User Action: Examine the PC location displayed in the message and check
the program listing to verify that operands or variables are specified correctly.
INTOVF,

integer overflow

Facility: LIB, Library Facility
Explanation: Either the library routine or the hardware detected an integer
overflow.
User Action: Choose a destination data type with a larger range.

2-272

Messages

INTP ATHSTKOV,

internal error: path stack overflow

Facility: CDU, Command Definition Utility
Explanation: CDU exhausted internal memory.
User Action: Submit a Software Performance Report including the CLD file.

INTRNLERR, internal error: 'code'
Facility: INSTALL, Install Utility
Explanation: INSTALL encountered an internal error.
User Action: Submit a Software Performance Report.

INTRNLERR,

LBR internal error. Please submit SPR.

Facility: LBR, Librarian Subroutine Package
Explanation: This is an internal consistency check.
User Action: Submit a Software Performance Report that includes relevant
files wherever possible.

INTSTKOV, linker internal stack of 'number' overflowed in module 'modulename' file 'filename'
Facility: LINK, Linker Utility
Explanation: The linker's internal stack overflowed because of a complex
calculation.
User Action: Submit a Software Performance Report.

INTSTKUN, linker internal stack of 'number' underflowed in module 'modulename' file 'filename'
Facility: LINK, Linker Utility
Explanation: An object module attempted to remove more items from the
stack than it pushed on it.
User Action: Submit a Software Performance Report on the appropriate
language compiler.

INTTERMIN,

participant stopped by PPL$TERMINATE

Facility: PPL, Parallel Processing Facility
Explanation: An application call to PPL$TERMINATE forced the temination
of this participant.
User Action: Since the application itself terminated this party, any actions
are application-dependent.

2-273

Messages

INVACC,

invalid access control specified for the executor

Facility: NCP, Network Control Program
Explanation: You specified invalid or conflicting access control information
for connecting to an executor node.
User Action: Confirm that the access control specified is correct. Use either
the standard VMS access control format (node-spec) or the NCP-specific
format (USER, ACCOUNT, PASSWORD), but do not use both.
INVACCESS,

error in access specification

Facility: AUTHORIZE, Authorize Utility
Explanation: The access specification contains a syntax error.
User Action: Correct the syntax and reenter the access specification.
INVACCESS,

invalid file access specified

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

record 'record' has invalid or unrecognized format

Facility: ACCOUNTING, Accounting Utility
Explanation: A record in the accounting file has an invalid or unrecognized
format. The ACCOUNTING Utility will attempt to continue processing
records.
User Action: Examine the accounting file and verify that it is a valid VMS
accounting file. Check for hardware errors. Submit a Software Performance
Report with the accounting file in question, if the problem persists.
INVADAP,

invalid adapter name specified

Facility: SYSGEN, System Generation Utility
Explanation: The specified adapter number is found to be invalid after
bootstrap.
User Action: Reenter the command using the correct adapter number.
Invalid buffer name
Facility: EDT, EDT Editor
Explanation: Invalid syntax is used for the buffer name in the EDT
command.
User Action: Reenter the EDT command specifying valid syntax for the
buffer name.

2-274

Messages

Invalid character
Facility: EDT, EDT Editor
Explanation: You attempted to insert a character by using the SPECINS
function or ASC command, but did not supply a valid decimal equivalent for
the character.
User Action: Reenter the command specifying a valid decimal equivalent for
the character.
Invalid entity
Facility: EDT, EDT Editor
Explanation: The entity portion of the EDT change mode command is not
recognized.
User Action: Reenter the EDT change mode command specifying a valid
entity.
Invalid option for that command
Facility: EDT, EDT Editor
Explanation: The /OPTION qualifier is specified for an EDT command that
does not accept the /OPTION qualifier.
User Action: Reenter the EDT command without specifying the /OPTION
qualifier.
Invalid parameter for SET or SHOW
Facility: EDT, EDT Editor
Explanation: The EDT commands SET and SHOW do not accept one of the
parameters you specified.
User Action: Reenter the EDT command specifying a valid parameter.
Invalid string
Facility: EDT, EDT Editor
Explanation: You specified a string that EDT could not handle. For example,
this message occurs when you use a search string longer than 64 characters.
User Action: Reenter the command specifying a valid string.
Invalid subcommand
Facility: EDT, EDT Editor
Explanation: You have used an improper name for an EDT change mode
subcommand.
User Action: Use a valid name. For a list of the EDT change mode
subcommands, type HELP CHANGE SUBCOMMANDS in line mode.

2-275

Messages

Invalid value in SET command
Facility: EDT, EDT Editor
Explanation: The EDT command SET has an invalid keyword.
User Action: Reenter the command specifying a valid keyword.

INVALIGN, invalid alignment
Facility: MACRO, VAX MACRO Assembler
Explanation: An unrecognized keyword or no integer or no keyword
followed the .ALIGN directive.
User Action: Correct the syntax of the .ALIGN directive.

INVALQUAL,

the 'qualifier-name' is an invalid qualifier in this context

Facility: BAD, Bad Block Locator Utility
Explanation: The qualifier indicated is issued in an invalid context.
User Action: Consult the documentation for the list of valid, nonconflicting
qualifier specifications and usage in various analysis contexts.

INVARG,

invalid argument

Facility: DCX, Disk Compression Utility
Explanation: A DCX procedure has been called with an incorrect argument.
User Action: Correct the application program.

INVARG,

invalid argument

Facility: DTK, DECtalk Facility
Explanation: The value of an argument is not in the correct range.
User Action: Examine each argument. Determine which one is out of range,
and correct your program.

INVARG,

invalid argument

Facility: PPL, Parallel Processing Facility
Explanation: A specified argument is invalid.
User Action: Recode the program to pass a valid argument.

INVARG,

invalid argument

Facility: SMG, Screen Management Facility
Explanation: The value of some argument is not in the correct range.
User Action: Examine each argument. Determine which one is out of range
and correct your program.

2-276

Messages

INVARG,

invalid arguments

Facility: Shared by several facilities
Explanation: This message is associated with a status code returned from the
Run-Time Library. A calling program passed one or more invalid arguments
to a library (LIB$) routine.
User Action: Check the arguments for the call to the Run-Time Library and
correct the program.
INVARGMAT,

invalid argument to math library user PC location

Facility: MTH, Mathematics Facility
Explanation: One of the math procedures is called with an invalid argument.
User Action: Locate the math procedure call that caused the error and correct
the argument.
INVARGORD,

invalid argument order

Facility: LIB, Library Facility
Explanation: The arguments were passed in an invalid order.
User Action: Examine each argument. Correct the program to pass the
arguments in a valid order.
INVARRDSC,

invalid array descriptor

Facility: DEBUG, VMS Debugger
Explanation: An array descriptor in the image does not have the correct
format. This can be caused by a reference to a VAX BASIC array when the
first line of the program has not been executed. The array is not set up
correctly until the BASIC program initialization is done. This message can
also be caused by an applications program or a DEPOSIT command altering a
compiler-generated array descriptor.
User Action: If the reference is to a VAX BASIC array, enter a STEP or GO
command to ensure that the BASIC program initialization is done and repeat
the reference. Otherwise, if an array descriptor has not been altered, submit a
Software Performance Report.
INVARRDSC,

invalid array descriptor

Facility: PATCH, Patch Utility
Explanation: The expression contained an array descriptor that PATCH did
not recognize.
User Action: Correct the array descriptor and retry.
INVATTSIZ,

invalid attribute record size in save set

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

2-277

Messages

INVATTSTR, invalid attribute record structure level in save set
Facility: BACKUP, Backup Utility
Explanation: An incorrect value occurred in the structure level field of a save
set record. Data in the save set is corrupted.
User Action: None. Save set data has been lost.

INVATTVAL,

invalid attribute record value in save set

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

INVBJLEOF,

invalid end of file position in BACKUP journal

Facility: BACKUP, Backup Utility
Explanation: The end-of-file pointer recorded for the journal file specified by
the /JOURNAL qualifier is invalid. The journal file is corrupted and cannot
be used.
User Action: Reconstruct the journal file from backup media.

INVBJLSIZ,

invalid record size in BACKUP journal

Facility: BACKUP, Backup Utility
Explanation: An invalid record size occurred in the journal file specified by
the /JOURNAL qualifier. The journal file is corrupted and cannot be used.
User Action: Reconstruct the journal file from backup media.

INVBJLSTR,

invalid structure level in BACKUP journal

Facility: BACKUP, Backup Utility
Explanation: The structure level recorded in the journal file specified by the
/JOURNAL qualifier is invalid. The journal file is corrupted and cannot be
used.
User Action: Reconstruct the journal file from backup media.

INVBJLTYP,

invalid record type in BACKUP journal

Facility: BACKUP, Backup Utility
Explanation: An invalid record type occurred in the journal file specified by
the /JOURNAL qualifier. The journal file is corrupted and cannot be used.
User Action: Reconstruct the journal file from backup media.

INVBKT,

invalid bucket at VBN 'number'

Facility: CONVERT, Convert Utility
Explanation: The Convert/Reclaim Utility has detected a structure error in
the bucket specified by 'number'.
User Action: Use the ANALYZE/RMS_FILE command to determine the
cause of the structure error.

2-278

Messages

INVBLK,

invalid RMS control block at virtual address nnnn

Facility: FOL, Create/FOL Utility
Explanation: FDL$GENERATE or FDL$RELEASE is passed an address that
is not a valid RMS control block.
User Action: Correct the invalid address.
INVBLK,

invalid RMS control block at virtual address 1XXXXXXXX 1

Facility: FOL, Edit/FOL Utility
Explanation: The FOL parsing facility checks the validity of RMS blocks
before deallocating them, and returns this error if a bad control block is
found.
User Action: Ascertain that the RMS control blocks passed to the
FDL$RELEASE routine are in the same state as when they were created
by the FDL$P ARSE routine.
INVBLKHDR,

invalid block header encountered in save set

Facility: BACKUP, Backup Utility
Explanation: An incorrect value occurred in the block header of a save set
block. Data in the save set is corrupted.
User Action: None. Save set data is lost.
INVBLKSIZE, invalid block size in save set
Facility: BACKUP, Backup Utility
Explanation: An incorrect value occurred in the block size field of a save set
block. Data in the save set is corrupted.
User Action: None. Save set data is lost.
INVBLKTYP,

invalid block type in specified block

Facility: SDA, System Dump Analyzer
Explanation: SDA is unable to identify the block type of a particular block.
The invalid block type message usually occurs when the SDA command
FORMAT tries to identify a block type using a byte offset.
User Action: None.
INVBLOCK,

internal job controller error; invalid use of the block number
1

Facility: JBC, Job Controller
Explanation: This message indicates a logic error in the job controller.
User Action: None.

2-279

Messages

INVBTIMSP,

invalid /BEGINNING time specification

Facility: MONITOR, Monitor Utility
Explanation: The value of the /BEGINNING qualifier is specified incorrectly.
You must specify the time as an absolute time, plus or minus a delta time.
You can omit either the absolute or the delta time; however, the delta time
must always be preceded by the plus or minus sign. Whenever you use a
plus sign, enclose the entire time specification in double quotes. See the VMS
DCL Dictionary for more information on specifying time values.
User Action: Reenter the MONITOR request with a correct value for the
/BEGINNING qualifier.

INVBUFDELETE,

cannot delete a permanent buffer

Facility: VAXTPU, VAX Text Processing Utility
Explanation: You attempted to delete a buffer that is set as a permanent
buffer.
User Action: None.

INVCALL,

invalid CALL nesting structure or data inconsistency detected

Facility: CU, Command Language Interpreter (DCL)
Explanation: There are three possible causes for these error messages:

•

You mismatched or unpaired SUBROUTINE and ENDSUBROUTINE
commands in a command procedure.

•

You used the GOSUB command with a label defined with the
SUBROUTINE command.

•

You entered the command CALL, SUBROUTINE, or ENDROUTINE at an
interactive (DCL) level.

User Action: Correct the command procedure and reexecute the program.

INVCCFIL,

invalid console carrier image file

Facility: MOM, Maintenance Operation Module
Explanation: The image that is being accessed to downline load the console
carrier code is unsupported.
User Action: Use a supported image type to downline load the console
carrier code.

INVCHA, invalid character
Facility: LIB, Library Facility
Explanation: A character is unable to be translated when converting either
from ASCII to EBCDIC or from EBCDIC to ASCII.
User Action: Ensure that translatable characters are used.

2-280

Messages

INVCHAN,

invalid ACP channel number

'name' is an invalid characteristic name

Facility: QUEMAN, Queue Manager
Explanation: The characteristic name specified is not syntactically valid.
After logical name translation, the characteristic name must be a character
string in the range of 1 to 31 characters. The character string must consist of
alphanumeric characters, dollar signs, or underscore (-) characters.
User Action: Correctly specify the characteristic name.
INVCHANUM,

'number' is an invalid characteristic number

Facility: QUEMAN, Queue Manager
Explanation: The specified characteristic number is syntactically invalid.
User Action: Correct the error and reenter the command.
INVCHAR, invalid character
Facility: PATCH, Patch Utility and DEBUG, VMS Debugger
Explanation: The command contained an invalid character.
User Action: Correct the character and reenter the command.
INVCHAR, invalid character encountered in position 'position'. It is ignored
Facility: CDU, Command Definition Utility
Explanation: CDU encountered an invalid character while reading from a
CLD file. The invalid character is ignored.
User Action: Edit the CLD file such that there are no invalid characters.

2-281

Messages

INVCHDABS,

invalid command in /ABSOLUTE context

Facility: PATCH, Patch Utility
Explanation: The command entered is invalid when patching a file in
absolute context. Use of symbol names, patch area, or ECOs is invalid
when invoking PATCH with the /ABSOLUTE qualifier.
User Action: Enter a valid command. If you are patching an image, invoke
the Patch Utility without the /ABSOLUTE qualifier.
INVCJFIOD,

invalid IO database structure (journaling)

invalid class in descriptor

Facility: LIB, Library Facility
Explanation: An unsupported class of descriptor is specified.
User Action: Retry the operation specifying a supported class of descriptor.
INVCLADTY,

invalid class data type combination in descriptor

Facility: LIB, Library Facility
Explanation: An unsupported class and data type combination is specified.
User Action: Ensure that both the class and data type specified are
supported.
INVCLIFLAG, invalid CLI flag 'flag-name' encountered
Facility: CDU, Command Definition Utility
Explanation: CDU encountered an invalid CU flag name while reading from
a CLD file.
User Action: Edit the CLD file so that all CLI flag names are valid.
INVCLSNM,

class-name 'class-name' is invalid or not uniquely identified

Facility: MONITOR, Monitor Utility
Explanation: The specified class name is not a valid MONITOR class. This
message can result from specifying a class name with too few characters to
uniquely identify it.
User Action: Check the list of valid MONITOR classes by entering the DCL
command, HELP MONITOR parameters. Reenter the MONITOR command
requesting only valid classes.

2-282

Messages

INVCMD,

invalid command

Facility: Shared by several facilities
Explanation: Your command is invalid, either because the command parser
cannot recognize the command, or because of incorrect syntax.
User Action: If necessary, refer to the appropriate documentation, then
reenter your command correctly.

INVCMD,

unrecognized command

Facility: NCP, Network Control Program
Explanation: The specified verb is invalid.
User Action: Check the input command for corrections and reenter the
command.

INVCOL,

invalid column

Facility: SMG, Screen Management Facility
Explanation: An invalid column number is specified. It is either less than 0
or larger than the number of columns in the virtual display.
User Action: Specify a valid column. Columns are numbered beginning
with 1.

INVCOLARG,

unknown color specified

Facility: SMG, Screen Management Facility
Explanation: An attempt is made to change the characteristics of the
terminal, changing its background color to a value that is not valid.
User Action: Check the symbolic name for the background color desired.
Specify it correctly.

INVCONT, invalid line continuation
Facility: INPSMB, Input Symbiont
Explanation: In a batch job entered from a card reader, a continued line is
followed by a line beginning with a dollar sign.
User Action: Correct the error and reenter the job.

INVCPUID,

invalid CPU identification

Facility: MONITOR, Monitor Utility
Explanation: The CPU identification specified with the /CPU qualifier was
invalid. Valid CPU identifications are integers 0-31.
User Action: Correct the CPU identification specification and reenter the
MONITOR command.

2-283

Messages

INVCTX,

invalid context block

Facility: DCX, Disk Compression Utility
Explanation: A DCX procedure is called with a context variable that is invalid
or with an invalid or corrupted context area. This problem may be caused by
failure to call the appropriate routine to initialize the context variable or by an
application program error.
User Action: Correct the application program.
INVCVT,

invalid conversion

Facility: LIB, Library Facility
Explanation: The source value is negative and the destination data type is
unsigned.
User Action: Ensure that the source value is positive and the destination data
type is signed.
INVDATA,

invalid data presented for expansion or bounded compression

Facility: DCX, Disk Compression Utility
Explanation: Two possible causes exist:
•

DCX$COMPRESS_DATA is called to compress a data record that is not
presented to DCX$ANALYZE_DATA when a bounded compression
function had been requested.

•

DCX$EXPAND_OATA is called to expand a compressed data record that
is truncated or corrupted in some fashion.

User Action: Correct the application program.
INVDATIM,

invalid date/time in statement 'number'

Facility: FDL, Create/FOL Utility
Explanation: An invalid date or time is included in the specified statement.
User Action: Correct the invalid date or time in the specified statement in the
FDL file.
INVDATIM,

invalid date/time in statement 'xxx'

Facility: FDL, Edit/FDL Utility
Explanation: The date or time specified to the FOL parser is incorrectly
formed.
User Action: Verify that the syntax of the date and time is correct. The valid
format is that of the SYS$BINTIM system service.
INVDEF,

'directory spec' does not exist

Facility: CU, Command Language Interpreter (DCL)
Explanation: You set your default to a nonexistent directory using the SET
DEFAULT command and then entered the SHOW DEFAULT command.
User Action: Set default to a valid directory and reenter the SET DEFAULT
command.

2-284

Messages

INVDEFATT,

invalid key-definition attributes

Facility: SMG, Screen Management Facility
Explanation: When a key is defined, attributes such as NOECHO may be
specified with the definition. An attempt is made to specify an unknown
attribute.
User Action: Check the list of valid attributes and correct your program.
INVDEFINE,

invalid DEFINE statement

Facility: CDU, Command Definition Utility
Explanation: CDU encountered an invalid DEFINE statement in a CLD file.
Valid keywords for the DEFINE statement are: VERB, SYNTAX, and TYPE.
User Action: Edit the CLD file so that the DEFINE commands contain proper
syntax.
INVDELIM,

invalid delimiter

Facility: STR, String Manipulation Facility
Explanation: The delimiter string passed to STR$ELEMENT is longer than a
single character.
User Action: Examine the delim_dec argument and make corrections.
INVDESC , invalid descriptor
Facility: PPL, Parallel Processing Facility
Explanation: The descriptor is invalid.
User Action: Recode your program to correct the descriptor.
INVDESC,

invalid string descriptor

Facility: DEBUG, VMS Debugger
Explanation: This message indicates an internal debugger error.
User Action: Submit a Software Performance Report.
INVDEV,

device is invalid for requested operation

Facility: SET, SET Facility
Explanation: The device type that is specified for the operation is not allowed
in the particular operation. For example, the user enters the command SET
DEVICE/SERVED CSAl to serve the console floppy which is not allowed.
User Action: Make sure that the device meets all of the requirements for the
operation.
INVDEV,

device name too long to add trailing ":"

Facility: AUTHORIZE, Authorize Utility
Explanation: You specified a device name with more than 15 characters.
User Action: Limit the device name to 15 characters.

2-285

Messages

INVDEVICE,

invalid device 'xxxxxx' specified

Facility: SYSMAN, Cluster System Management Utility
Explanation: The device indicated does not exist on the target system. If
'xxxxxx' is a logical name, then the translation of that logical name is not a
valid device on the target system.
User Action: Specify a valid device.

INVDEVICE, invalid device 'device-name'
Facility: VERIFY, Verify Utility
Explanation: An invalid device is specified in the command.
User Action: Reenter the command specifying a valid device. The
specification must reference a disk device and must not contain any file
specification components other than a device name.

INVDEVTYP,

invalid backup device type 'filespec'

Facility: BACKUP, Backup Utility
Explanation: The specified device must be a disk or tape device.
User Action: Reenter the command.

INVDIR,

invalid directive

Facility: SMG, Screen Management Facility
Explanation: The Termtable compiler accepts only a few FAQ directives. It
encountered one that it does not process.
User Action: Check your terminal definition. Make sure that you use only
valid FAQ directives.

INVDIRNAM,

invalid directory name: 'directory-name'

Facility: DEBUG, VMS Debugger
Explanation: The directory name 'directory-name' given in a SET SOURCE
command is not valid. Either the directory syntax is incorrect or the directory
does not exist.
User Action: Ensure that the directory exists and that the syntax is correct.

INVDIS_ID, invalid display-id
Facility: SMG, Screen Management Facility
Explanation: An invalid display identifier is specified.
User Action: Make sure you are passing the display identifier by reference,
not by value. Ensure that the display id is previously set up by a call to
SMG$CREATE_VIRTUAL_DISPLAY.

2-286

Messages

INVDPT,

invalid driver image-DPT$_TYPE, VBN 2 .NEQ. DYN$C_DPT

Facility: SYSGEN, System Generation Utility
Explanation: The driver image file specified in a SYSGEN command LOAD,
RELOAD, or CONNECT did not pass a basic validity check. This error can
be caused by one of the following conditions:

•

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

•

Not linking the driver as an executable image based at zero

•

Having PSECT statements in the driver program

•

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

User Action: Correct the driver code and reenter the command.

INVDPTINI,

invalid driver prologue init table value

Facility: SYSGEN, System Generation Utility
Explanation: One of the following conditions exists:

•

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

•

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

User Action: Correct the DPT_STORE macro in the driver prologue table.

INVDSTQUE, invalid destination queue
Facility: JBC, Job Controller
Explanation: The destination queue name specified is not syntactically
valid. After logical name translation, the destination queue name must be
a character string in the range of 1 to 31 characters. The character string
must consist of alphanumeric characters, dollar signs, and underscore (-)
characters.
User Action: Correctly specify the destination queue.

INVDSTREC,

invalid DST record

Facility: PATCH, Patch Utility and DEBUG, VMS Debugger
Explanation: An invalid Debug Symbol Table record is encountered. This
can be caused by a DEPOSIT to a random location or it may be a compiler
error.
User Action: Submit a Software Performance Report unless the applications
program or a DEPOSIT command has altered a Debug Symbol Table record.

2-287

Messages

INVDSTREC,

unimplemented delta-PC command in symbol table

Facility: TRACE, Traceback Facility
Explanation: A language processor has created a PC-to-line-number record
that the traceback facility has not implemented. The symbol table information
is either incorrect or is not known to the traceback facility.
User Action: Submit a Software Performance Report.
INVDTYDSC,

invalid data type in descriptor

Facility: LIB, Library Facility
Explanation: An unsupported data type is specified.
User Action: Retry the operation specifying a supported data type.
INVELEID , invalid element ID
Facility: PPL, Parallel Processing Facility
Explanation: The specified element ID is not valid.
User Action: Examine the program code. Some modification of the element
ID occurred.
INVELENAM,

invalid element name

Facility: PPL, Parallel Processing Facility
Explanation: An invalid character string is detected.
User Action: Specify a valid character string.
INVELETYP , invalid element type for requested operation
Facility: PPL, Parallel Processing Facility
Explanation: You specified an element type that cannot be used by the called
routine.
User Action: Recode the program to pass a valid element type.
INVETIMSP,

invalid /ENDING time specification

Facility: MONITOR, Monitor Utility
Explanation: The value of the /ENDING qualifier is specified incorrectly.
You must specify the time as an absolute time plus or minus a delta time.
You can omit either the absolute or the delta time; however, the delta time
must always be preceded by the plus or minus sign. Whenever you use a
plus sign, enclose the entire time specification in double quotes. See the VMS
DCL Dictionary for more information on specifying time values.
User Action: Reenter the MONITOR request with a correct value for the
/ENDING qualifier.
INVEVE,

invalid event range

Facility: NCP, Network Control Program
Explanation: The range of event types is invalid.
User Action: Reenter a valid event list.

2-288

Messages

INVEXCEPTN,

exception while above ASTDEL or on interrupt stack

termination handler control block list is corrupted

Facility: SYSTEM, VMS System Services
Explanation: The list of exit handler control blocks is in an inconsistent state,
either because the same exit handler is declared more than once or because
user code has minpulated one of the list pointers.
User Action: The program is in error. Change the source code that is
incorrectly manipulating the termination handler control block list.
INVEXP,

invalid expression

Facility: SMG, Screen Management Facility
Explanation: The Termtable compiler encountered an invalid arithmetic
expression.
User Action: Check your definition. Make sure that you have used only
valid operators and operands in your expressions.
INVEXTBACK,

file ('file-id') 'filename' invalid extension file header back link

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility has found that the back link in an extension
file header for the specified file does not point to the primary file header.
User Action: None. The back link is changed to point to the primary file
header.
INVEXTFID,

file ('file-id') 'filename' invalid extension file header forward link

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility has found that the forward link in a file
header to the next extension file header does not point to a valid file header.
User Action: Examine and delete the file. If possible, reconstruct the file
from backup media.

2-289

Messages

INVEXTHDR,

file ('file-id

1
)

filename invalid extension file header sequence
1

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility has found that the sequence numbers in
the extension file headers for the specified file are not correct. The sequence
number should increase by one in each extension file header.
User Action: The link that points to the erroneous extension file header is
cleared. Part of the file cannot be accessed by the operating system. You
should delete the file and, if possible, reconstruct it from backup media.

INVFAOP ARAM,

FAO parameter integer must be string or integer

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The FAO built-in procedure allows only string and integer
arguments.
User Action: Specify string and integer arguments only to the FAO built-in
procedure.

INVFCBDESC,

descriptor in $FCB for 1address 1 improperly initialized

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

INVFCO,

invalid file contents, filename

Facility: NCP, Network Control Program
Explanation: Your command could not access the file, because the file's
contents are invalid. An accompanying VMS RMS message should identify
the reason why the file contents are invalid.
User Action: Take corrective action based on the accompanying VMS RMS
message.

INVFID,

invalid file id in save set-cannot restore /IMAGE

Facility: BACKUP, Backup Utility
Explanation: An attempt is made to restore a file with a zero file
identification in /IMAGE mode. This may occur if the save set is written
by a non-VMS system.
User Action: Use a non-/IMAGE mode to restore the file.

INVFILEXT,

invalid file extension linkage in filespec

Facility: BACKUP, Backup Utility
Explanation: The specified save set file has an invalid pointer to a following
segment of the file. The remainder of the file is not accessible.
User Action: Attempt to recover data by beginning a restore operation with
the first unprocessed file segment.

2-290

Messages

INVFILSPE,

boot file specification too long

Facility: VAXCLUSTER, VAXcluster Facility
Explanation: You specified an invalid load assist parameter with the system
root specification.
User Action: Shorten the file specification for the system root.

INVFILSPE,

input or output file specification too long-shorten

Facility: CLI, Command Language Interpreter (DCL)
Explanation: A file specification is invalid.
User Action: Reenter the command, specifying a valid file specification.

INVFILSPE,

invalid file specification

Facility: LIB, Library Facility
Explanation: An invalid file specification is specified in a CREATE
/DIRECTORY, SET PROTECTION, RENAME, or UNLOCK command.
User Action: Refer to the VMS DCL Dictionary and reenter the command.

INVFILSPE,

invalid file specification 'filespec'

Facility: PRINT, PRINT Command and SUBMIT, SUBMIT Command
Explanation: The specified file specification is invalid. Files submitted to a
batch or print job must be disk files.
User Action: Correct the error and reenter the command.

INVFIXDST, invalid DST fixup records in image 'image-name', symbol references
to shareable images may be erroneous
Facility: DEBUG, VMS Debugger
Explanation: While attempting to read the Debug Symbol Table (DST) in the
specified image, the debugger found errors in the DST address fixup records.
These records are used to adjust for the base addresses of shareable images.
This means that any symbols in this image that point to addresses in other
(shareable) images are most likely incorrect. Symbols that refer to addresses
in this image are correct unless this is also a shareable image.
User Action: Relink the image and, if the error is reproducible, submit a
Software Performance Report explaining how the image file is created.

INVFLUSHSP,

invalid /FLUSH-INTERVAL specification

Facility: MONITOR, Monitor Utility
Explanation: The value of /FLUSH_INTERVAL must be an unsigned
contiguous string of decimal digits forming a value in the range of 1 to
9,999,999, inclusive.
User Action: Reenter the MONITOR request and specify a valid value for
/FLUSH__INTERVAL.

2-291

Messages

INVFORNAM,

invalid form name

Facility: JBC, Job Controller
Explanation: The form name specified is not syntactically valid. After logical
name translation, the form name must be a character string whose length
is in the range of 1 to 31 characters. The character string must consist of
alphanumeric characters, dollar signs, and underscore ( _) characters.
User Action: Correctly specify the form name.

INVFORNAM,

'name' is an invalid form name

Facility: QUEMAN, Queue Manager
Explanation: The form name specified is not syntactically valid. After logical
name translation, the form name must be a character string whose length
is in the range of 1 to 31 characters. The character string must consist of
alphanumeric characters, dollar signs, and underscore ( _) characters.
User Action: Correctly specify the form name.

INVFORNUM,

'number' is an invalid form number

Facility: QUEMAN, Queue Manager
Explanation: The specified form number is syntactically invalid.
User Action: Correct the error and reenter the command.

INVFUNC,

invalid function (valid choices are: SAVE, RESTORE, TEST,
COMPARE)

Facility: JBCUPGRAD, Queue Upgrade Utility
Explanation: An invalid function was requested for the queue upgrade utility.
User Action: Enter one of the valid function choices.

INVFUNCOD,

invalid function code

Facility: JBC, Job Controller
Explanation: The $GETQUI, $SNDACC, $SNDJBC, or $SNDSMB function
code is invalid.
User Action: Identify and correct the incorrect function code.

INVGOSUB,

invalid use of the GOSUB command

Facility: CU, Command Language Interpreter (DCL)
Explanation: You entered the GOSUB command in an environment other
than a command procedure. This command is invalid in interactive mode.
User Action: Use the GOSUB command only in command procedures.

INVHOMBLK,

'device-name' has invalid home block

Facility: BACKUP, Backup Utility
Explanation: The specified volume has an invalid Files-11 home block.
User Action: Repair the volume with the Verify Utility.

2-292

Messages

INVIDE,

invalid identification, 'component-id'

Facility: NCP, Network Control Program
Explanation: The format of a component identifier is incorrect, or the
KNOWN component keyword is used where it is not valid. The 'componentid' will identify the invalid identification.
User Action: Check the syntax rules for component identifiers and reenter
your command with the correct syntax.
INVIFNEST,

invalid IF-THEN-ELSE nesting structure or data inconsistency

Facility: CLI, Command Language Interpreter (DCL)
Explanation: An IF-THEN-ELSE statement is incorrectly structured.
User Action: Modify your command procedure using the correct IF-THENELSE structure. Check for inconsistent data types.
INVIMGHDR,

inconsistent debug and symbol data in image header

Facility: PATCH, Patch Utility
Explanation: The image header inconsistently describes the symbol
information causing the absence of symbol information at PATCH time.
User Action: Relink the image. If the problem persists, submit a Software
Performance Report.
INVINPFIL,

/INPUT file is not a valid MONITOR recording file

Facility: MONITOR, Monitor Utility
Explanation: The file specified with the /INPUT qualifier is not a MONITOR
recording file. When MONITOR creates a recording file, identification
information is stored in the header record; this information is then verified
when the file is used for input. The file specified on this MONITOR request
failed the verification.
User Action: Reenter the MONITOR request, specifying a valid MONITOR
recording file with the /INPUT qualifier.
INVINPUT,

invalid input format in file 'filename'

Facility: DSR, DIGITAL Standard Runoff
Explanation: The format of the input file is incorrect.
User Action: Correct the format of the input file.
INVINTSP,

invalid /INTERVAL specification

Facility: MONITOR, Monitor Utility
Explanation: The /INTERVAL qualifier value must be an unsigned
contiguous string of decimal digits forming a value in the range of 1 to
9,999,999 inclusive.
User Action: Reenter the MONITOR request, specifying a valid /INTERVAL
qualifier value.

2-293

Messages

INVIOCODE,

invalid operation code passed to an I/O operation

Facility: VAXTPU, VAX Text Processing Utility
Explanation: An invalid request is passed to enter the file operation routine
or the terminal input routine provided by VAXTPU.
User Action: If you are using the callable interface, correct your program.
If you are not using the callable interface, a software error has occurred. In
such a case, please submit a Software Performance Report describing the
conditions that lead to the error.

INVITEM,

invalid item code or list

Facility: DCX, Disk Compression Utility
Explanation: DCX$ANALYZE_INIT is called with either an incorrect
number of arguments (the number must be odd) or an unknown item code
argument.
User Action: Correct the application program.

INVITEM,

invalid item 'item-name' encountered. Some text will be skipped

Facility: CDU, Command Definition Utility
Explanation: CDU encountered an unexpected item while reading from a
CLD file. The unexpected item is ignored.
User Action: Make sure that all commands in the CLD file contain correct
syntax.

INVITEMCODE,

invalid item code specified in list

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

INVITEMNM,

/ITEM name 'item-name' is invalid or not uniquely identified

Facility: MONITOR, Monitor Utility
Explanation: The specified item name is not defined for the class with which
it is specified. This message can result from specifying an item name with too
few characters to uniquely identify it.
User Action: Check the list of items defined for the requested class by
entering: HELP MONITOR /ITEM. Reenter the MONITOR command
requesting only valid items.

INVITMCOD,

invalid item code, item code= 'item code (hex)'

Facility: PSM, Print Symbiont
Explanation: An invalid item code is detected.
User Action: Specify a valid item code.

2-294

Messages

INVITMCOD,

invalid item code or option code

Facility: JBC, Job Controller
Explanation: The $GETQUI or $SNDJBC item list contains an invalid item
code, or the $SNDSMB or $SNDACC option list contains an invalid option
code.
User Action: Correct the invalid item code or option code.
INVKBD_ID,

invalid keyboard-id

Facility: SMG, Screen Management Facility
Explanation: An invalid keyboard id is passed.
User Action: Make sure you are passing the keyboard id by reference,
not by value. Ensure that the keyboard id is previously set up by a call to
SMG$CREATE_VIRTUAL_KEYBOARD.
INVKEY,

invalid key

Facility: LBR, Librarian Subroutine Package
Explanation: This error message is generated by the Librarian routines.
The specified key is either of zero length or it is greater than the maximum
allowable length.
User Action: Either change the module name or change the name length
limit of the library.
INVKEY,

unrecognized keyword

Facility: NCP, Network Control Program
Explanation: NCP could not recognize a keyword in the command string.
This error is returned when the keyword is entered in response to a prompt.
User Action: Reenter the requested information.
INVKEYCHAR,

key not inserted; 'ASCII-character' (%X'hexadecimal-byte') is not
a valid key character

Facility: LIBRAR, LIBRARY Command
Explanation: The flagged character is not permitted in a HELP key. If the
HELP key is a level one key (topic), the module will not be inserted into the
HELP library.
User Action: Edit the module in the HELP file to remove the invalid
character from the key.
INVKEYNAM,

invalid key name

Facility: SMG, Screen Management Facility
Explanation: The specified key name is less than 1 character or more than 31
characters.
User Action: Choose a key name with 1 to 31 characters.

2-295

Messages

INVKTB_ID,

invalid key-table-id

Facility: SMG, Screen Management Facility
Explanation: An invalid key table id is passed.
User Action: Make sure you are passing the key table id by reference,
not by value. Ensure that the key table id is previously set up by a call to
SMG$CREATE_KEY_TABLE.
INVLDADR, invalid virtual address
Facility: SDA, System Dump Analyzer
Explanation: The virtual address lies outside the boundries of the virtual
addresses mapped by the system page table (SPT).
User Action: Reenter the command, specifying a valid virtual address.
INVLDRESP,

invalid operator response

Facility: MOUNT, Mount Utility
Explanation: The operator responded to a request with an invalid reply.
User Action: None. The request is automatically reentered.
INVLOCKID,

invalid lock id

invalid log file specification

Facility: CU, Command Language Interpreter (DCL)
Explanation: In a SUBMIT command, the log file specification is invalid.
This message is issued with an accompanying message providing more
information.
User Action: Refer to the VMS DCL Dictionary and reenter the command
specifying a valid file specification.
INVLOGFIL,

invalid log file specification

Facility: INPSMB, Input Symbiont, QUEMAN, Queue Manager, and
SUBMIT, SUBMIT Command
Explanation: The specified log file specification is syntactically invalid. The
accompanying message provides additional information.
User Action: Take corrective action based on the accompanying message.

2-296

Messages

INVLOGFIL, invalid log file specification
Facility: Shared by several facilities
Explanation: The batch log file specification supplied with the /LOG_FILE
qualifier is invalid. The file specification must reference a disk file and must
not contain a node name or wildcards.
User Action: Respecify the batch log file specification using the correct
syntax.
INVLOGIN,

Facility: SYSTEM, VMS System Services
Explanation: An attempt is made to initiate a DECnet logical link connection.
User Action: The access control string specified is incorrect. If default access
control is used, notify the system manager that the DECnet configuration
database needs to be updated.
This error can be returned if the specified access control string is not
recognized (for example, no record in the UAF), or is too long, or contained
invalid characters.
INVMAP,

invalid map

Facility: DCX, Disk Compression Utility
Explanation: A DCX procedure is called with an incorrectly formed map
argument or with an invalid context area.
User Action: Correct the application program.
INVMAR,

right margin must be greater than left

Facility: DEBUG, VMS Debugger
Explanation: You specified a right margin that is less than the left margin in
a SET MARGIN command. The right margin must be greater than the left
margin.
User Action: Specify a valid margin range and reenter the command.
INVMAXLEN,

invalid maximum length (greater than 512)

Facility: SMG, Screen Management Facility
Explanation: The maximum length specified for an input string is too long.
User Action: Correct your program so that it requests an input string of 512
characters or less.
INVMODE,

invalid mode parameter

Facility: DTK, DECtalk Facility
Explanation: The value of the mode argument is not in the correct range.
User Action: Examine the argument. Determine which value is out of range
and correct your program.

2-297

Messages

INVMSG,

invalid mailbox message received

Facility: JBC, Job Controller
Explanation: The job controller received an invalid mailbox message. This
message indicates a logic error in the system or in the job controller interface
of a user-written symbiont.
User Action: Identify the cause of the problem.

INVMSGBUF, invalid message buffer
Facility: JBC, Job Controller
Explanation: The $SNDSMB or $SNDACC message buffer is invalid because
it is not long enough to contain all required fields or an option extends
beyond the end of the message buffer.
User Action: Correct the message buffer format and retry the system service
call.

INVNAM, invalid NAM block
Facility: LBR, Librarian Subroutine Package
Explanation: This error message is generated by the Librarian routines. The
NAM block passed to LBR$INl_CONTROL is invalid.
User Action: Correct the NAM block before calling the routine.

INVNBDS,

invalid Numeric Byte Data String

Facility: LIB, Library Facility
Explanation: The string of bytes specified as a NBDS is not a NBDS.
Numeric Byte Data Strings are explained in the LIB$CVT_DX_DX routine
documentation in the VMS RTL Library (LIB$) Manual.
User Action: Check the NBDS descriptor against LIB$CVT_DX_DX
documentation.

INVNUMBER,

invalid numeric string

Facility: PATCH, Patch Utility and DEBUG, VMS Debugger
Explanation: You specified a numeric data string that is invalid in the current
context.
User Action: Specify the value in another numeric format or set the language
to one that accepts this type of numeric string.

INVNUMCHI , invalid number of children, must be positive
Facility: PPL, Parallel Processing Facility
Explanation: You tried to create a number less than 1.
User Action: Recode the program to request a value greater than or equal
to 1.

2-298

Messages

INVNUMSRC, invalid number of source files
Facility: DEBUG, VMS Debugger
Explanation: An invalid number of source files is specified with the SET
MAX_SOURCE_FILES command. The number of source files that the
debugger keeps open simultaneously must be in the range of 1 through 20.
User Action: Reenter the command specifying a valid number within the
range of 1 through 20.
INVNUMSTR,

invalid numeric string

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The specified string can not be converted to a number.
User Action: Use a string that correctly represents a number.
INVOPCODE,

opcode in delayed work queue is invalid

Facility: VAXTPU, VAX Text Processing Utility
Explanation: An internal VAXTPU failure occurred.
User Action: Submit a Software Performance Report.
INVOPER, invalid operation specified
Facility: LIB, Library Facility
Explanation: The operation code is out of range or invalid
User Action: Examine the operation code. Replace it with a valid operation
code.
INVOPEZON, invalid operation for zone
Facility: LIB, Library Facility
Explanation: The item code is invalid for the specified zone. This message is
also returned for an invalid use of an unspecified user zone action routine.
User Action: Specify a valid item code.
INVOPR,

unrecognized operator in expression

Facility: PATCH, Patch Utility and DEBUG, VMS Debugger
Explanation: The expression contained a character in place of a valid
operator that PATCH or DEBUG does not recognize.
User Action: Reenter the command with a valid expression.
INVOPRND,

unable to resolve operand 'xx'

Facility: PATCH, Patch Utility
Explanation: You specified an operand that PATCH does not recognize.
Operands such as 4(RO) must be preceded by BA, for example, BA4(RO).
User Action: Retry the operation specifying a valid operand.

2-299

Messages

INVOPTION,

non-supported flow control parameter received

Facility: DTR, DECnet Test Program Protocol
Explanation: This message indicates a DECnet test program protocol
incompatibility.
User Action: Run with a compatible version of DTRECV or equivalent.
INVOPTIONS,

to specify options, parameter 3 must be the word OPTIONS.

Facility: VMSINSTAL, Install Procedures
Explanation: If you are specifying VMSINSTAL options, the third parameter
to VMSINSTAL must be the word OPTIONS.
User Action: Restart VMSINSTAL, and specify the options in the correct
format.
INVOUTSPE,

invalid output file assignment

Facility: CLI, Command Language Interpreter (DCL)
Explanation: You specified an invalid or null file specification in defining
SYS$0UTPUT.
User Action: Reenter the command with a correct file specification.
INVOVERQUOTA,

invalid overdraft quota specified

Facility: SYSMAN, Cluster System Management Utility
Explanation: A DISKQUOTA ADD or MODIFY function specified an invalid
overdraft quota (nonnumeric, negative, or larger than 32 bits).
User Action: Respecify the command with a valid quota.
INVP AGARG,

height of 0 is not permitted

Facility: SMG, Screen Management Facility
Explanation: An attempt is made to change the characteristics of the
terminal, setting the height (page size) to 0.
User Action: Correct the code. A height of 0 is invalid.
INVPARAM,

parameter 'numbers', datatype 'type' illegal, expected 'type'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: A built-in procedure is invoked with an invalid data type as
one of its parameters.
User Action: Specify a valid data type.
INVP ARAM,

parameter value illegal (nonnumeric or too large)

Facility: SYSMAN, Cluster System Management Utility
Explanation: A PARAMETERS SET command specified an invalid value for
a parameter. The parameter is too large (for a numeric parameter) or contains
invalid numeric digits.
User Action: Supply a valid parameter value.

2-300

Messages

INVP ARFIL,

invalid parameter file

Facility: SYSGEN, System Generation Utility
Explanation: An error occurred accessing the file specified in a USE or
WRITE operation.
User Action: Check that the file is not protected against read or write access
and then reenter your command. If the error reoccurs, but the file can be read
or written by other utilities, submit a Software Performance Report. Include a
copy of the invalid parameter file with the SPR.
INVPARLEN,

invalid parameter length

Facility: JBC, Job Controller
Explanation: The buffer length specified for a $GETQUI or $SNDJBC item,
or the length of a string specified with a $SNDSMB option, is outside the
valid range for that item.
User Action: Specify a valid buffer length and retry the system service call.
INVP ARM,

parameter identifiers must be in the form Pn

Facility: CDU, Command Definition Utility
Explanation: CDU encountered a parameter definiton in which the parameter
being defined is not in the form Pn. All parameters must be in the form Pn.
User Action: Edit the CLD file so that all defined parameters are in the form
Pn.
INVP ARVAL,

invalid parameter value

Facility: JBC, Job Controller
Explanation: The parameter value specified for a $GETQUI or $SNDJBC
item, or a $SNDACC or $SNDSMB option, is outside the valid range for that
item.
User Action: Specify a valid value for the specified item and retry the system
service call.
INVPAS_ID,

invalid pasteboard-id

Facility: SMG, Screen Management Facility
Explanation: An invalid pasteboard identifier is specified.
User Action: Make sure that you are passing the pasteboard identifier
by reference, not by value. A reference to a 0 is valid, since 0 is a valid
pasteboard identifier. Make sure the pasteboard is previously set up by a
call to SMG$CREATE_PASTEBOARD and that the pasteboard has not been
deleted.
INVPASS,

invalid password 'password'

Facility: INPSMB, Input Symbiont
Explanation: The specified password is syntactically invalid.
User Action: Correct the error and reenter the job.

2-301

Messages

INVP ATH,

invalid path name started by 'string'

Facility: PATCH, Patch Utility
Explanation: This message indicates an incorrect use of path name rules.
User Action: Correct the path name according to path name rules and retry.
INVPERMQUOTA, invalid permanent quota specified

Facility: SYSMAN, Cluster System Management Utility
Explanation: A DISKQUOTA ADD or MODIFY function specified an invalid
permanent quota (nonnumeric, negative, or larger than 32 bits).
User Action: Respecify the command with a valid quota.
INVPGP,

invalid parameter grouping

Facility: NCP, Network Control Program
Explanation: The request contained multiple parameters that are in
incompatible groups. For example, the executor name and address cannot
be set together.
User Action: Divide the command into multiple commands, one command
for each parameter group.
INVPLACE,

placement must be GLOBAL, LOCAL, or POSITIONAL

Facility: CDU, Command Definition Utility
Explanation: An invalid keyword value is specified for the PLACEMENT
qualifier. Valid keyword values for the PLACEMENT qualifier are GLOBAL,
LOCAL, and POSITIONAL.
User Action: Edit the CLD file so that each PLACEMENT keyword value is
one of the following: GLOBAL, LOCAL, or POSITIONAL.
INVPRVNAM,

'privilege' is not a valid privilege

Facility: INSTALL, Install Utility
Explanation: An invalid privilege name is specified.
User Action: Correct the privilege name and reenter the command.
INVPTEFMT,

invalid page table entry format

2-302

Messages

INVPVA, invalid parameter value
Facility: NCP, Network Control Program
Explanation: The specified value for a parameter is invalid; for example, a
line identifier or a load address is incorrect.
User Action: Check the rules for specifying the parameter value and reenter
the command.
INVPWD,

invalid password

Facility: CAF, Cluster Authorization File Service
Explanation: A cluster password contains characters other than A-Z, 0-9, $,
hyphen, and underscore.
User Action: Reenter the command with a valid password.
INVPWDLEN,

invalid password length-password not changed

Facility: CAF, Cluster Authorization File Service
Explanation: A cluster password is null or has more than 31 characters.
User Action: Reenter the command with a valid password.
INVPWDLEN,

invalid password length-password not changed

Facility: SET, SET Facility
Explanation: A password is specified whose length is outside the range
established for valid passwords.
User Action: Make sure the password is the correct length and, if necessary,
change the password and reenter the command.
INVQUAL,

invalid qualifier

Facility: CLI, Command Language Interpreter (DCL)
Explanation: You entered an invalid qualifier for a DCL command.
User Action: Check your documentation for the command and reenter it
using the correct qualifier name.
INVQUAVAL,

value 'nn' invalid for /'qualifier' qualifier

Facility: BACKUP, Backup Utility
Explanation: The specified value is not valid for the specified qualifier.
User Action: Check the range of valid values for the qualifier and reenter the
command.
INVQUAVAL,

value 'value' invalid for qualifier 'qualifier'

Facility: ERF, Error Log Utility
Explanation: An invalid qualifier was specified.
User Action: Use the DCL HELP command or refer to the VMS DCL
Dictionary for the valid qualifier values. Then reenter your command.

2-303

Messages

INVQUENAM,

invalid queue name

Facility: JBC, Job Controller
Explanation: The queue name specified is not syntactically valid. After
logical name translation, the queue name must be a character string whose
length must be in the range of 1 to 31 characters. The character string
must consist of alphanumeric characters, dollar signs, and underscore (-)
characters.
User Action: Specify a syntactically valid queue name.
INVQUO,

quoted argument not allowed in current mode

Facility: PATCH, Patch Utility
Explanation: You attempted to enter an argument enclosed in quotation
marks or apostrophes when you were not in INSTRUCTION or ASCII mode.
User Action: Remove the quotation marks or apostrophes and retry the
operation. Or if you are entering instructions or ASCII data, indicate this in
the command.
INVRANGE,

field specification is out of bounds-check sign and size

Facility: CU, Command Language Interpreter (DCL)
Explanation: The offset and/or length arguments specify a location that is
out of the valid range of this operation.
User Action: Check the offset and length; also check the size of the item on
which you are operating.
INVRANGE,

invalid range enclosure specified

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The specified range encloses text in an invalid way.
User Action: Specify a range of text that consists of either complete lines or
a fragment of a single line.
INVRECFMT,

record format specified inconsistent with volume format

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility found that the format option on the
/RECORD_FORMAT qualifier is not valid for the volume against which it is
applied.
User Action: It is very seldom necessary to use a /RECORD_FORMAT
qualifier, since the defaults taken by EXCHANGE are usually correct. If it
is necessary to use a /RECORD_FORMAT qualifier, make sure it is on the
correct file specification. It is possible to put /RECORD_FORMAT on either
input or output specifications (or even on both), depending on the command.
INVRECORD, invalid record type in file 'filename'
Facility: DSR, DIGITAL Standard Runoff
Explanation: An invalid record type is encountered in the file.
User Action: Make sure that the file contains the correct record type.

2-304

Messages

INVRECSIZ,

invalid record size in save set

Facility: BACKUP, Backup Utility
Explanation: An incorrect value occurred in the record size field
(BRH$W_RSIZE) of a save set record. Data in the save set is corrupted.
User Action: None. Save set data is lost.
INVRECTYP,

invalid record type in save set

Facility: BACKUP, Backup Utility
Explanation: An incorrect value occurred in the record type field of a save
set record. Data in the save set is corrupted.
User Action: None. Save set data is lost.
INVREPTYP,

invalid report type

Facility: ERF, Error Log Utility
Explanation: An internal consistency error was encountered.
User Action: Submit a Software Performance Report.
INVREQ, invalid startup parameter
Facility: START, System Startup Driver
Explanation: The startup driver is executed with an invalid first parameter.
User Action: If the error occurs during a system boot, check the value of
the SYSGEN parameter STARTUP_Pl. If errors occur after a @STARTUP
command procedure, verify that the first parameter is FULL, MINIMUM,
UPGRADE, or the name of the system component to restart.
INVREQCOD,

not a valid request code

Facility: SMG, Screen Management Facility
Explanation: Data is requested from Termtable through request codes that
are available as symbolic names. The code you have specified is invalid.
User Action: Check the spelling of the symbolic name you are using.
INVREQPARM,

line 'line-number': All required parameters must precede optional
ones

Facility: CDU, Command Definition Utility
Explanation: CDU encountered a REQUIRED parameter specification after an
OPTIONAL parameter is specified. All REQUIRED parameter specifications
must precede OPTIONAL parameter specifications.
INVREQTYP,

invalid request type

Facility: CU, Command Language Interpreter (DCL)
Explanation: This message is associated with an internal status code returned
from the command interpreter result parse routine; it indicates a request to
perform an unimplemented function.
User Action: Submit a Software Performance Report.

2-305

Messages

INVRFA,

invalid RFA

Facility: LBR, Librarian Subroutine Package
Explanation: This error message is generated by the Librarian routines. The
specified RFA is invalid.
User Action: Correct the RFA before calling the routine.
INVRFM,

invalid record format-file must be FIXED length

Facility: CAP, Cluster Authorization File Service
Explanation: The file SYS$SYSTEM:CLUSTER-AUTHORIZE.DAT has an
invalid format.
User Action: Delete and re-create the file on all cluster members with a
CONFIGURATION SET CLUSTER-AUTHORIZATION command at the
SYSMAN> prompt.
INVRFM,

invalid record format for record I/0-file not opened

Facility: CLI, Command Language Interpreter (DCL)
Explanation: This message is returned by the DCL command OPEN if the
file you are trying to open has a record format that is incompatible with
record I/O.
User Action: You cannot use DCL to read or write to this file.
INVROUT,

invalid routine specified in command tables-check .CLD file

Facility: CLI, Command Language Interpreter (DCL)
Explanation: A user-defined command attempted to invoke a routine that
DCL could not find.
User Action: Correct the command definition file.
INVROUT,

line 'line-number': A ROUTINE clause is only valid when generating
an object file

Facility: CDU, Command Definition Utility
Explanation: CDU encountered a ROUTINE clause while not generating an
object file. The ROUTINE clause is only valid when object file generation is
requested.
User Action: Edit the CLD file to remove the ROUTINE clause or specify the
/OBJECT qualifier in the SET COMMAND.
INVROW,

invalid row

Facility: SMG, Screen Management Facility
Explanation: An invalid row number is specified. It is either less than 0 or
larger than the number of rows in the virtual display.
User Action: Specify a valid row number. Rows are numbered beginning
with 1.

2-306

Messages

INVRSP,

invalid management response

Facility: NCP, Network Control Program
Explanation: Either NCP could not recognize the form of the response from
the network management listener (NML) or the response is inappropriate.
User Action: Submit a Software Performance Report.
INVRSP,

invalid response

Facility: AUTHORIZE, Authorize Utility
Explanation: Your response is invalid.
User Action: Respond to the "Do you ... " message that follows this
message.
INVRSPID, RSPID not valid
Facility: BUGCHECK, System Bugcheck
Explanation: The VMS software detected an irrecoverable, inconsistent
condition. After all of physical memory is written to a system dump file, the
system will automatically reboot if the BUGREBOOT system parameter is set
to 1.
User Action: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error, and that includes a BACKUP save set
containing the system dump file and the error log file active at the time of the
error. (Use the /IGNORE=NOBACKUP qualifier on the BACKUP command
that produces the save set included with the SPR.)
INVSCRPOS,

invalid screen position

Facility: LIB, Library Facility
Explanation: Zero is specified for either the line number or the column
number.
User Action: Do not specify zero for either the line number or the column
number.
INVSEMINI,

invalid semaphore initial value, cannot exceed its maximum value

Facility: PPL, Parallel Processing Facility
Explanation: A semaphore initial value must be less than or equal to its
maximum value.
User Action: Lower the specified initial value. Check the values of the
parameters semaphore__maximum and semaphore_initial, and adjust the
incorrect value accordingly.
INVSEMMAX , invalid semaphore maximum value, must be positive
Facility: PPL, Parallel Processing Facility
Explanation: A semaphore's maximum value must be positive.
User Action: Change the specified maximum value to a positive value.

2-307

Messages

INVSMG,

invalid message format

Facility: NCP, Network Control Program
Explanation: The network management message is too long or too short (for
example, it may contain too much data or not enough data), or a field is not
correctly formatted for the data expected.
User Action: Submit a Software Performance Report; include the command
that caused this error.
INVSRCLIN,

invalid source line range

Facility: DEBUG, VMS Debugger
Explanation: An invalid source line range is entered with the TYPE
command. The first line number of the range must be nonnegative and
less than or equal to the second number in the range.
User Action: Reenter the command specifying a valid line number range.
INVSTANAM,

invalid state name

Facility: SMG, Screen Management Facility
Explanation: The specified state name is less than 1 character or more than
31 characters.
User Action: Choose a state name with 1 to 31 characters.
INVSTLEVEL,

structure level is invalid or already up to current structure level

Facility: MONITOR, Monitor Utility
Explanation: An error occurred while executing a MONITOR CONVERT
command. The structure level of the input file is either unknown or already
up to the current MONITOR structure level.
User Action: Try to play back the MONITOR recording file. If it plays back
properly, it is already up to the current structure level. If it still does not play
back, the structure level is unknown to this version of MONITOR.
INVSTMNBR,

invalid stream number

Facility: SMB, Symbiont Services
Explanation: An invalid stream number is detected. This is a fatal return
status.
User Action: Please submit a Software Performance Report.
INVSTR,

string too long for field

Facility: AUTHORIZE, Authorize Utility
Explanation: The character string you specified is too long.
User Action: See the VMS Authorize Utility Manual for information on
character string length restrictions.

2-308

Messages

INVSTRDES,

invalid string descriptor

Facility: LIB, Library Facility and OTS, General Purpose Facility
Explanation: A string descriptor passed to a general library procedure did
not contain a valid DSC$B_CLASS field.
User Action: Locate the call to the library that caused the error, and initialize
the field to the proper class of descriptor. Refer to the VMS Run-Time Library
Routines Volume for a description of the classes of descriptors.
INVSTRLEV,

invalid structure level

Facility: SMB, Symbiont Services
Explanation: An invalid structure level is returned by the SMB$INITIALIZE
routine. This is a fatal return status.
User Action: Specify a valid structure level not greater than SMBMSG$K_
STRUCTURE_LEVEL.
INVSTRUCT,

invalid structure level in save set

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

invalid symbol name

Facility: LIB, Library Facility
Explanation: The length of the specified symbol is greater than 255
characters or the symbol did not begin with a letter.
User Action: Do not specify a symbol name with more than 255 characters.
Ensure that all symbol names begin with letters.
INVTAB,

command tables have invalid format-see documentation

Facility: CU, Command Language Interpreter (DCL)
Explanation: An unrecognizable command table format is encountered while
attempting to automatically upgrade old command tables to the current
format.
User Action: Use the Command Definition Utility command SET
COMMAND to re-create the tables.
INVTABSPEC,

tabs specification incorrect, not changed

Facility: VAXTPU, VAX Text Processing Utility
Explanation: Your argument to the built-in procedure SET (TAB_STOPS)
is invalid. You must specify an integer value between 1 and 65535, or a
string consisting of only spaces and integers. If you specify a string, then the
integers must be given in ascending order to achieve predictable behavior.
User Action: Correct your argument with the built-in procedure SET (TAB_
STOPS).

2-309

Messages

INVTERTAB,

invalid terminal table

Facility: SMG, Screen Management Facility
Explanation: An invalid terminal table address is specified.
User Action: Make sure you are passing the terminal table argument by
reference and not by value. Make sure the terminal table address is acquired
by calling SMG$INIT_TERM_TABLE.

INVTIME,

invalid SLEEP time

Facility: VAXTPU, VAX Text Processing Utility
Explanation: An invalid time internal was used with the SLEEP built-in.
User Action: Correct the specified time internal.

INVTOKEN,

unrecognized token 'symbol-name'

Facility: PATCH, Patch Utility
Explanation: The symbol you specified is not recognized as a valid PATCH
command name or qualifier.
User Action: Specify valid symbol and retry.

INVTQEFMT,

invalid time queue entry format

INVTYPE,

built-in type 'type-name' is not defined

Facility: CDU, Command Definition Utility
Explanation: CDU encountered an invalid keyword in a built-in definition
while reading from a CLD file.
User Action: Edit the CLD file so that all built-in keywords are defined.

INVTYPE,

invalid LIB$TPARSE state table entry

Facility: LIB, Library Facility
Explanation: The state table passed to the LIB$TP ARSE procedure is invalid
and could not be processed.
User Action: Correct the format of the state table in your program. Refer to
the VMS Run-Time Library Routines Volume for the correct format.

2-310

Messages

INVUIC,

invalid UIC

Facility: SYSMAN, Cluster System Management Utility
Explanation: An invalid UIC is entered. Either the format is bad or an
alphanumeric UIC does not have a numeric equivalent.
User Action: Enter a valid UIC. See the VMS DCL Concepts Manual.
INVUIC, invalid UIC-must be of the form [group,member]
Facility: CU, Command Language Interpreter (DCL)
Explanation: The command contains an invalid UIC. The group and member
portions of a UIC must be specified within square brackets [] and must be
separated by a comma.
User Action: Correct the UIC and reenter the command.
INVUIC,

invalid UIC specified

Facility: SMI, System Management Intergator/Server
Explanation: A UIC is nonexistent or has an invalid format.
User Action: Respecify the associated SYSMAN command with a valid UIC.
INVUIC,

'UIC' is an invalid UIC specification

Facility: RUN, Run Detached Utility
Explanation: UIC value specified with the /UIC qualifier is invalid.
User Action: Enter a valid UIC.
INVUSER,

invalid user name 'name'

Facility: INPSMB, Input Symbiont
Explanation: The specified user name is syntactically invalid.
User Action: Correct the error and reenter the job.
INVUSERN AME,

user name syntax error

Facility: AUTHORIZE, Authorize Utility
Explanation: You specified an incorrect user name.
User Action: Enter a user name specifying a string of 1 through 12
alphanumeric characters, underscores, wildcard characters (dollar signs are
permissible, but usually reserved for system names), or a UIC.
INVUSERSPEC,

error in user specification

Facility: AUTHORIZE, Authorize Utility
Explanation: Your command included an incorrect user specification. In
a user specification, you may use a numeric UIC format (for example,
[007,007]), an alphanumeric format (for example, [COMPOSERS,HAYDN]),
or a user name (for example, HAYDN). You can use wildcards to specify
multiple users. Refer to the VMS Authorize Utility Manual for specific syntax
rules for the command you are using.
User Action: Correct the user specification and reenter your command.

2-311

Messages

INVVAL,

unrecognized value

Facility: NCP, Network Control Program
Explanation: A value entered for a parameter is invalid.
User Action: Check the rules for the parameter value and reenter the
command.
INVVALCLAUSE,

invalid value clause encountered

Facility: CDU, Command Definition Utility
Explanation: CDU encountered a invalid VALUE keyword while reading
from a CLD file.
User Action: Edit the CLD file so that all VALUE keywords are valid.
INVVEC, invalid or unspecified interrupt vector
Facility: SYSGEN, System Generation Utility
Explanation: Either no interrupt vector is specified in a SYSGEN command
CONNECT, or the one that is specified is not within the UNIBUS interrupt
vector address range.
User Action: Reenter the command specifying a valid vector number.
INVVIEWSP,

invalid /VIEWING_TIME specification

Facility: MONITOR, Monitor Utility
Explanation: The /VIEWING_TIME value must be an unsigned contiguous
string of decimal digits forming a value in the range of 1 to 9,999,999
inclusive.
User Action: Reenter the MONITOR request, specifying a valid /VIEWING_
TIME value.
INVVMSOSC, invalid VMS operating system command in record "record
number"
Facility: PSM, Print Symbiont
Explanation: This status is returned by a print symbiont format routine
indicating invalid VMS operating system command in record.
User Action: Please submit a Software Performance Report.
INVVOI_ID,

invalid voice-id

Facility: DTK, DECtalk Facility
Explanation: An invalid voice identifier is specified.
User Action: Ensure that you are passing the voice identifier by reference,
not by value. Ensure that the voice identifier is previously set up by a call to
DTK$INITIALIZE.

2-312

Messages

INVVOLFMT,

volume format specified is not consistent with file spec

Facility: EXCHANGE, Exchange Utility
Explanation: The Exchange Utility encountered a /VOLUME_FORMAT
qualifier which did not make sense for the volume type implied by the file
specification.
User Action: It is very seldom necessary to use a /VOLUMEJORMAT
qualifier, since the defaults taken by EXCHANGE are usually correct. Either
leave the /VOLUME_FORMAT off, or use the correct option.
INVWIDARG, width of 0 is not permitted
Facility: SMG, Screen Management Facility
Explanation: An attempt is made to change the characteristics of the
terminal, setting its width to 0.
User Action: Correct the code. A width of 0 is invalid.
IO_CONCLO, 1/0 continued to closed file
Facility: OTS, General Purpose Facility
Explanation: An attempt is made to perform 1/0 to a file being closed. This
error can occur only at AST level.
User Action: Correct the program so that AST level routines do not perform

1/0 on files which may be closing.

IOERROR, IjO error initializing volume on 'device-name'
Facility: INIT, INITIALIZE Command
Explanation: The operator requested a volume initialization. An 1/0 error
occurred during the write process.
User Action: Attempt to perform the operation again using another volume.
Dump the error log to determine whether a hardware error occurred.
IOP,

operation invalid for file organization or device
Facility: RMS, VMS Record Management Services
Explanation: An invalid VMS RMS operation is attempted. This error can be
caused by any of the following conditions:
•

An attempt to perform block 1/0 when block 1/0 access is not specified

•

An attempt to perform record 1/0 when record I/O access is not specified

•

An attempt to rewind a process-permanent file

•

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

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

2-313

Messages

IRC,

illegal record encountered; VBN or record number STV = 'nnn'
Facility: RMS, VMS Record Management Services
Explanation: The byte count field or the control byte for a record in a file is
invalid. For sequential and indexed files, the status value {STV) field contains
the virtual block number of the block containing the record. For relative
files, the status value {STV) field contains the record number of the corrupted
record.
User Action: For sequential and indexed files, try to re-create the rest of the
file. For relative files, reinsert the bad record with the $PUT service using the
UIF option in the ROP parameter.

This error is caused by hardware errors, VMS RMS or system software errors,
or inadvertent modification of files by non-RMS programs.
ISD_OFF, image section descriptor offset is invalid
Facility: IMGACT, Image Activator
Explanation: The offset in an image header block points beyond the end of
that block. This usually indicates a corrupted or invalid image.
User Action: Relink the image.

ISD_SIZ,

image section descriptor length is invalid

Facility: IMGACT, Image Activator
Explanation: The length field of an ISD is invalid. This usually indicates a
corrupted or invalid image.
User Action: Relink the image.

ISD_VBN, ISD VBN greater than header block count
Facility: IMGACT, Image Activator
Explanation: The list of ISDs has extended to a block beyond the maximum
number of blocks allocated to the image header. This usually indicates a
corrupted or invalid image.
User Action: Relink the image.

ISI, invalid internal stream identifier (ISI) value
Facility: RMS, VMS Record Management Services
Explanation: The internal stream identifier of the RAB does not specify a
valid stream.
User Action: This error usually indicates that the stream has not been
connected; or that the RAB is inadvertently altered.

ISQUAL,

qualifier required; not found

Facility: AUTHORIZE, Authorize Utility
Explanation: The CREATE, GRANT or REVOKE command is given without
its required qualifier.
User Action: Respecify the command with the required qualifier, for example,
GRANT /IDENTIFIER.

2-314

Messages

ITC,

index entry too complicated or long
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: The entry exceeds the limit of the index buffer for a single item.
User Action: Reduce the length of the index entry.

ITD,

.IF commands nested too deep: 'string'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: The number of nested conditional commands (.IF, .IFNOT)
exceeds the maximum limit of 10.
User Action: Reduce the number of conditional commands.

ITMNOTDEF,

item requested with the /ITEM qualifier not defined for this
revision level

Facility: MONITOR, Monitor Utility
Explanation: At least one of the items requested with the /ITEM qualifier is
not defined. For a playback request, this situation can occur if the file being
played back is recorded by MONITOR in a previous version of VMS. For that
version, the item may not have been defined. For a live request, the item may
no longer be defined for the current revision of VMS.
User Action: Reenter the MONITOR command, requesting only those items
that were defined when the input file is recorded or, for a live request, are
currently defined. As an alternative, specify the /ITEM=all qualifier to obtain
all items available in the file for the requested class.
IVADDID,

system# 'id-number' cannot be added to the display

Facility: SHOW CLUSTER, Show Cluster Utility
Explanation: Information for the system identified by the system ID number
entered is not available, or the system ID number entered is not the system ID
of a node which is previously removed from the display using the REMOVE
SYSTEM/ID=system-id command.
It should be noted that the system ID number must match the ID number in

the SYS_ID field and that it must be entered in the same radix as that of the
SYS_ID field. For more information about changing the radix of a field, enter
the HELP SET field/FORMAT.
User Action: Verify that the system ID entered is correct and reenter the
command with the correct system ID, or enter the INIT command to initialize
the display and restore all nodes to the display. If the system ID is correct,
then be sure to remove the node from the display before attempting to add it
to the display.

2-315

Messages

IVADDNODE,

node 'node-name' cannot be added to the display

Facility: SHOW CLUSTER, Show Cluster Utility
Explanation: Information for the system identified by the node name
entered is not available, or the node name entered is not the name of a
node which is previously removed from the display using the REMOVE
SYSTEM/NODE=node-name command.
User Action: Verify that the node name entered is correct and reenter
the command with the correct node name, or enter the INIT command to
initialize the display and restore all nodes to the display. If the node name is
correct, then be sure to remove the node from the display before attempting
to add it to the display.

IVADDR,

invalid media address

Facility: SYSTEM, VMS System Services
Explanation: A disk address specified in a physical disk read or write
operation is not valid. This error occurs for physical read and write operations
or as a result of a hardware error.
User Action: Verify the disk address specified and update the program.

IVATIME,

invalid absolute time-use DD-MMM-YYYY:HH:MM:SS.CC format

Facility: CU, Command Language Interpreter (DCL)
Explanation: The specified absolute time is in an incorrect format.
User Action: Reenter the time in the format shown in the error message.

IVBAKADIO,

invalid backing store address for I/O

IVBLKENT,

invalid bad block specifier in string 'string'

Facility: BAD, Bad Block Locator Utility
Explanation: The block, as specified, contains an invalid character.
User Action: Correct the value in the given field.

2-316

Messages

IVBLKNUM,

'string' is an invalid block number, 'position' value 'nnnnnnnn' is
out of range

Facility: BAD, Bad Block Locator Utility
Explanation: The block number as specified is invalid due to the value in the
'position' field.
User Action: Correct the value in the given field.
IVBUFLEN,

disk boot driver invalid buffer

Facility: VAXCLUSTER, VAXcluster Facility
Explanation: An internal MSCP error occurred.
User Action: Submit a Software Performance Report.
IVBUFLEN,

invalid buffer length

Facility: SYSTEM, VMS System Services
Explanation: The exact meaning of this message depends on the device.
If the device is an LPAll-K and if this error occurs for an initialize LPAll-K
request, the initialize command table length is not the required 278 bytes. If
this error occurs for a start data transfer request, there are several possible
causes:

•

Command table length is not the required 40 bytes.

•

Buffer area size is not evenly divisible by the number of buffers assigned.

•

Individual buffer size is 0.

•

Individual buffer size is not a multiple of 2 for a multirequest mode
request, or is not 4 for a dedicated mode request.

•

Random Channel List length is 0 or not a multiple of 2.

•

Bit 15 in the last word of the Random Channel List is not set.

If the device is a DR32 interface, the command block size or the buffer block

size is zero or equal to or greater than 2**29, or the command table length is
not XF$K_CMT_LENGTH.
User Action: Action depends on the type of device to which the 1/0 request
is directed. Refer to the VMS 1/0 User's Reference Volume for additional
information.
IVCHAN,

invalid 1/0 channel

Facility: SYSTEM, VMS System Services
Explanation: The channel number specified in an input or output request is
not a valid channel number; the 1/0 operation cannot be performed.
User Action: Check for a programming error. Verify that the request to
assign the 1/0 channel completed successfully and returned a valid channel
number.

2-317

Messages

IVCHAR,

invalid numeric value-check for invalid digits

Facility: CLI, Command Language Interpreter (DCL)
Explanation: The command interpreter encountered a character string in a
context where it expected a numeric value (as the object of an arithmetic
operation in an expression, or following a qualifier that requires a numeric
value.)
User Action: Examine the command string for an undefined or incorrectly
spelled symbol name, a missing radix operator (for example, %X) preceding
a hexadecimal or octal value, an invalid value following a radix operator (for
example, %09), or for a syntax error. Reenter the command.

IVCHNLSEC, invalid channel for create and map section
Facility: SYSTEM, VMS System Services
Explanation: The channel number specified in a request to create and/ or
map a section file is busy; the section cannot be mapped.
User Action: Verify that the $OPEN request (to open the section file)
completed successfully and returned a valid channel number.

IVCMD,

invalid command

Facility: LATCP, LAT Control Program
Explanation: The LATCP detected a command syntax error.
User Action: Enter a valid command.

IVDEV,

invalid node or device name

Facility: LATCP, LAT Control Program
Explanation: An invalid LAT device or node name is specified with the
CREATE or SHOW command, or an invalid or nonexistent LAT device name
is specified with the SET command.
User Action: Verify the node or device name, and reenter the command.

IVDEVNAM,

invalid device name

Facility: SYSTEM, VMS System Services
Explanation: A device name contains invalid characters, no device is
specified, or a command or program accepts only certain types of devices
in a particular context.
User Action: Verify that the device name is specified correctly and is suitable
for the requested operation. If a logical name is used, verify that it has been
assigned a proper equivalence name.

IVDTIME,

invalid delta time-use DDDD-HH:MM:SS.CC

Facility: CLI, Command Language Interpreter (DCL)
Explanation: The specified delta time is in an incorrect format.
User Action: Reenter the delta time in the format shown in the error
message.

2-318

Messages

IVFNAM,

invalid lexical function name-check validity and spelling

Facility: CLI, Command Language Interpreter (DCL)
Explanation: A command contains the character string F$name() where
name is not a valid function.
User Action: Verify the spelling of the lexical function. Use the DCL
command HELP or refer to the VMS DCL Dictionary for a list of lexical
functions.

IVGBLTYP, invalid global master PTE type
Facility: BUGCHECK, System Bugcheck
Explanation: The VMS software detected an irrecoverable, inconsistent
condition. After all of physical memory is written to a system dump file, the
system will automatically reboot if the BUGREBOOT system parameter is set
to 1.
User Action: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error, and that includes a BACKUP save set
containing the system dump file and the error log file active at the time of the
error. (Use the /IGNORE=NOBACKUP qualifier on the BACKUP command
that produces the save set included with the SPR.)

IVGSDNAM, invalid global section name
Facility: SYSTEM, VMS System Services
Explanation: An invalid global section name is specified.
User Action: Refer to the VMS System Services Reference Manual for global
section name requirements.

IVKEYNAM,

unrecognized key name-check validity and spelling

Facility: CLI, Command Language Interpreter (DCL)
Explanation: You specified a key name incorrectly.
User Action: Correct the spelling of the key name.

IVKEYW,

unrecognized keyword-check validity and spelling

Facility: CLI, Command Language Interpreter (DCL)
Explanation: A keyword specified in a command is not valid for the
command.
User Action: The rejected portion of the command is displayed between
backslashes. Use the DCL command HELP or refer to the VMS DCL
Dictionary for a list of valid keywords.

2-319

Messages

IVLISTK,

interrupt stack invalid restart

IVLOCKID,

invalid lock id

Facility: SYSTEM, VMS System Services
Explanation: The lock identification specified in a system service request (for
example, $ENQ or $DEQ) is not a valid lock identification for that process.
User Action: Check for a programming error. Verify that the $ENQ system
service request, which returned the lock identification, completed successfully.

IVLOGNAM,

invalid logical name

Facility: SYSTEM, VMS System Services
Explanation: A name string exceeds the maximum length permitted, or has a
length of zero, or is longer than the specified maximum length logical name
string, table name string, or equivalence string. Logical names are limited to
a length of 255 characters; global section names are limited to 63 characters;
common event flag, process names, and cluster names are limited to 15
characters. An error can be returned when a name table is defined and the
name for the new name table contains invalid characters.
User Action: If the error occurs during command processing, verify the
command. If the error occurs during execution of a program, check that
the character string descriptors pointing to name strings indicate the correct
lengths.

IVLOGTAB,

invalid logical name table number

Facility: SYSTEM, VMS System Services
Explanation: A create or delete logical name system service request specified
a logical name table number that is not 0 (system), 1 (group), or 2 (process).
User Action: Check for a programming error. Verify that the logical name
table number is 0, 1, or 2.

IVLVEC,

section not installed with privilege

Facility: SYSTEM, VMS System Services
Explanation: A shareable image has not been installed with privilege.
User Action: All privileged, shareable images, that is, those images that
contain user-written system service vectors, must be installed using the
/PROTECT qualifier.

2-320

Messages

IVMODE,

invalid mode for requested function

Facility: SYSTEM, VMS System Services
Explanation: This message is associated with a status code returned by an
initialize LPAll-K request. The first three bits (2:0) of the first word (mode
word) in the command table are not 0.
User Action: Correct the LPAll-K command table.
IVOPER,

unrecognized operator in expression-check spelling and syntax

Facility: CU, Command Language Interpreter (DCL)
Explanation: An arithmetic expression contains a period (. ), indicating a
logical, arithmetic, or string operator, but the operator is not a recognized
operator. The rejected portion of the command is displayed between
backslashes.
User Action: Correct the command. Enter the DCL command HELP
EXPRESSIONS for a list of valid operators or refer to the VMS DCL Dictionary.
IVORDER,

order of ACEs being modified is incorrect for object

Facility: SET, SET Facility
Explanation: The order of the ACEs being replaced is incorrect.
User Action: Verify the order of the ACEs being replaced with the
DIRECTORY/ ACL command or the DCL SHOW ACL command.
IVPFAIL,

the IVP for 'product' has failed.

Facility: VMSINSTAL, Install Procedures
Explanation: The installation verification procedure (IVP) for the specified
product failed.
User Action: If you can resolve the problem, reinstall the product.
Otherwise, contact your DIGITAL field service representative.
IVPROT,

invalid protection code only use combinations of R,W,E, and D

Facility: CU, Command Language Interpreter (DCL)
Explanation: The protection code specified for a file or volume is not in the
correct syntax.
User Action: Use the DCL command HELP or refer to the VMS DCL
Dictionary, if necessary, for the correct syntax and reenter the command.
IVPROTECT, invalid page protection code
Facility: SYSTEM, VMS System Services
Explanation: A page protection code is specified as 1 or is greater than 15.
User Action: Check for a programming error.

2-321

Messages

IVQLOC,

invalid qualifier location-place after a parameter

Facility: CLI, Command Language Interpreter (DCL)
Explanation: A qualifier that can be used only to qualify a parameter value
in a command is placed following the command name.
User Action: Reenter the command; place the qualifier following the
parameter value it actually qualifies. Use the DCL command HELP or refer
to the VMS DCL Dictionary to determine the meaning and placement of the
qualifier.

IVQUAL,

invalid qualifier name

Facility: INSTALL, Install Utility
Explanation: An invalid qualifier is specified.
User Action: Reenter the command line.

IVQUAL,

unrecognized qualifier-check validity, spelling, and placement

Facility: CLI, Command Language Interpreter (DCL)
Explanation: The qualifier is spelled incorrectly or is improperly placed in
the command line.
User Action: Correct the command line.

IVQUAL,

value for qualifier 'name' is invalid as 'number'

Facility: LATCP, LAT Control Program
Explanation: The value 'number' for the qualifier 'name' of a SET command
is invalid or out of range.
User Action: Reenter the command with a valid value.

IVQUOTAL, invalid quota list
Facility: SYSTEM, VMS System Services
Explanation: The quota list specified for a Create Process system service is
not in the proper format, or it contained invalid quota names.
User Action: Check for a programming error. Verify that the call to the
service is programmed correctly. Refer to the VMS System Services Reference
Manual for programming specifications.

IVREMID,

system# 'id-number' cannot be removed from the display

Facility: SHOW CLUSTER, Show Cluster Utility
Explanation: The system ID number entered is not the system ID number of
a node which is currently being displayed.
User Action: Verify that the SYS_ID field in the SYSTEMS class is being
displayed and if not, display the SYS-1D field by entering in the command
ADD SYS_ID.

Verify that the system ID entered is one of the system IDs being displayed in
the SYS_ID field.

2-322

Messages

IVREMNODE,

node 'node-name' cannot be removed from the display

Facility: SHOW CLUSTER, Show Cluster Utility
Explanation: The node name entered is not the name of a node which is
currently being displayed.
User Action: Verify that the NODE field in the SYSTEMS class is being
displayed and if not, display the NODE field by entering in the command
ADD NODE. Verify that the node name entered is one of the node names
being displayed in the NODE field.
IVS,

illegal /VARIANT qualifier
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: The name specification for conditional commands is invalid.
User Action: Correct the name specification.

IVSECFLG, invalid process/global section flags
Facility: SYSTEM, VMS System Services
Explanation: Flags specified as input arguments to a system service were not
valid.
User Action: Verify that the call to the service is coded correctly. See the
VMS System Services Reference Manual for coding specifications.
IVSECIDCTL,

invalid section identification match control

Facility: SYSTEM, VMS System Services
Explanation: The match control field in the section identification argument to
identify a global section contains an invalid number.
User Action: Verify that the call to the service is coded correctly. See the
VMS System Services Reference Manual for coding specifications.
IVSSRQ,

invalid system service request

Facility: SYSTEM, VMS System Services
Explanation: A call is made to a service that does not exist.
User Action: Check for a programming error.
IVSSRVRQST,

invalid system service request

2-323

Messages

IVSTSFLG,

invalid status flag

Facility: SYSTEM, VMS System Services
Explanation: If the Create Process system service ($CREPRC) is called, this
message indicates that a reserved bit is set in a status flag argument. If the
Create Mailbox and Assign Channel system service ($CREMBX) is called, this
message indicates that the prmflg byte is not set correctly.
User Action: If $CREPRC is called, verify that the call is coded correctly.
Refer to the VMS System Services Reference Manual for coding specifications. If
$CREMBX is called, set the prmflg argument to either 1 or 0.
IVSYMB,

invalid symbol name-start with an alphabetic character

Facility: CU, Command Language Interpreter (DCL)
Explanation: An assignment statement specified a symbol name that does
not begin with an alphabetic character.
User Action: Choose a name for the symbol that begins with one of the
letters A through Z and reenter the command.
IVTIME,

invalid time

Facility: SYSTEM, VMS System Services
Explanation: A time value specified in a system service call is invalid. Either
a delta time is greater than 10,000 days, or a calculated absolute time is less
than the system date and time.
User Action: Check for a programming error. Verify that the call to the
service is coded correctly.
IVTIME,

invalid time passed in, or computed

Facility: LIB, Library Facility
Explanation: The value of an argument is out of range, or the computed
delta time is out of range.
User Action: Examine each argument. Determine which one is out of range
or is causing the computed delta time to be out of range, and correct the
program.
IVTYPE,

invalid system type 'system-type', -must match HW_TYPE field or
ALL

Facility: SHOW CLUSTER, Show Cluster Utility
Explanation: The hardware type entered is not a valid hardware type or
information for systems of the type entered is not available.
User Action: Verify that the HW_TYPE field in the SYSTEMS class is being
displayed and if not, display the HW_TYPE field by entering in the command
ADD HW_TYPE. If using the REMOVE SYSTEMS/TYPE=hardware-type
command, then verify that the hardware type entered is one of the hardware
types being displayed in the HW_TYPE field. If using the ADD SYSTEMS
/TYPE=hardware-type command, then verify that the hardware type entered
is one of V785, V780, V750, or HSSO, or simply use the command ADD
SYSTEM/TYPE=ALL

2-324

Messages

IVVALU,

invalid value syntax-see command documentaion

Facility: CU, Command Language Interpreter (DCL)
Explanation: A value for a command qualifier is not specified correctly, or a
command is not being used in its proper context. The rejected portion of the
command is displayed between backslashes.
User Action: Use the DCL command HELP or refer to the VMS DCL
Dictionary to determine the proper syntax or use of the command.

IVVERB,

unrecognized command verb-check validity and spelling

Facility: CU, Command Language Interpreter (DCL)
Explanation: The first word on the command is not a valid DCL command
or a symbol name equated with a command. The rejected portion of the
command is displayed between backslashes.
User Action: Check the spelling of the command name or symbol name and
reenter the command.

IVWSETLIST,

invalid working set list entry

JBCERROR,

error communicating with job controller

Facility: SYSTEM, VMS System Services
Explanation: An error occurred in communicating with the job controller
while handling an implicitly spooled file.
User Action: The file may or may not be printed. If it is not printed, a lost
file results. The system manager should ensure that the job controller is
functioning properly.

JBRTAINHLD,

job job-name for user username in queue 'queue-name has had
option retained replaced with hold

Facility: JBCUPGRAD, Queue Upgrade Utility
Explanation: The status of a job has been changed from retain to hold.
User Action: Contact the owner of the job to determine what corrective
actions should be taken prior to releasing the job to be scheduled for
execution.

2-325

Messages

JEC,

Unexpected text at end of command: 'string'

Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: Extraneous text (not a valid terminator) follows this command.
User Action: Insert a valid terminator after the command.
JNLACP,

Fatal error detected by journal ACP

asynchronous actions prohibited when journal file open

Facility: VAXTPU, VAX Text Processing Utility
Explanation: Asynchronous action routines are prohibited when a journal file
is open.
User Action: You must choose between journaling routines and action
routines.
JNLDRV,

Fatal error detected by journal driver

RMS Journaling not authorized; operation not performed

Facility: RMS, VMS Record Management Services
Explanation: An attempt was made to open a file marked for RMS journaling
for write access on a node that is not authorized to perform RMS journaling.
Access to the file has been denied. The secondary status value (STV) contains
the error status from the License Management Utility.
User Action: If you want to journal the file, RMS journaling must be
authorized on the node from which you access the file. Either attempt to
access the file on a node that is authorized to perform RMS journaling, or fix
the error condition specified in the secondary status value (STV). See the VMS
License Management Utility Manual for more information.

2-326

Messages

If you do not want to journal the file, unmark the file for journaling by
entering a command in the following form:
SET FILE /NOAl _JOURNAL/NOBl _JOURNAL/NORU_JOURNAL file spec

JNLNOTOPEN,

journal file not open, recovery aborted

Facility: VAXTPU, VAX Text Processing Utility
Explanation: VAXTPU is asked to recover data from a journal file, but the
journal file was not opened.
User Action: Modify your section file to open the journal file during a
recovery.
JNLOPEN,

journal file already open

Facility: VAXTPU, VAX Text Processing Utility
Explanation: A journal file is already open.
User Action: Close the current journal file before opening another.
JNLPUT,

error writing to journal file

Facility: PATCH, Patch Utility
Explanation: An output error occurred while PATCH is writing to the journal
file.
User Action: This message is issued with accompanying messages. Take
corrective action based on the accompanying messages.
Job 'name' (queue 'name', entry 'number') completed
Facility: JBC, Job Controller
Explanation: This message is issued in response to the /NOTIFY qualifier
of the PRINT or SUBMIT command to indicate that the specified job has
completed. If the job completed unsuccessfully, this message is followed by
the completion status of the job. The message is informational.
User Action: None.
Job 'name' (queue 'name', entry 'number') holding
Facility: JBC, Job Controller
Explanation: This message is issued in response to the /IDENTIFY qualifier
of the PRINT or SUBMIT command to indicate that the specified job has
been successfully entered on the queue listed. By default, this information
is displayed on the current output device for the PRINT and SUBMIT
commands. This message is informational.
User Action: None.

2-327

Messages

Job name (queue name', entry 'number') holding until 'time'
1

Facility: JBC, Job Controller
Explanation: This message is issued in response to the /IDENTIFY qualifier
of the PRINT or SUBMIT command to indicate that the specified job has
been successfully entered on the queue listed. By default, this information
is displayed on the current output device for the PRINT and SUBMIT
commands. This message is informational.
User Action: None.
1

Job 'name' (queue 'name', entry number pending
)

•

Pending status caused by insufficient access to queue

•

Pending status caused by characteristic mismatch

•

Pending status caused by lowercase attribute not present on queue

•

Pending status caused by job size below queues minimum job size limit

•

Pending status caused by job size above queues maximum job size limit

•

Pending status caused by form/stock mismatch

•

Pending status caused by 'reason'

This message is informational.
User Action: None.
1

Job 'name' (queue 'name', entry number') started on 'name'
Facility: JBC, Job Controller
Explanation: This message is issued in response to the /IDENTIFY qualifier
of the PRINT or SUBMIT command to indicate that the specified job has
been successfully entered on the queue listed. By default, this information
is displayed on the current output device for the PRINT and SUBMIT
commands.
User Action: This message is informational.

JOBABORT, job aborted during execution
Facility: JBC, Job Controller
Explanation: The execution of the affected job is aborted by a STOP
/ABORT, STOP /ENTRY, or DELETE/ENTRY command.
User Action: If necessary, resubmit the job.

2-328

Messages

JOBCARD, job beginning command

Facility: INPSMB, Input Symbiont
Explanation: The system encountered an error in a batch job entered from
a card reader. This message displays the text of the JOB command; it is
followed by the error messages for the batch job.
User Action: Take corrective action based in the accompanying messages.
JOBCTLABORT,

request failed because job controller aborted

Facility: JBC, Job Controller
Explanation: The $GETQUI, $SNDACC, $SNDJBC, or $SNDSMB system
service operation failed because the job controller process terminated
execution. The job controller voluntarily aborts and restarts itself if it
encounters a fatal system error or an internal logic error.
User Action: None.
JOBDELETE, job deleted before execution
Facility: JBC, Job Controller
Explanation: The affected job was deleted by a DELETE/ENTRY or DELETE
/QUEUE command before it executed.
User Action: If necessary, resubmit the job.
JOBQUEDIS, system job queue manager is not running
Facility: JBC, Job Controller
Explanation: The requested operation cannot be executed because the system
job queue manager has not been started. This error is returned on queue
operations before the START/QUEUE/MANAGER command has been
executed.
User Action: Consult the system manager.
JOBQUEENA, system job queue manager is already running
Facility: JBC, Job Controller
Explanation: The system job queue manager cannot be started because it is
already running. This error is returned in response to the START/QUEUE
/MANAGER command when the queue manager has been previously started.
User Action: If the system job queue manager must be restarted to specify
different queue file parameters, first issue the STOP /QUEUE/MANAGER
command. Otherwise, no action is necessary.
JOBREQUEUE, job aborted during execution and then requeued
Facility: JBC, Job Controller
Explanation: The execution of the affected job is aborted by a STOP
/REQUEUE command. The job is requeued and will be executed again.
User Action: None.

2-329

Messages

Journal file could not be closed
Facility: EDT, EDT Editor
Explanation: You used the /RECOVER qualifier in your EDIT /EDT
command line, but EDT is unable to close the journal file after processing
the commands in it. Some problem exists at the system level with that file.
User Action: Correct the problem indicated by the file system message.

Journal file could not be opened
Facility: EDT, EDT Editor
Explanation: The journal file given in the command line cannot be opened.
EDT will display an associated file system message for the error.
User Action: Correct the problem indicated by the file system message.

JOURNAL,

journaling to 'filespec'

Facility: BACKUP, Backup Utility
Explanation: The Backup Utility is writing journal records to the specified file
in response to the /JOURNAL qualifier. This message is displayed only if the
/LOG qualifier is specified.
User Action: None.

JOURNALBEG, Journal of edit session started
Facility: VAXTPU, VAX Text Processing Utility
Explanation: The journaling of your VAXTPU session has begun.
User Action: None is required. However, you may execute the built-in
procedure JOURNAL_CLOSE if you want to close the journal file.

JOURNALCLOSE, Journal file successfully closed, journaling stopped
Facility: VAXTPU, VAX Text Processing Utility
Explanation: The built-in procedure JOURNAL _CLOSE has closed the
journal file. Your subsequent commands will not be written to the journal
file.
User Action: None.

JOURNALEOF,

End of journal file found unexpectedly

Facility: VAXTPU, VAX Text Processing Utility
Explanation: Journal recovery is aborted due to an unexpected end of file.
User Action: If the recovered information is sufficient, resume editing from
this point. VAXTPU has recovered as much as it can from your journal file.

2-330

Messages

KBF,

invalid key buffer
Facility: RMS, VMS Record Management Services
Explanation: The specified key buffer is in an area of memory that cannot be
correctly accessed by the caller.
User Action: Verify that the call to the VMS RMS service is programmed
correctly. Specifically, check that the key buffer address is correctly specified.

KEY,

invalid record key
Facility: CONVERT, Convert Utility
Explanation: You have specified a key of the wrong data type.
User Action: Supply a key with the correct data type.

KEY,

invalid record number key or key value
Facility: RMS, VMS Record Management Services
Explanation: An invalid key value is specified in one of the following ways:
•

A negative or zero record number is specified for a random operation on
a sequential or relative file.

•

A packed decimal key value specified for an indexed value contained an
invalid nibble.

User Action: Modify the program, if necessary, to detect and respond to the
condition.
KEYALRINS,

key already inserted in tree

Facility: LIB, Library Facility
Explanation: A key is found in the tree, so a new key is not inserted.
User Action: None. The operation is successful.
KEYAMBINC,

key specification is ambiguous or inconsistent

Facility: SORT, Sort/Merge Utility
Explanation: You specified duplicate key parameters for a single /KEY
qualifier.
User Action: Specify each key parameter only once. For multiple keys, use a
/KEY qualifier for each key.
KEYCNV,

synonym 'key name' has been converted to 'key name'

Facility: CLI, Command Language Interpreter (DCL)
Explanation: This informational message signifies that the key name specified
in the DEFINE/KEY command is a synonym for a definable key name. The
synonym name is converted to the actual key name prior to defining the key.
User Action: None.

2-331

Messages

KEYDEFPRO,

key definition is protected-cannot be changed or deleted

Facility: SMG, Screen Management Facility
Explanation: The specified key is already defined, and since its definition is
protected, it cannot be changed or redefined.
User Action: None.

KEYED,

mismatch between sort/merge keys and primary file key

Facility: SORT, Sort/Merge Utility
Explanation: You created an empty indexed file with a primary key that does
not match the sort key. The sort operation is less efficient than it is when the
two keys match.
User Action: For greater efficiency, create a new indexed file or change your
sort key.

KEY_LEN,

invalid key length, key number n, length n

Facility: SORT, Sort/Merge Utility
Explanation: The key size is incorrect for the data type, or the total key size
is greater than 32,767.
User Action: Specify the correct key field size. Size must be less than or
equal to 32,767 for character data; 1, 2, 4, 8, or 16 for binary data; and less
than or equal to 31 for decimal. Also, only ascending or descending order is
allowed.

KEYMAPNOTFND,

key map 'key-map-name' not found in key-map list 'keymap-list-name'

Facility: VAXTPU, VAX Text Processing Utility
Explanation: You are trying to remove a key map that is not in the key-map
list.
User Action: Enter the built-in procedure SHOW (KEY_MAP_LISTS) on the
command line to obtain the names of the key maps in your key-map list.

KEYNAMLNG,

key 'key-name 1 name length illegal in library 1filespec 1

Facility: LIBRAR, LIBRARY Command
Explanation: The name of the module you are inserting exceeds the name
length limit for the library.
User Action: Rename the module before inserting it into the library.

KEYNOTDEF,

key is not defined

Facility: SMG, Screen Management Facility
Explanation: An attempt is made to perform an operaton, such as
SMG$GET_KEY_DEF, on a key which is not defined.
User Action: Check your program to see if this key should have been
defined.

2-332

Messages

KEYNOTFND,

key not found

Facility: LBR, Librarian Subroutine Package

Explanation: This error message is generated by the Librarian routines. The
Librarian could not find the key you specified in the key name argument to
the LBR$LOOKUP_KEY routine.
User Action: Correct the key name argument before calling the routine.
KEYNOTFOU,

key not found in tree

Facility: LIB, Library Facility

Explanation: The specified key is not found in the tree.
User Action: Take appropriate action.
Keys cannot be defined in N okeypad mode
Facility: EDT, EDT Editor

Explanation: The nokeypad DEFK command can reassign the key definition
function only in keypad mode to a key other than CTRL/K. It cannot be used
to redefine keys. The attempted operation cannot be performed.
User Action: None.
KEYSUPERSEDED,

definition of key 'name' superseded

Facility: VAXTPU, VAX Text Processing Utility

Explanation: The key you are defining is already defined. The new
definition, which you supplied, will replace the old one.
User Action: None.
KEYWORDPARAM,

keyword 'name' used as procedure, variable, or constant

Facility: VAXTPU, VAX Text Processing Utility

Explanation: A keyword is being used as a user-defined procedure variable
or constant.
User Action: Use a name that is not a keyword and recompile your program.
KFF,

known file found
Facility: RMS, VMS Record Management Services

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

2-333

Messages

KNM,

key name buffer not accessible for key= 'nnn'

Facility: RMS, VMS Record Management Services
Explanation: The key name buffer address in a key definition XAB specifies
an area of memory that cannot be correctly accessed by the caller.
User Action: The status value (STV) field of the FAB provides the key of
reference of the XAB in error. Verify that the call to the VMS RMS service is
coded correctly; in particular, verify that the buffer is readable for a $CREATE
operation, and writeable for a $DISPLAY or $OPEN operation.
KRF,

invalid key-of-reference for $GET /$FIND

Facility: RMS, VMS Record Management Services
Explanation: The key-of-reference value specified in the RAB is greater than
the number of keys defined for the file.
User Action: Verify that the call to the VMS RMS service is coded correctly.
KRNLSTAKNV,

kernel stack not valid

index bucket will not hold two keys for key-of-reference= 'nnn'

Facility: RMS, VMS Record Management Services
Explanation: The size of the index buckets specified for the key must be
large enough to hold at least two key values.
User Action: The status code (STV) field of the FAB provides the key of
reference of the XAB in error. Verify that the VMS RMS service is coded
correctly.
KSZ,

invalid key size for $GET /$FIND

Facility: RMS, VMS Record Management Services
Explanation: The key size specified for a relative or sequential file does not
specify a length of four bytes. Or the key size specified for an indexed file is
greater than the key length or is zero for a string key.
User Action: Verify that the call to the VMS RMS service is coded correctly.

2-334

Messages

LABELERR,

error in tape label processing on 'save-set-spec'

Facility: BACKUP, Backup Utility
Explanation: The Backup Utility encountered an error during an attempt to
process the file labels on the specified volume. The accompanying message
provides additional information.
User Action: Correct the condition that caused the error and reenter the
command.
LAN,

invalid lowest-level-index area number for key= 'nnn'
Facility: RMS, VMS Record Management Services
Explanation: The lowest-level-index area number specified in a key definition
XAB is not a defined area for the file.
User Action: The status value (STV) field of the FAB provides the key of
reference of the XAB in error. Verify that the call to the VMS RMS service is
coded correctly.

LARGECNT,

'device-name' is too large to be processed

Facility: BACKUP, Backup Utility
Explanation: The specified volume is too large to be processed by the Backup
Utility. The error may be caused because the specified cluster factor is too
small.
User Action: Retry the operation using a larger volume cluster factor.
LARGECNT,

disk too large to be supported

Facility: INIT, INITIALIZE Command
Explanation: This version of Files-11 does not support a disk of this size.
User Action: Check the device driver to determine if it is initializing the
device database correctly. You may have a need for DIGITAL-supplied
custom software.
LASTCHANCE,

stack exception handlers lost, reinitializing stack

Facility: DEBUG, VMS Debugger
Explanation: The applications program contained an error that caused the
exception handling mechanism to fail. This error occurs when the stack is
overwitten by the applications program or by deposit commands.
User Action: Identify and correct the error in the application program.
LCKP AGFUL,

no more pages may be locked in memory

Facility: SYSTEM, VMS System Services
Explanation: An attempt to lock pages in memory failed because the system
limit for the number of locked pages is reached.
User Action: See your system manager. If some pages were successfully
locked, unlock them and attempt to load the new pages.

2-335

Messages

LDE, literal doesn't end with .END LITERAL: 'STRING'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: A DSR command .END LITERAL does not immediately follow
the final line of a DSR command .LITERAL n (where n is the number of lines
to be produced).
User Action: Put the DSR command .LITERAL on the correct line, recount
the number of lines of literal text and reset n, or remove then value.

LENMUSONE, length of fill string and clear string must be 1
Facility: SMG, Screen Management Facility
Explanation: A call to SMG$READ_VERIFY specified a fill string or a clear
string more than 1 character long. Since fill character matching is done one
character at a time, only one character may be specified for the fill and clear
string.
User Action: Modify the fill string or the clear string, or both, to be 1
character long.

LENNOTEQL,

length of picture string and initial string are not equal

Facility: SMG, Screen Management Facility
Explanation: A call to SMG$READ_VERIFY specified a picture string and an
initial string of unequal lengths. Since the initial string is used as the default
value for the input, it must match the picture string in length.
User Action: Modify the initial string so that is is the same length as the
picture string.

LENVIO,

address space length violation

Facility: SYSTEM, VMS System Services
Explanation: 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. Verify that the call to the
service is coded correct! y.

LEX,

invalid $EXTEND for area 'nnn' containing an unused extent
Facility: RMS, VMS Record Management Services
Explanation: A VMS RMS $EXTEND operation attempted to extend the
specified area, and an unused extent is already allocated. Each area has, at
most, one current extent and one unused next extent.
User Action: The status value (STV) field of the FAB contains the area
number in error. Verify that the call to the VMS RMS service is coded
correctly.

2-336

Messages

LIBFIND, failed to find valid module or STB at RFA 'number:number' for module
'module-name' file 'filename'
Facility: LINK, Linker Utility
Explanation: The linker tried to read the stated object module at the specified
Record File Address, but did not find a valid module. This is generally due to
someone deleting a module out of a library between Pass 1 and Pass 2.
User Action: Retry the link operation. If it continues to fail with the same
error, try rebuilding the library.

LIBNAMLNG, library module name 'module-name' has illegal length ('decimalnumber')
Facility: LINK, Linker Utility
Explanation: A library module name specified in the /INCLUDE qualifier
has illegal length.
User Action: Reenter the command correctly.

LIBNOTOPN, library not open
Facility: LBR, Librarian Subroutine Package
Explanation: This error message is generated by the Librarian routines.
Except for LBR$INl_CONTROL and LBR$0PEN, all routines require that the
library be open.
User Action: Open the library before calling the routine.

LIBOPN, library already open
Facility: LBR, Librarian Subroutine Package
Explanation: This warning message is generated by the Librarian routines.
The library you attempted to open is already open. Processing of your
program continues.
User Action: None.

LINCOM, line communication error
Facility: NCP, Network Control Program
Explanation: The requested line is unavailable, or an error occurred during
transmission to the line. For example, this error occurs if the line identifier is
incorrect.
User Action: Make sure that you are correctly identifying the line, and that
the line is in the correct state for the function you are performing.

2-337

Messages

LINEABRT,

host aborted transmission or failed to respond

Facility: SYSTEM, VMS System Services
Explanation: The IBM host either aborted the current transmission with a
protocol sequence (EOT) or failed to respond to an emulator-generated ENQ.
In the latter case, the emulator sent the number of ENQ sequences specified
by the ENQ count in 10$_SETCHAR, and the IBM host did not issue an
appropriate response.
User Action: Retry the transmission. If you continue to receive this message
after several attempts, the line is probably defective and/or unusable.

Line exceeded 255 characters, truncated
Facility: EDT, EDT Editor
Explanation: The input for the line exceeds 255 characters; the excess is
deleted.
User Action: None.

LINEINFO,

'line-description'

Facility: DEBUG, VMS Debugger
Explanation: Accompanying this message is one of the following lines of
text:

no line information is available
no 'line-number', previous line is 'line-number', next line is 'line-number'
This message is issued when the debugger cannot associate a specified line
number with an instruction in your program, for example, after an EXAMINE
/SOURCE or SET BREAK command.
User Action: Specify a line number associated with an instruction, for
example, a routine or a label.

LINERR,

command line segment in error 'text'

Facility: LINK, Linker Utility
Explanation: Errors were found during command line processing. The given
segment of the command line is in error.
User Action: Correct the error and retry the operation.

LINETOOLONG,

line is maximum length, cannot add text to it

Facility: VAXTPU, VAX Text Processing Utility
Explanation: The line in the text buffer is already at the maximum length
allowed.
User Action: Use the built-in procedure SHOW to find the maximum length
and then shorten the line.

2-338

Messages

LINK,

error on logical link

Facility: CNF, NI Configurator
Explanation: An error occurred on a logical link.
User Action: See the accompanying message to determine the appropriate
action.
LINKABORT,

network partner aborted logical link

Facility: SYSTEM, VMS System Services
Explanation: The remote process disconnected the logical link either because
the process exited prematurely or because it is the normal way for the process
to disconnect the link.
User Action: Check to see if the node is reachable and retry.
LINKACTIVE, link is already active
Facility: LATCP, LAT Control Program
Explanation: You attempted to activate a link (using the SET NODE or
START NODE command) that is already active.
User Action: None.
LINKDISCON,

network partner disconnected logical link

Facility: SYSTEM, VMS System Services
Explanation: The remote process disconnected the logical link. This is an
expected action.
User Action: None.
LINKEXISTS, link name already exists
Facility: LATCP, LAT Control Program
Explanation: You attempted to create a link that you have already created.
User Action: Reenter the command with a new link name.
LINKEXIT,

network partner exited

Facility: SYSTEM, VMS System Services
Explanation: The remote process exited before confirming the logical link for
one of the following reasons:
•

A problem with the log file on the remote node

•

An unopened remote log file because of a write-locked disk (on the
remote node)

•

A premature exit of the process

User Action: Refer to the VMS Networking Manual. Then either read the
remote log or retry the operation.

2-339

Messages

LINNOTFND,

requested line is not found

Facility: SMG, Screen Management Facility
Explanation: The input line requested in a call to SMG$RETURN _INPUT_
LINE is not found.
User Action: If necessary, modify your program to recognize this condition
and respond to it.

LINPRO, line protocol error
Facility: NCP, Network Control Program
Explanation: Indicates an invalid line protocol message or operation during
direct line access. In the case of a line loop test, an error that should have
been detected by the line protocol is detected during message comparison.
User Action: Make sure that the line protocol and the line characteristics are
set correctly.

LINTOOLONG, line too long
Facility: MACRO, VAX MACRO Assembler
Explanation: A source line in a macro definition is longer than 1000
characters.
User Action: Restructure the source code so that the line is shorter.

LISINPSAV,

/LIST requires save set as input

Facility: BACKUP, Backup Utility
Explanation: The input specification for a listing operation must reference a
save set.
User Action: Correct the specification and reenter the command.

LISTNOTFND,

attribute name not previously defined

Facility: CDU, Command Definition Utility
Explanation: There is an undefined symbol reference in the syntax of the
CLD file.
User Action: Define the syntax list in the CLD file.

LKBGRANTED,

LKB is granted, but shouldn't be

2-340

Messages

LKBREFNEG, LKB reference count negative
Facility: BUGCHECK, System Bugcheck
Explanation: The VMS software detected an irrecoverable, inconsistent
condition. After all of physical memory is written to a system dump file, the
system will automatically reboot if the BUGREBOOT system parameter is set
to 1.
User Action: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error, and that includes a BACKUP save set
containing the system dump file and the error log file active at the time of the
error. (Use the /IGNORE=NOBACKUP qualifier on the BACKUP command
that produces the save set included with the SPR.)
LKPNOTDON,

lookup has not been done

Facility: LBR, Librarian Subroutine Package
Explanation: This error message is generated by the Librarian routines.
LBR$LOOKUP-1<EY is not called before calling up LBR$GET_RECORD.
User Action: Call LBR$LOOKUP_KEY before calling LBR$GET_RECORD.
LKWSETFUL, locked portion of working set is full
Facility: SYSTEM, VMS System Services
Explanation: No more pages can be locked in the working set because there
would not be enough remaining pages available dynamically for the image to
continue execution.
User Action: Use the DCL command SET WORKING_SET to increase the
working set limit, if the limit is not already set at the maximum allowed. If
the working set limit is already at the maximum allowed, correct the program
that attempted to lock too many pages in the working set.
LNE, logical name translation error
Facility: RMS, VMS Record Management Services
Explanation: VMS RMS encountered an error while translating a logical
name. This can be an error from the following:
•

The limit of 10 levels of logical name translation has been exceeded.

•

A logical name is recursively entered in a logical name table.

•

A logical name translates to an invalid process permanent file name
equivalence string.

User Action: Use the DCL command SHOW LOGICAL to verify the current
result of translation on the specified logical name. Verify that the call to the
VMS RMS service is coded correctly.
LNK, invalid link identification
Facility: NCP, Network Control Program
Explanation: The format of the link identification is incorrect.
User Action: Check the syntax rules for link identifiers, and reenter your
command with the correct link identifier.

2-341

Messages

LOADERR,

error loading image, image-name

Facility: ERF, Error Log Utility
Explanation: An error occurred during an attempt to load the specified
image.
User Action: Obtain the specified image from your distribution kit. If
the specified image is not part of your distribution kit, submit a Software
Performance Report.

LOADIDX,

error loading secondary index n

Facility: CONVERT, Convert Utility
Explanation: Some error occurred during the load of the specified key of
reference on the output file. This message will be accompanied by another
message that will describe the error. NOTE: Indexes 0 through n-1 are intact.
User Action: Correct the error described by the other message and try again.

LOCKED,

data base locked. Try again later.

Facility: LATCP, LAT Control Program
Explanation: LATCP cannot run because another user is modifying the
LATCP database.
User Action: Wait for a while; then reenter the command. If the problem
persists, determine who is using LATCP. Wait until that person is finished, or
ask him or her to exit.

LOCKHEADER,

file (1file-id') filename deaccess locked

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the specified file is marked as
deaccess locked.
User Action: If the /CONFIRM qualifier is specified, the user may elect to
unlock or to delete the file.

LOCKMGRERR, error detected by Lock Manager
Facility: BUGCHECK, System Bugcheck
Explanation: The VMS software detected an irrecoverable, inconsistent
condition. After all of physical memory is written to a system dump file, the
system will automatically reboot if the BUGREBOOT system parameter is set
to 1.
User Action: Submit a Software Performance Report (SPR) that describes
the conditions leading to the error, and that includes a BACKUP save set
containing the system dump file and the error log file active at the time of the
error. (Use the /IGNORE=NOBACKUP qualifier on the BACKUP command
that produces the save set included with the SPR.)

2-342

Messages

LOCKVOL,

error locking volume set-/REP AIR canceled

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility encountered an error during an attempt to
lock the volume set to execute a /REP AIR operation. The accompanying
message provides additional information.
User Action: Correct the condition that caused the error and reenter the
Verify Utility command line. The /REPAIR qualifier requires a system UIC or
SYSPRV privilege, or that the user be the owner of the volume.
LOCNEG,

entity explicitly and locally negated in command string

Facility: CLI, Command Language Interpreter (DCL)
Explanation: The specified qualifier is present in its negated form (with /NO)
and is used as a local qualifier.
User Action: None.
LOCNOTEST, lock is not established
Facility: PPL, Parallel Processing Facility
Explanation: You cannot release a lock you have not been granted.
User Action: Code your program to ensure that the lock is held by the caller
attempting to release it.
LOCPRES,

entity value is locally present in command string

Facility: CLI, Command Language Interpreter (DCL)
Explanation: The specified qualifier is present and is used as a local qualifier.
User Action: None.
LOGCLOS,

logfile closed by operator 'filespec' logfile is 'filespec'

Facility: OPCOM, Operator Communication
Explanation: This message indicates that OPCOM has closed the operator's
log file.
User Action: None.
LOGDBUR,

event receiver database update at 'dd-mm-yy hh:mm:ss.ms'

Facility: EVL, Event Logger
Explanation: The event receiver updated its internal database as a result of a
startup or notification from NETACP. This message displays the time stamp
for the update. This is an informational message.
User Action: None.

2-343

Messages

LOGDBUT,

event transmitter database update at 'dd-mm-yy hh:mm:ss.ms'

Facility: EVL, Event Logger
Explanation: The event transmitter updated its internal database as a result
of EVL startup or notification from NETACP. This message displays the time
stamp for the update. This is an informational message.
User Action: None.

LOGFAIL,

failed logfile operation on file 'filespec'

Facility: OPCOM, Operator Communication
Explanation: The DCL command REPLY /LOG failed to create a new
operator communication log file. This message generally indicates a file
system failure.
User Action: Accompanying messages indicate the reason for the failure.

LOGIC, logic error in NCP
Facility: NCP, Network Control Program
Explanation: A logic error occurred in NCP.
User Action: Submit a Software Performance Report detailing the command
that caused this error.

LOGIC,

program logic error or unexpected condition

Facility: CNF, NI Configurator
Explanation: A condition or circumstance is encountered which NICONFIG
logic is unprepared to handle.
User Action: This is a programming error and should be reported.

LOGIN-account is auto-login only
Facility: LOGIN, Login Processor
Explanation: The automatic login feature permits users to log in to the
system without specifying a user name. An automatic login account cannot
be accessed by a normal interactive login or by an explicit DECnet access
control string. This message is not displayed to the user; it is written to the
system accounting and security audit records. The message displayed to the
user is "User authorization failure"; the message displayed to the system
manager is AUTOLOGIN.
User Action: None.

LOGIN-account is disabled
Facility: LOGIN, Login Processor
Explanation: An attempt is made to log in to an account when the account
is disabled. An account's system access can be restricted by setting the
DISUSER flag in the user authorization file. This message is not displayed
to the user; it is written to the system accounting and security audit records.
The message displayed to the user is "User authorization failure"; the message
displayed to the system manager is DISUSER.
User Action: None.

2-344

Messages

LOGIN-breakin evasion in effect
Facility: LOGIN, Login Processor
Explanation: Access to an account is denied because break-in evasion is
in effect for that account. This message is not displayed to the user; it is
written to the system accounting and security audit records. The message
displayed to the user is "User authorization failure"; the message displayed to
the system manager is EVADE.
User Action: None.
LOGIN-error accessing authorization record
Facility: LOGIN, Login Processor
Explanation: The Login Processor could not read the specific user record for
this user. The message displayed to the system manager is USERAUTH.
User Action: Try the operation again later.
LOGIN-error accessing network authorization file
Facility: LOGIN, Login Processor
Explanation: LOGIN could not read the SYS$SYSTEM:NETPROXY.DAT
network user authorization file. The message displayed to the system
manager is NETUAFERR.
User Action: Determine whether the file SYS$SYSTEM:NETPROXY.DAT
exists and, if it does, make sure it is not protected against system read access.
LOGIN-error accessing system authorization file
Facility: LOGIN, Login Processor
Explanation: LOGIN could not read SYS$SYSTEM:SYSUAF.DAT. The
message displayed to the system manager is FILEACC.
User Action: Check to see that the file exists and that it has system read
access.
LOGIN-error activating command interpreter 'CLI name'
Facility: LOGIN, Login Processor
Explanation: An error occurred when you tried to activate the specified
command interpreter. The message displayed to the system manager is
CLIFAIL.
User Action: Ensure that the command interpreter image exists and that the
image file has read access.
LOGIN-error activating command interpreter tables 'table name'
Facility: LOGIN, Login Processor
Explanation: LOGIN cannot access the specified command language
interpreter tables. The message displayed to the system manager is
CLITBLFAIL.
User Action: Determine whether the specified tables exist and, if they do,
make sure they are not protected against system read access.

2-345

Messages

LOGIN-error changing expired password
Facility: LOGIN, Login Processor
Explanation: An error occurred while changing an expired password. This
message is usually accompanyied by an additional message describing the
exact cause of the error. (This message appears as FRCPWDERR to the
system manager.)
User Action: Take corrective action based in the accompanying message.
LOGIN-error connecting to 'terminal-name'
Facility: LOGIN, Login Processor
Explanation: An error occurred when the system attempted to reconnect to
the specified disconnected terminal. The message displayed to the system
manager is CONNERR.
User Action: Try again. If the error reoccurs, report it to your system
manager.
LOGIN-error creating space for command interpreter symbol table
Facility: LOGIN, Login Processor
Explanation: There is not enough virtual address space available to create
the command interpreter symbol table. The message displayed to the system
manager is CLISYMTBL.
User Action: Check that the system is set up with the value of
VIRTUALPAGECOUNT large enough to allow the CU to be mapped.
LOGIN-error opening 'filename' as input
Facility: LOGIN, Login Processor
Explanation: A file to be read by LOGINOUT (for example, a file containing
the announcement message) cannot be opened. The message displayed to the
system manager is OPENIN.
User Action: Ensure that the file exists and that it has read access.
LOGIN-error opening primary input file SYS$INPUT
Facility: LOGIN, Login Processor
Explanation: The system cannot open the current input device and cannot
perform the login. This message is usually accompanied by a VMS RMS
message indicating the reason for the failure. The message displayed to the
system manager is INPUTERR.
User Action: Take corrective action based on the VMS RMS message, and
repeat the login procedure, if possible.

2-346

Messages

LOGIN-error opening primary output file SYS$0UTPUT
Facility: LOGIN, Login Processor
Explanation: The system cannot open the current output device and cannot
perform the login. This message is usually accompanied by a VMS RMS
message indicating the reason for the failure. The message displayed to the
system manager is OUTPUTERR.
User Action: Take corrective action based on the accompanying message,
and repeat the login procedure, if possible.

LOGIN-error protecting command interpreter pages
Facility: LOGIN, Login Processor
Explanation: An error occurred when you tried to write-protect the CU code.
The message displayed to the system manager is CLIPROT.
User Action: Try the operation again later.

LOGIN-error protecting command interpreter tables pages
Facility: LOGIN, Login Processor
Explanation: An error occurred when the system tried to write-protect the
command interpreter table pages. The message displayed to the system
manager is CLITBLPROT.
User Action: Try again. If the error reoccurs, report it to your system
manager.

LOGIN-error reading command input
Facility: LOGIN, Login Processor
Explanation: An error occurred during the entry of the command; for
example, the timeout period following the prompt for user name or password
expired before you entered the responses. The message displayed to the
system manager is CMDINPUT.
User Action: Repeat the login procedure.

LOGIN-fatal job controller interaction problem
Facility: LOGIN, Login Processor
Explanation: An internal error occurred in the job controller during the login;
the login cannot be performed. The message displayed to the system manager
is JBCMIXUP.
User Action: Repeat the login procedure. If the failure persists, notify the
system operator or manager of the problem.

LOGIN-invalid password
Facility: LOGIN, Login Processor
Explanation: The specified password is incorrect. This message is not
displayed to the user; it is written to the system accounting and security
audit records. The message displayed to the user is "User authorization
failure"; the message displayed to the system manager is INVPWD.
User Action: None.

2-347

Messages

LOGIN-invalid SYS$INPUT for interactive login
Facility: LOGIN, Login Processor
Explanation: SYS$INPUT is a logical name for the input from a process to
the system. When you use the system interactively, SYS$INPUT is assigned
to your terminal by default. The system then acts upon the input it receives
from your terminal. During your process, you can redefine SYS$INPUT to a
data file; the system will then read input from the file. However, you cannot
initiate an interactive process while SYS$INPUT is defined as a file. Filestructured storage devices are not permitted as SYS$INPUT for interactive
processes. The purpose of this restriction is to prevent LOGIN from reading
a user name and password from a file. The message displayed to the system
manager is INVINPUT.
User Action: Use a non-file-structured device as SYS$INPUT for an
interactive process.
LOGIN-licensed number of system users exceeded
Facility: LOGIN, Login Processor
Explanation: The maximum number of interactive users for which your
system is licensed have already logged in. Further logins are currently
disabled. The message displayed to the system manager is EXLICENSE.
User Action: Log in after another user has logged off. If the maximum
number of users is exceeded frequently, ask your system manager whether
the system's license can be upgraded.
LOGIN-logins are currently disabled-try again later
Facility: LOGIN, Login Processor
Explanation: Logins are currently disabled. The message displayed to the
system manager is LOGDISABLE.
User Action: Do not attempt to log in at this time. Try again later.
LOGIN-maximum number of users exceeded-try again later
Facility: LOGIN, Login Processor
Explanation: The installation-defined maximum number of users has been
reached. The message displayed to the system manager is EXQUOTA.
User Action: Wait and try to log in later, after other users have logged out.
LOGIN-no such user
Facility: LOGIN, Login Processor
Explanation: The specified user name does not exist. This message is not
displayed to the user; it is written to the system accounting and security audit
records. The message displayed to the user is "User authorization failure"; the
message displayed to the system manager is NOSUCHUSER.
User Action: None.

2-348

Messages

LOGIN-qualifier not allowed in captive accounts
Facility: LOGIN, Login Processor
Explanation: You attempted to use qualifiers (for example, /CLI or /DISK)
on an account logging in that is a captive account. If the account logging in
is a captive account, no qualifiers may be changed. The message displayed to
the system manager is CAPTIVE.
User Action: Retry without specifying qualifiers.

LOGIN-system password timeout
Facility: LOGIN, Login Processor
Explanation: A user failed to correctly enter the system password within
the allotted time period (as defined by the SYSGEN parameter LGJ_pwo_
TMO). This message is not displayed to the user; it is written to the system
accounting and security audit records. The user does not receive a message
display when this error occurs. The message displayed to the system manager
is SYSPWDTMD.
User Action: None.

LOGIN-unrecognized qualifier keyword
Facility: LOGIN, Login Processor
Explanation: An invalid qualifier is specified on the LOGIN command line.
The message displayed to the system manager is CLIFAIL.
User Action: Verify the command line you entered and repeat the login
procedure.

LOGIN-user authorization failure
Facility: LOGIN, Login Processor
Explanation: You incorrectly entered your user name, your password, or
both. The message displayed to the system manager is USERAUTH.
User Action: Repeat the login procedure.

LOGIN-value required on qualifier
Facility: LOGIN, Login Processor
Explanation: You specified a qualifier without a value.
User Action: Verify the command line you entered; specify a value and
repeat the login procedure.

LOGIN-VMS host system modem not wired correctly-contact your system
manager
Facility: LOGIN, Login Processor
Explanation: The modem connected to the VMS system is not asserting the
proper signal control as described in the VMS 1/0 User's Reference Volume.
(This message appears as NOTMODEM to the system manager.)
User Action: Contact your system manager.

2-349

Messages

LOGIN-you are at maximum allowed processes for your account name
Facility: LOGIN, Login Processor
Explanation: No more processes may be logged in under this account. The
message displayed to the system manager is ACNTEXC.
User Action: Wait until another process logged in under this account has
logged out.

LOGIN-you are at maximum processes for your user name
Facility: LOGIN, Login Processor
Explanation: No more processes may be logged in under this user name.
The message displayed to the system manager is EXQUOTA.
User Action: Wait until another process using this user name has logged out
and retry.

LOGIN-you are not authorized to do reconnections
Facility: LOGIN, Login Processor
Explanation: You are not authorized to reconnect to disconnected processes.
The message displayed to the system manager is DISRECONNECT.
User Action: Log in again without specifying the /CONNECT qualifier after
your user name.

LOGIN-you are not authorized to log in at this time
Facility: LOGIN, Login Processor
Explanation: At the present time, you are restricted from the class of login
you are attempting. The login classes are: LOCAL, DIALUP, REMOTE,
NETWORK, and BATCH. The system manager can restrict your use of each
login class at specific times. The message displayed to the system manager is
BAD HOUR.
User Action: If possible, try a different login class. For example, if you are
currently restricted from BATCH logins, try an interactive class (LOCAL,
REMOTE, or DIALUP). If you are currently restricted from all login classes,
you cannot log in until you are permitted to use the system. You may
also want to ask your system manager about the login restrictions for your
account.

LOGIN-you are not authorized to log in from this source
Facility: LOGIN, Login Processor
Explanation: You do not have authorization for the login class you are
attempting from the current source. The login classes are: LOCAL, DIALUP,
REMOTE, NETWORK, and BATCH. The system manager can restrict your
use of each login class at specific times. The message displayed to the system
manager is RESTRICT.
User Action: If possible, try a different login class. For example, if you are
currently restricted from BATCH logins, try an interactive class (LOCAL,
REMOTE, or DIALUP). If you are currently restricted from all login classes,
you cannot log in until you are permitted to use the system. You may
also want to ask your system manager about the login restrictions for your
account.

2-350

Messages

LOGIN-you are not authorized to log in today
Facility: LOGIN, Login Processor
Explanation: You are restricted from the class of login you have attempted
today. The system manager can restrict your use of a login class on specific
days. The message displayed to the system manager is BADDAY.
User Action: If possible, try a different login class. For example, if you
are restricted from BATCH logins today, try an interactive class (LOCAL,
REMOTE, or DIALUP). If you are restricted from all classes of logins today,
you cannot log in until you are permitted to use the system. You may
also want to ask your system manager about the login restrictions for your
account.

LOGIN-you are not authorized to specify CLI parameters
Facility: LOGIN, Login Processor
Explanation: You do not have authorization to specify an alternate command
language interpreter (CU), or alternate CU tables. The message displayed to
the system manager is DEFCLI.
User Action: Log in again without specifying the /CU or /TABLES qualifiers
after your user name.

LOGIN-your account has expired-contact your system manager
Facility: LOGIN, Login Processor
Explanation: When creating an account, the system manager can limit it to a
specific time period, after which the account becomes invalid. Your account
has exceeded its time limit. The message displayed to the system manager is
ACNTEXPIR.
User Action: Ask your system manager to renew your account.

LOGIN-your password has expired-contact your system manager
Facility: LOGIN, Login Processor
Explanation: Your password is valid for a specific length of time as
determined by your system manager. When a password reaches the end
of its specified time period, it expires and can no longer be used to gain access
to the system. This is a system security feature that forces users to change
their passwords on a regular basis. You should have been receiving advance
messages notifying you when your password would expire. The message
displayed to the system manager is PWDEXPIR.
User Action: Ask your system manager for a new password.

LOGINIT, logfile initialized by operator 'filespec' logfile is 'filespec'
Facility: OPCOM, Operator Communication
Explanation: A DCL command REPLY /LOG successfully initialized a new
operator communication log file. This message is informational.
User Action: None.

2-351

Messages

LOGIO, NICONFIG requires LOG_IO privilege
Facility: CNF, NI Configurator
Explanation: NICONFIG must run with LOG --10 privilege.
User Action: Install NICONFIG with LOG_IO privilege or run it from an
account with LOG _IO privilege.

LOGLINK,

network error creating link to node 'node-name::'

Facility: MAIL, Mail Utility
Explanation: An error occurred when MAIL attempted to use DECnet-VAX
to communicate with another system. This message is usually accompanied
by a system error message indicating the reason for the error.
User Action: Resolve the problem and reenter the command.

LOGNAME,

logical name is too long

Facility: MOUNT, Mount Utility
Explanation: A logical name contains more than 63 characters.
User Action: Reenter the command; specify a logical name that has fewer
than 63 characters.

LOGOPNM,

open link to event monitor 'sink-name' at 'dd-mm-yy hh:mm:ss.ms'

Facility: EVL, Event Logger
Explanation: The event receiver opened a logical link to the specified event
monitor program. This message displays the name of the program and the
time stamp for the operation. This is an informational message.
User Action: None.

LOGOPNR,

connect accepted by event receiver from node 'node-id' at 'dd-mm-yy
hh:mm:ss.ms'

Facility: EVL, Event Logger
Explanation: The event receiver accepted a link from an event transmitter on
the specified node. This message displays the identification of the node and
the time stamp for the operation. This is an informational message.
User Action: None.

LOGOPNT,

open link to event receiver on node 'node-id' at 'dd-mm-yy
hh:mm:ss.ms'

Facility: EVL, Event Logger
Explanation: The event transmitter attempted to open a logical link to the
event receiver on the specified node. This message displays the identification
of the node and the time stamp for the operation. This is an informational
message.
User Action: None.

2-352

Messages

LOGTIME, logfile time stamp
Facility: OPCOM, Operator Communication
Explanation: This message, written periodically in the operator's log file,
indicates that the system is functioning properly at the time specified.
User Action: None.
LOGZERNEG, logarithm of zero or negative value
user PC location
Facility: MTH, Mathematics Facility
Explanation: The LOG or DLOG math procedure is called with a zero or a
negative number. The result returned is the reserved operand, minus zero.
User Action: Locate the call to the library procedure that caused the error,
and correct the argument that is zero or negative.
LONGDST,

unable to include all module names in symbol table

Facility: PATCR Patch Utility
Explanation: When you initialized its symbot the image table could not
accommodate all the module names it found.
User Action: To determine which modules were placed in the symbol table,
enter the PATCH command SHOW MODULE. To make room for the new
modules, enter the PATCH command CANCEL MODULE specifying the
module names whose symbols are no longer required. Then reenter the
PATCH command SET MODULE.
LOOKUPERR,

error looking up 'module-name' in 'library filespec'

Facility: LIBRAR, LIBRARY Command
Explanation: The Librarian could not find the requested module in the MNT,
a VAX RMS error occurred, or there is not enough virtual memory available.
User Action: Reenter the command line specifying an existing module name.
LOSTEXTHDR,

file ('file-id') 'filename' lost extension file header

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that an extension file header is not in
the extension file header chain of any file. The file header is rewritten with
a deleted header, and the blocks allocated to the file header are marked free.
The /CONFIRM qualifier is ignored in this action.
User Action: None.
LOSTHEADEK

file ('file-id') 'filename' not found in a directory

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility found that the specified file is not cataloged
in a directory. This error is neither reported nor repaired if any errors
occurred in processing the directories on the volume set.
User Action: If the /CONFIRM qualifier is specified, you may elect to catalog
the file in directory [SYSLOST], or to delete the file. You may want to rerun
the Verify Utility after repairs have been made.

2-353

Messages

LOSTSCAN,

due to directory errors, lost files will not be entered

Facility: VERIFY, Verify Utility
Explanation: The Verify Utility encountered errors during the directory scan
that were reported by previous messages. Therefore, lost files will not be
entered in directory [SYSLOST].
User Action: Refer to the suggested user actions for the previously reported
errors, correct the errors, and reenter the Verify Utility command line.
Low Priority Command Queue Insert Failure
Facility: VAXport, VAXport Driver
Explanation: The VAXport driver attempts to reinitialize the port; after 50
failed attempts, it marks the device off line. This error is caused by a failure
to obtain access to an interlocked queue. Possible sources of the problem are
CI hardware failures or memory, SBI (11/780), CMI (11/750), or BI (8200,
8300, and 8800) contention.
User Action: Call you local DIGITAL field service representitive.
LOWQUOTA,

one or more account quotas may be too low.

Facility: VMSINSTAL, Install Procedures
Explanation: When VMSINSTAL begins an installation, it makes sure that
your process quotas are valid. This check failed.
User Action: You are asked if you want to continue the installation.
DIGITAL recommends that you correct this situation before continuing.
LRL _MISS,

LRL must be specified

Facility: SORT, Sort/Merge Utility
Explanation: If a record I/O interface subroutine package is selected, the
longest record length (LRL) must be passed to SORT in the call.
User Action: Specify the LRL.
LSTERR,

error generating listing file

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

writing listing file

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

listing file SYSUAF.LIS complete

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

2-354

Messages

LSTTOTBK,

device 'device-name' contains a total of 'number' blocks; 'number'
defective blocks detected

Facility: BAD, Bad Block Locator Utility
Explanation: This informational message details the number of bad blocks.
User Action: None.

LTC, line too complicated: 'string'
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: There is excessive use of boldface, underlining, overstriking,
and hyphenation on the line.
User Action: Simplify the line.

LUNALRFRE,

logical unit number already free

Facility: LIB, Library Facility
Explanation: A call is made to LIB$GET_LUN to free a logical unit number
that is not allocated.
User Action: Ensure that you use the correct logical unit number in the call
to LIG$GET_LUN.

LUNRESSYS,

logical unit number reserved to system

Facility: LIB, Library Facility
Explanation: A call is made to LIB$GET_LUN to reserve an invalid logical
unit number. The range for logical unit numbers is 100 to 119.
User Action: Retry the operation specifying a valid logical unit number.

2-355

Reader's Comments

VMS System Messages
and Recovery Procedures
Reference Manual: Part I
AA-LA 17 A-TE

Please use this postage-paid form to comment on this manual. If you require a written reply to a software
problem and are eligible to receive one under Software Performance Report (SPR) service, submit your
comments on an SPR form.
Thank you for your assistance.

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

Excellent

Good

Fair

Poor

D
D
D
D
D
D
D
D

I would like to see more /less

What I like best about this manual is

What I like least about this manual is

I found the following errors in this manual:
Page

Description

Additional comments or suggestions to improve this manual:

I am using Version ___ of the software this manual describes.

Name/Title

Dept.

Company

Date

Mailing Address
Phone

- - Do Not Tear - Fold Here and Tape

-------------------[lllr--------------No Postage

mamnoma™

~:~=j~=~

in the
United States

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

DIGIT AL EQUIPMENT CORPORATION
Corporate User Publications-Spit Brook
ZK01-3/J35 110 SPIT BROOK ROAD
NASHUA, NH 03062-9987

111 ..... 11.11 .... 11 .... 1.11.1 .. 1.1 .. 1•• 1.1 ••• 1.11 .. 1
- - Do Not Tear - Fold Here - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

I
I

I
I
I
I

I
I
I
I
I
I
I

Reader's Comments

VMS System Messages
and Recovery Procedures
Reference Manual: Part I
AA-LA 17 A-TE

Excellent

Good

Fair

Poor

D
D
D
D
D
D
D
D

D
D
D

D
D
0

D
D
D

D
D
D
D
D

D
D

I would like to see more /less

What I like best about this manual is

What I like least about this manual is

I found the following errors in this manual:
Page

Description

Additional comments or suggestions to improve this manual:

I am using Version _ _ _ of the software this manual describes.

Name/Title

Dept.
Date

Company
Mailing Address
Phone

- - Do Not Tear - Fold Here and Tape

-------------------[lllr--------------No Postage

mnmnoma™

~;~=~=~y
in the
United States

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

DIGIT AL EQUIPMENT CORPORATION
Corporate User Publications-Spit Brook
ZK01-3/J35 110 SPIT BROOK ROAD
NASHUA, NH 03062-9987

111 ..... 11.11 .... 11 .... 1.11.1 .. 1.1 .. 1•• 1.1 ... 1.11 .. 1
- - Do Not Tear - Fold Here - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -