A keyword used to describe the behavior of the hardware or software in the design models assumed by the standard. Other hardware and software design models may also be implemented.
Ignored
A keyword used to describe an unused bit, byte, word, field or code value. The contents or value of an ignored bit, byte, word, field or code value shall not be examined by the receiving SCSI device and may be set to any value by the transmitting SCSI device.
Invalid
A keyword used to describe an illegal or unsupported bit, byte, word, field or code value. Receipt of an invalid bit, byte, word, field or code value shall be reported as an error.
Mandatory
A keyword indicating an item that is required to be implemented as defined in this standard.
May
A keyword that indicates flexibility of choice with no implied preference (equivalent to “may or may not”).
May not
Keywords that indicate flexibility of choice with no implied preference (equivalent to “may or may not”).
Need not
Keywords indicating a feature that is not required to be implemented (equivalent to “is not required to”).
Obsolete
A keyword indicating that an item was defined in prior SCSI standards but has been removed from the standard.
Optional
A keyword that describes features that are not required to be implemented by the standard. However, if any optional feature defined in the standard is implemented, then it shall be implemented as defined in the standard.
Reserved
A keyword referring to bits, bytes, words, fields and code values that are set aside for future standardiza-tion. A reserved bit, byte, word or field shall be set to zero, or in accordance with a future extension to the standard. Recipients are not required to check reserved bits, bytes, words or fields for zero values. Receipt of reserved code values in defined fields shall be reported as an error.
Restricted
A keyword referring to bits, bytes, words, and fields that are set aside for use in other SCSI standards. A restricted bit, byte, word, or field shall be treated as a reserved bit, byte, word or field for the purposes of the requirements defined in the standard.
Shall
A keyword indicating a mandatory requirement. Designers are required to implement all such mandatory requirements to ensure interoperability with other products that conform to the standard.
Should
A keyword indicating flexibility of choice with a strongly preferred alternative; equivalent to the phrase “it is strongly recommended.”
Vendor-specific
Something (e.g., a bit, field, or code value) that is not defined by the standard and may be used differently in various implementations.
1.4 Conventions
Certain words and terms used in the standard have a specific meaning beyond the normal English meaning.
These words and terms are defined either in this clause or in the text where they first appear. Names of com-mands, status codes, sense keys, and additional sense codes are in all uppercase (e.g., REQUEST SENSE).
If there is more than one CDB length for a particular command (e.g., MODE SENSE(6) and MODE SENSE(10)) and the name of the command is used in a sentence without any CDB length descriptor (e.g., MODE SENSE), then the condition specified in the sentence applies to all CDB lengths for that command.
Names of fields and state variables are in uppercase (e.g. NAME). When a field or state variable name con-tains acronyms, uppercase letters may be used for readability. Normal case is used when the contents of a field or state variable are being discussed. Fields or state variables containing only one bit are usually referred to as the NAME bit instead of the NAME field.
Normal case is used for words having the normal English meaning.
A binary number is represented in the standard by any sequence of digits comprised of only the Western-Ara-bic numerals 0 and 1 immediately followed by a lower-case b (e.g., 0101b). Underscores or spaces may be included between characters in binary number representations to increase readability or delineate field bound-aries (e.g., 0 0101 1010b or 0_0101_1010b).
A hexadecimal number is represented in the standard by any sequence of digits comprised of only the West-ern-Arabic numerals 0 through 9 and/or the upper-case English letters A through F immediately followed by a lower-case h (e.g., FA23h). Underscores or spaces may be included in hexadecimal number representations to increase readability or delineate field boundaries (e.g., B FD8CFA23h or B_FD8C_FA23h).
A decimal number is represented in the standard by any sequence of digits comprised of only the Western-Ara-bic numerals 0 through 9 not immediately followed by a lower-case b or lower-case h (e.g., 25).
When the value of the bit or field is not relevant, x or xx appears in place of a specific value.
the standard uses the ISO convention for representing decimal numbers (e.g., the thousands and higher multi-ples are separated by a space and a comma is used as the decimal point). Table 1 shows some exammulti-ples of decimal numbers represented using the ISO and American conventions.
Table 1 — ISO v American Numbering Conventions
Lists sequenced by letters (e.g., a) red, b) blue, c) green) show no ordering relationship between the listed items. Lists sequenced by numbers (e.g., 1) red, 2) blue, 3) green) show an ordering relationship between the listed items.
If a conflict arises between text, tables or figures, the order of precedence to resolve the conflicts is text, then tables, and finally figures. Not all tables or figures are fully described in the text. Tables show data format and values. Notes do not constitute any requirements for implementors.
ISO American
0,6 0.6
3,141 592 65 3.14159265
1 000 1,000
1 323 462 1,323,462.95