DT DATA IN Phase Exception Handling

Spalding, AlanC Alan_Spalding at adaptec.com
Thu Mar 21 12:16:47 PST 2002

* From the T10 Reflector (t10 at t10.org), posted by:
* "Spalding, AlanC" <Alan_Spalding at adaptec.com>
Hi Folks,
I've some questions on one of the DATA-IN  IU exception handling conditions:

In SPI-4 rev 9 is paragraph 4.

"If a nexus has been fully identified and the information unit that failed
was not a SPI status information unit and the message received from the SCSI
initiator port was an INITIATOR DETECTED ERROR message then the SCSI target
port shall send a SPI L_Q/SPI status information unit pair to the SCSI
initiator port with a CHECK CONDITION status and a sense key set to ABORTED
COMMAND and an additional sense code set to INITIATOR DETECTED ERROR MESSAGE
RECEIVED for the task associated with the received INITIATOR DETECTED ERROR

Is it illegal for a target to generate a QAS message immediately after the
'Initiator Detected Error message"?

The wording seems to imply that target should immediately switch to DT
Data-In (IU). Is there any "wiggle room" for the target to 1st go bus free
and reconnect to send the SPI Status?

If there is "wiggle room" could a target send a QAS message after the
Initiator Detected Error message? Or, is a QAS message after a Message Out
phase completely illegal?  (SPI-4 seems to imply that a QAS message can only
occur immediately after DT DATA phase)?

Thanks in advance
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org

More information about the T10 mailing list