
Message Processing in Data Out Phase (WRITE
Command)
Figure D-7 shows how each message is processed during the Data
Out phase of a WRITE command.
Parity Error in User Data Associated with WRITE Command
When parity checking is enabled and the CTS detects a parity error in
the logical blocks of user data received from the initiator, the CTS
aborts the data transfer. The data block containing the parity error is
not written to tape.
After aborting the data transfer, the CTS sends Check Condition
status to the initiator, followed by a Command Complete message.
The sense key is set to Aborted Command (Bh) and the ASC and
ASCQ bytes are set to 47h and 00h. The SCSI Bus Parity Error (BPE)
bitissetto1.
If you are attempting to write a variable-length block, you may be
able to recover by reissuing the WRITE command an unlimited
number of times. Each time a failure is detected, the CTS returns
Check Condition status.
If you are attempting to write fixed-length blocks, you may be
able to recover by following these steps:
1. Issue a REQUEST SENSE command.
2. Look at the Information Bytes to determine how many fixed
blocks need to be re-sent. These bytes indicate how many
logical blocks were not transferred successfully (including
the logical block with the parity error).
3. Adjust the initiator’s data pointer to reflect the number of
blocks that were successfully transferred.
4. Issue a WRITE command to re-send the blocks that were not
successfully transferred.
May 1994 EXB-8205 and EXB-8505
(Standard and XL)
D-15
Appendix D SCSI Bus Message Processing and Error Recovery
Comentários a estes Manuais