Seagate SCSI Interface Product Manual page 62

48 SCSI Interface Product Manual, Rev. J
Contingent Allegiance condition exists. The normal initiator recovery action is to issue the command again at a
later time.
Intermediate or Intermediate–Condition Met—This status shall be returned for every command in a series of
linked commands (except the last command), unless an error, exception, or abnormal condition causes a
Check Condition status, a Reservation Conflict Status, or a Command Terminated Task Set Full or Busy status
to be sent. If this status is not returned, the chain of linked commands is broken; no further commands in the
series are executed.
Reservation Conflict—The status shall be returned whenever an initiator attempts to access a logical unit, an
extent within a logical unit or an element of a logical unit that is reserved with a conflicting reservation type for
another SCSI initiator (see the Reserve, Release, Persistent Reserve Out and Persistent Reserve In com-
mands). The recommended initiator recovery action is to issue the command again at a later time. Removing a
persistent reservation belonging to a failing initiator may require the executive of a Persistent Reserve Out
command with the Preempt or Preempt and Clear actions.
Command Terminated—This status shall be returned whenever the logical unit terminates a task in response
to a Terminate Task task management request (see Task Management Functions). This status also indicates
that an auto contingent allegiance has occurred (see Task Management Functions).
Task Set Full (formerly "Queue Full")—This status shall be implemented if the logical unit supports the cre-
ation of tagged tasks. This status shall be returned when the logical unit receives a command and does not
have enough resources to enter the associated task in the task set.
ACA Active—This status shall be returned when an auto contingent allegiance exists within a task set and an
initiator issues a command for that task set when at least one of the following is true:
a. There is a task with the ACA attribute in the task set;
b. The initiator issuing the command did not cause the ACA condition;
c. The task created to execute the command did not have the ACA attribute and the NACA bit was set to one
in the CDB control byte of the faulting command (see Task Management Functions).
The initiator may reissue the command after the ACA condition has been cleared.