Clarification on ENCSERV bit in the standard INQUIRY

Tue Oct 11 18:42:21 PDT 2005

* From the T10 Reflector (t10 at t10.org), posted by:
* <Kevin_Marks at Dell.com>
*
This is a multi-part message in MIME format.

------_=_NextPart_001_01C5CECE.308204FD
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

All,=20

I recall several months ago at a CAP meeting, a discussion of the
ENCSERV, MCHNGER and SCCS bits in the standard INQUIRY and when they =
are
set or not set. To my recollection from the discussion, these bits are
used to indicate that a device (LUN, further question) supports these
command sets in addition to the command set generally associated with
the peripheral device type.=20

So, for example if the block device with a peripheral device type of =
00h
(SBC-2 - Direct access block device) contained an attached enclosure
services process (one of the SES models) that it would have the ENCSERV
bit set to one in the standard INQUIRY to indicate that it contained an
embedded enclosure services processor. For a standalone enclosure
services processor, such as one that would be contained in a JBOD as an
accessible LUN, the ENCSERV bit would be set to zero, because the
peripheral device type is already set to 0Dh (SES - Enclosure services
device.)

So is my recollection correct. If so, then I have to additional
questions:

1.      SES-2r12 currently states that for both the attached enclosure
services process model and the standalone enclosure services process
model that the ENCSERV shall be set to one. Is this correct?

2.      SPC-3 and SPC-4r02 for the ENCSERV bit say "An Enclosure
Services (ENCSERV) bit set to one indicates that the SCSI target device
contains an embedded enclosure services component. See SES for details
about enclosure services, including a device model for an embedded
enclosure services device. An ENCSERV bit set to zero indicates that =
the
SCSI target device does not contain an embedded enclosure services
component." Should the SCSI target device actually be Logical Unit
instead? This question actually applies to several of these bits.

Thanks

Kevin

------_=_NextPart_001_01C5CECE.308204FD
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">

 Clarification on ENCSERV bit in the standard INQUIRY All, = I = recall several months ago at a CAP meeting, a discussion = of the ENCSERV, MCHNGER and SCCS bits in the standard = INQUIRY and when they are set or = not set. To my recollection from the discussion, these bits are used to indicate that a device (LUN, further question) supports these command = sets in addition to the command = set generally associated with the peripheral = device type. So, = for example if the block device with a peripheral device = type of 00h (SBC-2 - Direct access block device) contained an attached enclosure services = process (one of the = SES models) that = it would have the ENCSERV bit = set = to one in the standard INQUIRY to indicate that = it contained an embedded enclosure = services processor. For a standalone enclosure services processor, = such as one that would be contained in a JBOD as an accessible = LUN, the ENCSERV bit would be set to = zero, because the peripheral device = type is already set to 0Dh (SES - Enclosure services = device.) So is my = recollection correct. If so, then I have to additional questions: 1.      = SES-2r12 = currently states that for both the attached enclosure services = process model and = the = standalone enclosure services process model that = the = ENCSERV shall be set to one. Is this correct? 2.      SPC-3 and SPC-4r02 for the ENCSERV = bit = say ;An Enclosure Services = (ENCSERV) bit set to one indicates that the SCSI target device contains = an embedded enclosure services component. See SES for details about = enclosure services, including a device model for an embedded enclosure = services device. An ENCSERV bit = set to zero indicates that the SCSI target device does = not contain an embedded = enclosure services component.; Should the SCSI target deviceactually be Logical Unit instead? = This question actually applies = to several of these = bits. Thanks Kevin 
------_=_NextPart_001_01C5CECE.308204FD--