Table of Contents
Advertisement
VERIFY
7. ATAPI Packet Command Specification
If, however, the drive encounters a Set-mark during VERIFY, nothing is reported unless the drive has been
configured through MODE SELECT to Report Set-marks. The drive will space over the Set-mark and continue the
VERIFY. If the Report Set-marks configuration is enabled then the File-mark and Valid bits are set and the Sense
Key field is set to NO SENSE. The Information fields contain the residue count and the Additional Sense Code and
Additional Sense Code Qualifier fields are set to Set-mark Detected. The tape is logically positioned after the Set-
mark (EOM side).
If the drive detects EOD during VERIFY, the drive will return a CHECK CONDITION status. Within the Sense data,
the File-mark and Valid bits are set and the Sense Key field is set to BLANK CHECK. The Information fields
contain the residue count. The Additional Sense Code and Additional Sense Code Qualifier fields are not set.
Upon termination, the media will be physically positioned before EOD and after the last block on tape.
The meaning of EOM is different for VERIFY than for a WRITE type of command. EOM is only reported when the
physical EOM/P is encountered. The drive returns a CHECK CONDITION status. The EOM and Valid bits are set
and the Sense Key is set to MEDIUM ERROR. The Information fields contain the residue count and the Additional
Sense Code and Additional Sense Code Qualifier fields are set to EOM/P Detected. The tape is physically
positioned at EOM/P.
For a File-mark, a (reported) Set-mark, EOD or EOM detected, if the Fixed bit is set, the Information field in the
Request Sense Data will be set to the difference (residue) between the requested Verification Length and the
actual number of blocks verified (not including the File mark or Set-mark). If the fixed bit is set to ZERO, the
information bytes will be set to the difference (residue) between the requested Verification Length and the actual
number of bytes verified. File-marks and Set-marks are considered to have a byte count of ZERO, though this
does not cause the ILI bit to be set.
VERIFY may return the following sense keys on a CHECK CONDITION:
NO SENSE: If the actual block length is different from the specified Verification Length, in Variable Block mode,
the Incorrect Length Indicator (ILI) bit and Valid bit are set to one. The Information bytes in extended sense are set
to the difference (residue) between the requested length and the actual block length. In blocked mode, they are
set to the difference (residue) between the requested number of blocks and the actual number of blocks verified.
If the drive reads a File-mark during this command, it will set the File-mark bit in the Request Sense data. Upon
termination, the tape will be logically positioned after the File-mark (EOM side). If, however, the drive encounters a
Set-mark during this command, nothing will be reported unless the SDX-470V has been configured through MODE
SELECT to Report Set-marks.
If the Report Set-marks configuration is enabled, then the Valid bit and the Additional Sense Key flags will be set
in the Request Sense data to indicate that a Set-mark has been encountered. The tape will also be logically
positioned after the Save-Set Mark (EOM side). For both a File-mark and a (reported) Set-mark, if the Fixed bit is
one, the Information bytes in the Request Sense data are set to the difference (residue) between the requested
Verification Length and the actual number of blocks verified (not including the File-mark or Set-mark). If the Fixed
bit is set to ZERO, the Information blocks will be set to the difference (residue) between the requested Verification
Length and the actual number of bytes verified. File-marks and Save-Set Marks are considered to have a byte
count of ZERO, though this will not cause the ILI bit to be set.
This command is implemented for Microsoft logo certification (WHQL).
SONY AIT-1 Turbo drive SDX-470V series Ver.1.0
7-77
Advertisement
Table of Contents
