Talk:Key Code Qualifier

Latest comment: 5 years ago by Pokechu22 in topic Where are the sources?

Is it possible somone could add a link to a complete list of Sense Key/ASC/ASCQ codes. A lot of places seem to have partial lists and it would be a very useful resource.

The complete list is given in the SPC-4 spec. You can get the last draft from ftp.t10.org. --Ste.Ri 16:17, 7 August 2006 (UTC)Reply

195.212.29.83 (talk) 17:04, 6 January 2009 (UTC) KCQ's with C>127 or Q>127 are vendor unique (see the last few lines of table C.1 in spc4r11.pdf on ftp.t10.org), but a few of these have crept into the table. A complete list that includes all KCQ's from all vendors would be a REALLY useful resource, and would probably require multiple decodes in the hopefully occasional case where two vendors happen to have used the same KCQ combination to signify different errors. A vendor column would then also be required.Reply

The standard K's: http://www.t10.org/lists/2sensekey.htm
The standard CQ's: http://www.t10.org/lists/asc-num.htm
All part of 'SCSI Common Codes & Values' at: http://www.t10.org/lists/1spc-lst.htm
--T10fan (talk) 03:25, 17 February 2010 (UTC)Reply

Where are the sources?

edit

Unless someone can provide an official source for the term "key code qualifier" and the claim that "all three fields are usually logically combined into a 20 bit field", I think this article should be deleted. I can't find any mention of the term in the SAM or SPC documents and most of the Google results simply link back to this article. Furthermore, the Sense Key and ASC/ASCQ fields are separate and may appear in any combination, which means there is no reason to treat them as a single value. 198.45.199.90 (talk) 21:53, 7 July 2017 (UTC)Reply

I can't confirm the term "key code qualifier", nor can I confirm "usually" combined. However, §2.4.1.6 Additional Sense and Additional Sense Qualifier codes of Segate's SCSI Commands Reference Manual does group ASC/ASCQ with the sense key, albeit not in a way that exactly matches. --Pokechu22 (talk) 01:35, 1 September 2019 (UTC)Reply