Specifications
Message
ENGINEERING FILE
INFORMATION LISTING
LOGICAL UNIT
xx
name
DATE
TIME
aa
hhmm:ss
F
AlLURE CODE
bb
HARDWARE
STATUS
cc
Significance
error
code as shown in
section
6;
T is
the
time,
and zzzz is
the
status
word.
1.
In
response
to
MI,
then
EF: all failure codes
for
all
logic units
2.
In
response
to
MI,
then
EFLU:
the
failure
codes for
the
logic units
specified
3.
In
response
to
MI,
then
EFMM:
the
failure
codes for
the
core
resi-
dent
mass memory
fail-
ure table
Note
that
the
log for
each
logic unit is a wrap around.
The
operator
should inspect the
date
and
time
to
find
the
entry
for
the
logic unit most likely
to
reflect
the
particular
error
he is investigating.
OOEBUG
The on-line debug program (ODEBUG) allows
the
pro-
grammer
to
access
both
protected
and
unprotected
main
memory and mass
storage.
Both kinds
of
storage
may be
searched,
altered,
dumped, or moved. Main memory may be
allocated;
main memory and mass memory may be
com-
pared, threads may be
traced,
and magnetic
tape
transport
control
is available. Commands
executed
by ODEBUG
are
described
in
the
MSOS
reference
manual.
The messages
are:
Message
CELL
CONTENT
DEBUG
IN
DEBUG
OUT
DB
FORMAT
INVALID
DB
I/O ERROR
DB
ILLEGAL
LU
96769450
B
Significance
Shows
the
cell
content
in
hexadecimal
ODEBUG is
ready
for
the
first
command.
ODEBUG has
exited
from
the
system.
The
parameter
list
for
the
request
is invalid.
Input/output
failure during
processing
No
such logic unit in
the
LOG
tables
Message
DB
ILLEGAL
MM
ADD
DB
INVALID
REQUEST
DB
NO
CORE AVAIL-
ABLE
Significance
No
such
sector
address on
mass
storage
No
such
DEBUG
mnemonic
for command
Insufficient
core
to
load
ODEBUG
DB
ORDINAL LENGTH 0
No
program is
associated
with this ordinal (identifier)
in
the
system library.
DB
ORDIN
AL
OVER
This ordinal is
greater
than
MAX
the
largest
ordinal assigned
in
the
system library.
DB
SEARCH FINISHED All
searched
cells containing
the
specified value
are
list-
ed following
the
CELL
CONTENT message.
NEXT
BREAKPOINT
ODEBUG is ready for
the
next
command.
This background package allows
the
programmer
to
check
out
a program by use
of
conditional stops (breakpoints).
When the specified condition occurs and
the
program stops,
the
operator
may
alter
core
or
registers,
dump
core
as
registers, change
the
logic units, jump
or
resume processing,
or dump mass
storage.
Magnetic
tape
control
commands
are
also available. Commands
executed
by
breakpoint
are
described in the
MSOS
reference
manual. The messages
are:
Message
xxxx
FORMAT ERROR
xxxx
PROTECT ERROR
TOO
MANY
BREAK-
POINTS
xxxx
FORMAT ERROR
Significance
The
parameter
list
field I
specified for this breakpoint
command is
in
error.
The breakpoint specified I
does not lie
wi
thin unpro-
tected
core.
Only
15
active
breakpoints
are
allowed; xxxx is
the
location
of
the 16th
break-
I
point specified
in
the
SET
breakpoints command.
Alternate
forms
of
the
messages
are:
B01,
statement
Statement
or
parameters
are
unintelligible for
the
breakpoint
program~
4-15