Status When I/O Is
Idle
Attentionc* Status modifier Control-unit end
BusyChannel end
Device endc* Unit check C Unit exception C Program-
controlled
interruption
Incorrect length
Program check
Protection checkChannel-data check
Channel-controlC* check¢ Interface- C* control check Chaining check
Explanation:
AfterWhen or
Subch Upon TerminationRIO or
Is ofOperation at During Work i ng Command with Ctrl I/O Retry or
Device Subch Unit DevChaining C C C C C C C C C* C C C C C C* C C C C When SIO or When SIOF& Is TIO Is
Executed ExecutedS CS CS CS CS CS CS CS CS CS CS S CS CS CS S S CS S 5
SS S
SCS CS S When When When I/O ClRIO Is HIO or Inter
Executed HDV Is ruption
SS 5
SS S
S
S
S
s
S
SCS CS S + Executed Occurs CS CS CS CS CS S S
S
S
S
SCS S
SS S S
SCS CS S C The channel or device can create or present status at the indicated time. A CSW or its status
portion is not necessarily stored at this time.
Status such as channel end or device end is created at the indicated time.Other status bits
may have been created previously but are made accessible to the program only at the indicated
time. Examples of such status bits are program check and channel-data check, which are detec
ted while data is transferred but are made available to the program only with channel end, un
less thePCI flag or an equipment malfunction has cause an interruption condition to be gen
eratedearlier. S The status indication is stored in the CSW at the indicated time.
An"S" appearing alone indicates that the status has been created previously. The letter "C" appearing with the "S" indicates that the status did not necessarily exist previously in the
form that causes the program to be alerted, and may have been created by theI/O instruction
orI/O interruption. For example, an equipment malfunction may be detected during an I/O in
terruption, causing channel-control or interface-control check to be indicated; or a device
such as the IBM3705 may signal temporary control unit busy in response to interrogation by an I/O instruction, causing status modifier, busy, and control-unit end to be indicated in the CSW. * The status generates an interruption condition. Channel end and device end do not result in interruption conditions when command chaining is
specified or command retry is signaled, and no other unusual situations have been detected.
Unit check does not result in an interruption conditionwhen command retry is signaled and is
honored by the channel.Contents of the CSW Status Fields (Part 1 of 2) Chapter 13. Input/Output Operations 13-79
Idle
Attention
Busy
Device end
controlled
interruption
Incorrect length
Program check
Protection check
Channel-control
Explanation:
After
Subch Upon Termination
Is of
Device Subch Unit Dev
Executed Executed
S
S
Executed HDV Is ruption
S
S
S
S
S
s
S
S
S
S
S
S
S
S
portion is not necessarily stored at this time.
Status such as channel end or device end is created at the indicated time.
may have been created previously but are made accessible to the program only at the indicated
time. Examples of such status bits are program check and channel-data check, which are detec
ted while data is transferred but are made available to the program only with channel end, un
less the
erated
An
form that causes the program to be alerted, and may have been created by the
or
terruption, causing channel-control or interface-control check to be indicated; or a device
such as the IBM
specified or command retry is signaled, and no other unusual situations have been detected.
Unit check does not result in an interruption condition
honored by the channel.