Thanks Rob

Kishore

From: owner-t10@t10.org [mailto:owner-t10@t10.org] On Behalf Of Elliott, Robert (Server Storage)
Sent: Friday, August 03, 2007 7:32 PM
To: t10@t10.org
Subject: RE: Error in hexadecimal value of primitive encoding in SAS Standard

OPEN_REJECT (RESERVED ABANDON 0) became OPEN_REJECT (ZONE VIOLATION) in SAS-2. The reserved primitives were designed to be taken over in this manner by new features.

The hex column was off by one as you mention; it should be correct in sas2r11 (see http://www.t10.org/drafts.htm). Table consistency in this revision has been checked with a perl script.

--
Rob Elliott, elliott@hp.com
Hewlett-Packard Industry Standard Server Storage Advanced Technology
https://ecardfile.com/id/RobElliott

From: owner-t10@t10.org [mailto:owner-t10@t10.org] On Behalf Of Karthikeyan, Kishore K
Sent: Friday, August 03, 2007 8:01 PM
To: t10@t10.org
Cc: Karthikeyan, Kishore K
Subject: Error in hexadecimal value of primitive encoding in SAS Standard

I find two issues in this table

OPEN_REJECT (RESERVED ABANDON 0) primitive is no longer there. Was this removal from the standard intentional?

The hexadecimal values in the table corresponding to the primitives are not correct starting from OPEN_REJECT (RESERVED ABANDON 1) and has the wrong values for all open reject primitives.

Seems like when the row for the OPEN_REJECT (RESERVED ABANDON 0) got deleated, the deletion of the row was missed out from the last column and hence this column got shifted up by one row.

Thanks

Kishore