SPC Inquiry for Quad-Aligned Zero -- deprecated since SPC-4 maybe
roweber at ieee.org
Fri Jan 4 11:59:34 PST 2008
* From the T10 Reflector (t10 at t10.org), posted by:
* Ralph Weber <roweber at ieee.org>
I am totally flummoxed here. Why do you need a 'may' and a 'should'
in the same set of requirements when 'should' can always be read
as 'may be any value, but should be x'?
Please look carefully at the definition of the 'should' keyword
before carrying this too much farther.
All the best,
Knight, Frederick wrote:
> Actually, I was corrected offline. This wording can be taken to imply
> that "either a value of zero, or a value of at least file will return
> the ADDITIONAL LENGTH field in the parameter data". That is obviously
> incorrect. So, here's another suggestion:
> "The ALLOCATION LENGTH field is defined in 220.127.116.11. If EVPD is set to
> zero, the allocation length [[may be zero]]; or it should be at least
> five, so that the ADDITIONAL LENGTH field in the parameter data (see
> 6.4.2) is returned. If EVPD is set to one, the allocation length [[may
> be zero]]; or it should be [[-should be]] at least four, so that the
> PAGE LENGTH field in the parameter data (see 7.6) is returned."
> "The ALLOCATION LENGTH field is defined in 18.104.22.168. To return the
> ADDITIONAL LENGTH field in the parameter data (see 6.4.2) if EVPD is set
> to zero, the allocation length should be at least five. To return the
> PAGE LENGTH field in the parameter data (see 7.6) if EVPD is set to one,
> the allocation length should be should be at least four. To return no
> parameter data, the allocation length may be set to zero."
> Fred Knight
* 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