Specifications
TEXT
EDITOR
Using its own two files (work file and user file),
text
editor
can build files or
alter
any
job
processor files. The editor
can
operate
on any file
read
into
its
own file
sp~ce.
The
following diagnostic messages can appear
durmg those
commands shown:
Message Significance/Command
DISK
READ
ERROR The work file and
scratch
file
are
kept
on disk; each line is read as a
separate
record. A disk read or write
error
may occur during any read
operation.
Commands:
Any
DIRECTORY READ The
parameter
fileid cannot be
ERROR obtained while reading
the
job
processor directory.
Commands: GET, MERGE,
SAVE
FILE
NOT
DEFINED The
parameter
fileid is not in
the
job
processor direC!tory.
Commands: GET, MERGE,
SAVE
FILE SPACE FULL The file manager has run out
or
spaC!e
to
assign
to
its
text
editor (work
rile
or
user file).
Commands: Any
exC!ept
EXIT,
CLEAR,CONTROL
INVALID
COMMAND
The necessary charaC!ters
at
the
be-
ginning
of
the command
mnemoniC!
are
erroneous, or a necessary
param-
eter
is
omitted
or
wrong (e.g.,
k
2
<k
1
)·
INVALID
LINE
NUMBER
• 5-18
Commands:
Any
The line number
parameter
(k
or
n)
is
greater
than 9999.
Commands:
Any
but EXIT, CLEAR,
CONTROL,
SAVE,
ALIGN
Message
LINE
NUMBER
OVERFLOW
Significance
Line number >9999. For all but
RESEQ, the
text
editor saves in the
work file all
data
up
to the line
causing the overflow. For
RESEQ,
the work file is lost.
Commands: LOAD,
MERGE,
GET,
AUTO, RESEQ
NAME
NOT
UNIQUE
The operator specified only the first
letter
of the command mnemonic
(A,C,D,L,
or
S).
At
least
the
first
two
letters
of
these commands must
be
speC!ified.
Commands: AUTO,
ALIGN,
CHANGE, CLEAR,
CONTRL,
DE-
!rTE,
DUMr,
LIST, LOAD.
SAVE.
SEARCW- - - -
RPG
II
Numerous diagnostiC! messages
are
provided
by
the report
program
generator
(RPG
II):
Compilation errors:
• Control
C!ard
diagnostics
• Extention
<!Ode
diagnostiC!S
•
CalC!u1ation
diagnostiC!S
• Output
format
speC!ification diagnostics
• Compile time
array
diagnostics
Run
time
errors
Data
manager
errors
Disk file utility
errors
There
are
several hundred
of
these messages
that
are
very
closely tied
to
the source language format
of
RPG
II.
The
messages
are
listed in detail in the RPG
II
reference
manual,
appendix
E.
96769450 B