Fujitsu MAT3300FC User Manual
Command Processing
2-6
C141-C008
e. Bit 0 (Link)
This IDD does not support Link, so this bit should be set on “0”.
(6) Handling an illegal CDB
If there are errors in the contents of a CDB description (specification), or if there
is an error in the specification of a parameter transferred from the INIT in
accordance with a CDB specification, that command ends with the CHECK
CONDITION status. In the case of a command that changes data on the disk
medium, when there is an error in the CDB specification, the disk medium is not
changed by that command, but when there is an error in a parameter transferred in
a DATA frame, the contents of the disk medium in the area specified in that
command may be changed. Also, a DATA frame request may be executed after
receiving a DATA frame, but those data are not used.
is an error in the specification of a parameter transferred from the INIT in
accordance with a CDB specification, that command ends with the CHECK
CONDITION status. In the case of a command that changes data on the disk
medium, when there is an error in the CDB specification, the disk medium is not
changed by that command, but when there is an error in a parameter transferred in
a DATA frame, the contents of the disk medium in the area specified in that
command may be changed. Also, a DATA frame request may be executed after
receiving a DATA frame, but those data are not used.
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.
shown in Table 2.6.
The status byte is 1 byte of information in the STATUS 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 SET, ABTS, CLEAR TASK SET, TARGET RESET, LIP (XY)
or FC LOOP, if the command is cleared, the status byte for that command is not
reported.
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 SET, ABTS, CLEAR TASK SET, TARGET RESET, LIP (XY)
or FC LOOP, if the command is cleared, the status byte for that command is not
reported.
Table 2.6 Status
Status code
Status
00h GOOD
Status
02h
CHECK CONDITION Status
04h
CONDITION MET Status
08h BUSY
Status
10h INTERMEDIATE
Status
14h
INTERMEDIATE CONDITION MET Status
18h
RESERVATION CONFLICT Status
22h
COMMAND TERMINATED Status
28h
TASK SET FULL Status