Specifications
Device Failure
Code and Error
7 Compare
Pre-read
8 megal Hol-
lerith punch
9 Sequence
10
Non-negative
record length
11
Read/write
mode
change
96769450
A
Significance
Hardware problem: A compare error
occurs
when
a faulty signal is de-
tected
in the area of the punch
solenoid and echo amplifier circuits
during an echo check.
1728-430 Card Reader: Remove and
discard the last card punched. Ready
the device and type
RP.
Card readers: Attempt recovery as
for the card checksum error (see
error code
4).
A pre-read error occurs if all read
amplifiers are not off during a dark
check.
1728-430 Card Reader: Remove and
discard the last card punched. Ready
the device and type
RP.
Card readers: Attempt recovery as
for· the card checksum error (see
error code
4).
Occurs
when
the card reader en-
counters a punch sequence that does
not comply with the Hollerith to
ASCII
conversion table being used
by
the driver.
To
allow software recovery, the
driver places an ASCII?
in
the buffer
word for the bad column. Select the
repeat option
to
continue, or abort
the job and correct the mispunched
cards.
Cards within a record are not
in
sequential order. Abort the read
operation and restore the sequential
order
to
the record.
The first
word
of a formatted binary
record is the complement of the
number of records within the record.
The
word
may
be
a negative number
indicating that the card read
was
not
the first card of the record.
Attempt recovery using the proce-
dure for the checksum error (see
error code
4).
Indicates a switch from read or write
mode
1728-430 Card Reader: This message
is issued
only
as a warning to the
operator.
If
mode
switch is allowable, repeat
the request using the
RP
option.
Device Failure
Code and Error
12
7/9
punch
13
·Controller
write
on
device
14
Not ready
15
Noise
record
16
Controller
seek
17
Drive seek
18
Address
Significance
The error occurs
if
a 7/9 punch in
column 1 is read when an
FREAD·
ASCII
request is specified.
Card reader recovery:
•
If
column 1 is a 7/9 punch, there
is
no
recovery; the abort opera-
tion request is the wrong mode.
• If column 1
was
misread, read
the card as for a checksum error.
Magnetic tape: no write ring is
installed.
An
attempt
was
made to write
on
magnetic tape without the write en-
abled.
Insert the write ring and use the
RP
option.
Pseudo tape:
An
attempt
was
made
to write
on
a file
that
was
opened to
read only.
Magnetic tape simulator:
An
attempt
was
made to write with the write ring
not enabled.
See manual input opera-
tions.
1832-5 Cassette Tape: write not
enabled
1833-5 Flexible Disk: The write
enable switch is not
set
or the disk-
ette
has been defined as read only via
a motion request (code
=
5).
Ready the device and use the
RP
option.
1832-4 Magnetic Tape: A noise
record
was
detected and ignored.
The
controller seek error occurs
when
the controller has failed
to
obtain the
file address selected during a read,
write, compare, or checkword opera-
tion. This is usually an indication of
a positioning error.
A drive seek error occurs
when
the
drive unit detects
that
the cylinder
positioner moved beyond the legal
limits of the device during a load
address, write, read, compare, check-
word, check, or write address
function.
This error occurs when an illegal file
address obtained from the computer
is
detected or the controller has
6-3