Table of Contents
Advertisement
The IDD terminates abnormally all commands (which are being executed or are
being queued) which it has already received from an overlapping INIT and also
terminates abnormally both the commands that caused the overlap, in the order
described below.
1) If, during execution of a command received from an INIT, the IDD terminates
execution of the command. If the command is still in the queue and has not
yet been executed, the IDD clears that command.
2) The IDD reports the CHECK CONDITION status with for the command that
caused the overlap. The sense data generated by the IDD at this time shows
ABORTED COMMAND [= B]/Overlapped commands attempted [= 4E-00]
or Tagged Overlapped [= 4D-nn] (nn: tag number).
1) The INIT is permitted to sent an ABORT TASK, ABORT
2) Overlapped command specifications are applicable without
2.8.2 Illegal LUN specification
The IDD supports only the logical unit number (LUN) LUN = 0. If a LUN other
than this is specified, the IDD operates in one of the following ways, depending
on the type of command that is issued at that time.
1) For an INQUIRY command, even if an invalid LUN is specified, the
command is executed normally. However, byte 0 of the "Standard INQUIRY
Data" transferred to the INIT by that command (the "Qualifier" field and the
"Device Type Code" field) shows X'7F'.
2) If an invalid LUN is specified for any command other than the INQUIRY
command or the REQUEST SENSE command, that command is executed
normally.
2.8.3 Reserved operation code
Group 6, 7 command operation codes (X'C0' ~ X'FF') are reserved by Fujitsu.
When any command which has these operation codes is issued, the IDD may not
necessarily respond with the CHECK CONDITION status (ILLEGAL REQUEST
[= 5] Invalid command operation code [= 20-00]).
The INIT must not issue commands which have these operation codes.
C141-C009
TASK SET, CLEAR TASK SET, LOGICAL UNIT RESET, or
HARD RESET command, specifying the logical unit in order
to terminate processing of a command that is currently
disconnecting. (Shown in item 2.8.5.)
dependence on the type of command that was issued second.
For example, even if the command that was issued second is an
INQUIRY or REQUEST SENSE command, the IDD reports
the CHECK CONDITION status and terminates both
commands abnormally.
2.8 Command Processing Exceptions
2-15
Advertisement
Table of Contents
