Datasheet

Command Processing
2-28 C141-C008
(4) ABORT TASK SET
This processing is the same as the processing of SCSI equivalent messages, as can
be understood from Table 2.10.
However, this processing is transferred to the IDD by the FCP_CMND frame, and
after processing is completed, notification is made of completion by the
FCP_RSP frame.
The operation sequence is the same as that in Figure 2.6.
For an INIT which wants to clear only specific commands that it has issued,
ABORT TASK SET or ABTS must be used. In this case, if that command is now
being executed on the FC LOOP, the INIT sends ABORT TASK SET at the
desired point. Either that or a tag is specified and ABTS is sent. In the case of
ABORT TASK SET, only commands issued in the past (currently being executed
or in the queue) in the logical unit specified at that time by the INIT which issued
the ABORT TASK SET are cleared, and other commands are not influenced
(however, exercise caution, because this IDD supports only LUN=0).
(5) ABTS
This processing is implemented by Basic Link Service.
If the OX_ID of the exchange you would like to abort is set in the ABTS header
and transferred, if there are no errors in the header information, BA_ACC is sent
as a response and if there are errors, BA_RJT is sent as a response.
Furthermore, ABTS is used to abort not only for SCSI commands but also to
abort Extended Link Service.
When ABTS is received, since only the exchange specified by the ABTS is
cleared, there is no influence on the other commands. Concerning commands
which are cleared by this processing, no RESPONSE is reported.
In particular, if a command to write data to the disk medium which is currently
being executed is cleared, the IDD aborts processing of that command as shown
in Table 2.11. Stopping overlapped commands which are currently being executed
(see 2.7.1) is accomplished by the same treatment. The INIT must investigate the
command completion status, then if necessary, it must implement data recovery
processing.