Input/output interruptions provide a means for the
occur in
be caused by the program or by an external event at
the device.
Interruption Conditions
The conditions causing requests for
to be initiated are called interruption conditions. An
interruption condition can be brought to the attention
of the program only once and is cleared when it causes
an interruption. Alternatively, an interruption con
dition can be cleared by
erated by the
the operation at the subchannel can be cleared by
START
and control-unit-end conditions, and the channel-end
condition when provided by a device on the selector
channel after termination of the operation by HALT
interruption whenever it detects any of the following
conditions:
Channel end
Control unit end
Device end
Attention
When command chaining is specified and is not sup
pressed because of error conditions, channel end and
device end do not cause interruption conditions and
are not made available to the program. Unit-check and
unit-exception conditions cause interruption to be re
quested only when the conditions are detected during
the initiation of a chained command. Once the com
mand has been accepted by the device, unit check
and unit exception do not occur in the absence of
channel end, control unit end, or device end.
When the channel detects any of the following con
ditions, it initiates a request for an
without having received the status byte from the de
vice:
Execution of HALT
The interruption conditions from the channel can be
accompanied by other channel status indications, but
none of the device status bits is on when the channel
initiates the interruption.
A request for an
check condition detected during command chaining
(such as invalid command code, count of zero, or two
sequential transfer-in-channel commands) may be ini
tiated either by the
pending on the type of channel. To stack the inter
ruption condition in the device, as occurs on the
multiplexor channel, the channel signals the device to
respond with a unit-status byte consisting of all zeros
on a subsequent scan for interruption conditions. The
error indication is preserved in the subchannel.
The method of processing a request for interruption
due to equipment malfunctioning, as indicated by the
presence of the channel-control-check and interface
control-check conditions, depends on the model.
More than one interruption condition can be cleared
concurrently. As an example, when the
exists in the subchannel at the termination of an oper
ation, the PCI condition is indicated with channel end
and only one
is not cleared until device end is generated, both con
ditions may be indicated in the csw and cleared at
the device concurrently.
However, at
priority for interruptions to a condition associated with
an operation at the subehannel, the channel accepts
the status from the device and clears the condition at
the device. The interruption condition is subsequently
preserved in the snbchannel. Any subsequent status
generated by the device
dition at the suhchannel, even if the status is generated
before the
Priority of Interruptions
All requests for
the activity in the
sociated with more than one
the same time. The priority among requests is con
trolled by two types of mechanisms -one establishes
the priority among interruption conditions associated
with devices attached to the same channel, and another
establishes priority among requests from different
channels. A channel requests an
after it has established priority among requests from
its devices. The conditions responsible for the requests
are preserved in the dcvices or channels until accepted
by the
associated with devices on anyone channel is a func
tion of the type of interruption condition and the po
sition of the device on the
The selector channel assigns the highest priority to
conditions associated with the portion of the operation
in which the channel is involved. These conditions in
clude channel end, program-controlled interruptions,
errors detected or command chaining, and execution
of HALT