Specifications
Significance
LOADER
ERROR 3 Out-of-order input block
LOADER
ERROR 4 Illegal
data
or common declara-
tion
LOADER
ERROR 5 Core overflow
LOADER
ERROR 6 Overflow of entry point table
LOADER
ERROR 7 Data block overflow
LOADER
ERROR 8 Duplicate entry point
LOADER
ERROR 9 15/16-bit arithmetic error
LOADER
ERROR
10
Unpatched externals
LOADER
ERROR
11
Insufficient core for both
SYSDAT
and paging
LOADER
ERROR
12
Illegal page number used
LOADER
ERROR
13
Undefined transfer address
LOADER
ERROR 14
Invalid function for loader
LOADER
ER.ROR
15
Link table overflow
LOADER
ERROR
16
External table overflow
LOADER
ERROR
17
Entry point absolutized
to
7FFF
l6
SYSTEM INITIALIZER DISK ERROR
MESSAGES
DISK
ERROl"
DISK
FAILURE
xx
DISK
COMPARE
ERROR SECT
aaaa
WORD
bbbb
IS
cccc
sa
dddd
Significance
The address tag write sequence
was attempted, but an internal/-
external reject was found.
Surface
test
operation caused
error
xx. Refer
to
the
device
error
codes
to
interpret
xx.
Surface
test
pattern
error
on
sector aaaa
at
word bbbb. Only
one error is listed per sector.
Data read
was
cccc but
it
should
be dddd.
SYSTEM INITIALIZER DEVICE
FAILURE CODES
When
the system initializer device detects an input/output
failure, the message is printed:
2-2
L,
nn
FAILED xx (yyyy)
ACTION
Where:
nn
is the initializer logical unit
that
has failed.
xx
is the failure code.
yyyy is the
last
hardware
status
of the failed
device.
The error reponse is one of the two following entries:
RP
To
repeat the request
CU
Abort the operation and return
to
the com-
ment device for a subsequent control
state-
ment.
The .device failure codes for
the
system or initializer driver
follow. The
xx
failure codes
are
defined in section 6. These
failure codes
are
the same for initializer and normal
MSOS
processing.
ERROR RECOVERY
The initializer handles error recovery and flags error
conditions as they occur. Most error conditions
are
immediately recoverable, but
if
an irrecoverable loading
error occurs
in
the loading of a program, the initializer
bypasses the remainder of
the
program and continues loading
the next program.
ERROR
17
appears
on
the comment
device.
The following list identifies some
of
the problems
that
may
cause initializer malfunctions:
Problem
Initializer stops while
loading
the
SYSDAT
program
Initializer stops or
restarts
during loading
Cause
Index I (location FF
16)
is
not assembled in
SYSDAT
as
a
BSS(1).
Locations 0 and
FF
16
usually contain
the
same value, which is
the
address of
the
initializer's
constant table.
The first
*L
control
state-
ment tried
to
load
SYSDAT
into the system library (an
·Y,PROO,l
statement
has
been used). The
SYSDAT
program establishes the
location of the system
directory and therefore
can-
not be placed
in
the direc-
tory. This can be avoided by
changing the first
*y
state-
ment
to
*Y,PROO,2.
Data has been stored over
the initializer or a previ-
ously loaded program link
string
by
an
ORO
instruc-
tion. Locate the
ORO
in-
struction.
96769450 A