Table of Contents
Advertisement
Command Processing
2.2 Status Byte
The format of the status byte and the types of status which the IDD supports are
shown in Table 2.6.
The status byte is 1 byte of information in the RESP (response) frame which
notifies the INIT from the TARG after a command is completed, and which shows
the results of executing the command. Also, when an Input/Output operation
request has been received, even if the TARG cannot execute the command, the
status byte is reported. However, by forcibly interrupting execution by an
abnormal state such as ABORT TASK, ABORT TASK SET, CLEAR TASK
SET, LOGICAL UNIT RESET, HARD RESET, or SAS PORT, if the command
is cleared, the status byte for that command is not reported.
Status code
00h
02h
04h
08h
10h
14h
18h
22h
28h
(1) GOOD status
This status indicates that execution of the command ended normally.
(2) CHECK CONDITION status
This status is reported in the case of a)~c) below. The IDD generates sense data when
this status is reported and displays the detailed cause. The IDD transfers the generated
sense data together with this status report in the same RESP frame. Therefore, it is
unnecessary to gather sense data using the REQUEST SENSE command.
a) If the sense key in the sense data shows RECOVERED ERROR [= 1], it
shows that the last command, which resulted in the CHECK CONDITION
status, ended normally in conjunction with error recovery processing by the
IDD.
2-6
Table 2.6 Status
Status
GOOD Status
CHECK CONDITION Status
CONDITION MET Status
BUSY Status
INTERMEDIATE Status
INTERMEDIATE CONDITION MET Status
RESERVATION CONFLICT Status
COMMAND TERMINATED Status
TASK SET FULL Status
C141-C009
Advertisement
Table of Contents
