Digital PDFs

AA-5284D-TC

March 1984

216 pages

Original

85MB

view download

OCR Version

38MB

view download

Document:	RT-11 System Message Manual
Order Number:	AA-5284D-TC
Revision:	0
Pages:	216
Original Filename:

OCR Text

RT-11

System Message Manual
AA-5284D-TC

March 1983

This manual is for all RT-11 users. It provides a summary of error
conditions that may occur during system use, along with recommended
recovery procedures. This manual supersedes the RT-117 System Mes-

sage Manual, Order No. AA-5284C-TC.

This manual contains Update Notice 1, AD-5284D-T1.

Operating System:

Software:

RT-11 Version 5.1

FORTRAN IV Version 2.5
BASIC—-11 Version 2.0

To order additional documents from within DIGITAL, contact the Software Distribution
Center, Northboro, Massachusetts 01532.
To order additional documents from outside DIGITAL, refer to the instructions at the back
of this document.

digital equipment corporation - maynard, massachusetts

First Printing, March 1980

Updated, March 1981
Revised, March 1983

Updated, July 1984

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

ment.

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 or its affiliated companies.

Printed in U.S.A.

A postage-paid READER'S COMMENTS form is included on the last page of this

document. Your comments will assist us in preparing future documentation.
The following are trademarks of Digital Equipment Corporation:

DEC
DECmate

dlilgliltlall

MASSBUS
PDP

DECsystem—10

RT-11
UNIBUS

P/OS

DECSYSTEM-20

VAX

Professional

DECUS

VMS

Rainbow

DECwriter
DIBOL

RSTS
RSX

M33200

Work Processor

Contents
Page

1.0

Using the RT-11 System Message Manual . . . . . . . . . ... .. .. 1

1.1
1.2
2.0

Video Terminals . . .
Hard-Copy Terminals
Display Processor . .
Line Printers . . . .
Magtapes . . . . . .
Disks . . . . . . .

.
.
.
.
.

. . . . . . . . ... ... ... 5
. . . . . . .. ... ... .... 5
. . . . . . ... 5
. . .. e
e e e e e e e e e 6
..o oo
e
e
e e 6
e
e e e e
e 6

Using Memory More Effectively . . . . . . . . . . .. 9
Decreasing Program Size. . . . . . . . . . . . . .. 10

System Failures . . . . . . . . . . . . .. ..o

4.1
4.2

Failures That Cause Return to Keyboard Monitor . . . . . . .
Failures That Cause Monitor Halts. . . . . . . . . . . . . ..

12
12

4.2.1
4.2.2
4.2.3

Base-Line Monitor Halts . . . . . . . . . . . . . ..
Single-Job Monitor Halts. . . . . . . . . . . .. ..
Foreground/Background and Extended Memory
Monitor Halts . . . . . . . . . . . . . . ... ...
USR Swapping . . . . . . . . . . . . . . .. ...
Stack Overflow. . . . . . . . . . . . .. ... ...

13
14

Failures That Cause Program Looping . . . . . . . . . . . ..

4.3.1
4.3.2

Base-Line and Single-Job Monitor Looping . . . . . .
Foreground/Background and Extended Memory

Monitor Looping . . . . . . . . . .

19
20

4.2.4
4.2.5

4.3

4.3.3

. . .. ... ..
Handler Looping . . . . . . . . . . . . . . ... ..

FORTRAN IV Messages . . . . . . . . « v v v v v v v v v

5.1
5.2
6.0

.
.
.
.
.

Enlarging Storage Space. . . . . . . . . .. ..o 9
Increasing Memory Resources . . . . . . . . . . . . .. . ... 9
3.2.1
3.2.2

5.0

.
.
.
.
.

Increasing Storage and Memory Resources . . . . . . . . . . . . . . .. 9

3.1
3.2

4.0

e e e e e 2
o o 3

Hard Error Conditions. . . . . . . . . . . . . . . . oo 5

2.1
2.2
2.3
2.4
2.5
2.6
3.0

Order of Messages . . . . . . . . . . . .. .. e
Format of Messages . . . . . . . . . . . . .«

Special Information About FORTRAN IV Messages. . . . . . . 21
List of FORTRAN IV Messages . . . . . . . . . . . . . ... 22

BASIC-11 Messages . . . . . . . v v v v v v vt
6.1
6.2
6.3

15
17
17

e e e e

e 45

Description of BASIC-11 Messages. . . . . . . . . . . . . .. 45
Reducing the Size of Your BASIC-11 Program . . . . . . . . . 45
List of BASIC-11 Messages . . . . . . . . . . . « « . . ... 46

iii

7.0

System Messages
7.1
7.2
7.3

8.0

9.2

9.3

List of System Messages .

...

i 155

List of MACRO-11 Messages.

Editor Messages .
9.1

Special Information About System Messages . . . . . . . .
Professional 300 Series Bootstrap Software Error Messages.

MACRO-11 Messages .
8.1

9.0

.. 155

... 161

EDIT Messages

...e

e 161

9.1.1

Special Information About EDIT Messages .

9.1.2

List of EDIT Messages .

... 161

KED Messages.

...

9.2.1

Special Information About KED Messages

9.2.2

List of KED Messages

Single-Line Editor Messages .

. 161

... 164
.

... 165

.. 182

...

... 3

. 164

Table
1-1

Version 5.1, July 1984

Error Severity Levels

1.0

Using the RT-11 System Message Manual
This manual lists the diagnostic messages that RT-11 Version 5 can produce. The messages for FORTRAN IV, for single-user BASIC-11, and for

the editors (EDIT, KED, and the single-line editor) are also included. Each
message appears here in the same form as on your display terminal or
hard-copy terminal listing. When you receive a message, look it up in the
appropriate section, read the short explanation about the reason for the
message, and apply the remedies that are described. Section 5.0 lists messages for FORTRAN 1V, and Section 6.0 lists messages for single-user
BASIC—11. Section 7.0 contains messages for components of the RT-11
operating system. Section 8.0 contains messages for the MACRO-11 assembler. Section 9.0 lists the messages for EDIT, KED, and the single-line
editor.

RT-11 Version 5 provides keyboard monitor commands that automatically
call component parts of RT-11 into service for you. The keyboard monitor
commands are English-language words that are easy to recall. These commands allow you to use the services of different monitors and utility pro-

grams, such as PIP, without running them. Therefore, you may see messages from parts of RT-11 that you have not explicitly called into service.

Both the keyboard monitor command and the utility command for the same
operation will display the same error message if an error is detected. Whatever the case, when you see a message that is not from FORTRAN 1V,
BASIC-11, or one of the editors, look it up in the System Messages or
MACRO-11 Messages section. You may use either keyboard monitor commands or system utility commands to recover from error conditions. Both
are described. The RT-11 System User’s Guide contains a list of keyboard
monitor commands; the RT-11 System Utilities Manual describes associated system program commands.

Some error messages describe error conditions that you cannot resolve.
When you receive a message of this type, you should submit a Software
Performance Report (SPR) to DIGITAL. An SPR is a form that customers

who are in-warranty or have purchased support services can use to report

faults in the software and to suggest product improvements. In this manual, the abbreviation SPR means Software Performance Report.

Before using this manual, read the next two sections thoroughly. Section
1.1 describes how to find messages in the different sections of this manual.
Section 1.2 describes the format of error messages from RT-11.
Several messages from FORTRAN IV, BASIC-11, the RT-11 system, and
the editors pertain to hardware problems and to cases when external stor-

age space or memory is not adequate for the work you are trying to do.
Section 2.0, Hard Error Conditions, summarizes the most common problems with hardware.

RT-11 System Message Manual

Section 3.0, Increasing Storage and Memory Resources, provides useful
guidelines to follow when you have exhausted the resources of your system.

Section 4.0, System Failures, presents guidelines and instructions for both

experienced system programmers and less experienced users who are diag-

nosing the causes of system failures.

1.1

Order of Messages

Within the FORTRAN IV, BASIC-11, System, MACRO-11, and Editor
sections, the messages are in alphabetical order. This manual uses two
special conventions to alphabetize messages that contain certain special
characters and general references to your programs and commands.
Eight general references appear in various messages and stand for specific

names or values that are copied directly from the work you are doing. They
have not been used for alphabetizing. They are:

Hokokok

A label, name, or value that FORTRAN IV copies
into messages from the FORTRAN IV programs you

are using.

A specific command option that is copied into messages from commands you have typed.

AAAAAA

A label or name that RT-11 copies into messages
from the programs you are using.

A single character that RT-11 fills in — usually the

single-letter abbreviation for a file or command op-

tion.

'DEV:FILNAM.TYP

A file specification that RT-11 copies from one of

your commands.

MMMMMM
NNNNNN

Specific values that RT-11 reports as parts of certain messages — usually count totals, addresses, or
offsets that are current at the time of the message.
A single digit that RT-11 fills in — usually the unit

number in a device specification.

The second alphabetizing convention this manual uses is as follows:
With general references ignored, the first digit or letter in the error
message has been used for alphabetizing. For example, the following

error message is alphabetized using the letter e; the characters “<>"
~ are ignored:

¢EDIT-F-"<>” error; no command(s) executed
Therefore, if you have trouble finding a message in this manual, review the

following procedure:

RT-11 System Message Manual

Identify the message’s origin — this manual contains messages for only
the FORTRAN IV and BASIC-11 languages, the RT-11 operating system, the MACRO-11 assembler, and the RT-11 editors. Consult other
documentation about messages from other programs.

Ignore any special characters, such as a question mark (?) or a quotation mark ().

Ignore any number or name in the message that is specific to your
program or files.

Look up the message under the characters that remain.

1.2

Format of RT-11 System and MACRO-11 Messages

In this manual, each RT-11 system message appears in the same form as
on your display terminal and in your hard-copy terminal listings. The messages appear in the following form:
¢Prog—s—Message Text

The message text is prefixed by the name of the system program (Prog) that
issued the message. The program name is followed by a code (s) that indicates the severity of the error. RT-11 responds to error conditions based on

the level of severity indicated by the code.
Table 1-1:
Level

Information

Error Severity Levels
Severity Code

Effect

Execution continues. The program detected a
condition that you should be informed of. The
message appears at the terminal or in the list-

ing file. The condition may affect execution at a
later time and may require future action.

Warning

Execution continues. The program detected a
condition that may cause errors in execution.

Corrective action may be necessary. The message appears at the terminal or in the listing
file.

Error

Execution may terminate. The program detected an error that will cause other errors during execution. Corrective action is necessary.
The message appears at the terminal or in the
listing file.

Fatal/Severe

Execution terminates. The program detected a
serious error. You must enter another command
to continue processing. The message appears at

the terminal or in the listing file.

Unconditional
Abort

Execution terminates. An extremely serious error occurred that prevents further processing.

RT-11 System Message Manual

You can use the monitor SET command to change the effect of the severity
level on the system’s response. In particular, these settings affect the execu-

tion of indirect command files. Refer to the RT—11 System User’s Guide for

a description of the SET ERROR command.

In addition to the error message format described above, RT-11 Indirect |

Control File Processor (IND) messages provide additional information.
These messages appear in two categories: errors that can occur when IND
processes the directives in a control file, and errors that can occur during
data input/output transfers.
The format of the control file error messages is the same as the format that

appears above, but IND also prints the line in the control file that caused
the error. Control file error messages appear in the following form:
?Prog—s—Message Text
- Line In Control File
Input/output error messages include primary and secondary messages. Primary input/output error messages appear in the same format as shown

above, followed by a secondary input/output error message on the line below. The secondary error message helps define the error condition. In addition to the error messages, IND prints the line in the control file that
caused the error. Input/output error messages appear in the following form:
¢Prog—s—Primary Message

Secondary Message
Line In Control File
The FORTRAN IV, BASIC-11, single-line editor, and some KED messages

do not appear in the format described in the preceding paragraphs. See
Section 5.1 for a description of messages from FORTRAN IV and Section
6.1 for a description of messages from BASIC-11. See Section 9.2.1 for a
description of messages from KED and Section 9.3 for a description of messages from the single-line editor.

Professional 300 series bootstrap software error messages are not in the
format described in the preceding paragraphs. See Section 7.2 for the de-

scription of these messages.

Version 5.1, July 1984

RT-11 System Message Manual

2.0

Hard Error Conditions
Hard error conditions are detected by the hardware rather than by the
system software. RT—11 interprets hard errors by printing a short message
on the console terminal. The corrective action that you take depends upon
the type of hard error condition and the devicein use.

Often a hard error condition is simple to correct. The message will indicate

an off-line or write-locked device, for example, and the system may wait
until you correct the problem.

Other hard errors indicate more serious problems such as bad blocks on the
system volume or a malfunction in the hardware itself. You may have to

reinitiate the operation or use another device; in extreme cases, you may
need the advice of a hardware specialist.

Following are descriptions of the devices that can be used with RT-11 and
the hard error conditions that may occur for each device. Corrective actions
follow the error descriptions.

If an error persists after all possible corrective actions have been tried and
all appropriate diagnostics have been run, request the services of a DIGI-

TAL field service representative.

2.1

Video Terminals

Error Conditions

Video terminals do not report any hard error conditions.
Corrective Action

Before using the system, make sure that the terminal is turned on and is on
line. Adjust the scope on a video terminal so that it is bright enough to be
easily read. If you are using a VT100, you should then type CTRL/Q to
resume printing.

2.2

Hard-Copy Terminals

Error Conditions

Hard-copy terminals do not report any hard error conditions.
Corrective Action

Before using the system, make sure that the terminal is turned on, is on
line, and has sufficient paper and a ribbonin good condition.

DECwriter III out of paper: replace paper; turn the terminal off line and
" then on line. (Turning the terminal off and the;n on will also work.) You can
then enter keyboard input.

2.3

Display Processor

Error Conditions

The VT11 display processor does not report any hard error conditions.

RT-11 System Message Manual

Corrective Actions
Make sure that the display is turned on, and adjust the screen so that it is
bright enough to be easily read.

2.4

Line Printers

Error Conditions
No power, no paper, printer drum gate open, off line, over temperature
alarm, or no printer connected to control unit (LP11).
Corrective Actions
Make sure that the printer is turned on and is set on line. Make sure that
the paper is loaded properly. Make sure that a line printer is connected
properly to the controller (LP11).

The system waits while you take corrective action. (You can use the monitor commands SET LP HANG/NOHANG to control the wait feature; see
the RT-11 System User’s Guide.)

2.5

Magtapes

Error Conditions
Cyclical redundancy or parity (checksum) error, record length error, nonexistent memory, write-locked, off line, unit select, or power off.

Corrective Actions
Make sure that all magtape units are powered on — regardless of which
one is in use — set on line, and, if appropriate, write-enabled — insert a

write-ring on the back of a magtape to write-enable it. Make sure that the

tape is correctly mounted on the proper unit and that all units are assigned
different select numbers. Make sure that 7-track tapes are on 7-track
drives; 9-track tapes, on 9-track drives.

For checksum and bad tape errors, retry the operation, using another magtape or drive, if possible, or use the monitor COPY/IGNORE command or
the PIP /G option to ignore input errors while copying.

2.6

Disks

Error Conditions

Off line, write-locked, unit select, parity error, bad blocks, drive not ready,
or volume not formatted.
Corrective Actions
Make sure that the disk drive is set on line and is write-enabled, if appro-

priate. Make sure that the disk is correctly loaded in the proper unit and
that all units are assigned different select numbers. Note the locations of

drive 0 and drive 1. Make sure that a new disk is properly formatted before

you use it.

RT-11 System Message Manual

For parity errors, retry the operation, using another disk or drive, if possible, or use the monitor COPY/IGNORE command or the PIP /G option to

ignore input errors while copying.

Use the monitor INITIALIZE/BADBLOCKS command or the DUP /B option to detect and identify bad blocks on the new devices just received from
the manufacturer. This procedure initializes the device directory, leaving
only FILE.BAD entries in it. This ensures that the system will not try to
access these bad blocks during routine operations.

- Sometimes disks develop bad blocks as a result of use and age. Use the
monitor DIRECTORY/BADBLOCKS command or the DUP /K option to

detect bad blocks on devices that contain data. If the bad blocks fall within
a small area, use the monitor CREATE command or the DUP /C option to
assign a filename with a .BAD file type to the area (see the RT—11 System
User’s Guide). If hard errors are frequent, you can copy the device to a
second device, using the monitor COPY/DEVICE command or the DUP /I
option, and then copy the second device back to the first. This rewrites the

headers and eliminates hard errors. However, if hard errors persist, request
that a hardware maintenance specialist check the head alignment of your
device.

You can also use the FORMAT utility program to reformat devices that
generate hard errors. This procedure destroys the data on the device, which
is then suitable for use with RT-11. Use of FORMAT varies depending on
the type of device, however. See the RT-11 System Ultilities Manual for
information about FORMAT.

RT-11 System Message Manual

3.0

Increasing Storage a

——

mory Resources

Some RT-11 system errors result from insufficient free memory space or
insufficient space on a storage volume. Using one or more of the procedures
listed below may eliminate the problem. If, by using the methods listed
below, you still cannot provide adequate storage or memory resources for
your application, move the application to a system with larger capacities, if
possible.

3.1

Enlarging Storage Space

During an output operation, an error message may indicate that your output volume has insufficient space or, if the volumeis directory-structured,
that thereis not room for a new entry in its directory. Try one or more of
the following corrective actions:
Delete unnecessary files from the output volume, perhaps transferring
them to a backup volume.

Use another volume with more space.
Spemfy an explicit output file size by using the /ALLOCATE optmn or
the size option on the output file specification.

Compress the volume by using the monitor SQUEEZE command or the
DUP /S option. This creates the largest possible empty space on the
- volume by consolidating all the free blocks into one area. It also maximizes efficient use of the directory space.
If directory overflow persists, you can allocate more directory segments
on another volume by using the monitor INITIALIZE/SEGMENTS com-

mand or the DUP /N option and then transferring the files to this vol-

ume. Alternatively, you can create several logical devices on the physical device by using the MOUNT and DISMOUNT commands.
If device overflow persists, use a larger volume — for example, from
RX02 diskette to RK05 disk or from RK05 disk to RL0O2 disk.

If these methods do not provide sufficient space, consult the RT-11 Software Support Manual for more details about the directory structure of devices and the allocation of files.

3.2

Increasing Memory Resources

Many error messages indicate insufficient room in main memory. The following sections present some guidelines to help you use memory efficiently.

3.2.1 Increasing Memory Availability — The following methods make more
memory available without requiring you to redesign the program:
Use the SHOW command to find out which device handlers are loaded;
then use the UNLOAD command to take unnecessary device handlers

out of memory. Do not unload handlers that are needed to run a foreground or system job.

Terminate and unload the foreground program or one or more system

jobs.

Use the single-job or base-line monitor, which requires approximately
one-half the space needed by the foreground/background monitor.

Use the SET USR SWAP command (see the RT-11 System User’s

Guide) to allow USR swapping.

If you create a monitor through system generation, do not add any

features to the monitor that you do not need. Each feature you select
adds to the size of the monitor in memory. In a multiterminal system,
for example, support for each additional terminal you select adds approximately 200(decimal) words to the resident monitor.

3.2.2 Debreasing Program Size — In general, each of the following methods

reduces the maximum amount of memory a program requires at one time.

Use single buffering instead of double buffering.
Use smaller I/0 buffers.
Decrease the maximum number of channels open simultaneously.

Overlay the program or break the code into smaller modules for more

efficient overlaying.

Remove any testing code no longer required.

Use algorithms that require less main memory.
Transfer more data storage to mass storage devices.

Break the program into several programs to permit chaining between

them.

Use the extended memory overlay feature with the extended memory
monitor (XM) so only your program’s root need be resident in low memory. See the RT-11 System Utilities Manual for a description of extended memory overlays.

RT-11 System Message Manual

4.0

System Failures
An RT-11 system failure occurs whenever the currently mnning program
stops unexpectedly or suspends execution, leaving the system in what appears to be a nonfunctioning state. This section should help you to deter-

mine the cause of the system failure and also to distinguish between user

errors and system errors. In this section, text preceded by asterisks (**)is
meant primarily for experienced system programmers who have access to
monitor source listings, but all users should read this text for general
knowledge.

Most system failures fall into one of three categories: those that cause a
return to the keyboard monitor, those that cause a monitor halt, and those
that result in an indefinite program loop. Each is explained in detail below.
While attempting to analyze a system failure, keep in mind any new or
unusual system features, such as user-written device handlers, a complex
application program, or a special-purpose device.
When the system fails, follow this general procedure. Examine the programmer’s console immediately after the failure. Then use the programmer’s console to examine the program counter (PC), the stack pointer (SP),

the general-purpose registers (0 through 5), and certain memory locations.
However, if your processor is an LSI-11, 11/03, 11/23, 11/23 Plus, 11/24, or
11/44, use the on-board ROM ODT to determine the cause of the halt. See
the processor handbook for your PDP-11 for instructions on using ODT, the
programmer’s console, or the ROM ODT.
The first five of the following specific questions are generally useful for
finding the cause of a failure. Later questions are useful in special situations.

1. Did any meamge app sar on the terminal?
2.

Is the processor halted or looping? What is the value of the program
counter in either case?

If the processor is looping, do characters typed on the keyboard echo on
the console? Does CTRL/C have any effect?

Is the halt or loop in a device handler? Are the devices ready to run?
(Check the-line printer, if present.) Has code in the handlers been corrupted?

What are the contents of location 54, which points to the base of
RMON, and location 46, which is the USR load address? The location of
the halt or the loop may be determined by comparing the value of the
program counter with these numbers. If the program counter is higher
than the base of RMON or is within 2K words (010000 bytes, octal) of
the start of the USR, the halt or loop occurredin the monitor, and the
difference between the numbers gives the offset into the monitor code.

What is the value of the stack pointer and the first several elements in
the stack? Has the stack overflowed; is the stack pointer less than 400?

**What are the contents of the registers?

**Has monitor code been corrupted? Determine from a source listing, if
available, the integrity of significant areas in RMON, especially the
area immediately below the monitor stack.

9. **Can you determine from a source listing, if available, what code is
- indicated by the halt or loop?

10. **What are the contents of the monitor data base — for example, the
address of the running job or the addresses of the loaded handlers?

11. **Can the problem be localized to a single job? If so, what are the
contents of the job impure area — the job status word, channel status
words, the queue elements?

12. **Can the problem be localized to a single device? If so, what are the
contents of the handler data, handler queue, and device status regis-

ters?

13. **Has the job impure area in the FB and the XM monitors been cor-

rupted? Has the stack for the foreground or system job overflowed?

4.1

Failures That Cause a Return to Keyboard Monitor

A return to the keyboard monitor has occurred if the monitor’s prompting
character — a dot — is printed at the left margin of the console terminal. If

a monitor message, one beginning with ?MON-, has also been printed,
refer to its meaning and corrective action as listed in Section 7.0.

*+If only the monitor’s dot — without a message — is printed, an interrupt

through an empty vector to code at location 0 or another unexpected jump

to location 0 is indicated. The following code is stored at location 0:

Loc.

Octal Value

040000

BIC RO,RO

;,TO ENSURE A HARD EXIT

104350

.EXIT

:BACK TO KMON

**Possible causes of this type of error include the following: a spurious
interrupt request appeared, a vector was never filled, a filled vector was not

protected under the FB monitor, an .ASECT was attempted into a protected
vector, an application program was run with an incorrect vector address,

the program has a

JMP or a JSR instruction with an undefined label, or the

program has an RTS instruction with no valid return address on the stack.

4.2

Failures That Cause Monitorfi Halts

Monitor halts occur in high memory above the address in location 54, the

RMON base address pointer. The most common symptoms are the absence
of the monitor prompt and the lack of an echo when you type characters.
When a monitor halt occurs, do not attempt to restart the system by pressing the continue key (CONT) on the processor or by using the micro-ODT

RT-11 System Message Manual

“P” command. You must reboot the system. The following sections describe
the various kinds of halts that occur under the different monitors and the
special problems involved in USR swapping and stack overflow.
NOTE

Each description of a halt or loop in the following sections
includes a symbol name. Use the symbol name to find the
appropriate sections of code in the monitor source listings
that reveal offsets from location 54. If you are working with
the distributed version of RT-11, refer to the link maps on
the distribution kit for accurate offsets. If you created the
monitor you are working with through system generation,
the symbol names described here are accurate, but you must
refer to the link map created by system generation to determine the offsets. Therefore, for any special monitors you generate through system generation, such as a version of FB
with multiterminal support, use the symbols in your link
map to identify the appropriate code.

4.2.1 Base-Line Monitor Halts — The base-line monitor has five explicit
halts. Any other halts that occur may indicate that the monitor code has
been corrupted. If that is the case, check for logic errors in the user program, and reboot the system.

Absolute location 26(octal)

See ?MONmFmPower fail halt.
The monitor executes this halt on power up and power down.
2.

Absolute location 116(octal)

See 2MON-F-Memory error NNNNNN.
The monitor executes this halt when it detects a memory parity error.
3.

Absolute location 246(octal)

The monitor executes this halt if a floating-point interrupt occurs under
a monitor that does not have floating-point support. Programs that use
floating-point instructions must be run under monitors with floatingpoint support. Floating-point support for the BL monitor is available
through system generation.

**Check the symbol DEAD.
The monitor executes this halt when it encounters a hardware error
while reading the KMON or USR from the system device. This halt
indicates a temporary or permanent failure of the controller or the
physical volume. The base-line monitor does not execute this halt when
the system device is write-locked. If the system deviceis write-locked,
the monitor issues the message ?2MON-F-System write error and returns to KMON.

RT-11 System Message Manual

**Check the symbol 7$ in routine COMPLT.

The user set bit 7 in the job status word (absolute location 44) to request
halts on hard errors, and the monitor detected one. Register 5 points to
a queue element, specifically to the pointer to the channel status word.
Register 4 points to the current queue element pointer in the handler.
4.2.2 Single-Job Monitor Halts — The single-job monitor has seven explicit
halts. Some of them are mutually exclusive, however, because they depend
directly on system generation features that you are free to include or exclude. If a halt that is not enabled occurs, the monitor code may be cor-

rupted. Check for logic errors in the user program, and reboot the system.
1.

Absolute location 26(octal)

See MON-F-Power fail halt.
If the message ZMON-F—-Power fail halt is disabled during system generation, this halt is executed on power up and power down.
Absolute location 116(octal)

See ¢MON-F-Memory error NNNNNN.
During system generation, if memory support is not enabled — the
default for the distributed version of the single-job monitor — the monitor executes this halt when it detects a memory parity error. If the
message is enabled, the monitor issues it and returns to KMON.
Absolute location 244(octal)

The monitor executes this halt if a floating-point interrupt occurs under
a monitor that does not have floating-point support. Programs that use
floating-point instructions must be run under monitors with floatingpoint support. Floating-point support is available in the distributed
single-job monitor, as well as through system generation.
**Check the symbol 1$ before TRAPPF.

See !MON-F-Power fail halt.
During system generation, if the message 2MON-F—Power fail halt is
enabled — the default for the distributed version of the single-job
monitor — the monitor executes this halt on power down.

**Check the symbol 2$ in routine CRASHP.
See ZMON-F—-Power fail halt.
During system generation, if the message ZMON-F—-Power fail halt is
enabled — the default for the distributed version of the single-job monitor — the monitor issues the message and executes this halt on power
up.

RT-11 System Message Manual

**Check the symbol DEAD. The message ?MON-F-System read failure
halt precedes this halt only if system I/O messages are enabled during
system generation.

During system generation, if system I/O messages are enabled — the
default for the distributed version of the single-job monitor — the monitor executes a halt in routine CRASHP at symbol 2§ after printing the
message MON-F-System read failure halt. This halt occurs when the
monitor encounters a hardware error while reading the KMON or USR
from the system device. This halt indicates a temporary or permanent
failure in the controller or physical volume. If the system device is
write-locked, the single-job monitor displays the message
?MON-F-System write error and returns to KMON, rather than executing this halt.

**Check the symbol IOEHLT.

The monitor detected a hard I/O error after bit 7 in the job status word
(absolute location 44) was set. Register 5 points to a queue element,
specifically to the pointer to the channel status word. Register 4 points
to the current queue element pointer in the handler.
4.2.3 Foreground/Background and Extended Memory Monitor Halts — The
foreground/background monitor has four explicit halts, but the ones that
can occur for a particular version of the monitor depend on features you
choose or exclude during system generation.

The extended memory monitor has the same halts as the foreground/background monitor, but the offsets into RMON differ for the two monitors.
Make sure that you refer to the appropriate link map to determine the
symbol value (see Note in Section 4.2).

Any other halts that occur may indicate that the monitor code is corrupted.
When that is the case, check for logic errors in the user program, and reboot
the system.

Absolute location 26(octal)

See 2MON-F-Power fail halt.

If the message 2MON-F—-Power fail halt is disabled during system generation, this halt is executed on power up and power down. If the message is enabled, the monitor issues the message and halts.
2.

Absolute location 116(octal)

See 2MON-F-Memory error NNNNNN.

If memory parity support is disabled — the default for the distributed
versions of the monitors — the monitor executes this halt when it detects a memory parity error. The last item in this list of
foreground/background and extended memory monitor halts describes
the monitor action when the message is enabled.

Absolute location 244(octal)
The monitor executes this halt if a floating-point interrupt occurs under
a monitor that does not have floating-point support. Programs that use

floating-point instructions must be run under monitors with floatingpoint support. Floating-point support is included in the distributed
foreground/background monitor and is also available for the extended
memory monitor through system generation.

**Check the symbol SYHALT.

The monitor executes this halt in two general situations. The message
?MON-F-System halt may precede the halt.
a.

If the message MON-F-Power fail halt is enabled — the default
for the distributed version of the foreground/background monitor —
the monitor issues the message and executes this halt on power up.
On power down, the monitor executes this halt, but without supporting the overhead of the message.

The monitor executes this halt when it traps to 4 or 10 or when it
encounters a memory error, but only when it is executing critical

monitor or interrupt code — in interrupt service routines, device

handlers, or selected portions of the monitor. (When the monitor is
not executing critical code, it issues a message — ?MON-F-Memory error NNNNNN,
?MON-F-Trap to 4 NNNNNN, or
¢MON-F-Trap to 10 NNNNNN — aborts the program, and returns
to KMON.)
Check the contents of the stack pointer (register 6). If the contents
are less than 400(octal), stack overflow has caused the trap. Section
4.2.5 has further information about stack overflow.
The address where the trap occurred is at the top of the stack. If

this address is within user code, check for an error in an interrupt
service routine or a device handler. Verify that handlers are not
fetched into areas that will be destroyed by data buffers or overlaid
when the USR swaps. Section 4.2.4 has further information about
USR swapping.

Check for a reference to a nonexistent device. The reference causes
the handler to trap to 4 when it attempts to access the device registers. You can reduce the possibility of this error by deleting from
the system volume all handlers for devices that are not part of your
system.

If the address where the trap occurred is in the monitor, calculate
the corresponding monitor offset by subtracting the contents of lo-

cation 54. Consult a source listing of the monitor and compare the
monitor you are running to the sources. The monitor or data in the
monitor or user region, such as queue elements and channel status
tables, may be corrupted.

RT-11 System Message Manual

Hardware problems that cause bus timeout cause this halt because
they trap to 4. This is extremely rare, however; consider it only as a
last resort.

4.2.4 USR Swapping — Many system failures occur when the USR swaps
over important memory areas, such as device handlers, queue elements,
and completion routines; the latter may occur when you are running FORTRAN IV programs that use SYSLIB calls. One way to detect this type of
failure is to use the SET USR NOSWAP command and to rerun the program — if enough free memory exists. If the failure does not occur again,
USR swapping is probably causing the problem. The USR may be linked
with overlays or with a different bottom address. Make sure that the USR
does not swap over any important areas within the program. See the RT—-11
Programmer’s Reference Manual and the RT-11 Software Support Manual
for details concerning the swapping algorithm.
4.2.5 Stack Overflow — Stack overflow occurs when the stack is pushed
through its low limit. Whether it may be detected depends on the location
of the stack. The normal location for the user background stack is 1000,
with a low limit of 400. Most PDP-11 processors detect stack overflow at
400 and generate a trap to 4. (Some processors — for example, the
PDP-11/03 — do not provide this feature.) If the stack is located elsewhere,
overflow detection is not supported by the RT—-11 system.
Stack overflow is usually a fatal condition. RT-11 treats all detected user
stack overflows as fatal and aborts the offending program. Under the
single-job monitor, the system either halts or prints a monitor fatal error
message, depending on a SYSGEN feature. The foreground/background
monitor aborts the program with the ZMON—-F-Trap to 4 NNNNNN message.

The FORTRAN IV Object Time System may cause user stack overflow
because it uses large amounts of stack space. Extra stack space can be
allocated for background jobs by using LINK/BOTTOM to raise the program base. Extra stack space can be allocated for foreground jobs at link
time by using the :stacksize argument with the LINK/FOREGROUND
command.
|
Monitor stack overflow will generally not occur, since enough stack space is
allocated to handle “worst-case” situations. To determine if the stack overflowed, inspect the contents of the address in the stack pointer minus 2. If
the stack did not overflow, the contents will be 52525(octal), which is the

empty stack pattern. If the stack overflowed, the contents will be something
other than 52525. If it overflowed, you can allocate more stack space by
increasing the value of the conditional STAC$K in your system generated
conditional file and by assembling and linking the monitors again.

If you are using a user-written device handler that requires a large amount
of stack space, allocate stack space within the handler. A register other
than SP should be used to reference the stack.

RT-11 System Message Manual

4.3

Failures That Cause Program Looping

When your system repeats a set of instructions continuously, it is in a loop.
Programmed loops cause the system to wait until a device responds appropriately before resuming operation. However, looping can continue indefinitely if hard errors occur. This section describes causes of indefinite
looping.
Handler loops are the most common. Refer to Section 4.3.3 for further infor- mation about them.

The general method for diagnosing a program loop condition is to disable
any device that generates frequent interrupts (the KW11L clock, for example) and then to single-step through the set of looping instructions to find
the location in memory where the loop occurs. (Refer to the processor handbook for the PDP-11 you are using for instructions on single-stepping.) A
frequent cause of looping is the loss of an interrupt or interrupt enable bit
in a device or terminal interface. If you are familiar with the devices your
program is using, you can examine the device registers to determine if this

is the case.
4.3.1

Base-Line and Single-Job Monitor Looping — There are seven loops in

the base-line and single-job monitors. In four cases the offsets into RMON
are different for the two monitors. Make sure that you refer to the appropriate link map to determine the symbol value (see Note in Section 4.2).

1. **Check the symbol QRESET.

This loop waits for all I/0 to complete before executing an exit or chain.
When the system is in this loop, check the queue elements and channel
status word for outstanding I/O requests, and then examine the appropriate devices to determine why requests are not satisfied.
2.

**Check the symbol WAITDV.
This loop waits for I/O completion on a given channel and is entered
when a .WAIT request is issued. The device that is causing the loop can
be identified by checking register 3, which points to the channel status
table.

**Check the symbol QEWAIT.
This loop waits for a queue element. If an active program waits in this
loop for long periods of time, it is bound by queue elements and should
have its number of queue elements increased with the .QSET program
request. If a program hangs in this loop indefinitely, a device is not
satisfying an I/O request. The device can be identified by checking the
queue elements and channel status tables. Note that a mark time request (MRKT) ties up a queue element until it is complete.

RT-11 System Message Manual

**Check the symbol WAITIO.

This loop waits for I/O completion on a particular channel and register
3 points to the channel status table for the channel. When a program
hangs in this loop, the device on the channel is not satisfying an I/0
request.

**Check the symbol CDFNWT in the USR.

This loop is reached by a .CDFN programmed request and delays execution until all I/O is finished. A bad device can cause programs to hang
in this loop. Examine the queues, channel tables, and device queues to
identify a device that is not satisfying an I/O request, and then examine
the device registers.

**Check the symbol RSTTTW in the USR.

This loop delays a hard reset until console terminal output is finished.
If the system seems to hangin this loop, verify that the console terminal vectors are still pointing into RMON, that the output interrupt is
enabled, and that the console is opemtwe 'vpeCTRL/Q to evoke a
hard reset. Static electricity often clears the input interrupt enable bit.
Although foreground execution mntinuea, the terminal appears inoperative. The absence of the monitor prompt and the lack of an echo after
characters you type indicate this. This is not a loop. Type CTRL/Q to
restart processing.

**Check the symbol RSTIOWin the USR.

This loop is reached by a .SRESET programmed request and delays
execution until all I/0is finished. Use the same procedure as for item 5,
above.

4.3.2 Foreground/Background and Extended Memory Monitor Looping — The
foreground/background monitor has two loops. The extended memory monitor has the same two loops, but they are located at different offsets. Extended memory offsets are shown in parentheses in this section.
1.

**Check the symbol EXRDKM.

When the system encounters a hard error while reading the KMON or
USR, it issues the ?ZMON-F-System read error message. It may then
continuously retry the read operation. If this loop should occur, the
controller is malfunctioning. Halt the processor and try to reboot the
system. If the system does not boot, check the system device for bad
blocks.

**Check the symbol SCHDLR.
This is the scheduler and null job (idle) loop, which the system enters

when no job is runnable. Check the impure areas of all jobs to locate the
cause.

Check the symbol BCNTXT to determine the location of the pointer to
the background impure area. Check the symbol FCNTXT to determine
the location of the pointer to the foreground impure area. Using these
pointers, examine the L.BLOK words (see the RT-11 Software Support

Manual for details), the channel tables, and the queues to determine
why neither job is runnable.

Note that a job can be blocked by a lack of available queue elements
despite the fact that BLOK is zero, because on every significant event,
the job will be run to check for an available queue element. Note also

that the EXIT$ bit in I.BLOK can be set in several different ways —
with the .EXIT, .CDFN, or .SRESET programmed requests, for
example.
4.3.3 Handler Looping — By default, the line printer handler will loop on
hardware errors until the error condition has been removed. The system
will loop through the monitor service code and the handler detection code.
This condition can be changed by using the monitor SET command (see the
RT-11 System User’s Guide). The other supplied handlers use counts to
prevent indefinite retries on a device.

RT-11 System Message Manual

5.0

FORTRAN IV Messages
This section contains error messages displayed by FORTRAN IV. FOR-

TRAN IV error messages are generally clear in specifying the exact nature
of the error. However, if you cannot find the error by reading this section,
refer to the PDP-11 FORTRAN Language Reference Manual.

5.1

Special Information About FORTRAN IV Messages

FORTRAN IV has five groups of messages. Section 5.2 lists them in the

following order.

Fkxkke

Numbered

These messages are from the first compilation phase. They appear on

source listings after the statement towhich they apply, in the form of a
single-letter code (here represented by c). These messages report error
conditions that are easy to identify, such as syntax errors.

These messages are displayed by the FORTRAN IV Object Time Sys-

tem. They appear in the form nn text, where nn is a message number
from 0 through 68. These messages report error conditions that result
from input and output operations, arithmetic operations, and system
|

failures.

Each of these messages is assigned to one of four error classes, described
below. The associated abbreviations are used in this manual to indicate
the classification of the error message.

Class

Abbreviation

Description

The error is detected and the FORTRAN IV

IGNORE

compiler supplies necessary changes. No error message is sent to the terminal. Execution continues.

WARNING

The error message is sent to the terminal
and execution continues.

ERROR:

FATAL

The error message is sent to the terminal

COUNT:n

C:n

The error message is sent to the terminal

and execution is terminated.

and execution continues until the nth occurrence of the error, at which time the error
will be treated as FATAL.

These messages are from the second compilation phase. They appear in
the form In Line nnnn, ERROR: text, where nnnn is the internal sequence number of the statement in question, and text is the description
of the error.

?FORTRAN-

WARNING:

These messages are fatal compiler error messages. They appear in the

form ?FORTRAN-F—text, where text is the specific message you receive.
These messages report hardware error conditions, conditions that may
require rewriting the source program, or compiler errors.

These messages are from the second compilation phase. They appear in

the form In Line nnnn, WARNING: text, where nnnn is the internal
sequence number of the statement in question, and text is the description of the error. These messages report conditions that may cause errors during execution or that may cause incompatibility with the RT-11
FORTRAN 1V compiler.

RT-11 System Message Manual

Note again that some messages can include labels, names, and values from
the program you are running. This manual uses “**** tg indicate run-timespecific information for FORTRAN IV messages and ignores those general
references in alphabetizing.

5.2

List of FORTRAN IV Messages

*****B

Columns 1 through 5 of a continuation line
are not blank. Column 1 of a continuation
line may have a ‘D’, but columns 2 through 5
must be blank. FORTRAN IV ignores the
faulty columns.

Use a blank or a ‘D’ in column 1 and replace
columns 2 through 5 with blanks, if the line
is a genuine continuation line.

**#**C

The line is an invalid continuation line. Com-

Correct the program.

ments cannot be continued, for example, and
the first line of any program unit cannot be a

continuation line. FORTRAN IV ignores the
line.
bt
X

There is no END statement for the program.

FORTRAN IV supplies an END statement
when it detects the end of the file.

Add an END statement to the end of the program.
TM
P

*****H

A Hollerith string or a quoted literal string

Correct and modify the program, if neces-

either is longer than 255 characters or makes
the current statement too long. FORTRAN
IV ignores the statement.

sary, to support the long string properly.

bl|

The line contains a character that is not in
the FORTRAN IV character set, not within a
Hollerith string, or not in a comment. FORTRAN 1V ignores the character.

Make sure that all non-FORTRAN IV characters are either in Hollerith strings or in
comments.

A nonnumeric character is in a statement label. FORTRAN 1V ignores the label.

Use only numeric characters in the statement label.

Fokdkkk]

The line following this warning has more
than 80 characters. Note that each space and
tab is a single character. FORTRAN IV trun-

cates the line to 80 characters.

RT-11 System Message Manual

Shorten the line.

abt

i\ |

The statement has a label that is also used on
an earlier statement. Each statement label
must be unique. FORTRAN IV ignores all

Remove the duplicate label, or change it to a
unique form.

duplicate labels.
dokkkkPpP

The statement has unbalanced parentheses.
FORTRAN 1V ignores it.

Check for typing errors. Match each open
parenthesis with a close parenthesis.

*kkkkG

The statement has a syntax error. FOR-

Correct the syntax in the statement.

TRAN 1V ignores the statement.
*****U

The statement is not valid in FORTRAN IV.
FORTRAN 1V ignores it.

Review the description of the statement you
are trying to use, and recode the statement
correctly.

FORTRAN F or IG

0 Non-FORTRAN error call

This message indicates an error condition not
internal to the FORTRAN IV run-time system, that may have been caused by one of
four situations:

A foreground job using SYSLIB completion routines was not allocated enough
space with the FRUN /BUFFER option
for the initial call to a completion rou-

Check the RT-11 Programmer’s Reference Manual for the formula used to allocate more space.

tine.

Memory was not large enough for the

Under the SJ monitor, a SYSLIB completion routine interrupted another comple-

An assembly-language module linked
with a FORTRAN IV program issued a
TRAP instruction with an error code that
was not recognized by the FORTRAN IV
error handler. (Note that error messages
produced by the FORTRAN IV extensions package contain this message, preceded by a line describing the error in

Use the FB monitor to allow more than

one active completion routine (see the
RT-11 Programmer’s Reference Manual).

tion routine.

Refer to Section 3.0 for information on
how to increase memory space.

background job.

Correct the program logic, if necessary.

more detail.)
1 Integer overflow

During an integer multiplication, division, or
exponentiation operation, the value of the re-

FORTRAN F

Use floating-point notation to correct the program logic.

sult exceeded 32767.

RT-11 System Message Manual

2 Integer zero divide
During an integer mode arithmetic opera-

FORTRAN F

Correct the program logic.

tion, an attempt was made to divide by O.
3 Compiler generated error

FORTRAN F

An attempt was made to execute a FOR-

Consult the program listing generated by the

TRAN IV statement in which the compiler
had previously detected errors.

compiler, if one was requested, and correct
the program for the errors generated at compile time.

4 Computed GOTO out of range
The integer variable or expression in a com-

puted GOTO statement was less than 1 or
greater than the number of statement label

FORTRAN W

Examine the source program and correct the
program logic.

references in the list.
FORTRAN IV passes control to the next executable statement.
FORTRAN C:3

5 Input conversion error
During a formatted input operation, an in-

valid character was detected in an input

Examine the input data and correct the invalid record or the program logic.

field.

FORTRAN IV substitutes a value of O for the
result.
6 Output conversion error

During a formatted output operation, the
value of a particular number could not be

FORTRAN IG

Correct the FORMAT statement to allow a
greater field length.

output in the specified field length without
loss of significant digits.
FORTRAN 1V fills the field with asterisks.
10 Floating overflow

A real value resulting from an arithmetic operation exceeded the largest representable
real number.

FORTRAN C:3

Correct the program logic.

FORTRAN IV substitutes a value of O for the
result.
11 Floating underflow

A real number resulting from an arithmetic
operation was less than the smallest
representable real number.
FORTRAN 1V replaces the real number with

a value of 0.

RT-11 System Message Manual

FORTRAN IG

Correct the program logic.

12 Floating zero divide

During a real-mode arithmetic operation, an
attempt was made to divide by 0.

FORTRAN F
Correct the program logic.

FORTRAN IV sets the operation’s result to 0.
13 Square root of negative number
An attempt was made to calculate the square
root of a negative number.

FORTRAN C:3

Correct the program logic.

FORTRAN IV substitutes a value of O for the
result.
14 Undefined exponentiation operation

An attempt was made to perform an invalid
exponentiation operation. (For example,
-3.**.5 is invalid because the result would be
an imaginary number.)

FORTRAN F
Correct the program logic.

FORTRAN IV sets the operation’s result to 0.
15 Log of zero or negative number

An attempt was made to take the logarithm
of a negative number or 0.

FORTRAN F
Correct the program logic.

FORTRAN 1V sets the operation’s result to 0.
16 Wrong number of arguments

Either a FORTRAN 1V library function or a
system subroutine that checks for such an occurrence was called with an improper number of arguments.
20 Invalid logical unit number

An invalid logical unit number was specified
in an I/O statement.

21 Out of available logical units

An attempt was made to have too many logical units simultaneously open for I/O.

FORTRAN F

Check the format of the particular library
function or system subroutine call, and cor-

rect the call.

FORTRAN F

Correct the statement so that the logical unit
number is an integer within the range 1 to
99.
FORTRAN F
Increase the maximum number of active logi-

cal units — six by default — by recompiling the main program, using the /UNITS option to specify a larger number of available
channels; the valid range is 1 to 15.

22 Input record too long

During an input operation, a record exceeding the maximum record length was encountered.

FORTRAN F
Increase the default maximum record
length — 136(decimal) bytes — by recompiling the main program, using the /RECORD option to specify a larger run-time record buffer; the valid range is 4 to 4095.

RT-11 System Message Manual

23 Hardware I/O error

A hardware error was detected during an I/O
operation.

FORTRAN F

Check the procedures for recovery from hard
error conditions listed in Section 2.0.

24 Attempt to READ/WRITE past end of file
1.

During a sequential write operation, the
space allocated to the file was insuffi-

FORTRAN F
1.

Refer to Section 3.0 for information on
how to increase storage space.

cient.

During a sequential read operation, an
attempt was made to read beyond the
last record of the file.

During a random-access write operation,

Use an END= parameter on a sequential

read.

Correct the programming logic error in

the random-access read operation. Use

either the space allocated to the file was
insufficient or a programming error, such
as an attempt to reference a record number outside the bounds of the file, oc-

the square bracket construction to make
more space available when opening a file

with CALL ASSIGN.

curred during a read operation.
25 Attempt to read after write

An attempt was made to read after writing
on a sequential file.

FORTRAN F

Follow a write operation with a REWIND or

BACKSPACE before performing a read operation, and correct the program logic.

26 Recursive I/0 not allowed

An expression in the I/O list of a WRITE
statement initiated another READ or
WRITE operation. This can happen if a
FUNCTION that performs I/O is referenced
in an expression in a WRITE statement 1/0O

FORTRAN F

Correct the program logic.

list.

FORTRANF

27 Attempt to use device not in system

An attempt was made to access a device that
is not valid for the system being used.

Assign the required logical device name or
change the erroneous statement.

FORTRAN F

28 Open failed for file
1.

The file specified was not found.

Verify that the file name exists as speci-

fied and that FORTRAN IV default unit
numbers are assigned to the devices expected.

FORTRAN IV selected a channel already

Verify that the channel selected is not already in use by an assembler-level or

1n use.

SYSLIB call.
3.

The device did not have enough room for

the file.

26 RT-11 System Message Manual

Refer to Section 3.0 for information on
how to increase storage space.

FORTRAN F

29 No room for device handler

Not enough free memory is available to accommodate a specific device handler.

Move the file to the system device or to a
device whose handler is resident. Refer to
Section 3.0 for information on how to increase memory space. Recompile the FORTRAN
IV
program
with
/NOLINENUMBERS or link with $SHORT.
Use /UNITS to reduce the number of logical
units or /RECORD to reduce the record size
buffer.
FORTRAN F

30 No room for buffers

Not enough free memory is available to set
up the required 1I/O buffers.

Reduce the number of logical units that are
open simultaneously at the time of the error
(/UNITS). Refer to Section 3.0 for information on how to increase memory space. Recompile the FORTRAN IV program with
/NOLINENUMBERS or link with $SHORT.
Use /RECORD to reduce the record size
buffer.
FORTRAN F

31 No available 1/0 channel

More than the maximum number of
input/output channels available to the FORTRAN IV run-time system were requested to
be simultaneously opened for L/O.

Reduce the number of simultaneously open
input/output channels available to the FORTRAN IV run-time system to 15 or fewer.
Try the operation again.

32 Fmtd/unfmtd-random I'O to same file
An attempt was made to perform a combination of formatted/unformatted or random-access I/0 to the same file.

FORTRAN F
Correct the program logic.

FORTRAN F

33 Attempt to read past end of record

An attempt was made to read a larger record
than existed in a file.

Check the construction of the data file; correct the program logic.
FORTRAN F

34 Unfmtd 1/O to TT or LP

An attempt was made to perform an unformatted write operation on the terminal or
line printer.

Assign the logical unit in question to the appropriate device, using the ASSIGN key-

board monitor command, the ASSIGN FORTRAN library routine, or the IASIGN SYSLIB routine.
FORTRAN F

35 Attempt to output to a read only file

An attempt was made to write to a file designated as read-only.

Check the CALL ASSIGN system subroutine
or IASIGN SYSLIB function to make sure
that the correct arguments were used. Check
for a programming error.

RT-11 System Message Manual

36 Bad file specification string

FORTRAN F

The Hollerith, literal string, or array specifying the RT-11 device or file name in the
CALL ASSIGN system subroutine could not
be interpreted.

Check the format of the CALL ASSIGN
statement. If the square bracket construction
is used, an equal sign must follow it.

37 Random access read/write before define file

FORTRAN F

A random-access read or write operation was

Correct the program so that the DEFINE

attempted before a DEFINE FILE operation
was performed.

FILE operation is executed before any ran-

dom-access read or write operation.

FORTRAN F

38 Random I/O not allowed on TT or LP
Random-access I/O was attempted on the terminal or line printer.

Assign the logical unit in question to the appropriate device, using the ASSIGN key-

board monitor command, the ASSIGN FORTRAN library routine, or the IASIGN SYSLIB routine.
39 Record larger than record size in define file

FORTRAN F

A record encountered was larger than that

Shorten the I/0 list or redefine the file speci-

specified in the DEFINE FILE statement for

fying larger records.

a random-access file.
40 Request for a block numbered larger than 65535
An attempt was made to reference an absolute disk block address greater than 65535.

FORTRAN F

Correct the program logic.

41 DEFINE FILE attempted on an open unit

FORTRAN F

While a file was open on a unit, another DEFINE FILE operation was attempted on that

Close the open file before attempting another
DEFINE FILE operation.

unit.

42 Memory overflow compiling object time format

FORTRAN F

The OTS ran out of free memory while scan-

Use a FORMAT statement specification in

ning an array format generated at run time.

compile-time rather than object-time format.

Refer to Section 3.0 for information on how to
increase memory space.

43 Syntax error in object time format

FORTRAN F

The OTS detected a syntax error while
scanning an array format generated at run
time.

Correct the programming error.

44 Second record request in ENCODE/DECODE

FORTRAN F

An attempt was made to use ENCODE and
DECODE statements on more than one rec-

Correct the FORMAT statement associated
with the ENCODE or DECODE statement so

ord.

that it specifies only one record. Verify that
no ‘/ is in the FORMAT statement and that
unexpected format reversion does not occur

(see the PDP-11 FORTRAN Language Reference Manual).

RT-11 System Message Manual

45 Incompatible variable and format types

FORTRAN F

An attempt was made to output a real varia-

Correct the FORMAT statement associated

ble with either an integer field descriptor or
an integer variable with a real field descrip-

with the READ, WRITE, ENCODE, or DE-

CODE statement.

tor.

46 Infinite format loop

The format associated with an I/0O statement
that includes an I/O list had no field descriptors to use in transferring those variables.

Correct the erroneous FORMAT statement.

47 Attempt to store outside partition
In an attempt to store data in a subscripted
variable, the address calculated for the array
element in question did not lie within the
section of memory allocated to the job. The

FORTRAN F

Correct the program logic.

subscript in question was out of bounds. (This

message is issued only when bounds-checking modules have been installed in FORLIB,
that is, FORLIB.V2S.)

FORTRAN F

48 Unit already open

An attempt was made to perform an invalid
operation on an open file.

Close the file before attempting to perform
the operation.
FORTRAN F

49 ENDFILE on random file

An ENDFILE statement specified a unit
number of a file that was currently open as a
random-access file. (ENDFILE applies only
to sequential files.)

Correct the program logic.

50 Keyword value error in OPEN statement

FORTRAN F

An OPEN statement keyword was given an
invalid value.

Correct the OPEN statement so that the
value lies within the following ranges:

INITIALSIZE = -32768 to 32767
EXTENDSIZE
-32768 to 32767

BLOCKSIZE

0 to 32767

51 Inconsistent OPEN/CLOSE specifications

FORTRAN F

The specifications in an OPEN and/or
CLOSE statement have indicated one or

Check the OPEN and CLOSE statements for
consistency.

more of the following:

SCRATCH

file

or
NEW
A
READONLY.

The APPEND command was used with a
NEW, SCRATCH, or READONLY file.

The SAVE or PRINT command was used
with a SCRATCH file.

The DELETE or PRINT command was
used with a READONLY file.

RT-11 System Message Manual

FORTRAN W

59 USR not locked

The FORTRAN IV program is started if the
program was running in the foreground, the
/NOSWAP option was used during compilation, or the USR was swapping — a SET
USR NOSWAP command had not been done.

Reexamine the intent of the /INOSWAP option at compile time, and either compile
without /NOSWAP or issue a SET USR
NOSWAP command before running the program.

FORTRAN F

60 Stack overflowed

The hardware stack overflowed. More stack
space may be required for subprogram calls
and opening of files. Proper traceback is impaired. This message occurs in the back-

Allocate additional space by using the /BOTTOM option at link time. Check for a programming error.

ground only.

FORTRAN F

61 Illegal memory reference

Some type of BUS error, probably an invalid
memory address reference, occurred. (In most
cases, this is the FORTRAN IV equivalent of
the monitor MON-F-Trap to 4 NNNNNN
message.)

If the error occurred within a user-written
assembly-language routine, check for an error in the source code and correct the programming logic. If the error occurred in the
FORTRAN IV extensions package, verify
that the register addresses used in the extensions library correspond to those on the hardware. Verify that the correct FORTRAN 1V
library is being used.

FORTRAN F

62 FORTRAN start fail

The program was loaded into memory but
there was not enough free memory remaining for the OTS to initialize work space and
buffers.

Refer to Section 3.0 for information on how to
increase memory space. Recompile the FORTRAN IV program with /NOLINENUMBERS or link with $SHORT; if running
a foreground job, specify a larger value, using
the FRUN /BUFFER. Refer to the formulas
in the RT-11 Programmer’s Reference Manual.
FORTRAN F

63 Illegal instruction
The program attempted to execute an invalid
instruction — for example, floating-point
arithmetic instruction on a machine with no
floating-point hardware. (This is the FORTRAN IV equivalent of the monitor
¢MON-F-Trap to 10 NNNNNN message.)

If the error occurred within a user-written
assembly-language routine, check for an error in the source code and correct the programming logic. Otherwise, verify that the
correct FORTRAN 1V library is being used.

FORTRAN F

64 Virtual array initialization failure
FORTRAN IV cannot initialize a virtual array in the program. There are four typlcal
causes for this error.

The total storage requirements for VIRTUAL arrays exceed available system
memory.

RT-11 System Message Manual

Reduce VIRTUAL memory requirements
by decreasing the declared size of VIRTUAL arrays. If two programs will be ex-

ecuting under the XM monitor with
PLAS VIRTUAL support, verify that the
total VIRTUAL array requirements for
both programs do not exceed available
memory.

The program attempted PLAS VIRTUAL
array support while running the FB or
the SJ monitor.

Use the XM monitor for PLAS VIRTUAL

The program attempted non-PLAS VIRTUAL array support while running the

Use the SJ or the FB monitor for nonPLAS VIRTUAL array support.

Use the XM monitor and make sure that
the system has EIS hardware when calling for PLAS support.

array support.

XM monitor.

The program called for PLAS support,
but the system does not have EIS hardware.

FORTRAN F

65 Virtual array mapping error

Verify that the subscripts that define the array are within the bounds of the array.

A statement referred to a location outside the
bounds of the extended memory region allocated for VIRTUAL arrays. For example, a
subscript value was out of bounds.

66 Unsupported OPEN/CLOSE keyword or option

An option specified in the OPEN statement,

FORTRAN F

Correct the OPEN statement, using only
those options that are valid for the current
version of FORTRAN IV on your system.

such as EXTEND, is not supported by the
current version of FORTRAN IV.

FORTRAN W

67 Unsupported OPEN/CLOSE keyword or option
An option specified in the OPEN statement is
not supported by the current version of FOR-

Processing continues, but you should correct
the OPEN statement when possible, using
only those options that are valid for the current version of FORTRAN IV on your sys-

TRAN 1V.

tem.

68 Direct access record size error

FORTRAN F

The size of a direct-access record exceeded

Correct the program logic.

32767 double words.

ERROR: ACCESS="'DIRECT’ requires form = ‘unformatted’
FORM =‘FORMATTED’ was specified for a
direct-access file. FORTRAN IV supports
only unformatted direct-access input/output.

Correct the program logic.

ERROR: Adjustable dimensions illegal for array ****
Either an adjustable array was not a dummy
argument in a subprogram or the adjustable
dimensions were not integer dummy arguments in the subprogram. FORTRAN IV uses

FORTRAN

Correct the source program.

only one dimension.

RT-11 System Message Manual

ERROR: Array **** exceeds maximum size

FORTRAN

The storage required for a single array or for
all arrays in the program is more than 32K
words.

clare it with a smaller size and revise the

If the message includes the array name, de-

other program statements that are affected
by the change. Otherwise, check all array
declarations and reduce the total requirement for array storage.
FORTRAN

ERROR: Array exceeds maximum size

The storage required for a single array or for
all arrays in the program is more than 32K
words.

If the message includes the array name, declare it with a smaller size and revise the
other program statements that are affected
by the change. Otherwise, check all array
declarations and reduce the total requirement for array storage.
FORTRAN

ERROR: Array **** has too many dimensions
The array noted in the message has more
than seven dimensions.

Correct the array declaration and other program statements that are affected.

ERROR: **** gttempts to extend COMMON block backwards
While making arrays in COMMON equivalent, an attempt was made to extend COMMON past the recognized beginning of COMMON storage.

FORTRAN

Correct the program logic.

ERROR: COMMON block exceeds maximum size

An attempt was made to allocate more than
32K words to COMMON storage.

Correct the statement in error.

ERROR: Constant in FORMAT statement not in range
An integer constant in the FORMAT statement is not in the valid range, 1 to 255.

FORTRAN

Correct the FORMAT statement.

ERROR: Dangling operator

An operator is missing an operand. For example, the statement I=J + causes this mes-

FORTRAN

FORTRAN
Correct the statement in error.

sage.

ERROR: Defective dotted keyword
A dotted relational operator was not recognized. Two examples of this situation are

Check the spelling and format of relational
operators in the statement, and check all dec-

misplacing a decimal point and typing “EW.’
rather than ‘EQ..

imal points. Correct the statement.

ERROR: DEFINE FILE mode must be ‘U’
The third argument in the DEFINE FILE

statement is not U, for unformatted.

FORTRAN

RT-11 System Message Manual

FORTRAN
Replace the third argument with U.

ERROR: DO terminator **** precedes DO statement
Correct the program logic.
The statement specified as the DO loop ter-

FORTRAN

minator does not appear after the DO statement.

ERROR: Expecting left parenthesis after ****

An array name or function name is not fol-

FORTRAN
Correct the statement.

lowed by a left parenthesis.

ERROR: Expecting left parenthesis after subprogram name
A subroutine name or function name is not
followed by an argument list. Using the same
variable name for both a local variable and a

FORTRAN

Check the statement for typing errors and
name conflicts. Correct any other program
statements that are affected.

subprogram can cause this error.

ERROR: Extra characters at end of statement
Extra characters follow the valid statement.
This error can be caused by a missing comma
or an unintentional continuation character
on the line following the valid statement.

FORTRAN

Check the statement and the following one
for typing errors.

ERROR: Floating constant not in range
A floating constant in an expression is too
close to 0 to be processed.

FORTRAN

Use the constant 0.0, if possible. Correct the
program logic to account for the change, if
necessary.

FORTRAN

ERROR: Illegal adjacent operator

Two operators — such as +, *, and logical
operators — are incorrectly placed next to
each other — for example, I=J + *N.

Correct the statement.

ERROR: Illegal characters in expression

FORTRAN

An invalid character was used in an expres-

Check for typing errors and correct the state-

sion in the statement.

ment.

ERROR: Illegal DO terminator ordering at label ****
DO loops are nested improperly.

ERROR: Illegal DO terminator statement ****
The DO statement terminator is not valid. A
DO statement terminator may not be a
GOTO statement, an arithmetic IF statement, a RETURN statement, or another DO

FORTRAN

Correct the program so that the range of each
inner DO loop is within the range of the
proper outer DO loop.
FORTRAN

Use a valid DO statement terminator, and
change the program logic, if necessary.

statement. A logical IF statement is not a

valid DO terminator if it contains one of the
other invalid terminators.

RT-11 System Message Manual

ERROR: Illegal element in I/O list
The I/O list has a syntax error such as an
incorrect item, expression, or implied DO
specifier.

FORTRAN
Correct the I/O list.

ERROR: Illegal ENCODE/DECODE FORMAT specifier
In the ENCODE or DECODE statement, the
second argument inside the parentheses is an

invalid length specification.

FORTRAN

Correct the format specification by using a
FORMAT statement label or an array name
for the second argument inside the

parentheses.

ERROR: Illegal ENCODE/DECODE length expression
In the ENCODE or DECODE statement, the
first argument inside the parentheses is an
invalid length specification.

Correct the length specification by using an
integer expression for the first argument in-

side the parentheses.

ERROR: Illegal ENCODE/DECODE target
In the ENCODE or DECODE statement, the
third argument inside the parentheses is an
invalid target specification.

FORTRAN

Correct the target specification by using an
array name, an array element, or a variable

name for the third argument inside the
parentheses.

ERROR: Illegal initial value expression in DO statement
The equal sign (=) in the DO statement is
not followed by a valid integer expression.

FORTRAN
Correct the BLOCK DATA subprogram.

ERROR: Illegal statement label reference
The statement contains an invalid label. The
label must be from one to five digits long and
may not contain only zeros.

FORTRAN
Correct the invalid statement label.

ERROR: Illegal statement on logical IF

The logical IF statement contains an invalid
statement. For example, a logical IF state-

FORTRAN

Correct the DO statement.

ERROR: Illegal statement in BLOCK DATA
The BLOCK DATA subprogram contains an
invalid statement. A FORMAT statement or
any executable statement in a BLOCK
DATA subprogram causes this error.

FORTRAN

Correct the IF statement and change the program logic, if necessary.

ment may not contain another logical IF or

DO statement.
ERROR: Illegal subscripts for subprogram argument
An invalid element was used in an array subscript list or in a subprogram argument list.
ERROR: Illegal type for operator

The wrong variable type was used for the operation. For example, an invalid variable
type was used with an exponentiation or logical operator.

RT-11 System Message Manual

FORTRAN

Correct the invalid element in the list.

FORTRAN

Make sure that each variable has the proper
type for the operation FORTRAN IV is to
perform.

ERROR: Illegal usage of or missing left parenthesis
Either a required left parenthesis was omitted or an invalid left parenthesis was used.

FORTRAN

Correct the format of the statement.

For example, a variable reference or constant

was incorrectly followed by a left parenthesis.

FORTRAN

ERROR: Integer overflow

An integer constant or the value of an expression in the statement is outside the
range —32768 to +32767.

Change the constant or expression so that its
value is within the range —32768 to +32767.
Correct the program logic, if necessary.
FORTRAN

ERROR: Invalid complex constant

A complex constant in the statement was im-

Correct the complex constant.

properly formed.

ERROR: Invalid dimensions for array ****
The value used as the dimension of an array

FORTRAN

Correct the value.

is not in the range 1 to 32767.

ERROR: Invalid END= or ERR= keyword
The proper format was not used for an
END = or ERR = specification in the input or

FORTRAN

Check for a typing error in the statement and
correct it.

output statement.

ERROR: Invalid EQUIVALENCE
Either the EQUIVALENCE clause is invalid
or it conflicts with an earlier EQUIVA-

FORTRAN

Correct the program logic.

LENCE.

ERROR: Invalid FORMAT specifier
The format specifier is invalid because it is
neither a FORMAT statement label nor an

FORTRAN

Correct the statement, using a proper format
specifier.

array name.

ERROR: Invalid implicit range specifier
An invalid implicit range specifier was used
in the statement. A nonalphabetic specifier
or a range that is in reverse alphabetic order

FORTRAN

Correct the statement so that the implicit
range specifier indicates alphabetic characters that are in alphabetical order.

causes this error.

FORTRAN

ERROR: Invalid logical unit

A logical unit reference was used that is not
an integer variable or a constant in the range

Correct the statement.

1 to 99.

ERROR: Invalid octal constant
An octal constant is too large or contains an

invalid digit. Octal constants may only have
0 to 7 digits and must be in the range 0 to

FORTRAN

Correct the octal constant.

177777(octal).

RT-11 System Message Manual

ERROR: Invalid optional length specifier
An invalid optional length specifier was used

in the data type declaration. For example,
REAL*4 and REAL*8 are valid, but REAL*6

FORTRAN
Correct the declaration. Use valid length
specifiers.

has an invalid optional length.

ERROR: Invalid Radix—50 constant

FORTRAN

A character in the Radix—50 constant is not
in the Radix—50 character set.

Correct the Radix—50 constant.

ERROR: Invalid subroutine or function name
A CALL statement or a function reference
contains an invalid name. An array name in
a CALL statement would cause this error.

FORTRAN
Check for typing errors, and make sure that
the statement refers to valid names.

ERROR: Invalid target for assignment

The left side of the arithmetic assignment

FORTRAN
Correct the statement.

statement is neither a variable name nor a

reference to an array element.

ERROR: Invalid type specifier

FORTRAN

The statement contains an unrecognizable
data type.

Correct

the

statement,

using

ERROR: Invalid usage of subroutine or function name

A subroutine or a function name was used in
a DIMENSION, COMMON, DATA, EQUIV-

valid

data

types.

FORTRAN

Correct the statement.

ALENCE, or data type declaration statement.

ERROR: Invalid variable name

FORTRAN

A variable name is missing, is invalid because it contains an invalid character, or

Correct the variable name.

does not begin with an alphabetic character.

FORTRAN

ERROR: Label on declarative statement

A label was used on a declaration statement.

Correct the statement by removing the label.

ERROR: Missing ‘TO’ in ASSIGN statement
The label specification in the ASSIGN state-

ment is not followed by the keyword TO.

FORTRAN

Correct the statement.

FORTRAN

ERROR: Missing assignment operator
An equal sign was omitted or misplaced in

the

statement.

For

example,

the

Correct the statement.

invalid

statement I+JJ =K would cause this error.

ERROR: Missing comma
A required comma delimiter was omitted.

RT-11 System Message Manual

FORTRAN
Correct the format of the statement.

ERROR: Missing comma in OPEN or CLOSE keyword list
Two options in an OPEN or a CLOSE keyword list are not separated by a comma.

Correct the statement.

FORTRAN

ERROR: Missing delimiter in expression
The operator required between two operands

FORTRAN

Correct the statement.

in an expression is missing.
FORTRAN

ERROR: Missing expression

A required expression is missing from the
statement. For example, the limit expression
in a DO statement was omitted.

Correct the statement.

FORTRAN

ERROR: Missing label

FORTRAN IV expected a statement label but
could not identify one. For example, in the
statement ASSIGN J TO I, J is not a valid
label reference where the ASSIGN statement

Correct the statement, using valid statement
labels where syntax rules require them.

requires one.

FORTRAN

ERROR: Missing label list after comma

The assigned GOTO statement ends with a

Check for typing errors, and correct the

comma.

statement.

ERROR: Missing left parenthesis after OPEN or CLOSE
The keyword list of the OPEN or the CLOSE
statement is not preceded by a left paren-

FORTRAN

Check for a typing error, and correct the
statement.

thesis.

FORTRAN

ERROR: Missing operator after expression
An expression in the statement was not ter-

Correct the statement.

minated with a command, right parenthesis,
or operator.

FORTRAN

ERROR: Missing quotation mark

In the FIND statement, a single quotation

Correct the FIND statement.

mark () is missing between the logical unit
number and the record number.
FORTRAN

ERROR: Missing right parenthesis
A right parenthesis is out of place or is missing. For example, in the statement
READ(5,100,), the first nonblank character
following the format reference should be a

Correct the statement.

right parenthesis.

ERROR: Missing value for keyword in OPEN or CLOSE statement
A keyword that requires a value was specified without a value.

FORTRAN

Correct the statement.

RT-11 System Message Manual

ERROR: Missing variable
FORTRAN IV expected a variable but could
not find one. For example, in the statement
ASSIGN 100 TO 5, no recognizable variable

FORTRAN
Correct the statement.

name follows TO.

ERROR: Missing variable or constant
There is a comma, parenthesis, or other de-

limiter where FORTRAN IV expected a variable or a constant. For example, in the statement WRITE(), a unit number should follow
the left parenthesis.

FORTRAN

Check the format of the statement and cor-

rect it.

ERROR: Mode of expression must be integer
A required integer variable or an expression
was omitted. For example, one of these is required in the initial, terminal, and increment
parameters of a DO statement.

FORTRAN

Check the format of the statement and cor-

rect it.

ERROR: Modes of variable **** and data item differ
In the DATA statement, the data type of the
variable and an item in its associated data
list do not agree.

FORTRAN

Check the statement for a format error. Verify that the declared or default data type for

the variable is appropriate. Check for a typing error in the variable’s associated data

list.

ERROR: Multiple declaration for variable ****
The variable specified appears in another dimension statement or data type declaration.

FORTRAN

Correct the program logic.

ERROR: Multiple declaration of OPEN or CLOSE keyword
In the OPEN or the CLOSE statement, a
keyword was used more than once.

Remove all incorrect references to the keyword from the statement.

ERROR: OPEN or CLOSE keyword value must be quoted string
A keyword in the statement requires a
quoted string value, but was given an expres-

FORTRAN

Correct the syntax of the statement.

sion value.

ERROR: OPEN or CLOSE statement requires UNIT
The OPEN or the CLOSE statement could
not select the proper logical unit, because the

= specifier

FORTRAN

Add a UNIT = specification statement.

UNIT = specification was omitted.

ERROR: P-SCALE factor not in range -127 to +127
A P-SCALE factor is outside the valid range
-127 to +127.

Correct the statement.

ERROR: Parentheses nested too deeply

Group repeats in the FORTRAN IV statement were nested beyond the eight levels

supported by FORTRAN 1V.

RT-11 System Message Manual

FORTRAN

Revise the FORMAT statement.

FORTRAN
ERROR: Program or block data statement must be first
Verify that these statements, if used, appear
Either a program name statement or a block

data name statement was used, but not as

first in your program.

the first statement.

ERROR: Reference to incorrect type of label ****
The statement refers to a statement of the

wrong type. For example, a READ statement

refers to an executable statement; a GOTO

FORTRAN

Check for a typing error in the label. If the
label is correct, change the program logic.

statement refers to a FORMAT statement.

ERROR: Reference to undefined statement label
Correct the program logic.
A referenced statement label was not defined

FORTRAN

ERROR: Statement must be unlabeled
A label was used on a DATA, SUBROUTINE, FUNCTION, BLOCK DATA, statement function definition, or declarative

FORTRAN

in the program unit.

Remove the label from the statement.

statement.

FORTRAN

ERROR: Statement too complex

An arithmetic statement function has more
than 10 dummy arguments or is too long for
FORTRAN IV to process.

Reduce the dummy argument list to 10 or
fewer. Break long statements into two or
more shorter statements.

FORTRAN
ERROR: Subroutine or function statement must be first
Verify that a SUBROUTINE, FUNCTION,
A SUBROUTINE, FUNCTION, or BLOCK

DATA statement appears in the program

unit, but not as the first statement.

ERROR: Subscript of array **** not in range
A value in an array subscript is larger than
the corresponding dimension of the array.

or BLOCK DATA statement being used in a
program unit is the first statement in that
program unit.

FORTRAN

Correct the program so that no subscript values are calculated or assigned beyond the declared dimensions of any array.

FORTRAN

ERROR: Syntax error

The statement was formatted incorrectly.

Correct the format for the invalid statement.

ERROR: Syntax error in integer or floating constant
The wrong form was used for an integer or a
floating constant. For example, 1.23.45 con-

FORTRAN

Correct the constant.

tains two decimal points.

ERROR: Syntax error in label list
The list of labels for an assigned GOTO or
computed GOTO statement contains an error. The error may have been caused by a
format error in the label list or a label refer-

FORTRAN

Check the format of the label list, and verify
that each label in the list is an executable
statement. Correct the statement.

ence to a statement that is not executable.

RT-11 System Message Manual

ERROR: Target must be array
An

array element referenced in an
ENCODE/DECODE statement does not have

dimensions.

FORTRAN
Check the logic of your program. Make sure
that all arrays have dimensions.

ERROR: Unary operator has too many operands
Two or more operands were used in a statement with an operator that can have only
one operand. For example, .NOT. must have
a single operand.

Check for typing errors, including omitted
operators and omitted parentheses in the
statement. Correct the statement.

ERROR: Unlabeled FORMAT statement

The FORMAT statement does not have a la-

bel.

FORTRAN

Replace columns 1 through 5 with the proper

label.

ERROR: Unrecognized keyword in OPEN or CLOSE statement

The OPEN or the CLOSE statement contains
a keyword that the FORTRAN IV compiler
does not recognize.

FORTRAN

Correct the invalid quoted string value.

ERROR: Usage of variable **** jnvalid
An attempt was made either to use a common variable, an array variable, or a dummy

FORTRAN

Correct typing errors in the OPEN or the
CLOSE statement.

ERROR: Unrecognized value for OPEN or CLOSE keyword

The OPEN or the CLOSE statement contains
a keyword with an invalid quoted string
value — for example, DISPOSE = “SURE”.

FORTRAN

FORTRAN
Correct the program logic.

argument as an EXTERNAL variable or to

place a dummy argument or an external
name in COMMON.
ERROR: Value of constant not in range
1.

An integer constant in the line exceeds

65535, the maximum unsigned value.
2.

The dimension for an array is invalid.

A floating-point constant has an exponent that is too large.

FORTRAN
Correct the statement.

ERROR: Variable **** invalid in adjustable dimension

A variable used as an adjustable dimension
is not an integer dummy argument in the
subprogram unit.

ERROR: Wrong number of operands for binary operator

Only one operand was used in a statement

with an operator that requires two. In the
statement I=*J, for example, the multiplication operator requires two operands.

RT-11 System Message Manual

FORTRAN

Correct the program.

FORTRAN

Correct typing errors in the statement.

FORTRAN

ERROR: Wrong number of subscripts for array ****
An array reference does not have the same

number of subscripts as was specified for the

Correct the array reference error.

array’s dimensions.

?FORTRAN-F-Code generation stack overflow
Simplify complex statements.
A statement in the program is too complex to
process.

2FORTRAN-F-Compiler fatal error, analysis follows
If the analysis includes suggestions for corThe FORTRAN IV compiler malfunctioned.
The summary of the malfunction following
this message includes a partial dump of the
compiler, relevant non-FORTRAN IV messages about the cause of the malfunction, and

recting the malfunction, try them. In any
case, follow the instructions for reporting the
malfunction.

specific instructions.

2FORTRAN-F-Constant subscript stack overflow
Too many constant subscripts are in a pro-

Simplify the statement.

gram statement.

?FORTRAN-F-Device full

The output volume does not have enough
room for the object or listing files.

Increase available space by deleting unneces-

sary files or by using the SQUEEZE command. Otherwise, direct the object or listing
files to another device or use another volume
in the same device. Refer to Section 3.0 for
information on how to increase storage space.

?FORTRAN-F-Dynamic memory overflow
The program unit being compiled cannot be
processed in the available memory space.

Break the program unit into smaller subprograms, or run the program on a larger machine. Refer to Section 3.0 for information on
how to increase memory space.

?FORTRAN-F-Error reading source file
An unrecoverable error occurred while the

compiler was attempting to read a source

Refer to the procedures for recovery from

hard error conditions listed in Section 2.0.

program input file.

?FORTRAN-F-Error writing listing file
1. An unrecoverable error occurred while
the compiler was attempting to write the

Refer to Section 3.0 for information on how to
increase storage space.

listing output file.

2. The output volume does not have enough
room for the listing output file. Refer to
the procedures for recovery from hard error conditions listed in Section 2.0.

RT-11 System Message Manual

?FORTRAN-F-Error writing object file
1.

An unrecoverable error occurred while

the compiler was attempting to write the
object program output file.
2.

Refer to Section 3.0 for information on how to
increase storage space.

The output volume does not have enough
room for the object program output file.

Refer to the procedures for recovery from
hard error conditions listed in Section
2.0.

?FORTRAN-F-File not found
An input file specified in the command string
could not be found on the specified device.

Correct the command string to refer to an ex-

isting file or proper device, or install the

proper volume.

?FORTRAN-F-HELP file not found
The FORTRAN IV HELP file, SY:FORTRA.HLP, does not exist on the system volume.

Copy the file from the FORTRAN IV distribution volume.

?FORTRAN-F-Illegal command
An invalid format was used for the command
string presented to the compiler.

Correct the command string.

?FORTRAN-F-Illegal device
An invalid device was specified in the compiler command string.

Correct the device specification in the command string.

?FORTRAN-F-Illegal value for /x switch
An invalid value was used for the option (/x)
in the command string.

Refer to the PDP-11 FORTRAN Language
Reference Manual for compiler option information.

?FORTRAN-F-Optimizer stack overflow
Either a statement is too complex to process

too

many

common

subexpressions

are

Simplify complex statements.

present in a single basic block of the source
program.

?FORTRAN-F-Subexpression stack overflow
While compiling the program, FORTRAN IV

encountered a statement that may cause the

Simplify complex statements.

run-time stack to overflow at execution time.

?FORTRAN-F-Unknown switch—/x
An invalid option was used in the command

string.

Refer to the PDP-11 FORTRAN Language
Reference Manual for compiler option information.

RT-11 System Message Manual

?FORTRAN-I-AAAAAA Errors: NNNNNN, Warnings: MMMMMM
This message is informational.
FORTRAN IV provides this summary for
each program unit when it completes compilation. AAAAAA is the six-character name of
the program unit. NNNNNN and
MMMMMM are the numbers of errors and
warning conditions found.

WARNING: Loop entry at label **** precludes optimizations
A statement outside the DO loop transfers
control to this statement inside the DO loop.
This is an error if the loop does not have extended range. In any case, FORTRAN IV
does not attempt to optimize the loop.

To permit optimization, change the program
and loop logic so that control does not transfer from outside a DO loop to a labeled statement within a DO loop.

WARNING: Non-standard statement ordering

Program statements were not ordered according to the requirements stated in the PDP-11
FORTRAN Language Reference Manual.
Although the FORTRAN IV compiler rules
for statement ordering are less restrictive
than those covered in the PDP-11 FORTRAN Language Reference Manual (Chapter
7), violating the stricter rules may mean that
programs will not run on other FORTRAN

FORTRAN

To be sure that programs can run on other
FORTRAN compilers, standardize the order
of statements according to the requirements
stated in the PDP-11 FORTRAN Language
Reference Manual.

compilers.

WARNING: Possible modification of ****
A variable that is a control parameter of a
DO loop may possibly be modified by a statement within the DO loop.

WARNING: Variable **** is not word aligned
1. A variable or an array that is not LOGICAL*1 was placed in COMMON after a

FORTRAN

To permit optimization, change the program
logic so that DO loop control parameters are
not changed by statements within their DO
loops.

FORTRAN

This message is a warning.

LOGICAL*1 variable or array.

LOGICAL*1 and non-LOGICAL*1 variables or arrays were treated as equivalents in a program.

Attempts to reference the variables or arrays that are not word-aligned at run
time will cause an error condition.

FORTRAN
WARNING: Variable **** name exceeds size characters
Reduce the number of characters in the variThe FORTRAN IV compiler uses the first six
able name to six or fewer.
FORcharacters of the variable name. Other
over-long
TRAN compilers may consider the

name to be an error.

RT-11 Syatém Message Manual 43

6.0

BASIC-11 Messages
This section describes messages displayed by single-user BASIC-11. See
the BASIC-11 Language Reference Manual for more information about BASIC-11 error conditions.

6.1

Description of BASIC-11 Messages

This section contains both the abbreviated and long forms of messages from
BASIC-11. You can choose to have either the abbreviated or the long forms
of messages appear on your display terminal or hard-copy terminal listing.
See the BASIC—-11/RT-11 Installation Guide and Release Notes for details
on link options.

Each abbreviated message, followed by its long form, is presented in this
section in the following format:

?LFM

?LONG FORM OF MESSAGE

BASIC-11

WorF

The first and second lines of the format contain the abbreviated and long
forms, respectively, of a message from BASIC-11. The messages are presented in alphabetical order of the abbreviated version, which is generally
the first letter of each key word in the message.

The information to the right of the error messages is not displayed on your
video terminal or printed on your hard-copy terminal. This information
indicates that the BASIC-11 processor displayed the message and gives the
severity code for the condition the error message reports. The severity code
W indicates a warning; execution continues, although the program detected
a condition that may cause errors to occur. Corrective action may be necessary at a later time. The severity code F indicates a fatal error; execution
terminates because of the error detected. You must enter another command
to continue processing.

6.2

Reducing the Size of Your BASIC-11 Program

Some BASIC-11 errors occur because not enough memory is available. You
can sometimes correct this problem by reducing the size of the BASIC-11
program. In addition to following the suggestions in Section 3.0, you can
maximize space availability in the following ways:

Eliminate or reduce unnecesaary items, such as REMARK statements,
long error messages, and optional keywords — for example, LET.
Make maximum use of multiple statement lines.

Make efficient use of program loops, subroutines, and user-defined functions.

Split large programs into several smaller programs by using the
CHAIN or OVERLAY statements.

RT-11 System Message Manual

Reduce the size of arrays in memory to the size required, using the DIM
statement.

Use virtual array files for arrays that are too large to fit into memory.
Reduce the number of files simultaneously open by opening a file just
before it is needed and closing it immediately after its last use.
After you delete program lines, store the program with the SAVE command and restore it with the OLD command to further optimize program memory requirements.

6.3

List of BASIC-11 Messages

?ARG
?ARGUMENT ERROR
Arguments in a function do not match — in
number, range, or type — the arguments defined for the function.

?ATL
?ARRAYS TOO LARGE
Not enough memory is available for the arrays specified in the DIM statements.

?BDR
?BAD DATA READ
The wrong data type was specified for data
items to be used as input from a DATA statement or from a file.
BLG
?BAD LOG
The expression in a LOG or a LOG10 function equals 0 or is negative. BASIC-11 in-

BASIC-11 F

Make sure that the arguments in the function are of the proper type and number and
are in the correct range.

BASIC-11 F

Refer to Section 6.2 for information on how to
reduce the size of a BASIC-11 program.

BASIC-11 F

Make sure that the elements in the data list
are in the format specified in the READ or
INPUT statement.

BASIC-11 W

Correct the program logic, if necessary.

serts a result of 0 and processing continues.

?BRT
?BAD DATA — RETYPE FROM ERROR
The wrong data type was entered in response
to an INPUT statement.

?BSO
?BUFFER STORAGE OVERFLOW
Not enough room is availablein memory for
the file buffer.

RT-11 System Message Manual

BASIC-11 W

Retype the item that caused the error and
execution will continue.

BASIC-11 F

Refer to Section 6.2 for information on how to

reduce the size of a BASIC-11 program.

2CAO

?CHANNEL ALREADY OPEN

The OPEN statement specifies a channel
that is already associated with an open file.

BASIC-11 F

Correct the program logic, specify another
device channel, or eliminate redundant program statements.

2CCP

2CHECKSUM ERROR IN COMPILED PROGRAM
The file produced by the COMPILE command
contains a format error.

BASIC-11 F

Use a copy of the program created by a SAVE
or REPLACE command.

?CIE

?CHANNEL IO ERROR

Opening or closing a channel produced an error.

BASIC-11F

Make sure that the peripheral devices and
their storage media are working correctly.
Check the procedures for recovery from hard
error conditions listed in Section 2.0. This error may have occurred because the file accessed has a length of 0.

2CNO

?CHANNEL NOT OPEN

A PRINT #, PRINT USING #, IF END #, or
CLOSE statement specifies a file number not
associated with an open file.

BASIC-11 F

Use the OPEN statement to assign a file

number before attempting to input or output
data with the file.

2C00

?COMMON OUT OF ORDER
Variables in a common statement of one pro-

gram segment were not defined in the same

sequence and position as those in a common
statement of a previous program segment.

BASIC-11 F

Make sure that the variables to be shared by
programs are listed in the same order in the
COMMON statements of each program.

2CVO

?2CONTROL VARIABLE OUT OF RANGE
The value assigned to the control variable in
either the ON GOTO or the ON GOSUB
statement is not a positive integer in the
range 1 to n, where n represents the number
of branching options following GOTO or

BASIC-11F

Correct the program logic.

GOSUB.

DVO

?DIVISION BY ZERO

An attempt was made to divide a quantity by

BASIC-11 W

Correct the program logic, if necessary.

BASIC-11 substitutes a value of 0 for the result, and processing continues.

RT-11 System Message Manual 47

?EER
?EXPONENTIATION ERROR
An attempt was made to compute the value

A’B, where A<0 and B is not an integer or
B>255. This produces a complex number,
which is not representable in BASIC-11.

BASIC-11 W
Correct the program logic if necessary. Make
sure that A and B are valid values.

This message occurs only if the value of A

was computed.

BASIC-11 substitutes a value of 0 for the result, and execution continues.

?EIE
?EXCESS INPUT IGNORED
More data items than the INPUT statement

requested were input from the terminal.

Excess data items are ignored and processing
continues.

?ENL
?END NOT LAST
The END statement is not the last statement

in a BASIC-11 program.

?ETC
?EXPRESSION TOO COMPLEX
An expression is too complex for BASIC-11

to evaluate in the stack area. This may occur

because parentheses are nested too deeply or
because there are too many complex user-de-

fined functions in the program.

?FAD
?FUNCTION ALREADY DEFINED
The user-defined function was defined by an
earlier statement. BASIC-11 ignores the

new definition and continues to apply the

BASIC-11 W
Make sure that the program logic is clear
about how many data items should be supplied in response to the question mark (?)

prompt.

BASIC-11F
The line number of the END statement must
be the highest line number in the program,
since any lines numbered higher than the
END statement are not executed. Correct the
program.

BASIC-11F

The degree of complexity that produces this

error varies according to the amount of space

available in the stack at the time. Break the
statement into several simpler ones.

BASIC-11 F
Change conflicting function definitions so
that each function is defined only once.

earliest one.

?FNF
?FILE NOT FOUND
BASIC-11 could not find the requested file

on the specified device.

48 RT-11 Syatem Message Manual

BASIC-11 F

Check for a typing error in the command
line. Verify that the device, file name, and
file type exist as specified.

BASIC-11 W

The absolute value of the result of a
computation is greater than the largest
stored by
be
can
that
number

Correct the program logic, if necessary.

BASIC-11 — approximately 10°38.

BASIC-11 substitutes a value of 0 for the result, and processing continues.

FSV

?NESTED FOR STATEMENTS WITH SAME CONTROL VARIABLE
Nested FOR statements of the form FOR variable = expression 1 TO expression 2 STEP
- expression 3 used the same variable to control execution.

Correct the program logic; for example, if
nested FOR statements occur, use I for the
first control variable and T or I2 for the second.

FTS
?FILE TOO SHORT

The sequential file space allocated to an output file is inadequate. The file is not closed
and all data is lost.

BASIC-11 F

Use another device or make more space
available. If the error occurs in a data file,
specify a larger FILESIZE. If the error occurs
in a program file, delete unused files with the
UNSAVE command.

?FUN

BASIC-11 W

?FLOATING UNDERFLOW

The absolute value of the result of a
computation is less than the smallest
by
stored
be
can
that
number

BASIC-11 F

Correct the program logic, if necessary.

BASIC-11 — approximately 10°-38.

BASIC-11 substitutes a value of 0 for the result, and processing continues.

?FWN

BASIC-11 F

?FOR WITHOUT NEXT

The program contains a FOR statement with-

out a corresponding NEXT statement to terminate the loop.

Make sure that each FOR-NEXT loop in the
program is terminated by a NEXT statement.

?2ICN

BASIC-11 F

?ILLEGAL CHANNEL NUMBER

Either the file number specified is not in the

Correct the erroneous statement.

range 1 to 255 or the IF END statement specifies a file on a terminal.
?IDM

BASIC-11 F

?ILLEGAL DIM

A subscript in a DIM or COMMON statement is not an integer, more than one set of
dimensions was specified for an array, or an
array has more than two dimensions.

Correct the syntax of the dimension statement.

RT-11 System Message Manual

2IEF
?ILLEGAL END OF FILE IN COMPILED FILE
The file produced by the COMPILE command
contains a format error.

BASIC-11 F

Use a copy of the program created by a SAVE
or REPLACE command.

?2IFL
2ILLEGAL FILE LENGTH
An

invalid

value

was

supplied to the
FILESIZE option in an OPEN statement.

BASIC-11 F

Refer to the BASIC-11/RT-11 User’s Guide
for information on the valid range for
FILESIZE.

AFS
?ILLEGAL FILE SPECIFICATION
BASIC-11 could not interpret the file definition statements as entered because the character string used does not define a valid file

specification.

BASIC-11 F
Refer to the BASIC-11 Language Reference
Manual for the correct format of the virtual
memory file OPEN statement.

AID
?ILLEGAL I/0 DIRECTION

An attempt was made to output to an input
file or to input from an output file.

BASIC-11F

Verify that the proper device and file specifications were entered in the OPEN statements.

M
?ILLEGAL IN IMMEDIATE MODE
An attempt was made to execute an INPUT
statement while in immediate mode.

?INS
?INCONSISTENT NUMBER OF SUBSCRIPTS

A subscripted variable was referenced inconsistently with the definition of the array in
the DIM statement. For example, of two sub-

BASIC-11 F

Enter the statement in a program line, fol-

lowed by a STOP, and execute the statement
with an immediate-mode GOTO statement.

BASIC-11 F

Correct the number of subscripts in the DIM
statement or in the reference line.

scripts in the DIM statement, only one is in
the reference line, or one subscript is in the

DIM statement and two are in the reference
line.

210V
?INTEGER OVERFLOW
An integer variable was assigned a value
greater than + 32767 or less than —-32768, or
an integer expression produced a result that

exceeds this range.
BASIC-11 substitutes a value of 0 for the result, and processing continues.

RT-11 System Message Manual

BASIC-11 W

Change the variable or expression to floating-point format.

7ISE

?INPUT STRING ERROR

A string entered in response to an INPUT
statement begins with a single or a double
quotation mark, but is not terminated by a

BASIC-11 W

Correct the INPUT string, if necessary.

matching quotation mark.

BASIC-11 assigns to the string all the characters between the initial quote and the line
terminator; execution continues.

?LTL

?LINE TOO LONG

The line typed is longer than 132 characters.
The line buffer overflows and the line is ignored.

BASIC-11 W

Either break the line into two or more lines
or, if reading from a file, make sure that the
file contains only valid BASIC-11 program
lines.

"MSP

?MISSING SUBPROGRAM

A CALL statement specifies a nonexistent
routine name.

BASIC-11 F

Verify that the subprogram requested exists
as specified, that its name is typed correctly,
and that it does not contain any logical errors.

?NER

?NOT ENOUGH ROOM

Not enough memory is available for the
FILESIZE specified.

BASIC-11 F

Refer to Section 6.2 for information on how to
reduce the size of a BASIC-11 program.

?NGS

INEGATIVE SQUARE ROOT

An expression in the square root function has

BASIC-11 W

Correct the program logic, if necessary.

a negative value.

BASIC—-11 substitutes a value of 0 for the re-

sult, and processing continues.
?NRC

?NO ROOM FOR CALL

Not enough memory is available to process

the CALL statement.

BASIC-11 F

Refer to Section 6.2 for information on how to
reduce the size of a BASIC-11 program.

INSM

NUMBERS AND STRINGS MIXED

String and numeric variables are either used
in the same expression or set equal to each
other, as in A$=2.

BASIC-11 F

Make sure that numeric expressions are assigned to numeric variables and that string
expressions are assigned to string

variables — for example,

A=2 and A$="2".

RT-11 System Message Manual 51

’NWF
?NEXT WITHOUT FOR
A NEXT statement was used without a corresponding FOR statement, or control was

transferred into the middle of a loop.

BASIC-11 F

Make sure that each loop begins with a FOR
statement and ends with a NEXT statement.

Make sure that FOR-NEXT loops are entered
only by executing the FOR statement.

200D
20UT OF DATA
A

READ

statement

BASIC-11 F
requested

additional
data, but the data list is exhausted.

Add data items or reuse data by executing
the RESTORE statement.

?PRU
?PRINT USING ERROR
1.

In the PRINT USING

BASIC-11 F
statement, the for-

mat specification is not a valid string, is

Correct the PRINT USING statement.

null, or does not contain at least one
valid field.
2.

An attempt was made to print a numeric
value in a string field, a string value in a

numeric field, or a negative number in a
floating asterisk or a floating dollar sign

field that does not also specify a trailing
minus sign.
3.

The items in the list of strings to be
printed are not separated by commas or
semicolons.

?PTB
?PROGRAM TOO BIG
The line just entered caused the program to

exceed the user memory area.

BASIC-11F

Refer to Section 6.2 for information on how to
reduce the size of a BASIC-11 program.

?RES
?RESEQUENCE ERROR |
An invalid optional argument was supplied

to the RESEQ command.

BASIC-11F
Make sure that the arguments are valid
numbers for the old starting line number,
new starting line number, and interval.

?RPL
?USE REPLACE

A file name already associated with an existing file was used in saving a program. The
operation does not occur and the original file

is not disturbed.

RT-11 System Message Manual

BASIC-11 F

Use either a different name or the REPLACE

command.

RWG

?RETURN WITHOUT GOSUB

A RETURN statement was encountered before its corresponding GOSUB statement.

BASIC-11F

Check the program logic for correct branching instructions. Transfer control to a subroutine only by executing a GOSUB or a ON
GOSUB statement.

?SOB

?SUBSCRIPT OUT OF BOUNDS
The subscript computed is less than O,

greater than 32767, or outside the bounds de-

BASIC-11 F

Make sure that array subscripts fall within
the valid range.

fined in the DIM statement.

7SSO

?STRING STORAGE OVERFLOW

Memory does not have enough room to store
all the strings used in the program.

?STL

?STRING TOO LONG

The length of a string in a statement exceeds

BASIC-11 F

Refer to Section 6.2 for information on how to
reduce the size of a BASIC-11 program.

BASIC-11F

Split the string into smaller strings.

255 characters.

?SUB

?SUBSTITUTE ERROR

Either the second delimiter was omitted from
between the strings in the SUB command or
the command created an immediate-mode

BASIC-11 F

Check for typing errors and enter the SUB

command again.

statement.

?SYN

?SYNTAX ERROR

The program encountered an unrecognizable
statement. Common examples of syntax er-

rors are misspelled commands, unmatched
parentheses, and other typographical errors.
The wrong number of arguments or an invalid delimiter in a function can also cause

BASIC-11 F

Check for a typing error. Correct the pro-

gram statement.

this error.

?TIC

?TOO MANY ITEMS IN COMMON

The number of items specified in COMMON
exceeds the limit of 255.

BASIC-11 F

Reduce the number of items in COMMON either by converting individual variables to elements of an array or by passing fewer items
to the next program segment.

RT-11 System Message Manual

?TLT
?LINE TOO LONG TO TRANSLATE

The line just entered exceeds the area available for translation; input strings are translated as they are entered.

BASIC-11 F
BASIC-11 ignores the line. Break the line
into two lines. If reading from a file, make
sure that the file contains only valid BASIC—11 program lines.

TMG
?TOO MANY GOSUBS

GOSUBs are nested too deeply.

BASIC-11 F

Restrict GOSUB nesting to 20 levels.

UAC
?UNDIMENSIONED ARRAY IN CALL

The first reference to an array without dimensions appears in a CALL statement.

BASIC-11 F
Assign array dimensions with the DIM statement.

?UFN
?UNDEFINED FUNCTION
The function called is not defined by the program or was not loaded with BASIC-11. A
function is defined only after it has been exe-

BASIC-11F

Check all function calls in the statement for
correct spelling.

cuted or chained to. A user-defined function

cannot be defined by an immediate-mode
statement. Define all undefined functions in
the program.
?ULN

?UNDEFINED LINE NUMBER
The line number specified in an IF, GOTO,

GOSUB, or CHAIN statement does not exist
in the program.

BASIC-11 F

Check the program logic.

VCU
?VIRTUAL ARRAY CHANNEL ALREADY IN USE
The virtual array channel specified in a DIM
statement appears in a previous DIM statement.

RT-11 System Message Manual

BASIC-11 F

Correct the program logic; use a different
channel.

7.0

System Messages

This section contains diagnostic messages from the RT-11 monitor and
system programs. If you cannot determine the location of your error by
reading the explanation for the message in this section, see the R T-11
System User’s Guide or the RT-11 System Ultilities Manual for a description
of the system program or utility that displayed the message.

Special Information About RT-11 System Messages

7.1

See Section 1.2 for a description of the format of RT-11 system messages.

7.2

Professional 300 Series Bootstrap Software Error Messages
If a software bootstrap error occurs when you power up your system, the
octal number 051124 will appear on your screen. Below this will be a second octal number that is the error code. The following table gives the error
message assigned to each error code. Reference the error message, not the
error code number.

Error Message

Code Number

000001

?BOOT-F-No boot on volume

000002

?BOOT-F—Conflicting SYSGEN options

000003

?BOOT-U-Handler file not found

000004

?BOOT-U-Insufficient memory

000005

?BOOT-U-1/O error

000006

?BOOT-U-Monitor file not found

000007

?BOOT-U-No KT-11

000010

?7BOOT-U-Swap file too small

000011

?BOOT-U-SWAP.SYS not found

000012

?BOOT-W-Error reading handler

If a problem occurs when you boot your system but the octal number
051124 does not appear on your screen, you have a hardware problem and
should consult the Professional 300 Series Owner Manual.

7.3

List of System Messages

?BA-U-BC

The BATCH handler found bad code in' the
control file. This can happen when a .CTL

file is corrupted or if someone made an edit-

ing mistake when altering or creating the

BATCH

Make sure that no editing errors have been
introduced into the file. Recompile the .BAT
file.

file with a text editor.

Version 5.1, July 1984

RT-11 System Message Manual

?BA-U-FE
1.

BATCHF

An invalid \F followed by a carriage re-

turn was used in the .CTL file, causing a

after the \F' to prevent forced termina-

forced end to BATCH processing.
2.

Insert another BATCH control directive
tion.

BATCH was terminated from the console

by a \F followed by a carriage return.

Do not type \F followed by a carriage re-

turn at the console unless you intend to

terminate BATCH processing.

?BA-U-IO
1.

BATCH F

An input or an output error occurred —

probably because of a log file overflow —

when the BATCH handler tried to read
the .CTL file or to write to the log file.

This message may also appear if the
BATCH control file (.CTL) is not in the

Rerun the BATCH stream, specifying a

larger log file with the square bracket
construction; the default log size is 64

decimal blocks.
2.

Make sure that the .CTL file is a valid
control file output by the BATCH com-

correct format. Common format errors oc-

piler

and that the directives to the
BATCH run-time system are in the correct format.

cur when you run an uncompiled BATCH
input file or use a BATCH run-time system directive that is preceded by one
backslash instead of two.

?BA-U-LU

BATCH F

The BATCH handler could not find a free
channel. This can happen if all 16 channels
are opened for magtape or cassette operations
within the BATCH stream.

Check the program and make sure that one
channel is left open and is not specified for

use by magtape or cassette.

BASIC-11 messages

Section 6.0 contains all BASIC—11 messages.
NOTE

The BATCH program message END BATCH is alphabetized under “END.”
?BATCH-F-Abort job

Either an error occurred in compiling a
BATCH program or a diagnostic compile was
requested with /N.

The compiler forces the job to abort. Check
the log file for all error messages.

?BATCH-F-Ambiguous command
The command abbreviation entered is not
unique.

Make sure that the command includes
enough characters to make it unique.

?BATCH-F-Ambiguous option

The option
unique.

abbreviation

specified

RT-11 System Message Manual

not

Make sure that the option contains enough
characters to make it unique.

?BATCH-F-Batch fatal error

An unrecoverable error occurred. This may
indicate a problem in the software.

Check the procedures for recovery from hard

error conditions listed in Section 2.0. The system may have to be bootstrapped again. If
the problem continues, submit an SPR to
DIGITAL; include with the SPR a program
listing and a machine-readable source program, if possible.

'BATCH-F-Batch handler not resident

The BATCH run-time handler was not
loaded with the RT-11 LOAD command.

?BATCH-F-Batch stack overflow

The BATCH stream has too many nested
$CALL commands.

?BATCH-F-Channel in use

A channel that should have been free for
BATCH was busy as a result of an internal

Load the BATCH handler, using the LOAD
command to run BATCH.

Make sure that the BATCH stream includes
no more than 31 nested $CALL commands.

Try the program again.

BATCH error.

?BATCH-F-Dismount error

The logical device name specified does not exist.

?BATCH-F-Duplicate option

An option was specified more than once in a

Make sure that the device was assigned with
a SMOUNT command.

Correct the command line.

command line.

Version 5.1, July 1984

RT-11 System Message Manual

56.1

—

?BATCH-F-EOF with no $EOJ

A file was not terminated with a $EOJ command.

Insert a $EOJ command as the last statement in the BATCH job.

?BATCH-F-File created; protected file already exists
A protected file exists, along with a newly
created unprotected file of the same name.
The protected file is either a BATCH control
file or a log file.

List the directory, unsorted. If the unprotected file appears before the protected file in
the directory listing, either delete or rename
it. If the protected file appears first, either
rename it or change the protection code with

the PIP /Z option or the monitor UNPROTECT command.

?BATCH-F-File not found

A file specified as input to BATCH was not
found, or the /X option was specified but the
input to BATCH was not a precompiled
(.CTL) file.

Check the file specifications and correct the
program to reflect any changes made.

?BATCH-F-Input error

A hardware error occurred while BATCH
was attempting to read the compiler input

Check the procedures for recovery from hard
error conditions listed in Section 2.0.

file (BAT).

?BATCH-F-Input file

An input file descriptor was not specified in
the BATCH compiler command line.

Check for a typing error in the command
line. Specify an input file in the command
line.

?BATCH-F-Insufficient memory

The BATCH compiler does not have enough
memory to fetch the device handler it needs.
The handler is needed either as an I/O device
for the BATCH compiler or to satisfy a
$MOUNT or $DISMOUNT command in the

Check for a typing error in the command line
to the BATCH compiler or in the SMOUNT
or $DISMOUNT command in the BATCH in. put file. Refer to Section 3.0 for information
on how to increase storage space.

BATCH job.

?BATCH-F-Invalid *+’

The plus sign (+) construction was used
when not allowed — for example, in a
$RUN or a $BASIC input file descriptor.

A plus sign (+) either is in an output file
descriptor or terminates a file descriptor.

Verify that the plus sign (+) is used only to
indicate a positive value in an option or to
separate multiple file descriptors.

?BATCH-F-Invalid character

The character specified was not used in the

proper context.

Check the log file to determine the character
in error.

RT-11 System Message Manual 57

?BATCH-F-Invalid command line

The command line to the BATCH compiler is
incorrect.

Check for a typing error in the command
line. Check the format for the command and
enter the command again.

?BATCH-F-Invalid construction
In RT-11 mode, an IF statement was not in
the correct form, or an invalid ‘text’ directive
occurred in a command.

Verify that the format of the IF statement is
correct and that the ‘text’ directive is valid as
entered.

?BATCH-F-Invalid copy of handler

The copy of BA.SYS in memory is invalid.

Unlink the batch handler if necessary, unload the copy of BA.SYS in memory, reload
BA.SYS, and run BATCH.

?BATCH-F-Invalid device

An invalid or nonexistent device was specified in the command line.

Check for a typing error in the command
line. Verify that the device exists as entered
in the command line, or use another device.

Enter the command again.

?BATCH-F-Invalid LOG device
A magtape, cassette, or read-only device (for
example, CR:) was specified as the log device.

Check for a typing error in the command
line. Assign the log device to a suitable device.

?BATCH-F-Invalid option
1.

An invalid option was used in the command line to the BATCH handler.

Check for a typing error in the command
line. Make sure that the option indicated
is valid.

The option name specified is not a valid
RT-11 BATCH option or is not valid for
this field.

Make sure that the option name specified
is a valid RT-11 BATCH option or option
abbreviation and that it is valid for the

field to which it applies. See the RT-11
System Ultilities Manual or the RT-11
System User’s Guide for a list of valid options and option abbreviations.
?BATCH-F-Invalid option combination
More than one option of the same type was
specified on one command line.

Make sure that only one option from the following combinations is used: /MACRO, /INPUT, /SOURCE, and /FORTRAN, /INPUT,
/SOURCE, and /BASIC, /INPUT, /SOURCE.

?BATCH-F-Invalid sequence argument

A nonnumeric identification number was
specified in a $SEQUENCE command.

RT-11 System Message Manual

Enter the command again, specifying the
identification number as an unsigned decimal number.

?BATCH-F-Invalid variable

The variable specified is not one of the characters A to Z.

?BATCH-F-Invalid VID

An incorrect form was used when specifying
the volume identification in a $SMOUNT command.

?BATCH-F-Line too long

The input line entered contains more than 80

Enter the variable as an alphabetic character.

Make sure that the equal sign (=) and the
name of the volume are included in the command.

Correct the input line.

characters.

?BATCH-F-LOG device error

A hardware error occurred during a transfer

operation to the log device.

?BATCH-F-'$’ missing

A dollar sign ($) is not present in the first
position of the command line or card column

Check the procedures for recovery from hard
error conditions listed in Section 2.0.

Make sure that a dollar sign ($) begins the

command line.

?BATCH-F-No control file

The program attempted to send the .CTL file
to a non-file-structured device — for example, LP:.

?BATCH-F-No $EOJ

A $JOB or $SEQUENCE command was issued without a preceding $£EOJ command to

Check for a typing error in the command
line. Use a file-structured device for the .CTL

file, or use the /N option to inhibit execution.

Correct the BATCH stream by inserting a
$EOJ command.

end the previous job.

?BATCH-F-No file

Either no file descriptor app cared where ex-

pectedin the BATCH stream or no fiw name
was enteredin the SCREATE command.

?BATCH-F-No file name before “.”
A file type was specified, but no file name
?BATCH-F-No *,’ in $LIB

Libraries in a $LIBRARY command were
separated by a comma (,) instead of by a plus
sign (+).

?BATCH-F-No logiaal device

No logical device was apwcmfiadin a SMOUNT

comaiaxy :‘a‘

Enter a file descriptor where expected

BATCH stream, or enter a file name in the
$CREATE command.

Correct the format of the file descriptor.

Edit the $LIBRARY command in the BATCH
input file, using a plus sign (+) instead of a
comma (,).

Correct the command format.

?BATCH-F-No physical device

No physical device
$MOUNT command.

was

specified

Correct the command format.

?BATCH-F-Output device full

The temporary file (.CTL) created by BATCH
is too large for the specified device.

Refer to Section 3.0 for information on how to
increase storage space.

?BATCH-F-Output error
1.

Magtape or cassette was specified as the

A hard error was reported while BATCH

.CTL output device.

was attempting to write the compiler out-

put file (.CTL).

Check for a typing error in the command
line. Verify that the output device specified is neither magtape nor cassette.
Check the procedures for recovery from

hard error conditions listed in Section
2.0.

?BATCH-F-Output file not open
The .CTL file output channel was not opened,
probably because of an error in the BATCH
compiler.

Submit an SPR to DIGITAL; include with the
SPR a program listing and a machine-readable source program, if possible.

?BATCH-F-Please assign LOG,LST
The log device (LOG:) or the listing device
(LST:) was not assigned.

Use the ASSIGN command to assign LOG:
and LST: devices. LOG: must be assigned,

and LST: is recommended unless the BATCH
stream will definitely not reference LST:.

?BATCH-F-Please load LOG handler

The log device handler is not resident.

Check for a typing error in the LOAD command. Load the appropriate device handler.

?BATCH-F-Protected file already exists
An attempt was made to create a protected
file having the same name as an existing protected file.
|

Use the monitor UNPROTECT command or
the PIP /Z option to change the protection
level of the existing file, or use a different
name to create the new file.

?BATCH-F-Return from call error

BATCH could not read the control file that
called a subprogram. Execution could not be
resumed on return from the call.

Verify that the .CTL file has not been destroyed; recompile if necessary. Try the operation again. Use another drive or unit if pos-

sible.
?BATCH-F-Separator missing

A file descriptor was not terminated by a
space, a plus sign (+), a comma (,) or a carriage return.

RT-11 System Message Manual

Correct the format of the file descriptor.

?BATCH—F-Too many file descriptors
More than six file descriptors were specified
in a BATCH command line beginning with a
dollar sign ($).

Check for a typing error in the command
line. Limit the number of file descriptors to

six. Check the format of the command in
question.

?BATCH-F-Too many output files

More than two output files were specified.

Check for a typing error in the command
line. Limit the number of output file specifications to two. (For BATCH, output files represent the compiler output device and file
and the log file.)

?BATCH-F-Unknown command

The command specified with a dollar sign ($)
in character position 1 is not a valid BATCH

Check the command line for typing errors.

command.

An entry to ODT was caused by a breakpoint
trap that ODT did not expect. Location
NNNNNN represents the location after the
trap instruction that ODT did not expect.
Setting the T bit in the status register, jumping to the middle of ODT, or executing data
using an invalid trace trap instruction can

Correct the contents of the location before

cause this error.

?BINCOM-E-Device full DEV:FILNAM.TYP
Not enough room is available in the directory
of the output device to create the specified
output file.

Use SQUEEZE to compress the volume, or
use a different volume for this operation. See
Section 3.0 for information on how to increase memory resources.

?BINCOM-E-Device not active DEV:
Input or output was requested for a device
that is not on line, not write-enabled, or not
in the system’s device tables. Wildcards may
have been used in the command string.

Make sure that the device is on line and is
write-enabled. Use the INSTALL command
to enter the device into the system’s device
tables.

?BINCOM-E-Error reading directory DEV:

A hardware error occurred while the directory of the indicated input device was being
read. Wildcards were used in the command

Check the procedures for recovery from hard
error conditions listed in Section 2.0.

string.

RT-11 System Message Manual

?BINCOM-E-File created; protected file already exists DEV:FILNAM.TYP

A protected file exists, along with a newly
created unprotected file of the same name. |

TECT command.

?BINCOM-E-Input error DEV:FILNAM.TYP
1.

A hardware error occurred while the
specified input file was being read.

During an attempt to access an input device specified with wildcards, a hardware
error occurred.

Refer to the procedures for recovery from
hard error conditions listed in Section 2.0.

?BINCOM-E-Input file not found DEV:FILNAM.TYP
1.

The specified input file was not found on
the specified device.

Wildcards were used in the command

line and a match was not found.

Make sure that the command line contains
no errors and that the specified file exists on
the specified device. If the correct device is
not mounted, mount it and enter the command again.

?BINCOM-E-Insufficient memory
BINCOM does not have the minimum
amount of memory it requires to use as
buffer space when it compares files.

Refer to Section 3.0 for information on how to
increase memory resources.

?BINCOM-E-Invalid command
1.

An incorrect command was issued to
BINCOM.

Check for a typing error in the command
line and make sure that the format of the
command line is correct. Enter the command again.

A file specification was given in the command string of the device/device compari-

Retype the command line without any
file specifications.

Remove the patch file from the command

son.

A patch file was specified with wildcards.

line, and retry the operation.

?BINCOM-E-Invalid directory DEV:
Wildcards were used in the command line to
read a directory, and the volume was not in
RT-11 format.

Copy the files onto an RT-11 directory de-

vice.

?BINCOM-E-Invalid option /x
The option specified in the command line is
invalid.

RT-11 System Message Manual

Check for a typing error in the command
line. See the RT-11 System Utilities Manual
or the RT-11 System User’s Guide for a list of
valid options.
'

?BINCOM-E-Invalid option /x:val

An option that requires a value was not

given one, or an option that does not take a

Check for a typing error, and type the com-

mand line again.

value was given one.

?BINCOM-E-Output error DEV:FILNAM.TYP

A hardware error occurred while the specified output file was being written.

Refer to the procedures for recovery from

hard error conditions listed in Section 2.0.

?BINCOM-E-Output file full DEV:FILNAM.TYP

Not enough room was allocated to the specified output file when it was created.

Delete the existing output file, or use a different volume for the output file. See Section
3.0 for information on how to increase memory resources.

?BINCOM-F-Wrong version of RT-11

An attempt was made to run an RT-11 Ver-

sion 5 utility (BINCOM) on a previous ver-

Do not run RT-11 Version 5 utilities under

earlier RT-11 versions.

sion of RT-11.

?BINCOM-I-Comparing/DEV:FILNAM.TYP — DEV:FILNAM.TYP
This message is informational.
1. The two input files compared are different.

A comparison resulted from wildcards.
BINCOM prints this message to show
which two files are being compared.

?BINCOM-I-No differences found

The files compared are identical. BINCOM

does not create an output file unless you used
the monitor DIFFERENCES/ALWAYS command or specified the /O option in the com-

This message is informational.

mand string.

?BINCOM-W-Device is longer DEV:
Whether or not there are differences in the
binary data on the two devices compared, the

This message is informational.

devices differ in length.

?BINCOM-W-Devices are different
The devices compared are different.

?BINCOM-W-File is longer DEV:FILNAM.TYP

Whether or not there are differences in the

binary data in the two files compared, the

This message is informational.
This message is informational.

files differ in length.

?BINCOMmWwFflm are different
The files compared are different.

This message is informational.
Version 5.1, July 1984

RT-11 System Message Manual

?BOOT-F-No boot on volume
No bootstrap was written on the volume.

Use

the DUP /U option or the monitor
COPY/BOOT command to write the bootstrap.

?BOOT-U-Conflicting SYSGEN options

Support for the error logger, extended memory, and device timeout differs in the system

handler and the monitor. Execution terminates.

Make sure that the monitor and handler file

versions are correct. If these files are lost, as-

semble the monitor and handlers with the
same system generated conditional file. See

the RT-11 System Generation Guide for details about SYSGEN options.

?BOOT-U-Handler file not found
The handler for the system device was not
found during the bootstrap operation. Execution terminates.

Copy the handler file (xx.SYS) for the system
device onto the volume you are trying to
boot. Reboot.
Oy

?BOOT-U-Insufficient memory
1.

The bootstrap blocks designate a monitor

that is too large for the system’s memory.

For example, attempts to bootstrap the
FB monitor on a system that has only 8K

the monitor COPY/BOOT command to
copy the bootstrap blocks for that moni-

words of memory would cause this error.
Execution terminates.

Since RT-11 sizes memory, hardware
failure of a memory module may result in
the monitor’s booting into less memory
than is installed on the system.

Select a monitor that is small enough for
the system, and use the DUP /U option or

tor.

Make sure that the hardware device has
sufficient memory for the monitor.

Make sure that the proper monitor and

?BOOT-U-I/O error
1.

An /O error occurred during system
bootstrap. Using a monitor before copying that monitor’s bootstrap to the vol-

system handler are on the system disk.

Use the backup volume and the DUP /U
option or the monitor COPY/BOOT:xx
command to make sure that the boot-

ume bootstrap blocks causes this error.

Execution terminates.

strap for the monitor is on the corresponding system volume. See the RT-11

System User’s Guide for more information about copying the bootstrap. If the

error persists, check the procedures for

recovery from hard error conditions in

Section 2.0.
2.

An error occurred in the interface bethe ROM primitive 1I/O sub-

tween

routines and the RT-11 software boot-

strap. Execution terminates.

Retry the bootstrap operation. If the er-

ror persists, turn the PDT-11 power off

and then on. Then recopy the monitor file
onto your system volume from the distri-

bution kit, and reinstall the bootstrap
with the DUP /U option or the monitor

COPY/BOOT:PD command. If the error

persists,

the

problem

PDT-11 hardware.

RT-11 System Message Manual

may

the

MBOOT or MSBOOT selected the incorrect I/0 instructions for the specified
magtape (MM:, MT:, or MS:) because another peripheral is located at the standard address for that magtape.

Make sure that the magtape controller is
located at the correct standard address
and that the standard addresses for the
other magtape devices are not used.

Version 5.1, July 1984

RT-11 System Message Manual

64.1

?BOOT-U-Monitor file not found

The system volume’s bootstrap blocks designate a monitor file that is not on the volume.
Execution terminates.

Make sure that the proper file is on the system disk. Use the backup volume and the
DUP /U option or the monitor COPY/BOOT
command to make sure that the bootstrap for
the monitor is on the corresponding system

volume.

?BOOT-U-No KT-11

An attempt was made to boot an XM monitor
on a system that does not have a KT-11
memory-management unit. Execution termi-

Reboot and select the SJ or FB monitor, or
use a system that has KT11 memory-management hardware.

nates.

?BOOT-U-Swap file too small

The file SWAP.SYS is on the system volume,
but is less than 26(decimal) blocks long. Execution terminates.

Copy the SWAP.SYS file from another working system volume to the system volume, or
use the DUP /C option or the monitor CREATE command to create the file with the correct length. The DUP /T option or the moni-

tor CREATE/EXTENSION

command can

“also be used to extend the file to the correct
length.

?BOOT-U-SWAP.SYS not found

The system SWAP file was not found on the
system volume during the bootstrap opera-

Copy SWAP.SYS to the system volume. Reboot the monitor.

tion. Execution terminates.

?BOOT-W-Error reading handler

A hardware error occurred while a handler file was being read.

A nonsystem handler file resides on a
bad block. Entries for this handler are removed from the running system’s device

Refer to the procedures for recovery from
hard error conditions listed in Section 2.0.

handler tables.

‘7BOOT-W-Invalid or missing TT.SYS
1.

The terminal handler, TT.SYS, was not
on the system volume when the nonmultiterminal SJ or the BL monitor was
bootstrapped. Many keyboard monitor
commands default to device TT:, and its
absence from the system can cause many

Copy the file TT.SYS to the system volume. Reboot the system in order to install TT:.

The system generation features for the
handler do not match the features for the

Get either a copy of the TT.SYS file created by the same system generation as
the monitor or a copy that has the same
set of system generation features. If the
file is lost, assemble TT.MAC with a system generated conditional file (see the
RT-11 System Generation Guide for details).

confusing error messages.

monitor.

RT-11 System Message Manual 65

?BUP-E-Wrong volume number
During a restore operation, the correct set of
volumes was being used, but the wrong volume was mounted.

Mount the correct volume. Try the operation
again.

?BUP-F-Channel in use DEV:FILNAM.TYP
A serious BUP internal error occurred.

Reboot the system and retry the operation. If
the error occurs again, get a new copy of
BUP.SAV and try the operation again. If the
error persists, submit an SPR to DIGITAL;
include with the SPR a program listing and a
machine-readable source program, if possible.

?BUP-F-Device in use
Another job was using the specified device.

Try the operation again after the job is either
finished or aborted.

?BUP-F-Directory input error DEV:

A hardware error occurred while the directory was being read.

Check the procedures for recovery from hard
error conditions listed in Section 2.0.

?BUP-F-Directory output error DEV:
A hardware error occurred while the directory was being written.

Check the procedures for recovery from hard
error conditions listed in Section 2.0.

?BUP-F-Duplicate option
The same option was specified more than
once in a single command line.

Correct the command line.

?BUP-F-Enough space on one volume — use PIP

The backup operation input fits on one output volume.

Use the PIP utility program to back up the
file(s). Refer to the RT-11 System Ultilities
Manual for information on how to use PIP.

?BUP-F-Error reading directory

A hardware error occurred while the directory was being read.

Check the procedures for recovery from hard
error conditions listed in Section 2.0.

?BUP-F-Fetch error DEV:
1.

A serious BUP or system internal error

occurred.
2.

The copy of BUP.SAV, the monitor file,

or the specified device handler may be
corrupted on disk.

3. The in-core mpy of BUP or the monitor
may be corrupted.

RT-11 System Message Manual

Reboot the system and try the operation
again. If the error occurs again, get a new
copy of BUP.SAV and the specified device
handler. Retry the operation. If the error persists, submit an SPR to DIGITAL; include
with the SPR a program listing and a machine-readable source program, if possible.

?BUP-F-File not found DEV:FILNAM.TYP

The backup volume does not contain the input file specified in the command line. Control returns to the monitor.

Check for a typing error in the command
line. Make sure that the specified file resides
on the backup volume. Try the operation
again.

?BUP-F-Input error DEV:FILNAM.TYP
A hardware error occurred during a read op-

Check the procedures for recovery from hard

eration.

error conditions listed in Section 2.0 of this

manual.

?BUP-F-Insufficient memory

Not enough memory is available to complete

Refer to Section 3.0 for information on how to

the requested operation.

increase memory space.

?BUP-F-Invalid command

The command entered is invalid because the
command line specified contains a syntax error, too many files were specified, no device
was specified, or an attempt was made to use

Check for a typing error in the command
line. Verify that the file name exists as entered in the command line, and try the operation again.

wildcards.

?BUP-F-Invalid device DEV:
An invalid or nonexistent device was specified in the command line.

Check for a typing error in the command

line. Verify that the device indicated is valid.

?BUP-F-Invalid device combination

The same device and unit was specified for
both input and output.

Check for a typing error in the command

line. See the RT-11 System Utilities Manual
or the RT-11 System User’s Guide for valid
device combinations.

?BUP-F-Invalid directory

The volume in the specified device does not
contain a valid RT-11 directory structure.

Initialize the volume before using it for the
first time.

?BUP-F-Invalid option

An invalid option was used in the command
line.

Check for a typing error in the command
line. See the RT-11 System Ultilities Manual
or the RT-11 System User’s Guide for a list of
valid options.

?BUP-F-Invalid option combination

The specified options request conflicting
functions to be performed.

Examine the logic of the command line and

correct it if necessary. Refer to the RT-11
System Ultilities Manual or the RT-11 System User’'s Guide for valid option combina-

tions. Try the operation again.

RT-11 System Message Manual

?BUP-F-No room on output device DEV:

Not enough room is available on the output
device for BUP to complete the restore operation.

Try the operation again, using an output device that has a larger number of free blocks.

?BUP-F-Not a backup volume DEV:

The
volume
specified
in
the
DIRECTORY/BACKUP command is not a
backup volume. Control returns to the moni-

Use a backup volume for the directory operation.

tor.

?BUP-F-Operation not completed
The backup operation was aborted before it
was completed because a NO response was
given to the mount ‘query.

Try the operation again and type YES in response to the mount query.

?BUP-F-Output error DEV:FILNAM.TYP
A hardware error occurred during a write operation.

Check the procedures for recovery from hard
error conditions in Section 2.0.

?BUP-F-Too many bad blocks DEV:
More than 25 bad blocks were detected during a disk-to-disk backup or restore opera-

Verify that your disks are loaded correctly. If
that is not the problem, use another disk.

tion.

?BUP-F-Volume does not belong to this set
During the restore operation, the specified

Try the operation again, using volumes that

input file and the number of the mounted

are part of the set being restored.

volume match the file name and the volume
number of the backup volume. However, the
number of blocks that were backed up to the
mounted volume does not match the number
of blocks for the set of volumes being re-

stored.
?BUP-F-Wildcards not permitted on command line
An attempt was made to use wildcards in the
command line.

Try the operation again, using specific file
names in the command line. Do not use wild-

cards.

?BUP-F-Wrong version of RT-11
An attempt was made to run RT-11 Version

Do not run RT-11 Version 5 BUP under any

5 BUP on a previous version of the RT-11

earlier RT-11 versions.

system.

?BUP-I-Bad block scan started...
BUP has started to scan a volume for bad
blocks.

Version 5.1, July 1984

RT-11 System Message Manual

This message is informational.

2BUP-I-Bad blocks detected; use another volume
Use another volume and try the operation
BUP detected bad blocks on the specified volume.

?BUP-I-Copy operation is complete
BUP has finished restoring or backing up a

again.

This message is informational.

file or volume.

?BUP-I-Creating volume n

BUP is backing up information to the speci-

This message is informational.

fied volume.

?BUP-I-No bad blocks detected

BUP did not detect any bad blocks on the
specified volume during the bad block scan.

This message is informational.

?BUP-I-Restore operation start ed from volume n
This message is informational.
The restore operation has started from the
specified volume.

?BUP-W-Bad block read at nnnnnn
A bad block was detected at location nnnnnn
during a disk-to-disk backup or restore oper-

This message is a warning.

ation. The bad block was not copied.

?BUP-W-File not found DEV:FILNAM.TYP
During the restore operation, the input file
specified in the command line was not found
on the volume mounted. The wrong set of volumes may have been used. The mount query

Check for a typing error in the command
line. Make sure that the volume that is
mounted contains the specified file.

is repeated.

?BUP-W-Incompatible output volume size
The output volumes used during the backup
operation are a different size than the first
backup volume used. For example, this mes~ sage will appear if single-density and double“density diskettes are used for output volumes

Try the operation again, using volumes that
are the same size.

" during the operation.

?BUP-W-Not a backup volume DEV:
The volume specified in the command line for

a backup or a restore operation has not been
initialized as a backup volume. BUP repeats

Type YES in response to the initialization
|

query.

the initialization query.

?CREF-F-Chain-only CUSP

An attempt was made to use R CREF or the
START command to run a copy of CREF that
is in memory.

(CUSP stands for commonly used system program.) Use a language processor to invoke
CREF.
Version 5.1, July 1984

RT-11 System Message Manual

?CREF-F-CREF file error
An

input

error

DK:CREF.TMP,

the

occurred

while

temporary

input

passed to CREF, was being read.

file

Run the language processor again to create a

new CREF input file.

?CREF-F-Device not found
1.

A listing was written to magtape or cas-

sette before the magtape or cassette han-

Before writing a listing to magtape or
cassette,

dler was manually loaded.

manually

handler.
2.

The input file to CREF (CREF.TMP) is
not on a random-access device.

use

the

load

LOAD

the

command

appropriate

device

Verify that CREF.TMP is on a random-

access device and that CF: is assigned to

it.

The

language processor chaining to
CREF specified an invalid device. This

may be a system error.

If the error persists, submit an SPR to
DIGITAL; include with the SPR a program listing and a machine-readable
source program, if possible.

?CREF-F-File created; protected file already exists
A protected listing file exists, along with a
newly created unprotected file of the same
name.

List the directory, unsorted. If the unprotected file appears before the protected file in

the directory listing, either delete or rename

it. If the protected file appears first, either

rename it or change the protection code with

the monitor UNPROTECT command or the
PIP /Z option.

?CREF-F-LST file error
An output error occurred while the cross-reference table to the listing file was being written to. The output volume may not have
enough free space for the listing file.

Refer to Section 3.0 for information on how to

increase storage space. If the error persists

when space is adequate, check the procedures

for recovery from hard error conditions listed
in Section 2.0.

?CSI-F-Device full
The output file created by a user program
utilizing .CSIGEN with terminal input did

not fit on the device specified.

Refer to Section 3.0 for information on how to
increase storage space. Use the /ALLOCATE

option or the CSI square bracket ([]) construction to specify the size of the output file.

?CSI-F-File not found
The input file called by a user program using

.CSIGEN with terminal input was not found.

Check for a typing error in the command
line. Verify that all file names exist as entered in the command line, and try the opera-

tion again.

RT-11 System Message Manual

?CSI-F-Invalid command

‘The command line in a user program using
.CSIGEN or .CSISPC with terminal input
contains a syntax error.

An RT-11 directory-structured device
was specified for output without a file
*RKl:=
example,
name — for

A command line contains either more
than 80 printing characters before a carriage return or invalid characters, such

Check for a typing error in the command
line. Check the format of the monitor command and reenter it. Try to simplify the com-

mand, and retype it.

Make sure that input to a .GTLIN request
does not exceed 80 characters.

as blanks.

Too many files and devices were specified
in a keyboard monitor command.

Input to a .GTLIN request contains more
than 80 characters.

?2CSI-F-Invalid device

The device specified in a user program using
.CSIGEN with terminal input does not exist.

A device such as TT: or BA: was referenced, probably in a TYPE command, but
that device handler does not exist on the
system device, even though a SHOW
command lists the device as valid.

The DIRECTORY command was typed or
issued when running under the SJ monitor and the TT.SYS file is not on the system device. System commands that require TT.SYS will not operate properly

Check for a typing error in the command
line. Make sure that the device indicated is a
valid device; if it is not, copy TT.SYS onto the
system device and bootstrap the system
again since TT: and BA: cannot be installed.

without the TT.SYS file.

?CSI-F-Prot file

One or more files specified in a user program

using .CSIGEN with terminal input already
exist and are protected.

Either choose a different name for the new
output file or delete, rename, or change the
protection code of the existing file with the

monitor UNPROTECT command or the PIP
/Z option.

?CTn: Push rewind or mount new volume
The end of the cassette mounted on unit n
‘was reached. The cassette handler waits for
operator response.

Mount a new cassette on the indicated drive
for the cassette operation to proceed. Pushing
the REWIND button on the indicated drive
generates an error for the cassette transfer;
the system proceeds with the next operation
in the job.

RT-11 System Message Manual

?DIR-F-Device not active
Input or output was requested for a device

that was not on line, not write-enabled, or
not in the system’s device tables.

Make sure that the device is on line and is
write-enabled. Use the INSTALL command
to enter the device into the system’s device

tables.
?DIR-F-Error reading directory
A hardware error occurred while the directory was being read.

Check the procedures for recovery from hard
error conditions listed in Section 2.0.

?DIR-F-File created; protected file already exists DEV:FILNAM.TYP
A protected directory file exists, along with a
newly created unprotected file of the same
name.

List the directory, unsorted. If the unprotected file appears before the protected file in
‘the directory listing, either delete or rename
it. If the protected file appears first, either
rename it or change the protection code with

the monitor UNPROTECT command or the
PIP /Z option.

?DIR-F-Input error DEV:
A hardware error occurred when DIR tried to
open the input file.

Check the procedures for recovery from hard
error conditions listed in Section 2.0.

?DIR-F-Insufficient memory
Not enough memory is available to perform
the directory sort specified.

Use fewer file names in the sort. Specify only
the necessary files, or exclude files that do
not need to be sorted. Use the DIR /P or the
monitor /EXCLUDE option; for example, use

/EXCLUDE *.SYS to exclude all system files.
?DIR-F-Invalid command
An incorrect command format was used with

the DIRECTORY command.

Check the format of the DIRECTORY command; correct any typing errors and enter
the command again.

?DIR-F-Invalid device DEV:

The desired operation cannot be performed
on the device specified because the device is
not directory- and file-structured, such as TT:
or LP:.

Use a valid device name in the command.

?DIR-F-Invalid directory
An attempt was made to read a directory not
in RT-11 format.

If the volume is from another system, use the
corresponding option for that format; for example, use /DOS to read a RSTS directory.

?DIR-F-Invalid option: /x
An invalid option was used in the command
line.

Check for a typing error in the command
line. Refer to the RT-11 System Utilities

Manual or the RT-11 System User’s Guide
for a list of valid options.

RT-11 System Message Manual

?DIR-F-Output error DEV:FILNAM.TYP

A hardware error occurred while the output
file was being written.

?DIR-F-Output file full

The output file is full.

Check the procedures for recovery from hard
error conditions listed in Section 2.0.

Send the output from the DIRECTORY command to a printing device, or use the
JALLOCATE option to specify the size of the
output file. See Section 3.0 for information on
how to increase memory and storage resources.

?DIR‘-erPmtected file already exists DEV:FILNAM.TYP
Use the monitor UNPROTECT command or
An attempt was made to create a protected
the protection
file having the same name as an existing protected file.

?DIR-F-Wrong version of RT-11

An attempt was made to run an RT-11 Version 5 utility (DIR) on a previous version of

the PIP /Z option to change
level of the existing file, or use a different
name to create the new file.

Do not run RT-11 Version 5 utilities under

earlier RT-11 versions.

RT-11.

?DIR-I-Backup file — Use /BACKUP option
The file specified with the DIRECTORY com-

Enter the command line again using the

?DUMP-F-Device full DEV:FILNAM.TYP
The device does not have enough room for the

Refer to Section 3.0 for information on how to

mand was created by the BUP utility.

DUMP output file.

?DUMP-F-File or input device not found
Either the input file was not on the volume
specified or the device was not known to the

system. This error occurs if the device was

not installed or if its handler was not on the
system disk.

DIRECTORY/BACKUP command.

increase storage space.

Use the DIRECTORY command to check the
file names in the SY: directory. Verify that
the input file’s device handler is on SY:. Use
the SHOW command to list installed devices,
and install the appropriate device, if necessary, with the INSTALL command. Type the
command again.

?DUMP-F-Input error DEV:FILNAM.TYP
A hardware error occurred while the input
file was being read.

Check the procedures for recovery from hard
error conditions listed in Section 2.0. The
/IGNORE or the /G option may be used to
disregard input errors.

?DUMPwaInauffiai&nt memory

Fewer than the minimal 256 wnrds of memory are free for DUMP to use as a buffer. The

Refer to Section 3.0 for information on how to
increase the amount of available memory.

command is not executed.

Version 5.1, July 1984

RT-11 System Message Manual 73

?DUMP-F-Invalid command
The DUMP command line has an error, such

Correct the command line.

as more than one input or output file specifi-

cation. The command is not executed.

?DUMP—--F—-Invalid option: /x
An option in the command line is invalid, has

Check for a typing error in the command
line. Refer to the RT-11 System Utilities

an invalid value, or has no value where a

block number (octal) is required.

Manual or the RT-11 System User's Guide
for a list of valid options.

?DUMP-F-No LP
A line printer handler was not available on
the system.

Check for a typing error in the command
line. Indicate a specific valid output device
and file name.

?DUMP-F-Output error DEV:FILNAM.TYP

Either the output device is full or a hardware

Refer to Section 3.0 for information on how to
increase storage space. Check the procedures

error occurred in writing the output file.

for recovery from hard error conditions listed
in Section 2.0.

?DUMP-F-Protected file already exists DEV:FILNAM.TYP
An attempt was made to create a protected
file having the same name as an existing pro-

tected file.

Use the monitor UNPROTECT command or
the PIP /Z option to change the protection
level of the existing file, or use a different

name to create the new file.

?DUMP-F-Unexpected EOF DEV:FILNAM.TYP

DUMP found the end of the file before the
last block specified by an /END:block,

/ONLY:block, or /START:block option.

Retype the command, using the block values
(octal) of the file to be dumped. Use either the

monitor

DIRECTORY/BLOCKS/ORDER:
POSITION command or the DIR /B/S option

to show the position on the volume and the
starting block for each file.

?DUMP-F-Wrong version of RT-11
An attempt was made to run an RT-11 Version 5 utility (DUMP) on a previous version

of RT-11.

Do not run RT-11 Version 5 utilities under
earlier RT-11 versions.

?DUMP-W-File created; protected file already exists DEV:FI

A protected file exists, along with a newly

created unprotected file of the same name.

LNAM.TYP

List the directory, unsorted. If the unprotected file appears before the protected file in

the directory listing, either delete or rename
it. If the protected file appears first, either
rename it or change the protection code with

the monitor UNPROTECT command or the

PIP /Z option.

Version 5.1, July 1984

RT-11 System Message Manual

?DUP-E-Operation not completed
The /WAIT operation was aborted because
the response to the mount message began
with an N or was a CTRL/C.

2DUP-F-Bad block in system area DEV:
DUP found a bad block in a critical area of
the disk, making the volume unusable.

This message informs you that the operation
has been aborted. The response to the mount
message must begin with a Y for the /WAIT
operation to continue.

Reformat the volume, if possible; try the operation again. If the error persists, the volume must be replaced.

?DUP-F-Can’t squeeze SY: while foreground loaded
A foreground or a system job was loaded
when a SQUEEZE command was issued for
the system device.

2DUP-F-Channel in use DEV:FILNAM.TYP
An internal DUP error occurred.

Stop any foreground or system jobs, or wait
until they are complete and then unload
them. Issue the command again.

Reboot the system and retry the operation. If
the error occurs again, get a new copy of
DUP.SAV and retry the operation. If the error persists, submit an SPR to DIGITAL; include with the SPR a program listing and a
machine-readable source program, if possible.

Version 5.1, July 1984

RT-11 System Message Manual 74.1

?DUP-F-Channel not open DEV:FILNAM.TYP/

An internal DUP error occurred.

Reboot the system and retry the operation. If
the error occurs again, get a new copy of
DUP.SAV and retry the operation. If the error persists, submit an SPR to DIGITAL; in-

clude with the SPR a program listing and a
machine-readable source program, if possible.

?DUP-F-Conflicting SYSGEN options
The system device handler and the monitor
file have different SYSGEN options enabled.

Make sure that the correct monitor file was
specified in the command. Make sure that
the correct device handler is on the volume.

?DUP-F-Device full DEV:FILNAM.TYP
1.

The output volume does not have enough
room to receive the specified files or data.

No unused area is large enough to create
the file.

The specified file and successive files on
the input volume are not copied.

If the monitor CREATE command was used,
specify a smaller file size with the /ALLOCATE option or consolidate free space on the
output volume with the SQUEEZE command. If the monitor SQUEEZE/OUTPUT
command was used, initialize the output volume with fewer directory segments. If the
monitor COPY/DEVICE/FILE command was
used, copy to a different output volume, or
use the SQUEEZE command to create a large
enough contiguous unused area on the current volume.

?DUP-F-Directory full DEV:

The output volume directory does not have
enough space to create the output file.

Either use the SQUEEZE command to consolidate free space on the output volume or
copy the output volume to a volume with
more directory segments. Enter the command again.

?DUP-F-Directory input error DEV:

An error occurred while the directory of the
specified device was being read.

Check the procedures for recovery from hard
error conditions listed in Section 2.0. Try the
operation again. If the error persists, copy as
many files as possible to another volume,
then reformat the original volume. If the error still occurs, replace the volume.

?DUP-F-Directory output error DEV:

An error occurred while the directory of the
specified device was being written.

RT-11 System Message Manual

?DUP-F-Error reading bad block replacement table DEV:
~ An input error occurred while the bad-block
replacement table was being read from the
specified volume. This table is contained in
block 1, the home block of the volume.

Check for bad blocks on the volume. If the
home block is bad, the volume is unusable
and must be replaced. Check the procedures

for recovery from hard error conditions listed
in Section 2.0.

?DUP-F-Fetch error DEV:
1.

A serious DUP or internal system error
occurred. The copy of DUP.SAV, the
monitor file, or the specified device handler may be corrupted on disk.

The in-core copy of DUP or the monitor
may be corrupted.

Reboot the system and try the operation
again. If the error occurs again, get a new

copy of DUP.SAV and the specified device
handler. Retry the operation. If the error persists, submit an SPR to DIGITAL; include
with the SPR a program listing and a ma-

chine-readable source program, if possible.

?DUP-F-File not found DEV:FILNAM.TYP
The specified file was not found.

Check for a typing error in the command
line. Try the operation again.

?DUP-F-Input error DEV:FILNAM.TYP
A hard error occurred during a read operation.

Check the procedures for recovery from hard
error conditions in Section 2.0.

?DUP-F-Insufficient memory

Not enough memory is available to complete
the requested operation.

Refer to Section 3.0 for information on how to
increase memory space.

?DUP--F-—Invalid command
1.

The command entered is invalid.

Check for a typing error in the command
line.

The format specification is incorrect.

Check the format of the command line.

The combination of options specified is
invalid.

Refer to the RT—-11 System Utilities Manual or the RT—11 System User’s Guide for
a list of valid option combinations.

4. A device is not valid for the requested
operation.

Make sure that the specified device is
valid for the requested operation and try
the command again.

?DUP-F-Invalid device DEV:

The specified device is not installed in the
monitor device tables.

Check for a typing error in the command
line. Use the INSTALL command to add the
device to the monitor device tables.

?DUP-F-Invalid directory DEV:

The volume in the specified device does not
contain a valid RT-11 directory structure.

RT-11 System Message Manual

Initialize the volume before using it for the
first time.

?DUP-F-Invalid option: /x

The option specified in the command line is
invalid.

Check for a typing error in the command
line. See the RT—-11 System Utilities Manual
or the RT-11 System User’s Guide for a list of
valid options.

?DUP-F-Invalid restore data DEV:
DUP was unable to execute the monitor
INITIALIZE/RESTORE command or the

DUP /D option because data stored in the

home block of the volume is invalid.

The volume cannot be restored; files and directory entries present before the volume was
initialized are lost. Refer to the RT-11 System User’s Guide for more information about
the INITIALIZE/RESTORE command.

?DUP-F-Invalid value specified with option: /x

A value specified is outside the acceptable
range.

Check for a typing error in the command
line. Refer to the RT-11 System Ultilities
Manual or the RT-11 System User’s Guide
for a list of valid options and the range of
valid values for each option.

?DUP-F-Non-bootable driver DEV:FILNAM.TYP
1.

Either a monitor BOOT or COPY/BOOT
command or a DUP /U option was given
for a device whose device handler did not

The colon (:) that must follow the device
driver mnemonic is missing. DEV: repre-

The device cannot be booted. Use another
device for the operation.

contain a primary bootstrap.

Retype the command, typing a colon after
the device driver mnemonic.

sents the physical device name.

?DUP-F-No room for file DEV:FILNAM.TYP
Not enough room is available on the device to
create the file. Either the unused area is not
as large as the value specified with the /ALLOCATE or the DUP[n] option or a file already occupies the area specified.

Delete a file or files from the affected area of
the volume.

?DUP-F-No space for extension DEV:FILNAM.TYP
Specify a smaller value on the CREATE/EXThe unused area following the file is not
TENSION command or the DUP /T option, or
large enough to accommodate the required
delete a file or files from the affected area of
size specified by the monitor CREATE/EXTENSION command or DUP /T option.

the volume.

?DUP-F-No V5 boot on volume

1.
2.

An attempt was made to boot a volume

Use the COPY/BOOT command to copy a
bootstrap to the volume.

An attempt was made to boot a volume

Retry the operation, using
BOOT/FOREIGN command.

the

RT-11 System Message Manual

that does not contain a bootstrap.

containing a bootstrap that is not compatible with RT-11 Version 5.

?DUP-F-Output error DEV:FILNAM.TYP

A hard error occurred during a write opera-

tion.

Check the procedures for recovery from hard
error conditions listed in Section 2.0.

?DUP-F-Output file exists DEV:FILNAM.TYP
A CREATE command specified a file name
that already exists on the output volume. No
operation is performed.

Delete the file that exists on the volume, or
enter the command again, using a different
file name.

?DUP-F-Size function failed
An error occurred while DUP was determining the size of the volume mounted in a device. The monitor, the device handler, or
DUP may be corrupted. This message also oc-

Check the procedures for recovery from hard
error conditions listed in Section 2.0. Reboot
the system and try the operation again.

curs if the unit number specified is not supported by the monitor created through system generation.

?DUP-F-Unexpected EOF DEV:FILNAM.TYP

An internal DUP error occurred.

Reboot the system and try the operation
again. If the error occurs again, get a new
copy of DUP.SAV from your distribution volume and retry the operation. If the error per-

sists, submit an SPR to DIGITAL; include
with the SPR a program listing and a ma-

chine-readable source program, if possible.

?DUP-F-Uninitialized volume DEV:
The directory of the specified volume is not
initialized properly for the command.

Initialize

the directory,
INITIALIZE command.

using

the

?DUP-F-Volume not RT-11 format DEV:
The specified volume is not in RT-11 directory-structured format.

Either format the volume, using the
FORMAT command, or use another volume

for the operation.

?DUP-F-Wrong version of RT-11
An attempt was made to run an RT-11 Version 5 utility (DUP) on a previous version of

RT-11.

Do not run RT-11 Version 5 utilities under
earlier RT-11 versions.

?DUP-I-No bad blocks detected DEV:

No bad blocks were detected during the badblock scan initiated either by the monitor
commands DIRECTORY/BADBLOCKS,
INITIALIZE/REPLACE,
or
INITIALIZE
/BADBLOCKS or by the DUP /K, /R, or /B
options.

Version 5.1, July 1984

RT-11 System Message Manual

The volume is ready to use.

?DUP-U-Channel not open DEV:FILNAM.TYP
An internal DUP error occurred.

Reboot the system and try the operation
again. If the error occurs again, get a new

copy of DUP.SAV and retry the operation. If

the

error

persists,

submit

SPR

DIGITAL; include with the SPR a program
listing and a machine-readable source pro-

gram, if possible.

Version 5.1, July 1984

RT-11 System Message Manual

78.1

- ?2DUP-U-System error

Reboot the system and try the operation

An internal DUP error occurred.

again. If the error occurs again, get a new

copy of DUP.SAV and retry the operation. If
the error persists, submit an SPR to DIGITAL: include with the SPR a program listing
and a machine-readable source program, if
possible.

?DUP-U-Wrong version of RT-11

An attempt was made to run RT-11 Version
5 DUP on a previous version of the RT-11
system.

2’DUP-W-Bad blocks detected nnnnn

Bad blocks were detected during the bad-

block scan initiated either by the monitor
commands DIRECTORY/BADBLOCKS,
INITIALIZE/REPLACE,

Do not attempt to run RT-11 Version 5 DUP
under any RT-11 version preceding Version
5.

The volume is ready to use.

INITIALIZE/BADBLOCKS or by the DUP
/K, /R, or /B options.

?DUP-W-Device full DEV:FILNAM.TYP

The output volume does not have enough
room to receive the data specified in a
COPY/DEVICE command or a DUP /I operation.

9DUP-W-Output error DEV:FILNAM.TYP

An output error occurred during a SQUEEZE
operation.

Use an output volume that is larger than or
equal to the input volume. Refer to Section
3.0 for information on how to increase storage space.

DUP places a .BAD file over the bad block
and continues with the operation.

2DUP-W-Owner name truncated at ten characters

DUP truncated the owner name for a magtape because more than 10 characters were

entered as the name.

If truncation is not acceptable, initialize the
magtape again, entering 10 or fewer characters.

2DUP-W-Owner name truncated at twelve characters

DUP truncated the owner name for a disk
because more than 12 characters were entered as the name.

If truncation is not acceptable, use either the
monitor INITIALIZE/VOLUMEID:ONLY
command or the DUP /V option to change the

owner name. Remember to enter 12 or fewer
characters.

?DUP-W-Replacement table overflow DEV:

The specified device contains more than the
maximum replaceable bad blocks.

DUP prompts you to determine which blocks
should be replaced and which should be made

BAD files. The RT-11 System Utilities Manual and the RT-11 System User’s Guide describe how to create files over bad blocks.

RT-11 System Meamge Manual 79

?DUP-W-Too many bad blocks DEV:
More than 128 bad blocks were encountered
during a bad-block scan.

The volume cannot be used and must be reformatted or replaced.

?DUP-W-Verification error at relative block nnnnnn
During a COPY/DEVICE/VERIFY command, the input data did not match the out-

put data at the specified relative block.

Check the output volume for bad blocks.
Check the procedures for recovery from hard

error conditions listed in Section 2.0. Try
the
operation again.

?DUP-W-Volume ID truncated at six characters
DUP truncated the volume ID for a magtape
because more than six characters were entered as the ID.

If truncation is not acceptable, INITIALIZE
the magtape again. Remember to enter six or
fewer characters.

?DUP-W-Volume ID truncated at twelve characters
DUP truncated the volume ID for a disk be-

cause more than 12 characters were entered

as the ID.

If truncation is not acceptable, use the moni-

tor INITIALIZE/VOLUME:ONLY command
or the DUP /V option to change the volume

ID. Remember to enter 12 or fewer charac-

ters.

?EL-W-Buffer is full, logging suspended
The internal logging buffer is full. Logging of

new reports has been suspended, but statis-

tics will continue to be maintained along
with a count of the reports not logged. This

The current contents of the internal logging
buffer may be discarded by using the SET EL
PURGE command. Statistics are not affected.

state does not affect the operation of the sys-

tem.

?EL-W-Device statistics table is full
The error logger is maintaining statistics for
the number of devices selected during system

generation. Error reports from any device

Perform another system generation and select support for more devices.

will be logged, but statistics will be main-

tained only for those devices already having

statistics entries. This state does not affect
the operation of the system.

?ELINIT-F-Channel error
An internal error occurred.

Retry the operations that produced the error.
If the error persists, submit an SPR to DIGI-

TAL; include with the SPR a program listing

and a machine-readable source program, if
possible.

?ELINIT-F-Device full
Not enough room is available on the specified
device to create or expand the ERRLOG.DAT
file.

Use the monitor SQUEEZE command or the
DUP /S option to compress the volume, or use
a different disk for the operation. See Section
3.0 for information on how to increase mem-

ory and off-line storage resources.

RT-11 System Message Manual

2ELINIT-F-Device not available
The device requested by the operator is not

Load the device handler and run ELINIT

?ELINIT-F-ERRLOG.DAT file I/O error
An error was encountered while reading or
writing the ERRLOG.DAT file.

Refer to the procedures for recovery from
hard error conditions listed in Section 2.0.

2ELINIT-F-ERRLOG task not active
An attempt was made to initiate error logging before running the error logging job.

Run EL, using the monitor FRUN or the
SRUN command, before running ELINIT.

loaded.

?ELINIT-F-Internal error

An internal error occurred while the error
logger was recovering from a previous system
Or user error.

again.

Retry the operations that produced the error.
If the error persists, submit an SPR to DIGITAL; include with the SPR a program listing
and a machine-readable source program, if
possible.

2ELINIT-F-Protected file already exists ERRLOG.DAT
The ERRLOG.DAT file is protected.

Use the monitor UNPROTECT command or
the PIP /Z option to change the protection
level of the existing file, or use a different
name to create the new file. Then run ELINIT again.

?ELINIT-W-Invalid command
An invalid answer was given to an operator
command initialization question. The ques-

Correct the response to the question.

tion is asked again.

?ERRLOG-F-Channel error

An internal error occurred.

Retry the operations that produced the error.
If the error persists, submit an SPR to DIGITAL; include with the SPR a program listing
and a machine-readable source program, if
possible.

?ERRLOG-F-Internal error

An internal system error occurred.

Retry the operations that produced the error.
If the error persists, submit an SPR to DIGITAL; include with the SPR a program listing
and a machine-readable source program, if
possible.

?ERRLOG-F-Log file /O error

An error was encountered while reading or

writing the ERRLOG.DAT file.

Refer to the procedures for recovery from
hard error conditions listed in Section 2.0.

RT-11 System Message Manual

?ERRLOG-I-REMINDER: To initiate error logging, RUN ELINIT
ERRLOG prints this message as a reminder
that you must run the ELINIT program to
initiate error logging.

This message is informational.

?ERRLOG-I-To initiate error logging, RUN ELINIT
To initiate error logging, run the ELINIT

This message is informational.

program.

?ERRLOG-W-Invalid message received
A task or a background job other than
ERROUT tried to communicate with the EL
task. The attempt is ignored.

This message is informational.

?ERRLOG-W-Log file full, logging suspended

The ERRLOG.DAT file is full. The header
block continues to be updated, but error
records are not recorded.

Terminate ERRLOG and reinitialize to enable error logging again.

END BATCH
A BATCH job was terminated. Control returns to the monitor.

BATCH 1
This message is informational.

?ERROR: FORTRAN IV messages
Section 5.0 contains all FORTRAN IV error
messages.

?ERROUT-F-Channel error
An error occurred within the ERROUT program.

Submit an SPR to DIGITAL; include with the
SPR a program listing and a machine-readable source program, if possible.

?ERROUT-F-Device not found
The device specified in the command string
was not found.

Make sure that the specified device is installed. Reenter the command.

ERROUT-F-File not found
The input file containing the error log statistics was not found.

Make sure that the specified file resides on
the specified device. Reenter the command.

?ERROUTmFmInput error
A hardware error occurred.

Refer to the procedures for recovery from
hard error conditions listed in Section 2.0.

?ERROUT-F-Insufficient memory
Not enough memory is available to process
the statistics file.

RT-11 System Message Manual

Refer to Section 3.0 for information on how to
increase memory resources.

?ERROUT-F-Internal error

An error occurred within the ERROUT program.

?ERROUT-F-Invalid command
The ERROUT command is not in the correct
format.

ERROUT-F-Output error

A hardware error occurred.

?ERROUT-F-Output file full

The output file does not have enough room to
continue writing.

2ERROUT-F-Protected file already exists
An attempt was made to create a report file
having the same name as an existing protected file.

ERROUT-W-Device full

Not enough room is available on the specified

device to create the output file.

?FILEX-F-Channel not open

An IO channel that FILEX required for the
command is not open.

?FILEX-F-Device full

Either the directory or the output volume
does not have room for the file name.

?FILEX-F-Directory error input
Either an error occurred while the directory

of the input device was being read or looked
up or the input device does not have the
proper file structure.

Submit an SPR to DIGITAL; include with the
SPR a program listing and a machine-readable source program, if possible.

Make sure that the command is typed in the
correct format. Enter the command again.

Refer to the procedures for recovery from
hard error conditions listed in Section 2.0.

Refer to Section 3.0 for information on how to
increase storage space.

Use the monitor UNPROTECT command or
the PIP /Z option to change the protection
level of the existing file, or use a different
name to create the new file.

Use another device for this operation, or use
the monitor SQUEEZE command on the device to create more room.

Check the procedures for recovery from hard

error conditions listed in Section 2.0.

Refer to Section 3.0 for information on how to
increase storage space.

Check for a typing error in the command
line. Verify that the input device has the correct structure. If it does, a hard error condition exists. Check the procedures for recovery
from hard error conditions listed in Section
2.0.

2FILEX-F-File already exists DEV:FILNAM.TYP
Use the /D option to delete the file and try
An attempt was made to create the named
the transfer again, or use a new name to crealready
file on a DOS DECtape when a file
existed under the name specified.

ate the file.

RT-11 System Message Manual

?FILEX-F-File created; protected file already exists
A protected file exists, along with a newly
created unprotected output file of the same
name.

List the directory, unsorted. If the unprotected file appears before the protected file in
the directory listing, either delete or rename

it. If the protected file appears first, either

rename it or change the protection code with

the monitor UNPROTECT command or the
PIP /Z option.

?FILEX-F-File not found
Either the input file was not found or the
wildcard construction matched none of the
existing files.

Check for a typing error in the command
line. Verify that the file name exists as entered in the command line, and try the opera-

tion again.

?FILEX-F-Foreground loaded
An attempt was made to use the /T, or
/TOPS, option when a foreground job was active.

Terminate the foreground job and unload it,
using the monitor UNLOAD FG command.

?FILEX-F-Input error
A hardware error occurred during an input
operation.

Check the procedures for recovery from hard

error conditions listed in Section 2.0.

?FILEX-F-Insufficient memory
Not enough room is available in memory for
buffers and input list expansion.

Refer to Section 3.0 for information on how to
increase memory space. Try copying the files
one at a time without using the wildcard con-

struction on input.

?FILEX-F-Invalid command
The command entered is invalid for one of
the following reasons:
®

The length of the command line exceeds

72 characters.
®

The command line is not in the proper
CSI format.

The UIC exceeds the allowed number of

characters, or square brackets ([]) are unbalanced.
®

A wildcard construction was used on a sequential-access device.

No output or no input file was specified
for a copy operation.

RT-11 System Message Manual

Check for a typing error in the command
line. Verify that the format of the command
line is correct and that the UIC is in the
proper format. Verify that FILEX can perform all specified operations. Then retry the

operation.

More than one file name construction
(dev:filnam.typ) was specified on either
side of the equal sign (=) or less than sign
().

An operation that FILEX cannot perform
was attempted — for example, initializing an RT-11 device.

?FILEX-F-Invalid device
1.

The device handler was not found.

An invalid device name was used.

One of the following was attempted:

Check for a typing error in the command
line. Make sure that necessary device handlers are present on the system and that the
device indicated is a valid device name and is
valid for the operation indicated.

¢ RK or DT was not used for

DOS/BATCH (RSTS) in a copy operation.

e DT was not used for DOS/BATCH
(RSTS) output in an initialize or a delete operation.

"o DT was not used for DOS/BATCH
(RSTS) output in a copy operation.

e DT was not used for DECsystem—10
input in any operation.

?FILEX-F-Invalid option

An invalid option was used in a command
line.

Check for a typing error in the command
line. See the RT—11 System Ultilities Manual
or the RT-11 System User’s Guide for a list of
valid commands.

?FILEX-F-Invalid option combination
1. An attempt was made to use more than
one device option (/S, /T, /U), transfer option (/I, /P, /A), or operation option (/D,
/L, /F, /Z) in a FILEX command line.
Only one option can be used per combina-

Check the command line for invalid combina-

tions. Issue the command again.

tion.

An attempt was made to combine /DOS
and /TOPS in a COPY or a DELETE
command, to use /IMAGE and /ASCII to-

gether on a copy operation, or to use one

of these with INTERCHANGE on a DE
LETE operation.

RT-11 System Message Manual 85

?FILEX-F-Invalid output filename
The output file name is invalid or null.

Check for a typing error in the command
line. Verify that an output file name was
specified in the correct format and that it

contains no invalid characters.

?FILEX-F-Invalid PPN format
The DOS/BATCH user identification code
was not in the form [nnn,nnn], where each

Check the format of the user identification
code.

nnn is an octal number less than or equal to
3717.

?FILEX-F-Not interchange format
The /P option or the INTERCHANGE command was used and a diskette did not have a
directory in universal interchange format.

Check for a typing error in the command
line. Verify that the diskette has a directory
in universal interchange format.

?FILEX-F-Operation not completed
The /WAIT operation was aborted because
the response to the mount message began
with an N or was a CTRL/C.

This message informs you that the operation
has been aborted. The response to the mount
message must begin with a Y for the /WAIT

operation to continue.

?FILEX-F-Output error
An unrecoverable error occurred while an
output file was being processed.

Check the procedures for recovery from hard
error conditions listed in Section 2.0.

?FILEX-F-Protected file already exists DEV:FILNAM.TYP
An attempt was made to create a protected
file having the same name as an existing protected file.

Use the monitor UNPROTECT command or
the PIP /Z option to change the protection
level of the existing file, or use a different

name to create the new file.

?FILEX~-F-UFD not found

The specified UFD was not found on the DOS
input disk.

Verify that no typing error has been made
and that the input disk is the correct one.

?FILEX-F-Unexpected EOF
During

a transfer between a volume in
RT-11 format and a volume in universal interchange format, the system detected the
end of the file on the interchange volume before completing the transfer. Attempts to
read a faulty diskette or to read or write with

Check the procedures for recovery from hard
error conditions listed in Section 2.0. If the
error occurs on input hardware that is opera-

ting properly, check the hardware that wrote

the input volume, if possible.

a faulty device can cause this error.

FILEX-W-Volume ID truncated at six characters

FILEX truncated the volume ID for a magtape because more than six characters were
entered as the ID.

RT-11 System Message Manual

If truncation is not acceptable, INITIALIZE
the magtape again. Remember to enter six or
fewer characters.

2FORMAT-F-Device error

Either an error occurred while FORMAT was
attempting to format the device or the unit
number specified does not exist.

Make sure that the unit number specified is
valid. If the problem appears to be a hardware error, check the procedures for recovery
from hard error conditions listed in Section
2.0.

?FORMAT-F-Device invalid or not supported by FORMAT
The FORMAT program did not recognize the
device specified.

Retype the command line, using a valid device specification.

?FORMAT-F-Device not ready

The device specified is not ready to be formatted or verified because the device is off
line, write-protected,-or not up to speed.

Check the device unit. Make sure that it is
powered up, that the volume is write-enabled, and that the device — if it is a
disk — is up to speed.

?FORMAT-F-Error reading manufacturer’s bad sector file (RK06/07)

Sectors on the last file of the last track contain a manufacturer’s bad sector; the file
could not be read. Execution terminates.

Use another disk.

?FORMAT-F-Error writing headers (RK06/07)
The FORMAT program encountered errors
while writing headers to a track. Execution

Use another disk.

terminates.

?FORMAT-F-Error writing software bad block file
Formatting was successful, but no software
bad-block table was written.

FORMAT prompts for another command. No
corrective action is necessary for this condition.

?FORMAT-F-Insufficient memory

Not enough memory is available to perform
the specified function.

See Section 3.0 for information on how to increase memory resources.

?FORMAT-F-Invalid command line

The command line typed is incorrect, possibly
because an output as well as an input device
was specified; more than one input device
was specified; or a file name was given with

Reenter the command line in the format input-device[/options].

the device specification.

?FORMAT-F-Invalid option: /x

The option specified (/x) is not a valid option
for the device specified.

Reenter the command line and use only valid
options. See the RT—-11 System Utilities Manual or the RT-11 System User’s Guide for a

summary of valid options.

RT-11 System Message Manual

?FORMAT-F-Invalid option /x:val
The specified option (/x) does not accept an

Reenter the command line and use only valid

argument.

syntax. See the RT-11 System Utilities Man-

FORMAT prompts for another

command.

ual or the RT-11 System User’s Guide for a
summary of valid options.

?FORMAT-F-Invalid value specified with option: /x
An invalid value was specified with option /x.

Reenter the command line and use only valid
syntax. See the RT-11 System Utilities Manual or the RT-11 System User’s Guide for
valid option values.

?FORMAT-F-Manufacturer’s bad sector file corrupt (RK06/07)
The manufacturer’s bad sector file is not in a

Use another disk.

valid format. Execution terminates.
?FORMAT-F-Operation not completed

The /WAIT operation was aborted because
the response to the mount message began
with an N or was a CTRL/C.

This message informs you that the operation
has been aborted. The response to the mount

message must begin with a Y for the /WAIT
operation to continue.

?FORMAT-F-Unit number must be in range 0-7
An invalid unit number was specified for a

device.

Reenter the command line, using a device
unit number in the range 0 to 7.

?FORMAT-F-Unit number too large for RT-11 configuration
The unit number specified exceeds the number of units on the configuration.

Check the number of the required unit. Issue
the command again.

?FORMAT-F-Wrong version of RT-11
An attempt was made to run an RT-11 Version 5 utility (FORMAT) on a previous ver-

sion of RT-11.

Do not run RT-11 Version 5 utilities under
earlier RT-11 versions.

?FORMAT-I-Formatting aborted

device

error

occurred.

Formatting

aborted.

The device must be formatted successfully
before it can be used. Run the FORMAT program again.

FORMAT-I-Formatting complete
The device is now formatted.

The device is ready for use.

7FORMAT-I-Verification aborted
A device error or a user abort caused the pat-

Rerun the pattern verification to verify the

tern verification to terminate.

volume, if necessary. Refer to the procedures

for recovery from hard error conditions listed
in Section 2.0.
?FORMAT-I-Verification complete
The FORMAT program verification sequence
is complete.
Version 5.1, July 1984

RT-11 System Message Manual

This message is informational.

FORMAT-U-Device handler fetch error

The handler could not be fetched, probably
because the device handler was not present
to perform device verification.

?FORMAT-U-Disk is an alignment cartridge

The RK06/07 disk selected for formatting is
an alignment disk. Execution terminates.

Make sure that the device handler for the
disk being verified resides on the system volume. Run the FORMAT program again.
Use another disk.

2FORMAT-U-Formatting/Verifying the system volume is not allowed
Specify a different device unit number and
An attempt was made to format or to verify
format the device. You can also use the monithe volume on which the running RT-11 systor /WAIT or the /W option, which permits a
tem currently resides.

pause before formatting begins, so a second
volume can be substituted for the system device. See the RT-11 System Utilities Manual
or the RT-11 System User’s Guide for information on how to do this.

2FORMAT-U-Too many bad blocks DEV:

The software bad-block limit was exceeded.

?FORMAT-W-Duplicate option: /x

The option (/x) was already specified in the
command line.

Use another disk for the operation.

Check the command line for duplicate options, and enter the command again.

?FORTRAN messages

Section 5.0 contains all FORTRAN IV messages.

?HELP-F-File not a valid library HELP.MLB

The file HELP.MLB is not in proper library
format.

Create the file HELP.MLB by processing
HELP.TXT with the librarian after editing

HELP.TXT. Refer to the procedures for customizing the HELP text in the RT-11 Installation Guide.

?HELP-F-File not found HELP.MLB

The file HELP.TXT was not found on either
SY: or DK:, and HELP was built to run without an integral text file.

Copy HELP.TXT from the system backup
volume onto SY:, if SY: has room for it, and
use LIBR to create HELP.MLB. Copy the file

to DK: if SY: does not have room. Alternatively, copy HELP.SAV from the distribution
volume.

?HELP-F-Help not available for topic AAAAAA

The information requested is not available.

Consult the RT-11 System User’s Guide, the

RT-11 System Utilities Manual, or an experienced user.

RT-11 System Message Manual

?HELP-F-HELP.MLB has invalid format

The file HELP.MLB is in library format but
contains a line that is not in valid format.

Refer to the procedures for customizing the
HELP text in the RT-11 Installation Guide.
Make sure that you do not corrupt the format

of lines in the file HELP.MLB after it has
been created by processing HELP.TXT with
the librarian.

?HELP-F-Insufficient memory

An internal error occurred.

Submit an SPR to DIGITAL: include with the
SPR a program listing and a machine-readable source program, if possible.

?HELP-F-Invalid option, type ‘HELP<RET>’
An invalid HELP option was specified.

Check the command line for a typing error.
Type HELP<RET> or refer to the RT-11
System User’s Guide for a list of valid HELP
options. Retry the operation.

?HELP-F-Read error on HELP.MLB
A hard error occurred while
HELP.MLB was being read.

the

file

Check the procedures for recovery from hard
error conditions listed in Section 2.0.

?HELP-F-Syntax error in command, type ‘HELP<RET>’
The HELP command was improperly format-

ted.

Type HELP<RET> for a listing of the HELP

command text and an explanation of how to

use the HELP command.

?HELP-F-Write error on LP:
A hard error occurred during a write operation to the printer.

Check the procedures for recovery from hard
error conditions listed in Section 2.0.

?HELP-W-Help not available for subtopic AAAAAA
The information requested is not available.

Consult the RT-11 System User’s Guide, the
RT-11 System Utilities Manual, or an experienced user.

?HELP-W-Help not available for subtopic item AAAAAA
The information requested is not available.

Consult the RT-11 System User’s Guide, the
RT-11 System Utilities Manual, or an experienced user.

?HELP-W-Line printer not available — using terminal
An attempt was made to output information

from the HELP text to a line printer, and
either the line printer specified is not present
in the system or the handler is not installed.
The output will be sent to the console terminal.

RT-11 System Message Manual

Verify that the printer specified is installed
in the system.

Control File Messages

The format for control file messages is described in Section 1.2.

?IND-E-Invalid Answer or Terminator
1.

IND encountered an invalid response to

.ASK,

.ASKN, or .ASKS directive
prompt. For example, an alphabetic char-

Make sure that the response to the .ASK,
.ASKN, or .ASKS prompt is valid.

acter response may have been given to an

.ASKN prompt.
2.

Escape recognition is disabled, and an es- cape character was entered in response to
a prompt. The prompt is repeated.

?IND-E-String length not in range
The response entered to an .ASKS directive
prompt fell outside the range designated by

the prompt. The prompt is repeated.

Make sure that the response
within the specified range.

entered

Make sure that the response
within the specified range.

entered

?IND-E-Value not in range
The numeric value entered in response to an

ASKN

directive

prompt

fell

outside the

range designated by the prompt. The prompt

1s repeated.

?IND-F-Bad range or default specification

The default response fell outside the
range specified with an .ASKN or an

Make sure that a valid radix is used in

the

range specification and that
range is specified from low to high.

.ASKS prompt; the range used an invalid
radix; or the range was specified in an

the

invalid sequence.

The optional default value assigned to
the symbol in the .ASKS directive is not
a string literal or another string symbol.

Make sure that the default value assigned to the symbol in the .ASKS direc-

tive is a string literal or another string
symbol.

?IND-F-Data file open
-

IND attempted to execute a keyboard command before closing open files.

Close open files before the control file exits
from IND.

?IND-F-Deleting special symbol
An attempt was made to delete an IND spe-

cial symbol.

Check for a typing error. Do not try to delete
an IND special symbol.

?IND-F-File already open
An attempt was made to open a file with the

.OPEN, .OPENA, or .OPENR directive and
the file is already open.

Make sure that the file is closed before trying

to open it.

RT-11 System Message Manual

- ?2IND-F-File not found

The control file IND tried to process does not
exist in the directory of the specified volume.

Check the control file specifications to make
sure that they are correct and that the specified control file exists. Also, make sure that
the specified volume is mounted.

?IND-F-File not open

An attempt was made to access a file that is
not open.

Make sure that the file is open before trying
to access it.

?2IND-F-File read error

A hard error occurred when IND tried to read
a file.

?IND-F-Invalid attempt to erase symbol
An attempt was made to delete a symbol outside a Begin/End block.

Refer to the procedures for recovery from
hard error conditions listed in Section 2.0.

Try the operation again. Delete symbols only
within the current Begin/End block.

?2IND-F-Invalid command

IND encountered an error in a command line
used to execute another control file.

?2IND-Invalid device or unit

Either the device specification for a file IND
tried to access is invalid or the device specifi-

Make sure that nested control file specifications and options are correct. See the RT-11
System User’s Guide for information on
nested control file specifications and options.

Make sure that all device specifications are
valid.

cation is for a nonexistent device.

2IND-F-Invalid file number

The file number specified is outside the valid
range 0 to 3.

?IND-F-Invalid keyword

An unrecognized keyword, preceded by a period, was specified in the command.
?IND-F-Invalid nesting

Make sure that the file number falls within
the valid range.

Make sure that all directives are spelled correctly and that the directives are in the correct syntax.

IND found .END without .BEGIN or .BEGIN
without .END directives in the control file.

Make sure that each .BEGIN and .END directive has a corresponding .END and

2IND-F-Invalid operator for operation
You attempted to use an arithmetic operator
(+, —, * or /) in a logical expression with the

Do not use arithmetic operators in .SETL log-

SETL directive..

?IND-F-Invalid option

IND encountered an unrecognized option.

.BEGIN directive.

ical expressions. Use only the logical operators & (AND), ! (OR), and ~ (NOT).

Enter the command again. Use only the valid
options listed in the RT-11 System User’s
Guide.

Version 5.1, July 1984

RT-11 System Message Manual

?IND-F-Label not at beginning of line
A label does not appear as the first character(s) on a line, except for spaces or tabs.

Make sure that the labels have no embedded
spaces and that the labels do not appear in
the middle of the command line.

?IND-F-Maximum indirect files exceeded

An attempt was made to access a control file
at a depth greater than three levels.

Make sure that the nesting limit of three is
not exceeded. This limit does not include the
initial level.

2IND-F-Null control string

No delimiters were defined in a .PARSE directive control string. A control string cannot
be null.

Make sure that the correct syntax is used for
a control string.

2IND-F-Numeric under- or overflow

A value assigned as a numeric symbol falls
outside the valid range 0 to 177777(octal) or
65535(decimal).

Make sure that all numeric symbols have
values within the valid range. Make sure
that no arithmetic expression that IND tries
to assign to a numeric symbol yields a result

outside the valid range.
?IND-F-Prompt string too large

The prompt issued with the .ASK, .ASKN, or
ASKS directive has too many characters.

Specify a prompt that has a valid number of
characters.

?IND-F-Redefining special symbol

An attempt was made to change the value of

Do not try to change the value of an IND

a special symbol.

special symbol.

?IND-F-Redefining symbol to different type <symbol>

An .ASK, .ASKN, .ASKS, .READ,
SETT, .SETF, .SETL, .SETN, or SETS

Do not try to change the type of a defined

symbol. If you redefine a symbol, make
sure that the new definition has the same
type as the original symbol.

directive was used in an attempt to set

the specified defined symbol to a different
type. The first definition of a symbol determines its type, and subsequent redefinitions must conform to the original
type.

The numeric symbol specified with the
SETT, .SETF, or .SETL directive has not
been previously defined.

The numeric symbol specified with the
JFT or .IFF directive has been defined as
a logical or string symbol.

Define the numeric symbol being used
before you specify it with the .SETT,

SETF, or .SETL directive.
Define a new symbol as a numeric type.
Specify the numeric symbol with the .IFT
or .IFF directive.

RT-11 System Message Manual

?IND-F-.RETURN without .GOSUB
A .RETURN statement does not have a corre-

Make

sponding .GOSUB statement.

.RETURN statements and that all .GOSUB

sure that there are no extraneous

statements are used correctly. Make sure

that all . RETURN statements are located
correctly in the program logic.
?IND-F-String expression exceeds limit
The limit of 132 characters in a string ex-

Make sure that string expressions do not ex-

pression was exceeded; a string concatena-

ceed the 132-character limit. Make sure that

tion operation yielded a string that exceeds

all string expressions are properly enclosed

the 132-character limit; or quotes do not ap-

by quotes.

pear at the end of a string expression.

?IND-F-String substitution error
IND encountered an error while substituting
a symbol.

Make sure that all substituted symbols have
been defined and that each substituted symbol is enclosed with apostrophes.

?IND-F-Subroutine nesting too deep
The maximum subroutine nesting level of

Make sure that the maximum nesting level

eight is exceeded.

is not exceeded.

?IND-F-Symbol table overflow <symbol>
The IND symbol table is full; there is no

Use the .ERASE directive to delete symbol

space for the symbol represented by <symbol>.

definitions from the symbol table.

?IND-F-Symbol type error <symbol>
The symbol <symbol> was not used in the

Compare only symbols of the same type.

context for its type; for example, a numeric
expression referenced a logical symbol.

?IND-F-Syntax error
IND encountered an unrecognizable element.

Check for typing errors and enter the com-

Common

mand again.

examples

misspelled
parentheses,

of syntax

commands,
imbedded or

errors

are

unmatched
missing spaces,

and other typographical errors.
?IND-F-Undefined label <.label>
IND did not find the label, represented by

Check for a typing error. Check the program

<.label>, specified in a .GOTO, .GOSUB, or

logic and insert the label, represented by

.ONERR directive.

<.label>, where appropriate.

?IND-F-Undefined symbol <symbol>
A symbol in the command line is not defined.

Make sure that all symbols being used or
substituted are defined.

?IND-F-Wrong version of RT-11
An attempt was made to run an RT-11 Ver-

Do not run RT-11 Version 5 utilities under

sion 5 utility (IND) on a previous version of
RT-11.

earlier RT-11 versions.

Version 5.1, July 1984

RT-11 System Message Manual

Primary Input/Output Error Messages

The format for primary input/output error messages is described in Section 1.2.
2IND-F-Data file error

A hard error was encountered while IND was
processing an .OPEN, .OPENA, .CLOSE, or
DATA directive or a data mode access to the

Refer to the procedures for recovery from
hard error conditions listed in Section 2.0.

output file.

?2IND-F-Error reading from terminal
IND encountered an error while trying to receive data from the console.

?IND-F-Swap error

IND encountered an error while writing to
itself.

?2IND-W-Timeout support not available
IND tried to process a .ENABLE timeout directive either while a monitor without
timeout support was running or on a system
that does not have a clock.

Refer to the procedures for recovery from
hard error conditions listed in Section 2.0.
Make sure that the system device is not

write-locked.

Remove the .ENABLE timeout directive
from the program, use a monitor that has
timeout support, or run the program on a system that has a clock.

Secondary Input/Output Error Messages

The format for secondary input/output error messages is described in Section 1.2.
Bad file name

The file specification in the command line

Make sure that the format of the file specifi-

Bad record type — not ASCII data
The file specified as input to IND does not

Make sure that there are no typing errors in

is invalid.

contain valid ASCII characters.

Data overrun

Either more than 80 characters were entered at the terminal or an attempt was

made to read a record that contains more
than the maximum of 80 characters.

Device full

Not enough room is available in the directory of the output device to create the specified output file. This error generally oc-

curs when IND attempts to execute a
.OPEN or a .CLOSE directive.

cations is correct.

the specified file.

Make sure that input entered at the terminal
does not exceed 80 characters.

Make sure that the output device has enough
room for all the files to be stored there. Refer
to Section 3.0 for information on how to increase storage space.

RT-11 System Message Manual

Device read error

IND encountered a bad block or another
type of hard error when trying to access a

file.

Make

sure

that

each

device

accessed

mounted. Refer to the procedures for recovery

from hard error conditions listed in Section
2.0.

Device write error
IND encountered a bad block or another
type of hard error when trying to send out-

put to a file.

Make sure that the device to which data is
being sent is mounted and is write-enabled.

Refer to the procedures for recovery from
hard error conditions listed in Section 2.0.

File accessed for read
An attempt was made to write to a currently open file with the .OPENR directive.

Either close the file before writing to it or
purge the file.

File accessed for write
- An attempt was made to read a currently
open file with the .OPEN or .OPENA
directives.

Either close or purge the file before opening
it to be read.

File already open
An attempt was made to open a file with a
file number already in use.

Either use an available file number or close a
file that is already open.

File exceeds space allocated
The volume receiving data is full.

Use the monitor SQUEEZE command or the
DUP /S option to compress the volume. See
Section 3.0 for information on how to in-

crease storage space.

File protection error
An attempt was made either to create a
file with the same name as a protected file

that already exists or to delete a protected
file.

Either use the keyboard UNPROTECT command to disable a file’s protected status or

change the name of the new file.

Invalid device or unit

The device or unit specified with the

.OPEN, .OPENA, or .OPENR directives is

invalid.

Check for syntax errors in the device specifi-

cation.

No file accessed on channel
An internal error occurred in IND.

Try the operation again. If the error persists,
send an SPR to DIGITAL; include with the
SPR an output listing or log file and a machine-readable copy of the control file(s).

RT-11 System Message Manual

No such file

The file specified in the OPEN or DELETE
command was not found.

Undefined error code

IND has detected an error it cannot classify.

?KMON-F-Address

An address is out of range in an E or a D

command.

?KMON-F-Ambiguous command
The command abbreviation entered is not

unique — for example, CO could stand for
COPY or COMPILE.

Make sure that the file specification has the
correct syntax and spelling.

Submit an SPR to DIGITAL; include with the
SPR an output listing or log file and a machine-readable copy of the control file(s).
The allowable range is between 0 and the
base of RMON (contents of location 54 octal);
the locations in the E or the D commands
cannot exceed this range. If device handlers
are loaded, the high limit is the beginning
address of these loaded handlers. Check for a
typing error in a prior B command.

Use enough characters in a command abbreviation to make that command unique. Four
characters are usually enough. Refer to the
RT-11 System User’s Guide for the minimum
abbreviations.

?KMON-F—-Ambiguous option

The option abbreviation entered is not

unique.

?KMON-F-Bad fetch DEV:

An error occurred while KMON was reading
a device handler from SY:. This error can oc-

cur during the execution of a keyboard monitor LOAD, RUN, SRUN, or FRUN command,
or from using indirect files that do not reside
on the system device. The keyboard monitor
loads device handlers for these commands.
This error can also occur if the system disk-

Use enough characters in an option abbreviation to make that option unique. Four characters are usually sufficient; six characters
are sufficient in an option prefixed by NO.

Make sure that the device handlers refer-

enced are installed and are not in an area

that contains bad blocks. If you exchange the
system diskette, reboot the system.

ette was exchanged without rebooting.

?KMON-F-Command file nesting too deep
A reference was made to a fourth level of
nested indirect command files.

2KMON-F-Command string too complicated
The command is too complicated to parse,
probably because too many options are in the

Limit indirect command file nesting to three
levels.

Simplify the command and reenter it.

command line.

RT-11 System Message Manual

?KMON-F-Conflicting options

Incompatible options were specified in the
command line.

Refer to the RT-11 System User’s Guide for
valid option combinations.

?KMON-F—-Conflicting SYSGEN options
The SYSGEN options of the device handler
disagree with those of RMON.

Select a compatible RMON/handler combina-

tion.

?KMON-F-Console must be local
A SET TT CONSOL =n command specified a
logical unit of a terminal that is supported as
a remote terminal.

Specify a local terminal as the console termi-

nal and issue the command again.

?KMON-F-Device full DEV:FILNAM.TYP
Not enough room is available in the directory
of the output device to create the specified
output file.

Make room on the device by removing files,

or use another device for this operation. See

Section 3.0 for information on how to increase memory on off-line storage resources.

?KMON-F-Device loaded or not removable DEV:
1.

A REMOVE command specified an invalid device handler — for example, the
TT, BA, or system device handler.

Make sure the device handler specified in
the REMOVE command can be removed.

A REMOVE command specified a handler that is loaded.

Use the SHOW command to determine
which handlers are resident; unload resident handlers before removing them.

?KMON-F-Error in file spec
Either an error exists in the format of a file
specification or a file specification does not

appear in the command line where one is ex-

Verify that the dev:filnam.typ format is used,
and enter the command again.

pected.

?KMON-F-Extended memory monitor required for DEV:FILNAM.TYP
1.

A program was running under the SJ or
the FB monitor, but extended memory
overlays were requested.

Make sure that the system includes memory-

management hardware and that the program

is run under the XM monitor.

The virtual bit of the job status word is
set.

?KMON-F-File not found DEV:FILNAM.TYP
1.

The file specified in an R, RUN, FRUN,
SRUN, GET, SET, INSTALL, or indirect
file command was not found.

The file needed to process the command
was not found on the indicated devices.

Check for a typing error in the command
line. Verify that the file name is in the correct format and that it contains no invalid

characters. Verify that the named file resides
on the named device and that all files neces-

sary to process the command, such as utility
programs and handler files, also reside on the

named device. Type the command line again.

RT-11 System Message Manual

NOTE

This message can occur during system bootstrap if the start-up indirect command

file (STARTS, STARTF, or STARTX.COM) is not found. If this message occurs

during bootstrapping, the system has been bootstrapped properly even though the
start-up file was not found. The start-up file may have been accidentally deleted or
renamed.

To prevent this message from appearing whenever the system is bootstrapped,

replace the start-up file for the monitor in use, or create a new start-up file and
give it the proper name for the monitor being used (STARTS.COM for the SJ
monitor, STARTF.COM for the FB monitor, and STARTX.COM for the XM monitor).

?KMON-F-Foreground active
An attempt was made to execute an FRUN or

Wait for the foreground job to finish, unload

an UNLOAD F command when an active

it, and then start a new foreground job.

foreground job already existed.

?KMON-F-Input error DEV:FILNAM.TYP
1.

An input error occurred while the file
specified in an R, RUN, GET, FRUN, or
SRUN command was being read.

Check the procedures for recovery from hard
error conditions listed in Section 2.0.

An error occurred while block 0 of the
handler file was being read during the
INSTALL command.

An error occurred during the execution of
a SET command for a handler.
?KMON-F-Insufficient memory
1.

The monitor GET, R, or RUN command
was used on a file that is big enough to
overlay the monitor if loaded into mem-

Refer to Section 3.0 for information on
how to increase storage space.

Insert a CTRL/C in the middle of the in-

ory.

An indirect file is too large to be exe-

direct file to break it into two sections.

cuted.

The USR would have moved down into
the area of memory mapped by the KT11
PAR1 mapping register. Not enough
memory was detected by /O to or from
the system scratch area during command
processing — for example, on a SAVE

Reduce the size of the foreground program. Use the UNLOAD command to remove some resident device handlers, if

there are too many.

operation.

?KMON-F-Insufficient memory for region
Not enough memory is available to create the
virtual overlay region when running the pro-

See Section 3.0 for information on how to increase memory resources.

gram in extended memory.

RT-11 System Message Manual

?ZKMON-F-Invalid command

The KMON command used is invalid.

Check for a typing error in the command
line. Try the operation again.

An indirect file is not the last item, excluding comments, on a keyboard monitor command line — for example,
COMPILE FILE @A.

Make sure that the indirect file is the
last item on a keyboard monitor command line.

The command file name contains invalid
character(s) — for example, @A*B.

Make sure that the command file name

The command used is not available
through the DCL commands and no SAV
file type of the command name used ex-

ists.

contains only valid characters.
See the system manager about whether
the DCL command was removed from the
system during system generation. Make

sure that a SAV file type of the command

being used exists on the system volume.

?KMON-F-Invalid continuation
An attempt was made to continue a line from

When continuing a line from an indirect com-

a nonnested indirect file to the console terminal.

nested.

mand file, make sure that the indirect file is

?KMON-F-Invalid control file nesting
You are running an IND control file that
calls an indirect command file, which in turn
calls another IND control file.

You cannot include, in IND control files, an

indirect command file that calls another IND
control file.

?KMON-F-Invalid date
The DATE command argument is invalid.

Check for a typing error in the command
line. Enter the date using the correct
format — DATE dd-mmm-yy.

Version 5.1, July 1984

100

RT-11 System Message Manual

?KMON-F-Invalid device DEV:
1.

The device specified is invalid, the operation is invalid for the specified device, or

Check for a typing error in the command
line. Verify that the device indicated is

a device handler for use with a fore-

valid. Note that devices for R, RUN,

ground job (dev=F) was loaded when the

GET, SAV, SRUN, and FRUN must be
random-access devices. The dev=F (and

SJ monitor was running.

dev =B) construction is valid only under
the

FB monitor.

Enter the command

again.

An attempt was made to install either

TT: or BA..

Copy the TT: or BA: handler file to the
system volume, then reboot the system so

that TT: or BA: can be installed.
Under the FB and XM monitors, an at-

Unload the device after the foreground

tempt was made to unload a device the

job has finished.

foreground owns while a foreground job
was active. In this case, DEV: is the job
name.

The commands LOAD TT: (in SJ) or

Copy the TT: or BA: handler file to the

LOAD BA: (in any monitor) were used

system volume and reboot the system.

when

the

appropriate

file

(TT.SYS,

BA.SYS, or BAX.SYS) was not present
on the system device. In this situation,
TT: and BA: still appear in a SHOW listing because RT—-11 reserves device slots
for them.

Version 5.1, July 1984

RT-11 System Message Manual

100.1

?KMON-F-Invalid device for command file
An indirect file was invoked from a nonblock-replaceable device (PC:, CT:, MT:).

Copy the indirect file to a block-replaceable
device, such as RK: or DX:, and enter the
command line again.

?KMON-F-Invalid device installation DEV:FILNAM.TYP
Either the CSR specified in the handler is not
valid in the current configuration or the de-

Verify that the device specified by the CSR is
installed.

vice setup failed.

?KMON-F-Invalid file format DEV:FILNAM.TYP

In XM or FB, a .REL file produced by a
version of RT—-11 previous to Version 3
was specified in the foreground.

Because the .REL format of RT-11 Version 3 and later versions differs from the

.REL format of Version 2C and earlier
versions, foreground jobs must be relinked to run under Version 3 and later
monitors. Use the monitor LINK/FORE-

GROUND command or the LINK /R option to relink the file and reenter the

command.

In XM, the .SAV image specified for the
foreground is not a virtual job. In FB, the
file is not a .REL file.

Verify that the .SAV image specified for

the foreground is a virtual job in XM.
Also, check the file to make sure that the
virtual bit is set. Verify that the file is a
.REL file when running in FB.

?KMON-F-Invalid logical job name

An attempt was made to execute an SRUN or
an FRUN command with a job name already
associated with an active job or with an invalid job name.

Make sure that the job name contains from
one to six characters and that neither F nor B

is used for a logical job name. Verify that the
line contains no errors. Use the monitor
SHOW JOBS command or the RESORC /J
option to obtain a list of current job names.
Reenter the SRUN or the FRUN command
with a name not already associated with an
active job.

?KMON-F-Invalid NO on option
A NO prefix was specified with an option

that

does

not

allow

it — for

example,

COPY/NOBOOT.

Check the RT-11 System User’s Guide for a
list of options that are valid when prefixed by
NO. Omit the option. This may produce the
desired effect by default. Check and enter the
command line again.

?KMON-F-Invalid option

An invalid option was used in the command
line.

Check for a typing error in the command
line. Use only those options for keyboard
monitor commands listed in the RT-11 System User’s Guide.

RT-11 System Message Manual

101

?KMON-F-Invalid option for program

The option used belongs to another
program — not the one implied by the com-

Examine the command line, select an appropriate option, and try the operation again.

mand line.

?KMON-F-Invalid priority level

The priority level specified by the
SRUN/LEVEL option is either an invalid priority level or the same as another active job.

Use a value from one to six to specify the
priority level. Use the monitor SHOW JOBS
command or the RESORC /J option to list the
current job levels.

?KMON-F-Invalid set parameter

An invalid parameter was used in the
SET command.

The parameter specified in the command

Check for a typing error in the command
line. Make sure that valid arguments are

used for the parameters.

line does not exist.

A NO or a value was used on a parameter
not requiring one.

?KMON-F-Invalid terminal

The terminal number specified in the SET
TT CONSOLE=n command or FRUN or
SRUN/TERMINAL option is not a valid unit
number.

Check for a typing error in the command
line. Use the SHOW command to list the currently installed devices. Correct the unit
number.

A unit number may be invalid for the following reasons:

The unit number specified is larger than
the maximum number of units supported
on the system as configured.

The unit number is assigned to a terminal
that does not exist on the hardware configuration.

The terminal specified is being used by
another job.

The terminal specified is the system console terminal.

?KMON-F-Invalid time

The TIME command argument is invalid.

Check for a typing error in the command
line. Reenter the TIME command in the correct format — TIME hh:mm:ss.

?KMON-F-Invalid value specified with option

An option was modified by an invalid value.

102

RT-11 System Message Manual

Correct the value and type the command line
again.

P?KMON-F—Job active — cannot unload JOBNAME
An attempt was made to execute an

UNLOAD command for the existing active

job JOBNAME.

Wait for the job to finish, or abort it before
unloading and starting a new job. Use the
monitor SHOW JOBS command or the
RESORC /J option to obtain a listing of current jobs.

?7KMON-F-Line too long

A command line or a line in an indirect file is
too long. This condition usually results from
too many continuation lines.

fore the handler was unlinked.

file

was

named where

command, and retype the operation. Make
sure that each command line or indirect file
line contains 200(decimal) or fewer bytes.

9KMON-F-Must type ‘R BATCH’, type /U’
An UNLOAD BA command was entered be-

2KMON-F-No file

Divide the command line into more than one

one was

expected — for example, RUN followed by
RETURN.

2KMON-F-No foreground job

A SUSPEND, RESUME, or UNLOAD F command was given, but no foreground job was
in memory.

2?«KMON-F-No room

Either an attempt to install a new device revealed no free device slots in the monitor ta-

ble or an attempt to assign a user logical
name revealed no free slots in the monitor
user name table.

9KMON-F-No such job — JOBNAME

An attempt was made to execute an

UNLOAD, SUSPEND, or RESUME command for the job JOBNAME, which does not

Run BATCH and specify the /U option to unlink the handler. BATCH automatically performs the UNLOAD BA command.

Check for a typing error in the command

line; check the format of the monitor command and try the operation again, inserting
the proper file name.

Check for a typing error in the command

line. Enter a command that does not require
a foreground job.

Remove a device from the system and install
the new device, or deassign a user logical

name before assigning the new logical name.
Use the SHOW command to display the
status of the devices on the system.

Check for a typing error in the job name. Use

the SHOW JOBS command to list the current

jobs with their status.

exist.

2KMON-F-No such job or device — JOBNAME/DEVICENAME
An attempt was made to unload a job
(JOBNAME) or device (DEVICENAME) that
does not exist. This message appears only on
systems with system job support.

Verify that you typed the job name or device
name correctly. Use the SHOW JOBS or

SHOW DEVICES command to obtain a list of
current jobs or devices for your system.

Version 5.1, July 1984

RT-11 System Message Manual 103

?KMON-F-Output error DEV:FILENAM.TYP
An output error occurred either while a .REL
file was being written during FRUN or
SRUN command processing or while a SAVE

Verify that the system device is write-en-

abled. Check the procedures for recovery
from hard error conditions listed in Section

command was executing.

2.0.

?KMON-F-Parameters
Bad parameters were typed to the SAVE

Check for a typing error in the command
line. Check the format of the SAVE command and enter it again.

command.

?KMON-F-Protected file already exists DEV:FILNAM

.TYP

A protected file with the same name as the

file name specified with
already exists.

Use a different name to create a new file.

a SAVE command

?KMON-F-Six system jobs already running —

cannot SRUN job

An attempt was made to execute an SRUN

Wait for a job to finish before running the

command when the maximum number of

new job with SRUN.

jobs — six — was already running.

?KMON-F-SY: write-locked DEV:FILNAM.TYP
A SET command failed because the system
volume is write-protected.

Make sure the system device and volume are
write-enabled and reissue the SET comma
nd.

?KMON-F-Too many files
Too many files were specified for I/O in the

command line.

Refer to the RT—-11 System User's Guide for

restrictions on file specifications.

?KMON-U-Command file I'O error
An I/O error occurred while an indirect file
was being read. This is probably a hardware

malfunction.

Check the procedures for recovery from hard

error conditions listed in Section 2.0.

?KMON-U-Overlay read error
A hardware error occurred while a KMON
overlay, used to process the current command, was being read. This indicates that a

bad block is in the system file in question, or
that the system volume has been removed.

Check the procedures for recovery from hard

error conditions listed in Section 2.0.
Try

bootstrapping a different monitor file with
the BOOT command. Replace the system volume.

?KMON-U-System input error
A hard input error condition occurred on the

system device either while the system swap

area was being read or while the scroller code
was being read from the monitor file.

Version 5.1, July 1984

104

RT-11 System Message Manual

Check the procedures for recovery from hard

error conditions listed in Section 2.0.

?KMON-U-System output error

A hard output error condition occurred on the

system device while the system swap area
was being written.

Verify that the system device is write-en-

abled. Check the procedures for recovery
from hard error conditions listed in Section
2.0.

?2KMON-U-System output error DEV:FILNAM.TYP

A hard error condition occurred as a result of
a SET command while the indicated system
file was being output.

?KMON-W-Already installed/assigned DEV:

The device specified already exists in the system tables.

7KMON-W-Device not installed DEV:

An attempt was made to remove a device
that is not installed in the system table.

Verify that the system device is write-enabled. Check the procedures for recovery
from hard error conditions listed in Section
2.0.

Remove the device or deassign the device
name. Then install the new handler.
Verify that the device name was typed correctly. Use the SHOW command to determine which handlers are installed.

9KMON-W-File created; protected file already exists DEV:FILNAM.TYP
List the directory, unsorted. If the unproA protected file exists, along with a newly
tected file appears before the protected file in
created unprotected file of the same name.

the directory listing, either delete or rename
it. If the protected file appears first, either

rename it or change the protection code with
the monitor UNPROTECT command or the
PIP /Z option.

?KMON-W-Logical name not found DEV:

The logical device name in the DEASSIGN
command is unknown to the system.

Check for a typing error in the command
line. Use the SHOW command to list the

physical and logical device names currently
known to the system.

2KMON-W-No clock

No KW11 clock is available for the TIME
command.

2KMON-W-No date

The date was requested, but it had not yet
been set.

?LD-F-/C not specified alone

The /C option was specified with another option in the command line. This option cannot
be specified with any other option.

= The TIME command cannot be used on the
|

system.

Enter the date, using the format DATE ddmmm-yy.

Make sure that the /C option is not specified
with any other options. Enter the command
again.

RT-11 System Message Manual

105

?LD-F-Device not installed DEV:

The device specified does not have an in-

stalled handler.

Install the specified device and reenter the

command, or reenter the command, specify-

ing a device that is installed.

?LD-F-Fetch error
1.

A serious LD or system internal error occurred. The copy of LD, the monitor file,

or the specified device handler may be
corrupted on disk.
2.

The in-core copy of LD or the monitor
may be corrupted.

Reboot the system and retry the operation. If
the error occurs again, get a new copy of LD

and the specified device handler. Try the operation again. If the error persists, submit an

SPR to DIGITAL.

?LD-F-File not found DEV:FILNAM.TYP
The input file specified was not found.

Check for a typing error in the command
line. Make sure that the specified file resides

on the specified device. Enter the command
again.

?LD-F-Insufficient memory
Not enough memory is available to complete
the requested operation.

Refer to Section 3.0 for information on how to
increase memory space.

?LD-F-Invalid command

The command line typed is not valid.

Check for a typing error in the command line
and make sure that the command is in the

correct format. Enter the command again.

?LD-F-Invalid device DEV:

The device specified in the command line is
invalid. Only RT-11 directory-structured devices can be specified in LD commands.

Check for a typing error in the command
line. Verify that the device indicated is a

valid RT-11 directory-structured device.

?LD-F-Lookup for LD failed
An internal logic error occurred or LD.SYS
was renamed.

Verify that LD.SYS is on the system volume.
If it is not, copy LD.SYS from the distribu-

tion volume to the working system volume. If
it is, submit an SPR to DIGITAL.

?LD-F-No

file specified

‘The command line specified a device without
a file name.

Make sure that a file name is specified in the

command line, and try the operation again.

?LD-F-Only 1 option per SET allowed

More than one option was specified in the
same SET LDn command.

Reenter the command, using one option for
each SET LDn command.

?LD-F-.SpFun to LD failed
An internal logic error occurred.

106

RT-11 System Message Manual

Submit an SPR to DIGITAL.

2LD-F-Switch value out of range (0-7) /val
A value outside the range 0 to 7 was specified
for a switch operation.

?LD-F-Switch without required value
A switch was specified without a valid value.

?LD-F-SY: write-locked SY:LD.SYS
The LD handler could not be updated when
RT-11 was bootstrapped because the system
device was write-locked or the system volume

Check for a typing error. Retype the command, using a switch value in the range 0 to
7.

Retry the operation, using a valid switch
value.

Make sure the system device and system volume are write-enabled. Bootstrap the system
again.

was write-protected.

?LD-F-Unable to protect file DEV:FILNAM.TYP
Make sure that the output device is writeAn attempt was made to protect a file and
enabled, and try the operation again.
the operation failed because the output device is write-locked.

?LD-F-Unable to update LD handler

An internal error occurred.

Retry the operation that produced the error.

If the error persists, submit an SPR to
DIGITAL; include with the SPR a program
listing and a machine-readable source program, if possible.

Version 5.1, July 1984

RT-11 System Message Manual

106.1

?LD-F-Unit (n of LDn) not specified

A unit number (n) was not specified in LDn
of the SET LDn FREE or the SET LDn

Specify a unit number (n) in LDn of the SET
command. Try the operation again.

[NOIWRITE command.

?LD-F-Unknown switch (/C, /L, /R, or /W only)
Enter the command again, using a valid
A switch other than /C, /L, /R, or /W was
specified.

?LD-F-WritW to LD.SYS failed
The operation failed because the system device is write-locked.

switch.

Make sure that the system device is writeenabled, and try the operation again.

?LD-W-/W and /R specified for same unit, /W ignored
Reenter the command line, specifying differ/W:n and /R:n were specified in the command
line with the same unit n.

ent units with the /W and the /R options.

?LIBR-F-EOF during extract

The end of the input file was reached before
the end of the module being extracted was
reached.

?LIBR-F-File not found DEV:FILNAM.TYP
One of the input files specified in the command line was not found. The CSI program
prints an asterisk.

?LIBR-F-Input error in DEV:FILNAM.TYP
An unrecoverable error occurred during the
processing of an input file. The CSI prints an
asterisk and waits for another command to

The object module format is probably incorrect. Rebuild the library file. If the error persists, reassemble the object module(s) belonging to that file.

Check for a typing error in the command
line. Verify that the file name exists as entered in the command line, and try the operation again.

Check the procedures for recovery from hard
error conditions listed in Section 2.0.

be entered.

?LIBR-F-Insufficient memory

Available memory is used up. The current
command is aborted.

Refer to Section 3.0 for information on how to
increase memory space.

?LIBR-F-Internal error

An internal error occurred while the librar-

ian was recovering from a previous system or
user error.

Retry the operations that produced this error;
if the error persists, submit an SPR to DIGITAL; include a program listing and a machine-readable source program, if possible.

RT-11 System Message Manual

107

?LIBR~F-Invalid device DEV:

The device specified is not available.

Verify that the device is valid for the system

in use.

?LIBR-F-Invalid GSD in DEV:FILNAM.TYP
The global symbol directory (GSD) contains
an error. The file specified is probably not a

valid object module.

Verify that the correct file names were specified as input; check for a typing error in the

command line. Reassemble or recompile the

source to get a good object module, and try

the operation again.

?LIBR-F-Invalid input file DEV:FILNAM.TYP
A file other than a form library file or a form
descriptor file was given as input when a
form (/F) library was being created.

Make sure that the input file name is entered
correctly and that the file is a valid one.

?LIBR-F-Invalid library for listing or extract
The input file specified either for extraction
or to produce a directory listing is not a valid

object library file.

Verify the file name in the command line and
check for a typing error. It may be necessary

to rebuild the input file.

- ?LIBR-F-Invalid option: /x
The librarian did not recognize the given
option — /x represents the unrecognized option. The librarian restarts and prompts with

an asterisk.

Check for a typing error in the command
line. Verify that the option is valid for the
librarian, and try the operation again.

?LIBR-F-Invalid option combination
The options specified request conflicting
functions to be performed. For example, if /E
or /EXTRACT is specified, no other option

Correct the logic of the command line, if necessary. Check for a typing error, and retry
the operation.

may be used. If /M or /MACRO is specified,
continuation options — /C, //, or
/PROMPT may follow.
only

?LIBR-F-Invalid record type in DEV:FILNAM.TYP
A formatted binary record had a type not in
the range 1 to 10(octal).

Verify that the correct file names were specified as input; check for a typing error in the
command line. Reassemble or recompile the

source to obtain a good object module, and
retry the operation.

?LIBR-F-Macro name table full, use /M:n
The number of macros to be placed in the
macro name table is greater than the number

allowed.

?LIBR-F-No value allowed:

The specified option (/x) does not take a
value. The librarian restarts and prompts
with an asterisk.

108

Increase the size of the macro name table by
supplying a value (n) to the option /M:n. the
default is 128 names.

RT-11 System Message Manual

Check for typing errors; verify that the correct option has been specified in the command line, and try the operation again.

?LIBR-F-Output and input filenames the same
The same file name was specified for both input and output files in the command string to

build the macro library.

Use different file names for the input and
output files specified to build a macro library.
The input and output file type is .MAC.

?LIBR-F-Output device full DEV:FILNAM.TYP
The device is full; LIBR was unable to create
or to update the indicated library file.

Refer to Section 3.0 for information on how to
increase storage space.

?LIBR-F-Output error DEV:FILNAM.TYP
The LIBR program detected an unrecover-

Refer to Section 3.0 for information on how to

able error while processing an output file.
This may indicate that not enough space is
left on a device to create a file, although
enough directory entries may be left.

increase storage space.

?LIBR-F-Output file full

The output file is not large enough to hold
the library file or the list file.

Increase the output file size with either the
monitor /ALLOCATE command or the out-

put-filespec[:n] construction; otherwise, increase the free space on the output device.

?LIBR-F-Protected file already exists DEV:FILNAM.TYP

An attempt was made to open an output file
using ENTER with a name already assigned
to a protected file.

Use the monitor UNPROTECT command or
the PIP /Z option to change the protection
level of the existing file, or use a different
name to open a new file.

?LIBR-F-/R or /U given on library file DEV:FILNAM.TYP

A /R or /REPLACE or a /U or /UPDATE option incorrectly followed the specified library
file in the command string.

Use the /R or /REPLACE options or /U or
[UPDATE options only after input file names
containing modules for replacement or updating. Correct and reenter the command
string.

?LIBR-F-/U given on library file DEV:FILNAM.TYP
The /U option or the monitor LIBRARY/UPDATE command has incorrectly modified a
forms library file.

Use the monitor LIBRARY/UPDATE command or the /U option only after input file
names containing modules for replacement
or updating.

?LIBR-W-Duplicate form name of FORMNM
Two forms having the same name were specified as input, and the /U option or the moni-

tor LIBRARY/UPDATE command was not

Use the monitor LIBRARY/UPDATE command or the /U option to update a form of the
same name as a previously specified file.

given on the second form. The first form encountered was put in the output file; all du-

plicates are ignored.

RT-11 System Message Manual

109

?LIBR-W-Duplicate macro name of MACNAM
Two macros of the same name were specified

Make all macro names unique.

as input. The first macro encountered is put

in the output file; all duplicates are ignored.

?LIBR-W-Duplicate module name of AAAAAA
A new module inserted in a library has the
same name as a module that is already in the
library. The librarian does not reenter the
name in the directory. The old module is not
updated or replaced.

For the librarian program, insertion is the
default operation and no command option is
needed; the option for update is /U, and the
option for replacement is /R.
For the keyboard monitor LIBRARY command, /INSERT puts the duplicate name in
the module; /UPDATE and /REPLACE are
not possible operations in this case.

?LIBR-W-File created; protected file already exists DEV:FILNAM.TYP
A protected file exists, along with a newly

created unprotected file of the same name.

List the directory, unsorted. If the unprotected file appears before the protected file in
the directory listing, either delete or rename

it. If the protected file appears first, either
rename it or change the protection code with

the monitor UNPROTECT command or the
PIP /Z option.

?LIBR-W-Invalid character
The symbol name entered contains an invalid
character.

Retype the command line, using Radix-50
characters only, and try the operation again.

?LIBR-W-Invalid delete of AAAAAA
An attempt was made to delete a module or a
nonexistent entry point from the library’s directory; AAAAAA represents the module or
entry point name. The entry point name or
module name is ignored, and processing continues.

Check for a typing error in the command
line.

LIBR-W-Invalid extract of AAAAAA
An extraction of the identified global symbol
was attempted, but the symbol was not found
in the library.

Check the command string and the contents
of the library file for the correct library file
and global symbol specifications.

?LIBR-W-Invalid insert of AAAAAA

An attempt was made to insert into a library
a module that contains the same entry point
as an existing module. AAAAAA represents
the entry point name. The entry point is ig-

nored, but the module is still inserted into
the library.

110

RT-11 System Message Manual

No user action is necessary.

2LIBR-W-Invalid replacement of AAAAAA
An attempt was made to replace in the library file a nonexistent module. AAAAAA
represents the module name. The module is
ignored, and the library is built without it.

?LIBR-W-Null library

An attempt was made to build a library file
containing no directory entries.

Review the module names in the library file.

Make sure that the correct module was specified.

Verify that the correct file names were specified as input; check for a typing error in the
command line. Verify that the input to the
library has at least one directory entry.

?LIBR-W-Only continuation allowed
A command string was entered beyond the
end of the current line without the use of a

Enter a /C option or / (PROMPT) at the end
of the current line.

continuation character.

7LINK-F-Address space exceeded
The high limit of all program sections exceeded 32K words when all sections were
concatenated.

Reduce the size of the program by using overlays, by reducing the size of the root segment,
and/or by reducing the size of the largest segment within each overlay region. Refer to
Section 3.0 for information on how to increase memory resources.

?LINK-F-ASECT too big

An absolute section overlaps an occupied
area of memory or an overlay region.

?LINK-F—-/B no value

No argument was specified with the /B or the
/BOTTOM option.

?LINK-F-/B odd value

The argument specified with the /B or the
/BOTTOM option is not an unsigned even octal number.

Locate a segment of available memory large
enough to contain the absolute section, and
substitute the appropriate starting address.
Reenter the command string, specifying an
unsigned even octal number as the argument
to the /B or the monitor /BOTTOM option.
Reenter the command string, specifying an
unsigned even octal number as the argument
with the /B or the monitor /BOTTOM option.

2LINK-F-Cross reference device full DEV:FILNAM.TYP
Either the directory does not have enough
room for the file name or the output device
does not have enough room for the cross ref-

Refer to Section 3.0 for information on how to
ase storage space.

erence temporary file.

?LINK-F—/E no value

No argument was specified with the /E or the
/EXTEND option.

Reenter the command string specifying an
unsigned even octal number as the argument
with the /E or the monitor /EXTEND option.

RT-11 System Message Manual

111

?LINK-F-/E odd value
The argument specified with the /E or the
/EXTEND option is not an unsigned even octal number.

Reenter the command string, specifying an

unsigned even octal number as the argument

with the /E or the monitor /EXTEND option.

?LINK-F-/H no value
No argument was specified with the /H or the
/TOP option.

Reenter the command string specifying an
unsigned even octal number as the argument

with the /H or the monitor /TOP option.

?LINK-F—/H odd value

The argument specified with the /H or the
/TOP option is not an unsigned even octal
number.

Reenter the command string, specifying an

unsigned even octal number as the argument

with the /H or the monitor /TOP option.

?LINK-F—/H value too low

The value specified as the high address for
linking is too small to accommodate the code.

Obtain map output without using the /H or
the /TOP option to determine the space re-

quired, and try the operation again.

?LINK-F-Input error DEV:FILNAM.TYP
A hardware error occurred while the indicated input file was being read.

Check the procedures for recovery from hard

error conditions listed in Section 2.0.

?LINK-F-Insufficient memory
Not enough memory is available to accommodate the command, the symbol table, or the
resultant load module.

Refer to Section 3.0 for information on how to
increase memory space.

?LINK-F-Internal error
An internal error occurred while the linker
was recovering from a previous system or

user error.

Retry the operations that produced this error;
if it occurs again, submit an SPR to DIGITAL; include a program listing and a machine-readable source program, if possible.

?LINK-F-Invalid character

The character specified was not used in the

proper context.

Examine the command string for errors in

syntax, making sure that the characters for

symbols are valid Radix—50 characters. Correct and retype the command.

?LINK-F-Invalid complex relocation in DEV:FILNAM.TYP
During pass 2 of the linker, a complex reloca-

tion string in the input file was found to be
invalid.

Check for a typing error in the command
line; verify that the correct file names were
specified as input. Reassemble or recompile

to obtain a good object module and retry the

operation. If the error persists, verify
that

the source code is correct.

112

RT-11 System Message Manual

?LINK-F-Invalid device DEV:

The volume indicated is not available.

Verify that the device is valid for the system
in use.

?LINK-F-Invalid GSD in DEV:FILNAM.TYP
The global symbol directory (GSD) contains
an error. The file is probably not a valid object module.

Verify that the correct file names were specified as input; check for a typing error in the
command line. Reassemble or recompile the
source code to obtain a good object module,
then try the operation again.

?LINK-F-Invalid record type in DEV:FILNAM.TYP
A formatted binary record has a type not in
the range 1 to 10(octal).

Verify that the correct file names were specified as input; check for a typing error in the

command line. Reassemble or recompile the
source code to obtain a good object module,
and try the operation again.

?LINK-F-Invalid RLD in DEV:FILNAM.TYP

The input file contains an invalid relocation
directory (RLD) command. The file is probably not a valid input module.

Verify that the correct file names were specified as input; check for a typing error in the
command line. Reassemble or recompile to

obtain a good object module, and try the operation again. If the error persists, check the
source code to make sure that all modules
contributing to a data p-sect are wordaligned.

?LINK-F-Invalid RLD symbol in DEV:FILNAM.TYP
A global symbol named in a relocatable record was not defined in the global symbol definition record, resulting in an error in the language processor.

Reassemble the indicated file. If the condition persists, submit an SPR to DIGITAL; include with the SPR a program listing and a
machine-readable source program, if possible.

?LINK-F-/K invalid value

The argument specified with the /K or the
/LIMIT option is not in the range 2 to 28(decimal).

Reenter the command string, specifying a
valid unsigned even octal number as the argument with the /K or the monitor /LIMIT
option.

?LINK-F-/K no value

No argument was specified with the /K or the
/LIMIT option.

Reenter the command string, specifying an
unsigned even octal number as the argument
with the /K or the monitor /LIMIT option.

?LINK-F-Library EPT too big, increase buffer with /G

The /G option was not specified and a /X library with too large an Entry Point Table

Relink and issue the /G option on the first
input line.

was encountered.

RT-11 System Message Manual

113

?LINK-F-Library list overflow, increase size with /P
The maximum number of library routines for
the linker was exceeded.

Relink the program that uses the library
routines. The /P:n option default is 170 (decimal). Increase the size of the list by specifying a size greater than the default.

?7LINK-F-/M odd value

An odd value was specified for the stack address.

Check for a typing error in the command
line. Reenter the command, specifying an
even value with the /M or the /STACK option.

?LINK-F-Map device full DEV:FILENAM.TYP
Either the directory does not have enough
room for the file name or the output device
does not have enough room for the map file.

Refer to Section 3.0 for information on how to
increase storage space.

?LINK-F-0Ild library format in DEV:FILNAM.TYP
The format of the library file is outdated
(previous to Version 3B).

Rebuild the library file using the current librarian and the command format
LIBRARY/CREATE newlib oldlib for an object library.

?LINK-F-Protected file already exists DEV:FILNAM.TYP
An attempt was made to open a file with a
name already assigned to an existing protected file.

Use the monitor UNPROTECT command or
the PIP /Z option to change the protection
level of the existing file, or use a different
name to open a new file.

?LINK-F-/R odd value

The argument specified with the /R or the
/FOREGROUND option is not an unsigned

even octal number.

Reenter the command string, specifying an
unsigned even octal number as the argument

with the /R or the monitor /FOREGROUND
option.

?LINK-F-REL write beyond EOF
The relocation information section of an REL
file overflowed when an entire load module
required relocation.

Use a square bracket construction or the /ALLOCATE option to enclose a number twice
the size of the resulting .SAV file.

?LINK-F-SAYV device full DEV:FILENAM.TYP
Either the directory does not have room for
the file name or the output device does not
have room for the image file (SAV, REL).

Refer to Section 3.0 for information on how to
increase storage space.

?LINK-F-SAY read error
A hardware error occurred while LINK was
reading the image file (SAV, LDA, or REL).

114

RT-11 System Message Manual

Check the procedures for recovery from hard
error conditions listed in Section 2.0.

?LINK-F-SAYV write error

A hardware error occurred while LINK was
writing the image file (SAV, LDA, or REL).

2LINK-F-Size overflow of section AAAAAA

The program section in question increased
program size to more than 32K words.
?LINK-F-STB device full DEV:FILNAM.TYP
Either the directory does not have room for
the file name or the output device does not
have room for the symbol table (STB) file.

2LINK-F-STB not allowed with /S and a map
The /S or the /SLOWLY option was used to
produce STB and MAP files in the same link-

Check the procedures for recovery from hard
error conditions listed in Section 2.0.

Reduce the size of the program either in this
section or elsewhere in the program.

Refer to Section 3.0 for information on how to
increase storage space.

Produce STB and MAP files in separate linking operations.

ing operation.

?7LINK-F-STB write error

A hardware error occurred while the symbol

table (STB) file was being written.

9LINK-F-Storing text beyond high limit
1. An input object module may have caused
the linker to store information in the image file beyond the high limit of the pro-

Check the procedures for recovery from hard
error conditions listed in Section 2.0.

1. Reassemble or recompile the program.

gram,; if so, the object module has an error condition.

9. If an LDA file was being produced, the

output device did not have enough room
for the output file.

?LINK-F-Symbol table overflow

Too many global symbols were used in the
program.

2. Specify a larger output file size, or refer

to Section 3.0 for information on how to
increase storage space.

Try to link again using the /S or the monitor
LINK/SLOWLY command. If the error re-

curs, reduce the size of the library list, using
the /S and the /P:n options, with a value less
than the default. If the error persists, the
link cannot take place in the available memory. Refer to Section 3.0 for information on
how to increase memory space.

?LINK-F-/T odd value

An odd value was specified for the transfer
address.

2LINK-F-Too many program segments
More than 1777(octal) program segments
were specified.

Check for a typing error in the command
line. Reenter the command, specifying an
even value to the /T or the monitor /TRANS|
FER option.
Restructure the overlays to reduce the number of segments.

RT-11 System Message Manual 115

?LINK-F-Too many virtual overlay regions
More than eight extended memory overlay
regions (windows), including the root, were
in use for extended memory jobs.

Reorganize the extended memory overl
ay

structure to use eight or fewer memo

ry over-

lay regions, including the root.

?LINK-F-/U or /Y value not a power of 2
The value specified with the /U, the monitor
/ROUND, the /Y, or the monitor /BOUNDARY option is not a power of 2.

Reenter the command with a value that

positive power of 2.

is a

?LINK-F-Word relocation error in FILNAM
During concatenation of data p-sects, a word
reference was moved to an odd byte.

Place the .EVEN assembler directive
at the
end of data p-sects to make sure that all
word
references in data p-sects will be on a
word
boundary when relocated by LINK.

?LINK-F—/Y no value
No argument was specified with the /Y or the
/BOUNDARY option.

Reenter the command string, specifying
a

positive power of 2 as the argument

with the

/Y or the monitor BOUNDARY optio

?LINK-F-/Y odd value
An odd value was specified as the argument
with the /Y or the /BOUNDARY option.

Reenter the command string, speci
fying a
value that is a positive power of 2 as
the ar-

gument with the /Y or the monitor

ARY option.

?LINK-F-Virtual overlay logical address

/BOUND.WMW”‘“‘?‘&;

space exceeded

The virtual overlays in the program required

more than 96K words of extended memory.

Reorganize the overlays to use less exten

memory. See the LINK chapter in the

ded

RT-11

System Utilities Manual for more infor
mation about the extended memory overl
ay option.

?LINK-W-Additive reference of NNNNNN

at segment # MMMMMM

A call or a branch to an overlay segment was

not made directly to an entry point in the
segment. NNNNNN represents the entry
point; MMMMMM represents the segment

number.

Make sure that calls or branches to
segments are made directly to entry

overlay

points in

the segment. See the RT-11 System Utilit
ies
Manual for more information about
using
overlays.

?LINK-W-Boundary section not found
Either the program section name specified as
a boundary section with the /Y or the option

/BOUNDARY was not found in the modules
that were linked or the program section does

not exist in the root segment. The linker con-

tinues after the warning without changing
the program section.

116

RT-11 System Message Manual

Check the responses to the Boundary

prompt and correct the section name

time you link.

section?
the next

?LINK-W-Byte relocation error at NNNNNN
The linker tried to relocate and link byte
quantities, but failed because the high byte
of the relocated value (or the linked value)
was not all zeros. NNNNNN represents the
address at which the error occurred.

Correct the source program so that no byte
quantities are relocated. Reassemble and re-

link.

The relocated value is truncated to eight bits,
and the linker continues processing for SAV
and LDA files. For REL files no truncation is
performed, and processing continues.

?LINK-W-Complex relocation divide by 0 in DEV:FILNAM.TYP
An attempt was made to divide by 0 in a com-

plex relocation string in the specified file. A

Check the logic in the relocation string of the
program.

result of 0 is returned, and linking continues.

?LINK-W-Complex relocation of AAAAAA

The complex relocation of global symbols was
indicated for the linker in the foreground.

Examine the assembly listing. Edit the program to remove all complex expressions that

contain relocatable symbols. The MACRO assembler tags such occurrences with a C in
the binary contents column of the listing.

?LINK-W-Conflicting section attributes AAAAAA
The program section symbol is defined with
different attributes. The attributes of the
first definition are used and the linking pro-

Check the source program and use the desired section attributes for that program section.

cess continues.

?LINK-W-Cross reference input error

A hardware error occurred while the crossreference temporary file was being read. The
cross-reference portion of the map output is
eliminated, and the linking process contin-

Check the procedures for recovery from hard
error conditions listed in Section 2.0.

ues.

?LINK-W-Cross reference output error

A hardware error occurred while the crossreference temporary file was being written.
The cross-reference portion of the map output
is eliminated, and the linking process contin-

Check the procedures for recovery from hard
error conditions listed in Section 2.0.

ues.

RT-11 System Message Manual

117

?LINK-W-Default system library not found SYSLIB.OBJ

The linker did not find SYSLIB.OBJ on the
system device when undefined globals existed or when overlays were being used.

Get a copy of SYSLIB.OBJ from the backup
system volume and relink the program, or
correct the source files by removing the undefined globals listed on the terminal. The
RT-11 Installation Guide contains instruc-

tions for tailoring SYSLIB to meet various
needs. The current version of SYSLIB contains the overlay handlers, which are required when overlays are specified.

?LINK--»WmDuplicate symbol SYMBOL defined in DEV:FILNAM.TYP
An attempt was made to define a duplicate
symbol with the /D option, using nonlibrary
modules. The symbol is made nonduplicate,
and the definition is allowed to stand.

Avoid duplicating the module that contains
the symbol, represented by SYMBOL, by not
responding to the Duplicate symbol? query
with that symbol. Alternatively, duplicate
the module that contains SYMBOL by placing the module in an object library and specifying it as a library to LINK.

?LINK-W-Duplicate symbol SYMBOL is forced to the root
A module containing duplicate global symbols was forced to reside in the root, and the
symbol is made nonduplicate.

Avoid duplicating the module that contains
the symbol, represented by SYMBOL, by not
responding to the Duplicate symbol? query
with that symbol. Alternatively, eliminate

any references to SYMBOL from the root.

7LINK-W-Extend section not found
Either the extend section name given with
‘the /E or the monitor LINK/EXTEND command was not found in the modules linked or
the extend section did not exist in the root
segment. The linker continues after the
warning, without extending the section.

Check the response to the Extend section?
query, and correct the section name before

linking again.

?LINK-W-File created; protected file already exists DEV:FILNAM.TYP
A protected file exists, along with a newly
created unprotected file of the same name.

List the directory, unsorted. If the unprotected file appears before the protected file in

the directory listing, either delete or rename
it. If the protected file appears first, either
rename it or change the protection code with
the monitor RENAME/NOPROTECT command or the PIP /Z option.
?LINK-W-File not found DEV:FILNAM.TYP

The input file specified was not found.

The LINK or the EXECUTE command
was issued in response to the keyboard
monitor prompt, and a file specified in
the first line of the command was not
found. LINK exits and the keyboard
monitor prompt returns.

118

RT-11 System Message Manual

Check for a typing error in the command
line. Verify that the file name exists as entered in the command line, and try the operation again.

3. A file specified on a continuation line of
the LINK or the EXECUTE command
was not found. LINK reprompts for another file specification.

?LINK-W-Invalid option: /x

Either the linker did not recognize the option
(/x) specified in the command line or an invalid combination of options was used.

If the invalid option occurred in the first command line, control returns to the CSI; enter
another command. If the invalid option occurred on a subsequent command line, the
option is ignored and processing continues. In
a continued command line, make sure that

the only options used are /O, /V, /C, and //.
Valid linker options are listed in the RT-11
System Utilities Manual. Reexamine the
command line and check for a typing error.

?LINK-W-Load address odd

An odd load address was specified with the /Q

Reenter the line with an even address.

option.

?LINK-W-Load address too low PSECT
The load address specified for the p-sect is too
low. The p-sect was ignored to avoid overlay-

Relink and specify a higher load address for
the p-sect.

ing code in a previous section.

LINK continues execution without loading
the p-sect at the specified address.
NK-W-Load section not found PSECT

The load section specified was not found in
the root. LINK continues execution, ignoring
the p-sect that was not found.
?LINK-W-Map write error

A hardware error occurred while the map
output file was being written. The map output is terminated and the linking process

Reorder the modules to place the p-sect containing the load section in the root, then relink.

Check the procedures for recovery from hard

error conditions listed in Section 2.0.

continues.

?LINK-W-Multiple definition of SYMBOL
The symbol indicated was defined more than
once. Extra definitions are ignored.
?LINK-W-No load address

No address was specified with the /Q option.

Make sure that each symbol is defined only
once.

Reenter the command line and specify a load
address.

?LINK-W-/O or /V option error, re-enter line
An error was made in the use of the /O or the

/V option. There are four probable causes:
e

A /O option appears after a /V option.

No value was given with a /O or /V option.

An incorrect value was given.

A /O or a /V option was used with the /L

Check the context and reenter the line.

option.

?LINK-W-Round section not found AAAAAA
The symbol representing the program section
specified with the /U or the monitor ROUND
option was not found in the symbol table.
Linking continues with no round-up action.

Check the source to make sure that the symbol is globally defined.

?LINK-W-Stack address undefined or in overlay

The stack address specified by the /M or the
monitor /STACK option was either undefined
or in an overlay. For SAYV files, the stack address is set to the default, 1000. For REL
files, the default is 0 and will be revised
when the file is run in the foreground.

Check for a typing error in the command
line. Verify that the stack address or the
global symbol is not defined in an overlay
segment.

?LINK-W-Transfer address undefined or in overlay
The transfer address is not defined or is in an
overlay.

Check for a typing error in the command
line. Respond to the /T or the monitor
LINK/TRANSFER command either with a
colon followed by an unsigned six-digit octal

number or with a carriage return followed by
the global symbol whose value is the transfer

address of the load module.

?LINK-W-Undefined globals:
The globals listed are undefined because
SYSLIB is not present and overlays are used.

Check for a typing error in the command
line. The undefined globals are listed on the
terminal and also in the link map when requested. Correct the source program. Verify

that all necessary object modules are indicated in the command line or are present in
the libraries specified. See the RT-11 Installation Guide for instructions on tailoring
SYSLIB.

MACRO messages

Section 8.0 contains all MACRO-11 messages.

120

RT-11 System Message Manual

?MDUP-F-Bad block in system area DEV:

A bad block was found in a critical area of
the disk, making the volume unusable.

Reformat the volume, if possible. Try the operation again. If the error persists, the volume must be replaced.

?MDUP-F-Channel in use DEV:FILNAM.TYP
An internal MDUP error occurred.

Reboot the system and try the operation
again. If the error persists, submit an SPR to
DIGITAL; include with the SPR a program
listing and a machine-readable source program, if possible.

"MDUP-F-Conflicting SYSGEN options

The system device handler and the monitor
file have different SYSGEN options enabled.
This conflict prevents further processing.

Refer to the RT-11 Installation Guide for details about the MDUP system program.

?MDUP-F-Directory I/0O error DEV:FILNAM.TYP

An error occurred while MDUP was reading
the directory of the specified device.

Check the procedures for recovery from hard
error conditions listed in Section 2.0. Try the
operation again. If the error persists, reformat the volume. If the error still occurs, replace the volume.

?MDUP-F-Directory input error DEV:

An error occurred while the directory of the
specified device was being read.

Check the procedures for recovery from hard
error conditions listed in Section 2.0. Try the
operation again. If the error persists, reformat the volume. If the error still occurs, replace the volume.

MDUP-F-Directory output error DEV:

An error occurred while the directory of the
specified device was being written.

Check the procedures for recovery from hard
error conditions listed in Section 2.0. Try the
operation again. If the error persists, reformat the volume. If the error still occurs, replace the volume.

?MDUP-F-Error reading bad block replacement table DEV:

An input error occurred while MDUP was
reading the bad-block replacement table in
block 1, the home block of the specified volume.

Check for bad blocks on the volume. If the
home block is bad, the volume is unusable
and must be replaced. Check the procedures
for recovery from hard error conditions listed
in Section 2.0.

?MDUP-F-File not found DEV:FILNAM.TYP
The specified file was not found.

Check for a typing error in the command
line. Try the operation again.

?MDUP-F-Input error DEV:FILNAM.TYP

A hardware error occurred during a read operation.

Check the procedures for recovery from hard
error conditions listed in Section 2.0.

RT-11 System Message Manual

121

"MDUP-F-Insufficient memory
Not enough memory is available to complete
the requested operation.

Make sure that there are at least 12K words
of memory for the requested operation. See
the section on the MDUP.SAV program contained in the RT-11 Installation Guide.

?MDUP-F-Invalid command
1.

The command entered is invalid.

The format of the command line is incorrect.
'

An invalid combination of options was
specified.

A device may not be valid for the re-

Check for a typing error in the command
line. Check the format of the command line.
Refer to the section on DUP in the RT-11
System Utilities Manual or to the RT-11 System User’s Guide for a list of valid option
combinations. Make sure that the device
specified is valid for the requested operation.

quested operation.

?MDUP-F-Invalid device DEV:
The specified device is not supported for use

with MDUP.

Check for a typing error in the command
line. See the RT-11 Installation Guide for
the list of devices supported by MDUP.

MDUP-F-Invalid directory DEV:
The volume in the specified device does not
contain a valid RT-11 directory structure.

Initialize the volume before using it for the
first time. Review the discussion about using
the MDUP.SAV program in the RT-11 Installation Guide.

MDUP-F-Invalid option: /x
An invalid option was specified in the command line.

Check for a typing error in the command
line. Use only valid options. Refer to the section on DUP in the RT-11 System Ultilities
Manual or to the RT-11 System User’s Guide
for a list of valid options.

MDUP-F-Invalid value specified with option: /x

A value specified is outside the acceptable
range.

Check for a typing error in the command
line. Refer to the section on DUP in the
RT-11 System Utilities Manual or to the
RT-11 System User’s Guide for a list of valid

options and the range of valid values for each

option.

MDUP-F-Non-bootable driver DEV:FILNAM.TYP
The specified device handler does not contain
a valid primary bootstrap because either the
bootable magtape or the MDUP.Mx was built
incorrectly.

122

RT-11 System Message Manual

See the RT-11 Installation Guide for details

about the MDUP.SAV program.

YMDUP-F-No room for file DEV:FILNAM.TYP
Use the INITIALIZE command or the DUP /Z
The output volume does not have room for
the specified file.

option to initialize the output device before
copying the system to the output device. See
the RT-11 Installation Guide for more information.

?MDUP-F-QOutput error DEV:FILNAM.TYP
A hardware error occurred during a write operation.

?MDUP-F-Size function failed
An error occurred while DUP was determin-

ing the size of the volume mounted in a device. The monitor, the device handler, or

Check the procedures for recovery from hard
error conditions listed in Section 2.0.

Check the procedures for recovery from hard
error conditions listed in Section 2.0. Reboot
the system and try the operation again.

DUP may be corrupted.

MDUP-F-Trap to 4

An internal MDUP error occurred.

Reboot the system and try the operation
again. If the error persists, submit an SPR to

DIGITAL; include with the SPR a program
listing and a machine-readable source program, if possible.

?MDUP-F-Trap to 10

An internal MDUP error occurred.

Reboot the system and try the operation
again. If the error persists, submit an SPR to
DIGITAL; include with the SPR a program
listing and a machine-readable source program, if possible.

YMDUP-I-Bad blocks detected nnnnn.
The specified number of bad blocks was de-

tected during the bad block scan initiated by

The volume is ready to use.

the monitor INITIALIZE/BADBLOCKS command or the DUP /Z/B option.

?MDUP-I-No bad blocks detected DEV:
No bad blocks were detected during the bad
block scan initiated by the monitor
INITIALIZE/BADBLOCKS command or the
DUP /Z/B option.

The volume is ready to use.

MDUP-U-System error

An internal MDUP error occurred.

Reboot the system and try the operation

again. If the error persists, submit an SPR to

DIGITAL; include with the SPR a program
listing and a machine-readable source pro-

gram, if possible.

?MDUP-W-Too many bad blocks DEV:
More than 128 bad blocks were encountered
during a bad block scan.

The volume is unusable; reformat or replace.

?MON-F-Bad fetch
An error occurred while a device handler was
being read from SY:, the address at which
the handler was to be loaded was invalid, or
the handler to be fetched has SYSGEN options that do not match the SYSGEN options

of the monitor.

Make sure that the address at which the handler is to be loaded is not outside the bounds
of the program; also make sure that the handler is not so large that it will overflow the

program bounds — in this case, allow more

space for the handler. Examine location 60 of
the device handler and the monitor fixed offset for SYSGEN features; they should agree.

?MON-F-Dir I0 err NNNNNN

This error message is generated by only the
FB and the XM monitors. An error occurred
during I/O in the directory of a device. The
value NNNNNN is the address of the in-

Check the procedures for recovery from hard

error conditions listed in Section 2.0.

struction following the instruction or EMT

that caused the error.

?MON-F-Dir ovflo NNNNNN
This error message is generated by only the
FB and the XM monitors. No more directory
segments are available for expansion; the error occurred during file creation via .ENTER.

Refer to Section 3.0 for information on how to

increase storage space.

The value NNNNNN is the address of the

instruction following the instruction or EMT
that caused the error.

?MON-F-Directory I/0O error NNNNNN
This error message is generated by only the

SJ monitor. An error occurred during I/O in
the directory of a device. The value
NNNNNN is the address of the instruction
following the instruction or EMT that caused

the error.

124

RT-11 System Message Manual

Check the procedures for recovery from hard

error conditions listed in Section 2.0.

9MON-F-Directory overflow NNNNNN
This error message is generated by only the

SJ monitor. No more directory segments are

available for expansion; the error occurred
during file creation via .ENTER. The value
NNNNNN is the address of the instruction
following the instruction or EMT that caused

Refer to Section 3.0 for information on how to

increase storage space.

the error.

?MON-F-Directory unsafe

This error message is generated by only the
FB and the XM monitors. Along with the error message that appears immediately above
it, this message indicates that an I/0 error
occurred while the USR was updating a de-

Examine the device directory carefully for

lost files. Check the procedures for recovery
from hard error conditions listed in Section
2.0.

vice directory. The directory operation may

have failed; one or more files may have been
lost. The monitor attempts to complete the

directory operation before aborting the job.

?MON-F-FP trap NNNNNN

This error message is generated by only the

SJ monitor. A floating-point exception trap
occurred, and the user program had no
SFPA exception routine active. The job is
aborted. The value NNNNNN is the address
of the instruction following the instruction or

Examine the data for floating-point overflow
or underflow and adjust it accordingly.

EMT that caused the error.

?MON-F-FPU trap NNNNNN

This error message is generated by only the
FB and the XM monitors. A floating-point
exception trap occurred, and the user pro-

Examine the data for floating-point overflow
or underflow and adjust it accordingly.

gram had no .SFPA exception routine active.
The job is aborted. The value NNNNNN is
the address of the instruction following the
instruction or EMT that caused the error.

?MON-F-Inv addr NNNNNN

This error message is generated by only the
FB and the XM monitors. An address specified in a monitor call is odd or is not within
the job’s address space. The value NNNNNN
is the address of the instruction following the

Correct the address in error in the source
program.

instruction or EMT that caused the error.

?MON-F-Inv chan NNNNNN

This error message is generated by only the
FB and the XM monitors. A channel number
specified is too large. The value NNNNNN is
the address of the instruction following the
instruction or EMT that caused the error.

Use a valid channel number — the default
number is 16 channels — or define a larger
channel number (225 maximum), using the
.CDFN request.

RT-11 System Message Manual

125

?MON-F-Inv EMT NNNNNN
This error message is generated by only the
FB and the XM monitors. The function code
of an EMT is out of bounds. The value
NNNNNN is the address of the instruction
following the instruction or EMT that caused
the error.
?MON-F-Inv SST

Check the EMT instruction to determine the

correct code.

NNNNNN

This error message is generated by only the
XM monitor.
1.

The program has not supplied a valid
trap address for a synchronous system
trap.

Verify that valid trap addresses are supplied for synchronous system traps.

The program has not properly initialized
the trap vector before a trap instruction
(BPT, IOT, or TRAP), and the monitor
has intercepted the instruction. Zero and
odd addresses in the vector locations

Initialize the trap vector properly for
each trap instruction. If the program has

no trap instructions, check for a logic er-

ror

that is causing an inadvertent
trap — for example, improper execution

cause this error. The value NNNNNN is

of data. See the RT-11 Software Support
Manual for more information about syn-

the address of the instruction following
the instruction or EMT that caused the

chronous system traps.

error.

An internal mapping handler either has

not properly restored a kernel active
page register or has issued a device
timeout request without a .FORK.

Correct the handler logic.

?MON-F-Inv USR NNNNNN
This error message is generated by only the
FB monitor. A foreground job attempted to
load the USR at an address outside the job’s
limits. The value NNNNNN is the address of
the instruction following the instruction or
EMT that caused the error.

Make sure that jobs that issue programmed

requests requiring the USR provide an area

for the USR to swap into. This area must be
at least 2K words, wholly within the job’s upper and lower limits, and pointed to by location 46.

?MON-F-Invalid address NNNNNN
An address specified in a monitor call is odd
or is not within the job’s address space. The

value NNNNNN is the address of the instruction following the instruction or EMT

Correct the erroneous address in the source
program.

that caused the error.

?MON-F-Invalid call to USR

NNNNNN

This error message is generated by only the
SJ monitor. The USR was called from a completion routine. This error does not have a
soft return — that is, .SERR will not inhibit
this message. The value NNNNNN is the address of the instruction following the instruction or EMT that caused the error.

126

RT-11 System Message Manual

Correct the program so that the USR is not
called from within a completion routine.

2MON-F-Invalid channel NNNNNN

This error message is generated by only the
SJ monitor. A channel number specified is
too large. The value NNNNNN is the address

of the instruction following the instruction or

Use a valid channel number — the default
number is 16 channels — or define a larger
channel number (225 maximum), using the
.CDFN request.

EMT that caused the error.

MON-F-Invalid EMT NNNNNN

This error message is generated by only the
SJ monitor. The function code of an EMT is
out of bounds. The value NNNNNN is the
address of the instruction following the in-

Check the EMT instruction to determine the
correct code.

struction or EMT that caused the error.

?MON-F-INV DIR NNNNNN

This error message is generated by a DIR
hard error that is intercepted by the monitor.

?MON-F-Mem err NNNNNN

This error message is generated by only the
FB and the XM monitors. The monitor found
a memory parity error and aborted the user
program. The address NNNNNN is the value
of the program counter after the instruction
has been executed. That is, it is the address
of the instruction that caused a read of the
location with bad parity. (Memory parity

Check the procedures for recovery from hard
error conditions listed in Section 2.0.

Run the memory diagnostics and then notify
a DIGITAL field service specialist.

support must be chosen during system generation.) If the error persists or occurs at more

than one address, memory has become defective. A memory parity error in a system with
cache memory indicates failure of the main
memory, not the cache memory. Recoverable
cache errors are logged if error logging is active.

?MON-F-Memory error NNNNNN

This error message is generated by only the

SJ monitor. The monitor found a memory
parity error and aborted the user program.

Run the memory diagnostics and then notify
a DIGITAL field service specialist.

The address NNNNNN is the value of the
program counter after the instruction has
been executed. That is, it is the address of the
instruction that caused a read of the location

with bad parity. (Memory parity support

must be chosen during system generation.) If
the error persists or occurs at more than one
address, memory has become defective. A
memory parity error in a system with cache
memory indicates failure of the main mem-

ory, not the cache memory. Recoverable
cache errors are logged if error logging is active.
Version 5.1, July 1984

RT-11 System Message Manual

127

?MON-F-MMU fault NNNNNN

This error message is generated by only the

XM monitor. The program has a memory

management error in the form of a program

reference to an address that is outside the

Check the instruction that precedes address
NNNNNN and correct it. Run the program
again.

currently mapped bounds of the program.

The value NNNNNN is the address of the
instruction following the instruction or EMT
that caused the error.

?MON-F-No dev NNNNNN
This error message is generated by only the
FB and the XM monitors. A READ/WRITE

or a .LOOKUP operation was attempted, but

no handler was in memory for the device.
The value NNNNNN is the address of the

instruction following the instruction or EMT
that caused the error.

Verify that no .RELEASE was done before

the READ/WRITE operation. Make sure that

the program uses the .FETCH command to
fetch the handler, or load the appropriate
handler before running the program.

?MON-F-No device NNNNNN
This error message is generated by only the
SJ monitor. A READ/WRITE or a .LOOKUP

operation was attempted, but no handler was

memory

for

the

device.

The

value

NNNNNN is the address of the instruction

following the instruction or EMT that caused
the error.

Verify that no .RELEASE was done before
the READ/WRITE operation. Make sure that

the program uses the .FETCH command to

fetch the handler, or load the appropriate
handler before running the program.

?MON-F-Overlay error NNNNNN
This error message is generated by only the

SJ monitor. An error occurred when an overlaid user program tried to read an overlay.

The value NNNNNN is the address of the
instruction following the instruction or EMT
that caused the error.

Make sure that the program did not accidentally perform a .CLOSE or a .PURGE on
channel 15(decimal). Verify that the device
is
not off line and that the proper handler is
loaded if the overlay program is running
from other than the system device type.

?MON-F-Ovly err NNNNNN

This error message is generated by only the
FB and the XM monitors. An error occurred
when an overlaid user program tried to read
an overlay. The value NNNNNN is the ad-

dress of the instruction following the instruc-

tion or EMT that caused the error.

Make sure that the program did not accidentally perform a .CLOSE or a .PURGE on
channel 15(decimal). Verify that the device is
not off line and that the proper handle
r is
loaded if the overlay program is running

from other than the system device type.

?MON-F-Power fail halt
A power failure occurred. When power returns, the system prints the message — if

display of this message was chosen during

system generation — and halts.

128

RT-11 System Message Manual

Reboot the system.

?MON-F-Stack overflow

This error message is generated by only the
SJ monitor. A trap to 4 or to 10 occurred, and
the stack pointer is below 0400(octal).

Refer to the explanation and recovery procedures for the message ?MON-F-Trap to 4
NNNNNN.

?MON-F-Swap error

This error message is generated by only the
FB and the XM monitors. A hard error occurred while the system was attempting to
write a user program to the system swap
blocks. This may indicate that the system de-

Verify that the system device is write-enabled. Check the procedures for recovery
from hard error conditions listed in Section
2.0.

vice is write-locked.

?MON-F-System halt

This error message is generated by only the
FB and the XM monitors. An I/O error oc-

Verify that the system volume is mounted
and ready. Bootstrap a different monitor file

curred while the monitor was reading the
KMON or USR into memory. Either the system volume was dismounted or the monitor
file contained a bad block. The monitor continues to try to read the KMON after issuing

on your system volume. If the monitor file is

affected, obtain a new monitor file from your
system backup device and label the corrupted
file FILE.BAD to set aside the bad block.

this message.

?MON-F-System read failure halt

This error message is generated by only the
SJ monitor. An I/O error occurred while the
KMON or USR was being read into memory.
This indicates that the system volume is
dismounted or that the monitor file is situated on the system device in an area that developed one or more bad blocks. (Support for
display of this message must be selected dur-

Verify that the system volume is mounted in

the proper device and is ready. Bootstrap a
different monitor file on the system volume.
If the monitor file is affected, obtain a new
monitor file from the system backup device
and label the corrupted file FILE.BAD.

ing system generation.)

?MON-F-System write error

This error message is generated by only the
SJ monitor. The error occurred when the
monitor tried to write to SY: and was prevented, probably by a write-locked system
disk.

Verify that SY: is write-enabled when the error occurs; remember that SY: must be writeenabled for the USR to swap. Check the procedures for recovery from hard error conditions listed in Section 2.0.

?MON-F-Trap to 4 NNNNNN
?MON-F-Trap to 10 NNNNNN

A trap to location 10 occurs if the job
referenced invalid memory or device
registers or if an invalid instruction was
used.

Determine the bounds of the user program

from the link map or absolute locations 40,
46, 50, and 54. If the error occurred within
the bounds of the user program, correct the
programming logic. Verify that the program
has not corrupted vital monitor data, such as
the stack, the queue elements, or the monitor. Check USR swapping and program overlaying for possible error. Refer to Section 4.0

RT-11 System Message Manual

129

for more information. Check for reference to
a device that does not exist on the current
system — for example, PRINT FILE.FOR on
a system that does not have a line printer.

A trap to location 4 occurs if stack overflow occurred, a word instruction was executed with an odd address, or a hardware problem caused bus timeout.

Make sure that a transfer address is specified
in the .END directive of a MACRO-11 program or with the monitor LINK/TRANSFER
command or the linker /T option.

The value NNNNNN is the address of
the instruction following the instruction
or EMT that caused the error.
3.

A special trap to location 4 occurs if the
program counter (PC) is equal to 1, as in
the following error message, indicating
that the linker supplied a starting address of 1 for the program.

If none of these errors can be identified, submit an SPR to DIGITAL; include with the

SPR a program listing and a machine-readable source program, if possible.

?MON-F-Trap to 4 000001

This can occur if the transfer address was
omitted from the .END directive in a
MACRO-11 program or if no transfer address was specified with the monitor
LINK/TRANSFER command or the
linker /T option.
?MON-F-Unloaded driver NNNNNN

This error message is generated by only the
FB and the XM monitors. Under the FB monitor, the program attempted to use a device
handler that is not in memory and could not
be fetched. Under the XM monitor, there
may not be enough space for the device in the
interrupt-forwarding table. The value
NNNNNN
is the address of the instruction
following the instruction or EMT that caused
the error.

RT-11 requires device handlers to be loaded
manually for foreground and system jobs under the FB and XM monitors. Use the LOAD
command to load the handler(s) before running the program.
Load the handler into an area of memory
that is clear of the area mapped by kernel

active page registers 1 and 3. Alternatively,
perform another system generation and include additional device slots to increase the
size of the interrupt forwarding table.

MSBOOT-F-File not found
The specified file is not available
bootstrapping from the magtape.

for

Check for a typing error.

MSBOOT-F-Invalid file name
An invalid file name was specified.

130

RT-11 System Message Manual

Check for a typing error in the command
line. Verify that the file specification is in
the proper format.

'MSBOOT-F-1/O error

A hardware error occurred during a magtape

bootstrap operation.

?MSBOOT-F-Line too long

Refer to the procedures for recovery from
hard error conditions listed in Section 2.0.

More than 80 characters were used in the

Enter a valid MSBOOT command, limited to

?PAT-F-Correction file has invalid record
The format of the correction file is not compatible with the object file format PAT re-

Verify that the correction file has the proper
format, and retype the command line.

?PAT-F—Correction file missing
The command line has no correction file spec-

Enter a complete command to PAT.

MSBOOT command line.

quires. The standard language processors
should produce the required format.

ification. PAT requires both an input file and
a correction input file in every command.

?PAT-F—Correction file missing RLD record
The file is missing an RLD7 or p-sect definition command before the first TXT record.

a file name and file type.

Reassemble the correction file.

PAT cannot process the file.

?PAT-F-Correction file read error
PAT detected an error while reading the cor-

rection file. Input hardware can cause this
error.

?PAT-F-Device full DEV:FILNAM.TYP
The output volume does not have enough free
space for the corrected object file.

Try the command again. If the error persists,

refer to the procedures for recovery from hard
error conditions listed in Section 2.0.

If there is sufficient free space on the output

volume, use the form dev:filnam.typ[size] for
the output file specification. Otherwise, refer
to Section 3.0 for information on how to increase storage space.

?PAT-F-Incompatible reference to global AAAAAA
Modify the attributes of the global symbol.
The correction file contains a global symbol
with improper attributes. AAAAAA represents the name of the global symbol with improper attributes.

Choose DEFINITION or REFERENCE, and
choose RELOCATABLE or ABSOLUTE.
Reassemble the correction file, and type the
command line again.

?PAT-F-Incompatible reference to section AAAAAA
The correction file contains a section name
with improper attributes. AAAAAA represents the name of the section with improper
attributes.

Modify the section attributes or section type.
Choose RELOCATABLE or ABSOLUTE, and
specify .PSECT or .CSECT. Reassemble the
correction file and type the command line
again.

RT-11 System Message Manual

131

?PAT-F-Input file has invalid record

The format of the input file is not compatible
with the object file format PAT requires. The

standard language processors should produce
the required format.

Verify that the input file has the proper format, and retype the command line.

?PAT-F-Input file missing

The command line does not have an explicit
input file specification. PAT requires both an
input file and a correction file in every command.

Enter a complete command to PAT.

?PAT-F-Insufficient memory

Not enough contiguous memory is available
for the corrected output file.

Refer to Section 3.0 for information on how to
increase memory resources.

?PAT-F-Internal error

internal
curred.

software

error

condition

oc-

Try the operation again. If the error persists,
submit an SPR to DIGITAL; include with the

SPR a program listing and a machine-readable source program, if possible.

?PAT-F-Invalid command
The command line has a syntax error.

Check for typing errors and enter the command line again.

?PAT-F-Invalid GSD symbol in DEV:FILNAM.TYP
The global symbol directory (GSD) contains
an error. The file is probably not a valid ob-

ject module.

Verify that the input file name is correct;
check for a typing error in the command line.

Reassemble or recompile the source code to
obtain a good object module, and try the operation again.

?PAT-F-Invalid RLD symbol in DEV:FILNAM.TYP
An error occurred in the language processor
because a global symbol named in a relocatable record was not defined in the global symbol definition record.

Reassemble the indicated file. If the error

persists, submit an SPR to DIGITAL; include

with the SPR a program listing and a machine-readable source program, if possible.

?PAT-F-Only /C allowed

The input module or correction file specifications contain an invalid option that is neither
/C nor /C:n.

Enter a command line with appropriate op-

tions.

?PAT-F-Output error DEV:FILNAM.TYP
PAT encountered an error while writing the
output file. This error occurs when the output
device is write-locked or a hardware error
condition exists.

Check the procedures for recovery from hard

error conditions listed in Section 2.0.

132

RT-11 System Message Manual

?7PAT-F-Unable to locate module AAAAAA
The correction file has a module name that
does not exist in the input file. AAAAAA
represents the name of the nonexistent mod-

Update the input file to include the missing
module, or correct an improper module name
in the correction file. Retype the command

ule.

line.

?PAT-F-Wrong version of RT-11

An attempt was made to run an RT-11 Version 5 utility (PAT) on a previous version of

Do not run RT-11 Version 5 utilities under
earlier RT-11 versions.

RT-11.

?PAT-W-Additional input file ignored
The command line specified more than two
input files. PAT processes the first as the input module to be corrected and the second as
the correction file. PAT ignores all other

For each correction file, create a single input
object module to be corrected. Enter a correct
PAT command for the changes to be made.

files.

?PAT-W-Additional output file ignored
The command line has more than one output
file specification. PAT cannot create more
than one file for each command line. PAT

processes the first output file specified and

Enter a correct command. The general command line format outl,out2,out3 =input,correct, requires that PAT’s output file be in the
“outl” position.

ignores all others.

7PAT-W-Correction file checksum error

PAT found a checksum value that is different
from the value for the /C correction file option. Mistyping the /C option value or specifying an invalid version of the correction file

Check for typing errors. Check both the
checksum value and the correction file name
used. Correct the command line.

causes this error.

?PAT-W-Correction file checksum is NNNNNN
PAT responds to the /C option on the correction file with this message. NNNNNN is the
octal value of the sum of all binary data com-

This message is informational.

posing the file.

?PAT-W-File created; protected file already exists DEV:FILNAM.TYP
List the directory, unsorted. If the unproA protected file exists, along with a newly
created unprotected file of the same name.

tected file appears before the protected file in
the directory listing, either delete or rename
it. If the protected file appears first, either
rename it or change the protection code with
the monitor UNPROTECT command or the
PIP /Z option.

?PAT-W-Input file checksum error

PAT found a checksum value that is different
from the value for the /C input file option.
Mistyping the /C option value or specifying
an invalid version of the input file causes

Check for a typing error. Check both the
checksum value and the input file name

used. Correct the command line.

this warning.
Version 5.1, July 1984

RT-11 System Message Manual

133

?PAT-W-Input module checksum is

NNNNNN

PAT responds to the /C option on the input

module with this message. The octal value
NNNNNN is the sum of all binary data in
the file.

This message is informational.

?PIP-E-Operation not completed

The /WAIT operation was aborted because
the response to the mount message began
with an N or was a CTRL/C.

This message informs you that the operation
has been aborted. The response to the mount
message must begin with a Y for the /WAIT
operation to continue.

?PIP-E-Protected file already exists DEV:FILNAM.TYP
A protected file already existing on the output device has the same name as the file

specified in the command. The operation involving the protected output file is not processed. PIP processes any other operations
specified in the same command line that do

Use the monitor UNPROTECT command or
the PIP /Z option to change the protection
level of the existing file, or use a different
output file name.

not involve protected output files.

?PIP-F—-Channel in use
An internal PIP error occurred.

Reboot the system and try the operation
again. If the error occurs again, get a new
copy of PIP.SAV and retry the operation. If

the error persists, submit an SPR to DIGITAL; include with the SPR a program listing

and a machine-readable source program, if

possible.

?PIP-F-Channel not open DEV:FILNAM.TYP
An internal PIP error occurred.

Reboot the system and try the operation
again. If the error occurs again, get a new

copy of PIP.SAV and retry the operation. If

the error persists, submit an SPR to DIGITAL; include with the SPR a program listing

and a machine-readable source program, if

possible.

?PIP-F-Checksum error DEV:FILNAM.TYP
A checksum error occurred during a formatted binary transfer.

Check for a typing error in the command
line. Make sure that the correct file is being

transferred. Data may have been lost from
the input file. Try the operation again, using

the /G or the monitor IGNORE option, and
correct the file after input.

?PIP-F-Device full DEV:FILNAM.TYP

The output device does not have enough room
to contain the specified file, although preced-

ing files were copied.

134

RT-11 System Message Manual

Refer to Section 3.0 for information on how to
increase storage space.

?PIP-F-Device in use

Another job was using the device (normally
MT: or MM:).

?PIP-F-Directory full DEV:

The output volume’s directory does not have
enough space to create the output file.

Try the operation again after the other job is
either finished or aborted.
Use the SQUEEZE command to consolidate
free space on the output volume, or copy the
output volume to a volume with a larger
number of directory segments. Reenter the
command.

?PIP-F-Directory input error DEV:
A hardware error occurred while the direc-

Check the procedures for recovery from hard

?PIP-F-Fetch error DEV:
1. An internal PIP or a system error oc-

Reboot the system and try the operation

tory was being read.

curred. The copy of PIP.SAV, the monitor
file, or the specified device handler may
be corrupted on disk.

2. The in-core copy of PIP or the monitor
may be corrupted.

?PIP-F-File not found DEV:FILNAM.TYP
The input file specified was not found, or no

input files with the expected name or type

were found during a wildcard expansion.
This message also occurs if /BEFORE,
/SINCE, or /DATE was used and no files were
found that corresponded to the specified

error conditions listed in Section 2.0.

again. If the error occurs again, get a new

copy of PIP.SAV and the specified device
handler. Retry the operation. If the error persists, submit an SPR to DIGITAL; include
with the SPR a program listing and a machine-readable source program, if possible.

Check for a typing error in the command
line, verify that the file name exists as en-

tered in the command line, and try the operation again.

date(s).

?PIP-F-File sequence number not found
The input magtape volume has fewer files
than the sequence number in the monitor
/POSITION option.

?PIP-F-Input error DEV:FILNAM.TYP
PIP detected a hardware error while reading
the file.

Check for a mistyped file sequence number.
Check the magtape directory by using the
monitor DIRECTORY/POSITION command
or the DIR /B option. Reenter the command.

Check the procedures for recovery from hard
error conditions listed in Section 2.0. Try the
operation again, using the /G or the /IGNORE option.

?PIP-F-Insufficient memory

Memory overflow resulted from too many device and/or file specifications — usually in
wildcard operations — and no room for buff-

See Section 3.0 for information on how to increase memory space. Try copying the files
one at a time, without using wildcards.

ers.

RT-11 System Message Manual

135

?PIP-F-Invalid command

The command line is invalid. An option in-

compatible with the

been typed.

command may have

Check for a typing error. Verify that the for-

mat and syntax are correct, and retry the op-

eration.

?PIP-F-Invalid delete DEV:FILNAM.TYP
A magtape was used as the device in a DE-

LETE

command,

a TYPE/DELETE command, a PRINT/DELETE command, or with
the /D option in a PIP command line. No files
are deleted from the magtape.

Delete the files from the magtape by copying
files that should be saved to another volume

with a monitor COPY/QUERY command or a

PIP /G option, then reinitialize the original

magtape. Transfer the saved files back to the

magtape, if necessary.

?PIP-F-Invalid device DEV:

An invalid or a nonexistent device was specified.

Check for a typing error in the command
line. Verify that the device specified is valid.

?PIP-F-Invalid directory

The device did not contain a properly initialized directory structure — end-of-tape file
on cassette; empty file directory on other de-

vices.

Initialize the device with the INITIALIZE

command or the DUP /Z option before using

it the first time.

?PIP-F-Invalid option: /x
An invalid option was used in a command
line.

Check for a typing error in the command
line. Use only those options listed as valid for
PIP in the RT-11 System Utilities Manual.
(Also see the
RT—11 System User’s Guide for

the list of valid options for the COPY, DELETE, RENAME, PROTECT, and UNPROTECT commands.)

?PIP-F-Invalid output file

The specified file name is invalid for the command.

Type the command again.

?PIP-F-Invalid protect or unprotect DEV:FILNAM.TYP
An error was detected within the PIP program.

Submit an SPR to DIGITAL; include with the
SPR a program listing and a machine-readable source program, if possible.

?PIP-F-Invalid rename DEV:FILNAM.TYP
An invalid rename operation was attempted.

Check for a typing error in the command
line. Verify that the same device name ap-

pears in both the input and the output specifications.

?PIP-F-Invalid set date DEV:FILNAM.TYP
An error was detected within the PIP program.

136

RT-11 System Message Manual

Submit an SPR to DIGITAL; include with the
SPR a program listing and a machine-readable source program, if possible.

?PIP-F-Invalid use of wildcards DEV:FILNAM.TYP

The output file name or the file type does

not match the input file specifications in

Check for errors and retype the command
line.

the copy operation.

The output file specification contained
embedded wildcards (* or %) as In
A*B.MAC and A%B.MAC.

?PIP-F-Invalid value specified with option: /x

During the copying of a magtape, the value
of the file sequence number in a COPY/POSITION command or a PIP /M option is not in
the range —2 to +999. No files were copied

Check for a typing error. Retype the command, using the appropriate file sequence
number.

from the magtape.

?PIP-F-Library file not copied DEV:FILNAM.TYP

An OBJ library is an input file in a monitor
COPY/BINARY command or a PIP /B option.
The file name is shown in this message.
Copying stops.

Do not use the /BINARY or the /B option
when copying OBJ libraries. Use the
/QUERY or the PIP /Q option to copy files
selectively, and type NO for each OBJ library.

?PIP-F-Output error DEV:FILNAM.TYP

An unrecoverable error, perhaps caused
by a hardware or a checksum error, occurred while PIP was writing a file.

The device does not have enough room to

See Section 3.0 for information on how to increase storage space. Check the procedures
for recovery from hard error conditions listed
in Section 2.0.

create a file.

In a multiple file operation, the command
was successfully executed on every file
preceding the one interrupted by the error.

?PIP-F-Output file full DEV:FILNAM.TYP

Physical end-of-tape was detected on an
output magtape volume.

The output file is not large enough for
the input file.

Use the /ALLOCATE command or the square
bracket construction to specify large output

files, if the output volume has sufficient free
space. Check Section 3.0 for information on
how to increase storage space.

For devices other than magtapes, fragmented storage space can cause this mes-

sage. Copies from magtape or cassette

and copies with the /CONCATENATE
command or the PIP /U option also cause
the error.

?PIP-F-Protected file DEV:FILNAM.TYP

An attempt was made to delete a protected
file.

Remove the file’s protection, using the monitor UNPROTECT command or the PIP /Z option, and type the command again.

RT-11 System Message Manual

137

?PIP-F-Size function failed

PIP attempted to read the size of a device
that is on a unit not supported by the monitor.

Mount the device on a unit number that the

monitor supports. Otherwise, perform another system generation to add more units

for the specified device.

?PIP-F-System error
1.

An attempt was made to use a device not

on the system.

Make sure that the device specified is
loaded. Check the directory of the relevant device to ensure that the necessary
system programs are intact. Reboot the

system, if necessary.
2.

An internal error has occurred.

Try the operation again. If the error persists, submit an SPR to DIGITAL; include with the SPR a program listing and
a machine-readable source program, if

possible.

?PIP-F-Too many output files
More than one output file was specified in
the command line.

Limit the number of output files on the command line to one.

?PIP-F-Verification error DEV:FILNAM.TYP

The monitor /VERIFY command or the PIP
/V option was used after a copy operation and
found differences between the new and the
original copies of the file.

Check the procedures for recovery from hard

error conditions listed in Section 2.0.

?PIP-F-Wrong version of RT-11
An attempt was made to run RT-11 Version

5 PIP on an outdated version of RT-11.

Do not attempt to run RT-11 Version 5 PIP
under any earlier RT-11 versions.

?PIP-I-Device full DEV:FILNAM.TYP
The COPY/MULTIVOLUME command was
used with a mounted output device that is
full and does not have room for any of the
input files. PIP continues and asks for another output device to be mounted.

Remove the full output volume and mount
another output volume.

?PIP-1-File not found DEV:FILNAM.TYP

The specified file was not found.

This message is informational because the
/INFORMATION option was specified in the

command line.

?PIP-I-Protected file not found DEV:FILNAM.TYP
The file(s) specified was found, but it is already unprotected.

138

RT-11 System Message Manual

This message is informational.

?PIP-I-Unprotected file not found DEV:FILNAM.TYP

The file(s) specified was found, but it is al-

This message is informational.

ready protected.

?PIP-W-File larger than output device DEV:FILNAM.TYP
A
file
specified
in
the
COPY
/MULTIVOLUME command is larger than
the output device. The file is not copied and

Use a larger device to back up the specified

file that is too large.

the operation continues.

?PIP-W-Input error DEV:FILNAM.TYP

PIP detected a hardware error while reading
the file. Execution continues because a /G or
a monitor /IGNORE option was used in the

Examine the file for errors after the command finishes.

command line.

?PIP-W-No .SYS action
The /Y or the monitor /SYSTEM option was

not included with a command specified on a

Check for a typing error in the command
line. The command is executed for all but

SYS file. A wildcard transfer is most likely

SYS

to cause this message.

/ISYSTEM option if .SYS type files should

files.

Use

the

monitor

also be included in the operation.

?PIP-W-Output file found, no operation performed DEV:FILNAM.TYP
The command line included the monitor
/NOREPLACE or the PIP /N option, and a
file on the output volume already has the
name shown. That file is not changed, and
the input file with the same name is not copied.

If output files having the same names as in-

put files do not require protection, reissue the
command without the /NOREPLACE or the
/N option.

Otherwise,

change one of the

names in each conflicting pair — the file al-

ready on the output volume, the file on the
input volume, or the explicit output file name
in the command line.

?PIP-W-Reboot

System (.SYS) files have been created,
moved, renamed, or deleted from the system

system have been physically moved on the

device.

system device, reboot the system immedi-

If any of the .SYS files in use by the current

ately. (The reboot operation must not be performed until PIP returns with the prompting

asterisk for the next command or until a
monitor command returns to the monitor
prompt.) Otherwise, the message can be ignored.

?QUEMAN-E-File not found DEV:FILNAM.TYP
The specified file was not found.

Check for a typing error in the command
line. Make sure that the specified file resides
on the specified device. Enter the command

again.

RT-11 System Message Manual

139

?7QUEMAN-E-Insufficient memory

Not enough memory is available to build the

See Section 3.0 for information on how to in-

job request.

crease memory resources.

?QUEMAN-E-Invalid command
The command line given to QUEMAN is not
in the correct format.

Check for a typing error in the command line
and make sure that the command is in the
correct format. Enter the command again.

?QUEMAN-E-Invalid device DEV:
The specified device was not found in the sys-

Reenter the command, using a valid device.

tem device tables.

?QUEMAN-E-Invalid option: /x
An invalid option was specified in the com-

Check for a typing error in the command line

mand line.

and review the list of valid options. Reenter

the command line.

?QUEMAN-E—-Queue full

Not enough space is available in the workfile
for the number of input files specified.

Reduce the number of files requested or wait
until some jobs have run to completion before
making additional requests.

?QUEMAN-F-Handler not loaded DEV:
The handler for the device is not loaded.

Load the device handler and reenter the command.

?QUEMAN-F-Input error DEV:FILNAM.TYP
An error occurred while a file or the directory
was being read. This error may be caused by
a hard error or an accidental deletion of the
QUEUE workfile.

Try reading the file or directory again. Use
/L to list the current contents of the QUEUE.
If the error persists, copy each file to another

device. Reformat
FORMAT program.

the

disk,

using

the

If the error persists, the disk is bad. Use a
different disk for the operation.

?QUEMAN-F-Invalid date
Check for a typing error in the command

An invalid value was specified for the day,
month, or year in the /DATE, /BEFORE, or

line. Reenter the command, using valid val-

/SINCE option.

ues for the option.

?QUEMAN-F-QUEUE is not running
The QUEUE program is not running as either a foreground job or a system job.

Use FRUN to install QUEUE in the fore-

ground, or use SRUN to install QUEUE as a
system job.

?QUEMAN-F-Wrong version of RT-11
An attempt was made to run an RT-11 Ver-

Do not run RT-11 Version 5 utilities under

sion 5 utility (QUEMAN) on a previous ver-

earlier RT-11 versions.

sion of RT-11.
Version 5.1, July 1984

140

RT-11 System Message Manual

?QUEMAN-I-File not found DEV:FILNAM.TYP
The specified file was not found.

This message is informational because the
/INFORMATION option was specified in the
command line.

?QUEUE-E-Cannot delete protected file DEV:FILNAM.TYP

The referenced file is protected. QUEUE at-

Use the monitor UNPROTECT command or

tempted to delete an input file in response to
the /D option or the monitor PRINT/DELETE
command, to open an output file on a filestructured device, or to delete a workfile that
contained a protected file of the same name.

the PIP /Z option to remove the protection
status of the file, and reenter the request.

?QUEUE-E-Cannot open message channel
QUEUE was unable to open a message channel on which to receive job requests. This is
an internal error.

Submit an SPR to DIGITAL; include with the

SPR a program listing and a machine-readable source program, if possible.

?QUEUE-E-File not found DEV:FILNAM.TYP

The file sent to the workfile was deleted.

Make sure that the specified file resides on
the specified device. Reenter the job request
to print the file.

?QUEUE-E-Handler not loaded DEV:
The specified device handler is not loaded.

Load the handler and reenter the job request
to print the file.

?QUEUE-E-Protected file exists DEV:FILNAM.TYP
An attempt was made to create a protected
file having the same name as an existing protected file.

Use the monitor UNPROTECT command or
the PIP /Z option to change the protection
level of the existing file, or use a different
name to create the new file.

?QUEUE-F-Cannot open input device DEV:FILNAM.TYP
The specified input device could not be
opened.

Make sure that the input device is on line.
Reenter the job request.

?QUEUE-F-Cannot open output device DEV:

The specified output device could not be

Make sure that the output device is on line.

opened.

Reenter the job request.

?QUEUE-F-Input error DEV:FILNAM.TYP
An input error occurred on the specified file.

Refer to procedures for recovery from hard
error conditions listed in Section 2.0.

?QUEUE-F-No room for QUEUE workfile on DK:
The system device does not have enough
room for the QUEUE workfile.

Refer to Section 3.0 for instructions on how to
increase storage space on volumes.

RT-11 System Message Manual

141

?QUEUE-F-Output error DEV:FILNAM.TYP
A hard error occurred during an output
transfer while the specified job was being
processed.

Check the procedures for recovery from hard

error conditions listed in Section 2.0.

?QUEUE-F-Output error SY:QUFILE.TMP
A hard error occurred while the QUEUE
workfile was being updated.

Check the procedures for recovery from hard
error conditions listed in Section 2.0.

?QUEUE-F-Wrong version of RT-11
An attempt was made to run an RT-11 Version 5 utility (QUEUE) on a previous version

Do not run RT-11 Version 5 utilities under

earlier RT-11 versions.

of RT-11.

?QUEUE~W-Error sending message to JOBNAME
'QUEUE was unable to send an acknowledgment to the requesting job because the request message to QUEUE exited before re-

This message is informational.

ceiving an acknowledgment message.

?RESORC-F-Error reading directory

An input error occurred while RESORC was
reading a directory segment from the system

Make sure that the system device is mounted

device.

bad

and up to speed. Scan the system device for

blocks,

using

the

DIRECTORY

/BADBLOCKS command or the DUP /K option.

?RESORC-F-Input error FILNAM.TYP
An input error occurred while RESORC was

Scan the system device for bad blocks. It may

reading the specified file.

be necessary to obtain a fresh copy of the
monitor from a backup copy of the system.

?RESORC-F-Insufficient memory
Not enough free memory is available for

Unload the foreground or the system job, if

RESORC to allocate space to its input buffer.

possible, and any unnecessary handlers.

?RESORC-F-Invalid option
The option specified in the command line is
invalid.

Check for a typing error in the command
line. Use only valid options. See the RT-11
System Utilities Manual or the RT—11 System User’s Guide for a list of valid options.

?RESORC-F-System error
A .DSTATUS

or a .LOOKUP request to the

Make sure that the system device is mounted

system device failed. Either the system de-

and up to speed. It may be necessary to reboot the system.

vice 1s not mounted or the image of the monitor currently in memory is corrupted.

?RESORC-F-Wrong version of RT-11
An attempt was made to run RT-11 Version

5 RESORC on an outdated version of RT-11.
Version 5.1, July 1984

142

RT-11 System Message Manual

Do not attempt to run RT-11 Version 5
RESORC under any earlier RT-11 versions.

?RESORC-I-No queues active

Neither QUEUE nor SPOOL were running
when you issued a SHOW QUEUE or
RESORC /Q command.

This message is informational.

?SETUP-F-Ambiguous command <COMMAND>
The command abbreviation entered is not
unique.

Retype the command, using enough characters to distinguish it from other commands.

?SETUP-F-Ambiguous value <VALUE>

The value you specified contains too few
numbers to be unique.

Retype the command, using enough numbers
to distinguish the value from others.

?SETUP-F-ANSWERBACK message too long
The message you specified ffor the answerback feature has too many characters.

Retype the command, specifying an answerback message with 20(decimal) or fewer characters.

?SETUP-F-Channel in use

An internal SETUP error occurred.

Reboot the system and try the operation

again. If the error occurs again, get a new

copy of SETUP.SAV and retry the operation.
If the error persists, submit an SPR to
DIGITAL.

?SETUP-F-Channel not open DEV:FILNAM.TYP
An internal SETUP error occurred.

Reboot the system and try the operation
again. If the error occurs again, get a new
copy of SETUP.SAV and retry the operation.
If the error persists, submit an SPR to
DIGITAL.

?SETUP-F-Fetch error DEV:

An internal SETUP or a system error occurred. The copy of SETUP.SAV, the monitor
file, or the specified device handler may be
corrupted on disk. The in-core copy of SETUP
or the monitor may be corrupted.

Reboot the system and try the operation

again. If the error occurs again, get a new
copy of SETUP.SAV and retry the operation.

If the error persists, submit an SPR to
DIGITAL.

?SETUP-F-File not found DEV:FILNAM.TYP
The device handler file for the device you
specified was not found on the system vol-

Copy the handler file for the device to the
system volume and try the operation again.

ume.

?SETUP-F-Input error DEV:FILNAM.TYP

SETUP detected a hardware error while
reading the handler file.

Check the procedures for recovery from hard
error conditions listed in Section 2.0. Try the
operation again.

Version 5.1, July 1984

RT-11 System Message Manual

142.1

?SETUP-F-Insufficient memory

Not enough memory is available to complete
the requested operation.

Refer to Section 3.0 for information on how to
increase memory space.

?SETUP-F-Invalid command <COMMAND>
The command line is invalid.

Check for a typing error. Make sure the format and syntax of the command line are correct, and retype the command line.

?SETUP-F-Invalid command for destination
The command you typed is invalid for the
hardware you specified.

Retype the command, making sure the command option you choose is valid for the hardware (terminal, printer, or clock) you specify

in the command line.

?SETUP-F-Invalid device DEV:

The specified device is not installed in the
monitor device tables.

Check for a typing error in the command
line. Use the INSTALL command to add the
device to the monitor device tables.

?SETUP-F-Invalid processor for command <COMMAND>

The command you typed is invalid for your
processor. Some SETUP commands are valid
for Professional 300 series hardware only;

Make sure the command you type is valid for
your processor.

some commands are valid for PDP-11 hard-

ware only.

?SETUP-F-Invalid terminal for command
An attempt was made to execute the SETUP

COLOR command on a monochrome monitor.

Issue the SETUP COLOR command only
when using a color monitor.

?SETUP-F-Invalid value <VALUE>
A value specified in the command line is in-

valid.

Check for a typing error in the command
line. Make sure values you specify as arguments to SETUP commands are positive integers.

?SETUP-F-Unexpected EOF DEV:FILNAM.TYP
An internal SETUP error occurred.

Reboot the system and try the operation
again. If the error occurs again, get a new
copy of SETUP.SAV and retry the operation.
If the error persists, submit an SPR to
DIGITAL.

?SETUP-F-Wrong version of PI

You tried to run ‘SETUP, but the version of
PI(X).SYS on your system does not match the
version of SETUP.

Version 5.1, July 1984

142.2

RT-11 System Message Manual

Use the version of PI(X).SYS distributed
with the same version of RT—-11 as the version of SETUP you are using.

?SETUP-U-System error

An internal SETUP error occurred.

Reboot the system and try the operation
again. If the error occurs again, get a new
copy of SETUP.SAV and retry the operation.

If the error persists,

submit an

SPR to

DIGITAL.

?SIPP-E-Below segment boundary

An attempt was made to open a location below the low end of the segment. SIPP returns

Do not try to open a location below the low
end of the segment.

to the OFFSET? prompt.

Version 5.1, July 1984

RT-11 System Message Manual

142.3

?2SIPP-E-Checksum error

An invalid checksum was typed. SIPP returns to the SEGMENT? or the BASE?
prompt so that the error can be found and
corrected.

If the checksum was mistyped, type CTRL/Y,

followed by a carriage return, to return to the
checksum prompt, and type the checksum
again. If the modifications were typed incorrectly, type ;V to display the modifications in
words, not bytes, made in the current session.
Correct the modifications to reflect the distributed patch. Type CTRL/Y, followed by a
carriage return, and type the correct checksum. Note that SIPP does not install patches
and does not create a log file if the checksum
is incorrect.

?SIPP-E-End of file

An attempt was made to begin patching beyond the end of the file.

?SIPP-E-Exceeds program limit

The location being examined or modified is
beyond the end of the program.

2SIPP-E-Exceeds segment boundary
An attempt was made to examine or to

change a location beyond the segment’s block

SIPP returns with the OFFSET? prompt. It
does not discard any previous changes.

SIPP returns with the OFFSET? prompt and
does not discard any previous changes. The
current open location is not modified.

SIPP returns to the OFFSET? prompt without losing any previous changes.

boundary.

?SIPP-E-Invalid address

An invalid value was specified in the seg-

Control returns to the OFFSET? prompt.

ment, the base, or the offset.

?2SIPP-E-Invalid boundary size

The search range exceeded the size of the file.

?SIPP-E-Invalid command
The command line typed is not valid.

2SIPP-E-Invalid extension of root segment

An attempt was made to modify the root beyond the root segment. SIPP returns to the
OFFSET? prompt.

Retype the search command and respond to
the prompt with an accurate search range.

Check for a typing error in the command
|
string and try again.

If the overlaid file contains /V overlays, the
size of the root can be extended up to the

block boundary. Do not try to extend the root
segment if the overlaid file contains one or
more /O overlays.

?SIPP-E-Invalid input

The input is invalid. SIPP prompts again.

Check for a typing error. Review the valid
SIPP commands (see the RT—11 System Ultilities Manual). Try the operation again.

RT-11 System Message Manual

143

?SIPP-E-Invalid option: /x

An option specified in the command string is

not valid.

Check for a typing error in the command
line. Use only valid options. Refer to the
RT-11 System Utilities Manual for valid op-

tions.

?SIPP-E-Invalid option combination
Both the /C and /D options were used.

Enter the command line again, specifying
only one of these options.

?SIPP-E-Invalid search command

The command or input to the search prompts
is not valid.

Check for a typing error and try again.

?SIPP-E-Invalid segment number

The segment number specified does not exist.
SIPP repeats the SEGMENT? prompt or the
START? prompt if in search mode.

Check for a typing error. Check the program’s link map to determine the true over-

lay structure.

?SIPP-E—-Not V4 overlaid file
The file being patched is overlaid, but was
not produced by a Version 4 or later linker.

SIPP repeats its prompt and waits for an-

other command line.

Relink the program, using a Version 4 or
later linker, or modify the file as explained in
the RT-11 System Utilities Manual.

?SIPP-E-0Odd base address
An odd base address was specified. SIPP
repeats the BASE? prompt.

Type an even number. An odd base address

may be specified in response to the OFFSET?

prompt.

?SIPP-E—-Patch buffer full

All memory available for storing modifications is in use.

Type CTRL/Y followed by a carriage return

to insert the modifications typed so far. If

this message occurs while you are extending
a file, a segment, or a program, reopen the
file and place a 0 one point beyond the location at which the message was produced.
?SIPP-E-Region size exceeds 96K

The modified program was extended beyond
the maximum overlay address space.

Stop the current operation by typing CTRL/C
and reapply the modifications. Alternatively,
continue the current operation by correcting
the size of this segment to the size indicated
in the overlay table and the two size words

for this segment in the window definition
block of the handler.
?SIPP-F-Device full DEV:FILNAM.TYP

The output device does not have enough room
for the SIPP modification. The log file is not

created.

144

RT-11 System Message Manual

Use the SQUEEZE command to consolidate
the disk, or use another device for this opera-

tion.

?SIPP-F-File not found DEV:FILNAM.TYP
The input file is not on the specified device.

Check for a typing error in the command
line, verify that the file name exists as it was

typed, and try again.

?SIPP-F-Input error DEV:FILNAM.TYP
A hardware error occurred when SIPP read
the file to be modified.

Check the procedures for recovery from hard

error conditions listed in Section 2.0.

?SIPP-F-Insufficient memory

Not enough memory is available to run SIPP.

Increase the available memory by unloading
device handlers, the foreground job, or one or
more system jobs.

?SIPP-F-Invalid device DEV:
‘The specified device is not a random-access
device.

Use a valid device.

?SIPP-F-Output error DEV:FILNAM.TYP
A hardware error occurred when SIPP tried
to patch the file.

Check the procedures for recovery from hard
error conditions listed in Section 2.0.

?SIPP-F-Patch aborted, no modifications made

A hardware error occurred. The patch is not

Check the procedures for recovery from hard

installed.

error conditions listed in Section 2.0.

?SIPP-F-Protected file already exists DEV:FILNAM.TYP
An attempt was made to create a log file having the same name as an existing protected
file.

Use the monitor UNPROTECT command or
the PIP /Z option to change the protection

status of the file.

?SIPP-F-Size function failed

A hardware error occurred while SIPP was
determining the size of the volume.

Check the procedures for recovery from hard
error conditions listed in Section 2.0.

?SIPP-F-Wrong version of RT-11

An attempt was made to run an RT-11 Version 5 utility (SIPP) on a previous version of
RT-11.

Do not run RT-11 Version 5 utilities under
earlier RT-11 versions.

?SIPP-I-Approaching segment boundary
SIPP is within five words of exceeding the
high limit, or block boundary, of an overlay

This message is informational; the operation
continues.

segment.

?SIPP-I-End of file

SIPP opened the next location beyond the
end of the file during a patch operation.

SIPP returns to the OFFSET? prompt.

Version 5.1, July 1984

RT-11 System Message Manual

145

?SIPP-I-Extending high limit

An attempt was made to request a change to

When SIPP installs the patch, it calculates

a location beyond the program’s high limit.

the new high limit and updates location 50
and the bit map of the program. This informational message is printed only once during
a session.

?SIPP-I-Extending overlay segment
An attempt was made to request a change to

a location beyond the segment’s linked limit,

When SIPP installs the patch, it automatically updates the segment size in the overlay

but before its block boundary.

table. This message will occur the first time
an overlay segment is extended during a session.

(Each session begins
SEGMENT? or BASE? prompt.)

with

the

?SIPP-I-No modifications made
The patch operation was terminated before

This message is informational; the operation

modifications were made to the file; the file is

continues.

not patched.

?SIPP-W-Patch buffer approaching limit

SIPP is about to run out of memory for storage of modifications.

SIPP can accept five more modifications. To
extend the file, type CTRL/Y and insert the
remaining patches.

?SLP-F-Audit trail exceeds line limit
The /S or /L option values were used in invalid combinations. The current editing ses-

Check the RT-11 System Ultilities Manual for
valid combinations of option values. Retype

sion is terminated and no output files are

the command.

produced. Control returns to the CSI level.
?SLP-F-Audit trail overwrites line
Text on a source line went beyond the point

where the audit trail was placed. The current

Use the /P option to reposition the audit trail.

editing session is terminated and no output
files are produced. Control returns to the CSI

level.

?SLP-F-Backup file suppression unsuccessful

The /N option was specified to suppress the
.BAK file. The operation was unsuccessful.

If the original source file is protected, use the
monitor UNPROTECT command or the PIP
/Z option to remove the protection.

?SLP-F-Characters before the *-” in DEV:FILNAM.TYP
SLP found characters before the hyphen symbol (-) in the update text file. Any data that
precedes this symbol in the update text file is
ignored.

146

RT-11 System Message Manual

Make sure that the hyphen symbol (-) is at
the beginning of the update text file.

?SLP-F-Command syntax error

A line read from the command file is not a
valid command. The current editing session
is terminated and no output files are pro-

duced. Control returns to the CSI level.

Check the command line for a typing error.
Make sure that the command is formatted
correctly (refer to the RT—-11 System Utilities
Manual). Try the operation again.

?SLP-F-Correction file checksum error

The computed checksum of the command file
does not match the value specified in the /C:n
option of the SLP command line.

Check for a typing error in the command
line; verify that the correct checksum value
and file name were specified. Retype the command line.

?SLP-F-Device full DEV:FILNAM.TYP
During a write operation, an end-of-file was
reached. The current editing session is terminated and no output files are produced. Control returns to the CSI level.

Refer to Section 3.0 for information on how to
increase storage space, or use another output
volume.

?SLP-F-Extra file(s) specified

More than two output or input files were
specified in the command line. The current
editing session is terminated and no output
files are produced. Control returns to the CSI

Retype the command line, using no more
than two output files and two input files.

level.

?SLP-F-File created; protected file already exists DEV:FILNAM.TYP
A protected file exists, along with a newly

created unprotected file of the same name.

List an unsorted directory. If the unprotected
file appears before the protected file in the
directory listing, either delete or rename it. If
the protected file appears first, either rename
it or change the protection code with the
monitor UNPROTECT command or the PIP
/Z option.

?SLP-F-File not found DEV:FILNAM.TYP
The specified file is not located on the specified device.

Check the command line for typing errors.
Verify the location of the specified file and
issue the command again.

?SLP-F-File protected

An attempt was made to modify a protected
file.

Change the protection status of the file with
the monitor RENAME/NOPROTECT command or the PIP /Z option.

?SLP-F-Hard error on device

A hardware error occurred during an /O

transfer. The current editing session is termi-

Refer to the procedures for recovery from
hard error conditions listed in Section 2.0.

nated and no output files are produced. Control returns to the CSI level.

RT-11 System Message Manual

147

~ ?SLP-F-Insufficient memory
Not enough memory is available for the combined requirements of the line buffer and

Refer to Section 3.0 for information on how to
increase memory resources.

block buffers for the files. The current editing
session is terminated and no output files are

produced. Control returns to the CSI level.

?SLP-F-/C Invalid option
The /C option was specified with an output

file in the SLP command line.

Make sure that the /C option is specified in
the SLP command line with a SLP input file

and/or command file.

?SLP-F-Invalid option: /x
An invalid option was specified. The current

editing session is.terminated and no output
files are produced. Control returns to the CSI
level.

Refer to the

RT-11 System Utilities Manual
for a list of valid options.

?SLP-F-Invalid rename
The SLP program tried to rename the output
file that was sent to magtape.

Send the SLP output file to a volume other
than magtape, which is not a valid output

‘device for SLP operations.
?SLP-F-Invalid value specified with option: /x
An option value specified is not within the
range of valid values. The current editing
session is terminated and no output files are

Refer to the RT—11 System Utilities Manual
for a list of valid options and the range of
valid values for each option.

produced. Control returns to the CSI level.

?SLP-F-Line number error
A command line specified a numeric line locator that is not in the correct format. In an

update line, locator2 pointed to a source file
line that appears before the line pointed to by

locatorl. This message can also indicate that
the update lines do not edit the source file in

Check the command line for a typing error.
Make sure that the command is formatted
correctly,

that the update lines reference
source file lines in the correct order, and that

locatorl and locator2 correctly define a range
of lines in the source file.

order from the beginning of the file to the
end.

?SLP-F-Line too long
A line was read that is longer than the line
buffer. The current editing session is termi-

Use the /L option to make the buffer larger.

nated and no output files are produced. Control returns to the CSI level.

?SLP-F-Protected file already exists DEV:FILNAM.TYP
An attempt was made to create a protected

file having the same name as an existing file.

Use the monitor UNPROTECT command or
the PIP /Z option to change the protection
level of the existing file, or use a different
name to create the new file.

148

RT-11 System Message Manual

?SLP-F-Search failure in source file
A specified source line was not found in the
source file. The current editing session is terminated and no output files are produced.
Control returns to the CSI level.

Verify that the specified source line is in the
source file. Add the missing source line, if
necessary, or specify another source line.

?SLP-F-Source file checksum error

The computed checksum of the source file
being updated does not match the value specified in the /C:n option of the SLP command
line.

Check for a typing error in the command
line; verify that the correct checksum value

and file name were specified. Retype the command line.

?SLP-F-Source file not specified

The command did not specify a source file.
The current editing session is terminated and
~ no output files are produced. Control returns

Try the operation again, specifying a source

file in the command line.

to the CSI level.
?SLP-F-System error

This is an internal error. The current editing
session is terminated and no output files are
produced. Control returns to the CSI level.

Submit an SPR to DIGITAL; include with the
SPR a program listing and a machine-readable source program, if possible.

?SLP-F-Unexpected end of correction file
The correction file does not contain the endof-file line (/). The current editing session is
terminated and no output files are produced.
Control returns to the CSI level.

Change the correction file to include the endof-file line (/).

?SLP-F-Value required: /x

An option specified requires a value, but
none was given. The current editing session

Specify a value for the option and type the
command again.

is terminated and no output files are pro-

duced. Control returns to the CSI level.

?SLP-F-Wrong version of RT-11

An attempt was made to run an RT-11 Version 5 utility (SLP) on a previous version of

Do not run RT-11 Version 5 utilities under
earlier RT-11 versions.

RT-11.

?SLP-I-DEV:FILNAM.TYP checksum is n

The /C option was specified in the SLP command line to determine the checksum of an

This message is informational.

input file.

?SLP-W-Audit trail overwrites existing audit trail
An attempt was made to write an audit trail
at the end of a line that already ends with an
audit trail. The new audit trail overwrites

If the new audit trail is not acceptable, write
either the original or a new audit trail at the
end of the line.

the old audit trail.

Version 5.1, July 1984

RT-11 System Message Manual

149

?SLP-W-No update text found

The update text file does not have the hy-

Check for a typing error. Make sure that the

phen symbol (-). No changes were made, and

hyphen symbol (-) precedes the update text

control returns to the CSI prompt.

file.

?SPOOL~-F-Cannot attach output terminal

SPOOL could not use the logical unit number

Make sure the terminal intended as the out-

specified for output. This message appears

put device is not in use by a job other than

only if you are running under a multitermi-

SPOOL.

nal system.
?SPOOL-F-Cannot get memory (use /BUFF:256.)
While running under the FB monitor, you at-

Run SPOOL again and include the option

tempted to run SPOOL as a foreground job,
but neglected to use the /BUFFER option.

/BUFF:256. in the command line.

?SPOOL~-F-Cannot get required extended memory
Not enough extended memory is available for
SPOOL to allocate for its output buffers.

Make sure you use the /BUFF:256. option
when running SPOOL. Make sure your sys-

tem is configured so that 256 words of extended memory are available, possibly by

changing the base address of VM.

?SPOOL-F-Cannot map window to extended memory
An internal SPOOL error has occurred.

Try the operation again. If the error persists,
submit an SPR to DIGITAL; include with the
SPR a program listing and machine-readable
source program, if possible.

?SPOOL-F-Device for work file non-existent
The

device

specified

for

the

work

file

SPOOL.SYS does not exist.

Check for a typing error. Reassign the logical
device name SFD to a valid device.

?SPOOL-F-1/0 error on work file
An error occurred while SPOOL was using

Check the work file volume for bad blocks by

the work file.

using the DIR/BADBLOCKS command. Initialize the volume or use another volume if
necessary.

?SPOOL-F-SET USR NOSWAP
While running under the FB monitor, you at-

Issue the command SET USR NOSWAP and

tempted to run SPOOL but neglected to set

retype the command to run SPOOL. Then, is-

the USR to NOSWAP first.

sue the command SET USR SWAP.

?SPOOL-F-Spooled device DEV: non-existent or not loaded
The SPOOL output device does not exist, or

Load the handler for the output device, and

the handler for that device is not loaded.

restart SPOOL. Make sure the logical device

name SOO: is assigned to a valid device.

Version 5.1, July 1984

150

RT-11 System Message Manual

?SPOOL-F-Work file device handler not loaded
The handler for the device specified for the
work file SPOOL.SYS is not loaded.

Load the handler and restart SPOOL.

?SPOOL-I-Invalid SP unit number specified
An attempt was made to issue a SET command for a SPOOL device other than SPO:.

Retype the SET command, using SPO:.

?SPOOL-W-Insufficient room for work file of nnn blocks

There is not enough room on the specified device for a work file of the size specified.

SPOOL allocates the largest free area on the
specified device for SPOOL.SYS. If you require a larger work file, create SPOOL.SYS
on a volume with more free space by assigning the logical name SF: to another volume.

?SRCCOM-F-Device not active DEV:
The command string requested input or output for a device that is not on line, writeenabled, or in the system’s device tables.
Wildcards may have been used.

Make sure that the device is on line and not
write-locked. Use the INSTALL command to
enter the device into the system’s device tables.

?SRCCOM-F-Error reading directory DEV:
A hardware error occurred while the directory of the indicated device was being read.

Check the procedures for recovery from hard
error conditions listed in Section 2.0.

Wildecards may have been used.

?SRCCOM-F-File created; protected file already exists
A protected file exists, along with a newly

created unprotected file of the same name.

?SRCCOM-F-File not found DEV:FILNAM.TYP
The specified input file was not found on the
specified device. Wildcards may have been
used.

Make sure that the command line contains
no errors and that the specified file exists on
the specified device. If the correct device is
not mounted, mount it and reenter the command.

?SRCCOM-F-Input error DEV:FILNAM.TYP
An attempt was made to access an input device for a comparison and a hardware error
occurred. Wildcards may have been used.

Check the procedures for recovery from hard
error conditions listed in Section 2.0.

?SRCCOM-F-Insufficient memory

Not enough memory is available to hold a
particular difference section. Wildcards may

Refer to Section 3.0 for information on how to
increase memory space.

have been used.
Version 5.1, July 1984

RT-11 System Message Manual

151

?SRCCOM-F-Invalid command
An invalid command to SRCCOM was typed.

Check the valid commands for SRCCOM. Enter a valid command.

?SRCCOM-F-Invalid directory DEV:
An attempt was made to read a directory
that is not in RT-11 format. Wildcards may
have been used.

Copy the files onto an RT-11 directory de-

vice.

?SRCCOM-F-Invalid option: /x
Either an invalid option was found or an option other than /MATCH was given a value.

Check for a typing error in the command
line. Use only those options listed in the
RT-11
System
Utilities
Manual
for
SRCCOM. Also see the valid options for the
DIFFERENCES command in the RT-11 System User’s Guide, and specify values only for
those options requiring values.

?SRCCOM-F-Invalid value specified with option: /x
An invalid value was specified in the command to SRCCOM.

Check the RT-11 System Utilities Manual or
the RT-11 System User’s Guide for a list of

options and the range of validd values for each
option. Enter the command again.

?SRCCOM-F-Protected file already exists DEV:FILNAM.TYP
An attempt was made to create a protected
file with a name already associated with an
existing file.

Use the monitor UNPROTECT command or
the PIP /Z option to change the protection
level of the existing file, or use a different
name to create the new file.

?SRCCOM-F-Read error
A hardware error was reported during an input operation.

Check the procedures for recovery from hard

error conditions listed in Section 2.0.

?SRCCOM-F-Too many differences
More than 310(octal) lines were found to be
different when two files were compared.

Check for a typing error in the command
line. A limit of 310(octal) lines of difference is
set for SRCCOM. (Note that the value speci-

fied to the /L [/MATCH] option must be
<=310.)

?SRCCOM-F—-Write error
Either the output device was full or a hardware error occurred in writing the output

file.

Refer to Section 3.0 for information on how to

increase storage space. Check the procedures
for recovery from hard error conditions listed
in Section 2.0.

?SRCCOM-F-Wrong version of RT-11
An attempt was made to run an RT-11 Version 5 utility (SRCCOM) on a previous -ver-

sion of RT-11.

Version 5.1, July 1984

152

RT-11 System Message Manual

Do not run RT-11 Version 5 utilities under
earlier RT-11 versions.

?SRCCOM-I-No differences found

The specified files were compared and no dif-

This message is informational.

ferences were found.

?SRCCOM-W-Audit trail truncated to eleven characters

The audit trail exceeded 11 characters and
was truncated.

If the truncated audit trail is unacceptable,
enter a new set of characters that contains 11

or fewer characters.

?SRCCOM-W-Files are different

The specified files were compared and differ-

This message is informational.

ences were located.

?SYSGEN-E-File not found DEV:FILNAM.TYP

The specified SYSGEN answer file was not
found on the specified device. SYSGEN asks
~for a file name again.
?SYSGEN-E-Invalid baud rate

The baud rate specified is invalid.

?SYSGEN-E-Invalid device DEV:

An invalid device was specified.

Check ffor a typing error. Give the name of an
existing SYSGEN answer file. Press the
ESCAPE key for more information.

Check for a typing error. Be sure to specify

one of the following bauds: 110, 150, 300,
1200, 2400, 4800, or 9600.

SYSGEN asks for another device specifica-

tion. Type a question mark (?) for a list of
valid device names. Respond to the SYSGEN
dialog with a valid device specification. Press
the ESCAPE key for more information.

2SYSGEN-E-Invalid device for the monitor(s) selected DEV:

The specified device handler cannot be built
with the monitor(s) specified.

To build the specified device handler, rerun
SYSGEN and specify the appropriate monitor. Press the ESCAPE key for more information.

9SYSGEN-E-Invalid filename: DEV:FILNAM.TYP

An invalid file name was used to specify a
SYSGEN answer file.

Try the operation again using a valid file
name. Press the ESCAPE key for more information.

?SYSGEN-E-No monitor requested

A NO response was given to all possible mon-

itor choices during a SYSGEN run.

SYSGEN asks again which monitors are to

be built. Respond with YES to at least one of
the monitor type queries of the SYSGEN dialog. Press the ESCAPE key for more information.

?SYSGEN-F-Error creating DEV:FILNAM.TYP

An error occurred while the specified

SYSGEN output file was being created.

Check the procedures for recovery from hard
error conditions listed in Section 2.0.

Version 5.1, July 1984

RT-11 System Message Manual

153

?SYSGEN-F-Input
error DEV:FILNAM.TYP
A hardware error occurred while SYSGEN
was accessing the specified file.

Check the procedures for recovery from hard
error conditions listed in Section 2.0.

?SYSGEN-F-Protected file already exists DEV:FILNAM.TYP
An attempt was made to open a file, using a
name already associated with an existing
protected file.

Use the monitor UNPROTECT command or
the PIP /Z option to change the protection
level of the existing file, or use a different
name to open a new file.

?SYSGEN-W-Exceeded total number of valid DL11 lines

The number of local and remote lines is
greater than eight.

SYSGEN asks again for the number of
LOCAL and REMOTE lines. Respond to the

SYSGEN dialog with a number of local and
remote lines that is eight or less. Press the
ESCAPE key for more information.

?SYSGEN-W-File already exists DEV:FILNAM.TYP
The filename specified already exists.

SYSGEN asks if this file will be used or if
another filename will be specified. Respond
to the SYSGEN dialog. Press the ESCAPE
key for more information.

?SYSGEN-W-Invalid physical device name DEV:

The physical device name is not one to three
alphanumeric characters.

SYSGEN asks for another physical device
name. Provide a valid physical device name

in response to the SYSGEN prompt. Press
the ESCAPE key for more information.

?SYSGEN-W-Output error DEV:FILNAM.TYP
A hardware error occurred while SYSGEN
was accessing the specified file.

Check the procedures for recovery from hard
error conditions listed in Section 2.0.

?TRANSF-F-Channel in use

An internal TRANSF error occurred.

Reboot the host system and try the operation
again. If the error occurs again, install a new

copy of TRANSF.SAV on the host and retry
the operation. If the error persists, submit an

SPR to DIGITAL. If possible, include a hardcopy listing or a summary of the console ses-

sion from boot time until the error occurred.

- ?TRANSF-F-Channel not open
An internal TRANSF error occurred.

Reboot the host system and try the operation
again. If the error occurs again, install a new

copy of TRANSF.SAV on the host and retry
the operation. If the error persists, submit an

SPR to DIGITAL. If possible, include a hardcopy listing or a summary of the console ses-

sion from boot time until the error occurred.

Version 5.1, July 1984

154

RT-11 System Message Manual

?TRANSF-F-Conflicting option information

The /T option was specified with both the input and output file.

Use the /T option with only the input or output file specification, whichever is associated
with your stand-alone system.

?TRANSF-F-Device full DEV:

The directory of the specified output device
on the host system does not have enough
room for the file name of the file being trans-

Choose another output device for the operation, or delete some files from the output device and retry the operation.

ferred.

TRANSF-F-File created; protected file already exists DEV:FILNAM.TYP
A protected file exists on the host output device, along with a newly created unprotected
file of the same name.

?TRANSF-F-File not found DEV:FILNAM.TYP
Check for a typing error in the command
The input file specified was not found on the
host device specified.

line. Verify that the file name exists as en-

tered in the command line, and try the operation again.

?TRANSF-F-Input error DEV:

A hardware error occurred while TRANSF
was reading from the host device.

Check the procedures in Section 2.0 for recov-

ery from hard error conditions.

?TRANSF-F-Invalid command

The command string entered is not a valid
CSI or CCL command string.

?TRANSF-F-Invalid device DEV:

The host device specified in a TRANSF command line is invalid.

?TRANSF-F-Invalid option: /x

An invalid option was used in the TRANSF
command line.

?TRANSF-F-Output error DEV:
A hardware error occurred while TRANSF
was writing to the host device.

Check the command line for typing errors.

Reenter the command, using CSI or CCL
command string syntax.

Check for a typing error in the command
line. Verify that the device specified is valid.

Check for a typing error in the command
line. Use only the options listed as valid for
TRANSF.

Check the procedures in Section 2.0 for recov-

ery from hard error conditions.

?TRANSF-F-Protected file already exists DEV:FILNAM.TYP
A protected file already exists on the host
output device with the same name as the file
specified in the command. The file transfer is

Remove the protection from the existing file,
or use a different output file name.

not processed.

Version 5.1, July 1984

RT-11 System Message Manual

154.1

?TRANSF-F-Read past end of file
An internal TRANSF error occurred.

Reboot the host system and try the operation
again. If the error occurs again, install a new
copy of TRANSF.SAV on the host and retry
the operation. If the error persists, submit an

SPR to DIGITAL. If possible, include a hardcopy listing or a summary of the console session from boot time until the error occurred.

?TRANSF-F-Transfer aborted
A

file

transfer

was

aborted.

Either

If an I/O error occurred, try the operation
again after hard-error recovery procedures

<CTRL/C> was typed or an I/O error oc-

curred on the host system.

have been performed on the host.

?TRANSF-F-Transfer aborted by remote
A file transfer was aborted due to an I/O er-

Check the procedures listed in Section 2.0 for

ror on the stand-alone system or via the

recovery from hard error conditions.

RESET command.

?TRANSF-F-Unable to attach terminal

In a multiterminal environment, TRANSF

Remove the job that has attached the shared

was unable to attach the shared console be-

console and run TRANSF again.

cause it was already attached by another job.

?TRANSF-F-VTCOM not running on remote

VTCOM is not running on your stand-alone

Run VTCOM and try the operation again.

system, or the host system’s response time is

slow due to heavy usage and TRANSF timed
out

before

receiving

response

from

VTCOM.

?TRANSF-F-Write past end of file
An internal TRANSF error occurred.

Reboot the host system and try the operation
again. If the error occurs again, install a new
copy of TRANSF.SAV on the host and retry

the operation. If the error persists, submit an
SPR to DIGITAL. If possible, include a hardcopy listing or a summary of the console ses-

sion from boot time until the error occurred.

?TRANSF-W-Transfer completed with n retries
The transfer completed, but n retries were

performed.

Check the transfer output to make sure no
errors were transmitted.

?VHANDL-F-Window error
The file created with the linker /V option is
using too many windows.

Relink, using fewer windows.

?VTCOM-E-No dial string
You issued the DIAL command without specifying a dial string, and no default dial string
has been set.
Version 5.1, July 1984

154.2

RT-11 System Message Manual

Retype

the

DIAL

command.

When

prompt appears, type a dial string.

the

?VTCOM-F-Device full

In an OPENLOG operation or in a TRANSF
file transfer from the host, the directory of
the output device does not have enough room
for the file name of the file being transferred.

?VTCOM-F-Directory 1/0 error

A hardware error occurred while a directory
was being read when a SEND, OPENLOG, or
TRANSF operation was started.

VTCOM-F-Fetch error dd:
A serious VICOM or internal system error

occurred. The copy of VTCOM, the monitor
file, or the specified device handler (XL or
XC) may be corrupted on disk. The in-core
copy of VICOM or the monitor may have
been corrupted.

Choose another output device for the operation, or delete some files from the output device and retry the operation.

Check the procedures listed in Section 2.0 for

recovery from hard error conditions.

Reboot the system and try the operation

again. If the error occurs again, get a new

copy of VTCOM and the specified device handler. Retry the operation. If the error per-

sists, submit an SPR to DIGITAL. If possible,
include a hard-copy listing or a summary of
the console session from boot time until the
error occurred.

2VTCOM-F-File not found

The input file specified during a SEND operation or a TRANSF file transfer from your

Check for a typing error in the command
line, verify that the file name exists as typed
in the command line, and try the operation

ume you specified.

again.

stand-alone system was not found on the vol-

2VTCOM-F-Handler not loaded
The handler needed for a SEND, OPENLOG,
or TRANSEF operation is not loaded.

PVTCOM-F-Handler not loaded dd:
The VTCOM handler (XL or XC) is not
loaded.

VTCOM-F-Insufficient memory

Not enough memory is available for VTICOM
to fetch the XC or XL handler.

Load the handler by using the LOAD com-

mand and retry the operation.

Load the proper handler (XL for PDP-11 and

PDT-11 systems, XC for Professional 300 series systems) and retry the operation.

If you are running under the XM monitor,
run VITCOM.SAV rather than VTCOM.REL.
Otherwise, see Section 3.0 for information on
how to increase memory resources.

VTCOM-F-Internal error

An internal error has occurred.

Run VTCOM again and retry the operation.
If the error persists, submit an SPR to
DIGITAL. If possible, include a hard-copy
listing or a summary of the console session
from boot time until the error occurred.

Version 5.1, July 1984

RT-11 System Message Manual 154.3

?VTCOM-F-Internal task stack overflow
An internal error hds occurred.

?VTCOM-F-Invalid command
The command you
VTCOM command.

typed

is not

a valid

Check for a typing error in the command
line. Check the list of valid VTCOM com-

mands and command abbreviations by typing

RETURN in response to the TT::VTCOM>

prompt. Try the operation again.

?VTCOM-F-Invalid device
The device specified in an OPENLOG or
SEND operation, or the device on the standalone system in a TRANSF file transfer, is
invalid.

Check for a typing error in the command
line. Verify that the device specified is valid.

?VTCOM-F-Invalid device dd:
The device (XC or XL) was not found in the
system device tables.

Make sure XC or XL has been installed. Try
the operation again.

?VTCOM-F-Invalid file name
The file name specified for a SEND or
OPENLOG operation, or the stand-alone sys-

tem’s file name during a TRANSF file transfer, is invalid.

Check for a typing error in the command
line. Make sure the file name you specify in-

cludes only six characters in the file name
and three in the file type.

?VTCOM-F-1/O error
A hardware error occurred during a SEND,

OPENLOG, or TRANSF operation.

Check the procedures in Section 2.0 for recovery from hard error conditions.

?VTCOM-F-Line too long
The line you typed in response to the
VTCOM prompt TT:VICOM> during a

SEND or OPENLOG operation is too long.

Check for a typing error in the command
line. Make sure the command you typed is a

valid VTCOM command, and make sure your

response to the VITCOM prompt includes no

more than 40 characters. Try the operation

again.

?VTCOM-F-.LOOKUP error dd:
An error occurred when VITCOM attempted

to open a channel to the XC or XL handler.

Run VTCOM again and retry the operation.
If the error persists, submit an SPR to
DIGITAL. If possible, include a hard-copy

listing or a summary of the console session
from boot time until the error occurred.

Version 5.1, July 1984

154.4

RT-11 System Message Manual

?VTCOM-F-Protected file already exists
The file you specified for an OPENLOG or
TRANSF operation already exists as a pro-

tected file on the stand-alone system volume

Use another file name, or unprotect the file

on the stand-alone system. Try the operation

again.

you specified.

2VTCOM-F-Protocol version mismatch
The versions of the VTCOM and TRANSF
protocol you are using do not match.

Make sure the version of TRANSF installed

on the host system was distributed with the
same version of RT-11 as the version of
VTCOM. VTCOM and TRANSF are distributed on the RT-11 distribution kit as
matched versions.

2VTCOM-F-Unexpected EOF

The log file became full before you closed it
with the CLOSE command. VTCOM closes

Squeeze the device on which the log file resides, or use another device for the log file.

the log file when this error occurs.

?VTCOM-F-Wrong version of dd:
The version of XL or XC you are using is not
the version required by VITCOM.

2VTCOM-I-Connection established
VTCOM has established a connection to a remote modem.

VTCOM-I-Connection lost

The connection to a remote modem has been

lost.

Make sure the version of XC or XL you are

using was distributed with the same version
of RT-11 as the version of VTCOM. VTCOM
and its handlers are distributed on the
RT-11 distribution kit as matched versions.

You can now log onto your host system. This

message is informational.

Reestablish the connection, or leave VTCOM
terminal mode. This message is informational.

2VTCOM-W-File not sent, transfer in progress
The second SEND command is ignored. Wait
A SEND command was issued while a SEND
until the operation in progress completes beoperation was already in progress.
fore issuing another SEND command.

VTCOM-W-Log file closed due to I/O error

A hardware error has occurred during an

OPENLOG operation. The log file has been

Check the procedures listed in Section 2.0 for

recovery from hard error conditions.

closed.

?VTCOM-W-Log file not open

A log file was not open when a LOG or
NOLOG command was issued.

Open a log file by using the OPENLOG command and reissue the command.

WARNING: FORTRAN IV messages

Section 5.0 contains all FORTRAN IV mes-

sages.

Version 5.1, July 1984

RT-11 System Message Manual

154.5

8.0

MACRO-11 Messages
The MACRO-11 system prints diagnostic error codes during the second
assembly pass as the first character of a source line on which the assembler
detects an error. These one-letter diagnostic error codes indicate the type of
error that has occurred. This section begins with this group of codes; all
other MACRO-11 messages are alphabetized according to the rules detailed in Section 1.1.

See the PDP-11 MACRO-11 Language Reference Manual for more information about MACRO-11 error conditions.

8.1

List of MACRO-11 Messages

MACRO-11
MACRO-11 found an addressing or a relocation error.

Check the suggested remedies for the possible causes of error listed below, and refer to
the RT-11 System Utilities Manual for more
detailed information.
General Addressing Errors
Check for a conditional branch instruction
target that is too far above or below the current statement. Make sure that the target is
within —128 to + 127 (decimal) words of the
instruction.
Check for a statement that makes an invalid

change to the current location counter. For
example, a statement could force the current
location counter to cross a .PSECT boundary.
Check for a statement that contains an invalid address expression. For example, an absolute address expression may not have a
global symbol, a relocatable value, or a complex relocatable value. The directives .BLKB,
.BLKW, and .REPT must have an absolute
value or an expression that reduces to an ab-

solute value.
Check the statement for separate expressions
that are not separated by commas.
Make sure that symbols defined by the .ENABL GBL directive as globals during the
first pass have not been defined during the
second pass; if this happens, a general addressing error occurs.
Invalid Forward References

Check for a global assignment statement
that contains a forward reference to another
symbol.

RT-11 System Message Manual

155

Check for an expression that defines the
value of the current location counter and contains a forward reference.
Invalid Argument for Directive
.ENABL/.DSABL — Check for
rectly defined argument.

incor-

JF/IIF — Check for a missing conditional
argument, an incorrectly defined conditional
test, or an invalid argument expression
value.

JRP/IRPC — Check for a missing dummy
argument.

LIST/NLIST — Check for an incorrectly
defined argument.

.MACRO — Check for an invalid or a duplicate symbol in the dummy argument list.
NARG/.NCHAR/NTYPE — Include a symbol in the directive.

PSECT — Check for an incorrectly defined
argument.

.RADIX — The new radix can have a value
only of 2, 8, or 10.

.TITLE — Check for a missing program
name or for a program name with an invalid
first character. The first character must be
from the Radix—50 character set.
Unmatched Delimiter or Invalid Argument
Construction
ASCII/.ASCIZ/.RAD50/.INDENT/
NCHAR — Check for unbalanced character
string or argument string delimiters, an invalid character used as a delimiter, or an invalid argument construction.

Instructions or word data are being assembled at an odd address. The system increments the location counter by 1 and contin-

Insert an .EVEN statement before the statement in error.

ues.

MACRO-11 found a nonlocal label that is defined in an earlier statement.

156

RT-11 System Message Manual

Rename one of the labels.

MACRO-11 reached the end of the source in-

Insert a .END directive.

put without finding a .END directive. The
-system supplies a .END statement and completes the current assembly pass.

MACRO-11 detected one or more invalid
characters. A question mark (?) replaces each
invalid character on the assembly listing,
and MACRO-11 continues after ignoring the
character.

Replace invalid characters with characters
that are in the language character set.

MACRO-11 encountered an input line longer
than 132 characters. This error often occurs
when expansion of a macro causes excessive
substitution of real arguments for dummy ar-

Shorten the line to 132 or fewer characters.

guments.

MACRO-11 detected a label that is the same

as an earlier label. Two labels whose first six
characters are equal cause this error.

Change one of the conflicting labels.

MACRO-11 detected a number that is not in
the current program radix. The number is
processed as a decimal value.

Correct the number.

MACRO-11 encountered an op-code error, or
the permissible nesting level for conditional
assemblies was exceeded. Attempting to ex-

Check for a syntax error in the statement.
Make sure that the instruction format for the
op code is correct. Check the program logic to
verify that conditionals are not nested more
than 16 levels deep.

pand a macro that is unidentified after a
.MCALL search also causes this error.

MACRO-11 encountered a phase error. This
error occurs when the definition or the value
of a label differs from one assembly pass to
the next or when a local symbol is used more
than once in a local symbol block.

Check the program logic.

MACRO-11 found a statement with questionable syntax. For example, arguments
may be missing, there may be too many arguments, or the instruction scan may not
have been completed.

Check for a syntax error, and verify that a
line feed or a form feed immediately follows a
carriage return.

RT-11 System Message Manual

157

MACRO-11 found an error that involves a
register. There may be an invalid reference
to a register or an invalid use of a register.
Attempting to redefine a standard register
symbol without first issuing the .DSABL
REG directive also causes this error.

Correct the program logic and the statement.

MACRO-11 detected a truncation error. A
number that generates more than 16 bitsin a
word and an expression in a .BYTE directive

Correct the statement.

(or trap instruction) that generates more

than 8 significant bits causes this error.
U

MACRO-11 found an undefined symbol. The

Define the symbol.

MACRO-11 found an incompatible instruction. This is a warning that the instruction is
not defined for all PDP-11 hardware configu-

Refer to the appropriate processor handbook
for a description of the instruction set to be

symbol is assigned a value of 0.

used with the system.

rations.

MACRO-F-Device full DEV:

The output volume does not have enough
room for an output file specified in the com-

Refer to Section 3.0 for information on how to
increase storage space.

mand string.

?MACRO-F-File not found DEV:FILNAM.TYP
The input file in the command line is not on
the specified device.

Correct any file specification errors in the

command line and enter it again.

'MACRO-F-.INCLUDE directive file error
1. The file specified in the INCLUDE statement either does not exist or is invalid.

The device specified in the command line

The .INCLUDE stacking depth exceeds

with the INCLUDE directive.

is not available.
five.

MACRO-F-Insufficient memory

MACRO does not have the minimum amount
of memory (16K words) necessary to run.

Check for a typing error in the command
line. Use file specifications that are valid
Enter the command line again, specifying an available device.

Make sure that the INCLUDE stacking

depth does not exceed five.

Refer to Section 3.0 for information on how to
increase memory space.

‘MACRO-F-Invalid command
The command line contains a syntax error or

specifies more than six input files.

158 RT-11 System Message Manual

Correct and retype the command line.

MACRO-F-Invalid device

The device specified in the command line is
not on the system.

Either install the device or substitute another.

?MACRO-F-Invalid macro library

The library file either has been corrupted or
was not produced by the RT-11 librarian,

Use LIBR to generate a new copy of SYSMAC.SML.

LIBR.

?MACRO-F-Invalid option: /x

The specified option was not recognized by
the program.

Check for a typing error in the command
line. Use only a valid listing control or a
functional control (or CREF) option.

"MACRO-F-1/O error on DEV:FILNAM.TYP
A hardware error occurred during a read
from or write to the specified file.

Check the procedures for recovery from hard
error conditions listed in Section 2.0.

MACRO-F-I/O error on workfile

MACRO failed to read, write, or open to its
workfile, WRK.TMP, possibly because of a
hard error condition. This error can occur
when there is not enough contiguous disk
space to accommodate the workfile.

Check the procedures for recovery from hard
error conditions listed in Section 2.0.
Use the SQUEEZE command or the DUP /S
option to accommodate the workfile.

MACRO-F-LIBRARY directive file error

The file specified in the .LIBRARY statement either does not exist or is invalid.

Check for a typing error in the command
line. Use file specifications that are valid
with the .LIBRARY directive.

The file specification in the .LIBRARY
directive is for a non-random-access de-

Make sure that the file specification used
in the .LIBRARY directive is for a random-access device.

Enter the command line again, specifying an available device.

Make sure that the .LIBRARY stacking
depth does not exceed the maximum
depth allowed.

vice.

The device specified in the command line
is not available.

The .LIBRARY stacking depth exceeds
the maximum depth allowed.

MACRO-F-Protected file already exists DEV:FILNAM.TYP

An attempt was made to create a file having
the same name as an existing protected file.

Use the monitor UNPROTECT command or
the PIP /Z option to change the protection
level of the existing file, or use a different
name to create the new file.

?MACRO-F-Storage limit exceeded (64K)

MACROQO’s Virtual Symbol Table can store
symbols and macros up to 64K in any combination. The program contains more than 64K
of one or both of these elements.

Check the program logic for a condition that
leads to excessive size, such as a macro expansion that recursively calls itself without a
terminating condition. If necessary, reduce
the requirements of the source program by
segmenting it into separate modules, and assemble each separately.

MACRO-W-I/O error on CREF file: CREF aborted
Either not enough space was available to perform the operation or an I/O error occurred
while the CREF workfile was being written.
CREF processing is terminated, but the assembly will continue.

160

RT-11 System Message Manual

Refer to Section 3.0 for information about increasing storage space.

9.0

Editor Messages
This section contains the messages displayed by the system EDIT program,
the keypad editor program (KED), and the system single-line editor program. The messages are alphabetized according to the rules detailed in
Section 1.1.

9.1

Edit Messages

This section lists the error messages displayed by the RT—-11 system utility
EDIT program. If you cannot determine the location of your error by reading the explanation for the message in this section, see the RT-11 System

User’s Guide for a description of EDIT.

9.1.1 Special Information About EDIT Messages — See Section 1.2 for a description of the format of EDIT messages.
9.1.2

List of EDIT Messages

?EDIT-F-Command aborted
A command was prematurely terminated because CTRL/C was typed twice.

Examine the effect of the termination for any
undesirable conditions and correct, if necessary.

?EDIT-F-Command buffer full; no command(s) executed
The command exceeded the space allowed for
a command string in the command buffer.

Empty the save or the macro buffers, if possible, or write part of the text buffer to the output file. Retype the command and any subsequent lengthy commands as a series of
smaller commands or shorter sequences.

EDIT-F-Device full

Not enough disk space is available to accommodate a file of the size requested in the EW
or the EB command or in the /ALLOCATE
specification to the EDIT command.

Use the SQUEEZE command to compress the
disk, if possible, or request a file of smaller
size. See Section 3.0 for information on how
to increase storage and memory resources.

No room exists in the volume directory for
the output file name. This message occurs
following an EB or an EW command or the
input specification to the EDIT command.

Refer to Section 3.0 for information on how to
increase storage space.

?EDIT-F-End of input file

A READ, NEXT, or file search command was
not executed because the end of the input file
was reached.

Close the file by using EX or EF; reopen it if
more editing remains to be done.

RT-11 System Message Manual

161

?EDIT-F-"<>" error; no command(s) executed
Iteration brackets are nested too deep, used

Make sure that all brackets are properly

incorrectly, or not matched.

matched and that the number of nested
brackets does not exceed 20 levels.

?EDI’l‘mF-?File not found
An attempt was made to open a nonexistent

Check for a typing error in the command

file for editing.

line. Verify that the file name exists as entered in the command line, and try the operation again.

?EDIT-F-Input error

A hardware error occurred during a read operation.

Check the procedures for recovery from hard
error conditions listed in Section 2.0.

?EDIT-F-Insufficient memory

An attempt was made touse the I, S, U, R, N,
C, or E command with insufficient room for
the appropriate buffer.

Delete unwanted buffers to create more room
by using the OU or OM command (see the
RT-11 System User’s Guide), or write text to
the output file.

?EDIT-F-Invalid argument; no command(s) executed
1.

The argument specified is invalid for the

command used.

2. A negative argument is specified where a

Check the command format for proper argument usage and reenter the command correctly.

positive one is expected.

The

argument

outside

the

range

+ 16,383 to —16,383.

?EDIT-F-Invalid command; no command(s) executed
1.

The editor does not recognize the command line specified.

Check for a typing error in the command
line. Check the format of any editing
command that produces this error, and
enter the command correctly.

ED was not the first command used to
activate the display hardware.

Recall the editor and type ED before entering any other editing commands. Remember to type the insert command (I)
before inserting text.

?EDIT-F-Invalid device
An attempt was made to open a file on an
invalid device or to use display hardware
when none is available.

Check for a typing error in the command
line. Verify that the device indicated is valid
and that display hardware exists and is not

already in use by another job.

162 RT-11 Syatem Message Manual

?EDIT-F-Invalid file name

An invalid file name was specified in an EB,
EW, or ER command, or as input to the EDIT
command.

Check for a typing error in the command
line. Make sure that the dev:filname.typ[n]
specification does not exceed 19 characters
and is in the proper format. Verify that an
input file name exists as entered.

?EDIT-F-Invalid macro; no commé nd(s) executed

Delimiters in an M command are used

improperly.

Check for a typing error in the command
line. Make sure that the character used
for the delimiters does not appear in the
macro.

An attempt was made to enter an M or
an EM command during execution of a

Try the command again, and wait until
the current macro has finished executing
before entering the M or EM command.

?EDIT-F-No file open for input

An R, N, F, or P command was issued, but no
file had been opened for input.

Check for a typing error in the command
line. Use the ER command to open a file for
input and then reenter the command.

?EDIT-F-No file open for output

An EX, EF, F, or W command was issued, but
no file had been opened for output.

Check for a typing error in the command
line. Use the EW command to open a file for
output and then reenter the command.

?EDIT-F-Output error

A hardware error occurred during a write operation.

Check the procedures for recovery from hard
error conditions listed in Section 2.0.

?EDIT-F-Output file full

No free space is left in the output file.

Close the file by using an EF command, or
close the file and open a new file for output
by using the EW command.

?EDIT-F-Protected file already exists

An attempt was made to edit a protected file
or to create a protected file with the same
name as an existing file.

Use the monitor UNPROTECT command or
the PIP /Z option to change the protection
level of the existing file, or use a different
name to create the new file.

?EDIT-F-Protected .BAK file exists
A protected .BAK file having the same name

Exit from EDIT, then use the monitor UNPROTECT command or the PIP /Z option to

in an edit backup operation.

change the protection level of the backup file.

as the specified file has already been created

Perform the edit backup operation again.

?EDIT-F-Search failed
The text string specified in a G, F, or P command was not found.

Check for a typing error in the command
line. Make sure that the text string exists in
the file as specified in the command line. If
this error occurs following a Get command,
the pointer is positioned at the end of the current text buffer and the command can be
reentered. If the error follows a Find or a Position command, the end-of-the file is detected and the pointer is positioned at the beginning of an empty text buffer; close the file,
reopen it, and then reenter the command.

?EDITmFQ-System I/O error
A system operation, such as opening a file,
failed because of an I/O error, most probably
one involving a write-protected volume.

Check the procedures for recovery from hard
error conditions listed in Section 2.0.

EDIT-W-Command buffer almost full

The command entered is within 10 characters of exceeding the space available in the
command buffer.

Complete the command, using fewer than 10
characters, if possible. Otherwise, press the
ESCAPE key twice to execute that portion of
the command line already completed, and
then enter the remainder as a second command.

?EDIT-W-Superseding existing file

An EW or an EB command was issued for an
already existing file name. If the new file is
closed, the old one will be deleted.

9.2

To avoid replacing the file, terminate the edit

with CTRL/C, followed by two ESCAPEs.
Then use the monitor REENTER command.

KED Messages

This section lists the error messages that the keypad editor can display. If
you cannot find the error by reading this section, refer to the Keypad Editor
User’s Guide.
9.2.1

Special Information About KED Messages —

The keypad editor has

three groups of error messages:

Command-level messages

HELP function messages

Prompts and informative messages

The command-level messages are listed first, and they appear in the format
described in Section 1.2. The HELP function messages, which appear in the
center of the bottom screen line of your video terminal, are then listed,
followed by the list of prompts and informative messages.

164

RT-11 System Message Manual

9.2.2

List of KED Messages

?KED-F-Bad call to .VVV.V

The keypad editor may have malfunctioned.

Try the operation again. If the error persists,
submit an SPR to DIGITAL; include with the
SPR a program listing and a machine-readable source program, if possible.

?KED-F-Illegal command line

?KED-F-Illegal file specification
The keypad editor may have malfunctioned.

Try the operation again. If the error persists,
submit an SPR to DIGITAL; include with the
SPR a program listing and a machine-read-

able source program, if possible.
?KED-F-Insufficient memory

The keypad editor may have malfunctioned,
or it cannot run because too little memory is
available. (The keypad editor requires approximately 16K words.)

Switch to a system that provides more memory resources or to a smaller RT-11 monitor.
Refer to Section 3.0 for information on how to
increase memory resources. If the error persists, submit an SPR to DIGITAL; include
with the SPR a program listing and a machine-readable source program, if possible.

?KED-F-1/0O or device error — Continue (Y,N) ?

The keypad editor detected an I/O or a device
error. Situations that can cause this message

e A device being used is switched off line.
e An output device being used is write- locked.

e A volume being used has a bad block.

Before typing a response, check that the device is on line; if it is an output device, check
that it is write-enabled. To make the keypad
editor try the same function or command
again, type Y and press the RETURN key. If
the command or function works, continue
editing. If the command or function does not
work, or if any character other than Y was
typed, the keypad editor quits without saving
any of the editing work and returns to the
monitor.

?KED-F-L/O error while trimming output
The keypad editor may have malfunctioned.

Try the operation again. If the error persists,
submit an SPR to DIGITAL; include with the
SPR a program listing and a machine-readable source program, if possible.

?KED-F-Output file shorter than input file

The space available for the output file is
smaller than the input file.

Use the SQUEEZE command to consolidate
free space on the output volume or use a different volume. Refer to Section 3.0 for information on how to increase storage space.

RT-11 System Message Manual

165

?KED-F-RDBKW — No space to read into
?KED-F-RDFWD — No space to read

?KED-F-RDFWD — Pointer corrupt
?KED-F-SETUP — Allocation error

?KED-F-SPCFRE — Logic error, character count wrong
The keypad editor may have malfunctioned.

Try the operation again. If the error persists,

submit an SPR to DIGITAL; include with the
SPR a program listing and a machine-readable source program, if possible.

?KED-F-Temporary file shorter than input file

The number of blocks specified with the /BL
option is less than the size of the input file
that was specified.

Enter the command line again with a temporary file size that is greater than the input
file size.

?KED-F-TTY??? Logic error

The keypad editor may have malfunctioned.

Try the operation again. If the error persists,
submit an SPR to DIGITAL; include with the
SPR a program listing and a machine-readable source program, if possible.

?KED-F-Unable to access input device
The keypad editor could not access the auxiliary device for one of the following reasons:
®

The device is invalid.

The device is not ready.

The device is not installed.

The volume has too many bad blocks.

No room is available for the device handler.

Check the device abbreviation. If it is correct,
make sure that the device is on line. Use the
SHOW/DEVICES command to see which devices your system includes, and use the IN-

STALL command to install the device you
need, if necessary. If the message persists,
use the DIRECTORY/BADBLOCKS command to check the volume being used for bad
blocks; if many bad blocks are on the volume,
use another copy. If the handler for the device to be used cannot be installed, switch to
a system that provides more memory resources or to a smaller RT-11 monitor. Refer

to Section 3.0 for information on how to increase memory resources. If the error still

persists, submit an SPR to DIGITAL; include
with the SPR a program listing and a ma-

chine-readable source program, if possible.
?KED-F-Unable to access output device

The keypad editor probably could not load
the output device handler.

If the device name is correct, make sure that
the system volume contains the device han-

dler. If the message occurs again, check the
device abbreviation. If it is correct, make
sure that the device is on line. Use the
SHOW/DEVICES command to see which devices your system includes, and use the IN-

STALL command to install the device you
need, if necessary. If the error persists, use

166

RT-11 System Message Manual

the DIRECTORY/BADBLOCKS command to
check the volume being used for bad blocks;
if many bad blocks are on the volume, use
another copy. If the handler for the device to
be used cannot be installed switch to a system that provides more memory resources or
to a smaller RT-11 monitor. Refer to Section
3.0 for information on how to increase memory resources. If the error still persists, submit an SPR to DIGITAL; include with the
SPR a program listing and a machine-readable source program, if possible.

?KED-F-Unable to attach terminal

The keypad editor cannot attach the terminal

Check with your system manager.

and therefore cannot proceed.

?KED-F-Unable to create output file
?KED-F-Unable to edit input file

The input file specified is too long to be han-

dled by the keypad editor. With the keypad
editor, a file that is larger than 16383(decimal) blocks cannot be edited.

Find another way to edit the file. If neces-

sary, consult an experienced user about splitting the file into separate parts that are
small enough for the keypad editor.

?KED-F-Unable to open input file
The keypad editor could not open the input
file for one of the following reasons:

e The volume does not contain the file.

Check the file specification. If it is correct,
make sure that the correct volume is installed and that the input device is on line.

e The volume has not been initialized.
e The input device is not on line.

?KED-F-Unable to open output file

The keypad editor could not open the output

file for one of the following reasons:

e The device is not ready or is write-locked.

Make sure that the output volume is properly
installed and initialized. If the volume is too
full, use another volume. To edit a protected
file, use a different output file specification.

e The volume is not initialized.

e The volume does not have sufficient free
space for the output file.

e The output file exists and is protected.
?KED-F-Unable to trim output file

?KED..FWWRBKW — Bad block number
?KED-F-WRBKW — Block overrun
?KED-F-WRBKW — Plygnd not empty

?KED-F-WRFWD — Bad block number
?KED-F-WRFWD — Block overrun

?KED-F-WRFWD — Not enough data
RT-11 System Message Manual

167

The keypad editor may have malfunctioned.

Try the operation again. If the error persists,
submit an SPR to DIGITAL; include with the

SPR a program listing and a machine-readable source program, if possible.
?KED-F-Wrong version of RT-11

An attempt was made to run an RT-11 Version 5 utility (KED) on a previous version of
RT-11.

Do not run RT-11 Version 5 utilities under
earlier RT-11 versions.

?KED-W-Input file contains records that will be truncated — Continue (Y,N)?
The largest variable length record in the in-

put file is larger than the space that the keypad editor has available to read records.
Records larger than that space will be truncated when read, and the truncated data will
be lost.

To have the keypad editor continue process-

ing, type Y and press the RETURN key. To
stop the keypad editor, type N and press the
RETURN key.

?KED-W-Input file not properly closed — Continue (Y,N)?
The keypad editor found conflicting informa~ tion about the input file that was specified.

To have the keypad editor continue, type Y
and press the RETURN key. The keypad editor will try to read the file, but the file may
contain invalid data or no data. If data at the
end of the file appears to have been deleted
because the end-of-file symbol appears earlier than expected, the file may contain a record that is too long for one of the keypad editor’s buffers.
To stop the keypad editor, type N and press
the RETURN key.

?KED-W-Only MMMMMM blocks available for insertions — Continue (Y,N) ?
Free space on the output volume is less than
10 blocks larger than the input file. The key-

pad editor reports (in decimal) the number of
blocks available.

To continue the editing session, type Y and
press the RETURN key. The keypad editor
will signal when the file becomes as large as
possible. To cancel the editing session and return to the command level prompt (%), type

any other answer. Use the SQUEEZE command to consolidate free space on the output
volume, or specify an output volume that has
more free space.

?KED-W-Output file exists — Continue (Y,N) ?
The output file name specified is the same as
an existing file on the output volume.

To delete the existing file and create a new
one with the same name, type Y and press
the RETURN key. To preserve the existing

file and return to the system or keypad editor
prompt, type any other answer.

Version 5.1, July 1984

168 RT-11 System Message Manual

?KED-W-Output files purged

The keypad editor displays this message

when the QUIT command is used. If an auxiliary output file is open when the command
is typed, the keypad editor does not save the
file. If a file is being edited or created, the
keypad editor does not save any of the edit-

This message is informational.

ing work.

Version 5.1, July 1984

RT-11 System Message Manual

168.1

?KED-W-Unable to rename input file to BAK file type

The original input file was not saved with
the .BAK file type. However, the keypad editor attempted to save the output file.

This message is informational. If another
copy of the original file is not available, it
cannot be recovered.

ADJUST illegal in inspect mode
The TABS ADJUST command is invalid
when a file is inspected.

Use another command or function.

Advance char finds end of file
The CHAR function or the rightarrow function moved the cursor to the bottom of the
file.

Use any valid function or command.

Advance line finds end of file
The BLINE function moved the cursor to the

Use another function.

end of the file. With line count definitions,
the PAGE and SECTION functions can also
cause this message.
Advance word finds end of file

The WORD function moved the cursor to the
bottom of the file, or the DELWORD function
deleted the last character in the file.

Use any valid function or command.

Argument error to INCLUDE or SKIP

The keypad editor did not complete an INCLUDE or a SKIP command because a negative line or a page count was specified.

Use any valid function or command.

Argument error to WRITE
The keypad editor did not complete a WRITE
command because a negative line or a page
count was specified.

Use any valid function or command.

Arrow command finds extremity of file

The uparrow function moved the cursor to
the top of the file, or the downarrow function
moved the cursor to the bottom of the file.

Use any valid function or command.

Auxiliary input file contains records that will be truncated

The keypad editor loads this message for in-

Use any valid function or command.

formation purposes when the answer NO is
given to the message Auxiliary input file
contains
records
that
will
Dbe
truncated — Continue (Y,N)?.

RT-11 System Message Manual

169

Auxiliary input file contains records that will be truncated — Continue (Y,N)?

The largest record in the auxiliary input file
specified is larger than the keypad editor can
read.

To have the keypad editor continue, type Y
and press the RETURN key. The overlong
record will be truncated when the keypad editor reads it, and the truncated data will be
lost. To stop the keypad editor, type N and
press the RETURN key.

wAuxiliary input file not open
The keypad editor did not complete an INCLUDE command because no auxiliary input
file is open. The keypad editor closes an auxiliary input file when an INCLUDE or a SKIP
command has processed the entire file.

To open an auxiliary input file, use the

OPEN INPUT command. Otherwise, use any
valid function or command.

Auxiliary input illegal during inspect

While a file was being inspected, an attempt
was made to complete functions and commands that would modify the file.

Use any valid function or command.

Auxiliary output file exists

The keypad editor loads this message for information purposes when the answer NO is
given to the message Auxiliary output file
exists — Replace (Y,N)?.

Use any valid function or command.

Auxiliary output file exists — Replace (Y,N)?

The auxiliary output file name specified is
the same as an existing file on the output
volume.

To delete the existing file and create a new
one with the same name, type Y and press
the RETURN key. To preserve the existing
file, type any other answer.

Auxiliary output file full

No more space remains in the auxiliary output file.

Use the CLOSE command to close the auxiliary output file. Open another file for auxiliary output and merge the files later in a sep-

arate editing session or with the RT-11
COPY command.

Auxiliary output file not open
The keypad editor did not complete a WRITE
command because no auxiliary output file is
open. The CLOSE and the EXIT commands
close an auxiliary output file. The PURGE
and the QUIT commands discard an auxiliary output file, if one is open.

To open an auxiliary output file, use the
OPEN OUTPUT command. Otherwise, use
any valid function or command.

Backup char finds beginning of file

The CHAR function or the leftarrow function
moved the cursor to the top of the file.

170

RT-11 System Message Manual

Use any valid function or command.

Backup line finds beginnin
The BLINE function has moved the cursor to
the top of the file. With line count definitions, the PAGE and the SECTION functions
can also cause this message.

Use any valid function or command.

Backup word finds beginning
The WORD function or the LINEFEED function moved the cursor to the top of the file.

Use any valid function or command.

Bounded search reached bound

The SET SEARCH BOUNDED command
was used to limit searches to one page. Then
a FIND or a FINDNEXT function moved the
cursor to the top or the bottom of a page without finding a string that matches the model
specified.

Use any valid function or command.

CHNGCASE finds end of file

In the ADVANCE directional mode, the
CHNGCASE function changed the case of the
last character in the file.
CHNGCASE is illegal durmg inspect

While a file was being inspected, an attempt
was made to complete functions and commands that would modify the file.

The keypad edlmr loads this

Use any valid function or command.

;

Use any valid function or command.

The keypad editor loads this message when
CTRL/C CTRL/C is typed to cancel the command or function that the keypad editor is

Use any valid function or command.

CTRL/Z or CTRL/C is typed to canml a keym
pad editor command and the Command:
prompt.

CTRL/C entered to stop operation

processing. The keypad editor repaints the

terminal screen and shows where the cursor
moved. If commands or functions are typed
while the keypad editor is displaying the
nores them.

CTRL/C or CTRL/Z ignored — use QUIT

While working with a file, the keypad editor
ignores the CTRL/Z and CTRL/C combinations.

ert

CTRL/Z or CTRL/Cin a

file, use the

SPECINS f‘umctwn To cancel a keypad editor
session without saving any open output files,
use the QUIT command.

CTRL/U finds beginning of file

The CTRL/U function deleted the first char-

Use any valid function or command.

acter in the file.

Cursor not at target

With no existing select range, the keypad editor could not complete a CUT, APPEND,
PASTE, or SUBSTITUTE function because

Use any valid function or command.

the cursor is not at a valid search target.

DELCHAR finds end of file

The DELCHAR function deleted the last

Use any valid function or command.

character in the file.

DELEOL finds end of file

The DELEOL function deleted the last char-

Use any valid function or command.

acter in the file.

DELETE finds beginning of file

The DELETE function deleted the first char-

Use any valid function or command.

acter in the file.

DELLINE finds end of file

The DELLINE function deleted the last char-

Use any valid function or command.

acter in the file.

Empty select range specified to CHNGCASE
After using the SELECT function, the
CHNGCASE function was used before a select range was built.

To change the case of several letters, build a
select range that includes them, and then use
the CHNGCASE function.

End of file reached on auxiliary input file
A SKIP or an INCLUDE command finished
reading to the bottom of an auxiliary input
file, and the keypad editor closed the file.

Use any valid function or command.

EOL finds beginning of file

The EOL function moved the cursor to the

Use any valid function or command.

top of the file.

EOL finds end of file

The EOL function moved the cursor to the

Use any valid function or command.

bottom of the file.

Erasures are illegal during inspect

While a file was being inspected, an attempt
was made to complete functions and commands that would modify the file.

172

RT-11 System Message Manual

Use any valid function or command.

Error reading auxiliary input file
The keypad editor could not read the auxiliary input device. The problem is not due to
reaching the end of the file.

If the file name is correct, make sure that the
device is on line and that it contains the
proper volume. Use another device if the device is faulty.

Error writing auxiliary output file

may have detected a bad
keypad editordevice.
The
block or a faulty

~ Make sure that the device is on line, writeenabled, and properly formatted. Try using
another auxiliary output device or volume.

Use the RT-11 DIRECTORY/BADBLOCKS
command to check for bad blocks.

EXIT stopped by CTRL/C

The keypad editor loads this message when
CTRL/C is used to cancel the EXIT command. The results are unpredictable because
they depend on several variable factors, such
as the output file size, the speed of the hardware components, and when CTRL/C is typed

‘during the exit process.

If CTRL/C CTRL/C is typed too late to cancel
the exit process, the keypad editor displays
the command-level prompt again. In this
case, the output files originally specified
have been saved. If automatic backup of
input files was also specified, they have also
been renamed. If CTRL/C CTRL/C cancels
the exit process, the keypad editor repaints
the terminal screen with the part of the file
that contains the cursor. In this case, continue editing by using any valid function or
command.

The keypad editor could not complete the
FILL command or function because the
output file or temporary file is full.
File full during INCLUDE

The keypad editor could not complete the INCLUDE command because the output file is
not large enough for the material to be
copied. The cursor is to the right of the last
character the keypad editor copied from the
auxiliary input file.

Exit and start a new session, delete and

make room for insertions, or use an auxiliary
output file.

If the file is full, exit and start a new session,
delete and make room for insertions, or use

an auxiliary output file. The CLOSE or QUIT

commands or any functions or commands
that delete material from the file can also be
used.

FILL illegal during inspect

The FILL command or function is invalid

Use another function or command.

while inspecting a file.

I/O error closing auxiliary output file
The keypad editor could not write to the auxiliary output file during a close operation.
The keypad editor may have detected a bad
block.

Try using another auxiliary output volume.
Use the RT-11 DIRECTORY/BADBLOCKS
command to check for bad blocks.

Illegal command

The keypad editor could not recognize the
command typed.

Use any valid function or command.

Illegal definition of PAGE or SECTION
The keypad editor could not process a SET
ENTITY PAGE or SET ENTITY SECTION
command for one of the following reasons:

The string marker was not enclosed in
matching single or double quotes.

The string marker was enclosed in invalid
delimiters.

In a line count definition, a value greater
than 0 was not specified.

Use any valid function or command.

Illegal file specification
The file specification in an OPEN INPUT or
an OPEN OUTPUT command was not a
valid file specification.

Use any valid function or command.

Illegal function

The keypad editor could not recognize the
function specified and could not directly insert the characters typed. The most common
cause is pressing the ESCAPE key and then

almost any other key on the keyboard or the
keypad.

To insert an ESCAPE character or another
character that cannot be inserted directly,
use the SPECINS function. Any valid function or command can also be used.

Illegal right column for wrap
A right margin specified in the SET WRAP
command is greater than 256.

Enter the command again, or use another
function or command.

Illegal tab indent value
An indentation value specified in the SET
TABS command is O or less.

~ Enter the command again, or use another
function or command.

Illegal terminating key
The keypad editor could not complete a FIND
function for one of the following reasons:

The model included an invalid character.

The model was not terminated with the
ADVANCE or the BACKUP function.

Use any valid function or command.

Illegal terminating key to command prompt

The keypad editor could not process a command for one of the following reasons:

174

RT-11 System Message Manual

Use any valid function or command.

° An mvalmd character was includedin the

the ENTERfimctlm |
llegal to insert null

The NULL character (ASCII code 0) was

Use any valid command or function.

specified with the SPECINS function. The

kaypad editor does not allow insertion of
nullsin any file.

me a fil@ was bmnginspected

Use any valid function or command.

ade to mmplaw functmm and comodify the file.
iliary input file

The last INCLUDE command copied the last
character of the auxiliary input file to the
main file. The keypad editor closed the auxiliary input file.

Use another function or command.

The processing of a LOCAL command was
stopped by CTRL/C, or the keypad editor
muld not finish processing for some other

Tha kaypad mhtar wuld mtinsert th

cter

typed because theoutput file is not

large mcmgh

If the file is full, exit and start a new session,
delete and make room for insertions, or use
an auxiliary output file. The CLOSE or the
QUIT mmmand or any functions or com-

:’M% material from the file can

While a file was being inspected, an attempt

was made to complete functions and commands that would modify the file.

Um any valid function or command.

Invalid pammawr to ADJUST
ment outside the range of -50 to +50 was

Invalid parameter to LOCAL

In the LOCAL command, a starting value or
increment of 0 or greater than 32767 was

Enter the command again, or use another

command or function.

Enter the command again, or use another
command or function.
|

Learn buffer filled

The functions and commands used after the
LEARN command require too many bytes for
the learn buffer. The keypad editor immediately stops storing the macro and deletes the
contents of the learn buffer.

Make sure that unnecessary ADVANCE or
BACKUP functions are not being used in the

macro.

Use

abbreviations for commands

within the macro, and use the shortest possible search models within the model.

LOCAL illegal during inspect

The LOCAL command was entered while a

Use another command or function.

file was being inspected.

Local symbol definition too long

In processing a LOCAL command, the
keypad editor detected a local symbol that is

Make sure that the local symbol is correct.

more than six digits long.

Logic error in ADJUST

Logic error in CHNGCASE

Logic error
in CUT
Logic error in FILL

Logic error in PASTE

Logic error in SUBSTITUTE
Logic error in undelete
Logic error in undelete setup

Logic error in WRITE SELECT

The keypad editor may have malfunctioned.

Try the operation again. If the error persists,
submit an SPR to DIGITAL,; include with the

SPR a program listing and a machine-readable source program, if possible.

Move failure in local

The processing of a LOCAL command was
stopped by pressing CTRL/C, or the keypad
editor could not finish processing the command for some other reason.

Move PAGE or SECTION finds extremity of file
A PAGE or a SECTION function moved the
cursor to the top or the bottom of the file.

Use any valid function or command.

Move to bottom when at bottom

The BOTTOM function is not valid when the

Use any valid function or command.

cursor is at the bottom of the file.

Move to top when at top

The TOP function is not valid when the
cursor is at the top of the file.

176

RT-11 System Message Manual

Use any valid function or command.

No macro to execute

| The macro buffer is empty elt;lmr )ecause

LEARNcommand was not used to stor

Use the LEARN command to store the macro
that you want to use.

macro or because the last macro attempte

be stored failed while it was being defimd
No model defined

The keypad editor could not process the
FINDNEXT REPLACE or SUBSTITUTE

To search for a string, use the FIND function,
type a model of the string the keypad editor
is to mmh for, and then specify the direction
.

mth

the

ADVANCE

the

aAnycthm* vahd function

No select range defined

An attempt was made to use the REPLACE,
APPEND, or CUT function without previously defining a select range and locating the

Use any valid function or command.

cursor at a search target.

No select range define for FILL

No characters were in a select range, or a

select range was not being built when the
FILL function or command was used.

~ Before using the FILL command or function,
~ build a select range that contains the segment of the file that is to be reformatted.

No select range for ADJUST

A select range is not being built, or no characters are in the select range that is being

built.

Nfl select range for WRITE SELECT
The SELECT function was used and then the

WRITE SELECT command was entered.
However, no characters are in the select
range that is being built.

Not enough file space to do PASTE
The keypad editor could not complete the
PASTE function because the output file is
not large enough for the material thatis in

the paste buffer. The cursor is lmmmd to the
right of the last character the keypad editor
copied from the paste buffer.

Before using the TABS ADJUST command,

build a select range that includes the
seg-

ment of the file thatis to be adjusted.

Build a select range that includes the mate-

rial that is to be copied to the auxiliary

output file, and then enter the

WRIT E SE-

LECT command.

Exit and start a new session, delete and
make room for insertions, or use an auxiliary
output file. The EXIT or the QUIT command
or any fun tions or commands that delete
material from the file can also be used. If the
EXIT or tm_ QUIT command is used, the
- keypad editor pr eserves the material in the
paste buffer for the next session until the
keypad editor is completely stopped and returns to the system level.

RT-11 System Message Manual

177

Not enough space to undelete
The keypad editor could not complete an UNDELLINE, UNDELWORD, or UNDELCHAR function because the output file is not
large enough for the added material. The
cursor is located to the right of the last character the keypad editor copied.

Exit and start a new session, delete and
make room for insertions, or use an auxiliary
output file.

Nothing to undelete

The keypad editor could not process an UNDELLINE, UNDELWORD, or UNDELCHAR function because the corresponding
line, word, or character buffer is empty.

Use any valid function or command.

OPENLINE finds file full

The keypad editor could not process the
OPENLINE function because the output file
is too small for a Carriage-Return/Linefeed
pair.

Exit and start a new session, delete and
make room for insertions, or use an auxiliary
output file.
|

OPENLINE illegal during inspect

While a file was being inspected, an attempt
was made to complete functions and commands that would modify the file.

Use any valid function or command.

PASTE is illegal during inspect
While a file was being inspected, an attempt
was made to complete functions and commands that would modify the file.

Use any valid function or command.

REPLACE is illegal during inspect
While a file was being inspected, an attempt
was made to complete functions and commands that would modify the file.

Use any valid function or command.

Search canceled
The keypad editor loads this message when

CTRL/C or CTRL/Z is typed to cancel the
FIND function and Model : prompt.

Use any valid function or command.

Select range too large to CUT
The keypad editor cannot complete a CUT or
an APPEND function because the paste
buffer is too small for all of the material you
want to store in the buffer.

178

RT-11 System Message Manual

Either process the selection as smaller select
ranges or use auxiliary files for the same
purpose as the CUT, APPEND, and PASTE

functions. For example, write the selection
temporarily to an auxiliary output file and
close it, delete the selection, move the cursor
to where you want the selection to be, and
copy the material from the temporary file as
auxiliary input file. Any other valid function
or command can also be used.

TAB Indent value wrong for align

With the A function, the column number of
the cursor’s position is not evenly divisible by

the current setting for the indentation.

Make sure that the cursor’s position and the
indent setting are both correct. To align the
structured tab feature, use the A function
again.

Tabs not enabled for ADJUST

The TABS ADJUST command was used before the SET TABS command was used.

Enable structured tabs with the SET TABS
command before using the TABS ADJUST
command.

Target not found

A FIND or a FINDNEXT function moved the
cursor to the top or the bottom of the file
without finding a string that matches the

Use any valid function or command.

model specified.

Too many arguments for command
The keypad editor did not recognize a com-

mand because extra characters were added
on the command line after the last valid word

Use any valid function or command.

or argument in the command.

Unable to access auxiliary device
The keypad editor could not access the auxiliary device for one of the following reasons:
e The device is invalid.
e The device is not ready.

e The device is not installed.

e The volume has too many bad blocks.

e No room is available for the device handler.

Unable to close auxiliary file
The keypad editor could not close the auxiliary output file. The output device may

have caused the problem, and the keypad ed- itor may have malfunctioned.

Check the device abbreviation. If it is correct,
make sure that the device is on line. Use the
SHOW/DEVICES command to see which devices your system includes, and use the INSTALL command to install the device you
need, if necessary. If the message persists,
use the DIRECTORY/BADBLOCKS command to check the volume being used for bad
blocks; if many bad blocks are on the volume,
use another copy. If the handler for the device to be used cannot be installed, switch to
a system that provides more memory resources or to a smaller RT-11 monitor. Refer
to Section 3.0 for information on how to increase memory resources. If the error still
persists, submit an SPR to DIGITAL; include
with the SPR a program listing and a machine-readable source program, if possible.

Make sure that the output device is on line.
Check the device abbreviation. If it is correct,
make sure that the device is on line. Use the
SHOW/DEVICES command to see which devices your system includes, and use the INSTALL command to install the device you
need, if necessary. If the message persists,

RT-11 System Message Manual

179

use

the DIRECTORY/BADBLOCKS command to check the volume being used for bad
blocks; if many bad blocks are on the volume,
use another copy. If the handler for the device to be used cannot be installed, switch to
a system that provides more memory resources or to a smaller RT-11 monitor. Refer
to Section 3.0 for information on how to increase memory resources. If the error still

persists, submit an SPR to DIGITAL; include

with the SPR a program listing and a machine-readable source program, if possible.

Unable to delete local symbol marker

Unable to delete target

Unable to insert tab
The keypad editor may have malfunctioned.

Try the operation again. If the error persists,
submit an SPR to DIGITAL; include with the

SPR a program listing and a machine-readable source program, if possible.

Unable to open auxiliary input file

The keypad editor could not open the aux-

Check the file specification. If it is correct,

iliary input file for one of the following rea-

make sure that the correct volume is in-

sons:

stalled and that the auxiliary input device is

The volume does not contain the file.

The volume is not initialized.

The device is not ready.

on line.

Unable to open auxiliary output file
The keypad editor could not open the auxiliary output file for one of the following reasons:
e

The volume is not initialized.

The device is not ready.

The device is write-locked.

Make sure that the auxiliary output volume
has been initialized. Also make sure that the
auxiliary input device is on line and is write-

enabled.

Unable to replace symbol

The keypad editor may have malfunctioned.

Try the operation again. If the error persists,
submit an SPR to DIGITAL; include with the
SPR a program listing and a machine-readable source program, if possible.

180

RT-11 System Message Manual

—

Undelete buffer full

The keypad editor could not finish processing
a DELLINE or a DELWORD function for one
of the following reasons:

e DELLINE would have deleted more than
132 characters, the capacity of the line
buffer.

To delete strings larger than the line and
word buffers can hold, use repeated DELLINE or DELWORD functions and ignore the
error signal, or use the paste buffer or auxiliary files. Any other valid function or command can also be used.

e DELWORD would have deleted more than
80 characters, the capacity of the word
buffer.

Undeletes are illegal during inspect
While a file was being inspected, an attempt
was made to complete functions and commands that would modify the file.

Use any valid function or command.

Valid start of LSB not found

No global symbol or .ENABL LSB directive
exists between the cursor’s position and the
preceding Formfeed character or the top of

Verify that the cursor is located in the first
page of an LSB before using the LOCAL command.

the file.

WRITE finds end of file

The last WRITE command copied the last
character of the main file to the auxiliary

Use any valid command or function.

output file.

Command:

~ The keypad editor displays this prompt after
the COMMAND

function is used.

Type a keypad editor command and terminate the command with the ENTER function.

Model:

The keypad editor displays this prompt after

the FIND function is used.

Type the string that the keypad editor is to
search for and then specify the direction of
search with the ADVANCE or the BACKUP
function. Models from 1 to 46 characters long
can be specified.

Repeat:

The keypad editor displays this message
when the GOLD key is pressed. The message
appears when the sequence to repeat a function is used and when the SPECINS function
is used to insert a character that cannot be

This message is primarily informational. It is
also a warning that the special effects of repeated functions and the SPECINS function
are enabled.

inserted directly.

RT-11 System Message Manual

181

WORKING. ..

When a process takes longer than normal,
the keypad editor flashes this message at the
top of the terminal screen until the process is
complete. Several interrelated factors, such
as the length of the file edited, the devices
used, and the functions used, determine

This message is informational.

when the WORKING, .+ . message appears.

9.3

Single-Line Editor Messages

This section lists the messages that can be displayed by the RT-11 system
single-line editor. The single-line editor error messages appear in the
center of the bottom screen line of your video terminal. If you cannot determine the location of your error by reading the explanation for the message
in this section, see the RT—-11 System User’s Guide for a description of the
single-line editor.
At left margin now

An attempt was made to move or delete to
the left when the cursor is at the left margin.

Enter a command that moves or deletes to
the right.

At right margin now

An attempt was made to move or delete to
the right when the cursor is at the right

Enter a command that moves or deletes to
the left.

margin.

Invalid control character

The control character typed is invalid when
the single-line editor is used.

Use only the control characters that are valid
for the single-line editor. Refer to the RT-11

System User’s Guide for valid control characters.

Invalid key

The key used is invalid when the single-line
editor is used.

Use only the keys that are valid for the

single-line editor. Refer to the RT—-11 System
User’s Guide for valid keys.

No previous line

The uparrow ( 1) key was used to get the previous line when no previous line exists.

Use any valid function or command.

No room to insert

Not enough room is available to insert text
on the line the cursor is on.

182

RT-11 System Message Manual

Either delete text from the line and then insert the new text, or advance to the next line.

Nothing to undelete

An attempt was made to undelete text when
no text had been deleted.

Use any valid function or command.

Unsupported command

The command entered is not supported under
the single-line editor.

Use only the commands that are supported.
Refer to the RT-11 System User’s Guide for
the supported commands.

RT-11 System Message Manual

183

HOW TO ORDER
ADDITIONAL DOCUMENTATION
From

Call

Chicago

312-640-5612

Digital Equipment Corporation

8:15 Am. 10 5:00 PM. CT

Accessories & Supplies Center

Write

1050 East Remington Road
Schaumburg, IL 60195

San Francisco
Alaska, Hawaii

408-734-4915

Digital Equipment Corporation

8:15AM. to 5:00pPM. PT

Accessories & Supplies Center

603-884—-6660

632 Caribbean Drive
Sunnyvale, CA 94086

8:30 AM. t0 6:00 PM. ET
or

408-734-4915
8:15 am. t0 5:00 pm. PT

New Hampshire

Rest of U.S.A.,
Puerto Rico*

6038846660

Digital Equipment Corporation

8:30 AM. t0 6:00 PM. ET

Accessories & Supplies Center

1-800-258-1710
8:30 AM. 10 6:00 PM. ET

P.O. Box CS2008
Nashua, NH 03061

*Prepaid orders from Puerto Rico must be placed with the local DIGITAL subsidiary (call 809-754-7575)

Canada
British Columbia
|

Ottawa—Hull
Elsewhere

1-800-267-6146
8:00 aM. to 5:00 pm. ET

613-234-7726

8:00 Am.t0 5:00 PM. ET

Digital Equipment of Canada Ltd
940 Belfast Road
Ottawa, Ontario K1G 4C2

Attn: A&SG Business Manager

112-800-267-6146
8:00 Am. to 5:00 PM. ET

Elsewhere

Digital Equipment Corporation
A&SG Business Manager”
*c/o DIGITAL's local subsidiary or approved distributor

Wity

RT-11 System
Message Manual
AD-5284D-T1

READER’S COMMENTS

NOTE: This form is for document comments only. DIGITAL will use comments submitted on this form at the
company’s discretion. If you require a written reply and are eligible to receive one under Software
Performance Report (SPR) service, submit your comments on an SPR form.

Did you find this manual understandable, usable, and well organized? Please make suggestions for improvement.

Did you find errors in this manual? If so, specify the error and the page number.

Please indicate the type of user/reader that you most nearly represent.

—

Assembly language programmer
Higher-level language programmer

—

Student programmer

—

Other (please specify)

—

— Occasional programmer (experienced)
__ User with little programming experience

Name

Date

Organization

Telephone

Street

City

State

Zip Code
or Country

Do Not Tear — Fold Here and Tape

Wm%mmmmmmmmm

No Postage
Necessary
if Mailed in the

United States

BUSINESS REPLY MAIL
FIRST CLASS PERMIT NO.33 MAYNARD MASS.

POSTAGE WILL BE PAID BY ADDRESSEE

SSG/ML PUBLICATIONS, MLO5-5/E45

DIGITAL EQUIPMENT CORPORATION
146 MAIN STREET
MAYNARD, MA 01754-2571

——

—————

SORESSES

w——

————

GRRNIOE

GRS

————.

GRS

——————

shese

SGRSIEE

sdMeeN

sussRaite

memWONE

—-————

comeswss

Cut Along Dotted Line

A————

A———"

—

Do Not Tear — Fold Here

RIS

GRNING

djilglilt/a

”*—-mmm”mm—n—_fimm_—mwm-—mm“

mmwwmwm

—