Next: Index
Previous: exaEdit Synopsis
Up: The Editor exaEdit
The exaEdit Messages
Here you will find, in alphabetical order, most of the messages
exaEdit can generate. Beneath every message, there are one or
more links to the pages that describe the message.
The exaEdit commands are presented in capital letters.
1 file loaded
... files loaded
... subdirectories skipped
1 subdirectory skipped
... times changed
A directory cannot be edited
access errno = ...
Access not allowed
ATTENTION: Data not saved!
Begin column larger than end column
This error message can occur with many exaEdit commands, but is
described only here:
If a command needs a parameter which restricts the affected columns, the
left column number has to given prior to the right one. Reversing
this leads to the given error message. Mind that the column parameters
may be parameter variables.
Begin of data
This error message can occur with many exaEdit commands, but is
described only here:
A exaEdit positioning command demands that the current line is
positioned before the first line of the workfile.
In contrast to searching (see the description of RLOCATE), it is not possible
for positioning commands to continue with the last line after stepping over
the first line of the workfile.
Bus error
Cancelled at recursive X
Cancelled at recursive Y
Case-insensitive
Case-sensitive
Changes not saved
Character string in all records: ...
Character string not found: ...
Character string too long
This error message can occur with many exaEdit commands, but is
described only here:
If a exaEdit command needs a string for a parameter, the programming
language reserves a certain amount of memory for that string. If the
string is too long to be contained in that memory, the programming
language generates an error. This results in the exaEdit message
string too long. Since the amount of memory maximally available is
large enough, this does not restrict working with exaEdit.
CODEPAGE is only for Windows systems
Command in error: ...
compress #...
Compressed n times in m records by k blanks
Curses: ..., Characters: ..., Escape: ..., Function: ...
Data saved
Data set may be read only
Data set not opened (does not exist?)
Directory not found
Directory not opened
DOS
End of data
This error message can occur with many exaEdit commands, but is
described only here:
This error message has two possible reasons:
One would be a exaEdit positioning command like DOWN that demands the
current line to be positioned past the last line of the workfile.
In contrast to searching (see the description of LOCATE), it is not possible
for positioning commands to continue with the first line after stepping over
the last line of the workfile.
The second possible reason would be a command that tries to obtain data from
behind the last line of the workfile during its execution. This could, for
example, happen when you use the command CHANGE together with the parameter
n.
End process
Ending ' missing
Enter J or Y to stop:
EOF
Escape-sequences instead of keys: ...
n. EXEC line longer than window width ...
Expanded n times in m records by k blanks
External command ended
F-key is not defined
F-key now defined
File not found)
File not found
File system may be read only
First number larger than second
getcwd errno = ...
'I' will be ignored as H is specified
Illegal instruction
Input
Mixed (lower): without translation to capital letters
n. EXEC line longer than window width ...
New data set, press J or Y to create it:
No connection to another computer
No file and no directory
No Home-directory found for ...
Number ... not found
Number 0 not allowed
Number too large
This error message can occur with many exaEdit commands, but is
described only here:
You have used a parameter variable for a string parameter, but the
parameter variable used was defined for (line) numbers, and not for
strings.
Object is no directory
Odd number of hex characters
Old data set, press J or Y to replace it:
Operand missing in: ...
Parameter missing
Parameter variable no character string
This error message can occur with many exaEdit commands, but is
described only here:
You have used a parameter variable for a string parameter, but the
parameter variable used was defined for (line) numbers, and not for
strings.
Parameter variable not defined
This error message can occur with many exaEdit commands, but is
described only here:
Parameter variables that are not included in exaEdit by default have
to be defined via the command & before use.
Parameter variable not numerical
This error message can occur with many exaEdit commands, but is
described only here:
You have used a parameter variable for a number parameter (column,
line, etc.), but the used parameter variable was defined for a character
string and not for numbers.
Part of the name is no directory
exaEdit in line mode
exaEdit: Bus error
exaEdit: End process
exaEdit: Escape-sequences instead of keys: ...
exaEdit: External command ended
exaEdit: Illegal instruction
exaEdit: Press Enter, when you have seen everything
exaEdit: Segmentation fault
Press Enter, when you have seen everything
Press J or Y to stop:
Press key:
Records counted: ..., size of workfile: ...
REKEY produces too large number
Renumbered
Search from begin (wrap)
Search from end (wrap)
Segmentation fault
SEQUENCE exceeds 99999999 or field width
SET storage changed, return to previous record
SET storage invalid
This error message can occur with many exaEdit commands, but is
described only here:
You have used the symbolic line number s with a command such as COPY.
s refers to the record that has been marked with the command SET.
The command SET has been used in the current workfile, but the
record it referred to has been deleted in the meantime. As a
consequence, the symbolic line number s cannot be used any more.
Note that some commands create the message SET storage changed,
return to previous record instead.
SET storage unused
This error message can occur with many exaEdit commands, but is
described only here:
You have used the symolic line number s in a command, e.g. COPY.
s refers to the record that has been marked via the SET
command. But this command has either not yet been given in the current
workfile or the complete content of the workfile has been
deleted in the meantime. Due to that, s is not defined, so you
receive an error message. The command RETURN can produce the same
error message.
Sorry, I don't know how to deal with your '...' terminal.
Sorry, I need to know a more specific terminal type than ''.
Sort fields overlap
Sorted
Source and target area overlap
stat errno = ...
Target in COPY area
Target in MOVE area
Target record not found
TERM not defined
Terminaltype is ...
There is no column 0
This error message can occur with many exaEdit commands, but is
described only here:
Some exaEdit commands need a column specification for a parameter.
The columns are counted from number 1 onwards, a column with the
number 0 is not allowed. Mind that a parameter variable also can have
the value 0 and thus result in the given error message.
There is no next record
This error message can occur with many exaEdit commands, but is
described only here:
You have used the symbolic line number n with a command,
e.g. MOVE. n refers to the record following the current record,
but since the current line is the last line of the workfile, there
is no next record.
There is no previous record
This error message can occur with many exaEdit commands, but is
described only here:
You have used the symbolic line number p with a command, e.g. COUNT.
p refers to the line prior to the current one, but since the current
line is the first line of the workfile, there is no previous record.
There is no such command
... times changed
Too many symbolic links, refer to itself?
TOP
Translation to lower case
Translation to upper case
Upper: with translation to capital letters (no German umlauts)
WIN
Workfile not found
Workfiles not saved: ...
Wrong hex character
Wrong parameter
X is not defined
exaEdit.dmp [not] opened
exaEdit.dmp closed
exaEdit.jjjj.mm.tt-hh.mm.ss.wfn.dsn [not] opened
Y is not defined
You cannot ... the top line
... can be replaced with: change, concatenate,
delete, move or sort.
This error message can occur with many exaEdit commands, but is
described only here:
The execution of the command you have given would concern the top
line, while it is not possible for the given command to work with the
top line, e.g. copy t 500. This can often be corrected by
replacing the symbolic line number t, which denotes the top
line, with the symbolic line number f, which denotes the first
line.
Next: Index
Previous: exaEdit Synopsis
Up: The Editor exaEdit