Table
4.
Automatic
Mode
Stacking
Action
Order
Stacking
Action
t
X'06'
X'16'
X'36'
X'OE'
X'lE'
X'3E'
Model 7120
Stack
card in normal
stacker.
Stack
card
in
alternate
stacker
1.
Stack
card
in
alternate
stacker
2.
If
no
validity
error
or
data
overrun occurs,
stack
card in normal
stacker;
if
validity
error or
data
overrun occurs,
stack
card in
alternate
stacker
2.
If
no
validity
error or
data
overrun occurs,
stack
card in
alternate
stacker
1; if
validity
error
or
data
overrun occurs,
stack
card in
alternate
stacker
2.
Stack
card
in
alternate
stacker
2.
Model 7140
Stack
card in normal
stacker.
Stack
card
in
alternate
stacker.
Stack
card
in normal
stacker.
If
neither
validity,
data
overrun,
nor read
verify
error
occurs,
stack
card in normal
stacker;
if
error occurs, stack
card
in
alter-
nate
stacker.
Stack
card in
alternate
stacker.
Same as 'OE'.
tModels
7121/7122
accept
all the
above
order
codes
but
offer no
alternative
stacking
since
they
have
only
one
stacker.
READ
CARD
AUTOMATIC
The orders (hexadecimal code) listed in
Table
4 cause
the
card
reader
to feed
and
read a card in
the
automatic
mode,
with the card
being
directed
to
one
of
the
multiple
stackers.
To
facilitate
reading
of
intermixed
EBCDIC
and
binary
card
decks,
card column 1
is
sensed for
the
presence
of
punches
in rows 1 and
2;
if
both
are
present,
the
read
operation
is
automatically
forced to
the
binary
read mode and
all
data,
including
column 1,
is
transmitted as
described
previously
under
"B
inary Card
Format".
In
the
EBCDIC
card format, 80 bytes
are
present on a
card.
Incorrect
length will be
signaled
if
either
fewer or more
than
80 bytes
are
requested for
an
EBCDIC
card.
However,
if
the
binary
read mode
is
invoked
automatically,
incorrect
length will
be
signaled
if
either
fewer
or
more than
120
bytes
are
requested.
KEY
EVENTS
The key
events
that
occur
during a card read
operation
are
described
in
the
following paragraphs.
No
chronological
order
should
be
assumed from
the
order
of
presentation.
Timing information is discussed
under
"Programming
Considerations"
•
START
INPUT/OUTPUT
A card read
operation
is
initiated
with
the
execution
of
a
START
INPUT/OUTPUT instruction by
the
controlling
sys-
tem.
If
I/O
address
recognition
exists
and
the
reader
is
in
the
"ready"
condition
with
no
interrupt pending,
the
con-
trolling system sets its
"I/O
address
recognition"
and
"510
6 Key Events
accepted"
indicators.
The card
reader
advances
from
the
"ready"
to
the
"busy"
condition
and,
if
the
reader
is
in
the
"automatic"
mode,
it
requests an
order
byte
from
the
con-
trolling
system.
Note
that
"510
accepted"
does not mean
that
the card
reader
has
started
to feed
and
read a
card.
"510
accepted"
signifies only
that
a
device
has
accepted
the
510 instruction
and
the
device
was in
the
"ready"
con-
dition
with
no
interrupt
pending.
UNUSUAL
END
CONDITIONS
The
detection
of
any
of
the
following during the "busy"
con-
dition
causes the
card
reader
to
return
an
"unusual
end"
indi-
cation
to
the
controlling
system
at
the
time
the
condition
occurs:
1.
Invalid
order
code
2.
Read
station
malfunction
3. Transport mechanism malfunction
4. Absence (or
failure)
of
ac
and/or
dc
power in
reader
5.
Operator
pressing
the
RESET
switch
6.
The
occurrence
of
a
data
overrun
7.
lOP
Halt
(not
applicable
to Sigma 2)
CHANNEL
END
CONDITIONS
After
receiving
an
order
from the control I ing system,
the
card
reader
signals
"channel
end"
to the
controlling
system
when
the
end of
the
card
is
encountered
or
an
"unusual
end"
condition
occurs,
whichever
occurs first.
To Next Page
Loading...
