Section 5
SCSI Programming Guidelines
o
1
ADDITIONAL SENSE LENGTH (Byte
7)
-
The
number
of
additional bytes to follow.
This
value will not
be
truncated
if
the allocation length
in
the
command
descriptor block is too small to
transfer all
of
the additional sense bytes.
The
ProDri
••
uses a value
of
OA
H in byte 7.
ADDITIONAL SENSE CODE (Byte
12)
-
Refer
to
Table
5-12.
FRU -
FIELD
REPLACEABLE UNIT FAILED (Byte 14) -
The
format
of
this
byte
is
vendor unique. A value
of
zero
means
that
no
FRU is
to
be
reported.
FPV -
FIELD
POINTER V ALID (Byte 15, Bit 7) -
Set
to
zero indicates
that
the
C/O
bit
and
BPV
bi~
and
bytes
16
and
17
are not valid. An
FPV
bit
set
to
one
indicates
that
the field pointer
bytes
16
and
17,
the
C/O
bit
and
BPV
bit, are
s~gnificant.
C/D • CONTROL/DAT A
BIT
(Byte 15, Bit 6) -
Set
to
one
indicates
that
the
value
reported
in
the field pointer is the
Command
Descriptor
Block
(COB) byte' number for which
an
ILLEGAL
REQUEST
sense
key
was issued. A
C/O
bit
of
zero indicates that the value reported in the field
pointer is the byte number
of
the
DATA
phase for which
an
ILLEGAL
REQUEST
sense
key
was
issued.
VENDOR UNIQUE (Byte 15, Bits 5·4) - Bits 5
and
4
of
byte
15
are
vendor
unique.
BPV • BIT POINTER VALID (Byte 15, Bit 3) -
Set
to
zero indicates
that
the
bit
pointer
field is not valid. A
BPV
bit
set
to
one indicates that the
bit
pointer field (Bits 0 - 2) is valid.
BIT
POINTER
(Byte 15, Bits 2·0) -
If
BPV is set, this field points
to
the
bit
within the byte
that is
in
error.
FIELD POINTER (Bytes
16-17)
-
These
bytes represent
an
index into the
Command
Descriptor
Block
fields
or
the
DATA
phase fields for which an
ILLEGAL
REQUEST
sense
key
was issued. In
the case
of
multiple byte fields, the field pointer bytes index the
most
significant byte
of
the field for
which
an
illegal request sense
key
was issued.
These
bytes are only valid
if
the Field Pointer Valid
(FPV)
bit
is
set
to
one.
00
00
02
10
11
TABLE 5·12 Sense Error Codes
Description
NO
SENSE.
No
specific sense key information
to
be
reported.
This
would be the
case for a successful command
or
a command that received a
CHECK
CONDmON
status because
one
of
the filemark,
EOM,
or
ILl
bits
is
set
to
one.
No
additional infonnation
RECOVERED
ERROR.
The
last
command
was completed successfully with
some
recovery action performed
by
the ProD';
••.
Details
may
be
detennined
by
examining
the additional sense bytes
and
the
information bytes.
No
additional infonnation
Recovered seek timeout
Recovered
ID
CRC
error
Recovered data
ECC
on
last retry
5·24
SCSI Programming Guidelines