4.5Status: STATUS phase (target Æ initiator)
Each time a command is terminated, the target moves into the STATUS phase and returns a status byte to the initiator to report the completion of the command.
Status byte |
|
|
|
|
|
|
|
|
| ||
| 7 | 6 | 5 | 4 | 3 |
| 2 | 1 | 0 | ||
Byte 0 |
|
|
|
| Status byte code |
|
| (Reserved) | |||
|
|
|
|
|
|
|
|
|
|
|
|
The status supported by this scanner are summarized in the following table.
Code | Status of unit |
000000 GOOD
fThe command has successfully terminated. 000001 CHECK CONDITION
a)The command has abnormally terminated.
b)An abnormal condition was detected before a unit is selected.
f The target detected an error before start of command>controlled processing.
f A unit that switched from the NOT READY status to the READY status was selected for the first time.
f A unit that received a RESET CONDITION or a BUS DEVICE RESET message was selected for the first time.
00100 BUSY
A target or logical unit cannot accept a new command.
fThe logical unit is executing processing.
fThe target is executing processing on a specified logical unit or other logical unit.
fThe target intends to report to an other initiator the sense data of a specified logical unit.
fThe target intends to report to an other initiator the sense data of a logical unit that was not specified.
fThe target intends to report the status to any initiator.
01100 RESERVATION CONFLICT
fThe specified unit is already reserved by another initiator.
When a target is released from the BUSY status, it will not issue a notification of the release. Therefore, the initiator needs to check the status of units periodically and needs to issue the command again.
4 $ 88