N WORKING                                                                 X3T9.2N DRAFT                                                             Project 375D  N                                                                   Revision 10LN                                                                       7-SEP-93/      NOTE:  This file is provided to facilitate ,      review and comments on the draft SCSI-22      standard.  It is NOT intended as a substitute1      for obtaining a paper copy of this document. /      The figures and formatting information are 0      omitted.  Please contact Global Engineering2      Documents at (800) 854-7179 or (303) 792-2181      to obtain a paper copy.       Information technology -# Small Computer System Interface - 2        Secretariat:7 Computer & Business Equipment Manufacturers Association       A This is a draft proposed American National Standard of Accredited G Standards Committee X3.  As such this is not a completed standard.  The I X3T9 Technical Committee may modify this document as a result of comments B received during the public review process and the approval of thisF document as a standard.  Use of the information contained herein is at your own risk.  ? Permission is granted to members of X3 and ISO, their technical G committees, and their associated task groups to reproduce this document I for the purposes of X3 and ISO standardization activities without further C permission, provided this notice is included.  All other rights are C reserved.  Any commercial or for-profit use is strictly prohibited.                       @ ASC X3T9.2 Technical Editor:                  Lawrence J. Lamers@                                               Maxtor Corporation5                                               MS A697 D                                               150 River Oaks ParkwayF                                               San Jose, CA  95134-19831                                               USA E                                               Telephone: 408-432-3889 E                                               Facsimile: 408-432-3833 L                                               Email: larry_lamers@maxtor.com      >                                               Reference numberC                                               ISO/IEC 9316-1 : 199x @                                               ANSI X3.131 - 199xN                                               Printed November, 7, 1993 3:39pm   POINTS OF CONTACT:  > X3T9.2 Chair                                 X3T9.2 Vice-Chair9 John B. Lohmeyer                             I. Dal Allan I NCR Corporation                              ENDL                         E 1635 Aeroplaza Drive                         14426 Black Walnut Court @ Colo Spgs, CO 80916                          Saratoga, CA  95070  H Tel:   (719) 573-3362                        Tel:         (408) 867-6630H Fax:   (719) 597-8225                        Fax:         (408) 867-2115N Email: john.lohmeyer@ftcollinsco.ncr.com     Email:        2501752@mcimail.com   X3 Secretariat
 Lynn Barra" Administrator Standards ProcessingF X3 Secretariat                               Telephone:   202-626-5738F 1250 Eye Street, NW   Suite 200              Facsimile:   202-638-4922 Washington, DC   20005   SCSI Reflector8 Internet address for subscription to the SCSI reflector: scsiadm@wichitaks.ncr.com 5 Internet address for distribution via SCSI reflector:  scsi@wichitaks.ncr.com   SCSI Bulletin Board  719-574-0424   Document Distribution J Global Engineering                            Telephone:  303-792-2181 or F 15 Inverness Way East                                     800-854-7179F Englewood, CO   80112-5704                    Facsimile:  303-792-2192    (                                 ABSTRACT  J The SCSI protocol is designed to provide an efficient peer-to-peer I/O bus@ with up to 16 devices, including one or more hosts.  Data may be> transferred asynchronously at rates that only depend on deviceJ implementation and cable length.  Synchronous data transfers are supportedG at rates up to 10 mega-transfers per second.  With the 32-bit wide data J transfer option, data rates of up to 40 megabytes per second are possible.  C SCSI-2 includes command sets for magnetic and optical disks, tapes, = printers, processors, CD-ROMs, scanners, medium changers, and  communications devices.     -                              PATENT STATEMENT   G The developers of this standard have requested that holder's of patents F that may be required for the  implementation of the standard, discloseF such patents to the publisher.  However neither the developers nor theG publisher have undertaken a patent search in order to identify which if ' any patents may apply to this standard.   E No position is taken with respect to the validity of any claim or any A patent rights that may have been disclosed.  Details of submitted I statements may be obtained from the publisher concerning any statement of @ patents and willingness to grant a license under these rights onC reasonable and nondiscriminatory terms and conditions to applicants " desiring to obtain such a license.     Document Status   7 The following are the changes from revision 10k to 10l.   M 1.     Page 3, clause 3, move the sentence beginning "For the purposes" after "        the title to subclause 3.1.  M 2.     Pages 3 to 5, clause 3, definitions should not begin with phrases such $        as "This term refers to" etc.  F 3.     Page 8, clause 5, remove the full stop after the clause number.  B 4.     Page 8, subclause 5.2.1, line 1, replace "meters" with "m".  C 5.     In the Introduction, item c) under the list of new low-level K        requirements should read:  "The arbitration delay was increased from         2.2 to 2.4 us"   I 6.     In 4.1 Overview, the last line of the fifth paragraph should read: @        "are contending and can be completed in less than 10 us."  K 7.     In 8.3.3.2 Disconnect-reconnect page, there are three occurrences of I        100 ms being substituted for 100 microsecond.  These should all be D        changed to 100 us.  The corrected lines should read: "The busI        inactivity limit field indicates the maximum time in 100 us ...".  L        "The disconnect time limit field indicates the minimum time in 100 usM        ...".  "The connect time limit field indicates the maximum time in 100         us ..."  M 8.     In 9.3.3.2 Flexible disk page, the paragraph describing the drive step L        rate should begin: "The drive step rate field specifies the step rate        in units of 100 us."   J 9.     In 12.2.2, paragraph 7, the reference is to Table 65, not 8.2.14.1.  J 10.       The Foreword and Introduction clauses were modified to correctly%           reflect the ANSI/ISO style.   0 11.       Updated the Vendor ID list in Annex E.   ERRATA  G The following errors have been reported.  Due to the constraints of the I standards process these errors cannot be corrected within the body of the F document.  The X3T9.2 committee plans to issue errata to correct these items.  I 1.     An error exists in Table 161.  The Head load bit pattern should be         P011 not P000.    ContentsM                                                                          Page M Foreword. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxix   M Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxx   M 1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .   1   M 2 Normative references. . . . . . . . . . . . . . . . . . . . . . . . . .   2   M 3 Definitions, symbols and abbreviations. . . . . . . . . . . . . . . . .   3 M    3.1 Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . .   3 M    3.2 Symbols and abbreviations. . . . . . . . . . . . . . . . . . . . .   5   M 4 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .   6 M    4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . .   6 M    4.2 Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . .   7   M 5 Physical characteristics. . . . . . . . . . . . . . . . . . . . . . . .   9 M    5.1 Physical description . . . . . . . . . . . . . . . . . . . . . . .   9 M    5.2 Cable requirements   . . . . . . . . . . . . . . . . . . . . . . .   9 M    5.2.1 Single-ended cable . . . . . . . . . . . . . . . . . . . . . . .   9 M    5.2.2 Differential cable . . . . . . . . . . . . . . . . . . . . . . .  10 M    5.2.3 Cable requirements for fast synchronous data transfer. . . . . .  10 M    5.3 Connector requirements . . . . . . . . . . . . . . . . . . . . . .  10 M    5.3.1 Non-shielded connector requirements. . . . . . . . . . . . . . .  10 M    5.3.1.1 Non-shielded connector alternative 1 - A cable . . . . . . . .  10 M    5.3.1.2 Non-shielded connector alternative 2 - A cable . . . . . . . .  11 M    5.3.1.3 Non-shielded connector - B cable . . . . . . . . . . . . . . .  11 M    5.3.2 Shielded connector requirements. . . . . . . . . . . . . . . . .  16 M    5.3.2.1 Shielded connector alternative 1 - A cable . . . . . . . . . .  16 M    5.3.2.2 Shielded connector alternative 2 - A cable . . . . . . . . . .  16 M    5.3.2.3 Shielded connector - B cable . . . . . . . . . . . . . . . . .  16 M    5.3.3 Connector contact assignments. . . . . . . . . . . . . . . . . .  21 M    5.4 Electrical description . . . . . . . . . . . . . . . . . . . . . .  26 M    5.4.1 Single-ended alternative . . . . . . . . . . . . . . . . . . . .  26 M    5.4.1.1 Output characteristics . . . . . . . . . . . . . . . . . . . .  26 M    5.4.1.2 Input characteristics. . . . . . . . . . . . . . . . . . . . .  26 M    5.4.2 Differential alternative . . . . . . . . . . . . . . . . . . . .  27 M    5.4.2.1 Output characteristics . . . . . . . . . . . . . . . . . . . .  27 M    5.4.2.2 Input characteristics. . . . . . . . . . . . . . . . . . . . .  27 M    5.4.3 Terminator power . . . . . . . . . . . . . . . . . . . . . . . .  27 M    5.4.4 RESERVED lines . . . . . . . . . . . . . . . . . . . . . . . . .  30 M    5.5 SCSI bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  31 M    5.6 SCSI bus signals . . . . . . . . . . . . . . . . . . . . . . . . .  332M    5.6.1 Signal values. . . . . . . . . . . . . . . . . . . . . . . . . .  34DM    5.6.2 OR-tied signals. . . . . . . . . . . . . . . . . . . . . . . . .  341M    5.6.3 Signal sources . . . . . . . . . . . . . . . . . . . . . . . . .  34-M    5.7 SCSI bus timing. . . . . . . . . . . . . . . . . . . . . . . . . .  36oM    5.7.1 Arbitration delay  . . . . . . . . . . . . . . . . . . . . . . .  36rM    5.7.2 Assertion period . . . . . . . . . . . . . . . . . . . . . . . .  36oM    5.7.3 Bus clear delay  . . . . . . . . . . . . . . . . . . . . . . . .  36aM    5.7.4 Bus free delay . . . . . . . . . . . . . . . . . . . . . . . . .  37tM    5.7.5 Bus set delay  . . . . . . . . . . . . . . . . . . . . . . . . .  37pM    5.7.6 Bus settle delay . . . . . . . . . . . . . . . . . . . . . . . .  37pM    5.7.7 Cable skew delay . . . . . . . . . . . . . . . . . . . . . . . .  37hM    5.7.8 Data release delay . . . . . . . . . . . . . . . . . . . . . . .  37hM    5.7.9 Deskew delay . . . . . . . . . . . . . . . . . . . . . . . . . .  37 M    5.7.10 Disconnection delay . . . . . . . . . . . . . . . . . . . . . .  37iM    5.7.11 Hold time . . . . . . . . . . . . . . . . . . . . . . . . . . .  37IM    5.7.12 Negation period . . . . . . . . . . . . . . . . . . . . . . . .  37 M    5.7.13 Power-on to selection time  . . . . . . . . . . . . . . . . . .  37uM    5.7.14 Reset to selection time . . . . . . . . . . . . . . . . . . . .  38 M    5.7.15 Reset hold time . . . . . . . . . . . . . . . . . . . . . . . .  38 M    5.7.16 Selection abort time  . . . . . . . . . . . . . . . . . . . . .  38 M    5.7.17 Selection time-out delay  . . . . . . . . . . . . . . . . . . .  38 M    5.7.18 Transfer period . . . . . . . . . . . . . . . . . . . . . . . .  38 M    5.8 Fast synchronous transfer option . . . . . . . . . . . . . . . . .  38aM    5.8.1 Fast assertion period  . . . . . . . . . . . . . . . . . . . . .  38 M    5.8.2 Fast cable skew delay  . . . . . . . . . . . . . . . . . . . . .  38 M    5.8.3 Fast deskew delay  . . . . . . . . . . . . . . . . . . . . . . .  39 M    5.8.4 Fast hold time . . . . . . . . . . . . . . . . . . . . . . . . .  39 M    5.8.5 Fast negation period . . . . . . . . . . . . . . . . . . . . . .  39   M 6 Logical characteristics . . . . . . . . . . . . . . . . . . . . . . . .  41 M    6.1 SCSI bus phases. . . . . . . . . . . . . . . . . . . . . . . . . .  41eM    6.1.1 BUS FREE phase . . . . . . . . . . . . . . . . . . . . . . . . .  41 M    6.1.2 ARBITRATION phase. . . . . . . . . . . . . . . . . . . . . . . .  42aM    6.1.3 SELECTION phase. . . . . . . . . . . . . . . . . . . . . . . . .  42 M    6.1.3.1 SELECTION time-out procedure . . . . . . . . . . . . . . . . .  43oM    6.1.4 RESELECTION phase. . . . . . . . . . . . . . . . . . . . . . . .  435M    6.1.4.1 RESELECTION    . . . . . . . . . . . . . . . . . . . . . . . .  432M    6.1.4.2 RESELECTION time-out procedure . . . . . . . . . . . . . . . .  44lM    6.1.5 Information transfer phases. . . . . . . . . . . . . . . . . . .  44rM    6.1.5.1 Asynchronous information transfer. . . . . . . . . . . . . . .  45 M    6.1.5.2 Synchronous data transfer. . . . . . . . . . . . . . . . . . .  45cM    6.1.5.3 Wide data transfer . . . . . . . . . . . . . . . . . . . . . .  46eM    6.1.6 COMMAND phase. . . . . . . . . . . . . . . . . . . . . . . . . .  48tM    6.1.7 Data phase . . . . . . . . . . . . . . . . . . . . . . . . . . .  48BM    6.1.7.1 DATA IN phase. . . . . . . . . . . . . . . . . . . . . . . . .  48 M    6.1.7.2 DATA OUT phase . . . . . . . . . . . . . . . . . . . . . . . .  48 M    6.1.8 STATUS phase . . . . . . . . . . . . . . . . . . . . . . . . . .  48 M    6.1.9 Message phase. . . . . . . . . . . . . . . . . . . . . . . . . .  48TM    6.1.9.1 MESSAGE IN phase . . . . . . . . . . . . . . . . . . . . . . .  48 M    6.1.9.2 MESSAGE OUT phase. . . . . . . . . . . . . . . . . . . . . . .  48sM    6.1.10 Signal restrictions between phases. . . . . . . . . . . . . . .  49tM    6.2 SCSI bus conditions. . . . . . . . . . . . . . . . . . . . . . . .  50pM    6.2.1 Attention condition. . . . . . . . . . . . . . . . . . . . . . .  50 M    6.2.2 Reset condition. . . . . . . . . . . . . . . . . . . . . . . . .  51 M    6.2.2.1 Hard reset alternative . . . . . . . . . . . . . . . . . . . .  51nM    6.2.2.2 Soft reset alternative . . . . . . . . . . . . . . . . . . . .  51TM    6.3 SCSI bus phase sequences . . . . . . . . . . . . . . . . . . . . .  52eM    6.4 SCSI pointers. . . . . . . . . . . . . . . . . . . . . . . . . . .  54uM    6.5 Message system description . . . . . . . . . . . . . . . . . . . .  55 M    6.6 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  58 M    6.6.1 ABORT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  58fM    6.6.2 ABORT TAG. . . . . . . . . . . . . . . . . . . . . . . . . . . .  58mM    6.6.3 BUS DEVICE RESET . . . . . . . . . . . . . . . . . . . . . . . .  59oM    6.6.4 CLEAR QUEUE. . . . . . . . . . . . . . . . . . . . . . . . . . .  59eM    6.6.5 COMMAND COMPLETE . . . . . . . . . . . . . . . . . . . . . . . .  59sM    6.6.6 DISCONNECT . . . . . . . . . . . . . . . . . . . . . . . . . . .  59sM    6.6.7 IDENTIFY . . . . . . . . . . . . . . . . . . . . . . . . . . . .  60hM    6.6.8 IGNORE WIDE RESIDUE. . . . . . . . . . . . . . . . . . . . . . .  61cM    6.6.9 INITIATE RECOVERY. . . . . . . . . . . . . . . . . . . . . . . .  61rM    6.6.10 INITIATOR DETECTED ERROR. . . . . . . . . . . . . . . . . . . .  62eM    6.6.11 LINKED COMMAND COMPLETE . . . . . . . . . . . . . . . . . . . .  62 M    6.6.12 LINKED COMMAND COMPLETE (WITH FLAG) . . . . . . . . . . . . . .  62rM    6.6.13 MESSAGE PARITY ERROR. . . . . . . . . . . . . . . . . . . . . .  622M    6.6.14 MESSAGE REJECT. . . . . . . . . . . . . . . . . . . . . . . . .  62oM    6.6.15 MODIFY DATA POINTER Message . . . . . . . . . . . . . . . . . .  63 M    6.6.16 NO OPERATION. . . . . . . . . . . . . . . . . . . . . . . . . .  63 M    6.6.17 Queue tag messages. . . . . . . . . . . . . . . . . . . . . . .  63 M    6.6.17.1 HEAD OF QUEUE TAG . . . . . . . . . . . . . . . . . . . . . .  64tM    6.6.17.2 ORDERED QUEUE TAG . . . . . . . . . . . . . . . . . . . . . .  64eM    6.6.17.3 SIMPLE QUEUE TAG. . . . . . . . . . . . . . . . . . . . . . .  64nM    6.6.18 RELEASE RECOVERY. . . . . . . . . . . . . . . . . . . . . . . .  64 M    6.6.19 RESTORE POINTERS. . . . . . . . . . . . . . . . . . . . . . . .  65 M    6.6.20 SAVE DATA POINTER . . . . . . . . . . . . . . . . . . . . . . .  65 M    6.6.21 SYNCHRONOUS DATA TRANSFER REQUEST message . . . . . . . . . . .  65bM    6.6.22 TERMINATE I/O PROCESS . . . . . . . . . . . . . . . . . . . . .  67dM    6.6.23 WIDE DATA TRANSFER REQUEST message. . . . . . . . . . . . . . .  67   M 7 SCSI commands and status. . . . . . . . . . . . . . . . . . . . . . . .  71eM    7.1 Command implementation requirements. . . . . . . . . . . . . . . .  71rM    7.1.1 Reserved . . . . . . . . . . . . . . . . . . . . . . . . . . . .  71eM    7.1.2 Operation code types . . . . . . . . . . . . . . . . . . . . . .  71dM    7.2 Command descriptor block . . . . . . . . . . . . . . . . . . . . .  72 M    7.2.1 Operation code . . . . . . . . . . . . . . . . . . . . . . . . .  73 M    7.2.2 Logical unit number. . . . . . . . . . . . . . . . . . . . . . .  74nM    7.2.3 Logical block address. . . . . . . . . . . . . . . . . . . . . .  74 M    7.2.4 Transfer length. . . . . . . . . . . . . . . . . . . . . . . . .  74tM    7.2.5 Parameter list length. . . . . . . . . . . . . . . . . . . . . .  74iM    7.2.6 Allocation length. . . . . . . . . . . . . . . . . . . . . . . .  751M    7.2.7 Control field. . . . . . . . . . . . . . . . . . . . . . . . . .  752M    7.3 Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  76eM    7.4 Command examples . . . . . . . . . . . . . . . . . . . . . . . . .  774M    7.4.1 Single command example . . . . . . . . . . . . . . . . . . . . .  774M    7.4.2 Disconnect example . . . . . . . . . . . . . . . . . . . . . . .  77 M    7.4.3 Linked command example . . . . . . . . . . . . . . . . . . . . .  78 M    7.5 Command processing considerations and exception conditions . . . .  79 M    7.5.1 Programmable operating definition. . . . . . . . . . . . . . . .  79 M    7.5.2 Incorrect initiator connection . . . . . . . . . . . . . . . . .  79 M    7.5.3 Selection of an invalid logical unit . . . . . . . . . . . . . .  80 M    7.5.4 Parameter rounding . . . . . . . . . . . . . . . . . . . . . . .  80 M    7.5.5 Asynchronous event notification  . . . . . . . . . . . . . . . .  81 M    7.5.6 Unexpected reselection . . . . . . . . . . . . . . . . . . . . .  82 M    7.6 Contingent allegiance condition. . . . . . . . . . . . . . . . . .  82 M    7.7 Extended contingent allegiance condition . . . . . . . . . . . . .  83 M    7.8 Queued I/O processes . . . . . . . . . . . . . . . . . . . . . . .  84 M    7.8.1 Untagged queuing . . . . . . . . . . . . . . . . . . . . . . . .  84 M    7.8.2 Tagged queuing . . . . . . . . . . . . . . . . . . . . . . . . .  84 M    7.8.3 Example of queued I/O process. . . . . . . . . . . . . . . . . .  86 M    7.8.3.1 Typical sequences for tagged queuing . . . . . . . . . . . . .  86 M    7.8.3.2 Example of tagged queuing. . . . . . . . . . . . . . . . . . .  86 M    7.9  Unit attention condition. . . . . . . . . . . . . . . . . . . . .  88   M 8  All device types . . . . . . . . . . . . . . . . . . . . . . . . . . .  915M    8.1 Model for all device types . . . . . . . . . . . . . . . . . . . .  915M    8.1.1 SCSI addresses . . . . . . . . . . . . . . . . . . . . . . . . .  915M    8.1.1.1 SCSI device address. . . . . . . . . . . . . . . . . . . . . .  915M    8.1.1.2 Logical units. . . . . . . . . . . . . . . . . . . . . . . . .  915M    8.1.1.3 Target routines. . . . . . . . . . . . . . . . . . . . . . . .  915M    8.1.2 Commands implemented by all SCSI devices . . . . . . . . . . . .  915M    8.1.2.1 Using the INQUIRY command. . . . . . . . . . . . . . . . . . .  925M    8.1.2.2 Using the REQUEST SENSE command. . . . . . . . . . . . . . . .  925M    8.1.2.3 Using the SEND DIAGNOSTIC command. . . . . . . . . . . . . . .  925M    8.1.2.4 Using the TEST UNIT READY command. . . . . . . . . . . . . . .  925M    8.2 Commands for all device types. . . . . . . . . . . . . . . . . . .  925M    8.2.1 CHANGE DEFINITION command. . . . . . . . . . . . . . . . . . . .  935M    8.2.2 COMPARE command. . . . . . . . . . . . . . . . . . . . . . . . .  955M    8.2.3 COPY command . . . . . . . . . . . . . . . . . . . . . . . . . .  965M    8.2.3.1 Errors detected by the managing SCSI device. . . . . . . . . .  985M    8.2.3.2 Errors detected by a target. . . . . . . . . . . . . . . . . .  985M    8.2.3.3 COPY function code 00h and 01h . . . . . . . . . . . . . . . .  995M    8.2.3.4 COPY function code 02h . . . . . . . . . . . . . . . . . . . . 1005M    8.2.3.5 COPY function code 03h . . . . . . . . . . . . . . . . . . . . 1005M    8.2.3.6 COPY function code 04h . . . . . . . . . . . . . . . . . . . . 1015M    8.2.3.7 Copies with unequal block lengths. . . . . . . . . . . . . . . 1025M    8.2.4 COPY AND VERIFY command. . . . . . . . . . . . . . . . . . . . . 1035M    8.2.5 INQUIRY command. . . . . . . . . . . . . . . . . . . . . . . . . 1045M    8.2.5.1 Standard INQUIRY data. . . . . . . . . . . . . . . . . . . . . 1055M    8.2.5.2 Vital product data . . . . . . . . . . . . . . . . . . . . . . 1085M    8.2.6 LOG SELECT command . . . . . . . . . . . . . . . . . . . . . . . 1095M    8.2.7 LOG SENSE command. . . . . . . . . . . . . . . . . . . . . . . . 1115M    8.2.8 MODE SELECT(6) command . . . . . . . . . . . . . . . . . . . . . 1125M    8.2.9 MODE SELECT(10) command. . . . . . . . . . . . . . . . . . . . . 1145M    8.2.10 MODE SENSE(6) command . . . . . . . . . . . . . . . . . . . . . 1155M    8.2.10.1 Current values. . . . . . . . . . . . . . . . . . . . . . . . 1165M    8.2.10.2 Changeable values . . . . . . . . . . . . . . . . . . . . . . 1165M    8.2.10.3 Default values. . . . . . . . . . . . . . . . . . . . . . . . 1165M    8.2.10.4 Saved values. . . . . . . . . . . . . . . . . . . . . . . . . 1165M    8.2.10.5 Initial responses . . . . . . . . . . . . . . . . . . . . . . 1175M    8.2.11 MODE SENSE(10) command. . . . . . . . . . . . . . . . . . . . . 1175M    8.2.12 READ BUFFER Command . . . . . . . . . . . . . . . . . . . . . . 118 M    8.2.12.1 Combined header and data mode (000b). . . . . . . . . . . . . 118 M    8.2.12.2 Vendor-specific mode (001b) . . . . . . . . . . . . . . . . . 119 M    8.2.12.3 Data mode (010b). . . . . . . . . . . . . . . . . . . . . . . 119 M    8.2.12.4 Descriptor mode (011b). . . . . . . . . . . . . . . . . . . . 119 M    8.2.13 RECEIVE DIAGNOSTIC RESULTS command. . . . . . . . . . . . . . . 121 M    8.2.14 REQUEST SENSE Command . . . . . . . . . . . . . . . . . . . . . 122 M    8.2.14.1 Sense-key specific. . . . . . . . . . . . . . . . . . . . . . 125 M    8.2.14.2 Deferred errors . . . . . . . . . . . . . . . . . . . . . . . 126 M    8.2.14.3 Sense key and sense code definitions. . . . . . . . . . . . . 128 M    8.2.15 SEND DIAGNOSTIC Command . . . . . . . . . . . . . . . . . . . . 134 M    8.2.16 TEST UNIT READY Command . . . . . . . . . . . . . . . . . . . . 135 M    8.2.17 WRITE BUFFER command. . . . . . . . . . . . . . . . . . . . . . 136 M    8.2.17.1 Combined header and data mode (000b). . . . . . . . . . . . . 137 M    8.2.17.2 Vendor-specific mode (001b) . . . . . . . . . . . . . . . . . 137 M    8.2.17.3 Data mode (010b). . . . . . . . . . . . . . . . . . . . . . . 137 M    8.2.17.4 Download microcode mode (100b). . . . . . . . . . . . . . . . 138 M    8.2.17.5 Download microcode and save mode (101b) . . . . . . . . . . . 138 M    8.3 Parameters for all device types. . . . . . . . . . . . . . . . . . 138 M    8.3.1 Diagnostic parameters  . . . . . . . . . . . . . . . . . . . . . 138 M    8.3.1.1 Supported diagnostic pages . . . . . . . . . . . . . . . . . . 139 M    8.3.2 Log parameters . . . . . . . . . . . . . . . . . . . . . . . . . 140 M    8.3.2.1 Buffer over-run/under-run page . . . . . . . . . . . . . . . . 143 M    8.3.2.2 Error counter pages. . . . . . . . . . . . . . . . . . . . . . 144 M    8.3.2.3 Last n error events page . . . . . . . . . . . . . . . . . . . 145 M    8.3.2.4 Non-medium error page  . . . . . . . . . . . . . . . . . . . . 145 M    8.3.2.5 Supported log pages. . . . . . . . . . . . . . . . . . . . . . 145 M    8.3.3 Mode parameters. . . . . . . . . . . . . . . . . . . . . . . . . 146 M    8.3.3.1 Control mode page. . . . . . . . . . . . . . . . . . . . . . . 149 M    8.3.3.2 Disconnect-reconnect page. . . . . . . . . . . . . . . . . . . 152 M    8.3.3.3 Peripheral device page . . . . . . . . . . . . . . . . . . . . 154 M    8.3.4 Vital product data parameters. . . . . . . . . . . . . . . . . . 154 M    8.3.4.1 ASCII implemented operating definition page. . . . . . . . . . 155 M    8.3.4.2 ASCII information page . . . . . . . . . . . . . . . . . . . . 156 M    8.3.4.3 Implemented operating definition page. . . . . . . . . . . . . 156 M    8.3.4.4 Supported vital product data pages . . . . . . . . . . . . . . 158 M    8.3.4.5 Unit serial number page. . . . . . . . . . . . . . . . . . . . 159   M 9 Direct-access devices . . . . . . . . . . . . . . . . . . . . . . . . . 1616M    9.1 Direct-access device model . . . . . . . . . . . . . . . . . . . . 1616M    9.1.1 Removable medium . . . . . . . . . . . . . . . . . . . . . . . . 1616M    9.1.2 Logical blocks . . . . . . . . . . . . . . . . . . . . . . . . . 1616M    9.1.3 Ready state. . . . . . . . . . . . . . . . . . . . . . . . . . . 1626M    9.1.4 Initialization . . . . . . . . . . . . . . . . . . . . . . . . . 1626M    9.1.5 Medium defects . . . . . . . . . . . . . . . . . . . . . . . . . 1626M    9.1.6 Data cache . . . . . . . . . . . . . . . . . . . . . . . . . . . 1636M    9.1.7 Reservations . . . . . . . . . . . . . . . . . . . . . . . . . . 1646M    9.1.8 Seek and rezero. . . . . . . . . . . . . . . . . . . . . . . . . 1656M    9.1.9 Notched drives . . . . . . . . . . . . . . . . . . . . . . . . . 1656M    9.1.10 Rotational position locking . . . . . . . . . . . . . . . . . . 1656M    9.1.11 Relative addressing . . . . . . . . . . . . . . . . . . . . . . 1656M    9.1.12 Error reporting . . . . . . . . . . . . . . . . . . . . . . . . 1666M    9.1.13 Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1666M    9.1.13.1 Rotating media. . . . . . . . . . . . . . . . . . . . . . . . 1666M    9.1.13.2 Sequential media. . . . . . . . . . . . . . . . . . . . . . . 1676M    9.1.13.3 Memory media. . . . . . . . . . . . . . . . . . . . . . . . . 1676M    9.2 Commands for direct-access devices.. . . . . . . . . . . . . . . . 1686M    9.2.1 FORMAT UNIT command. . . . . . . . . . . . . . . . . . . . . . . 1696M    9.2.1.1 Defect list formats. . . . . . . . . . . . . . . . . . . . . . 174 M    9.2.1.2 Initialization pattern option. . . . . . . . . . . . . . . . . 175 M    9.2.2 LOCK UNLOCK CACHE command. . . . . . . . . . . . . . . . . . . . 177 M    9.2.3 PRE-FETCH command. . . . . . . . . . . . . . . . . . . . . . . . 178 M    9.2.4 PREVENT ALLOW MEDIUM REMOVAL command . . . . . . . . . . . . . . 179 M    9.2.5 READ(6) command. . . . . . . . . . . . . . . . . . . . . . . . . 180 M    9.2.6 READ(10) command . . . . . . . . . . . . . . . . . . . . . . . . 181 M    9.2.7 READ CAPACITY command. . . . . . . . . . . . . . . . . . . . . . 182 M    9.2.8 READ DEFECT DATA command . . . . . . . . . . . . . . . . . . . . 183 M    9.2.9 READ LONG command. . . . . . . . . . . . . . . . . . . . . . . . 185 M    9.2.10 REASSIGN BLOCKS command . . . . . . . . . . . . . . . . . . . . 186 M    9.2.11 RELEASE command . . . . . . . . . . . . . . . . . . . . . . . . 187 M    9.2.11.1 Logical unit release. . . . . . . . . . . . . . . . . . . . . 188 M    9.2.11.2 Extent release. . . . . . . . . . . . . . . . . . . . . . . . 188 M    9.2.11.3 Third-party release . . . . . . . . . . . . . . . . . . . . . 188 M    9.2.12 RESERVE command . . . . . . . . . . . . . . . . . . . . . . . . 189 M    9.2.12.1 Logical unit reservation. . . . . . . . . . . . . . . . . . . 189 M    9.2.12.2 Extent reservation. . . . . . . . . . . . . . . . . . . . . . 189 M    9.2.12.3 Third-party reservation . . . . . . . . . . . . . . . . . . . 191 M    9.2.12.4 Superseding reservations. . . . . . . . . . . . . . . . . . . 192 M    9.2.13 REZERO UNIT command . . . . . . . . . . . . . . . . . . . . . . 192 M    9.2.14 SEARCH DATA commands. . . . . . . . . . . . . . . . . . . . . . 193 M    9.2.14.1 SEARCH DATA EQUAL command . . . . . . . . . . . . . . . . . . 195 M    9.2.14.2 SEARCH DATA HIGH command. . . . . . . . . . . . . . . . . . . 195 M    9.2.14.3 SEARCH DATA LOW command . . . . . . . . . . . . . . . . . . . 195 M    9.2.15 SEEK(6) and SEEK(10) commands . . . . . . . . . . . . . . . . . 196 M    9.2.16 SET LIMITS command. . . . . . . . . . . . . . . . . . . . . . . 197 M    9.2.17 START STOP UNIT command . . . . . . . . . . . . . . . . . . . . 198 M    9.2.18 SYNCHRONIZE CACHE command . . . . . . . . . . . . . . . . . . . 199 M    9.2.19 VERIFY command. . . . . . . . . . . . . . . . . . . . . . . . . 200 M    9.2.20 WRITE(6) command. . . . . . . . . . . . . . . . . . . . . . . . 201 M    9.2.21 WRITE(10) command . . . . . . . . . . . . . . . . . . . . . . . 202 M    9.2.22 WRITE AND VERIFY command. . . . . . . . . . . . . . . . . . . . 203 M    9.2.23 WRITE LONG command. . . . . . . . . . . . . . . . . . . . . . . 204 M    9.2.24 WRITE SAME command. . . . . . . . . . . . . . . . . . . . . . . 205 M    9.3 Parameters for direct-access devices . . . . . . . . . . . . . . . 206 M    9.3.1 Diagnostic parameters. . . . . . . . . . . . . . . . . . . . . . 206 M    9.3.1.1 Translate address page - SEND DIAGNOSTIC . . . . . . . . . . . 206 M    9.3.1.2 Translate address page - RECEIVE DIAGNOSTIC  . . . . . . . . . 207 M    9.3.2 Log parameters . . . . . . . . . . . . . . . . . . . . . . . . . 208 M    9.3.3 Mode parameters. . . . . . . . . . . . . . . . . . . . . . . . . 208 M    9.3.3.1 Caching page . . . . . . . . . . . . . . . . . . . . . . . . . 210 M    9.3.3.2 Flexible disk page . . . . . . . . . . . . . . . . . . . . . . 213 M    9.3.3.3 Format device page . . . . . . . . . . . . . . . . . . . . . . 216 M    9.3.3.4 Medium types supported page. . . . . . . . . . . . . . . . . . 219 M    9.3.3.5 Notch and partition page . . . . . . . . . . . . . . . . . . . 220 M    9.3.3.6 Read-write error recovery page . . . . . . . . . . . . . . . . 222 M    9.3.3.7 Rigid disk drive geometry page . . . . . . . . . . . . . . . . 229 M    9.3.3.8 Verify error recovery page . . . . . . . . . . . . . . . . . . 231 M    9.4 Definitions specific to direct-access devices. . . . . . . . . . . 232   M 10 Sequential-access devices. . . . . . . . . . . . . . . . . . . . . . . 233 M    10.1 Sequential-access device model. . . . . . . . . . . . . . . . . . 233 M    10.1.1 Physical elements . . . . . . . . . . . . . . . . . . . . . . . 233 M    10.1.2 Data storage characteristics. . . . . . . . . . . . . . . . . . 234 M    10.1.3 Partitions within a volume. . . . . . . . . . . . . . . . . . . 236 M    10.1.4 Logical elements within a partition . . . . . . . . . . . . . . 237 M    10.1.5 Data buffering. . . . . . . . . . . . . . . . . . . . . . . . . 238 M    10.1.6 Recorded object descriptors (block identifiers) . . . . . . . . 239 M    10.1.7 Direction and position definitions. . . . . . . . . . . . . . . 239 M    10.1.8 Error reporting . . . . . . . . . . . . . . . . . . . . . . . . 240 M    10.2 Command descriptions for sequential-access devices. . . . . . . . 241 M    10.2.1 ERASE command . . . . . . . . . . . . . . . . . . . . . . . . . 243 M    10.2.2 LOAD UNLOAD command . . . . . . . . . . . . . . . . . . . . . . 244 M    10.2.3 LOCATE command. . . . . . . . . . . . . . . . . . . . . . . . . 245 M    10.2.4 READ command. . . . . . . . . . . . . . . . . . . . . . . . . . 246 M    10.2.5 READ BLOCK LIMITS command . . . . . . . . . . . . . . . . . . . 248 M    10.2.6 READ POSITION command . . . . . . . . . . . . . . . . . . . . . 249 M    10.2.7 READ REVERSE command. . . . . . . . . . . . . . . . . . . . . . 251 M    10.2.8 RECOVER BUFFERED DATA command . . . . . . . . . . . . . . . . . 252 M    10.2.9 RELEASE UNIT command. . . . . . . . . . . . . . . . . . . . . . 253 M    10.2.9.1 Third-party release . . . . . . . . . . . . . . . . . . . . . 253 M    10.2.10 RESERVE UNIT command . . . . . . . . . . . . . . . . . . . . . 254 M    10.2.10.1 Third-party reservation. . . . . . . . . . . . . . . . . . . 254 M    10.2.10.2 Superseding reservations . . . . . . . . . . . . . . . . . . 255 M    10.2.11 REWIND command . . . . . . . . . . . . . . . . . . . . . . . . 255 M    10.2.12 SPACE command. . . . . . . . . . . . . . . . . . . . . . . . . 256 M    10.2.13 VERIFY command . . . . . . . . . . . . . . . . . . . . . . . . 258 M    10.2.14 WRITE command. . . . . . . . . . . . . . . . . . . . . . . . . 259 M    10.2.15 WRITE FILEMARKS command. . . . . . . . . . . . . . . . . . . . 261 M    10.3 Parameters for sequential-access devices. . . . . . . . . . . . . 262 M    10.3.1 Diagnostic parameters . . . . . . . . . . . . . . . . . . . . . 262 M    10.3.2 Log parameters. . . . . . . . . . . . . . . . . . . . . . . . . 262 M    10.3.3 Mode parameters . . . . . . . . . . . . . . . . . . . . . . . . 263 M    10.3.3.1 Device configuration page . . . . . . . . . . . . . . . . . . 266 M    10.3.3.2 Medium partition page(1). . . . . . . . . . . . . . . . . . . 269 M    10.3.3.3 Medium partition page(2-4). . . . . . . . . . . . . . . . . . 270 M    10.3.3.4 Read-write error recovery page. . . . . . . . . . . . . . . . 270 M    10.4 Definitions specific to sequential access devices . . . . . . . . 272   M 11 Commands for printer devices . . . . . . . . . . . . . . . . . . . . . 2738M    11.1 Model for printer devices . . . . . . . . . . . . . . . . . . . . 2738M    11.2 Commands for printer devices. . . . . . . . . . . . . . . . . . . 2748M    11.2.1 FORMAT command. . . . . . . . . . . . . . . . . . . . . . . . . 2758M    11.2.2 PRINT command . . . . . . . . . . . . . . . . . . . . . . . . . 2768M    11.2.3 RECOVER BUFFERED DATA command . . . . . . . . . . . . . . . . . 2768M    11.2.4 SLEW AND PRINT command. . . . . . . . . . . . . . . . . . . . . 2778M    11.2.5 STOP PRINT command. . . . . . . . . . . . . . . . . . . . . . . 2788M    11.2.6 SYNCHRONIZE BUFFER command. . . . . . . . . . . . . . . . . . . 2788M    11.3 Parameters for printer devices. . . . . . . . . . . . . . . . . . 2798M    11.3.1 Diagnostic parameters . . . . . . . . . . . . . . . . . . . . . 2798M    11.3.2 Log parameters. . . . . . . . . . . . . . . . . . . . . . . . . 2798M    11.3.3 Mode parameters . . . . . . . . . . . . . . . . . . . . . . . . 2798M    11.3.3.1 Parallel printer interface page . . . . . . . . . . . . . . . 2808M    11.3.3.2 Printer options page. . . . . . . . . . . . . . . . . . . . . 2828M    11.3.3.3 Serial printer interface page . . . . . . . . . . . . . . . . 2858  M 12 Processor devices. . . . . . . . . . . . . . . . . . . . . . . . . . . 2873M    12.1 Model for processor devices . . . . . . . . . . . . . . . . . . . 2873M    12.1.1 Host-to-host communication, SEND only . . . . . . . . . . . . . 2883M    12.1.2 Host-to-host communication, SEND and RECEIVE. . . . . . . . . . 288iM    12.1.3 Host-to-special-output peripheral . . . . . . . . . . . . . . . 2889M    12.1.4 Host-to-special-input peripheral. . . . . . . . . . . . . . . . 2889M    12.2 Commands for processor devices. . . . . . . . . . . . . . . . . . 2899M    12.2.1 RECEIVE command . . . . . . . . . . . . . . . . . . . . . . . . 2899M    12.2.2 SEND command. . . . . . . . . . . . . . . . . . . . . . . . . . 2909M    12.3 Parameters for processor devices. . . . . . . . . . . . . . . . . 2919M    12.3.1 Diagnostic parameters . . . . . . . . . . . . . . . . . . . . . 2919M    12.3.2 Log parameters. . . . . . . . . . . . . . . . . . . . . . . . . 2919M    12.4 Definitions specific to processor devices . . . . . . . . . . . . 2929  M 13 Write-once devices . . . . . . . . . . . . . . . . . . . . . . . . . . 2931M    13.1 Model for write-once devices. . . . . . . . . . . . . . . . . . . 2931M    13.1.1 Logical blocks. . . . . . . . . . . . . . . . . . . . . . . . . 2931M    13.1.2 Initialization. . . . . . . . . . . . . . . . . . . . . . . . . 2931M    13.1.3 Physical medium defects . . . . . . . . . . . . . . . . . . . . 2931M    13.1.4 Error reporting . . . . . . . . . . . . . . . . . . . . . . . . 2931M    13.2 Commands for write-once devices . . . . . . . . . . . . . . . . . 2941M    13.3 Parameters for write-once devices . . . . . . . . . . . . . . . . 2961M    13.4 Definitions specific to write-once devices. . . . . . . . . . . . 2962  M 14 CD-ROM devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2971M    14.1 Model for CD-ROM devices. . . . . . . . . . . . . . . . . . . . . 2971M    14.1.1 CD-ROM media organization . . . . . . . . . . . . . . . . . . . 2971M    14.1.2 CD-ROM physical data format . . . . . . . . . . . . . . . . . . 3002M    14.1.2.1 Frame format for audio. . . . . . . . . . . . . . . . . . . . 3003M    14.1.2.2 Sector format for data. . . . . . . . . . . . . . . . . . . . 3014M    14.1.2.3 Sub-channel information formats . . . . . . . . . . . . . . . 3015M    14.1.3 CD Audio error reporting. . . . . . . . . . . . . . . . . . . . 3026M    14.1.4 CD-ROM ready condition/not ready condition. . . . . . . . . . . 3027M    14.1.5 CD-ROM address reporting formats (MSF bit). . . . . . . . . . . 3038M    14.1.6 Sensing support for CD-audio commands.. . . . . . . . . . . . . 3039M    14.1.7 Error reporting . . . . . . . . . . . . . . . . . . . . . . . . 3031M    14.2 Commands for CD-ROM devices . . . . . . . . . . . . . . . . . . . 3051M    14.2.1 PAUSE RESUME command. . . . . . . . . . . . . . . . . . . . . . 3061M    14.2.2 PLAY AUDIO(10) command. . . . . . . . . . . . . . . . . . . . . 3071M    14.2.3 PLAY AUDIO(12) command  . . . . . . . . . . . . . . . . . . . . 3081M    14.2.4 PLAY AUDIO MSF command. . . . . . . . . . . . . . . . . . . . . 3091M    14.2.5 PLAY AUDIO TRACK INDEX command. . . . . . . . . . . . . . . . . 3101M    14.2.6 PLAY AUDIO TRACK RELATIVE(10) command . . . . . . . . . . . . . 3111M    14.2.7 PLAY AUDIO TRACK RELATIVE(12) command . . . . . . . . . . . . . 3121M    14.2.8 READ CD-ROM CAPACITY command. . . . . . . . . . . . . . . . . . 3131M    14.2.9 READ HEADER command . . . . . . . . . . . . . . . . . . . . . . 3141M    14.2.10 READ SUB-CHANNEL command . . . . . . . . . . . . . . . . . . . 3161M    14.2.10.1 Sub-Q channel data format. . . . . . . . . . . . . . . . . . 3171M    14.2.10.2 CD-ROM current position data format. . . . . . . . . . . . . 3201M    14.2.10.3 Media catalogue number data format . . . . . . . . . . . . . 3201M    14.2.10.4 Track international standard recording code data format. . . 3211M    14.2.11 READ TOC command . . . . . . . . . . . . . . . . . . . . . . . 3231M    14.3 Parameters for CD-ROM devices . . . . . . . . . . . . . . . . . . 3251M    14.3.1 Diagnostic parameters . . . . . . . . . . . . . . . . . . . . . 3251M    14.3.2 Log parameters. . . . . . . . . . . . . . . . . . . . . . . . . 3251M    14.3.3 Mode parameters . . . . . . . . . . . . . . . . . . . . . . . . 3252M    14.3.3.1 CD-ROM audio control parameters . . . . . . . . . . . . . . . 3272M    14.3.3.2 CD-ROM device parameters  . . . . . . . . . . . . . . . . . . 3292M    14.3.3.3 Read error recovery parameters  . . . . . . . . . . . . . . . 3302M    14.3.3.4 Verify error recovery parameters. . . . . . . . . . . . . . . 3362M    14.4 Definitions specific to CD-ROM devices. . . . . . . . . . . . . . 336P  M 15 Scanner devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . 339DM    15.1 Model for scanner devices . . . . . . . . . . . . . . . . . . . . 3391M    15.2 Commands for scanner devices. . . . . . . . . . . . . . . . . . . 3402M    15.2.1 GET DATA BUFFER STATUS command. . . . . . . . . . . . . . . . . 341LM    15.2.2 GET WINDOW command. . . . . . . . . . . . . . . . . . . . . . . 343MM    15.2.3 OBJECT POSITION command . . . . . . . . . . . . . . . . . . . . 3471M    15.2.4 READ command. . . . . . . . . . . . . . . . . . . . . . . . . . 3492M    15.2.5 SCAN command. . . . . . . . . . . . . . . . . . . . . . . . . . 3503M    15.2.6 SEND command. . . . . . . . . . . . . . . . . . . . . . . . . . 3504M    15.2.7 SET WINDOW command. . . . . . . . . . . . . . . . . . . . . . . 3515M    15.3 Parameters for scanner devices. . . . . . . . . . . . . . . . . . 3526M    15.3.1 Diagnostic parameters . . . . . . . . . . . . . . . . . . . . . 3527M    15.3.2 Log parameters. . . . . . . . . . . . . . . . . . . . . . . . . 3528M    15.3.3 Mode parameters . . . . . . . . . . . . . . . . . . . . . . . . 353fM    15.3.3.1 Measurement units page. . . . . . . . . . . . . . . . . . . . 353eM    15.4 Definitions specific to scanner devices . . . . . . . . . . . . . 355   M 16  Optical memory devices. . . . . . . . . . . . . . . . . . . . . . . . 357 M    16.1 Model for optical memory devices. . . . . . . . . . . . . . . . . 357 M    16.1.1 Defect management . . . . . . . . . . . . . . . . . . . . . . . 358 M    16.1.2 Error reporting . . . . . . . . . . . . . . . . . . . . . . . . 358 M    16.2 Commands for optical memory devices . . . . . . . . . . . . . . . 359 M    16.2.1 ERASE(10) command . . . . . . . . . . . . . . . . . . . . . . . 360 M    16.2.2 ERASE(12) command . . . . . . . . . . . . . . . . . . . . . . . 361 M    16.2.3 MEDIUM SCAN command . . . . . . . . . . . . . . . . . . . . . . 362 M    16.2.4 READ(12) command. . . . . . . . . . . . . . . . . . . . . . . . 364oM    16.2.5 READ DEFECT DATA(12) command. . . . . . . . . . . . . . . . . . 364 M    16.2.6 READ GENERATION command . . . . . . . . . . . . . . . . . . . . 366 M    16.2.7 READ UPDATED BLOCK(10) command. . . . . . . . . . . . . . . . . 367 M    16.2.8 SEARCH DATA(12) commands. . . . . . . . . . . . . . . . . . . . 368 M    16.2.9 SET LIMITS(12) command. . . . . . . . . . . . . . . . . . . . . 368 M    16.2.10 UPDATE BLOCK command . . . . . . . . . . . . . . . . . . . . . 369 M    16.2.11 VERIFY(10) command . . . . . . . . . . . . . . . . . . . . . . 370 M    16.2.12 VERIFY(12) command . . . . . . . . . . . . . . . . . . . . . . 371 M    16.2.13 WRITE(10) command. . . . . . . . . . . . . . . . . . . . . . . 372 M    16.2.14 WRITE(12) command. . . . . . . . . . . . . . . . . . . . . . . 373.M    16.2.15 WRITE AND VERIFY(10) command . . . . . . . . . . . . . . . . . 3730M    16.2.16 WRITE AND VERIFY(12) command . . . . . . . . . . . . . . . . . 3740M    16.3 Parameters for optical memory devices . . . . . . . . . . . . . . 3750M    16.3.1 Diagnostic parameters . . . . . . . . . . . . . . . . . . . . . 3751M    16.3.2 Log parameters. . . . . . . . . . . . . . . . . . . . . . . . . 3752M    16.3.3 Mode parameters . . . . . . . . . . . . . . . . . . . . . . . . 3753M    16.3.3.1 Optical memory page . . . . . . . . . . . . . . . . . . . . . 3784M    16.4 Definitions specific to write-once and optical memory devices . . 3785  M 17 Medium-changer devices . . . . . . . . . . . . . . . . . . . . . . . . 379aM    17.1 Medium-changer device model . . . . . . . . . . . . . . . . . . . 379iM    17.1.1 Medium-changer elements . . . . . . . . . . . . . . . . . . . . 379oM    17.1.1.1 Medium transport elements . . . . . . . . . . . . . . . . . . 379oM    17.1.1.2 Storage elements. . . . . . . . . . . . . . . . . . . . . . . 380 M    17.1.1.3 Import export elements. . . . . . . . . . . . . . . . . . . . 380 M    17.1.1.4 Data transfer element . . . . . . . . . . . . . . . . . . . . 380 M    17.1.2 SCSI addressing of medium changer devices . . . . . . . . . . . 381 M    17.1.3 Data access operations using a medium changer device. . . . . . 381iM    17.1.4 Element status maintenance requirements . . . . . . . . . . . . 381dM    17.1.5 Volume tags . . . . . . . . . . . . . . . . . . . . . . . . . . 381oM    17.1.5.1 Volume tag format . . . . . . . . . . . . . . . . . . . . . . 382oM    17.1.5.2 Primary and alternate volume tag information. . . . . . . . . 382 M    17.2 Commands for medium changer devices . . . . . . . . . . . . . . . 383 M    17.2.1 EXCHANGE MEDIUM command . . . . . . . . . . . . . . . . . . . . 384 M    17.2.2 INITIALIZE ELEMENT STATUS command . . . . . . . . . . . . . . . 385 M    17.2.3 MOVE MEDIUM command . . . . . . . . . . . . . . . . . . . . . . 386 M    17.2.4 POSITION TO ELEMENT command . . . . . . . . . . . . . . . . . . 387 M    17.2.5 READ ELEMENT STATUS command . . . . . . . . . . . . . . . . . . 388aM    17.2.5.1 Element status data . . . . . . . . . . . . . . . . . . . . . 389 M    17.2.5.2 Element status page . . . . . . . . . . . . . . . . . . . . . 391 M    17.2.5.3 Medium transport element descriptor . . . . . . . . . . . . . 392 M    17.2.5.4 Storage element descriptor. . . . . . . . . . . . . . . . . . 393.M    17.2.5.5 Import export element descriptor. . . . . . . . . . . . . . . 394.M    17.2.5.6 Data transfer element descriptor. . . . . . . . . . . . . . . 395.M    17.2.6 REQUEST VOLUME ELEMENT ADDRESS command. . . . . . . . . . . . . 396eM    17.2.7 RELEASE command . . . . . . . . . . . . . . . . . . . . . . . . 398 M    17.2.7.1 Logical unit release. . . . . . . . . . . . . . . . . . . . . 398.M    17.2.7.2 Element release (optional). . . . . . . . . . . . . . . . . . 398.M    17.2.7.3 Third party release . . . . . . . . . . . . . . . . . . . . . 398.M    17.2.8 RESERVE command . . . . . . . . . . . . . . . . . . . . . . . . 399.M    17.2.8.1 Logical unit reservation. . . . . . . . . . . . . . . . . . . 399 M    17.2.8.2 Element reservation (optional). . . . . . . . . . . . . . . . 399.M    17.2.8.3 Third party reservation . . . . . . . . . . . . . . . . . . . 400.M    17.2.8.4 Superseding reservations. . . . . . . . . . . . . . . . . . . 401 M    17.2.9 SEND VOLUME TAG command . . . . . . . . . . . . . . . . . . . . 401.M    17.3 Parameters for medium changer devices . . . . . . . . . . . . . . 404.M    17.3.1 Diagnostic parameters . . . . . . . . . . . . . . . . . . . . . 404 M    17.3.2 Log parameters. . . . . . . . . . . . . . . . . . . . . . . . . 404iM    17.3.3 Mode parameters . . . . . . . . . . . . . . . . . . . . . . . . 404.M    17.3.3.1 Device capabilities page. . . . . . . . . . . . . . . . . . . 405.M    17.3.3.2 Element address assignment page . . . . . . . . . . . . . . . 406.M    17.3.3.3 Transport geometry parameters page. . . . . . . . . . . . . . 409.M    17.4 Definitions specific to medium changer devices. . . . . . . . . . 410.  M 18 Communications devices . . . . . . . . . . . . . . . . . . . . . . . . 411 M    18.1 Communications device model . . . . . . . . . . . . . . . . . . . 411 M    18.1.1 Implementation examples . . . . . . . . . . . . . . . . . . . . 412 M    18.1.1.1 Host-to-host communications . . . . . . . . . . . . . . . . . 412-M    18.1.1.2 Host-to-device communications . . . . . . . . . . . . . . . . 412.M    18.1.1.3 Multiple role communications  . . . . . . . . . . . . . . . . 413.M    18.2 Command descriptions for communications devices . . . . . . . . . 413.M    18.2.1 GET MESSAGE(6) command. . . . . . . . . . . . . . . . . . . . . 414.M    18.2.2 GET MESSAGE(10) command . . . . . . . . . . . . . . . . . . . . 414.M    18.2.3 GET MESSAGE(12) command . . . . . . . . . . . . . . . . . . . . 415.M    18.2.4 SEND MESSAGE(6) command . . . . . . . . . . . . . . . . . . . . 416.M    18.2.5 SEND MESSAGE(10) command. . . . . . . . . . . . . . . . . . . . 416.M    18.2.6 SEND MESSAGE(12) command. . . . . . . . . . . . . . . . . . . . 417.M    18.3 Parameters for communication devices. . . . . . . . . . . . . . . 418.M    18.3.1 Diagnostic parameters . . . . . . . . . . . . . . . . . . . . . 418.M    18.3.2 Log parameters. . . . . . . . . . . . . . . . . . . . . . . . . 418.M    18.3.3 Mode parameters . . . . . . . . . . . . . . . . . . . . . . . . 418.M    18.4 Definitions specific to communications devices. . . . . . . . . . 419.M    C.1 SCSI-3 standards projects. . . . . . . . . . . . . . . . . . . . . 427.M    C.2 Digital data exchange for colour electronic prepress systems . . . 427.M    C.3 Fibre channel. . . . . . . . . . . . . . . . . . . . . . . . . . . 427.  M Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443.       AnnexesAM                                                                          PageAM Annex A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421AM SCSI signal sequence example. . . . . . . . . . . . . . . . . . . . . . . 421o  M Annex B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425EM Fast SCSI skew time . . . . . . . . . . . . . . . . . . . . . . . . . . . 425l  M Annex C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427 M Other SCSI standardization activities . . . . . . . . . . . . . . . . . . 427e  M Annex D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429nM Numeric order codes . . . . . . . . . . . . . . . . . . . . . . . . . . . 429   M Annex E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439eM Vendor identification . . . . . . . . . . . . . . . . . . . . . . . . . . 439      Figures M                                                                          Page > Figure 1 - 50/68-contact non-shielded high-density SCSI deviceM    connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  12rM Figure 2 - 50/68-contact non-shielded high-density cable connector. . . .  13aM Figure 3 - 50-contact non-shielded low-density SCSI device connector. . .  14rM Figure 4 - 50-Contact non-shielded low-density cable connector. . . . . .  15vM Figure 5 - 50/68-contact shielded high-density SCSI device connector. . .  17tM Figure 6 - 50/68-contact shielded high-density cable connector. . . . . .  18 M Figure 7 - 50-contact shielded low-density SCSI device connector. . . . .  19eM Figure 8 - 50-contact shielded low-density cable connector. . . . . . . .  20rM Figure 9 - Alternative 1 termination. . . . . . . . . . . . . . . . . . .  29TM Figure 10 - Alternative 2 termination for single-ended devices. . . . . .  29dM Figure 11 - Termination for differential devices. . . . . . . . . . . . .  30oM Figure 12 - Differential driver protection circuit. . . . . . . . . . . .  30 M Figure 13 - SCSI ID bits. . . . . . . . . . . . . . . . . . . . . . . . .  31 M Figure 14 - Sample SCSI configurations. . . . . . . . . . . . . . . . . .  32 M Figure 15 - Wide SCSI byte ordering . . . . . . . . . . . . . . . . . . .  47dM Figure 16 - Phase sequences . . . . . . . . . . . . . . . . . . . . . . .  53nM Figure 17 - Simplified SCSI system. . . . . . . . . . . . . . . . . . . .  54tM Figure 18 - Typical volume layout . . . . . . . . . . . . . . . . . . . . 234 M Figure 19 - Typical medium track layout . . . . . . . . . . . . . . . . . 234 M Figure 20 - Serpentine recording example  . . . . . . . . . . . . . . . . 234tM Figure 21 - Parallel recording example. . . . . . . . . . . . . . . . . . 235cM Figure 22 - Helical scan recording example. . . . . . . . . . . . . . . . 235sM Figure 23 - Early-warning example . . . . . . . . . . . . . . . . . . . . 235 M Figure 24 - Partitioning example - one partition per track group. . . . . 236nM Figure 25 - Partitioning example - one partition per two track groups . . 236 M Figure 26 - Partitioning example - two partitions per track group . . . . 237cM Figure 27 - SCSI printer model. . . . . . . . . . . . . . . . . . . . . . 273nM Figure 28 - Illustration of element status data structure . . . . . . . . 390nM Figure A.1 - SCSI signal sequence example . . . . . . . . . . . . . . . . 424mM Figure C.1 - SCSI-3 standards structure . . . . . . . . . . . . . . . . . 427d         TablesM                                                                          Page M Table 1 - Cross-reference to connector contact assignments. . . . . . . .  21 M Table 2 - Single-ended contact assignments - A cable. . . . . . . . . . .  21 M Table 3 - Single-ended contact assignments - B cable. . . . . . . . . . .  22 M Table 4 - Differential contact assignments - A cable. . . . . . . . . . .  23 M Table 5 - Differential contact assignments - B cable. . . . . . . . . . .  24 M Table 6 - Signal sources. . . . . . . . . . . . . . . . . . . . . . . . .  34 M Table 7 - SCSI bus timing values. . . . . . . . . . . . . . . . . . . . .  36 M Table 8 - Information transfer phases . . . . . . . . . . . . . . . . . .  45 M Table 9 - Message format. . . . . . . . . . . . . . . . . . . . . . . . .  55 M Table 10 - Message codes. . . . . . . . . . . . . . . . . . . . . . . . .  55 M Table 11 - Extended message format. . . . . . . . . . . . . . . . . . . .  57 M Table 12 - Extended message codes . . . . . . . . . . . . . . . . . . . .  57iM Table 13 - IDENTIFY message format. . . . . . . . . . . . . . . . . . . .  60 M Table 14 - IGNORE WIDE RESIDUE message format . . . . . . . . . . . . . .  61 M Table 15 - Ignore field definition. . . . . . . . . . . . . . . . . . . .  61 M Table 16 - MODIFY DATA POINTER. . . . . . . . . . . . . . . . . . . . . .  63 M Table 17 - Queue tag message format . . . . . . . . . . . . . . . . . . .  63eM Table 18 - SYNCHRONOUS DATA TRANSFER REQUEST. . . . . . . . . . . . . . .  65 M Table 19 - WIDE DATA TRANSFER MESSAGE . . . . . . . . . . . . . . . . . .  67 M Table 20 - Operation code type. . . . . . . . . . . . . . . . . . . . . .  71 M Table 21 - Typical command descriptor block for six-byte commands . . . .  72 M Table 22 - Typical command descriptor block for ten-byte commands . . . .  72 M Table 23 - Typical command descriptor block for twelve-byte commands. . .  72 M Table 24 - Operation code . . . . . . . . . . . . . . . . . . . . . . . .  74 M Table 25 - Control field. . . . . . . . . . . . . . . . . . . . . . . . .  75nM Table 26 - Status byte. . . . . . . . . . . . . . . . . . . . . . . . . .  76aM Table 27 - Status byte code . . . . . . . . . . . . . . . . . . . . . . .  76qM Table 28 - Commands in order received by target . . . . . . . . . . . . .  86 M Table 29 - Commands in order of execution . . . . . . . . . . . . . . . .  87 M Table 30 - Modified by HEAD OF QUEUE TAG message. . . . . . . . . . . . .  87eM Table 31 - Commands for all device types. . . . . . . . . . . . . . . . .  92iM Table 32 - CHANGE DEFINITION command. . . . . . . . . . . . . . . . . . .  93 M Table 33 - Definition parameter field . . . . . . . . . . . . . . . . . .  94mM Table 34 - COMPARE command. . . . . . . . . . . . . . . . . . . . . . . .  95 M Table 35 - COPY command . . . . . . . . . . . . . . . . . . . . . . . . .  96 M Table 36 - COPY parameter list. . . . . . . . . . . . . . . . . . . . . .  96 M Table 37 - COPY function codes. . . . . . . . . . . . . . . . . . . . . .  97 M Table 38 - Segment descriptor for COPY function codes 00h and 01h . . . .  99 M Table 39 - Segment descriptor for COPY function code 02h. . . . . . . . . 100sM Table 40 - Segment descriptor for COPY function code 03h. . . . . . . . . 100 M Table 41 - Segment descriptor for COPY function code 04h. . . . . . . . . 102iM Table 42 - Pad and cat bit definition . . . . . . . . . . . . . . . . . . 102iM Table 43 - COPY AND VERIFY command. . . . . . . . . . . . . . . . . . . . 103SM Table 44 - INQUIRY command. . . . . . . . . . . . . . . . . . . . . . . . 104 M Table 45 - Standard INQUIRY data format . . . . . . . . . . . . . . . . . 105 M Table 46 - Peripheral qualifier . . . . . . . . . . . . . . . . . . . . . 105 M Table 47 - Peripheral device type . . . . . . . . . . . . . . . . . . . . 106 M Table 48 - ANSI-approved version. . . . . . . . . . . . . . . . . . . . . 107 M Table 49 - LOG SELECT command . . . . . . . . . . . . . . . . . . . . . . 109 M Table 50 - Page control field . . . . . . . . . . . . . . . . . . . . . . 110aM Table 51 - LOG SENSE command. . . . . . . . . . . . . . . . . . . . . . . 111 M Table 52 - MODE SELECT(6) command . . . . . . . . . . . . . . . . . . . . 112 M Table 53 - MODE SELECT(10) command. . . . . . . . . . . . . . . . . . . . 114 M Table 54 - MODE SENSE(6) command. . . . . . . . . . . . . . . . . . . . . 115eM Table 55 - Page control field . . . . . . . . . . . . . . . . . . . . . . 115 M Table 56 - Mode page code usage for all devices . . . . . . . . . . . . . 115 M Table 57 - MODE SENSE(10) command . . . . . . . . . . . . . . . . . . . . 117 M Table 58 - READ BUFFER command. . . . . . . . . . . . . . . . . . . . . . 118 M Table 59 - READ BUFFER mode field . . . . . . . . . . . . . . . . . . . . 118pM Table 60 - READ BUFFER header . . . . . . . . . . . . . . . . . . . . . . 118rM Table 61 - READ BUFFER descriptor . . . . . . . . . . . . . . . . . . . . 119cM Table 62 - Buffer offset boundary . . . . . . . . . . . . . . . . . . . . 120 M Table 63 - RECEIVE DIAGNOSTIC RESULTS command . . . . . . . . . . . . . . 121 M Table 64 - REQUEST SENSE command. . . . . . . . . . . . . . . . . . . . . 122 M Table 65 - Error codes 70h and 71h sense data format. . . . . . . . . . . 123nM Table 66 - Field pointer bytes. . . . . . . . . . . . . . . . . . . . . . 125iM Table 67 - Actual retry count bytes . . . . . . . . . . . . . . . . . . . 125oM Table 68 - Format progress indication bytes . . . . . . . . . . . . . . . 126uM Table 69 - Sense key (0h-7h) descriptions . . . . . . . . . . . . . . . . 128 M Table 70 - Sense key (8h-Fh) descriptions . . . . . . . . . . . . . . . . 129 M Table 71 - ASC and ASCQ assignments . . . . . . . . . . . . . . . . . . . 130 M Table 72 - SEND DIAGNOSTIC command. . . . . . . . . . . . . . . . . . . . 134 M Table 73 - TEST UNIT READY command. . . . . . . . . . . . . . . . . . . . 135 M Table 74 - Preferred TEST UNIT READY responses. . . . . . . . . . . . . . 135 M Table 75 - WRITE BUFFER command . . . . . . . . . . . . . . . . . . . . . 136dM Table 76 - WRITE BUFFER mode field. . . . . . . . . . . . . . . . . . . . 137 M Table 77 - Diagnostic page format . . . . . . . . . . . . . . . . . . . . 138 M Table 78 - Diagnostic page codes. . . . . . . . . . . . . . . . . . . . . 139 M Table 79 - Supported diagnostic pages . . . . . . . . . . . . . . . . . . 139nM Table 80 - Log page format. . . . . . . . . . . . . . . . . . . . . . . . 140 M Table 81 - Log parameter. . . . . . . . . . . . . . . . . . . . . . . . . 140uM Table 82 - Threshold met criteria . . . . . . . . . . . . . . . . . . . . 142 M Table 83 - Log page codes . . . . . . . . . . . . . . . . . . . . . . . . 143 = Table 84 - Parameter code field for buffer over-run/under-run M    counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143eM Table 85 - Count basis definition . . . . . . . . . . . . . . . . . . . . 144IM Table 86 - Cause field definition . . . . . . . . . . . . . . . . . . . . 144nM Table 87 - Parameter codes for error counter pages. . . . . . . . . . . . 144aM Table 88 - Non-medium error event parameter codes . . . . . . . . . . . . 145 M Table 89 - Supported log pages. . . . . . . . . . . . . . . . . . . . . . 146 M Table 90 - Mode parameter list. . . . . . . . . . . . . . . . . . . . . . 146 M Table 91 - Mode parameter header(6) . . . . . . . . . . . . . . . . . . . 146nM Table 92 - Mode parameter header(10). . . . . . . . . . . . . . . . . . . 147 M Table 93 - Mode parameter block descriptor. . . . . . . . . . . . . . . . 1483M Table 94 - Mode page format . . . . . . . . . . . . . . . . . . . . . . . 1483M Table 95 - Mode page codes. . . . . . . . . . . . . . . . . . . . . . . . 149 M Table 96 - Control mode page. . . . . . . . . . . . . . . . . . . . . . . 149eM Table 97 - Queue algorithm modifier . . . . . . . . . . . . . . . . . . . 150rM Table 98 - Disconnect-reconnect page. . . . . . . . . . . . . . . . . . . 152aM Table 99 - Data transfer disconnect control . . . . . . . . . . . . . . . 153rM Table 100 - Peripheral device page. . . . . . . . . . . . . . . . . . . . 154vM Table 101 - Interface identifier codes. . . . . . . . . . . . . . . . . . 154tM Table 102 - Vital product data page codes . . . . . . . . . . . . . . . . 154 M Table 103 - ASCII implemented operating definition  . . . . . . . . . . . 155eM Table 104 - ASCII information page. . . . . . . . . . . . . . . . . . . . 156rM Table 105 - Implemented operating definition page . . . . . . . . . . . . 156TM Table 106 - Supported vital product data pages. . . . . . . . . . . . . . 158dM Table 107 - Unit serial number page . . . . . . . . . . . . . . . . . . . 159oM Table 108 - Commands for direct-access devices. . . . . . . . . . . . . . 168 M Table 109 - FORMAT UNIT command . . . . . . . . . . . . . . . . . . . . . 169 M Table 110 - FORMAT UNIT parameter list. . . . . . . . . . . . . . . . . . 170 M Table 111 - Defect list header. . . . . . . . . . . . . . . . . . . . . . 170dM Table 112 - FORMAT UNIT defect descriptor format and requirements . . . . 171nM Table 113 - Defect descriptor - Block format. . . . . . . . . . . . . . . 174tM Table 114 - Defect descriptor - Bytes from index format . . . . . . . . . 174 M Table 115 - Defect descriptor - Physical sector format. . . . . . . . . . 175 M Table 116 - Initialization pattern descriptor . . . . . . . . . . . . . . 175tM Table 117 - Initialization pattern modifier . . . . . . . . . . . . . . . 175cM Table 118 - Initialization pattern type . . . . . . . . . . . . . . . . . 176sM Table 119 - LOCK UNLOCK CACHE command . . . . . . . . . . . . . . . . . . 177 M Table 120 - PRE-FETCH command . . . . . . . . . . . . . . . . . . . . . . 178nM Table 121 - PREVENT ALLOW MEDIUM REMOVAL command. . . . . . . . . . . . . 179 M Table 122 - READ(6) command . . . . . . . . . . . . . . . . . . . . . . . 180cM Table 123 - READ(10) command. . . . . . . . . . . . . . . . . . . . . . . 181nM Table 124 - READ CAPACITY command . . . . . . . . . . . . . . . . . . . . 182nM Table 125 - READ CAPACITY data. . . . . . . . . . . . . . . . . . . . . . 182mM Table 126 - READ DEFECT DATA command. . . . . . . . . . . . . . . . . . . 183dM Table 127 - READ DEFECT DATA defect list. . . . . . . . . . . . . . . . . 184 M Table 128 - READ LONG command . . . . . . . . . . . . . . . . . . . . . . 185 M Table 129 - REASSIGN BLOCKS command . . . . . . . . . . . . . . . . . . . 186 M Table 130 - REASSIGN BLOCKS defect list . . . . . . . . . . . . . . . . . 186 M Table 131 - RELEASE command . . . . . . . . . . . . . . . . . . . . . . . 187 M Table 132 - RESERVE command . . . . . . . . . . . . . . . . . . . . . . . 189 M Table 133 - Data format of extent descriptors . . . . . . . . . . . . . . 190 M Table 134 - Reservation types . . . . . . . . . . . . . . . . . . . . . . 190 M Table 135 - REZERO UNIT command . . . . . . . . . . . . . . . . . . . . . 192 M Table 136 - SEARCH DATA commands. . . . . . . . . . . . . . . . . . . . . 193 M Table 137 - SEARCH DATA parameter list. . . . . . . . . . . . . . . . . . 194 M Table 138 - SEEK(6) command . . . . . . . . . . . . . . . . . . . . . . . 196 M Table 139 - SEEK(10) command. . . . . . . . . . . . . . . . . . . . . . . 196 M Table 140 - SET LIMITS command. . . . . . . . . . . . . . . . . . . . . . 197 M Table 141 - START STOP UNIT command . . . . . . . . . . . . . . . . . . . 198 M Table 142 - SYNCHRONIZE CACHE command . . . . . . . . . . . . . . . . . . 199 M Table 143 - VERIFY command. . . . . . . . . . . . . . . . . . . . . . . . 200 M Table 144 - WRITE(6) command. . . . . . . . . . . . . . . . . . . . . . . 201 M Table 145 - WRITE(10) command . . . . . . . . . . . . . . . . . . . . . . 202 M Table 146 - WRITE AND VERIFY command. . . . . . . . . . . . . . . . . . . 203 M Table 147 - WRITE LONG command. . . . . . . . . . . . . . . . . . . . . . 204 M Table 148 - WRITE SAME command. . . . . . . . . . . . . . . . . . . . . . 205aM Table 149 - Diagnostic page codes . . . . . . . . . . . . . . . . . . . . 206aM Table 150 - Translate address page - SEND DIAGNOSTIC. . . . . . . . . . . 206oM Table 151 - Translate address page - RECEIVE DIAGNOSTIC . . . . . . . . . 207 M Table 152 - Log page codes. . . . . . . . . . . . . . . . . . . . . . . . 208 M Table 153 - Direct-access medium-type codes . . . . . . . . . . . . . . . 208 M Table 154 - Device specific parameter . . . . . . . . . . . . . . . . . . 209 M Table 155 - Mode page codes . . . . . . . . . . . . . . . . . . . . . . . 210 M Table 156 - Caching page. . . . . . . . . . . . . . . . . . . . . . . . . 210 M Table 157 - Demand read and write retention priority. . . . . . . . . . . 211 M Table 158 - Flexible disk page. . . . . . . . . . . . . . . . . . . . . . 213 M Table 159 - Examples of transfer rates. . . . . . . . . . . . . . . . . . 214 M Table 160 - Pin 34 field. . . . . . . . . . . . . . . . . . . . . . . . . 215 M Table 161 - Pin 4 field . . . . . . . . . . . . . . . . . . . . . . . . . 215 M Table 162 - Pin 34 field. . . . . . . . . . . . . . . . . . . . . . . . . 216 M Table 163 - Format device page. . . . . . . . . . . . . . . . . . . . . . 216 M Table 164 - Reporting of default sector formatting support. . . . . . . . 218 M Table 165 - Reporting of changeable sector formatting support . . . . . . 219 M Table 166 - Medium types supported page . . . . . . . . . . . . . . . . . 219 M Table 167 - Notch page. . . . . . . . . . . . . . . . . . . . . . . . . . 220 M Table 168 - Read-write error recovery page. . . . . . . . . . . . . . . . 222 M Table 169 - Error recovery bit definitions. . . . . . . . . . . . . . . . 223 M Table 170 - Combined error recovery parameter descriptions. . . . . . . . 224 M Table 171 - Rigid disk drive geometry page. . . . . . . . . . . . . . . . 229 M Table 172 - Rotational position locking . . . . . . . . . . . . . . . . . 230 M Table 173 - Verify error recovery page. . . . . . . . . . . . . . . . . . 231 M Table 174 - Commands for sequential-access devices. . . . . . . . . . . . 241 M Table 175 - ERASE command . . . . . . . . . . . . . . . . . . . . . . . . 243 M Table 176 - LOAD UNLOAD command . . . . . . . . . . . . . . . . . . . . . 244 M Table 177 - LOCATE command. . . . . . . . . . . . . . . . . . . . . . . . 245 M Table 178 - READ command. . . . . . . . . . . . . . . . . . . . . . . . . 246 M Table 179 - READ BLOCK LIMITS command . . . . . . . . . . . . . . . . . . 248 M Table 180 - READ BLOCK LIMITS data. . . . . . . . . . . . . . . . . . . . 248 M Table 181 - READ POSITION command . . . . . . . . . . . . . . . . . . . . 249 M Table 182 - READ POSITION data format . . . . . . . . . . . . . . . . . . 249 M Table 183 - READ REVERSE command. . . . . . . . . . . . . . . . . . . . . 251 M Table 184 - RECOVER BUFFERED DATA command . . . . . . . . . . . . . . . . 252 M Table 185 - RELEASE UNIT command. . . . . . . . . . . . . . . . . . . . . 253 M Table 186 - RESERVE UNIT command. . . . . . . . . . . . . . . . . . . . . 254 M Table 187 - REWIND command. . . . . . . . . . . . . . . . . . . . . . . . 255 M Table 188 - SPACE command . . . . . . . . . . . . . . . . . . . . . . . . 256 M Table 189 - Code field definition . . . . . . . . . . . . . . . . . . . . 256 M Table 190 - VERIFY command. . . . . . . . . . . . . . . . . . . . . . . . 258 M Table 191 - WRITE command . . . . . . . . . . . . . . . . . . . . . . . . 259 M Table 192 - WRITE FILEMARKS command . . . . . . . . . . . . . . . . . . . 261 M Table 193 - Diagnostic page codes . . . . . . . . . . . . . . . . . . . . 262 M Table 194 - Log page codes. . . . . . . . . . . . . . . . . . . . . . . . 262 M Table 195 - Device-specific parameter . . . . . . . . . . . . . . . . . . 263 M Table 196 - Buffered modes. . . . . . . . . . . . . . . . . . . . . . . . 263 M Table 197 - Speed field definition. . . . . . . . . . . . . . . . . . . . 263 M Table 198 - Sequential-access density codes . . . . . . . . . . . . . . . 264 M Table 199 - Mode page codes . . . . . . . . . . . . . . . . . . . . . . . 265 M Table 200 - Device configuration page . . . . . . . . . . . . . . . . . . 266 M Table 201 - EOD formats . . . . . . . . . . . . . . . . . . . . . . . . . 268 M Table 202 - Medium partition page(1). . . . . . . . . . . . . . . . . . . 269 M Table 203 - Medium partition page(2-4). . . . . . . . . . . . . . . . . . 270 M Table 204 - Read-write error recovery page. . . . . . . . . . . . . . . . 270 M Table 205 - Commands for printer devices. . . . . . . . . . . . . . . . . 274 M Table 206 - FORMAT command. . . . . . . . . . . . . . . . . . . . . . . . 275 M Table 207 - Format type . . . . . . . . . . . . . . . . . . . . . . . . . 275 M Table 208 - PRINT command . . . . . . . . . . . . . . . . . . . . . . . . 276 M Table 209 - RECOVER BUFFERED DATA command . . . . . . . . . . . . . . . . 276 M Table 210 - SLEW AND PRINT command. . . . . . . . . . . . . . . . . . . . 277 M Table 211 - STOP PRINT command. . . . . . . . . . . . . . . . . . . . . . 278 M Table 212 - SYNCHRONIZE BUFFER command. . . . . . . . . . . . . . . . . . 278eM Table 213 - Diagnostic page codes . . . . . . . . . . . . . . . . . . . . 279IM Table 214 - Log page codes. . . . . . . . . . . . . . . . . . . . . . . . 279nM Table 215 - Printer device-specific parameter . . . . . . . . . . . . . . 279aM Table 216 - Mode page codes . . . . . . . . . . . . . . . . . . . . . . . 280 M Table 217 - Parallel printer interface. . . . . . . . . . . . . . . . . . 280 M Table 218 - Parity select . . . . . . . . . . . . . . . . . . . . . . . . 281 M Table 219 - VFU control byte. . . . . . . . . . . . . . . . . . . . . . . 281nM Table 220 - Printer options . . . . . . . . . . . . . . . . . . . . . . . 282 M Table 221 - Font identification . . . . . . . . . . . . . . . . . . . . . 2823M Table 222 - Slew mode . . . . . . . . . . . . . . . . . . . . . . . . . . 2833M Table 223 - Line slew . . . . . . . . . . . . . . . . . . . . . . . . . . 283 M Table 224 - Form slew . . . . . . . . . . . . . . . . . . . . . . . . . . 284eM Table 225 - Data termination option . . . . . . . . . . . . . . . . . . . 284rM Table 226 - Serial printer interface. . . . . . . . . . . . . . . . . . . 285aM Table 227 - Parity selection. . . . . . . . . . . . . . . . . . . . . . . 286rM Table 228 - Pacing protocol . . . . . . . . . . . . . . . . . . . . . . . 286vM Table 229 - Commands for processor devices. . . . . . . . . . . . . . . . 289tM Table 230 - RECEIVE command . . . . . . . . . . . . . . . . . . . . . . . 289 M Table 231 - SEND command. . . . . . . . . . . . . . . . . . . . . . . . . 290eM Table 232 - SEND command - AEN data format. . . . . . . . . . . . . . . . 290rM Table 233 - Diagnostic page codes . . . . . . . . . . . . . . . . . . . . 291TM Table 234 - Log page codes. . . . . . . . . . . . . . . . . . . . . . . . 291dM Table 235 - Commands for write-once devices . . . . . . . . . . . . . . . 294oM Table 236 - Example mixed mode CD-ROM disc layout . . . . . . . . . . . . 298 M Table 237 - MSF address format. . . . . . . . . . . . . . . . . . . . . . 303 M Table 238 - Commands for CD-ROM device. . . . . . . . . . . . . . . . . . 305 M Table 239 - PAUSE RESUME command. . . . . . . . . . . . . . . . . . . . . 306dM Table 240 - PLAY AUDIO(10) command. . . . . . . . . . . . . . . . . . . . 307nM Table 241 - PLAY AUDIO(12) command. . . . . . . . . . . . . . . . . . . . 308tM Table 242 - PLAY AUDIO MSF command. . . . . . . . . . . . . . . . . . . . 309 M Table 243 - PLAY AUDIO TRACK INDEX command. . . . . . . . . . . . . . . . 310 M Table 244 - PLAY AUDIO TRACK RELATIVE(10) command . . . . . . . . . . . . 311tM Table 245 - PLAY AUDIO TRACK RELATIVE(12) command . . . . . . . . . . . . 312cM Table 246 - READ CD-ROM CAPACITY command. . . . . . . . . . . . . . . . . 313sM Table 247 - READ CAPACITY data format . . . . . . . . . . . . . . . . . . 314 M Table 248 - READ HEADER command . . . . . . . . . . . . . . . . . . . . . 314nM Table 249 - READ HEADER data format . . . . . . . . . . . . . . . . . . . 314 M Table 250 - CD-ROM data mode codes. . . . . . . . . . . . . . . . . . . . 315cM Table 251 - READ SUB-CHANNEL command. . . . . . . . . . . . . . . . . . . 316nM Table 252 - Sub-channel data format codes . . . . . . . . . . . . . . . . 316nM Table 253 - Sub-Q channel data format . . . . . . . . . . . . . . . . . . 317mM Table 254 - Audio status codes. . . . . . . . . . . . . . . . . . . . . . 318dM Table 255 - ADR sub-channel Q field . . . . . . . . . . . . . . . . . . . 318 M Table 256 - Sub-channel Q control bits. . . . . . . . . . . . . . . . . . 318 M Table 257 - CD-ROM current position data format . . . . . . . . . . . . . 320 M Table 258 - Media catalogue number data format. . . . . . . . . . . . . . 320 M Table 259 - Track international standard recording code data format . . . 321 M Table 260 - READ TOC command. . . . . . . . . . . . . . . . . . . . . . . 323 M Table 261 - READ TOC data format  . . . . . . . . . . . . . . . . . . . . 323 M Table 262 - Diagnostic page codes . . . . . . . . . . . . . . . . . . . . 325 M Table 263 - Log page codes. . . . . . . . . . . . . . . . . . . . . . . . 325 M Table 264 - CD-ROM medium type codes. . . . . . . . . . . . . . . . . . . 325 M Table 265 - CD-ROM device-specific parameter. . . . . . . . . . . . . . . 326 M Table 266 - CD-ROM density codes. . . . . . . . . . . . . . . . . . . . . 326 M Table 267 - Mode page codes . . . . . . . . . . . . . . . . . . . . . . . 327 M Table 268 - CD-ROM audio control parameters page. . . . . . . . . . . . . 327 M Table 269 - Multiplier for LBAs . . . . . . . . . . . . . . . . . . . . . 328 M Table 270 - Output port channel selection . . . . . . . . . . . . . . . . 328 M Table 271 - CD-ROM parameters page. . . . . . . . . . . . . . . . . . . . 329 M Table 272 - Inactivity timer multiplier values. . . . . . . . . . . . . . 329 M Table 273 - Read error recovery parameters page . . . . . . . . . . . . . 330 M Table 274 - Error recovery bit settings . . . . . . . . . . . . . . . . . 331 M Table 275 - CD-ROM error recovery descriptions. . . . . . . . . . . . . . 331 M Table 276 - Verify error recovery parameters page . . . . . . . . . . . . 336aM Table 277 - Commands for scanner devices. . . . . . . . . . . . . . . . . 340aM Table 278 - GET DATA BUFFER STATUS command. . . . . . . . . . . . . . . . 341oM Table 279 - Data buffer status format . . . . . . . . . . . . . . . . . . 341 M Table 280 - GET WINDOW command. . . . . . . . . . . . . . . . . . . . . . 343 M Table 281 - Get window data header. . . . . . . . . . . . . . . . . . . . 343 M Table 282 - Window descriptor bytes . . . . . . . . . . . . . . . . . . . 344 M Table 283 - Image composition codes . . . . . . . . . . . . . . . . . . . 345 M Table 284 - Padding types . . . . . . . . . . . . . . . . . . . . . . . . 346 M Table 285 - Compression types and arguments . . . . . . . . . . . . . . . 346 M Table 286 - OBJECT POSITION command . . . . . . . . . . . . . . . . . . . 347 M Table 287 - Position function . . . . . . . . . . . . . . . . . . . . . . 347 M Table 288 - READ command. . . . . . . . . . . . . . . . . . . . . . . . . 349 M Table 289 - Data type codes . . . . . . . . . . . . . . . . . . . . . . . 349 M Table 290 - SCAN command. . . . . . . . . . . . . . . . . . . . . . . . . 350 M Table 291 - SEND command. . . . . . . . . . . . . . . . . . . . . . . . . 350 M Table 292 - SET WINDOW command. . . . . . . . . . . . . . . . . . . . . . 351 M Table 293 - Set window data header. . . . . . . . . . . . . . . . . . . . 351 M Table 294 - Diagnostic page codes . . . . . . . . . . . . . . . . . . . . 352 M Table 295 - Log page codes. . . . . . . . . . . . . . . . . . . . . . . . 352 M Table 296 - Mode page codes . . . . . . . . . . . . . . . . . . . . . . . 353 M Table 297 - Measurement units page. . . . . . . . . . . . . . . . . . . . 353 M Table 298 - Basic measurement units . . . . . . . . . . . . . . . . . . . 354 M Table 299 - Commands for optical memory devices . . . . . . . . . . . . . 359 M Table 300 - ERASE(10) command . . . . . . . . . . . . . . . . . . . . . . 360 M Table 301 - ERASE(12) command . . . . . . . . . . . . . . . . . . . . . . 361 M Table 302 - MEDIUM SCAN command . . . . . . . . . . . . . . . . . . . . . 362 M Table 303 - MEDIUM SCAN parameter list. . . . . . . . . . . . . . . . . . 363 M Table 304 - READ(12) command. . . . . . . . . . . . . . . . . . . . . . . 364 M Table 305 - READ DEFECT DATA(12) command. . . . . . . . . . . . . . . . . 364 M Table 306 - READ DEFECT DATA(12) list header. . . . . . . . . . . . . . . 365 M Table 307 - READ GENERATION command . . . . . . . . . . . . . . . . . . . 366 M Table 308 - Maximum generation data block . . . . . . . . . . . . . . . . 366 M Table 309 - READ UPDATED BLOCK(10) command. . . . . . . . . . . . . . . . 367 M Table 310 - SEARCH DATA(12) commands. . . . . . . . . . . . . . . . . . . 368 M Table 311 - SET LIMITS(12) command. . . . . . . . . . . . . . . . . . . . 368 M Table 312 - UPDATE BLOCK command. . . . . . . . . . . . . . . . . . . . . 369 M Table 313 - VERIFY command. . . . . . . . . . . . . . . . . . . . . . . . 370 M Table 314 - VERIFY(12) command. . . . . . . . . . . . . . . . . . . . . . 371 M Table 315 - WRITE(10) command . . . . . . . . . . . . . . . . . . . . . . 372 M Table 316 - WRITE(12) command . . . . . . . . . . . . . . . . . . . . . . 373 M Table 317 - WRITE AND VERIFY(10) command. . . . . . . . . . . . . . . . . 373 M Table 318 - WRITE AND VERIFY(12) command. . . . . . . . . . . . . . . . . 374 M Table 319 - Diagnostic page codes . . . . . . . . . . . . . . . . . . . . 375 M Table 320 - Log page codes. . . . . . . . . . . . . . . . . . . . . . . . 375 M Table 321 - Optical memory medium-type codes. . . . . . . . . . . . . . . 375 M Table 322 - Optical memory device specific parameter. . . . . . . . . . . 376 M Table 323 - Optical memory density codes. . . . . . . . . . . . . . . . . 376 M Table 324 - Mode page codes . . . . . . . . . . . . . . . . . . . . . . . 377 M Table 325 - Optical memory page . . . . . . . . . . . . . . . . . . . . . 378 M Table 326 - Volume tag information format . . . . . . . . . . . . . . . . 382 M Table 327 - Commands for medium changer devices . . . . . . . . . . . . . 383 M Table 328 - EXCHANGE MEDIUM command . . . . . . . . . . . . . . . . . . . 384 M Table 329 - INITIALIZE ELEMENT STATUS command . . . . . . . . . . . . . . 385 M Table 330 - MOVE MEDIUM command . . . . . . . . . . . . . . . . . . . . . 386 M Table 331 - POSITION TO ELEMENT command . . . . . . . . . . . . . . . . . 387 M Table 332 - READ ELEMENT STATUS command . . . . . . . . . . . . . . . . . 388 M Table 333 - Element type code . . . . . . . . . . . . . . . . . . . . . . 388 M Table 334 - Element status data . . . . . . . . . . . . . . . . . . . . . 389 M Table 335 - Element status page . . . . . . . . . . . . . . . . . . . . . 391 M Table 336 - Medium transport element descriptor . . . . . . . . . . . . . 392 M Table 337 - Storage element descriptor. . . . . . . . . . . . . . . . . . 393 M Table 338 - Import export element descriptor. . . . . . . . . . . . . . . 394 M Table 339 - Data transfer element descriptor. . . . . . . . . . . . . . . 395 M Table 340 - REQUEST VOLUME ELEMENT ADDRESS command. . . . . . . . . . . . 396eM Table 341 - Volume element address header format. . . . . . . . . . . . . 397IM Table 342 - RELEASE command . . . . . . . . . . . . . . . . . . . . . . . 398nM Table 343 - RESERVE command . . . . . . . . . . . . . . . . . . . . . . . 399aM Table 344 - Data format of element list descriptors . . . . . . . . . . . 400 M Table 345 - SEND VOLUME TAG command . . . . . . . . . . . . . . . . . . . 401 M Table 346 - Send volume tag action codes. . . . . . . . . . . . . . . . . 402 M Table 347 - Send volume tag parameters format . . . . . . . . . . . . . . 402nM Table 348 - Diagnostic page codes . . . . . . . . . . . . . . . . . . . . 404 M Table 349 - Log page codes. . . . . . . . . . . . . . . . . . . . . . . . 4043M Table 350 - Mode page codes . . . . . . . . . . . . . . . . . . . . . . . 4053M Table 351 - Device capabilities page. . . . . . . . . . . . . . . . . . . 405 M Table 352 - Element address assignment page . . . . . . . . . . . . . . . 406eM Table 353 - Transport geometry parameters page. . . . . . . . . . . . . . 409rM Table 354 - Commands for communications devices . . . . . . . . . . . . . 413aM Table 355 - GET MESSAGE(6) command. . . . . . . . . . . . . . . . . . . . 414rM Table 356 - GET MESSAGE(10) command . . . . . . . . . . . . . . . . . . . 414vM Table 357 - GET MESSAGE(12) command . . . . . . . . . . . . . . . . . . . 415tM Table 358 - SEND MESSAGE(6) command . . . . . . . . . . . . . . . . . . . 416 M Table 359 - SEND MESSAGE(10) command. . . . . . . . . . . . . . . . . . . 416eM Table 360 - SEND MESSAGE(12) command. . . . . . . . . . . . . . . . . . . 417rM Table 361 - Diagnostic page codes . . . . . . . . . . . . . . . . . . . . 418TM Table 362 - Log page codes. . . . . . . . . . . . . . . . . . . . . . . . 418dM Table 363 - Mode page codes . . . . . . . . . . . . . . . . . . . . . . . 419oM Table B.1 - Fast SCSI jitter budget . . . . . . . . . . . . . . . . . . . 425 M Table B.2 - Mapping of jitter to SCSI . . . . . . . . . . . . . . . . . . 425 M Table D.1 - ASC and ASCQ assignments. . . . . . . . . . . . . . . . . . . 429 M Table D.2 - SCSI-2 Operation Codes. . . . . . . . . . . . . . . . . . . . 435dM Table E.1 - Vendor identification list. . . . . . . . . . . . . . . . . . 439nM Table 1 - Cross-reference to connector contact assignments. . . . . . . .  20tM Table 2 - Single-ended contact assignments - A cable. . . . . . . . . . .  20 M Table 3 - Single-ended contact assignments - B cable. . . . . . . . . . .  21 M Table 4 - Differential contact assignments - A cable. . . . . . . . . . .  22tM Table 5 - Differential contact assignments - B cable. . . . . . . . . . .  23cM Table 6 - Signal sources. . . . . . . . . . . . . . . . . . . . . . . . .  33sM Table 7 - SCSI bus timing values. . . . . . . . . . . . . . . . . . . . .  35 M Table 8 - Information transfer phases . . . . . . . . . . . . . . . . . .  43nM Table 9 - Message format. . . . . . . . . . . . . . . . . . . . . . . . .  53 M Table 10 - Message codes. . . . . . . . . . . . . . . . . . . . . . . . .  53cM Table 11 - Extended message format. . . . . . . . . . . . . . . . . . . .  55nM Table 12 - Extended message codes . . . . . . . . . . . . . . . . . . . .  55nM Table 13 - IDENTIFY message format. . . . . . . . . . . . . . . . . . . .  58mM Table 14 - IGNORE WIDE RESIDUE message format . . . . . . . . . . . . . .  59dM Table 15 - Ignore field definition. . . . . . . . . . . . . . . . . . . .  59 M Table 16 - MODIFY DATA POINTER. . . . . . . . . . . . . . . . . . . . . .  61 M Table 17 - Queue tag message format . . . . . . . . . . . . . . . . . . .  61 M Table 18 - SYNCHRONOUS DATA TRANSFER REQUEST. . . . . . . . . . . . . . .  63 M Table 19 - WIDE DATA TRANSFER MESSAGE . . . . . . . . . . . . . . . . . .  65 M Table 20 - Operation code type. . . . . . . . . . . . . . . . . . . . . .  68 M Table 21 - Typical command descriptor block for six-byte commands . . . .  69 M Table 22 - Typical command descriptor block for ten-byte commands . . . .  69 M Table 23 - Typical command descriptor block for twelve-byte commands. . .  69 M Table 24 - Operation code . . . . . . . . . . . . . . . . . . . . . . . .  71 M Table 25 - Control field. . . . . . . . . . . . . . . . . . . . . . . . .  72 M Table 26 - Status byte. . . . . . . . . . . . . . . . . . . . . . . . . .  73 M Table 27 - Status byte code . . . . . . . . . . . . . . . . . . . . . . .  73 M Table 28 - Commands in order received by target . . . . . . . . . . . . .  83 M Table 29 - Commands in order of execution . . . . . . . . . . . . . . . .  84 M Table 30 - Modified by HEAD OF QUEUE TAG message. . . . . . . . . . . . .  84 M Table 31 - Commands for all device types. . . . . . . . . . . . . . . . .  88 M Table 32 - CHANGE DEFINITION command. . . . . . . . . . . . . . . . . . .  89 M Table 33 - Definition parameter field . . . . . . . . . . . . . . . . . .  90 M Table 34 - COMPARE command. . . . . . . . . . . . . . . . . . . . . . . .  91 M Table 35 - COPY command . . . . . . . . . . . . . . . . . . . . . . . . .  92 M Table 36 - COPY parameter list. . . . . . . . . . . . . . . . . . . . . .  92aM Table 37 - COPY function codes. . . . . . . . . . . . . . . . . . . . . .  93aM Table 38 - Segment descriptor for COPY function codes 00h and 01h . . . .  95oM Table 39 - Segment descriptor for COPY function code 02h. . . . . . . . .  96 M Table 40 - Segment descriptor for COPY function code 03h. . . . . . . . .  96 M Table 41 - Segment descriptor for COPY function code 04h. . . . . . . . .  98 M Table 42 - Pad and cat bit definition . . . . . . . . . . . . . . . . . .  98 M Table 43 - COPY AND VERIFY command. . . . . . . . . . . . . . . . . . . .  99 M Table 44 - INQUIRY command. . . . . . . . . . . . . . . . . . . . . . . . 100 M Table 45 - Standard INQUIRY data format . . . . . . . . . . . . . . . . . 101 M Table 46 - Peripheral qualifier . . . . . . . . . . . . . . . . . . . . . 101 M Table 47 - Peripheral device type . . . . . . . . . . . . . . . . . . . . 102 M Table 48 - ANSI-approved version. . . . . . . . . . . . . . . . . . . . . 103 M Table 49 - LOG SELECT command . . . . . . . . . . . . . . . . . . . . . . 105 M Table 50 - Page control field . . . . . . . . . . . . . . . . . . . . . . 106 M Table 51 - LOG SENSE command. . . . . . . . . . . . . . . . . . . . . . . 107 M Table 52 - MODE SELECT(6) command . . . . . . . . . . . . . . . . . . . . 108 M Table 53 - MODE SELECT(10) command. . . . . . . . . . . . . . . . . . . . 110 M Table 54 - MODE SENSE(6) command. . . . . . . . . . . . . . . . . . . . . 111 M Table 55 - Page control field . . . . . . . . . . . . . . . . . . . . . . 111 M Table 56 - Mode page code usage for all devices . . . . . . . . . . . . . 111 M Table 57 - MODE SENSE(10) command . . . . . . . . . . . . . . . . . . . . 113 M Table 58 - READ BUFFER command. . . . . . . . . . . . . . . . . . . . . . 114 M Table 59 - READ BUFFER mode field . . . . . . . . . . . . . . . . . . . . 114 M Table 60 - READ BUFFER header . . . . . . . . . . . . . . . . . . . . . . 114 M Table 61 - READ BUFFER descriptor . . . . . . . . . . . . . . . . . . . . 115 M Table 62 - Buffer offset boundary . . . . . . . . . . . . . . . . . . . . 116 M Table 63 - RECEIVE DIAGNOSTIC RESULTS command . . . . . . . . . . . . . . 117 M Table 64 - REQUEST SENSE command. . . . . . . . . . . . . . . . . . . . . 118 M Table 65 - Error codes 70h and 71h sense data format. . . . . . . . . . . 119 M Table 66 - Field pointer bytes. . . . . . . . . . . . . . . . . . . . . . 121 M Table 67 - Actual retry count bytes . . . . . . . . . . . . . . . . . . . 121 M Table 68 - Format progress indication bytes . . . . . . . . . . . . . . . 122 M Table 69 - Sense key (0h-7h) descriptions . . . . . . . . . . . . . . . . 124 M Table 70 - Sense key (8h-Fh) descriptions . . . . . . . . . . . . . . . . 125 M Table 71 - ASC and ASCQ assignments . . . . . . . . . . . . . . . . . . . 126 M Table 72 - SEND DIAGNOSTIC command. . . . . . . . . . . . . . . . . . . . 130 M Table 73 - TEST UNIT READY command. . . . . . . . . . . . . . . . . . . . 131 M Table 74 - Preferred TEST UNIT READY responses. . . . . . . . . . . . . . 131 M Table 75 - WRITE BUFFER command . . . . . . . . . . . . . . . . . . . . . 132 M Table 76 - WRITE BUFFER mode field. . . . . . . . . . . . . . . . . . . . 133 M Table 77 - Diagnostic page format . . . . . . . . . . . . . . . . . . . . 134 M Table 78 - Diagnostic page codes. . . . . . . . . . . . . . . . . . . . . 135 M Table 79 - Supported diagnostic pages . . . . . . . . . . . . . . . . . . 135 M Table 80 - Log page format. . . . . . . . . . . . . . . . . . . . . . . . 136 M Table 81 - Log parameter. . . . . . . . . . . . . . . . . . . . . . . . . 136 M Table 82 - Threshold met criteria . . . . . . . . . . . . . . . . . . . . 138 M Table 83 - Log page codes . . . . . . . . . . . . . . . . . . . . . . . . 139 = Table 84 - Parameter code field for buffer over-run/under-run M    counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 M Table 85 - Count basis definition . . . . . . . . . . . . . . . . . . . . 140 M Table 86 - Cause field definition . . . . . . . . . . . . . . . . . . . . 140 M Table 87 - Parameter codes for error counter pages. . . . . . . . . . . . 140 M Table 88 - Non-medium error event parameter codes . . . . . . . . . . . . 141 M Table 89 - Supported log pages. . . . . . . . . . . . . . . . . . . . . . 142 M Table 90 - Mode parameter list. . . . . . . . . . . . . . . . . . . . . . 142 M Table 91 - Mode parameter header(6) . . . . . . . . . . . . . . . . . . . 142 M Table 92 - Mode parameter header(10). . . . . . . . . . . . . . . . . . . 143 M Table 93 - Mode parameter block descriptor. . . . . . . . . . . . . . . . 144 M Table 94 - Mode page format . . . . . . . . . . . . . . . . . . . . . . . 144 M Table 95 - Mode page codes. . . . . . . . . . . . . . . . . . . . . . . . 145 M Table 96 - Control mode page. . . . . . . . . . . . . . . . . . . . . . . 145 M Table 97 - Queue algorithm modifier . . . . . . . . . . . . . . . . . . . 146 M Table 98 - Disconnect-reconnect page. . . . . . . . . . . . . . . . . . . 148 M Table 99 - Data transfer disconnect control . . . . . . . . . . . . . . . 149 M Table 100 - Peripheral device page. . . . . . . . . . . . . . . . . . . . 150 M Table 101 - Interface identifier codes. . . . . . . . . . . . . . . . . . 150 M Table 102 - Vital product data page codes . . . . . . . . . . . . . . . . 150 M Table 103 - ASCII implemented operating definition  . . . . . . . . . . . 151 M Table 104 - ASCII information page. . . . . . . . . . . . . . . . . . . . 152 M Table 105 - Implemented operating definition page . . . . . . . . . . . . 152 M Table 106 - Supported vital product data pages. . . . . . . . . . . . . . 154 M Table 107 - Unit serial number page . . . . . . . . . . . . . . . . . . . 155 M Table 108 - Commands for direct-access devices. . . . . . . . . . . . . . 163 M Table 109 - FORMAT UNIT command . . . . . . . . . . . . . . . . . . . . . 164 M Table 110 - FORMAT UNIT parameter list. . . . . . . . . . . . . . . . . . 165 M Table 111 - Defect list header. . . . . . . . . . . . . . . . . . . . . . 165 M Table 112 - FORMAT UNIT defect descriptor format and requirements . . . . 166 M Table 113 - Defect descriptor - Block format. . . . . . . . . . . . . . . 169 M Table 114 - Defect descriptor - Bytes from index format . . . . . . . . . 169 M Table 115 - Defect descriptor - Physical sector format. . . . . . . . . . 170 M Table 116 - Initialization pattern descriptor . . . . . . . . . . . . . . 170 M Table 117 - Initialization pattern modifier . . . . . . . . . . . . . . . 170 M Table 118 - Initialization pattern type . . . . . . . . . . . . . . . . . 171 M Table 119 - LOCK UNLOCK CACHE command . . . . . . . . . . . . . . . . . . 172 M Table 120 - PRE-FETCH command . . . . . . . . . . . . . . . . . . . . . . 173 M Table 121 - PREVENT ALLOW MEDIUM REMOVAL command. . . . . . . . . . . . . 174 M Table 122 - READ(6) command . . . . . . . . . . . . . . . . . . . . . . . 175 M Table 123 - READ(10) command. . . . . . . . . . . . . . . . . . . . . . . 176 M Table 124 - READ CAPACITY command . . . . . . . . . . . . . . . . . . . . 177 M Table 125 - READ CAPACITY data. . . . . . . . . . . . . . . . . . . . . . 177 M Table 126 - READ DEFECT DATA command. . . . . . . . . . . . . . . . . . . 178 M Table 127 - READ DEFECT DATA defect list. . . . . . . . . . . . . . . . . 179 M Table 128 - READ LONG command . . . . . . . . . . . . . . . . . . . . . . 180 M Table 129 - REASSIGN BLOCKS command . . . . . . . . . . . . . . . . . . . 181 M Table 130 - REASSIGN BLOCKS defect list . . . . . . . . . . . . . . . . . 181 M Table 131 - RELEASE command . . . . . . . . . . . . . . . . . . . . . . . 182 M Table 132 - RESERVE command . . . . . . . . . . . . . . . . . . . . . . . 184 M Table 133 - Data format of extent descriptors . . . . . . . . . . . . . . 185 M Table 134 - Reservation types . . . . . . . . . . . . . . . . . . . . . . 185 M Table 135 - REZERO UNIT command . . . . . . . . . . . . . . . . . . . . . 187 M Table 136 - SEARCH DATA commands. . . . . . . . . . . . . . . . . . . . . 188 M Table 137 - SEARCH DATA parameter list. . . . . . . . . . . . . . . . . . 189 M Table 138 - SEEK(6) command . . . . . . . . . . . . . . . . . . . . . . . 191 M Table 139 - SEEK(10) command. . . . . . . . . . . . . . . . . . . . . . . 191 M Table 140 - SET LIMITS command. . . . . . . . . . . . . . . . . . . . . . 192 M Table 141 - START STOP UNIT command . . . . . . . . . . . . . . . . . . . 193 M Table 142 - SYNCHRONIZE CACHE command . . . . . . . . . . . . . . . . . . 194 M Table 143 - VERIFY command. . . . . . . . . . . . . . . . . . . . . . . . 195 M Table 144 - WRITE(6) command. . . . . . . . . . . . . . . . . . . . . . . 196 M Table 145 - WRITE(10) command . . . . . . . . . . . . . . . . . . . . . . 197 M Table 146 - WRITE AND VERIFY command. . . . . . . . . . . . . . . . . . . 198 M Table 147 - WRITE LONG command. . . . . . . . . . . . . . . . . . . . . . 199 M Table 148 - WRITE SAME command. . . . . . . . . . . . . . . . . . . . . . 200aM Table 149 - Diagnostic page codes . . . . . . . . . . . . . . . . . . . . 201aM Table 150 - Translate address page - SEND DIAGNOSTIC. . . . . . . . . . . 201oM Table 151 - Translate address page - RECEIVE DIAGNOSTIC . . . . . . . . . 202 M Table 152 - Log page codes. . . . . . . . . . . . . . . . . . . . . . . . 203 M Table 153 - Direct-access medium-type codes . . . . . . . . . . . . . . . 203 M Table 154 - Device specific parameter . . . . . . . . . . . . . . . . . . 204 M Table 155 - Mode page codes . . . . . . . . . . . . . . . . . . . . . . . 205 M Table 156 - Caching page. . . . . . . . . . . . . . . . . . . . . . . . . 205 M Table 157 - Demand read and write retention priority. . . . . . . . . . . 206 M Table 158 - Flexible disk page. . . . . . . . . . . . . . . . . . . . . . 208 M Table 159 - Examples of transfer rates. . . . . . . . . . . . . . . . . . 209 M Table 160 - Pin 34 field. . . . . . . . . . . . . . . . . . . . . . . . . 210 M Table 161 - Pin 4 field . . . . . . . . . . . . . . . . . . . . . . . . . 210 M Table 162 - Pin 34 field. . . . . . . . . . . . . . . . . . . . . . . . . 211 M Table 163 - Format device page. . . . . . . . . . . . . . . . . . . . . . 211 M Table 164 - Reporting of default sector formatting support. . . . . . . . 213 M Table 165 - Reporting of changeable sector formatting support . . . . . . 214 M Table 166 - Medium types supported page . . . . . . . . . . . . . . . . . 214 M Table 167 - Notch page. . . . . . . . . . . . . . . . . . . . . . . . . . 215 M Table 168 - Read-write error recovery page. . . . . . . . . . . . . . . . 217 M Table 169 - Error recovery bit definitions. . . . . . . . . . . . . . . . 218 M Table 170 - Combined error recovery parameter descriptions. . . . . . . . 219 M Table 171 - Rigid disk drive geometry page. . . . . . . . . . . . . . . . 224 M Table 172 - Rotational position locking . . . . . . . . . . . . . . . . . 225 M Table 173 - Verify error recovery page. . . . . . . . . . . . . . . . . . 226 M Table 174 - Commands for sequential-access devices. . . . . . . . . . . . 236 M Table 175 - ERASE command . . . . . . . . . . . . . . . . . . . . . . . . 238 M Table 176 - LOAD UNLOAD command . . . . . . . . . . . . . . . . . . . . . 239 M Table 177 - LOCATE command. . . . . . . . . . . . . . . . . . . . . . . . 240 M Table 178 - READ command. . . . . . . . . . . . . . . . . . . . . . . . . 241 M Table 179 - READ BLOCK LIMITS command . . . . . . . . . . . . . . . . . . 243 M Table 180 - READ BLOCK LIMITS data. . . . . . . . . . . . . . . . . . . . 243 M Table 181 - READ POSITION command . . . . . . . . . . . . . . . . . . . . 244 M Table 182 - READ POSITION data format . . . . . . . . . . . . . . . . . . 244 M Table 183 - READ REVERSE command. . . . . . . . . . . . . . . . . . . . . 246 M Table 184 - RECOVER BUFFERED DATA command . . . . . . . . . . . . . . . . 247 M Table 185 - RELEASE UNIT command. . . . . . . . . . . . . . . . . . . . . 248 M Table 186 - RESERVE UNIT command. . . . . . . . . . . . . . . . . . . . . 249 M Table 187 - REWIND command. . . . . . . . . . . . . . . . . . . . . . . . 250 M Table 188 - SPACE command . . . . . . . . . . . . . . . . . . . . . . . . 251 M Table 189 - Code field definition . . . . . . . . . . . . . . . . . . . . 251 M Table 190 - VERIFY command. . . . . . . . . . . . . . . . . . . . . . . . 253 M Table 191 - WRITE command . . . . . . . . . . . . . . . . . . . . . . . . 254 M Table 192 - WRITE FILEMARKS command . . . . . . . . . . . . . . . . . . . 256 M Table 193 - Diagnostic page codes . . . . . . . . . . . . . . . . . . . . 257 M Table 194 - Log page codes. . . . . . . . . . . . . . . . . . . . . . . . 257 M Table 195 - Device-specific parameter . . . . . . . . . . . . . . . . . . 258 M Table 196 - Buffered modes. . . . . . . . . . . . . . . . . . . . . . . . 258 M Table 197 - Speed field definition. . . . . . . . . . . . . . . . . . . . 258 M Table 198 - Sequential-access density codes . . . . . . . . . . . . . . . 259 M Table 199 - Mode page codes . . . . . . . . . . . . . . . . . . . . . . . 260 M Table 200 - Device configuration page . . . . . . . . . . . . . . . . . . 261 M Table 201 - EOD formats . . . . . . . . . . . . . . . . . . . . . . . . . 263 M Table 202 - Medium partition page(1). . . . . . . . . . . . . . . . . . . 264 M Table 203 - Medium partition page(2-4). . . . . . . . . . . . . . . . . . 265 M Table 204 - Read-write error recovery page. . . . . . . . . . . . . . . . 265 M Table 205 - Commands for printer devices. . . . . . . . . . . . . . . . . 269 M Table 206 - FORMAT command. . . . . . . . . . . . . . . . . . . . . . . . 270 M Table 207 - Format type . . . . . . . . . . . . . . . . . . . . . . . . . 270 M Table 208 - PRINT command . . . . . . . . . . . . . . . . . . . . . . . . 271 M Table 209 - RECOVER BUFFERED DATA command . . . . . . . . . . . . . . . . 271 M Table 210 - SLEW AND PRINT command. . . . . . . . . . . . . . . . . . . . 272 M Table 211 - STOP PRINT command. . . . . . . . . . . . . . . . . . . . . . 273 M Table 212 - SYNCHRONIZE BUFFER command. . . . . . . . . . . . . . . . . . 273 M Table 213 - Diagnostic page codes . . . . . . . . . . . . . . . . . . . . 274 M Table 214 - Log page codes. . . . . . . . . . . . . . . . . . . . . . . . 274 M Table 215 - Printer device-specific parameter . . . . . . . . . . . . . . 274 M Table 216 - Mode page codes . . . . . . . . . . . . . . . . . . . . . . . 275 M Table 217 - Parallel printer interface. . . . . . . . . . . . . . . . . . 275 M Table 218 - Parity select . . . . . . . . . . . . . . . . . . . . . . . . 276 M Table 219 - VFU control byte. . . . . . . . . . . . . . . . . . . . . . . 276 M Table 220 - Printer options . . . . . . . . . . . . . . . . . . . . . . . 277 M Table 221 - Font identification . . . . . . . . . . . . . . . . . . . . . 277 M Table 222 - Slew mode . . . . . . . . . . . . . . . . . . . . . . . . . . 278 M Table 223 - Line slew . . . . . . . . . . . . . . . . . . . . . . . . . . 278 M Table 224 - Form slew . . . . . . . . . . . . . . . . . . . . . . . . . . 279 M Table 225 - Data termination option . . . . . . . . . . . . . . . . . . . 279 M Table 226 - Serial printer interface. . . . . . . . . . . . . . . . . . . 280 M Table 227 - Parity selection. . . . . . . . . . . . . . . . . . . . . . . 281 M Table 228 - Pacing protocol . . . . . . . . . . . . . . . . . . . . . . . 281 M Table 229 - Commands for processor devices. . . . . . . . . . . . . . . . 284 M Table 230 - RECEIVE command . . . . . . . . . . . . . . . . . . . . . . . 284 M Table 231 - SEND command. . . . . . . . . . . . . . . . . . . . . . . . . 285 M Table 232 - SEND command - AEN data format. . . . . . . . . . . . . . . . 285 M Table 233 - Diagnostic page codes . . . . . . . . . . . . . . . . . . . . 286 M Table 234 - Log page codes. . . . . . . . . . . . . . . . . . . . . . . . 286 M Table 235 - Commands for write-once devices . . . . . . . . . . . . . . . 289 M Table 236 - Example mixed mode CD-ROM disc layout . . . . . . . . . . . . 293 M Table 237 - MSF address format. . . . . . . . . . . . . . . . . . . . . . 298 M Table 238 - Commands for CD-ROM device. . . . . . . . . . . . . . . . . . 300 M Table 239 - PAUSE RESUME command. . . . . . . . . . . . . . . . . . . . . 301 M Table 240 - PLAY AUDIO(10) command. . . . . . . . . . . . . . . . . . . . 302 M Table 241 - PLAY AUDIO(12) command. . . . . . . . . . . . . . . . . . . . 303 M Table 242 - PLAY AUDIO MSF command. . . . . . . . . . . . . . . . . . . . 304 M Table 243 - PLAY AUDIO TRACK INDEX command. . . . . . . . . . . . . . . . 305 M Table 244 - PLAY AUDIO TRACK RELATIVE(10) command . . . . . . . . . . . . 306 M Table 245 - PLAY AUDIO TRACK RELATIVE(12) command . . . . . . . . . . . . 307 M Table 246 - READ CD-ROM CAPACITY command. . . . . . . . . . . . . . . . . 308 M Table 247 - READ CAPACITY data format . . . . . . . . . . . . . . . . . . 309 M Table 248 - READ HEADER command . . . . . . . . . . . . . . . . . . . . . 309 M Table 249 - READ HEADER data format . . . . . . . . . . . . . . . . . . . 309 M Table 250 - CD-ROM data mode codes. . . . . . . . . . . . . . . . . . . . 310 M Table 251 - READ SUB-CHANNEL command. . . . . . . . . . . . . . . . . . . 311 M Table 252 - Sub-channel data format codes . . . . . . . . . . . . . . . . 311 M Table 253 - Sub-Q channel data format . . . . . . . . . . . . . . . . . . 312 M Table 254 - Audio status codes. . . . . . . . . . . . . . . . . . . . . . 313 M Table 255 - ADR sub-channel Q field . . . . . . . . . . . . . . . . . . . 313 M Table 256 - Sub-channel Q control bits. . . . . . . . . . . . . . . . . . 313 M Table 257 - CD-ROM current position data format . . . . . . . . . . . . . 315 M Table 258 - Media catalogue number data format. . . . . . . . . . . . . . 315 M Table 259 - Track international standard recording code data format . . . 316 M Table 260 - READ TOC command. . . . . . . . . . . . . . . . . . . . . . . 318 M Table 261 - READ TOC data format  . . . . . . . . . . . . . . . . . . . . 318 M Table 262 - Diagnostic page codes . . . . . . . . . . . . . . . . . . . . 320 M Table 263 - Log page codes. . . . . . . . . . . . . . . . . . . . . . . . 320 M Table 264 - CD-ROM medium type codes. . . . . . . . . . . . . . . . . . . 320 M Table 265 - CD-ROM device-specific parameter. . . . . . . . . . . . . . . 321 M Table 266 - CD-ROM density codes. . . . . . . . . . . . . . . . . . . . . 321 M Table 267 - Mode page codes . . . . . . . . . . . . . . . . . . . . . . . 322 M Table 268 - CD-ROM audio control parameters page. . . . . . . . . . . . . 322 M Table 269 - Multiplier for LBAs . . . . . . . . . . . . . . . . . . . . . 323 M Table 270 - Output port channel selection . . . . . . . . . . . . . . . . 323 M Table 271 - CD-ROM parameters page. . . . . . . . . . . . . . . . . . . . 324 M Table 272 - Inactivity timer multiplier values. . . . . . . . . . . . . . 324 M Table 273 - Read error recovery parameters page . . . . . . . . . . . . . 325 M Table 274 - Error recovery bit settings . . . . . . . . . . . . . . . . . 326 M Table 275 - CD-ROM error recovery descriptions. . . . . . . . . . . . . . 326 M Table 276 - Verify error recovery parameters page . . . . . . . . . . . . 331aM Table 277 - Commands for scanner devices. . . . . . . . . . . . . . . . . 335aM Table 278 - GET DATA BUFFER STATUS command. . . . . . . . . . . . . . . . 336oM Table 279 - Data buffer status format . . . . . . . . . . . . . . . . . . 336 M Table 280 - GET WINDOW command. . . . . . . . . . . . . . . . . . . . . . 338 M Table 281 - Get window data header. . . . . . . . . . . . . . . . . . . . 338 M Table 282 - Window descriptor bytes . . . . . . . . . . . . . . . . . . . 339 M Table 283 - Image composition codes . . . . . . . . . . . . . . . . . . . 340 M Table 284 - Padding types . . . . . . . . . . . . . . . . . . . . . . . . 341 M Table 285 - Compression types and arguments . . . . . . . . . . . . . . . 341 M Table 286 - OBJECT POSITION command . . . . . . . . . . . . . . . . . . . 342 M Table 287 - Position function . . . . . . . . . . . . . . . . . . . . . . 342 M Table 288 - READ command. . . . . . . . . . . . . . . . . . . . . . . . . 344 M Table 289 - Data type codes . . . . . . . . . . . . . . . . . . . . . . . 344 M Table 290 - SCAN command. . . . . . . . . . . . . . . . . . . . . . . . . 345 M Table 291 - SEND command. . . . . . . . . . . . . . . . . . . . . . . . . 345 M Table 292 - SET WINDOW command. . . . . . . . . . . . . . . . . . . . . . 346 M Table 293 - Set window data header. . . . . . . . . . . . . . . . . . . . 346 M Table 294 - Diagnostic page codes . . . . . . . . . . . . . . . . . . . . 347 M Table 295 - Log page codes. . . . . . . . . . . . . . . . . . . . . . . . 347 M Table 296 - Mode page codes . . . . . . . . . . . . . . . . . . . . . . . 348 M Table 297 - Measurement units page. . . . . . . . . . . . . . . . . . . . 348 M Table 298 - Basic measurement units . . . . . . . . . . . . . . . . . . . 349 M Table 299 - Commands for optical memory devices . . . . . . . . . . . . . 353 M Table 300 - ERASE(10) command . . . . . . . . . . . . . . . . . . . . . . 354 M Table 301 - ERASE(12) command . . . . . . . . . . . . . . . . . . . . . . 355 M Table 302 - MEDIUM SCAN command . . . . . . . . . . . . . . . . . . . . . 356 M Table 303 - MEDIUM SCAN parameter list. . . . . . . . . . . . . . . . . . 357 M Table 304 - READ(12) command. . . . . . . . . . . . . . . . . . . . . . . 358 M Table 305 - READ DEFECT DATA(12) command. . . . . . . . . . . . . . . . . 358 M Table 306 - READ DEFECT DATA(12) list header. . . . . . . . . . . . . . . 359 M Table 307 - READ GENERATION command . . . . . . . . . . . . . . . . . . . 360 M Table 308 - Maximum generation data block . . . . . . . . . . . . . . . . 360 M Table 309 - READ UPDATED BLOCK(10) command. . . . . . . . . . . . . . . . 361 M Table 310 - SEARCH DATA(12) commands. . . . . . . . . . . . . . . . . . . 362 M Table 311 - SET LIMITS(12) command. . . . . . . . . . . . . . . . . . . . 362 M Table 312 - UPDATE BLOCK command. . . . . . . . . . . . . . . . . . . . . 363 M Table 313 - VERIFY command. . . . . . . . . . . . . . . . . . . . . . . . 364 M Table 314 - VERIFY(12) command. . . . . . . . . . . . . . . . . . . . . . 365 M Table 315 - WRITE(10) command . . . . . . . . . . . . . . . . . . . . . . 366 M Table 316 - WRITE(12) command . . . . . . . . . . . . . . . . . . . . . . 367 M Table 317 - WRITE AND VERIFY(10) command. . . . . . . . . . . . . . . . . 367 M Table 318 - WRITE AND VERIFY(12) command. . . . . . . . . . . . . . . . . 368 M Table 319 - Diagnostic page codes . . . . . . . . . . . . . . . . . . . . 369 M Table 320 - Log page codes. . . . . . . . . . . . . . . . . . . . . . . . 369 M Table 321 - Optical memory medium-type codes. . . . . . . . . . . . . . . 369 M Table 322 - Optical memory device specific parameter. . . . . . . . . . . 370 M Table 323 - Optical memory density codes. . . . . . . . . . . . . . . . . 370 M Table 324 - Mode page codes . . . . . . . . . . . . . . . . . . . . . . . 371 M Table 325 - Optical memory page . . . . . . . . . . . . . . . . . . . . . 372 M Table 326 - Volume tag information format . . . . . . . . . . . . . . . . 376 M Table 327 - Commands for medium changer devices . . . . . . . . . . . . . 377 M Table 328 - EXCHANGE MEDIUM command . . . . . . . . . . . . . . . . . . . 378 M Table 329 - INITIALIZE ELEMENT STATUS command . . . . . . . . . . . . . . 379 M Table 330 - MOVE MEDIUM command . . . . . . . . . . . . . . . . . . . . . 380 M Table 331 - POSITION TO ELEMENT command . . . . . . . . . . . . . . . . . 381 M Table 332 - READ ELEMENT STATUS command . . . . . . . . . . . . . . . . . 382 M Table 333 - Element type code . . . . . . . . . . . . . . . . . . . . . . 382 M Table 334 - Element status data . . . . . . . . . . . . . . . . . . . . . 383 M Table 335 - Element status page . . . . . . . . . . . . . . . . . . . . . 385 M Table 336 - Medium transport element descriptor . . . . . . . . . . . . . 386 M Table 337 - Storage element descriptor. . . . . . . . . . . . . . . . . . 387 M Table 338 - Import export element descriptor. . . . . . . . . . . . . . . 388 M Table 339 - Data transfer element descriptor. . . . . . . . . . . . . . . 389 M Table 340 - REQUEST VOLUME ELEMENT ADDRESS command. . . . . . . . . . . . 390 M Table 341 - Volume element address header format. . . . . . . . . . . . . 391 M Table 342 - RELEASE command . . . . . . . . . . . . . . . . . . . . . . . 392 M Table 343 - RESERVE command . . . . . . . . . . . . . . . . . . . . . . . 393 M Table 344 - Data format of element list descriptors . . . . . . . . . . . 394 M Table 345 - SEND VOLUME TAG command . . . . . . . . . . . . . . . . . . . 395 M Table 346 - Send volume tag action codes. . . . . . . . . . . . . . . . . 396 M Table 347 - Send volume tag parameters format . . . . . . . . . . . . . . 396 M Table 348 - Diagnostic page codes . . . . . . . . . . . . . . . . . . . . 398 M Table 349 - Log page codes. . . . . . . . . . . . . . . . . . . . . . . . 398 M Table 350 - Mode page codes . . . . . . . . . . . . . . . . . . . . . . . 399 M Table 351 - Device capabilities page. . . . . . . . . . . . . . . . . . . 399 M Table 352 - Element address assignment page . . . . . . . . . . . . . . . 400 M Table 353 - Transport geometry parameters page. . . . . . . . . . . . . . 403 M Table 354 - Commands for communications devices . . . . . . . . . . . . . 407 M Table 355 - GET MESSAGE(6) command. . . . . . . . . . . . . . . . . . . . 408 M Table 356 - GET MESSAGE(10) command . . . . . . . . . . . . . . . . . . . 408 M Table 357 - GET MESSAGE(12) command . . . . . . . . . . . . . . . . . . . 409 M Table 358 - SEND MESSAGE(6) command . . . . . . . . . . . . . . . . . . . 410 M Table 359 - SEND MESSAGE(10) command. . . . . . . . . . . . . . . . . . . 410 M Table 360 - SEND MESSAGE(12) command. . . . . . . . . . . . . . . . . . . 411 M Table 361 - Diagnostic page codes . . . . . . . . . . . . . . . . . . . . 412 M Table 362 - Log page codes. . . . . . . . . . . . . . . . . . . . . . . . 412 M Table 363 - Mode page codes . . . . . . . . . . . . . . . . . . . . . . . 413 M Table B.1 - Fast SCSI jitter budget . . . . . . . . . . . . . . . . . . . 418 M Table B.2 - Mapping of jitter to SCSI . . . . . . . . . . . . . . . . . . 418 M Table D.1 - ASC and ASCQ assignments. . . . . . . . . . . . . . . . . . . 421 M Table D.2 - SCSI-2 Operation Codes. . . . . . . . . . . . . . . . . . . . 427 M Table E.1 - Vendor identification list. . . . . . . . . . . . . . . . . . 431            Foreword  G This Small Computer System Interface -2 standard is designed to provideLI an efficient peer-to-peer I/O bus with up to 16 devices, including one or F more hosts.  Data may be transferred asynchronously at rates that onlyC depend on device implementation and cable length.  Synchronous data J transfers are supported at rates up to 10 mega-transfers per second.  WithJ the 32-bit wide data transfer option, data rates of up to 40 megabytes perJ second are possible.  This standard includes command sets for magnetic andE optical disks, tapes, printers, processors, CD-ROMs, scanners, medium % changers, and communications devices.          Introduction  F This part of ANSI X3.131-199x replaces ANSI X3.131-1986 Small Computer System Interface.   0 The clauses contain material as described below.  (    Clause 1         describes the scope.  3    Clause 2         lists the normative references.e  E    Clause 3         provides a glossary common to the whole document.r  :    Clause 4         provides descriptions and conventions.  ;    Clause 5         describes the physical characteristics.   K    Clause 6         describes the logical characteristics of the interface.   D    Clause 7         describes the SCSI command and status structure.  O    Clause 8         specifies those commands that have a consistent meaning for1%                     all device types.d  A    Clause 9         specifies commands for direct-access devices.t  I    Clause 10            specifies commands for sequential-access devices.m  ?    Clause 11            specifies commands for printer devices.   A    Clause 12            specifies commands for processor devices.a  B    Clause 13            specifies commands for write-once devices.  >    Clause 14            specifies commands for CD-ROM devices.  ?    Clause 15            specifies commands for scanner devices.   F    Clause 16            specifies commands for optical memory devices.  F    Clause 17            specifies commands for medium changer devices.  F    Clause 18            specifies commands for communications devices.  9    Annex A              illustrates SCSI signal sequence.   8    Annex B              illustrates fast SCSI skew time.  H    Annex C              describes other SCSI standardization activities.  M    Annex D              contains SCSI-2 additional sense codes and operation  /                         codes in numeric order.   K    Annex E              contains the list of SCSI-2 vendor identifications.e  J The SCSI protocol is designed to provide an efficient peer-to-peer I/O bus@ with up to 16 devices, including one or more hosts.  Data may be> transferred asynchronously at rates that only depend on deviceJ implementation and cable length.  Synchronous data transfers are supportedG at rates up to 10 mega-transfers per second.  With the 32-bit wide data3J transfer option, data rates of up to 40 megabytes per second are possible.  C SCSI-2 includes command sets for magnetic and optical disks, tapes, = printers, processors, CD-ROMs, scanners, medium changers, and  communications devices.   A In 1985, when the first SCSI standard was being finalized several G manufacturers wanted to increase the mandatory requirements of SCSI and H to define further features for direct-access devices.  Rather than delayI the SCSI standard, formed an ad hoc group was formed to develop a working I paper that was eventually called the Common Command Set (CCS).  Many disk 0 products were designed using this working paper.  H In parallel with the development of the CCS working paper, work began onF an enhanced SCSI standard which was named SCSI-2.  SCSI-2 included theH results of the CCS working paper and extended them to all device types. E It also added caching commands, performance enhancement features, and B other worthwhile functions.  While SCSI-2 has gone well beyond theE original SCSI standard (now referred to as SCSI-1), it retains a high , degree of compatibility with SCSI-1 devices.  I SCSI-2 has evolved significantly from SCSI-1 with the new document nearly C three times larger.  Most of the changes are additions, but severala obsolete options were removed:!    a)     Single initiator option (    b)     Non-arbitrating systems option5    c)     The SCSI-1 alternative 1 shielded connector9(    d)     Non-extended sense data option$    e)     Reservation queuing option+    f)     The read-only device command set.   - There are several new low-level requirements:      a)     Parity is now required=    b)     Initiators are required to provide terminator power @    c)     The arbitration delay was increased from 2.2 to 2.4 us*    d)     Message support is now required.  % Several low-level options were added: =    a)     Wide SCSI (up to 32 bits wide using a second cable)(N    b)     Fast SCSI (synchronous data transfers of up to 10 mega-transfers per           second) M    c)     Command queuing (up to 256 commands per initiator per logical unit)t8    d)     High-density connector alternatives were added)    e)     Asynchronous event notification )    f)     Extended contingent allegiance.   & New command sets were added including:,    a)     CD-ROM (replaces read-only device)    b)     Scanner deviceH    c)     Optical memory device (provides for write-once, read-only, and           erasable media)     d)     Medium changer devicet    e)     Communications device    All command sets were enhanced:D"    a)     Device models were added%    b)     Extended sense was expandedD'    c)     The INQUIRY data was expanded K    d)     The MODE SELECT and MODE SENSE commands were paged for all device            types N    e)     The CHANGE DEFINITION, LOG SELECT, LOG SENSE, READ BUFFER, and WRITE9           BUFFER commands were added for all device types K    f)     The COPY command definition was expanded to include inexact block 1           size handling and an image copy option.nH    g)     The direct-access device command set was enhanced to add cacheH           management, several new commands and to provide more initiator(           control over defect managementH    h)     The sequential-access device command set was enhanced to add a#           partitioned media concept L    i)     The printer device command set was enhanced by adding several mode           pagessL    j)     The write-once (optical) device command set was enhanced by addingH           several new commands plus extending several command descriptorH           blocks to twelve bytes to accommodate larger transfer lengths.          ) draft proposed American National Standard  for Information Systems       ' Information technology - Small Computer  System Interface-2   1 Scope   G This standard defines an input/output bus for interconnecting computers2D and peripheral devices.  It defines extensions to the Small ComputerH System Interface (ISO 9316:1989), referred to herein as SCSI-1.  It alsoH provides more complete standardization of the previously defined commandA sets.  It includes the necessary specification of the mechanical, D electrical, and functional characteristics of the interface to allowF inter-operability of conforming devices.  This standard is referred toH herein as SCSI-2.  The term SCSI is used wherever it is not necessary to% distinguish between the two versions.      2 Normative references  F The following standards contain provisions which, through reference inB this text, constitute provisions of this standard.  At the time ofJ publication, the editions indicated were valid.  All standards are subjectA to revision, and parties to agreements based on this standard are E encouraged to investigate the possibility of applying the most recent B editions of the standards indicated below.  Members of IEC and ISO0 maintain registers of currently valid standards.  J ISO/IEC 10149:1989, Information technology - Data interchange on read-only# 120 mm optical data disks (CD-ROM).d  0 IEC 908:1987, Compact Disc Digital Audio System.  G American National Standard ANSI BSR X3.170A-1991, Enhanced Small DeviceS
 Interface.  F EIA RS-485-1983, Standard for Electrical Characteristics of Generators= and Receivers for use in Balanced Digital Multipoint Systems.4    ( 3 Definitions, symbols and abbreviations     3.1 Definitions9  C For the purposes of this standard, the following definitions apply.   G 3.1.1 active I/O process: An I/O process that is presently in execution 
 (not queued).   ) 3.1.2 byte: Indicates an 8-bit construct.   G 3.1.3 command descriptor block (CDB): The structure used to communicate ' commands from an initiator to a target.l  J 3.1.4 command queue: The queue used to store the queued I/O processes (see 7.8).   H 3.1.5 connect: The initiator function that selects a target to establishG a nexus and to start an I/O process.  The connection that results is an  initial connection.d  J 3.1.6 connection: An initial connection or reconnection.  A connection can1 only occur between one initiator and one target.    A 3.1.7 contact: The electrically-conductive portion of a connector . associated with a single conductor in a cable.  G 3.1.8 contingent allegiance: A condition typically generated by a CHECK0G CONDITION status during which a target preserves sense data (see 7.6.).S  I 3.1.9 current I/O process: The I/O process that is presently connected onM
 the SCSI bus.n  F 3.1.10 disconnect: The action that occurs when an SCSI device releasesA control of the SCSI bus, allowing it to go to the BUS FREE phase.D  B 3.1.11 extended contingent allegiance: A condition generated by anI INITIATE RECOVERY message to assist in extended error recovery proceduresa% in multi-initiator systems (see 7.7).   5 3.1.12 field: A group of one or more contiguous bits.g  J 3.1.13 host adapter: A device which connects between a host system and theC SCSI bus.  The device usually performs the lower layers of the SCSI.H protocol and normally operates in the initiator role.  This function may# be integrated into the host system.   C 3.1.14 initial connection: An initial connection is the result of adI connect and it exists from the assertion of the BSY signal in a SELECTIONc+ phase until the next BUS FREE phase occurs.   C 3.1.15 initiator: An SCSI device that requests an I/O process to ben, performed by another SCSI device (a target).  I 3.1.16 invalid: An illegal (reserved) or unsupported field or code value.   I 3.1.17 I/O process: An I/O process consists of one initial connection andeI zero or more reconnections, all pertaining to a single command or a grouptF of linked commands.  More specifically, the connection(s) pertain to aG nexus in which zero or more command descriptor blocks are transferred. hH An I/O process begins with the establishment of a nexus.  An I/O processH normally ends with the BUS FREE phase following successful transfer of aI COMMAND COMPLETE or a RELEASE RECOVERY message.  An I/O process also endscH with the BUS FREE phase following an ABORT, ABORT TAG, BUS DEVICE RESET,@ CLEAR QUEUE message, or a hard RESET condition, or an unexpected disconnect occurs.  I 3.1.18 I_T nexus: A nexus which exists between an initiator and a target.s  H 3.1.19 I_T_L nexus: A nexus which exists between an initiator, a target,D and a logical unit.  This relationship replaces the prior I_T nexus.  H 3.1.20 I_T_R nexus: A nexus which exists between an initiator, a target,F and a target routine.  This relationship replaces the prior I_T nexus.  D 3.1.21 I_T_x nexus: A nexus which is either an I_T_L or I_T_R nexus.  G 3.1.22 I_T_L_Q nexus: A nexus between an initiator, a target, a logicalsJ unit, and a queue tag following the successful receipt of one of the queue@ tag messages.  This relationship replaces the prior I_T_L nexus.  B 3.1.23 I_T_x_y nexus: A nexus which is either an I_T_x or I_T_L_Q.  @ 3.1.24 logical block: A unit of data supplied or requested by an
 initiator.  H 3.1.25 logical unit: A physical or virtual peripheral device addressable through a target.p  C 3.1.26 logical unit number: An encoded three-bit identifier for thee
 logical unit.s  J 3.1.27 mandatory: The referenced item is required to claim compliance with this standard.  E 3.1.28 nexus: A relationship that begins with the establishment of an H initial connection and ends with the completion of the I/O process.  TheI relationship may be restricted to specify a single logical unit or target ? routine by the successful transfer of an IDENTIFY message.  The F relationship may be further restricted by the successful transfer of a queue tag message.  B 3.1.29 one: A true signal value or a true condition of a variable.  H 3.1.30 optional: The referenced item is not required to claim complianceJ with this standard.  Implementation of an optional item must be as defined in this standard.r  G 3.1.31 page: Several commands use regular parameter structures that are G referred to as pages.  These pages are identified with a value known asa a page code.  nB 3.1.32 peripheral device: A physical peripheral device that can be@ attached to an SCSI device, which connects to the SCSI bus.  TheD peripheral device and the SCSI device (peripheral controller) may beJ physically packaged together.  Often there is a one-to-one mapping betweenI peripheral devices and logical units, but this is not required.  ExamplessG of peripheral devices are: magnetic disks, printers, optical disks, and  magnetic tapes.t  H 3.1.33 queue tag: The value associated with an I/O process that uniquelyI identifies it from other queued I/O processes in the logical unit for ther same initiator.u  G 3.1.34 queued I/O process: An I/O process that is in the command queue.m  J 3.1.35 reconnect: The act of reviving a nexus to continue an I/O process. H A target reconnects to an initiator by using the RESELECTION and MESSAGEI IN phases after winning arbitration.  An initiator reconnects to a targetdG by using the SELECTION and MESSAGE OUT phases after winning arbitrationp (see 7.5.2).  G 3.1.36 reconnection: A reconnection is the result of a reconnect and itwI exists from the assertion of the BSY signal in a SELECTION or RESELECTIONa+ phase until the next BUS FREE phase occurs.h  F 3.1.37 reserved: Identifies bits, fields, and code values that are set! aside for future standardization.e  H 3.1.38 SCSI address: The hex representation of the unique address (0-15)H assigned to an SCSI device.  This address would normally be assigned and2 set in the SCSI device during system installation.  F 3.1.39 SCSI ID: The bit-significant representation of the SCSI address- referring to one of the signal lines DB(7-0).u  E 3.1.40 SCSI device: A host adapter or a target controller that can bee attached to the SCSI bus.n  G 3.1.41 signal assertion: The act of driving a signal to the true state.o  I 3.1.42 signal negation: The act of driving a signal to the false state ormH allowing the cable terminators to bias the signal to the false state (by4 placing the driver in the high impedance condition).  H 3.1.43 signal release: The act of allowing the cable terminators to biasJ the signal to the false state (by placing the driver in the high impedance condition).u  I 3.1.44 status: One byte of information sent from a target to an initiatorn  upon completion of each command.  H 3.1.45 target: An SCSI device that performs an operation requested by an
 initiator.  G 3.1.46 target routine: A target routine is an I/O process directed to ay. target, and not to a logical unit (see 6.6.7).  H 3.1.47 third-party: When used in reference to COPY commands, third-partyE means a COPY command issued to one device to perform a copy operationsI between two other devices.  When used in reference to RESERVE, or RELEASEaJ commands, third-party means a reservation made on behalf of another deviceE (e.g. A processor device requests that a direct-access device reserved8 itself for exclusive use by a sequential-access device).  H 3.1.48 unexpected disconnect: A disconnection that occurs as a result of# an exception condition (see 6.1.1).e  F 3.1.49 vendor-specific (VS): Something (e.g. a bit, field, code value,I etc.) that is not defined by this standard and may be used differently ini various implementations.  E 3.1.50 zero: A false signal value or a false condition of a variable.s   3.2 Symbols and abbreviations   5 AEN       Asynchronous event notification (see 7.5.5)u AWG       American Wire Gauget LSB       Least significant bit  LUN       Logical unit numberi MSB       Most significant bit! SCSI      Either SCSI-1 or SCSI-2 @ SCSI-1       The Small Computer System Interface (ISO 9316:1989)D SCSI-2       The Small Computer System Interface - 2 (this atandard)      	 4 Generala   4.1 Overview  F SCSI is a local I/O bus that can be operated over a wide range of dataA rates.  The primary objective of the interface is to provide hostoD computers with device independence within a class of devices.  Thus,G different disk drives, tape drives, printers, optical media drives, andoB other devices can be added to the host computers without requiringH modifications to generic system hardware or software.  Provision is madeE for the addition of special features and functions through the use ofoG vendor unique fields and codes.  Reserved fields and codes are providedi for future standardization.l  G A second key objective of SCSI-2 is to provide compatibility with thosepH SCSI-1 devices that support bus parity and that meet conformance level 2G of SCSI-1.  While some previously vendor unique commands and parameterssJ have been defined by the SCSI-2 standard, devices meeting SCSI-1 and SCSI-D 2 can co-exist on the same bus.  It is intended that those operatingE systems providing support for both command sets be able to operate ineJ environments mixing SCSI-1 and SCSI-2 devices.  Properly conforming SCSI-1E devices, both initiators and targets, should respond in an acceptablegA manner to reject SCSI-2 protocol extensions.  All SCSI-2 protocoltH extensions are designed to be permissive of such rejections and to allowH the SCSI-1 device to continue operation without requiring the use of the
 extension.  H A third key objective of SCSI-2 is to move device-dependent intelligence? out to the SCSI-2 devices.  The command set definitions allow a D sophisticated operating system to obtain all required initializationI information from the attached SCSI-2 devices.  The formalized sequence of I requests identify the type of attached SCSI-2 device, the characteristicsdJ of the device, and all the changeable parameters supported by the device. J Further requests can determine the readiness of the device to operate, theF types of media supported by the device, and all other pertinent systemG information.  Those parameters not required by the operating system fortI operation, initialization, or system tuning are not exposed to the SCSI-2 7 interface, but are managed by the SCSI-2 device itself.c  G The interface uses logical rather than physical addressing for all datatI blocks.  For direct-access devices, each logical unit may be interrogatedaF to determine how many blocks it contains.  A logical unit may coincide( with all or part of a peripheral device.  H The interface protocol includes provision for the connection of multipleI initiators (SCSI devices capable of initiating an operation) and multiplecF targets (SCSI devices capable of responding to a request to perform anI operation).  Distributed arbitration (i.e. bus-contention logic) is builtsJ into the architecture of SCSI.  A priority system awards interface controlK to the highest priority SCSI device that is contending for use of the bus. tH The time to complete arbitration is independent of the number of devices< that are contending and can be completed in less than 10 us.  F There are two electrical alternatives: single-ended and differential. G Single-ended and differential devices are electrically incompatible and * can not be mixed on the same physical bus.  I Provision is made for cable lengths up to 25 m using differential driversaC and receivers.  A single-ended driver and receiver configuration isrD defined for cable lengths of up to 6 m and is primarily intended for applications within a cabinet.  B Arbitration is defined to permit multiple initiators and to permitG concurrent I/O operations.  All SCSI devices are required to be capablenA of operating with the defined asynchronous transfer protocol.  InhJ addition, an optional synchronous transfer protocol is defined.  A messageH protocol for control of the interface is also specified.  In most cases,C messages are not directly apparent to the host computer software.  I  I Commands are classified as mandatory, optional, or vendor-specific.  SCSIoH devices are required to implement all mandatory commands defined for theG appropriate device type and may implement other commands as well.  SCSIwH devices contain commands that facilitate the writing of self-configuringI software drivers that can discover all necessary attributes without priordA knowledge of specific peripheral characteristics (such as storageNC capacity).  Many commands also implement a very large logical block G address space (232 blocks), although some commands implement a somewhat 2 smaller logical block address space (221 blocks).   I Starting with clause 8 and for each clause on a specific device type, thetG clause is constructed of at least four subclauses.  The first subclausesJ is the model for the device type.  The model establishes the framework forB interpreting the commands for the device type.  The attributes andJ capabilities of the device type are discussed and examples are given.  TheI second subclause defines the commands applicable to the device type.  ThetF third subclause defines the parameters applicable to the device type. H These are the diagnostic parameters, log parameters, mode parameters andA vital product data parameters that are transmitted as part of thepH appropriate commands.  Most of the parameters are formatted into pages. J The fourth subclause gives the definition of terms that apply specifically to that device type. n  G Starting with clause 9 the commands in each of these clauses are uniquedJ to the device type, or they have interpretations, fields, or features thatH are specific for the device type.  Thus, for example, although the WRITEJ command is used for several device types, it has a somewhat different formH for each type, with different parameters and meanings.  Therefore, it is* specified separately for each device type.   4.2 Conventionsa  B Certain words and terms used in this International Standard have aJ specific meaning beyond the normal English meaning.  These words and termsG are defined either in clause 3 or in the text where they first appear.  C Names of signals, phases, messages, commands, statuses, sense keys,vG additional sense codes, and additional sense code qualifiers are in all H uppercase (e.g. REQUEST SENSE).  Lower case is used for words having the normal English meaning.n  F Fields containing only one bit are usually referred to as the name bit instead of the name field.  J Numbers that are not immediately followed by lower-case b or h are decimal values.e  E Numbers immediately followed by lower-case b (xxb) are binary values.   J Numbers immediately followed by lower-case h (xxh) are hexadecimal values.     5 Physical characteristics  H This clause contains the physical definition of SCSI-2.  The connectors,G cables, signals, terminators, and bus timing values needed to implementa the interface are covered.   5.1 Physical description  C SCSI devices are daisy-chained together using a common 50-conductoruI A cable and, optionally, a 68-conductor B cable.  Both ends of each cableeG are terminated.  All signals are common between all SCSI devices on the4H A cable.  In systems that employ the wide SCSI option, wide SCSI devicesG additionally connect to the B cable.  Various width SCSI devices may be  mixed.  K    NOTE 1 An alternate 16-bit single-cable solution and an alternate 32-bit L    solution is being defined and the B cable definition will be removed in a    future version of SCSI.  / Two driver/receiver alternatives are specified:rI    a)     Single-ended drivers and receivers, which allow a maximum cableoG           length of 6 m (primarily for connection within an enclosure).nI    b)     Differential drivers and receivers, which allow a maximum cablei           length of 25 m.a  H The single-ended and differential alternatives are mutually exclusive on the same physical bus.  M    NOTE 2 Use of single-ended drivers and receivers with the fast synchronouss+    data transfer option is not recommended.t   5.2 Cable requirements    H The characteristic impedance of the cable should be no less than 90 ohmsH and no greater than 140 ohms.  The characteristic impedance of the cableC used when implementing the fast synchronous data transfer option is. defined in 5.2.3.:  M    NOTE 3 There are successful single-ended implementations using cables withcL    less than 90 ohms characteristic impedance.  However, system integrity inM    single-ended implementations is improved when the characteristic impedancenD    of the cable is greater than 90 ohms. Cable parameters other thanK    characteristic impedance are critical to system integrity.  Alternative  L    cable parameters are being investigated as a part of a future version of     SCSI.  C A minimum conductor size of 0,080 42 mm2 (28 AWG) should be used toeK minimize noise effects and ensure proper distribution of terminator power. .F A smaller conductor size may be used for signals other than terminator power. n  
    NOTES     lL    4 To minimize discontinuities and signal reflections, cables of differentN    impedances should not be used in the same bus.  Implementations may requireL    trade-offs in shielding effectiveness, cable length, the number of loads,F    transfer rates, and cost to achieve satisfactory system operation. O    5 To minimize discontinuities due to local impedance variation, a flat cabledL    should be spaced at least 1,27 mm (0,050 in) from other cables, any other;    conductor, or the cable itself when the cable is folded.e=    6 Regulatory agencies may require use of larger wire size.:   5.2.1 Single-ended cable  G A 50-conductor flat cable or 25-signal twisted-pair cable shall be useddE for the A cable.  A 68-conductor flat cable or 34-signal twisted-pair > cable shall be used for the B cable if the wide SCSI option isE implemented.  The maximum cumulative cable length shall be 6,0 m.  If F twisted-pair cables are used, then twisted pairs in the cable shall be7 wired to physically opposing contacts in the connector.   ? A stub length of no more than 0,1 m is allowed off the mainline D interconnection within any connected equipment or from any connected point.  M    NOTE 7 Stub clustering should be avoided.  Stubs should be spaced at least     0,3 m apart.p  J SCSI bus termination shall be at each end of the cable and may be internal6 to the SCSI devices that are at the ends of the cable.   5.2.2 Differential cable  G A 50-conductor flat cable or 25-signal twisted-pair cable shall be usedsE for the A cable.  A 68-conductor flat cable or 34-signal twisted-pairi> cable shall be used for the B cable if the wide SCSI option isD implemented.  The maximum cumulative cable length shall be 25 m.  IfF twisted-pair cables are used, then twisted pairs in the cable shall be7 wired to physically opposing contacts in the connector.d  ? A stub length of no more than 0,2 m is allowed off the mainlineCD interconnection within any connected equipment or from any connected point.  J SCSI bus termination shall be at each end of the cable and may be internal6 to the SCSI devices that are at the ends of the cable.  M    NOTE 8 The use of twisted pair cable (either twisted-flat or discrete wireyO    twisted pairs) is strongly recommended.  Without twisted pairs, even at slowsJ    data rates and very short distances, crosstalk between adjacent signals4    causes spurious pulses with differential signals.  ; 5.2.3 Cable requirements for fast synchronous data transferp  I In systems which use the fast synchronous data transfer option (see 5.8),aI the A and B cables should meet the conductor size recommendation in 5.2. tE The cable should have an overall shield suitable for termination in ae shielded connector.u  ? In such systems, the cables shall have the following electricalh characteristics:>    Characteristic impedance:               90 ohms to 132 ohmsN    Signal attenuation:                     0,095 dB maximum per metre at 5 MhzD    Pair-to-pair propagation delay delta:   0,20 ns maximum per metreN    DC resistance:                          0,230 ohms maximum per metre at 20 4                                            degrees C   5.3 Connector requirements  I Two types of connectors are defined: non-shielded and shielded.  The non-nD shielded connectors are typically used for in-cabinet applications. F Shielded connectors are typically used for external applications whereE electromagnetic compatibility (EMC) and electrostatic discharge (ESD)hJ protection may be required.  Either type of connector may be used with the% single-ended or differential drivers.o  ) 5.3.1 Non-shielded connector requirementsg  I Two non-shielded connector alternatives are specified for the A cable andf8 one non-shielded connector is specified for the B cable.  6 5.3.1.1 Non-shielded connector alternative 1 - A cable  I The alternative 1 non-shielded high-density SCSI device connector for theeJ A cable (see figure 1) shall be a 50-conductor connector consisting of twoK rows of 25 female contacts with adjacent contacts 1,27 mm (0,05 in) apart. tD The non-mating portion of the connector is shown for reference only.  E The alternative 1 non-shielded high-density cable connector for the AfH cable (see figure 2) shall be a 50-conductor connector consisting of twoI rows of 25 male contacts with adjacent contacts 1,27 mm (0,05 in) apart. rD The non-mating portion of the connector is shown for reference only.  6 5.3.1.2 Non-shielded connector alternative 2 - A cable  H The alternative 2 non-shielded low-density SCSI device connector for theJ A cable (see figure 3) shall be a 50-conductor connector consisting of twoI rows of 25 male pins with adjacent pins 2,54 mm (0,1 in) apart.  A shroudoH and header body should be used.  The non-mating portion of the connector is shown for reference only.  J The alternative 2 non-shielded low-density cable connector for the A cableG (see figure 4) shall be a 50-conductor connector consisting of two rows H of 25 female contacts with adjacent contacts 2,54 mm (0,1 in) apart.  It- is recommended that keyed connectors be used.a  ( 5.3.1.3 Non-shielded connector - B cable  H The non-shielded high-density SCSI device connector for the B cable (seeH figure 1) shall be a 68-conductor connector consisting of two rows of 34I female contacts with adjacent contacts 1,27 mm (0,05 in) apart.  The non- < mating portion of the connector is shown for reference only.  I The non-shielded high-density cable connector for the B cable (see figurerF 2) shall be a 68-conductor connector consisting of two rows of 34 maleH contacts with adjacent contacts 1,27 mm (0,05 in) apart.  The non-mating5 portion of the connector is shown for reference only.o                                                                                                    K    Figure 1 - 50/68-contact non-shielded high-density SCSI device connectorh/                               (A cable/B cable)u                                                                                                            H       Figure 2 - 50/68-contact non-shielded high-density cable connector/                               (A cable/B cable)a                                                                                                        I      Figure 3 - 50-contact non-shielded low-density SCSI device connectori+                                   (A cable)a                                                                                                            F         Figure 4 - 50-Contact non-shielded low-density cable connector+                                   (A cable)l    % 5.3.2 Shielded connector requirements   I Two shielded connector alternatives are specified for the A cable and oneeI shielded connector is specified for the B cable.  The connector shieldingtF system should provide a d.c. resistance of less than 10 mohms from theC cable shield at its termination point to the SCSI device enclosure.t  B In order to support daisy-chain connections, SCSI devices that useH shielded connectors should provide two shielded device connectors on theF device enclosure.  These two connectors may be wired one-to-one with aI stub to the SCSI device's drivers and receivers provided the maximum stubrJ length is not violated.  Alternatively, two cables may be run from the twoI shielded connectors to the drivers and receivers so that the maximum stubnB length is not violated.  The length of the cable within the deviceI enclosure is included when calculating the total cable length of the SCSIg bus.  K    NOTE 9 SCSI-1 defined three shielded connector systems in an annex.  The J    alternative 1 shielded connector of SCSI-1 has been replaced by a high-H    density connector in this International Standard.  The alternative 2 G    shielded  connector remains unchanged.  The EUROCARD boxes shielded aN    connector system of SCSI-1 has been deleted in this International Standard.  2 5.3.2.1 Shielded connector alternative 1 - A cable  D The shielded high-density SCSI device connector for the A cable (seeI figure 5) is a 50-conductor connector consisting of two rows of 25 femaledH contacts with adjacent contacts 1,27 mm (0,05 in) apart.  The non-mating5 portion of the connector is shown for reference only.c  H The shielded high-density cable connector for the A cable (see figure 6)F is a 50-conductor connector consisting of two rows of 25 male contactsG with adjacent contacts 1,27 mm (0,05 in) apart.  The non-mating portions- of the connector is shown for reference only.i  2 5.3.2.2 Shielded connector alternative 2 - A cable  H The shielded low-density device connector for the A cable (see figure 7)E is a 50-conductor connector consisting of two rows of ribbon contactsiI spaced 2,16 mm (0,085 in) apart.  The non-mating portion of the connectora is shown for reference only.  G The shielded low-density cable connector for the A cable (see figure 8)iE is a 50-conductor connector consisting of two rows of ribbon contacts5I spaced 2,16 mm (0,085 in) apart.  The non-mating portion of the connectorv is shown for reference only.  $ 5.3.2.3 Shielded connector - B cable  D The shielded high-density SCSI device connector for the B cable (seeI figure 5) is a 68-conductor connector consisting of two rows of 34 femaleoH contacts with adjacent contacts 1,27 mm (0,05 in) apart.  The non-mating5 portion of the connector is shown for reference only.m  H The shielded high-density cable connector for the B cable (see figure 6)F is a 68-conductor connector consisting of two rows of 34 male contactsG with adjacent contacts 1,27 mm (0,05 in) apart.  The non-mating portione- of the connector is shown for reference only.                                                                                                           I      Figure 5 - 50/68-contact shielded high-density SCSI device connectorA/                               (A cable/B cable)t                                                                                                        F         Figure 6 - 50/68-contact shielded high-density cable connector/                               (A cable/B cable)e                                                                                                        G        Figure 7 - 50-contact shielded low-density SCSI device connectort                                                                                                            D           Figure 8 - 50-contact shielded low-density cable connector  # 5.3.3 Connector contact assignmentsi  E The connector contact assignments are defined in tables 1 through 5. sF Table 1 defines which of the other four tables to use and which set of contact assignments to use.i  D           Table 1 - Cross-reference to connector contact assignmentsL +==========================-============-=====-=========-==========-=======+L |                          |   Driver/  |     |         |  Contact |       |L |                          |  receiver  |     |Connector|assignment|Contact|L |     Connector type       |    type    |Cable|  figure |   table  |   set |L |--------------------------+------------+-----+---------+----------+-------|L |Non-shielded alternative 1|Single-ended|  A  |  1 & 2  |      2   |    2  |L |Non-shielded alternative 1|Single-ended|  B  |  1 & 2  |      3   |       |L |Non-shielded alternative 1|Differential|  A  |  1 & 2  |      4   |    2  |L |Non-shielded alternative 1|Differential|  B  |  1 & 2  |      5   |       |L |                          |            |     |         |          |       |L |Non-shielded alternative 2|Single-ended|  A  |  3 & 4  |      2   |    1  |L |Non-shielded alternative 2|Differential|  A  |  3 & 4  |      4   |    1  |L |                          |            |     |         |          |       |L | Shielded alternative 1   |Single-ended|  A  |  5 & 6  |      2   |    2  |L | Shielded alternative 1   |Single-ended|  B  |  5 & 6  |      3   |       |L | Shielded alternative 1   |Differential|  A  |  5 & 6  |      4   |    2  |L | Shielded alternative 1   |Differential|  B  |  5 & 6  |      5   |       |L |                          |            |     |         |          |       |L | Shielded alternative 2   |Single-ended|  A  |  7 & 8  |      2   |    2  |L | Shielded alternative 2   |Differential|  A  |  7 & 8  |      4   |    2  |L +==========================================================================+    A              Table 2 - Single-ended contact assignments - A cable M +================-===============-=========-===============-================+ M |                |  Connector    |         |  Connector    |                | M |                | contact number|  Cable  |contact number |                |tM |      Signal    |---------------|conductor|---------------|    Signal      | M |       name     | Set 2 | Set 1 | number  | Set 1 | Set 2 |     name       |aM |----------------+-------+-------+---------+-------+-------+----------------|mM |      GROUND    |   1   |   1   |  1 |  2 |   2   |  26   |    -DB(0)      |tM |      GROUND    |   2   |   3   |  3 |  4 |   4   |  27   |    -DB(1)      | M |      GROUND    |   3   |   5   |  5 |  6 |   6   |  28   |    -DB(2)      |oM |      GROUND    |   4   |   7   |  7 |  8 |   8   |  29   |    -DB(3)      | M |      GROUND    |   5   |   9   |  9 | 10 |  10   |  30   |    -DB(4)      | M |      GROUND    |   6   |  11   | 11 | 12 |  12   |  31   |    -DB(5)      |eM |      GROUND    |   7   |  13   | 13 | 14 |  14   |  32   |    -DB(6)      | M |      GROUND    |   8   |  15   | 15 | 16 |  16   |  33   |    -DB(7)      |eM |      GROUND    |   9   |  17   | 17 | 18 |  18   |  34   |    -DB(P)      |iM |      GROUND    |  10   |  19   | 19 | 20 |  20   |  35   |    GROUND      |eM |      GROUND    |  11   |  21   | 21 | 22 |  22   |  36   |    GROUND      |nM |      RESERVED  |  12   |  23   | 23 | 24 |  24   |  37   |    RESERVED    |oM |       OPEN     |  13   |  25   | 25 | 26 |  26   |  38   |    TERMPWR     | M |      RESERVED  |  14   |  27   | 27 | 28 |  28   |  39   |    RESERVED    |-M |      GROUND    |  15   |  29   | 29 | 30 |  30   |  40   |    GROUND      |aM |      GROUND    |  16   |  31   | 31 | 32 |  32   |  41   |    -ATN        |tM |      GROUND    |  17   |  33   | 33 | 34 |  34   |  42   |    GROUND      |oM |      GROUND    |  18   |  35   | 35 | 36 |  36   |  43   |    -BSY        |sM |      GROUND    |  19   |  37   | 37 | 38 |  38   |  44   |    -ACK        |nM |      GROUND    |  20   |  39   | 39 | 40 |  40   |  45   |    -RST        |mM |      GROUND    |  21   |  41   | 41 | 42 |  42   |  46   |    -MSG        |rM |      GROUND    |  22   |  43   | 43 | 44 |  44   |  47   |    -SEL        |eM |      GROUND    |  23   |  45   | 45 | 46 |  46   |  48   |    -C/D        |fM |      GROUND    |  24   |  47   | 47 | 48 |  48   |  49   |    -REQ        |iM |      GROUND    |  25   |  49   | 49 | 50 |  50   |  50   |    -I/O        |dM |---------------------------------------------------------------------------|.M |NOTES                                                                      | M |  1 The minus sign next to a signal indicates active low.                  | M |  2 The conductor number refers to the conductor position when using       |dM |    0,050 inch centreline flat ribbon cable with a low-density connector or| M |    when using 0,025 inch centreline flat ribbon cable with a high-density |uM |    connector.  Other cable types may be used to implement equivalent      |nM |    contact assignments.                                                   |nM |  3 Two sets of contact assignments are shown.  Refer to table 1 to        | M |    determine which set of contacts applies to each connector.             |tM |  4 See 4.4.4 for a definition of the RESERVED lines.                      |0M +===========================================================================+       A              Table 3 - Single-ended contact assignments - B cable M +================-===============-=========-===============-================+-M |                |   Connector   |  Cable  |   Connector   |                |uM |      Signal    |    contact    |conductor|    contact    |    Signal      | M |       name     |     number    | number  |     number    |     name       |dM |----------------+---------------+---------+---------------+----------------| M |      GROUND    |       1       |  1 |  2 |      35       |    GROUND      | M |      GROUND    |       2       |  3 |  4 |      36       |    -DB(8)      |cM |      GROUND    |       3       |  5 |  6 |      37       |    -DB(9)      | M |      GROUND    |       4       |  7 |  8 |      38       |    -DB(10)     | M |      GROUND    |       5       |  9 | 10 |      39       |    -DB(11)     | M |      GROUND    |       6       | 11 | 12 |      40       |    -DB(12)     |iM |      GROUND    |       7       | 13 | 14 |      41       |    -DB(13)     |nM |      GROUND    |       8       | 15 | 16 |      42       |    -DB(14)     |nM |      GROUND    |       9       | 17 | 18 |      43       |    -DB(15)     |lM |      GROUND    |      10       | 19 | 20 |      44       |    -DB(P1)     | M |      GROUND    |      11       | 21 | 22 |      45       |    -ACKB       |uM |      GROUND    |      12       | 23 | 24 |      46       |    GROUND      |cM |      GROUND    |      13       | 25 | 26 |      47       |    -REQB       | M |      GROUND    |      14       | 27 | 28 |      48       |    -DB(16)     |wM |      GROUND    |      15       | 29 | 30 |      49       |    -DB(17)     |eM |      GROUND    |      16       | 31 | 32 |      50       |    -DB(18)     |wM |     TERMPWRB   |      17       | 33 | 34 |      51       |    TERMPWRB    | M |     TERMPWRB   |      18       | 35 | 36 |      52       |    TERMPWRB    | M |      GROUND    |      19       | 37 | 38 |      53       |    -DB(19)     |aM |      GROUND    |      20       | 39 | 40 |      54       |    -DB(20)     |nM |      GROUND    |      21       | 41 | 42 |      55       |    -DB(21)     |dM |      GROUND    |      22       | 43 | 44 |      56       |    -DB(22)     |rM |      GROUND    |      23       | 45 | 46 |      57       |    -DB(23)     |eM |      GROUND    |      24       | 47 | 48 |      58       |    -DB(P2)     |oM |      GROUND    |      25       | 49 | 50 |      59       |    -DB(24)     |,M |      GROUND    |      26       | 51 | 52 |      60       |    -DB(25)     |eM |      GROUND    |      27       | 53 | 54 |      61       |    -DB(26)     |eM |      GROUND    |      28       | 55 | 56 |      62       |    -DB(27)     |cM |      GROUND    |      29       | 57 | 58 |      63       |    -DB(28)     |fM |      GROUND    |      30       | 59 | 60 |      64       |    -DB(29)     |rM |      GROUND    |      31       | 61 | 62 |      65       |    -DB(30)     | M |      GROUND    |      32       | 63 | 64 |      66       |    -DB(31)     |nM |      GROUND    |      33       | 65 | 66 |      67       |    -DB(P3)     |oM |      GROUND    |      34       | 67 | 68 |      68       |    GROUND      |rM |---------------------------------------------------------------------------|sM |NOTES                                                                      |oM |  1 The minus sign next to a signal indicates active low.                  |BM |  2 The conductor number refers to the conductor position when using       | M |    0,025 inch centreline flat ribbon cable.  Other cable types may be used|tM |    to implement contact assignments.                                      |fM +===========================================================================+     L    NOTE 10 An alternate 16-bit single-cable solution and an alternate 32-bitL    solution is being defined and the B cable definition will be removed in a    future version of SCSI.  A              Table 4 - Differential contact assignments - A cable M +================-===============-=========-===============-================+ M |                |  Connector    |         |  Connector    |                | M |                |contact number |  Cable  |contact number |                | M |      Signal    |---------------|conductor|---------------|    Signal      | M |       name     | Set 2 | Set 1 | number  | Set 1 | Set 2 |     name       | M |----------------+-------+-------+---------+-------+-------+----------------| M |      GROUND    |   1   |   1   |  1 |  2 |   2   |  26   |    GROUND      |0M |      +DB(0)    |   2   |   3   |  3 |  4 |   4   |  27   |    -DB(0)      | M |      +DB(1)    |   3   |   5   |  5 |  6 |   6   |  28   |    -DB(1)      | M |      +DB(2)    |   4   |   7   |  7 |  8 |   8   |  29   |    -DB(2)      | M |      +DB(3)    |   5   |   9   |  9 | 10 |  10   |  30   |    -DB(3)      | M |      +DB(4)    |   6   |  11   | 11 | 12 |  12   |  31   |    -DB(4)      | M |      +DB(5)    |   7   |  13   | 13 | 14 |  14   |  32   |    -DB(5)      |eM |      +DB(6)    |   8   |  15   | 15 | 16 |  16   |  33   |    -DB(6)      |=M |      +DB(7)    |   9   |  17   | 17 | 18 |  18   |  34   |    -DB(7)      | M |      +DB(P)    |  10   |  19   | 19 | 20 |  20   |  35   |    -DB(P)      | M |      DIFFSENS  |  11   |  21   | 21 | 22 |  22   |  36   |    GROUND      |eM |      RESERVED  |  12   |  23   | 23 | 24 |  24   |  37   |    RESERVED    |-M |      TERMPWR   |  13   |  25   | 25 | 26 |  26   |  38   |    TERMPWR     |1M |      RESERVED  |  14   |  27   | 27 | 28 |  28   |  39   |    RESERVED    |&M |      +ATN      |  15   |  29   | 29 | 30 |  30   |  40   |    -ATN        |2M |      GROUND    |  16   |  31   | 31 | 32 |  32   |  41   |    GROUND      | M |      +BSY      |  17   |  33   | 33 | 34 |  34   |  42   |    -BSY        | M |      +ACK      |  18   |  35   | 35 | 36 |  36   |  43   |    -ACK        | M |      +RST      |  19   |  37   | 37 | 38 |  38   |  44   |    -RST        | M |      +ACK      |  18   |  35   | 35 | 36 |  36   |  43   |    -ACK        | M |      +RST      |  19   |  37   | 37 | 38 |  38   |  44   |    -RST        | M |      +MSG      |  20   |  39   | 39 | 40 |  40   |  45   |    -MSG        ||M |      +SEL      |  21   |  41   | 41 | 42 |  42   |  46   |    -SEL        | M |      +C/D      |  22   |  43   | 43 | 44 |  44   |  47   |    -C/D        | M |      +REQ      |  23   |  45   | 45 | 46 |  46   |  48   |    -REQ        | M |      +I/O      |  24   |  47   | 47 | 48 |  48   |  49   |    -I/O        ||M |      GROUND    |  25   |  49   | 49 | 50 |  50   |  50   |    GROUND      | M |---------------------------------------------------------------------------| M |NOTES                                                                      |=M |  1 The conductor number refers to the conductor position when using       | M |    0,050 inch centreline flat ribbon cable with a low-density connector or| M |    when using 0,025 inch centreline flat ribbon cable with a high-density |gM |    connector.  Other cable types may be used to implement equivalent      |aM |    contact assignments.                                                   |-M |  2 Two sets of contact assignments are shown.  Refer to table 1 to        |OM |    determine which set of contacts applies to each connector.             |OM |  3 See 5.4.4 for a definition of the RESERVED lines.                      |OM +===========================================================================+O    A              Table 5 - Differential contact assignments - B cable M +================-===============-=========-===============-================+ M |                |   Connector   |  Cable  |   Connector   |                | M |      Signal    |    contact    |conductor|    contact    |    Signal      | M |       name     |     number    | number  |     number    |     name       | M |----------------+---------------+---------+---------------+----------------| M |      GROUND    |       1       |  1 |  2 |      35       |    GROUND      | M |      +DB(8)    |       2       |  3 |  4 |      36       |    -DB(8)      | M |      +DB(9)    |       3       |  5 |  6 |      37       |    -DB(9)      | M |      +DB(10)   |       4       |  7 |  8 |      38       |    -DB(10)     | M |      +DB(11)   |       5       |  9 | 10 |      39       |    -DB(11)     | M |      +DB(12)   |       6       | 11 | 12 |      40       |    -DB(12)     | M |      +DB(13)   |       7       | 13 | 14 |      41       |    -DB(13)     | M |      +DB(14)   |       8       | 15 | 16 |      42       |    -DB(14)     | M |      +DB(15)   |       9       | 17 | 18 |      43       |    -DB(15)     | M |      +DB(P1)   |      10       | 19 | 20 |      44       |    -DB(P1)     | M |      +ACKB     |      11       | 21 | 22 |      45       |    -ACKB       | M |      GROUND    |      12       | 23 | 24 |      46       |    DIFFSENS    | M |      +REQB     |      13       | 25 | 26 |      47       |    -REQB       | M |      +DB(16)   |      14       | 27 | 28 |      48       |    -DB(16)     | M |      +DB(17)   |      15       | 29 | 30 |      49       |    -DB(17)     | M |      +DB(18)   |      16       | 31 | 32 |      50       |    -DB(18)     |-M |      TERMPWRB  |      17       | 33 | 34 |      51       |    TERMPWRB    |NM |      TERMPWRB  |      18       | 35 | 36 |      52       |    TERMPWRB    | M |      +DB(19)   |      19       | 37 | 38 |      53       |    -DB(19)     | M |      +DB(20)   |      20       | 39 | 40 |      54       |    -DB(20)     | M |      +DB(21)   |      21       | 41 | 42 |      55       |    -DB(21)     | M |      +DB(22)   |      22       | 43 | 44 |      56       |    -DB(22)     | M |      +DB(23)   |      23       | 45 | 46 |      57       |    -DB(23)     | M |      +DB(P2)   |      24       | 47 | 48 |      58       |    -DB(P2)     | M |      +DB(24)   |      25       | 49 | 50 |      59       |    -DB(24)     | M |      +DB(25)   |      26       | 51 | 52 |      60       |    -DB(25)     | M |      +DB(26)   |      27       | 53 | 54 |      61       |    -DB(26)     |=M |      +DB(27)   |      28       | 55 | 56 |      62       |    -DB(27)     | M |      +DB(28)   |      29       | 57 | 58 |      63       |    -DB(28)     |=M |      +DB(29)   |      30       | 59 | 60 |      64       |    -DB(29)     | M |      +DB(30)   |      31       | 61 | 62 |      65       |    -DB(30)     |SM |      +DB(31)   |      32       | 63 | 64 |      66       |    -DB(31)     | M |      +DB(P3)   |      33       | 65 | 66 |      67       |    -DB(P3)     |-M |      GROUND    |      34       | 67 | 68 |      68       |    GROUND      |GM |---------------------------------------------------------------------------|GM |NOTE                                                                       |GM |  The conductor number refers to the conductor position when using         |GM |  0,025 inch centreline flat ribbon cable.  Other cable types may be used  |GM |  to implement equivalent contact assignments.                             |GM +===========================================================================+G    L    NOTE 11 An alternate 16-bit single-cable solution and an alternate 32-bitL    solution is being defined and the B cable definition will be removed in a    future version of SCSI.     5.4 Electrical description  G For the measurements in this subclause, SCSI bus termination is assumed A to be external to the SCSI device.  See 5.4.4 for the terminating5I requirements for the RESERVED lines.  SCSI devices may have the provision + for allowing optional internal termination.    5.4.1 Single-ended alternative  @ All signals not defined as RESERVED, GROUND, or TERMPWR shall beH terminated at both ends of the cable.  The implementor may choose one ofG the following two methods to terminate each end (see figures 9 and 10):   M    a)     The termination of each signal shall consist of 220 ohms (+/-5%) to7K           the TERMPWR line and 330 ohms (+/-5%) to ground.  Using resistors 6           with +/-1% tolerance improves noise margins.G    b)     The termination of each signal shall meet these requirements: I        1)    The terminators shall each supply a characteristic impedance0,              between 100 ohms and 132 ohms. I        2)    The terminators shall be powered by the TERMPWR line and may N              receive additional power from other sources but shall not requireD              such additional power for proper operation (see 5.4.3).M        3)    The current available to any signal line driver shall not exceed O              48 mA when the driver asserts the line and pulls it to 0,5 V d.c.  I              Only 44,8 mA of this current shall be available from the two               terminators. M        4)    The voltage on all released signal lines shall be at least 2,5 V G              d.c. when the TERMPWR line is within specified values (see8              5.4.3). DJ        5)    These conditions shall be met with any legal configuration ofE              targets and initiators as long as at least one device is               supplying TERMPWR.G  H The first termination method above is the same as in SCSI-1.  The second< termination method is recommended for better signal quality.   5.4.1.1 Output characteristics  I All signals shall use open-collector or three-state drivers.  Each signal-H driven by an SCSI device shall have the following output characteristics- when measured at the SCSI device's connector:   C VOL (low-level output voltage) = 0,0 to 0,5 V d.c. at 48 mA sinkingv (signal assertion)  F VOH (high-level output voltage) = 2,5 to 5,25 V d.c. (signal negation)   5.4.1.2 Input characteristicst  > SCSI devices with power on shall meet the following electricalD characteristics on each signal (including both receivers and passive	 drivers):=I VIL (low-level input voltage)    = 0,0 V d.c. to 0,8 V d.c. (signal true) K VIH (high-level input voltage)   = 2,0 V d.c. to 5,25 V d.c. (signal false) G IIL (low-level input current)    = -0,4 mA to 0,0 mA at VI = 0,5 V d.c.nE IIH (high-level input current)   = 0,0 mAto 0,1 mA at VI = 2,7 V d.c.o- Minimum input hysteresis         = 0,2 V d.c.-K Maximum input capacitance        = 25 pF (measured at the device connector  K                                    closest to the stub, if any, within the  *                                    device)  J It is recommended that SCSI devices with power off also meet the above IIL2 and IIH electrical characteristics on each signal.  E To achieve maximum noise immunity and to assure proper operation with-J complex cable configurations, it is recommended that the nominal switching! threshold be approximately 1,4 V.    5.4.2 Differential alternative  G All signals consist of two lines denoted +SIGNAL and -SIGNAL.  A signal I is true when +SIGNAL is more positive than -SIGNAL, and a signal is false H when -SIGNAL is more positive than +SIGNAL.  All assigned signals of theF A and B cables described in 5.6 shall be terminated at each end of the@ cable with a terminator network as shown in figure 11.  Resistor= tolerances in the terminator network shall be +/-5 % or less.1  I The DIFFSENS signal of the connector is used as an active high enable for|D the differential drivers.  If a single-ended device or terminator is? inadvertently connected, this signal is grounded, disabling theB% differential drivers (see figure 12).   E The characteristic impedance of differential terminators is 122 ohms.|   5.4.2.1 Output characteristics  D Each signal driven by an SCSI device shall have the following output= characteristics when measured at the SCSI device's connector: J VOL (low-level output voltage)    = 1,7 V maximum at IOL (low-level output5                                     current) = 55 mA.|D VOH (high-level output voltage)   = 2,7 V minimum at IOH (high-level=                                     output current) = -55 mA. B VOD (differential output voltage) = 1,0 V minimum with common-modeO                                     voltage ranges from -7 V d.c. to +12 V d.c.   I VOL and VOH shall be as measured between the output terminal and the SCSIT  device's logic ground reference.  I The output characteristics shall additionally conform to EIA RS-485-1983.    5.4.2.2 Input characteristics   H SCSI devices shall meet the following electrical characteristics on each6 signal (including both receivers and passive drivers):; II (input current on either input)    = +/- 2,0 mA maximum.+. Maximum input capacitance             = 25 pF.  I The II requirement shall be met with the input voltage varying between -7 D V d.c. and +12 V d.c., with power on or off, and with the hysteresis equaling 35 mv, minimum.  H The input characteristics shall additionally conform to EIA RS-485-1983.   5.4.3 Terminator power  G SCSI initiators shall supply terminator power to the TERMPWR contact(s) F and, if it implements the wide SCSI option, to the TERMPWRB contacts. J This power shall be supplied through a diode or similar semiconductor thatH prevents backflow of power to the SCSI device.  Targets and SCSI devicesG that become temporary initiators (e.g. targets which implement the COPYhF command or asynchronous event notification) are not required to supplyJ terminator power.  Any SCSI device may supply terminator power.  InterfaceE error rates are lower if the termination voltage is maintained at theo extreme ends of the cable.  I All terminators independent of location shall be powered from the TERMPWR G and TERMPWRB contact(s).  The use of keyed connectors is recommended in J SCSI devices that provide terminator power to prevent accidental grounding0 or the incorrect connection of terminator power.  K    NOTE 12 Regulatory agencies may require limiting maximum (short circuit)=N    current to the terminator power lines.  Recommended current limiting is 1,5F    A for TERMPWR and 2 A for TERMPWRB.  For systems utilizing multipleM    initiators, the initiators may be configured with option straps or current F    limiting devices.  Maximum available current should not exceed 5 A.  I SCSI devices shall sink no more than 1,0 mA from TERMPWR and no more than E 1,0 mA from TERMPWRB except to power an optional internal terminator.8  J Single-ended SCSI devices providing terminator power on cable A shall have the following characteristics:) VTerm        = 4,25 V d.c. to 5,25 V d.c. 5                900 mA minimum source drive capability   J Differential SCSI devices providing terminator power on cable A shall have the following characteristics:( VTerm        = 4,0 V d.c. to 5,25 V d.c.5                600 mA minimum source drive capability   J Single-ended SCSI devices providing terminator power on cable B shall have the following characteristics:( VTerm        = 4,5 V d.c. to 5,25 V d.c.6                1500 mA minimum source drive capability  J Differential SCSI devices providing terminator power on cable B shall have the following characteristics:( VTerm        = 4,0 V d.c. to 5,25 V d.c.6                1000 mA minimum source drive capability  L    NOTE 13 It is recommended that the terminator power lines be decoupled atM    each terminator with at least a 2,2 uF high-frequency capacitor to improve     signal quality.                          E         Figure 9 - Alternative 1 termination for single-ended devices                                                                                   F         Figure 10 - Alternative 2 termination for single-ended devices                                  ?                Figure 11 - Termination for differential devices|                        @               Figure 12 - Differential driver protection circuit     5.4.4 RESERVED lines  D The lines labelled RESERVED in the A cable contact assignment tablesH (table 2 and table 4) shall be connected to ground in the bus terminatorG assemblies or in the end devices on the SCSI cable.  The RESERVED lines|I should be open in the other SCSI devices, but may be connected to ground.    5.5 SCSI bus  I Communication on the SCSI bus is allowed between only two SCSI devices at|E any given time.  There is a maximum of eight SCSI devices.  Each SCSI5G device has an SCSI ID bit assigned as shown in figure 13.  Three sample ? system configurations are shown in figure 14.  There can be any G combination of initiators and targets provided there is at least one ofB each.|  A When two SCSI devices communicate on the SCSI bus, one acts as an+F initiator and the other acts as a target.  The initiator originates anH operation and the target performs the operation.  An SCSI device usuallyH has a fixed role as an initiator or target, but some devices may be able to assume either role.  J An initiator may address up to eight peripheral devices that are connectedG to a target.  The target may be physically housed within the peripheral-H device in which case the peripheral device is referred to as an embedded SCSI device.  I Certain SCSI bus functions are assigned to the initiator and certain SCSInJ bus functions are assigned to the target.  The initiator may arbitrate forH the SCSI bus and select a particular target.  The target may request theH transfer of COMMAND, DATA, STATUS, or other information on the DATA BUS,C and in some cases it may arbitrate for the SCSI bus and reselect an=5 initiator for the purpose of continuing an operation.l  C Information transfers on the DATA BUS are asynchronous and follow aaC defined REQ/ACK handshake protocol.  One byte of information may beSD transferred with each handshake on the A cable and, if the wide dataH transfer option is implemented, one or three bytes of information may beI transferred with each handshake on the B cable.  An option is defined for  synchronous data transfer.                                                  3                            Figure 13 - SCSI ID bits                                                                                             :                     Figure 14 - Sample SCSI configurations   5.6 SCSI bus signals  F There are a total of 18 signals on the A cable and 29 signals on the BF cable.  A total of 11 signals are used for control and 36 are used forD data (messages, commands, status and data), including parity.  These! signals are described as follows:   M a)        BSY (BUSY).  An OR-tied signal that indicates that the bus is beingt           used.e  K b)        SEL (SELECT).  An OR-tied signal used by an initiator to select ah9           target or by a target to reselect an initiator.T  L    NOTE 14 The SEL signal was not defined as OR-tied in SCSI-1.  It has beenJ    defined as OR-tied in SCSI-2 in anticipation of needing another OR-tiedI    signal for future standardization.  This does not cause an operationalr/    problem in mixing SCSI-1 and SCSI-2 devices.r  I c)        C/D (CONTROL/DATA).  A signal driven by a target that indicates G           whether CONTROL or DATA information is on the DATA BUS.  Trues           indicates CONTROL.  L d)        I/O (INPUT/OUTPUT).  A signal driven by a target that controls theG           direction of data movement on the DATA BUS with respect to an K           initiator. True indicates input to the initiator.  This signal is L           also used to distinguish between SELECTION and RESELECTION phases.  H e)        MSG (MESSAGE).  A signal driven by a target during the MESSAGE           phase.  G f)        REQ (REQUEST).  A signal driven by a target on the A cable to.G           indicate a request for an ACK information transfer handshake.-  H g)        REQB (REQUEST).  A signal driven by a target on the B cable toH           indicate a request for an ACKB information transfer handshake.  L h)        ACK (ACKNOWLEDGE).  A signal driven by an initiator on the A cableF           to indicate an acknowledgment for a REQ information transfer           handshake.  M i)        ACKB (ACKNOWLEDGE).  A signal driven by an initiator on the B cable G           to indicate an acknowledgment for a REQB information transferp           handshake.  K j)        ATN (ATTENTION).  A signal driven by an initiator to indicate theh           ATTENTION condition.  M k)        RST (RESET).  An OR-tied signal that indicates the RESET condition.A  J l)        DB(7-0,P) (DATA BUS).  Eight data-bit signals, plus a parity-bitM           signal that form a DATA BUS.  DB(7) is the most significant bit anduM           has the highest priority during the ARBITRATION phase.  Bit number, L           significance, and priority decrease downward to DB(0).  A data bitK           is defined as one when the signal value is true and is defined ashJ           zero when the signal value is false.  Data parity DB(P) shall beA           odd.  Parity is undefined during the ARBITRATION phase.r  H m)     DB(31-8,P1,P2,P3) (DATA BUS).  Twenty-four data-bit signals, plusI        three parity-bit signals that form an extension to the DATA BUS.  aJ        DB(P1,P2,P3) are parity bits for DB(15-8), DB(23-16), and DB(31-24)K        respectively.  A data bit is defined as one when the signal value isiH        true and is defined as zero when the signal value is false.  Data"        parity DB(Px) shall be odd.   5.6.1 Signal valuese  J Signals may assume true or false values.  There are two methods of drivingH these signals.  In both cases, the signal shall be actively driven true,G or asserted.  In the case of OR-tied drivers, the driver does not driveoC the signal to the false state, rather the bias circuitry of the bus I terminators pulls the signal false whenever it is released by the driversrK at every SCSI device.  If any driver is asserted, then the signal is true. iE In the case of non-OR-tied drivers, the signal may be actively drivensJ false.  In this International Standard, wherever the term negated is used,G it means that the signal may be actively driven false, or may be simply I released (in which case the bias circuitry pulls it false), at the option D of the implementor.  The advantage to actively driving signals falseE during information transfer is that the transition from true to falseuJ occurs more quickly and the noise margin is much higher than if the signalD is simply released.  This facilitates reliable data transfer at highD rates, especially at the longer cable lengths used with differential drivers.   5.6.2 OR-tied signalsT  E The BSY, SEL, and RST signals shall be OR-tied only.  In the ordinarydJ operation of the bus, the BSY and RST signals may be simultaneously drivenG true by several drivers.  No signals other than BSY, RST, and DB(P) are G simultaneously driven by two or more drivers, and any signal other than I BSY, SEL, and RST may employ OR-tied or non-OR-tied drivers.  DB(P) shall H not be driven false during the ARBITRATION phase but may be driven falseG in other phases.  There is no operational problem in mixing OR-tied and 6 non-OR-tied drivers on signals other than BSY and RST.   5.6.3 Signal sources  E Table 6 indicates which type of SCSI device is allowed to source eachiF signal.  No attempt is made to show if the source is driving asserted,E driving negated, or is passive.  All SCSI device drivers that are notpG active sources be in the passive state.  The RST signal may be assertedv by any SCSI device at any time.I  3                            Table 6 - Signal sourcesrO +==============-=====================================-========================+nO |  Bus phase   |         A cable signals             |     B cable signals    |yO |              |-------------------------------------+------------------------|lO |              |      |      | C/D, |      |         |      |      | DB(31-8) |dO |              |      |      | I/O, |      |         |      |      |  DB(P1)  | O |              |      |      | MSG, | ACK, | DB(7-0) |      |      |  DB(P2)  |pO |              | BSY  | SEL  | REQ  | ATN  |  DB(P)  | REQB | ACKB |  DB(P3)  |oO |--------------+------+------+------+------+---------+------+------+----------|tO |  BUS FREE    | None | None | None | None |   None  | None | None |    None  |5O |  ARBITRATION | All  | Win  | None | None |   S ID  | None | None |    None  |iO |  SELECTION   | I&T  | Init | None | Init |   Init  | None | None |    None  |nO |  RESELECTION | I&T  | Targ | Targ | Init |   Targ  | None | None |    None  |lO |  COMMAND     | Targ | None | Targ | Init |   Init  | None | None |    None  |cO |  DATA IN     | Targ | None | Targ | Init |   Targ  | Targ | Init |    Targ  |dO |  DATA OUT    | Targ | None | Targ | Init |   Init  | Targ | Init |    Init  | O |  STATUS      | Targ | None | Targ | Init |   Targ  | None | None |    None  |cO |  MESSAGE IN  | Targ | None | Targ | Init |   Targ  | None | None |    None  |lO |  MESSAGE OUT | Targ | None | Targ | Init |   Init  | None | None |    None  | O |-----------------------------------------------------------------------------|eO |                                                                             |:O |All:    The signal shall be driven by all SCSI devices that are actively     | O |        arbitrating.                                                         | O |                                                                             | O |S ID:   A unique data bit (the SCSI ID) shall be driven by each SCSI device  |rO |        that is actively arbitrating; the other seven data bits shall be     |tO |        released (i.e., not driven) by this SCSI device.  The parity bit     | O |        (DB(P)) may be released or driven to the true state, but shall never |eO |        be driven to the false state during this phase.                      | O |                                                                             |sO |I&T:    The signal shall be driven by the initiator, target, or both, as     |fO |        specified in the SELECTION phase and RESELECTION phase.              |lO |                                                                             |EO |Init:   If driven, this signal shall be driven only by the active initiator. |tO |                                                                             |cO |None:   The signal shall be released; that is, not be driven by any SCSI     |cO |        device.  The bias circuitry of the bus terminators pulls the signal  |bO |        to the false state.                                                  |SO |                                                                             | O |Win:    The signal shall be driven by the one SCSI device that wins          | O |        arbitration.                                                         | O |                                                                             |nO |Targ:   If the signal is driven, it shall be driven only by the active       |gO |        target.                                                              |tO +=============================================================================+r     5.7 SCSI bus timingp  E Unless otherwise indicated, the delay-time measurements for each SCSIsD device, shown in table 7, shall be calculated from signal conditionsD existing at that SCSI device's own SCSI bus connection.  Thus, theseF measurements (except cable skew delay) can be made without consideringC delays in the cable.  The timing characteristics of each signal areh& described in the following paragraphs.  7                        Table 7 - SCSI bus timing valuesSD +==============================-===================================+D |  Timing description          |      Timing value                 |D |------------------------------+-----------------------------------|D |  Arbitration delay           |     2,4 us                        |D |  Assertion period            |      90 ns                        |D |  Bus clear delay             |     800 ns                        |D |  Bus free delay              |     800 ns                        |D |  Bus set delay               |     1,8 us                        |D |  Bus settle delay            |     400 ns                        |D |  Cable skew delay            |      10 ns                        |D |  Data release delay          |     400 ns                        |D |  Deskew delay                |      45 ns                        |D |  Disconnection delay         |     200 us                        |D |  Hold time                   |      45 ns                        |D |  Negation period             |      90 ns                        |D |  Power-on to selection time  |      10 s recommended             |D |  Reset to selection time     |     250 ms recommended            |D |  Reset hold time             |      25 us                        |D |  Selection abort time        |     200 us                        |D |  Selection time-out delay    |     250 ms recommended            |D |  Transfer period             |     set during an SDTR message    |D |  Fast assertion period       |      30 ns                        |D |  Fast cable skew delay       |       5 ns                        |D |  Fast deskew delay           |      20 ns                        |D |  Fast hold time              |      10 ns                        |D |  Fast negation period        |      30 ns                        |D +==================================================================+   5.7.1 Arbitration delay   A The minimum time an SCSI device shall wait from asserting BSY for H arbitration until the DATA BUS can be examined to see if arbitration has$ been won.  There is no maximum time.   5.7.2 Assertion period S  E The minimum time that a target shall assert REQ (or REQB) while using E synchronous data transfers.  Also, the minimum time that an initiatortH shall assert ACK (or ACKB) while using synchronous data transfers.  REQB= and ACKB timings only apply to optional wide data transfers.     5.7.3 Bus clear delay   J The maximum time for an SCSI device to stop driving all bus signals after:4    a)     The BUS FREE phase is detected (see 6.1.1)I    b)     SEL is received from another SCSI device during the ARBITRATIONr           phase (    c)     The transition of RST to true.  E For the first condition above, the maximum time for an SCSI device to F clear the bus is 1200 nanoseconds from BSY and SEL first becoming bothI false.  If an SCSI device requires more than a bus settle delay to detect I BUS FREE phase, it shall clear the bus within a bus clear delay minus thes excess time.   5.7.4 Bus free delay n  I The minimum time that an SCSI device shall wait from its detection of thebG BUS FREE phase (see 6.1.1) until its assertion of BSY when going to the  ARBITRATION phase.   5.7.5 Bus set delay   H The maximum time for an SCSI device to assert BSY and its SCSI ID bit onH the DATA BUS after it detects BUS FREE phase (see 6.1.1) for the purpose" of entering the ARBITRATION phase.   5.7.6 Bus settle delay e  E The minimum time to wait for the bus to settle after changing certain : control signals as called out in the protocol definitions.   5.7.7 Cable skew delay A  G The maximum difference in propagation time allowed between any two SCSIl2 bus signals measured between any two SCSI devices.   5.7.8 Data release delay    A The maximum time for an initiator to release the DATA BUS signalsb> following the transition of the I/O signal from false to true.   5.7.9 Deskew delay    8 The minimum time required for deskew of certain signals.   5.7.10 Disconnection delay e  D The minimum time that a target shall wait after releasing BSY beforeI participating in an ARBITRATION phase when honouring a DISCONNECT messaget from the initiator.n   5.7.11 Hold time d  H The minimum time added between the assertion of REQ (or REQB) or ACK (orD ACKB) and the changing of the data lines to provide hold time in theJ initiator or target while using synchronous data transfers.  REQB and ACKB4 timings only apply to optional wide data transfers.    5.7.12 Negation period n  E The minimum time that a target shall negate REQ (or REQB) while usingvE synchronous data transfers.  Also, the minimum time that an initiatordH shall negate ACK (or ACKB) while using synchronous data transfers.  REQB= and ACKB timings only apply to optional wide data transfers. n  " 5.7.13 Power-on to selection time   H The recommended maximum time from power application until an SCSI targetJ is able to respond with appropriate status and sense data to the TEST UNIT+ READY, INQUIRY, and REQUEST SENSE commands.d   5.7.14 Reset to selection time a  G The recommended maximum time after a hard RESET condition until an SCSIRG target is able to respond with appropriate status and sense data to then5 TEST UNIT READY, INQUIRY, and REQUEST SENSE commands.i   5.7.15 Reset hold time    F The minimum time for which RST is asserted.  There is no maximum time.   5.7.16 Selection abort time   F The maximum time that a target (or initiator) shall take from its mostH recent detection of being selected (or reselected) until asserting a BSY@ response.  This time-out is required to ensure that a target (orG initiator) does not assert BSY after a SELECTION (or RESELECTION) phaserI has been aborted.  This is not the selection time-out period; see 6.1.3.1 ' and 6.1.4.2 for a complete description.l    5.7.17 Selection time-out delay   J The minimum time that an SCSI device should wait for a BSY response duringK the SELECTION or RESELECTION phase before starting the time-out procedure. p    J    Note 15 The selection time-out delay is only a recommended time period.   5.7.18 Transfer period    D The minimum time allowed between the leading edges of successive REQK pulses or of successive ACK pulses while using synchronous data transfers. a (See 6.1.5.2 and 6.6.21.)e  $ 5.8 Fast synchronous transfer option  J When devices negotiate a synchronous data transfer period of less than 200F ns they are said to be using fast synchronous data transfers.  DevicesG that negotiate a synchronous data transfer period greater than or equal J to 200 ns use timing parameters specified in 5.7.  When a fast synchronousJ data transfer period is negotiated, those specific times redefined in thisC section are used; those not redefined remain the same.  The minimum-+ synchronous data transfer period is 100 ns.    5.8.1 Fast assertion period   J The minimum time that a target shall assert REQ (or REQB) while using fastJ synchronous data transfers.  It is also the minimum time that an initiatorH shall assert ACK (or ACKB) while using fast synchronous data transfers. B REQB and ACKB timings only apply to optional wide data transfers.    5.8.2 Fast cable skew delay   G The maximum difference in propagation time allowed between any two SCSIrB bus signals measured between any two SCSI devices while using fast synchronous data transfers.t   5.8.3 Fast deskew delay   H The minimum time required for deskew of certain signals while using fast synchronous data transfers.    5.8.4 Fast hold time    H The minimum time added between the assertion of REQ (or REQB) or ACK (orD ACKB) and the changing of the data lines to provide hold time in theJ initiator or target while using fast synchronous data transfers.  REQB and9 ACKB timings only apply to optional wide data transfers. g   5.8.5 Fast negation period    J The minimum time that a target shall negate REQ (or REQB) while using fastE synchronous data transfers.  Also, the minimum time that an initiator H shall negate ACK (or ACKB) while using fast synchronous data transfers. A REQB and ACKB timings only apply to optional wide data transfers.a     6 Logical characteristicso   6.1 SCSI bus phasesa  5 The SCSI architecture includes eight distinct phases:s          a)    BUS FREE phase         b)    ARBITRATION phase        c)    SELECTION phase        d)    RESELECTION phase$        e)    COMMAND phase         +N        f)    DATA phase            |      These phases are collectively termedJ        g)    STATUS phase          |      the information transfer phases.$        h)    MESSAGE phase         +  G The SCSI bus can never be in more than one phase at any given time.  In G the following descriptions, signals that are not mentioned shall not be 	 asserted.    6.1.1 BUS FREE phase  J The BUS FREE phase indicates that there is no current I/O process and that+ the SCSI bus is available for a connection.   J SCSI devices shall detect the BUS FREE phase after the SEL and BSY signals/ are both false for at least a bus settle delay.h  H SCSI devices shall release all SCSI bus signals within a bus clear delayH after the BSY and SEL signals become continuously false for a bus settleI delay.  If an SCSI device requires more than a bus settle delay to detect J the BUS FREE phase then it shall release all SCSI bus signals within a busJ clear delay minus the excess time to detect the BUS FREE phase.  The totalI time to clear the SCSI bus shall not exceed a bus settle delay plus a bus  clear delay.  C During normal operation the BUS FREE phase is entered when a targettD releases the BSY signal.  However, the BUS FREE phase may be enteredH following the release of the SEL signal after a SELECTION or RESELECTION phase time-out.=  H Initiators normally do not expect BUS FREE phase to begin because of theD target's release of the BSY signal except after one of the following occurrences:.    a)     after a reset condition is detected;F    b)     after an ABORT message is successfully received by a target;H    c)     after a BUS DEVICE RESET message is successfully received by a           target;iN    d)     after a DISCONNECT message is successfully transmitted from a target           (see 6.6.6);K    e)     after a COMMAND COMPLETE message is successfully transmitted from=           a target (see 6.6.5); H    f)     after a RELEASE RECOVERY message is successfully received by a           target;-J    g)     after an ABORT TAG message is successfully received by a target;K    h)     after a CLEAR QUEUE message is successfully received by a target.   J If an initiator detects the release of the BSY signal by the target at anyJ other time, the target is indicating an error condition to the initiator. H The target may perform this transition to the BUS FREE phase independentJ of the state of the ATN signal.  The initiator shall manage this conditionJ as an unsuccessful I/O process termination.  The target terminates the I/OC process by clearing all pending data and status information for the I affected nexus.  The target may optionally prepare sense data that may be % retrieved by a REQUEST SENSE command.    6.1.2 ARBITRATION phase   H The ARBITRATION phase allows one SCSI device to gain control of the SCSI5 bus so that it can initiate or resume an I/O process.s  H The procedure for an SCSI device to obtain control of the SCSI bus is as follows:L    a)     The SCSI device shall first wait for the BUS FREE phase to occur. N           The BUS FREE phase is detected whenever both the BSY and SEL signalsJ           are simultaneously and continuously false for a minimum of a bus           settle delay.   I    NOTE 16 This bus settle delay is necessary because a transmission lineeL    phenomenon known as a wired-OR glitch may cause the BSY signal to briefly5    appear false, even though it is being driven true.w  H    b)     The SCSI device shall wait a minimum of a bus free delay afterM           detection of the BUS FREE phase (i.e. after the BSY and SEL signals K           are both false for a bus settle delay) before driving any signal.=G    c)     Following the bus free delay in step (b), the SCSI device may M           arbitrate for the SCSI bus by asserting both the BSY signal and itsAH           own SCSI ID, however the SCSI device shall not arbitrate (i.e.M           assert the BSY signal and its SCSI ID) if more than a bus set delayl@           has passed since the BUS FREE phase was last observed.  L    NOTE 17 There is no maximum delay before asserting the BSY signal and theN    SCSI ID following the bus free delay in step (b) as long as the bus remainsM    in the BUS FREE phase.  However, SCSI devices that delay longer than a busvO    settle delay plus a bus set delay from the time when the BSY and SEL signalstL    first become false may fail to participate in arbitration when competing     with faster SCSI devices.  H    d)     After waiting at least an arbitration delay (measured from itsM           assertion of the BSY signal) the SCSI device shall examine the DATAmH           BUS.  If a higher priority SCSI ID bit is true on the DATA BUSC           (DB(7) is the highest), then the SCSI device has lost theeL           arbitration and the SCSI device may release its signals and returnM           to step (a).  If no higher priority SCSI ID bit is true on the DATAbH           BUS, then the SCSI device has won the arbitration and it shallK           assert the SEL signal.  Any SCSI device other than the winner hasdL           lost the arbitration and shall release the BSY signal and its SCSIM           ID bit within a bus clear delay after the SEL signal becomes true. .G           An SCSI device that loses arbitration may return to step (a).a      NOTESN    18 Step d) above requires that any device complete the arbitration phase toO    the point of SEL being asserted if it begins the arbitration phase as statedaE    in step c).  This precludes the possibility of the bus being hung..K    19 It is recommended that new implementations wait for the SEL signal toTO    become true before releasing the BSY signal and SCSI ID bit when arbitration     is lost.d  I    e)     The SCSI device that wins arbitration shall wait at least a busDL           clear delay plus a bus settle delay after asserting the SEL signal&           before changing any signals.  N    NOTE 20 The SCSI ID bit is a single bit on the DATA BUS that corresponds toK    the SCSI device's unique SCSI address.  All other DATA BUS bits shall be K    released by the SCSI device.  Parity is not valid during the ARBITRATIONtO    phase.  During the ARBITRATION phase, DB(P) may be released or asserted, buti&    shall not be actively driven false.   6.1.3 SELECTION phaset  J The SELECTION phase allows an initiator to select a target for the purposeI of initiating some target function (e.g., READ or WRITE command).  DuringaG the SELECTION phase the I/O signal is negated so that this phase can be ) distinguished from the RESELECTION phase.a  I The SCSI device that won the arbitration has both the BSY and SEL signalsnE asserted and has delayed at least a bus clear delay plus a bus settleoH delay before ending the ARBITRATION phase.  The SCSI device that won theB arbitration becomes an initiator by not asserting the I/O signal.   J The initiator shall set the DATA BUS to a value that is the OR of its SCSIF ID bit and the target's SCSI ID bit and it shall assert the ATN signalH (indicating that a MESSAGE OUT phase is to follow the SELECTION phase). H The initiator shall then wait at least two deskew delays and release theF BSY signal.  The initiator shall then wait at least a bus settle delay. before looking for a response from the target.  J The target shall determine that it is selected when the SEL signal and itsG SCSI ID bit are true and the BSY and I/O signals are false for at least)J a bus settle delay.  The selected target may examine the DATA BUS in orderI to determine the SCSI ID of the selecting initiator.  The selected target J shall then assert the BSY signal within a selection abort time of its mostJ recent detection of being selected; this is required for correct operation% of the selection time-out procedure. i  G The target shall not respond to a selection if bad parity is detected. sI Also, if more than two SCSI ID bits are on the DATA BUS, the target shall  not respond to selection.a  O    NOTE 21 Although an SCSI-2 initiator may not use the single initiator optionoM    or the selection without asserting ATN option of SCSI-1, an SCSI-2 target sP    may elect to support these options for compatibility with SCSI-1 initiators. G    When doing so the SCSI-2 target responds as described in the SCSI-1 v    standard.  I No less than two deskew delays after the initiator detects the BSY signalsJ is true, it shall release the SEL signal and may change the DATA BUS.  TheH target shall wait until the SEL signal is false before asserting the REQ. signal to enter an information transfer phase.  $ 6.1.3.1 SELECTION time-out procedure  I Two optional selection time-out procedures are specified for clearing theaG SCSI bus if the initiator waits a minimum of a selection time-out delaye: and there has been no BSY signal response from the target:L    a)     Optionally, the initiator shall assert the RST signal (see 6.2.2);L    b)     Optionally, the initiator shall continue asserting the SEL and ATNK           signals and shall release the DATA BUS.  If the initiator has notoM           detected the BSY signal to be true after at least a selection abortcN           time plus two deskew delays, the initiator shall release the SEL andN           ATN signals allowing the SCSI bus to go to the BUS FREE phase.  SCSII           devices shall ensure that when responding to selection that the J           selection was still valid within a selection abort time of theirC           assertion of the BSY signal.  Failure to comply with thisdH           requirement could result in an improper selection (two targetsG           connected to the same initiator, wrong target connected to ang<           initiator, or a target connected to no initiator).   6.1.4 RESELECTION phasen  H RESELECTION is an optional phase that allows a target to reconnect to anJ initiator for the purpose of continuing some operation that was previouslyJ started by the initiator but was suspended by the target, (i.e. the targetG disconnected by allowing a BUS FREE phase to occur before the operationB was complete).   6.1.4.1 RESELECTION     G Upon completing the ARBITRATION phase, the winning SCSI device has botheE the BSY and SEL signals asserted and has delayed at least a bus clear H delay plus a bus settle delay.  The winning SCSI device becomes a targetH by asserting the I/O signal.  The winning SCSI device shall also set theE DATA BUS to a value that is the logical OR of its SCSI ID bit and theeJ initiator's SCSI ID bit.  The target shall wait at least two deskew delaysF and release the BSY signal.  The target shall then wait at least a bus> settle delay before looking for a response from the initiator.  H The initiator shall determine that it is reselected when the SEL and I/OG signals and its SCSI ID bit are true and the BSY signal is false for atdH least a bus settle delay.  The reselected initiator may examine the DATAE BUS in order to determine the SCSI ID of the reselecting target.  The H reselected initiator shall then assert the BSY signal within a selectionD abort time of its most recent detection of being reselected; this isH required for correct operation of the time-out procedure.  The initiatorJ shall not respond to a RESELECTION phase if bad parity is detected.  Also,H the initiator shall not respond to a RESELECTION phase if other than two" SCSI ID bits are on the DATA BUS.   I After the target detects the BSY signal is true, it shall also assert the G BSY signal and wait at least two deskew delays and then release the SELeE signal.  The target may then change the I/O signal and the DATA BUS. aH After the reselected initiator detects the SEL signal is false, it shallD release the BSY signal.  The target shall continue asserting the BSY* signal until it relinquishes the SCSI bus.  K    NOTE 22 When the target is asserting the BSY signal, a transmission linesK    phenomenon known as a wired-OR glitch may cause the BSY signal to appeareN    false for up to a round-trip propagation delay following the release of theM    BSY signal by the initiator.  This is the reason why the BUS FREE phase isaM    recognized only after both the BSY and SEL signals are continuously false rO    for a minimum of a bus settle delay.  Cables longer than 25 m should not be fM    used even if the chosen driver, receiver, and cable provide adequate noiselL    margins, because they increase the duration of the glitch and could cause;    SCSI devices to inadvertently detect the BUS FREE phase.g  & 6.1.4.2 RESELECTION time-out procedure  G Two optional RESELECTION time-out procedures are specified for clearingtH the SCSI bus during a RESELECTION phase if the target waits a minimum ofI a selection time-out delay and there has been no BSY signal response fromr the initiator:  I    a)     Optionally, the target shall assert the RST signal (see 6.2.2);eI    b)     Optionally, the target shall continue asserting the SEL and I/ONL           signals and shall release all DATA BUS signals.  If the target hasK           not detected the BSY signal to be true after at least a selection M           abort time plus two deskew delays, the target shall release the SELCM           and I/O signals allowing the SCSI bus to go to the BUS FREE phase. FN           SCSI devices that respond to the RESELECTION phase shall ensure thatJ           the reselection was still valid within a selection abort time ofI           their assertion of the BSY signal.  Failure to comply with thiseM           requirement could result in an improper reselection (two initiatorsdL           connected to the same target or the wrong initiator connected to a           target).  ! 6.1.5 Information transfer phasesl  H    NOTE 23 The COMMAND, DATA, STATUS, and MESSAGE phases are all groupedK    together as the information transfer phases because they are all used toaM    transfer data or control information via the DATA BUS.  The actual contente:    of the information is beyond the scope of this section.  A The C/D, I/O, and MSG signals are used to distinguish between the G different information transfer phases (see table 8).  The target drives H these three signals and therefore controls all changes from one phase toH another.  The initiator can request a MESSAGE OUT phase by asserting theJ ATN signal, while the target can cause the BUS FREE phase by releasing the MSG, C/D, I/O, and BSY signals.   E The information transfer phases use one or more REQ/ACK handshakes torD control the information transfer.  Each REQ/ACK handshake allows theE transfer of one byte of information.  During the information transfermG phases the BSY signal shall remain true and the SEL signal shall remainaH false.  Additionally, during the information transfer phases, the targetG shall continuously envelope the REQ/ACK handshake(s) with the C/D, I/O,iI and MSG signals in such a manner that these control signals are valid fortF a bus settle delay before the assertion of the REQ signal of the firstH handshake and remain valid until after the negation of the ACK signal at; the end of the handshake of the last transfer of the phase.h      NOTESM    24 After the negation of the ACK signal of the last transfer of the phase,hL    the target may prepare for a new phase by asserting or negating the C/D, C    I/O, and MSG signals.  These signals may be changed together or rO    individually. They may be changed in any order and may be changed more than eM    once.  It is desirable that each line change only once.  A new phase does oL    not begin until the REQ signal is asserted for the first byte of the new 	    phase.lK    25 A phase is defined as ending when the C/D, I/O, or MSG signals change M    after the negation of the ACK signal.  The time between the end of a phaseyN    and the assertion of the REQ signal beginning a new phase is undefined.  AnN    initiator is allowed to anticipate a new phase based on the previous phase,L    the expected new phase, and early information provided by changes in the K    C/D, I/O, and MSG signals.  However, the anticipated phase is not valid lG    until the REQ signal is asserted at the beginning of the next phase.n  9                     Table 8 - Information transfer phasesAO +=============-===============-==================================-============+TO |    Signal   |  Phase name   |       Direction of transfer      |  Comment   | O |-------------|               |                                  |            |oO | MSG|C/D|I/O |               |                                  |            |tO |----+---+----+---------------+----------------------------------+------------|fO |  0 | 0 | 0  |  DATA OUT     |       Initiator to target     \  |  Data      |EO |  0 | 0 | 1  |  DATA IN      |       Initiator from target   /  |  phase     |rO |  0 | 1 | 0  |  COMMAND      |       Initiator to target        |            |hO |  0 | 1 | 1  |  STATUS       |       Initiator from target      |            |aO |  1 | 0 | 0  |  *            |                                  |            |nO |  1 | 0 | 1  |  *            |                                  |            |nO |  1 | 1 | 0  |  MESSAGE OUT  |       Initiator to target     \  |  Message   |tO |  1 | 1 | 1  |  MESSAGE IN   |       Initiator from target   /  |  phase     |SO |-----------------------------------------------------------------------------| O | Key:  0 = False,  1 = True,  * = Reserved for future standardization        | O +=============================================================================+     ) 6.1.5.1 Asynchronous information transferd  G The target shall control the direction of information transfer by meansaE of the I/O signal.  When the I/O signal is true, information shall beyE transferred from the target to the initiator.  When the I/O signal isnI false, information shall be transferred from the initiator to the target.   G If the I/O signal is true (transfer to the initiator), the target shallsI first drive the DB(7-0,P) signals to their desired values, delay at least J one deskew delay plus a cable skew delay, then assert the REQ signal.  TheH DB(7-0,P) signals shall remain valid until the ACK signal is true at theE target.  The initiator shall read the DB(7-0,P) signals after the REQ I signal is true, then indicate its acceptance of the data by asserting thetG ACK signal.  When the ACK signal becomes true at the target, the targetsD may change or release the DB(7-0,P) signals and shall negate the REQJ signal.  After the REQ signal is false the initiator shall then negate theF ACK signal.  After the ACK signal is false the target may continue theG transfer by driving the DB(7-0,P) signals and asserting the REQ signal,T as described above.   D If the I/O signal is false (transfer to the target) the target shallE request information by asserting the REQ signal.  The initiator shall G drive the DB(7-0,P) signals to their desired values, delay at least onehD deskew delay plus a cable skew delay and assert the ACK signal.  TheE initiator shall continue to drive the DB(7-0,P) signals until the REQaE signal is false.  When the ACK signal becomes true at the target, the;J target shall read the DB(7-0,P), signals then negate the REQ signal.  WhenG the REQ signal becomes false at the initiator, the initiator may changeaH or release the DB(7-0,P) signals and shall negate the ACK signal.  AfterI the ACK signal is false the target may continue the transfer by assertingl# the REQ signal, as described above.l  ! 6.1.5.2 Synchronous data transferB  G Synchronous data transfer is optional and is only used in data phases. oI It shall be used in a data phase if a synchronous data transfer agreementnG has been established (see 6.6.21).  The agreement specifies the REQ/ACKc' offset and the minimum transfer period.o  I The REQ/ACK offset specifies the maximum number of REQ pulses that can besG sent by the target in advance of the number of ACK pulses received fromaE the initiator, establishing a pacing mechanism.  If the number of REQTI pulses exceeds the number of ACK pulses by the REQ/ACK offset, the target H shall not assert the REQ signal until after the leading edge of the nextF ACK pulse is received.  For successful completion of the data phase is6 that the number of ACK and REQ pulses shall be equal.   D The target shall assert the REQ signal for a minimum of an assertionE period. The target shall then wait at least the greater of a transfer I period from the last transition of the REQ signal to true or a minimum ofsE a negation period from the last transition of the REQ signal to falset& before again asserting the REQ signal.  G The initiator shall send one pulse on the ACK signal for each REQ pulseIH received.  The ACK signal may be asserted as soon as the leading edge ofJ the corresponding REQ pulse has been received.  The initiator shall assertI the ACK signal for a minimum of an assertion period.  The initiator shall.G wait at least the greater of a transfer period from the last transitionIH of the ACK signal to true or for a minimum of a negation period from theC last transition of the ACK signal to false before asserting the ACKh signal.U  G If the I/O signal is true (transfer to the initiator), the target shalleH first drive the DB(7-0,P) signals to their desired values, wait at leastI one deskew delay plus one cable skew delay, then assert the REQ signals. rE The DB(7-0,P) signals shall be held valid for a minimum of one deskew I delay plus one cable skew delay plus one hold time after the assertion ofaH the REQ signal.  The target shall assert the REQ signal for a minimum ofJ an assertion period.  The target may then negate the REQ signal and changeH or release the DB(7-0,P) signals.  The initiator shall read the value onG the DB(7-0,P) signals within one hold time of the transition of the REQiD signal to true.  The initiator shall then respond with an ACK pulse.  H If the I/O signal is false (transfer to the target), the initiator shallC transfer one byte for each REQ pulse received.  After receiving the J leading edge of a REQ pulse, the initiator shall first drive the DB(7-0,P)I signals to their desired values, delay at least one deskew delay plus oneaG cable skew delay, then assert the ACK signal.  The initiator shall holdsH the DB(7-0,P) signals valid for at least one deskew delay plus one cableI skew delay plus one hold time after the assertion of the ACK signal.  TheoC initiator shall assert the ACK signal for a minimum of an assertionoG period.  The initiator may then negate the ACK signal and may change oreF release the DB(7-0,P) signals.  The target shall read the value of theJ DB(7-0,P) signals within one hold time of the transition of the ACK signal to true.  N    NOTE 26 The description in SCSI-1 allowed some implementors to presume thatN    the leading edge of the first REQ pulse beyond the REQ/ACK offset agreementM    would not occur until after the trailing edge of the last ACK pulse withindM    the agreement.  Devices implemented with this understanding may be subjectnO    to data destruction when in synchronous data transfer mode with devices that G    issue the leading edge of the next REQ pulse, at the boundary of thenJ    agreement, as soon as the leading edge of the last ACK pulse within theK    agreement is received.  Implementors using devices of the former type iniM    initiator designs may insure data integrity by restricting the synchronous K    offset agreement to values smaller than the maximum nominally offered byd    their device.   6.1.5.3 Wide data transfer  H Wide data transfer is optional and may be used in the DATA phase only ifC a non-zero wide data transfer agreement is in effect (see WIDE DATA J TRANSFER REQUEST message, 6.6.23).  The messages determine the use of wideD mode by both SCSI devices and establish a data path width to be used during the DATA phase.  F Wide data transfers of 16- or 32-bits may be established.  Targets andH initiators that support 32-bit wide transfers should also support 16-bitE wide transfers.  All SCSI devices shall support 8-bit data transfers.a  G During 16-bit wide data transfers, the first logical data byte for eachtE data phase shall be transferred across the DB(7-0,P) signals on the A F cable and the second logical data byte shall be transferred across theG DB(15-8,P1) signals on the B cable.  Subsequent pairs of data bytes arehF likewise transferred in parallel across the A and B cables (see figure 15).  N    NOTE 27 X3T9.2 is documenting an alternate 16-bit single-cable solution andL    an alternate 32-bit solution and expects to be able to remove the B cable*    definition in a future version of SCSI.  G During 32-bit wide data transfers, the first logical data byte for each E data phase shall be transferred across the DB(7-0,P) signals on the A.C cable and the second, third, and fourth logical data bytes shall benB transferred across the DB(15-8,P1), DB(23-16,P2), and DB(31-24,P3)F signals, respectively, on the B cable.  Subsequent groups of four dataI bytes are likewise transferred in parallel across the A and B cables (seea figure 15).s                                                8                      Figure 15 - Wide SCSI byte ordering    J If the last data byte transferred does not fall on the DB(15-8,P1) signalsH for a 16-bit wide transfer or the DB(31-24,P3) signals for a 32-bit wideC transfer, then the values of the remaining higher-numbered bits areeI undefined.  However, parity bits for these undefined bytes shall be validC' for whatever data is placed on the bus.n  G To ensure proper data integrity, certain sequence requirements shall benC met between the REQ/ACK handshakes on the A cable and the REQB/ACKBt handshakes on the B cable:M    a)     The REQB and ACKB signals shall only be asserted during data phasessK           while a nonzero wide data transfer agreement is in effect.  These/<           signals shall not be asserted during other phases.J    b)     The same information transfer mode (asynchronous or synchronous)M           shall be used for both the A cable and the B cable.  If synchronousoF           data transfer mode is in effect, the same REQ/ACK offset and8           transfer period shall be used for both cables.L    c)     The information transfer procedures defined in 6.1.5.1 and 6.1.5.2J           for the A cable (the REQ, ACK, and DB(7-0,P) signals) shall alsoE           apply to the B cable (the REQB, ACKB, and DB(31-8,P1,P2,P3)=H           signals).  The only means available for a target to manage theJ           timing relationship between the signals on the two cables is itsL           management of the REQ and REQB signals.  Similarly, the only meansN           for the initiator to manage the timing between the two cables is its1           management of the ACK and ACKB signals.-K    d)     The target shall ensure that the number of REQ/ACK handshakes and M           the number of REQB/ACKB handshakes in a data phase are equal before M           it changes to another phase.  The target shall not change the phase L           until the ACK and ACKB signals have both become false for the last=           REQ/ACK handshake and the last REQB/ACKB handshake.0  K    NOTE 28 If any violations of these rules are detected by the target, the|O    target may attempt to end the data phase and return CHECK CONDITION status. |L    If it is impossible to correctly terminate the data phase, the target mayL    abnormally terminate the I/O process by an unexpected disconnect.  If anyM    violations of these rules are detected by the initiator, the initiator may M    attempt to send an INITIATOR DETECTED ERROR message to the target.  If the M    initiator is unable to terminate the I/O process normally, it may generate=    the reset condition.o   6.1.6 COMMAND phased  G The COMMAND phase allows the target to request command information froma the initiator.  I The target shall assert the C/D signal and negate the I/O and MSG signalse. during the REQ/ACK handshake(s) of this phase.   6.1.7 Data phase  H The data phase is a term that encompasses both the DATA IN phase and the DATA OUT phase.s   6.1.7.1 DATA IN phasee  G The DATA IN phase allows the target to request that data be sent to thed initiator from the target.  I The target shall assert the I/O signal and negate the C/D and MSG signalsn. during the REQ/ACK handshake(s) of this phase.   6.1.7.2 DATA OUT phase  J The DATA OUT phase allows the target to request that data be sent from the initiator to the target.  H The target shall negate the C/D, I/O, and MSG signals during the REQ/ACK handshake(s) of this phase.a   4s STATUS phase   H The STATUS phase allows the target to request that status information be& sent from the target to the initiator.  I The target shall assert the C/D and I/O signals and negate the MSG signale+ during the REQ/ACK handshake of this phase.n   6.1.9 Message phasen  E The message phase is a term that references either a MESSAGE IN, or a G MESSAGE OUT phase.  Multiple messages may be sent during either phase. .F The first byte transferred in either of these phases shall be either aB single-byte message or the first byte of a multiple-byte message. H Multiple-byte messages shall be wholly contained within a single message phase.   6.1.9.1 MESSAGE IN phase  I The MESSAGE IN phase allows the target to request that message(s) be senta! to the initiator from the target.e  H The target shall assert the C/D, I/O, and MSG signals during the REQ/ACK handshake(s) of this phase.a   6.1.9.2 MESSAGE OUT phases  J The MESSAGE OUT phase allows the target to request that message(s) be sentC from the initiator to the target.  The target invokes this phase inlI response to the attention condition created by the initiator (see 6.2.1).o  I The target shall assert the C/D and MSG signals and negate the I/O signal J during the REQ/ACK handshake(s) of this phase.  The target shall handshakeB byte(s) in this phase until the ATN signal is negated, except when rejecting a message.  H If the target detects one or more parity error(s) on the message byte(s)I received, it may indicate its desire to retry the message(s) by assertingoI the REQ signal after detecting the ATN signal has gone false and prior tot@ changing to any other phase.  The initiator, upon detecting thisG condition, shall resend all of the previous message byte(s) in the sameuI order as previously sent during this phase.  When resending more than onenD message byte, the initiator shall assert the ATN signal at least twoE deskew delays prior to asserting the ACK signal on the first byte andlE shall maintain the ATN signal asserted until the last byte is sent asa described in 6.2.1.g  E If the target does not retry the MESSAGE OUT phase or it exhausts itso retry limit it mayH    a)     return CHECK CONDITION status and set the sense key to ABORTEDD           COMMAND and the additional sense code to MESSAGE ERROR or;E    b)     indicate an exception condition by performing an unexpected            disconnect.i  H The target may act on messages as received as long as no parity error isA detected and may ignore all remaining messages sent under one ATNaH condition after a parity error is detected.  When a sequence of messagesH is resent by an initiator because of a target detected parity error, theD target shall not act on any message which it acted on the first time received.     G If the target receives all of the message byte(s) successfully (i.e. notC parity errors), it shall indicate that it does not wish to retry bykE changing to any information transfer phase other than the MESSAGE OUTeH phase and transfer at least one byte.  The target may also indicate thatG it has successfully received the message byte(s) by changing to the BUSh5 FREE phase (e.g. ABORT or BUS DEVICE RESET messages).n  ) 6.1.10 Signal restrictions between phasess  A When the SCSI bus is between two information transfer phases, thea; following restrictions shall apply to the SCSI bus signals:iI    a)     The BSY, SEL, REQ, REQB, ACK and ACKB signals shall not change. M    b)     The C/D, I/O, MSG, and DATA BUS signals may change.  When switchingtK           the DATA BUS direction from out (initiator driving) to in (target K           driving), the target shall delay driving the DATA BUS by at leasttN           a data release delay plus a bus settle delay after asserting the I/OK           signal and the initiator shall release the DATA BUS no later thanhO           a data release delay after the transition of the I/O signal to true. kK           When switching the DATA BUS direction from in (target driving) totK           out (initiator driving), the target shall release the DATA BUS noeB           later than a deskew delay after negating the I/O signal.N    c)     The ATN and RST signals may change as defined under the descriptionsJ           for the attention condition (see 6.2.1) and reset condition (see           6.2.2).p     6.2 SCSI bus conditionsm  I The SCSI bus has two asynchronous conditions; the attention condition and G the reset condition.  These conditions cause the SCSI device to perform 1 certain actions and can alter the phase sequence.t  F Furthermore, SCSI devices may not all be powered-on at the same time. F This standard does not address power sequencing issues.  However, eachE SCSI device, as it is powered on, should perform appropriate internalnG reset operations and internal test operations.  Following a power-on totJ selection time after power-on, SCSI targets should be able to respond withF appropriate status and sense data to the TEST UNIT READY, INQUIRY, and REQUEST SENSE commands.  e   6.2.1 Attention conditiont  G The attention condition allows an initiator to inform a target that thenB initiator has a message ready.  The target may get this message by performing a MESSAGE OUT phase.a  J The initiator creates the attention condition by asserting ATN at any time1 except during the ARBITRATION or BUS FREE phases.e  D The initiator shall negate the ATN signal at least two deskew delaysG before asserting the ACK signal while transferring the last byte of thehJ messages indicated with a Yes in table 10.  If the target detects that theJ initiator failed to meet this requirement, then the target shall go to BUS. FREE phase (see unexpected disconnect, 6.1.1).  D The initiator shall assert the ATN signal at least two deskew delaysE before negating the ACK signal for the last byte transferred in a bustG phase for the attention condition to be honoured before transition to aeJ new bus phase.  Asserting the ATN signal later might not be honoured untilA a later bus phase and then may not result in the expected action.c  9 A target shall respond with MESSAGE OUT phase as follows: K    a)     If the ATN signal becomes true during a COMMAND phase, the targetfM           shall enter MESSAGE OUT phase after transferring part or all of thef)           command descriptor block bytes.eN    b)     If the ATN signal becomes true during a DATA phase, the target shallN           enter MESSAGE OUT phase at the target's earliest convenience (often,J           but not necessarily on a logical block boundary).  The initiatorO           shall continue REQ/ACK handshakes until it detects the phase change. r
           J    c)     If the ATN signal becomes true during a STATUS phase, the targetF           shall enter MESSAGE OUT phase after the status byte has been*           acknowledged by the initiator.  N    d)     If the ATN signal becomes true during a MESSAGE IN phase, the targetN           shall enter MESSAGE OUT phase before it sends another message.  ThisI           permits a MESSAGE PARITY ERROR message from the initiator to beb2           associated with the appropriate message.L    e)     If the ATN signal becomes true during a SELECTION phase and beforeG           the initiator releases the BSY signal, the target shall enterhD           MESSAGE OUT phase immediately after that SELECTION phase. H    f)     If the ATN signal becomes true during a RESELECTION phase, theL           target shall enter MESSAGE OUT phase after the target has sent its8           IDENTIFY message for that RESELECTION phase.    O    NOTE 29 The initiator should only assert the ATN signal during a RESELECTIONaN    phase to transmit a BUS DEVICE RESET or DISCONNECT message.  Other uses may.    result in ambiguities concerning the nexus.  I The initiator shall keep the ATN signal asserted if more than one byte isuG to be transferred.  The initiator may negate the ATN signal at any timeCJ except it shall not negate the ATN signal while the ACK signal is assertedD during a MESSAGE OUT phase.  Normally, the initiator negates the ATNJ signal while the REQ signal is true and the ACK signal is false during the0 last REQ/ACK handshake of the MESSAGE OUT phase.   6.2.2 Reset conditionE  J The reset condition is used to immediately clear all SCSI devices from theD bus.  This condition shall take precedence over all other phases andH conditions.  Any SCSI device may create the reset condition by asserting2 the RST signal for a minimum of a reset hold time.  C All SCSI devices shall release all SCSI bus signals (except the RSTaG signal) within a bus clear delay of the transition of the RST signal to = true.  The BUS FREE phase always follows the reset condition.a  @ The effect of the reset condition on I/O processes that have notG completed, SCSI device reservations, and SCSI device operating modes is D determined by whether the SCSI device has implemented the hard reset@ alternative or the soft reset alternative (one of which shall beH implemented) as defined in 6.2.2.1 and 6.2.2.2.  The hard and soft resetD alternatives are mutually exclusive within a system.  A facility forG targets to report which reset alternative is implemented is provided inO. the SftRe bit of the INQUIRY data (see 8.2.5).  N    NOTE 30 Environmental conditions (e.g. static discharge) may generate briefM    glitches on the RST signal.  It is recommended that SCSI devices not reacteM    to these glitches.  The manner of rejecting glitches is vendor-specific.  lM    The bus clear delay following a RST signal transition to true is measured hN    from the original transition of the RST signal, not from the time that the N    signal has been confirmed.  This limits the time to confirm the RST signal %    to a maximum of a bus clear delay.t   6.2.2.1 Hard reset alternative  I SCSI devices that implement the hard reset alternative, upon detection ofl the reset condition, shall:iA    a)     clear all I/O processes including queued I/O processes.A/    b)     release all SCSI device reservations.gM    c)     return any SCSI device operating modes to their appropriate initialtK           conditions, similar to those conditions that would be found afteroL           a normal power-on reset.  MODE SELECT conditions shall be restoredL           to their last saved values if saved values have been established. M           MODE SELECT conditions for which no values have been saved shall beg+           returned to their default values..:    d)     unit attention condition shall be set (see 7.9).  G It is recommended that following a reset to selection time after a hardeF reset condition ends, SCSI targets be able to respond with appropriateH status and sense data to the TEST UNIT READY, INQUIRY, and REQUEST SENSE	 commands.e   6.2.2.2 Soft reset alternative  I SCSI devices that implement the soft reset alternative, upon detection of  the reset condition, shall:aL    a)     Attempt to complete any I/O processes which have not completed and$           that were fully identified/    b)     Preserve all SCSI device reservationsAN    c)     Preserve any SCSI device operating modes (MODE SELECT, PREVENT/ALLOW(           MEDIUM REMOVAL commands, etc.)N    d)     Preserve all the information required to continue normal dispatching?           of I/O processes queued prior to the reset condition.i  I The soft reset alternative allows an initiator to reset the SCSI bus withaE minimum disruption to the operation of other initiators in a multiple F initiator system.  To ensure proper operation the following conditions
 shall be met.hD    a)     An initiator shall not consider an I/O process to be fullyJ           identified until the IDENTIFY message (and queue tag message, ifK           any) is sent to the target and the target responds by changing to M           any other information transfer phase and requests that at least one            byte be transferred.L    b)     A target shall consider an I/O process to be fully identified whenI           it successfully receives the IDENTIFY message and any queue tagn;           message and the initiator negates the ATN signal.yK    c)     If an initiator selects a logical unit for which there already iseM           an active I/O process with the same queue tag (if any) for the samefH           initiator, the target shall clear the original I/O process and&           perform the new I/O process.K    d)     If a target reselects an initiator to continue an I/O process fordK           which the initiator has no record, the initiator shall abort thatdM           I/O process by sending the ABORT or ABORT TAG message, depending ontF           whether the reselecting I/O process is a tagged I/O process.L    e)     An initiator shall consider an I/O process to be completed when itK           negates ACK for a successfully received COMMAND COMPLETE message.aH    f)     A target shall consider an I/O process to be completed when itI           detects the transition of ACK to false for the COMMAND COMPLETEv,           message with the ATN signal false.H    g)     An initiator shall not negate the ACK signal for the SAVE DATAN           POINTER message until it has actually saved the data pointer for the           I/O process.N    h)     A target shall consider the data pointer to be saved when it detectsM           the transition of the ACK signal to false for the SAVE DATA POINTERS,           message with the ATN signal false.H    i)     If the reset condition occurs between the time that the targetI           asserts the REQ signal for the SAVE DATA POINTER message and it M           detects the transition of the ACK signal to false, the target shall L           terminate the I/O process with CHECK CONDITION status.  The targetH           shall set the sense key to ABORTED COMMAND.  This is necessaryJ           because the target cannot determine whether the data pointer has           actually been saved.  M    NOTE 31 If the ATN signal is true in conditions f) or h), the target wouldtP    normally switch to MESSAGE OUT phase and attempt to transfer a message byte. L    If the reset condition occurs before the target successfully receives theO    message byte, it may assume that the initiator has not successfully receivedtN    the COMMAND COMPLETE message or the SAVE DATA POINTER message.  In the caseI    of COMMAND COMPLETE message, the target may reselect the initiator andaO    attempt to send the COMMAND COMPLETE message again.  In the case of the SAVE1P    DATA POINTER message, the target may reselect the initiator and terminate the,    I/O process as described in condition i).   6.3 SCSI bus phase sequences  G The order in which phases are used on the SCSI bus follows a prescribedi	 sequence.n  I The reset condition can abort any phase and is always followed by the BUSpG FREE phase.  Also any other phase can be followed by the BUS FREE phasec9 but many such instances are error conditions (see 6.1.1).n  G The additional allowable sequences shall be as shown in Figure 16.  TheoB normal progression is from the BUS FREE phase to ARBITRATION, fromJ ARBITRATION to SELECTION or RESELECTION, and from SELECTION or RESELECTIONI to one or more of the information transfer phases (COMMAND, DATA, STATUS,.J or MESSAGE).  The final information transfer phase is normally the MESSAGEH IN phase where a DISCONNECT, or COMMAND COMPLETE message is transferred, followed by the BUS FREE phase.S                                                                  4                          Figure 16 - Phase sequences     6.4 SCSI pointerss  G Consider the system shown in figure 17 in which an initiator and target ? communicate on the SCSI bus in order to execute an I/O process.o  G The SCSI architecture provides for a set of three pointers for each I/OhI process, called the saved pointers.  The set of three pointers consist of G one for the command, one for the data, and one for the status.  When anhH I/O process becomes active, its three saved pointers are copied into theD initiator's set of three current pointers.  There is only one set ofF current pointers in each initiator.  The current pointers point to the@ next command, data, or status byte to be transferred between theI initiator's memory and the target.  The saved and current pointers residea in the initiator.S  C The saved command pointer always points to the start of the commandrI descriptor block (see 7.2) for the I/O process.  The saved status pointerfG always points to the start of the status area for the I/O process.  ThebH saved data pointer points to the start of the data area until the targetC sends a SAVE DATA POINTER message (see 6.6.20) for the I/O process.e                      8                       Figure 17 - Simplified SCSI system    F In response to the SAVE DATA POINTER message, the initiator stores theJ value of the current data pointer into the saved data pointer for that I/OJ process.  The target may restore the current pointers to the saved pointerG values for the active I/O process by sending a RESTORE POINTERS message.J (see 6.6.19) to the initiator.  The initiator then copies the set of savedI pointers into the set of current pointers.  Whenever a target disconnectssF from the bus, only the set of saved pointers are retained.  The set of@ current pointers is restored from the set of saved pointers upon  reconnection of the I/O process.  M    NOTE 32 Since the data pointer value may be modified by the target before eK    the I/O process ends, it should not be used to test for actual transfer  %    length because it is not reliable.    6.5 Message system description  G The message system allows communication between an initiator and targeteG for the purpose of interface management.  A message may be one, two, orED multiple bytes in length.  One or more messages may be sent during aE single MESSAGE phase, but a message may not be split between multiplerG MESSAGE phases.  The initiator is required to end the MESSAGE OUT phase H (by negating ATN) when it sends certain messages identified in table 10.  H One-byte, two-byte, and extended message formats are defined.  The first@ byte of the message determines the format as defined in table 9.  3                            Table 9 - Message formatrO +=============-===============================================================+ O |    Value    |  Message format                                               | O |-------------+---------------------------------------------------------------|SO |     00h     |  One-byte message (COMMAND COMPLETE)                          |hO |     01h     |  Extended messages                                            |gO |  02h - 1Fh  |  One-byte messages                                            |lO |  20h - 2Fh  |  Two-byte messages                                            |hO |  30h - 7Fh  |  Reserved                                                     |rO |  80h - FFh  |  One-byte message (IDENTIFY)                                  |nO +=============================================================================+e    G One-byte messages consist of a single byte transferred during a MESSAGE I phase.  The value of the byte determines which message is to be performede as defined in table 10.   3                            Table 10 - Message codeslR +========-=========-===================================-=========-===============+R |Code    | Support |Message Name                       |Direction|               |R |        |---------|                                   |         |   Negate ATN  |R |        |Init|Targ|                                   |         |before last ACK|R |--------+----+----+-----------------------------------+---------+---------------|R |06h     | O  | M  |ABORT                              |      Out|      Yes      |R |0Dh     | O  | O  |ABORT TAG see note 1)              |      Out|      Yes      |R |0Ch     | O  | M  |BUS DEVICE RESET                   |      Out|      Yes      |R |0Eh     | O  | O  |CLEAR QUEUE see note 1)            |      Out|      Yes      |R |00h     | M  | M  |COMMAND COMPLETE                   | In      |      ---      |R |04h     | O  | O  |DISCONNECT                         | In      |      ---      |R |04h     | O  | O  |DISCONNECT                         |      Out|      Yes      |R |80h+    | M  | O  |IDENTIFY                           | In      |      ---      |R |80h+    | M  | M  |IDENTIFY                           |      Out|      No       |R |23h     | O  | O  |IGNORE WIDE RESIDUE (two bytes)    | In      |      ---      |R |0Fh     | O  | O  |INITIATE RECOVERY                  | In      |      ---      |R |0Fh     | O  | O  |INITIATE RECOVERY see note 2)      |      Out|      Yes      |R |05h     | M  | M  |INITIATOR DETECTED ERROR           |      Out|      Yes      |R |0Ah     | O  | O  |LINKED COMMAND COMPLETE            | In      |      ---      |R |0Bh     | O  | O  |LINKED COMMAND COMPLETE (WITH FLAG)| In      |      ---      |R |09h     | M  | M  |MESSAGE PARITY ERROR               |      Out|      Yes      |R |07h     | M  | M  |MESSAGE REJECT                     | In   Out|      Yes      |R |***     | O  | O  |MODIFY DATA POINTER                | In      |      ---      |R |08h     | M  | M  |NO OPERATION                       |      Out|      Yes      |R |        |    |    |Queue tag messages (two bytes)     |         |               |R |21h     | O  | O  |  HEAD OF QUEUE TAG                |      Out|      No       |R |22h     | O  | O  |  ORDERED QUEUE TAG                |      Out|      No       |R |20h     | O  | O  |  SIMPLE QUEUE TAG                 | In   Out|      No       |R |10h     | O  | O  |RELEASE RECOVERY                   |      Out|      Yes      |R |03h     | O  | O  |RESTORE POINTERS                   | In      |      ---      |R |02h     | O  | O  |SAVE DATA POINTER                  | In      |      ---      |R |***     | O  | O  |SYNCHRONOUS DATA TRANSFER REQUEST  | In   Out|      Yes      |R |11h     | O  | O  |TERMINATE I/O PROCESS              |      Out|      Yes      |R |***     | O  | O  |WIDE DATA TRANSFER REQUEST         | In   Out|      Yes      |R |12h-1Fh |    |    |Reserved                           |         |               |R |24h-2Fh |    |    |Reserved for two-byte messages     |         |               |R |30h-7Fh |    |    |Reserved                           |         |               |R |--------------------------------------------------------------------------------|R |Key:      M    = Mandatory support, O = Optional support.                       |R |          In   = Target to initiator,  Out = Initiator to target.               |R |          Yes  = Initiator shall negate ATN before last ACK of message.         |R |          No   = Initiator may or may not negate ATN before last ACK of         |R |                 message.  (see attention condition, 6.2.1.)                    |R |          ---  = Not applicable                                                 |R |          ***  = Extended message (see tables 11 and 12)                        |R |          80h+ = Codes 80h through FFh are used for IDENTIFY messages           |R |                 (see table 13).                                                |R |--------------------------------------------------------------------------------|R |      NOTES                                                                     |R |      1 The ABORT TAG and CLEAR QUEUE messages are required if tagged queuing   |R |        is implemented.                                                         |R |      2 Outbound INITIATE RECOVERY messages are only valid during the           |R |        asynchronous event notification protocol.                               |R +================================================================================+      G Two-byte messages consist of two consecutive bytes transferred during a/G MESSAGE phase.  The value of the first byte determines which message ishG to be performed as defined in table 10.  The second byte is a parameter C byte which is used as defined in the message description (see 6.6).l  H A value of one in the first byte of a message indicates the beginning ofG a multiple-byte extended message.  The minimum number of bytes sent for B an extended message is three.  The extended message format and theC extended message codes are shown in tables 11 and 12, respectively.e  8                       Table 11 - Extended message formatQ +=======-========-========-========-========-========-========-========-========+NQ |   Bit |   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |tQ |Byte   |        |        |        |        |        |        |        |        |gQ |=======+=======================================================================|iQ | 0     |                           Extended message (01h)                      |rQ |-------+-----------------------------------------------------------------------| Q | 1     |                           Extended message length (n)                 |sQ |-------+-----------------------------------------------------------------------|oQ | 2     |                           Extended message code (y)                   |1Q |-------+-----------------------------------------------------------------------|RQ | 3     |                                                                       |eQ |-------+---                        Extended message arguments               ---|aQ | n+1   |                                                                       |oQ +===============================================================================+     I The extended message length specifies the length in bytes of the extended G message code plus the extended message arguments to follow.  Therefore,sG the total length of the message is equal to the extended message lengthnH plus two.  A value of zero for the extended message length indicates 256
 bytes follow.a  H The extended message codes are listed in table 12.  The extended messageA arguments are specified within the extended message descriptions.t  7                       Table 12 - Extended message codesoO +=============-===============================================================+eO |  Code (y)   |  Description                                                  | O |-------------+---------------------------------------------------------------|sO |     02h     |  Reserved (see note)                                          |nO |     00h     |  MODIFY DATA POINTER                                          |eO |     01h     |  SYNCHRONOUS DATA TRANSFER REQUEST                            |dO |     03h     |  WIDE DATA TRANSFER REQUEST                                   |sO |  04h - 7Fh  |  Reserved                                                     |tO |  80h - FFh  |  Vendor-specific                                              | O |-----------------------------------------------------------------------------|oO |   NOTE - Extended message code 02h was used for the EXTENDED IDENTIFY       |eO |   message in SCSI-1.                                                        |yO +=============================================================================+c    G The first message sent by the initiator after the SELECTION phase shallhI be an IDENTIFY, ABORT, or BUS DEVICE RESET message.  If a target receivesp? any other message it shall go to BUS FREE phase (see unexpecteds disconnect, 6.1.1).a  G If the first message is an IDENTIFY message, then it may be immediatelydF followed by other messages, such as the first of a pair of SYNCHRONOUSH DATA TRANSFER REQUEST messages.  If tagged queuing is used the queue tagB message immediately follows the IDENTIFY message (see 6.6.7).  TheG IDENTIFY message establishes a logical connection between the initiatorhH and the specified logical unit or target routine within the target knownC as an I_T_L nexus or I_T_R nexus.  After the RESELECTION phase, theEI target's first message shall be IDENTIFY.  This allows the I_T_L nexus orgI I_T_R nexus to be reestablished.  Only one logical unit or target routine F shall be identified for any connection.  If a target receives a secondG IDENTIFY message with a different logical unit number or target routine-I number during a connection, it shall go to BUS FREE phase (see unexpectedoJ disconnect, 6.1.1).  The treatment of other logical unit addressing errors is described in 7.5.  F All initiators shall implement the mandatory messages tabulated in theC Init column of table 10.  All targets shall implement the mandatory 2 messages tabulated in the Targ column of table 10.  J Whenever an I_T_L nexus or I_T_R nexus is established by an initiator thatF is allowing disconnection, the initiator shall ensure that the currentI pointers are equal to the saved pointers for that particular logical unit H or target routine.  An implied restore pointers operation shall occur as a result of a reconnection.    6.6 Messages  0 The SCSI messages are defined in this subclause.   6.6.1 ABORTR  G The ABORT message is sent from the initiator to the target to clear anyhE I/O process for the I_T_x nexus.  The target shall go to the BUS FREE=F phase following successful receipt of this message.  The pending data,C status, and I/O processes for any other nexus shall not be cleared.r  I If only an I_T nexus has been established, the target shall go to the BUSbC FREE phase.  No status or message shall be sent for the current I/OT3 process and no other I/O process shall be affected.=      NOTESH    33 The ABORT message in the case of only an I_T nexus is useful to anM    initiator that cannot get an IDENTIFY message through to the target due to K    parity errors and just needs to end the current connection.  Any pending|K    data, status, or queued I/O processes for the I_T nexus is not affected.-P    34 It is not possible to abort an I_T nexus on a reconnection because of item    f) in 6.2.1.   H It is not an error to issue this message to an I_T_x nexus that does not% have an active or queued I/O process.   D Previously established conditions, including MODE SELECT parameters,H reservations, and extended contingent allegiance shall not be changed by the ABORT message.  K    NOTE 35 The BUS DEVICE RESET, CLEAR QUEUE, ABORT, and ABORT TAG messages|E    provide a means to clear one or more I/O processes prior to normal N    termination.  The BUS DEVICE RESET message clears all I/O processes for allN    initiators on all logical units and all target routines of the target.  TheI    CLEAR QUEUE message clears all I/O processes for all initiators on theYM    specified logical unit or target routine of the target.  The ABORT messageOP    clears all I/O processes for the selecting initiator on the specified logicalJ    unit or target routine of the target.  The ABORT TAG message clears the    current I/O process only.   6.6.2 ABORT TAGu  ? The ABORT TAG message shall be implemented if tagged queuing is G implemented and may be implemented if untagged queuing is implemented. MI The target shall go to the BUS FREE phase following successful receipt ofMF this message.  The target shall clear the current I/O process.  If theF target has already started execution of the I/O process, the executionG shall be halted.  The medium contents may have been modified before the I execution was halted.  In either case, any pending status or data for the J I/O process shall be cleared and no status or ending message shall be sentI to the initiator.  Pending status, data, and commands for other active or|C queued I/O processes shall not be affected.  Execution of other I/O : processes queued for the I_T_x nexus shall not be aborted.  D Previously established conditions, including MODE SELECT parameters,H reservations, and extended contingent allegiance shall not be changed by the ABORT TAG message.  G On a reconnection, the ABORT TAG message aborts the current I/O processOF if it is fully identified.  If the I/O process is not fully identifiedJ (i.e. an I_T_L nexus exists, but the target is reconnecting for an I_T_L_QJ nexus), then the I/O process is not aborted and the target goes to the BUS FREE phase.|  N    NOTE 36 A nexus is not fully identified on a reconnection if the ATN signalN    is asserted during or prior to the IDENTIFY message and the target only hasA    tagged I/O processes for that initiator on that logical unit.     6.6.3 BUS DEVICE RESET  I The BUS DEVICE RESET message is sent from an initiator to direct a target F to clear all I/O processes on that SCSI device.  This message forces aI hard reset condition to the selected SCSI device.  The target shall go to-E the BUS FREE phase following successful receipt of this message.  TheaF target shall create a unit attention condition for all initiators (see 7.9).    6.6.4 CLEAR QUEUE.  A The CLEAR QUEUE message shall be implemented if tagged queuing is G implemented and may be implemented if untagged queuing is implemented. tI The target shall go to the BUS FREE phase following successful receipt ofaI this message.  The target shall perform an action equivalent to receivinglH a series of ABORT messages from each initiator.  All I/O processes, fromD all initiators, in the queue for the specified logical unit shall beG cleared from the queue.  All active I/O processes shall be terminated.  E The medium may have been altered by partially executed commands.  All G pending status and data for that logical unit or target routine for all-H initiators shall be cleared.  No status or message shall be sent for anyH of the I/O processes.  A unit attention condition shall be generated forG all other initiators with I/O processes that either were active or were.H queued for that logical unit or target routine.  When reporting the unitF attention condition the additional sense code shall be set to COMMANDS CLEARED BY ANOTHER INITIATOR.i  D Previously established conditions, including MODE SELECT parameters,H reservations, and extended contingent allegiance shall not be changed by the CLEAR QUEUE message.   6.6.5 COMMAND COMPLETE  E The COMMAND COMPLETE message is sent from a target to an initiator toiJ indicate that the execution of an I/O process has completed and that validG status has been sent to the initiator.  After successfully sending thiseG message, the target shall go to the BUS FREE phase by releasing the BSYeA signal.  The target shall consider the message transmission to befG successful when it detects the negation of ACK for the COMMAND COMPLETEm$ message with the ATN signal false.    O    NOTE 37 The I/O process may have completed successfully or unsuccessfully asn    indicated in the status.=   6.6.6 DISCONNECT  H The DISCONNECT message is sent from a target to inform an initiator thatA the present connection is going to be broken (the target plans to H disconnect by releasing the BSY signal), but that a later reconnect willG be required in order to complete the current I/O process.  This message=> shall not cause the initiator to save the data pointer.  AfterF successfully sending this message, the target shall go to the BUS FREEI phase by releasing the BSY signal.  The target shall consider the message E transmission to be successful when it detects the negation of the ACK-< signal for the DISCONNECT message with the ATN signal false.  J Targets that break data transfers into multiple connections shall end eachI successful connection (except possibly the last) with a SAVE DATA POINTER- - DISCONNECT message sequence.  G This message may also be sent from an initiator to a target to instruct-I the target to disconnect from the SCSI bus.  If this option is supported,aH and after the DISCONNECT message is received, the target shall switch toH MESSAGE IN phase, send the DISCONNECT message to the initiator (possiblyH preceded by SAVE DATA POINTER message), and then disconnect by releasingI BSY.  After releasing the BSY signal, the target shall not participate insH another ARBITRATION phase for at least a disconnection delay or the timeI limit specified in the disconnect time limit mode parameter (see 8.3.3.2)gD whichever is greater.  If this option is not supported or the targetJ cannot disconnect at the time when it receives the DISCONNECT message fromC the initiator, the target shall respond by sending a MESSAGE REJECT2 message to the initiator.    6.6.7 IDENTIFY  J The IDENTIFY message (see table 13) is sent by either the initiator or the5 target to establish an I_T_L nexus or an I_T_R nexus.   I    NOTE 38 Use of the IDENTIFY message to establish an I_T_R nexus allows-P    connection to one of up to eight target routines or functions in the target. O    These target routines are expected to be used for maintenance and diagnostic     purposes.  8                       Table 13 - IDENTIFY message formatO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |=====+========+========+========+========+========+==========================| O |     |Identify|DiscPriv| LUNTAR |Reserved|Reserved|          LUNTRN          |-O +=============================================================================+E    H The identify bit shall be set to one to specify that this is an IDENTIFY message.  I A disconnect privilege (DiscPriv) bit of one specifies that the initiator=I has granted the target the privilege of disconnecting.  A DiscPriv bit of E zero specifies that the target shall not disconnect.  This bit is notaF defined and shall be set to zero when an IDENTIFY message is sent by a target.u  I A logical unit target (LUNTAR) bit of zero specifies that the I/O processgJ is directed to or from a logical unit.  A LUNTAR bit of one specifies that: the I/O process is directed to or from a target routine.    H The logical unit number target routine number (LUNTRN) field specifies aJ logical unit number if the LUNTAR bit is zero.  The LUNTRN field specifiesE a target routine number if the LUNTAR bit is one.  The response to antJ invalid value in the LUNTRN field is described in 7.5.3.  Only the INQUIRYF and REQUEST SENSE commands are valid for target routines.  If a targetF receives any other command for a target routine, it shall return CHECK@ CONDITION status and shall set the sense key to ILLEGAL REQUEST.  H An IDENTIFY message is invalid if a reserved bit is set to one or if theA LUNTAR bit is set to one and the target does not implement target A routines.  A device may respond to an invalid IDENTIFY message by B immediately sending a MESSAGE REJECT message or by returning CHECKI CONDITION status.  If a CHECK CONDITION status is returned, the sense key J shall be set to ILLEGAL REQUEST and the additional sense code shall be set* to INVALID BITS IN IDENTIFY MESSAGE FIELD.  I Only one logical unit number or target routine number shall be identifiedaF per I/O process.  The initiator may send one or more IDENTIFY messagesI during a connection.  A second IDENTIFY message with a different value incF either the LUNTAR bit or LUNTRN field shall not be issued before a BUSH FREE phase has occurred;  if a target receives a second IDENTIFY messageI with a different value in either of these fields, it shall go to BUS FREEsG phase (see unexpected disconnect, 6.1.1).  Thus an initiator may change_H the DiscPriv bit, but may not attempt to switch to another I/O process. B (See the DTDC field of the disconnect-reconnect page (8.3.3.2) for( additional controls over disconnection.)  G An implied RESTORE POINTERS message shall be performed by the initiator I prior to the assertion of the ACK signal on the next phase for an inbound/* IDENTIFY message sent during reconnection.  H An implied RESTORE POINTERS message shall be performed by the initiator G following  successful identification of the nexus during the MESSAGE INtG phase of a reconnection and before the  negation  of  the  ACK  signal c@ for  the  next transfer following the successful identification.  G Identification is considered successful during an initial connection orbB an initiator reconnect when the target detects no error during theI transfer of the IDENTIFY message and an optional queue tag message in thetJ MESSAGE OUT phase immediately following the SELECTION phase.   See 6.5 forF the ordering of the  IDENTIFY and queue tag messages.  See 6.1.9.2 for> handling target detected errors during the MESSAGE OUT phase.   J Identification is considered successful during a target reconnect when theE ATN signal is not asserted during the transfer of either the IDENTIFY C message or the SIMPLE QUEUE TAG message for an I_T_L_Q nexus in thefI MESSAGE IN phase immediately following the RESELECTION phase.  See clauseaH 6.5 for the ordering of the IDENTIFY and queue tag messages.  See 6.2.1,I item d), for handling target detected errors during the MESSAGE IN phase.h   6.6.8 IGNORE WIDE RESIDUEl  =                 Table 14 - IGNORE WIDE RESIDUE message formatcP +======-========-========-========-========-========-========-========-========+P |   Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P |Byte  |        |        |        |        |        |        |        |        |P |======+=======================================================================|P | 0    |                           Message code (23h)                          |P |------+-----------------------------------------------------------------------|P | 1    |                           Ignore (01h, 02h, 03h)                      |P +==============================================================================+    J The IGNORE WIDE RESIDUE message (see table 14) shall be sent from a targetG to indicate that the number of valid bytes sent during the last REQ/ACKeE handshake and REQB/ACKB handshake of a DATA IN phase is less than thefD negotiated transfer width.  The ignore field indicates the number ofG invalid data bytes transferred.  This message shall be sent immediatelynI following that DATA IN phase and prior to any other messages.  The ignorer field is defined in table 15.a  L    NOTE 39 More than one IGNORE WIDE RESIDUE message may occur during an I/O    process.l  8                       Table 15 - Ignore field definition7 +=============-=======================================+s7 |   Ignore    |           Invalid data bits           |e7 |             |---------------------------------------|o7 |             |  32-bit transfers | 16-bit transfers  |r7 |-------------+-------------------+-------------------|e7 |     00h     |      Reserved     |    Reserved       | 7 |     01h     |      DB(31-24)    |    DB(15-8)       |e7 |     02h     |      DB(31-16)    |    Reserved       |a7 |     03h     |      DB(31-8)     |    Reserved       |s7 |  04h - FFh  |      Reserved     |    Reserved       |e7 +=====================================================+s    I Even though a byte is invalid its corresponding parity bit shall be validiF for the value transferred.  For 16-bit transfers, DB(31-16) are always; invalid and the corresponding parity bits are also invalid.m   6.6.9 INITIATE RECOVERYd  F A target that supports extended contingent allegiance shall inform theG initiator it is entering this condition by sending an INITIATE RECOVERY E message immediately following a CHECK CONDITION or COMMAND TERMINATEDfG status.  The extended contingent allegiance condition remains in effecte% until terminated as described in 7.7.e  A If an asynchronous event occurs, the target may enter an extendedeE contingent allegiance condition by becoming a temporary initiator and H sending the INITIATE RECOVERY message following the IDENTIFY message andF any queue tag message and before the COMMAND phase of the SEND commandI that is used to perform the asynchronous event notification (see 7.5.5). dD The successful transmission of this message establishes the extendedH contingent allegiance condition which remains in effect until terminated as described in 7.7.  P    NOTE 40 If the target notifies multiple initiators of the asynchronous event,E    it should include the INITIATE RECOVERY message in only one of them    notifications.s  H A MESSAGE REJECT response to an INITIATE RECOVERY message indicates thatJ an extended contingent allegiance condition shall not be established.  TheC enabled or disabled state of an extended contingent allegiance (see I 8.3.3.1) is not changed by the rejection of an INITIATE RECOVERY message.a   6.6.10 INITIATOR DETECTED ERRORi  H The INITIATOR DETECTED ERROR message is sent from an initiator to informJ a target that an error has occurred that does not preclude the target fromI retrying the operation.  The source of the error may either be related to G previous activities on the SCSI bus or may be internal to the initiatoreJ and unrelated to any previous SCSI bus activity.  Although present pointerD integrity is not assured, a RESTORE POINTERS message or a disconnectI followed by a reconnect, shall cause the pointers to be restored to theirt defined prior state.   6.6.11 LINKED COMMAND COMPLETE  I The LINKED COMMAND COMPLETE message is sent from a target to an initiatorOI to indicate that the execution of a linked command has completed and thatiG status has been sent.  The initiator shall then set the pointers to theh* initial state for the next linked command.  * 6.6.12 LINKED COMMAND COMPLETE (WITH FLAG)  H The LINKED COMMAND COMPLETE (WITH FLAG) message is sent from a target toI an initiator to indicate that the execution of a linked command (with thekF flag bit set to one) has completed and that status has been sent.  TheF initiator shall then set the pointers to the initial state of the nextA linked command.  Typically this message would be used to cause ana7 interrupt in the initiator between two linked commands.o   6.6.13 MESSAGE PARITY ERROR   I The MESSAGE PARITY ERROR message is sent from the initiator to the targetlD to indicate that it received a message byte with a parity error (see	 6.1.9.2).b  J In order to indicate its intentions of sending this message, the initiatorJ shall assert the ATN signal prior to its release of the ACK signal for theF REQ/ACK handshake of the message byte that has the parity error.  ThisI provides an interlock so that the target can determine which message bytegJ has the parity error.  If the target receives this message under any otherI circumstance, it shall signal a catastrophic error condition by releasing D the BSY signal without any further information transfer attempt (see 6.1.1).e  I If after receiving the MESSAGE PARITY ERROR message the target returns to E the MESSAGE IN phase before switching to some other phase, the targetn: shall resend the entire message that had the parity error.   6.6.14 MESSAGE REJECTa  I The MESSAGE REJECT message is sent from either the initiator or target toh> indicate that the last message or message byte it received was* inappropriate or has not been implemented.  J In order to indicate its intentions of sending this message, the initiatorJ shall assert the ATN signal prior to its release of the ACK signal for theE REQ/ACK handshake of the message byte that is to be rejected.  If the=J target receives this message under any other circumstance, it shall reject this message.  f  I When a target sends this message, it shall change to MESSAGE IN phase and=G send this message prior to requesting additional message bytes from the J initiator.  This provides an interlock so that the initiator can determine which message byte is rejected.e  F After a target sends a MESSAGE REJECT message and if the ATN signal isC still asserted, then it shall return to the MESSAGE OUT phase.  ThesJ subsequent MESSAGE OUT phase shall begin with the first byte of a message.  " 6.6.15 MODIFY DATA POINTER Message  6                         Table 16 - MODIFY DATA POINTERP +======-========-========-========-========-========-========-========-========+P |   Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P |Byte  |        |        |        |        |        |        |        |        |P |======+=======================================================================|P | 0    |                           Extended message (01h)                      |P |------+-----------------------------------------------------------------------|P | 1    |                           Extended message length (05h)               |P |------+-----------------------------------------------------------------------|P | 2    |                           MODIFY DATA POINTER (00h)                   |P |------+-----------------------------------------------------------------------|P | 3    | (MSB)                                                                 |P |------+---                        Argument                                 ---|P | 6    |                                                                 (LSB) |P +==============================================================================+    I The MODIFY DATA POINTER message (see table 16) is sent from the target tolC the initiator and requests that the signed argument be added (two'se5 complement) to the value of the current data pointer.T   6.6.16 NO OPERATIONe  C The NO OPERATION message is sent from an initiator in response to aeI target's request for a message when the initiator does not currently haveN  any other valid message to send.  F For example, if the target does not respond to the attention conditionF until a later phase and at that time the original message is no longerE valid the initiator may send the NO OPERATION message when the target  enters the MESSAGE OUT phase.c   6.6.17 Queue tag messagesn  8                      Table 17 - Queue tag message formatP +======-========-========-========-========-========-========-========-========+P |   Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P |Byte  |        |        |        |        |        |        |        |        |P |======+=======================================================================|P | 0    |                           Message code (20h, 21h, 22h)                |P |------+-----------------------------------------------------------------------|P | 1    |                           Queue tag (00h - FFh)                       |P +==============================================================================+    F Table 17 defines the format for the queue tag messages.  If the targetH implements tagged queuing, all of the queue tag messages are mandatory: C HEAD OF QUEUE TAG, ORDERED QUEUE TAG, and SIMPLE QUEUE TAG.  TaggedAC queuing is only defined for logical units, not for target routines.r  H If a target does not implement tagged queuing and a queue tag message isG received or if a queue tag message is received for a target routine, itQI shall respond with a MESSAGE REJECT message and accept the I/O process ase if it were untagged.  H The queue tag messages are used to specify an identifier, called a queueG tag, for the I/O process that establishes the I_T_L_Q nexus.  The queue.G tag field is an 8-bit unsigned integer assigned by the initiator duringmJ an initial connection.  The queue tag for every I/O process for each I_T_LC nexus should be unique.  If the target receives a queue tag that is3I currently in use for the I_T_L nexus, then it shall respond as defined in C 7.5.2.  A queue tag becomes available for reassignment when the I/O=J process ends.  The numeric value of a queue tag has no effect on the order
 of execution.a  M    NOTE 41 For each logical unit on each target, each initiator has up to 256-K    queue tags to assign to I/O processes.  Thus a target with eight logicalIK    units could have up to 14 336 I/O processes concurrently in existence if=*    there were seven initiators on the bus.  E Whenever an initiator connects to a target, the appropriate queue tagoD message shall be sent immediately following the IDENTIFY message andH within the same MESSAGE OUT phase to establish the I_T_L_Q nexus for the@ I/O process.  Only one I_T_L_Q nexus may be established during aI connection.  If a queue tag message is not sent, then only an I_T_x nexusn6 is established for the I/O process (untagged command).  E Whenever a target reconnects to an initiator to continue a tagged I/ONI process, the SIMPLE QUEUE TAG message shall be sent immediately following G the IDENTIFY message and within the same MESSAGE IN phase to revive the=I I_T_L_Q nexus for the I/O process.  Only one I_T_L_Q nexus may be revived I during a reconnection.  If the SIMPLE QUEUE TAG message is not sent, then-F only an I_T_x nexus is revived for the I/O process (untagged command).  F If a target attempts to reconnect using an invalid queue tag, then the3 initiator should respond with an ABORT TAG message.    6.6.17.1 HEAD OF QUEUE TAG  F The HEAD OF QUEUE TAG message specifies that the I/O process be placedI first in that logical unit's command queue.  An I/O process already beinghH executed by the target shall not be preempted.  A subsequent I/O processH received with a HEAD OF QUEUE TAG message shall be placed at the head of= the command queue for execution in last-in, first-out order.     6.6.17.2 ORDERED QUEUE TAG  I The ORDERED QUEUE TAG message specifies that the I/O process be placed in G that logical unit's command queue for execution in the order received. lH All queued I/O processes for the logical unit received prior to this I/OD process shall be executed before this I/O process is executed.   AllF queued I/O processes received after this I/O process shall be executedH after this I/O process, except for I/O processes received with a HEAD OF QUEUE TAG message.   6.6.17.3 SIMPLE QUEUE TAGe  H The SIMPLE QUEUE TAG message specifies that the I/O process be placed inG that logical unit's command queue.  The order of execution is describedm in 7.8.d   6.6.18 RELEASE RECOVERY   E The RELEASE RECOVERY message is sent from an initiator to a target to @ terminate an extended contingent allegiance condition previouslyH established by an INITIATE RECOVERY message.  This message shall be sentJ immediately following the IDENTIFY message in the same MESSAGE OUT phase. I The extended contingent allegiance condition ends upon successful receiptvE of the RELEASE RECOVERY message.  The target shall go to the BUS FREE 3 phase following successful receipt of this message.   E If a RELEASE RECOVERY message is received by a target that implementslE extended contingent allegiance when an extended contingent allegiancetJ condition does not exist, the message shall not be rejected and the target shall go to the BUS FREE phase.E   6.6.19 RESTORE POINTERSI  J The RESTORE POINTERS message is sent from a target to direct the initiatorJ to copy the most recently saved command, data, and status pointers for theJ I/O process to the corresponding current pointers.  The command and statusF pointers shall be restored to the beginning of the present command andE status areas.  The data pointer shall be restored to the value at the H beginning of the data area in the absence of a SAVE DATA POINTER messageH or to the value at the point at which the last SAVE DATA POINTER message occurred for that nexus.   6.6.20 SAVE DATA POINTER  A The SAVE DATA POINTER message is sent from a target to direct thenH initiator to copy the current data pointer to the saved data pointer forA the current I/O process.  (See 6.4 for a definition of pointers.)i  0 6.6.21 SYNCHRONOUS DATA TRANSFER REQUEST message  =                  Table 18 - SYNCHRONOUS DATA TRANSFER REQUESTEP +======-========-========-========-========-========-========-========-========+P |   Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P |Byte  |        |        |        |        |        |        |        |        |P |======+=======================================================================|P | 0    |                           Extended message (01h)                      |P |------+-----------------------------------------------------------------------|P | 1    |                           Extended message length (03h)               |P |------+-----------------------------------------------------------------------|P | 2    |                           SYNCHRONOUS DATA TRANSFER REQUEST code (01h)|P |------+-----------------------------------------------------------------------|P | 3    |                           Transfer period factor                      |P |------+-----------------------------------------------------------------------|P | 4    |                           REQ/ACK offset                              |P +==============================================================================+  J A SYNCHRONOUS DATA TRANSFER REQUEST (SDTR) message (see table 18) exchangeH shall be initiated by an SCSI device whenever a previously-arranged dataJ transfer agreement may have become invalid.  The agreement becomes invalidE after any condition which may leave the data transfer agreement in ant indeterminate state such as:'    a)     after a hard reset condition;y/    b)     after a BUS DEVICE RESET message and;     c)     after a power cycle.  J In addition, an SCSI device may initiate an SDTR message exchange wheneverD it is appropriate to negotiate a new data transfer agreement (either? synchronous or asynchronous).  SCSI devices that are capable oftF synchronous data transfers shall not respond to an SDTR message with a MESSAGE REJECT message.t      NOTESN    42 Renegotiation at every selection is not recommended, since a significant"    performance impact is likely.  O    43 Due to historical problems with early host adapters that could not accepttO    an SDTR message, some targets may not initiate synchronous negotiation after J    a power cycle as required by this standard.  Host adapters that supportJ    synchronous mode may avoid the ensuing failure modes when the target isM    independently power cycled by initiating a synchronous negotiation on each %    REQUEST SENSE and INQUIRY command.T  J The SDTR message exchange establishes the permissible transfer periods andH the REQ/ACK offsets for all logical units and target routines on the two5 devices.  This agreement only applies to data phases.   K The transfer period factor times four is the value of the transfer period. =H The transfer period is the minimum time allowed between leading edges ofE successive REQ pulses and of successive ACK pulses to meet the device-0 requirements for successful reception of data.    D The REQ/ACK offset is the maximum number of REQ pulses allowed to beE outstanding before the leading edge of its corresponding ACK pulse is-A received at the target.  This value is chosen to prevent overflowMJ conditions in the device's reception buffer and offset counter.  A REQ/ACKF offset value of zero shall indicate asynchronous data transfer mode; a5 value of FFh shall indicate unlimited REQ/ACK offset.   F The originating device (the device that sends the first of the pair ofH SDTR messages) sets its values according to the rules above to permit itH to receive data successfully.  If the responding device can also receiveJ data successfully with these values (or smaller transfer periods or largerJ REQ/ACK offsets or both), it returns the same values in its SDTR message. J If it requires a larger transfer period, a smaller REQ/ACK offset, or bothH in order to receive data successfully, it substitutes values in its SDTRE message as required, returning unchanged any value not required to benI changed.  Each device when transmitting data shall respect the limits setxF by the other's SDTR message, but it is permitted to transfer data withH larger transfer periods, smaller REQ/ACK offsets, or both than specifiedI in the other's SDTR message.  The successful completion of an exchange ofM. SDTR messages implies an agreement as follows:  K Responding device SDTR response                           Implied agreement=X a) Non-zero REQ/ACK offset                             Each device transmits data with a_                                                        transfer period equal to or greater than \                                                        and a REQ/ACK offset equal to or less\                                                        than the values received in the otherM                                                        device's SDTR message.-  R b) REQ/ACK offset equal to zero                              Asynchronous transfer  H c) MESSAGE REJECT message                          Asynchronous transfer  H If the initiator recognizes that negotiation is required, it asserts theF ATN signal and sends a SDTR message to begin the negotiating process. E After successfully completing the MESSAGE OUT phase, the target shallQH respond with the proper SDTR message.  If an abnormal condition preventsH the target from returning an appropriate response, both devices shall goE to asynchronous data transfer mode for data transfers between the twot devices.  J Following target response (1) above, the implied agreement for synchronousI operation shall be considered to be negated by both the initiator and theaH target if the initiator asserts the ATN signal and the first message outD is either MESSAGE PARITY ERROR or MESSAGE REJECT. In this case, bothF devices shall go to asynchronous data transfer mode for data transfersH between the two devices.  For the MESSAGE PARITY ERROR case, the impliedJ agreement shall be reinstated if a retransmittal of the second of the pairI of messages is successfully accomplished.  After a vendor-specific number G of retry attempts (greater than zero), if the target receives a MESSAGEaI PARITY ERROR message, it shall terminate the retry activity.  This may be C done either by changing to any other information transfer phase andaI transferring at least one byte of information or by going to the BUS FREEhJ phase (see 6.1.1).  The initiator shall accept such action as aborting theI negotiation, and both devices shall go to asynchronous data transfer mode - for data transfers between the two devices.  n  G If the target recognizes that negotiation is required, it sends an SDTRUH message to the initiator.  Prior to releasing the ACK signal on the lastH byte of the SDTR message from the target, the initiator shall assert theE ATN signal and respond with its SDTR message or with a MESSAGE REJECToH message.  If an abnormal condition prevents the initiator from returningC an appropriate response, both devices shall go to asynchronous data 9 transfer mode for data transfers between the two devices.t  J Following an initiator's responding SDTR message, an implied agreement forG synchronous operation shall not be considered to exist until the targeteI leaves the MESSAGE OUT phase, indicating that the target has accepted thedG negotiation.  After a vendor-specific number of retry attempts (greaternJ than zero), if the target has not received the initiator's responding SDTRJ message, it shall go to the BUS FREE phase without any further informationG transfer attempt (see 6.1.1).  This indicates that a catastrophic errortC condition has occurred.  Both devices shall go to asynchronous datag9 transfer mode for data transfers between the two devices.v  G If, following an initiator's responding SDTR message, the target shiftsmC to MESSAGE IN phase and the first message in is MESSAGE REJECT, theDJ implied agreement shall be considered to be negated and both devices shallH go to asynchronous data transfer mode for data transfers between the two devices.  D The implied synchronous agreement shall remain in effect until a BUSI DEVICE RESET message is received, until a hard reset condition occurs, orAF until one of the two SCSI devices elects to modify the agreement.  TheC default data transfer mode is asynchronous data transfer mode.  TheHE default data transfer mode is entered at power on, after a BUS DEVICEQ/ RESET message, or after a hard reset condition.e   6.6.22 TERMINATE I/O PROCESS  J The TERMINATE I/O PROCESS message is sent from the initiator to the targetC to terminate the current I/O process without corrupting the medium.r  I With the following exceptions, the target shall terminate the current I/OoI process and return COMMAND TERMINATED status.  The sense key shall be seteD to NO SENSE.  The additional sense code and qualifier are set to I/O PROCESS TERMINATED.d  I If the associated I/O process involves a data phase, the target shall setEG the valid bit in the sense data to one and set the information field as  follows:K    a)     If the command descriptor block specifies an allocation length ortJ           parameter list length, the information field shall be set to theG           difference (residue) between the number of bytes successfullyj/           transferred and the requested length.aL    b)     If the command descriptor block specifies a transfer length field,L           the information field shall be set as defined in the REQUEST SENSE           command (see 8.2.14)./  G If an error is detected for the associated I/O process the target shallo) ignore the TERMINATE I/O PROCESS message.f  B If the operation requested for the associated I/O process has beenG completed but status has not been returned, the target shall ignore thea TERMINATE I/O PROCESS message.  D If the target does not support this message or is unable to stop theB current I/O process, it shall send a MESSAGE REJECT message to the: initiator and continue the I/O process in a normal manner.  J The effect of a TERMINATE I/O PROCESS message on the command queue dependsJ on the queue error recovery option specified in the control mode page (seeC 8.3.3.1) and on whether or not a contingent allegiance condition isR
 generated.  O    NOTE 44 The TERMINATE I/O PROCESS message provides a means for the initiator=M    to request the target to reduce the transfer length of the current command N    to the amount that has already been transferred.  The initiator can use theN    sense data to determine the actual number of bytes or blocks that have beenI    transferred.  This message is normally used by the initiator to stop a0M    lengthy read, write, or verify operation when a higher-priority command is-G    available to be executed.  It is up to the initiator to complete the 3    terminated command at a later time, if required.-  ) 6.6.23 WIDE DATA TRANSFER REQUEST message-  9                     Table 19 - WIDE DATA TRANSFER MESSAGEOP +======-========-========-========-========-========-========-========-========+P |   Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P |Byte  |        |        |        |        |        |        |        |        |P |======+=======================================================================|P | 0    |                           Extended message (01h)                      |P |------+-----------------------------------------------------------------------|P | 1    |                           Extended message length (02h)               |P |------+-----------------------------------------------------------------------|P | 2    |                           WIDE DATA TRANSFER REQUEST code (03h)       |P |------+-----------------------------------------------------------------------|P | 3    |                           Transfer width exponent                     |P +==============================================================================+    I A WIDE DATA TRANSFER REQUEST (WDTR) message (see table 19) exchange shall F be initiated by an SCSI device whenever a previously-arranged transferG width agreement may have become invalid.  The agreement becomes invalidaE after any condition which may leave the data transfer agreement in ann indeterminate state such as:'    a)     after a hard reset condition; /    b)     after a BUS DEVICE RESET message and;h    c)     after a power cycle.  I In addition, an SCSI device may initiate a WDTR message exchange wheneverpD it is appropriate to negotiate a new transfer width agreement.  SCSII devices that are capable of wide data transfers (greater than eight bits) B shall not respond to a WDTR message with a MESSAGE REJECT message.  G    NOTE 45 Renegotiation at every selection is not recommended, since aa-    significant performance impact is likely. s  C The WDTR message exchange establishes an agreement between two SCSItI devices on the width of the data path to be used for DATA phase transfersfH between the two devices.  This agreement applies to DATA IN and DATA OUTJ phases only.  All other information transfer phases shall use an eight-bit
 data path.  ? If an SCSI device implements both wide data transfer option andrG synchronous data transfer option, then it shall negotiate the wide databE transfer agreement prior to negotiating the synchronous data transferiG agreement.  If a synchronous data transfer agreement is in effect, thenoF an SCSI device that accepts a WDTR message shall reset the synchronous agreement to asynchronous mode.s  I The transfer width is two to the transfer width exponent bytes wide.  TheFG transfer width that is established applies to all logical units on bothhB SCSI devices.  Valid transfer widths are 8 bits (m = 00h), 16 bitsC (m = 01h), and 32 bits (m = 02h).  Values of m greater than 02h areu	 reserved.   H The originating SCSI device (the SCSI device that sends the first of theH pair of WDTR messages) sets its transfer width value to the maximum dataG path width it elects to accommodate.  If the responding SCSI device cannF also accommodate this transfer width, it returns the same value in itsJ WDTR message.  If it requires a smaller transfer width, it substitutes theC smaller value in its WDTR message.  The successful completion of anh: exchange of WDTR messages implies an agreement as follows:  K Responding device WDTR response                           Implied agreement a a) Non-zero transfer width                                Each device transmits and receives dataf\                                                           with a transfer width equal to the[                                                           responding SCSI device's transfert@                                                           width.  X b) Transfer width equal to zero                                  Eight-bit data transfer  J c) MESSAGE REJECT message                          Eight-bit data transfer  H If the initiator recognizes that negotiation is required, it asserts theF ATN signal and sends a WDTR message to begin the negotiating process. E After successfully completing the MESSAGE OUT phase, the target shall H respond with the proper WDTR message.  If an abnormal condition preventsH the target from returning an appropriate response, both devices shall goB to eight-bit data transfer mode for data transfers between the two devices.  G Following target response 1) above, the implied agreement for wide datayI transfers shall be considered to be negated by both the initiator and theeG target if the initiator asserts ATN and the first message out is eithernI MESSAGE PARITY ERROR or MESSAGE REJECT.  In this case, both devices shallaE go to eight-bit data transfer mode for data transfers between the twoaH devices.  For the MESSAGE PARITY ERROR case, the implied agreement shallI be reinstated if a retransmittal of the second of the pair of messages is C successfully accomplished.  After a vendor-specific number of retrytE attempts (greater than zero), if the target receives a MESSAGE PARITY G ERROR message, it shall terminate the retry activity.  This may be doneh> either by changing to any other information transfer phase andI transferring at least one byte of information or by going to the BUS FREE J phase (see 6.1.1).  The initiator shall accept such action as aborting theJ negotiation, and both devices shall go to eight-bit data transfer mode for( data transfers between the two devices.   F If the target recognizes that negotiation is required, it sends a WDTRH message to the initiator.  Prior to releasing the ACK signal on the lastH byte of the WDTR message from the target, the initiator shall assert theE ATN signal and respond with its WDTR message or with a MESSAGE REJECTtH message.  If an abnormal condition prevents the initiator from returningI an appropriate response, both devices shall go to eight-bit data transfer 0 mode for data transfers between the two devices.  J Following an initiator's responding WDTR message, an implied agreement forG wide data transfer operation shall not be considered to exist until theeC target leaves the MESSAGE OUT phase, indicating that the target hastB accepted the negotiation.  After a vendor-specific number of retry@ attempts (greater than zero), if the target has not received theF initiator's responding WDTR message, it shall go to the BUS FREE phaseC without any further information transfer attempt (see 6.1.1).  ThiscI indicates that a catastrophic error condition has occurred.  Both devicesiG shall go to eight-bit data transfer mode for data transfers between thei two devices.  G If, following an initiator's responding WDTR message, the target shiftsiC to MESSAGE IN phase and the first message in is MESSAGE REJECT, thetJ implied agreement shall be considered to be negated and both devices shallE go to eight-bit data transfer mode for data transfers between the two  devices.  G The implied transfer width agreement shall remain in effect until a BUS I DEVICE RESET message is received, until a hard reset condition occurs, or F until one of the two SCSI devices elects to modify the agreement.  TheI default data transfer width is eight-bit data transfer mode.  The defaultoC data transfer mode is entered at power on, after a BUS DEVICE RESETo) message, or after a hard reset condition.m     7 SCSI commands and status  D This clause defines the SCSI command and status structures and gives several examples.n  G By keeping to a minimum the functions essential to communicate via thisaF protocol, a wide range of peripheral devices of varying capability canJ operate in the same environment.  Because subsets of the full architecture1 may be implemented, optional functions are noted.I  ' 7.1 Command implementation requirementss  F The first byte of all SCSI commands shall contain an operation code asD defined in this International Standard.  Targets shall implement allI commands with a mandatory operation code (see 7.1.2) both in clause 8 andD0 in the appropriate clause for their device type.   7.1.1 Reserved  F Reserved bits, fields, bytes, and code values are set aside for futureI standardization.  Their use and interpretation may be specified by futureEI extensions to this standard.  A reserved bit, field, or byte shall be set F to zero, or in accordance with a future extension to this standard.  AG target that receives a reserved bit, field, or byte that is not zero oraE receives a reserved code value shall terminate the command with CHECKbG CONDITION status and the sense key shall be set to ILLEGAL REQUEST.  ItbI shall also be acceptable for a target to interpret a bit, field, byte, or F code value in accordance with a future extension to this International	 Standard.    7.1.2 Operation code types  1 The operation code types are defined in table 20.t  6                         Table 20 - Operation code typeO +=============-===============================================================+eO |  Operation  |  Description                                                  |RO |  code type  |                                                               |pO |-------------+---------------------------------------------------------------|oO |      M      |  Mandatory - Commands so designated shall be implemented in   |/O |             |  order to meet the minimum requirement of this International  |nO |             |  Standard.                                                    |gO |             |                                                               |mO |      O      |  Optional - Commands so designated, if implemented, shall be  |eO |             |  implemented as defined in this International Standard.       |tO |             |                                                               |bO |      V      |  Vendor-specific - Operation codes so designated are available|sO |             |  for vendor defined commands.  See the vendor specifications  |aO |             |  where compatibility is desired.                              |aO |             |                                                               |.O |      R      |  Reserved - Operation codes so designated shall not be used.  |AO |             |  They are reserved for future extensions to this              |-O |             |  International Standard.                                      ||O +=============================================================================+|     7.2 Command descriptor block  F A command is communicated by sending a command descriptor block to theJ target.  For several commands, the command descriptor block is accompaniedI by a list of parameters sent during the DATA OUT phase.  See the specific-" commands for detailed information.  F The command descriptor block always has an operation code as its first) byte and a control byte as its last byte.-  A For all commands, if there is an invalid parameter in the command E descriptor block, then the target shall terminate the command without- altering the medium.  G       Table 21 - Typical command descriptor block for six-byte commands P +======-========-========-========-========-========-========-========-========+P |   Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P |Byte  |        |        |        |        |        |        |        |        |P |======+=======================================================================|P | 0    |                           Operation code                              |P |------+-----------------------------------------------------------------------|P | 1    |   Logical unit number    | (MSB)                                      |P |------+------------------------------                                      ---|P | 2    |                           Logical block address (if required)         |P |------+---                                                                 ---|P | 3    |                                                                 (LSB) |P |------+-----------------------------------------------------------------------|P |      |                           Transfer length (if required)               |P | 4    |                           Parameter list length (if required)         |P |      |                           Allocation length (if required)             |P |------+-----------------------------------------------------------------------|P | 5    |                           Control                                     |P +==============================================================================+  G       Table 22 - Typical command descriptor block for ten-byte commands P +======-========-========-========-========-========-========-========-========+P |   Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P |Byte  |        |        |        |        |        |        |        |        |P |======+=======================================================================|P | 0    |                           Operation code                              |P |------+-----------------------------------------------------------------------|P | 1    |   Logical unit number    |                  Reserved                  |P |------+-----------------------------------------------------------------------|P | 2    | (MSB)                                                                 |P |------+---                                                                 ---|P | 3    |                                                                       |P |------+---                        Logical block address (if required)      ---|P | 4    |                                                                       |P |------+---                                                                 ---|P | 5    |                                                                 (LSB) |P |------+-----------------------------------------------------------------------|P | 6    |                           Reserved                                    |P |------+-----------------------------------------------------------------------|P | 7    | (MSB)                     Transfer length (if required)               |P |------+---                        Parameter list length (if required)      ---|P | 8    |                           Allocation length (if required)       (LSB) |P |------+-----------------------------------------------------------------------|P | 9    |                           Control                                     |P +==============================================================================+    I      Table 23 - Typical command descriptor block for twelve-byte commandsdP +======-========-========-========-========-========-========-========-========+P |   Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P |Byte  |        |        |        |        |        |        |        |        |P |======+=======================================================================|P | 0    |                           Operation code                              |P |------+-----------------------------------------------------------------------|P | 1    |   Logical unit number    |                  Reserved                  |P |------+-----------------------------------------------------------------------|P | 2    | (MSB)                                                                 |P |------+---                                                                 ---|P | 3    |                                                                       |P |------+---                        Logical block address (if required)      ---|P | 4    |                                                                       |P |------+---                                                                 ---|P | 5    |                                                                 (LSB) |P |------+-----------------------------------------------------------------------|P | 6    | (MSB)                                                                 |P |------+---                                                                 ---|P | 7    |                           Transfer length (if required)               |P |------+---                        Parameter list length (if required)      ---|P | 8    |                           Allocation length (if required)             |P |------+---                                                                 ---|P | 9    |                                                                 (LSB) |P |------+-----------------------------------------------------------------------|P |10    |                           Reserved                                    |P |------+-----------------------------------------------------------------------|P |11    |                           Control                                     |P +==============================================================================+     7.2.1 Operation code  G The operation code (see table 24) of the command descriptor block has a J group code field and a command code field.  The three-bit group code fieldF provides for eight groups of command codes.  The five-bit command codeI field provides for thirty-two command codes in each group.  Thus, a total J of 256 possible operation codes exist.  Operation codes are defined in the subsequent subclauses.  5 The group code specifies one of the following groups:o4    a)     Group 0 - six-byte commands (see table 21)4    b)     Group 1 - ten-byte commands (see table 22)4    c)     Group 2 - ten-byte commands (see table 22)    d)     Group 3 - reserved    e)     Group 4 - reserved7    f)     Group 5 - twelve-byte commands (see table 23)u$    g)     Group 6 - vendor-specific #    h)     Group 7 - vendor-specifica  3                           Table 24 - Operation code O +=====-========-========-========-========-========-========-========-========+dO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |aO |=====+==========================+============================================|TO |     |         Group code       |                Command code                |bO +=============================================================================+e   7.2.2 Logical unit numberd  H The logical unit number is defined in the IDENTIFY message (6.6.7).  TheH target shall ignore the logical unit number specified within the commandH descriptor block if an IDENTIFY message was received.  It is recommendedF that the logical unit number in the command descriptor block be set to zero.  e  O    NOTICE:  The logical unit number field is included in the command descriptorrG    block for compatibility with some SCSI-1 devices.  This field may bebM    reclaimed in SCSI-3.  New implementations should use the outbound IDENTIFYrG    message, which is mandatory in SCSI-2, to establish the I_T_L nexus.i   7.2.3 Logical block addressa  J The logical block address on logical units or within a partition on deviceD volumes shall begin with block zero and be contiguous up to the last< logical block on that logical unit or within that partition.  C A six-byte command descriptor block contains a 21-bit logical block D address.  The ten-byte and the twelve-byte command descriptor blocksC contain 32-bit logical block addresses.  Logical block addresses in-K additional parameter data have their length specified for each occurrence. o& See the specific command descriptions.   7.2.4 Transfer length   I The transfer length field specifies the amount of data to be transferred, G usually the number of blocks.  For several commands the transfer length D indicates the requested number of bytes to be sent as defined in theI command description.  For these commands the transfer length field may beeG identified by a different name.  See the following descriptions and thee8 individual command descriptions for further information.  I Commands that use one byte for the transfer length allow up to 256 blocks-G of data to be transferred by one command.  A transfer length value of 1 I to 255 indicates the number of blocks that shall be transferred.  A value  of zero indicates 256 blocks.e  G In commands that use multiple bytes for the transfer length, a transfer I length of zero indicates that no data transfer shall take place.  A valuep> of one or greater indicates the number of blocks that shall be transferred.  B Refer to the specific command description for further information.   7.2.5 Parameter list length   E The parameter list length is used to specify the number of bytes sent=C during the DATA OUT phase.  This field is typically used in commandrE descriptor blocks for parameters that are sent to a target (e.g. modecF parameters, diagnostic parameters, log parameters, etc.).  A parameterA length of zero indicates that no data shall be transferred.  Thise. condition shall not be considered as an error.   7.2.6 Allocation lengthc  I The allocation length field specifies the maximum number of bytes that antH initiator has allocated for returned data.  An allocation length of zeroI indicates that no data shall be transferred.  This condition shall not bemJ considered as an error.  The target shall terminate the DATA IN phase whenH allocation length bytes have been transferred or when all available dataJ have been transferred to the initiator, whichever is less.  The allocationI length is used to limit the maximum amount of data (e.g. sense data, mode|@ data, log data, diagnostic data, etc.) returned to an initiator.   7.2.7 Control field=  J The control field is the last byte of every command descriptor block.  The% control field is defined in table 25.   3                            Table 25 - Control field-O +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |=====+=================+===================================+========+========|bO |     | Vendor-specific |         Reserved                  |  Flag  |  Link  | O +=============================================================================+     C The flag bit specifies which message the target shall return to the-J initiator if the link bit is one and the command completes without error. + Implementation of the flag bit is optional.   H The flag bit should be set to zero if the link bit is zero.  If link bitH is zero and the flag bit is one, the target shall return CHECK CONDITION7 status.  The sense key shall be set to ILLEGAL REQUEST.-  C If the flag bit is zero and the link bit is one, and if the command I completes successfully, the target shall send the LINKED COMMAND COMPLETE=D message.  If the flag bit is one and the link bit is one, and if theH command completes successfully, the target shall send the LINKED COMMAND COMPLETE (WITH FLAG) message.=  P    NOTE 46 The flag bit is typically used to cause an interrupt in the initiator    between linked commands.   K The link bit is used to continue the I/O process across multiple commands.  - Implementation of the link bit is optional.  =I A link bit of one indicates that the initiator requests a continuation of G the I/O process and that the target should enter the command phase upon-. successful completion of the current command.   F If the link bit is one, and if the command completes successfully, theI target shall return INTERMEDIATE or INTERMEDIATE-CONDITION MET status and-@ shall then send one of the two messages defined by the flag bit.  G If either of the link and flag bits are set to one, and the target does G not implement linked commands, it shall return CHECK CONDITION status.  . The sense key shall be set to ILLEGAL REQUEST.  
 7.3 Status  H The status byte and status byte code are defined in tables 26 and 27.  AE status byte shall be sent from the target to the initiator during the D STATUS phase at the completion of each command unless the command is, terminated by one of the following events:      a)     an ABORT message;     b)     an ABORT TAG message;-%    c)     a BUS DEVICE RESET message;-     d)     a CLEAR QUEUE message;!    e)     a hard reset condition; /    f)     an unexpected disconnect (see 6.1.1).-  J The STATUS phase normally occurs at the end of a command but in some cases= may occur prior to transferring the command descriptor block.e  2                             Table 26 - Status byteO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |-O |=====+=================+============================================+========| O |     |     Reserved    |               Status byte code             |Reserved|=O +=============================================================================+n    4                          Table 27 - Status byte codeC +==================================-==============================+ C |    Bits of status byte           |  Status                      | C |----------------------------------|                              | C |   7 | 6 | 5 | 4 | 3 | 2 | 1 | 0  |                              |=C |-----+---+---+---+---+---+---+----+------------------------------| C |   R | R | 0 | 0 | 0 | 0 | 0 | R  |  GOOD                        |-C |   R | R | 0 | 0 | 0 | 0 | 1 | R  |  CHECK CONDITION             | C |   R | R | 0 | 0 | 0 | 1 | 0 | R  |  CONDITION MET               ||C |   R | R | 0 | 0 | 1 | 0 | 0 | R  |  BUSY                        |-C |   R | R | 0 | 1 | 0 | 0 | 0 | R  |  INTERMEDIATE                | C |   R | R | 0 | 1 | 0 | 1 | 0 | R  |  INTERMEDIATE-CONDITION MET  | C |   R | R | 0 | 1 | 1 | 0 | 0 | R  |  RESERVATION CONFLICT        | C |   R | R | 1 | 0 | 0 | 0 | 1 | R  |  COMMAND TERMINATED          | C |   R | R | 1 | 0 | 1 | 0 | 0 | R  |  QUEUE FULL                  ||C |----------------------------------|                              | C |           All other codes        |  Reserved                    | C |-----------------------------------------------------------------| C |  Key: R = Reserved bit                                          |-C +=================================================================+   5 A definition of the status byte codes is given below.-  C 7.3.1 GOOD:  This status indicates that the target has successfully- completed the command.  J 7.3.2 CHECK CONDITION:  This status indicates that a contingent allegiance! condition has occurred (see 7.6).e  B 7.3.3 CONDITION MET:  This status or INTERMEDIATE-CONDITION MET isF returned whenever the requested operation is satisfied (see the SEARCH DATA and PREFETCH commands).    H 7.3.4 BUSY:  This status indicates that the target is busy.  This statusI shall be returned whenever a target is unable to accept a command from an-D otherwise acceptable initiator (i.e. no reservation conflicts).  TheH recommended initiator recovery action is to issue the command again at a later time.-  G 7.3.5 INTERMEDIATE:  This status or INTERMEDIATE-CONDITION MET shall benG returned for every successfully completed command in a series of linked=I commands (except the last command), unless the command is terminated witheH CHECK CONDITION, RESERVATION CONFLICT, or COMMAND TERMINATED status.  IfF INTERMEDIATE or INTERMEDIATE-CONDITION MET status is not returned, theE series of linked commands is terminated and the I/O process is ended.n  H 7.3.6 INTERMEDIATE-CONDITION MET:  This status is the combination of the( CONDITION MET and INTERMEDIATE statuses.  F 7.3.7 RESERVATION CONFLICT:  This status shall be returned whenever anI initiator attempts to access a logical unit or an extent within a logicalyJ unit that is reserved with a conflicting reservation type for another SCSID device (see the RESERVE and RESERVE UNIT commands).  The recommendedH initiator recovery action is to issue the command again at a later time.  E 7.3.8 COMMAND TERMINATED:  This status shall be returned whenever the I target terminates the current I/O process after receiving a TERMINATE I/OO@ PROCESS message (see 6.6.22).  This status also indicates that a7 contingent allegiance condition has occurred (see 7.6).   H 7.3.9 QUEUE FULL:  This status shall be implemented if tagged queuing isF implemented.  This status is returned when a SIMPLE QUEUE TAG, ORDEREDI QUEUE TAG, or HEAD OF QUEUE TAG message is received and the command queue== is full.  The I/O process is not placed in the command queue.=   7.4 Command examples  G The following subclauses give examples of typical command processing ins the SCSI environment.g   7.4.1 Single command example  J An I/O process containing one untagged READ command is used in this clauseJ to illustrate a simple I/O process on the SCSI bus.  This example does not& include error or exception conditions.  D The initiator has one set of active pointers that includes a commandJ pointer, a data pointer, and a status pointer.  In addition, the initiatorE has one set of saved pointers for each I/O process that it is able touG concurrently manage.  The initiator sets up the saved pointers to pointtJ to the appropriate bytes for the I/O process and copies the saved pointersF to the active pointers.  It then arbitrates for the SCSI bus, and uponJ winning arbitration, selects the target.  Once the target is selected, the* target assumes control of the I/O process.  J During the SELECTION phase, the initiator asserts the ATN signal to informJ the target that the initiator wishes to send a message.  The target entersA the MESSAGE OUT phase and transfers the IDENTIFY message from thetG initiator.  This message informs the target of which logical unit is tofH be used.  At this point, an I_T_L nexus has been established for the I/OE process.  This nexus associates the initiator's pointers with the I/Ob process.  B The target switches to the COMMAND phase and transfers the commandJ descriptor block from the initiator.  In this case, the command descriptorE block contains a READ command.  The target interprets the command andnE switches to the DATA IN phase, transfers the data, switches to STATUSsG phase, sends GOOD status, switches to MESSAGE IN phase, and transfers atJ COMMAND COMPLETE message.  After successfully sending the COMMAND COMPLETEJ message, the target goes to the BUS FREE phase by releasing the BSY signal and the I/O process ends.    7.4.2 Disconnect example  D In the above single command example, the length of time necessary toA obtain the data may require a time-consuming physical positioningaA operation.  In order to improve system throughput, the target may J disconnect from the initiator, thereby freeing the SCSI bus to allow other I/O process to occur.  o  G After the target has received the READ command (and has determined thatsE there will be a delay), it disconnects from the SCSI bus by sending ad6 DISCONNECT message and by going to the BUS FREE phase.  H After the target retrieves the requested data from the peripheral deviceG it arbitrates for the SCSI bus.  Upon winning arbitration, it reselects D the initiator and sends an IDENTIFY message to the initiator via theI MESSAGE IN phase.  This revives the I_T_L nexus so that the initiator canpH retrieve the correct set of pointers for the I/O process.  The initiatorI restores the active pointers to their most recent saved values (which, inbF this case, are the initial values) and the target continues (as in the2 single command example) to finish the I/O process.  H If target wishes to disconnect after transferring part of the data (e.g.H while crossing a cylinder boundary), it may do so by sending a SAVE DATAB POINTER message and a DISCONNECT message to the initiator and thenH disconnecting.  When reconnection is completed, the current data pointerC is restored to its value immediately prior to the SAVE DATA POINTERo message.  F On those occasions when an error or exception condition occurs and theG target elects to repeat the information transfer, the target may repeat=? the transfer by either issuing a RESTORE POINTERS message or by|@ disconnecting without issuing a SAVE DATA POINTER message.  WhenC reconnection is completed, the most recent saved pointer values are+	 restored.    7.4.3 Linked command example  C An I/O process may contain multiple commands linked together.  Upon=B completing a linked command successfully, the target automaticallyI proceeds to the next linked command for the I/O process.  All commands in H a series of linked commands are addressed to the same nexus and are part of a single I/O process.  C The commands are not entirely independent.  When using the relativeoH address bit (see 9.1.11), the address of the last logical block accessedF by one of the commands is available to the next command.  Thus one canI search for a particular data pattern using a SEARCH DATA command and thenoF read the logical block containing the data pattern with a READ commandH linked to the SEARCH DATA command.  One can also read a logical block atD a specified displacement from the block containing the data pattern.  H A LINKED COMMAND COMPLETE or LINKED COMMAND COMPLETE (WITH FLAG) messageJ is sent from the target to the initiator to indicate that a linked commandG completed.  The initiator then updates the saved pointers for the nexus G so that subsequent transfers from the target reference the next commandaC of the series.  Command processing of linked and single commands isnH similar except that relative addressing is permitted in linked commands.  J For example, a successful completion of a SEARCH DATA EQUAL command causesH the target to continue with the linked READ command from the initiator. H If the relative address bit in the READ command has been set to one, andJ the address field of the READ command is set to zero, the target transfers2 the successfully searched block to the initiator.   3 7.5 Command processing considerations and exception  conditions t  F The following subclauses describe some exception conditions and errorsB associated with command processing and the sequencing of commands.  ' 7.5.1 Programmable operating definitionT  I Some applications require that the operating definition of a logical unitbH be modified to meet the special requirements of a particular initiator. B The program-controlled modification of the operating definition isE typically provided to allow operating systems to change the operating C definition of a more recently developed targets to one that is morelE compatible with the operating system.  This ability requires that thet@ system comply with the low-level hardware definitions of SCSI-2.  H The parameters that can be changed by modifying the operating definitionI of a logical unit include the vendor identification, the device type, the4J device model, the SCSI compliance level, the SCSI specification level, theE command set, and other parameters.  The low-level hardware parameters C including signal timing and parity definitions cannot be changed by=H modifying the operating definition.  The present operating definition ofI a logical unit with respect to an initiator can be determined at any time=J by execution of an INQUIRY command.  In some vendor-specific cases, it mayI also be necessary to perform other commands including MODE SENSE and READ-	 CAPACITY.   H Each logical unit begins with a particular operating definition.  If theJ logical unit supports the CHANGE DEFINITION command, the present operatingH definition can be changed to any other operating definition supported byF the logical unit.  The actual details of the operating definition of aI logical unit are vendor-specific.  If the operating definition is changed|F to one that does not include the CHANGE DEFINITION command, the target8 should continue to accept the CHANGE DEFINITION command.  G If an error occurs during execution of a CHANGE DEFINITION command, theTD original operating definition remains in effect after the command is@ executed. The new operating definition becomes active only after8 successful execution of the CHANGE DEFINITION command.    A Since new operating definitions may preclude the execution of I/O J processes that are already in progress, the target may disconnect to allow@ completion of any I/O processes that are in progress.  OperatingJ definition changes that may cause conflicts with the normal operation fromG other initiators shall be indicated to those initiators by generating a=H unit attention condition for each other initiator.  The additional sense2 code shall be set to CHANGED OPERATING DEFINITION.  E An initiator may request a list of the operating definitions that theuH target supports and descriptive text for each operating definition using the INQUIRY command.  $ 7.5.2 Incorrect initiator connection  > An incorrect initiator connection occurs on a reconnection if:C    a)     an initiator attempts to reconnect to an I/O process, and 7    b)     a soft reset condition has not occurred, and hL    c)     the initiator does not send an ABORT, ABORT TAG, BUS DEVICE RESET,G           CLEAR QUEUE, or TERMINATE I/O PROCESS message during the samen4           MESSAGE OUT phase as the IDENTIFY message.  F An incorrect initiator connection also occurs on an initial connection when an initiator:L    a)     attempts to establish an I_T_L_Q nexus when an I_T_L nexus already/           exists from a previous connection, oreL    b)     attempts to establish an I_T_L nexus when an I_T_L_Q nexus alreadyE           exists, unless there is a contingent allegiance or extendedaH           contingent allegiance condition present for the logical unit.   G A target that detects an incorrect initiator connection shall abort all I I/O processes for the initiator on the logical unit or target routine andEC shall return CHECK CONDITION status.  The sense key shall be set toaH ABORTED COMMAND and the additional sense code shall be set to OVERLAPPED COMMANDS ATTEMPTED.h  G If an initiator reconnects to an I/O process and a soft reset conditionn@ has occurred, the target shall meet the requirements of 6.2.2.2.      NOTESL    47 An incorrect initiator connection may be indicative of a serious errorN    and, if not detected, could result in an I/O process operating with a wrongM    set of pointers.  This is considered a catastrophic failure on the part of N    the initiator.  Therefore, vendor-specific error recovery procedures may beJ    required to guarantee the data integrity on the medium.  The target mayM    return additional sense data to aid in this error recovery procedure (e.g.oM    sequential-access devices may return the residue of blocks remaining to be/@    written or read at the time the second command was received).O    48 Some targets may not detect an incorrect initiator connection until after 2    the command descriptor block has been received.  * 7.5.3 Selection of an invalid logical unit  I The target's response to selection of a logical unit that is not valid is & described in the following paragraphs.  * The logical unit may not be valid because:I    a)     the target does not support the logical unit (e.g. some targets I           support only one peripheral device).  In response to an INQUIRYsD           command, the target shall return the INQUIRY data with theH           peripheral qualifier set to the value required in 8.2.5.1.  InN           response to any other command except REQUEST SENSE, the target shallL           terminate the command with CHECK CONDITION status.  In response toK           a REQUEST SENSE command, the target shall return sense data.  The L           sense key shall be set to ILLEGAL REQUEST and the additional sense:           code shall be set to LOGICAL UNIT NOT SUPPORTED.L    b)     the target supports the logical unit, but the peripheral device isJ           not currently attached to the target.  In response to an INQUIRYD           command, the target shall return the INQUIRY data with theH           peripheral qualifier set to the value required in 8.2.5.1.  InN           response to any other command except REQUEST SENSE, the target shallL           terminate the command with CHECK CONDITION status.  In response toK           a REQUEST SENSE command, the target shall return sense data.  ThehL           sense key shall be set to ILLEGAL REQUEST and the additional sense:           code shall be set to LOGICAL UNIT NOT SUPPORTED.K    c)     the target supports the logical unit and the peripheral device is L           attached, but not operational.  In response to an INQUIRY command,F           the target shall return the INQUIRY data with the peripheralG           qualifier set to the value required in 8.2.5.1.  The target'soI           response to any command other than INQUIRY and REQUEST SENSE ist           vendor-specific.N    d)     the target supports the logical unit but is incapable of determiningL           if the peripheral device is attached or is not operational when itK           is not ready.  In response to an INQUIRY command,the target shall J           return the INQUIRY data with the peripheral qualifier set to theM           value required in 8.2.5.1.  In response to a REQUEST SENSE command,mL           the target shall return the REQUEST SENSE data with a sense key ofG           NO SENSE unless a contingent allegiance exists.  The target'si;           response to any other command is vendor-specific.u   7.5.4 Parameter rounding  I Certain parameters sent to a target with various commands contain a rangeeJ of values.  Targets may choose to implement only selected values from thisE range.  When the target receives a value that it does not support, itiG either rejects the command (CHECK CONDITION status with ILLEGAL REQUESTiE sense key) or it rounds the value received to a supported value.  ThelJ target shall reject unsupported values unless rounding is permitted in the description of the parameter.a  C Rounding of parameter values, when permitted, shall be performed asnH follows -  A target that receives a parameter value that is not an exactH supported value shall adjust the value to one that it supports and shallG return CHECK CONDITION status with a sense key of RECOVERED ERROR.  ThehG additional sense code shall be set to ROUNDED PARAMETER.  The initiatoreF is responsible to issue an appropriate command to learn what value the target has selected.  O    NOTE 49 Generally, the target should adjust maximum-value fields down to thecP    next lower supported value than the one specified by the initiator.  Minimum-P    value fields should be rounded up to the next higher supported value than theN    one specified by the initiator.  In some cases, the type of rounding (up orE    down) is explicitly specified in the description of the parameter.l  & 7.5.5 Asynchronous event notification   D Implementation of asynchronous event notification is optional.  ThisE protocol can be used to inform processor devices that an asynchronousiG event has occurred.  A SEND command with an AEN bit of one is issued toaI a processor device with a subsequent data phase that includes the REQUESTnH SENSE information.  SCSI devices that respond to an INQUIRY command as aI processor device type with asynchronous event notification capability may G be notified of asynchronous events using this protocol.  An SCSI deviceN? has to be capable of acting as an initiator in order to perform   asynchronous event notification.  L    NOTE 50 Asynchronous event notification cannot be used with a device thatM    acts as a temporary initiator (e.g. devices executing COPY commands) sincem1    they are not identified as a processor device.a  C Parameters affecting the use of asynchronous event notification arei1 contained in the control mode page (see 8.3.3.1).u  5 The four uses of asynchronous event notification are:aG    a)     informing a processor of an error condition encountered aftere           command completion;AL    b)     informing all processor devices that a newly initialized device is           available;M    c)     informing all processor devices of other unit attention conditions;rG    d)     informing all processor devices of other asynchronous events.c  F An example of the first case above is a device that implements a writeJ cache.  If the target is unable to write cached data to the medium, it mayE use an asynchronous event notification to inform the initiator of theoA failure.  An extended contingent allegiance condition may also beoG established during the same I_T_L nexus used for the asynchronous evente notification (see 6.6.9).a  F An example of the third case above is a device that supports removableJ media.  Asynchronous event notification may be used to inform an initiatorE of a not-ready-to-ready transition (medium changed) or of an operator G initiated event (e.g. activating a write protect switch or activating a  start or stop switch).  A An example of the fourth case above is a sequential-access devicee? performing a REWIND command with the immediate bit set to one. aG Asynchronous event notification may be used to inform an initiator thatmG the beginning of medium has been reached.  Completion of a CD-ROM AUDIOaE PLAY command started in the immediate mode is another example of thisi case.e  I Notification of an asynchronous event is performed using the SEND command G with the AEN bit set to one.  The information identifying the conditionoF being reported shall be returned during the DATA OUT phase of the SENDF command.  See 12.2.2 for further information on the format of the data sent.t  I An error condition or unit attention condition shall be reported once perED occurrence of the event causing it.  The target may choose to use anH asynchronous event notification or to return CHECK CONDITION status on aH subsequent command, but not both.  Notification of command-related errorE conditions shall be sent only to the processor that initiated the I/Oc process.  B The asynchronous event notification protocol can be used to notifyD processor devices that a system resource has become available.  If aG target chooses to use this method, the sense key in the sense data sente8 to the processor device shall be set to UNIT ATTENTION.   G The asynchronous event notification protocol shall be sent only to SCSIND devices that return processor device type with an AENC bit of one inH response to an INQUIRY command.  The INQUIRY command should be issued toD logical unit zero of each SCSI device responding to selection.  ThisB procedure shall be conducted prior to the first asynchronous event? notification and shall be repeated whenever the device deems itoC appropriate or when an event occurs that may invalidate the currenteI information.  (See 6.6.21, SYNCHRONOUS DATA TRANSFER REQUEST message, forD examples of these events.)  G Each SCSI device that returns processor device type with an AENC bit ofnH one shall be issued a TEST UNIT READY command to determine that the SCSIG device is ready to receive an asynchronous event notification.  An SCSIeK device returning CHECK CONDITION status is issued a REQUEST SENSE command. eF This clears any pending unit attention condition.  An SCSI device thatF returns processor device type with an AENC bit of one and returns GOODH status when issued a TEST UNIT READY command shall accept a SEND command with an AEN bit of one.   J    NOTE 51 An SCSI device which can use asynchronous event notification atP    initialization time should provide means to defeat these notifications.  ThisJ    can be done with a switch or jumper wire.  Devices that implement savedH    parameters may alternatively save the asynchronous event notificationM    permissions either on a per SCSI device basis or as a system-wide option. nP    In any case, a device conducts a survey with INQUIRY commands to be sure thatM    the devices on the SCSI bus are appropriate destinations for SEND commands N    with an AEN bit of one.  (The devices on the bus or the SCSI ID assignments    may have changed.)u   7.5.6 Unexpected reselection  H An unexpected reselection occurs if an SCSI device attempts to reconnectJ to an I/O process for which a nexus does not exist.  An SCSI device shouldA respond to an unexpected reselection by sending an ABORT message.a  # 7.6 Contingent allegiance condition.  G The contingent allegiance condition shall exist following the return of H CHECK CONDITION or COMMAND TERMINATED status.  The contingent allegianceJ condition shall be preserved for the I_T_x nexus until it is cleared.  TheG contingent allegiance condition shall be cleared upon the generation ofiB a hard reset condition, or by an ABORT message, a BUS DEVICE RESETB message, or any subsequent command for the I_T_x nexus.  While theJ contingent allegiance condition exists the target shall preserve the sense data for the initiator.e  I While the contingent allegiance condition exists, if the target is unableoF to maintain separate sense data, the target shall respond to any otherF requests for access to the logical unit or target routine from anotherH initiator with a BUSY status.  Execution of all tagged I/O processes forJ the I_T_L nexus for which the contingent allegiance condition exists shallB be suspended until the contingent allegiance condition is cleared.  , 7.7 Extended contingent allegiance condition  B Implementation of extended contingent allegiance is optional.  TheJ extended contingent allegiance condition extends the contingent allegianceH condition for an I_T_x nexus.  This condition is generated by the targetE sending an INITIATE RECOVERY message to the initiator following CHECK H CONDITION or COMMAND TERMINATED status and prior to the COMMAND COMPLETEH message.  This condition shall be preserved until it is cleared by a BUSA DEVICE RESET message, a RELEASE RECOVERY message, or a hard reset 
 condition.  E While the extended contingent allegiance condition exists, the target F shall respond to any other request for access to the logical unit fromG another initiator with BUSY status.  Execution of all I/O processes for G the logical unit for which the extended contingent allegiance conditionlH exists shall be suspended until the RELEASE RECOVERY message is received by the target.      NOTESP    52 It is not required to generate an extended contingent allegiance conditionN    for every CHECK CONDITION or COMMAND TERMINATED status that occurs.  SimpleK    errors not requiring an extended recovery may be dealt with by using theh"    contingent allegiance protocol.L    53 During the existence of the extended contingent allegiance condition, K    appropriate error recovery sequences may be executed.  Such commands candM    correct data, modify or delete queued commands, perform LOG SENSE commandssH    and obtain diagnostic information.  Extended contingent allegiance isO    recommended for error conditions that may require execution of multiple-step G    error-recovery protocols without interference from other initiators.R  G An extended contingent allegiance condition may also be generated using I an asynchronous event notification protocol.  When the event is detected,aE the bus device that detected the event assumes the initiator role andaB transmits a SEND command with an AEN bit of one to the appropriate device(s) (see 12.2.2).i  B If the device wishes to generate an extended contingent allegianceE condition during an asynchronous event notification, it shall send ansG INITIATE RECOVERY message following the IDENTIFY message (and followingEK any queue tag message) and prior to the COMMAND phase of the SEND command.  I An extended contingent allegiance condition can be generated for only oneiG I_T_L nexus at a time.  The extended contingent allegiance condition isvF cleared when a RELEASE RECOVERY message is received from the device toG which the INITIATE RECOVERY message was sent.  The generation of a hardiE reset condition, or receipt of a BUS DEVICE RESET message, shall also 3 clear the extended contingent allegiance condition.r  J During an extended contingent allegiance, only untagged I/O processes fromH the SCSI device to which the INITIATE RECOVERY message was sent shall beF executed by the target for the logical unit.  If the initiator sends aJ queue tag message, the target shall respond with QUEUE FULL status.  AfterE the extended contingent allegiance condition is cleared, any commandsa1 remaining in the command queue shall be executed.i    Queued I/O processese  H The implementation of queuing for I/O processes is optional.  Queuing of? I/O processes allows a target to accept multiple I/O processes.   I There are two methods for implementation of queuing, tagged and untagged.cI Tagged queuing allows a target to accept multiple I/O processes from eachiE initiator for each logical unit.  Untagged queuing allows a target toeJ accept one I/O process from each initiator for each logical unit or targetI routine.  Untagged queuing may be supported by SCSI-1 or SCSI-2 devices. f  Tagged queuing is new in SCSI-2.  H A target may support both tagged and untagged queuing.  An initiator mayE not mix the use of tagged and untagged queuing for I/O processes to atJ logical unit, except during a contingent allegiance or extended contingentI allegiance condition when only untagged initial connections are allowed. cH An initiator that elects to use tagged queuing does not preclude another; initiator on the same SCSI bus from using untagged queuing.v   7.8.1 Untagged queuing  J Untagged queuing allows a target to accept a command from an initiator forJ a logical unit or target routine while I/O processes from other initiatorsC are being executed.  Only one command for each I_T_x nexus shall bei accepted at a time.  a  H An I/O process may be initiated any time the BUS FREE phase exists, even@ if an I/O process from a different initiator is  active.  If theJ disconnect privilege is not granted in the IDENTIFY message of the currentH I/O process, the target may either suspend all other I/O processes or it2 may return BUSY status to the current I/O process.  J The I_T_x nexus sufficiently specifies the relationship so that the targetI can reconnect to the initiator to restore the pointers for I/O process aszB long as only one I/O process per I_T_x nexus is issued.  It is theH responsibility of the initiator to assure that only one such I/O process" is issued at any time (see 7.5.2).   7.8.2 Tagged queuing  H Tagged queuing allows a target to accept multiple I/O processes from theF same or different initiators until the logical unit's command queue isG full.  If an I/O process is received and the command queue is full, then@ target shall terminate the I/O process with QUEUE FULL status.    J The command queue is setup by the target for each supported logical unit. H Initiators may add or delete I/O processes to the queue.  When adding anJ I/O process, the initiator may specify fixed order of execution, allow theH target to define the order of execution, or specify that the I/O process is to be executed next.n  H If the disconnect privilege is not granted in the IDENTIFY message for a8 tagged I/O process, the target shall return BUSY status.  F The queue tag messages (see 6.6.17) allow the initiator to establish aE unique I_T_L_Q nexus to identify each I/O process.  The I_T_L_Q nexusiH allows the target to reconnect to a specific I/O process, and allows theB initiator to restore the set of pointers for that I/O process.  AnI initiator may have several I/O processes ongoing to the same or differentm1 logical units as long as each has a unique nexus.   F If only SIMPLE QUEUE TAG messages are used, the target may execute theH commands in any order that is deemed desirable within the constraints ofF the queue management algorithm specified in the control mode page (see	 8.3.3.1).a  D If ORDERED QUEUE TAG messages are used, the target shall execute theF commands in the order received with respect to other commands receivedE with ORDERED QUEUE TAG messages.  All commands received with a SIMPLE G QUEUE TAG message prior to a command received with an ORDERED QUEUE TAGtG message, regardless of initiator, shall be executed before that commandoH with the ORDERED QUEUE TAG message.  All commands received with a SIMPLED QUEUE TAG message after a command received with an ORDERED QUEUE TAGF message, regardless of initiator, shall be executed after that command$ with the ORDERED QUEUE TAG message.   J A command received with a HEAD OF QUEUE TAG message is placed first in theH queue, to be executed next.  A command received with a HEAD OF QUEUE TAGG message shall be executed prior to any queued I/O process.  ConsecutiveiI commands received with HEAD OF QUEUE TAG messages are executed in a last-  in-first-out order.i  H An I/O process received without a queue tag message, while there are anyG tagged I/O commands in the command queue from the same initiator, is anvH incorrect initiator connection (see 7.5.2), unless there is a contingent7 allegiance or extended contingent allegiance condition.h  C A series of linked commands constitute a single I/O process.  ThesenK commands are assigned the queue tag established in the initial connection. eG A command received with a HEAD OF QUEUE TAG message shall not suspend aeC series of linked commands for which the target has begun execution.e  I The RESERVE and RELEASE commands should be sent with an ORDERED QUEUE TAGuH message.  Use of the HEAD OF QUEUE TAG message with these commands could@ result in reservation conflicts with previously issued commands.  H    NOTE 54 Initiators should not issue another I/O processes following aJ    reservation request until that request is honoured by the target.  ThisA    prevents possible sequencing errors or file system corruption.   C There are two methods of dealing with the command queue following avE contingent allegiance condition.  The method used is specified in theaB control mode page by the queue error management bit (see 8.3.3.1).  G The first method allows the execution of tagged I/O processes to resumedJ when the contingent allegiance or extended contingent allegiance conditionI is cleared.  The target returns BUSY status to other initiators while the J contingent allegiance or extended contingent allegiance condition exists. B During this time, all tagged I/O processes are suspended.  All I/OH processes used for recovery operations shall be untagged.  The queue mayG be modified by removing all or selected I/O processes from the queue ast part of the recovery procedure.t  I If commands are combined by the queuing algorithm such that the exceptionTE condition affects more than one command, then a contingent allegiance 7 condition shall be generated for all affected commands.d  I The second method aborts all I/O processes when the contingent allegianceoI or extended contingent allegiance condition is cleared.  A unit attentionsH condition shall be generated for all other initiators and the additionalA sense code shall be set to COMMANDS CLEARED BY ANOTHER INITIATOR.a  J A device that does not support tagged I/O processes (e.g. not implemented,D disabled by the Dque bit in the control mode page, or switched to anI operating definition that does not include tagged I/O processes) it shall D respond to any queue tag message with a MESSAGE REJECT message.  TheC target shall continue the I/O process as if it were an untagged I/Ol process.  > Tagged queuing may also be temporarily disabled during certainD initialization periods or to control internal resource utilization. F During these periods the target may return QUEUE FULL status or it may? respond to any queue tag message with a MESSAGE REJECT message.l  H Several messages may be used to clear part or all of the command queue. G Please refer to the ABORT, ABORT TAG, BUS DEVICE RESET, and CLEAR QUEUEH! messages in clause 6 for details.E  # 7.8.3 Example of queued I/O processE  D This example of queuing I/O processes illustrates the execution of aG number of commands.  After each command, the state of the queue kept in F the target is shown to indicate the function actually performed by the queuing.  , 7.8.3.1 Typical sequences for tagged queuing  D An I/O process using tagged queuing uses the following sequences forG normal execution.  The initiator first arbitrates for the SCSI bus, andtG after successfully obtaining the SCSI bus, selects the appropriate SCSI J device.  The ATN signal is asserted during the SELECTION phase to indicateJ that a MESSAGE OUT phase is requested by the initiator.  The first messageH byte transferred is an IDENTIFY message.  The ATN signal continues to beH asserted during the MESSAGE OUT phase to indicate that the initiator hasG another message.  The second message byte transferred is the first bytedE of the appropriate queue tag message, in this case a SIMPLE QUEUE TAGuG message.  The third and last message byte is transmitted containing thel> second byte of the queue tag message, the queue tag.  As it isG transferred, the ATN signal is negated to indicate that no more messagedF bytes are available.  The target then transfers the command descriptorI block.  Assuming the command requires disconnection, the target transmitseJ a DISCONNECT message to the initiator and then enters the BUS FREE phase. F The target places the command, identified by the I_T_L_Q nexus, at the' appropriate place in the command queue.m  E When the target removes I/O processes from the queue for execution, anG physical latency period may occur.  At the end of this period, when the I target is prepared to transfer the appropriate data, the target begins ansG ARBITRATION phase and, upon winning, enters a RESELECTION phase.  AfternH a successful reselection, the target sends the IDENTIFY message followedI by a SIMPLE QUEUE TAG message with the queue tag value originally sent bycD the initiator.  The initiator uses the I_T_L_Q nexus to identify theJ correct set of pointers and control blocks associated with the I/O processH and to establish the necessary conditions for data transfer.  The targetH begins data transfer.  When the data transfer is successfully completed,D the target returns GOOD status and terminates the I/O process with a COMMAND COMPLETE message.   ! 7.8.3.2 Example of tagged queuingn  H An example of the execution of five queued I/O processes is described toF demonstrate how tagged queuing operates.  All tagged I/O processes areI from one initiator to a single logical unit of a single target.  The fivepE I/O processes are defined in table 28.  The target is a direct-accesscF device.  At the time the I/O processes are first being executed, it isH assumed that the actuator is in position to access logical block 10 000.  >                Table 28 - Commands in order received by targetO +===========-=============-=============-============-=============-==========+aO |  Command  |  Queue tag  |  Queue tag  |  Logical   |   Transfer  |  Status  |mO |           |   message   |    value    |   block    |    length   |          |iO |           |             |             |  address   |             |          |aO |-----------+-------------+-------------+------------+-------------+----------| O |   READ    |    SIMPLE   |     01h     |   10 000   |    1 000    |  Queued  |aO |   READ    |    SIMPLE   |     02h     |      100   |        1    |  Queued  |eO |   READ    |   ORDERED   |     03h     |    1 000   |    1 000    |  Queued  | O |   READ    |    SIMPLE   |     04h     |   10 000   |        1    |  Queued  |nO |   READ    |    SIMPLE   |     05h     |    2 000   |    1 000    |  Queued  |eO +=============================================================================+n  G The optimum order would require that those blocks close to the actuator I position be the first blocks accessed, followed by those increasingly far G from the actuator position.  However, the command with queue tag 03h isxD an ordered I/O process, so that all simple I/O processes transferredB previously must be executed before, while all simple I/O processesD transferred after the ordered I/O process must be executed after the ordered I/O process.  J If a target supports an optimizing algorithm the actual order in which the9 I/O processes are executed could be as shown in table 29.   ;                   Table 29 - Commands in order of executiontO +===========-=============-=============-============-=============-==========+sO |  Command  |  Queue tag  |  Queue tag  |  Logical   |   Transfer  |  Status  | O |           |   message   |    value    |   block    |    length   |          | O |           |             |             |  address   |             |          |wO |-----------+-------------+-------------+------------+-------------+----------|sO |   READ    |    SIMPLE   |     01h     |   10 000   |    1 000    |  Queued  |aO |   READ    |    SIMPLE   |     02h     |      100   |        1    |  Queued  |UO |   READ    |   ORDERED   |     03h     |    1 000   |    1 000    |  Queued  | O |   READ    |    SIMPLE   |     05h     |    2 000   |    1 000    |  Queued  |dO |   READ    |    SIMPLE   |     04h     |   10 000   |        1    |  Queued  |eO +=============================================================================+   I I/O processes with queue tag values 01h and 02h are executed in the orderII received since the actuator is already in position to execute I/O process D 01h.  I/O process 02h must be executed before I/O process 04h or 05hG because the ordered I/O process 03h was transmitted after I/O processesiJ 01h and 02h but before I/O processes 04h and 05h.  I/O process 03h is thenB executed after I/O process 02h.  The I/O processes 04h and 05h areH executed after the ordered I/O process 03h.  I/O process 05h is executedJ before I/O process 04h because the actuator is in position to access blockJ 2 000 after executing I/O process 03h.  I/O process 04h is executed last.   D As an example of the operation of the HEAD OF QUEUE TAG I/O process,J consider that a new I/O process, identified by a HEAD OF QUEUE TAG messageG with a queue tag of 08h, is transmitted to the target while the ordered A I/O process 03h is being executed.  The I/O process 03h continuesDE execution, but the new HEAD OF QUEUE TAG I/O process is placed in theeG queue for execution before all subsequent I/O processes.  In this case,gF the queue for execution after the ordered I/O process 03h was executed" would appear as shown in table 30.  ?                Table 30 - Modified by HEAD OF QUEUE TAG messagevO +===========-=============-=============-============-=============-==========+ O |  Command  |  Queue tag  |  Queue tag  |  Logical   |   Transfer  |  Status  |tO |           |   message   |    value    |   block    |    length   |          | O |           |             |             |  address   |             |          |aO |-----------+-------------+-------------+------------+-------------+----------|sO |   READ    |   ORDERED   |     03h     |    1 000   |    1 000    | Executing|iO |   READ    |HEAD OF QUEUE|     08h     |        0   |        8    |  Queued  |dO |   READ    |    SIMPLE   |     05h     |    2 000   |    1 000    |  Queued  |)O |   READ    |    SIMPLE   |     04h     |   10 000   |        1    |  Queued  |iO +=============================================================================+o  I To obtain maximum performance gains using tagged queuing requires careful E implementation of the queuing algorithms in the target.  In addition, F initiators should allow a maximum number of simple I/O processes to beE executed with a minimum number of ordered I/O processes.  RESERVE andAG RELEASE commands, SET LIMITS commands, and appropriate software lockinguG conventions should be used to guarantee the proper relationship between E the commands executed and the data stored on the peripheral devices.  3 These conventions are not defined by this standard.    7.9  Unit attention condition   G The target shall generate a unit attention condition for each initiatorhF on each valid logical unit whenever the target has been reset by a BUSJ DEVICE RESET message, a hard reset condition, or by a power-on reset.  TheE target shall also generate a unit attention condition on the affectedhG logical unit(s) for each initiator whenever one of the following eventsi occurs:x3    a)     A removable medium may have been changed;TL    b)     The mode parameters in effect for this initiator have been changed            by another initiator; =    c)     The version or level of microcode has been changed;eK    d)     Tagged commands queued for this initiator were cleared by another            initiator;(    e)     INQUIRY data has been changed;L    f)     The mode parameters in effect for the initiator have been restored#           from non-volatile memory;o>    g)     A change in the condition of a synchronized spindle;N    h)     Any other event occurs that requires the attention of the initiator.      NOTESN    56 Targets may queue unit attention conditions on logical units.  After theN    first unit attention condition is cleared, another unit attention conditionF    may exist (e.g. a power on condition followed by a microcode change    condition).K    57 See 7.5.3 for requirements concerning selection of an invalid logicalt    unit.  G The unit attention condition shall persist on the logical unit for each G initiator until that initiator clears the condition as described in thei following paragraphs.s  J If an INQUIRY command is received from an initiator to a logical unit withC a pending unit attention condition (before the target generates theeF contingent allegiance condition), the target shall perform the INQUIRYI command and shall not clear the unit attention condition.  If the INQUIRYiA command is received after the target has generated the contingentoJ allegiance condition for a pending unit attention condition, then the unitH attention condition on the logical unit shall be cleared, and the target" shall perform the INQUIRY command.  C If any other command is received after the target has generated thesG contingent allegiance condition for a pending unit attention condition, I the unit attention condition on the logical unit shall be cleared, and ifoI no other unit attention condition is pending the target shall perform the J command.  If another unit attention condition is pending, the target shallH not perform the command and shall generate another contingent allegiance
 condition.  G If a REQUEST SENSE command is received from an initiator with a pendingtD unit attention condition (before the target generates the contingent4 allegiance condition), then the target shall either:G    a)     report any pending sense data and preserve the unit attentioni,           condition on the logical unit, or,L    b)     report the unit attention condition, may discard any pending senseN           data, and clear the unit attention condition on the logical unit for           that initiator.   G If the target has already generated the contingent allegiance conditionME for the unit attention condition, the target shall perform the secondd action listed above.  J If an initiator issues a command other than INQUIRY or REQUEST SENSE whileI a unit attention condition exists for that initiator (prior to generating.J the contingent allegiance condition for the unit attention condition), theE target shall not perform the command and shall report CHECK CONDITIONeG status unless a higher priority status as defined by the target is also , pending (e.g. BUSY or RESERVATION CONFLICT).  F If, after generating the contingent allegiance condition for a pendingG unit attention condition, the next command received from that initiator D on the logical unit is not REQUEST SENSE, then that command shall beD performed and the unit attention condition shall be cleared for thatC initiator on the logical unit and the sense data is lost (see 7.6).f  I If a target becomes a temporary initiator to issue a SEND command with anUJ AEN bit of one, which informs the initiator (temporary target) of the unitJ attention condition, and the SEND command completes with GOOD status, thenI the target shall clear the unit attention condition for that initiator one the logical unit (see 7.5.5).t   8  All device typese     8.1 Model for all device types  I This model describes some of the general characteristics expected of mostaF SCSI devices.  It is not intended to define any requirements nor is itJ intended to alter any requirements defined elsewhere in this InternationalE Standard.  Clause 7 also contains model information pertaining to allg
 device types.s   8.1.1 SCSI addresses  H There are two levels of addresses within the SCSI architecture: the SCSID device address and the logical unit number or target routine number.   8.1.1.1 SCSI device addresst  C SCSI devices occupy (i.e. respond to) one address on the SCSI bus. eG Generally, the SCSI device provides a means (e.g. switches, jumpers) toeH select one of the eight available addresses (0 through 7).  This addressC is used during bus arbitration and selection or reselection of SCSILC devices.  Each device on the SCSI bus is assigned a unique address.v  J Normally, the SCSI device address is set when the system is configured andG it remains static thereafter.  Some systems and devices provide vendor--4 specific means to alter this address at other times.   8.1.1.2 Logical unitsS  F Each target has one or more logical units, beginning with logical unitJ zero.  There is a maximum of eight logical units.  These logical units areH usually mapped directly to peripheral devices, but they may be a portionC of a peripheral device or may comprise multiple peripheral devices.   H An initiator can determine whether a target implements a logical unit byJ issuing an INQUIRY command and examining the returned peripheral qualifier and peripheral device type.   H The concept of a logical unit is not defined for an initiator.  (An SCSIJ device may implement both the initiator role and the target role.  In this; case logical unit(s) are defined only for the target role.)g   8.1.1.3 Target routineso  H An optional feature of the SCSI architecture permits each target to haveH one or more target routines, beginning with target routine number zero. G There is a maximum of eight target routines.  These target routines areeI processes that execute directly on the target and are not associated withsD a particular logical unit or peripheral device.  Target routines areC addressed using the LUNTAR bit of the IDENTIFY message (see 6.6.7).=  H Target routines are principally intended to return information about theA target and the only valid commands are INQUIRY and REQUEST SENSE.   . 8.1.2 Commands implemented by all SCSI devices  G This standard defines four commands that all SCSI-2 targets implement -sD INQUIRY, REQUEST SENSE, SEND DIAGNOSTIC, and TEST UNIT READY.  TheseI commands are used to configure the system, to test targets, and to return A important information concerning errors and exception conditions.S  ! 8.1.2.1 Using the INQUIRY command   J The INQUIRY command may be used by a system to determine the configurationG of the SCSI bus.  Target devices respond with information that includes J their type and standard level and may include the vendor's identification,G model number and other useful information.  It is recommended that SCSI=H targets be capable of returning this information (or whatever part of itD that is available) upon completing power-on initialization.  An SCSIC device may take longer to get certain portions of this information,/; especially if it retrieves the information from the medium.   ' 8.1.2.2 Using the REQUEST SENSE commandn  H Whenever a contingent allegiance condition (see 7.6) is established, theI initiator that received the error should issue a REQUEST SENSE command toeG receive the sense data describing what caused the contingent allegianceoI condition.  If the initiator issues some other command, the sense data isi lost.   ) 8.1.2.3 Using the SEND DIAGNOSTIC commands  E The SEND DIAGNOSTIC command provides a means to request the target toiE perform a self test.  While the test is target specific, the means ofsJ requesting the test is standardized and the response is simply GOOD status; if all is well or CHECK CONDITION status if the test fails.s  F The SEND DIAGNOSTIC command also provides other powerful features whenI used in conjunction with the RECEIVE DIAGNOSTIC RESULTS command, but thisa capability is optional.e  ) 8.1.2.4 Using the TEST UNIT READY commandf  G The TEST UNIT READY command is useful in that it allows an initiator toeH poll a logical unit until it is ready without the need to allocate spaceH for returned data.  It is especially useful to check cartridge status ofD logical units with removable media.  Targets are expected to respondD promptly to indicate the current status of the device (i.e. a targetF should avoid lengthy disconnections in an attempt to respond with GOOD status).  |! 8.2 Commands for all device types-  J The operation codes for commands that apply to all device types are listed in table 31.  ;                    Table 31 - Commands for all device types H +=====================================-============-======-============+H |  Command name                       | Operation  | Type |  Subclause |H |                                     |   code     |      |            |H |-------------------------------------+------------+------+------------|H |  CHANGE DEFINITION                  |    40h     |   O  |   8.2.1    |H |  COMPARE                            |    39h     |   O  |   8.2.2    |H |  COPY                               |    18h     |   O  |   8.2.3    |H |  COPY AND VERIFY                    |    3Ah     |   O  |   8.2.4    |H |  INQUIRY                            |    12h     |   M  |   8.2.5    |H |  LOG SELECT                         |    4Ch     |   O  |   8.2.6    |H |  LOG SENSE                          |    4Dh     |   O  |   8.2.7    |H |  MODE SELECT(6)                     |    15h     |   Z  |   8.2.8    |H |  MODE SELECT(10)                    |    55h     |   Z  |   8.2.9    |H |  MODE SENSE(6)                      |    1Ah     |   Z  |   8.2.10   |H |  MODE SENSE(10)                     |    5Ah     |   Z  |   8.2.11   |H |  READ BUFFER                        |    3Ch     |   O  |   8.2.12   |H |  RECEIVE DIAGNOSTIC RESULTS         |    1Ch     |   O  |   8.2.13   |H |  REQUEST SENSE                      |    03h     |   M  |   8.2.14   |H |  SEND DIAGNOSTIC                    |    1Dh     |   M  |   8.2.15   |H |  TEST UNIT READY                    |    00h     |   M  |   8.2.16   |H |  WRITE BUFFER                       |    3Bh     |   O  |   8.2.17   |H |----------------------------------------------------------------------|H |Key:  M = Command implementation is mandatory.                        |H |      O = Command implementation is optional.                         |H |      Z = Command implementation is device type specific.             |H +======================================================================+     8.2.1 CHANGE DEFINITION commanda  C The CHANGE DEFINITION command (see table 32) modifies the operating J definition of the selected logical unit or target with respect to commands4 from the selecting initiator or for all initiators.   9                      Table 32 - CHANGE DEFINITION commanduO +=====-========-========-========-========-========-========-========-========+iO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |iO |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================|nO | 0   |                           Operation code (40h)                        |oO |-----+-----------------------------------------------------------------------|nO | 1   | Logical unit number      |              Reserved                      |sO |-----+-----------------------------------------------------------------------|dO | 2   |                  Reserved                                    |  Save  |nO |-----+-----------------------------------------------------------------------|vO | 3   |Reserved|                  Definition parameter                        |dO |-----+-----------------------------------------------------------------------|sO | 4   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------| O | 5   |                           Reserved                                    |iO |-----+-----------------------------------------------------------------------| O | 6   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|gO | 7   |                           Reserved                                    |uO |-----+-----------------------------------------------------------------------|sO | 8   |                           Parameter data length                       |fO |-----+-----------------------------------------------------------------------|eO | 9   |                           Control                                     |oO +=============================================================================+a  NJ A save control bit (Save) of zero indicates that the target shall not saveF the operating definition.  A Save bit of one indicates that the target< shall save the operating definition to non-volatile memory.   6 The definition parameter field is defined in table 33.  9                     Table 33 - Definition parameter fielde3 +============-====================================+e3 |   Value    |  Meaning of definition parameter   |a3 |------------+------------------------------------|r3 |    00h     |  Use current operating definition  |n3 |    01h     |  SCSI-1 operating definition       |e3 |    02h     |  CCS operating definition          |o3 |    03h     |  SCSI-2 operating definition       |a3 |  04 - 3Fh  |  Reserved                          |r3 |  40 - 7Fh  |  Vendor-specific                   |i3 +=================================================+e  P    NOTE 57 The current operating definition parameter values establish operatingK    definitions compatible with the appropriate SCSI specification.  Vendor-rJ    specific values are available for those applications where more complexO    operation definition changes are required. Definitions supported by a deviceeK    are returned in the implemented operating definition page (see 8.3.4.3).s  D The parameter data length field specifies the length in bytes of theK parameter data that shall be transferred from the initiator to the target. g? A parameter data length of zero indicates that no data shall be B transferred.  This condition shall not be considered as an error. H Parameter data lengths greater than zero indicate the number of bytes of) parameter data that shall be transferred.i  & The parameter data is vendor-specific.  N    NOTE 58 The parameter data may be used to specify a password to validate an    operating definition change.d  D The CHANGE DEFINITION command causes one of the operating definition modifications listed below:SK    a)     Change the operating definition of a logical unit relative to the I           initiator that issued the command.  In this case, the target is H           capable of maintaining an unique operating definition for each@           logical unit relative to each initiator in the system.G    b)     Change the operating definition of the target relative to the I           initiator that issued the command.  In this case, the target iscH           capable of maintaining a unique operating definition, for eachK           initiator in the system, that applies to all logical units of thec           target.rD    c)     The operating definition of a logical unit relative to allK           initiators in the system.  In this case, the target is capable ofhJ           maintaining an unique operating definition for each logical unit3           relative to all initiators in the system.tK    d)     The operating definition of the target relative to all initiatorslL           in the system.  In this case, the target is capable of maintaining(           only one operating definition.      NOTESN    59 This International Standard does not provide a direct means to determineJ    which of the above four methods has been implemented by the target.  AnO    indirect means of determining which method is implemented exists in that thegK    target is required to inform affected initiators of operating definitionT.    changes via the unit attention condition.  O    60 The final two mondifications listed above may result in incompatibilitiesa;    if other initiators are operated below the SCSI-2 level.   G The operating definition is modified after successful completion of therI command.  A target shall consider the command successfully completed whenDC it detects the assertion of the ACK signal for the COMMAND COMPLETEuE message.  The initiator should verify the new operating definition byoJ issuing an INQUIRY command requesting the implemented operating definition page (see 8.3.4.1).   I It is permissible for an SCSI-2 device that has its definition changed to.7 an SCSI-1 device to accept a CHANGE DEFINITION command.   L    NOTE 61 The method of changing the operating definition is implementationP    dependent.  Some implementations may require that the target's operating modeG    be reinitialized as if a power-up or hard-reset had occurred.  OtheriP    implementations may modify only those operating definitions that are affected$    by the CHANGE DEFINITION command.  E If the CHANGE DEFINITION command is not executed successfully for any.G reason, the operating definition shall remain the same as it was beforeeD the CHANGE DEFINITION command was attempted.  If it is impossible toG return to the previous operating definition, a unit attention conditions! shall be generated by the target.a  G    NOTE 62 The present operating definition of the target may always besK    interrogated through the INQUIRY command.  When an SCSI-2 target has itsDO    operating definition changed to CCS or SCSI-1, certain changes are needed to.M    promote compatibility with preexisting SCSI-1 initiators.  The recommendedd    changes are as follows:L    a)     The target should not initiate selections to other SCSI devices toQ           determine if any initiators support AEN.  The target should assume thatiA           none are capable of receiving AEN and not issue an AEN.aR    b)     The target should not generate extended contingent allegiance conditions2           by issuing an INITIATE RECOVERY message.S    c)     If a REQUEST SENSE command with an allocation length of zero is received,e<           the target should return four bytes of sense data.J    d)     If an INQUIRY command is received, the returned data should haveR           appropriate values in the ANSI version and response data format fields. 5           The features supported bits should be zero.wT    e)     A change in the operating definition may change the vendor identifier, theS           device type, the device model, the SCSI implementation level, the command C           set, mode pages, and any other operating characteristics.=  J After a power-on condition or a hard RESET condition, the target shall setF its initial operating definition to the last saved value, if saving is@ implemented, or its default value, if saving is not implemented.   8.2.2 COMPARE command-  J The COMPARE command (see table 34) provides the means to compare data fromJ one logical unit with another or the same logical unit in a manner similar to the COPY command.  4                           Table 34 - COMPARE commandO +=====-========-========-========-========-========-========-========-========+.O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    ||O |Byte |        |        |        |        |        |        |        |        |GO |=====+=======================================================================|TO | 0   |                           Operation code (39h)                        | O |-----+-----------------------------------------------------------------------| O | 1   | Logical unit number      |              Reserved             |  Pad   | O |-----+-----------------------------------------------------------------------|hO | 2   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------| O | 3   | (MSB)                                                                 | O |-----+---                                                                 ---|WO | 4   |                           Parameter list length                       |-O |-----+---                                                                 ---|iO | 5   |                                                                 (LSB) |tO |-----+-----------------------------------------------------------------------|sO | 6   |                           Reserved                                    |=O |-----+-----------------------------------------------------------------------|DO | 7   |                           Reserved                                    |tO |-----+-----------------------------------------------------------------------|oO | 8   |                           Reserved                                    |nO |-----+-----------------------------------------------------------------------|=O | 9   |                           Control                                     | O +=============================================================================+     J This command functions in the same manner as the COPY command, except thatJ the data from the source is compared on a byte-by-byte basis with the dataJ from the destination.  The parameter list transferred to the target is the? same as for the COPY command.  This parameter list contains the H information to identify the logical units involved in the comparison andJ the length of the comparison.  (See 8.2.3 for additional information about the COPY command.)  G If the comparison is unsuccessful, the command shall be terminated with-I CHECK CONDITION status and the sense key shall be set to MISCOMPARE.  TheiI remaining fields in the sense data shall be set as documented in the COPY- command.   8.2.3 COPY command  F The COPY command (see table 35) provides a means to copy data from oneH logical unit to another or the same logical unit.  The logical unit thatG receives and performs the COPY command is called the copy manager.  The H copy manager is responsible for copying data from a logical unit (sourceH device) to a logical unit (destination device).  These logical units mayE reside on different SCSI devices or the same SCSI device (in fact all-F three may be the same logical unit).  Some SCSI devices that implementJ this command may not support copies to or from another SCSI device, or mayH not support third party copies (i.e. both the source and the destination, logical units reside on other SCSI devices).  2                            Table 35 - COPY commandO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |=O |Byte |        |        |        |        |        |        |        |        |cO |=====+=======================================================================| O | 0   |                           Operation code (18h)                        |gO |-----+-----------------------------------------------------------------------| O | 1   | Logical unit number      |              Reserved             |  Pad   |=O |-----+-----------------------------------------------------------------------|tO | 2   | (MSB)                                                                 |hO |-----+---                                                                 ---|fO | 3   |                           Parameter list length                       | O |-----+---                                                                 ---| O | 4   |                                                                 (LSB) |=O |-----+-----------------------------------------------------------------------|nO | 5   |                           Control                                     |pO +=============================================================================+e    G The pad bit (8.2.3.7) is used in conjunction with the cat bit (8.2.3.7)dG in the segment descriptors to define what action should be taken when aoB segment of the copy does not fit exactly into an integer number of destination blocks.   D The parameter list length field specifies the length in bytes of theH parameters that shall be sent during the DATA OUT phase of the command. ? A parameter list length of zero indicates that no data shall beo@ transferred. This condition shall not be considered as an error.  J The COPY parameter list (see table 36) begins with a four-byte header thatJ contains the COPY function code and priority.  Following the header is one or more segment descriptors.  6                         Table 36 - COPY parameter listO +=====-========-========-========-========-========-========-========-========+tO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |tO |Byte |        |        |        |        |        |        |        |        | O |=====+============================================+==========================| O | 0   |         COPY function code                 |         Priority         |oO |-----+-----------------------------------------------------------------------|eO | 1   |                           Vendor-specific                             |uO |-----+-----------------------------------------------------------------------|lO | 2   |                           Reserved                                    |iO |-----+-----------------------------------------------------------------------| O | 3   |                           Reserved                                    |eO |=====+=======================================================================|mO |     |                         Segment descriptor(s)                         | O |=====+=======================================================================| O | 0   |                           Segment descriptor 0                        |rO |- - -+---                                                                 ---|sO | n   |                     (See specific table for length.)                  |mO |-----+-----------------------------------------------------------------------|dO |     |                                 .                                     |.O |     |                                 .                                     |eO |-----+-----------------------------------------------------------------------| O | 0   |                           Segment descriptor x                        |aO |- - -+---                                                                 ---| O | n   |                     (See specific table for length.)                  |hO +=============================================================================+n    F The COPY function code field defines a specific format for the segmentH descriptors.  The COPY function codes are defined in table 37.  A target8 need not support all function codes for its device type.  6                         Table 37 - COPY function codesN +===============================================-========-==========-========+N |       Peripheral device type                  |  COPY  | Segment  |        |N |-----------------------------------------------|function|descriptor|        |N | Source                | Destination           |  code  |  table   |Comments|N |-----------------------+-----------------------+--------+----------+--------|N | Block devices         | Stream devices        |    0   |    38    |        |N | (Device types 0,4,5,7)| (Device types 1,2,3,9)|        |          |        |N | Stream devices        | Block devices         |    1   |    38    |(Note 3)|N | (Device types 1,3,9)  | (Device types 0,4,5,7)|        |          |        |N | Block devices         | Block devices         |    2   |    39    |(Note 3)|N | (Device types 0,4,5,7)| (Device types 0,4,5,7)|        |          |        |N | Stream devices        | Stream devices        |    3   |    40    |        |N | (Device types 1,3,9)  | (Device types 1,2,3,9)|        |          |        |N | Sequential-access     | Sequential-access     |    4   |    41    | Image  |N | (Device type 1)       | (Device type 1)       |        |          |  copy  |N |----------------------------------------------------------------------------|N |  NOTES                                                                     |N |   1 COPY function codes 05h - 0Fh are reserved.                            |N |   2 COPY function codes 10h - 1Fh are vendor-specific.                     |N |   3 When using the COMPARE command the destination block device may be a   |N |      CD-ROM device or an optical-memory device that uses read-only media.  |N |   4 See 8.2.5.1 for peripheral device type definitions.                    |N +============================================================================+    F The priority field of the COPY parameter list establishes the relativeJ priority of this COPY command to other commands being executed by the sameA target.  All other commands are assumed to have a priority of 1. vE Priority 0 is the highest priority, with increasing values indicating. lower priorities.o  I The segment descriptor formats are determined by the COPY function code. tJ The segment descriptor format used for block devices (i.e. write-once, CD-G ROM, optical-memory, and direct-access devices) shall be the same.  TheA@ segment descriptor format used for stream devices (i.e. printer,9 processor, communications, and sequential-access devices) H  shall be the same.  Thus a copy operation from a write-once device to aJ printer device uses the same segment descriptor format as a copy operationJ from a direct-access device to a sequential-access device (see table 37). I The segment descriptor formats are described in 8.2.3.3 through 8.2.3.6. -@ A maximum of 256 segment descriptors are permitted.  The segmentD descriptors are identified by ascending numbers beginning with zero.  3 8.2.3.1 Errors detected by the managing SCSI device-  H Two classes of exception conditions may occur during execution of a COPYI command.  The first class consists of those exception conditions detected-E by the SCSI device that received the COPY command and is managing theBG execution of the command.  These conditions include parity errors while-H transferring the COPY command and status byte, invalid parameters in theD COPY command, invalid segment descriptors, and inability of the SCSIJ device controlling the COPY functions to continue operating.  In the eventH of such an exception condition, the SCSI device managing the COPY shall:A    a)     terminate the COPY command with CHECK CONDITION status.-I    b)     set the valid bit in the sense data to one.  The segment number L           shall contain the number of the segment descriptor being processedI           at the time the exception condition is detected.  The sense key M           shall contain the sense key code describing the exception condition-K           (i.e. not COPY ABORTED).  The information field shall contain the F           difference between the number of blocks field in the segmentN           descriptor being processed at the time of the failure and the numberG           of blocks successfully copied.  This number is the residue of B           unprocessed blocks remaining for the segment descriptor.  # 8.2.3.2 Errors detected by a targett  G The second class of errors consists of exception conditions detected by C the SCSI device transferring data at the request of the SCSI devicesI managing the transfer.  The SCSI device managing the COPY command detects H exception conditions by receiving CHECK CONDITION status from one of theB SCSI devices it is managing.  It then shall recover the sense data( associated with the exception condition.  C The SCSI device managing the COPY command may also be the source orsJ destination SCSI device (or both).  It shall distinguish between a failureF of the management of the COPY and a failure of the data transfer beingF requested. It shall then create the appropriate sense data internally.  G After recovering the sense data associated with the detected error, them, SCSI device managing the COPY command shall:A    a)     terminate the COPY command with CHECK CONDITION status.mK    b)     The valid bit in the sense data shall be set to one.  The segmentnI           number shall contain the number of the segment descriptor beingdI           processed at the time the exception condition is detected.  TheaN           sense key shall be set to COPY ABORTED.  The information field shallJ           contain the difference between the number of blocks field in theK           segment descriptor being processed at the time of the failure anddG           the number of blocks successfully copied.  This number is the M           residue of unprocessed blocks remaining for the segment descriptor.=  J The first byte of the command-specific information field shall specify theJ starting byte number, relative to the first byte of sense data, of an areaI that contains (unchanged) the source logical unit's status byte and sense=H data.  A zero value indicates that no status byte or sense data is being% returned for the source logical unit.8  G The second byte of the command-specific information field shall specify-I the starting byte number, relative to the first byte of sense data, of an I area that contains (unchanged) the destination logical unit's status byte-I and sense data.  A zero value indicates that no status byte or sense data 3 is being returned for the destination logical unit.   & 8.2.3.3 COPY function code 00h and 01h  G The format for the segment descriptors for COPY transfers between blockaI and stream devices is specified in table 38.  This format is required for G COPY function codes 00h or 01h.  The segment descriptor may be repeated I up to 256 times within the parameter list length specified in the command- descriptor block.-  G       Table 38 - Segment descriptor for COPY function codes 00h and 01h O +=====-========-========-========-========-========-========-========-========+=O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |uO |Byte |        |        |        |        |        |        |        |        |iO |=====+==========================+========+========+==========================|iO | 0   | Source address           |Reserved|  Cat   |     Source LUN           | O |-----+--------------------------+-----------------+--------------------------|TO | 1   | Destination address      |    Reserved     |     Destination LUN      |aO |-----+-----------------------------------------------------------------------| O | 2   | (MSB)                                                                 |iO |-----+---                        Stream device block length               ---|mO | 3   |                                                                 (LSB) |=O |-----+-----------------------------------------------------------------------|tO | 4   | (MSB)                                                                 | O |-----+---                        Block device number of blocks            ---|=O | 7   |                                                                 (LSB) | O |--- -+-----------------------------------------------------------------------|-O | 8   | (MSB)                                                                 | O |--- -+---                        Block device logical block address       ---|-O | 11  |                                                                 (LSB) | O +=============================================================================+-    D The source address and source LUN fields specify the SCSI bus ID andH logical unit of the device to copy the data from for this segment of theH COPY command. The destination address and destination LUN fields specifyH the SCSI bus ID and logical unit to copy the data to for this segment ofH the COPY command.  Some SCSI devices may not support third-party COPY inG which the copying SCSI device is not the source or destination device. nE Some SCSI devices only support COPY within the SCSI device and not to G other SCSI devices.  If an unsupported COPY operation is requested, the I command shall be terminated with CHECK CONDITION status and the sense key-H shall be set to ILLEGAL REQUEST with an additional sense code of INVALID& FIELD IN PARAMETER LIST (see 8.2.3.1).  F A catenate (Cat) bit (optional) of one indicates that the COPY managerG shall catenate the last source block of a segment with the first source-G block of the next segment if the last source block does not end exactly I at the end of the destination block.  The definition of a cat bit of zero J depends on the setting of the pad bit in the command descriptor block (see	 8.2.3.7).   J The stream device block-length field specifies the block length to be usedK on the stream device logical unit during this segment of the COPY command. nC If the SCSI device managing the COPY knows this block length is notrJ supported, the command shall be terminated with CHECK CONDITION status andF the sense key shall be set to ILLEGAL REQUEST with an additional senseI code of INVALID FIELD IN PARAMETER LIST.  If the block length is found to=J be invalid while executing a read or write operation to the stream device,I the command shall be terminated with CHECK CONDITION status and the sense-/ key shall be set to COPY ABORTED (see 8.2.3.2).r  I The block device number of blocks field specifies the number of blocks in-D the current segment to be copied.  A value of zero indicates that no, blocks shall be transferred in this segment.  C The block device logical block address field specifies the startingc; logical block address on the logical unit for this segment.c   8.2.3.4 COPY function code 02h  E The format for the segment descriptors for COPY transfers among block,C devices is specified in table 39.  This format is required for COPY J function code 02h.  The segment descriptor may be repeated up to 256 timesD within the parameter list length specified in the command descriptor block.  C            Table 39 - Segment descriptor for COPY function code 02h,O +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |-O |=====+==========================+========+========+==========================| O | 0   | Source address           |   DC   |  Cat   | Source LUN               |5O |-----+--------------------------+-----------------+--------------------------| O | 1   | Destination address      |   Reserved      | Destination LUN          |mO |-----+-----------------------------------------------------------------------|lO | 2   |                              Reserved                                 |vO |-----+-----------------------------------------------------------------------|=O | 3   |                              Reserved                                 |mO |-----+-----------------------------------------------------------------------|dO | 4   | (MSB)                                                                 |rO |- - -+---                Number of blocks                                 ---|tO | 7   |                                                                 (LSB) |CO |-----+-----------------------------------------------------------------------|wO | 8   | (MSB)                                                                 |.O |- - -+---                Source logical block address                     ---|oO | 11  |                                                                 (LSB) |oO |-----+-----------------------------------------------------------------------|dO | 12  | (MSB)                                                                 |-O |- - -+---                Destination logical block address                ---|.O | 15  |                                                                 (LSB) |eO +=============================================================================+     F See 8.2.3.3 for definitions of the source address, the source LUN, the9 destination address, the destination LUN, and CAT fields.n  H A destination count (DC) bit of zero indicates that the number of blocksH field refers to the source logical unit.  A DC bit of one indicates thatC the number of blocks field refers to the destination logical unit. n  ? The number of blocks field specifies the number of blocks to beeH transferred to or from (depending on the DC bit) the block device during@ this segment.  A value of zero indicates that no blocks shall be transferred.  E The source logical block address field specifies the starting logical * block address on the source block device.   J The destination logical block address field specifies the starting logical. block address on the destination block device.   8.2.3.5 COPY function code 03h  F The format for the segment descriptors for COPY transfers among streamC devices is specified by table 40.  This format is required for COPYhJ function code 03h.  The segment descriptor may be repeated up to 256 timesD within the parameter list length specified in the command descriptor block.  C            Table 40 - Segment descriptor for COPY function code 03h O +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |pO |Byte |        |        |        |        |        |        |        |        |tO |=====+==========================+========+========+==========================|rO | 0   | Source address           |   DC   |  Cat   | Source LUN               |CO |-----+--------------------------+-----------------+--------------------------|oO | 1   | Destination address      |   Reserved      | Destination LUN          | O |-----+-----------------------------------------------------------------------|mO | 2   |                              Reserved                                 |iO |-----+-----------------------------------------------------------------------| O | 3   |                              Reserved                                 |aO |-----+-----------------------------------------------------------------------| O | 4   | (MSB)                                                                 |dO |-----+---                        Source block length                      ---|eO | 5   |                                                                 (LSB) |eO |-----+-----------------------------------------------------------------------|dO | 6   | (MSB)                                                                 |nO |-----+---                        Destination block length                 ---| O | 7   |                                                                 (LSB) |nO |-----+-----------------------------------------------------------------------| O | 8   | (MSB)                                                                 | O |- - -+---                        Number of blocks                         ---|bO | 11  |                                                                 (LSB) |uO +=============================================================================+n    F See 8.2.3.3 for definitions of the source address, the source LUN, the9 destination address, the destination LUN, and CAT fields.n  H A destination count (DC) bit of zero indicates that the number of blocksH field refers to the source logical unit.  A DC bit of one indicates thatC the number of blocks field refers to the destination logical unit. a  F The source block length field specifies the block-length of the sourceD device for this segment of the COPY.  A zero in this field indicatesG variable block-length.  For non-zero values, this field shall match thet$ logical unit's actual block-length.   J If block-length mismatches are detected prior to the beginning of the readD operation by the SCSI device managing the COPY, the command shall beF terminated with CHECK CONDITION status.  The sense key shall be set toE ILLEGAL REQUEST and the additional sense code shall be set to INVALID=' FIELD IN PARAMETER LIST (see 8.2.3.1). =  D If the mismatches are detected during the read operation by the COPYJ manager, the command shall be terminated with CHECK CONDITION status.  TheI sense key shall be set to COPY ABORTED (see 8.2.3.2).  and the additional+; sense code shall be set to INVALID FIELD IN PARAMETER LIST.e  H The destination block-length field specifies the block length to be usedJ on the destination logical unit during the COPY.  Destination block lengthD mismatches are handled in an analogous manner as source block length mismatches.-  ? The number of blocks field specifies the number of blocks to be-G transferred to or from (depending on the DC bit) the device during this H segment.  A value of zero indicates that no blocks shall be transferred.   8.2.3.6 COPY function code 04h  G The format for the segment descriptors for image COPY transfers between-C sequential-access devices is specified in table 41.  This format is-C required for COPY function code 04h.  The segment descriptor may be J repeated up to 256 times within the parameter list length specified in the command descriptor block.   C            Table 41 - Segment descriptor for COPY function code 04h O +=====-========-========-========-========-========-========-========-========+-O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        | O |=====+==========================+=================+==========================| O | 0   | Source address           |   Reserved      | Source LUN               |=O |-----+--------------------------+-----------------+--------------------------|dO | 1   | Destination address      |   Reserved      | Destination LUN          |cO |-----+-----------------------------------------------------------------------|IO | 2   |                              Count                                    |mO |-----+-----------------------------------------------------------------------| O | 3   |                                                                       |iO |- - -+---                           Reserved                              ---|rO | 7   |                                                                       | O |-----+-----------------------------------------------------------------------| O | 8   |                                                                       |nO |- - -+---                           Vendor-specific                       ---|oO | 11  |                                                                       |bO +=============================================================================+o    F See 8.2.3.3 for definitions of the source address, the source LUN, the9 destination address, the destination LUN, and CAT fields.-  F The image mode COPY command copies an exact image of the source deviceC medium to the destination device medium, beginning at their currente? positions. The copy function terminates when the source device:,I    a)     encounters an end-of-partition as defined by the source device; I    b)     encounters an end-of-data as defined by the source device (i.e.I!           BLANK CHECK sense key);bI    c)     has copied the number of consecutive filemarks specified in theiG           count field from the source device to the destination device;IN    d)     has copied the number of consecutive setmarks specified in the countM           field from the source device to the destination device, if the RSmk F           bit in the device configuration page (see 10.3.3.1) is one.   I A count field of zero indicates that the COPY command shall not terminateeG due to any number of consecutive filemarks or setmarks.  Other error ori@ exception conditions (e.g. early-warning end-of-partition on theD destination device) may cause the COPY command to terminate prior toI completion.  In such cases, it is not possible to calculate a residue, sod= the information field in the sense data shall be set to zero.   $ 4s Copies with unequal block lengths  G When copying data between two devices with unequal block lengths, it isiB possible for the last source block to not completely fill the lastD destination block for one or more segments in the COPY command.  TwoE optional bits are defined to assist in controlling the copy manager's E actions in this circumstance.  The Pad bit (in the command descriptor=J block) and the Cat bit (in each applicable segment descriptor) are defined in table 42.  9                     Table 42 - Pad and cat bit definition O +=====-=====-=================================================================+-O | Pad | Cat | COPY manager's action                                           | O |-----+-----+-----------------------------------------------------------------|-O |  0  |  0  | On inexact segments, it is device specific whether the COPY     | O |     |     | manager rejects the COPY command with CHECK CONDITION status and|-O |     |     | ILLEGAL REQUEST sense key, the COPY manager writes or accepts   | O |     |     | short blocks (variable-block mode on sequential-access devices),|-O |     |     | or the COPY manager adds pad characters (00h) to the destination| O |     |     | block or strips pad characters from the source block.           | O |     |     |                                                                 | O |  1  |  0  | On inexact segments, the COPY manager shall add pad characters  |-O |     |     | (00h) to the destination block to completely fill the block, or | O |     |     | it shall strip pad characters from the source block, always     | O |     |     | stopping at the end of a complete block.                        | O |     |     |                                                                 |-O |  X  |  1  | The COPY manager shall always write or read complete blocks.  On| O |     |     | inexact segments, the remainder of the block contains data from | O |     |     | the next segment.  This code is not valid in the last segment of| O |     |     | the COPY command.                                               |=O +=============================================================================+t    P    NOTE 63 Use of pad characters is intended to assist in managing COPY commandsN    between devices of different block lengths where partial-block residues mayG    occur.  The initiator who issued the COPY command is responsible fordH    management of these pad areas (i.e. remembering where they are).  OneI    possible method is to write the COPY parameter list information to thetN    destination medium prior to issuing the COPY command for backup and to readB    this information prior to issuing the COPY command for restore.   8.2.4 COPY AND VERIFY commando  H The COPY AND VERIFY command (see table 43) performs the same function asG the COPY command, except that a verification of the data written to theeE destination logical unit is performed after the data is written.  ThemD parameter list transferred to the target is the same as for the COPYE command. This parameter list contains the information to identify thenI logical units involved in the copy and the length of the copy.  See 8.2.3t2 for additional information about the COPY command.  8                       Table 43 - COPY AND VERIFY commandO +=====-========-========-========-========-========-========-========-========+-O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    ||O |Byte |        |        |        |        |        |        |        |        ||O |=====+=======================================================================|+O | 0   |                           Operation code (3Ah)                        ||O |-----+-----------------------------------------------------------------------|+O | 1   | Logical unit number      |        Reserved          | BytChk |  Pad   ||O |-----+-----------------------------------------------------------------------|-O | 2   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|-O | 3   | (MSB)                                                                 | O |-----+---                                                                 ---|-O | 4   |                           Parameter list length                       | O |-----+---                                                                 ---|tO | 5   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|-O | 6   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------| O | 7   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|-O | 8   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------| O | 9   |                           Control                                     | O +=============================================================================+=    D A byte check (BytChk) bit of zero causes a medium verification to beI performed with no data comparison.  A BytChk bit of one causes a byte-by-nF byte comparison of data written on the destination medium and the dataJ transferred from the source medium.  If the comparison is unsuccessful forI any reason, the copy manager shall return CHECK CONDITION status with thecJ sense key set to MISCOMPARE.  The remaining fields in the sense data shall) be set as documented in the COPY command.P   8.2.5 INQUIRY commandi  F The INQUIRY command (see table 44) requests that information regardingI parameters of the target and its attached peripheral device(s) be sent tosD the initiator.  An option allows the initiator to request additional; information about the target or logical unit (see 8.2.5.2).w  4                           Table 44 - INQUIRY commandO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |eO |Byte |        |        |        |        |        |        |        |        |DO |=====+=======================================================================|eO | 0   |                           Operation code (12h)                        | O |-----+-----------------------------------------------------------------------|iO | 1   | Logical unit number      |                  Reserved         |  EVPD  |nO |-----+-----------------------------------------------------------------------| O | 2   |                           Page code                                   |dO |-----+-----------------------------------------------------------------------|hO | 3   |                           Reserved                                    |tO |-----+-----------------------------------------------------------------------| O | 4   |                           Allocation length                           |dO |-----+-----------------------------------------------------------------------|eO | 5   |                           Control                                     |4O +=============================================================================+=    H An enable vital product data (EVPD) bit of one specifies that the targetG shall return the optional vital product data specified by the page code I field.  If the target does not support vital product data and this bit is=I set to one, the target shall return CHECK CONDITION status with the sense H key set to ILLEGAL REQUEST and an additional sense code of INVALID FIELD IN CDB.-  G An EVPD bit of zero specifies that the target shall return the standard J INQUIRY data.  If the page code field is not zero, the target shall returnG CHECK CONDITION status with the sense key set to ILLEGAL REQUEST and an-. additional sense code of INVALID FIELD IN CDB.  J The page code field specifies which page of vital product data information$ the target shall return (see 8.3.4).  E The INQUIRY command shall return CHECK CONDITION status only when the 1 target cannot return the requested INQUIRY data.    P    NOTE 64 The INQUIRY data should be returned even though the peripheral device'    may not be ready for other commands.   G If an INQUIRY command is received from an initiator with a pending unit-C attention condition (i.e. before the target reports CHECK CONDITION I status), the target shall perform the INQUIRY command and shall not clearc' the unit attention condition (see 7.9).       NOTESM    65 The INQUIRY command is typically used by the initiator after a reset or=N    power-up condition to determine the device types for system configuration. O    To minimize delays after a reset or power-up condition, the standard INQUIRYdN    data should be available without incurring any media access delays.  If theP    target does store some of the INQUIRY data on the device, it may return zerosM    or ASCII spaces (20h) in those fields until the data is available from the,
    device.K    66 The INQUIRY data may change as the target executes its initializationnL    sequence or in response to a CHANGE DEFINITION command.  For example, theN    target may contain a minimum command set in its non-volatile memory and mayO    load its final firmware from the device when it becomes ready.  After it has H    loaded the firmware, it may support more options and therefore return?    different supported options information in the INQUIRY data.t   8.2.5.1 Standard INQUIRY data   D The standard INQUIRY data (see table 45) contains 36 required bytes,F followed by a variable number of vendor-specific parameters.  Bytes 56C through 95, if returned, are reserved for future standardization.  r  :                    Table 45 - Standard INQUIRY data formatO +=====-========-========-========-========-========-========-========-========+oO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |oO |Byte |        |        |        |        |        |        |        |        |bO |=====+==========================+============================================| O | 0   | Peripheral qualifier     |           Peripheral device type           |nO |-----+-----------------------------------------------------------------------| O | 1   |  RMB   |                  Device-type modifier                        |eO |-----+-----------------------------------------------------------------------|cO | 2   |   ISO version   |       ECMA version       |  ANSI-approved version   |2O |-----+-----------------+-----------------------------------------------------|=O | 3   |  AENC  | TrmIOP |     Reserved    |         Response data format      | O |-----+-----------------------------------------------------------------------|-O | 4   |                           Additional length (n-4)                     |pO |-----+-----------------------------------------------------------------------|tO | 5   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|nO | 6   |                           Reserved                                    |tO |-----+-----------------------------------------------------------------------| O | 7   | RelAdr | WBus32 | WBus16 |  Sync  | Linked |Reserved| CmdQue | SftRe  | O |-----+-----------------------------------------------------------------------|eO | 8   | (MSB)                                                                 |oO |- - -+---                        Vendor identification                    ---|tO | 15  |                                                                 (LSB) |lO |-----+-----------------------------------------------------------------------| O | 16  | (MSB)                                                                 | O |- - -+---                        Product identification                   ---|tO | 31  |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------| O | 32  | (MSB)                                                                 |=O |- - -+---                        Product revision level                   ---|tO | 35  |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|mO | 36  |                                                                       |eO |- - -+---                        Vendor-specific                          ---|iO | 55  |                                                                       |dO |-----+-----------------------------------------------------------------------|.O | 56  |                                                                       |mO |- - -+---                        Reserved                                 ---|wO | 95  |                                                                       | O |=====+=======================================================================|nO |     |                       Vendor-specific parameters                      |nO |=====+=======================================================================|aO | 96  |                                                                       |cO |- - -+---                        Vendor-specific                          ---|=O | n   |                                                                       |0O +=============================================================================+     G The peripheral qualifier and peripheral device-type fields identify the=E device currently connected to the logical unit.  If the target is not H capable of supporting a device on this logical unit, this field shall beG set to 7Fh (peripheral qualifier set to 011b and peripheral device typeeE set to 1Fh).  The peripheral qualifier is defined in table 46 and the-. peripheral device type is defined in table 47.  6                        Table 46 - Peripheral qualifierO +=========-===================================================================+-O |Qualifier|  Description                                                      | O |---------+-------------------------------------------------------------------| O |   000b  |  The specified peripheral device type is currently connected to   | O |         |  this logical unit.  If the target cannot determine whether or    | O |         |  not a physical device is currently connected, it shall also use  | O |         |  this peripheral qualifier when returning the INQUIRY data.       |-O |         |  This peripheral qualifier does not mean that the device is ready | O |         |  for access by the initiator.                                     |-O |         |                                                                   | O |   001b  |  The target is capable of supporting the specified peripheral     |-O |         |  device type on this logical unit;  however, the physical device  | O |         |  is not currently connected to this logical unit.                 |-O |         |                                                                   | O |   010b  |  Reserved                                                         |=O |         |                                                                   |iO |   011b  |  The target is not capable of supporting a physical device on     |bO |         |  this logical unit. For this peripheral qualifier the peripheral  | O |         |  device type shall be set to 1Fh to provide compatibility with    |eO |         |  previous versions of SCSI.  All other peripheral device type     |eO |         |  values are reserved for this peripheral qualifier.               |tO |         |                                                                   |bO |   1XXb  |  Vendor-specific                                                  |cO +=============================================================================+t    7                       Table 47 - Peripheral device typeiO +=============-===============================================================+ O |    Code     |  Description                                                  | O |-------------+---------------------------------------------------------------| O |     00h     |  Direct-access device (e.g. magnetic disk)                    | O |     01h     |  Sequential-access device (e.g. magnetic tape)                | O |     02h     |  Printer device                                               | O |     03h     |  Processor device                                             | O |     04h     |  Write-once device (e.g. some optical disks)                  | O |     05h     |  CD-ROM device                                                | O |     06h     |  Scanner device                                               | O |     07h     |  Optical memory device (e.g. some optical disks)              | O |     08h     |  Medium changer device (e.g. jukeboxes)                       | O |     09h     |  Communications device                                        | O |  0Ah - 0Bh  |  Defined by ASC IT8 (Graphic arts pre-press devices)          | O |  0Ch - 1Eh  |  Reserved                                                     | O |     1Fh     |  Unknown or no device type                                    | O +=============================================================================+     E A removable medium (RMB) bit of zero indicates that the medium is nottD removable.  A RMB bit of one indicates that the medium is removable.  F The device-type modifier field was defined in SCSI-1 to permit vendor-H specific qualification codes of the device type.  This field is retainedF for compatibility with SCSI-1.  Targets that do not support this field should return a value of zero.  E The usage of non-zero code values in the ISO version and ECMA version H fields are defined by the International Organization for StandardizationJ and the European Computer Manufacturers Association, respectively.  A zeroH code value in these fields shall indicate that the target does not claimG compliance to the ISO version of SCSI (ISO 9316) or the ECMA version of8G SCSI (ECMA-111). It is possible to claim compliance to more than one ofe these SCSI standards.e  I The ANSI-approved version field indicates the implemented version of thise2 International Standard and is defined in table 48.  7                        Table 48 - ANSI-approved versionrO +=============-===============================================================+tO |    Code     |  Description                                                  | O |-------------+---------------------------------------------------------------|SO |      0h     |  The device might or might not comply to an ANSI-approved     | O |             |  standard.                                                    | O |      1h     |  The device complies to ANSI X3.131-1986 (SCSI-1).            | O |      2h     |  The device complies to this version of SCSI.  This code is   |tO |             |  reserved to designate this standard upon approval by ANSI.   |oO |   3h - 7h   |  Reserved                                                     |vO +=============================================================================+n    H The asynchronous event notification capability (AENC) bit indicates thatE the device supports the asynchronous event notification capability asy defined in 7.5.5. N    a)     Processor device-type definition:  An AENC bit of one indicates thatI           the processor device is capable of accepting asynchronous eventeI           notifications. An AENC bit of zero indicates that the processorIC           device does not support asynchronous event notifications.r8    b)     All other device-types:  This bit is reserved.  E A terminate I/O process (TrmIOP) bit of one indicates that the deviceuI supports the TERMINATE I/O PROCESS message as defined in 6.6.22.  A valuedD of zero indicates that the device does not support the TERMINATE I/O PROCESS message.  I A response data format value of zero indicates the INQUIRY data format is F as specified in SCSI-1.  A response data format value of one indicates@ compatibility with some products that were designed prior to theI development of this standard (i.e. CCS).  A response data format value of D two indicates that the data shall be in the format specified in thisI International Standard.  Response data format values greater than two are 	 reserved.   D The additional length field shall specify the length in bytes of theH parameters.  If the allocation length of the command descriptor block isH too small to transfer all of the parameters, the additional length shall* not be adjusted to reflect the truncation.  C A relative addressing (RelAdr) bit of one indicates that the device I supports the relative addressing mode for this logical unit.  If this bit-H is set to one, the linked command (Linked) bit shall also be set to one;J since relative addressing can only be used with linked commands.  A RelAdrI bit of zero indicates the device does not support relative addressing for  this logical unit.  H A wide bus 32 (Wbus32) bit of one indicates that the device supports 32-H bit wide data transfers.  A value of zero indicates that the device does' not support 32-bit wide data transfers.   H A wide bus 16 (Wbus16) bit of one indicates that the device supports 16-H bit wide data transfers.  A value of zero indicates that the device does' not support 16-bit wide data transfers.-  P    NOTE 67 If the values of both the Wbus16 and Wbus32 bits are zero, the device+    only supports 8-bit wide data transfers.   B A synchronous transfer (Sync) bit of one indicates that the deviceI supports synchronous data transfer.  A value of zero indicates the device + does not support synchronous data transfer.-  G A linked command (Linked) bit of one indicates that the device supports E linked commands for this logical unit.  A value of zero indicates the > device does not support linked commands for this logical unit.  H A command queuing (CmdQue) bit of one indicates that the device supportsH tagged command queuing for this logical unit.  A value of zero indicatesI the device does not support tagged command queuing for this logical unit.   J A soft reset (SftRe) bit of zero indicates that the device responds to theG RESET condition with the hard RESET alternative (see 6.2.2.1).  A SftRe I bit of one indicates that the device responds to the RESET condition with-) the soft RESET alternative (see 6.2.2.2).-  H ASCII data fields shall contain only graphic codes (i.e. code values 20hJ through 7Eh).  Left-aligned fields shall place any unused bytes at the endG of the field (highest offset) and the unused bytes shall be filled with J space characters (20h).  Right-aligned fields shall place any unused bytesG at the start of the field (lowest offset) and the unused bytes shall be # filled with space characters (20h).   B The vendor identification field contains eight bytes of ASCII dataF identifying the vendor of the product.  The data shall be left aligned within this field.    P    NOTE 68 It is intended that this field provide a unique vendor identificationF    of the manufacturer of the SCSI device.  In the absence of a formalK    registration procedure, X3T9.2 maintains a list of vendor identification=C    codes in use.  Vendors are requested to voluntarily submit their P    identification codes to X3T9.2 to prevent duplication of codes (see annex E).  H The product identification field contains sixteen bytes of ASCII data asI defined by the vendor.  The data shall be left-aligned within this field.=  E The product revision level field contains four bytes of ASCII data aslI defined by the vendor.  The data shall be left-aligned within this field.y   8.2.5.2 Vital product data  B Implementation of vital product data is optional.  The informationD returned consists of configuration data (e.g. vendor identification,G product identification, model, serial number), manufacturing data (e.g.iE plant and date of manufacture), field replaceable unit data and otherb" vendor- or device-specific data.    H The initiator requests the vital product data information by setting theI EVPD bit to one and specifying the page code of the desired vital product I data (see 8.3.4).  If the target does not implement the requested page it-E shall return CHECK CONDITION status.  The a sense key shall be set toiE ILLEGAL REQUEST and the additional sense code shall be set to INVALIDt
 FIELD IN CDB.t      NOTESL    69 The target should have the ability to execute the INQUIRY command evenO    when a device error occurs that prohibits normal command execution.  In suchrL    a case, CHECK CONDITION status should be returned for commands other thanK    INQUIRY or REQUEST SENSE.  The sense data returned may contain the fieldeL    replaceable unit code.  The vital product data should be obtained for the,    failing device using the INQUIRY command.F    70 This International Standard defines a format that allows device-O    independent initiator software to display the vital product data returned bypH    the INQUIRY command.  For example, the initiator may display the dataM    associated for the field replaceable unit returned in the sense data.  The O    contents of the data may be vendor-specific; therefore, it may not be usable 1    without detailed information about the device. K    71 This International Standard does not define the location or method oftI    storing the vital product data.  The retrieval of the data may require L    completion of initialization operations within the device that may induceG    delays before the data is available to the initiator.  Time-critical L    requirements are an implementation consideration and are not addressed in    this International Standard.v   8.2.6 LOG SELECT command  H The LOG SELECT command (see table 49) provides a means for the initiatorD to manage statistical information maintained by the device about theC device or its logical units.  Targets that implement the LOG SELECT=F command shall also implement the LOG SENSE command.  Structures in theJ form of log parameters within log pages are defined as a way to manage theF log data. The LOG SELECT command provides for sending zero or more logG pages during a DATA OUT phase.  This International Standard defines the-E format of the log pages, but does not define the exact conditions and  events that are logged.s  5                         Table 49 - LOG SELECT command O +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================| O | 0   |                           Operation code (4Ch)                        | O |-----+-----------------------------------------------------------------------| O | 1   | Logical unit number      |              Reserved    |  PCR   |   SP   | O |-----+-----------------------------------------------------------------------| O | 2   |        PC       |         Reserved                                    |hO |-----+-----------------------------------------------------------------------|hO | 3   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|=O | 4   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------| O | 5   |                           Reserved                                    |iO |-----+-----------------------------------------------------------------------| O | 6   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|nO | 7   | (MSB)                                                                 | O |-----+---                        Parameter list length                    ---|tO | 8   |                                                                 (LSB) |tO |-----+-----------------------------------------------------------------------|)O | 9   |                           Control                                     |mO +=============================================================================+a    F A parameter code reset (PCR) bit of one and a parameter list length ofD zero shall cause all implemented parameters to be set to the target-B defined default values (e.g. zero).  If the PCR bit is one and theJ parameter list length is greater than zero, the command is terminated withJ CHECK CONDITION status.  The sense key shall be set to ILLEGAL REQUEST andJ the additional sense code shall be set to INVALID FIELD IN CDB.  A PCR bit= of zero specifies that the log parameters shall not be reset.   E A save parameters (SP) bit of one indicates that after performing theeD specified LOG SELECT operation the target shall save to non-volatileI memory all parameters identified as savable by the DS bit in the log page E (see 8.3.2).  A SP bit of zero specifies that parameters shall not beI saved.  I Saving of log parameters is optional and indicated for each log parameter J by the DS bit in the page.  Log parameters may be saved at vendor-specificF times subject to the TSD bit (see 8.3.2) in the log parameter.  If theH target does not implement saved parameters for any log parameter and theJ SP bit is set to one, the command shall be terminated with CHECK CONDITIONJ status.  The sense key shall be set to ILLEGAL REQUEST, and the additional( sense code set to INVALID FIELD IN CDB.   J It is not an error to set the SP bit to one and to set the DS bit of a logA parameter to one.  In this case, the parameter value for that logb parameter is not saved.p  F The page control (PC) field defines the type of parameter values to be9 selected.  The page control field is defined in table 50.E  5                         Table 50 - Page control fieldaJ    +=======-==============================-==============================+J    | Type  |  LOG SELECT parameter values |  LOG SENSE parameter values  |J    |-------+------------------------------+------------------------------|J    |  00b  |  Current threshold values    |  Threshold values            |J    |  01b  |  Current cumulative values   |  Cumulative values           |J    |  10b  |  Default threshold values    |  Default threshold values    |J    |  11b  |  Default cumulative values   |  Default cumulative values   |J    +=====================================================================+    D The current cumulative values may be updated by the target or by theG initiator using the LOG SELECT command to reflect the cumulative numbersJ of events experienced by the target.  Fields in the parameter control byteD (8.3.2) of each log parameter control the updating and saving of the  current cumulative parameters.    D The target shall set the current threshold parameters to the defaultJ threshold values in response to a LOG SELECT command with the PC field set7 to 10b and the parameter list length field set to zero.i  I The target shall set all cumulative parameters to their default values innE response to a LOG SELECT command with the PC field set to 11b and the ) parameter list length field set to zero.    I The current threshold value can only be modified by the initiator via theiJ LOG SELECT command.  If the initiator attempts to change current thresholdH values that are not available or not implemented for that log parameter,A then the target shall terminate the LOG SELECT command with CHECK J CONDITION status, the sense key set to ILLEGAL REQUEST, and the additionalI sense code set to INVALID FIELD IN PARAMETER LIST.  The saving of currentoI threshold parameters and the criteria for the current threshold being mets> are controlled by bits in the parameter control byte (8.3.2).   N    NOTE 72 Pages or log parameters that are not available may become available?    at some later time (e.g. after the device has become ready).a  D The parameter list length field specifies the length in bytes of theI parameter list that shall be transferred from the initiator to the targettJ during the DATA OUT phase.  A parameter list length of zero indicates thatI no pages shall be transferred.  This condition shall not be considered antG error.  If the initiator sends page codes or parameter codes within thenF parameter list that are reserved or not implemented by the target, theK target shall terminate the LOG SELECT command with CHECK CONDITION status. -F The sense key shall be set to ILLEGAL REQUEST and the additional sense, code set to INVALID FIELD IN PARAMETER LIST.  J If a parameter list length results in the truncation of any log parameter,H the target shall terminate the command with CHECK CONDITION status.  TheG sense key shall be set to ILLEGAL REQUEST and the additional sense codet set to INVALID FIELD IN CDB.    H The initiator should send pages in ascending order by page code value ifA multiple pages are sent during a DATA OUT phase.  If multiple logdH parameters within a page are sent during the DATA OUT phase, they shouldE be sent in ascending order by parameter code value.  The target shall G return CHECK CONDITION status if the initiator sends pages out of orderrG or parameter codes out of order.  The sense key shall be set to ILLEGAL G REQUEST and the additional sense code set to INVALID FIELD IN PARAMETERi LIST.c  J    NOTE 73 Initiators should issue LOG SENSE commands prior to issuing LOGA    SELECT commands to determine supported pages and page lengths.   J The target may provide independent sets of log parameters for each logicalE unit or for each combination of logical units and initiators.  If the F target does not support independent sets of log parameters and any logJ parameters are changed that affect other initiators, then the target shallJ generate a unit attention condition for all initiators except the one thatG issued the LOG SELECT command (see 7.9).  This unit attention conditionfD is returned with an additional sense code of LOG PARAMETERS CHANGED.  C If the initiator sends a log parameter that is not supported by theaC target, the target shall terminate the command with CHECK CONDITIONbJ status, set the sense key to ILLEGAL REQUEST, and set the additional sense( code to INVALID FIELD IN PARAMETER LIST.   8.2.7 LOG SENSE command   G The LOG SENSE command (see table 51) provides a means for the initiatorEF to retrieve statistical information maintained by the device about theF device or its logical units.  It is a complementary command to the LOG SELECT command.o  5                          Table 51 - LOG SENSE commandnO +=====-========-========-========-========-========-========-========-========+eO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |rO |Byte |        |        |        |        |        |        |        |        |uO |=====+=======================================================================|IO | 0   |                           Operation code (4Dh)                        |tO |-----+-----------------------------------------------------------------------|dO | 1   | Logical unit number      |         Reserved         |  PPC   |    SP  |eO |-----+-----------------------------------------------------------------------|vO | 2   |        PC        |        Page code                                   | O |-----+-----------------------------------------------------------------------|nO | 3   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|nO | 4   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|iO | 5   | (MSB)                                                                 |(O |-----+---                        Parameter pointer                        ---|oO | 6   |                                                                 (LSB) |iO |-----+-----------------------------------------------------------------------|rO | 7   | (MSB)                                                                 |aO |-----+---                        Allocation length                        ---| O | 8   |                                                                 (LSB) |oO |-----+-----------------------------------------------------------------------|oO | 9   |                           Control                                     |-O +=============================================================================+|    G The parameter pointer control (PPC) bit controls the type of parameters  requested from the target:L    a)     A PPC bit of one indicates that the target shall return a log pageI           with parameter code values that have changed since the last LOG J           SELECT or LOG SENSE command.  The target shall return only those@           parameter codes following the parameter pointer field.K    b)     A PPC bit of zero indicates that the log parameter requested from-I           the target shall begin with the parameter code specified in the M           parameter pointer field and return the number of bytes specified by K           the allocation length field in ascending order of parameter codes-I           from the specified log page.  A PPC bit of zero and a parameter L           pointer field of zero shall cause all available log parameters forK           the specified log page to be returned to the initiator subject to *           the specified allocation length.  G Saving parameters is an optional function of the LOG SENSE command.  If C the target does not implement saving log parameters and if the save-H parameters (SP) bit is one, then the target shall return CHECK CONDITIONJ status, set the sense key to ILLEGAL REQUEST, and set the additional sense code to INVALID FIELD IN CDB.   F An SP bit of zero indicates the target shall perform the specified LOGC SENSE command and shall not save any log parameters.  If saving log-E parameters is implemented, an SP bit of one indicates that the target D shall perform the specified LOG SENSE command and shall save all logI parameters identified as savable by the DS bit (8.3.2) to a non-volatile,- vendor-specific location.   F The page control (PC) field defines the type of parameter values to beG selected (see 8.2.6 for the definition of the page control field).  The=B parameter values returned by a LOG SENSE command are determined as follows:K    a)     The specified parameter values at the last update (in response toeH           a LOG SELECT or LOG SENSE command or done automatically by the(           target for cumulative values).H    b)     The saved values, if an update has not occurred since the lastI           power-on, hard RESET condition, or BUS DEVICE RESET message and +           saved parameters are implemented.cJ    c)     The default values, if an update has not occurred since the lastI           power-on, hard RESET condition, or BUS DEVICE RESET message anda<           saved values are not available or not implemented.  I The page code field identifies which page of data is being requested (seebJ 8.3.2).  If the page code is reserved or not implemented, the target shallG terminate the command with CHECK CONDITION status.  The sense key shalliG be set to ILLEGAL REQUEST with the additional sense code set to INVALIDj FIELD IN CDB.   J The parameter pointer field allows the initiator to request parameter dataI beginning from a specific parameter code to the maximum allocation length J or the maximum parameter code supported by the target, whichever is less. F If the value of the parameter pointer field is larger than the largestB available parameter code that can be returned by the target on theA specified page, the target shall terminate the command with CHECKrH CONDITION status.  The sense key shall be set to ILLEGAL REQUEST and the< additional sense code shall be set to INVALID FIELD IN CDB.   D Log parameters within the specified log page shall be transferred in, ascending order according to parameter code.   8.2.8 MODE SELECT(6) command  B The MODE SELECT(6) command (see table 52) provides a means for theJ initiator to specify medium, logical unit, or peripheral device parametersI to the target.  Targets that implement the MODE SELECT command shall also E implement the MODE SENSE command.  Initiators should issue MODE SENSElI prior to each MODE SELECT to determine supported pages, page lengths, andu other parameters.r  7                       Table 52 - MODE SELECT(6) command O +=====-========-========-========-========-========-========-========-========+=O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |aO |=====+=======================================================================|oO | 0   |                           Operation code (15h)                        |rO |-----+-----------------------------------------------------------------------|tO | 1   | Logical unit number      |   PF   |         Reserved         |  SP    | O |-----+-----------------------------------------------------------------------|gO | 2   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|iO | 3   |                           Reserved                                    |tO |-----+-----------------------------------------------------------------------|tO | 4   |                           Parameter list length                       |,O |-----+-----------------------------------------------------------------------|tO | 5   |                           Control                                     | O +=============================================================================+d  G If a target supports saved pages, it may save only one copy of the pageiI for each logical unit and have it apply to all initiators, or it may savesF separate copies for each initiator for each logical unit.  If separateG copies are saved, the target shall maintain separate current values for J each I_T_L nexus. Pages that are common to all initiators are not required to have multiple copies. e  G If an initiator sends a MODE SELECT command that changes any parametersaH applying to other initiators, the target shall generate a unit attentionG condition for all initiators except the one that issued the MODE SELECTwJ command (see 7.9).  The target shall set the additional sense code to MODE PARAMETERS CHANGED.   B The target may provide for independent sets of parameters for eachA attached logical unit or for each combination of logical unit andoJ initiator.  If independent sets of parameters are implemented, and a thirdJ party reservation is requested, the target transfers the set of parametersI in effect for the initiator of the RESERVE command to the parameters usedAF for commands from the third party device (see 9.2.12.3 and 10.2.10.1).  H A page format (PF) bit of zero indicates that the MODE SELECT parameters@ are as specified in SCSI-1, (i.e. all parameters after the blockJ descriptors are vendor-specific).  A PF bit of one indicates that the MODEB SELECT parameters following the header and block descriptor(s) areF structured as pages of related parameters and are as specified in this	 standard.p  D A save pages (SP) bit of zero indicates the target shall perform theI specified MODE SELECT operation, and shall not save any pages.  An SP bitTH of one indicates that the target shall perform the specified MODE SELECTH operation, and shall save to a non-volatile vendor-specific location allG the savable pages including any sent during the DATA OUT phase.  The SPgI bit is optional, even when mode pages are supported by the target.  Pages B that are saved are identified by the parameter savable bit that isJ returned in the page header by the MODE SENSE command (see 8.3.3).  If theF PS bit is set in the MODE SENSE data then the page shall be savable byJ issuing a MODE SELECT command with the SP bit set.  If the target does notH implement saved pages and the SP bit is set to one, the command shall beE terminated with CHECK CONDITION status. The sense key shall be set tohF ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN CDB.  I The parameter list length field specifies the length in bytes of the modetI parameter list that shall be transferred from the initiator to the targetEJ during the DATA OUT phase.  A parameter list length of zero indicates thatH no data shall be transferred.  This condition shall not be considered as	 an error.t  I The target shall terminate the command with CHECK CONDITION status if the E parameter list length results in the truncation of any mode parameter=H header, mode parameter block descriptor(s), or mode page.  The sense keyG shall be set to ILLEGAL REQUEST, and the additional sense code shall be $ set to PARAMETER LIST LENGTH ERROR.   F The mode parameter list for the MODE SELECT and MODE SENSE commands isI defined in 8.3.3.  Parts of each mode parameter list are uniquely definedp for each device-type.   G The target shall terminate the MODE SELECT command with CHECK CONDITION-F status, set the sense key to ILLEGAL REQUEST, set the additional senseG code to INVALID FIELD IN PARAMETER LIST, and  shall not change any mode-( parameters for the following conditions:L    a)     If the initiator sets any field that is reported as not changeable@           by the target to a value other than its current value.I    b)     If the initiator sets any field in the mode parameter header or 6           block descriptor(s) to an unsupported value.K    c)     If an initiator sends a mode page with a page length not equal to K           the page length returned by the MODE SENSE command for that page.-M    d)     If the initiator sends a unsupported value for a mode parameter and >           rounding is not implemented for that mode parameter.M    e)     If the initiator sets any reserved field in the mode parameter list-           to a non-zero value.  G If the initiator sends a value for a mode parameter that is outside the-G range supported by the target and rounding is implemented for that mode ! parameter, the target may either: N    a)     round the parameter to an acceptable value and terminate the command            as described in 7.5.4;N    b)     terminate the command with CHECK CONDITION status, the sense key setJ           to ILLEGAL REQUEST, and set the additional sense code to INVALID"           FIELD IN PARAMETER LIST.  B A target may alter any mode parameter in any mode page (even those@ reported as non-changeable) as a result of changes to other mode parameters.e  C The target validates the non-changeable mode parameters against theeG current values that existed for those mode parameters prior to the MODEs SELECT command.   P    NOTE 74 If the current values calculated by the target affect the initiator'sM    operation, the initiator should issue a MODE SENSE command after each MODE     SELECT command.   8.2.9 MODE SELECT(10) commandi  C The MODE SELECT(10) command (see table 53) provides a means for theeJ initiator to specify medium, logical unit, or peripheral device parametersH to the target.  See the MODE SELECT(6) command (8.2.8) for a descriptionH of the fields in this command.  Initiators should issue MODE SENSE priorI to each MODE SELECT to determine supported mode pages, mode page lengths,z and other parameters.   8                       Table 53 - MODE SELECT(10) commandO +=====-========-========-========-========-========-========-========-========+sO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |aO |=====+=======================================================================| O | 0   |                           Operation code (55h)                        |eO |-----+-----------------------------------------------------------------------|aO | 1   | Logical unit number      |   PF   |         Reserved         |  SP    |aO |-----+-----------------------------------------------------------------------|nO | 2   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|aO | 3   |                           Reserved                                    |eO |-----+-----------------------------------------------------------------------|nO | 4   |                           Reserved                                    |eO |-----+-----------------------------------------------------------------------|eO | 5   |                           Reserved                                    |tO |-----+-----------------------------------------------------------------------|pO | 6   |                           Reserved                                    |rO |-----+-----------------------------------------------------------------------|cO | 7   | (MSB)                                                                 | O |-----+---                        Parameter list length                    ---| O | 8   |                                                                 (LSB) |iO |-----+-----------------------------------------------------------------------|rO | 9   |                           Control                                     |aO +=============================================================================+o    G Targets that implement the MODE SELECT(10) command shall also implementi the MODE SENSE(10) command.  a   8.2.10 MODE SENSE(6) command  I The MODE SENSE(6) command (see table 54) provides a means for a target to I report parameters to the initiator.  It is a complementary command to the  MODE SELECT(6) command.   7                        Table 54 - MODE SENSE(6) commandeO +=====-========-========-========-========-========-========-========-========+tO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |eO |Byte |        |        |        |        |        |        |        |        |wO |=====+=======================================================================|oO | 0   |                           Operation code (1Ah)                        |eO |-----+-----------------------------------------------------------------------|oO | 1   | Logical unit number      |Reserved|   DBD  |         Reserved         |EO |-----+-----------------------------------------------------------------------|sO | 2   |       PC        |                   Page code                         |tO |-----+-----------------------------------------------------------------------|oO | 3   |                           Reserved                                    |=O |-----+-----------------------------------------------------------------------|0O | 4   |                           Allocation length                           | O |-----+-----------------------------------------------------------------------|=O | 5   |                           Control                                     | O +=============================================================================+-    G A disable block descriptors (DBD) bit of zero indicates that the target|I may return zero or more block descriptors in the returned MODE SENSE data-I (see 8.3.3), at the target's discretion.  A DBD bit of one specifies that F the target shall not return any block descriptors in the returned MODE SENSE data.-  H The page control (PC) field defines the type of mode parameter values toD be returned in the mode pages.  The page control field is defined in	 table 55.-  5                         Table 55 - Page control field , +=======-=====================-============+, | Code  |  Type of parameter  | Subclause  |, |-------+---------------------+------------|, |  00b  |  Current values     |  8.2.10.1  |, |  01b  |  Changeable values  |  8.2.10.2  |, |  10b  |  Default values     |  8.2.10.3  |, |  11b  |  Saved values       |  8.2.10.4  |, +==========================================+  M    NOTE 75 The page control field only affects the mode parameters within theeJ    mode pages, however the PS bit, page code and page length fields shouldO    return current values since they have no meaning when used with other types.xN    The mode parameter header and mode parameter block descriptor should return    current values.  E The page code specifies which mode page(s) to return.  Mode page codeg usage is defined in table 56.t  >                Table 56 - Mode page code usage for all devicesO +=============-==================================================-============+tO |  Page code  |  Description                                     |  Subclause |eO |-------------+--------------------------------------------------+------------|oO |     00h     |  Vendor-specific (does not require page format)  |            | O |  01h - 1Fh  |  See specific device-types                       |            |eO |  20h - 3Eh  |  Vendor-specific (page format required)          |            |aO |     3Fh     |  Return all mode pages                           |            |1O +=============================================================================+r  H An initiator may request any one or all of the supported mode pages fromG a target.  If an initiator issues a MODE SENSE command with a page coderB value not implemented by the target, the target shall return CHECKG CONDITION status and shall set the sense key to ILLEGAL REQUEST and the / additional sense code to INVALID FIELD IN CDB. g  J A page code of 3Fh indicates that all mode pages implemented by the targetG shall be returned to the initiator.  If the mode parameter list exceedseJ 256 bytes for a MODE SENSE(6) command or 65 536 bytes for a MODE SENSE(10)I command, the target shall return CHECK CONDITION status and the sense keypD shall be set to ILLEGAL REQUEST and the additional sense code set to INVALID FIELD IN CDB.   E Mode page 00h, if implemented, shall be returned after all other moded pages.      NOTESP    76 Mode pages should be returned in ascending page code order except for mode    page 00h.M    77 If the PC field and the page code field are both set to zero the targettO    should return a mode parameter header and block descriptor (if applicable). nC    This provides for compatibility with existing SCSI-1 initiators.l  E The mode parameter list for all device types for MODE SELECT and MODEI@ SENSE is defined in 8.3.3.  Parts of the mode parameter list areG specifically defined for each device type.  See subclause three of eacho/ peripheral device type for further information.U   8.2.10.1 Current valuesl  I A PC field value of 0h requests that the target return the current valuesh9 of the mode parameters.  The current values returned are:rG    a)     the current values of the mode parameters established by lastn)           successful MODE SELECT command;aN    b)     the saved values of the mode parameters if a MODE SELECT command hasH           not successfully completed since the last power-on, hard RESET1           condition, or BUS DEVICE RESET message;eM    c)     the default values of the mode parameters, if saved values, are not3%           available or not supported.e   8.2.10.2 Changeable values  F A PC field value of 1h requests that the target return a mask denotingJ those mode parameters that are changeable.  In the mask, the fields of theH mode parameters that are changeable shall be set to all one bits and theJ fields of the mode parameters that are non-changeable (i.e. defined by the& target) shall be set to all zero bits.      NOTESL    78 An attempt to change a non-changeable mode parameter (via MODE SELECT)-    results in an error condition (see 8.2.8).aN    79 The initiator should issue a MODE SENSE command with the PC field set toJ    1h and the page code field set to 3Fh to determine which mode pages areM    supported, which mode parameters within the mode pages are changeable, anddJ    the supported length of each mode page prior to issuing any MODE SELECT    commands.   8.2.10.3 Default values   I A PC field value of 2h requests that the target return the default valueshH of the mode parameters.  Parameters not supported by the target shall beE set to zero.  Default values are accessible even if the device is note ready.   8.2.10.4 Saved valuesm  G A PC field value of 3h requests that the target return the saved valuesnC of the mode parameters.  Implementation of saved page parameters is F optional.  Mode parameters not supported by the target shall be set to@ zero.  If saved values are not implemented, the command shall beD terminated with CHECK CONDITION status, the sense key set to ILLEGALB REQUEST and the additional sense code set to SAVING PARAMETERS NOT
 SUPPORTED.  N    NOTE 80 The method of saving parameters is vendor-specific.  The parametersK    are preserved in such a manner that they are retained when the target isrN    powered down.  All savable pages can be considered saved when a MODE SELECTP    command issued with the SP bit set to one has returned a GOOD status or after6    the successful completion of a FORMAT UNIT command.   8.2.10.5 Initial responses  D After a power-up condition or hard reset condition, the target shall  respond in the following manner:E    a)     If default values are requested, report the default values.eC    b)     If saved values are requested, report valid restored modemM           parameters, or restore the mode parameters and report them.  If thelN           saved values of the mode parameters are not able to be accessed fromJ           the non-volatile vendor-specific location, terminate the commandN           with CHECK CONDITION status and set the sense key set to NOT READY. G           If saved parameters are not implemented respond as defined in            8.2.10.4. L    c)     If current values are requested and the current values of the modeK           parameters have not been sent by the initiator (via a MODE SELECT=M           command), the target may return either the default or saved values,)J           as defined above.  If current values have been sent, the current#           values shall be reported.     MODE SENSE(10) command   G The MODE SENSE(10) command (see table 57) provides a means for a target-H to report parameters to the initiator.  It is a complementary command to? the MODE SELECT(10) command.  If the MODE SELECT(10) command is-J implemented the MODE SENSE(10) command shall be implemented.  See the MODEA SENSE(6) command for a description of the fields in this command.   7                       Table 57 - MODE SENSE(10) command-O +=====-========-========-========-========-========-========-========-========+dO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |-O |Byte |        |        |        |        |        |        |        |        |dO |=====+=======================================================================|-O | 0   |                           Operation code (5Ah)                        |dO |-----+-----------------------------------------------------------------------|-O | 1   | Logical unit number      |Reserved|  DBD   |         Reserved         | O |-----+-----------------------------------------------------------------------|eO | 2   |       PC        |                   Page code                         | O |-----+-----------------------------------------------------------------------|-O | 3   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|=O | 4   |                           Reserved                                    |TO |-----+-----------------------------------------------------------------------| O | 5   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|tO | 6   |                           Reserved                                    |6O |-----+-----------------------------------------------------------------------|-O | 7   | (MSB)                                                                 ||O |-----+---                        Allocation length                        ---||O | 8   |                                                                 (LSB) |=O |-----+-----------------------------------------------------------------------| O | 9   |                           Control                                     |-O +=============================================================================+      8.2.12 READ BUFFER Command  F The READ BUFFER command (see table 58) is used in conjunction with theG WRITE BUFFER command as a diagnostic function for testing target memory-E and the SCSI bus integrity.  This command shall not alter the medium.-  6                         Table 58 - READ BUFFER commandO +=====-========-========-========-========-========-========-========-========+-O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |-O |=====+=======================================================================| O | 0   |                           Operation code (3Ch)                        |=O |-----+-----------------------------------------------------------------------|nO | 1   | Logical unit number      |     Reserved    |           Mode           |eO |-----+-----------------------------------------------------------------------|eO | 2   |                           Buffer ID                                   |OO |-----+-----------------------------------------------------------------------|rO | 3   | (MSB)                                                                 | O |-----+---                                                                 ---|=O | 4   |                           Buffer offset                               |-O |-----+---                                                                 ---|1O | 5   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|=O | 6   | (MSB)                                                                 |mO |-----+---                                                                 ---| O | 7   |                           Allocation length                           |eO |-----+---                                                                 ---|iO | 8   |                                                                 (LSB) |(O |-----+-----------------------------------------------------------------------|TO | 9   |                           Control                                     |=O +=============================================================================+     I The function of this command and the meaning of fields within the command-J descriptor block depend on the contents of the mode field.  The mode field is defined in table 59.p  7                       Table 59 - READ BUFFER mode field D          +========-============================-===================+D          |  Mode  |  Description               |    Type           |D          |--------+----------------------------+-------------------|D          |  000b  |  Combined header and data  |  Optional         |D          |  001b  |  Vendor-specific           |  Vendor-specific  |D          |  010b  |  Data                      |  Optional         |D          |  011b  |  Descriptor                |  Optional         |D          |  100b  |  Reserved                  |  Reserved         |D          |  101b  |  Reserved                  |  Reserved         |D          |  110b  |  Reserved                  |  Reserved         |D          |  111b  |  Reserved                  |  Reserved         |D          +=========================================================+  P    NOTE 81 Modes 000b and 001b are included for compatibility with products thatN    were designed prior to the generation of this International Standard.  SomeL    products that were designed prior to the generation of this International:    Standard restrict the available length to 65 535 bytes.  - 8.2.12.1 Combined header and data mode (000b)o  J In this mode, a four-byte header followed by data bytes is returned to theH initiator during the DATA IN phase.  The buffer ID and the buffer offset fields are reserved. o  I The four-byte READ BUFFER header (see table 60) is followed by data bytes  from the target's data buffer.  5                         Table 60 - READ BUFFER headerEO +=====-========-========-========-========-========-========-========-========+nO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |rO |Byte |        |        |        |        |        |        |        |        |eO |=====+=======================================================================|eO | 0   |                           Reserved                                    |aO |-----+-----------------------------------------------------------------------| O | 1   | (MSB)                                                                 |fO |- - -+---                        Buffer capacity                          ---|EO | 3   |                                                                 (LSB) |eO +=============================================================================+     B The buffer capacity field specifies the total number of data bytesE available in the target's data buffer.  This number is not reduced tofG reflect the allocation length;  nor is it reduced to reflect the actual F number of bytes written using the WRITE BUFFER command.  Following theI READ BUFFER header, the target shall transfer data from its data buffer.  G The target terminates the DATA IN phase when allocation length bytes of G header plus data have been transferred or when all available header andiF buffer data have been transferred to the initiator, whichever is less.  $ 8.2.12.2 Vendor-specific mode (001b)  J In this mode, the meanings of the buffer ID, buffer offset, and allocation? length fields are not specified by this International Standard.    8.2.12.3 Data mode (010b)   J In this mode, the DATA IN phase contains buffer data.  The buffer ID fieldG identifies a specific buffer within the target from which data shall berF transferred.  The vendor assigns buffer ID codes to buffers within theF target. Buffer ID zero shall be supported.  If more than one buffer isE supported, additional buffer ID codes shall be assigned contiguously,lJ beginning with one. Buffer ID code assignments for the READ BUFFER commandE shall be the same as for the WRITE BUFFER command.  If an unsupported C buffer ID code is selected, the target shall return CHECK CONDITIONmJ status, shall set the sense key to ILLEGAL REQUEST, and set the additionalF sense code to ILLEGAL FIELD IN CDB.  The target terminates the DATA INH phase when allocation length bytes have been transferred or when all theE available data from the buffer has been transferred to the initiator,  whichever amount is less..  E The buffer offset field contains the byte offset within the specifieddG buffer from which data shall be transferred from.  The initiator should G conform to the offset boundary requirements returned in the READ BUFFERrA descriptor (see 8.2.12.4).  If the target is unable to accept the J specified buffer offset, it shall return CHECK CONDITION status, shall setF the sense key to ILLEGAL REQUEST, and set the additional sense code to ILLEGAL FIELD IN CDB.i   8.2.12.4 Descriptor mode (011b)e  ? In this mode, a maximum of four bytes of READ BUFFER descriptor @ information is returned.  The target shall return the descriptorJ information for the buffer specified by the buffer ID (see the descriptionI of the buffer ID in 8.2.12.3).  If there is no buffer associated with theNI specified buffer ID, the target shall return all zeros in the READ BUFFERfC descriptor.  The buffer offset field is reserved in this mode.  ThesE allocation length should be set to four or greater.  The target shalleI transfer the lesser of the allocation length or four bytes of READ BUFFERtH descriptor.  The READ BUFFER descriptor is defined as shown in table 61.  7                       Table 61 - READ BUFFER descriptor O +=====-========-========-========-========-========-========-========-========+mO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |nO |Byte |        |        |        |        |        |        |        |        |MO |=====+=======================================================================|mO | 0   |                           Offset boundary                             |mO |--- -+-----------------------------------------------------------------------|=O | 1   | (MSB)                                                                 | O |- - -+---                        Buffer capacity                          ---| O | 3   |                                                                 (LSB) |=O +=============================================================================+     C The offset boundary field returns the boundary alignment within the-J selected buffer for subsequent WRITE BUFFER and READ BUFFER commands.  TheF value contained in the offset boundary field shall be interpreted as a
 power of two.-  I The value contained in the buffer offset field of subsequent WRITE BUFFER M and READ BUFFER commands should be a multiple of 2offset boundary as shown in 	 table 62.-  7                       Table 62 - Buffer offset boundary-J +========-====================-==========================================+J |Offset  |                    |                                          |J |boundary| 2**Offset boundary |  Buffer offsets                          |J |--------+--------------------+------------------------------------------|J |   0    |      2**0 = 1      |  Byte boundaries                         |J |   1    |      2**1 = 2      |  Even-byte boundaries                    |J |   2    |      2**2 = 4      |  Four-byte boundaries                    |J |   3    |      2**3 = 8      |  Eight-byte boundaries                   |J |   4    |      2**4 = 16     |  16-byte boundaries                      |J |   .    |          .         |         .                                |J |   .    |          .         |         .                                |J |  FFh   |  Not applicable    |  0 is the only supported buffer offset.  |J +========================================================================+    I The buffer capacity field shall return the size of the selected buffer in  bytes.  O    NOTE 82 In a multi-tasking system, a buffer may be altered between the WRITE P    BUFFER and READ BUFFER commands by another task.  Buffer testing applicationsP    may wish to insure that only a single task is active. Use of reservations (toM    all logical units on the device) or linked commands may also be helpful ini:    avoiding buffer alteration between these two commands.   ) 8.2.13 RECEIVE DIAGNOSTIC RESULTS command=  G The RECEIVE DIAGNOSTIC RESULTS command (see table 63) requests analysis C data be sent to the initiator after completion of a SEND DIAGNOSTIC G command (see 8.2.15).  If the target supports the optional page format,=J the page code field sent in the previous SEND DIAGNOSTIC command specifies! the format of the returned data. o  =                 Table 63 - RECEIVE DIAGNOSTIC RESULTS command-O +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |-O |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================|-O | 0   |                           Operation code (1Ch)                        | O |-----+-----------------------------------------------------------------------| O | 1   | Logical unit number      |             Reserved                       | O |-----+-----------------------------------------------------------------------| O | 2   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|-O | 3   | (MSB)                                                                 | O |-----+---                        Allocation length                        ---| O | 4   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------| O | 5   |                           Control                                     | O +=============================================================================+-      NOTESM    83 To insure that the diagnostic command information is not destroyed by aoJ    command sent from another initiator, either the SEND DIAGNOSTIC commandK    should either be linked to the RECEIVE DIAGNOSTIC RESULTS command or thea#    logical unit should be reserved.hM    84 Although diagnostic software is generally device-specific, this commandeK    and the SEND DIAGNOSTIC command provide a means to isolate the operatingFK    system software from the device-specific diagnostic software. Hence, the=O    operating system can remain device-independent.  This also allows diagnostic E    software to be transferred more easily to other operating systems.   A See 8.3.1 for RECEIVE DIAGNOSTIC RESULTS page format definitions.    8.2.14 REQUEST SENSE Command  J The REQUEST SENSE command (see table 64) requests that the target transfer sense data to the initiator.  7                        Table 64 - REQUEST SENSE command O +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================|=O | 0   |                           Operation code (03h)                        |tO |-----+-----------------------------------------------------------------------|rO | 1   | Logical unit number      |                  Reserved                  |oO |-----+-----------------------------------------------------------------------| O | 2   |                           Reserved                                    |dO |-----+-----------------------------------------------------------------------| O | 3   |                           Reserved                                    |DO |-----+-----------------------------------------------------------------------|bO | 4   |                           Allocation length                           |-O |-----+-----------------------------------------------------------------------||O | 5   |                           Control                                     ||O +=============================================================================+=     The sense data:=L    a)     shall be available if a contingent allegiance condition exists for           the I_T_x nexus;K    b)     shall be available if other information (e.g. medium position) is-!           available in any field;B@    c)     may be available if an unexpected disconnect occurred.  J If the target has no other sense data available to return, it shall returnE a sense key of NO SENSE and an additional sense code of NO ADDITIONAL  SENSE INFORMATION.  G The sense data shall be preserved by the target fo  the initiator until=J retrieved by a REQUEST SENSE command or until the receipt of any other I/OC process for the same I_T_x nexus.  Sense data shall be cleared uponfF receipt of any subsequent I/O process (including REQUEST SENSE) to the same I_T_x nexus.   I    NOTE 85 Some target implementations do not update sense data except onhP    commands that return CHECK CONDITION or COMMAND TERMINATED status.  Thus whenN    polling for a logical unit to become ready, the initiator should issue TESTP    UNIT READY commands until GOOD status is returned.  If desired, the initiatorK    may issue REQUEST SENSE commands after the TEST UNIT READY commands thatiP    return CHECK CONDITION or COMMAND TERMINATED status to obtain the sense data.  J The target shall return CHECK CONDITION status for a REQUEST SENSE commandH only to report exception conditions specific to the command itself.  For example:N    a)     A non-zero reserved bit is detected in the command descriptor block;C    b)     An unrecovered parity error is detected on the data bus; gA    c)     A target malfunction prevents return of the sense data.   E If a recovered error occurs during the execution of the REQUEST SENSEeG command, the target shall return the sense data with GOOD status.  If a F target returns CHECK CONDITION status for a REQUEST SENSE command, the sense data may be invalid. h  L    NOTE 86 The sense data appropriate to the selection of an invalid logical    unit is defined in 7.5.3.  H Targets shall be capable of returning eighteen bytes of data in responseD to a REQUEST SENSE command.  If the allocation length is eighteen orC greater, and a target returns less than eighteen bytes of data, theiF initiator should assume that the bytes not transferred would have beenH zeros had the target returned those bytes.  Initiators can determine howD much sense data has been returned by examining the allocation lengthI parameter in the command descriptor block and the additional sense lengtheH in the sense data.  Targets shall not adjust the additional sense lengthJ to reflect truncation if the allocation length is less than the sense data available. n  B The sense data format for error codes 70h (current errors) and 71hG (deferred errors) are defined in table 65.  Error code values of 72h to E 7Eh are reserved.  Error code 7Fh is for a vendor-specific sense dataoH format.  Targets shall implement error code 70h; implementation of errorH code 71h is optional. Error code values of 00h to 6Fh are not defined by= this International Standard and their use is not recommended.E  A              Table 65 - Error codes 70h and 71h sense data formatmO +=====-========-========-========-========-========-========-========-========+eO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |cO |Byte |        |        |        |        |        |        |        |        | O |=====+========+==============================================================|-O | 0   | Valid  |                  Error code (70h or 71h)                     ||O |-----+-----------------------------------------------------------------------||O | 1   |                           Segment number                              |=O |-----+-----------------------------------------------------------------------| O | 2   |Filemark|  EOM   |  ILI   |Reserved|         Sense key                 |-O |-----+-----------------------------------------------------------------------| O | 3   | (MSB)                                                                 | O |- - -+---                        Information                              ---| O | 6   |                                                                 (LSB) |=O |-----+-----------------------------------------------------------------------|uO | 7   |                           Additional sense length (n-7)               |EO |-----+-----------------------------------------------------------------------|aO | 8   | (MSB)                                                                 |tO |- - -+---                        Command-specific information             ---| O | 11  |                                                                 (LSB) |BO |-----+-----------------------------------------------------------------------|=O | 12  |                           Additional sense code                       | O |-----+-----------------------------------------------------------------------| O | 13  |                           Additional sense code qualifier             | O |-----+-----------------------------------------------------------------------| O | 14  |                           Field replaceable unit code                 | O |-----+-----------------------------------------------------------------------|*O | 15  |  SKSV  |                                                              |1O |- - -+------------               Sense-key specific                       ---| O | 17  |                                                                       | O |-----+-----------------------------------------------------------------------| O | 18  |                                                                       |=O |- - -+---                        Additional sense bytes                   ---|fO | n   |                                                                       |rO +=============================================================================+     J A valid bit of zero indicates that the information field is not as definedA in this International Standard.  A valid bit of one indicates thee? information field contains valid information as defined in thisf? International Standard.  Targets shall implement the valid bit.N  C The segment number field contains the number of the current segmentaJ descriptor if the REQUEST SENSE command is in response to a COPY, COMPARE,H or COPY AND VERIFY command.  Up to 256 segments are supported, beginning with segment zero.    I The filemark bit is mandatory for sequential-access devices, and this bithH is reserved for all other device types.  A filemark bit of one indicatesH that the current command has read a filemark or setmark.  The additionalJ sense code field may be used to indicate whether a filemark or setmark wasJ read.  Reporting of setmarks is optional and indicated by the Rsmk bit forC sequential-access devices in the configuration parameters page (see=
 10.3.3.1).  J The end-of-medium (EOM) bit is mandatory for sequential-access and printerI devices, and this bit is reserved for all other device types.  An EOM bit-C of one indicates that an end-of-medium condition (end-of-partition,aJ beginning-of-partition, out-of-paper, etc.) exists.  For sequential-accessI devices, this bit indicates that the unit is at or past the early-warning H if the direction was forward, or that the command could not be completedC because beginning-of-partition was encountered if the direction was-
 reverse.    I An incorrect length indicator (ILI) bit of one usually indicates that the H requested logical block length did not match the logical block length of the data on the medium.   H The sense key, additional sense code and additional sense code qualifierI provide a hierarchy of information.  The intention of the hierarchy is to-E provide a top-down approach for an initiator to determine information G relating to the error and exception conditions.  The sense key provides=A generic categories in which error and exception conditions can beiI reported.  Initiators would typically use sense keys for high level erroriC recovery procedures.  Additional sense codes provide further detailkG describing the sense key.  Additional sense code qualifiers add furtheruC detail to the additional sense code.  The additional sense code andi? additional sense code qualifier can be used by initiators whereoD sophisticated error recovery procedures require detailed information. describing the error and exception conditions.  B The sense key field is mandatory and indicates generic informationG describing an error or exception condition.  The sense keys are defineds in 8.2.14.3.  H The contents of the information field is device-type or command specificC and is defined within the appropriate clause for the device type oreE command of interest.  Targets shall implement the information field.  0 Unless specified otherwise, this field contains:K    a)     the unsigned logical block address associated with the sense key, G           for direct-access devices (device type 0), write-once devices M           (device type 4), CD-ROM devices (device type 5), and optical memory|"           devices (device type 7).K    b)     the difference (residue) of the requested length minus the actual M           length in either bytes or blocks, as determined by the command, for-L           sequential-access devices (device type 1), printer devices (deviceK           type 2), processor devices (device type 3) and some direct access-K           device commands, except as defined for d) below. (Negative values 6           are indicated by two's complement notation.)N    c)     the difference (residue) of the requested number of blocks minus theL           actual number of blocks copied or compared for the current segmentD           descriptor of a COPY, COMPARE, or COPY AND VERIFY command.L    d)     For sequential-access devices operating in buffered modes 1h or 2hN           that detect an unrecoverable write error when unwritten data blocks,G           filemarks, or setmarks remain in the buffer, the value of the 6           information field for all commands shall be:L        1)    the total number of data blocks, filemarks, and setmarks in theL              buffer if the device is in fixed block mode (block length fieldM              of the MODE SENSE block descriptor is non-zero and the fixed biti+              of the WRITE command is one). -G        2)    the number of bytes in the buffer, including filemarks andeN              setmarks, if the device is in variable mode (the fixed bit of the'              WRITE command is zero).   f  J The additional sense length field indicates the number of additional senseJ bytes to follow.  If the allocation length of the command descriptor blockJ is too small to transfer all of the additional sense bytes, the additional7 sense length is not adjusted to reflect the truncation.e  H The command-specific information field contains information that dependsD on the command that was executed.  Further meaning for this field isI defined within the command description.  The command-specific information I field is mandatory if the target supports any of the following commands: bA COPY, COMPARE, COPY AND VERIFY, SEARCH DATA, and REASSIGN BLOCKS.s  C The additional sense code (ASC) field indicates further informationeE related to the error or exception condition reported in the sense keytG field.  Targets shall support the additional sense code field.  Support.= of the additional sense codes not explicitly required by thisTH International Standard is optional.  A list of additional sense codes isH in 8.2.14.3.  If the target does not have further information related toH the error or exception condition, the additional sense code is set to NO ADDITIONAL SENSE INFORMATION.c  I The additional sense code qualifier (ASCQ) indicates detailed informationrJ related to the additional sense code.  The additional sense code qualifierF is optional.  If the error or exception condition is reportable by theE device, the value returned shall be as specified in 8.2.14.3.  If theyA target does not have detailed information related to the error orcH exception condition, the additional sense code qualifier is set to zero.  D Non-zero values in the field replaceable unit code field are used toG define a device-specific mechanism or unit that has failed.  A value oftH zero in this field shall indicate that no specific mechanism or unit hasF been identified to have failed or that the data is not available.  TheA field replaceable unit code field is optional. The format of thistF information is not specified by this standard.  Additional informationJ about the field replaceable unit may be available in the ASCII information0 page (see 8.3.4.2), if supported by the target.   > The sense-key specific bytes are described in 8.2.14.1, below.  C The additional sense bytes field may contain command specific data, E peripheral device specific data, or vendor-specific data that further.1 defines the nature of the CHECK CONDITION status.E   8.2.14.1 Sense-key specificp  F The sense-key specific field as defined by this International StandardF when the value of the sense-key specific valid (SKSV) bit is one.  TheH sense-key specific valid bit and sense-key specific field are optional. H The definition of this field is determined by the value of the sense keyF field.  This field is reserved for sense keys not described below.  AnF SKSV value of zero indicates that this field is not as defined by this International Standard.   H If the sense key field is set to ILLEGAL REQUEST and the SKSV bit is setJ to one, the sense-key specific field shall be as defined as shown in tableE 66. The field pointer field indicates which illegal parameters in the = command descriptor block or the data parameters are in error.-  6                         Table 66 - Field pointer bytesO +=====-========-========-========-========-========-========-========-========+-O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    ||O |Byte |        |        |        |        |        |        |        |        |-O |=====+========+========+========+========+========+==========================| O | 15  |  SKSV  |  C/D   |Reserved|Reserved|  BPV   |    Bit pointer           | O |-----+-----------------------------------------------------------------------| O | 16  | (MSB)                                                                 |-O |-----+---                        Field pointer                            ---| O | 17  |                                                                 (LSB) |-O +=============================================================================+     G A command data (C/D) bit of one indicates that the illegal parameter is F in the command descriptor block.  A C/D bit of zero indicates that theH illegal parameter is in the data parameters sent by the initiator during the DATA OUT phase.-  I A bit pointer valid (BPV) bit of zero indicates that the value in the bit D pointer field is not valid.  A BPV bit of one indicates that the bitE pointer field specifies which bit of the byte designated by the field-J pointer field is in error.  When a multiple-bit field is in error, the bitH pointer field shall point to the most-significant (left-most) bit of the field.  F The field pointer field indicates which byte of the command descriptorI block or of the parameter data was in error.  Bytes are numbered starting-J from zero, as shown in the tables describing the commands and parameters. F When a multiple-byte field is in error, the pointer shall point to the0 most- significant (left-most) byte of the field.  P    NOTE 87 Bytes identified as being in error are not necessarily the place that,    has to be changed to correct the problem.  G If the sense key is RECOVERED ERROR, HARDWARE ERROR or MEDIUM ERROR and I if the SKSV bit is one, the sense-key specific field shall be as shown ini	 table 67.b  8                      Table 67 - Actual retry count bytesO +=====-========-========-========-========-========-========-========-========+=O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |aO |Byte |        |        |        |        |        |        |        |        | O |=====+========+==============================================================|aO | 15  |  SKSV  |                  Reserved                                    |tO |-----+-----------------------------------------------------------------------|iO | 16  | (MSB)                                                                 | O |-----+---                        Actual retry count                       ---| O | 17  |                                                                 (LSB) |sO +=============================================================================+c    H The actual retry count field returns implementation-specific informationA on the actual number of retries of the recovery algorithm used in 7 attempting to recover an error or exception condition. s  N    NOTE 88 This field should relate to the retry count fields within the error,    recovery page of the MODE SELECT command.  D If the sense key is NOT READY and the SKSV bit is one, the sense-keyI specific field shall be as shown in table 68.  These fields only apply tod6 the FORMAT UNIT command with the Immed bit set to one.  <                  Table 68 - Format progress indication bytesO +=====-========-========-========-========-========-========-========-========+dO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |nO |Byte |        |        |        |        |        |        |        |        |lO |=====+========+==============================================================|lO | 15  |  SKSV  |                  Reserved                                    | O |-----+-----------------------------------------------------------------------| O | 16  | (MSB)                                                                 |-O |-----+---                        Progress indication                      ---|nO | 17  |                                                                 (LSB) |oO +=============================================================================+s    G The progress indication field is a percent complete indication in whichoC the returned value is the numerator that has 65 536 (10000h) as itseF denominator. The progress indication shall based upon the total formatC operation including any certification or initialization operations.y  H    NOTE 89 It is intended that the progress indication be time related. L    However, since format time varies with the number of defects encountered,J    etc., it is reasonable for the target to assign values to various stepsM    within the process.  The granularity of these steps should be small enoughsK    to provide reasonable assurances to the initiator that progress is beingw    made.   8.2.14.2 Deferred errors  G Error code 70h indicates that the CHECK CONDITION or COMMAND TERMINATEDoG status returned is the result of an error or exception condition on thehJ I/O process that returned the CHECK CONDITION or COMMAND TERMINATED statusC or an unexpected disconnect.  This includes errors generated during B execution of the command by the actual execution process.  It alsoI includes errors not related to any command that are first observed during)F execution of a command.  Examples of this latter type of error includeB disk servo-mechanism, off-track errors, and power-up test errors.   I Error code 71h (deferred error) indicates that the CHECK CONDITION status2G returned is the result of an error or exception condition that occurredeH during execution of a previous command for which GOOD status has alreadyF been returned.  Such commands are associated with use of the immediateF bit, with some forms of caching, and with multiple command buffering. H Targets that implement these features are required to implement deferred error reporting.  J The deferred error indication may be sent at a time selected by the targetI through the asynchronous event notification process (see 7.5.5) if AEN isb- supported by both the initiator and target.     I If AEN is not supported, the deferred error may be indicated by returning H CHECK CONDITION status to the appropriate initiator as described below. D The subsequent execution of a REQUEST SENSE command shall return the! deferred error sense information.o  @ If an I/O process terminates with CHECK CONDITION status and theI subsequent sense data returns a deferred error that I/O process shall noteH have been executed.  After the target detects a deferred error conditionJ on a logical unit, it shall return a deferred error according to the rules described below:  F    a)     If a deferred error can be recovered with no external systemN           intervention, a deferred error indication shall not be posted unlessF           required by the error handling parameters of the MODE SELECTL           command.  The occurrence of the error may be logged if statistical(           or error logging is supported.L    b)     If a deferred error can be associated with a causing initiator andL           with a particular function or a particular subset of data, and theL           error is either unrecovered or required to be reported by the modeJ           parameters, a deferred error indication shall be returned to theN           causing initiator.  If an initiator other than the causing initiatorF           attempts access to the particular function or subset of dataM           associated with the deferred error, a BUSY status shall be returned M           to that initiator in response to the command attempting the access.T  L    NOTE 91 Not all devices may be sufficiently sophisticated to identify theM    function or data that failed.  Those that cannot should treat the error in     the following manner.  K    c)     If a deferred error cannot be associated with a causing initiatoriJ           or with a particular subset of data, a deferred error indicationI           shall be returned on behalf of the failing logical unit to eachoK           initiator.  If multiple deferred errors have accumulated for somea<           initiators, only the last error shall be returned.L    d)     If a deferred error cannot be associated with a particular logicalI           unit, it shall be returned to the appropriate initiator for alle0           logical units supported by the target.L    e)     If a current command has not yet started executing, and a deferredL           error occurs, the command shall be terminated with CHECK CONDITIONM           status and deferred error information posted in the sense data.  BylG           convention, the current command is considered to have startednM           execution if the target has changed phase from the COMMAND phase toaM           the next normal phase of the command sequence.  If a deferred erroroM           occurs while a current command is executing and the current command L           has been affected by the error, the command shall be terminated byG           CHECK CONDITION status and current error information shall be I           returned in the sense data.  In this case, if the current erroreN           information does not adequately define the deferred error condition,N           a deferred error may be returned after the current error informationI           has been recovered.  If a deferred error occurs while a currentiN           command is executing and the current command completes successfully,N           the target may choose to return the deferred error information after0           the completion of the current command.  O    NOTE 91 Deferred errors may indicate that an operation was unsuccessful longeP    after the command performing the data transfer returned GOOD status.  If dataL    that cannot be replicated or recovered from other sources is being storedP    using buffered write operations, synchronization commands should be performedH    before the critical data is destroyed in the host initiator.  This isM    necessary to be sure that recovery actions can be taken if deferred errors F    do occur in the storing of the data. If AEN is not implemented, theG    synchronizing process should provide the necessary commands to allow=N    returning CHECK CONDITION status and subsequent returning of deferred errorG    sense information after all buffered operations are guaranteed to be     complete.    - 8.2.14.3 Sense key and sense code definitions-  / The sense keys are defined in tables 69 and 70.   ;                   Table 69 - Sense key (0h-7h) descriptions O +========-====================================================================+ O | Sense  |  Description                                                       |=O |  key   |                                                                    |aO |--------+--------------------------------------------------------------------|rO |   0h   |  NO SENSE.  Indicates that there is no specific sense key          |aO |        |  information to be reported for the designated logical unit.  This | O |        |  would be the case for a successful command or a command that      |tO |        |  received CHECK CONDITION or COMMAND TERMINATED status because one |iO |        |  of the filemark, EOM, or ILI bits is set to one.                  |lO |--------+--------------------------------------------------------------------|nO |   1h   |  RECOVERED ERROR.  Indicates that the last command completed       |oO |        |  successfully with some recovery action performed by the target.   | O |        |  Details may be determinable by examining the additional sense     | O |        |  bytes and the information field.  When multiple recovered errors  |tO |        |  occur during one command, the choice of which error to report     |eO |        |  (first, last, most severe, etc.) is device specific.              |oO |--------+--------------------------------------------------------------------|UO |   2h   |  NOT READY.  Indicates that the logical unit addressed cannot be   |oO |        |  accessed.  Operator intervention may be required to correct this  |=O |        |  condition.                                                        | O |--------+--------------------------------------------------------------------|BO |   3h   |  MEDIUM ERROR.  Indicates that the command terminated with a non-  |=O |        |  recovered error condition that was probably caused by a flaw in   | O |        |  the medium or an error in the recorded data.  This sense key may  |-O |        |  also be returned if the target is unable to distinguish between a | O |        |  flaw in the medium and a specific hardware failure (sense key 4h).|-O |--------+--------------------------------------------------------------------| O |   4h   |  HARDWARE ERROR.  Indicates that the target detected a non-        |=O |        |  recoverable hardware failure (for example, controller failure,    | O |        |  device failure, parity error, etc.) while performing the command  |eO |        |  or during a self test.                                            |eO |--------+--------------------------------------------------------------------|eO |   5h   |  ILLEGAL REQUEST.  Indicates that there was an illegal parameter in|.O |        |  the command descriptor block or in the additional parameters      |cO |        |  supplied as data for some commands (FORMAT UNIT, SEARCH DATA,     |IO |        |  etc.).  If the target detects an invalid parameter in the command |oO |        |  descriptor block, then it shall terminate the command without     |=O |        |  altering the medium.  If the target detects an invalid parameter  | O |        |  in the additional parameters supplied as data, then the target may| O |        |  have already altered the medium.  This sense key may also indicate|=O |        |  that an invalid IDENTIFY message was received (6.6.7).            | O |--------+--------------------------------------------------------------------|-O |   6h   |  UNIT ATTENTION.  Indicates that the removable medium may have been| O |        |  changed or the target has been reset.  See 7.9 for more detailed  | O |        |  information about the unit attention condition.                   | O |--------+--------------------------------------------------------------------|=O |   7h   |  DATA PROTECT.  Indicates that a command that reads or writes the  |nO |        |  medium was attempted on a block that is protected from this       |aO |        |  operation.  The read or write operation is not performed.         |pO +=============================================================================+I    ;                   Table 70 - Sense key (8h-Fh) descriptionsHO +========-====================================================================+,O | Sense  |  Description                                                       | O |  key   |                                                                    |eO |--------+--------------------------------------------------------------------|2O |   8h   |  BLANK CHECK.  Indicates that a write-once device or a sequential- |TO |        |  access device encountered blank medium or format-defined end-of-  |hO |        |  data indication while reading or a write-once device encountered a|rO |        |  non-blank medium while writing.                                   |tO |--------+--------------------------------------------------------------------| O |   9h   |  VENDOR-SPECIFIC.  This sense key is available for reporting vendor| O |        |  specific conditions.                                              | O |--------+--------------------------------------------------------------------|KO |   Ah   |  COPY ABORTED.  Indicates a COPY, COMPARE, or COPY AND VERIFY      |tO |        |  command was aborted due to an error condition on the source       |aO |        |  device, the destination device, or both.  (See 8.2.3.2 for        |wO |        |  additional information about this sense key.)                     |pO |--------+--------------------------------------------------------------------| O |   Bh   |  ABORTED COMMAND.  Indicates that the target aborted the command.  |hO |        |  The initiator may be able to recover by trying the command again. |tO |--------+--------------------------------------------------------------------| O |   Ch   |  EQUAL.  Indicates a SEARCH DATA command has satisfied an equal    |sO |        |  comparison.                                                       |uO |--------+--------------------------------------------------------------------|HO |   Dh   |  VOLUME OVERFLOW.  Indicates that a buffered peripheral device has | O |        |  reached the end-of-partition and data may remain in the buffer    |eO |        |  that has not been written to the medium.  A RECOVER BUFFERED DATA |tO |        |  command(s) may be issued to read the unwritten data from the      | O |        |  buffer.                                                           | O |--------+--------------------------------------------------------------------| O |   Eh   |  MISCOMPARE.  Indicates that the source data did not match the data|cO |        |  read from the medium.                                             |eO |--------+--------------------------------------------------------------------| O |   Fh   |  RESERVED.                                                         |qO +=============================================================================+o    C The additional sense codes and additional sense code qualifiers are  defined in table 71.  8                      Table 71 - ASC and ASCQ assignmentsO +=============================================================================+uO |           D - DIRECT ACCESS DEVICE                                          |mO |           .T - SEQUENTIAL ACCESS DEVICE                                     |dO |           . L - PRINTER DEVICE                                              |tO |           .  P - PROCESSOR DEVICE                                           |bO |           .  .W - WRITE ONCE READ MULTIPLE DEVICE                           |dO |           .  . R - READ ONLY (CD-ROM) DEVICE                                |iO |           .  .  S - SCANNER DEVICE                                          |eO |           .  .  .O - OPTICAL MEMORY DEVICE                                  |eO |           .  .  . M - MEDIA CHANGER DEVICE                                  | O |           .  .  .  C - COMMUNICATION DEVICE                                 | O |           .  .  .  .                                                        |tO | ASC ASCQ  DTLPWRSOMC  DESCRIPTION                                           | O | --- ----              ----------------------------------------------------- |oO | 13h  00h  D   W  O    ADDRESS MARK NOT FOUND FOR DATA FIELD                 |nO | 12h  00h  D   W  O    ADDRESS MARK NOT FOUND FOR ID FIELD                   |mO | 00h  11h       R      AUDIO PLAY OPERATION IN PROGRESS                      | O | 00h  12h       R      AUDIO PLAY OPERATION PAUSED                           |hO | 00h  14h       R      AUDIO PLAY OPERATION STOPPED DUE TO ERROR             |eO | 00h  13h       R      AUDIO PLAY OPERATION SUCCESSFULLY COMPLETED           |aO | 00h  04h   T    S     BEGINNING-OF-PARTITION/MEDIUM DETECTED                |eO | 14h  04h   T          BLOCK SEQUENCE ERROR                                  | O | 30h  02h  DT  WR O    CANNOT READ MEDIUM - INCOMPATIBLE FORMAT              | O | 30h  01h  DT  WR O    CANNOT READ MEDIUM - UNKNOWN FORMAT                   | O | 52h  00h   T          CARTRIDGE FAULT                                       | O | 3Fh  02h  DTLPWRSOMC  CHANGED OPERATING DEFINITION                          |hO | 11h  06h      WR O    CIRC UNRECOVERED ERROR                                |hO | 30h  03h  DT          CLEANING CARTRIDGE INSTALLED                          |tO | 4Ah  00h  DTLPWRSOMC  COMMAND PHASE ERROR                                   | O | 2Ch  00h  DTLPWRSOMC  COMMAND SEQUENCE ERROR                                |zO | 2Fh  00h  DTLPWRSOMC  COMMANDS CLEARED BY ANOTHER INITIATOR                 |hO | 2Bh  00h  DTLPWRSO C  COPY CANNOT EXECUTE SINCE HOST CANNOT DISCONNECT      |tO | 41h  00h  D           DATA PATH FAILURE (SHOULD USE 40 NN)                  |mO | 4Bh  00h  DTLPWRSOMC  DATA PHASE ERROR                                      | O | 11h  07h      W  O    DATA RESYNCHRONIZATION ERROR                          |eO | 16h  00h  D   W  O    DATA SYNCHRONIZATION MARK ERROR                       | O | 19h  00h  D      O    DEFECT LIST ERROR                                     |aO | 19h  03h  D      O    DEFECT LIST ERROR IN GROWN LIST                       |)O | 19h  02h  D      O    DEFECT LIST ERROR IN PRIMARY LIST                     |=O | 19h  01h  D      O    DEFECT LIST NOT AVAILABLE                             | O | 1Ch  00h  D      O    DEFECT LIST NOT FOUND                                 | O | 32h  01h  D   W  O    DEFECT LIST UPDATE FAILURE                            |-O | 40h  NNh  DTLPWRSOMC  DIAGNOSTIC FAILURE ON COMPONENT NN (80H-FFH)          |kO | 63h  00h       R      END OF USER AREA ENCOUNTERED ON THIS TRACK            | O | 00h  05h   T    S     END-OF-DATA DETECTED                                  |nO | 14h  03h   T          END-OF-DATA NOT FOUND                                 | O | 00h  02h   T    S     END-OF-PARTITION/MEDIUM DETECTED                      | O | 51h  00h   T     O    ERASE FAILURE                                         |-O | 0Ah  00h  DTLPWRSOMC  ERROR LOG OVERFLOW                                    |pO | 11h  02h  DT  W SO    ERROR TOO LONG TO CORRECT                             |hO | 03h  02h   T          EXCESSIVE WRITE ERRORS                                |aO | 3Bh  07h    L         FAILED TO SENSE BOTTOM-OF-FORM                        |eO | 3Bh  06h    L         FAILED TO SENSE TOP-OF-FORM                           |oO | 00h  01h   T          FILEMARK DETECTED                                     | O | 14h  02h   T          FILEMARK OR SETMARK NOT FOUND                         |-O | 09h  02h      WR O    FOCUS SERVO FAILURE                                   | O | 31h  01h  D L    O    FORMAT COMMAND FAILED                                 |oO | 58h  00h         O    GENERATION DOES NOT EXIST                             | O +=============================================================================+-     Table 71  (continued) O +=============================================================================+ O | ASC ASCQ  DTLPWRSOMC  DESCRIPTION                                           | O | --- ----              ----------------------------------------------------- | O | 1Ch  02h  D      O    GROWN DEFECT LIST NOT FOUND                           | O | 00h  06h  DTLPWRSOMC  I/O PROCESS TERMINATED                                |-O | 10h  00h  D   W  O    ID CRC OR ECC ERROR                                   | O | 22h  00h  D           ILLEGAL FUNCTION (SHOULD USE 20 00, 24 00, OR 26 00)  | O | 64h  00h       R      ILLEGAL MODE FOR THIS TRACK                           | O | 28h  01h          M   IMPORT OR EXPORT ELEMENT ACCESSED                     | O | 30h  00h  DT  WR OM   INCOMPATIBLE MEDIUM INSTALLED                         |-O | 11h  08h   T          INCOMPLETE BLOCK READ                                 | O | 48h  00h  DTLPWRSOMC  INITIATOR DETECTED ERROR MESSAGE RECEIVED             | O | 3Fh  03h  DTLPWRSOMC  INQUIRY DATA HAS CHANGED                              | O | 44h  00h  DTLPWRSOMC  INTERNAL TARGET FAILURE                               | O | 3Dh  00h  DTLPWRSOMC  INVALID BITS IN IDENTIFY MESSAGE                      | O | 2Ch  02h        S     INVALID COMBINATION OF WINDOWS SPECIFIED              | O | 20h  00h  DTLPWRSOMC  INVALID COMMAND OPERATION CODE                        | O | 21h  01h          M   INVALID ELEMENT ADDRESS                               | O | 24h  00h  DTLPWRSOMC  INVALID FIELD IN CDB                                  | O | 26h  00h  DTLPWRSOMC  INVALID FIELD IN PARAMETER LIST                       |-O | 49h  00h  DTLPWRSOMC  INVALID MESSAGE ERROR                                 | O | 11h  05h      WR O    L-EC UNCORRECTABLE ERROR                              | O | 60h  00h        S     LAMP FAILURE                                          | O | 5Bh  02h  DTLPWRSOM   LOG COUNTER AT MAXIMUM                                |-O | 5Bh  00h  DTLPWRSOM   LOG EXCEPTION                                         | O | 5Bh  03h  DTLPWRSOM   LOG LIST CODES EXHAUSTED                              | O | 2Ah  02h  DTL WRSOMC  LOG PARAMETERS CHANGED                                | O | 21h  00h  DT  WR OM   LOGICAL BLOCK ADDRESS OUT OF RANGE                    |=O | 08h  00h  DTL WRSOMC  LOGICAL UNIT COMMUNICATION FAILURE                    | O | 08h  02h  DTL WRSOMC  LOGICAL UNIT COMMUNICATION PARITY ERROR               |=O | 08h  01h  DTL WRSOMC  LOGICAL UNIT COMMUNICATION TIME-OUT                   | Q  | 05h  00h  DTLPWRSOMC  LOGICAL UNIT DOES NOT RESPOND TO SELECTION            |  O | 4Ch  00h  DTLPWRSOMC  LOGICAL UNIT FAILED SELF-CONFIGURATION                |-O | 3Eh  00h  DTLPWRSOMC  LOGICAL UNIT HAS NOT SELF-CONFIGURED YET              |iO | 04h  01h  DTLPWRSOMC  LOGICAL UNIT IS IN PROCESS OF BECOMING READY          |oO | 04h  00h  DTLPWRSOMC  LOGICAL UNIT NOT READY, CAUSE NOT REPORTABLE          |hO | 04h  04h  DTL    O    LOGICAL UNIT NOT READY, FORMAT IN PROGRESS            |wO | 04h  02h  DTLPWRSOMC  LOGICAL UNIT NOT READY, INITIALIZING COMMAND REQUIRED |-O | 04h  03h  DTLPWRSOMC  LOGICAL UNIT NOT READY, MANUAL INTERVENTION REQUIRED  | O | 25h  00h  DTLPWRSOMC  LOGICAL UNIT NOT SUPPORTED                            |nO | 15h  01h  DTL WRSOM   MECHANICAL POSITIONING ERROR                          |-O | 53h  00h  DTL WRSOM   MEDIA LOAD OR EJECT FAILED                            |dO | 3Bh  0Dh          M   MEDIUM DESTINATION ELEMENT FULL                       |eO | 31h  00h  DT  W  O    MEDIUM FORMAT CORRUPTED                               |nO | 3Ah  00h  DTL WRSOM   MEDIUM NOT PRESENT                                    |aO | 53h  02h  DT  WR OM   MEDIUM REMOVAL PREVENTED                              |-O | 3Bh  0Eh          M   MEDIUM SOURCE ELEMENT EMPTY                           | O | 43h  00h  DTLPWRSOMC  MESSAGE ERROR                                         | O | 3Fh  01h  DTLPWRSOMC  MICROCODE HAS BEEN CHANGED                            |-O | 1Dh  00h  D   W  O    MISCOMPARE DURING VERIFY OPERATION                    | O | 11h  0Ah  DT     O    MISCORRECTED ERROR                                    | O | 2Ah  01h  DTL WRSOMC  MODE PARAMETERS CHANGED                               |-O | 07h  00h  DTL WRSOM   MULTIPLE PERIPHERAL DEVICES SELECTED                  | O | 11h  03h  DT  W SO    MULTIPLE READ ERRORS                                  |fO | 00h  00h  DTLPWRSOMC  NO ADDITIONAL SENSE INFORMATION                       | O | 00h  15h       R      NO CURRENT AUDIO STATUS TO RETURN                     | O | 32h  00h  D   W  O    NO DEFECT SPARE LOCATION AVAILABLE                    | O | 11h  09h   T          NO GAP FOUND                                          |-O | 01h  00h  D   W  O    NO INDEX/SECTOR SIGNAL                                |cO | 06h  00h  D   WR OM   NO REFERENCE POSITION FOUND                           |iO +=============================================================================+-     Table 71  (continued)-O +=============================================================================+ O | ASC ASCQ  DTLPWRSOMC  DESCRIPTION                                           |=O | --- ----              ----------------------------------------------------- |qO | 02h  00h  D   WR OM   NO SEEK COMPLETE                                      |SO | 03h  01h   T          NO WRITE CURRENT                                      |=O | 28h  00h  DTLPWRSOMC  NOT READY TO READY TRANSITION, MEDIUM MAY HAVE CHANGED| O | 5Ah  01h  DT  WR OM   OPERATOR MEDIUM REMOVAL REQUEST                       | O | 5Ah  00h  DTLPWRSOM   OPERATOR REQUEST OR STATE CHANGE INPUT (UNSPECIFIED)  | O | 5Ah  03h  DT  W  O    OPERATOR SELECTED WRITE PERMIT                        | O | 5Ah  02h  DT  W  O    OPERATOR SELECTED WRITE PROTECT                       | O | 61h  02h        S     OUT OF FOCUS                                          | O | 4Eh  00h  DTLPWRSOMC  OVERLAPPED COMMANDS ATTEMPTED                         | O | 2Dh  00h   T          OVERWRITE ERROR ON UPDATE IN PLACE                    | O | 3Bh  05h    L         PAPER JAM                                             | O | 1Ah  00h  DTLPWRSOMC  PARAMETER LIST LENGTH ERROR                           | O | 26h  01h  DTLPWRSOMC  PARAMETER NOT SUPPORTED                               | O | 26h  02h  DTLPWRSOMC  PARAMETER VALUE INVALID                               | O | 2Ah  00h  DTL WRSOMC  PARAMETERS CHANGED                                    |-O | 03h  00h  DTL W SO    PERIPHERAL DEVICE WRITE FAULT                         | O | 50h  02h   T          POSITION ERROR RELATED TO TIMING                      | O | 3Bh  0Ch        S     POSITION PAST BEGINNING OF MEDIUM                     | O | 3Bh  0Bh        S     POSITION PAST END OF MEDIUM                           | O | 15h  02h  DT  WR O    POSITIONING ERROR DETECTED BY READ OF MEDIUM          | O | 29h  00h  DTLPWRSOMC  POWER ON, RESET, OR BUS DEVICE RESET OCCURRED         |EO | 42h  00h  D           POWER-ON OR SELF-TEST FAILURE (SHOULD USE 40 NN)      | O | 1Ch  01h  D      O    PRIMARY DEFECT LIST NOT FOUND                         | O | 40h  00h  D           RAM FAILURE (SHOULD USE 40 NN)                        | O | 15h  00h  DTL WRSOM   RANDOM POSITIONING ERROR                              | O | 3Bh  0Ah        S     READ PAST BEGINNING OF MEDIUM                         | O | 3Bh  09h        S     READ PAST END OF MEDIUM                               | O | 11h  01h  DT  W SO    READ RETRIES EXHAUSTED                                | O | 14h  01h  DT  WR O    RECORD NOT FOUND                                      | O | 14h  00h  DTL WRSO    RECORDED ENTITY NOT FOUND                             | O | 18h  02h  D   WR O    RECOVERED DATA - DATA AUTO-REALLOCATED                | O | 18h  05h  D   WR O    RECOVERED DATA - RECOMMEND REASSIGNMENT               | O | 18h  06h  D   WR O    RECOVERED DATA - RECOMMEND REWRITE                    |CO | 17h  05h  D   WR O    RECOVERED DATA USING PREVIOUS SECTOR ID               | O | 18h  03h       R      RECOVERED DATA WITH CIRC                              | O | 18h  01h  D   WR O    RECOVERED DATA WITH ERROR CORRECTION & RETRIES APPLIED| O | 18h  00h  DT  WR O    RECOVERED DATA WITH ERROR CORRECTION APPLIED          | O | 18h  04h       R      RECOVERED DATA WITH L-EC                              | O | 17h  03h  DT  WR O    RECOVERED DATA WITH NEGATIVE HEAD OFFSET              | O | 17h  00h  DT  WRSO    RECOVERED DATA WITH NO ERROR CORRECTION APPLIED       | O | 17h  02h  DT  WR O    RECOVERED DATA WITH POSITIVE HEAD OFFSET              | O | 17h  01h  DT  WRSO    RECOVERED DATA WITH RETRIES                           | O | 17h  04h      WR O    RECOVERED DATA WITH RETRIES AND/OR CIRC APPLIED       | O | 17h  06h  D   W  O    RECOVERED DATA WITHOUT ECC - DATA AUTO-REALLOCATED    |FO | 17h  07h  D   W  O    RECOVERED DATA WITHOUT ECC - RECOMMEND REASSIGNMENT   |KO | 17h  08h  D   W  O    RECOVERED DATA WITHOUT ECC - RECOMMEND REWRITE        | O | 1Eh  00h  D   W  O    RECOVERED ID WITH ECC CORRECTION                      | O | 3Bh  08h   T          REPOSITION ERROR                                      | O | 36h  00h    L         RIBBON, INK, OR TONER FAILURE                         | O | 37h  00h  DTL WRSOMC  ROUNDED PARAMETER                                     | O | 5Ch  00h  D      O    RPL STATUS CHANGE                                     | O | 39h  00h  DTL WRSOMC  SAVING PARAMETERS NOT SUPPORTED                       | O | 62h  00h        S     SCAN HEAD POSITIONING ERROR                           | O | 47h  00h  DTLPWRSOMC  SCSI PARITY ERROR                                     | O | 54h  00h     P        SCSI TO HOST SYSTEM INTERFACE FAILURE                 | O | 45h  00h  DTLPWRSOMC  SELECT OR RESELECT FAILURE                            | O +=============================================================================+      Table 71  (concluded) O +=============================================================================+ O | ASC ASCQ  DTLPWRSOMC  DESCRIPTION                                           |=O | --- ----              ----------------------------------------------------- |1O | 3Bh  00h   TL         SEQUENTIAL POSITIONING ERROR                          |=O | 00h  03h   T          SETMARK DETECTED                                      | O | 3Bh  04h    L         SLEW FAILURE                                          |-O | 09h  03h      WR O    SPINDLE SERVO FAILURE                                 | O | 5Ch  02h  D      O    SPINDLES NOT SYNCHRONIZED                             | O | 5Ch  01h  D      O    SPINDLES SYNCHRONIZED                                 | O | 1Bh  00h  DTLPWRSOMC  SYNCHRONOUS DATA TRANSFER ERROR                       |,O | 55h  00h     P        SYSTEM RESOURCE FAILURE                               | O | 33h  00h   T          TAPE LENGTH ERROR                                     | O | 3Bh  03h    L         TAPE OR ELECTRONIC VERTICAL FORMS UNIT NOT READY      | O | 3Bh  01h   T          TAPE POSITION ERROR AT BEGINNING-OF-MEDIUM            | O | 3Bh  02h   T          TAPE POSITION ERROR AT END-OF-MEDIUM                  | O | 3Fh  00h  DTLPWRSOMC  TARGET OPERATING CONDITIONS HAVE CHANGED              | O | 5Bh  01h  DTLPWRSOM   THRESHOLD CONDITION MET                               | O | 26h  03h  DTLPWRSOMC  THRESHOLD PARAMETERS NOT SUPPORTED                    | O | 2Ch  01h        S     TOO MANY WINDOWS SPECIFIED                            | O | 09h  00h  DT  WR O    TRACK FOLLOWING ERROR                                 | O | 09h  01h      WR O    TRACKING SERVO FAILURE                                | O | 61h  01h        S     UNABLE TO ACQUIRE VIDEO                               | O | 57h  00h       R      UNABLE TO RECOVER TABLE-OF-CONTENTS                   | O | 53h  01h   T          UNLOAD TAPE FAILURE                                   | O | 11h  00h  DT  WRSO    UNRECOVERED READ ERROR                                | O | 11h  04h  D   W  O    UNRECOVERED READ ERROR - AUTO REALLOCATE FAILED       | O | 11h  0Bh  D   W  O    UNRECOVERED READ ERROR - RECOMMEND REASSIGNMENT       | O | 11h  0Ch  D   W  O    UNRECOVERED READ ERROR - RECOMMEND REWRITE THE DATA   | O | 46h  00h  DTLPWRSOMC  UNSUCCESSFUL SOFT RESET                               | O | 59h  00h         O    UPDATED BLOCK READ                                    | O | 61h  00h        S     VIDEO ACQUISITION ERROR                               | O | 50h  00h   T          WRITE APPEND ERROR                                    | O | 50h  01h   T          WRITE APPEND POSITION ERROR                           | O | 0Ch  00h   T    S     WRITE ERROR                                           | O | 0Ch  02h  D   W  O    WRITE ERROR - AUTO REALLOCATION FAILED                |OO | 0Ch  01h  D   W  O    WRITE ERROR RECOVERED WITH AUTO REALLOCATION          | O | 27h  00h  DT  W  O    WRITE PROTECTED                                       |TO |                                                                             |RO | 80h  XXh     \                                                              |TO | THROUGH       >       Vendor-specific.                                      |EO | FFh  XX      /                                                              |MO |                                                                             |TO | XXh  80h     \                                                              | O | THROUGH       >       Vendor-specific QUALIFICATION OF STANDARD ASC.        | O | XXh  FFh     /                                                              | O |                       ALL CODES NOT SHOWN ARE RESERVED.                     | O |-----------------------------------------------------------------------------| O |NOTE - Annex D contains the ASC and ASCQ assignments in numeric order.       | O +=============================================================================+        8.2.15 SEND DIAGNOSTIC Command  I The SEND DIAGNOSTIC command (see table 72) requests the target to performPF diagnostic operations on itself, on the logical unit, or on both.  TheF only mandatory implementation of this command is the self-test featureI with the parameter list length of zero.  Except when the self-test bit is E one, this command is usually followed by a RECEIVE DIAGNOSTIC RESULTS  command.  8                       Table 72 - SEND DIAGNOSTIC commandO +=====-========-========-========-========-========-========-========-========+EO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |MO |=====+=======================================================================|OO | 0   |                           Operation code (1Dh)                        |AO |-----+-----------------------------------------------------------------------| O | 1   | Logical unit number      |   PF   |Reserved|SelfTest| DevOfL | UnitOfL| O |-----+-----------------------------------------------------------------------|NO | 2   |                           Reserved                                    |=O |-----+-----------------------------------------------------------------------|=O | 3   | (MSB)                                                                 |CO |-----+---                        Parameter list length                    ---| O | 4   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------| O | 5   |                           Control                                     |CO +=============================================================================+     @ A page format (PF) bit of one specifies that the SEND DIAGNOSTIC= parameters conform to the page structure as specified in thisEG International Standard.  The implementation of the PF bit is optional.  D See 87.3.1 for the definition of diagnostic pages.  A PF bit of zeroH indicates that the SEND DIAGNOSTIC parameters are as specified in SCSI-1* (i.e. all parameters are vendor-specific).  D A self-test (SelfTest) bit of one directs the target to complete itsE default self-test.  If the self-test successfully passes, the command E shall be terminated with GOOD status; otherwise, the command shall be H terminated with CHECK CONDITION status and the sense key shall be set to HARDWARE ERROR.   G A self-test bit of zero requests that the target perform the diagnostic J operation specified in the parameter list.  The diagnostic operation mightE or might not require a target to return data that contains diagnostic J results.  If the return of data is not required, the return of GOOD statusD indicates successful completion of the diagnostic operation.  If the4 return of data is required, the target shall either:L    a)     perform the requested diagnostic operation, prepare the data to beI           returned and indicate completion by returning GOOD status.  The N           initiator issues a RECEIVE DIAGNOSTIC RESULTS command to recover the           data;0I    b)     accept the parameter list, and if no errors are detected in the G           parameter list, return GOOD status.  The requested diagnostic F           operation and the preparation of the data to be returned areI           performed upon receipt of a RECEIVE DIAGNOSTIC RESULTS command.   M    NOTE 92 To insure that the diagnostic command information is not destroyed O    by a command sent from another initiator, either the SEND DIAGNOSTIC command L    should be linked to the RECEIVE DIAGNOSTIC RESULTS command or the logical    unit should be reserved.1  A The device off-line (DevOfL) and unit off-line (UnitOfL) bits are G generally set by operating system software, while the parameter list is I prepared by diagnostic application software.  These bits grant permission G to perform vendor-specific diagnostic operations on the target that mayRG be visible to attached initiators.  Thus, by preventing operations thatCI are not enabled by these bits, the target assists the operating system inA protecting its resources.   J A UnitOfL bit of one grants permission to the target to perform diagnosticJ operations that may affect the user accessible medium on the logical unit,H e.g. write operations to the user accessible medium, or repositioning ofC the medium on sequential access devices.  The implementation of theAH UnitOfl bit is optional.  A UnitOfL bit of zero prohibits any diagnostic> operations that may be detected by subsequent I/O processes.    I A DevOfl bit of one grants permission to the target to perform diagnostic B operations that may affect all the logical units on a target, e.g.> alteration of reservations, log parameters, or sense data. TheC implementation of the DevOfl bit is optional.  A DevOfL bit of zero F prohibits diagnostic operations that may be detected by subsequent I/O
 processes.  D The parameter list length field specifies the length in bytes of theK parameter list that shall be transferred from the initiator to the target. E? A parameter list length of zero indicates that no data shall be E transferred. This condition shall not be considered an error.  If the H specified parameter list length results in the truncation of one or moreH pages (PF bit set to one) the target shall return CHECK CONDITION statusC with a sense key of ILLEGAL REQUEST and an additional sense code of  INVALID FIELD IN CDB.  7  C See note 83 under the RECEIVE DIAGNOSTIC RESULTS command in 8.2.13.    8.2.16 TEST UNIT READY Command  G The TEST UNIT READY command (see table 73) provides a means to check ifCJ the logical unit is ready.  This is not a request for a self-test.  If theF logical unit would accept an appropriate medium-access command withoutK returning CHECK CONDITION status, this command shall return a GOOD status.  H If the logical unit cannot become operational or is in a state such thatJ an initiator action (e.g. START UNIT command) is required to make the unitI ready, the target shall return CHECK CONDITION status with a sense key of=
 NOT READY.  8                       Table 73 - TEST UNIT READY commandO +=====-========-========-========-========-========-========-========-========+EO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |-O |Byte |        |        |        |        |        |        |        |        |EO |=====+=======================================================================|EO | 0   |                           Operation code (00h)                        |LO |-----+-----------------------------------------------------------------------|PO | 1   | Logical unit number      |                  Reserved                  |PO |-----+-----------------------------------------------------------------------|PO | 2   |                           Reserved                                    |YO |-----+-----------------------------------------------------------------------|YO | 3   |                           Reserved                                    |AO |-----+-----------------------------------------------------------------------|AO | 4   |                           Reserved                                    |AO |-----+-----------------------------------------------------------------------|AO | 5   |                           Control                                     |AO +=============================================================================+H    H Table 74 defines the preferred responses to the TEST UNIT READY command.F Higher-priority responses (e.g. BUSY or RESERVATION CONFLICT) are also
 permitted.  >                 Table 74 - Preferred TEST UNIT READY responsesO +=================-=================-=========================================+0O |      Status     |    Sense key    |             ASC and ASCQ                |0O |-----------------+-----------------+-----------------------------------------|0O | GOOD            | NO SENSE        | NO ADDITIONAL SENSE INFORMATION or      |0O |                 |                 |    other valid additional sense code.   |0O |-----------------+-----------------+-----------------------------------------|0O | CHECK CONDITION | ILLEGAL REQUEST | LOGICAL UNIT NOT SUPPORTED              |0O |                 |                 |                                         |0O |-----------------+-----------------+-----------------------------------------|0O | CHECK CONDITION | NOT READY       | LOGICAL UNIT DOES NOT RESPOND           |0O |                 |                 |    TO SELECTION                         |0O |-----------------+-----------------+-----------------------------------------|0O | CHECK CONDITION | NOT READY       | MEDIUM NOT PRESENT                      |0O |                 |                 |                                         |0O |-----------------+-----------------+-----------------------------------------|0O | CHECK CONDITION | NOT READY       | LOGICAL UNIT NOT READY,                 |0O |                 |                 |    CAUSE NOT REPORTABLE                 |0O |-----------------+-----------------+-----------------------------------------| O | CHECK CONDITION | NOT READY       | LOGICAL UNIT IS IN PROCESS              |XO |                 |                 |    OF BECOMING READY                    |GO |-----------------+-----------------+-----------------------------------------|XO | CHECK CONDITION | NOT READY       | LOGICAL UNIT NOT READY,                 | O |                 |                 |    INITIALIZING COMMAND REQUIRED        |8O |-----------------+-----------------+-----------------------------------------|GO | CHECK CONDITION | NOT READY       | LOGICAL UNIT NOT READY,                 |FO |                 |                 |    MANUAL INTERVENTION REQUIRED         | O |-----------------+-----------------+-----------------------------------------|-O | CHECK CONDITION | NOT READY       | LOGICAL UNIT NOT READY,                 | O |                 |                 |    FORMAT IN PROGRESS                   |=O +=============================================================================+.     8.2.17 WRITE BUFFER commandh  G The WRITE BUFFER command (see table 75) is used in conjunction with theiJ READ BUFFER command as a diagnostic for testing target memory and the SCSIG bus integrity.  Additional modes are provided for downloading microcodee) and for downloading and saving microcode.n  6                        Table 75 - WRITE BUFFER commandO +=====-========-========-========-========-========-========-========-========+-O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |=O |Byte |        |        |        |        |        |        |        |        |2O |=====+=======================================================================| O | 0   |                           Operation code (3Bh)                        |=O |-----+-----------------------------------------------------------------------| O | 1   | Logical unit number      |     Reserved    |          Mode            |-O |-----+-----------------------------------------------------------------------|fO | 2   |                           Buffer ID                                   |-O |-----+-----------------------------------------------------------------------| O | 3   | (MSB)                                                                 |-O |-----+---                                                                 ---| O | 4   |                           Buffer offset                               | O |-----+---                                                                 ---| O | 5   |                                                                 (LSB) |-O |-----+-----------------------------------------------------------------------| O | 6   | (MSB)                                                                 |=O |-----+---                                                                 ---|NO | 7   |                           Parameter list length                       |eO |-----+---                                                                 ---|fO | 8   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|-O | 9   |                           Control                                     |sO +=============================================================================+e    H This command shall not alter any medium of the target when the data mode4 or the combined header and data mode is specified.    I The function of this command and the meaning of fields within the commandrJ descriptor block depend on the contents of the mode field.  The mode field is defined in table 76.m  8                       Table 76 - WRITE BUFFER mode fieldG       +========-==================================-===================+OG       |  Mode  |  Description                     |  Implementation   |fG       |        |                                  |  requirements     |fG       |--------+----------------------------------+-------------------| G       |  000b  |  Write combined header and data  |  Optional         | G       |  001b  |  Vendor-specific                 |  Vendor-specific  | G       |  010b  |  Write data                      |  Optional         | G       |  011b  |  Reserved                        |  Reserved         |eG       |  100b  |  Download microcode              |  Optional         |bG       |  101b  |  Download microcode and save     |  Optional         |RG       |  110b  |  Reserved                        |  Reserved         |rG       |  111b  |  Reserved                        |  Reserved         |tG       +===============================================================+N    O    NOTE 93 Modes 000b and 001b are included for compatibility with CCS productslM    that were designed prior to the generation of this International Standard.sG    These products restrict the maximum transfer length to 65 535 bytes.i  - 8.2.17.1 Combined header and data mode (000b)o  H In this mode, data to be transferred is preceded by a four-byte header. G The four-byte header consists of all reserved bytes.  The buffer ID and H the buffer offset fields shall be zero.  The parameter list length fieldJ specifies the maximum number of bytes that shall be transferred during theG DATA OUT phase.  This number includes four bytes of header, so the dataeI length to be stored in the target's buffer is parameter list length minusmE four.  The initiator should attempt to ensure that the parameter listhG length is not greater than four plus the buffer capacity (see 8.2.12.1) I that is returned in the header of the READ BUFFER command (mode 00b).  If I the parameter list length exceeds the buffer capacity target shall returnoF CHECK CONDITION status and shall set the sense key to ILLEGAL REQUEST.  $ 8.2.17.2 Vendor-specific mode (001b)  H In this mode, the meaning of the buffer ID, buffer offset, and parameterD list length fields are not specified by this International Standard.   8.2.17.3 Data mode (010b)O  E In this mode, the DATA OUT phase contains buffer data.  The buffer IDyI field identifies a specific buffer within the target.  The vendor assignstF buffer ID codes to buffers within the target.  Buffer ID zero shall beF supported.  If more than one buffer is supported, additional buffer ID@ codes shall be assigned contiguously, beginning with one.  If anE unsupported buffer ID code is selected, the target shall return CHECK G CONDITION status and shall set the sense key to ILLEGAL REQUEST with ane. additional sense code of INVALID FIELD IN CDB.  H Data are written to the target buffer starting at the location specifiedJ by the buffer offset.  The initiator should conform to the offset boundaryF requirements returned in the READ BUFFER descriptor.  If the target isC unable to accept the specified buffer offset, it shall return CHECKdG CONDITION status and it shall set the sense key to ILLEGAL REQUEST withd1 an additional sense code of INVALID FIELD IN CDB.   J The parameter list length specifies the maximum number of bytes that shallF be transferred during the DATA OUT phase to be stored in the specifiedG buffer beginning at the buffer offset.  The initiator should attempt to E ensure that the parameter list length plus the buffer offset does not=I exceed the capacity of the specified buffer.  (The capacity of the buffer A can be determined by the buffer capacity field in the READ BUFFER-C descriptor.)  If the buffer offset and parameter list length fields J specify a transfer that would exceed the buffer capacity, the target shallD return CHECK CONDITION status and shall set the sense key to ILLEGAL? REQUEST with an additional sense code of INVALID FIELD IN CDB. -  ' 8.2.17.4 Download microcode mode (100b)-  G In this mode, vendor-specific microcode or control information shall be F transferred to the control memory space of the target.  After a power-F cycle or reset, the device operation shall revert to a vendor-specificG condition.  The meanings of the buffer ID, buffer offset, and parameter-G list length fields are not specified by this International Standard andeD are not required to be zero-filled.  When the microcode download hasA completed successfully the target shall generate a unit attention H condition for all initiators except the one that issued the WRITE BUFFERG command (see 7.9).  The additional sense code shall be set to MICROCODE- HAS BEEN CHANGED.   0 8.2.17.5 Download microcode and save mode (101b)  G In this mode, vendor-specific microcode or control information shall be=& transferred to the target and, if the H WRITE BUFFER command is completed successfully, also shall be saved in aJ non-volatile memory space (semiconductor, disk, or other).  The downloadedI code shall then be effective after each power-cycle and reset until it is=J supplanted in another download microcode and save operation.  The meaningsI of the buffer ID, buffer offset, and parameter list length fields are not-I specified by this International Standard and are not required to be zero-0C filled.  When the download microcode and save command has completedOF successfully the target shall generate a unit attention condition (seeC 7.9) for all initiators except the one that issued the WRITE BUFFER-G command.  When reporting the unit attention condition, the target shall < set the additional sense code to MICROCODE HAS BEEN CHANGED.  # 8.3 Parameters for all device types      8.3.1 Diagnostic parameters   I This subclause describes the diagnostic page structure and the diagnosticCF pages that are applicable to all SCSI devices.  Pages specific to eachD device type are described in the third subclause of each device-type clause (i.e. 9.3, 10.3, etc.).  F A SEND DIAGNOSTIC command with a PF bit of one specifies that the SENDG DIAGNOSTIC parameter list consists of zero or more diagnostic pages and C that the data returned by the subsequent RECEIVE DIAGNOSTIC RESULTS H command shall use the diagnostic page format (see table 77) described in this International Standard.  7                       Table 77 - Diagnostic page format O +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |-O |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================| O | 0   |                           Page code                                   |-O |-----+-----------------------------------------------------------------------| O | 1   |                           Reserved                                    |DO |-----+-----------------------------------------------------------------------|-O | 2   | (MSB)                                                                 | O |-----+---                        Page length (n-3)                        ---| O | 3   |                                                                 (LSB) |-O |-----+-----------------------------------------------------------------------| O | 4   |                                                                       | O |- - -+---                        Diagnostic parameters                    ---|=O | n   |                                                                       |lO +=============================================================================+e    J Each diagnostic page defines a function or operation that the target shallG perform.  The page contains a page header followed by the analysis data F that is formatted according to the page code specified in the previous SEND DIAGNOSTIC command.    E Targets that implement diagnostic pages are only required to accept a # single diagnostic page per command.0  E The page code field identifies which diagnostic page is being sent or 2 returned.  The page codes are defined in table 78.  7                        Table 78 - Diagnostic page codes O +=============-==================================================-============+-O |  Page code  |  Description                                     | Subclause  |aO |-------------+--------------------------------------------------+------------|-O |     00h     |  Supported diagnostics pages                     |  8.3.1.1   | O |  01h - 3Fh  |  Reserved (for all device type pages)            |            |-O |  40h - 7Fh  |  See specific device type for definition         |            | O |  80h - FFh  |  Vendor-specific pages                           |            | O +=============================================================================+     E The page length field specifies the length in bytes of the diagnostic-H parameters that follow this field.  If the initiator sends a page lengthA that results in the truncation of any parameter, the target shall G terminate the command with CHECK CONDITION status.  The sense key shall-G be set to ILLEGAL REQUEST with the additional sense code set to INVALID  FIELD IN PARAMETER LIST.  I The diagnostic parameters are defined for each page code.  The diagnostic H parameters within a page may be defined differently in a SEND DIAGNOSTIC5 command than in a RECEIVE DIAGNOSTIC RESULTS command.   " 8.3.1.1 Supported diagnostic pages  A The supported diagnostics page (see table 79) returns the list of ? diagnostic pages implemented by the target.  This page shall be-G implemented if the target implements the page format option of the SEND 3 DIAGNOSTIC and RECEIVE DIAGNOSTIC RESULTS commands.=  9                     Table 79 - Supported diagnostic pages=O +=====-========-========-========-========-========-========-========-========+eO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |mO |Byte |        |        |        |        |        |        |        |        |eO |=====+=======================================================================| O | 0   |                           Page code (00h)                             |=O |-----+-----------------------------------------------------------------------| O | 1   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|-O | 2   | (MSB)                                                                 | O |-----+---                        Page length (n-3)                        ---| O | 3   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------| O | 4   |                                                                       |nO |- - -+---                        Supported page list                      ---| O | n   |                                                                       | O +=============================================================================+=    I The definition of this page for the SEND DIAGNOSTIC command includes only G the first four bytes.  If the page length field is not zero, the targetrI shall terminate the SEND DIAGNOSTIC command with CHECK CONDITION status. mF The sense key shall be set to ILLEGAL REQUEST with an additional senseH code of INVALID FIELD IN PARAMETER LIST.  This page instructs the targetB to make available the list of all supported diagnostic pages to be= returned by a subsequent RECEIVE DIAGNOSTIC RESULTS command.    F The definition of this page for the RECEIVE DIAGNOSTIC RESULTS command> includes the list of diagnostic pages supported by the target.  D The page length field specifies the length in bytes of the following supported page list.  I The supported page list field shall contain a list of all diagnostic pagetF codes implemented by the target in ascending order beginning with page	 code 00h.    8.3.2 Log parameters  J This subclause describes the log page structure and the log pages that areG applicable to all SCSI devices.  Pages specific to each device type areTH described in the third subclause of each device-type clause (i.e. 9.3.2,H 10.3.2, etc.).  The LOG SELECT command supports the ability to send zeroC or more log pages.  The LOG SENSE command returns a single log pagehE specified in the page code field of the command descriptor block (seee 8.2.7).A  J Each log page begins with a four-byte page header followed by zero or moreJ variable-length log parameters defined for that page.  The log page format is defined in table 80.   4                           Table 80 - Log page formatQ +=======-========-========-========-========-========-========-========-========+iQ |    Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |CQ |Byte   |        |        |        |        |        |        |        |        |iQ |=======+=================+=====================================================|tQ | 0     |    Reserved     |            Page code                                |rQ |-------+-----------------------------------------------------------------------|tQ | 1     |                              Reserved                                 | Q |-------+-----------------------------------------------------------------------|oQ | 2     | (MSB)                                                                 | Q |-------+---                           Page length (n-3)                     ---|sQ | 3     |                                                                 (LSB) |dQ |=======+=======================================================================|=Q |       |                         Log parameters(s)                             |eQ |=======+=======================================================================|bQ | 4     |                              Log parameter (First)                    |dQ |- --- -+---                           (Length x)                            ---| Q | x+3   |                                                                       | Q |-------+-----------------------------------------------------------------------| Q |       |                                 .                                     | Q |       |                                 .                                     |oQ |-------+-----------------------------------------------------------------------|aQ | n-y+1 |                              Log parameter (Last)                     | Q |- --- -+---                           (Length y)                            ---|cQ | n     |                                                                       |eQ +===============================================================================+e    E The page code field identifies which log page is being transferred.  i  H The page length field specifies the length in bytes of the following logE parameters.  If the initiator sends a page length that results in theRH truncation of any parameter, the target shall terminate the command withF CHECK CONDITION status.  The sense key shall be set to ILLEGAL REQUESTF with the additional sense code set to INVALID FIELD IN PARAMETER LIST.  E Most log pages contain one or more special data structures called logeD parameters (see table 81).  Log parameters may be data counters thatI record a count of a particular event (or events) or log parameters may be E list parameters (strings) which contain a description of a particular  event.  3                            Table 81 - Log parametertO +=====-========-========-========-========-========-========-========-========+BO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |rO |=====+=======================================================================|tO | 0   | (MSB)                                                                 |lO |-----+---                        Parameter code                           ---|bO | 1   |                                                                 (LSB) |oO |-----+-----------------------------------------------------------------------|sO | 2   |   DU   |   DS   |  TSD   |   ETC  |       TMC       |Reserved|  LP    |eO |-----+-----------------------------------------------------------------------| O | 3   |                           Parameter length (n-3)                      |lO |-----+-----------------------------------------------------------------------|=O | 4   |                                                                       | O |- - -+---                        Parameter value                          ---| O | n   |                                                                       |=O +=============================================================================+     G Each log parameter begins with a four-byte parameter header followed by-* one or more bytes of parameter value data.  J The parameter code field identifies the log parameter is being transferred for that log page.    H The DU, DS, TSD, ETC, TMC, and LP fields are collectively referred to as> the parameter control byte.  These fields are described below.  I For cumulative log parameter values (indicated by the PC field of the LOG G SELECT and LOG SENSE command descriptor block), the disable update (DU)  bit is defined as follows:E    a)     A zero value indicates that the target shall update the log L           parameter value to reflect all events that should be noted by that           parameter.  H    b)     A one value indicates that the target shall not update the logI           parameter value except in response to a LOG SELECT command that=2           specifies a new value for the parameter.  J    NOTE 94 When updating cumulative log parameter values, a target may useO    volatile memory to hold these values until a LOG SELECT or LOG SENSE commandsN    is received with an SP bit of one (or a target-defined event occurs).  ThusK    the updated cumulative log parameter values may be lost if a power cyclen
    occurs.  I The DU bit is not defined for threshold values (indicated by the PC fieldnB of the LOG SENSE command descriptor block) nor for list parametersG (indicated by the LP bit).  The target shall ignore the value of any DUo bits in a LOG SELECT command.=  I A disable save (DS) bit of zero indicates that the target supports savingoH for that log parameter.  The target shall save the current cumulative orG the current threshold parameter value (depending on the value in the PC-I field of the command descriptor block) in response to a LOG SELECT or LOG.H SENSE command with an SP bit of one.  A DS bit of one indicates that theF target does not support saving that log parameter in response to a LOG2 SELECT or LOG SENSE command with an SP bit of one.  J A target save disable (TSD) bit of zero indicates that the target providesH a target-defined method for saving log parameters.  This implicit savingG operation shall be done frequently enough to insure that the cumulativeeC parameter values retain statistical significance (i.e. across powertD cycles).  A TSD bit of one indicates that either the target does notH provide a target-defined method for saving log parameters or the target-2 defined method has been disabled by the initiator.  @ An enable threshold comparison (ETC) bit of one indicates that aF comparison to the threshold value is performed whenever the cumulativeH value is updated.  An ETC bit of zero indicates that a comparison is notC performed.  The value of the ETC bit is the same for cumulative andg threshold parameters.g  G The threshold met criteria (TMC) field (see table 82) defines the basistH for comparison of the cumulative and threshold values.  The TMC field isI valid only if the ETC bit is one.  The value of the TMC field is the sameE( for cumulative and threshold parameters.  7                       Table 82 - Threshold met criteria=< +========-=================================================+< |  Code  |  Basis for comparison                           |< |--------+-------------------------------------------------|< |   00b  |  Every update of the cumulative value           |< |   01b  |  Cumulative value     equal    threshold value  |< |   10b  |  Cumulative value   not equal  threshold value  |< |   11b  |  Cumulative value greater than threshold value  |< +==========================================================+    F If the ETC bit is one and the result of the comparison is true, a unitJ attention condition shall be generated for all initiators.  When reportingH the unit attention condition, the target shall set the sense key to UNITG ATTENTION and set the additional sense code to THRESHOLD CONDITION MET.   G The list parameter (LP) bit indicates the format of the log parameter. LH If an initiator attempts to set the value of the LP bit to a value otherJ than the one returned for the same parameter in the LOG SENSE command, theJ target shall terminate the command with CHECK CONDITION status.  The senseI key shall be set to ILLEGAL REQUEST with the additional sense code set to   INVALID FIELD IN PARAMETER LIST.  G An LP bit of zero indicates that the parameter is a data counter.  Data=E counters are associated with one of more events;  the data counter isnJ updated whenever one of these events occurs by incrementing of the counterC value. If each data counter has associated with it a target-definedNH maximum value.  Upon reaching this maximum value, the data counter shallH not be incremented (i.e. it does not wrap).  When a data counter reachesI its maximum value, the target shall set the associated DU bit to one.  IfsH the data counter is at or reaches its maximum value during the executionD of a command, the target shall complete the command.  If the commandE completes correctly (except for the data counter being at its maximum G value) and if the RLEC bit of the control mode page (8.3.3.1) is set toeE one; then the target shall terminate the command with CHECK CONDITIONlI status and set the sense key to RECOVERED ERROR with the additional sensen% code set to LOG COUNTER AT MAXIMUM.     H An LP bit of one indicates that the parameter is a list parameter.  ListH parameters are not counters and thus the ETC and TMC fields shall be setH to zero.  A list parameter is a string of ASCII graphic codes (i.e. code values 20h through 7Eh).  D If more than one list parameter is defined in a single log page, the3 following rules apply to assigning parameter codes:pL    a)     The parameter updated last shall have a higher parameter code than?           the previous parameter, except as defined in rule b).lJ    b)     When the maximum parameter code value supported by the target isM           reached, the target shall assign the lowest parameter code value tolL           the next log parameter (i.e. wrap-around parameter codes).  If theJ           associated command completes correctly (except for the parameterM           code being at its maximum value) and if the RLEC bit of the control L           mode page (8.3.3.1) is set to one; then the target shall terminateJ           the command with CHECK CONDITION status and set the sense key toN           RECOVERED ERROR with the additional sense code set to LOG LIST CODES           EXHAUSTED.  J    NOTE 95 List parameters can be used to store the locations of defectiveP    blocks in the following manner.  When a defective block is identified, a listN    parameter is updated to reflect the location and cause of the defect.  WhenJ    the next defect is encountered, the list parameter with the next higherM    parameter code is updated to record this defect.  The size of the page can P    be made target specific to accommodate memory limitations.  It is recommendedK    that one or more data counter parameters be defined for the page to keep M    track of the number of valid list parameters and the parameter code of the=O    parameter with the oldest recorded defect.  This technique can be adapted to %    record other types of information.m  I The parameter length field specifies the length in bytes of the followingeF parameter value.  If the initiator sends a parameter length value thatB results in the truncation of the parameter value, the target shallG terminate the command with CHECK CONDITION status.  The sense key shall G be set to ILLEGAL REQUEST with the additional sense code set to INVALID  FIELD IN PARAMETER LIST.  F If the initiator sends a log parameter value that is outside the rangeH supported by the target, and rounding is implemented for that parameter, the target may either:M    a)     round to an acceptable value and terminate the command as described            in 7.5.4; orM    b)     terminate the command with CHECK CONDITION status and set the sense N           key to ILLEGAL REQUEST with the additional sense code set to INVALID"           FIELD IN PARAMETER LIST.  I When any counter in a log page reaches its maximum value, incrementing ofeD all counters in that log page shall cease until reinitialized by theH initiator via a LOG SELECT command.  If the RLEC bit of the control modeB page is one, then the target shall report the exception condition.  C The page code assignments for the log pages are listed in table 83.   3                           Table 83 - Log page codestO +=============-==================================================-============+dO |  Page code  |  Description                                     | Subclause  |aO |-------------+--------------------------------------------------+------------|sO |     01h     |  Buffer over-run/under-run page                  |  8.3.2.1   | O |     03h     |  Error counter page (read) page                  |  8.3.2.2   |=O |     04h     |  Error counter page (read reverse) page          |  8.3.2.2   | O |     05h     |  Error counter page (verify) page                |  8.3.2.2   | O |     02h     |  Error counter page (write) page                 |  8.3.2.2   |=O |     07h     |  Last n error events page                        |  8.3.2.3   | O |     06h     |  Non-medium error page                           |  8.3.2.4   | O |     00h     |  Supported log pages                             |  8.3.2.5   | O |  08h - 2Fh  |  Reserved                                        |            |-O |     3Fh     |  Reserved                                        |            | O |  30h - 3Eh  |  Vendor-specific pages                           |            |-O +=============================================================================+     & 8.3.2.1 Buffer over-run/under-run page  B The buffer over-run/under-run page (page code 01h) defines 24 dataE counters that may be used to record the number of buffer over-runs or H under-runs for the logical unit.  A target that implements this page may5 implement one or more of the defined data counters.     C A buffer over-run or under-run can occur when an initiator does not H transmit data to or from the target's buffer fast enough to keep up withI reading or writing the media.  This can be caused by a slow transfer rate C across the SCSI bus or by a high SCSI bus utilization that preventseI reconnection by the target.  A buffer over-run condition can occur duringlI a read operation when a buffer full condition prevents continued transfereG of data from the media to the buffer.  A buffer under-run condition can.E occur during a write operation when a buffer empty condition preventshF continued transfer of data to the media from the buffer.  Most devices< incur a delay at this point while the media is repositioned.  H Table 84 defines the parameter code field for the buffer over-run/under-
 run counters.e  J     Table 84 - Parameter code field for buffer over-run/under-run countersO +=====-========-========-========-========-========-========-========-========+xO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |oO |Byte |        |        |        |        |        |        |        |        |aO |=====+=======================================================================|EO | 0   |                          Reserved                                     |uO |-----+-----------------------------------------------------------------------| O | 1   |      Count basis         |               Cause               |  Type  |yO +=============================================================================+s    H The parameter code field for buffer over-run/under-run counters is a 16-I bit value comprised of eight reserved bits, a three-bit count basis fieldhI (see table 85), a four-bit cause field (see table 86), and a one-bit typeaF field.  These are concatenated to determine the value of the parameterG code for that log parameter.  For example, a counter for parameter code G value of 0023h specifies a count basis of 001b; a cause of 0001b; and a I type of 1b; this counter is incremented once per command that experiencesa+ an over-run due to the SCSI bus being busy.E  7                       Table 85 - Count basis definition ( +=============-========================+( | Count basis |  Description           |( |-------------+------------------------|( |    000b     |  Undefined             |( |    001b     |  Per command           |( |    010b     |  Per failed reconnect  |( |    011b     |  Per unit of time      |( | 100b - 111b |  Reserved              |( +======================================+    I The count basis field defines the criteria for incrementing the counter. n$ The following criteria are defined:   M    NOTE 95 The per unit of time count basis is device type specific.  Direct-oL    access devices typically use a latency period (i.e. one revolution of the    medium) as the unit of time.e  C The cause field indicates the reason that the over-run or under-run 8 occurred.  The following causes are defined in table 86.  7                       Table 86 - Cause field definitiona' +============-========================+ ' |    Cause   |Description             |e' |------------+------------------------| ' |      0h    |Undefined               | ' |      1h    |SCSI bus busy           |m' |      2h    |Transfer rate too slow  |=' |   3h - Fh  |Reserved                | ' +=====================================+     H The type field indicates whether the counter records under-runs or over-I runs.  A value of zero specifies a buffer under-run condition and a valuea- of one specifies a buffer over-run condition.   H The counters contain the total number of times buffer over-run or under-J run conditions have occurred since the last time the counter was cleared. G The counter shall be incremented for each occurrence of an under-run or E over-run condition and can be incremented more than once for multiplef5 occurrences during the execution of a single command.c   8.3.2.2 Error counter pagest  E This clause defines the optional error counter pages for write errorsSG (page code 02h), read errors (page code 03h), read reverse errors (pageoD code 04h) and verify errors (page code 05h).  The log page format isG defined near the beginning of 8.3.2.  A page can return one or more logi= parameters this record events defined by the parameter codes.d  J Table 87 defines the parameter codes for the error counter pages.  Support# of each log parameter is optional.    @               Table 87 - Parameter codes for error counter pagesI        +=================-==============================================+eI        | Parameter code  |  Description                                 |sI        |-----------------+----------------------------------------------|oI        |     0000h       |  Errors corrected without substantial delay  |mI        |     0001h       |  Errors corrected with possible delays       | I        |     0002h       |  Total (e.g. rewrites or rereads)            |sI        |     0003h       |  Total errors corrected                      | I        |     0004h       |  Total times correction algorithm processed  |mI        |     0005h       |  Total bytes processed                       |gI        |     0006h       |  Total uncorrected errors                    |3I        |  0007h - 7FFFh  |  Reserved                                    | I        |  8000h - FFFFh  |  Vendor-specific                             |oI        +================================================================+c    I    NOTE 96 The exact definition of the error counters is not part of this H    International Standard.  These counters should not be used to compare?    products because the products may define errors differently.7    8.3.2.3 Last n error events page  J Log page (07h) provides for a number of error-event records using the listJ parameter format of the log page.  The number of these error-event recordsC supported, n, is device-specific.  Each error-event record containseH device-specific diagnostic information for a single error encountered byB the device.  The parameter code associated with error-event recordB indicates the relative time at which the error occurred.  A higherE parameter code indicates that the error event occurred later in time.m  J The content of the parameter value field of each log parameter is an ASCIIH character string which may describe the error event.  The exact contentsF of the character string is not defined by this International Standard.  H When the last supported parameter code is used by an error-event record,J the recording on this page of all subsequent error information shall ceaseI until one or more of the list parameters with the highest parameter codescB have been reinitialized.  If the RLEC bit of the control mode pageG (8.3.3.1) is set to one, the target shall return CHECK CONDITION statusaG with the sense key set to RECOVERED ERROR and the additional sense codeaF set to LOG LIST CODES EXHAUSTED.  Alternatively, the target may report? this condition via asynchronous event notification (see 7.5.5).    8.3.2.4 Non-medium error page   A This page (page code 06h) provides for summing the occurrences ofnH recoverable error events other than write, read, or verify failures.  NoI discrimination among the various types of events is provided by parametertD code (see table 88).  Vendor-specific discrimination may be provided, through the vendor-specific parameter codes.  ?               Table 88 - Non-medium error event parameter codesiB +=================-==============================================+B | Parameter code  |  Description                                 |B |-----------------+----------------------------------------------|B |      0000h      |  Non-medium error count                      |B |  0001h - 7FFFh  |  Reserved                                    |B |  8000h - FFFFh  |  Vendor-specific error counts                |B +================================================================+     8.3.2.5 Supported log pagese  C The supported log page (see table 89) returns the list of log pages H implemented by the target.  Targets that implement the LOG SENSE command shall implement this log page.  6                         Table 89 - Supported log pagesO +=====-========-========-========-========-========-========-========-========+iO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |tO |Byte |        |        |        |        |        |        |        |        |,O |=====+=================+=====================================================|tO | 0   |    Reserved     |        Page code (00h)                              |3O |-----+-----------------------------------------------------------------------|=O | 1   |                          Reserved                                     | O |-----+-----------------------------------------------------------------------|-O | 2   | (MSB)                                                                 | O |-----+---                       Page length (n-3)                         ---| O | 3   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------| O | 4   |                                                                       | O |- - -+---                       Supported page list                       ---| O | n   |                                                                       | O +=============================================================================+     C This page is not defined for the LOG SELECT command.  This log page G returns the list of supported log pages for the specified logical unit.   D The page length field specifies the length in bytes of the following supported page list.  H The supported page list field shall contain a list of all log page codesJ implemented by the target in ascending order beginning with page code 00h.   8.3.3 Mode parameters-  F This subclause describes the block descriptors and the pages used withC MODE SELECT and MODE SENSE commands that are applicable to all SCSIiG devices.  Pages specific to each device type are described in the thirdd< subclause of each device-type clause (i.e. 9.3, 10.3, etc.).  H The mode parameter list shown in table 90 contains a header, followed byH zero or more block descriptors, followed by zero or more variable-length9 pages.  Parameter lists are defined for each device type.b  6                         Table 90 - Mode parameter listP +======-========-========-========-========-========-========-========-========+P |   Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P |Byte  |        |        |        |        |        |        |        |        |P |======+=======================================================================|P |0 - n |                        Mode parameter header                          |P |======+=======================================================================|P |0 - n |                        Block descriptor(s)                            |P |======+=======================================================================|P |0 - n |                        Page(s)                                        |P +==============================================================================+    J The six-byte command descriptor block parameter header is defined in table 91.=  8                      Table 91 - Mode parameter header(6)O +=====-========-========-========-========-========-========-========-========+-O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |=O |=====+=======================================================================|nO | 0   |                           Mode data length                            |-O |-----+-----------------------------------------------------------------------|dO | 1   |                           Medium type                                 |rO |-----+-----------------------------------------------------------------------| O | 2   |                           Device-specific parameter                   | O |-----+-----------------------------------------------------------------------|uO | 3   |                           Block descriptor length                     |fO +=============================================================================+     J The ten-byte command descriptor block parameter header is defined in table 92.   9                      Table 92 - Mode parameter header(10) O +=====-========-========-========-========-========-========-========-========+-O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |hO |Byte |        |        |        |        |        |        |        |        |lO |=====+=======================================================================|vO | 0   | (MSB)                                                                 |.O |-----+---                        Mode data length                         ---|iO | 1   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|oO | 2   |                           Medium type                                 | O |-----+-----------------------------------------------------------------------| O | 3   |                           Device-specific parameter                   | O |-----+-----------------------------------------------------------------------|=O | 4   |                           Reserved                                    |rO |-----+-----------------------------------------------------------------------|aO | 5   |                           Reserved                                    |lO |-----+-----------------------------------------------------------------------|eO | 6   | (MSB)                                                                 |cO |-----+---                        Block descriptor length                  ---| O | 7   |                                                                 (LSB) |.O +=============================================================================+f  G When using the MODE SENSE command, the mode data length field specifieseA the length in bytes of the following data that is available to beoG transferred.  The mode data length does not include itself.  When using 0 the MODE SELECT command, this field is reserved.  L    NOTE 97 Targets that support more than 256 bytes of block descriptors andL    pages may need to implement ten-byte mode commands.  The mode data lengthL    field in the six-byte command descriptor block header limits the returned    data to 256 bytes.=  @ Medium types are unique for each device type.  Refer to the modeE parameters clause of the specific device type for definition of these-. values.  Some device types reserve this field.  G The device specific parameter is unique for each device type.  Refer to H the mode parameters clause of the specific device type for definition ofA this field.  Some device types reserve all or part of this field.   J The block descriptor length specifies the length in bytes of all the blockI descriptors.  It is equal to the number of block descriptors times eight, J and does not include pages or vendor-specific parameters, if any, that mayD follow the last block descriptor.  A block descriptor length of zeroF indicates that no block descriptors are included in the mode parameter7 list.  This condition shall not be considered an error.   9 The mode parameter block descriptor is shown in table 93.=  <                   Table 93 - Mode parameter block descriptorO +=====-========-========-========-========-========-========-========-========+aO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |dO |Byte |        |        |        |        |        |        |        |        |aO |=====+=======================================================================|oO | 0   |                           Density code                                |dO |-----+-----------------------------------------------------------------------|fO | 1   | (MSB)                                                                 |iO |-----+---                                                                 ---|rO | 2   |                           Number of blocks                            |iO |-----+---                                                                 ---|IO | 3   |                                                                 (LSB) |eO |-----+-----------------------------------------------------------------------| O | 4   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|sO | 5   | (MSB)                                                                 |RO |-----+---                                                                 ---|nO | 6   |                           Block length                                |iO |-----+---                                                                 ---| O | 7   |                                                                 (LSB) |.O +=============================================================================+c    G Block descriptors specify some of the medium characteristics for all oruI part of a logical unit.  Support for block descriptors is optional.  EachaI block descriptor contains a density code field, a number of blocks field,dE and a block length field.  Block descriptor values are always current E (i.e. saving is not supported).  A unit attention condition (see 7.9)=@ shall be generated when any block descriptor values are changed.  H The density code field is unique for each device type. Refer to the modeD parameters clause of the specific device type for definition of this< field.  Some device types reserve all or part of this field.  H The number of blocks field specifies the number of logical blocks on theH medium to which the density code and block length fields apply.  A valueI of zero indicates that all of the remaining logical blocks of the logical 5 unit shall have the medium characteristics specified.       NOTESO    98 There may be implicit association between parameters defined in the pagessN    and block descriptors.  For direct-access devices, the block length affectsP    the optimum values (the values that achieve best performance) for the sectorsM    per track, bytes per physical sector, track skew factor, and cylinder skew M    factor fields in the format parameters page.  In this case, the target may=I    change parameters not explicitly sent with the MODE SELECT command.  A =    subsequent MODE SENSE command would reflect these changes. K    99 The number of remaining logical blocks may be unknown for some device-	    types.-  D The block length specifies the length in bytes of each logical blockJ described by the block descriptor.  For sequential-access devices, a blockJ length of zero indicates that the logical block size written to the mediumI is specified by the transfer length field in the command descriptor blockh (see 10.2.4 and 10.2.14)  , The mode page format is defined in table 94.  4                          Table 94 - Mode page formatO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |-O |Byte |        |        |        |        |        |        |        |        | O |=====+========+========+=====================================================|=O | 0   |   PS   |Reserved|         Page code                                   |pO |-----+-----------------------------------------------------------------------|oO | 1   |                           Page length (n-1))                          |pO |-----+-----------------------------------------------------------------------|eO | 2   |                                                                       |tO |-----+--                         Mode parameters                          ---| O | n   |                                                                       |LO +=============================================================================+c    E Each mode page contains a page code, a page length, and a set of modeiI parameters.  The page codes are defined in this subclause and in the modet2 parameter sub-clauses of the specific device type.  G When using the MODE SENSE command, a parameters savable (PS) bit of oneeJ indicates that the mode page can be saved by the target in a non-volatile,H vendor-specific location.  A PS bit of zero indicates that the supportedG parameters cannot be saved.  When using the MODE SELECT command, the PS  bit is reserved.  I The page code field identifies the format and parameters defined for that G mode page.  Some page codes are defined as applying to all device types=@ and other page codes are defined for the specific device type.    J When using the MODE SENSE command, if page code 00h (vendor-specific page)G is implemented, the target shall return that page last in response to a H request to return all pages (page code 3Fh).  When using the MODE SELECT' command, this page should be sent last.=  J The page length field specifies the length in bytes of the mode parametersH that follow.  If the initiator does not set this value to the value thatD is returned for the page by the MODE SENSE command, the target shallG terminate the command with CHECK CONDITION status.  The sense key shall G be set to ILLEGAL REQUEST with the additional sense code set to INVALID=J FIELD IN PARAMETER LIST.  The target is permitted to implement a mode pageD that is less than the full page length defined in this InternationalB Standard, provided no field is truncated and the page length field2 correctly specifies the actual length implemented.  J The mode parameters for each page are defined in the following subclauses,H or in the mode parameters sub-clause for the specific device type.  Mode> parameters not implemented by the target shall be set to zero.  G Table 95 defines the mode pages that are applicable to all device types-5 that include the MODE SELECT and MODE SENSE commands.-  4                           Table 95 - Mode page codesO +=============-==================================================-============+-O |  Page code  |  Description                                     | Subclause  |eO |-------------+--------------------------------------------------+------------|=O |     0Ah     |  Control mode page                               |  8.3.3.1   | O |     02h     |  Disconnect-reconnect page                       |  8.3.3.2   |eO |     09h     |  Peripheral device page                          |  8.3.3.3   |=O |     01h     |  (See specific device type)                      |            | O |  03h - 08h  |  (See specific device type)                      |            | O |  0Bh - 1Fh  |  (See specific device type)                      |            |=O |     00h     |  Vendor-specific (does not require page format)  |            | O |  20h - 3Eh  |  Vendor-specific (page format required)          |            | O |     3Fh     |  Return all pages                                |            | O |             |     (valid only for the MODE SENSE command)      |            |-O +=============================================================================+      8.3.3.1 Control mode page-  J The control mode page (see table 96) provides controls over several SCSI-2H features that are applicable to all device types such as tagged queuing,J extended contingent allegiance, asynchronous event notification, and error logging.  5                          Table 96 - Control mode page O +=====-========-========-========-========-========-========-========-========+-O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |-O |=====+========+========+=====================================================| O | 0   |   PS   |Reserved|         Page code (0Ah)                             | O |-----+-----------------------------------------------------------------------| O | 1   |                           Page length (06h)                           |=O |-----+-----------------------------------------------------------------------| O | 2   |                           Reserved                           |  RLEC  |bO |-----+--------------------------------------------------------------+--------| O | 3   |     Queue algorithm modifier      |    Reserved     |  QErr  |  DQue  |oO |-----+-----------------------------------------------------+--------+--------|tO | 4   |  EECA  |              Reserved             | RAENP  | UAAENP | EAENP  |oO |-----+-----------------------------------------------------------------------|iO | 5   |                           Reserved                                    |eO |-----+-----------------------------------------------------------------------|.O | 6   | (MSB)                                                                 | O |-----+---                        Ready AEN holdoff period                 ---| O | 7   |                                                                 (LSB) |nO +=============================================================================+t    E A report log exception condition (RLEC) bit of one specifies that the F target shall report log exception conditions as described in 8.3.2.  AI RLEC bit of zero specifies that the target shall not report log exceptiont conditions.d  H The queue algorithm modifier field (see table 97) specifies restrictionsF on the algorithm used for reordering commands that are tagged with the SIMPLE QUEUE TAG message.-  8                      Table 97 - Queue algorithm modifier2 +===========-====================================+2 |   Value   |  Definition                        |2 |-----------+------------------------------------|2 |     0h    |  Restricted reordering             |2 |     1h    |  Unrestricted reordering allowed   |2 |  2h - 7h  |  Reserved                          |2 |  8h - Fh  |  Vendor-specific                   |2 +================================================+    G A value of zero in this field specifies that the target shall order the F actual execution sequence of the commands with a SIMPLE QUEUE tag suchG that data integrity is maintained for that initiator.  This means that, J if the transmission of new commands is halted at any time, the final valueI of all data observable on the medium shall have exactly the same value asID it would have if the commands had been executed in the same receivedG sequence without tagged queuing.  The restricted reordering value shall- be the default value.   F A value of one in this field specifies that the target may reorder theH actual execution sequence of the commands with a SIMPLE QUEUE tag in anyG manner.  Any data integrity exposures related to command sequence order @ are explicitly handled by the initiator through the selection of- appropriate commands and queue tag messages.    D A queue error management (QErr) bit of zero specifies that remainingB suspended I/O process shall resume after the contingent allegianceB condition or extended contingent allegiance condition (see 7.8).    G A QErr bit of one specifies all remaining suspended I/O processes shall=@ be aborted after the contingent allegiance condition or extendedF contingent allegiance condition (see 7.8).  A unit attention conditionH (see 7.9) shall be generated for each initiator that had a suspended I/O@ process aborted except for the initiator that had the contingentF allegiance condition or extended contingent allegiance condition.  TheH target shall set the additional sense code to TAGGED COMMANDS CLEARED BY ANOTHER INITIATOR.  H A disable queuing (DQue) bit of zero specifies that tagged queuing shallD be enabled if the target supports tagged queuing.  A DQue bit of oneI specifies that tagged queuing shall be disabled.  Any queued commands for D that I_T_x nexus shall be aborted.  Any subsequent queue tag messageD received shall be rejected with a MESSAGE REJECT message and the I/O= process shall be executed as an untagged command (see 7.8.1).a  I An enable extended contingent allegiance (EECA) bit of one specifies thatiI extended contingent allegiance is enabled (see 7.7).  An EECA bit of zero : specifies that extended contingent allegiance is disabled.  G The RAENP, UAAENP, and EAENP bits enable specific events to be reported J via the asynchronous event notification protocol.  When all three bits areC zero, the target shall not create asynchronous event notifications.c  G A ready AEN permission (RAENP) bit of one specifies that the target may < issue an asynchronous event notification upon completing itsJ initialization sequence instead of generating a unit attention condition. @ A RAENP bit of zero specifies that the target shall not issue anB asynchronous event notification upon completing its initialization	 sequence.h  N    NOTE 100 If the target's default value for the RAENP bit is one and it doesO    not implement saved parameters or include a hardware switch, then it may notiH    be possible to disable the initialization sequence asynchronous event    notification.  F A unit attention AEN permission (UAAENP) bit of one specifies that theG target may issue an asynchronous event notification instead of creating=J a unit attention condition upon detecting an event that would cause a unitA attention condition (other than upon completing an initialization J sequence).  A UAAENP bit of zero specifies that the target shall not issueG an asynchronous event notification instead of creating a unit attention=
 condition.  H An error AEN permission (EAENP) bit of one specifies that the target mayH issue an asynchronous event notification upon detecting a deferred errorE condition instead of waiting to report the deferred error on the next I command.  An EAENP bit of zero specifies that the target shall not report-A deferred error conditions via an asynchronous event notification.   @ The ready AEN holdoff period field specifies the minimum time inH milliseconds after the target starts its initialization sequence that itK shall delay before attempting to issue an asynchronous event notification. =1 This value may be rounded up as defined in 7.5.4.=   8. Disconnect-reconnect page  G The disconnect-reconnect page (see table 98) provides the initiator the . means to tune the performance of the SCSI bus.  9                      Table 98 - Disconnect-reconnect pagehO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |vO |=====+========+========+=====================================================|dO | 0   |   PS   |Reserved|         Page code (02h)                             |pO |-----+-----------------------------------------------------------------------|dO | 1   |                           Page length (0Eh)                           |aO |-----+-----------------------------------------------------------------------|pO | 2   |                           Buffer full ratio                           |iO |-----+-----------------------------------------------------------------------|iO | 3   |                           Buffer empty ratio                          |iO |-----+-----------------------------------------------------------------------| O | 4   | (MSB)                                                                 |sO |-----+---                        Bus inactivity limit                     ---| O | 5   |                                                                 (LSB) |eO |-----+-----------------------------------------------------------------------|nO | 6   | (MSB)                                                                 | O |-----+---                        Disconnect time limit                    ---| O | 7   |                                                                 (LSB) |eO |-----+-----------------------------------------------------------------------|eO | 8   | (MSB)                                                                 |yO |-----+---                        Connect time limit                       ---| O | 9   |                                                                 (LSB) |=O |-----+-----------------------------------------------------------------------| O | 10  | (MSB)                                                                 |-O |-----+---                        Maximum burst size                       ---| O | 11  |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------| O | 12  |                           Reserved                  |      DTDC       | O |-----+-----------------------------------------------------------------------| O | 13  |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|qO | 14  |                           Reserved                                    | O |-----+-----------------------------------------------------------------------| O | 15  |                           Reserved                                    |SO +=============================================================================+=    H The buffer full ratio field indicates to the target, on read operations,I how full the buffer should be prior to attempting a reselection.  TargetssJ that do not implement the requested ratio should round down to the nearest& implemented ratio as defined in 7.5.4.  J The buffer empty ratio field indicates to the target, on write operations,J how empty the buffer should be prior to attempting a reselection.  TargetsJ that do not implement the requested ratio should round down to the nearest& implemented ratio as defined in 7.5.4.  F The buffer full and buffer empty ratios are numerators of a fractionalF multiplier that has 256 as its denominator.  A value of zero indicatesG that the target determines when to initiate reselection consistent with J the disconnect time limit parameter.  These parameters are advisory to the target.-  L    NOTE 101 As an example, consider a target with ten 512-byte buffers and a7    specified buffer full ratio of 3Fh.  The formula is:-P    INTEGER((ratio/256)*number of buffers).  Thus INTEGER((3Fh/256)*10) = 2.  TheN    target should attempt to reselect the initiator on read operations whenever     two or more buffers are full.  C The bus inactivity limit field indicates the maximum time in 100 us H increments that the target is permitted to assert the BSY signal withoutH a REQ/ACK handshake.  If the bus inactivity limit is exceeded the targetG shall attempt to disconnect if the initiator has granted the disconnect-G privilege (see 6.6.7) and it is not restricted by DTDC.  This value mayeH be rounded as defined in 7.5.4.  A value of zero indicates that there is no bus inactivity limit.  D The disconnect time limit field indicates the minimum time in 100 usI increments that the target shall wait after releasing the SCSI bus beforedH attempting reselection.  This value may be rounded as defined in 7.5.4. A A value of zero indicates that there is no disconnect time limit.=  A The connect time limit field indicates the maximum time in 100 us @ increments that the target is allowed to use the SCSI bus beforeI disconnecting, if the initiator has granted the disconnect privilege (seeAF 6.6.7) and it is not restricted by DTDC.  This value may be rounded asJ defined in 7.5.4.  A value of zero indicates that there is no connect time limit.  J The maximum burst size field indicates the maximum amount of data that theE target shall transfer during a data phase before disconnecting if theuH initiator has granted the disconnect privilege.  This value is expressedJ in increments of 512 bytes (e.g. a value of one means 512 bytes, two meansF 1024 bytes, etc.).  A value of zero indicates there is no limit on the, amount of data transferred per connection.    H The data transfer disconnect control (DTDC) field (see table 99) defines7 further restrictions on when a disconnect is permitted.=  <                  Table 99 - Data transfer disconnect controlO +=======-=====================================================================+eO | DTDC  |  Description                                                        |tO |-------+---------------------------------------------------------------------|aO |  00b  |  Data transfer disconnect control is not used.  Disconnect is       | O |       |  controlled by the other fields in this page.                       |eO |  01b  |  A target shall not attempt to disconnect once the data transfer of | O |       |  a command has started until all data the command is to transfer has|mO |       |  been transferred.  The connect time limit and bus inactivity limit | O |       |  are ignored during the data transfer.                              | O |  10b  |  Reserved                                                           |mO |  11b  |  A target shall not attempt to disconnect once the data transfer of |cO |       |  a command has started, until the command is complete.  The connect |eO |       |  time limit and bus inactivity limit are ignored once data transfer |EO |       |  has started.                                                       |aO +=============================================================================+t    F If DTDC is non-zero and the maximum burst size is non-zero, the targetC shall return CHECK CONDITION status.  The sense key shall be set totE ILLEGAL REQUEST and the additional sense code set to ILLEGAL FIELD INc PARAMETER LIST.    8.3.3.3 Peripheral device page  J The peripheral device page (see table 100) is used to pass vendor-specificE information between an initiator and a peripheral interface below thesA target (i.e. between the target and the peripheral device).  This I International Standard does not define the format of this data, except tod provide a standard header. l  8                       Table 100 - Peripheral device pageO +=====-========-========-========-========-========-========-========-========+eO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |eO |Byte |        |        |        |        |        |        |        |        |eO |=====+========+========+=====================================================|sO | 0   |   PS   |Reserved|         Page code (09h)                             | O |-----+-----------------------------------------------------------------------|oO | 1   |                           Page length (n-1)                           |eO |-----+-----------------------------------------------------------------------| O | 2   | (MSB)                                                                 |tO |-----+---                        Interface identifier                     ---|hO | 3   |                                                                 (LSB) |iO |-----+-----------------------------------------------------------------------|oO | 4   |                           Reserved                                    |hO |-----+-----------------------------------------------------------------------|sO | 5   |                           Reserved                                    |pO |-----+-----------------------------------------------------------------------|cO | 6   |                           Reserved                                    |nO |-----+-----------------------------------------------------------------------|.O | 7   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|AO | 8   |                                                                       |nO |-----+---                        Vendor-specific                          ---|iO | n   |                                                                       |iO +=============================================================================+n    8 Interface identifier codes are defined in the table 101.  :                     Table 101 - Interface identifier codesO +=================-======================================-====================+eO |                 |                                      |       ANSI         |nO |   Code value    |               Interface              | Reference standard |bO |-----------------+--------------------------------------+--------------------|.O |      0000h      |  Small computer cystem interface     |  X3.131-1986       |=O |      0001h      |  Storage module interface            |  X3.91M-1990       | O |      0002h      |  Enhanced small device interface     |  X3.170A-1991      | O |      0003h      |  Intelligent peripheral interface-2  |  X3.130-1986;      |=O |                 |                                      |    X3T9.3/87-002   |eO |      0004h      |  Intelligent peripheral interface-3  |  X3.132-1987;      |-O |                 |                                      |    X3.147-1988     | O |  0005h - 7FFFh  |  Reserved                            |                    |-O |  8000h - FFFFh  |  Vendor-specific                     |                    | O +=============================================================================+-  # 8.3.4 Vital product data parameters-  H This clause describes the optional vital product data page structure andG the vital product data pages (see table 102) that are applicable to all-I SCSI devices.  These pages are optionally returned by the INQUIRY command I (8.2.5) and contain vendor-specific product information about a target or H logical unit.  The vital product data may include vendor identification,J product identification, unit serial numbers, device operating definitions,I manufacturing data, field replaceable unit information, and other vendor-BH specific information.  This International Standard defines the structure0 of the vital product data, but not the contents.  ;                   Table 102 - Vital product data page codes O +=============-==================================================-============+-O |  Page code  |  Description                                     | Subclause  | O |-------------+--------------------------------------------------+------------|oO |     82h     |  ASCII implemented operating definition page     |  8.3.4.1   | O |  01h - 7Fh  |  ASCII information page                          |  8.3.4.2   |-O |     81h     |  Implemented operating definitions page          |  8.3.4.3   | O |     00h     |  Supported vital product data pages              |  8.3.4.4   |aO |     80h     |  Unit serial number page                         |  8.3.4.5   | O |  83h - BFh  |  Reserved                                        |            |-O |  C0h - FFh  |  Vendor-specific                                 |            |eO +=============================================================================+-    3 8.3.4.1 ASCII implemented operating definition page   H The ASCII implemented operation definition page (see table 103) containsC operating definition description data for all operating definitions-G implemented by the target.  The contents of this data is not defined by  this International Standard.  A               Table 103 - ASCII implemented operating definition 5O +=====-========-========-========-========-========-========-========-========+=O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |lO |=====+==========================+============================================|mO | 0   | Peripheral qualifier     |           Peripheral device type           |sO |-----+-----------------------------------------------------------------------|iO | 1   |                           Page code (82h)                             | O |-----+-----------------------------------------------------------------------|eO | 2   |                           Reserved                                    |tO |-----+-----------------------------------------------------------------------|AO | 3   |                           Page length (n-3)                           | O |-----+-----------------------------------------------------------------------|sO | 4   |              ASCII operating definition description length (m-4)      |-O |-----+-----------------------------------------------------------------------|IO | 5   |                                                                       |tO |- - -+---           ASCII operating definition description data           ---|oO | m   |                                                                       |mO |-----+-----------------------------------------------------------------------|lO | m+1 |                                                                       |tO |- - -+---           Vendor-specific description data                      ---|lO | n   |                                                                       | O +=============================================================================+i    G The peripheral qualifier field and the peripheral device type field aren as defined in 8.2.5.1.  G The page length field specifies the length of the following page data. TB If the allocation length is less than the length of the data to beJ returned, the page length shall not be adjusted to reflect the truncation.  E The ASCII operating definition description length field specifies thelG length in bytes of the ASCII operating definition description data thatnH follows.  If the allocation length is less than the length of data to beH returned, the ASCII operating definition description length shall not beB adjusted to reflect the truncation.  A value of zero in this field@ indicates that no ASCII operating definition description data is
 available.  H The ASCII operating definition description data field contains the ASCIIJ operating definition description data for the target or logical unit.  TheG data in this field shall be formatted in lines (or character strings).  H Each line shall contain only graphic codes (i.e. code values 20h through: 7Eh) and shall be terminated with a NULL (00h) character.    8.3.4.2 ASCII information page  F The ASCII information page (see table 104) returns information for theC field replaceable unit code returned in the REQUEST SENSE data (see=
 8.2.14).    8                       Table 104 - ASCII information pageO +=====-========-========-========-========-========-========-========-========+-O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |tO |Byte |        |        |        |        |        |        |        |        |nO |=====+==========================+============================================|tO | 0   | Peripheral qualifier     |           Peripheral device type           |cO |-----+-----------------------------------------------------------------------|eO | 1   |                           Page code (01h - 7Fh)                       |eO |-----+-----------------------------------------------------------------------|sO | 2   |                           Reserved                                    |tO |-----+-----------------------------------------------------------------------|cO | 3   |                           Page length (n-3)                           |mO |-----+-----------------------------------------------------------------------|sO | 4   |                           ASCII length (m-4)                          |=O |-----+-----------------------------------------------------------------------|sO | 5   |                                                                       |CO |- - -+---                        ASCII information                        ---|nO | m   |                                                                       |vO |-----+-----------------------------------------------------------------------|cO | m+1 |                                                                       |gO |- - -+---                        Vendor-specific information              ---|nO | n   |                                                                       |eO +=============================================================================+-    G The peripheral qualifier field and the peripheral device type field are  defined in 8.2.5.1.|  H The page code field contains the same value as in the page code field ofG the INQUIRY command descriptor block (see 8.2.5) and is associated with=F the field replaceable unit code returned by the REQUEST SENSE command.  O    NOTE 102 The field replaceable unit field in the sense data provides for 255-K    possible codes, while the page code field provides for only 127 possible L    codes.  Thus it is not possible to return ASCII information pages for the    upper code values.-  G The page length field specifies the length of the following page data.  H If the allocation length of the command descriptor block is too small toJ transfer all of the page, the page length shall not be adjusted to reflect the truncation.   A The ASCII length field specifies the length in bytes of the ASCII-D information that follows.  If the allocation length is less than theI length of the data to be returned, the ASCII length shall not be adjusted H to reflect the truncation.  A value of zero in this field indicates that> no ASCII information is available for the specified page code.  E The ASCII information field contains ASCII information concerning the-E field replaceable unit identified by the page code.  The data in this F field shall be formatted in one or more lines (or character strings). H Each line shall contain only graphic codes (i.e. code values 20h through: 7Eh) and shall be terminated with a NULL (00h) character.   G The contents of the vendor-specific information field is not defined in- this International Standard.  - 8.3.4.3 Implemented operating definition page   E The implemented operating definition page (see table 105) defines the G current operating definition, the default operating definition, and the A operating definitions implemented by the target.  These operating=E definition values are specified in the CHANGE DEFINITION command (seed 8.2.1).f  ?               Table 105 - Implemented operating definition page O +=====-========-========-========-========-========-========-========-========+=O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |rO |=====+==========================+============================================|-O | 0   | Peripheral qualifier     |           Peripheral device type           |1O |-----+-----------------------------------------------------------------------|9O | 1   |                           Page code (81h)                             |1O |-----+-----------------------------------------------------------------------|1O | 2   |                           Reserved                                    |3O |-----+-----------------------------------------------------------------------|1O | 3   |                           Page length (n-3)                           |3O |-----+-----------------------------------------------------------------------| O | 4   |Reserved|         Current operating definition                         | O |-----+--------+--------------------------------------------------------------|=O | 5   | SavImp |         Default operating definition                         | O |-----+--------+--------------------------------------------------------------|(O | 6   | SavImp |                                                              |aO |-----+---     +         Supported operating definition list               ---| O | n   | SavImp |                                                              | O +=============================================================================+t    G The peripheral qualifier field and the peripheral device type field are  defined in 8.2.5.1.f  E The page length field specifies the length of the following operatingeI definitions.  If the allocation length of the command descriptor block is C too small to transfer all of the page, the page length shall not be=# adjusted to reflect the truncation.=  F For each operating definition, there is an associated save implementedD (SavImp) bit.  A SavImp bit of zero indicates that the correspondingD operating definition parameter cannot be saved.  A SavImp bit of oneF indicates that the corresponding operating definition parameter can be saved.  J All returned operating definitions use the codes defined in table 33.  TheC current operating definition field returns the value of the presentdG operating definition.  If no operating definition is saved, the defaultUH operating definition field returns the value of the operating definitionJ the target uses when power is applied.  The supported operating definitionI list returns one or more operating definitions implemented by the target.e  * 8.3.4.4 Supported vital product data pages  > The supported vital product data pages are shown in table 106.  >                 Table 106 - Supported vital product data pagesO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |IO |=====+==========================+============================================|=O | 0   | Peripheral qualifier     |           Peripheral device type           | O |-----+-----------------------------------------------------------------------| O | 1   |                           Page code (00h)                             |=O |-----+-----------------------------------------------------------------------| O | 2   |                           Reserved                                    |-O |-----+-----------------------------------------------------------------------| O | 3   |                           Page length (n-3)                           |-O |-----+-----------------------------------------------------------------------| O | 4   |                                                                       |-O |-----+---                        Supported page list                      ---|tO | n   |                                                                       |-O +=============================================================================+t    G The peripheral qualifier field and the peripheral device type field are- defined in 8.2.5.1.-  G The page code field shall be set to the value of the page code field in 1 the INQUIRY command descriptor block (see 8.2.5).I  G The page length field specifies the length of the supported page list.  F If the allocation length is too small to transfer all of the page, the< page length shall not be adjusted to reflect the truncation.  G The supported page list field shall contain a list of all vital product G data page codes implemented for the target or logical unit in ascending # order beginning with page code 00h.    8.3.4.5 Unit serial number page   I This page (see table 107) provides a product serial number for the target= or logical unit.  8                      Table 107 - Unit serial number pageO +=====-========-========-========-========-========-========-========-========+lO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |jO |=====+==========================+============================================|nO | 0   | Peripheral qualifier     |           Peripheral device type           |iO |-----+-----------------------------------------------------------------------|aO | 1   |                           Page code (80h)                             |eO |-----+-----------------------------------------------------------------------|hO | 2   |                           Reserved                                    |rO |-----+-----------------------------------------------------------------------|dO | 3   |                           Page length (n-3)                           | O |-----+-----------------------------------------------------------------------|cO | 4   |                                                                       |0O |- - -+---                        Product serial number                    ---|eO | n   |                                                                       | O +=============================================================================+I    G The peripheral qualifier field and the peripheral device type field are= defined in 8.2.5.1.-  I The page length field specifies the length of the product serial number.  F If the allocation length is too small to transfer all of the page, the< page length shall not be adjusted to reflect the truncation.  C The product serial number field contains ASCII data that is vendor- J specific. The least significant ASCII character of the serial number shallF appear as the last byte of a successful data transfer.  If the productJ serial number is not available, the target shall return ASCII spaces (20h) in this field. -     9 Direct-access devices-     9.1 Direct-access device model  E Direct-access devices store blocks of data for later retrieval.  Each-H block of data is stored at a unique logical block address.  An initiatorH issues WRITE commands to store the blocks of data (write operations) andF READ commands to retrieve the blocks of data (read operations).  OtherI commands issued by the initiator may also cause write and read operations G to occur. A write operation causes a block of data to be written on the-D medium.  A read operation causes a block of data to be read from theE medium.  A verify operation confirms that a block of data can be read  without error from the medium.  G Blocks of data are stored by a process that causes localized changes or G transitions within the medium.  The changes made to the medium to store-E the blocks of data may be volatile (i.e. not retained through a power H cycle) or non-volatile (retained through a power cycle).  The medium mayJ be divided in parts that are used for data blocks, parts that are reservedA for defect management, and parts that are reserved for use by the=, controller for the management of the device.   9.1.1 Removable medium  F The medium may be removable (e.g. used in a floppy disk drive) or non-J removable (e.g. used in a hard disk drive).  Removable medium is containedA within a cartridge (or jacket) to prevent damage to the recordingeC surfaces. The combination of medium and cartridge is often called au volume.h  F A volume has an attribute of being mounted or de-mounted on a suitableG transport mechanism.  A volume is mounted when the direct-access deviceeC is capable of performing write or read operations to the medium.  AsI mounted volume may not be accessible by an initiator if it is reserved byhI another initiator.  A volume is de-mounted at any other time (e.g. duringt" loading, unloading, or storage).    I An initiator may check whether a volume is mounted by issuing a TEST UNIThJ READY command.  A volume that is loaded may need a START STOP UNIT command9 issued to become accessible for write or read operations.t  H The PREVENT ALLOW MEDIUM REMOVAL command allows an initiator to restrictC the demounting of the volume.  This is useful in maintaining systemtG integrity. If the direct-access device implements cache memory, it mustaI ensure that all logical blocks of the medium contain the most recent datalH prior to permitting demounting of the volume.  If the initiator issues aE START STOP UNIT command to eject the cartridge, and the direct-access G device is prevented from demounting by the PREVENT ALLOW MEDIUM REMOVALgE command, the START STOP unit command is rejected by the direct-accessd device.U    Logical blocks   I Blocks of data are stored on the medium along with additional information I that the controller uses to manage the storage and retrieval.  The formatgH of the additional information is unique and is hidden from the initiatorG during normal read or write operations.  This additional information ishJ often used to identify the physical location of the blocks of data and theH address of the logical block, and to provide protection against the loss of the user data.   H The address of the first logical block is zero.  The address of the lastA logical block is [n-1], where [n] is the number of logical blocks B available on the medium.  A READ CAPACITY command may be issued toJ determine the value of [n-1].  If a command is issued that requests accessH to a logical block not within the capacity of the medium, the command is! terminated with CHECK CONDITION. l  H The number of bytes of data contained in a logical block is known as theI block length.  Each logical block has a block length associated with it.  H The block length may be different for each logical block on the medium. J However, in a typical device only one block length is used at a time.  TheH block descriptor in the MODE SENSE data describes the block lengths thatD are used on the medium.  A MODE SELECT command can be used to set upI extents.  An extent is a specified number of logical blocks that have thenI specified block length.  The FORMAT UNIT command is typically required to-J change the block length of devices that support variable block lengths and( make the extents that were setup active.  J The location of a logical block on the medium does not have a relationshipH to the location of any other logical block. However, in a typical deviceI the logical blocks are located in an ascending order.  The time to access-F the logical block at address [x] and then the logical block at addressJ [x+1] need not be less than time to access [x] and then [x+100].  The READD CAPACITY with a PMI bit of one is useful in determining where longer access times occur.    9.1.3 Ready state   B A direct-access device is ready when medium access commands can beF executed.  A device using removable media is usually not ready until aF volume is mounted.  Such a device, with a volume not mounted, normallyC returns CHECK CONDITION status and sets the sense key to NOT READY.a  H Some direct-access devices may be switched from being ready to being notE ready by using the START STOP UNIT command.  An initiator may need to 3 issue a START UNIT command to bring a device ready.i   9.1.4 Initialization  H Many direct-access devices require initialization prior to write or readF operations.  This initialization is usually performed by a FORMAT UNIT< command.  Parameters related to the geometry and performanceD characteristics can be set with the MODE SELECT command prior to theI format operation.  Some devices are initialized by means not specified invG this International Standard.  The time at which this occurs is specifics2 to the implementation of the direct-access device.  J Devices using a non-volatile medium typically save the parameters and onlyG need to be initialized once.  However, some mode parameters may need toiH be initialized after each power-on and reset.  A catastrophic failure ofB the direct-access device may require the FORMAT UNIT command to be
 reissued.   E Devices that use a volatile medium may need to be initialized at each=B power-on prior to the execution of read or write operations.  Mode( parameters may also need initialization.   9.1.5 Medium defects  G Any medium has the potential for defects that can cause user data to be|H lost.  Therefore, each logical block may contain information that allowsI the detection of changes to the user data caused by defects in the medium C or other phenomena, and may also allow the data to be reconstructed-C following the detection of such a change.  Some devices provide the I initiator control through use of the mode parameters.  Some devices allow-G the initiator to examine and modify the additional information by using D the READ LONG and WRITE LONG commands.  Some media having a very low8 probability of defects may not require these structures.  G Defects may also be detected and managed during execution of the FORMATlE UNIT command.  The FORMAT UNIT command defines four sources of defect-C information.  These defects may be reassigned or avoided during the E initialization process so that they do not appear in a logical block.-  G Defects may also be avoided after initialization.  The initiator issues E a REASSIGN BLOCKS command to request that the specified logical block H address be reassigned to a different part of the medium.  This operationJ can be repeated if a new defect appears at a later time.  The total numberJ of defects that may be handled in this manner can be specified in the mode parameters.f  G Defect management on direct-access devices is usually vendor-specific. IB Devices not using a removable medium typically optimize the defectC management for capacity or performance or both.  Devices that use aeF removable medium typically do not support defect management (e.g. someI floppy disk drives) or use defect management that is based on the ability  to interchange the medium.   9.1.6 Data cache  E Some direct-access devices implement cache memory.  A cache memory is.G usually an area of temporary storage in the direct-access device with at@ fast access time that is used to enhance performance.  It existsF separately from the blocks of data stored and is normally not directlyC accessible by the initiator.  Use of cache memory for write or read|G operations typically reduces the access time to a logical block and can ' increase the overall data throughput.     I During read operations, the direct-access device uses the cache memory to=H store blocks of data that the initiator may request at some future time.A The algorithm used to manage the cache memory is not part of this-G International Standard.  However, parameters are provided to advise the E direct-access device about future requests, or to restrict the use of-' cache memory for a particular request. -  G During write operations, the direct-access device uses the cache memorydE to store data that is written to the medium at a later time.  This is-E called a write-back caching algorithm.  Thus the command may complete J prior to blocks of data being written to the medium.  As a result of usingJ a write-back caching algorithm there is a period of time when the data mayC be lost if a power or a hardware failure occurs.  There is also the0J possibility of an error occurring during the write operation.  If an errorF occurred during the write, it may be reported as a deferred error on aH later command.  However, the initiator can request write-through caching- to prevent these circumstances from arising. a  J When the cache memory fills up with blocks of data that are being kept forC possible future access, new blocks of data that are to be kept mustmH replace those currently in cache memory.  The disable page out (DPO) bitI is used to control replacement of logical blocks in the cache.  For writerG operations, setting this bit to one advises the direct-access device to I not replace existing blocks in the cache memory with the write data.  For G read operations, setting this bit to one causes blocks of data that aree< being read to not replace existing ones in the cache memory.  I Sometimes the initiator may wish to have the blocks of data read from theeI medium instead of from the cache memory.  The force unit access (FUA) bitEB is used to indicate that the direct-access device shall access theF physical medium.  For a write operation, setting FUA to one causes theF direct-access device to complete the data write to the physical mediumH before completing the command.  For a read operation, setting FUA to oneE causes the logical blocks to be retrieved from the physical medium.  e  H When the DPO and FUA bits are both set to one, write and read operations bypass the cache memory.  I When a VERIFY command is executed, a forced unit access is implied, sincetI the blocks of data stored on the medium are being verified.  Furthermore,cB a SYNCHRONIZE CACHE operation (see below) is also implied to writeI unwritten blocks of data still in the cache memory.  These blocks of dataoH must be stored on the medium before the verify operation can begin.  TheI DPO bit is provided since the VERIFY command may cause the replacement of D blocks in the cache.  The above also applies to the WRITE AND VERIFY command.  F Commands may be implemented by the direct-access device that allow the9 initiator to control other behaviour of the cache memory:r  M =      LOCK UNLOCK CACHE controls whether certain logical blocks will be heldnJ        in the data cache for future use.  Locking a logical block preventsM        its replacement by a future access.  Unlocking a logical block exposes A        it to possible replacement by a future access (see 9.2.2).t  J =      PRE-FETCH causes a set of logical blocks requested by the initiatorM        to be read into the data cache for possible future access.  The blocks K        fetched are subject to later replacement unless they are locked (seen        9.2.3).  K =      SYNCHRONIZE CACHE forces any pending write data in the requested seteK        of logical blocks to be stored in the physical medium.  This commandUE        can be used to ensure that the data was written and any errorsT        reported (see 9.2.18).s  F =      The MODE SELECT command defines a page for the control of cacheG        behavior and handles certain basic elements of cache replacementi         algorithms (see 9.3.3.1).   9.1.7 Reservations  B The access enabled or access disabled condition determines when anH initiator may store or retrieve user data on all or part of the medium. I Access may be restricted for read operations, write operations, or both.  C This attribute may be controlled by an external mechanism or by thev5 RESERVE and RELEASE commands (see 9.2.12 and 9.2.11).A  I The RESERVE and RELEASE commands define how different types of restrictedeC access may be achieved, and to whom the access is restricted.  This G subclause describes the interaction of the initiator that requested thee& reservation, and the other initiators.  G An initiator uses reservations to gain a level of exclusivity in accessiD to all or part of the medium for itself or another initiator.  It isC expected that the reservation will be retained until released.  ThedH direct-access device must ensure that the initiator with the reservationD is able to access the reserved media within the operating parameters  established by that initiator.    D The following paragraphs explain, on a command by command basis, theH appropriate target response when a reservation exists.  Unless otherwiseH noted, the appropriate response to an initiator that issues a command to? a direct-access device that is reserved to another initiator ise RESERVATION CONFLICT status.  I The CHANGE DEFINITION command is dealt with as follows.  If any initiatoreG has an extent reservation on a direct-access device, no other initiator.D may affect the operating definition of that initiator by use of this@ command.  If the direct-access device allows different operatingG definitions for each initiator, then there is no conflict; otherwise, al reservation conflict occurs.  A The COMPARE, COPY, and COPY AND VERIFY commands are evaluated fornJ reservation conflict as if they were normal write and read operations evenH when a direct-access device is requested to copy to or from itself.  ForH example, if a COPY is issued to logical unit 0 that requests the direct-F access device to copy from logical unit 0 to logical unit 1, access to3 logical unit 1 must also be evaluated for conflict.o  J The FORMAT UNIT, PREVENT ALLOW MEDIUM REMOVAL (with a prevent bit of one),G REZERO UNIT, and START STOP UNIT commands return a RESERVATION CONFLICTcJ status if any other initiator has an extent reservation on a direct-access device.i  F The INQUIRY and REQUEST SENSE commands are not affected by any kind of reservation.  J The LOG SELECT, LOG SENSE, MODE SENSE, TEST UNIT READY, READ CAPACITY (PMIJ set to zero), READ BUFFER, WRITE BUFFER, and READ DEFECT DATA commands are& not affected by extent reservations.    J The SEEK, LOCK UNLOCK CACHE, PRE-FETCH, and SYNCHRONIZE CACHE commands areG evaluated for reservation conflict as if they were normal write or readT operations.o  H The MODE SELECT command is dealt with as follows. If an initiator has anC extent reservation on a direct-access device, and another initiatorsD attempts one of these commands, a reservation conflict occurs if theE command affects the manner in which access of the extent by the firsteE initiator is performed.  If the command does not affect access to theRH extent, or parameters are saved for each initiator, then a conflict does not occur.    I The SEND DIAGNOSTIC, RECEIVE DIAGNOSTIC RESULTS commands conflict with an I extent reservation only if they affect access to the extent (as with MODEd SELECT).  I The REASSIGN BLOCKS command may not reassign a block that is in an extentc reserved to another initiator.  F The SET LIMITS command generates a reservation conflict if the logicalD blocks specified are within an extent reserved to another initiator.  J ALL other commands are that request read or write operations are evaluated= for reservation conflict as described in the RESERVE command.   G When a system is integrated with more than one initiator, there must be I agreement between the initiators as to how media is reserved and releasedeI during operations, otherwise, an initiator may be locked out of access totG a target in the middle of an operation.  For example, initiator 'A' haseF a write operation in progress to a direct-access device which has dataH stored in cache memory.  Then, initiator 'B' issues a RESERVE command toF the direct-access device.  As a result, initiator 'A' is locked out ofI issuing a SYNCHRONIZE CACHE command to ensure the integrity of the data. hJ To prevent this from happening, initiator 'A' should issue a RESERVE prior to the write command.i   9.1.8 Seek and rezeron  H The SEEK command provides a way for the initiator to position the deviceE in preparation for access to a particular logical block at some laterlG time.  Since this positioning action is implicit in other commands, the ? SEEK command may not be useful with some direct-access devices.t  H The REZERO UNIT command is provided to bring the direct-access device toD a known condition.  This International Standard does not specify theG condition.  The REZERO UNIT command is used in some devices to positionNG the actuator at cylinder zero.  Some devices return GOOD status withoutr attempting any action.   9.1.9 Notched drives  J A notched (also called partitioned or zoned) drive has areas of the mediumF in which the drive geometry changes.  In the simplest case, the entireF medium consists of a single notch.  Multiple notches are often used toG increase capacity of the drive.  The notch page is used to indicate thepE notch for assignment of values to the parameters in the format deviceoI page.  By sequencing the notch page through each notch, the format devicem@ parameters of each notch are set.  This is usually done prior to* initialization by the FORMAT UNIT command.  " 9.1.10 Rotational position locking  F Rotational position locking is an optional feature implemented in someH direct-access devices to allow the synchronization of spindles between aI number of devices.  The rotational position offset feature allows devicesfE to synchronize spindles at offsets from index.  This may be useful inbB improving performance in systems that implement arrays of devices.   9.1.11 Relative addressing  I Relative addressing is a technique useful in accessing structured data in H a uniform manner.  Relative addressing is only allowed when commands areF linked.  An example of relative addressing and linking for SEARCH DATA@ commands appropriate to direct-access devices is given in 7.4.3.  I The SET LIMITS command is provided to define the limits of a linked chain E of relative addressing commands.  This gives an additional protection-I against exceeding a particular set of blocks.  The SET LIMITS command hasd! no effect on any other initiator.m   9.1.12 Error reporting  B If any of the following conditions occur during the execution of aI command, the target shall return CHECK CONDITION status.  The appropriatedF sense key and additional sense code should be set.  The following listJ illustrates some error conditions and the applicable sense keys.  The listE does not provide an exhaustive enumeration of all conditions that may ! cause the CHECK CONDITION status.e  b Condition                                                                                Sense keyn Invalid logical block address                                                                          ILLEGAL REQUESTt  r Unsupported option requested                                                                       ILLEGAL REQUEST  { Target reset or medium change since last command from this initiator                                                       o UNIT ATTENTION  q Self diagnostic failed                                                                             HARDWARE ERRORs  o Unrecovered read error                                                                          MEDIUM ERROR oro`                                                                                   HARDWARE ERROR  o Recovered read error                                                                            RECOVERED ERRORt  { Overrun or other error that might be resolved by repeating the command                                                     , ABORTED COMMANDn  q Attempt to write on write protected medium                                                                   DATA  PROTECTd    ? In the case of an invalid logical block address, the sense dataeH information field shall be set to the logical block address of the first invalid address.  H In the case of an attempt to read a blank or previously unwritten block,F the information field shall be set to the logical block address of theG first blank block encountered.  The data read up to that block shall ber9 transferred (optical memory and write-once devices only).s  H In the case of an attempt to write a previously written block when blankF checking is enabled, the information field shall be set to the logicalJ block address of the first non-blank block encountered (optical memory and write-once devices only).i   9.1.13 Examples   H The following examples show some typical variations of the direct-access' device.  Other variations are possible.r   9.1.13.1 Rotating mediao  G The typical application of a direct-access device is a disk drive.  ThelD medium is a disk coated with a material in which flux changes may beH induced.  The disk drive allows direct and random access to the medium. G This is done with an actuator that positions the read-write head, and aeJ rotating disk. Data is stored and retrieved through the interaction of the read-write head and the disk.e  I The disk is typically divided into cylinders.  Each cylinder is typicallytF divided into tracks.  Each track is typically divided into sectors.  AH cylinder is a set of tracks that can be accessed without movement of theE actuator.  A track is a recording path over which the read-write head G travels during one rotation of the disk.  A sector is a part of a tracki% that contains the stored data blocks.s  G A logical block is stored in one or more sectors, or a sector may storeoH more than one logical block.  A sector is typically made up of a header,G data and a trailer.  The header contains a preamble used to synchronize I read circuits to the data, an address field to identify the sector, flagsaH to use for defect management, and a checksum that validates the header. F The data contains the block of data.  The trailer contains checksum orC error correction information.  The checksum or the error correction = information allows the correction of data for medium defects.n  J A disk drive is ready when the disks are rotating at the correct speed andG the read-write circuitry is powered and ready to access the disks. Some F disks, particularly removable disks, require the user to issue load or: start commands to bring the disk drive to the ready state.  E A disk drive will typically have to be formatted prior to the initialsH access.  Exceptions to this are drives that are formatted at the factoryJ and some optical drives with pre-formatted media (see 13.1).  A disk driveG format will typically create the headers for each sector and initializehH the data field.  The MODE SELECT command is often used at format time toF establish the geometry (number of heads and tracks, sectors per track,J etc.) and defect management scheme.  Disk drives are usually non-volatile.  G The defect management scheme of a disk drive is often shielded from thei@ user, though some aspects can be evaluated and controlled by theJ initiator.  The direct-access device will usually reserve some sectors andH tracks for recording defect lists and for reassigning defective blocks. I The READ LONG and WRITE LONG commands will typically access the user data I and checksum portions of the data field so that defects may be induced byiE the initiator to test the defect detection logic of the direct-accesse device.   I Notches find their most typical use in a rotating disk drive.  On a disk,aD the inner tracks are physically shorter than the outer tracks.  As aH result, if each track is made to store the same number of data bits, theG data is packed more densely on the inner tracks than the outer tracks. sE By using notches, the outer tracks may be made to contain a differentiK number of sectors than the inner tracks, while balancing the data density. O# This results in increased capacity.A   9.1.13.2 Sequential media,  H Some tape devices are implemented as a direct access device so that theyJ can be used in disk oriented operating system environments.  These devicesF are sometimes referred to as random access tape or floppy tape.  TheseJ devices might be thought of as a disk drive with one or more long tracks. G Access time to a logical block is usually longer than for a disk drive,RD since the tape must be fast forwarded or rewound to the block.  As aH result, the SEEK command will often be more useful for a tape than for aH disk.  The only way an initiator may determine if a direct-access deviceE is a tape is by using the medium type code returned by the MODE SENSEf command.   9.1.13.3 Memory mediaa  E Memory media includes devices that are traditionally used for primaryhF storage within computer systems, such as solid state static or dynamicJ random access memories (SRAM or DRAM), or magnetic core or bubble memory. D These devices are typically non-mechanical, and therefore the entireG physical medium may be accessed in virtually the same access time.  TheEG data is typically accessed as a bit or byte and this also speeds accesseH time.  Memory devices typically store less data than disks or tapes, and: are usually volatile when not protected by battery backup.  ' 9.2 Commands for direct-access devices.e  F The commands for direct-access devices shall be as shown in table 108.  >                 Table 108 - Commands for direct-access devicesI +=====================================-============-======-=============+tI |  Command name                       | Operation  | Type | Subclause   |mI |                                     |   code     |      |             |uI |-------------------------------------+------------+------+-------------|lI |  CHANGE DEFINITION                  |    40h     |   O  |   8.2.1     |eI |  COMPARE                            |    39h     |   O  |   8.2.2     | I |  COPY                               |    18h     |   O  |   8.2.3     |aI |  COPY AND VERIFY                    |    3Ah     |   O  |   8.2.4     | I |  FORMAT UNIT                        |    04h     |   M  |   9.2.1     |uI |  INQUIRY                            |    12h     |   M  |   8.2.5     |pI |  LOCK-UNLOCK CACHE                  |    36h     |   O  |   9.2.2     |tI |  LOG SELECT                         |    4Ch     |   O  |   8.2.6     | I |  LOG SENSE                          |    4Dh     |   O  |   8.2.7     |aI |  MODE SELECT(6)                     |    15h     |   O  |   8.2.8     |iI |  MODE SELECT(10)                    |    55h     |   O  |   8.2.9     | I |  MODE SENSE(6)                      |    1Ah     |   O  |   8.2.10    |gI |  MODE SENSE(10)                     |    5Ah     |   O  |   8.2.11    |rI |  PRE-FETCH                          |    34h     |   O  |   9.2.3     | I |  PREVENT-ALLOW MEDIUM REMOVAL       |    1Eh     |   O  |   9.2.4     |OI |  READ(6)                            |    08h     |   M  |   9.2.5     |cI |  READ(10)                           |    28h     |   M  |   9.2.6     |iI |  READ BUFFER                        |    3Ch     |   O  |   8.2.12    |nI |  READ CAPACITY                      |    25h     |   M  |   9.2.7     |cI |  READ DEFECT DATA                   |    37h     |   O  |   9.2.8     |nI |  READ LONG                          |    3Eh     |   O  |   9.2.9     |gI |  REASSIGN BLOCKS                    |    07h     |   O  |   9.2.10    |nI |  RECEIVE DIAGNOSTIC RESULTS         |    1Ch     |   O  |   8.2.13    |UI |  RELEASE                            |    17h     |   M  |   9.2.11    |oI |  REQUEST SENSE                      |    03h     |   M  |   8.2.14    |aI |  RESERVE                            |    16h     |   M  |   9.2.12    |aI |  REZERO UNIT                        |    01h     |   O  |   9.2.13    |oI |  SEARCH DATA EQUAL                  |    31h     |   O  |   9.2.14.1  |sI |  SEARCH DATA HIGH                   |    30h     |   O  |   9.2.14.2  |eI |  SEARCH DATA LOW                    |    32h     |   O  |   9.2.14.3  |rI |  SEEK(6)                            |    0Bh     |   O  |   9.2.15    |AI |  SEEK(10)                           |    2Bh     |   O  |   9.2.15    |oI |  SEND DIAGNOSTIC                    |    1Dh     |   M  |   8.2.15    |dI |  SET LIMITS                         |    33h     |   O  |   9.2.16    |gI |  START STOP UNIT                    |    1Bh     |   O  |   9.2.17    |cI |  SYNCHRONIZE CACHE                  |    35h     |   O  |   9.2.18    |iI |  TEST UNIT READY                    |    00h     |   M  |   8.2.16    |cI |  VERIFY                             |    2Fh     |   O  |   9.2.19    |II |  WRITE(6)                           |    0Ah     |   O  |   9.2.20    | I |  WRITE(10)                          |    2Ah     |   O  |   9.2.21    |bI |  WRITE AND VERIFY                   |    2Eh     |   O  |   9.2.22    | I |  WRITE BUFFER                       |    3Bh     |   O  |   8.2.17    | I |  WRITE LONG                         |    3Fh     |   O  |   9.2.23    |nI |  WRITE SAME                         |    41h     |   O  |   9.2.24    | I |-----------------------------------------------------------------------|rI |Key:  M = Command implementation is mandatory.                         | I |      O = Command implementation is optional.                          | I +=======================================================================+T    F The following operation codes are vendor-specific: 02h, 05h, 06h, 09h,J 0Ch, 0Dh, 0Eh, 0Fh, 10h, 11h, 13h, 14h, 19h, 20h, 21h, 22h, 23h, 24h, 26h,J 27h, 29h, 2Ch, 2Dh and C0h through FFh.  All remaining operation codes for> direct-access devices are reserved for future standardization.   9.2.1 FORMAT UNIT command   I The FORMAT UNIT command (see table 109) formats the medium into initiator A addressable logical blocks per the initiator defined options.  InuC addition, the medium may be certified and control structures may be B created for the management of the medium and defects.  There is no6 guarantee that the medium has or has not been altered.  6                        Table 109 - FORMAT UNIT commandO +=====-========-========-========-========-========-========-========-========+eO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |iO |Byte |        |        |        |        |        |        |        |        |lO |=====+=======================================================================|sO | 0   |                           Operation code (04h)                        | O |-----+-----------------------------------------------------------------------|iO | 1   | Logical unit number      | FmtData| CmpLst |   Defect list format     |eO |-----+-----------------------------------------------------------------------|tO | 2   |                           Vendor-specific                             |oO |-----+-----------------------------------------------------------------------|rO | 3   | (MSB)                                                                 | O |-----+---                        Interleave                               ---|mO | 4   |                                                                 (LSB) |rO |-----+-----------------------------------------------------------------------|aO | 5   |                           Control                                     |eO +=============================================================================+n    F The simplest mandatory form of the FORMAT UNIT command (with no formatG data) accomplishes medium formatting with little initiator control overcF defect management.  The target implementation determines the degree ofJ defect management that is to be performed.  Two additional mandatory formsI of this command increase the initiator's control over defect management. sG Several optional forms of this command further increase the initiator'srJ control over defect management, by allowing the initiator to specify whichF defect list(s) are to be used, to specify defect locations (in severalJ formats), to enable target certification, and to specify what to do in the, event that defect lists are not accessible.   J The FORMAT UNIT command shall be rejected with RESERVATION CONFLICT statusD if the logical unit is reserved, or any extent reservation, from any3 initiator, is active in the specified logical unit.e  D During the format operation, the target shall respond to commands as	 follows: tK    a)     In response to all commands except REQUEST SENSE and INQUIRY, theoI           target shall return CHECK CONDITION status unless a reservationuM           conflict exists, in which case RESERVATION CONFLICT status shall be.           returned.   I    b)     In response to the INQUIRY command, the target shall respond ast           commanded.  G    c)     In response to the REQUEST SENSE command, unless an error hasaK           occurred, the target shall return a sense key of NOT READY and an M           additional sense code of LOGICAL UNIT NOT READY FORMAT IN PROGRESS,aK           with the sense key specific bytes set for progress indication (as I           described in 8.2.14.1).  Refer to 8.2.14.2 for a description ofnM           deferred error handling that may occur during the format operation.o  O    NOTE 103 It is recommended that MODE SELECT parameters (if any) be set prior.'    to issuing the FORMAT UNIT command. e  G During the execution of the FORMAT UNIT command, the target may performnD a medium defect management algorithm (which can be controlled by theI initiator, using optional forms of this command).  Four sources of defect G location information (hereafter called defects) are defined as follows:g  I a)     Primary defect list (Plist).  This is the list of defects, usuallyaJ        supplied by the original manufacturer of the device or medium, thatM        are considered permanent defects.  The Plist is located outside of theuL        initiator-accessible logical block space.  The Plist is accessible byI        the target (to reference while formatting), but it is not normallyiF        accessible by the initiator except through the READ DEFECT DATAI        command.  Once created, the original Plist shall not be subject toe        change.  E b)     Target certification list (Clist).  This list includes defects F        detected by the target during an optional certification processL        executed during the FORMAT UNIT command.  This list shall be added to        the Glist.g  H c)     Data defect list (Dlist).  This list of defect descriptors may beK        supplied to the target by the initiator in the DATA OUT phase of thesH        FORMAT UNIT command.  This list shall be added to the Glist.  TheI        defect list length in the defect list header may be zero, in whichr         case there is no Dlist.    M d)     Grown defect list (Glist).  The Glist includes all defects sent by theoK        initiator or detected by the target.  The Glist does not include theaH        Plist.  If the CmpLst bit is zero, the Glist shall include DlistsM        provided to the target during the previous and the current FORMAT UNITc/        commands.  The Glist shall also include:l@    a)     defects detected by the format operation during medium           certification;G    b)     defects previously identified with a REASSIGN BLOCKS command; E    c)     defects previously detected by the target and automaticallyt           reallocated.  A A format data (FmtData) bit of one indicates that the FORMAT UNIT G parameter list (see table 110) shall be transferred during the DATA OUTvG phase.   The DATA OUT phase consists of a defect list header (see tablenH 111), followed by an initialization pattern descriptor, followed by zeroI or more defect descriptors.  Each defect descriptor identifies a locationrI on the medium that the target shall map out of the user-accessible area. o    :                     Table 110 - FORMAT UNIT parameter listO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |3O |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================|OO |     |                           Defect list header                          | O |=====+=======================================================================| O |     |                           Initialization pattern descriptor (if any)  |tO |=====+=======================================================================|LO |     |                           Defect descriptor(s) (if any)               |EO |=====+=======================================================================|1O | 0   |                           Defect descriptor 0                         | O |-----+---                  (See specific table for length.)               ---| O | n   |                                                                       | O |-----+-----------------------------------------------------------------------| O |     |                                  .                                    |hO |     |                                  .                                    ||O |-----+-----------------------------------------------------------------------| O | 0   |                           Defect descriptor x                         |.O |-----+---                  (See specific table for length.)               ---| O | n   |                                                                       | O +=============================================================================+C    H The  defect list header (see table 111) provides several optional formatB control bits. Targets that implement these bits give the initiatorC additional control over the use of the four defect sources, and the J formatting operation. If the initiator attempts to select any function notF implemented by the target, the target shall terminate the command withJ CHECK CONDITION status.  The sense key shall be set to ILLEGAL REQUEST andJ the additional sense code shall be set to INVALID FIELD IN PARAMETER LIST.  6                         Table 111 - Defect list headerO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |.O |=====+=======================================================================| O | 0   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------| O | 1   |  FOV   |  DPRY  |  DCRT  |  STPF  |   IP   |   DSP  |  Immed |   VS   | O |-----+-----------------------------------------------------------------------| O | 2   | (MSB)                                                                 | O |-----+---                        Defect list length                       ---| O | 3   |                                                                 (LSB) | O +=============================================================================+3    G A FmtData bit of zero indicates that a DATA OUT phase shall not occur. h2 The source of defect information is not specified.  G A complete list (CmpLst) bit of one indicates that the defect list sentpI by the initiator is a complete list of defects.  Any existing defect listpJ except the Plist shall be ignored by the target.  As a result, a new GlistH is constructed that contains the Dlist (if it is sent by the initiator),D and the Clist (if certification is enabled).  The target may add any= defects it detects during the format operation to this Dlist.7  I A CmpLst bit of zero indicates that the defect list sent by the initiatoreH is an addition to the existing list of defects.  As a result a new GlistI is constructed that contains the existing Glist, the Dlist (if it is sentmD by the initiator), and the Clist (if certification is enabled).  TheI target may add any defects it detects during the format operation to thiss Dlist.  E Table 112 defines the implementation requirements for the FORMAT UNITr command.  G       Table 112 - FORMAT UNIT defect descriptor format and requirements9O +=======-======-========-========-======-=====================================+=O |       |      | Defect | Defect |      |                                     | O |       |      |  list  |  list  |      |                                     | O |FmtData|CmpLst| format | length | Type |  Comments                           |=O |-------+------+--------+--------+------+-------------------------------------| O |   0   |   0  |  000b  |   N/A  |   M  |  Vendor-specific                    |-O |-----------------------------------------------------------------------------|fO |                                 BLOCK FORMAT                                |-O |-----------------------------------------------------------------------------| O |   1   |   0  |  000b  |  Zero  |   M  | See notes (1) and (3)               |-O |   1   |   1  |  000b  |  Zero  |   M  | See notes (1) and (4)               | O |   1   |   0  |  000b  |   >0   |   O  | See notes (2) and (3)               | O |   1   |   1  |  000b  |   >0   |   O  | See notes (2) and (4)               | O |-----------------------------------------------------------------------------|-O |                          BYTES FROM INDEX FORMAT                            | O |-----------------------------------------------------------------------------|=O |   1   |   0  |  100b  |  Zero  |   O  | See notes (1) and (3)               |dO |   1   |   1  |  100b  |  Zero  |   O  | See notes (1) and (4)               |rO |   1   |   0  |  100b  |   >0   |   O  | See notes (2) and (3)               | O |   1   |   1  |  100b  |   >0   |   O  | See notes (2) and (4)               |iO |-----------------------------------------------------------------------------|iO |                           PHYSICAL SECTOR FORMAT                            | O |-----------------------------------------------------------------------------|uO |   1   |   0  |  101b  |  Zero  |   O  | See notes (1) and (3)               |aO |   1   |   1  |  101b  |  Zero  |   O  | See notes (1) and (4)               |eO |   1   |   0  |  101b  |   >0   |   O  | See notes (2) and (3)               | O |   1   |   1  |  101b  |   >0   |   O  | See notes (2) and (4)               |iO |-----------------------------------------------------------------------------|eO |                           VENDOR-SPECIFIC FORMAT                            | O |-----------------------------------------------------------------------------|TO |   1   |   0  |  110b  |        |      |                                     |AO |   1   |   1  |  110b  |        |      |                                     |tO |-----------------------------------------------------------------------------| O |  All remaining codes are reserved.                                          |rO |-----------------------------------------------------------------------------|lO |  Key:  M = Command implementation is mandatory.                             |nO |        O = Command implementation is optional.                              |2O |-----------------------------------------------------------------------------|nO |  NOTES                                                                      |hO |    1  No Dlist is transferred to the target during the DATA OUT phase.      |oO |    2  A Dlist is transferred to the target during the DATA OUT phase.       |rO |       Add the Dlist defects to the new Glist.                               |oO |    3  Use the existing Glist as a defect source.  Add existing Glist        |rO |       defects to the new Glist.                                             |cO |    4  Discard the existing Glist. Do not add existing Glist defects to      |iO |       the new Glist.                                                        | O |    5  All the options described in this table cause a new Glist to be       |aO |       created during execution of the FORMAT UNIT command as described in   | O |       the text.                                                             |hO +=============================================================================+l    I The defect list format field specifies which defect descriptor is used if)' the FmtData bit is one (see table 112).t  J The interleave field specifies the interleave that is used when performingH the format operation.  This allows the logical blocks to be related in aJ way that facilitates matching the transfer rate  between the initiator andH the peripheral.  An interleave of zero specifies that the target use itsD default interleave.  An interleave of one specifies that consecutiveI logical blocks be placed in contiguous ascending order.  All other valuesz are vendor-specific.  H A format options valid (FOV) bit of zero indicates that the target shallH use its default settings for the DPRY, DCRT, STPF, IP and  DSP bits (seeI below). The initiator shall set these bits to zero.  If any of these bitseI are not zero, the target shall terminate the command with CHECK CONDITIONeI status.  The sense key shall be set to ILLEGAL REQUEST and the additionall< sense code  shall be set to INVALID FIELD IN PARAMETER LIST.  G A FOV bit of one indicates that the target shall examine the setting ofeJ the DPRY, DCRT, STPF, IP and DSP bits.  When the FOV bit is one, the DPRY,3 DCRT, STPF, IP and DSP bits are defined as follows.o  H A disable primary (DPRY) bit of zero indicates that the target shall notH use portions of the medium identified as defective in the primary defectE Plist for initiator addressable logical blocks.  If the target cannotlH locate the Plist or it cannot determine whether a Plist exists, it shallA perform the action specified by  the STPF bit.  A DPRY bit of oneaG indicates that the target shall not use the Plist to identify defectives/ areas of the medium.  The Plist is not deleted.   J A disable certification (DCRT) bit of zero indicates that the target shallF perform a vendor-specific medium certification operation to generate aI Clist.  A DCRT bit of one indicates that the target shall not perform any|C vendor-specific medium certification process or format verification=2 operation while executing the FORMAT UNIT command.  H The stop format (STPF) bit controls the behaviour of the target when one of the following events occurs:=L    a)     The target has been requested to use the primary defect list (DPRYL           is  set to zero), or the grown defect list (CmpLst is set to zero)N           and the target cannot locate the list nor determine whether the list           exists. L    b)     The target has been requested to use the primary defect list (DPRYK           is set to zero) or the grown defect list (CmpLst is set to zero), M           and the target encounters an error while accessing the defect list.   I A STPF bit of zero indicates that, if one or both of the above conditions J occurs, the target shall continue to execute the FORMAT UNIT command.  TheJ target shall return CHECK CONDITION status at the completion of the FORMATD UNIT command.  The sense key shall be set to RECOVERED ERROR and theI additional sense code shall be set to either DEFECT LIST NOT FOUND if the F first condition occurred, or DEFECT LIST ERROR if the second condition	 occurred.-  H A STPF bit of one indicates that, if one or both of the above conditionsE occurs, the target shall terminate the FORMAT UNIT command with CHECKeE CONDITION status.  The sense key shall be set to MEDIUM ERROR and the I additional sense code shall be set to either DEFECT LIST NOT FOUND if the=F first condition occurred, or DEFECT LIST ERROR if the second condition	 occurred.1  M    NOTE 104 The use of the FmtData bit, the CmpLst bit, and the defect headerbL    allow the initiator to control the source of the defect lists used by theI    FORMAT UNIT command. Setting the defect list length to zero allows thenN    initiator to control the use of Plist and Clist without having to specify a	    Dlist.C    J An initialization pattern (IP) bit of one indicates that an initializationI pattern descriptor (see 9.2.1.2) is included in the FORMAT UNIT parameter E list immediately following the defect list header.  An IP bit of zero=G indicates that an initialization pattern descriptor is not included and = that the target shall use its default initialization pattern.   F A disable saving parameters (DSP) bit of one specifies that the targetH shall not save the MODE SELECT savable parameters to non-volatile memoryI during the format operation.  A DSP bit of zero specifies that the target G shall save all the MODE SELECT savable parameters for all initiators to-D non-volatile memory during the format operation.  Pages that are notH reported as savable are not affected by the DSP bit (i.e. if pages 03h &I 04h are not returned with the PS bit set they may be saved even if DSP is 	 cleared).   H An immediate (Immed) bit of zero indicates that status shall be returnedD after the format operation has completed.  An Immed bit value of oneD indicates that the target shall return status as soon as the commandH descriptor block has been validated, and the entire defect list has been transferred.  ) The bit designated VS is vendor-specific.s  J The defect list length field in the defect list header specifies the totalJ length in bytes of the defect descriptors that follow and does not includeI the initialization pattern descriptor or initialization pattern, if any. eI The length of the defect descriptors varies with the format of the defectcH list. The three formats for the defect descriptor(s) field in the defect lists are shown in 9.2.1.1.s   9.2.1.1 Defect list formatsa  F This clause describes the defect list formats used in the FORMAT UNIT,F READ DEFECT DATA and translate page of the SEND DIAGNOSTIC and RECEIVE DIAGNOSTIC RESULTS commands.  P    NOTE 105 The selected reporting format accounts for variables that impact theM    information in the returned data.  For example, the specific location of aiK    defect, while constant in angular and radial location on the device, mayrI    change in reported location a format operation with different geometryiM    parameters is performed.  It is the responsibility of the initiator to usedO    a defect list format appropriate for the intended operation with the current=K    or future geometry parameters.  If the target is able to detect that the M    selected defect list format would provide inconsistent results, the target %    may return CHECK CONDITION status.   I Each block format defect descriptor (see table 113) specifies a four-byte 1 defective block address that contains the defect.-  =                  Table 113 - Defect descriptor - Block format/O +=====-========-========-========-========-========-========-========-========+-O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |-O |=====+=======================================================================|rO | 0   | (MSB)                                                                 |rO |- - -+---                     Defective block address                     ---|0O | 3   |                                                                 (LSB) |0O +=============================================================================+-    B The defect list length is equal to four times the number of defect descriptors.  C The defect descriptors should be in ascending order.  More than one-G physical or logical block may be affected by each defect descriptor.  A|F target may return CHECK CONDITION if the defect descriptors are not in ascending order.  D Each byte from index defect descriptor (see table 114) specifies the; location of a defect that is no more than eight bytes long.   B            Table 114 - Defect descriptor - Bytes from index formatO +=====-========-========-========-========-========-========-========-========+-O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |-O |=====+=======================================================================| O | 0   | (MSB)                                                                 | O |- - -+---                        Cylinder number of defect                ---| O | 2   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|-O | 3   |                           Head number of defect                       | O |-----+-----------------------------------------------------------------------|-O | 4   | (MSB)                                                                 | O |- - -+---                        Defect bytes from index                  ---| O | 7   |                                                                 (LSB) |-O +=============================================================================+     C The defect list length is equal to eight times the number of defect- descriptors.  G Each descriptor is comprised of the cylinder number of defect, the head E number of defect, and the defect bytes from index to the defect.  The F defect descriptors shall be in ascending order. The cylinder number ofG defect is the most significant part of the address and the defect bytes G from index is the least significant part of the address.  More than onerH physical or logical block may be affected by each defect.  If the defectI bytes from index has a value of FFFFFFFFh, this indicates that the entireh$ track shall be considered defective.  D Each physical sector defect descriptor (see table 115) specifies the4 location of a defect that is the length of a sector.  B             Table 115 - Defect descriptor - Physical sector formatO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================| O | 0   | (MSB)                                                                 |=O |- - -+---                        Cylinder number of defect                ---| O | 2   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|eO | 3   |                           Head number of defect                       |bO |-----+-----------------------------------------------------------------------|nO | 4   | (MSB)                                                                 |gO |- - -+---                        Defective sector number                  ---| O | 7   |                                                                 (LSB) |eO +=============================================================================+g    C The defect list length is equal to eight times the number of defectb descriptors.  E Each descriptor is comprised of a cylinder number of defect, the headrJ number of defect, and the defective sector number.  The defect descriptorsG shall be in ascending order.  The cylinder number of defect is the most F significant part of the address and the defective sector number is theB least significant part of the address.  More than one block may beA affected by each defect descriptor.  A defective sector number ofDH FFFFFFFFh indicates that the entire track shall be considered defective.  % 9.2.1.2 Initialization pattern optionh  C The initialization pattern option specifies that the logical blocksiI contain the specified initialization pattern.  The initialization patternhF descriptor (see table 116) is sent to the target as part of the FORMAT UNIT parameter list.  =                 Table 116 - Initialization pattern descriptor O +=====-========-========-========-========-========-========-========-========+fO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |iO |=====+=================+=====================================================|hO | 0   |   IP modifier   |                    Reserved                         |fO |-----+-----------------------------------------------------------------------|SO | 1   |                           Pattern type                                |cO |-----+-----------------------------------------------------------------------|PO | 2   | (MSB)                                                                 | O |-----+---                Initialization pattern length                    ---| O | 3   |                                                                 (LSB) |cO |-----+-----------------------------------------------------------------------|oO | 4   |                                                                       | O |-----+---                Initialization pattern                           ---|nO | n   |                                                                       |aO +=============================================================================+m    P    NOTE 106 The initialization pattern option is not intended for media analysisN    or certification.  This option may only initialize the initiator accessibleP    area of the media to the specified pattern and may not write to any initiator"    inaccessible areas of the disk.  F The IP modifier field specifies the type and location of a header that4 modifies the initialization pattern (see table 117).  <                  Table 117 - Initialization pattern modifierO +=============-===============================================================+TO | IP modifier |   Description                                                 |bO |-------------+---------------------------------------------------------------| O |     00b     |   No header. The target shall not modify the initialization   |tO |             |   pattern.                                                    |iO |     01b     |   The target shall overwrite the initialization pattern to    |tO |             |   write the logical block address in the first four bytes of  |lO |             |   the logical block.  The logical block address shall be      |aO |             |   written with the most significant byte first.               |nO |     10b     |   The target shall overwrite the initialization pattern to    | O |             |   write the logical block address in the first four bytes of  |oO |             |   each physical block contained within the logical block.  The|aO |             |   The lowest numbered logical block or part thereof that      |DO |             |   occurs within the physical block is used.  The logical block|eO |             |   address shall be written with the most significant byte     |hO |             |   first.                                                      | O |     11b     |   Reserved.                                                   |sO +=============================================================================+e    H The initialization pattern type field (see table 118) indicates the typeG of pattern the target shall use to initialize each logical block withinsC the initiator accessible portion of the medium.  All bytes within asD logical block shall be written with the initialization pattern.  TheH initialization pattern is modified by the IP modifier field as described
 in table 117.   :                    Table 118 - Initialization pattern typeC +==============-==================================================+ C |Initialization|  Description                                     |fC | pattern type |                                                  |sC |--------------+--------------------------------------------------|hC |     00h      |  Use default pattern. (note 1)                   |OC |     01h      |  Repeat the initialization pattern as            |eC |              |  required to fill the logical block. (note 2)    |rC |  02h - 7Fh   |  Reserved                                        |iC |  80h - FFh   |  Vendor-specific                                 |iC |-----------------------------------------------------------------|eC |  Notes                                                          | C |  1)  If the initialization pattern length is not zero the target| C |  shall terminate the command with CHECK CONDITION status.  The  |sC |  sense key shall be set to ILLEGAL REQUEST and the additional   | C |  sense code to INVALID FIELD IN PARAMETER LIST.                 | C |  2)  If the initialization pattern length is zero the target    |tC |  shall terminate the command with CHECK CONDITION status.  The  |nC |  sense key shall be set to ILLEGAL REQUEST and the additional   |oC |  sense code to INVALID FIELD IN PARAMETER LIST.                 |=C +=================================================================+     E The initialization pattern length field indicates the number of bytes C contained in the initialization pattern.  If the length exceeds the=F current logical block size the target shall terminate the command withJ CHECK CONDITION status.  The sense key shall be set to ILLEGAL REQUEST andK the additional sense code shall be set to INVALID FIELD IN PARAMETER LIST.  1 The pattern is modified by the IP modifier field.      9.2.2 LOCK UNLOCK CACHE command=  F The LOCK UNLOCK CACHE command (see table 119) requests that the targetI disallow or allow logical blocks within the specified range to be removed.J from the cache memory by the target's cache replacement algorithm.  LockedH logical blocks may be written to the medium when modified, but a copy of< the modified logical block shall remain in the cache memory.  9                     Table 119 - LOCK UNLOCK CACHE commandiO +=====-========-========-========-========-========-========-========-========+hO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |mO |Byte |        |        |        |        |        |        |        |        |=O |=====+=======================================================================| O | 0   |                           Operation code (36h)                        | O |-----+-----------------------------------------------------------------------|=O | 1   | Logical unit number      |         Reserved         |  Lock  | RelAdr | O |-----+-----------------------------------------------------------------------|-O | 2   | (MSB)                                                                 | O |-----+---                                                                 ---|-O | 3   |                                                                       | O |-----+---                        Logical block address                    ---|-O | 4   |                                                                       | O |-----+---                                                                 ---|-O | 5   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|=O | 6   |                           Reserved                                    |cO |-----+-----------------------------------------------------------------------|aO | 7   | (MSB)                                                                 |tO |-----+---                        Number of blocks                         ---|oO | 8   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|eO | 9   |                           Control                                     |FO +=============================================================================+p    I A lock bit of one indicates that any logical block in the specified rangeeH that is currently present in the cache memory shall be locked into cacheI memory.  Only logical blocks that are already present in the cache memory=J are actually locked.  A lock bit of zero indicates that all logical blocksF in the specified range that are currently locked into the cache memory/ shall be unlocked, but not necessarily removed.   G A relative address (RelAdr) bit of one indicates that the logical block=C address field is a two's complement displacement.  This negative or F positive displacement shall be added to the logical block address lastG accessed on the logical unit to form the logical block address for this D command.  This feature is only available when linking commands.  TheJ feature requires that a previous command in the linked group have accessed$ a block of data on the logical unit.  C A RelAdr bit of zero indicates that the logical block address field-F specifies the first logical block of the range of logical blocks to be operated on by this command.  E The number of blocks specifies the total number of contiguous logical I blocks within the range.  A number of blocks field of zero indicates that D all remaining logical blocks on the logical unit shall be within the range.    I Multiple locks may be in effect from more than one initiator.  Locks fromsG different initiators may overlap.  An unlock of an overlapped area does * not release the lock of another initiator.   9.2.3 PRE-FETCH commandv  G The PRE-FETCH command (see table 120) requests that the target transfer C the specified logical blocks to the cache memory.  No data shall bes transferred to the initiator.e  5                         Table 120 - PRE-FETCH commandaO +=====-========-========-========-========-========-========-========-========+rO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |fO |=====+=======================================================================|iO | 0   |                           Operation code (34h)                        |oO |-----+-----------------------------------------------------------------------|pO | 1   | Logical unit number      |         Reserved         | Immed  | RelAdr |=O |-----+-----------------------------------------------------------------------| O | 2   | (MSB)                                                                 | O |-----+---                                                                 ---|=O | 3   |                                                                       | O |-----+---                        Logical block address                    ---|-O | 4   |                                                                       | O |-----+---                                                                 ---|-O | 5   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------| O | 6   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|-O | 7   | (MSB)                                                                 | O |-----+---                        Transfer length                             | O | 8   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|=O | 9   |                           Control                                     |nO +=============================================================================+     G An immediate (Immed) bit of one indicates that status shall be returnedoI as soon as the command descriptor block has been validated.  An Immed bitfF of zero indicates that status shall be returned after the operation is	 complete.t  J See 9.2.2 for a definition of the RelAdr bit and the logical block address field.  D The transfer length field specifies the number of contiguous logicalG blocks of data that shall be transferred to the target's cache memory.  I A transfer length of zero indicates that the contiguous logical blocks up-D to and including the last logical block of the logical unit shall beH transferred to the target's cache memory.  Any other value indicates theI number of logical blocks that shall be transferred.  The target may electaF to not transfer logical blocks that already are contained in the cache memory.   > If the Immed bit is zero and the specified logical blocks wereE successfully transferred to the cache memory, the target shall returnaE CONDITION MET status.  If the link bit (see 7.2.7) is one, the target / shall return INTERMEDIATE-CONDITION MET status.e  I If Immed is one, and the unlocked cache memory has sufficient capacity toaC accept all of the specified logical blocks, the target shall returnhE CONDITION MET status.  If the link bit (see 7.2.7) is one, the target / shall return INTERMEDIATE-CONDITION MET status.h  G If Immed is one, and the unlocked cache memory does not have sufficientsH capacity to accept all of the specified logical blocks, the target shallF return GOOD status.  The target shall transfer to cache memory as manyD logical blocks as will fit.  If the link bit (see 7.2.7) is one, the( target shall return INTERMEDIATE status.  * 9.2.4 PREVENT ALLOW MEDIUM REMOVAL command  J The PREVENT ALLOW MEDIUM REMOVAL command (see table 121) requests that theH target enable or disable the removal of the medium in the logical unit. I This mechanism is independent of device reservations and the target shallpF not allow medium removal if any initiator currently has medium removal
 prevented.  ?                Table 121 - PREVENT ALLOW MEDIUM REMOVAL command O +=====-========-========-========-========-========-========-========-========+8O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |=O |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================|-O | 0   |                           Operation code (1Eh)                        ||O |-----+-----------------------------------------------------------------------|eO | 1   | Logical unit number      |                  Reserved                  |lO |-----+-----------------------------------------------------------------------| O | 2   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|tO | 3   |                           Reserved                                    |tO |-----+-----------------------------------------------------------------------|dO | 4   |                           Reserved                           | Prevent|EO |-----+-----------------------------------------------------------------------| O | 5   |                           Control                                     | O +=============================================================================+e    H The prevention of medium removal shall begin when any initiator issues aF PREVENT ALLOW MEDIUM REMOVAL command with a prevent bit of one (mediumJ removal prevented).  The prevention of medium removal for the logical unit shall terminate:G    a)     after all initiators that have medium removal prevented issue.K           PREVENT ALLOW MEDIUM REMOVAL commands with a prevent bit of zero,mG           and the target has successfully performed a synchronize cachee           operation;L    b)     upon the receipt of a BUS DEVICE RESET message from any initiator;           or&    c)     upon a hard RESET condition.  F While a prevention of medium removal condition is in effect the targetH shall inhibit mechanisms that normally allow removal of the medium by an	 operator.p   9.2.5 READ(6) commande  J The READ(6) command (see table 122) requests that the target transfer dataF to the initiator.  The most recent data value written in the addressed" logical block shall be returned.    4                          Table 122 - READ(6) commandO +=====-========-========-========-========-========-========-========-========+=O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================|=O | 0   |                           Operation code (08h)                        |oO |-----+-----------------------------------------------------------------------|-O | 1   | Logical unit number      | (MSB)                                      |sO |-----+------------------------------                                      ---|-O | 2   |                           Logical block address                       | O |-----+---                                                                 ---| O | 3   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|cO | 4   |                           Transfer length                             | O |-----+-----------------------------------------------------------------------| O | 5   |                           Control                                     | O +=============================================================================+-    F The cache control bits (see 9.2.6) are not provided for this command. I Targets with cache memory may have values for the cache control bits that-H affect the READ(6) command; however, no default value is defined by thisF International Standard.  If explicit control is required, the READ(10) command should be used.o  H The logical block address field specifies the logical block at which the read operation shall begin.   D The transfer length field specifies the number of contiguous logicalF blocks of data to be transferred.  A transfer length of zero indicatesH that 256 logical blocks shall be transferred.  Any other value indicates7 the number of logical blocks that shall be transferred.t   9.2.6 READ(10) command  F The READ(10) command (see table 123) requests that the target transferA data to the initiator.  The most recent data value written in thes+ addressed logical block shall be returned. =  5                          Table 123 - READ(10) command O +=====-========-========-========-========-========-========-========-========+hO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |(O |Byte |        |        |        |        |        |        |        |        |mO |=====+=======================================================================| O | 0   |                           Operation code (28h)                        |bO |-----+-----------------------------------------------------------------------|mO | 1   |   Logical unit number    |   DPO  |   FUA  |     Reserved    | RelAdr |eO |-----+-----------------------------------------------------------------------| O | 2   | (MSB)                                                                 |oO |-----+---                                                                 ---|iO | 3   |                                                                       |oO |-----+---                        Logical block address                    ---|aO | 4   |                                                                       | O |-----+---                                                                 ---| O | 5   |                                                                 (LSB) |-O |-----+-----------------------------------------------------------------------|tO | 6   |                           Reserved                                    |rO |-----+-----------------------------------------------------------------------|mO | 7   | (MSB)                                                                 |=O |-----+---                        Transfer length                             | O | 8   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|=O | 9   |                           Control                                     | O +=============================================================================+-    J A disable page out (DPO) bit of one indicates that the target shall assignI the logical blocks accessed by this command the lowest priority for being-F fetched into or retained by the cache.  A DPO bit of one overrides anyH retention priority specified in the cache page (see 9.3.3.1).  A DPO bitC of zero indicates the priority shall be determined by the retention F priority fields in the cache page.  All other aspects of the algorithmJ implementing the cache memory replacement strategy are not defined by this International Standard.   O    NOTE 107 The DPO bit is used to control replacement of logical blocks in the P    cache memory when the host has information on the future usage of the logicalK    blocks.  If the DPO bit is set to one, the host knows the logical blocks-J    accessed by the command are not likely to be accessed again in the nearM    future and should not be put in the cache memory nor retained by the cache-H    memory.  If the DPO bit is zero, the host expects that logical blocksO    accessed by this command are likely to be accessed again in the near future.   D A force unit access (FUA) bit of one indicates that the target shallK access the media in performing the command prior to returning GOOD status. -G  Read commands shall access the specified logical blocks from the media G (i.e.  the data is not directly retrieved from the cache).  In the case J where the cache contains a more recent version of a logical block than theD media, the logical block shall first be written to the media.  WriteC commands shall not return GOOD status until the logical blocks havetH actually been written on the media (i.e. the data is not write cached).   G An FUA bit of zero indicates that the target may satisfy the command bytI accessing the cache memory.  For read operations, any logical blocks thateE are contained in the cache memory may be transferred to the initiatoreI directly from the cache memory.  For write operations, logical blocks mayhI be transferred directly to the cache memory.  GOOD status may be returnedcH to the initiator prior to writing the logical blocks to the medium.  AnyH error that occurs after the GOOD status is returned is a deferred error,F and information regarding the error is not reported until a subsequent command.  J See 9.2.2 for a definition of the RelAdr bit and the logical block address field.  D The transfer length field specifies the number of contiguous logicalD blocks of data that shall be transferred.  A transfer length of zeroF indicates that no logical blocks shall be transferred.  This conditionG shall not be considered an error.  Any other value indicates the numberc, of logical blocks that shall be transferred.   9.2.7 READ CAPACITY command   B The READ CAPACITY command (see table 124) provides a means for theF initiator to request information regarding the capacity of the logical unit.a  7                       Table 124 - READ CAPACITY commandlO +=====-========-========-========-========-========-========-========-========+eO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |kO |Byte |        |        |        |        |        |        |        |        |RO |=====+=======================================================================|eO | 0   |                           Operation code (25h)                        |mO |-----+-----------------------------------------------------------------------|tO | 1   | Logical unit number      |             Reserved              | RelAdr |rO |-----+-----------------------------------------------------------------------|mO | 2   | (MSB)                                                                 |=O |-----+---                                                                 ---| O | 3   |                                                                       | O |-----+---                        Logical block address                    ---|=O | 4   |                                                                       | O |-----+---                                                                 ---|-O | 5   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|-O | 6   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|-O | 7   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|-O | 8   |                           Reserved                           |  PMI   |eO |-----+-----------------------------------------------------------------------|-O | 9   |                           Control                                     | O +=============================================================================+=    J See 9.2.2 for a definition of the RelAdr bit and the logical block address field.  G The logical block address shall be zero if the PMI bit is zero.  If the E PMI bit is zero and the logical block address is not zero, the targetlD shall return a CHECK CONDITION status, the sense key shall be set toJ ILLEGAL REQUEST and the additional sense code set to ILLEGAL FIELD IN CDB.  H A partial medium indicator (PMI) bit of zero indicates that the returnedI logical block address and the block length in bytes are those of the last $ logical block on the logical unit.    F A PMI bit of one indicates that the returned logical block address andH block length in bytes are those of the logical block address after whichH a substantial delay in data transfer will be encountered.  This returnedI logical block address shall be greater than or equal to the logical blockhG address specified by the RelAdr and logical block address fields in thet command descriptor block.     N    NOTE 108 This function is intended to assist storage management software inP    determining whether there is sufficient space on the current track, cylinder,H    etc., to contain a frequently accessed data structure, such as a file>    directory or file index, without incurring an access delay.  G The READ CAPACITY data (see table 125) shall be sent during the DATA IN= phase of the command.=  6                         Table 125 - READ CAPACITY dataO +=====-========-========-========-========-========-========-========-========+-O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================| O | 0   | (MSB)                                                                 | O |- - -+---                        Returned logical block address           ---| O | 3   |                                                                 (LSB) |-O |-----+-----------------------------------------------------------------------|tO | 4   | (MSB)                                                                 |-O |- - -+---                        Block length In bytes                    ---| O | 7   |                                                                 (LSB) |=O +=============================================================================+p     9.2.8 READ DEFECT DATA command  E The READ DEFECT DATA command (see table 126) requests that the targett1 transfer the medium defect data to the initiator.d9                      Table 126 - READ DEFECT DATA commandlO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |hO |Byte |        |        |        |        |        |        |        |        |aO |=====+=======================================================================| O | 0   |                           Operation code (37h)                        |aO |-----+-----------------------------------------------------------------------|aO | 1   | Logical unit number      |                  Reserved                  |nO |-----+--------------------------+--------------------------------------------| O | 2   |          Reserved        | Plist  | Glist  | Defect list format       |=O |-----+-----------------------------------------------------------------------| O | 3   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|=O | 4   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|-O | 5   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|-O | 6   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------| O | 7   | (MSB)                                                                 | O |-----+---                        Allocation length                           | O | 8   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------| O | 9   |                           Control                                     | O +=============================================================================+-    B If the target is unable to access any medium defect data, it shallG terminate the command with CHECK CONDITION status.  The sense key shall-G be set to either MEDIUM ERROR, if a medium error occurred, or NO SENSE, I if the list does not exist; and the additional sense code shall be set to= DEFECT LIST NOT FOUND.  K    NOTE 109 Some targets may not be able to return medium defect data until ?    after a FORMAT UNIT command has been completed successfully.-  G A primary defect list (Plist) bit of one request that the target return=J the primary list of defects.  A Plist bit of zero requests that the target' not return the primary list of defects.=  I A grown defect list (Glist) bit of one request that the target return thebD grown defect list.  A Glist bit of zero requests that the target not return the grown defect list.e  I A Plist bit of one and a Glist bit of one requests that the target returnoK the primary and the grown defect lists.  The  order in which the lists are )D returned is vendor-specific.  Whether the lists are merged or not is vendor-specific. i  D A Plist bit of zero and a Glist bit of zero requests that the target# return only the defect list header.t  E The defect list format field is used by the initiator to indicate thehG preferred format for the defect list.  This field is intended for thosecD targets capable of returning more than one format, as defined in theG FORMAT UNIT command (see 9.2.1.2, defect list format).  A target unablelJ to return the requested format shall return the defect list in its defaultJ format (see the defect list format field in the defect list header below).  G If the requested defect list format and the returned defect list formatiD are not the same, the target shall transfer the defect data and thenG terminate the command with CHECK CONDITION status.  The sense key shalltG be set to RECOVERED ERROR and the additional sense code shall be set to  DEFECT LIST NOT FOUND.    E The READ DEFECT DATA defect list (see table 127) contains a four-byte 4 header, followed by zero or more defect descriptors.  ;                    Table 127 - READ DEFECT DATA defect listiO +=====-========-========-========-========-========-========-========-========+oO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |sO |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================|sO | 0   |                           Reserved                                    |eO |-----+-----------------------------------------------------------------------|hO | 1   |          Reserved        | Plist  | Glist  | Defect list format       |tO |-----+-----------------------------------------------------------------------| O | 2   | (MSB)                                                                 |sO |-----+---                        Defect list length                          |eO | 3   |                                                                 (LSB) |dO |=====+=======================================================================|bO |     |                           Defect descriptor(s) (if any)               |eO |=====+=======================================================================|iO | 0   |                           Defect descriptor 0                         |lO |-----+---                  (See specific table for length.)               ---|EO | n   |                                                                       |tO |-----+-----------------------------------------------------------------------| O |     |                                  .                                    |=O |     |                                  .                                    | O |-----+-----------------------------------------------------------------------| O | 0   |                           Defect descriptor x                         |=O |-----+---                  (See specific table for length.)               ---| O | n   |                                                                       |-O +=============================================================================+     H A Plist bit of one indicates that the data returned contains the primaryG defect list.  A Plist bit of zero indicates that the data returned does $ not contain the primary defect list.  F A Glist bit of one indicates that the data returned contains the grownG defect list.  A Glist bit of zero indicates that the data returned does " not contain the grown defect list.  ? The defect list format field indicates the format of the defect-H descriptors returned by the target.  This field is defined in the FORMAT UNIT command (see 9.2.1.2).   G    NOTE 110 The use of the block format is not recommended. There is no I    universal model that sensibly defines the meaning of the logical block-M    address of a defect.  In the usual case, a defect that has been reassigned )    no longer has a logical block address.   E Defect descriptors returned in the block format are vendor-specific. -H Defect descriptors returned in the physical sector format may or may notA include defects in areas not accessible to the initiator.  Defect-I descriptors returned in bytes-from-index format shall comprise a complete I list of defects.  A complete list of defects may include defects in areas-> not within the capacity returned in the READ CAPACITY command.  H The defect list length field specifies the length in bytes of the defectJ descriptors that follow.  The defect list length is equal to four or eightF times the number of defect descriptors, depending on the format of the# returned descriptors (see 9.2.1.1).l  F If the allocation length is insufficient to transfer all of the defectH descriptors, the defect list length shall not be adjusted to reflect theE truncation.  The target shall not create CHECK CONDITION status.  TheoE initiator is responsible for comparing the defect list length and the A allocation length to ensure that a partial list was not received.   P    NOTE 111 The initiator may determine the length of the defect list by sendingP    the READ DEFECT DATA command with an allocation length of   four.  The targetL    will return the defect list header that contains the length of the defect    list.  F The defect descriptors may or may not be sent in ascending order.  TheJ initiator may determine the exact number of defects by dividing the defectH list length by the length of a single defect descriptor for the returned format.l   9.2.9 READ LONG commandt  G The READ LONG command (see table 128) requests that the target transferaG data to the initiator.  The data passed during the READ LONG command ishC vendor-specific, but shall include the data bytes and the ECC bytes F recorded on the medium.  The most recent data written in the addressed  logical block shall be returned.  5                         Table 128 - READ LONG commandAO +=====-========-========-========-========-========-========-========-========+TO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |=O |Byte |        |        |        |        |        |        |        |        |0O |=====+=======================================================================| O | 0   |                           Operation code (3Eh)                        |=O |-----+-----------------------------------------------------------------------| O | 1   |  Logical unit number      |        Reserved         | CORRCT | RelAdr | O |-----+-----------------------------------------------------------------------|LO | 2   | (MSB)                                                                 |-O |-----+---                                                                 ---| O | 3   |                                                                       | O |-----+---                        Logical block address                    ---|LO | 4   |                                                                       |=O |-----+---                                                                 ---|aO | 5   |                                                                 (LSB) |tO |-----+-----------------------------------------------------------------------|-O | 6   |                           Reserved                                    ||O |-----+-----------------------------------------------------------------------||O | 7   | (MSB)                                                                 |=O |-----+---                        Byte transfer length                        | O | 8   |                                                                 (LSB) |-O |-----+-----------------------------------------------------------------------| O | 9   |                           Control                                     |-O +=============================================================================+     K    NOTE 112 Any other bytes that can be corrected by ECC should be included-N    (e.g. data synchronization mark within the area covered by ECC).  It is notP    important for the ECC bytes to be at the end of the data bytes; however, they8    should be in the same order as they are on the media.  J A corrected (CORRCT) bit of zero causes a logical block to be read withoutG any correction made by the target.  A CORRCT bit of one causes the data-A to be corrected by ECC before being transferred to the initiator.   J See 9.2.2 for a definition of the RelAdr bit and the logical block address field.  I The byte transfer length field should specify exactly the number of bytes E of data that are available for transfer.  If a non-zero byte transfer-I length does not exactly match the available data length, the target shall I terminate the command with CHECK CONDITION status, the sense key shall be H set to ILLEGAL REQUEST and an additional sense code set to INVALID FIELDG IN CDB.  The valid and ILI bits shall be set to one and the information-F field shall be set to the difference (residue) of the requested lengthH minus the actual length in bytes.  Negative values shall be indicated by two's complement notation.    ? A byte transfer length of zero indicates that no bytes shall bef3 transferred and shall not be considered an error.  a   9.2.10 REASSIGN BLOCKS command  B The REASSIGN BLOCKS command (see table 129) requests the target toG reassign the defective logical blocks to another area on the medium setnJ aside for this purpose.  The target should also record the location of theC defective logical blocks to the grown defect list if such a list iseG supported.  More than one physical or logical block may be relocated byfJ each defect descriptor sent by the initiator.  This command does not alterG the contents or location of the Plist (see 9.2.1, FORMAT UNIT command).h  8                      Table 129 - REASSIGN BLOCKS commandO +=====-========-========-========-========-========-========-========-========+tO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |rO |=====+=======================================================================| O | 0   |                           Operation code (07h)                        |iO |-----+-----------------------------------------------------------------------|eO | 1   | Logical unit number      |                  Reserved                  | O |-----+-----------------------------------------------------------------------|iO | 2   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------| O | 3   |                           Reserved                                    |tO |-----+-----------------------------------------------------------------------|qO | 4   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|EO | 5   |                           Control                                     |iO +=============================================================================+A    E The initiator transfers a defect list that contains the logical blockeJ addresses to be reassigned.  The target shall reassign the physical mediumG used for each logical block address in the list.  The data contained in=G the logical blocks specified in the defect list may be altered, but the B data in all other logical blocks on the medium shall be preserved.  J    NOTE 113 The effect of specifying a logical block to be reassigned thatP    previously has been reassigned is to reassign the block again.  Over the lifeP    of the medium, a logical block can be assigned to multiple physical addresses6    until no more spare locations remain on the medium.  D The REASSIGN BLOCKS defect list (see table 130) contains a four-byteF header followed by one or more defect descriptors.  The length of each  defect descriptor is four bytes.  :                    Table 130 - REASSIGN BLOCKS defect listO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |=O |=====+=======================================================================| O | 0   |                           Reserved                                    |=O |-----+-----------------------------------------------------------------------| O | 1   |                           Reserved                                    |-O |-----+-----------------------------------------------------------------------| O | 2   | (MSB)                                                                 |-O |-----+---                        Defect list length                       ---| O | 3   |                                                                 (LSB) | O |=====+=======================================================================|-O |     |                        Defect descriptor(s)                           | O |=====+=======================================================================|-O | 0   | (MSB)                                                                 | O |- - -+---                     Defect logical block address                ---|=O | 3   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|tO |     |                                  .                                    |eO |     |                                  .                                    |eO |-----+-----------------------------------------------------------------------|iO | 0   | (MSB)                                                                 |lO |- - -+---                     Defect logical block address                ---|fO | 3   |                                                                 (LSB) |bO +=============================================================================+a  G The defect list length field specifies the total length in bytes of thekH defect descriptors that follow.  The defect list length is equal to fourF times the number of defect descriptors and does not include the defect list header length.   H The defect descriptor specifies a four-byte defect logical block addressG that contains the defect.  The defect descriptors shall be in ascendingt order.  D If the logical unit has insufficient capacity to reassign all of theE logical blocks specified in the defect descriptors, the command shallfD terminate with CHECK CONDITION status, the sense key shall be set toC HARDWARE ERROR and the additional sense code set to NO DEFECT SPAREb LOCATION AVAILABLE.  s  H If the logical unit is unable to successfully complete a REASSIGN BLOCKSI command, the command shall terminate with CHECK CONDITION status with theiF appropriate sense information.  The logical block address of the firstJ defect descriptor not reassigned shall be returned in the command-specificD information field of the sense data.  If information about the firstH defect descriptor not reassigned is not available, or if all the defects; have been reassigned, this field shall be set to FFFFFFFFh.y  H If the REASSIGN BLOCKS command failed due to an unexpected unrecoverableH read error that would cause the loss of data in a block not specified inE the defect list, the logical block address of the unrecoverable blockeJ shall be returned in the information field of the sense data and the valid bit shall be set to one.  M    NOTE 114 If the REASSIGN BLOCKS command returns CHECK CONDITION status andoM    the sense data command-specific information field contains a valid logicaluM    block address, the initiator should remove all defect descriptors from thetL    defect list prior to the one returned in the command-specific informationH    field. If the sense key is MEDIUM ERROR and the valid bit is one (theK    information field contains the valid block address) the initiator shouldaK    insert that new defective logical block address into the defect list and=P    reissue the REASSIGN BLOCKS command with the new defect list.  Otherwise, theM    initiator should perform any corrective action indicated by the sense data I    and then reissue the REASSIGN BLOCKS command with the new defect list.=   9.2.11 RELEASE command  C The RELEASE command (see table 131) is used to release a previously G reserved logical unit, or, if the extent release option is implemented,-= to release previously reserved extents within a logical unit.   4                          Table 131 - RELEASE commandO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |-O |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================|-O | 0   |                           Operation code (17h)                        | O |-----+-----------------------------------------------------------------------|-O | 1   | Logical unit number      | 3rdPty | Third party device ID    | Extent | O |-----+-----------------------------------------------------------------------|-O | 2   |                           Reservation identification                  | O |-----+-----------------------------------------------------------------------|-O | 3   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|-O | 4   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|-O | 5   |                           Control                                     | O +=============================================================================+=    @ The RESERVE and RELEASE commands provide the basic mechanism forG contention resolution in multiple-initiator systems.  A reservation maylG only be released by the initiator that made it.  It is not an error fordF an initiator to attempt to release a reservation that is not currentlyG valid, or is held by another initiator.  In this case, the target shalle: return GOOD status without altering any other reservation.  O    NOTE 115 The reservation queuing option in X3.131-1986 has been removed fromo
    SCSI-2.   9.2.11.1 Logical unit releaseC  G Implementation of logical unit release is mandatory.  If the extent bitoH is zero, this command shall cause the target to terminate all non-third-C party logical unit and extent reservations that are active from thehI initiator to the specified logical unit.  The reservation ID field in theo2 command descriptor block is ignored by the target.   9.2.11.2 Extent releasem  G Implementation of extent release is optional.  If the extent bit is oneQJ and the extent release option is not implemented, then the RELEASE commandG shall be terminated with CHECK CONDITION status and the sense key shalltJ be set to ILLEGAL REQUEST.  This option shall be implemented if the extent1 reservation option (see 9.2.12.2) is implemented.w  F If the extent bit is one and the extent release option is implemented,F this command shall cause any reservation from the requesting initiatorC with a matching reservation identification to be terminated.  OthersB reservations from the requesting initiator shall remain in effect.   9.2.11.3 Third-party release  G Implementation of third-party release is mandatory. Third-party releasetI allows an initiator to release a logical unit or extents within a logicaltE unit that were previously reserved using third-party reservation (seetH 9.2.12.3).  Third-party release shall be implemented and is intended for< use in multiple-initiator systems that use the COPY command.  J If the third-party (3rdPty) bit is zero, then a third-party release is notF requested.  If the 3rdPty bit is one then the target shall release theG specified logical unit or extents, but only if the reservation was made G using a third-party reservation by the initiator that is requesting the|G release for the same SCSI device as specified in the third-party device=	 ID field.=  H If the 3rdPty bit is one the target shall not modify the mode parametersD for commands received from the third-party device even if the targetE implements the transfer of mode parameters with a third-party RESERVE  command.  M    NOTE 116 If a target implements independent storage of mode parameters for-H    each initiator, a third-party RESERVE command copies the current modeL    parameters for the initiator that sent the RESERVE command to the currentH    mode parameters for the initiator specified as the third-party deviceK    (usually a copy master device).  A unit attention condition notifies the-H    third-party of the changed mode parameters due to the reservation.  AJ    successful third-party RELEASE command  does not return the third-partyN    devices' current mode parameters back to their previous values.  The third-J    party device can issue MODE SENSE and MODE SELECT commands to query and!    modify the mode parameters.   =   9.2.12 RESERVE command  I The RESERVE command (see table 132) is used to reserve a logical unit or,nI if the extent reservation option is implemented, extents within a logicals unit.e  4                          Table 132 - RESERVE commandO +=====-========-========-========-========-========-========-========-========+sO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |bO |Byte |        |        |        |        |        |        |        |        |gO |=====+=======================================================================| O | 0   |                           Operation code (16h)                        |aO |-----+-----------------------------------------------------------------------|BO | 1   | Logical unit number      | 3rdPty | Third party device ID    | Extent | O |-----+-----------------------------------------------------------------------| O | 2   |                           Reservation identification                  |=O |-----+-----------------------------------------------------------------------| O | 3   | (MSB)                                                                 | O |-----+---                        Extent list length                       ---|=O | 4   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|-O | 5   |                           Control                                     | O +=============================================================================+-    @ The RESERVE and RELEASE commands provide the basic mechanism forE contention resolution in multiple-initiator systems.  The third-party F reservation allows logical units or extents to be reserved for another specified SCSI device.  O    NOTE 117 The reservation queuing option in X3.131-1986 has been removed from=
    SCSI-2.  ! 9.2.12.1 Logical unit reservation=  G Implementation of logical unit reservation is mandatory.  If the extent G bit is zero, this command shall request that the entire logical unit be=H reserved for the exclusive use of the initiator until the reservation isH superseded by another valid RESERVE command from the initiator that madeD the reservation or until released by a RELEASE command from the sameG initiator that made the reservation, by a BUS DEVICE RESET message from-D any initiator, by a hard RESET condition, or by a power on cycle.  AH logical unit reservation shall not be granted if the logical unit or anyH extent is reserved by another initiator.  It shall be permissible for anF initiator to reserve a logical unit that is currently reserved by thatI initiator.  If the extent bit is zero, the reservation identification and ( the extent list length shall be ignored.  J If the logical unit, or any extent within the logical unit is reserved forH another initiator, the target shall return RESERVATION CONFLICT status.     D If, after honouring the reservation, any other initiator attempts toG perform any command on the reserved logical unit other than an INQUIRY,oI REQUEST SENSE, PREVENT ALLOW MEDIUM REMOVAL (with a prevent bit of zero), C or a RELEASE command the command shall be rejected with RESERVATION  CONFLICT status.   9.2.12.2 Extent reservationp  B Implementation of extent reservation is optional.  The reservationG identification field provides a means for an initiator to identify eachtC extent reservation.  This allows an initiator in a multiple taskingiH environment, to have multiple reservations outstanding.  The reservationJ identification is used in the RELEASE command to specify which reservationF is to be released.  It is also used in superseding RESERVE commands to. specify which reservation is to be superseded.  H If the extent reservation option is implemented, then the extent releaseF option (see 9.2.11.2) shall also be implemented.  These options permitD multiple extents within the logical unit to be reserved, each with a separate reservation type.  > If the extent bit is one, and the extent reservation option isE implemented, then the target shall process the reservation request aso follows:K    a)     The extent list shall be checked for the number of extents in thefM           reservation request.  If the extent list length is zero, no currentrN           reservations shall be changed, no new reservations shall be created,M           and this condition shall not be treated as an error.  If the extenttL           list contains more extents than are supported on the logical unit,M           the command shall be terminated with CHECK CONDITION status and thenH           sense key shall be set to ILLEGAL REQUEST.  If the extent listK           contains more extents than are currently available on the logicalsL           unit, then the target shall return a RESERVATION CONFLICT status. I    b)     The extent list shall be checked for valid extent logical block N           addresses.  If any logical block address is invalid for this logicalK           unit, the command shall be terminated with CHECK CONDITION statussM           and the sense key shall be set to ILLEGAL REQUEST.  The extent listwE           shall be checked for invalid extent overlaps (as defined byyL           reservation type) with other extent descriptors in the extent listL           and if invalid overlaps are found, the command shall be terminatedG           with CHECK CONDITION status and the sense key shall be set toe           ILLEGAL REQUEST.I    c)     If the requested reservation does not conflict with an existing D           reservation, the extents specified shall be reserved untilM           superseded by another valid RESERVE command from the initiator that|N           made the reservation or until released by a RELEASE command from theK           same initiator, by a BUS DEVICE RESET message from any initiator,=M           or by a hard RESET condition.  If either of the last two conditions N           occur, the next command from each initiator shall be terminated withG           CHECK CONDITION status and the sense key shall be set to UNIT-           ATTENTION.L    d)     If the reservation request conflicts with an existing reservation,E           then the target shall return a RESERVATION CONFLICT status.   B If the extent bit is one, and the extent reservation option is notB implemented, then the RESERVE command shall be rejected with CHECKC CONDITION status and the sense key shall be set to ILLEGAL REQUEST.   F The size of the extent list shall be defined by the extent list lengthJ field.  The extent list shall consist of zero or more descriptors as shownH in table 133.  Each extent descriptor defines an extent beginning at theG specified logical block address for the specified number of blocks.  If E the number of blocks is zero, the extent shall begin at the specified=I logical block address and continue through the last logical block address  on the logical unit.  =                 Table 133 - Data format of extent descriptors O +=====-========-========-========-========-========-========-========-========+aO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |rO |Byte |        |        |        |        |        |        |        |        |sO |=====+============================================+========+=================|oO | 0   |               Reserved                     | RelAdr | Reservation type|fO |-----+-----------------------------------------------------------------------|nO | 1   | (MSB)                                                                 |hO |- - -+---                        Number of blocks                         ---|tO | 3   |                                                                 (LSB) |oO |-----+-----------------------------------------------------------------------|2O | 4   | (MSB)                                                                 |bO |- - -+---                        Logical block address                    ---|mO | 7   |                                                                 (LSB) |eO +=============================================================================+t    I The reservation type field shall define the type of reservation in effecteC for the extent.  The types of reservation are defined in table 134.s  5                         Table 134 - Reservation typese, +====================-=====================+, | Reservation type   |  Description        |, |--------------------+---------------------|, |        00b         |  Read shared        |, |        01b         |  Write exclusive    |, |        10b         |  Read exclusive     |, |        11b         |  Exclusive access   |, +==========================================+  L a)     Read exclusive.  While this reservation is active, no other initiatorH        shall be permitted read operations to the indicated extent.  ThisK        reservation shall not inhibit write operations from any initiator or.L        conflict with a write exclusive reservation; however, read exclusive,G        exclusive access, and read shared reservations that overlap thisa3        extent shall conflict with this reservation.h  M b)     Write exclusive.  While this reservation is active, no other initiatorfI        shall be permitted write operations to the indicated extent.  ThisaJ        reservation shall not inhibit read operations from any initiator orK        conflict with a read exclusive reservation from any initiator.  ThismM        reservation shall conflict with write exclusive, exclusive access, andr9        read shared reservations that overlap this extent.p  D c)     Exclusive access.  While this reservation is active, no otherL        initiator shall be permitted any access to the indicated extent.  AllJ        reservation types that overlap this extent shall conflict with this        reservation.h  J d)     Read shared.  While this reservation is active, no write operationsI        shall be permitted by any initiator to the indicated extent.  This J        reservation shall not inhibit read operations from any initiator orF        conflict with a read shared reservation.  Read exclusive, writeJ        exclusive, and exclusive access reservations that overlap with this3        extent shall conflict with this reservation.l  D If the relative address bit is one, the logical block address in theG extent descriptor shall be treated as a two's complement displacement. RB This displacement shall be added to the logical block address lastG accessed on the logical unit to form the logical block address for this J extent.  This feature is only available when linking commands and requiresH that a previous command in the linked group has accessed a logical blockI on the logical unit; if not, the RESERVE command shall be terminated with I CHECK CONDITION status and the sense key shall be set to ILLEGAL REQUEST.-  C If an initiator attempts a command to a logical block that has beeniF reserved and that access is prohibited by the reservation, the commandA shall not be performed and the command shall be terminated with a-J RESERVATION CONFLICT status.  If a reservation conflict precludes any partF of the command, none of the command shall be performed.  COPY commandsG shall be terminated with CHECK CONDITION status and the sense key shall I be set to DATA PROTECT if any part of the copy operation is prohibited bytJ an active reservation.  If any extent in a logical unit is reserved in anyE way, by any initiator, a FORMAT UNIT command shall be rejected with a- RESERVATION CONFLICT status.  ! 9.2.12.3 Third-party reservation    H Implementation of third-party reservation is mandatory.  The third-partyD reservation for the RESERVE command allows an initiator to reserve aG logical unit or extents within a logical unit for another SCSI device. fH This is intended for use in multiple-initiator systems that use the COPY/ command.  Third-party reservation is required. b  G If the third-party (3rdPty) bit is zero, then a third-party reservationoI is not requested.  If the 3rdPty bit is one then the target shall reserve2J the specified logical unit or extents for the SCSI device specified in theG third-party device ID field.  The target shall preserve the reservationtJ until it is superseded by another valid RESERVE command from the initiatorH that made the reservation or until it is released by the same initiator,A by a BUS DEVICE reset message from any initiator, or a hard resetRJ condition.  The target shall ignore any attempt to release the reservation made by any other initiator.  @ If independent sets of parameters are implemented, a third partyG reservation shall cause the target to transfer the set of parameters in J effect for the initiator of the RESERVE command to the parameters used forG commands from the third party device.  Any subsequent command issued bytF the third-party device is executed according to the mode parameters in7 effect for the initiator that sent the RESERVE command.l  P    NOTE 118 This transfer of the mode parameters is applicable to target devicesM    which store mode information independently for different initiators.  This O    mechanism allows an initiator to set the mode parameters of a target for the L    use of a copy master (i.e. the third-party device).  The third-party copyI    master may subsequently issue a MODE SELECT command to modify the modeb    parameters.  ! 9.2.12.4 Superseding reservations.  F Implementation of superseding reservations is mandatory.  An initiatorA that holds a current reservation (unit or extent) may modify thatiF reservation by issuing another RESERVE command (unit or extent) to theE same logical unit.  The superseding RESERVE command shall release thetD previous reservation state (unit or extent) when the new reservationD request is granted.  If the superseding reservation is for an extentJ reservation and the current reservation is also an extent reservation, the? current extent reservation identification value is used for thehG superseding reservation.  The current reservation shall not be modified A if the superseding reservation request cannot be granted.  If therE superseding reservation cannot be granted because of conflicts with aeH previous reservation (other than the reservation being superseded), then6 the target shall return RESERVATION CONFLICT status.    N    NOTE 119 Superseding reservations allow the SCSI device ID to be changed onN    a reservation using the third-party reservation option.  This capability isJ    necessary for certain situations when using COMPARE, COPY, and COPY AND    VERIFY commands.s   9.2.13 REZERO UNIT command  H The REZERO UNIT command (see table 135) requests that the target set theI logical unit to a specific state.  See vendor specifications for details.C  6                        Table 135 - REZERO UNIT commandO +=====-========-========-========-========-========-========-========-========+eO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |nO |Byte |        |        |        |        |        |        |        |        |vO |=====+=======================================================================| O | 0   |                           Operation code (01h)                        |EO |-----+-----------------------------------------------------------------------|.O | 1   | Logical unit number      |                  Reserved                  |fO |-----+-----------------------------------------------------------------------| O | 2   |                           Reserved                                    |dO |-----+-----------------------------------------------------------------------| O | 3   |                           Reserved                                    |tO |-----+-----------------------------------------------------------------------|tO | 4   |                           Reserved                                    ||O |-----+-----------------------------------------------------------------------| O | 5   |                           Control                                     | O +=============================================================================+      9.2.14 SEARCH DATA commandse  J The SEARCH DATA commands (see table 136) search one or more logical blocksE for equality or inequality to a data pattern.  The concept of recordstI within a logical block is used to allow multiple records within a logicalh block to be searched.u  7                        Table 136 - SEARCH DATA commandsoO +=====-========-========-========-========-========-========-========-========+nO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |oO |Byte |        |        |        |        |        |        |        |        |lO |=====+=======================================================================|sO | 0   |                           Operation code (31h 30h 32h)                |pO |-----+-----------------------------------------------------------------------|rO | 1   | Logical unit number      | Invert |     Reserved    | SpnDat | RelAdr |sO |-----+-----------------------------------------------------------------------| O | 2   | (MSB)                                                                 |=O |-----+---                                                                 ---|6O | 3   |                                                                       | O |-----+---                        Logical block address                    ---|=O | 4   |                                                                       | O |-----+---                                                                 ---|-O | 5   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------| O | 6   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|-O | 7   | (MSB)                                                                 | O |-----+---                        Number of blocks to search               ---| O | 8   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|=O | 9   |                           Control                                     | O +=============================================================================+t    J The invert bit determines whether the search condition is to be inverted. H See 9.2.14.1 through 9.2.14.3 for a description of the search conditions( for the individual SEARCH DATA commands.  G A spanned data (SpnDat) bit of zero indicates that each record shall bedH wholly contained within a single block.  Any space at the end of a blockD that is smaller than the record length is ignored by the SEARCH DATAA commands.   A SpnDat bit of one indicates that records span blockRH boundaries (i.e.  record may start in one block and end in the next or a subsequent block.e  D The number of blocks to search field specifies the maximum number ofI contiguous logical blocks to be searched.  A value of zero indicates thath@ no logical blocks shall be searched. This condition shall not beE considered an error.  Any other value indicates the maximum number of & logical blocks that shall be searched.  H A link bit (see 7.2.7) of zero indicates a non-linked command and if theI search is satisfied, the command shall be terminated with a CONDITION METxD status.  A REQUEST SENSE command can then be issued to determine theG logical block address and record offset of the matching record.  If themA search is not satisfied and no error occurs, the command shall bee terminated with GOOD status.  I A link bit (see 7.2.7) of one indicates a command is linked to the SEARCHcG DATA command and if the search is satisfied, INTERMEDIATE-CONDITION METtG status is returned and the next command is executed.  If the RelAdr bitsI in the next command is one, the logical block address of the next commandsE is used as a displacement from the logical block address at which the G search was satisfied.  If a linked search is not satisfied, the commandaG is terminated with CHECK CONDITION status.  A REQUEST SENSE command mayf then be issued.   H A REQUEST SENSE command following a satisfied SEARCH DATA command shall:M    a)     return a sense key of EQUAL if the search was satisfied by an exact K           match.  If the search was satisfied by an inequality then a sensei,           key of NO SENSE shall be returned.*    b)     return the valid bit set to one.N    c)     return the logical block address of the logical block containing the9           first matching record in the information field.gI    d)     return the record offset of the matching record in the command-l%           specific information field.e  C A REQUEST SENSE command following a SEARCH DATA command that is notl satisfied shall:J    a)     return a sense key of NO SENSE, if no errors occurred during the           command execution.+    b)     return the valid bit set to zero.s  G The SEARCH DATA parameter list (see table 137) contains a fourteen-byter= header, followed by one or more search argument descriptors. d  :                     Table 137 - SEARCH DATA parameter listO +=====-========-========-========-========-========-========-========-========+oO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |CO |Byte |        |        |        |        |        |        |        |        |hO |=====+=======================================================================|gO | 0   | (MSB)                                                                 |bO |- - -+---                        Logical record length                    ---|iO | 3   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|tO | 4   | (MSB)                                                                 |rO |- - -+---                        First record offset                      ---|vO | 7   |                                                                 (LSB) |tO |-----+-----------------------------------------------------------------------| O | 8   | (MSB)                                                                 |tO |- - -+---                        Number of records                        ---|iO | 11  |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|eO | 12  | (MSB)                                                                 |nO |-----+---                        Search argument length                   ---|dO | 13  |                                                                 (LSB) |sO |=====+=======================================================================|hO |     |                        Search argument descriptor(s)                  |eO |=====+=======================================================================|gO | 0   | (MSB)                                                                 |dO |- - -+---                        Displacement                             ---|vO | 3   |                                                                 (LSB) |iO |-----+-----------------------------------------------------------------------|hO | 4   | (MSB)                                                                 | O |-----+---                        Pattern length                           ---|rO | 5   |                                                                 (LSB) |eO |-----+-----------------------------------------------------------------------| O | 6   |                                                                       | O |-----+---                        Pattern                                  ---| O | n   |                                                                       |sO +=============================================================================+h    E The logical record length field specifies the record length in bytes.s  I The first record offset field specifies the number of bytes that shall be J ignored in the first logical block before the search begins.  If the valueG of the first record offset field shall is larger than the logical blocknD length the target shall terminate the command with a CHECK CONDITIONI status, set the sense key to ILLEGAL REQUEST and set the additional senseOJ code to INVALID FIELD IN PARAMETERS LIST.  Subsequent logical blocks shallE be searched beginning with the first byte in the logical block.  Thisi4 permits one or more records to be skipped initially.  H The number of records field specifies the maximum number of records thatF shall be searched by this command.  An search shall terminate when theJ search pattern is found or when the number of records is exhausted or when, the number of blocks to search is exhausted.  I The search argument length field specifies the length in bytes of all the=* search argument descriptors that follow.    P    NOTE 120 Since the pattern length can vary, there is no fixed multiple of theF    search argument descriptor to determine the search argument length.  H The search argument descriptors specify one or more search conditions toD execute within a single record in order to satisfy the search.  EachH search argument descriptor is made up of a displacement field, a pattern" length field, and a pattern field.  G The displacement field specifies the displacement in bytes of the first E byte of the data to be compared from the start of the logical record.-  J The pattern length field specifies the length in bytes of the pattern that follows.  F The pattern field specifies the data to compare to the logical record.  " 9.2.14.1 SEARCH DATA EQUAL command  G The SEARCH DATA EQUAL command (see table 136, operation code 31h) shall-I be satisfied by the first logical record searched that contains data that I satisfies all of the search argument descriptor(s).  If the invert bit in|G the command descriptor block is zero, the search argument descriptor(s)-H shall be satisfied by data in the logical record being equal to the data> in the pattern.  If the invert bit is one, the search argumentH descriptor(s) shall be satisfied by data in the logical record being not0 equal to the data in the pattern.  (See 9.2.14.)  ! 9.2.14.2 SEARCH DATA HIGH commando  I The SEARCH DATA HIGH command (see table 136, operation code 30h) shall beoF satisfied by the first logical record searched that contains data thatI satisfies all of the search argument descriptor(s).  If the invert bit in=G the command descriptor block is zero, the search argument descriptor(s) G shall be satisfied by data in the logical record being greater than the0C data in the pattern.  If the invert bit is one, the search argument I descriptor(s) shall be satisfied by data in the logical record being less=8 than or equal to the data in the pattern.  (See 9.2.14.)    9.2.14.3 SEARCH DATA LOW command  H The SEARCH DATA LOW command (see table 136, operation code 32h) shall beF satisfied by the first logical record searched that contains data thatI satisfies all of the search argument descriptor(s).  If the invert bit in-G the command descriptor block is zero, the search argument descriptor(s) I shall be satisfied by data in the logical record being less than the data > in the pattern.  If the invert bit is one, the search argumentD descriptor(s) shall be satisfied by data in the logical record being@ greater than or equal to the data in the pattern.  (See 9.2.14.)  $ 9.2.15 SEEK(6) and SEEK(10) commands  I The SEEK(6) (see table 138) and SEEK(10) (see table 139) commands request B that the logical unit seek to the specified logical block address.  4                          Table 138 - SEEK(6) commandO +=====-========-========-========-========-========-========-========-========+-O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |-O |=====+=======================================================================| O | 0   |                           Operation code (0Bh)                        | O |-----+-----------------------------------------------------------------------| O | 1   | Logical unit number      | (MSB)                                      |-O |-----+-------------------------------                                     ---| O | 2   |                           Logical block address                       |=O |-----+---                                                                 ---|oO | 3   |                                                                 (LSB) |dO |-----+-----------------------------------------------------------------------|fO | 4   |                           Reserved                                    |kO |-----+-----------------------------------------------------------------------|oO | 5   |                           Control                                     |aO +=============================================================================+a    5                          Table 139 - SEEK(10) commanddO +=====-========-========-========-========-========-========-========-========+lO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |hO |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================|tO | 0   |                           Operation code (2Bh)                        |mO |-----+-----------------------------------------------------------------------| O | 1   | Logical unit number      |                  Reserved                  | O |-----+-----------------------------------------------------------------------|mO | 2   | (MSB)                                                                 |lO |-----+---                                                                 ---|OO | 3   |                                                                       | O |-----+---                        Logical block address                    ---| O | 4   |                                                                       |sO |-----+---                                                                 ---|hO | 5   |                                                                 (LSB) |UO |-----+-----------------------------------------------------------------------|uO | 6   |                           Reserved                                    |.O |-----+-----------------------------------------------------------------------| O | 7   |                           Reserved                                    |eO |-----+-----------------------------------------------------------------------|sO | 8   |                           Reserved                                    |oO |-----+-----------------------------------------------------------------------| O | 9   |                           Control                                     |hO +=============================================================================+      9.2.16 SET LIMITS command   E The SET LIMITS command (see table 140) defines the range within whichiH subsequent linked commands may operate.  A second SET LIMITS command mayF not be linked to a chain of commands in which a SET LIMITS command has already been issued.  6                         Table 140 - SET LIMITS commandO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |=O |=====+=======================================================================| O | 0   |                           Operation code (33h)                        |tO |-----+-----------------------------------------------------------------------| O | 1   | Logical unit number      |         Reserved         | RdInh  | WrInh  |-O |-----+-----------------------------------------------------------------------| O | 2   | (MSB)                                                                 | O |-----+---                                                                 ---| O | 3   |                                                                       |-O |-----+---                        Logical block address                    ---| O | 4   |                                                                       | O |-----+---                                                                 ---| O | 5   |                                                                 (LSB) |-O |-----+-----------------------------------------------------------------------| O | 6   |                           Reserved                                    |gO |-----+-----------------------------------------------------------------------| O | 7   | (MSB)                                                                 |=O |-----+---                        Number of blocks                         ---|pO | 8   |                                                                 (LSB) |=O |-----+-----------------------------------------------------------------------| O | 9   |                           Control                                     | O +=============================================================================+     I The read inhibit (RdInh) bit of one indicates that read operations within- the range shall be inhibited.     I A write inhibit (WrInh) bit of one indicates that write operations within  the range shall be inhibited.   F The logical block address field specifies the starting address for the range.  H The number of blocks field specifies the number of logical blocks withinE the range.  A number of blocks of zero indicates that the range shall 5 extend to the last logical block on the logical unit.   G Any attempt to access outside of the restricted range or any attempt to G perform an inhibited operation within the restricted range shall not be G performed.  The command shall be terminated with CHECK CONDITION status=D and the sense key shall be set to DATA PROTECT.  A second SET LIMITSE command within a linked list of commands shall be rejected with CHECKp@ CONDITION status and the sense key shall be set to DATA PROTECT.   9.2.17 START STOP UNIT command  D The START STOP UNIT command (see table 141) requests that the target? enable or disable the logical unit for media access operations.n  8                      Table 141 - START STOP UNIT commandO +=====-========-========-========-========-========-========-========-========+TO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |tO |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================|eO | 0   |                           Operation code (1Bh)                        | O |-----+-----------------------------------------------------------------------| O | 1   | Logical unit number      |                  Reserved         | Immed  |bO |-----+-----------------------------------------------------------------------| O | 2   |                           Reserved                                    |tO |-----+-----------------------------------------------------------------------|iO | 3   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|sO | 4   |                           Reserved                  |  LoEj  |  Start |tO |-----+-----------------------------------------------------------------------|cO | 5   |                           Control                                     |iO +=============================================================================+e    G An immediate (Immed) bit of one indicates that status shall be returnedmI as soon as the command descriptor block has been validated.  An Immed bithF of zero indicates that status shall be returned after the operation is completed. i  J A load eject (LoEj) bit of zero requests that no action be taken regardingD loading or ejecting the medium.  A LoEj bit of one requests that theE medium shall be unloaded if the start bit is zero.  A LoEj bit of one A requests that the medium is to be loaded if the start bit is one.c  F A start bit of one requests the logical unit be made ready for use.  AI start bit of zero requests that the logical unit be stopped (media cannoto be accessed by the initiator).  H Targets that contain cache memory shall implicitly perform a SYNCHRONIZED CACHE command for the entire medium prior to executing the STOP UNIT command.    9.2.18 SYNCHRONIZE CACHE command  I The SYNCHRONIZE CACHE command (see table 142) ensures that logical blocksrG in the cache memory, within the specified range, have their most recent H data value recorded on the physical medium.  If a more recent data valueI for a logical block within the specified range exists in the cache memory=I than on the physical medium, then the logical block from the cache memoryC@ shall be written to the physical medium.  Logical blocks are notH necessarily removed from the cache memory as a result of the synchronize cache operation.  9                     Table 142 - SYNCHRONIZE CACHE command O +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |tO |Byte |        |        |        |        |        |        |        |        |tO |=====+=======================================================================|aO | 0   |                           Operation code (35h)                        |nO |-----+-----------------------------------------------------------------------| O | 1   | Logical unit number       |         Reserved        | Immed  | RelAdr | O |-----+-----------------------------------------------------------------------|=O | 2   | (MSB)                                                                 | O |-----+---                                                                 ---| O | 3   |                                                                       |=O |-----+---                        Logical block address                    ---|tO | 4   |                                                                       |-O |-----+---                                                                 ---|)O | 5   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|aO | 6   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------| O | 7   | (MSB)                                                                 |-O |-----+---                        Number of blocks                         ---|vO | 8   |                                                                 (LSB) |-O |-----+-----------------------------------------------------------------------|oO | 9   |                           Control                                     |=O +=============================================================================+-    F An immediate (Immed) bit of one indicates that the target shall returnF status as soon as the command descriptor block has been validated.  AnG Immed bit of zero indicates that the status shall not be returned until H the operation has been completed. If the Immed bit is one and the targetI does not support it then the command shall terminate with CHECK CONDITION I status.  The sense key shall be set to ILLEGAL REQUEST and the additional-0 sense code shall be set to INVALID FIELD IN CDB.  J See 9.2.2 for a definition of the RelAdr bit and the logical block address field.  C The number of blocks field specifies the total number of contiguous-F logical blocks within the range.  A number of blocks of zero indicatesI that all remaining logical blocks on the logical unit shall be within the  range.    I A logical block within the specified range that is not in cache memory is  not considered an error.   9.2.19 VERIFY command   F The VERIFY command (see table 143) requests that the target verify the data written on the medium.   4                           Table 143 - VERIFY commandO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |-O |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================|-O | 0   |                           Operation code (2Fh)                        | O |-----+-----------------------------------------------------------------------|-O | 1   |   Logical unit number    |   DPO  |Reserved|Reserved| BytChk | RelAdr | O |-----+-----------------------------------------------------------------------|-O | 2   | (MSB)                                                                 | O |-----+---                                                                 ---|=O | 3   |                                                                       |MO |-----+---                        Logical block address                    ---|hO | 4   |                                                                       |oO |-----+---                                                                 ---|nO | 5   |                                                                 (LSB) |=O |-----+-----------------------------------------------------------------------| O | 6   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|=O | 7   | (MSB)                                                                 | O |-----+---                        Verification length                         |-O | 8   |                                                                 (LSB) |aO |-----+-----------------------------------------------------------------------|-O | 9   |                           Control                                     | O +=============================================================================+     H If the MODE SELECT command is implemented, and the verify error recoveryF parameters page is also implemented, then the current settings in thatC page specifies the verification error criteria. If the verify error B recovery parameters page is not implemented, then the verification criteria is vendor-specific. -  D A byte check (BytChk) bit of zero causes a medium verification to beI performed with no data comparison.  A BytChk bit of one causes a byte-by- H byte compare of data written on the medium and the data transferred fromI the initiator.  If the compare is unsuccessful for any reason, the target I shall return CHECK CONDITION status with the sense key set to MISCOMPARE.-  J See 9.2.2 for a definition of the RelAdr bit and the logical block address field.  H The verification length field specifies the number of contiguous logicalA blocks of data that shall be verified.  A transfer length of zero I indicates that no logical blocks shall be verified.  This condition shall-G not be considered as an error.  Any other value indicates the number of & logical blocks that shall be verified.  ; See 9.2.6 for a description of the cache control bit (DPO).=   9.2.20 WRITE(6) command=  G The WRITE(6) command (see table 144) requests that the target write thet2 data transferred by the initiator to the medium.    5                          Table 144 - WRITE(6) commandrO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |iO |Byte |        |        |        |        |        |        |        |        |iO |=====+=======================================================================|nO | 0   |                           Operation code (0Ah)                        | O |-----+-----------------------------------------------------------------------|eO | 1   | Logical unit number      | (MSB)                                      |eO |-----+------------------------------                                      ---|tO | 2   |                           Logical block address                       |aO |-----+---                                                                 ---|IO | 3   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------| O | 4   |                           Transfer length                             |=O |-----+-----------------------------------------------------------------------| O | 5   |                           Control                                     | O +=============================================================================+=    F The cache control bits (see 9.2.6) are not provided for this command. J Targets with cache memory may have values for the cache control bits whichG may affect the WRITE(6) command, however no default value is defined by B this International Standard.  If explicit control is required, the! WRITE(10) command should be used.-  H The logical block address field specifies the logical block at which the write operation shall begin.  D The transfer length field specifies the number of contiguous logicalH blocks of data to transferred.  A transfer length of zero indicates thatG 256 logical blocks shall be transferred.  Any other value indicates the-3 number of logical blocks that shall be transferred.v   9.2.21 WRITE(10) command  H The WRITE(10) command (see table 145) requests that the target write the0 data transferred by the initiator to the medium.  5                         Table 145 - WRITE(10) command=O +=====-========-========-========-========-========-========-========-========+nO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |sO |Byte |        |        |        |        |        |        |        |        |eO |=====+=======================================================================|eO | 0   |                           Operation code (2Ah)                        |tO |-----+-----------------------------------------------------------------------| O | 1   | Logical unit number      |   DPO  |   FUA  |Reserved|Reserved| RelAdr |dO |-----+-----------------------------------------------------------------------|aO | 2   | (MSB)                                                                 | O |-----+---                                                                 ---|rO | 3   |                                                                       |oO |-----+---                        Logical block address                    ---| O | 4   |                                                                       |cO |-----+---                                                                 ---|eO | 5   |                                                                 (LSB) |nO |-----+-----------------------------------------------------------------------|eO | 6   |                           Reserved                                    |uO |-----+-----------------------------------------------------------------------| O | 7   | (MSB)                                                                 |ZO |-----+---                        Transfer length                             |=O | 8   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------| O | 9   |                           Control                                     |=O +=============================================================================+     G See READ(10) command (9.2.6) for a definition of the cache control bits- (DPO and FUA).  J See 9.2.2 for a definition of the RelAdr bit and the logical block address field.  D The transfer length field specifies the number of contiguous logicalD blocks of data that shall be transferred.  A transfer length of zeroF indicates that no logical blocks shall be transferred.  This conditionI shall not be considered an error and no data shall be written.  Any other G value indicates the number of logical blocks that shall be transferred.    9.2.22 WRITE AND VERIFY command   E The WRITE AND VERIFY command (see table 146) requests that the target D write the data transferred from the initiator to the medium and thenG verify that the data is correctly written. The data is only transferred & once from the initiator to the target.  9                      Table 146 - WRITE AND VERIFY command-O +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |-O |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================| O | 0   |                           Operation code (2Eh)                        | O |-----+-----------------------------------------------------------------------|-O | 1   |   Logical unit number    |   DPO  |Reserved|Reserved| BytChk | RelAdr | O |-----+-----------------------------------------------------------------------|=O | 2   | (MSB)                                                                 | O |-----+---                                                                 ---| O | 3   |                                                                       | O |-----+---                        Logical block address                    ---|pO | 4   |                                                                       |eO |-----+---                                                                 ---| O | 5   |                                                                 (LSB) |lO |-----+-----------------------------------------------------------------------|mO | 6   |                           Reserved                                    |iO |-----+-----------------------------------------------------------------------|hO | 7   | (MSB)                                                                 |eO |-----+---                        Transfer length                             |dO | 8   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|=O | 9   |                           Control                                     | O +=============================================================================+     H If the MODE SELECT command is implemented, and the verify error recoveryI page is also implemented (see 9.3.3.8), then the current settings in that D page along with the AWRE bit from the read-write error recovery page? specify the verification error criteria. If these pages are not-? implemented, then the verification criteria is vendor-specific.|  F A byte check (BytChk) bit of zero requests a medium verification to beH performed with no data comparison.  A BytChk bit of one requests a byte-F by-byte compare of data written on the medium and the data transferredG from the initiator.  If the compare is unsuccessful for any reason, the D target shall return CHECK CONDITION status with the sense key set to MISCOMPARE.   J See 9.2.2 for a definition of the RelAdr bit and the logical block address field.  J See WRITE(10) command (see 9.2.21) for a definition of the transfer length field.  ; See 9.2.6 for a description of the cache control bit (DPO).   N    NOTE 121 The WRITE AND VERIFY command specifically states that the data areN    not to be transferred twice (i.e. once for the write pass, and once for theK    verify pass) when performing a byte compare.  If there is a need for two-N    transfers to occur (e.g. to ensure the integrity of the path to the media),I    then the initiator should issue a WRITE command with a LINK bit of one O    followed by a VERIFY command with a BytCmp bit of one, transferring the same     data on each command.   9.2.23 WRITE LONG command   I The WRITE LONG command (see table 147) requests that the target write the-H data transferred by the initiator to the medium.  The data passed duringH the WRITE LONG command is implementation specific, but shall include the data bytes and the ECC bytes.  =  6                         Table 147 - WRITE LONG commandO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |vO |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================|uO | 0   |                           Operation code (3Fh)                        |sO |-----+-----------------------------------------------------------------------|eO | 1   | Logical unit number      |              Reserved             | RelAdr | O |-----+-----------------------------------------------------------------------|eO | 2   | (MSB)                                                                 | O |-----+---                                                                 ---|sO | 3   |                                                                       |oO |-----+---                        Logical block address                    ---|rO | 4   |                                                                       |fO |-----+---                                                                 ---|IO | 5   |                                                                 (LSB) |rO |-----+-----------------------------------------------------------------------| O | 6   |                           Reserved                                    |=O |-----+-----------------------------------------------------------------------| O | 7   | (MSB)                                                                 | O |-----+---                        Byte transfer length                        |=O | 8   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|-O | 9   |                           Control                                     | O +=============================================================================+     K    NOTE 122 Any other bytes that can be corrected by ECC should be includedlN    (e.g. a data synchronization mark within the area covered by ECC). The READP    LONG command is usually issued before issuing a WRITE LONG command. The WRITEH    LONG data should be the same length and in the same order as the data%    returned by the READ LONG command.-  J See 9.2.2 for a definition of the RelAdr bit and the logical block address field.  I The byte transfer length field should specify the number of bytes of data-F that the target would return for the READ LONG command.  If a non-zeroF byte transfer length does not exactly match the data length the targetG would return for the READ LONG command, then the target shall terminatetJ the command with CHECK CONDITION status and a sense key of ILLEGAL REQUESTG and an additional sense code of INVALID FIELD IN CDB. The ILI and valid F bits shall be set to one and the information field shall be set to theG difference (residue) of the requested length minus the actual length inaH bytes. Negative values shall be indicated by two's complement notation. J A transfer length of zero indicates that no bytes shall be transferred and! shall not be considered an error.r   9.2.24 WRITE SAME command   I The WRITE SAME command (see table 148) requests that the target write theaH single block of data transferred by the initiator to the medium multiple times.  6                         Table 148 - WRITE SAME commandO +=====-========-========-========-========-========-========-========-========+dO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |=O |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================| O | 0   |                           Operation code (41h)                        |=O |-----+-----------------------------------------------------------------------| O | 1   | Logical unit number      |     Reserved    | PBdata | LBdata | RelAdr |-O |-----+-----------------------------------------------------------------------|nO | 2   | (MSB)                                                                 |-O |-----+---                                                                 ---| O | 3   |                                                                       | O |-----+---                        Logical block address                    ---| O | 4   |                                                                       | O |-----+---                                                                 ---| O | 5   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------| O | 6   |                           Reserved                                    |-O |-----+-----------------------------------------------------------------------| O | 7   | (MSB)                                                                 |-O |-----+---                        Number of blocks                            | O | 8   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------| O | 9   |                           Control                                     |-O +=============================================================================+     J    NOTE 123 This command is useful if large areas of the medium need to beL    written, prepared for certification, or otherwise initialized without the-    initiator having to transfer all the data.c  I A logical block data (LBdata) bit of one requests that the target replacebE the first four bytes of the data to be written to the current logicalpJ block with the logical block address of the block currently being written.  J A physical block data (PBdata) bit of one requests that the target replaceG the first eight bytes of the data to be written to the current physicalaF sector with the physical address of the sector currently being written/ using the physical sector format (see 9.2.1.1).A  G If PBdata and LBdata are one the command shall be terminated with CHECK A CONDITION status.  The sense key shall be set to ILLEGAL REQUEST.t  J See 9.2.2 for a definition of the RelAdr bit and the logical block address field.  E The number of blocks field specifies the number of contiguous logicalbI blocks to be written.  A number of blocks field of zero requests that all=6 the remaining logical blocks on the medium be written.    ( 9.3 Parameters for direct-access devices     9.3.1 Diagnostic parameters   J This subclause defines the descriptors and pages for diagnostic parameters! used with direct-access devices. =  H The diagnostic page codes for direct-access devices are defined in table 149.  7                       Table 149 - Diagnostic page codes-O +=============-==================================================-============+tO |  Page code  |  Description                                     | Subclause  |-O |-------------+--------------------------------------------------+------------| O |     00h     |  Supported diagnostic pages                      |  8.3.1.1   | O |     40h     |  Translate address page                          |  9.3.1.1   | O |  01h - 3Fh  |  Reserved (for all device type pages)            |            | O |  41h - 7Fh  |  Reserved                                        |            | O |  80h - FFh  |  Vendor-specific pages                           |            | O +=============================================================================+     1 9.3.1.1 Translate address page - SEND DIAGNOSTIC    F The translate address page allows the initiator to translate a logicalC block address, physical sector address or physical bytes from index H address into any one of the other formats.  The address to be translatedH is passed to the target with the SEND DIAGNOSTIC command and the resultsI are returned to the initiator by the RECEIVE DIAGNOSTIC RESULTS command. rF The format of the translate address page - SEND DIAGNOSTIC is shown inG table 150.  The translated address is returned in the translate address-0 page - RECEIVE DIAGNOSTIC RESULTS (see 9.3.1.2).  A              Table 150 - Translate address page - SEND DIAGNOSTIC O +=====-========-========-========-========-========-========-========-========+=O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |vO |Byte |        |        |        |        |        |        |        |        |tO |=====+=======================================================================|aO | 0   |                           Page code (40h)                             |,O |-----+-----------------------------------------------------------------------| O | 1   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|uO | 2   | (MSB)                                                                 |oO |-----+---                        Page length (000Ah)                      ---| O | 3   |                                                                 (LSB) |cO |-----+-----------------------------------------------------------------------|fO | 4   |                   Reserved                 |     Supplied format      |bO |-----+--------------------------------------------+--------------------------|hO | 5   |                   Reserved                 |     Translate format     |eO |-----+-----------------------------------------------------------------------| O | 6   |                                                                       |aO |- - -+---                        Address to translate                     ---| O | 13  |                                                                       | O +=============================================================================+e    F The supplied format field specifies the format of address to translateJ field.  Valid values for this field are defined in the FORMAT UNIT commandJ (see 9.2.1).  If the target does not support the requested format it shallG terminate the SEND DIAGNOSTIC command with CHECK CONDITION status.  The=F sense key shall be set to ILLEGAL REQUEST and an additional sense code0 shall be set to INVALID FIELD IN PARAMETER LIST.  J The translate format field specifies which format the initiator would likeI the address to be translated to.  Valid values for this field are defined=G in the FORMAT UNIT command (see 9.2.1).  If the target does not support H the requested format it shall terminate the command with CHECK CONDITIONH status.  The sense key shall be set to ILLEGAL REQUEST and an additional; sense code shall be set to INVALID FIELD IN PARAMETER LIST.   I The address to translate field contains a single address the initiator is-H requesting the target to translate.  The format of this field depends onE the value in the supplied format field.  The formats are described in J 9.2.1.1.  If the logical block format is specified the block address shallG be in the first four bytes of the field with the remaining bytes set tol zero.r  4 9.3.1.2 Translate address page - RECEIVE DIAGNOSTIC   F The translate address page allows the initiator to translate a logicalD block address, physical sector address, or physical bytes from indexH address into any one of the other formats.  The address to be translatedH is passed to the target with the SEND DIAGNOSTIC command and the resultsI are returned to the initiator by the RECEIVE DIAGNOSTIC RESULTS command.  J The translated address is returned in the translate address page - RECEIVE DIAGNOSTIC (see table 151).   B            Table 151 - Translate address page - RECEIVE DIAGNOSTICP +======-========-========-========-========-========-========-========-========+P |   Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P |Byte  |        |        |        |        |        |        |        |        |P |======+=======================================================================|P | 0    |                           Page code (40h)                             |P |------+-----------------------------------------------------------------------|P | 1    |                           Reserved                                    |P |------+-----------------------------------------------------------------------|P | 2    | (MSB)                                                                 |P |------+---                        Page length                              ---|P | 3    |                                                                 (LSB) |P |------+-----------------------------------------------------------------------|P | 4    |                   Reserved                 |     Supplied format      |P |------+--------------------------------------------+--------------------------|P | 5    | RAREA  | ALTSEC | ALTTRK |     Reserved    |     Translated format    |P |======+=======================================================================|P |      |                          Translated addresses                         |P |======+=======================================================================|P | 6    |                                                                       |P |- - --+---                        Translated address 1                     ---|P | 13   |                                                                       |P |------+-----------------------------------------------------------------------|P |      |                                 .                                     |P |      |                                 .                                     |P |------+-----------------------------------------------------------------------|P | n    |                                                                       |P |- - --+---                        Translated address x (if required)       ---|P | n+7  |                                                                       |P +==============================================================================+    A The translate address page contains a four byte page header whichlG specifies the page code and length followed by two bytes which describe-F the translated address followed by zero or more translated address(s).  J The page length field contains the number of parameter bytes which follow.  E The supplied format field contains the value from the SEND DIAGNOSTIC , command supplied format field (see 9.3.1.1).  D A reserved area (RAREA) bit of one indicates that all or part of theI translated address falls within a reserved area of the medium (e.g. speed E tolerance gap, alternate sector, vendor reserved area, etc.).  If the I entire translated address falls within a reserved area the target may not I return a translated address.  An RAREA bit of zero indicates that no part-E of the translated address falls within a reserved area of the medium.d  E An alternate sector (ALTSEC) bit of one indicates that the translated-G address is physically located in an alternate sector of the medium.  If G the target cannot determine if all or part of the translated address is H located in an alternate sector it shall set this bit to zero.  An ALTSECG bit of zero indicates that no part of the translated address is located-D in an alternate sector of the medium or that the target is unable to determine this information.   H An alternate track (ALTTRK) bit of one indicates that part or all of theH translated address is located on an alternate track of the medium or theC target cannot determine if all or part of the translated address is G located on an alternate track.  An ALTTRK bit of zero indicates that nooF part of the translated address is located on an alternate track of the medium.B  G The translated format field contains the value from the SEND DIAGNOSTIC - command translate format field (see 9.3.1.1).   J The translated address field contains the address(s) the target translatedJ from the address supplied by the initiator in the SEND DIAGNOSTIC command.J This field shall be in the format specified in the translate format field.E The different formats are described in 9.2.1.1.  If the logical blocksI format is specified the block address shall be in the first four bytes ofo7 the field and the remaining bytes shall be set to zero.   J If the returned data is in the logical block or physical sector format andF the address to be translated covers more than one address after it hasI been translated (e.g. accounting for speed tolerance or multiple physicaltG sectors within a single logical block or multiple logical blocks withineH a single physical sector) the target shall return all possible addressesJ which are contained in the area specified by the address to be translated.  J If the returned data is in bytes from index format the target shall returnH a pair of translated values for each of the possible addresses which areJ contained in the area specified by the address to translate field.  Of theD pair of translated values returned, the first indicates the starting8 location and the second the ending location of the area.   9.3.2 Log parameters  H This subclause defines the descriptors and pages for log parameters used with direct-access devices.   F The log page codes for direct-access devices are defined in table 152.  4                           Table 152 - Log page codesO +=============-==================================================-============+sO |  Page code  |  Description                                     | Subclause  | O |-------------+--------------------------------------------------+------------| O |     01h     |  Buffer over-run/under-run page                  |  8.3.2.1   |=O |     03h     |  Error counter page (read) page                  |  8.3.2.2   |CO |     05h     |  Error counter page (verify) page                |  8.3.2.2   |cO |     02h     |  Error counter page (write) page                 |  8.3.2.2   |yO |     07h     |  Last n error events page                        |  8.3.2.3   | O |     06h     |  Non-medium error page                           |  8.3.2.    |yO |     00h     |  Supported log pages                             |  8.3.2.5   |aO |     04h     |  Reserved                                        |            |iO |  08h - 2Fh  |  Reserved                                        |            | O |     3Fh     |  Reserved                                        |            |=O |  30h - 3Eh  |  Vendor-specific pages                           |            | O +=============================================================================+      9.3.3 Mode parameters   I This subclause defines the descriptors and pages for mode parameters used= with direct-access devices.   E The mode parameter list, including the mode parameter header and mode ( block descriptor are described in 8.3.3.  I The medium-type code field is contained in the mode parameter header (see @ 8.3.3).  Table 153 defines this field for direct-access devices.  <                  Table 153 - Direct-access medium-type codesO +=======-=====================================================================+ O |  Code |                                                                     | O | value |                        Medium type                                  | O |-------+---------------------------------------------------------------------|-O |  00h  |  Default medium type (currently mounted medium type)                |oO |  01h  |  Flexible disk, single-sided; unspecified medium                    |-O |  02h  |  Flexible disk, double-sided; unspecified medium                    |fO |       |                                                                     |-O |       |                     Flexible disks                                  | O |       |  Diameter    Bit density  Track density  Number     ANSI reference  | O |       |  mm (in)     Bits/radian   /mm (/in)     of sides      standard     | O |       | ----------  -----------  -------------  --------  ----------------  |=O |  05h  | 200 (8,0)      6 631        1,9 (48)        1      ANSI X3.73-1980  |aO |  06h  | 200 (8,0)      6 631        1,9 (48)        2          (Note 1)     |dO |  09h  | 200 (8,0)     13 262        1,9 (48)        1            None       |mO |  0Ah  | 200 (8,0)     13 262        1,9 (48)        2      ANSI X3.121-1984 |hO |  0Dh  | 130 (5,25)     3 979        1,9 (48)        1      ANSI X3.82-1980  |IO |  12h  | 130 (5,25)     7 958        1,9 (48)        2      ANSI X3.125-1985 |hO |  16h  | 130 (5,25)     7 958        3,8 (96)        2      ANSI X3.126-1986 |iO |  1Ah  | 130 (5,25)    13 262        3,8 (96)        2      ISO DIS8630-1985 | O |  1Eh  |  90 (3,5)      7 958        5,3 (135)       2        ANSI X3.137    |NO |       |                                                        (Note 2)     | O |       |             Direct-access magnetic yapes                            |eO |       |  Width               Density      ANSI reference                    |sO |       |  mm (in)     Tracks  ftpmm (ftpi)    standard                       |dO |       | ----------  ------  ------------  --------------                    |iO |  40h  | 6,3 (0,25)    12    394 (10 000)      Note 1                        |iO |  44h  | 6,3 (0,25)    24    394 (10 000)      Note 1                        | O |-----------------------------------------------------------------------------| O |  Code values 80h - FFh are vendor-specific.  All remaining code values      |oO |  are reserved.                                                              |iO |-----------------------------------------------------------------------------|tO |  NOTES                                                                      |hO |   1  See annex c for additional standards information.                      |bO |   2  This standard is under development.  Please contact the secretariat    |=O |      for current information on status and availability.                    | O +=============================================================================+     G The device specific parameter field (see table 154) is contained in the=" mode parameter header (see 8.3.3).  9                     Table 154 - Device specific parameter O +=====-========-========-========-========-========-========-========-========+-O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |rO |=====+========+=================+========+===================================|-O |     |   WP   |     Reserved    | DPOFUA |             Reserved              | O +=============================================================================+     H When used with the MODE SELECT command the write protect (WP) bit is not defined.  I When used with the MODE SENSE command a WP bit of zero indicates that the-F medium is write enabled.  A WP bit of one indicates that the medium is write protected.  J When used with the MODE SELECT command, the DPOFUA bit is not used and the field is reserved.  I When used with the MODE SENSE command, a DPOFUA bit of one indicates thatnI the target supports the DPO and FUA bits (see 9.2.6).  When used with the=G MODE SENSE command, a DPOFUA bit of zero indicates that the target doesd! not support the DPO and FUA bits.=  J The density code field is contained in the mode parameter block descriptor? (see 7.3.3).  This field is reserved for direct-access devices.   E The mode page codes for direct-access devices are shown in table 155.   4                          Table 155 - Mode page codesO +=============-==================================================-============+-O |  Page code  |  Description                                     | Subclause  | O |-------------+--------------------------------------------------+------------| O |     08h     |  Caching page                                    |  9.3.3.1   |-O |     0Ah     |  Control mode page                               |  8.3.3.1   | O |     02h     |  Disconnect-reconnect page                       |  8.3.3.2   | O |     05h     |  Flexible disk page                              |  9.3.3.2   | O |     03h     |  Format device page                              |  9.3.3.3   |=O |     0Bh     |  Medium types supported page                     |  9.3.3.4   |eO |     0Ch     |  Notch and partition page                        |  9.3.3.5   |oO |     09h     |  Peripheral device page                          |  8.3.3.3   | O |     01h     |  Read-write error recovery page                  |  9.3.3.6   |bO |     04h     |  Rigid disk geometry page                        |  9.3.3.7   |DO |     07h     |  Verify error recovery page                      |  9.3.3.8   |AO |     06h     |  Reserved                                        |            | O |  0Dh - 1Fh  |  Reserved                                        |            | O |     00h     |  Vendor-specific (does not require page format)  |            | O |  20h - 3Eh  |  Vendor-specific (page format required)          |            |cO |     3Fh     |  Return all pages                                |            | O |             |     (valid only for the MODE SENSE command)      |            |-O +=============================================================================+a    H For direct-access devices, if the notch page is not supported, or if theF active notch field in the notch page is zero then each page descriptorI specifies mode parameters for the target to use for subsequent operationseG on the specified logical unit.  If the notch page is supported, and thesH active notch is not zero, then each page descriptor specifies parametersA for the target to use for subsequent operations on the disk notchcI specified by the current value of the active notch field on the specifiedl
 logical unit.    9.3.3.1 Caching page    G The caching parameters page (see table 156) defines the parameters thatd affect the use of the cache.  3                            Table 156 - Caching page O +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |nO |Byte |        |        |        |        |        |        |        |        |.O |=====+========+========+=====================================================| O | 0   |   PS   |Reserved|        Page code (08h)                              |cO |-----+-----------------------------------------------------------------------|eO | 1   |                          Page length (0Ah)                            |oO |-----+-----------------------------------------------------------------------|nO | 2   |                          Reserved          |  WCE   |   MF   |  RCD   |uO |-----+-----------------------------------------------------------------------|sO | 3   |   Demand read retention priority  |     Write retention priority      |sO |-----+-----------------------------------------------------------------------|fO | 4   | (MSB)                                                                 |oO |-----+---                       Disable pre-fetch transfer length         ---|eO | 5   |                                                                 (LSB) |lO |-----+-----------------------------------------------------------------------|gO | 6   | (MSB)                                                                 |rO |-----+---                       Minimum pre-fetch                         ---| O | 7   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|=O | 8   | (MSB)                                                                 | O |-----+---                       Maximum pre-fetch                         ---|-O | 9   |                                                                 (LSB) |pO |-----+-----------------------------------------------------------------------|pO | 10  | (MSB)                                                                 |)O |-----+---                       Maximum pre-fetch ceiling                 ---| O | 11  |                                                                 (LSB) | O +=============================================================================+     J The parameters savable (PS) bit is only used with the MODE SENSE command. C This bit is reserved with the MODE SELECT command.  A PS bit of one I indicates that the target is capable of saving the page in a non-volatileeJ vendor-specific location.  If the PS is set to one in MODE SENSE data thenI the page shall be savable by issuing a MODE SELECT command with SP set toh one.  F A write cache enable (WCE) bit of zero specifies that the target shallH return GOOD status for a WRITE command after successfully writing all ofG the data to the medium.  A WCE bit of one specifies that the target maygG return GOOD status for a WRITE command after successfully receiving ther? data and prior to having successfully written it to the medium.   H A multiplication factor (MF) bit of zero specifies that the target shallI interpret the minimum and maximum pre-fetch fields in terms of the number G of logical blocks for each of the respective types of pre-fetch.  An MFmD bit of one specifies that the target shall interpret the minimum andD maximum pre-fetch fields to be specified in terms of a scaler numberH which, when multiplied by the number of logical blocks to be transferredH for the current command, yields the number of logical blocks for each of" the respective types of pre-fetch.  D A read cache disable (RCD) bit of zero specifies that the target mayH return data requested by a READ command by accessing either the cache orH media.  A RCD bit of one specifies that the target shall transfer all ofI the data requested by a READ command from the medium (i.e. data cannot be  transferred from the cache).  D The demand read retention priority field (see table 157) advises theH target on the retention priority to assign data read into the cache that; has also been transferred from the target to the initiator.   A              Table 157 - Demand read and write retention priority O +===========-=================================================================+ O |   Value   |  Description                                                    | O |-----------+-----------------------------------------------------------------| O |     0h    |  Indicates the target should not distinguish between retaining  | O |           |  the indicated data and data placed into the cache memory by    | O |           |  other means (e.g. pre-fetch).                                  | O |           |                                                                 | O |     1h    |  Demand read retention priority:  Data put into the cache via a | O |           |  READ command should be replaced sooner (has lower priority)    | O |           |  than data placed into the cache by other means (e.g.           | O |           |  pre-fetch).                                                    | O |           |                                                                 | O |           |  Write retention priority:  Data put into the cache during a    | O |           |  WRITE or WRITE AND VERIFY command should be replaced sooner    | O |           |  (has lower priority) than data placed into the cache by other  | O |           |  means (e.g. pre-fetch).                                        | O |           |                                                                 |-O |     Fh    |  Demand read retention priority:  Data put into the cache via a | O |           |  READ command should not be replaced if there is other data in  |rO |           |  the cache that was placed into the cache by other means (e.g.  |-O |           |  pre-fetch) and it may be replaced (i.e. it is not locked).     |SO |           |                                                                 |SO |           |  Write retention priority:  Data put into the cache during a    |TO |           |  WRITE or WRITE AND VERIFY command should not be replaced if    |fO |           |  there is other data in the cache that was placed into the cache|=O |           |  by other means (e.g. pre-fetch) and it may be replaced (i.e.   | O |           |  it is not locked).                                             |tO |           |                                                                 |eO |  2h - Eh  |  Reserved                                                       |=O +=============================================================================+     H The write retention priority field (see table 157) advises the target onJ the retention priority to assign data written into the cache that has also5 been transferred from the cache memory to the medium.=  J An anticipatory pre-fetch occurs when data is placed in the cache that hasI not been requested.  This usually happens in conjunction with the reading F of data that has been requested.  All the following parameters give anI indication to the target how it should manage the cache based on the lastnA READ command.  An anticipatory pre-fetch may occur based on othertJ information. All the remaining caching parameters are only recommendationsD to the target and should not cause a CHECK CONDITION to occur if the" target cannot satisfy the request.  C The disable pre-fetch transfer length field specifies the selectiveoH disabling of anticipatory pre-fetch on long transfer lengths.  The valueJ in this field is compared to the number of blocks requested by the currentG READ command.  If the number of blocks is greater than the disable pre-eI fetch transfer length, then an anticipatory pre-fetch is not done for theeI command.  Otherwise the target should attempt an anticipatory pre-fetch. =A If the pre-fetch disable transfer length is set to zero, then all I anticipatory pre-fetching is disabled for any request for data, including- those for zero logical blocks.  D The minimum pre-fetch field indicates either a number of blocks or aG scaler multiplier of the transfer length, depending upon the setting of I the MF bit.  In either case, the resulting number of blocks is the number A to pre-fetch regardless of the delays it might cause in executing  subsequent commands.  H The pre-fetching operation begins at the logical block immediately afterH the last logical block of the previous READ command.  Pre-fetching shallF always halt before the end of the media.  Errors that occur during theI pre-fetching operation shall not be reported to the initiator unless thateD target cannot, as a result of the error, execute subsequent commandsH correctly.  In this case the error may be reported either immediately asE an error for the current READ command, or as a deferred error, at the J discretion of the target and according to the rules for reporting deferred errors.6  C If pre-fetch has read more than the amount of data indicated by the I minimum pre-fetch then pre-fetching should be terminated whenever another D command is ready to execute.  This consideration is ignored when the5 minimum pre-fetch is equal to the maximum pre-fetch. a  D The maximum pre-fetch field indicates either a number of blocks or aG scaler multiplier of the transfer length, depending upon the setting of I the MF bit.  In either case, the resulting number of blocks is the number=E to pre-fetch if there are no delays in executing subsequent commands.   G The maximum pre-fetch field contains the maximum amount of data to pre- D fetch into the cache as a result of one READ command.  It is used inG conjunction with the disable pre-fetch transfer length and maximum pre-n@ fetch ceiling parameters to trade off pre-fetching new data with0 displacing old data already stored in the cache.  J The maximum pre-fetch ceiling field specifies an upper limit on the numberG of logical blocks computed as the maximum pre-fetch.  If this number oftH blocks is greater than the maximum pre-fetch, then the number of logicalI blocks to pre-fetch shall be truncated to the value stored in the maximume pre-fetch ceiling field.  N    NOTE 124 If the MF bit is one the maximum pre-fetch ceiling field is useful4    in limiting the amount of data to be pre-fetched.   9.3.3.2 Flexible disk page  J The flexible disk page (see table 158) contains parameters for control and, reporting of flexible disk drive parameters.  6                         Table 158 - Flexible disk pageO +=====-========-========-========-========-========-========-========-========+8O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |-O |Byte |        |        |        |        |        |        |        |        |(O |=====+========+========+=====================================================|-O | 0   |   PS   |Reserved|         Page code (05h)                             | O |-----+-----------------------------------------------------------------------|-O | 1   |                           Page length in bytes (1Eh)                  | O |-----+-----------------------------------------------------------------------|-O | 2   | (MSB)                                                                 | O |-----+---                        Transfer rate                            ---|fO | 3   |                                                                  (LSB)| O |-----+-----------------------------------------------------------------------|-O | 4   |                           Number of heads                             | O |-----+-----------------------------------------------------------------------|fO | 5   |                           Sectors per track                           | O |-----+-----------------------------------------------------------------------|-O | 6   | (MSB)                                                                 | O |-----+---                     Data bytes per sector                      ----|fO | 7   |                                                                  (LSB)| O |-----+-----------------------------------------------------------------------|-O | 8   | (MSB)                                                                 | O |-----+---                       Number of cylinders                       ---|fO | 9   |                                                                  (LSB)| O |-----+-----------------------------------------------------------------------|=O | 10  | (MSB)                                                                 |sO |-----+---                Starting cylinder-write precompensation             |nO | 11  |                                                                  (LSB)|aO |-----+-----------------------------------------------------------------------|dO | 12  | (MSB)                                                                 |tO |-----+---                Starting cylinder-reduced write current             |lO | 13  |                                                                  (LSB)|aO |-----+-----------------------------------------------------------------------|tO | 14  | (MSB)                                                                 |iO |-----+---                       Drive step rate                           ---| O | 15  |                                                                  (LSB)| O |-----+-----------------------------------------------------------------------|sO | 16  |                          Drive step pulse width                       |mO |-----+-----------------------------------------------------------------------| O | 17  | (MSB)                                                                 | O |-----+---                       Head settle delay                         ---|tO | 18  |                                                                  (LSB)|aO |-----+-----------------------------------------------------------------------|rO | 19  |                          Motor on delay                               |aO |-----+-----------------------------------------------------------------------| O | 20  |                          Motor off delay                              |sO |-----+-----------------------------------------------------------------------| O | 21  | TRDY   |   SSN  |   MO   |            Reserved                        |eO |-----+-----------------------------------------------------------------------|=O | 22  |            Reserved               |               SPC                 | O |-----+-----------------------------------------------------------------------|-O | 23  |                          Write compensation                           |rO |-----+-----------------------------------------------------------------------|tO | 24  |                          Head load delay                              |.O |-----+-----------------------------------------------------------------------| O | 25  |                          Head unload delay                            |nO |-----+-----------------------------------------------------------------------|uO | 26  |             Pin 34                |               Pin 2               | O |-----+-----------------------------------+-----------------------------------| O | 27  |             Pin 4                 |               Pin 1               | O |-----+-----------------------------------------------------------------------|pO | 28  |                                                                       |NO |-----+---                       Medium rotation rate                      ---|iO | 29  |                                                                 (LSB) |fO |-----+-----------------------------------------------------------------------| O | 30  |                          Reserved                                     |nO |-----+-----------------------------------------------------------------------|uO | 31  |                          Reserved                                     |aO +=============================================================================+t    J The parameters savable (PS) bit is only used with the MODE SENSE command. C This bit is reserved with the MODE SELECT command.  A PS bit of oneiI indicates that the target is capable of saving the page in a non-volatile  vendor-specific location.Y  L    NOTE 125 This page is mainly intended for defining parameters of flexibleA    disk drives, but may be used for other devices, if applicable.   H The transfer rate indicates the data rate of the peripheral device.  See0 table 159 for examples of common transfer rates.  :                     Table 159 - Examples of transfer rates* +=========-==============================+* |  Value  |  Transfer rate               |* |---------+------------------------------|* |  00FAh  |  250 kbit/s transfer rate    |* |  012Ch  |  300 kbit/s transfer rate    |* |  01F4h  |  500 kbit/s tranfer rate     |* |  03E8h  |  1 mbit/s transfer rate      |* |  07D0h  |  2 mbit/s transfer rate      |* |  1388h  |  5 mbit/s transfer rate      |* +========================================+    H The number of heads field specifies the number of heads used for readingA and writing data on the medium.  Heads used exclusively for servoe information are excluded.   J The sectors per track field specifies the number of sectors per revolution	 per head.l  I The data bytes per sector field specifies the number of bytes of data pero+ sector that an initiator can read or write.   H The number of cylinders field specifies the number of cylinders used for data storage.   C The starting cylinder for write precompensation field specifies therC cylinder at which write precompensation is to begin.  Cylinders are-@ numbered starting with zero.  If the starting cylinder for writeG precompensation is equal to the value in the number of cylinders field,h8 write precompensation shall be disabled by the target.    H The starting cylinder for reduced write current field specifies cylinderH at which write current is reduced.  Cylinders are numbered starting withI zero.  If the starting cylinder for reduced write current is equal to theoF value in the number of cylinders field, reduced write current shall be disabled by the target.     F The drive step rate field specifies the step rate in units of 100 us. H This value may be rounded as defined in 7.5.4.  A value of zero requests$ the target to set its default value.  I The drive step pulse width field specifies the width of the step pulse ingI microseconds.  This value may be rounded as defined in 7.5.4.  A value ofb2 zero requests the target to set its default value.  J The head settle delay field specifies the head settle time in units of 100D us.  This value may be rounded as defined in 7.5.4.  A value of zero- requests the target to set its default value.t  A If a true ready signal is not available, the motor on delay fieldsJ specifies in tenths of a second the time that the target shall wait beforeG attempting to access the medium after the motor on signal is asserted.  G If a true ready signal is available, the motor on delay field specifieseI in tenths of a second the time that the target shall wait for drive ready G status before aborting an attempt to access the medium.  This value maym! be rounded as defined in 7.5.4.  s  G The motor off delay field specifies in tenths of a second the time thatcH the target shall wait before releasing the motor on signal after an idleJ condition exists.  A value of FFh indicates that the motor on signal shallE not be released.  The START STOP UNIT command is not affected by thiss; parameter. This value may be rounded as defined in 7.5.4.     G A true ready (TRDY) bit of one specifies that a signal is provided thati- indicates the medium is ready to be accessed.   J A start sector number (SSN) bit of one specifies that sectors are numberedJ starting with one.  An SSN bit of zero specifies that sectors are numbered starting with zero.r  H A motor on (MO) bit of one specifies that pin 16 (motor on) shall remainE released.  This bit shall be set to one when using high capacity (192tH tracks per inch) drives and their pre-formatted diskettes.  An MO bit of8 zero indicates that pin 16 (motor on) shall be asserted.  H The step pulse per cylinder (SPC) field is used to specify the number ofF additional step pulses required per cylinder.  Non-zero values allow aD drive to read a diskette formatted on a drive with a lower number ofH tracks per inch.  For example, a value of one allows a 96 track-per-inchI drive to access tracks on a diskette that was formatted for 48 tracks pern inch.d  C The write compensation field is used to specify the amount of write J compensation to be used starting at the cylinder specified in the startingH cylinder for write precompensation field.  The correlation of any valuesI used in this field to actual write precompensation time values is vendor- H specific.  If a zero is specified in this field the target shall use itsJ default write precompensation value.  This value may be rounded as defined in 7.5.4.     K The head load delay field specifies the head loading time in milliseconds. -H This value may be rounded as defined in 7.5.4.  A value of zero requests$ the target to set its default value.  @ The head unload delay field specifies the head unloading time inI milliseconds.  This value may be rounded as defined in 7.5.4.  A value of 2 zero requests the target to set its default value.  G The Pin 34 field defines the usage of pin 34 of the flexible disk drive F interface.  This use of this pin varies among vendors and drives.  TheF settings allow the initiator to select how pin 34 shall be used by the interface.  See table 160.  3                            Table 160 - Pin 34 field O +==============-==============================================================+-O | Bit 7 6 5 4  |  Description of pin 34 use                                   | O |--------------+--------------------------------------------------------------|-O |     P 0 0 0  |  Open                                                        | O |     P 0 0 1  |  Ready                                                       | O |     P 0 1 0  |  Disk changed                                                | O |-----------------------------------------------------------------------------|-O |  NOTES                                                                      | O |   1  P is a polarity bit, where 0 is active low and 1 is active high.       | O |   2  All undefined values are reserved.                                     | O +=============================================================================+-    E The pin 4 field defines the usage of pin 4 of the flexible disk drive H interface.  This use of this pin varies among drive vendors and drives. G  The settings allow the initiator to specify how pin 4 shall be used by  the interface.  See table 161.  2                            Table 161 - Pin 4 fieldO +==============-==============================================================+ O | Bit 7 6 5 4  |  Description of pin 4 use                                    |eO |--------------+--------------------------------------------------------------| O |     P 0 0 0  |  Open                                                        |-O |     P 0 0 1  |  In use                                                      | O |     P 0 1 0  |  Eject                                                       |aO |     P 0 0 0  |  Head load                                                   | O |-----------------------------------------------------------------------------|-O |  NOTES                                                                      |uO |   1  P is a polarity bit, where 0 is active low and 1 is active high.       |-O |   2  All undefined values are reserved.                                     | O +=============================================================================+d    E The pin 1 field defines the usage of pin 1 of the flexible disk drive F interface.  This use of this pin varies among vendors and drives.  TheF settings allow the initiator to specify how pin 1 shall be used by the interface.  See table 162.  3                            Table 162 - Pin 34 field-O +==============-==============================================================+ O | Bit 7 6 5 4  |  Description of pin 34 use                                   |-O |--------------+--------------------------------------------------------------|NO |     P 0 0 0  |  Open                                                        |-O |     P 0 0 1  |  Disk change reset                                           |sO |-----------------------------------------------------------------------------|-O |  NOTES                                                                      | O |   1  P is a polarity bit, where 0 is active low and 1 is active high.       |-O |   2  All undefined values are reserved.                                     | O +=============================================================================+-    F The medium rotation rate field specifies the speed at which the mediumH rotates.  The unit of measure is rotations per minute (e.g. 2 400 rpm). 6 This field cannot be changed by a MODE SELECT command.   9.3.3.3 Format device page  H The format device page (see table 163) contains parameters which specify the medium format.  6                         Table 163 - Format device pageO +=====-========-========-========-========-========-========-========-========+-O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |-O |=====+========+========+=====================================================| O | 0   |   PS   |Reserved|            Page code (03h)                          |-O |-----+-----------------------------------------------------------------------| O | 1   |                              Page length (16h)                        |-O |-----+-----------------------------------------------------------------------| O | 2   | (MSB)                                                                 |=O |-----+---                  Tracks per zone                                ---| O | 3   |                                                                 (LSB) |sO |-----+-----------------------------------------------------------------------|tO | 4   | (MSB)                                                                 |iO |-----+---                  Alternate sectors per zone                     ---|bO | 5   |                                                                 (LSB) |nO |-----+-----------------------------------------------------------------------|xO | 6   | (MSB)                                                                 |rO |-----+---                  Alternate tracks per zone                      ---|aO | 7   |                                                                 (LSB) |kO |-----+-----------------------------------------------------------------------| O | 8   | (MSB)                                                                 |DO |-----+---                  Alternate tracks per logical unit              ---| O | 9   |                                                                 (LSB) |eO |-----+-----------------------------------------------------------------------|eO | 10  | (MSB)                                                                 |lO |-----+---                  Sectors per track                              ---|rO | 11  |                                                                 (LSB) |rO |-----+-----------------------------------------------------------------------|iO | 12  | (MSB)                                                                 | O |-----+---                  Data bytes per physical sector                 ---|dO | 13  |                                                                 (LSB) |mO |-----+-----------------------------------------------------------------------|eO | 14  | (MSB)                                                                 |rO |-----+---                  Interleave                                     ---|rO | 15  |                                                                 (LSB) |uO |-----+-----------------------------------------------------------------------|rO | 16  | (MSB)                                                                 |hO |-----+---                  Track skew factor                              ---| O | 17  |                                                                 (LSB) |pO |-----+-----------------------------------------------------------------------|aO | 18  | (MSB)                                                                 | O |-----+---                  Cylinder skew factor                           ---|iO | 19  |                                                                 (LSB) |oO |-----+-----------------------------------------------------------------------|iO | 20  |  SSEC  |  HSEC  |  RMB   |  SURF  |             Reserved              |iO |-----+-----------------------------------------------------------------------|oO | 21  |                                                                       |eO |- - -+---                  Reserved                                       ---|oO | 23  |                                                                       |uO +=============================================================================+     J The parameters savable (PS) bit is only used with the MODE SENSE command. C This bit is reserved with the MODE SELECT command.  A PS bit of oneiI indicates that the target is capable of saving the page in a non-volatile  vendor-specific location.t  K    NOTE 126 If the initiator changes any of the current physical parametersaO    defined below, the target may not be able to access the media until a FORMATi0    UNIT command has been successfully completed.  D If the defect handling format parameters (tracks per zone, alternateD sectors per zone, alternate tracks per zone and alternate tracks perI logical unit) requested by the initiator are not supported by the target  F the target may round these fields to acceptable values as described in 7.5.4.    H The tracks per zone field specifies the number of tracks per zone to useD in dividing the capacity of the device for the purpose of allocatingJ alternate sectors.  A value of zero means that one zone is defined for theF entire device.  The last zone on the device might not contain the same+ number of tracks as the previous zone(s).  w  H The alternate sectors per zone field specifies the number of sectors perH zone the target shall reserve for defect handling.  The target shall de-G allocate these sectors from the initiator addressable blocks during thehH FORMAT UNIT command.  If the notch page is implemented and the ND bit ofE the notch page is one and the active notch field of the notch page isrG zero, then a value of zero indicates that no alternate sectors shall benB reserved.  Otherwise, a value of zero indicates that the number of% alternate sectors is target specific.   F The alternate tracks per zone field specifies the number of tracks perH zone the target shall reserve for defect handling.  The target shall de-F allocate these tracks from the initiator addressable blocks during theH FORMAT UNIT command.  If the notch page is implemented and the ND bit ofE the notch page is one and the active notch field of the notch page isuF zero, then a value of zero indicates that no alternate tracks shall beB reserved.  Otherwise, a value of zero indicates that the number of$ alternate tracks is target specific.  J The alternate tracks per logical unit field specifies the number of tracksI per logical unit the target shall reserve for defect handling. The targetcD shall de-allocate these tracks from the initiator addressable blocksI during the FORMAT UNIT command.  If the notch page is implemented and the=G ND bit of the notch page is one and the active notch field of the notch E page is zero, then a value of zero indicates that no alternate tracks-H shall be reserved.  Otherwise, a value of zero indicates that the number' of alternate tracks is target specific.   F The sectors per track field specifies the number of physical sectors  G included within each track.  This number includes any alternate sectors F the target may allocate.  A value of zero during MODE SELECT indicatesJ that the target shall define the number of sectors per track.  For devicesE with a variable number of sectors per track, the value in MODE SELECTvD shall be zero and the value reported in MODE SENSE for the number of% sectors per track is vendor-specific.   E The data bytes per physical sector field specifies the number of data=G bytes per physical sector that the target shall use.  This value may belH different than the logical block size reported in the MODE SELECT data. H The target shall return CHECK CONDITION status if it determines that theD combination of this field and the sectors per track field exceed theH capability of the medium.  A value of zero indicates that the data bytes- per physical sector is defined by the target.i  H For MODE SENSE the interleave field returns the same parameter passed inE the FORMAT UNIT command, The target shall report this field as target-F defined in the corresponding MODE SENSE command.  For MODE SELECT this field is ignored.-  O    NOTE 127 It is recommended that this field be marked non-changeable and that N    initiators send the value returned in MODE SENSE.  This allows migration toJ    specifying interleave as a mode parameter instead of in the FORMAT UNIT    command.-  D The track skew factor field specifies the number of physical sectorsG between the last logical block of one track and the first logical block 2 on the next sequential track of the same cylinder.  G The cylinder skew factor field specifies the number of physical sectorseJ between the last logical block of one cylinder and the first logical block  on the next sequential cylinder.  G The SSEC bit set to one indicates that the target shall use soft sectorl formatting.r  G The HSEC bit set to one indicates that the target shall use hard sectoreI formatting.  The HSEC bit and the SSEC bit are mutually exclusive in MODEn SELECT commands.  J The combinations sector formatting supported that are reported in response9 to a request for default values are defined in table 164.=  D           Table 164 - Reporting of default sector formatting supportH +======-======-========================================================+H | SSEC | HSEC |  Description                                           |H |------+------+--------------------------------------------------------|H |   0  |   0  |  Target shall not return this combination              |H |   1  |   0  |  Target supports soft sector formatting only           |H |   0  |   1  |  Target supports hard sector formatting only           |H |   1  |   1  |  Target supports both soft and hard sector formatting  |H +======================================================================+    J The combinations sector formatting supported that are reported in response< to a request for changeable values are defined in table 165.  E         Table 165 - Reporting of changeable sector formatting supportgH +======-======-========================================================+H | SSEC | HSEC |  Description                                           |H |------+------+--------------------------------------------------------|H |   0  |   0  |  Sector formatting not changeable                      |H |   1  |   0  |  Target shall not return this combination              |H |   0  |   1  |  Target shall not return this combination              |H |   1  |   1  |  Target supports both soft and hard sector formatting  |H +======================================================================+    B The removable (RMB) bit set to one indicates that the logical unitD supports removable media.  A RMB  bit set to zero indicates that theF logical unit does not support removable media.  The status of this bitD shall be reflected in the INQUIRY command removable media bit (RMB).  B The surface (SURF) bit set to zero indicates that the target shallF allocate progressive addresses to all logical blocks within a cylinderG prior to allocating addresses on the next cylinder.  A  SURF bit set to I one indicates that the target shall allocate progressive addresses to all-G logical blocks on a surface prior to allocating sector addresses on the 
 next surface.   M    NOTE 128 If the target supports savable parameters, all savable parameters N    for this initiator, including those in page codes 3, 4, and 5, are saved toG    non-volatile memory when the save parameters bit (SP) in the command-O    descriptor block is set to one.  The savable parameters may also be saved to @    non-volatile memory during a FORMAT UNIT command (see 9.2.1).  # 9.3.3.4 Medium types supported pagee  F The medium types supported page (see table 166) contains a list of the9 medium types implemented by the target for logical units.-  :                    Table 166 - Medium types supported pageO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        | O |=====+========+========+=====================================================|-O | 0   |   PS   |Reserved|         Page code (0Bh)                             | O |-----+-----------------------------------------------------------------------| O | 1   |                           Page length (06h)                           | O |-----+-----------------------------------------------------------------------|-O | 2   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------| O | 3   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|-O | 4   |                           Medium type one supported                   | O |-----+-----------------------------------------------------------------------| O | 5   |                           Medium type two supported                   | O |-----+-----------------------------------------------------------------------|-O | 6   |                           Medium type three supported                 | O |-----+-----------------------------------------------------------------------| O | 7   |                           Medium type four supported                  | O +=============================================================================+-    J The parameters savable (PS) bit is only used with the MODE SENSE command. C This bit is reserved with the MODE SELECT command.  A PS bit of one I indicates that the target is capable of saving the page in a non-volatile  vendor-specific location.   H The code values for each medium type supported by the target (up to fourF maximum), are reported in ascending order.  If only the default mediumG type is supported zero is reported.  If less than four medium types are-7 supported the unused entries shall be returned as zero.     9.3.3.5 Notch and partition page  D The notch page (see table 167) contains parameters for direct-accessD devices which implement a variable number of blocks per cylinder andD support this page.  Each clause of the logical unit with a different8 number of blocks per cylinder is referred to as a notch.  2                             Table 167 - Notch pageO +=====-========-========-========-========-========-========-========-========+bO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |tO |Byte |        |        |        |        |        |        |        |        |hO |=====+========+========+=====================================================|cO | 0   |   PS   |Reserved|         Page code (0Ch)                             | O |-----+-----------------------------------------------------------------------|eO | 1   |                           Page length (16h)                           |eO |-----+-----------------------------------------------------------------------|fO | 2   |   ND   |  LPN   |         Reserved                                    | O |-----+-----------------------------------------------------------------------|eO | 3   |                           Reserved                                    |tO |-----+-----------------------------------------------------------------------|oO | 4   | (MSB)                                                                 | O |-----+---                        Maximum number of notches                ---| O | 5   |                                                                 (LSB) |hO |-----+-----------------------------------------------------------------------|gO | 6   | (MSB)                                                                 |eO |-----+---                        Active notch                             ---|sO | 7   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------| O | 8   | (MSB)                                                                 |lO |- - -+---                        Starting boundary                        ---|bO | 11  |                                                                 (LSB) |NO |-----+-----------------------------------------------------------------------| O | 12  | (MSB)                                                                 | O |- - -+---                        Ending boundary                          ---|gO | 15  |                                                                 (LSB) |oO |-----+-----------------------------------------------------------------------|eO | 16  | (MSB)                                                                 |tO |- - -+---                        Pages notched                            ---| O | 23  |                                                                 (LSB) |vO +=============================================================================+a    J The parameters savable (PS) bit is only used with the MODE SENSE command. C This bit is reserved with the MODE SELECT command.  A PS bit of onecI indicates that the target is capable of saving the page in a non-volatilet vendor-specific location.t  I A notched drive (ND) bit of zero indicates that the device is not notchedeG and that all other parameters in this page shall be returned as zero by G the target.  A ND bit of one indicates that the device is notched.  For D each supported active notch value this page defines the starting and ending boundaries of the notch.p  @ A logical or physical notch (LPN) bit of zero indicates that theI boundaries are based on the physical parameters of the logical unit.  TheeG cylinder is considered most significant, the head least significant.  ArG LPN bit of one indicates that the notch boundaries are based on logicali blocks of the logical unit.   C The maximum number of notches field indicates the maximum number oftG notches supported by the logical unit.  This field shall be reported as 
 unchangeable.t  H The active notch field indicates the notch that this and subsequent MODEH SELECT and MODE SENSE commands shall refer to, until the active notch isF changed by a later MODE SELECT command.  The value of the active notchI shall be greater than or equal to 0 and less than or equal to the maximumdI number of notches.  An active notch value of zero indicates that this andiF subsequent MODE SELECT and MODE SENSE commands refer to the parameters that apply across all notches. h  G The starting boundary field indicates the beginning of the active notch F or, if the active notch is zero, the beginning boundary of the logicalE unit.  If the LPN bit is one, then the four bytes represent a logicalrG block address.  If the LPN bit is zero, then the three most significantlH bytes shall represent the cylinder number and the least significant byteA shall represent the head number.  This field shall be reported aslC unchangeable.  When used with the MODE SELECT command this field is  ignored.  I The ending boundary field indicates the ending of the active notch or, ifmI the active notch is zero, the ending of the logical unit.  If the LPN bitmH is one, then the four bytes represent logical block address.  If the LPNF bit is zero, then the three most significant bytes shall represent theG cylinder number and the least significant byte shall represent the head=J number.  This field shall be reported as unchangeable.  When used with the* MODE SELECT command this field is ignored.  H Each notch shall span a set of consecutive logical blocks on the logicalB unit, the notches shall not overlap, and no logical block shall be excluded from a notch.  J The pages notched field is a bit map of the mode page codes that indicatesB which pages contain parameters that may be different for differentI notches.  The most significant bit of this field corresponds to page code=I 3Fh and the least significant bit corresponds to page code 00h.  If a bittH is one, then the corresponding mode page contains parameters that may beJ different for different notches.  If a bit is zero, then the correspondingF mode page contains parameters that are constant for all notches.  This( field shall be reported as unchangeable.  & 9.3.3.6 Read-write error recovery page  F The read-write error recovery page (see table 168) specifies the errorI recovery parameters the target shall use during any command that performs J a read or write operation to the medium (e.g. READ(6), READ(10), WRITE(6),0 WRITE(10), COPY, COMPARE, WRITE & VERIFY, etc.).  <                   Table 168 - Read-write error recovery pageO +=====-========-========-========-========-========-========-========-========+=O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |oO |Byte |        |        |        |        |        |        |        |        |zO |=====+========+========+=====================================================|sO | 0   |   PS   |Reserved|        Page code (01h)                              |.O |-----+-----------------------------------------------------------------------|pO | 1   |                           Page length (0Ah)                           | O |-----+-----------------------------------------------------------------------|eO | 2   |  AWRE  |  ARRE  |   TB   |   RC   |  EER   |  PER   |  DTE   |  DCR   | O |-----+-----------------------------------------------------------------------|eO | 3   |                           Read retry count                            |cO |-----+-----------------------------------------------------------------------| O | 4   |                           Correction span                             | O |-----+-----------------------------------------------------------------------|MO | 5   |                           Head offset count                           |mO |-----+-----------------------------------------------------------------------|eO | 6   |                           Data strobe offset count                    |yO |-----+-----------------------------------------------------------------------|=O | 7   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------| O | 8   |                           Write retry count                           |=O |-----+-----------------------------------------------------------------------| O | 9   |                           Reserved                                    |-O |-----+-----------------------------------------------------------------------| O | 10  | (MSB)                                                                 |-O |-----+---                        Recovery time limit                      ---| O | 11  |                                                                 (LSB) |-O +=============================================================================+     J The parameters savable (PS) bit is only used with the MODE SENSE command. C This bit is reserved with the MODE SELECT command.  A PS bit of onenI indicates that the target is capable of saving the page in a non-volatile- vendor-specific location.-  H An automatic write reallocation enabled (AWRE) bit of one indicates thatE the target shall enable automatic reallocation to be performed during-H write operations.  The automatic reallocation shall be performed only ifB the target has the valid data (e.g. original data in the buffer orB recovered from the medium).  The valid data shall be placed in theJ reallocated block.  Error reporting as required by the error recovery bitsH (EER, PER, DTE, and DCR) shall be performed only after completion of theH reallocation.  The reallocation operation shall report any failures thatF occur.  See the REASSIGN BLOCKS command (9.2.10) for error procedures.  I An AWRE bit of zero indicates that the target shall not perform automatice> reallocation of defective data blocks during write operations.  G An automatic read reallocation enabled (ARRE) bit of one indicates thatrG the target shall enable automatic reallocation of defective data blocks I during read operations.  All error recovery actions required by the erroruB recovery bits (TB, EER, PER, DTE, and DCR) shall be executed.  TheA automatic reallocation shall then be performed only if the targetcJ successfully recovers the data.  The recovered data shall be placed in theJ reallocated block.  Error reporting as required by the error recovery bitsB shall be performed only after completion of the reallocation.  TheC reallocation process shall present any failures that occur. See the=7 REASSIGN BLOCKS command (9.2.10) for error procedures.    I An ARRE bit of zero indicates that the target shall not perform automatic = reallocation of defective data blocks during read operations.=  H A transfer block (TB) bit of one indicates that a data block that is notJ recovered within the recovery limits specified shall be transferred to theF initiator before CHECK CONDITION status is returned.  A TB bit of zero@ indicates that such a data block shall not be transferred to theE initiator.  The TB bit does not affect the action taken for recovered- data.-  I A read continuous (RC) bit of one indicates the target shall transfer thedF entire requested length of data without adding delays to perform errorH recovery procedures.  This implies that the target may send data that isH erroneous or fabricated in order to maintain a continuous flow of data. C The target shall assign priority to this bit over conflicting error 9 control bits (EER, DCR, DTE, and PER) within this byte.     J    NOTE 129 Fabricated data may be data already in the buffer or any otherP    target-specific data.  This bit is typically used in image processing, audio,    or video applications.-  D A RC bit of zero indicates that error recovery operations that causeB delays are acceptable during the data transfer.  Data shall not be fabricated.   I The individual bit definitions for EER, PER, DTE and DCR are contained in G table 169.  The combinations of these bits are explained in table 170.    <                   Table 169 - Error recovery bit definitionsR +====================-===========================================================+R |EER  PER  DTE  DCR  |  Description                                              |R |--------------------+-----------------------------------------------------------|R | 1    -    -    -   |  An enable early recovery (EER) bit of one indicates that |R |                    |  the target shall use of the most expedient form of error |R |                    |  recovery first.  This bit only applies to data error     |R |                    |  recovery and it does not affect positioning retries and  |R |                    |  the message system error recovery procedures.            |R |                    |                                                           |R | 0    -    -    -   |  An EER bit of zero indicates that the target shall use an|R |                    |  error recovery procedure that minimizes the risk of mis- |R |                    |  detection or mis-correction.                             |R |                    |                                                           |R | -    1    -    -   |  A post error (PER) bit of one indicates that the target  |R |                    |  shall report recovered errors.                           |R |                    |                                                           |R | -    0    -    -   |  A PER bit of zero indicates that the target shall not    |R |                    |  report recovered errors.  Error recovery procedures shall|R |                    |  be performed within the limits established by the error  |R |                    |  recovery parameters.                                     |R |                    |                                                           |R | -    -    1    -   |  A disable transfer on error (DTE) bit of one indicates   |R |                    |  that the target shall terminate the data phase upon      |R |                    |  detection of a recovered error.                          |R |                    |                                                           |R | -    -    0    -   |  A DTE bit of zero indicates that the target shall not    |R |                    |  terminate the data phase upon detection of a recovered   |R |                    |  error.                                                   |R |                    |                                                           |R | -    -    -    1   |  A disable correction (DCR) bit of one indicates that     |R |                    |  error correction codes shall not be used for data error  |R |                    |  recovery.                                                |R |                    |                                                           |R | -    -    -    0   |  A DCR bit of zero allows the use of error correction     |R |                    |  codes for data error recovery.                           |R +================================================================================+    N    NOTE 130 An EER bit of one may imply an increase in the probability of mis-L    detection or mis-correction.  An EER bit of zero typically means that theL    specified retry limit is exhausted prior to using error correction codes.  D           Table 170 - Combined error recovery parameter descriptionsR +====================-===========================================================+R |EER  PER  DTE  DCR  |  Description                                              |R |--------------------+-----------------------------------------------------------|R | 0    0    0    0   |  The full number of retries (specified in the read, write |R |                    |  or verify retry count field) and error correction are    |R |                    |  attempted to recover the data (EER and DCR set to 0).  A |R |                    |  CHECK CONDITION is not reported at the completion of the |R |                    |  command for recovered errors (PER set to 0).  The command|R |                    |  terminates with CHECK CONDITION status before the        |R |                    |  transfer count is exhausted only if an unrecoverable     |R |                    |  error is detected.  If an unrecoverable data error       |R |                    |  occurred, the data in the block with the unrecoverable   |R |                    |  error may or may not be transferred to the initiator     |R |                    |  depending on the setting of the transfer block (TB) bit  |R |                    |  (read operation only).                                   |R |                    |                                                           |R | 0    0    0    1   |  Error correction is disabled (DCR set to one) so only the|R |                    |  full number of retries (specified in the read, write or  |R |                    |  verify retry count field) are attempted to recover the   |R |                    |  data (EER set to 0).  A CHECK CONDITION is not reported  |R |                    |  at the completion of the command for recoverable errors  |R |                    |  (PER set to 0).  The command terminates with CHECK       |R |                    |  CONDITION status before the transfer count is exhausted  |R |                    |  only if an unrecoverable error is detected.  If an       |R |                    |  unrecoverable data error occurred, the data in the block |R |                    |  with the unrecoverable error may or may not be           |R |                    |  transferred to the initiator depending on the setting of |R |                    |  the transfer block (TB) bit (read operation only).       |R |                    |                                                           |R | 0    0    1    0   |  Invalid mode (PER must be set to one if DTE is set to    |R |                    |  one).  1)                                                |R |                    |                                                           |R | 0    0    1    1   |  Invalid mode (PER must be set to one if DTE is set to    |R |                    |  one).  1)                                                |R |                    |                                                           |R | 0    1    0    0   |  The full number of retries (specified in the read, write |R |                    |  or verify retry count field) and error correction are    |R |                    |  attempted to recover the data (EER and DCR set to 0).    |R |                    |  The command terminates with CHECK CONDITION status before|R |                    |  the transfer count is exhausted only if an unrecoverable |R |                    |  error is detected.  If an unrecoverable data error       |R |                    |  occurred, the data in the block with the unrecoverable   |R |                    |  error may or may not be transferred to the initiator     |R |                    |  depending on the setting of the transfer block (TB) bit  |R |                    |  (read operation only).  A CHECK CONDITION with a sense   |R |                    |  key of RECOVERED ERROR is reported at the completion of  |R |                    |  the command for any recoverable error that occurs (PER   |R |                    |  set to 1).  The information field in the sense data shall|R |                    |  contain the logical block address of the last recovered  |R |                    |  error which occurred during the transfer.                |R +================================================================================+     Table 170 - (continued)eR +====================-===========================================================+R |EER  PER  DTE  DCR  |  Description                                              |R |--------------------+-----------------------------------------------------------|R |                    |                                                           |R | 0    1    0    1   |  Error correction is disabled (DCR set to one) so only the|R |                    |  full number of retries (specified in the read, write or  |R |                    |  verify retry count field) are attempted to recover the   |R |                    |  data (EER set to 0).  The command terminates with CHECK  |R |                    |  CONDITION status before the transfer count is exhausted  |R |                    |  only if an unrecoverable error is detected.  If an       |R |                    |  unrecoverable data error occurred, the data in the block |R |                    |  with the unrecoverable error may or may not be           |R |                    |  transferred to the initiator depending on the setting of |R |                    |  the transfer block (TB) bit (read operation only).  A    |R |                    |  CHECK CONDITION with a sense key of RECOVERED ERROR is   |R |                    |  reported at the completion of the command for any        |R |                    |  recoverable error that occurs (PER set to 1).  The       |R |                    |  information field in the sense data shall contain the    |R |                    |  logical block address of the last recovered error which  |R |                    |  occurred during the transfer.                            |R |                    |                                                           |R | 0    1    1    0   |  The full number of retries (specified in the read, write |R |                    |  or verify retry count field) and error correction are    |R |                    |  attempted to recover the data (EER and DCR set to 0).    |R |                    |  The command terminates with CHECK CONDITION status before|R |                    |  the transfer count is exhausted if any error (recoverable|R |                    |  or unrecoverable) is detected (DTE set to 1).  The       |R |                    |  information field in the sense data shall contain the    |R |                    |  logical block address of the block in error.  If an      |R |                    |  unrecoverable data error occurs the data in the block    |R |                    |  with the error may or may not be transferred to the      |R |                    |  initiator depending on the setting of the transfer block |R |                    |  (TB) bit (read operation only).                          |R |                    |                                                           |R | 0    1    1    1   |  Error correction is disabled (DCR set to one) so only the|R |                    |  full number of retries (specified in the read, write or  |R |                    |  verify retry count field) are attempted to recover the   |R |                    |  data (EER set to 0).  The command terminates with CHECK  |R |                    |  CONDITION status before the transfer count is exhausted  |R |                    |  if any error (recoverable or unrecoverable) is detected  |R |                    |  (DTE set to 1).  The information field in the sense data |R |                    |  shall contain the logical block address of the block in  |R |                    |  error.  If an unrecoverable data error occurs the data in|R |                    |  the block with the error may or may not be transferred to|R |                    |  the initiator depending on the setting of the transfer   |R |                    |  block (TB) bit (read operation only).                    |R |                    |                                                           |R | 1    0    0    0   |  The fewest possible retries and error correction are     |R |                    |  attempted to recover the data (EER set to one and DCR set|R |                    |  to 0).  A CHECK CONDITION is not reported at the         |R |                    |  completion of the command for recoverable errors (PER set|R |                    |  to 0).  The command terminates with CHECK CONDITION      |R |                    |  status before the transfer count is exhausted only if an |R |                    |  unrecoverable error is detected.  If an unrecoverable    |R |                    |  data error occurred, the data in the block with the      |R |                    |  unrecoverable error may or may not be transferred to the |R |                    |  initiator depending on the setting of the transfer block |R |                    |  (TB) bit (read operation only).                          |R +================================================================================+     Table 170 - (concluded) R +=====================-==========================================================+R |EER  PER  DTE  DCR   | Description                                              |R |---------------------+----------------------------------------------------------|R |                     |                                                          |R | 1    0    0    1    | Invalid mode (DCR must be set to zero if EER is set to   |R |                     | one).  1)                                                |R |                     |                                                          |R | 1    0    1    0    | Invalid mode (PER must be set to one if DTE is set to    |R |                     | one).  1)                                                |R |                     |                                                          |R | 1    0    1    1    | Invalid mode (PER must be set to one if DTE is set to    |R |                     | one).  1)                                                |R |                     |                                                          |R | 1    1    0    0    | The fewest possible retries and error correction are     |R |                     | attempted to recover the data (EER set to one and DCR set|R |                     | to 0).  The command terminates with CHECK CONDITION      |R |                     | status before the transfer count is exhausted only if an |R |                     | unrecoverable error is detected.  If an unrecoverable    |R |                     | data error occurred, the data in the block with the      |R |                     | unrecoverable error may or may not be transferred to the |R |                     | initiator depending on the setting of the transfer block |R |                     | (TB) bit (read operation only).  A CHECK CONDITION with a|R |                     | sense key of RECOVERED ERROR is reported at the          |R |                     | completion of the command for any recoverable error that |R |                     | occurs (PER set to 1).  The information field in the     |R |                     | sense data shall contain the logical block address of the|R |                     | last recovered error which occurred during the transfer. |R |                     |                                                          |R | 1    1    0    1    | Invalid mode (DCR must be set to zero if EER is set to   |R |                     | one).  1)                                                |R |                     |                                                          |R | 1    1    1    0    | The fewest possible retries and error correction are     |R |                     | attempted to recover the data (EER set to one and DCR set|R |                     | to 0).  The command terminates with CHECK CONDITION      |R |                     | status before the transfer count is exhausted if any     |R |                     | error (recoverable or unrecoverable) is detected (DTE set|R |                     | to 1).  The information field in the sense data shall    |R |                     | contain the logical block address of the block in error. |R |                     | If an unrecoverable data error occurs the data in the    |R |                     | block with the error may or may not be transferred to the|R |                     | initiator depending on the setting of the transfer block |R |                     | (TB) bit (read operation only).                          |R |                     |                                                          |R | 1    1    1    1    | Invalid mode (DCR must be set to zero if EER is set to   |R |                     | one).  1)                                                |R |--------------------------------------------------------------------------------|R |   1)     If an invalid mode for the error recovery combination is              |R |          sent by the initiator the target shall return CHECK CONDITION         |R |          status with the sense key set to ILLEGAL REQUEST and the              |R |          additional sense code set to INVALID FIELD IN PARAMETER LIST.         |R +================================================================================+    F The read and write retry count fields specify the number of times thatE the target shall attempt its recovery algorithm during read and write D operations, respectively.  If the retry count field and the recoveryG time limit field are both specified in a MODE SELECT command, the field|G that requires the least time for data error recovery actions shall have  priority.  r  E The correction span field specifies the size, in bits, of the largest E data error burst for which data error correction may be attempted.  A G correction span of zero specifies that the target shall use its defaultR* value or that this field is not supported.  E The head offset count field specifies in two's-complement notation antD incremental offset position from the track center to which the heads@ shall be moved.  The effect of this field on write operations isE unspecified.  A head offset count of zero indicates that no offset is=A specified.  A positive value indicates moving in the direction of-F increasing logical block addresses.  A negative value indicates movingB in the direction of decreasing logical block addresses.  Any value? specified in this field does not preclude the target from using-G positive or negative head offset during error recovery.  However, after G any error recovery is completed the target shall return the head offsetn% to the value specified in this field.h  M    NOTE 131 The degree of offset for each incremental value and the number ofoJ    valid values are device specific.  It is recommended that the number ofJ    valid values be equal for the positive and negative head offset counts.  F The target shall return CHECK CONDITION status and shall set the sense= key to ILLEGAL REQUEST if an unsupported head offset value is G specified.  The valid bit shall be set to one and the information field|C shall be set to the positive value of the maximum head offset count D that is supported.  The target shall set the valid bit to zero if it; cannot determine the maximum head offset count supported.  p  H    NOTE 132 If the target does not support this field, it returns a zero$    value in the MODE SENSE command.)  @ The data strobe offset count field specifies in two's-complementC notation an incremental position to which the recovered data strobehE shall be adjusted from its nominal setting.  The effect of this fieldhF on write operations is unspecified.  A value of zero indicates that noE data strobe offset is specified.  A positive value indicates movement C in a positive direction as defined by the target.  A negative value G indicates movement in the negative direction as defined by the target.  C Any value specified in this field does not preclude the target from E using positive or negative data strobe offset during error recovery. pF However, after any error recovery is completed the target shall return< the data strobe offset to the value specified in this field.  M    NOTE 133 The degree of offset for each incremental value and the number of J    valid values are device specific.  It is recommended that the number ofI    valid values be equal for the positive and negative data strobe offset 
    counts.  F The target shall return CHECK CONDITION status and shall set the senseG key to ILLEGAL REQUEST if an unsupported data strobe offset count value D is specified.  The valid bit shall be set to one and the informationC field shall be set to the positive value of the maximum data strobeoF offset count that is supported.  The target shall set the valid bit toG zero if it cannot determine the maximum data strobe offset supported.  t    G    NOTE 134 If the target does not support the data strobe offset count|<    field, it returns a zero value in the MODE SENSE command.  C The recovery time limit field specifies in increments of one ms the G maximum time duration that the target shall use for data error recovery D procedures.  The target may round this value as described in 7.5.4. B The limits in this field specifies the maximum error recovery timeC allowed for any individual logical block.  A recovery time limit of ; zero specifies that the target shall use its default value.   D If both retry count and recovery time limit are specified, the field? that specifies the recovery action of least duration shall have 
 priority.   & 9.3.3.7 Rigid disk drive geometry page  G The rigid disk drive geometry page (see table 171) specifies parameters 7 for direct-access devices employing a rigid disk drive.e  <                   Table 171 - Rigid disk drive geometry pageO +=====-========-========-========-========-========-========-========-========+rO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |nO |Byte |        |        |        |        |        |        |        |        |dO |=====+========+========+=====================================================| O | 0   |   PS   |Reserved|         Page code (04h)                             |iO |-----+-----------------------------------------------------------------------|rO | 1   |                           Page length (16h)                           |HO |-----+-----------------------------------------------------------------------|nO | 2   | (MSB)                                                                 | O |- - -+---                        Number of cylinders                      ---|sO | 4   |                                                                 (LSB) |eO |-----+-----------------------------------------------------------------------|aO | 5   |                           Number of heads                             | O |-----+-----------------------------------------------------------------------||O | 6   | (MSB)                                                                 | O |- - -+---               Starting cylinder-write precompensation           ---|=O | 8   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|=O | 9   | (MSB)                                                                 | O |- - -+---               Starting cylinder-reduced write current           ---|-O | 11  |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|rO | 12  | (MSB)                                                                 | O |-----+---                        Drive step rate                          ---| O | 13  |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------| O | 14  | (MSB)                                                                 | O |- - -+---                        Landing zone cylinder                    ---|bO | 16  |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------| O | 17  |                           Reserved                  |       RPL       |lO |-----+-----------------------------------------------------------------------|cO | 18  |                           Rotational offset                           |oO |-----+-----------------------------------------------------------------------|rO | 19  |                           Reserved                                    |aO |-----+-----------------------------------------------------------------------|rO | 20  | (MSB)                                                                 |oO |-----+---                        Medium rotation rate                     ---|tO | 21  |                                                                 (LSB) |TO |-----+-----------------------------------------------------------------------| O | 22  |                           Reserved                                    | O |-----+-----------------------------------------------------------------------| O | 23  |                           Reserved                                    | O +=============================================================================+     @ The parameters savable (PS) bit is only used with the MODE SENSEF command.  This bit is reserved with the MODE SELECT command.  A PS bitC of one indicates that the target is capable of saving the page in ar& non-volatile vendor-specific location.  H    NOTE 135 This page is intended to define drive geometry parameters ofF    rigid disk drives.  It may be used for other devices if applicable.  F The number of cylinders field defines the number of physical cylinders used for data storage.    G The number of heads field defines the physical number of heads used for ? data storage.  Heads used exclusively for servo information areD
 excluded.   E The starting cylinder for write precompensation field is the physicalf? cylinder at which write precompensation is to begin.  The firste< cylinder is number zero.  If the starting cylinder for writeG precompensation is equal to the value in the number of cylinders field, 6 write precompensation shall be disabled by the target.  E The starting cylinder for reduced write current field is the physicalaB cylinder at which write current is reduced.  The first cylinder isC number zero.  If the starting cylinder for reduced write current iseB equal to the value in the number of cylinders field, reduced write( current shall be disabled by the target.  G The drive step rate field indicates the step rate in 100 ns increments. F The target shall use the drive step rate, greater than or equal to theD drive step rate specified.  If the target rounds this field it shallF terminate the command as described in 7.5.4.  A value of zero requests$ the target to set its default value.  C The landing zone cylinder field indicates two's complement location A where the target shall position the disk heads.  A negative valueiC indicates that the heads are positioned below cylinder zero by thataA number of cylinders.  A positive value greater than the number of|F cylinders indicates that the heads are positioned beyond the cylindersA used for data storage at the cylinder location specified.  A zero=* indicates that the default should be used.  ? The rotational position locking (RPL) field is used for spindleaD synchronization as defined in table 172.  See K of the ANSI X3.170A-6 1991 for further information on synchronized spindles.  :                    Table 172 - Rotational position lockingO +=======-=====================================================================+sO |  RPL  |  Description                                                        |tO |-------+---------------------------------------------------------------------|pO |  00b  |  Indicates that spindle synchronization is disabled or not supported|RO |  01b  |  The target operates as a synchronized-spindle slave                |fO |  10b  |  The target operates as a synchronized-spindle master               |cO |  11b  |  The target operates as a synchronized-spindle master control       |aO +=============================================================================+     K    NOTE 136 The signals and connectors used for rotational position lockinggF    are external to the SCSI bus and are not part of this International    Standard.  C If a target fails to achieve synchronization it shall create a unittE attention condition to all initiators.  The sense key shall be set tonG UNIT ATTENTION and the additional sense code set to RPL STATUS CHANGE. a    F If subsequent to achieving synchronization the target detects a change of synchronization:rD    a)     and, if the logical unit is not presently executing an I/OC           process for the initiator, the target shall create a unitvB           attention condition.  The sense key shall be set to UNITK           ATTENTION and the additional sense code set to RPL STATUS CHANGE. H    b)     and, if the logical unit is presently executing an I/O processG           and no other error occurs, then the target shall return CHECKsJ           CONDITION status.  The sense key shall be set to RECOVERED ERRORG           if the target is able to complete the I/O process or HARDWAREeI           ERROR if the target is unable to complete the I/O process.  Then<           additional sense code is set to RPL STATUS CHANGE.  F The rotational offset indicates the amount of rotational skew that theF target shall use when synchronized.  The rotational skew is applied in? the retarded direction (lagging the synchronized spindle master B control).  The value in the field is the numerator of a fractional? multiplier that has 256 as its denominator (e.g. a value of 128vF indicates a one-half revolution skew).  A value of zero indicates thatB rotational offset shall not be used.  This value may be rounded asE defined in 7.5.4.  The rotational offset is not used when a target ist+ configured as synchronized-spindle master.    @ The medium rotation rate indicates the speed at which the mediumH rotates.  The unit of measure is rotations per minute (e.g. 3 600 rpm).     " 9.3.3.8 Verify error recovery page  B The verify error recovery page (see table 173) specifies the errorG recovery parameters the target shall use during the VERIFY command, the ? verify operation of the WRITE AND VERIFY command and the verify ) operation of the COPY AND VERIFY command.   :                     Table 173 - Verify error recovery pageO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |lO |Byte |        |        |        |        |        |        |        |        |sO |=====+========+========+=====================================================| O | 0   |   PS   |Reserved|            Page code (07h)                          |sO |-----+-----------------------------------------------------------------------|DO | 1   |                           Parameter length (0Ah)                      |mO |-----+-----------------------------------------------------------------------| O | 2   |             Reserved              |  EER   |  PER   |  DTE   |  DCR   |iO |-----+-----------------------------------------------------------------------|lO | 3   |                           Verify retry count                          |uO |-----+-----------------------------------------------------------------------|eO | 4   |                           Verify correction span                      |rO |-----+-----------------------------------------------------------------------|rO | 5   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|aO | 6   |                           Reserved                                    |=O |-----+-----------------------------------------------------------------------| O | 7   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|=O | 8   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|-O | 9   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|-O | 10  | (MSB)                                                                 | O |-----+---                        Verify recovery time limit               ---|-O | 11  |                                                                 (LSB) | O +=============================================================================+-    @ The parameters savable (PS) bit is only used with the MODE SENSEF command.  This bit is reserved with the MODE SELECT command.  A PS bitC of one indicates that the target is capable of saving the page in a & non-volatile vendor-specific location.  B The AWRE bit as defined in the read-write error recovery page (seeA 9.3.3.6) applies to the WRITE AND VERIFY command.  The VERIFY and D COMPARE commands shall not perform automatic reallocation.  The COPYA and COPY AND VERIFY commands might or might not perform automatic > reallocation depending on the settings of the mode parameters.  ; The EER, PER, DTE and DCR bits are defined in 9.3.3.6.  The-0 combinations of these bits is defined in 93.3.6.  C The verify retry count field specifies the number of times that the-G target shall attempt its recovery algorithm during a verify operation.  E If the verify retry count and the verify recovery time limit are both G specified, the one that requires the least time for data error recovery  actions shall have priority.  D The verify correction span field specifies the size, in bits, of the? largest burst data error for which data error correction may be C attempted.  If the target does not implement this field, a value of-$ zero is returned in MODE SENSE data.  C The verify recovery time limit field specifies in increments of one E millisecond the maximum time duration that the target shall use error-E recovery procedures to recover data for an individual logical block.  E The target may round this value as described in 7.5.4.  If the verify F retry count and the verify recovery time limit are both specified, theF one that requires the least time for data error recovery actions shall have priority.  H    NOTE 137 To disable all types of correction and retries the initiatorK    should set the EER bit to zero, the PER, DTE and DCR bits to one and the 5    number of retries and recovery time limit to zero.-  1 9.4 Definitions specific to direct-access devices   C 9.4.1 cache memory:   A temporary (and often volatile) data storage-A area outside the user-accessible area.  A cache memory is usually F faster to access than the medium and thus has the effect of increasingA data throughput by reducing the number of accesses to the medium.-  E 9.4.2 non-volatile medium:  Physical storage medium that retains datav@ written to it for a subsequent read operation through a power-onB condition. An example of this is a disk device that stores data as: magnetic fields that do not require device power to exist.  B 9.4.3 notch:  A notch refers to all or part of the medium having aD consistent set of geometry parameters.  Notches are used to increaseF storage capacity by optimizing the number of sectors per track between the inner and outer tracks.e  G 9.4.4 user-accessible:  The area of the medium that can be read from ore& written to by READ and WRITE commands.  E 9.4.5 volatile medium:  Medium that may not retain data written to itd@ for a subsequent read operation through a power-on condition. AnE example of this is a silicon memory device that loses data written tos it if device power is lost.      10 Sequential-access devices    # 10.1 Sequential-access device models   10.1.1 Physical elements  F Sequential-access devices (called devices below) optimize their use inE storing or retrieving user data in a sequential manner.  Since accessc@ is sequential, position changes typically take a long time, when" compared to direct-access devices.  E Sequential-access devices are usually tape devices.  The remainder ofrE this description is from the point of view of a tape device; however,l( other implementations are not precluded.  D The recording medium for tape devices consists of various widths andE lengths of a flexible substrate coated with a semi-permanent magneticeA material.  The recording medium may be wound onto single reels ordF encapsulated into cartridges containing both a supply reel and a take-@ up reel.  Several American National Standards exist covering the? construction of reels and cartridges for interchange as well as D recording techniques for many of the format or density combinations.  A A complete unit composed of the recording medium and its physical E carrier (e.g. reel, cartridge, cassette) is called a volume.  Volumesi> have an attribute of being mounted or de-mounted on a suitable transport mechanism.  F Mounted is the state of a volume when the device is physically capableE of executing commands that cause the medium to be moved.  A volume isbF de-mounted when it is being loaded, threaded, unloaded, unthreaded, or" when not attached to the device.    B Ready is the state of the device when medium access and non-mediumA access commands can be executed.  The device is not ready when no D volume is mounted or, from the initiator's perspective, whenever allD medium access commands report CHECK CONDITION status and a NOT READYB sense key.  Some devices may have a separate switch function whichG places the device in a not ready state even when a volume is mounted.  s  G The write enabled or write protected state determines when an initiator = may write information on a volume.  This attribute is usually-F controlled by the user of the volume through manual intervention (e.g. thumbwheel switch).t  E The recording medium has two physical attributes called beginning-of-aD medium (BOM) and end-of-medium (EOM).  Beginning-of-medium is at theF end of the medium that is attached to the take-up reel.  End-of-mediumD is at the end of the medium that is attached to the supply reel.  InC some cases, the medium is permanently affixed to one or both of the3
 reel hubs.  B As shown in figure 18, the entire physical length of medium is notF usable for recording data. For most volumes, a length of the medium isC reserved before the beginning-of-medium and after the end-of-mediumtE position. This is done to provide sufficient tape wraps onto the reelnE hub(s) and to ensure that recording starts in an undamaged section of. the medium.b                            7                       Figure 18 - Typical volume layoutr  # 10.1.2 Data storage characteristics   D The position on the medium where a pattern of recorded signal may beD written by one write component is called a track (see figure 19).  AE device may write or read from one or more tracks at a time, dependinge on the format.                          :                    Figure 19 - Typical medium track layout  F On a new volume, recording of one or more tracks begins after mountingD the volume and moving from beginning-of-medium toward end-of-medium.@ The number of tracks written at one time is called a track groupA (TrkGrp).  For recorded volumes, reading in the forward directionl2 follows the same course of tracks as when writing.  ? If not all tracks are recorded at the same time, and the deviceaG reverses direction when approaching end-of-medium and begins writing onn@ remaining tracks, the recording method is called serpentine. ForF serpentine devices that record only one track at a time, each physical1 track represents one track group (see figure 20).a                        <                    Figure 20 - Serpentine recording example   D Some multi-track devices have only one track group, using a parallel> storage format that supports the simultaneous recording of all! available tracks (see figure 21).t                        :                     Figure 21 - Parallel recording example  C The serpentine and parallel recording formats shown in the previoust; examples define tracks as longitudinal patterns of recordedrC information.  One other storage format used by some devices recordsiG tracks diagonally across the medium.  This recording technique is knownY  as helical scan (see figure 22).                        <                   Figure 22 - Helical scan recording example  E For most recording formats, an area at beginning-of-medium contains a=? format identification in the form of a tone burst or some other=C recognizable pattern.  User data is not recorded in this area.  The F format identification is an attribute of a volume used for interchange1 purposes and is defined in applicable standards. =  F When writing, the initiator needs an indication that it is approachingA the end of the permissible recording area.  This position, calleds? early-warning (EW), is typically reported to the initiator at a-F position early enough for the device to write any buffered data to theE medium while still leaving enough room for additional recorded labels-@ or filemarks.  Some American National Standards include physicalD requirements for a marker placed on the medium to be detected by the( device as early-warning (see figure 23).                    7                       Figure 23 - Early-warning example   A For devices which implement large data buffers, the early-warning-D position defined by a physical marker may be too close to the end ofF the recording region to permit emptying the data buffer(s).  For theseG devices, a logical concept of early-warning is often used to signal the B initiator at an appropriate location prior to the physical marker.  ! 10.1.3 Partitions within a volume-  @ Another attribute of a volume is called a partition.  PartitionsE consist of one or more non-overlapped mini-volumes, each with its own-F beginning and ending points, contained within single physical volume. G Each partition (x) within a volume has a defined beginning-of-partition G (BOP x), an early-warning position (EW x), and an end-of-partition (EOP- x).  -  C All volumes have a minimum of one partition called partition 0, the F default data partition.  For devices which support only one partition,@ the beginning-of-partition zero (BOP 0) may be equivalent to the@ beginning-of-medium and the end-of-partition zero (EOP 0) may be  equivalent to the end-of-medium.  D When a volume is mounted, it is logically positioned to beginning ofF the default data partition (BOP 0).  When a REWIND command is received? in any partition (x), the device positions to the beginning-of-  partition (BOP x).  G Partitions on a volume do not need to be recorded in any defined order,=B nor do all partition numbers in a sequence need to be present on a= volume.  It is sufficient for a device to be able to locate abF partition, given its code value, or determine that it does or does not> exist on the volume.  For interchange, information about whichC partitions are present on a volume may be stored on the volume in arB device-defined area (possibly unavailable to the initiator) or theG information may be an intrinsic attribute of the device implementation.c  D Figure 24 shows a possible partition implementation for a four-trackE serpentine recording device, assuming that each track group defines ae
 partition.                    G        Figure 24 - Partitioning example - one partition per track groupi  = Another possible partition implementation for this four-trackeB serpentine recording device is shown in figure 25, using two track  groups to define each partition.                      I     Figure 25 - Partitioning example - one partition per two track groupse  @ The previous examples show the beginning and ending points for aD partition aligned with physical bounds of the medium.  This is not aE mandatory requirement for partitioning; it is sufficient for a deviceyD to be able to locate to and stay in any partition bounded by a BOP x? and EOP x.  In this case, a recorded mark or some other device- B recognizable attribute could be used to delineate the partitions. D Figure 26 shows a possible two-partition implementation for a device with only one track group.                        G       Figure 26 - Partitioning example - two partitions per track group   D Three methods are defined in the MODE SENSE and MODE SELECT commandsG for managing partitions; each method is progressively more difficult to  implement and manage: )    a)     device-defined fixed locations;dA    b)     device-defined based on an initiator supplied number of E           partitions and a device specific allocation algorithm; and,e:    c)     definition by name and capacity by an initiator.  * 10.1.4 Logical elements within a partition  F The area between BOP x and EOP x on a typical recorded volume containsD at least two types of initiator accessible elements, data blocks andF tape marks.  These elements are controlled and transferred between theC initiator and the medium using READ, READ REVERSE, WRITE, and WRITEs FILEMARKS commands.t  @ A unit of data supplied or requested by an initiator is called a: logical block.  Logical blocks are stored according to theF specifications of the format for the volume and may be recorded as oneG or more physical blocks on the medium.  When the physical block and theaF logical block are not recorded in a one-to-one relationship, it is theB responsibility of the device to perform all blocking, de-blocking,? padding, stripping, splitting or rebuilding of the logical datar  block(s) sent by an initiator.    E Filemarks are special recorded elements containing no user data.  The:@ filemark format is defined in some American National Standards. A Initiators traditionally use filemarks to separate user data fromsA labels and logical groupings of data from each other.  Since somepB format standards do not define an explicit end-of-data (EOD), hostF software has often used conventions with filemarks to represent an EODA indication.  At least one American National Standard specificallytD defines filemark use for this purpose.  In some implementations, theE device's EOD definition may be specified the initiator using the MODEt SELECT command.   C A setmark is another type of special recorded element containing norE user data, providing a segmentation scheme hierarchically superior tolF filemarks. This level of segmentation is useful for some high capacityE storage devices to provide concise addressing and fast positioning torG specific sets of data within a partition.  In some implementations, theuF detection and reporting of setmarks may be controlled by the initiator using the MODE SELECT command.  G Inter-block gaps, the gaps between blocks, filemarks, and setmarks, aresG introduced on the medium at the time a block or mark is written withouteB explicit action by the initiator.  Minimum and maximum lengths forE inter-block gaps are defined in some American National Standards.  IngC some devices, the length of inter-block gaps may be selected by thetG initiator using the MODE SELECT command while in other devices the gaps. are fixed and non-changeable.  uA In addition to blocks, filemarks, and setmarks, erase gaps may betB recorded on the medium through use of the ERASE command or device-F initiated error recovery actions.  Although explicitly recorded on theE medium, there is normally no distinction between two contiguous erase B gaps.  An erase gap may be a length of erased medium or a recordedD pattern not distinguishable as a block or mark.  Minimum and maximumF lengths for erase gaps are defined in some American National Standards@ while some devices may have no implementation of an erase gap.    ? After writing data from BOP x, the medium is considered to be amF contiguous grouping of blocks, filemarks, setmarks, and gaps.  CertainF American National Standards define gap lengths which, if exceeded, areB to be considered as having reached blank medium.  Depending on theF format, this blank medium may be treated as an end-of-data indication,C an error recovery area, or an unrecoverable medium error causing aniB interchange error.  Unrecorded volumes (new or erased) may exhibitG blank medium characteristics if an attempt is made to read or space the & volume before data has been written.    @ A sequential-access device may be capable of supporting fixed orB variable length blocks.  The concept of fixed or variable mode forA writing and reading blocks only indicates the method by which thenD initiator specifies the size of a logical block for transfer and notB the method of recording physical blocks on the medium.  However, aB device that supports only fixed-length physical blocks may only beG capable of supporting logical blocks of the same length.  The length of G a logical block is always described in bytes.  The length of a physicalrE block may or may not be recorded as an exact byte count, depending one the format.    10.1.5 Data bufferingi  G A device may contain a temporary storage area capable of holding one ordF more logical blocks - a data buffer.  A device data buffer may includeD any combination of blocks, filemarks, and setmarks in the process ofE being written to the medium, or it may contain read-ahead data blocks  transferred from the medium.  C A device with a data buffer may be capable of operating in either awB buffered mode or an unbuffered mode.  A device with no data bufferD operates only in unbuffered mode.  Either term is only applicable toG the manner in which the device manages information to be written to them= medium. Buffered mode is not applicable during read commands,m= regardless of whether read data passes through a data buffer.e  D A device operating in buffered mode may return GOOD status for writeE operations when all write data has been successfully transferred fromiD the initiator into the device data buffer.  For devices operating inF unbuffered mode, GOOD status is not returned until all requested data,? filemarks, or setmarks are successfully recorded on the medium.l  F When issuing a buffered WRITE FILEMARKS command with the immediate bit= set to one, GOOD status is returned as soon as the command iseC validated.  A WRITE FILEMARKS command with the immediate bit set topF zero causes any buffered blocks, filemarks, and setmarks to be writtenD to the medium.  Upon successful completion of this process, which isA called a synchronize operation, no blocks, filemarks, or setmarksnG remain in the data buffer which have not been written to the medium.  A C synchronize operation has no effect on a data buffer which containsiF only read-ahead data or write data which has already been successfully written to the medium.  E Should an unrecoverable write error occur while in buffered mode, thedF device generates an error condition to the current active command.  IfF no command is active, the error may be reported on the next applicable7 operation as a deferred error (see 8.2.14.2).  For someiG implementations, asynchronous event notification or extended contingentoF allegiance may be required.  Refer to 10.5.5 and 10.7 for descriptionsE of asynchronous event notification and extended contingent allegianceo	 protocol.m  A The READ POSITION command may be used to determine the number andfE storage space of buffered blocks not written before the unrecoverablen error was encountered.  G A device with read-ahead data blocks in the data buffer does not report.G an unrecovered read error until the data block in error is requested bym
 an initiator.i  6 10.1.6 Recorded object descriptors (block identifiers)  = Some recording formats specify that recorded objects (blocks,nB filemarks, and setmarks) have identifiers included in the recordedD information to help determine write sequence and also to help detectE device positioning errors.  The identifier values are unique within al, partition and may be unique within a volume.  G The use of the term block identifier may imply some arithmetic sequencesD applied to the assignment of recorded objects.  The block identifierE assignment algorithm may be defined in an applicable format standard.h  C For some pre-formatted volumes, the identifiers are associated withBD physical blocks.  In variable-length implementations, the identifierF can be associated with a physical block when the logical block and the> physical block have a one-to-one relationship on the medium.    B Some formats may carry both physical and logical block identifiersE recorded on the medium.  When a logical block is split over more than G one physical block, or multiple logical blocks are concatenated to formiE a physical block, the logical block identifier and the physical block C identifier are not the same.  Filemarks and setmarks may or may notiE have recorded identifiers, but if identifiers are used in the format, ? then each mark is assigned a value even if it is not explicitlyo	 recorded.i  B The READ POSITION and LOCATE commands use four-byte fields to holdC these format dependent identifiers.  For some implementations, this @ value may correspond to a real physical location; however, it isG sufficient for the device to map the identifier to a value representingoD the unique recorded object.  With this capability, the READ POSITIONG command may be used to report a device-defined block identifier and therE initiator may use this value with a LOCATE command to position to theiC same location at some future time (provided the volume has not beens rewritten in the interim).    ) 10.1.7 Direction and position definitions   A For sequential-access devices, positioning has the connotation of D logically being in, at, before, or after some defined place within a? volume.  This definition means the position is capable of beingrD repeated under the same circumstances.  The orientation of usage forG the four words (in, at, before, or after) is in one direction, from BOPsB x toward EOP x.  All positioning defined below is worded from thisG perspective.  Devices without buffers have some physical position whichmF relates to these logical positions.  However, these definitions do not@ require the medium to have a physical position equivalent to the* logical position unless explicitly stated.  D The forward direction is defined as logically progressing from BOP xG toward EOP x. The reverse direction is defined as logically progressing G from EOP x toward BOP x.  In serpentine devices, the logical forward ortA reverse direction has an alternating relationship to the physical  motion of the medium.  E  G The concept of being in some position means not being outside a definedeF region.  The definition allows the position to be on the boundary of aE defined region.  When a volume is first mounted, the logical positionsA is always at the beginning of the default data partition (BOP0). cB Whenever a volume is mounted and the medium motion is stopped, theF position is in some partition.  While moving between partitions, there is no stable position.    E The concept of being at some position indicates being positioned to aeB logical or physical extremity of a partition.  A sequential-accessE device may be positioned at beginning-of-medium, at BOP x, at end-of-AG data (EOD), at EOP x, or at end-of-medium (EOM), since these are stablea( positions at extremities of a partition.  F The concept of being before some position indicates that there is someE element (data block, filemark, setmark, or other defined point) whichmG may be encountered when moving toward EOP x, if the proper commands areiF issued.  Being positioned before a particular data block means that ifG the device receives a valid READ command, the data block is transferredsC to the initiator.  This position may also be before EW x and EOP x, F since these are defined points within any partition.  However, if dataE has not been written to the end-of-partition, these points may not ben accessible by the initiator.  E The concept of being after some position indicates that there is somegF element (data block, filemark, setmark, or other defined point) on theB BOP x side of the current position which may be encountered if theB proper commands are issued.  When a READ command for a single dataG block has been successfully executed, the logical position is after thet transferred data block.l   10.1.8 Error reporting  B If any of the following conditions occur during the execution of a< command the target shall return CHECK CONDITION status.  TheC appropriate sense key and additional sense code should be set.  TheaC following list illustrates some error conditions and the applicableuG sense keys.  The list does not provide an exhaustive enumeration of alln5 conditions that may cause the CHECK CONDITION status.p  e Condition                                                                                   Sense Keyiq Invalid logical block address                                                                             ILLEGAL  REQUESTd  n Unsupported option requested                                                                           ILLEGAL REQUESTt  { Target reset or medium change since last command from this initiator                                                       y    UNIT ATTENTIONt  r Self diagnostic failed                                                                                    HARDWARE ERRORb  m Unrecovered read error                                                                                 MEDIUMv ERRORnc                                                                                      HARDWARE ERRORs  s Recovered read or write error                                                                             RECOVERED  ERRORu  z Overrun or other error that might be resolved by repeating the command                                                     ABORTED commandy  E Attempt a WRITE, READ, READ REVERSE, VERIFY, or RECOVER BUFFERED DATA  commanddz with the fixed bit set to zero and variable block mode is not supported                                                    ILLEGAL REQUESTn  E Attempt a WRITE, READ, READ REVERSE, VERIFY, or RECOVER BUFFERED DATAdB command with a fixed bit of zero and requested block length is not# supported           ILLEGAL REQUESTr  E Attempt a WRITE, READ, READ REVERSE, VERIFY, or RECOVER BUFFERED DATArz command with a fixed bit of one and MODE SENSE block length set to zero                                                    ILLEGAL REQUEST   G Attempt to execute an erase or write-type operation on write protected pe medium                                                                                   DATA PROTECTn  m Deferred write error                                                                                   MEDIUMd ERRORhd                                                                                      VOLUME OVERFLOW  D In the case of an unrecovered read or write error, if the read-writeA error recovery page (10.3.3.4) is implemented, the current valuese@ specify the target error recovery criteria.  If this page is not3 implemented, the error recovery is vendor-specific.m  F In the case of an unrecovered read error, if the fixed bit is one, theG valid bit shall be set to one and the information field shall be set to D the requested transfer length minus the actual number of blocks readE (not including the unrecovered block).  If the fixed bit is zero, thecG valid bit shall be set to one and the information field shall be set towF the requested transfer length.  Upon termination, the logical position% shall be after the unrecovered block.   @ In the case of an unrecovered write error, if unbuffered mode isG selected and the fixed bit is set to one, the valid bit shall be set toeD one and the information field shall be set to the requested transferE length minus the actual number of blocks written.  If unbuffered moderC is selected and the fixed bit is set to zero, the information fieldw. shall be set to the requested transfer length.  G In the case of an unrecovered write error or a deferred write error, ifoG buffered mode is selected and the fixed bit is one, the valid bit shalllA be set to one and the information field shall be set to the totaldD number of blocks, filemarks, and setmarks not written (the number ofD blocks not transferred from the initiator plus the number of blocks,G filemarks, and setmarks remaining in the target's buffer).  If bufferedeG mode is selected and the fixed bit is zero, the information field shall @ be set to the total number of bytes, filemarks, and setmarks notD written (the number of bytes not transferred from the initiator plusF the number of bytes, filemarks, and setmarks remaining in the target'sF buffer).  In both cases, the value in the information field may exceed the transfer length.  G In the case of an unrecovered write error or a deferred write error, iftF buffered mode 1h is selected, the error shall be reported to the firstD initiator issuing a command (other than INQUIRY or REQUEST SENSE) orF the first initiator responding to asynchronous event notification.  If@ buffered mode 2h is selected, the error shall be reported to the, initiator with unwritten data in the buffer.  7 10.2 Command descriptions for sequential-access devicesr  E The commands for sequential-access devices shall be as shown in tablei 174.  @               Table 174 - Commands for sequential-access devicesH +=====================================-============-======-============+H |  Command name                       | Operation  | Type |  Subclause |H |                                     |   code     |      |            |H |-------------------------------------+------------+------+------------|H | CHANGE DEFINITION                   |    40h     |   O  |   8.2.1    |H | COMPARE                             |    39h     |   O  |   8.2.2    |H | COPY                                |    18h     |   O  |   8.2.3    |H | COPY AND VERIFY                     |    3Ah     |   O  |   8.2.4    |H | ERASE                               |    19h     |   M  |  10.2.1    |H | INQUIRY                             |    12h     |   M  |   8.2.5    |H | LOAD UNLOAD                         |    1Bh     |   O  |  10.2.2    |H | LOCATE                              |    2Bh     |   O  |  10.2.3    |H | LOG SELECT                          |    4Ch     |   O  |   8.2.6    |H | LOG SENSE                           |    4Dh     |   O  |   8.2.7    |H | MODE SELECT(6)                      |    15h     |   M  |   8.2.8    |H | MODE SELECT(10)                     |    55h     |   O  |   8.2.9    |H | MODE SENSE(6)                       |    1Ah     |   M  |   8.2.10   |H | MODE SENSE(10)                      |    5Ah     |   O  |   8.2.11   |H | PREVENT ALLOW MEDIUM REMOVAL        |    1Eh     |   O  |   9.2.4    |H | READ                                |    08h     |   M  |  10.2.4    |H | READ BLOCK LIMITS                   |    05h     |   M  |  10.2.5    |H | READ BUFFER                         |    3Ch     |   O  |   8.2.12   |H | READ POSITION                       |    34h     |   O  |  10.2.6    |H | READ REVERSE                        |    0Fh     |   O  |  10.2.7    |H | RECEIVE DIAGNOSTIC RESULTS          |    1Ch     |   O  |   8.2.13   |H | RECOVER BUFFERED DATA               |    14h     |   O  |  10.2.8    |H | RELEASE UNIT                        |    17h     |   M  |  10.2.9    |H | REQUEST SENSE                       |    03h     |   M  |   8.2.14   |H | RESERVE UNIT                        |    16h     |   M  |  10.2.10   |H | REWIND                              |    01h     |   M  |  10.2.11   |H | SEND DIAGNOSTIC                     |    1Dh     |   M  |   8.2.15   |H | SPACE                               |    11h     |   M  |  10.2.12   |H | TEST UNIT READY                     |    00h     |   M  |   8.2.16   |H | VERIFY                              |    13h     |   O  |  10.2.13   |H | WRITE                               |    0Ah     |   M  |  10.2.14   |H | WRITE BUFFER                        |    3Bh     |   O  |   8.2.17   |H | WRITE FILEMARKS                     |    10h     |   M  |  10.2.15   |H |----------------------------------------------------------------------|H |Key:  M = command implementation is mandatory.                        |H |      O = command implementation is optional.                         |H +======================================================================+    D The following command codes are vendor-specific: 02h, 06h, 07h, 09h,D 0Ch, and 0Eh.  All other command codes for sequential-access devices( are reserved for future standardization.   10.2.1 ERASE command  E The ERASE command (see table 175) causes part or all of the medium to D be erased beginning at the current position on the logical unit.  AsF used here, erased means either the medium shall be erased or a patternC shall be written on the medium that appears as a gap to the target.e  3                           Table 175 - ERASE commandeO +=====-========-========-========-========-========-========-========-========+nO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |,O |Byte |        |        |        |        |        |        |        |        |eO |=====+=======================================================================|tO | 0   |                           Operation code (19h)                        |AO |-----+-----------------------------------------------------------------------|iO | 1   |   Logical unit number    |         Reserved          | Immed |  Long  |nO |-----+-----------------------------------------------------------------------|nO | 2   |                           Reserved                                    |aO |-----+-----------------------------------------------------------------------| O | 3   |                           Reserved                                    |iO |-----+-----------------------------------------------------------------------|iO | 4   |                           Reserved                                    |nO |-----+-----------------------------------------------------------------------|cO | 5   |                           Control                                     |cO +=============================================================================+o    D An immediate (Immed) bit of zero indicates that the target shall notG return status until the erase operation has completed.  An Immed bit ofh@ one indicates that the target shall return status as soon as theE command has been validated. If CHECK CONDITION status is returned forhD an ERASE command with an Immed bit of one, the erase operation shall not be performed.   D A long bit of one indicates that all remaining medium in the currentE partition shall be erased beginning at the current logical position. TF If the Immed bit is one, the target shall return status as soon as allE buffered commands have completed execution and the command descriptor D block of the ERASE command has been validated.  The logical positionE following an ERASE command with a long bit of one is not specified by  this standard.  M    NOTE 138 Some targets may reject an ERASE command with the long bit set to <    one if the logical unit is not at beginning-of-partition.  G A long bit of zero specifies an erase gap defined by the gap size fielddE in the device configuration page (10.3.3.1).  If the gap size is zero C or the field is not supported, a device defined erase gap operation E shall be performed.  If the Immed bit is one, the target shall returnEC status as soon as the command descriptor block has been validated.  G Erase gaps may be used in initiator controlled error recovery or update  in place applications.    E If the logical unit encounters early-warning during an ERASE command,eG and any buffered data, filemarks, or setmarks remain to be written, the D target action shall be as defined for the early-warning condition of@ the WRITE command (10.2.14).  If the long bit is zero, the eraseF operation shall terminate with CHECK CONDITION status and return senseC data as defined for the WRITE command.  Any buffered erases are nott* reported as part of the information field.   10.2.2 LOAD UNLOAD command  G The LOAD UNLOAD command (see table 176) requests that the target enableRE or disable the logical unit for further operations.  This command mayhF also be used to request a retension function.  Prior to performing theC load or unload operation, the target shall ensure that all bufferedoB data, filemarks, and setmarks have been transferred to the medium.  6                        Table 176 - LOAD UNLOAD commandO +=====-========-========-========-========-========-========-========-========+tO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================|MO | 0   |                           Operation code (1Bh)                        | O |-----+-----------------------------------------------------------------------| O | 1   |   Logical unit number    |              Reserved             | Immed  |eO |-----+-----------------------------------------------------------------------|lO | 2   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|nO | 3   |                           Reserved                                    |nO |-----+-----------------------------------------------------------------------| O | 4   |                           Reserved         |   EOT  |  Reten |  Load  |tO |-----+-----------------------------------------------------------------------| O | 5   |                           Control                                     | O +=============================================================================+     D An immediate (Immed) bit of zero indicates that the target shall notC return status until the load or unload operation has completed.  AnrF Immed bit of one indicates that the target shall return status as soonA as all buffered commands have completed execution and the commandsC descriptor block of the LOAD UNLOAD command has been validated.  IfrD CHECK CONDITION status is returned for a LOAD UNLOAD command with anF Immed bit of one, the load or unload operation shall not be performed.  L    NOTE 139 For compatibility with devices implemented prior to this versionG    of the standard, a WRITE FILEMARKS command with an Immed bit of zeroaJ    should be used to ensure that all buffered data, filemarks, or setmarksM    have been transferred to the medium prior to issuing a LOAD UNLOAD commando    with an Immed bit of one.  B An end-of-tape (EOT) bit of one indicates that an unload operationE (load bit set to zero) shall position the medium at end-of-medium foraE removal from the device.  An EOT bit of zero indicates that an unload F operation shall position the medium at beginning-of-medium for removal from the device.  A An EOT bit of one and a load bit of one shall cause the target torG return CHECK CONDITION status and the sense key shall be set to ILLEGALE REQUEST in the sense data.  G A retension (ReTen) bit of one indicates that the medium on the logicaliC unit shall have the correct tension applied.  Implementation of thet& retension function is device specific.  F If the load bit is set to one, the medium in the logical unit shall beF loaded and positioned to the beginning-of-partition zero.  If the loadC bit is zero, the medium in the logical unit shall be positioned for=E removal at the extreme position along the medium specified by the EOT A bit.  Following successful completion of an unload operation, the D target shall return CHECK CONDITION status with the sense key set toF NOT READY for all subsequent medium-access commands until a new volume9 is mounted or a load operation is successfully completed.   G When operating in buffered mode 1h or 2h (see 10.3.3), the target shall|D discard any unwritten buffered data after the LOAD UNLOAD command isE validated if the previous command was terminated with CHECK CONDITION.B status and the device is unable to continue successfully writing.    10.2.3 LOCATE command   @ LOCATE command (see table 177) causes the target to position theF logical unit to the specified block address in a specified partition. C Upon completion, the logical position shall be before the specified E location.  Prior to performing the locate operation, the target shall|@ ensure that all buffered data, filemarks, and setmarks have been transferred to the medium.  4                           Table 177 - LOCATE commandO +=====-========-========-========-========-========-========-========-========+SO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |)O |Byte |        |        |        |        |        |        |        |        |RO |=====+=======================================================================| O | 0   |                           Operation code (2Bh)                        | O |-----+-----------------------------------------------------------------------| O | 1   |    Logical unit number   |      Reserved   |   BT   |   CP   | Immed  |OO |-----+-----------------------------------------------------------------------|.O | 2   |                           Reserved                                    ||O |-----+-----------------------------------------------------------------------|EO | 3   | (MSB)                                                                 |SO |-----+---                                                                 ---| O | 4   |                                                                       | O |-----+---                        Block address                            ---| O | 5   |                                                                       |hO |-----+---                                                                 ---| O | 6   |                                                                 (LSB) |1O |-----+-----------------------------------------------------------------------| O | 7   |                           Reserved                                    |RO |-----+-----------------------------------------------------------------------|-O | 8   |                           Partition                                   |iO |-----+-----------------------------------------------------------------------|tO | 9   |                           Control                                     |=O +=============================================================================+s    E A block address type (BT) bit of one indicates the value in the blockqD address field shall be interpreted as a device-specific value.  A BTC bit of zero indicates the value in the block address field shall ber- interpreted as an SCSI logical block address.t  A A change partition (CP) bit of one indicates that a change to the ? partition specified in the partition field is to occur prior tooD positioning to the block specified in the block address field.  A CP? bit of zero indicates no partition change is to be made and the=! partition field is to be ignored.=  D An immediate (Immed) bit of zero indicates that the target shall notE return status until the locate operation has completed.  An Immed bit C of one indicates that the target shall return status as soon as all=E buffered commands have completed execution and the command descriptor C block of the LOCATE command has been validated.  If CHECK CONDITION-E status is returned for a LOCATE command with an Immed bit of one, the ( locate operation shall not be performed.  C The block address field (see 10.1.6) specifies the block address to-G which the target shall position the medium based on the current setting  of the BT bit.  E The partition field specifies which partition to select if the CP bit-E is one.  Refer to the sequential-access device model (see 10.1.3) and E the medium partition pages (see 10.3.3.2 and 10.3.3.3) for additional- information about partitioning.-   10.2.4 READ command-  F The READ command (see table 178) requests that the target transfer oneG or more block(s) of data to the initiator beginning with the next block- on the logical unit.  3                            Table 178 - READ command O +=====-========-========-========-========-========-========-========-========+=O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |aO |Byte |        |        |        |        |        |        |        |        |nO |=====+=======================================================================| O | 0   |                           Operation code (08h)                        |cO |-----+-----------------------------------------------------------------------| O | 1   |   Logical unit number     |        Reserved         |  SILI  | Fixed  |hO |-----+-----------------------------------------------------------------------|nO | 2   | (MSB)                                                                 |dO |-----+---                                                                 ---|aO | 3   |                           Transfer length                             |nO |-----+---                                                                 ---|cO | 4   |                                                                 (LSB) |oO |-----+-----------------------------------------------------------------------| O | 5   |                           Control                                     |rO +=============================================================================+o    F The fixed bit specifies whether fixed-length or variable-length blocksC are to be transferred.  Refer to the READ BLOCK LIMITS command (see G 10.2.5) for additional information about fixed and variable block mode.i  D If the fixed bit is one, the transfer length specifies the number ofE fixed-length blocks to be transferred, using the current block lengthiE reported in the mode parameters block descriptor (see 8.3.3).  If thed@ fixed bit is zero, a variable-length block is requested with theD transfer length specifying the maximum number of bytes allocated for the returned data.  D A successful READ command with a fixed bit of one shall transfer theD requested transfer length times the current block length in bytes toB the initiator.  A successful READ command with a fixed bit of zeroH shall transfer the requested transfer length in bytes to the initiator. C Upon completion, the logical position shall be after the last blocke$ transferred (end-of-partition side).  D If the suppress incorrect length indicator (SILI) bit is one and the$ fixed bit is zero, the target shall:I    a)     report CHECK CONDITION status for an incorrect length condition=J           only if the overlength condition exists (see 10.4) and the blockH           length field in the mode parameter block descriptor is nonzero           (see 8.3.3).D    b)     not report CHECK CONDITION status if the only error is theG           underlength condition (see 10.4), or if the only error is the E           overlength condition and the block length field of the mode-.           parameters block descriptor is zero.  B    NOTE 140 Since the residue information normally provided in theM    information field of the sense data may not be available when the SILI bit-J    is set, other methods for determining the actual block length should be>    used (e.g. including length information in the data block).  A If the SILI bit is one and the fixed bit is one, the target shall C terminate the command with CHECK CONDITION status and the sense key @ shall be set to ILLEGAL REQUEST with an additional sense code of INVALID FIELD IN CDB.   D If the SILI bit is zero and an incorrect length block is read, CHECKF CONDITION status shall be returned and the ILI and valid bits shall beE set to one in the sense data.  Upon termination, the logical position F shall be after the incorrect length block (end-of-partition side).  If? the fixed bit is one, the information field shall be set to thebE requested transfer length minus the actual number of blocks read (not E including the incorrect length block).  If the fixed bit is zero, thesE information field shall be set to the requested transfer length minushE the actual block length.  Targets that do not support negative valuesUD shall set the information field to zero if the overlength  condition exists (see 10.4).  M    NOTE 141 In the above case with the fixed bit of one, only the position ofeM    the incorrect-length logical block can be determined from the sense data. sM    The actual length of the incorrect block is not reported.  Other means mayrL    be used to determine its actual length (e.g. read it again with the fixed    bit set to zero).  G A transfer length of zero indicates that no data shall be transferred. d? This condition shall not be considered an error and the logical  position shall not be changed.  F If the logical unit encounters a filemark during a READ command, CHECKB CONDITION status shall be returned and the filemark and valid bitsE shall be set to one in the sense data.  The sense key shall be set tovC NO SENSE or RECOVERED ERROR, as appropriate.  Upon termination, thetF logical position shall be after the filemark (end-of-partition side). B If the fixed bit is one, the information field shall be set to theE requested transfer length minus the actual number of blocks read (not C including the filemark).  If the fixed bit is zero, the informatione5 field shall be set to the requested transfer length.    F If the logical unit encounters a setmark during a READ command and theG RSmk bit is set to one in the device configuration page (see 10.3.3.1),hC CHECK CONDITION status shall be returned and the filemark and validiG bits shall be set to one in the sense data.  The sense key shall be setoB to NO SENSE or RECOVERED ERROR, as appropriate, and the additionalC sense code shall be set to SETMARK DETECTED.  Upon termination, theaE logical position shall be after the setmark (end-of-partition side). cB If the fixed bit is one, the information field shall be set to theE requested transfer length minus the actual number of blocks read (notUB including the setmark).  If the fixed bit is zero, the informationF field shall be set to the requested transfer length.  The target shallD not return CHECK CONDITION when a setmark is encountered if the RSmk6 bit is set to zero or if this option is not supported.  F If the logical unit encounters early-warning during a READ command and? the REW bit is set to one in the device configuration page (seePF 10.3.3.1), CHECK CONDITION status shall be returned upon completion ofG the current block.  The sense key shall be set to NO SENSE or RECOVEREDmE ERROR, as appropriate.  The EOM and valid bits shall be set to one in=F the sense data.  Upon termination, the logical position shall be afterE the last block transferred (end-of-partition side).  If the fixed bit|D is one, the information field shall be set to the requested transferC length minus the actual number of blocks read.  If the fixed bit is=B zero, the information field shall be set to the requested transferB length minus the actual block length.  The target shall not returnG CHECK CONDITION status when early-warning is encountered if the REW bit . is zero or if the REW option is not supported.  L    NOTE 142 A REW bit of one is not recommended for most system applications7    since read data may be present after early-warning.    G If the logical unit encounters end-of-data during a READ command, CHECK-G CONDITION status shall be returned, the sense key shall be set to BLANK C CHECK, and the valid bit shall be set to one in the sense data.  If-G end-of-data is encountered at or after early-warning, the EOM bit shall C also be set to one. Upon termination, the logical position shall be F after the last recorded logical block (end-of-partition side).  If theE fixed bit is one, the information field shall be set to the requested E transfer length minus the actual number of blocks read.  If the fixed @ bit is zero, the information field shall be set to the requested transfer length.  F If the logical unit encounters end-of-partition during a READ command,G CHECK CONDITION status shall be returned, the sense key shall be set to C MEDIUM ERROR, and the EOM and valid bits shall be set to one in the-? sense data. The medium position following this condition is not-E defined.  If the fixed bit is one, the information field shall be set B to the requested transfer length minus the actual number of blocksE read. If the fixed bit is zero, the information field shall be set to  the requested transfer length.    10.2.5 READ BLOCK LIMITS command  G The READ BLOCK LIMITS command (see table 179) requests that the logicaleB unit's block length limits capability be returned.  The READ BLOCK1 LIMITS data shown in table 180 shall be returned.T  9                     Table 179 - READ BLOCK LIMITS commandsO +=====-========-========-========-========-========-========-========-========+PO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |nO |Byte |        |        |        |        |        |        |        |        |rO |=====+=======================================================================|=O | 0   |                           Operation code (05h)                        |sO |-----+-----------------------------------------------------------------------|dO | 1   |   Logical unit number    |                  Reserved                  | O |-----+-----------------------------------------------------------------------|cO | 2   |                           Reserved                                    |nO |-----+-----------------------------------------------------------------------|tO | 3   |                           Reserved                                    |sO |-----+-----------------------------------------------------------------------|fO | 4   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------| O | 5   |                           Control                                     |bO +=============================================================================+q    8                       Table 180 - READ BLOCK LIMITS dataO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |=O |Byte |        |        |        |        |        |        |        |        |4O |=====+=======================================================================| O | 0   |                           Reserved                                    |=O |-----+-----------------------------------------------------------------------|rO | 1   | (MSB)                                                                 |-O |-----+---                                                                 ---| O | 2   |                           Maximum block length limit                  |-O |-----+---                                                                 ---| O | 3   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|nO | 4   | (MSB)                                                                 | O |-----+---                        Minimum block length limit               ---| O | 5   |                                                                 (LSB) |-O +=============================================================================+t    G If the maximum block length limit value equals the minimum block length=B limit value, the logical unit supports the transfer of data in theG fixed-block mode only, with the block length equal to the given value. rD In this case the fixed bit shall be set to one in the WRITE and READ	 commands.a  C If the maximum block length limit value is not equal to the minimumtC block length limit value, the logical unit supports the transfer of B data in either fixed-block or variable-block modes, with the block@ length constrained between the given limits in either mode.  TheA transfer mode is controlled by the fixed bit in the WRITE or READpF commands. If the maximum block limit is zero a maximum block length is not specified.   10.2.6 READ POSITION command  F The READ POSITION command (see table 181) reports the current positionA of the logical unit and any data blocks in the buffer.  No mediuma2 movement shall occur as a result of the command.    7                       Table 181 - READ POSITION commandtO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |iO |Byte |        |        |        |        |        |        |        |        |nO |=====+=======================================================================|sO | 0   |                           Operation code (34h)                        |pO |-----+-----------------------------------------------------------------------|uO | 1   |   Logical unit number    |             Reserved              |   BT   | O |-----+-----------------------------------------------------------------------|tO | 2   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|aO | 3   |                           Reserved                                    |iO |-----+-----------------------------------------------------------------------|iO | 4   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|lO | 5   |                           Reserved                                    |BO |-----+-----------------------------------------------------------------------|TO | 6   |                           Reserved                                    |hO |-----+-----------------------------------------------------------------------|eO | 7   |                           Reserved                                    |oO |-----+-----------------------------------------------------------------------|fO | 8   |                           Reserved                                    |eO |-----+-----------------------------------------------------------------------| O | 9   |                           Control                                     | O +=============================================================================+     F A block address type (BT) bit of one requests the target to return itsA current first block location and last block location as a device-eC specific value.  A BT bit of zero requests the target to return thepC first block location and the last block location as an SCSI logicale* block address (relative to a partition).    D If the logical unit is not capable of reporting block locations, theC BPU bit shall be set to one in the returned data.  Support for thishD option of the READ POSITION command is indicated by a BIS bit set to4 one in the device configuration page (see 10.3.3.1).  < The READ POSITION data shown in table 182 shall be returned.  9                     Table 182 - READ POSITION data formatsO +=====-========-========-========-========-========-========-========-========+iO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |bO |Byte |        |        |        |        |        |        |        |        |iO |=====+========+========+==========================+========+=================|dO | 0   |  BOP   |   EOP  |        Reserved          |  BPU   |     Reserved    |tO |-----+-----------------------------------------------------------------------|SO | 1   |                          Partition number                             |DO |-----+-----------------------------------------------------------------------|oO | 2   |                          Reserved                                     |RO |-----+-----------------------------------------------------------------------|.O | 3   |                          Reserved                                     |tO |-----+-----------------------------------------------------------------------|eO | 4   | (MSB)                                                                 |nO |- - -+---                       First block location                      ---| O | 7   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------| O | 8   | (MSB)                                                                 |aO |- - -+---                       Last block location                       ---|CO | 11  |                                                                 (LSB) |hO |-----+-----------------------------------------------------------------------|OO | 12  |                          Reserved                                     |lO |-----+-----------------------------------------------------------------------|)O | 13  | (MSB)                                                                 | O |- - -+---                       Number of blocks in buffer                ---|eO | 15  |                                                                 (LSB) |eO |-----+-----------------------------------------------------------------------|aO | 16  | (MSB)                                                                 |uO |- - -+---                       Number of bytes in buffer                 ---|cO | 19  |                                                                 (LSB) |lO +=============================================================================+l    D A beginning of partition (BOP) bit of one indicates that the logicalF unit is at the beginning-of-partition in the current partition.  A BOPE bit of zero indicates that the current logical position is not at thep beginning-of-partition.     G An end of partition (EOP) bit of one indicates that the logical unit is D positioned between early-warning and end-of-partition in the currentA partition.  An EOP bit of zero indicates that the current logical ; position is not between early-warning and end-of-partition.l  I    NOTE 143 The BOP and EOP indications are not necessarily a result of ae2    physical tape marker (e.g. reflective marker).   F A block position unknown (BPU) bit of one indicates that the first andG last block locations are not known or cannot be obtained.  A BPU bit of D zero indicates that the first and last block location fields contain valid position information.n  G The partition number field reports the partition number for the currentbF logical position.  If the logical unit only supports one partition for, the medium, this field shall be set to zero.  E The first block location field indicates the block address associatedtF with the current logical position.  The value shall indicate the blockF address of the next data block to be transferred between the initiator4 and the target if a READ or WRITE command is issued.  F The last block location field indicates the block address (see 10.1.6)G associated with the next block to be transferred from the buffer to the D medium.  The value shall indicate the block address of the next dataB block to be transferred between the buffer and the medium.  If theD buffer does not contain a whole block of data or is empty, the value@ reported for the last block location shall be equal to the value& reported for the first block location.  I    NOTE 144 The information provided by the first and last block locationmL    fields can be used in conjunction with the LOCATE command to position theK    medium at the appropriate logical block on another device in the case of ,    unrecoverable errors on the first device.  A The number of blocks in buffer field indicates the number of data-G blocks in the target's buffer that have not been written to the medium.   F The number of bytes in buffer field indicates the total number of dataF bytes in the target's buffer that have not been written to the medium.   10.2.7 READ REVERSE command   A The READ REVERSE command (see table 183) requests that the target-G transfer one or more block(s) of data to the initiator beginning at thet% current position on the logical unit.   7                        Table 183 - READ REVERSE command=O +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |=O |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================| O | 0   |                           Operation code (0Fh)                        |=O |-----+-----------------------------------------------------------------------| O | 1   |   Logical unit number    |         Reserved         |  SILI  | Fixed  |-O |-----+-----------------------------------------------------------------------| O | 2   | (MSB)                                                                 |-O |-----+---                                                                 ---| O | 3   |                           Transfer length                             |-O |-----+---                                                                 ---|BO | 4   |                                                                 (LSB) |-O |-----+-----------------------------------------------------------------------| O | 5   |                           Control                                     |-O +=============================================================================+B    C The execution of this command is similar to the READ command except=F that medium motion is in the reverse direction.  All block(s), and theG byte(s) within the block(s), are transferred in the reverse order.  ThefE order of bits within each byte shall not be changed.  Upon completion C of a READ REVERSE command, the logical position shall be before the 5 last block transferred (beginning-of-partition side).t  E Refer to the READ command (see 10.2.4) for a description of the fixed F bit, the SILI bit, the transfer length field, and any associated error conditions.m  B Filemarks, setmarks, incorrect length blocks, and unrecovered readD errors are handled the same as in the READ command, except that uponG termination the logical position shall be before the filemark, setmark,oD incorrect length block, or unrecovered block (beginning-of-partition side).  C If the logical unit encounters beginning-of-partition during a READlE REVERSE command, CHECK CONDITION status shall be returned and the EOMcD and valid bits shall be set to one in the sense data.  The sense keyD shall be set to NO SENSE or RECOVERED ERROR, as appropriate.  If theE fixed bit is one, the information field shall be set to the requested F transfer length minus the actual number of blocks transferred.  If theF fixed bit is zero, the information field shall be set to the requested transfer length.  $ 10.2.8 RECOVER BUFFERED DATA command  D The RECOVER BUFFERED DATA command (see table 184) is used to recoverF data that has been transferred to the target's buffer but has not beenC successfully written to the medium.  It is normally used to recover G from error or exception conditions that make it impossible to write the-G buffered data to the medium. One or more RECOVER BUFFERED DATA commands 7 may be required to recover all unwritten buffered data.-  ;                   Table 184 - RECOVER BUFFERED DATA command-O +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |-O |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================|-O | 0   |                           Operation code (14h)                        | O |-----+-----------------------------------------------------------------------|-O | 1   |   Logical unit number    |         Reserved         |  SILI  | Fixed  | O |-----+-----------------------------------------------------------------------|-O | 2   | (MSB)                                                                 | O |-----+---                                                                 ---|-O | 3   |                           Transfer length                             | O |-----+---                                                                 ---|-O | 4   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|=O | 5   |                           Control                                     |eO +=============================================================================+c    C The execution of this command is similar to the READ command exceptlD that the data is transferred from the target's buffer instead of theF medium.  The order in which block(s) are transferred is defined by theD RBO bit in the device configuration page (see 10.3.3.1).  If the RBOG bit is not implemented, block(s) are transferred in the same order theys* would have been transferred to the medium.  E Refer to the READ command (see 10.2.4) for a description of the fixediF bit, the SILI bit, the transfer length field, and any associated error conditions.f  D If the fixed bit is zero, no more than the requested transfer lengthA shall be transferred to the initiator.  If the requested transfer C length is smaller than the actual length of the logical block to be E recovered, only the requested transfer length shall be transferred to=B the initiator and the remaining data for the current logical block shall be discarded.s  I    NOTE 145 During recovery operations involving unknown block sizes, the-K    initiator should select the maximum block length supported by the target M    to ensure that all buffered data will be transferred and set the fixed bit-    to zero.-  D If a buffered filemark is encountered during a RECOVER BUFFERED DATAF command, CHECK CONDITION status shall be returned, the sense key shallG be set to NO SENSE, and the filemark and valid bits shall be set to one C in the sense data.  Upon termination, the logical position shall be C after the filemark.  If the fixed bit is one, the information field-E shall be set to the requested transfer length minus the actual number 5 of blocks transferred (not including the filemark).  F  C If the fixed bit is zero, the information field shall be set to the  requested transfer length.  C If a buffered setmark is encountered during a RECOVER BUFFERED DATA-G command and the RSmk bit is set to one in the device configuration page @ (see 10.3.3.1), CHECK CONDITION status shall be returned and theC filemark and valid bits shall be set to one in the sense data.  The F sense key shall be set to NO SENSE and the additional sense code shallC be set to SETMARK DETECTED.  Upon termination, the logical position-E shall be after the setmark.  If the fixed bit is one, the information D field shall be set to the requested transfer length minus the actualG number of blocks transferred (not including the setmark).  If the fixed @ bit is zero, the information field shall be set to the requestedC transfer length. The target shall not return CHECK CONDITION when a G setmark is encountered if the RSmk bit is zero or if this option is not 
 supported.  E If an attempt is made to recover more logical blocks of data than are6A contained in the target's buffer, CHECK CONDITION status shall be G returned, the sense key shall be set to NO SENSE, and the EOM and valid E bits shall be set to one in the sense data.  If the fixed bit is one, C the information field shall be set to the requested transfer length=C minus the actual number of blocks transferred.  If the fixed bit is(B zero, the information field shall be set to the requested transfer length.t   10.2.9 RELEASE UNIT commandA  F The RELEASE UNIT command (see table 185) is used to release previouslyB reserved logical units for the requesting initiator, or if it is a6 third-party release, to another specified SCSI device.  7                        Table 185 - RELEASE UNIT commandtO +=====-========-========-========-========-========-========-========-========+wO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |nO |Byte |        |        |        |        |        |        |        |        |rO |=====+=======================================================================| O | 0   |                           Operation code (17h)                        |dO |-----+-----------------------------------------------------------------------|rO | 1   | Logical unit number      | 3rdPty | Third party device ID    |Reserved|nO |-----+-----------------------------------------------------------------------|eO | 2   |                           Reserved                                    |sO |-----+-----------------------------------------------------------------------|lO | 3   |                           Reserved                                    |eO |-----+-----------------------------------------------------------------------|kO | 4   |                           Reserved                                    |tO |-----+-----------------------------------------------------------------------|tO | 5   |                           Control                                     |aO +=============================================================================+,    F The RESERVE UNIT and RELEASE UNIT commands provide the basic mechanism8 for contention resolution in multiple-initiator systems.  C If a valid reservation exists for the I_T_L nexus, the target shall / release the reservation and return GOOD status.d  E A reservation may only be released by the initiator that made it.  Ite? is not an error to attempt to release a reservation that is not.C currently valid or is held by another initiator.  In this case, the-G target shall return GOOD status without altering any other reservation.    10.2.9.1 Third-party release    F Third-party release allows an initiator to release a logical unit that< was previously reserved using a third-party reservation (see 10.2.10.1).h  F If the third party (3rdPty) bit is zero, then a third-party release isD not requested.  If the 3rdPty bit is one, and if the reservation was= made using a third-party reservation by the initiator that isbC requesting the release for the same SCSI device as specified in the=E third-party device ID, then the target shall release the reservation.   > If the 3rdPty bit is one, the target shall not modify the modeD parameters for commands received from the third-party device even ifC the target implements the transfer of mode parameters with a third-= party RESERVE UNIT command.   K    NOTE 146 When a target implements independent storage of mode parameters-L    for each initiator, a third-party RESERVE UNIT command effects a transferH    of the current mode parameters.  Those set up by the initiator of theK    RESERVE UNIT are to be set as the mode parameters used for commands from K    the third-party device (usually a copy master device).  A unit attention M    condition notifies the third-party device of the changed mode parameters. -G    A successful third-party RELEASE UNIT command leaves the transferred K    parameters intact.  The third-party device can issue MODE SENSE and MODE >    SELECT commands to query and modify the mode parameters.      10.2.10 RESERVE UNIT command  C The RESERVE UNIT command (see table 186) is used to reserve logical-F units for the exclusive use of the requesting initiator, or if it is a: third-party reservation, to another specified SCSI device.  7                        Table 186 - RESERVE UNIT commandtO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |eO |Byte |        |        |        |        |        |        |        |        |tO |=====+=======================================================================|hO | 0   |                           Operation code (16h)                        |eO |-----+-----------------------------------------------------------------------| O | 1   | Logical unit number      | 3rdPty | Third party device ID    |Reserved|kO |-----+-----------------------------------------------------------------------|eO | 2   |                           Reserved                                    |sO |-----+-----------------------------------------------------------------------|oO | 3   |                           Reserved                                    |-O |-----+-----------------------------------------------------------------------|eO | 4   |                           Reserved                                    |kO |-----+-----------------------------------------------------------------------|iO | 5   |                           Control                                     |iO +=============================================================================+r  F The RESERVE UNIT and RELEASE UNIT commands provide the basic mechanism8 for contention resolution in multiple-initiator systems.  F This command requests that the entire logical unit be reserved for theE exclusive use of the initiator until the reservation is superseded byiC another valid RESERVE UNIT command from the initiator that made theoE reservation or until released by a RELEASE UNIT command from the sameOG initiator that made the reservation, by a BUS DEVICE RESET message fromlF any initiator, by a hard reset condition, or by a power on cycle.  TheC reservation shall not be granted if the logical unit is reserved by=G another initiator.  It shall be permissible for an initiator to reserve < a logical unit that is currently reserved by that initiator.  G If the logical unit is reserved for another initiator, the target shall=% return RESERVATION CONFLICT status.  =  D If, after honouring the reservation, any other initiator attempts toG perform any command on the reserved logical unit other than an INQUIRY,-B REQUEST SENSE, PREVENT ALLOW MEDIUM REMOVAL (with a prevent bit ofD zero), or a RELEASE UNIT command, the command shall be rejected with RESERVATION CONFLICT status. -  ! 10.2.10.1 Third-party reservation   E Third-party reservation allows an initiator to reserve a logical unit ? for another SCSI device.  This is intended for use in multiple- . initiator systems that use the COPY command.    E If the third-party (3rdPty) bit is zero, a third-party reservation is E not requested.  If the 3rdPty bit is one the target shall reserve the G logical unit for the SCSI device specified in the third-party device ID G field. The target shall preserve the reservation until it is superseded-F by another valid RESERVE UNIT command from the initiator that made theC reservation or until it is released by the same initiator, by a BUS=D DEVICE RESET message from any initiator, or a hard reset condition. F The target shall ignore any attempt to release the reservation made by any other initiator.  @ If independent sets of parameters are implemented, a third partyG reservation shall cause the target to transfer the set of parameters in F effect for the initiator of the RESERVE command to the parameters usedA for commands from the third-party device.  Any subsequent commandoB issued by the third-party device is executed according to the modeE parameters in effect for the initiator that sent the RESERVE command.d  @ If independent sets of parameters are implemented, a third partyG reservation shall cause the target to transfer the set of parameters inaF effect for the initiator of the RESERVE command to the parameters usedA for commands from the third party device.  Any subsequent commandeB issued by the third-party device is executed according to the modeE parameters in effect for the initiator that sent the RESERVE command.s  H    NOTE 147 This transfer of the mode parameters is applicable to targetC    devices which store mode information independently for differentdM    initiators.  This mechanism allows an initiator to set the mode parameters K    of a target for the use of a copy master (i.e. the third-party device). IK    The third-party copy master may subsequently issue a MODE SELECT command !    to modify the mode parameters.t  " 10.2.10.2 Superseding reservations  F An initiator that currently has a logical unit reserved may modify theG current reservation by issuing another RESERVE UNIT command to the samefD logical unit.  The superseding reservation shall release the currentC reservation if the superseding reservation request is granted.  Thel< current reservation shall not be modified if the supersedingF reservation request cannot be granted.  If the superseding reservationB cannot be granted because of conflicts with a previous reservationB (other than the current reservation), then the target shall return RESERVATION CONFLICT status.    L    NOTE 148 Superseding reservations allow the third-party SCSI device ID toM    be changed during a reservation using the third-party reservation option. cJ    This capability is necessary for certain situations when using COMPARE,&    COPY, and COPY AND VERIFY commands.   10.2.11 REWIND command  D The REWIND command (see table 187) causes the target to position theE logical unit to the beginning-of-partition in the current partition. rF Prior to performing the rewind operation, the target shall ensure thatG all buffered data, filemarks, and setmarks have been transferred to thei medium.u  4                           Table 187 - REWIND commandO +=====-========-========-========-========-========-========-========-========+tO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |aO |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================|lO | 0   |                           Operation code (01h)                        | O |-----+-----------------------------------------------------------------------| O | 1   |   Logical unit number    |              Reserved             | Immed  |dO |-----+-----------------------------------------------------------------------|tO | 2   |                           Reserved                                    |IO |-----+-----------------------------------------------------------------------|-O | 3   |                           Reserved                                    ||O |-----+-----------------------------------------------------------------------||O | 4   |                           Reserved                                    |=O |-----+-----------------------------------------------------------------------| O | 5   |                           Control                                     |-O +=============================================================================+|    D An immediate (Immed) bit of zero indicates that the target shall notE return status until the rewind operation has completed.  An Immed bit C of one indicates that the target shall return status as soon as all-E buffered commands have completed execution and the command descriptor C block of the REWIND command has been validated.  If CHECK CONDITION-E status is returned for a REWIND command with an Immed bit of one, the ( rewind operation shall not be performed.  D    NOTE 149 For compatibility with devices implemented prior to thisM    standard, it is suggested that a WRITE FILEMARKS command with an Immed bittK    of zero be used to ensure that all buffered data, filemarks, or setmarks=K    have been transferred to the medium before issuing a REWIND command withA    an Immed bit of one.t  G When operating in buffered mode 1h or 2h (see 10.3.3), the target shall.? discard any unwritten buffered data after the REWIND command is E validated if the previous command was terminated with CHECK CONDITIONoB status and the device is unable to continue successfully writing.    10.2.12 SPACE commande  C The SPACE command (see table 188) provides a variety of positioningnF functions that are determined by the code and count.  Both forward and@ reverse positioning are provided, although some targets may only> support a subset of this command.  If an initiator requests an@ unsupported function, the command shall be terminated with CHECKC CONDITION status and the sense key shall be set to ILLEGAL REQUEST.   3                           Table 188 - SPACE commandiO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |iO |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================|mO | 0   |                           Operation  (11h)                            |nO |-----+-----------------------------------------------------------------------|4O | 1   |   Logical unit number    |     Reserved    |           Code           |nO |-----+-----------------------------------------------------------------------| O | 2   | (MSB)                                                                 | O |-----+---                                                                 ---|uO | 3   |                           Count                                       |aO |-----+---                                                                 ---| O | 4   |                                                                 (LSB) |cO |-----+-----------------------------------------------------------------------| O | 5   |                           Control                                     |aO +=============================================================================+n    ' The code field is defined in table 189.v  7                       Table 189 - Code field definition 6 +=============-========================-=============+6 |    Code     |  Description           |  Support    |6 |-------------+------------------------+-------------|6 |    000b     |  Blocks                |  Mandatory  |6 |    001b     |  Filemarks             |  Mandatory  |6 |    010b     |  Sequential filemarks  |  Optional   |6 |    011b     |  End-of-data           |  Optional   |6 |    100b     |  Setmarks              |  Optional   |6 |    101b     |  Sequential setmarks   |  Optional   |6 | 110b - 111b |  Reserved              |             |6 +====================================================+  A When spacing over blocks, filemarks, or setmarks, the count field-C specifies the number of blocks, filemarks, or setmarks to be spaced E over in the current partition.  A positive value N in the count field-@ shall cause forward positioning (toward end-of-partition) over NE blocks, filemarks, or setmarks ending on the end-of-partition side of-F the last block, filemark, or setmark.  A zero value in the count fieldF shall cause no change of logical position.  A negative value -N (two'sG complement notation) in the count field shall cause reverse positioning-E (toward beginning-of-partition) over N blocks, filemarks, or setmarks F ending on the beginning-of-partition side of the last block, filemark,F or setmark.  Support of spacing in the reverse direction is optional.   C If a filemark is encountered while spacing over blocks, the commandaB shall be terminated.  The logical position shall be on the end-of-G partition side of the filemark if movement was in the forward directioniF and on the beginning-of-partition side of the filemark if movement wasF in the reverse direction.  CHECK CONDITION status shall be returned toG the initiator, the sense key shall be set to NO SENSE, and the filemarkTF and valid bits shall be set to one in the sense data.  The informationD field shall be set to the requested count minus the actual number of0 blocks spaced over (not including the filemark).  F If a setmark is encountered while spacing over blocks or filemarks and@ the RSmk bit is set to one in the device configuration page (seeB 10.3.3.1), the command shall be terminated, CHECK CONDITION statusC shall be returned to the initiator, and the filemark and valid bitsaE shall be set to one in the sense data.  The sense key shall be set to > NO SENSE and the additional sense code shall be set to SETMARKD DETECTED.  The information field shall be set to the requested count? minus the actual number of blocks or filemarks spaced over (notrE including the setmark).  The logical position shall be on the end-of-rF partition side of the setmark if movement was in the forward directionE and on the beginning-of-partition side of the setmark if movement wastF in the reverse direction.  The target shall not return CHECK CONDITIONF status when a setmark is encountered if the RSmk bit is set to zero or  if this option is not supported.  E If early-warning is encountered while spacing over blocks, filemarks,rE or setmarks and the REW bit is set to one in the device configurationnB page (see 10.3.3.1), CHECK CONDITION status shall be returned, theG sense key shall be set to NO SENSE, and the EOM and valid bits shall beaD set to one in the sense data.  The information field shall be set toD the requested count minus the actual number of blocks, filemarks, orE setmarks spaced over as defined by the code value.  If the REW bit islG zero or the option is not supported by the target, the target shall noti9 report CHECK CONDITION status at the early-warning point.   B    NOTE 150 Setting the REW bit is not recommended for most system>    applications since data may be present after early-warning.  F If end-of-data is encountered while spacing over blocks, filemarks, orG setmarks, CHECK CONDITION status shall be returned, the sense key shalloC be set to BLANK CHECK, and the valid bit shall be set to one in thetE sense data.  Additionally, the EOM bit shall be set to one if end-of-oE data is encountered at or after early-warning.  The information field F shall be set to the requested count minus the actual number of blocks,@ filemarks, or setmarks spaced over as defined by the code value.  A If the end-of-partition is encountered while spacing forward over ? blocks, filemarks, or setmarks, CHECK CONDITION status shall bedG returned, the sense key shall be set to MEDIUM ERROR, the EOM bit shallmF be set to one, and the valid bit shall be set to one.  The informationD field shall be set to the requested count minus the actual number ofA blocks, filemarks, or setmarks spaced over as defined by the code. value.  C If beginning-of-partition is encountered while spacing over blocks,sA filemarks, or setmarks in the reverse direction, the target shallEG return CHECK CONDITION status and shall set the sense key to NO SENSE. aE The EOM and valid bits shall be set to one, and the information fieldeD set to the total number of blocks, filemarks, or setmarks not spacedF over (the requested number of blocks, filemarks, or setmarks minus the= actual number of blocks, filemarks, or setmarks spaced over).v  E When spacing over sequential filemarks (or setmarks), the count fieldh is interpreted as follows:F    a)     A positive value N shall cause forward movement to the firstK           occurrence of N or more consecutive filemarks (or setmarks) beingrC           logically positioned after the Nth filemark (or setmark). E    b)     A zero value shall cause no change in the logical position. K    c)     A negative value -N (2's complement notation) shall cause reversegC           movement to the first occurrence of N or more consecutive C           filemarks (or setmarks) being logically positioned on theaG           beginning-of-partition side of the Nth filemark (or setmark).e  E If a setmark is encountered while spacing to sequential filemarks and @ the RSmk bit is set to one in the device configuration page (seeE 10.3.3.1), CHECK CONDITION status shall be returned, the filemark bit G shall be set to one, and the valid bit shall be set to zero.  The sense G key shall be set to NO SENSE and the additional sense code shall be set=A to SETMARK DETECTED.  The target shall not return CHECK CONDITION F status when a setmark is encountered if the RSmk bit is set to zero or  if this option is not supported.  > If end-of-partition is encountered while spacing to sequentialD filemarks or setmarks, CHECK CONDITION status shall be returned, theC sense key shall be set to MEDIUM ERROR, the EOM bit shall be set to-, one, and the valid bit shall be set to zero.  F If end-of-data is encountered while spacing to sequential filemarks orG setmarks, CHECK CONDITION status shall be returned, the sense key shall ? be set to BLANK CHECK, and the valid bit shall be set to zero. -? Additionally, the EOM bit shall be set to one if end-of-data is-& encountered at or after early-warning.  > When spacing to end-of-data, the count field is ignored.  UponA successful completion, the medium shall be positioned such that a F subsequent write operation would append to the last logically recorded information.  F If end-of-partition is encountered while spacing to end-of-data, CHECKA CONDITION status shall be returned, the sense key shall be set toaF MEDIUM ERROR, the EOM bit shall be set to one, and the valid bit shall be set to zero.d   10.2.13 VERIFY command  F The VERIFY command (see table 190) requests that the target verify oneC or more block(s) beginning with the next block on the logical unit.v  4                           Table 190 - VERIFY commandO +=====-========-========-========-========-========-========-========-========+fO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |oO |=====+=======================================================================| O | 0   |                           Operation code (13h)                        | O |-----+-----------------------------------------------------------------------| O | 1   |   Logical unit number    |    Reserved     | Immed  | BytCmp | Fixed  |eO |-----+-----------------------------------------------------------------------|vO | 2   | (MSB)                                                                 | O |-----+---                                                                 ---|aO | 3   |                           Verification length                         |rO |-----+---                                                                 ---|iO | 4   |                                                                 (LSB) |CO |-----+-----------------------------------------------------------------------| O | 5   |                           Control                                     |=O +=============================================================================+     E An immediate (Immed) bit of zero indicates that the command shall not E return status until the verify operation has completed.  An Immed bit=E of one indicates that status shall be returned as soon as the command E descriptor block has been validated (but after the data transfer from + the initiator, if the BytCmp bit is one).  -  L    NOTE 151 In order to ensure that no errors are lost, the initiator shouldM    set the Immed bit to zero on the last VERIFY command when issuing a series-    of VERIFY commands.  C A byte compare (BytCmp) bit of zero indicates that the verification E shall be simply a medium verification (e.g. CRC, ECC).  No data shall 0 be transferred from the initiator to the target.  F A BytCmp bit of one indicates that the target shall perform a byte-by-D byte compare of the data on the medium and the data transferred fromC the initiator.  Data shall be transferred from the initiator to the D target as in a WRITE command.  If the BytCmp bit is one and the byteG compare option is not supported, the target shall terminate the commandoE with CHECK CONDITION status and the sense key shall be set to ILLEGAL= REQUEST.  B The verification length specifies the amount of data to verify, inA blocks or bytes, as indicated by the fixed bit. Refer to the READf? command (see 10.2.4) for a description of the fixed bit and any = associated error conditions. If the BytCmp bit is one and the-F verification length is zero, no data shall be verified and the currentC logical position shall not be changed.  This condition shall not be  considered as an error.0  C The VERIFY command shall terminate when the verification length has-E been satisfied, when an incorrect length block is encountered, when a|G filemark is encountered, when a setmark is encountered (if the RSmk bit D is one in the device configuration page, see 10.3.3.1), when end-of-C data is encountered, when the end-of-partition is encountered, wheniA early-warning is encountered (if the REW bit is one in the devicecF configuration page, see 10.3.3.1), or when an unrecoverable read errorG is encountered.  The status and sense data for each of these conditions D are handled in the same manner as in the READ command (see 10.2.4). D Upon successful completion of a VERIFY command, the logical position' shall be after the last block verified.l  C If the data does not compare (BytCmp bit of one), the command shallpD terminate with CHECK CONDITION status, the valid bit shall be set toG one, and the sense key shall be set to MISCOMPARE.  If the fixed bit isnE one, the information field shall be set to the requested verificationrG length minus the actual number of blocks successfully verified.  If thefF fixed bit is zero, the information field shall be set to the requestedA verification length minus the actual number of bytes successfullytD verified.  This number may be larger than the requested verificationG length if the error occurred on a previous VERIFY command with an ImmednG bit of one.  Upon termination, the medium shall be positioned after the 8 block containing the miscompare (end-of-partition side).   10.2.14 WRITE commands  D The WRITE command (see table 191) requests that the target write theF data that is transferred from the initiator to the current position on the logical unit.   3                           Table 191 - WRITE commandnO +=====-========-========-========-========-========-========-========-========+aO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |sO |Byte |        |        |        |        |        |        |        |        |sO |=====+=======================================================================|dO | 0   |                           Operation code (0Ah)                        |lO |-----+-----------------------------------------------------------------------|aO | 1   |   Logical unit number    |              Reserved             | Fixed  |-O |-----+-----------------------------------------------------------------------| O | 2   | (MSB)                                                                 |eO |-----+---                                                                 ---|sO | 3   |                           Transfer length                             | O |-----+---                                                                 ---|aO | 4   |                                                                 (LSB) |1O |-----+-----------------------------------------------------------------------|NO | 5   |                           Control                                     |rO +=============================================================================+k    F The fixed bit specifies whether fixed-length or variable-length blocksF are to be transferred.  See the READ BLOCK LIMITS command (see 10.2.5)? for additional information about fixed and variable block mode.g  D If the fixed bit is one, the transfer length specifies the number ofE fixed-length blocks to be transferred, using the current block length D reported in the mode parameter block descriptor (see 8.3.3).  If theB fixed bit is zero, a single block is transferred with the transfer, length specifying the block length in bytes.  D If the transfer length is zero, no data shall be transferred and the@ current position on the logical unit shall not be changed.  This+ condition shall not be considered an error.   B A WRITE command may be buffered or unbuffered, as indicated by theC buffered mode field of the mode parameter header (see 10.3.3).  ForeD unbuffered operation (buffered mode 0h), the target shall not returnC GOOD status until all data block(s) are successfully written to thehD medium.  For buffered operation (buffered mode 1h or 2h), the targetD may return GOOD status as soon as all data block(s) are successfully# transferred to the target's buffer.i  L    NOTE 152 For compatibility with devices implemented prior to this versionK    of this International Standard, a WRITE FILEMARKS command with the ImmedgD    bit set to zero should be issued when completing a buffered writeJ    operation to ensure that all buffered data, filemarks, and setmarks are    written to the medium.i  G If the logical unit encounters early-warning during a WRITE command, anmD attempt to finish writing any data may be made, as determined by theD current settings of the REW and SEW bits in the device configurationF page (see 10.3.3.1).  The command shall terminate with CHECK CONDITIONB status and the EOM and valid bits shall be set to one in the senseG data.  If all data that is to be written is successfully transferred tofF the medium, the sense key shall be set to NO SENSE or RECOVERED ERROR,< as appropriate.  If any data that is to be written cannot beF transferred to the medium when early-warning is encountered, the sense$ key shall be set to VOLUME OVERFLOW.  2 The information field shall be defined as follows:I    a)     If unbuffered mode is reported in the mode parameter header and I           the fixed bit is set to one, the information field shall be set E           to the requested transfer length minus the actual number off           blocks written.hJ    b)     If unbuffered mode is reported and the fixed bit is set to zero,F           the information field shall be set to the requested transfer           length.lK    c)     If buffered mode is reported in the mode parameter header and the H           fixed bit is set to one, the information field shall be set toI           the total number of blocks, filemarks, and setmarks not written K           (the number of blocks not transferred from the initiator plus theiD           number of blocks, filemarks, and setmarks remaining in theI           target's buffer).  Note that the value in the information field )           may exceed the transfer length. H    d)     If buffered mode is reported and the fixed bit is set to zero,J           the information field shall be set to the total number of bytes,F           filemarks, and setmarks not written (the number of bytes notB           transferred from the initiator plus the number of bytes,F           filemarks, and setmarks remaining in the target's buffer).        NOTES   eI    153 The value in the information field may exceed the transfer length.eO    154 The target should ensure that some additional data can be written to thetM    medium (e.g. labels, filemarks, or setmarks) after the first early-warning 1    indication has been returned to the initiator.w  C If a WRITE command is received while the logical unit is positioned C between early-warning and end-of-partition, the target shall returntD CHECK CONDITION status after attempting to perform the command.  TheF EOM and valid bits shall be set to one in the sense data.  If all dataD that is to be written is successfully transferred to the medium, theB information field shall be set to zero.  If any data that is to beF written is not transferred to the medium prior to encountering end-of-@ partition, the sense key shall be set to VOLUME OVERFLOW and the. information field shall be defined as follows:H    a)     If the fixed bit is one, the information field shall be set toI           the requested transfer length minus the actual number of blocks             written to the medium.I    b)     If the fixed bit is zero, the information field shall be set to-(           the requested transfer length.  L    NOTE 155 In some systems it is important to recognize an error if end-of-H    partition is encountered during execution of a WRITE command, withoutD    regard for whether all data that is to be written is successfullyK    transferred to the medium.  By its definition, the VOLUME OVERFLOW sense H    key may always validly be returned if end-of-partition is encounteredL    while writing, and such usage is recommended.  Reporting the MEDIUM ERRORM    sense key, as was done in some SCSI-1 implementations, may cause confusion E    as to whether there was really defective medium encountered during-'    execution of the last write command.-   10.2.15 WRITE FILEMARKS command   D The WRITE FILEMARKS command (see table 192) requests that the targetB write the specified number of filemarks or setmarks to the current position on the logical unit.e  8                      Table 192 - WRITE FILEMARKS commandO +=====-========-========-========-========-========-========-========-========+sO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |bO |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================|sO | 0   |                           Operation code (10h)                        | O |-----+-----------------------------------------------------------------------|cO | 1   |   Logical unit number    |         Reserved         |  WSmk  | Immed  |eO |-----+-----------------------------------------------------------------------|hO | 2   | (MSB)                                                                 |dO |-----+---                                                                 ---|iO | 3   |                           Transfer length                             |yO |-----+---                                                                 ---|hO | 4   |                                                                 (LSB) |hO |-----+-----------------------------------------------------------------------|,O | 5   |                           Control                                     |sO +=============================================================================+t    E If the Write Setmark (WSmk) bit is one, the transfer length specifiesdC the number of setmarks to be written.  If the WSmk bit is zero, thes@ transfer length specifies the number of filemarks to be written.  F An immediate (Immed) bit of one indicates that the target shall returnF status as soon as the command descriptor block has been validated.  AnG Immed bit of one is only valid if buffered mode is reported in the modeu parameter header (see 10.3.3).  F An Immed bit of zero indicates that the target shall not return statusG until the write operation has completed.  Any buffered data, filemarks, C and setmarks shall be written to the medium prior to completing ther command.  J    NOTE 156 Upon completion of any buffered write operation, the initiatorM    can issue a WRITE FILEMARKS command with the Immed bit set to zero and theeF    transfer length field set to zero to ensure that all buffered data,B    filemarks, and setmarks are successfully written to the medium.  E If the logical unit encounters early-warning during a WRITE FILEMARKStF command, an attempt to finish writing any buffered data, filemarks, orF setmarks may be made, as determined by the current settings of the REWB and SEW bits in the device configuration page (see 10.3.3.1).  TheC command shall terminate with CHECK CONDITION status and the EOM andaB valid bits shall be set to one in the sense data.  If all bufferedA data, filemarks, and setmarks are successfully transferred to theaE medium, the sense key shall be set to NO SENSE or RECOVERED ERROR, assG appropriate. If any buffered data, filemarks, or setmarks to be written D are not transferred to the medium when early-warning is encountered,. the sense key shall be set to VOLUME OVERFLOW.  2 The information field shall be defined as follows:J    a)     If unbuffered mode is reported in the mode parameter header, theI           information field shall be set to the requested transfer lengthTC           minus the actual number of filemarks or setmarks written.=K    b)     If buffered mode is reported in the mode parameter header and the I           buffered data was written in variable block mode (see 10.2.14), J           the information field shall be set to the total number of bytes,I           filemarks, and setmarks not written (the number of filemarks orpH           setmarks not transferred from the initiator plus the number ofK           bytes, filemarks and setmarks remaining in the target's buffer). nI           Note that it is possible for the value in the information field-(           to exceed the transfer length.K    c)     If buffered mode is reported and the buffered data was written in H           fixed block mode (see 10.2.14), the information field shall beH           set to the total number of blocks, filemarks, and setmarks notH           written (the number filemarks or setmarks not transferred fromJ           the initiator plus the number of blocks, filemarks, and setmarksJ           remaining in the target's buffer).  Note that it is possible forK           the value in the information field to exceed the transfer length.   M    NOTE 157 The target should ensure that some additional data can be written=M    to the medium (e.g. labels, filemarks, or setmarks) after the first early- 9    warning indication has been returned to the initiator.s  B If a WRITE FILEMARKS command is received while the logical unit isG positioned between early-warning and end-of-partition, the target shallfG return CHECK CONDITION status after attempting to perform the command. -E The EOM and valid bits shall be set to one in the sense data.  If alltG filemarks or setmarks to be written are successfully transferred to the E medium, the information field shall be set to zero.  If any filemarksyD or setmarks to be written are not transferred to the medium prior toC encountering end-of-partition, the sense key shall be set to VOLUMEt@ OVERFLOW and the information field shall be set to the requested@ transfer length minus the actual number of filemarks or setmarks written to the medium.  - 10.3 Parameters for sequential-access devices3      e 10.3.1 Diagnostic parameters  ? This subclause defines the descriptors and pages for diagnostica0 parameters used with sequential-access devices.   F The diagnostic page codes for sequential-access devices are defined in
 table 193.  7                       Table 193 - Diagnostic page codes O +=============-==================================================-============+dO |  Page code  |  Description                                     |  Subclause |aO |-------------+--------------------------------------------------+------------|dO |     00h     |  Supported diagnostic pages                      |  8.3.1.1   |eO |  01h - 3Fh  |  Reserved (for all device type pages)            |            |nO |  40h - 7Fh  |  Reserved                                        |            |iO |  80h - FFh  |  Vendor-specific pages                           |            | O +=============================================================================+d     10.3.2 Log parametersl  C This subclause defines the descriptors and pages for log parametersi% used with sequential-access devices. i  E The log page codes for sequential-access devices are defined in tabler 194.  4                           Table 194 - Log page codesO +=============-==================================================-============+ O |  Page code  |  Description                                     |  Subclause | O |-------------+--------------------------------------------------+------------|iO |     01h     |  Buffer over-run/under-run page                  |  8.3.2.1   |eO |     02h     |  Error counter page (write) page                 |  8.3.2.2   |bO |     03h     |  Error counter page (read) page                  |  8.3.2.2   | O |     04h     |  Error counter page (read reverse) page          |  8.3.2.2   | O |     05h     |  Error counter page (verify) page                |  8.3.2.2   | O |     07h     |  Last n error events page                        |  8.3.2.3   |hO |     06h     |  Non-media error page                            |  8.3.2.4   |mO |     00h     |  Supported log pages                             |  8.3.2.5   |lO |  08h - 2Fh  |  Reserved                                        |            | O |     3Fh     |  Reserved                                        |            |hO |  30h - 3Eh  |  Vendor-specific                                 |            | O +=============================================================================+      10.3.3 Mode parameters  D This subclause defines the descriptors and pages for mode parameters% used with sequential-access devices.    E The mode parameter list, including the mode parameter header and mode ) block descriptor, are described in 8.3.3.l  G The medium-type code field in the mode parameter header is reserved form sequential-access devices.  D The device-specific parameter byte of the mode parameter header (see= 8.3.3) is defined in table 195 for sequential-access devices.i  :                     Table 195 - Device-specific parameter O +=====-========-========-========-========-========-========-========-========+rO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |=====+========+==========================+===================================| O |     |   WP   |      Buffered mode       |               Speed               |eO +=============================================================================+m    G When used with the MODE SENSE command, a write protect (WP) bit of zeroMG indicates that medium is write enabled.  A WP bit of one indicates that G the medium is write protected.  When used with the MODE SELECT command,  this field is not defined.  < Values for the buffered mode field are defined in table 196.    4                           Table 196 - Buffered modesO +===========-=================================================================+ O |  Code     |  Description                                                    |nO |-----------+-----------------------------------------------------------------|eO |   0h      |  The target shall not report GOOD status on write commands until|BO |           |  the data blocks are actually written on the medium.            |eO |           |                                                                 |nO |   1h      |  The target may report GOOD status on write commands as soon as |eO |           |  as all the data specified in the write command has been        |mO |           |  transferred to the target's buffer.  One or more blocks may be |IO |           |  buffered prior to writing the block(s) to the medium.          | O |           |                                                                 |iO |   2h      |  The target may report GOOD status on write commands as soon as:|aO |           |     a) All the data specified in the write command has been     |=O |           |    successfully transferred to the target's buffer, and         | O |           |     b) All buffered data from different initiators has been     | O |           |    successfully written to the medium.                          |=O |           |                                                                 | O |  3h - 7h  |  Reserved                                                       |-O +=============================================================================+     E Values for the speed field shall be assigned as defined in table 197.-  8                       Table 197 - Speed field definitionO +===========-=================================================================+ O |  Code     |  Description                                                    | O |-----------+-----------------------------------------------------------------| O |     0h    |  Default (Use the peripheral device's default speed).           | O |     1h    |  Use the peripheral device's lowest speed.                      |-O |  2h - Fh  |  Use increasing peripheral device speeds.                       | O +=============================================================================+=    F For the MODE SELECT command, the density code field of the sequential-E access device block descriptor (8.3.3) indicates the density selectedIF by the initiator for use in subsequent read and write operations.  ForB devices capable of automatic density recognition, the density code? selected by the initiator may be overridden by the target for aiB subsequent read operation if the selected value does not match theC current recorded density of the medium.  If the MODE SELECT command3@ specifies the default density code the device selects the actualB density code to be used in a vendor-specific manner.  The value isG expected to be the principal density code (or an optimal density code).m  G For the MODE SENSE command, the density code field reflects the current D operating density of the device.  If a current operating density hasG not been selected, either because no medium is installed or because thetD density of the installed medium has not been determined, the densityB code field should be set to the principal density code value.  TheA principal density code is the highest density code supported, the ? optimal density code supported, or the most common density codesF supported.  In some devices, the principal density code value returnedG in response to a MODE SENSE command may change dynamically to match theCC most recently selected density.  The density code value returned ine= response to a MODE SENSE command shall be as described below:aK    a)     Following a UNIT ATTENTION condition for a power on or hard resettK           condition, while not ready, the target shall report the principalr           density.G    b)     Following a UNIT ATTENTION condition for a not-ready-to-readyn'           transition, the target shall:UL        1)    report the principal density if no attempt has been made by the-              target to determine the density;mL        2)    report the principal density if the target cannot automatically3              determine the density from the medium;fK        3)    report the current medium density if the target has determined       the density from the medium. I    c)     Following a successful read operation at or after beginning-of- I           medium, the target shall report a density code value reflecting H           the recorded density of the medium.  For some implementations,D           the target may automatically determine this value from the?           medium.  For devices not capable of automatic density'I           determination, the principal density is reported if the densitymJ           code value is not provided by the preceding MODE SELECT command.H    d)     Following an unsuccessful read operation or a successful writeG           operation, while at beginning-of-partition, the target shall:oF        1)    report a density code value as described for item b) if aL              previous MODE SELECT command has not established a density code.              for the currently mounted volume;K        2)    report a density code value as provided by the last successfulbB              MODE SELECT command for the currently mounted volume.I    e)     Following a successful unload operation the target shall reportaF           the most recent density code value as determined by items b)           through d) above.   ; Table 198 lists the sequential-access device density codes    <                  Table 198 - Sequential-access density codesX +==========-======================================================================-====+X |Code value|                           Description                                |Note|X |----------+----------------------------------------------------------------------+----|X |   00h    | Default density (MODE SELECT command only)                           |    |X |   0Eh    | Reserved for ECMA                                                    |    |X |15h - 7Eh | Reserved                                                             |    |X |   7Fh    | No change from previous density (NO-OP)                              |  7 |X |80h - FFh | Vendor-specific                                                      |    |X |          |----------------------------------------------------------------------+----|X |          |               Descriptions for magnetic tapes                        |    |X |          |----------------------------------------------------------------------|    |X |          |Width      mm(in) |Tracks|Density     bpmm(bpi)|Code|Type|Reference   |    |X |          |------------------+------+---------------------+----+----+------------|    |X |   01h    |12,7      (0,5)   |   9  |     32        (800) |NRZI| R  |X3.22-1983  |  2 |X |   02h    |12,7      (0,5)   |   9  |     63      (1 600) |PE  | R  |X3.39-1986  |  2 |X |   03h    |12,7      (0,5)   |   9  |    246      (6 250) |GCR | R  |X3.54-1986  |  2 |X |   05h    | 6,3      (0,25)  |  4/9 |    315      (8 000) |GCR | C  |X3.136-1986 |  1 |X |   06h    |12,7      (0,5)   |   9  |    126      (3 200) |PE  | R  |X3.157-1987 | 2,4|X |   07h    | 6,3      (0,25)  |   4  |    252      (6 400) |IMFM| C  |X3.116-1986 |  1 |X |   08h    | 3,81     (0,15)  |   4  |    315      (8 000) |GCR | CS |X3.158-1987 | 1,4|X |   09h    |12,7      (0,5)   |  18  |  1 491     (37 871) |GCR | C  |X3B5/87-099 | 2,4|X |   0Ah    |12,7      (0,5)   |  22  |    262      (6 667) |MFM | C  |X3B5/86-199 | 1,4|X |   0Bh    | 6,3      (0,25)  |   4  |     63      (1 600) |PE  | C  |X3.56-1986  |  1 |X |   0Ch    |12,7      (0,5)   |  24  |    500     (12 690) |GCR | C  |HI-TC1      | 1,6|X |   0Dh    |12,7      (0,5)   |  24  |    999     (25 380) |GCR | C  |HI-TC2      | 1,6|X |   0Fh    | 6,3      (0,25)  |  15  |    394     (10 000) |GCR | C  |QIC-120     | 1,6|X |   10h    | 6,3      (0,25)  |  18  |    394     (10 000) |GCR | C  |QIC-150     | 1,6|X |   11h    | 6,3      (0,25)  |  26  |    630     (16 000) |GCR | C  |QIC-320     | 1,6|X |   12h    | 6,3      (0,25)  |  30  |  2 034     (51 667) |RLL | C  |QIC-1350    | 1,6|X |   13h    | 3,81     (0,15)  |   1  |  2 400     (61 000) |DDS | CS |X3B5/88-185A|  5 |X |   14h    | 8,00     (0,315) |   1  |  1 703     (43 245) |RLL | CS |X3.202-1991 |  5 |X |   15h    | 8,00     (0,315) |   1  |  1 789     (45 434) |RLL | CS |ECMA TC17   |  5 |X |   16h    |12,7      (0,5)   |  48  |    394     (10 000) |MFM | C  |X3.193-1990 | 1,4|X |   17h    |12,7      (0,5)   |  48  |  1 673     (42 500) |MFM | C  |X3B5/91-174 | 1,4|X |--------------------------------------------------------------------------------------|X |   Code  Description                                              Type  Description   |X |   ----  ---------------------------------------                  ----  ------------  |X |   NRZI  Non return to zero, change on ones                         R   Reel-to-reel  |X |   GCR   Group code recording                                       C   Cartridge     |X |   PE    Phase encoded                                              CS  Cassette      |X |   IMFM  Inverted modified frequency modulation                                       |X |   MFM   Modified frequency modulation                                                |X |   DDS   DAT data storage                                                             |X |   RLL   Run length limited                                                           |X |--------------------------------------------------------------------------------------|X | NOTES                                                                                |X |  1   Serial recorded.                                                                |X |  2   Parallel recorded.                                                              |X |  3   Old format known as QIC-11.                                                     |X |  4   See annex D for additional standards information.                               |X |  5   Helical scan                                                                    |X |  6   This is not an American National Standard.  The reference is based              |X |      on an industry standard definition of the media format.                         |X |  7   This density code value is defined for the MODE SELECT command and              |X |      shall not be returned by the MODE SENSE command.                                |X +======================================================================================+    F The mode page codes for sequential-access devices are defined in table 199.  4                          Table 199 - Mode page codesO +=============-==================================================-============+ O |  Page code  |  Description                                     |  Subclause | O |-------------+--------------------------------------------------+------------| O |     0Ah     |  Control mode page                               |  8.3.3.1   |:O |     10h     |  Device configuration page                       | 10.3.3.1   | O |     02h     |  Disconnect-reconnect page                       |  8.3.3.2   | O |     11h     |  Medium partition page(1)                        | 10.3.3.2   | O |     12h     |  Medium partition page(2)                        | 10.3.3.3   | O |     13h     |  Medium partition page(3)                        | 10.3.3.3   | O |     14h     |  Medium partition page(4)                        | 10.3.3.3   | O |     09h     |  Peripheral device page                          |  8.3.3.3   |=O |     01h     |  Read-write error recovery page                  | 10.3.3.4   | O |     00h     |  Vendor-specific (does not require page format)  |            |=O |  03h - 08h  |  Reserved                                        |            |iO |  0Bh - 0Fh  |  Reserved                                        |            |-O |  15h - 3Eh  |  Vendor-specific (page format required)          |            |(O |     3Fh     |  Return all pages                                |            |pO |             |     (valid only for the MODE SENSE command)      |            |eO +=============================================================================+=    " 10.3.3.1 Device configuration page  D The device configuration page (see table 200) is used to specify the3 appropriate sequential-access device configuration.(  9                     Table 200 - Device configuration pageuO +=====-========-========-========-========-========-========-========-========+nO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |yO |Byte |        |        |        |        |        |        |        |        |hO |=====+========+========+=====================================================|fO | 0   |   PS   |Reserved|         Page code (10h)                             |eO |-----+-----------------------------------------------------------------------|yO | 1   |                           Page length (0Eh)                           |oO |-----+-----------------------------------------------------------------------|eO | 2   |Reserved|  CAP   |  CAF   |                Active format               |eO |-----+-----------------------------------------------------------------------| O | 3   |                           Active partition                            |sO |-----+-----------------------------------------------------------------------|tO | 4   |                           Write buffer full ratio                     |dO |-----+-----------------------------------------------------------------------|cO | 5   |                           Read buffer empty ratio                     |nO |-----+-----------------------------------------------------------------------| O | 6   | (MSB)                                                                 |dO |-----+---                        Write delay time                         ---|.O | 7   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|nO | 8   |  DBR   |  BIS   |  RSmk  |  AVC   |      SOCF       |   RBO  |  REW   | O |-----+-----------------------------------------------------------------------| O | 9   |                           Gap size                                    |eO |-----+-----------------------------------------------------------------------| O | 10  |      EOD defined         |  EEG   |  SEW   |        Reserved          | O |-----+-----------------------------------------------------------------------| O | 11  | (MSB)                                                                 |mO |-----+---                                                                 ---|tO | 12  |                           Buffer size at early warning                | O |-----+---                                                                 ---|OO | 13  |                                                                 (LSB) |sO |-----+-----------------------------------------------------------------------|lO | 14  |                           Select data compression algorithm           | O |-----+-----------------------------------------------------------------------| O | 15  |                           Reserved                                    | O +=============================================================================+t    E A change active partition (CAP) bit of one indicates that the logicalaG partition is to be changed to the one specified by the active partitionmD field. A CAP bit of zero indicates no partition change is specified.  A A change active format (CAF) bit of one indicates that the active8C format is to be changed to the value specified in the active format=> field.  A CAF bit of zero indicates no active format change isE specified.  For some devices, the format may only be changed when the * logical unit is at beginning-of-partition.  G  The active format field indicates which recording format is in use fortC the selected density code when reading or writing data on a logical A unit.  The value of the active format field is vendor-specific.     B The active partition field indicates the current logical partition number in use on the medium.  G The write buffer full ratio, on WRITE commands, indicates to the target B how full the buffer shall be before writing data to the medium.  A8 value of zero indicates that the value is not specified.  F The read buffer empty ratio, on READ commands, indicates to the targetD how empty the buffer shall be before retrieving additional data fromG the medium.  A value of zero indicates that the value is not specified.-  F The write delay time indicates the maximum time, in 100 ms increments,B that the target should wait before any buffered data that is to beF written, is forced to the medium after the last buffered WRITE commandG that did not cause the buffer to exceed the buffer full ratio.  A value D of zero indicates that the target shall never force buffered data to" the medium under these conditions.  A A data buffer recovery (DBR) bit of one indicates that the targetCG supports data buffer recovery using the RECOVER BUFFERED DATA command.  A A DBR bit of zero indicates that the target does not support data0- buffer recovery.  This bit is target-defined.3  D A block identifiers supported (BIS) bit of zero indicates that blockE IDs are not supported in the format written on the medium.  A BIS bit G of one indicates that the format on the medium has recorded information A about the block IDs relative to a partition.  This bit is target-| defined.  C A report setmarks (RSmk) bit of one indicates that the target shall9> recognize and report setmarks during appropriate read or spaceC operations.  A RSmk bit of zero indicates that the target shall not2 report setmarks.  C The automatic velocity control (AVC) bit of one, indicates that the2C device shall select the speed (if the device supports more than one6E speed) based on the data transfer rate that should optimize streaming,? activity and minimize medium repositioning.  An AVC bit of zeroC@ indicates the speed chosen should be the device's default speed.  F A stop on consecutive filemarks (SOCF) field of 00b indicates that theB device shall pre-read data from the medium in buffered mode to theA limits of the buffer capacity without regard for filemarks.  ThisSA implies that the device can differentiate between data blocks and C filemarks in the buffer.  Values 01b, 10b, and 11b specify that the3C device shall terminate the pre-read operation if one, two, or three6E consecutive filemarks are detected, respectively.  If the RSmk bit is1A one, the target shall interpret this field as stop on consecutive0	 setmarks.   B A recover buffer order (RBO) bit of one indicates that data blocksG shall be returned from the target's buffer on a RECOVERED BUFFERED DATA F command in LIFO order (last-in-first-out) from which they were written@ to the buffer.  A RBO bit of zero indicates data blocks shall be, returned in FIFO (first-in-first-out) order.  B A report early-warning (REW) bit of zero indicates that the targetG shall not report the early-warning condition for read operations and it A shall report early-warning at or before any medium-defined early- * warning position during write operations.   G A REW bit of one indicates that the target shall return CHECK CONDITION D status with the EOM bit set in the sense data when the early-warningE position is encountered during read and write operations.  If the REW A bit is one and the SEW bit is zero, the target shall return CHECK F CONDITION status with the sense key set to VOLUME OVERFLOW when early-/ warning is encountered during write operations.-  M    NOTE 158 A REW bit of one is intended for compatibility with those systems I    using old tape formats that require an early-warning indication during G    read operations.  Other systems should set this bit to zero to avoid K    potential data loss when interchanging tapes between peripheral devices.n  G The GapSize field value determines the size of the inter-block gap when G writing data.  A value of 00h specifies the device's defined gap size.  G A value of 01h specifies a device defined gap size sufficiently long to F support update-in-place.  Values of 02h through 0Fh are multipliers onE the device's defined gap size.  Values 10h through 7Fh are reserved. a+ Values 80h through FFh are vendor-specific.   C The end-of-data (EOD) defined field indicates which format type theSF logical unit shall use to detect and generate the EOD area.  The types* of EOD formats are specified in table 201.  2                            Table 201 - EOD formatsC +=============-===================================================+oC |    Value    |  Description                                      | C |-------------+---------------------------------------------------|=C |     000b    |  Logical unit's default EOD definition            | C |     001b    |  Format-defined erased area of medium             |-C |     010b    |  As specified in the SOCF field                   |-C |     011b    |  EOD recognition and generation is not supported  | C | 100b - 111b |  Reserved                                         | C +=================================================================+     @ An enable EOD generation (EEG) bit set to one indicates that theF logical unit shall generate the appropriate EOD area, as determined byG the EOD defined field. A value of zero indicates that EOD generation is3	 disabled.d  L    NOTE 159 Some logical units may not generate EOD at the completion of any    write-type operation.  D The synchronize at early-warning (SEW) bit set to one indicates thatF the target shall cause any buffered write data, filemarks, or setmarksD to be transferred to the medium when early-warning is encountered. AB value of zero indicates that the target shall retain any unwrittenF buffered data, filemarks, or setmarks in the buffer when early-warningG is encountered (see the WRITE command, 10.2.14, and the WRITE FILEMARKS  command, 10.2.15).  E The buffer size at early-warning field indicates the value, in bytes, G to which the target shall reduce its logical buffer size when writing. |F The target should reduce the buffer size only when the logical unit isF positioned between its early-warning and end-of-partition.  A value ofA zero indicates that the implementation of this function is deviceo specific.     M    NOTE 160 The intent is to prevent the loss of data by limiting the size ofu-    the buffer when near the end-of-partition.   E The select data compression algorithm field set to 00h indicates that=G the target shall not use a compression algorithm on any data sent to it G prior to writing the data to the medium.  A value of 01h indicates that E the data to be written shall be compressed using the target's default D compression algorithm.  Values 02h through 7Fh are reserved.  Values$ 80h through FFh are vendor-specific.  ! 10.3.3.2 Medium partition page(1)   C The medium partition page(1) (see table 202) is used to specify the-E first group of medium partitions.  Additional groups are specified inl medium partition pages(2-4).  9                      Table 202 - Medium partition page(1)-O +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |-O |Byte |        |        |        |        |        |        |        |        |nO |=====+========+========+=====================================================|-O | 0   |   PS   |Reserved|         Page code (11h)                             |lO |-----+-----------------------------------------------------------------------|-O | 1   |                           Page length                                 |tO |-----+-----------------------------------------------------------------------|-O | 2   |                           Maximum additional partitions               | O |-----+-----------------------------------------------------------------------|eO | 3   |                           Additional partitions defined               | O |-----+-----------------------------------------------------------------------|-O | 4   |  FDP   |  SDP   |  IDP   |       PSUM      |       Reserved           |SO |-----+-----------------------------------------------------------------------|-O | 5   |                           Medium format recognition                   | O |-----+-----------------------------------------------------------------------|-O | 6   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|-O | 7   |                           Reserved                                    | O |=====+=======================================================================| O |     |                   Partition size descriptor(s)                        |eO |=====+=======================================================================| O | 0   | (MSB)                                                                 | O |-----+---                        Partition size                           ---|-O | 1   |                                                                 (LSB) |pO +=============================================================================+-    A The maximum additional partitions field is a target-defined valuevG indicating the maximum number of additional partitions supported by the=D logical unit.  A value of zero indicates that no value is specified.  ? The additional partitions defined field specifies the number ofsD additional partitions to be defined for a volume when the SDP or IDPF bit is set to one.  The maximum value allowed is the value returned in( the maximum additional partitions field.  B A fixed data partitions (FDP) bit of one indicates that the device@ assigns partitions based on its fixed definition of partitions. G Setting this bit to one may only be valid at beginning-of-partition andg0 is mutually exclusive with the SDP and IDP bits.  F A select data partitions (SDP) bit of one indicates that the device isE to partition the medium into the number of partitions as specified byoE the additional partitions defined field using partition sizes defined G by the device.  Setting this bit to one may only be valid at beginning- F of-partition and it is mutually exclusive with the FDP and IDP fields.  C An initiator-defined partitions (IDP) bit of one indicates that therF initiator is defining the number and size of the data partitions using> the additional partitions defined field and the partition sizeG descriptors. Setting this bit to one may only be valid at beginning-of- @ partition and is mutually exclusive with the FDP and SDP fields.  M    NOTE 161 Since defining partitions may require reformatting the medium foriG    some implementations, an implicit write to the medium may occur as aaI    result of a MODE SELECT command that supplies any of these parameters.I  F Partition size unit of measure (PSUM) field defines the units in whichE the partition size descriptors select the partition size.  The valuesdF 00b, 01b, and 10b define the units as bytes, kilobytes, and megabytes,) respectively.  The value 11b is reserved.   >  The medium format recognition field is a target-defined valueG indicating the device's capability to automatically identify the medium0@ format and partition information when reading an unknown volume.  C Values for the medium format recognition field shall be assigned asp follows:D    a)     00h       Logical unit is incapable of format or partition                      recognition.G    b)     01h       Logical unit is capable of format recognition only. J    c)     02h       Logical unit is capable of partition recognition only.C    d)     03h       Logical unit is capable of format and partition                       recognition.+        e)    04h - FFh            Reserved.   I    NOTE 162 If a target indicates that it is not capable of medium formatsJ    recognition, the initiator must supply all necessary parameters for theJ    device to identify the specific format.  The value in this field may be'    different following a medium change.i  G Partition size descriptors define the size of the respective partitions E in the units specified in the PSUM field.  Up to 64 partitions may benF defined using this page.  If additional partitions need to be defined,B up to 64 partitions can be defined in each of the medium partition pages(2-4) defined in 10.3.3.3.v  # 10.3.3.3 Medium partition page(2-4)k  A The medium partition page(2-4) (see table 203) is used to specifyaE additional groups of medium partitions.  The first group is specifiedh/ in the medium partition page(1) (see 10.3.3.2).i  :                     Table 203 - Medium partition page(2-4)O +=====-========-========-========-========-========-========-========-========+oO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |eO |=====+========+========+=====================================================| O | 0   |   PS   |Reserved|         Page code (12h, 13h, 14h)                   |oO |-----+-----------------------------------------------------------------------|rO | 1   |                           Page length                                 |nO |=====+=======================================================================|tO |     |                       Partition size descriptor(s)                    |tO |=====+=======================================================================|tO | 0   | (MSB)                                                                 |rO |-----+---                        Partition size                           ---|lO | 1   |                                                                 (LSB) |oO +=============================================================================+h    C The additional page codes defined for partition size definition arerF 12h, 13h, and 14h.  Up to a maximum of 64 partitions can be defined inG each of these pages.  The partition size is defined by the value of the C partition size field.  The units of size used by the partition size D field is specified in the PSUM field of the medium partition page(1) (see 10.3.3.2).d  M    NOTE 163 Since defining partitions may require reformatting the medium for G    some implementations, an implicit write to the medium may occur as asC    result of a MODE SELECT command that supplies these parameters. p  ' 10.3.3.4 Read-write error recovery pagei  F The read-write error recovery page (see table 204) specifies the error@ recovery and reporting parameters that the target shall use when> transferring data between the initiator and the medium.  TheseD parameters only apply to read-write errors and do not affect message8 system retries or positioning error recovery procedures.  <                   Table 204 - Read-write error recovery pageO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        | O |=====+========+========+=====================================================| O | 0   |   PS   |Reserved|         Page code (01h)                             |=O |-----+-----------------------------------------------------------------------| O | 1   |                           Page length (0Ah)                           |rO |-----+-----------------------------------------------------------------------|3O | 2   |Reserved|Reserved|   TB   |Reserved|  EER   |  PER   |  DTE   |  DCR   |tO |-----+-----------------------------------------------------------------------|tO | 3   |                           Read retry count                            |aO |-----+-----------------------------------------------------------------------|eO | 4   |                           Reserved                                    |dO |-----+-----------------------------------------------------------------------|eO | 5   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|tO | 6   |                           Reserved                                    |uO |-----+-----------------------------------------------------------------------|rO | 7   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|eO | 8   |                           Write retry count                           |iO |-----+-----------------------------------------------------------------------|hO | 9   |                           Reserved                                    |wO |-----+-----------------------------------------------------------------------|iO | 10  |                           Reserved                                    |uO |-----+-----------------------------------------------------------------------| O | 11  |                           Reserved                                    |)O |-----------------------------------------------------------------------------|eO |   NOTE - The parameters in this page also apply to verify operations.       |MO +=============================================================================+=    D A transfer block (TB) bit of one indicates that a data block that is= not recoverable within the specified recovery limits shall be H transferred to the initiator before CHECK CONDITION status is returned. F A TB bit of zero indicates that the unrecoverable data block shall notC be transferred to the initiator.  Data blocks that can be recovered D within the recovery limits are always transferred, regardless of the value of the TB bit.  C An enable early recovery (EER) bit of one indicates that the target C shall use the most expedient error recovery algorithm (e.g. attempt-F error correction prior to retries).  An EER bit of zero indicates thatB the target shall use the most deliberate error recovery algorithm,D within the limits established by the other error recovery parametersB (e.g. attempt to recover the block error-free prior to using error correction).  D A post error (PER) bit of one indicates that the target shall returnE CHECK CONDITION status to report recovered errors.  A PER bit of zero-F indicates that the target shall not report errors recovered within theD limits established by the error recovery parameters.  If this bit is+ zero, the DTE bit must also be set to zero.-  F A disable transfer on error (DTE) bit of one indicates that the targetD shall terminate the data transfer after a recovered read-write errorE occurs.  All data from the recovered block shall be transferred prior E to terminating the read-write operation.  A DTE bit of zero indicates E that the target shall not terminate the transfer for errors recovered=> within the limits established by the read-write error recovery parameters.   E A disable correction (DCR) bit of one indicates that the target shall=C not use error correction codes during error recovery.  A DCR bit of A zero allows the use of error correction codes for error recovery.   B The read retry count specifies the number of times that the targetG should attempt its recovery algorithm during a read operation before an=F unrecoverable error is reported.  A read retry count of zero indicates@ that the target shall not use its recovery algorithm during read operations.g  C The write retry count specifies the number of times that the target E should attempt its recovery algorithm during a write operation beforei@ an unrecoverable error is reported.  A write retry count of zeroE indicates that the target shall not use its recovery algorithm duringt write operations.u  6 10.4 Definitions specific to sequential access devices  D 10.4.1 beginning-of-partition:  The position at the beginning of theF permissible recording region of a partition.  If only one partition isC defined, this position is typically equivalent to the beginning-of-i medium.t  E 10.4.2 beginning-of-medium:  The extreme position along the medium indD the direction away from the supply reel which can be accessed by the device.   B 10.4.3 buffered mode:  A mode of data transfer in write operationsB which facilitates tape streaming (10.1.5), as reported in the mode4 parameter header device-specific parameter (10.3.3).  G 10.4.4 early-warning:  A physical mark or device computed position neardB but logically before the end-of-partition (independent of physical@ direction).  See the REW bit in the device configuration page in	 10.3.3.1.g  E 10.4.5 end-of-data:  End of data in a partition is denoted in format-tF specific manner. See the EOD defined field in the device configuration page in 10.3.3.1.   C 10.4.6 end-of-medium:  The extreme position along the medium in therA direction away from the take-up reel which can be accessed by theaG device.  This position may be accessed by devices that support the LOADD+ UNLOAD command with the EOT bit set to one.a  D 10.4.7 end-of-partition:  The position at the end of the permissible  recording region of a partition.  @ 10.4.8 filemark:  A special recorded element within a partition,> containing no user data, which provides a segmentation scheme.  D 10.4.9 overlength:  The incorrect length condition that exists afterA executing a read command when the length of the actual block read F exceeds the requested transfer length in the command descriptor block.  E 10.4.10 partition:  The entire usable region of recording and readingfC paths in a volume or in a portion of a volume, defined in a device-tD specific manner.  If there is more than one partition, they shall be? numbered starting with zero (i.e. beginning-of-partition-zero).o  @ 10.4.11 setmark:  A special recorded element within a partition,= containing no user data, which provides a segmentation schemefB hierarchically superior to filemarks for use in addressing or fast- positioning on high capacity storage devices.6  C 10.4.12 spacing:  The act of positioning the medium on a sequentialc access device.  F 10.4.13 underlength:  The incorrect length condition that exists afterB executing a read command when the requested transfer length in theE command descriptor block exceeds the length of the actual block read.i  G 10.4.14 volume:  A recording medium together with its physical carrier.      11 Commands for printer devices      11.1 Model for printer devices t  @ This command set includes capability for the printer-controllingF device, that is an SCSI target to be is functionally separate from theG physical printer device (see figure 27) as well as integrated with it. 0F The physical printer device is connected to the SCSI target via one ofC several common device-level interfaces.  There may be more than one)G physical printer device attached to the printer controlling device.  In=@ such a case, each physical printer device is assigned a separateB logical unit number, beginning with zero.  The printer-controllingG device, printer device-level interface, and the physical printer device|3 are referred to collectively as the printer device.=                    6                         Figure 27 - SCSI printer model  G Specific control mechanisms are defined in mode pages for two industry--F standard interfaces known as the line printer interface (e.g. the DataG Products interface or equivalent) and the EIA RS-232C interface.  These F mode pages are used to control optional features of these interfaces. C No mode page was defined for the popular industry-standard paralleloD interface because the options requiring controls are embedded in the data.=  C The printer-controlling device may be integrated within the printer > device; it is not required to use one of the industry-standard interfaces referenced above.  A The printer device commands are structured on the assumption that F specific printer control codes may be embedded in the data transferredC by the FORMAT, PRINT, and SLEW AND PRINT commands.  The transparentlG control codes may take the form of escape code sequences.  commands for.E the operation of the target function and some printer controls, whicheC are not convenient to handle in a transparent way, are specified ine 11.2.   C This International Standard does not specify which character set ishB used by the printer device; nor does it specify the meaning of the) escape code sequences that may be used.  u  ! 11.2 Commands for printer devicess  @ The commands for printer devices shall be as shown in table 205.  ;                    Table 205 - Commands for printer devicestH +=====================================-============-======-============+H |  Command name                       | Operation  | Type |  Subclause |H |                                     |   code     |      |            |H |-------------------------------------+------------+------+------------|H | CHANGE DEFINITION                   |    40h     |   O  |   8.2.1    |H | COMPARE                             |    39h     |   O  |   8.2.2    |H | COPY                                |    18h     |   O  |   8.2.3    |H | COPY AND VERIFY                     |    3Ah     |   O  |   8.2.4    |H | FORMAT                              |    04h     |   O  |  11.2.1    |H | INQUIRY                             |    12h     |   M  |   8.2.5    |H | LOG SELECT                          |    4Ch     |   O  |   8.2.6    |H | LOG SENSE                           |    4Dh     |   O  |   8.2.7    |H | MODE SELECT(6)                      |    15h     |   O  |   8.2.8    |H | MODE SELECT(10)                     |    55h     |   O  |   8.2.9    |H | MODE SENSE(6)                       |    1Ah     |   O  |   8.2.10   |H | MODE SENSE(10)                      |    5Ah     |   O  |   8.2.11   |H | PRINT                               |    0Ah     |   M  |  11.2.2    |H | READ BUFFER                         |    3Ch     |   O  |   8.2.12   |H | RECEIVE DIAGNOSTIC RESULTS          |    1Ch     |   O  |   8.2.13   |H | RECOVER BUFFERED DATA               |    14h     |   O  |  11.2.3    |H | RELEASE UNIT                        |    17h     |   M  |  10.2.9    |H | REQUEST SENSE                       |    03h     |   M  |   8.2.14   |H | RESERVE UNIT                        |    16h     |   M  |  10.2.10   |H | SEND DIAGNOSTIC                     |    1Dh     |   M  |   8.2.15   |H | SLEW AND PRINT                      |    0Bh     |   O  |  11.2.4    |H | STOP PRINT                          |    1Bh     |   O  |  11.2.5    |H | SYNCHRONIZE BUFFER                  |    10h     |   O  |  11.2.6    |H | TEST UNIT READY                     |    00h     |   M  |   8.2.16   |H | WRITE BUFFER                        |    3Bh     |   O  |   8.2.17   |H |----------------------------------------------------------------------|H |Key:  M = command implementation is mandatory.                        |H |      O = command implementation is optional.                         |H +======================================================================+    F The following operation codes are vendor-specific: 01h, 02h, 05h, 06h,G 07h, 08h, 09h, 0Ch, 0Dh, 0Eh, 0Fh, 11h, 13h, 19h, and C0h through FFh.  B All remaining operation codes for printer devices are reserved for future standardization.-   11.2.1 FORMAT command-  E The FORMAT command (see table 206) provides a means for the initiatorsE to specify forms or fonts to printers that support programmable forms=@ or fonts.  The format information is peripheral-device specific.  4                           Table 206 - FORMAT commandO +=====-========-========-========-========-========-========-========-========+tO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |tO |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================|rO | 0   |                           Operation code (04h)                        |tO |-----+-----------------------------------------------------------------------|lO | 1   | Logical unit number      |         Reserved         | Format type     |nO |-----+-----------------------------------------------------------------------| O | 2   | (MSB)                                                                 |pO |-----+---                                                                 ---|rO | 3   |                           Transfer length                             |sO |-----+---                                                                 ---| O | 4   |                                                                 (LSB) |pO |-----+-----------------------------------------------------------------------|aO | 5   |                           Control                                     | O +=============================================================================+r    D The format type field specifies the type of format information to beG transferred from the initiator to the target.  This field is defined inn
 table 207.  2                            Table 207 - Format type +========-===================+ |  Code  |  Format type      | |--------+-------------------| |   00b  |  Set form         | |   01b  |  Set font         | |   10b  |  Vendor-specific  | |   11b  |  Reserved         | +============================+    G The transfer length specifies the length in bytes of format information G that shall be transferred during the DATA OUT phase.  A transfer length C of zero indicates that no format information shall be transferred. s0 This condition shall not be considered as error.   11.2.2 PRINT command  C The PRINT command (see table 208) transfers the specified number oft5 bytes from the initiator to the target to be printed.w  3                           Table 208 - PRINT commandtO +=====-========-========-========-========-========-========-========-========+oO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |tO |Byte |        |        |        |        |        |        |        |        |nO |=====+=======================================================================| O | 0   |                           Operation code (0Ah)                        | O |-----+-----------------------------------------------------------------------|tO | 1   | Logical unit number      |                  Reserved                  |fO |-----+-----------------------------------------------------------------------|sO | 2   | (MSB)                                                                 |mO |-----+---                                                                 ---|iO | 3   |                           Transfer length                             |eO |-----+---                                                                 ---|5O | 4   |                                                                 (LSB) |.O |-----+-----------------------------------------------------------------------|4O | 5   |                           Control                                     |fO +=============================================================================+     G The transfer length specifies the length in bytes of data that shall beeA transferred during the DATA OUT phase.  A transfer length of zerotF indicates that no data shall be transferred.  This condition shall not be considered as error.w  $ 11.2.3 RECOVER BUFFERED DATA command  @ The RECOVER BUFFERED DATA command (see table 209) returns to theG initiator data that was transferred to the target, but not yet printed.w  ;                   Table 209 - RECOVER BUFFERED DATA command O +=====-========-========-========-========-========-========-========-========+eO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |vO |Byte |        |        |        |        |        |        |        |        |oO |=====+=======================================================================|oO | 0   |                           Operation code (14h)                        |nO |-----+-----------------------------------------------------------------------|lO | 1   | Logical unit number      |                  Reserved                  |sO |-----+-----------------------------------------------------------------------|sO | 2   | (MSB)                                                                 |rO |-----+---                                                                 ---|cO | 3   |                           Transfer length                             |rO |-----+---                                                                 ---| O | 4   |                                                                 (LSB) |iO |-----+-----------------------------------------------------------------------|nO | 5   |                           Control                                     |aO +=============================================================================+n    E This command is normally used only to recover from error or exception C conditions that make it impossible to print the buffered data.  TheIG order in which data are transferred from the target to the initiator isiE the same as when the data were previously transferred using the PRINT D command or SLEW AND PRINT command.  Data transferred by this commandG are  deleted from the target data buffer.  One or more RECOVER BUFFERED A DATA commands may be used to return the buffered data that is notr printed.  C If an attempt is made to recover more data than is contained in thenG buffer, the command shall be terminated with CHECK CONDITION status andqE the sense key shall be set to NO SENSE.  In addition, the EOM, valid,oE and ILI bits shall be set to one.  The information bytes shall be setnF to the difference (residue) between the transfer length and the actual number of bytes returned.   F The transfer length specifies the maximum length in bytes of data thatD shall be transferred during the DATA IN phase.  A transfer length ofG zero indicates that no data shall be transferred.  This condition shalla not be considered as error.u   11.2.4 SLEW AND PRINT commandn  B The SLEW AND PRINT command (see table 210) transfers the specifiedE number of bytes from the initiator to the target to be printed.  ThisaA command is provided for printer devices that do not support forms 3 control information embedded within the print data.c  8                       Table 210 - SLEW AND PRINT commandO +=====-========-========-========-========-========-========-========-========+tO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |sO |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================| O | 0   |                           Operation code (0Bh)                        |=O |-----+-----------------------------------------------------------------------|pO | 1   | Logical unit number      |                  Reserved         | Channel| O |-----+-----------------------------------------------------------------------|-O | 2   |                           Slew value                                  |.O |-----+-----------------------------------------------------------------------| O | 3   | (MSB)                                                                 |AO |-----+---                        Transfer length                          ---| O | 4   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------| O | 5   |                           Control                                     | O +=============================================================================+     G The transfer length specifies the length in bytes of data that shall be|A transferred during the DATA OUT phase.  A transfer length of zerohF indicates that no data shall be transferred.  This condition shall not be considered as error.   B If the channel bit is zero, the slew value specifies the number ofA lines the form shall be advanced before printing.  A value of 255 G indicates that the form shall be advanced to the first line of the next @ form before printing.  If the channel bit is one, the slew valueE specifies the forms control channel number to which the form shall be A advanced prior to printing the data.  If implemented, the printer0C options page in the MODE SELECT command provides additional control ' over the usage of the slew value field.D  E If the channel bit is one, and the channel option is not implemented,AC the command shall be terminated with CHECK CONDITION status and theT* sense key shall be set to ILLEGAL REQUEST.   11.2.5 STOP PRINT commandY  D The STOP PRINT command (see table 211) requests that the target halt3 printing on buffered devices in an orderly fashion.M  6                         Table 211 - STOP PRINT commandO +=====-========-========-========-========-========-========-========-========+-O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================|+O | 0   |                           Operation code (1Bh)                        |,O |-----+-----------------------------------------------------------------------|nO | 1   | Logical unit number      |                  Reserved         | Retain | O |-----+-----------------------------------------------------------------------|oO | 2   |                           Vendor-specific                             | O |-----+-----------------------------------------------------------------------| O | 3   |                           Reserved                                    |-O |-----+-----------------------------------------------------------------------||O | 4   |                           Reserved                                    ||O |-----+-----------------------------------------------------------------------|=O | 5   |                           Control                                     | O +=============================================================================+-    G A retain bit of zero requests that the target data buffer be discarded; @ otherwise, the data not printed shall be retained.  The data notD printed may be recovered using the RECOVER BUFFERED DATA command, ifD implemented by the target.  A subsequent SYNCHRONIZE BUFFER command,G PRINT command, or SLEW AND PRINT command shall cause the remaining data F not already printed to be printed, followed by the data transferred by? the subsequent command, if any.  The point at which printing is - suspended by this command is vendor-specific.   ! 11.2.6 SYNCHRONIZE BUFFER command   F The SYNCHRONIZE BUFFER command (see table 212) provides a means for anF initiator to ensure that the data have been printed successfully priorD to releasing the peripheral device.  This is useful for applicationsB that handle any error or exception conditions (e.g. end-of-medium)( prior to termination of the application.  :                     Table 212 - SYNCHRONIZE BUFFER commandO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |tO |Byte |        |        |        |        |        |        |        |        |1O |=====+=======================================================================| O | 0   |                           Operation code (10h)                        |gO |-----+-----------------------------------------------------------------------| O | 1   | Logical unit number      |                  Reserved                  | O |-----+-----------------------------------------------------------------------|cO | 2   |                           Reserved                                    |yO |-----+-----------------------------------------------------------------------| O | 3   |                           Reserved                                    |=O |-----+-----------------------------------------------------------------------| O | 4   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|=O | 5   |                           Control                                     |)O +=============================================================================+-    A When all buffered data are actually printed, the command shall be ? terminated with a GOOD status.  If it is not possible to finish-? printing all of the buffered data (due to an error or exceptionB? condition on the peripheral device), then this command shall be G terminated with a CHECK CONDITION status and the appropriate sense key.   D The printer options page in the MODE SELECT command, if implemented,F provides additional control over termination sequences when using this command.  # 11.3 Parameters for printer devices      11.3.1 Diagnostic parameters  ? This subclause defines the descriptors and pages for diagnostic-& parameters used with printer devices.   G The diagnostic page codes for printer devices are defined in table 213.   7                       Table 213 - Diagnostic page codes=O +=============-==================================================-============+yO |  Page code  |  Description                                     |  Subclause |nO |-------------+--------------------------------------------------+------------|nO |     00h     |  Supported diagnostic pages                      |  8.3.1.1   |EO |  01h - 3Fh  |  Reserved (for all device type pages)            |            |rO |  40h - 7Fh  |  Reserved                                        |            |EO |  80h - FFh  |  Vendor-specific pages                           |            |-O +=============================================================================+|     11.3.2 Log parametersv  C This subclause defines the descriptors and pages for log parameters| used with printer devices. =  @ The log page codes for printer devices are defined in table 214.  4                           Table 214 - Log page codesO +=============-==================================================-============+-O |  Page code  |  Description                                     |  Subclause |dO |-------------+--------------------------------------------------+------------|-O |     01h     |  Buffer over-run/under-run page                  |  8.3.2.1   | O |     07h     |  Last n error events page                        |  8.3.2.3   | O |     06h     |  Non-medium error page                           |  8.3.2.4   | O |     00h     |  Supported log pages                             |  8.3.2.5   | O |  02h - 05h  |  Reserved                                        |            | O |  08h - 2Fh  |  Reserved                                        |            |-O |     3Fh     |  Reserved                                        |            | O |  30h - 3Eh  |  Vendor-specific pages                           |            |=O +=============================================================================+r     11.3.3 Mode parameters  D This subclause defines the descriptors and pages for mode parameters used with printer devices. e  E The mode parameter list, including the mode parameter header and moder) block descriptor, are described in 8.3.3.   D The medium-type code field is contained in the mode parameter header9 (see 8.3.3).  This field is reserved for printer devices.A  F The device-specific parameter field is contained in the mode parameterD header (see 8.3.3).  Table 215 defines the device-specific parameter used for printer devices.   =                 Table 215 - Printer device-specific parameterlO +=====-========-========-========-========-========-========-========-========+oO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |hO |=====+========+==========================+===================================|tO |     |   WP   |      Buffered mode       |            Reserved               | O +=============================================================================+a    E When using the MODE SELECT command, a buffered mode of zero indicatesEC that the target shall not report a GOOD status on PRINT commands ora? SLEW AND PRINT commands until the data are actually printed.  AaG buffered mode of one indicates that the target may report a GOOD statusdE on PRINT commands or SLEW AND PRINT commands as soon as the data haveaF been transferred to the SCSI device buffer.  The data from one or moreA commands may be buffered prior to printing.  Buffered modes of 2h= through 7h are reserved.  F When using the MODE SENSE command, the buffered mode field returns the  current value of this parameter.  ? The density code field is contained in the mode parameter block=G descriptor (see table 93).  This field is reserved for printer devices.   ? The mode page codes for printer devices are shown in table 216.-  4                          Table 216 - Mode page codesO +=============-==================================================-============+ O |  Page code  |  Description                                     |  Subclause |-O |-------------+--------------------------------------------------+------------| O |     0Ah     |  Control mode page                               |  8.3.3.1   |-O |     02h     |  Disconnect-reconnect page                       |  8.3.3.2   | O |     03h     |  Parallel printer interface page                 | 11.3.3.1   | O |     09h     |  Peripheral device page                          |  8.3.3.3   | O |     05h     |  Printer options page                            | 11.3.3.2   |-O |     04h     |  Serial printer interface page                   | 11.3.3.3   | O |     01h     |  Reserved                                        |            |=O |  06h - 08h  |  Reserved                                        |            |tO |  0Bh - 1Fh  |  Reserved                                        |            |nO |     00h     |  Vendor-specific (does not require page format)  |            |eO |  20h - 3Eh  |  Vendor-specific (page format required)          |            |fO |     3Fh     |  Return all pages                                |            |hO |             |     (valid only for the MODE SENSE command)      |            |gO +=============================================================================+     & 11.3.3 Parallel printer interface page  B The parallel printer interface page (see table 217) is intended toC support printer devices that use the industry-standard line printeru
 interface.  :                     Table 217 - Parallel printer interfaceO +=====-========-========-========-========-========-========-========-========+IO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |NO |Byte |        |        |        |        |        |        |        |        |tO |=====+========+========+=====================================================| O | 0   |   PS   |Reserved|            Page code (03h)                          |=O |-----+-----------------------------------------------------------------------| O | 1   |                           Parameter length (03h)                      | O |-----+-----------------------------------------------------------------------|=O | 2   |  Parity select  |  PIPC  |Reserved|  VCBP  |  VCBS  |  VES   | Autofd |(O |-----+-----------------------------------------------------------------------|-O | 3   |                           Reserved                                    | O +=============================================================================+-    @ The parameters savable (PS) bit is only used with the MODE SENSEF command.  This bit is reserved with the MODE SELECT command.  A PS bitC of one indicates that the target is capable of saving the page in a ' non-volatile, vendor-specific location.   B The parity select field specifies parity generation on the printer" interface is defined in table 218.  3                           Table 218 - Parity select # +========-========================+-# |  Code  |  Parity select         |-# |--------+------------------------| # |   00b  |  No parity generation  | # |   01b  |  Even parity           | # |   10b  |  Odd parity            |=# |   11b  |  Reserved              |=# +=================================+t    E A paper instruction parity check (PIPC) bit of one indicates that thee@ printer interface Paper Instruction signal is included in parityF generation on the printer interface by the target.  A PIPC bit of zeroE indicates that the Paper Instruction signal is not included in parityc2 generation on the printer interface by the target.      NOTESL    164 The format of the vertical forms unit (VFU) control byte is specifiedM    by the VCBP, VCBS, and VES bits.  The VFU control byte is not part of thiscF    standard; however, a discussion of it is included here for a betterF    understanding.  This VFU control byte (see table, below) includes aI    control bit (C) to select whether to slew over a number of lines or toiG    skip to a vertical forms unit (VFU) channel number.  This bit may becI    located in two different bit positions and may have either polarity.   L    165 The number of lines to slew over may be coded as an unsigned four-bitL    number (NNNN) or an unsigned six-bit number (EENNNN).  The upper two bitsK    of the six-bit number (EE) may be positioned contiguously with the lower L    four bits (NNNN) or they may be separated from the lower four bits by theF    control bit (C).  Furthermore, the upper two bits may or may not be
    supported. L    166 The VFU channel to select is specified by an unsigned four-bit number"    (NNNN) in the VFU control byte.;    167 Pictorially, the control byte is shown in table 219.m  5                          Table 219 - VFU control byte H +=======================-==============================================+H |   VFU control byte    |  Description                                 |H |-----------------------|                                              |H | Bits 7 6 5 4 3 2 1 0  |                                              |H |-----------------------+----------------------------------------------|H |      0 E E C N N N N  |  Advance (EE)NNNN lines   (C = line skip)    |H |      0 0 0 C N N N N  |  Skip to VFU channel NNNN (C = VFU channel)  |H |      0 C E E N N N N  |  Advance (EE)NNNN lines   (C = line skip)    |H |      0 C 0 0 N N N N  |  Skip to VFU channel NNNN (C = VFU channel)  |H |----------------------------------------------------------------------|H | Key:  C = VFU control bit                                            |H +======================================================================+    C A VFU control bit polarity (VCBP) bit of one indicates that the VFUrF control bit (C) is true for a VFU channel command and false for a lineC skip command.  A VCBP bit of zero indicates the opposite polarity.    E A VFU control bit select (VCBS) bit of one indicates that the controltG bit (C) is in bit position 6 and the EE bits are in bit positions 5 andrC 4.  A VCBS bit of zero indicates that the control bit (C) is in bitl8 position 4 and the EE bits are in bit positions 6 and 5.  C A VFU extended skip (VES) bit of one indicates that the EE bits arerE supported for line skip operations.  A VES bit of zero indicates that  the EE bits are not supported.  E For MODE SELECT, an automatic line feed (Autofd) bit of one specifies=G that the target assert the printer interface Auto Line Feed signal.  An ? Autofd bit of zero specifies that the target negate the printer-B interface Auto Line Feed signal.  For MODE SENSE, the target shall% return the current value of this bit.    11.3.3.2 Printer options pager  G The printer options page (see table 220) supports control and reportinge) of various target functions and features.   4                          Table 220 - Printer optionsO +=====-========-========-========-========-========-========-========-========+=O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |uO |Byte |        |        |        |        |        |        |        |        |eO |=====+========+========+=====================================================| O | 0   |   PS   |Reserved|            Page code (05h)                          |=O |-----+-----------------------------------------------------------------------| O | 1   |                           Parameter length (0Ah)                      |-O |-----+-----------------------------------------------------------------------|uO | 2   |  EVFU  |                  Font identification                         |nO |-----+-----------------------------------------------------------------------| O | 3   |     Reserved    |    Slew mode    |    Reserved     |  SCTE  |  AFC   |gO |-----+-----------------------------------------------------------------------| O | 4   | (MSB)                                                                 | O |-----+---                        Maximum line length                      ---| O | 5   |                                                                 (LSB) |pO |-----+-----------------------------------------------------------------------|=O | 6   |                           EVFU format start character                 |sO |-----+-----------------------------------------------------------------------|eO | 7   |                           EVFU format stop character                  |mO |-----+-----------------------------------------------------------------------| O | 8   |  Line slew options                |  Form slew options                |pO |-----+-----------------------------------+-----------------------------------|pO | 9   |  Data termination options         |         Reserved                  |sO |-----+-----------------------------------------------------------------------|aO | 10  |                           Reserved                                    |=O |-----+-----------------------------------------------------------------------| O | 11  |                           Reserved                                    |=O +=============================================================================+     @ The parameters savable (PS) bit is only used with the MODE SENSEF command.  This bit is reserved with the MODE SELECT command.  A PS bitC of one indicates that the target is capable of saving the page in at& non-volatile vendor-specific location.  D An electronic vertical forms unit (EVFU) bit of one indicates that a@ tape or electronic vertical forms unit is present in the printerC device.  An EVFU bit of zero indicates that the electronic verticalsD forms unit should not be used or that the unit is not present in the printer device.  i  D For the MODE SELECT command, the font identification field specifiesA which font is to be used.  For the MODE SENSE command, this field F identifies the currently selected font.  The font identification codes are defined table 221.  6                        Table 221 - Font identification( +=============-========================+( |    Code     |  Font identification   |( |-------------+------------------------|( |     00h     |  Default font          |( |  01h - 3Fh  |  Reserved              |( |  40h - 7Fh  |  Vendor-specific font  |( +======================================+    F For the MODE SELECT command, the slew mode field controls the target'sE behavior when a SLEW AND PRINT command is received with a channel bit E of zero (see 11.2.4).  For the MODE SENSE command, this field reportsa? the current slew mode.  This slew mode is defined in table 222.e  1                             Table 222 - Slew mode O +========-====================================================================+ O |  Code  |  Slew mode                                                         | O |--------+--------------------------------------------------------------------| O |   00b  |  SLEW AND PRINT commands with a channel bit of zero are supported  | O |        |  without any required setup.                                       | O |        |                                                                    | O |   01b  |  SLEW AND PRINT commands with a channel bit of zero are only       | O |        |  accepted after the initiator issues a FORMAT command with a format| O |        |  type of set form (to initialize the electronic vertical forms     | O |        |  unit).                                                            | O |        |                                                                    |=O |   10b  |  SLEW AND PRINT commands with a channel bit of zero are always     |pO |        |  accepted.  The target shall use the electronic vertical forms unit|-O |        |  if it has previously been initialized or it shall initialize the  |iO |        |  electronic vertical forms unit for line skipping by sending the   |=O |        |  EVFU start format character immediately followed by the EVFU stop | O |        |  format character (both are defined below) prior to executing the  | O |        |  SLEW AND PRINT command.                                           |=O |        |                                                                    | O |   11b  |  Reserved                                                          |-O +=============================================================================+     G For the MODE SELECT command, a step count truncate enable (SCTE) bit of-E one indicates that the target shall assume the printer truncates slew|G values in SLEW AND PRINT commands, so that the data prints on the first-D line of the next form.  A SCTE bit of zero indicates that the targetC shall assume the printer continues to slew over forms boundaries in=? SLEW AND PRINT commands if the slew value exceeds the number of A remaining lines on the current form.  The target shall return theo3 current value of this field in the MODE SENSE data.m  B An ASCII forms control (AFC) bit of one indicates that the printerF supports ASCII forms control characters.  An AFC bit of zero indicatesA that the printer does not support ASCII forms control characters.s  C The maximum line length field specifies the maximum transfer lengthsG (maximum number of bytes per line) to be accepted in the SLEW AND PRINT C command.  A value of 0000h in MODE SELECT specifies that the target F shall use its default value.  In any case, the target shall report its0 actual value in the MODE SENSE data (not 0000h).  E The EVFU format start character field specifies the character code toiC be used by the target to start the initialization of the electronice9 vertical forms unit, if slew mode option 10b is selected.h  G The EVFU format stop character field specifies the character code to beP? used by the target to stop the initialization of the electronic 9 vertical forms unit, if slew mode option 10b is selected.e  D The line slew options field specifies the implementation of the lineA slew (using ASCII forms control characters) in the SLEW AND PRINTf= command.  Code values in this field are defined in table 223.r  1                             Table 223 - Line slewyO +=========-===================================================================+eO |   Code  |  Line slew option                                                 |.O |---------+-------------------------------------------------------------------| O |    0h   |  Not implemented.  (SLEW AND PRINT commands cause CHECK CONDITION | O |         |  status with ILLEGAL REQUEST sense key.)                          | O |         |                                                                   | O |    1h   |  The target shall insert an ASCII carriage return character (0Dh) | O |         |  for each line to slew over.                                      |dO |         |                                                                   | O |    2h   |  The target shall insert an ASCII line feed character (0Ah) for   | O |         |  each line to slew over.                                          |=O |         |                                                                   | O |    3h   |  The target shall insert an ASCII carriage return character (0Dh) |-O |         |  and line feed character (0Ah) for each line to slew over.        | O |         |                                                                   |-O | 4h - 7h |  Reserved                                                         |eO |         |                                                                   |=O | 8h - Fh |  Vendor-specific                                                  |kO +=============================================================================+|    @ The form slew options field specifies the implementation of formE slewing in the SLEW AND PRINT command.  Code values in this field are  defined in table 224.=  1                             Table 224 - Form slew=O +=========-===================================================================+tO |   Code  |  Form slew option                                                 | O |---------+-------------------------------------------------------------------|tO |    0h   |  Not implemented.  (SLEW AND PRINT commands cause CHECK CONDITION |tO |         |  status with ILLEGAL REQUEST sense key.)                          | O |         |                                                                   | O |    1h   |  The target shall insert an ASCII form feed character (0Ch) to    |rO |         |  move to the beginning of the next form.                          | O |         |                                                                   |cO |    2h   |  The target shall insert an ASCII carriage return character (0Dh) | O |         |  and form feed character (0Ch) to move to the beginning of the    |LO |         |  next form.                                                       |hO |         |                                                                   | O | 3h - 7h |  Reserved                                                         | O |         |                                                                   |=O | 8h - Fh |  Vendor-specific                                                  | O +=============================================================================+     E The data termination options field specifies the termination sequence=G to be issued to the printer device when a SYNCHRONIZE BUFFER command isS? received.  Code values for this field are defined in table 225.   8                      Table 225 - Data termination optionO +=========-===================================================================+)O |   Code  |  Line slew option                                                 |-O |---------+-------------------------------------------------------------------| O |    0h   |  Selects the target default implementation (MODE SELECT).         |-O |         |                                                                   | O |    1h   |  No termination sequence.  (The target sends any remaining data   |-O |         |  in its buffer to the printer device with no termination sequence | O |         |                                                                   | O |    2h   |  The target shall print any buffered data followed by an ASCII    | O |         |  carriage return character (0Dh).                                 |-O |         |                                                                   |rO |    3h   |  The target shall print any buffered data followed by an ASCII    |-O |         |  line feed character (0Ah).                                       |aO |         |                                                                   |-O |    4h   |  The target shall print any buffered data followed by an ASCII    |oO |         |  carriage return, line feed character sequence (0Dh, 0Ah).        |-O |         |                                                                   |eO |    5h   |  The target shall send any buffered data followed by an ASCII     |-O |         |  form feed character (0Ch).                                       | O |         |                                                                   |-O |    6h   |  The target shall print any buffered data followed by an ASCII    | O |         |  carriage return, form feed character sequence (0Dh, 0Ch).        |=O |         |                                                                   |hO |    7h   |  The target shall issue a zero line slew command to the printer   |bO |         |  device.                                                          |aO |         |                                                                   | O | 8h - Bh |  Reserved                                                         |iO |         |                                                                   | O | Ch - Fh |  Vendor-specific                                                  |iO +=============================================================================+o    & 11.3.3.3 Serial printer interface page  @ The serial printer interface page (see table 226) is intended toG support printer devices that use the industry-standard serial interfacee# usually referred to as EIA RS-232C.=  9                      Table 226 - Serial printer interfaceiO +=====-========-========-========-========-========-========-========-========+nO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |pO |Byte |        |        |        |        |        |        |        |        | O |=====+========+========+=====================================================|TO | 0   |   PS   |Reserved|            Page code (04h)                          |SO |-----+-----------------------------------------------------------------------| O | 1   |                           Parameter length (06h)                      |=O |-----+-----------------------------------------------------------------------| O | 2   |     Reserved    |         Stop bit length                             |-O |-----+-----------------------------------------------------------------------| O | 3   |     Parity selection     |Reserved|        Bits per character         | O |-----+-----------------------------------+-----------------------------------| O | 4   |  RTS   |  CTS   |     Reserved    |        Pacing protocol            | O |-----+-----------------------------------------------------------------------| O | 5   | (MSB)                                                                 | O |-----+---                                                                 ---| O | 6   |                           Baud rate                                   | O |-----+---                                                                 ---| O | 7   |                                                                 (LSB) | O +=============================================================================+     @ The parameters savable (PS) bit is only used with the MODE SENSEF command.  This bit is reserved with the MODE SELECT command.  A PS bitC of one indicates that the target is capable of saving the page in ad& non-volatile vendor-specific location.  D The stop bit length field specifies the length of the stop bit(s) inC units of 1/16 bit.  The target may round this field as described in F 7.5.4.  A stop bit length of zero in the MODE SELECT command indicates, that the target shall use its default value.  F The parity selection field specifies parity generation and checking as defined in table 227.=  5                          Table 227 - Parity selection  +========-===================+ |  Code  |  Parity selection | |--------+-------------------| |  000b  |  None             | |  001b  |  Mark             | |  010b  |  Space            | |  011b  |  Odd              | |  100b  |  Even             | |  101b  |  Reserved         | |  110b  |  Reserved         | |  111b  |  Reserved         | +============================+    A The bits per character field specifies the number of bits in eachsE character.  A value of zero in the MODE SELECT command indicates that 0 the target shall use its default character size.  ? For the MODE SELECT command, a request to send (RTS) bit of oneCG specifies that the target shall insure the Request to Send (RTS) signaltC in the serial interface follows the line state of the Data Terminalu> Ready (DTR) signal in the serial interface.  A RTS bit of zeroG specifies that the target shall set the Request to Send (RTS) signal topF high whenever the target power is on.  For the MODE SENSE command, the4 target shall report the current value of this field.  G For the MODE SELECT command, a clear to send (CTS) bit of one specifies C that the target shall delay data transmission to the printer device F until the printer device asserts the Clear to Send (CTS) signal in theD serial interface.  A CTS bit of zero indicates that the target shallA ignore the Clear to Send signal.  For the MODE SENSE command, thee4 target shall report the current value of this field.  G The code values for the pacing protocol field are defined in table 228.n  4                          Table 228 - Pacing protocol +=========-==================+ |   Code  |  Pacing protocol | |---------+------------------| |    0h   |  None            | |    1h   |  XON/XOFF        | |    2h   |  ETX/ACK         | |    3h   |  DTR             | | 4h - 7h |  Reserved        | | 8h - Fh |  Vendor-specific | +============================+    D The baud rate field specifies the baud rate in bits per second.  TheG target may round this value as described in 7.5.4.  A baud rate of zero B in the MODE SELECT command specifies that the target shall use its default baud rate.     12 Processor devices      12.1 Model for processor devices  C The SCSI processor device is a target with the characteristics of arF primary computing device, typically a personal computer, minicomputer,D mainframe computer, or auxiliary computing device or server.  Such aF primary computing device is often called a host.  The processor deviceC receives or provides packets of data as requested by the initiator.   F In the SCSI processor device, the target accepts and provides the dataD packets transferred according to the commands of the initiator.  TheE initiator and the processor device are both assumed to know the ruleshF by which information is exchanged between them, how the information is@ interpreted by the processor device, and when it is allowable to@ exchange the information.  These rules are not specified by this International Standard.   C The initiator requests that the processor device accept a packet of E data by transmitting a SEND command.  The initiator requests that thecB processor device return a packet of data by transmitting a RECEIVEA command.  A COPY command can also be transmitted to the processor C device to request that it serve as a copy manager.  The actual data G flow can be between the processor device and another SCSI device or caneA be between two SCSI devices under control of the processor devicem acting as a copy manager.=  G If a processor device temporarily has no resource available to manage aFD data packet from the initiator, has no data packet to provide to theE initiator, or has no resources assigned to perform the operation, the-7 device may then choose one of the following responses: mI    a)     Terminate the command with CHECK CONDITION status and the sensenJ           key NOT READY with the appropriate additional sense code for theK           condition.  This is the appropriate response to a TEST UNIT READYe           command.  H    b)     Disconnect until the necessary resource or data packet becomesG           available, and then reconnect to the initiator and resume the            operation.1    c)     Terminate the command with BUSY status.n  F More than one logical unit can be implemented by a processor device.  A Logical units can serve as additional paths to a single resource, C and/or each logical unit can serve as a path to different resourceshE within the device.  A single logical unit may also serve as a path to D multiple resources if the processor device can interpret information> within the data packet and route the packet to the appropriateG resource.  If the logical unit addressed by the initiator does not have F an available resource or data packet associated with it, the processorF device may choose to treat the logical unit as an invalid logical unit> (see 7.5.3) or respond as described in the previous paragraph.  E If the processor device determines that an error or unusual condition G has occurred while performing an operation specified by the contents of C a data packet, the information describing the condition is normally== returned as a part of a data packet.  If the processor device @ determines that an error or unusual condition has occurred while= executing the SCSI command from the initiator, the command is-A terminated with a CHECK CONDITION and the failures are identifiede  through a REQUEST SENSE command.  E The SCSI processor device is distinguished from a SCSI communications F device by the fact that the primary destination of the data packets isE within the target device.  A SCSI communications device, in contrast,e@ passes the data on to an ultimate destination outside the targetC through a network.  Many types of devices may find it convenient to C function as processor devices if no other suitable SCSI device type D exists and if the packet exchange protocol dictated by the processorD device model meets their functional requirements.  Devices requiringB totally incompatible protocols and command sets should be examinedF carefully to ensure that the incompatibilities are based on functionalD requirements.  If  they are, they should be treated as vendor-unique
 device types.   D Several examples of processor device implementations are provided to: clarify the range of utility of the SCSI processor device.  , 12.1.1 Host-to-host communication, SEND only  ? A host system, (host A), takes the initiator role and selects a D processor device (host B), transmitting a packet to host B using theF SEND command.  The SEND command contains an operating system call thatG requests data from the local storage devices attached to host B.  After D performing the functions required by the data packet, Host B assumesF the initiator mode and selects host A as a processor device and uses aC SEND command to transmit the requested data back to host A.  Host AeE thus acts as a primary computer and host B acts as a specialized data G server computer.  Note that the SEND command is sufficient to perform aeG complete transaction if both host A and host B are capable of acting as D initiators.  This provides the capability of a high bandwidth inter-+ communication among nearby host processors.   3 12.1.2 Host-to-host communication, SEND and RECEIVE   G A host system (host A) takes the initiator role and selects a processor G device (host B), transmitting a packet using the SEND command to host BfC containing instructions about an operation to be performed.  Host A=F again takes the initiator role and sends the data to be used by host BE in the operation.  Host A then assumes that a result will be obtainedpE consistent with rules understood by both devices.  Host A generates aeG RECEIVE command to obtain the result from host B.  If the result is not=F yet ready, host B may disconnect until the calculation is complete and6 the requested data packet can be returned to host A.    K    NOTE 168 Host A need not support target mode and host B need not support F    initiator mode to successfully complete an exchange between the two    devices.   ( 12.1.3 Host-to-special-output peripheral  @ A special co-processor device which can use the processor deviceA command set is a high-performance graphics display terminal.  The F initiator sends to the display terminal control and data packets  thatG contain the image to be displayed.  Only the SEND command is required.  A A peripheral failure should be indicated through the normal CHECK-$ CONDITION / REQUEST SENSE protocol.   ' 12.1.4 Host-to-special-input peripheral   F A second special co-processor device that can use the processor deviceA command set is a data acquisition subsystem.  Such subsystems maynF multiplex and compact streams of data from many sources.  A host couldG control the data acquisition modes and the selection of data streams byRC transmitting control packets to the processor device using the SEND E command.  The host could then obtain the acquired data by executing a-C series of RECEIVE commands.  The data acquisition device could also G serve as an initiator, selecting peripheral storage devices and storing G the compacted acquired data there for later access directly by the hosttF or through host to host communication protocols.  A peripheral failureE would be indicated through the normal CHECK CONDITION / REQUEST SENSE 	 protocol.   # 12.2 Commands for processor devicesL  B The commands for processor devices shall be as shown in table 229.  <                   Table 229 - Commands for processor devicesH +=====================================-============-======-============+H |  Command name                       | Operation  | Type |  Subclause |H |                                     |   code     |      |            |H |-------------------------------------+------------+------+------------|H | CHANGE DEFINITION                   |    40h     |   O  |   8.2.1    |H | COMPARE                             |    39h     |   O  |   8.2.2    |H | COPY                                |    18h     |   O  |   8.2.3    |H | COPY AND VERIFY                     |    3Ah     |   O  |   8.2.4    |H | INQUIRY                             |    12h     |   M  |   8.2.5    |H | LOG SELECT                          |    4Ch     |   O  |   8.2.6    |H | LOG SENSE                           |    4Dh     |   O  |   8.2.7    |H | READ BUFFER                         |    3Ch     |   O  |   8.2.12   |H | RECEIVE                             |    08h     |   O  |  12.2.1    |H | RECEIVE DIAGNOSTIC RESULTS          |    1Ch     |   O  |   8.2.13   |H | REQUEST SENSE                       |    03h     |   M  |   8.2.14   |H | SEND                                |    0Ah     |   M  |  12.2.2    |H | SEND DIAGNOSTIC                     |    1Dh     |   M  |   8.2.15   |H | TEST UNIT READY                     |    00h     |   M  |   8.2.16   |H | WRITE BUFFER                        |    3Bh     |   O  |   8.2.17   |H |----------------------------------------------------------------------|H |Key:  M = command implementation is mandatory.                        |H |      O = command implementation is optional.                         |H +======================================================================+    F The following operation codes are vendor-specific: 02h, 05h, 06h, 09h,B 0Ch, 0Dh, 0Eh, 0Fh, 10h, 11h, 13h, 14h, 19h, C0h through FFh.  AllG remaining operation codes for processor devices are reserved for futureS standardization.   12.2.1 RECEIVE command  E The RECEIVE command (see table 230) requests that the target transfergC data to the initiator.  The contents of the data are not defined byo this International Standard.  4                          Table 230 - RECEIVE commandO +=====-========-========-========-========-========-========-========-========+tO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================|=O | 0   |                           Operation code (08h)                        |oO |-----+-----------------------------------------------------------------------| O | 1   | Logical unit number      |                  Reserved                  |dO |-----+-----------------------------------------------------------------------|IO | 2   | (MSB)                                                                 |eO |-----+---                                                                 ---|aO | 3   |                           Allocation length                           |aO |-----+---                                                                 ---|yO | 4   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|nO | 5   |                           Control                                     |fO +=============================================================================+o     12.2.2 SEND commandt  G The SEND command (see table 231) requests that the target transfer datab from the initiator.   3                            Table 231 - SEND command O +=====-========-========-========-========-========-========-========-========+eO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |IO |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================|hO | 0   |                           Operation code (0Ah)                        |nO |-----+-----------------------------------------------------------------------|rO | 1   | Logical unit number      |                  Reserved         |  AEN   |iO |-----+-----------------------------------------------------------------------|sO | 2   | (MSB)                                                                 | O |-----+---                                                                 ---| O | 3   |                           Transfer length                             |eO |-----+---                                                                 ---| O | 4   |                                                                 (LSB) |kO |-----+-----------------------------------------------------------------------|hO | 5   |                           Control                                     |oO +=============================================================================+t    F An asynchronous event notification (AEN) bit of one indicates that theF data to be transferred conforms to AEN data format as defined in tableC 232.  A SEND command with an AEN bit of one shall be only issued toi logical unit zero.  <                   Table 232 - SEND command - AEN data formatO +=====-========-========-========-========-========-========-========-========+tO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |eO |Byte |        |        |        |        |        |        |        |        |tO |=====+=================+========+=================+==========================|sO | 0   |     Reserved    | LUNTAR |     Reserved    |          LUNTRN          |oO |-----+-----------------------------------------------------------------------|dO | 1   |                               Reserved                                |eO |-----+-----------------------------------------------------------------------|iO | 2   |                               Reserved                                |tO |-----+-----------------------------------------------------------------------|mO | 3   |                               Reserved                                |eO |-----+-----------------------------------------------------------------------|tO | 4   |                               Sense data byte (0)                     | O |- - -+---                                                                 ---|iO | n+4 |                               Sense data byte (n)                     |eO +=============================================================================+o    @ An AEN bit of zero indicates that the data to be transferred are vendor-specific.  G The transfer length specifies the length in bytes of data that shall berD sent during the DATA OUT phase.  A transfer length of zero indicatesF that no data shall be sent.  This condition shall not be considered an error.  = A logical unit target (LUNTAR) bit of zero specifies that therC asynchronous event occurred on a logical unit.  A LUNTAR bit of one-C specifies that the asynchronous event occurred on a target routine.e  A If the LUNTAR bit is zero, the logical unit number target routinen= number (LUNTRN) field specifies the logical unit on which the B asynchronous event occurred.  If the LUNTAR bit is one, the LUNTRN> field specifies on the routine on which the asynchronous event	 occurred.i  - The sense data bytes are defined in table 65.a  % 12.3 Parameters for processor devicesr     12.3.1 Diagnostic parameters  ? This subclause defines the descriptors and pages for diagnostics( parameters used with processor devices.   D The diagnostic page codes for processor devices are defined in table 233.  7                       Table 233 - Diagnostic page codesBO +=============-==================================================-============+aO |  Page code  |  Description                                     | Subclause  |sO |-------------+--------------------------------------------------+------------|rO |     00h     |  List of supported parameters page               |  8.3.1.1   |NO |  01h - 3Fh  |  Reserved (for all device type pages)            |            | O |  40h - 7Fh  |  Reserved                                        |            | O |  80h - FFh  |  Vendor-specific pages                           |            |tO +=============================================================================+o     12.3.2 Log parametersB  C This subclause defines the descriptors and pages for log parametersl used with processor devices.  B The log page codes for processor devices are defined in table 234.  4                           Table 234 - Log page codesO +=============-==================================================-============+dO |  Page code  |  Description                                     |  Subclause |vO |-------------+--------------------------------------------------+------------|sO |     01h     |  Buffer over-run/under-run page                  |  8.3.2.1   |aO |     07h     |  Last n error events page                        |  8.3.2.3   |iO |     00h     |  List of supported parameters page               |  8.3.2.5   |TO |     06h     |  Non-medium error page                           |  8.3.2.4   |eO |  02h - 05h  |  Reserved                                        |            |sO |  08h - 2Fh  |  Reserved                                        |            |mO |  30h - 3Eh  |  Vendor-specific pages                           |            |dO |     3Fh     |  Reserved                                        |            | O +=============================================================================+     . 12.4 Definitions specific to processor devices  F 12.4.1 host:  A device with the characteristics of a primary computingA device, typically a personal computer, workstation, minicomputer,o< mainframe computer, or auxiliary computing device or server.  G 12.4.2 data packet:  The data transferred during the DATA IN phase of atG RECEIVE command, or during the DATA OUT phase of a SEND command. A dataoG packet often contains information at the beginning or end of the packetoF that describes the contents of the packet. A data packet might contain9 control or status information for the destination device.=  F 12.4.3 resource:  A part of the device required to operate on or store the data packet.     13 Write-once devices     ! 13.1 Model for write-once devices   A The model for the write-once device is a variation on the optical-E memory model.  Most of the aspects of a write-once device are similarOB to optical memory devices.  The differences are summarized in this clause.    13.1.1 Logical blocks   E Data may be written to a logical block only once.  A subsequent writeV? to a logical block already written may or may not be corrupted,NC depending on the implementation.  Write-once physical media is non- 	 volatile.T  B The updating of blocks (see 16.1) is discouraged.  SCSI write-onceG devices are intended to be archival in nature.  Data at a logical blockBA address is not expected to change once it is written.  The update ? commands are not defined for this device type.  Devices are not A precluded from implementing the update function by this standard, F though devices that require the update function should use the optical memory device type.   F Devices may be able to determine the state of a logical block prior to@ access.  These devices can determine whether a block is blank orC written. This is useful in detecting previously written blocks, and C preventing a destructive overwrite.  This is also useful in finding.F blank areas for later writing.  The MEDIUM SCAN command can be used to< find blank and written areas prior to WRITE and READ access.   13.1.2 Initialization   F The FORMAT UNIT command is not defined for write-once devices.  Write-D once media is shipped pre-formatted by the manufacturer and is ready for use when mounted.t   13.1.3 Physical medium defects  C The raw defect rate is typically higher for optical medium than foru> magnetic medium.  Data is usually recovered through the use of> sophisticated error correction algorithms.  The level of errorE correction used for data recovery is often can be selected.  However,sD many write-once devices have a minimum level that is always used andA cannot be de-selected through the error recovery mode parameter. eE Control of the error correction algorithms and level of correction is= vendor-specific.  D Defect management on write-once devices is usually vendor-specific. D However, there are standards for some types of write-once media thatB specify defect management techniques.  These standards, where theyB exist, may supersede the implementation requirements pertaining to: error and defect reporting in this International Standard.   13.1.4 Error reporting  B If any of the following conditions occur during the execution of a< command the target shall return CHECK CONDITION status.  TheC appropriate sense key and additional sense code should be set.  The-C following list illustrates some error conditions and the applicable G sense keys.  The list does not provide an exhaustive enumeration of all 5 conditions that may cause the CHECK CONDITION status.   b Condition                                                                                Sense Keyn Invalid logical block address                                                                          ILLEGAL REQUEST   j Unsupported option requested                                                                       ILLEGAL REQUEST   { Target reset or medium change since last command from this initiator                                                       =    UNIT ATTENTIONS  o Self diagnostic failed                                                                                 HARDWARE  ERROR   o Unrecovered read error                                                                             MEDIUM ERROR=`                                                                                   HARDWARE ERROR  o Recovered read error                                                                            RECOVERED ERROR=  z Overrun or other error that might be resolved by repeating the command                                                     ABORTED command-  q Attempt to write on write protected medium                                                                   DATAe PROTECT   t Attempt to read a blank or previously unwritten block                                                                BLANK CHECK   A Attempt to write a previously written block and blank checking is  enabled          BLANK CHECK    ? In the case of an invalid logical block address, the sense datarB information field shall be set to the logical block address of the first invalid address.  A In the case of an attempt to read a blank or previously unwritten C block, the sense data information field shall be set to the logical-E block address of the first blank block encountered.  The data read up # to that block shall be transferred.   G In the case of an attempt to write a previously written block and blank=D checking is enabled, the sense information field shall be set to the? logical block address of the first non-blank block encountered.o  $ 13.2 Commands for write-once devices  C The commands for write-once devices shall be as shown in table 235.i  <                  Table 235 - Commands for write-once devicesH +=====================================-============-======-============+H |  Command name                       | Operation  | Type |  Subclause |H |                                     |   code     |      |            |H |-------------------------------------+------------+------+------------|H | CHANGE DEFINITION                   |    40h     |   O  |   8.2.1    |H | COMPARE                             |    39h     |   O  |   8.2.2    |H | COPY                                |    18h     |   O  |   8.2.3    |H | COPY AND VERIFY                     |    3Ah     |   O  |   8.2.4    |H | INQUIRY                             |    12h     |   M  |   8.2.5    |H | LOCK UNLOCK CACHE                   |    36h     |   O  |   9.2.2    |H | LOG SELECT                          |    4Ch     |   O  |   8.2.6    |H | LOG SENSE                           |    4Dh     |   O  |   8.2.7    |H | MEDIUM SCAN                         |    38h     |   O  |  16.2.3    |H | MODE SELECT(6)                      |    15h     |   O  |   8.2.8    |H | MODE SELECT(10)                     |    55h     |   O  |   8.2.9    |H | MODE SENSE(6)                       |    1Ah     |   O  |   8.2.10   |H | MODE SENSE(10)                      |    5Ah     |   O  |   8.2.11   |H | PRE-FETCH                           |    34h     |   O  |   9.2.3    |H | PREVENT ALLOW MEDIUM REMOVAL        |    1Eh     |   O  |   9.2.4    |H | READ(6)                             |    08h     |   O  |   9.2.5    |H | READ(10)                            |    28h     |   M  |   9.2.6    |H | READ(12)                            |    A8h     |   O  |  16.2.4    |H | READ BUFFER                         |    3Ch     |   O  |   8.2.12   |H | READ CAPACITY                       |    25h     |   M  |   9.2.7    |H | READ LONG                           |    3Eh     |   O  |   9.2.9    |H | REASSIGN BLOCKS                     |    07h     |   O  |   9.2.10   |H | RECEIVE DIAGNOSTIC RESULTS          |    1Ch     |   O  |   8.2.13   |H | RELEASE                             |    17h     |   M  |   9.2.11   |H | REQUEST SENSE                       |    03h     |   M  |   8.2.14   |H | RESERVE                             |    16h     |   M  |   9.2.12   |H | REZERO UNIT                         |    01h     |   O  |   9.2.13   |H | SEARCH DATA EQUAL(10)               |    31h     |   O  |   9.2.14.1 |H | SEARCH DATA EQUAL(12)               |    B1h     |   O  |  16.2.8    |H | SEARCH DATA HIGH(10)                |    30h     |   O  |   9.2.14.2 |H | SEARCH DATA HIGH(12)                |    B0h     |   O  |  16.2.8    |H | SEARCH DATA LOW(10)                 |    32h     |   O  |   9.2.14.3 |H | SEARCH DATA LOW(12)                 |    B2h     |   O  |  16.2.8    |H | SEEK(6)                             |    0Bh     |   O  |   9.2.15   |H | SEEK(10)                            |    2Bh     |   O  |   9.2.15   |H | SEND DIAGNOSTIC                     |    1Dh     |   M  |   8.2.15   |H | SET LIMITS(10)                      |    33h     |   O  |   9.2.16   |H | SET LIMITS(12)                      |    B3h     |   O  |  16.2.9    |H | START STOP UNIT                     |    1Bh     |   O  |   9.2.17   |H | SYNCHRONIZE CACHE                   |    35h     |   O  |   9.2.18   |H | TEST UNIT READY                     |    00h     |   M  |   8.2.16   |H | VERIFY(10)                          |    2Fh     |   O  |  16.2.11   |H | VERIFY(12)                          |    AFh     |   O  |  16.2.12   |H | WRITE(6)                            |    0Ah     |   O  |   9.2.20   |H | WRITE(10)                           |    2Ah     |   M  |   9.2.21   |H | WRITE(12)                           |    AAh     |   O  |  16.2.14   |H | WRITE AND VERIFY(10)                |    2Eh     |   O  |   9.2.22   |H | WRITE AND VERIFY(12)                |    AEh     |   O  |  16.2.16   |H | WRITE BUFFER                        |    3Bh     |   O  |   8.2.17   |H | WRITE LONG                          |    3Fh     |   O  |   9.2.23   |H |----------------------------------------------------------------------|H |Key:  M = command implementation is mandatory.                        |H |      O = command implementation is optional.                         |H +======================================================================+    E The following command codes are vendor-specific:  02h, 05h, 06h, 09h,=E 0Ch, 0Dh, 0Eh, 0Fh, 10h, 11h, 13h, 14h, 19h, 20h, 21h, 22h, 23h, 24h,eD 26h, 27h, 29h, and C0h through FFh.  All remaining command codes for; write-once devices are reserved for future standardization.s  & 13.3 Parameters for write-once devices  > Refer to the parameters for optical memory devices (see 16.3).  / 13.4 Definitions specific to write-once devicest  	 See 16.4.m     14 CD-ROM devices      14.1 Model for CD-ROM deviceso  F CD-ROM devices permit reading data from a rotating media.  Writing the@ media is not supported.  Data transfer can begin with any of theB consecutively numbered logical blocks.  Data on CD-ROM devices areF addressed the same as usual (magnetic) direct-access devices. Some CD-D ROM devices support a separate information stream (e.g. audio and/or@ video but referred to as audio in this clause) transmitted via aE connection other than the SCSI Bus. This device type defines commandse1 for controlling these other information streams. h  F CD-ROM drives are designed to work with any disc that meets IEC.  ManyB new drives read CD-ROM data discs, digital audio discs, and audio-B combined discs (i.e. some tracks are audio, some tracks are data).    14.1.1 CD-ROM media organization  A The formats written on the CD-ROM and CD-DA (Digital Audio) medial, require special interfacing considerations.   G    NOTE 169 This subclause contains a number of terms that have specialBK    meanings peculiar to CD-ROM technology or that may be unfamiliar to manysK    readers of this International Standard. The glossary (see 14.4.) definese    these terms.e  D Discs may contain either audio, data or a mixture of the two.  TableD 236 gives an example of a of a audio-combined disc to illustrate theE relationship between the logical block addresses reported in SCSI anddE the MSF address encoded on the media.  The logical addresses given inuD the table assume a block length of 2 048, 2 336 or 2 340 bytes.  ForC block lengths of 1 024, 512 or 256 multiply all values given in the / SCSI address columns by 2, 4 or 8 respectively.   L    NOTE 170 The term frame is used in two different ways in the CD-ROM mediaK    standard.  The intended meaning can only be determined from the context.tM    Whenever possible, this description replaces the larger data unit with thesJ    more familiar term sector.  The primary exception to this policy is theK    use of frame when referring to the MSF address.  In the MSF context, oneaJ    frame (F field unit) equals one sector.  On a typical two channel CD-DAD    media, each frame (F field unit) is played in 1/75th of a second.    ?               Table 236 - Example mixed mode CD-ROM disc layoutti +================-==========================-===========================================================+ei |                |      SCSI address        |       /--- Sub-channel information ----\                  | i |----------------+--------------------------+-----------------------------------------------------------| i |                |  Logical    |   Track    |    Absolute  |  Track |  Track    |Sector  | Mode  |CD-ROM| i |                |  address    |  relative  |      MSF     |   and  | relative  |is info | audio |data  |ri |     Block      |  (decimal)  |  logical   |    address1  |  index |   MSF     | or is  |  or   |mode2 | i |  description   |             |  address   |              |        | address   | pause  | data  |      |ni |----------------+-------------+------------+--------------+--------+-----------+--------+-------+------|ai |Lead-in area3)  |      ---    |    ---     |     ---      |  0/-   |    ---    |  ---   | Audio | ---  | i |Pre-gap3)       |     ---     |    ---     |  00/00/00    |  1/0   | 00/02/00  | Pause  | Data  | Null | i |                |             |            |              |        |           |        |       |      |pi |1st track data  |   0 0005)   |       0    |  00/02/004)  |  1/1   | 00/00/00  | Info   | Data  | L-EC |ai |2nd track data  |   6 0005)   |       0    |  01/22/004)  |  2/1   | 00/00/00  | Info   | Data  | L-EC | i |                |   7 500     |   1 500    |  01/42/00    |  2/2   | 00/20/00  | Info   | Data  | L-EC | i |                |             |            |              |        |           |        |       |      | i |Post-gap        |   9 000     |   3 000    |  02/02/00    |  2/3   | 00/40/00  | Pause  | Data  | Null | i |                |             |            |              |        |           |        |       |      | i |Pause-silence   |   9 150     |    -1509)  |  02/04/00    |  3/0   | 00/02/008 | Pause  | Audio | ---  |yi |                |             |            |              |        |           |        |       |      |wi |3rd track audio |   9 3007)   |       0    |  02/04/006)  |  3/1   | 00/00/00  | Info   | Audio | ---  |Ti |                |  11 400     |   2 250    |  02/34/00    |  3/2   | 00/30/00  | Info   | Audio | ---  | i |4th track audio |  21 9757)   |       0    |  04/53/006)  |  4/1   | 00/00/00  | Info   | Audio | ---  |ei |                |             |            |              |        |           |        |       |      |ii |Pre-gap part 1  |  30 000     |    -2259)  |  06/40/00    |  5/0   | 00/03/00  | Pause  | Audio | ---  |oi |Pre-gap part 2  |  30 075     |    -150    |  06/41/00    |  5/0   | 00/02/00  | Pause  | Data  | Null |-i |                |             |            |              |        |           |        |       |      |di |5th track data  |  30 225     |       0    |  06/43/00    |  5/1   | 00/00/00  | Info   | Data  | L-EC |ni |                |             |            |              |        |           |        |       |      | i |Last information| 263 99910)  | 233 774    |  58/39/74    |  5/1   | 51/56/74  | Info   | Data  | L-EC |5i |                |             |            |              |        |           |        |       |      |=i |Post-gap        |     ---     | 233 775    |  58/40/00    |  5/2   | 51/57/00  | Pause  | Data  | Null | i |                |             |            |              |        |           |        |       |      |-i |Lead-out track  | 264 00011)  |       0    |  58/42/0012) | AA/13  | 00/00/00  | Pause  | Audio | ---  | i |-------------------------------------------------------------------------------------------------------| i |  Notes                                                                                                | i |  1  Absolute MSF address repeated in the header field of data blocks.                                 | i |  2  The CD-ROM data mode is stored in the header of data tracks. This indicates that                  |Oi |     the block is part of a data pre-gap or post-gap (null), that this is a data                       | i |     block using the auxiliary field for L-EC symbols (ECC - CD-ROM data mode one),                    | i |     or that this is a data block using the auxiliary field for user data (CD-ROM                      |Ni |     data mode two).                                                                                   |5i |  3  Table of contents information is stored in the sub-channel of lead-in area.  The                  |Ri |     lead-in area is coded as track zero. Track zero and the initial 150 sector pre-                   | i |     -gap (or audio pause) are not accessible with logical addressing.                                 ||i |  4  Value stored in table of contents with zero tolerance.                                            | i |  5  Exact value returned by READ TOC command.                                                         |.i |  6  Value stored in table of contents plus or minus 75 sectors.                                       | i |  7  Value returned by READ TOC command plus or minus 75 blocks.                                       | i |  8  Track relative MSF value decreases to 0 in pre-gap areas.                                         | i |  9  Track relative logical addresses are negative in the pre-gap areas.                               | i |     Pre-gap areas have index values of zero.                                                          | i |  10  Minimum value returned by READ CD-ROM CAPACITY - exact value depends                             | i |      on encoding of this track and the lead out track and whether this is                             |Hi |      derived from the TOC data.                                                                       | i |  11  Value returned by READ TOC command - exact if lead-out track is                                  | i |      encoded as data, or plus or minus 75 blocks if encoded as audio.                                 | i |  12  Value stored in table of contents -  exact if lead-out track is coded                            | i |      as data, or plus or minus 75 blocks if coded as audio.                                           | i |  13  Lead-out track number is defined as 0AAh.                                                        |.i +=======================================================================================================+     D The physical format defined by the CD-ROM media standards provides 2G 352 bytes per sector. For usual computer data applications, 2 048 bytes E are used for user data, 12 bytes for a synchronization field, 4 bytes D for a sector address tag field and 288 bytes - the auxiliary field -A for L-EC (CD-ROM data mode 1). In less critical applications, the F auxiliary field may also be used for user data (CD-ROM data mode 2). AF CD-ROM physical sector size is 2 048, 2 336 or 2 340 bytes per sector.? These values correspond to user data field only, user data plus D auxiliary data, the 4 byte address tag plus user data plus auxiliary data.R  G Selection among these options is made by setting the density code field-G of the MODE SELECT block descriptor. The usual selection is 2 048 bytes E per physical sector via a density code setting of 1. See the table of % CD-ROM density code values in 14.3.3.a  D This same area of the CD-ROM or CD audio media may store 1/75th of aF second of two channel audio information formatted according to the CD-F DA specification. (These audio channels are usually the left and rightE components of a stereo pair.) An audio only density code value can be G used to declare an area of the media to be invalid for data operations.u    B For data and mixed mode media (those conforming to ISO/IEC 10149),@ logical block address zero shall be assigned to the block at MSFF address 00/02/00.  For audio media (those conforming only to IEC 908),D logical block address zero should be assigned to the actual startingC address of track 1.  This may be approximated by using the startingtA address of track 1 contained in the table of contents (TOC) or byd@ assigning logical block address zero to the block at MSF address	 00/02/00.g  B Logical addressing of CD-ROM information may use any logical blockF length. When the specified logical block length is an exact divisor orD integral multiple of the selected number of bytes per CD-ROM sector,C the device shall map (one to one) the bytes transferred from CD-ROMmE sectors to the bytes of logical blocks.  For instance, if 2 048 bytesa@ are transferred from each CD-ROM sector (specified by the CD-ROMD density code value), and the logical block length is 512 bytes, thenB each CD-ROM sector shall map to exactly four logical blocks.  ThisC International Standard does not define the mapping of logical blockcD lengths which do not evenly divide or are not exact multiples of the+ selected number of bytes per CD-ROM sector.a  G A track may be viewed as a partition of the CD-ROM address space. A CD-rC ROM media contains from one to ninety-nine tracks.  All informationeF sectors of a track are required to be of the same type (audio or data)F and mode.  Each change in the type of information on the disc requiresF a change in track number.  A disc containing both audio and data would; have at least two tracks, one for audio and one for data.  e  G The tracks of a CD media are numbered consecutively with values between3@ 1 and 99. However, the first information track may have a numberE greater than 1. Tracks have a minimum length of 300 sectors includinge] any transition area that is part of a e used at the beginning or end of any track.  For audiorE tracks the transition areas are called pause areas.  For data tracks,WF transition areas are called pre-gap and post-gap areas.  See table 236@ for an example.  The IEC 908 and ISO/IEC 10149 standards specifyG minimum time durations for these areas.  Maximum time durations are notM specified. n  C Transition areas are formatted and the logical address continues tolE increment through transition areas.  Some media (i.e. discs with onlycE one track) may not have transition areas.  The means to determine theuF location of the transition areas is vendor or application-specific and0 is addressed by other standards (e.g. ISO 9660).  F CD-ROM is a unique SCSI device in the respect that some logical blocksF on a disc may not be accessible by all commands.  SEEK commands may beG issued to any logical block address within the reported capacity of the E disc.  READ commands cannot be issued to logical blocks that occur inoC some transition areas, or to logical blocks within an audio track.  G PLAY commands cannot be issued to logical blocks within a data track.       E The blank verify (BlkVfy) option of the verify command (see 16.2.11),|> for CD-ROM devices, shall verify that the addressed blocks are transition area blocks.d  F CD-ROM media have lead-in and lead-out areas.  These areas are outsideC of the user-accessible area as reported in the READ CD-ROM CAPACITY C data.  The lead-in area of the media is designated track zero.  The G lead-out area is designated track 0AAh.  The sub-channel Q in the lead- 8 in track contains a table of contents (TOC) of the disc.  F    NOTE 171 The READ CD-ROM CAPACITY command returns the logical blockM    address of the last block prior to the lead-out area. This location may be|B    in a transition area and therefore not a valid address for read    operations. k  B The table of contents gives the absolute MSF location of the firstC information sector of each track.  Control information (audio/data, C method of audio encoding, etc.) for each track is also given in the G TOC.  However, the TOC does not distinguish between the different modes F of data tracks (i.e. CD-ROM data mode one vs. CD-ROM data mode two).    @ The MSF locations of the beginning of data tracks in the TOC areF required to be accurate, however, the TOC values for audio tracks haveE a tolerance of plus or minus 75 sectors. Information from the TOC can1G be used to reply to a READ CD-ROM CAPACITY command.  When this is done, A the drive implementor should consider the possible tolerances and = return a value that allows access to all information sectors.)  F An index is a partition of a track.  Pre-gap areas are encoded with anF index value of zero.  Pause areas at the beginning of audio tracks areG also encoded with an index value of zero.  The first information sector|F of a track has an index value of one.  Consecutive values up to 99 areC permitted.  Index information is not contained in the TOC.  Not all G sectors are encoded with the index value in the Q-sub-channel data (the|@ requirement is 9 out of 10).  A sector without an index value is8 presumed to have the same index as the preceding sector.  G Tracks and indexes are not defined to be any particular length, (except E for a minimum track length of 300 sectors.)  A CD disc may be created C with a single information track that has a single index; or with 99/) information tracks, each with 99 indexes.t  C The sub-channel information which is part of each sector includes a D track relative MSF location value giving the distance from the firstC information sector of the track. On the media, this value decreases|F during the pre-gap area (sectors with index values of 0) and increasesE for the rest of the track. The data, returned by the READ SUB-CHANNEL|C command with MSF bit set to zero, converts this to a track relative G logical block address (TRLBA). The TRLBA is continually increasing over E the whole track, and pre-gap areas shall return negative values. When|B the MSF bit in the read sub-channel command is set to one, the MSF@ track relative location value from the media is reported without change.-  " 14.1.2 CD-ROM physical data format  D The physical format of CD-ROM and CD-DA media uses a smaller unit ofD synchronization than the more familiar magnetic or optical recordingF systems. The basic data stream synchronization unit is a small frame. C This is not the same large frame (sector) as referred to in the MSFoG unit.  Each small frame consists of 588 bits.  A sector on CD-ROM medias consists of 98 small frames.  ! A CD-ROM small frame consists of: L    a)     1      synchronization pattern                         (24+3 bits)H    b)     1      byte of sub-channel data                    (14+3 bits)L    c)     24     bytes of data                            (24 x (14+3) bits)j    d)     8      bytes of CIRC code                       (8 x (14+3) bits)                     Total: 588           bits.l  F Data, sub-channel and CIRC bytes are encoded with an eight-to-fourteenB bit code; then three merging bits are added.  The merging bits areC chosen to provide minimum low-frequency signal content and optimize  phase lock loop performance. c   14.1.2.1 Frame format for audio   C Each small frame of an audio track on a two-channel CD-DA or CD-ROMtE media consists of six digitized 16-bit samples of each audio channel. C These 24 bytes of data are combined with a synchronization pattern, C CIRC bytes and a sub-channel byte to make a frame. Each frame takesnG approximately 136.05 uS to play. This gives a sampling rate of 44,1 khz F for each channel. The sub-channel information creates the higher level! sector grouping for audio tracks.    14.1.2.2 Sector format for datae  D The data bytes of 98 small frames comprise the physical unit of dataC referred to as a sector.  (98 small frames times 24 bytes per smalle/ frame equal 2 352 bytes of data per sector.)   a  B A sector that contains CD-ROM data mode one data has the following format:   )    a)   12 bytes    Synchronization field )    b)   4 bytes     CD-ROM data header   d5                       Absolute M field in bcd format  4                       Absolute S field in bcd format5                       Absolute F field in bcd format  .                       CD-ROM data mode field  6    c)   2048 bytes                User data field     3    d)    4 bytes               Error detection code 3    e)    8 bytes               Zero                a<    f)  276 bytes               Layered error correction code    B A sector that contains CD-ROM Data Mode two data has the following format:a  *    a)  12 bytes      Synchronization field)    b)  4 bytes       CD-ROM data header  l4                       Absolute M field in bcd format4                       Absolute S field in bcd format4                       Absolute F field in bcd format,                       CD-ROM data mode fieldO    c)  2 336 bytes                User data field (2048 bytes of mode 1 data    >                       plus 288 bytes of auxiliary data)           M    NOTE 172 Many drives are capable of returning CD-ROM data mode one data in J    a CD-ROM data mode two format.  This allows the user to investigate theK    error detection and error correction codes.  However data encoded as CD-MA    ROM data mode two cannot be read as CD-ROM data mode one data.   ( 14.1.2.3 Sub-channel information formats  F The sub-channel byte of each frame is assigned one bit for each of theG 8 sub-channels, designated P, Q, R, S, T, U, V, W.  Only sub-channels P C and Q are defined for CD-ROM media.  The other sub-channel bits arey zero.R  D Sub-channel P is a simple flag bit that may be used for audio muting* control and track boundary determination.   D Sub-channel Q has a higher level of structure. All the sub-channel QB bits of a sector define the sub-channel Q information block.  (ForG audio tracks, decoding the Q sub-channel is the only way to distinguish  sector boundaries.)   D The sub-channel Q block consists of 98 bits, one bit from each smallC frame in a sector.  Three formats are defined for the sub-channel Q E information block. The first format provides location information andr is defined as follows:  <    a)     2 bits           Sub-channel synchronization field:    b)     4 bits           ADR field - defines the format =    c)     4 bits           Control field - defines the type  /0                    of information in this sector0    d)     8 bits           Track number (in BCD)0    e)     8 bits           Index number (in BCD)5    f)     24 bits          Track relative MSF address 2    g)     8 bits           Reserved (0)           0    h)     24 bits          Absolute MSF address 4    i)     16 bits          CRC error detection code   < This format is required to exist in at least nine out of ten consecutive sectors. b  G The second and third formats are optional.  If used, they must exist inrG at least one out of 100 consecutive sectors.  They include the absolute = frame byte of the MSF address to provide location informations continuity.c  E The second format gives the catalogue number of the disc (UPC/EAN bar B code number).  This information is constant over the whole media.   G The third format gives the International Standard Recording Code (ISRC) E for each track.  The ISRC is defined in ISO 3901.  This format is notcC present on lead-in or lead-out tracks and may change only after thet track number changes.b   14.1.3 CD Audio error reporting   C PLAY AUDIO commands with the immediate bit set in the audio controleG mode return status as soon as the command has been validated (which mayf? involve a seek to the starting address). The playback operation B continues and may complete without notification to the initiator. > Error termination of audio operations shall be reported to theC initiator by returning immediate CHECK CONDITION status to the next C command (except for REQUEST SENSE and INQUIRY.)  The deferred errorwD sense data (see 8.2.14.2.) is used to indicate that the error is not due to the current command.   G The status of the play operation may be determined by issuing a REQUESTtE SENSE command.  The sense key is set to NO SENSE and the audio statustG (see 14.2.10) is reported in the additional sense code qualifier field.n  1 14.1.4 CD-ROM ready condition/not ready conditionb  F The ready condition occurs after a cartridge is inserted and the driveF has performed its initialization tasks.  These may include reading the! table of contents from the media.a  < A not ready condition may occur for the following reasons:  )    a)     There is no cartridge inserted.i>    b)     The drive is unable to load or unload the cartridge.?    c)     The drive is unable to recover the table of contents.r3    d)     The controller cannot select the drive.  t  1 14.1.5 CD-ROM address reporting formats (MSF bit)e  G Several CD-ROM specific commands can report addresses either in logicallD or in MSF format (see table 237).  The READ HEADER, READ SUB-CHANNEL6 and READ TABLE OF CONTENTS commands have this feature.  6                         Table 237 - MSF address formatO +=====-========-========-========-========-========-========-========-========+mO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |eO |Byte |        |        |        |        |        |        |        |        |hO |=====+=======================================================================|aO | 0   |                           Reserved                                    |eO |-----+-----------------------------------------------------------------------|dO | 1   |                           M field                                     |sO |-----+-----------------------------------------------------------------------|sO | 2   |                           S field                                     |aO |-----+-----------------------------------------------------------------------| O | 3   |                           F field                                     | O +=============================================================================+e  D An MSF bit of zero requests that the logical block address format beE used for the CD-ROM absolute address field or for the offset from theeF beginning of the current track expressed as a number of logical blocksF in a CD-ROM track relative address field.  This track relative logicalD block address (TRLBA) value is reported as a negative value in twos-A complement notation for transition areas that have decreasing MSFf encoded relative addresses.f  @ An MSF bit of one requests that the MSF format be used for theseD fields.  In certain transition areas, the relative MSF addresses areB decreasing positive values.  The absolute MSF addresses are always/ increasing positive values (see entry in 14.4).t  C The M, S, and F fields are expressed as binary numbers.  The values.C match those on the media, except for the encoding.  The ratios of M C field units to S field units and S field units to F field units ares2 reported in the mode parameters page (see 14.3.3).  - 14.1.6 Sensing support for CD-audio commands.n  E If any commands related to audio operations are implemented, then the A PLAY AUDIO command shall be implemented to allow a method for thetC initiator to determine if audio operations are supported.  A targetiG responding to a PLAY AUDIO command which has a transfer length of zero,gA with CHECK CONDITION status, and setting the sense key to ILLEGALc0 REQUEST does not support audio play operations.   M    NOTE 173 The PLAY AUDIO command may be implemented without support for any +    of the other audio operations commands. f   14.1.7 Error reporting  B If any of the following conditions occur during the execution of a= command, the target shall return CHECK CONDITION status.  TheaC appropriate sense key and additional sense code should be set.  ThecC following list illustrates some error conditions and the applicable-G sense keys.  The list does not provide an exhaustive enumeration of allt5 conditions that may cause the CHECK CONDITION status.n  b Condition                                                                                Sense Keyn Invalid logical block address                                                                          ILLEGALn                                                                                                        REQUEST  j Unsupported option requested                                                                       ILLEGALj                                                                                                    REQUEST  { Target reset or medium change since last command from this initiator                                                       D    UNIT ATTENTIONn  o Self diagnostic failed                                                                                 HARDWAREsl                                                                                                        ERROR  o Unrecovered read error                                                                             MEDIUM ERRORa`                                                                                   HARDWARE ERROR  o Recovered read error                                                                            RECOVERED ERRORl  z Overrun or other error that might be resolved by repeating the command                                                     ABORTED commande  r Attempt to read a blank block                                                                          BLANK CHECK  o Attempt to play a data block as audio                                                                     BLANKpo                                                                                                           CHECKt    ? In the case of an invalid logical block address, the sense data4B information field shall be set to the logical block address of the first invalid address.  A In the case of an attempt to read a blank or previously unwritten C block, the sense data information field shall be set to the logicaltE block address of the first blank block encountered.  The data read up # to that block shall be transferred.   C There are other special error situations for CD-ROM devices. In the A following cases the sense key shall be set to BLANK CHECK and theSA additional sense code set to END OF USER AREA ENCOUNTERED ON THIS  TRACK:  G    a)     a post-gap area is encountered (i.e. a block with CD-ROM Data            Mode 0);I    b)     a pre-gap area is encountered (i.e. a block with index equal tob
           0); 9    c)     The information type (data vs. audio) changes. y  @ When not performing audio playback, if the logical block addressE requested is not within a data track, the command shall be terminatedoG with CHECK CONDITION status.  The sense key shall be set to BLANK CHECK G and the additional sense code set to ILLEGAL MODE FOR THIS TRACK.  Thisf- applies to audio-combined and audio media.   u    14.2 Commands for CD-ROM devices  ? The commands for CD-ROM devices shall be as shown in table 238.   :                     Table 238 - Commands for CD-ROM deviceH +=====================================-============-======-============+H |  Command name                       | Operation  | Type |  Subclause |H |                                     |   code     |      |            |H |-------------------------------------+------------+------+------------|H | CHANGE DEFINITION                   |    40h     |   O  |   8.2.1    |H | COMPARE                             |    39h     |   O  |   8.2.2    |H | COPY                                |    18h     |   O  |   8.2.3    |H | COPY AND VERIFY                     |    3Ah     |   O  |   8.2.4    |H | INQUIRY                             |    12h     |   M  |   8.2.5    |H | LOCK/UNLOCK CACHE                   |    36h     |   O  |   9.2.2    |H | LOG SELECT                          |    4Ch     |   O  |   8.2.6    |H | LOG SENSE                           |    4Dh     |   O  |   8.2.7    |H | MODE SELECT(6)                      |    15h     |   O  |   8.2.8    |H | MODE SELECT(10)                     |    55h     |   O  |   8.2.9    |H | MODE SENSE(6)                       |    1Ah     |   O  |   8.2.10   |H | MODE SENSE(10)                      |    5Ah     |   O  |   8.2.11   |H | PAUSE/RESUME                        |    4Bh     |   O  |  14.2.1    |H | PLAY AUDIO(10)                      |    45h     |   O* |  14.2.2    |H | PLAY AUDIO(12)                      |    A5h     |   O* |  14.2.3    |H | PLAY AUDIO MSF                      |    47h     |   O* |  14.2.4    |H | PLAY AUDIO TRACK/INDEX              |    48h     |   O* |  14.2.5    |H | PLAY TRACK RELATIVE(10)             |    49h     |   O* |  14.2.6    |H | PLAY TRACK RELATIVE(12)             |    A9h     |   O* |  14.2.7    |H | PRE-FETCH                           |    34h     |   O  |   9.2.3    |H | PREVENT/ALLOW MEDIUM REMOVAL        |    1Eh     |   O  |   9.2.4    |H | READ(6)                             |    08h     |   O  |   9.2.5    |H | READ(10)                            |    28h     |   M  |   9.2.6    |H | READ(12)                            |    A8h     |   O  |  16.2.4    |H | READ BUFFER                         |    3Ch     |   O  |   8.2.12   |H | READ CD-ROM CAPACITY                |    25h     |   M  |  14.2.8    |H | READ HEADER                         |    44h     |   O  |  14.2.9    |H | READ LONG                           |    3Eh     |   O  |   9.2.9    |H | READ SUB-CHANNEL                    |    42h     |   O  |  14.2.10   |H | READ TOC                            |    43h     |   O  |  14.2.11   |H | RECEIVE DIAGNOSTIC RESULTS          |    1Ch     |   O  |   8.2.13   |H | RELEASE                             |    17h     |   M  |   9.2.11   |H | REQUEST SENSE                       |    03h     |   M  |   8.2.14   |H | RESERVE                             |    16h     |   M  |   9.2.12   |H | REZERO UNIT                         |    01h     |   O  |   9.2.13   |H | SEARCH DATA EQUAL(10)               |    31h     |   O  |   9.2.14.1 |H | SEARCH DATA EQUAL(12)               |    B1h     |   O  |  16.2.8    |H | SEARCH DATA HIGH(10)                |    30h     |   O  |   9.2.14.2 |H | SEARCH DATA HIGH(12)                |    B0h     |   O  |  16.2.8    |H | SEARCH DATA LOW(10)                 |    32h     |   O  |   9.2.14.3 |H | SEARCH DATA LOW(12)                 |    B2h     |   O  |  16.2.8    |H | SEEK(6)                             |    0Bh     |   O  |   9.2.15   |H | SEEK(10)                            |    2Bh     |   O  |   9.2.15   |H | SEND DIAGNOSTIC                     |    1Dh     |   M  |   8.2.15   |H | SET LIMITS(10)                      |    33h     |   O  |   9.2.16   |H | SET LIMITS(12)                      |    B3h     |   O  |  16.2.9    |H | START STOP UNIT                     |    1Bh     |   O  |   9.2.17   |H | SYNCHRONIZE CACHE                   |    35h     |   O  |   9.2.18   |H | TEST UNIT READY                     |    00h     |   M  |   8.2.16   |H | VERIFY(10)                          |    2Fh     |   O  |  16.2.11   |H | VERIFY(12)                          |    Afh     |   O  |  16.2.12   |H | WRITE BUFFER                        |    3Bh     |   O  |   8.2.17   |H |----------------------------------------------------------------------|H |Key:  M = command implementation is mandatory.                        |H |      O = command implementation is optional.                         |H |      * = indicates a PLAY AUDIO command                              |H +======================================================================+    E The following command codes are vendor-specific:  02h, 05h, 06h, 09h,-E 0Ch, 0Dh, 0Eh, 0Fh, 10h, 11h, 13h, 14h, 19h, 20h, 21h, 22h, 23h, 24h, D 26h, 27h, 29h, and C0h through FFh.  All remaining command codes for7 CD-ROM devices are reserved for future standardization.-  @ If any of the PLAY AUDIO commands (indicated by an * in the typeG column) are implemented, the PLAY AUDIO command shall be implemented by- the target.    14.2.1 PAUSE RESUME command   F The PAUSE RESUME command (see table 239) requests that the device stopG or start an audio play operation.  This command is used with PLAY AUDIO=6 commands issued while the immediate bit is set to one.  7                        Table 239 - PAUSE RESUME commandeO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |tO |=====+=======================================================================| O | 0   |                           Operation code (4Bh)                        |rO |-----+-----------------------------------------------------------------------|rO | 1   | Logical unit number      |                     Reserved               |vO |-----+-----------------------------------------------------------------------|nO | 2   |                           Reserved                                    |iO |-----+-----------------------------------------------------------------------|eO | 3   |                           Reserved                                    |-O |-----+-----------------------------------------------------------------------|tO | 4   |                           Reserved                                    |tO |-----+-----------------------------------------------------------------------| O | 5   |                           Reserved                                    |aO |-----+-----------------------------------------------------------------------|pO | 6   |                           Reserved                                    |rO |-----+-----------------------------------------------------------------------|gO | 7   |                           Reserved                                    |tO |-----+-----------------------------------------------------------------------|dO | 8   |                           Reserved                           | Resume |oO |-----+-----------------------------------------------------------------------|eO | 9   |                           Control                                     |oO +=============================================================================+     C A resume bit of zero causes the drive to enter the hold track state B with the audio output muted after the current block is played.   AF resume bit of one causes the drive to release the pause and begin play- at the block following the last block played.r  G If an audio play operation cannot be resumed and the resume bit is one, D the command is terminated with CHECK CONDITION status. If the resumeC bit is zero and an audio play operation cannot be paused, (no audioe> play operation has been requested, or the requested audio playC operation has been completed), the command is terminated with CHECKf CONDITION status.     F It shall not be considered an error to request a pause when a pause isE already in effect, or to request a resume when a play operation is in 	 progress.    14.2.2 PLAY AUDIO(10) commandE  E The PLAY AUDIO command (see table 240) requests that the target begin G an audio playback operation. The command function (Immed and SOTC bits) E and the output of audio signals shall be as specified by the settings ' of the mode parameters (see 14.3.3.1.).   8                       Table 240 - PLAY AUDIO(10) commandO +=====-========-========-========-========-========-========-========-========+mO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |eO |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================| O | 0   |                           Operation code (45h)                        | O |-----+-----------------------------------------------------------------------| O | 1   | Logical unit number      |             Reserved              | RelAdr |4O |-----+-----------------------------------------------------------------------|iO | 2   | (MSB)                                                                 | O |-----+---                                                                 ---|sO | 3   |                                                                       |eO |-----+---                 Starting logical block address                  ---| O | 4   |                                                                       |nO |-----+---                                                                 ---| O | 5   |                                                                  (LSB)| O |-----+-----------------------------------------------------------------------| O | 6   |                           Reserved                                    |pO |-----+-----------------------------------------------------------------------| O | 7   | (MSB)                                                                 |eO |-----+---                        Transfer length                          ---|LO | 8   |                                                                 (LSB) |4O |-----+-----------------------------------------------------------------------|wO | 9   |                           Control                                     |=O +=============================================================================+d    D If any commands related to audio operations are implemented then theA PLAY AUDIO command shall be implemented to allow a method for the-C initiator to determine if audio operations are supported.  A target E responding to a PLAY AUDIO command that has a transfer length of zero|@ with CHECK CONDITION status and setting the sense key to ILLEGAL0 REQUEST does not support audio play operations.   D The logical block address field specifies the logical block at which) the audio playback operation shall begin.R  D The transfer length field specifies the number of contiguous logicalF blocks that shall be played. A transfer length field of zero indicatesA that no audio operation shall occur.  This condition shall not be| considered an error.    G If the logical block length is not equal to the sector size, the target F may adjust the starting logical block address and the transfer length.D In such case, it is recommended that the target start the audio playF operation with the beginning of a sector whenever the starting logicalF address falls within that sector (MSF unit). If the requested transferA length causes the end of an audio play operation to fall within aAE sector, the target may continue the play operation through the end ofY that sector.  E If the starting address is not found, if the address is not within an E audio track, or if a not ready condition exists, the command shall beK( terminated with CHECK CONDITION status.   F If the CD-ROM information type (data vs. audio) changes, the sense keyG shall be set to BLANK CHECK and the additional sense code set to END OF % USER AREA ENCOUNTERED ON THIS TRACK.    D If the logical block address requested is not within an audio track,G the command shall be terminated with CHECK CONDITION status.  The sense D key shall be set to BLANK CHECK and the additional sense code set to ILLEGAL MODE FOR THIS TRACK.   14.2.3 PLAY AUDIO(12) command   F The PLAY AUDIO(12) command (see table 241) requests that the target toG begin an audio playback operation. The command function (Immed and SOTC-B bits) and the output of audio signals shall be as specified by theG settings of the mode parameters (see 14.3.3.1.). See the PLAY AUDIO(10)E8 command for a description of the fields in this command.  8                       Table 241 - PLAY AUDIO(12) commandO +=====-========-========-========-========-========-========-========-========+OO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |.O |Byte |        |        |        |        |        |        |        |        ||O |=====+=======================================================================|EO | 0   |                           Operation code (A5h)                        | O |-----+-----------------------------------------------------------------------|0O | 1   | Logical unit number      |               Reserved            | RelAdr | O |-----+-----------------------------------------------------------------------| O | 2   | (MSB)                                                                 |hO |-----+---                                                                 ---| O | 3   |                                                                       |1O |-----+---                      Logical block address                      ---| O | 4   |                                                                       |EO |-----+---                                                                 ---|SO | 5   |                                                                  (LSB)| O |-----+-----------------------------------------------------------------------| O | 6   | (MSB)                                                                 | O |-----+---                                                                 ---|0O | 7   |                                                                       ||O |-----+---                        Transfer length                          ---| O | 8   |                                                                       |7O |-----+---                                                                 ---|KO | 9   |                                                                 (LSB) |=O |-----+-----------------------------------------------------------------------|tO | 10  |                             Reserved                                  |=O |-----+-----------------------------------------------------------------------|rO | 11  |                           Control                                     | O +=============================================================================+g     14.2.4 PLAY AUDIO MSF commanda  F The PLAY AUDIO MSF command (see table 242) requests that the target toC begin an audio playback operation.  The command function (Immed and G SOTC bits) and the output of audio signals shall be as specified by theM0 settings of the mode parameters (see 14.3.3.1.).  8                       Table 242 - PLAY AUDIO MSF commandO +=====-========-========-========-========-========-========-========-========+iO |  Bit|        |   6    |   5    |   4    |   3    |   2    |   1    |   0    |eO |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================| O | 0   |                           Operation code (47h)                        |tO |-----+-----------------------------------------------------------------------| O | 1   | Logical unit number      |                  Reserved                  |rO |-----+-----------------------------------------------------------------------|rO | 2   |                           Reserved                                    |vO |-----+-----------------------------------------------------------------------|nO | 3   |                           Starting M field                            |iO |-----+-----------------------------------------------------------------------|eO | 4   |                           Starting S field                            |-O |-----+-----------------------------------------------------------------------|tO | 5   |                           Starting F field                            |tO |-----+-----------------------------------------------------------------------| O | 6   |                           Ending M field                              |aO |-----+-----------------------------------------------------------------------|pO | 7   |                           Ending S field                              |rO |-----+-----------------------------------------------------------------------|gO | 8   |                           Ending F field                              |tO |-----+-----------------------------------------------------------------------|dO | 9   |                           Control                                     |oO +=============================================================================+e    D The starting M field, the starting S field, and the starting F fieldB specify the absolute MSF address at which the audio play operationF shall begin.  The ending M field, the ending S field, and the ending FE field specify the absolute MSF address where the audio play operation E shall end.  All contiguous audio sectors between the starting and the # ending MSF address shall be played.l  E A starting MSF address equal to an ending MSF address causes no audiosD play operation to occur.  This shall not be considered an error.  IfA the starting MSF address is less than the ending MSF address, therG command shall be terminated with CHECK CONDITION status.  The sense key   shall be set to ILLEGAL REQUEST.  E If the starting address is not found, if the address is not within antE audio track, or if a not ready condition exists, the command shall be E terminated with CHECK CONDITION status.  See 14.1.7 for a descriptiont of error reporting information.P  % 14.2.5 PLAY AUDIO TRACK INDEX commandc  F The PLAY AUDIO TRACK INDEX command (see table 243) requests the targetF to begin an audio play operation. The command function (Immed and SOTCB bits) and the output of audio signals shall be as specified by the0 settings of the mode parameters (see 14.3.3.1.).  <                   Table 243 - PLAY AUDIO TRACK INDEX commandO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |=O |=====+=======================================================================| O | 0   |                           Operation code (48h)                        |-O |-----+-----------------------------------------------------------------------|mO | 1   | Logical unit number      |                  Reserved                  |-O |-----+-----------------------------------------------------------------------| O | 2   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------| O | 3   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------| O | 4   |                           Starting track                              | O |-----+-----------------------------------------------------------------------| O | 5   |                           Starting index                              |-O |-----+-----------------------------------------------------------------------| O | 6   |                           Reserved                                    |-O |-----+-----------------------------------------------------------------------| O | 7   |                           Ending track                                | O |-----+-----------------------------------------------------------------------| O | 8   |                           Ending index                                |-O |-----+-----------------------------------------------------------------------| O | 9   |                           Control                                     |=O +=============================================================================+a    C The starting track field specifies the track number of the startinglA audio track.  The starting index field specifies the index numberiA within the track at which the audio play operation shall begin.  A  E The ending track field specifies the track number of the ending audioaD track.  The ending index field specifies the index number within theF track after which the audio play operation shall stop.  The audio playF operation shall terminate at the last block with an index number equalF to the ending index. All contiguous audio sectors between the starting' and the ending address shall be played.f  D If the starting address is less than the ending address, the commandE shall be terminated with CHECK CONDITION status.  The sense key shallt be set to ILLEGAL REQUEST.  E If the starting address is not found, or if the address is not within E an audio track, or if a not ready condition exists, the command shall < be terminated with CHECK CONDITION status.  See 14.1.7 for a+ description of error reporting information.n  F    NOTE 174 Valid values for the track and index fields are 1 to 99. AK    starting index value of one specifies that playback is to start with the J    first audio sector of the track following the (optional) pause.  A lastG    index value of 99 specifies that playback continues through the lastn    sector of the track.   E If the ending track is greater than the last information track on theeE media, the playback shall continue until the last track is complete.  B If the ending index is greater than the largest index value on theG ending track, the playback shall continue until this track is complete;qA then terminate.  These conditions shall not be considered errors.e  D If the starting index is greater than the largest index value on theF starting track, and the stop on track crossing (SOTC) bit of the audio? control MODE SELECT parameters page (see 14.3.3.1) is zero, theeC playback operation shall start at the beginning of the next track. r This situation is not an error.d  D If the starting index is greater than the largest index value on theF starting track, and the stop on track crossing (SOTC) bit of the audioG control MODE SELECT parameters page (see 14.3.3.1) is one, the playback G shall not begin. The target shall return CHECK CONDITION, and the sense=$ key shall be set to ILLEGAL REQUEST.  M    NOTE 175 The operation of the SOTC bit described above comes about because L    the user may not be able to determine the largest index value on a track,M    either from the table of contents or by other means. The SOTC bit one case=I    allows the user to determine the largest index. The SOTC bit zero caseoJ    allows the user to set up play operations without complete knowledge of    the media layout. -  , 14.2.6 PLAY AUDIO TRACK RELATIVE(10) command  G The PLAY AUDIO TRACK RELATIVE(10) command (see table 244) requests that-F the device begin an audio playback operation.  The starting address is> specified as a track relative logical block address within theD specified starting track. The command function (Immed and SOTC bits)E and the output of audio signals shall be as specified by the settings ' of the mode parameters (see 14.3.3.1.).   ?               Table 244 - PLAY AUDIO TRACK RELATIVE(10) command O +=====-========-========-========-========-========-========-========-========+-O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |-O |=====+=======================================================================| O | 0   |                           Operation code (49h)                        |-O |-----+-----------------------------------------------------------------------| O | 1   | Logical unit number      |                  Reserved                  |-O |-----+-----------------------------------------------------------------------| O | 2   | (MSB)                                                                 |-O |-----+---                                                                 ---| O | 3   |                                                                       |-O |-----+---              Track relative logical block address               ---| O | 4   |                                                                       |-O |-----+---                                                                 ---| O | 5   |                                                                  (LSB)|=O |-----+-----------------------------------------------------------------------| O | 6   |                           Starting track                              |qO |-----+-----------------------------------------------------------------------|nO | 7   | (MSB)                                                                 | O |-----+---                        Transfer length                          ---|aO | 8   |                                                                 (LSB) |=O |-----+-----------------------------------------------------------------------| O | 9   |                           Control                                     | O +=============================================================================+=    C The starting track field specifies the track number of the startingt audio track.    D The track relative logical block address (TRLBA) field specifies the? two's complement starting logical block address relative to the F beginning of the first sector on the track with an index value of one.C Negative values indicate a starting location within the audio pause - area at the beginning of the requested track.   D The transfer length field specifies the number of contiguous logicalF blocks that shall be output as audio data.  A transfer length field ofB zero indicates that no audio playback operation shall occur.  ThisF condition shall not be considered an error.  Any other value indicates2 the number of logical blocks that shall be output.  F If the logical block length is not equal to the sector size the targetF may adjust the starting logical block address and the transfer length.D In such case, it is recommended that the target start the audio playF operation with the beginning of a sector whenever the starting logicalF address falls within that sector (MSF unit). If the requested transferA length causes the end of an audio play operation to fall within a E sector, the target may continue the play operation through the end of  that sector.  E If the starting address is not found, or if the address is not within-B an audio track, or if a not ready condition exists, the command isE terminated with CHECK CONDITION status.  See 14.1.7 for a description- of error reporting information.   , 14.2.7 PLAY AUDIO TRACK RELATIVE(12) command  G The PLAY AUDIO TRACK RELATIVE(12) command (see table 245) requests that=B the device begin an audio playback operation. The command functionA (Immed and SOTC bits) and the output of audio signals shall be asdE specified by the settings of the mode parameters (see 14.3.3.1.). SeedB the PLAY AUDIO TRACK RELATIVE(10) command for a description of the fields in this command.o  ?               Table 245 - PLAY AUDIO TRACK RELATIVE(12) commandtO +=====-========-========-========-========-========-========-========-========+eO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |sO |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================|.O | 0   |                           Operation code (A9h)                        |nO |-----+-----------------------------------------------------------------------|iO | 1   | Logical unit number      |                  Reserved                  |.O |-----+-----------------------------------------------------------------------|CO | 2   | (MSB)                                                                 |hO |-----+---                                                                 ---| O | 3   |                                                                       |hO |-----+---              Track relative logical block address               ---|AO | 4   |                                                                       |=O |-----+---                                                                 ---| O | 5   |                                                                  (LSB)| O |-----+-----------------------------------------------------------------------|=O | 6   | (MSB)                                                                 | O |-----+---                                                                 ---|-O | 7   |                                                                       | O |-----+---                        Transfer length                          ---|-O | 8   |                                                                       | O |-----+---                                                                 ---|-O | 9   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|-O | 10  |                           Starting track                              | O |-----+-----------------------------------------------------------------------|-O | 11  |                           Control                                     | O +=============================================================================+-    # 14.2.8 READ CD-ROM CAPACITY command   E The READ CD-ROM CAPACITY command (see table 246) provides a means for-B the initiator to request information regarding the capacity of the
 logical unit.   ;                    Table 246 - READ CD-ROM CAPACITY command O +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================| O | 0   |                           Operation code (25h)                        | O |-----+-----------------------------------------------------------------------|rO | 1   | Logical unit number      |             Reserved              | RelAdr |hO |-----+-----------------------------------------------------------------------|tO | 2   | (MSB)                                                                 |eO |-----+---                                                                 ---| O | 3   |                                                                       |eO |-----+---                        Logical block address                    ---| O | 4   |                                                                       |eO |-----+---                                                                 ---| O | 5   |                                                                 (LSB) |uO |-----+-----------------------------------------------------------------------| O | 6   |                           Reserved                                    |7O |-----+-----------------------------------------------------------------------|fO | 7   |                           Reserved                                    |iO |-----+-----------------------------------------------------------------------|oO | 8   |                           Reserved                           |  PMI   |cO |-----+-----------------------------------------------------------------------|eO | 9   |                           Control                                     |uO +=============================================================================+s    F    NOTE 176 This command has the same operation code (25h) as the READI    CAPACITY command (see 92.7).  The general function is the same but theeI    exact definitions of the returned logical block address is modified to G    allow returning a possibly inexact value (but one with a known erroraK    bound) based on CD-ROM table of contents data.  For many CD-ROM devices,a1    this implementation allows a quicker response.x  ? A partial medium indicator (PMI) bit of zero indicates that theeB information returned in the READ CD-ROM CAPACITY data shall be theC logical block address and block length (in bytes) of the last validLB logical block of the logical unit for seek operations. The logicalA block address returned shall be greater than or equal to the last @ readable or playable block. If greater, this address may be in aE transition area beyond the last valid logical block for read or audioeD play operations. The value returned shall not be not be more than 75F sectors (MSF units) greater than the logical block address of the lastG readable or playable block. (This value arises because the CD-ROM tableaG of contents lead-out track location  has a +/- 75 sector tolerance when C the lead-out track is encoded as an audio track.) The logical block E address in the command descriptor block shall be set to zero for thisa option.e  E A PMI bit of one indicates that the information returned shall be theeE logical block address and block length (in bytes) of the last logicaliF block address after which a substantial delay in data transfer will beF encountered. This logical block address shall be greater than or equalH to the logical block address specified in the command descriptor block. B On CD-ROM media, this is interpreted as being the last readable or< playable logical block of the information area containing or< immediately following the specified logical block address.    M    NOTE 177 This option may take several seconds to complete on CD-ROM media.=  B See 9.1.10 for a description of the relative address bit (RelAdr).  F Eight bytes of READ CD-ROM CAPACITY data (see table 247) shall be sent( during the DATA IN phase of the command.  9                     Table 247 - READ CAPACITY data formatiO +=====-========-========-========-========-========-========-========-========+-O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |BO |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================| O | 0   | (MSB)                                                                 | O |- - -+---                        Logical block address                    ---| O | 3   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------| O | 4   | (MSB)                                                                 |-O |- - -+---                        Block length                             ---| O | 7   |                                                                 (LSB) |-O +=============================================================================+B     14.2.9 READ HEADER command  G The READ HEADER command (see table 248) requests that the device returnnE the CD-ROM data block address header of the requested logical block.    6                        Table 248 - READ HEADER commandO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |=O |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================|.O | 0   |                           Operation code (44h)                        | O |-----+-----------------------------------------------------------------------|tO | 1   | Logical unit number      |         Reserved         |  MSF   |Reserved|tO |-----+-----------------------------------------------------------------------|kO | 2   | (MSB)                                                                 |sO |-----+---                                                                 ---|tO | 3   |                                                                       |eO |-----+---                        Logical block address                    ---| O | 4   |                                                                       |gO |-----+---                                                                 ---|cO | 5   |                                                                 (LSB) |eO |-----+-----------------------------------------------------------------------|eO | 6   |                           Reserved                                    |yO |-----+-----------------------------------------------------------------------|tO | 7   | (MSB)                                                                 |hO |-----+---                        Allocation length                        ---| O | 8   |                                                                 (LSB) |-O |-----+-----------------------------------------------------------------------|dO | 9   |                           Control                                     | O +=============================================================================+i    - See 14.1.5. for a description of the MSF bit.p  D The logical block address field specifies the logical block at which& the read header operation shall begin.  G See the READ command for exception handling.  If the logical block size4B is other than the physical block size, it shall be mapped into theE appropriate physical block from which the data would have been read.    C The READ HEADER data format (see table 249) defines the CD-ROM datat4 block address header of the requested logical block.  8                      Table 249 - READ HEADER data formatO +=====-========-========-========-========-========-========-========-========+pO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |-O |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================|-O | 0   |                       CD-ROM data mode                                | O |-----+-----------------------------------------------------------------------| O | 1   |                          Reserved                                     | O |-----+-----------------------------------------------------------------------|iO | 2   |                          Reserved                                     | O |-----+-----------------------------------------------------------------------| O | 3   |                          Reserved                                     | O |-----+-----------------------------------------------------------------------|-O | 4   | (MSB)                                                                 | O |- - -+---                    Absolute CD-ROM address                      ---| O | 7   |                                                                 (LSB) | O +=============================================================================+r    @ The CD-ROM data mode field specifies the CD-ROM data mode of theD logical blocks in this sector of data.  The values in this field are defined in table 250.   8                       Table 250 - CD-ROM data mode codesK   +=============-============================-============================+-K   |    CD-ROM   |  User data field contents  |  Auxiliary field contents  | K   |     mode    |       (2 048 bytes)        |        (288 bytes)         |-K   |-------------+----------------------------+----------------------------|-K   |     00h     |  All bytes zero            |  All bytes zero            | K   |     01h     |  User data                 |  L-EC symbols              |=K   |     02h     |  User data                 |  User data                 |YK   |  03h - FFh  |  Reserved                  |  Reserved                  |rK   +=======================================================================+b    D If the MSF bit is zero, the absolute address field gives the logicalE block address of the first logical block in the physical sector where F the data for the requested logical block address is found.  If the MSFC bit is one, the absolute address field gives the MSF address of the=G sector where the data for the requested logical block address is found.= (See 14.1.5.)     14.2.10 READ SUB-CHANNEL command  E The READ SUB-CHANNEL command (see table 251) requests that the target-B return the requested sub-channel data plus the state of audio play operations.   9                      Table 251 - READ SUB-CHANNEL command-O +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================| O | 0   |                          Operation code (42h)                         | O |-----+-----------------------------------------------------------------------| O | 1   | Logical unit number      |         Reserved         |  MSF   |Reserved| O |-----+-----------------------------------------------------------------------|-O | 2   |Reserved|  SubQ  |                       Reserved                      | O |-----+-----------------------------------------------------------------------|-O | 3   |                        Sub-channel data format                        | O |-----+-----------------------------------------------------------------------|-O | 4   |                               Reserved                                | O |-----+-----------------------------------------------------------------------|-O | 5   |                               Reserved                                | O |-----+-----------------------------------------------------------------------|=O | 6   |                             Track number                              |hO |-----+-----------------------------------------------------------------------|eO | 7   | (MSB)                                                                 |eO |-----+---                       Allocation length                         ---|cO | 8   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|eO | 9   |                               Control                                 |oO +=============================================================================+n    J    NOTE 178 Sub-channel data returned by this command may be from the lastJ    appropriate sector encountered by a current or previous media accessingK    operation. When there is no current audio play operation, the target maysK    access the media to read the sub-channel data. The target is responsible L    that the data returned are current and consistent.  For example with sub-J    channel data format 0, the International Standard Recording Code (ISRC)H    data reported must have been read from the same track as the reported    current position data.t  - See 14.1.5. for a description of the MSF bit.d  C The sub Q bit set to one requests that the target return the Q sub-nD channel data. The sub Q bit set to zero requests that no sub-channel8 data be returned. This shall not be considered an error.  ?    NOTE 179 The other bits in this byte are reserved for future H    standardization when they may be defined to request other sub-channel    data.  D The sub-channel data format field specifies the returned sub channelA data (see table 252). If this field is 00h, sub-Q channel data iscD returned. If this field is 01h, 02h or 03h, the requested sub-Q data item is returned.b  ;                   Table 252 - Sub-channel data format codestF +=============-======================================================+F | Format Code |  Returned data                                       |F |-------------+------------------------------------------------------|F |     00h     |  Sub-Q channel data                                  |F |     01h     |  CD-ROM current position                             |F |     02h     |  Media catalogue number (UPC/bar code)               |F |     03h     |  Track international standard recording code (ISRC)  |F |  04h - EFh  |  Reserved                                            |F |  F0h - FFh  |  Vendor-specific                                     |F +====================================================================+    B The track number field specifies the track from which ISRC data isF read. This field must have a value between 01h and 63h (99bcd), and isB valid only when the sub-channel data format field is 03h.  In this2 case, the target returns ISRC data for this track.  # 14.2.10.1 Sub-Q channel data format-  B The sub-CHANNEL command data formats consist of a four-byte headerD followed by a sub-channel data block.  The header contains the audioG status byte and the sub-channel data length field.  If the sub Q bit is E zero, the target shall not return the sub-channel data block; in this=' case, the sub-channel data length is 0.=  0 Table 253 defines the sub-Q channel data format.  9                     Table 253 - Sub-Q channel data formateO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |=O |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================| O |     |                        Sub-channel data header                        |=O |=====+=======================================================================| O | 0   |                                Reserved                               |-O |-----+-----------------------------------------------------------------------|mO | 1   |                              Audio status                             |-O |-----+-----------------------------------------------------------------------| O | 2   | (MSB)                                                                 | O |-----+---                     Sub-channel data length                     ---| O | 3   |                                                                 (LSB) | O |=====+=======================================================================| O |     |                        Sub-Q channel data block                       | O |=====+=======================================================================| O | 4   |                    Sub channel data format code (00h)                 |-O |-----+-----------------------------------------------------------------------| O | 5   |                ADR                |             Control               |-O |-----+-----------------------------------------------------------------------| O | 6   |                             Track number                              | O |-----+-----------------------------------------------------------------------| O | 7   |                             Index number                              |-O |-----+-----------------------------------------------------------------------| O | 8   | (MSB)                                                                 |=O |- - -+---                     Absolute CD-ROM address                     ---|eO | 11  |                                                                 (LSB) |aO |--- -+-----------------------------------------------------------------------|fO | 12  | (MSB)                                                                 |oO |- - -+---                  Track relative CD-ROM address                  ---|aO | 15  |                                                                 (LSB) | O |--- -+-----------------------------------------------------------------------| O | 16  |  MCVal |                       Reserved                               |=O |--- -+-----------------------------------------------------------------------| O | 17  | (MSB)                                                                 | O |- - -+---                Media catalogue number (UPC/Bar code)            ---|=O | 31  |                                                                 (LSB) |DO |--- -+-----------------------------------------------------------------------|-O | 32  |  TCVal |                       Reserved                               | O |--- -+-----------------------------------------------------------------------|-O | 33  | (MSB)                                                                 | O |- - -+---        Track international standard recording code (ISRC)       ---|-O | 47  |                                                                 (LSB) | O +=============================================================================+-    F The audio status field indicates the status of audio play operations. E The audio status values are defined in table 254. Audio status values G greater than zero are returned only to the initiator that requested the A last audio play operation. Audio status values 13h and 14h returnBE information on previous audio operations; they are returned only once=E after the condition has occurred.  If another audio play operation isaA not requested, the audio status returned for subsequent READ SUB-  CHANNEL commands is 15h.  6                         Table 254 - Audio status codesD          +========-================================================+D          | Status |  Description                                   |D          |--------+------------------------------------------------|D          |   00h  |  Audio status byte not supported or not valid  |D          |   11h  |  Audio play operation in progress              |D          |   12h  |  Audio play operation paused                   |D          |   13h  |  Audio play operation successfully completed   |D          |   14h  |  Audio play operation stopped due to error     |D          |   15h  |  No current audio status to return             |D          +=========================================================+    @ The sub-channel data length specifies the length in bytes of theD following sub-channel data block.  A sub-channel data length of zeroD indicates that no sub-channel data block is included in the returned data.   M    NOTE 180 Usual values for sub-channel data length are 0, 12, 20, 28 and 44 K    bytes.  Sub-channel data length does not include the sub channel header.=  B The sub-Q channel data block consists of control data (bytes 4-5),F current position data (bytes 6 - 15) and identification data (bytes 16G - 47).  The control data and current position data is obtained from the G Q sub-channel information of the current block. Identification data may=G be reported that was obtained from a previous block.  If identification E data is reported, the data shall be valid for the sector addressed by  the current position data.E    a)     If an audio play operation is proceeding in the background,=E           position data for the last sector played shall be reported. K    b)     In other cases, for instance after a READ command, the target may-G           either report position data for the last sector processed for-K           that operation or may report position data from the sector at thee%           current read head position.-  L    NOTE 181 When the type of information encoded in the Q sub-channel of theL    current sector is the media catalog number or ISRC; the track, index, andB    address fields should be extrapolated from the previous sector.  A The ADR field gives the type of information encoded in the Q sub- - channel of this block, as shown in table 255.-  8                      Table 255 - ADR sub-channel Q fieldK   +===========-===========================================================+-K   |  ADR code |  Description                                              | K   |-----------+-----------------------------------------------------------|-K   |     0h    |  Sub-channel Q mode information not supplied              | K   |     1h    |  Sub-channel Q encodes current position data              |-K   |           |  (i.e. track, index, absolute address, relative address)  | K   |     2h    |  Sub-channel Q encodes media catalogue number             |eK   |     3h    |  Sub-channel Q encodes ISRC                               |-K   |  4h - Fh  |  Reserved                                                 | K   +=======================================================================+-  * The control bits are defined in table 256.  :                     Table 256 - Sub-channel Q control bitsB +=====-==============================-===========================+B | Bit |       Equals zero            |       Equals one          |B |-----+------------------------------+---------------------------|B |  0  |  Audio without pre-emphasis  |  Audio with pre-emphasis  |B |  1  |  Digital copy prohibited     |  Digital copy permitted   |B |  2  |  Audio track                 |  Data track               |B |  3  |  Two-channel audio           |  Four-channel audio       |B +================================================================+              4 The track number specifies the current track number.  A The index number specifies the index number in the current track.b  E The absolute CD-ROM address field gives the current location relativebD to the logical beginning of the media.  If the MSF bit is zero, thisG field is a logical block address.  If the MSF bit is one, this field is7& an absolute MSF address. (See 14.1.5.)  B The track relative CD-ROM address field gives the current locationG relative to the logical beginning of the current track.  If the MSF biteG is zero, this field is a track relative logical block address.  (If theu? current block is in the pre-gap area of a track, this will be a G negative value, expressed as a twos-complement number. See 14.1.5).  If5E the MSF bit is one, this field is the relative MSF address from the Q=
 sub-channel. =  C A media catalogue valid (MCVal) bit of one indicates that the media D catalogue number field is valid.  A MCVal bit of zero indicates that. the media catalogue number field is not valid.  C The media catalogue number field contains the identifying number ofuD this media according to the uniform product code values (UPC/EAN bar= coding) expressed in ASCII. Non-zero values in this field are B controlled by the Uniform Product Code Council 1) and the EuropeanD Article Number Council 2).  A value in this field of all ASCII zeros8 indicates that the media catalog number is not supplied.  E The track code valid (TCVal) bit of one indicates that the track ISRC+= field is valid.  A TCVal bit of zero indicates that the trackC@ international standard recording code (ISRC) field is not valid.  B The track ISRC field contains the identifying number of this mediaB according to the ISRC standards (DIN-31-621) expressed in ASCII.   ----D    1) The Uniform Product Code Council is located at 8163 Old Yankee" Road, Suite J, Dayton, Ohio 45459.?    2) The European Article Number Council is located at Rue des * Colonies, 54-BTE8, 1000 Brussels, Belgium.        - 14.2.10.2 CD-ROM current position data formatt  : Table 257 defines the CD-ROM current position data format.  >                Table 257 - CD-ROM current position data formatO +=====-========-========-========-========-========-========-========-========+=O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================|=O |     |                        Sub-channel data header                        | O |=====+=======================================================================|=O | 0   |                               Reserved                                | O |-----+-----------------------------------------------------------------------|-O | 1   |                             Audio status                              | O |-----+-----------------------------------------------------------------------|-O | 2   | (MSB)                                                                 | O |-----+---                     Sub-channel data length                     ---|-O | 3   |                                                                 (LSB) | O |=====+=======================================================================|=O |     |                  CD-ROM current position data block                   | O |=====+=======================================================================|=O | 4   |                  Sub channel data format code (01h)                   | O |-----+-----------------------------------------------------------------------|-O | 5   |                ADR                |             Control               | O |-----+-----------------------------------------------------------------------|-O | 6   |                             Track number                              | O |-----+-----------------------------------------------------------------------|-O | 7   |                             Index number                              | O |-----+-----------------------------------------------------------------------|-O | 8   | (MSB)                                                                 | O |- - -+---                     Absolute CD-ROM address                     ---|-O | 11  |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|-O | 12  | (MSB)                                                                 | O |- - -+---                  Track relative CD-ROM address                  ---|-O | 15  |                                                                 (LSB) | O +=============================================================================+-    , 14.2.10.3 Media catalogue number data format  9 Table 258 defines the media catalogue number data format.   >                 Table 258 - Media catalogue number data formatO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================|-O |     |                        Sub-channel data header                        | O |=====+=======================================================================|-O | 0   |                               Reserved                                | O |-----+-----------------------------------------------------------------------|cO | 1   |                             Audio status                              | O |-----+-----------------------------------------------------------------------|=O | 2   | (MSB)                                                                 |fO |-----+---                     Sub-channel data length                     ---| O | 3   |                                                                 (LSB) |oO |=====+=======================================================================|sO |     |                   Media catalogue number data block                   | O |=====+=======================================================================|aO | 4   |                  Sub channel data format code (02h)                   |mO |-----+-----------------------------------------------------------------------|+O | 5   |                               Reserved                                |DO |-----+-----------------------------------------------------------------------|-O | 6   |                               Reserved                                |pO |-----+-----------------------------------------------------------------------| O | 7   |                               Reserved                                | O |-----+-----------------------------------------------------------------------| O | 8   |  MCVal |                      Reserved                                | O |-----+-----------------------------------------------------------------------|=O | 9   | (MSB)                                                                 |eO |- - -+---              Media catalogue number (UPC/Bar code)              ---|hO | 23  |                                                                 (LSB) |aO +=============================================================================+d  F If media catalogue number data is found, the MCVal bit is set to one. E If MCN data is not detected, the MCVal bit is set to zero to indicates, the media catalogue number field is invalid.  J    NOTE 182 Media catalogue number data returned by this command with sub-L    channel data format field code 02h may be from any block that has UPC barD    code Q sub-channel data. (This code is constant anywhere in every    applicable disc.)  A 14.2.10.4 Track international standard recording code data formate  F Table 259 defines the track international standard recording code data format.e  H      Table 259 - Track international standard recording code data formatO +=====-========-========-========-========-========-========-========-========+,O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |sO |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================|rO |     |                       Sub-channel data header                         |gO |=====+=======================================================================|fO | 0   |                               Reserved                                |nO |-----+-----------------------------------------------------------------------| O | 1   |                             Audio status                              |=O |-----+-----------------------------------------------------------------------| O | 2   | (MSB)                                                                 |-O |-----+---                     Sub-channel data length                     ---|uO | 3   |                                                                 (LSB) |aO |=====+=======================================================================|vO |     |                         Track ISRC data block                         | O |=====+=======================================================================| O | 4   |                    Sub channel data format code (03h)                 | O |-----+-----------------------------------------------------------------------| O | 5   |              ADR                  |               Control             |uO |-----+-----------------------------------------------------------------------|=O | 6   |                             Track number                              |-O |-----+-----------------------------------------------------------------------|wO | 7   |                               Reserved                                |tO |-----+-----------------------------------------------------------------------|aO | 8   |  TCVal |                      Reserved                                |oO |-----+-----------------------------------------------------------------------| O | 9   | (MSB)                                                                 |rO |- - -+---         Track international standard recording code (ISRC)      ---| O | 23  |                                                                 (LSB) |.O +=============================================================================+     G If ISRC data is detected, the TCVal bit is set to one.  If ISRC data iseE not detected, the TCVal bit is set to zero to indicate the ISRC field  is invalid.n  J    NOTE 183 Track ISRC data returned by this command with sub-channel dataI    format field 03h may be from any block in the specified track that hasa
    ISRC data.i   14.2.11 READ TOC command  G The READ TOC command (see table 260) requests that the target transferso1 data from the table of contents to the initiator.   5                          Table 260 - READ TOC command O +=====-========-========-========-========-========-========-========-========+fO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |tO |=====+=======================================================================|eO | 0   |                         Operation code (43h)                          |nO |-----+-----------------------------------------------------------------------|rO | 1   | Logical unit number      |         Reserved         |  MSF   |Reserved|lO |-----+-----------------------------------------------------------------------|tO | 2   |                           Reserved                                    |fO |-----+-----------------------------------------------------------------------|sO | 3   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------| O | 4   |                           Reserved                                    |uO |-----+-----------------------------------------------------------------------|eO | 5   |                           Reserved                                    |rO |-----+-----------------------------------------------------------------------|=O | 6   |                           Starting track                              | O |-----+-----------------------------------------------------------------------| O | 7   | (MSB)                                                                 |=O |-----+---                        Allocation length                        ---| O | 8   |                                                                 (LSB) |=O |-----+-----------------------------------------------------------------------| O | 9   |                           Control                                     |-O +=============================================================================+     - See 14.1.5. for a description of the MSF bit.   F The starting track field specifies the starting track number for which@ the data shall be returned.  If this value is zero, the table ofG contents data shall begin with the first track on the medium.  The data : are returned in contiguous ascending track number order.    D If the starting track field is not valid for the currently installedE medium, the command shall be terminated with CHECK CONDITION status. =F The sense key shall be set to ILLEGAL REQUEST and the additional sense! code set to INVALID FIELD IN CDB.=  K    NOTE 184 The maximum TOC data length possible on currently available CD- 8    ROM media is 804 bytes, or 100 TOC track descriptors.  : The format of the data returned is specified in table 261.  8                        Table 261 - READ TOC data format O +=====-========-========-========-========-========-========-========-========+-O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |-O |=====+=======================================================================| O | 0   | (MSB)                                                                 |-O |-----+---                        TOC data length                          ---| O | 1   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------| O | 2   |                           First track number                          |-O |-----+-----------------------------------------------------------------------| O | 3   |                           Last track number                           | O |=====+=======================================================================| O |     |                         TOC track descriptor(s)                       |=O |=====+=======================================================================|uO | 0   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|=O | 1   |              ADR                  |             Control               | O |-----+-----------------------------------------------------------------------| O | 2   |                           Track number                                |=O |-----+-----------------------------------------------------------------------| O | 3   |                           Reserved                                    |=O |-----+-----------------------------------------------------------------------| O | 4   | (MSB)                                                                 |-O |- ---+---                        Absolute CD-ROM address                  ---| O | 7   |                                                                 (LSB) |-O +=============================================================================+     G The TOC data block contains a four-byte header followed by zero or more- TOC track descriptors.  F The TOC data length specifies the length in bytes of the following TOCF data that is available to be transferred during the DATA IN phase. The@ TOC data length value does not include the TOC data length field itself.   D The first track number field indicates the first track number in the table of contents.    B The last track number field indicates the last track number in the3 table of contents before the lead-out track number.   I    NOTE 185 The first track number is not required to be one.  A disc may-H    start at any valid track number.  The track numbers between the firstJ    track number and the last track number are required to be in contiguous2    ascending order, except for the lead-out track.  A The ADR field gives the type of information encoded in the Q sub--F channel of the block where this TOC entry was found.  The possible ADR  values are defined in 14.2.10.1.  F The control field indicates the attributes of the track.  The possible. control field values are defined in 14.2.10.1.  G The track number field indicates the track number for which the data in D the TOC track descriptor is valid.  A track number of 0AAh indicates@ that the track descriptor is for the start of the lead-out area.  C The absolute CD-ROM address contains the address of the first block E with user information for that track number as read from the table of @ contents.  An MSF bit of zero indicates that the absolute CD-ROMB address field contains a logical block address.  An MSF bit of oneC indicates the absolute CD-ROM address field contains an MSF addressb (see 14.1.5).   K    NOTE 186 The starting logical block address value recovered from the TOC J    has a tolerance of zero for data tracks and plus or minus 75 CD sectorsK    for audio tracks.  This tolerance is multiplied by a factor dependent on     the logical block length.  " 14.3 Parameters for CD-ROM devices     14.3.1 Diagnostic parameters  ? This subclause defines the descriptors and pages for diagnostict% parameters used with CD-ROM devices. a  F The diagnostic page codes for CD-ROM devices are defined in table 262.  7                       Table 262 - Diagnostic page codesdO +=============-==================================================-============+=O |  Page code  |  Description                                     |  Subclause | O |-------------+--------------------------------------------------+------------| O |     00h     |  Supported diagnostic pages                      |  8.3.1.1   |=O |  01h - 3Fh  |  Reserved (for all device type pages)            |            | O |  40h - 7Fh  |  Reserved                                        |            |=O |  80h - FFh  |  Vendor-specific pages                           |            | O +=============================================================================+-     14.3.2 Log parameters   C This subclause defines the descriptors and pages for log parameters  used with CD-ROM devices.-  ? The log page codes for CD-ROM devices are defined in table 263.M  4                           Table 263 - Log page codesO +=============-==================================================-============+ O |  Page code  |  Description                                     |  Subclause | O |-------------+--------------------------------------------------+------------|=O |     01h     |  Buffer over-run/under-run page                  |  8.3.2.1   | O |     03h     |  Error counter page (read) page                  |  8.3.2.2   |=O |     07h     |  Last n error events page                        |  8.3.2.3   | O |     06h     |  Non-medium error page                           |  8.3.2.4   |-O |     02h     |  Reserved                                        |            | O |  04h - 05h  |  Reserved                                        |            |-O |  08h - 2Fh  |  Reserved                                        |            | O |     3Fh     |  Reserved                                        |            |-O |     00h     |  Supported log pages                             |  8.3.2.5   | O |  30h - 3Eh  |  Vendor-specific pages                           |            |-O +=============================================================================+      14.3.3 Mode parameters  D This subclause defines the descriptors and pages for mode parameters used with CD-ROM devices.   E The mode parameter list, including the mode parameter header and modea& block descriptor are defined in 8.3.3.  D The medium-type code field is contained in the mode parameter headerA (see 8.3.3).  Table 264 defines the medium type values for CD-ROM= devices.    9                      Table 264 - CD-ROM medium type codes 9 +=============-=========================================+d9 |     Code    |  Medium type description                | 9 |=============+=========================================|s9 |     00h     |  Default (only one type supported)      |f9 |     01h     |  120 mm CD-ROM data only                |a9 |     02h     |  120 mm CD-DA audio only                | 9 |     03h     |  120 mm CD-ROM data and audio combined  |h9 |     04h     |  Reserved                               | 9 |     05h     |  80 mm CD-ROM data only                 |=9 |     06h     |  80 mm CD-DA audio only                 | 9 |     07h     |  80 mm CD-ROM data and audio combined   | 9 |  08h - 7Fh  |  Reserved                               | 9 |  80h - FFh  |  Vendor-specific                        |=9 +=======================================================+=    F The device-specific parameter field is contained in the mode parameterD header (see 8.3.3).  Table 265 defines the device-specific parameter field for CD-ROM devices.     =                  Table 265 - CD-ROM device-specific parametereO +=====-========-========-========-========-========-========-========-========+-O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |=====+==========================+========+==========================+========|-O |     |         Reserved         | DPOFUA |           Reserved       |  EBC   | O +=============================================================================+-    F When used with the MODE SELECT command, the DPOFUA bit is not used and the field is reserved.  D When used with the MODE SENSE command, a DPOFUA bit of one indicates: that the target supports the DPO and FUA bits (see 9.2.6).  - The enable blank check (EBC) bit is reserved.-  ? The density code field is contained in the mode parameter block F descriptor (see 8.3.3).  Table 266 defines the density code values for CD-ROM devices.-    7                        Table 266 - CD-ROM density codes E +================-==================================================+ E |    Code        |  Data types to be transferred                    | E |================+==================================================| E |     00h        |  Default density code                            |-E |     01h        |  User data only                                  | E |                |    (2 048 bytes per physical sector)             |=E |     02h        |  User data plus auxiliary data field             |1E |                |    (2 336 bytes per sector)                      |iE |     03h        |  4-byte tag field, user data plus auxiliary data |IE |                |    (2 340 bytes per sector)                      |fE |     04h        |  Audio information only                          |iE |                |    (1/75th of a second per logical block)        |rE |  05h - 7Fh     |  Reserved                                        |CE |  80h - FFh     |  Vendor-specific                                 | E +===================================================================+     I    NOTE 187 The number of bytes per sector specified by this parameter isdD    used with the block length to map CD-ROM sectors to logical block
    addresses.s  @ The mode page codes for CD-ROM devices are defined in table 267.  4                          Table 267 - Mode page codesO +=============-==================================================-============+ O |  Page code  |  Description                                     |  Subclause | O |-------------+--------------------------------------------------+------------|=O |     08h     |  Caching page                                    |   9.3.3.1  | O |     0Eh     |  CD-ROM audio control page                       |  14.3.3.1  |aO |     0Dh     |  CD-ROM page                                     |  14.3.3.2  | O |     0Ah     |  Control mode page                               |   8.3.3.1  |-O |     02h     |  Disconnect-reconnect page                       |   8.3.3.2  | O |     0Bh     |  Medium types supported page                     |   9.3.3.4  |-O |     09h     |  Peripheral device page                          |   8.3.3.3  |tO |     01h     |  Read error recovery page                        |  14.3.3.3  |=O |  03h - 06h  |  Reserved                                        |            |cO |     0Ch     |  Reserved                                        |            |=O |  0Fh - 1Fh  |  Reserved                                        |            |vO |     07h     |  Verify error recovery page                      |  14.3.3.4  |-O |     00h     |  Vendor-specific (does not require page format)  |            | O |  20h - 3Eh  |  Vendor-specific (page format required)          |            |-O |     3Fh     |  Return all pages                                |            | O |             |     (valid only for the MODE SENSE command)      |            |-O +=============================================================================+v    ( 14.3.3.1 CD-ROM audio control parameters  A The CD-ROM audio control parameters page (see table 268) sets the-E playback modes and output controls for subsequent PLAY AUDIO commands * and any current audio playback operation.   ?                Table 268 - CD-ROM audio control parameters page O +=====-========-========-========-========-========-========-========-========+=O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |iO |=====+========+========+=====================================================| O | 0   |   PS   |Reserved|            Page code (0Eh)                          |lO |-----+-----------------------------------------------------------------------|cO | 1   |                           Parameter length (0Eh)                      |hO |-----+-----------------------------------------------------------------------|tO | 2   |                  Reserved                  | Immed  |  SOTC  |Reserved| O |-----+-----------------------------------------------------------------------|nO | 3   |                           Reserved                                    |tO |-----+-----------------------------------------------------------------------| O | 4   |                           Reserved                                    |wO |-----+-----------------------------------------------------------------------|.O | 5   | APRVal |         Reserved         |        Format of LBAs / Sec.      |oO |-----+-----------------------------------------------------------------------|tO | 6   | (MSB)                                                                 |uO |-----+---          Logical blocks per second of audio playback            ---|tO | 7   |                                                                  (LSB)|iO |-----+-----------------------------------------------------------------------|AO | 8   |              Reserved             |  Output port 0 channel selection  |gO |-----+-----------------------------------------------------------------------|lO | 9   |                           Output port 0 volume                        |oO |-----+-----------------------------------------------------------------------|cO | 10  |              Reserved             |  Output port 1 channel selection  |pO |-----+-----------------------------------------------------------------------|oO | 11  |                           Output port 1 volume                        |dO |-----+-----------------------------------------------------------------------|hO | 12  |              Reserved             |  Output port 2 channel selection  | O |-----+-----------------------------------------------------------------------|=O | 13  |                           Output port 2 volume                        | O |-----+-----------------------------------------------------------------------|-O | 14  |              Reserved             |  Output port 3 channel selection  |sO |-----+-----------------------------------------------------------------------|lO | 15  |                           Output port 3 volume                        | O +=============================================================================+p    @ The parameters savable (PS) bit is only used with the MODE SENSEF command.  This bit is reserved with the MODE SELECT command.  A PS bitC of one indicates that the target is capable of saving the page in ar& non-volatile vendor-specific location.  D An immediate (Immed) bit of zero indicates the target shall not sendC completion status until the audio playback operation is terminated.=  E An Immed bit of one indicates the target shall send completion statusP3 as soon as the playback operation has been started.   H    NOTE 188 It is recommended that a Logical Unit type RESERVE be issuedJ    prior to starting audio play operations with an Immed bit of one in any"    multiple initiator environment.  F A stop on track crossing (SOTC) bit of zero indicates the target shallB terminate the audio playback operation when the transfer length isE satisfied.  Multiple tracks shall be played as necessary.  Periods of F time encoded as audio pause/silence at the beginning of tracks, (index 0) shall also be played.    E A stop on track crossing (SOTC) bit of one indicates the target shall > terminate the audio playback operation when the beginning of a  following track is encountered.   F The audio playback rate valid (APRVal) bit value of one indicates thatD the format of logical blocks per second field and the logical blocks- per second of audio playback field are valid.o  A The format of logical blocks addresses per second field gives the=A multiplier to be used with the logical blocks per second of audio=( playback.  This is defined in table 269.  6                        Table 269 - Multiplier for LBAsD +==============================-===================================+D |  Format of LBAs / Sec value  |  Multiplier for LBAs / Sec field  |D |------------------------------+-----------------------------------|D |                0h            |                1                  |D |              1h - 7h         |                Reserved           |D |                8h            |                1/256              |D |              9h - Fh         |                Reserved           |D +==================================================================+    M    NOTE 189 This field is provided as a means to return fractional (i.e. non- F    integral) values in the logical block addresses per second of audioI    playback.  This shall occur when logical block sizes that are not even >    multiples or divisions of the physical block size are used.  ? The logical blocks per second of audio playback field gives theCD relationship between time and the duration of play per logical blockD address. The value in this field is to be multiplied by the value in! format of LBAs per second field. n  I    NOTE 190 The logical blocks per second of audio playback field and its=I    companion format of LBAs per second field may not be supported by mosti@    current CD-ROM devices as a modifiable mode select parameter.  G The output port channel selection specifies the audio channels from theTD disc to which this output port should be connected (see table 270). E More than one output port may be connected to an audio channel.  More ; than one audio channel may be connected to an output port.    ;                   Table 270 - Output port channel selection=< +==========-===============================================+< |   Code   |  Description                                  |< |==========+===============================================|< |   0000b  |  output port muted                            |< |   0001b  |  connect audio channel 0 to this output port  |< |   0010b  |  connect audio channel 1 to this output port  |< |   0100b  |  connect audio channel 2 to this output port  |< |   1000b  |  connect audio channel 3 to this output port  |< +==========================================================+    H The channel volume control indicates the relative volume level for this G audio output port. A value of zero indicates the output is muted, and a=, value of FFh indicates maximum volume level.  H    NOTE 191 If volume controls are implemented, the default volume levelH    should be no more than 25 % of the maximum level as a personal safety    consideration.   " 14.3.3.2 CD-ROM device parameters   D The CD-ROM parameters page (see table 271) specifies parameters that affect all CD-ROM data types.|  8                       Table 271 - CD-ROM parameters pageO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |eO |Byte |        |        |        |        |        |        |        |        |pO |=====+========+========+=====================================================| O | 0   |   PS   |Reserved|         Page code (0Dh)                             |lO |-----+-----------------------------------------------------------------------| O | 1   |                           Parameter length (06h)                      |=O |-----+-----------------------------------------------------------------------|8O | 2   |                           Reserved                                    |eO |-----+-----------------------------------------------------------------------|pO | 3   |             Reserved              |     Inactivity timer multiplier   | O |-----+-----------------------------------------------------------------------|=O | 4   |                                                                       | O |-----| - - -         Number of MSF - S units per MSF - M unit          - - - |-O | 5   |                                                                       | O |-----+-----------------------------------------------------------------------| O | 6   |                                                                       | O |-----| - - -         Number of MSF - F units per MSF - S unit          - - - | O | 7   |                                                                       | O +=============================================================================+     @ The parameters savable (PS) bit is only used with the MODE SENSEF command.  This bit is reserved with the MODE SELECT command.  A PS bitC of one indicates that the target is capable of saving the page in aR& non-volatile vendor-specific location.  E The inactivity timer multiplier specifies the length of time that the E drive shall remain in the hold track state after completion of a seek " or read operation (see table 272).  M    NOTE 192 Higher values in this parameter may have an adverse effect on the4'    drive MTBF, in some implementations.o  >                 Table 272 - Inactivity timer multiplier valuesN +==================-==================-===================-==================+N | Inactivity timer | Minimum time in  | Inactivity timer  | Minimum time in  |N |    multiplier    | hold track state |    multiplier     | hold track state |N |------------------+------------------+-------------------+------------------|N |       0h         | Vendor-specific  |       8h          |      16s         |N |       1h         | 125 ms           |       9h          |      32s         |N |       2h         | 250 ms           |       Ah          |      1 min       |N |       3h         | 500 ms           |       Bh          |      2 min       |N |       4h         |   1 s            |       Ch          |      4 min       |N |       5h         |   2 s            |       Dh          |      8 min       |N |       6h         |   4 s            |       Eh          |     16 min       |N |       7h         |   8 s            |       Fh          |     32 min       |N +=====================================-======================================+    C The number of S units per M unit field gives the ratio of these MSF F address values. For media conforming to the CD-ROM and CD-DA standard, this value is 60.   C The number of F units per S unit field gives the ratio of these MSF F address values. For media conforming to the CD-ROM and CD-DA standard, this value is 75.-  ( 14.3.3.3 Read error recovery parameters   E The read error recovery parameters page (see table 273) specifies the F error recovery parameters the target shall use during any command thatA performs a data read operation to the media (e.g. READ, READ TOC,e etc.).    >                Table 273 - Read error recovery parameters pageO +=====-========-========-========-========-========-========-========-========+rO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |-O |Byte |        |        |        |        |        |        |        |        | O |=====+========+========+=====================================================|lO | 0   |   PS   |Reserved|                 Page code (01h)                     | O |-----+-----------------------------------------------------------------------|-O | 1   |                       Parameter length (06h)                          | O |-----+-----------------------------------------------------------------------|-O | 2   |                       Error recovery parameter                        | O |-----+-----------------------------------------------------------------------|-O | 3   |                        Read retry count                               | O |-----+-----------------------------------------------------------------------|-O | 4   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|-O | 5   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|-O | 6   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|-O | 7   |                           Reserved                                    | O +=============================================================================+-    @ The parameters savable (PS) bit is only used with the MODE SENSEF command.  This bit is reserved with the MODE SELECT command.  A PS bitC of one indicates that the target is capable of saving the page in a=& non-volatile vendor-specific location.  : The error recovery parameter bits are defined in 9.3.3.6.   F    NOTE 193 The implementation of error recovery procedures for CD-ROMI    devices is markedly different from those used for magnetic medium diskoM    drives.  At least one level of error correction (i.e. CIRC) is required topI    transfer the data stream.  Therefore, the performance of the drive maydM    differ substantially from what would be expected by sending the same errorp3    recovery parameters to a magnetic medium device.t  D The correlation of the error recovery parameter and the bit settingsE defined for CD-ROM devices is given in table 274.  The interpretationiF of these bit settings for CD-ROM devices is given in table 275. If theE error recovery parameter is set to any other value, the command shalleF be terminated with CHECK CONDITION status.  The sense key shall be setE to ILLEGAL REQUEST and the additional sense code set to INVALID FIELDg IN PARAMETER LIST.  :                    Table 274 - Error recovery bit settings +===========-=================+r | Error     |   Bit settings  |l | recovery  |-----------------|n | parameter | 7 6 5 4 3 2 1 0 |t |===========+=================|  |    00h    | R R 0 0 R 0 0 0 |n |    01h    | R R 0 0 R 0 0 1 |a |    04h    | R R 0 0 R 1 0 0 |  |    05h    | R R 0 0 R 1 0 1 |i |    06h    | R R 0 0 R 1 1 0 |h |    07h    | R R 0 0 R 1 1 1 |s |    10h    | R R 0 1 R 0 0 0 |u |    11h    | R R 0 1 R 0 0 1 |c |    14h    | R R 0 1 R 1 0 0 |l |    15h    | R R 0 1 R 1 0 1 |  |    20h    | R R 1 0 R 0 0 0 |b |    21h    | R R 1 0 R 0 0 1 |= |    24h    | R R 1 0 R 1 0 0 |= |    25h    | R R 1 0 R 1 0 1 |  |    26h    | R R 1 0 R 1 1 0 |u |    27h    | R R 1 0 R 1 1 1 |  |    30h    | R R 1 1 R 0 0 0 |- |    31h    | R R 1 1 R 0 0 1 || |    34h    | R R 1 1 R 1 0 0 || |    35h    | R R 1 1 R 1 0 1 |  |-----------------------------|  |NOTE   Reserved bits shall   |  |       be set to zero.       |  +=============================+     >                 Table 275 - CD-ROM error recovery descriptionsO +=============================================================================+ O |Error recovery description                                                   | O |-----------------------------------------------------------------------------|cO | 00h The maximum error recovery procedures available are used.  If an error  | O |     occurs which is uncorrectable with the error correction codes (ECC) on  |fO |     the media, data transfer is terminated with CHECK CONDITION status. The |lO |     block with the error is not transferred. The sense key is set to MEDIUM | O |     ERROR. The information bytes give the address of the block where the    |rO |     unrecovered error was detected. Recovered errors are not reported.      |fO |                                                                             |eO | 01h Only retries of the read operation and CIRC are used (layered error     |eO |     correction is not used). Only CIRC unrecovered data errors are reported.| O |     If an CIRC unrecovered data error occurs, data transfer is terminated   |eO |     with CHECK CONDITION status.  The block with the error is not           |7O |     transferred. The sense key is set to MEDIUM ERROR. The information bytes|=O |     give the address of the block where the unrecovered error was detected. |=O |     Recovered errors are not reported.                                      |rO |                                                                             |iO | 04h The maximum error recovery procedures available are used. Recovered data| O |     errors are reported.  If a recovered data error occurs, data transfer is| O |     not terminated.   However, when the data transfer has completed CHECK   |=O |     CONDITION status is reported.  The sense key is set to RECOVERED ERROR. |lO |     The information bytes give the address of the last block where a        | O |     recovered data error was detected.                                      |tO |                                                                             | O |     If a data error occurs that is uncorrectable with the ECC information   |iO |     available on the media, data transfer is terminated and CHECK CONDITION | O |     status is reported. The block with the error is not transferred. The    |pO |     sense key is set to MEDIUM ERROR. The information bytes give the address|=O |     of the block where the uncorrectable error was detected.                | O |                                                                             | O | 05h Only retries of the read operation and CIRC are used (layered error     |=O |     correction is not used).  Recovered data errors are reported.  If a     | O |     recovered data error occurs, data transfer is not terminated.  However, |-O |     when the data transfer has completed CHECK CONDITION status is reported.| O |     The sense key is set to RECOVERED ERROR. The information bytes give the |-O |     address of the last block where a CIRC recovered data error was         | O |     detected.                                                               |-O |                                                                             |mO |     If an unrecovered data error occurs, data transfer is terminated and    |-O |     CHECK CONDITION status is reported. The block with the error is not     | O |     transferred. The sense key is set to MEDIUM ERROR. The information bytes| O |     give the address of the block where the unrecovered error was detected. | O |                                                                             |-O | 06h The maximum error recovery procedures are used. Recovered data errors   | O |     are reported.  If a recovered data error occurs data transfer is        | O |     terminated and CHECK CONDITION status is reported.  The block with the  | O |     recovered error is not transferred. The sense key is set to RECOVERED   |=O |     ERROR.  The information bytes give the address of the block where the   |NO |     recovered data error was detected.                                      |eO |                                                                             |oO |     If a data error occurs that is uncorrectable with the ECC information   |iO |     on the medium, data transfer is terminated with CHECK CONDITION status. |eO |     The block with the error is not transferred.  The sense key is set to   |eO |     MEDIUM ERROR. The information bytes give the address of the block where | O |     the uncorrectable error was detected.                                   |=O +=============================================================================+r     Table 275  (continued)P +==============================================================================+P |Error recovery description                                                    |P |------------------------------------------------------------------------------|P | 07h Only retries of the read operation are used (layer error correction is   |P |     not used).  CIRC recovered data errors are reported.  If a CIRC          |P |     recovered data error occurs, data transfer is terminated with CHECK      |P |     CONDITION status.  The block with the recovered error is not             |P |     transferred.  The sense key is set to RECOVERED ERROR. The information   |P |     bytes give the address of the block where the recovered data error was   |P |     detected.                                                                |P |                                                                              |P |     If an CIRC unrecovered data error occurs, data transfer is terminated    |P |     with CHECK CONDITION status.  The block with the error is not            |P |     transferred.  The sense key is set to MEDIUM ERROR. The information      |P |     bytes give the address of the block where the unrecovered error was      |P |     detected.                                                                |P |                                                                              |P | 10h If data transfer can be maintained, the maximum error recovery           |P |     procedures available are used. (RC = 1.) If an error occurs which is     |P |     uncorrectable with the error correction codes (ECC) on the media, or is  |P |     uncorrectable in time to maintain data transfer, the data transfer is    |P |     not terminated.  However, when the data transfer has completed, CHECK    |P |     CONDITION status is reported.  The sense key is set to MEDIUM ERROR.     |P |     The information bytes give the address of the block where the first      |P |     unrecovered error was detected. Recovered errors are not reported.       |P |                                                                              |P | 11h If data transfer can be maintained, retries of the read operation and    |P |     CIRC are used (layered error correction is not used). (RC = 1.)  Only    |P |     CIRC unrecovered data errors are reported. If a CIRC unrecovered data    |P |     error occurs, data transfer is not terminated. However, when the data    |P |     transfer has completed, CHECK CONDITION status is reported.  The sense   |P |     key is set to MEDIUM ERROR. The information bytes give the address of    |P |     the block where the first unrecovered error was detected.  Recovered     |P |     errors are not reported.                                                 |P |                                                                              |P | 14h If data transfer can be maintained, the maximum error recovery           |P |     procedures available are used. (RC = 1.)  Recovered data errors are      |P |     reported.  If a recovered data error occurs, data transfer is not        |P |     terminated.   However, when the data transfer has completed, CHECK       |P |     CONDITION status is reported.  The sense key is set to RECOVERED ERROR.  |P |     The information bytes give the address of the block where a recovered    |P |     data error was detected.                                                 |P |                                                                              |P |     If an data error occurs that is uncorrectable with the ECC information   |P |     available on the media, or is uncorrectable in time to maintain data     |P |     transfer, the data transfer is not terminated.  However, when the data   |P |     transfer has completed CHECK CONDITION, status is reported. The sense key|P |     is set to MEDIUM ERROR. The information bytes give the address of the    |P |     block where the first uncorrectable error was detected.  Reporting       |P |     unrecovered errors takes precedence over reporting recovered errors.     |P +==============================================================================+       Table 275  (continued)O +=============================================================================+NO |Error recovery description                                                   | O |-----------------------------------------------------------------------------|EO | 15h If data transfer can be maintained, retries of the read operation and   | O |     CIRC are used (layered error correction is not used). (RC = 1.)         | O |     Recovered data errors are reported.  If a recovered data error occurs,  | O |     data transfer is not terminated.  However, when the data transfer has   | O |     completed CHECK CONDITION status is reported.  The sense key is set to  |hO |     RECOVERED ERROR. The information bytes give the address of the block    | O |     where a CIRC recovered data error was detected.                         | O |                                                                             | O |     If an unrecovered data error occurs, data transfer is not terminated.   | O |     However, when the data transfer has completed CHECK CONDITION status is | O |     reported.  The sense key is set to MEDIUM ERROR. The information bytes  |-O |     give the address of the block where the first unrecovered error was     |=O |     detected.  Reporting unrecovered errors takes precedence over reporting |rO |     recovered errors.                                                       |=O |                                                                             | O | 20h The maximum error recovery procedures available are used.  If an error  |-O |     occurs which is uncorrectable with the error correction codes (ECC) on  |IO |     the media, data transfer is terminated with CHECK CONDITION status. The |eO |     block with the error is transferred. The sense key is set to MEDIUM     | O |     ERROR. The information bytes give the address of the block where the    |eO |     unrecovered error was detected. Recovered errors are not reported.      |wO |                                                                             |pO | 21h Only retries of the read operation and CIRC are used (layered error     | O |     correction is not used). Only CIRC unrecovered data errors are reported.|eO |     If a CIRC unrecovered data error occurs data transfer is terminated     |aO |     with CHECK CONDITION status. The block with the error is transferred.   |tO |     The sense key is set to MEDIUM ERROR. The information bytes give the    |oO |     address of the block where the unrecovered error was detected.          |rO |     Recovered errors are not reported.                                      |aO |                                                                             | O | 24h The maximum error recovery procedures available are used. Recovered data| O |     errors are reported.  If a recovered data error occurs data transfer is |eO |     not terminated.   However, when the data transfer has completed, CHECK  |aO |     CONDITION status is reported.  The sense key is set to RECOVERED ERROR. |eO |     The information bytes give the address of the last block where a        |VO |     recovered data error was detected.                                      |eO |                                                                             | O |     If a data error occurs that is uncorrectable with the ECC information   | O |     available on the media data transfer is terminated and CHECK CONDITION  |nO |     status is reported. The block with the error is transferred. The sense  |CO |     key is set to MEDIUM ERROR. The information bytes give the address of   |rO |     the block where the uncorrectable error was detected.                   |eO +=============================================================================+        Table 275  (concluded)P +==============================================================================+P |Error recovery description                                                    |P |------------------------------------------------------------------------------|P | 25h Only retries of the read operation and CIRC are used (layered error      |P |     correction is not used).  Recovered data errors are reported.  If a      |P |     recovered data error occurs, data transfer is not terminated.  However,  |P |     when the data transfer has completed, CHECK CONDITION status is reported.|P |     The sense key is set to RECOVERED ERROR. The information bytes give the  |P |     address of the last block where an CIRC recovered data error was         |P |     detected.                                                                |P |                                                                              |P |     If an unrecovered data error occurs, data transfer is terminated and     |P |     CHECK CONDITION status is reported. The block with the error is          |P |     transferred.  The sense key is set to MEDIUM ERROR.  The information     |P |     bytes give the address of the block where the unrecovered error was      |P |     detected.                                                                |P |                                                                              |P | 26h The maximum error recovery procedures are used.  Recovered data errors   |P |     are reported.  If a recovered data error occurs, data transfer is        |P |     terminated and CHECK CONDITION status is reported.  The block with the   |P |     recovered error is transferred.  The sense key is set to RECOVERED       |P |     ERROR.  The information bytes give the address of the block where the    |P |     recovered data error was detected.                                       |P |                                                                              |P |     If a data error occurs that is uncorrectable with the ECC information    |P |     on the media, data transfer is terminated with CHECK CONDITION status.   |P |     The block with the error is transferred. The sense key is set to MEDIUM  |P |     ERROR. The information bytes give the address of the block where the     |P |     uncorrectable error was detected.                                        |P |                                                                              |P | 27h Only retries of the read operation are used (layer error correction is   |P |     not used).  CIRC recovered data errors are reported.  If a CIRC          |P |     recovered data error occurs, data transfer is terminated with CHECK      |P |     CONDITION status.  The block with the recovered error is transferred.    |P |     The sense key is set to RECOVERED ERROR. The information bytes give the  |P |     address of the block where the recovered data error was detected.        |P |                                                                              |P |     If a CIRC unrecovered data error occurs, data transfer is terminated     |P |     with CHECK CONDITION status. The block with the error is transferred.    |P |     The sense key is set to MEDIUM ERROR. The information bytes give the     |P |     address of the block where the unrecovered error was detected.           |P |                                                                              |P | 30h  Same as code 10H.                                                       |P |                                                                              |P | 31h  Same as code 11H.                                                       |P |                                                                              |P | 34h  Same as code 14H.                                                       |P |                                                                              |P | 35h  Same as code 15H.                                                       |P +==============================================================================+    A The read retry count field specifies the number of times that the 7 controller shall attempt its read recovery algorithm.  t  D A CIRC recovered data error is defined as a block for which the CIRCE based error correction algorithm was unsuccessful for a read attempt, G but on a subsequent read operation no error was reported. The number of F subsequent read operations is limited to the read retry count. Layered error correction was not used.       F A CIRC unrecovered data error is defined as a block for which the CIRCF based error correction algorithm was unsuccessful on all read attemptsC up to the read retry count. Layered error correction was not used.    E An L-EC recovered data error is defined as a block for which the CIRC B based error correction algorithm was unsuccessful, but the layeredD error correction was able to correct the block within the read retry count.  F An L-EC uncorrectable data error is defined as a block which could notE be corrected by layered error correction within the read retry count.   ) 14.3.3.4 Verify error recovery parameters   G The verify error recovery parameters page (see table 276) specifies the G error recovery parameter the target shall use during verify operations.     ?               Table 276 - Verify error recovery parameters pageeO +=====-========-========-========-========-========-========-========-========+RO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |rO |Byte |        |        |        |        |        |        |        |        | O |=====+========+========+=====================================================| O | 0   |   PS   |Reserved|                  Page code (07h)                    |EO |-----+-----------------------------------------------------------------------|mO | 1   |                      Parameter length (06h)                           |,O |-----+-----------------------------------------------------------------------|tO | 2   |                    Error recovery parameter                           |aO |-----+-----------------------------------------------------------------------| O | 3   |                       Verify retry count                              |vO |-----+-----------------------------------------------------------------------|=O | 4   |                           Reserved                                    |=O |-----+-----------------------------------------------------------------------| O | 5   |                           Reserved                                    |-O |-----+-----------------------------------------------------------------------|aO | 6   |                           Reserved                                    |rO |-----+-----------------------------------------------------------------------| O | 7   |                           Reserved                                    |iO +=============================================================================+     @ The parameters savable (PS) bit is only used with the MODE SENSEF command.  This bit is reserved with the MODE SELECT command.  A PS bitC of one indicates that the target is capable of saving the page in a & non-volatile vendor-specific location.  E The error recovery parameters for verify operations are as defined bye2 the read error recovery parameters (see 14.3.3.3).    + 14.4 Definitions specific to CD-ROM devicese  E 14.4.1 absolute F field:  The sub-division of the S Field part of theM? absolute physical address from the beginning of the media.  One A physical sector.  Written on CD-ROM media in binary coded decimaltH notation.  The value is from 00bcd to 74bcd. (See 14.4.12 and 14.4.18.)     C 14.4.2 absolute M field:  The most significant part of the absolute C physical address from the beginning of the media. Written on CD-ROM C media in binary coded decimal notation.  The value is from 00bcd to  74bcd.  (See 14.4.18.)  B 14.4.3 absolute S field:  The intermediate significant part of theF absolute physical address from the beginning of the media.  Written onG CD-ROM media in binary coded decimal notation.  The value is from 00bcds to 59bcd.  (See 14.4.18.)   @ 14.4.4 bcd; binary coded decimal:  The number system used on theE physical CD-ROM and CD-DA media.  Numbers that use this notation haveoG the 'bcd' suffix attached. A byte has two four-bit values each of which H can have a value from 0 to 9.  The maximum value is 99bcd (99 decimal). , Hence the maximum number of tracks is 99bcd.  D        Example: 00 01 02 03 ... 08 09 10 11 ... 19 20 21 ... 98 99.   G 14.4.5 block:  The term block refers to the data in one logical block -rC the number of bytes defined by the logical block length in the mode  block descriptor.d  F 14.4.6 blocks per sector:  The number of logical blocks read from eachE CD-ROM physical sector. The value depends on the logical block LengthwB as defined in the mode block descriptor.  The value for blocks per
 sector is:>                       1 if the logical block length is 2 048, =                       2 if the logical block length is 1 024, ?                       4 if the logical block length is 512, and A                       8 if the logical block length is 256 bytes.nG        (Assuming a density code of 1 - 2 048 bytes of data per sector.)o  G 14.4.7 CD-DA; compact disc - digital audio:  The standardized media foreB recording digital audio information.  The 'Red Book' defines CD-DA media.  F 14.4.8 CD-ROM; compact disc - read only memory:  A standardized mediumC for recording digitized audio and digital data.   CD-ROM is used to D describe media with digital data rather than discs that encode audio7 only.  The ISO/IEC 10149 standard defines CD-ROM media.   C 14.4.9 CD-ROM control field:  A four bit field in the Q sub-channelKF data indicating the type of information encoded on the current track. E Indicates audio versus data and the type of audio encoding, etc.  Thet= control field is also found in the table of contents entries.n  H 14.4.10 CD-ROM data mode:  A byte in the header of CD-ROM data sectors. A This indicates if data is present and if layered error correctiona information is present.=  G 14.4.11 CIRC; cross interleaved reed-solomon code:  The error detection+D and correction technique used within small frames of audio or data. ? The CIRC bytes are present in all CD-ROM data modes.  The error-D correction procedure which uses the CIRC bytes is referred to as the> CIRC based algorithm.  In most CD-ROM drives, this function is implemented in hardware.    D 14.4.12 frame:  A physical sector on CD-ROM media.  Also the F fieldE unit of a MSF CD-ROM address.  The term frame is also used in the CD-h9 ROM model to describe the amount of data received betweenhF synchronization patterns. 98 of these frames make a sector.  This sortB of frame is referred to as 'small frames' where the meaning is not clear from context.   E 14.4.13 hold track state:  When a CD-ROM device enters the hold track|D state the optical pick-up is maintained at an approximately constantD position on the media.  This allows a paused operation to be resumedD without latency due to seeking.  Rotational latency may be incurred, however.  E 14.4.14 index:  An index is a subdivision of a CD-ROM track.  A trackEF can have from 1 to 99 index numbers.  Index numbers within a track are sequential starting with 1.   E 14.4.15 lead-in area:  The area on a CD-ROM disc prior to track one.  @ The main channel in the lead-in area contains audio or data nullE information.  This area is coded as track zero but is not addressableyG via the SCSI command set.  The Q sub-channel in this area is coded with " the table of contents information.  A 14.4.16 lead-out area:  The area on a CD-ROM disc beyond the lastrB information track.  The main channel in the lead-out area containsF audio or data null information.  This area is coded as track AAbcd butF is not addressable via the SCSI command set.  The READ CD-ROM CAPACITY? data is the first logical block address of this area minus one.|  G 14.4.17 L-EC; layered error correction:  The error correction technique F used with CD-ROM data mode one sectors.  In such sectors, 276 bytes ofE the auxiliary data field contain L-EC bytes.  The algorithm that usesCC these bytes to perform error correction is often implemented in ther drive firmware.   D 14.4.18 MSF address:  The physical address written on CD-ROM discs. C Expressed as a sector count relative to either the beginning of thedF medium (absolute) or to the beginning of the current track (relative).F As defined by the CD-DA and CD-ROM standards, each F field unit is oneD physical sector; each S field unit is 75 F field units; each M fieldG unit is 60 S field units.  Valid contents of F fields are binary values|G from 0 through 74.  Valid contents of S fields are binary values from 0C@ through 59.  Valid contents of M fields are binary values from 0 through 74.   C 14.4.19 output port:  A means for connecting the audio signal beingi. played to equipment outside the CD-ROM device.  D 14.4.20 pause area:  A transition area at the beginning or end of an@ audio track encoded with audio silence.  This transition area isA required where the audio track immediately precedes a data track.m  D 14.4.21 post-gap area:  A transition area at the end of a data trackF encoded with null information.  This transition area is required where3 the data track immediately precedes an audio track.e  C 14.4.22 pre-gap area:  A transition area at the beginning of a data F track encoded with null information.  This transition area is required8 where the data track immediately follows an audio track.  F 14.4.23 relative F field:  The sub-division of the S field part of theG relative physical address from the beginning of the current track.  One B physical sector.  Written on CD-ROM medium in binary coded decimal> notation.  The value is from 00bcd to 74bcd.  (See 14.4.12 and 14.4.18.)  .  D 14.4.24 relative M field:  The most significant part of the relativeE physical address from the beginning of the current track.  Written on5G CD-ROM media in binary coded decimal notation.  The value is from 00bcd  to 74bcd.  (See 14.4.18.)=  C 14.4.25 relative S field:  The intermediate significant part of therC relative physical address from the beginning of the current track. sE Written on CD-ROM medium in binary coded decimal notation.  The valuer' is from 00bcd to 59bcd.  (See 14.4.18.)I  E 14.4.26 sector:  Refers to the data contained during one frame time.  ? (On CD-DA medium with two channels of audio this is 1/75th of auD second).  In the CD-ROM standard document the term block is used forA this unit.  There may be more than one logical block per sector. r> Similarly, a single logical block may map to multiple sectors.  F 14.4.27 sub-channel:  CD-ROM and CD-DA media have a main channel and aE sub-channel.  The sub-channel area has eight parts called P, Q, R, S,eE T, U, V, and W.  The Q-sub-channel contains information useful to theoG controller and drive, such as the control field and MSF addresses.  ThenD data rate of each sub-channel (P, Q, etc.) is 1/192nd of that of the
 main channel.   G 14.4.28 TOC:  The table of contents has information on the type of discrG and the starting address of the tracks.  This information is encoded ino the Q sub-channel.    G 14.4.29 track:  A sub-division of the CD-ROM media. A disc has from oneoE to ninety-nine tracks.  The data within a track is always of the same E type.  A track can be either CD-ROM or CD-Audio.  A disc can start at= any track number.=  E 14.4.30 track relative logical address:  An offset from the beginning|@ of the recorded information on a track expressed in units of theB logical block length.  The value is used to address logical blocksC relative to the beginning of a track using the relative MSF address=$ encoded in the CD-ROM Q sub-channel.  C 14.4.31 transition area:  Sectors at the beginning or end of tracks-D coded with null information.  Where required by the media standards,D these areas have minimum lengths of 1 s or 2 s.  The maximum lengthsD are not specified.  Transition areas at the beginning of a track areF encoded with index zero.  Addresses within transition areas may not be read.a 15 Scanner devices     15.1 Model for scanner devices  C Scanner devices generate a digital representation of two- or three- E dimensional objects (e.g. a page of text, a photograph, or a piece of C art). This is accomplished by sensing the amount of light reflected-F from the object and generating the digital data.  The digital data can< then be sent across the SCSI bus to an initiator for further processing.-  G There are two types of scanners in use; in one type, the operations and E functions of the scanner are fixed; in the other type, the operations-C and functions are programmable and need to be set up prior to being  used for scanning objects.  D The scanner device generates the data and transfers it in accordanceC with the commands received from the initiator.  The contents of the F data is vendor-specific; therefore, the initiator and the scanner must) know how to use the contents of the data.=  C Scanners generate a digital image of an object in a two dimensionalhF plane.  The x-axis dimension is along the cross-scan direction that isB perpendicular to the direction in which a scan occurs.  The y-axisG dimension is along the scan direction, and is parallel to the directioneD in which a scan occurs.  The coordinates are measured from the upperF left hand corner of the two dimensional plane.  The x-axis measurementG increases in a positive manner going from left to right.  The left sidelE of the two dimensional plane (i.e. where x equals zero) is called theiB base element line.  The y-axis measurement increases in a positiveE manner going from top to bottom.  The top side of the two dimensional G plane (i.e. where y equals zero) is called the base line.  The scanningeE range encompasses the area in which the scanner can operate, from then? scan line and base line to the maximum x and y position.  TheserE conventions are adopted to aid in understanding the fields within thenF command descriptor blocks and parameters used for scanner devices.  AsB such this is a conceptual model and may not accurately reflect the physical device.  D The displacements used for positioning windows is independent of the> resolution with which a window is scanned.  The measurement ofD displacements is controlled by the scan measurement mode parameters.  D In the event of a scanner automatic creation of sub-windows within aD defined window (i.e. the auto bit in the DEFINE WINDOW parameters is4 one), one of the following responses is appropriate:J    a)     the initiator may issue a GET WINDOW PARAMETERS command prior to           any READ commands;E    b)     if the initiator issues a READ command before issuing a GEToB           WINDOW PARAMETERS command, the target shall return CHECKK           CONDITION status.  The ILI and valid bits in the sense data shall F           be set to one.  The initiator should then issue a GET WINDOWJ           PARAMETERS command.  This feature is useful when the scanner hasG           the ability to distinguish between image and text data and tog%           define windows accordingly.   F It may occur that a scanner device temporarily does not have resourcesG available to manage a data transfer from the initiator or does not haveiB data available to transfer to the initiator.  One of the following) responses is appropriate in such a case: eJ    a)     A CHECK CONDITION status is returned and the sense key is set toE           NOT READY with the appropriate additional sense code.  Thisd>           response is applicable to a TEST UNIT READY command.J    b)     The target disconnects until the resource or data are available,6           and then reconnects to resume the operation.$    c)     A BUSY status is returned.  E If the scanner device determines that an error or exception conditionyC has occurred while executing the SCSI command from the initiator, asE CHECK CONDITION status is returned.  A REQUEST SENSE command can thensB be used to determine additional information regarding the error or exception condition.    ! 15.2 Commands for scanner devicesc  @ The commands for scanner devices shall be as shown in table 277.  ;                    Table 277 - Commands for scanner devicescH +=====================================-============-======-============+H |  Command name                       | Operation  | Type |  Subclause |H |                                     |   code     |      |            |H |-------------------------------------+------------+------+------------|H | CHANGE DEFINITION                   |    40h     |   O  |   8.2.1    |H | COMPARE                             |    39h     |   O  |   8.2.2    |H | COPY                                |    18h     |   O  |   8.2.3    |H | COPY AND VERIFY                     |    3Ah     |   O  |   8.2.4    |H | GET DATA BUFFER STATUS              |    34h     |   O  |  15.2.1    |H | GET WINDOW                          |    25h     |   O  |  15.2.2    |H | INQUIRY                             |    12h     |   M  |   8.2.5    |H | LOG SELECT                          |    4Ch     |   O  |   8.2.6    |H | LOG SENSE                           |    4Dh     |   O  |   8.2.7    |H | MODE SELECT(6)                      |    15h     |   O  |   8.2.8    |H | MODE SELECT(10)                     |    55h     |   O  |   8.2.9    |H | MODE SENSE(6)                       |    1Ah     |   O  |   8.2.10   |H | MODE SENSE(10)                      |    5Ah     |   O  |   8.2.11   |H | OBJECT POSITION                     |    31h     |   O  |  15.2.3    |H | READ                                |    28h     |   M  |  15.2.4    |H | READ BUFFER                         |    3Ch     |   O  |   8.2.12   |H | RECEIVE DIAGNOSTIC RESULTS          |    1Ch     |   O  |   8.2.13   |H | RELEASE UNIT                        |    17h     |   M  |  10.2.9    |H | REQUEST SENSE                       |    03h     |   M  |   8.2.14   |H | RESERVE UNIT                        |    16h     |   M  |  10.2.10   |H | SCAN                                |    1Bh     |   O  |  15.2.5    |H | SET WINDOW                          |    24h     |   M  |  15.2.7    |H | SEND                                |    2Ah     |   O  |  15.2.6    |H | SEND DIAGNOSTIC                     |    1Dh     |   M  |   8.2.15   |H | TEST UNIT READY                     |    00h     |   M  |   8.2.16   |H | WRITE BUFFER                        |    3Bh     |   O  |   8.2.17   |H |----------------------------------------------------------------------|H |Key:  M = command implementation is mandatory.                        |H |      O = command implementation is optional.                         |H +======================================================================+    F All other operation codes for scanner devices are  reserved for future standardization.    % 15.2.1 GET DATA BUFFER STATUS command9  G The GET DATA BUFFER STATUS command (see table 278) provides a means for4G the initiator to get information about the data buffer.  Information istF returned only for window identifiers for which a SCAN command has been received (see 15.2.5).  <                   Table 278 - GET DATA BUFFER STATUS commandO +=====-========-========-========-========-========-========-========-========+kO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |eO |Byte |        |        |        |        |        |        |        |        |iO |=====+=======================================================================|aO | 0   |                           Operation code (34h)                        | O |-----+-----------------------------------------------------------------------|4O | 1   | Logical unit number      |            Reserved               |  Wait  |iO |-----+-----------------------------------------------------------------------|tO | 2   |                           Reserved                                    |tO |-----+-----------------------------------------------------------------------|iO | 3   |                           Reserved                                    |tO |-----+-----------------------------------------------------------------------|sO | 4   |                           Reserved                                    |eO |-----+-----------------------------------------------------------------------|hO | 5   |                           Reserved                                    |hO |-----+-----------------------------------------------------------------------|tO | 6   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|oO | 7   | (MSB)                                                                 |rO |-----+---                        Allocation length                        ---|hO | 8   |                                                                 (LSB) |hO |-----+-----------------------------------------------------------------------|lO | 9   |                           Control                                     |iO +=============================================================================+n    H A wait bit of zero indicates that the target shall respond immediately. E A wait bit of one indicates that the target shall wait for image data 4 to be available before returning scan status data.    ; The data buffer status data format is defined in table 279.h  9                     Table 279 - Data buffer status format O +=====-========-========-========-========-========-========-========-========+cO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |fO |Byte |        |        |        |        |        |        |        |        |tO |=====+=======================================================================|aO | 0   | (MSB)                                                                 |CO |-----+---                                                                 ---| O | 1   |                           Data buffer status length                   | O |-----+---                                                                 ---|cO | 2   |                                                                 (LSB) |.O |-----+-----------------------------------------------------------------------|5O | 3   |                           Reserved                           |  Block | O |=====+=======================================================================|pO |     |                           Data buffer status descriptor(s)            |rO |=====+=======================================================================|tO | 0   |                           Window identifier                           |yO |-----+-----------------------------------------------------------------------|rO | 1   |                           Reserved                                    |dO |-----+-----------------------------------------------------------------------|iO | 2   | (MSB)                                                                 |fO |-----+---                                                                 ---| O | 3   |                           Available data buffer                       |nO |-----+---                                                                 ---|xO | 4   |                                                                 (LSB) |cO |-----+-----------------------------------------------------------------------|aO | 5   | (MSB)                                                                 |aO |-----+---                                                                 ---|mO | 6   |                           Filled data buffer                          |dO |-----+---                                                                 ---|eO | 7   |                                                                 (LSB) |oO +=============================================================================+r    D The data buffer status length indicates the length, in bytes, of theE following scan status data that is available to be transferred duringeA the DATA IN phase. The data buffer status length does not includeiA itself.  The data buffer status data transferred to the initiatornF includes zero or more data buffer status descriptors.  Each descriptorF returns information for the window specified by the window identifier.  E The block bit specifies the buffering capabilities of the scanner.  A E block bit of one indicates that the data buffer is full and all imagelC data must be transferred to the initiator before the scan operationnC resumes.  A block bit of zero indicates that the data buffer is nottD full and scan operations can continue with the available data buffer space.  B The available data buffer field indicates, in bytes, the amount ofG buffer available for transfers from the initiator.  This field is validtF only in scanners with the ability to accept data from an initiator for
 processing.  o  B The filled data buffer field indicates the amount of image data in. bytes available for transfer to the initiator.   15.2.2 GET WINDOW commandn  ? The GET WINDOW command (see table 280) provides a means for thed> initiator to get information about previously defined windows.  6                         Table 280 - GET WINDOW commandO +=====-========-========-========-========-========-========-========-========+oO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |iO |Byte |        |        |        |        |        |        |        |        |fO |=====+=======================================================================| O | 0   |                           Operation code (25h)                        |oO |-----+-----------------------------------------------------------------------|UO | 1   | Logical unit number      |              Reserved             | Single |rO |-----+-----------------------------------------------------------------------| O | 2   |                           Reserved                                    |eO |-----+-----------------------------------------------------------------------|rO | 3   |                           Reserved                                    |uO |-----+-----------------------------------------------------------------------|oO | 4   |                           Reserved                                    |aO |-----+-----------------------------------------------------------------------|eO | 5   |                           Window identifier                           |=O |-----+-----------------------------------------------------------------------| O | 6   | (MSB)                                                                 |-O |-----+---                                                                 ---| O | 7   |                           Transfer length                             | O |-----+---                                                                 ---| O | 8   |                                                                 (LSB) |3O |-----+-----------------------------------------------------------------------||O | 9   |                           Control                                     | O +=============================================================================+     F A single bit of one specifies that a single window descriptor shall beC returned for the specified window identifier.  A single bit of zero.< specifies that window descriptors be returned for all window@ identifiers that were defined by a SET WINDOWS command or by the- target, if the automatic bit was set to one.    F The GET WINDOW data shall consist of a header (see table 281) followedD by one or more window descriptors.  Each window descriptor specifies: the location, size, and scanning method used for a window.  8                       Table 281 - Get window data headerO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |EO |Byte |        |        |        |        |        |        |        |        |EO |=====+=======================================================================| O | 0   | (MSB)                                                                 | O |-----+---                        Window data length                       ---| O | 1   |                                                                 (LSB) |2O |-----+-----------------------------------------------------------------------||O | 2   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|7O | 3   |                           Reserved                                    |KO |-----+-----------------------------------------------------------------------|=O | 4   |                           Reserved                                    |=O |-----+-----------------------------------------------------------------------|oO | 5   |                           Reserved                                    |TO |-----+-----------------------------------------------------------------------|)O | 6   | (MSB)                                                                 |IO |-----+---                        Window descriptor length                 ---| O | 7   |                                                                 (LSB) |TO +=============================================================================+-    E The window data length specifies the length in bytes of the following F data that is available to be transferred.  The window data length doesB not include itself.  If the allocation length is not sufficient toC return all the get window data, the window data length shall not be ) adjusted to reflect the truncation data.    F The window descriptor length specifies the length in bytes of a singleB window descriptor.  Each descriptor shall be of equal length.  TheF first forty-eight bytes are defined in this International Standard and; the remaining bytes in each descriptor are vendor-specific.   0 The window descriptors are defined in table 282.  8                      Table 282 - Window descriptor bytesO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |-O |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================|-O | 0   |                           Window identifier                           | O |-----+-----------------------------------------------------------------------|-O | 1   |                           Reserved                           |  Auto  | O |-----+-----------------------------------------------------------------------|-O | 2   | (MSB)                                                                 | O |-----+---                        X-Axis resolution                        ---|tO | 3   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|-O | 4   | (MSB)                                                                 | O |-----+---                        Y-Axis resolution                        ---|=O | 5   |                                                                 (LSB) |sO |-----+-----------------------------------------------------------------------|tO | 6   | (MSB)                                                                 |aO |- - -+- - -                      X-Axis upper left                      - - -| O | 9   |                                                                 (LSB) |=O |-----+-----------------------------------------------------------------------| O | 10  | (MSB)                                                                 | O |- - -+- - -                      Y-Axis upper left                      - - -|=O | 13  |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------| O | 14  | (MSB)                                                                 |tO |- - -+- - -                      Window width                           - - -| O | 17  |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|-O | 18  | (MSB)                                                                 | O |- - -+- - -                      Window length                          - - -|=O | 21  |                                                                 (LSB) |tO |-----+-----------------------------------------------------------------------|=O | 22  |                           Brightness                                  |fO |-----+-----------------------------------------------------------------------|-O | 23  |                           Threshold                                   | O |-----+-----------------------------------------------------------------------|-O | 24  |                           Contrast                                    | O |-----+-----------------------------------------------------------------------| O | 25  |                           Image composition                           |aO |-----+-----------------------------------------------------------------------| O | 26  |                           Bits per pixel                              | O |-----+-----------------------------------------------------------------------|-O | 27  | (MSB)                                                                 | O |-----+---                        Halftone pattern                         ---| O | 28  |                                                                 (LSB) |uO |-----+-----------------------------------------------------------------------| O | 29  |  RIF   |                  Reserved         |      Padding type        | O |-----+-----------------------------------------------------------------------|=O | 30  | (MSB)                                                                 | O |-----+---                        Bit ordering                             ---|sO | 31  |                                                                 (LSB) |iO |-----+-----------------------------------------------------------------------|rO | 32  |                           Compression type                            |oO |-----+-----------------------------------------------------------------------|uO | 33  |                           Compression argument                        |aO |-----+-----------------------------------------------------------------------|tO | 34  |                                                                       |iO |- - -+---                        Reserved                                 ---|cO | 39  |                                                                       |aO |-----+-----------------------------------------------------------------------|sO | 40  |                                                                       |lO |- - -+---                        Vendor-specific parameter byte(s)        ---|rO | n   |                                                                       |(O +=============================================================================+i    @ The window identifier specifies the window defined by the windowG descriptor. A window is referenced by the window identifier during data=  transfers and parameter updates.  E When used with the SET WINDOW command, an automatic (auto) bit of one E indicates that the target is allowed to create sub-windows within the G window specified.  An auto bit of zero indicates that the target is not= allowed to create sub-windows.  D When used with the GET WINDOW command, an auto bit of zero indicatesB that the window was defined directly by the SET WINDOW command.  AG value of one indicates that the window was defined by the target.  This|@ is a sub-window within a window defined by a SET WINDOW command.  G The window identifiers assigned by the target shall be unique and shall C not be currently in use.  The parameters for the sub-windows may be-' retrieved using the GET WINDOW command.-  E The x-axis resolution field specifies the resolution in the scan line G direction.  The unit of measure is picture elements (pixels) per inch. -3 A value of zero specifies the default resolution.     E The y-axis resolution field specifies the resolution in the base line-C direction.  The unit of measure is scan lines per inch.  A value of ( zero specifies the default resolution.    B The x-axis upper left field specifies the x-axis coordinate of theF upper left corner of the window.  This coordinate is measured from theB scan line using the target's current measurement unit divisor (see
 15.3.3.1).  B The y-axis upper left field specifies the y-axis coordinate of theF upper left corner of the window.  This coordinate is measured from the> base line using target's current measurement unit divisor (see
 15.3.3.1).  E The window width field specifies the width of window in the scan line C direction.  The window width is measured using the target's current-( measurement unit divisor (see 15.3.3.1).  F The window length field specifies the length of the window in the baseA line direction.  The window length is measured using the target's 0 current measurement unit divisor (see 15.3.3.1).  G The brightness field specifies the level of brightness used to scan thelF object.  A value of zero specifies the default brightness or automaticD brightness control, if it is supported.  Any other value indicates aD relative brightness setting, with 255 being the highest setting, one< being the lowest setting, and 128 being the nominal setting.  A The threshold field specifies the threshold at which scan data isa@ converted to binary data.  A value of zero specifies the defaultG threshold or automatic threshold control if it is supported.  Any other=F value indicates relative threshold setting, with 255 being the highest@ setting, one being the lowest setting, and 128 being the nominal setting.  C The contrast field specifies the level of contrast used to scan the=D object.  A value of zero specifies the default contrast or automaticB contrast control, if it is supported.  Any other value indicates aB relative contrast setting, with 255 being the highest setting, one< being the lowest setting, and 128 being the nominal setting.  D The halftone field specifies the level of halftone at which the scanG data is converted to binary data.  The values in this field are vendor- C specific.  The halftone field is used in conjunction with the image  composition field.  @ The image composition field specifies the type of scan operationC requested.  The image composition is defined as shown in table 283.   8                      Table 283 - Image composition codes: +=============-==========================================+: |    Code     |  Description                             |: |-------------+------------------------------------------|: |     00h     |  Bi-level black & white                  |: |     01h     |  Dithered/halftone black & white         |: |     02h     |  Multi-level black & white (gray scale)  |: |     03h     |  Bi-level RGB colour                     |: |     04h     |  Dithered/halftone RGB colour            |: |     05h     |  Multi-level RGB colour                  |: |  06h - FFh  |  Reserved                                |: +========================================================+    G The bits per pixel field specifies the number of bits used to represent ! the intensity of a single colour.a  D A reverse image format (RIF) bit of zero indicates that white pixelsE are indicated by zeros and black pixels are indicated by ones.  A RIFtF bit of one indicates that white pixels are to be indicated by ones andE black pixels are to be indicated by zeros.  The RIF bit is applicablet3 only for images represented by one bit per pixel.  a  C The padding type field specifies how the target shall pad the imagerD data transmitted to the initiator if it is not an integral number of1 bytes.  The padding type is defined in table 284.d  3                           Table 284 - Padding types 1 +=============-=================================+=1 |    Code     |  Description                    |=1 |-------------+---------------------------------| 1 |     00h     |  No padding                     |B1 |     01h     |  Pad with 0's to byte boundary  | 1 |     02h     |  Pad with 1's to byte boundary  |=1 |     03h     |  Truncate to byte boundary      |=1 |  04h - FFh  |  Reserved                       |t1 +===============================================+-    G The bit ordering field specifies the order in which data is transferred F to the host from the window.  The bit ordering specifies the directionE of pixels in a scan line, the direction of scan lines within a window-G and the image data packing within a byte.  The values in this field are  vendor-specific.    @ The compression type and compression argument fields specify theF compression technique to be applied to the image data (see table 285).  <                  Table 285 - Compression types and argumentsO +=============-===============================================-===============+ O | Compression |  Description                                  |  Compression  |sO |   code      |                                               |   argument    | O |-------------+-----------------------------------------------+---------------|-O |     00h     |  No compression                               |   Reserved    | O |     01h     |  CCITT group III, 1 dimensional               |   Reserved    |pO |     02h     |  CCITT group III, 2 dimensional               |   K factor    | O |     03h     |  CCITT group IV, 2 dimensional                |   Reserved    |-O |  04h - 0Fh  |  Reserved                                     |   Reserved    | O |     10h     |  Optical character recognition (OCR)          |Vendor-specific|pO |  11h - 7Fh  |  Reserved                                     |   Reserved    | O |  80h - FFh  |  Vendor-specific                              |Vendor-specific|-O +=============================================================================+      15.2.3 OBJECT POSITION command  @ The OBJECT POSITION command (see table 286) provides positioningE functions.  Absolute as well as relative positioning is provided.   A C target shall return CHECK CONDITION status and set the sense key to-B ILLEGAL REQUEST if a positioning function is requested that is not
 supported.  8                      Table 286 - OBJECT POSITION commandO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |-O |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================|-O | 0   |                           Operation code (31h)                        | O |-----+-----------------------------------------------------------------------|-O | 1   | Logical unit number      |    Reserved     |      Position function   | O |-----+-----------------------------------------------------------------------|-O | 2   | (MSB)                                                                 | O |-----+---                                                                 ---|-O | 3   |                           Count                                       | O |-----+---                                                                 ---|-O | 4   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------| O | 5   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|-O | 6   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|-O | 7   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------| O | 8   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|-O | 9   |                           Control                                     | O +=============================================================================+-    G The position function field specifies the requested function (see table  287).   5                         Table 287 - Position function ( +=============-========================+( |  Position   |  Description           |( |  function   |                        |( |-------------+------------------------|( |    000b     |  Unload object         |( |    001b     |  Load object           |( |    010b     |  Absolute positioning  |( |    011b     |  Relative positioning  |( |    100b     |  Rotate object         |( |    101b     |  Reserved              |( |    110b     |  Reserved              |( |    111b     |  Reserved              |( +======================================+    J    a)     Unload Object.  This position function specifies that the objectK           shall be positioned for removal.  If upon receipt of this command=L           there is no object loaded, the target shall return a GOOD status. E           This condition shall not be considered as an error.  If thedK           target is unable to unload the object (i.e. paper jam or mis-feedhH           condition), the target shall return CHECK CONDITION status and2           set the sense key sense to MEDIUM ERROR.  K    b)     Load object.  This position function specifies that the object islK           to be loaded and positioned to the base line.  If upon receipt ofoI           this command there is a object already loaded, the target shallDI           returns GOOD status.  This condition shall not be considered asaK           an error.  If an object is not loaded and the target is unable to.H           load an object, the target shall return CHECK CONDITION statusG           and set the EOM bit to one and the sense key to MEDIUM ERROR.   J    c)     Absolute positioning.  This position function specifies that theK           object is to be positioned at a y-axis displacement from the baseuF           line.  The y-axis displacement is determined using the countF           field and the target's current measurement unit divisor (seeG           15.3.3.1).  A count field of zero positions the object at the            base line.    C        Any other value in the count field shall cause the target to @        position the object that number of units in the scan lineJ        direction.  If there is no object loaded or if the specified y-axisB        displacement is not achieved, the target shall return CHECKG        CONDITION status and set the EOM bit to one and the sense key to.        MEDIUM ERROR.  J    d)     Relative positioning.  This position function specifies that theI           object is to be positioned at a y-axis displacement relative tohF           the current position.  The y-axis displacement is determinedI           using the count field and the target's current measurement unitiI           divisor (see 15.3.3.1).  A count field of zero causes no changen&           in position of the object.    D        A positive value in the count field shall cause the target to@        position the object that number of units in the scan lineI        direction.  If the scan range is exceeded, the target shall returncJ        CHECK CONDITION status.  The EOM bit is set to one,  the ILI bit isG        set to one, and the sense key is set to MEDIUM ERROR.  The validiA        bit is set to one and the information bytes are set to thefF        difference (residue) between the requested count and the actual        number of units moved.  t  J        A negative value (e.g. twos complement notation) in the count fieldI        shall cause the target to position the object that number of unitsnD        toward the base line.  If there is no object loaded or if theF        specified y-axis displacement is not achieved, the target shallG        return CHECK CONDITION status and set the EOM bit to one and thetG        sense key to MEDIUM ERROR.  If the base line is encountered, thecI        target shall position the object at the base line and return CHECKsH        CONDITION status.  The ILI bit is set to one and the sense key is@        set to MEDIUM ERROR.  The valid bit is set to one and theH        information bytes are set to the difference (residue) between the<        requested count and the actual number of units moved.  J    e)     Rotate object.  This position function specifies that the object@           is rotated in an anti-clockwise direction expressed inK           thousandths of a degree.  The count field specifies the number of=/           units that the object is to be moved.   H        The count field is used with the position function to specify the"        displacement of the object.   15.2.4 READ command   G The READ command (see table 288) requests that the target transfer data& to the initiator.   3                            Table 288 - READ command|O +=====-========-========-========-========-========-========-========-========+tO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |=O |=====+=======================================================================|eO | 0   |                           Operation code (28h)                        |oO |-----+-----------------------------------------------------------------------| O | 1   | Logical unit number      |             Reserved                       |dO |-----+-----------------------------------------------------------------------|iO | 2   |                           Data type code                              |eO |-----+-----------------------------------------------------------------------|hO | 3   |                           Reserved                                    |yO |-----+-----------------------------------------------------------------------|lO | 4   | (MSB)                                                                 |CO |-----+---                        Data type qualifier                      ---|-O | 5   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|aO | 6   | (MSB)                                                                 |rO |-----+---                                                                 ---| O | 7   |                           Transfer length                             |tO |-----+---                                                                 ---|aO | 8   |                                                                 (LSB) |iO |-----+-----------------------------------------------------------------------|eO | 9   |                           Control                                     |bO +=============================================================================+r    C The transfer data type distinguishes between the different types of=G data that may be transferred between the initiator and the target.  The . types of transfers are specified in table 289.  4                          Table 289 - Data type codes# +=============-===================+-# |    Code     |  Description      |-# |-------------+-------------------| # |     00h     |  Image            | # |     01h     |  Vendor-specific  | # |     02h     |  Halftone mask    |s# |     03h     |  Gamma function   |p# |  04h - 7Fh  |  Reserved         | # |  80h - FFh  |  Vendor-specific  |r# +=================================+I    D The data type qualifier field provides a means to differentiate dataD transfers of the same data type code.  The values used in this field are vendor-specific. r  C The transfer length specifies the number of blocks the target shalleF transfer to the initiator during the DATA IN phase.  The block size isC the current block size in the mode parameters block descriptor (see=D 8.3.3).  A transfer length of zero is not considered an error and no data shall be transferred.    A If the target transfers less than transfer length blocks, a CHECKsD CONDITION status shall be returned.   The ILI bit is set to one, theA valid bit is set to one, and the information bytes are set to thetB difference (residue) between the requested transfer length and the% actual number of blocks transferred.    F This command shall be terminated with a status of RESERVATION CONFLICTD if any reservation access conflict (see 10.2.10) exists, and no data shall be transferred.    15.2.5 SCAN command   A The SCAN command (see table 290) requests the target begin a scan 
 operation.  3                            Table 290 - SCAN command=O +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |-O |Byte |        |        |        |        |        |        |        |        ||O |=====+=======================================================================|-O | 0   |                           Operation code (1Bh)                        | O |-----+-----------------------------------------------------------------------| O | 1   | Logical unit number      |                  Reserved                  | O |-----+-----------------------------------------------------------------------| O | 2   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|-O | 3   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|-O | 4   |                           Transfer length                             | O |-----+-----------------------------------------------------------------------|-O | 5   |                           Control                                     | O +=============================================================================+-    ? The transfer length specifies the length in bytes of the window @ identifier list that shall be sent during the DATA OUT phase.  AE transfer length of zero indicates that no data shall be transferred. -0 This condition shall not be considered an error.  G The window identifier list consists of zero or more window identifiers,=0 each of which specifies a window to be scanned.      15.2.6 SEND commandp  E The SEND command (see table 291) transfers data from the initiator to  the target.   3                            Table 291 - SEND command=O +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |tO |Byte |        |        |        |        |        |        |        |        |oO |=====+=======================================================================|bO | 0   |                           Operation code (2Ah)                        |eO |-----+-----------------------------------------------------------------------|=O | 1   | Logical unit number      |             Reserved                       |sO |-----+-----------------------------------------------------------------------|tO | 2   |                           Data type code                              | O |-----+-----------------------------------------------------------------------| O | 3   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|eO | 4   | (MSB)                                                                 |uO |-----+---                        Data type qualifier                      ---|eO | 5   |                                                                 (LSB) |yO |-----+-----------------------------------------------------------------------|nO | 6   | (MSB)                                                                 |gO |-----+---                                                                 ---|OO | 7   |                           Transfer length                             | O |-----+---                                                                 ---| O | 8   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------| O | 9   |                           Control                                     |oO +=============================================================================+A    B The data type code and data type qualifier are defined in the READ command (see 15.2.4).   C The transfer length specifies the number of blocks the target shalltF transfer from the initiator during the DATA OUT phase.  The block sizeF is the current block size in the mode parameters block descriptor (seeD 8.3.3).  A transfer length of zero is not considered an error and no data shall be transferred.    F This command shall be terminated with a status of RESERVATION CONFLICTD if any reservation access conflict (see 10.2.10) exists, and no data shall be transferred.i   15.2.7 SET WINDOW command   ? The SET WINDOW command (see table 292) provides a means for the E initiator to specify one or more windows within the scanning range of  the device.t  6                         Table 292 - SET WINDOW commandO +=====-========-========-========-========-========-========-========-========+tO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |sO |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================| O | 0   |                           Operation code (24H)                        |eO |-----+-----------------------------------------------------------------------|mO | 1   | Logical unit number      |                  Reserved                  |fO |-----+-----------------------------------------------------------------------| O | 2   |                           Reserved                                    |iO |-----+-----------------------------------------------------------------------|OO | 3   |                           Reserved                                    |RO |-----+-----------------------------------------------------------------------|cO | 4   |                           Reserved                                    |tO |-----+-----------------------------------------------------------------------|oO | 5   |                           Reserved                                    |nO |-----+-----------------------------------------------------------------------|oO | 6   | (MSB)                                                                 |tO |-----+---                                                                 ---|.O | 7   |                           Transfer length                             | O |-----+---                                                                 ---|yO | 8   |                                                                 (LSB) |aO |-----+-----------------------------------------------------------------------| O | 9   |                           Control                                     |=O +=============================================================================+     D The transfer length specifies the length, in bytes, of the data thatC shall be sent during the DATA OUT phase.  A transfer length of zero=D indicates that no window parameters data shall be transferred.  This+ condition shall not be considered an error.o  G The window parameters data shall consist of a header followed by one or-> more window descriptors.  Each window descriptor specifies the8 location, size, and scanning method used for a window.    3 The set window data header is defined in table 293.-  8                       Table 293 - Set window data headerO +=====-========-========-========-========-========-========-========-========+-O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |-O |=====+=======================================================================| O | 0   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------| O | 1   |                           Reserved                                    |-O |-----+-----------------------------------------------------------------------| O | 2   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------| O | 3   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------| O | 4   |                           Reserved                                    |-O |-----+-----------------------------------------------------------------------| O | 5   |                           Reserved                                    |=O |-----+-----------------------------------------------------------------------|dO | 6   | (MSB)                                                                 |nO |-----+---                        Window descriptor length                 ---|8O | 7   |                                                                 (LSB) |=O +=============================================================================+-    A The window descriptor length specifies the length, in bytes, of a-E single window descriptor.  Each descriptor shall be of equal length. mE The first 48 bytes are defined in this International Standard and the 7 remaining bytes in each descriptor are vendor-specific.I  8 See table 282 for the definition of a window descriptor.  # 15.3 Parameters for scanner devicesa     15.3.1 Diagnostic parameters  ? This subclause defines the descriptors and pages for diagnostic & parameters used with scanner devices.   G The diagnostic page codes for scanner devices are defined in table 294.   7                       Table 294 - Diagnostic page codes(O +=============-==================================================-============+sO |  Page code  |  Description                                     | Subclause  |sO |-------------+--------------------------------------------------+------------| O |     00h     |  Supported diagnostic pages                      |  8.3.1.1   |eO |  01h - 7Fh  |  Reserved                                        |            |nO |  80h - FFh  |  Vendor-specific pages                           |            |IO +=============================================================================+e     15.3.2 Log parametersA  C This subclause defines the descriptors and pages for log parametersn used with scanner devices.    @ The log page codes for scanner devices are defined in table 295.  4                           Table 295 - Log page codesO +=============-==================================================-============+ O |  Page code  |  Description                                     | Subclause  | O |-------------+--------------------------------------------------+------------|=O |     01h     |  Buffer over-run/under-run page                  |  8.3.2.1   | O |     03h     |  Error counter page (read) page                  |  8.3.2.2   |-O |     07h     |  Last n error events page                        |  8.3.2.3   | O |     06h     |  Non-medium error page                           |  8.3.2.4   |-O |     00h     |  Supported log pages                             |  8.3.2.5   | O |  08h - 2Fh  |  Reserved                                        |            |-O |     3Fh     |  Reserved                                        |            | O |  30h - 3Eh  |  Vendor-specific pages                           |            |-O +=============================================================================+      15.3.3 Mode parameters  D This subclause defines the descriptors and pages for mode parameters used with scanner devices.    E The mode parameter list, including the mode parameter header and mode=& block descriptor, is defined in 8.3.3.  D The medium-type code field is contained in the mode parameter header: (see 8.3.3).  This field is reserved for scanners devices.  F The device specific parameter field is contained in the mode parameter@ header (see 8.3.3).  This field is reserved for scanner devices.  ? The density code field is contained in the mode parameter block=A descriptor (see table 8.3.3).  This field is reserved for scanner  devices.  A The mode page codes for scanner devices are defined in table 296.t  4                          Table 296 - Mode page codesO +=============-==================================================-============+=O |  Page code  |  Description                                     | Subclause  | O |-------------+--------------------------------------------------+------------| O |     0Ah     |  Control mode page                               |  8.3.3.1   |=O |     02h     |  Disconnect-reconnect page                       |  8.3.3.2   | O |     03h     |  Measurement units page                          | 15.3.3.1   |-O |     09h     |  Peripheral device page                          |  8.3.3.3   | O |     01h     |  Reserved                                        |            |-O |  03h - 08h  |  Reserved                                        |            | O |  0Bh - 1Fh  |  Reserved                                        |            |-O |     00h     |  Vendor-specific (does not require page format)  |            | O |  20h - 3Eh  |  Vendor-specific (page format required)          |            |-O |     3Fh     |  Return all pages                                |            | O |             |     (valid only for the MODE SENSE command)      |            | O +=============================================================================+      15.3.3.1 Measurement units page-  A The measurement units page (see table 297) specifies the units of C measurement used for calculating the displacement of window and for  positioning an object.  D The measurement units are independent of the horizontal and vertical scan resolutions.     8                       Table 297 - Measurement units pageO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |-O |Byte |        |        |        |        |        |        |        |        | O |=====+========+========+=====================================================|=O | 0   |   PS   |Reserved|         Page code (03h)                             |aO |-----+-----------------------------------------------------------------------|)O | 1   |                           Parameter length (06h)                      |fO |-----+-----------------------------------------------------------------------|bO | 2   |                           Basic measurement unit                      |hO |-----+-----------------------------------------------------------------------|cO | 3   |                           Reserved                                    |iO |-----+-----------------------------------------------------------------------|5O | 4   | (MSB)                                                                 |nO |-----+---                        Measurement unit divisor                 ---| O | 5   |                                                                 (LSB) |=O |-----+-----------------------------------------------------------------------| O | 6   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|=O | 7   |                           Reserved                                    | O +=============================================================================+-    @ The parameters savable (PS) bit is only used with the MODE SENSEE command.  This bit is reserved for the MODE SELECT command.  A PS bit C of one indicates that the target is capable of saving the page in a-& non-volatile vendor-specific location.  B The basic measurement unit field is defined in table 298.  Targets7 shall use inches as the default basic measurement unit.-  8                      Table 298 - Basic measurement units +=============-===============+  |    Code     |  Description  |- |-------------+---------------|- |     00h     |  Inch         |  |     01h     |  Millimetre   |  |     02h     |  Point        |  |  03h - FFh  |  Reserved     |- +=============================+-    D The measurement unit divisor specifies the number of units needed toA equal one basic measurement unit.  Targets shall use 1 200 as the-F default measurement unit divisor.  If a value of zero is specified theC target shall return CHECK CONDITION status and set the sense key to  ILLEGAL REQUEST.  G    NOTE 194 A target that does not implement this page or only supports K    default values uses twelve hundredths (1/1200) of an inch as the unit of     measure.   , 15.4 Definitions specific to scanner devices  @ 15.4.1 base element line:  An x-axis displacement equal to zero.  8 15.4.2 base line:  An y-axis displacement equal to zero.  G 15.4.3 beginning-of-medium:  A x-axis and y-axis of zero displacement.  F Alternatively this is being positioned at the intersection of the base and scan lines.=  B 15.4.4 end-of-medium:  The maximum x-axis and y-axis displacement.  , 15.4.5 image:  The digital result of a scan.  3 15.4.6 object:  The original or item being scanned.i  D 15.4.7 pixel:  Picture-element, which is the smallest photo sight in
 the array.  > 15.4.8 platen:  The surface on which the target is positioned.  B 15.4.9 scan:  An operation that generates a digital image from the reflected light of an object.   = 15.4.10 scan line:  A y-axis displacement from the base line.e  F 15.4.11 scanning range:  The total area that a scanner can generate anC image from.  For two dimensional objects this may correspond to the=# largest object that can be scanned.=  D 15.4.12 window:   All or part of the scanning range of a scanner.  A. window defines the part of the object scanned.       Optical memory devices    % 16.1 Model for optical memory devices=  C An optical memory device is a device that can potentially support a C variety of optical media, (e.g. read-only, write-once, erasable, or F reversible).  In several respects, an optical memory device is similarE to a direct-access device.  However, optical memory devices typically C offer features that are not available with other devices, including-% very large capacity removable media.    G These devices often require the functions that are not found in direct--? access devices such as logical block update, pre-erasure before-= writing, or scanning for blank medium and twelve-byte command  descriptor blocks.  A This standard has specific device types for write-once and CD-ROM-F devices that also use optical media, but are not capable of supportingD several types of optical media.  A device that uses write-once mediaF can be an optical memory device.  Devices that use read-only media canC be optical memory devices; however, devices using CD-ROM media have-G certain unique characteristics and should not be implemented as optical  memory devices.   E A model of optical memory devices is complicated by the nature of one @ of its potential advantages, that it can support media which hasE different characteristics.  There are three types of optical media in G general use, read-only, write-once and reversible.  Read-only media are=E typically used for publishing applications requiring dissemination of,D large amounts of data, since the data can be replicated on a disk atD low cost.  Write-once media are used in applications that have largeG backup or archiving requirements.  It is also used in applications thatfF need large amounts of on-line reference information.  Reversible mediaF is typically used in applications that need large amounts of temporary@ storage (e.g. a graphics workstation), and can take advantage ofC removable media.  In some applications, reversible media drives are ' used in place of direct-access devices.   E Reversible media usually need to be reversed (erased, blanked) before=F new data can be written.  In such cases an erase operation is requiredE before data can be written.  Some optical memory devices perform thisuA erase operation implicit with each write operation that typically-@ impacts the data throughput. Some devices can perform the erase H separately.  The ERASE command may be used to erase areas of the medium D with a corresponding increase in data throughput on subsequent writeF operations.  Products using optical media should not be implemented asF direct-access devices, due to the overhead penalty on performance fromF the emulation and the lack of support in direct-access devices to takeE advantage of the sophisticated features available with optical memoryd
 devices.    A The type of medium supported by the device and the type of mediumlE currently loaded can be determined by examining the MODE SENSE data. =E One unique feature of optical memory devices is support of media with B mixed types (e.g. media with read-only and write-once areas).  TheC INQUIRY command informs the initiator that the target is an optical G memory device; the initiator should then determine the medium type from C the MODE SENSE data.  The initiator needs to be cognizant of medium.E type since the device's characteristics can change when the media are  changed.  F Write-once media can have valid data written to a logical block once. F This is an important feature where audit trails and permanent archivesD are needed.  Many optical memory devices supporting write-once mediaC have the ability to update a logical block, preserving the previous E generation of data.  These devices usually provide a means to recoveroG the previous data through use of commands that allow read access to the=G different generations of data that are stored at the same logical block5 address.  E An important requirement in dealing with optical media is determiningaG which logical blocks contain written data and which are blank.  A blankiF logical block is one that is properly initialized so that data written? to it can be recovered.  The logical blocks usually have a flagaE associated with each that indicates whether they have been written or. not.    C Many of the strategies used to manage write once and erasable mediadB depend on being able to determine the boundary between written and@ blank areas of the medium.  The MEDIUM SCAN command is useful in4 finding blank areas for subsequent write operations.   16.1.1 Defect management  E Defect management can be performed on logical blocks by updating in a F manner similar to that used by direct-access devices with the REASSIGNB BLOCKS command.  The advantage of using the updating (which is notC supported by direct-access devices) is access to the previous data.-  G The update operation assigns an alternate physical block to the logical-G block while simultaneously writing the data to the block.  commands are.A provided to allow the recovery of previous generations of updated  blocks.|  H Defect management on optical-memory devices is usually vendor-specific. G However there are standards for some types of optical-memory media that B specify defect management techniques.  These standards, where theyB exist, may supersede the implementation requirements pertaining to: error and defect reporting in this International Standard.   16.1.2 Error reporting  B If any of the following conditions occur during the execution of a< command the target shall return CHECK CONDITION status.  TheC appropriate sense key and additional sense code should be set.  The|C following list illustrates some error conditions and the applicable G sense keys.  The list does not provide an exhaustive enumeration of allS5 conditions that may cause the CHECK CONDITION status.=  b Condition                                                                                Sense Keyn Invalid logical block address                                                                          ILLEGALn                                                                                                        REQUEST  j Unsupported option requested                                                                       ILLEGALj                                                                                                    REQUEST  { Target reset or medium change since last command from this initiator                                                       =    UNIT ATTENTION=  o Self diagnostic failed                                                                                 HARDWARE l                                                                                                        ERROR  o Unrecovered read error                                                                             MEDIUM ERROR-`                                                                                   HARDWARE ERROR  o Recovered read error                                                                            RECOVERED ERROR   z Overrun or other error that might be resolved by repeating the command                                                     ABORTED command-  q Attempt to write on write protected medium                                                                   DATA t                                                                                                              PROTECT  t Attempt to read a blank or previously unwritten block                                                                BLANK CHECK   A Attempt to write a previously written block and blank checking is- enabled          BLANK CHECK  n Attempt to write on read-only medium                                                                      DATAq                                                                                                           PROTECTi    ? In the case of an invalid logical block address, the sense datarB information field shall be set to the logical block address of the first invalid address.  A In the case of an attempt to read a blank or previously unwritteneC block, the sense data information field shall be set to the logicalhE block address of the first blank block encountered.  The data read upe# to that block shall be transferred.=  B In the case of an attempt to write a previously written block whenF blank checking is enabled, the sense information field shall be set toC the logical block address of the first non-blank block encountered.   ( 16.2 Commands for optical memory devices  G The commands for optical memory devices shall be as shown in table 299.e  >                Table 299 - Commands for optical memory devicesH +=====================================-============-======-============+H |  Command name                       | Operation  | Type |  Subclause |H |                                     |   code     |      |            |H |-------------------------------------+------------+------+------------|H | CHANGE DEFINITION                   |    40h     |   O  |   8.2.1    |H | COMPARE                             |    39h     |   O  |   8.2.2    |H | COPY                                |    18h     |   O  |   8.2.3    |H | COPY AND VERIFY                     |    3Ah     |   O  |   8.2.4    |H | ERASE(10)                           |    2Ch     |   O  |  16.2.1    |H | ERASE(12)                           |    ACh     |   O  |  16.2.2    |H | FORMAT UNIT                         |    04h     |   O  |   9.2.1    |H | INQUIRY                             |    12h     |   M  |   8.2.5    |H | LOCK UNLOCK CACHE                   |    36h     |   O  |   9.2.2    |H | LOG SELECT                          |    4Ch     |   O  |   8.2.6    |H | LOG SENSE                           |    4Dh     |   O  |   8.2.7    |H | MEDIUM SCAN                         |    38h     |   O  |  16.2.3    |H | MODE SELECT(6)                      |    15h     |   O  |   8.2.8    |H | MODE SELECT(10)                     |    55h     |   O  |   8.2.9    |H | MODE SENSE(6)                       |    1Ah     |   O  |   8.2.10   |H | MODE SENSE(10)                      |    5Ah     |   O  |   8.2.11   |H | PRE-FETCH                           |    34h     |   O  |   9.2.3    |H | PREVENT ALLOW MEDIUM REMOVAL        |    1Eh     |   O  |   9.2.4    |H | READ(6)                             |    08h     |   O  |   9.2.5    |H | READ(10)                            |    28h     |   M  |   9.2.6    |H | READ(12)                            |    A8h     |   O  |  16.2.4    |H | READ BUFFER                         |    3Ch     |   O  |   8.2.12   |H | READ CAPACITY                       |    25h     |   M  |   9.2.7    |H | READ DEFECT DATA(10)                |    37h     |   O  |   9.2.8    |H | READ DEFECT DATA(12)                |    B7h     |   O  |  16.2.5    |H | READ GENERATION                     |    29h     |   O  |  16.2.6    |H | READ LONG                           |    3Eh     |   O  |   9.2.9    |H | READ UPDATED BLOCK                  |    2Dh     |   O  |  16.2.7    |H | REASSIGN BLOCKS                     |    07h     |   O  |   9.2.10   |H | RECEIVE DIAGNOSTIC RESULTS          |    1Ch     |   O  |   8.2.13   |H | RELEASE                             |    17h     |   M  |   9.2.11   |H | REQUEST SENSE                       |    03h     |   M  |   8.2.14   |H | RESERVE                             |    16h     |   M  |   9.2.12   |H | REZERO UNIT                         |    01h     |   O  |   9.2.13   |H | SEARCH DATA EQUAL(10)               |    31h     |   O  |   9.2.14.1 |H | SEARCH DATA EQUAL(12)               |    B1h     |   O  |  16.2.8    |H | SEARCH DATA HIGH(10)                |    30h     |   O  |   9.2.14.2 |H | SEARCH DATA HIGH(12)                |    B0h     |   O  |  16.2.8    |H | SEARCH DATA LOW(12)                 |    B2h     |   O  |  16.2.8    |H | SEEK(6)                             |    0Bh     |   O  |   9.2.15   |H | SEEK(10)                            |    2Bh     |   O  |   9.2.15   |H | SEND DIAGNOSTIC                     |    1Dh     |   M  |   8.2.15   |H | SET LIMITS(10)                      |    33h     |   O  |   9.2.16   |H | SET LIMITS(12)                      |    B3h     |   O  |  16.2.9    |H | START STOP UNIT                     |    1Bh     |   O  |   9.2.17   |H | SYNCHRONIZE CACHE                   |    35h     |   O  |   9.2.18   |H | TEST UNIT READY                     |    00h     |   M  |   8.2.16   |H | UPDATE BLOCK                        |    3Dh     |   O  |  16.2.10   |H | VERIFY(10)                          |    2Fh     |   O  |  16.2.11   |H | VERIFY(12)                          |    AFh     |   O  |  16.2.12   |H | WRITE(6)                            |    0Ah     |   O  |   9.2.20   |H | WRITE(10)                           |    2Ah     |   M  |  16.2.13   |H | WRITE(12)                           |    AAh     |   O  |  16.2.14   |H | WRITE AND VERIFY(10)                |    2Eh     |   O  |  16.2.15   |H | WRITE AND VERIFY(12)                |    AEh     |   O  |  16.2.16   |H | WRITE BUFFER                        |    3Bh     |   O  |   8.2.17   |H | WRITE LONG                          |    3Fh     |   O  |   9.2.23   |H |----------------------------------------------------------------------|H |Key:  M = command implementation is mandatory.                        |H |      O = command implementation is optional.                         |H +======================================================================+    D The following codes are vendor-specific: 20h, 21h, 22h, 23h, and C0h@ through FFh.  All remaining codes for optical memory devices are$ reserved for future standardization.   16.2.1 ERASE(10) command  D The ERASE(10) command (see table 300) requests that the target eraseF the specified number of blocks starting at the specified logical blockD address on the medium.  As used here, erased means either the mediumA shall be erased, or a pattern shall be written on the medium thataE appears to the target as no data present.  The blocks erased shall bes@ considered blank for purposes of blank checking (see 16.1).  TheG previous data recorded on the medium, if any, shall not be recoverable.n  5                         Table 300 - ERASE(10) commandeO +=====-========-========-========-========-========-========-========-========+lO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |hO |Byte |        |        |        |        |        |        |        |        |nO |=====+=======================================================================|iO | 0   |                           Operation code (2Ch)                        |nO |-----+-----------------------------------------------------------------------|eO | 1   |   Logical unit number    |     Reserved    |  ERA   |Reserved| RelAdr |rO |-----+-----------------------------------------------------------------------|vO | 2   | (MSB)                                                                 |sO |-----+---                                                                 ---|cO | 3   |                                                                       |kO |-----+---                        Logical block address                    ---|eO | 4   |                                                                       |cO |-----+---                                                                 ---| O | 5   |                                                                 (LSB) |pO |-----+-----------------------------------------------------------------------|iO | 6   |                           Reserved                                    |nO |-----+-----------------------------------------------------------------------|CO | 7   | (MSB)                                                                 |bO |-----+---                        Transfer length                          ---| O | 8   |                                                                 (LSB) |tO |-----+-----------------------------------------------------------------------| O | 9   |                           Control                                     |iO +=============================================================================+     F The erase all (ERA) bit set to one indicates that all remaining blocksG on the medium shall be erased.  If the ERA bit is set to one and if thenF number of blocks is not zero, the target shall return CHECK CONDITION,E and the sense key shall be set to ILLEGAL REQUEST, with an additional # sense code of INVALID FIELD IN CDB.   G See 9.2.2 for a description of the RelAdr bit and logical block addresss field.  E The transfer length specifies the number of contiguous logical blocksTF that shall be erased when the ERA bit is zero.  If the ERA bit is zeroD a transfer length of zero indicates that no blocks shall be erased. D This condition shall not be considered an error and no data shall beD erased.  Any other value indicates the number of logical blocks that shall be erased.    F This command shall be terminated with a status of RESERVATION CONFLICTB if any reservation access conflict (see 9.2.12) exists and no data shall be erased.  H    NOTE 195 This command allows the user to separate the erase and writeM    operations.  This may increase system performance in certain applications.a   16.2.2 ERASE(12) command  D The ERASE(12) command (see table 301) requests that the target eraseF the specified number of blocks starting at the specified logical block address on the medium.  5                         Table 301 - ERASE(12) command O +=====-========-========-========-========-========-========-========-========+oO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |lO |=====+=======================================================================|eO | 0   |                           Operation code (ACh)                        | O |-----+-----------------------------------------------------------------------| O | 1   |   Logical unit number    |     Reserved    |  ERA   |Reserved| RelAdr |lO |-----+-----------------------------------------------------------------------| O | 2   | (MSB)                                                                 |nO |-----+---                                                                 ---|tO | 3   |                                                                       |dO |-----+---                        Logical block address                    ---|aO | 4   |                                                                       |fO |-----+---                                                                 ---|uO | 5   |                                                                 (LSB) |mO |-----+-----------------------------------------------------------------------|aO | 6   | (MSB)                                                                 |=O |-----+---                                                                 ---| O | 7   |                                                                       | O |-----+---                        Transfer length                          ---| O | 8   |                                                                       |RO |-----+---                                                                 ---| O | 9   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------| O | 10  |                           Reserved                                    | O |-----+-----------------------------------------------------------------------| O | 11  |                           Control                                     |MO +=============================================================================+.    E See the ERASE(10) command (16.2.1) for a description of the fields in.
 this command.E   16.2.3 MEDIUM SCAN command  C The MEDIUM SCAN command (see table 302) requests that the target to @ scan the medium for a contiguous set of written or blank logical	 blocks.     6                        Table 302 - MEDIUM SCAN commandO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================|OO | 0   |                            Operation code (38h)                       |.O |-----+-----------------------------------------------------------------------||O | 1   |  Logical unit number     |   WBS  |   ASA  |   RSD  |   PRA  | RelAdr |DO |-----+-----------------------------------------------------------------------|TO | 2   |  (MSB)                                                                |)O |-----+----                                                                ---| O | 3   |                                                                       | O |-----+----                      Logical block address                     ---|hO | 4   |                                                                       | O |-----+----                                                                ---| O | 5   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|EO | 6   |                            Reserved                                   | O |-----+-----------------------------------------------------------------------| O | 7   |                            Reserved                                   | O |-----+-----------------------------------------------------------------------| O | 8   |                            Parameter list length                      |3O |-----+-----------------------------------------------------------------------||O | 9   |                            Control                                    | O +=============================================================================+5    G A written block search (WBS) bit of zero indicates that the scan is for|F blank blocks.  A WBS bit of one indicates that the scan is for written blocks.   D An advanced scan algorithm (ASA) bit of zero indicates that the scanE area is scanned in sequential order (as selected by the RSD bit).  An G ASA bit of one indicates to the target that the written and blank areas E within the scan area form contiguous extents (as opposed to scattered 4 blocks).  This indication is advisory to the target.  H    NOTE 196 The purpose of this bit is to allow the target to use a moreG    advanced algorithm (such as a binary search) to locate the requestedO
    blocks.  C A reverse scan direction (RSD) bit of zero indicates the scan shall.E begin with the first logical block of the scan area. A RSD bit of one.F indicates the scan shall begin with the last logical block of the scan area.   F A partial results acceptable (PRA) bit of zero indicates that the scanE shall not be considered satisfied until a contiguous set of blocks is5G found within the scan area that is at least equal in size to the number6B of blocks requested, and meets the other criteria specified in theG command descriptor block.  A PRA bit of one indicates that the scan may G be satisfied by a contiguous set of blocks within the scan area that is-F less than the number of blocks requested, and meets the other criteria* specified in the command descriptor block.  G See 9.2.2 for a description of the RelAdr bit and logical block address= field.  > The parameter list length specifies the length in bytes of theF parameter list that shall be transferred during the DATA OUT phase.  AA parameter list length of zero indicates that the number of blockstD requested field has a value of one, and the number of blocks to scanE field has a value of zero.  This condition shall not be considered antF error.  The contents of the parameter list are specified in table 303.  :                     Table 303 - MEDIUM SCAN parameter listO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |eO |Byte |        |        |        |        |        |        |        |        |bO |=====+=======================================================================|=O | 0   | (MSB)                                                                 | O |-----+---                                                                 ---| O | 1   |                                                                       |=O |-----+---                        Number of blocks requested               ---| O | 2   |                                                                       |-O |-----+---                                                                 ---| O | 3   |                                                                 (LSB) |-O |-----+-----------------------------------------------------------------------| O | 4   | (MSB)                                                                 | O |-----+---                                                                 ---| O | 5   |                                                                       | O |-----+---                        Number of blocks to scan                 ---| O | 6   |                                                                       | O |-----+---                                                                 ---| O | 7   |                                                                 (LSB) |-O +=============================================================================+     A A link bit of zero indicates a non-linked command; if the scan is-H satisfied, the command shall be terminated with a CONDITION MET status. D A REQUEST SENSE command can then be issued to determine the startingF logical block address of the area that meets the request.  If the scanE is not satisfied and no error occurs, the command shall be terminated  with GOOD status.   G A link bit of one indicates that a command is linked to the MEDIUM SCAN-E command; if the search is satisfied, CONDITION MET status is returned @ and the next command is executed.  If the RelAdr bit in the nextE command is one, the logical block address of the next command is used D as a displacement from the logical block address at which the searchC was satisfied.    If a linked scan is not satisfied, the command isiF terminated with a CHECK CONDITION status.  A REQUEST SENSE command may then be issued.L  A A REQUEST SENSE command following a satisfied MEDIUM SCAN commandB shall:D    a)     return a sense key of EQUAL if the scan was satisfied by aH           contiguous set of blocks equal in size to the number of blocksJ           requested. If the PRA bis is one and the scan was satisfied by aA           contiguous set of blocks less than the number of blocksrD           requested, then a sense key of NO SENSE shall be returned;*    b)     return the valid bit set to one;H    c)     return the logical block address of the first logical block ofJ           the contiguous set of blocks that satisfied the scan criteria in            the information bytes;I    d)     return the number of contiguous logical blocks meeting the scan =           criteria in the command specific information bytes.   D A REQUEST SENSE command following an unsatisfied MEDIUM SCAN command shall:I    a)     return a sense key of NO SENSE if no errors occurred during thef           command execution;+    b)     return the valid bit set to zero.e  C The number of blocks requested field specifies the number of blocks=E that meet the specified requirements.  The number of blocks requested=E field, if set to zero, indicates that the scan shall not take place.  0 This shall not be considered an error condition.  D The number of blocks to scan field specifies the length in blocks ofC the area to be scanned on the medium.  The number of blocks to scan E field, if set to zero, indicates that the scan shall continue for all-C remaining blocks on the medium or until the scan is satisfied.  See-, 16.1.2 for a description of error reporting.   16.2.4 READ(12) commands  F The READ(12) command (see table 304) requests that the target transfer@ data to the initiator from the medium.  See the READ(10) commandA (9.2.6) for a complete description of the fields in this command.   5                          Table 304 - READ(12) command O +=====-========-========-========-========-========-========-========-========+-O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |-O |=====+=======================================================================| O | 0   |                           Operation code (A8h)                        |-O |-----+-----------------------------------------------------------------------| O | 1   |   Logical unit number    |   DPO  |   FUA  |     Reserved    | RelAdr |-O |-----+-----------------------------------------------------------------------| O | 2   | (MSB)                                                                 |-O |-----+---                                                                 ---| O | 3   |                                                                       |-O |-----+---                        Logical block address                    ---| O | 4   |                                                                       |-O |-----+---                                                                 ---| O | 5   |                                                                 (LSB) |-O |-----+-----------------------------------------------------------------------| O | 6   | (MSB)                                                                 |=O |-----+---                                                                 ---| O | 7   |                                                                       |mO |-----+---                        Transfer length                          ---|eO | 8   |                                                                       |aO |-----+---                                                                 ---| O | 9   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------| O | 10  |                           Reserved                                    | O |-----+-----------------------------------------------------------------------| O | 11  |                           Control                                     | O +=============================================================================+     # 16.2.5 READ DEFECT DATA(12) command   B The READ DEFECT DATA(12) command (see table 305) requests that theE target transfer the medium defect data to the initiator. See the READ G DEFECT DATA(10) command (9.2.8) for a description of the fields in this  command.  ;                    Table 305 - READ DEFECT DATA(12) command O +=====-========-========-========-========-========-========-========-========+-O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |-O |=====+=======================================================================| O | 0   |                           Operation code (B7h)                        |-O |-----+-----------------------------------------------------------------------| O | 1   |   Logical unit number    | Plist  | GList  | Defect list format       |-O |-----+-----------------------------------------------------------------------| O | 2   |                           Reserved                                    |-O |-----+-----------------------------------------------------------------------| O | 3   |                           Reserved                                    |-O |-----+-----------------------------------------------------------------------| O | 4   |                           Reserved                                    |=O |-----+-----------------------------------------------------------------------| O | 5   |                           Reserved                                    |lO |-----+-----------------------------------------------------------------------|vO | 6   | (MSB)                                                                 |nO |-----+---                                                                 ---| O | 7   |                                                                       |sO |-----+---                        Allocation length                        ---|tO | 8   |                                                                       |eO |-----+---                                                                 ---|oO | 9   |                                                                 (LSB) |iO |-----+-----------------------------------------------------------------------| O | 10  |                           Reserved                                    |uO |-----+-----------------------------------------------------------------------| O | 11  |                           Control                                     |sO +=============================================================================+c    F The READ DEFECT DATA(12) list header (see table 306) contains an eight9 byte header, followed by zero or more defect descriptors.   =                  Table 306 - READ DEFECT DATA(12) list headercO +=====-========-========-========-========-========-========-========-========+lO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |eO |=====+=======================================================================|nO | 0   |                           Reserved                                    |oO |-----+-----------------------------------------------------------------------|sO | 1   |          Reserved        | PList  | GList  | Defect list format       |iO |-----+-----------------------------------------------------------------------|=O | 2   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|BO | 3   |                           Reserved                                    |=O |-----+-----------------------------------------------------------------------| O | 4   | (MSB)                                                                 |-O |-----+---                                                                 ---| O | 5   |                                                                       |-O |-----+---                        Defect list length                          | O | 6   |                                                                       |-O |-----+---                                                                 ---| O | 7   |                                                                 (LSB) |-O |=============================================================================| O |                              Defect descriptors                             |-O |=====-=======================================================================| O | 0   |                                                                       |-O |-----+---                                                                 ---| O | n   |                                                                       |-O +=============================================================================+     E See the description of the READ DEFECT DATA defect list (see 9.2.1.1) / for a description of the fields in this header.=   16.2.6 READ GENERATION command  D The READ GENERATION command (see table 307) requests that the target@ transfer to the initiator the maximum generation address for the logical block specified.  8                      Table 307 - READ GENERATION commandO +=====-========-========-========-========-========-========-========-========+dO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |iO |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================|iO | 0   |                           Operation code (29h)                        |rO |-----+-----------------------------------------------------------------------|sO | 1   |   Logical unit number    |             Reserved              | RelAdr |mO |-----+-----------------------------------------------------------------------| O | 2   | (MSB)                                                                 |mO |-----+---                                                                 ---|aO | 3   |                                                                       | O |-----+---                        Logical block address                    ---|oO | 4   |                                                                       | O |-----+---                                                                 ---| O | 5   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------| O | 6   |                           Reserved                                    |sO |-----+-----------------------------------------------------------------------| O | 7   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------| O | 8   |                           Allocation length                           |rO |-----+-----------------------------------------------------------------------|eO | 9   |                           Control                                     |sO +=============================================================================+d    G See 9.2.2 for a description of the RelAdr bit and logical block addressf field.  1 The READ GENERATION data is defined in table 308.   ;                   Table 308 - Maximum generation data blockcO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |hO |=====+=======================================================================|sO | 0   | (MSB)                                                                 |RO |-----+---                       Maximum generation address                ---|=O | 1   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------| O | 2   |                          Reserved                                     |=O |-----+-----------------------------------------------------------------------| O | 3   |                          Reserved                                     |-O +=============================================================================+e    C The maximum generation address field defines the maximum generation-: address available for the logical block address specified.  % 16.2.7 READ UPDATED BLOCK(10) command   D The READ UPDATED BLOCK(10) command (see table 309) requests that theG target transfer data to the initiator from the specified generation and  logical block.  <                   Table 309 - READ UPDATED BLOCK(10) commandO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================|-O | 0   |                           Operation code (2Dh)                        | O |-----+-----------------------------------------------------------------------| O | 1   |   Logical unit number    |   DPO  |   FUA  |     Reserved    | RelAdr | O |-----+-----------------------------------------------------------------------| O | 2   | (MSB)                                                                 | O |-----+---                                                                 ---| O | 3   |                                                                       | O |-----+---                        Logical block address                    ---|-O | 4   |                                                                       | O |-----+---                                                                 ---|-O | 5   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|=O | 6   | Latest | (MSB)                                                        |FO |-----+------------               Generation address                          |mO | 7   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|RO | 8   |                           Reserved                                    |-O |-----+-----------------------------------------------------------------------||O | 9   |                           Control                                     ||O +=============================================================================+=    E See 9.2.6 for a description of the cache control bits (DPO and FUA). oG See 9.2.2 for a description of the RelAdr bit and logical block address- field.  : One block of data is transferred during the DATA IN phase.  G The latest bit determines the meaning of the generation address field. -G A latest bit of zero indicates that the generation address is specified F relative to the first generation of the block; generation address zero@ specifies the first generation.  Increasing generation addresses specify later generations.  F A latest bit of one indicates that the generation address is specifiedG relative to the latest generation of the block; generation address zero F specifies the most recent generation.  Increasing generation addresses specify earlier generations.  @ If the requested generation does not exist, the command shall beF terminated with CHECK CONDITION status.  The sense key shall be set toE BLANK CHECK, and the additional sense code shall be set to GENERATION- DOES NOT EXIST.   F This command shall be terminated with a status of RESERVATION CONFLICTB if any reservation access conflict (see 9.2.12) exists and no data shall be transferred.    16.2.8 SEARCH DATA(12) commands   G The SEARCH DATA(12) commands (see table 310) search one or more logical D blocks for equality or inequality to a data pattern.  See the SEARCHB DATA(10) commands (9.2.14) for a description of the fields in this command.  9                      Table 310 - SEARCH DATA(12) commandsoO +=====-========-========-========-========-========-========-========-========+iO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |uO |=====+=======================================================================| O | 0   |                           Operation code (B0h, B1h, B2h)              |sO |-----+-----------------------------------------------------------------------|cO | 1   |   Logical unit number    | Invert |    Reserved     | SpnDat | RelAdr |eO |-----+-----------------------------------------------------------------------|3O | 2   | (MSB)                                                                 |=O |-----+---                                                                 ---| O | 3   |                                                                       | O |-----+---                        Logical block address                    ---|=O | 4   |                                                                       |dO |-----+---                                                                 ---|-O | 5   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|-O | 6   | (MSB)                                                                 |dO |-----+---                                                                 ---|-O | 7   |                                                                       |dO |-----+---                        Transfer length                          ---|-O | 8   |                                                                       | O |-----+---                                                                 ---| O | 9   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|lO | 10  |                           Reserved                                    | O |-----+-----------------------------------------------------------------------| O | 11  |                           Control                                     | O +=============================================================================+=     16.2.9 SET LIMITS(12) command=  C The SET LIMITS(12) command (see table 311) defines the range within E which subsequent linked commands may operate.  See the SET LIMITS(10)=A command (9.2.16) for a description of the fields in this command.   8                       Table 311 - SET LIMITS(12) commandO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |=O |Byte |        |        |        |        |        |        |        |        |oO |=====+=======================================================================|eO | 0   |                           Operation code (B3h)                        |mO |-----+-----------------------------------------------------------------------|uO | 1   |   Logical unit number    |         Reserved         | RdInh  | WrInh  |bO |-----+-----------------------------------------------------------------------|=O | 2   | (MSB)                                                                 | O |-----+---                                                                 ---| O | 3   |                                                                       |=O |-----+---                        Logical block address                    ---|eO | 4   |                                                                       |-O |-----+---                                                                 ---|RO | 5   |                                                                 (LSB) |-O |-----+-----------------------------------------------------------------------| O | 6   | (MSB)                                                                 | O |-----+---                                                                 ---| O | 7   |                                                                       | O |-----+---                        Number of blocks                         ---| O | 8   |                                                                       | O |-----+---                                                                 ---| O | 9   |                                                                 (LSB) |-O |-----+-----------------------------------------------------------------------| O | 10  |                           Reserved                                    |-O |-----+-----------------------------------------------------------------------| O | 11  |                           Control                                     |-O +=============================================================================+n          16.2.10 UPDATE BLOCK command  A The UPDATE BLOCK command (see table 312) requests that the target-G logically replace data on the medium with the data sent during the DATA 
 OUT phase.  7                        Table 312 - UPDATE BLOCK command=O +=====-========-========-========-========-========-========-========-========+iO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |=O |=====+=======================================================================| O | 0   |                           Operation code (3Dh)                        | O |-----+-----------------------------------------------------------------------|=O | 1   |   Logical unit number    |            Reserved               | RelAdr | O |-----+-----------------------------------------------------------------------| O | 2   | (MSB)                                                                 | O |-----+---                                                                 ---|-O | 3   |                                                                       | O |-----+---                        Logical block address                    ---|-O | 4   |                                                                       | O |-----+---                                                                 ---|=O | 5   |                                                                 (LSB) |eO |-----+-----------------------------------------------------------------------| O | 6   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------| O | 7   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|=O | 8   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------| O | 9   |                           Control                                     |=O +=============================================================================+     G See 9.2.2 for a description of the RelAdr bit and logical block address- field.  < One block of data is transferred during the DATA OUT phase.   M    NOTE 197 See the MODE Parameters (16.3) for a description of the behaviour-L    of the UPDATE BLOCK command relative to the enable blank check (EBC) bit.  G This standard does not define the result of a WRITE command issued to a-G block previously updated by an UPDATE BLOCK command when blank checking-
 is disabled.    E    NOTE 198 It is recommended that the target inhibit this behaviour.-  @ A logical block may be updated until the alternate block area isD exhausted.  The alternate blocks used for the update operation shallF not be reported in the READ CAPACITY data. If the alternate block areaF is exhausted, the command shall be terminated with CHECK CONDITION andE the sense key shall be set to  MEDIUM ERROR, and the additional sense-/ code set to NO DEFECT SPARE LOCATION AVAILABLE.-  ? If the report updated block read parameter specifies posting of G recovered errors for a read operation of a logical block that has had a ? successful update operation performed, occurs the command shall G terminate with a CHECK CONDITION status.  The sense key shall be set to-B RECOVERED ERROR and the additional sense code set to UPDATED BLOCK READ.    16.2.11 VERIFY(10) command  F The VERIFY command (see table 313) requests that the target verify the data on the medium.-  4                           Table 313 - VERIFY commandO +=====-========-========-========-========-========-========-========-========+=O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |eO |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================|AO | 0   |                           Operation code (2Fh)                        |lO |-----+-----------------------------------------------------------------------|eO | 1   |   Logical unit number    |   DPO  |Reserved| BlkVfy | BytChk | RelAdr |hO |-----+-----------------------------------------------------------------------| O | 2   | (MSB)                                                                 |eO |-----+---                                                                 ---|oO | 3   |                                                                       |nO |-----+---                        Logical block address                    ---|dO | 4   |                                                                       |eO |-----+---                                                                 ---|aO | 5   |                                                                 (LSB) |aO |-----+-----------------------------------------------------------------------|SO | 6   |                           Reserved                                    |nO |-----+-----------------------------------------------------------------------| O | 7   | (MSB)                                                                 |nO |-----+---                        Verification length                         |-O | 8   |                                                                 (LSB) ||O |-----+-----------------------------------------------------------------------||O | 9   |                           Control                                     |=O +=============================================================================+     ? If the MODE SELECT command is implemented, and the Verify Error-G Recovery Parameters page is also implemented, then the current settings-B in that page define the verification criteria. If the Verify ErrorB Recovery Parameters page is not implemented, then the verification criteria is vendor unique.  D A byte check (BytChk) bit of zero causes a medium verification to beE performed with no data comparison. A BytChk bit of one causes a byte- > by-byte compare of the data written on the medium and the dataD transferred from the initiator.  The data shall be transferred as itF would be for a WRITE command.  If the compare is unsuccessful, for anyD reason, the target shall return CHECK CONDITION status and the sense key shall be set to MISCOMPARE.   A A blank verify (BlkVfy) bit of one causes a verification that the  blocks are blank.   > If the BytChk is one when the BlkVfy bit is one, this shall beG considered an error. The target shall return CHECK CONDITION status and G the sense key shall be set to ILLEGAL REQUEST, and the additional sense ! code set to INVALID FIELD IN CDB.   G See 9.2.6 for a description of the cache control bits (DPO).  See 9.2.2 D for a description of the RelAdr bit and logical block address field.  B The verification length specifies the number of contiguous logicalG blocks of data or blanks that shall be verified.  A verification length A of zero indicates that no logical blocks shall be verified.  This ? condition shall not be considered as an error.  Any other value > indicates the number of logical blocks that shall be verified.   16.2.12 VERIFY(12) command  F The VERIFY(12) command (see table 314) requests that the target verifyC the data on the medium.  See the VERIFY(10) command (16.2.11) for a-* description of the fields in this command.  6                         Table 314 - VERIFY(12) commandO +=====-========-========-========-========-========-========-========-========+=O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |1O |Byte |        |        |        |        |        |        |        |        |tO |=====+=======================================================================|aO | 0   |                           Operation code (AFh)                        |-O |-----+-----------------------------------------------------------------------||O | 1   |   Logical unit number    |   DPO  |Reserved| BlkVfy | BytChk | RelAdr ||O |-----+-----------------------------------------------------------------------|=O | 2   | (MSB)                                                                 | O |-----+---                                                                 ---|-O | 3   |                                                                       |aO |-----+---                        Logical block address                    ---|-O | 4   |                                                                       | O |-----+---                                                                 ---| O | 5   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------| O | 6   | (MSB)                                                                 | O |-----+---                                                                 ---| O | 7   |                                                                       | O |-----+---                        Verification length                      ---|-O | 8   |                                                                       | O |-----+---                                                                 ---| O | 9   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------| O | 10  |                           Reserved                                    | O |-----+-----------------------------------------------------------------------| O | 11  |                           Control                                     | O +=============================================================================+-     16.2.13 WRITE(10) command-  D The WRITE(10) command (see table 315) requests that the target write6 the data transferred from the initiator to the medium.  5                         Table 315 - WRITE(10) command-O +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |=O |Byte |        |        |        |        |        |        |        |        |eO |=====+=======================================================================| O | 0   |                           Operation code (2Ah)                        |UO |-----+-----------------------------------------------------------------------|=O | 1   |   Logical unit number    |   DPO  |   FUA  |   EBP  |Reserved| RelAdr | O |-----+-----------------------------------------------------------------------| O | 2   | (MSB)                                                                 |=O |-----+---                                                                 ---| O | 3   |                                                                       |-O |-----+---                        Logical block address                    ---| O | 4   |                                                                       |-O |-----+---                                                                 ---| O | 5   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------| O | 6   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------| O | 7   | (MSB)                                                                 | O |-----+---                        Transfer length                             | O | 8   |                                                                 (LSB) |-O |-----+-----------------------------------------------------------------------| O | 9   |                           Control                                     |-O +=============================================================================+     A An erase by-pass (EBP) bit of zero indicates that the device will-C default to the normal write operation.  An EBP bit of one indicateseB that the target is allowed to by-pass the erase operation prior toG writing the data. When accessing write-once media, the EBP bit shall be  considered reserved.  E See 9.2.6 for a description of the cache control bits (DPO and FUA). =G See 9.2.2 for a description of the RelAdr bit and logical block addresse field.  E The transfer length specifies the number of contiguous logical blockstG of data that shall be transferred.  A transfer length of zero indicatesP? that no data shall be transferred.  This condition shall not bePB considered an error and no data shall be written.  Any other valueA indicates the number of logical blocks that shall be transferred.t  F This command shall be terminated with a status of RESERVATION CONFLICTC if any reservation access conflict (see 9.2.12) exists, and no data  shall be written.o   16.2.14 WRITE(12) commande  D The WRITE(12) command (see table 316) requests that the target write? the data transferred from the initiator to the medium.  See theRC WRITE(10) command (16.2.13) for a description of the fields in thism command.  5                         Table 316 - WRITE(12) commandlO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |iO |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================|aO | 0   |                           Operation code (AAh)                        | O |-----+-----------------------------------------------------------------------| O | 1   |   Logical unit number    |   DPO  |   FUA  |   EBP  |Reserved| RelAdr | O |-----+-----------------------------------------------------------------------|=O | 2   | (MSB)                                                                 | O |-----+---                                                                 ---| O | 3   |                                                                       |=O |-----+---                        Logical block address                    ---| O | 4   |                                                                       |-O |-----+---                                                                 ---|oO | 5   |                                                                 (LSB) |-O |-----+-----------------------------------------------------------------------|BO | 6   | (MSB)                                                                 | O |-----+---                                                                 ---| O | 7   |                                                                       | O |-----+---                        Transfer length                          ---| O | 8   |                                                                       | O |-----+---                                                                 ---| O | 9   |                                                                 (LSB) |-O |-----+-----------------------------------------------------------------------| O | 10  |                           Reserved                                    |-O |-----+-----------------------------------------------------------------------|BO | 11  |                           Control                                     | O +=============================================================================+     $ 16.2.15 WRITE AND VERIFY(10) command  B The WRITE AND VERIFY(10) command (see table 317) requests that theF target write the data transferred from the initiator to the medium and/ then verify that the data is correctly written.   ;                    Table 317 - WRITE AND VERIFY(10) command=O +=====-========-========-========-========-========-========-========-========+rO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |nO |Byte |        |        |        |        |        |        |        |        |tO |=====+=======================================================================| O | 0   |                           Operation code (2Eh)                        |iO |-----+-----------------------------------------------------------------------|eO | 1   |   Logical unit number    |   DPO  |Reserved|   EBP  | BytChk | RelAdr |tO |-----+-----------------------------------------------------------------------|sO | 2   | (MSB)                                                                 |eO |-----+---                                                                 ---|uO | 3   |                                                                       | O |-----+---                        Logical block address                    ---|EO | 4   |                                                                       |aO |-----+---                                                                 ---|oO | 5   |                                                                 (LSB) |iO |-----+-----------------------------------------------------------------------|rO | 6   |                           Reserved                                    |iO |-----+-----------------------------------------------------------------------| O | 7   | (MSB)                                                                 | O |-----+---                        Transfer length                             | O | 8   |                                                                 (LSB) |oO |-----+-----------------------------------------------------------------------|eO | 9   |                           Control                                     |=O +=============================================================================+     ? If the MODE SELECT command is implemented, and the Verify Error G Recovery Parameters page is also implemented, then the current settings B in that page define the verification criteria. If the Verify ErrorB Recovery Parameters page is not implemented, then the verification criteria is vendor unique.  D A byte check (BytChk) bit of zero causes a medium verification to beE performed with no data comparison. A BytChk bit of one causes a byte-R> by-byte compare of the data written on the medium and the dataD transferred from the initiator.  The data shall be transferred as itF would be for a WRITE command.  If the compare is unsuccessful, for anyD reason, the target shall return CHECK CONDITION status and the sense key shall be set to MISCOMPARE.   A An erase by-pass (EBP) bit of zero indicates that the device will C default to the normal write operation.  An EBP bit of one indicates B that the target is allowed to by-pass the erase operation prior toE writing the data.  When accessing write-once media, the EBP bit shall  be considered reserved.   G See 9.2.6 for a description of the cache control bits (DPO).  See 9.2.2 D for a description of the RelAdr bit and logical block address field.  E The transfer length specifies the number of contiguous logical blocks G of data that shall be transferred.  A transfer length of zero indicates F that no logical blocks shall be transferred.  This condition shall notB be considered as an error and no data shall be written.  Any otherG value indicates the number of logical blocks that shall be transferred.   $ 16.2.16 WRITE AND VERIFY(12) command  B The WRITE AND VERIFY(12) command (see table 318) requests that theF target write the data transferred from the initiator to the medium andB then verify that the data is correctly written.  See the WRITE ANDB VERIFY(10) command (16.2.15) for a description of the bits in this command.  ;                    Table 318 - WRITE AND VERIFY(12) command-O +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |=O |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================|aO | 0   |                           Operation code (AEh)                        | O |-----+-----------------------------------------------------------------------|=O | 1   |   Logical unit number    |   DPO  |Reserved|   EBP  | BytChk | RelAdr | O |-----+-----------------------------------------------------------------------| O | 2   | (MSB)                                                                 |=O |-----+---                                                                 ---| O | 3   |                                                                       |-O |-----+---                        Logical block address                    ---| O | 4   |                                                                       |-O |-----+---                                                                 ---| O | 5   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------| O | 6   | (MSB)                                                                 | O |-----+---                                                                 ---| O | 7   |                                                                       | O |-----+---                        Transfer length                          ---| O | 8   |                                                                       |-O |-----+---                                                                 ---| O | 9   |                                                                 (LSB) |-O |-----+-----------------------------------------------------------------------| O | 10  |                           Reserved                                    | O |-----+-----------------------------------------------------------------------| O | 11  |                           Control                                     |-O +=============================================================================+     * 16.3 Parameters for optical memory devices     16.3.1 Diagnostic parameters  ? This subclause defines the descriptors and pages for diagnostic-- parameters used with optical memory devices. e  C The diagnostic page codes for optical memory devices are defined ina
 table 319.  7                       Table 319 - Diagnostic page codesoO +=============-==================================================-============+dO |  Page code  |  Description                                     | Subclause  |FO |-------------+--------------------------------------------------+------------| O |     00h     |  List of supported parameters page               |  8.3.1.1   | O |  01h - 3Fh  |  Reserved (for all device type pages)            |            | O |     40h     |  Translate address page                          |  9.3.1     | O |  41h - 7Fh  |  Reserved                                        |            |sO |  80h - FFh  |  Vendor-specific pages                           |            | O +=============================================================================+      16.3.2 Log parameterso  C This subclause defines the descriptors and pages for log parameters " used with optical memory devices.   G The log page codes for optical memory devices are defined in table 320.m  4                           Table 320 - Log page codesO +=============-==================================================-============+=O |  Page code  |  Description                                     | Subclause  | O |-------------+--------------------------------------------------+------------| O |     01h     |  Buffer over-run/under-run page                  |  8.3.2.1   |=O |     03h     |  Error counter page (read) page                  |  8.3.2.2   | O |     05h     |  Error counter page (verify) page                |  8.3.2.2   |-O |     02h     |  Error counter page (write) page                 |  8.3.2.2   |iO |     07h     |  Last n error events page                        |  8.3.2.3   |-O |     00h     |  List of supported parameters page               |  8.3.2.5   | O |     06h     |  Non-media error page                            |  8.3.2.4   | O |     04h     |  Reserved                                        |            | O |  08h - 2Fh  |  Reserved                                        |            | O |  30h - 3Eh  |  Vendor-specific                                 |            | O |     3Fh     |  Reserved                                        |            | O +=============================================================================+      16.3.3 Mode parameters  D This subclause defines the descriptors and pages for mode parameters" used with optical memory devices.   E The mode parameter list, including the mode parameter header and mode ' block descriptor, are defined in 8.3.3.   D The medium-type code field is contained in the mode parameter headerD (see 8.3.3).  Table 321 defines the medium-type code values used for optical memory devices.   =                  Table 321 - Optical memory medium-type codes O +=============-===============================================================+-O |    Code     |  Description                                                  | O |-------------+---------------------------------------------------------------|-O |     00h     |  Default (only one medium type supported)                     | O |     01h     |  Optical read-only medium                                     |-O |     02h     |  Optical write-once medium                                    | O |     03h     |  Optical reversible or erasable medium                        |=O |     04h     |  Combination of read-only and write-once medium               |2O |     05h     |  Combination of read-only and reversible or erasable medium   |1O |     06h     |  Combination of write-once and reversible or erasable medium  | O |  07h - 7Fh  |  RESERVED                                                     | O |  80h - FFh  |  Vendor-specific                                              |=O +=============================================================================+4    F The device specific parameter field is contained in the mode parameterD header (see 8.3.3).  Table 322 defines the device specific parameter' values used for optical memory devices.=  A              Table 322 - Optical memory device specific parameter(O +=====-========-========-========-========-========-========-========-========+-O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |eO |=====+========+=================+========+==========================+========|-O |     |   WP   |    Reserved     | DPOFUA |           Reserved       |  EBC   | O +=============================================================================+     A When used with the MODE SELECT command the WP bit is not defined.   D When used with the MODE SENSE command, a write protected (WP) bit ofA zero indicates that the medium is write enabled.  A WP bit of one F indicates that the medium is write protected.  For read-only media the WP bit is reserved.   B When used with the MODE SELECT command the DPOFUA bit is reserved.  D When used with the MODE SENSE command, a DPOFUA bit of one indicates: that the target supports the DPO and FUA bits (see 9.2.6).  D For the MODE SELECT command, an enable blank check (EBC) bit of zeroA advises the target to disable the blank checking operation of the-E medium during write operations or during an UPDATE BLOCK command.  An E EBC bit of one enables blank checking.  If a non-blank block is found F during a write operation, the command shall be terminated with a CHECKE CONDITION status and the sense key shall be set to BLANK CHECK.  If a-F blank block is found during an UPDATE BLOCK command, the command shallG be terminated with a CHECK CONDITION status, and the sense key shall be B set to BLANK CHECK.  For read-only media, the EBC bit is reserved.  C For the MODE SENSE command, an enable blank check (EBC) bit of zeronF indicates that blank checking of the medium during write operations isG disabled.  An EBC bit of one indicates that blank checking during writeiF and update operations is enabled.  For read-only media, the EBC bit is	 reserved.i  ? The density code field is contained in the mode parameter blockzG descriptor (see 8.3.3).  Table 323 defines the density code values used. for optical memory devices.   ;                    Table 323 - Optical memory density codeshQ +========-======================================================================+ Q |Density |                      Optical media                                   |tQ | code   |                                                                      | Q |--------+----------------------------------------------------------------------|tQ |  00h   |Default density (currently mounted density)                           |dQ |        |----------------------------------------------------------------------|nQ |        | Diameter | Type|  Sector   | Tracks | Sides | Servo| Reference |Notes|oQ |        | mm (in)  |     |   size    |        |       |      | standard  |     | Q |        |----------+-----+-----------+--------+-------+------+-----------+-----|tQ |  01h   | 86 (3,5) | R/W | 512/1 024 | 12 500 |   1   |      |  660-D    | 1   |rQ |  02h   | 89 (3,5) | R/W | 512/1 024 | 12 500 |   2   |      |  581-D    | 1   |tQ |  03h   |130 (5,25)| R/W | 512/1 024 | 18 750 |   2   |  CS  |  607-I    | 1   |eQ |  04h   |130 (5,25)| W-O | 512/1 024 | 30 000 |   2   |  SS  |  655-D    | 1,2 |IQ |  05h   |130 (5,25)| W-O | 512/1 024 | 20 000 |   2   |  SS  |  659-D    | 1,3 |eQ |  06h   |130 (5,25)| W-O | 512/1 024 | 18 750 |   2   |  CS  |  457-D    | 1   |fQ |  07h   |200 (8,0) |     |           |        |       |      |  407-D    | 1,4 |1Q |  08h   |300 (12,0)|     |   1 024   |        |   2   |      |  408-D    | 1,4 |-Q |  09h   |356 (14,0)|     |   1 024   | 56 350 |   2   |      |  456-D    | 1   |-Q |        |          |     |           |        |       |      |           |     | Q |-------------------------------------------------------------------------------| Q | Codes 80h - FFh are vendor-specific, all other codes are reserved             |=Q |-------------------------------------------------------------------------------| Q |Key:    Type    Description                 Servo  Description                 |-Q |        ----    -----------                 -----  ----------------            |yQ |        R/W     Erasable                     CS    Continuous servo            |-Q |        W-O     Write once                   SS    Sampled servo               | Q |        R/O     Read only                                                      | Q |-------------------------------------------------------------------------------| Q | NOTES                                                                         | Q |  1 The reference standard refers to an ANSI X3B11 project under               | Q | development.  The project may have several documents describing different     |-Q | aspects of the media. Please contact the Secretariat for current information  | Q | on status and availability.                                                   | Q |  2 RZ modulation.                                                             |-Q |  3 4/15 modulation.                                                           | Q |  4 This project is not presently active.                                      |-Q +===============================================================================+     F The mode page codes for optical memory devices are shown in table 324.  4                          Table 324 - Mode page codesO +=============-==================================================-============+ O |  Page code  |  Description                                     | Subclause  |-O |-------------+--------------------------------------------------+------------| O |     08h     |  Caching page                                    |  9.3.3.1   |-O |     0Ah     |  Control mode page                               |  8.5.3.1   | O |     02h     |  Disconnect-reconnect page                       |  8.3.3.2   |=O |     0Bh     |  Medium types supported page                     |  9.3.3.4   |1O |     06h     |  Optical memory page                             | 16.3.3.1   |aO |     09h     |  Peripheral device page                          |  8.3.3.3   |oO |     01h     |  Read-write error recovery page                  |  9.3.3.6   | O |     07h     |  Verify error recovery page                      |  9.3.3.8   |=O |  03h - 05h  |  Reserved                                        |            | O |  0Ch - 1Fh  |  Reserved                                        |            |-O |     00h     |  Vendor-specific (does not require page format)  |            |rO |  20h - 3Eh  |  Vendor-specific (page format required)          |            |yO |     3Fh     |  Return all pages                                |            | O |             |     (valid only for the MODE SENSE command)      |            | O +=============================================================================+      16.3.3.1 Optical memory page  F The optical memory page (see table 325) defines parameters for control of optical memory devices.  6                        Table 325 - Optical memory pageO +=====-========-========-========-========-========-========-========-========+sO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |=O |=====+========+========+=====================================================| O | 0   |   PS   |Reserved|         Page code (06h)                             |-O |-----+-----------------------------------------------------------------------| O | 1   |                           Parameter length (02h)                      | O |-----+-----------------------------------------------------------------------| O | 2   |                           Reserved                           |  RUBR  | O |-----+-----------------------------------------------------------------------| O | 3   |                           Reserved                                    | O +=============================================================================+     @ The parameters savable (PS) bit is only used with the MODE SENSEF command.  This bit is reserved with the MODE SELECT command.  A PS bitC of one indicates that the target is capable of saving the page in aV' non-volatile, vendor-specific location.   C A report updated block read (RUBR) bit of zero indicates the target F shall not report an error when a command performs a successful read ofF a block that has been updated.  A RUBR bit of one indicates the targetG shall terminate a command that performs a read of a block that has beendC updated with CHECK CONDITION status, the sense key set to RECOVEREDtC ERROR, the additional sense code set to UPDATED BLOCK READ, and the8E data shall be transferred to the initiator.  The default state of the D RUBR bit for write-once devices (as reported in the INQUIRY command)
 shall be one.   : 16.4 Definitions specific to write-once and optical memory devicest  F 16.4.1 blank:  The logical block contains no information detectable byF the target, or is written with a pattern that appears to the target asC no data present.  The logical block is considered ready for a write-
 operation.  E 16.4.2 generation:   Indicates a relative revision level of a logicalyD block that has been updated via the UPDATE BLOCK command.  A logicalD block that has never been updated has only one generation associated with it.  D 16.4.3 read-only medium:   This is medium that may not be written byG the initiator. The media contains data prepared in a manner not defined  by this International Standard.   = 16.4.4 update:   To write new data to a logical block withoutoG destroying the previous data.  After a block has been updated, a normali= read returns the most recent generation of the data.  Earlier01 generations are still available after the update.   C 16.4.5 write-once medium:   This is medium that may be written only D once by the initiator.  Logical blocks on write-once media that haveD not been written are considered blank.  Logical blocks on write-once6 media that have been written may not be written again.     17 Medium-changer devicesf      17.1 Medium-changer device model  B Medium changer devices mechanize the movement of media to and fromA primary devices (such as disk or tape drives) and other locations=F within the range of the medium changer. The medium changer command set3 is based on a physical model of this functionality.   G This command set supports varied physical implementations of the medium=> changer function. Most of these variations are hidden from theG initiator by the high level of function provided by the MOVE MEDIUM and=E EXCHANGE MEDIUM commands and by the generalized nature of the elementEB addressing scheme. However, initiators may need to be aware of the; capabilities of the particular medium changer device. ThesetC characteristics and capabilities are conveyed via MODE SENSE pages.e   17.1.1 Medium-changer elements  C The medium-changer command set uses as its address space the set ofEF physical locations and mechanisms within the scope of a medium changerG device. The term element is used throughout this clause to refer to oneaF member of the medium changer address space. Each element is a discreteF physical entity that may hold zero or one physical unit of media - oneG disk cartridge, one spool of tape, etc. Element addresses do not extendBD across multiple physical units of media. Likewise, element addressesG are independent of any logical partitioning that the primary device mayi+ support within a physical unit of media.   s  D A medium changer is viewed as a set of addressable elements, each ofF which may contain a unit of media or be used to move a unit of media. E Each medium changer element has a unique 16 bit element address. Eachr@ element is an instance of one of four classes or element types.   #    a)     MEDIUM TRANSPORT ELEMENT      b)     STORAGE ELEMENT      c)     IMPORT EXPORT ELEMENT      d)     DATA TRANSFER ELEMENT   E Units of media (cartridges, cassettes, caddies, etc.) are referred toeE only indirectly by this device model.  Units of media can be moved to G or from any of the elements of the medium changer device.  The presencetG of media at the various elements in a medium changer can be sensed.  IniF order to ensure exclusive access to a unit of media, the element whereE the unit of media is located (the element address) must be reserved. =  A Elements of the medium transport, import export and (rarely) dataiD transport types may not provide independent storage for medium.  TheB capabilities of a particular medium changer in this respect can beC sensed via the device capabilities page of the mode sense data. The D following hypothetical medium changer implementation illustrates oneA case of an element not providing independent storage for medium. -@ Consider a medium changer which has a carousel style storage forD medium. The import export function could be provided by a port whichA allows operator access to one of the storage elements.  In such a F device, the MOVE ELEMENT command from storage element to import export@ element would rotate the carousel to align the addressed storageE element to the import export position. In this case the import export|E element does not provide independent storage but rather access to one2 of the storage elements.  " 17.1.1.1 Medium transport elements  E Medium transport elements address the functions of the medium changerhB device that perform the movement of units of media. Where a mediumD transport element can serve (even temporarily) as a storage locationC for medium, the location of each unit of media must have a separate  element address.  F In larger medium changer devices, the medium movement functions may beD performed by multiple independent robotics subsystems. Each of theseD may have a number of medium transport element addresses. The elementG addresses within each subsystem shall be contiguous. Any of the element-F addresses within a subsystem may be used interchangeably in the mediumB transport element address field of MOVE MEDIUM and EXCHANGE MEDIUMC commands. An initiator may determine the capabilities of the medium-@ movement facilities of a medium changer device via the transport' geometry MODE SENSE page, see 17.3.3.3.-  @ Element address zero is reserved for use in the medium transportD element address field of MOVE MEDIUM and EXCHANGE MEDIUM commands toE direct the medium changer to use a default or medium changer selected  medium transport element.   G In some implementations, medium transport elements may be source and/or C destination addresses in MOVE MEDIUM and EXCHANGE MEDIUM commands. -D They may or may not provide independent storage of a unit of media. 8 See the device capabilities MODE SENSE page, see 17.3.3.   17.1.1.2 Storage elementst  B Storage elements are locations of units of media while not in someG other element type.  Medium in storage elements is available for accessf by medium transport elements.   C Storage elements may be source and/or destination addresses in MOVE $ MEDIUM and EXCHANGE MEDIUM commands.   17.1.1.3 Import export elements   F Import export elements are locations of units of media which are beingE inserted into or withdrawn from the medium changer device.  Medium in F these elements is accessible by both medium transport elements, by the< operator, or by another independent medium changer device.    D Import export elements may be source and/or destination addresses inE MOVE MEDIUM and EXCHANGE MEDIUM commands. They may or may not provide3C independent storage of a unit of media, see the device capabilities= MODE SENSE page, see 17.3.3.  A Particular import export elements may be capable of either import|> actions, export actions, both or neither (if an element is not	 present).-   17.1.1.4 Data transfer element    E Data transfer elements are locations of the primary devices which are D capable of reading or writing the medium. Data transfer elements mayD also be viewed as medium changer element addresses of units of mediaE loaded in or available for loading in or removal from primary devices B such as disk or tape drives. Note that the medium changer functionE specified in this clause does not control the primary device. That ise! the responsibility of the system.|  D Data transfer elements may be source and/or destination addresses inE MOVE MEDIUM and EXCHANGE MEDIUM commands. They may or may not provide C independent storage of a unit of media, see the device capabilities  MODE SENSE page, see 17.3.3.  0 17.1.2 SCSI addressing of medium changer devices  C Medium changer devices respond to a SCSI ID / LUN address different-B from those used by the data transfer element devices.  If the dataG transfer elements served by the medium changer device are SCSI devices, G they may be addressed though the same SCSI ID as the changer device but D with a different logical unit number or through a different SCSI ID.A There is no requirement that communication with the data transfer=G elements be done with the same SCSI bus as the medium changer device orp? by an SCSI interface at all.  This command set does not support C addressing both the changer and the data transfer elements with thecC same SCSI ID / LUN because the device at a particular SCSI ID / LUN=3 address must have a single peripheral device type.    @ The READ ELEMENT STATUS response page for data transfer elementsG provides the SCSI ID / LUN address of the primary devices serviced by a== medium changer device if known to the medium changer device. =  ; 17.1.3 Data access operations using a medium changer device   @ The medium changer device moves units of media among the severalF elements accessible to it.  It is able to report the full/empty status? of any of these elements.  Data transfer elements represent the-C interface between the medium changer device and some primary device < such as a removable media optical disk drive or tape drive.   A In order to access data on a unit of media currently located in a-G medium changer storage element, a system will have to issue commands tovG both the medium changer device and to the primary device.  The commands=E to the medium changer may include MOVE MEDIUM or EXCHANGE MEDIUM plusvE READ ELEMENT STATUS commands.  The commands to the primary device mayeE include TEST UNIT READY, INQUIRY, START STOP and LOAD UNLOAD commandsh( in addition to READ and WRITE commands.   . 17.1.4 Element status maintenance requirements  B If the medium changer device chooses to implement the READ ELEMENTF STATUS command, the medium changer device must be capable of reportingE the various data (i.e. full, error, etc.) required by each page type.h@ The medium changer may maintain this information at all times orA regenerate it in response to the READ ELEMENT STATUS command. TheOF INITIALIZE ELEMENT STATUS command can be used to force regeneration of this information.    17.1.5 Volume tags  ? The read element status descriptor format for all element types F includes two sets of fields that contain volume tag information. TheseC optional fields are used to report media identification information B that the medium changer has acquired either by reading an externalF label (e.g. bar code labels), by a SEND VOLUME TAG command or by otherG means which may be vendor unique. The same volume tag information shall E be available to all initiators whether assigned by that initiator, by 4 some other initiator or by the media changer itself.  D Volume tag information provides a means to confirm the identity of aD unit of media that resides in a medium changer element. This commandD set does not define any direct addressing of units of media based onD these fields. However, commands are defined that provide translationF between volume tag information and the element address where that unit of media currently resides.o  = The medium changer command set definition does not impose therC requirement that volume tag information be unique over the units ofh. media within the scope of the changer device.   E The following commands support the optional volume tag functionality:sK    a)     SEND VOLUME TAG - either as a translation request or to associateaF           a volume tag with the unit of media currently residing at an           element address.E    b)     REQUEST VOLUME ELEMENT ADDRESS - return the element addresscJ           currently associated with the volume tag information transferred0           with the last send volume tag command.I    c)     READ ELEMENT STATUS - optionally reports volume tag information             for all element types.G    d)     MOVE MEDIUM and EXCHANGE MEDIUM commands - if volume tags aremI           implemented, these commands must retain the association betweentJ           volume tag information and units of media as they are moved from           element to element.e   17.1.5.1 Volume tag format E  B Volume tag information consists of a volume identifier field of 32@ bytes plus a volume sequence number field of 2 bytes. The volume> identifier shall consist of a left justified sequence of ASCIIG characters. Unused positions shall be blank (20h) filled.  In order for F the SEND VOLUME TAG translate with template to work the characters '*'F and'?' (2Ah and 3Fh) must not appear in volume identification data andG there must be no blanks (20h) within the significant part of the volumesA identifier. If volume tag information for a particular element iso7 undefined, the volume identifier field shall be zero.     C The volume sequence number is a 2 byte integer field. If the volumehE sequence number is not used this field shall be zero.  The volume tagaA contents are independent of the volume identification informationn recorded on the media. .  J    NOTE 199 For compatibility with the volume identifier defined by volumeM    and file structure standards, it is recommended that the characters in thedM    significant non-blank portion of the volume identifier field be restrictednI    to the set: '0'..'9', 'A'..'Z', and '_' (30h .. 39h, 41h .. 5Ah, 5Fh).OL    Specific systems may have differing requirements that may take precedence    over this recommendation.  E Table 326 defines the fields within the 36 byte primary and alternateeF volume tag information fields found in READ ELEMENT STATUS descriptors7 and in the data format for the SEND VOLUME TAG command.e  ;                   Table 326 - Volume tag information formatcO +=====-========-========-========-========-========-========-========-========+tO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |rO |Byte |        |        |        |        |        |        |        |        |nO |=====+=======================================================================| O | 0   |                                                                       |iO |- - -+---                   Volume identification field                   ---|lO | 31  |                                                                       |fO |-----+-----------------------------------------------------------------------|eO | 32  |                                                                       |oO |- - -+---                            Reserved                             ---|mO | 33  |                                                                       |aO |-----+-----------------------------------------------------------------------|hO | 34  | (MSB)                                                                 |tO |-----+---                     Volume sequence number                      ---|tO | 35  |                                                                 (LSB) |rO +=============================================================================+e    5 17.1.5.2 Primary and alternate volume tag informationi  A Element status descriptors as reported by the READ ELEMENT STATUSn@ command define a primary volume tag and an alternate volume tag.E Alternate volume tag information provides a means for a system to useeC different volume identification information for each side of doubletA sided media. In such a system, the primary volume tag informationlA refers to the logical medium accessible via a MOVE MEDIUM command G without the invert bit set. The alternate volume tag information refersED to the other side of the media, i.e. the side that would be accessed2 via a MOVE MEDIUM command with the invert bit set.    ( 17.2 Commands for medium changer devices  G The commands for medium changer devices shall be as shown in table 327.a  >                Table 327 - Commands for medium changer devicesH +=====================================-============-======-============+H |  Command name                       | Operation  | Type |  Subclause |H |                                     |   code     |      |            |H |-------------------------------------+------------+------+------------|H | CHANGE DEFINITION                   |    40h     |   O  |   8.2.1    |H | EXCHANGE MEDIUM                     |    A6h     |   O  |  17.2.1    |H | INITIALIZE ELEMENT STATUS           |    07h     |   O  |  17.2.2    |H | INQUIRY                             |    12h     |   M  |   8.2.5    |H | LOG SELECT                          |    4Ch     |   O  |   8.2.6    |H | LOG SENSE                           |    4Dh     |   O  |   8.2.7    |H | MODE SELECT(6)                      |    15h     |   O  |   8.2.8    |H | MODE SELECT(10)                     |    55h     |   O  |   8.2.9    |H | MODE SENSE(6)                       |    1Ah     |   O  |   8.2.10   |H | MODE SENSE(10)                      |    5Ah     |   O  |   8.2.11   |H | MOVE MEDIUM                         |    A5h     |   M  |  17.2.3    |H | POSITION TO ELEMENT                 |    2Bh     |   O  |  17.2.4    |H | PREVENT ALLOW MEDIUM REMOVAL        |    1Eh     |   O  |   9.2.4    |H | READ BUFFER                         |    3Ch     |   O  |   8.2.12   |H | READ ELEMENT STATUS                 |    B8h     |   O  |  17.2.5    |H | RECEIVE DIAGNOSTIC RESULTS          |    1Ch     |   O  |   8.2.13   |H | RELEASE                             |    17h     |   O  |  17.2.6    |H | REQUEST VOLUME ELEMENT ADDRESS      |    B5h     |   O  |  17.2.7    |H | REQUEST SENSE                       |    03h     |   M  |   8.2.14   |H | RESERVE                             |    16h     |   O  |  17.2.8    |H | REZERO UNIT                         |    01h     |   O  |   9.2.13   |H | SEND DIAGNOSTIC                     |    1Dh     |   M  |   8.2.15   |H | SEND VOLUME TAG                     |    B6h     |   O  |  17.2.9    |H | TEST UNIT READY                     |    00h     |   M  |   8.2.16   |H | WRITE BUFFER                        |    3Bh     |   O  |   8.2.17   |H |----------------------------------------------------------------------|H |Key:  M = command implementation is mandatory.                        |H |      O = command implementation is optional.                         |H +======================================================================+    B Operation codes 0Ch, and C0h through FFh are vendor-specific.  All# other operation codes are reserved.C     17.2.1 EXCHANGE MEDIUM command  ? The EXCHANGE MEDIUM command (see table 328) provides a means toaG exchange the medium in the source element, with the medium located at a. destination element.    8                      Table 328 - EXCHANGE MEDIUM commandO +=====-========-========-========-========-========-========-========-========+IO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |EO |Byte |        |        |        |        |        |        |        |        |dO |=====+=======================================================================| O | 0   |                           Operation code (A6h)                        |dO |-----+-----------------------------------------------------------------------|nO | 1   | Logical unit number      |                  Reserved                  | O |-----+-----------------------------------------------------------------------|aO | 2   | (MSB)                                                                 |eO |-----+---                        Transport element address                ---|iO | 3   |                                                                 (LSB) |oO |-----+-----------------------------------------------------------------------|dO | 4   | (MSB)                                                                 | O |-----+---                        Source address                           ---|IO | 5   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|eO | 6   | (MSB)                                                                 | O |-----+---                        First destination address                ---|bO | 7   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|EO | 8   | (MSB)                                                                 | O |-----+---                        Second destination address               ---| O | 9   |                                                                 (LSB) |pO |-----+-----------------------------------------------------------------------|uO | 10  |                           Reserved                  |  Inv2  |  Inv1  |)O |-----+-----------------------------------------------------------------------| O | 11  |                           Control                                     |eO +=============================================================================+     E    NOTE 200 Support of this command requires that the device have theoH    capability of handling two units of media at the same time or that it    emulate this capability.   B The medium in the source element is moved to the first destinationE element and the medium that previously occupied the first destinatione> element is moved to the second destination element. The secondD destination element may or may not be the same element as the sourceF element.  In the case of a simple exchange, the source element and the) second destination element are the same.    B If this command is received and the source element is empty or theE first destination element is empty, or the second destination elementt= (if different from the source element) is full, or the secondiE destination element (if the same as the source element) is empty, theTC target shall return CHECK CONDITION status and set the sense key tod ILLEGAL REQUEST. g  D The transport element address specifies the medium transport elementC that is to be used in executing this command. The default transportoF element address of zero may be used if this functionality is supported> by the medium changer device. If the transport element addressB specified has not been assigned or has been assigned to an elementD other than a medium transport element, the target shall return CHECK? CONDITION status and the set the sense key to ILLEGAL REQUEST. u  A The source address, the first destination address, and the second E destination address may represent a storage element, an import exportsD element, a data transfer element, or a medium transport element.  IfD the address specified has not been assigned to a specific element ofF the medium changer, the target shall return CHECK CONDITION status and& set the sense key to ILLEGAL REQUEST.   B The device capabilities page (see 17.3.3.) provides a matrix whichG defines the supported source element type and first destination elementlF type combinations for EXCHANGE MEDIUM commands when the source element4 type is the same as second destination element type.  G An Inv1 bit of one specifies that the medium shall be inverted prior toT: depositing the medium into the first destination element.   G An Inv2 bit of one specifies that the medium shall be inverted prior tob; depositing the medium into the second destination element. l  C If the medium changer does not support medium rotation for handling D double sided media, the Inv1 and Inv2 bits should be set to zero. IfB either of these bits is non-zero, a target which is not capable ofE medium rotation shall return CHECK CONDITION status and set the senset key to ILLEGAL REQUEST.   ( 17.2.2 INITIALIZE ELEMENT STATUS command  D The INITIALIZE ELEMENT STATUS command (see table 329) will cause theD medium changer to check all elements for medium and any other statusE relevant to that element. The intent of this command is to enable the2F initiator to get a quick response from a following READ ELEMENT STATUSF command. It may be useful to issue this command after a power failure,G or if medium has been changed by an operator, or if configurations have 
 been changed.|  =                 Table 329 - INITIALIZE ELEMENT STATUS command=O +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================|-O | 0   |                           Operation code (07h)                        | O |-----+-----------------------------------------------------------------------| O | 1   | Logical unit number      |                Reserved                    | O |-----+-----------------------------------------------------------------------|-O | 2   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------| O | 3   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|=O | 4   |                           Reserved                                    |aO |-----+-----------------------------------------------------------------------|dO | 5   |                           Control                                     |eO +=============================================================================+s     17.2.3 MOVE MEDIUM command  G The MOVE MEDIUM command (see table 330) requests that the target move ae> unit of media from a source element to a destination element.   6                        Table 330 - MOVE MEDIUM commandO +=====-========-========-========-========-========-========-========-========+dO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |rO |Byte |        |        |        |        |        |        |        |        |uO |=====+=======================================================================|CO | 0   |                           Operation code (A5h)                        |=O |-----+-----------------------------------------------------------------------|TO | 1   | Logical unit number      |             Reserved                       | O |-----+-----------------------------------------------------------------------|-O | 2   | (MSB)                                                                 |XO |-----+---                        Transport element address                ---|EO | 3   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------| O | 4   | (MSB)                                                                 | O |-----+---                        Source address                           ---|1O | 5   |                                                                 (LSB) ||O |-----+-----------------------------------------------------------------------| O | 6   | (MSB)                                                                 |1O |-----+---                        Destination address                      ---| O | 7   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------| O | 8   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------| O | 9   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------| O | 10  |                           Reserved                           | Invert | O |-----+-----------------------------------------------------------------------|.O | 11  |                           Control                                     | O +=============================================================================+V    B The source address specifies the location that the medium is takenA from, and the destination address specifies the location that the  medium is moved to.   B If this command is received and the source element is empty or theG destination element (if different from the source element) is full, thedC target shall return CHECK CONDITION status and set the sense key tom ILLEGAL REQUEST.    D The transport element address specifies the medium transport element@ that is to be used in executing this command. The default mediumF transport element address of zero may be used if this functionality isE supported by the medium changer device.  If the address specified has A not been assigned or has been assigned to an element other than anA medium transport element, the target shall return CHECK CONDITIONm5 status and the set the sense key to ILLEGAL REQUEST. I  F The source address and the destination address may represent a storageG element, an import export element, a data transfer element, or a medium F transport element. If the address specified has not been assigned to aE specific element of the medium changer, the target shall return CHECK=; CONDITION status and set the sense key to ILLEGAL REQUEST.    B The device capabilities MODE SENSE page provides a matrix with theD supported source element or destination element combinations for the  MOVE MEDIUM command. See 17.3.3.  C An invert bit of one specifies that the medium shall be inverted or-G rotated prior to depositing the medium into the destination element. If G the medium changer does not support medium rotation for handling doubleeG sided media, the invert bit should be set to zero.  If this bit is non- B zero, a target that is not capable of medium rotation shall returnA CHECK CONDITION status and set the sense key to ILLEGAL REQUEST. -  " 17.2.4 POSITION TO ELEMENT command  A The POSITION TO ELEMENT command (see table 331) will position the ? transport element specified in front of the destination element  specified.    :                    Table 331 - POSITION TO ELEMENT commandO +=====-========-========-========-========-========-========-========-========+-O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |tO |=====+=======================================================================| O | 0   |                           Operation code (2Bh)                        |-O |-----+-----------------------------------------------------------------------| O | 1   | Logical unit number      |                Reserved                    |aO |-----+-----------------------------------------------------------------------| O | 2   | (MSB)                                                                 |-O |-----+---                        Transport element address                ---| O | 3   |                                                                 (LSB) |-O |-----+-----------------------------------------------------------------------| O | 4   | (MSB)                                                                 |=O |-----+---                        Destination element address              ---|sO | 5   |                                                                 (LSB) |aO |-----+-----------------------------------------------------------------------|eO | 6   |                           Reserved                                    |pO |-----+-----------------------------------------------------------------------|hO | 7   |                           Reserved                                    |lO |-----+-----------------------------------------------------------------------|iO | 8   |                           Reserved                           | Invert |eO |-----+-----------------------------------------------------------------------| O | 9   |                           Control                                     |tO +=============================================================================+r    I    NOTE 201 In this context, in front of is defined to mean positioned sorI    that no further motion of the medium transport element is necessary tobG    execute an appropriate MOVE MEDIUM command between the two elements.   A An invert bit value of one requests that the transport element be B inverted or rotated before positioning in front of the destinationC element. A value of zero requests that the orientation be unchanged 7 before positioning in front of the destination element.O  " 17.2.5 READ ELEMENT STATUS command  A The READ ELEMENT STATUS command (see table 332) requests that thesC target report the status of its internal elements to the initiator.n  :                    Table 332 - READ ELEMENT STATUS commandO +=====-========-========-========-========-========-========-========-========+eO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |tO |Byte |        |        |        |        |        |        |        |        |eO |=====+=======================================================================| O | 0   |                           Operation code (B8h)                        |hO |-----+-----------------------------------------------------------------------| O | 1   | Logical unit number      | VolTag |        Element type code          |mO |-----+-----------------------------------------------------------------------|hO | 2   | (MSB)                                                                 |nO |-----+---                        Starting element address                 ---|nO | 3   |                                                                 (LSB) |hO |-----+-----------------------------------------------------------------------|hO | 4   | (MSB)                                                                 | O |-----+---                        Number of elements                       ---| O | 5   |                                                                 (LSB) |nO |-----+-----------------------------------------------------------------------|aO | 6   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|iO | 7   | (MSB)                                                                 | O |-----+---                                                                 ---|=O | 8   |                           Allocation length                           | O |-----+---                                                                 ---| O | 9   |                                                                 (LSB) |=O |-----+-----------------------------------------------------------------------| O |10   |                           Reserved                                    |-O |-----+-----------------------------------------------------------------------|nO |11   |                           Control                                     |-O +=============================================================================+     G A volume tag (VolTag) bit of one indicates that the target shall report-D volume tag information if this feature is supported. A value of zeroC indicates that volume tag information shall not be reported. If the B volume tag feature is not supported this field shall be treated as	 reserved.-  D The element type code field specifies the particular element type(s)G selected for reporting by this command.  A value of zero specifies that-G status for all element types shall be reported.  The element type codes  are defined in table 333.   5                         Table 333 - Element type code=H      +=============-===================================================+H      |    Code     |  Description                                      |H      |-------------+---------------------------------------------------|H      |      0h     |  All element types reported, (valid in CDB only)  |H      |      1h     |  Medium transport element                         |H      |      2h     |  Storage element                                  |H      |      3h     |  Import export element                            |H      |      4h     |  Data transfer element                            |H      |   5h - Fh   |  Reserved                                         |H      +=================================================================+    E The starting element address specifies the minimum element address to @ report. Only elements with an element type code permitted by theG element type code specification, and an element address greater than or @ equal to the starting element address shall be reported. ElementD descriptor blocks are not generated for undefined element addresses.  > The number of elements specifies the maximum number of elementC descriptors to be created by the target for this command. The value-C specified by this field is not the range of element addresses to be E considered for reporting but rather the number of defined elements toeF report. If the allocation length is not sufficient to transfer all theD element descriptors, the target shall transfer all those descriptorsF that can be completely transferred and this shall not be considered an error.   17.2.5.1 Element status data    B The data returned by the READ ELEMENT STATUS command is defined inF table 334 and 17.2.5.3 through 17.2.5.6.  Element status data consists@ of an eight-byte header, (see table 334) followed by one or more element status pages.-  6                        Table 334 - Element status dataO +=====-========-========-========-========-========-========-========-========+-O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |-O |=====+=======================================================================| O | 0   | (MSB)                                                                 |-O |-----+---                  First element address reported                 ---| O | 1   |                                                                 (LSB) |=O |-----+-----------------------------------------------------------------------|rO | 2   | (MSB)                                                                 |tO |-----+---                    Number of elements available                 ---|mO | 3   |                                                                 (LSB) |iO |-----+-----------------------------------------------------------------------|OO | 4   |                              Reserved                                 |dO |-----+-----------------------------------------------------------------------|sO | 5   | (MSB)                                                                 |iO |-----+---                                                                 ---|fO | 6   |                     Byte count of report available                    |iO |-----+---                        (all pages, n - 7 )                      ---|tO | 7   |                                                                 (LSB) |dO |=====+=======================================================================|eO | 8   |                                                                       |sO |- - -+---                     Element status page(s)                      ---|=O | n   |                                                                       |bO +=============================================================================+e    F The first element address reported field indicates the element addressF of the element with the smallest element address found to meet the CDB request.  G The number of elements available field indicates the number of elementsaD meeting the request in the command descriptor block.  The status for> these elements is returned if sufficient allocation length was
 specified.  F The byte count of report available field indicates the number of bytesB of element status page data available for all elements meeting theA request in the command descriptor block.  This value shall not be13 adjusted to match the allocation length available. f  C    NOTE 202 - The READ ELEMENT STATUS command can be issued with anbH    allocation length of eight bytes in order to determine the allocationK    length required to transfer all the element status data specified by the     command.   = Figure 28 provides an illustration of the element status data 
 structure.                                                                C           Figure 28 - Illustration of element status data structure      17.2.5.2 Element status page  E The element status page is defined in table 335.  Each element status-B page includes an eight-byte header followed by one or more elementB descriptor blocks.  The header includes the element type code, theB length of each descriptor block and the number of bytes of elementE descriptor information that follow the header for this element type.    7                        Table 335 - Element status page lO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |-O |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================| O | 0   |                           Element type code                           | O |-----+-----------------------------------------------------------------------|-O | 1   | PVolTag| AVolTag|                      Reserved                       | O |-----+-----------------------------------------------------------------------|-O | 2   | (MSB)                                                                 | O |-----+---                    Element descriptor length                    ---|-O | 3   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|-O | 4   |                              Reserved                                 | O |-----+-----------------------------------------------------------------------|=O | 5   | (MSB)                                                                 |iO |-----+---                                                                 ---|rO | 6   |                Byte count of descriptor data available                | O |-----+---                      (this page, n - 7)                         ---|eO | 7   |                                                                 (LSB) |nO |=====+=======================================================================|gO | 8   |                                                                       |hO |- - -+---                     Element descriptor(s)                       ---|hO | n   |                                                                       |3O +=============================================================================+=    G The element type code field indicates the element type reported by this  page.|  D A primary volume tag (PVolTag) bit of one indicates that the primary@ volume tag information field is present in each of the followingE element descriptor blocks. A value of zero indicates that these bytes 5 are omitted from the element descriptors that follow.   ? An alternate volume tag (AVolTag) bit of one indicates that the-@ alternate volume tag information field is present in each of theC following element descriptor blocks. A value of zero indicates that-A these bytes are omitted from the element descriptors that follow.   D The element descriptor length field indicates the number of bytes in each element descriptor.    F The byte count of descriptor data available field indicates the numberB of bytes of element descriptor data available for elements of thisD element type meeting the request in the CDB. This value shall not be2 adjusted to match the allocation length available.  F Each element descriptor includes the element address and status flags;G it may also contain sense code information as well as other information > depending on the element type (see 17.2.5.3 through 17.2.5.6).  , 17.2.5.3 Medium transport element descriptor  : Table 336 defines the medium transport element descriptor.  >                Table 336 - Medium transport element descriptorP +======-========-========-========-========-========-========-========-========+P |   Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P |Byte  |        |        |        |        |        |        |        |        |P |======+=======================================================================|P |  0   | (MSB)                                                                 |P |------+---                      Element address                            ---|P |  1   |                                                                 (LSB) |P |------+-----------------------------------------------------------------------|P |  2   |            Reserved                        | Except |Reserved|  Full  |P |------+-----------------------------------------------------------------------|P |  3   |                            Reserved                                   |P |------+-----------------------------------------------------------------------|P |  4   |                      Additional sense code                            |P |------+-----------------------------------------------------------------------|P |  5   |                  Additional sense code qualifier                      |P |------+-----------------------------------------------------------------------|P |  6   |                                                                       |P |- - --+---                         Reserved                                ---|P |  8   |                                                                       |P |------+-----------------------------------------------------------------------|P |  9   | SValid | Invert |                      Reserved                       |P |------+-----------------------------------------------------------------------|P | 10   | (MSB)                                                                 |P |------+---                Source storage element address                   ---|P | 11   |                                                                (LSB)  |P |------+-----------------------------------------------------------------------|P | 12   |                                                                       |P |- - --+---                Primary volume tag information                   ---|P | 47   |                   (Field omitted if PVolTag = 0)                      |P |------+-----------------------------------------------------------------------|P | 48   |                                                                       |P |- - --+---               Alternate volume tag information                  ---|P | 83   |                   (Field omitted if AVolTag = 0)                      |P |------+-----------------------------------------------------------------------|P | 84   |                                                                       |P |- - --+---                          Reserved                               ---|P | 87   |    (Field moved up if volume tag information field(s) are omitted.)   |P |------+-----------------------------------------------------------------------|P | 88   |                                                                       |P |- - --+---                        Vendor-specific                          ---|P | z-1  |    (Field moved up if volume tag information field(s) are omitted.)   |P +==============================================================================+    A The element address field gives the address of the medium changer B element whose status is reported by this element descriptor block.  ? An exception (Except) bit of one indicates the element is in an=G abnormal state.  An exception bit of zero indicates the element is in a D normal state.  If this bit is one, information on the abnormal stateG may be available in the additional sense code and additional sense code  qualifier bytes.  E A full bit value of one indicates that the element contains a unit of E media.  A value of zero indicates that the element does not contain a- unit of media.  F The additional sense code field may provide specific information on anD abnormal element state.  The values in this field are as defined forC the additional sense code of the REQUEST SENSE data (see 8.2.14.3).   C The additional sense code qualifier field may provide more detailed-G information on an abnormal element state.  The values in this field are G as defined for the additional sense code qualifier of the REQUEST SENSE- data (see 8.2.14.4).  B A source valid (SValid) bit value of one indicates that the sourceG storage element address field and the invert bit information are valid. A A value of zero indicates that the values in these fields are not  valid.    G An invert bit value of one indicates that the unit of media now in this G element was inverted by MOVE MEDIUM or EXCHANGE MEDIUM operations since E it was last in the source storage element.  A value of zero indicates 0 that no inversion occurred during the operation.  D The source storage element address field provides the address of theG last storage element this unit of media was moved.  This field is validE only if the SValid bit is one.  C The primary and alternate volume tag information fields provide for E identifying the unit of media residing in this element (see 17.1.5.).=A Either or both of these fields may be omitted for all the element F descriptor blocks that comprise an element status page as indicated by? the PVolTag and AVolTag bits in the element status page header.b  # 17.2.5.4 Storage element descriptors  1 Table 337 defines the storage element descriptor.c  :                     Table 337 - Storage element descriptorP +======-========-========-========-========-========-========-========-========+P |   Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P | Byte |        |        |        |        |        |        |        |        |P |======+=======================================================================|P |  0   | (MSB)                                                                 |P |------+---                      Element address                            ---|P |  1   |                                                                 (LSB) |P |------+-----------------------------------------------------------------------|P |  2   |            Reserved               | Access | Except |Reserved|  Full  |P |------+-----------------------------------------------------------------------|P |  3   |                            Reserved                                   |P |------+-----------------------------------------------------------------------|P |  4   |                       Additional sense code                           |P |------+-----------------------------------------------------------------------|P |  5   |                   Additional sense code qualifier                     |P |------+-----------------------------------------------------------------------|P |  6   |                                                                       |P |- - --+---                         Reserved                                ---|P |  8   |                                                                       |P |------+-----------------------------------------------------------------------|P |  9   | SValid | Invert |                      Reserved                       |P |------+-----------------------------------------------------------------------|P | 10   | (MSB)                                                                 |P |------+---                    Source element address                       ---|P | 11   |                                                                (LSB)  |P |------+-----------------------------------------------------------------------|P | 12   |                                                                       |P |- - --+---                 Primary volume tag information                  ---|P | 47   |                    (Field omitted if PVolTag = 0)                     |P |------+-----------------------------------------------------------------------|P | 48   |                                                                       |P |- - --+---                Alternate volume tag information                 ---|P | 83   |                    (Field omitted if PVolTag = 0)                     |P |------+-----------------------------------------------------------------------|P | 84   |                                                                       |P |- - --+---                         Reserved                                ---|P | 87   |    (Field moved up if volume tag information field(s) are omitted.)   |P |------+-----------------------------------------------------------------------|P | 88   |                                                                       |P |- - --+---                      Vendor unique                              ---|P | z-1  |    (Field moved up if volume tag information field(s) are omitted.)   |P +==============================================================================+    D An access bit value of one indicates that access to the element by aE medium transport element is allowed.  An access bit of zero indicatessE that access to the element by the medium transport element is denied.f  D The source storage element address field provides the address of theD last storage element this unit of media was moved from. This elementG address value may or may not be the same as this element. This field is $ valid only if the SValid bit is one.  7 For fields not defined in this subclause, see 17.2.5.3.b  ) 17.2.5.5 Import export element descriptora  7 Table 338 defines the import export element descriptor.i  =                  Table 338 - Import export element descriptoriP +======-========-========-========-========-========-========-========-========+P |   Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P |Byte  |        |        |        |        |        |        |        |        |P |======+=======================================================================|P |  0   | (MSB)                                                                 |P |------+---                        Element address                          ---|P |  1   |                                                                 (LSB) |P |------+-----------------------------------------------------------------------|P |  2   |     Reserved    | InEnab | ExEnab | Access | Except | ImpExp |  Full  |P |------+-----------------------------------------------------------------------|P |  3   |                             Reserved                                  |P |------+-----------------------------------------------------------------------|P |  4   |                        Additional sense code                          |P |------+-----------------------------------------------------------------------|P |  5   |                    Additional sense code qualifier                    |P |------+-----------------------------------------------------------------------|P |  6   |                                                                       |P |------+---                          Reserved                               ---|P |  8   |                                                                       |P |------+-----------------------------------------------------------------------|P |  9   | SValid | Invert |                      Reserved                       |P |------+-----------------------------------------------------------------------|P | 10   | (MSB)                                                                 |P |------+---                  Source storage element address                 ---|P | 11   |                                                                (LSB)  |P |------+-----------------------------------------------------------------------|P | 12   |                                                                       |P |- - --+---                  Primary volume tag information                 ---|P | 47   |                     (Field omitted if PVolTag = 0)                    |P |------+-----------------------------------------------------------------------|P | 48   |                                                                       |P |- - --+---                 Alternate volume tag information                ---|P | 83   |                     (Field omitted if PVolTag = 0)                    |P |------+-----------------------------------------------------------------------|P | 84   |                                                                       |P |- - --+---                          Reserved                               ---|P | 87   |    (Field moved up if volume tag information field(s) are omitted.)   |P |------+-----------------------------------------------------------------------|P | 88   |                                                                       |P |- - --+---                         Vendor unique                           ---|P | z-1  |    (Field moved up if volume tag information field(s) are omitted.)   |P +==============================================================================+    E An import enable (InEnab) bit of one indicates that the import export-G element supports movement of media into the scope of the medium changer C device.  An InEnab bit of zero indicates that this element does not  support import actions.   E An export enable (ExEnab) bit of one indicates that the import exportdA element supports movement of media out of the scope of the medium=F changer device. An ExEnab bit of zero indicates that this element does not support export actions.   G An access bit of one indicates that access to the import export element(@ by a medium transport element is allowed.  An access bit of zeroA indicates access to the import export element by medium transports elements is denied.   J    NOTE 203 An example of when access would be denied is when the operator5    has exclusive access to the import export element.   G An import export (ImpExp) bit of one indicates the unit of media in theiE import export element was placed there by an operator.  An ImpExp bittD of zero indicates the unit of media in the import export element was- placed there by the medium transport element.l  4 For fields not defined in this clause, see 17.2.5.3.  ) 17.2.5.6 Data transfer element descriptor.  7 Table 339 defines the data transfer element descriptor.d  =                  Table 339 - Data transfer element descriptorvP +======-========-========-========-========-========-========-========-========+P |   Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P |Byte  |        |        |        |        |        |        |        |        |P |======+=======================================================================|P |  0   | (MSB)                                                                 |P |------+---                      Element address                            ---|P |  1   |                                                                 (LSB) |P |------+-----------------------------------------------------------------------|P |  2   |            Reserved               | Access | Except |Reserved|  Full  |P |------+-----------------------------------------------------------------------|P |  3   |                            Reserved                                   |P |------+-----------------------------------------------------------------------|P |  4   |                       Additional sense code                           |P |------+-----------------------------------------------------------------------|P |  5   |                   Additional sense code qualifier                     |P |------+-----------------------------------------------------------------------|P |  6   |Not bus|Reserved|ID valid|LU valid|Reserved|    Logical unit number    |P |------+-----------------------------------------------------------------------|P |  7   |                         SCSI bus address                              |P |------+-----------------------------------------------------------------------|P |  8   |                             Reserved                                  |P |------+-----------------------------------------------------------------------|P |  9   | SValid | Invert |                      Reserved                       |P |------+-----------------------------------------------------------------------|P | 10   | (MSB)                                                                 |P |------+---              Source storage element address                     ---|P | 11   |                                                                (LSB)  |P |------+-----------------------------------------------------------------------|P | 12   |                                                                       |P |- - --+---                 Primary volume tag information                  ---|P | 47   |                    (Field omitted if PVolTag = 0)                     |P |------+-----------------------------------------------------------------------|P | 48   |                                                                       |P |- - --+---                Alternate volume tag information                 ---|P | 83   |                    (Field omitted if PVolTag = 0)                     |P |------+-----------------------------------------------------------------------|P | 84   |                                                                       |P |- - --+---                         Reserved                                ---|P | 87   |    (Field moved up if volume tag information field(s) are omitted.)   |P |------+-----------------------------------------------------------------------|P | 88   |                                                                       |P |- - --+---                        Vendor unique                            ---|P | z-1  |    (Field moved up if volume tag information field(s) are omitted.)   |P +==============================================================================+    @ An access bit value of one indicates access to the data transferD element by the medium transport element is allowed.  A value of zeroC indicates access to the data transfer element by a medium transport  element is denied.  L    NOTE 204 Access to the data transfer element by medium transport elementsJ    might be denied if a data transfer operation was under way. Note that aE    one value in this bit may not be sufficient to ensure a successful-M    operation. This bit can only reflect the best information available to the K    medium changer device, which may not accurately reflect the state of the "    primary (data transfer) device.  E A not this bus (not bus) bit value of one indicates that the SCSI bus E address and logical unit number values are not valid for the SCSI bus-E used to select the medium changer device. A not bus bit value of zero F indicates that the SCSI address and logical unit values, if valid, are- on the same bus as the medium changer device.d  F An ID Valid bit value of one indicates that the SCSI bus address fieldG contains valid information. An LU Valid bit value of one indicates that 9 the logical unit number field contains valid information.l  G The SCSI bus address field, if valid, provides the SCSI address (binaryiE representation) of the primary device served by the medium changer ate this element address.o  B The logical unit number field, if valid, provides the logical unitE number within the SCSI bus device of the primary device served by thea' medium changer at this element address.   4 For fields not defined in this clause, see 17.2.5.3.  - 17.2.6 REQUEST VOLUME ELEMENT ADDRESS command2  E The REQUEST VOLUME ELEMENT ADDRESS command (see table 340) is used to D transfer the results of a SEND VOLUME TAG command.  Multiple REQUESTG VOLUME ELEMENT ADDRESS commands may be used to recover the results of a=9 single SEND VOLUME TAG command with the translate option.   @               Table 340 - REQUEST VOLUME ELEMENT ADDRESS commandO +=====-========-========-========-========-========-========-========-========+=O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |-O |=====+=======================================================================| O | 0   |                           Operation code (B5h)                        |-O |-----+-----------------------------------------------------------------------| O | 1   | Logical unit number      | VolTag |        Element type code          |-O |-----+-----------------------------------------------------------------------| O | 2   | (MSB)                                                                 |-O |-----+---                        Element address                          ---| O | 3   |                                                                 (LSB) |-O |-----+-----------------------------------------------------------------------| O | 4   | (MSB)                                                                 |-O |-----+---                        Number of elements                       ---| O | 5   |                                                                 (LSB) |-O |-----+-----------------------------------------------------------------------| O | 6   |                           Reserved                                    |-O |-----+-----------------------------------------------------------------------| O | 7   | (MSB)                                                                 |-O |-----+---                                                                 ---| O | 8   |                           Allocation length                           |-O |-----+---                                                                 ---| O | 9   |                                                                 (LSB) |-O |-----+-----------------------------------------------------------------------| O |10   |                           Reserved                                    |-O |-----+-----------------------------------------------------------------------| O |11   |                           Control                                     |-O +=============================================================================+     D For each SEND VOLUME TAG command, the target shall be able to reportE multiple elements that match a volume tag template in element address G order.  Once information for a given element address has been reported,0D only higher element addresses will be reported by subsequent REQUEST! VOLUME ELEMENT ADDRESS commands.    I    NOTE 205 In order to ensure the successful completion of a SEND VOLUME D    TAG, REQUEST VOLUME ELEMENT ADDRESS sequence in a multi-initiatorL    environment, it may be necessary to reserve the medium changer device. ToM    do this, issue a unit RESERVE command prior to the SEND VOLUME TAG command-L    and delay issuing the RELEASE until after the last REQUEST VOLUME ELEMENT    ADDRESS.   G A volume tag (VolTag) bit of one indicates that the target shall report A volume tag information. A value of zero indicates that volume tagtE information shall not be reported. This is provided for compatibility=% with the READ ELEMENT STATUS command.+  D The element type code field specifies the particular element type(s)G selected for reporting by this command.  A value of zero specifies thatnB status for all element types shall be reported. The codes for thisA field are defined in 17.2.5.  This acts as a qualification of thef> element(s) determined by SEND VOLUME TAG to match the template specified. t  F The element address field gives a medium changer element address whoseE interpretation depends on the send action code received with the lastiC SEND VOLUME TAG command.  This code is echoed in the volume elementdF address return format transferred by this command.  When the last send@ action code was a translate, (code values 0h .. 7h), the elementF address field gives the minimum element address to be reported by thisB command.  When the send action code is other than translate, (i.e.B assert, replace, and undefined, code values 8h .. Dh), the elementG address field gives the particular element whose volume tag informationp
 was modified.r  C The number of elements specifies the maximum number of elements andtD volume tags to be reported by the target for this command. The valueC specified by this field is not the range of element addresses to be.G considered for reporting but rather the number of elements to report of D those that match the last send volume tag translate template. If the? allocation length is not sufficient to transfer all the element E descriptors, the target shall transfer all those descriptors that can D be completely transferred and this shall not be considered an error.  D The data returned by this command consists of a header as defined byC table 341, plus one or more element type specific pages in the same 5 format as defined by the READ ELEMENT STATUS command.   ?                Table 341 - Volume element address header format|P +======-========-========-========-========-========-========-========-========+P |   Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P |Byte  |        |        |        |        |        |        |        |        |P |======+=======================================================================|P | 0    | (MSB)                                                                 |P |------+---                  First element address reported                 ---|P | 1    |                                                                 (LSB) |P |------+-----------------------------------------------------------------------|P | 2    | (MSB)                                                                 |P |------+---                    Number of elements reported                  ---|P | 3    |                                                                 (LSB) |P |------+-----------------------------------------------------------------------|P | 4    |          Reserved        |              Send action code              |P |------+-----------------------------------------------------------------------|P | 5    | (MSB)                                                                 |P |------+---                                                                 ---|P | 6    |                     Byte count of report available                    |P |------+---                        (all pages, x - 7 )                      ---|P | 7    |                                                                 (LSB) |P |======+=======================================================================|P |8 to  |                                                                       |P |  - --+---                     Element status page(s)                      ---|P | x    |                                                                       |P +==============================================================================+    C The send action code field gives the function performed by the last F SEND VOLUME TAG command as defined in 17.2.9. This command reports the+ results of this send action code operation.   7 For fields not defined in this subclause, see 17.2.5.1.-   17.2.7 RELEASE command  A The RELEASE command (see table 342) is used to release previously A reserved units, or, if the element release option is implemented,-E previously reserved elements within units.  It is not an error for an-C initiator to attempt to release a reservation that is not currently B active.  In this case, the target shall return GOOD status without altering any other reservation.   4                          Table 342 - RELEASE commandO +=====-========-========-========-========-========-========-========-========+-O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================|lO | 0   |                           Operation code (17h)                        |=O |-----+-----------------------------------------------------------------------|tO | 1   | Logical unit number      | 3rdPty | Third party device ID    | Element| O |-----+-----------------------------------------------------------------------|dO | 2   |                           Reservation identification                  |mO |-----+-----------------------------------------------------------------------| O | 3   |                           Reserved                                    |iO |-----+-----------------------------------------------------------------------|hO | 4   |                           Reserved                                    |aO |-----+-----------------------------------------------------------------------|eO | 5   |                           Control                                     |-O +=============================================================================+e     17.2.7.1 Logical unit release   B If the element bit is zero, this command shall cause the target toD terminate all non-third party unit and element reservations that are8 active from the initiator to the specified logical unit.  # 17.2.7.2 Element release (optional)n  ? If the element bit is one and the element release option is nots? implemented, the RELEASE command shall be terminated with CHECKiD CONDITION status and the sense key shall be set to ILLEGAL REQUEST. G This option shall be implemented if the element reservation option (seei 17.2.8.1) is implemented.   ; If the element bit is one and the element release option isa> implemented, this command shall cause any reservation from theE requesting initiator with a matching reservation identification to be2C terminated.  Other reservations from the requesting initiator shalld remain in effect.r   17.2.7.3 Third party release n  ? The third-party release option of the RELEASE command allows ano? initiator to release a unit or elements within a unit that werehB previously reserved using third-party reservation (see 17.2.8.3). C Third-party release shall be  implemented if third-party reserve is=
 implemented. =  G If the third-party (3rdPty) bit is zero, the third-party release option E is not requested.  If the 3rdPty bit is one and the target implements F the third-party release option, the target shall release the specifiedG unit or elements, but only if the reservation was made using the third- @ party reservation option by the initiator that is requesting theG release for the same SCSI device as specified in the third-party device 	 ID field.n  E If the 3rdPty bit is one and the target does not implement the third--G party release option, the target shall terminate the command with CHECK C CONDITION status and the sense key shall be set to ILLEGAL REQUEST.    17.2.8 RESERVE command  G The RESERVE command (see table 343) is used to reserve units or, if the D element reservation option is implemented, elements within units forF the use of the initiator.  The third-party reservation allows units orG elements to be reserved for another specified SCSI device.  The RESERVE ? and RELEASE commands provide the basic mechanism for contentionl) resolution in multiple-initiator systems.   4                          Table 343 - RESERVE commandO +=====-========-========-========-========-========-========-========-========+-O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |-O |=====+=======================================================================| O | 0   |                           Operation code (16h)                        | O |-----+-----------------------------------------------------------------------| O | 1   | Logical unit number      | 3rdPty | Third party device ID    | Element| O |-----+-----------------------------------------------------------------------| O | 2   |                           Reservation identification                  |-O |-----+-----------------------------------------------------------------------| O | 3   | (MSB)                                                                 |-O |-----+---                        Element list length                      ---| O | 4   |                                                                 (LSB) |=O |-----+-----------------------------------------------------------------------|tO | 5   |                           Control                                     | O +=============================================================================+g    ! 17.2.8.1 Logical unit reservationb  F If the element bit is zero, this command shall request that the entireA unit be reserved for the exclusive use of the initiator until theGC reservation is superseded by another valid RESERVE command from thevB initiator that made the reservation or until released by a RELEASEC command from the same initiator that made the reservation, by a BUS F DEVICE RESET message from any initiator, by a hard RESET condition, orD by a power off/on cycle.  A unit reservation shall not be granted ifF the unit or any element is reserved by another initiator.  It shall be@ permissible for an initiator to reserve a unit that is currently< reserved by that initiator.  If the element bit is zero, the? reservation identification and the element list length shall bea ignored.  D If the unit, or any element within the unit, is reserved for anotherE initiator, the target shall respond by returning RESERVATION CONFLICTo status.h  D If, after honouring the reservation, any other initiator attempts toG perform any command on the reserved unit other than an INQUIRY, REQUEST.G SENSE, ALLOW MEDIUM REMOVAL, RESERVE, or a RELEASE command, the commando4 shall be rejected with RESERVATION CONFLICT status.   ' 17.2.8.2 Element reservation (optional)n  C The reservation identification provides a means for an initiator torA identify each element reservation.  This allows an initiator in ar; multiple-tasking environment, to have multiple reservationsiC outstanding.  The reservation identification is used in the RELEASEnC command to specify which reservation is to be released.  It is also,G used in superseding RESERVE commands to specify which reservation is toh be superseded.  E If the element reservation option is implemented, the element releasenF option (see 17.2.7.2) shall also be implemented.  These options permitF multiple elements within the unit to be reserved, each with a separate reservation identification.d  @ If the element bit is one, and the element reservation option is@ implemented, the target shall process the reservation request as follows:I    a)     The element list shall be checked for valid element addresses. mF           If any element address is invalid for this unit, the commandK           shall be terminated with CHECK CONDITION status and the sense key E           shall be set to ILLEGAL REQUEST.  The element list shall beaA           checked for invalid element overlaps with other element E           descriptors in the element list and if invalid overlaps are E           found, the command shall be terminated with CHECK CONDITION=C           status and the sense key shall be set to ILLEGAL REQUEST.|K    b)     If the requested reservation does not conflict with any active ortK           previously requested reservation, the elements specified shall be I           reserved until superseded by another valid RESERVE command from=I           the initiator that made the reservation, or until released by a H           RELEASE command from the same initiator, by a BUS DEVICE RESETG           message from any initiator, or by a hard RESET condition.  If H           either of the last two conditions occur, the next command fromH           each initiator shall be terminated with CHECK CONDITION status;           and the sense key shall be set to UNIT ATTENTION. I    c)     If the reservation request conflicts with a reservation already E           active the target shall return RESERVATION CONFLICT status.-  D If the element bit is one, and the element reservation option is not? implemented, the RESERVE command shall be terminated with CHECKiA CONDITION status.  The sense key shall be set to ILLEGAL REQUEST.-  A The size of the element list shall be defined by the element list A length parameter.  The element list shall consist of zero or more @ descriptors as shown in table 344.  Each element list descriptorG defines a series of elements beginning at the specified element address C for the specified number of elements.  If the number of elements is G zero, the element list shall begin at the specified element address and 6 continue through the last element address on the unit.  @              Table 344 - Data format of element list descriptorsO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |=O |=====+=======================================================================|tO | 0   |                                                                       | O |- - -+---                         Reserved                                ---|oO | 1   |                                                                       |RO |-----+-----------------------------------------------------------------------|lO | 2   | (MSB)                                                                 |yO |-----+---                        Number of elements                       ---|tO | 3   |                                                                 (LSB) |eO |-----+-----------------------------------------------------------------------| O | 4   | (MSB)                                                                 |=O |-----+---                        Element address                          ---|4O | 5   |                                                                 (LSB) | O +=============================================================================+=    E If an initiator issues a command to an element that has been reserved D by a different initiator, the command shall not be performed and theE command shall be terminated with a RESERVATION CONFLICT status.  If aoC reservation conflict precludes any part of the command, none of the  command shall be performed.  -    17.2.8.3 Third party reservation  C The third-party reservation option of the RESERVE command allows anaF initiator to reserve a unit or elements within a unit for another SCSI device.-  D If the third-party (3rdPty) bit is zero, the third-party reservationF option is not requested.  If the 3rdPty bit is one and the third-partyD reservation option is implemented, the RESERVE command shall reserveC the specified unit or elements for the SCSI device specified in the-G third-party device ID field.  The target shall preserve the reservation @ until it is superseded by another valid RESERVE command from theG initiator that made the reservation or until it is released by the same=F initiator, by a BUS DEVICE RESET message from any initiator, or a hardD RESET condition.  The target shall ignore any attempt to release the( reservation made by any other initiator.  F If the 3rdPty bit is one and the third-party reservation option is notC implemented, the target shall reject the RESERVE command with CHECKhD CONDITION status and the sense key shall be set to ILLEGAL REQUEST.   ! 17.2.8.4 Superseding reservationsO  = An initiator that holds a current reservation may modify thatsG reservation by issuing another RESERVE command to the same unit and, if2G the element bit is one, using the same reservation identification.  ThesE superseding RESERVE command shall release the previous reservation inm? place when the new reservation request is granted.  The currenttG reservation shall not be modified if the new reservation request cannot E be granted.  If the superseding reservation cannot be granted becauser? of conflicts with a previous active reservation (other than theoB reservation being superseded), the target shall return RESERVATION CONFLICT status.  J    NOTE 206 Superseding reservations are principally intended to allow theF    SCSI device ID to be changed on a reservation using the third-party    reservation option.   17.2.9 SEND VOLUME TAG command  B The SEND VOLUME TAG command (see table 345) transfers a volume tagD template to be searched for or new volume tag information for one orG more media changer elements. The function of the command is conveyed byaF the send action code field. The REQUEST VOLUME ELEMENT ADDRESS command@ is used to transfer the results of a translate search operation.  8                      Table 345 - SEND VOLUME TAG commandO +=====-========-========-========-========-========-========-========-========+mO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |EO |Byte |        |        |        |        |        |        |        |        |rO |=====+=======================================================================|hO | 0   |                           Operation code (B6h)                        | O |-----+-----------------------------------------------------------------------| O | 1   | Logical unit number      |Reserved|        Element type code          |pO |-----+-----------------------------------------------------------------------|=O | 2   | (MSB)                                                                 | O |-----+---                        Element address                          ---|BO | 3   |                                                                 (LSB) |=O |-----+-----------------------------------------------------------------------| O | 4   |                           Reserved                                    |-O |-----+-----------------------------------------------------------------------| O | 5   |          Reserved        |              Send action code              |-O |-----+-----------------------------------------------------------------------| O | 6   |                                                                       |-O |-----+---                        Reserved                                 ---| O | 7   |                                                                       |-O |-----+-----------------------------------------------------------------------| O | 8   | (MSB)                                                                 |-O |-----+---                     Parameter list length                       ---| O | 9   |                                                                 (LSB) |=O |-----+-----------------------------------------------------------------------| O |10   |                           Reserved                                    |sO |-----+-----------------------------------------------------------------------|aO |11   |                           Control                                     |hO +=============================================================================+r    F The element type code field specifies an element type specification asA defined in 17.2.5.  If the send action code indicates a translateoD operation, this field indicates the element types to be searched. If@ this is a zero, all element types are candidates for a translateF operation. If the send action code does not indicate a translate, this# field shall be treated as reserved.s  E The send action code field gives the function to be performed by thisb  command as listed in table 346.   ;                    Table 346 - Send volume tag action codestO +=============-===============================================================+ O |    Code     |  Description                                                  |nO |-------------+---------------------------------------------------------------|RO |      0h     |  Translate - search all defined volume tags                   |NO |      1h     |  Translate - search only primary volume tags                  |nO |      2h     |  Translate - search only alternate volume tags                |oO |      3h     |  Reserved                                                     |eO |      4h     |  Translate - search all defined tags - ignore sequence numbers|SO |      5h     |  Translate - search primary tags - ignore sequence numbers    | O |      6h     |  Translate - search alternate tags - ignore sequence numbers  | O |      7h     |  Reserved                                                     |(O |      8h     |  Assert - as the primary volume tag - if tag now undefined    | O |      9h     |  Assert - as the alternate volume tag - if tag now undefined  |dO |      Ah     |  Replace - the primary volume tag - current tag ignored       |,O |      Bh     |  Replace - the alternate volume tag - current tag ignored     |mO |      Ch     |  Undefined - the primary volume tag - current tag ignored     |tO |      Dh     |  Undefined - the alternate volume tag - current tag ignored   |hO |   Eh - 1Bh  |  Reserved                                                     |UO |  1Ch - 1Fh  |  Vendor-specific                                              |wO +=============================================================================+l    B Translate operations request that the target search the volume tagE information available to it for elements whose volume tag informationQC matches the template given by the command parameters. The resulting G information is reported via the REQUEST VOLUME ELEMENT ADDRESS command.s  G Assert operations define volume tag information for a single element. ASG CHECK CONDITION with ILLEGAL REQUEST is reported if the subject element F already has defined volume tag information; in this case, the original/ volume tag information shall remain unaltered. y  F Replace operations define volume tag information for a single element.= Any previously defined volume tag information is overwritten.i  D Undefined operations cause previously defined volume tag informationF for the specified element to be cleared. It shall not be considered anA error to undefined volume tag information that was not previouslye defined.  B A medium changer device that implements volume tag information mayA choose to not implement the facilities that modify the volume tagSC information.  With such an implementation a request for the assert,sF replace or undefined functions would cause the SEND VOLUME TAG command@ to be terminated with CHECK CONDITION and a sense key of ILLEGAL REQUEST.  F The element address field gives a medium changer element address whoseA interpretation depends on the send action code received with this ? command. When the send action code is a translate, (code valuesnE 0h .. 7h), the element address field gives the starting element to beaF examined for satisfaction of the search criteria. When the send actionC code is other than translate, (i.e. assert, replace, and undefined,nE code values 8h .. Dh), the element address field gives the particular-7 element whose volume tag information is to be modified.   A The volume tag information used for translate, assert and replace|C functions is defined in table 347.  No parameters are necessary for= undefined operations.=  =                 Table 347 - Send volume tag parameters format O +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |-O |=====+=======================================================================|BO | 0   |                                                                       | O |- - -+---               Volume identification template field              ---| O | 31  |                                                                       |-O |-----+-----------------------------------------------------------------------|BO | 32  |                                                                       | O |-----+---                            Reserved                             ---| O | 33  |                                                                       |=O |-----+-----------------------------------------------------------------------|nO | 34  | (MSB)                                                                 |iO |- - -+---                  Minimum volume sequence number                 ---|iO | 35  |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|rO | 36  |                                                                       |sO |-----+---                            Reserved                             ---|iO | 37  |                                                                       |iO |-----+-----------------------------------------------------------------------|pO | 38  | (MSB)                                                                 |mO |- - -+---                  Maximum volume sequence number                 ---|gO | 39  |                                                                 (LSB) |VO +=============================================================================+y    D The volume identification template field specifies a search template= for translate functions and the exact value of the new volume G identification information for other SEND VOLUME TAG command functions.   D As a search template, this field may contain the wildcard charactersC '*' and '?' (2Ah and 3Fh). '*' will match any string of characters,tB when it appears in a template the remainder of the template is not+ used. '?' will match any single character.    G For a function other than translate, this field may not contain the '*'r or '?' wildcard characters.   C The minimum volume sequence number field specifies the new sequencefB number for the assert and replace functions. For a translate, thisC specifies the least value that will meet the search specification. .  E The maximum volume sequence number field specifies the greatest valuerA that will meet the search specification. This field is ignored onb functions other than translate.w  * 17.3 Parameters for medium changer devices     17.3.1 Diagnostic parameters  ? This subclause defines the descriptors and pages for diagnostic - parameters used with medium changer devices. t  C The diagnostic page codes for medium changer devices are defined ini table 348. p  7                       Table 348 - Diagnostic page codesaO +=============-==================================================-============+eO |  Page code  |  Description                                     | Subclause  |eO |-------------+--------------------------------------------------+------------| O |     00h     |  Supported diagnostic pages                      |  8.3.1.1   |tO |  01h - 3Fh  |  Reserved (for all device type pages)            |            |mO |  40h - 7Fh  |  Reserved                                        |            |=O |  80h - FFh  |  Vendor-specific pages                           |            | O +=============================================================================+      17.3.2 Log parameters=  C This subclause defines the descriptors and pages for log parameters " used with medium changer devices.   G The log page codes for medium changer devices are defined in table 349.-  4                           Table 349 - Log page codesO +=============-==================================================-============+-O |  Page code  |  Description                                     | Subclause  | O |-------------+--------------------------------------------------+------------| O |     00h     |  Supported log pages                             |  8.3.2.5   | O |     06h     |  Non-medium error page                           |  8.3.2.4   |-O |     07h     |  Last n error events page                        |  8.3.2.3   | O |  01h - 05h  |  Reserved                                        |            |-O |  08h - 2Fh  |  Reserved                                        |            | O |     3Fh     |  Reserved                                        |            |-O |  30h - 3Eh  |  Vendor-specific pages                           |            | O +=============================================================================+      17.3.3 Mode parameters  D This subclause defines the descriptors and pages for mode parameters" used with medium changer devices.   E The mode parameter list, including the mode parameter header and mode-' block descriptor, are defined in 8.3.3.   D The medium-type code field is contained in the mode parameter header@ (see 8.3.3).  This field is reserved for medium changer devices.  F The device specific parameter field is contained in the mode parameterG header (see 8.3.3).  This field is reserved for medium changer devices.-  ? The density code field is contained in the mode parameter block B descriptor (see 8.3.3).  This field is reserved for medium changer devices.  F The mode page codes for medium changer devices are shown in table 350.  4                          Table 350 - Mode page codesO +=============-==================================================-============+lO |  Page code  |  Description                                     | Subclause  |.O |-------------+--------------------------------------------------+------------|eO |     1Fh     |  Device capabilities                             | 17.3.3.1   |dO |     1Dh     |  Element address assignment                      | 17.3.3.2   |aO |     1Eh     |  Transport geometry parameters                   | 17.3.3.3   |gO |  01h - 1Ch  |  Reserved                                        |            | O |     00h     |  Vendor-specific (does not require page format)  |            |=O |  20h - 3Eh  |  Vendor-specific (page format required)          |            |rO |     3Fh     |  Return all pages                                |            |-O |             |     (valid only for the MODE SENSE command)      |            |sO +=============================================================================+s    ! 17.3.3.1 Device capabilities page   G The device capabilities page (see table 351) defines characteristics ofm= the element types on this medium changer implementation. This C information may be employed by the initiator to determine functionse: permitted by the MOVE MEDIUM and EXCHANGE MEDIUM commands.  9                      Table 351 - Device capabilities pageeO +=====-========-========-========-========-========-========-========-========+nO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |uO |=====+========+========+=====================================================|wO | 0   |   PS   |Reserved|         Page code (1Fh)                             |gO |-----+-----------------------------------------------------------------------| O | 1   |                       Parameter length (12h)                          | O |-----+-----------------------------------------------------------------------|aO | 2   |               Reserved            | StorDT | StorI/E| StorST | StorMT | O |-----+-----------------------------------------------------------------------| O | 3   |                           Reserved                                    |=O |-----+-----------------------------------------------------------------------|eO | 4   |               Reserved            | MT->DT | MT->I/E| MT->ST | MT->MT |cO |-----+-----------------------------------+--------+--------+--------+--------|rO | 5   |               Reserved            | ST->DT | ST->I/E| ST->ST | ST->MT |iO |-----+-----------------------------------+--------+--------+--------+--------|RO | 6   |               Reserved            |I/E->DT |I/E->I/E|I/E->ST |I/E->MT |aO |-----+-----------------------------------+--------+--------+--------+--------|yO | 7   |               Reserved            | DT->DT | DT->I/E| DT->ST | DT->MT |rO |-----+-----------------------------------------------------------------------|cO | 8   |                                                                       |lO |- - -+---                        Reserved                                 ---|hO | 11  |                                                                       |eO |-----+-----------------------------------------------------------------------|mO | 12  |               Reserved            | MT<>DT | MT<>I/E| MT<>ST | MT<>MT |lO |-----+-----------------------------------+--------+--------+--------+--------|tO | 13  |               Reserved            | ST<>DT | ST<>I/E| ST<>ST | ST<>MT |sO |-----+-----------------------------------+--------+--------+--------+--------|hO | 14  |               Reserved            |I/E<>DT |I/E<>I/E|I/E<>ST |I/E<>MT |rO |-----+-----------------------------------+--------+--------+--------+--------|lO | 15  |               Reserved            | DT<>DT | DT<>I/E| DT<>ST | DT<>MT |iO +=============================================================================+l    @ The parameters savable (PS) bit is only used with the MODE SENSEF command.  This bit is reserved with the MODE SELECT command.  A PS bitC of one indicates that the target is capable of saving the page in ad' non-volatile, vendor-specific location.r  ; In the field names on this page, the following element typee abbreviations are used:f(     MT       a medium transport element,     ST       a storage element,=1     I/E             an import export element, and4%     DT       a data transfer element. : In the descriptions, XX and YY are any of the element type abbreviations.    E A StorXX bit value of one indicated that the defined elements of type=G XX may provide independent storage for a unit of media. A value of zero = indicates that elements of type XX provide virtual sources oriF destinations, that the location of the unit of media is provided by an= element of some other type. The value of StorST is one by the-$ definition of that type. See 17.1.1.  C An XX->YY bit value of one indicates that the medium changer device F supports all MOVE MEDIUM commands where the source is element type XX,B the destination is element type YY and these element addresses areF otherwise valid. An XX->YY bit value of zero indicates that these MOVEC MEDIUM commands may or may not be valid depending on the particular-C elements requested. Those which are not valid will be rejected with  ILLEGAL REQUEST.  C An XX<>YY bit value of one indicates that the medium changer device F supports all EXCHANGE MEDIUM commands where the source is element typeG XX, destination 1 is element type YY, destination 2 is the same type as-A the source element type and these element addresses are otherwise G valid. An XX<>YY bit value of zero indicates that these EXCHANGE MEDIUM E commands may or may not be valid depending on the particular elements B requested. Those which are not valid will be rejected with ILLEGAL REQUEST.  ( 17.3.3.2 Element address assignment page  E The element address assignment page (see table 352) is used to assign D addresses to the elements of the medium changer (MODE SELECT) and toA report those assignments (MODE SENSE). This page also defines the ' number of each type of element present.   <                  Table 352 - Element address assignment pageO +=====-========-========-========-========-========-========-========-========+iO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |mO |Byte |        |        |        |        |        |        |        |        |sO |=====+========+========+=====================================================|2O | 0   |   PS   |Reserved|         Page code (1Dh)                             |lO |-----+-----------------------------------------------------------------------|eO | 1   |                           Parameter length (12h)                      | O |-----+-----------------------------------------------------------------------|sO | 2   | (MSB)                                                                 | O |-----+---                        Medium transport element address         ---| O | 3   |                                                                 (LSB) |tO |-----+-----------------------------------------------------------------------|aO | 4   | (MSB)                                                                 |eO |-----+---                        Number of medium transport elements      ---|sO | 5   |                                                                 (LSB) |gO |-----+-----------------------------------------------------------------------|gO | 6   | (MSB)                                                                 |=O |-----+---                        First storage element address            ---| O | 7   |                                                                 (LSB) |-O |-----+-----------------------------------------------------------------------| O | 8   | (MSB)                                                                 | O |-----+---                        Number of storage elements               ---| O | 9   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|=O | 10  | (MSB)                                                                 |rO |-----+---                        First import export element address      ---|oO | 11  |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------|=O | 12  | (MSB)                                                                 | O |-----+---                        Number of import export elements         ---|-O | 13  |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------| O | 14  | (MSB)                                                                 |gO |-----+---                        First data transfer element address      ---| O | 15  |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------| O | 16  | (MSB)                                                                 | O |-----+---                        Number of data transfer elements         ---|=O | 17  |                                                                 (LSB) |lO |-----+-----------------------------------------------------------------------|gO | 18  |                                                                       |mO |-----+---                        Reserved                                 ---|oO | 19  |                                                                       |dO +=============================================================================+o    @ The parameters savable (PS) bit is only used with the MODE SENSEF command.  This bit is reserved with the MODE SELECT command.  A PS bitC of one indicates that the target is capable of saving the page in ai& non-volatile vendor-specific location.  E The first medium transport element address field identifies the first D medium transport element contained in the medium changer (other thanC the default medium transport address of zero). The number of mediumsE transport elements field defines the total number of medium transport-A elements contained in the medium changer. If the number of medium-E transport elements field in a MODE SELECT command is greater than the1C default value returned in the MODE SENSE parameter data, the target D shall return CHECK CONDITION status and set the sense key to ILLEGAL REQUEST.  C The first storage element address field identifies the first medium G storage element contained in the medium changer.  The number of storageoB elements field defines the total number of medium storage elements@ contained in the medium changer. If the number of medium storageC elements field in a MODE SELECT command is greater than the default A value returned in the MODE SENSE parameter data, the target shall G return CHECK CONDITION status and set the sense key to ILLEGAL REQUEST.=  B The first import export element address field identifies the firstE medium portal that is accessible both by the medium transport devicesmF and also by an operator from outside the medium changer. The number ofF import export elements field defines the total number of import exportE elements contained in the medium changer and accessible to the medium F transport elements. If the number of import export elements field in aE MODE SELECT command is greater than the default value returned in the6B MODE SENSE parameter data, the target shall return CHECK CONDITION1 status and set the sense key to ILLEGAL REQUEST .   =    NOTE 207 The number of import export elements may be zero.=  G The first data transfer element address field identifies the first dataaD transfer element contained in the medium changer.  The data transferF elements may be either read/write or read-only devices.  The number ofF data transfer field defines the total number of data transfer elements@ contained within the medium changer and accessible to the mediumG transport elements.  If the number of data transfer elements field in a E MODE SELECT command is greater than the default value returned in the-B MODE SENSE parameter data, the target shall return CHECK CONDITION1 status and set the sense key to ILLEGAL REQUEST .-  E Each element in the medium changer must have a unique address. If the G address ranges defined for any of the element types overlap, the target-D shall return CHECK CONDITION status and set the sense key to ILLEGAL	 REQUEST. -  + 17.3.3.3 Transport geometry parameters page   F The transport geometry parameters page (see table 353) defines whetherC each medium transport element is a member of a set of elements that G share a common robotics subsystem and whether the element is capable of-E media rotation.  One transport geometry descriptor is transferred for > each medium transport element, beginning with the first mediumG transport element. (Other than the default transport element address of- zero.) -  >                 Table 353 - Transport geometry parameters pageO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |-O |=====+========+========+=====================================================||O | 0   |   PS   |Reserved|         Page code (1Eh)                             |+O |-----+-----------------------------------------------------------------------||O | 1   |                           Parameter length                            |+O |=====+=======================================================================||O |     |                        Transport geometry descriptor(s)               |+O |=====+==============================================================-========||O | 0   |                           Reserved                           | Rotate |=O |-----+-----------------------------------------------------------------------|tO | 1   |                Member number in transport element set                 | O +=============================================================================+-    @ The parameters savable (PS) bit is only used with the MODE SENSEF command.  This bit is reserved with the MODE SELECT command.  A PS bitC of one indicates that the target is capable of saving the page in a & non-volatile vendor-specific location.  ? The parameter length specifies the number of bytes of transport > geometry descriptors that follow.  The geometry of each mediumE transport element is defined using a two-byte field as defined below.p  ? A rotate bit of one indicates that the medium transport elementnF supports media rotation for handling double-sided media.  A rotate bitD of zero indicates that the medium transport element does not support media rotation.e  D The member number in set indicates the position of this element in a= set of medium transport elements that share a common roboticsgB subsystem. The first element in a set has a member number of zero.  J    NOTE 208 This page reports information about the way transport elementsG    are physically clustered in a system. The model for this is a mediumOJ    changer device with more than one independent robotics subsystem, whereL    each of these supports multiple transport elements. The elements that areH    supported by a particular robotics subsystem form a set. This sort ofM    information is helpful for optimization and error recovery in such a largeXI    system.  (Recall that in the model for this device type, see 17.1, the K    individual transport element is addressed not the robotics subsystem. An>M    element is defined to be a place where a unit of media may be at any point     in time.)  3 17.4 Definitions specific to medium changer devicesw  F 17.4.1 data transfer element:  A component of a medium changer used to@ access the data stored on a unit of media. The address in medium+ changer element space of a primary device. e  F 17.4.2 element:  An addressable physical component of a medium changer9 device that can serve as the location of a unit of media.b  A 17.4.3 import export element:  A location within a medium changerEE device that can be accessed by both the medium transport elements and= by the operator.  A 17.4.4 medium transport element:  A component of a medium changer - device that is used to move units of media.     D 17.4.5 media rotation:  The process of changing the orientation of aG unit of media. In particular this refers to inverting a two sided media=G cartridge so that a data transport element that can access only side at + a time can access data on the other side.  -  H 17.4.6 primary device:  A device for reading or writing data on medium. E These devices would typically implement the direct access, sequential-< access, optical memory device or CD-ROM command sets in thisE International Standard.  Examples are magnetic disk drives, cartridge D tape drives, optical disk drives and CD-ROM drives.  Use in a mediumG changer environment implies that the device supports removable media.       D 17.4.7 storage element:  A component of a medium changer device used( for inactive storage of a unit of media.     18 Communications devices       18.1 Communications device model  ? A communications device provides a facility to send and receivesB information over some medium (usually an electrical or fiber-opticA cable) using a defined protocol to one or more other systems that-G support the same protocol.  The media and protocols are often specified G in national or international standards, although some are proprietary.  B Within this subclause, the protocol used on the external medium is called the external protocol.   @ The SCSI communications device model assumes that information toE control the external protocol is embedded within the data transferred @ by the SEND and GET MESSAGE commands.  The structure of the dataB transferred by these commands is not defined by this International= Standard.  Vendor-unique MODE pages may be defined to provide . additional control over the external protocol.  F The SCSI communications device is a target with the characteristics ofC a network access device, typically attached to a local area network D (LAN), public telecommunications network, private telecommunicationsH network, or packet switching network, etc., with no theoretical limits. A Such a communications device is often called a network node.  The-> communications device transmits or receives packets of data asA requested by the initiator.  The contents and meaning of the data-G packets is not defined by this standard.  The bytes in the data packets-B may or may not contain addressing, path selection, or path controlF information identifying separate data streams.  Additional informationG may be provided by the stream selection identifier found in the ten and 2 twelve byte SEND MESSAGE and GET MESSAGE commands.  F In the SCSI communications device, the target accepts and provides theF data packets transferred in accordance with commands received from the= initiator.  There is an assumption that the initiator and the-F communications device know the rules by which information is exchanged= between them, how the information is to be interpreted by the ? communications device, and when it is allowable to exchange the A information.  These rules are not specified by this International-	 Standard.-  E The initiator requests that the communications device accept a packet G of data by transmitting a SEND MESSAGE command.  The initiator requestsmF that the communications device return a packet of data by transmitting? a GET MESSAGE command.  The communications device also supports B commands related to configuration of the network access device andF network management of the particular environment.  MODE SENSE and MODE4 SELECT are examples of these configuration commands.  C If a communications device temporarily has no resource available totA handle a data packet from the initiator, or has no data packet toeE provide to the initiator, or has no resources assigned to perform thesF operation, the device may then choose one of the following responses: K    a)     Terminate the command with CHECK CONDITION status.  The sense keyeH           shall be set to NOT READY and the appropriate additional sense!           code for the condition.dH    b)     Disconnect until the necessary resource or data packet becomesG           available, and then reconnect to the initiator and resume the            operation.1    c)     Terminate the command with BUSY status.s  B More than one logical unit  can be implemented by a communicationsG device.   Logical units can serve as multiple paths to a single networkiG access device, and/or each logical unit can serve as a discrete path tosF different resources within the device.  A single logical unit may alsoF serve as a path to multiple resources if the communications device canD interpret information within the data packet and route the packet to? the appropriate resource.  If the logical unit addressed by the G initiator does not have an available resource or data packet associatedmG with it, the communications device may choose to treat the logical unitbE as an invalid logical unit (see 7.5.3) or respond as described in thei previous paragraph..  @ If the communications device determines that an error or unusualE condition has occurred while performing an operation specified by theiF contents of a data packet, the information describing the condition isA normally returned as a part of a data packet from another network A device.  If the communications device determines that an error or F unusual condition has occurred while either executing the SCSI commandF from the initiator, or during a network medium access transaction, the? command is terminated with a CHECK CONDITION.  The failures aret+ identified through a REQUEST SENSE command.i  F The SCSI communications device is distinguished from an SCSI processorC device by the fact that the primary destination of the data packetsuA transferred to the communications device is not the target device F itself, but another network node.  A SCSI communications device passesC the data on to an ultimate destination outside the target through ahF network.  In contrast, the SCSI processor device is itself the primaryA destination of the data packets.  Devices requiring protocols andAB command sets that are totally incompatible with the communicationsA device protocols should be examined carefully to be sure that they9 incompatibilities are based on functional requirements.  u   18.1.1 Implementation examples  F Several examples of communications device implementations are provided4 to clarify the range of utility of this device type.  % 18.1.1.1 Host-to-host communications a  E In this example of host to host communications, only the SEND MESSAGE  command is used.  F A communications device (comm A) is attached to a network (net A), andD another communications device (comm B) is attached to a network (netA B).  Comm A takes the initiator role and selects a communicationseG device (comm B), transmitting a packet to comm B using the SEND MESSAGEyF command.  After transmitting the packet on the attached network medium@ (net B), the action required by the SEND MESSAGE command, comm BA assumes the initiator mode and selects comm A as a communications C device, and uses a SEND MESSAGE command to transmit a packet on the=% network (net A) attached to comm A.  =  F    Note 209 The SEND MESSAGE command is sufficient to perform completeJ    transactions between communications devices if comm A and comm B act asM    initiators.  This provides the function of a network bridge or gateway foraB    high bandwidth intercommunication among nearby host processors.  ' 18.1.1.2 Host-to-device communications =  F In this example of host to device communications, the SEND MESSAGE and GET MESSAGE commands are used.  = A host system, host A, takes the initiator role and selects a== communications device (comm A) attached to a network (net A), D transmitting a packet on network net A to some other network node(s)E using the SEND MESSAGE command to comm A.  Host A then assumes that abD result will be obtained by the other network node(s) consistent withE rules understood by all involved network devices.  Host A generates aaC GET MESSAGE command to obtain packets from other network nodes.  IfhE there are no packets that need handling pending at comm A, comm A mayc@ disconnect until a packet arrives.  Comm A can then complete theF transaction,  reconnect to host A and the requested data packet can beF returned to host A.  Note that Host A need not support target mode andB Comm A need not support initiator mode to successfully complete anB exchange between the two devices.  The host system (host A) can beC replaced by a communications device that is capable of acting as ani
 initiator.  & 18.1.1.3 Multiple role communications   E In this example of multiple role communications, the SEND MESSAGE andnD GET MESSAGE commands are used.  The device acts as both a host and aF communications device, depending on its needs and the requests made in the network.  F A communications device (comm A) is attached to a network (net A), andE another communications device (comm B)  is attached to a network (netsA B).  Comm A takes the initiator role and selects a communications G device (comm B).  Comm A transmits a packet for network net B using the G SEND MESSAGE command to comm B.  Comm A then requests data packets fromtG net B by issuing a GET MESSAGE command to the comm B device.  FollowingpG these actions, comm B assumes the initiator role and transmits a packetcD using the SEND MESSAGE command to comm A for transmission to networkG node(s) located on net A.  Comm B then requests data packets from net Ae+ by issuing a GET MESSAGE command to comm A.   4 18.2 Command descriptions for communications devices  G The commands for communications devices shall be as shown in table 354.A  >                Table 354 - Commands for communications devicesH +=====================================-============-======-============+H |  Command name                       | Operation  | Type |  Subclause |H |                                     |   code     |      |            |H |-------------------------------------+------------+------+------------|H | CHANGE DEFINITION                   |    40h     |   O  |   8.2.1    |H | GET MESSAGE(6)                      |    08h     |   O  |   8.2.17   |H | GET MESSAGE(10)                     |    28h     |   O  |  18.2.2    |H | GET MESSAGE(12)                     |    A8h     |   O  |  18.2.3    |H | INQUIRY                             |    12h     |   M  |   8.2.5    |H | LOG SELECT                          |    4Ch     |   O  |   8.2.6    |H | LOG SENSE                           |    4Dh     |   O  |   8.2.7    |H | MODE SELECT(6)                      |    15h     |   O  |   8.2.8    |H | MODE SELECT(10)                     |    55h     |   O  |   8.2.9    |H | MODE SENSE(6)                       |    1Ah     |   O  |   8.2.10   |H | MODE SENSE(10)                      |    5Ah     |   O  |   8.2.11   |H | READ BUFFER                         |    3Ch     |   O  |   8.2.12   |H | RECEIVE DIAGNOSTIC RESULTS          |    1Ch     |   O  |   8.2.13   |H | REQUEST SENSE                       |    03h     |   M  |   8.2.14   |H | SEND DIAGNOSTIC                     |    1Dh     |   M  |   8.2.15   |H | SEND MESSAGE(6)                     |    0Ah     |   M  |  18.2.4    |H | SEND MESSAGE(10)                    |    2Ah     |   O  |  18.2.5    |H | SEND MESSAGE(12)                    |    AAh     |   O  |  18.2.6    |H | TEST UNIT READY                     |    00h     |   M  |   8.2.16   |H | WRITE BUFFER                        |    3Bh     |   O  |   8.2.17   |H |----------------------------------------------------------------------|H |Key:  M = command implementation is mandatory.                        |H |      O = command implementation is optional.                         |H +======================================================================+    E All other operation codes for communications devices are reserved forf future standardization.n   18.2.1 GET MESSAGE(6) commando  B The GET MESSAGE(6) command (see table 355) transfers data from the target to the initiator.  8                       Table 355 - GET MESSAGE(6) commandO +=====-========-========-========-========-========-========-========-========+tO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |iO |Byte |        |        |        |        |        |        |        |        |iO |=====+=======================================================================|tO | 0   |                           Operation code (08h)                        |-O |-----+-----------------------------------------------------------------------| O | 1   | Logical unit number      |                  Reserved                  |eO |-----+-----------------------------------------------------------------------|GO | 2   | (MSB)                                                                 | O |-----+---                                                                 ---|tO | 3   |                           Allocation length                           |sO |-----+---                                                                 ---|nO | 4   |                                                                 (LSB) |oO |-----+-----------------------------------------------------------------------|nO | 5   |                           Control                                     |eO +=============================================================================+e     18.2.2 GET MESSAGE(10) command  C The GET MESSAGE(10) command (see table 356) transfers data from theo target to the initiator.  8                      Table 356 - GET MESSAGE(10) commandO +=====-========-========-========-========-========-========-========-========+nO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |nO |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================|eO | 0   |                           Operation code (28h)                        |oO |-----+-----------------------------------------------------------------------|hO | 1   | Logical unit number      |                  Reserved                  |sO |-----+-----------------------------------------------------------------------|yO | 2   |                           Reserved                                    |iO |-----+-----------------------------------------------------------------------|iO | 3   |                           Reserved                                    |tO |-----+-----------------------------------------------------------------------|cO | 4   | (MSB)                                                                 | O |-----+---                        Stream selection                         ---|mO | 5   |                                                                 (LSB) |tO |-----+-----------------------------------------------------------------------| O | 6   |                           Reserved                                    |kO |-----+-----------------------------------------------------------------------|lO | 7   | (MSB)                                                                 |rO |-----+---                        Allocation length                        ---|uO | 8   |                                                                 (LSB) |tO |-----+-----------------------------------------------------------------------|rO | 9   |                           Control                                     |oO +=============================================================================+e    F The stream selection field specifies a further level of addressing forG the data, so that it can be accessed by the target from the appropriateT data stream.   18.2.3 GET MESSAGE(12) command  C The GET MESSAGE(12) command (see table 357) transfers data from thea target to the initiator.  8                      Table 357 - GET MESSAGE(12) commandO +=====-========-========-========-========-========-========-========-========+ O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |iO |Byte |        |        |        |        |        |        |        |        |rO |=====+=======================================================================|eO | 0   |                           Operation code (A8h)                        |nO |-----+-----------------------------------------------------------------------|oO | 1   | Logical unit number      |                  Reserved                  |xO |-----+-----------------------------------------------------------------------| O | 2   |                           Reserved                                    |mO |-----+-----------------------------------------------------------------------|SO | 3   |                           Reserved                                    |rO |-----+-----------------------------------------------------------------------|nO | 4   | (MSB)                                                                 |oO |-----+---                        Stream selection                         ---|rO | 5   |                                                                 (LSB) |dO |-----+-----------------------------------------------------------------------| O | 6   | (MSB)                                                                 |kO |-----+---                                                                 ---|EO | 7   |                                                                       |sO |-----+---                        Allocation length                        ---|oO | 8   |                                                                       |aO |-----+---                                                                 ---|lO | 9   |                                                                 (LSB) |eO |-----+-----------------------------------------------------------------------|cO | 10  |                           Reserved                                    |nO |-----+-----------------------------------------------------------------------|mO | 11  |                           Control                                     |dO +=============================================================================+e    F The stream selection field specifies a further level of addressing forG the data, so that it can be accessed by the target from the appropriatea data stream.   18.2.4 SEND MESSAGE(6) command  C The SEND MESSAGE(6) command (see table 358) transfers data from thee initiator to the target.  8                      Table 358 - SEND MESSAGE(6) commandO +=====-========-========-========-========-========-========-========-========+nO |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |nO |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================| O | 0   |                           Operation code (0Ah)                        |aO |-----+-----------------------------------------------------------------------|wO | 1   | Logical unit number      |                  Reserved                  |nO |-----+-----------------------------------------------------------------------| O | 2   | (MSB)                                                                 |tO |-----+---                                                                 ---|CO | 3   |                           Transfer length                             | O |-----+---                                                                 ---|aO | 4   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------| O | 5   |                           Control                                     | O +=============================================================================+w    G The transfer length specifies the length in bytes of data that shall bevD sent during the DATA OUT phase.  A transfer length of zero indicatesF that no data shall be sent.  This condition shall not be considered an error.   18.2.5 SEND MESSAGE(10) command   D The SEND MESSAGE(10) command (see table 359) transfers data from the initiator to the target.  9                      Table 359 - SEND MESSAGE(10) command4O +=====-========-========-========-========-========-========-========-========+|O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        | O |=====+=======================================================================| O | 0   |                           Operation code (2Ah)                        |SO |-----+-----------------------------------------------------------------------| O | 1   | Logical unit number      |                  Reserved                  | O |-----+-----------------------------------------------------------------------| O | 2   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------| O | 3   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|.O | 4   | (MSB)                                                                 | O |-----+---                        Stream selection                         ---|MO | 5   |                                                                 (LSB) |1O |-----+-----------------------------------------------------------------------| O | 6   |                           Reserved                                    | O |-----+-----------------------------------------------------------------------|-O | 7   | (MSB)                                                                 | O |-----+---                        Transfer length                          ---| O | 8   |                                                                 (LSB) |=O |-----+-----------------------------------------------------------------------|oO | 9   |                           Control                                     |(O +=============================================================================+     F The stream selection field specifies a further level of addressing forE the data, so that it can be directed by the target to the appropriate  data stream.  D Please refer to the SEND MESSAGE(6) command for a description of the fields in this command.    18.2.6 SEND MESSAGE(12) command   D The SEND MESSAGE(12) command (see table 360) transfers data from the initiator to the target.  9                      Table 360 - SEND MESSAGE(12) command O +=====-========-========-========-========-========-========-========-========+-O |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | O |Byte |        |        |        |        |        |        |        |        |-O |=====+=======================================================================| O | 0   |                           Operation code (AAh)                        | O |-----+-----------------------------------------------------------------------| O | 1   | Logical unit number      |                  Reserved                  | O |-----+-----------------------------------------------------------------------| O | 2   |                           Reserved                                    |-O |-----+-----------------------------------------------------------------------| O | 3   |                           Reserved                                    |=O |-----+-----------------------------------------------------------------------|tO | 4   | (MSB)                                                                 | O |-----+---                        Stream selection                         ---|=O | 5   |                                                                 (LSB) | O |-----+-----------------------------------------------------------------------| O | 6   | (MSB)                                                                 |=O |-----+---                                                                 ---|oO | 7   |                                                                       |-O |-----+---                        Transfer length                          ---| O | 8   |                                                                       |-O |-----+---                                                                 ---|dO | 9   |                                                                 (LSB) |-O |-----+-----------------------------------------------------------------------|dO | 10  |                           Reserved                                    |-O |-----+-----------------------------------------------------------------------| O | 11  |                           Control                                     |sO +=============================================================================+     F The stream selection field specifies a further level of addressing forE the data, so that it can be directed by the target to the appropriate  data stream.  D Please refer to the SEND MESSAGE(6) command for a description of the fields in this command.-  ) 18.3 Parameters for communication devices    18.3.1 Diagnostic parameters  ? This subclause defines the descriptors and pages for diagnostico, parameters used with communication devices.   B The diagnostic page codes for communication devices are defined in
 table 361.  7                       Table 361 - Diagnostic page codes-O +=============-==================================================-============+ O |  Page Code  |  Description                                     |  Subclause |=O |-------------+--------------------------------------------------+------------|dO |     00h     |  Supported log pages                             |   8.3.1.1  |iO |  01h - 3Fh  |  Reserved (for all device type pages)            |            |nO |  40h - 7Fh  |  Reserved                                        |            | O |  80h - FFh  |  Vendor-specific pages                           |            |-O +=============================================================================+|     18.3.2 Log parameters   C This subclause defines the descriptors and pages for log parameters|! used with communication devices. =  F The log page codes for communication devices are defined in table 362.  4                           Table 362 - Log page codesO +=============-==================================================-============+-O |  Page code  |  Description                                     |  Subclause |eO |-------------+--------------------------------------------------+------------|-O |     01h     |  Buffer over-run/under-run page                  |   8.3.2.1  | O |     02h     |  Error counter page (write) page                 |   8.3.2.2  |-O |     03h     |  Error counter page (read) page                  |   8.3.2.2  | O |     04h     |  Error counter page (read reverse) page          |   8.3.2.2  |-O |     05h     |  Error counter page (verify) page                |   8.3.2.2  | O |     07h     |  Last n error events page                        |   8.3.2.3  | O |     06h     |  Non-medium error page                           |   8.3.2.4  | O |     00h     |  Supported log pages                             |   8.3.2.5  |-O |  08h - 2Fh  |  Reserved                                        |            | O |  30h - 3Eh  |  Vendor-specific pages                           |            | O |     3Fh     |  Reserved                                        |            | O +=============================================================================+      18.3.3 Mode parameters  D This subclause defines the descriptors and pages for mode parameters! used with communication devices.    E The mode parameter list, including the mode parameter header and mode ' block descriptor, are defined in 8.3.3.   D The medium-type code field is contained in the mode parameter header@ (see 8.3.3).  This field is reserved for communications devices.  F The device specific parameter field is contained in the mode parameterG header (see 8.3.3).  This field is reserved for communications devices.   ? The density code field is contained in the mode parameter block=B descriptor (see 8.3.3).  This field is reserved for communications devices.  F The mode page codes for communications devices are shown in table 363.  4                          Table 363 - Mode page codesO +=============-==================================================-============+SO |  Page code  |  Description                                     |  Subclause |.O |-------------+--------------------------------------------------+------------|=O |     0Ah     |  Control mode page                               |   8.3.3.1  |6O |     02h     |  Disconnect-reconnect page                       |   8.3.3.2  | O |     09h     |  Peripheral device page                          |   8.3.3.3  |=O |     01h     |  Reserved                                        |            | O |  03h - 08h  |  Reserved                                        |            |-O |  0Bh - 1Fh  |  Reserved                                        |            |tO |     00h     |  Vendor-specific (does not require page format)  |            |-O |  20h - 3Eh  |  Vendor-specific (page format required)          |            | O |     3Fh     |  Return all pages                                |            | O |             |     (valid only for the MODE SENSE command)      |            | O +=============================================================================+     3 18.4 Definitions specific to communications devices-  G 18.4.1 communications device:   An SCSI device whose principal function > is to communicate with one or more other systems, usually over@ distances that exceed the maximum cable length defined for SCSI.  F 18.4.2 external medium:   The medium used by the communications deviceD to send or receive information to or from one or more communicationsE devices.  The other communications devices may or may not use an SCSI 
 interface.  F 18.4.3 external protocol:   The protocol(s) used by the communicationsF device to transfer information over the external medium.  The external; protocol(s) are not defined by this International Standard.)         Annex Ar
 (informative)o   SCSI signal sequence example    E This annex is included to provide an example of the signal sequencing=G of an I/O process that includes most of the SCSI bus phases (see figure6G 29).  In this example, the target does not disconnect from the SCSI bus $ prior to completing the I/O process.  M    In a typical system, the computer's host adapter acts as the initiator and=K    the peripheral device's controller acts as the target.  In general, thisoL    International Standard does not attempt to distinguish between a computerI    and its host adapter.  These functions may be separate or merged.  The M    term initiator encompasses both.  The term target refers to the controller-B    portion of the peripheral device, which may be separate (bridgeE    controller) from the peripheral device or merged with it (embedded-D    controller).  The term SCSI device refers to a device that may beL    connected to the SCSI bus.  An SCSI device may act in the initiator role,"    the target role, or both roles.  ( The following notes apply to figure A.1.   DATA BUS NOTES,    1)     DB(7) is the most significant bit.8    2)     DB(7) is the highest priority arbitration bit.I    3)     DB(P) is the data parity bit (odd).  Parity is not valid during             the ARBITRATION phase.   BUS PHASE NOTES1H    1)        BUS FREE phase.  BUS FREE phase begins when the SEL and BSYL              signals are both continuously false for a bus settle delay.  ItK              ends when the BSY signal becomes true.  (In the SCSI-1 single--I              initiator option, BUS FREE phase could also end when the SEL !              signal became true.)   I    2)        ARBITRATION phase.  This phase is documented as mandatory in 9              SCSI-2.  In SCSI-1, this phase was optional.   K           At least one bus free delay after first detecting BUS FREE phase,-K           but no more than a bus set delay after the bus was last free, the J           initiator asserts the BSY signal and its assigned SCSI device IDI           bit on the DATA BUS.  The initiator waits an arbitration delay,rJ           then examines the DATA BUS.  If a higher priority SCSI device IDJ           bit is true, the initiator loses arbitration and may release theH           BSY signal and its SCSI ID bit.  Otherwise, the initiator winsH           arbitration and asserts the SEL signal.  All SCSI devices mustI           release the BSY signal and their SCSI ID bit within a bus clear0H           delay after the SEL signal becomes true (even if they have notG           yet examined the DATA BUS).  The winning SCSI device waits at I           least a bus clear delay plus a bus settle delay after asserting @           the SEL signal before changing any signals on the bus.  K    3)        SELECTION phase.  The I/O signal is false during this phase to 7              distinguish it from the RESELECTION phase.   I              NON-ARBITRATING SYSTEMS (only permitted in SCSI-1):  In such-J              systems, the initiator waits at least a bus clear delay afterL              detecting BUS FREE phase, then it asserts the target's  SCSI IDI              bit and, optionally, the initiator's SCSI ID bit on the DATA J              BUS.  After at least two deskew delays, the initiator asserts              the SEL signal.  L              ARBITRATING SYSTEMS:  In such systems, the SCSI device that wonJ              arbitration has both the BSY and SEL signals asserted.  AfterJ              at least a bus clear delay plus a bus settle delay, it placesK              both the target's and the initiator's SCSI ID bits on the DATA H              BUS.  At least two deskew delays later, it releases the BSY              signal.  I              ALL SYSTEMS:  The target determines that it is selected when-L              the SEL signal and its SCSI ID bit are true and the BSY and I/OK              signals are false for at least a bus settle delay.  The target L              then asserts the BSY signal within a selection abort time afterG              it last determined that it was still being selected.  (ThenF              target is not required to respond to a selection within aG              selection abort time;  but it must ensure that it will not I              assert the BSY signal more than a selection abort time after 7              the initiator aborts a selection attempt.)-  H           At least two deskew delays after the initiator detects the BSY5           signal is true, it releases the SEL signal.   I    4)        MESSAGE OUT phase.  During this phase the initiator sends an-L              IDENTIFY message to the target.  The target asserts the C/D andC              MSG signals and negates the I/O signal for the message=L              transfer.  After detecting the assertion of the REQ signal, theF              initiator negates the ATN signal before asserting the ACKG              signal.  (Refer to the handshake procedure for the commande              phase.)  J    5)        COMMAND phase.  The target asserts the C/D signal and negatesL              the I/O and MSG signals for all of the bytes transferred duringL              this phase.  The direction of transfer is from the initiator to              the target.  H           HANDSHAKE PROCEDURE:  The target asserts the REQ signal.  UponI           detecting the REQ signal is true, the initiator drives the DATA=J           BUS to the desired value, waits at least one deskew delay plus aJ           cable skew delay and then asserts the ACK signal.  The initiatorH           continues to drive the DATA BUS until the REQ signal is false.  I           When the ACK signal is true at the target, the target reads the 3           DATA BUS and then negates the REQ signal.c  K           When the REQ signal becomes false at the initiator, the initiator G           may change or release the DATA BUS and negate the ACK signal.f  K           The target may continue to request command bytes by asserting the=I           REQ signal again.  The number of command bytes is determined bytK           the group code (most significant 3 bits) that is contained in the            first command byte..  J    6)        DATA IN phase.  The target asserts the I/O signal and negatesK              the C/D and MSG signal for all of the bytes transferred during=I              this phase.  The direction of transfer is from the target to               the initiator.   G           HANDSHAKE PROCEDURE:  The target first drives the DATA BUS to-F           their desired values, waits at least one deskew delay plus aH           cable skew delay, and then asserts the REQ signal.  The targetG           continues to drive the DATA BUS until the ACK signal is true.   K           When the REQ signal is true at the initiator, the initiator reads 7           the DATA BUS and then asserts the ACK signal.8  J           When the ACK signal is true at the target, the target may change<           or release the DATA BUS and negate the REQ signal.  F           When the REQ signal is false at the initiator, the initiatorE           negates the ACK signal.  After the ACK signal is false, thelF           target may continue the transfer by driving the DATA BUS and6           asserting the REQ signal as described above.  J    7)        DATA OUT phase (not shown in the figure).  The target negatesK              the C/D, I/O, and MSG signals for all of the bytes transferred|F              during this phase.  The direction of transfer is from theL              initiator to the target.  (Refer to the handshake procedure for               the command phase.)  J    8)        STATUS phase.  The target asserts the C/D and I/O signals andH              negates the MSG signal for the byte transferred during thisH              phase.  The direction of transfer is from the target to theJ              initiator.  (Refer to the handshake procedure for the DATA IN              phase.)  H    9)        MESSAGE IN phase.  The target asserts the C/D, I/O, and MSGD              signals during the byte transferred during this phase. H              Typically, a command COMPLETE message would be sent at thisH              point.  The direction of transfer is from the target to theJ              initiator.  (Refer to the handshake procedure for the DATA IN              phase.)  E    10)       BUS FREE phase.  The target returns to BUS FREE phase by=I              releasing the BSY signal.  Both the target and the initiator K              release all bus signals within a bus clear delay after the BSY-A              signal is continuously false for a bus settle delay.                                                                                                 ;                   Figure A.1 - SCSI signal sequence examplei       Annex B 
 (informative)    Fast SCSI skew time     C This annex is included to explain the skew budget for the fast SCSI $ option which is defined in Clause 4.  E Synchronous transfer rates using a transfer period between 100 ns and C 200 ns are known as the fast SCSI option.  Fast data transfer times E have been tested using the following skew budget (see table B.1) withhE the differential alternative using transceivers with 25 m of 0,080 42 ; mm2 (28 AWG) twisted pair cable as specified in 5.2.3.  The E transceivers were subjected to a maximum temperature difference of 25N4 degrees C and a maximum of 200 mV of VCC difference.  8                      Table B.1 - Fast SCSI jitter budgetO +================-============================================-===============+nO |       Parameter|                                            | Jitter budget |oO |           label|           Description                      |    +/- ns     |hO |----------------+--------------------------------------------+---------------|iO |              a | clock offset                               |       5       | O |              b | transmitting logic skew                    |       3       |.O |Transmitting  c | foil delay                                 |       1       |eO |  Device      d | transmitter propogation delay skew         |       6       | O |              e | foil delay                                 |       1       | O |              f | drop cable propogation delay               |       1       | O |-- Connector  --|--------------------------------------------|---------------|eO |              g | external cable - skew between pairs        |       5       |SO |   Cable      h | distortion due to cable impedance          |       1       |tO |              i | distortion due to intersymbol interferance |       2       |eO |              j | bias distortion                            |       2       |mO |-- Connector  --|--------------------------------------------|---------------|aO |              k | drop cable propogation delay               |       1       |gO |Receiving     l | foil delay                                 |       1       |eO | Device       m | receiver propogation delay skew            |       9       |dO |              n | foil delay                                 |       1       |nO |              o | logic setup/hold                           |       5       |rO |----------------+--------------------------------------------+---------------|NO |                | total jitter budget                        |      44       |tO +=============================================================================+   E Mapping the above jitter or skew budget to the SCSI format in 5.7 and1 5.8 is done in Table B.2.s  9                     Table B.2 - Mapping of jitter to SCSIs7 +=======================-=============-===============+.7 | SCSI timing parameter | Calculation | Value (ns)    | 7 |-----------------------+-------------+---------------|B7 | Fast cable skew delay |      g      |   5           |s7 | Fast deskew delay     |  SUM(h..n)  |  20 (note 1)  |T7 | Fast hold time        |      o      |  10 (note 1)  |S7 | Fast assertion period |   (note 2)  |  30           |t7 | Fast negation period  |   (note 2)  |  30           |p7 |-----------------------------------------------------|t7 | Notes                                               |h7 |  1) Value is rounded up from the jitter budget.     |i7 |  2) The fast assertion period and fast negation     |l7 |     period are derived from isolated pulse          |p7 |     mesurements and represent a minimum pulse width |t7 |     with a satisfactory margin.                     |i7 +=====================================================+     H The maximum driver skew allowed was 6 ns (tPLH min. - tPHL max.) and theF maximum receiver skew tested was 9 ns (tPLH min. - tPHL max.).  ValuesE greater than these could be used if other numbers could be reduced --t the sum is what is important.T  D Fast data transfer timing parameters were not tested for the single-C ended transceiver option prior to publication of this Internationaln	 Standard.h       Annex Ca
 (informative)   % Other SCSI standardization activitiess    ? This annex provides information on other formal standardizationm activities related to SCSI.    C.1 SCSI-3 standards projectsS  F Accredited Standards Committee X3 has approved several SCSI-3 projectsG to enhance and restructure the SCSI-2 standard as shown in figure C.1.  E These projects (except fibre channel) are assigned to the X3T9.2 Taski@ Group which developed this International Standard and the SCSI-1< standard.  Please contact the Chairman of X3T9.2 for further& information concerning these projects.  8 C.2 Digital data exchange for colour electronic prepress systems   B Accredited Standards Committee IT8 has developed several standardsD pertaining to the exchange of digital data between colour electronic@ prepress systems.  These devices are used for high quality colorF printing.  At least one of the IT8 projects involves transferring suchB data over SCSI.  Please contact the Secretariat of IT8 for further& information concerning their projects.   C.3 Fibre channel   E Accredited Standards Committee X3 has approved a project to develop a A fibre optic channel physical layer for the Intelligent PeripheraltB Interface (IPI), SCSI, and the High Performance Parallel InterfaceD (HIPPI).  This project is assigned to the X3T9.3 Task Group.  PleaseF contact the Chairman of X3T9.3 for further information concerning this project.                                          :                    Figure C.1 - SCSI-3 standards structure         Annex Dl
 (informative)l   Numeric order codes     E This annex contains SCSI-2 additional sense codes and operation codeslA in numeric order as a reference.  In the event of a conflict with B between the codes in this annex and the body of this International> Standard, the codes in the body should be regarded as correct.  D Table D.1 is a numerical order listing of the additional sense codes) and the additional sense code qualifiers.O  9                      Table D.1 - ASC and ASCQ assignmentstO +=============================================================================+sO |           D - DIRECT ACCESS DEVICE                                          |cO |           .T - SEQUENTIAL ACCESS DEVICE                                     |tO |           . L - PRINTER DEVICE                                              |rO |           .  P - PROCESSOR DEVICE                                           |tO |           .  .W - WRITE ONCE READ MULTIPLE DEVICE                           | O |           .  . R - READ ONLY (CD-ROM) DEVICE                                | O |           .  .  S - SCANNER DEVICE                                          |eO |           .  .  .O - OPTICAL MEMORY DEVICE                                  |eO |           .  .  . M - MEDIA CHANGER DEVICE                                  |iO |           .  .  .  C - COMMUNICATION DEVICE                                 |,O |           .  .  .  .                                                        | O | ASC ASCQ  DTLPWRSOMC  DESCRIPTION                                           | O | --- ----              ----------------------------------------------------- |hO |  00  00   DTLPWRSOMC  NO ADDITIONAL SENSE INFORMATION                       |iO |  00  01    T          FILEMARK DETECTED                                     |oO |  00  02    T    S     END-OF-PARTITION/MEDIUM DETECTED                      |yO |  00  03    T          SETMARK DETECTED                                      |sO |  00  04    T    S     BEGINNING-OF-PARTITION/MEDIUM DETECTED                | O |  00  05    T    S     END-OF-DATA DETECTED                                  | O |  00  06   DTLPWRSOMC  I/O PROCESS TERMINATED                                |hO |  00  11   R           AUDIO PLAY OPERATION IN PROGRESS                      |lO |  00  12   R           AUDIO PLAY OPERATION PAUSED                           | O |  00  13   R           AUDIO PLAY OPERATION SUCCESSFULLY COMPLETED           | O |  00  14   R           AUDIO PLAY OPERATION STOPPED DUE TO ERROR             |hO |  00  15   R           NO CURRENT AUDIO STATUS TO RETURN                     |tO |  01  00   DW  O       NO INDEX/SECTOR SIGNAL                                |eO |  02  00   DWR OM      NO SEEK COMPLETE                                      |tO |  03  00   DTL W SO    PERIPHERAL DEVICE WRITE FAULT                         |hO |  03  01    T          NO WRITE CURRENT                                      | O |  03  02    T          EXCESSIVE WRITE ERRORS                                |nO |  04  00   DTLPWRSOMC  LOGICAL UNIT NOT READY, CAUSE NOT REPORTABLE          |sO |  04  01   DTLPWRSOMC  LOGICAL UNIT IS IN PROCESS OF BECOMING READY          |rO |  04  02   DTLPWRSOMC  LOGICAL UNIT NOT READY, INITIALIZING command REQUIRED |tO |  04  03   DTLPWRSOMC  LOGICAL UNIT NOT READY, MANUAL INTERVENTION REQUIRED  |UO |  04  04   DTL    O    LOGICAL UNIT NOT READY, FORMAT IN PROGRESS            |eO |  05  00   DTL WRSOMC  LOGICAL UNIT DOES NOT RESPOND TO SELECTION            |iO |  06  00   DWR OM  NO  REFERENCE POSITION FOUND                              |hO |  07  00   DTL WRSOM   MULTIPLE PERIPHERAL DEVICES SELECTED                  |IO |  08  00   DTL WRSOMC  LOGICAL UNIT COMMUNICATION FAILURE                    |hO |  08  01   DTL WRSOMC  LOGICAL UNIT COMMUNICATION TIME-OUT                   |EO |  08  02   DTL WRSOMC  LOGICAL UNIT COMMUNICATION PARITY ERROR               | O |  09  00   DT  WR O    TRACK FOLLOWING ERROR                                 |eO |  09  01       WR O    TRACKING SERVO FAILURE                                |tO |  09  02       WR O    FOCUS SERVO FAILURE                                   |tO |  09  03       WR O    SPINDLE SERVO FAILURE                                 | O +=============================================================================+d     Table D.1  (continued)O +=============================================================================+ O |           D - DIRECT ACCESS DEVICE                                          |iO |           .T - SEQUENTIAL ACCESS DEVICE                                     |eO |           . L - PRINTER DEVICE                                              |rO |           .  P - PROCESSOR DEVICE                                           |SO |           .  .W - WRITE ONCE READ MULTIPLE DEVICE                           | O |           .  . R - READ ONLY (CD-ROM) DEVICE                                |hO |           .  .  S - SCANNER DEVICE                                          | O |           .  .  .O - OPTICAL MEMORY DEVICE                                  | O |           .  .  . M - MEDIA CHANGER DEVICE                                  |sO |           .  .  .  C - COMMUNICATION DEVICE                                 |=O |           .  .  .  .                                                        | O | ASC ASCQ  DTLPWRSOMC  DESCRIPTION                                           | O | --- ----              ----------------------------------------------------- |-O |  0A  00   DTLPWRSOMC  ERROR LOG OVERFLOW                                    | O |  0B  00                                                                     | O |  0C  00    T     S    WRITE ERROR                                           | O |  0C  01   D   W  O    WRITE ERROR RECOVERED WITH AUTO REALLOCATION          | O |  0C  02   D   W  O    WRITE ERROR - AUTO REALLOCATION FAILED                | O |  0D  00                                                                     | O |  0E  00                                                                     |-O |  0F  00                                                                     | O |  10  00   D   W  O    ID CRC OR ECC ERROR                                   | O |  11  00   DT  WRSO    UNRECOVERED READ ERROR                                |cO |  11  01   DT  W SO    READ RETRIES EXHAUSTED                                | O |  11  02   DT  W SO    ERROR TOO LONG TO CORRECT                             |-O |  11  03   DT  W SO    MULTIPLE READ ERRORS                                  | O |  11  04   D   W  O    UNRECOVERED READ ERROR - AUTO REALLOCATE FAILED       | O |  11  05       WR O    L-EC UNCORRECTABLE ERROR                              | O |  11  06       WR O    CIRC UNRECOVERED ERROR                                | O |  11  07       W  O    DATA RESYNCHRONIZATION ERROR                          | O |  11  08    T          INCOMPLETE BLOCK READ                                 |-O |  11  09    T          NO GAP FOUND                                          | O |  11  0A   DT     O    MISCORRECTED ERROR                                    |=O |  11  0B   D   W  O    UNRECOVERED READ ERROR - RECOMMEND REASSIGNMENT       |tO |  11  0C   D   W  O    UNRECOVERED READ ERROR - RECOMMEND REWRITE THE DATA   |nO |  12  00   D   W  O    ADDRESS MARK NOT FOUND FOR ID FIELD                   | O |  13  00   D   W  O    ADDRESS MARK NOT FOUND FOR DATA FIELD                 |-O |  14  00   DTL WRSO    RECORDED ENTITY NOT FOUND                             | O |  14  01   DT  WR O    RECORD NOT FOUND                                      |eO |  14  02    T          FILEMARK OR SETMARK NOT FOUND                         | O |  14  03    T          END-OF-DATA NOT FOUND                                 |-O |  14  04    T          BLOCK SEQUENCE ERROR                                  | O |  15  00   DTL WRSOM   RANDOM POSITIONING ERROR                              | O |  15  01   DTL WRSOM   MECHANICAL POSITIONING ERROR                          |rO |  15  02   DT  WR O    POSITIONING ERROR DETECTED BY READ OF MEDIUM          |uO |  16  00   DW     O    DATA SYNCHRONIZATION MARK ERROR                       |=O |  17  00   DT  WRSO    RECOVERED DATA WITH NO ERROR CORRECTION APPLIED       |eO |  17  01   DT  WRSO    RECOVERED DATA WITH RETRIES                           | O |  17  02   DT  WR O    RECOVERED DATA WITH POSITIVE HEAD OFFSET              |rO |  17  03   DT  WR O    RECOVERED DATA WITH NEGATIVE HEAD OFFSET              |nO |  17  04       WR O    RECOVERED DATA WITH RETRIES AND/OR CIRC APPLIED       |uO |  17  05   D   WR O    RECOVERED DATA USING PREVIOUS SECTOR ID               |tO |  17  06   D   W  O    RECOVERED DATA WITHOUT ECC - DATA AUTO-REALLOCATED    |rO |  17  07   D   W  O    RECOVERED DATA WITHOUT ECC - RECOMMEND REASSIGNMENT   |oO |  17  08   D   W  O    RECOVERED DATA WITHOUT ECC - RECOMMEND REWRITE        | O |  18  00   DT  WR O    RECOVERED DATA WITH ERROR CORRECTION APPLIED          |rO |  18  01   D   WR O    RECOVERED DATA WITH ERROR CORRECTION & RETRIES APPLIED|oO |  18  02   D   WR O    RECOVERED DATA - DATA AUTO-REALLOCATED                |iO |  18  03        R      RECOVERED DATA WITH CIRC                              | O |  18  04        R      RECOVERED DATA WITH LEC                               |mO |  18  05   D   WR O    RECOVERED DATA - RECOMMEND REASSIGNMENT               | O |  18  06   D   WR O    RECOVERED DATA - RECOMMEND REWRITE                    |hO +=============================================================================+      Table D.1  (continued)O +=============================================================================+tO |           D - DIRECT ACCESS DEVICE                                          |eO |           .T - SEQUENTIAL ACCESS DEVICE                                     |aO |           . L - PRINTER DEVICE                                              | O |           .  P - PROCESSOR DEVICE                                           |oO |           .  .W - WRITE ONCE READ MULTIPLE DEVICE                           | O |           .  . R - READ ONLY (CD-ROM) DEVICE                                | O |           .  .  S - SCANNER DEVICE                                          |CO |           .  .  .O - OPTICAL MEMORY DEVICE                                  |.O |           .  .  . M - MEDIA CHANGER DEVICE                                  |oO |           .  .  .  C - COMMUNICATION DEVICE                                 |cO |           .  .  .  .                                                        |hO | ASC ASCQ  DTLPWRSOMC  DESCRIPTION                                           |AO | --- ----              ----------------------------------------------------- |=O |  19  00   D      O    DEFECT LIST ERROR                                     | O |  19  01   D      O    DEFECT LIST NOT AVAILABLE                             | O |  19  02   D      O    DEFECT LIST ERROR IN PRIMARY LIST                     | O |  19  03   D      O    DEFECT LIST ERROR IN GROWN LIST                       | O |  1A  00   DTLPWRSOMC  PARAMETER LIST LENGTH ERROR                           | O |  1B  00   DTLPWRSOMC  SYNCHRONOUS DATA TRANSFER ERROR                       | O |  1C  00   D      O    DEFECT LIST NOT FOUND                                 | O |  1C  01   D      O    PRIMARY DEFECT LIST NOT FOUND                         | O |  1C  02   D      O    GROWN DEFECT LIST NOT FOUND                           | O |  1D  00   D   W  O    MISCOMPARE DURING VERIFY OPERATION                    | O |  1E  00   D   W  O    RECOVERED ID WITH ECC                                 | O |  1F  00                                                                     | O |  20  00   DTLPWRSOMC  INVALID command OPERATION CODE                        |-O |  21  00   DT  WR OM   LOGICAL BLOCK ADDRESS OUT OF RANGE                    | O |  21  01           M   INVALID ELEMENT ADDRESS                               | O |  22  00   D           ILLEGAL FUNCTION (SHOULD USE 20 00, 24 00, OR 26 00)  | O |  23  00                                                                     | O |  24  00   DTLPWRSOMC  INVALID FIELD IN CDB                                  | O |  25  00   DTLPWRSOMC  LOGICAL UNIT NOT SUPPORTED                            | O |  26  00   DTLPWRSOMC  INVALID FIELD IN PARAMETER LIST                       | O |  26  01   DTLPWRSOMC  PARAMETER NOT SUPPORTED                               | O |  26  02   DTLPWRSOMC  PARAMETER VALUE INVALID                               | O |  26  03   DTLPWRSOMC  THRESHOLD PARAMETERS NOT SUPPORTED                    |EO |  27  00   DT  W  O    WRITE PROTECTED                                       |OO |  28  00   DTLPWRSOMC  NOT READY TO READY TRANSITION(MEDIUM MAY HAVE CHANGED)| O |  28  01           M   IMPORT OR EXPORT ELEMENT ACCESSED                     | O |  29  00   DTLPWRSOMC  POWER ON, RESET, OR BUS DEVICE RESET OCCURRED         | O |  2A  00   DTL WRSOMC  PARAMETERS CHANGED                                    | O |  2A  01   DTL WRSOMC  MODE PARAMETERS CHANGED                               | O |  2A  02   DTL WRSOMC  LOG PARAMETERS CHANGED                                | O |  2B  00   DTLPWRSO C  COPY CANNOT EXECUTE SINCE HOST CANNOT DISCONNECT      |TO |  2C  00   DTLPWRSOMC  command SEQUENCE ERROR                                |RO |  2C  01         S     TOO MANY WINDOWS SPECIFIED                            |mO |  2C  02         S     INVALID COMBINATION OF WINDOWS SPECIFIED              |TO |  2D  00    T          OVERWRITE ERROR ON UPDATE IN PLACE                    |EO |  2E  00                                                                     |IO |  2F  00   DTLPWRSOMC  commandS CLEARED BY ANOTHER INITIATOR                 | O |  30  00   DT  WR OM   INCOMPATIBLE MEDIUM INSTALLED                         | O |  30  01   DT  WR O    CANNOT READ MEDIUM - UNKNOWN FORMAT                   | O |  30  02   DT  WR O    CANNOT READ MEDIUM - INCOMPATIBLE FORMAT              | O |  30  03   DT          CLEANING CARTRIDGE INSTALLED                          | O |  31  00   DT  W  O    MEDIUM FORMAT CORRUPTED                               | O |  31  01   D L    O    FORMAT command FAILED                                 | O |  32  00   D   W  O    NO DEFECT SPARE LOCATION AVAILABLE                    | O |  32  01   D   W  O    DEFECT LIST UPDATE FAILURE                            | O |  33  00    T          TAPE LENGTH ERROR                                     |=O |  34  00                                                                     |=O |  35  00                                                                     |EO |  36  00     L         RIBBON, INK, OR TONER FAILURE                         |DO +=============================================================================+      Table D.1  (continued)O +=============================================================================+ O |           D - DIRECT ACCESS DEVICE                                          | O |           .T - SEQUENTIAL ACCESS DEVICE                                     | O |           . L - PRINTER DEVICE                                              | O |           .  P - PROCESSOR DEVICE                                           | O |           .  .W - WRITE ONCE READ MULTIPLE DEVICE                           | O |           .  . R - READ ONLY (CD-ROM) DEVICE                                | O |           .  .  S - SCANNER DEVICE                                          | O |           .  .  .O - OPTICAL MEMORY DEVICE                                  | O |           .  .  . M - MEDIA CHANGER DEVICE                                  |-O |           .  .  .  C - COMMUNICATION DEVICE                                 | O |           .  .  .  .                                                        | O | ASC ASCQ  DTLPWRSOMC  DESCRIPTION                                           | O | --- ----              ----------------------------------------------------- |AO |  37  00   DTL WRSOMC  ROUNDED PARAMETER                                     | O |  38  00                                                                     | O |  39  00   DTL WRSOMC  SAVING PARAMETERS NOT SUPPORTED                       | O |  3A  00   DTL WRSOM   MEDIUM NOT PRESENT                                    | O |  3B  00    TL         SEQUENTIAL POSITIONING ERROR                          | O |  3B  01    T          TAPE POSITION ERROR AT BEGINNING-OF-MEDIUM            | O |  3B  02    T          TAPE POSITION ERROR AT END-OF-MEDIUM                  | O |  3B  03     L         TAPE OR ELECTRONIC VERTICAL FORMS UNIT NOT READY      | O |  3B  04     L         SLEW FAILURE                                          | O |  3B  05     L         PAPER JAM                                             |EO |  3B  06     L         FAILED TO SENSE TOP-OF-FORM                           | O |  3B  07     L         FAILED TO SENSE BOTTOM-OF-FORM                        | O |  3B  08    T          REPOSITION ERROR                                      | O |  3B  09         S     READ PAST END OF MEDIUM                               | O |  3B  0A         S     READ PAST BEGINNING OF MEDIUM                         | O |  3B  0B         S     POSITION PAST END OF MEDIUM                           | O |  3B  0C         S     POSITION PAST BEGINNING OF MEDIUM                     |SO |  3B  0D           M   MEDIUM DESTINATION ELEMENT FULL                       |IO |  3B  0E           M   MEDIUM SOURCE ELEMENT EMPTY                           | O |  3C  00                                                                     | O |  3D  00   DTLPWRSOMC  INVALID BITS IN IDENTIFY MESSAGE                      | O |  3E  00   DTLPWRSOMC  LOGICAL UNIT HAS NOT SELF-CONFIGURED YET              | O |  3F  00   DTLPWRSOMC  TARGET OPERATING CONDITIONS HAVE CHANGED              | O |  3F  01   DTLPWRSOMC  MICROCODE HAS BEEN CHANGED                            | O |  3F  02   DTLPWRSOMC  CHANGED OPERATING DEFINITION                          | O |  3F  03   DTLPWRSOMC  INQUIRY DATA HAS CHANGED                              | O |  40  00   D           RAM FAILURE (SHOULD USE 40 NN)                        | O |  40  NN   DTLPWRSOMC  DIAGNOSTIC FAILURE ON COMPONENT NN (80H-FFH)          |EO |  41  00   D           DATA PATH FAILURE (SHOULD USE 40 NN)                  | O |  42  00   D           POWER-ON OR SELF-TEST FAILURE (SHOULD USE 40 NN)      | O |  43  00   DTLPWRSOMC  MESSAGE ERROR                                         | O |  44  00   DTLPWRSOMC  INTERNAL TARGET FAILURE                               |TO |  45  00   DTLPWRSOMC  SELECT OR RESELECT FAILURE                            |TO |  46  00   DTLPWRSOMC  UNSUCCESSFUL SOFT RESET                               | O |  47  00   DTLPWRSOMC  SCSI PARITY ERROR                                     | O |  48  00   DTLPWRSOMC  INITIATOR DETECTED ERROR MESSAGE RECEIVED             |RO |  49  00   DTLPWRSOMC  INVALID MESSAGE ERROR                                 |RO |  4A  00   DTLPWRSOMC  command PHASE ERROR                                   |RO |  4B  00   DTLPWRSOMC  DATA PHASE ERROR                                      |PO |  4C  00   DTLPWRSOMC  LOGICAL UNIT FAILED SELF-CONFIGURATION                |RO |  4D  00                                                                     | O |  4E  00   DTLPWRSOMC  OVERLAPPED COMMANDS ATTEMPTED                         | O |  4F  00                                                                     | O |  50  00    T          WRITE APPEND ERROR                                    | O |  50  01    T          WRITE APPEND POSITION ERROR                           | O |  50  02    T          POSITION ERROR RELATED TO TIMING                      |=O |  51  00    T     O    ERASE FAILURE                                         |=O |  52  00    T          CARTRIDGE FAULT                                       |EO +=============================================================================+D     Table D.1  (continued)O +=============================================================================+ O |           D - DIRECT ACCESS DEVICE                                          | O |           .T - SEQUENTIAL ACCESS DEVICE                                     | O |           . L - PRINTER DEVICE                                              | O |           .  P - PROCESSOR DEVICE                                           | O |           .  .W - WRITE ONCE READ MULTIPLE DEVICE                           | O |           .  . R - READ ONLY (CD-ROM) DEVICE                                | O |           .  .  S - SCANNER DEVICE                                          | O |           .  .  .O - OPTICAL MEMORY DEVICE                                  | O |           .  .  . M - MEDIA CHANGER DEVICE                                  | O |           .  .  .  C - COMMUNICATION DEVICE                                 |-O |           .  .  .  .                                                        | O | ASC ASCQ  DTLPWRSOMC  DESCRIPTION                                           | O | --- ----              ----------------------------------------------------- | O |  53  00   DTL WRSOM   MEDIA LOAD OR EJECT FAILED                            | O |  53  01    T          UNLOAD TAPE FAILURE                                   | O |  53  02   DT  WR OM   MEDIUM REMOVAL PREVENTED                              | O |  54  00      P        SCSI TO HOST SYSTEM INTERFACE FAILURE                 | O |  55  00      P        SYSTEM RESOURCE FAILURE                               | O |  56  00                                                                     | O |  57  00        R      UNABLE TO RECOVER TABLE-OF-CONTENTS                   | O |  58  00     O         GENERATION DOES NOT EXIST                             | O |  59  00     O         UPDATED BLOCK READ                                    | O |  5A  00   DTLPWRSOM   OPERATOR REQUEST OR STATE CHANGE INPUT (UNSPECIFIED)  | O |  5A  01   DT  WR OM   OPERATOR MEDIUM REMOVAL REQUEST                       | O |  5A  02   DT  W  O    OPERATOR SELECTED WRITE PROTECT                       | O |  5A  03   DT  W  O    OPERATOR SELECTED WRITE PERMIT                        |0O |  5B  00   DTLPWRSOM   LOG EXCEPTION                                         | O |  5B  01   DTLPWRSOM   THRESHOLD CONDITION MET                               | O |  5B  02   DTLPWRSOM   LOG COUNTER AT MAXIMUM                                | O |  5B  03   DTLPWRSOM   LOG LIST CODES EXHAUSTED                              | O |  5C  00   D   O       RPL STATUS CHANGE                                     | O |  5C  01   D   O       SPINDLES SYNCHRONIZED                                 | O |  5C  02   D   O       SPINDLES NOT SYNCHRONIZED                             | O |  5D  00                                                                     | O |  5E  00                                                                     |YO |  5F  00                                                                     | O |  60  00         S     LAMP FAILURE                                          |CO |  61  00         S     VIDEO ACQUISITION ERROR                               | O |  61  01         S     UNABLE TO ACQUIRE VIDEO                               | O |  61  02         S     OUT OF FOCUS                                          | O |  62  00         S     SCAN HEAD POSITIONING ERROR                           |IO |  63  00        R      END OF USER AREA ENCOUNTERED ON THIS TRACK            | O |  64  00        R      ILLEGAL MODE FOR THIS TRACK                           | O |  65  00                                                                     |DO |  66  00                                                                     | O |  67  00                                                                     | O |  68  00                                                                     | O |  69  00                                                                     | O |  6A  00                                                                     | O |  6B  00                                                                     |TO |  6C  00                                                                     | O |  6D  00                                                                     | O |  6E  00                                                                     | O |  6F  00                                                                     | O +=============================================================================+      Table D.1  (concluded)O +=============================================================================+ O |           D - DIRECT ACCESS DEVICE                                          | O |           .T - SEQUENTIAL ACCESS DEVICE                                     | O |           . L - PRINTER DEVICE                                              |=O |           .  P - PROCESSOR DEVICE                                           | O |           .  .W - WRITE ONCE READ MULTIPLE DEVICE                           |=O |           .  . R - READ ONLY (CD-ROM) DEVICE                                | O |           .  .  S - SCANNER DEVICE                                          | O |           .  .  .O - OPTICAL MEMORY DEVICE                                  | O |           .  .  . M - MEDIA CHANGER DEVICE                                  | O |           .  .  .  C - COMMUNICATION DEVICE                                 | O |           .  .  .  .                                                        | O | ASC ASCQ  DTLPWRSOMC  DESCRIPTION                                           | O | --- ----              ----------------------------------------------------- | O |  70  00                                                                     | O |  71  00                                                                     | O |  72  00                                                                     | O |  73  00                                                                     | O |  74  00                                                                     |-O |  75  00                                                                     | O |  76  00                                                                     | O |  77  00                                                                     | O |  78  00                                                                     | O |  79  00                                                                     | O |  7A  00                                                                     |IO |  7B  00                                                                     | O |  7C  00                                                                     |NO |  7D  00                                                                     | O |  7E  00                                                                     | O |  7F  00                                                                     | O |                                                                             | O |  80  xxh \                                                                  | O |   THROUGH >  Vendor-specific.                                               | O |  FF  xxh /                                                                  | O |                                                                             | O |  xxh 80 \                                                                   | O |  THROUGH >  Vendor-specific QUALIFICATION OF STANDARD ASC.                  | O |  xxh FF /                                                                   | O |               ALL CODES NOT SHOWN OR BLANK ARE RESERVED.                    | O +=============================================================================+       F Table D.2 is a numerical order listing of the command operation codes.  8                       Table D.2 - SCSI-2 Operation CodesO +=============================================================================+ O |           D - DIRECT ACCESS DEVICE                       Device column key  |TO |           .T - SEQUENTIAL ACCESS DEVICE                  M = Mandatory      |HO |           . L - PRINTER DEVICE                           O = Optional       |SO |           .  P - PROCESSOR DEVICE                        V = Vendor-specific|IO |           .  .W - WRITE ONCE READ MULTIPLE DEVICE        R = Reserved       |LO |           .  . R - READ ONLY (CD-ROM) DEVICE                                |EO |           .  .  S - SCANNER DEVICE                                          | O |           .  .  .O - OPTICAL MEMORY DEVICE                                  |EO |           .  .  . M - MEDIA CHANGER DEVICE                                  |EO |           .  .  .  C - COMMUNICATION DEVICE                                 |SO |           .  .  .  .                                                        |RO |        OP DTLPWRSOMC Description                                            |EO |----------+----------+-------------------------------------------------------|GO |        00 MMMMMMMMMM TEST UNIT READY                                        | O |        01  M         REWIND                                                 |RO |        01 O V OO OO  REZERO UNIT                                            |FO |        02 VVVVVV  V                                                         | O |        03 MMMMMMMMMM REQUEST SENSE                                          |MO |        04   O        FORMAT                                                 | O |        04 M      O   FORMAT UNIT                                            |EO |        05 VMVVVV  V  READ BLOCK LIMITS                                      |PO |        06 VVVVVV  V                                                         |RO |        07         O  INITIALIZE ELEMENT STATUS                              | O |        07 OVV O  OV  REASSIGN BLOCKS                                        |LO |        08          M GET MESSAGE(06)                                        |=O |        08 OMV OO OV  READ(06)                                               |=O |        08    O       RECEIVE                                                | O |        09 VVVVVV  V                                                         | O |        0A   M        PRINT                                                  | O |        0A          M SEND MESSAGE(06)                                       | O |        0A    M       SEND(06)                                               | O |        0A OM  O  OV  WRITE(06)                                              | O |        0B O   OO OV  SEEK(06)                                               | O |        0B   O        SLEW AND PRINT                                         | O |        0C VVVVVV  V                                                         | O |        0D VVVVVV  V                                                         | O |        0E VVVVVV  V                                                         | O |        0F VOVVVV  V  READ REVERSE                                           |QO |        10   O O      SYNCHRONIZE BUFFER                                     |-O |        10 VM VVV     WRITE FILEMARKS                                        | O |        11 VMVVVV     SPACE                                                  | O |        12 MMMMMMMMMM INQUIRY                                                | O |        13 VOVVVV     VERIFY(06)                                             | O |        14 VOOVVV     RECOVER BUFFERED DATA                                  | O |        15 OMO OOOOOO MODE SELECT(06)                                        | O |        16 M   MM MO  RESERVE                                                | O |        16  MM   M    RESERVE UNIT                                           | O |        17 M   MM MO  RELEASE                                                | O |        17  MM   M    RELEASE UNIT                                           | O |        18 OOOOOOOO   COPY                                                   | O |        19 VMVVVV     ERASE                                                  | O |        1A OMO OOOOOO MODE SENSE(06)                                         | O |        1B  O         LOAD UNLOAD                                            | O |        1B       O    SCAN                                                   | O |        1B   O        STOP PRINT                                             | O |        1B O   OO O   STOP START UNIT                                        | O +=============================================================================+      Table D.2 (continued)AO +=============================================================================+HO |           D - DIRECT ACCESS DEVICE                       Device column key  |SO |           .T - SEQUENTIAL ACCESS DEVICE                  M = Mandatory      | O |           . L - PRINTER DEVICE                           O = Optional       | O |           .  P - PROCESSOR DEVICE                        V = Vendor-specific| O |           .  .W - WRITE ONCE READ MULTIPLE DEVICE        R = Reserved       | O |           .  . R - READ ONLY (CD-ROM) DEVICE                                |TO |           .  .  S - SCANNER DEVICE                                          |UO |           .  .  .O - OPTICAL MEMORY DEVICE                                  | O |           .  .  . M - MEDIA CHANGER DEVICE                                  |IO |           .  .  .  C - COMMUNICATION DEVICE                                 |RO |           .  .  .  .                                                        |FO |        OP DTLPWRSOMC Description                                            | O |----------+----------+-------------------------------------------------------| O |        1C OOOOOOOOOO RECEIVE DIAGNOSTIC RESULTS                             | O |        1D MMMMMMMMMM SEND DIAGNOSTIC                                        | O |        1E OO  OO OO  PREVENT ALLOW MEDIUM REMOVAL                           | O |        1F                                                                   | O |        20 V   VV V                                                          | O |        21 V   VV V                                                          | O |        22 V   VV V                                                          | O |        23 V   VV V                                                          | O |        24 V   VVM    SET WINDOW                                             | O |        25       O    GET WINDOW                                             |=O |        25 M   M  M   READ CAPACITY                                          |=O |        25      M     READ CD-ROM CAPACITY                                   | O |        26 V   VV                                                            | O |        27 V   VV                                                            | O |        28          O GET MESSAGE(10)                                        | O |        28 M   MMMM   READ(10)                                               | O |        29 V   VV O   READ GENERATION                                        | O |        2A          O SEND MESSAGE(10)                                       | O |        2A       O    SEND(10)                                               | O |        2A O   M  M   WRITE(10)                                              | O |        2B  O         LOCATE                                                 | O |        2B         O  POSITION TO ELEMENT                                    | O |        2B O   OO O   SEEK(10)                                               |QO |        2C V      O   ERASE(10)                                              |-O |        2D V   O  O   READ UPDATED BLOCK                                     | O |        2E O   O  O   WRITE AND VERIFY(10)                                   | O |        2F O   OO O   VERIFY(10)                                             | O |        30 O   OO O   SEARCH DATA HIGH(10)                                   | O |        31       O    OBJECT POSITION                                        | O |        31 O   OO O   SEARCH DATA EQUAL(10)                                  | O |        32 O   OO O   SEARCH DATA LOW(10)                                    | O |        33 O   OO O   SET LIMITS(10)                                         | O |        34       O    GET DATA BUFFER STATUS                                 | O |        34 O   OO O   PRE-FETCH                                              | O |        34  O         READ POSITION                                          | O |        35 O   OO O   SYNCHRONIZE CACHE                                      | O |        36 O   OO O   LOCK UNLOCK CACHE                                      | O |        37 O      O   READ DEFECT DATA(10)                                   | O |        38     O  O   MEDIUM SCAN                                            | O |        39 OOOOOOOO   COMPARE                                                | O |        3A OOOOOOOO   COPY AND VERIFY                                        | O |        3B OOOOOOOOOO WRITE BUFFER                                           |hO |        3C OOOOOOOOOO READ BUFFER                                            |GO |        3D     O  O   UPDATE BLOCK                                           |hO |        3E O   OO O   READ LONG                                              | O |        3F O   O  O   WRITE LONG                                             | O +=============================================================================+H     Table D.2 (continued)CO +=============================================================================+ O |           D - DIRECT ACCESS DEVICE                       Device column key  |RO |           .T - SEQUENTIAL ACCESS DEVICE                  M = Mandatory      |=O |           . L - PRINTER DEVICE                           O = Optional       |lO |           .  P - PROCESSOR DEVICE                        V = Vendor-specific|2O |           .  .W - WRITE ONCE READ MULTIPLE DEVICE        R = Reserved       |=O |           .  . R - READ ONLY (CD-ROM) DEVICE                                |cO |           .  .  S - SCANNER DEVICE                                          |MO |           .  .  .O - OPTICAL MEMORY DEVICE                                  |OO |           .  .  . M - MEDIA CHANGER DEVICE                                  |VO |           .  .  .  C - COMMUNICATION DEVICE                                 |RO |           .  .  .  .                                                        | O |        OP DTLPWRSOMC Description                                            | O |----------+----------+-------------------------------------------------------| O |        40 OOOOOOOOOO CHANGE DEFINITION                                      | O |        41 O          WRITE SAME                                             | O |        42      O     READ SUB-CHANNEL                                       | O |        43      O     READ TOC                                               | O |        44      O     READ HEADER                                            |-O |        45      O     PLAY AUDIO(10)                                         | O |        46                                                                   | O |        47      O     PLAY AUDIO MSF                                         | O |        48      O     PLAY AUDIO TRACK INDEX                                 | O |        49      O     PLAY TRACK RELATIVE(10)                                | O |        4A                                                                   | O |        4B      O     PAUSE RESUME                                           | O |        4C OOOOOOOOOO LOG SELECT                                             | O |        4D OOOOOOOOOO LOG SENSE                                              | O |        4E                                                                   | O |        4F                                                                   | O |        50                                                                   | O |        51                                                                   | O |        52                                                                   | O |        53                                                                   | O |        54                                                                   | O |        55 OOO OOOOOO MODE SELECT(10)                                        | O |        56                                                                   | O |        57                                                                   | O |        58                                                                   | O |        59                                                                   | O |        5A OOO OOOOOO MODE SENSE(10)                                         | O |        5B                                                                   | O |        5C                                                                   | O |        5D                                                                   | O |        5E                                                                   | O |        5F                                                                   | O +=============================================================================+      Table D.2 (concluded)1O +=============================================================================+1O |           D - DIRECT ACCESS DEVICE                       Device column key  |1O |           .T - SEQUENTIAL ACCESS DEVICE                  M = Mandatory      |1O |           . L - PRINTER DEVICE                           O = Optional       |1O |           .  P - PROCESSOR DEVICE                        V = Vendor-specific|1O |           .  .W - WRITE ONCE READ MULTIPLE DEVICE        R = Reserved       |1O |           .  . R - READ ONLY (CD-ROM) DEVICE                                |1O |           .  .  S - SCANNER DEVICE                                          |1O |           .  .  .O - OPTICAL MEMORY DEVICE                                  |1O |           .  .  . M - MEDIA CHANGER DEVICE                                  |1O |           .  .  .  C - COMMUNICATION DEVICE                                 |1O |           .  .  .  .                                                        |1O |        OP DTLPWRSOMC Description                                            |1O |----------+----------+-------------------------------------------------------|1O |        A0                                                                   |=O |        A1                                                                   | O |        A2                                                                   |=O |        A3                                                                   |cO |        A4                                                                   |MO |        A5         M  MOVE MEDIUM                                            |OO |        A5      O     PLAY AUDIO(12)                                         |VO |        A6         O  EXCHANGE MEDIUM                                        |RO |        A7                                                                   | O |        A8          O GET MESSAGE(12)                                        | O |        A8     OO O   READ(12)                                               | O |        A9      O     PLAY TRACK RELATIVE(12)                                | O |        AA          O SEND MESSAGE(12)                                       | O |        AA     O  O   WRITE(12)                                              | O |        AB                                                                   | O |        AC        O   ERASE(12)                                              |-O |        AD                                                                   | O |        AE     O  O   WRITE AND VERIFY(12)                                   | O |        AF     OO O   VERIFY(12)                                             | O |        B0     OO O   SEARCH DATA HIGH(12)                                   | O |        B1     OO O   SEARCH DATA EQUAL(12)                                  | O |        B2     OO O   SEARCH DATA LOW(12)                                    | O |        B3     OO O   SET LIMITS(12)                                         | O |        B4                                                                   | O |        B5                                                                   | O |        B5         O  REQUEST VOLUME ELEMENT ADDRESS                         | O |        B6                                                                   | O |        B6         O  SEND VOLUME TAG                                        | O |        B7        O   READ DEFECT DATA(12)                                   | O |        B8                                                                   | O |        B8         O  READ ELEMENT STATUS                                    | O |        B9                                                                   | O |        BA                                                                   | O |        BB                                                                   | O |        BC                                                                   | O |        BD                                                                   | O |        BE                                                                   | O |        BF                                                                   | O +=============================================================================+     H                                                                                                             Annex ER
 (informative)C   Vendor identification     B This annex contains the list of SCSI-2 vendor identifications (seeE table E.1) as of the date of this document.  The purpose of this list G is to help avoid redundant usage of vendor identifications.  Task GroupGF X3T9.2 of Accredited Standards Committee X3 maintains an informal list? of vendor identifications currently in use.  Please contact the F chairman of X3T9.2 prior to using a new vendor identification to avoid
 conflicts.  :                     Table E.1 - Vendor identification listR +==========-=====================================================================+R |     ID   |                          Organization                               |R |----------+---------------------------------------------------------------------|R | 3M       |  3M Company                                                         |R | ACL      |  Automated Cartridge Librarys, Inc.                                 |R | ADAPTEC  |  Adaptec                                                            |R | ADSI     |  Adaptive Data Systems, Inc. (a Western Digital subsidiary)         |R | AMCODYNE |  Amcodyne                                                           |R | ANAMATIC |  Anamartic Limited (England)                                        |R | ANCOT    |  ANCOT Corp.                                                        |R | ANRITSU  |  Anritsu Corporation                                                |R | APPLE    |  Apple Computer, Inc.                                               |R | ARCHIVE  |  Archive                                                            |R | ASACA    |  ASACA Corporation                                                  |R | ASPEN    |  Aspen Peripherals                                                  |R | AST      |  AST Research                                                       |R | ASTK     |  Alcatel STK A/S                                                    |R | AT&T     |  AT&T                                                               |R | ATARI    |  Atari Corporation                                                  |R | ATTO     |  ATTO Technology Inc.                                               |R | ATX      |  Alphatronix                                                        |R | AVR      |  Advanced Vision Research                                           |R | BALLARD  |  Ballard Synergy Corp.                                              |R | BERGSWD  |  Berg Software Design                                               |R | BEZIER   |  Bezier Systems, Inc.                                               |R | BULL     |  Bull Peripherals Corp.                                             |R | CalComp  |  CalComp, A Lockheed Company                                        |R | CALIPER  |  Caliper (California Peripheral Corp.)                              |R | CAST     |  Advanced Storage Tech                                              |R | CDC      |  Control Data or MPI                                                |R | CDP      |  Columbia Data Products                                             |R | CHEROKEE |  Cherokee Data Systems                                              |R | CHINON   |  Chinon                                                             |R | CIE&YED  |  YE Data, C.Itoh Electric Corp.                                     |R | CIPHER   |  Cipher Data Products                                               |R +================================================================================+     Table E.1 - (continued) R +==========-=====================================================================+R |   ID     |                          Organization                               |R |----------+---------------------------------------------------------------------|R | Ciprico  |  Ciprico, Inc.                                                      |R | CMD      |  CMD Technology                                                     |R | CNGR SFW |  Congruent Software, Inc.                                           |R | COGITO   |  Cogito                                                             |R | COMPORT  |  Comport Corp.                                                      |R | COMPSIG  |  Computer Signal Corporation                                        |R | CONNER   |  Conner Peripherals                                                 |R | CPU TECH |  CPU Technology, Inc                                                |R | CREO     |  CREO Products Inc.                                                 |R | CROSFLD  |  Crosfield Electronics                                              |R | CSM, INC |  Computer SM, Inc.                                                  |R | CYGNET   |  Cygnet Systems, Inc.                                               |R | DATABOOK |  Databook, Inc.                                                     |R | DATACOPY |  Datacopy Corp.                                                     |R | DATAPT   |  Datapoint Corp.                                                    |R | DEC      |  Digital Equipment                                                  |R | DELPHI   |  Delphi Data Div. of Sparks Industries, Inc.                        |R | DENON    |  Denon/Nippon Columbia                                              |R | DEST     |  DEST Corp.                                                         |R | DGC      |  Data General Corp.                                                 |R | DIGIDATA |  Digi-Data Corporation                                              |R | DILOG    |  Distributed Logic Corp.                                            |R | DISC     |  Document Imaging Systems Corp.                                     |R | DPT      |  Distributed Processing Technology                                  |R | DSM      |  Deterner Steuerungs- und Maschinenbau GmbH & Co.                   |R | DTC QUME |  Data Technology Qume                                               |R | DXIMAGIN |  DX Imaging                                                         |R | EMULEX   |  Emulex                                                             |R | EPSON    |  Epson                                                              |R | EXABYTE  |  Exabyte Corp.                                                      |R | FILENET  |  FileNet Corp.                                                      |R | FUJI     |  Fuji Electric Co., Ltd. (Japan)                                    |R | FUJITSU  |  Fujitsu                                                            |R | FUTURED  |  Future Domain Corp.                                                |R | Gen_Dyn  |  General Dynamics                                                   |R | GIGATAPE |  GIGATAPE GmbH                                                      |R | GIGATRND |  GigaTrend Incorporated                                             |R | Goidelic |  Goidelic Precision, Inc.                                           |R | GOULD    |  Gould                                                              |R | HITACHI  |  Hitachi America Ltd or Nissei Sangyo America Ltd                   |R | HONEYWEL |  Honeywell Inc.                                                     |R | HP       |  Hewlett Packard                                                    |R | IBM      |  International Business Machines                                    |R | ICL      |  ICL                                                                |R | IDE      |  International Data Engineering, Inc.                               |R | IGR      |  Intergraph Corp.                                                   |R | IMPLTD   |  Integrated Micro Products Ltd.                                     |R | IMPRIMIS |  Imprimis Technology Inc.                                           |R | INSITE   |  Insite Peripherals                                                 |R | IOC      |  I/O Concepts, Inc.                                                 |R | IOMEGA   |  Iomega                                                             |R +================================================================================+       Table E.1 - (continued) R +==========-=====================================================================+R |   ID     |                          Organization                               |R |----------+---------------------------------------------------------------------|R | ISi      |  Information Storage inc.                                           |R | ITC      |  International Tapetronics Corporation                              |R | JVC      |  JVC Information Products Co.                                       |R | KENNEDY  |  Kennedy Company                                                    |R | KODAK    |  Eastman Kodak                                                      |R | KONAN    |  Konan                                                              |R | KONICA   |  Konica Japan                                                       |R | LAPINE   |  Lapine Technology                                                  |R | LASERDRV |  LaserDrive Limited                                                 |R | LASERGR  |  Lasergraphics, Inc.                                                |R | LMS      |  Laser Magnetic Storage International Company                       |R | MATSHITA |  Matsushita                                                         |R | MAXTOR   |  Maxtor Corp.                                                       |R | MaxOptix |  Maxoptix Corp.                                                     |R | MDI      |  Micro Design International, Inc.                                   |R | MELA     |  Mitsubishi Electronics America                                     |R | MELCO    |  Mitsubishi Electric (Japan)                                        |R | MEMREL   |  Memrel Corporation                                                 |R | MEMTECH  |  MemTech Technology                                                 |R | MICROBTX |  Microbotics Inc.                                                   |R | MICROP   |  Micropolis                                                         |R | MICROTEK |  Microtek Storage Corp                                              |R | MINSCRIB |  Miniscribe                                                         |R | MITSUMI  |  MITSUMI Electric Co., Ltd.                                         |R | MOTOROLA |  Motorola                                                           |R | MST      |  Morning Star Technologies, Inc.                                    |R | NAI      |  North Atlantic Industries                                          |R | NatInst  |  National Instruments                                               |R | NatSemi  |  National Semiconductor Corp.                                       |R | NCL      |  NCL America                                                        |R | NCR      |  NCR Corporation                                                    |R | NEC      |  NEC                                                                |R | NISCA    |  NISCA Inc.                                                         |R | NKK      |  NKK Corp.                                                          |R | NT       |  Northern Telecom                                                   |R | OCE      |  Oce Graphics                                                       |R | OMI      |  Optical Media International                                        |R | OMNIS    |  OMNIS Company (FRANCE)                                             |R | OPTIMEM  |  Cipher/Optimem                                                     |R | OPTOTECH |  Optotech                                                           |R | ORCA     |  Orca Technology                                                    |R | OSI      |  Optical Storage International                                      |R | OTL      |  OTL Engineering                                                    |R | PASCOsci |  Pasco Scientific                                                   |R | PERTEC   |  Pertec Peripherals Corporation                                     |R | PFTI     |  Performance Technology Inc.                                        |R | PIONEER  |  Pioneer Electronic Corp.                                           |R | PRAIRIE  |  PrairieTek                                                         |R | PRESOFT  |  PreSoft Architects                                                 |R | PRESTON  |  Preston Scientific                                                 |R | PRIAM    |  Priam                                                              |R | PRIMAGFX |  Primagraphics Ltd                                                  |R +================================================================================+     Table E.1 - (concluded) R +==========-=====================================================================+R |   ID     |                          Organization                               |R |----------+---------------------------------------------------------------------|R | PTI      |  Peripheral Technology Inc.                                         |R | QUALSTAR |  Qualstar                                                           |R | QUANTEL  |  Quantel Ltd.                                                       |R | QUANTUM  |  Quantum Corp.                                                      |R | R-BYTE   |  R-Byte Inc.                                                        |R | RACALREC |  Racal Recorders                                                    |R | RADSTONE |  Radstone Technology                                                |R | RGI      |  Raster Graphics, Inc.                                              |R | RICOH    |  Ricoh                                                              |R | RODIME   |  Rodime                                                             |R | RTI      |  Reference Technology                                               |R | SANKYO   |  Sankyo Seiki                                                       |R | SANYO    |  SANYO Electric Co., Ltd.                                           |R | SCREEN   |  Dainippon Screen Mfg. Co., Ltd.                                    |R | SEAGATE  |  Seagate                                                            |R | SEQUOIA  |  Sequoia Advanced Technologies, Inc.                                |R | Shinko   |  Shinko Electric Co., Ltd.                                          |R | SIEMENS  |  Siemens                                                            |R | SII      |  Seiko Instruments Inc.                                             |R | SMS      |  Scientific Micro Systems/OMTI                                      |R | SNYSIDE  |  Sunnyside Computing Inc.                                           |R | SONIC    |  Sonic Solutions                                                    |R | SONY     |  Sony Corporation Japan                                             |R | SPECTRA  |  Spectra Logic, a Division of Western Automation Labs, Inc.         |R | SPERRY   |  Sperry (now Unisys Corp.)                                          |R | STK      |  Storage Technology Corporation                                     |R | SUMITOMO |  Sumitomo Electric Industries, Ltd.                                 |R | SUN      |  Sun Microsystems, Inc.                                             |R | SyQuest  |  SyQuest Technology, Inc.                                           |R | SYSGEN   |  Sysgen                                                             |R | T-MITTON |  Transmitton England                                                |R | TALARIS  |  Talaris Systems, Inc.                                              |R | TALLGRAS |  Tallgrass Technologies                                             |R | TANDBERG |  Tandberg Data A/S                                                  |R | TANDON   |  Tandon                                                             |R | TEAC     |  TEAC Japan                                                         |R | TECOLOTE |  Techolote Designs                                                  |R | TEGRA    |  Tegra Varityper                                                    |R | Tek      |  Tektronix                                                          |R | TI-DSG   |  Texas Instruments                                                  |R | TOSHIBA  |  Toshiba Japan                                                      |R | ULTRA    |  UltraStor Corporation                                              |R | UNISYS   |  Unisys                                                             |R | USDC     |  US Design Corp.                                                    |R | VERBATIM |  Verbatim Corporation                                               |R | VRC      |  Vermont Research Corp.                                             |R | WangDAT  |  WangDAT                                                            |R | WANGTEK  |  Wangtek                                                            |R | WDIGTL   |  Western Digital                                                    |R | WEARNES  |  Wearnes Technology Corporation                                     |R | XEBEC    |  Xebec Corporation                                                  |R +================================================================================+           Index   O 3rdPty bit. . . . . . . . . . . . . . . . . . . . . 188, 191, 253, 254, 398-401 O ABORT . . . . 3, 36, 38, 41, 43, 44, 49, 52, 55-59, 64, 76, 79, 80, 82, 85, 422 O ABORT TAG . . . . . . . . . . . . . . . . 3, 41, 52, 55, 56, 58, 64, 76, 79, 85|O absolute CD-ROM address field . . . . . . . . . . . . . . . . . . . . .319, 324 O access bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394-396 O active format field . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267 O active I/O process. . . . . . . . . . . . . . . . . . . . . . . . . . 3, 51, 54 O active notch field. . . . . . . . . . . . . . . . . . . . . . . . 210, 218, 221 O active partition field. . . . . . . . . . . . . . . . . . . . . . . . .266, 267 O actual retry count field. . . . . . . . . . . . . . . . . . . . . . . . . . 126=O additional length field . . . . . . . . . . . . . . . . . . . . . . . . . . 107=O additional partitions defined field . . . . . . . . . . . . . . . . . . . . 269 O additional sense code field . . . . . . . . . . . . . . . . . . . 123, 124, 392-O additional sense code qualifier . . . . . . . . . . . . .123, 124, 302, 392-395tO ADDRESS MARK NOT FOUND FOR DATA FIELD . . . . . . . . . . . . . . . . .130, 430aO ADDRESS MARK NOT FOUND FOR ID FIELD . . . . . . . . . . . . . . . . . .130, 430mO address to translate field. . . . . . . . . . . . . . . . . . . . . . . 206-208 O ADR field . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302, 318, 324aO advanced scan algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . 362aO AEN . . . . . . . . . . . . . . .xxv, 5, 81-83, 89, 95, 126, 127, 150, 151, 290oO AENC bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82, 107 O AFC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .282, 283|P Allocation Length . . 67, 72, 73, 75, 95, 104, 107, 111, 112, 115, 117-119, 121,Q                       122, 124, 155-159, 183, 185, 289, 314, 316, 323, 341, 343,  A                       364, 366, 388, 389, 391, 396, 397, 414, 415 O allocation length field . . . . . . . . . . . . . . . . . . . . . . . . 75, 111 O alternate sector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 O alternate sectors per zone field. . . . . . . . . . . . . . . . . . . . . . 218 O alternate track . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 O alternate tracks per logical unit field . . . . . . . . . . . . . . . . . . 218 O alternate tracks per zone . . . . . . . . . . . . . . . . . . . . . . . 216-218 O alternate volume tag. . . . . . . . . . . . . . . . . . . . . 382, 391-395, 402 O alternate volume tag information field. . . . . . . . . . . . . . . . . . . 391 O ALTSEC bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 O ALTTRK bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 O ANSI-approved version field . . . . . . . . . . . . . . . . . . . . . . . . 106 O APRVal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .327, 328 O Arbitration Delay . . . . . . . . . . . . . . . . . . . . .3, xxxi, 36, 42, 421 O ARBITRATION Phase . . . . . . . . . . . . . .33, 34, 36, 37, 41-43, 59, 86, 421 O ARRE bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 O ASA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362 O ASC . . . . . . . . . . . . . . 1, xxii, xxvii, 106, 124, 130-133, 135, 429-434 O ASCII forms control . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.O ASCII Implemented Operating Definition Page . . . . . . . . . . . . . . . . 155 O ASCII information field . . . . . . . . . . . . . . . . . . . . . . . . . . 156 O ASCII operating definition description data field . . . . . . . . . . . . . 155 O ASCQ. . . . . . . . . . . . . . . . . . xxii, xxvii, 124, 130-133, 135, 429-434 O Assertion Period. . . . . . . . . . . . . . . . . . . . . . 36, 38, 45, 46, 425 O asynchronous event notification . . xxxi, 5, 27, 56, 61, 81-83, 107, 126, 145, m;                                     149, 151, 238, 241, 290 O attention condition . . . . . . . . 33, 48-51, 56, 59, 63, 79, 81, 82, 85, 88,  N                                     89, 94, 95, 104, 110, 112, 128, 138, 142, E                                     148, 150, 151, 188, 230, 253, 264 O AUDIO PLAY OPERATION IN PROGRESS. . . . . . . . . . . . . . . . . 130, 318, 429 O AUDIO PLAY OPERATION PAUSED . . . . . . . . . . . . . . . . . . . 130, 318, 429 O AUDIO PLAY OPERATION STOPPED DUE TO ERROR . . . . . . . . . . . . 130, 318, 429 O AUDIO PLAY OPERATION SUCCESSFULLY COMPLETED . . . . . . . . . . . 130, 318, 429 O audio playback rate valid . . . . . . . . . . . . . . . . . . . . . . . . . 328 O audio status field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317 O auto bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .339, 345 O autofd. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280, 282 O automatic line feed . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 O automatic read reallocation . . . . . . . . . . . . . . . . . . . . . . . . 223 O automatic velocity control. . . . . . . . . . . . . . . . . . . . . . . . . 267 O automatic write reallocation. . . . . . . . . . . . . . . . . . . . . . . . 222 O available data buffer field . . . . . . . . . . . . . . . . . . . . . . . . 342 O AVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .266, 267 O AVolTag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391-393=O AWG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5, 9, 425-O AWRE bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203, 223, 231 O basic measurement unit field. . . . . . . . . . . . . . . . . . . . . . . . 354-O baud rate field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286 O beginning of partition. . . . . . . . . . . . . . . . . . . . . . . . . . . 250UO BEGINNING-OF-PARTITION/MEDIUM DETECTED. . . . . . . . . . . . . . . . .130, 429 O BIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . .249, 266, 267, 363 O bit ordering field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346|O bit pointer field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 O bit pointer valid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 O bits per character field. . . . . . . . . . . . . . . . . . . . . . . . . . 286 O bits per pixel field. . . . . . . . . . . . . . . . . . . . . . . . . . . . 346 O BLANK CHECK . . . . .102, 129, 247, 257, 294, 304, 307, 326, 358, 367, 370, 376 O blank verify. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .299, 370 O BlkVfy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299, 370, 371 O block address type. . . . . . . . . . . . . . . . . . . . . . . . . . .245, 249 L block descriptor. .  xxii, 113, 115, 116, 124, 146-148, 161, 208, 209, 246, L                      259, 263, 264, 279, 280, 298, 325, 326, 337, 349, 351, ,                      353, 375, 376, 404, 418O block descriptor length . . . . . . . . . . . . . . . . . . . . . . . . . . 147 O block device logical block address field. . . . . . . . . . . . . . . . . . .99|O block device number of blocks field . . . . . . . . . . . . . . . . . . . . .99 O block identifiers supported . . . . . . . . . . . . . . . . . . . . . . . . 267 O block length field. . . . . . . . . . . . . . . . . . . . . .101, 124, 148, 246 O block length in bytes . . . . . . . . . . . . . . . . . . . .182, 183, 246, 259NO block position unknown. . . . . . . . . . . . . . . . . . . . . . . . . . . 250 O BLOCK SEQUENCE ERROR. . . . . . . . . . . . . . . . . . . . . . . . . .130, 430 O BOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236-240, 249, 250|O BPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .249, 250 O BPV bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 O brightness field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345 O BT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245, 249 O buffer capacity field . . . . . . . . . . . . . . . . . . . . . . 119, 120, 137 O buffer empty ratio field. . . . . . . . . . . . . . . . . . . . . . . . . . 152 O buffer full ratio field . . . . . . . . . . . . . . . . . . . . . . . . . . 152 O buffer ID field . . . . . . . . . . . . . . . . . . . . . . . . . . . .119, 137 O buffer offset field . . . . . . . . . . . . . . . . . . . . . . . . . .119, 120 O Buffer Over-Run/Under-Run Page. . . 143, 208, 262, 279, 291, 325, 352, 375, 418 O buffered mode field . . . . . . . . . . . . . . . . . . . . . . . 259, 263, 280 O Bus Clear Delay . . . . . . . . . . . . . . . . . . . . 36, 41-43, 51, 421, 423 N BUS DEVICE RESET. . . . . . .3, 41, 49, 50, 55, 57-59, 65, 67-69, 76, 79, 82, K                              83, 85, 88, 112, 116, 132, 179, 189-191, 254,  )                              399-401, 431 O Bus Free Delay. . . . . . . . . . . . . . . . . . . . . . . . . 36, 37, 42, 421 M BUS FREE Phase. . 3, 4, 36, 37, 41-44, 49-52, 57-60, 64, 66, 68, 69, 77, 84,                     86, 421, 423O Bus Set Delay . . . . . . . . . . . . . . . . . . . . . . . . . 36, 37, 42, 421 O Bus Settle Delay. . . . . . . . . . . . . . . . . . .36, 37, 41-44, 49, 421-423rO BUSY status . . . . . . . . . . . . . . . . . . . . . 82-85, 127, 287, 339, 411 O BytChk bit. . . . . . . . . . . . . . . . . . . . . . . 103, 200, 203, 370, 374oO byte check. . . . . . . . . . . . . . . . . . . . . . . 103, 200, 203, 370, 374CO byte count of descriptor data available field . . . . . . . . . . . . . . . 391 O byte count of report available field. . . . . . . . . . . . . . . . . . . . 389AO byte transfer length field. . . . . . . . . . . . . . . . . . . . . . .185, 204gO C/D bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125eO Cable Skew Delay. . . . . . . . . . . . . . . . . . . . 36-38, 45, 46, 422, 425 O Caching Page  . . . . . . . . . . . . . . . . . . . . . . . . . . 210, 327, 377|O CAF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .266, 267=O CANNOT READ MEDIUM - INCOMPATIBLE FORMAT. . . . . . . . . . . . . . . .130, 431 O CANNOT READ MEDIUM - UNKNOWN FORMAT . . . . . . . . . . . . . . . . . .130, 4314O CAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2662O CARTRIDGE FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . .130, 4327O cat bit . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxi, 96, 99, 102 O catenate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99 O cause field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii, 144 O CD-ROM Audio Control Page . . . . . . . . . . . . . . . . . . . . . . . . . 327 O CD-ROM devices. xxx, 124, 297, 299, 304, 305, 313, 325, 326, 328, 330, 336, 357,O CD-ROM Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327 O change active format. . . . . . . . . . . . . . . . . . . . . . . . . . . . 267 O change active partition . . . . . . . . . . . . . . . . . . . . . . . . . . 266 O CHANGE DEFINITION command . . . . . . . . . . . . xxi, 79, 93-95, 104, 156, 164 O change partition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245,O CHANGED OPERATING DEFINITION. . . . . . . . . . . . . . . . . . . .79, 130, 4322O channel bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .277, 283 O channel volume control. . . . . . . . . . . . . . . . . . . . . . . . . . . 329 M CHECK CONDITION status. . . . . 3, 47, 49, 52, 60, 71, 75, 80-82, 88, 92, 95, N                                 98, 99, 101, 102, 104, 108-113, 115-117, 119, L                                 122, 125-127, 134, 135, 137, 139, 140, 142, H                                 143, 145, 149, 153, 162, 166, 169, 170, K                                 172-174, 176, 182-185, 187, 188, 190, 191,  O                                 193, 194, 197, 199, 200, 203-206, 218, 223-226, O                                 228, 230, 233, 240, 243-247, 251-253, 255-262, 7P                                 267, 271, 276-278, 287, 293, 302-304, 306, 307, P                                 309, 310, 312, 323, 331-335, 339, 347-349, 354, M                                 358, 363, 367, 370, 371, 374, 376, 378, 384,  @                                 385, 386, 398-401, 407, 408, 411O CIRC UNRECOVERED ERROR. . . . . . . . . . . . . . . . . . . . . . . . .130, 430 O CLEANING CARTRIDGE INSTALLED. . . . . . . . . . . . . . . . . . . . . .130, 431 O CLEAR QUEUE . . . . . . . . . . . . . . . . . 3, 41, 55, 56, 58, 59, 76, 79, 85 O clear to send . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286 O CmpLst bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . 170, 171, 173 O code field. . . xxii, xxiv, 73, 97, 104, 112, 116, 121, 123-125, 139-141, 143,  L                 144, 148, 149, 156, 158, 208, 209, 256, 263, 264, 279, 280, L                 298, 325, 326, 353, 375, 376, 388, 391, 392, 397, 398, 401,                  402, 404, 418 O command code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73, 74 O COMMAND COMPLETE. . . . . . .3, 41, 52, 55, 59, 62, 75, 77, 78, 83, 86, 94, 423 O command data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125, 317 N command descriptor block. . . xxi, 3, 50, 54, 67, 72-77, 80, 86, 99-102, 107, O                               118, 122, 124, 125, 128, 137, 140, 141, 146-148,  O                               156-158, 173, 178, 182, 188, 195, 198, 199, 219,  H                               243-245, 255, 258, 261, 272, 313, 362, 389O COMMAND Phase . . . . . . . 41, 48, 50, 61, 75, 77, 83, 127, 130, 422, 423, 432 O COMMAND PHASE ERROR . . . . . . . . . . . . . . . . . . . . . . . . . .130, 432 O command queue . . . . . . . . . . . . . . . . . . . . . 3, 4, 64, 67, 77, 83-86 O COMMAND SEQUENCE ERROR. . . . . . . . . . . . . . . . . . . . . . . . .130, 431 O COMMAND TERMINATED status . . . . . . . . . . 61, 67, 76, 82, 83, 122, 126, 128 O command-specific information field. . . . . . . . . . . . . . 98, 124, 187, 194 O COMMANDS CLEARED BY ANOTHER INITIATOR . . . . . . . . . . 59, 85, 130, 150, 4318O communications devices. . . . . . .2, xxvii, xxix, xxx, xxxi, 411-413, 418, 4199O COMPARE command . . . . . . . . . . . . . . . . . . . . . . . . . . xxi, 95, 97,O complete list . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171, 184 O CONDITION MET status. . . . . . . . . . . . . . . . . . . 75, 77, 178, 193, 363LO connect time limit field. . . . . . . . . . . . . . . . . . . . . . . . .3, 153LO connection. . . . . 3, 4, 6, 9, 27, 36, 41, 57-60, 63, 64, 79, 80, 85, 153, 297LM contingent allegiance . .xxxi, 3, 58, 59, 61, 62, 64, 67, 76, 77, 79-85, 88,  2                          92, 95, 122, 149-151, 238O contrast field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345 N control . . . . . .xxi, xxii, xxiv, xxv, xxxii, 3, 6, 33, 37, 42, 44, 45, 67, M                    72, 73, 75, 77, 81, 84-86, 93, 95, 96, 103, 104, 109-112,  L                    114, 115, 117, 118, 121, 122, 134-136, 138, 141-143, 145,L                    149, 153, 162-164, 169, 170, 173, 177-183, 185-187, 189, M                    192, 193, 196-205, 210, 213, 223, 230, 243-246, 248, 249,  M                    251-256, 258, 259, 261, 265, 267, 273, 275-278, 280, 281,  P                    282, 283, 287-290, 292, 293, 300-302, 306-314, 316-318, 320, J                    321, 323, 324, 327, 329, 337, 338, 341, 343, 345, 347, K                    349-351, 353, 360-362, 364-374, 377, 378, 380, 384-388,  =                    396, 398, 399, 401, 411, 414-417, 419, 439 O Control Field . . . . . . . . . . . . xxi, 75, 109-111, 115, 302, 324, 337, 338 L Control Mode Page . . . xxii, 67, 81, 84, 85, 142, 143, 145, 149, 210, 265, /                         280, 327, 353, 377, 419 O COPY ABORTED. . . . . . . . . . . . . . . . . . . . . . . . . .98, 99, 101, 129 O COPY AND VERIFY command . . . . . . . . . . . . . . . . xxi, 103, 123, 124, 231 O COPY CANNOT EXECUTE SINCE HOST CANNOT DISCONNECT. . . . . . . . . . . .130, 431 O COPY command. . . . . . . xxi, xxxii, 5, 27, 95-99, 102-104, 188, 191, 254, 287 O COPY function code field. . . . . . . . . . . . . . . . . . . . . . . . . . .97 O CORRCT bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 O correct . . . . . . . 4, 43, 78, 83, 86, 125, 128, 130, 167, 244, 335, 429, 430 O count basis field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 O count field . . . . . . . . . . . . . 102, 126, 224-228, 231, 256-258, 335, 348 O CP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 O CTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .285, 286,O current I/O process . . . . . . . . . . . . . . . 3, 41, 58, 59, 65, 67, 77, 84 O current operating definition field. . . . . . . . . . . . . . . . . . . . . 157 O cylinder skew factor field. . . . . . . . . . . . . . . . . . . . . . . . . 218 O data buffer recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . 267,O data buffer status descriptor . . . . . . . . . . . . . . . . . . . . . . . 3417O data bytes per physical sector field. . . . . . . . . . . . . . . . . . . . 218tO data bytes per sector field . . . . . . . . . . . . . . . . . . . . . . . . 214bO data defect list. . . . . . . . . . . . . . . . . . . . . .xxiii, 170, 184, 365fP DATA IN Phase . . .48, 61, 75, 77, 118, 119, 182, 277, 292, 313, 324, 342, 349,                      367, 422, 423I DATA OUT Phase. . .48, 72, 74, 81, 96, 109, 110, 113, 125, 137, 170-172,  B                    275-277, 290, 292, 350, 351, 362, 369, 416, 423O DATA PATH FAILURE (SHOULD USE 40 NN). . . . . . . . . . . . . . . . . .130, 432 O DATA PHASE ERROR. . . . . . . . . . . . . . . . . . . . . . . . . . . .130, 432 O DATA PROTECT. . . . . . . . . . . . . . . . . 128, 166, 191, 197, 240, 294, 358 O Data Release Delay. . . . . . . . . . . . . . . . . . . . . . . . . .36, 37, 49 O DATA SYNCHRONIZATION MARK ERROR . . . . . . . . . . . . . . . . . . . .130, 430 O data transfer disconnect control. . . . . . . . . . . . . . . . . . . xxii, 153 O data transfer element . . . xxvii, 379-381, 384, 386, 388, 395, 396, 405, 406,  $                             408, 410O data type qualifier field . . . . . . . . . . . . . . . . . . . . . . . . . 3490O DBD bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 O DBR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .266, 267 O DC bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100, 1019O DCR bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224, 2719O DCRT bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1735O default operating definition field. . . . . . . . . . . . . . . . . . . . . 1573O defect descriptor . . . . . . . . . . . . . . . . xxii, xxiii, 170-175, 184-1871O DEFECT LIST ERROR . . . . . . . . . . . . . . . . . . . . . . . . 130, 173, 431 O DEFECT LIST ERROR IN GROWN LIST . . . . . . . . . . . . . . . . . . . .130, 431 O DEFECT LIST ERROR IN PRIMARY LIST . . . . . . . . . . . . . . . . . . .130, 431 O defect list format field. . . . . . . . . . . . . . . . . . . . . . . .172, 1844O defect list length field. . . . . . . . . . . . . . . . . . . . . 173, 184, 187eO DEFECT LIST NOT AVAILABLE . . . . . . . . . . . . . . . . . . . . . . .130, 431eO DEFECT LIST NOT FOUND . . . . . . . . . . . . . . . 130-132, 173, 183, 184, 431sO DEFECT LIST UPDATE FAILURE. . . . . . . . . . . . . . . . . . . . . . .130, 431kO defect logical block address. . . . . . . . . . . . . . . . . . . . . .186, 187cO definition parameter field. . . . . . . . . . . . . . . . . . . . . xxi, 93, 94cO demand read retention priority field. . . . . . . . . . . . . . . . . . . . 211cO Deskew Delay. . . . . . . . . . . . . . . . . .36, 37, 39, 45, 46, 49, 422, 425tO destination count . . . . . . . . . . . . . . . . . . . . . . . . . . .100, 101iO destination logical block address field . . . . . . . . . . . . . . . . . . 100 O device off-line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134nO device-specific parameter . . . . . . . xxiv, xxv, 146, 147, 263, 272, 279, 326 O DevOfl bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135TO DIAGNOSTIC FAILURE ON COMPONENT NN (80H-FFH). . . . . . . . . . . . . .130, 432TL Diagnostic Parameters . 7, 74, 134, 138, 139, 206, 262, 279, 291, 325, 352, %                         375, 404, 418 M direct-access devices . xxii, xxx, xxxi, 6, 97, 124, 144, 148, 161-163, 165,  L                         168, 206, 208-210, 220, 229, 232, 233, 297, 357, 358O disable block descriptors . . . . . . . . . . . . . . . . . . . . . . . . . 115 O disable certification . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 O disable correction. . . . . . . . . . . . . . . . . . . . . . . . . . .224, 271 O disable page out. . . . . . . . . . . . . . . . . . . . . . . . . . . .163, 181 O disable pre-fetch transfer length field . . . . . . . . . . . . . . . . . . 212 O disable primary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 O disable queuing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 O disable save. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 O disable saving parameters . . . . . . . . . . . . . . . . . . . . . . . . . 173 O disable transfer on error . . . . . . . . . . . . . . . . . . . . . . .223, 271 O disable update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 L DISCONNECT. . . . . .3, xxii, 3, 5, 37, 41, 47, 49, 50, 52, 55, 57, 59, 60, K                      62, 76-79, 84, 86, 122, 126, 130, 149, 152, 153, 210,  O                      265, 280, 287, 288, 327, 353, 377, 411, 412, 419, 421, 431 O disconnect time limit field . . . . . . . . . . . . . . . . . . . . . . .3, 153 M Disconnect-Reconnect Page . .3, xxii, 60, 149, 152, 210, 265, 280, 327, 353, 4%                              377, 419 O Disconnection Delay . . . . . . . . . . . . . . . . . . . . . . . . .36, 37, 59 O displacement field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 O download microcode. . . . . . . . . . . . . . . . . . . . . . . . . . .137, 138 O DPO bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163, 181 O DPOFUA bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . 209, 326, 376 O DPRY bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 O DQue bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85, 150RO drive step pulse width field. . . . . . . . . . . . . . . . . . . . . . . . 214SO drive step rate field . . . . . . . . . . . . . . . . . . . . . . . 3, 214, 230 O DS bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109, 111, 141 O DSP bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 O dt. . . . . . . . . . . . . . . . . . . . . . . . . .130-133, 405, 429-431, 433 O DTE bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224, 2711O DU bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141, 142 O EAENP bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 O EBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326, 370, 376 O EBP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372-374 O EECA bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 O EEG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .266, 268 O EER bit . . . . . . . . . . . . . . . . . . . . . . . . . . .223, 224, 232, 271 O electronic vertical forms unit. . . . . . . . . . . . . . . .133, 282, 283, 432 O Element Address Assignment Page . . . . . . . . . . . . . . . . . . .xxvii, 406 O element address field . . . . . . . . . . . . .380, 392-394, 397, 402, 407, 408 O element bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398-401 O element descriptor length field . . . . . . . . . . . . . . . . . . . . . . 391 O element descriptors . . . . . . . . . . . . . . . . . . 388, 389, 391, 397, 400 O element status. . . . . .xxvi, xxvii, 381-383, 385, 388-391, 393, 397, 435, 438-O element type code field . . . . . . . . . . . . . . . . . . .388, 391, 397, 401SO enable blank check. . . . . . . . . . . . . . . . . . . . . . . . 326, 370, 376cO enable early recovery . . . . . . . . . . . . . . . . . . . . . . . . .223, 271 O enable EOD generation . . . . . . . . . . . . . . . . . . . . . . . . . . . 268eO enable extended contingent allegiance . . . . . . . . . . . . . . . . . . . 151OO enable threshold comparison . . . . . . . . . . . . . . . . . . . . . . . . 141 O enable vital product data . . . . . . . . . . . . . . . . . . . . . . . . . 104iO end of partition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250eO END OF USER AREA ENCOUNTERED ON THIS TRACK. . . . . . . . . .130, 304, 307, 433 O END-OF-DATA DETECTED. . . . . . . . . . . . . . . . . . . . . . . . . .130, 429 O END-OF-DATA NOT FOUND . . . . . . . . . . . . . . . . . . . . . . . . .130, 430,O end-of-medium . . . . . . 123, 133, 233, 234, 236, 239, 244, 272, 278, 355, 432-O END-OF-PARTITION/MEDIUM DETECTED. . . . . . . . . . . . . . . . . . . .130, 429 O end-of-tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 O ending boundary field . . . . . . . . . . . . . . . . . . . . . . . . . . . 222,O ending F field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3092O ending index field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310,O ending M field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3094O ending S field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3093O ending track field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310oO EOD defined field . . . . . . . . . . . . . . . . . . . . . . . . . . .268, 272oO EOM bit . . . . . . . . . . . . . . . . . . . 123, 247, 257, 258, 267, 347, 348 O EOP . . . . . . . . . . . . . . . . . . . . . . . .236, 237, 239, 240, 249, 250 O EOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .244, 272 M EQUAL . . 38, 45, 47, 57, 66, 68, 78, 113, 129, 142, 147, 168, 174, 175, 182,OK           184, 187, 193, 195, 212, 214, 221, 228, 230, 248, 250, 295, 301, xJ           304, 305, 307, 309-311, 313, 344, 352, 354, 355, 359, 362, 363,            388, 436, 438 O ERA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .360, 361 O erase all . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3601O erase by-pass . . . . . . . . . . . . . . . . . . . . . . . . . . . . .372, 374 O ERASE command . . . . . . . . . . . . . . . . . . . . . . . xxiv, 238, 243, 357-O ERASE FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130, 432 O ERASE(10) command . . . . . . . . . . . . . . . . . . . . . . . .xxvi, 360, 361 O ERASE(12) command . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi, 361,O error AEN permission. . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 O Error Counter Pages . . . . . . . . . . . . . . . . . . . . . . . . . xxii, 144 O ERROR LOG OVERFLOW. . . . . . . . . . . . . . . . . . . . . . . . . . .130, 430 O ERROR TOO LONG TO CORRECT . . . . . . . . . . . . . . . . . . . . . . .130, 430 O ETC bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141, 142 O EVFU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .282, 283 O EVFU format start character field . . . . . . . . . . . . . . . . . . . . . 283 O EVFU format stop character field. . . . . . . . . . . . . . . . . . . . . . 2837O EVPD bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104, 108 L except. . . . . . . . . 28, 36, 41, 48, 50, 51, 59, 64, 76, 78, 80, 84, 95, N                         103, 110, 112, 116, 122, 124, 134, 138, 141, 142, 150,J                         154, 169, 170, 171, 251, 252, 300, 302, 303, 324, $                         392-395, 427O EXCESSIVE WRITE ERRORS. . . . . . . . . . . . . . . . . . . . . . . . .130, 4297O EXCHANGE MEDIUM command . . . . . . . . . . . . . . . . . . . . . . . xxvi, 384 O exclusive access. . . . . . . . . . . . . . . . . . . . . . .190, 191, 379, 395 O ExEnab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394 O export enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394 O extended contingent allegiance. . .xxxi, 3, 58, 59, 61, 62, 64, 79, 81, 83-85,  3                                    95, 149-151, 2380O extent. . . . . . . . . . . . . . . . . .xxiii, 77, 162, 164, 165, 169, 187-192 O extent bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188-190 O extent list length field. . . . . . . . . . . . . . . . . . . . . . . . . . 1909O FAILED TO SENSE BOTTOM-OF-FORM. . . . . . . . . . . . . . . . . . . . .130, 4329O FAILED TO SENSE TOP-OF-FORM . . . . . . . . . . . . . . . . . . . . . .130, 4325O Fast Assertion Period . . . . . . . . . . . . . . . . . . . . . . . 36, 38, 4253O Fast Cable Skew Delay . . . . . . . . . . . . . . . . . . . . . . . 36, 38, 4251O Fast Deskew Delay . . . . . . . . . . . . . . . . . . . . . . . . . 36, 39, 425 O Fast Hold Time. . . . . . . . . . . . . . . . . . . . . . . . . . . 36, 39, 425 O Fast Negation Period. . . . . . . . . . . . . . . . . . . . . . . . 36, 39, 425 O Fast Synchronous Transfer Option. . . . . . . . . . . . . . . . . . . . . . .384O FDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269eO field pointer field . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125eO filemark. . . . .123, 128, 130, 237, 240, 247, 251, 252, 256-258, 272, 429, 430sO filemark bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123, 257kO FILEMARK DETECTED . . . . . . . . . . . . . . . . . . . . . . . . . . .130, 429cO FILEMARK OR SETMARK NOT FOUND . . . . . . . . . . . . . . . . . . . . .130, 430cO filled data buffer field. . . . . . . . . . . . . . . . . . . . . . . . . . 342cO first block location field. . . . . . . . . . . . . . . . . . . . . . . . . 250tO first data transfer element address field . . . . . . . . . . . . . . . . . 408iO first element address reported field. . . . . . . . . . . . . . . . . . . . 389 O first import export element address field . . . . . . . . . . . . . . . . . 408nO first record offset field . . . . . . . . . . . . . . . . . . . . . . . . . 194 O first storage element address field . . . . . . . . . . . . . . . . . . . . 407TO fixed bit . . . . . . . . . . . . . . .124, 240, 241, 246-248, 251-253, 258-260TO fixed data partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 O flag bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62, 75, 301 O Flexible Disk Page. . . . . . . . . . . . . . . . . . . . . .3, xxiii, 210, 2130O FmtData bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171-173 O FOCUS SERVO FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . .130, 429 O font identification field . . . . . . . . . . . . . . . . . . . . . . . . . 282 O forced unit access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 O form slew options field . . . . . . . . . . . . . . . . . . . . . . . . . . 284 O FORMAT command. . . . . . . . . . . . . . . . . . . . .xxiv, 130, 275, 283, 431 O FORMAT COMMAND FAILED . . . . . . . . . . . . . . . . . . . . . . . . .130, 431 O format data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169, 170 O Format Device Page. . . . . . . . . . . . . . . . . . . . .xxiii, 165, 210, 216 O format of logical blocks addresses per second field . . . . . . . . . . . . 328 O format options valid. . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 O format type field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2759P FORMAT UNIT command . . .xxii, 116, 126, 162, 165, 169-173, 183, 184, 186, 191, *                          206, 217-219, 293O FOV bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172iO FUA bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181tO full bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392 O gap size field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 O generation address field. . . . . . . . . . . . . . . . . . . . . . . .366, 367 O GENERATION DOES NOT EXIST . . . . . . . . . . . . . . . . . . . . 130, 367, 433 O GET DATA BUFFER STATUS command. . . . . . . . . . . . . . . . . . . . xxvi, 341 O GET MESSAGE(10) command . . . . . . . . . . . . . . . . . . . . . . .xxvii, 414 O GET MESSAGE(12) command . . . . . . . . . . . . . . . . . . . . . . .xxvii, 415 O GET WINDOW command. . . . . . . . . . . . . . . . . . . . . . . .xxvi, 343, 345 O Glist bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183, 184 L GOOD status . . 77, 82, 86, 89, 92, 116, 122, 126, 127, 134, 135, 165, 178, O                 181, 187, 193, 211, 238, 253, 259, 263, 278, 280, 347, 363, 398 O group code. . . . . . . . . . . . . . . . . . . . . . . . . . .73, 74, 265, 422 O grown defect list . . . . . . . . . . . . . . 131, 170, 173, 183, 184, 186, 4313O GROWN DEFECT LIST NOT FOUND . . . . . . . . . . . . . . . . . . . . . .131, 431 O hard sector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .218, 219 O HARDWARE ERROR. . . . . . . . .125, 128, 134, 166, 187, 230, 240, 294, 304, 358 O head load delay field . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 O HEAD OF QUEUE TAG . . . . . . . . . . . . . . . . . xxi, 55, 63, 64, 77, 85, 87 O head settle delay field . . . . . . . . . . . . . . . . . . . . . . . . . . 214 O head unload delay . . . . . . . . . . . . . . . . . . . . . . . . . . .213, 215 O Hold Time . . . . . . . . . . . . . . . . . . . . . . . . . .36-39, 46, 51, 425 O host adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3, 5, 421 O HSEC bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 O i/e . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405,J I/O process . . . .3-5, 41, 42, 47, 51, 52, 54, 55, 58-61, 63-65, 67, 75, N                    77-82, 84-87, 107, 122, 126, 127, 131, 150, 151, 230, 421,                     429O I/O PROCESS TERMINATED. . . . . . . . . . . . . . . . . . . . . . .67, 131, 429 O I_T . . . . 4, 57, 58, 60, 61, 63, 64, 74, 77-79, 81-84, 86, 112, 122, 150, 253 O I_T_L . . . . . . . . 4, 57, 58, 60, 61, 63, 64, 74, 77-79, 81-84, 86, 112, 253 O I_T_L_Q . . . . . . . . . . . . . . . . . . . . . 4, 58, 61, 63, 64, 79, 84, 86 O I_T_R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4, 57, 60 O I_T_x . . . . . . . . . . . . . . . . . . . . . . . .4, 58, 64, 82-84, 122, 150 O I_T_x_y . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 O ID CRC OR ECC ERROR . . . . . . . . . . . . . . . . . . . . . . . . . .131, 430 O ID Valid bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396 N IDENTIFY. . . 2, xxi, 4, 6, 50, 51, 55-58, 60, 61, 64, 74, 77-79, 83, 84, 86, M               91, 95, 103, 105, 127, 128, 131, 161, 167, 173, 189, 270, 399, 3               422, 432O IDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269OO IGNORE WIDE RESIDUE . . . . . . . . . . . . . . . . . . . . . . . . xxi, 55, 61 O ILI bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .348, 349IO ILLEGAL FUNCTION (SHOULD USE 20 00, 24 00, OR 26 00). . . . . . . . . .131, 431 O ILLEGAL MODE FOR THIS TRACK . . . . . . . . . . . . . . . . .131, 304, 307, 433rP ILLEGAL REQUEST . . .60, 71, 75, 80, 99, 101, 102, 104, 108-113, 115, 116, 119, L                      125, 128, 135, 137, 139, 140, 142, 143, 149, 153, 166, F                      170, 172, 176, 182, 185, 188, 190, 191, 194, 199,K                      204-206, 227, 228, 240, 244, 246, 256, 258, 277, 283, 0K                      284, 294, 303, 304, 307, 309-311, 323, 331, 347, 354,  =                      358, 360, 371, 384-386, 398-402, 406-408 O image composition field . . . . . . . . . . . . . . . . . . . . . . . . . . 345 O Immed bit . . . . . . 126, 173, 178, 198, 199, 243-245, 255, 258, 259, 261, 328 N immediate . . . . . 81, 126, 173, 178, 198, 199, 238, 243-245, 255, 258, 261, !                     302, 306, 328 O ImpExp. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .394, 395 O Implemented Operating Definition Page . . . . . . . . . . . .xxii, 94, 155, 156 O import enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394,O import export . . .xxvii, 379, 380, 384, 386, 388, 394, 395, 405, 406, 408, 410 O import export element . xxvii, 379, 384, 386, 388, 394, 395, 405, 406, 408, 410 O IMPORT OR EXPORT ELEMENT ACCESSED . . . . . . . . . . . . . . . . . . .131, 431 O inactivity timer multiplier . . . . . . . . . . . . . . . . . . . . . .xxv, 329 O INCOMPATIBLE MEDIUM INSTALLED . . . . . . . . . . . . . . . . . . . . .131, 431 O INCOMPLETE BLOCK READ . . . . . . . . . . . . . . . . . . . . . . . . .131, 430 O incorrect length indicator. . . . . . . . . . . . . . . . . . . . . . .123, 246 O InEnab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394 K information field . . 67, 98, 102, 123, 124, 128, 156, 166, 185, 187, 194,  O                      204, 225-228, 241, 243, 246, 247, 251-253, 256, 257, 259, x?                      260, 261, 262, 294, 304, 358, 359, 391-395 O Information Page. . . . . . . . . . . . . . . . . . . . . . xxii, 125, 155, 156 O initial connection. . . . . . . . . . . . . . . . . . . . .3, 4, 60, 63, 79, 85 O initialization pattern. . . . . . . . . . . . . . . . xxiii, 170, 173, 175, 176 O initialization pattern descriptor . . . . . . . . . . . . .xxiii, 170, 173, 175 O initialization pattern length field . . . . . . . . . . . . . . . . . . . . 176 O INITIALIZE ELEMENT STATUS command . . . . . . . . . . . . . . . .xxvi, 381, 385 O INITIATE RECOVERY . . . . . . . . . . . . . . . . 3, 55, 56, 61, 62, 64, 83, 95 O INITIATOR DETECTED ERROR. . . . . . . . . . . . . . . . . .47, 55, 62, 131, 4321O INITIATOR DETECTED ERROR MESSAGE RECEIVED . . . . . . . . . . . . . . .131, 4322O initiator-defined partitions. . . . . . . . . . . . . . . . . . . . . . . . 269 O INQUIRY command . . . .xxi, 65, 79-82, 88, 91, 92, 94, 95, 104, 108, 154, 156,  .                        158, 169, 219, 357, 378O INQUIRY DATA HAS CHANGED. . . . . . . . . . . . . . . . . . . . . . . .131, 4329O interleave field. . . . . . . . . . . . . . . . . . . . . . . . . . . .172, 2189O INTERMEDIATE status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1789O INTERMEDIATE-CONDITION MET status . . . . . . . . . . . . . . .75, 77, 178, 193,O INTERNAL TARGET FAILURE . . . . . . . . . . . . . . . . . . . . . . . .131, 432 O Inv1 bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385 O Inv2 bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385dO INVALID BITS IN IDENTIFY MESSAGE. . . . . . . . . . . . . . . . . .60, 131, 432OO INVALID COMBINATION OF WINDOWS SPECIFIED. . . . . . . . . . . . . . . .131, 431FO INVALID COMMAND OPERATION CODE. . . . . . . . . . . . . . . . . . . . .131, 431 O INVALID ELEMENT ADDRESS . . . . . . . . . . . . . . . . . . . . . . . .131, 431 L INVALID FIELD IN CDB. . . .104, 108-113, 115, 116, 131, 135, 137, 185, 199, 7                            204, 246, 323, 360, 371, 4312L INVALID FIELD IN PARAMETER LIST . . .99, 101, 110, 111, 113, 131, 139, 140, M                                      142, 143, 149, 170, 172, 176, 206, 227,  -                                      331, 431 O INVALID MESSAGE ERROR . . . . . . . . . . . . . . . . . . . . . . . . .131, 432 O invert. . . . . . . . . . . . . . . . . . 193, 195, 368, 382, 386, 387, 392-395 O Invert bit. . . . . . . . . . . . . . . . . . . . .193, 195, 382, 386, 387, 3932O IP bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 O IP modifier field . . . . . . . . . . . . . . . . . . . . . . . . . . .175, 176 O L-EC UNCORRECTABLE ERROR. . . . . . . . . . . . . . . . . . . . . . . .131, 430 O LAMP FAILURE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131, 433 O landing zone cylinder field . . . . . . . . . . . . . . . . . . . . . . . . 230 O last block location field . . . . . . . . . . . . . . . . . . . . . . . . . 250iO Last n Error Events Page. 143, 145, 208, 262, 279, 291, 325, 353, 375, 404, 418 O latest bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367iO line slew options field . . . . . . . . . . . . . . . . . . . . . . . . . . 283 O link bit. . . . . . . . . . . . . . . . . . . . . . . . .75, 178, 193, 203, 363 O LINKED COMMAND COMPLETE . . . . . . . . . . . . . . . . . . . . .55, 62, 75, 78 O LINKED COMMAND COMPLETE (WITH FLAG) . . . . . . . . . . . . . . .55, 62, 75, 78 O list parameter. . . . . . . . . . . . . . . . . . . . . . . . . . . . .142, 145 O load bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4, 244 O load eject. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 O LOAD UNLOAD command . . . . . . . . . . . . . . . . . . . . . . .xxiv, 244, 272 O LOCATE command. . . . . . . . . . . . . . . . . . . . . . . xxiv, 239, 245, 250 O lock. . . . . . . . . . . . .xxiii, 163, 164, 168, 177, 294, 300, 305, 359, 436 O lock bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 O LOCK UNLOCK CACHE command . . . . . . . . . . . . . . . . . . . . . .xxiii, 177 O LoEj bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 O LOG COUNTER AT MAXIMUM. . . . . . . . . . . . . . . . . . . . . . 131, 142, 433 O LOG EXCEPTION . . . . . . . . . . . . . . . . . . . . . . . . . . 131, 150, 433 O LOG LIST CODES EXHAUSTED. . . . . . . . . . . . . . . . . . .131, 142, 145, 433rM Log Parameters. . . .7, 74, 109-112, 131, 135, 140, 141, 144, 208, 262, 279,  6                      291, 325, 352, 375, 404, 418, 431O LOG PARAMETERS CHANGED. . . . . . . . . . . . . . . . . . . . . . 110, 131, 431IO LOG SELECT command. . . . . . . . . . . . . . .xxi, 109-111, 140, 141, 143, 146 O LOG SENSE command . . . . . . . . . . . . . . . . . xxi, 109, 111, 140-142, 145 H logical block . . 4, 7, 50, 72-74, 78, 86, 99, 100, 123, 124, 131, 148, O                   161-163, 165-167, 169, 174, 176-178, 180-187, 190, 191, 193,  L                   194, 196, 197, 199-208, 212, 218, 221, 222, 225-228, 231, M                   237-240, 245, 247, 249, 250, 252, 293, 294, 297, 299, 300,  M                   303, 304, 307, 308, 311-315, 319, 324, 326, 328, 337, 338,  ,                   357-364, 366-374, 378, 431H Logical Block Address . . . 7, 72-74, 99, 100, 124, 131, 161, 162, 166, L                             176-178, 180-187, 190, 191, 193, 194, 196, 197, M                             199-207, 221, 222, 225, 226, 227, 240, 245, 249,  L                             293, 294, 299, 300, 303, 304, 307, 308, 311-315,O                             319, 324, 328, 337, 357-364, 366, 367, 368-374, 431 O LOGICAL BLOCK ADDRESS OUT OF RANGE. . . . . . . . . . . . . . . . . . .131, 431,O logical block data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2050O logical blocks per second of audio playback field . . . . . . . . . . . . . 3287O logical or physical notch . . . . . . . . . . . . . . . . . . . . . . . . . 2213O logical record length field . . . . . . . . . . . . . . . . . . . . . . . . 194 M logical unit. . .xxxi, 4-6, 51, 57-60, 64, 72-74, 77, 79, 80, 82-84, 86, 88,  O                  89, 91-96, 98-101, 103-107, 109-112, 114, 115, 117, 118, 121, 2L                  122, 127, 128, 131, 134-136, 143, 146, 148, 154, 155, 158, N                  159, 164, 169, 177-183, 185-193, 196-205, 210, 216, 217-222, M                  230, 243-256, 258-262, 267-270, 273, 275-278, 287, 289, 290, O                  306-314, 316, 323, 328, 341, 343, 347, 349-351, 360-362, 364,  O                  366-374, 381, 384-388, 395, 396, 398, 399, 401, 411, 414-417,                    429, 431, 432O LOGICAL UNIT COMMUNICATION FAILURE. . . . . . . . . . . . . . . . . . .131, 429CO LOGICAL UNIT COMMUNICATION PARITY ERROR . . . . . . . . . . . . . . . .131, 429 O LOGICAL UNIT COMMUNICATION TIME-OUT . . . . . . . . . . . . . . . . . .131, 429 O LOGICAL UNIT DOES NOT RESPOND TO SELECTION. . . . . . . . . . . . . . .131, 429 O LOGICAL UNIT FAILED SELF-CONFIGURATION. . . . . . . . . . . . . . . . .131, 432 O LOGICAL UNIT HAS NOT SELF-CONFIGURED YET. . . . . . . . . . . . . . . .131, 432,O LOGICAL UNIT IS IN PROCESS OF BECOMING READY. . . . . . . . . . . . . .131, 429,O LOGICAL UNIT NOT READY, CAUSE NOT REPORTABLE. . . . . . . . . . . . . .131, 429,O LOGICAL UNIT NOT READY, FORMAT IN PROGRESS. . . . . . . . . . . . . . .131, 4297O LOGICAL UNIT NOT READY, INITIALIZING COMMAND REQUIRED . . . . . . . . .131, 429 O LOGICAL UNIT NOT READY, MANUAL INTERVENTION REQUIRED. . . . . . . . . .131, 429,O LOGICAL UNIT NOT SUPPORTED. . . . . . . . . . . . . . . . . . 80, 131, 135, 431 L Logical Unit Number . . 4, 5, 57, 60, 72-74, 91, 93, 95, 96, 103, 104, 109, N                         111, 112, 114, 115, 117, 118, 121, 122, 134-136, 169, O                         177-183, 185-187, 189, 192, 193, 196-205, 243-246, 248,9M                         249, 251-256, 258, 259, 261, 273, 275-278, 289, 290, 8H                         306, 307-314, 316, 323, 341, 343, 347, 349-351, L                         360-362, 364, 366-374, 381, 384-388, 395, 396, 398, .                         399, 401, 414, 415-417O long bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2434O LP bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141, 1423O LPN bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .221, 2223O LU Valid bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3969L mandatory . . . . . . . .xxxi, 4, 6, 56, 57, 63, 71, 74, 92, 123, 124, 134, P                          168, 169, 172, 188, 189, 191, 192, 237, 242, 256, 274, H                          289, 295, 305, 340, 359, 383, 413, 421, 435-438O maximum additional partitions field . . . . . . . . . . . . . . . . . . . . 269 O maximum burst size field. . . . . . . . . . . . . . . . . . . . . . . . . . 153 O maximum generation address field. . . . . . . . . . . . . . . . . . . . . . 3662O maximum line length field . . . . . . . . . . . . . . . . . . . . . . . . . 283 O maximum number of notches field . . . . . . . . . . . . . . . . . . . . . . 2213O maximum pre-fetch ceiling field . . . . . . . . . . . . . . . . . . . . . . 2123O maximum pre-fetch field . . . . . . . . . . . . . . . . . . . . . . . . . . 2121O maximum volume sequence number. . . . . . . . . . . . . . . . . . . . . . . 403 O MCVal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317, 319, 3214O Measurement Units Page. . . . . . . . . . . . . . . . . . . . . . . . xxvi, 3534O MECHANICAL POSITIONING ERROR. . . . . . . . . . . . . . . . . . . . . .131, 4301O MEDIA LOAD OR EJECT FAILED. . . . . . . . . . . . . . . . . . . . . . .131, 433xO MEDIUM DESTINATION ELEMENT FULL . . . . . . . . . . . . . . . . . . . .131, 4321M MEDIUM ERROR. . . . .xxii, 125, 128, 143, 145, 166, 173, 183, 187, 208, 238,  P                      240, 247, 257, 258, 260, 279, 291, 294, 304, 325, 331-335, 6                      347, 348, 353, 358, 370, 404, 418O MEDIUM FORMAT CORRUPTED . . . . . . . . . . . . . . . . . . . . . . . .131, 431,O medium format recognition field . . . . . . . . . . . . . . . . . . . . . . 2706O MEDIUM NOT PRESENT. . . . . . . . . . . . . . . . . . . . . . . . 131, 135, 4325O Medium Partition Page . . . . . . . . . . . . . . . . . . . xxiv, 266, 269, 270iO MEDIUM REMOVAL PREVENTED. . . . . . . . . . . . . . . . . . . . . 131, 179, 433,O medium rotation rate field. . . . . . . . . . . . . . . . . . . . . . . . . 2160O MEDIUM SCAN command . . . . . . . . . . . . . . . . . .xxvi, 293, 358, 362, 363iO MEDIUM SOURCE ELEMENT EMPTY . . . . . . . . . . . . . . . . . . . . . .131, 432 H medium transport element. .xxvii, 379, 380, 384, 386-388, 392, 394-396, ,                            405-407, 409, 410O medium transport element address field. . . . . . . . . . . . . . . . .380, 407EO medium type . . . . . . . . . .xxv, 146, 147, 167, 209, 219, 220, 325, 357, 375EO medium types supported. . . . . . . . . . . . . . . . xxiii, 210, 219, 327, 377aO Medium Types Supported Page . . . . . . . . . . . . . xxiii, 210, 219, 327, 377 O medium-changer devices. . . . . . . . . . . . . . . . . . . . . . . . . . . 379 O MESSAGE ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . .49, 131, 432 O MESSAGE IN Phase. . . . . . . . . . .48, 50, 52, 59-62, 64, 66, 69, 77, 78, 423 O MESSAGE OUT Phase 43, 44, 48-50, 52, 55, 60, 62-64, 66, 68, 69, 77, 79, 86, 422 O MESSAGE PARITY ERROR. . . . . . . . . . . . . . . . . . . . .50, 55, 62, 66, 68 O MESSAGE REJECT. . . . . . . . . . . . . . . .55, 59, 60, 62, 63, 65-69, 85, 151 O MF bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211, 212 O MICROCODE HAS BEEN CHANGED. . . . . . . . . . . . . . . . . . 88, 131, 138, 432 O minimum pre-fetch field . . . . . . . . . . . . . . . . . . . . . . . . . . 212 O minimum volume sequence number. . . . . . . . . . . . . . . . . . . . . . . 403 O MISCOMPARE. . . . . . . . . . . 95, 104, 129, 131, 200, 203, 259, 370, 374, 431 O MISCOMPARE DURING VERIFY OPERATION. . . . . . . . . . . . . . . . . . .131, 431 O MISCORRECTED ERROR. . . . . . . . . . . . . . . . . . . . . . . . . . .131, 4301O MO bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 O mode field. . . . . . . . . . xxi, xxii, 118, 137, 259, 263, 280, 283, 301, 315 P mode parameter header . . . . xxii, 113, 115, 116, 146, 147, 208, 209, 259-261, N                               263, 272, 279, 325, 326, 353, 375, 376, 404, 418P Mode Parameters . . . . . . . .7, 74, 88, 112, 113, 115-117, 127, 131, 146-149, P                                162, 188, 191, 208, 210, 231, 246, 253-255, 263, P                                279, 303, 307, 308, 309-312, 325, 339, 349, 351, ;                                353, 370, 375, 404, 418, 431 O MODE PARAMETERS CHANGED . . . . . . . . . . . . . . . . . . . . . 112, 131, 431EO MODE SELECT(10) command . . . . . . . . . . . . . . . . . . . . . xxi, 114, 117 O MODE SENSE(10) command. . . . . . . . . . . . . . . . . . . .xxi, 114, 115, 117nO MODIFY DATA POINTER . . . . . . . . . . . . . . . . . . . . . . xxi, 55, 57, 63oO motor off delay field . . . . . . . . . . . . . . . . . . . . . . . . . . . 214tO motor on. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213-215 O motor on delay field. . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 O MOVE MEDIUM command . . . . . . . . . . . . . . . . . . . . xxvi, 382, 386, 387 P MSF . . . . . . . . . xxv, 297-300, 302, 303, 305, 307, 309, 311, 313-316, 319, 7                       323, 324, 329, 330, 337, 338, 437,O mt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405,O MULTIPLE PERIPHERAL DEVICES SELECTED. . . . . . . . . . . . . . . . . .131, 429 O MULTIPLE READ ERRORS. . . . . . . . . . . . . . . . . . . . . . . . . .131, 430 O multiplication factor . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 O ND bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .218, 221 O Negation Period . . . . . . . . . . . . . . . . . . . . 36, 37, 39, 45, 46, 425 O nexus . . . . .3, 4, 41, 50, 57, 58, 60, 61, 63-65, 74, 77-79, 81-84, 86, 112,                  122, 151, 253O NO ADDITIONAL SENSE INFORMATION . . . . . . . . . . . . 122, 124, 131, 135, 429nO NO CURRENT AUDIO STATUS TO RETURN . . . . . . . . . . . . . . . . 131, 318, 429 O NO DEFECT SPARE LOCATION AVAILABLE. . . . . . . . . . . . . .131, 187, 370, 431 O NO GAP FOUND. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131, 430 O NO INDEX/SECTOR SIGNAL. . . . . . . . . . . . . . . . . . . . . . . . .131, 429DO NO OPERATION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55, 63 O NO SEEK COMPLETE. . . . . . . . . . . . . . . . . . . . . . . . . . . .132, 429 N NO SENSE. . . . 67, 80, 122, 128, 135, 183, 193, 194, 247, 251-253, 256, 257, '                 259, 261, 276, 302, 363TO NO WRITE CURRENT. . . . . . . . . . . . . . . . . . . . . . . . . . . .132, 429 O Non-Medium Error Page . . . . . . . 143, 145, 208, 279, 291, 325, 353, 404, 418lO Not Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .395, 396 L NOT READY . . . . 80, 116, 117, 126, 128, 131-133, 135, 136, 162, 169, 233, N                   244, 264, 287, 302, 307, 309, 310, 312, 339, 411, 429, 431,                    4329O NOT READY TO READY TRANSITION(MEDIUM MAY HAVE CHANGED). . . . . . . . . . . 431-O not this bus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3961O Notch and Partition Page. . . . . . . . . . . . . . . . . . . . . . . .210, 220 O notched drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 O number of blocks field. . . . . . . . . . . . . 98-101, 148, 177, 197, 199, 205 O number of blocks in buffer field. . . . . . . . . . . . . . . . . . . . . . 251 O number of blocks requested field. . . . . . . . . . . . . . . . . . . .362, 363DO number of blocks to scan field. . . . . . . . . . . . . . . . . . . . .362, 363aO number of bytes in buffer field . . . . . . . . . . . . . . . . . . . . . . 251pO number of cylinders field . . . . . . . . . . . . . . . . . . . . 214, 229, 230iO number of data transfer elements field. . . . . . . . . . . . . . . . . . . 408lO number of elements available field. . . . . . . . . . . . . . . . . . . . . 389 O number of F units per S unit field. . . . . . . . . . . . . . . . . . . . . 3308O number of heads field . . . . . . . . . . . . . . . . . . . . . . . . .214, 2291O number of import export elements field. . . . . . . . . . . . . . . . . . . 408 O number of medium transport elements field . . . . . . . . . . . . . . . . . 4074O number of records field . . . . . . . . . . . . . . . . . . . . . . . . . . 194 O number of S units per M unit field. . . . . . . . . . . . . . . . . . . . . 330 O number of storage elements field. . . . . . . . . . . . . . . . . . . . . . 407,O OBJECT POSITION command . . . . . . . . . . . . . . . . . . . . . . . xxvi, 347 O offset boundary field . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 M Operation Code. . . . .xxi, 71-74, 93, 95, 96, 103, 104, 109, 111, 112, 114, 1L                        115, 117, 118, 121, 122, 131, 134-136, 169, 177-183, L                        185, 186, 187, 189, 192, 193, 195-205, 243-246, 248, G                        249, 251-255, 258, 259, 261, 275-278, 289, 290,  K                        306-314, 316, 323, 341, 343, 347, 349-351, 360-362,  K                        364, 366-374, 384-388, 396, 398, 399, 401, 414-417,                          431O OPERATOR MEDIUM REMOVAL REQUEST . . . . . . . . . . . . . . . . . . . .132, 4332O OPERATOR REQUEST OR STATE CHANGE INPUT (UNSPECIFIED). . . . . . . . . .132, 4332O OPERATOR SELECTED WRITE PERMIT. . . . . . . . . . . . . . . . . . . . .132, 4332O OPERATOR SELECTED WRITE PROTECT . . . . . . . . . . . . . . . . . . . .132, 4333O optical memory devices. . . . .xxvi, xxx, 124, 293, 296, 357, 359, 360, 375-378 O Optical Memory Page . . . . . . . . . . . . . . . . . . . . . . .xxvi, 377, 378 O ORDERED QUEUE TAG . . . . . . . . . . . . . . . . . . . .55, 63, 64, 77, 84, 85 O OUT OF FOCUS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132, 433 O output port channel selection . . . . . . . . . . . . . . . . . . . . .xxv, 328 O OVERLAPPED COMMANDS ATTEMPTED . . . . . . . . . . . . . . . . . . .80, 132, 432 O OVERWRITE ERROR ON UPDATE IN PLACE. . . . . . . . . . . . . . . . . . .132, 431 O pacing protocol field . . . . . . . . . . . . . . . . . . . . . . . . . . . 286 O pad bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96, 99, 102 O padding type field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346 O page code field . . . . . . . . . . . . .112, 116, 121, 139, 140, 149, 156, 1587O page control. . . . . . . . . . . . . . . . . . . . . . . . . xxi, 109-111, 115,P page format . .xxii, 112, 115, 121, 134, 138-140, 144, 148, 149, 210, 266, 280, &                327, 353, 377, 405, 419O page length field . . . . . . . . . . . . . . .139, 140, 146, 149, 155-159, 207fO pages notched field . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222aO paper instruction parity check. . . . . . . . . . . . . . . . . . . . . . . 281 O PAPER JAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132, 347, 432oO Parallel Printer Interface Page . . . . . . . . . . . . . . . . . . . . . . 280eO parameter code field. . . . . . . . . . . . . . . . . . . . xxii, 141, 143, 144iO parameter code reset. . . . . . . . . . . . . . . . . . . . . . . . . . . . 109eO parameter data length field . . . . . . . . . . . . . . . . . . . . . . . . .94 O Parameter List Length . . . 67, 72-74, 95, 96, 99-101, 103, 109, 110, 112-114, a7                             132, 134-138, 362, 401, 4315O PARAMETER LIST LENGTH ERROR . . . . . . . . . . . . . . . . . . . 113, 132, 4313O parameter list length field . . . . . . . . . . . . . . .96, 110, 113, 135, 1373O PARAMETER NOT SUPPORTED . . . . . . . . . . . . . . . . . . . . . . . .132, 4313O parameter pointer control . . . . . . . . . . . . . . . . . . . . . . . . . 111 O parameter rounding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80 O parameter value field . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 O PARAMETER VALUE INVALID . . . . . . . . . . . . . . . . . . . . . . . .132, 431oO PARAMETERS CHANGED. . . . . . . . . . . . . . . . . . . 110, 112, 131, 132, 431 N parameters savable. . . 149, 210, 214, 217, 220-222, 229, 231, 281, 282, 285, =                         328-330, 336, 354, 378, 405, 407, 409IO parity select field . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281iO parity selection field. . . . . . . . . . . . . . . . . . . . . . . . . . . 286IO partial medium indicator. . . . . . . . . . . . . . . . . . . . . . . .182, 313IO partial results acceptable. . . . . . . . . . . . . . . . . . . . . . . . . 362iO partition field . . . . . . . . . . . . . . . . . . . . . . . . . 245, 266, 267 O partition size descriptor . . . . . . . . . . . . . . . . . . . . . . .269, 270 O partition size field. . . . . . . . . . . . . . . . . . . . . . . . . . . . 2706O partition size unit of measure. . . . . . . . . . . . . . . . . . . . . . . 269 O pattern field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 O pattern length field. . . . . . . . . . . . . . . . . . . . . . . . . .176, 195 O pattern type field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 O PAUSE RESUME command. . . . . . . . . . . . . . . . . . . . . . . . . .xxv, 306,O PCR bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109-O PER bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223, 271 O Peripheral Device Page. . . . xxii, 149, 154, 210, 266, 280, 327, 353, 377, 419,O peripheral device type field. . . . . . . . . . . . . . . . . . . . . . 155-159 O PERIPHERAL DEVICE WRITE FAULT . . . . . . . . . . . . . . . . . . . . .132, 429 O peripheral qualifier field. . . . . . . . . . . . . . . . . . . . . . . 155-159 O PF bit. . . . . . . . . . . . . . . . . . . . . . . . . . . .112, 134, 135, 138 O physical block data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2053O pin 1 field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 O pin 34 field. . . . . . . . . . . . . . . . . . . . . . . . . . xxiii, 215, 216 O pin 4 field . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxiii, 215 O PIPC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280, 2813O PLAY AUDIO MSF command. . . . . . . . . . . . . . . . . . . . . . . . .xxv, 3091O PLAY AUDIO TRACK INDEX command. . . . . . . . . . . . . . . . . . . . .xxv, 3105O PLAY AUDIO(10) command. . . . . . . . . . . . . . . . . . . . . . xxv, 307, 3083O PLAY AUDIO(12) command. . . . . . . . . . . . . . . . . . . . . . . . .xxv, 308,O Plist bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183, 184,O PMI bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162, 182, 313,O POSITION ERROR RELATED TO TIMING. . . . . . . . . . . . . . . . . . . .132, 432,O position function field . . . . . . . . . . . . . . . . . . . . . . . . . . 347,O POSITION PAST BEGINNING OF MEDIUM . . . . . . . . . . . . . . . . . . .132, 432,O POSITION PAST END OF MEDIUM . . . . . . . . . . . . . . . . . . . . . .132, 4325O POSITION TO ELEMENT command . . . . . . . . . . . . . . . . . . . . .xxvii, 387 O POSITIONING ERROR DETECTED BY READ OF MEDIUM. . . . . . . . . . . . . .132, 430 O post error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223, 271 O POWER ON, RESET, OR BUS DEVICE RESET OCCURRED . . . . . . . . . . . . .132, 431,O POWER-ON OR SELF-TEST FAILURE (SHOULD USE 40 NN). . . . . . . . . . . .132, 432-O Power-On to Selection Time. . . . . . . . . . . . . . . . . . . . . .36, 37, 50 O PPC bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111RO PRA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .362, 363AO PRE-FETCH command . . . . . . . . . . . . . . . . . . . . . . . . . .xxiii, 178iO prevent . . . . xxiii, 27, 51, 65, 108, 161, 163-165, 168, 179, 189, 241, 254,  ,                 268, 295, 305, 359, 383, 436O PREVENT ALLOW MEDIUM REMOVAL command. . . . . . . . . . . . . . xxiii, 161, 1796O prevent bit . . . . . . . . . . . . . . . . . . . . . . . . .164, 179, 189, 2547O primary defect list . . . . . . . . . . . . . . . .132, 169, 173, 183, 184, 431TO PRIMARY DEFECT LIST NOT FOUND . . . . . . . . . . . . . . . . . . . . .132, 431RO primary volume tag. . . . . . . . . . . . . . . . . . . . . . 382, 391-395, 402AO primary volume tag information field. . . . . . . . . . . . . . . . . . . . 391 O PRINT command . . . . . . . . . . . . . . . . . . . . . xxiv, 276-278, 283, 284 O printer devices . . . . . . . xxiv, xxx, 123, 124, 273, 274, 277, 279, 280, 285 O Printer Options Page. . . . . . . . . . . . . . . . . . . . .277, 278, 280, 282 O priority field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97, 211,O product identification field. . . . . . . . . . . . . . . . . . . . . . . . 108,O product serial number field . . . . . . . . . . . . . . . . . . . . . . . . 159 O progress indication field . . . . . . . . . . . . . . . . . . . . . . . . . 126,P PS bit. . . . . 113, 115, 149, 173, 210, 214, 217, 220-222, 229, 231, 281, 282, :                 285, 328-330, 336, 354, 378, 405, 407, 409O PSUM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .269, 270,O PVolTag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391-395(O QErr bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 O queue algorithm modifier field. . . . . . . . . . . . . . . . . . . . . . . 150 O queue error management. . . . . . . . . . . . . . . . . . . . . . . . . 85, 150 O QUEUE FULL status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83-85 O queue tag . . . . . . . xxi, 4, 51, 55, 57, 60, 61, 63, 64, 77, 83-87, 150, 151eO queued I/O process. . . . . . . . . . . . . . . . . . . . . . . . 4, 58, 85, 86eO RAENP bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151dO RAM FAILURE (SHOULD USE 40 NN). . . . . . . . . . . . . . . . . . . . .132, 432lO RANDOM POSITIONING ERROR. . . . . . . . . . . . . . . . . . . . . . . .132, 430 O RAREA bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207nO RBO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252, 266, 267fO RC bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223fO RCD bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 O READ BLOCK LIMITS command . . . . . . . . . . . . . . . . . xxiv, 246, 248, 259nO READ BUFFER command . . . . . . . . . . . . . . . . . . xxi, 118, 119, 136, 137eO read cache disable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 O READ CAPACITY command . . . . . . . . . . . . . . . . xxiii, 161, 182, 184, 313fO READ CD-ROM CAPACITY command. . . . . . . . . . . . . . . . .xxv, 299, 300, 313eO read continuous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 O READ DEFECT DATA(10) command. . . . . . . . . . . . . . . . . . . . . . . . 364 O READ DEFECT DATA(12) command. . . . . . . . . . . . . . . . . . . . . xxvi, 3641O READ ELEMENT STATUS command . . . . . . . . xxvii, 381, 382, 385, 388, 389, 397,O read exclusive. . . . . . . . . . . . . . . . . . . . . . . . . . . . .190, 1917O READ GENERATION command . . . . . . . . . . . . . . . . . . . . . . . xxvi, 3668O READ HEADER command . . . . . . . . . . . . . . . . . . . . . . . . . .xxv, 3143O read inhibit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1973O READ LONG command . . . . . . . . . . . . . . . . . . . . . . . xxiii, 185, 204UO READ PAST BEGINNING OF MEDIUM . . . . . . . . . . . . . . . . . . . . .132, 432HO READ PAST END OF MEDIUM . . . . . . . . . . . . . . . . . . . . . . . .132, 432MO READ POSITION command . . . . . . . . . . . . . . . . . . . . . .xxiv, 239, 249TO READ RETRIES EXHAUSTED. . . . . . . . . . . . . . . . . . . . . . . . .132, 430 O READ REVERSE command. . . . . . . . . . . . . . . . . . . . . . . . . xxiv, 251 O read shared . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .190, 191 O READ SUB-CHANNEL command. . . . . . . . . . . . . . . . . . . . . xxv, 300, 316 O READ TOC command. . . . . . . . . . . . . . . . . . . . . . . . . xxv, 298, 323oO READ(10) command. . . . . . . . . . . . . . . . . . . xxiii, 180, 181, 202, 364EO READ(12) command. . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi, 364NO Read-Write Error Recovery Page. . . xxiii, xxiv, 203, 210, 222, 231, 240, 266,  ,                                     270, 377O ready AEN permission. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1519O REASSIGN BLOCKS command . . . . . . . .xxiii, 162, 165, 170, 186, 187, 223, 358 O RECEIVE command . . . . . . . . . . . . . . . . . . . . . . . xxv, 287-289, 2926O RECEIVE DIAGNOSTIC RESULTS command. xxii, 92, 121, 134, 135, 138, 139, 206, 2071M reconnect . . . . 3, xxii, 4, 43, 59-62, 64, 79, 82, 84, 144, 149, 152, 210, 6=                   265, 280, 287, 327, 353, 377, 411, 412, 419iO RECORD NOT FOUND. . . . . . . . . . . . . . . . . . . . . . . . . . . .132, 430 O RECORDED ENTITY NOT FOUND . . . . . . . . . . . . . . . . . . . . . . .132, 430tO recover buffer order. . . . . . . . . . . . . . . . . . . . . . . . . . . . 267 O RECOVER BUFFERED DATA command . . . . . . . . . . xxiv, 240, 252, 267, 276, 278tO RECOVERED DATA - DATA AUTO-REALLOCATED. . . . . . . . . . . . . . . . .132, 430eO RECOVERED DATA - RECOMMEND REASSIGNMENT . . . . . . . . . . . . . . . .132, 430eO RECOVERED DATA - RECOMMEND REWRITE. . . . . . . . . . . . . . . . . . .132, 430aO RECOVERED DATA USING PREVIOUS SECTOR ID . . . . . . . . . . . . . . . .132, 430tO RECOVERED DATA WITH CIRC. . . . . . . . . . . . . . . . . . . . . . . .132, 430 O RECOVERED DATA WITH ERROR CORRECTION & RETRIES APPLIED. . . . . . . . .132, 430 O RECOVERED DATA WITH ERROR CORRECTION APPLIED. . . . . . . . . . . . . .132, 430 O RECOVERED DATA WITH L-EC. . . . . . . . . . . . . . . . . . . . . . . . . . 132 O RECOVERED DATA WITH NEGATIVE HEAD OFFSET. . . . . . . . . . . . . . . .132, 430 O RECOVERED DATA WITH NO ERROR CORRECTION APPLIED . . . . . . . . . . . .132, 430 O RECOVERED DATA WITH POSITIVE HEAD OFFSET. . . . . . . . . . . . . . . .132, 430 O RECOVERED DATA WITH RETRIES . . . . . . . . . . . . . . . . . . . . . .132, 430 O RECOVERED DATA WITH RETRIES AND/OR CIRC APPLIED . . . . . . . . . . . .132, 430 O RECOVERED DATA WITHOUT ECC - DATA AUTO-REALLOCATED. . . . . . . . . . .132, 430,O RECOVERED DATA WITHOUT ECC - RECOMMEND REASSIGNMENT . . . . . . . . . .132, 4305O RECOVERED DATA WITHOUT ECC - RECOMMEND REWRITE. . . . . . . . . . . . .132, 430 O RECOVERED ERROR . . . . . 80, 122, 125, 128, 142, 145, 166, 173, 184, 224-227,  K                           230, 240, 247, 251, 259, 261, 294, 304, 331-335,  '                           358, 370, 378tO RECOVERED ID WITH ECC . . . . . . . . . . . . . . . . . . . . . . . . .132, 431lO REFERENCE POSITION FOUND. . . . . . . . . . . . . . . . . . . . . . . .131, 429eP RelAdr bit. . . . . . . . 107, 177, 178, 181, 182, 185, 193, 199, 200, 202-205, E                           360, 362, 363, 366, 367, 369, 371, 372, 374tO RELEASE command . . . . . . . . . . . . . . . . .xxiii, xxvii, 187-190, 398-400tO RELEASE RECOVERY. . . . . . . . . . . . . . . . . . . . . . . 3, 41, 55, 64, 83tO RELEASE UNIT command. . . . . . . . . . . . . . . . . . . . . . .xxiv, 253, 254tO removable . . . . . . . 81, 88, 92, 106, 128, 161, 162, 167, 219, 357, 381, 410SO report early-warning. . . . . . . . . . . . . . . . . . . . . . . . . . . . 267 O report log exception condition. . . . . . . . . . . . . . . . . . . . . . . 150 O report setmarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267iO report updated block read . . . . . . . . . . . . . . . . . . . . . . .370, 378iO REPOSITION ERROR. . . . . . . . . . . . . . . . . . . . . . . . . . . .132, 432IO REQUEST SENSE command . .xxii, 41, 67, 80, 82, 88, 92, 95, 122, 123, 127, 156, i?                          169, 193, 194, 287, 302, 339, 363, 412 O request to send . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286,O REQUEST VOLUME ELEMENT ADDRESS command. . . . . . . . . . .xxvii, 396, 401, 402 O RESELECTION Phase . . . . . . . . . . . . 4, 34, 38, 41-44, 50, 57, 61, 86, 421 O RESERVATION CONFLICT status . . . . . . . .164, 169, 189-192, 254, 255, 399-401,O reservation identification field. . . . . . . . . . . . . . . . . . . . . . 189xO reservation type field. . . . . . . . . . . . . . . . . . . . . . . . . . . 190 O RESERVE command . . . . xxiii, xxvii, 112, 165, 188-192, 254, 255, 397, 399-401 O RESERVE UNIT command. . . . . . . . . . . . . . . . . . . . . . . xxiv, 253-255 O reserved area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207,P reset condition . . . .3, 33, 38, 41, 47, 49-52, 59, 65, 67-69, 76, 79, 80, 82, O                        83, 88, 95, 108, 112, 116, 117, 179, 189-191, 254, 264,  $                        399, 400, 401O Reset Hold Time . . . . . . . . . . . . . . . . . . . . . . . . . . .36, 38, 51 O Reset to Selection Time . . . . . . . . . . . . . . . . . . . . . . .36, 38, 51 O RESTORE POINTERS. . . . . . . . . . . . . . . . . . .54, 55, 57, 60, 62, 65, 78FO resume bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306UO retain bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278nO reverse scan direction. . . . . . . . . . . . . . . . . . . . . . . . . . . 362DO REW . . . . . . . . . . . . . . . . . . . . . . 247, 257-259, 261, 266-268, 272 O REWIND command. . . . . . . . . . . . . . . . . . . . . . . .xxiv, 81, 236, 255EO REZERO UNIT command . . . . . . . . . . . . . . . . . . . . . . xxiii, 165, 192LO RIBBON, INK, OR TONER FAILURE . . . . . . . . . . . . . . . . . . . . .132, 431eO RIF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .344, 346 O Rigid Disk Drive Geometry Page. . . . . . . . . . . . . . . . . . . . xxiv, 229 O RLEC bit. . . . . . . . . . . . . . . . . . . . . . . . . . .142, 143, 145, 150 O RMB bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106,O rotate bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409 O ROUNDED PARAMETER . . . . . . . . . . . . . . . . . . . . . . . . .81, 132, 432 O RPL . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132, 229, 230, 4331O RPL STATUS CHANGE . . . . . . . . . . . . . . . . . . . . . . . . 132, 230, 4331O RSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362 O RSmk. . . . . . . . . . . . . . . . . . . 102, 123, 247, 252, 256-258, 266, 267 O RTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .285, 286 O RUBR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378 O save bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .932O SAVE DATA POINTER . . . . . . . . . . . . . . . . . . . .52, 54, 55, 59, 65, 782O save implemented. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 O save parameters . . . . . . . . . . . . . . . . . . . . . . . . . 109, 111, 219 O SavImp bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 O SAVING PARAMETERS NOT SUPPORTED . . . . . . . . . . . . . . . . . 116, 132, 432 O SCAN command. . . . . . . . . . . . . . . . .xxvi, 293, 341, 350, 358, 362, 3632O SCAN HEAD POSITIONING ERROR . . . . . . . . . . . . . . . . . . . . . .132, 433SO scanner devices . . . . . . . . . . . . . . .xxvi, xxx, 339, 340, 352, 353, 355VO SCSI ID . . . . . . . . . . . . . . . .5, 31, 34, 37, 42, 43, 82, 381, 421, 422EO SCSI PARITY ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . .132, 432uO SCSI Pointers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54uO SCSI TO HOST SYSTEM INTERFACE FAILURE . . . . . . . . . . . . . . . . .132, 433UO SCSI-2. . . . 2, xxvii, xxx, xxxi, 1, 5, 6, 9, 33, 43, 74, 79, 84, 91, 94, 95, u4               149, 187, 189, 421, 427, 429, 435, 439O SCTE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .282, 283 O SDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 O search argument descriptor. . . . . . . . . . . . . . . . . . . . . . .194, 195 O search argument length field. . . . . . . . . . . . . . . . . . . . . . . . 194 O sectors per track field . . . . . . . . . . . . . . . . . . . . . . . .214, 218 O SEEK(10) command. . . . . . . . . . . . . . . . . . . . . . . . . . .xxiii, 196 O segment descriptor. . . . . . . . . . . . . . . . . . . . xxi, 96-102, 123, 124 O segment number field. . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 O select data compression algorithm field . . . . . . . . . . . . . . . . . . 268 O select data partitions. . . . . . . . . . . . . . . . . . . . . . . . . . . 269 O SELECT OR RESELECT FAILURE. . . . . . . . . . . . . . . . . . . . . . .132, 432 O Selection Abort Time. . . . . . . . . . . . . . . . . . . . 36, 38, 43, 44, 422xO SELECTION Phase . . . . . . . . . . . . . 3, 34, 41-43, 50, 57, 60, 77, 86, 421 O Selection Time-out Delay. . . . . . . . . . . . . . . . . . . . .36, 38, 43, 44 O self test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92, 128 O send action code field. . . . . . . . . . . . . . . . . . . . . . 398, 401, 402 O SEND DIAGNOSTIC command . . . . . . . . . xxii, 92, 121, 134, 138, 139, 206-208 O SEND MESSAGE(10) command. . . . . . . . . . . . . . . . . . . . . . .xxvii, 416 O SEND MESSAGE(12) command. . . . . . . . . . . . . . . . . . . . . . .xxvii, 417 O SEND VOLUME TAG command . . . . . . . . . . . xxvii, 381, 382, 396-398, 401-403 O sense key field . . . . . . . . . . . . . . . . . . . . . . . . . . . .124, 125 O sense-key specific field. . . . . . . . . . . . . . . . . . . . . . . .125, 126 O sense-key specific valid. . . . . . . . . . . . . . . . . . . . . . . . . . 125 O SEQUENTIAL POSITIONING ERROR. . . . . . . . . . . . . . . . . . . . . .133, 432 P sequential-access devices . . .xxiv, xxx, 80, 97, 101, 102, 123, 124, 148, 233, ;                                239, 241, 242, 262, 263, 265 O Serial Printer Interface Page . . . . . . . . . . . . . . . . . . . . .280, 285 O SET LIMITS(10) command. . . . . . . . . . . . . . . . . . . . . . . . . . . 368 O SET LIMITS(12) command. . . . . . . . . . . . . . . . . . . . . . . . xxvi, 368 O SET WINDOW command. . . . . . . . . . . . . . . . . . . . . . . .xxvi, 345, 351 O SETMARK DETECTED. . . . . . . . . . . . . . . . . .133, 247, 252, 256, 257, 429 O SEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259, 261, 266-268 O SftRe bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51, 108 O SILI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246, 251, 252 O SIMPLE QUEUE TAG. . . . . . . . . . . . . . . . .55, 61, 63, 64, 77, 84-86, 150 O single bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42, 3432O SKSV bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125, 1262O SLEW AND PRINT command. . . . . . . . . . . . . . . . . xxiv, 276-278, 283, 2842O SLEW FAILURE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133, 432 O slew mode field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283TO slew value field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277EO SOCF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266-268uO soft sector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .218, 219UO SOTC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307-312, 327, 328 O source block length field . . . . . . . . . . . . . . . . . . . . . . . . . 101 O source logical block address field. . . . . . . . . . . . . . . . . . . . . 100 O source storage element address field. . . . . . . . . . . . . . . . . .393, 394 O source valid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393 O SP bit. . . . . . . . . . . . . . . . . . . . . . . . . 109, 111, 113, 116, 141 O SPACE command . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv, 256 O spanned data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 O speed field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv, 263 O SPINDLE SERVO FAILURE . . . . . . . . . . . . . . . . . . . . . . . . .133, 429 O SPINDLES NOT SYNCHRONIZED . . . . . . . . . . . . . . . . . . . . . . .133, 433 O SPINDLES SYNCHRONIZED . . . . . . . . . . . . . . . . . . . . . . . . .133, 433 O SpnDat bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 O SSEC bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 O SSN bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 O st. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405 O start . . . . . xxiii, 3, 54, 81, 108, 135, 161, 162, 164, 167, 168, 193, 195,  O                 198, 214, 215, 282, 283, 295, 305-307, 310, 311, 324, 338, 359,                  381, 435O start bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198tO start sector number . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215lO starting boundary field . . . . . . . . . . . . . . . . . . . . . . . . . . 221eO starting F field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 O starting index field. . . . . . . . . . . . . . . . . . . . . . . . . . . . 310 O starting M field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 O starting S field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 O starting track field. . . . . . . . . . . . . . . . . . . . . . . 310, 311, 323lN status. . . . . .3, xxi, xxv, xxvi, xxvii, xxx, 3, 5, 31, 33, 34, 37, 38, 41, M                  44, 45, 47-52, 54, 58-62, 65, 67, 71, 75-77, 80-89, 92, 95, oL                  98, 99, 101, 102, 104, 108-113, 115-117, 119, 122, 125-128,M                  131, 132, 134, 135, 137, 139, 140, 142, 143, 145, 149, 153, iN                  162, 164-166, 169, 170, 172-174, 176, 178, 181-185, 187-194, O                  197-200, 203-206, 209, 211, 214, 218, 219, 223-228, 230, 233, 3N                  238, 240, 243-247, 251-263, 267, 271, 276-278, 280, 283, 284,L                  287, 292, 293, 302-304, 306, 307, 309, 310, 312, 317, 318, O                  320, 321, 323, 328, 331-335, 339-342, 347-349, 351, 354, 358, SI                  360, 363, 367, 370-372, 374, 376-378, 381-386, 388-393,  E                  397-401, 407, 408, 411, 423, 429, 433, 435, 436, 438 O STATUS Phase. . . . . . . . . . . . . . . . . . . . . . 41, 48, 50, 76, 77, 423 O step count truncate enable. . . . . . . . . . . . . . . . . . . . . . . . . 283 O step pulse per cylinder . . . . . . . . . . . . . . . . . . . . . . . . . . 215 O stop bit length field . . . . . . . . . . . . . . . . . . . . . . . . . . . 286 O stop format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 O stop on consecutive filemarks . . . . . . . . . . . . . . . . . . . . . . . 267 O stop on track crossing. . . . . . . . . . . . . . . . . . . . . . 310, 311, 328 O STOP PRINT command. . . . . . . . . . . . . . . . . . . . . . . . . . xxiv, 2784O storage element . . . . . xxvii, 379, 381, 384, 386, 388, 392-395, 405-407, 410 O STPF bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 O stream selection field. . . . . . . . . . . . . . . . . . . . . . . . . 414-417 O sub Q bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .316, 317 O sub-channel data format field . . . . . . . . . . . . . . . .316, 317, 321, 322 O sub-channel data header . . . . . . . . . . . . . . . . . . . . . 317, 320, 321 O sub-channel data length field . . . . . . . . . . . . . . . . . . . . . . . 317 O SubQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 O supplied format field . . . . . . . . . . . . . . . . . . . . . . . . .206, 207 O Supported Diagnostic Pages. . . . . . . xxii, 139, 206, 262, 279, 325, 352, 404 O Supported Log Pages . . .xxii, 143, 145, 146, 208, 262, 279, 325, 353, 404, 418 O supported page list field . . . . . . . . . . . . . . . . . . . . 140, 146, 158 O Supported Vital Product Data Pages. . . . . . . . . . . . . . . .xxii, 155, 158 O suppress incorrect length indicator . . . . . . . . . . . . . . . . . . . . 246 O SURF bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 O surface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219, 355 O SValid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392-395 O SYNCHRONIZE BUFFER command. . . . . . . . . . . . . . . . . . . .xxiv, 278, 284 O SYNCHRONIZE CACHE command . . . . . . . . . . . . . . . . .xxiii, 165, 198, 199 O SYNCHRONOUS DATA TRANSFER ERROR . . . . . . . . . . . . . . . . . . . .133, 431 O SYNCHRONOUS DATA TRANSFER REQUEST . . . . . . . . . . . . . xxi, 55, 57, 65, 82 O SYSTEM RESOURCE FAILURE . . . . . . . . . . . . . . . . . . . . . . . .133, 433 O TAPE LENGTH ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . .133, 431 O TAPE OR ELECTRONIC VERTICAL FORMS UNIT NOT READY. . . . . . . . . . . .133, 432 O TAPE POSITION ERROR AT BEGINNING-OF-MEDIUM. . . . . . . . . . . . . . .133, 432 O TAPE POSITION ERROR AT END-OF-MEDIUM. . . . . . . . . . . . . . . . . .133, 432 O target certification list . . . . . . . . . . . . . . . . . . . . . . . . . 170 O TARGET OPERATING CONDITIONS HAVE CHANGED. . . . . . . . . . . . . . . .133, 432 O target routine. . . . . . . . . . . . . . .4, 5, 57-60, 63, 80, 82, 84, 91, 290 O target save disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 O TB bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223, 271 O TCVal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317, 319, 322 O TERMINATE I/O PROCESS . . . . . . . . . . . . . . . . . . . 55, 67, 77, 79, 107 O TEST UNIT READY command . . . . . . . . . . . .xxii, 82, 92, 135, 161, 287, 339 O third party . . . . . . . . . . . . . .96, 112, 187, 189, 191, 253-255, 398-400LO third party reservation . . . . . . . . . . . . . . . . . . .112, 191, 254, 400,O THRESHOLD CONDITION MET . . . . . . . . . . . . . . . . . . . . . 133, 142, 433 O threshold field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345 O threshold met criteria. . . . . . . . . . . . . . . . . . . . . . . . xxii, 142 O THRESHOLD PARAMETERS NOT SUPPORTED. . . . . . . . . . . . . . . . . . .133, 431 O TOO MANY WINDOWS SPECIFIED. . . . . . . . . . . . . . . . . . . . . . .133, 431 O track code valid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319 O TRACK FOLLOWING ERROR . . . . . . . . . . . . . . . . . . . . . . . . .133, 429 O track number field. . . . . . . . . . . . . . . . . . . . . . . . . . .317, 324,O track relative CD-ROM address field . . . . . . . . . . . . . . . . . . . . 319 O track skew factor field . . . . . . . . . . . . . . . . . . . . . . . . . . 218 O TRACKING SERVO FAILURE. . . . . . . . . . . . . . . . . . . . . . . . .133, 429 O tracks per zone field . . . . . . . . . . . . . . . . . . . . . . . . .217, 218 O transfer block. . . . . . . . . . . . . . . . . . . . . . . . . . .223-227, 2716N Transfer Length . . 54, 67, 72-74, 137, 148, 178, 180-182, 185, 200-204, 210, M                     212, 241, 246, 247, 251-253, 259-262, 272, 275-277, 283,  O                     290, 303, 307, 308, 311, 312, 328, 343, 349-351, 360, 361,  /                     364, 368, 372-374, 416, 417 O Transfer Period . . . . . . . . . . . . . . . . . . .36, 38, 45-47, 65, 66, 425 O Translate Address Page - RECEIVE DIAGNOSTIC . . . . . . . . . . xxiii, 206, 207 O Translate Address Page - SEND DIAGNOSTIC. . . . . . . . . . . . . . .xxiii, 206 O translate format field. . . . . . . . . . . . . . . . . . . . . . . . .206, 208 O translated address field. . . . . . . . . . . . . . . . . . . . . . . . . . 208 O transport element address field . . . . . . . . . . . . . . . . . . . .380, 407 O transport geometry descriptor . . . . . . . . . . . . . . . . . . . . . . . 409 O true ready. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214, 215RO TSD bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109, 141 O UAAENP bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 O UNABLE TO ACQUIRE VIDEO . . . . . . . . . . . . . . . . . . . . . . . .133, 433 O UNABLE TO RECOVER TABLE-OF-CONTENTS . . . . . . . . . . . . . . . . . .133, 433 O unexpected disconnect . . . . . . . . . .3, 5, 47, 49, 50, 57, 60, 76, 122, 126 O unexpected reselection. . . . . . . . . . . . . . . . . . . . . . . . . . . .82 L UNIT ATTENTION. . . . . . 51, 59, 79, 81, 82, 85, 88, 89, 94, 95, 104, 110, L                           112, 128, 138, 142, 148, 150, 151, 166, 188, 190, @                           230, 240, 253, 264, 294, 304, 358, 400O unit attention AEN permission . . . . . . . . . . . . . . . . . . . . . . . 151 O unit off-line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 O Unit Serial Number Page . . . . . . . . . . . . . . . . . . . . .xxii, 155, 159 O UnitOfl bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 O UNLOAD TAPE FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . .133, 433dO UNRECOVERED READ ERROR. . . . . . . . . . 133, 166, 239-241, 294, 304, 358, 430 O UNRECOVERED READ ERROR - AUTO REALLOCATE FAILED . . . . . . . . . . . .133, 430 O UNRECOVERED READ ERROR - RECOMMEND REASSIGNMENT . . . . . . . . . . . .133, 430 O UNRECOVERED READ ERROR - RECOMMEND REWRITE THE DATA . . . . . . . . . .133, 430 O UNSUCCESSFUL SOFT RESET . . . . . . . . . . . . . . . . . . . . . . . .133, 432 O UPDATE BLOCK command. . . . . . . . . . . . . . . . . .xxvi, 369, 370, 376, 378 O UPDATED BLOCK READ. . . . . . . . . . . . . . . . . . . . . .133, 370, 378, 433iO VCBP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280, 281aO VCBS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280, 281tO vendor identification field . . . . . . . . . . . . . . . . . . . . . . . . 108 O verification length field . . . . . . . . . . . . . . . . . . . . . . . . . 200 O verify correction span field. . . . . . . . . . . . . . . . . . . . . . . . 231 O Verify Error Recovery Page. . . . . . . . . . . . xxiv, 203, 210, 231, 327, 377 O verify recovery time limit field. . . . . . . . . . . . . . . . . . . . . . 231 O verify retry count field. . . . . . . . . . . . . . . . . . . . . .224-226, 231 O VERIFY(10) command. . . . . . . . . . . . . . . . . . .xxvi, 370, 371, 373, 374IO VERIFY(12) command. . . . . . . . . . . . . . . . . . . . . . . .xxvi, 371, 374 O vertical forms unit . . . . . . . . . . . . . . . . . . . . . 133, 281-283, 432 O VES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280, 281 O VFU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv, 281 O VFU control bit polarity. . . . . . . . . . . . . . . . . . . . . . . . . . 281 O VFU control bit select. . . . . . . . . . . . . . . . . . . . . . . . . . . 281,O VFU extended skip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2812O VIDEO ACQUISITION ERROR . . . . . . . . . . . . . . . . . . . . . . . .133, 4334O Vital Product Data Parameters . . . . . . . . . . . . . . . . . . . . . .7, 1549O VolTag. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388, 396, 3971O volume identification field . . . . . . . . . . . . . . . . . . . . . . . . 3822O volume identification template field. . . . . . . . . . . . . . . . . . . . 4030O VOLUME OVERFLOW . . . . . . . . . . . . . . . . . . . . .129, 240, 259-262, 2671O volume sequence number field. . . . . . . . . . . . . . . . . . . . . .382, 4030O volume tag. . . . . . . . . . .xxvi, xxvii, 381-383, 388, 391-398, 401-403, 4380O wait bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3412O WBS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362 O WCE bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 O WIDE DATA TRANSFER REQUEST. . . . . . . . . . . . . . . . . .46, 55, 57, 67, 68 O window length field . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345 O window width field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345 O WP bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209, 263, 376 O WRITE AND VERIFY(10) command. . . . . . . . . . . . . . . . . . .xxvi, 373, 374 O WRITE AND VERIFY(12) command. . . . . . . . . . . . . . . . . . . . . xxvi, 374 O WRITE APPEND ERROR. . . . . . . . . . . . . . . . . . . . . . . . . . .133, 432 O WRITE APPEND POSITION ERROR . . . . . . . . . . . . . . . . . . . . . .133, 4327O WRITE BUFFER command. . . . . . . . . . . . . . . . . .xxii, 118, 119, 136, 138 O write cache enable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 O WRITE ERROR . . xxiii, xxiv, 124, 133, 203, 210, 222, 231, 238, 240, 241, 266,  "                 270, 271, 377, 430O WRITE ERROR - AUTO REALLOCATION FAILED. . . . . . . . . . . . . . . . .133, 430 O WRITE ERROR RECOVERED WITH AUTO REALLOCATION. . . . . . . . . . . . . .133, 430 O write exclusive . . . . . . . . . . . . . . . . . . . . . . . . . . . .190, 191 O WRITE FILEMARKS command . . . . . . . . xxiv, 238, 244, 255, 259, 261, 262, 268 O write inhibit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 O WRITE LONG command. . . . . . . . . . . . . . . . . . . . . . . . . .xxiii, 204,O write precompensation field . . . . . . . . . . . . . . . . . . . 214, 215, 230 O write protect . . . . . . . . . . . . . . . . . . . . . .81, 132, 209, 263, 433 O WRITE PROTECTED . . . . . . . .133, 166, 209, 233, 240, 263, 294, 358, 376, 431 O write retention priority field. . . . . . . . . . . . . . . . . . . . . . . 211 O WRITE SAME command. . . . . . . . . . . . . . . . . . . . . . . . . .xxiii, 205 O write setmark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 O WRITE(10) command . . . . . . . . . . . . . . . .xxiii, xxvi, 201-203, 372, 373 O WRITE(12) command . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi, 373 O written block search. . . . . . . . . . . . . . . . . . . . . . . . . . . . 362 O WSmk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 O X-axis resolution field . . . . . . . . . . . . . . . . . . . . . . . . . . 345 O X-axis upper left field . . . . . . . . . . . . . . . . . . . . . . . . . . 345xO Y-axis resolution field . . . . . . . . . . . . . . . . . . . . . . . . . . 345 O Y-axis upper left field . . . . . . . . . . . . . . . . . . . . . . . . . . 345     