99-266r1 - Description Lengths for 5D ASC/ASCQs

Gerry_Houlder at notes.seagate.com Gerry_Houlder at notes.seagate.com
Wed Sep 22 12:26:37 PDT 1999


* From the T10 Reflector (t10 at t10.org), posted by:
* Gerry_Houlder at notes.seagate.com
*
When the ASC/ASCQ description is in document text, it just refers to the
description. The reader then has to look up the description in SPC-2 to
figure out what the sense bytes should be.

If the description isn't an exact match and you are unlucky enough to find
two or more descriptions that are close, which one is correct? What if your
customer's opinion about which is right differs from yours? The only sure
way to eliminate this situation is to always have an exact match between
the text description in the SPC-2 tables and the command set documents.





"Edward A. Gardner" <eag at ophidian.com> on 09/22/99 11:46:55 AM

To:   Gerry Houlder, t10 at t10.org
cc:

Subject:  Re: 99-266r1 - Description Lengths for 5D ASC/ASCQs




>* From the T10 Reflector (t10 at t10.org), posted by:
>* Gerry_Houlder at notes.seagate.com
>*
>If RBC description already differs from SPC-2, perhaps the SPC-2 wording
>should be changed to exactly match RBC? This would help avoid future
>confusion.

Or maybe someone should make a public review comment for RBC, requesting
that it change to match SPC-2's wording.

Does it really matter whether the wording is identical, so long as they
mean
the same thing?  Many concepts more fundamental (to SCSI) than these have
been phrased differently in different documents without harm.

Edward A. Gardner               eag at ophidian.com
Ophidian Designs                719 593-8866 voice
1262 Hofstead Terrace           719 593-8989 fax
Colorado Springs, CO  80907






*
* 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