O  WORKING                                                                 X3T9.2 O  DRAFT                                                             Project 375D    O                                                                    Revision 10L O                                                                        7-SEP-93 0       NOTE:  This file is provided to facilitate-       review and comments on the draft SCSI-2 3       standard.  It is NOT intended as a substitute 2       for obtaining a paper copy of this document.0       The figures and formatting information are1       omitted.  Please contact Global Engineering 3       Documents at (800) 854-7179 or (303) 792-2181        to obtain a paper copy.            Information technology - $  Small Computer System Interface - 2         
  Secretariat: 8  Computer & Business Equipment Manufacturers Association         B  This is a draft proposed American National Standard of AccreditedH  Standards Committee X3.  As such this is not a completed standard.  TheJ  X3T9 Technical Committee may modify this document as a result of commentsC  received during the public review process and the approval of this G  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 technicalH  committees, and their associated task groups to reproduce this documentJ  for the purposes of X3 and ISO standardization activities without furtherD  permission, provided this notice is included.  All other rights areD  reserved.  Any commercial or for-profit use is strictly prohibited.                                 A  ASC X3T9.2 Technical Editor:                  Lawrence J. Lamers A                                                Maxtor Corporation 6                                                MS A697E                                                150 River Oaks Parkway G                                                San Jose, CA  95134-1983 2                                                USAF                                                Telephone: 408-432-3889F                                                Facsimile: 408-432-3833M                                                Email: larry_lamers@maxtor.com          ?                                                Reference number D                                                ISO/IEC 9316-1 : 199xA                                                ANSI X3.131 - 199x O                                                Printed November, 7, 1993 3:39pm      POINTS OF CONTACT:    ?  X3T9.2 Chair                                 X3T9.2 Vice-Chair :  John B. Lohmeyer                             I. Dal AllanJ  NCR Corporation                              ENDL                        F  1635 Aeroplaza Drive                         14426 Black Walnut CourtA  Colo Spgs, CO 80916                          Saratoga, CA  95070    I  Tel:   (719) 573-3362                        Tel:         (408) 867-6630 I  Fax:   (719) 597-8225                        Fax:         (408) 867-2115 O  Email: john.lohmeyer@ftcollinsco.ncr.com     Email:        2501752@mcimail.com      X3 Secretariat   Lynn Barra #  Administrator Standards Processing G  X3 Secretariat                               Telephone:   202-626-5738 G  1250 Eye Street, NW   Suite 200              Facsimile:   202-638-4922   Washington, DC   20005      SCSI Reflector 9  Internet address for subscription to the SCSI reflector:   scsiadm@wichitaks.ncr.com6  Internet address for distribution via SCSI reflector:  scsi@wichitaks.ncr.com      SCSI Bulletin Board
  719-574-0424      Document DistributionK  Global Engineering                            Telephone:  303-792-2181 or  G  15 Inverness Way East                                     800-854-7179 G  Englewood, CO   80112-5704                    Facsimile:  303-792-2192       )                                  ABSTRACT    K  The SCSI protocol is designed to provide an efficient peer-to-peer I/O bus A  with up to 16 devices, including one or more hosts.  Data may be ?  transferred asynchronously at rates that only depend on device K  implementation and cable length.  Synchronous data transfers are supported H  at rates up to 10 mega-transfers per second.  With the 32-bit wide dataK  transfer option, data rates of up to 40 megabytes per second are possible.    D  SCSI-2 includes command sets for magnetic and optical disks, tapes,>  printers, processors, CD-ROMs, scanners, medium changers, and  communications devices.      .                               PATENT STATEMENT   H  The developers of this standard have requested that holder's of patentsG  that may be required for the  implementation of the standard, disclose G  such patents to the publisher.  However neither the developers nor the H  publisher have undertaken a patent search in order to identify which if(  any patents may apply to this standard.   F  No position is taken with respect to the validity of any claim or anyB  patent rights that may have been disclosed.  Details of submittedJ  statements may be obtained from the publisher concerning any statement ofA  patents and willingness to grant a license under these rights on D  reasonable and nondiscriminatory terms and conditions to applicants#  desiring to obtain such a license.         Document Status   8  The following are the changes from revision 10k to 10l.   N  1.     Page 3, clause 3, move the sentence beginning "For the purposes" after#         the title to subclause 3.1.    N  2.     Pages 3 to 5, clause 3, definitions should not begin with phrases such%         as "This term refers to" etc.    G  3.     Page 8, clause 5, remove the full stop after the clause number.    C  4.     Page 8, subclause 5.2.1, line 1, replace "meters" with "m".    D  5.     In the Introduction, item c) under the list of new low-levelL         requirements should read:  "The arbitration delay was increased from         2.2 to 2.4 us"   J  6.     In 4.1 Overview, the last line of the fifth paragraph should read:A         "are contending and can be completed in less than 10 us."    L  7.     In 8.3.3.2 Disconnect-reconnect page, there are three occurrences ofJ         100 ms being substituted for 100 microsecond.  These should all beE         changed to 100 us.  The corrected lines should read: "The bus J         inactivity limit field indicates the maximum time in 100 us ...". M         "The disconnect time limit field indicates the minimum time in 100 us N         ...".  "The connect time limit field indicates the maximum time in 100         us ..."    N  8.     In 9.3.3.2 Flexible disk page, the paragraph describing the drive stepM         rate should begin: "The drive step rate field specifies the step rate          in units of 100 us."   K  9.     In 12.2.2, paragraph 7, the reference is to Table 65, not 8.2.14.1.    K  10.       The Foreword and Introduction clauses were modified to correctly &            reflect the ANSI/ISO style.   1  11.       Updated the Vendor ID list in Annex E.      ERRATA    H  The following errors have been reported.  Due to the constraints of theJ  standards process these errors cannot be corrected within the body of theG  document.  The X3T9.2 committee plans to issue errata to correct these   items.    J  1.     An error exists in Table 161.  The Head load bit pattern should be         P011 not P000.   	  Contents N                                                                           PageN  Foreword. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxix   N  Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxx   N  1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .   1   N  2 Normative references. . . . . . . . . . . . . . . . . . . . . . . . . .   2   N  3 Definitions, symbols and abbreviations. . . . . . . . . . . . . . . . .   3N     3.1 Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . .   3N     3.2 Symbols and abbreviations. . . . . . . . . . . . . . . . . . . . .   5   N  4 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .   6N     4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . .   6N     4.2 Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . .   7   N  5 Physical characteristics. . . . . . . . . . . . . . . . . . . . . . . .   9N     5.1 Physical description . . . . . . . . . . . . . . . . . . . . . . .   9N     5.2 Cable requirements   . . . . . . . . . . . . . . . . . . . . . . .   9N     5.2.1 Single-ended cable . . . . . . . . . . . . . . . . . . . . . . .   9N     5.2.2 Differential cable . . . . . . . . . . . . . . . . . . . . . . .  10N     5.2.3 Cable requirements for fast synchronous data transfer. . . . . .  10N     5.3 Connector requirements . . . . . . . . . . . . . . . . . . . . . .  10N     5.3.1 Non-shielded connector requirements. . . . . . . . . . . . . . .  10N     5.3.1.1 Non-shielded connector alternative 1 - A cable . . . . . . . .  10N     5.3.1.2 Non-shielded connector alternative 2 - A cable . . . . . . . .  11N     5.3.1.3 Non-shielded connector - B cable . . . . . . . . . . . . . . .  11N     5.3.2 Shielded connector requirements. . . . . . . . . . . . . . . . .  16N     5.3.2.1 Shielded connector alternative 1 - A cable . . . . . . . . . .  16N     5.3.2.2 Shielded connector alternative 2 - A cable . . . . . . . . . .  16N     5.3.2.3 Shielded connector - B cable . . . . . . . . . . . . . . . . .  16N     5.3.3 Connector contact assignments. . . . . . . . . . . . . . . . . .  21N     5.4 Electrical description . . . . . . . . . . . . . . . . . . . . . .  26N     5.4.1 Single-ended alternative . . . . . . . . . . . . . . . . . . . .  26N     5.4.1.1 Output characteristics . . . . . . . . . . . . . . . . . . . .  26N     5.4.1.2 Input characteristics. . . . . . . . . . . . . . . . . . . . .  26N     5.4.2 Differential alternative . . . . . . . . . . . . . . . . . . . .  27N     5.4.2.1 Output characteristics . . . . . . . . . . . . . . . . . . . .  27N     5.4.2.2 Input characteristics. . . . . . . . . . . . . . . . . . . . .  27N     5.4.3 Terminator power . . . . . . . . . . . . . . . . . . . . . . . .  27N     5.4.4 RESERVED lines . . . . . . . . . . . . . . . . . . . . . . . . .  30N     5.5 SCSI bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  31N     5.6 SCSI bus signals . . . . . . . . . . . . . . . . . . . . . . . . .  33N     5.6.1 Signal values. . . . . . . . . . . . . . . . . . . . . . . . . .  34N     5.6.2 OR-tied signals. . . . . . . . . . . . . . . . . . . . . . . . .  34N     5.6.3 Signal sources . . . . . . . . . . . . . . . . . . . . . . . . .  34N     5.7 SCSI bus timing. . . . . . . . . . . . . . . . . . . . . . . . . .  36N     5.7.1 Arbitration delay  . . . . . . . . . . . . . . . . . . . . . . .  36N     5.7.2 Assertion period . . . . . . . . . . . . . . . . . . . . . . . .  36N     5.7.3 Bus clear delay  . . . . . . . . . . . . . . . . . . . . . . . .  36N     5.7.4 Bus free delay . . . . . . . . . . . . . . . . . . . . . . . . .  37N     5.7.5 Bus set delay  . . . . . . . . . . . . . . . . . . . . . . . . .  37N     5.7.6 Bus settle delay . . . . . . . . . . . . . . . . . . . . . . . .  37N     5.7.7 Cable skew delay . . . . . . . . . . . . . . . . . . . . . . . .  37N     5.7.8 Data release delay . . . . . . . . . . . . . . . . . . . . . . .  37N     5.7.9 Deskew delay . . . . . . . . . . . . . . . . . . . . . . . . . .  37N     5.7.10 Disconnection delay . . . . . . . . . . . . . . . . . . . . . .  37N     5.7.11 Hold time . . . . . . . . . . . . . . . . . . . . . . . . . . .  37N     5.7.12 Negation period . . . . . . . . . . . . . . . . . . . . . . . .  37N     5.7.13 Power-on to selection time  . . . . . . . . . . . . . . . . . .  37N     5.7.14 Reset to selection time . . . . . . . . . . . . . . . . . . . .  38N     5.7.15 Reset hold time . . . . . . . . . . . . . . . . . . . . . . . .  38N     5.7.16 Selection abort time  . . . . . . . . . . . . . . . . . . . . .  38N     5.7.17 Selection time-out delay  . . . . . . . . . . . . . . . . . . .  38N     5.7.18 Transfer period . . . . . . . . . . . . . . . . . . . . . . . .  38N     5.8 Fast synchronous transfer option . . . . . . . . . . . . . . . . .  38N     5.8.1 Fast assertion period  . . . . . . . . . . . . . . . . . . . . .  38N     5.8.2 Fast cable skew delay  . . . . . . . . . . . . . . . . . . . . .  38N     5.8.3 Fast deskew delay  . . . . . . . . . . . . . . . . . . . . . . .  39N     5.8.4 Fast hold time . . . . . . . . . . . . . . . . . . . . . . . . .  39N     5.8.5 Fast negation period . . . . . . . . . . . . . . . . . . . . . .  39  9N  6 Logical characteristics . . . . . . . . . . . . . . . . . . . . . . . .  41N     6.1 SCSI bus phases. . . . . . . . . . . . . . . . . . . . . . . . . .  41N     6.1.1 BUS FREE phase . . . . . . . . . . . . . . . . . . . . . . . . .  41N     6.1.2 ARBITRATION phase. . . . . . . . . . . . . . . . . . . . . . . .  42N     6.1.3 SELECTION phase. . . . . . . . . . . . . . . . . . . . . . . . .  42N     6.1.3.1 SELECTION time-out procedure . . . . . . . . . . . . . . . . .  43N     6.1.4 RESELECTION phase. . . . . . . . . . . . . . . . . . . . . . . .  43N     6.1.4.1 RESELECTION    . . . . . . . . . . . . . . . . . . . . . . . .  43N     6.1.4.2 RESELECTION time-out procedure . . . . . . . . . . . . . . . .  44N     6.1.5 Information transfer phases. . . . . . . . . . . . . . . . . . .  44N     6.1.5.1 Asynchronous information transfer. . . . . . . . . . . . . . .  45N     6.1.5.2 Synchronous data transfer. . . . . . . . . . . . . . . . . . .  45N     6.1.5.3 Wide data transfer . . . . . . . . . . . . . . . . . . . . . .  46N     6.1.6 COMMAND phase. . . . . . . . . . . . . . . . . . . . . . . . . .  48N     6.1.7 Data phase . . . . . . . . . . . . . . . . . . . . . . . . . . .  48N     6.1.7.1 DATA IN phase. . . . . . . . . . . . . . . . . . . . . . . . .  48N     6.1.7.2 DATA OUT phase . . . . . . . . . . . . . . . . . . . . . . . .  48N     6.1.8 STATUS phase . . . . . . . . . . . . . . . . . . . . . . . . . .  48N     6.1.9 Message phase. . . . . . . . . . . . . . . . . . . . . . . . . .  48N     6.1.9.1 MESSAGE IN phase . . . . . . . . . . . . . . . . . . . . . . .  48N     6.1.9.2 MESSAGE OUT phase. . . . . . . . . . . . . . . . . . . . . . .  48N     6.1.10 Signal restrictions between phases. . . . . . . . . . . . . . .  49N     6.2 SCSI bus conditions. . . . . . . . . . . . . . . . . . . . . . . .  50N     6.2.1 Attention condition. . . . . . . . . . . . . . . . . . . . . . .  50N     6.2.2 Reset condition. . . . . . . . . . . . . . . . . . . . . . . . .  51N     6.2.2.1 Hard reset alternative . . . . . . . . . . . . . . . . . . . .  51N     6.2.2.2 Soft reset alternative . . . . . . . . . . . . . . . . . . . .  51N     6.3 SCSI bus phase sequences . . . . . . . . . . . . . . . . . . . . .  52N     6.4 SCSI pointers. . . . . . . . . . . . . . . . . . . . . . . . . . .  54N     6.5 Message system description . . . . . . . . . . . . . . . . . . . .  55N     6.6 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  58N     6.6.1 ABORT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  58N     6.6.2 ABORT TAG. . . . . . . . . . . . . . . . . . . . . . . . . . . .  58N     6.6.3 BUS DEVICE RESET . . . . . . . . . . . . . . . . . . . . . . . .  59N     6.6.4 CLEAR QUEUE. . . . . . . . . . . . . . . . . . . . . . . . . . .  59N     6.6.5 COMMAND COMPLETE . . . . . . . . . . . . . . . . . . . . . . . .  59N     6.6.6 DISCONNECT . . . . . . . . . . . . . . . . . . . . . . . . . . .  59N     6.6.7 IDENTIFY . . . . . . . . . . . . . . . . . . . . . . . . . . . .  60N     6.6.8 IGNORE WIDE RESIDUE. . . . . . . . . . . . . . . . . . . . . . .  61N     6.6.9 INITIATE RECOVERY. . . . . . . . . . . . . . . . . . . . . . . .  61N     6.6.10 INITIATOR DETECTED ERROR. . . . . . . . . . . . . . . . . . . .  62N     6.6.11 LINKED COMMAND COMPLETE . . . . . . . . . . . . . . . . . . . .  62N     6.6.12 LINKED COMMAND COMPLETE (WITH FLAG) . . . . . . . . . . . . . .  62N     6.6.13 MESSAGE PARITY ERROR. . . . . . . . . . . . . . . . . . . . . .  62N     6.6.14 MESSAGE REJECT. . . . . . . . . . . . . . . . . . . . . . . . .  62N     6.6.15 MODIFY DATA POINTER Message . . . . . . . . . . . . . . . . . .  63N     6.6.16 NO OPERATION. . . . . . . . . . . . . . . . . . . . . . . . . .  63N     6.6.17 Queue tag messages. . . . . . . . . . . . . . . . . . . . . . .  63N     6.6.17.1 HEAD OF QUEUE TAG . . . . . . . . . . . . . . . . . . . . . .  64N     6.6.17.2 ORDERED QUEUE TAG . . . . . . . . . . . . . . . . . . . . . .  64N     6.6.17.3 SIMPLE QUEUE TAG. . . . . . . . . . . . . . . . . . . . . . .  64N     6.6.18 RELEASE RECOVERY. . . . . . . . . . . . . . . . . . . . . . . .  64N     6.6.19 RESTORE POINTERS. . . . . . . . . . . . . . . . . . . . . . . .  65N     6.6.20 SAVE DATA POINTER . . . . . . . . . . . . . . . . . . . . . . .  65N     6.6.21 SYNCHRONOUS DATA TRANSFER REQUEST message . . . . . . . . . . .  65N     6.6.22 TERMINATE I/O PROCESS . . . . . . . . . . . . . . . . . . . . .  67N     6.6.23 WIDE DATA TRANSFER REQUEST message. . . . . . . . . . . . . . .  67   N  7 SCSI commands and status. . . . . . . . . . . . . . . . . . . . . . . .  71N     7.1 Command implementation requirements. . . . . . . . . . . . . . . .  71N     7.1.1 Reserved . . . . . . . . . . . . . . . . . . . . . . . . . . . .  71N     7.1.2 Operation code types . . . . . . . . . . . . . . . . . . . . . .  71N     7.2 Command descriptor block . . . . . . . . . . . . . . . . . . . . .  72N     7.2.1 Operation code . . . . . . . . . . . . . . . . . . . . . . . . .  73N     7.2.2 Logical unit number. . . . . . . . . . . . . . . . . . . . . . .  74N     7.2.3 Logical block address. . . . . . . . . . . . . . . . . . . . . .  74N     7.2.4 Transfer length. . . . . . . . . . . . . . . . . . . . . . . . .  74N     7.2.5 Parameter list length. . . . . . . . . . . . . . . . . . . . . .  74N     7.2.6 Allocation length. . . . . . . . . . . . . . . . . . . . . . . .  75N     7.2.7 Control field. . . . . . . . . . . . . . . . . . . . . . . . . .  75N     7.3 Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  76N     7.4 Command examples . . . . . . . . . . . . . . . . . . . . . . . . .  77N     7.4.1 Single command example . . . . . . . . . . . . . . . . . . . . .  77N     7.4.2 Disconnect example . . . . . . . . . . . . . . . . . . . . . . .  77N     7.4.3 Linked command example . . . . . . . . . . . . . . . . . . . . .  78N     7.5 Command processing considerations and exception conditions . . . .  79N     7.5.1 Programmable operating definition. . . . . . . . . . . . . . . .  79N     7.5.2 Incorrect initiator connection . . . . . . . . . . . . . . . . .  79N     7.5.3 Selection of an invalid logical unit . . . . . . . . . . . . . .  80N     7.5.4 Parameter rounding . . . . . . . . . . . . . . . . . . . . . . .  80N     7.5.5 Asynchronous event notification  . . . . . . . . . . . . . . . .  81N     7.5.6 Unexpected reselection . . . . . . . . . . . . . . . . . . . . .  82N     7.6 Contingent allegiance condition. . . . . . . . . . . . . . . . . .  82N     7.7 Extended contingent allegiance condition . . . . . . . . . . . . .  83N     7.8 Queued I/O processes . . . . . . . . . . . . . . . . . . . . . . .  84N     7.8.1 Untagged queuing . . . . . . . . . . . . . . . . . . . . . . . .  84N     7.8.2 Tagged queuing . . . . . . . . . . . . . . . . . . . . . . . . .  84N     7.8.3 Example of queued I/O process. . . . . . . . . . . . . . . . . .  86N     7.8.3.1 Typical sequences for tagged queuing . . . . . . . . . . . . .  86N     7.8.3.2 Example of tagged queuing. . . . . . . . . . . . . . . . . . .  86N     7.9  Unit attention condition. . . . . . . . . . . . . . . . . . . . .  88   N  8  All device types . . . . . . . . . . . . . . . . . . . . . . . . . . .  91N     8.1 Model for all device types . . . . . . . . . . . . . . . . . . . .  91N     8.1.1 SCSI addresses . . . . . . . . . . . . . . . . . . . . . . . . .  91N     8.1.1.1 SCSI device address. . . . . . . . . . . . . . . . . . . . . .  91N     8.1.1.2 Logical units. . . . . . . . . . . . . . . . . . . . . . . . .  91N     8.1.1.3 Target routines. . . . . . . . . . . . . . . . . . . . . . . .  91N     8.1.2 Commands implemented by all SCSI devices . . . . . . . . . . . .  91N     8.1.2.1 Using the INQUIRY command. . . . . . . . . . . . . . . . . . .  92N     8.1.2.2 Using the REQUEST SENSE command. . . . . . . . . . . . . . . .  92N     8.1.2.3 Using the SEND DIAGNOSTIC command. . . . . . . . . . . . . . .  92N     8.1.2.4 Using the TEST UNIT READY command. . . . . . . . . . . . . . .  92N     8.2 Commands for all device types. . . . . . . . . . . . . . . . . . .  92N     8.2.1 CHANGE DEFINITION command. . . . . . . . . . . . . . . . . . . .  93N     8.2.2 COMPARE command. . . . . . . . . . . . . . . . . . . . . . . . .  95N     8.2.3 COPY command . . . . . . . . . . . . . . . . . . . . . . . . . .  96N     8.2.3.1 Errors detected by the managing SCSI device. . . . . . . . . .  98N     8.2.3.2 Errors detected by a target. . . . . . . . . . . . . . . . . .  98N     8.2.3.3 COPY function code 00h and 01h . . . . . . . . . . . . . . . .  99N     8.2.3.4 COPY function code 02h . . . . . . . . . . . . . . . . . . . . 100N     8.2.3.5 COPY function code 03h . . . . . . . . . . . . . . . . . . . . 100N     8.2.3.6 COPY function code 04h . . . . . . . . . . . . . . . . . . . . 101N     8.2.3.7 Copies with unequal block lengths. . . . . . . . . . . . . . . 102N     8.2.4 COPY AND VERIFY command. . . . . . . . . . . . . . . . . . . . . 103N     8.2.5 INQUIRY command. . . . . . . . . . . . . . . . . . . . . . . . . 104N     8.2.5.1 Standard INQUIRY data. . . . . . . . . . . . . . . . . . . . . 105N     8.2.5.2 Vital product data . . . . . . . . . . . . . . . . . . . . . . 108N     8.2.6 LOG SELECT command . . . . . . . . . . . . . . . . . . . . . . . 109N     8.2.7 LOG SENSE command. . . . . . . . . . . . . . . . . . . . . . . . 111N     8.2.8 MODE SELECT(6) command . . . . . . . . . . . . . . . . . . . . . 112N     8.2.9 MODE SELECT(10) command. . . . . . . . . . . . . . . . . . . . . 114N     8.2.10 MODE SENSE(6) command . . . . . . . . . . . . . . . . . . . . . 115N     8.2.10.1 Current values. . . . . . . . . . . . . . . . . . . . . . . . 116N     8.2.10.2 Changeable values . . . . . . . . . . . . . . . . . . . . . . 116N     8.2.10.3 Default values. . . . . . . . . . . . . . . . . . . . . . . . 116N     8.2.10.4 Saved values. . . . . . . . . . . . . . . . . . . . . . . . . 116N     8.2.10.5 Initial responses . . . . . . . . . . . . . . . . . . . . . . 117N     8.2.11 MODE SENSE(10) command. . . . . . . . . . . . . . . . . . . . . 117N     8.2.12 READ BUFFER Command . . . . . . . . . . . . . . . . . . . . . . 118N     8.2.12.1 Combined header and data mode (000b). . . . . . . . . . . . . 118N     8.2.12.2 Vendor-specific mode (001b) . . . . . . . . . . . . . . . . . 119N     8.2.12.3 Data mode (010b). . . . . . . . . . . . . . . . . . . . . . . 119N     8.2.12.4 Descriptor mode (011b). . . . . . . . . . . . . . . . . . . . 119N     8.2.13 RECEIVE DIAGNOSTIC RESULTS command. . . . . . . . . . . . . . . 121N     8.2.14 REQUEST SENSE Command . . . . . . . . . . . . . . . . . . . . . 122N     8.2.14.1 Sense-key specific. . . . . . . . . . . . . . . . . . . . . . 125N     8.2.14.2 Deferred errors . . . . . . . . . . . . . . . . . . . . . . . 126N     8.2.14.3 Sense key and sense code definitions. . . . . . . . . . . . . 128N     8.2.15 SEND DIAGNOSTIC Command . . . . . . . . . . . . . . . . . . . . 134N     8.2.16 TEST UNIT READY Command . . . . . . . . . . . . . . . . . . . . 135N     8.2.17 WRITE BUFFER command. . . . . . . . . . . . . . . . . . . . . . 136N     8.2.17.1 Combined header and data mode (000b). . . . . . . . . . . . . 137N     8.2.17.2 Vendor-specific mode (001b) . . . . . . . . . . . . . . . . . 137N     8.2.17.3 Data mode (010b). . . . . . . . . . . . . . . . . . . . . . . 137N     8.2.17.4 Download microcode mode (100b). . . . . . . . . . . . . . . . 138N     8.2.17.5 Download microcode and save mode (101b) . . . . . . . . . . . 138N     8.3 Parameters for all device types. . . . . . . . . . . . . . . . . . 138N     8.3.1 Diagnostic parameters  . . . . . . . . . . . . . . . . . . . . . 138N     8.3.1.1 Supported diagnostic pages . . . . . . . . . . . . . . . . . . 139N     8.3.2 Log parameters . . . . . . . . . . . . . . . . . . . . . . . . . 140N     8.3.2.1 Buffer over-run/under-run page . . . . . . . . . . . . . . . . 143N     8.3.2.2 Error counter pages. . . . . . . . . . . . . . . . . . . . . . 144N     8.3.2.3 Last n error events page . . . . . . . . . . . . . . . . . . . 145N     8.3.2.4 Non-medium error page  . . . . . . . . . . . . . . . . . . . . 145N     8.3.2.5 Supported log pages. . . . . . . . . . . . . . . . . . . . . . 145N     8.3.3 Mode parameters. . . . . . . . . . . . . . . . . . . . . . . . . 146N     8.3.3.1 Control mode page. . . . . . . . . . . . . . . . . . . . . . . 149N     8.3.3.2 Disconnect-reconnect page. . . . . . . . . . . . . . . . . . . 152N     8.3.3.3 Peripheral device page . . . . . . . . . . . . . . . . . . . . 154N     8.3.4 Vital product data parameters. . . . . . . . . . . . . . . . . . 154N     8.3.4.1 ASCII implemented operating definition page. . . . . . . . . . 155N     8.3.4.2 ASCII information page . . . . . . . . . . . . . . . . . . . . 156N     8.3.4.3 Implemented operating definition page. . . . . . . . . . . . . 156N     8.3.4.4 Supported vital product data pages . . . . . . . . . . . . . . 158N     8.3.4.5 Unit serial number page. . . . . . . . . . . . . . . . . . . . 159   N  9 Direct-access devices . . . . . . . . . . . . . . . . . . . . . . . . . 161N     9.1 Direct-access device model . . . . . . . . . . . . . . . . . . . . 161N     9.1.1 Removable medium . . . . . . . . . . . . . . . . . . . . . . . . 161N     9.1.2 Logical blocks . . . . . . . . . . . . . . . . . . . . . . . . . 161N     9.1.3 Ready state. . . . . . . . . . . . . . . . . . . . . . . . . . . 162N     9.1.4 Initialization . . . . . . . . . . . . . . . . . . . . . . . . . 162N     9.1.5 Medium defects . . . . . . . . . . . . . . . . . . . . . . . . . 162N     9.1.6 Data cache . . . . . . . . . . . . . . . . . . . . . . . . . . . 163N     9.1.7 Reservations . . . . . . . . . . . . . . . . . . . . . . . . . . 164N     9.1.8 Seek and rezero. . . . . . . . . . . . . . . . . . . . . . . . . 165N     9.1.9 Notched drives . . . . . . . . . . . . . . . . . . . . . . . . . 165N     9.1.10 Rotational position locking . . . . . . . . . . . . . . . . . . 165N     9.1.11 Relative addressing . . . . . . . . . . . . . . . . . . . . . . 165N     9.1.12 Error reporting . . . . . . . . . . . . . . . . . . . . . . . . 166N     9.1.13 Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . 166N     9.1.13.1 Rotating media. . . . . . . . . . . . . . . . . . . . . . . . 166N     9.1.13.2 Sequential media. . . . . . . . . . . . . . . . . . . . . . . 167N     9.1.13.3 Memory media. . . . . . . . . . . . . . . . . . . . . . . . . 167N     9.2 Commands for direct-access devices.. . . . . . . . . . . . . . . . 168N     9.2.1 FORMAT UNIT command. . . . . . . . . . . . . . . . . . . . . . . 169N     9.2.1.1 Defect list formats. . . . . . . . . . . . . . . . . . . . . . 174N     9.2.1.2 Initialization pattern option. . . . . . . . . . . . . . . . . 175N     9.2.2 LOCK UNLOCK CACHE command. . . . . . . . . . . . . . . . . . . . 177N     9.2.3 PRE-FETCH command. . . . . . . . . . . . . . . . . . . . . . . . 178N     9.2.4 PREVENT ALLOW MEDIUM REMOVAL command . . . . . . . . . . . . . . 179N     9.2.5 READ(6) command. . . . . . . . . . . . . . . . . . . . . . . . . 180N     9.2.6 READ(10) command . . . . . . . . . . . . . . . . . . . . . . . . 181N     9.2.7 READ CAPACITY command. . . . . . . . . . . . . . . . . . . . . . 182N     9.2.8 READ DEFECT DATA command . . . . . . . . . . . . . . . . . . . . 183N     9.2.9 READ LONG command. . . . . . . . . . . . . . . . . . . . . . . . 185N     9.2.10 REASSIGN BLOCKS command . . . . . . . . . . . . . . . . . . . . 186N     9.2.11 RELEASE command . . . . . . . . . . . . . . . . . . . . . . . . 187N     9.2.11.1 Logical unit release. . . . . . . . . . . . . . . . . . . . . 188N     9.2.11.2 Extent release. . . . . . . . . . . . . . . . . . . . . . . . 188N     9.2.11.3 Third-party release . . . . . . . . . . . . . . . . . . . . . 188N     9.2.12 RESERVE command . . . . . . . . . . . . . . . . . . . . . . . . 189N     9.2.12.1 Logical unit reservation. . . . . . . . . . . . . . . . . . . 189N     9.2.12.2 Extent reservation. . . . . . . . . . . . . . . . . . . . . . 189N     9.2.12.3 Third-party reservation . . . . . . . . . . . . . . . . . . . 191N     9.2.12.4 Superseding reservations. . . . . . . . . . . . . . . . . . . 192N     9.2.13 REZERO UNIT command . . . . . . . . . . . . . . . . . . . . . . 192N     9.2.14 SEARCH DATA commands. . . . . . . . . . . . . . . . . . . . . . 193N     9.2.14.1 SEARCH DATA EQUAL command . . . . . . . . . . . . . . . . . . 195N     9.2.14.2 SEARCH DATA HIGH command. . . . . . . . . . . . . . . . . . . 195N     9.2.14.3 SEARCH DATA LOW command . . . . . . . . . . . . . . . . . . . 195N     9.2.15 SEEK(6) and SEEK(10) commands . . . . . . . . . . . . . . . . . 196N     9.2.16 SET LIMITS command. . . . . . . . . . . . . . . . . . . . . . . 197N     9.2.17 START STOP UNIT command . . . . . . . . . . . . . . . . . . . . 198N     9.2.18 SYNCHRONIZE CACHE command . . . . . . . . . . . . . . . . . . . 199N     9.2.19 VERIFY command. . . . . . . . . . . . . . . . . . . . . . . . . 200N     9.2.20 WRITE(6) command. . . . . . . . . . . . . . . . . . . . . . . . 201N     9.2.21 WRITE(10) command . . . . . . . . . . . . . . . . . . . . . . . 202N     9.2.22 WRITE AND VERIFY command. . . . . . . . . . . . . . . . . . . . 203N     9.2.23 WRITE LONG command. . . . . . . . . . . . . . . . . . . . . . . 204N     9.2.24 WRITE SAME command. . . . . . . . . . . . . . . . . . . . . . . 205N     9.3 Parameters for direct-access devices . . . . . . . . . . . . . . . 206N     9.3.1 Diagnostic parameters. . . . . . . . . . . . . . . . . . . . . . 206N     9.3.1.1 Translate address page - SEND DIAGNOSTIC . . . . . . . . . . . 206N     9.3.1.2 Translate address page - RECEIVE DIAGNOSTIC  . . . . . . . . . 207N     9.3.2 Log parameters . . . . . . . . . . . . . . . . . . . . . . . . . 208N     9.3.3 Mode parameters. . . . . . . . . . . . . . . . . . . . . . . . . 208N     9.3.3.1 Caching page . . . . . . . . . . . . . . . . . . . . . . . . . 210N     9.3.3.2 Flexible disk page . . . . . . . . . . . . . . . . . . . . . . 213N     9.3.3.3 Format device page . . . . . . . . . . . . . . . . . . . . . . 216N     9.3.3.4 Medium types supported page. . . . . . . . . . . . . . . . . . 219N     9.3.3.5 Notch and partition page . . . . . . . . . . . . . . . . . . . 220N     9.3.3.6 Read-write error recovery page . . . . . . . . . . . . . . . . 222N     9.3.3.7 Rigid disk drive geometry page . . . . . . . . . . . . . . . . 229N     9.3.3.8 Verify error recovery page . . . . . . . . . . . . . . . . . . 231N     9.4 Definitions specific to direct-access devices. . . . . . . . . . . 232  .N  10 Sequential-access devices. . . . . . . . . . . . . . . . . . . . . . . 233N     10.1 Sequential-access device model. . . . . . . . . . . . . . . . . . 233N     10.1.1 Physical elements . . . . . . . . . . . . . . . . . . . . . . . 233N     10.1.2 Data storage characteristics. . . . . . . . . . . . . . . . . . 234N     10.1.3 Partitions within a volume. . . . . . . . . . . . . . . . . . . 236N     10.1.4 Logical elements within a partition . . . . . . . . . . . . . . 237N     10.1.5 Data buffering. . . . . . . . . . . . . . . . . . . . . . . . . 238N     10.1.6 Recorded object descriptors (block identifiers) . . . . . . . . 239N     10.1.7 Direction and position definitions. . . . . . . . . . . . . . . 239N     10.1.8 Error reporting . . . . . . . . . . . . . . . . . . . . . . . . 240N     10.2 Command descriptions for sequential-access devices. . . . . . . . 241N     10.2.1 ERASE command . . . . . . . . . . . . . . . . . . . . . . . . . 243N     10.2.2 LOAD UNLOAD command . . . . . . . . . . . . . . . . . . . . . . 244N     10.2.3 LOCATE command. . . . . . . . . . . . . . . . . . . . . . . . . 245N     10.2.4 READ command. . . . . . . . . . . . . . . . . . . . . . . . . . 246N     10.2.5 READ BLOCK LIMITS command . . . . . . . . . . . . . . . . . . . 248N     10.2.6 READ POSITION command . . . . . . . . . . . . . . . . . . . . . 249N     10.2.7 READ REVERSE command. . . . . . . . . . . . . . . . . . . . . . 251N     10.2.8 RECOVER BUFFERED DATA command . . . . . . . . . . . . . . . . . 252N     10.2.9 RELEASE UNIT command. . . . . . . . . . . . . . . . . . . . . . 253N     10.2.9.1 Third-party release . . . . . . . . . . . . . . . . . . . . . 253N     10.2.10 RESERVE UNIT command . . . . . . . . . . . . . . . . . . . . . 254N     10.2.10.1 Third-party reservation. . . . . . . . . . . . . . . . . . . 254N     10.2.10.2 Superseding reservations . . . . . . . . . . . . . . . . . . 255N     10.2.11 REWIND command . . . . . . . . . . . . . . . . . . . . . . . . 255N     10.2.12 SPACE command. . . . . . . . . . . . . . . . . . . . . . . . . 256N     10.2.13 VERIFY command . . . . . . . . . . . . . . . . . . . . . . . . 258N     10.2.14 WRITE command. . . . . . . . . . . . . . . . . . . . . . . . . 259N     10.2.15 WRITE FILEMARKS command. . . . . . . . . . . . . . . . . . . . 261N     10.3 Parameters for sequential-access devices. . . . . . . . . . . . . 262N     10.3.1 Diagnostic parameters . . . . . . . . . . . . . . . . . . . . . 262N     10.3.2 Log parameters. . . . . . . . . . . . . . . . . . . . . . . . . 262N     10.3.3 Mode parameters . . . . . . . . . . . . . . . . . . . . . . . . 263N     10.3.3.1 Device configuration page . . . . . . . . . . . . . . . . . . 266N     10.3.3.2 Medium partition page(1). . . . . . . . . . . . . . . . . . . 269N     10.3.3.3 Medium partition page(2-4). . . . . . . . . . . . . . . . . . 270N     10.3.3.4 Read-write error recovery page. . . . . . . . . . . . . . . . 270N     10.4 Definitions specific to sequential access devices . . . . . . . . 272  7N  11 Commands for printer devices . . . . . . . . . . . . . . . . . . . . . 273N     11.1 Model for printer devices . . . . . . . . . . . . . . . . . . . . 273N     11.2 Commands for printer devices. . . . . . . . . . . . . . . . . . . 274N     11.2.1 FORMAT command. . . . . . . . . . . . . . . . . . . . . . . . . 275N     11.2.2 PRINT command . . . . . . . . . . . . . . . . . . . . . . . . . 276N     11.2.3 RECOVER BUFFERED DATA command . . . . . . . . . . . . . . . . . 276N     11.2.4 SLEW AND PRINT command. . . . . . . . . . . . . . . . . . . . . 277N     11.2.5 STOP PRINT command. . . . . . . . . . . . . . . . . . . . . . . 278N     11.2.6 SYNCHRONIZE BUFFER command. . . . . . . . . . . . . . . . . . . 278N     11.3 Parameters for printer devices. . . . . . . . . . . . . . . . . . 279N     11.3.1 Diagnostic parameters . . . . . . . . . . . . . . . . . . . . . 279N     11.3.2 Log parameters. . . . . . . . . . . . . . . . . . . . . . . . . 279N     11.3.3 Mode parameters . . . . . . . . . . . . . . . . . . . . . . . . 279N     11.3.3.1 Parallel printer interface page . . . . . . . . . . . . . . . 280N     11.3.3.2 Printer options page. . . . . . . . . . . . . . . . . . . . . 282N     11.3.3.3 Serial printer interface page . . . . . . . . . . . . . . . . 285  SN  12 Processor devices. . . . . . . . . . . . . . . . . . . . . . . . . . . 287N     12.1 Model for processor devices . . . . . . . . . . . . . . . . . . . 287N     12.1.1 Host-to-host communication, SEND only . . . . . . . . . . . . . 288N     12.1.2 Host-to-host communication, SEND and RECEIVE. . . . . . . . . . 288N     12.1.3 Host-to-special-output peripheral . . . . . . . . . . . . . . . 288N     12.1.4 Host-to-special-input peripheral. . . . . . . . . . . . . . . . 288N     12.2 Commands for processor devices. . . . . . . . . . . . . . . . . . 289N     12.2.1 RECEIVE command . . . . . . . . . . . . . . . . . . . . . . . . 289N     12.2.2 SEND command. . . . . . . . . . . . . . . . . . . . . . . . . . 290N     12.3 Parameters for processor devices. . . . . . . . . . . . . . . . . 291N     12.3.1 Diagnostic parameters . . . . . . . . . . . . . . . . . . . . . 291N     12.3.2 Log parameters. . . . . . . . . . . . . . . . . . . . . . . . . 291N     12.4 Definitions specific to processor devices . . . . . . . . . . . . 292  kN  13 Write-once devices . . . . . . . . . . . . . . . . . . . . . . . . . . 293N     13.1 Model for write-once devices. . . . . . . . . . . . . . . . . . . 293N     13.1.1 Logical blocks. . . . . . . . . . . . . . . . . . . . . . . . . 293N     13.1.2 Initialization. . . . . . . . . . . . . . . . . . . . . . . . . 293N     13.1.3 Physical medium defects . . . . . . . . . . . . . . . . . . . . 293N     13.1.4 Error reporting . . . . . . . . . . . . . . . . . . . . . . . . 293N     13.2 Commands for write-once devices . . . . . . . . . . . . . . . . . 294N     13.3 Parameters for write-once devices . . . . . . . . . . . . . . . . 296N     13.4 Definitions specific to write-once devices. . . . . . . . . . . . 296  fN  14 CD-ROM devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297N     14.1 Model for CD-ROM devices. . . . . . . . . . . . . . . . . . . . . 297N     14.1.1 CD-ROM media organization . . . . . . . . . . . . . . . . . . . 297N     14.1.2 CD-ROM physical data format . . . . . . . . . . . . . . . . . . 300N     14.1.2.1 Frame format for audio. . . . . . . . . . . . . . . . . . . . 300N     14.1.2.2 Sector format for data. . . . . . . . . . . . . . . . . . . . 301N     14.1.2.3 Sub-channel information formats . . . . . . . . . . . . . . . 301N     14.1.3 CD Audio error reporting. . . . . . . . . . . . . . . . . . . . 302N     14.1.4 CD-ROM ready condition/not ready condition. . . . . . . . . . . 302N     14.1.5 CD-ROM address reporting formats (MSF bit). . . . . . . . . . . 303N     14.1.6 Sensing support for CD-audio commands.. . . . . . . . . . . . . 303N     14.1.7 Error reporting . . . . . . . . . . . . . . . . . . . . . . . . 303N     14.2 Commands for CD-ROM devices . . . . . . . . . . . . . . . . . . . 305N     14.2.1 PAUSE RESUME command. . . . . . . . . . . . . . . . . . . . . . 306N     14.2.2 PLAY AUDIO(10) command. . . . . . . . . . . . . . . . . . . . . 307N     14.2.3 PLAY AUDIO(12) command  . . . . . . . . . . . . . . . . . . . . 308N     14.2.4 PLAY AUDIO MSF command. . . . . . . . . . . . . . . . . . . . . 309N     14.2.5 PLAY AUDIO TRACK INDEX command. . . . . . . . . . . . . . . . . 310N     14.2.6 PLAY AUDIO TRACK RELATIVE(10) command . . . . . . . . . . . . . 311N     14.2.7 PLAY AUDIO TRACK RELATIVE(12) command . . . . . . . . . . . . . 312N     14.2.8 READ CD-ROM CAPACITY command. . . . . . . . . . . . . . . . . . 313N     14.2.9 READ HEADER command . . . . . . . . . . . . . . . . . . . . . . 314N     14.2.10 READ SUB-CHANNEL command . . . . . . . . . . . . . . . . . . . 316N     14.2.10.1 Sub-Q channel data format. . . . . . . . . . . . . . . . . . 317N     14.2.10.2 CD-ROM current position data format. . . . . . . . . . . . . 320N     14.2.10.3 Media catalogue number data format . . . . . . . . . . . . . 320N     14.2.10.4 Track international standard recording code data format. . . 321N     14.2.11 READ TOC command . . . . . . . . . . . . . . . . . . . . . . . 323N     14.3 Parameters for CD-ROM devices . . . . . . . . . . . . . . . . . . 325N     14.3.1 Diagnostic parameters . . . . . . . . . . . . . . . . . . . . . 325N     14.3.2 Log parameters. . . . . . . . . . . . . . . . . . . . . . . . . 325N     14.3.3 Mode parameters . . . . . . . . . . . . . . . . . . . . . . . . 325N     14.3.3.1 CD-ROM audio control parameters . . . . . . . . . . . . . . . 327N     14.3.3.2 CD-ROM device parameters  . . . . . . . . . . . . . . . . . . 329N     14.3.3.3 Read error recovery parameters  . . . . . . . . . . . . . . . 330N     14.3.3.4 Verify error recovery parameters. . . . . . . . . . . . . . . 336N     14.4 Definitions specific to CD-ROM devices. . . . . . . . . . . . . . 336  rN  15 Scanner devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . 339N     15.1 Model for scanner devices . . . . . . . . . . . . . . . . . . . . 339N     15.2 Commands for scanner devices. . . . . . . . . . . . . . . . . . . 340N     15.2.1 GET DATA BUFFER STATUS command. . . . . . . . . . . . . . . . . 341N     15.2.2 GET WINDOW command. . . . . . . . . . . . . . . . . . . . . . . 343N     15.2.3 OBJECT POSITION command . . . . . . . . . . . . . . . . . . . . 347N     15.2.4 READ command. . . . . . . . . . . . . . . . . . . . . . . . . . 349N     15.2.5 SCAN command. . . . . . . . . . . . . . . . . . . . . . . . . . 350N     15.2.6 SEND command. . . . . . . . . . . . . . . . . . . . . . . . . . 350N     15.2.7 SET WINDOW command. . . . . . . . . . . . . . . . . . . . . . . 351N     15.3 Parameters for scanner devices. . . . . . . . . . . . . . . . . . 352N     15.3.1 Diagnostic parameters . . . . . . . . . . . . . . . . . . . . . 352N     15.3.2 Log parameters. . . . . . . . . . . . . . . . . . . . . . . . . 352N     15.3.3 Mode parameters . . . . . . . . . . . . . . . . . . . . . . . . 353N     15.3.3.1 Measurement units page. . . . . . . . . . . . . . . . . . . . 353N     15.4 Definitions specific to scanner devices . . . . . . . . . . . . . 355  cN  16  Optical memory devices. . . . . . . . . . . . . . . . . . . . . . . . 357N     16.1 Model for optical memory devices. . . . . . . . . . . . . . . . . 357N     16.1.1 Defect management . . . . . . . . . . . . . . . . . . . . . . . 358N     16.1.2 Error reporting . . . . . . . . . . . . . . . . . . . . . . . . 358N     16.2 Commands for optical memory devices . . . . . . . . . . . . . . . 359N     16.2.1 ERASE(10) command . . . . . . . . . . . . . . . . . . . . . . . 360N     16.2.2 ERASE(12) command . . . . . . . . . . . . . . . . . . . . . . . 361N     16.2.3 MEDIUM SCAN command . . . . . . . . . . . . . . . . . . . . . . 362N     16.2.4 READ(12) command. . . . . . . . . . . . . . . . . . . . . . . . 364N     16.2.5 READ DEFECT DATA(12) command. . . . . . . . . . . . . . . . . . 364N     16.2.6 READ GENERATION command . . . . . . . . . . . . . . . . . . . . 366N     16.2.7 READ UPDATED BLOCK(10) command. . . . . . . . . . . . . . . . . 367N     16.2.8 SEARCH DATA(12) commands. . . . . . . . . . . . . . . . . . . . 368N     16.2.9 SET LIMITS(12) command. . . . . . . . . . . . . . . . . . . . . 368N     16.2.10 UPDATE BLOCK command . . . . . . . . . . . . . . . . . . . . . 369N     16.2.11 VERIFY(10) command . . . . . . . . . . . . . . . . . . . . . . 370N     16.2.12 VERIFY(12) command . . . . . . . . . . . . . . . . . . . . . . 371N     16.2.13 WRITE(10) command. . . . . . . . . . . . . . . . . . . . . . . 372N     16.2.14 WRITE(12) command. . . . . . . . . . . . . . . . . . . . . . . 373N     16.2.15 WRITE AND VERIFY(10) command . . . . . . . . . . . . . . . . . 373N     16.2.16 WRITE AND VERIFY(12) command . . . . . . . . . . . . . . . . . 374N     16.3 Parameters for optical memory devices . . . . . . . . . . . . . . 375N     16.3.1 Diagnostic parameters . . . . . . . . . . . . . . . . . . . . . 375N     16.3.2 Log parameters. . . . . . . . . . . . . . . . . . . . . . . . . 375N     16.3.3 Mode parameters . . . . . . . . . . . . . . . . . . . . . . . . 375N     16.3.3.1 Optical memory page . . . . . . . . . . . . . . . . . . . . . 378N     16.4 Definitions specific to write-once and optical memory devices . . 378  KN  17 Medium-changer devices . . . . . . . . . . . . . . . . . . . . . . . . 379N     17.1 Medium-changer device model . . . . . . . . . . . . . . . . . . . 379N     17.1.1 Medium-changer elements . . . . . . . . . . . . . . . . . . . . 379N     17.1.1.1 Medium transport elements . . . . . . . . . . . . . . . . . . 379N     17.1.1.2 Storage elements. . . . . . . . . . . . . . . . . . . . . . . 380N     17.1.1.3 Import export elements. . . . . . . . . . . . . . . . . . . . 380N     17.1.1.4 Data transfer element . . . . . . . . . . . . . . . . . . . . 380N     17.1.2 SCSI addressing of medium changer devices . . . . . . . . . . . 381N     17.1.3 Data access operations using a medium changer device. . . . . . 381N     17.1.4 Element status maintenance requirements . . . . . . . . . . . . 381N     17.1.5 Volume tags . . . . . . . . . . . . . . . . . . . . . . . . . . 381N     17.1.5.1 Volume tag format . . . . . . . . . . . . . . . . . . . . . . 382N     17.1.5.2 Primary and alternate volume tag information. . . . . . . . . 382N     17.2 Commands for medium changer devices . . . . . . . . . . . . . . . 383N     17.2.1 EXCHANGE MEDIUM command . . . . . . . . . . . . . . . . . . . . 384N     17.2.2 INITIALIZE ELEMENT STATUS command . . . . . . . . . . . . . . . 385N     17.2.3 MOVE MEDIUM command . . . . . . . . . . . . . . . . . . . . . . 386N     17.2.4 POSITION TO ELEMENT command . . . . . . . . . . . . . . . . . . 387N     17.2.5 READ ELEMENT STATUS command . . . . . . . . . . . . . . . . . . 388N     17.2.5.1 Element status data . . . . . . . . . . . . . . . . . . . . . 389N     17.2.5.2 Element status page . . . . . . . . . . . . . . . . . . . . . 391N     17.2.5.3 Medium transport element descriptor . . . . . . . . . . . . . 392N     17.2.5.4 Storage element descriptor. . . . . . . . . . . . . . . . . . 393N     17.2.5.5 Import export element descriptor. . . . . . . . . . . . . . . 394N     17.2.5.6 Data transfer element descriptor. . . . . . . . . . . . . . . 395N     17.2.6 REQUEST VOLUME ELEMENT ADDRESS command. . . . . . . . . . . . . 396N     17.2.7 RELEASE command . . . . . . . . . . . . . . . . . . . . . . . . 398N     17.2.7.1 Logical unit release. . . . . . . . . . . . . . . . . . . . . 398N     17.2.7.2 Element release (optional). . . . . . . . . . . . . . . . . . 398N     17.2.7.3 Third party release . . . . . . . . . . . . . . . . . . . . . 398N     17.2.8 RESERVE command . . . . . . . . . . . . . . . . . . . . . . . . 399N     17.2.8.1 Logical unit reservation. . . . . . . . . . . . . . . . . . . 399N     17.2.8.2 Element reservation (optional). . . . . . . . . . . . . . . . 399N     17.2.8.3 Third party reservation . . . . . . . . . . . . . . . . . . . 400N     17.2.8.4 Superseding reservations. . . . . . . . . . . . . . . . . . . 401N     17.2.9 SEND VOLUME TAG command . . . . . . . . . . . . . . . . . . . . 401N     17.3 Parameters for medium changer devices . . . . . . . . . . . . . . 404N     17.3.1 Diagnostic parameters . . . . . . . . . . . . . . . . . . . . . 404N     17.3.2 Log parameters. . . . . . . . . . . . . . . . . . . . . . . . . 404N     17.3.3 Mode parameters . . . . . . . . . . . . . . . . . . . . . . . . 404N     17.3.3.1 Device capabilities page. . . . . . . . . . . . . . . . . . . 405N     17.3.3.2 Element address assignment page . . . . . . . . . . . . . . . 406N     17.3.3.3 Transport geometry parameters page. . . . . . . . . . . . . . 409N     17.4 Definitions specific to medium changer devices. . . . . . . . . . 410  rN  18 Communications devices . . . . . . . . . . . . . . . . . . . . . . . . 411N     18.1 Communications device model . . . . . . . . . . . . . . . . . . . 411N     18.1.1 Implementation examples . . . . . . . . . . . . . . . . . . . . 412N     18.1.1.1 Host-to-host communications . . . . . . . . . . . . . . . . . 412N     18.1.1.2 Host-to-device communications . . . . . . . . . . . . . . . . 412N     18.1.1.3 Multiple role communications  . . . . . . . . . . . . . . . . 413N     18.2 Command descriptions for communications devices . . . . . . . . . 413N     18.2.1 GET MESSAGE(6) command. . . . . . . . . . . . . . . . . . . . . 414N     18.2.2 GET MESSAGE(10) command . . . . . . . . . . . . . . . . . . . . 414N     18.2.3 GET MESSAGE(12) command . . . . . . . . . . . . . . . . . . . . 415N     18.2.4 SEND MESSAGE(6) command . . . . . . . . . . . . . . . . . . . . 416N     18.2.5 SEND MESSAGE(10) command. . . . . . . . . . . . . . . . . . . . 416N     18.2.6 SEND MESSAGE(12) command. . . . . . . . . . . . . . . . . . . . 417N     18.3 Parameters for communication devices. . . . . . . . . . . . . . . 418N     18.3.1 Diagnostic parameters . . . . . . . . . . . . . . . . . . . . . 418N     18.3.2 Log parameters. . . . . . . . . . . . . . . . . . . . . . . . . 418N     18.3.3 Mode parameters . . . . . . . . . . . . . . . . . . . . . . . . 418N     18.4 Definitions specific to communications devices. . . . . . . . . . 419N     C.1 SCSI-3 standards projects. . . . . . . . . . . . . . . . . . . . . 427N     C.2 Digital data exchange for colour electronic prepress systems . . . 427N     C.3 Fibre channel. . . . . . . . . . . . . . . . . . . . . . . . . . . 427  UN  Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443     C  E  AnnexesN                                                                           PageN  Annex A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421N  SCSI signal sequence example. . . . . . . . . . . . . . . . . . . . . . . 421  .N  Annex B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425N  Fast SCSI skew time . . . . . . . . . . . . . . . . . . . . . . . . . . . 425  .N  Annex C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427N  Other SCSI standardization activities . . . . . . . . . . . . . . . . . . 427  .N  Annex D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429N  Numeric order codes . . . . . . . . . . . . . . . . . . . . . . . . . . . 429  .N  Annex E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439N  Vendor identification . . . . . . . . . . . . . . . . . . . . . . . . . . 439  .  .  FiguresN                                                                           Page?  Figure 1 - 50/68-contact non-shielded high-density SCSI device.N     connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  12N  Figure 2 - 50/68-contact non-shielded high-density cable connector. . . .  13N  Figure 3 - 50-contact non-shielded low-density SCSI device connector. . .  14N  Figure 4 - 50-Contact non-shielded low-density cable connector. . . . . .  15N  Figure 5 - 50/68-contact shielded high-density SCSI device connector. . .  17N  Figure 6 - 50/68-contact shielded high-density cable connector. . . . . .  18N  Figure 7 - 50-contact shielded low-density SCSI device connector. . . . .  19N  Figure 8 - 50-contact shielded low-density cable connector. . . . . . . .  20N  Figure 9 - Alternative 1 termination. . . . . . . . . . . . . . . . . . .  29N  Figure 10 - Alternative 2 termination for single-ended devices. . . . . .  29N  Figure 11 - Termination for differential devices. . . . . . . . . . . . .  30N  Figure 12 - Differential driver protection circuit. . . . . . . . . . . .  30N  Figure 13 - SCSI ID bits. . . . . . . . . . . . . . . . . . . . . . . . .  31N  Figure 14 - Sample SCSI configurations. . . . . . . . . . . . . . . . . .  32N  Figure 15 - Wide SCSI byte ordering . . . . . . . . . . . . . . . . . . .  47N  Figure 16 - Phase sequences . . . . . . . . . . . . . . . . . . . . . . .  53N  Figure 17 - Simplified SCSI system. . . . . . . . . . . . . . . . . . . .  54N  Figure 18 - Typical volume layout . . . . . . . . . . . . . . . . . . . . 234N  Figure 19 - Typical medium track layout . . . . . . . . . . . . . . . . . 234N  Figure 20 - Serpentine recording example  . . . . . . . . . . . . . . . . 234N  Figure 21 - Parallel recording example. . . . . . . . . . . . . . . . . . 235N  Figure 22 - Helical scan recording example. . . . . . . . . . . . . . . . 235N  Figure 23 - Early-warning example . . . . . . . . . . . . . . . . . . . . 235N  Figure 24 - Partitioning example - one partition per track group. . . . . 236N  Figure 25 - Partitioning example - one partition per two track groups . . 236N  Figure 26 - Partitioning example - two partitions per track group . . . . 237N  Figure 27 - SCSI printer model. . . . . . . . . . . . . . . . . . . . . . 273N  Figure 28 - Illustration of element status data structure . . . . . . . . 390N  Figure A.1 - SCSI signal sequence example . . . . . . . . . . . . . . . . 424N  Figure C.1 - SCSI-3 standards structure . . . . . . . . . . . . . . . . . 427  .  .  .  .  Tables4N                                                                           PageN  Table 1 - Cross-reference to connector contact assignments. . . . . . . .  21N  Table 2 - Single-ended contact assignments - A cable. . . . . . . . . . .  21N  Table 3 - Single-ended contact assignments - B cable. . . . . . . . . . .  22N  Table 4 - Differential contact assignments - A cable. . . . . . . . . . .  23N  Table 5 - Differential contact assignments - B cable. . . . . . . . . . .  24N  Table 6 - Signal sources. . . . . . . . . . . . . . . . . . . . . . . . .  34N  Table 7 - SCSI bus timing values. . . . . . . . . . . . . . . . . . . . .  36N  Table 8 - Information transfer phases . . . . . . . . . . . . . . . . . .  45N  Table 9 - Message format. . . . . . . . . . . . . . . . . . . . . . . . .  55N  Table 10 - Message codes. . . . . . . . . . . . . . . . . . . . . . . . .  55N  Table 11 - Extended message format. . . . . . . . . . . . . . . . . . . .  57N  Table 12 - Extended message codes . . . . . . . . . . . . . . . . . . . .  57N  Table 13 - IDENTIFY message format. . . . . . . . . . . . . . . . . . . .  60N  Table 14 - IGNORE WIDE RESIDUE message format . . . . . . . . . . . . . .  61N  Table 15 - Ignore field definition. . . . . . . . . . . . . . . . . . . .  61N  Table 16 - MODIFY DATA POINTER. . . . . . . . . . . . . . . . . . . . . .  63N  Table 17 - Queue tag message format . . . . . . . . . . . . . . . . . . .  63N  Table 18 - SYNCHRONOUS DATA TRANSFER REQUEST. . . . . . . . . . . . . . .  65N  Table 19 - WIDE DATA TRANSFER MESSAGE . . . . . . . . . . . . . . . . . .  67N  Table 20 - Operation code type. . . . . . . . . . . . . . . . . . . . . .  71N  Table 21 - Typical command descriptor block for six-byte commands . . . .  72N  Table 22 - Typical command descriptor block for ten-byte commands . . . .  72N  Table 23 - Typical command descriptor block for twelve-byte commands. . .  72N  Table 24 - Operation code . . . . . . . . . . . . . . . . . . . . . . . .  74N  Table 25 - Control field. . . . . . . . . . . . . . . . . . . . . . . . .  75N  Table 26 - Status byte. . . . . . . . . . . . . . . . . . . . . . . . . .  76N  Table 27 - Status byte code . . . . . . . . . . . . . . . . . . . . . . .  76N  Table 28 - Commands in order received by target . . . . . . . . . . . . .  86N  Table 29 - Commands in order of execution . . . . . . . . . . . . . . . .  87N  Table 30 - Modified by HEAD OF QUEUE TAG message. . . . . . . . . . . . .  87N  Table 31 - Commands for all device types. . . . . . . . . . . . . . . . .  92N  Table 32 - CHANGE DEFINITION command. . . . . . . . . . . . . . . . . . .  93N  Table 33 - Definition parameter field . . . . . . . . . . . . . . . . . .  94N  Table 34 - COMPARE command. . . . . . . . . . . . . . . . . . . . . . . .  95N  Table 35 - COPY command . . . . . . . . . . . . . . . . . . . . . . . . .  96N  Table 36 - COPY parameter list. . . . . . . . . . . . . . . . . . . . . .  96N  Table 37 - COPY function codes. . . . . . . . . . . . . . . . . . . . . .  97N  Table 38 - Segment descriptor for COPY function codes 00h and 01h . . . .  99N  Table 39 - Segment descriptor for COPY function code 02h. . . . . . . . . 100N  Table 40 - Segment descriptor for COPY function code 03h. . . . . . . . . 100N  Table 41 - Segment descriptor for COPY function code 04h. . . . . . . . . 102N  Table 42 - Pad and cat bit definition . . . . . . . . . . . . . . . . . . 102N  Table 43 - COPY AND VERIFY command. . . . . . . . . . . . . . . . . . . . 103N  Table 44 - INQUIRY command. . . . . . . . . . . . . . . . . . . . . . . . 104N  Table 45 - Standard INQUIRY data format . . . . . . . . . . . . . . . . . 105N  Table 46 - Peripheral qualifier . . . . . . . . . . . . . . . . . . . . . 105N  Table 47 - Peripheral device type . . . . . . . . . . . . . . . . . . . . 106N  Table 48 - ANSI-approved version. . . . . . . . . . . . . . . . . . . . . 107N  Table 49 - LOG SELECT command . . . . . . . . . . . . . . . . . . . . . . 109N  Table 50 - Page control field . . . . . . . . . . . . . . . . . . . . . . 110N  Table 51 - LOG SENSE command. . . . . . . . . . . . . . . . . . . . . . . 111N  Table 52 - MODE SELECT(6) command . . . . . . . . . . . . . . . . . . . . 112N  Table 53 - MODE SELECT(10) command. . . . . . . . . . . . . . . . . . . . 114N  Table 54 - MODE SENSE(6) command. . . . . . . . . . . . . . . . . . . . . 115N  Table 55 - Page control field . . . . . . . . . . . . . . . . . . . . . . 115N  Table 56 - Mode page code usage for all devices . . . . . . . . . . . . . 115N  Table 57 - MODE SENSE(10) command . . . . . . . . . . . . . . . . . . . . 117N  Table 58 - READ BUFFER command. . . . . . . . . . . . . . . . . . . . . . 118N  Table 59 - READ BUFFER mode field . . . . . . . . . . . . . . . . . . . . 118N  Table 60 - READ BUFFER header . . . . . . . . . . . . . . . . . . . . . . 118N  Table 61 - READ BUFFER descriptor . . . . . . . . . . . . . . . . . . . . 119N  Table 62 - Buffer offset boundary . . . . . . . . . . . . . . . . . . . . 120N  Table 63 - RECEIVE DIAGNOSTIC RESULTS command . . . . . . . . . . . . . . 121N  Table 64 - REQUEST SENSE command. . . . . . . . . . . . . . . . . . . . . 122N  Table 65 - Error codes 70h and 71h sense data format. . . . . . . . . . . 123N  Table 66 - Field pointer bytes. . . . . . . . . . . . . . . . . . . . . . 125N  Table 67 - Actual retry count bytes . . . . . . . . . . . . . . . . . . . 125N  Table 68 - Format progress indication bytes . . . . . . . . . . . . . . . 126N  Table 69 - Sense key (0h-7h) descriptions . . . . . . . . . . . . . . . . 128N  Table 70 - Sense key (8h-Fh) descriptions . . . . . . . . . . . . . . . . 129N  Table 71 - ASC and ASCQ assignments . . . . . . . . . . . . . . . . . . . 130N  Table 72 - SEND DIAGNOSTIC command. . . . . . . . . . . . . . . . . . . . 134N  Table 73 - TEST UNIT READY command. . . . . . . . . . . . . . . . . . . . 135N  Table 74 - Preferred TEST UNIT READY responses. . . . . . . . . . . . . . 135N  Table 75 - WRITE BUFFER command . . . . . . . . . . . . . . . . . . . . . 136N  Table 76 - WRITE BUFFER mode field. . . . . . . . . . . . . . . . . . . . 137N  Table 77 - Diagnostic page format . . . . . . . . . . . . . . . . . . . . 138N  Table 78 - Diagnostic page codes. . . . . . . . . . . . . . . . . . . . . 139N  Table 79 - Supported diagnostic pages . . . . . . . . . . . . . . . . . . 139N  Table 80 - Log page format. . . . . . . . . . . . . . . . . . . . . . . . 140N  Table 81 - Log parameter. . . . . . . . . . . . . . . . . . . . . . . . . 140N  Table 82 - Threshold met criteria . . . . . . . . . . . . . . . . . . . . 142N  Table 83 - Log page codes . . . . . . . . . . . . . . . . . . . . . . . . 143>  Table 84 - Parameter code field for buffer over-run/under-runN     counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143N  Table 85 - Count basis definition . . . . . . . . . . . . . . . . . . . . 144N  Table 86 - Cause field definition . . . . . . . . . . . . . . . . . . . . 144N  Table 87 - Parameter codes for error counter pages. . . . . . . . . . . . 144N  Table 88 - Non-medium error event parameter codes . . . . . . . . . . . . 145N  Table 89 - Supported log pages. . . . . . . . . . . . . . . . . . . . . . 146N  Table 90 - Mode parameter list. . . . . . . . . . . . . . . . . . . . . . 146N  Table 91 - Mode parameter header(6) . . . . . . . . . . . . . . . . . . . 146N  Table 92 - Mode parameter header(10). . . . . . . . . . . . . . . . . . . 147N  Table 93 - Mode parameter block descriptor. . . . . . . . . . . . . . . . 148N  Table 94 - Mode page format . . . . . . . . . . . . . . . . . . . . . . . 148N  Table 95 - Mode page codes. . . . . . . . . . . . . . . . . . . . . . . . 149N  Table 96 - Control mode page. . . . . . . . . . . . . . . . . . . . . . . 149N  Table 97 - Queue algorithm modifier . . . . . . . . . . . . . . . . . . . 150N  Table 98 - Disconnect-reconnect page. . . . . . . . . . . . . . . . . . . 152N  Table 99 - Data transfer disconnect control . . . . . . . . . . . . . . . 153N  Table 100 - Peripheral device page. . . . . . . . . . . . . . . . . . . . 154N  Table 101 - Interface identifier codes. . . . . . . . . . . . . . . . . . 154N  Table 102 - Vital product data page codes . . . . . . . . . . . . . . . . 154N  Table 103 - ASCII implemented operating definition  . . . . . . . . . . . 155N  Table 104 - ASCII information page. . . . . . . . . . . . . . . . . . . . 156N  Table 105 - Implemented operating definition page . . . . . . . . . . . . 156N  Table 106 - Supported vital product data pages. . . . . . . . . . . . . . 158N  Table 107 - Unit serial number page . . . . . . . . . . . . . . . . . . . 159N  Table 108 - Commands for direct-access devices. . . . . . . . . . . . . . 168N  Table 109 - FORMAT UNIT command . . . . . . . . . . . . . . . . . . . . . 169N  Table 110 - FORMAT UNIT parameter list. . . . . . . . . . . . . . . . . . 170N  Table 111 - Defect list header. . . . . . . . . . . . . . . . . . . . . . 170N  Table 112 - FORMAT UNIT defect descriptor format and requirements . . . . 171N  Table 113 - Defect descriptor - Block format. . . . . . . . . . . . . . . 174N  Table 114 - Defect descriptor - Bytes from index format . . . . . . . . . 174N  Table 115 - Defect descriptor - Physical sector format. . . . . . . . . . 175N  Table 116 - Initialization pattern descriptor . . . . . . . . . . . . . . 175N  Table 117 - Initialization pattern modifier . . . . . . . . . . . . . . . 175N  Table 118 - Initialization pattern type . . . . . . . . . . . . . . . . . 176N  Table 119 - LOCK UNLOCK CACHE command . . . . . . . . . . . . . . . . . . 177N  Table 120 - PRE-FETCH command . . . . . . . . . . . . . . . . . . . . . . 178N  Table 121 - PREVENT ALLOW MEDIUM REMOVAL command. . . . . . . . . . . . . 179N  Table 122 - READ(6) command . . . . . . . . . . . . . . . . . . . . . . . 180N  Table 123 - READ(10) command. . . . . . . . . . . . . . . . . . . . . . . 181N  Table 124 - READ CAPACITY command . . . . . . . . . . . . . . . . . . . . 182N  Table 125 - READ CAPACITY data. . . . . . . . . . . . . . . . . . . . . . 182N  Table 126 - READ DEFECT DATA command. . . . . . . . . . . . . . . . . . . 183N  Table 127 - READ DEFECT DATA defect list. . . . . . . . . . . . . . . . . 184N  Table 128 - READ LONG command . . . . . . . . . . . . . . . . . . . . . . 185N  Table 129 - REASSIGN BLOCKS command . . . . . . . . . . . . . . . . . . . 186N  Table 130 - REASSIGN BLOCKS defect list . . . . . . . . . . . . . . . . . 186N  Table 131 - RELEASE command . . . . . . . . . . . . . . . . . . . . . . . 187N  Table 132 - RESERVE command . . . . . . . . . . . . . . . . . . . . . . . 189N  Table 133 - Data format of extent descriptors . . . . . . . . . . . . . . 190N  Table 134 - Reservation types . . . . . . . . . . . . . . . . . . . . . . 190N  Table 135 - REZERO UNIT command . . . . . . . . . . . . . . . . . . . . . 192N  Table 136 - SEARCH DATA commands. . . . . . . . . . . . . . . . . . . . . 193N  Table 137 - SEARCH DATA parameter list. . . . . . . . . . . . . . . . . . 194N  Table 138 - SEEK(6) command . . . . . . . . . . . . . . . . . . . . . . . 196N  Table 139 - SEEK(10) command. . . . . . . . . . . . . . . . . . . . . . . 196N  Table 140 - SET LIMITS command. . . . . . . . . . . . . . . . . . . . . . 197N  Table 141 - START STOP UNIT command . . . . . . . . . . . . . . . . . . . 198N  Table 142 - SYNCHRONIZE CACHE command . . . . . . . . . . . . . . . . . . 199N  Table 143 - VERIFY command. . . . . . . . . . . . . . . . . . . . . . . . 200N  Table 144 - WRITE(6) command. . . . . . . . . . . . . . . . . . . . . . . 201N  Table 145 - WRITE(10) command . . . . . . . . . . . . . . . . . . . . . . 202N  Table 146 - WRITE AND VERIFY command. . . . . . . . . . . . . . . . . . . 203N  Table 147 - WRITE LONG command. . . . . . . . . . . . . . . . . . . . . . 204N  Table 148 - WRITE SAME command. . . . . . . . . . . . . . . . . . . . . . 205N  Table 149 - Diagnostic page codes . . . . . . . . . . . . . . . . . . . . 206N  Table 150 - Translate address page - SEND DIAGNOSTIC. . . . . . . . . . . 206N  Table 151 - Translate address page - RECEIVE DIAGNOSTIC . . . . . . . . . 207N  Table 152 - Log page codes. . . . . . . . . . . . . . . . . . . . . . . . 208N  Table 153 - Direct-access medium-type codes . . . . . . . . . . . . . . . 208N  Table 154 - Device specific parameter . . . . . . . . . . . . . . . . . . 209N  Table 155 - Mode page codes . . . . . . . . . . . . . . . . . . . . . . . 210N  Table 156 - Caching page. . . . . . . . . . . . . . . . . . . . . . . . . 210N  Table 157 - Demand read and write retention priority. . . . . . . . . . . 211N  Table 158 - Flexible disk page. . . . . . . . . . . . . . . . . . . . . . 213N  Table 159 - Examples of transfer rates. . . . . . . . . . . . . . . . . . 214N  Table 160 - Pin 34 field. . . . . . . . . . . . . . . . . . . . . . . . . 215N  Table 161 - Pin 4 field . . . . . . . . . . . . . . . . . . . . . . . . . 215N  Table 162 - Pin 34 field. . . . . . . . . . . . . . . . . . . . . . . . . 216N  Table 163 - Format device page. . . . . . . . . . . . . . . . . . . . . . 216N  Table 164 - Reporting of default sector formatting support. . . . . . . . 218N  Table 165 - Reporting of changeable sector formatting support . . . . . . 219N  Table 166 - Medium types supported page . . . . . . . . . . . . . . . . . 219N  Table 167 - Notch page. . . . . . . . . . . . . . . . . . . . . . . . . . 220N  Table 168 - Read-write error recovery page. . . . . . . . . . . . . . . . 222N  Table 169 - Error recovery bit definitions. . . . . . . . . . . . . . . . 223N  Table 170 - Combined error recovery parameter descriptions. . . . . . . . 224N  Table 171 - Rigid disk drive geometry page. . . . . . . . . . . . . . . . 229N  Table 172 - Rotational position locking . . . . . . . . . . . . . . . . . 230N  Table 173 - Verify error recovery page. . . . . . . . . . . . . . . . . . 231N  Table 174 - Commands for sequential-access devices. . . . . . . . . . . . 241N  Table 175 - ERASE command . . . . . . . . . . . . . . . . . . . . . . . . 243N  Table 176 - LOAD UNLOAD command . . . . . . . . . . . . . . . . . . . . . 244N  Table 177 - LOCATE command. . . . . . . . . . . . . . . . . . . . . . . . 245N  Table 178 - READ command. . . . . . . . . . . . . . . . . . . . . . . . . 246N  Table 179 - READ BLOCK LIMITS command . . . . . . . . . . . . . . . . . . 248N  Table 180 - READ BLOCK LIMITS data. . . . . . . . . . . . . . . . . . . . 248N  Table 181 - READ POSITION command . . . . . . . . . . . . . . . . . . . . 249N  Table 182 - READ POSITION data format . . . . . . . . . . . . . . . . . . 249N  Table 183 - READ REVERSE command. . . . . . . . . . . . . . . . . . . . . 251N  Table 184 - RECOVER BUFFERED DATA command . . . . . . . . . . . . . . . . 252N  Table 185 - RELEASE UNIT command. . . . . . . . . . . . . . . . . . . . . 253N  Table 186 - RESERVE UNIT command. . . . . . . . . . . . . . . . . . . . . 254N  Table 187 - REWIND command. . . . . . . . . . . . . . . . . . . . . . . . 255N  Table 188 - SPACE command . . . . . . . . . . . . . . . . . . . . . . . . 256N  Table 189 - Code field definition . . . . . . . . . . . . . . . . . . . . 256N  Table 190 - VERIFY command. . . . . . . . . . . . . . . . . . . . . . . . 258N  Table 191 - WRITE command . . . . . . . . . . . . . . . . . . . . . . . . 259N  Table 192 - WRITE FILEMARKS command . . . . . . . . . . . . . . . . . . . 261N  Table 193 - Diagnostic page codes . . . . . . . . . . . . . . . . . . . . 262N  Table 194 - Log page codes. . . . . . . . . . . . . . . . . . . . . . . . 262N  Table 195 - Device-specific parameter . . . . . . . . . . . . . . . . . . 263N  Table 196 - Buffered modes. . . . . . . . . . . . . . . . . . . . . . . . 263N  Table 197 - Speed field definition. . . . . . . . . . . . . . . . . . . . 263N  Table 198 - Sequential-access density codes . . . . . . . . . . . . . . . 264N  Table 199 - Mode page codes . . . . . . . . . . . . . . . . . . . . . . . 265N  Table 200 - Device configuration page . . . . . . . . . . . . . . . . . . 266N  Table 201 - EOD formats . . . . . . . . . . . . . . . . . . . . . . . . . 268N  Table 202 - Medium partition page(1). . . . . . . . . . . . . . . . . . . 269N  Table 203 - Medium partition page(2-4). . . . . . . . . . . . . . . . . . 270N  Table 204 - Read-write error recovery page. . . . . . . . . . . . . . . . 270N  Table 205 - Commands for printer devices. . . . . . . . . . . . . . . . . 274N  Table 206 - FORMAT command. . . . . . . . . . . . . . . . . . . . . . . . 275N  Table 207 - Format type . . . . . . . . . . . . . . . . . . . . . . . . . 275N  Table 208 - PRINT command . . . . . . . . . . . . . . . . . . . . . . . . 276N  Table 209 - RECOVER BUFFERED DATA command . . . . . . . . . . . . . . . . 276N  Table 210 - SLEW AND PRINT command. . . . . . . . . . . . . . . . . . . . 277N  Table 211 - STOP PRINT command. . . . . . . . . . . . . . . . . . . . . . 278N  Table 212 - SYNCHRONIZE BUFFER command. . . . . . . . . . . . . . . . . . 278N  Table 213 - Diagnostic page codes . . . . . . . . . . . . . . . . . . . . 279N  Table 214 - Log page codes. . . . . . . . . . . . . . . . . . . . . . . . 279N  Table 215 - Printer device-specific parameter . . . . . . . . . . . . . . 279N  Table 216 - Mode page codes . . . . . . . . . . . . . . . . . . . . . . . 280N  Table 217 - Parallel printer interface. . . . . . . . . . . . . . . . . . 280N  Table 218 - Parity select . . . . . . . . . . . . . . . . . . . . . . . . 281N  Table 219 - VFU control byte. . . . . . . . . . . . . . . . . . . . . . . 281N  Table 220 - Printer options . . . . . . . . . . . . . . . . . . . . . . . 282N  Table 221 - Font identification . . . . . . . . . . . . . . . . . . . . . 282N  Table 222 - Slew mode . . . . . . . . . . . . . . . . . . . . . . . . . . 283N  Table 223 - Line slew . . . . . . . . . . . . . . . . . . . . . . . . . . 283N  Table 224 - Form slew . . . . . . . . . . . . . . . . . . . . . . . . . . 284N  Table 225 - Data termination option . . . . . . . . . . . . . . . . . . . 284N  Table 226 - Serial printer interface. . . . . . . . . . . . . . . . . . . 285N  Table 227 - Parity selection. . . . . . . . . . . . . . . . . . . . . . . 286N  Table 228 - Pacing protocol . . . . . . . . . . . . . . . . . . . . . . . 286N  Table 229 - Commands for processor devices. . . . . . . . . . . . . . . . 289N  Table 230 - RECEIVE command . . . . . . . . . . . . . . . . . . . . . . . 289N  Table 231 - SEND command. . . . . . . . . . . . . . . . . . . . . . . . . 290N  Table 232 - SEND command - AEN data format. . . . . . . . . . . . . . . . 290N  Table 233 - Diagnostic page codes . . . . . . . . . . . . . . . . . . . . 291N  Table 234 - Log page codes. . . . . . . . . . . . . . . . . . . . . . . . 291N  Table 235 - Commands for write-once devices . . . . . . . . . . . . . . . 294N  Table 236 - Example mixed mode CD-ROM disc layout . . . . . . . . . . . . 298N  Table 237 - MSF address format. . . . . . . . . . . . . . . . . . . . . . 303N  Table 238 - Commands for CD-ROM device. . . . . . . . . . . . . . . . . . 305N  Table 239 - PAUSE RESUME command. . . . . . . . . . . . . . . . . . . . . 306N  Table 240 - PLAY AUDIO(10) command. . . . . . . . . . . . . . . . . . . . 307N  Table 241 - PLAY AUDIO(12) command. . . . . . . . . . . . . . . . . . . . 308N  Table 242 - PLAY AUDIO MSF command. . . . . . . . . . . . . . . . . . . . 309N  Table 243 - PLAY AUDIO TRACK INDEX command. . . . . . . . . . . . . . . . 310N  Table 244 - PLAY AUDIO TRACK RELATIVE(10) command . . . . . . . . . . . . 311N  Table 245 - PLAY AUDIO TRACK RELATIVE(12) command . . . . . . . . . . . . 312N  Table 246 - READ CD-ROM CAPACITY command. . . . . . . . . . . . . . . . . 313N  Table 247 - READ CAPACITY data format . . . . . . . . . . . . . . . . . . 314N  Table 248 - READ HEADER command . . . . . . . . . . . . . . . . . . . . . 314N  Table 249 - READ HEADER data format . . . . . . . . . . . . . . . . . . . 314N  Table 250 - CD-ROM data mode codes. . . . . . . . . . . . . . . . . . . . 315N  Table 251 - READ SUB-CHANNEL command. . . . . . . . . . . . . . . . . . . 316N  Table 252 - Sub-channel data format codes . . . . . . . . . . . . . . . . 316N  Table 253 - Sub-Q channel data format . . . . . . . . . . . . . . . . . . 317N  Table 254 - Audio status codes. . . . . . . . . . . . . . . . . . . . . . 318N  Table 255 - ADR sub-channel Q field . . . . . . . . . . . . . . . . . . . 318N  Table 256 - Sub-channel Q control bits. . . . . . . . . . . . . . . . . . 318N  Table 257 - CD-ROM current position data format . . . . . . . . . . . . . 320N  Table 258 - Media catalogue number data format. . . . . . . . . . . . . . 320N  Table 259 - Track international standard recording code data format . . . 321N  Table 260 - READ TOC command. . . . . . . . . . . . . . . . . . . . . . . 323N  Table 261 - READ TOC data format  . . . . . . . . . . . . . . . . . . . . 323N  Table 262 - Diagnostic page codes . . . . . . . . . . . . . . . . . . . . 325N  Table 263 - Log page codes. . . . . . . . . . . . . . . . . . . . . . . . 325N  Table 264 - CD-ROM medium type codes. . . . . . . . . . . . . . . . . . . 325N  Table 265 - CD-ROM device-specific parameter. . . . . . . . . . . . . . . 326N  Table 266 - CD-ROM density codes. . . . . . . . . . . . . . . . . . . . . 326N  Table 267 - Mode page codes . . . . . . . . . . . . . . . . . . . . . . . 327N  Table 268 - CD-ROM audio control parameters page. . . . . . . . . . . . . 327N  Table 269 - Multiplier for LBAs . . . . . . . . . . . . . . . . . . . . . 328N  Table 270 - Output port channel selection . . . . . . . . . . . . . . . . 328N  Table 271 - CD-ROM parameters page. . . . . . . . . . . . . . . . . . . . 329N  Table 272 - Inactivity timer multiplier values. . . . . . . . . . . . . . 329N  Table 273 - Read error recovery parameters page . . . . . . . . . . . . . 330N  Table 274 - Error recovery bit settings . . . . . . . . . . . . . . . . . 331N  Table 275 - CD-ROM error recovery descriptions. . . . . . . . . . . . . . 331N  Table 276 - Verify error recovery parameters page . . . . . . . . . . . . 336N  Table 277 - Commands for scanner devices. . . . . . . . . . . . . . . . . 340N  Table 278 - GET DATA BUFFER STATUS command. . . . . . . . . . . . . . . . 341N  Table 279 - Data buffer status format . . . . . . . . . . . . . . . . . . 341N  Table 280 - GET WINDOW command. . . . . . . . . . . . . . . . . . . . . . 343N  Table 281 - Get window data header. . . . . . . . . . . . . . . . . . . . 343N  Table 282 - Window descriptor bytes . . . . . . . . . . . . . . . . . . . 344N  Table 283 - Image composition codes . . . . . . . . . . . . . . . . . . . 345N  Table 284 - Padding types . . . . . . . . . . . . . . . . . . . . . . . . 346N  Table 285 - Compression types and arguments . . . . . . . . . . . . . . . 346N  Table 286 - OBJECT POSITION command . . . . . . . . . . . . . . . . . . . 347N  Table 287 - Position function . . . . . . . . . . . . . . . . . . . . . . 347N  Table 288 - READ command. . . . . . . . . . . . . . . . . . . . . . . . . 349N  Table 289 - Data type codes . . . . . . . . . . . . . . . . . . . . . . . 349N  Table 290 - SCAN command. . . . . . . . . . . . . . . . . . . . . . . . . 350N  Table 291 - SEND command. . . . . . . . . . . . . . . . . . . . . . . . . 350N  Table 292 - SET WINDOW command. . . . . . . . . . . . . . . . . . . . . . 351N  Table 293 - Set window data header. . . . . . . . . . . . . . . . . . . . 351N  Table 294 - Diagnostic page codes . . . . . . . . . . . . . . . . . . . . 352N  Table 295 - Log page codes. . . . . . . . . . . . . . . . . . . . . . . . 352N  Table 296 - Mode page codes . . . . . . . . . . . . . . . . . . . . . . . 353N  Table 297 - Measurement units page. . . . . . . . . . . . . . . . . . . . 353N  Table 298 - Basic measurement units . . . . . . . . . . . . . . . . . . . 354N  Table 299 - Commands for optical memory devices . . . . . . . . . . . . . 359N  Table 300 - ERASE(10) command . . . . . . . . . . . . . . . . . . . . . . 360N  Table 301 - ERASE(12) command . . . . . . . . . . . . . . . . . . . . . . 361N  Table 302 - MEDIUM SCAN command . . . . . . . . . . . . . . . . . . . . . 362N  Table 303 - MEDIUM SCAN parameter list. . . . . . . . . . . . . . . . . . 363N  Table 304 - READ(12) command. . . . . . . . . . . . . . . . . . . . . . . 364N  Table 305 - READ DEFECT DATA(12) command. . . . . . . . . . . . . . . . . 364N  Table 306 - READ DEFECT DATA(12) list header. . . . . . . . . . . . . . . 365N  Table 307 - READ GENERATION command . . . . . . . . . . . . . . . . . . . 366N  Table 308 - Maximum generation data block . . . . . . . . . . . . . . . . 366N  Table 309 - READ UPDATED BLOCK(10) command. . . . . . . . . . . . . . . . 367N  Table 310 - SEARCH DATA(12) commands. . . . . . . . . . . . . . . . . . . 368N  Table 311 - SET LIMITS(12) command. . . . . . . . . . . . . . . . . . . . 368N  Table 312 - UPDATE BLOCK command. . . . . . . . . . . . . . . . . . . . . 369N  Table 313 - VERIFY command. . . . . . . . . . . . . . . . . . . . . . . . 370N  Table 314 - VERIFY(12) command. . . . . . . . . . . . . . . . . . . . . . 371N  Table 315 - WRITE(10) command . . . . . . . . . . . . . . . . . . . . . . 372N  Table 316 - WRITE(12) command . . . . . . . . . . . . . . . . . . . . . . 373N  Table 317 - WRITE AND VERIFY(10) command. . . . . . . . . . . . . . . . . 373N  Table 318 - WRITE AND VERIFY(12) command. . . . . . . . . . . . . . . . . 374N  Table 319 - Diagnostic page codes . . . . . . . . . . . . . . . . . . . . 375N  Table 320 - Log page codes. . . . . . . . . . . . . . . . . . . . . . . . 375N  Table 321 - Optical memory medium-type codes. . . . . . . . . . . . . . . 375N  Table 322 - Optical memory device specific parameter. . . . . . . . . . . 376N  Table 323 - Optical memory density codes. . . . . . . . . . . . . . . . . 376N  Table 324 - Mode page codes . . . . . . . . . . . . . . . . . . . . . . . 377N  Table 325 - Optical memory page . . . . . . . . . . . . . . . . . . . . . 378N  Table 326 - Volume tag information format . . . . . . . . . . . . . . . . 382N  Table 327 - Commands for medium changer devices . . . . . . . . . . . . . 383N  Table 328 - EXCHANGE MEDIUM command . . . . . . . . . . . . . . . . . . . 384N  Table 329 - INITIALIZE ELEMENT STATUS command . . . . . . . . . . . . . . 385N  Table 330 - MOVE MEDIUM command . . . . . . . . . . . . . . . . . . . . . 386N  Table 331 - POSITION TO ELEMENT command . . . . . . . . . . . . . . . . . 387N  Table 332 - READ ELEMENT STATUS command . . . . . . . . . . . . . . . . . 388N  Table 333 - Element type code . . . . . . . . . . . . . . . . . . . . . . 388N  Table 334 - Element status data . . . . . . . . . . . . . . . . . . . . . 389N  Table 335 - Element status page . . . . . . . . . . . . . . . . . . . . . 391N  Table 336 - Medium transport element descriptor . . . . . . . . . . . . . 392N  Table 337 - Storage element descriptor. . . . . . . . . . . . . . . . . . 393N  Table 338 - Import export element descriptor. . . . . . . . . . . . . . . 394N  Table 339 - Data transfer element descriptor. . . . . . . . . . . . . . . 395N  Table 340 - REQUEST VOLUME ELEMENT ADDRESS command. . . . . . . . . . . . 396N  Table 341 - Volume element address header format. . . . . . . . . . . . . 397N  Table 342 - RELEASE command . . . . . . . . . . . . . . . . . . . . . . . 398N  Table 343 - RESERVE command . . . . . . . . . . . . . . . . . . . . . . . 399N  Table 344 - Data format of element list descriptors . . . . . . . . . . . 400N  Table 345 - SEND VOLUME TAG command . . . . . . . . . . . . . . . . . . . 401N  Table 346 - Send volume tag action codes. . . . . . . . . . . . . . . . . 402N  Table 347 - Send volume tag parameters format . . . . . . . . . . . . . . 402N  Table 348 - Diagnostic page codes . . . . . . . . . . . . . . . . . . . . 404N  Table 349 - Log page codes. . . . . . . . . . . . . . . . . . . . . . . . 404N  Table 350 - Mode page codes . . . . . . . . . . . . . . . . . . . . . . . 405N  Table 351 - Device capabilities page. . . . . . . . . . . . . . . . . . . 405N  Table 352 - Element address assignment page . . . . . . . . . . . . . . . 406N  Table 353 - Transport geometry parameters page. . . . . . . . . . . . . . 409N  Table 354 - Commands for communications devices . . . . . . . . . . . . . 413N  Table 355 - GET MESSAGE(6) command. . . . . . . . . . . . . . . . . . . . 414N  Table 356 - GET MESSAGE(10) command . . . . . . . . . . . . . . . . . . . 414N  Table 357 - GET MESSAGE(12) command . . . . . . . . . . . . . . . . . . . 415N  Table 358 - SEND MESSAGE(6) command . . . . . . . . . . . . . . . . . . . 416N  Table 359 - SEND MESSAGE(10) command. . . . . . . . . . . . . . . . . . . 416N  Table 360 - SEND MESSAGE(12) command. . . . . . . . . . . . . . . . . . . 417N  Table 361 - Diagnostic page codes . . . . . . . . . . . . . . . . . . . . 418N  Table 362 - Log page codes. . . . . . . . . . . . . . . . . . . . . . . . 418N  Table 363 - Mode page codes . . . . . . . . . . . . . . . . . . . . . . . 419N  Table B.1 - Fast SCSI jitter budget . . . . . . . . . . . . . . . . . . . 425N  Table B.2 - Mapping of jitter to SCSI . . . . . . . . . . . . . . . . . . 425N  Table D.1 - ASC and ASCQ assignments. . . . . . . . . . . . . . . . . . . 429N  Table D.2 - SCSI-2 Operation Codes. . . . . . . . . . . . . . . . . . . . 435N  Table E.1 - Vendor identification list. . . . . . . . . . . . . . . . . . 439N  Table 1 - Cross-reference to connector contact assignments. . . . . . . .  20N  Table 2 - Single-ended contact assignments - A cable. . . . . . . . . . .  20N  Table 3 - Single-ended contact assignments - B cable. . . . . . . . . . .  21N  Table 4 - Differential contact assignments - A cable. . . . . . . . . . .  22N  Table 5 - Differential contact assignments - B cable. . . . . . . . . . .  23N  Table 6 - Signal sources. . . . . . . . . . . . . . . . . . . . . . . . .  33N  Table 7 - SCSI bus timing values. . . . . . . . . . . . . . . . . . . . .  35N  Table 8 - Information transfer phases . . . . . . . . . . . . . . . . . .  43N  Table 9 - Message format. . . . . . . . . . . . . . . . . . . . . . . . .  53N  Table 10 - Message codes. . . . . . . . . . . . . . . . . . . . . . . . .  53N  Table 11 - Extended message format. . . . . . . . . . . . . . . . . . . .  55N  Table 12 - Extended message codes . . . . . . . . . . . . . . . . . . . .  55N  Table 13 - IDENTIFY message format. . . . . . . . . . . . . . . . . . . .  58N  Table 14 - IGNORE WIDE RESIDUE message format . . . . . . . . . . . . . .  59N  Table 15 - Ignore field definition. . . . . . . . . . . . . . . . . . . .  59N  Table 16 - MODIFY DATA POINTER. . . . . . . . . . . . . . . . . . . . . .  61N  Table 17 - Queue tag message format . . . . . . . . . . . . . . . . . . .  61N  Table 18 - SYNCHRONOUS DATA TRANSFER REQUEST. . . . . . . . . . . . . . .  63N  Table 19 - WIDE DATA TRANSFER MESSAGE . . . . . . . . . . . . . . . . . .  65N  Table 20 - Operation code type. . . . . . . . . . . . . . . . . . . . . .  68N  Table 21 - Typical command descriptor block for six-byte commands . . . .  69N  Table 22 - Typical command descriptor block for ten-byte commands . . . .  69N  Table 23 - Typical command descriptor block for twelve-byte commands. . .  69N  Table 24 - Operation code . . . . . . . . . . . . . . . . . . . . . . . .  71N  Table 25 - Control field. . . . . . . . . . . . . . . . . . . . . . . . .  72N  Table 26 - Status byte. . . . . . . . . . . . . . . . . . . . . . . . . .  73N  Table 27 - Status byte code . . . . . . . . . . . . . . . . . . . . . . .  73N  Table 28 - Commands in order received by target . . . . . . . . . . . . .  83N  Table 29 - Commands in order of execution . . . . . . . . . . . . . . . .  84N  Table 30 - Modified by HEAD OF QUEUE TAG message. . . . . . . . . . . . .  84N  Table 31 - Commands for all device types. . . . . . . . . . . . . . . . .  88N  Table 32 - CHANGE DEFINITION command. . . . . . . . . . . . . . . . . . .  89N  Table 33 - Definition parameter field . . . . . . . . . . . . . . . . . .  90N  Table 34 - COMPARE command. . . . . . . . . . . . . . . . . . . . . . . .  91N  Table 35 - COPY command . . . . . . . . . . . . . . . . . . . . . . . . .  92N  Table 36 - COPY parameter list. . . . . . . . . . . . . . . . . . . . . .  92N  Table 37 - COPY function codes. . . . . . . . . . . . . . . . . . . . . .  93N  Table 38 - Segment descriptor for COPY function codes 00h and 01h . . . .  95N  Table 39 - Segment descriptor for COPY function code 02h. . . . . . . . .  96N  Table 40 - Segment descriptor for COPY function code 03h. . . . . . . . .  96N  Table 41 - Segment descriptor for COPY function code 04h. . . . . . . . .  98N  Table 42 - Pad and cat bit definition . . . . . . . . . . . . . . . . . .  98N  Table 43 - COPY AND VERIFY command. . . . . . . . . . . . . . . . . . . .  99N  Table 44 - INQUIRY command. . . . . . . . . . . . . . . . . . . . . . . . 100N  Table 45 - Standard INQUIRY data format . . . . . . . . . . . . . . . . . 101N  Table 46 - Peripheral qualifier . . . . . . . . . . . . . . . . . . . . . 101N  Table 47 - Peripheral device type . . . . . . . . . . . . . . . . . . . . 102N  Table 48 - ANSI-approved version. . . . . . . . . . . . . . . . . . . . . 103N  Table 49 - LOG SELECT command . . . . . . . . . . . . . . . . . . . . . . 105N  Table 50 - Page control field . . . . . . . . . . . . . . . . . . . . . . 106N  Table 51 - LOG SENSE command. . . . . . . . . . . . . . . . . . . . . . . 107N  Table 52 - MODE SELECT(6) command . . . . . . . . . . . . . . . . . . . . 108N  Table 53 - MODE SELECT(10) command. . . . . . . . . . . . . . . . . . . . 110N  Table 54 - MODE SENSE(6) command. . . . . . . . . . . . . . . . . . . . . 111N  Table 55 - Page control field . . . . . . . . . . . . . . . . . . . . . . 111N  Table 56 - Mode page code usage for all devices . . . . . . . . . . . . . 111N  Table 57 - MODE SENSE(10) command . . . . . . . . . . . . . . . . . . . . 113N  Table 58 - READ BUFFER command. . . . . . . . . . . . . . . . . . . . . . 114N  Table 59 - READ BUFFER mode field . . . . . . . . . . . . . . . . . . . . 114N  Table 60 - READ BUFFER header . . . . . . . . . . . . . . . . . . . . . . 114N  Table 61 - READ BUFFER descriptor . . . . . . . . . . . . . . . . . . . . 115N  Table 62 - Buffer offset boundary . . . . . . . . . . . . . . . . . . . . 116N  Table 63 - RECEIVE DIAGNOSTIC RESULTS command . . . . . . . . . . . . . . 117N  Table 64 - REQUEST SENSE command. . . . . . . . . . . . . . . . . . . . . 118N  Table 65 - Error codes 70h and 71h sense data format. . . . . . . . . . . 119N  Table 66 - Field pointer bytes. . . . . . . . . . . . . . . . . . . . . . 121N  Table 67 - Actual retry count bytes . . . . . . . . . . . . . . . . . . . 121N  Table 68 - Format progress indication bytes . . . . . . . . . . . . . . . 122N  Table 69 - Sense key (0h-7h) descriptions . . . . . . . . . . . . . . . . 124N  Table 70 - Sense key (8h-Fh) descriptions . . . . . . . . . . . . . . . . 125N  Table 71 - ASC and ASCQ assignments . . . . . . . . . . . . . . . . . . . 126N  Table 72 - SEND DIAGNOSTIC command. . . . . . . . . . . . . . . . . . . . 130N  Table 73 - TEST UNIT READY command. . . . . . . . . . . . . . . . . . . . 131N  Table 74 - Preferred TEST UNIT READY responses. . . . . . . . . . . . . . 131N  Table 75 - WRITE BUFFER command . . . . . . . . . . . . . . . . . . . . . 132N  Table 76 - WRITE BUFFER mode field. . . . . . . . . . . . . . . . . . . . 133N  Table 77 - Diagnostic page format . . . . . . . . . . . . . . . . . . . . 134N  Table 78 - Diagnostic page codes. . . . . . . . . . . . . . . . . . . . . 135N  Table 79 - Supported diagnostic pages . . . . . . . . . . . . . . . . . . 135N  Table 80 - Log page format. . . . . . . . . . . . . . . . . . . . . . . . 136N  Table 81 - Log parameter. . . . . . . . . . . . . . . . . . . . . . . . . 136N  Table 82 - Threshold met criteria . . . . . . . . . . . . . . . . . . . . 138N  Table 83 - Log page codes . . . . . . . . . . . . . . . . . . . . . . . . 139>  Table 84 - Parameter code field for buffer over-run/under-runN     counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139N  Table 85 - Count basis definition . . . . . . . . . . . . . . . . . . . . 140N  Table 86 - Cause field definition . . . . . . . . . . . . . . . . . . . . 140N  Table 87 - Parameter codes for error counter pages. . . . . . . . . . . . 140N  Table 88 - Non-medium error event parameter codes . . . . . . . . . . . . 141N  Table 89 - Supported log pages. . . . . . . . . . . . . . . . . . . . . . 142N  Table 90 - Mode parameter list. . . . . . . . . . . . . . . . . . . . . . 142N  Table 91 - Mode parameter header(6) . . . . . . . . . . . . . . . . . . . 142N  Table 92 - Mode parameter header(10). . . . . . . . . . . . . . . . . . . 143N  Table 93 - Mode parameter block descriptor. . . . . . . . . . . . . . . . 144N  Table 94 - Mode page format . . . . . . . . . . . . . . . . . . . . . . . 144N  Table 95 - Mode page codes. . . . . . . . . . . . . . . . . . . . . . . . 145N  Table 96 - Control mode page. . . . . . . . . . . . . . . . . . . . . . . 145N  Table 97 - Queue algorithm modifier . . . . . . . . . . . . . . . . . . . 146N  Table 98 - Disconnect-reconnect page. . . . . . . . . . . . . . . . . . . 148N  Table 99 - Data transfer disconnect control . . . . . . . . . . . . . . . 149N  Table 100 - Peripheral device page. . . . . . . . . . . . . . . . . . . . 150N  Table 101 - Interface identifier codes. . . . . . . . . . . . . . . . . . 150N  Table 102 - Vital product data page codes . . . . . . . . . . . . . . . . 150N  Table 103 - ASCII implemented operating definition  . . . . . . . . . . . 151N  Table 104 - ASCII information page. . . . . . . . . . . . . . . . . . . . 152N  Table 105 - Implemented operating definition page . . . . . . . . . . . . 152N  Table 106 - Supported vital product data pages. . . . . . . . . . . . . . 154N  Table 107 - Unit serial number page . . . . . . . . . . . . . . . . . . . 155N  Table 108 - Commands for direct-access devices. . . . . . . . . . . . . . 163N  Table 109 - FORMAT UNIT command . . . . . . . . . . . . . . . . . . . . . 164N  Table 110 - FORMAT UNIT parameter list. . . . . . . . . . . . . . . . . . 165N  Table 111 - Defect list header. . . . . . . . . . . . . . . . . . . . . . 165N  Table 112 - FORMAT UNIT defect descriptor format and requirements . . . . 166N  Table 113 - Defect descriptor - Block format. . . . . . . . . . . . . . . 169N  Table 114 - Defect descriptor - Bytes from index format . . . . . . . . . 169N  Table 115 - Defect descriptor - Physical sector format. . . . . . . . . . 170N  Table 116 - Initialization pattern descriptor . . . . . . . . . . . . . . 170N  Table 117 - Initialization pattern modifier . . . . . . . . . . . . . . . 170N  Table 118 - Initialization pattern type . . . . . . . . . . . . . . . . . 171N  Table 119 - LOCK UNLOCK CACHE command . . . . . . . . . . . . . . . . . . 172N  Table 120 - PRE-FETCH command . . . . . . . . . . . . . . . . . . . . . . 173N  Table 121 - PREVENT ALLOW MEDIUM REMOVAL command. . . . . . . . . . . . . 174N  Table 122 - READ(6) command . . . . . . . . . . . . . . . . . . . . . . . 175N  Table 123 - READ(10) command. . . . . . . . . . . . . . . . . . . . . . . 176N  Table 124 - READ CAPACITY command . . . . . . . . . . . . . . . . . . . . 177N  Table 125 - READ CAPACITY data. . . . . . . . . . . . . . . . . . . . . . 177N  Table 126 - READ DEFECT DATA command. . . . . . . . . . . . . . . . . . . 178N  Table 127 - READ DEFECT DATA defect list. . . . . . . . . . . . . . . . . 179N  Table 128 - READ LONG command . . . . . . . . . . . . . . . . . . . . . . 180N  Table 129 - REASSIGN BLOCKS command . . . . . . . . . . . . . . . . . . . 181N  Table 130 - REASSIGN BLOCKS defect list . . . . . . . . . . . . . . . . . 181N  Table 131 - RELEASE command . . . . . . . . . . . . . . . . . . . . . . . 182N  Table 132 - RESERVE command . . . . . . . . . . . . . . . . . . . . . . . 184N  Table 133 - Data format of extent descriptors . . . . . . . . . . . . . . 185N  Table 134 - Reservation types . . . . . . . . . . . . . . . . . . . . . . 185N  Table 135 - REZERO UNIT command . . . . . . . . . . . . . . . . . . . . . 187N  Table 136 - SEARCH DATA commands. . . . . . . . . . . . . . . . . . . . . 188N  Table 137 - SEARCH DATA parameter list. . . . . . . . . . . . . . . . . . 189N  Table 138 - SEEK(6) command . . . . . . . . . . . . . . . . . . . . . . . 191N  Table 139 - SEEK(10) command. . . . . . . . . . . . . . . . . . . . . . . 191N  Table 140 - SET LIMITS command. . . . . . . . . . . . . . . . . . . . . . 192N  Table 141 - START STOP UNIT command . . . . . . . . . . . . . . . . . . . 193N  Table 142 - SYNCHRONIZE CACHE command . . . . . . . . . . . . . . . . . . 194N  Table 143 - VERIFY command. . . . . . . . . . . . . . . . . . . . . . . . 195N  Table 144 - WRITE(6) command. . . . . . . . . . . . . . . . . . . . . . . 196N  Table 145 - WRITE(10) command . . . . . . . . . . . . . . . . . . . . . . 197N  Table 146 - WRITE AND VERIFY command. . . . . . . . . . . . . . . . . . . 198N  Table 147 - WRITE LONG command. . . . . . . . . . . . . . . . . . . . . . 199N  Table 148 - WRITE SAME command. . . . . . . . . . . . . . . . . . . . . . 200N  Table 149 - Diagnostic page codes . . . . . . . . . . . . . . . . . . . . 201N  Table 150 - Translate address page - SEND DIAGNOSTIC. . . . . . . . . . . 201N  Table 151 - Translate address page - RECEIVE DIAGNOSTIC . . . . . . . . . 202N  Table 152 - Log page codes. . . . . . . . . . . . . . . . . . . . . . . . 203N  Table 153 - Direct-access medium-type codes . . . . . . . . . . . . . . . 203N  Table 154 - Device specific parameter . . . . . . . . . . . . . . . . . . 204N  Table 155 - Mode page codes . . . . . . . . . . . . . . . . . . . . . . . 205N  Table 156 - Caching page. . . . . . . . . . . . . . . . . . . . . . . . . 205N  Table 157 - Demand read and write retention priority. . . . . . . . . . . 206N  Table 158 - Flexible disk page. . . . . . . . . . . . . . . . . . . . . . 208N  Table 159 - Examples of transfer rates. . . . . . . . . . . . . . . . . . 209N  Table 160 - Pin 34 field. . . . . . . . . . . . . . . . . . . . . . . . . 210N  Table 161 - Pin 4 field . . . . . . . . . . . . . . . . . . . . . . . . . 210N  Table 162 - Pin 34 field. . . . . . . . . . . . . . . . . . . . . . . . . 211N  Table 163 - Format device page. . . . . . . . . . . . . . . . . . . . . . 211N  Table 164 - Reporting of default sector formatting support. . . . . . . . 213N  Table 165 - Reporting of changeable sector formatting support . . . . . . 214N  Table 166 - Medium types supported page . . . . . . . . . . . . . . . . . 214N  Table 167 - Notch page. . . . . . . . . . . . . . . . . . . . . . . . . . 215N  Table 168 - Read-write error recovery page. . . . . . . . . . . . . . . . 217N  Table 169 - Error recovery bit definitions. . . . . . . . . . . . . . . . 218N  Table 170 - Combined error recovery parameter descriptions. . . . . . . . 219N  Table 171 - Rigid disk drive geometry page. . . . . . . . . . . . . . . . 224N  Table 172 - Rotational position locking . . . . . . . . . . . . . . . . . 225N  Table 173 - Verify error recovery page. . . . . . . . . . . . . . . . . . 226N  Table 174 - Commands for sequential-access devices. . . . . . . . . . . . 236N  Table 175 - ERASE command . . . . . . . . . . . . . . . . . . . . . . . . 238N  Table 176 - LOAD UNLOAD command . . . . . . . . . . . . . . . . . . . . . 239N  Table 177 - LOCATE command. . . . . . . . . . . . . . . . . . . . . . . . 240N  Table 178 - READ command. . . . . . . . . . . . . . . . . . . . . . . . . 241N  Table 179 - READ BLOCK LIMITS command . . . . . . . . . . . . . . . . . . 243N  Table 180 - READ BLOCK LIMITS data. . . . . . . . . . . . . . . . . . . . 243N  Table 181 - READ POSITION command . . . . . . . . . . . . . . . . . . . . 244N  Table 182 - READ POSITION data format . . . . . . . . . . . . . . . . . . 244N  Table 183 - READ REVERSE command. . . . . . . . . . . . . . . . . . . . . 246N  Table 184 - RECOVER BUFFERED DATA command . . . . . . . . . . . . . . . . 247N  Table 185 - RELEASE UNIT command. . . . . . . . . . . . . . . . . . . . . 248N  Table 186 - RESERVE UNIT command. . . . . . . . . . . . . . . . . . . . . 249N  Table 187 - REWIND command. . . . . . . . . . . . . . . . . . . . . . . . 250N  Table 188 - SPACE command . . . . . . . . . . . . . . . . . . . . . . . . 251N  Table 189 - Code field definition . . . . . . . . . . . . . . . . . . . . 251N  Table 190 - VERIFY command. . . . . . . . . . . . . . . . . . . . . . . . 253N  Table 191 - WRITE command . . . . . . . . . . . . . . . . . . . . . . . . 254N  Table 192 - WRITE FILEMARKS command . . . . . . . . . . . . . . . . . . . 256N  Table 193 - Diagnostic page codes . . . . . . . . . . . . . . . . . . . . 257N  Table 194 - Log page codes. . . . . . . . . . . . . . . . . . . . . . . . 257N  Table 195 - Device-specific parameter . . . . . . . . . . . . . . . . . . 258N  Table 196 - Buffered modes. . . . . . . . . . . . . . . . . . . . . . . . 258N  Table 197 - Speed field definition. . . . . . . . . . . . . . . . . . . . 258N  Table 198 - Sequential-access density codes . . . . . . . . . . . . . . . 259N  Table 199 - Mode page codes . . . . . . . . . . . . . . . . . . . . . . . 260N  Table 200 - Device configuration page . . . . . . . . . . . . . . . . . . 261N  Table 201 - EOD formats . . . . . . . . . . . . . . . . . . . . . . . . . 263N  Table 202 - Medium partition page(1). . . . . . . . . . . . . . . . . . . 264N  Table 203 - Medium partition page(2-4). . . . . . . . . . . . . . . . . . 265N  Table 204 - Read-write error recovery page. . . . . . . . . . . . . . . . 265N  Table 205 - Commands for printer devices. . . . . . . . . . . . . . . . . 269N  Table 206 - FORMAT command. . . . . . . . . . . . . . . . . . . . . . . . 270N  Table 207 - Format type . . . . . . . . . . . . . . . . . . . . . . . . . 270N  Table 208 - PRINT command . . . . . . . . . . . . . . . . . . . . . . . . 271N  Table 209 - RECOVER BUFFERED DATA command . . . . . . . . . . . . . . . . 271N  Table 210 - SLEW AND PRINT command. . . . . . . . . . . . . . . . . . . . 272N  Table 211 - STOP PRINT command. . . . . . . . . . . . . . . . . . . . . . 273N  Table 212 - SYNCHRONIZE BUFFER command. . . . . . . . . . . . . . . . . . 273N  Table 213 - Diagnostic page codes . . . . . . . . . . . . . . . . . . . . 274N  Table 214 - Log page codes. . . . . . . . . . . . . . . . . . . . . . . . 274N  Table 215 - Printer device-specific parameter . . . . . . . . . . . . . . 274N  Table 216 - Mode page codes . . . . . . . . . . . . . . . . . . . . . . . 275N  Table 217 - Parallel printer interface. . . . . . . . . . . . . . . . . . 275N  Table 218 - Parity select . . . . . . . . . . . . . . . . . . . . . . . . 276N  Table 219 - VFU control byte. . . . . . . . . . . . . . . . . . . . . . . 276N  Table 220 - Printer options . . . . . . . . . . . . . . . . . . . . . . . 277N  Table 221 - Font identification . . . . . . . . . . . . . . . . . . . . . 277N  Table 222 - Slew mode . . . . . . . . . . . . . . . . . . . . . . . . . . 278N  Table 223 - Line slew . . . . . . . . . . . . . . . . . . . . . . . . . . 278N  Table 224 - Form slew . . . . . . . . . . . . . . . . . . . . . . . . . . 279N  Table 225 - Data termination option . . . . . . . . . . . . . . . . . . . 279N  Table 226 - Serial printer interface. . . . . . . . . . . . . . . . . . . 280N  Table 227 - Parity selection. . . . . . . . . . . . . . . . . . . . . . . 281N  Table 228 - Pacing protocol . . . . . . . . . . . . . . . . . . . . . . . 281N  Table 229 - Commands for processor devices. . . . . . . . . . . . . . . . 284N  Table 230 - RECEIVE command . . . . . . . . . . . . . . . . . . . . . . . 284N  Table 231 - SEND command. . . . . . . . . . . . . . . . . . . . . . . . . 285N  Table 232 - SEND command - AEN data format. . . . . . . . . . . . . . . . 285N  Table 233 - Diagnostic page codes . . . . . . . . . . . . . . . . . . . . 286N  Table 234 - Log page codes. . . . . . . . . . . . . . . . . . . . . . . . 286N  Table 235 - Commands for write-once devices . . . . . . . . . . . . . . . 289N  Table 236 - Example mixed mode CD-ROM disc layout . . . . . . . . . . . . 293N  Table 237 - MSF address format. . . . . . . . . . . . . . . . . . . . . . 298N  Table 238 - Commands for CD-ROM device. . . . . . . . . . . . . . . . . . 300N  Table 239 - PAUSE RESUME command. . . . . . . . . . . . . . . . . . . . . 301N  Table 240 - PLAY AUDIO(10) command. . . . . . . . . . . . . . . . . . . . 302N  Table 241 - PLAY AUDIO(12) command. . . . . . . . . . . . . . . . . . . . 303N  Table 242 - PLAY AUDIO MSF command. . . . . . . . . . . . . . . . . . . . 304N  Table 243 - PLAY AUDIO TRACK INDEX command. . . . . . . . . . . . . . . . 305N  Table 244 - PLAY AUDIO TRACK RELATIVE(10) command . . . . . . . . . . . . 306N  Table 245 - PLAY AUDIO TRACK RELATIVE(12) command . . . . . . . . . . . . 307N  Table 246 - READ CD-ROM CAPACITY command. . . . . . . . . . . . . . . . . 308N  Table 247 - READ CAPACITY data format . . . . . . . . . . . . . . . . . . 309N  Table 248 - READ HEADER command . . . . . . . . . . . . . . . . . . . . . 309N  Table 249 - READ HEADER data format . . . . . . . . . . . . . . . . . . . 309N  Table 250 - CD-ROM data mode codes. . . . . . . . . . . . . . . . . . . . 310N  Table 251 - READ SUB-CHANNEL command. . . . . . . . . . . . . . . . . . . 311N  Table 252 - Sub-channel data format codes . . . . . . . . . . . . . . . . 311N  Table 253 - Sub-Q channel data format . . . . . . . . . . . . . . . . . . 312N  Table 254 - Audio status codes. . . . . . . . . . . . . . . . . . . . . . 313N  Table 255 - ADR sub-channel Q field . . . . . . . . . . . . . . . . . . . 313N  Table 256 - Sub-channel Q control bits. . . . . . . . . . . . . . . . . . 313N  Table 257 - CD-ROM current position data format . . . . . . . . . . . . . 315N  Table 258 - Media catalogue number data format. . . . . . . . . . . . . . 315N  Table 259 - Track international standard recording code data format . . . 316N  Table 260 - READ TOC command. . . . . . . . . . . . . . . . . . . . . . . 318N  Table 261 - READ TOC data format  . . . . . . . . . . . . . . . . . . . . 318N  Table 262 - Diagnostic page codes . . . . . . . . . . . . . . . . . . . . 320N  Table 263 - Log page codes. . . . . . . . . . . . . . . . . . . . . . . . 320N  Table 264 - CD-ROM medium type codes. . . . . . . . . . . . . . . . . . . 320N  Table 265 - CD-ROM device-specific parameter. . . . . . . . . . . . . . . 321N  Table 266 - CD-ROM density codes. . . . . . . . . . . . . . . . . . . . . 321N  Table 267 - Mode page codes . . . . . . . . . . . . . . . . . . . . . . . 322N  Table 268 - CD-ROM audio control parameters page. . . . . . . . . . . . . 322N  Table 269 - Multiplier for LBAs . . . . . . . . . . . . . . . . . . . . . 323N  Table 270 - Output port channel selection . . . . . . . . . . . . . . . . 323N  Table 271 - CD-ROM parameters page. . . . . . . . . . . . . . . . . . . . 324N  Table 272 - Inactivity timer multiplier values. . . . . . . . . . . . . . 324N  Table 273 - Read error recovery parameters page . . . . . . . . . . . . . 325N  Table 274 - Error recovery bit settings . . . . . . . . . . . . . . . . . 326N  Table 275 - CD-ROM error recovery descriptions. . . . . . . . . . . . . . 326N  Table 276 - Verify error recovery parameters page . . . . . . . . . . . . 331N  Table 277 - Commands for scanner devices. . . . . . . . . . . . . . . . . 335N  Table 278 - GET DATA BUFFER STATUS command. . . . . . . . . . . . . . . . 336N  Table 279 - Data buffer status format . . . . . . . . . . . . . . . . . . 336N  Table 280 - GET WINDOW command. . . . . . . . . . . . . . . . . . . . . . 338N  Table 281 - Get window data header. . . . . . . . . . . . . . . . . . . . 338N  Table 282 - Window descriptor bytes . . . . . . . . . . . . . . . . . . . 339N  Table 283 - Image composition codes . . . . . . . . . . . . . . . . . . . 340N  Table 284 - Padding types . . . . . . . . . . . . . . . . . . . . . . . . 341N  Table 285 - Compression types and arguments . . . . . . . . . . . . . . . 341N  Table 286 - OBJECT POSITION command . . . . . . . . . . . . . . . . . . . 342N  Table 287 - Position function . . . . . . . . . . . . . . . . . . . . . . 342N  Table 288 - READ command. . . . . . . . . . . . . . . . . . . . . . . . . 344N  Table 289 - Data type codes . . . . . . . . . . . . . . . . . . . . . . . 344N  Table 290 - SCAN command. . . . . . . . . . . . . . . . . . . . . . . . . 345N  Table 291 - SEND command. . . . . . . . . . . . . . . . . . . . . . . . . 345N  Table 292 - SET WINDOW command. . . . . . . . . . . . . . . . . . . . . . 346N  Table 293 - Set window data header. . . . . . . . . . . . . . . . . . . . 346N  Table 294 - Diagnostic page codes . . . . . . . . . . . . . . . . . . . . 347N  Table 295 - Log page codes. . . . . . . . . . . . . . . . . . . . . . . . 347N  Table 296 - Mode page codes . . . . . . . . . . . . . . . . . . . . . . . 348N  Table 297 - Measurement units page. . . . . . . . . . . . . . . . . . . . 348N  Table 298 - Basic measurement units . . . . . . . . . . . . . . . . . . . 349N  Table 299 - Commands for optical memory devices . . . . . . . . . . . . . 353N  Table 300 - ERASE(10) command . . . . . . . . . . . . . . . . . . . . . . 354N  Table 301 - ERASE(12) command . . . . . . . . . . . . . . . . . . . . . . 355N  Table 302 - MEDIUM SCAN command . . . . . . . . . . . . . . . . . . . . . 356N  Table 303 - MEDIUM SCAN parameter list. . . . . . . . . . . . . . . . . . 357N  Table 304 - READ(12) command. . . . . . . . . . . . . . . . . . . . . . . 358N  Table 305 - READ DEFECT DATA(12) command. . . . . . . . . . . . . . . . . 358N  Table 306 - READ DEFECT DATA(12) list header. . . . . . . . . . . . . . . 359N  Table 307 - READ GENERATION command . . . . . . . . . . . . . . . . . . . 360N  Table 308 - Maximum generation data block . . . . . . . . . . . . . . . . 360N  Table 309 - READ UPDATED BLOCK(10) command. . . . . . . . . . . . . . . . 361N  Table 310 - SEARCH DATA(12) commands. . . . . . . . . . . . . . . . . . . 362N  Table 311 - SET LIMITS(12) command. . . . . . . . . . . . . . . . . . . . 362N  Table 312 - UPDATE BLOCK command. . . . . . . . . . . . . . . . . . . . . 363N  Table 313 - VERIFY command. . . . . . . . . . . . . . . . . . . . . . . . 364N  Table 314 - VERIFY(12) command. . . . . . . . . . . . . . . . . . . . . . 365N  Table 315 - WRITE(10) command . . . . . . . . . . . . . . . . . . . . . . 366N  Table 316 - WRITE(12) command . . . . . . . . . . . . . . . . . . . . . . 367N  Table 317 - WRITE AND VERIFY(10) command. . . . . . . . . . . . . . . . . 367N  Table 318 - WRITE AND VERIFY(12) command. . . . . . . . . . . . . . . . . 368N  Table 319 - Diagnostic page codes . . . . . . . . . . . . . . . . . . . . 369N  Table 320 - Log page codes. . . . . . . . . . . . . . . . . . . . . . . . 369N  Table 321 - Optical memory medium-type codes. . . . . . . . . . . . . . . 369N  Table 322 - Optical memory device specific parameter. . . . . . . . . . . 370N  Table 323 - Optical memory density codes. . . . . . . . . . . . . . . . . 370N  Table 324 - Mode page codes . . . . . . . . . . . . . . . . . . . . . . . 371N  Table 325 - Optical memory page . . . . . . . . . . . . . . . . . . . . . 372N  Table 326 - Volume tag information format . . . . . . . . . . . . . . . . 376N  Table 327 - Commands for medium changer devices . . . . . . . . . . . . . 377N  Table 328 - EXCHANGE MEDIUM command . . . . . . . . . . . . . . . . . . . 378N  Table 329 - INITIALIZE ELEMENT STATUS command . . . . . . . . . . . . . . 379N  Table 330 - MOVE MEDIUM command . . . . . . . . . . . . . . . . . . . . . 380N  Table 331 - POSITION TO ELEMENT command . . . . . . . . . . . . . . . . . 381N  Table 332 - READ ELEMENT STATUS command . . . . . . . . . . . . . . . . . 382N  Table 333 - Element type code . . . . . . . . . . . . . . . . . . . . . . 382N  Table 334 - Element status data . . . . . . . . . . . . . . . . . . . . . 383N  Table 335 - Element status page . . . . . . . . . . . . . . . . . . . . . 385N  Table 336 - Medium transport element descriptor . . . . . . . . . . . . . 386N  Table 337 - Storage element descriptor. . . . . . . . . . . . . . . . . . 387N  Table 338 - Import export element descriptor. . . . . . . . . . . . . . . 388N  Table 339 - Data transfer element descriptor. . . . . . . . . . . . . . . 389N  Table 340 - REQUEST VOLUME ELEMENT ADDRESS command. . . . . . . . . . . . 390N  Table 341 - Volume element address header format. . . . . . . . . . . . . 391N  Table 342 - RELEASE command . . . . . . . . . . . . . . . . . . . . . . . 392N  Table 343 - RESERVE command . . . . . . . . . . . . . . . . . . . . . . . 393N  Table 344 - Data format of element list descriptors . . . . . . . . . . . 394N  Table 345 - SEND VOLUME TAG command . . . . . . . . . . . . . . . . . . . 395N  Table 346 - Send volume tag action codes. . . . . . . . . . . . . . . . . 396N  Table 347 - Send volume tag parameters format . . . . . . . . . . . . . . 396N  Table 348 - Diagnostic page codes . . . . . . . . . . . . . . . . . . . . 398N  Table 349 - Log page codes. . . . . . . . . . . . . . . . . . . . . . . . 398N  Table 350 - Mode page codes . . . . . . . . . . . . . . . . . . . . . . . 399N  Table 351 - Device capabilities page. . . . . . . . . . . . . . . . . . . 399N  Table 352 - Element address assignment page . . . . . . . . . . . . . . . 400N  Table 353 - Transport geometry parameters page. . . . . . . . . . . . . . 403N  Table 354 - Commands for communications devices . . . . . . . . . . . . . 407N  Table 355 - GET MESSAGE(6) command. . . . . . . . . . . . . . . . . . . . 408N  Table 356 - GET MESSAGE(10) command . . . . . . . . . . . . . . . . . . . 408N  Table 357 - GET MESSAGE(12) command . . . . . . . . . . . . . . . . . . . 409N  Table 358 - SEND MESSAGE(6) command . . . . . . . . . . . . . . . . . . . 410N  Table 359 - SEND MESSAGE(10) command. . . . . . . . . . . . . . . . . . . 410N  Table 360 - SEND MESSAGE(12) command. . . . . . . . . . . . . . . . . . . 411N  Table 361 - Diagnostic page codes . . . . . . . . . . . . . . . . . . . . 412N  Table 362 - Log page codes. . . . . . . . . . . . . . . . . . . . . . . . 412N  Table 363 - Mode page codes . . . . . . . . . . . . . . . . . . . . . . . 413N  Table B.1 - Fast SCSI jitter budget . . . . . . . . . . . . . . . . . . . 418N  Table B.2 - Mapping of jitter to SCSI . . . . . . . . . . . . . . . . . . 418N  Table D.1 - ASC and ASCQ assignments. . . . . . . . . . . . . . . . . . . 421N  Table D.2 - SCSI-2 Operation Codes. . . . . . . . . . . . . . . . . . . . 427N  Table E.1 - Vendor identification list. . . . . . . . . . . . . . . . . . 431  T  e  1  P   	  Forewordo  nH  This Small Computer System Interface -2 standard is designed to provideJ  an efficient peer-to-peer I/O bus with up to 16 devices, including one orG  more hosts.  Data may be transferred asynchronously at rates that only D  depend on device implementation and cable length.  Synchronous dataK  transfers are supported at rates up to 10 mega-transfers per second.  WitheK  the 32-bit wide data transfer option, data rates of up to 40 megabytes perbK  second are possible.  This standard includes command sets for magnetic andTF  optical disks, tapes, printers, processors, CD-ROMs, scanners, medium&  changers, and communications devices.  .  .  .  .
  Introduction.  .G  This part of ANSI X3.131-199x replaces ANSI X3.131-1986 Small Computer.  System Interface.  21  The clauses contain material as described below..  .)     Clause 1         describes the scope.t  o4     Clause 2         lists the normative references.  3F     Clause 3         provides a glossary common to the whole document.  e;     Clause 4         provides descriptions and conventions..  .<     Clause 5         describes the physical characteristics.  .L     Clause 6         describes the logical characteristics of the interface.  .E     Clause 7         describes the SCSI command and status structure..  .P     Clause 8         specifies those commands that have a consistent meaning for&                      all device types.  tB     Clause 9         specifies commands for direct-access devices.  RJ     Clause 10            specifies commands for sequential-access devices.  R@     Clause 11            specifies commands for printer devices.  bB     Clause 12            specifies commands for processor devices.  3C     Clause 13            specifies commands for write-once devices..  .?     Clause 14            specifies commands for CD-ROM devices..  .@     Clause 15            specifies commands for scanner devices.  .G     Clause 16            specifies commands for optical memory devices..  .G     Clause 17            specifies commands for medium changer devices..  .G     Clause 18            specifies commands for communications devices.e  s:     Annex A              illustrates SCSI signal sequence.   9     Annex B              illustrates fast SCSI skew time.2  -I     Annex C              describes other SCSI standardization activities.2  -N     Annex D              contains SCSI-2 additional sense codes and operation 0                          codes in numeric order.  .L     Annex E              contains the list of SCSI-2 vendor identifications.  .K  The SCSI protocol is designed to provide an efficient peer-to-peer I/O bus.A  with up to 16 devices, including one or more hosts.  Data may be.?  transferred asynchronously at rates that only depend on devicemK  implementation and cable length.  Synchronous data transfers are supportediH  at rates up to 10 mega-transfers per second.  With the 32-bit wide dataK  transfer option, data rates of up to 40 megabytes per second are possible.u  oD  SCSI-2 includes command sets for magnetic and optical disks, tapes,>  printers, processors, CD-ROMs, scanners, medium changers, and  communications devices.  .B  In 1985, when the first SCSI standard was being finalized severalH  manufacturers wanted to increase the mandatory requirements of SCSI andI  to define further features for direct-access devices.  Rather than delaydJ  the SCSI standard, formed an ad hoc group was formed to develop a workingJ  paper that was eventually called the Common Command Set (CCS).  Many disk1  products were designed using this working paper..  .I  In parallel with the development of the CCS working paper, work began on.G  an enhanced SCSI standard which was named SCSI-2.  SCSI-2 included the.I  results of the CCS working paper and extended them to all device types. .F  It also added caching commands, performance enhancement features, andC  other worthwhile functions.  While SCSI-2 has gone well beyond the.F  original SCSI standard (now referred to as SCSI-1), it retains a high-  degree of compatibility with SCSI-1 devices..  3J  SCSI-2 has evolved significantly from SCSI-1 with the new document nearlyD  three times larger.  Most of the changes are additions, but several  obsolete options were removed:g"     a)     Single initiator option)     b)     Non-arbitrating systems optiond6     c)     The SCSI-1 alternative 1 shielded connector)     d)     Non-extended sense data option.%     e)     Reservation queuing option3,     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 powerA     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)O     b)     Fast SCSI (synchronous data transfers of up to 10 mega-transfers per(            second)N     c)     Command queuing (up to 256 commands per initiator per logical unit)9     d)     High-density connector alternatives were added *     e)     Asynchronous event notification*     f)     Extended contingent allegiance.  c'  New command sets were added including:.-     a)     CD-ROM (replaces read-only device)o     b)     Scanner device.I     c)     Optical memory device (provides for write-once, read-only, and.            erasable media)      d)     Medium changer device      e)     Communications device  b   All command sets were enhanced:#     a)     Device models were added3&     b)     Extended sense was expanded(     c)     The INQUIRY data was expandedL     d)     The MODE SELECT and MODE SENSE commands were paged for all device            typesO     e)     The CHANGE DEFINITION, LOG SELECT, LOG SENSE, READ BUFFER, and WRITEI:            BUFFER commands were added for all device typesL     f)     The COPY command definition was expanded to include inexact block2            size handling and an image copy option.I     g)     The direct-access device command set was enhanced to add cache.I            management, several new commands and to provide more initiator.)            control over defect managementTI     h)     The sequential-access device command set was enhanced to add a9$            partitioned media conceptM     i)     The printer device command set was enhanced by adding several modes            pagesM     j)     The write-once (optical) device command set was enhanced by adding.I            several new commands plus extending several command descriptor.I            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  .H  This standard defines an input/output bus for interconnecting computersE  and peripheral devices.  It defines extensions to the Small Computer.I  System Interface (ISO 9316:1989), referred to herein as SCSI-1.  It also.I  provides more complete standardization of the previously defined command.B  sets.  It includes the necessary specification of the mechanical,E  electrical, and functional characteristics of the interface to allowoG  inter-operability of conforming devices.  This standard is referred tosI  herein as SCSI-2.  The term SCSI is used wherever it is not necessary toe&  distinguish between the two versions.  .  .  2 Normative references-  dG  The following standards contain provisions which, through reference in7C  this text, constitute provisions of this standard.  At the time of K  publication, the editions indicated were valid.  All standards are subject8B  to revision, and parties to agreements based on this standard areF  encouraged to investigate the possibility of applying the most recentC  editions of the standards indicated below.  Members of IEC and ISOa1  maintain registers of currently valid standards.E  mK  ISO/IEC 10149:1989, Information technology - Data interchange on read-onlyc$  120 mm optical data disks (CD-ROM).  .1  IEC 908:1987, Compact Disc Digital Audio System.   tH  American National Standard ANSI BSR X3.170A-1991, Enhanced Small Device  Interface..  .G  EIA RS-485-1983, Standard for Electrical Characteristics of Generators.>  and Receivers for use in Balanced Digital Multipoint Systems.  m  r)  3 Definitions, symbols and abbreviationsT  e  8  3.1 Definitions  dD  For the purposes of this standard, the following definitions apply.  eH  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.  3H  3.1.3 command descriptor block (CDB): The structure used to communicate(  commands from an initiator to a target.  .K  3.1.4 command queue: The queue used to store the queued I/O processes (seeg  7.8).  .I  3.1.5 connect: The initiator function that selects a target to establish.H  a nexus and to start an I/O process.  The connection that results is an  initial connection.  .K  3.1.6 connection: An initial connection or reconnection.  A connection can.2  only occur between one initiator and one target.   .B  3.1.7 contact: The electrically-conductive portion of a connector/  associated with a single conductor in a cable.e  9H  3.1.8 contingent allegiance: A condition typically generated by a CHECKH  CONDITION status during which a target preserves sense data (see 7.6.).  TJ  3.1.9 current I/O process: The I/O process that is presently connected on  the SCSI bus.  pG  3.1.10 disconnect: The action that occurs when an SCSI device releases-B  control of the SCSI bus, allowing it to go to the BUS FREE phase.  bC  3.1.11 extended contingent allegiance: A condition generated by an.J  INITIATE RECOVERY message to assist in extended error recovery procedures&  in multi-initiator systems (see 7.7).  e6  3.1.12 field: A group of one or more contiguous bits.  SK  3.1.13 host adapter: A device which connects between a host system and the-D  SCSI bus.  The device usually performs the lower layers of the SCSII  protocol and normally operates in the initiator role.  This function mays$  be integrated into the host system.  iD  3.1.14 initial connection: An initial connection is the result of aJ  connect and it exists from the assertion of the BSY signal in a SELECTION,  phase until the next BUS FREE phase occurs.  cD  3.1.15 initiator: An SCSI device that requests an I/O process to be-  performed by another SCSI device (a target).n  rJ  3.1.16 invalid: An illegal (reserved) or unsupported field or code value.  nJ  3.1.17 I/O process: An I/O process consists of one initial connection andJ  zero or more reconnections, all pertaining to a single command or a groupG  of linked commands.  More specifically, the connection(s) pertain to arH  nexus in which zero or more command descriptor blocks are transferred. I  An I/O process begins with the establishment of a nexus.  An I/O processbI  normally ends with the BUS FREE phase following successful transfer of a3J  COMMAND COMPLETE or a RELEASE RECOVERY message.  An I/O process also endsI  with the BUS FREE phase following an ABORT, ABORT TAG, BUS DEVICE RESET,uA  CLEAR QUEUE message, or a hard RESET condition, or an unexpectede  disconnect occurs.t  lJ  3.1.18 I_T nexus: A nexus which exists between an initiator and a target.  eI  3.1.19 I_T_L nexus: A nexus which exists between an initiator, a target,oE  and a logical unit.  This relationship replaces the prior I_T nexus.l  vI  3.1.20 I_T_R nexus: A nexus which exists between an initiator, a target,eG  and a target routine.  This relationship replaces the prior I_T nexus.c   E  3.1.21 I_T_x nexus: A nexus which is either an I_T_L or I_T_R nexus.e  eH  3.1.22 I_T_L_Q nexus: A nexus between an initiator, a target, a logicalK  unit, and a queue tag following the successful receipt of one of the queue.A  tag messages.  This relationship replaces the prior I_T_L nexus.    C  3.1.23 I_T_x_y nexus: A nexus which is either an I_T_x or I_T_L_Q.    A  3.1.24 logical block: A unit of data supplied or requested by an.  initiator.u  1I  3.1.25 logical unit: A physical or virtual peripheral device addressablee  through a target.  sD  3.1.26 logical unit number: An encoded three-bit identifier for the  logical unit.  nK  3.1.27 mandatory: The referenced item is required to claim compliance with   this standard.    F  3.1.28 nexus: A relationship that begins with the establishment of anI  initial connection and ends with the completion of the I/O process.  The J  relationship may be restricted to specify a single logical unit or target@  routine by the successful transfer of an IDENTIFY message.  TheG  relationship may be further restricted by the successful transfer of ap  queue tag message.d   C  3.1.29 one: A true signal value or a true condition of a variable.s  aI  3.1.30 optional: The referenced item is not required to claim compliancetK  with this standard.  Implementation of an optional item must be as definedt  in this standard.   H  3.1.31 page: Several commands use regular parameter structures that areH  referred to as pages.  These pages are identified with a value known as
  a page code.p   C  3.1.32 peripheral device: A physical peripheral device that can beeA  attached to an SCSI device, which connects to the SCSI bus.  ThesE  peripheral device and the SCSI device (peripheral controller) may be K  physically packaged together.  Often there is a one-to-one mapping between J  peripheral devices and logical units, but this is not required.  ExamplesH  of peripheral devices are: magnetic disks, printers, optical disks, and  magnetic tapes.  eI  3.1.33 queue tag: The value associated with an I/O process that uniquelynJ  identifies it from other queued I/O processes in the logical unit for the  same initiator.  CH  3.1.34 queued I/O process: An I/O process that is in the command queue.  lK  3.1.35 reconnect: The act of reviving a nexus to continue an I/O process. aI  A target reconnects to an initiator by using the RESELECTION and MESSAGE J  IN phases after winning arbitration.  An initiator reconnects to a targetH  by using the SELECTION and MESSAGE OUT phases after winning arbitration
  (see 7.5.2).r  SH  3.1.36 reconnection: A reconnection is the result of a reconnect and itJ  exists from the assertion of the BSY signal in a SELECTION or RESELECTION,  phase until the next BUS FREE phase occurs.  iG  3.1.37 reserved: Identifies bits, fields, and code values that are setr"  aside for future standardization.  tI  3.1.38 SCSI address: The hex representation of the unique address (0-15)cI  assigned to an SCSI device.  This address would normally be assigned and 3  set in the SCSI device during system installation.   uG  3.1.39 SCSI ID: The bit-significant representation of the SCSI addressc.  referring to one of the signal lines DB(7-0).  oF  3.1.40 SCSI device: A host adapter or a target controller that can be  attached to the SCSI bus.  iH  3.1.41 signal assertion: The act of driving a signal to the true state.   J  3.1.42 signal negation: The act of driving a signal to the false state orI  allowing the cable terminators to bias the signal to the false state (byt5  placing the driver in the high impedance condition).r  uI  3.1.43 signal release: The act of allowing the cable terminators to biascK  the signal to the false state (by placing the driver in the high impedancei  condition).  SJ  3.1.44 status: One byte of information sent from a target to an initiator!  upon completion of each command.   iI  3.1.45 target: An SCSI device that performs an operation requested by an   initiator.s   H  3.1.46 target routine: A target routine is an I/O process directed to a/  target, and not to a logical unit (see 6.6.7).a  xI  3.1.47 third-party: When used in reference to COPY commands, third-partylF  means a COPY command issued to one device to perform a copy operationJ  between two other devices.  When used in reference to RESERVE, or RELEASEK  commands, third-party means a reservation made on behalf of another deviceiF  (e.g. A processor device requests that a direct-access device reserve9  itself for exclusive use by a sequential-access device).c  tI  3.1.48 unexpected disconnect: A disconnection that occurs as a result ofr$  an exception condition (see 6.1.1).  eG  3.1.49 vendor-specific (VS): Something (e.g. a bit, field, code value,nJ  etc.) that is not defined by this standard and may be used differently in  various implementations.n  cF  3.1.50 zero: A false signal value or a false condition of a variable.  t  3.2 Symbols and abbreviations  e6  AEN       Asynchronous event notification (see 7.5.5)  AWG       American Wire Gauge   LSB       Least significant bit  LUN       Logical unit number  MSB       Most significant bitd"  SCSI      Either SCSI-1 or SCSI-2A  SCSI-1       The Small Computer System Interface (ISO 9316:1989) E  SCSI-2       The Small Computer System Interface - 2 (this atandard)d  f  s   
  4 General  s
  4.1 Overviewc  gG  SCSI is a local I/O bus that can be operated over a wide range of dataCB  rates.  The primary objective of the interface is to provide hostE  computers with device independence within a class of devices.  Thus,uH  different disk drives, tape drives, printers, optical media drives, andC  other devices can be added to the host computers without requiringtI  modifications to generic system hardware or software.  Provision is madeiF  for the addition of special features and functions through the use ofH  vendor unique fields and codes.  Reserved fields and codes are provided  for future standardization.  oH  A second key objective of SCSI-2 is to provide compatibility with thoseI  SCSI-1 devices that support bus parity and that meet conformance level 2hH  of SCSI-1.  While some previously vendor unique commands and parametersK  have been defined by the SCSI-2 standard, devices meeting SCSI-1 and SCSI-iE  2 can co-exist on the same bus.  It is intended that those operatingdF  systems providing support for both command sets be able to operate inK  environments mixing SCSI-1 and SCSI-2 devices.  Properly conforming SCSI-1 F  devices, both initiators and targets, should respond in an acceptableB  manner to reject SCSI-2 protocol extensions.  All SCSI-2 protocolI  extensions are designed to be permissive of such rejections and to allow.I  the SCSI-1 device to continue operation without requiring the use of ther  extension.i  sI  A third key objective of SCSI-2 is to move device-dependent intelligencey@  out to the SCSI-2 devices.  The command set definitions allow aE  sophisticated operating system to obtain all required initializationaJ  information from the attached SCSI-2 devices.  The formalized sequence ofJ  requests identify the type of attached SCSI-2 device, the characteristicsK  of the device, and all the changeable parameters supported by the device. tK  Further requests can determine the readiness of the device to operate, theuG  types of media supported by the device, and all other pertinent systemnH  information.  Those parameters not required by the operating system forJ  operation, initialization, or system tuning are not exposed to the SCSI-28  interface, but are managed by the SCSI-2 device itself.  aH  The interface uses logical rather than physical addressing for all dataJ  blocks.  For direct-access devices, each logical unit may be interrogatedG  to determine how many blocks it contains.  A logical unit may coincide )  with all or part of a peripheral device.s  uI  The interface protocol includes provision for the connection of multipletJ  initiators (SCSI devices capable of initiating an operation) and multipleG  targets (SCSI devices capable of responding to a request to perform anaJ  operation).  Distributed arbitration (i.e. bus-contention logic) is builtK  into the architecture of SCSI.  A priority system awards interface controlIL  to the highest priority SCSI device that is contending for use of the bus. I  The time to complete arbitration is independent of the number of deviceso=  that are contending and can be completed in less than 10 us.t  eG  There are two electrical alternatives: single-ended and differential.  H  Single-ended and differential devices are electrically incompatible and+  can not be mixed on the same physical bus.t  hJ  Provision is made for cable lengths up to 25 m using differential driversD  and receivers.  A single-ended driver and receiver configuration isE  defined for cable lengths of up to 6 m and is primarily intended for3  applications within a cabinet.h  rC  Arbitration is defined to permit multiple initiators and to permitrH  concurrent I/O operations.  All SCSI devices are required to be capableB  of operating with the defined asynchronous transfer protocol.  InK  addition, an optional synchronous transfer protocol is defined.  A messagenI  protocol for control of the interface is also specified.  In most cases,tD  messages are not directly apparent to the host computer software.    cJ  Commands are classified as mandatory, optional, or vendor-specific.  SCSII  devices are required to implement all mandatory commands defined for theeH  appropriate device type and may implement other commands as well.  SCSII  devices contain commands that facilitate the writing of self-configuringTJ  software drivers that can discover all necessary attributes without priorB  knowledge of specific peripheral characteristics (such as storageD  capacity).  Many commands also implement a very large logical blockH  address space (232 blocks), although some commands implement a somewhat3  smaller logical block address space (221 blocks). s   J  Starting with clause 8 and for each clause on a specific device type, theH  clause is constructed of at least four subclauses.  The first subclauseK  is the model for the device type.  The model establishes the framework foreC  interpreting the commands for the device type.  The attributes andaK  capabilities of the device type are discussed and examples are given.  ThehJ  second subclause defines the commands applicable to the device type.  TheG  third subclause defines the parameters applicable to the device type.  I  These are the diagnostic parameters, log parameters, mode parameters andiB  vital product data parameters that are transmitted as part of theI  appropriate commands.  Most of the parameters are formatted into pages. :K  The fourth subclause gives the definition of terms that apply specificallyr  to that device type.   eH  Starting with clause 9 the commands in each of these clauses are uniqueK  to the device type, or they have interpretations, fields, or features that I  are specific for the device type.  Thus, for example, although the WRITEsK  command is used for several device types, it has a somewhat different formlI  for each type, with different parameters and meanings.  Therefore, it isc+  specified separately for each device type.t  m  4.2 Conventions   C  Certain words and terms used in this International Standard have a1K  specific meaning beyond the normal English meaning.  These words and terms H  are defined either in clause 3 or in the text where they first appear. D  Names of signals, phases, messages, commands, statuses, sense keys,H  additional sense codes, and additional sense code qualifiers are in allI  uppercase (e.g. REQUEST SENSE).  Lower case is used for words having thep  normal English meaning.  tG  Fields containing only one bit are usually referred to as the name bith  instead of the name field.e  SK  Numbers that are not immediately followed by lower-case b or h are decimale  values.  oF  Numbers immediately followed by lower-case b (xxb) are binary values.   K  Numbers immediately followed by lower-case h (xxh) are hexadecimal values.e     i  5 Physical characteristicse   I  This clause contains the physical definition of SCSI-2.  The connectors,lH  cables, signals, terminators, and bus timing values needed to implement  the interface are covered.3  3  5.1 Physical descriptionO  oD  SCSI devices are daisy-chained together using a common 50-conductorJ  A cable and, optionally, a 68-conductor B cable.  Both ends of each cableH  are terminated.  All signals are common between all SCSI devices on theI  A cable.  In systems that employ the wide SCSI option, wide SCSI devicesnH  additionally connect to the B cable.  Various width SCSI devices may be  mixed.c  nL     NOTE 1 An alternate 16-bit single-cable solution and an alternate 32-bitM     solution is being defined and the B cable definition will be removed in aR     future version of SCSI.   e0  Two driver/receiver alternatives are specified:J     a)     Single-ended drivers and receivers, which allow a maximum cableH            length of 6 m (primarily for connection within an enclosure).J     b)     Differential drivers and receivers, which allow a maximum cable            length of 25 m.   I  The single-ended and differential alternatives are mutually exclusive onc  the same physical bus.e  gN     NOTE 2 Use of single-ended drivers and receivers with the fast synchronous,     data transfer option is not recommended.  3  5.2 Cable requirements      I  The characteristic impedance of the cable should be no less than 90 ohmstI  and no greater than 140 ohms.  The characteristic impedance of the cable D  used when implementing the fast synchronous data transfer option is  defined in 5.2.3.  oN     NOTE 3 There are successful single-ended implementations using cables withM     less than 90 ohms characteristic impedance.  However, system integrity incN     single-ended implementations is improved when the characteristic impedanceE     of the cable is greater than 90 ohms. Cable parameters other thantL     characteristic impedance are critical to system integrity.  Alternative M     cable parameters are being investigated as a part of a future version of r	     SCSI.t   D  A minimum conductor size of 0,080 42 mm2 (28 AWG) should be used toL  minimize noise effects and ensure proper distribution of terminator power. G  A smaller conductor size may be used for signals other than terminatori  power.   o     NOTES     M     4 To minimize discontinuities and signal reflections, cables of differentcO     impedances should not be used in the same bus.  Implementations may requirelM     trade-offs in shielding effectiveness, cable length, the number of loads,sG     transfer rates, and cost to achieve satisfactory system operation. tP     5 To minimize discontinuities due to local impedance variation, a flat cableM     should be spaced at least 1,27 mm (0,050 in) from other cables, any otherr<     conductor, or the cable itself when the cable is folded.>     6 Regulatory agencies may require use of larger wire size.  s  5.2.1 Single-ended cableN   H  A 50-conductor flat cable or 25-signal twisted-pair cable shall be usedF  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 isIF  implemented.  The maximum cumulative cable length shall be 6,0 m.  IfG  twisted-pair cables are used, then twisted pairs in the cable shall bef8  wired to physically opposing contacts in the connector.  l@  A stub length of no more than 0,1 m is allowed off the mainlineE  interconnection within any connected equipment or from any connectedw  point.e  dN     NOTE 7 Stub clustering should be avoided.  Stubs should be spaced at least     0,3 m apart.  mK  SCSI bus termination shall be at each end of the cable and may be internale7  to the SCSI devices that are at the ends of the cable.f  r  5.2.2 Differential cabler  eH  A 50-conductor flat cable or 25-signal twisted-pair cable shall be usedF  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 is E  implemented.  The maximum cumulative cable length shall be 25 m.  IftG  twisted-pair cables are used, then twisted pairs in the cable shall bev8  wired to physically opposing contacts in the connector.  h@  A stub length of no more than 0,2 m is allowed off the mainlineE  interconnection within any connected equipment or from any connectedo  point.p  tK  SCSI bus termination shall be at each end of the cable and may be internal 7  to the SCSI devices that are at the ends of the cable.o  iN     NOTE 8 The use of twisted pair cable (either twisted-flat or discrete wireP     twisted pairs) is strongly recommended.  Without twisted pairs, even at slowK     data rates and very short distances, crosstalk between adjacent signalsn5     causes spurious pulses with differential signals.A  i<  5.2.3 Cable requirements for fast synchronous data transfer  cJ  In systems which use the fast synchronous data transfer option (see 5.8),J  the A and B cables should meet the conductor size recommendation in 5.2. F  The cable should have an overall shield suitable for termination in a  shielded connector.  a@  In such systems, the cables shall have the following electrical  characteristics:r?     Characteristic impedance:               90 ohms to 132 ohmsnO     Signal attenuation:                     0,095 dB maximum per metre at 5 MhzdE     Pair-to-pair propagation delay delta:   0,20 ns maximum per metre O     DC resistance:                          0,230 ohms maximum per metre at 20 u5                                             degrees C   a  5.3 Connector requirementsl   J  Two types of connectors are defined: non-shielded and shielded.  The non-E  shielded connectors are typically used for in-cabinet applications. gG  Shielded connectors are typically used for external applications wherecF  electromagnetic compatibility (EMC) and electrostatic discharge (ESD)K  protection may be required.  Either type of connector may be used with thee&  single-ended or differential drivers.  n*  5.3.1 Non-shielded connector requirements  eJ  Two non-shielded connector alternatives are specified for the A cable and9  one non-shielded connector is specified for the B cable.e   7  5.3.1.1 Non-shielded connector alternative 1 - A cableh  iJ  The alternative 1 non-shielded high-density SCSI device connector for theK  A cable (see figure 1) shall be a 50-conductor connector consisting of two L  rows of 25 female contacts with adjacent contacts 1,27 mm (0,05 in) apart. E  The non-mating portion of the connector is shown for reference only.   fF  The alternative 1 non-shielded high-density cable connector for the AI  cable (see figure 2) shall be a 50-conductor connector consisting of two J  rows of 25 male contacts with adjacent contacts 1,27 mm (0,05 in) apart. E  The non-mating portion of the connector is shown for reference only.p  a7  5.3.1.2 Non-shielded connector alternative 2 - A cable   bI  The alternative 2 non-shielded low-density SCSI device connector for thenK  A cable (see figure 3) shall be a 50-conductor connector consisting of two J  rows of 25 male pins with adjacent pins 2,54 mm (0,1 in) apart.  A shroudI  and header body should be used.  The non-mating portion of the connectoro  is shown for reference only.i  dK  The alternative 2 non-shielded low-density cable connector for the A cablesH  (see figure 4) shall be a 50-conductor connector consisting of two rowsI  of 25 female contacts with adjacent contacts 2,54 mm (0,1 in) apart.  It .  is recommended that keyed connectors be used.  i)  5.3.1.3 Non-shielded connector - B cablev  sI  The non-shielded high-density SCSI device connector for the B cable (seerI  figure 1) shall be a 68-conductor connector consisting of two rows of 34dJ  female contacts with adjacent contacts 1,27 mm (0,05 in) apart.  The non-=  mating portion of the connector is shown for reference only.s  eJ  The non-shielded high-density cable connector for the B cable (see figureG  2) shall be a 68-conductor connector consisting of two rows of 34 male I  contacts with adjacent contacts 1,27 mm (0,05 in) apart.  The non-matinga6  portion of the connector is shown for reference only.        i  t  .  h  o     a  s        m  r  o     t  r  n  h  o  n  f  t  d  c  y     e  t  u     a  c  b  t     t  d  c  y  a  d  u  d  d  a  e  r  iL     Figure 1 - 50/68-contact non-shielded high-density SCSI device connector0                                (A cable/B cable)  l  b  t  h  e  e  p     T  e  e  e  a  s     a  e        a  e     e  r  t     i  v  l  o  t  t  a  e  s  a  r  r  m  e  s  r  f  e  a  o  a  c  a  .  o  o  h  aI        Figure 2 - 50/68-contact non-shielded high-density cable connectori0                                (A cable/B cable)  c  y     e  S  t     h  a     h  o  n  i  a  o  h     u        q           i  t  ,     y  v  n  p  a  n  f  d  o  e  r  t     a  s  i           i  t  .  hJ       Figure 3 - 50-contact non-shielded low-density SCSI device connector,                                    (A cable)     e  i  d  e  t  r  t        n  s  T  e  e  t  c  s  i  d  p  t        h  v     e        2  n  t  s     C  a  w  s  d  r  u     t     e  t  a  t  a  h        eG          Figure 4 - 50-Contact non-shielded low-density cable connector ,                                    (A cable)  e  t&  5.3.2 Shielded connector requirements  eJ  Two shielded connector alternatives are specified for the A cable and oneJ  shielded connector is specified for the B cable.  The connector shieldingG  system should provide a d.c. resistance of less than 10 mohms from the D  cable shield at its termination point to the SCSI device enclosure.   C  In order to support daisy-chain connections, SCSI devices that useoI  shielded connectors should provide two shielded device connectors on theyG  device enclosure.  These two connectors may be wired one-to-one with aeJ  stub to the SCSI device's drivers and receivers provided the maximum stubK  length is not violated.  Alternatively, two cables may be run from the twoSJ  shielded connectors to the drivers and receivers so that the maximum stubC  length is not violated.  The length of the cable within the device J  enclosure is included when calculating the total cable length of the SCSI  bus.t   L     NOTE 9 SCSI-1 defined three shielded connector systems in an annex.  TheK     alternative 1 shielded connector of SCSI-1 has been replaced by a high-bI     density connector in this International Standard.  The alternative 2 tH     shielded  connector remains unchanged.  The EUROCARD boxes shielded O     connector system of SCSI-1 has been deleted in this International Standard.b   3  5.3.2.1 Shielded connector alternative 1 - A cablei  wE  The shielded high-density SCSI device connector for the A cable (seeeJ  figure 5) is a 50-conductor connector consisting of two rows of 25 femaleI  contacts with adjacent contacts 1,27 mm (0,05 in) apart.  The non-matingo6  portion of the connector is shown for reference only.  vI  The shielded high-density cable connector for the A cable (see figure 6) G  is a 50-conductor connector consisting of two rows of 25 male contactseH  with adjacent contacts 1,27 mm (0,05 in) apart.  The non-mating portion.  of the connector is shown for reference only.  t3  5.3.2.2 Shielded connector alternative 2 - A cableq  eI  The shielded low-density device connector for the A cable (see figure 7)tF  is a 50-conductor connector consisting of two rows of ribbon contactsJ  spaced 2,16 mm (0,085 in) apart.  The non-mating portion of the connector  is shown for reference only.    H  The shielded low-density cable connector for the A cable (see figure 8)F  is a 50-conductor connector consisting of two rows of ribbon contactsJ  spaced 2,16 mm (0,085 in) apart.  The non-mating portion of the connector  is shown for reference only.b  i%  5.3.2.3 Shielded connector - B cables  hE  The shielded high-density SCSI device connector for the B cable (see.J  figure 5) is a 68-conductor connector consisting of two rows of 34 femaleI  contacts with adjacent contacts 1,27 mm (0,05 in) apart.  The non-matingm6  portion of the connector is shown for reference only.  nI  The shielded high-density cable connector for the B cable (see figure 6)aG  is a 68-conductor connector consisting of two rows of 34 male contacts H  with adjacent contacts 1,27 mm (0,05 in) apart.  The non-mating portion.  of the connector is shown for reference only.  m  u     l  n  i        u  l     r  -  s     e  n  f  t  n  ,  b  l  t  t  n  e  f  a  s     r  f  r  s  n  o  t  c  v  a  f  o  s  e  p  t  .        o  n  zJ       Figure 5 - 50/68-contact shielded high-density SCSI device connector0                                (A cable/B cable)  l        e        d  o  o  h  a     e  w        l  s  l  .        u  o  a  c        u        l  e  i  s  .  s  5  1  n  -  e  a  N     A  -  d  o  l  c  eG          Figure 6 - 50/68-contact shielded high-density cable connectoro0                                (A cable/B cable)  s  l     d  r  e  c  e        e  S  p  n  I  i  e  t     e  x  m  m  t     l  e  h  a  b  ,  .  f  t  t  p     l  a  u  ,  e  w  e  a     t  c  e  a  b   H         Figure 7 - 50-contact shielded low-density SCSI device connector  o  o  r  h  0  m     o           n  e  i  r  n  i  w  i  n  o  c     i  n  r  o  n  o  c  w  p  t           E  S     s  i  s  l  e  o  d  S  s  o     s  e  t  aE            Figure 8 - 50-contact shielded low-density cable connector    $  5.3.3 Connector contact assignments  dF  The connector contact assignments are defined in tables 1 through 5. G  Table 1 defines which of the other four tables to use and which set ofb  contact assignments to use.  oE            Table 1 - Cross-reference to connector contact assignmentstM  +==========================-============-=====-=========-==========-=======+aM  |                          |   Driver/  |     |         |  Contact |       |rM  |                          |  receiver  |     |Connector|assignment|Contact|oM  |     Connector type       |    type    |Cable|  figure |   table  |   set |rM  |--------------------------+------------+-----+---------+----------+-------| M  |Non-shielded alternative 1|Single-ended|  A  |  1 & 2  |      2   |    2  |tM  |Non-shielded alternative 1|Single-ended|  B  |  1 & 2  |      3   |       |oM  |Non-shielded alternative 1|Differential|  A  |  1 & 2  |      4   |    2  |iM  |Non-shielded alternative 1|Differential|  B  |  1 & 2  |      5   |       |dM  |                          |            |     |         |          |       | M  |Non-shielded alternative 2|Single-ended|  A  |  3 & 4  |      2   |    1  |hM  |Non-shielded alternative 2|Differential|  A  |  3 & 4  |      4   |    1  |fM  |                          |            |     |         |          |       |eM  | Shielded alternative 1   |Single-ended|  A  |  5 & 6  |      2   |    2  |tM  | Shielded alternative 1   |Single-ended|  B  |  5 & 6  |      3   |       | M  | Shielded alternative 1   |Differential|  A  |  5 & 6  |      4   |    2  | M  | Shielded alternative 1   |Differential|  B  |  5 & 6  |      5   |       |BM  |                          |            |     |         |          |       |nM  | Shielded alternative 2   |Single-ended|  A  |  7 & 8  |      2   |    2  |xM  | Shielded alternative 2   |Differential|  A  |  7 & 8  |      4   |    2  | M  +==========================================================================+-  e  dB               Table 2 - Single-ended contact assignments - A cableN  +================-===============-=========-===============-================+N  |                |  Connector    |         |  Connector    |                |N  |                | contact number|  Cable  |contact number |                |N  |      Signal    |---------------|conductor|---------------|    Signal      |N  |       name     | Set 2 | Set 1 | number  | Set 1 | Set 2 |     name       |N  |----------------+-------+-------+---------+-------+-------+----------------|N  |      GROUND    |   1   |   1   |  1 |  2 |   2   |  26   |    -DB(0)      |N  |      GROUND    |   2   |   3   |  3 |  4 |   4   |  27   |    -DB(1)      |N  |      GROUND    |   3   |   5   |  5 |  6 |   6   |  28   |    -DB(2)      |N  |      GROUND    |   4   |   7   |  7 |  8 |   8   |  29   |    -DB(3)      |N  |      GROUND    |   5   |   9   |  9 | 10 |  10   |  30   |    -DB(4)      |N  |      GROUND    |   6   |  11   | 11 | 12 |  12   |  31   |    -DB(5)      |N  |      GROUND    |   7   |  13   | 13 | 14 |  14   |  32   |    -DB(6)      |N  |      GROUND    |   8   |  15   | 15 | 16 |  16   |  33   |    -DB(7)      |N  |      GROUND    |   9   |  17   | 17 | 18 |  18   |  34   |    -DB(P)      |N  |      GROUND    |  10   |  19   | 19 | 20 |  20   |  35   |    GROUND      |N  |      GROUND    |  11   |  21   | 21 | 22 |  22   |  36   |    GROUND      |N  |      RESERVED  |  12   |  23   | 23 | 24 |  24   |  37   |    RESERVED    |N  |       OPEN     |  13   |  25   | 25 | 26 |  26   |  38   |    TERMPWR     |N  |      RESERVED  |  14   |  27   | 27 | 28 |  28   |  39   |    RESERVED    |N  |      GROUND    |  15   |  29   | 29 | 30 |  30   |  40   |    GROUND      |N  |      GROUND    |  16   |  31   | 31 | 32 |  32   |  41   |    -ATN        |N  |      GROUND    |  17   |  33   | 33 | 34 |  34   |  42   |    GROUND      |N  |      GROUND    |  18   |  35   | 35 | 36 |  36   |  43   |    -BSY        |N  |      GROUND    |  19   |  37   | 37 | 38 |  38   |  44   |    -ACK        |N  |      GROUND    |  20   |  39   | 39 | 40 |  40   |  45   |    -RST        |N  |      GROUND    |  21   |  41   | 41 | 42 |  42   |  46   |    -MSG        |N  |      GROUND    |  22   |  43   | 43 | 44 |  44   |  47   |    -SEL        |N  |      GROUND    |  23   |  45   | 45 | 46 |  46   |  48   |    -C/D        |N  |      GROUND    |  24   |  47   | 47 | 48 |  48   |  49   |    -REQ        |N  |      GROUND    |  25   |  49   | 49 | 50 |  50   |  50   |    -I/O        |N  |---------------------------------------------------------------------------|N  |NOTES                                                                      |N  |  1 The minus sign next to a signal indicates active low.                  |N  |  2 The conductor number refers to the conductor position when using       |N  |    0,050 inch centreline flat ribbon cable with a low-density connector or|N  |    when using 0,025 inch centreline flat ribbon cable with a high-density |N  |    connector.  Other cable types may be used to implement equivalent      |N  |    contact assignments.                                                   |N  |  3 Two sets of contact assignments are shown.  Refer to table 1 to        |N  |    determine which set of contacts applies to each connector.             |N  |  4 See 4.4.4 for a definition of the RESERVED lines.                      |N  +===========================================================================+         B               Table 3 - Single-ended contact assignments - B cableN  +================-===============-=========-===============-================+N  |                |   Connector   |  Cable  |   Connector   |                |N  |      Signal    |    contact    |conductor|    contact    |    Signal      |N  |       name     |     number    | number  |     number    |     name       |N  |----------------+---------------+---------+---------------+----------------|N  |      GROUND    |       1       |  1 |  2 |      35       |    GROUND      |N  |      GROUND    |       2       |  3 |  4 |      36       |    -DB(8)      |N  |      GROUND    |       3       |  5 |  6 |      37       |    -DB(9)      |N  |      GROUND    |       4       |  7 |  8 |      38       |    -DB(10)     |N  |      GROUND    |       5       |  9 | 10 |      39       |    -DB(11)     |N  |      GROUND    |       6       | 11 | 12 |      40       |    -DB(12)     |N  |      GROUND    |       7       | 13 | 14 |      41       |    -DB(13)     |N  |      GROUND    |       8       | 15 | 16 |      42       |    -DB(14)     |N  |      GROUND    |       9       | 17 | 18 |      43       |    -DB(15)     |N  |      GROUND    |      10       | 19 | 20 |      44       |    -DB(P1)     |N  |      GROUND    |      11       | 21 | 22 |      45       |    -ACKB       |N  |      GROUND    |      12       | 23 | 24 |      46       |    GROUND      |N  |      GROUND    |      13       | 25 | 26 |      47       |    -REQB       |N  |      GROUND    |      14       | 27 | 28 |      48       |    -DB(16)     |N  |      GROUND    |      15       | 29 | 30 |      49       |    -DB(17)     |N  |      GROUND    |      16       | 31 | 32 |      50       |    -DB(18)     |N  |     TERMPWRB   |      17       | 33 | 34 |      51       |    TERMPWRB    |N  |     TERMPWRB   |      18       | 35 | 36 |      52       |    TERMPWRB    |N  |      GROUND    |      19       | 37 | 38 |      53       |    -DB(19)     |N  |      GROUND    |      20       | 39 | 40 |      54       |    -DB(20)     |N  |      GROUND    |      21       | 41 | 42 |      55       |    -DB(21)     |N  |      GROUND    |      22       | 43 | 44 |      56       |    -DB(22)     |N  |      GROUND    |      23       | 45 | 46 |      57       |    -DB(23)     |N  |      GROUND    |      24       | 47 | 48 |      58       |    -DB(P2)     |N  |      GROUND    |      25       | 49 | 50 |      59       |    -DB(24)     |N  |      GROUND    |      26       | 51 | 52 |      60       |    -DB(25)     |N  |      GROUND    |      27       | 53 | 54 |      61       |    -DB(26)     |N  |      GROUND    |      28       | 55 | 56 |      62       |    -DB(27)     |N  |      GROUND    |      29       | 57 | 58 |      63       |    -DB(28)     |N  |      GROUND    |      30       | 59 | 60 |      64       |    -DB(29)     |N  |      GROUND    |      31       | 61 | 62 |      65       |    -DB(30)     |N  |      GROUND    |      32       | 63 | 64 |      66       |    -DB(31)     |N  |      GROUND    |      33       | 65 | 66 |      67       |    -DB(P3)     |N  |      GROUND    |      34       | 67 | 68 |      68       |    GROUND      |N  |---------------------------------------------------------------------------|N  |NOTES                                                                      |N  |  1 The minus sign next to a signal indicates active low.                  |N  |  2 The conductor number refers to the conductor position when using       |N  |    0,025 inch centreline flat ribbon cable.  Other cable types may be used|N  |    to implement contact assignments.                                      |N  +===========================================================================+  h  nM     NOTE 10 An alternate 16-bit single-cable solution and an alternate 32-bitlM     solution is being defined and the B cable definition will be removed in a      future version of SCSI.    B               Table 4 - Differential contact assignments - A cableN  +================-===============-=========-===============-================+N  |                |  Connector    |         |  Connector    |                |N  |                |contact number |  Cable  |contact number |                |N  |      Signal    |---------------|conductor|---------------|    Signal      |N  |       name     | Set 2 | Set 1 | number  | Set 1 | Set 2 |     name       |N  |----------------+-------+-------+---------+-------+-------+----------------|N  |      GROUND    |   1   |   1   |  1 |  2 |   2   |  26   |    GROUND      |N  |      +DB(0)    |   2   |   3   |  3 |  4 |   4   |  27   |    -DB(0)      |N  |      +DB(1)    |   3   |   5   |  5 |  6 |   6   |  28   |    -DB(1)      |N  |      +DB(2)    |   4   |   7   |  7 |  8 |   8   |  29   |    -DB(2)      |N  |      +DB(3)    |   5   |   9   |  9 | 10 |  10   |  30   |    -DB(3)      |N  |      +DB(4)    |   6   |  11   | 11 | 12 |  12   |  31   |    -DB(4)      |N  |      +DB(5)    |   7   |  13   | 13 | 14 |  14   |  32   |    -DB(5)      |N  |      +DB(6)    |   8   |  15   | 15 | 16 |  16   |  33   |    -DB(6)      |N  |      +DB(7)    |   9   |  17   | 17 | 18 |  18   |  34   |    -DB(7)      |N  |      +DB(P)    |  10   |  19   | 19 | 20 |  20   |  35   |    -DB(P)      |N  |      DIFFSENS  |  11   |  21   | 21 | 22 |  22   |  36   |    GROUND      |N  |      RESERVED  |  12   |  23   | 23 | 24 |  24   |  37   |    RESERVED    |N  |      TERMPWR   |  13   |  25   | 25 | 26 |  26   |  38   |    TERMPWR     |N  |      RESERVED  |  14   |  27   | 27 | 28 |  28   |  39   |    RESERVED    |N  |      +ATN      |  15   |  29   | 29 | 30 |  30   |  40   |    -ATN        |N  |      GROUND    |  16   |  31   | 31 | 32 |  32   |  41   |    GROUND      |N  |      +BSY      |  17   |  33   | 33 | 34 |  34   |  42   |    -BSY        |N  |      +ACK      |  18   |  35   | 35 | 36 |  36   |  43   |    -ACK        |N  |      +RST      |  19   |  37   | 37 | 38 |  38   |  44   |    -RST        |N  |      +ACK      |  18   |  35   | 35 | 36 |  36   |  43   |    -ACK        |N  |      +RST      |  19   |  37   | 37 | 38 |  38   |  44   |    -RST        |N  |      +MSG      |  20   |  39   | 39 | 40 |  40   |  45   |    -MSG        |N  |      +SEL      |  21   |  41   | 41 | 42 |  42   |  46   |    -SEL        |N  |      +C/D      |  22   |  43   | 43 | 44 |  44   |  47   |    -C/D        |N  |      +REQ      |  23   |  45   | 45 | 46 |  46   |  48   |    -REQ        |N  |      +I/O      |  24   |  47   | 47 | 48 |  48   |  49   |    -I/O        |N  |      GROUND    |  25   |  49   | 49 | 50 |  50   |  50   |    GROUND      |N  |---------------------------------------------------------------------------|N  |NOTES                                                                      |N  |  1 The conductor number refers to the conductor position when using       |N  |    0,050 inch centreline flat ribbon cable with a low-density connector or|N  |    when using 0,025 inch centreline flat ribbon cable with a high-density |N  |    connector.  Other cable types may be used to implement equivalent      |N  |    contact assignments.                                                   |N  |  2 Two sets of contact assignments are shown.  Refer to table 1 to        |N  |    determine which set of contacts applies to each connector.             |N  |  3 See 5.4.4 for a definition of the RESERVED lines.                      |N  +===========================================================================+      B               Table 5 - Differential contact assignments - B cableN  +================-===============-=========-===============-================+N  |                |   Connector   |  Cable  |   Connector   |                |N  |      Signal    |    contact    |conductor|    contact    |    Signal      |N  |       name     |     number    | number  |     number    |     name       |N  |----------------+---------------+---------+---------------+----------------|N  |      GROUND    |       1       |  1 |  2 |      35       |    GROUND      |N  |      +DB(8)    |       2       |  3 |  4 |      36       |    -DB(8)      |N  |      +DB(9)    |       3       |  5 |  6 |      37       |    -DB(9)      |N  |      +DB(10)   |       4       |  7 |  8 |      38       |    -DB(10)     |N  |      +DB(11)   |       5       |  9 | 10 |      39       |    -DB(11)     |N  |      +DB(12)   |       6       | 11 | 12 |      40       |    -DB(12)     |N  |      +DB(13)   |       7       | 13 | 14 |      41       |    -DB(13)     |N  |      +DB(14)   |       8       | 15 | 16 |      42       |    -DB(14)     |N  |      +DB(15)   |       9       | 17 | 18 |      43       |    -DB(15)     |N  |      +DB(P1)   |      10       | 19 | 20 |      44       |    -DB(P1)     |N  |      +ACKB     |      11       | 21 | 22 |      45       |    -ACKB       |N  |      GROUND    |      12       | 23 | 24 |      46       |    DIFFSENS    |N  |      +REQB     |      13       | 25 | 26 |      47       |    -REQB       |N  |      +DB(16)   |      14       | 27 | 28 |      48       |    -DB(16)     |N  |      +DB(17)   |      15       | 29 | 30 |      49       |    -DB(17)     |N  |      +DB(18)   |      16       | 31 | 32 |      50       |    -DB(18)     |N  |      TERMPWRB  |      17       | 33 | 34 |      51       |    TERMPWRB    |N  |      TERMPWRB  |      18       | 35 | 36 |      52       |    TERMPWRB    |N  |      +DB(19)   |      19       | 37 | 38 |      53       |    -DB(19)     |N  |      +DB(20)   |      20       | 39 | 40 |      54       |    -DB(20)     |N  |      +DB(21)   |      21       | 41 | 42 |      55       |    -DB(21)     |N  |      +DB(22)   |      22       | 43 | 44 |      56       |    -DB(22)     |N  |      +DB(23)   |      23       | 45 | 46 |      57       |    -DB(23)     |N  |      +DB(P2)   |      24       | 47 | 48 |      58       |    -DB(P2)     |N  |      +DB(24)   |      25       | 49 | 50 |      59       |    -DB(24)     |N  |      +DB(25)   |      26       | 51 | 52 |      60       |    -DB(25)     |N  |      +DB(26)   |      27       | 53 | 54 |      61       |    -DB(26)     |N  |      +DB(27)   |      28       | 55 | 56 |      62       |    -DB(27)     |N  |      +DB(28)   |      29       | 57 | 58 |      63       |    -DB(28)     |N  |      +DB(29)   |      30       | 59 | 60 |      64       |    -DB(29)     |N  |      +DB(30)   |      31       | 61 | 62 |      65       |    -DB(30)     |N  |      +DB(31)   |      32       | 63 | 64 |      66       |    -DB(31)     |N  |      +DB(P3)   |      33       | 65 | 66 |      67       |    -DB(P3)     |N  |      GROUND    |      34       | 67 | 68 |      68       |    GROUND      |N  |---------------------------------------------------------------------------|N  |NOTE                                                                       |N  |  The conductor number refers to the conductor position when using         |N  |  0,025 inch centreline flat ribbon cable.  Other cable types may be used  |N  |  to implement equivalent contact assignments.                             |N  +===========================================================================+      M     NOTE 11 An alternate 16-bit single-cable solution and an alternate 32-bit M     solution is being defined and the B cable definition will be removed in a      future version of SCSI.   -  1  5.4 Electrical description    H  For the measurements in this subclause, SCSI bus termination is assumedB  to be external to the SCSI device.  See 5.4.4 for the terminatingJ  requirements for the RESERVED lines.  SCSI devices may have the provision,  for allowing optional internal termination.  4  5.4.1 Single-ended alternative   RA  All signals not defined as RESERVED, GROUND, or TERMPWR shall be|I  terminated at both ends of the cable.  The implementor may choose one of H  the following two methods to terminate each end (see figures 9 and 10):  )N     a)     The termination of each signal shall consist of 220 ohms (+/-5%) toL            the TERMPWR line and 330 ohms (+/-5%) to ground.  Using resistors7            with +/-1% tolerance improves noise margins. H     b)     The termination of each signal shall meet these requirements:J         1)    The terminators shall each supply a characteristic impedance-               between 100 ohms and 132 ohms.  J         2)    The terminators shall be powered by the TERMPWR line and mayO               receive additional power from other sources but shall not require E               such additional power for proper operation (see 5.4.3). N         3)    The current available to any signal line driver shall not exceedP               48 mA when the driver asserts the line and pulls it to 0,5 V d.c. J               Only 44,8 mA of this current shall be available from the two               terminators.N         4)    The voltage on all released signal lines shall be at least 2,5 VH               d.c. when the TERMPWR line is within specified values (see               5.4.3). K         5)    These conditions shall be met with any legal configuration of1F               targets and initiators as long as at least one device is                supplying TERMPWR.  BI  The first termination method above is the same as in SCSI-1.  The second =  termination method is recommended for better signal quality.   6  5.4.1.1 Output characteristics-  -J  All signals shall use open-collector or three-state drivers.  Each signalI  driven by an SCSI device shall have the following output characteristics|.  when measured at the SCSI device's connector:  eD  VOL (low-level output voltage) = 0,0 to 0,5 V d.c. at 48 mA sinking  (signal assertion)u  gG  VOH (high-level output voltage) = 2,5 to 5,25 V d.c. (signal negation)e  a  5.4.1.2 Input characteristics  a?  SCSI devices with power on shall meet the following electrical=E  characteristics on each signal (including both receivers and passiveh
  drivers):J  VIL (low-level input voltage)    = 0,0 V d.c. to 0,8 V d.c. (signal true)L  VIH (high-level input voltage)   = 2,0 V d.c. to 5,25 V d.c. (signal false)H  IIL (low-level input current)    = -0,4 mA to 0,0 mA at VI = 0,5 V d.c.F  IIH (high-level input current)   = 0,0 mAto 0,1 mA at VI = 2,7 V d.c..  Minimum input hysteresis         = 0,2 V d.c.L  Maximum input capacitance        = 25 pF (measured at the device connector L                                     closest to the stub, if any, within the +                                     device)-  -K  It is recommended that SCSI devices with power off also meet the above IILe3  and IIH electrical characteristics on each signal.-  -F  To achieve maximum noise immunity and to assure proper operation withK  complex cable configurations, it is recommended that the nominal switching "  threshold be approximately 1,4 V.     5.4.2 Differential alternative    H  All signals consist of two lines denoted +SIGNAL and -SIGNAL.  A signalJ  is true when +SIGNAL is more positive than -SIGNAL, and a signal is falseI  when -SIGNAL is more positive than +SIGNAL.  All assigned signals of the G  A and B cables described in 5.6 shall be terminated at each end of the|A  cable with a terminator network as shown in figure 11.  Resistor5>  tolerances in the terminator network shall be +/-5 % or less.   J  The DIFFSENS signal of the connector is used as an active high enable forE  the differential drivers.  If a single-ended device or terminator is @  inadvertently connected, this signal is grounded, disabling the&  differential drivers (see figure 12).   F  The characteristic impedance of differential terminators is 122 ohms.  E  5.4.2.1 Output characteristics   2E  Each signal driven by an SCSI device shall have the following output1>  characteristics when measured at the SCSI device's connector:K  VOL (low-level output voltage)    = 1,7 V maximum at IOL (low-level output 6                                      current) = 55 mA.E  VOH (high-level output voltage)   = 2,7 V minimum at IOH (high-level >                                      output current) = -55 mA.C  VOD (differential output voltage) = 1,0 V minimum with common-mode P                                      voltage ranges from -7 V d.c. to +12 V d.c.   J  VOL and VOH shall be as measured between the output terminal and the SCSI!  device's logic ground reference.   SJ  The output characteristics shall additionally conform to EIA RS-485-1983.  S  5.4.2.2 Input characteristics   I  SCSI devices shall meet the following electrical characteristics on each 7  signal (including both receivers and passive drivers):|<  II (input current on either input)    = +/- 2,0 mA maximum./  Maximum input capacitance             = 25 pF.4   J  The II requirement shall be met with the input voltage varying between -7E  V d.c. and +12 V d.c., with power on or off, and with the hysteresis-  equaling 35 mv, minimum.-  -I  The input characteristics shall additionally conform to EIA RS-485-1983.      5.4.3 Terminator power    H  SCSI initiators shall supply terminator power to the TERMPWR contact(s)G  and, if it implements the wide SCSI option, to the TERMPWRB contacts. tK  This power shall be supplied through a diode or similar semiconductor thatdI  prevents backflow of power to the SCSI device.  Targets and SCSI devicesvH  that become temporary initiators (e.g. targets which implement the COPYG  command or asynchronous event notification) are not required to supplyeK  terminator power.  Any SCSI device may supply terminator power.  InterfacecF  error rates are lower if the termination voltage is maintained at the  extreme ends of the cable.   |J  All terminators independent of location shall be powered from the TERMPWRH  and TERMPWRB contact(s).  The use of keyed connectors is recommended inK  SCSI devices that provide terminator power to prevent accidental grounding=1  or the incorrect connection of terminator power.e   L     NOTE 12 Regulatory agencies may require limiting maximum (short circuit)O     current to the terminator power lines.  Recommended current limiting is 1,5 G     A for TERMPWR and 2 A for TERMPWRB.  For systems utilizing multiple-N     initiators, the initiators may be configured with option straps or currentG     limiting devices.  Maximum available current should not exceed 5 A.   3J  SCSI devices shall sink no more than 1,0 mA from TERMPWR and no more thanF  1,0 mA from TERMPWRB except to power an optional internal terminator.   K  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.6                 900 mA minimum source drive capability   K  Differential SCSI devices providing terminator power on cable A shall have   the following characteristics:5)  VTerm        = 4,0 V d.c. to 5,25 V d.c.|6                 600 mA minimum source drive capability   K  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. 7                 1500 mA minimum source drive capability   |K  Differential SCSI devices providing terminator power on cable B shall have5  the following characteristics: )  VTerm        = 4,0 V d.c. to 5,25 V d.c. 7                 1000 mA minimum source drive capability7   M     NOTE 13 It is recommended that the terminator power lines be decoupled at N     each terminator with at least a 2,2 uF high-frequency capacitor to improve     signal quality.|        5           R  R              MF          Figure 9 - Alternative 1 termination for single-ended devices     (                    |        5           B  )              (                    |        5           B  )            G          Figure 10 - Alternative 2 termination for single-ended devices|     D  2        2        3  4                 -  2@                 Figure 11 - Termination for differential devices        B  )              (         A                Figure 12 - Differential driver protection circuit(        5.4.4 RESERVED lines    E  The lines labelled RESERVED in the A cable contact assignment tables|I  (table 2 and table 4) shall be connected to ground in the bus terminator H  assemblies or in the end devices on the SCSI cable.  The RESERVED linesJ  should be open in the other SCSI devices, but may be connected to ground.   
  5.5 SCSI bus    J  Communication on the SCSI bus is allowed between only two SCSI devices atF  any given time.  There is a maximum of eight SCSI devices.  Each SCSIH  device has an SCSI ID bit assigned as shown in figure 13.  Three sample@  system configurations are shown in figure 14.  There can be anyH  combination of initiators and targets provided there is at least one of  each.   B  When two SCSI devices communicate on the SCSI bus, one acts as anG  initiator and the other acts as a target.  The initiator originates anEI  operation and the target performs the operation.  An SCSI device usually|I  has a fixed role as an initiator or target, but some devices may be able|  to assume either role.n  lK  An initiator may address up to eight peripheral devices that are connectednH  to a target.  The target may be physically housed within the peripheralI  device in which case the peripheral device is referred to as an embeddedE
  SCSI device.e  -J  Certain SCSI bus functions are assigned to the initiator and certain SCSIK  bus functions are assigned to the target.  The initiator may arbitrate for I  the SCSI bus and select a particular target.  The target may request thetI  transfer of COMMAND, DATA, STATUS, or other information on the DATA BUS, D  and in some cases it may arbitrate for the SCSI bus and reselect an6  initiator for the purpose of continuing an operation.   D  Information transfers on the DATA BUS are asynchronous and follow aD  defined REQ/ACK handshake protocol.  One byte of information may beE  transferred with each handshake on the A cable and, if the wide dataeI  transfer option is implemented, one or three bytes of information may be0J  transferred with each handshake on the B cable.  An option is defined for  synchronous data transfer.R  R  n  n  3  h  (  5  t  r  d  U  g  s  o           w     1  o  a     r  s4                             Figure 13 - SCSI ID bits  a  h     t  e  r  i  e  :        )        m  t     l  a  s  l     r  e  t  i  d  e              w        s  d  2  m           )        m;                      Figure 14 - Sample SCSI configurations      5.6 SCSI bus signalsw  fG  There are a total of 18 signals on the A cable and 29 signals on the BoG  cable.  A total of 11 signals are used for control and 36 are used forlE  data (messages, commands, status and data), including parity.  Theset"  signals are described as follows:   N  a)        BSY (BUSY).  An OR-tied signal that indicates that the bus is being            used.   L  b)        SEL (SELECT).  An OR-tied signal used by an initiator to select a:            target or by a target to reselect an initiator.   M     NOTE 14 The SEL signal was not defined as OR-tied in SCSI-1.  It has beentK     defined as OR-tied in SCSI-2 in anticipation of needing another OR-tied J     signal for future standardization.  This does not cause an operational0     problem in mixing SCSI-1 and SCSI-2 devices.  mJ  c)        C/D (CONTROL/DATA).  A signal driven by a target that indicatesH            whether CONTROL or DATA information is on the DATA BUS.  True            indicates CONTROL.e  aM  d)        I/O (INPUT/OUTPUT).  A signal driven by a target that controls thetH            direction of data movement on the DATA BUS with respect to anL            initiator. True indicates input to the initiator.  This signal isM            also used to distinguish between SELECTION and RESELECTION phases.   aI  e)        MSG (MESSAGE).  A signal driven by a target during the MESSAGE             phase.o  gH  f)        REQ (REQUEST).  A signal driven by a target on the A cable toH            indicate a request for an ACK information transfer handshake.   I  g)        REQB (REQUEST).  A signal driven by a target on the B cable to5I            indicate a request for an ACKB information transfer handshake.m  tM  h)        ACK (ACKNOWLEDGE).  A signal driven by an initiator on the A cable,G            to indicate an acknowledgment for a REQ information transferc            handshake.p  mN  i)        ACKB (ACKNOWLEDGE).  A signal driven by an initiator on the B cableH            to indicate an acknowledgment for a REQB information transfer            handshake.d  tL  j)        ATN (ATTENTION).  A signal driven by an initiator to indicate the            ATTENTION condition.    N  k)        RST (RESET).  An OR-tied signal that indicates the RESET condition.  bK  l)        DB(7-0,P) (DATA BUS).  Eight data-bit signals, plus a parity-bitbN            signal that form a DATA BUS.  DB(7) is the most significant bit andN            has the highest priority during the ARBITRATION phase.  Bit number,M            significance, and priority decrease downward to DB(0).  A data bitoL            is defined as one when the signal value is true and is defined asK            zero when the signal value is false.  Data parity DB(P) shall beoB            odd.  Parity is undefined during the ARBITRATION phase.  wI  m)     DB(31-8,P1,P2,P3) (DATA BUS).  Twenty-four data-bit signals, plusuJ         three parity-bit signals that form an extension to the DATA BUS.  K         DB(P1,P2,P3) are parity bits for DB(15-8), DB(23-16), and DB(31-24)eL         respectively.  A data bit is defined as one when the signal value isI         true and is defined as zero when the signal value is false.  Data #         parity DB(Px) shall be odd.i     5.6.1 Signal values  aK  Signals may assume true or false values.  There are two methods of driving I  these signals.  In both cases, the signal shall be actively driven true,lH  or asserted.  In the case of OR-tied drivers, the driver does not driveD  the signal to the false state, rather the bias circuitry of the busJ  terminators pulls the signal false whenever it is released by the driversL  at every SCSI device.  If any driver is asserted, then the signal is true. F  In the case of non-OR-tied drivers, the signal may be actively drivenK  false.  In this International Standard, wherever the term negated is used, H  it means that the signal may be actively driven false, or may be simplyJ  released (in which case the bias circuitry pulls it false), at the optionE  of the implementor.  The advantage to actively driving signals false F  during information transfer is that the transition from true to falseK  occurs more quickly and the noise margin is much higher than if the signal E  is simply released.  This facilitates reliable data transfer at high E  rates, especially at the longer cable lengths used with differentialf	  drivers.t  h  5.6.2 OR-tied signals  ,F  The BSY, SEL, and RST signals shall be OR-tied only.  In the ordinaryK  operation of the bus, the BSY and RST signals may be simultaneously drivensH  true by several drivers.  No signals other than BSY, RST, and DB(P) areH  simultaneously driven by two or more drivers, and any signal other thanJ  BSY, SEL, and RST may employ OR-tied or non-OR-tied drivers.  DB(P) shallI  not be driven false during the ARBITRATION phase but may be driven falseyH  in other phases.  There is no operational problem in mixing OR-tied and7  non-OR-tied drivers on signals other than BSY and RST.i  o  5.6.3 Signal sourcesc  aF  Table 6 indicates which type of SCSI device is allowed to source eachG  signal.  No attempt is made to show if the source is driving asserted, F  driving negated, or is passive.  All SCSI device drivers that are notH  active sources be in the passive state.  The RST signal may be asserted   by any SCSI device at any time.  a4                             Table 6 - Signal sourcesP  +==============-=====================================-========================+P  |  Bus phase   |         A cable signals             |     B cable signals    |P  |              |-------------------------------------+------------------------|P  |              |      |      | C/D, |      |         |      |      | DB(31-8) |P  |              |      |      | I/O, |      |         |      |      |  DB(P1)  |P  |              |      |      | MSG, | ACK, | DB(7-0) |      |      |  DB(P2)  |P  |              | BSY  | SEL  | REQ  | ATN  |  DB(P)  | REQB | ACKB |  DB(P3)  |P  |--------------+------+------+------+------+---------+------+------+----------|P  |  BUS FREE    | None | None | None | None |   None  | None | None |    None  |P  |  ARBITRATION | All  | Win  | None | None |   S ID  | None | None |    None  |P  |  SELECTION   | I&T  | Init | None | Init |   Init  | None | None |    None  |P  |  RESELECTION | I&T  | Targ | Targ | Init |   Targ  | None | None |    None  |P  |  COMMAND     | Targ | None | Targ | Init |   Init  | None | None |    None  |P  |  DATA IN     | Targ | None | Targ | Init |   Targ  | Targ | Init |    Targ  |P  |  DATA OUT    | Targ | None | Targ | Init |   Init  | Targ | Init |    Init  |P  |  STATUS      | Targ | None | Targ | Init |   Targ  | None | None |    None  |P  |  MESSAGE IN  | Targ | None | Targ | Init |   Targ  | None | None |    None  |P  |  MESSAGE OUT | Targ | None | Targ | Init |   Init  | None | None |    None  |P  |-----------------------------------------------------------------------------|P  |                                                                             |P  |All:    The signal shall be driven by all SCSI devices that are actively     |P  |        arbitrating.                                                         |P  |                                                                             |P  |S ID:   A unique data bit (the SCSI ID) shall be driven by each SCSI device  |P  |        that is actively arbitrating; the other seven data bits shall be     |P  |        released (i.e., not driven) by this SCSI device.  The parity bit     |P  |        (DB(P)) may be released or driven to the true state, but shall never |P  |        be driven to the false state during this phase.                      |P  |                                                                             |P  |I&T:    The signal shall be driven by the initiator, target, or both, as     |P  |        specified in the SELECTION phase and RESELECTION phase.              |P  |                                                                             |P  |Init:   If driven, this signal shall be driven only by the active initiator. |P  |                                                                             |P  |None:   The signal shall be released; that is, not be driven by any SCSI     |P  |        device.  The bias circuitry of the bus terminators pulls the signal  |P  |        to the false state.                                                  |P  |                                                                             |P  |Win:    The signal shall be driven by the one SCSI device that wins          |P  |        arbitration.                                                         |P  |                                                                             |P  |Targ:   If the signal is driven, it shall be driven only by the active       |P  |        target.                                                              |P  +=============================================================================+  o  n  5.7 SCSI bus timing  tF  Unless otherwise indicated, the delay-time measurements for each SCSIE  device, shown in table 7, shall be calculated from signal conditions E  existing at that SCSI device's own SCSI bus connection.  Thus, theseSG  measurements (except cable skew delay) can be made without considering D  delays in the cable.  The timing characteristics of each signal are'  described in the following paragraphs.n   8                         Table 7 - SCSI bus timing valuesE  +==============================-===================================+lE  |  Timing description          |      Timing value                 | E  |------------------------------+-----------------------------------| E  |  Arbitration delay           |     2,4 us                        | E  |  Assertion period            |      90 ns                        | E  |  Bus clear delay             |     800 ns                        |sE  |  Bus free delay              |     800 ns                        |lE  |  Bus set delay               |     1,8 us                        |sE  |  Bus settle delay            |     400 ns                        |4E  |  Cable skew delay            |      10 ns                        |aE  |  Data release delay          |     400 ns                        |eE  |  Deskew delay                |      45 ns                        |tE  |  Disconnection delay         |     200 us                        |gE  |  Hold time                   |      45 ns                        |sE  |  Negation period             |      90 ns                        | E  |  Power-on to selection time  |      10 s recommended             | E  |  Reset to selection time     |     250 ms recommended            |EE  |  Reset hold time             |      25 us                        | E  |  Selection abort time        |     200 us                        |tE  |  Selection time-out delay    |     250 ms recommended            |eE  |  Transfer period             |     set during an SDTR message    | E  |  Fast assertion period       |      30 ns                        | E  |  Fast cable skew delay       |       5 ns                        | E  |  Fast deskew delay           |      20 ns                        |nE  |  Fast hold time              |      10 ns                        |mE  |  Fast negation period        |      30 ns                        |iE  +==================================================================+t  i  5.7.1 Arbitration delay     B  The minimum time an SCSI device shall wait from asserting BSY forI  arbitration until the DATA BUS can be examined to see if arbitration hasE%  been won.  There is no maximum time.      5.7.2 Assertion period   tF  The minimum time that a target shall assert REQ (or REQB) while usingF  synchronous data transfers.  Also, the minimum time that an initiatorI  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 i  eK  The maximum time for an SCSI device to stop driving all bus signals after:m5     a)     The BUS FREE phase is detected (see 6.1.1) J     b)     SEL is received from another SCSI device during the ARBITRATION            phase)     c)     The transition of RST to true.   NF  For the first condition above, the maximum time for an SCSI device toG  clear the bus is 1200 nanoseconds from BSY and SEL first becoming bothtJ  false.  If an SCSI device requires more than a bus settle delay to detectJ  BUS FREE phase, it shall clear the bus within a bus clear delay minus the
  excess time.      5.7.4 Bus free delay    J  The minimum time that an SCSI device shall wait from its detection of theH  BUS FREE phase (see 6.1.1) until its assertion of BSY when going to the  ARBITRATION phase.   i  5.7.5 Bus set delay n  vI  The maximum time for an SCSI device to assert BSY and its SCSI ID bit onlI  the DATA BUS after it detects BUS FREE phase (see 6.1.1) for the purposen#  of entering the ARBITRATION phase.   3  5.7.6 Bus settle delay   eF  The minimum time to wait for the bus to settle after changing certain;  control signals as called out in the protocol definitions.e  r  5.7.7 Cable skew delay   1H  The maximum difference in propagation time allowed between any two SCSI3  bus signals measured between any two SCSI devices.s  r  5.7.8 Data release delay   eB  The maximum time for an initiator to release the DATA BUS signals?  following the transition of the I/O signal from false to true.o  t  5.7.9 Deskew delay   s9  The minimum time required for deskew of certain signals.   e  5.7.10 Disconnection delay    E  The minimum time that a target shall wait after releasing BSY beforeaJ  participating in an ARBITRATION phase when honouring a DISCONNECT message  from the initiator.     5.7.11 Hold time   rI  The minimum time added between the assertion of REQ (or REQB) or ACK (orhE  ACKB) and the changing of the data lines to provide hold time in theeK  initiator or target while using synchronous data transfers.  REQB and ACKBe5  timings only apply to optional wide data transfers. y     5.7.12 Negation period   aF  The minimum time that a target shall negate REQ (or REQB) while usingF  synchronous data transfers.  Also, the minimum time that an initiatorI  shall negate ACK (or ACKB) while using synchronous data transfers.  REQBa>  and ACKB timings only apply to optional wide data transfers.   r#  5.7.13 Power-on to selection time a  tI  The recommended maximum time from power application until an SCSI targetdK  is able to respond with appropriate status and sense data to the TEST UNITR,  READY, INQUIRY, and REQUEST SENSE commands.  y   5.7.14 Reset to selection time   RH  The recommended maximum time after a hard RESET condition until an SCSIH  target is able to respond with appropriate status and sense data to the6  TEST UNIT READY, INQUIRY, and REQUEST SENSE commands.  T  5.7.15 Reset hold time   -G  The minimum time for which RST is asserted.  There is no maximum time.h     5.7.16 Selection abort time t   G  The maximum time that a target (or initiator) shall take from its mostiI  recent detection of being selected (or reselected) until asserting a BSY A  response.  This time-out is required to ensure that a target (orcH  initiator) does not assert BSY after a SELECTION (or RESELECTION) phaseJ  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.   !  5.7.17 Selection time-out delay     K  The minimum time that an SCSI device should wait for a BSY response duringuL  the SELECTION or RESELECTION phase before starting the time-out procedure.   =  +K     Note 15 The selection time-out delay is only a recommended time period.   |  5.7.18 Transfer period   -E  The minimum time allowed between the leading edges of successive REQ L  pulses or of successive ACK pulses while using synchronous data transfers.   (See 6.1.5.2 and 6.6.21.)   %  5.8 Fast synchronous transfer option    K  When devices negotiate a synchronous data transfer period of less than 200 G  ns they are said to be using fast synchronous data transfers.  Devices H  that negotiate a synchronous data transfer period greater than or equalK  to 200 ns use timing parameters specified in 5.7.  When a fast synchronousnK  data transfer period is negotiated, those specific times redefined in this|D  section are used; those not redefined remain the same.  The minimum,  synchronous data transfer period is 100 ns.     5.8.1 Fast assertion period a   K  The minimum time that a target shall assert REQ (or REQB) while using fastnK  synchronous data transfers.  It is also the minimum time that an initiator I  shall assert ACK (or ACKB) while using fast synchronous data transfers. IC  REQB and ACKB timings only apply to optional wide data transfers. n     5.8.2 Fast cable skew delay N   H  The maximum difference in propagation time allowed between any two SCSIC  bus signals measured between any two SCSI devices while using fast   synchronous data transfers.     5.8.3 Fast deskew delay -  -I  The minimum time required for deskew of certain signals while using fast   synchronous data transfers.     5.8.4 Fast hold time   :I  The minimum time added between the assertion of REQ (or REQB) or ACK (or E  ACKB) and the changing of the data lines to provide hold time in the K  initiator or target while using fast synchronous data transfers.  REQB and :  ACKB timings only apply to optional wide data transfers.   e  5.8.5 Fast negation period   |K  The minimum time that a target shall negate REQ (or REQB) while using fast|F  synchronous data transfers.  Also, the minimum time that an initiatorI  shall negate ACK (or ACKB) while using fast synchronous data transfers. bB  REQB and ACKB timings only apply to optional wide data transfers.  a     6 Logical characteristics     6.1 SCSI bus phases   6  The SCSI architecture includes eight distinct phases:  h         a)    BUS FREE phase         b)    ARBITRATION phase          c)    SELECTION phasee         d)    RESELECTION phasep%         e)    COMMAND phase         + O         f)    DATA phase            |      These phases are collectively termedeK         g)    STATUS phase          |      the information transfer phases. %         h)    MESSAGE phase         +    H  The SCSI bus can never be in more than one phase at any given time.  InH  the following descriptions, signals that are not mentioned shall not be
  asserted.  o  6.1.1 BUS FREE phase    K  The BUS FREE phase indicates that there is no current I/O process and that ,  the SCSI bus is available for a connection.   K  SCSI devices shall detect the BUS FREE phase after the SEL and BSY signalsn0  are both false for at least a bus settle delay.  tI  SCSI devices shall release all SCSI bus signals within a bus clear delay I  after the BSY and SEL signals become continuously false for a bus settlegJ  delay.  If an SCSI device requires more than a bus settle delay to detectK  the BUS FREE phase then it shall release all SCSI bus signals within a bus K  clear delay minus the excess time to detect the BUS FREE phase.  The total=J  time to clear the SCSI bus shall not exceed a bus settle delay plus a bus
  clear delay.r  nD  During normal operation the BUS FREE phase is entered when a targetE  releases the BSY signal.  However, the BUS FREE phase may be enteredtI  following the release of the SEL signal after a SELECTION or RESELECTIONh  phase time-out.  lI  Initiators normally do not expect BUS FREE phase to begin because of thedE  target's release of the BSY signal except after one of the followingC
  occurrences:a/     a)     after a reset condition is detected;=G     b)     after an ABORT message is successfully received by a target; I     c)     after a BUS DEVICE RESET message is successfully received by a-            target;O     d)     after a DISCONNECT message is successfully transmitted from a targete            (see 6.6.6); L     e)     after a COMMAND COMPLETE message is successfully transmitted from             a target (see 6.6.5);I     f)     after a RELEASE RECOVERY message is successfully received by au            target;K     g)     after an ABORT TAG message is successfully received by a target; L     h)     after a CLEAR QUEUE message is successfully received by a target.   K  If an initiator detects the release of the BSY signal by the target at any K  other time, the target is indicating an error condition to the initiator.  I  The target may perform this transition to the BUS FREE phase independent K  of the state of the ATN signal.  The initiator shall manage this condition K  as an unsuccessful I/O process termination.  The target terminates the I/O D  process by clearing all pending data and status information for theJ  affected nexus.  The target may optionally prepare sense data that may be&  retrieved by a REQUEST SENSE command.  s  6.1.2 ARBITRATION phase  |I  The ARBITRATION phase allows one SCSI device to gain control of the SCSIe6  bus so that it can initiate or resume an I/O process.   I  The procedure for an SCSI device to obtain control of the SCSI bus is as 	  follows:aM     a)     The SCSI device shall first wait for the BUS FREE phase to occur. eO            The BUS FREE phase is detected whenever both the BSY and SEL signals K            are simultaneously and continuously false for a minimum of a bus             settle delay.   J     NOTE 16 This bus settle delay is necessary because a transmission lineM     phenomenon known as a wired-OR glitch may cause the BSY signal to briefly 6     appear false, even though it is being driven true.  eI     b)     The SCSI device shall wait a minimum of a bus free delay after N            detection of the BUS FREE phase (i.e. after the BSY and SEL signalsL            are both false for a bus settle delay) before driving any signal.H     c)     Following the bus free delay in step (b), the SCSI device mayN            arbitrate for the SCSI bus by asserting both the BSY signal and itsI            own SCSI ID, however the SCSI device shall not arbitrate (i.e.aN            assert the BSY signal and its SCSI ID) if more than a bus set delayA            has passed since the BUS FREE phase was last observed.h   M     NOTE 17 There is no maximum delay before asserting the BSY signal and theuO     SCSI ID following the bus free delay in step (b) as long as the bus remains N     in the BUS FREE phase.  However, SCSI devices that delay longer than a busP     settle delay plus a bus set delay from the time when the BSY and SEL signalsM     first become false may fail to participate in arbitration when competing s     with faster SCSI devices.n  bI     d)     After waiting at least an arbitration delay (measured from itsTN            assertion of the BSY signal) the SCSI device shall examine the DATAI            BUS.  If a higher priority SCSI ID bit is true on the DATA BUSAD            (DB(7) is the highest), then the SCSI device has lost theM            arbitration and the SCSI device may release its signals and returncN            to step (a).  If no higher priority SCSI ID bit is true on the DATAI            BUS, then the SCSI device has won the arbitration and it shalluL            assert the SEL signal.  Any SCSI device other than the winner hasM            lost the arbitration and shall release the BSY signal and its SCSInN            ID bit within a bus clear delay after the SEL signal becomes true. H            An SCSI device that loses arbitration may return to step (a).  o	     NOTEStO     18 Step d) above requires that any device complete the arbitration phase torP     the point of SEL being asserted if it begins the arbitration phase as statedF     in step c).  This precludes the possibility of the bus being hung.L     19 It is recommended that new implementations wait for the SEL signal toP     become true before releasing the BSY signal and SCSI ID bit when arbitration     is lost.  oJ     e)     The SCSI device that wins arbitration shall wait at least a busM            clear delay plus a bus settle delay after asserting the SEL signal '            before changing any signals.n  oO     NOTE 20 The SCSI ID bit is a single bit on the DATA BUS that corresponds torL     the SCSI device's unique SCSI address.  All other DATA BUS bits shall beL     released by the SCSI device.  Parity is not valid during the ARBITRATIONP     phase.  During the ARBITRATION phase, DB(P) may be released or asserted, but'     shall not be actively driven false.i     6.1.3 SELECTION phase   K  The SELECTION phase allows an initiator to select a target for the purposedJ  of initiating some target function (e.g., READ or WRITE command).  DuringH  the SELECTION phase the I/O signal is negated so that this phase can be*  distinguished from the RESELECTION phase.   J  The SCSI device that won the arbitration has both the BSY and SEL signalsF  asserted and has delayed at least a bus clear delay plus a bus settleI  delay before ending the ARBITRATION phase.  The SCSI device that won thecC  arbitration becomes an initiator by not asserting the I/O signal. c  SK  The initiator shall set the DATA BUS to a value that is the OR of its SCSItG  ID bit and the target's SCSI ID bit and it shall assert the ATN signalmI  (indicating that a MESSAGE OUT phase is to follow the SELECTION phase).  I  The initiator shall then wait at least two deskew delays and release theiG  BSY signal.  The initiator shall then wait at least a bus settle delayh/  before looking for a response from the target.o  pK  The target shall determine that it is selected when the SEL signal and itseH  SCSI ID bit are true and the BSY and I/O signals are false for at leastK  a bus settle delay.  The selected target may examine the DATA BUS in orderaJ  to determine the SCSI ID of the selecting initiator.  The selected targetK  shall then assert the BSY signal within a selection abort time of its mostTK  recent detection of being selected; this is required for correct operation &  of the selection time-out procedure.   cH  The target shall not respond to a selection if bad parity is detected. J  Also, if more than two SCSI ID bits are on the DATA BUS, the target shall  not respond to selection.  nP     NOTE 21 Although an SCSI-2 initiator may not use the single initiator optionN     or the selection without asserting ATN option of SCSI-1, an SCSI-2 target Q     may elect to support these options for compatibility with SCSI-1 initiators.  H     When doing so the SCSI-2 target responds as described in the SCSI-1 
     standard.f  dJ  No less than two deskew delays after the initiator detects the BSY signalK  is true, it shall release the SEL signal and may change the DATA BUS.  ThelI  target shall wait until the SEL signal is false before asserting the REQi/  signal to enter an information transfer phase.l  s%  6.1.3.1 SELECTION time-out procedureh  oJ  Two optional selection time-out procedures are specified for clearing theH  SCSI bus if the initiator waits a minimum of a selection time-out delay;  and there has been no BSY signal response from the target:sM     a)     Optionally, the initiator shall assert the RST signal (see 6.2.2);tM     b)     Optionally, the initiator shall continue asserting the SEL and ATNrL            signals and shall release the DATA BUS.  If the initiator has notN            detected the BSY signal to be true after at least a selection abortO            time plus two deskew delays, the initiator shall release the SEL andlO            ATN signals allowing the SCSI bus to go to the BUS FREE phase.  SCSI J            devices shall ensure that when responding to selection that theK            selection was still valid within a selection abort time of theireD            assertion of the BSY signal.  Failure to comply with thisI            requirement could result in an improper selection (two targets H            connected to the same initiator, wrong target connected to an=            initiator, or a target connected to no initiator).s     6.1.4 RESELECTION phase  TI  RESELECTION is an optional phase that allows a target to reconnect to an K  initiator for the purpose of continuing some operation that was previously K  started by the initiator but was suspended by the target, (i.e. the target H  disconnected by allowing a BUS FREE phase to occur before the operation  was complete).   T  6.1.4.1 RESELECTION   t  iH  Upon completing the ARBITRATION phase, the winning SCSI device has bothF  the BSY and SEL signals asserted and has delayed at least a bus clearI  delay plus a bus settle delay.  The winning SCSI device becomes a target I  by asserting the I/O signal.  The winning SCSI device shall also set thehF  DATA BUS to a value that is the logical OR of its SCSI ID bit and theK  initiator's SCSI ID bit.  The target shall wait at least two deskew delayshG  and release the BSY signal.  The target shall then wait at least a bus ?  settle delay before looking for a response from the initiator.   aI  The initiator shall determine that it is reselected when the SEL and I/OsH  signals and its SCSI ID bit are true and the BSY signal is false for atI  least a bus settle delay.  The reselected initiator may examine the DATAwF  BUS in order to determine the SCSI ID of the reselecting target.  TheI  reselected initiator shall then assert the BSY signal within a selectionlE  abort time of its most recent detection of being reselected; this isSI  required for correct operation of the time-out procedure.  The initiatorhK  shall not respond to a RESELECTION phase if bad parity is detected.  Also,tI  the initiator shall not respond to a RESELECTION phase if other than twod#  SCSI ID bits are on the DATA BUS. b  uJ  After the target detects the BSY signal is true, it shall also assert theH  BSY signal and wait at least two deskew delays and then release the SELF  signal.  The target may then change the I/O signal and the DATA BUS. I  After the reselected initiator detects the SEL signal is false, it shall-E  release the BSY signal.  The target shall continue asserting the BSYu+  signal until it relinquishes the SCSI bus.e  .L     NOTE 22 When the target is asserting the BSY signal, a transmission lineL     phenomenon known as a wired-OR glitch may cause the BSY signal to appearO     false for up to a round-trip propagation delay following the release of theBN     BSY signal by the initiator.  This is the reason why the BUS FREE phase isN     recognized only after both the BSY and SEL signals are continuously false P     for a minimum of a bus settle delay.  Cables longer than 25 m should not be N     used even if the chosen driver, receiver, and cable provide adequate noiseM     margins, because they increase the duration of the glitch and could cause.<     SCSI devices to inadvertently detect the BUS FREE phase.   '  6.1.4.2 RESELECTION time-out procedurei  eH  Two optional RESELECTION time-out procedures are specified for clearingI  the SCSI bus during a RESELECTION phase if the target waits a minimum of J  a selection time-out delay and there has been no BSY signal response from  the initiator: J     a)     Optionally, the target shall assert the RST signal (see 6.2.2);J     b)     Optionally, the target shall continue asserting the SEL and I/OM            signals and shall release all DATA BUS signals.  If the target has L            not detected the BSY signal to be true after at least a selectionN            abort time plus two deskew delays, the target shall release the SELN            and I/O signals allowing the SCSI bus to go to the BUS FREE phase. O            SCSI devices that respond to the RESELECTION phase shall ensure that K            the reselection was still valid within a selection abort time ofrJ            their assertion of the BSY signal.  Failure to comply with thisN            requirement could result in an improper reselection (two initiatorsM            connected to the same target or the wrong initiator connected to aa            target).u  e"  6.1.5 Information transfer phases   I     NOTE 23 The COMMAND, DATA, STATUS, and MESSAGE phases are all grouped L     together as the information transfer phases because they are all used toN     transfer data or control information via the DATA BUS.  The actual content;     of the information is beyond the scope of this section.b  sB  The C/D, I/O, and MSG signals are used to distinguish between theH  different information transfer phases (see table 8).  The target drivesI  these three signals and therefore controls all changes from one phase to I  another.  The initiator can request a MESSAGE OUT phase by asserting the K  ATN signal, while the target can cause the BUS FREE phase by releasing thet   MSG, C/D, I/O, and BSY signals.   F  The information transfer phases use one or more REQ/ACK handshakes toE  control the information transfer.  Each REQ/ACK handshake allows thesF  transfer of one byte of information.  During the information transferH  phases the BSY signal shall remain true and the SEL signal shall remainI  false.  Additionally, during the information transfer phases, the targettH  shall continuously envelope the REQ/ACK handshake(s) with the C/D, I/O,J  and MSG signals in such a manner that these control signals are valid forG  a bus settle delay before the assertion of the REQ signal of the first I  handshake and remain valid until after the negation of the ACK signal atr<  the end of the handshake of the last transfer of the phase.   	     NOTES N     24 After the negation of the ACK signal of the last transfer of the phase,M     the target may prepare for a new phase by asserting or negating the C/D, CD     I/O, and MSG signals.  These signals may be changed together or P     individually. They may be changed in any order and may be changed more than N     once.  It is desirable that each line change only once.  A new phase does M     not begin until the REQ signal is asserted for the first byte of the new  
     phase.L     25 A phase is defined as ending when the C/D, I/O, or MSG signals changeN     after the negation of the ACK signal.  The time between the end of a phaseO     and the assertion of the REQ signal beginning a new phase is undefined.  An O     initiator is allowed to anticipate a new phase based on the previous phase, M     the expected new phase, and early information provided by changes in the nL     C/D, I/O, and MSG signals.  However, the anticipated phase is not valid H     until the REQ signal is asserted at the beginning of the next phase.  .:                      Table 8 - Information transfer phasesP  +=============-===============-==================================-============+P  |    Signal   |  Phase name   |       Direction of transfer      |  Comment   |P  |-------------|               |                                  |            |P  | MSG|C/D|I/O |               |                                  |            |P  |----+---+----+---------------+----------------------------------+------------|P  |  0 | 0 | 0  |  DATA OUT     |       Initiator to target     \  |  Data      |P  |  0 | 0 | 1  |  DATA IN      |       Initiator from target   /  |  phase     |P  |  0 | 1 | 0  |  COMMAND      |       Initiator to target        |            |P  |  0 | 1 | 1  |  STATUS       |       Initiator from target      |            |P  |  1 | 0 | 0  |  *            |                                  |            |P  |  1 | 0 | 1  |  *            |                                  |            |P  |  1 | 1 | 0  |  MESSAGE OUT  |       Initiator to target     \  |  Message   |P  |  1 | 1 | 1  |  MESSAGE IN   |       Initiator from target   /  |  phase     |P  |-----------------------------------------------------------------------------|P  | Key:  0 = False,  1 = True,  * = Reserved for future standardization        |P  +=============================================================================+  e  .*  6.1.5.1 Asynchronous information transfer  iH  The target shall control the direction of information transfer by meansF  of the I/O signal.  When the I/O signal is true, information shall beF  transferred from the target to the initiator.  When the I/O signal isJ  false, information shall be transferred from the initiator to the target.   H  If the I/O signal is true (transfer to the initiator), the target shallJ  first drive the DB(7-0,P) signals to their desired values, delay at leastK  one deskew delay plus a cable skew delay, then assert the REQ signal.  ThesI  DB(7-0,P) signals shall remain valid until the ACK signal is true at thefF  target.  The initiator shall read the DB(7-0,P) signals after the REQJ  signal is true, then indicate its acceptance of the data by asserting theH  ACK signal.  When the ACK signal becomes true at the target, the targetE  may change or release the DB(7-0,P) signals and shall negate the REQtK  signal.  After the REQ signal is false the initiator shall then negate thelG  ACK signal.  After the ACK signal is false the target may continue theoH  transfer by driving the DB(7-0,P) signals and asserting the REQ signal,  as described above.  aE  If the I/O signal is false (transfer to the target) the target shalluF  request information by asserting the REQ signal.  The initiator shallH  drive the DB(7-0,P) signals to their desired values, delay at least oneE  deskew delay plus a cable skew delay and assert the ACK signal.  The F  initiator shall continue to drive the DB(7-0,P) signals until the REQF  signal is false.  When the ACK signal becomes true at the target, theK  target shall read the DB(7-0,P), signals then negate the REQ signal.  WhenaH  the REQ signal becomes false at the initiator, the initiator may changeI  or release the DB(7-0,P) signals and shall negate the ACK signal.  After J  the ACK signal is false the target may continue the transfer by asserting$  the REQ signal, as described above.  w"  6.1.5.2 Synchronous data transfer   H  Synchronous data transfer is optional and is only used in data phases. J  It shall be used in a data phase if a synchronous data transfer agreementH  has been established (see 6.6.21).  The agreement specifies the REQ/ACK(  offset and the minimum transfer period.   J  The REQ/ACK offset specifies the maximum number of REQ pulses that can beH  sent by the target in advance of the number of ACK pulses received fromF  the initiator, establishing a pacing mechanism.  If the number of REQJ  pulses exceeds the number of ACK pulses by the REQ/ACK offset, the targetI  shall not assert the REQ signal until after the leading edge of the nextsG  ACK pulse is received.  For successful completion of the data phase isT7  that the number of ACK and REQ pulses shall be equal. a  SE  The target shall assert the REQ signal for a minimum of an assertion F  period. The target shall then wait at least the greater of a transferJ  period from the last transition of the REQ signal to true or a minimum ofF  a negation period from the last transition of the REQ signal to false'  before again asserting the REQ signal.   sH  The initiator shall send one pulse on the ACK signal for each REQ pulseI  received.  The ACK signal may be asserted as soon as the leading edge ofiK  the corresponding REQ pulse has been received.  The initiator shall assert J  the ACK signal for a minimum of an assertion period.  The initiator shallH  wait at least the greater of a transfer period from the last transitionI  of the ACK signal to true or for a minimum of a negation period from thegD  last transition of the ACK signal to false before asserting the ACK  signal.  lH  If the I/O signal is true (transfer to the initiator), the target shallI  first drive the DB(7-0,P) signals to their desired values, wait at least J  one deskew delay plus one cable skew delay, then assert the REQ signals. F  The DB(7-0,P) signals shall be held valid for a minimum of one deskewJ  delay plus one cable skew delay plus one hold time after the assertion ofI  the REQ signal.  The target shall assert the REQ signal for a minimum ofsK  an assertion period.  The target may then negate the REQ signal and changehI  or release the DB(7-0,P) signals.  The initiator shall read the value oneH  the DB(7-0,P) signals within one hold time of the transition of the REQE  signal to true.  The initiator shall then respond with an ACK pulse.   II  If the I/O signal is false (transfer to the target), the initiator shallsD  transfer one byte for each REQ pulse received.  After receiving theK  leading edge of a REQ pulse, the initiator shall first drive the DB(7-0,P)oJ  signals to their desired values, delay at least one deskew delay plus oneH  cable skew delay, then assert the ACK signal.  The initiator shall holdI  the DB(7-0,P) signals valid for at least one deskew delay plus one cable.J  skew delay plus one hold time after the assertion of the ACK signal.  TheD  initiator shall assert the ACK signal for a minimum of an assertionH  period.  The initiator may then negate the ACK signal and may change orG  release the DB(7-0,P) signals.  The target shall read the value of the-K  DB(7-0,P) signals within one hold time of the transition of the ACK signale	  to true.i   O     NOTE 26 The description in SCSI-1 allowed some implementors to presume thatlO     the leading edge of the first REQ pulse beyond the REQ/ACK offset agreementtN     would not occur until after the trailing edge of the last ACK pulse withinN     the agreement.  Devices implemented with this understanding may be subjectP     to data destruction when in synchronous data transfer mode with devices thatH     issue the leading edge of the next REQ pulse, at the boundary of theK     agreement, as soon as the leading edge of the last ACK pulse within theLL     agreement is received.  Implementors using devices of the former type inN     initiator designs may insure data integrity by restricting the synchronousL     offset agreement to values smaller than the maximum nominally offered by     their device.e  a  6.1.5.3 Wide data transferF  uI  Wide data transfer is optional and may be used in the DATA phase only ifrD  a non-zero wide data transfer agreement is in effect (see WIDE DATAK  TRANSFER REQUEST message, 6.6.23).  The messages determine the use of wideaE  mode by both SCSI devices and establish a data path width to be usedS  during the DATA phase.e   G  Wide data transfers of 16- or 32-bits may be established.  Targets and I  initiators that support 32-bit wide transfers should also support 16-bitcF  wide transfers.  All SCSI devices shall support 8-bit data transfers.  TH  During 16-bit wide data transfers, the first logical data byte for eachF  data phase shall be transferred across the DB(7-0,P) signals on the AG  cable and the second logical data byte shall be transferred across theoH  DB(15-8,P1) signals on the B cable.  Subsequent pairs of data bytes areG  likewise transferred in parallel across the A and B cables (see figuret  15).   ,O     NOTE 27 X3T9.2 is documenting an alternate 16-bit single-cable solution andAM     an alternate 32-bit solution and expects to be able to remove the B cablel+     definition in a future version of SCSI.n  DH  During 32-bit wide data transfers, the first logical data byte for eachF  data phase shall be transferred across the DB(7-0,P) signals on the AD  cable and the second, third, and fourth logical data bytes shall beC  transferred across the DB(15-8,P1), DB(23-16,P2), and DB(31-24,P3)nG  signals, respectively, on the B cable.  Subsequent groups of four datatJ  bytes are likewise transferred in parallel across the A and B cables (see  figure 15).  a  n           n  a     e  d        d  k  f  e  s  r  f  o  h  h  .   9                       Figure 15 - Wide SCSI byte orderingf  e  sK  If the last data byte transferred does not fall on the DB(15-8,P1) signalstI  for a 16-bit wide transfer or the DB(31-24,P3) signals for a 32-bit wide D  transfer, then the values of the remaining higher-numbered bits areJ  undefined.  However, parity bits for these undefined bytes shall be valid(  for whatever data is placed on the bus.   H  To ensure proper data integrity, certain sequence requirements shall beD  met between the REQ/ACK handshakes on the A cable and the REQB/ACKB  handshakes on the B cable:hN     a)     The REQB and ACKB signals shall only be asserted during data phasesL            while a nonzero wide data transfer agreement is in effect.  These=            signals shall not be asserted during other phases.sK     b)     The same information transfer mode (asynchronous or synchronous)eN            shall be used for both the A cable and the B cable.  If synchronousG            data transfer mode is in effect, the same REQ/ACK offset andx9            transfer period shall be used for both cables.aM     c)     The information transfer procedures defined in 6.1.5.1 and 6.1.5.2=K            for the A cable (the REQ, ACK, and DB(7-0,P) signals) shall also F            apply to the B cable (the REQB, ACKB, and DB(31-8,P1,P2,P3)I            signals).  The only means available for a target to manage the K            timing relationship between the signals on the two cables is its-M            management of the REQ and REQB signals.  Similarly, the only meansIO            for the initiator to manage the timing between the two cables is itsI2            management of the ACK and ACKB signals.L     d)     The target shall ensure that the number of REQ/ACK handshakes andN            the number of REQB/ACKB handshakes in a data phase are equal beforeN            it changes to another phase.  The target shall not change the phaseM            until the ACK and ACKB signals have both become false for the last >            REQ/ACK handshake and the last REQB/ACKB handshake.   L     NOTE 28 If any violations of these rules are detected by the target, theP     target may attempt to end the data phase and return CHECK CONDITION status. M     If it is impossible to correctly terminate the data phase, the target mayaM     abnormally terminate the I/O process by an unexpected disconnect.  If any=N     violations of these rules are detected by the initiator, the initiator mayN     attempt to send an INITIATOR DETECTED ERROR message to the target.  If theN     initiator is unable to terminate the I/O process normally, it may generate     the reset condition.  .  6.1.6 COMMAND phase   H  The COMMAND phase allows the target to request command information from  the initiator.   nJ  The target shall assert the C/D signal and negate the I/O and MSG signals/  during the REQ/ACK handshake(s) of this phase.t  a  6.1.7 Data phasea  lI  The data phase is a term that encompasses both the DATA IN phase and thes  DATA OUT phase.  n  6.1.7.1 DATA IN phase  aH  The DATA IN phase allows the target to request that data be sent to the  initiator from the target.n  aJ  The target shall assert the I/O signal and negate the C/D and MSG signals/  during the REQ/ACK handshake(s) of this phase.y  a  6.1.7.2 DATA OUT phase,  sK  The DATA OUT phase allows the target to request that data be sent from the   initiator to the target.   lI  The target shall negate the C/D, I/O, and MSG signals during the REQ/ACK   handshake(s) of this phase.  )  4s STATUS phase  gI  The STATUS phase allows the target to request that status information bea'  sent from the target to the initiator.r  eJ  The target shall assert the C/D and I/O signals and negate the MSG signal,  during the REQ/ACK handshake of this phase.     6.1.9 Message phase  aF  The message phase is a term that references either a MESSAGE IN, or aH  MESSAGE OUT phase.  Multiple messages may be sent during either phase. G  The first byte transferred in either of these phases shall be either aeC  single-byte message or the first byte of a multiple-byte message. QI  Multiple-byte messages shall be wholly contained within a single messages  phase.7  P  6.1.9.1 MESSAGE IN phaset  AJ  The MESSAGE IN phase allows the target to request that message(s) be sent"  to the initiator from the target.   I  The target shall assert the C/D, I/O, and MSG signals during the REQ/ACKd  handshake(s) of this phase.  n  6.1.9.2 MESSAGE OUT phase  hK  The MESSAGE OUT phase allows the target to request that message(s) be senteD  from the initiator to the target.  The target invokes this phase inJ  response to the attention condition created by the initiator (see 6.2.1).  iJ  The target shall assert the C/D and MSG signals and negate the I/O signalK  during the REQ/ACK handshake(s) of this phase.  The target shall handshakehC  byte(s) in this phase until the ATN signal is negated, except whens  rejecting a message.    I  If the target detects one or more parity error(s) on the message byte(s)eJ  received, it may indicate its desire to retry the message(s) by assertingJ  the REQ signal after detecting the ATN signal has gone false and prior toA  changing to any other phase.  The initiator, upon detecting thisrH  condition, shall resend all of the previous message byte(s) in the sameJ  order as previously sent during this phase.  When resending more than oneE  message byte, the initiator shall assert the ATN signal at least tworF  deskew delays prior to asserting the ACK signal on the first byte andF  shall maintain the ATN signal asserted until the last byte is sent as  described in 6.2.1.  hF  If the target does not retry the MESSAGE OUT phase or it exhausts its  retry limit it mayrI     a)     return CHECK CONDITION status and set the sense key to ABORTEDaE            COMMAND and the additional sense code to MESSAGE ERROR or;iF     b)     indicate an exception condition by performing an unexpected            disconnect.  oI  The target may act on messages as received as long as no parity error is/B  detected and may ignore all remaining messages sent under one ATNI  condition after a parity error is detected.  When a sequence of messageseI  is resent by an initiator because of a target detected parity error, theeE  target shall not act on any message which it acted on the first timel  received.     H  If the target receives all of the message byte(s) successfully (i.e. noD  parity errors), it shall indicate that it does not wish to retry byF  changing to any information transfer phase other than the MESSAGE OUTI  phase and transfer at least one byte.  The target may also indicate that(H  it has successfully received the message byte(s) by changing to the BUS6  FREE phase (e.g. ABORT or BUS DEVICE RESET messages).  e*  6.1.10 Signal restrictions between phases  oB  When the SCSI bus is between two information transfer phases, the<  following restrictions shall apply to the SCSI bus signals:J     a)     The BSY, SEL, REQ, REQB, ACK and ACKB signals shall not change.N     b)     The C/D, I/O, MSG, and DATA BUS signals may change.  When switchingL            the DATA BUS direction from out (initiator driving) to in (targetL            driving), the target shall delay driving the DATA BUS by at leastO            a data release delay plus a bus settle delay after asserting the I/OlL            signal and the initiator shall release the DATA BUS no later thanP            a data release delay after the transition of the I/O signal to true. L            When switching the DATA BUS direction from in (target driving) toL            out (initiator driving), the target shall release the DATA BUS noC            later than a deskew delay after negating the I/O signal.iO     c)     The ATN and RST signals may change as defined under the descriptionseK            for the attention condition (see 6.2.1) and reset condition (see             6.2.2).  n  s  6.2 SCSI bus conditions  oJ  The SCSI bus has two asynchronous conditions; the attention condition andH  the reset condition.  These conditions cause the SCSI device to perform2  certain actions and can alter the phase sequence.  AG  Furthermore, SCSI devices may not all be powered-on at the same time. cG  This standard does not address power sequencing issues.  However, each F  SCSI device, as it is powered on, should perform appropriate internalH  reset operations and internal test operations.  Following a power-on toK  selection time after power-on, SCSI targets should be able to respond withDG  appropriate status and sense data to the TEST UNIT READY, INQUIRY, and   REQUEST SENSE commands.    S  6.2.1 Attention condition  eH  The attention condition allows an initiator to inform a target that theC  initiator has a message ready.  The target may get this message byt   performing a MESSAGE OUT phase.  aK  The initiator creates the attention condition by asserting ATN at any time 2  except during the ARBITRATION or BUS FREE phases.  sE  The initiator shall negate the ATN signal at least two deskew delayssH  before asserting the ACK signal while transferring the last byte of theK  messages indicated with a Yes in table 10.  If the target detects that thebK  initiator failed to meet this requirement, then the target shall go to BUSu/  FREE phase (see unexpected disconnect, 6.1.1).f  eE  The initiator shall assert the ATN signal at least two deskew delaysOF  before negating the ACK signal for the last byte transferred in a busH  phase for the attention condition to be honoured before transition to aK  new bus phase.  Asserting the ATN signal later might not be honoured untildB  a later bus phase and then may not result in the expected action.  l:  A target shall respond with MESSAGE OUT phase as follows:L     a)     If the ATN signal becomes true during a COMMAND phase, the targetN            shall enter MESSAGE OUT phase after transferring part or all of the*            command descriptor block bytes.O     b)     If the ATN signal becomes true during a DATA phase, the target shalleO            enter MESSAGE OUT phase at the target's earliest convenience (often,sK            but not necessarily on a logical block boundary).  The initiatoreP            shall continue REQ/ACK handshakes until it detects the phase change.             tK     c)     If the ATN signal becomes true during a STATUS phase, the target G            shall enter MESSAGE OUT phase after the status byte has beend+            acknowledged by the initiator.  iO     d)     If the ATN signal becomes true during a MESSAGE IN phase, the targeteO            shall enter MESSAGE OUT phase before it sends another message.  ThisRJ            permits a MESSAGE PARITY ERROR message from the initiator to be3            associated with the appropriate message. M     e)     If the ATN signal becomes true during a SELECTION phase and beforegH            the initiator releases the BSY signal, the target shall enterE            MESSAGE OUT phase immediately after that SELECTION phase. cI     f)     If the ATN signal becomes true during a RESELECTION phase, the M            target shall enter MESSAGE OUT phase after the target has sent itsa9            IDENTIFY message for that RESELECTION phase.     dP     NOTE 29 The initiator should only assert the ATN signal during a RESELECTIONO     phase to transmit a BUS DEVICE RESET or DISCONNECT message.  Other uses may)/     result in ambiguities concerning the nexus.e  QJ  The initiator shall keep the ATN signal asserted if more than one byte isH  to be transferred.  The initiator may negate the ATN signal at any timeK  except it shall not negate the ATN signal while the ACK signal is asserted E  during a MESSAGE OUT phase.  Normally, the initiator negates the ATNaK  signal while the REQ signal is true and the ACK signal is false during theA1  last REQ/ACK handshake of the MESSAGE OUT phase.n  e  6.2.2 Reset condition   K  The reset condition is used to immediately clear all SCSI devices from the E  bus.  This condition shall take precedence over all other phases andhI  conditions.  Any SCSI device may create the reset condition by assertingt3  the RST signal for a minimum of a reset hold time.s  eD  All SCSI devices shall release all SCSI bus signals (except the RSTH  signal) within a bus clear delay of the transition of the RST signal to>  true.  The BUS FREE phase always follows the reset condition.  sA  The effect of the reset condition on I/O processes that have not H  completed, SCSI device reservations, and SCSI device operating modes isE  determined by whether the SCSI device has implemented the hard resetiA  alternative or the soft reset alternative (one of which shall begI  implemented) as defined in 6.2.2.1 and 6.2.2.2.  The hard and soft reseteE  alternatives are mutually exclusive within a system.  A facility forAH  targets to report which reset alternative is implemented is provided in/  the SftRe bit of the INQUIRY data (see 8.2.5).h   O     NOTE 30 Environmental conditions (e.g. static discharge) may generate briefdN     glitches on the RST signal.  It is recommended that SCSI devices not reactN     to these glitches.  The manner of rejecting glitches is vendor-specific.  N     The bus clear delay following a RST signal transition to true is measured O     from the original transition of the RST signal, not from the time that the sO     signal has been confirmed.  This limits the time to confirm the RST signal s&     to a maximum of a bus clear delay.     6.2.2.1 Hard reset alternativer   J  SCSI devices that implement the hard reset alternative, upon detection of  the reset condition, shall:B     a)     clear all I/O processes including queued I/O processes.0     b)     release all SCSI device reservations.N     c)     return any SCSI device operating modes to their appropriate initialL            conditions, similar to those conditions that would be found afterM            a normal power-on reset.  MODE SELECT conditions shall be restoredsM            to their last saved values if saved values have been established. NN            MODE SELECT conditions for which no values have been saved shall be,            returned to their default values.;     d)     unit attention condition shall be set (see 7.9).s  yH  It is recommended that following a reset to selection time after a hardG  reset condition ends, SCSI targets be able to respond with appropriatesI  status and sense data to the TEST UNIT READY, INQUIRY, and REQUEST SENSEb
  commands.     6.2.2.2 Soft reset alternativeT  tJ  SCSI devices that implement the soft reset alternative, upon detection of  the reset condition, shall:M     a)     Attempt to complete any I/O processes which have not completed ands%            that were fully identifiedn0     b)     Preserve all SCSI device reservationsO     c)     Preserve any SCSI device operating modes (MODE SELECT, PREVENT/ALLOW.)            MEDIUM REMOVAL commands, etc.)MO     d)     Preserve all the information required to continue normal dispatchinga@            of I/O processes queued prior to the reset condition.  NJ  The soft reset alternative allows an initiator to reset the SCSI bus withF  minimum disruption to the operation of other initiators in a multipleG  initiator system.  To ensure proper operation the following conditionsQ  shall be met.E     a)     An initiator shall not consider an I/O process to be fullyhK            identified until the IDENTIFY message (and queue tag message, ifoL            any) is sent to the target and the target responds by changing toN            any other information transfer phase and requests that at least one            byte be transferred. M     b)     A target shall consider an I/O process to be fully identified whenmJ            it successfully receives the IDENTIFY message and any queue tag<            message and the initiator negates the ATN signal.L     c)     If an initiator selects a logical unit for which there already isN            an active I/O process with the same queue tag (if any) for the sameI            initiator, the target shall clear the original I/O process andi'            perform the new I/O process. L     d)     If a target reselects an initiator to continue an I/O process forL            which the initiator has no record, the initiator shall abort thatN            I/O process by sending the ABORT or ABORT TAG message, depending onG            whether the reselecting I/O process is a tagged I/O process.hM     e)     An initiator shall consider an I/O process to be completed when itcL            negates ACK for a successfully received COMMAND COMPLETE message.I     f)     A target shall consider an I/O process to be completed when it J            detects the transition of ACK to false for the COMMAND COMPLETE-            message with the ATN signal false.gI     g)     An initiator shall not negate the ACK signal for the SAVE DATAsO            POINTER message until it has actually saved the data pointer for the             I/O process.cO     h)     A target shall consider the data pointer to be saved when it detectspN            the transition of the ACK signal to false for the SAVE DATA POINTER-            message with the ATN signal false.aI     i)     If the reset condition occurs between the time that the targetyJ            asserts the REQ signal for the SAVE DATA POINTER message and itN            detects the transition of the ACK signal to false, the target shallM            terminate the I/O process with CHECK CONDITION status.  The targetaI            shall set the sense key to ABORTED COMMAND.  This is necessarysK            because the target cannot determine whether the data pointer hasi            actually been saved.    N     NOTE 31 If the ATN signal is true in conditions f) or h), the target wouldQ     normally switch to MESSAGE OUT phase and attempt to transfer a message byte. lM     If the reset condition occurs before the target successfully receives thedP     message byte, it may assume that the initiator has not successfully receivedO     the COMMAND COMPLETE message or the SAVE DATA POINTER message.  In the casesJ     of COMMAND COMPLETE message, the target may reselect the initiator andP     attempt to send the COMMAND COMPLETE message again.  In the case of the SAVEQ     DATA POINTER message, the target may reselect the initiator and terminate ther-     I/O process as described in condition i).n     6.3 SCSI bus phase sequencesd  eH  The order in which phases are used on the SCSI bus follows a prescribed
  sequence.  ,J  The reset condition can abort any phase and is always followed by the BUSH  FREE phase.  Also any other phase can be followed by the BUS FREE phase:  but many such instances are error conditions (see 6.1.1).   H  The additional allowable sequences shall be as shown in Figure 16.  TheC  normal progression is from the BUS FREE phase to ARBITRATION, fromwK  ARBITRATION to SELECTION or RESELECTION, and from SELECTION or RESELECTIONTJ  to one or more of the information transfer phases (COMMAND, DATA, STATUS,K  or MESSAGE).  The final information transfer phase is normally the MESSAGEeI  IN phase where a DISCONNECT, or COMMAND COMPLETE message is transferred,n   followed by the BUS FREE phase.  k  d  y     f     e  n  h  C  i  l  i  t  s  r        t  t  f  e  m  a     i  e  i  a  s     l  05                           Figure 16 - Phase sequenceso  e  h  6.4 SCSI pointers  eH  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.  dH  The SCSI architecture provides for a set of three pointers for each I/OJ  process, called the saved pointers.  The set of three pointers consist ofH  one for the command, one for the data, and one for the status.  When anI  I/O process becomes active, its three saved pointers are copied into the E  initiator's set of three current pointers.  There is only one set of G  current pointers in each initiator.  The current pointers point to the A  next command, data, or status byte to be transferred between the J  initiator's memory and the target.  The saved and current pointers reside  in the initiator.  gD  The saved command pointer always points to the start of the commandJ  descriptor block (see 7.2) for the I/O process.  The saved status pointerH  always points to the start of the status area for the I/O process.  TheI  saved data pointer points to the start of the data area until the target)D  sends a SAVE DATA POINTER message (see 6.6.20) for the I/O process.           a  e  r  S  E  T  a  a9                        Figure 17 - Simplified SCSI systemt  i  iG  In response to the SAVE DATA POINTER message, the initiator stores thehK  value of the current data pointer into the saved data pointer for that I/OoK  process.  The target may restore the current pointers to the saved pointertH  values for the active I/O process by sending a RESTORE POINTERS messageK  (see 6.6.19) to the initiator.  The initiator then copies the set of savedgJ  pointers into the set of current pointers.  Whenever a target disconnectsG  from the bus, only the set of saved pointers are retained.  The set of A  current pointers is restored from the set of saved pointers upon !  reconnection of the I/O process.   SN     NOTE 32 Since the data pointer value may be modified by the target before L     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   CH  The message system allows communication between an initiator and targetH  for the purpose of interface management.  A message may be one, two, orE  multiple bytes in length.  One or more messages may be sent during aiF  single MESSAGE phase, but a message may not be split between multipleH  MESSAGE phases.  The initiator is required to end the MESSAGE OUT phaseI  (by negating ATN) when it sends certain messages identified in table 10.a  sI  One-byte, two-byte, and extended message formats are defined.  The first A  byte of the message determines the format as defined in table 9.t   4                             Table 9 - Message formatP  +=============-===============================================================+P  |    Value    |  Message format                                               |P  |-------------+---------------------------------------------------------------|P  |     00h     |  One-byte message (COMMAND COMPLETE)                          |P  |     01h     |  Extended messages                                            |P  |  02h - 1Fh  |  One-byte messages                                            |P  |  20h - 2Fh  |  Two-byte messages                                            |P  |  30h - 7Fh  |  Reserved                                                     |P  |  80h - FFh  |  One-byte message (IDENTIFY)                                  |P  +=============================================================================+  o   H  One-byte messages consist of a single byte transferred during a MESSAGEJ  phase.  The value of the byte determines which message is to be performed  as defined in table 10.  i4                             Table 10 - Message codesS  +========-=========-===================================-=========-===============+aS  |Code    | Support |Message Name                       |Direction|               | S  |        |---------|                                   |         |   Negate ATN  |SS  |        |Init|Targ|                                   |         |before last ACK|hS  |--------+----+----+-----------------------------------+---------+---------------|2S  |06h     | O  | M  |ABORT                              |      Out|      Yes      |vS  |0Dh     | O  | O  |ABORT TAG see note 1)              |      Out|      Yes      |sS  |0Ch     | O  | M  |BUS DEVICE RESET                   |      Out|      Yes      | S  |0Eh     | O  | O  |CLEAR QUEUE see note 1)            |      Out|      Yes      | S  |00h     | M  | M  |COMMAND COMPLETE                   | In      |      ---      |rS  |04h     | O  | O  |DISCONNECT                         | In      |      ---      |aS  |04h     | O  | O  |DISCONNECT                         |      Out|      Yes      |iS  |80h+    | M  | O  |IDENTIFY                           | In      |      ---      |uS  |80h+    | M  | M  |IDENTIFY                           |      Out|      No       |rS  |23h     | O  | O  |IGNORE WIDE RESIDUE (two bytes)    | In      |      ---      |dS  |0Fh     | O  | O  |INITIATE RECOVERY                  | In      |      ---      |ES  |0Fh     | O  | O  |INITIATE RECOVERY see note 2)      |      Out|      Yes      |nS  |05h     | M  | M  |INITIATOR DETECTED ERROR           |      Out|      Yes      |fS  |0Ah     | O  | O  |LINKED COMMAND COMPLETE            | In      |      ---      |hS  |0Bh     | O  | O  |LINKED COMMAND COMPLETE (WITH FLAG)| In      |      ---      | S  |09h     | M  | M  |MESSAGE PARITY ERROR               |      Out|      Yes      |DS  |07h     | M  | M  |MESSAGE REJECT                     | In   Out|      Yes      |eS  |***     | O  | O  |MODIFY DATA POINTER                | In      |      ---      |rS  |08h     | M  | M  |NO OPERATION                       |      Out|      Yes      |aS  |        |    |    |Queue tag messages (two bytes)     |         |               | S  |21h     | O  | O  |  HEAD OF QUEUE TAG                |      Out|      No       |gS  |22h     | O  | O  |  ORDERED QUEUE TAG                |      Out|      No       |sS  |20h     | O  | O  |  SIMPLE QUEUE TAG                 | In   Out|      No       |gS  |10h     | O  | O  |RELEASE RECOVERY                   |      Out|      Yes      | S  |03h     | O  | O  |RESTORE POINTERS                   | In      |      ---      | S  |02h     | O  | O  |SAVE DATA POINTER                  | In      |      ---      |uS  |***     | O  | O  |SYNCHRONOUS DATA TRANSFER REQUEST  | In   Out|      Yes      |yS  |11h     | O  | O  |TERMINATE I/O PROCESS              |      Out|      Yes      |IS  |***     | O  | O  |WIDE DATA TRANSFER REQUEST         | In   Out|      Yes      |eS  |12h-1Fh |    |    |Reserved                           |         |               | S  |24h-2Fh |    |    |Reserved for two-byte messages     |         |               |eS  |30h-7Fh |    |    |Reserved                           |         |               | S  |--------------------------------------------------------------------------------| S  |Key:      M    = Mandatory support, O = Optional support.                       |hS  |          In   = Target to initiator,  Out = Initiator to target.               |lS  |          Yes  = Initiator shall negate ATN before last ACK of message.         |eS  |          No   = Initiator may or may not negate ATN before last ACK of         | S  |                 message.  (see attention condition, 6.2.1.)                    |oS  |          ---  = Not applicable                                                 | S  |          ***  = Extended message (see tables 11 and 12)                        |aS  |          80h+ = Codes 80h through FFh are used for IDENTIFY messages           | S  |                 (see table 13).                                                | S  |--------------------------------------------------------------------------------|mS  |      NOTES                                                                     |tS  |      1 The ABORT TAG and CLEAR QUEUE messages are required if tagged queuing   | S  |        is implemented.                                                         |gS  |      2 Outbound INITIATE RECOVERY messages are only valid during the           |eS  |        asynchronous event notification protocol.                               | S  +================================================================================+t  l  e  sH  Two-byte messages consist of two consecutive bytes transferred during aH  MESSAGE phase.  The value of the first byte determines which message isH  to be performed as defined in table 10.  The second byte is a parameterD  byte which is used as defined in the message description (see 6.6).  eI  A value of one in the first byte of a message indicates the beginning ofoH  a multiple-byte extended message.  The minimum number of bytes sent forC  an extended message is three.  The extended message format and the D  extended message codes are shown in tables 11 and 12, respectively.  I9                        Table 11 - Extended message formatmR  +=======-========-========-========-========-========-========-========-========+R  |   Bit |   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |R  |Byte   |        |        |        |        |        |        |        |        |R  |=======+=======================================================================|R  | 0     |                           Extended message (01h)                      |R  |-------+-----------------------------------------------------------------------|R  | 1     |                           Extended message length (n)                 |R  |-------+-----------------------------------------------------------------------|R  | 2     |                           Extended message code (y)                   |R  |-------+-----------------------------------------------------------------------|R  | 3     |                                                                       |R  |-------+---                        Extended message arguments               ---|R  | n+1   |                                                                       |R  +===============================================================================+  g   J  The extended message length specifies the length in bytes of the extendedH  message code plus the extended message arguments to follow.  Therefore,H  the total length of the message is equal to the extended message lengthI  plus two.  A value of zero for the extended message length indicates 256p  bytes follow.  vI  The extended message codes are listed in table 12.  The extended message B  arguments are specified within the extended message descriptions.   8                        Table 12 - Extended message codesP  +=============-===============================================================+P  |  Code (y)   |  Description                                                  |P  |-------------+---------------------------------------------------------------|P  |     02h     |  Reserved (see note)                                          |P  |     00h     |  MODIFY DATA POINTER                                          |P  |     01h     |  SYNCHRONOUS DATA TRANSFER REQUEST                            |P  |     03h     |  WIDE DATA TRANSFER REQUEST                                   |P  |  04h - 7Fh  |  Reserved                                                     |P  |  80h - FFh  |  Vendor-specific                                              |P  |-----------------------------------------------------------------------------|P  |   NOTE - Extended message code 02h was used for the EXTENDED IDENTIFY       |P  |   message in SCSI-1.                                                        |P  +=============================================================================+  e   H  The first message sent by the initiator after the SELECTION phase shallJ  be an IDENTIFY, ABORT, or BUS DEVICE RESET message.  If a target receives@  any other message it shall go to BUS FREE phase (see unexpected  disconnect, 6.1.1).  eH  If the first message is an IDENTIFY message, then it may be immediatelyG  followed by other messages, such as the first of a pair of SYNCHRONOUSrI  DATA TRANSFER REQUEST messages.  If tagged queuing is used the queue tagoC  message immediately follows the IDENTIFY message (see 6.6.7).  The H  IDENTIFY message establishes a logical connection between the initiatorI  and the specified logical unit or target routine within the target knownbD  as an I_T_L nexus or I_T_R nexus.  After the RESELECTION phase, theJ  target's first message shall be IDENTIFY.  This allows the I_T_L nexus orJ  I_T_R nexus to be reestablished.  Only one logical unit or target routineG  shall be identified for any connection.  If a target receives a secondaH  IDENTIFY message with a different logical unit number or target routineJ  number during a connection, it shall go to BUS FREE phase (see unexpectedK  disconnect, 6.1.1).  The treatment of other logical unit addressing errors   is described in 7.5.    G  All initiators shall implement the mandatory messages tabulated in the-D  Init column of table 10.  All targets shall implement the mandatory3  messages tabulated in the Targ column of table 10.   eK  Whenever an I_T_L nexus or I_T_R nexus is established by an initiator that G  is allowing disconnection, the initiator shall ensure that the current J  pointers are equal to the saved pointers for that particular logical unitI  or target routine.  An implied restore pointers operation shall occur as|  a result of a reconnection.  a
  6.6 Messages    1  The SCSI messages are defined in this subclause.=  =  6.6.1 ABORT  =H  The ABORT message is sent from the initiator to the target to clear anyF  I/O process for the I_T_x nexus.  The target shall go to the BUS FREEG  phase following successful receipt of this message.  The pending data,.D  status, and I/O processes for any other nexus shall not be cleared.  =J  If only an I_T nexus has been established, the target shall go to the BUSD  FREE phase.  No status or message shall be sent for the current I/O4  process and no other I/O process shall be affected.   	     NOTES I     33 The ABORT message in the case of only an I_T nexus is useful to an N     initiator that cannot get an IDENTIFY message through to the target due toL     parity errors and just needs to end the current connection.  Any pendingL     data, status, or queued I/O processes for the I_T nexus is not affected.Q     34 It is not possible to abort an I_T nexus on a reconnection because of itemS     f) in 6.2.1.   I  It is not an error to issue this message to an I_T_x nexus that does note&  have an active or queued I/O process.   E  Previously established conditions, including MODE SELECT parameters, I  reservations, and extended contingent allegiance shall not be changed by   the ABORT message.    L     NOTE 35 The BUS DEVICE RESET, CLEAR QUEUE, ABORT, and ABORT TAG messagesF     provide a means to clear one or more I/O processes prior to normalO     termination.  The BUS DEVICE RESET message clears all I/O processes for all O     initiators on all logical units and all target routines of the target.  The)J     CLEAR QUEUE message clears all I/O processes for all initiators on theN     specified logical unit or target routine of the target.  The ABORT messageQ     clears all I/O processes for the selecting initiator on the specified logicalTK     unit or target routine of the target.  The ABORT TAG message clears theE     current I/O process only.      6.6.2 ABORT TAG  h@  The ABORT TAG message shall be implemented if tagged queuing isH  implemented and may be implemented if untagged queuing is implemented. J  The target shall go to the BUS FREE phase following successful receipt ofG  this message.  The target shall clear the current I/O process.  If theAG  target has already started execution of the I/O process, the executionMH  shall be halted.  The medium contents may have been modified before theJ  execution was halted.  In either case, any pending status or data for theK  I/O process shall be cleared and no status or ending message shall be sentNJ  to the initiator.  Pending status, data, and commands for other active orD  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.L  EE  Previously established conditions, including MODE SELECT parameters, I  reservations, and extended contingent allegiance shall not be changed by2  the ABORT TAG message.A  IH  On a reconnection, the ABORT TAG message aborts the current I/O processG  if it is fully identified.  If the I/O process is not fully identified K  (i.e. an I_T_L nexus exists, but the target is reconnecting for an I_T_L_Q|K  nexus), then the I/O process is not aborted and the target goes to the BUS   FREE phase.   O     NOTE 36 A nexus is not fully identified on a reconnection if the ATN signalFO     is asserted during or prior to the IDENTIFY message and the target only has0B     tagged I/O processes for that initiator on that logical unit.      6.6.3 BUS DEVICE RESET-  -J  The BUS DEVICE RESET message is sent from an initiator to direct a targetG  to clear all I/O processes on that SCSI device.  This message forces ahJ  hard reset condition to the selected SCSI device.  The target shall go toF  the BUS FREE phase following successful receipt of this message.  TheG  target shall create a unit attention condition for all initiators (seea  7.9).  r  6.6.4 CLEAR QUEUE   B  The CLEAR QUEUE message shall be implemented if tagged queuing isH  implemented and may be implemented if untagged queuing is implemented. J  The target shall go to the BUS FREE phase following successful receipt ofJ  this message.  The target shall perform an action equivalent to receivingI  a series of ABORT messages from each initiator.  All I/O processes, from E  all initiators, in the queue for the specified logical unit shall be-H  cleared from the queue.  All active I/O processes shall be terminated. F  The medium may have been altered by partially executed commands.  AllH  pending status and data for that logical unit or target routine for allI  initiators shall be cleared.  No status or message shall be sent for any I  of the I/O processes.  A unit attention condition shall be generated formH  all other initiators with I/O processes that either were active or wereI  queued for that logical unit or target routine.  When reporting the unit=G  attention condition the additional sense code shall be set to COMMANDS   CLEARED BY ANOTHER INITIATOR.  oE  Previously established conditions, including MODE SELECT parameters,eI  reservations, and extended contingent allegiance shall not be changed by   the CLEAR QUEUE message.t  s  6.6.5 COMMAND COMPLETE   uF  The COMMAND COMPLETE message is sent from a target to an initiator toK  indicate that the execution of an I/O process has completed and that valideH  status has been sent to the initiator.  After successfully sending thisH  message, the target shall go to the BUS FREE phase by releasing the BSYB  signal.  The target shall consider the message transmission to beH  successful when it detects the negation of ACK for the COMMAND COMPLETE%  message with the ATN signal false.  =  =P     NOTE 37 The I/O process may have completed successfully or unsuccessfully as     indicated in the status.     6.6.6 DISCONNECT    I  The DISCONNECT message is sent from a target to inform an initiator that=B  the present connection is going to be broken (the target plans toI  disconnect by releasing the BSY signal), but that a later reconnect will-H  be required in order to complete the current I/O process.  This message?  shall not cause the initiator to save the data pointer.  After G  successfully sending this message, the target shall go to the BUS FREE-J  phase by releasing the BSY signal.  The target shall consider the messageF  transmission to be successful when it detects the negation of the ACK=  signal for the DISCONNECT message with the ATN signal false.    K  Targets that break data transfers into multiple connections shall end each J  successful connection (except possibly the last) with a SAVE DATA POINTER  - DISCONNECT message sequence.    H  This message may also be sent from an initiator to a target to instructJ  the target to disconnect from the SCSI bus.  If this option is supported,I  and after the DISCONNECT message is received, the target shall switch totI  MESSAGE IN phase, send the DISCONNECT message to the initiator (possiblytI  preceded by SAVE DATA POINTER message), and then disconnect by releasingzJ  BSY.  After releasing the BSY signal, the target shall not participate inI  another ARBITRATION phase for at least a disconnection delay or the timegJ  limit specified in the disconnect time limit mode parameter (see 8.3.3.2)E  whichever is greater.  If this option is not supported or the target=K  cannot disconnect at the time when it receives the DISCONNECT message from D  the initiator, the target shall respond by sending a MESSAGE REJECT  message to the initiator.  -  6.6.7 IDENTIFY-  -K  The IDENTIFY message (see table 13) is sent by either the initiator or the 6  target to establish an I_T_L nexus or an I_T_R nexus.  NJ     NOTE 38 Use of the IDENTIFY message to establish an I_T_R nexus allowsQ     connection to one of up to eight target routines or functions in the target. RP     These target routines are expected to be used for maintenance and diagnostic
     purposes.    9                        Table 13 - IDENTIFY message formateP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |=====+========+========+========+========+========+==========================|P  |     |Identify|DiscPriv| LUNTAR |Reserved|Reserved|          LUNTRN          |P  +=============================================================================+     tI  The identify bit shall be set to one to specify that this is an IDENTIFYS	  message.E  eJ  A disconnect privilege (DiscPriv) bit of one specifies that the initiatorJ  has granted the target the privilege of disconnecting.  A DiscPriv bit ofF  zero specifies that the target shall not disconnect.  This bit is notG  defined and shall be set to zero when an IDENTIFY message is sent by aa  target.  eJ  A logical unit target (LUNTAR) bit of zero specifies that the I/O processK  is directed to or from a logical unit.  A LUNTAR bit of one specifies thatn;  the I/O process is directed to or from a target routine.  r   I  The logical unit number target routine number (LUNTRN) field specifies a K  logical unit number if the LUNTAR bit is zero.  The LUNTRN field specifiesaF  a target routine number if the LUNTAR bit is one.  The response to anK  invalid value in the LUNTRN field is described in 7.5.3.  Only the INQUIRYtG  and REQUEST SENSE commands are valid for target routines.  If a target G  receives any other command for a target routine, it shall return CHECK A  CONDITION status and shall set the sense key to ILLEGAL REQUEST.o  rI  An IDENTIFY message is invalid if a reserved bit is set to one or if therB  LUNTAR bit is set to one and the target does not implement targetB  routines.  A device may respond to an invalid IDENTIFY message byC  immediately sending a MESSAGE REJECT message or by returning CHECKLJ  CONDITION status.  If a CHECK CONDITION status is returned, the sense keyK  shall be set to ILLEGAL REQUEST and the additional sense code shall be set +  to INVALID BITS IN IDENTIFY MESSAGE FIELD.i   J  Only one logical unit number or target routine number shall be identifiedG  per I/O process.  The initiator may send one or more IDENTIFY messagessJ  during a connection.  A second IDENTIFY message with a different value inG  either the LUNTAR bit or LUNTRN field shall not be issued before a BUSrI  FREE phase has occurred;  if a target receives a second IDENTIFY messagecJ  with a different value in either of these fields, it shall go to BUS FREEH  phase (see unexpected disconnect, 6.1.1).  Thus an initiator may changeI  the DiscPriv bit, but may not attempt to switch to another I/O process. uC  (See the DTDC field of the disconnect-reconnect page (8.3.3.2) for )  additional controls over disconnection.)E   H  An implied RESTORE POINTERS message shall be performed by the initiatorJ  prior to the assertion of the ACK signal on the next phase for an inbound+  IDENTIFY message sent during reconnection.    I  An implied RESTORE POINTERS message shall be performed by the initiator  H  following  successful identification of the nexus during the MESSAGE INH  phase of a reconnection and before the  negation  of  the  ACK  signal A  for  the  next transfer following the successful identification.e  hH  Identification is considered successful during an initial connection orC  an initiator reconnect when the target detects no error during theoJ  transfer of the IDENTIFY message and an optional queue tag message in theK  MESSAGE OUT phase immediately following the SELECTION phase.   See 6.5 for G  the ordering of the  IDENTIFY and queue tag messages.  See 6.1.9.2 fore?  handling target detected errors during the MESSAGE OUT phase.     K  Identification is considered successful during a target reconnect when theeF  ATN signal is not asserted during the transfer of either the IDENTIFYD  message or the SIMPLE QUEUE TAG message for an I_T_L_Q nexus in theJ  MESSAGE IN phase immediately following the RESELECTION phase.  See clauseI  6.5 for the ordering of the IDENTIFY and queue tag messages.  See 6.2.1,TJ  item d), for handling target detected errors during the MESSAGE IN phase.  O  6.6.8 IGNORE WIDE RESIDUE  a>                  Table 14 - IGNORE WIDE RESIDUE message formatQ  +======-========-========-========-========-========-========-========-========+ Q  |   Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |eQ  |Byte  |        |        |        |        |        |        |        |        |IQ  |======+=======================================================================|dQ  | 0    |                           Message code (23h)                          |aQ  |------+-----------------------------------------------------------------------|nQ  | 1    |                           Ignore (01h, 02h, 03h)                      |eQ  +==============================================================================+       K  The IGNORE WIDE RESIDUE message (see table 14) shall be sent from a targetnH  to indicate that the number of valid bytes sent during the last REQ/ACKF  handshake and REQB/ACKB handshake of a DATA IN phase is less than theE  negotiated transfer width.  The ignore field indicates the number of H  invalid data bytes transferred.  This message shall be sent immediatelyJ  following that DATA IN phase and prior to any other messages.  The ignore  field is defined in table 15.  aM     NOTE 39 More than one IGNORE WIDE RESIDUE message may occur during an I/Os     process.  f9                        Table 15 - Ignore field definitionu8  +=============-=======================================+8  |   Ignore    |           Invalid data bits           |8  |             |---------------------------------------|8  |             |  32-bit transfers | 16-bit transfers  |8  |-------------+-------------------+-------------------|8  |     00h     |      Reserved     |    Reserved       |8  |     01h     |      DB(31-24)    |    DB(15-8)       |8  |     02h     |      DB(31-16)    |    Reserved       |8  |     03h     |      DB(31-8)     |    Reserved       |8  |  04h - FFh  |      Reserved     |    Reserved       |8  +=====================================================+     pJ  Even though a byte is invalid its corresponding parity bit shall be validG  for the value transferred.  For 16-bit transfers, DB(31-16) are alwaysi<  invalid and the corresponding parity bits are also invalid.  i  6.6.9 INITIATE RECOVERY  aG  A target that supports extended contingent allegiance shall inform thehH  initiator it is entering this condition by sending an INITIATE RECOVERYF  message immediately following a CHECK CONDITION or COMMAND TERMINATEDH  status.  The extended contingent allegiance condition remains in effect&  until terminated as described in 7.7.  rB  If an asynchronous event occurs, the target may enter an extendedF  contingent allegiance condition by becoming a temporary initiator andI  sending the INITIATE RECOVERY message following the IDENTIFY message and G  any queue tag message and before the COMMAND phase of the SEND commandpJ  that is used to perform the asynchronous event notification (see 7.5.5). E  The successful transmission of this message establishes the extendedsI  contingent allegiance condition which remains in effect until terminatedn  as described in 7.7.c  hQ     NOTE 40 If the target notifies multiple initiators of the asynchronous event,uF     it should include the INITIATE RECOVERY message in only one of the     notifications.  eI  A MESSAGE REJECT response to an INITIATE RECOVERY message indicates thatnK  an extended contingent allegiance condition shall not be established.  TheaD  enabled or disabled state of an extended contingent allegiance (seeJ  8.3.3.1) is not changed by the rejection of an INITIATE RECOVERY message.      6.6.10 INITIATOR DETECTED ERROR  EI  The INITIATOR DETECTED ERROR message is sent from an initiator to inform K  a target that an error has occurred that does not preclude the target fromaJ  retrying the operation.  The source of the error may either be related toH  previous activities on the SCSI bus or may be internal to the initiatorK  and unrelated to any previous SCSI bus activity.  Although present pointertE  integrity is not assured, a RESTORE POINTERS message or a disconnect J  followed by a reconnect, shall cause the pointers to be restored to their  defined prior state.e  u  6.6.11 LINKED COMMAND COMPLETEg  sJ  The LINKED COMMAND COMPLETE message is sent from a target to an initiatorJ  to indicate that the execution of a linked command has completed and thatH  status has been sent.  The initiator shall then set the pointers to the+  initial state for the next linked command.s  s+  6.6.12 LINKED COMMAND COMPLETE (WITH FLAG)s  eI  The LINKED COMMAND COMPLETE (WITH FLAG) message is sent from a target toSJ  an initiator to indicate that the execution of a linked command (with theG  flag bit set to one) has completed and that status has been sent.  The.G  initiator shall then set the pointers to the initial state of the nextiB  linked command.  Typically this message would be used to cause an8  interrupt in the initiator between two linked commands.  A  6.6.13 MESSAGE PARITY ERROR  cJ  The MESSAGE PARITY ERROR message is sent from the initiator to the targetE  to indicate that it received a message byte with a parity error (seee
  6.1.9.2).  tK  In order to indicate its intentions of sending this message, the initiator.K  shall assert the ATN signal prior to its release of the ACK signal for the=G  REQ/ACK handshake of the message byte that has the parity error.  ThisfJ  provides an interlock so that the target can determine which message byteK  has the parity error.  If the target receives this message under any othersJ  circumstance, it shall signal a catastrophic error condition by releasingE  the BSY signal without any further information transfer attempt (seee  6.1.1).  bJ  If after receiving the MESSAGE PARITY ERROR message the target returns toF  the MESSAGE IN phase before switching to some other phase, the target;  shall resend the entire message that had the parity error.      6.6.14 MESSAGE REJECT  eJ  The MESSAGE REJECT message is sent from either the initiator or target to?  indicate that the last message or message byte it received was +  inappropriate or has not been implemented.    K  In order to indicate its intentions of sending this message, the initiator=K  shall assert the ATN signal prior to its release of the ACK signal for the F  REQ/ACK handshake of the message byte that is to be rejected.  If theK  target receives this message under any other circumstance, it shall rejecty  this message.    TJ  When a target sends this message, it shall change to MESSAGE IN phase andH  send this message prior to requesting additional message bytes from theK  initiator.  This provides an interlock so that the initiator can determine    which message byte is rejected.  bG  After a target sends a MESSAGE REJECT message and if the ATN signal isgD  still asserted, then it shall return to the MESSAGE OUT phase.  TheK  subsequent MESSAGE OUT phase shall begin with the first byte of a message.   e#  6.6.15 MODIFY DATA POINTER Message   g7                          Table 16 - MODIFY DATA POINTERnQ  +======-========-========-========-========-========-========-========-========+oQ  |   Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | Q  |Byte  |        |        |        |        |        |        |        |        | Q  |======+=======================================================================|eQ  | 0    |                           Extended message (01h)                      |IQ  |------+-----------------------------------------------------------------------|aQ  | 1    |                           Extended message length (05h)               | Q  |------+-----------------------------------------------------------------------|vQ  | 2    |                           MODIFY DATA POINTER (00h)                   |nQ  |------+-----------------------------------------------------------------------|kQ  | 3    | (MSB)                                                                 |tQ  |------+---                        Argument                                 ---|rQ  | 6    |                                                                 (LSB) |nQ  +==============================================================================+   i  rJ  The MODIFY DATA POINTER message (see table 16) is sent from the target toD  the initiator and requests that the signed argument be added (two's6  complement) to the value of the current data pointer.  e  6.6.16 NO OPERATION  UD  The NO OPERATION message is sent from an initiator in response to aJ  target's request for a message when the initiator does not currently have!  any other valid message to send.    G  For example, if the target does not respond to the attention conditionnG  until a later phase and at that time the original message is no longeryF  valid the initiator may send the NO OPERATION message when the target  enters the MESSAGE OUT phase.  g  6.6.17 Queue tag messages   9                       Table 17 - Queue tag message formatyQ  +======-========-========-========-========-========-========-========-========+SQ  |   Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |fQ  |Byte  |        |        |        |        |        |        |        |        |oQ  |======+=======================================================================| Q  | 0    |                           Message code (20h, 21h, 22h)                | Q  |------+-----------------------------------------------------------------------|SQ  | 1    |                           Queue tag (00h - FFh)                       |eQ  +==============================================================================+.      G  Table 17 defines the format for the queue tag messages.  If the targethI  implements tagged queuing, all of the queue tag messages are mandatory:  D  HEAD OF QUEUE TAG, ORDERED QUEUE TAG, and SIMPLE QUEUE TAG.  TaggedD  queuing is only defined for logical units, not for target routines.  eI  If a target does not implement tagged queuing and a queue tag message isTH  received or if a queue tag message is received for a target routine, itJ  shall respond with a MESSAGE REJECT message and accept the I/O process as  if it were untagged.m   I  The queue tag messages are used to specify an identifier, called a queue=H  tag, for the I/O process that establishes the I_T_L_Q nexus.  The queueH  tag field is an 8-bit unsigned integer assigned by the initiator duringK  an initial connection.  The queue tag for every I/O process for each I_T_L=D  nexus should be unique.  If the target receives a queue tag that isJ  currently in use for the I_T_L nexus, then it shall respond as defined inD  7.5.2.  A queue tag becomes available for reassignment when the I/OK  process ends.  The numeric value of a queue tag has no effect on the order=  of execution.  =N     NOTE 41 For each logical unit on each target, each initiator has up to 256L     queue tags to assign to I/O processes.  Thus a target with eight logicalL     units could have up to 14 336 I/O processes concurrently in existence if+     there were seven initiators on the bus.n  eF  Whenever an initiator connects to a target, the appropriate queue tagE  message shall be sent immediately following the IDENTIFY message andeI  within the same MESSAGE OUT phase to establish the I_T_L_Q nexus for theoA  I/O process.  Only one I_T_L_Q nexus may be established during aGJ  connection.  If a queue tag message is not sent, then only an I_T_x nexus7  is established for the I/O process (untagged command).=  =F  Whenever a target reconnects to an initiator to continue a tagged I/OJ  process, the SIMPLE QUEUE TAG message shall be sent immediately followingH  the IDENTIFY message and within the same MESSAGE IN phase to revive theJ  I_T_L_Q nexus for the I/O process.  Only one I_T_L_Q nexus may be revivedJ  during a reconnection.  If the SIMPLE QUEUE TAG message is not sent, thenG  only an I_T_x nexus is revived for the I/O process (untagged command).    G  If a target attempts to reconnect using an invalid queue tag, then theF4  initiator should respond with an ABORT TAG message.  =  6.6.17.1 HEAD OF QUEUE TAG=  =G  The HEAD OF QUEUE TAG message specifies that the I/O process be placedtJ  first in that logical unit's command queue.  An I/O process already beingI  executed by the target shall not be preempted.  A subsequent I/O processaI  received with a HEAD OF QUEUE TAG message shall be placed at the head ofn>  the command queue for execution in last-in, first-out order.   s  6.6.17.2 ORDERED QUEUE TAGI   J  The ORDERED QUEUE TAG message specifies that the I/O process be placed inH  that logical unit's command queue for execution in the order received. I  All queued I/O processes for the logical unit received prior to this I/O E  process shall be executed before this I/O process is executed.   AlliG  queued I/O processes received after this I/O process shall be executedmI  after this I/O process, except for I/O processes received with a HEAD OFr  QUEUE TAG message.f  e  6.6.17.3 SIMPLE QUEUE TAG  oI  The SIMPLE QUEUE TAG message specifies that the I/O process be placed in H  that logical unit's command queue.  The order of execution is described  in 7.8.  n  6.6.18 RELEASE RECOVERY  lF  The RELEASE RECOVERY message is sent from an initiator to a target toA  terminate an extended contingent allegiance condition previously I  established by an INITIATE RECOVERY message.  This message shall be sent.K  immediately following the IDENTIFY message in the same MESSAGE OUT phase. aJ  The extended contingent allegiance condition ends upon successful receiptF  of the RELEASE RECOVERY message.  The target shall go to the BUS FREE4  phase following successful receipt of this message.  AF  If a RELEASE RECOVERY message is received by a target that implementsF  extended contingent allegiance when an extended contingent allegianceK  condition does not exist, the message shall not be rejected and the targett   shall go to the BUS FREE phase.  h  6.6.19 RESTORE POINTERS   K  The RESTORE POINTERS message is sent from a target to direct the initiator K  to copy the most recently saved command, data, and status pointers for the K  I/O process to the corresponding current pointers.  The command and statusoG  pointers shall be restored to the beginning of the present command andfF  status areas.  The data pointer shall be restored to the value at theI  beginning of the data area in the absence of a SAVE DATA POINTER messageaI  or to the value at the point at which the last SAVE DATA POINTER messagea  occurred for that nexus.   l  6.6.20 SAVE DATA POINTERt   B  The SAVE DATA POINTER message is sent from a target to direct theI  initiator to copy the current data pointer to the saved data pointer forsB  the current I/O process.  (See 6.4 for a definition of pointers.)  u1  6.6.21 SYNCHRONOUS DATA TRANSFER REQUEST messageo  e>                   Table 18 - SYNCHRONOUS DATA TRANSFER REQUESTQ  +======-========-========-========-========-========-========-========-========+yQ  |   Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | Q  |Byte  |        |        |        |        |        |        |        |        |OQ  |======+=======================================================================| Q  | 0    |                           Extended message (01h)                      |nQ  |------+-----------------------------------------------------------------------|rQ  | 1    |                           Extended message length (03h)               |tQ  |------+-----------------------------------------------------------------------|eQ  | 2    |                           SYNCHRONOUS DATA TRANSFER REQUEST code (01h)|gQ  |------+-----------------------------------------------------------------------|yQ  | 3    |                           Transfer period factor                      | Q  |------+-----------------------------------------------------------------------|nQ  | 4    |                           REQ/ACK offset                              |lQ  +==============================================================================+    K  A SYNCHRONOUS DATA TRANSFER REQUEST (SDTR) message (see table 18) exchangeiI  shall be initiated by an SCSI device whenever a previously-arranged dataaK  transfer agreement may have become invalid.  The agreement becomes invalid F  after any condition which may leave the data transfer agreement in an  indeterminate state such as:a(     a)     after a hard reset condition;0     b)     after a BUS DEVICE RESET message and;     c)     after a power cycle.t   K  In addition, an SCSI device may initiate an SDTR message exchange wheneveriE  it is appropriate to negotiate a new data transfer agreement (eitherp@  synchronous or asynchronous).  SCSI devices that are capable ofG  synchronous data transfers shall not respond to an SDTR message with am  MESSAGE REJECT message.   	     NOTESrO     42 Renegotiation at every selection is not recommended, since a significante#     performance impact is likely.  pP     43 Due to historical problems with early host adapters that could not acceptP     an SDTR message, some targets may not initiate synchronous negotiation afterK     a power cycle as required by this standard.  Host adapters that support=K     synchronous mode may avoid the ensuing failure modes when the target is N     independently power cycled by initiating a synchronous negotiation on each&     REQUEST SENSE and INQUIRY command.   K  The SDTR message exchange establishes the permissible transfer periods and=I  the REQ/ACK offsets for all logical units and target routines on the two 6  devices.  This agreement only applies to data phases.  -L  The transfer period factor times four is the value of the transfer period. I  The transfer period is the minimum time allowed between leading edges of-F  successive REQ pulses and of successive ACK pulses to meet the device1  requirements for successful reception of data.      E  The REQ/ACK offset is the maximum number of REQ pulses allowed to be-F  outstanding before the leading edge of its corresponding ACK pulse isB  received at the target.  This value is chosen to prevent overflowK  conditions in the device's reception buffer and offset counter.  A REQ/ACK G  offset value of zero shall indicate asynchronous data transfer mode; a=6  value of FFh shall indicate unlimited REQ/ACK offset.  =G  The originating device (the device that sends the first of the pair ofmI  SDTR messages) sets its values according to the rules above to permit iteI  to receive data successfully.  If the responding device can also receive1K  data successfully with these values (or smaller transfer periods or largersK  REQ/ACK offsets or both), it returns the same values in its SDTR message. nK  If it requires a larger transfer period, a smaller REQ/ACK offset, or both I  in order to receive data successfully, it substitutes values in its SDTRhF  message as required, returning unchanged any value not required to beJ  changed.  Each device when transmitting data shall respect the limits setG  by the other's SDTR message, but it is permitted to transfer data witheI  larger transfer periods, smaller REQ/ACK offsets, or both than specified-J  in the other's SDTR message.  The successful completion of an exchange of/  SDTR messages implies an agreement as follows:    L  Responding device SDTR response                           Implied agreementY  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 lessa]                                                         than the values received in the other=N                                                         device's SDTR message.  mS  b) REQ/ACK offset equal to zero                              Asynchronous transferr  aI  c) MESSAGE REJECT message                          Asynchronous transfera  dI  If the initiator recognizes that negotiation is required, it asserts the G  ATN signal and sends a SDTR message to begin the negotiating process. TF  After successfully completing the MESSAGE OUT phase, the target shallI  respond with the proper SDTR message.  If an abnormal condition prevents I  the target from returning an appropriate response, both devices shall go F  to asynchronous data transfer mode for data transfers between the two	  devices.L  nK  Following target response (1) above, the implied agreement for synchronoustJ  operation shall be considered to be negated by both the initiator and theI  target if the initiator asserts the ATN signal and the first message outgE  is either MESSAGE PARITY ERROR or MESSAGE REJECT. In this case, bothaG  devices shall go to asynchronous data transfer mode for data transfersnI  between the two devices.  For the MESSAGE PARITY ERROR case, the implied K  agreement shall be reinstated if a retransmittal of the second of the pairgJ  of messages is successfully accomplished.  After a vendor-specific numberH  of retry attempts (greater than zero), if the target receives a MESSAGEJ  PARITY ERROR message, it shall terminate the retry activity.  This may beD  done either by changing to any other information transfer phase andJ  transferring at least one byte of information or by going to the BUS FREEK  phase (see 6.1.1).  The initiator shall accept such action as aborting the J  negotiation, and both devices shall go to asynchronous data transfer mode.  for data transfers between the two devices.     H  If the target recognizes that negotiation is required, it sends an SDTRI  message to the initiator.  Prior to releasing the ACK signal on the lastaI  byte of the SDTR message from the target, the initiator shall assert thefF  ATN signal and respond with its SDTR message or with a MESSAGE REJECTI  message.  If an abnormal condition prevents the initiator from returning D  an appropriate response, both devices shall go to asynchronous data:  transfer mode for data transfers between the two devices.  rK  Following an initiator's responding SDTR message, an implied agreement fornH  synchronous operation shall not be considered to exist until the targetJ  leaves the MESSAGE OUT phase, indicating that the target has accepted theH  negotiation.  After a vendor-specific number of retry attempts (greaterK  than zero), if the target has not received the initiator's responding SDTRoK  message, it shall go to the BUS FREE phase without any further informationGH  transfer attempt (see 6.1.1).  This indicates that a catastrophic errorD  condition has occurred.  Both devices shall go to asynchronous data:  transfer mode for data transfers between the two devices.  eH  If, following an initiator's responding SDTR message, the target shiftsD  to MESSAGE IN phase and the first message in is MESSAGE REJECT, theK  implied agreement shall be considered to be negated and both devices shalltI  go to asynchronous data transfer mode for data transfers between the twoe	  devices.a  rE  The implied synchronous agreement shall remain in effect until a BUSQJ  DEVICE RESET message is received, until a hard reset condition occurs, orG  until one of the two SCSI devices elects to modify the agreement.  ThetD  default data transfer mode is asynchronous data transfer mode.  TheF  default data transfer mode is entered at power on, after a BUS DEVICE0  RESET message, or after a hard reset condition.  c  6.6.22 TERMINATE I/O PROCESSp  iK  The TERMINATE I/O PROCESS message is sent from the initiator to the targetsD  to terminate the current I/O process without corrupting the medium.   J  With the following exceptions, the target shall terminate the current I/OJ  process and return COMMAND TERMINATED status.  The sense key shall be setE  to NO SENSE.  The additional sense code and qualifier are set to I/OE  PROCESS TERMINATED.   J  If the associated I/O process involves a data phase, the target shall setH  the valid bit in the sense data to one and set the information field as	  follows: L     a)     If the command descriptor block specifies an allocation length orK            parameter list length, the information field shall be set to the H            difference (residue) between the number of bytes successfully0            transferred and the requested length.M     b)     If the command descriptor block specifies a transfer length field,tM            the information field shall be set as defined in the REQUEST SENSEl             command (see 8.2.14).  gH  If an error is detected for the associated I/O process the target shall*  ignore the TERMINATE I/O PROCESS message.  AC  If the operation requested for the associated I/O process has beenEH  completed but status has not been returned, the target shall ignore the  TERMINATE I/O PROCESS message.t  cE  If the target does not support this message or is unable to stop theoC  current I/O process, it shall send a MESSAGE REJECT message to theU;  initiator and continue the I/O process in a normal manner.   -K  The effect of a TERMINATE I/O PROCESS message on the command queue depends=K  on the queue error recovery option specified in the control mode page (see|D  8.3.3.1) and on whether or not a contingent allegiance condition is  generated.|   P     NOTE 44 The TERMINATE I/O PROCESS message provides a means for the initiatorN     to request the target to reduce the transfer length of the current commandO     to the amount that has already been transferred.  The initiator can use the-O     sense data to determine the actual number of bytes or blocks that have been J     transferred.  This message is normally used by the initiator to stop aN     lengthy read, write, or verify operation when a higher-priority command isH     available to be executed.  It is up to the initiator to complete the4     terminated command at a later time, if required.  -*  6.6.23 WIDE DATA TRANSFER REQUEST message   :                      Table 19 - WIDE DATA TRANSFER MESSAGEQ  +======-========-========-========-========-========-========-========-========+ Q  |   Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |=Q  |Byte  |        |        |        |        |        |        |        |        |AQ  |======+=======================================================================|bQ  | 0    |                           Extended message (01h)                      |mQ  |------+-----------------------------------------------------------------------|wQ  | 1    |                           Extended message length (02h)               | Q  |------+-----------------------------------------------------------------------| Q  | 2    |                           WIDE DATA TRANSFER REQUEST code (03h)       |tQ  |------+-----------------------------------------------------------------------|aQ  | 3    |                           Transfer width exponent                     |aQ  +==============================================================================+M  A  RJ  A WIDE DATA TRANSFER REQUEST (WDTR) message (see table 19) exchange shallG  be initiated by an SCSI device whenever a previously-arranged transferpH  width agreement may have become invalid.  The agreement becomes invalidF  after any condition which may leave the data transfer agreement in an  indeterminate state such as: (     a)     after a hard reset condition;0     b)     after a BUS DEVICE RESET message and;     c)     after a power cycle.e  hJ  In addition, an SCSI device may initiate a WDTR message exchange wheneverE  it is appropriate to negotiate a new transfer width agreement.  SCSI J  devices that are capable of wide data transfers (greater than eight bits)C  shall not respond to a WDTR message with a MESSAGE REJECT message.d  cH     NOTE 45 Renegotiation at every selection is not recommended, since a.     significant performance impact is likely.   iD  The WDTR message exchange establishes an agreement between two SCSIJ  devices on the width of the data path to be used for DATA phase transfersI  between the two devices.  This agreement applies to DATA IN and DATA OUTKK  phases only.  All other information transfer phases shall use an eight-bitr  data path.   e@  If an SCSI device implements both wide data transfer option andH  synchronous data transfer option, then it shall negotiate the wide dataF  transfer agreement prior to negotiating the synchronous data transferH  agreement.  If a synchronous data transfer agreement is in effect, thenG  an SCSI device that accepts a WDTR message shall reset the synchronousn   agreement to asynchronous mode.  eJ  The transfer width is two to the transfer width exponent bytes wide.  TheH  transfer width that is established applies to all logical units on bothC  SCSI devices.  Valid transfer widths are 8 bits (m = 00h), 16 bitssD  (m = 01h), and 32 bits (m = 02h).  Values of m greater than 02h are
  reserved.  tI  The originating SCSI device (the SCSI device that sends the first of the I  pair of WDTR messages) sets its transfer width value to the maximum datasH  path width it elects to accommodate.  If the responding SCSI device canG  also accommodate this transfer width, it returns the same value in its K  WDTR message.  If it requires a smaller transfer width, it substitutes the D  smaller value in its WDTR message.  The successful completion of an;  exchange of WDTR messages implies an agreement as follows:e  aL  Responding device WDTR response                           Implied agreementb  a) Non-zero transfer width                                Each device transmits and receives data]                                                            with a transfer width equal to the \                                                            responding SCSI device's transferA                                                            width.    Y  b) Transfer width equal to zero                                  Eight-bit data transfer    K  c) MESSAGE REJECT message                          Eight-bit data transfer/   I  If the initiator recognizes that negotiation is required, it asserts theaG  ATN signal and sends a WDTR message to begin the negotiating process. eF  After successfully completing the MESSAGE OUT phase, the target shallI  respond with the proper WDTR message.  If an abnormal condition preventsrI  the target from returning an appropriate response, both devices shall gosC  to eight-bit data transfer mode for data transfers between the twon	  devices.   eH  Following target response 1) above, the implied agreement for wide dataJ  transfers shall be considered to be negated by both the initiator and theH  target if the initiator asserts ATN and the first message out is eitherJ  MESSAGE PARITY ERROR or MESSAGE REJECT.  In this case, both devices shallF  go to eight-bit data transfer mode for data transfers between the twoI  devices.  For the MESSAGE PARITY ERROR case, the implied agreement shallsJ  be reinstated if a retransmittal of the second of the pair of messages isD  successfully accomplished.  After a vendor-specific number of retryF  attempts (greater than zero), if the target receives a MESSAGE PARITYH  ERROR message, it shall terminate the retry activity.  This may be done?  either by changing to any other information transfer phase and J  transferring at least one byte of information or by going to the BUS FREEK  phase (see 6.1.1).  The initiator shall accept such action as aborting themK  negotiation, and both devices shall go to eight-bit data transfer mode fory)  data transfers between the two devices.    eG  If the target recognizes that negotiation is required, it sends a WDTRoI  message to the initiator.  Prior to releasing the ACK signal on the last I  byte of the WDTR message from the target, the initiator shall assert theiF  ATN signal and respond with its WDTR message or with a MESSAGE REJECTI  message.  If an abnormal condition prevents the initiator from returning,J  an appropriate response, both devices shall go to eight-bit data transfer1  mode for data transfers between the two devices.r   K  Following an initiator's responding WDTR message, an implied agreement foroH  wide data transfer operation shall not be considered to exist until theD  target leaves the MESSAGE OUT phase, indicating that the target hasC  accepted the negotiation.  After a vendor-specific number of retrynA  attempts (greater than zero), if the target has not received the G  initiator's responding WDTR message, it shall go to the BUS FREE phaseaD  without any further information transfer attempt (see 6.1.1).  ThisJ  indicates that a catastrophic error condition has occurred.  Both devicesH  shall go to eight-bit data transfer mode for data transfers between the
  two devices.1   H  If, following an initiator's responding WDTR message, the target shiftsD  to MESSAGE IN phase and the first message in is MESSAGE REJECT, theK  implied agreement shall be considered to be negated and both devices shall F  go to eight-bit data transfer mode for data transfers between the two	  devices.E  JH  The implied transfer width agreement shall remain in effect until a BUSJ  DEVICE RESET message is received, until a hard reset condition occurs, orG  until one of the two SCSI devices elects to modify the agreement.  ThemJ  default data transfer width is eight-bit data transfer mode.  The defaultD  data transfer mode is entered at power on, after a BUS DEVICE RESET*  message, or after a hard reset condition.  r  f  7 SCSI commands and statust  sE  This clause defines the SCSI command and status structures and givese  several examples.  mH  By keeping to a minimum the functions essential to communicate via thisG  protocol, a wide range of peripheral devices of varying capability cantK  operate in the same environment.  Because subsets of the full architectureu2  may be implemented, optional functions are noted.  l(  7.1 Command implementation requirements  rG  The first byte of all SCSI commands shall contain an operation code asTE  defined in this International Standard.  Targets shall implement allAJ  commands with a mandatory operation code (see 7.1.2) both in clause 8 and1  in the appropriate clause for their device type.n  e  7.1.1 Reserved   lG  Reserved bits, fields, bytes, and code values are set aside for future J  standardization.  Their use and interpretation may be specified by futureJ  extensions to this standard.  A reserved bit, field, or byte shall be setG  to zero, or in accordance with a future extension to this standard.  A H  target that receives a reserved bit, field, or byte that is not zero orF  receives a reserved code value shall terminate the command with CHECKH  CONDITION status and the sense key shall be set to ILLEGAL REQUEST.  ItJ  shall also be acceptable for a target to interpret a bit, field, byte, orG  code value in accordance with a future extension to this Internationalp
  Standard.  E  7.1.2 Operation code typeso  e2  The operation code types are defined in table 20.  O7                          Table 20 - Operation code typehP  +=============-===============================================================+P  |  Operation  |  Description                                                  |P  |  code type  |                                                               |P  |-------------+---------------------------------------------------------------|P  |      M      |  Mandatory - Commands so designated shall be implemented in   |P  |             |  order to meet the minimum requirement of this International  |P  |             |  Standard.                                                    |P  |             |                                                               |P  |      O      |  Optional - Commands so designated, if implemented, shall be  |P  |             |  implemented as defined in this International Standard.       |P  |             |                                                               |P  |      V      |  Vendor-specific - Operation codes so designated are available|P  |             |  for vendor defined commands.  See the vendor specifications  |P  |             |  where compatibility is desired.                              |P  |             |                                                               |P  |      R      |  Reserved - Operation codes so designated shall not be used.  |P  |             |  They are reserved for future extensions to this              |P  |             |  International Standard.                                      |P  +=============================================================================+  |  -  7.2 Command descriptor block-  -G  A command is communicated by sending a command descriptor block to the K  target.  For several commands, the command descriptor block is accompanied-J  by a list of parameters sent during the DATA OUT phase.  See the specific#  commands for detailed information.R  EG  The command descriptor block always has an operation code as its first-*  byte and a control byte as its last byte.   B  For all commands, if there is an invalid parameter in the commandF  descriptor block, then the target shall terminate the command without  altering the medium.A  DH        Table 21 - Typical command descriptor block for six-byte commandsQ  +======-========-========-========-========-========-========-========-========+eQ  |   Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |iQ  |Byte  |        |        |        |        |        |        |        |        | Q  |======+=======================================================================|nQ  | 0    |                           Operation code                              | Q  |------+-----------------------------------------------------------------------|dQ  | 1    |   Logical unit number    | (MSB)                                      |nQ  |------+------------------------------                                      ---| Q  | 2    |                           Logical block address (if required)         |iQ  |------+---                                                                 ---|sQ  | 3    |                                                                 (LSB) |oQ  |------+-----------------------------------------------------------------------|NQ  |      |                           Transfer length (if required)               |iQ  | 4    |                           Parameter list length (if required)         |pQ  |      |                           Allocation length (if required)             | Q  |------+-----------------------------------------------------------------------| Q  | 5    |                           Control                                     |aQ  +==============================================================================+.  eH        Table 22 - Typical command descriptor block for ten-byte commandsQ  +======-========-========-========-========-========-========-========-========+ Q  |   Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |bQ  |Byte  |        |        |        |        |        |        |        |        |SQ  |======+=======================================================================|eQ  | 0    |                           Operation code                              |aQ  |------+-----------------------------------------------------------------------|eQ  | 1    |   Logical unit number    |                  Reserved                  |tQ  |------+-----------------------------------------------------------------------|iQ  | 2    | (MSB)                                                                 |dQ  |------+---                                                                 ---|tQ  | 3    |                                                                       |aQ  |------+---                        Logical block address (if required)      ---|eQ  | 4    |                                                                       | Q  |------+---                                                                 ---|wQ  | 5    |                                                                 (LSB) |-Q  |------+-----------------------------------------------------------------------|iQ  | 6    |                           Reserved                                    | Q  |------+-----------------------------------------------------------------------|.Q  | 7    | (MSB)                     Transfer length (if required)               |dQ  |------+---                        Parameter list length (if required)      ---|mQ  | 8    |                           Allocation length (if required)       (LSB) |sQ  |------+-----------------------------------------------------------------------|pQ  | 9    |                           Control                                     |tQ  +==============================================================================+d  e  rJ       Table 23 - Typical command descriptor block for twelve-byte commandsQ  +======-========-========-========-========-========-========-========-========+tQ  |   Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |hQ  |Byte  |        |        |        |        |        |        |        |        |sQ  |======+=======================================================================|tQ  | 0    |                           Operation code                              |rQ  |------+-----------------------------------------------------------------------|rQ  | 1    |   Logical unit number    |                  Reserved                  |iQ  |------+-----------------------------------------------------------------------|aQ  | 2    | (MSB)                                                                 |dQ  |------+---                                                                 ---|hQ  | 3    |                                                                       |rQ  |------+---                        Logical block address (if required)      ---|eQ  | 4    |                                                                       | Q  |------+---                                                                 ---|eQ  | 5    |                                                                 (LSB) |rQ  |------+-----------------------------------------------------------------------| Q  | 6    | (MSB)                                                                 |hQ  |------+---                                                                 ---|iQ  | 7    |                           Transfer length (if required)               |bQ  |------+---                        Parameter list length (if required)      ---|iQ  | 8    |                           Allocation length (if required)             |yQ  |------+---                                                                 ---|oQ  | 9    |                                                                 (LSB) |fQ  |------+-----------------------------------------------------------------------|aQ  |10    |                           Reserved                                    |tQ  |------+-----------------------------------------------------------------------|gQ  |11    |                           Control                                     |sQ  +==============================================================================+n     e  7.2.1 Operation code   EH  The operation code (see table 24) of the command descriptor block has aK  group code field and a command code field.  The three-bit group code field G  provides for eight groups of command codes.  The five-bit command codefJ  field provides for thirty-two command codes in each group.  Thus, a totalK  of 256 possible operation codes exist.  Operation codes are defined in theu  subsequent subclauses.n  n6  The group code specifies one of the following groups:5     a)     Group 0 - six-byte commands (see table 21)m5     b)     Group 1 - ten-byte commands (see table 22) 5     c)     Group 2 - ten-byte commands (see table 22)e     d)     Group 3 - reservedo     e)     Group 4 - reservedb8     f)     Group 5 - twelve-byte commands (see table 23)%     g)     Group 6 - vendor-specific T$     h)     Group 7 - vendor-specific  c4                            Table 24 - Operation codeP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |=====+==========================+============================================|P  |     |         Group code       |                Command code                |P  +=============================================================================+     7.2.2 Logical unit number  cI  The logical unit number is defined in the IDENTIFY message (6.6.7).  TheeI  target shall ignore the logical unit number specified within the commandcI  descriptor block if an IDENTIFY message was received.  It is recommended G  that the logical unit number in the command descriptor block be set to   zero.    tP     NOTICE:  The logical unit number field is included in the command descriptorH     block for compatibility with some SCSI-1 devices.  This field may beN     reclaimed in SCSI-3.  New implementations should use the outbound IDENTIFYH     message, which is mandatory in SCSI-2, to establish the I_T_L nexus.  =  7.2.3 Logical block address  =K  The logical block address on logical units or within a partition on device E  volumes shall begin with block zero and be contiguous up to the last =  logical block on that logical unit or within that partition.-  -D  A six-byte command descriptor block contains a 21-bit logical blockE  address.  The ten-byte and the twelve-byte command descriptor blocks D  contain 32-bit logical block addresses.  Logical block addresses inL  additional parameter data have their length specified for each occurrence. '  See the specific command descriptions.      7.2.4 Transfer length   J  The transfer length field specifies the amount of data to be transferred,H  usually the number of blocks.  For several commands the transfer lengthE  indicates the requested number of bytes to be sent as defined in the J  command description.  For these commands the transfer length field may beH  identified by a different name.  See the following descriptions and the9  individual command descriptions for further information.r  oJ  Commands that use one byte for the transfer length allow up to 256 blocksH  of data to be transferred by one command.  A transfer length value of 1J  to 255 indicates the number of blocks that shall be transferred.  A value  of zero indicates 256 blocks.  uH  In commands that use multiple bytes for the transfer length, a transferJ  length of zero indicates that no data transfer shall take place.  A value?  of one or greater indicates the number of blocks that shall be2
  transferred.p   C  Refer to the specific command description for further information.r  o  7.2.5 Parameter list length   F  The parameter list length is used to specify the number of bytes sentD  during the DATA OUT phase.  This field is typically used in commandF  descriptor blocks for parameters that are sent to a target (e.g. modeG  parameters, diagnostic parameters, log parameters, etc.).  A parametertB  length of zero indicates that no data shall be transferred.  This/  condition shall not be considered as an error.t  i  7.2.6 Allocation length  tJ  The allocation length field specifies the maximum number of bytes that anI  initiator has allocated for returned data.  An allocation length of zero-J  indicates that no data shall be transferred.  This condition shall not beK  considered as an error.  The target shall terminate the DATA IN phase when I  allocation length bytes have been transferred or when all available data=K  have been transferred to the initiator, whichever is less.  The allocation J  length is used to limit the maximum amount of data (e.g. sense data, modeA  data, log data, diagnostic data, etc.) returned to an initiator.|     7.2.7 Control field   K  The control field is the last byte of every command descriptor block.  The-&  control field is defined in table 25.   4                             Table 25 - Control fieldP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |=====+=================+===================================+========+========|P  |     | Vendor-specific |         Reserved                  |  Flag  |  Link  |P  +=============================================================================+     aD  The flag bit specifies which message the target shall return to theK  initiator if the link bit is one and the command completes without error. -,  Implementation of the flag bit is optional.  -I  The flag bit should be set to zero if the link bit is zero.  If link bit I  is zero and the flag bit is one, the target shall return CHECK CONDITION=8  status.  The sense key shall be set to ILLEGAL REQUEST.   D  If the flag bit is zero and the link bit is one, and if the commandJ  completes successfully, the target shall send the LINKED COMMAND COMPLETEE  message.  If the flag bit is one and the link bit is one, and if the|I  command completes successfully, the target shall send the LINKED COMMAND   COMPLETE (WITH FLAG) message.  =Q     NOTE 46 The flag bit is typically used to cause an interrupt in the initiator      between linked commands.   L  The link bit is used to continue the I/O process across multiple commands. .  Implementation of the link bit is optional.  J  A link bit of one indicates that the initiator requests a continuation ofH  the I/O process and that the target should enter the command phase upon/  successful completion of the current command.     G  If the link bit is one, and if the command completes successfully, the J  target shall return INTERMEDIATE or INTERMEDIATE-CONDITION MET status andA  shall then send one of the two messages defined by the flag bit.    H  If either of the link and flag bits are set to one, and the target doesH  not implement linked commands, it shall return CHECK CONDITION status. /  The sense key shall be set to ILLEGAL REQUEST.      7.3 Status   -I  The status byte and status byte code are defined in tables 26 and 27.  A F  status byte shall be sent from the target to the initiator during theE  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;0     f)     an unexpected disconnect (see 6.1.1).   K  The STATUS phase normally occurs at the end of a command but in some cases >  may occur prior to transferring the command descriptor block.  -3                              Table 26 - Status byte P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |=====+=================+============================================+========|P  |     |     Reserved    |               Status byte code             |Reserved|P  +=============================================================================+      5                           Table 27 - Status byte code D  +==================================-==============================+D  |    Bits of status byte           |  Status                      |D  |----------------------------------|                              |D  |   7 | 6 | 5 | 4 | 3 | 2 | 1 | 0  |                              |D  |-----+---+---+---+---+---+---+----+------------------------------|D  |   R | R | 0 | 0 | 0 | 0 | 0 | R  |  GOOD                        |D  |   R | R | 0 | 0 | 0 | 0 | 1 | R  |  CHECK CONDITION             |D  |   R | R | 0 | 0 | 0 | 1 | 0 | R  |  CONDITION MET               |D  |   R | R | 0 | 0 | 1 | 0 | 0 | R  |  BUSY                        |D  |   R | R | 0 | 1 | 0 | 0 | 0 | R  |  INTERMEDIATE                |D  |   R | R | 0 | 1 | 0 | 1 | 0 | R  |  INTERMEDIATE-CONDITION MET  |D  |   R | R | 0 | 1 | 1 | 0 | 0 | R  |  RESERVATION CONFLICT        |D  |   R | R | 1 | 0 | 0 | 0 | 1 | R  |  COMMAND TERMINATED          |D  |   R | R | 1 | 0 | 1 | 0 | 0 | R  |  QUEUE FULL                  |D  |----------------------------------|                              |D  |           All other codes        |  Reserved                    |D  |-----------------------------------------------------------------|D  |  Key: R = Reserved bit                                          |D  +=================================================================+   6  A definition of the status byte codes is given below.  eD  7.3.1 GOOD:  This status indicates that the target has successfully  completed the command.    K  7.3.2 CHECK CONDITION:  This status indicates that a contingent allegiance "  condition has occurred (see 7.6).   C  7.3.3 CONDITION MET:  This status or INTERMEDIATE-CONDITION MET isBG  returned whenever the requested operation is satisfied (see the SEARCH-  DATA and PREFETCH commands).      I  7.3.4 BUSY:  This status indicates that the target is busy.  This status-J  shall be returned whenever a target is unable to accept a command from anE  otherwise acceptable initiator (i.e. no reservation conflicts).  The I  recommended initiator recovery action is to issue the command again at a=  later time.   H  7.3.5 INTERMEDIATE:  This status or INTERMEDIATE-CONDITION MET shall beH  returned for every successfully completed command in a series of linkedJ  commands (except the last command), unless the command is terminated withI  CHECK CONDITION, RESERVATION CONFLICT, or COMMAND TERMINATED status.  IfdG  INTERMEDIATE or INTERMEDIATE-CONDITION MET status is not returned, the F  series of linked commands is terminated and the I/O process is ended.  oI  7.3.6 INTERMEDIATE-CONDITION MET:  This status is the combination of thet)  CONDITION MET and INTERMEDIATE statuses.p  -G  7.3.7 RESERVATION CONFLICT:  This status shall be returned whenever ansJ  initiator attempts to access a logical unit or an extent within a logicalK  unit that is reserved with a conflicting reservation type for another SCSIoE  device (see the RESERVE and RESERVE UNIT commands).  The recommended I  initiator recovery action is to issue the command again at a later time.-  =F  7.3.8 COMMAND TERMINATED:  This status shall be returned whenever theJ  target terminates the current I/O process after receiving a TERMINATE I/OA  PROCESS message (see 6.6.22).  This status also indicates that a 8  contingent allegiance condition has occurred (see 7.6).  dI  7.3.9 QUEUE FULL:  This status shall be implemented if tagged queuing is=G  implemented.  This status is returned when a SIMPLE QUEUE TAG, ORDEREDlJ  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.  s  7.4 Command examplesN  YH  The following subclauses give examples of typical command processing in  the SCSI environment.  l  7.4.1 Single command example   OK  An I/O process containing one untagged READ command is used in this clause K  to illustrate a simple I/O process on the SCSI bus.  This example does note'  include error or exception conditions.h  dE  The initiator has one set of active pointers that includes a commandtK  pointer, a data pointer, and a status pointer.  In addition, the initiatorcF  has one set of saved pointers for each I/O process that it is able toH  concurrently manage.  The initiator sets up the saved pointers to pointK  to the appropriate bytes for the I/O process and copies the saved pointersmG  to the active pointers.  It then arbitrates for the SCSI bus, and uponbK  winning arbitration, selects the target.  Once the target is selected, thel+  target assumes control of the I/O process.a  tK  During the SELECTION phase, the initiator asserts the ATN signal to informtK  the target that the initiator wishes to send a message.  The target enterssB  the MESSAGE OUT phase and transfers the IDENTIFY message from theH  initiator.  This message informs the target of which logical unit is toI  be used.  At this point, an I_T_L nexus has been established for the I/OaF  process.  This nexus associates the initiator's pointers with the I/O	  process.y  dC  The target switches to the COMMAND phase and transfers the commandoK  descriptor block from the initiator.  In this case, the command descriptor F  block contains a READ command.  The target interprets the command andF  switches to the DATA IN phase, transfers the data, switches to STATUSH  phase, sends GOOD status, switches to MESSAGE IN phase, and transfers aK  COMMAND COMPLETE message.  After successfully sending the COMMAND COMPLETE K  message, the target goes to the BUS FREE phase by releasing the BSY signal   and the I/O process ends.  d  7.4.2 Disconnect example   tE  In the above single command example, the length of time necessary toiB  obtain the data may require a time-consuming physical positioningB  operation.  In order to improve system throughput, the target mayK  disconnect from the initiator, thereby freeing the SCSI bus to allow others  I/O process to occur.     H  After the target has received the READ command (and has determined thatF  there will be a delay), it disconnects from the SCSI bus by sending a7  DISCONNECT message and by going to the BUS FREE phase.   sI  After the target retrieves the requested data from the peripheral devicegH  it arbitrates for the SCSI bus.  Upon winning arbitration, it reselectsE  the initiator and sends an IDENTIFY message to the initiator via theaJ  MESSAGE IN phase.  This revives the I_T_L nexus so that the initiator canI  retrieve the correct set of pointers for the I/O process.  The initiator J  restores the active pointers to their most recent saved values (which, inG  this case, are the initial values) and the target continues (as in the 3  single command example) to finish the I/O process.s  aI  If target wishes to disconnect after transferring part of the data (e.g.|I  while crossing a cylinder boundary), it may do so by sending a SAVE DATAyC  POINTER message and a DISCONNECT message to the initiator and then2I  disconnecting.  When reconnection is completed, the current data pointer=D  is restored to its value immediately prior to the SAVE DATA POINTER	  message.    G  On those occasions when an error or exception condition occurs and the=H  target elects to repeat the information transfer, the target may repeat@  the transfer by either issuing a RESTORE POINTERS message or byA  disconnecting without issuing a SAVE DATA POINTER message.  When=D  reconnection is completed, the most recent saved pointer values are
  restored.  s  7.4.3 Linked command examplei  hD  An I/O process may contain multiple commands linked together.  UponC  completing a linked command successfully, the target automatically J  proceeds to the next linked command for the I/O process.  All commands inI  a series of linked commands are addressed to the same nexus and are partl  of a single I/O process..   D  The commands are not entirely independent.  When using the relativeI  address bit (see 9.1.11), the address of the last logical block accessedEG  by one of the commands is available to the next command.  Thus one can J  search for a particular data pattern using a SEARCH DATA command and thenG  read the logical block containing the data pattern with a READ command I  linked to the SEARCH DATA command.  One can also read a logical block at E  a specified displacement from the block containing the data pattern.o  nI  A LINKED COMMAND COMPLETE or LINKED COMMAND COMPLETE (WITH FLAG) messagedK  is sent from the target to the initiator to indicate that a linked commandaH  completed.  The initiator then updates the saved pointers for the nexusH  so that subsequent transfers from the target reference the next commandD  of the series.  Command processing of linked and single commands isI  similar except that relative addressing is permitted in linked commands.s  fK  For example, a successful completion of a SEARCH DATA EQUAL command causesnI  the target to continue with the linked READ command from the initiator. CI  If the relative address bit in the READ command has been set to one, and K  the address field of the READ command is set to zero, the target transfers 3  the successfully searched block to the initiator. a  t4  7.5 Command processing considerations and exception  conditions   oG  The following subclauses describe some exception conditions and errors C  associated with command processing and the sequencing of commands.   )(  7.5.1 Programmable operating definition  aJ  Some applications require that the operating definition of a logical unitI  be modified to meet the special requirements of a particular initiator. tC  The program-controlled modification of the operating definition isiF  typically provided to allow operating systems to change the operatingD  definition of a more recently developed targets to one that is moreF  compatible with the operating system.  This ability requires that theA  system comply with the low-level hardware definitions of SCSI-2.+  =I  The parameters that can be changed by modifying the operating definition J  of a logical unit include the vendor identification, the device type, theK  device model, the SCSI compliance level, the SCSI specification level, the F  command set, and other parameters.  The low-level hardware parametersD  including signal timing and parity definitions cannot be changed byI  modifying the operating definition.  The present operating definition of-J  a logical unit with respect to an initiator can be determined at any timeK  by execution of an INQUIRY command.  In some vendor-specific cases, it may-J  also be necessary to perform other commands including MODE SENSE and READ
  CAPACITY.   I  Each logical unit begins with a particular operating definition.  If the K  logical unit supports the CHANGE DEFINITION command, the present operating|I  definition can be changed to any other operating definition supported by0G  the logical unit.  The actual details of the operating definition of a1J  logical unit are vendor-specific.  If the operating definition is changedG  to one that does not include the CHANGE DEFINITION command, the target|9  should continue to accept the CHANGE DEFINITION command.0  1H  If an error occurs during execution of a CHANGE DEFINITION command, theE  original operating definition remains in effect after the command issA  executed. The new operating definition becomes active only after-9  successful execution of the CHANGE DEFINITION command.  s  eB  Since new operating definitions may preclude the execution of I/OK  processes that are already in progress, the target may disconnect to allowsA  completion of any I/O processes that are in progress.  OperatingiK  definition changes that may cause conflicts with the normal operation fromCH  other initiators shall be indicated to those initiators by generating aI  unit attention condition for each other initiator.  The additional senseN3  code shall be set to CHANGED OPERATING DEFINITION.r  eF  An initiator may request a list of the operating definitions that theI  target supports and descriptive text for each operating definition usingh  the INQUIRY command.e  n%  7.5.2 Incorrect initiator connectiont  c?  An incorrect initiator connection occurs on a reconnection if:iD     a)     an initiator attempts to reconnect to an I/O process, and8     b)     a soft reset condition has not occurred, and M     c)     the initiator does not send an ABORT, ABORT TAG, BUS DEVICE RESET,rH            CLEAR QUEUE, or TERMINATE I/O PROCESS message during the same5            MESSAGE OUT phase as the IDENTIFY message.h  CG  An incorrect initiator connection also occurs on an initial connection   when an initiator:RM     a)     attempts to establish an I_T_L_Q nexus when an I_T_L nexus alreadyi0            exists from a previous connection, orM     b)     attempts to establish an I_T_L nexus when an I_T_L_Q nexus alreadyIF            exists, unless there is a contingent allegiance or extendedI            contingent allegiance condition present for the logical unit.    iH  A target that detects an incorrect initiator connection shall abort allJ  I/O processes for the initiator on the logical unit or target routine andD  shall return CHECK CONDITION status.  The sense key shall be set toI  ABORTED COMMAND and the additional sense code shall be set to OVERLAPPED:  COMMANDS ATTEMPTED.  tH  If an initiator reconnects to an I/O process and a soft reset conditionA  has occurred, the target shall meet the requirements of 6.2.2.2.l  i	     NOTESaM     47 An incorrect initiator connection may be indicative of a serious errorEO     and, if not detected, could result in an I/O process operating with a wrongiN     set of pointers.  This is considered a catastrophic failure on the part ofO     the initiator.  Therefore, vendor-specific error recovery procedures may be K     required to guarantee the data integrity on the medium.  The target mayiN     return additional sense data to aid in this error recovery procedure (e.g.N     sequential-access devices may return the residue of blocks remaining to beA     written or read at the time the second command was received). P     48 Some targets may not detect an incorrect initiator connection until after3     the command descriptor block has been received.e  i+  7.5.3 Selection of an invalid logical unita  pJ  The target's response to selection of a logical unit that is not valid is'  described in the following paragraphs.i  s+  The logical unit may not be valid because:rJ     a)     the target does not support the logical unit (e.g. some targetsJ            support only one peripheral device).  In response to an INQUIRYE            command, the target shall return the INQUIRY data with the I            peripheral qualifier set to the value required in 8.2.5.1.  InIO            response to any other command except REQUEST SENSE, the target shallaM            terminate the command with CHECK CONDITION status.  In response togL            a REQUEST SENSE command, the target shall return sense data.  TheM            sense key shall be set to ILLEGAL REQUEST and the additional sense ;            code shall be set to LOGICAL UNIT NOT SUPPORTED. M     b)     the target supports the logical unit, but the peripheral device isOK            not currently attached to the target.  In response to an INQUIRY E            command, the target shall return the INQUIRY data with theaI            peripheral qualifier set to the value required in 8.2.5.1.  IncO            response to any other command except REQUEST SENSE, the target shallSM            terminate the command with CHECK CONDITION status.  In response toML            a REQUEST SENSE command, the target shall return sense data.  TheM            sense key shall be set to ILLEGAL REQUEST and the additional senset;            code shall be set to LOGICAL UNIT NOT SUPPORTED. L     c)     the target supports the logical unit and the peripheral device isM            attached, but not operational.  In response to an INQUIRY command, G            the target shall return the INQUIRY data with the peripheraltH            qualifier set to the value required in 8.2.5.1.  The target'sJ            response to any command other than INQUIRY and REQUEST SENSE is            vendor-specific.iO     d)     the target supports the logical unit but is incapable of determining M            if the peripheral device is attached or is not operational when ithL            is not ready.  In response to an INQUIRY command,the target shallK            return the INQUIRY data with the peripheral qualifier set to theoN            value required in 8.2.5.1.  In response to a REQUEST SENSE command,M            the target shall return the REQUEST SENSE data with a sense key ofoH            NO SENSE unless a contingent allegiance exists.  The target's<            response to any other command is vendor-specific.  s  7.5.4 Parameter roundingn  xJ  Certain parameters sent to a target with various commands contain a rangeK  of values.  Targets may choose to implement only selected values from this F  range.  When the target receives a value that it does not support, itH  either rejects the command (CHECK CONDITION status with ILLEGAL REQUESTF  sense key) or it rounds the value received to a supported value.  TheK  target shall reject unsupported values unless rounding is permitted in thea  description of the parameter.  rD  Rounding of parameter values, when permitted, shall be performed asI  follows -  A target that receives a parameter value that is not an exactoI  supported value shall adjust the value to one that it supports and shallrH  return CHECK CONDITION status with a sense key of RECOVERED ERROR.  TheH  additional sense code shall be set to ROUNDED PARAMETER.  The initiatorG  is responsible to issue an appropriate command to learn what value thec  target has selected.u  aP     NOTE 49 Generally, the target should adjust maximum-value fields down to theQ     next lower supported value than the one specified by the initiator.  Minimum- Q     value fields should be rounded up to the next higher supported value than the O     one specified by the initiator.  In some cases, the type of rounding (up orcF     down) is explicitly specified in the description of the parameter.   '  7.5.5 Asynchronous event notification r  sE  Implementation of asynchronous event notification is optional.  ThistF  protocol can be used to inform processor devices that an asynchronousH  event has occurred.  A SEND command with an AEN bit of one is issued toJ  a processor device with a subsequent data phase that includes the REQUESTI  SENSE information.  SCSI devices that respond to an INQUIRY command as a J  processor device type with asynchronous event notification capability mayH  be notified of asynchronous events using this protocol.  An SCSI device@  has to be capable of acting as an initiator in order to perform!  asynchronous event notification.c  aM     NOTE 50 Asynchronous event notification cannot be used with a device thatsN     acts as a temporary initiator (e.g. devices executing COPY commands) since2     they are not identified as a processor device.  aD  Parameters affecting the use of asynchronous event notification are2  contained in the control mode page (see 8.3.3.1).  h6  The four uses of asynchronous event notification are:H     a)     informing a processor of an error condition encountered after            command completion;M     b)     informing all processor devices that a newly initialized device iso            available;aN     c)     informing all processor devices of other unit attention conditions;H     d)     informing all processor devices of other asynchronous events.   G  An example of the first case above is a device that implements a writetK  cache.  If the target is unable to write cached data to the medium, it maypF  use an asynchronous event notification to inform the initiator of theB  failure.  An extended contingent allegiance condition may also beH  established during the same I_T_L nexus used for the asynchronous event  notification (see 6.6.9).   G  An example of the third case above is a device that supports removablemK  media.  Asynchronous event notification may be used to inform an initiatoraF  of a not-ready-to-ready transition (medium changed) or of an operatorH  initiated event (e.g. activating a write protect switch or activating a  start or stop switch).e  sB  An example of the fourth case above is a sequential-access device@  performing a REWIND command with the immediate bit set to one. H  Asynchronous event notification may be used to inform an initiator thatH  the beginning of medium has been reached.  Completion of a CD-ROM AUDIOF  PLAY command started in the immediate mode is another example of this  case.  rJ  Notification of an asynchronous event is performed using the SEND commandH  with the AEN bit set to one.  The information identifying the conditionG  being reported shall be returned during the DATA OUT phase of the SENDnG  command.  See 12.2.2 for further information on the format of the datae  sent.  iJ  An error condition or unit attention condition shall be reported once perE  occurrence of the event causing it.  The target may choose to use andI  asynchronous event notification or to return CHECK CONDITION status on aeI  subsequent command, but not both.  Notification of command-related erroreF  conditions shall be sent only to the processor that initiated the I/O	  process.s   C  The asynchronous event notification protocol can be used to notify E  processor devices that a system resource has become available.  If aIH  target chooses to use this method, the sense key in the sense data sent9  to the processor device shall be set to UNIT ATTENTION. t  eH  The asynchronous event notification protocol shall be sent only to SCSIE  devices that return processor device type with an AENC bit of one in I  response to an INQUIRY command.  The INQUIRY command should be issued tonE  logical unit zero of each SCSI device responding to selection.  ThisiC  procedure shall be conducted prior to the first asynchronous event @  notification and shall be repeated whenever the device deems itD  appropriate or when an event occurs that may invalidate the currentJ  information.  (See 6.6.21, SYNCHRONOUS DATA TRANSFER REQUEST message, for  examples of these events.)   oH  Each SCSI device that returns processor device type with an AENC bit ofI  one shall be issued a TEST UNIT READY command to determine that the SCSIeH  device is ready to receive an asynchronous event notification.  An SCSIL  device returning CHECK CONDITION status is issued a REQUEST SENSE command. G  This clears any pending unit attention condition.  An SCSI device that G  returns processor device type with an AENC bit of one and returns GOOD I  status when issued a TEST UNIT READY command shall accept a SEND commandi  with an AEN bit of one.  _K     NOTE 51 An SCSI device which can use asynchronous event notification at Q     initialization time should provide means to defeat these notifications.  ThiseK     can be done with a switch or jumper wire.  Devices that implement savedgI     parameters may alternatively save the asynchronous event notificationtN     permissions either on a per SCSI device basis or as a system-wide option. Q     In any case, a device conducts a survey with INQUIRY commands to be sure thatON     the devices on the SCSI bus are appropriate destinations for SEND commandsO     with an AEN bit of one.  (The devices on the bus or the SCSI ID assignmentsr     may have changed.)     7.5.6 Unexpected reselections  cI  An unexpected reselection occurs if an SCSI device attempts to reconnect K  to an I/O process for which a nexus does not exist.  An SCSI device shouldEB  respond to an unexpected reselection by sending an ABORT message.  t$  7.6 Contingent allegiance condition   H  The contingent allegiance condition shall exist following the return ofI  CHECK CONDITION or COMMAND TERMINATED status.  The contingent allegianceuK  condition shall be preserved for the I_T_x nexus until it is cleared.  TheoH  contingent allegiance condition shall be cleared upon the generation ofC  a hard reset condition, or by an ABORT message, a BUS DEVICE RESET C  message, or any subsequent command for the I_T_x nexus.  While the K  contingent allegiance condition exists the target shall preserve the sense   data for the initiator.  oJ  While the contingent allegiance condition exists, if the target is unableG  to maintain separate sense data, the target shall respond to any other G  requests for access to the logical unit or target routine from anotheroI  initiator with a BUSY status.  Execution of all tagged I/O processes foriK  the I_T_L nexus for which the contingent allegiance condition exists shallpC  be suspended until the contingent allegiance condition is cleared.N  R-  7.7 Extended contingent allegiance conditione  eC  Implementation of extended contingent allegiance is optional.  TheoK  extended contingent allegiance condition extends the contingent allegianceeI  condition for an I_T_x nexus.  This condition is generated by the targetTF  sending an INITIATE RECOVERY message to the initiator following CHECKI  CONDITION or COMMAND TERMINATED status and prior to the COMMAND COMPLETE I  message.  This condition shall be preserved until it is cleared by a BUSuB  DEVICE RESET message, a RELEASE RECOVERY message, or a hard reset  condition.a  cF  While the extended contingent allegiance condition exists, the targetG  shall respond to any other request for access to the logical unit fromlH  another initiator with BUSY status.  Execution of all I/O processes forH  the logical unit for which the extended contingent allegiance conditionI  exists shall be suspended until the RELEASE RECOVERY message is receiveda  by the target.m  d	     NOTEStQ     52 It is not required to generate an extended contingent allegiance conditionTO     for every CHECK CONDITION or COMMAND TERMINATED status that occurs.  SimpleOL     errors not requiring an extended recovery may be dealt with by using the#     contingent allegiance protocol.oM     53 During the existence of the extended contingent allegiance condition, eL     appropriate error recovery sequences may be executed.  Such commands canN     correct data, modify or delete queued commands, perform LOG SENSE commandsI     and obtain diagnostic information.  Extended contingent allegiance is P     recommended for error conditions that may require execution of multiple-stepH     error-recovery protocols without interference from other initiators.   H  An extended contingent allegiance condition may also be generated usingJ  an asynchronous event notification protocol.  When the event is detected,F  the bus device that detected the event assumes the initiator role andC  transmits a SEND command with an AEN bit of one to the appropriatea  device(s) (see 12.2.2).   C  If the device wishes to generate an extended contingent allegiance F  condition during an asynchronous event notification, it shall send anH  INITIATE RECOVERY message following the IDENTIFY message (and followingL  any queue tag message) and prior to the COMMAND phase of the SEND command. J  An extended contingent allegiance condition can be generated for only oneH  I_T_L nexus at a time.  The extended contingent allegiance condition isG  cleared when a RELEASE RECOVERY message is received from the device tovH  which the INITIATE RECOVERY message was sent.  The generation of a hardF  reset condition, or receipt of a BUS DEVICE RESET message, shall also4  clear the extended contingent allegiance condition.  sK  During an extended contingent allegiance, only untagged I/O processes fromdI  the SCSI device to which the INITIATE RECOVERY message was sent shall beHG  executed by the target for the logical unit.  If the initiator sends aaK  queue tag message, the target shall respond with QUEUE FULL status.  AfterlF  the extended contingent allegiance condition is cleared, any commands2  remaining in the command queue shall be executed.  d   Queued I/O processes  sI  The implementation of queuing for I/O processes is optional.  Queuing ofi@  I/O processes allows a target to accept multiple I/O processes.  xJ  There are two methods for implementation of queuing, tagged and untagged.J  Tagged queuing allows a target to accept multiple I/O processes from eachF  initiator for each logical unit.  Untagged queuing allows a target toK  accept one I/O process from each initiator for each logical unit or targetlJ  routine.  Untagged queuing may be supported by SCSI-1 or SCSI-2 devices. !  Tagged queuing is new in SCSI-2.c  aI  A target may support both tagged and untagged queuing.  An initiator maynF  not mix the use of tagged and untagged queuing for I/O processes to aK  logical unit, except during a contingent allegiance or extended contingenthJ  allegiance condition when only untagged initial connections are allowed. I  An initiator that elects to use tagged queuing does not preclude anotheri<  initiator on the same SCSI bus from using untagged queuing.     7.8.1 Untagged queuingo  eK  Untagged queuing allows a target to accept a command from an initiator for K  a logical unit or target routine while I/O processes from other initiatorstD  are being executed.  Only one command for each I_T_x nexus shall be  accepted at a time.    nI  An I/O process may be initiated any time the BUS FREE phase exists, evensA  if an I/O process from a different initiator is  active.  If theoK  disconnect privilege is not granted in the IDENTIFY message of the current;I  I/O process, the target may either suspend all other I/O processes or ite3  may return BUSY status to the current I/O process.l  oK  The I_T_x nexus sufficiently specifies the relationship so that the targetpJ  can reconnect to the initiator to restore the pointers for I/O process asC  long as only one I/O process per I_T_x nexus is issued.  It is thegI  responsibility of the initiator to assure that only one such I/O processo#  is issued at any time (see 7.5.2).n  a  7.8.2 Tagged queuingA  xI  Tagged queuing allows a target to accept multiple I/O processes from the G  same or different initiators until the logical unit's command queue is9H  full.  If an I/O process is received and the command queue is full, theA  target shall terminate the I/O process with QUEUE FULL status.  o  aK  The command queue is setup by the target for each supported logical unit. pI  Initiators may add or delete I/O processes to the queue.  When adding aniK  I/O process, the initiator may specify fixed order of execution, allow the I  target to define the order of execution, or specify that the I/O processi  is to be executed next.   I  If the disconnect privilege is not granted in the IDENTIFY message for ao9  tagged I/O process, the target shall return BUSY status.P   G  The queue tag messages (see 6.6.17) allow the initiator to establish a F  unique I_T_L_Q nexus to identify each I/O process.  The I_T_L_Q nexusI  allows the target to reconnect to a specific I/O process, and allows theiC  initiator to restore the set of pointers for that I/O process.  AntJ  initiator may have several I/O processes ongoing to the same or different2  logical units as long as each has a unique nexus.  oG  If only SIMPLE QUEUE TAG messages are used, the target may execute theiI  commands in any order that is deemed desirable within the constraints ofoG  the queue management algorithm specified in the control mode page (see 
  8.3.3.1).   E  If ORDERED QUEUE TAG messages are used, the target shall execute the G  commands in the order received with respect to other commands receivediF  with ORDERED QUEUE TAG messages.  All commands received with a SIMPLEH  QUEUE TAG message prior to a command received with an ORDERED QUEUE TAGH  message, regardless of initiator, shall be executed before that commandI  with the ORDERED QUEUE TAG message.  All commands received with a SIMPLElE  QUEUE TAG message after a command received with an ORDERED QUEUE TAG G  message, regardless of initiator, shall be executed after that commandm%  with the ORDERED QUEUE TAG message.    oK  A command received with a HEAD OF QUEUE TAG message is placed first in thedI  queue, to be executed next.  A command received with a HEAD OF QUEUE TAGpH  message shall be executed prior to any queued I/O process.  ConsecutiveJ  commands received with HEAD OF QUEUE TAG messages are executed in a last-  in-first-out order.  ,I  An I/O process received without a queue tag message, while there are anyeH  tagged I/O commands in the command queue from the same initiator, is anI  incorrect initiator connection (see 7.5.2), unless there is a contingentc8  allegiance or extended contingent allegiance condition.   D  A series of linked commands constitute a single I/O process.  TheseL  commands are assigned the queue tag established in the initial connection. H  A command received with a HEAD OF QUEUE TAG message shall not suspend aD  series of linked commands for which the target has begun execution.  oJ  The RESERVE and RELEASE commands should be sent with an ORDERED QUEUE TAGI  message.  Use of the HEAD OF QUEUE TAG message with these commands couldnA  result in reservation conflicts with previously issued commands.   vI     NOTE 54 Initiators should not issue another I/O processes following ahK     reservation request until that request is honoured by the target.  This B     prevents possible sequencing errors or file system corruption.  eD  There are two methods of dealing with the command queue following aF  contingent allegiance condition.  The method used is specified in theC  control mode page by the queue error management bit (see 8.3.3.1).   eH  The first method allows the execution of tagged I/O processes to resumeK  when the contingent allegiance or extended contingent allegiance conditionwJ  is cleared.  The target returns BUSY status to other initiators while theK  contingent allegiance or extended contingent allegiance condition exists. cC  During this time, all tagged I/O processes are suspended.  All I/OiI  processes used for recovery operations shall be untagged.  The queue maynH  be modified by removing all or selected I/O processes from the queue as   part of the recovery procedure.  eJ  If commands are combined by the queuing algorithm such that the exceptionF  condition affects more than one command, then a contingent allegiance8  condition shall be generated for all affected commands.   J  The second method aborts all I/O processes when the contingent allegianceJ  or extended contingent allegiance condition is cleared.  A unit attentionI  condition shall be generated for all other initiators and the additionaloB  sense code shall be set to COMMANDS CLEARED BY ANOTHER INITIATOR.  uK  A device that does not support tagged I/O processes (e.g. not implemented,/E  disabled by the Dque bit in the control mode page, or switched to ancJ  operating definition that does not include tagged I/O processes) it shallE  respond to any queue tag message with a MESSAGE REJECT message.  TheeD  target shall continue the I/O process as if it were an untagged I/O	  process.   t?  Tagged queuing may also be temporarily disabled during certaincE  initialization periods or to control internal resource utilization. TG  During these periods the target may return QUEUE FULL status or it may @  respond to any queue tag message with a MESSAGE REJECT message.  LI  Several messages may be used to clear part or all of the command queue.  H  Please refer to the ABORT, ABORT TAG, BUS DEVICE RESET, and CLEAR QUEUE"  messages in clause 6 for details.  o$  7.8.3 Example of queued I/O process   E  This example of queuing I/O processes illustrates the execution of anH  number of commands.  After each command, the state of the queue kept inG  the target is shown to indicate the function actually performed by thec	  queuing.e  t-  7.8.3.1 Typical sequences for tagged queuing   sE  An I/O process using tagged queuing uses the following sequences forqH  normal execution.  The initiator first arbitrates for the SCSI bus, andH  after successfully obtaining the SCSI bus, selects the appropriate SCSIK  device.  The ATN signal is asserted during the SELECTION phase to indicate K  that a MESSAGE OUT phase is requested by the initiator.  The first messageeI  byte transferred is an IDENTIFY message.  The ATN signal continues to becI  asserted during the MESSAGE OUT phase to indicate that the initiator hasqH  another message.  The second message byte transferred is the first byteF  of the appropriate queue tag message, in this case a SIMPLE QUEUE TAGH  message.  The third and last message byte is transmitted containing the?  second byte of the queue tag message, the queue tag.  As it isxH  transferred, the ATN signal is negated to indicate that no more messageG  bytes are available.  The target then transfers the command descriptoreJ  block.  Assuming the command requires disconnection, the target transmitsK  a DISCONNECT message to the initiator and then enters the BUS FREE phase.  G  The target places the command, identified by the I_T_L_Q nexus, at thel(  appropriate place in the command queue.  vF  When the target removes I/O processes from the queue for execution, aH  physical latency period may occur.  At the end of this period, when theJ  target is prepared to transfer the appropriate data, the target begins anH  ARBITRATION phase and, upon winning, enters a RESELECTION phase.  AfterI  a successful reselection, the target sends the IDENTIFY message followedmJ  by a SIMPLE QUEUE TAG message with the queue tag value originally sent byE  the initiator.  The initiator uses the I_T_L_Q nexus to identify the K  correct set of pointers and control blocks associated with the I/O processcI  and to establish the necessary conditions for data transfer.  The targetII  begins data transfer.  When the data transfer is successfully completed, E  the target returns GOOD status and terminates the I/O process with ah  COMMAND COMPLETE message.  g"  7.8.3.2 Example of tagged queuing   I  An example of the execution of five queued I/O processes is described tosG  demonstrate how tagged queuing operates.  All tagged I/O processes are.J  from one initiator to a single logical unit of a single target.  The fiveF  I/O processes are defined in table 28.  The target is a direct-accessG  device.  At the time the I/O processes are first being executed, it is I  assumed that the actuator is in position to access logical block 10 000.   t?                 Table 28 - Commands in order received by targetUP  +===========-=============-=============-============-=============-==========+P  |  Command  |  Queue tag  |  Queue tag  |  Logical   |   Transfer  |  Status  |P  |           |   message   |    value    |   block    |    length   |          |P  |           |             |             |  address   |             |          |P  |-----------+-------------+-------------+------------+-------------+----------|P  |   READ    |    SIMPLE   |     01h     |   10 000   |    1 000    |  Queued  |P  |   READ    |    SIMPLE   |     02h     |      100   |        1    |  Queued  |P  |   READ    |   ORDERED   |     03h     |    1 000   |    1 000    |  Queued  |P  |   READ    |    SIMPLE   |     04h     |   10 000   |        1    |  Queued  |P  |   READ    |    SIMPLE   |     05h     |    2 000   |    1 000    |  Queued  |P  +=============================================================================+  cH  The optimum order would require that those blocks close to the actuatorJ  position be the first blocks accessed, followed by those increasingly farH  from the actuator position.  However, the command with queue tag 03h isE  an ordered I/O process, so that all simple I/O processes transferredgC  previously must be executed before, while all simple I/O processesYE  transferred after the ordered I/O process must be executed after the   ordered I/O process.h  sK  If a target supports an optimizing algorithm the actual order in which theo:  I/O processes are executed could be as shown in table 29.   <                    Table 29 - Commands in order of executionP  +===========-=============-=============-============-=============-==========+P  |  Command  |  Queue tag  |  Queue tag  |  Logical   |   Transfer  |  Status  |P  |           |   message   |    value    |   block    |    length   |          |P  |           |             |             |  address   |             |          |P  |-----------+-------------+-------------+------------+-------------+----------|P  |   READ    |    SIMPLE   |     01h     |   10 000   |    1 000    |  Queued  |P  |   READ    |    SIMPLE   |     02h     |      100   |        1    |  Queued  |P  |   READ    |   ORDERED   |     03h     |    1 000   |    1 000    |  Queued  |P  |   READ    |    SIMPLE   |     05h     |    2 000   |    1 000    |  Queued  |P  |   READ    |    SIMPLE   |     04h     |   10 000   |        1    |  Queued  |P  +=============================================================================+   J  I/O processes with queue tag values 01h and 02h are executed in the orderJ  received since the actuator is already in position to execute I/O processE  01h.  I/O process 02h must be executed before I/O process 04h or 05h H  because the ordered I/O process 03h was transmitted after I/O processesK  01h and 02h but before I/O processes 04h and 05h.  I/O process 03h is thenhC  executed after I/O process 02h.  The I/O processes 04h and 05h aretI  executed after the ordered I/O process 03h.  I/O process 05h is executed K  before I/O process 04h because the actuator is in position to access blockcK  2 000 after executing I/O process 03h.  I/O process 04h is executed last. e  tE  As an example of the operation of the HEAD OF QUEUE TAG I/O process,eK  consider that a new I/O process, identified by a HEAD OF QUEUE TAG messagedH  with a queue tag of 08h, is transmitted to the target while the orderedB  I/O process 03h is being executed.  The I/O process 03h continuesF  execution, but the new HEAD OF QUEUE TAG I/O process is placed in theH  queue for execution before all subsequent I/O processes.  In this case,G  the queue for execution after the ordered I/O process 03h was executedl#  would appear as shown in table 30.t  h@                 Table 30 - Modified by HEAD OF QUEUE TAG messageP  +===========-=============-=============-============-=============-==========+P  |  Command  |  Queue tag  |  Queue tag  |  Logical   |   Transfer  |  Status  |P  |           |   message   |    value    |   block    |    length   |          |P  |           |             |             |  address   |             |          |P  |-----------+-------------+-------------+------------+-------------+----------|P  |   READ    |   ORDERED   |     03h     |    1 000   |    1 000    | Executing|P  |   READ    |HEAD OF QUEUE|     08h     |        0   |        8    |  Queued  |P  |   READ    |    SIMPLE   |     05h     |    2 000   |    1 000    |  Queued  |P  |   READ    |    SIMPLE   |     04h     |   10 000   |        1    |  Queued  |P  +=============================================================================+  nJ  To obtain maximum performance gains using tagged queuing requires carefulF  implementation of the queuing algorithms in the target.  In addition,G  initiators should allow a maximum number of simple I/O processes to benF  executed with a minimum number of ordered I/O processes.  RESERVE andH  RELEASE commands, SET LIMITS commands, and appropriate software lockingH  conventions should be used to guarantee the proper relationship betweenF  the commands executed and the data stored on the peripheral devices. 4  These conventions are not defined by this standard.  o  7.9  Unit attention condition  iH  The target shall generate a unit attention condition for each initiatorG  on each valid logical unit whenever the target has been reset by a BUSeK  DEVICE RESET message, a hard reset condition, or by a power-on reset.  TherF  target shall also generate a unit attention condition on the affectedH  logical unit(s) for each initiator whenever one of the following events  occurs:4     a)     A removable medium may have been changed;M     b)     The mode parameters in effect for this initiator have been changede!            by another initiator; .>     c)     The version or level of microcode has been changed;L     d)     Tagged commands queued for this initiator were cleared by another            initiator;e)     e)     INQUIRY data has been changed;nM     f)     The mode parameters in effect for the initiator have been restoreds$            from non-volatile memory;?     g)     A change in the condition of a synchronized spindle;cO     h)     Any other event occurs that requires the attention of the initiator.   t	     NOTES O     56 Targets may queue unit attention conditions on logical units.  After theeO     first unit attention condition is cleared, another unit attention conditiondG     may exist (e.g. a power on condition followed by a microcode changey     condition).tL     57 See 7.5.3 for requirements concerning selection of an invalid logical	     unit.g  IH  The unit attention condition shall persist on the logical unit for eachH  initiator until that initiator clears the condition as described in the  following paragraphs.   K  If an INQUIRY command is received from an initiator to a logical unit withiD  a pending unit attention condition (before the target generates theG  contingent allegiance condition), the target shall perform the INQUIRYsJ  command and shall not clear the unit attention condition.  If the INQUIRYB  command is received after the target has generated the contingentK  allegiance condition for a pending unit attention condition, then the unitaI  attention condition on the logical unit shall be cleared, and the target #  shall perform the INQUIRY command.s  lD  If any other command is received after the target has generated theH  contingent allegiance condition for a pending unit attention condition,J  the unit attention condition on the logical unit shall be cleared, and ifJ  no other unit attention condition is pending the target shall perform theK  command.  If another unit attention condition is pending, the target shalltI  not perform the command and shall generate another contingent allegiancep  condition.I  dH  If a REQUEST SENSE command is received from an initiator with a pendingE  unit attention condition (before the target generates the contingente5  allegiance condition), then the target shall either:AH     a)     report any pending sense data and preserve the unit attention-            condition on the logical unit, or, M     b)     report the unit attention condition, may discard any pending senseuO            data, and clear the unit attention condition on the logical unit fors            that initiator.  iH  If the target has already generated the contingent allegiance conditionF  for the unit attention condition, the target shall perform the second  action listed above.   eK  If an initiator issues a command other than INQUIRY or REQUEST SENSE while J  a unit attention condition exists for that initiator (prior to generatingK  the contingent allegiance condition for the unit attention condition), thedF  target shall not perform the command and shall report CHECK CONDITIONH  status unless a higher priority status as defined by the target is also-  pending (e.g. BUSY or RESERVATION CONFLICT).c   G  If, after generating the contingent allegiance condition for a pending H  unit attention condition, the next command received from that initiatorE  on the logical unit is not REQUEST SENSE, then that command shall betE  performed and the unit attention condition shall be cleared for thataD  initiator on the logical unit and the sense data is lost (see 7.6).  iJ  If a target becomes a temporary initiator to issue a SEND command with anK  AEN bit of one, which informs the initiator (temporary target) of the unitrK  attention condition, and the SEND command completes with GOOD status, theneJ  the target shall clear the unit attention condition for that initiator on  the logical unit (see 7.5.5).     8  All device types  s  .  8.1 Model for all device typesq  iJ  This model describes some of the general characteristics expected of mostG  SCSI devices.  It is not intended to define any requirements nor is iteK  intended to alter any requirements defined elsewhere in this International F  Standard.  Clause 7 also contains model information pertaining to all  device types.  t  8.1.1 SCSI addressese  rI  There are two levels of addresses within the SCSI architecture: the SCSIoE  device address and the logical unit number or target routine number.   o  8.1.1.1 SCSI device address  =D  SCSI devices occupy (i.e. respond to) one address on the SCSI bus. H  Generally, the SCSI device provides a means (e.g. switches, jumpers) toI  select one of the eight available addresses (0 through 7).  This addresstD  is used during bus arbitration and selection or reselection of SCSID  devices.  Each device on the SCSI bus is assigned a unique address.  -K  Normally, the SCSI device address is set when the system is configured and H  it remains static thereafter.  Some systems and devices provide vendor-5  specific means to alter this address at other times.R     8.1.1.2 Logical units   G  Each target has one or more logical units, beginning with logical unit K  zero.  There is a maximum of eight logical units.  These logical units are I  usually mapped directly to peripheral devices, but they may be a portion=D  of a peripheral device or may comprise multiple peripheral devices.  tI  An initiator can determine whether a target implements a logical unit by K  issuing an INQUIRY command and examining the returned peripheral qualifierc  and peripheral device type.  mI  The concept of a logical unit is not defined for an initiator.  (An SCSI K  device may implement both the initiator role and the target role.  In this <  case logical unit(s) are defined only for the target role.)  e  8.1.1.3 Target routines  dI  An optional feature of the SCSI architecture permits each target to havelI  one or more target routines, beginning with target routine number zero. eH  There is a maximum of eight target routines.  These target routines areJ  processes that execute directly on the target and are not associated withE  a particular logical unit or peripheral device.  Target routines are D  addressed using the LUNTAR bit of the IDENTIFY message (see 6.6.7).  lI  Target routines are principally intended to return information about the B  target and the only valid commands are INQUIRY and REQUEST SENSE.  -/  8.1.2 Commands implemented by all SCSI devices    H  This standard defines four commands that all SCSI-2 targets implement -E  INQUIRY, REQUEST SENSE, SEND DIAGNOSTIC, and TEST UNIT READY.  These|J  commands are used to configure the system, to test targets, and to returnB  important information concerning errors and exception conditions.  0"  8.1.2.1 Using the INQUIRY command  PK  The INQUIRY command may be used by a system to determine the configuration=H  of the SCSI bus.  Target devices respond with information that includesK  their type and standard level and may include the vendor's identification,eH  model number and other useful information.  It is recommended that SCSII  targets be capable of returning this information (or whatever part of ittE  that is available) upon completing power-on initialization.  An SCSIdD  device may take longer to get certain portions of this information,<  especially if it retrieves the information from the medium.  r(  8.1.2.2 Using the REQUEST SENSE command  3I  Whenever a contingent allegiance condition (see 7.6) is established, thetJ  initiator that received the error should issue a REQUEST SENSE command toH  receive the sense data describing what caused the contingent allegianceJ  condition.  If the initiator issues some other command, the sense data is  lost.   *  8.1.2.3 Using the SEND DIAGNOSTIC command   F  The SEND DIAGNOSTIC command provides a means to request the target toF  perform a self test.  While the test is target specific, the means ofK  requesting the test is standardized and the response is simply GOOD statusr<  if all is well or CHECK CONDITION status if the test fails.  eG  The SEND DIAGNOSTIC command also provides other powerful features whensJ  used in conjunction with the RECEIVE DIAGNOSTIC RESULTS command, but this  capability is optional.  =*  8.1.2.4 Using the TEST UNIT READY command  =H  The TEST UNIT READY command is useful in that it allows an initiator toI  poll a logical unit until it is ready without the need to allocate spacekI  for returned data.  It is especially useful to check cartridge status of E  logical units with removable media.  Targets are expected to respond-E  promptly to indicate the current status of the device (i.e. a targetDG  should avoid lengthy disconnections in an attempt to respond with GOODE	  status).|   "  8.2 Commands for all device types  QK  The operation codes for commands that apply to all device types are listed 
  in table 31.|  R<                     Table 31 - Commands for all device typesI  +=====================================-============-======-============+=I  |  Command name                       | Operation  | Type |  Subclause |uI  |                                     |   code     |      |            |rI  |-------------------------------------+------------+------+------------| I  |  CHANGE DEFINITION                  |    40h     |   O  |   8.2.1    | I  |  COMPARE                            |    39h     |   O  |   8.2.2    |aI  |  COPY                               |    18h     |   O  |   8.2.3    |pI  |  COPY AND VERIFY                    |    3Ah     |   O  |   8.2.4    |cI  |  INQUIRY                            |    12h     |   M  |   8.2.5    |aI  |  LOG SELECT                         |    4Ch     |   O  |   8.2.6    |oI  |  LOG SENSE                          |    4Dh     |   O  |   8.2.7    |eI  |  MODE SELECT(6)                     |    15h     |   Z  |   8.2.8    |pI  |  MODE SELECT(10)                    |    55h     |   Z  |   8.2.9    |nI  |  MODE SENSE(6)                      |    1Ah     |   Z  |   8.2.10   |oI  |  MODE SENSE(10)                     |    5Ah     |   Z  |   8.2.11   |eI  |  READ BUFFER                        |    3Ch     |   O  |   8.2.12   |hI  |  RECEIVE DIAGNOSTIC RESULTS         |    1Ch     |   O  |   8.2.13   | I  |  REQUEST SENSE                      |    03h     |   M  |   8.2.14   |iI  |  SEND DIAGNOSTIC                    |    1Dh     |   M  |   8.2.15   |YI  |  TEST UNIT READY                    |    00h     |   M  |   8.2.16   |iI  |  WRITE BUFFER                       |    3Bh     |   O  |   8.2.17   | I  |----------------------------------------------------------------------|hI  |Key:  M = Command implementation is mandatory.                        |EI  |      O = Command implementation is optional.                         |fI  |      Z = Command implementation is device type specific.             |tI  +======================================================================+o  e  a   8.2.1 CHANGE DEFINITION command  5D  The CHANGE DEFINITION command (see table 32) modifies the operatingK  definition of the selected logical unit or target with respect to commands 5  from the selecting initiator or for all initiators. i  a:                       Table 32 - CHANGE DEFINITION commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (40h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |              Reserved                      |P  |-----+-----------------------------------------------------------------------|P  | 2   |                  Reserved                                    |  Save  |P  |-----+-----------------------------------------------------------------------|P  | 3   |Reserved|                  Definition parameter                        |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 8   |                           Parameter data length                       |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+   K  A save control bit (Save) of zero indicates that the target shall not saveaG  the operating definition.  A Save bit of one indicates that the targetC=  shall save the operating definition to non-volatile memory.    d7  The definition parameter field is defined in table 33.   m:                      Table 33 - Definition parameter field4  +============-====================================+4  |   Value    |  Meaning of definition parameter   |4  |------------+------------------------------------|4  |    00h     |  Use current operating definition  |4  |    01h     |  SCSI-1 operating definition       |4  |    02h     |  CCS operating definition          |4  |    03h     |  SCSI-2 operating definition       |4  |  04 - 3Fh  |  Reserved                          |4  |  40 - 7Fh  |  Vendor-specific                   |4  +=================================================+   Q     NOTE 57 The current operating definition parameter values establish operatingoL     definitions compatible with the appropriate SCSI specification.  Vendor-K     specific values are available for those applications where more complexeP     operation definition changes are required. Definitions supported by a deviceL     are returned in the implemented operating definition page (see 8.3.4.3).   E  The parameter data length field specifies the length in bytes of theeL  parameter data that shall be transferred from the initiator to the target. @  A parameter data length of zero indicates that no data shall beC  transferred.  This condition shall not be considered as an error. cI  Parameter data lengths greater than zero indicate the number of bytes ofa*  parameter data that shall be transferred.   '  The parameter data is vendor-specific.t   O     NOTE 58 The parameter data may be used to specify a password to validate anu      operating definition change.  eE  The CHANGE DEFINITION command causes one of the operating definitiont  modifications listed below:L     a)     Change the operating definition of a logical unit relative to theJ            initiator that issued the command.  In this case, the target isI            capable of maintaining an unique operating definition for eachiA            logical unit relative to each initiator in the system.eH     b)     Change the operating definition of the target relative to theJ            initiator that issued the command.  In this case, the target isI            capable of maintaining a unique operating definition, for eachnL            initiator in the system, that applies to all logical units of the            target.E     c)     The operating definition of a logical unit relative to all L            initiators in the system.  In this case, the target is capable ofK            maintaining an unique operating definition for each logical units4            relative to all initiators in the system.L     d)     The operating definition of the target relative to all initiatorsM            in the system.  In this case, the target is capable of maintainingt)            only one operating definition.   e	     NOTES O     59 This International Standard does not provide a direct means to determinecK     which of the above four methods has been implemented by the target.  AnsP     indirect means of determining which method is implemented exists in that theL     target is required to inform affected initiators of operating definition/     changes via the unit attention condition.   P     60 The final two mondifications listed above may result in incompatibilities<     if other initiators are operated below the SCSI-2 level.  DH  The operating definition is modified after successful completion of theJ  command.  A target shall consider the command successfully completed whenD  it detects the assertion of the ACK signal for the COMMAND COMPLETEF  message.  The initiator should verify the new operating definition byK  issuing an INQUIRY command requesting the implemented operating definitiont  page (see 8.3.4.1). c  eJ  It is permissible for an SCSI-2 device that has its definition changed to8  an SCSI-1 device to accept a CHANGE DEFINITION command.  gM     NOTE 61 The method of changing the operating definition is implementation Q     dependent.  Some implementations may require that the target's operating mode H     be reinitialized as if a power-up or hard-reset had occurred.  OtherQ     implementations may modify only those operating definitions that are affecteda%     by the CHANGE DEFINITION command.i  dF  If the CHANGE DEFINITION command is not executed successfully for anyH  reason, the operating definition shall remain the same as it was beforeE  the CHANGE DEFINITION command was attempted.  If it is impossible toeH  return to the previous operating definition, a unit attention condition"  shall be generated by the target.   H     NOTE 62 The present operating definition of the target may always beL     interrogated through the INQUIRY command.  When an SCSI-2 target has itsP     operating definition changed to CCS or SCSI-1, certain changes are needed toN     promote compatibility with preexisting SCSI-1 initiators.  The recommended     changes are as follows:nM     a)     The target should not initiate selections to other SCSI devices to.R            determine if any initiators support AEN.  The target should assume thatB            none are capable of receiving AEN and not issue an AEN.S     b)     The target should not generate extended contingent allegiance conditionsa3            by issuing an INITIATE RECOVERY message.iT     c)     If a REQUEST SENSE command with an allocation length of zero is received,=            the target should return four bytes of sense data.gK     d)     If an INQUIRY command is received, the returned data should haveCS            appropriate values in the ANSI version and response data format fields.  6            The features supported bits should be zero.U     e)     A change in the operating definition may change the vendor identifier, the=T            device type, the device model, the SCSI implementation level, the commandD            set, mode pages, and any other operating characteristics.  cK  After a power-on condition or a hard RESET condition, the target shall set-G  its initial operating definition to the last saved value, if saving is A  implemented, or its default value, if saving is not implemented.   |  8.2.2 COMPARE command  2K  The COMPARE command (see table 34) provides the means to compare data from K  one logical unit with another or the same logical unit in a manner similar   to the COPY command.    5                            Table 34 - COMPARE command P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (39h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |              Reserved             |  Pad   |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 4   |                           Parameter list length                       |P  |-----+---                                                                 ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 8   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+  i  cK  This command functions in the same manner as the COPY command, except that-K  the data from the source is compared on a byte-by-byte basis with the data K  from the destination.  The parameter list transferred to the target is the-@  same as for the COPY command.  This parameter list contains theI  information to identify the logical units involved in the comparison and-K  the length of the comparison.  (See 8.2.3 for additional information about|  the COPY command.)    H  If the comparison is unsuccessful, the command shall be terminated withJ  CHECK CONDITION status and the sense key shall be set to MISCOMPARE.  TheJ  remaining fields in the sense data shall be set as documented in the COPY	  command.-  -  8.2.3 COPY command-  -G  The COPY command (see table 35) provides a means to copy data from one I  logical unit to another or the same logical unit.  The logical unit that-H  receives and performs the COPY command is called the copy manager.  TheI  copy manager is responsible for copying data from a logical unit (source-I  device) to a logical unit (destination device).  These logical units may F  reside on different SCSI devices or the same SCSI device (in fact allG  three may be the same logical unit).  Some SCSI devices that implement8K  this command may not support copies to or from another SCSI device, or may I  not support third party copies (i.e. both the source and the destination--  logical units reside on other SCSI devices).l   3                             Table 35 - COPY command=P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (18h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |              Reserved             |  Pad   |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                           Parameter list length                       |P  |-----+---                                                                 ---|P  | 4   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+  r  nH  The pad bit (8.2.3.7) is used in conjunction with the cat bit (8.2.3.7)H  in the segment descriptors to define what action should be taken when aC  segment of the copy does not fit exactly into an integer number ofe  destination blocks. t  hE  The parameter list length field specifies the length in bytes of theoI  parameters that shall be sent during the DATA OUT phase of the command. s@  A parameter list length of zero indicates that no data shall beA  transferred. This condition shall not be considered as an error.y   K  The COPY parameter list (see table 36) begins with a four-byte header that K  contains the COPY function code and priority.  Following the header is onem  or more segment descriptors.    7                          Table 36 - COPY parameter listtP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+============================================+==========================|P  | 0   |         COPY function code                 |         Priority         |P  |-----+-----------------------------------------------------------------------|P  | 1   |                           Vendor-specific                             |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |=====+=======================================================================|P  |     |                         Segment descriptor(s)                         |P  |=====+=======================================================================|P  | 0   |                           Segment descriptor 0                        |P  |- - -+---                                                                 ---|P  | n   |                     (See specific table for length.)                  |P  |-----+-----------------------------------------------------------------------|P  |     |                                 .                                     |P  |     |                                 .                                     |P  |-----+-----------------------------------------------------------------------|P  | 0   |                           Segment descriptor x                        |P  |- - -+---                                                                 ---|P  | n   |                     (See specific table for length.)                  |P  +=============================================================================+  C  1G  The COPY function code field defines a specific format for the segmentdI  descriptors.  The COPY function codes are defined in table 37.  A targeto9  need not support all function codes for its device type.m   7                          Table 37 - COPY function codes O  +===============================================-========-==========-========+ O  |       Peripheral device type                  |  COPY  | Segment  |        |FO  |-----------------------------------------------|function|descriptor|        |nO  | Source                | Destination           |  code  |  table   |Comments|aO  |-----------------------+-----------------------+--------+----------+--------| O  | Block devices         | Stream devices        |    0   |    38    |        |hO  | (Device types 0,4,5,7)| (Device types 1,2,3,9)|        |          |        |uO  | Stream devices        | Block devices         |    1   |    38    |(Note 3)|cO  | (Device types 1,3,9)  | (Device types 0,4,5,7)|        |          |        | O  | Block devices         | Block devices         |    2   |    39    |(Note 3)|nO  | (Device types 0,4,5,7)| (Device types 0,4,5,7)|        |          |        | O  | Stream devices        | Stream devices        |    3   |    40    |        |tO  | (Device types 1,3,9)  | (Device types 1,2,3,9)|        |          |        |TO  | Sequential-access     | Sequential-access     |    4   |    41    | Image  | O  | (Device type 1)       | (Device type 1)       |        |          |  copy  |nO  |----------------------------------------------------------------------------|tO  |  NOTES                                                                     | O  |   1 COPY function codes 05h - 0Fh are reserved.                            | O  |   2 COPY function codes 10h - 1Fh are vendor-specific.                     |zO  |   3 When using the COMPARE command the destination block device may be a   |iO  |      CD-ROM device or an optical-memory device that uses read-only media.  |eO  |   4 See 8.2.5.1 for peripheral device type definitions.                    |cO  +============================================================================+e     sG  The priority field of the COPY parameter list establishes the relativepK  priority of this COPY command to other commands being executed by the sameMB  target.  All other commands are assumed to have a priority of 1. F  Priority 0 is the highest priority, with increasing values indicating  lower priorities.   J  The segment descriptor formats are determined by the COPY function code. K  The segment descriptor format used for block devices (i.e. write-once, CD-=H  ROM, optical-memory, and direct-access devices) shall be the same.  TheA  segment descriptor format used for stream devices (i.e. printer, :  processor, communications, and sequential-access devices)I   shall be the same.  Thus a copy operation from a write-once device to a K  printer device uses the same segment descriptor format as a copy operation-K  from a direct-access device to a sequential-access device (see table 37). |J  The segment descriptor formats are described in 8.2.3.3 through 8.2.3.6. A  A maximum of 256 segment descriptors are permitted.  The segment-E  descriptors are identified by ascending numbers beginning with zero.    4  8.2.3.1 Errors detected by the managing SCSI device  -I  Two classes of exception conditions may occur during execution of a COPY J  command.  The first class consists of those exception conditions detectedF  by the SCSI device that received the COPY command and is managing theH  execution of the command.  These conditions include parity errors whileI  transferring the COPY command and status byte, invalid parameters in the|E  COPY command, invalid segment descriptors, and inability of the SCSI K  device controlling the COPY functions to continue operating.  In the event-I  of such an exception condition, the SCSI device managing the COPY shall: B     a)     terminate the COPY command with CHECK CONDITION status.J     b)     set the valid bit in the sense data to one.  The segment numberM            shall contain the number of the segment descriptor being processed-J            at the time the exception condition is detected.  The sense keyN            shall contain the sense key code describing the exception conditionL            (i.e. not COPY ABORTED).  The information field shall contain theG            difference between the number of blocks field in the segment=O            descriptor being processed at the time of the failure and the numbermH            of blocks successfully copied.  This number is the residue ofC            unprocessed blocks remaining for the segment descriptor.   f$  8.2.3.2 Errors detected by a target  tH  The second class of errors consists of exception conditions detected byD  the SCSI device transferring data at the request of the SCSI deviceJ  managing the transfer.  The SCSI device managing the COPY command detectsI  exception conditions by receiving CHECK CONDITION status from one of thesC  SCSI devices it is managing.  It then shall recover the sense dataI)  associated with the exception condition.t  ID  The SCSI device managing the COPY command may also be the source orK  destination SCSI device (or both).  It shall distinguish between a failuremG  of the management of the COPY and a failure of the data transfer being G  requested. It shall then create the appropriate sense data internally.n  eH  After recovering the sense data associated with the detected error, the-  SCSI device managing the COPY command shall:iB     a)     terminate the COPY command with CHECK CONDITION status.L     b)     The valid bit in the sense data shall be set to one.  The segmentJ            number shall contain the number of the segment descriptor beingJ            processed at the time the exception condition is detected.  TheO            sense key shall be set to COPY ABORTED.  The information field shallnK            contain the difference between the number of blocks field in the L            segment descriptor being processed at the time of the failure andH            the number of blocks successfully copied.  This number is theN            residue of unprocessed blocks remaining for the segment descriptor.   K  The first byte of the command-specific information field shall specify the=K  starting byte number, relative to the first byte of sense data, of an area J  that contains (unchanged) the source logical unit's status byte and senseI  data.  A zero value indicates that no status byte or sense data is beingl&  returned for the source logical unit.   H  The second byte of the command-specific information field shall specifyJ  the starting byte number, relative to the first byte of sense data, of anJ  area that contains (unchanged) the destination logical unit's status byteJ  and sense data.  A zero value indicates that no status byte or sense data4  is being returned for the destination logical unit.  -'  8.2.3.3 COPY function code 00h and 01h    H  The format for the segment descriptors for COPY transfers between blockJ  and stream devices is specified in table 38.  This format is required forH  COPY function codes 00h or 01h.  The segment descriptor may be repeatedJ  up to 256 times within the parameter list length specified in the command  descriptor block.  =H        Table 38 - Segment descriptor for COPY function codes 00h and 01hP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+==========================+========+========+==========================|P  | 0   | Source address           |Reserved|  Cat   |     Source LUN           |P  |-----+--------------------------+-----------------+--------------------------|P  | 1   | Destination address      |    Reserved     |     Destination LUN      |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                        Stream device block length               ---|P  | 3   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 4   | (MSB)                                                                 |P  |-----+---                        Block device number of blocks            ---|P  | 7   |                                                                 (LSB) |P  |--- -+-----------------------------------------------------------------------|P  | 8   | (MSB)                                                                 |P  |--- -+---                        Block device logical block address       ---|P  | 11  |                                                                 (LSB) |P  +=============================================================================+      E  The source address and source LUN fields specify the SCSI bus ID and=I  logical unit of the device to copy the data from for this segment of the I  COPY command. The destination address and destination LUN fields specify=I  the SCSI bus ID and logical unit to copy the data to for this segment of I  the COPY command.  Some SCSI devices may not support third-party COPY in H  which the copying SCSI device is not the source or destination device. F  Some SCSI devices only support COPY within the SCSI device and not toH  other SCSI devices.  If an unsupported COPY operation is requested, theJ  command shall be terminated with CHECK CONDITION status and the sense keyI  shall be set to ILLEGAL REQUEST with an additional sense code of INVALID-'  FIELD IN PARAMETER LIST (see 8.2.3.1).-  -G  A catenate (Cat) bit (optional) of one indicates that the COPY managerrH  shall catenate the last source block of a segment with the first sourceH  block of the next segment if the last source block does not end exactlyJ  at the end of the destination block.  The definition of a cat bit of zeroK  depends on the setting of the pad bit in the command descriptor block (seec
  8.2.3.7).   K  The stream device block-length field specifies the block length to be usedcL  on the stream device logical unit during this segment of the COPY command. D  If the SCSI device managing the COPY knows this block length is notK  supported, the command shall be terminated with CHECK CONDITION status and=G  the sense key shall be set to ILLEGAL REQUEST with an additional senseOJ  code of INVALID FIELD IN PARAMETER LIST.  If the block length is found toK  be invalid while executing a read or write operation to the stream device, J  the command shall be terminated with CHECK CONDITION status and the sense0  key shall be set to COPY ABORTED (see 8.2.3.2).  dJ  The block device number of blocks field specifies the number of blocks inE  the current segment to be copied.  A value of zero indicates that no -  blocks shall be transferred in this segment.    D  The block device logical block address field specifies the starting<  logical block address on the logical unit for this segment.     8.2.3.4 COPY function code 02h    F  The format for the segment descriptors for COPY transfers among blockD  devices is specified in table 39.  This format is required for COPYK  function code 02h.  The segment descriptor may be repeated up to 256 timeseE  within the parameter list length specified in the command descriptors  block.q  tD             Table 39 - Segment descriptor for COPY function code 02hP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+==========================+========+========+==========================|P  | 0   | Source address           |   DC   |  Cat   | Source LUN               |P  |-----+--------------------------+-----------------+--------------------------|P  | 1   | Destination address      |   Reserved      | Destination LUN          |P  |-----+-----------------------------------------------------------------------|P  | 2   |                              Reserved                                 |P  |-----+-----------------------------------------------------------------------|P  | 3   |                              Reserved                                 |P  |-----+-----------------------------------------------------------------------|P  | 4   | (MSB)                                                                 |P  |- - -+---                Number of blocks                                 ---|P  | 7   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 8   | (MSB)                                                                 |P  |- - -+---                Source logical block address                     ---|P  | 11  |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 12  | (MSB)                                                                 |P  |- - -+---                Destination logical block address                ---|P  | 15  |                                                                 (LSB) |P  +=============================================================================+  f  CG  See 8.2.3.3 for definitions of the source address, the source LUN, thee:  destination address, the destination LUN, and CAT fields.  iI  A destination count (DC) bit of zero indicates that the number of blocks I  field refers to the source logical unit.  A DC bit of one indicates thateD  the number of blocks field refers to the destination logical unit.   f@  The number of blocks field specifies the number of blocks to beI  transferred to or from (depending on the DC bit) the block device duringnA  this segment.  A value of zero indicates that no blocks shall beC
  transferred.s  uF  The source logical block address field specifies the starting logical+  block address on the source block device. f  eK  The destination logical block address field specifies the starting logicaln/  block address on the destination block device.a  c  8.2.3.5 COPY function code 03hi  tG  The format for the segment descriptors for COPY transfers among streamiD  devices is specified by table 40.  This format is required for COPYK  function code 03h.  The segment descriptor may be repeated up to 256 timestE  within the parameter list length specified in the command descriptoro  block.i  uD             Table 40 - Segment descriptor for COPY function code 03hP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+==========================+========+========+==========================|P  | 0   | Source address           |   DC   |  Cat   | Source LUN               |P  |-----+--------------------------+-----------------+--------------------------|P  | 1   | Destination address      |   Reserved      | Destination LUN          |P  |-----+-----------------------------------------------------------------------|P  | 2   |                              Reserved                                 |P  |-----+-----------------------------------------------------------------------|P  | 3   |                              Reserved                                 |P  |-----+-----------------------------------------------------------------------|P  | 4   | (MSB)                                                                 |P  |-----+---                        Source block length                      ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   | (MSB)                                                                 |P  |-----+---                        Destination block length                 ---|P  | 7   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 8   | (MSB)                                                                 |P  |- - -+---                        Number of blocks                         ---|P  | 11  |                                                                 (LSB) |P  +=============================================================================+      G  See 8.2.3.3 for definitions of the source address, the source LUN, thee:  destination address, the destination LUN, and CAT fields.  cI  A destination count (DC) bit of zero indicates that the number of blocksdI  field refers to the source logical unit.  A DC bit of one indicates thateD  the number of blocks field refers to the destination logical unit.    G  The source block length field specifies the block-length of the sourceeE  device for this segment of the COPY.  A zero in this field indicatesoH  variable block-length.  For non-zero values, this field shall match the%  logical unit's actual block-length. w  iK  If block-length mismatches are detected prior to the beginning of the read E  operation by the SCSI device managing the COPY, the command shall behG  terminated with CHECK CONDITION status.  The sense key shall be set to=F  ILLEGAL REQUEST and the additional sense code shall be set to INVALID(  FIELD IN PARAMETER LIST (see 8.2.3.1).   |E  If the mismatches are detected during the read operation by the COPY=K  manager, the command shall be terminated with CHECK CONDITION status.  TheuJ  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.  -I  The destination block-length field specifies the block length to be usedtK  on the destination logical unit during the COPY.  Destination block length-E  mismatches are handled in an analogous manner as source block length   mismatches.   @  The number of blocks field specifies the number of blocks to beH  transferred to or from (depending on the DC bit) the device during thisI  segment.  A value of zero indicates that no blocks shall be transferred.-  -  8.2.3.6 COPY function code 04h-   H  The format for the segment descriptors for image COPY transfers betweenD  sequential-access devices is specified in table 41.  This format isD  required for COPY function code 04h.  The segment descriptor may beK  repeated up to 256 times within the parameter list length specified in the-  command descriptor block.  -D             Table 41 - Segment descriptor for COPY function code 04hP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+==========================+=================+==========================|P  | 0   | Source address           |   Reserved      | Source LUN               |P  |-----+--------------------------+-----------------+--------------------------|P  | 1   | Destination address      |   Reserved      | Destination LUN          |P  |-----+-----------------------------------------------------------------------|P  | 2   |                              Count                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                                                                       |P  |- - -+---                           Reserved                              ---|P  | 7   |                                                                       |P  |-----+-----------------------------------------------------------------------|P  | 8   |                                                                       |P  |- - -+---                           Vendor-specific                       ---|P  | 11  |                                                                       |P  +=============================================================================+  k  nG  See 8.2.3.3 for definitions of the source address, the source LUN, theo:  destination address, the destination LUN, and CAT fields.  CG  The image mode COPY command copies an exact image of the source devicehD  medium to the destination device medium, beginning at their current@  positions. The copy function terminates when the source device:J     a)     encounters an end-of-partition as defined by the source device;J     b)     encounters an end-of-data as defined by the source device (i.e."            BLANK CHECK sense key);J     c)     has copied the number of consecutive filemarks specified in theH            count field from the source device to the destination device;O     d)     has copied the number of consecutive setmarks specified in the countaN            field from the source device to the destination device, if the RSmkG            bit in the device configuration page (see 10.3.3.1) is one. d  sJ  A count field of zero indicates that the COPY command shall not terminateH  due to any number of consecutive filemarks or setmarks.  Other error orA  exception conditions (e.g. early-warning end-of-partition on the E  destination device) may cause the COPY command to terminate prior to J  completion.  In such cases, it is not possible to calculate a residue, so>  the information field in the sense data shall be set to zero.   %  4s Copies with unequal block lengths=  =H  When copying data between two devices with unequal block lengths, it isC  possible for the last source block to not completely fill the last E  destination block for one or more segments in the COPY command.  Two F  optional bits are defined to assist in controlling the copy manager'sF  actions in this circumstance.  The Pad bit (in the command descriptorK  block) and the Cat bit (in each applicable segment descriptor) are defined-
  in table 42.-  -:                      Table 42 - Pad and cat bit definitionP  +=====-=====-=================================================================+P  | Pad | Cat | COPY manager's action                                           |P  |-----+-----+-----------------------------------------------------------------|P  |  0  |  0  | On inexact segments, it is device specific whether the COPY     |P  |     |     | manager rejects the COPY command with CHECK CONDITION status and|P  |     |     | ILLEGAL REQUEST sense key, the COPY manager writes or accepts   |P  |     |     | short blocks (variable-block mode on sequential-access devices),|P  |     |     | or the COPY manager adds pad characters (00h) to the destination|P  |     |     | block or strips pad characters from the source block.           |P  |     |     |                                                                 |P  |  1  |  0  | On inexact segments, the COPY manager shall add pad characters  |P  |     |     | (00h) to the destination block to completely fill the block, or |P  |     |     | it shall strip pad characters from the source block, always     |P  |     |     | stopping at the end of a complete block.                        |P  |     |     |                                                                 |P  |  X  |  1  | The COPY manager shall always write or read complete blocks.  On|P  |     |     | inexact segments, the remainder of the block contains data from |P  |     |     | the next segment.  This code is not valid in the last segment of|P  |     |     | the COPY command.                                               |P  +=============================================================================+  b  kQ     NOTE 63 Use of pad characters is intended to assist in managing COPY commandseO     between devices of different block lengths where partial-block residues may H     occur.  The initiator who issued the COPY command is responsible forI     management of these pad areas (i.e. remembering where they are).  OneaJ     possible method is to write the COPY parameter list information to theO     destination medium prior to issuing the COPY command for backup and to read C     this information prior to issuing the COPY command for restore.s  e  8.2.4 COPY AND VERIFY command   I  The COPY AND VERIFY command (see table 43) performs the same function asnH  the COPY command, except that a verification of the data written to theF  destination logical unit is performed after the data is written.  TheE  parameter list transferred to the target is the same as for the COPYeF  command. This parameter list contains the information to identify theJ  logical units involved in the copy and the length of the copy.  See 8.2.33  for additional information about the COPY command.-  =9                        Table 43 - COPY AND VERIFY command|P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (3Ah)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |        Reserved          | BytChk |  Pad   |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 4   |                           Parameter list length                       |P  |-----+---                                                                 ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 8   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+  n  dE  A byte check (BytChk) bit of zero causes a medium verification to beCJ  performed with no data comparison.  A BytChk bit of one causes a byte-by-G  byte comparison of data written on the destination medium and the data K  transferred from the source medium.  If the comparison is unsuccessful forfJ  any reason, the copy manager shall return CHECK CONDITION status with theK  sense key set to MISCOMPARE.  The remaining fields in the sense data shallz*  be set as documented in the COPY command.  l  8.2.5 INQUIRY command  .G  The INQUIRY command (see table 44) requests that information regardingfJ  parameters of the target and its attached peripheral device(s) be sent toE  the initiator.  An option allows the initiator to request additionale<  information about the target or logical unit (see 8.2.5.2).   5                            Table 44 - INQUIRY command P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (12h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |                  Reserved         |  EVPD  |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Page code                                   |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Allocation length                           |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+     |I  An enable vital product data (EVPD) bit of one specifies that the target H  shall return the optional vital product data specified by the page codeJ  field.  If the target does not support vital product data and this bit isJ  set to one, the target shall return CHECK CONDITION status with the senseI  key set to ILLEGAL REQUEST and an additional sense code of INVALID FIELDs  IN CDB.  eH  An EVPD bit of zero specifies that the target shall return the standardK  INQUIRY data.  If the page code field is not zero, the target shall return H  CHECK CONDITION status with the sense key set to ILLEGAL REQUEST and an/  additional sense code of INVALID FIELD IN CDB.-  -K  The page code field specifies which page of vital product data information %  the target shall return (see 8.3.4).    F  The INQUIRY command shall return CHECK CONDITION status only when the2  target cannot return the requested INQUIRY data.    Q     NOTE 64 The INQUIRY data should be returned even though the peripheral device-(     may not be ready for other commands.   H  If an INQUIRY command is received from an initiator with a pending unitD  attention condition (i.e. before the target reports CHECK CONDITIONJ  status), the target shall perform the INQUIRY command and shall not clear(  the unit attention condition (see 7.9).  =	     NOTES=N     65 The INQUIRY command is typically used by the initiator after a reset orO     power-up condition to determine the device types for system configuration.  P     To minimize delays after a reset or power-up condition, the standard INQUIRYO     data should be available without incurring any media access delays.  If the Q     target does store some of the INQUIRY data on the device, it may return zerosaN     or ASCII spaces (20h) in those fields until the data is available from the     device.tL     66 The INQUIRY data may change as the target executes its initializationM     sequence or in response to a CHANGE DEFINITION command.  For example, thedO     target may contain a minimum command set in its non-volatile memory and maybP     load its final firmware from the device when it becomes ready.  After it hasI     loaded the firmware, it may support more options and therefore returni@     different supported options information in the INQUIRY data.     8.2.5.1 Standard INQUIRY data  dE  The standard INQUIRY data (see table 45) contains 36 required bytes,tG  followed by a variable number of vendor-specific parameters.  Bytes 56pD  through 95, if returned, are reserved for future standardization.    i;                     Table 45 - Standard INQUIRY data formatlP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+==========================+============================================|P  | 0   | Peripheral qualifier     |           Peripheral device type           |P  |-----+-----------------------------------------------------------------------|P  | 1   |  RMB   |                  Device-type modifier                        |P  |-----+-----------------------------------------------------------------------|P  | 2   |   ISO version   |       ECMA version       |  ANSI-approved version   |P  |-----+-----------------+-----------------------------------------------------|P  | 3   |  AENC  | TrmIOP |     Reserved    |         Response data format      |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Additional length (n-4)                     |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   | RelAdr | WBus32 | WBus16 |  Sync  | Linked |Reserved| CmdQue | SftRe  |P  |-----+-----------------------------------------------------------------------|P  | 8   | (MSB)                                                                 |P  |- - -+---                        Vendor identification                    ---|P  | 15  |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 16  | (MSB)                                                                 |P  |- - -+---                        Product identification                   ---|P  | 31  |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 32  | (MSB)                                                                 |P  |- - -+---                        Product revision level                   ---|P  | 35  |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 36  |                                                                       |P  |- - -+---                        Vendor-specific                          ---|P  | 55  |                                                                       |P  |-----+-----------------------------------------------------------------------|P  | 56  |                                                                       |P  |- - -+---                        Reserved                                 ---|P  | 95  |                                                                       |P  |=====+=======================================================================|P  |     |                       Vendor-specific parameters                      |P  |=====+=======================================================================|P  | 96  |                                                                       |P  |- - -+---                        Vendor-specific                          ---|P  | n   |                                                                       |P  +=============================================================================+  =   H  The peripheral qualifier and peripheral device-type fields identify theF  device currently connected to the logical unit.  If the target is notI  capable of supporting a device on this logical unit, this field shall be H  set to 7Fh (peripheral qualifier set to 011b and peripheral device typeF  set to 1Fh).  The peripheral qualifier is defined in table 46 and the/  peripheral device type is defined in table 47.+  -7                         Table 46 - Peripheral qualifier-P  +=========-===================================================================+P  |Qualifier|  Description                                                      |P  |---------+-------------------------------------------------------------------|P  |   000b  |  The specified peripheral device type is currently connected to   |P  |         |  this logical unit.  If the target cannot determine whether or    |P  |         |  not a physical device is currently connected, it shall also use  |P  |         |  this peripheral qualifier when returning the INQUIRY data.       |P  |         |  This peripheral qualifier does not mean that the device is ready |P  |         |  for access by the initiator.                                     |P  |         |                                                                   |P  |   001b  |  The target is capable of supporting the specified peripheral     |P  |         |  device type on this logical unit;  however, the physical device  |P  |         |  is not currently connected to this logical unit.                 |P  |         |                                                                   |P  |   010b  |  Reserved                                                         |P  |         |                                                                   |P  |   011b  |  The target is not capable of supporting a physical device on     |P  |         |  this logical unit. For this peripheral qualifier the peripheral  |P  |         |  device type shall be set to 1Fh to provide compatibility with    |P  |         |  previous versions of SCSI.  All other peripheral device type     |P  |         |  values are reserved for this peripheral qualifier.               |P  |         |                                                                   |P  |   1XXb  |  Vendor-specific                                                  |P  +=============================================================================+  8  58                        Table 47 - Peripheral device typeP  +=============-===============================================================+P  |    Code     |  Description                                                  |P  |-------------+---------------------------------------------------------------|P  |     00h     |  Direct-access device (e.g. magnetic disk)                    |P  |     01h     |  Sequential-access device (e.g. magnetic tape)                |P  |     02h     |  Printer device                                               |P  |     03h     |  Processor device                                             |P  |     04h     |  Write-once device (e.g. some optical disks)                  |P  |     05h     |  CD-ROM device                                                |P  |     06h     |  Scanner device                                               |P  |     07h     |  Optical memory device (e.g. some optical disks)              |P  |     08h     |  Medium changer device (e.g. jukeboxes)                       |P  |     09h     |  Communications device                                        |P  |  0Ah - 0Bh  |  Defined by ASC IT8 (Graphic arts pre-press devices)          |P  |  0Ch - 1Eh  |  Reserved                                                     |P  |     1Fh     |  Unknown or no device type                                    |P  +=============================================================================+  r   F  A removable medium (RMB) bit of zero indicates that the medium is notE  removable.  A RMB bit of one indicates that the medium is removable.    G  The device-type modifier field was defined in SCSI-1 to permit vendor-sI  specific qualification codes of the device type.  This field is retainedIG  for compatibility with SCSI-1.  Targets that do not support this fieldr  should return a value of zero..  fF  The usage of non-zero code values in the ISO version and ECMA versionI  fields are defined by the International Organization for StandardizationeK  and the European Computer Manufacturers Association, respectively.  A zeropI  code value in these fields shall indicate that the target does not claim)H  compliance to the ISO version of SCSI (ISO 9316) or the ECMA version ofH  SCSI (ECMA-111). It is possible to claim compliance to more than one of  these SCSI standards.  rJ  The ANSI-approved version field indicates the implemented version of this3  International Standard and is defined in table 48.   i8                         Table 48 - ANSI-approved versionP  +=============-===============================================================+P  |    Code     |  Description                                                  |P  |-------------+---------------------------------------------------------------|P  |      0h     |  The device might or might not comply to an ANSI-approved     |P  |             |  standard.                                                    |P  |      1h     |  The device complies to ANSI X3.131-1986 (SCSI-1).            |P  |      2h     |  The device complies to this version of SCSI.  This code is   |P  |             |  reserved to designate this standard upon approval by ANSI.   |P  |   3h - 7h   |  Reserved                                                     |P  +=============================================================================+  e  pI  The asynchronous event notification capability (AENC) bit indicates thatmF  the device supports the asynchronous event notification capability as  defined in 7.5.5. hO     a)     Processor device-type definition:  An AENC bit of one indicates that J            the processor device is capable of accepting asynchronous eventJ            notifications. An AENC bit of zero indicates that the processorD            device does not support asynchronous event notifications.9     b)     All other device-types:  This bit is reserved.e  vF  A terminate I/O process (TrmIOP) bit of one indicates that the deviceJ  supports the TERMINATE I/O PROCESS message as defined in 6.6.22.  A valueE  of zero indicates that the device does not support the TERMINATE I/O   PROCESS message.   |J  A response data format value of zero indicates the INQUIRY data format isG  as specified in SCSI-1.  A response data format value of one indicates=A  compatibility with some products that were designed prior to the J  development of this standard (i.e. CCS).  A response data format value ofE  two indicates that the data shall be in the format specified in this J  International Standard.  Response data format values greater than two are
  reserved.  -E  The additional length field shall specify the length in bytes of therI  parameters.  If the allocation length of the command descriptor block is-I  too small to transfer all of the parameters, the additional length shall +  not be adjusted to reflect the truncation.   sD  A relative addressing (RelAdr) bit of one indicates that the deviceJ  supports the relative addressing mode for this logical unit.  If this bitI  is set to one, the linked command (Linked) bit shall also be set to one;-K  since relative addressing can only be used with linked commands.  A RelAdr J  bit of zero indicates the device does not support relative addressing for  this logical unit.-  -I  A wide bus 32 (Wbus32) bit of one indicates that the device supports 32-eI  bit wide data transfers.  A value of zero indicates that the device does-(  not support 32-bit wide data transfers.   I  A wide bus 16 (Wbus16) bit of one indicates that the device supports 16-RI  bit wide data transfers.  A value of zero indicates that the device does-(  not support 16-bit wide data transfers.   Q     NOTE 67 If the values of both the Wbus16 and Wbus32 bits are zero, the deviceV,     only supports 8-bit wide data transfers.  1C  A synchronous transfer (Sync) bit of one indicates that the device(J  supports synchronous data transfer.  A value of zero indicates the device,  does not support synchronous data transfer.   H  A linked command (Linked) bit of one indicates that the device supportsF  linked commands for this logical unit.  A value of zero indicates the?  device does not support linked commands for this logical unit.|  -I  A command queuing (CmdQue) bit of one indicates that the device supports I  tagged command queuing for this logical unit.  A value of zero indicates J  the device does not support tagged command queuing for this logical unit.   K  A soft reset (SftRe) bit of zero indicates that the device responds to the H  RESET condition with the hard RESET alternative (see 6.2.2.1).  A SftReJ  bit of one indicates that the device responds to the RESET condition with*  the soft RESET alternative (see 6.2.2.2).   I  ASCII data fields shall contain only graphic codes (i.e. code values 20h K  through 7Eh).  Left-aligned fields shall place any unused bytes at the end-H  of the field (highest offset) and the unused bytes shall be filled withK  space characters (20h).  Right-aligned fields shall place any unused bytes H  at the start of the field (lowest offset) and the unused bytes shall be$  filled with space characters (20h).   C  The vendor identification field contains eight bytes of ASCII data=G  identifying the vendor of the product.  The data shall be left aligned   within this field.  -  cQ     NOTE 68 It is intended that this field provide a unique vendor identification=G     of the manufacturer of the SCSI device.  In the absence of a formal L     registration procedure, X3T9.2 maintains a list of vendor identificationD     codes in use.  Vendors are requested to voluntarily submit theirQ     identification codes to X3T9.2 to prevent duplication of codes (see annex E).=  =I  The product identification field contains sixteen bytes of ASCII data aseJ  defined by the vendor.  The data shall be left-aligned within this field.   F  The product revision level field contains four bytes of ASCII data asJ  defined by the vendor.  The data shall be left-aligned within this field.  a  8.2.5.2 Vital product datae  hC  Implementation of vital product data is optional.  The informationiE  returned consists of configuration data (e.g. vendor identification,-H  product identification, model, serial number), manufacturing data (e.g.F  plant and date of manufacture), field replaceable unit data and other#  vendor- or device-specific data.      I  The initiator requests the vital product data information by setting the-J  EVPD bit to one and specifying the page code of the desired vital productJ  data (see 8.3.4).  If the target does not implement the requested page itF  shall return CHECK CONDITION status.  The a sense key shall be set toF  ILLEGAL REQUEST and the additional sense code shall be set to INVALID  FIELD IN CDB.  a	     NOTES M     69 The target should have the ability to execute the INQUIRY command eveneP     when a device error occurs that prohibits normal command execution.  In suchM     a case, CHECK CONDITION status should be returned for commands other than L     INQUIRY or REQUEST SENSE.  The sense data returned may contain the fieldM     replaceable unit code.  The vital product data should be obtained for thet-     failing device using the INQUIRY command. G     70 This International Standard defines a format that allows device- P     independent initiator software to display the vital product data returned byI     the INQUIRY command.  For example, the initiator may display the data N     associated for the field replaceable unit returned in the sense data.  TheP     contents of the data may be vendor-specific; therefore, it may not be usable2     without detailed information about the device.L     71 This International Standard does not define the location or method ofJ     storing the vital product data.  The retrieval of the data may requireM     completion of initialization operations within the device that may inducesH     delays before the data is available to the initiator.  Time-criticalM     requirements are an implementation consideration and are not addressed in       this International Standard.     8.2.6 LOG SELECT command   |I  The LOG SELECT command (see table 49) provides a means for the initiator=E  to manage statistical information maintained by the device about theeD  device or its logical units.  Targets that implement the LOG SELECTG  command shall also implement the LOG SENSE command.  Structures in the K  form of log parameters within log pages are defined as a way to manage the-G  log data. The LOG SELECT command provides for sending zero or more loggH  pages during a DATA OUT phase.  This International Standard defines theF  format of the log pages, but does not define the exact conditions and  events that are logged.   6                          Table 49 - LOG SELECT commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (4Ch)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |              Reserved    |  PCR   |   SP   |P  |-----+-----------------------------------------------------------------------|P  | 2   |        PC       |         Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   | (MSB)                                                                 |P  |-----+---                        Parameter list length                    ---|P  | 8   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+  -  =G  A parameter code reset (PCR) bit of one and a parameter list length of E  zero shall cause all implemented parameters to be set to the target-|C  defined default values (e.g. zero).  If the PCR bit is one and the-K  parameter list length is greater than zero, the command is terminated withpK  CHECK CONDITION status.  The sense key shall be set to ILLEGAL REQUEST and K  the additional sense code shall be set to INVALID FIELD IN CDB.  A PCR bitS>  of zero specifies that the log parameters shall not be reset.   F  A save parameters (SP) bit of one indicates that after performing theE  specified LOG SELECT operation the target shall save to non-volatiledJ  memory all parameters identified as savable by the DS bit in the log pageF  (see 8.3.2).  A SP bit of zero specifies that parameters shall not be  saved.r  uJ  Saving of log parameters is optional and indicated for each log parameterK  by the DS bit in the page.  Log parameters may be saved at vendor-specific G  times subject to the TSD bit (see 8.3.2) in the log parameter.  If thesI  target does not implement saved parameters for any log parameter and thesK  SP bit is set to one, the command shall be terminated with CHECK CONDITIONeK  status.  The sense key shall be set to ILLEGAL REQUEST, and the additional )  sense code set to INVALID FIELD IN CDB. i  eK  It is not an error to set the SP bit to one and to set the DS bit of a log B  parameter to one.  In this case, the parameter value for that log  parameter is not saved.  cG  The page control (PC) field defines the type of parameter values to bee:  selected.  The page control field is defined in table 50.  U6                          Table 50 - Page control fieldK     +=======-==============================-==============================+wK     | Type  |  LOG SELECT parameter values |  LOG SENSE parameter values  |oK     |-------+------------------------------+------------------------------| K     |  00b  |  Current threshold values    |  Threshold values            |aK     |  01b  |  Current cumulative values   |  Cumulative values           |tK     |  10b  |  Default threshold values    |  Default threshold values    |mK     |  11b  |  Default cumulative values   |  Default cumulative values   |dK     +=====================================================================+r  t   E  The current cumulative values may be updated by the target or by the H  initiator using the LOG SELECT command to reflect the cumulative numberK  of events experienced by the target.  Fields in the parameter control bytevE  (8.3.2) of each log parameter control the updating and saving of the !  current cumulative parameters.  s  oE  The target shall set the current threshold parameters to the defaultbK  threshold values in response to a LOG SELECT command with the PC field sets8  to 10b and the parameter list length field set to zero.  sJ  The target shall set all cumulative parameters to their default values inF  response to a LOG SELECT command with the PC field set to 11b and the*  parameter list length field set to zero.   tJ  The current threshold value can only be modified by the initiator via theK  LOG SELECT command.  If the initiator attempts to change current thresholdeI  values that are not available or not implemented for that log parameter,hB  then the target shall terminate the LOG SELECT command with CHECKK  CONDITION status, the sense key set to ILLEGAL REQUEST, and the additionallJ  sense code set to INVALID FIELD IN PARAMETER LIST.  The saving of currentJ  threshold parameters and the criteria for the current threshold being met?  are controlled by bits in the parameter control byte (8.3.2). m  dO     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).  cE  The parameter list length field specifies the length in bytes of theAJ  parameter list that shall be transferred from the initiator to the targetK  during the DATA OUT phase.  A parameter list length of zero indicates thattJ  no pages shall be transferred.  This condition shall not be considered anH  error.  If the initiator sends page codes or parameter codes within theG  parameter list that are reserved or not implemented by the target, thedL  target shall terminate the LOG SELECT command with CHECK CONDITION status. G  The sense key shall be set to ILLEGAL REQUEST and the additional sensei-  code set to INVALID FIELD IN PARAMETER LIST.   aK  If a parameter list length results in the truncation of any log parameter,eI  the target shall terminate the command with CHECK CONDITION status.  ThenH  sense key shall be set to ILLEGAL REQUEST and the additional sense code  set to INVALID FIELD IN CDB.   iI  The initiator should send pages in ascending order by page code value ifuB  multiple pages are sent during a DATA OUT phase.  If multiple logI  parameters within a page are sent during the DATA OUT phase, they shouldtF  be sent in ascending order by parameter code value.  The target shallH  return CHECK CONDITION status if the initiator sends pages out of orderH  or parameter codes out of order.  The sense key shall be set to ILLEGALH  REQUEST and the additional sense code set to INVALID FIELD IN PARAMETER  LIST.   K     NOTE 73 Initiators should issue LOG SENSE commands prior to issuing LOGlB     SELECT commands to determine supported pages and page lengths.  tK  The target may provide independent sets of log parameters for each logical F  unit or for each combination of logical units and initiators.  If theG  target does not support independent sets of log parameters and any log K  parameters are changed that affect other initiators, then the target shallaK  generate a unit attention condition for all initiators except the one thatoH  issued the LOG SELECT command (see 7.9).  This unit attention conditionE  is returned with an additional sense code of LOG PARAMETERS CHANGED.a  cD  If the initiator sends a log parameter that is not supported by theD  target, the target shall terminate the command with CHECK CONDITIONK  status, set the sense key to ILLEGAL REQUEST, and set the additional sense )  code to INVALID FIELD IN PARAMETER LIST.I  D  8.2.7 LOG SENSE command  eH  The LOG SENSE command (see table 51) provides a means for the initiatorG  to retrieve statistical information maintained by the device about theuG  device or its logical units.  It is a complementary command to the LOGh  SELECT command.   6                           Table 51 - LOG SENSE commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (4Dh)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |         Reserved         |  PPC   |    SP  |P  |-----+-----------------------------------------------------------------------|P  | 2   |        PC        |        Page code                                   |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 5   | (MSB)                                                                 |P  |-----+---                        Parameter pointer                        ---|P  | 6   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 7   | (MSB)                                                                 |P  |-----+---                        Allocation length                        ---|P  | 8   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+  +  =H  The parameter pointer control (PPC) bit controls the type of parameters  requested from the target: M     a)     A PPC bit of one indicates that the target shall return a log page-J            with parameter code values that have changed since the last LOGK            SELECT or LOG SENSE command.  The target shall return only those-A            parameter codes following the parameter pointer field.|L     b)     A PPC bit of zero indicates that the log parameter requested fromJ            the target shall begin with the parameter code specified in theN            parameter pointer field and return the number of bytes specified byL            the allocation length field in ascending order of parameter codesJ            from the specified log page.  A PPC bit of zero and a parameterM            pointer field of zero shall cause all available log parameters for-L            the specified log page to be returned to the initiator subject to+            the specified allocation length.-  -H  Saving parameters is an optional function of the LOG SENSE command.  IfD  the target does not implement saving log parameters and if the saveI  parameters (SP) bit is one, then the target shall return CHECK CONDITION7K  status, set the sense key to ILLEGAL REQUEST, and set the additional sense   code to INVALID FIELD IN CDB.    rG  An SP bit of zero indicates the target shall perform the specified LOG D  SENSE command and shall not save any log parameters.  If saving logF  parameters is implemented, an SP bit of one indicates that the targetE  shall perform the specified LOG SENSE command and shall save all log|J  parameters identified as savable by the DS bit (8.3.2) to a non-volatile,  vendor-specific location. c   G  The page control (PC) field defines the type of parameter values to be H  selected (see 8.2.6 for the definition of the page control field).  TheC  parameter values returned by a LOG SENSE command are determined asg	  follows:eL     a)     The specified parameter values at the last update (in response toI            a LOG SELECT or LOG SENSE command or done automatically by thea)            target for cumulative values).iI     b)     The saved values, if an update has not occurred since the lastsJ            power-on, hard RESET condition, or BUS DEVICE RESET message and,            saved parameters are implemented.K     c)     The default values, if an update has not occurred since the lastiJ            power-on, hard RESET condition, or BUS DEVICE RESET message and=            saved values are not available or not implemented.    J  The page code field identifies which page of data is being requested (seeK  8.3.2).  If the page code is reserved or not implemented, the target shall H  terminate the command with CHECK CONDITION status.  The sense key shallH  be set to ILLEGAL REQUEST with the additional sense code set to INVALID  FIELD IN CDB. t  HK  The parameter pointer field allows the initiator to request parameter datatJ  beginning from a specific parameter code to the maximum allocation lengthK  or the maximum parameter code supported by the target, whichever is less. tG  If the value of the parameter pointer field is larger than the largest C  available parameter code that can be returned by the target on therB  specified page, the target shall terminate the command with CHECKI  CONDITION status.  The sense key shall be set to ILLEGAL REQUEST and the==  additional sense code shall be set to INVALID FIELD IN CDB. =  wE  Log parameters within the specified log page shall be transferred inu-  ascending order according to parameter code.-  +  8.2.8 MODE SELECT(6) command    C  The MODE SELECT(6) command (see table 52) provides a means for the K  initiator to specify medium, logical unit, or peripheral device parameters J  to the target.  Targets that implement the MODE SELECT command shall alsoF  implement the MODE SENSE command.  Initiators should issue MODE SENSEJ  prior to each MODE SELECT to determine supported pages, page lengths, and  other parameters.   8                        Table 52 - MODE SELECT(6) commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (15h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |   PF   |         Reserved         |  SP    |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Parameter list length                       |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+  tH  If a target supports saved pages, it may save only one copy of the pageJ  for each logical unit and have it apply to all initiators, or it may saveG  separate copies for each initiator for each logical unit.  If separaterH  copies are saved, the target shall maintain separate current values forK  each I_T_L nexus. Pages that are common to all initiators are not requiredd  to have multiple copies.   cH  If an initiator sends a MODE SELECT command that changes any parametersI  applying to other initiators, the target shall generate a unit attentionaH  condition for all initiators except the one that issued the MODE SELECTK  command (see 7.9).  The target shall set the additional sense code to MODEo  PARAMETERS CHANGED. o  VC  The target may provide for independent sets of parameters for eachtB  attached logical unit or for each combination of logical unit andK  initiator.  If independent sets of parameters are implemented, and a thirdoK  party reservation is requested, the target transfers the set of parameters J  in effect for the initiator of the RESERVE command to the parameters usedG  for commands from the third party device (see 9.2.12.3 and 10.2.10.1).   rI  A page format (PF) bit of zero indicates that the MODE SELECT parameters A  are as specified in SCSI-1, (i.e. all parameters after the block K  descriptors are vendor-specific).  A PF bit of one indicates that the MODE C  SELECT parameters following the header and block descriptor(s) are G  structured as pages of related parameters and are as specified in this 
  standard.   E  A save pages (SP) bit of zero indicates the target shall perform thelJ  specified MODE SELECT operation, and shall not save any pages.  An SP bitI  of one indicates that the target shall perform the specified MODE SELECT I  operation, and shall save to a non-volatile vendor-specific location allrH  the savable pages including any sent during the DATA OUT phase.  The SPJ  bit is optional, even when mode pages are supported by the target.  PagesC  that are saved are identified by the parameter savable bit that istK  returned in the page header by the MODE SENSE command (see 8.3.3).  If thenG  PS bit is set in the MODE SENSE data then the page shall be savable by K  issuing a MODE SELECT command with the SP bit set.  If the target does notrI  implement saved pages and the SP bit is set to one, the command shall besF  terminated with CHECK CONDITION status. The sense key shall be set toG  ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN   CDB.G  NJ  The parameter list length field specifies the length in bytes of the modeJ  parameter list that shall be transferred from the initiator to the targetK  during the DATA OUT phase.  A parameter list length of zero indicates that I  no data shall be transferred.  This condition shall not be considered as=
  an error.  =J  The target shall terminate the command with CHECK CONDITION status if theF  parameter list length results in the truncation of any mode parameterI  header, mode parameter block descriptor(s), or mode page.  The sense key=H  shall be set to ILLEGAL REQUEST, and the additional sense code shall be%  set to PARAMETER LIST LENGTH ERROR. n  dG  The mode parameter list for the MODE SELECT and MODE SENSE commands is-J  defined in 8.3.3.  Parts of each mode parameter list are uniquely defined  for each device-type.  |H  The target shall terminate the MODE SELECT command with CHECK CONDITIONG  status, set the sense key to ILLEGAL REQUEST, set the additional sense H  code to INVALID FIELD IN PARAMETER LIST, and  shall not change any mode)  parameters for the following conditions: M     a)     If the initiator sets any field that is reported as not changeable|A            by the target to a value other than its current value.-J     b)     If the initiator sets any field in the mode parameter header or7            block descriptor(s) to an unsupported value.-L     c)     If an initiator sends a mode page with a page length not equal toL            the page length returned by the MODE SENSE command for that page.N     d)     If the initiator sends a unsupported value for a mode parameter and?            rounding is not implemented for that mode parameter.-N     e)     If the initiator sets any reserved field in the mode parameter list            to a non-zero value.    H  If the initiator sends a value for a mode parameter that is outside theH  range supported by the target and rounding is implemented for that mode"  parameter, the target may either:O     a)     round the parameter to an acceptable value and terminate the command-!            as described in 7.5.4; O     b)     terminate the command with CHECK CONDITION status, the sense key set=K            to ILLEGAL REQUEST, and set the additional sense code to INVALIDr#            FIELD IN PARAMETER LIST.r   C  A target may alter any mode parameter in any mode page (even thoseCA  reported as non-changeable) as a result of changes to other mode   parameters.  eD  The target validates the non-changeable mode parameters against theH  current values that existed for those mode parameters prior to the MODE  SELECT command.  iQ     NOTE 74 If the current values calculated by the target affect the initiator'soN     operation, the initiator should issue a MODE SENSE command after each MODE     SELECT command.e     8.2.9 MODE SELECT(10) command  dD  The MODE SELECT(10) command (see table 53) provides a means for theK  initiator to specify medium, logical unit, or peripheral device parameterseI  to the target.  See the MODE SELECT(6) command (8.2.8) for a description I  of the fields in this command.  Initiators should issue MODE SENSE priordJ  to each MODE SELECT to determine supported mode pages, mode page lengths,  and other parameters.   9                        Table 53 - MODE SELECT(10) command P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (55h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |   PF   |         Reserved         |  SP    |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   | (MSB)                                                                 |P  |-----+---                        Parameter list length                    ---|P  | 8   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+  e  xH  Targets that implement the MODE SELECT(10) command shall also implement  the MODE SENSE(10) command.       8.2.10 MODE SENSE(6) commandf  dJ  The MODE SENSE(6) command (see table 54) provides a means for a target toJ  report parameters to the initiator.  It is a complementary command to the  MODE SELECT(6) command. s  u8                         Table 54 - MODE SENSE(6) commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (1Ah)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |Reserved|   DBD  |         Reserved         |P  |-----+-----------------------------------------------------------------------|P  | 2   |       PC        |                   Page code                         |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Allocation length                           |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+  -  -H  A disable block descriptors (DBD) bit of zero indicates that the targetJ  may return zero or more block descriptors in the returned MODE SENSE dataJ  (see 8.3.3), at the target's discretion.  A DBD bit of one specifies thatG  the target shall not return any block descriptors in the returned MODE-  SENSE data.  -I  The page control (PC) field defines the type of mode parameter values tolE  be returned in the mode pages.  The page control field is defined in-
  table 55.  -6                          Table 55 - Page control field-  +=======-=====================-============+ -  | Code  |  Type of parameter  | Subclause  |=-  |-------+---------------------+------------|I-  |  00b  |  Current values     |  8.2.10.1  |l-  |  01b  |  Changeable values  |  8.2.10.2  |a-  |  10b  |  Default values     |  8.2.10.3  |a-  |  11b  |  Saved values       |  8.2.10.4  |h-  +==========================================+,  eN     NOTE 75 The page control field only affects the mode parameters within theK     mode pages, however the PS bit, page code and page length fields should P     return current values since they have no meaning when used with other types.O     The mode parameter header and mode parameter block descriptor should returnn     current values.x  tF  The page code specifies which mode page(s) to return.  Mode page code  usage is defined in table 56.  o?                 Table 56 - Mode page code usage for all devicesnP  +=============-==================================================-============+P  |  Page code  |  Description                                     |  Subclause |P  |-------------+--------------------------------------------------+------------|P  |     00h     |  Vendor-specific (does not require page format)  |            |P  |  01h - 1Fh  |  See specific device-types                       |            |P  |  20h - 3Eh  |  Vendor-specific (page format required)          |            |P  |     3Fh     |  Return all mode pages                           |            |P  +=============================================================================+  fI  An initiator may request any one or all of the supported mode pages fromeH  a target.  If an initiator issues a MODE SENSE command with a page codeC  value not implemented by the target, the target shall return CHECKiH  CONDITION status and shall set the sense key to ILLEGAL REQUEST and the0  additional sense code to INVALID FIELD IN CDB.   eK  A page code of 3Fh indicates that all mode pages implemented by the targetlH  shall be returned to the initiator.  If the mode parameter list exceedsK  256 bytes for a MODE SENSE(6) command or 65 536 bytes for a MODE SENSE(10)gJ  command, the target shall return CHECK CONDITION status and the sense keyE  shall be set to ILLEGAL REQUEST and the additional sense code set to)  INVALID FIELD IN CDB. t   F  Mode page 00h, if implemented, shall be returned after all other mode  pages.m  d	     NOTESPQ     76 Mode pages should be returned in ascending page code order except for mode 
     page 00h.dN     77 If the PC field and the page code field are both set to zero the targetP     should return a mode parameter header and block descriptor (if applicable). D     This provides for compatibility with existing SCSI-1 initiators.   F  The mode parameter list for all device types for MODE SELECT and MODEA  SENSE is defined in 8.3.3.  Parts of the mode parameter list areoH  specifically defined for each device type.  See subclause three of each0  peripheral device type for further information.     8.2.10.1 Current values  iJ  A PC field value of 0h requests that the target return the current values:  of the mode parameters.  The current values returned are:H     a)     the current values of the mode parameters established by last*            successful MODE SELECT command;O     b)     the saved values of the mode parameters if a MODE SELECT command hasDI            not successfully completed since the last power-on, hard RESETe2            condition, or BUS DEVICE RESET message;N     c)     the default values of the mode parameters, if saved values, are not&            available or not supported.  A  8.2.10.2 Changeable values   sG  A PC field value of 1h requests that the target return a mask denotingoK  those mode parameters that are changeable.  In the mask, the fields of theeI  mode parameters that are changeable shall be set to all one bits and thetK  fields of the mode parameters that are non-changeable (i.e. defined by they'  target) shall be set to all zero bits.    	     NOTESdM     78 An attempt to change a non-changeable mode parameter (via MODE SELECT) .     results in an error condition (see 8.2.8).O     79 The initiator should issue a MODE SENSE command with the PC field set to K     1h and the page code field set to 3Fh to determine which mode pages arerN     supported, which mode parameters within the mode pages are changeable, andK     the supported length of each mode page prior to issuing any MODE SELECTo
     commands.I  h  8.2.10.3 Default values   J  A PC field value of 2h requests that the target return the default valuesI  of the mode parameters.  Parameters not supported by the target shall be F  set to zero.  Default values are accessible even if the device is not  ready.      8.2.10.4 Saved values   H  A PC field value of 3h requests that the target return the saved valuesD  of the mode parameters.  Implementation of saved page parameters isG  optional.  Mode parameters not supported by the target shall be set tolA  zero.  If saved values are not implemented, the command shall benE  terminated with CHECK CONDITION status, the sense key set to ILLEGAL C  REQUEST and the additional sense code set to SAVING PARAMETERS NOT   SUPPORTED.e  hO     NOTE 80 The method of saving parameters is vendor-specific.  The parameters L     are preserved in such a manner that they are retained when the target isO     powered down.  All savable pages can be considered saved when a MODE SELECT Q     command issued with the SP bit set to one has returned a GOOD status or afterc7     the successful completion of a FORMAT UNIT command.r     8.2.10.5 Initial responses   pE  After a power-up condition or hard reset condition, the target shallo!  respond in the following manner:oF     a)     If default values are requested, report the default values.D     b)     If saved values are requested, report valid restored modeN            parameters, or restore the mode parameters and report them.  If theO            saved values of the mode parameters are not able to be accessed from=K            the non-volatile vendor-specific location, terminate the command|O            with CHECK CONDITION status and set the sense key set to NOT READY. |H            If saved parameters are not implemented respond as defined in            8.2.10.4.M     c)     If current values are requested and the current values of the mode L            parameters have not been sent by the initiator (via a MODE SELECTN            command), the target may return either the default or saved values,K            as defined above.  If current values have been sent, the current-$            values shall be reported.      MODE SENSE(10) command   H  The MODE SENSE(10) command (see table 57) provides a means for a targetI  to report parameters to the initiator.  It is a complementary command tor@  the MODE SELECT(10) command.  If the MODE SELECT(10) command isK  implemented the MODE SENSE(10) command shall be implemented.  See the MODE B  SENSE(6) command for a description of the fields in this command.  -8                        Table 57 - MODE SENSE(10) commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (5Ah)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |Reserved|  DBD   |         Reserved         |P  |-----+-----------------------------------------------------------------------|P  | 2   |       PC        |                   Page code                         |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   | (MSB)                                                                 |P  |-----+---                        Allocation length                        ---|P  | 8   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+  -  +  8.2.12 READ BUFFER Command-  -G  The READ BUFFER command (see table 58) is used in conjunction with the H  WRITE BUFFER command as a diagnostic function for testing target memoryF  and the SCSI bus integrity.  This command shall not alter the medium.   7                          Table 58 - READ BUFFER command P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (3Ch)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |     Reserved    |           Mode           |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Buffer ID                                   |P  |-----+-----------------------------------------------------------------------|P  | 3   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 4   |                           Buffer offset                               |P  |-----+---                                                                 ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 7   |                           Allocation length                           |P  |-----+---                                                                 ---|P  | 8   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+  e  rJ  The function of this command and the meaning of fields within the commandK  descriptor block depend on the contents of the mode field.  The mode field   is defined in table 59.  m8                        Table 59 - READ BUFFER mode fieldE           +========-============================-===================+=E           |  Mode  |  Description               |    Type           | E           |--------+----------------------------+-------------------|sE           |  000b  |  Combined header and data  |  Optional         |pE           |  001b  |  Vendor-specific           |  Vendor-specific  | E           |  010b  |  Data                      |  Optional         |TE           |  011b  |  Descriptor                |  Optional         | E           |  100b  |  Reserved                  |  Reserved         |sE           |  101b  |  Reserved                  |  Reserved         | E           |  110b  |  Reserved                  |  Reserved         |(E           |  111b  |  Reserved                  |  Reserved         |sE           +=========================================================+e  tQ     NOTE 81 Modes 000b and 001b are included for compatibility with products thateO     were designed prior to the generation of this International Standard.  SomeuM     products that were designed prior to the generation of this Internationalh;     Standard restrict the available length to 65 535 bytes.a  t.  8.2.12.1 Combined header and data mode (000b)  cK  In this mode, a four-byte header followed by data bytes is returned to thetI  initiator during the DATA IN phase.  The buffer ID and the buffer offseto  fields are reserved.   NJ  The four-byte READ BUFFER header (see table 60) is followed by data bytes  from the target's data buffer.S  s6                          Table 60 - READ BUFFER headerP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 1   | (MSB)                                                                 |P  |- - -+---                        Buffer capacity                          ---|P  | 3   |                                                                 (LSB) |P  +=============================================================================+  e  mC  The buffer capacity field specifies the total number of data byteshF  available in the target's data buffer.  This number is not reduced toH  reflect the allocation length;  nor is it reduced to reflect the actualG  number of bytes written using the WRITE BUFFER command.  Following the J  READ BUFFER header, the target shall transfer data from its data buffer. H  The target terminates the DATA IN phase when allocation length bytes ofH  header plus data have been transferred or when all available header andG  buffer data have been transferred to the initiator, whichever is less.u  r%  8.2.12.2 Vendor-specific mode (001b)s  nK  In this mode, the meanings of the buffer ID, buffer offset, and allocationi@  length fields are not specified by this International Standard.  o  8.2.12.3 Data mode (010b)  eK  In this mode, the DATA IN phase contains buffer data.  The buffer ID fieldcH  identifies a specific buffer within the target from which data shall beG  transferred.  The vendor assigns buffer ID codes to buffers within theuG  target. Buffer ID zero shall be supported.  If more than one buffer is F  supported, additional buffer ID codes shall be assigned contiguously,K  beginning with one. Buffer ID code assignments for the READ BUFFER commandaF  shall be the same as for the WRITE BUFFER command.  If an unsupportedD  buffer ID code is selected, the target shall return CHECK CONDITIONK  status, shall set the sense key to ILLEGAL REQUEST, and set the additionaleG  sense code to ILLEGAL FIELD IN CDB.  The target terminates the DATA INhI  phase when allocation length bytes have been transferred or when all thevF  available data from the buffer has been transferred to the initiator,  whichever amount is less.  eF  The buffer offset field contains the byte offset within the specifiedH  buffer from which data shall be transferred from.  The initiator shouldH  conform to the offset boundary requirements returned in the READ BUFFERB  descriptor (see 8.2.12.4).  If the target is unable to accept theK  specified buffer offset, it shall return CHECK CONDITION status, shall setmG  the sense key to ILLEGAL REQUEST, and set the additional sense code to   ILLEGAL FIELD IN CDB.  a   8.2.12.4 Descriptor mode (011b)  f@  In this mode, a maximum of four bytes of READ BUFFER descriptorA  information is returned.  The target shall return the descriptoreK  information for the buffer specified by the buffer ID (see the descriptioneJ  of the buffer ID in 8.2.12.3).  If there is no buffer associated with theJ  specified buffer ID, the target shall return all zeros in the READ BUFFERD  descriptor.  The buffer offset field is reserved in this mode.  TheF  allocation length should be set to four or greater.  The target shallJ  transfer the lesser of the allocation length or four bytes of READ BUFFERI  descriptor.  The READ BUFFER descriptor is defined as shown in table 61.D  E8                        Table 61 - READ BUFFER descriptorP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Offset boundary                             |P  |--- -+-----------------------------------------------------------------------|P  | 1   | (MSB)                                                                 |P  |- - -+---                        Buffer capacity                          ---|P  | 3   |                                                                 (LSB) |P  +=============================================================================+  -  -D  The offset boundary field returns the boundary alignment within theK  selected buffer for subsequent WRITE BUFFER and READ BUFFER commands.  The-G  value contained in the offset boundary field shall be interpreted as a   power of two.   J  The value contained in the buffer offset field of subsequent WRITE BUFFERN  and READ BUFFER commands should be a multiple of 2offset boundary as shown in
  table 62.   8                        Table 62 - Buffer offset boundaryK  +========-====================-==========================================+rK  |Offset  |                    |                                          |-K  |boundary| 2**Offset boundary |  Buffer offsets                          | K  |--------+--------------------+------------------------------------------|-K  |   0    |      2**0 = 1      |  Byte boundaries                         | K  |   1    |      2**1 = 2      |  Even-byte boundaries                    |-K  |   2    |      2**2 = 4      |  Four-byte boundaries                    | K  |   3    |      2**3 = 8      |  Eight-byte boundaries                   | K  |   4    |      2**4 = 16     |  16-byte boundaries                      ||K  |   .    |          .         |         .                                |-K  |   .    |          .         |         .                                | K  |  FFh   |  Not applicable    |  0 is the only supported buffer offset.  | K  +========================================================================+=  =   J  The buffer capacity field shall return the size of the selected buffer in  bytes.u   P     NOTE 82 In a multi-tasking system, a buffer may be altered between the WRITEQ     BUFFER and READ BUFFER commands by another task.  Buffer testing applicationsdQ     may wish to insure that only a single task is active. Use of reservations (to=N     all logical units on the device) or linked commands may also be helpful in;     avoiding buffer alteration between these two commands.    |*  8.2.13 RECEIVE DIAGNOSTIC RESULTS command   H  The RECEIVE DIAGNOSTIC RESULTS command (see table 63) requests analysisD  data be sent to the initiator after completion of a SEND DIAGNOSTICH  command (see 8.2.15).  If the target supports the optional page format,K  the page code field sent in the previous SEND DIAGNOSTIC command specifiesc"  the format of the returned data.    >                  Table 63 - RECEIVE DIAGNOSTIC RESULTS commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (1Ch)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |             Reserved                       |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   | (MSB)                                                                 |P  |-----+---                        Allocation length                        ---|P  | 4   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+  =	     NOTES=N     83 To insure that the diagnostic command information is not destroyed by aK     command sent from another initiator, either the SEND DIAGNOSTIC command L     should either be linked to the RECEIVE DIAGNOSTIC RESULTS command or the$     logical unit should be reserved.N     84 Although diagnostic software is generally device-specific, this commandL     and the SEND DIAGNOSTIC command provide a means to isolate the operatingL     system software from the device-specific diagnostic software. Hence, theP     operating system can remain device-independent.  This also allows diagnosticF     software to be transferred more easily to other operating systems.   B  See 8.3.1 for RECEIVE DIAGNOSTIC RESULTS page format definitions.  i  8.2.14 REQUEST SENSE Command    K  The REQUEST SENSE command (see table 64) requests that the target transfers  sense data to the initiator.d   8                         Table 64 - REQUEST SENSE commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (03h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |                  Reserved                  |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Allocation length                           |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+        The sense data:M     a)     shall be available if a contingent allegiance condition exists for(            the I_T_x nexus; L     b)     shall be available if other information (e.g. medium position) is"            available in any field;A     c)     may be available if an unexpected disconnect occurred.    K  If the target has no other sense data available to return, it shall return=F  a sense key of NO SENSE and an additional sense code of NO ADDITIONAL  SENSE INFORMATION.   eH  The sense data shall be preserved by the target fo  the initiator untilK  retrieved by a REQUEST SENSE command or until the receipt of any other I/OnD  process for the same I_T_x nexus.  Sense data shall be cleared uponG  receipt of any subsequent I/O process (including REQUEST SENSE) to ther  same I_T_x nexus.  tJ     NOTE 85 Some target implementations do not update sense data except onQ     commands that return CHECK CONDITION or COMMAND TERMINATED status.  Thus whenrO     polling for a logical unit to become ready, the initiator should issue TESTbQ     UNIT READY commands until GOOD status is returned.  If desired, the initiatoriL     may issue REQUEST SENSE commands after the TEST UNIT READY commands thatQ     return CHECK CONDITION or COMMAND TERMINATED status to obtain the sense data.h  uK  The target shall return CHECK CONDITION status for a REQUEST SENSE commandtI  only to report exception conditions specific to the command itself.  Fort	  example:tO     a)     A non-zero reserved bit is detected in the command descriptor block;dD     b)     An unrecovered parity error is detected on the data bus; B     c)     A target malfunction prevents return of the sense data.  sF  If a recovered error occurs during the execution of the REQUEST SENSEH  command, the target shall return the sense data with GOOD status.  If aG  target returns CHECK CONDITION status for a REQUEST SENSE command, thes  sense data may be invalid.   .M     NOTE 86 The sense data appropriate to the selection of an invalid logicalb     unit is defined in 7.5.3.v  aI  Targets shall be capable of returning eighteen bytes of data in responsehE  to a REQUEST SENSE command.  If the allocation length is eighteen orfD  greater, and a target returns less than eighteen bytes of data, theG  initiator should assume that the bytes not transferred would have beensI  zeros had the target returned those bytes.  Initiators can determine how E  much sense data has been returned by examining the allocation lengthOJ  parameter in the command descriptor block and the additional sense lengthI  in the sense data.  Targets shall not adjust the additional sense lengthmK  to reflect truncation if the allocation length is less than the sense datat  available.   iC  The sense data format for error codes 70h (current errors) and 71hrH  (deferred errors) are defined in table 65.  Error code values of 72h toF  7Eh are reserved.  Error code 7Fh is for a vendor-specific sense dataI  format.  Targets shall implement error code 70h; implementation of errorpI  code 71h is optional. Error code values of 00h to 6Fh are not defined bye>  this International Standard and their use is not recommended.   B               Table 65 - Error codes 70h and 71h sense data formatP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+========+==============================================================|P  | 0   | Valid  |                  Error code (70h or 71h)                     |P  |-----+-----------------------------------------------------------------------|P  | 1   |                           Segment number                              |P  |-----+-----------------------------------------------------------------------|P  | 2   |Filemark|  EOM   |  ILI   |Reserved|         Sense key                 |P  |-----+-----------------------------------------------------------------------|P  | 3   | (MSB)                                                                 |P  |- - -+---                        Information                              ---|P  | 6   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 7   |                           Additional sense length (n-7)               |P  |-----+-----------------------------------------------------------------------|P  | 8   | (MSB)                                                                 |P  |- - -+---                        Command-specific information             ---|P  | 11  |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 12  |                           Additional sense code                       |P  |-----+-----------------------------------------------------------------------|P  | 13  |                           Additional sense code qualifier             |P  |-----+-----------------------------------------------------------------------|P  | 14  |                           Field replaceable unit code                 |P  |-----+-----------------------------------------------------------------------|P  | 15  |  SKSV  |                                                              |P  |- - -+------------               Sense-key specific                       ---|P  | 17  |                                                                       |P  |-----+-----------------------------------------------------------------------|P  | 18  |                                                                       |P  |- - -+---                        Additional sense bytes                   ---|P  | n   |                                                                       |P  +=============================================================================+     =K  A valid bit of zero indicates that the information field is not as defined B  in this International Standard.  A valid bit of one indicates the@  information field contains valid information as defined in this@  International Standard.  Targets shall implement the valid bit.  nD  The segment number field contains the number of the current segmentK  descriptor if the REQUEST SENSE command is in response to a COPY, COMPARE,fI  or COPY AND VERIFY command.  Up to 256 segments are supported, beginningf  with segment zero.      J  The filemark bit is mandatory for sequential-access devices, and this bitI  is reserved for all other device types.  A filemark bit of one indicates|I  that the current command has read a filemark or setmark.  The additional|K  sense code field may be used to indicate whether a filemark or setmark was|K  read.  Reporting of setmarks is optional and indicated by the Rsmk bit for=D  sequential-access devices in the configuration parameters page (see  10.3.3.1).    K  The end-of-medium (EOM) bit is mandatory for sequential-access and printer-J  devices, and this bit is reserved for all other device types.  An EOM bitD  of one indicates that an end-of-medium condition (end-of-partition,K  beginning-of-partition, out-of-paper, etc.) exists.  For sequential-access J  devices, this bit indicates that the unit is at or past the early-warningI  if the direction was forward, or that the command could not be completed D  because beginning-of-partition was encountered if the direction was  reverse.     gJ  An incorrect length indicator (ILI) bit of one usually indicates that theI  requested logical block length did not match the logical block length of-  the data on the medium.  -I  The sense key, additional sense code and additional sense code qualifier J  provide a hierarchy of information.  The intention of the hierarchy is toF  provide a top-down approach for an initiator to determine informationH  relating to the error and exception conditions.  The sense key providesB  generic categories in which error and exception conditions can beJ  reported.  Initiators would typically use sense keys for high level errorD  recovery procedures.  Additional sense codes provide further detailH  describing the sense key.  Additional sense code qualifiers add furtherD  detail to the additional sense code.  The additional sense code and@  additional sense code qualifier can be used by initiators whereE  sophisticated error recovery procedures require detailed informationt/  describing the error and exception conditions.t   C  The sense key field is mandatory and indicates generic informationeH  describing an error or exception condition.  The sense keys are defined
  in 8.2.14.3.    I  The contents of the information field is device-type or command specific D  and is defined within the appropriate clause for the device type orF  command of interest.  Targets shall implement the information field. 1  Unless specified otherwise, this field contains: L     a)     the unsigned logical block address associated with the sense key,H            for direct-access devices (device type 0), write-once devicesN            (device type 4), CD-ROM devices (device type 5), and optical memory#            devices (device type 7). L     b)     the difference (residue) of the requested length minus the actualN            length in either bytes or blocks, as determined by the command, forM            sequential-access devices (device type 1), printer devices (device-L            type 2), processor devices (device type 3) and some direct accessL            device commands, except as defined for d) below. (Negative values7            are indicated by two's complement notation.)eO     c)     the difference (residue) of the requested number of blocks minus the-M            actual number of blocks copied or compared for the current segmentcE            descriptor of a COPY, COMPARE, or COPY AND VERIFY command.-M     d)     For sequential-access devices operating in buffered modes 1h or 2h O            that detect an unrecoverable write error when unwritten data blocks,=H            filemarks, or setmarks remain in the buffer, the value of the7            information field for all commands shall be:iM         1)    the total number of data blocks, filemarks, and setmarks in thevM               buffer if the device is in fixed block mode (block length field N               of the MODE SENSE block descriptor is non-zero and the fixed bit,               of the WRITE command is one). H         2)    the number of bytes in the buffer, including filemarks andO               setmarks, if the device is in variable mode (the fixed bit of the (               WRITE command is zero).     uK  The additional sense length field indicates the number of additional sense K  bytes to follow.  If the allocation length of the command descriptor blockrK  is too small to transfer all of the additional sense bytes, the additional 8  sense length is not adjusted to reflect the truncation.  nI  The command-specific information field contains information that depends E  on the command that was executed.  Further meaning for this field istJ  defined within the command description.  The command-specific informationJ  field is mandatory if the target supports any of the following commands: B  COPY, COMPARE, COPY AND VERIFY, SEARCH DATA, and REASSIGN BLOCKS.  CD  The additional sense code (ASC) field indicates further informationF  related to the error or exception condition reported in the sense keyH  field.  Targets shall support the additional sense code field.  Support>  of the additional sense codes not explicitly required by thisI  International Standard is optional.  A list of additional sense codes isyI  in 8.2.14.3.  If the target does not have further information related tonI  the error or exception condition, the additional sense code is set to NOx  ADDITIONAL SENSE INFORMATION.  aJ  The additional sense code qualifier (ASCQ) indicates detailed informationK  related to the additional sense code.  The additional sense code qualifier G  is optional.  If the error or exception condition is reportable by thetF  device, the value returned shall be as specified in 8.2.14.3.  If theB  target does not have detailed information related to the error orI  exception condition, the additional sense code qualifier is set to zero.e  rE  Non-zero values in the field replaceable unit code field are used torH  define a device-specific mechanism or unit that has failed.  A value ofI  zero in this field shall indicate that no specific mechanism or unit hassG  been identified to have failed or that the data is not available.  TheiB  field replaceable unit code field is optional. The format of thisG  information is not specified by this standard.  Additional informationtK  about the field replaceable unit may be available in the ASCII informationa1  page (see 8.3.4.2), if supported by the target. d  7?  The sense-key specific bytes are described in 8.2.14.1, below.a   D  The additional sense bytes field may contain command specific data,F  peripheral device specific data, or vendor-specific data that further2  defines the nature of the CHECK CONDITION status.  t  8.2.14.1 Sense-key specific  oG  The sense-key specific field as defined by this International StandardoG  when the value of the sense-key specific valid (SKSV) bit is one.  TheeI  sense-key specific valid bit and sense-key specific field are optional. -I  The definition of this field is determined by the value of the sense key G  field.  This field is reserved for sense keys not described below.  An G  SKSV value of zero indicates that this field is not as defined by this=  International Standard. =  =I  If the sense key field is set to ILLEGAL REQUEST and the SKSV bit is set K  to one, the sense-key specific field shall be as defined as shown in table-F  66. The field pointer field indicates which illegal parameters in the>  command descriptor block or the data parameters are in error.  -7                          Table 66 - Field pointer bytesaP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+========+========+========+========+========+==========================|P  | 15  |  SKSV  |  C/D   |Reserved|Reserved|  BPV   |    Bit pointer           |P  |-----+-----------------------------------------------------------------------|P  | 16  | (MSB)                                                                 |P  |-----+---                        Field pointer                            ---|P  | 17  |                                                                 (LSB) |P  +=============================================================================+      H  A command data (C/D) bit of one indicates that the illegal parameter isG  in the command descriptor block.  A C/D bit of zero indicates that the I  illegal parameter is in the data parameters sent by the initiator during   the DATA OUT phase.  -J  A bit pointer valid (BPV) bit of zero indicates that the value in the bitE  pointer field is not valid.  A BPV bit of one indicates that the bit-F  pointer field specifies which bit of the byte designated by the fieldK  pointer field is in error.  When a multiple-bit field is in error, the bit I  pointer field shall point to the most-significant (left-most) bit of the-  field.   1G  The field pointer field indicates which byte of the command descriptor J  block or of the parameter data was in error.  Bytes are numbered startingK  from zero, as shown in the tables describing the commands and parameters.  G  When a multiple-byte field is in error, the pointer shall point to the-1  most- significant (left-most) byte of the field.    Q     NOTE 87 Bytes identified as being in error are not necessarily the place thatA-     has to be changed to correct the problem.|   H  If the sense key is RECOVERED ERROR, HARDWARE ERROR or MEDIUM ERROR andJ  if the SKSV bit is one, the sense-key specific field shall be as shown in
  table 67.   9                       Table 67 - Actual retry count bytessP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+========+==============================================================|P  | 15  |  SKSV  |                  Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 16  | (MSB)                                                                 |P  |-----+---                        Actual retry count                       ---|P  | 17  |                                                                 (LSB) |P  +=============================================================================+  n  nI  The actual retry count field returns implementation-specific informationoB  on the actual number of retries of the recovery algorithm used in8  attempting to recover an error or exception condition.    O     NOTE 88 This field should relate to the retry count fields within the errore-     recovery page of the MODE SELECT command.t  ,E  If the sense key is NOT READY and the SKSV bit is one, the sense-keyaJ  specific field shall be as shown in table 68.  These fields only apply to7  the FORMAT UNIT command with the Immed bit set to one.d  u=                   Table 68 - Format progress indication bytesnP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+========+==============================================================|P  | 15  |  SKSV  |                  Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 16  | (MSB)                                                                 |P  |-----+---                        Progress indication                      ---|P  | 17  |                                                                 (LSB) |P  +=============================================================================+  o  eH  The progress indication field is a percent complete indication in whichD  the returned value is the numerator that has 65 536 (10000h) as itsG  denominator. The progress indication shall based upon the total formatnD  operation including any certification or initialization operations.  aI     NOTE 89 It is intended that the progress indication be time related.  M     However, since format time varies with the number of defects encountered,eK     etc., it is reasonable for the target to assign values to various stepseN     within the process.  The granularity of these steps should be small enoughL     to provide reasonable assurances to the initiator that progress is being	     made.e  s  8.2.14.2 Deferred errors   oH  Error code 70h indicates that the CHECK CONDITION or COMMAND TERMINATEDH  status returned is the result of an error or exception condition on theK  I/O process that returned the CHECK CONDITION or COMMAND TERMINATED status)D  or an unexpected disconnect.  This includes errors generated duringC  execution of the command by the actual execution process.  It alsooJ  includes errors not related to any command that are first observed duringG  execution of a command.  Examples of this latter type of error include C  disk servo-mechanism, off-track errors, and power-up test errors.    bJ  Error code 71h (deferred error) indicates that the CHECK CONDITION statusH  returned is the result of an error or exception condition that occurredI  during execution of a previous command for which GOOD status has already G  been returned.  Such commands are associated with use of the immediateEG  bit, with some forms of caching, and with multiple command buffering. fI  Targets that implement these features are required to implement deferredh  error reporting.l  sK  The deferred error indication may be sent at a time selected by the target J  through the asynchronous event notification process (see 7.5.5) if AEN is.  supported by both the initiator and target.    sJ  If AEN is not supported, the deferred error may be indicated by returningI  CHECK CONDITION status to the appropriate initiator as described below. aE  The subsequent execution of a REQUEST SENSE command shall return the "  deferred error sense information.  ,A  If an I/O process terminates with CHECK CONDITION status and theiJ  subsequent sense data returns a deferred error that I/O process shall notI  have been executed.  After the target detects a deferred error conditionoK  on a logical unit, it shall return a deferred error according to the rulesp  described below: G     a)     If a deferred error can be recovered with no external systemnO            intervention, a deferred error indication shall not be posted unlessnG            required by the error handling parameters of the MODE SELECTwM            command.  The occurrence of the error may be logged if statisticale)            or error logging is supported.nM     b)     If a deferred error can be associated with a causing initiator andCM            with a particular function or a particular subset of data, and thetM            error is either unrecovered or required to be reported by the modeoK            parameters, a deferred error indication shall be returned to thepO            causing initiator.  If an initiator other than the causing initiatortG            attempts access to the particular function or subset of datatN            associated with the deferred error, a BUSY status shall be returnedN            to that initiator in response to the command attempting the access.   M     NOTE 91 Not all devices may be sufficiently sophisticated to identify theoN     function or data that failed.  Those that cannot should treat the error in     the following manner.s  eL     c)     If a deferred error cannot be associated with a causing initiatorK            or with a particular subset of data, a deferred error indication J            shall be returned on behalf of the failing logical unit to eachL            initiator.  If multiple deferred errors have accumulated for some=            initiators, only the last error shall be returned. M     d)     If a deferred error cannot be associated with a particular logical J            unit, it shall be returned to the appropriate initiator for all1            logical units supported by the target.aM     e)     If a current command has not yet started executing, and a deferredoM            error occurs, the command shall be terminated with CHECK CONDITIONmN            status and deferred error information posted in the sense data.  ByH            convention, the current command is considered to have startedN            execution if the target has changed phase from the COMMAND phase toN            the next normal phase of the command sequence.  If a deferred errorN            occurs while a current command is executing and the current commandM            has been affected by the error, the command shall be terminated by H            CHECK CONDITION status and current error information shall beJ            returned in the sense data.  In this case, if the current errorO            information does not adequately define the deferred error condition,rO            a deferred error may be returned after the current error informationeJ            has been recovered.  If a deferred error occurs while a currentO            command is executing and the current command completes successfully,lO            the target may choose to return the deferred error information afteri1            the completion of the current command.6  TP     NOTE 91 Deferred errors may indicate that an operation was unsuccessful longQ     after the command performing the data transfer returned GOOD status.  If data6M     that cannot be replicated or recovered from other sources is being stored=Q     using buffered write operations, synchronization commands should be performed I     before the critical data is destroyed in the host initiator.  This is N     necessary to be sure that recovery actions can be taken if deferred errorsG     do occur in the storing of the data. If AEN is not implemented, therH     synchronizing process should provide the necessary commands to allowO     returning CHECK CONDITION status and subsequent returning of deferred error H     sense information after all buffered operations are guaranteed to be
     complete.d  i  r.  8.2.14.3 Sense key and sense code definitions   0  The sense keys are defined in tables 69 and 70.   <                    Table 69 - Sense key (0h-7h) descriptionsP  +========-====================================================================+P  | Sense  |  Description                                                       |P  |  key   |                                                                    |P  |--------+--------------------------------------------------------------------|P  |   0h   |  NO SENSE.  Indicates that there is no specific sense key          |P  |        |  information to be reported for the designated logical unit.  This |P  |        |  would be the case for a successful command or a command that      |P  |        |  received CHECK CONDITION or COMMAND TERMINATED status because one |P  |        |  of the filemark, EOM, or ILI bits is set to one.                  |P  |--------+--------------------------------------------------------------------|P  |   1h   |  RECOVERED ERROR.  Indicates that the last command completed       |P  |        |  successfully with some recovery action performed by the target.   |P  |        |  Details may be determinable by examining the additional sense     |P  |        |  bytes and the information field.  When multiple recovered errors  |P  |        |  occur during one command, the choice of which error to report     |P  |        |  (first, last, most severe, etc.) is device specific.              |P  |--------+--------------------------------------------------------------------|P  |   2h   |  NOT READY.  Indicates that the logical unit addressed cannot be   |P  |        |  accessed.  Operator intervention may be required to correct this  |P  |        |  condition.                                                        |P  |--------+--------------------------------------------------------------------|P  |   3h   |  MEDIUM ERROR.  Indicates that the command terminated with a non-  |P  |        |  recovered error condition that was probably caused by a flaw in   |P  |        |  the medium or an error in the recorded data.  This sense key may  |P  |        |  also be returned if the target is unable to distinguish between a |P  |        |  flaw in the medium and a specific hardware failure (sense key 4h).|P  |--------+--------------------------------------------------------------------|P  |   4h   |  HARDWARE ERROR.  Indicates that the target detected a non-        |P  |        |  recoverable hardware failure (for example, controller failure,    |P  |        |  device failure, parity error, etc.) while performing the command  |P  |        |  or during a self test.                                            |P  |--------+--------------------------------------------------------------------|P  |   5h   |  ILLEGAL REQUEST.  Indicates that there was an illegal parameter in|P  |        |  the command descriptor block or in the additional parameters      |P  |        |  supplied as data for some commands (FORMAT UNIT, SEARCH DATA,     |P  |        |  etc.).  If the target detects an invalid parameter in the command |P  |        |  descriptor block, then it shall terminate the command without     |P  |        |  altering the medium.  If the target detects an invalid parameter  |P  |        |  in the additional parameters supplied as data, then the target may|P  |        |  have already altered the medium.  This sense key may also indicate|P  |        |  that an invalid IDENTIFY message was received (6.6.7).            |P  |--------+--------------------------------------------------------------------|P  |   6h   |  UNIT ATTENTION.  Indicates that the removable medium may have been|P  |        |  changed or the target has been reset.  See 7.9 for more detailed  |P  |        |  information about the unit attention condition.                   |P  |--------+--------------------------------------------------------------------|P  |   7h   |  DATA PROTECT.  Indicates that a command that reads or writes the  |P  |        |  medium was attempted on a block that is protected from this       |P  |        |  operation.  The read or write operation is not performed.         |P  +=============================================================================+  u  r<                    Table 70 - Sense key (8h-Fh) descriptionsP  +========-====================================================================+P  | Sense  |  Description                                                       |P  |  key   |                                                                    |P  |--------+--------------------------------------------------------------------|P  |   8h   |  BLANK CHECK.  Indicates that a write-once device or a sequential- |P  |        |  access device encountered blank medium or format-defined end-of-  |P  |        |  data indication while reading or a write-once device encountered a|P  |        |  non-blank medium while writing.                                   |P  |--------+--------------------------------------------------------------------|P  |   9h   |  VENDOR-SPECIFIC.  This sense key is available for reporting vendor|P  |        |  specific conditions.                                              |P  |--------+--------------------------------------------------------------------|P  |   Ah   |  COPY ABORTED.  Indicates a COPY, COMPARE, or COPY AND VERIFY      |P  |        |  command was aborted due to an error condition on the source       |P  |        |  device, the destination device, or both.  (See 8.2.3.2 for        |P  |        |  additional information about this sense key.)                     |P  |--------+--------------------------------------------------------------------|P  |   Bh   |  ABORTED COMMAND.  Indicates that the target aborted the command.  |P  |        |  The initiator may be able to recover by trying the command again. |P  |--------+--------------------------------------------------------------------|P  |   Ch   |  EQUAL.  Indicates a SEARCH DATA command has satisfied an equal    |P  |        |  comparison.                                                       |P  |--------+--------------------------------------------------------------------|P  |   Dh   |  VOLUME OVERFLOW.  Indicates that a buffered peripheral device has |P  |        |  reached the end-of-partition and data may remain in the buffer    |P  |        |  that has not been written to the medium.  A RECOVER BUFFERED DATA |P  |        |  command(s) may be issued to read the unwritten data from the      |P  |        |  buffer.                                                           |P  |--------+--------------------------------------------------------------------|P  |   Eh   |  MISCOMPARE.  Indicates that the source data did not match the data|P  |        |  read from the medium.                                             |P  |--------+--------------------------------------------------------------------|P  |   Fh   |  RESERVED.                                                         |P  +=============================================================================+  i  tD  The additional sense codes and additional sense code qualifiers are  defined in table 71.r  b9                       Table 71 - ASC and ASCQ assignments,P  +=============================================================================+P  |           D - DIRECT ACCESS DEVICE                                          |P  |           .T - SEQUENTIAL ACCESS DEVICE                                     |P  |           . L - PRINTER DEVICE                                              |P  |           .  P - PROCESSOR DEVICE                                           |P  |           .  .W - WRITE ONCE READ MULTIPLE DEVICE                           |P  |           .  . R - READ ONLY (CD-ROM) DEVICE                                |P  |           .  .  S - SCANNER DEVICE                                          |P  |           .  .  .O - OPTICAL MEMORY DEVICE                                  |P  |           .  .  . M - MEDIA CHANGER DEVICE                                  |P  |           .  .  .  C - COMMUNICATION DEVICE                                 |P  |           .  .  .  .                                                        |P  | ASC ASCQ  DTLPWRSOMC  DESCRIPTION                                           |P  | --- ----              ----------------------------------------------------- |P  | 13h  00h  D   W  O    ADDRESS MARK NOT FOUND FOR DATA FIELD                 |P  | 12h  00h  D   W  O    ADDRESS MARK NOT FOUND FOR ID FIELD                   |P  | 00h  11h       R      AUDIO PLAY OPERATION IN PROGRESS                      |P  | 00h  12h       R      AUDIO PLAY OPERATION PAUSED                           |P  | 00h  14h       R      AUDIO PLAY OPERATION STOPPED DUE TO ERROR             |P  | 00h  13h       R      AUDIO PLAY OPERATION SUCCESSFULLY COMPLETED           |P  | 00h  04h   T    S     BEGINNING-OF-PARTITION/MEDIUM DETECTED                |P  | 14h  04h   T          BLOCK SEQUENCE ERROR                                  |P  | 30h  02h  DT  WR O    CANNOT READ MEDIUM - INCOMPATIBLE FORMAT              |P  | 30h  01h  DT  WR O    CANNOT READ MEDIUM - UNKNOWN FORMAT                   |P  | 52h  00h   T          CARTRIDGE FAULT                                       |P  | 3Fh  02h  DTLPWRSOMC  CHANGED OPERATING DEFINITION                          |P  | 11h  06h      WR O    CIRC UNRECOVERED ERROR                                |P  | 30h  03h  DT          CLEANING CARTRIDGE INSTALLED                          |P  | 4Ah  00h  DTLPWRSOMC  COMMAND PHASE ERROR                                   |P  | 2Ch  00h  DTLPWRSOMC  COMMAND SEQUENCE ERROR                                |P  | 2Fh  00h  DTLPWRSOMC  COMMANDS CLEARED BY ANOTHER INITIATOR                 |P  | 2Bh  00h  DTLPWRSO C  COPY CANNOT EXECUTE SINCE HOST CANNOT DISCONNECT      |P  | 41h  00h  D           DATA PATH FAILURE (SHOULD USE 40 NN)                  |P  | 4Bh  00h  DTLPWRSOMC  DATA PHASE ERROR                                      |P  | 11h  07h      W  O    DATA RESYNCHRONIZATION ERROR                          |P  | 16h  00h  D   W  O    DATA SYNCHRONIZATION MARK ERROR                       |P  | 19h  00h  D      O    DEFECT LIST ERROR                                     |P  | 19h  03h  D      O    DEFECT LIST ERROR IN GROWN LIST                       |P  | 19h  02h  D      O    DEFECT LIST ERROR IN PRIMARY LIST                     |P  | 19h  01h  D      O    DEFECT LIST NOT AVAILABLE                             |P  | 1Ch  00h  D      O    DEFECT LIST NOT FOUND                                 |P  | 32h  01h  D   W  O    DEFECT LIST UPDATE FAILURE                            |P  | 40h  NNh  DTLPWRSOMC  DIAGNOSTIC FAILURE ON COMPONENT NN (80H-FFH)          |P  | 63h  00h       R      END OF USER AREA ENCOUNTERED ON THIS TRACK            |P  | 00h  05h   T    S     END-OF-DATA DETECTED                                  |P  | 14h  03h   T          END-OF-DATA NOT FOUND                                 |P  | 00h  02h   T    S     END-OF-PARTITION/MEDIUM DETECTED                      |P  | 51h  00h   T     O    ERASE FAILURE                                         |P  | 0Ah  00h  DTLPWRSOMC  ERROR LOG OVERFLOW                                    |P  | 11h  02h  DT  W SO    ERROR TOO LONG TO CORRECT                             |P  | 03h  02h   T          EXCESSIVE WRITE ERRORS                                |P  | 3Bh  07h    L         FAILED TO SENSE BOTTOM-OF-FORM                        |P  | 3Bh  06h    L         FAILED TO SENSE TOP-OF-FORM                           |P  | 00h  01h   T          FILEMARK DETECTED                                     |P  | 14h  02h   T          FILEMARK OR SETMARK NOT FOUND                         |P  | 09h  02h      WR O    FOCUS SERVO FAILURE                                   |P  | 31h  01h  D L    O    FORMAT COMMAND FAILED                                 |P  | 58h  00h         O    GENERATION DOES NOT EXIST                             |P  +=============================================================================+  |  3  Table 71  (continued)P  +=============================================================================+P  | ASC ASCQ  DTLPWRSOMC  DESCRIPTION                                           |P  | --- ----              ----------------------------------------------------- |P  | 1Ch  02h  D      O    GROWN DEFECT LIST NOT FOUND                           |P  | 00h  06h  DTLPWRSOMC  I/O PROCESS TERMINATED                                |P  | 10h  00h  D   W  O    ID CRC OR ECC ERROR                                   |P  | 22h  00h  D           ILLEGAL FUNCTION (SHOULD USE 20 00, 24 00, OR 26 00)  |P  | 64h  00h       R      ILLEGAL MODE FOR THIS TRACK                           |P  | 28h  01h          M   IMPORT OR EXPORT ELEMENT ACCESSED                     |P  | 30h  00h  DT  WR OM   INCOMPATIBLE MEDIUM INSTALLED                         |P  | 11h  08h   T          INCOMPLETE BLOCK READ                                 |P  | 48h  00h  DTLPWRSOMC  INITIATOR DETECTED ERROR MESSAGE RECEIVED             |P  | 3Fh  03h  DTLPWRSOMC  INQUIRY DATA HAS CHANGED                              |P  | 44h  00h  DTLPWRSOMC  INTERNAL TARGET FAILURE                               |P  | 3Dh  00h  DTLPWRSOMC  INVALID BITS IN IDENTIFY MESSAGE                      |P  | 2Ch  02h        S     INVALID COMBINATION OF WINDOWS SPECIFIED              |P  | 20h  00h  DTLPWRSOMC  INVALID COMMAND OPERATION CODE                        |P  | 21h  01h          M   INVALID ELEMENT ADDRESS                               |P  | 24h  00h  DTLPWRSOMC  INVALID FIELD IN CDB                                  |P  | 26h  00h  DTLPWRSOMC  INVALID FIELD IN PARAMETER LIST                       |P  | 49h  00h  DTLPWRSOMC  INVALID MESSAGE ERROR                                 |P  | 11h  05h      WR O    L-EC UNCORRECTABLE ERROR                              |P  | 60h  00h        S     LAMP FAILURE                                          |P  | 5Bh  02h  DTLPWRSOM   LOG COUNTER AT MAXIMUM                                |P  | 5Bh  00h  DTLPWRSOM   LOG EXCEPTION                                         |P  | 5Bh  03h  DTLPWRSOM   LOG LIST CODES EXHAUSTED                              |P  | 2Ah  02h  DTL WRSOMC  LOG PARAMETERS CHANGED                                |P  | 21h  00h  DT  WR OM   LOGICAL BLOCK ADDRESS OUT OF RANGE                    |P  | 08h  00h  DTL WRSOMC  LOGICAL UNIT COMMUNICATION FAILURE                    |P  | 08h  02h  DTL WRSOMC  LOGICAL UNIT COMMUNICATION PARITY ERROR               |P  | 08h  01h  DTL WRSOMC  LOGICAL UNIT COMMUNICATION TIME-OUT                   |R   | 05h  00h  DTLPWRSOMC  LOGICAL UNIT DOES NOT RESPOND TO SELECTION            | P  | 4Ch  00h  DTLPWRSOMC  LOGICAL UNIT FAILED SELF-CONFIGURATION                |P  | 3Eh  00h  DTLPWRSOMC  LOGICAL UNIT HAS NOT SELF-CONFIGURED YET              |P  | 04h  01h  DTLPWRSOMC  LOGICAL UNIT IS IN PROCESS OF BECOMING READY          |P  | 04h  00h  DTLPWRSOMC  LOGICAL UNIT NOT READY, CAUSE NOT REPORTABLE          |P  | 04h  04h  DTL    O    LOGICAL UNIT NOT READY, FORMAT IN PROGRESS            |P  | 04h  02h  DTLPWRSOMC  LOGICAL UNIT NOT READY, INITIALIZING COMMAND REQUIRED |P  | 04h  03h  DTLPWRSOMC  LOGICAL UNIT NOT READY, MANUAL INTERVENTION REQUIRED  |P  | 25h  00h  DTLPWRSOMC  LOGICAL UNIT NOT SUPPORTED                            |P  | 15h  01h  DTL WRSOM   MECHANICAL POSITIONING ERROR                          |P  | 53h  00h  DTL WRSOM   MEDIA LOAD OR EJECT FAILED                            |P  | 3Bh  0Dh          M   MEDIUM DESTINATION ELEMENT FULL                       |P  | 31h  00h  DT  W  O    MEDIUM FORMAT CORRUPTED                               |P  | 3Ah  00h  DTL WRSOM   MEDIUM NOT PRESENT                                    |P  | 53h  02h  DT  WR OM   MEDIUM REMOVAL PREVENTED                              |P  | 3Bh  0Eh          M   MEDIUM SOURCE ELEMENT EMPTY                           |P  | 43h  00h  DTLPWRSOMC  MESSAGE ERROR                                         |P  | 3Fh  01h  DTLPWRSOMC  MICROCODE HAS BEEN CHANGED                            |P  | 1Dh  00h  D   W  O    MISCOMPARE DURING VERIFY OPERATION                    |P  | 11h  0Ah  DT     O    MISCORRECTED ERROR                                    |P  | 2Ah  01h  DTL WRSOMC  MODE PARAMETERS CHANGED                               |P  | 07h  00h  DTL WRSOM   MULTIPLE PERIPHERAL DEVICES SELECTED                  |P  | 11h  03h  DT  W SO    MULTIPLE READ ERRORS                                  |P  | 00h  00h  DTLPWRSOMC  NO ADDITIONAL SENSE INFORMATION                       |P  | 00h  15h       R      NO CURRENT AUDIO STATUS TO RETURN                     |P  | 32h  00h  D   W  O    NO DEFECT SPARE LOCATION AVAILABLE                    |P  | 11h  09h   T          NO GAP FOUND                                          |P  | 01h  00h  D   W  O    NO INDEX/SECTOR SIGNAL                                |P  | 06h  00h  D   WR OM   NO REFERENCE POSITION FOUND                           |P  +=============================================================================+  -  -  Table 71  (continued)P  +=============================================================================+P  | ASC ASCQ  DTLPWRSOMC  DESCRIPTION                                           |P  | --- ----              ----------------------------------------------------- |P  | 02h  00h  D   WR OM   NO SEEK COMPLETE                                      |P  | 03h  01h   T          NO WRITE CURRENT                                      |P  | 28h  00h  DTLPWRSOMC  NOT READY TO READY TRANSITION, MEDIUM MAY HAVE CHANGED|P  | 5Ah  01h  DT  WR OM   OPERATOR MEDIUM REMOVAL REQUEST                       |P  | 5Ah  00h  DTLPWRSOM   OPERATOR REQUEST OR STATE CHANGE INPUT (UNSPECIFIED)  |P  | 5Ah  03h  DT  W  O    OPERATOR SELECTED WRITE PERMIT                        |P  | 5Ah  02h  DT  W  O    OPERATOR SELECTED WRITE PROTECT                       |P  | 61h  02h        S     OUT OF FOCUS                                          |P  | 4Eh  00h  DTLPWRSOMC  OVERLAPPED COMMANDS ATTEMPTED                         |P  | 2Dh  00h   T          OVERWRITE ERROR ON UPDATE IN PLACE                    |P  | 3Bh  05h    L         PAPER JAM                                             |P  | 1Ah  00h  DTLPWRSOMC  PARAMETER LIST LENGTH ERROR                           |P  | 26h  01h  DTLPWRSOMC  PARAMETER NOT SUPPORTED                               |P  | 26h  02h  DTLPWRSOMC  PARAMETER VALUE INVALID                               |P  | 2Ah  00h  DTL WRSOMC  PARAMETERS CHANGED                                    |P  | 03h  00h  DTL W SO    PERIPHERAL DEVICE WRITE FAULT                         |P  | 50h  02h   T          POSITION ERROR RELATED TO TIMING                      |P  | 3Bh  0Ch        S     POSITION PAST BEGINNING OF MEDIUM                     |P  | 3Bh  0Bh        S     POSITION PAST END OF MEDIUM                           |P  | 15h  02h  DT  WR O    POSITIONING ERROR DETECTED BY READ OF MEDIUM          |P  | 29h  00h  DTLPWRSOMC  POWER ON, RESET, OR BUS DEVICE RESET OCCURRED         |P  | 42h  00h  D           POWER-ON OR SELF-TEST FAILURE (SHOULD USE 40 NN)      |P  | 1Ch  01h  D      O    PRIMARY DEFECT LIST NOT FOUND                         |P  | 40h  00h  D           RAM FAILURE (SHOULD USE 40 NN)                        |P  | 15h  00h  DTL WRSOM   RANDOM POSITIONING ERROR                              |P  | 3Bh  0Ah        S     READ PAST BEGINNING OF MEDIUM                         |P  | 3Bh  09h        S     READ PAST END OF MEDIUM                               |P  | 11h  01h  DT  W SO    READ RETRIES EXHAUSTED                                |P  | 14h  01h  DT  WR O    RECORD NOT FOUND                                      |P  | 14h  00h  DTL WRSO    RECORDED ENTITY NOT FOUND                             |P  | 18h  02h  D   WR O    RECOVERED DATA - DATA AUTO-REALLOCATED                |P  | 18h  05h  D   WR O    RECOVERED DATA - RECOMMEND REASSIGNMENT               |P  | 18h  06h  D   WR O    RECOVERED DATA - RECOMMEND REWRITE                    |P  | 17h  05h  D   WR O    RECOVERED DATA USING PREVIOUS SECTOR ID               |P  | 18h  03h       R      RECOVERED DATA WITH CIRC                              |P  | 18h  01h  D   WR O    RECOVERED DATA WITH ERROR CORRECTION & RETRIES APPLIED|P  | 18h  00h  DT  WR O    RECOVERED DATA WITH ERROR CORRECTION APPLIED          |P  | 18h  04h       R      RECOVERED DATA WITH L-EC                              |P  | 17h  03h  DT  WR O    RECOVERED DATA WITH NEGATIVE HEAD OFFSET              |P  | 17h  00h  DT  WRSO    RECOVERED DATA WITH NO ERROR CORRECTION APPLIED       |P  | 17h  02h  DT  WR O    RECOVERED DATA WITH POSITIVE HEAD OFFSET              |P  | 17h  01h  DT  WRSO    RECOVERED DATA WITH RETRIES                           |P  | 17h  04h      WR O    RECOVERED DATA WITH RETRIES AND/OR CIRC APPLIED       |P  | 17h  06h  D   W  O    RECOVERED DATA WITHOUT ECC - DATA AUTO-REALLOCATED    |P  | 17h  07h  D   W  O    RECOVERED DATA WITHOUT ECC - RECOMMEND REASSIGNMENT   |P  | 17h  08h  D   W  O    RECOVERED DATA WITHOUT ECC - RECOMMEND REWRITE        |P  | 1Eh  00h  D   W  O    RECOVERED ID WITH ECC CORRECTION                      |P  | 3Bh  08h   T          REPOSITION ERROR                                      |P  | 36h  00h    L         RIBBON, INK, OR TONER FAILURE                         |P  | 37h  00h  DTL WRSOMC  ROUNDED PARAMETER                                     |P  | 5Ch  00h  D      O    RPL STATUS CHANGE                                     |P  | 39h  00h  DTL WRSOMC  SAVING PARAMETERS NOT SUPPORTED                       |P  | 62h  00h        S     SCAN HEAD POSITIONING ERROR                           |P  | 47h  00h  DTLPWRSOMC  SCSI PARITY ERROR                                     |P  | 54h  00h     P        SCSI TO HOST SYSTEM INTERFACE FAILURE                 |P  | 45h  00h  DTLPWRSOMC  SELECT OR RESELECT FAILURE                            |P  +=============================================================================+        Table 71  (concluded)P  +=============================================================================+P  | ASC ASCQ  DTLPWRSOMC  DESCRIPTION                                           |P  | --- ----              ----------------------------------------------------- |P  | 3Bh  00h   TL         SEQUENTIAL POSITIONING ERROR                          |P  | 00h  03h   T          SETMARK DETECTED                                      |P  | 3Bh  04h    L         SLEW FAILURE                                          |P  | 09h  03h      WR O    SPINDLE SERVO FAILURE                                 |P  | 5Ch  02h  D      O    SPINDLES NOT SYNCHRONIZED                             |P  | 5Ch  01h  D      O    SPINDLES SYNCHRONIZED                                 |P  | 1Bh  00h  DTLPWRSOMC  SYNCHRONOUS DATA TRANSFER ERROR                       |P  | 55h  00h     P        SYSTEM RESOURCE FAILURE                               |P  | 33h  00h   T          TAPE LENGTH ERROR                                     |P  | 3Bh  03h    L         TAPE OR ELECTRONIC VERTICAL FORMS UNIT NOT READY      |P  | 3Bh  01h   T          TAPE POSITION ERROR AT BEGINNING-OF-MEDIUM            |P  | 3Bh  02h   T          TAPE POSITION ERROR AT END-OF-MEDIUM                  |P  | 3Fh  00h  DTLPWRSOMC  TARGET OPERATING CONDITIONS HAVE CHANGED              |P  | 5Bh  01h  DTLPWRSOM   THRESHOLD CONDITION MET                               |P  | 26h  03h  DTLPWRSOMC  THRESHOLD PARAMETERS NOT SUPPORTED                    |P  | 2Ch  01h        S     TOO MANY WINDOWS SPECIFIED                            |P  | 09h  00h  DT  WR O    TRACK FOLLOWING ERROR                                 |P  | 09h  01h      WR O    TRACKING SERVO FAILURE                                |P  | 61h  01h        S     UNABLE TO ACQUIRE VIDEO                               |P  | 57h  00h       R      UNABLE TO RECOVER TABLE-OF-CONTENTS                   |P  | 53h  01h   T          UNLOAD TAPE FAILURE                                   |P  | 11h  00h  DT  WRSO    UNRECOVERED READ ERROR                                |P  | 11h  04h  D   W  O    UNRECOVERED READ ERROR - AUTO REALLOCATE FAILED       |P  | 11h  0Bh  D   W  O    UNRECOVERED READ ERROR - RECOMMEND REASSIGNMENT       |P  | 11h  0Ch  D   W  O    UNRECOVERED READ ERROR - RECOMMEND REWRITE THE DATA   |P  | 46h  00h  DTLPWRSOMC  UNSUCCESSFUL SOFT RESET                               |P  | 59h  00h         O    UPDATED BLOCK READ                                    |P  | 61h  00h        S     VIDEO ACQUISITION ERROR                               |P  | 50h  00h   T          WRITE APPEND ERROR                                    |P  | 50h  01h   T          WRITE APPEND POSITION ERROR                           |P  | 0Ch  00h   T    S     WRITE ERROR                                           |P  | 0Ch  02h  D   W  O    WRITE ERROR - AUTO REALLOCATION FAILED                |P  | 0Ch  01h  D   W  O    WRITE ERROR RECOVERED WITH AUTO REALLOCATION          |P  | 27h  00h  DT  W  O    WRITE PROTECTED                                       |P  |                                                                             |P  | 80h  XXh     \                                                              |P  | THROUGH       >       Vendor-specific.                                      |P  | FFh  XX      /                                                              |P  |                                                                             |P  | XXh  80h     \                                                              |P  | THROUGH       >       Vendor-specific QUALIFICATION OF STANDARD ASC.        |P  | XXh  FFh     /                                                              |P  |                       ALL CODES NOT SHOWN ARE RESERVED.                     |P  |-----------------------------------------------------------------------------|P  |NOTE - Annex D contains the ASC and ASCQ assignments in numeric order.       |P  +=============================================================================+     |  |  8.2.15 SEND DIAGNOSTIC CommandR  EJ  The SEND DIAGNOSTIC command (see table 72) requests the target to performG  diagnostic operations on itself, on the logical unit, or on both.  TheMG  only mandatory implementation of this command is the self-test featureWJ  with the parameter list length of zero.  Except when the self-test bit isF  one, this command is usually followed by a RECEIVE DIAGNOSTIC RESULTS	  command.D  W9                        Table 72 - SEND DIAGNOSTIC command P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (1Dh)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |   PF   |Reserved|SelfTest| DevOfL | UnitOfL|P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   | (MSB)                                                                 |P  |-----+---                        Parameter list length                    ---|P  | 4   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+  R  EA  A page format (PF) bit of one specifies that the SEND DIAGNOSTICS>  parameters conform to the page structure as specified in thisH  International Standard.  The implementation of the PF bit is optional. E  See 87.3.1 for the definition of diagnostic pages.  A PF bit of zero6I  indicates that the SEND DIAGNOSTIC parameters are as specified in SCSI-1|+  (i.e. all parameters are vendor-specific).S  TE  A self-test (SelfTest) bit of one directs the target to complete itsRF  default self-test.  If the self-test successfully passes, the commandF  shall be terminated with GOOD status; otherwise, the command shall beI  terminated with CHECK CONDITION status and the sense key shall be set to   HARDWARE ERROR.  RH  A self-test bit of zero requests that the target perform the diagnosticK  operation specified in the parameter list.  The diagnostic operation mightMF  or might not require a target to return data that contains diagnosticK  results.  If the return of data is not required, the return of GOOD status E  indicates successful completion of the diagnostic operation.  If the|5  return of data is required, the target shall either:EM     a)     perform the requested diagnostic operation, prepare the data to beMJ            returned and indicate completion by returning GOOD status.  TheO            initiator issues a RECEIVE DIAGNOSTIC RESULTS command to recover theB            data;J     b)     accept the parameter list, and if no errors are detected in theH            parameter list, return GOOD status.  The requested diagnosticG            operation and the preparation of the data to be returned areUJ            performed upon receipt of a RECEIVE DIAGNOSTIC RESULTS command.  NN     NOTE 92 To insure that the diagnostic command information is not destroyedP     by a command sent from another initiator, either the SEND DIAGNOSTIC commandM     should be linked to the RECEIVE DIAGNOSTIC RESULTS command or the logicalE     unit should be reserved.   B  The device off-line (DevOfL) and unit off-line (UnitOfL) bits areH  generally set by operating system software, while the parameter list isJ  prepared by diagnostic application software.  These bits grant permissionH  to perform vendor-specific diagnostic operations on the target that mayH  be visible to attached initiators.  Thus, by preventing operations thatJ  are not enabled by these bits, the target assists the operating system in  protecting its resources.  OK  A UnitOfL bit of one grants permission to the target to perform diagnosticRK  operations that may affect the user accessible medium on the logical unit,HI  e.g. write operations to the user accessible medium, or repositioning ofTD  the medium on sequential access devices.  The implementation of theI  UnitOfl bit is optional.  A UnitOfL bit of zero prohibits any diagnostic ?  operations that may be detected by subsequent I/O processes.  1   J  A DevOfl bit of one grants permission to the target to perform diagnosticC  operations that may affect all the logical units on a target, e.g. ?  alteration of reservations, log parameters, or sense data. The D  implementation of the DevOfl bit is optional.  A DevOfL bit of zeroG  prohibits diagnostic operations that may be detected by subsequent I/OD  processes.C   E  The parameter list length field specifies the length in bytes of theHL  parameter list that shall be transferred from the initiator to the target. @  A parameter list length of zero indicates that no data shall beF  transferred. This condition shall not be considered an error.  If theI  specified parameter list length results in the truncation of one or more I  pages (PF bit set to one) the target shall return CHECK CONDITION status|D  with a sense key of ILLEGAL REQUEST and an additional sense code of  INVALID FIELD IN CDB.     D  See note 83 under the RECEIVE DIAGNOSTIC RESULTS command in 8.2.13.     8.2.16 TEST UNIT READY CommandT  PH  The TEST UNIT READY command (see table 73) provides a means to check ifK  the logical unit is ready.  This is not a request for a self-test.  If theEG  logical unit would accept an appropriate medium-access command without L  returning CHECK CONDITION status, this command shall return a GOOD status. I  If the logical unit cannot become operational or is in a state such that=K  an initiator action (e.g. START UNIT command) is required to make the unit7J  ready, the target shall return CHECK CONDITION status with a sense key of  NOT READY.=  =9                        Table 73 - TEST UNIT READY command P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (00h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |                  Reserved                  |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+      I  Table 74 defines the preferred responses to the TEST UNIT READY command. G  Higher-priority responses (e.g. BUSY or RESERVATION CONFLICT) are also   permitted.    ?                  Table 74 - Preferred TEST UNIT READY responses P  +=================-=================-=========================================+P  |      Status     |    Sense key    |             ASC and ASCQ                |P  |-----------------+-----------------+-----------------------------------------|P  | GOOD            | NO SENSE        | NO ADDITIONAL SENSE INFORMATION or      |P  |                 |                 |    other valid additional sense code.   |P  |-----------------+-----------------+-----------------------------------------|P  | CHECK CONDITION | ILLEGAL REQUEST | LOGICAL UNIT NOT SUPPORTED              |P  |                 |                 |                                         |P  |-----------------+-----------------+-----------------------------------------|P  | CHECK CONDITION | NOT READY       | LOGICAL UNIT DOES NOT RESPOND           |P  |                 |                 |    TO SELECTION                         |P  |-----------------+-----------------+-----------------------------------------|P  | CHECK CONDITION | NOT READY       | MEDIUM NOT PRESENT                      |P  |                 |                 |                                         |P  |-----------------+-----------------+-----------------------------------------|P  | CHECK CONDITION | NOT READY       | LOGICAL UNIT NOT READY,                 |P  |                 |                 |    CAUSE NOT REPORTABLE                 |P  |-----------------+-----------------+-----------------------------------------|P  | CHECK CONDITION | NOT READY       | LOGICAL UNIT IS IN PROCESS              |P  |                 |                 |    OF BECOMING READY                    |P  |-----------------+-----------------+-----------------------------------------|P  | CHECK CONDITION | NOT READY       | LOGICAL UNIT NOT READY,                 |P  |                 |                 |    INITIALIZING COMMAND REQUIRED        |P  |-----------------+-----------------+-----------------------------------------|P  | CHECK CONDITION | NOT READY       | LOGICAL UNIT NOT READY,                 |P  |                 |                 |    MANUAL INTERVENTION REQUIRED         |P  |-----------------+-----------------+-----------------------------------------|P  | CHECK CONDITION | NOT READY       | LOGICAL UNIT NOT READY,                 |P  |                 |                 |    FORMAT IN PROGRESS                   |P  +=============================================================================+     r  8.2.17 WRITE BUFFER command  uH  The WRITE BUFFER command (see table 75) is used in conjunction with theK  READ BUFFER command as a diagnostic for testing target memory and the SCSI H  bus integrity.  Additional modes are provided for downloading microcode*  and for downloading and saving microcode.   7                         Table 75 - WRITE BUFFER command=P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (3Bh)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |     Reserved    |          Mode            |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Buffer ID                                   |P  |-----+-----------------------------------------------------------------------|P  | 3   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 4   |                           Buffer offset                               |P  |-----+---                                                                 ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 7   |                           Parameter list length                       |P  |-----+---                                                                 ---|P  | 8   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+  n  hI  This command shall not alter any medium of the target when the data modeo5  or the combined header and data mode is specified.  a  nJ  The function of this command and the meaning of fields within the commandK  descriptor block depend on the contents of the mode field.  The mode field   is defined in table 76.  u9                        Table 76 - WRITE BUFFER mode fieldpH        +========-==================================-===================+H        |  Mode  |  Description                     |  Implementation   |H        |        |                                  |  requirements     |H        |--------+----------------------------------+-------------------|H        |  000b  |  Write combined header and data  |  Optional         |H        |  001b  |  Vendor-specific                 |  Vendor-specific  |H        |  010b  |  Write data                      |  Optional         |H        |  011b  |  Reserved                        |  Reserved         |H        |  100b  |  Download microcode              |  Optional         |H        |  101b  |  Download microcode and save     |  Optional         |H        |  110b  |  Reserved                        |  Reserved         |H        |  111b  |  Reserved                        |  Reserved         |H        +===============================================================+  L  nP     NOTE 93 Modes 000b and 001b are included for compatibility with CCS productsN     that were designed prior to the generation of this International Standard.H     These products restrict the maximum transfer length to 65 535 bytes.  t.  8.2.17.1 Combined header and data mode (000b)  oI  In this mode, data to be transferred is preceded by a four-byte header. hH  The four-byte header consists of all reserved bytes.  The buffer ID andI  the buffer offset fields shall be zero.  The parameter list length fieldRK  specifies the maximum number of bytes that shall be transferred during theHH  DATA OUT phase.  This number includes four bytes of header, so the dataJ  length to be stored in the target's buffer is parameter list length minusF  four.  The initiator should attempt to ensure that the parameter listH  length is not greater than four plus the buffer capacity (see 8.2.12.1)J  that is returned in the header of the READ BUFFER command (mode 00b).  IfJ  the parameter list length exceeds the buffer capacity target shall returnG  CHECK CONDITION status and shall set the sense key to ILLEGAL REQUEST.   t%  8.2.17.2 Vendor-specific mode (001b)t   I  In this mode, the meaning of the buffer ID, buffer offset, and parameter/E  list length fields are not specified by this International Standard.n     8.2.17.3 Data mode (010b)  sF  In this mode, the DATA OUT phase contains buffer data.  The buffer IDJ  field identifies a specific buffer within the target.  The vendor assignsG  buffer ID codes to buffers within the target.  Buffer ID zero shall berG  supported.  If more than one buffer is supported, additional buffer IDtA  codes shall be assigned contiguously, beginning with one.  If aneF  unsupported buffer ID code is selected, the target shall return CHECKH  CONDITION status and shall set the sense key to ILLEGAL REQUEST with an/  additional sense code of INVALID FIELD IN CDB.T  PI  Data are written to the target buffer starting at the location specified K  by the buffer offset.  The initiator should conform to the offset boundary G  requirements returned in the READ BUFFER descriptor.  If the target is D  unable to accept the specified buffer offset, it shall return CHECKH  CONDITION status and it shall set the sense key to ILLEGAL REQUEST with2  an additional sense code of INVALID FIELD IN CDB.  )K  The parameter list length specifies the maximum number of bytes that shallOG  be transferred during the DATA OUT phase to be stored in the specifiedbH  buffer beginning at the buffer offset.  The initiator should attempt toF  ensure that the parameter list length plus the buffer offset does notJ  exceed the capacity of the specified buffer.  (The capacity of the bufferB  can be determined by the buffer capacity field in the READ BUFFERD  descriptor.)  If the buffer offset and parameter list length fieldsK  specify a transfer that would exceed the buffer capacity, the target shall E  return CHECK CONDITION status and shall set the sense key to ILLEGAL-@  REQUEST with an additional sense code of INVALID FIELD IN CDB.   R(  8.2.17.4 Download microcode mode (100b)  -H  In this mode, vendor-specific microcode or control information shall beG  transferred to the control memory space of the target.  After a power-|G  cycle or reset, the device operation shall revert to a vendor-specific-H  condition.  The meanings of the buffer ID, buffer offset, and parameterH  list length fields are not specified by this International Standard andE  are not required to be zero-filled.  When the microcode download has B  completed successfully the target shall generate a unit attentionI  condition for all initiators except the one that issued the WRITE BUFFER H  command (see 7.9).  The additional sense code shall be set to MICROCODE  HAS BEEN CHANGED.  =1  8.2.17.5 Download microcode and save mode (101b)7  eH  In this mode, vendor-specific microcode or control information shall be'  transferred to the target and, if the NI  WRITE BUFFER command is completed successfully, also shall be saved in aeK  non-volatile memory space (semiconductor, disk, or other).  The downloaded=J  code shall then be effective after each power-cycle and reset until it isK  supplanted in another download microcode and save operation.  The meanings+J  of the buffer ID, buffer offset, and parameter list length fields are notJ  specified by this International Standard and are not required to be zero-D  filled.  When the download microcode and save command has completedG  successfully the target shall generate a unit attention condition (seeED  7.9) for all initiators except the one that issued the WRITE BUFFERH  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  I  N  8.3.1 Diagnostic parameters I  OJ  This subclause describes the diagnostic page structure and the diagnosticG  pages that are applicable to all SCSI devices.  Pages specific to each-E  device type are described in the third subclause of each device-typeY  clause (i.e. 9.3, 10.3, etc.).    G  A SEND DIAGNOSTIC command with a PF bit of one specifies that the SEND H  DIAGNOSTIC parameter list consists of zero or more diagnostic pages andD  that the data returned by the subsequent RECEIVE DIAGNOSTIC RESULTSI  command shall use the diagnostic page format (see table 77) described in   this International Standard.    8                        Table 77 - Diagnostic page formatP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Page code                                   |P  |-----+-----------------------------------------------------------------------|P  | 1   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                        Page length (n-3)                        ---|P  | 3   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 4   |                                                                       |P  |- - -+---                        Diagnostic parameters                    ---|P  | n   |                                                                       |P  +=============================================================================+  v   K  Each diagnostic page defines a function or operation that the target shall=H  perform.  The page contains a page header followed by the analysis dataG  that is formatted according to the page code specified in the previous   SEND DIAGNOSTIC command.       F  Targets that implement diagnostic pages are only required to accept a$  single diagnostic page per command.  =F  The page code field identifies which diagnostic page is being sent or3  returned.  The page codes are defined in table 78.-  -8                         Table 78 - Diagnostic page codesP  +=============-==================================================-============+P  |  Page code  |  Description                                     | Subclause  |P  |-------------+--------------------------------------------------+------------|P  |     00h     |  Supported diagnostics pages                     |  8.3.1.1   |P  |  01h - 3Fh  |  Reserved (for all device type pages)            |            |P  |  40h - 7Fh  |  See specific device type for definition         |            |P  |  80h - FFh  |  Vendor-specific pages                           |            |P  +=============================================================================+  |   F  The page length field specifies the length in bytes of the diagnosticI  parameters that follow this field.  If the initiator sends a page length-B  that results in the truncation of any parameter, the target shallH  terminate the command with CHECK CONDITION status.  The sense key shallH  be set to ILLEGAL REQUEST with the additional sense code set to INVALID  FIELD IN PARAMETER LIST.    J  The diagnostic parameters are defined for each page code.  The diagnosticI  parameters within a page may be defined differently in a SEND DIAGNOSTIC 6  command than in a RECEIVE DIAGNOSTIC RESULTS command.  -#  8.3.1.1 Supported diagnostic pages-   B  The supported diagnostics page (see table 79) returns the list of@  diagnostic pages implemented by the target.  This page shall beH  implemented if the target implements the page format option of the SEND4  DIAGNOSTIC and RECEIVE DIAGNOSTIC RESULTS commands.  h:                      Table 79 - Supported diagnostic pagesP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Page code (00h)                             |P  |-----+-----------------------------------------------------------------------|P  | 1   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                        Page length (n-3)                        ---|P  | 3   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 4   |                                                                       |P  |- - -+---                        Supported page list                      ---|P  | n   |                                                                       |P  +=============================================================================+  e  aJ  The definition of this page for the SEND DIAGNOSTIC command includes onlyH  the first four bytes.  If the page length field is not zero, the targetJ  shall terminate the SEND DIAGNOSTIC command with CHECK CONDITION status. G  The sense key shall be set to ILLEGAL REQUEST with an additional senseTI  code of INVALID FIELD IN PARAMETER LIST.  This page instructs the targetiC  to make available the list of all supported diagnostic pages to bee>  returned by a subsequent RECEIVE DIAGNOSTIC RESULTS command.   uG  The definition of this page for the RECEIVE DIAGNOSTIC RESULTS commande?  includes the list of diagnostic pages supported by the target.t  tE  The page length field specifies the length in bytes of the followingu  supported page list.s  8J  The supported page list field shall contain a list of all diagnostic pageG  codes implemented by the target in ascending order beginning with pageh
  code 00h.  E  8.3.2 Log parameters   lK  This subclause describes the log page structure and the log pages that are(H  applicable to all SCSI devices.  Pages specific to each device type areI  described in the third subclause of each device-type clause (i.e. 9.3.2,tI  10.3.2, etc.).  The LOG SELECT command supports the ability to send zerohD  or more log pages.  The LOG SENSE command returns a single log pageF  specified in the page code field of the command descriptor block (see  8.2.7).  eK  Each log page begins with a four-byte page header followed by zero or moreuK  variable-length log parameters defined for that page.  The log page formati  is defined in table 80.  o5                            Table 80 - Log page formatnR  +=======-========-========-========-========-========-========-========-========+R  |    Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |R  |Byte   |        |        |        |        |        |        |        |        |R  |=======+=================+=====================================================|R  | 0     |    Reserved     |            Page code                                |R  |-------+-----------------------------------------------------------------------|R  | 1     |                              Reserved                                 |R  |-------+-----------------------------------------------------------------------|R  | 2     | (MSB)                                                                 |R  |-------+---                           Page length (n-3)                     ---|R  | 3     |                                                                 (LSB) |R  |=======+=======================================================================|R  |       |                         Log parameters(s)                             |R  |=======+=======================================================================|R  | 4     |                              Log parameter (First)                    |R  |- --- -+---                           (Length x)                            ---|R  | x+3   |                                                                       |R  |-------+-----------------------------------------------------------------------|R  |       |                                 .                                     |R  |       |                                 .                                     |R  |-------+-----------------------------------------------------------------------|R  | n-y+1 |                              Log parameter (Last)                     |R  |- --- -+---                           (Length y)                            ---|R  | n     |                                                                       |R  +===============================================================================+  -  cF  The page code field identifies which log page is being transferred.    aI  The page length field specifies the length in bytes of the following logeF  parameters.  If the initiator sends a page length that results in theI  truncation of any parameter, the target shall terminate the command withdG  CHECK CONDITION status.  The sense key shall be set to ILLEGAL REQUESTeG  with the additional sense code set to INVALID FIELD IN PARAMETER LIST.i  lF  Most log pages contain one or more special data structures called logE  parameters (see table 81).  Log parameters may be data counters thateJ  record a count of a particular event (or events) or log parameters may beF  list parameters (strings) which contain a description of a particular  event.T  U4                             Table 81 - Log parameterP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   | (MSB)                                                                 |P  |-----+---                        Parameter code                           ---|P  | 1   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 2   |   DU   |   DS   |  TSD   |   ETC  |       TMC       |Reserved|  LP    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Parameter length (n-3)                      |P  |-----+-----------------------------------------------------------------------|P  | 4   |                                                                       |P  |- - -+---                        Parameter value                          ---|P  | n   |                                                                       |P  +=============================================================================+     1H  Each log parameter begins with a four-byte parameter header followed by+  one or more bytes of parameter value data.-  -K  The parameter code field identifies the log parameter is being transferred   for that log page.      I  The DU, DS, TSD, ETC, TMC, and LP fields are collectively referred to as ?  the parameter control byte.  These fields are described below.    J  For cumulative log parameter values (indicated by the PC field of the LOGH  SELECT and LOG SENSE command descriptor block), the disable update (DU)  bit is defined as follows: F     a)     A zero value indicates that the target shall update the logM            parameter value to reflect all events that should be noted by that             parameter.   I     b)     A one value indicates that the target shall not update the log=J            parameter value except in response to a LOG SELECT command that3            specifies a new value for the parameter.e  rK     NOTE 94 When updating cumulative log parameter values, a target may use P     volatile memory to hold these values until a LOG SELECT or LOG SENSE commandO     is received with an SP bit of one (or a target-defined event occurs).  Thus L     the updated cumulative log parameter values may be lost if a power cycle     occurs.r  .J  The DU bit is not defined for threshold values (indicated by the PC fieldC  of the LOG SENSE command descriptor block) nor for list parameters=H  (indicated by the LP bit).  The target shall ignore the value of any DU  bits in a LOG SELECT command.   J  A disable save (DS) bit of zero indicates that the target supports savingI  for that log parameter.  The target shall save the current cumulative or H  the current threshold parameter value (depending on the value in the PCJ  field of the command descriptor block) in response to a LOG SELECT or LOGI  SENSE command with an SP bit of one.  A DS bit of one indicates that theaG  target does not support saving that log parameter in response to a LOG=3  SELECT or LOG SENSE command with an SP bit of one.    K  A target save disable (TSD) bit of zero indicates that the target providespI  a target-defined method for saving log parameters.  This implicit savingtH  operation shall be done frequently enough to insure that the cumulativeD  parameter values retain statistical significance (i.e. across powerE  cycles).  A TSD bit of one indicates that either the target does notFI  provide a target-defined method for saving log parameters or the target-c3  defined method has been disabled by the initiator.g  aA  An enable threshold comparison (ETC) bit of one indicates that aRG  comparison to the threshold value is performed whenever the cumulativeeI  value is updated.  An ETC bit of zero indicates that a comparison is not D  performed.  The value of the ETC bit is the same for cumulative and  threshold parameters.  eH  The threshold met criteria (TMC) field (see table 82) defines the basisI  for comparison of the cumulative and threshold values.  The TMC field istJ  valid only if the ETC bit is one.  The value of the TMC field is the same)  for cumulative and threshold parameters.    8                        Table 82 - Threshold met criteria=  +========-=================================================+ =  |  Code  |  Basis for comparison                           |==  |--------+-------------------------------------------------|P=  |   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  |-=  +==========================================================+       G  If the ETC bit is one and the result of the comparison is true, a unit K  attention condition shall be generated for all initiators.  When reporting I  the unit attention condition, the target shall set the sense key to UNIT-H  ATTENTION and set the additional sense code to THRESHOLD CONDITION MET.   H  The list parameter (LP) bit indicates the format of the log parameter. I  If an initiator attempts to set the value of the LP bit to a value other K  than the one returned for the same parameter in the LOG SENSE command, the K  target shall terminate the command with CHECK CONDITION status.  The sense=J  key shall be set to ILLEGAL REQUEST with the additional sense code set to!  INVALID FIELD IN PARAMETER LIST.e   H  An LP bit of zero indicates that the parameter is a data counter.  DataF  counters are associated with one of more events;  the data counter isK  updated whenever one of these events occurs by incrementing of the counterID  value. If each data counter has associated with it a target-definedI  maximum value.  Upon reaching this maximum value, the data counter shallnI  not be incremented (i.e. it does not wrap).  When a data counter reachesrJ  its maximum value, the target shall set the associated DU bit to one.  IfI  the data counter is at or reaches its maximum value during the executionnE  of a command, the target shall complete the command.  If the commandtF  completes correctly (except for the data counter being at its maximumH  value) and if the RLEC bit of the control mode page (8.3.3.1) is set toF  one; then the target shall terminate the command with CHECK CONDITIONJ  status and set the sense key to RECOVERED ERROR with the additional sense&  code set to LOG COUNTER AT MAXIMUM.    sI  An LP bit of one indicates that the parameter is a list parameter.  List.I  parameters are not counters and thus the ETC and TMC fields shall be set I  to zero.  A list parameter is a string of ASCII graphic codes (i.e. coded  values 20h through 7Eh).t  cE  If more than one list parameter is defined in a single log page, thea4  following rules apply to assigning parameter codes:M     a)     The parameter updated last shall have a higher parameter code thane@            the previous parameter, except as defined in rule b).K     b)     When the maximum parameter code value supported by the target is-N            reached, the target shall assign the lowest parameter code value toM            the next log parameter (i.e. wrap-around parameter codes).  If the K            associated command completes correctly (except for the parameter=N            code being at its maximum value) and if the RLEC bit of the controlM            mode page (8.3.3.1) is set to one; then the target shall terminate-K            the command with CHECK CONDITION status and set the sense key to O            RECOVERED ERROR with the additional sense code set to LOG LIST CODES-            EXHAUSTED.-  -K     NOTE 95 List parameters can be used to store the locations of defective Q     blocks in the following manner.  When a defective block is identified, a list3O     parameter is updated to reflect the location and cause of the defect.  When K     the next defect is encountered, the list parameter with the next higher=N     parameter code is updated to record this defect.  The size of the page canQ     be made target specific to accommodate memory limitations.  It is recommended=L     that one or more data counter parameters be defined for the page to keepN     track of the number of valid list parameters and the parameter code of theP     parameter with the oldest recorded defect.  This technique can be adapted to&     record other types of information.   J  The parameter length field specifies the length in bytes of the followingG  parameter value.  If the initiator sends a parameter length value that C  results in the truncation of the parameter value, the target shall.H  terminate the command with CHECK CONDITION status.  The sense key shallH  be set to ILLEGAL REQUEST with the additional sense code set to INVALID  FIELD IN PARAMETER LIST.e  LG  If the initiator sends a log parameter value that is outside the rangetI  supported by the target, and rounding is implemented for that parameter,   the target may either: N     a)     round to an acceptable value and terminate the command as described            in 7.5.4; or-N     b)     terminate the command with CHECK CONDITION status and set the senseO            key to ILLEGAL REQUEST with the additional sense code set to INVALIDr#            FIELD IN PARAMETER LIST.g  eJ  When any counter in a log page reaches its maximum value, incrementing ofE  all counters in that log page shall cease until reinitialized by the I  initiator via a LOG SELECT command.  If the RLEC bit of the control modeFC  page is one, then the target shall report the exception condition.c   D  The page code assignments for the log pages are listed in table 83.  a4                            Table 83 - Log page codesP  +=============-==================================================-============+P  |  Page code  |  Description                                     | Subclause  |P  |-------------+--------------------------------------------------+------------|P  |     01h     |  Buffer over-run/under-run page                  |  8.3.2.1   |P  |     03h     |  Error counter page (read) page                  |  8.3.2.2   |P  |     04h     |  Error counter page (read reverse) page          |  8.3.2.2   |P  |     05h     |  Error counter page (verify) page                |  8.3.2.2   |P  |     02h     |  Error counter page (write) page                 |  8.3.2.2   |P  |     07h     |  Last n error events page                        |  8.3.2.3   |P  |     06h     |  Non-medium error page                           |  8.3.2.4   |P  |     00h     |  Supported log pages                             |  8.3.2.5   |P  |  08h - 2Fh  |  Reserved                                        |            |P  |     3Fh     |  Reserved                                        |            |P  |  30h - 3Eh  |  Vendor-specific pages                           |            |P  +=============================================================================+      '  8.3.2.1 Buffer over-run/under-run page    C  The buffer over-run/under-run page (page code 01h) defines 24 data F  counters that may be used to record the number of buffer over-runs orI  under-runs for the logical unit.  A target that implements this page may 6  implement one or more of the defined data counters.     D  A buffer over-run or under-run can occur when an initiator does notI  transmit data to or from the target's buffer fast enough to keep up with J  reading or writing the media.  This can be caused by a slow transfer rateD  across the SCSI bus or by a high SCSI bus utilization that preventsJ  reconnection by the target.  A buffer over-run condition can occur duringJ  a read operation when a buffer full condition prevents continued transferH  of data from the media to the buffer.  A buffer under-run condition canF  occur during a write operation when a buffer empty condition preventsG  continued transfer of data to the media from the buffer.  Most devices =  incur a delay at this point while the media is repositioned.t  aI  Table 84 defines the parameter code field for the buffer over-run/under-L  run counters.  hK      Table 84 - Parameter code field for buffer over-run/under-run countersnP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                          Reserved                                     |P  |-----+-----------------------------------------------------------------------|P  | 1   |      Count basis         |               Cause               |  Type  |P  +=============================================================================+  t   I  The parameter code field for buffer over-run/under-run counters is a 16-eJ  bit value comprised of eight reserved bits, a three-bit count basis fieldJ  (see table 85), a four-bit cause field (see table 86), and a one-bit typeG  field.  These are concatenated to determine the value of the parameteroH  code for that log parameter.  For example, a counter for parameter codeH  value of 0023h specifies a count basis of 001b; a cause of 0001b; and aJ  type of 1b; this counter is incremented once per command that experiences,  an over-run due to the SCSI bus being busy.  t8                        Table 85 - Count basis definition)  +=============-========================+s)  | Count basis |  Description           | )  |-------------+------------------------|e)  |    000b     |  Undefined             |e)  |    001b     |  Per command           |o)  |    010b     |  Per failed reconnect  |s)  |    011b     |  Per unit of time      |r)  | 100b - 111b |  Reserved              |s)  +======================================+e     fJ  The count basis field defines the criteria for incrementing the counter. %  The following criteria are defined: m   N     NOTE 95 The per unit of time count basis is device type specific.  Direct-M     access devices typically use a latency period (i.e. one revolution of the       medium) as the unit of time.   D  The cause field indicates the reason that the over-run or under-run9  occurred.  The following causes are defined in table 86.    8                        Table 86 - Cause field definition(  +============-========================+(  |    Cause   |Description             |(  |------------+------------------------|(  |      0h    |Undefined               |(  |      1h    |SCSI bus busy           |(  |      2h    |Transfer rate too slow  |(  |   3h - Fh  |Reserved                |(  +=====================================+  l   I  The type field indicates whether the counter records under-runs or over-bJ  runs.  A value of zero specifies a buffer under-run condition and a value.  of one specifies a buffer over-run condition.   I  The counters contain the total number of times buffer over-run or under-aK  run conditions have occurred since the last time the counter was cleared. tH  The counter shall be incremented for each occurrence of an under-run orF  over-run condition and can be incremented more than once for multiple6  occurrences during the execution of a single command.  t  8.3.2.2 Error counter pages  tF  This clause defines the optional error counter pages for write errorsH  (page code 02h), read errors (page code 03h), read reverse errors (pageE  code 04h) and verify errors (page code 05h).  The log page format is H  defined near the beginning of 8.3.2.  A page can return one or more log>  parameters this record events defined by the parameter codes.  tK  Table 87 defines the parameter codes for the error counter pages.  Support $  of each log parameter is optional.    A                Table 87 - Parameter codes for error counter pages J         +=================-==============================================+J         | Parameter code  |  Description                                 |J         |-----------------+----------------------------------------------|J         |     0000h       |  Errors corrected without substantial delay  |J         |     0001h       |  Errors corrected with possible delays       |J         |     0002h       |  Total (e.g. rewrites or rereads)            |J         |     0003h       |  Total errors corrected                      |J         |     0004h       |  Total times correction algorithm processed  |J         |     0005h       |  Total bytes processed                       |J         |     0006h       |  Total uncorrected errors                    |J         |  0007h - 7FFFh  |  Reserved                                    |J         |  8000h - FFFFh  |  Vendor-specific                             |J         +================================================================+  C  gJ     NOTE 96 The exact definition of the error counters is not part of thisI     International Standard.  These counters should not be used to comparey@     products because the products may define errors differently.   !  8.3.2.3 Last n error events paget  eK  Log page (07h) provides for a number of error-event records using the list K  parameter format of the log page.  The number of these error-event records D  supported, n, is device-specific.  Each error-event record containsI  device-specific diagnostic information for a single error encountered byhC  the device.  The parameter code associated with error-event record C  indicates the relative time at which the error occurred.  A higherEF  parameter code indicates that the error event occurred later in time.  eK  The content of the parameter value field of each log parameter is an ASCIIaI  character string which may describe the error event.  The exact contentsnG  of the character string is not defined by this International Standard.i  pI  When the last supported parameter code is used by an error-event record,hK  the recording on this page of all subsequent error information shall ceaseeJ  until one or more of the list parameters with the highest parameter codesC  have been reinitialized.  If the RLEC bit of the control mode pageeH  (8.3.3.1) is set to one, the target shall return CHECK CONDITION statusH  with the sense key set to RECOVERED ERROR and the additional sense codeG  set to LOG LIST CODES EXHAUSTED.  Alternatively, the target may reporte@  this condition via asynchronous event notification (see 7.5.5).  e  8.3.2.4 Non-medium error page     B  This page (page code 06h) provides for summing the occurrences ofI  recoverable error events other than write, read, or verify failures.  No J  discrimination among the various types of events is provided by parameterE  code (see table 88).  Vendor-specific discrimination may be providedn-  through the vendor-specific parameter codes..  t@                Table 88 - Non-medium error event parameter codesC  +=================-==============================================+oC  | Parameter code  |  Description                                 |oC  |-----------------+----------------------------------------------|tC  |      0000h      |  Non-medium error count                      |iC  |  0001h - 7FFFh  |  Reserved                                    |mC  |  8000h - FFFFh  |  Vendor-specific error counts                |cC  +================================================================+t  L  A  8.3.2.5 Supported log pages  sD  The supported log page (see table 89) returns the list of log pagesI  implemented by the target.  Targets that implement the LOG SENSE commandl  shall implement this log page.c  e7                          Table 89 - Supported log pages P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=================+=====================================================|P  | 0   |    Reserved     |        Page code (00h)                              |P  |-----+-----------------------------------------------------------------------|P  | 1   |                          Reserved                                     |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                       Page length (n-3)                         ---|P  | 3   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 4   |                                                                       |P  |- - -+---                       Supported page list                       ---|P  | n   |                                                                       |P  +=============================================================================+      D  This page is not defined for the LOG SELECT command.  This log pageH  returns the list of supported log pages for the specified logical unit.  =E  The page length field specifies the length in bytes of the followingb  supported page list.n  gI  The supported page list field shall contain a list of all log page codeseK  implemented by the target in ascending order beginning with page code 00h.h  i  8.3.3 Mode parameters  iG  This subclause describes the block descriptors and the pages used withrD  MODE SELECT and MODE SENSE commands that are applicable to all SCSIH  devices.  Pages specific to each device type are described in the third=  subclause of each device-type clause (i.e. 9.3, 10.3, etc.).a  sI  The mode parameter list shown in table 90 contains a header, followed byoI  zero or more block descriptors, followed by zero or more variable-lengthr:  pages.  Parameter lists are defined for each device type.   7                          Table 90 - Mode parameter listnQ  +======-========-========-========-========-========-========-========-========+nQ  |   Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |rQ  |Byte  |        |        |        |        |        |        |        |        | Q  |======+=======================================================================|eQ  |0 - n |                        Mode parameter header                          |=Q  |======+=======================================================================| Q  |0 - n |                        Block descriptor(s)                            | Q  |======+=======================================================================|=Q  |0 - n |                        Page(s)                                        | Q  +==============================================================================+-  -  -K  The six-byte command descriptor block parameter header is defined in table   91.   9                       Table 91 - Mode parameter header(6)=P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Mode data length                            |P  |-----+-----------------------------------------------------------------------|P  | 1   |                           Medium type                                 |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Device-specific parameter                   |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Block descriptor length                     |P  +=============================================================================+      K  The ten-byte command descriptor block parameter header is defined in table=  92.  =:                       Table 92 - Mode parameter header(10)P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   | (MSB)                                                                 |P  |-----+---                        Mode data length                         ---|P  | 1   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Medium type                                 |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Device-specific parameter                   |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 6   | (MSB)                                                                 |P  |-----+---                        Block descriptor length                  ---|P  | 7   |                                                                 (LSB) |P  +=============================================================================+  fH  When using the MODE SENSE command, the mode data length field specifiesB  the length in bytes of the following data that is available to beH  transferred.  The mode data length does not include itself.  When using1  the MODE SELECT command, this field is reserved.    M     NOTE 97 Targets that support more than 256 bytes of block descriptors and=M     pages may need to implement ten-byte mode commands.  The mode data lengthDM     field in the six-byte command descriptor block header limits the returned-     data to 256 bytes.  -A  Medium types are unique for each device type.  Refer to the mode F  parameters clause of the specific device type for definition of these/  values.  Some device types reserve this field.    H  The device specific parameter is unique for each device type.  Refer toI  the mode parameters clause of the specific device type for definition of B  this field.  Some device types reserve all or part of this field.   K  The block descriptor length specifies the length in bytes of all the block J  descriptors.  It is equal to the number of block descriptors times eight,K  and does not include pages or vendor-specific parameters, if any, that may E  follow the last block descriptor.  A block descriptor length of zero=G  indicates that no block descriptors are included in the mode parameter 8  list.  This condition shall not be considered an error.  s:  The mode parameter block descriptor is shown in table 93.  d=                    Table 93 - Mode parameter block descriptorrP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Density code                                |P  |-----+-----------------------------------------------------------------------|P  | 1   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 2   |                           Number of blocks                            |P  |-----+---                                                                 ---|P  | 3   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 5   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 6   |                           Block length                                |P  |-----+---                                                                 ---|P  | 7   |                                                                 (LSB) |P  +=============================================================================+  e  yH  Block descriptors specify some of the medium characteristics for all orJ  part of a logical unit.  Support for block descriptors is optional.  EachJ  block descriptor contains a density code field, a number of blocks field,F  and a block length field.  Block descriptor values are always currentF  (i.e. saving is not supported).  A unit attention condition (see 7.9)A  shall be generated when any block descriptor values are changed.-  iI  The density code field is unique for each device type. Refer to the mode E  parameters clause of the specific device type for definition of this =  field.  Some device types reserve all or part of this field.=  =I  The number of blocks field specifies the number of logical blocks on the I  medium to which the density code and block length fields apply.  A valueeJ  of zero indicates that all of the remaining logical blocks of the logical6  unit shall have the medium characteristics specified.  b	     NOTESpP     98 There may be implicit association between parameters defined in the pagesO     and block descriptors.  For direct-access devices, the block length affects Q     the optimum values (the values that achieve best performance) for the sectors N     per track, bytes per physical sector, track skew factor, and cylinder skewN     factor fields in the format parameters page.  In this case, the target mayJ     change parameters not explicitly sent with the MODE SELECT command.  A>     subsequent MODE SENSE command would reflect these changes.L     99 The number of remaining logical blocks may be unknown for some device
     types.  -E  The block length specifies the length in bytes of each logical block K  described by the block descriptor.  For sequential-access devices, a blockaK  length of zero indicates that the logical block size written to the medium J  is specified by the transfer length field in the command descriptor block  (see 10.2.4 and 10.2.14)-  --  The mode page format is defined in table 94.    5                           Table 94 - Mode page format|P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+========+========+=====================================================|P  | 0   |   PS   |Reserved|         Page code                                   |P  |-----+-----------------------------------------------------------------------|P  | 1   |                           Page length (n-1))                          |P  |-----+-----------------------------------------------------------------------|P  | 2   |                                                                       |P  |-----+--                         Mode parameters                          ---|P  | n   |                                                                       |P  +=============================================================================+  e   F  Each mode page contains a page code, a page length, and a set of modeJ  parameters.  The page codes are defined in this subclause and in the mode3  parameter sub-clauses of the specific device type.    H  When using the MODE SENSE command, a parameters savable (PS) bit of oneK  indicates that the mode page can be saved by the target in a non-volatile, I  vendor-specific location.  A PS bit of zero indicates that the supported H  parameters cannot be saved.  When using the MODE SELECT command, the PS  bit is reserved.=  =J  The page code field identifies the format and parameters defined for thatH  mode page.  Some page codes are defined as applying to all device typesA  and other page codes are defined for the specific device type.  =  =K  When using the MODE SENSE command, if page code 00h (vendor-specific page) H  is implemented, the target shall return that page last in response to aI  request to return all pages (page code 3Fh).  When using the MODE SELECT (  command, this page should be sent last.  =K  The page length field specifies the length in bytes of the mode parameterseI  that follow.  If the initiator does not set this value to the value that9E  is returned for the page by the MODE SENSE command, the target shall=H  terminate the command with CHECK CONDITION status.  The sense key shallH  be set to ILLEGAL REQUEST with the additional sense code set to INVALIDK  FIELD IN PARAMETER LIST.  The target is permitted to implement a mode page E  that is less than the full page length defined in this International=C  Standard, provided no field is truncated and the page length fielda3  correctly specifies the actual length implemented.-  -K  The mode parameters for each page are defined in the following subclauses, I  or in the mode parameters sub-clause for the specific device type.  Mode-?  parameters not implemented by the target shall be set to zero.-  |H  Table 95 defines the mode pages that are applicable to all device types6  that include the MODE SELECT and MODE SENSE commands.  -5                            Table 95 - Mode page codes P  +=============-==================================================-============+P  |  Page code  |  Description                                     | Subclause  |P  |-------------+--------------------------------------------------+------------|P  |     0Ah     |  Control mode page                               |  8.3.3.1   |P  |     02h     |  Disconnect-reconnect page                       |  8.3.3.2   |P  |     09h     |  Peripheral device page                          |  8.3.3.3   |P  |     01h     |  (See specific device type)                      |            |P  |  03h - 08h  |  (See specific device type)                      |            |P  |  0Bh - 1Fh  |  (See specific device type)                      |            |P  |     00h     |  Vendor-specific (does not require page format)  |            |P  |  20h - 3Eh  |  Vendor-specific (page format required)          |            |P  |     3Fh     |  Return all pages                                |            |P  |             |     (valid only for the MODE SENSE command)      |            |P  +=============================================================================+  D  c  8.3.3.1 Control mode page   K  The control mode page (see table 96) provides controls over several SCSI-2-I  features that are applicable to all device types such as tagged queuing, K  extended contingent allegiance, asynchronous event notification, and error-	  logging.-  -6                           Table 96 - Control mode pageP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+========+========+=====================================================|P  | 0   |   PS   |Reserved|         Page code (0Ah)                             |P  |-----+-----------------------------------------------------------------------|P  | 1   |                           Page length (06h)                           |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                           |  RLEC  |P  |-----+--------------------------------------------------------------+--------|P  | 3   |     Queue algorithm modifier      |    Reserved     |  QErr  |  DQue  |P  |-----+-----------------------------------------------------+--------+--------|P  | 4   |  EECA  |              Reserved             | RAENP  | UAAENP | EAENP  |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 6   | (MSB)                                                                 |P  |-----+---                        Ready AEN holdoff period                 ---|P  | 7   |                                                                 (LSB) |P  +=============================================================================+      F  A report log exception condition (RLEC) bit of one specifies that theG  target shall report log exception conditions as described in 8.3.2.  AsJ  RLEC bit of zero specifies that the target shall not report log exception  conditions.  wI  The queue algorithm modifier field (see table 97) specifies restrictionsrG  on the algorithm used for reordering commands that are tagged with the=  SIMPLE QUEUE TAG message.   9                       Table 97 - Queue algorithm modifier 3  +===========-====================================+ 3  |   Value   |  Definition                        |=3  |-----------+------------------------------------|=3  |     0h    |  Restricted reordering             |d3  |     1h    |  Unrestricted reordering allowed   |-3  |  2h - 7h  |  Reserved                          |-3  |  8h - Fh  |  Vendor-specific                   | 3  +================================================+       H  A value of zero in this field specifies that the target shall order theG  actual execution sequence of the commands with a SIMPLE QUEUE tag such+H  that data integrity is maintained for that initiator.  This means that,K  if the transmission of new commands is halted at any time, the final value)J  of all data observable on the medium shall have exactly the same value asE  it would have if the commands had been executed in the same received H  sequence without tagged queuing.  The restricted reordering value shall  be the default value.   G  A value of one in this field specifies that the target may reorder the I  actual execution sequence of the commands with a SIMPLE QUEUE tag in any H  manner.  Any data integrity exposures related to command sequence orderA  are explicitly handled by the initiator through the selection of .  appropriate commands and queue tag messages.    E  A queue error management (QErr) bit of zero specifies that remaining=C  suspended I/O process shall resume after the contingent allegiance=C  condition or extended contingent allegiance condition (see 7.8).  i  cH  A QErr bit of one specifies all remaining suspended I/O processes shallA  be aborted after the contingent allegiance condition or extendednG  contingent allegiance condition (see 7.8).  A unit attention conditioneI  (see 7.9) shall be generated for each initiator that had a suspended I/OnA  process aborted except for the initiator that had the contingentuG  allegiance condition or extended contingent allegiance condition.  TheyI  target shall set the additional sense code to TAGGED COMMANDS CLEARED BYd  ANOTHER INITIATOR.f  dI  A disable queuing (DQue) bit of zero specifies that tagged queuing shallfE  be enabled if the target supports tagged queuing.  A DQue bit of oneoJ  specifies that tagged queuing shall be disabled.  Any queued commands forE  that I_T_x nexus shall be aborted.  Any subsequent queue tag message E  received shall be rejected with a MESSAGE REJECT message and the I/O8>  process shall be executed as an untagged command (see 7.8.1).  eJ  An enable extended contingent allegiance (EECA) bit of one specifies thatJ  extended contingent allegiance is enabled (see 7.7).  An EECA bit of zero;  specifies that extended contingent allegiance is disabled.r  rH  The RAENP, UAAENP, and EAENP bits enable specific events to be reportedK  via the asynchronous event notification protocol.  When all three bits areyD  zero, the target shall not create asynchronous event notifications.   H  A ready AEN permission (RAENP) bit of one specifies that the target may=  issue an asynchronous event notification upon completing itsnK  initialization sequence instead of generating a unit attention condition. lA  A RAENP bit of zero specifies that the target shall not issue anfC  asynchronous event notification upon completing its initializationi
  sequence.  tO     NOTE 100 If the target's default value for the RAENP bit is one and it does4P     not implement saved parameters or include a hardware switch, then it may notI     be possible to disable the initialization sequence asynchronous event=     notification.-  =G  A unit attention AEN permission (UAAENP) bit of one specifies that the H  target may issue an asynchronous event notification instead of creatingK  a unit attention condition upon detecting an event that would cause a unit=B  attention condition (other than upon completing an initializationK  sequence).  A UAAENP bit of zero specifies that the target shall not issue-H  an asynchronous event notification instead of creating a unit attention  condition.   gI  An error AEN permission (EAENP) bit of one specifies that the target may-I  issue an asynchronous event notification upon detecting a deferred error F  condition instead of waiting to report the deferred error on the nextJ  command.  An EAENP bit of zero specifies that the target shall not reportB  deferred error conditions via an asynchronous event notification.   A  The ready AEN holdoff period field specifies the minimum time in=I  milliseconds after the target starts its initialization sequence that itaL  shall delay before attempting to issue an asynchronous event notification. 2  This value may be rounded up as defined in 7.5.4.  d  8. Disconnect-reconnect pageh  OH  The disconnect-reconnect page (see table 98) provides the initiator the/  means to tune the performance of the SCSI bus.o  i:                       Table 98 - Disconnect-reconnect pageP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+========+========+=====================================================|P  | 0   |   PS   |Reserved|         Page code (02h)                             |P  |-----+-----------------------------------------------------------------------|P  | 1   |                           Page length (0Eh)                           |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Buffer full ratio                           |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Buffer empty ratio                          |P  |-----+-----------------------------------------------------------------------|P  | 4   | (MSB)                                                                 |P  |-----+---                        Bus inactivity limit                     ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   | (MSB)                                                                 |P  |-----+---                        Disconnect time limit                    ---|P  | 7   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 8   | (MSB)                                                                 |P  |-----+---                        Connect time limit                       ---|P  | 9   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 10  | (MSB)                                                                 |P  |-----+---                        Maximum burst size                       ---|P  | 11  |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 12  |                           Reserved                  |      DTDC       |P  |-----+-----------------------------------------------------------------------|P  | 13  |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 14  |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 15  |                           Reserved                                    |P  +=============================================================================+  e  hI  The buffer full ratio field indicates to the target, on read operations,oJ  how full the buffer should be prior to attempting a reselection.  TargetsK  that do not implement the requested ratio should round down to the nearest='  implemented ratio as defined in 7.5.4.=  -K  The buffer empty ratio field indicates to the target, on write operations, K  how empty the buffer should be prior to attempting a reselection.  Targets K  that do not implement the requested ratio should round down to the nearest='  implemented ratio as defined in 7.5.4.    G  The buffer full and buffer empty ratios are numerators of a fractional-G  multiplier that has 256 as its denominator.  A value of zero indicates|H  that the target determines when to initiate reselection consistent withK  the disconnect time limit parameter.  These parameters are advisory to the-  target.   M     NOTE 101 As an example, consider a target with ten 512-byte buffers and a|8     specified buffer full ratio of 3Fh.  The formula is:Q     INTEGER((ratio/256)*number of buffers).  Thus INTEGER((3Fh/256)*10) = 2.  The O     target should attempt to reselect the initiator on read operations whenever-!     two or more buffers are full.E   D  The bus inactivity limit field indicates the maximum time in 100 usI  increments that the target is permitted to assert the BSY signal without|I  a REQ/ACK handshake.  If the bus inactivity limit is exceeded the target H  shall attempt to disconnect if the initiator has granted the disconnectH  privilege (see 6.6.7) and it is not restricted by DTDC.  This value mayI  be rounded as defined in 7.5.4.  A value of zero indicates that there isf  no bus inactivity limit.|  |E  The disconnect time limit field indicates the minimum time in 100 us(J  increments that the target shall wait after releasing the SCSI bus beforeI  attempting reselection.  This value may be rounded as defined in 7.5.4. pB  A value of zero indicates that there is no disconnect time limit.  rB  The connect time limit field indicates the maximum time in 100 usA  increments that the target is allowed to use the SCSI bus beforemJ  disconnecting, if the initiator has granted the disconnect privilege (seeG  6.6.7) and it is not restricted by DTDC.  This value may be rounded assK  defined in 7.5.4.  A value of zero indicates that there is no connect time=  limit.=  =K  The maximum burst size field indicates the maximum amount of data that the F  target shall transfer during a data phase before disconnecting if theI  initiator has granted the disconnect privilege.  This value is expressedoK  in increments of 512 bytes (e.g. a value of one means 512 bytes, two means|G  1024 bytes, etc.).  A value of zero indicates there is no limit on the=-  amount of data transferred per connection.  e   I  The data transfer disconnect control (DTDC) field (see table 99) definest8  further restrictions on when a disconnect is permitted.  t=                   Table 99 - Data transfer disconnect controlsP  +=======-=====================================================================+P  | DTDC  |  Description                                                        |P  |-------+---------------------------------------------------------------------|P  |  00b  |  Data transfer disconnect control is not used.  Disconnect is       |P  |       |  controlled by the other fields in this page.                       |P  |  01b  |  A target shall not attempt to disconnect once the data transfer of |P  |       |  a command has started until all data the command is to transfer has|P  |       |  been transferred.  The connect time limit and bus inactivity limit |P  |       |  are ignored during the data transfer.                              |P  |  10b  |  Reserved                                                           |P  |  11b  |  A target shall not attempt to disconnect once the data transfer of |P  |       |  a command has started, until the command is complete.  The connect |P  |       |  time limit and bus inactivity limit are ignored once data transfer |P  |       |  has started.                                                       |P  +=============================================================================+  t  dG  If DTDC is non-zero and the maximum burst size is non-zero, the target D  shall return CHECK CONDITION status.  The sense key shall be set toF  ILLEGAL REQUEST and the additional sense code set to ILLEGAL FIELD IN  PARAMETER LIST. c  e  8.3.3.3 Peripheral device page   bK  The peripheral device page (see table 100) is used to pass vendor-specificaF  information between an initiator and a peripheral interface below theB  target (i.e. between the target and the peripheral device).  ThisJ  International Standard does not define the format of this data, except to  provide a standard header.   o9                        Table 100 - Peripheral device pagegP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+========+========+=====================================================|P  | 0   |   PS   |Reserved|         Page code (09h)                             |P  |-----+-----------------------------------------------------------------------|P  | 1   |                           Page length (n-1)                           |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                        Interface identifier                     ---|P  | 3   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 8   |                                                                       |P  |-----+---                        Vendor-specific                          ---|P  | n   |                                                                       |P  +=============================================================================+  a  t9  Interface identifier codes are defined in the table 101.b  r;                      Table 101 - Interface identifier codesTP  +=================-======================================-====================+P  |                 |                                      |       ANSI         |P  |   Code value    |               Interface              | Reference standard |P  |-----------------+--------------------------------------+--------------------|P  |      0000h      |  Small computer cystem interface     |  X3.131-1986       |P  |      0001h      |  Storage module interface            |  X3.91M-1990       |P  |      0002h      |  Enhanced small device interface     |  X3.170A-1991      |P  |      0003h      |  Intelligent peripheral interface-2  |  X3.130-1986;      |P  |                 |                                      |    X3T9.3/87-002   |P  |      0004h      |  Intelligent peripheral interface-3  |  X3.132-1987;      |P  |                 |                                      |    X3.147-1988     |P  |  0005h - 7FFFh  |  Reserved                            |                    |P  |  8000h - FFFFh  |  Vendor-specific                     |                    |P  +=============================================================================+   $  8.3.4 Vital product data parameters  -I  This clause describes the optional vital product data page structure and|H  the vital product data pages (see table 102) that are applicable to allJ  SCSI devices.  These pages are optionally returned by the INQUIRY commandJ  (8.2.5) and contain vendor-specific product information about a target orI  logical unit.  The vital product data may include vendor identification,-K  product identification, unit serial numbers, device operating definitions, J  manufacturing data, field replaceable unit information, and other vendor-I  specific information.  This International Standard defines the structure 1  of the vital product data, but not the contents.-  -<                    Table 102 - Vital product data page codesP  +=============-==================================================-============+P  |  Page code  |  Description                                     | Subclause  |P  |-------------+--------------------------------------------------+------------|P  |     82h     |  ASCII implemented operating definition page     |  8.3.4.1   |P  |  01h - 7Fh  |  ASCII information page                          |  8.3.4.2   |P  |     81h     |  Implemented operating definitions page          |  8.3.4.3   |P  |     00h     |  Supported vital product data pages              |  8.3.4.4   |P  |     80h     |  Unit serial number page                         |  8.3.4.5   |P  |  83h - BFh  |  Reserved                                        |            |P  |  C0h - FFh  |  Vendor-specific                                 |            |P  +=============================================================================+  -  -4  8.3.4.1 ASCII implemented operating definition page  -I  The ASCII implemented operation definition page (see table 103) contains D  operating definition description data for all operating definitionsH  implemented by the target.  The contents of this data is not defined by  this International Standard.    B                Table 103 - ASCII implemented operating definition P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+==========================+============================================|P  | 0   | Peripheral qualifier     |           Peripheral device type           |P  |-----+-----------------------------------------------------------------------|P  | 1   |                           Page code (82h)                             |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Page length (n-3)                           |P  |-----+-----------------------------------------------------------------------|P  | 4   |              ASCII operating definition description length (m-4)      |P  |-----+-----------------------------------------------------------------------|P  | 5   |                                                                       |P  |- - -+---           ASCII operating definition description data           ---|P  | m   |                                                                       |P  |-----+-----------------------------------------------------------------------|P  | m+1 |                                                                       |P  |- - -+---           Vendor-specific description data                      ---|P  | n   |                                                                       |P  +=============================================================================+  t  tH  The peripheral qualifier field and the peripheral device type field are  as defined in 8.2.5.1.o  eH  The page length field specifies the length of the following page data. C  If the allocation length is less than the length of the data to beaK  returned, the page length shall not be adjusted to reflect the truncation.b  bF  The ASCII operating definition description length field specifies theH  length in bytes of the ASCII operating definition description data thatI  follows.  If the allocation length is less than the length of data to becI  returned, the ASCII operating definition description length shall not beiC  adjusted to reflect the truncation.  A value of zero in this fieldaA  indicates that no ASCII operating definition description data isc  available.   sI  The ASCII operating definition description data field contains the ASCIIsK  operating definition description data for the target or logical unit.  TheiH  data in this field shall be formatted in lines (or character strings). I  Each line shall contain only graphic codes (i.e. code values 20h throughf;  7Eh) and shall be terminated with a NULL (00h) character.       8.3.4.2 ASCII information pagef  dG  The ASCII information page (see table 104) returns information for the=D  field replaceable unit code returned in the REQUEST SENSE data (see  8.2.14).      9                        Table 104 - ASCII information page-P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+==========================+============================================|P  | 0   | Peripheral qualifier     |           Peripheral device type           |P  |-----+-----------------------------------------------------------------------|P  | 1   |                           Page code (01h - 7Fh)                       |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Page length (n-3)                           |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           ASCII length (m-4)                          |P  |-----+-----------------------------------------------------------------------|P  | 5   |                                                                       |P  |- - -+---                        ASCII information                        ---|P  | m   |                                                                       |P  |-----+-----------------------------------------------------------------------|P  | m+1 |                                                                       |P  |- - -+---                        Vendor-specific information              ---|P  | n   |                                                                       |P  +=============================================================================+      H  The peripheral qualifier field and the peripheral device type field are  defined in 8.2.5.1.   I  The page code field contains the same value as in the page code field of=H  the INQUIRY command descriptor block (see 8.2.5) and is associated withG  the field replaceable unit code returned by the REQUEST SENSE command.-  -P     NOTE 102 The field replaceable unit field in the sense data provides for 255L     possible codes, while the page code field provides for only 127 possibleM     codes.  Thus it is not possible to return ASCII information pages for the      upper code values.   H  The page length field specifies the length of the following page data. I  If the allocation length of the command descriptor block is too small to K  transfer all of the page, the page length shall not be adjusted to reflect-  the truncation.  -B  The ASCII length field specifies the length in bytes of the ASCIIE  information that follows.  If the allocation length is less than the-J  length of the data to be returned, the ASCII length shall not be adjustedI  to reflect the truncation.  A value of zero in this field indicates that-?  no ASCII information is available for the specified page code.|   F  The ASCII information field contains ASCII information concerning theF  field replaceable unit identified by the page code.  The data in thisG  field shall be formatted in one or more lines (or character strings).  I  Each line shall contain only graphic codes (i.e. code values 20h through-;  7Eh) and shall be terminated with a NULL (00h) character.     H  The contents of the vendor-specific information field is not defined in  this International Standard.    .  8.3.4.3 Implemented operating definition page   F  The implemented operating definition page (see table 105) defines theH  current operating definition, the default operating definition, and theB  operating definitions implemented by the target.  These operatingF  definition values are specified in the CHANGE DEFINITION command (see  8.2.1).  =@                Table 105 - Implemented operating definition pageP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+==========================+============================================|P  | 0   | Peripheral qualifier     |           Peripheral device type           |P  |-----+-----------------------------------------------------------------------|P  | 1   |                           Page code (81h)                             |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Page length (n-3)                           |P  |-----+-----------------------------------------------------------------------|P  | 4   |Reserved|         Current operating definition                         |P  |-----+--------+--------------------------------------------------------------|P  | 5   | SavImp |         Default operating definition                         |P  |-----+--------+--------------------------------------------------------------|P  | 6   | SavImp |                                                              |P  |-----+---     +         Supported operating definition list               ---|P  | n   | SavImp |                                                              |P  +=============================================================================+  .  hH  The peripheral qualifier field and the peripheral device type field are  defined in 8.2.5.1.  -F  The page length field specifies the length of the following operatingJ  definitions.  If the allocation length of the command descriptor block isD  too small to transfer all of the page, the page length shall not be$  adjusted to reflect the truncation.  -G  For each operating definition, there is an associated save implementedSE  (SavImp) bit.  A SavImp bit of zero indicates that the corresponding E  operating definition parameter cannot be saved.  A SavImp bit of one G  indicates that the corresponding operating definition parameter can be4  saved.|   K  All returned operating definitions use the codes defined in table 33.  The|D  current operating definition field returns the value of the presentH  operating definition.  If no operating definition is saved, the defaultI  operating definition field returns the value of the operating definition K  the target uses when power is applied.  The supported operating definition=J  list returns one or more operating definitions implemented by the target.  t+  8.3.4.4 Supported vital product data pagesn  f?  The supported vital product data pages are shown in table 106.c  t?                  Table 106 - Supported vital product data pagestP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+==========================+============================================|P  | 0   | Peripheral qualifier     |           Peripheral device type           |P  |-----+-----------------------------------------------------------------------|P  | 1   |                           Page code (00h)                             |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Page length (n-3)                           |P  |-----+-----------------------------------------------------------------------|P  | 4   |                                                                       |P  |-----+---                        Supported page list                      ---|P  | n   |                                                                       |P  +=============================================================================+      H  The peripheral qualifier field and the peripheral device type field are  defined in 8.2.5.1.   H  The page code field shall be set to the value of the page code field in2  the INQUIRY command descriptor block (see 8.2.5).  -H  The page length field specifies the length of the supported page list. G  If the allocation length is too small to transfer all of the page, the =  page length shall not be adjusted to reflect the truncation.a   H  The supported page list field shall contain a list of all vital productH  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  lJ  This page (see table 107) provides a product serial number for the target  or logical unit.d  e9                       Table 107 - Unit serial number pageoP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+==========================+============================================|P  | 0   | Peripheral qualifier     |           Peripheral device type           |P  |-----+-----------------------------------------------------------------------|P  | 1   |                           Page code (80h)                             |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Page length (n-3)                           |P  |-----+-----------------------------------------------------------------------|P  | 4   |                                                                       |P  |- - -+---                        Product serial number                    ---|P  | n   |                                                                       |P  +=============================================================================+      H  The peripheral qualifier field and the peripheral device type field are  defined in 8.2.5.1.   J  The page length field specifies the length of the product serial number. G  If the allocation length is too small to transfer all of the page, thea=  page length shall not be adjusted to reflect the truncation.   -D  The product serial number field contains ASCII data that is vendor-K  specific. The least significant ASCII character of the serial number shall G  appear as the last byte of a successful data transfer.  If the product-K  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-  -F  Direct-access devices store blocks of data for later retrieval.  EachI  block of data is stored at a unique logical block address.  An initiator-I  issues WRITE commands to store the blocks of data (write operations) and4G  READ commands to retrieve the blocks of data (read operations).  Other-J  commands issued by the initiator may also cause write and read operationsH  to occur. A write operation causes a block of data to be written on theE  medium.  A read operation causes a block of data to be read from the F  medium.  A verify operation confirms that a block of data can be read  without error from the medium.-  -H  Blocks of data are stored by a process that causes localized changes orH  transitions within the medium.  The changes made to the medium to storeF  the blocks of data may be volatile (i.e. not retained through a powerI  cycle) or non-volatile (retained through a power cycle).  The medium may=K  be divided in parts that are used for data blocks, parts that are reservedeB  for defect management, and parts that are reserved for use by the-  controller for the management of the device.d  n  9.1.1 Removable mediumn  eG  The medium may be removable (e.g. used in a floppy disk drive) or non-nK  removable (e.g. used in a hard disk drive).  Removable medium is containedTB  within a cartridge (or jacket) to prevent damage to the recordingD  surfaces. The combination of medium and cartridge is often called a  volume.  rG  A volume has an attribute of being mounted or de-mounted on a suitablerH  transport mechanism.  A volume is mounted when the direct-access deviceD  is capable of performing write or read operations to the medium.  AJ  mounted volume may not be accessible by an initiator if it is reserved byJ  another initiator.  A volume is de-mounted at any other time (e.g. during#  loading, unloading, or storage).  i   J  An initiator may check whether a volume is mounted by issuing a TEST UNITK  READY command.  A volume that is loaded may need a START STOP UNIT commandh:  issued to become accessible for write or read operations.  nI  The PREVENT ALLOW MEDIUM REMOVAL command allows an initiator to restrictaD  the demounting of the volume.  This is useful in maintaining systemH  integrity. If the direct-access device implements cache memory, it mustJ  ensure that all logical blocks of the medium contain the most recent dataI  prior to permitting demounting of the volume.  If the initiator issues apF  START STOP UNIT command to eject the cartridge, and the direct-accessH  device is prevented from demounting by the PREVENT ALLOW MEDIUM REMOVALF  command, the START STOP unit command is rejected by the direct-access  device.  e   Logical blocks  nJ  Blocks of data are stored on the medium along with additional informationJ  that the controller uses to manage the storage and retrieval.  The formatI  of the additional information is unique and is hidden from the initiatorgH  during normal read or write operations.  This additional information isK  often used to identify the physical location of the blocks of data and theeI  address of the logical block, and to provide protection against the loss=  of the user data.   I  The address of the first logical block is zero.  The address of the last B  logical block is [n-1], where [n] is the number of logical blocksC  available on the medium.  A READ CAPACITY command may be issued to=K  determine the value of [n-1].  If a command is issued that requests accesscI  to a logical block not within the capacity of the medium, the command is-"  terminated with CHECK CONDITION.    I  The number of bytes of data contained in a logical block is known as the+J  block length.  Each logical block has a block length associated with it. I  The block length may be different for each logical block on the medium.  K  However, in a typical device only one block length is used at a time.  The-I  block descriptor in the MODE SENSE data describes the block lengths that E  are used on the medium.  A MODE SELECT command can be used to set up-J  extents.  An extent is a specified number of logical blocks that have theJ  specified block length.  The FORMAT UNIT command is typically required toK  change the block length of devices that support variable block lengths andn)  make the extents that were setup active.-  +K  The location of a logical block on the medium does not have a relationship6I  to the location of any other logical block. However, in a typical device|J  the logical blocks are located in an ascending order.  The time to accessG  the logical block at address [x] and then the logical block at address K  [x+1] need not be less than time to access [x] and then [x+100].  The READ=E  CAPACITY with a PMI bit of one is useful in determining where longeri  access times occur. d  e  9.1.3 Ready state   C  A direct-access device is ready when medium access commands can beaG  executed.  A device using removable media is usually not ready until alG  volume is mounted.  Such a device, with a volume not mounted, normally D  returns CHECK CONDITION status and sets the sense key to NOT READY.  iI  Some direct-access devices may be switched from being ready to being notoF  ready by using the START STOP UNIT command.  An initiator may need to4  issue a START UNIT command to bring a device ready.     9.1.4 Initializationt   I  Many direct-access devices require initialization prior to write or readiG  operations.  This initialization is usually performed by a FORMAT UNITo=  command.  Parameters related to the geometry and performance.E  characteristics can be set with the MODE SELECT command prior to theoJ  format operation.  Some devices are initialized by means not specified inH  this International Standard.  The time at which this occurs is specific3  to the implementation of the direct-access device.r  .K  Devices using a non-volatile medium typically save the parameters and onlypH  need to be initialized once.  However, some mode parameters may need toI  be initialized after each power-on and reset.  A catastrophic failure of=C  the direct-access device may require the FORMAT UNIT command to be   reissued.     F  Devices that use a volatile medium may need to be initialized at eachC  power-on prior to the execution of read or write operations.  Mode=)  parameters may also need initialization.=  =  9.1.5 Medium defectsP  pH  Any medium has the potential for defects that can cause user data to beI  lost.  Therefore, each logical block may contain information that allows J  the detection of changes to the user data caused by defects in the mediumD  or other phenomena, and may also allow the data to be reconstructedD  following the detection of such a change.  Some devices provide theJ  initiator control through use of the mode parameters.  Some devices allowH  the initiator to examine and modify the additional information by usingE  the READ LONG and WRITE LONG commands.  Some media having a very low-9  probability of defects may not require these structures.    H  Defects may also be detected and managed during execution of the FORMATF  UNIT command.  The FORMAT UNIT command defines four sources of defectD  information.  These defects may be reassigned or avoided during theF  initialization process so that they do not appear in a logical block.  =H  Defects may also be avoided after initialization.  The initiator issuesF  a REASSIGN BLOCKS command to request that the specified logical blockI  address be reassigned to a different part of the medium.  This operationcK  can be repeated if a new defect appears at a later time.  The total numbereK  of defects that may be handled in this manner can be specified in the modet  parameters.   H  Defect management on direct-access devices is usually vendor-specific. C  Devices not using a removable medium typically optimize the defectvD  management for capacity or performance or both.  Devices that use aG  removable medium typically do not support defect management (e.g. some J  floppy disk drives) or use defect management that is based on the ability  to interchange the medium.o  a  9.1.6 Data cache    F  Some direct-access devices implement cache memory.  A cache memory isH  usually an area of temporary storage in the direct-access device with aA  fast access time that is used to enhance performance.  It exists G  separately from the blocks of data stored and is normally not directly D  accessible by the initiator.  Use of cache memory for write or readH  operations typically reduces the access time to a logical block and can(  increase the overall data throughput.    -J  During read operations, the direct-access device uses the cache memory toI  store blocks of data that the initiator may request at some future time.-B  The algorithm used to manage the cache memory is not part of thisH  International Standard.  However, parameters are provided to advise theF  direct-access device about future requests, or to restrict the use of(  cache memory for a particular request.    H  During write operations, the direct-access device uses the cache memoryF  to store data that is written to the medium at a later time.  This isF  called a write-back caching algorithm.  Thus the command may completeK  prior to blocks of data being written to the medium.  As a result of using K  a write-back caching algorithm there is a period of time when the data may D  be lost if a power or a hardware failure occurs.  There is also theK  possibility of an error occurring during the write operation.  If an erroreG  occurred during the write, it may be reported as a deferred error on ahI  later command.  However, the initiator can request write-through cachingi.  to prevent these circumstances from arising.    K  When the cache memory fills up with blocks of data that are being kept foreD  possible future access, new blocks of data that are to be kept mustI  replace those currently in cache memory.  The disable page out (DPO) bitaJ  is used to control replacement of logical blocks in the cache.  For writeH  operations, setting this bit to one advises the direct-access device toJ  not replace existing blocks in the cache memory with the write data.  ForH  read operations, setting this bit to one causes blocks of data that are=  being read to not replace existing ones in the cache memory.l  oJ  Sometimes the initiator may wish to have the blocks of data read from theJ  medium instead of from the cache memory.  The force unit access (FUA) bitC  is used to indicate that the direct-access device shall access thecG  physical medium.  For a write operation, setting FUA to one causes thecG  direct-access device to complete the data write to the physical medium I  before completing the command.  For a read operation, setting FUA to onebF  causes the logical blocks to be retrieved from the physical medium.    dI  When the DPO and FUA bits are both set to one, write and read operationsw  bypass the cache memory.g  mJ  When a VERIFY command is executed, a forced unit access is implied, sinceJ  the blocks of data stored on the medium are being verified.  Furthermore,C  a SYNCHRONIZE CACHE operation (see below) is also implied to writelJ  unwritten blocks of data still in the cache memory.  These blocks of dataI  must be stored on the medium before the verify operation can begin.  The J  DPO bit is provided since the VERIFY command may cause the replacement ofE  blocks in the cache.  The above also applies to the WRITE AND VERIFY.	  command.   iG  Commands may be implemented by the direct-access device that allow thee:  initiator to control other behaviour of the cache memory:  iN  =      LOCK UNLOCK CACHE controls whether certain logical blocks will be heldK         in the data cache for future use.  Locking a logical block prevents N         its replacement by a future access.  Unlocking a logical block exposesB         it to possible replacement by a future access (see 9.2.2).   K  =      PRE-FETCH causes a set of logical blocks requested by the initiator N         to be read into the data cache for possible future access.  The blocksL         fetched are subject to later replacement unless they are locked (see         9.2.3).y  eL  =      SYNCHRONIZE CACHE forces any pending write data in the requested setL         of logical blocks to be stored in the physical medium.  This commandF         can be used to ensure that the data was written and any errors         reported (see 9.2.18).  cG  =      The MODE SELECT command defines a page for the control of cachelH         behavior and handles certain basic elements of cache replacement!         algorithms (see 9.3.3.1).i  t  9.1.7 ReservationsS   C  The access enabled or access disabled condition determines when ansI  initiator may store or retrieve user data on all or part of the medium. hJ  Access may be restricted for read operations, write operations, or both. D  This attribute may be controlled by an external mechanism or by the6  RESERVE and RELEASE commands (see 9.2.12 and 9.2.11).  gJ  The RESERVE and RELEASE commands define how different types of restrictedD  access may be achieved, and to whom the access is restricted.  ThisH  subclause describes the interaction of the initiator that requested the'  reservation, and the other initiators.n  hH  An initiator uses reservations to gain a level of exclusivity in accessE  to all or part of the medium for itself or another initiator.  It issD  expected that the reservation will be retained until released.  TheI  direct-access device must ensure that the initiator with the reservationcE  is able to access the reserved media within the operating parametersi!  established by that initiator.     oE  The following paragraphs explain, on a command by command basis, therI  appropriate target response when a reservation exists.  Unless otherwiseiI  noted, the appropriate response to an initiator that issues a command toa@  a direct-access device that is reserved to another initiator is  RESERVATION CONFLICT status.t  mJ  The CHANGE DEFINITION command is dealt with as follows.  If any initiatorH  has an extent reservation on a direct-access device, no other initiatorE  may affect the operating definition of that initiator by use of thiseA  command.  If the direct-access device allows different operating H  definitions for each initiator, then there is no conflict; otherwise, a  reservation conflict occurs.    B  The COMPARE, COPY, and COPY AND VERIFY commands are evaluated forK  reservation conflict as if they were normal write and read operations evenkI  when a direct-access device is requested to copy to or from itself.  For I  example, if a COPY is issued to logical unit 0 that requests the direct-eG  access device to copy from logical unit 0 to logical unit 1, access tos4  logical unit 1 must also be evaluated for conflict.   K  The FORMAT UNIT, PREVENT ALLOW MEDIUM REMOVAL (with a prevent bit of one),iH  REZERO UNIT, and START STOP UNIT commands return a RESERVATION CONFLICTK  status if any other initiator has an extent reservation on a direct-accesse  device.  oG  The INQUIRY and REQUEST SENSE commands are not affected by any kind of 
  reservation.   lK  The LOG SELECT, LOG SENSE, MODE SENSE, TEST UNIT READY, READ CAPACITY (PMIsK  set to zero), READ BUFFER, WRITE BUFFER, and READ DEFECT DATA commands aret'  not affected by extent reservations.  g  aK  The SEEK, LOCK UNLOCK CACHE, PRE-FETCH, and SYNCHRONIZE CACHE commands aremH  evaluated for reservation conflict as if they were normal write or read  operations.  tI  The MODE SELECT command is dealt with as follows. If an initiator has anrD  extent reservation on a direct-access device, and another initiatorE  attempts one of these commands, a reservation conflict occurs if the.F  command affects the manner in which access of the extent by the firstF  initiator is performed.  If the command does not affect access to theI  extent, or parameters are saved for each initiator, then a conflict doesf  not occur.   mJ  The SEND DIAGNOSTIC, RECEIVE DIAGNOSTIC RESULTS commands conflict with anJ  extent reservation only if they affect access to the extent (as with MODE	  SELECT).o  mJ  The REASSIGN BLOCKS command may not reassign a block that is in an extent  reserved to another initiator.d  cG  The SET LIMITS command generates a reservation conflict if the logical E  blocks specified are within an extent reserved to another initiator.a   K  ALL other commands are that request read or write operations are evaluatedt>  for reservation conflict as described in the RESERVE command.   H  When a system is integrated with more than one initiator, there must beJ  agreement between the initiators as to how media is reserved and releasedJ  during operations, otherwise, an initiator may be locked out of access toH  a target in the middle of an operation.  For example, initiator 'A' hasG  a write operation in progress to a direct-access device which has datatI  stored in cache memory.  Then, initiator 'B' issues a RESERVE command toiG  the direct-access device.  As a result, initiator 'A' is locked out ofAJ  issuing a SYNCHRONIZE CACHE command to ensure the integrity of the data. K  To prevent this from happening, initiator 'A' should issue a RESERVE priorc  to the write command.  u  9.1.8 Seek and rezero  oI  The SEEK command provides a way for the initiator to position the devicenF  in preparation for access to a particular logical block at some laterH  time.  Since this positioning action is implicit in other commands, the@  SEEK command may not be useful with some direct-access devices.  SI  The REZERO UNIT command is provided to bring the direct-access device to E  a known condition.  This International Standard does not specify the H  condition.  The REZERO UNIT command is used in some devices to positionH  the actuator at cylinder zero.  Some devices return GOOD status without  attempting any action.   a  9.1.9 Notched drives   iK  A notched (also called partitioned or zoned) drive has areas of the mediumaG  in which the drive geometry changes.  In the simplest case, the entire.G  medium consists of a single notch.  Multiple notches are often used toaH  increase capacity of the drive.  The notch page is used to indicate theF  notch for assignment of values to the parameters in the format deviceJ  page.  By sequencing the notch page through each notch, the format deviceA  parameters of each notch are set.  This is usually done prior tov+  initialization by the FORMAT UNIT command.   a#  9.1.10 Rotational position lockingt   G  Rotational position locking is an optional feature implemented in some I  direct-access devices to allow the synchronization of spindles between aaJ  number of devices.  The rotational position offset feature allows devicesF  to synchronize spindles at offsets from index.  This may be useful inC  improving performance in systems that implement arrays of devices.r  y  9.1.11 Relative addressing-  TJ  Relative addressing is a technique useful in accessing structured data inI  a uniform manner.  Relative addressing is only allowed when commands areeG  linked.  An example of relative addressing and linking for SEARCH DATA A  commands appropriate to direct-access devices is given in 7.4.3.t  cJ  The SET LIMITS command is provided to define the limits of a linked chainF  of relative addressing commands.  This gives an additional protectionJ  against exceeding a particular set of blocks.  The SET LIMITS command has"  no effect on any other initiator.  e  9.1.12 Error reportingh   C  If any of the following conditions occur during the execution of awJ  command, the target shall return CHECK CONDITION status.  The appropriateG  sense key and additional sense code should be set.  The following listmK  illustrates some error conditions and the applicable sense keys.  The listaF  does not provide an exhaustive enumeration of all conditions that may"  cause the CHECK CONDITION status.  oc  Condition                                                                                Sense key o  Invalid logical block address                                                                          ILLEGAL   REQUEST  cs  Unsupported option requested                                                                       ILLEGAL REQUESTc  o|  Target reset or medium change since last command from this initiator                                                         UNIT ATTENTIONh  ar  Self diagnostic failed                                                                             HARDWARE ERROR  lp  Unrecovered read error                                                                          MEDIUM ERROR ora                                                                                    HARDWARE ERRORn  ep  Recovered read error                                                                            RECOVERED ERROR  e|  Overrun or other error that might be resolved by repeating the command                                                       ABORTED COMMAND   r  Attempt to write on write protected medium                                                                   DATA  PROTECT  t   @  In the case of an invalid logical block address, the sense dataI  information field shall be set to the logical block address of the firsta  invalid address.   oI  In the case of an attempt to read a blank or previously unwritten block,hG  the information field shall be set to the logical block address of thetH  first blank block encountered.  The data read up to that block shall be:  transferred (optical memory and write-once devices only).  pI  In the case of an attempt to write a previously written block when blankdG  checking is enabled, the information field shall be set to the logical K  block address of the first non-blank block encountered (optical memory andr  write-once devices only).     9.1.13 Examples  dI  The following examples show some typical variations of the direct-accesse(  device.  Other variations are possible.  g  9.1.13.1 Rotating media  tH  The typical application of a direct-access device is a disk drive.  TheE  medium is a disk coated with a material in which flux changes may be I  induced.  The disk drive allows direct and random access to the medium.  H  This is done with an actuator that positions the read-write head, and aK  rotating disk. Data is stored and retrieved through the interaction of thet  read-write head and the disk.  lJ  The disk is typically divided into cylinders.  Each cylinder is typicallyG  divided into tracks.  Each track is typically divided into sectors.  AoI  cylinder is a set of tracks that can be accessed without movement of thetF  actuator.  A track is a recording path over which the read-write headH  travels during one rotation of the disk.  A sector is a part of a track&  that contains the stored data blocks.  sH  A logical block is stored in one or more sectors, or a sector may storeI  more than one logical block.  A sector is typically made up of a header,eH  data and a trailer.  The header contains a preamble used to synchronizeJ  read circuits to the data, an address field to identify the sector, flagsI  to use for defect management, and a checksum that validates the header. eG  The data contains the block of data.  The trailer contains checksum orsD  error correction information.  The checksum or the error correction>  information allows the correction of data for medium defects.  hK  A disk drive is ready when the disks are rotating at the correct speed andtH  the read-write circuitry is powered and ready to access the disks. SomeG  disks, particularly removable disks, require the user to issue load or-;  start commands to bring the disk drive to the ready state.t  cF  A disk drive will typically have to be formatted prior to the initialI  access.  Exceptions to this are drives that are formatted at the factory,K  and some optical drives with pre-formatted media (see 13.1).  A disk driveeH  format will typically create the headers for each sector and initializeI  the data field.  The MODE SELECT command is often used at format time tovG  establish the geometry (number of heads and tracks, sectors per track,GK  etc.) and defect management scheme.  Disk drives are usually non-volatile.e  rH  The defect management scheme of a disk drive is often shielded from theA  user, though some aspects can be evaluated and controlled by theIK  initiator.  The direct-access device will usually reserve some sectors and I  tracks for recording defect lists and for reassigning defective blocks. cJ  The READ LONG and WRITE LONG commands will typically access the user dataJ  and checksum portions of the data field so that defects may be induced byF  the initiator to test the defect detection logic of the direct-access  device.  aJ  Notches find their most typical use in a rotating disk drive.  On a disk,E  the inner tracks are physically shorter than the outer tracks.  As alI  result, if each track is made to store the same number of data bits, theRH  data is packed more densely on the inner tracks than the outer tracks. F  By using notches, the outer tracks may be made to contain a differentL  number of sectors than the inner tracks, while balancing the data density. $  This results in increased capacity.  r  9.1.13.2 Sequential media   I  Some tape devices are implemented as a direct access device so that they,K  can be used in disk oriented operating system environments.  These devicesCG  are sometimes referred to as random access tape or floppy tape.  TheseSK  devices might be thought of as a disk drive with one or more long tracks. uH  Access time to a logical block is usually longer than for a disk drive,E  since the tape must be fast forwarded or rewound to the block.  As aiI  result, the SEEK command will often be more useful for a tape than for aiI  disk.  The only way an initiator may determine if a direct-access device F  is a tape is by using the medium type code returned by the MODE SENSE	  command.i  r  9.1.13.3 Memory media  aF  Memory media includes devices that are traditionally used for primaryG  storage within computer systems, such as solid state static or dynamicTK  random access memories (SRAM or DRAM), or magnetic core or bubble memory.  E  These devices are typically non-mechanical, and therefore the entire H  physical medium may be accessed in virtually the same access time.  TheH  data is typically accessed as a bit or byte and this also speeds accessI  time.  Memory devices typically store less data than disks or tapes, ande;  are usually volatile when not protected by battery backup.r  h(  9.2 Commands for direct-access devices.  aG  The commands for direct-access devices shall be as shown in table 108.   e?                  Table 108 - Commands for direct-access devices J  +=====================================-============-======-=============+J  |  Command name                       | Operation  | Type | Subclause   |J  |                                     |   code     |      |             |J  |-------------------------------------+------------+------+-------------|J  |  CHANGE DEFINITION                  |    40h     |   O  |   8.2.1     |J  |  COMPARE                            |    39h     |   O  |   8.2.2     |J  |  COPY                               |    18h     |   O  |   8.2.3     |J  |  COPY AND VERIFY                    |    3Ah     |   O  |   8.2.4     |J  |  FORMAT UNIT                        |    04h     |   M  |   9.2.1     |J  |  INQUIRY                            |    12h     |   M  |   8.2.5     |J  |  LOCK-UNLOCK CACHE                  |    36h     |   O  |   9.2.2     |J  |  LOG SELECT                         |    4Ch     |   O  |   8.2.6     |J  |  LOG SENSE                          |    4Dh     |   O  |   8.2.7     |J  |  MODE SELECT(6)                     |    15h     |   O  |   8.2.8     |J  |  MODE SELECT(10)                    |    55h     |   O  |   8.2.9     |J  |  MODE SENSE(6)                      |    1Ah     |   O  |   8.2.10    |J  |  MODE SENSE(10)                     |    5Ah     |   O  |   8.2.11    |J  |  PRE-FETCH                          |    34h     |   O  |   9.2.3     |J  |  PREVENT-ALLOW MEDIUM REMOVAL       |    1Eh     |   O  |   9.2.4     |J  |  READ(6)                            |    08h     |   M  |   9.2.5     |J  |  READ(10)                           |    28h     |   M  |   9.2.6     |J  |  READ BUFFER                        |    3Ch     |   O  |   8.2.12    |J  |  READ CAPACITY                      |    25h     |   M  |   9.2.7     |J  |  READ DEFECT DATA                   |    37h     |   O  |   9.2.8     |J  |  READ LONG                          |    3Eh     |   O  |   9.2.9     |J  |  REASSIGN BLOCKS                    |    07h     |   O  |   9.2.10    |J  |  RECEIVE DIAGNOSTIC RESULTS         |    1Ch     |   O  |   8.2.13    |J  |  RELEASE                            |    17h     |   M  |   9.2.11    |J  |  REQUEST SENSE                      |    03h     |   M  |   8.2.14    |J  |  RESERVE                            |    16h     |   M  |   9.2.12    |J  |  REZERO UNIT                        |    01h     |   O  |   9.2.13    |J  |  SEARCH DATA EQUAL                  |    31h     |   O  |   9.2.14.1  |J  |  SEARCH DATA HIGH                   |    30h     |   O  |   9.2.14.2  |J  |  SEARCH DATA LOW                    |    32h     |   O  |   9.2.14.3  |J  |  SEEK(6)                            |    0Bh     |   O  |   9.2.15    |J  |  SEEK(10)                           |    2Bh     |   O  |   9.2.15    |J  |  SEND DIAGNOSTIC                    |    1Dh     |   M  |   8.2.15    |J  |  SET LIMITS                         |    33h     |   O  |   9.2.16    |J  |  START STOP UNIT                    |    1Bh     |   O  |   9.2.17    |J  |  SYNCHRONIZE CACHE                  |    35h     |   O  |   9.2.18    |J  |  TEST UNIT READY                    |    00h     |   M  |   8.2.16    |J  |  VERIFY                             |    2Fh     |   O  |   9.2.19    |J  |  WRITE(6)                           |    0Ah     |   O  |   9.2.20    |J  |  WRITE(10)                          |    2Ah     |   O  |   9.2.21    |J  |  WRITE AND VERIFY                   |    2Eh     |   O  |   9.2.22    |J  |  WRITE BUFFER                       |    3Bh     |   O  |   8.2.17    |J  |  WRITE LONG                         |    3Fh     |   O  |   9.2.23    |J  |  WRITE SAME                         |    41h     |   O  |   9.2.24    |J  |-----------------------------------------------------------------------|J  |Key:  M = Command implementation is mandatory.                         |J  |      O = Command implementation is optional.                          |J  +=======================================================================+  r  rG  The following operation codes are vendor-specific: 02h, 05h, 06h, 09h, K  0Ch, 0Dh, 0Eh, 0Fh, 10h, 11h, 13h, 14h, 19h, 20h, 21h, 22h, 23h, 24h, 26h, K  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  oJ  The FORMAT UNIT command (see table 109) formats the medium into initiatorB  addressable logical blocks per the initiator defined options.  InD  addition, the medium may be certified and control structures may beC  created for the management of the medium and defects.  There is noe7  guarantee that the medium has or has not been altered.f  a7                         Table 109 - FORMAT UNIT commandhP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (04h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      | FmtData| CmpLst |   Defect list format     |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Vendor-specific                             |P  |-----+-----------------------------------------------------------------------|P  | 3   | (MSB)                                                                 |P  |-----+---                        Interleave                               ---|P  | 4   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+     lG  The simplest mandatory form of the FORMAT UNIT command (with no formataH  data) accomplishes medium formatting with little initiator control overG  defect management.  The target implementation determines the degree ofaK  defect management that is to be performed.  Two additional mandatory formsmJ  of this command increase the initiator's control over defect management. H  Several optional forms of this command further increase the initiator'sK  control over defect management, by allowing the initiator to specify whicheG  defect list(s) are to be used, to specify defect locations (in severaleK  formats), to enable target certification, and to specify what to do in thee-  event that defect lists are not accessible. o  nK  The FORMAT UNIT command shall be rejected with RESERVATION CONFLICT statusrE  if the logical unit is reserved, or any extent reservation, from any 4  initiator, is active in the specified logical unit.  rE  During the format operation, the target shall respond to commands asa
  follows: L     a)     In response to all commands except REQUEST SENSE and INQUIRY, theJ            target shall return CHECK CONDITION status unless a reservationN            conflict exists, in which case RESERVATION CONFLICT status shall be            returned.  tJ     b)     In response to the INQUIRY command, the target shall respond as            commanded.p  lH     c)     In response to the REQUEST SENSE command, unless an error hasL            occurred, the target shall return a sense key of NOT READY and anN            additional sense code of LOGICAL UNIT NOT READY FORMAT IN PROGRESS,L            with the sense key specific bytes set for progress indication (asJ            described in 8.2.14.1).  Refer to 8.2.14.2 for a description ofN            deferred error handling that may occur during the format operation.  lP     NOTE 103 It is recommended that MODE SELECT parameters (if any) be set prior(     to issuing the FORMAT UNIT command.   aH  During the execution of the FORMAT UNIT command, the target may performE  a medium defect management algorithm (which can be controlled by theiJ  initiator, using optional forms of this command).  Four sources of defectH  location information (hereafter called defects) are defined as follows:  tJ  a)     Primary defect list (Plist).  This is the list of defects, usuallyK         supplied by the original manufacturer of the device or medium, thatsN         are considered permanent defects.  The Plist is located outside of theM         initiator-accessible logical block space.  The Plist is accessible byaJ         the target (to reference while formatting), but it is not normallyG         accessible by the initiator except through the READ DEFECT DATAaJ         command.  Once created, the original Plist shall not be subject to         change.n  yF  b)     Target certification list (Clist).  This list includes defectsG         detected by the target during an optional certification processiM         executed during the FORMAT UNIT command.  This list shall be added tou         the Glist.  dI  c)     Data defect list (Dlist).  This list of defect descriptors may be L         supplied to the target by the initiator in the DATA OUT phase of theI         FORMAT UNIT command.  This list shall be added to the Glist.  ThevJ         defect list length in the defect list header may be zero, in which!         case there is no Dlist.  m  aN  d)     Grown defect list (Glist).  The Glist includes all defects sent by theL         initiator or detected by the target.  The Glist does not include theI         Plist.  If the CmpLst bit is zero, the Glist shall include DlistseN         provided to the target during the previous and the current FORMAT UNIT0         commands.  The Glist shall also include:A     a)     defects detected by the format operation during mediuml            certification;eH     b)     defects previously identified with a REASSIGN BLOCKS command;F     c)     defects previously detected by the target and automatically            reallocated..  aB  A format data (FmtData) bit of one indicates that the FORMAT UNITH  parameter list (see table 110) shall be transferred during the DATA OUTH  phase.   The DATA OUT phase consists of a defect list header (see tableI  111), followed by an initialization pattern descriptor, followed by zeroeJ  or more defect descriptors.  Each defect descriptor identifies a locationJ  on the medium that the target shall map out of the user-accessible area.   |  |;                      Table 110 - FORMAT UNIT parameter list8P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  |     |                           Defect list header                          |P  |=====+=======================================================================|P  |     |                           Initialization pattern descriptor (if any)  |P  |=====+=======================================================================|P  |     |                           Defect descriptor(s) (if any)               |P  |=====+=======================================================================|P  | 0   |                           Defect descriptor 0                         |P  |-----+---                  (See specific table for length.)               ---|P  | n   |                                                                       |P  |-----+-----------------------------------------------------------------------|P  |     |                                  .                                    |P  |     |                                  .                                    |P  |-----+-----------------------------------------------------------------------|P  | 0   |                           Defect descriptor x                         |P  |-----+---                  (See specific table for length.)               ---|P  | n   |                                                                       |P  +=============================================================================+     7I  The  defect list header (see table 111) provides several optional format3C  control bits. Targets that implement these bits give the initiator|D  additional control over the use of the four defect sources, and theK  formatting operation. If the initiator attempts to select any function not G  implemented by the target, the target shall terminate the command with K  CHECK CONDITION status.  The sense key shall be set to ILLEGAL REQUEST and K  the additional sense code shall be set to INVALID FIELD IN PARAMETER LIST.    7                          Table 111 - Defect list header P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 1   |  FOV   |  DPRY  |  DCRT  |  STPF  |   IP   |   DSP  |  Immed |   VS   |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                        Defect list length                       ---|P  | 3   |                                                                 (LSB) |P  +=============================================================================+  -  -H  A FmtData bit of zero indicates that a DATA OUT phase shall not occur. 3  The source of defect information is not specified.    H  A complete list (CmpLst) bit of one indicates that the defect list sentJ  by the initiator is a complete list of defects.  Any existing defect listK  except the Plist shall be ignored by the target.  As a result, a new Glist0I  is constructed that contains the Dlist (if it is sent by the initiator), E  and the Clist (if certification is enabled).  The target may add any >  defects it detects during the format operation to this Dlist.  nJ  A CmpLst bit of zero indicates that the defect list sent by the initiatorI  is an addition to the existing list of defects.  As a result a new Glist J  is constructed that contains the existing Glist, the Dlist (if it is sentE  by the initiator), and the Clist (if certification is enabled).  The J  target may add any defects it detects during the format operation to this  Dlist.    F  Table 112 defines the implementation requirements for the FORMAT UNIT	  command.=  =H        Table 112 - FORMAT UNIT defect descriptor format and requirementsP  +=======-======-========-========-======-=====================================+P  |       |      | Defect | Defect |      |                                     |P  |       |      |  list  |  list  |      |                                     |P  |FmtData|CmpLst| format | length | Type |  Comments                           |P  |-------+------+--------+--------+------+-------------------------------------|P  |   0   |   0  |  000b  |   N/A  |   M  |  Vendor-specific                    |P  |-----------------------------------------------------------------------------|P  |                                 BLOCK FORMAT                                |P  |-----------------------------------------------------------------------------|P  |   1   |   0  |  000b  |  Zero  |   M  | See notes (1) and (3)               |P  |   1   |   1  |  000b  |  Zero  |   M  | See notes (1) and (4)               |P  |   1   |   0  |  000b  |   >0   |   O  | See notes (2) and (3)               |P  |   1   |   1  |  000b  |   >0   |   O  | See notes (2) and (4)               |P  |-----------------------------------------------------------------------------|P  |                          BYTES FROM INDEX FORMAT                            |P  |-----------------------------------------------------------------------------|P  |   1   |   0  |  100b  |  Zero  |   O  | See notes (1) and (3)               |P  |   1   |   1  |  100b  |  Zero  |   O  | See notes (1) and (4)               |P  |   1   |   0  |  100b  |   >0   |   O  | See notes (2) and (3)               |P  |   1   |   1  |  100b  |   >0   |   O  | See notes (2) and (4)               |P  |-----------------------------------------------------------------------------|P  |                           PHYSICAL SECTOR FORMAT                            |P  |-----------------------------------------------------------------------------|P  |   1   |   0  |  101b  |  Zero  |   O  | See notes (1) and (3)               |P  |   1   |   1  |  101b  |  Zero  |   O  | See notes (1) and (4)               |P  |   1   |   0  |  101b  |   >0   |   O  | See notes (2) and (3)               |P  |   1   |   1  |  101b  |   >0   |   O  | See notes (2) and (4)               |P  |-----------------------------------------------------------------------------|P  |                           VENDOR-SPECIFIC FORMAT                            |P  |-----------------------------------------------------------------------------|P  |   1   |   0  |  110b  |        |      |                                     |P  |   1   |   1  |  110b  |        |      |                                     |P  |-----------------------------------------------------------------------------|P  |  All remaining codes are reserved.                                          |P  |-----------------------------------------------------------------------------|P  |  Key:  M = Command implementation is mandatory.                             |P  |        O = Command implementation is optional.                              |P  |-----------------------------------------------------------------------------|P  |  NOTES                                                                      |P  |    1  No Dlist is transferred to the target during the DATA OUT phase.      |P  |    2  A Dlist is transferred to the target during the DATA OUT phase.       |P  |       Add the Dlist defects to the new Glist.                               |P  |    3  Use the existing Glist as a defect source.  Add existing Glist        |P  |       defects to the new Glist.                                             |P  |    4  Discard the existing Glist. Do not add existing Glist defects to      |P  |       the new Glist.                                                        |P  |    5  All the options described in this table cause a new Glist to be       |P  |       created during execution of the FORMAT UNIT command as described in   |P  |       the text.                                                             |P  +=============================================================================+     sJ  The defect list format field specifies which defect descriptor is used if(  the FmtData bit is one (see table 112).   K  The interleave field specifies the interleave that is used when performingdI  the format operation.  This allows the logical blocks to be related in a K  way that facilitates matching the transfer rate  between the initiator andeI  the peripheral.  An interleave of zero specifies that the target use itsvE  default interleave.  An interleave of one specifies that consecutivewJ  logical blocks be placed in contiguous ascending order.  All other values  are vendor-specific.s  lI  A format options valid (FOV) bit of zero indicates that the target shallsI  use its default settings for the DPRY, DCRT, STPF, IP and  DSP bits (seetJ  below). The initiator shall set these bits to zero.  If any of these bitsJ  are not zero, the target shall terminate the command with CHECK CONDITIONJ  status.  The sense key shall be set to ILLEGAL REQUEST and the additional=  sense code  shall be set to INVALID FIELD IN PARAMETER LIST.w   H  A FOV bit of one indicates that the target shall examine the setting ofK  the DPRY, DCRT, STPF, IP and DSP bits.  When the FOV bit is one, the DPRY,t4  DCRT, STPF, IP and DSP bits are defined as follows.  lI  A disable primary (DPRY) bit of zero indicates that the target shall not I  use portions of the medium identified as defective in the primary defect F  Plist for initiator addressable logical blocks.  If the target cannotI  locate the Plist or it cannot determine whether a Plist exists, it shalliB  perform the action specified by  the STPF bit.  A DPRY bit of oneH  indicates that the target shall not use the Plist to identify defective0  areas of the medium.  The Plist is not deleted.  -K  A disable certification (DCRT) bit of zero indicates that the target shall G  perform a vendor-specific medium certification operation to generate a J  Clist.  A DCRT bit of one indicates that the target shall not perform anyD  vendor-specific medium certification process or format verification3  operation while executing the FORMAT UNIT command.=  +I  The stop format (STPF) bit controls the behaviour of the target when one|   of the following events occurs:M     a)     The target has been requested to use the primary defect list (DPRY=M            is  set to zero), or the grown defect list (CmpLst is set to zero) O            and the target cannot locate the list nor determine whether the list=            exists.M     b)     The target has been requested to use the primary defect list (DPRYtL            is set to zero) or the grown defect list (CmpLst is set to zero),N            and the target encounters an error while accessing the defect list.   J  A STPF bit of zero indicates that, if one or both of the above conditionsK  occurs, the target shall continue to execute the FORMAT UNIT command.  The K  target shall return CHECK CONDITION status at the completion of the FORMAT E  UNIT command.  The sense key shall be set to RECOVERED ERROR and the-J  additional sense code shall be set to either DEFECT LIST NOT FOUND if theG  first condition occurred, or DEFECT LIST ERROR if the second condition-
  occurred.   I  A STPF bit of one indicates that, if one or both of the above conditions F  occurs, the target shall terminate the FORMAT UNIT command with CHECKF  CONDITION status.  The sense key shall be set to MEDIUM ERROR and theJ  additional sense code shall be set to either DEFECT LIST NOT FOUND if theG  first condition occurred, or DEFECT LIST ERROR if the second conditiono
  occurred.   N     NOTE 104 The use of the FmtData bit, the CmpLst bit, and the defect headerM     allow the initiator to control the source of the defect lists used by thegJ     FORMAT UNIT command. Setting the defect list length to zero allows theO     initiator to control the use of Plist and Clist without having to specify aa
     Dlist.  V  DK  An initialization pattern (IP) bit of one indicates that an initializationiJ  pattern descriptor (see 9.2.1.2) is included in the FORMAT UNIT parameterF  list immediately following the defect list header.  An IP bit of zeroH  indicates that an initialization pattern descriptor is not included and>  that the target shall use its default initialization pattern.  =G  A disable saving parameters (DSP) bit of one specifies that the target I  shall not save the MODE SELECT savable parameters to non-volatile memory-J  during the format operation.  A DSP bit of zero specifies that the targetH  shall save all the MODE SELECT savable parameters for all initiators toE  non-volatile memory during the format operation.  Pages that are not-I  reported as savable are not affected by the DSP bit (i.e. if pages 03h & J  04h are not returned with the PS bit set they may be saved even if DSP is
  cleared).  |I  An immediate (Immed) bit of zero indicates that status shall be returned(E  after the format operation has completed.  An Immed bit value of one=E  indicates that the target shall return status as soon as the commandOI  descriptor block has been validated, and the entire defect list has beeni
  transferred.m  t*  The bit designated VS is vendor-specific.  eK  The defect list length field in the defect list header specifies the totalgK  length in bytes of the defect descriptors that follow and does not include J  the initialization pattern descriptor or initialization pattern, if any. J  The length of the defect descriptors varies with the format of the defectI  list. The three formats for the defect descriptor(s) field in the defectn  lists are shown in 9.2.1.1.     9.2.1.1 Defect list formats  iG  This clause describes the defect list formats used in the FORMAT UNIT, G  READ DEFECT DATA and translate page of the SEND DIAGNOSTIC and RECEIVEi  DIAGNOSTIC RESULTS commands.)  nQ     NOTE 105 The selected reporting format accounts for variables that impact thetN     information in the returned data.  For example, the specific location of aL     defect, while constant in angular and radial location on the device, mayJ     change in reported location a format operation with different geometryN     parameters is performed.  It is the responsibility of the initiator to useP     a defect list format appropriate for the intended operation with the currentL     or future geometry parameters.  If the target is able to detect that theN     selected defect list format would provide inconsistent results, the target&     may return CHECK CONDITION status.  -J  Each block format defect descriptor (see table 113) specifies a four-byte2  defective block address that contains the defect.  ->                   Table 113 - Defect descriptor - Block formatP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   | (MSB)                                                                 |P  |- - -+---                     Defective block address                     ---|P  | 3   |                                                                 (LSB) |P  +=============================================================================+  -  -C  The defect list length is equal to four times the number of defect|
  descriptors.0   D  The defect descriptors should be in ascending order.  More than oneH  physical or logical block may be affected by each defect descriptor.  AG  target may return CHECK CONDITION if the defect descriptors are not in   ascending order.|  1E  Each byte from index defect descriptor (see table 114) specifies the-<  location of a defect that is no more than eight bytes long.  -C             Table 114 - Defect descriptor - Bytes from index format P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   | (MSB)                                                                 |P  |- - -+---                        Cylinder number of defect                ---|P  | 2   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Head number of defect                       |P  |-----+-----------------------------------------------------------------------|P  | 4   | (MSB)                                                                 |P  |- - -+---                        Defect bytes from index                  ---|P  | 7   |                                                                 (LSB) |P  +=============================================================================+      D  The defect list length is equal to eight times the number of defect
  descriptors.    H  Each descriptor is comprised of the cylinder number of defect, the headF  number of defect, and the defect bytes from index to the defect.  TheG  defect descriptors shall be in ascending order. The cylinder number ofdH  defect is the most significant part of the address and the defect bytesH  from index is the least significant part of the address.  More than oneI  physical or logical block may be affected by each defect.  If the defect J  bytes from index has a value of FFFFFFFFh, this indicates that the entire%  track shall be considered defective.    E  Each physical sector defect descriptor (see table 115) specifies thei5  location of a defect that is the length of a sector.    C              Table 115 - Defect descriptor - Physical sector formattP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   | (MSB)                                                                 |P  |- - -+---                        Cylinder number of defect                ---|P  | 2   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Head number of defect                       |P  |-----+-----------------------------------------------------------------------|P  | 4   | (MSB)                                                                 |P  |- - -+---                        Defective sector number                  ---|P  | 7   |                                                                 (LSB) |P  +=============================================================================+  a  nD  The defect list length is equal to eight times the number of defect
  descriptors.e   F  Each descriptor is comprised of a cylinder number of defect, the headK  number of defect, and the defective sector number.  The defect descriptorseH  shall be in ascending order.  The cylinder number of defect is the mostG  significant part of the address and the defective sector number is theSC  least significant part of the address.  More than one block may bezB  affected by each defect descriptor.  A defective sector number ofI  FFFFFFFFh indicates that the entire track shall be considered defective.e  b&  9.2.1.2 Initialization pattern option  lD  The initialization pattern option specifies that the logical blocksJ  contain the specified initialization pattern.  The initialization patternG  descriptor (see table 116) is sent to the target as part of the FORMATe  UNIT parameter list.P  t>                  Table 116 - Initialization pattern descriptorP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=================+=====================================================|P  | 0   |   IP modifier   |                    Reserved                         |P  |-----+-----------------------------------------------------------------------|P  | 1   |                           Pattern type                                |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                Initialization pattern length                    ---|P  | 3   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 4   |                                                                       |P  |-----+---                Initialization pattern                           ---|P  | n   |                                                                       |P  +=============================================================================+  c  iQ     NOTE 106 The initialization pattern option is not intended for media analysisPO     or certification.  This option may only initialize the initiator accessibleeQ     area of the media to the specified pattern and may not write to any initiator #     inaccessible areas of the disk.R  dG  The IP modifier field specifies the type and location of a header that 5  modifies the initialization pattern (see table 117).   t=                   Table 117 - Initialization pattern modifierhP  +=============-===============================================================+P  | IP modifier |   Description                                                 |P  |-------------+---------------------------------------------------------------|P  |     00b     |   No header. The target shall not modify the initialization   |P  |             |   pattern.                                                    |P  |     01b     |   The target shall overwrite the initialization pattern to    |P  |             |   write the logical block address in the first four bytes of  |P  |             |   the logical block.  The logical block address shall be      |P  |             |   written with the most significant byte first.               |P  |     10b     |   The target shall overwrite the initialization pattern to    |P  |             |   write the logical block address in the first four bytes of  |P  |             |   each physical block contained within the logical block.  The|P  |             |   The lowest numbered logical block or part thereof that      |P  |             |   occurs within the physical block is used.  The logical block|P  |             |   address shall be written with the most significant byte     |P  |             |   first.                                                      |P  |     11b     |   Reserved.                                                   |P  +=============================================================================+  n  hI  The initialization pattern type field (see table 118) indicates the typeiH  of pattern the target shall use to initialize each logical block withinD  the initiator accessible portion of the medium.  All bytes within aE  logical block shall be written with the initialization pattern.  ThetI  initialization pattern is modified by the IP modifier field as describedr  in table 117.  o;                     Table 118 - Initialization pattern typeeD  +==============-==================================================+D  |Initialization|  Description                                     |D  | pattern type |                                                  |D  |--------------+--------------------------------------------------|D  |     00h      |  Use default pattern. (note 1)                   |D  |     01h      |  Repeat the initialization pattern as            |D  |              |  required to fill the logical block. (note 2)    |D  |  02h - 7Fh   |  Reserved                                        |D  |  80h - FFh   |  Vendor-specific                                 |D  |-----------------------------------------------------------------|D  |  Notes                                                          |D  |  1)  If the initialization pattern length is not zero the target|D  |  shall terminate the command with CHECK CONDITION status.  The  |D  |  sense key shall be set to ILLEGAL REQUEST and the additional   |D  |  sense code to INVALID FIELD IN PARAMETER LIST.                 |D  |  2)  If the initialization pattern length is zero the target    |D  |  shall terminate the command with CHECK CONDITION status.  The  |D  |  sense key shall be set to ILLEGAL REQUEST and the additional   |D  |  sense code to INVALID FIELD IN PARAMETER LIST.                 |D  +=================================================================+     |F  The initialization pattern length field indicates the number of bytesD  contained in the initialization pattern.  If the length exceeds theG  current logical block size the target shall terminate the command withdK  CHECK CONDITION status.  The sense key shall be set to ILLEGAL REQUEST and L  the additional sense code shall be set to INVALID FIELD IN PARAMETER LIST. 2  The pattern is modified by the IP modifier field.  f      9.2.2 LOCK UNLOCK CACHE command  eG  The LOCK UNLOCK CACHE command (see table 119) requests that the target J  disallow or allow logical blocks within the specified range to be removedK  from the cache memory by the target's cache replacement algorithm.  LockedeI  logical blocks may be written to the medium when modified, but a copy of =  the modified logical block shall remain in the cache memory.a  f:                      Table 119 - LOCK UNLOCK CACHE commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (36h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |         Reserved         |  Lock  | RelAdr |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                                                                       |P  |-----+---                        Logical block address                    ---|P  | 4   |                                                                       |P  |-----+---                                                                 ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   | (MSB)                                                                 |P  |-----+---                        Number of blocks                         ---|P  | 8   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+  h  eJ  A lock bit of one indicates that any logical block in the specified rangeI  that is currently present in the cache memory shall be locked into cache=J  memory.  Only logical blocks that are already present in the cache memoryK  are actually locked.  A lock bit of zero indicates that all logical blocks G  in the specified range that are currently locked into the cache memory=0  shall be unlocked, but not necessarily removed.  SH  A relative address (RelAdr) bit of one indicates that the logical blockD  address field is a two's complement displacement.  This negative orG  positive displacement shall be added to the logical block address last H  accessed on the logical unit to form the logical block address for thisE  command.  This feature is only available when linking commands.  TheoK  feature requires that a previous command in the linked group have accessed-%  a block of data on the logical unit.|   D  A RelAdr bit of zero indicates that the logical block address fieldG  specifies the first logical block of the range of logical blocks to be   operated on by this command.    F  The number of blocks specifies the total number of contiguous logicalJ  blocks within the range.  A number of blocks field of zero indicates thatE  all remaining logical blocks on the logical unit shall be within the 	  range.  s   J  Multiple locks may be in effect from more than one initiator.  Locks fromH  different initiators may overlap.  An unlock of an overlapped area does+  not release the lock of another initiator.e  u  9.2.3 PRE-FETCH command  sH  The PRE-FETCH command (see table 120) requests that the target transferD  the specified logical blocks to the cache memory.  No data shall be  transferred to the initiator.   6                          Table 120 - PRE-FETCH commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (34h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |         Reserved         | Immed  | RelAdr |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                                                                       |P  |-----+---                        Logical block address                    ---|P  | 4   |                                                                       |P  |-----+---                                                                 ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   | (MSB)                                                                 |P  |-----+---                        Transfer length                             |P  | 8   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+  t  oH  An immediate (Immed) bit of one indicates that status shall be returnedJ  as soon as the command descriptor block has been validated.  An Immed bitG  of zero indicates that status shall be returned after the operation isn
  complete.  eK  See 9.2.2 for a definition of the RelAdr bit and the logical block address=  field.|   E  The transfer length field specifies the number of contiguous logical H  blocks of data that shall be transferred to the target's cache memory. J  A transfer length of zero indicates that the contiguous logical blocks upE  to and including the last logical block of the logical unit shall be I  transferred to the target's cache memory.  Any other value indicates thehJ  number of logical blocks that shall be transferred.  The target may electG  to not transfer logical blocks that already are contained in the cacheo  memory.  c?  If the Immed bit is zero and the specified logical blocks were F  successfully transferred to the cache memory, the target shall returnF  CONDITION MET status.  If the link bit (see 7.2.7) is one, the target0  shall return INTERMEDIATE-CONDITION MET status.  oJ  If Immed is one, and the unlocked cache memory has sufficient capacity toD  accept all of the specified logical blocks, the target shall returnF  CONDITION MET status.  If the link bit (see 7.2.7) is one, the target0  shall return INTERMEDIATE-CONDITION MET status.   H  If Immed is one, and the unlocked cache memory does not have sufficientI  capacity to accept all of the specified logical blocks, the target shall G  return GOOD status.  The target shall transfer to cache memory as many E  logical blocks as will fit.  If the link bit (see 7.2.7) is one, the=)  target shall return INTERMEDIATE status.z  o+  9.2.4 PREVENT ALLOW MEDIUM REMOVAL commands  eK  The PREVENT ALLOW MEDIUM REMOVAL command (see table 121) requests that thehI  target enable or disable the removal of the medium in the logical unit. lJ  This mechanism is independent of device reservations and the target shallG  not allow medium removal if any initiator currently has medium removal   prevented.o   @                 Table 121 - PREVENT ALLOW MEDIUM REMOVAL commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (1Eh)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |                  Reserved                  |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved                           | Prevent|P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+      I  The prevention of medium removal shall begin when any initiator issues a G  PREVENT ALLOW MEDIUM REMOVAL command with a prevent bit of one (mediumtK  removal prevented).  The prevention of medium removal for the logical unitr  shall terminate:sH     a)     after all initiators that have medium removal prevented issueL            PREVENT ALLOW MEDIUM REMOVAL commands with a prevent bit of zero,H            and the target has successfully performed a synchronize cache            operation; M     b)     upon the receipt of a BUS DEVICE RESET message from any initiator;m
            or '     c)     upon a hard RESET condition.   aG  While a prevention of medium removal condition is in effect the targetaI  shall inhibit mechanisms that normally allow removal of the medium by anb
  operator.  i  9.2.5 READ(6) command  iK  The READ(6) command (see table 122) requests that the target transfer dataeG  to the initiator.  The most recent data value written in the addressed+#  logical block shall be returned.  =  -5                           Table 122 - READ(6) command P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (08h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      | (MSB)                                      |P  |-----+------------------------------                                      ---|P  | 2   |                           Logical block address                       |P  |-----+---                                                                 ---|P  | 3   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Transfer length                             |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+  -  -G  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 thatI  affect the READ(6) command; however, no default value is defined by this G  International Standard.  If explicit control is required, the READ(10)|  command should be used.  -I  The logical block address field specifies the logical block at which the   read operation shall begin.   E  The transfer length field specifies the number of contiguous logical=G  blocks of data to be transferred.  A transfer length of zero indicatestI  that 256 logical blocks shall be transferred.  Any other value indicates 8  the number of logical blocks that shall be transferred.  l  9.2.6 READ(10) commandr  yG  The READ(10) command (see table 123) requests that the target transfernB  data to the initiator.  The most recent data value written in the,  addressed logical block shall be returned.    6                           Table 123 - READ(10) commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (28h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   |   Logical unit number    |   DPO  |   FUA  |     Reserved    | RelAdr |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                                                                       |P  |-----+---                        Logical block address                    ---|P  | 4   |                                                                       |P  |-----+---                                                                 ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   | (MSB)                                                                 |P  |-----+---                        Transfer length                             |P  | 8   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+  -  -K  A disable page out (DPO) bit of one indicates that the target shall assign J  the logical blocks accessed by this command the lowest priority for beingG  fetched into or retained by the cache.  A DPO bit of one overrides any I  retention priority specified in the cache page (see 9.3.3.1).  A DPO bit D  of zero indicates the priority shall be determined by the retentionG  priority fields in the cache page.  All other aspects of the algorithm|K  implementing the cache memory replacement strategy are not defined by this|  International Standard.   P     NOTE 107 The DPO bit is used to control replacement of logical blocks in theQ     cache memory when the host has information on the future usage of the logical L     blocks.  If the DPO bit is set to one, the host knows the logical blocksK     accessed by the command are not likely to be accessed again in the near N     future and should not be put in the cache memory nor retained by the cacheI     memory.  If the DPO bit is zero, the host expects that logical blocks P     accessed by this command are likely to be accessed again in the near future.  -E  A force unit access (FUA) bit of one indicates that the target shall|L  access the media in performing the command prior to returning GOOD status. H   Read commands shall access the specified logical blocks from the mediaH  (i.e.  the data is not directly retrieved from the cache).  In the caseK  where the cache contains a more recent version of a logical block than theIE  media, the logical block shall first be written to the media.  WriteeD  commands shall not return GOOD status until the logical blocks haveI  actually been written on the media (i.e. the data is not write cached). d  eH  An FUA bit of zero indicates that the target may satisfy the command byJ  accessing the cache memory.  For read operations, any logical blocks thatF  are contained in the cache memory may be transferred to the initiatorJ  directly from the cache memory.  For write operations, logical blocks mayJ  be transferred directly to the cache memory.  GOOD status may be returnedI  to the initiator prior to writing the logical blocks to the medium.  AnyhI  error that occurs after the GOOD status is returned is a deferred error,zG  and information regarding the error is not reported until a subsequentt	  command.m  ,K  See 9.2.2 for a definition of the RelAdr bit and the logical block address   field.h  aE  The transfer length field specifies the number of contiguous logicalsE  blocks of data that shall be transferred.  A transfer length of zero G  indicates that no logical blocks shall be transferred.  This conditionMH  shall not be considered an error.  Any other value indicates the number-  of logical blocks that shall be transferred.e  s  9.2.7 READ CAPACITY command  rC  The READ CAPACITY command (see table 124) provides a means for thelG  initiator to request information regarding the capacity of the logicalt  unit.  c8                        Table 124 - READ CAPACITY commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (25h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |             Reserved              | RelAdr |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                                                                       |P  |-----+---                        Logical block address                    ---|P  | 4   |                                                                       |P  |-----+---                                                                 ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 8   |                           Reserved                           |  PMI   |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+  b  oK  See 9.2.2 for a definition of the RelAdr bit and the logical block addresse  field.u  rH  The logical block address shall be zero if the PMI bit is zero.  If theF  PMI bit is zero and the logical block address is not zero, the targetE  shall return a CHECK CONDITION status, the sense key shall be set topK  ILLEGAL REQUEST and the additional sense code set to ILLEGAL FIELD IN CDB.e   I  A partial medium indicator (PMI) bit of zero indicates that the returned J  logical block address and the block length in bytes are those of the last%  logical block on the logical unit.  a  iG  A PMI bit of one indicates that the returned logical block address andaI  block length in bytes are those of the logical block address after whichrI  a substantial delay in data transfer will be encountered.  This returned J  logical block address shall be greater than or equal to the logical blockH  address specified by the RelAdr and logical block address fields in the  command descriptor block.    =O     NOTE 108 This function is intended to assist storage management software in3Q     determining whether there is sufficient space on the current track, cylinder, I     etc., to contain a frequently accessed data structure, such as a file=?     directory or file index, without incurring an access delay.    H  The READ CAPACITY data (see table 125) shall be sent during the DATA IN  phase of the command.  -7                          Table 125 - READ CAPACITY datarP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   | (MSB)                                                                 |P  |- - -+---                        Returned logical block address           ---|P  | 3   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 4   | (MSB)                                                                 |P  |- - -+---                        Block length In bytes                    ---|P  | 7   |                                                                 (LSB) |P  +=============================================================================+     d  9.2.8 READ DEFECT DATA command   tF  The READ DEFECT DATA command (see table 126) requests that the target2  transfer the medium defect data to the initiator.:                       Table 126 - READ DEFECT DATA commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (37h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |                  Reserved                  |P  |-----+--------------------------+--------------------------------------------|P  | 2   |          Reserved        | Plist  | Glist  | Defect list format       |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   | (MSB)                                                                 |P  |-----+---                        Allocation length                           |P  | 8   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+      C  If the target is unable to access any medium defect data, it shall-H  terminate the command with CHECK CONDITION status.  The sense key shallH  be set to either MEDIUM ERROR, if a medium error occurred, or NO SENSE,J  if the list does not exist; and the additional sense code shall be set to  DEFECT LIST NOT FOUND.    L     NOTE 109 Some targets may not be able to return medium defect data until@     after a FORMAT UNIT command has been completed successfully.   H  A primary defect list (Plist) bit of one request that the target returnK  the primary list of defects.  A Plist bit of zero requests that the targete(  not return the primary list of defects.  eJ  A grown defect list (Glist) bit of one request that the target return theE  grown defect list.  A Glist bit of zero requests that the target notr  return the grown defect list.  cJ  A Plist bit of one and a Glist bit of one requests that the target returnL  the primary and the grown defect lists.  The  order in which the lists are E  returned is vendor-specific.  Whether the lists are merged or not iss  vendor-specific.    E  A Plist bit of zero and a Glist bit of zero requests that the targetd$  return only the defect list header.   F  The defect list format field is used by the initiator to indicate theH  preferred format for the defect list.  This field is intended for thoseE  targets capable of returning more than one format, as defined in theeH  FORMAT UNIT command (see 9.2.1.2, defect list format).  A target unableK  to return the requested format shall return the defect list in its defaulthK  format (see the defect list format field in the defect list header below).b  cH  If the requested defect list format and the returned defect list formatE  are not the same, the target shall transfer the defect data and then H  terminate the command with CHECK CONDITION status.  The sense key shallH  be set to RECOVERED ERROR and the additional sense code shall be set to  DEFECT LIST NOT FOUND.   IF  The READ DEFECT DATA defect list (see table 127) contains a four-byte5  header, followed by zero or more defect descriptors.   w<                     Table 127 - READ DEFECT DATA defect listP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 1   |          Reserved        | Plist  | Glist  | Defect list format       |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                        Defect list length                          |P  | 3   |                                                                 (LSB) |P  |=====+=======================================================================|P  |     |                           Defect descriptor(s) (if any)               |P  |=====+=======================================================================|P  | 0   |                           Defect descriptor 0                         |P  |-----+---                  (See specific table for length.)               ---|P  | n   |                                                                       |P  |-----+-----------------------------------------------------------------------|P  |     |                                  .                                    |P  |     |                                  .                                    |P  |-----+-----------------------------------------------------------------------|P  | 0   |                           Defect descriptor x                         |P  |-----+---                  (See specific table for length.)               ---|P  | n   |                                                                       |P  +=============================================================================+  -  -I  A Plist bit of one indicates that the data returned contains the primary H  defect list.  A Plist bit of zero indicates that the data returned does%  not contain the primary defect list.    G  A Glist bit of one indicates that the data returned contains the grown-H  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 defectI  descriptors returned by the target.  This field is defined in the FORMAT   UNIT command (see 9.2.1.2).   H     NOTE 110 The use of the block format is not recommended. There is noJ     universal model that sensibly defines the meaning of the logical blockN     address of a defect.  In the usual case, a defect that has been reassigned*     no longer has a logical block address.  |F  Defect descriptors returned in the block format are vendor-specific. I  Defect descriptors returned in the physical sector format may or may not-B  include defects in areas not accessible to the initiator.  DefectJ  descriptors returned in bytes-from-index format shall comprise a completeJ  list of defects.  A complete list of defects may include defects in areas?  not within the capacity returned in the READ CAPACITY command.=  =I  The defect list length field specifies the length in bytes of the defectaK  descriptors that follow.  The defect list length is equal to four or eightTG  times the number of defect descriptors, depending on the format of theP$  returned descriptors (see 9.2.1.1).  eG  If the allocation length is insufficient to transfer all of the defecteI  descriptors, the defect list length shall not be adjusted to reflect thetF  truncation.  The target shall not create CHECK CONDITION status.  TheF  initiator is responsible for comparing the defect list length and theB  allocation length to ensure that a partial list was not received.  nQ     NOTE 111 The initiator may determine the length of the defect list by sendingaQ     the READ DEFECT DATA command with an allocation length of   four.  The targetbM     will return the defect list header that contains the length of the defectb	     list.s  aG  The defect descriptors may or may not be sent in ascending order.  ThehK  initiator may determine the exact number of defects by dividing the defect I  list length by the length of a single defect descriptor for the returnedo  format.     9.2.9 READ LONG command  sH  The READ LONG command (see table 128) requests that the target transferH  data to the initiator.  The data passed during the READ LONG command isD  vendor-specific, but shall include the data bytes and the ECC bytesG  recorded on the medium.  The most recent data written in the addressedn!  logical block shall be returned.b  16                          Table 128 - READ LONG commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (3Eh)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   |  Logical unit number      |        Reserved         | CORRCT | RelAdr |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                                                                       |P  |-----+---                        Logical block address                    ---|P  | 4   |                                                                       |P  |-----+---                                                                 ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   | (MSB)                                                                 |P  |-----+---                        Byte transfer length                        |P  | 8   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+  -  -L     NOTE 112 Any other bytes that can be corrected by ECC should be includedO     (e.g. data synchronization mark within the area covered by ECC).  It is not-Q     important for the ECC bytes to be at the end of the data bytes; however, they 9     should be in the same order as they are on the media.-  -K  A corrected (CORRCT) bit of zero causes a logical block to be read without H  any correction made by the target.  A CORRCT bit of one causes the dataB  to be corrected by ECC before being transferred to the initiator.   K  See 9.2.2 for a definition of the RelAdr bit and the logical block address+  field.-  -J  The byte transfer length field should specify exactly the number of bytesF  of data that are available for transfer.  If a non-zero byte transferJ  length does not exactly match the available data length, the target shallJ  terminate the command with CHECK CONDITION status, the sense key shall beI  set to ILLEGAL REQUEST and an additional sense code set to INVALID FIELD-H  IN CDB.  The valid and ILI bits shall be set to one and the informationG  field shall be set to the difference (residue) of the requested length=I  minus the actual length in bytes.  Negative values shall be indicated bym  two's complement notation.  t  i@  A byte transfer length of zero indicates that no bytes shall be4  transferred and shall not be considered an error.    r  9.2.10 REASSIGN BLOCKS commande  oC  The REASSIGN BLOCKS command (see table 129) requests the target toNH  reassign the defective logical blocks to another area on the medium setK  aside for this purpose.  The target should also record the location of thesD  defective logical blocks to the grown defect list if such a list isH  supported.  More than one physical or logical block may be relocated byK  each defect descriptor sent by the initiator.  This command does not alterfH  the contents or location of the Plist (see 9.2.1, FORMAT UNIT command).   9                       Table 129 - REASSIGN BLOCKS commandrP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (07h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |                  Reserved                  |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+      F  The initiator transfers a defect list that contains the logical blockK  addresses to be reassigned.  The target shall reassign the physical medium H  used for each logical block address in the list.  The data contained inH  the logical blocks specified in the defect list may be altered, but theC  data in all other logical blocks on the medium shall be preserved.=  =K     NOTE 113 The effect of specifying a logical block to be reassigned that Q     previously has been reassigned is to reassign the block again.  Over the life-Q     of the medium, a logical block can be assigned to multiple physical addresses 7     until no more spare locations remain on the medium.-  -E  The REASSIGN BLOCKS defect list (see table 130) contains a four-byte G  header followed by one or more defect descriptors.  The length of eachc!  defect descriptor is four bytes.   |;                     Table 130 - REASSIGN BLOCKS defect list P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 1   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                        Defect list length                       ---|P  | 3   |                                                                 (LSB) |P  |=====+=======================================================================|P  |     |                        Defect descriptor(s)                           |P  |=====+=======================================================================|P  | 0   | (MSB)                                                                 |P  |- - -+---                     Defect logical block address                ---|P  | 3   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  |     |                                  .                                    |P  |     |                                  .                                    |P  |-----+-----------------------------------------------------------------------|P  | 0   | (MSB)                                                                 |P  |- - -+---                     Defect logical block address                ---|P  | 3   |                                                                 (LSB) |P  +=============================================================================+  lH  The defect list length field specifies the total length in bytes of theI  defect descriptors that follow.  The defect list length is equal to foureG  times the number of defect descriptors and does not include the defectm  list header length.  eI  The defect descriptor specifies a four-byte defect logical block addresseH  that contains the defect.  The defect descriptors shall be in ascending  order.c  iE  If the logical unit has insufficient capacity to reassign all of theoF  logical blocks specified in the defect descriptors, the command shallE  terminate with CHECK CONDITION status, the sense key shall be set torD  HARDWARE ERROR and the additional sense code set to NO DEFECT SPARE  LOCATION AVAILABLE.     I  If the logical unit is unable to successfully complete a REASSIGN BLOCKStJ  command, the command shall terminate with CHECK CONDITION status with theG  appropriate sense information.  The logical block address of the firsthK  defect descriptor not reassigned shall be returned in the command-specific E  information field of the sense data.  If information about the firstiI  defect descriptor not reassigned is not available, or if all the defectso<  have been reassigned, this field shall be set to FFFFFFFFh.  aI  If the REASSIGN BLOCKS command failed due to an unexpected unrecoverablerI  read error that would cause the loss of data in a block not specified ineF  the defect list, the logical block address of the unrecoverable blockK  shall be returned in the information field of the sense data and the valid9  bit shall be set to one.e  AN     NOTE 114 If the REASSIGN BLOCKS command returns CHECK CONDITION status andN     the sense data command-specific information field contains a valid logicalN     block address, the initiator should remove all defect descriptors from theM     defect list prior to the one returned in the command-specific information I     field. If the sense key is MEDIUM ERROR and the valid bit is one (the=L     information field contains the valid block address) the initiator shouldL     insert that new defective logical block address into the defect list andQ     reissue the REASSIGN BLOCKS command with the new defect list.  Otherwise, the=N     initiator should perform any corrective action indicated by the sense dataJ     and then reissue the REASSIGN BLOCKS command with the new defect list.  -  9.2.11 RELEASE command-  -D  The RELEASE command (see table 131) is used to release a previouslyH  reserved logical unit, or, if the extent release option is implemented,>  to release previously reserved extents within a logical unit.  |5                           Table 131 - RELEASE command P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (17h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      | 3rdPty | Third party device ID    | Extent |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reservation identification                  |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+      A  The RESERVE and RELEASE commands provide the basic mechanism foraH  contention resolution in multiple-initiator systems.  A reservation mayH  only be released by the initiator that made it.  It is not an error forG  an initiator to attempt to release a reservation that is not currentlysH  valid, or is held by another initiator.  In this case, the target shall;  return GOOD status without altering any other reservation.   oP     NOTE 115 The reservation queuing option in X3.131-1986 has been removed from     SCSI-2.h  o  9.2.11.1 Logical unit release   H  Implementation of logical unit release is mandatory.  If the extent bitI  is zero, this command shall cause the target to terminate all non-third-lD  party logical unit and extent reservations that are active from theJ  initiator to the specified logical unit.  The reservation ID field in the3  command descriptor block is ignored by the target.o  s  9.2.11.2 Extent release  .H  Implementation of extent release is optional.  If the extent bit is oneK  and the extent release option is not implemented, then the RELEASE commandaH  shall be terminated with CHECK CONDITION status and the sense key shallK  be set to ILLEGAL REQUEST.  This option shall be implemented if the extenty2  reservation option (see 9.2.12.2) is implemented.  aG  If the extent bit is one and the extent release option is implemented,SG  this command shall cause any reservation from the requesting initiator D  with a matching reservation identification to be terminated.  OtherC  reservations from the requesting initiator shall remain in effect.l  c  9.2.11.3 Third-party releasei  iH  Implementation of third-party release is mandatory. Third-party releaseJ  allows an initiator to release a logical unit or extents within a logicalF  unit that were previously reserved using third-party reservation (seeI  9.2.12.3).  Third-party release shall be implemented and is intended for =  use in multiple-initiator systems that use the COPY command.=  =K  If the third-party (3rdPty) bit is zero, then a third-party release is not G  requested.  If the 3rdPty bit is one then the target shall release the H  specified logical unit or extents, but only if the reservation was madeH  using a third-party reservation by the initiator that is requesting theH  release for the same SCSI device as specified in the third-party device
  ID field.  -I  If the 3rdPty bit is one the target shall not modify the mode parameters E  for commands received from the third-party device even if the target-F  implements the transfer of mode parameters with a third-party RESERVE	  command.    N     NOTE 116 If a target implements independent storage of mode parameters forI     each initiator, a third-party RESERVE command copies the current mode M     parameters for the initiator that sent the RESERVE command to the current-I     mode parameters for the initiator specified as the third-party device L     (usually a copy master device).  A unit attention condition notifies theI     third-party of the changed mode parameters due to the reservation.  A|K     successful third-party RELEASE command  does not return the third-party|O     devices' current mode parameters back to their previous values.  The third-+K     party device can issue MODE SENSE and MODE SELECT commands to query ando"     modify the mode parameters.     a  9.2.12 RESERVE commandh  cJ  The RESERVE command (see table 132) is used to reserve a logical unit or,J  if the extent reservation option is implemented, extents within a logical  unit.  t5                           Table 132 - RESERVE commandeP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (16h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      | 3rdPty | Third party device ID    | Extent |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reservation identification                  |P  |-----+-----------------------------------------------------------------------|P  | 3   | (MSB)                                                                 |P  |-----+---                        Extent list length                       ---|P  | 4   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+  +   A  The RESERVE and RELEASE commands provide the basic mechanism for|F  contention resolution in multiple-initiator systems.  The third-partyG  reservation allows logical units or extents to be reserved for another=  specified SCSI device.    P     NOTE 117 The reservation queuing option in X3.131-1986 has been removed from     SCSI-2.=  ="  9.2.12.1 Logical unit reservation  =H  Implementation of logical unit reservation is mandatory.  If the extentH  bit is zero, this command shall request that the entire logical unit beI  reserved for the exclusive use of the initiator until the reservation is I  superseded by another valid RESERVE command from the initiator that made-E  the reservation or until released by a RELEASE command from the same H  initiator that made the reservation, by a BUS DEVICE RESET message fromE  any initiator, by a hard RESET condition, or by a power on cycle.  A-I  logical unit reservation shall not be granted if the logical unit or any I  extent is reserved by another initiator.  It shall be permissible for an G  initiator to reserve a logical unit that is currently reserved by that J  initiator.  If the extent bit is zero, the reservation identification and)  the extent list length shall be ignored.=  =K  If the logical unit, or any extent within the logical unit is reserved foriI  another initiator, the target shall return RESERVATION CONFLICT status. l  .  hE  If, after honouring the reservation, any other initiator attempts tocH  perform any command on the reserved logical unit other than an INQUIRY,J  REQUEST SENSE, PREVENT ALLOW MEDIUM REMOVAL (with a prevent bit of zero),D  or a RELEASE command the command shall be rejected with RESERVATION  CONFLICT status.   i  9.2.12.2 Extent reservation  yC  Implementation of extent reservation is optional.  The reservationcH  identification field provides a means for an initiator to identify eachD  extent reservation.  This allows an initiator in a multiple taskingI  environment, to have multiple reservations outstanding.  The reservationiK  identification is used in the RELEASE command to specify which reservationhG  is to be released.  It is also used in superseding RESERVE commands tof/  specify which reservation is to be superseded.h  dI  If the extent reservation option is implemented, then the extent release G  option (see 9.2.11.2) shall also be implemented.  These options permitdE  multiple extents within the logical unit to be reserved, each with ao  separate reservation type.   l?  If the extent bit is one, and the extent reservation option is F  implemented, then the target shall process the reservation request as	  follows:fL     a)     The extent list shall be checked for the number of extents in theN            reservation request.  If the extent list length is zero, no currentO            reservations shall be changed, no new reservations shall be created,EN            and this condition shall not be treated as an error.  If the extentM            list contains more extents than are supported on the logical unit,eN            the command shall be terminated with CHECK CONDITION status and theI            sense key shall be set to ILLEGAL REQUEST.  If the extent list L            contains more extents than are currently available on the logicalM            unit, then the target shall return a RESERVATION CONFLICT status. eJ     b)     The extent list shall be checked for valid extent logical blockO            addresses.  If any logical block address is invalid for this logicaluL            unit, the command shall be terminated with CHECK CONDITION statusN            and the sense key shall be set to ILLEGAL REQUEST.  The extent listF            shall be checked for invalid extent overlaps (as defined byM            reservation type) with other extent descriptors in the extent listnM            and if invalid overlaps are found, the command shall be terminated H            with CHECK CONDITION status and the sense key shall be set to            ILLEGAL REQUEST.=J     c)     If the requested reservation does not conflict with an existingE            reservation, the extents specified shall be reserved until N            superseded by another valid RESERVE command from the initiator thatO            made the reservation or until released by a RELEASE command from theOL            same initiator, by a BUS DEVICE RESET message from any initiator,N            or by a hard RESET condition.  If either of the last two conditionsO            occur, the next command from each initiator shall be terminated with-H            CHECK CONDITION status and the sense key shall be set to UNIT            ATTENTION.nM     d)     If the reservation request conflicts with an existing reservation,-F            then the target shall return a RESERVATION CONFLICT status.  sC  If the extent bit is one, and the extent reservation option is not-C  implemented, then the RESERVE command shall be rejected with CHECK D  CONDITION status and the sense key shall be set to ILLEGAL REQUEST.  -G  The size of the extent list shall be defined by the extent list length|K  field.  The extent list shall consist of zero or more descriptors as shown I  in table 133.  Each extent descriptor defines an extent beginning at the=H  specified logical block address for the specified number of blocks.  IfF  the number of blocks is zero, the extent shall begin at the specifiedJ  logical block address and continue through the last logical block address  on the logical unit.a   >                  Table 133 - Data format of extent descriptorsP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+============================================+========+=================|P  | 0   |               Reserved                     | RelAdr | Reservation type|P  |-----+-----------------------------------------------------------------------|P  | 1   | (MSB)                                                                 |P  |- - -+---                        Number of blocks                         ---|P  | 3   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 4   | (MSB)                                                                 |P  |- - -+---                        Logical block address                    ---|P  | 7   |                                                                 (LSB) |P  +=============================================================================+     tJ  The reservation type field shall define the type of reservation in effectD  for the extent.  The types of reservation are defined in table 134.  c6                          Table 134 - Reservation types-  +====================-=====================+r-  | Reservation type   |  Description        |a-  |--------------------+---------------------|w-  |        00b         |  Read shared        |v-  |        01b         |  Write exclusive    |a-  |        10b         |  Read exclusive     | -  |        11b         |  Exclusive access   |m-  +==========================================+   oM  a)     Read exclusive.  While this reservation is active, no other initiatornI         shall be permitted read operations to the indicated extent.  ThisyL         reservation shall not inhibit write operations from any initiator orM         conflict with a write exclusive reservation; however, read exclusive, H         exclusive access, and read shared reservations that overlap this4         extent shall conflict with this reservation.  vN  b)     Write exclusive.  While this reservation is active, no other initiatorJ         shall be permitted write operations to the indicated extent.  ThisK         reservation shall not inhibit read operations from any initiator oriL         conflict with a read exclusive reservation from any initiator.  ThisN         reservation shall conflict with write exclusive, exclusive access, and:         read shared reservations that overlap this extent.   E  c)     Exclusive access.  While this reservation is active, no othereM         initiator shall be permitted any access to the indicated extent.  All K         reservation types that overlap this extent shall conflict with this          reservation.  aK  d)     Read shared.  While this reservation is active, no write operationssJ         shall be permitted by any initiator to the indicated extent.  ThisK         reservation shall not inhibit read operations from any initiator orlG         conflict with a read shared reservation.  Read exclusive, writeoK         exclusive, and exclusive access reservations that overlap with this 4         extent shall conflict with this reservation.  =E  If the relative address bit is one, the logical block address in the H  extent descriptor shall be treated as a two's complement displacement. C  This displacement shall be added to the logical block address last H  accessed on the logical unit to form the logical block address for thisK  extent.  This feature is only available when linking commands and requires I  that a previous command in the linked group has accessed a logical block-J  on the logical unit; if not, the RESERVE command shall be terminated withJ  CHECK CONDITION status and the sense key shall be set to ILLEGAL REQUEST.  -D  If an initiator attempts a command to a logical block that has beenG  reserved and that access is prohibited by the reservation, the command-B  shall not be performed and the command shall be terminated with aK  RESERVATION CONFLICT status.  If a reservation conflict precludes any part+G  of the command, none of the command shall be performed.  COPY commands H  shall be terminated with CHECK CONDITION status and the sense key shallJ  be set to DATA PROTECT if any part of the copy operation is prohibited byK  an active reservation.  If any extent in a logical unit is reserved in any F  way, by any initiator, a FORMAT UNIT command shall be rejected with a  RESERVATION CONFLICT status.    "  9.2.12.3 Third-party reservation   dI  Implementation of third-party reservation is mandatory.  The third-partysE  reservation for the RESERVE command allows an initiator to reserve a H  logical unit or extents within a logical unit for another SCSI device. I  This is intended for use in multiple-initiator systems that use the COPY=0  command.  Third-party reservation is required.   eH  If the third-party (3rdPty) bit is zero, then a third-party reservationJ  is not requested.  If the 3rdPty bit is one then the target shall reserveK  the specified logical unit or extents for the SCSI device specified in the H  third-party device ID field.  The target shall preserve the reservationK  until it is superseded by another valid RESERVE command from the initiator I  that made the reservation or until it is released by the same initiator,yB  by a BUS DEVICE reset message from any initiator, or a hard resetK  condition.  The target shall ignore any attempt to release the reservationr  made by any other initiator.h   A  If independent sets of parameters are implemented, a third partysH  reservation shall cause the target to transfer the set of parameters inK  effect for the initiator of the RESERVE command to the parameters used for=H  commands from the third party device.  Any subsequent command issued byG  the third-party device is executed according to the mode parameters ina8  effect for the initiator that sent the RESERVE command.  eQ     NOTE 118 This transfer of the mode parameters is applicable to target deviceshN     which store mode information independently for different initiators.  ThisP     mechanism allows an initiator to set the mode parameters of a target for theM     use of a copy master (i.e. the third-party device).  The third-party copytJ     master may subsequently issue a MODE SELECT command to modify the mode     parameters.   t"  9.2.12.4 Superseding reservations  tG  Implementation of superseding reservations is mandatory.  An initiatorvB  that holds a current reservation (unit or extent) may modify thatG  reservation by issuing another RESERVE command (unit or extent) to thebF  same logical unit.  The superseding RESERVE command shall release theE  previous reservation state (unit or extent) when the new reservationiE  request is granted.  If the superseding reservation is for an extent.K  reservation and the current reservation is also an extent reservation, then@  current extent reservation identification value is used for theH  superseding reservation.  The current reservation shall not be modifiedB  if the superseding reservation request cannot be granted.  If theF  superseding reservation cannot be granted because of conflicts with aI  previous reservation (other than the reservation being superseded), thent7  the target shall return RESERVATION CONFLICT status.     lO     NOTE 119 Superseding reservations allow the SCSI device ID to be changed onoO     a reservation using the third-party reservation option.  This capability is K     necessary for certain situations when using COMPARE, COPY, and COPY ANDl     VERIFY commands.     9.2.13 REZERO UNIT command    I  The REZERO UNIT command (see table 135) requests that the target set the J  logical unit to a specific state.  See vendor specifications for details.   7                         Table 135 - REZERO UNIT commandTP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (01h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |                  Reserved                  |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+        9.2.14 SEARCH DATA commands  fK  The SEARCH DATA commands (see table 136) search one or more logical blocks F  for equality or inequality to a data pattern.  The concept of recordsJ  within a logical block is used to allow multiple records within a logical  block to be searched.   8                         Table 136 - SEARCH DATA commandsP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (31h 30h 32h)                |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      | Invert |     Reserved    | SpnDat | RelAdr |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                                                                       |P  |-----+---                        Logical block address                    ---|P  | 4   |                                                                       |P  |-----+---                                                                 ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   | (MSB)                                                                 |P  |-----+---                        Number of blocks to search               ---|P  | 8   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+  R  rK  The invert bit determines whether the search condition is to be inverted. -I  See 9.2.14.1 through 9.2.14.3 for a description of the search conditions )  for the individual SEARCH DATA commands.    H  A spanned data (SpnDat) bit of zero indicates that each record shall beI  wholly contained within a single block.  Any space at the end of a blockiE  that is smaller than the record length is ignored by the SEARCH DATAlB  commands.   A SpnDat bit of one indicates that records span blockI  boundaries (i.e.  record may start in one block and end in the next or a   subsequent block.  rE  The number of blocks to search field specifies the maximum number of J  contiguous logical blocks to be searched.  A value of zero indicates thatA  no logical blocks shall be searched. This condition shall not belF  considered an error.  Any other value indicates the maximum number of'  logical blocks that shall be searched.t  .I  A link bit (see 7.2.7) of zero indicates a non-linked command and if theiJ  search is satisfied, the command shall be terminated with a CONDITION METE  status.  A REQUEST SENSE command can then be issued to determine thecH  logical block address and record offset of the matching record.  If theB  search is not satisfied and no error occurs, the command shall be  terminated with GOOD status.   lJ  A link bit (see 7.2.7) of one indicates a command is linked to the SEARCHH  DATA command and if the search is satisfied, INTERMEDIATE-CONDITION METH  status is returned and the next command is executed.  If the RelAdr bitJ  in the next command is one, the logical block address of the next commandF  is used as a displacement from the logical block address at which theH  search was satisfied.  If a linked search is not satisfied, the commandH  is terminated with CHECK CONDITION status.  A REQUEST SENSE command may  then be issued.  iI  A REQUEST SENSE command following a satisfied SEARCH DATA command shall:iN     a)     return a sense key of EQUAL if the search was satisfied by an exactL            match.  If the search was satisfied by an inequality then a sense-            key of NO SENSE shall be returned.c+     b)     return the valid bit set to one. O     c)     return the logical block address of the logical block containing them:            first matching record in the information field.J     d)     return the record offset of the matching record in the command-&            specific information field.  CD  A REQUEST SENSE command following a SEARCH DATA command that is not  satisfied shall:aK     a)     return a sense key of NO SENSE, if no errors occurred during the             command execution.n,     b)     return the valid bit set to zero.  oH  The SEARCH DATA parameter list (see table 137) contains a fourteen-byte>  header, followed by one or more search argument descriptors.   c;                      Table 137 - SEARCH DATA parameter listtP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   | (MSB)                                                                 |P  |- - -+---                        Logical record length                    ---|P  | 3   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 4   | (MSB)                                                                 |P  |- - -+---                        First record offset                      ---|P  | 7   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 8   | (MSB)                                                                 |P  |- - -+---                        Number of records                        ---|P  | 11  |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 12  | (MSB)                                                                 |P  |-----+---                        Search argument length                   ---|P  | 13  |                                                                 (LSB) |P  |=====+=======================================================================|P  |     |                        Search argument descriptor(s)                  |P  |=====+=======================================================================|P  | 0   | (MSB)                                                                 |P  |- - -+---                        Displacement                             ---|P  | 3   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 4   | (MSB)                                                                 |P  |-----+---                        Pattern length                           ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   |                                                                       |P  |-----+---                        Pattern                                  ---|P  | n   |                                                                       |P  +=============================================================================+  i  vF  The logical record length field specifies the record length in bytes.  aJ  The first record offset field specifies the number of bytes that shall beK  ignored in the first logical block before the search begins.  If the valueiH  of the first record offset field shall is larger than the logical blockE  length the target shall terminate the command with a CHECK CONDITION J  status, set the sense key to ILLEGAL REQUEST and set the additional senseK  code to INVALID FIELD IN PARAMETERS LIST.  Subsequent logical blocks shalliF  be searched beginning with the first byte in the logical block.  This5  permits one or more records to be skipped initially.U   I  The number of records field specifies the maximum number of records thatrG  shall be searched by this command.  An search shall terminate when thenK  search pattern is found or when the number of records is exhausted or when -  the number of blocks to search is exhausted.=  =J  The search argument length field specifies the length in bytes of all the+  search argument descriptors that follow.      Q     NOTE 120 Since the pattern length can vary, there is no fixed multiple of the=G     search argument descriptor to determine the search argument length.|   I  The search argument descriptors specify one or more search conditions to-E  execute within a single record in order to satisfy the search.  Each-I  search argument descriptor is made up of a displacement field, a pattern #  length field, and a pattern field.-  -H  The displacement field specifies the displacement in bytes of the firstF  byte of the data to be compared from the start of the logical record.  -K  The pattern length field specifies the length in bytes of the pattern that 	  follows.    G  The pattern field specifies the data to compare to the logical record.-  -#  9.2.14.1 SEARCH DATA EQUAL command-  -H  The SEARCH DATA EQUAL command (see table 136, operation code 31h) shallJ  be satisfied by the first logical record searched that contains data thatJ  satisfies all of the search argument descriptor(s).  If the invert bit inH  the command descriptor block is zero, the search argument descriptor(s)I  shall be satisfied by data in the logical record being equal to the datan?  in the pattern.  If the invert bit is one, the search argumentoI  descriptor(s) shall be satisfied by data in the logical record being notc1  equal to the data in the pattern.  (See 9.2.14.)a  w"  9.2.14.2 SEARCH DATA HIGH command  oJ  The SEARCH DATA HIGH command (see table 136, operation code 30h) shall beG  satisfied by the first logical record searched that contains data that=J  satisfies all of the search argument descriptor(s).  If the invert bit inH  the command descriptor block is zero, the search argument descriptor(s)H  shall be satisfied by data in the logical record being greater than theD  data in the pattern.  If the invert bit is one, the search argumentJ  descriptor(s) shall be satisfied by data in the logical record being less9  than or equal to the data in the pattern.  (See 9.2.14.)   L!  9.2.14.3 SEARCH DATA LOW command   RI  The SEARCH DATA LOW command (see table 136, operation code 32h) shall be-G  satisfied by the first logical record searched that contains data that J  satisfies all of the search argument descriptor(s).  If the invert bit inH  the command descriptor block is zero, the search argument descriptor(s)J  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 argument E  descriptor(s) shall be satisfied by data in the logical record being A  greater than or equal to the data in the pattern.  (See 9.2.14.)    %  9.2.15 SEEK(6) and SEEK(10) commands    J  The SEEK(6) (see table 138) and SEEK(10) (see table 139) commands requestC  that the logical unit seek to the specified logical block address.    5                           Table 138 - SEEK(6) command P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (0Bh)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      | (MSB)                                      |P  |-----+-------------------------------                                     ---|P  | 2   |                           Logical block address                       |P  |-----+---                                                                 ---|P  | 3   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+  f  r6                           Table 139 - SEEK(10) commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (2Bh)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |                  Reserved                  |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                                                                       |P  |-----+---                        Logical block address                    ---|P  | 4   |                                                                       |P  |-----+---                                                                 ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 8   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+  b  1  9.2.16 SET LIMITS command  hF  The SET LIMITS command (see table 140) defines the range within whichI  subsequent linked commands may operate.  A second SET LIMITS command may=G  not be linked to a chain of commands in which a SET LIMITS command has7  already been issued.    7                          Table 140 - SET LIMITS command P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (33h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |         Reserved         | RdInh  | WrInh  |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                                                                       |P  |-----+---                        Logical block address                    ---|P  | 4   |                                                                       |P  |-----+---                                                                 ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   | (MSB)                                                                 |P  |-----+---                        Number of blocks                         ---|P  | 8   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+      J  The read inhibit (RdInh) bit of one indicates that read operations within   the range shall be inhibited.     J  A write inhibit (WrInh) bit of one indicates that write operations within  the range shall be inhibited.  -G  The logical block address field specifies the starting address for the-  range.    I  The number of blocks field specifies the number of logical blocks within-F  the range.  A number of blocks of zero indicates that the range shall6  extend to the last logical block on the logical unit.   H  Any attempt to access outside of the restricted range or any attempt toH  perform an inhibited operation within the restricted range shall not beH  performed.  The command shall be terminated with CHECK CONDITION statusE  and the sense key shall be set to DATA PROTECT.  A second SET LIMITSoF  command within a linked list of commands shall be rejected with CHECKA  CONDITION status and the sense key shall be set to DATA PROTECT.   g  9.2.17 START STOP UNIT commandt   E  The START STOP UNIT command (see table 141) requests that the target @  enable or disable the logical unit for media access operations.  s9                       Table 141 - START STOP UNIT commandhP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (1Bh)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |                  Reserved         | Immed  |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved                  |  LoEj  |  Start |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+  A  UH  An immediate (Immed) bit of one indicates that status shall be returnedJ  as soon as the command descriptor block has been validated.  An Immed bitG  of zero indicates that status shall be returned after the operation isr  completed.   rK  A load eject (LoEj) bit of zero requests that no action be taken regardingcE  loading or ejecting the medium.  A LoEj bit of one requests that the F  medium shall be unloaded if the start bit is zero.  A LoEj bit of oneB  requests that the medium is to be loaded if the start bit is one.  SG  A start bit of one requests the logical unit be made ready for use.  AAJ  start bit of zero requests that the logical unit be stopped (media cannot  be accessed by the initiator).h  cI  Targets that contain cache memory shall implicitly perform a SYNCHRONIZEfE  CACHE command for the entire medium prior to executing the STOP UNITr	  command.r  o!  9.2.18 SYNCHRONIZE CACHE commandn  eJ  The SYNCHRONIZE CACHE command (see table 142) ensures that logical blocksH  in the cache memory, within the specified range, have their most recentI  data value recorded on the physical medium.  If a more recent data valuerJ  for a logical block within the specified range exists in the cache memoryJ  than on the physical medium, then the logical block from the cache memoryA  shall be written to the physical medium.  Logical blocks are notsI  necessarily removed from the cache memory as a result of the synchronizec  cache operation.l   :                      Table 142 - SYNCHRONIZE CACHE commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (35h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number       |         Reserved        | Immed  | RelAdr |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                                                                       |P  |-----+---                        Logical block address                    ---|P  | 4   |                                                                       |P  |-----+---                                                                 ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   | (MSB)                                                                 |P  |-----+---                        Number of blocks                         ---|P  | 8   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+  =  +G  An immediate (Immed) bit of one indicates that the target shall return G  status as soon as the command descriptor block has been validated.  An H  Immed bit of zero indicates that the status shall not be returned untilI  the operation has been completed. If the Immed bit is one and the target J  does not support it then the command shall terminate with CHECK CONDITIONJ  status.  The sense key shall be set to ILLEGAL REQUEST and the additional1  sense code shall be set to INVALID FIELD IN CDB.+  -K  See 9.2.2 for a definition of the RelAdr bit and the logical block address|  field.    D  The number of blocks field specifies the total number of contiguousG  logical blocks within the range.  A number of blocks of zero indicates|J  that all remaining logical blocks on the logical unit shall be within the	  range.  +   J  A logical block within the specified range that is not in cache memory is  not considered an error.      9.2.19 VERIFY command   G  The VERIFY command (see table 143) requests that the target verify the   data written on the medium.   5                            Table 143 - VERIFY command P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (2Fh)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   |   Logical unit number    |   DPO  |Reserved|Reserved| BytChk | RelAdr |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                                                                       |P  |-----+---                        Logical block address                    ---|P  | 4   |                                                                       |P  |-----+---                                                                 ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   | (MSB)                                                                 |P  |-----+---                        Verification length                         |P  | 8   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+      I  If the MODE SELECT command is implemented, and the verify error recoverykG  parameters page is also implemented, then the current settings in that D  page specifies the verification error criteria. If the verify errorC  recovery parameters page is not implemented, then the verification   criteria is vendor-specific.    E  A byte check (BytChk) bit of zero causes a medium verification to be-J  performed with no data comparison.  A BytChk bit of one causes a byte-by-I  byte compare of data written on the medium and the data transferred from-J  the initiator.  If the compare is unsuccessful for any reason, the targetJ  shall return CHECK CONDITION status with the sense key set to MISCOMPARE.   K  See 9.2.2 for a definition of the RelAdr bit and the logical block address   field.    I  The verification length field specifies the number of contiguous logical-B  blocks of data that shall be verified.  A transfer length of zeroJ  indicates that no logical blocks shall be verified.  This condition shallH  not be considered as an error.  Any other value indicates the number of'  logical blocks that shall be verified.f  e<  See 9.2.6 for a description of the cache control bit (DPO).  i  9.2.20 WRITE(6) command  (H  The WRITE(6) command (see table 144) requests that the target write the3  data transferred by the initiator to the medium.  s  i6                           Table 144 - WRITE(6) commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (0Ah)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      | (MSB)                                      |P  |-----+------------------------------                                      ---|P  | 2   |                           Logical block address                       |P  |-----+---                                                                 ---|P  | 3   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Transfer length                             |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+  -  -G  The cache control bits (see 9.2.6) are not provided for this command.  K  Targets with cache memory may have values for the cache control bits which-H  may affect the WRITE(6) command, however no default value is defined byC  this International Standard.  If explicit control is required, the|"  WRITE(10) command should be used.  -I  The logical block address field specifies the logical block at which the   write operation shall begin.    E  The transfer length field specifies the number of contiguous logical-I  blocks of data to transferred.  A transfer length of zero indicates that H  256 logical blocks shall be transferred.  Any other value indicates the4  number of logical blocks that shall be transferred.     9.2.21 WRITE(10) command    I  The WRITE(10) command (see table 145) requests that the target write the=1  data transferred by the initiator to the medium.e  t6                          Table 145 - WRITE(10) commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (2Ah)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |   DPO  |   FUA  |Reserved|Reserved| RelAdr |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                                                                       |P  |-----+---                        Logical block address                    ---|P  | 4   |                                                                       |P  |-----+---                                                                 ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   | (MSB)                                                                 |P  |-----+---                        Transfer length                             |P  | 8   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+  c  uH  See READ(10) command (9.2.6) for a definition of the cache control bits  (DPO and FUA).-  -K  See 9.2.2 for a definition of the RelAdr bit and the logical block address   field.    E  The transfer length field specifies the number of contiguous logical E  blocks of data that shall be transferred.  A transfer length of zero G  indicates that no logical blocks shall be transferred.  This condition J  shall not be considered an error and no data shall be written.  Any otherH  value indicates the number of logical blocks that shall be transferred.  -   9.2.22 WRITE AND VERIFY command   F  The WRITE AND VERIFY command (see table 146) requests that the targetE  write the data transferred from the initiator to the medium and then-H  verify that the data is correctly written. The data is only transferred'  once from the initiator to the target.    :                       Table 146 - WRITE AND VERIFY commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (2Eh)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   |   Logical unit number    |   DPO  |Reserved|Reserved| BytChk | RelAdr |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                                                                       |P  |-----+---                        Logical block address                    ---|P  | 4   |                                                                       |P  |-----+---                                                                 ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   | (MSB)                                                                 |P  |-----+---                        Transfer length                             |P  | 8   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+  =  =I  If the MODE SELECT command is implemented, and the verify error recoverycJ  page is also implemented (see 9.3.3.8), then the current settings in thatE  page along with the AWRE bit from the read-write error recovery pager@  specify the verification error criteria. If these pages are not@  implemented, then the verification criteria is vendor-specific.  |G  A byte check (BytChk) bit of zero requests a medium verification to be I  performed with no data comparison.  A BytChk bit of one requests a byte- G  by-byte compare of data written on the medium and the data transferred H  from the initiator.  If the compare is unsuccessful for any reason, theE  target shall return CHECK CONDITION status with the sense key set to   MISCOMPARE.   K  See 9.2.2 for a definition of the RelAdr bit and the logical block address   field.    K  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).  -O     NOTE 121 The WRITE AND VERIFY command specifically states that the data are O     not to be transferred twice (i.e. once for the write pass, and once for the-L     verify pass) when performing a byte compare.  If there is a need for twoO     transfers to occur (e.g. to ensure the integrity of the path to the media), J     then the initiator should issue a WRITE command with a LINK bit of oneP     followed by a VERIFY command with a BytCmp bit of one, transferring the same     data on each command.|     9.2.23 WRITE LONG command  nJ  The WRITE LONG command (see table 147) requests that the target write theI  data transferred by the initiator to the medium.  The data passed duringCI  the WRITE LONG command is implementation specific, but shall include thei   data bytes and the ECC bytes.    s7                          Table 147 - WRITE LONG commandcP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (3Fh)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |              Reserved             | RelAdr |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                                                                       |P  |-----+---                        Logical block address                    ---|P  | 4   |                                                                       |P  |-----+---                                                                 ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   | (MSB)                                                                 |P  |-----+---                        Byte transfer length                        |P  | 8   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+  |  -L     NOTE 122 Any other bytes that can be corrected by ECC should be includedO     (e.g. a data synchronization mark within the area covered by ECC). The READ|Q     LONG command is usually issued before issuing a WRITE LONG command. The WRITE4I     LONG data should be the same length and in the same order as the data|&     returned by the READ LONG command.  -K  See 9.2.2 for a definition of the RelAdr bit and the logical block addressn  field.    J  The byte transfer length field should specify the number of bytes of dataG  that the target would return for the READ LONG command.  If a non-zero9G  byte transfer length does not exactly match the data length the targetyH  would return for the READ LONG command, then the target shall terminateK  the command with CHECK CONDITION status and a sense key of ILLEGAL REQUEST H  and an additional sense code of INVALID FIELD IN CDB. The ILI and validG  bits shall be set to one and the information field shall be set to thecH  difference (residue) of the requested length minus the actual length inI  bytes. Negative values shall be indicated by two's complement notation. AK  A transfer length of zero indicates that no bytes shall be transferred ande"  shall not be considered an error.  n  9.2.24 WRITE SAME command  aJ  The WRITE SAME command (see table 148) requests that the target write theI  single block of data transferred by the initiator to the medium multipley  times.i  r7                          Table 148 - WRITE SAME command-P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (41h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |     Reserved    | PBdata | LBdata | RelAdr |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                                                                       |P  |-----+---                        Logical block address                    ---|P  | 4   |                                                                       |P  |-----+---                                                                 ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   | (MSB)                                                                 |P  |-----+---                        Number of blocks                            |P  | 8   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+  =  =K     NOTE 123 This command is useful if large areas of the medium need to behM     written, prepared for certification, or otherwise initialized without the .     initiator having to transfer all the data.  TJ  A logical block data (LBdata) bit of one requests that the target replaceF  the first four bytes of the data to be written to the current logicalK  block with the logical block address of the block currently being written.t   K  A physical block data (PBdata) bit of one requests that the target replacesH  the first eight bytes of the data to be written to the current physicalG  sector with the physical address of the sector currently being writtene0  using the physical sector format (see 9.2.1.1).  rH  If PBdata and LBdata are one the command shall be terminated with CHECKB  CONDITION status.  The sense key shall be set to ILLEGAL REQUEST.  hK  See 9.2.2 for a definition of the RelAdr bit and the logical block address+  field.=  =F  The number of blocks field specifies the number of contiguous logicalJ  blocks to be written.  A number of blocks field of zero requests that all7  the remaining logical blocks on the medium be written.   |   )  9.3 Parameters for direct-access devices=  =  =  9.3.1 Diagnostic parameters  =K  This subclause defines the descriptors and pages for diagnostic parameters "  used with direct-access devices.   -I  The diagnostic page codes for direct-access devices are defined in tablel  149.u  r8                        Table 149 - Diagnostic page codesP  +=============-==================================================-============+P  |  Page code  |  Description                                     | Subclause  |P  |-------------+--------------------------------------------------+------------|P  |     00h     |  Supported diagnostic pages                      |  8.3.1.1   |P  |     40h     |  Translate address page                          |  9.3.1.1   |P  |  01h - 3Fh  |  Reserved (for all device type pages)            |            |P  |  41h - 7Fh  |  Reserved                                        |            |P  |  80h - FFh  |  Vendor-specific pages                           |            |P  +=============================================================================+      2  9.3.1.1 Translate address page - SEND DIAGNOSTIC    G  The translate address page allows the initiator to translate a logical-D  block address, physical sector address or physical bytes from indexI  address into any one of the other formats.  The address to be translated I  is passed to the target with the SEND DIAGNOSTIC command and the results J  are returned to the initiator by the RECEIVE DIAGNOSTIC RESULTS command. G  The format of the translate address page - SEND DIAGNOSTIC is shown in H  table 150.  The translated address is returned in the translate address1  page - RECEIVE DIAGNOSTIC RESULTS (see 9.3.1.2).=  =B               Table 150 - Translate address page - SEND 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 (000Ah)                      ---|P  | 3   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 4   |                   Reserved                 |     Supplied format      |P  |-----+--------------------------------------------+--------------------------|P  | 5   |                   Reserved                 |     Translate format     |P  |-----+-----------------------------------------------------------------------|P  | 6   |                                                                       |P  |- - -+---                        Address to translate                     ---|P  | 13  |                                                                       |P  +=============================================================================+  C  tG  The supplied format field specifies the format of address to translate K  field.  Valid values for this field are defined in the FORMAT UNIT commandIK  (see 9.2.1).  If the target does not support the requested format it shall=H  terminate the SEND DIAGNOSTIC command with CHECK CONDITION status.  TheG  sense key shall be set to ILLEGAL REQUEST and an additional sense code|1  shall be set to INVALID FIELD IN PARAMETER LIST.=  =K  The translate format field specifies which format the initiator would like J  the address to be translated to.  Valid values for this field are definedH  in the FORMAT UNIT command (see 9.2.1).  If the target does not supportI  the requested format it shall terminate the command with CHECK CONDITIONAI  status.  The sense key shall be set to ILLEGAL REQUEST and an additional-<  sense code shall be set to INVALID FIELD IN PARAMETER LIST.   J  The address to translate field contains a single address the initiator isI  requesting the target to translate.  The format of this field depends on F  the value in the supplied format field.  The formats are described inK  9.2.1.1.  If the logical block format is specified the block address shall H  be in the first four bytes of the field with the remaining bytes set to  zero.   5  9.3.1.2 Translate address page - RECEIVE DIAGNOSTIC     G  The translate address page allows the initiator to translate a logical|E  block address, physical sector address, or physical bytes from index-I  address into any one of the other formats.  The address to be translated I  is passed to the target with the SEND DIAGNOSTIC command and the results-J  are returned to the initiator by the RECEIVE DIAGNOSTIC RESULTS command. K  The translated address is returned in the translate address page - RECEIVEn  DIAGNOSTIC (see table 151).  8C             Table 151 - Translate address page - RECEIVE DIAGNOSTIC(Q  +======-========-========-========-========-========-========-========-========+-Q  |   Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | Q  |Byte  |        |        |        |        |        |        |        |        |+Q  |======+=======================================================================|dQ  | 0    |                           Page code (40h)                             ||Q  |------+-----------------------------------------------------------------------|4Q  | 1    |                           Reserved                                    |eQ  |------+-----------------------------------------------------------------------| Q  | 2    | (MSB)                                                                 |dQ  |------+---                        Page length                              ---|NQ  | 3    |                                                                 (LSB) |eQ  |------+-----------------------------------------------------------------------|rQ  | 4    |                   Reserved                 |     Supplied format      | Q  |------+--------------------------------------------+--------------------------|hQ  | 5    | RAREA  | ALTSEC | ALTTRK |     Reserved    |     Translated format    |dQ  |======+=======================================================================|lQ  |      |                          Translated addresses                         |sQ  |======+=======================================================================|9Q  | 6    |                                                                       | Q  |- - --+---                        Translated address 1                     ---|iQ  | 13   |                                                                       |-Q  |------+-----------------------------------------------------------------------| Q  |      |                                 .                                     ||Q  |      |                                 .                                     |=Q  |------+-----------------------------------------------------------------------| Q  | n    |                                                                       |+Q  |- - --+---                        Translated address x (if required)       ---|LQ  | n+7  |                                                                       |-Q  +==============================================================================+)      B  The translate address page contains a four byte page header whichH  specifies the page code and length followed by two bytes which describeG  the translated address followed by zero or more translated address(s).    K  The page length field contains the number of parameter bytes which follow.   -F  The supplied format field contains the value from the SEND DIAGNOSTIC-  command supplied format field (see 9.3.1.1).    E  A reserved area (RAREA) bit of one indicates that all or part of the J  translated address falls within a reserved area of the medium (e.g. speedF  tolerance gap, alternate sector, vendor reserved area, etc.).  If theJ  entire translated address falls within a reserved area the target may notJ  return a translated address.  An RAREA bit of zero indicates that no partF  of the translated address falls within a reserved area of the medium.   F  An alternate sector (ALTSEC) bit of one indicates that the translatedH  address is physically located in an alternate sector of the medium.  IfH  the target cannot determine if all or part of the translated address isI  located in an alternate sector it shall set this bit to zero.  An ALTSEC H  bit of zero indicates that no part of the translated address is locatedE  in an alternate sector of the medium or that the target is unable to   determine this information.  oI  An alternate track (ALTTRK) bit of one indicates that part or all of thewI  translated address is located on an alternate track of the medium or the.D  target cannot determine if all or part of the translated address isH  located on an alternate track.  An ALTTRK bit of zero indicates that noG  part of the translated address is located on an alternate track of thei  medium.   H  The translated format field contains the value from the SEND DIAGNOSTIC.  command translate format field (see 9.3.1.1).  iK  The translated address field contains the address(s) the target translated K  from the address supplied by the initiator in the SEND DIAGNOSTIC command.rK  This field shall be in the format specified in the translate format field.CF  The different formats are described in 9.2.1.1.  If the logical blockJ  format is specified the block address shall be in the first four bytes of8  the field and the remaining bytes shall be set to zero.  rK  If the returned data is in the logical block or physical sector format andeG  the address to be translated covers more than one address after it hastJ  been translated (e.g. accounting for speed tolerance or multiple physicalH  sectors within a single logical block or multiple logical blocks withinI  a single physical sector) the target shall return all possible addressesaK  which are contained in the area specified by the address to be translated.r   K  If the returned data is in bytes from index format the target shall return=I  a pair of translated values for each of the possible addresses which are|K  contained in the area specified by the address to translate field.  Of the-E  pair of translated values returned, the first indicates the starting|9  location and the second the ending location of the area.      9.3.2 Log parameters4   I  This subclause defines the descriptors and pages for log parameters used1  with direct-access devices. e  eG  The log page codes for direct-access devices are defined in table 152.    5                            Table 152 - Log page codesFP  +=============-==================================================-============+P  |  Page code  |  Description                                     | Subclause  |P  |-------------+--------------------------------------------------+------------|P  |     01h     |  Buffer over-run/under-run page                  |  8.3.2.1   |P  |     03h     |  Error counter page (read) page                  |  8.3.2.2   |P  |     05h     |  Error counter page (verify) page                |  8.3.2.2   |P  |     02h     |  Error counter page (write) page                 |  8.3.2.2   |P  |     07h     |  Last n error events page                        |  8.3.2.3   |P  |     06h     |  Non-medium error page                           |  8.3.2.    |P  |     00h     |  Supported log pages                             |  8.3.2.5   |P  |     04h     |  Reserved                                        |            |P  |  08h - 2Fh  |  Reserved                                        |            |P  |     3Fh     |  Reserved                                        |            |P  |  30h - 3Eh  |  Vendor-specific pages                           |            |P  +=============================================================================+  (  )  9.3.3 Mode parameters   J  This subclause defines the descriptors and pages for mode parameters used  with direct-access devices.     F  The mode parameter list, including the mode parameter header and mode)  block descriptor are described in 8.3.3.-  -J  The medium-type code field is contained in the mode parameter header (seeA  8.3.3).  Table 153 defines this field for direct-access devices.g  (=                   Table 153 - Direct-access medium-type codes P  +=======-=====================================================================+P  |  Code |                                                                     |P  | value |                        Medium type                                  |P  |-------+---------------------------------------------------------------------|P  |  00h  |  Default medium type (currently mounted medium type)                |P  |  01h  |  Flexible disk, single-sided; unspecified medium                    |P  |  02h  |  Flexible disk, double-sided; unspecified medium                    |P  |       |                                                                     |P  |       |                     Flexible disks                                  |P  |       |  Diameter    Bit density  Track density  Number     ANSI reference  |P  |       |  mm (in)     Bits/radian   /mm (/in)     of sides      standard     |P  |       | ----------  -----------  -------------  --------  ----------------  |P  |  05h  | 200 (8,0)      6 631        1,9 (48)        1      ANSI X3.73-1980  |P  |  06h  | 200 (8,0)      6 631        1,9 (48)        2          (Note 1)     |P  |  09h  | 200 (8,0)     13 262        1,9 (48)        1            None       |P  |  0Ah  | 200 (8,0)     13 262        1,9 (48)        2      ANSI X3.121-1984 |P  |  0Dh  | 130 (5,25)     3 979        1,9 (48)        1      ANSI X3.82-1980  |P  |  12h  | 130 (5,25)     7 958        1,9 (48)        2      ANSI X3.125-1985 |P  |  16h  | 130 (5,25)     7 958        3,8 (96)        2      ANSI X3.126-1986 |P  |  1Ah  | 130 (5,25)    13 262        3,8 (96)        2      ISO DIS8630-1985 |P  |  1Eh  |  90 (3,5)      7 958        5,3 (135)       2        ANSI X3.137    |P  |       |                                                        (Note 2)     |P  |       |             Direct-access magnetic yapes                            |P  |       |  Width               Density      ANSI reference                    |P  |       |  mm (in)     Tracks  ftpmm (ftpi)    standard                       |P  |       | ----------  ------  ------------  --------------                    |P  |  40h  | 6,3 (0,25)    12    394 (10 000)      Note 1                        |P  |  44h  | 6,3 (0,25)    24    394 (10 000)      Note 1                        |P  |-----------------------------------------------------------------------------|P  |  Code values 80h - FFh are vendor-specific.  All remaining code values      |P  |  are reserved.                                                              |P  |-----------------------------------------------------------------------------|P  |  NOTES                                                                      |P  |   1  See annex c for additional standards information.                      |P  |   2  This standard is under development.  Please contact the secretariat    |P  |      for current information on status and availability.                    |P  +=============================================================================+      H  The device specific parameter field (see table 154) is contained in the#  mode parameter header (see 8.3.3).-  -:                      Table 154 - Device specific parameterP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |=====+========+=================+========+===================================|P  |     |   WP   |     Reserved    | DPOFUA |             Reserved              |P  +=============================================================================+  -  -I  When used with the MODE SELECT command the write protect (WP) bit is not 	  defined.v   J  When used with the MODE SENSE command a WP bit of zero indicates that theG  medium is write enabled.  A WP bit of one indicates that the medium isA  write protected.   sK  When used with the MODE SELECT command, the DPOFUA bit is not used and the=  field is reserved.=  =J  When used with the MODE SENSE command, a DPOFUA bit of one indicates thatJ  the target supports the DPO and FUA bits (see 9.2.6).  When used with theH  MODE SENSE command, a DPOFUA bit of zero indicates that the target does"  not support the DPO and FUA bits.   K  The density code field is contained in the mode parameter block descriptor @  (see 7.3.3).  This field is reserved for direct-access devices.   F  The mode page codes for direct-access devices are shown in table 155.  -5                           Table 155 - Mode page codes P  +=============-==================================================-============+P  |  Page code  |  Description                                     | Subclause  |P  |-------------+--------------------------------------------------+------------|P  |     08h     |  Caching page                                    |  9.3.3.1   |P  |     0Ah     |  Control mode page                               |  8.3.3.1   |P  |     02h     |  Disconnect-reconnect page                       |  8.3.3.2   |P  |     05h     |  Flexible disk page                              |  9.3.3.2   |P  |     03h     |  Format device page                              |  9.3.3.3   |P  |     0Bh     |  Medium types supported page                     |  9.3.3.4   |P  |     0Ch     |  Notch and partition page                        |  9.3.3.5   |P  |     09h     |  Peripheral device page                          |  8.3.3.3   |P  |     01h     |  Read-write error recovery page                  |  9.3.3.6   |P  |     04h     |  Rigid disk geometry page                        |  9.3.3.7   |P  |     07h     |  Verify error recovery page                      |  9.3.3.8   |P  |     06h     |  Reserved                                        |            |P  |  0Dh - 1Fh  |  Reserved                                        |            |P  |     00h     |  Vendor-specific (does not require page format)  |            |P  |  20h - 3Eh  |  Vendor-specific (page format required)          |            |P  |     3Fh     |  Return all pages                                |            |P  |             |     (valid only for the MODE SENSE command)      |            |P  +=============================================================================+  z  .I  For direct-access devices, if the notch page is not supported, or if the G  active notch field in the notch page is zero then each page descriptornJ  specifies mode parameters for the target to use for subsequent operationsH  on the specified logical unit.  If the notch page is supported, and theI  active notch is not zero, then each page descriptor specifies parameterslB  for the target to use for subsequent operations on the disk notchJ  specified by the current value of the active notch field on the specified  logical unit.  a  9.3.3.1 Caching page   dH  The caching parameters page (see table 156) defines the parameters that  affect the use of the cache.r   4                             Table 156 - Caching pageP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+========+========+=====================================================|P  | 0   |   PS   |Reserved|        Page code (08h)                              |P  |-----+-----------------------------------------------------------------------|P  | 1   |                          Page length (0Ah)                            |P  |-----+-----------------------------------------------------------------------|P  | 2   |                          Reserved          |  WCE   |   MF   |  RCD   |P  |-----+-----------------------------------------------------------------------|P  | 3   |   Demand read retention priority  |     Write retention priority      |P  |-----+-----------------------------------------------------------------------|P  | 4   | (MSB)                                                                 |P  |-----+---                       Disable pre-fetch transfer length         ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   | (MSB)                                                                 |P  |-----+---                       Minimum pre-fetch                         ---|P  | 7   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 8   | (MSB)                                                                 |P  |-----+---                       Maximum pre-fetch                         ---|P  | 9   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 10  | (MSB)                                                                 |P  |-----+---                       Maximum pre-fetch ceiling                 ---|P  | 11  |                                                                 (LSB) |P  +=============================================================================+      K  The parameters savable (PS) bit is only used with the MODE SENSE command.  D  This bit is reserved with the MODE SELECT command.  A PS bit of oneJ  indicates that the target is capable of saving the page in a non-volatileK  vendor-specific location.  If the PS is set to one in MODE SENSE data thendJ  the page shall be savable by issuing a MODE SELECT command with SP set to  one.=  =G  A write cache enable (WCE) bit of zero specifies that the target shall I  return GOOD status for a WRITE command after successfully writing all ofpH  the data to the medium.  A WCE bit of one specifies that the target mayH  return GOOD status for a WRITE command after successfully receiving the@  data and prior to having successfully written it to the medium.  hI  A multiplication factor (MF) bit of zero specifies that the target shallrJ  interpret the minimum and maximum pre-fetch fields in terms of the numberH  of logical blocks for each of the respective types of pre-fetch.  An MFE  bit of one specifies that the target shall interpret the minimum and E  maximum pre-fetch fields to be specified in terms of a scaler numbermI  which, when multiplied by the number of logical blocks to be transferred-I  for the current command, yields the number of logical blocks for each oft#  the respective types of pre-fetch.    E  A read cache disable (RCD) bit of zero specifies that the target may I  return data requested by a READ command by accessing either the cache ormI  media.  A RCD bit of one specifies that the target shall transfer all of J  the data requested by a READ command from the medium (i.e. data cannot be  transferred from the cache).    E  The demand read retention priority field (see table 157) advises the I  target on the retention priority to assign data read into the cache that <  has also been transferred from the target to the initiator.  -B               Table 157 - Demand read and write retention priorityP  +===========-=================================================================+P  |   Value   |  Description                                                    |P  |-----------+-----------------------------------------------------------------|P  |     0h    |  Indicates the target should not distinguish between retaining  |P  |           |  the indicated data and data placed into the cache memory by    |P  |           |  other means (e.g. pre-fetch).                                  |P  |           |                                                                 |P  |     1h    |  Demand read retention priority:  Data put into the cache via a |P  |           |  READ command should be replaced sooner (has lower priority)    |P  |           |  than data placed into the cache by other means (e.g.           |P  |           |  pre-fetch).                                                    |P  |           |                                                                 |P  |           |  Write retention priority:  Data put into the cache during a    |P  |           |  WRITE or WRITE AND VERIFY command should be replaced sooner    |P  |           |  (has lower priority) than data placed into the cache by other  |P  |           |  means (e.g. pre-fetch).                                        |P  |           |                                                                 |P  |     Fh    |  Demand read retention priority:  Data put into the cache via a |P  |           |  READ command should not be replaced if there is other data in  |P  |           |  the cache that was placed into the cache by other means (e.g.  |P  |           |  pre-fetch) and it may be replaced (i.e. it is not locked).     |P  |           |                                                                 |P  |           |  Write retention priority:  Data put into the cache during a    |P  |           |  WRITE or WRITE AND VERIFY command should not be replaced if    |P  |           |  there is other data in the cache that was placed into the cache|P  |           |  by other means (e.g. pre-fetch) and it may be replaced (i.e.   |P  |           |  it is not locked).                                             |P  |           |                                                                 |P  |  2h - Eh  |  Reserved                                                       |P  +=============================================================================+      I  The write retention priority field (see table 157) advises the target on=K  the retention priority to assign data written into the cache that has alsoW6  been transferred from the cache memory to the medium.  )K  An anticipatory pre-fetch occurs when data is placed in the cache that has J  not been requested.  This usually happens in conjunction with the readingG  of data that has been requested.  All the following parameters give anEJ  indication to the target how it should manage the cache based on the lastB  READ command.  An anticipatory pre-fetch may occur based on otherK  information. All the remaining caching parameters are only recommendations E  to the target and should not cause a CHECK CONDITION to occur if thet#  target cannot satisfy the request.F  bD  The disable pre-fetch transfer length field specifies the selectiveI  disabling of anticipatory pre-fetch on long transfer lengths.  The valueeK  in this field is compared to the number of blocks requested by the current H  READ command.  If the number of blocks is greater than the disable pre-J  fetch transfer length, then an anticipatory pre-fetch is not done for theJ  command.  Otherwise the target should attempt an anticipatory pre-fetch. B  If the pre-fetch disable transfer length is set to zero, then allJ  anticipatory pre-fetching is disabled for any request for data, including  those for zero logical blocks.h   E  The minimum pre-fetch field indicates either a number of blocks or a H  scaler multiplier of the transfer length, depending upon the setting ofJ  the MF bit.  In either case, the resulting number of blocks is the numberB  to pre-fetch regardless of the delays it might cause in executing  subsequent commands.    I  The pre-fetching operation begins at the logical block immediately after|I  the last logical block of the previous READ command.  Pre-fetching shall3G  always halt before the end of the media.  Errors that occur during the J  pre-fetching operation shall not be reported to the initiator unless thatE  target cannot, as a result of the error, execute subsequent commands I  correctly.  In this case the error may be reported either immediately aseF  an error for the current READ command, or as a deferred error, at theK  discretion of the target and according to the rules for reporting deferred   errors.   D  If pre-fetch has read more than the amount of data indicated by theJ  minimum pre-fetch then pre-fetching should be terminated whenever anotherE  command is ready to execute.  This consideration is ignored when the|6  minimum pre-fetch is equal to the maximum pre-fetch.    E  The maximum pre-fetch field indicates either a number of blocks or a H  scaler multiplier of the transfer length, depending upon the setting ofJ  the MF bit.  In either case, the resulting number of blocks is the numberF  to pre-fetch if there are no delays in executing subsequent commands.  rH  The maximum pre-fetch field contains the maximum amount of data to pre-E  fetch into the cache as a result of one READ command.  It is used in H  conjunction with the disable pre-fetch transfer length and maximum pre-A  fetch ceiling parameters to trade off pre-fetching new data withe1  displacing old data already stored in the cache.h  uK  The maximum pre-fetch ceiling field specifies an upper limit on the number9H  of logical blocks computed as the maximum pre-fetch.  If this number ofI  blocks is greater than the maximum pre-fetch, then the number of logical J  blocks to pre-fetch shall be truncated to the value stored in the maximum  pre-fetch ceiling field.=  =O     NOTE 124 If the MF bit is one the maximum pre-fetch ceiling field is useful 5     in limiting the amount of data to be pre-fetched.      9.3.3.2 Flexible disk page   |K  The flexible disk page (see table 158) contains parameters for control and=-  reporting of flexible disk drive parameters.d  07                          Table 158 - Flexible disk page-P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+========+========+=====================================================|P  | 0   |   PS   |Reserved|         Page code (05h)                             |P  |-----+-----------------------------------------------------------------------|P  | 1   |                           Page length in bytes (1Eh)                  |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                        Transfer rate                            ---|P  | 3   |                                                                  (LSB)|P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Number of heads                             |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Sectors per track                           |P  |-----+-----------------------------------------------------------------------|P  | 6   | (MSB)                                                                 |P  |-----+---                     Data bytes per sector                      ----|P  | 7   |                                                                  (LSB)|P  |-----+-----------------------------------------------------------------------|P  | 8   | (MSB)                                                                 |P  |-----+---                       Number of cylinders                       ---|P  | 9   |                                                                  (LSB)|P  |-----+-----------------------------------------------------------------------|P  | 10  | (MSB)                                                                 |P  |-----+---                Starting cylinder-write precompensation             |P  | 11  |                                                                  (LSB)|P  |-----+-----------------------------------------------------------------------|P  | 12  | (MSB)                                                                 |P  |-----+---                Starting cylinder-reduced write current             |P  | 13  |                                                                  (LSB)|P  |-----+-----------------------------------------------------------------------|P  | 14  | (MSB)                                                                 |P  |-----+---                       Drive step rate                           ---|P  | 15  |                                                                  (LSB)|P  |-----+-----------------------------------------------------------------------|P  | 16  |                          Drive step pulse width                       |P  |-----+-----------------------------------------------------------------------|P  | 17  | (MSB)                                                                 |P  |-----+---                       Head settle delay                         ---|P  | 18  |                                                                  (LSB)|P  |-----+-----------------------------------------------------------------------|P  | 19  |                          Motor on delay                               |P  |-----+-----------------------------------------------------------------------|P  | 20  |                          Motor off delay                              |P  |-----+-----------------------------------------------------------------------|P  | 21  | TRDY   |   SSN  |   MO   |            Reserved                        |P  |-----+-----------------------------------------------------------------------|P  | 22  |            Reserved               |               SPC                 |P  |-----+-----------------------------------------------------------------------|P  | 23  |                          Write compensation                           |P  |-----+-----------------------------------------------------------------------|P  | 24  |                          Head load delay                              |P  |-----+-----------------------------------------------------------------------|P  | 25  |                          Head unload delay                            |P  |-----+-----------------------------------------------------------------------|P  | 26  |             Pin 34                |               Pin 2               |P  |-----+-----------------------------------+-----------------------------------|P  | 27  |             Pin 4                 |               Pin 1               |P  |-----+-----------------------------------------------------------------------|P  | 28  |                                                                       |P  |-----+---                       Medium rotation rate                      ---|P  | 29  |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 30  |                          Reserved                                     |P  |-----+-----------------------------------------------------------------------|P  | 31  |                          Reserved                                     |P  +=============================================================================+      K  The parameters savable (PS) bit is only used with the MODE SENSE command. tD  This bit is reserved with the MODE SELECT command.  A PS bit of oneJ  indicates that the target is capable of saving the page in a non-volatile  vendor-specific location.  lM     NOTE 125 This page is mainly intended for defining parameters of flexibleyB     disk drives, but may be used for other devices, if applicable.   I  The transfer rate indicates the data rate of the peripheral device.  See 1  table 159 for examples of common transfer rates.    ;                      Table 159 - Examples of transfer rates +  +=========-==============================+=+  |  Value  |  Transfer rate               | +  |---------+------------------------------|b+  |  00FAh  |  250 kbit/s transfer rate    |n+  |  012Ch  |  300 kbit/s transfer rate    |h+  |  01F4h  |  500 kbit/s tranfer rate     |c+  |  03E8h  |  1 mbit/s transfer rate      |o+  |  07D0h  |  2 mbit/s transfer rate      |e+  |  1388h  |  5 mbit/s transfer rate      |u+  +========================================+g  o  aI  The number of heads field specifies the number of heads used for readingtB  and writing data on the medium.  Heads used exclusively for servo  information are excluded.   K  The sectors per track field specifies the number of sectors per revolutiona
  per head.  lJ  The data bytes per sector field specifies the number of bytes of data per,  sector that an initiator can read or write.  tI  The number of cylinders field specifies the number of cylinders used fore  data storage. n  iD  The starting cylinder for write precompensation field specifies theD  cylinder at which write precompensation is to begin.  Cylinders areA  numbered starting with zero.  If the starting cylinder for write H  precompensation is equal to the value in the number of cylinders field,9  write precompensation shall be disabled by the target.  a  yI  The starting cylinder for reduced write current field specifies cylindernI  at which write current is reduced.  Cylinders are numbered starting withuJ  zero.  If the starting cylinder for reduced write current is equal to theG  value in the number of cylinders field, reduced write current shall ber  disabled by the target.    tG  The drive step rate field specifies the step rate in units of 100 us. hI  This value may be rounded as defined in 7.5.4.  A value of zero requestsg%  the target to set its default value.f  hJ  The drive step pulse width field specifies the width of the step pulse inJ  microseconds.  This value may be rounded as defined in 7.5.4.  A value of3  zero requests the target to set its default value.    K  The head settle delay field specifies the head settle time in units of 100 E  us.  This value may be rounded as defined in 7.5.4.  A value of zero .  requests the target to set its default value.   B  If a true ready signal is not available, the motor on delay fieldK  specifies in tenths of a second the time that the target shall wait beforelH  attempting to access the medium after the motor on signal is asserted. H  If a true ready signal is available, the motor on delay field specifiesJ  in tenths of a second the time that the target shall wait for drive readyH  status before aborting an attempt to access the medium.  This value may"  be rounded as defined in 7.5.4.    fH  The motor off delay field specifies in tenths of a second the time thatI  the target shall wait before releasing the motor on signal after an idleeK  condition exists.  A value of FFh indicates that the motor on signal shallaF  not be released.  The START STOP UNIT command is not affected by this<  parameter. This value may be rounded as defined in 7.5.4.     H  A true ready (TRDY) bit of one specifies that a signal is provided that.  indicates the medium is ready to be accessed.  uK  A start sector number (SSN) bit of one specifies that sectors are numbereddK  starting with one.  An SSN bit of zero specifies that sectors are numberedc  starting with zero.   I  A motor on (MO) bit of one specifies that pin 16 (motor on) shall remainfF  released.  This bit shall be set to one when using high capacity (192I  tracks per inch) drives and their pre-formatted diskettes.  An MO bit ofe9  zero indicates that pin 16 (motor on) shall be asserted.=   I  The step pulse per cylinder (SPC) field is used to specify the number ofuG  additional step pulses required per cylinder.  Non-zero values allow aFE  drive to read a diskette formatted on a drive with a lower number ofsI  tracks per inch.  For example, a value of one allows a 96 track-per-inchdJ  drive to access tracks on a diskette that was formatted for 48 tracks per  inch.  =D  The write compensation field is used to specify the amount of writeK  compensation to be used starting at the cylinder specified in the starting|I  cylinder for write precompensation field.  The correlation of any values|J  used in this field to actual write precompensation time values is vendor-I  specific.  If a zero is specified in this field the target shall use its K  default write precompensation value.  This value may be rounded as defined-  in 7.5.4.    1L  The head load delay field specifies the head loading time in milliseconds. I  This value may be rounded as defined in 7.5.4.  A value of zero requests-%  the target to set its default value.    A  The head unload delay field specifies the head unloading time in J  milliseconds.  This value may be rounded as defined in 7.5.4.  A value of3  zero requests the target to set its default value.   LH  The Pin 34 field defines the usage of pin 34 of the flexible disk driveG  interface.  This use of this pin varies among vendors and drives.  The G  settings allow the initiator to select how pin 34 shall be used by the-  interface.  See table 160.   54                             Table 160 - Pin 34 fieldP  +==============-==============================================================+P  | Bit 7 6 5 4  |  Description of pin 34 use                                   |P  |--------------+--------------------------------------------------------------|P  |     P 0 0 0  |  Open                                                        |P  |     P 0 0 1  |  Ready                                                       |P  |     P 0 1 0  |  Disk changed                                                |P  |-----------------------------------------------------------------------------|P  |  NOTES                                                                      |P  |   1  P is a polarity bit, where 0 is active low and 1 is active high.       |P  |   2  All undefined values are reserved.                                     |P  +=============================================================================+  a  nF  The pin 4 field defines the usage of pin 4 of the flexible disk driveI  interface.  This use of this pin varies among drive vendors and drives. -H   The settings allow the initiator to specify how pin 4 shall be used by  the interface.  See table 161.   |3                             Table 161 - Pin 4 fielddP  +==============-==============================================================+P  | Bit 7 6 5 4  |  Description of pin 4 use                                    |P  |--------------+--------------------------------------------------------------|P  |     P 0 0 0  |  Open                                                        |P  |     P 0 0 1  |  In use                                                      |P  |     P 0 1 0  |  Eject                                                       |P  |     P 0 0 0  |  Head load                                                   |P  |-----------------------------------------------------------------------------|P  |  NOTES                                                                      |P  |   1  P is a polarity bit, where 0 is active low and 1 is active high.       |P  |   2  All undefined values are reserved.                                     |P  +=============================================================================+  -  -F  The pin 1 field defines the usage of pin 1 of the flexible disk driveG  interface.  This use of this pin varies among vendors and drives.  The-G  settings allow the initiator to specify how pin 1 shall be used by the   interface.  See table 162.    4                             Table 162 - Pin 34 fieldP  +==============-==============================================================+P  | Bit 7 6 5 4  |  Description of pin 34 use                                   |P  |--------------+--------------------------------------------------------------|P  |     P 0 0 0  |  Open                                                        |P  |     P 0 0 1  |  Disk change reset                                           |P  |-----------------------------------------------------------------------------|P  |  NOTES                                                                      |P  |   1  P is a polarity bit, where 0 is active low and 1 is active high.       |P  |   2  All undefined values are reserved.                                     |P  +=============================================================================+  -  -G  The medium rotation rate field specifies the speed at which the medium I  rotates.  The unit of measure is rotations per minute (e.g. 2 400 rpm). -7  This field cannot be changed by a MODE SELECT command.      9.3.3.3 Format device page|   I  The format device page (see table 163) contains parameters which specify-  the medium format.-  -7                          Table 163 - Format device page P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+========+========+=====================================================|P  | 0   |   PS   |Reserved|            Page code (03h)                          |P  |-----+-----------------------------------------------------------------------|P  | 1   |                              Page length (16h)                        |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                  Tracks per zone                                ---|P  | 3   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 4   | (MSB)                                                                 |P  |-----+---                  Alternate sectors per zone                     ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   | (MSB)                                                                 |P  |-----+---                  Alternate tracks per zone                      ---|P  | 7   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 8   | (MSB)                                                                 |P  |-----+---                  Alternate tracks per logical unit              ---|P  | 9   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 10  | (MSB)                                                                 |P  |-----+---                  Sectors per track                              ---|P  | 11  |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 12  | (MSB)                                                                 |P  |-----+---                  Data bytes per physical sector                 ---|P  | 13  |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 14  | (MSB)                                                                 |P  |-----+---                  Interleave                                     ---|P  | 15  |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 16  | (MSB)                                                                 |P  |-----+---                  Track skew factor                              ---|P  | 17  |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 18  | (MSB)                                                                 |P  |-----+---                  Cylinder skew factor                           ---|P  | 19  |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 20  |  SSEC  |  HSEC  |  RMB   |  SURF  |             Reserved              |P  |-----+-----------------------------------------------------------------------|P  | 21  |                                                                       |P  |- - -+---                  Reserved                                       ---|P  | 23  |                                                                       |P  +=============================================================================+     nK  The parameters savable (PS) bit is only used with the MODE SENSE command. tD  This bit is reserved with the MODE SELECT command.  A PS bit of oneJ  indicates that the target is capable of saving the page in a non-volatile  vendor-specific location.  hL     NOTE 126 If the initiator changes any of the current physical parametersP     defined below, the target may not be able to access the media until a FORMAT1     UNIT command has been successfully completed.h  sE  If the defect handling format parameters (tracks per zone, alternate E  sectors per zone, alternate tracks per zone and alternate tracks pertJ  logical unit) requested by the initiator are not supported by the target G  the target may round these fields to acceptable values as described inp	  7.5.4.  r  )I  The tracks per zone field specifies the number of tracks per zone to usetE  in dividing the capacity of the device for the purpose of allocating.K  alternate sectors.  A value of zero means that one zone is defined for thetG  entire device.  The last zone on the device might not contain the samew,  number of tracks as the previous zone(s).    nI  The alternate sectors per zone field specifies the number of sectors permI  zone the target shall reserve for defect handling.  The target shall de- H  allocate these sectors from the initiator addressable blocks during theI  FORMAT UNIT command.  If the notch page is implemented and the ND bit ofiF  the notch page is one and the active notch field of the notch page isH  zero, then a value of zero indicates that no alternate sectors shall beC  reserved.  Otherwise, a value of zero indicates that the number ofi&  alternate sectors is target specific.  sG  The alternate tracks per zone field specifies the number of tracks perdI  zone the target shall reserve for defect handling.  The target shall de-dG  allocate these tracks from the initiator addressable blocks during thedI  FORMAT UNIT command.  If the notch page is implemented and the ND bit of.F  the notch page is one and the active notch field of the notch page isG  zero, then a value of zero indicates that no alternate tracks shall be C  reserved.  Otherwise, a value of zero indicates that the number ofh%  alternate tracks is target specific.l   K  The alternate tracks per logical unit field specifies the number of tracks J  per logical unit the target shall reserve for defect handling. The targetE  shall de-allocate these tracks from the initiator addressable blockssJ  during the FORMAT UNIT command.  If the notch page is implemented and theH  ND bit of the notch page is one and the active notch field of the notchF  page is zero, then a value of zero indicates that no alternate tracksI  shall be reserved.  Otherwise, a value of zero indicates that the number (  of alternate tracks is target specific.   G  The sectors per track field specifies the number of physical sectors  -H  included within each track.  This number includes any alternate sectorsG  the target may allocate.  A value of zero during MODE SELECT indicatesaK  that the target shall define the number of sectors per track.  For deviceslF  with a variable number of sectors per track, the value in MODE SELECTE  shall be zero and the value reported in MODE SENSE for the number of=&  sectors per track is vendor-specific.  tF  The data bytes per physical sector field specifies the number of dataH  bytes per physical sector that the target shall use.  This value may beI  different than the logical block size reported in the MODE SELECT data. eI  The target shall return CHECK CONDITION status if it determines that the=E  combination of this field and the sectors per track field exceed the I  capability of the medium.  A value of zero indicates that the data bytes .  per physical sector is defined by the target.  -I  For MODE SENSE the interleave field returns the same parameter passed in F  the FORMAT UNIT command, The target shall report this field as targetG  defined in the corresponding MODE SENSE command.  For MODE SELECT thise  field is ignored.   P     NOTE 127 It is recommended that this field be marked non-changeable and thatO     initiators send the value returned in MODE SENSE.  This allows migration to-K     specifying interleave as a mode parameter instead of in the FORMAT UNIT      command.   E  The track skew factor field specifies the number of physical sectorswH  between the last logical block of one track and the first logical block3  on the next sequential track of the same cylinder.=  =H  The cylinder skew factor field specifies the number of physical sectorsK  between the last logical block of one cylinder and the first logical blocka!  on the next sequential cylinder.o  vH  The SSEC bit set to one indicates that the target shall use soft sector  formatting.  bH  The HSEC bit set to one indicates that the target shall use hard sectorJ  formatting.  The HSEC bit and the SSEC bit are mutually exclusive in MODE  SELECT commands.=  =K  The combinations sector formatting supported that are reported in response :  to a request for default values are defined in table 164.  -E            Table 164 - Reporting of default sector formatting support I  +======-======-========================================================+ I  | SSEC | HSEC |  Description                                           |-I  |------+------+--------------------------------------------------------| I  |   0  |   0  |  Target shall not return this combination              |tI  |   1  |   0  |  Target supports soft sector formatting only           |eI  |   0  |   1  |  Target supports hard sector formatting only           |=I  |   1  |   1  |  Target supports both soft and hard sector formatting  | I  +======================================================================+   r  tK  The combinations sector formatting supported that are reported in responsei=  to a request for changeable values are defined in table 165.F  aF          Table 165 - Reporting of changeable sector formatting supportI  +======-======-========================================================+TI  | SSEC | HSEC |  Description                                           |-I  |------+------+--------------------------------------------------------| I  |   0  |   0  |  Sector formatting not changeable                      | I  |   1  |   0  |  Target shall not return this combination              |+I  |   0  |   1  |  Target shall not return this combination              |sI  |   1  |   1  |  Target supports both soft and hard sector formatting  |-I  +======================================================================+|      C  The removable (RMB) bit set to one indicates that the logical unit-E  supports removable media.  A RMB  bit set to zero indicates that the-G  logical unit does not support removable media.  The status of this bit E  shall be reflected in the INQUIRY command removable media bit (RMB).    C  The surface (SURF) bit set to zero indicates that the target shall G  allocate progressive addresses to all logical blocks within a cylinder-H  prior to allocating addresses on the next cylinder.  A  SURF bit set toJ  one indicates that the target shall allocate progressive addresses to allH  logical blocks on a surface prior to allocating sector addresses on the  next surface.   N     NOTE 128 If the target supports savable parameters, all savable parametersO     for this initiator, including those in page codes 3, 4, and 5, are saved to H     non-volatile memory when the save parameters bit (SP) in the commandP     descriptor block is set to one.  The savable parameters may also be saved toA     non-volatile memory during a FORMAT UNIT command (see 9.2.1).-  -$  9.3.3.4 Medium types supported page  -G  The medium types supported page (see table 166) contains a list of the :  medium types implemented by the target for logical units.  a;                     Table 166 - Medium types supported page P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+========+========+=====================================================|P  | 0   |   PS   |Reserved|         Page code (0Bh)                             |P  |-----+-----------------------------------------------------------------------|P  | 1   |                           Page length (06h)                           |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Medium type one supported                   |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Medium type two supported                   |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Medium type three supported                 |P  |-----+-----------------------------------------------------------------------|P  | 7   |                           Medium type four supported                  |P  +=============================================================================+      K  The parameters savable (PS) bit is only used with the MODE SENSE command. -D  This bit is reserved with the MODE SELECT command.  A PS bit of oneJ  indicates that the target is capable of saving the page in a non-volatile  vendor-specific location.  -I  The code values for each medium type supported by the target (up to four G  maximum), are reported in ascending order.  If only the default medium H  type is supported zero is reported.  If less than four medium types are8  supported the unused entries shall be returned as zero.   !  9.3.3.5 Notch and partition page=  =E  The notch page (see table 167) contains parameters for direct-accessrE  devices which implement a variable number of blocks per cylinder andiE  support this page.  Each clause of the logical unit with a differents9  number of blocks per cylinder is referred to as a notch.a  e3                              Table 167 - Notch page P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+========+========+=====================================================|P  | 0   |   PS   |Reserved|         Page code (0Ch)                             |P  |-----+-----------------------------------------------------------------------|P  | 1   |                           Page length (16h)                           |P  |-----+-----------------------------------------------------------------------|P  | 2   |   ND   |  LPN   |         Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   | (MSB)                                                                 |P  |-----+---                        Maximum number of notches                ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   | (MSB)                                                                 |P  |-----+---                        Active notch                             ---|P  | 7   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 8   | (MSB)                                                                 |P  |- - -+---                        Starting boundary                        ---|P  | 11  |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 12  | (MSB)                                                                 |P  |- - -+---                        Ending boundary                          ---|P  | 15  |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 16  | (MSB)                                                                 |P  |- - -+---                        Pages notched                            ---|P  | 23  |                                                                 (LSB) |P  +=============================================================================+  u   K  The parameters savable (PS) bit is only used with the MODE SENSE command. aD  This bit is reserved with the MODE SELECT command.  A PS bit of oneJ  indicates that the target is capable of saving the page in a non-volatile  vendor-specific location.  tJ  A notched drive (ND) bit of zero indicates that the device is not notchedH  and that all other parameters in this page shall be returned as zero byH  the target.  A ND bit of one indicates that the device is notched.  ForE  each supported active notch value this page defines the starting andd   ending boundaries of the notch.  rA  A logical or physical notch (LPN) bit of zero indicates that theCJ  boundaries are based on the physical parameters of the logical unit.  TheH  cylinder is considered most significant, the head least significant.  AH  LPN bit of one indicates that the notch boundaries are based on logical  blocks of the logical unit. E   D  The maximum number of notches field indicates the maximum number ofH  notches supported by the logical unit.  This field shall be reported as  unchangeable.  OI  The active notch field indicates the notch that this and subsequent MODE1I  SELECT and MODE SENSE commands shall refer to, until the active notch is G  changed by a later MODE SELECT command.  The value of the active notchtJ  shall be greater than or equal to 0 and less than or equal to the maximumJ  number of notches.  An active notch value of zero indicates that this andG  subsequent MODE SELECT and MODE SENSE commands refer to the parametersf   that apply across all notches.   eH  The starting boundary field indicates the beginning of the active notchG  or, if the active notch is zero, the beginning boundary of the logicalfF  unit.  If the LPN bit is one, then the four bytes represent a logicalH  block address.  If the LPN bit is zero, then the three most significantI  bytes shall represent the cylinder number and the least significant byteaB  shall represent the head number.  This field shall be reported asD  unchangeable.  When used with the MODE SELECT command this field is	  ignored.t  fJ  The ending boundary field indicates the ending of the active notch or, ifJ  the active notch is zero, the ending of the logical unit.  If the LPN bitI  is one, then the four bytes represent logical block address.  If the LPN=G  bit is zero, then the three most significant bytes shall represent the H  cylinder number and the least significant byte shall represent the headK  number.  This field shall be reported as unchangeable.  When used with thet+  MODE SELECT command this field is ignored.    I  Each notch shall span a set of consecutive logical blocks on the logical C  unit, the notches shall not overlap, and no logical block shall be1  excluded from a notch.t  oK  The pages notched field is a bit map of the mode page codes that indicates=C  which pages contain parameters that may be different for differentrJ  notches.  The most significant bit of this field corresponds to page codeJ  3Fh and the least significant bit corresponds to page code 00h.  If a bitI  is one, then the corresponding mode page contains parameters that may be=K  different for different notches.  If a bit is zero, then the corresponding G  mode page contains parameters that are constant for all notches.  This-)  field shall be reported as unchangeable.|  0'  9.3.3.6 Read-write error recovery pageb   G  The read-write error recovery page (see table 168) specifies the errormJ  recovery parameters the target shall use during any command that performsK  a read or write operation to the medium (e.g. READ(6), READ(10), WRITE(6),d1  WRITE(10), COPY, COMPARE, WRITE & VERIFY, etc.).=  ==                    Table 168 - Read-write error recovery pagebP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+========+========+=====================================================|P  | 0   |   PS   |Reserved|        Page code (01h)                              |P  |-----+-----------------------------------------------------------------------|P  | 1   |                           Page length (0Ah)                           |P  |-----+-----------------------------------------------------------------------|P  | 2   |  AWRE  |  ARRE  |   TB   |   RC   |  EER   |  PER   |  DTE   |  DCR   |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Read retry count                            |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Correction span                             |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Head offset count                           |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Data strobe offset count                    |P  |-----+-----------------------------------------------------------------------|P  | 7   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 8   |                           Write retry count                           |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 10  | (MSB)                                                                 |P  |-----+---                        Recovery time limit                      ---|P  | 11  |                                                                 (LSB) |P  +=============================================================================+      K  The parameters savable (PS) bit is only used with the MODE SENSE command. -D  This bit is reserved with the MODE SELECT command.  A PS bit of oneJ  indicates that the target is capable of saving the page in a non-volatile  vendor-specific location.  -I  An automatic write reallocation enabled (AWRE) bit of one indicates that F  the target shall enable automatic reallocation to be performed duringI  write operations.  The automatic reallocation shall be performed only if|C  the target has the valid data (e.g. original data in the buffer or C  recovered from the medium).  The valid data shall be placed in the=K  reallocated block.  Error reporting as required by the error recovery bitseI  (EER, PER, DTE, and DCR) shall be performed only after completion of the I  reallocation.  The reallocation operation shall report any failures thatiG  occur.  See the REASSIGN BLOCKS command (9.2.10) for error procedures.c  eJ  An AWRE bit of zero indicates that the target shall not perform automatic?  reallocation of defective data blocks during write operations.z   H  An automatic read reallocation enabled (ARRE) bit of one indicates thatH  the target shall enable automatic reallocation of defective data blocksJ  during read operations.  All error recovery actions required by the errorC  recovery bits (TB, EER, PER, DTE, and DCR) shall be executed.  TheiB  automatic reallocation shall then be performed only if the targetK  successfully recovers the data.  The recovered data shall be placed in the K  reallocated block.  Error reporting as required by the error recovery bits=C  shall be performed only after completion of the reallocation.  The D  reallocation process shall present any failures that occur. See the8  REASSIGN BLOCKS command (9.2.10) for error procedures.    J  An ARRE bit of zero indicates that the target shall not perform automatic>  reallocation of defective data blocks during read operations.  )I  A transfer block (TB) bit of one indicates that a data block that is not-K  recovered within the recovery limits specified shall be transferred to the G  initiator before CHECK CONDITION status is returned.  A TB bit of zero-A  indicates that such a data block shall not be transferred to the F  initiator.  The TB bit does not affect the action taken for recovered  data.  -J  A read continuous (RC) bit of one indicates the target shall transfer theG  entire requested length of data without adding delays to perform error-I  recovery procedures.  This implies that the target may send data that is I  erroneous or fabricated in order to maintain a continuous flow of data.  D  The target shall assign priority to this bit over conflicting error:  control bits (EER, DCR, DTE, and PER) within this byte.     K     NOTE 129 Fabricated data may be data already in the buffer or any other-Q     target-specific data.  This bit is typically used in image processing, audio,      or video applications.   E  A RC bit of zero indicates that error recovery operations that cause C  delays are acceptable during the data transfer.  Data shall not be   fabricated.   J  The individual bit definitions for EER, PER, DTE and DCR are contained inH  table 169.  The combinations of these bits are explained in table 170.    =                    Table 169 - Error recovery bit definitions S  +====================-===========================================================+ S  |EER  PER  DTE  DCR  |  Description                                              |-S  |--------------------+-----------------------------------------------------------| S  | 1    -    -    -   |  An enable early recovery (EER) bit of one indicates that | S  |                    |  the target shall use of the most expedient form of error | S  |                    |  recovery first.  This bit only applies to data error     |-S  |                    |  recovery and it does not affect positioning retries and  | S  |                    |  the message system error recovery procedures.            | S  |                    |                                                           ||S  | 0    -    -    -   |  An EER bit of zero indicates that the target shall use an|uS  |                    |  error recovery procedure that minimizes the risk of mis- |TS  |                    |  detection or mis-correction.                             |hS  |                    |                                                           | S  | -    1    -    -   |  A post error (PER) bit of one indicates that the target  |tS  |                    |  shall report recovered errors.                           |DS  |                    |                                                           |vS  | -    0    -    -   |  A PER bit of zero indicates that the target shall not    |gS  |                    |  report recovered errors.  Error recovery procedures shall|nS  |                    |  be performed within the limits established by the error  |iS  |                    |  recovery parameters.                                     |dS  |                    |                                                           |fS  | -    -    1    -   |  A disable transfer on error (DTE) bit of one indicates   |tS  |                    |  that the target shall terminate the data phase upon      |aS  |                    |  detection of a recovered error.                          |eS  |                    |                                                           |uS  | -    -    0    -   |  A DTE bit of zero indicates that the target shall not    |oS  |                    |  terminate the data phase upon detection of a recovered   |aS  |                    |  error.                                                   |pS  |                    |                                                           | S  | -    -    -    1   |  A disable correction (DCR) bit of one indicates that     |iS  |                    |  error correction codes shall not be used for data error  |aS  |                    |  recovery.                                                |eS  |                    |                                                           |bS  | -    -    -    0   |  A DCR bit of zero allows the use of error correction     |cS  |                    |  codes for data error recovery.                           | S  +================================================================================+.  f  eO     NOTE 130 An EER bit of one may imply an increase in the probability of mis-PM     detection or mis-correction.  An EER bit of zero typically means that thecM     specified retry limit is exhausted prior to using error correction codes..  hE            Table 170 - Combined error recovery parameter descriptions S  +====================-===========================================================+vS  |EER  PER  DTE  DCR  |  Description                                              |lS  |--------------------+-----------------------------------------------------------| S  | 0    0    0    0   |  The full number of retries (specified in the read, write |iS  |                    |  or verify retry count field) and error correction are    | S  |                    |  attempted to recover the data (EER and DCR set to 0).  A |bS  |                    |  CHECK CONDITION is not reported at the completion of the |eS  |                    |  command for recovered errors (PER set to 0).  The command|nS  |                    |  terminates with CHECK CONDITION status before the        |aS  |                    |  transfer count is exhausted only if an unrecoverable     |rS  |                    |  error is detected.  If an unrecoverable data error       |eS  |                    |  occurred, the data in the block with the unrecoverable   |mS  |                    |  error may or may not be transferred to the initiator     |)S  |                    |  depending on the setting of the transfer block (TB) bit  |=S  |                    |  (read operation only).                                   | S  |                    |                                                           | S  | 0    0    0    1   |  Error correction is disabled (DCR set to one) so only the|+S  |                    |  full number of retries (specified in the read, write or  | S  |                    |  verify retry count field) are attempted to recover the   |-S  |                    |  data (EER set to 0).  A CHECK CONDITION is not reported  |gS  |                    |  at the completion of the command for recoverable errors  |-S  |                    |  (PER set to 0).  The command terminates with CHECK       | S  |                    |  CONDITION status before the transfer count is exhausted  |-S  |                    |  only if an unrecoverable error is detected.  If an       | S  |                    |  unrecoverable data error occurred, the data in the block |-S  |                    |  with the unrecoverable error may or may not be           | S  |                    |  transferred to the initiator depending on the setting of |-S  |                    |  the transfer block (TB) bit (read operation only).       | S  |                    |                                                           |-S  | 0    0    1    0   |  Invalid mode (PER must be set to one if DTE is set to    | S  |                    |  one).  1)                                                | S  |                    |                                                           |-S  | 0    0    1    1   |  Invalid mode (PER must be set to one if DTE is set to    ||S  |                    |  one).  1)                                                |-S  |                    |                                                           | S  | 0    1    0    0   |  The full number of retries (specified in the read, write |-S  |                    |  or verify retry count field) and error correction are    | S  |                    |  attempted to recover the data (EER and DCR set to 0).    | S  |                    |  The command terminates with CHECK CONDITION status before| S  |                    |  the transfer count is exhausted only if an unrecoverable |=S  |                    |  error is detected.  If an unrecoverable data error       |tS  |                    |  occurred, the data in the block with the unrecoverable   |ES  |                    |  error may or may not be transferred to the initiator     |eS  |                    |  depending on the setting of the transfer block (TB) bit  |eS  |                    |  (read operation only).  A CHECK CONDITION with a sense   |tS  |                    |  key of RECOVERED ERROR is reported at the completion of  |eS  |                    |  the command for any recoverable error that occurs (PER   | S  |                    |  set to 1).  The information field in the sense data shall|bS  |                    |  contain the logical block address of the last recovered  |DS  |                    |  error which occurred during the transfer.                |nS  +================================================================================+(  .     Table 170 - (continued)S  +====================-===========================================================+cS  |EER  PER  DTE  DCR  |  Description                                              |lS  |--------------------+-----------------------------------------------------------|rS  |                    |                                                           |tS  | 0    1    0    1   |  Error correction is disabled (DCR set to one) so only the|uS  |                    |  full number of retries (specified in the read, write or  |eS  |                    |  verify retry count field) are attempted to recover the   |bS  |                    |  data (EER set to 0).  The command terminates with CHECK  |nS  |                    |  CONDITION status before the transfer count is exhausted  |nS  |                    |  only if an unrecoverable error is detected.  If an       |sS  |                    |  unrecoverable data error occurred, the data in the block |rS  |                    |  with the unrecoverable error may or may not be           |TS  |                    |  transferred to the initiator depending on the setting of |yS  |                    |  the transfer block (TB) bit (read operation only).  A    |tS  |                    |  CHECK CONDITION with a sense key of RECOVERED ERROR is   |aS  |                    |  reported at the completion of the command for any        |rS  |                    |  recoverable error that occurs (PER set to 1).  The       |rS  |                    |  information field in the sense data shall contain the    |vS  |                    |  logical block address of the last recovered error which  |aS  |                    |  occurred during the transfer.                            |pS  |                    |                                                           |tS  | 0    1    1    0   |  The full number of retries (specified in the read, write |oS  |                    |  or verify retry count field) and error correction are    |nS  |                    |  attempted to recover the data (EER and DCR set to 0).    |cS  |                    |  The command terminates with CHECK CONDITION status before|sS  |                    |  the transfer count is exhausted if any error (recoverable| S  |                    |  or unrecoverable) is detected (DTE set to 1).  The       |bS  |                    |  information field in the sense data shall contain the    |=S  |                    |  logical block address of the block in error.  If an      |PS  |                    |  unrecoverable data error occurs the data in the block    |-S  |                    |  with the error may or may not be transferred to the      | S  |                    |  initiator depending on the setting of the transfer block | S  |                    |  (TB) bit (read operation only).                          | S  |                    |                                                           | S  | 0    1    1    1   |  Error correction is disabled (DCR set to one) so only the| S  |                    |  full number of retries (specified in the read, write or  | S  |                    |  verify retry count field) are attempted to recover the   | S  |                    |  data (EER set to 0).  The command terminates with CHECK  | S  |                    |  CONDITION status before the transfer count is exhausted  | S  |                    |  if any error (recoverable or unrecoverable) is detected  | S  |                    |  (DTE set to 1).  The information field in the sense data | S  |                    |  shall contain the logical block address of the block in  | S  |                    |  error.  If an unrecoverable data error occurs the data in| S  |                    |  the block with the error may or may not be transferred to| S  |                    |  the initiator depending on the setting of the transfer   | S  |                    |  block (TB) bit (read operation only).                    | S  |                    |                                                           | S  | 1    0    0    0   |  The fewest possible retries and error correction are     | S  |                    |  attempted to recover the data (EER set to one and DCR set| S  |                    |  to 0).  A CHECK CONDITION is not reported at the         | S  |                    |  completion of the command for recoverable errors (PER set| S  |                    |  to 0).  The command terminates with CHECK CONDITION      | S  |                    |  status before the transfer count is exhausted only if an | S  |                    |  unrecoverable error is detected.  If an unrecoverable    | S  |                    |  data error occurred, the data in the block with the      | S  |                    |  unrecoverable error may or may not be transferred to the | S  |                    |  initiator depending on the setting of the transfer block | S  |                    |  (TB) bit (read operation only).                          | S  +================================================================================+         Table 170 - (concluded)S  +=====================-==========================================================+ S  |EER  PER  DTE  DCR   | Description                                              |oS  |---------------------+----------------------------------------------------------|rS  |                     |                                                          |=S  | 1    0    0    1    | Invalid mode (DCR must be set to zero if EER is set to   |yS  |                     | one).  1)                                                |ES  |                     |                                                          |rS  | 1    0    1    0    | Invalid mode (PER must be set to one if DTE is set to    |yS  |                     | one).  1)                                                |=S  |                     |                                                          | S  | 1    0    1    1    | Invalid mode (PER must be set to one if DTE is set to    |-S  |                     | one).  1)                                                |iS  |                     |                                                          |rS  | 1    1    0    0    | The fewest possible retries and error correction are     | S  |                     | attempted to recover the data (EER set to one and DCR set| S  |                     | to 0).  The command terminates with CHECK CONDITION      |sS  |                     | status before the transfer count is exhausted only if an |aS  |                     | unrecoverable error is detected.  If an unrecoverable    |fS  |                     | data error occurred, the data in the block with the      |rS  |                     | unrecoverable error may or may not be transferred to the |tS  |                     | initiator depending on the setting of the transfer block |dS  |                     | (TB) bit (read operation only).  A CHECK CONDITION with a|aS  |                     | sense key of RECOVERED ERROR is reported at the          | S  |                     | completion of the command for any recoverable error that | S  |                     | occurs (PER set to 1).  The information field in the     |sS  |                     | sense data shall contain the logical block address of the|iS  |                     | last recovered error which occurred during the transfer. |mS  |                     |                                                          |IS  | 1    1    0    1    | Invalid mode (DCR must be set to zero if EER is set to   |oS  |                     | one).  1)                                                |nS  |                     |                                                          |eS  | 1    1    1    0    | The fewest possible retries and error correction are     |dS  |                     | attempted to recover the data (EER set to one and DCR set| S  |                     | to 0).  The command terminates with CHECK CONDITION      |rS  |                     | status before the transfer count is exhausted if any     |dS  |                     | error (recoverable or unrecoverable) is detected (DTE set|oS  |                     | to 1).  The information field in the sense data shall    | S  |                     | contain the logical block address of the block in error. |nS  |                     | If an unrecoverable data error occurs the data in the    | S  |                     | block with the error may or may not be transferred to the| S  |                     | initiator depending on the setting of the transfer block |nS  |                     | (TB) bit (read operation only).                          | S  |                     |                                                          | S  | 1    1    1    1    | Invalid mode (DCR must be set to zero if EER is set to   |iS  |                     | one).  1)                                                |rS  |--------------------------------------------------------------------------------| S  |   1)     If an invalid mode for the error recovery combination is              |CS  |          sent by the initiator the target shall return CHECK CONDITION         |lS  |          status with the sense key set to ILLEGAL REQUEST and the              |rS  |          additional sense code set to INVALID FIELD IN PARAMETER LIST.         |tS  +================================================================================+d      G  The read and write retry count fields specify the number of times thateF  the target shall attempt its recovery algorithm during read and writeE  operations, respectively.  If the retry count field and the recoveryyH  time limit field are both specified in a MODE SELECT command, the fieldH  that requires the least time for data error recovery actions shall have  priority.     F  The correction span field specifies the size, in bits, of the largestF  data error burst for which data error correction may be attempted.  AH  correction span of zero specifies that the target shall use its default+  value or that this field is not supported.=  =F  The head offset count field specifies in two's-complement notation anE  incremental offset position from the track center to which the heads=A  shall be moved.  The effect of this field on write operations is F  unspecified.  A head offset count of zero indicates that no offset isB  specified.  A positive value indicates moving in the direction ofG  increasing logical block addresses.  A negative value indicates moving C  in the direction of decreasing logical block addresses.  Any valuet@  specified in this field does not preclude the target from usingH  positive or negative head offset during error recovery.  However, afterH  any error recovery is completed the target shall return the head offset&  to the value specified in this field.  iN     NOTE 131 The degree of offset for each incremental value and the number ofK     valid values are device specific.  It is recommended that the number of K     valid values be equal for the positive and negative head offset counts.t  rG  The target shall return CHECK CONDITION status and shall set the sense >  key to ILLEGAL REQUEST if an unsupported head offset value isH  specified.  The valid bit shall be set to one and the information fieldD  shall be set to the positive value of the maximum head offset countE  that is supported.  The target shall set the valid bit to zero if ite<  cannot determine the maximum head offset count supported.    tI     NOTE 132 If the target does not support this field, it returns a zeror%     value in the MODE SENSE command.)o  .A  The data strobe offset count field specifies in two's-complementeD  notation an incremental position to which the recovered data strobeF  shall be adjusted from its nominal setting.  The effect of this fieldG  on write operations is unspecified.  A value of zero indicates that no F  data strobe offset is specified.  A positive value indicates movementD  in a positive direction as defined by the target.  A negative valueH  indicates movement in the negative direction as defined by the target. D  Any value specified in this field does not preclude the target fromF  using positive or negative data strobe offset during error recovery. G  However, after any error recovery is completed the target shall return =  the data strobe offset to the value specified in this field.v  bN     NOTE 133 The degree of offset for each incremental value and the number ofK     valid values are device specific.  It is recommended that the number oflJ     valid values be equal for the positive and negative data strobe offset     counts.    G  The target shall return CHECK CONDITION status and shall set the sensedH  key to ILLEGAL REQUEST if an unsupported data strobe offset count valueE  is specified.  The valid bit shall be set to one and the informationdD  field shall be set to the positive value of the maximum data strobeG  offset count that is supported.  The target shall set the valid bit to H  zero if it cannot determine the maximum data strobe offset supported.       0H     NOTE 134 If the target does not support the data strobe offset count=     field, it returns a zero value in the MODE SENSE command.i  iD  The recovery time limit field specifies in increments of one ms theH  maximum time duration that the target shall use for data error recoveryE  procedures.  The target may round this value as described in 7.5.4.  C  The limits in this field specifies the maximum error recovery time|D  allowed for any individual logical block.  A recovery time limit of<  zero specifies that the target shall use its default value.  mE  If both retry count and recovery time limit are specified, the fieldn@  that specifies the recovery action of least duration shall have  priority.     '  9.3.3.7 Rigid disk drive geometry paget  nH  The rigid disk drive geometry page (see table 171) specifies parameters8  for direct-access devices employing a rigid disk drive.  i=                    Table 171 - Rigid disk drive geometry page P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+========+========+=====================================================|P  | 0   |   PS   |Reserved|         Page code (04h)                             |P  |-----+-----------------------------------------------------------------------|P  | 1   |                           Page length (16h)                           |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |- - -+---                        Number of cylinders                      ---|P  | 4   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Number of heads                             |P  |-----+-----------------------------------------------------------------------|P  | 6   | (MSB)                                                                 |P  |- - -+---               Starting cylinder-write precompensation           ---|P  | 8   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 9   | (MSB)                                                                 |P  |- - -+---               Starting cylinder-reduced write current           ---|P  | 11  |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 12  | (MSB)                                                                 |P  |-----+---                        Drive step rate                          ---|P  | 13  |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 14  | (MSB)                                                                 |P  |- - -+---                        Landing zone cylinder                    ---|P  | 16  |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 17  |                           Reserved                  |       RPL       |P  |-----+-----------------------------------------------------------------------|P  | 18  |                           Rotational offset                           |P  |-----+-----------------------------------------------------------------------|P  | 19  |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 20  | (MSB)                                                                 |P  |-----+---                        Medium rotation rate                     ---|P  | 21  |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 22  |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 23  |                           Reserved                                    |P  +=============================================================================+      A  The parameters savable (PS) bit is only used with the MODE SENSEoG  command.  This bit is reserved with the MODE SELECT command.  A PS bit D  of one indicates that the target is capable of saving the page in a'  non-volatile vendor-specific location.    I     NOTE 135 This page is intended to define drive geometry parameters oftG     rigid disk drives.  It may be used for other devices if applicable.E  eG  The number of cylinders field defines the number of physical cylindersi  used for data storage.      H  The number of heads field defines the physical number of heads used for@  data storage.  Heads used exclusively for servo information are  excluded. s  tF  The starting cylinder for write precompensation field is the physical@  cylinder at which write precompensation is to begin.  The first=  cylinder is number zero.  If the starting cylinder for write H  precompensation is equal to the value in the number of cylinders field,7  write precompensation shall be disabled by the target.n  bF  The starting cylinder for reduced write current field is the physicalC  cylinder at which write current is reduced.  The first cylinder isiD  number zero.  If the starting cylinder for reduced write current isC  equal to the value in the number of cylinders field, reduced write )  current shall be disabled by the target.m   H  The drive step rate field indicates the step rate in 100 ns increments.G  The target shall use the drive step rate, greater than or equal to the-E  drive step rate specified.  If the target rounds this field it shall G  terminate the command as described in 7.5.4.  A value of zero requestsC%  the target to set its default value.   gD  The landing zone cylinder field indicates two's complement locationB  where the target shall position the disk heads.  A negative valueD  indicates that the heads are positioned below cylinder zero by thatB  number of cylinders.  A positive value greater than the number ofG  cylinders indicates that the heads are positioned beyond the cylinderssB  used for data storage at the cylinder location specified.  A zero+  indicates that the default should be used.i  ,@  The rotational position locking (RPL) field is used for spindleE  synchronization as defined in table 172.  See K of the ANSI X3.170A-a7  1991 for further information on synchronized spindles.   l;                     Table 172 - Rotational position lockingsP  +=======-=====================================================================+P  |  RPL  |  Description                                                        |P  |-------+---------------------------------------------------------------------|P  |  00b  |  Indicates that spindle synchronization is disabled or not supported|P  |  01b  |  The target operates as a synchronized-spindle slave                |P  |  10b  |  The target operates as a synchronized-spindle master               |P  |  11b  |  The target operates as a synchronized-spindle master control       |P  +=============================================================================+  i  hL     NOTE 136 The signals and connectors used for rotational position lockingG     are external to the SCSI bus and are not part of this International 
     Standard.i  eD  If a target fails to achieve synchronization it shall create a unitF  attention condition to all initiators.  The sense key shall be set toH  UNIT ATTENTION and the additional sense code set to RPL STATUS CHANGE.   n  eG  If subsequent to achieving synchronization the target detects a changeu  of synchronization:E     a)     and, if the logical unit is not presently executing an I/OTD            process for the initiator, the target shall create a unitC            attention condition.  The sense key shall be set to UNITeL            ATTENTION and the additional sense code set to RPL STATUS CHANGE.I     b)     and, if the logical unit is presently executing an I/O processoH            and no other error occurs, then the target shall return CHECKK            CONDITION status.  The sense key shall be set to RECOVERED ERRORdH            if the target is able to complete the I/O process or HARDWAREJ            ERROR if the target is unable to complete the I/O process.  The=            additional sense code is set to RPL STATUS CHANGE.r  dG  The rotational offset indicates the amount of rotational skew that thehG  target shall use when synchronized.  The rotational skew is applied in @  the retarded direction (lagging the synchronized spindle masterC  control).  The value in the field is the numerator of a fractional @  multiplier that has 256 as its denominator (e.g. a value of 128G  indicates a one-half revolution skew).  A value of zero indicates thatuC  rotational offset shall not be used.  This value may be rounded asrF  defined in 7.5.4.  The rotational offset is not used when a target is,  configured as synchronized-spindle master.   oA  The medium rotation rate indicates the speed at which the mediumfI  rotates.  The unit of measure is rotations per minute (e.g. 3 600 rpm). d  c  p#  9.3.3.8 Verify error recovery pageu  rC  The verify error recovery page (see table 173) specifies the errorrH  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.  f;                      Table 173 - Verify error recovery page P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+========+========+=====================================================|P  | 0   |   PS   |Reserved|            Page code (07h)                          |P  |-----+-----------------------------------------------------------------------|P  | 1   |                           Parameter length (0Ah)                      |P  |-----+-----------------------------------------------------------------------|P  | 2   |             Reserved              |  EER   |  PER   |  DTE   |  DCR   |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Verify retry count                          |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Verify correction span                      |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 8   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 10  | (MSB)                                                                 |P  |-----+---                        Verify recovery time limit               ---|P  | 11  |                                                                 (LSB) |P  +=============================================================================+  -  -A  The parameters savable (PS) bit is only used with the MODE SENSE G  command.  This bit is reserved with the MODE SELECT command.  A PS bit D  of one indicates that the target is capable of saving the page in a'  non-volatile vendor-specific location.    C  The AWRE bit as defined in the read-write error recovery page (see-B  9.3.3.6) applies to the WRITE AND VERIFY command.  The VERIFY andE  COMPARE commands shall not perform automatic reallocation.  The COPY B  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.  The1  combinations of these bits is defined in 93.3.6.    D  The verify retry count field specifies the number of times that theH  target shall attempt its recovery algorithm during a verify operation. F  If the verify retry count and the verify recovery time limit are bothH  specified, the one that requires the least time for data error recovery  actions shall have priority.    E  The verify correction span field specifies the size, in bits, of the @  largest burst data error for which data error correction may beD  attempted.  If the target does not implement this field, a value of%  zero is returned in MODE SENSE data.-  -D  The verify recovery time limit field specifies in increments of oneF  millisecond the maximum time duration that the target shall use errorF  recovery procedures to recover data for an individual logical block. F  The target may round this value as described in 7.5.4.  If the verifyG  retry count and the verify recovery time limit are both specified, the-G  one that requires the least time for data error recovery actions shall   have priority.    I     NOTE 137 To disable all types of correction and retries the initiator-L     should set the EER bit to zero, the PER, DTE and DCR bits to one and the6     number of retries and recovery time limit to zero.  n2  9.4 Definitions specific to direct-access devices   D  9.4.1 cache memory:   A temporary (and often volatile) data storageB  area outside the user-accessible area.  A cache memory is usuallyG  faster to access than the medium and thus has the effect of increasing B  data throughput by reducing the number of accesses to the medium.  -F  9.4.2 non-volatile medium:  Physical storage medium that retains dataA  written to it for a subsequent read operation through a power-on=C  condition. An example of this is a disk device that stores data asa;  magnetic fields that do not require device power to exist.T   C  9.4.3 notch:  A notch refers to all or part of the medium having aiE  consistent set of geometry parameters.  Notches are used to increase G  storage capacity by optimizing the number of sectors per track betweeni  the inner and outer tracks.   H  9.4.4 user-accessible:  The area of the medium that can be read from or'  written to by READ and WRITE commands.s  eF  9.4.5 volatile medium:  Medium that may not retain data written to itA  for a subsequent read operation through a power-on condition. AndF  example of this is a silicon memory device that loses data written to  it if device power is lost.  f  w  10 Sequential-access devicesh  h  c$  10.1 Sequential-access device model  i  10.1.1 Physical elements   lG  Sequential-access devices (called devices below) optimize their use iniF  storing or retrieving user data in a sequential manner.  Since accessA  is sequential, position changes typically take a long time, wheni#  compared to direct-access devices.i  hF  Sequential-access devices are usually tape devices.  The remainder ofF  this description is from the point of view of a tape device; however,)  other implementations are not precluded.f  lE  The recording medium for tape devices consists of various widths andmF  lengths of a flexible substrate coated with a semi-permanent magneticB  material.  The recording medium may be wound onto single reels orG  encapsulated into cartridges containing both a supply reel and a take-dA  up reel.  Several American National Standards exist covering theo@  construction of reels and cartridges for interchange as well asE  recording techniques for many of the format or density combinations.e  eB  A complete unit composed of the recording medium and its physicalF  carrier (e.g. reel, cartridge, cassette) is called a volume.  Volumes?  have an attribute of being mounted or de-mounted on a suitables  transport mechanism.d  rG  Mounted is the state of a volume when the device is physically capablerF  of executing commands that cause the medium to be moved.  A volume isG  de-mounted when it is being loaded, threaded, unloaded, unthreaded, or #  when not attached to the device.  1   C  Ready is the state of the device when medium access and non-mediumoB  access commands can be executed.  The device is not ready when noE  volume is mounted or, from the initiator's perspective, whenever all=E  medium access commands report CHECK CONDITION status and a NOT READY C  sense key.  Some devices may have a separate switch function which-H  places the device in a not ready state even when a volume is mounted.    iH  The write enabled or write protected state determines when an initiator>  may write information on a volume.  This attribute is usuallyG  controlled by the user of the volume through manual intervention (e.g.   thumbwheel switch).  tF  The recording medium has two physical attributes called beginning-of-E  medium (BOM) and end-of-medium (EOM).  Beginning-of-medium is at theiG  end of the medium that is attached to the take-up reel.  End-of-mediumnE  is at the end of the medium that is attached to the supply reel.  IneD  some cases, the medium is permanently affixed to one or both of the  reel hubs.a  cC  As shown in figure 18, the entire physical length of medium is notsG  usable for recording data. For most volumes, a length of the medium isSD  reserved before the beginning-of-medium and after the end-of-mediumF  position. This is done to provide sufficient tape wraps onto the reelF  hub(s) and to ensure that recording starts in an undamaged section of  the medium.  h  a  t  a  c  t     t           t  i  c8                        Figure 18 - Typical volume layout  T$  10.1.2 Data storage characteristics  tE  The position on the medium where a pattern of recorded signal may beeE  written by one write component is called a track (see figure 19).  AeF  device may write or read from one or more tracks at a time, depending  on the format.  O  E  R  d                 g  i  b  t;                     Figure 19 - Typical medium track layouth  aG  On a new volume, recording of one or more tracks begins after mountingeE  the volume and moving from beginning-of-medium toward end-of-medium.cA  The number of tracks written at one time is called a track groupnB  (TrkGrp).  For recorded volumes, reading in the forward direction3  follows the same course of tracks as when writing.n  l@  If not all tracks are recorded at the same time, and the deviceH  reverses direction when approaching end-of-medium and begins writing onA  remaining tracks, the recording method is called serpentine. FortG  serpentine devices that record only one track at a time, each physicali2  track represents one track group (see figure 20).  e  s  c  i  e  s  n  o  e  p  l  a=                     Figure 20 - Serpentine recording example i  tE  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).  b  1     c  e  h  r  r  r  v     a;                      Figure 21 - Parallel recording examplev  fD  The serpentine and parallel recording formats shown in the previous<  examples define tracks as longitudinal patterns of recordedD  information.  One other storage format used by some devices recordsH  tracks diagonally across the medium.  This recording technique is known!  as helical scan (see figure 22).               |  |  e              |=                    Figure 22 - Helical scan recording example+  =F  For most recording formats, an area at beginning-of-medium contains a@  format identification in the form of a tone burst or some otherD  recognizable pattern.  User data is not recorded in this area.  TheG  format identification is an attribute of a volume used for interchangen2  purposes and is defined in applicable standards.   -G  When writing, the initiator needs an indication that it is approaching B  the end of the permissible recording area.  This position, called@  early-warning (EW), is typically reported to the initiator at aG  position early enough for the device to write any buffered data to the F  medium while still leaving enough room for additional recorded labelsA  or filemarks.  Some American National Standards include physical E  requirements for a marker placed on the medium to be detected by the-)  device as early-warning (see figure 23).-  -  -  |  |                  8                        Figure 23 - Early-warning example  -B  For devices which implement large data buffers, the early-warningE  position defined by a physical marker may be too close to the end of G  the recording region to permit emptying the data buffer(s).  For these-H  devices, a logical concept of early-warning is often used to signal theC  initiator at an appropriate location prior to the physical marker.-  -"  10.1.3 Partitions within a volume  |A  Another attribute of a volume is called a partition.  Partitions F  consist of one or more non-overlapped mini-volumes, each with its ownG  beginning and ending points, contained within single physical volume.  H  Each partition (x) within a volume has a defined beginning-of-partitionH  (BOP x), an early-warning position (EW x), and an end-of-partition (EOP  x).     D  All volumes have a minimum of one partition called partition 0, theG  default data partition.  For devices which support only one partition, A  the beginning-of-partition zero (BOP 0) may be equivalent to the=A  beginning-of-medium and the end-of-partition zero (EOP 0) may be=!  equivalent to the end-of-medium.   )E  When a volume is mounted, it is logically positioned to beginning of G  the default data partition (BOP 0).  When a REWIND command is receivede@  in any partition (x), the device positions to the beginning-of-  partition (BOP x).e  RH  Partitions on a volume do not need to be recorded in any defined order,C  nor do all partition numbers in a sequence need to be present on aa>  volume.  It is sufficient for a device to be able to locate aG  partition, given its code value, or determine that it does or does noto?  exist on the volume.  For interchange, information about whichRD  partitions are present on a volume may be stored on the volume in aC  device-defined area (possibly unavailable to the initiator) or the H  information may be an intrinsic attribute of the device implementation.  gE  Figure 24 shows a possible partition implementation for a four-trackvF  serpentine recording device, assuming that each track group defines a  partition.f  d     o  e  e     t  s  a  hH         Figure 24 - Partitioning example - one partition per track group  b>  Another possible partition implementation for this four-trackC  serpentine recording device is shown in figure 25, using two tracke!  groups to define each partition.n  D  E     a        e  r     o  yJ      Figure 25 - Partitioning example - one partition per two track groups   A  The previous examples show the beginning and ending points for aeE  partition aligned with physical bounds of the medium.  This is not asF  mandatory requirement for partitioning; it is sufficient for a deviceE  to be able to locate to and stay in any partition bounded by a BOP xl@  and EOP x.  In this case, a recorded mark or some other device-C  recognizable attribute could be used to delineate the partitions.  E  Figure 26 shows a possible two-partition implementation for a devicet  with only one track group.o  e  e  n  e  e  t     i  o  r      H        Figure 26 - Partitioning example - two partitions per track group   E  Three methods are defined in the MODE SENSE and MODE SELECT commandsaH  for managing partitions; each method is progressively more difficult to  implement and manage: c*     a)     device-defined fixed locations;B     b)     device-defined based on an initiator supplied number ofF            partitions and a device specific allocation algorithm; and,;     c)     definition by name and capacity by an initiator.e  p+  10.1.4 Logical elements within a partitiona   G  The area between BOP x and EOP x on a typical recorded volume containsnE  at least two types of initiator accessible elements, data blocks andnG  tape marks.  These elements are controlled and transferred between thepD  initiator and the medium using READ, READ REVERSE, WRITE, and WRITE  FILEMARKS commands.   A  A unit of data supplied or requested by an initiator is called ao;  logical block.  Logical blocks are stored according to thelG  specifications of the format for the volume and may be recorded as oneeH  or more physical blocks on the medium.  When the physical block and theG  logical block are not recorded in a one-to-one relationship, it is the C  responsibility of the device to perform all blocking, de-blocking,n@  padding, stripping, splitting or rebuilding of the logical data!  block(s) sent by an initiator.  c  bF  Filemarks are special recorded elements containing no user data.  TheA  filemark format is defined in some American National Standards. cB  Initiators traditionally use filemarks to separate user data fromB  labels and logical groupings of data from each other.  Since someC  format standards do not define an explicit end-of-data (EOD), host G  software has often used conventions with filemarks to represent an EODmB  indication.  At least one American National Standard specificallyE  defines filemark use for this purpose.  In some implementations, the F  device's EOD definition may be specified the initiator using the MODE  SELECT command.  iD  A setmark is another type of special recorded element containing noF  user data, providing a segmentation scheme hierarchically superior toG  filemarks. This level of segmentation is useful for some high capacityoF  storage devices to provide concise addressing and fast positioning toH  specific sets of data within a partition.  In some implementations, theG  detection and reporting of setmarks may be controlled by the initiator   using the MODE SELECT command.i  dH  Inter-block gaps, the gaps between blocks, filemarks, and setmarks, areH  introduced on the medium at the time a block or mark is written withoutC  explicit action by the initiator.  Minimum and maximum lengths foreF  inter-block gaps are defined in some American National Standards.  InD  some devices, the length of inter-block gaps may be selected by theH  initiator using the MODE SELECT command while in other devices the gaps   are fixed and non-changeable.  B  In addition to blocks, filemarks, and setmarks, erase gaps may beC  recorded on the medium through use of the ERASE command or device-nG  initiated error recovery actions.  Although explicitly recorded on theiF  medium, there is normally no distinction between two contiguous eraseC  gaps.  An erase gap may be a length of erased medium or a recordedtE  pattern not distinguishable as a block or mark.  Minimum and maximumrG  lengths for erase gaps are defined in some American National StandardshA  while some devices may have no implementation of an erase gap.  d   @  After writing data from BOP x, the medium is considered to be aG  contiguous grouping of blocks, filemarks, setmarks, and gaps.  CertainiG  American National Standards define gap lengths which, if exceeded, arepC  to be considered as having reached blank medium.  Depending on the G  format, this blank medium may be treated as an end-of-data indication,eD  an error recovery area, or an unrecoverable medium error causing anC  interchange error.  Unrecorded volumes (new or erased) may exhibit.H  blank medium characteristics if an attempt is made to read or space the'  volume before data has been written.  a  eA  A sequential-access device may be capable of supporting fixed or C  variable length blocks.  The concept of fixed or variable mode foroB  writing and reading blocks only indicates the method by which theE  initiator specifies the size of a logical block for transfer and notrC  the method of recording physical blocks on the medium.  However, atC  device that supports only fixed-length physical blocks may only betH  capable of supporting logical blocks of the same length.  The length ofH  a logical block is always described in bytes.  The length of a physicalF  block may or may not be recorded as an exact byte count, depending on  the format.  d  10.1.5 Data buffering   H  A device may contain a temporary storage area capable of holding one orG  more logical blocks - a data buffer.  A device data buffer may includeeE  any combination of blocks, filemarks, and setmarks in the process ofcF  being written to the medium, or it may contain read-ahead data blocks  transferred from the medium.r  nD  A device with a data buffer may be capable of operating in either aC  buffered mode or an unbuffered mode.  A device with no data bufferyE  operates only in unbuffered mode.  Either term is only applicable to H  the manner in which the device manages information to be written to the>  medium. Buffered mode is not applicable during read commands,>  regardless of whether read data passes through a data buffer.   E  A device operating in buffered mode may return GOOD status for write F  operations when all write data has been successfully transferred fromE  the initiator into the device data buffer.  For devices operating inrG  unbuffered mode, GOOD status is not returned until all requested data,u@  filemarks, or setmarks are successfully recorded on the medium.  sG  When issuing a buffered WRITE FILEMARKS command with the immediate bite>  set to one, GOOD status is returned as soon as the command isD  validated.  A WRITE FILEMARKS command with the immediate bit set toG  zero causes any buffered blocks, filemarks, and setmarks to be written,E  to the medium.  Upon successful completion of this process, which ishB  called a synchronize operation, no blocks, filemarks, or setmarksH  remain in the data buffer which have not been written to the medium.  AD  synchronize operation has no effect on a data buffer which containsG  only read-ahead data or write data which has already been successfullyn  written to the medium.   eF  Should an unrecoverable write error occur while in buffered mode, theG  device generates an error condition to the current active command.  If G  no command is active, the error may be reported on the next applicablet8  operation as a deferred error (see 8.2.14.2).  For someH  implementations, asynchronous event notification or extended contingentG  allegiance may be required.  Refer to 10.5.5 and 10.7 for descriptionssF  of asynchronous event notification and extended contingent allegiance
  protocol.   B  The READ POSITION command may be used to determine the number andF  storage space of buffered blocks not written before the unrecoverable  error was encountered.   sH  A device with read-ahead data blocks in the data buffer does not reportH  an unrecovered read error until the data block in error is requested by  an initiator.  i7  10.1.6 Recorded object descriptors (block identifiers)   k>  Some recording formats specify that recorded objects (blocks,C  filemarks, and setmarks) have identifiers included in the recorded E  information to help determine write sequence and also to help detecteF  device positioning errors.  The identifier values are unique within a-  partition and may be unique within a volume.f  rH  The use of the term block identifier may imply some arithmetic sequenceE  applied to the assignment of recorded objects.  The block identifier F  assignment algorithm may be defined in an applicable format standard.  oD  For some pre-formatted volumes, the identifiers are associated withE  physical blocks.  In variable-length implementations, the identifier)G  can be associated with a physical block when the logical block and thee?  physical block have a one-to-one relationship on the medium.     tC  Some formats may carry both physical and logical block identifiers F  recorded on the medium.  When a logical block is split over more thanH  one physical block, or multiple logical blocks are concatenated to formF  a physical block, the logical block identifier and the physical blockD  identifier are not the same.  Filemarks and setmarks may or may notF  have recorded identifiers, but if identifiers are used in the format,@  then each mark is assigned a value even if it is not explicitly
  recorded.  sC  The READ POSITION and LOCATE commands use four-byte fields to holdaD  these format dependent identifiers.  For some implementations, thisA  value may correspond to a real physical location; however, it is4H  sufficient for the device to map the identifier to a value representingE  the unique recorded object.  With this capability, the READ POSITIONfH  command may be used to report a device-defined block identifier and theF  initiator may use this value with a LOCATE command to position to theD  same location at some future time (provided the volume has not been  rewritten in the interim).  r  e*  10.1.7 Direction and position definitions   B  For sequential-access devices, positioning has the connotation ofE  logically being in, at, before, or after some defined place within ao@  volume.  This definition means the position is capable of beingE  repeated under the same circumstances.  The orientation of usage forfH  the four words (in, at, before, or after) is in one direction, from BOPC  x toward EOP x.  All positioning defined below is worded from thissH  perspective.  Devices without buffers have some physical position whichG  relates to these logical positions.  However, these definitions do nottA  require the medium to have a physical position equivalent to thee+  logical position unless explicitly stated.    E  The forward direction is defined as logically progressing from BOP x H  toward EOP x. The reverse direction is defined as logically progressingH  from EOP x toward BOP x.  In serpentine devices, the logical forward orB  reverse direction has an alternating relationship to the physical  motion of the medium.    aH  The concept of being in some position means not being outside a definedG  region.  The definition allows the position to be on the boundary of aaF  defined region.  When a volume is first mounted, the logical positionB  is always at the beginning of the default data partition (BOP0). C  Whenever a volume is mounted and the medium motion is stopped, theaG  position is in some partition.  While moving between partitions, theree  is no stable position.  a  tF  The concept of being at some position indicates being positioned to aC  logical or physical extremity of a partition.  A sequential-accesseF  device may be positioned at beginning-of-medium, at BOP x, at end-of-H  data (EOD), at EOP x, or at end-of-medium (EOM), since these are stable)  positions at extremities of a partition.h  hG  The concept of being before some position indicates that there is someaF  element (data block, filemark, setmark, or other defined point) whichH  may be encountered when moving toward EOP x, if the proper commands areG  issued.  Being positioned before a particular data block means that iflH  the device receives a valid READ command, the data block is transferredD  to the initiator.  This position may also be before EW x and EOP x,G  since these are defined points within any partition.  However, if datafF  has not been written to the end-of-partition, these points may not be  accessible by the initiator.   sF  The concept of being after some position indicates that there is someG  element (data block, filemark, setmark, or other defined point) on thenC  BOP x side of the current position which may be encountered if thevC  proper commands are issued.  When a READ command for a single dataSH  block has been successfully executed, the logical position is after the  transferred data block.  r  10.1.8 Error reportingh   C  If any of the following conditions occur during the execution of a =  command the target shall return CHECK CONDITION status.  ThecD  appropriate sense key and additional sense code should be set.  TheD  following list illustrates some error conditions and the applicableH  sense keys.  The list does not provide an exhaustive enumeration of all6  conditions that may cause the CHECK CONDITION status.  ef  Condition                                                                                   Sense Keyr  Invalid logical block address                                                                             ILLEGAL  REQUEST  do  Unsupported option requested                                                                           ILLEGALm  REQUEST   |  Target reset or medium change since last command from this initiator                                                            UNIT ATTENTION   s  Self diagnostic failed                                                                                    HARDWAREi  ERROR  tn  Unrecovered read error                                                                                 MEDIUM  ERRORd                                                                                       HARDWARE ERROR  pt  Recovered read or write error                                                                             RECOVERED  ERROR  r{  Overrun or other error that might be resolved by repeating the command                                                    e  ABORTED command  iF  Attempt a WRITE, READ, READ REVERSE, VERIFY, or RECOVER BUFFERED DATA  command{  with the fixed bit set to zero and variable block mode is not supported                                                      ILLEGAL REQUEST  oF  Attempt a WRITE, READ, READ REVERSE, VERIFY, or RECOVER BUFFERED DATAC  command with a fixed bit of zero and requested block length is notc$  supported           ILLEGAL REQUEST  tF  Attempt a WRITE, READ, READ REVERSE, VERIFY, or RECOVER BUFFERED DATA{  command with a fixed bit of one and MODE SENSE block length set to zero                                                   a  ILLEGAL REQUEST  yH  Attempt to execute an erase or write-type operation on write protected f  medium                                                                                   DATA PROTECT  vn  Deferred write error                                                                                   MEDIUM  ERRORe                                                                                       VOLUME OVERFLOWy   E  In the case of an unrecovered read or write error, if the read-write B  error recovery page (10.3.3.4) is implemented, the current valuesA  specify the target error recovery criteria.  If this page is not 4  implemented, the error recovery is vendor-specific.  iG  In the case of an unrecovered read error, if the fixed bit is one, thetH  valid bit shall be set to one and the information field shall be set toE  the requested transfer length minus the actual number of blocks readiF  (not including the unrecovered block).  If the fixed bit is zero, theH  valid bit shall be set to one and the information field shall be set toG  the requested transfer length.  Upon termination, the logical positiont&  shall be after the unrecovered block.  pA  In the case of an unrecovered write error, if unbuffered mode issH  selected and the fixed bit is set to one, the valid bit shall be set toE  one and the information field shall be set to the requested transfersF  length minus the actual number of blocks written.  If unbuffered modeD  is selected and the fixed bit is set to zero, the information field/  shall be set to the requested transfer length.s  aH  In the case of an unrecovered write error or a deferred write error, ifH  buffered mode is selected and the fixed bit is one, the valid bit shallB  be set to one and the information field shall be set to the totalE  number of blocks, filemarks, and setmarks not written (the number ofcE  blocks not transferred from the initiator plus the number of blocks,sH  filemarks, and setmarks remaining in the target's buffer).  If bufferedH  mode is selected and the fixed bit is zero, the information field shallA  be set to the total number of bytes, filemarks, and setmarks not E  written (the number of bytes not transferred from the initiator plusdG  the number of bytes, filemarks, and setmarks remaining in the target'sSG  buffer).  In both cases, the value in the information field may exceedv  the transfer length.c  iH  In the case of an unrecovered write error or a deferred write error, ifG  buffered mode 1h is selected, the error shall be reported to the first(E  initiator issuing a command (other than INQUIRY or REQUEST SENSE) ortG  the first initiator responding to asynchronous event notification.  If A  buffered mode 2h is selected, the error shall be reported to the -  initiator with unwritten data in the buffer.   e8  10.2 Command descriptions for sequential-access devices  dF  The commands for sequential-access devices shall be as shown in table  174.r  sA                Table 174 - Commands for sequential-access devicestI  +=====================================-============-======-============+nI  |  Command name                       | Operation  | Type |  Subclause |tI  |                                     |   code     |      |            | I  |-------------------------------------+------------+------+------------|eI  | CHANGE DEFINITION                   |    40h     |   O  |   8.2.1    |dI  | COMPARE                             |    39h     |   O  |   8.2.2    |nI  | COPY                                |    18h     |   O  |   8.2.3    |mI  | COPY AND VERIFY                     |    3Ah     |   O  |   8.2.4    |nI  | ERASE                               |    19h     |   M  |  10.2.1    | I  | INQUIRY                             |    12h     |   M  |   8.2.5    |oI  | LOAD UNLOAD                         |    1Bh     |   O  |  10.2.2    |lI  | LOCATE                              |    2Bh     |   O  |  10.2.3    |bI  | LOG SELECT                          |    4Ch     |   O  |   8.2.6    |aI  | LOG SENSE                           |    4Dh     |   O  |   8.2.7    |oI  | MODE SELECT(6)                      |    15h     |   M  |   8.2.8    | I  | MODE SELECT(10)                     |    55h     |   O  |   8.2.9    |oI  | MODE SENSE(6)                       |    1Ah     |   M  |   8.2.10   | I  | MODE SENSE(10)                      |    5Ah     |   O  |   8.2.11   |rI  | PREVENT ALLOW MEDIUM REMOVAL        |    1Eh     |   O  |   9.2.4    |rI  | READ                                |    08h     |   M  |  10.2.4    |cI  | READ BLOCK LIMITS                   |    05h     |   M  |  10.2.5    |hI  | READ BUFFER                         |    3Ch     |   O  |   8.2.12   | I  | READ POSITION                       |    34h     |   O  |  10.2.6    |iI  | READ REVERSE                        |    0Fh     |   O  |  10.2.7    |uI  | RECEIVE DIAGNOSTIC RESULTS          |    1Ch     |   O  |   8.2.13   |bI  | RECOVER BUFFERED DATA               |    14h     |   O  |  10.2.8    |uI  | RELEASE UNIT                        |    17h     |   M  |  10.2.9    |oI  | REQUEST SENSE                       |    03h     |   M  |   8.2.14   |)I  | RESERVE UNIT                        |    16h     |   M  |  10.2.10   |cI  | REWIND                              |    01h     |   M  |  10.2.11   |bI  | SEND DIAGNOSTIC                     |    1Dh     |   M  |   8.2.15   |nI  | SPACE                               |    11h     |   M  |  10.2.12   | I  | TEST UNIT READY                     |    00h     |   M  |   8.2.16   |iI  | VERIFY                              |    13h     |   O  |  10.2.13   |oI  | WRITE                               |    0Ah     |   M  |  10.2.14   |yI  | WRITE BUFFER                        |    3Bh     |   O  |   8.2.17   |dI  | WRITE FILEMARKS                     |    10h     |   M  |  10.2.15   |eI  |----------------------------------------------------------------------|dI  |Key:  M = command implementation is mandatory.                        |eI  |      O = command implementation is optional.                         |BI  +======================================================================+s     eE  The following command codes are vendor-specific: 02h, 06h, 07h, 09h,eE  0Ch, and 0Eh.  All other command codes for sequential-access devicesr)  are reserved for future standardization.t  e  10.2.1 ERASE command   fF  The ERASE command (see table 175) causes part or all of the medium toE  be erased beginning at the current position on the logical unit.  AseG  used here, erased means either the medium shall be erased or a patternsD  shall be written on the medium that appears as a gap to the target.  l4                            Table 175 - ERASE commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (19h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   |   Logical unit number    |         Reserved          | Immed |  Long  |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+  .   E  An immediate (Immed) bit of zero indicates that the target shall nottH  return status until the erase operation has completed.  An Immed bit ofA  one indicates that the target shall return status as soon as theeF  command has been validated. If CHECK CONDITION status is returned forE  an ERASE command with an Immed bit of one, the erase operation shallt  not be performed. n  hE  A long bit of one indicates that all remaining medium in the current F  partition shall be erased beginning at the current logical position. G  If the Immed bit is one, the target shall return status as soon as all F  buffered commands have completed execution and the command descriptorE  block of the ERASE command has been validated.  The logical position F  following an ERASE command with a long bit of one is not specified by  this standard.o  nN     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.    H  A long bit of zero specifies an erase gap defined by the gap size fieldF  in the device configuration page (10.3.3.1).  If the gap size is zeroD  or the field is not supported, a device defined erase gap operationF  shall be performed.  If the Immed bit is one, the target shall returnD  status as soon as the command descriptor block has been validated. H  Erase gaps may be used in initiator controlled error recovery or update  in place applications.   oF  If the logical unit encounters early-warning during an ERASE command,H  and any buffered data, filemarks, or setmarks remain to be written, theE  target action shall be as defined for the early-warning condition of A  the WRITE command (10.2.14).  If the long bit is zero, the erase G  operation shall terminate with CHECK CONDITION status and return sensetD  data as defined for the WRITE command.  Any buffered erases are not+  reported as part of the information field.   c  10.2.2 LOAD UNLOAD command    H  The LOAD UNLOAD command (see table 176) requests that the target enableF  or disable the logical unit for further operations.  This command mayG  also be used to request a retension function.  Prior to performing the D  load or unload operation, the target shall ensure that all bufferedC  data, filemarks, and setmarks have been transferred to the medium.    7                         Table 176 - LOAD UNLOAD commandTP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (1Bh)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   |   Logical unit number    |              Reserved             | Immed  |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved         |   EOT  |  Reten |  Load  |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+  ,  eE  An immediate (Immed) bit of zero indicates that the target shall notaD  return status until the load or unload operation has completed.  AnG  Immed bit of one indicates that the target shall return status as soonsB  as all buffered commands have completed execution and the commandD  descriptor block of the LOAD UNLOAD command has been validated.  IfE  CHECK CONDITION status is returned for a LOAD UNLOAD command with anlG  Immed bit of one, the load or unload operation shall not be performed.u  rM     NOTE 139 For compatibility with devices implemented prior to this versionbH     of the standard, a WRITE FILEMARKS command with an Immed bit of zeroK     should be used to ensure that all buffered data, filemarks, or setmarksfN     have been transferred to the medium prior to issuing a LOAD UNLOAD command     with an Immed bit of one.i  fC  An end-of-tape (EOT) bit of one indicates that an unload operationcF  (load bit set to zero) shall position the medium at end-of-medium forF  removal from the device.  An EOT bit of zero indicates that an unloadG  operation shall position the medium at beginning-of-medium for removalr  from the device.r  uB  An EOT bit of one and a load bit of one shall cause the target toH  return CHECK CONDITION status and the sense key shall be set to ILLEGAL  REQUEST in the sense data.o  fH  A retension (ReTen) bit of one indicates that the medium on the logicalD  unit shall have the correct tension applied.  Implementation of the'  retension function is device specific.   =G  If the load bit is set to one, the medium in the logical unit shall be|G  loaded and positioned to the beginning-of-partition zero.  If the load D  bit is zero, the medium in the logical unit shall be positioned forF  removal at the extreme position along the medium specified by the EOTB  bit.  Following successful completion of an unload operation, theE  target shall return CHECK CONDITION status with the sense key set to G  NOT READY for all subsequent medium-access commands until a new volume :  is mounted or a load operation is successfully completed.  |H  When operating in buffered mode 1h or 2h (see 10.3.3), the target shallE  discard any unwritten buffered data after the LOAD UNLOAD command is F  validated if the previous command was terminated with CHECK CONDITIONC  status and the device is unable to continue successfully writing.       10.2.3 LOCATE command   A  LOCATE command (see table 177) causes the target to position the G  logical unit to the specified block address in a specified partition. DD  Upon completion, the logical position shall be before the specifiedF  location.  Prior to performing the locate operation, the target shallA  ensure that all buffered data, filemarks, and setmarks have been   transferred to the medium.    5                            Table 177 - LOCATE command P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (2Bh)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   |    Logical unit number   |      Reserved   |   BT   |   CP   | Immed  |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 4   |                                                                       |P  |-----+---                        Block address                            ---|P  | 5   |                                                                       |P  |-----+---                                                                 ---|P  | 6   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 7   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 8   |                           Partition                                   |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+  i  tF  A block address type (BT) bit of one indicates the value in the blockE  address field shall be interpreted as a device-specific value.  A BToD  bit of zero indicates the value in the block address field shall be.  interpreted as an SCSI logical block address.  tB  A change partition (CP) bit of one indicates that a change to the@  partition specified in the partition field is to occur prior toE  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.   E  An immediate (Immed) bit of zero indicates that the target shall not=F  return status until the locate operation has completed.  An Immed bitD  of one indicates that the target shall return status as soon as allF  buffered commands have completed execution and the command descriptorD  block of the LOCATE command has been validated.  If CHECK CONDITIONF  status is returned for a LOCATE command with an Immed bit of one, the)  locate operation shall not be performed.    D  The block address field (see 10.1.6) specifies the block address toH  which the target shall position the medium based on the current setting  of the BT bit.    F  The partition field specifies which partition to select if the CP bitF  is one.  Refer to the sequential-access device model (see 10.1.3) andF  the medium partition pages (see 10.3.3.2 and 10.3.3.3) for additional   information about partitioning.  -  10.2.4 READ command  -G  The READ command (see table 178) requests that the target transfer one H  or more block(s) of data to the initiator beginning with the next block  on the logical unit.=  =4                             Table 178 - READ commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (08h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   |   Logical unit number     |        Reserved         |  SILI  | Fixed  |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                           Transfer length                             |P  |-----+---                                                                 ---|P  | 4   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+     aG  The fixed bit specifies whether fixed-length or variable-length blocks D  are to be transferred.  Refer to the READ BLOCK LIMITS command (seeH  10.2.5) for additional information about fixed and variable block mode.  mE  If the fixed bit is one, the transfer length specifies the number ofyF  fixed-length blocks to be transferred, using the current block lengthF  reported in the mode parameters block descriptor (see 8.3.3).  If theA  fixed bit is zero, a variable-length block is requested with thebE  transfer length specifying the maximum number of bytes allocated forc  the returned data.   mE  A successful READ command with a fixed bit of one shall transfer therE  requested transfer length times the current block length in bytes tocC  the initiator.  A successful READ command with a fixed bit of zeropI  shall transfer the requested transfer length in bytes to the initiator.  D  Upon completion, the logical position shall be after the last block%  transferred (end-of-partition side).a   E  If the suppress incorrect length indicator (SILI) bit is one and the-%  fixed bit is zero, the target shall:|J     a)     report CHECK CONDITION status for an incorrect length conditionK            only if the overlength condition exists (see 10.4) and the block I            length field in the mode parameter block descriptor is nonzero=            (see 8.3.3). E     b)     not report CHECK CONDITION status if the only error is the|H            underlength condition (see 10.4), or if the only error is theF            overlength condition and the block length field of the mode/            parameters block descriptor is zero.-  -C     NOTE 140 Since the residue information normally provided in the N     information field of the sense data may not be available when the SILI bitK     is set, other methods for determining the actual block length should be ?     used (e.g. including length information in the data block).-  +B  If the SILI bit is one and the fixed bit is one, the target shallD  terminate the command with CHECK CONDITION status and the sense keyA  shall be set to ILLEGAL REQUEST with an additional sense code of-  INVALID FIELD IN CDB.  -E  If the SILI bit is zero and an incorrect length block is read, CHECK G  CONDITION status shall be returned and the ILI and valid bits shall be=F  set to one in the sense data.  Upon termination, the logical positionG  shall be after the incorrect length block (end-of-partition side).  Ifr@  the fixed bit is one, the information field shall be set to theF  requested transfer length minus the actual number of blocks read (notF  including the incorrect length block).  If the fixed bit is zero, theF  information field shall be set to the requested transfer length minusF  the actual block length.  Targets that do not support negative valuesE  shall set the information field to zero if the overlength  conditione  exists (see 10.4).o  oN     NOTE 141 In the above case with the fixed bit of one, only the position ofN     the incorrect-length logical block can be determined from the sense data. N     The actual length of the incorrect block is not reported.  Other means mayM     be used to determine its actual length (e.g. read it again with the fixedd     bit set to zero).p  tH  A transfer length of zero indicates that no data shall be transferred. @  This condition shall not be considered an error and the logical  position shall not be changed.o  hG  If the logical unit encounters a filemark during a READ command, CHECK C  CONDITION status shall be returned and the filemark and valid bitsrF  shall be set to one in the sense data.  The sense key shall be set toD  NO SENSE or RECOVERED ERROR, as appropriate.  Upon termination, theG  logical position shall be after the filemark (end-of-partition side). pC  If the fixed bit is one, the information field shall be set to the F  requested transfer length minus the actual number of blocks read (notD  including the filemark).  If the fixed bit is zero, the information6  field shall be set to the requested transfer length.   aG  If the logical unit encounters a setmark during a READ command and thepH  RSmk bit is set to one in the device configuration page (see 10.3.3.1),D  CHECK CONDITION status shall be returned and the filemark and validH  bits shall be set to one in the sense data.  The sense key shall be setC  to NO SENSE or RECOVERED ERROR, as appropriate, and the additionaleD  sense code shall be set to SETMARK DETECTED.  Upon termination, theF  logical position shall be after the setmark (end-of-partition side). C  If the fixed bit is one, the information field shall be set to theCF  requested transfer length minus the actual number of blocks read (notC  including the setmark).  If the fixed bit is zero, the informationbG  field shall be set to the requested transfer length.  The target shalldE  not return CHECK CONDITION when a setmark is encountered if the RSmka7  bit is set to zero or if this option is not supported.o  oG  If the logical unit encounters early-warning during a READ command ande@  the REW bit is set to one in the device configuration page (seeG  10.3.3.1), CHECK CONDITION status shall be returned upon completion of=H  the current block.  The sense key shall be set to NO SENSE or RECOVEREDF  ERROR, as appropriate.  The EOM and valid bits shall be set to one inG  the sense data.  Upon termination, the logical position shall be after F  the last block transferred (end-of-partition side).  If the fixed bitE  is one, the information field shall be set to the requested transferaD  length minus the actual number of blocks read.  If the fixed bit isC  zero, the information field shall be set to the requested transferiC  length minus the actual block length.  The target shall not return-H  CHECK CONDITION status when early-warning is encountered if the REW bit/  is zero or if the REW option is not supported.    M     NOTE 142 A REW bit of one is not recommended for most system applications-8     since read data may be present after early-warning.    H  If the logical unit encounters end-of-data during a READ command, CHECKH  CONDITION status shall be returned, the sense key shall be set to BLANKD  CHECK, and the valid bit shall be set to one in the sense data.  IfH  end-of-data is encountered at or after early-warning, the EOM bit shallD  also be set to one. Upon termination, the logical position shall beG  after the last recorded logical block (end-of-partition side).  If the F  fixed bit is one, the information field shall be set to the requestedF  transfer length minus the actual number of blocks read.  If the fixedA  bit is zero, the information field shall be set to the requested   transfer length.r   G  If the logical unit encounters end-of-partition during a READ command,-H  CHECK CONDITION status shall be returned, the sense key shall be set toD  MEDIUM ERROR, and the EOM and valid bits shall be set to one in the@  sense data. The medium position following this condition is notF  defined.  If the fixed bit is one, the information field shall be setC  to the requested transfer length minus the actual number of blocks=F  read. If the fixed bit is zero, the information field shall be set to  the requested transfer length.d  s!  10.2.5 READ BLOCK LIMITS commandv  -H  The READ BLOCK LIMITS command (see table 179) requests that the logicalC  unit's block length limits capability be returned.  The READ BLOCKt2  LIMITS data shown in table 180 shall be returned.  c:                      Table 179 - READ BLOCK LIMITS commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (05h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   |   Logical unit number    |                  Reserved                  |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+      9                        Table 180 - READ BLOCK LIMITS data=P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 1   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 2   |                           Maximum block length limit                  |P  |-----+---                                                                 ---|P  | 3   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 4   | (MSB)                                                                 |P  |-----+---                        Minimum block length limit               ---|P  | 5   |                                                                 (LSB) |P  +=============================================================================+  w  hH  If the maximum block length limit value equals the minimum block lengthC  limit value, the logical unit supports the transfer of data in themH  fixed-block mode only, with the block length equal to the given value. E  In this case the fixed bit shall be set to one in the WRITE and READe
  commands.  sD  If the maximum block length limit value is not equal to the minimumD  block length limit value, the logical unit supports the transfer ofC  data in either fixed-block or variable-block modes, with the block A  length constrained between the given limits in either mode.  ThesB  transfer mode is controlled by the fixed bit in the WRITE or READG  commands. If the maximum block limit is zero a maximum block length isi  not specified.s     10.2.6 READ POSITION commandf  rG  The READ POSITION command (see table 181) reports the current positionoB  of the logical unit and any data blocks in the buffer.  No medium3  movement shall occur as a result of the command.  I  h8                        Table 181 - READ POSITION commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (34h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   |   Logical unit number    |             Reserved              |   BT   |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 8   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+  c  bG  A block address type (BT) bit of one requests the target to return itstB  current first block location and last block location as a device-D  specific value.  A BT bit of zero requests the target to return theD  first block location and the last block location as an SCSI logical+  block address (relative to a partition).  c  iE  If the logical unit is not capable of reporting block locations, theID  BPU bit shall be set to one in the returned data.  Support for thisE  option of the READ POSITION command is indicated by a BIS bit set to 5  one in the device configuration page (see 10.3.3.1).s  l=  The READ POSITION data shown in table 182 shall be returned.   m:                      Table 182 - READ POSITION data formatP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+========+========+==========================+========+=================|P  | 0   |  BOP   |   EOP  |        Reserved          |  BPU   |     Reserved    |P  |-----+-----------------------------------------------------------------------|P  | 1   |                          Partition number                             |P  |-----+-----------------------------------------------------------------------|P  | 2   |                          Reserved                                     |P  |-----+-----------------------------------------------------------------------|P  | 3   |                          Reserved                                     |P  |-----+-----------------------------------------------------------------------|P  | 4   | (MSB)                                                                 |P  |- - -+---                       First block location                      ---|P  | 7   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 8   | (MSB)                                                                 |P  |- - -+---                       Last block location                       ---|P  | 11  |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 12  |                          Reserved                                     |P  |-----+-----------------------------------------------------------------------|P  | 13  | (MSB)                                                                 |P  |- - -+---                       Number of blocks in buffer                ---|P  | 15  |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 16  | (MSB)                                                                 |P  |- - -+---                       Number of bytes in buffer                 ---|P  | 19  |                                                                 (LSB) |P  +=============================================================================+  e  tE  A beginning of partition (BOP) bit of one indicates that the logical G  unit is at the beginning-of-partition in the current partition.  A BOPtF  bit of zero indicates that the current logical position is not at the  beginning-of-partition.     H  An end of partition (EOP) bit of one indicates that the logical unit isE  positioned between early-warning and end-of-partition in the currentbB  partition.  An EOP bit of zero indicates that the current logical<  position is not between early-warning and end-of-partition.  iJ     NOTE 143 The BOP and EOP indications are not necessarily a result of a3     physical tape marker (e.g. reflective marker). M  dG  A block position unknown (BPU) bit of one indicates that the first andfH  last block locations are not known or cannot be obtained.  A BPU bit ofE  zero indicates that the first and last block location fields containh  valid position information.  .H  The partition number field reports the partition number for the currentG  logical position.  If the logical unit only supports one partition fore-  the medium, this field shall be set to zero.e   F  The first block location field indicates the block address associatedG  with the current logical position.  The value shall indicate the block G  address of the next data block to be transferred between the initiator=5  and the target if a READ or WRITE command is issued.=  =G  The last block location field indicates the block address (see 10.1.6) H  associated with the next block to be transferred from the buffer to theE  medium.  The value shall indicate the block address of the next data=C  block to be transferred between the buffer and the medium.  If theeE  buffer does not contain a whole block of data or is empty, the value-A  reported for the last block location shall be equal to the valueg'  reported for the first block location.s  eJ     NOTE 144 The information provided by the first and last block locationM     fields can be used in conjunction with the LOCATE command to position the L     medium at the appropriate logical block on another device in the case of-     unrecoverable errors on the first device.    B  The number of blocks in buffer field indicates the number of dataH  blocks in the target's buffer that have not been written to the medium.   G  The number of bytes in buffer field indicates the total number of data G  bytes in the target's buffer that have not been written to the medium.-  -  10.2.7 READ REVERSE command   B  The READ REVERSE command (see table 183) requests that the targetH  transfer one or more block(s) of data to the initiator beginning at the&  current position on the logical unit.  R8                         Table 183 - READ REVERSE commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (0Fh)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   |   Logical unit number    |         Reserved         |  SILI  | Fixed  |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                           Transfer length                             |P  |-----+---                                                                 ---|P  | 4   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+  l  tD  The execution of this command is similar to the READ command exceptG  that medium motion is in the reverse direction.  All block(s), and thebH  byte(s) within the block(s), are transferred in the reverse order.  TheF  order of bits within each byte shall not be changed.  Upon completionD  of a READ REVERSE command, the logical position shall be before the6  last block transferred (beginning-of-partition side).  nF  Refer to the READ command (see 10.2.4) for a description of the fixedG  bit, the SILI bit, the transfer length field, and any associated errori  conditions.  hC  Filemarks, setmarks, incorrect length blocks, and unrecovered readiE  errors are handled the same as in the READ command, except that uponDH  termination the logical position shall be before the filemark, setmark,E  incorrect length block, or unrecovered block (beginning-of-partition   side).N  eD  If the logical unit encounters beginning-of-partition during a READF  REVERSE command, CHECK CONDITION status shall be returned and the EOME  and valid bits shall be set to one in the sense data.  The sense key E  shall be set to NO SENSE or RECOVERED ERROR, as appropriate.  If the F  fixed bit is one, the information field shall be set to the requestedG  transfer length minus the actual number of blocks transferred.  If the=G  fixed bit is zero, the information field shall be set to the requested   transfer length.   |%  10.2.8 RECOVER BUFFERED DATA command-  -E  The RECOVER BUFFERED DATA command (see table 184) is used to recover G  data that has been transferred to the target's buffer but has not been-D  successfully written to the medium.  It is normally used to recoverH  from error or exception conditions that make it impossible to write theH  buffered data to the medium. One or more RECOVER BUFFERED DATA commands8  may be required to recover all unwritten buffered data.   <                    Table 184 - RECOVER BUFFERED DATA commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (14h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   |   Logical unit number    |         Reserved         |  SILI  | Fixed  |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                           Transfer length                             |P  |-----+---                                                                 ---|P  | 4   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+  l  bD  The execution of this command is similar to the READ command exceptE  that the data is transferred from the target's buffer instead of the G  medium.  The order in which block(s) are transferred is defined by theIE  RBO bit in the device configuration page (see 10.3.3.1).  If the RBOuH  bit is not implemented, block(s) are transferred in the same order they+  would have been transferred to the medium.   TF  Refer to the READ command (see 10.2.4) for a description of the fixedG  bit, the SILI bit, the transfer length field, and any associated error|  conditions.  |E  If the fixed bit is zero, no more than the requested transfer length B  shall be transferred to the initiator.  If the requested transferD  length is smaller than the actual length of the logical block to beF  recovered, only the requested transfer length shall be transferred toC  the initiator and the remaining data for the current logical block-  shall be discarded.   J     NOTE 145 During recovery operations involving unknown block sizes, theL     initiator should select the maximum block length supported by the targetN     to ensure that all buffered data will be transferred and set the fixed bit     to zero.  -E  If a buffered filemark is encountered during a RECOVER BUFFERED DATA|G  command, CHECK CONDITION status shall be returned, the sense key shall H  be set to NO SENSE, and the filemark and valid bits shall be set to oneD  in the sense data.  Upon termination, the logical position shall beD  after the filemark.  If the fixed bit is one, the information fieldF  shall be set to the requested transfer length minus the actual number6  of blocks transferred (not including the filemark).    -D  If the fixed bit is zero, the information field shall be set to the  requested transfer length.   D  If a buffered setmark is encountered during a RECOVER BUFFERED DATAH  command and the RSmk bit is set to one in the device configuration pageA  (see 10.3.3.1), CHECK CONDITION status shall be returned and the-D  filemark and valid bits shall be set to one in the sense data.  TheG  sense key shall be set to NO SENSE and the additional sense code shall D  be set to SETMARK DETECTED.  Upon termination, the logical positionF  shall be after the setmark.  If the fixed bit is one, the informationE  field shall be set to the requested transfer length minus the actual H  number of blocks transferred (not including the setmark).  If the fixedA  bit is zero, the information field shall be set to the requested-D  transfer length. The target shall not return CHECK CONDITION when aH  setmark is encountered if the RSmk bit is zero or if this option is not  supported.   -F  If an attempt is made to recover more logical blocks of data than areB  contained in the target's buffer, CHECK CONDITION status shall beH  returned, the sense key shall be set to NO SENSE, and the EOM and validF  bits shall be set to one in the sense data.  If the fixed bit is one,D  the information field shall be set to the requested transfer lengthD  minus the actual number of blocks transferred.  If the fixed bit isC  zero, the information field shall be set to the requested transferA  length.  i  10.2.9 RELEASE UNIT command  hG  The RELEASE UNIT command (see table 185) is used to release previouslyiC  reserved logical units for the requesting initiator, or if it is at7  third-party release, to another specified SCSI device.g  d8                         Table 185 - RELEASE UNIT commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (17h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      | 3rdPty | Third party device ID    |Reserved|P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+  O  1G  The RESERVE UNIT and RELEASE UNIT commands provide the basic mechanisml9  for contention resolution in multiple-initiator systems.s  oD  If a valid reservation exists for the I_T_L nexus, the target shall0  release the reservation and return GOOD status.   F  A reservation may only be released by the initiator that made it.  It@  is not an error to attempt to release a reservation that is notD  currently valid or is held by another initiator.  In this case, theH  target shall return GOOD status without altering any other reservation.  i  10.2.9.1 Third-party release   EG  Third-party release allows an initiator to release a logical unit thats=  was previously reserved using a third-party reservation (see   10.2.10.1).  nG  If the third party (3rdPty) bit is zero, then a third-party release is E  not requested.  If the 3rdPty bit is one, and if the reservation was=>  made using a third-party reservation by the initiator that isD  requesting the release for the same SCSI device as specified in theF  third-party device ID, then the target shall release the reservation.  |?  If the 3rdPty bit is one, the target shall not modify the mode=E  parameters for commands received from the third-party device even ifhD  the target implements the transfer of mode parameters with a third-  party RESERVE UNIT command.  -L     NOTE 146 When a target implements independent storage of mode parametersM     for each initiator, a third-party RESERVE UNIT command effects a transfer-I     of the current mode parameters.  Those set up by the initiator of the L     RESERVE UNIT are to be set as the mode parameters used for commands fromL     the third-party device (usually a copy master device).  A unit attentionN     condition notifies the third-party device of the changed mode parameters. H     A successful third-party RELEASE UNIT command leaves the transferredL     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    D  The RESERVE UNIT command (see table 186) is used to reserve logicalG  units for the exclusive use of the requesting initiator, or if it is ai;  third-party reservation, to another specified SCSI device.   e8                         Table 186 - RESERVE UNIT commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (16h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      | 3rdPty | Third party device ID    |Reserved|P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+  EG  The RESERVE UNIT and RELEASE UNIT commands provide the basic mechanism 9  for contention resolution in multiple-initiator systems.e  uG  This command requests that the entire logical unit be reserved for therF  exclusive use of the initiator until the reservation is superseded byD  another valid RESERVE UNIT command from the initiator that made theF  reservation or until released by a RELEASE UNIT command from the sameH  initiator that made the reservation, by a BUS DEVICE RESET message fromG  any initiator, by a hard reset condition, or by a power on cycle.  The D  reservation shall not be granted if the logical unit is reserved byH  another initiator.  It shall be permissible for an initiator to reserve=  a logical unit that is currently reserved by that initiator.=  =H  If the logical unit is reserved for another initiator, the target shall&  return RESERVATION CONFLICT status.    -E  If, after honouring the reservation, any other initiator attempts togH  perform any command on the reserved logical unit other than an INQUIRY,C  REQUEST SENSE, PREVENT ALLOW MEDIUM REMOVAL (with a prevent bit of-E  zero), or a RELEASE UNIT command, the command shall be rejected with   RESERVATION CONFLICT status.    "  10.2.10.1 Third-party reservation   F  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.  |   F  If the third-party (3rdPty) bit is zero, a third-party reservation isF  not requested.  If the 3rdPty bit is one the target shall reserve theH  logical unit for the SCSI device specified in the third-party device IDH  field. The target shall preserve the reservation until it is supersededG  by another valid RESERVE UNIT command from the initiator that made theiD  reservation or until it is released by the same initiator, by a BUSE  DEVICE RESET message from any initiator, or a hard reset condition. sG  The target shall ignore any attempt to release the reservation made byn  any other initiator.I  hA  If independent sets of parameters are implemented, a third partymH  reservation shall cause the target to transfer the set of parameters inG  effect for the initiator of the RESERVE command to the parameters usedIB  for commands from the third-party device.  Any subsequent commandC  issued by the third-party device is executed according to the modenF  parameters in effect for the initiator that sent the RESERVE command.  nA  If independent sets of parameters are implemented, a third partykH  reservation shall cause the target to transfer the set of parameters inG  effect for the initiator of the RESERVE command to the parameters used-B  for commands from the third party device.  Any subsequent commandC  issued by the third-party device is executed according to the modeaF  parameters in effect for the initiator that sent the RESERVE command.   I     NOTE 147 This transfer of the mode parameters is applicable to targetfD     devices which store mode information independently for differentN     initiators.  This mechanism allows an initiator to set the mode parametersL     of a target for the use of a copy master (i.e. the third-party device). L     The third-party copy master may subsequently issue a MODE SELECT command"     to modify the mode parameters.  e#  10.2.10.2 Superseding reservationsa  eG  An initiator that currently has a logical unit reserved may modify thehH  current reservation by issuing another RESERVE UNIT command to the sameE  logical unit.  The superseding reservation shall release the currentiD  reservation if the superseding reservation request is granted.  The=  current reservation shall not be modified if the superseding1G  reservation request cannot be granted.  If the superseding reservation C  cannot be granted because of conflicts with a previous reservation C  (other than the current reservation), then the target shall returnA  RESERVATION CONFLICT status.  h  oM     NOTE 148 Superseding reservations allow the third-party SCSI device ID torN     be changed during a reservation using the third-party reservation option. K     This capability is necessary for certain situations when using COMPARE,t'     COPY, and COPY AND VERIFY commands.s  t  10.2.11 REWIND commande  eE  The REWIND command (see table 187) causes the target to position thenF  logical unit to the beginning-of-partition in the current partition. G  Prior to performing the rewind operation, the target shall ensure thataH  all buffered data, filemarks, and setmarks have been transferred to the  medium.  s5                            Table 187 - REWIND commanddP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (01h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   |   Logical unit number    |              Reserved             | Immed  |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+      E  An immediate (Immed) bit of zero indicates that the target shall not-F  return status until the rewind operation has completed.  An Immed bitD  of one indicates that the target shall return status as soon as allF  buffered commands have completed execution and the command descriptorD  block of the REWIND command has been validated.  If CHECK CONDITIONF  status is returned for a REWIND command with an Immed bit of one, the)  rewind operation shall not be performed.    E     NOTE 149 For compatibility with devices implemented prior to this=N     standard, it is suggested that a WRITE FILEMARKS command with an Immed bitL     of zero be used to ensure that all buffered data, filemarks, or setmarksL     have been transferred to the medium before issuing a REWIND command with     an Immed bit of one.  tH  When operating in buffered mode 1h or 2h (see 10.3.3), the target shall@  discard any unwritten buffered data after the REWIND command isF  validated if the previous command was terminated with CHECK CONDITIONC  status and the device is unable to continue successfully writing. t  w  10.2.12 SPACE command  eD  The SPACE command (see table 188) provides a variety of positioningG  functions that are determined by the code and count.  Both forward andeA  reverse positioning are provided, although some targets may only ?  support a subset of this command.  If an initiator requests aniA  unsupported function, the command shall be terminated with CHECKoD  CONDITION status and the sense key shall be set to ILLEGAL REQUEST.  r4                            Table 188 - SPACE commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation  (11h)                            |P  |-----+-----------------------------------------------------------------------|P  | 1   |   Logical unit number    |     Reserved    |           Code           |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                           Count                                       |P  |-----+---                                                                 ---|P  | 4   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+  N  c(  The code field is defined in table 189.  =8                        Table 189 - Code field definition7  +=============-========================-=============+ 7  |    Code     |  Description           |  Support    | 7  |-------------+------------------------+-------------|=7  |    000b     |  Blocks                |  Mandatory  | 7  |    001b     |  Filemarks             |  Mandatory  | 7  |    010b     |  Sequential filemarks  |  Optional   |-7  |    011b     |  End-of-data           |  Optional   |L7  |    100b     |  Setmarks              |  Optional   | 7  |    101b     |  Sequential setmarks   |  Optional   |-7  | 110b - 111b |  Reserved              |             | 7  +====================================================+    B  When spacing over blocks, filemarks, or setmarks, the count fieldD  specifies the number of blocks, filemarks, or setmarks to be spacedF  over in the current partition.  A positive value N in the count fieldA  shall cause forward positioning (toward end-of-partition) over N F  blocks, filemarks, or setmarks ending on the end-of-partition side ofG  the last block, filemark, or setmark.  A zero value in the count field G  shall cause no change of logical position.  A negative value -N (two's=H  complement notation) in the count field shall cause reverse positioningF  (toward beginning-of-partition) over N blocks, filemarks, or setmarksG  ending on the beginning-of-partition side of the last block, filemark,TG  or setmark.  Support of spacing in the reverse direction is optional. e  uD  If a filemark is encountered while spacing over blocks, the commandC  shall be terminated.  The logical position shall be on the end-of-sH  partition side of the filemark if movement was in the forward directionG  and on the beginning-of-partition side of the filemark if movement wasiG  in the reverse direction.  CHECK CONDITION status shall be returned torH  the initiator, the sense key shall be set to NO SENSE, and the filemarkG  and valid bits shall be set to one in the sense data.  The informationlE  field shall be set to the requested count minus the actual number ofa1  blocks spaced over (not including the filemark).t  aG  If a setmark is encountered while spacing over blocks or filemarks andrA  the RSmk bit is set to one in the device configuration page (seeoC  10.3.3.1), the command shall be terminated, CHECK CONDITION statusRD  shall be returned to the initiator, and the filemark and valid bitsF  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 SETMARKpE  DETECTED.  The information field shall be set to the requested counto@  minus the actual number of blocks or filemarks spaced over (notF  including the setmark).  The logical position shall be on the end-of-G  partition side of the setmark if movement was in the forward directionPF  and on the beginning-of-partition side of the setmark if movement wasG  in the reverse direction.  The target shall not return CHECK CONDITIONeG  status when a setmark is encountered if the RSmk bit is set to zero orN!  if this option is not supported.m   F  If early-warning is encountered while spacing over blocks, filemarks,F  or setmarks and the REW bit is set to one in the device configurationC  page (see 10.3.3.1), CHECK CONDITION status shall be returned, theaH  sense key shall be set to NO SENSE, and the EOM and valid bits shall beE  set to one in the sense data.  The information field shall be set toaE  the requested count minus the actual number of blocks, filemarks, orEF  setmarks spaced over as defined by the code value.  If the REW bit isH  zero or the option is not supported by the target, the target shall not:  report CHECK CONDITION status at the early-warning point.  oC     NOTE 150 Setting the REW bit is not recommended for most systeme?     applications since data may be present after early-warning.t  eG  If end-of-data is encountered while spacing over blocks, filemarks, orRH  setmarks, CHECK CONDITION status shall be returned, the sense key shallD  be set to BLANK CHECK, and the valid bit shall be set to one in theF  sense data.  Additionally, the EOM bit shall be set to one if end-of-F  data is encountered at or after early-warning.  The information fieldG  shall be set to the requested count minus the actual number of blocks,fA  filemarks, or setmarks spaced over as defined by the code value.s  lB  If the end-of-partition is encountered while spacing forward over@  blocks, filemarks, or setmarks, CHECK CONDITION status shall beH  returned, the sense key shall be set to MEDIUM ERROR, the EOM bit shallG  be set to one, and the valid bit shall be set to one.  The informationeE  field shall be set to the requested count minus the actual number ofhB  blocks, filemarks, or setmarks spaced over as defined by the code  value.   gD  If beginning-of-partition is encountered while spacing over blocks,B  filemarks, or setmarks in the reverse direction, the target shallH  return CHECK CONDITION status and shall set the sense key to NO SENSE. F  The EOM and valid bits shall be set to one, and the information fieldE  set to the total number of blocks, filemarks, or setmarks not spacedhG  over (the requested number of blocks, filemarks, or setmarks minus theC>  actual number of blocks, filemarks, or setmarks spaced over).   F  When spacing over sequential filemarks (or setmarks), the count field  is interpreted as follows:tG     a)     A positive value N shall cause forward movement to the firstnL            occurrence of N or more consecutive filemarks (or setmarks) beingD            logically positioned after the Nth filemark (or setmark).F     b)     A zero value shall cause no change in the logical position.L     c)     A negative value -N (2's complement notation) shall cause reverseD            movement to the first occurrence of N or more consecutiveD            filemarks (or setmarks) being logically positioned on theH            beginning-of-partition side of the Nth filemark (or setmark).  =F  If a setmark is encountered while spacing to sequential filemarks andA  the RSmk bit is set to one in the device configuration page (see F  10.3.3.1), CHECK CONDITION status shall be returned, the filemark bitH  shall be set to one, and the valid bit shall be set to zero.  The senseH  key shall be set to NO SENSE and the additional sense code shall be setB  to SETMARK DETECTED.  The target shall not return CHECK CONDITIONG  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 sequential E  filemarks or setmarks, CHECK CONDITION status shall be returned, the|D  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.s  eG  If end-of-data is encountered while spacing to sequential filemarks or-H  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.C  r?  When spacing to end-of-data, the count field is ignored.  Upon=B  successful completion, the medium shall be positioned such that aG  subsequent write operation would append to the last logically recordedt
  information.l  eG  If end-of-partition is encountered while spacing to end-of-data, CHECKeB  CONDITION status shall be returned, the sense key shall be set toG  MEDIUM ERROR, the EOM bit shall be set to one, and the valid bit shalla  be set to zero.  .  10.2.13 VERIFY commanda   G  The VERIFY command (see table 190) requests that the target verify onepD  or more block(s) beginning with the next block on the logical unit.   5                            Table 190 - VERIFY command P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (13h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   |   Logical unit number    |    Reserved     | Immed  | BytCmp | Fixed  |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                           Verification length                         |P  |-----+---                                                                 ---|P  | 4   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+  =  =F  An immediate (Immed) bit of zero indicates that the command shall notF  return status until the verify operation has completed.  An Immed bitF  of one indicates that status shall be returned as soon as the commandF  descriptor block has been validated (but after the data transfer from,  the initiator, if the BytCmp bit is one).    -M     NOTE 151 In order to ensure that no errors are lost, the initiator should N     set the Immed bit to zero on the last VERIFY command when issuing a series     of VERIFY commands.    D  A byte compare (BytCmp) bit of zero indicates that the verificationF  shall be simply a medium verification (e.g. CRC, ECC).  No data shall1  be transferred from the initiator to the target.    G  A BytCmp bit of one indicates that the target shall perform a byte-by--E  byte compare of the data on the medium and the data transferred from D  the initiator.  Data shall be transferred from the initiator to theE  target as in a WRITE command.  If the BytCmp bit is one and the byte=H  compare option is not supported, the target shall terminate the commandF  with CHECK CONDITION status and the sense key shall be set to ILLEGAL	  REQUEST.=  =C  The verification length specifies the amount of data to verify, intB  blocks or bytes, as indicated by the fixed bit. Refer to the READ@  command (see 10.2.4) for a description of the fixed bit and any>  associated error conditions. If the BytCmp bit is one and theG  verification length is zero, no data shall be verified and the current D  logical position shall not be changed.  This condition shall not be  considered as an error.  |D  The VERIFY command shall terminate when the verification length hasF  been satisfied, when an incorrect length block is encountered, when aH  filemark is encountered, when a setmark is encountered (if the RSmk bitE  is one in the device configuration page, see 10.3.3.1), when end-of-oD  data is encountered, when the end-of-partition is encountered, whenB  early-warning is encountered (if the REW bit is one in the deviceG  configuration page, see 10.3.3.1), or when an unrecoverable read erroriH  is encountered.  The status and sense data for each of these conditionsE  are handled in the same manner as in the READ command (see 10.2.4). uE  Upon successful completion of a VERIFY command, the logical positionr(  shall be after the last block verified.  oD  If the data does not compare (BytCmp bit of one), the command shallE  terminate with CHECK CONDITION status, the valid bit shall be set tosH  one, and the sense key shall be set to MISCOMPARE.  If the fixed bit isF  one, the information field shall be set to the requested verificationH  length minus the actual number of blocks successfully verified.  If theG  fixed bit is zero, the information field shall be set to the requestedrB  verification length minus the actual number of bytes successfullyE  verified.  This number may be larger than the requested verification H  length if the error occurred on a previous VERIFY command with an ImmedH  bit of one.  Upon termination, the medium shall be positioned after the9  block containing the miscompare (end-of-partition side).   c  10.2.14 WRITE command  fE  The WRITE command (see table 191) requests that the target write theoG  data that is transferred from the initiator to the current position on   the logical unit. )  h4                            Table 191 - WRITE commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (0Ah)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   |   Logical unit number    |              Reserved             | Fixed  |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                           Transfer length                             |P  |-----+---                                                                 ---|P  | 4   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+  a  tG  The fixed bit specifies whether fixed-length or variable-length blocksoG  are to be transferred.  See the READ BLOCK LIMITS command (see 10.2.5) @  for additional information about fixed and variable block mode.  IE  If the fixed bit is one, the transfer length specifies the number of F  fixed-length blocks to be transferred, using the current block lengthE  reported in the mode parameter block descriptor (see 8.3.3).  If the C  fixed bit is zero, a single block is transferred with the transfer--  length specifying the block length in bytes.g  TE  If the transfer length is zero, no data shall be transferred and thetA  current position on the logical unit shall not be changed.  Thisn,  condition shall not be considered an error.  iC  A WRITE command may be buffered or unbuffered, as indicated by thesD  buffered mode field of the mode parameter header (see 10.3.3).  ForE  unbuffered operation (buffered mode 0h), the target shall not returnaD  GOOD status until all data block(s) are successfully written to theE  medium.  For buffered operation (buffered mode 1h or 2h), the targetrE  may return GOOD status as soon as all data block(s) are successfullyn$  transferred to the target's buffer.  nM     NOTE 152 For compatibility with devices implemented prior to this versionaL     of this International Standard, a WRITE FILEMARKS command with the ImmedE     bit set to zero should be issued when completing a buffered write K     operation to ensure that all buffered data, filemarks, and setmarks are      written to the medium.  ,H  If the logical unit encounters early-warning during a WRITE command, anE  attempt to finish writing any data may be made, as determined by theoE  current settings of the REW and SEW bits in the device configurationAG  page (see 10.3.3.1).  The command shall terminate with CHECK CONDITIONoC  status and the EOM and valid bits shall be set to one in the sense H  data.  If all data that is to be written is successfully transferred toG  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 berG  transferred to the medium when early-warning is encountered, the sense %  key shall be set to VOLUME OVERFLOW.g  g3  The information field shall be defined as follows:tJ     a)     If unbuffered mode is reported in the mode parameter header andJ            the fixed bit is set to one, the information field shall be setF            to the requested transfer length minus the actual number of            blocks written.K     b)     If unbuffered mode is reported and the fixed bit is set to zero,sG            the information field shall be set to the requested transfere            length.L     c)     If buffered mode is reported in the mode parameter header and theI            fixed bit is set to one, the information field shall be set topJ            the total number of blocks, filemarks, and setmarks not writtenL            (the number of blocks not transferred from the initiator plus theE            number of blocks, filemarks, and setmarks remaining in theeJ            target's buffer).  Note that the value in the information field*            may exceed the transfer length.I     d)     If buffered mode is reported and the fixed bit is set to zero, K            the information field shall be set to the total number of bytes,lG            filemarks, and setmarks not written (the number of bytes notaC            transferred from the initiator plus the number of bytes,lG            filemarks, and setmarks remaining in the target's buffer).  n  s     NOTES   J     153 The value in the information field may exceed the transfer length.P     154 The target should ensure that some additional data can be written to theN     medium (e.g. labels, filemarks, or setmarks) after the first early-warning2     indication has been returned to the initiator.  iD  If a WRITE command is received while the logical unit is positionedD  between early-warning and end-of-partition, the target shall returnE  CHECK CONDITION status after attempting to perform the command.  The G  EOM and valid bits shall be set to one in the sense data.  If all data=E  that is to be written is successfully transferred to the medium, theiC  information field shall be set to zero.  If any data that is to be G  written is not transferred to the medium prior to encountering end-of- A  partition, the sense key shall be set to VOLUME OVERFLOW and the=/  information field shall be defined as follows: I     a)     If the fixed bit is one, the information field shall be set to-J            the requested transfer length minus the actual number of blocks!            written to the medium.eJ     b)     If the fixed bit is zero, the information field shall be set to)            the requested transfer length.|   M     NOTE 155 In some systems it is important to recognize an error if end-of--I     partition is encountered during execution of a WRITE command, without|E     regard for whether all data that is to be written is successfully L     transferred to the medium.  By its definition, the VOLUME OVERFLOW senseI     key may always validly be returned if end-of-partition is encountered M     while writing, and such usage is recommended.  Reporting the MEDIUM ERROR-N     sense key, as was done in some SCSI-1 implementations, may cause confusionF     as to whether there was really defective medium encountered during(     execution of the last write command.  A   10.2.15 WRITE FILEMARKS command  aE  The WRITE FILEMARKS command (see table 192) requests that the targetoC  write the specified number of filemarks or setmarks to the currente  position on the logical unit.  d9                       Table 192 - WRITE FILEMARKS commandsP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (10h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   |   Logical unit number    |         Reserved         |  WSmk  | Immed  |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                           Transfer length                             |P  |-----+---                                                                 ---|P  | 4   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+  i  eF  If the Write Setmark (WSmk) bit is one, the transfer length specifiesD  the number of setmarks to be written.  If the WSmk bit is zero, theA  transfer length specifies the number of filemarks to be written.o  eG  An immediate (Immed) bit of one indicates that the target shall return3G  status as soon as the command descriptor block has been validated.  AncH  Immed bit of one is only valid if buffered mode is reported in the mode  parameter header (see 10.3.3).e  .G  An Immed bit of zero indicates that the target shall not return statussH  until the write operation has completed.  Any buffered data, filemarks,D  and setmarks shall be written to the medium prior to completing the	  command.F  oK     NOTE 156 Upon completion of any buffered write operation, the initiatorIN     can issue a WRITE FILEMARKS command with the Immed bit set to zero and theG     transfer length field set to zero to ensure that all buffered data, C     filemarks, and setmarks are successfully written to the medium.   oF  If the logical unit encounters early-warning during a WRITE FILEMARKSG  command, an attempt to finish writing any buffered data, filemarks, or G  setmarks may be made, as determined by the current settings of the REW C  and SEW bits in the device configuration page (see 10.3.3.1).  ThesD  command shall terminate with CHECK CONDITION status and the EOM andC  valid bits shall be set to one in the sense data.  If all bufferednB  data, filemarks, and setmarks are successfully transferred to theF  medium, the sense key shall be set to NO SENSE or RECOVERED ERROR, asH  appropriate. If any buffered data, filemarks, or setmarks to be writtenE  are not transferred to the medium when early-warning is encountered,n/  the sense key shall be set to VOLUME OVERFLOW.    3  The information field shall be defined as follows:=K     a)     If unbuffered mode is reported in the mode parameter header, the|J            information field shall be set to the requested transfer lengthD            minus the actual number of filemarks or setmarks written.L     b)     If buffered mode is reported in the mode parameter header and theJ            buffered data was written in variable block mode (see 10.2.14),K            the information field shall be set to the total number of bytes,-J            filemarks, and setmarks not written (the number of filemarks orI            setmarks not transferred from the initiator plus the number of-L            bytes, filemarks and setmarks remaining in the target's buffer). J            Note that it is possible for the value in the information field)            to exceed the transfer length.|L     c)     If buffered mode is reported and the buffered data was written inI            fixed block mode (see 10.2.14), the information field shall be I            set to the total number of blocks, filemarks, and setmarks not I            written (the number filemarks or setmarks not transferred from-K            the initiator plus the number of blocks, filemarks, and setmarks K            remaining in the target's buffer).  Note that it is possible for=L            the value in the information field to exceed the transfer length.  nN     NOTE 157 The target should ensure that some additional data can be writtenN     to the medium (e.g. labels, filemarks, or setmarks) after the first early-:     warning indication has been returned to the initiator.  pC  If a WRITE FILEMARKS command is received while the logical unit is H  positioned between early-warning and end-of-partition, the target shallH  return CHECK CONDITION status after attempting to perform the command. F  The EOM and valid bits shall be set to one in the sense data.  If allH  filemarks or setmarks to be written are successfully transferred to theF  medium, the information field shall be set to zero.  If any filemarksE  or setmarks to be written are not transferred to the medium prior tofD  encountering end-of-partition, the sense key shall be set to VOLUMEA  OVERFLOW and the information field shall be set to the requestedfA  transfer length minus the actual number of filemarks or setmarksl  written to the medium.s  l.  10.3 Parameters for sequential-access devices  (       10.3.1 Diagnostic parameters   y@  This subclause defines the descriptors and pages for diagnostic1  parameters used with sequential-access devices. E  2G  The diagnostic page codes for sequential-access devices are defined inf  table 193.t  a8                        Table 193 - Diagnostic page codesP  +=============-==================================================-============+P  |  Page code  |  Description                                     |  Subclause |P  |-------------+--------------------------------------------------+------------|P  |     00h     |  Supported diagnostic pages                      |  8.3.1.1   |P  |  01h - 3Fh  |  Reserved (for all device type pages)            |            |P  |  40h - 7Fh  |  Reserved                                        |            |P  |  80h - FFh  |  Vendor-specific pages                           |            |P  +=============================================================================+     S  10.3.2 Log parameters   D  This subclause defines the descriptors and pages for log parameters&  used with sequential-access devices.   uF  The log page codes for sequential-access devices are defined in table  194.n  e5                            Table 194 - Log page codesrP  +=============-==================================================-============+P  |  Page code  |  Description                                     |  Subclause |P  |-------------+--------------------------------------------------+------------|P  |     01h     |  Buffer over-run/under-run page                  |  8.3.2.1   |P  |     02h     |  Error counter page (write) page                 |  8.3.2.2   |P  |     03h     |  Error counter page (read) page                  |  8.3.2.2   |P  |     04h     |  Error counter page (read reverse) page          |  8.3.2.2   |P  |     05h     |  Error counter page (verify) page                |  8.3.2.2   |P  |     07h     |  Last n error events page                        |  8.3.2.3   |P  |     06h     |  Non-media error page                            |  8.3.2.4   |P  |     00h     |  Supported log pages                             |  8.3.2.5   |P  |  08h - 2Fh  |  Reserved                                        |            |P  |     3Fh     |  Reserved                                        |            |P  |  30h - 3Eh  |  Vendor-specific                                 |            |P  +=============================================================================+  s  m  10.3.3 Mode parametersf  )E  This subclause defines the descriptors and pages for mode parameterse&  used with sequential-access devices.   gF  The mode parameter list, including the mode parameter header and mode*  block descriptor, are described in 8.3.3.  rH  The medium-type code field in the mode parameter header is reserved for  sequential-access devices.s  cE  The device-specific parameter byte of the mode parameter header (seee>  8.3.3) is defined in table 195 for sequential-access devices.  f;                      Table 195 - Device-specific parameter bP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |=====+========+==========================+===================================|P  |     |   WP   |      Buffered mode       |               Speed               |P  +=============================================================================+  e  iH  When used with the MODE SENSE command, a write protect (WP) bit of zeroH  indicates that medium is write enabled.  A WP bit of one indicates thatH  the medium is write protected.  When used with the MODE SELECT command,  this field is not defined.e  q=  Values for the buffered mode field are defined in table 196.s  p  a5                            Table 196 - Buffered modeseP  +===========-=================================================================+P  |  Code     |  Description                                                    |P  |-----------+-----------------------------------------------------------------|P  |   0h      |  The target shall not report GOOD status on write commands until|P  |           |  the data blocks are actually written on the medium.            |P  |           |                                                                 |P  |   1h      |  The target may report GOOD status on write commands as soon as |P  |           |  as all the data specified in the write command has been        |P  |           |  transferred to the target's buffer.  One or more blocks may be |P  |           |  buffered prior to writing the block(s) to the medium.          |P  |           |                                                                 |P  |   2h      |  The target may report GOOD status on write commands as soon as:|P  |           |     a) All the data specified in the write command has been     |P  |           |    successfully transferred to the target's buffer, and         |P  |           |     b) All buffered data from different initiators has been     |P  |           |    successfully written to the medium.                          |P  |           |                                                                 |P  |  3h - 7h  |  Reserved                                                       |P  +=============================================================================+      F  Values for the speed field shall be assigned as defined in table 197.   9                        Table 197 - Speed field definition P  +===========-=================================================================+P  |  Code     |  Description                                                    |P  |-----------+-----------------------------------------------------------------|P  |     0h    |  Default (Use the peripheral device's default speed).           |P  |     1h    |  Use the peripheral device's lowest speed.                      |P  |  2h - Fh  |  Use increasing peripheral device speeds.                       |P  +=============================================================================+  m  iG  For the MODE SELECT command, the density code field of the sequential-wF  access device block descriptor (8.3.3) indicates the density selectedG  by the initiator for use in subsequent read and write operations.  ForvC  devices capable of automatic density recognition, the density codee@  selected by the initiator may be overridden by the target for aC  subsequent read operation if the selected value does not match thetD  current recorded density of the medium.  If the MODE SELECT commandA  specifies the default density code the device selects the actualeC  density code to be used in a vendor-specific manner.  The value isoH  expected to be the principal density code (or an optimal density code).  mH  For the MODE SENSE command, the density code field reflects the currentE  operating density of the device.  If a current operating density hasyH  not been selected, either because no medium is installed or because theE  density of the installed medium has not been determined, the densitybC  code field should be set to the principal density code value.  The B  principal density code is the highest density code supported, the@  optimal density code supported, or the most common density codeG  supported.  In some devices, the principal density code value returnednH  in response to a MODE SENSE command may change dynamically to match theD  most recently selected density.  The density code value returned in>  response to a MODE SENSE command shall be as described below:L     a)     Following a UNIT ATTENTION condition for a power on or hard resetL            condition, while not ready, the target shall report the principal            density.rH     b)     Following a UNIT ATTENTION condition for a not-ready-to-ready(            transition, the target shall:M         1)    report the principal density if no attempt has been made by theh.               target to determine the density;M         2)    report the principal density if the target cannot automaticallya4               determine the density from the medium;L         3)    report the current medium density if the target has determined  l      the density from the medium.J     c)     Following a successful read operation at or after beginning-of-J            medium, the target shall report a density code value reflectingI            the recorded density of the medium.  For some implementations,eE            the target may automatically determine this value from thei@            medium.  For devices not capable of automatic densityJ            determination, the principal density is reported if the densityK            code value is not provided by the preceding MODE SELECT command.sI     d)     Following an unsuccessful read operation or a successful writewH            operation, while at beginning-of-partition, the target shall:G         1)    report a density code value as described for item b) if a M               previous MODE SELECT command has not established a density code /               for the currently mounted volume;hL         2)    report a density code value as provided by the last successfulC               MODE SELECT command for the currently mounted volume.oJ     e)     Following a successful unload operation the target shall reportG            the most recent density code value as determined by items b)h            through d) above.  e<  Table 198 lists the sequential-access device density codes   r=                   Table 198 - Sequential-access density codesdY  +==========-======================================================================-====+eY  |Code value|                           Description                                |Note|aY  |----------+----------------------------------------------------------------------+----| Y  |   00h    | Default density (MODE SELECT command only)                           |    |EY  |   0Eh    | Reserved for ECMA                                                    |    |aY  |15h - 7Eh | Reserved                                                             |    |sY  |   7Fh    | No change from previous density (NO-OP)                              |  7 |iY  |80h - FFh | Vendor-specific                                                      |    |eY  |          |----------------------------------------------------------------------+----|1Y  |          |               Descriptions for magnetic tapes                        |    |=Y  |          |----------------------------------------------------------------------|    | Y  |          |Width      mm(in) |Tracks|Density     bpmm(bpi)|Code|Type|Reference   |    |-Y  |          |------------------+------+---------------------+----+----+------------|    | Y  |   01h    |12,7      (0,5)   |   9  |     32        (800) |NRZI| R  |X3.22-1983  |  2 | Y  |   02h    |12,7      (0,5)   |   9  |     63      (1 600) |PE  | R  |X3.39-1986  |  2 | Y  |   03h    |12,7      (0,5)   |   9  |    246      (6 250) |GCR | R  |X3.54-1986  |  2 |+Y  |   05h    | 6,3      (0,25)  |  4/9 |    315      (8 000) |GCR | C  |X3.136-1986 |  1 |.Y  |   06h    |12,7      (0,5)   |   9  |    126      (3 200) |PE  | R  |X3.157-1987 | 2,4|sY  |   07h    | 6,3      (0,25)  |   4  |    252      (6 400) |IMFM| C  |X3.116-1986 |  1 |iY  |   08h    | 3,81     (0,15)  |   4  |    315      (8 000) |GCR | CS |X3.158-1987 | 1,4|rY  |   09h    |12,7      (0,5)   |  18  |  1 491     (37 871) |GCR | C  |X3B5/87-099 | 2,4|eY  |   0Ah    |12,7      (0,5)   |  22  |    262      (6 667) |MFM | C  |X3B5/86-199 | 1,4|-Y  |   0Bh    | 6,3      (0,25)  |   4  |     63      (1 600) |PE  | C  |X3.56-1986  |  1 |eY  |   0Ch    |12,7      (0,5)   |  24  |    500     (12 690) |GCR | C  |HI-TC1      | 1,6|(Y  |   0Dh    |12,7      (0,5)   |  24  |    999     (25 380) |GCR | C  |HI-TC2      | 1,6|eY  |   0Fh    | 6,3      (0,25)  |  15  |    394     (10 000) |GCR | C  |QIC-120     | 1,6| Y  |   10h    | 6,3      (0,25)  |  18  |    394     (10 000) |GCR | C  |QIC-150     | 1,6| Y  |   11h    | 6,3      (0,25)  |  26  |    630     (16 000) |GCR | C  |QIC-320     | 1,6| Y  |   12h    | 6,3      (0,25)  |  30  |  2 034     (51 667) |RLL | C  |QIC-1350    | 1,6| Y  |   13h    | 3,81     (0,15)  |   1  |  2 400     (61 000) |DDS | CS |X3B5/88-185A|  5 ||Y  |   14h    | 8,00     (0,315) |   1  |  1 703     (43 245) |RLL | CS |X3.202-1991 |  5 |dY  |   15h    | 8,00     (0,315) |   1  |  1 789     (45 434) |RLL | CS |ECMA TC17   |  5 | Y  |   16h    |12,7      (0,5)   |  48  |    394     (10 000) |MFM | C  |X3.193-1990 | 1,4|=Y  |   17h    |12,7      (0,5)   |  48  |  1 673     (42 500) |MFM | C  |X3B5/91-174 | 1,4|eY  |--------------------------------------------------------------------------------------| Y  |   Code  Description                                              Type  Description   |pY  |   ----  ---------------------------------------                  ----  ------------  |iY  |   NRZI  Non return to zero, change on ones                         R   Reel-to-reel  |eY  |   GCR   Group code recording                                       C   Cartridge     |.Y  |   PE    Phase encoded                                              CS  Cassette      |=Y  |   IMFM  Inverted modified frequency modulation                                       | Y  |   MFM   Modified frequency modulation                                                |+Y  |   DDS   DAT data storage                                                             | Y  |   RLL   Run length limited                                                           |=Y  |--------------------------------------------------------------------------------------|oY  | NOTES                                                                                |uY  |  1   Serial recorded.                                                                |eY  |  2   Parallel recorded.                                                              | Y  |  3   Old format known as QIC-11.                                                     |=Y  |  4   See annex D for additional standards information.                               | Y  |  5   Helical scan                                                                    |-Y  |  6   This is not an American National Standard.  The reference is based              ||Y  |      on an industry standard definition of the media format.                         | Y  |  7   This density code value is defined for the MODE SELECT command and              |hY  |      shall not be returned by the MODE SENSE command.                                |dY  +======================================================================================+r  '  uG  The mode page codes for sequential-access devices are defined in tablet  199.   c5                           Table 199 - Mode page codes P  +=============-==================================================-============+P  |  Page code  |  Description                                     |  Subclause |P  |-------------+--------------------------------------------------+------------|P  |     0Ah     |  Control mode page                               |  8.3.3.1   |P  |     10h     |  Device configuration page                       | 10.3.3.1   |P  |     02h     |  Disconnect-reconnect page                       |  8.3.3.2   |P  |     11h     |  Medium partition page(1)                        | 10.3.3.2   |P  |     12h     |  Medium partition page(2)                        | 10.3.3.3   |P  |     13h     |  Medium partition page(3)                        | 10.3.3.3   |P  |     14h     |  Medium partition page(4)                        | 10.3.3.3   |P  |     09h     |  Peripheral device page                          |  8.3.3.3   |P  |     01h     |  Read-write error recovery page                  | 10.3.3.4   |P  |     00h     |  Vendor-specific (does not require page format)  |            |P  |  03h - 08h  |  Reserved                                        |            |P  |  0Bh - 0Fh  |  Reserved                                        |            |P  |  15h - 3Eh  |  Vendor-specific (page format required)          |            |P  |     3Fh     |  Return all pages                                |            |P  |             |     (valid only for the MODE SENSE command)      |            |P  +=============================================================================+  e  h#  10.3.3.1 Device configuration page    E  The device configuration page (see table 200) is used to specify the 4  appropriate sequential-access device configuration.  e:                      Table 200 - Device configuration pageP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+========+========+=====================================================|P  | 0   |   PS   |Reserved|         Page code (10h)                             |P  |-----+-----------------------------------------------------------------------|P  | 1   |                           Page length (0Eh)                           |P  |-----+-----------------------------------------------------------------------|P  | 2   |Reserved|  CAP   |  CAF   |                Active format               |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Active partition                            |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Write buffer full ratio                     |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Read buffer empty ratio                     |P  |-----+-----------------------------------------------------------------------|P  | 6   | (MSB)                                                                 |P  |-----+---                        Write delay time                         ---|P  | 7   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 8   |  DBR   |  BIS   |  RSmk  |  AVC   |      SOCF       |   RBO  |  REW   |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Gap size                                    |P  |-----+-----------------------------------------------------------------------|P  | 10  |      EOD defined         |  EEG   |  SEW   |        Reserved          |P  |-----+-----------------------------------------------------------------------|P  | 11  | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 12  |                           Buffer size at early warning                |P  |-----+---                                                                 ---|P  | 13  |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 14  |                           Select data compression algorithm           |P  |-----+-----------------------------------------------------------------------|P  | 15  |                           Reserved                                    |P  +=============================================================================+  t  iF  A change active partition (CAP) bit of one indicates that the logicalH  partition is to be changed to the one specified by the active partitionE  field. A CAP bit of zero indicates no partition change is specified.=  =B  A change active format (CAF) bit of one indicates that the activeD  format is to be changed to the value specified in the active format?  field.  A CAF bit of zero indicates no active format change is-F  specified.  For some devices, the format may only be changed when the+  logical unit is at beginning-of-partition.   EH   The active format field indicates which recording format is in use forD  the selected density code when reading or writing data on a logicalB  unit.  The value of the active format field is vendor-specific.    pC  The active partition field indicates the current logical partition   number in use on the medium.    H  The write buffer full ratio, on WRITE commands, indicates to the targetC  how full the buffer shall be before writing data to the medium.  A 9  value of zero indicates that the value is not specified.    G  The read buffer empty ratio, on READ commands, indicates to the target-E  how empty the buffer shall be before retrieving additional data from)H  the medium.  A value of zero indicates that the value is not specified.  -G  The write delay time indicates the maximum time, in 100 ms increments, C  that the target should wait before any buffered data that is to beRG  written, is forced to the medium after the last buffered WRITE command H  that did not cause the buffer to exceed the buffer full ratio.  A valueE  of zero indicates that the target shall never force buffered data to #  the medium under these conditions.   8B  A data buffer recovery (DBR) bit of one indicates that the targetH  supports data buffer recovery using the RECOVER BUFFERED DATA command. B  A DBR bit of zero indicates that the target does not support data.  buffer recovery.  This bit is target-defined.   E  A block identifiers supported (BIS) bit of zero indicates that block F  IDs are not supported in the format written on the medium.  A BIS bitH  of one indicates that the format on the medium has recorded informationB  about the block IDs relative to a partition.  This bit is target-	  defined.P  |D  A report setmarks (RSmk) bit of one indicates that the target shall?  recognize and report setmarks during appropriate read or space D  operations.  A RSmk bit of zero indicates that the target shall not  report setmarks.,   D  The automatic velocity control (AVC) bit of one, indicates that theD  device shall select the speed (if the device supports more than oneF  speed) based on the data transfer rate that should optimize streaming@  activity and minimize medium repositioning.  An AVC bit of zeroA  indicates the speed chosen should be the device's default speed.   |G  A stop on consecutive filemarks (SOCF) field of 00b indicates that the/C  device shall pre-read data from the medium in buffered mode to the3B  limits of the buffer capacity without regard for filemarks.  ThisB  implies that the device can differentiate between data blocks andD  filemarks in the buffer.  Values 01b, 10b, and 11b specify that theD  device shall terminate the pre-read operation if one, two, or threeF  consecutive filemarks are detected, respectively.  If the RSmk bit isB  one, the target shall interpret this field as stop on consecutive
  setmarks.   C  A recover buffer order (RBO) bit of one indicates that data blocks H  shall be returned from the target's buffer on a RECOVERED BUFFERED DATAG  command in LIFO order (last-in-first-out) from which they were written A  to the buffer.  A RBO bit of zero indicates data blocks shall be -  returned in FIFO (first-in-first-out) order.    C  A report early-warning (REW) bit of zero indicates that the target H  shall not report the early-warning condition for read operations and itB  shall report early-warning at or before any medium-defined early-+  warning position during write operations.     H  A REW bit of one indicates that the target shall return CHECK CONDITIONE  status with the EOM bit set in the sense data when the early-warning F  position is encountered during read and write operations.  If the REWB  bit is one and the SEW bit is zero, the target shall return CHECKG  CONDITION status with the sense key set to VOLUME OVERFLOW when early- 0  warning is encountered during write operations.   N     NOTE 158 A REW bit of one is intended for compatibility with those systemsJ     using old tape formats that require an early-warning indication duringH     read operations.  Other systems should set this bit to zero to avoidL     potential data loss when interchanging tapes between peripheral devices.   H  The GapSize field value determines the size of the inter-block gap whenH  writing data.  A value of 00h specifies the device's defined gap size. H  A value of 01h specifies a device defined gap size sufficiently long toG  support update-in-place.  Values of 02h through 0Fh are multipliers on F  the device's defined gap size.  Values 10h through 7Fh are reserved. ,  Values 80h through FFh are vendor-specific.  rD  The end-of-data (EOD) defined field indicates which format type theG  logical unit shall use to detect and generate the EOD area.  The types=+  of EOD formats are specified in table 201.s  r3                             Table 201 - EOD formats9D  +=============-===================================================+D  |    Value    |  Description                                      |D  |-------------+---------------------------------------------------|D  |     000b    |  Logical unit's default EOD definition            |D  |     001b    |  Format-defined erased area of medium             |D  |     010b    |  As specified in the SOCF field                   |D  |     011b    |  EOD recognition and generation is not supported  |D  | 100b - 111b |  Reserved                                         |D  +=================================================================+      A  An enable EOD generation (EEG) bit set to one indicates that the G  logical unit shall generate the appropriate EOD area, as determined by H  the EOD defined field. A value of zero indicates that EOD generation is
  disabled.   M     NOTE 159 Some logical units may not generate EOD at the completion of any      write-type operation.   |E  The synchronize at early-warning (SEW) bit set to one indicates that G  the target shall cause any buffered write data, filemarks, or setmarks|E  to be transferred to the medium when early-warning is encountered. A C  value of zero indicates that the target shall retain any unwritten G  buffered data, filemarks, or setmarks in the buffer when early-warningqH  is encountered (see the WRITE command, 10.2.14, and the WRITE FILEMARKS  command, 10.2.15).    F  The buffer size at early-warning field indicates the value, in bytes,H  to which the target shall reduce its logical buffer size when writing. G  The target should reduce the buffer size only when the logical unit isgG  positioned between its early-warning and end-of-partition.  A value of B  zero indicates that the implementation of this function is device  specific.    TN     NOTE 160 The intent is to prevent the loss of data by limiting the size of.     the buffer when near the end-of-partition.  7F  The select data compression algorithm field set to 00h indicates thatH  the target shall not use a compression algorithm on any data sent to itH  prior to writing the data to the medium.  A value of 01h indicates thatF  the data to be written shall be compressed using the target's defaultE  compression algorithm.  Values 02h through 7Fh are reserved.  Values-%  80h through FFh are vendor-specific.    "  10.3.3.2 Medium partition page(1)  ED  The medium partition page(1) (see table 202) is used to specify theF  first group of medium partitions.  Additional groups are specified in  medium partition pages(2-4).o  t:                       Table 202 - Medium partition page(1)P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+========+========+=====================================================|P  | 0   |   PS   |Reserved|         Page code (11h)                             |P  |-----+-----------------------------------------------------------------------|P  | 1   |                           Page length                                 |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Maximum additional partitions               |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Additional partitions defined               |P  |-----+-----------------------------------------------------------------------|P  | 4   |  FDP   |  SDP   |  IDP   |       PSUM      |       Reserved           |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Medium format recognition                   |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   |                           Reserved                                    |P  |=====+=======================================================================|P  |     |                   Partition size descriptor(s)                        |P  |=====+=======================================================================|P  | 0   | (MSB)                                                                 |P  |-----+---                        Partition size                           ---|P  | 1   |                                                                 (LSB) |P  +=============================================================================+  =  =B  The maximum additional partitions field is a target-defined valueH  indicating the maximum number of additional partitions supported by theE  logical unit.  A value of zero indicates that no value is specified.n  a@  The additional partitions defined field specifies the number ofE  additional partitions to be defined for a volume when the SDP or IDPtG  bit is set to one.  The maximum value allowed is the value returned ind)  the maximum additional partitions field.i   C  A fixed data partitions (FDP) bit of one indicates that the deviceuA  assigns partitions based on its fixed definition of partitions. nH  Setting this bit to one may only be valid at beginning-of-partition and1  is mutually exclusive with the SDP and IDP bits.h  aG  A select data partitions (SDP) bit of one indicates that the device istF  to partition the medium into the number of partitions as specified byF  the additional partitions defined field using partition sizes definedH  by the device.  Setting this bit to one may only be valid at beginning-G  of-partition and it is mutually exclusive with the FDP and IDP fields.    D  An initiator-defined partitions (IDP) bit of one indicates that theG  initiator is defining the number and size of the data partitions usingo?  the additional partitions defined field and the partition size H  descriptors. Setting this bit to one may only be valid at beginning-of-A  partition and is mutually exclusive with the FDP and SDP fields.t  hN     NOTE 161 Since defining partitions may require reformatting the medium forH     some implementations, an implicit write to the medium may occur as aJ     result of a MODE SELECT command that supplies any of these parameters.   G  Partition size unit of measure (PSUM) field defines the units in whichiF  the partition size descriptors select the partition size.  The valuesG  00b, 01b, and 10b define the units as bytes, kilobytes, and megabytes,h*  respectively.  The value 11b is reserved.  y?   The medium format recognition field is a target-defined valuedH  indicating the device's capability to automatically identify the mediumA  format and partition information when reading an unknown volume.f  aD  Values for the medium format recognition field shall be assigned as	  follows:iE     a)     00h       Logical unit is incapable of format or partitioni!                      recognition.sH     b)     01h       Logical unit is capable of format recognition only.K     c)     02h       Logical unit is capable of partition recognition only.eD     d)     03h       Logical unit is capable of format and partition!                      recognition.t,         e)    04h - FFh            Reserved.  sJ     NOTE 162 If a target indicates that it is not capable of medium formatK     recognition, the initiator must supply all necessary parameters for theeK     device to identify the specific format.  The value in this field may bef(     different following a medium change.  hH  Partition size descriptors define the size of the respective partitionsF  in the units specified in the PSUM field.  Up to 64 partitions may beG  defined using this page.  If additional partitions need to be defined,sC  up to 64 partitions can be defined in each of the medium partitionh   pages(2-4) defined in 10.3.3.3.  i$  10.3.3.3 Medium partition page(2-4)  rB  The medium partition page(2-4) (see table 203) is used to specifyF  additional groups of medium partitions.  The first group is specified0  in the medium partition page(1) (see 10.3.3.2).  a;                      Table 203 - Medium partition page(2-4)RP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+========+========+=====================================================|P  | 0   |   PS   |Reserved|         Page code (12h, 13h, 14h)                   |P  |-----+-----------------------------------------------------------------------|P  | 1   |                           Page length                                 |P  |=====+=======================================================================|P  |     |                       Partition size descriptor(s)                    |P  |=====+=======================================================================|P  | 0   | (MSB)                                                                 |P  |-----+---                        Partition size                           ---|P  | 1   |                                                                 (LSB) |P  +=============================================================================+  n  tD  The additional page codes defined for partition size definition areG  12h, 13h, and 14h.  Up to a maximum of 64 partitions can be defined inaH  each of these pages.  The partition size is defined by the value of theD  partition size field.  The units of size used by the partition sizeE  field is specified in the PSUM field of the medium partition page(1)   (see 10.3.3.2).  lN     NOTE 163 Since defining partitions may require reformatting the medium forH     some implementations, an implicit write to the medium may occur as aD     result of a MODE SELECT command that supplies these parameters.   =(  10.3.3.4 Read-write error recovery page  sG  The read-write error recovery page (see table 204) specifies the error=A  recovery and reporting parameters that the target shall use when ?  transferring data between the initiator and the medium.  These-E  parameters only apply to read-write errors and do not affect message09  system retries or positioning error recovery procedures.    =                    Table 204 - Read-write error recovery page|P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+========+========+=====================================================|P  | 0   |   PS   |Reserved|         Page code (01h)                             |P  |-----+-----------------------------------------------------------------------|P  | 1   |                           Page length (0Ah)                           |P  |-----+-----------------------------------------------------------------------|P  | 2   |Reserved|Reserved|   TB   |Reserved|  EER   |  PER   |  DTE   |  DCR   |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Read retry count                            |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 8   |                           Write retry count                           |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 10  |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 11  |                           Reserved                                    |P  |-----------------------------------------------------------------------------|P  |   NOTE - The parameters in this page also apply to verify operations.       |P  +=============================================================================+  e   E  A transfer block (TB) bit of one indicates that a data block that is >  not recoverable within the specified recovery limits shall beI  transferred to the initiator before CHECK CONDITION status is returned.  G  A TB bit of zero indicates that the unrecoverable data block shall not-D  be transferred to the initiator.  Data blocks that can be recoveredE  within the recovery limits are always transferred, regardless of the-  value of the TB bit.-  -D  An enable early recovery (EER) bit of one indicates that the targetD  shall use the most expedient error recovery algorithm (e.g. attemptG  error correction prior to retries).  An EER bit of zero indicates that C  the target shall use the most deliberate error recovery algorithm,-E  within the limits established by the other error recovery parameters|C  (e.g. attempt to recover the block error-free prior to using error 
  correction).-  -E  A post error (PER) bit of one indicates that the target shall return F  CHECK CONDITION status to report recovered errors.  A PER bit of zeroG  indicates that the target shall not report errors recovered within the-E  limits established by the error recovery parameters.  If this bit is ,  zero, the DTE bit must also be set to zero.  -G  A disable transfer on error (DTE) bit of one indicates that the target E  shall terminate the data transfer after a recovered read-write error=F  occurs.  All data from the recovered block shall be transferred priorF  to terminating the read-write operation.  A DTE bit of zero indicatesF  that the target shall not terminate the transfer for errors recovered?  within the limits established by the read-write error recovery   parameters.   F  A disable correction (DCR) bit of one indicates that the target shallD  not use error correction codes during error recovery.  A DCR bit ofB  zero allows the use of error correction codes for error recovery.  =C  The read retry count specifies the number of times that the targetmH  should attempt its recovery algorithm during a read operation before anG  unrecoverable error is reported.  A read retry count of zero indicatesiA  that the target shall not use its recovery algorithm during reade  operations.  tD  The write retry count specifies the number of times that the targetF  should attempt its recovery algorithm during a write operation beforeA  an unrecoverable error is reported.  A write retry count of zerooF  indicates that the target shall not use its recovery algorithm during  write operations.  u7  10.4 Definitions specific to sequential access devicesr  iE  10.4.1 beginning-of-partition:  The position at the beginning of theiG  permissible recording region of a partition.  If only one partition iscD  defined, this position is typically equivalent to the beginning-of-  medium.   F  10.4.2 beginning-of-medium:  The extreme position along the medium inE  the direction away from the supply reel which can be accessed by theS	  device.     C  10.4.3 buffered mode:  A mode of data transfer in write operationslC  which facilitates tape streaming (10.1.5), as reported in the mode 5  parameter header device-specific parameter (10.3.3).t  iH  10.4.4 early-warning:  A physical mark or device computed position nearC  but logically before the end-of-partition (independent of physicaleA  direction).  See the REW bit in the device configuration page inn
  10.3.3.1.  yF  10.4.5 end-of-data:  End of data in a partition is denoted in format-G  specific manner. See the EOD defined field in the device configurationt  page in 10.3.3.1.   D  10.4.6 end-of-medium:  The extreme position along the medium in theB  direction away from the take-up reel which can be accessed by theH  device.  This position may be accessed by devices that support the LOAD,  UNLOAD command with the EOT bit set to one.   E  10.4.7 end-of-partition:  The position at the end of the permissibles!  recording region of a partition.e   A  10.4.8 filemark:  A special recorded element within a partition,d?  containing no user data, which provides a segmentation scheme.h  eE  10.4.9 overlength:  The incorrect length condition that exists afterfB  executing a read command when the length of the actual block readG  exceeds the requested transfer length in the command descriptor block.m  oF  10.4.10 partition:  The entire usable region of recording and readingD  paths in a volume or in a portion of a volume, defined in a device-E  specific manner.  If there is more than one partition, they shall be0@  numbered starting with zero (i.e. beginning-of-partition-zero).   A  10.4.11 setmark:  A special recorded element within a partition,.>  containing no user data, which provides a segmentation schemeC  hierarchically superior to filemarks for use in addressing or fasts.  positioning on high capacity storage devices.  eD  10.4.12 spacing:  The act of positioning the medium on a sequential  access device.a  .G  10.4.13 underlength:  The incorrect length condition that exists aftertC  executing a read command when the requested transfer length in the F  command descriptor block exceeds the length of the actual block read.  nH  10.4.14 volume:  A recording medium together with its physical carrier.  p  s   11 Commands for printer devices  .      11.1 Model for printer devices   mA  This command set includes capability for the printer-controllingtG  device, that is an SCSI target to be is functionally separate from the H  physical printer device (see figure 27) as well as integrated with it. G  The physical printer device is connected to the SCSI target via one of=D  several common device-level interfaces.  There may be more than oneH  physical printer device attached to the printer controlling device.  InA  such a case, each physical printer device is assigned a separate=C  logical unit number, beginning with zero.  The printer-controlling=H  device, printer device-level interface, and the physical printer device4  are referred to collectively as the printer device.  -  -  -  -  -  -  -  -  -  |7                          Figure 27 - SCSI printer model    H  Specific control mechanisms are defined in mode pages for two industry-G  standard interfaces known as the line printer interface (e.g. the DatazH  Products interface or equivalent) and the EIA RS-232C interface.  TheseG  mode pages are used to control optional features of these interfaces.  D  No mode page was defined for the popular industry-standard parallelE  interface because the options requiring controls are embedded in the   data.   D  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  aB  The printer device commands are structured on the assumption thatG  specific printer control codes may be embedded in the data transferredpD  by the FORMAT, PRINT, and SLEW AND PRINT commands.  The transparentH  control codes may take the form of escape code sequences.  commands forF  the operation of the target function and some printer controls, whichD  are not convenient to handle in a transparent way, are specified in  11.2.  fD  This International Standard does not specify which character set isC  used by the printer device; nor does it specify the meaning of thee*  escape code sequences that may be used.     "  11.2 Commands for printer devices  yA  The commands for printer devices shall be as shown in table 205.   a<                     Table 205 - Commands for printer devicesI  +=====================================-============-======-============+wI  |  Command name                       | Operation  | Type |  Subclause |rI  |                                     |   code     |      |            | I  |-------------------------------------+------------+------+------------|=I  | CHANGE DEFINITION                   |    40h     |   O  |   8.2.1    | I  | COMPARE                             |    39h     |   O  |   8.2.2    | I  | COPY                                |    18h     |   O  |   8.2.3    |=I  | COPY AND VERIFY                     |    3Ah     |   O  |   8.2.4    |PI  | FORMAT                              |    04h     |   O  |  11.2.1    |-I  | INQUIRY                             |    12h     |   M  |   8.2.5    | I  | LOG SELECT                          |    4Ch     |   O  |   8.2.6    |-I  | LOG SENSE                           |    4Dh     |   O  |   8.2.7    |eI  | MODE SELECT(6)                      |    15h     |   O  |   8.2.8    |-I  | MODE SELECT(10)                     |    55h     |   O  |   8.2.9    | I  | MODE SENSE(6)                       |    1Ah     |   O  |   8.2.10   | I  | MODE SENSE(10)                      |    5Ah     |   O  |   8.2.11   |-I  | PRINT                               |    0Ah     |   M  |  11.2.2    | I  | READ BUFFER                         |    3Ch     |   O  |   8.2.12   |-I  | RECEIVE DIAGNOSTIC RESULTS          |    1Ch     |   O  |   8.2.13   | I  | RECOVER BUFFERED DATA               |    14h     |   O  |  11.2.3    |-I  | RELEASE UNIT                        |    17h     |   M  |  10.2.9    |rI  | REQUEST SENSE                       |    03h     |   M  |   8.2.14   |-I  | RESERVE UNIT                        |    16h     |   M  |  10.2.10   | I  | SEND DIAGNOSTIC                     |    1Dh     |   M  |   8.2.15   |-I  | SLEW AND PRINT                      |    0Bh     |   O  |  11.2.4    | I  | STOP PRINT                          |    1Bh     |   O  |  11.2.5    |-I  | SYNCHRONIZE BUFFER                  |    10h     |   O  |  11.2.6    |9I  | TEST UNIT READY                     |    00h     |   M  |   8.2.16   ||I  | WRITE BUFFER                        |    3Bh     |   O  |   8.2.17   |-I  |----------------------------------------------------------------------| I  |Key:  M = command implementation is mandatory.                        |-I  |      O = command implementation is optional.                         | I  +======================================================================+-  -  -G  The following operation codes are vendor-specific: 01h, 02h, 05h, 06h,yH  07h, 08h, 09h, 0Ch, 0Dh, 0Eh, 0Fh, 11h, 13h, 19h, and C0h through FFh. C  All remaining operation codes for printer devices are reserved for)  future standardization.  d  11.2.1 FORMAT command  cF  The FORMAT command (see table 206) provides a means for the initiatorF  to specify forms or fonts to printers that support programmable formsA  or fonts.  The format information is peripheral-device specific.r  f5                            Table 206 - FORMAT commandrP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (04h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |         Reserved         | Format type     |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                           Transfer length                             |P  |-----+---                                                                 ---|P  | 4   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+     pE  The format type field specifies the type of format information to behH  transferred from the initiator to the target.  This field is defined in  table 207.z   3                             Table 207 - Format typec  +========-===================+   |  Code  |  Format type      |t  |--------+-------------------|   |   00b  |  Set form         |o  |   01b  |  Set font         |e  |   10b  |  Vendor-specific  |   |   11b  |  Reserved         |h  +============================+r  l  iH  The transfer length specifies the length in bytes of format informationH  that shall be transferred during the DATA OUT phase.  A transfer lengthD  of zero indicates that no format information shall be transferred. 1  This condition shall not be considered as error.g  s  11.2.2 PRINT commandr  lD  The PRINT command (see table 208) transfers the specified number of6  bytes from the initiator to the target to be printed.  i4                            Table 208 - PRINT commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (0Ah)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |                  Reserved                  |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                           Transfer length                             |P  |-----+---                                                                 ---|P  | 4   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+  e  lH  The transfer length specifies the length in bytes of data that shall beB  transferred during the DATA OUT phase.  A transfer length of zeroG  indicates that no data shall be transferred.  This condition shall nott  be considered as error.  s%  11.2.3 RECOVER BUFFERED DATA commando  nA  The RECOVER BUFFERED DATA command (see table 209) returns to thegH  initiator data that was transferred to the target, but not yet printed.   <                    Table 209 - RECOVER BUFFERED DATA commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (14h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |                  Reserved                  |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                           Transfer length                             |P  |-----+---                                                                 ---|P  | 4   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+  n  aF  This command is normally used only to recover from error or exceptionD  conditions that make it impossible to print the buffered data.  TheH  order in which data are transferred from the target to the initiator isF  the same as when the data were previously transferred using the PRINTE  command or SLEW AND PRINT command.  Data transferred by this commandeH  are  deleted from the target data buffer.  One or more RECOVER BUFFEREDB  DATA commands may be used to return the buffered data that is not	  printed.C  tD  If an attempt is made to recover more data than is contained in theH  buffer, the command shall be terminated with CHECK CONDITION status andF  the sense key shall be set to NO SENSE.  In addition, the EOM, valid,F  and ILI bits shall be set to one.  The information bytes shall be setG  to the difference (residue) between the transfer length and the actualn  number of bytes returned.    eG  The transfer length specifies the maximum length in bytes of data thatsE  shall be transferred during the DATA IN phase.  A transfer length oftH  zero indicates that no data shall be transferred.  This condition shall  not be considered as error.  k  11.2.4 SLEW AND PRINT command  .C  The SLEW AND PRINT command (see table 210) transfers the specifiedrF  number of bytes from the initiator to the target to be printed.  ThisB  command is provided for printer devices that do not support forms4  control information embedded within the print data.  ;9                        Table 210 - SLEW AND PRINT commandeP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (0Bh)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |                  Reserved         | Channel|P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Slew value                                  |P  |-----+-----------------------------------------------------------------------|P  | 3   | (MSB)                                                                 |P  |-----+---                        Transfer length                          ---|P  | 4   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+      H  The transfer length specifies the length in bytes of data that shall beB  transferred during the DATA OUT phase.  A transfer length of zeroG  indicates that no data shall be transferred.  This condition shall not|  be considered as error.   C  If the channel bit is zero, the slew value specifies the number of8B  lines the form shall be advanced before printing.  A value of 255H  indicates that the form shall be advanced to the first line of the nextA  form before printing.  If the channel bit is one, the slew value3F  specifies the forms control channel number to which the form shall beB  advanced prior to printing the data.  If implemented, the printerD  options page in the MODE SELECT command provides additional control(  over the usage of the slew value field.   F  If the channel bit is one, and the channel option is not implemented,D  the command shall be terminated with CHECK CONDITION status and the+  sense key shall be set to ILLEGAL REQUEST.      11.2.5 STOP PRINT command   E  The STOP PRINT command (see table 211) requests that the target halt24  printing on buffered devices in an orderly fashion.  -7                          Table 211 - STOP PRINT commandaP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (1Bh)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |                  Reserved         | Retain |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Vendor-specific                             |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+     eH  A retain bit of zero requests that the target data buffer be discarded;A  otherwise, the data not printed shall be retained.  The data not E  printed may be recovered using the RECOVER BUFFERED DATA command, if E  implemented by the target.  A subsequent SYNCHRONIZE BUFFER command, H  PRINT command, or SLEW AND PRINT command shall cause the remaining dataG  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   G  The SYNCHRONIZE BUFFER command (see table 212) provides a means for an+G  initiator to ensure that the data have been printed successfully prior=E  to releasing the peripheral device.  This is useful for applicationsmC  that handle any error or exception conditions (e.g. end-of-medium)e)  prior to termination of the application.    ;                      Table 212 - SYNCHRONIZE BUFFER command=P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (10h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |                  Reserved                  |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+      B  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 exception@  condition on the peripheral device), then this command shall beH  terminated with a CHECK CONDITION status and the appropriate sense key.   E  The printer options page in the MODE SELECT command, if implemented, G  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. =  =H  The diagnostic page codes for printer devices are defined in table 213.  t8                        Table 213 - Diagnostic page codesP  +=============-==================================================-============+P  |  Page code  |  Description                                     |  Subclause |P  |-------------+--------------------------------------------------+------------|P  |     00h     |  Supported diagnostic pages                      |  8.3.1.1   |P  |  01h - 3Fh  |  Reserved (for all device type pages)            |            |P  |  40h - 7Fh  |  Reserved                                        |            |P  |  80h - FFh  |  Vendor-specific pages                           |            |P  +=============================================================================+  =  =  11.3.2 Log parameters  =D  This subclause defines the descriptors and pages for log parameters  used with printer devices.    A  The log page codes for printer devices are defined in table 214.-  -5                            Table 214 - Log page codesuP  +=============-==================================================-============+P  |  Page code  |  Description                                     |  Subclause |P  |-------------+--------------------------------------------------+------------|P  |     01h     |  Buffer over-run/under-run page                  |  8.3.2.1   |P  |     07h     |  Last n error events page                        |  8.3.2.3   |P  |     06h     |  Non-medium error page                           |  8.3.2.4   |P  |     00h     |  Supported log pages                             |  8.3.2.5   |P  |  02h - 05h  |  Reserved                                        |            |P  |  08h - 2Fh  |  Reserved                                        |            |P  |     3Fh     |  Reserved                                        |            |P  |  30h - 3Eh  |  Vendor-specific pages                           |            |P  +=============================================================================+        11.3.3 Mode parameterss  tE  This subclause defines the descriptors and pages for mode parametersc  used with printer devices.    F  The mode parameter list, including the mode parameter header and mode*  block descriptor, are described in 8.3.3.  mE  The medium-type code field is contained in the mode parameter headert:  (see 8.3.3).  This field is reserved for printer devices.   G  The device-specific parameter field is contained in the mode parametertE  header (see 8.3.3).  Table 215 defines the device-specific parameter   used for printer devices. e  t>                  Table 215 - Printer device-specific parameterP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |=====+========+==========================+===================================|P  |     |   WP   |      Buffered mode       |            Reserved               |P  +=============================================================================+  t  eF  When using the MODE SELECT command, a buffered mode of zero indicatesD  that the target shall not report a GOOD status on PRINT commands or@  SLEW AND PRINT commands until the data are actually printed.  AH  buffered mode of one indicates that the target may report a GOOD statusF  on PRINT commands or SLEW AND PRINT commands as soon as the data haveG  been transferred to the SCSI device buffer.  The data from one or more B  commands may be buffered prior to printing.  Buffered modes of 2h  through 7h are reserved.    G  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 blockH  descriptor (see table 93).  This field is reserved for printer devices.  1@  The mode page codes for printer devices are shown in table 216.  h5                           Table 216 - Mode page codes-P  +=============-==================================================-============+P  |  Page code  |  Description                                     |  Subclause |P  |-------------+--------------------------------------------------+------------|P  |     0Ah     |  Control mode page                               |  8.3.3.1   |P  |     02h     |  Disconnect-reconnect page                       |  8.3.3.2   |P  |     03h     |  Parallel printer interface page                 | 11.3.3.1   |P  |     09h     |  Peripheral device page                          |  8.3.3.3   |P  |     05h     |  Printer options page                            | 11.3.3.2   |P  |     04h     |  Serial printer interface page                   | 11.3.3.3   |P  |     01h     |  Reserved                                        |            |P  |  06h - 08h  |  Reserved                                        |            |P  |  0Bh - 1Fh  |  Reserved                                        |            |P  |     00h     |  Vendor-specific (does not require page format)  |            |P  |  20h - 3Eh  |  Vendor-specific (page format required)          |            |P  |     3Fh     |  Return all pages                                |            |P  |             |     (valid only for the MODE SENSE command)      |            |P  +=============================================================================+  c  a'  11.3.3 Parallel printer interface page   gC  The parallel printer interface page (see table 217) is intended tohD  support printer devices that use the industry-standard line printer  interface.T   ;                      Table 217 - Parallel printer interface P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+========+========+=====================================================|P  | 0   |   PS   |Reserved|            Page code (03h)                          |P  |-----+-----------------------------------------------------------------------|P  | 1   |                           Parameter length (03h)                      |P  |-----+-----------------------------------------------------------------------|P  | 2   |  Parity select  |  PIPC  |Reserved|  VCBP  |  VCBS  |  VES   | Autofd |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  +=============================================================================+  -  -A  The parameters savable (PS) bit is only used with the MODE SENSE G  command.  This bit is reserved with the MODE SELECT command.  A PS bit+D  of one indicates that the target is capable of saving the page in a(  non-volatile, vendor-specific location.  eC  The parity select field specifies parity generation on the printer-#  interface is defined in table 218.-  -4                            Table 218 - Parity select$  +========-========================+$  |  Code  |  Parity select         |$  |--------+------------------------|$  |   00b  |  No parity generation  |$  |   01b  |  Even parity           |$  |   10b  |  Odd parity            |$  |   11b  |  Reserved              |$  +=================================+  E  EF  A paper instruction parity check (PIPC) bit of one indicates that theA  printer interface Paper Instruction signal is included in paritymG  generation on the printer interface by the target.  A PIPC bit of zerooF  indicates that the Paper Instruction signal is not included in parity3  generation on the printer interface by the target.a  i	     NOTESeM     164 The format of the vertical forms unit (VFU) control byte is specifiedmN     by the VCBP, VCBS, and VES bits.  The VFU control byte is not part of thisG     standard; however, a discussion of it is included here for a bettercG     understanding.  This VFU control byte (see table, below) includes a J     control bit (C) to select whether to slew over a number of lines or toH     skip to a vertical forms unit (VFU) channel number.  This bit may beJ     located in two different bit positions and may have either polarity.  M     165 The number of lines to slew over may be coded as an unsigned four-bit|M     number (NNNN) or an unsigned six-bit number (EENNNN).  The upper two bits L     of the six-bit number (EE) may be positioned contiguously with the lowerM     four bits (NNNN) or they may be separated from the lower four bits by the G     control bit (C).  Furthermore, the upper two bits may or may not be-     supported.M     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.   6                           Table 219 - VFU control byteI  +=======================-==============================================+-I  |   VFU control byte    |  Description                                 | I  |-----------------------|                                              |-I  | Bits 7 6 5 4 3 2 1 0  |                                              | I  |-----------------------+----------------------------------------------|-I  |      0 E E C N N N N  |  Advance (EE)NNNN lines   (C = line skip)    |nI  |      0 0 0 C N N N N  |  Skip to VFU channel NNNN (C = VFU channel)  |=I  |      0 C E E N N N N  |  Advance (EE)NNNN lines   (C = line skip)    |dI  |      0 C 0 0 N N N N  |  Skip to VFU channel NNNN (C = VFU channel)  |tI  |----------------------------------------------------------------------|(I  | Key:  C = VFU control bit                                            |iI  +======================================================================+p  t  eD  A VFU control bit polarity (VCBP) bit of one indicates that the VFUG  control bit (C) is true for a VFU channel command and false for a linehD  skip command.  A VCBP bit of zero indicates the opposite polarity.    F  A VFU control bit select (VCBS) bit of one indicates that the controlH  bit (C) is in bit position 6 and the EE bits are in bit positions 5 andD  4.  A VCBS bit of zero indicates that the control bit (C) is in bit9  position 4 and the EE bits are in bit positions 6 and 5.   eD  A VFU extended skip (VES) bit of one indicates that the EE bits areF  supported for line skip operations.  A VES bit of zero indicates that  the EE bits are not supported.-  -F  For MODE SELECT, an automatic line feed (Autofd) bit of one specifiesH  that the target assert the printer interface Auto Line Feed signal.  An@  Autofd bit of zero specifies that the target negate the printerC  interface Auto Line Feed signal.  For MODE SENSE, the target shall &  return the current value of this bit.  0  11.3.3.2 Printer options page   H  The printer options page (see table 220) supports control and reporting*  of various target functions and features.   5                           Table 220 - Printer optionsiP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+========+========+=====================================================|P  | 0   |   PS   |Reserved|            Page code (05h)                          |P  |-----+-----------------------------------------------------------------------|P  | 1   |                           Parameter length (0Ah)                      |P  |-----+-----------------------------------------------------------------------|P  | 2   |  EVFU  |                  Font identification                         |P  |-----+-----------------------------------------------------------------------|P  | 3   |     Reserved    |    Slew mode    |    Reserved     |  SCTE  |  AFC   |P  |-----+-----------------------------------------------------------------------|P  | 4   | (MSB)                                                                 |P  |-----+---                        Maximum line length                      ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           EVFU format start character                 |P  |-----+-----------------------------------------------------------------------|P  | 7   |                           EVFU format stop character                  |P  |-----+-----------------------------------------------------------------------|P  | 8   |  Line slew options                |  Form slew options                |P  |-----+-----------------------------------+-----------------------------------|P  | 9   |  Data termination options         |         Reserved                  |P  |-----+-----------------------------------------------------------------------|P  | 10  |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 11  |                           Reserved                                    |P  +=============================================================================+  f  eA  The parameters savable (PS) bit is only used with the MODE SENSEsG  command.  This bit is reserved with the MODE SELECT command.  A PS bitcD  of one indicates that the target is capable of saving the page in a'  non-volatile vendor-specific location.s   E  An electronic vertical forms unit (EVFU) bit of one indicates that atA  tape or electronic vertical forms unit is present in the printereD  device.  An EVFU bit of zero indicates that the electronic verticalE  forms unit should not be used or that the unit is not present in thel  printer device.    tE  For the MODE SELECT command, the font identification field specifies B  which font is to be used.  For the MODE SENSE command, this fieldG  identifies the currently selected font.  The font identification codesc  are defined table 221..  h7                         Table 221 - Font identification )  +=============-========================+=)  |    Code     |  Font identification   |a)  |-------------+------------------------| )  |     00h     |  Default font          |-)  |  01h - 3Fh  |  Reserved              |-)  |  40h - 7Fh  |  Vendor-specific font  | )  +======================================+      8G  For the MODE SELECT command, the slew mode field controls the target's F  behavior when a SLEW AND PRINT command is received with a channel bitF  of zero (see 11.2.4).  For the MODE SENSE command, this field reports@  the current slew mode.  This slew mode is defined in table 222.  i2                              Table 222 - Slew modeP  +========-====================================================================+P  |  Code  |  Slew mode                                                         |P  |--------+--------------------------------------------------------------------|P  |   00b  |  SLEW AND PRINT commands with a channel bit of zero are supported  |P  |        |  without any required setup.                                       |P  |        |                                                                    |P  |   01b  |  SLEW AND PRINT commands with a channel bit of zero are only       |P  |        |  accepted after the initiator issues a FORMAT command with a format|P  |        |  type of set form (to initialize the electronic vertical forms     |P  |        |  unit).                                                            |P  |        |                                                                    |P  |   10b  |  SLEW AND PRINT commands with a channel bit of zero are always     |P  |        |  accepted.  The target shall use the electronic vertical forms unit|P  |        |  if it has previously been initialized or it shall initialize the  |P  |        |  electronic vertical forms unit for line skipping by sending the   |P  |        |  EVFU start format character immediately followed by the EVFU stop |P  |        |  format character (both are defined below) prior to executing the  |P  |        |  SLEW AND PRINT command.                                           |P  |        |                                                                    |P  |   11b  |  Reserved                                                          |P  +=============================================================================+  B  |H  For the MODE SELECT command, a step count truncate enable (SCTE) bit ofF  one indicates that the target shall assume the printer truncates slewH  values in SLEW AND PRINT commands, so that the data prints on the firstE  line of the next form.  A SCTE bit of zero indicates that the targetaD  shall assume the printer continues to slew over forms boundaries in@  SLEW AND PRINT commands if the slew value exceeds the number ofB  remaining lines on the current form.  The target shall return the4  current value of this field in the MODE SENSE data.  eC  An ASCII forms control (AFC) bit of one indicates that the printer G  supports ASCII forms control characters.  An AFC bit of zero indicates B  that the printer does not support ASCII forms control characters.   D  The maximum line length field specifies the maximum transfer lengthH  (maximum number of bytes per line) to be accepted in the SLEW AND PRINTD  command.  A value of 0000h in MODE SELECT specifies that the targetG  shall use its default value.  In any case, the target shall report its 1  actual value in the MODE SENSE data (not 0000h).s  cF  The EVFU format start character field specifies the character code toD  be used by the target to start the initialization of the electronic:  vertical forms unit, if slew mode option 10b is selected.  tH  The EVFU format stop character field specifies the character code to be@  used by the target to stop the initialization of the electronic:  vertical forms unit, if slew mode option 10b is selected.  sE  The line slew options field specifies the implementation of the lineeB  slew (using ASCII forms control characters) in the SLEW AND PRINT>  command.  Code values in this field are defined in table 223.  e2                              Table 223 - Line slewP  +=========-===================================================================+P  |   Code  |  Line slew option                                                 |P  |---------+-------------------------------------------------------------------|P  |    0h   |  Not implemented.  (SLEW AND PRINT commands cause CHECK CONDITION |P  |         |  status with ILLEGAL REQUEST sense key.)                          |P  |         |                                                                   |P  |    1h   |  The target shall insert an ASCII carriage return character (0Dh) |P  |         |  for each line to slew over.                                      |P  |         |                                                                   |P  |    2h   |  The target shall insert an ASCII line feed character (0Ah) for   |P  |         |  each line to slew over.                                          |P  |         |                                                                   |P  |    3h   |  The target shall insert an ASCII carriage return character (0Dh) |P  |         |  and line feed character (0Ah) for each line to slew over.        |P  |         |                                                                   |P  | 4h - 7h |  Reserved                                                         |P  |         |                                                                   |P  | 8h - Fh |  Vendor-specific                                                  |P  +=============================================================================+      A  The form slew options field specifies the implementation of form=F  slewing in the SLEW AND PRINT command.  Code values in this field are  defined in table 224.  i2                              Table 224 - Form slewP  +=========-===================================================================+P  |   Code  |  Form slew option                                                 |P  |---------+-------------------------------------------------------------------|P  |    0h   |  Not implemented.  (SLEW AND PRINT commands cause CHECK CONDITION |P  |         |  status with ILLEGAL REQUEST sense key.)                          |P  |         |                                                                   |P  |    1h   |  The target shall insert an ASCII form feed character (0Ch) to    |P  |         |  move to the beginning of the next form.                          |P  |         |                                                                   |P  |    2h   |  The target shall insert an ASCII carriage return character (0Dh) |P  |         |  and form feed character (0Ch) to move to the beginning of the    |P  |         |  next form.                                                       |P  |         |                                                                   |P  | 3h - 7h |  Reserved                                                         |P  |         |                                                                   |P  | 8h - Fh |  Vendor-specific                                                  |P  +=============================================================================+  =  =F  The data termination options field specifies the termination sequenceH  to be issued to the printer device when a SYNCHRONIZE BUFFER command is@  received.  Code values for this field are defined in table 225.   9                       Table 225 - Data termination option P  +=========-===================================================================+P  |   Code  |  Line slew option                                                 |P  |---------+-------------------------------------------------------------------|P  |    0h   |  Selects the target default implementation (MODE SELECT).         |P  |         |                                                                   |P  |    1h   |  No termination sequence.  (The target sends any remaining data   |P  |         |  in its buffer to the printer device with no termination sequence |P  |         |                                                                   |P  |    2h   |  The target shall print any buffered data followed by an ASCII    |P  |         |  carriage return character (0Dh).                                 |P  |         |                                                                   |P  |    3h   |  The target shall print any buffered data followed by an ASCII    |P  |         |  line feed character (0Ah).                                       |P  |         |                                                                   |P  |    4h   |  The target shall print any buffered data followed by an ASCII    |P  |         |  carriage return, line feed character sequence (0Dh, 0Ah).        |P  |         |                                                                   |P  |    5h   |  The target shall send any buffered data followed by an ASCII     |P  |         |  form feed character (0Ch).                                       |P  |         |                                                                   |P  |    6h   |  The target shall print any buffered data followed by an ASCII    |P  |         |  carriage return, form feed character sequence (0Dh, 0Ch).        |P  |         |                                                                   |P  |    7h   |  The target shall issue a zero line slew command to the printer   |P  |         |  device.                                                          |P  |         |                                                                   |P  | 8h - Bh |  Reserved                                                         |P  |         |                                                                   |P  | Ch - Fh |  Vendor-specific                                                  |P  +=============================================================================+  u  n'  11.3.3.3 Serial printer interface pageo  oA  The serial printer interface page (see table 226) is intended to2H  support printer devices that use the industry-standard serial interface$  usually referred to as EIA RS-232C.  |:                       Table 226 - Serial printer interfaceP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+========+========+=====================================================|P  | 0   |   PS   |Reserved|            Page code (04h)                          |P  |-----+-----------------------------------------------------------------------|P  | 1   |                           Parameter length (06h)                      |P  |-----+-----------------------------------------------------------------------|P  | 2   |     Reserved    |         Stop bit length                             |P  |-----+-----------------------------------------------------------------------|P  | 3   |     Parity selection     |Reserved|        Bits per character         |P  |-----+-----------------------------------+-----------------------------------|P  | 4   |  RTS   |  CTS   |     Reserved    |        Pacing protocol            |P  |-----+-----------------------------------------------------------------------|P  | 5   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 6   |                           Baud rate                                   |P  |-----+---                                                                 ---|P  | 7   |                                                                 (LSB) |P  +=============================================================================+  z  hA  The parameters savable (PS) bit is only used with the MODE SENSE G  command.  This bit is reserved with the MODE SELECT command.  A PS bitfD  of one indicates that the target is capable of saving the page in a'  non-volatile vendor-specific location.|   E  The stop bit length field specifies the length of the stop bit(s) in D  units of 1/16 bit.  The target may round this field as described inG  7.5.4.  A stop bit length of zero in the MODE SELECT command indicates -  that the target shall use its default value.=  =G  The parity selection field specifies parity generation and checking asD  defined in table 227.  u6                           Table 227 - Parity selection  +========-===================+   |  Code  |  Parity selection |N  |--------+-------------------|a  |  000b  |  None             |e  |  001b  |  Mark             |n  |  010b  |  Space            |a  |  011b  |  Odd              |e  |  100b  |  Even             |   |  101b  |  Reserved         |l  |  110b  |  Reserved         |i  |  111b  |  Reserved         |e  +============================+t  l  oB  The bits per character field specifies the number of bits in eachF  character.  A value of zero in the MODE SELECT command indicates that1  the target shall use its default character size.    @  For the MODE SELECT command, a request to send (RTS) bit of oneH  specifies that the target shall insure the Request to Send (RTS) signalD  in the serial interface follows the line state of the Data Terminal?  Ready (DTR) signal in the serial interface.  A RTS bit of zero H  specifies that the target shall set the Request to Send (RTS) signal toG  high whenever the target power is on.  For the MODE SENSE command, thes5  target shall report the current value of this field.b  sH  For the MODE SELECT command, a clear to send (CTS) bit of one specifiesD  that the target shall delay data transmission to the printer deviceG  until the printer device asserts the Clear to Send (CTS) signal in therE  serial interface.  A CTS bit of zero indicates that the target shall B  ignore the Clear to Send signal.  For the MODE SENSE command, the5  target shall report the current value of this field.i  AH  The code values for the pacing protocol field are defined in table 228.  i5                           Table 228 - Pacing protocol   +=========-==================+   |   Code  |  Pacing protocol |=  |---------+------------------|=  |    0h   |  None            |   |    1h   |  XON/XOFF        |   |    2h   |  ETX/ACK         |   |    3h   |  DTR             |-  | 4h - 7h |  Reserved        |-  | 8h - Fh |  Vendor-specific |m  +============================+n  c  eE  The baud rate field specifies the baud rate in bits per second.  The.H  target may round this value as described in 7.5.4.  A baud rate of zeroC  in the MODE SELECT command specifies that the target shall use itsi  default baud rate.g  e  n  12 Processor devices      |!  12.1 Model for processor devices    D  The SCSI processor device is a target with the characteristics of aG  primary computing device, typically a personal computer, minicomputer,iE  mainframe computer, or auxiliary computing device or server.  Such anG  primary computing device is often called a host.  The processor device D  receives or provides packets of data as requested by the initiator.   G  In the SCSI processor device, the target accepts and provides the data|E  packets transferred according to the commands of the initiator.  TherF  initiator and the processor device are both assumed to know the rulesG  by which information is exchanged between them, how the information is A  interpreted by the processor device, and when it is allowable to A  exchange the information.  These rules are not specified by thise  International Standard.   D  The initiator requests that the processor device accept a packet ofF  data by transmitting a SEND command.  The initiator requests that theC  processor device return a packet of data by transmitting a RECEIVEPB  command.  A COPY command can also be transmitted to the processorD  device to request that it serve as a copy manager.  The actual dataH  flow can be between the processor device and another SCSI device or canB  be between two SCSI devices under control of the processor device  acting as a copy manager.  -H  If a processor device temporarily has no resource available to manage aE  data packet from the initiator, has no data packet to provide to the F  initiator, or has no resources assigned to perform the operation, the8  device may then choose one of the following responses: J     a)     Terminate the command with CHECK CONDITION status and the senseK            key NOT READY with the appropriate additional sense code for theeL            condition.  This is the appropriate response to a TEST UNIT READY            command. I     b)     Disconnect until the necessary resource or data packet becomesgH            available, and then reconnect to the initiator and resume the            operation.o2     c)     Terminate the command with BUSY status.   G  More than one logical unit can be implemented by a processor device.   B  Logical units can serve as additional paths to a single resource,D  and/or each logical unit can serve as a path to different resourcesF  within the device.  A single logical unit may also serve as a path toE  multiple resources if the processor device can interpret information ?  within the data packet and route the packet to the appropriate=H  resource.  If the logical unit addressed by the initiator does not haveG  an available resource or data packet associated with it, the processoraG  device may choose to treat the logical unit as an invalid logical unite?  (see 7.5.3) or respond as described in the previous paragraph.a  rF  If the processor device determines that an error or unusual conditionH  has occurred while performing an operation specified by the contents ofD  a data packet, the information describing the condition is normally>  returned as a part of a data packet.  If the processor deviceA  determines that an error or unusual condition has occurred while|>  executing the SCSI command from the initiator, the command isB  terminated with a CHECK CONDITION and the failures are identified!  through a REQUEST SENSE command.    F  The SCSI processor device is distinguished from a SCSI communicationsG  device by the fact that the primary destination of the data packets is F  within the target device.  A SCSI communications device, in contrast,A  passes the data on to an ultimate destination outside the target D  through a network.  Many types of devices may find it convenient toD  function as processor devices if no other suitable SCSI device typeE  exists and if the packet exchange protocol dictated by the processoriE  device model meets their functional requirements.  Devices requiring C  totally incompatible protocols and command sets should be examined G  carefully to ensure that the incompatibilities are based on functionalaE  requirements.  If  they are, they should be treated as vendor-uniquec  device types.   E  Several examples of processor device implementations are provided to ;  clarify the range of utility of the SCSI processor device.d  t-  12.1.1 Host-to-host communication, SEND onlym  e@  A host system, (host A), takes the initiator role and selects aE  processor device (host B), transmitting a packet to host B using the G  SEND command.  The SEND command contains an operating system call that H  requests data from the local storage devices attached to host B.  AfterE  performing the functions required by the data packet, Host B assumes G  the initiator mode and selects host A as a processor device and uses a D  SEND command to transmit the requested data back to host A.  Host AF  thus acts as a primary computer and host B acts as a specialized dataH  server computer.  Note that the SEND command is sufficient to perform aH  complete transaction if both host A and host B are capable of acting asE  initiators.  This provides the capability of a high bandwidth inter- ,  communication among nearby host processors.   4  12.1.2 Host-to-host communication, SEND and RECEIVE  =H  A host system (host A) takes the initiator role and selects a processorH  device (host B), transmitting a packet using the SEND command to host BD  containing instructions about an operation to be performed.  Host AG  again takes the initiator role and sends the data to be used by host B.F  in the operation.  Host A then assumes that a result will be obtainedF  consistent with rules understood by both devices.  Host A generates aH  RECEIVE command to obtain the result from host B.  If the result is notG  yet ready, host B may disconnect until the calculation is complete and|7  the requested data packet can be returned to host A.  =  =L     NOTE 168 Host A need not support target mode and host B need not supportG     initiator mode to successfully complete an exchange between the two-     devices.  -)  12.1.3 Host-to-special-output peripheral    A  A special co-processor device which can use the processor device B  command set is a high-performance graphics display terminal.  TheG  initiator sends to the display terminal control and data packets  that H  contain the image to be displayed.  Only the SEND command is required. B  A peripheral failure should be indicated through the normal CHECK%  CONDITION / REQUEST SENSE protocol.     (  12.1.4 Host-to-special-input peripheral  -G  A second special co-processor device that can use the processor deviceeB  command set is a data acquisition subsystem.  Such subsystems mayG  multiplex and compact streams of data from many sources.  A host could H  control the data acquisition modes and the selection of data streams byD  transmitting control packets to the processor device using the SENDF  command.  The host could then obtain the acquired data by executing aD  series of RECEIVE commands.  The data acquisition device could alsoH  serve as an initiator, selecting peripheral storage devices and storingH  the compacted acquired data there for later access directly by the hostG  or through host to host communication protocols.  A peripheral failure F  would be indicated through the normal CHECK CONDITION / REQUEST SENSE
  protocol.  D$  12.2 Commands for processor devices  iC  The commands for processor devices shall be as shown in table 229.l  e=                    Table 229 - Commands for processor devicesiI  +=====================================-============-======-============+oI  |  Command name                       | Operation  | Type |  Subclause |OI  |                                     |   code     |      |            |=I  |-------------------------------------+------------+------+------------|aI  | CHANGE DEFINITION                   |    40h     |   O  |   8.2.1    |yI  | COMPARE                             |    39h     |   O  |   8.2.2    | I  | COPY                                |    18h     |   O  |   8.2.3    | I  | COPY AND VERIFY                     |    3Ah     |   O  |   8.2.4    | I  | INQUIRY                             |    12h     |   M  |   8.2.5    |eI  | LOG SELECT                          |    4Ch     |   O  |   8.2.6    | I  | LOG SENSE                           |    4Dh     |   O  |   8.2.7    |lI  | READ BUFFER                         |    3Ch     |   O  |   8.2.12   | I  | RECEIVE                             |    08h     |   O  |  12.2.1    |cI  | RECEIVE DIAGNOSTIC RESULTS          |    1Ch     |   O  |   8.2.13   |fI  | REQUEST SENSE                       |    03h     |   M  |   8.2.14   |nI  | SEND                                |    0Ah     |   M  |  12.2.2    |RI  | SEND DIAGNOSTIC                     |    1Dh     |   M  |   8.2.15   |tI  | TEST UNIT READY                     |    00h     |   M  |   8.2.16   |rI  | WRITE BUFFER                        |    3Bh     |   O  |   8.2.17   |eI  |----------------------------------------------------------------------| I  |Key:  M = command implementation is mandatory.                        | I  |      O = command implementation is optional.                         |lI  +======================================================================+i  e  hG  The following operation codes are vendor-specific: 02h, 05h, 06h, 09h,SC  0Ch, 0Dh, 0Eh, 0Fh, 10h, 11h, 13h, 14h, 19h, C0h through FFh.  AlliH  remaining operation codes for processor devices are reserved for future  standardization.      12.2.1 RECEIVE commanda  gF  The RECEIVE command (see table 230) requests that the target transferD  data to the initiator.  The contents of the data are not defined by  this International Standard.    5                           Table 230 - RECEIVE command P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (08h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |                  Reserved                  |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                           Allocation length                           |P  |-----+---                                                                 ---|P  | 4   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+     e  12.2.2 SEND command  tH  The SEND command (see table 231) requests that the target transfer data  from the initiator.  d4                             Table 231 - SEND commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (0Ah)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |                  Reserved         |  AEN   |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                           Transfer length                             |P  |-----+---                                                                 ---|P  | 4   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+  e   G  An asynchronous event notification (AEN) bit of one indicates that thenG  data to be transferred conforms to AEN data format as defined in tabletD  232.  A SEND command with an AEN bit of one shall be only issued to  logical unit zero.   o=                    Table 232 - SEND command - AEN data format P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=================+========+=================+==========================|P  | 0   |     Reserved    | LUNTAR |     Reserved    |          LUNTRN          |P  |-----+-----------------------------------------------------------------------|P  | 1   |                               Reserved                                |P  |-----+-----------------------------------------------------------------------|P  | 2   |                               Reserved                                |P  |-----+-----------------------------------------------------------------------|P  | 3   |                               Reserved                                |P  |-----+-----------------------------------------------------------------------|P  | 4   |                               Sense data byte (0)                     |P  |- - -+---                                                                 ---|P  | n+4 |                               Sense data byte (n)                     |P  +=============================================================================+  e  aA  An AEN bit of zero indicates that the data to be transferred aref  vendor-specific.o   H  The transfer length specifies the length in bytes of data that shall beE  sent during the DATA OUT phase.  A transfer length of zero indicatestG  that no data shall be sent.  This condition shall not be considered ani  error.o  m>  A logical unit target (LUNTAR) bit of zero specifies that theD  asynchronous event occurred on a logical unit.  A LUNTAR bit of oneD  specifies that the asynchronous event occurred on a target routine.  aB  If the LUNTAR bit is zero, the logical unit number target routine>  number (LUNTRN) field specifies the logical unit on which theC  asynchronous event occurred.  If the LUNTAR bit is one, the LUNTRNr?  field specifies on the routine on which the asynchronous evente
  occurred.  h.  The sense data bytes are defined in table 65.  d&  12.3 Parameters for processor devices     p  12.3.1 Diagnostic parametersn  s@  This subclause defines the descriptors and pages for diagnostic)  parameters used with processor devices. r   E  The diagnostic page codes for processor devices are defined in tablen  233.n  b8                        Table 233 - Diagnostic page codesP  +=============-==================================================-============+P  |  Page code  |  Description                                     | Subclause  |P  |-------------+--------------------------------------------------+------------|P  |     00h     |  List of supported parameters page               |  8.3.1.1   |P  |  01h - 3Fh  |  Reserved (for all device type pages)            |            |P  |  40h - 7Fh  |  Reserved                                        |            |P  |  80h - FFh  |  Vendor-specific pages                           |            |P  +=============================================================================+  A  =  12.3.2 Log parameters  eD  This subclause defines the descriptors and pages for log parameters  used with processor devices.n  cC  The log page codes for processor devices are defined in table 234.p  p5                            Table 234 - Log page codesnP  +=============-==================================================-============+P  |  Page code  |  Description                                     |  Subclause |P  |-------------+--------------------------------------------------+------------|P  |     01h     |  Buffer over-run/under-run page                  |  8.3.2.1   |P  |     07h     |  Last n error events page                        |  8.3.2.3   |P  |     00h     |  List of supported parameters page               |  8.3.2.5   |P  |     06h     |  Non-medium error page                           |  8.3.2.4   |P  |  02h - 05h  |  Reserved                                        |            |P  |  08h - 2Fh  |  Reserved                                        |            |P  |  30h - 3Eh  |  Vendor-specific pages                           |            |P  |     3Fh     |  Reserved                                        |            |P  +=============================================================================+  a  d/  12.4 Definitions specific to processor devices    G  12.4.1 host:  A device with the characteristics of a primary computinglB  device, typically a personal computer, workstation, minicomputer,=  mainframe computer, or auxiliary computing device or server.    H  12.4.2 data packet:  The data transferred during the DATA IN phase of aH  RECEIVE command, or during the DATA OUT phase of a SEND command. A dataH  packet often contains information at the beginning or end of the packetG  that describes the contents of the packet. A data packet might contain :  control or status information for the destination device.   G  12.4.3 resource:  A part of the device required to operate on or store-  the data packet.E  I  N  13 Write-once devices      "  13.1 Model for write-once devices   B  The model for the write-once device is a variation on the opticalF  memory model.  Most of the aspects of a write-once device are similarC  to optical memory devices.  The differences are summarized in this   clause.     13.1.1 Logical blocks  |F  Data may be written to a logical block only once.  A subsequent write@  to a logical block already written may or may not be corrupted,D  depending on the implementation.  Write-once physical media is non-
  volatile.   C  The updating of blocks (see 16.1) is discouraged.  SCSI write-once H  devices are intended to be archival in nature.  Data at a logical blockB  address is not expected to change once it is written.  The update@  commands are not defined for this device type.  Devices are notB  precluded from implementing the update function by this standard,G  though devices that require the update function should use the optical   memory device type.   G  Devices may be able to determine the state of a logical block prior to A  access.  These devices can determine whether a block is blank or-D  written. This is useful in detecting previously written blocks, andD  preventing a destructive overwrite.  This is also useful in findingG  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  gG  The FORMAT UNIT command is not defined for write-once devices.  Write-hE  once media is shipped pre-formatted by the manufacturer and is readya  for use when mounted.  v  13.1.3 Physical medium defectsa  rD  The raw defect rate is typically higher for optical medium than for?  magnetic medium.  Data is usually recovered through the use ofi?  sophisticated error correction algorithms.  The level of errortF  correction used for data recovery is often can be selected.  However,E  many write-once devices have a minimum level that is always used and=B  cannot be de-selected through the error recovery mode parameter. F  Control of the error correction algorithms and level of correction is  vendor-specific.|   E  Defect management on write-once devices is usually vendor-specific. =E  However, there are standards for some types of write-once media thatcC  specify defect management techniques.  These standards, where they-C  exist, may supersede the implementation requirements pertaining to ;  error and defect reporting in this International Standard.|  -  13.1.4 Error reporting-  -C  If any of the following conditions occur during the execution of a =  command the target shall return CHECK CONDITION status.  The-D  appropriate sense key and additional sense code should be set.  TheD  following list illustrates some error conditions and the applicableH  sense keys.  The list does not provide an exhaustive enumeration of all6  conditions that may cause the CHECK CONDITION status.   c  Condition                                                                                Sense Key-o  Invalid logical block address                                                                          ILLEGAL=  REQUEST  =k  Unsupported option requested                                                                       ILLEGALo  REQUEST  b|  Target reset or medium change since last command from this initiator                                                            UNIT ATTENTION  =p  Self diagnostic failed                                                                                 HARDWARE  ERROR  1p  Unrecovered read error                                                                             MEDIUM ERRORa                                                                                    HARDWARE ERROR   ep  Recovered read error                                                                            RECOVERED ERROR  -{  Overrun or other error that might be resolved by repeating the command                                                    -  ABORTED command  -r  Attempt to write on write protected medium                                                                   DATA  PROTECT   u  Attempt to read a blank or previously unwritten block                                                                  BLANK CHECK  |B  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 dataC  information field shall be set to the logical block address of the-  first invalid address.    B  In the case of an attempt to read a blank or previously unwrittenD  block, the sense data information field shall be set to the logicalF  block address of the first blank block encountered.  The data read up$  to that block shall be transferred.  sH  In the case of an attempt to write a previously written block and blankE  checking is enabled, the sense information field shall be set to the @  logical block address of the first non-blank block encountered.  =%  13.2 Commands for write-once devices=  =D  The commands for write-once devices shall be as shown in table 235.   =                   Table 235 - Commands for write-once devices I  +=====================================-============-======-============++I  |  Command name                       | Operation  | Type |  Subclause |eI  |                                     |   code     |      |            |-I  |-------------------------------------+------------+------+------------||I  | CHANGE DEFINITION                   |    40h     |   O  |   8.2.1    ||I  | COMPARE                             |    39h     |   O  |   8.2.2    |-I  | COPY                                |    18h     |   O  |   8.2.3    | I  | COPY AND VERIFY                     |    3Ah     |   O  |   8.2.4    |-I  | INQUIRY                             |    12h     |   M  |   8.2.5    | I  | LOCK UNLOCK CACHE                   |    36h     |   O  |   9.2.2    |-I  | LOG SELECT                          |    4Ch     |   O  |   8.2.6    |tI  | LOG SENSE                           |    4Dh     |   O  |   8.2.7    | I  | MEDIUM SCAN                         |    38h     |   O  |  16.2.3    | I  | MODE SELECT(6)                      |    15h     |   O  |   8.2.8    |=I  | MODE SELECT(10)                     |    55h     |   O  |   8.2.9    |zI  | MODE SENSE(6)                       |    1Ah     |   O  |   8.2.10   | I  | MODE SENSE(10)                      |    5Ah     |   O  |   8.2.11   |sI  | PRE-FETCH                           |    34h     |   O  |   9.2.3    | I  | PREVENT ALLOW MEDIUM REMOVAL        |    1Eh     |   O  |   9.2.4    |oI  | READ(6)                             |    08h     |   O  |   9.2.5    |cI  | READ(10)                            |    28h     |   M  |   9.2.6    |tI  | READ(12)                            |    A8h     |   O  |  16.2.4    |RI  | READ BUFFER                         |    3Ch     |   O  |   8.2.12   |dI  | READ CAPACITY                       |    25h     |   M  |   9.2.7    | I  | READ LONG                           |    3Eh     |   O  |   9.2.9    |hI  | REASSIGN BLOCKS                     |    07h     |   O  |   9.2.10   | I  | RECEIVE DIAGNOSTIC RESULTS          |    1Ch     |   O  |   8.2.13   |iI  | RELEASE                             |    17h     |   M  |   9.2.11   | I  | REQUEST SENSE                       |    03h     |   M  |   8.2.14   |sI  | RESERVE                             |    16h     |   M  |   9.2.12   | I  | REZERO UNIT                         |    01h     |   O  |   9.2.13   |=I  | SEARCH DATA EQUAL(10)               |    31h     |   O  |   9.2.14.1 ||I  | SEARCH DATA EQUAL(12)               |    B1h     |   O  |  16.2.8    |-I  | SEARCH DATA HIGH(10)                |    30h     |   O  |   9.2.14.2 | I  | SEARCH DATA HIGH(12)                |    B0h     |   O  |  16.2.8    ||I  | SEARCH DATA LOW(10)                 |    32h     |   O  |   9.2.14.3 | I  | SEARCH DATA LOW(12)                 |    B2h     |   O  |  16.2.8    | I  | SEEK(6)                             |    0Bh     |   O  |   9.2.15   | I  | SEEK(10)                            |    2Bh     |   O  |   9.2.15   |=I  | SEND DIAGNOSTIC                     |    1Dh     |   M  |   8.2.15   |sI  | SET LIMITS(10)                      |    33h     |   O  |   9.2.16   |rI  | SET LIMITS(12)                      |    B3h     |   O  |  16.2.9    |bI  | START STOP UNIT                     |    1Bh     |   O  |   9.2.17   |=I  | SYNCHRONIZE CACHE                   |    35h     |   O  |   9.2.18   | I  | TEST UNIT READY                     |    00h     |   M  |   8.2.16   |uI  | VERIFY(10)                          |    2Fh     |   O  |  16.2.11   |-I  | VERIFY(12)                          |    AFh     |   O  |  16.2.12   | I  | WRITE(6)                            |    0Ah     |   O  |   9.2.20   | I  | WRITE(10)                           |    2Ah     |   M  |   9.2.21   | I  | WRITE(12)                           |    AAh     |   O  |  16.2.14   | I  | WRITE AND VERIFY(10)                |    2Eh     |   O  |   9.2.22   | I  | WRITE AND VERIFY(12)                |    AEh     |   O  |  16.2.16   | I  | WRITE BUFFER                        |    3Bh     |   O  |   8.2.17   |eI  | WRITE LONG                          |    3Fh     |   O  |   9.2.23   |eI  |----------------------------------------------------------------------|=I  |Key:  M = command implementation is mandatory.                        |1I  |      O = command implementation is optional.                         | I  +======================================================================+o     pF  The following command codes are vendor-specific:  02h, 05h, 06h, 09h,F  0Ch, 0Dh, 0Eh, 0Fh, 10h, 11h, 13h, 14h, 19h, 20h, 21h, 22h, 23h, 24h,E  26h, 27h, 29h, and C0h through FFh.  All remaining command codes forT<  write-once devices are reserved for future standardization.  i'  13.3 Parameters for write-once devices   a?  Refer to the parameters for optical memory devices (see 16.3).i   0  13.4 Definitions specific to write-once devices  v
  See 16.4.  .  e  14 CD-ROM devices  d  c  14.1 Model for CD-ROM devices   G  CD-ROM devices permit reading data from a rotating media.  Writing theoA  media is not supported.  Data transfer can begin with any of the C  consecutively numbered logical blocks.  Data on CD-ROM devices areiG  addressed the same as usual (magnetic) direct-access devices. Some CD-aE  ROM devices support a separate information stream (e.g. audio and/or A  video but referred to as audio in this clause) transmitted via atF  connection other than the SCSI Bus. This device type defines commands2  for controlling these other information streams.    G  CD-ROM drives are designed to work with any disc that meets IEC.  Many C  new drives read CD-ROM data discs, digital audio discs, and audio-tC  combined discs (i.e. some tracks are audio, some tracks are data).r  e!  14.1.1 CD-ROM media organizatione  eB  The formats written on the CD-ROM and CD-DA (Digital Audio) media-  require special interfacing considerations. g  eH     NOTE 169 This subclause contains a number of terms that have specialL     meanings peculiar to CD-ROM technology or that may be unfamiliar to manyL     readers of this International Standard. The glossary (see 14.4.) defines     these terms.  sE  Discs may contain either audio, data or a mixture of the two.  TabletE  236 gives an example of a of a audio-combined disc to illustrate thewF  relationship between the logical block addresses reported in SCSI andF  the MSF address encoded on the media.  The logical addresses given inE  the table assume a block length of 2 048, 2 336 or 2 340 bytes.  ForeD  block lengths of 1 024, 512 or 256 multiply all values given in the0  SCSI address columns by 2, 4 or 8 respectively.  dM     NOTE 170 The term frame is used in two different ways in the CD-ROM mediahL     standard.  The intended meaning can only be determined from the context.N     Whenever possible, this description replaces the larger data unit with theK     more familiar term sector.  The primary exception to this policy is thesL     use of frame when referring to the MSF address.  In the MSF context, oneK     frame (F field unit) equals one sector.  On a typical two channel CD-DAtE     media, each frame (F field unit) is played in 1/75th of a second.e  o  r@                Table 236 - Example mixed mode CD-ROM disc layoutj  +================-==========================-===========================================================+j  |                |      SCSI address        |       /--- Sub-channel information ----\                  |j  |----------------+--------------------------+-----------------------------------------------------------|j  |                |  Logical    |   Track    |    Absolute  |  Track |  Track    |Sector  | Mode  |CD-ROM|j  |                |  address    |  relative  |      MSF     |   and  | relative  |is info | audio |data  |j  |     Block      |  (decimal)  |  logical   |    address1  |  index |   MSF     | or is  |  or   |mode2 |j  |  description   |             |  address   |              |        | address   | pause  | data  |      |j  |----------------+-------------+------------+--------------+--------+-----------+--------+-------+------|j  |Lead-in area3)  |      ---    |    ---     |     ---      |  0/-   |    ---    |  ---   | Audio | ---  |j  |Pre-gap3)       |     ---     |    ---     |  00/00/00    |  1/0   | 00/02/00  | Pause  | Data  | Null |j  |                |             |            |              |        |           |        |       |      |j  |1st track data  |   0 0005)   |       0    |  00/02/004)  |  1/1   | 00/00/00  | Info   | Data  | L-EC |j  |2nd track data  |   6 0005)   |       0    |  01/22/004)  |  2/1   | 00/00/00  | Info   | Data  | L-EC |j  |                |   7 500     |   1 500    |  01/42/00    |  2/2   | 00/20/00  | Info   | Data  | L-EC |j  |                |             |            |              |        |           |        |       |      |j  |Post-gap        |   9 000     |   3 000    |  02/02/00    |  2/3   | 00/40/00  | Pause  | Data  | Null |j  |                |             |            |              |        |           |        |       |      |j  |Pause-silence   |   9 150     |    -1509)  |  02/04/00    |  3/0   | 00/02/008 | Pause  | Audio | ---  |j  |                |             |            |              |        |           |        |       |      |j  |3rd track audio |   9 3007)   |       0    |  02/04/006)  |  3/1   | 00/00/00  | Info   | Audio | ---  |j  |                |  11 400     |   2 250    |  02/34/00    |  3/2   | 00/30/00  | Info   | Audio | ---  |j  |4th track audio |  21 9757)   |       0    |  04/53/006)  |  4/1   | 00/00/00  | Info   | Audio | ---  |j  |                |             |            |              |        |           |        |       |      |j  |Pre-gap part 1  |  30 000     |    -2259)  |  06/40/00    |  5/0   | 00/03/00  | Pause  | Audio | ---  |j  |Pre-gap part 2  |  30 075     |    -150    |  06/41/00    |  5/0   | 00/02/00  | Pause  | Data  | Null |j  |                |             |            |              |        |           |        |       |      |j  |5th track data  |  30 225     |       0    |  06/43/00    |  5/1   | 00/00/00  | Info   | Data  | L-EC |j  |                |             |            |              |        |           |        |       |      |j  |Last information| 263 99910)  | 233 774    |  58/39/74    |  5/1   | 51/56/74  | Info   | Data  | L-EC |j  |                |             |            |              |        |           |        |       |      |j  |Post-gap        |     ---     | 233 775    |  58/40/00    |  5/2   | 51/57/00  | Pause  | Data  | Null |j  |                |             |            |              |        |           |        |       |      |j  |Lead-out track  | 264 00011)  |       0    |  58/42/0012) | AA/13  | 00/00/00  | Pause  | Audio | ---  |j  |-------------------------------------------------------------------------------------------------------|j  |  Notes                                                                                                |j  |  1  Absolute MSF address repeated in the header field of data blocks.                                 |j  |  2  The CD-ROM data mode is stored in the header of data tracks. This indicates that                  |j  |     the block is part of a data pre-gap or post-gap (null), that this is a data                       |j  |     block using the auxiliary field for L-EC symbols (ECC - CD-ROM data mode one),                    |j  |     or that this is a data block using the auxiliary field for user data (CD-ROM                      |j  |     data mode two).                                                                                   |j  |  3  Table of contents information is stored in the sub-channel of lead-in area.  The                  |j  |     lead-in area is coded as track zero. Track zero and the initial 150 sector pre-                   |j  |     -gap (or audio pause) are not accessible with logical addressing.                                 |j  |  4  Value stored in table of contents with zero tolerance.                                            |j  |  5  Exact value returned by READ TOC command.                                                         |j  |  6  Value stored in table of contents plus or minus 75 sectors.                                       |j  |  7  Value returned by READ TOC command plus or minus 75 blocks.                                       |j  |  8  Track relative MSF value decreases to 0 in pre-gap areas.                                         |j  |  9  Track relative logical addresses are negative in the pre-gap areas.                               |j  |     Pre-gap areas have index values of zero.                                                          |j  |  10  Minimum value returned by READ CD-ROM CAPACITY - exact value depends                             |j  |      on encoding of this track and the lead out track and whether this is                             |j  |      derived from the TOC data.                                                                       |j  |  11  Value returned by READ TOC command - exact if lead-out track is                                  |j  |      encoded as data, or plus or minus 75 blocks if encoded as audio.                                 |j  |  12  Value stored in table of contents -  exact if lead-out track is coded                            |j  |      as data, or plus or minus 75 blocks if coded as audio.                                           |j  |  13  Lead-out track number is defined as 0AAh.                                                        |j  +=======================================================================================================+  |  6E  The physical format defined by the CD-ROM media standards provides 2|H  352 bytes per sector. For usual computer data applications, 2 048 bytesF  are used for user data, 12 bytes for a synchronization field, 4 bytesE  for a sector address tag field and 288 bytes - the auxiliary field - B  for L-EC (CD-ROM data mode 1). In less critical applications, theG  auxiliary field may also be used for user data (CD-ROM data mode 2). A|G  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 plusE  auxiliary data, the 4 byte address tag plus user data plus auxiliary-  data.  -H  Selection among these options is made by setting the density code fieldH  of the MODE SELECT block descriptor. The usual selection is 2 048 bytesF  per physical sector via a density code setting of 1. See the table of&  CD-ROM density code values in 14.3.3.  =E  This same area of the CD-ROM or CD audio media may store 1/75th of a,G  second of two channel audio information formatted according to the CD-2G  DA specification. (These audio channels are usually the left and righteF  components of a stereo pair.) An audio only density code value can beH  used to declare an area of the media to be invalid for data operations.  o  cC  For data and mixed mode media (those conforming to ISO/IEC 10149),tA  logical block address zero shall be assigned to the block at MSF G  address 00/02/00.  For audio media (those conforming only to IEC 908),rE  logical block address zero should be assigned to the actual startingsD  address of track 1.  This may be approximated by using the startingB  address of track 1 contained in the table of contents (TOC) or byA  assigning logical block address zero to the block at MSF addresst
  00/02/00.  tC  Logical addressing of CD-ROM information may use any logical blockuG  length. When the specified logical block length is an exact divisor ortE  integral multiple of the selected number of bytes per CD-ROM sector, D  the device shall map (one to one) the bytes transferred from CD-ROMF  sectors to the bytes of logical blocks.  For instance, if 2 048 bytesA  are transferred from each CD-ROM sector (specified by the CD-ROMeE  density code value), and the logical block length is 512 bytes, thentC  each CD-ROM sector shall map to exactly four logical blocks.  ThistD  International Standard does not define the mapping of logical blockE  lengths which do not evenly divide or are not exact multiples of theh,  selected number of bytes per CD-ROM sector.  dH  A track may be viewed as a partition of the CD-ROM address space. A CD-D  ROM media contains from one to ninety-nine tracks.  All informationG  sectors of a track are required to be of the same type (audio or data)oG  and mode.  Each change in the type of information on the disc requirestG  a change in track number.  A disc containing both audio and data woulds<  have at least two tracks, one for audio and one for data.     H  The tracks of a CD media are numbered consecutively with values betweenA  1 and 99. However, the first information track may have a numberdF  greater than 1. Tracks have a minimum length of 300 sectors including^  any transition area that is part of a e used at the beginning or end of any track.  For audioF  tracks the transition areas are called pause areas.  For data tracks,G  transition areas are called pre-gap and post-gap areas.  See table 236hA  for an example.  The IEC 908 and ISO/IEC 10149 standards specify H  minimum time durations for these areas.  Maximum time durations are not  specified.    D  Transition areas are formatted and the logical address continues toF  increment through transition areas.  Some media (i.e. discs with onlyF  one track) may not have transition areas.  The means to determine theG  location of the transition areas is vendor or application-specific andr1  is addressed by other standards (e.g. ISO 9660).-   G  CD-ROM is a unique SCSI device in the respect that some logical blocks-G  on a disc may not be accessible by all commands.  SEEK commands may beLH  issued to any logical block address within the reported capacity of theF  disc.  READ commands cannot be issued to logical blocks that occur inD  some transition areas, or to logical blocks within an audio track. H  PLAY commands cannot be issued to logical blocks within a data track.    m  2F  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.  -G  CD-ROM media have lead-in and lead-out areas.  These areas are outside D  of the user-accessible area as reported in the READ CD-ROM CAPACITYD  data.  The lead-in area of the media is designated track zero.  TheH  lead-out area is designated track 0AAh.  The sub-channel Q in the lead-9  in track contains a table of contents (TOC) of the disc.    G     NOTE 171 The READ CD-ROM CAPACITY command returns the logical block0N     address of the last block prior to the lead-out area. This location may beC     in a transition area and therefore not a valid address for read      operations.    C  The table of contents gives the absolute MSF location of the first0D  information sector of each track.  Control information (audio/data,D  method of audio encoding, etc.) for each track is also given in theH  TOC.  However, the TOC does not distinguish between the different modesG  of data tracks (i.e. CD-ROM data mode one vs. CD-ROM data mode two).      A  The MSF locations of the beginning of data tracks in the TOC areaG  required to be accurate, however, the TOC values for audio tracks have0F  a tolerance of plus or minus 75 sectors. Information from the TOC canH  be used to reply to a READ CD-ROM CAPACITY command.  When this is done,B  the drive implementor should consider the possible tolerances and>  return a value that allows access to all information sectors.   G  An index is a partition of a track.  Pre-gap areas are encoded with an|G  index value of zero.  Pause areas at the beginning of audio tracks are0H  also encoded with an index value of zero.  The first information sectorG  of a track has an index value of one.  Consecutive values up to 99 areaD  permitted.  Index information is not contained in the TOC.  Not allH  sectors are encoded with the index value in the Q-sub-channel data (theA  requirement is 9 out of 10).  A sector without an index value is 9  presumed to have the same index as the preceding sector.    H  Tracks and indexes are not defined to be any particular length, (exceptF  for a minimum track length of 300 sectors.)  A CD disc may be createdD  with a single information track that has a single index; or with 99*  information tracks, each with 99 indexes.  iD  The sub-channel information which is part of each sector includes aE  track relative MSF location value giving the distance from the first D  information sector of the track. On the media, this value decreasesG  during the pre-gap area (sectors with index values of 0) and increases0F  for the rest of the track. The data, returned by the READ SUB-CHANNELD  command with MSF bit set to zero, converts this to a track relativeH  logical block address (TRLBA). The TRLBA is continually increasing overF  the whole track, and pre-gap areas shall return negative values. WhenC  the MSF bit in the read sub-channel command is set to one, the MSF A  track relative location value from the media is reported without   change.   #  14.1.2 CD-ROM physical data format    E  The physical format of CD-ROM and CD-DA media uses a smaller unit of E  synchronization than the more familiar magnetic or optical recordingdG  systems. The basic data stream synchronization unit is a small frame. aD  This is not the same large frame (sector) as referred to in the MSFH  unit.  Each small frame consists of 588 bits.  A sector on CD-ROM media  consists of 98 small frames.    "  A CD-ROM small frame consists of:M     a)     1      synchronization pattern                         (24+3 bits) I     b)     1      byte of sub-channel data                    (14+3 bits) M     c)     24     bytes of data                            (24 x (14+3) bits)tk     d)     8      bytes of CIRC code                       (8 x (14+3) bits)                     Total: 588             bits.  iG  Data, sub-channel and CIRC bytes are encoded with an eight-to-fourteeneC  bit code; then three merging bits are added.  The merging bits are D  chosen to provide minimum low-frequency signal content and optimize  phase lock loop performance.       14.1.2.1 Frame format for audio  yD  Each small frame of an audio track on a two-channel CD-DA or CD-ROMF  media consists of six digitized 16-bit samples of each audio channel.D  These 24 bytes of data are combined with a synchronization pattern,D  CIRC bytes and a sub-channel byte to make a frame. Each frame takesH  approximately 136.05 uS to play. This gives a sampling rate of 44,1 khzG  for each channel. The sub-channel information creates the higher levela"  sector grouping for audio tracks.      14.1.2.2 Sector format for data  |E  The data bytes of 98 small frames comprise the physical unit of data D  referred to as a sector.  (98 small frames times 24 bytes per small0  frame equal 2 352 bytes of data per sector.)      C  A sector that contains CD-ROM data mode one data has the followingo  format:  w*     a)   12 bytes    Synchronization field*     b)   4 bytes     CD-ROM data header   6                        Absolute M field in bcd format 5                        Absolute S field in bcd formate6                        Absolute F field in bcd format /                        CD-ROM data mode field  57     c)   2048 bytes                User data field      4     d)    4 bytes               Error detection code4     e)    8 bytes               Zero                =     f)  276 bytes               Layered error correction codeu  .   C  A sector that contains CD-ROM Data Mode two data has the followinge  format:  a+     a)  12 bytes      Synchronization field *     b)  4 bytes       CD-ROM data header  5                        Absolute M field in bcd format=5                        Absolute S field in bcd formatt5                        Absolute F field in bcd format2-                        CD-ROM data mode fieldiP     c)  2 336 bytes                User data field (2048 bytes of mode 1 data   ?                        plus 288 bytes of auxiliary data)       u  i   N     NOTE 172 Many drives are capable of returning CD-ROM data mode one data inK     a CD-ROM data mode two format.  This allows the user to investigate theOL     error detection and error correction codes.  However data encoded as CD-B     ROM data mode two cannot be read as CD-ROM data mode one data.  ,)  14.1.2.3 Sub-channel information formats   iG  The sub-channel byte of each frame is assigned one bit for each of the H  8 sub-channels, designated P, Q, R, S, T, U, V, W.  Only sub-channels PD  and Q are defined for CD-ROM media.  The other sub-channel bits are  zero.   E  Sub-channel P is a simple flag bit that may be used for audio mutingf+  control and track boundary determination. h   E  Sub-channel Q has a higher level of structure. All the sub-channel Q C  bits of a sector define the sub-channel Q information block.  (FornH  audio tracks, decoding the Q sub-channel is the only way to distinguish  sector boundaries.) e   E  The sub-channel Q block consists of 98 bits, one bit from each small D  frame in a sector.  Three formats are defined for the sub-channel QF  information block. The first format provides location information and  is defined as follows:o  c=     a)     2 bits           Sub-channel synchronization fieldd;     b)     4 bits           ADR field - defines the format h>     c)     4 bits           Control field - defines the type  1                     of information in this sectora1     d)     8 bits           Track number (in BCD) 1     e)     8 bits           Index number (in BCD)f6     f)     24 bits          Track relative MSF address3     g)     8 bits           Reserved (0)           d1     h)     24 bits          Absolute MSF address e5     i)     16 bits          CRC error detection code o  t=  This format is required to exist in at least nine out of ten   consecutive sectors.   tH  The second and third formats are optional.  If used, they must exist inH  at least one out of 100 consecutive sectors.  They include the absolute>  frame byte of the MSF address to provide location information  continuity.  tF  The second format gives the catalogue number of the disc (UPC/EAN barC  code number).  This information is constant over the whole media. h  sH  The third format gives the International Standard Recording Code (ISRC)F  for each track.  The ISRC is defined in ISO 3901.  This format is notD  present on lead-in or lead-out tracks and may change only after the  track number changes.  t   14.1.3 CD Audio error reporting  hD  PLAY AUDIO commands with the immediate bit set in the audio controlH  mode return status as soon as the command has been validated (which may@  involve a seek to the starting address). The playback operationC  continues and may complete without notification to the initiator. 9?  Error termination of audio operations shall be reported to thetD  initiator by returning immediate CHECK CONDITION status to the nextD  command (except for REQUEST SENSE and INQUIRY.)  The deferred errorE  sense data (see 8.2.14.2.) is used to indicate that the error is nota  due to the current command.   H  The status of the play operation may be determined by issuing a REQUESTF  SENSE command.  The sense key is set to NO SENSE and the audio statusH  (see 14.2.10) is reported in the additional sense code qualifier field.  T2  14.1.4 CD-ROM ready condition/not ready condition  oG  The ready condition occurs after a cartridge is inserted and the drivewG  has performed its initialization tasks.  These may include reading thei"  table of contents from the media.  a=  A not ready condition may occur for the following reasons:  r*     a)     There is no cartridge inserted.?     b)     The drive is unable to load or unload the cartridge.o@     c)     The drive is unable to recover the table of contents.4     d)     The controller cannot select the drive.    o2  14.1.5 CD-ROM address reporting formats (MSF bit)  sH  Several CD-ROM specific commands can report addresses either in logicalE  or in MSF format (see table 237).  The READ HEADER, READ SUB-CHANNELg7  and READ TABLE OF CONTENTS commands have this feature.r   7                          Table 237 - MSF address formatrP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 1   |                           M field                                     |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           S field                                     |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           F field                                     |P  +=============================================================================+  kE  An MSF bit of zero requests that the logical block address format beFF  used for the CD-ROM absolute address field or for the offset from theG  beginning of the current track expressed as a number of logical blockseG  in a CD-ROM track relative address field.  This track relative logicaleE  block address (TRLBA) value is reported as a negative value in twos-iB  complement notation for transition areas that have decreasing MSF  encoded relative addresses.  oA  An MSF bit of one requests that the MSF format be used for these E  fields.  In certain transition areas, the relative MSF addresses areeC  decreasing positive values.  The absolute MSF addresses are alwaysr0  increasing positive values (see entry in 14.4).  iD  The M, S, and F fields are expressed as binary numbers.  The valuesD  match those on the media, except for the encoding.  The ratios of MD  field units to S field units and S field units to F field units are3  reported in the mode parameters page (see 14.3.3).   p.  14.1.6 Sensing support for CD-audio commands.  tF  If any commands related to audio operations are implemented, then theB  PLAY AUDIO command shall be implemented to allow a method for theD  initiator to determine if audio operations are supported.  A targetH  responding to a PLAY AUDIO command which has a transfer length of zero,B  with CHECK CONDITION status, and setting the sense key to ILLEGAL1  REQUEST does not support audio play operations.     N     NOTE 173 The PLAY AUDIO command may be implemented without support for any,     of the other audio operations commands.      14.1.7 Error reportingr  eC  If any of the following conditions occur during the execution of aa>  command, the target shall return CHECK CONDITION status.  TheD  appropriate sense key and additional sense code should be set.  TheD  following list illustrates some error conditions and the applicableH  sense keys.  The list does not provide an exhaustive enumeration of all6  conditions that may cause the CHECK CONDITION status.   c  Condition                                                                                Sense KeyCo  Invalid logical block address                                                                          ILLEGALeo                                                                                                         REQUEST   ek  Unsupported option requested                                                                       ILLEGAL k                                                                                                     REQUEST    |  Target reset or medium change since last command from this initiator                                                            UNIT ATTENTION   p  Self diagnostic failed                                                                                 HARDWAREm                                                                                                         ERRORu  ep  Unrecovered read error                                                                             MEDIUM ERRORa                                                                                    HARDWARE ERROR    p  Recovered read error                                                                            RECOVERED ERROR   {  Overrun or other error that might be resolved by repeating the command                                                    y  ABORTED command  as  Attempt to read a blank block                                                                          BLANK CHECKc  np  Attempt to play a data block as audio                                                                     BLANKp                                                                                                            CHECK  a   @  In the case of an invalid logical block address, the sense dataC  information field shall be set to the logical block address of theh  first invalid address.w   B  In the case of an attempt to read a blank or previously unwrittenD  block, the sense data information field shall be set to the logicalF  block address of the first blank block encountered.  The data read up$  to that block shall be transferred.   D  There are other special error situations for CD-ROM devices. In theB  following cases the sense key shall be set to BLANK CHECK and theB  additional sense code set to END OF USER AREA ENCOUNTERED ON THIS  TRACK: H     a)     a post-gap area is encountered (i.e. a block with CD-ROM Data            Mode 0);nJ     b)     a pre-gap area is encountered (i.e. a block with index equal to            0);:     c)     The information type (data vs. audio) changes.    A  When not performing audio playback, if the logical block address F  requested is not within a data track, the command shall be terminatedH  with CHECK CONDITION status.  The sense key shall be set to BLANK CHECKH  and the additional sense code set to ILLEGAL MODE FOR THIS TRACK.  This.  applies to audio-combined and audio media.     l!  14.2 Commands for CD-ROM devicesE  2@  The commands for CD-ROM devices shall be as shown in table 238.   ;                      Table 238 - Commands for CD-ROM deviceeI  +=====================================-============-======-============+ I  |  Command name                       | Operation  | Type |  Subclause |eI  |                                     |   code     |      |            |lI  |-------------------------------------+------------+------+------------|dI  | CHANGE DEFINITION                   |    40h     |   O  |   8.2.1    |fI  | COMPARE                             |    39h     |   O  |   8.2.2    |PI  | COPY                                |    18h     |   O  |   8.2.3    |kI  | COPY AND VERIFY                     |    3Ah     |   O  |   8.2.4    |uI  | INQUIRY                             |    12h     |   M  |   8.2.5    |rI  | LOCK/UNLOCK CACHE                   |    36h     |   O  |   9.2.2    | I  | LOG SELECT                          |    4Ch     |   O  |   8.2.6    |nI  | LOG SENSE                           |    4Dh     |   O  |   8.2.7    |aI  | MODE SELECT(6)                      |    15h     |   O  |   8.2.8    |pI  | MODE SELECT(10)                     |    55h     |   O  |   8.2.9    |2I  | MODE SENSE(6)                       |    1Ah     |   O  |   8.2.10   | I  | MODE SENSE(10)                      |    5Ah     |   O  |   8.2.11   |iI  | PAUSE/RESUME                        |    4Bh     |   O  |  14.2.1    |aI  | PLAY AUDIO(10)                      |    45h     |   O* |  14.2.2    | I  | PLAY AUDIO(12)                      |    A5h     |   O* |  14.2.3    |FI  | PLAY AUDIO MSF                      |    47h     |   O* |  14.2.4    |2I  | PLAY AUDIO TRACK/INDEX              |    48h     |   O* |  14.2.5    |oI  | PLAY TRACK RELATIVE(10)             |    49h     |   O* |  14.2.6    |oI  | PLAY TRACK RELATIVE(12)             |    A9h     |   O* |  14.2.7    |pI  | PRE-FETCH                           |    34h     |   O  |   9.2.3    |sI  | PREVENT/ALLOW MEDIUM REMOVAL        |    1Eh     |   O  |   9.2.4    |dI  | READ(6)                             |    08h     |   O  |   9.2.5    |lI  | READ(10)                            |    28h     |   M  |   9.2.6    |oI  | READ(12)                            |    A8h     |   O  |  16.2.4    |aI  | READ BUFFER                         |    3Ch     |   O  |   8.2.12   |II  | READ CD-ROM CAPACITY                |    25h     |   M  |  14.2.8    |yI  | READ HEADER                         |    44h     |   O  |  14.2.9    |rI  | READ LONG                           |    3Eh     |   O  |   9.2.9    |cI  | READ SUB-CHANNEL                    |    42h     |   O  |  14.2.10   |hI  | READ TOC                            |    43h     |   O  |  14.2.11   |nI  | RECEIVE DIAGNOSTIC RESULTS          |    1Ch     |   O  |   8.2.13   |rI  | RELEASE                             |    17h     |   M  |   9.2.11   |nI  | REQUEST SENSE                       |    03h     |   M  |   8.2.14   |EI  | RESERVE                             |    16h     |   M  |   9.2.12   |uI  | REZERO UNIT                         |    01h     |   O  |   9.2.13   |TI  | SEARCH DATA EQUAL(10)               |    31h     |   O  |   9.2.14.1 |NI  | SEARCH DATA EQUAL(12)               |    B1h     |   O  |  16.2.8    |4I  | SEARCH DATA HIGH(10)                |    30h     |   O  |   9.2.14.2 |.I  | SEARCH DATA HIGH(12)                |    B0h     |   O  |  16.2.8    |rI  | SEARCH DATA LOW(10)                 |    32h     |   O  |   9.2.14.3 |zI  | SEARCH DATA LOW(12)                 |    B2h     |   O  |  16.2.8    |eI  | SEEK(6)                             |    0Bh     |   O  |   9.2.15   | I  | SEEK(10)                            |    2Bh     |   O  |   9.2.15   | I  | SEND DIAGNOSTIC                     |    1Dh     |   M  |   8.2.15   |hI  | SET LIMITS(10)                      |    33h     |   O  |   9.2.16   | I  | SET LIMITS(12)                      |    B3h     |   O  |  16.2.9    | I  | START STOP UNIT                     |    1Bh     |   O  |   9.2.17   | I  | SYNCHRONIZE CACHE                   |    35h     |   O  |   9.2.18   |NI  | TEST UNIT READY                     |    00h     |   M  |   8.2.16   |-I  | VERIFY(10)                          |    2Fh     |   O  |  16.2.11   |=I  | VERIFY(12)                          |    Afh     |   O  |  16.2.12   |3I  | WRITE BUFFER                        |    3Bh     |   O  |   8.2.17   | I  |----------------------------------------------------------------------|=I  |Key:  M = command implementation is mandatory.                        | I  |      O = command implementation is optional.                         |-I  |      * = indicates a PLAY AUDIO command                              | I  +======================================================================+-  -  -F  The following command codes are vendor-specific:  02h, 05h, 06h, 09h,F  0Ch, 0Dh, 0Eh, 0Fh, 10h, 11h, 13h, 14h, 19h, 20h, 21h, 22h, 23h, 24h,E  26h, 27h, 29h, and C0h through FFh.  All remaining command codes for-8  CD-ROM devices are reserved for future standardization.   A  If any of the PLAY AUDIO commands (indicated by an * in the type=H  column) are implemented, the PLAY AUDIO command shall be implemented by
  the target. i     14.2.1 PAUSE RESUME command  oG  The PAUSE RESUME command (see table 239) requests that the device stopgH  or start an audio play operation.  This command is used with PLAY AUDIO7  commands issued while the immediate bit is set to one.i  e8                         Table 239 - PAUSE RESUME commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (4Bh)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |                     Reserved               |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 8   |                           Reserved                           | Resume |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+      D  A resume bit of zero causes the drive to enter the hold track stateC  with the audio output muted after the current block is played.   AEG  resume bit of one causes the drive to release the pause and begin play .  at the block following the last block played.  eH  If an audio play operation cannot be resumed and the resume bit is one,E  the command is terminated with CHECK CONDITION status. If the resumeSD  bit is zero and an audio play operation cannot be paused, (no audio?  play operation has been requested, or the requested audio play D  operation has been completed), the command is terminated with CHECK  CONDITION status.   U  cG  It shall not be considered an error to request a pause when a pause is F  already in effect, or to request a resume when a play operation is in
  progress.     14.2.2 PLAY AUDIO(10) command  RF  The PLAY AUDIO command (see table 240) requests that the target beginH  an audio playback operation. The command function (Immed and SOTC bits)F  and the output of audio signals shall be as specified by the settings(  of the mode parameters (see 14.3.3.1.).  T9                        Table 240 - PLAY AUDIO(10) command P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (45h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |             Reserved              | RelAdr |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                                                                       |P  |-----+---                 Starting logical block address                  ---|P  | 4   |                                                                       |P  |-----+---                                                                 ---|P  | 5   |                                                                  (LSB)|P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   | (MSB)                                                                 |P  |-----+---                        Transfer length                          ---|P  | 8   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+  -  -E  If any commands related to audio operations are implemented then the B  PLAY AUDIO command shall be implemented to allow a method for theD  initiator to determine if audio operations are supported.  A targetF  responding to a PLAY AUDIO command that has a transfer length of zeroA  with CHECK CONDITION status and setting the sense key to ILLEGALQ1  REQUEST does not support audio play operations.     E  The logical block address field specifies the logical block at which *  the audio playback operation shall begin.   E  The transfer length field specifies the number of contiguous logical G  blocks that shall be played. A transfer length field of zero indicates B  that no audio operation shall occur.  This condition shall not be  considered an error.     5H  If the logical block length is not equal to the sector size, the targetG  may adjust the starting logical block address and the transfer length. E  In such case, it is recommended that the target start the audio play G  operation with the beginning of a sector whenever the starting logical G  address falls within that sector (MSF unit). If the requested transfer B  length causes the end of an audio play operation to fall within aF  sector, the target may continue the play operation through the end of
  that sector.    F  If the starting address is not found, if the address is not within anF  audio track, or if a not ready condition exists, the command shall be)  terminated with CHECK CONDITION status. |  EG  If the CD-ROM information type (data vs. audio) changes, the sense keyPH  shall be set to BLANK CHECK and the additional sense code set to END OF&  USER AREA ENCOUNTERED ON THIS TRACK.   8E  If the logical block address requested is not within an audio track, H  the command shall be terminated with CHECK CONDITION status.  The senseE  key shall be set to BLANK CHECK and the additional sense code set to   ILLEGAL MODE FOR THIS TRACK.1     14.2.3 PLAY AUDIO(12) command     G  The PLAY AUDIO(12) command (see table 241) requests that the target to H  begin an audio playback operation. The command function (Immed and SOTCC  bits) and the output of audio signals shall be as specified by the H  settings of the mode parameters (see 14.3.3.1.). See the PLAY AUDIO(10)9  command for a description of the fields in this command.C  E9                        Table 241 - PLAY AUDIO(12) command P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (A5h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |               Reserved            | RelAdr |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                                                                       |P  |-----+---                      Logical block address                      ---|P  | 4   |                                                                       |P  |-----+---                                                                 ---|P  | 5   |                                                                  (LSB)|P  |-----+-----------------------------------------------------------------------|P  | 6   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 7   |                                                                       |P  |-----+---                        Transfer length                          ---|P  | 8   |                                                                       |P  |-----+---                                                                 ---|P  | 9   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 10  |                             Reserved                                  |P  |-----+-----------------------------------------------------------------------|P  | 11  |                           Control                                     |P  +=============================================================================+  n  (  14.2.4 PLAY AUDIO MSF command  lG  The PLAY AUDIO MSF command (see table 242) requests that the target toeD  begin an audio playback operation.  The command function (Immed andH  SOTC bits) and the output of audio signals shall be as specified by the1  settings of the mode parameters (see 14.3.3.1.).O  c9                        Table 242 - PLAY AUDIO MSF command P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|        |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (47h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |                  Reserved                  |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Starting M field                            |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Starting S field                            |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Starting F field                            |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Ending M field                              |P  |-----+-----------------------------------------------------------------------|P  | 7   |                           Ending S field                              |P  |-----+-----------------------------------------------------------------------|P  | 8   |                           Ending F field                              |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+  =  =E  The starting M field, the starting S field, and the starting F field C  specify the absolute MSF address at which the audio play operationiG  shall begin.  The ending M field, the ending S field, and the ending FeF  field specify the absolute MSF address where the audio play operationF  shall end.  All contiguous audio sectors between the starting and the$  ending MSF address shall be played.  eF  A starting MSF address equal to an ending MSF address causes no audioE  play operation to occur.  This shall not be considered an error.  If B  the starting MSF address is less than the ending MSF address, theH  command shall be terminated with CHECK CONDITION status.  The sense key!  shall be set to ILLEGAL REQUEST.n  eF  If the starting address is not found, if the address is not within anF  audio track, or if a not ready condition exists, the command shall beF  terminated with CHECK CONDITION status.  See 14.1.7 for a description   of error reporting information.  i&  14.2.5 PLAY AUDIO TRACK INDEX command  (G  The PLAY AUDIO TRACK INDEX command (see table 243) requests the targetiG  to begin an audio play operation. The command function (Immed and SOTC C  bits) and the output of audio signals shall be as specified by the=1  settings of the mode parameters (see 14.3.3.1.).=  ==                    Table 243 - PLAY AUDIO TRACK INDEX command P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (48h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |                  Reserved                  |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Starting track                              |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Starting index                              |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   |                           Ending track                                |P  |-----+-----------------------------------------------------------------------|P  | 8   |                           Ending index                                |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+  r  eD  The starting track field specifies the track number of the startingB  audio track.  The starting index field specifies the index numberB  within the track at which the audio play operation shall begin.    QF  The ending track field specifies the track number of the ending audioE  track.  The ending index field specifies the index number within theaG  track after which the audio play operation shall stop.  The audio playeG  operation shall terminate at the last block with an index number equallG  to the ending index. All contiguous audio sectors between the startingi(  and the ending address shall be played.  rE  If the starting address is less than the ending address, the command F  shall be terminated with CHECK CONDITION status.  The sense key shall  be set to ILLEGAL REQUEST.i  sF  If the starting address is not found, or if the address is not withinF  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.   G     NOTE 174 Valid values for the track and index fields are 1 to 99. A L     starting index value of one specifies that playback is to start with theK     first audio sector of the track following the (optional) pause.  A lastoH     index value of 99 specifies that playback continues through the last     sector of the track.     F  If the ending track is greater than the last information track on theF  media, the playback shall continue until the last track is complete. C  If the ending index is greater than the largest index value on thetH  ending track, the playback shall continue until this track is complete;B  then terminate.  These conditions shall not be considered errors.  sE  If the starting index is greater than the largest index value on theaG  starting track, and the stop on track crossing (SOTC) bit of the audioa@  control MODE SELECT parameters page (see 14.3.3.1) is zero, theD  playback operation shall start at the beginning of the next track.    This situation is not an error.  dE  If the starting index is greater than the largest index value on thesG  starting track, and the stop on track crossing (SOTC) bit of the audioeH  control MODE SELECT parameters page (see 14.3.3.1) is one, the playbackH  shall not begin. The target shall return CHECK CONDITION, and the sense%  key shall be set to ILLEGAL REQUEST.    N     NOTE 175 The operation of the SOTC bit described above comes about becauseM     the user may not be able to determine the largest index value on a track,=N     either from the table of contents or by other means. The SOTC bit one caseJ     allows the user to determine the largest index. The SOTC bit zero caseK     allows the user to set up play operations without complete knowledge of      the media layout.   +-  14.2.6 PLAY AUDIO TRACK RELATIVE(10) command-  -H  The PLAY AUDIO TRACK RELATIVE(10) command (see table 244) requests thatG  the device begin an audio playback operation.  The starting address is ?  specified as a track relative logical block address within the E  specified starting track. The command function (Immed and SOTC bits) F  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) commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (49h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |                  Reserved                  |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                                                                       |P  |-----+---              Track relative logical block address               ---|P  | 4   |                                                                       |P  |-----+---                                                                 ---|P  | 5   |                                                                  (LSB)|P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Starting track                              |P  |-----+-----------------------------------------------------------------------|P  | 7   | (MSB)                                                                 |P  |-----+---                        Transfer length                          ---|P  | 8   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+      D  The starting track field specifies the track number of the starting  audio track.  |   E  The track relative logical block address (TRLBA) field specifies the @  two's complement starting logical block address relative to theG  beginning of the first sector on the track with an index value of one. D  Negative values indicate a starting location within the audio pause.  area at the beginning of the requested track.   E  The transfer length field specifies the number of contiguous logical|G  blocks that shall be output as audio data.  A transfer length field of-C  zero indicates that no audio playback operation shall occur.  This G  condition shall not be considered an error.  Any other value indicates-3  the number of logical blocks that shall be output.    G  If the logical block length is not equal to the sector size the target-G  may adjust the starting logical block address and the transfer length. E  In such case, it is recommended that the target start the audio play-G  operation with the beginning of a sector whenever the starting logical|G  address falls within that sector (MSF unit). If the requested transfer B  length causes the end of an audio play operation to fall within aF  sector, the target may continue the play operation through the end of
  that sector.    F  If the starting address is not found, or if the address is not withinC  an audio track, or if a not ready condition exists, the command is F  terminated with CHECK CONDITION status.  See 14.1.7 for a description   of error reporting information.  =-  14.2.7 PLAY AUDIO TRACK RELATIVE(12) commandt   H  The PLAY AUDIO TRACK RELATIVE(12) command (see table 245) requests thatC  the device begin an audio playback operation. The command functioneB  (Immed and SOTC bits) and the output of audio signals shall be asF  specified by the settings of the mode parameters (see 14.3.3.1.). SeeC  the PLAY AUDIO TRACK RELATIVE(10) command for a description of thep  fields in this command.  d@                Table 245 - PLAY AUDIO TRACK RELATIVE(12) commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (A9h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |                  Reserved                  |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                                                                       |P  |-----+---              Track relative logical block address               ---|P  | 4   |                                                                       |P  |-----+---                                                                 ---|P  | 5   |                                                                  (LSB)|P  |-----+-----------------------------------------------------------------------|P  | 6   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 7   |                                                                       |P  |-----+---                        Transfer length                          ---|P  | 8   |                                                                       |P  |-----+---                                                                 ---|P  | 9   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 10  |                           Starting track                              |P  |-----+-----------------------------------------------------------------------|P  | 11  |                           Control                                     |P  +=============================================================================+  -  -$  14.2.8 READ CD-ROM CAPACITY command  -F  The READ CD-ROM CAPACITY command (see table 246) provides a means forC  the initiator to request information regarding the capacity of the-  logical unit.  -<                     Table 246 - READ CD-ROM CAPACITY commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (25h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |             Reserved              | RelAdr |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                                                                       |P  |-----+---                        Logical block address                    ---|P  | 4   |                                                                       |P  |-----+---                                                                 ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 8   |                           Reserved                           |  PMI   |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+     mG     NOTE 176 This command has the same operation code (25h) as the READrJ     CAPACITY command (see 92.7).  The general function is the same but theJ     exact definitions of the returned logical block address is modified toH     allow returning a possibly inexact value (but one with a known errorL     bound) based on CD-ROM table of contents data.  For many CD-ROM devices,2     this implementation allows a quicker response.  i@  A partial medium indicator (PMI) bit of zero indicates that theC  information returned in the READ CD-ROM CAPACITY data shall be the D  logical block address and block length (in bytes) of the last validC  logical block of the logical unit for seek operations. The logicalEB  block address returned shall be greater than or equal to the lastA  readable or playable block. If greater, this address may be in a F  transition area beyond the last valid logical block for read or audioE  play operations. The value returned shall not be not be more than 75iG  sectors (MSF units) greater than the logical block address of the lastuH  readable or playable block. (This value arises because the CD-ROM tableH  of contents lead-out track location  has a +/- 75 sector tolerance whenD  the lead-out track is encoded as an audio track.) The logical blockF  address in the command descriptor block shall be set to zero for this  option.  aF  A PMI bit of one indicates that the information returned shall be theF  logical block address and block length (in bytes) of the last logicalG  block address after which a substantial delay in data transfer will be.G  encountered. This logical block address shall be greater than or equalaI  to the logical block address specified in the command descriptor block. =C  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.  =  =N     NOTE 177 This option may take several seconds to complete on CD-ROM media.   C  See 9.1.10 for a description of the relative address bit (RelAdr).-  -G  Eight bytes of READ CD-ROM CAPACITY data (see table 247) shall be sentc)  during the DATA IN phase of the command.r   :                      Table 247 - READ CAPACITY data formatP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   | (MSB)                                                                 |P  |- - -+---                        Logical block address                    ---|P  | 3   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 4   | (MSB)                                                                 |P  |- - -+---                        Block length                             ---|P  | 7   |                                                                 (LSB) |P  +=============================================================================+     g  14.2.9 READ HEADER command-   H  The READ HEADER command (see table 248) requests that the device returnF  the CD-ROM data block address header of the requested logical block.   -7                         Table 248 - READ HEADER command P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (44h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |         Reserved         |  MSF   |Reserved|P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                                                                       |P  |-----+---                        Logical block address                    ---|P  | 4   |                                                                       |P  |-----+---                                                                 ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   | (MSB)                                                                 |P  |-----+---                        Allocation length                        ---|P  | 8   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+  s   .  See 14.1.5. for a description of the MSF bit.   E  The logical block address field specifies the logical block at whicht'  the read header operation shall begin.5  PH  See the READ command for exception handling.  If the logical block sizeC  is other than the physical block size, it shall be mapped into the F  appropriate physical block from which the data would have been read.    D  The READ HEADER data format (see table 249) defines the CD-ROM data5  block address header of the requested logical block.=  =9                       Table 249 - READ HEADER data formatnP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                       CD-ROM data mode                                |P  |-----+-----------------------------------------------------------------------|P  | 1   |                          Reserved                                     |P  |-----+-----------------------------------------------------------------------|P  | 2   |                          Reserved                                     |P  |-----+-----------------------------------------------------------------------|P  | 3   |                          Reserved                                     |P  |-----+-----------------------------------------------------------------------|P  | 4   | (MSB)                                                                 |P  |- - -+---                    Absolute CD-ROM address                      ---|P  | 7   |                                                                 (LSB) |P  +=============================================================================+      A  The CD-ROM data mode field specifies the CD-ROM data mode of the E  logical blocks in this sector of data.  The values in this field are   defined in table 250.   9                        Table 250 - CD-ROM data mode codes-L    +=============-============================-============================+L    |    CD-ROM   |  User data field contents  |  Auxiliary field contents  |L    |     mode    |       (2 048 bytes)        |        (288 bytes)         |L    |-------------+----------------------------+----------------------------|L    |     00h     |  All bytes zero            |  All bytes zero            |L    |     01h     |  User data                 |  L-EC symbols              |L    |     02h     |  User data                 |  User data                 |L    |  03h - FFh  |  Reserved                  |  Reserved                  |L    +=======================================================================+  =  =E  If the MSF bit is zero, the absolute address field gives the logical F  block address of the first logical block in the physical sector whereG  the data for the requested logical block address is found.  If the MSF=D  bit is one, the absolute address field gives the MSF address of theH  sector where the data for the requested logical block address is found.  (See 14.1.5.) -  -!  14.2.10 READ SUB-CHANNEL command-  -F  The READ SUB-CHANNEL command (see table 251) requests that the targetC  return the requested sub-channel data plus the state of audio play-  operations.  -:                       Table 251 - READ SUB-CHANNEL commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                          Operation code (42h)                         |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |         Reserved         |  MSF   |Reserved|P  |-----+-----------------------------------------------------------------------|P  | 2   |Reserved|  SubQ  |                       Reserved                      |P  |-----+-----------------------------------------------------------------------|P  | 3   |                        Sub-channel data format                        |P  |-----+-----------------------------------------------------------------------|P  | 4   |                               Reserved                                |P  |-----+-----------------------------------------------------------------------|P  | 5   |                               Reserved                                |P  |-----+-----------------------------------------------------------------------|P  | 6   |                             Track number                              |P  |-----+-----------------------------------------------------------------------|P  | 7   | (MSB)                                                                 |P  |-----+---                       Allocation length                         ---|P  | 8   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 9   |                               Control                                 |P  +=============================================================================+     iK     NOTE 178 Sub-channel data returned by this command may be from the lastaK     appropriate sector encountered by a current or previous media accessingrL     operation. When there is no current audio play operation, the target mayL     access the media to read the sub-channel data. The target is responsibleM     that the data returned are current and consistent.  For example with sub-hK     channel data format 0, the International Standard Recording Code (ISRC)nI     data reported must have been read from the same track as the reporteda     current position data.   .  See 14.1.5. for a description of the MSF bit.  eD  The sub Q bit set to one requests that the target return the Q sub-E  channel data. The sub Q bit set to zero requests that no sub-channeln9  data be returned. This shall not be considered an error.i  a@     NOTE 179 The other bits in this byte are reserved for futureI     standardization when they may be defined to request other sub-channel 	     data.c  eE  The sub-channel data format field specifies the returned sub channeleB  data (see table 252). If this field is 00h, sub-Q channel data isE  returned. If this field is 01h, 02h or 03h, the requested sub-Q datag  item is returned.   <                    Table 252 - Sub-channel data format codesG  +=============-======================================================+dG  | Format Code |  Returned data                                       |tG  |-------------+------------------------------------------------------| G  |     00h     |  Sub-Q channel data                                  |=G  |     01h     |  CD-ROM current position                             |iG  |     02h     |  Media catalogue number (UPC/bar code)               ||G  |     03h     |  Track international standard recording code (ISRC)  | G  |  04h - EFh  |  Reserved                                            |=G  |  F0h - FFh  |  Vendor-specific                                     | G  +====================================================================+k  d  sC  The track number field specifies the track from which ISRC data is G  read. This field must have a value between 01h and 63h (99bcd), and is-C  valid only when the sub-channel data format field is 03h.  In this 3  case, the target returns ISRC data for this track.    $  14.2.10.1 Sub-Q channel data format  lC  The sub-CHANNEL command data formats consist of a four-byte header E  followed by a sub-channel data block.  The header contains the audio=H  status byte and the sub-channel data length field.  If the sub Q bit isF  zero, the target shall not return the sub-channel data block; in this(  case, the sub-channel data length is 0.  a1  Table 253 defines the sub-Q channel data format.o   :                      Table 253 - Sub-Q channel data formatP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  |     |                        Sub-channel data header                        |P  |=====+=======================================================================|P  | 0   |                                Reserved                               |P  |-----+-----------------------------------------------------------------------|P  | 1   |                              Audio status                             |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                     Sub-channel data length                     ---|P  | 3   |                                                                 (LSB) |P  |=====+=======================================================================|P  |     |                        Sub-Q channel data block                       |P  |=====+=======================================================================|P  | 4   |                    Sub channel data format code (00h)                 |P  |-----+-----------------------------------------------------------------------|P  | 5   |                ADR                |             Control               |P  |-----+-----------------------------------------------------------------------|P  | 6   |                             Track number                              |P  |-----+-----------------------------------------------------------------------|P  | 7   |                             Index number                              |P  |-----+-----------------------------------------------------------------------|P  | 8   | (MSB)                                                                 |P  |- - -+---                     Absolute CD-ROM address                     ---|P  | 11  |                                                                 (LSB) |P  |--- -+-----------------------------------------------------------------------|P  | 12  | (MSB)                                                                 |P  |- - -+---                  Track relative CD-ROM address                  ---|P  | 15  |                                                                 (LSB) |P  |--- -+-----------------------------------------------------------------------|P  | 16  |  MCVal |                       Reserved                               |P  |--- -+-----------------------------------------------------------------------|P  | 17  | (MSB)                                                                 |P  |- - -+---                Media catalogue number (UPC/Bar code)            ---|P  | 31  |                                                                 (LSB) |P  |--- -+-----------------------------------------------------------------------|P  | 32  |  TCVal |                       Reserved                               |P  |--- -+-----------------------------------------------------------------------|P  | 33  | (MSB)                                                                 |P  |- - -+---        Track international standard recording code (ISRC)       ---|P  | 47  |                                                                 (LSB) |P  +=============================================================================+      G  The audio status field indicates the status of audio play operations.  F  The audio status values are defined in table 254. Audio status valuesH  greater than zero are returned only to the initiator that requested theB  last audio play operation. Audio status values 13h and 14h returnF  information on previous audio operations; they are returned only onceF  after the condition has occurred.  If another audio play operation isB  not requested, the audio status returned for subsequent READ SUB-  CHANNEL commands is 15h.=  =7                          Table 254 - Audio status codes E           +========-================================================+ E           | Status |  Description                                   |-E           |--------+------------------------------------------------| E           |   00h  |  Audio status byte not supported or not valid  | E           |   11h  |  Audio play operation in progress              | E           |   12h  |  Audio play operation paused                   | E           |   13h  |  Audio play operation successfully completed   |eE           |   14h  |  Audio play operation stopped due to error     |=E           |   15h  |  No current audio status to return             |tE           +=========================================================+   c  nA  The sub-channel data length specifies the length in bytes of thecE  following sub-channel data block.  A sub-channel data length of zerolE  indicates that no sub-channel data block is included in the returnedd  data. b  kN     NOTE 180 Usual values for sub-channel data length are 0, 12, 20, 28 and 44L     bytes.  Sub-channel data length does not include the sub channel header.   C  The sub-Q channel data block consists of control data (bytes 4-5),iG  current position data (bytes 6 - 15) and identification data (bytes 16=H  - 47).  The control data and current position data is obtained from theH  Q sub-channel information of the current block. Identification data mayH  be reported that was obtained from a previous block.  If identificationF  data is reported, the data shall be valid for the sector addressed by  the current position data. F     a)     If an audio play operation is proceeding in the background,F            position data for the last sector played shall be reported.L     b)     In other cases, for instance after a READ command, the target mayH            either report position data for the last sector processed forL            that operation or may report position data from the sector at the&            current read head position.  +M     NOTE 181 When the type of information encoded in the Q sub-channel of the M     current sector is the media catalog number or ISRC; the track, index, and-C     address fields should be extrapolated from the previous sector.-  -B  The ADR field gives the type of information encoded in the Q sub-.  channel of this block, as shown in table 255.  -9                       Table 255 - ADR sub-channel Q field L    +===========-===========================================================+L    |  ADR code |  Description                                              |L    |-----------+-----------------------------------------------------------|L    |     0h    |  Sub-channel Q mode information not supplied              |L    |     1h    |  Sub-channel Q encodes current position data              |L    |           |  (i.e. track, index, absolute address, relative address)  |L    |     2h    |  Sub-channel Q encodes media catalogue number             |L    |     3h    |  Sub-channel Q encodes ISRC                               |L    |  4h - Fh  |  Reserved                                                 |L    +=======================================================================+  =+  The control bits are defined in table 256.S  c;                      Table 256 - Sub-channel Q control bits C  +=====-==============================-===========================+sC  | Bit |       Equals zero            |       Equals one          |hC  |-----+------------------------------+---------------------------|tC  |  0  |  Audio without pre-emphasis  |  Audio with pre-emphasis  |iC  |  1  |  Digital copy prohibited     |  Digital copy permitted   |aC  |  2  |  Audio track                 |  Data track               |eC  |  3  |  Two-channel audio           |  Four-channel audio       |tC  +================================================================+Q  t  t        u  s  a5  The track number specifies the current track number.Q  tB  The index number specifies the index number in the current track.  lF  The absolute CD-ROM address field gives the current location relativeE  to the logical beginning of the media.  If the MSF bit is zero, thisnH  field is a logical block address.  If the MSF bit is one, this field is'  an absolute MSF address. (See 14.1.5.)n  eC  The track relative CD-ROM address field gives the current location H  relative to the logical beginning of the current track.  If the MSF bitH  is zero, this field is a track relative logical block address.  (If the@  current block is in the pre-gap area of a track, this will be aH  negative value, expressed as a twos-complement number. See 14.1.5).  IfF  the MSF bit is one, this field is the relative MSF address from the Q  sub-channel.    D  A media catalogue valid (MCVal) bit of one indicates that the mediaE  catalogue number field is valid.  A MCVal bit of zero indicates that /  the media catalogue number field is not valid.P  aD  The media catalogue number field contains the identifying number ofE  this media according to the uniform product code values (UPC/EAN bar >  coding) expressed in ASCII. Non-zero values in this field areC  controlled by the Uniform Product Code Council 1) and the European=E  Article Number Council 2).  A value in this field of all ASCII zeros 9  indicates that the media catalog number is not supplied.T   F  The track code valid (TCVal) bit of one indicates that the track ISRC>  field is valid.  A TCVal bit of zero indicates that the trackA  international standard recording code (ISRC) field is not valid.b  cC  The track ISRC field contains the identifying number of this media C  according to the ISRC standards (DIN-31-621) expressed in ASCII.  e  ----nE     1) The Uniform Product Code Council is located at 8163 Old YankeeI#  Road, Suite J, Dayton, Ohio 45459. @     2) The European Article Number Council is located at Rue des+  Colonies, 54-BTE8, 1000 Brussels, Belgium.d  n  t  s  Q.  14.2.10.2 CD-ROM current position data format  b;  Table 257 defines the CD-ROM current position data format.-  =?                 Table 257 - CD-ROM current position data format P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  |     |                        Sub-channel data header                        |P  |=====+=======================================================================|P  | 0   |                               Reserved                                |P  |-----+-----------------------------------------------------------------------|P  | 1   |                             Audio status                              |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                     Sub-channel data length                     ---|P  | 3   |                                                                 (LSB) |P  |=====+=======================================================================|P  |     |                  CD-ROM current position data block                   |P  |=====+=======================================================================|P  | 4   |                  Sub channel data format code (01h)                   |P  |-----+-----------------------------------------------------------------------|P  | 5   |                ADR                |             Control               |P  |-----+-----------------------------------------------------------------------|P  | 6   |                             Track number                              |P  |-----+-----------------------------------------------------------------------|P  | 7   |                             Index number                              |P  |-----+-----------------------------------------------------------------------|P  | 8   | (MSB)                                                                 |P  |- - -+---                     Absolute CD-ROM address                     ---|P  | 11  |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 12  | (MSB)                                                                 |P  |- - -+---                  Track relative CD-ROM address                  ---|P  | 15  |                                                                 (LSB) |P  +=============================================================================+  -  --  14.2.10.3 Media catalogue number data format-  -:  Table 258 defines the media catalogue number data format.   ?                  Table 258 - Media catalogue number data formatgP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  |     |                        Sub-channel data header                        |P  |=====+=======================================================================|P  | 0   |                               Reserved                                |P  |-----+-----------------------------------------------------------------------|P  | 1   |                             Audio status                              |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                     Sub-channel data length                     ---|P  | 3   |                                                                 (LSB) |P  |=====+=======================================================================|P  |     |                   Media catalogue number data block                   |P  |=====+=======================================================================|P  | 4   |                  Sub channel data format code (02h)                   |P  |-----+-----------------------------------------------------------------------|P  | 5   |                               Reserved                                |P  |-----+-----------------------------------------------------------------------|P  | 6   |                               Reserved                                |P  |-----+-----------------------------------------------------------------------|P  | 7   |                               Reserved                                |P  |-----+-----------------------------------------------------------------------|P  | 8   |  MCVal |                      Reserved                                |P  |-----+-----------------------------------------------------------------------|P  | 9   | (MSB)                                                                 |P  |- - -+---              Media catalogue number (UPC/Bar code)              ---|P  | 23  |                                                                 (LSB) |P  +=============================================================================+  aG  If media catalogue number data is found, the MCVal bit is set to one. nF  If MCN data is not detected, the MCVal bit is set to zero to indicate-  the media catalogue number field is invalid.o  hK     NOTE 182 Media catalogue number data returned by this command with sub- M     channel data format field code 02h may be from any block that has UPC bardE     code Q sub-channel data. (This code is constant anywhere in everyI     applicable disc.)o  sB  14.2.10.4 Track international standard recording code data format  eG  Table 259 defines the track international standard recording code dataf  format.  mI       Table 259 - Track international standard recording code data formateP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  |     |                       Sub-channel data header                         |P  |=====+=======================================================================|P  | 0   |                               Reserved                                |P  |-----+-----------------------------------------------------------------------|P  | 1   |                             Audio status                              |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                     Sub-channel data length                     ---|P  | 3   |                                                                 (LSB) |P  |=====+=======================================================================|P  |     |                         Track ISRC data block                         |P  |=====+=======================================================================|P  | 4   |                    Sub channel data format code (03h)                 |P  |-----+-----------------------------------------------------------------------|P  | 5   |              ADR                  |               Control             |P  |-----+-----------------------------------------------------------------------|P  | 6   |                             Track number                              |P  |-----+-----------------------------------------------------------------------|P  | 7   |                               Reserved                                |P  |-----+-----------------------------------------------------------------------|P  | 8   |  TCVal |                      Reserved                                |P  |-----+-----------------------------------------------------------------------|P  | 9   | (MSB)                                                                 |P  |- - -+---         Track international standard recording code (ISRC)      ---|P  | 23  |                                                                 (LSB) |P  +=============================================================================+  a  eH  If ISRC data is detected, the TCVal bit is set to one.  If ISRC data isF  not detected, the TCVal bit is set to zero to indicate the ISRC field  is invalid.  oK     NOTE 183 Track ISRC data returned by this command with sub-channel datawJ     format field 03h may be from any block in the specified track that has     ISRC data.  t  14.2.11 READ TOC commandr  tH  The READ TOC command (see table 260) requests that the target transfers2  data from the table of contents to the initiator.  n6                           Table 260 - READ TOC commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                         Operation code (43h)                          |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |         Reserved         |  MSF   |Reserved|P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Starting track                              |P  |-----+-----------------------------------------------------------------------|P  | 7   | (MSB)                                                                 |P  |-----+---                        Allocation length                        ---|P  | 8   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+      .  See 14.1.5. for a description of the MSF bit.  -G  The starting track field specifies the starting track number for which A  the data shall be returned.  If this value is zero, the table of H  contents data shall begin with the first track on the medium.  The data;  are returned in contiguous ascending track number order.  (  )E  If the starting track field is not valid for the currently installed=F  medium, the command shall be terminated with CHECK CONDITION status. G  The sense key shall be set to ILLEGAL REQUEST and the additional sense="  code set to INVALID FIELD IN CDB.  |L     NOTE 184 The maximum TOC data length possible on currently available CD-9     ROM media is 804 bytes, or 100 TOC track descriptors.-  -;  The format of the data returned is specified in table 261.    9                         Table 261 - READ TOC data format -P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   | (MSB)                                                                 |P  |-----+---                        TOC data length                          ---|P  | 1   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           First track number                          |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Last track number                           |P  |=====+=======================================================================|P  |     |                         TOC track descriptor(s)                       |P  |=====+=======================================================================|P  | 0   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 1   |              ADR                  |             Control               |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Track number                                |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   | (MSB)                                                                 |P  |- ---+---                        Absolute CD-ROM address                  ---|P  | 7   |                                                                 (LSB) |P  +=============================================================================+  +   H  The TOC data block contains a four-byte header followed by zero or more  TOC track descriptors.    G  The TOC data length specifies the length in bytes of the following TOC=G  data that is available to be transferred during the DATA IN phase. The A  TOC data length value does not include the TOC data length field=  itself.  =E  The first track number field indicates the first track number in the|  table of contents.  h  eC  The last track number field indicates the last track number in the-4  table of contents before the lead-out track number.   J     NOTE 185 The first track number is not required to be one.  A disc mayI     start at any valid track number.  The track numbers between the first-K     track number and the last track number are required to be in contiguous 3     ascending order, except for the lead-out track.-  -B  The ADR field gives the type of information encoded in the Q sub-G  channel of the block where this TOC entry was found.  The possible ADR-!  values are defined in 14.2.10.1.-  -G  The control field indicates the attributes of the track.  The possible /  control field values are defined in 14.2.10.1.-  -H  The track number field indicates the track number for which the data inE  the TOC track descriptor is valid.  A track number of 0AAh indicates A  that the track descriptor is for the start of the lead-out area.   -D  The absolute CD-ROM address contains the address of the first blockF  with user information for that track number as read from the table ofA  contents.  An MSF bit of zero indicates that the absolute CD-ROMuC  address field contains a logical block address.  An MSF bit of one D  indicates the absolute CD-ROM address field contains an MSF address  (see 14.1.5). h   L     NOTE 186 The starting logical block address value recovered from the TOCK     has a tolerance of zero for data tracks and plus or minus 75 CD sectors L     for audio tracks.  This tolerance is multiplied by a factor dependent on     the logical block length.4  a#  14.3 Parameters for CD-ROM deviceso  d     14.3.1 Diagnostic parameterst  t@  This subclause defines the descriptors and pages for diagnostic&  parameters used with CD-ROM devices.   dG  The diagnostic page codes for CD-ROM devices are defined in table 262.-  =8                        Table 262 - Diagnostic page codesP  +=============-==================================================-============+P  |  Page code  |  Description                                     |  Subclause |P  |-------------+--------------------------------------------------+------------|P  |     00h     |  Supported diagnostic pages                      |  8.3.1.1   |P  |  01h - 3Fh  |  Reserved (for all device type pages)            |            |P  |  40h - 7Fh  |  Reserved                                        |            |P  |  80h - FFh  |  Vendor-specific pages                           |            |P  +=============================================================================+  -  -  14.3.2 Log parameters  -D  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.   5                            Table 263 - Log page codes P  +=============-==================================================-============+P  |  Page code  |  Description                                     |  Subclause |P  |-------------+--------------------------------------------------+------------|P  |     01h     |  Buffer over-run/under-run page                  |  8.3.2.1   |P  |     03h     |  Error counter page (read) page                  |  8.3.2.2   |P  |     07h     |  Last n error events page                        |  8.3.2.3   |P  |     06h     |  Non-medium error page                           |  8.3.2.4   |P  |     02h     |  Reserved                                        |            |P  |  04h - 05h  |  Reserved                                        |            |P  |  08h - 2Fh  |  Reserved                                        |            |P  |     3Fh     |  Reserved                                        |            |P  |     00h     |  Supported log pages                             |  8.3.2.5   |P  |  30h - 3Eh  |  Vendor-specific pages                           |            |P  +=============================================================================+        14.3.3 Mode parameters   |E  This subclause defines the descriptors and pages for mode parameters)  used with CD-ROM devices.   F  The mode parameter list, including the mode parameter header and mode'  block descriptor are defined in 8.3.3.=  =E  The medium-type code field is contained in the mode parameter headerbB  (see 8.3.3).  Table 264 defines the medium type values for CD-ROM	  devices.   i  c:                       Table 264 - CD-ROM medium type codes:  +=============-=========================================+:  |     Code    |  Medium type description                |:  |=============+=========================================|:  |     00h     |  Default (only one type supported)      |:  |     01h     |  120 mm CD-ROM data only                |:  |     02h     |  120 mm CD-DA audio only                |:  |     03h     |  120 mm CD-ROM data and audio combined  |:  |     04h     |  Reserved                               |:  |     05h     |  80 mm CD-ROM data only                 |:  |     06h     |  80 mm CD-DA audio only                 |:  |     07h     |  80 mm CD-ROM data and audio combined   |:  |  08h - 7Fh  |  Reserved                               |:  |  80h - FFh  |  Vendor-specific                        |:  +=======================================================+  -  -G  The device-specific parameter field is contained in the mode parameter E  header (see 8.3.3).  Table 265 defines the device-specific parameter-  field for CD-ROM devices.     2>                   Table 265 - CD-ROM device-specific parameterP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |=====+==========================+========+==========================+========|P  |     |         Reserved         | DPOFUA |           Reserved       |  EBC   |P  +=============================================================================+  -  -G  When used with the MODE SELECT command, the DPOFUA bit is not used and   the field is reserved.-  -E  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 blockG  descriptor (see 8.3.3).  Table 266 defines the density code values for   CD-ROM devices.  c  o8                         Table 266 - CD-ROM density codesF  +================-==================================================+F  |    Code        |  Data types to be transferred                    |F  |================+==================================================|F  |     00h        |  Default density code                            |F  |     01h        |  User data only                                  |F  |                |    (2 048 bytes per physical sector)             |F  |     02h        |  User data plus auxiliary data field             |F  |                |    (2 336 bytes per sector)                      |F  |     03h        |  4-byte tag field, user data plus auxiliary data |F  |                |    (2 340 bytes per sector)                      |F  |     04h        |  Audio information only                          |F  |                |    (1/75th of a second per logical block)        |F  |  05h - 7Fh     |  Reserved                                        |F  |  80h - FFh     |  Vendor-specific                                 |F  +===================================================================+  i  pJ     NOTE 187 The number of bytes per sector specified by this parameter isE     used with the block length to map CD-ROM sectors to logical block=     addresses.  +A  The mode page codes for CD-ROM devices are defined in table 267.1   5                           Table 267 - Mode page codes|P  +=============-==================================================-============+P  |  Page code  |  Description                                     |  Subclause |P  |-------------+--------------------------------------------------+------------|P  |     08h     |  Caching page                                    |   9.3.3.1  |P  |     0Eh     |  CD-ROM audio control page                       |  14.3.3.1  |P  |     0Dh     |  CD-ROM page                                     |  14.3.3.2  |P  |     0Ah     |  Control mode page                               |   8.3.3.1  |P  |     02h     |  Disconnect-reconnect page                       |   8.3.3.2  |P  |     0Bh     |  Medium types supported page                     |   9.3.3.4  |P  |     09h     |  Peripheral device page                          |   8.3.3.3  |P  |     01h     |  Read error recovery page                        |  14.3.3.3  |P  |  03h - 06h  |  Reserved                                        |            |P  |     0Ch     |  Reserved                                        |            |P  |  0Fh - 1Fh  |  Reserved                                        |            |P  |     07h     |  Verify error recovery page                      |  14.3.3.4  |P  |     00h     |  Vendor-specific (does not require page format)  |            |P  |  20h - 3Eh  |  Vendor-specific (page format required)          |            |P  |     3Fh     |  Return all pages                                |            |P  |             |     (valid only for the MODE SENSE command)      |            |P  +=============================================================================+      )  14.3.3.1 CD-ROM audio control parameters    B  The CD-ROM audio control parameters page (see table 268) sets theF  playback modes and output controls for subsequent PLAY AUDIO commands+  and any current audio playback operation. =  =@                 Table 268 - CD-ROM audio control parameters pageP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+========+========+=====================================================|P  | 0   |   PS   |Reserved|            Page code (0Eh)                          |P  |-----+-----------------------------------------------------------------------|P  | 1   |                           Parameter length (0Eh)                      |P  |-----+-----------------------------------------------------------------------|P  | 2   |                  Reserved                  | Immed  |  SOTC  |Reserved|P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 5   | APRVal |         Reserved         |        Format of LBAs / Sec.      |P  |-----+-----------------------------------------------------------------------|P  | 6   | (MSB)                                                                 |P  |-----+---          Logical blocks per second of audio playback            ---|P  | 7   |                                                                  (LSB)|P  |-----+-----------------------------------------------------------------------|P  | 8   |              Reserved             |  Output port 0 channel selection  |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Output port 0 volume                        |P  |-----+-----------------------------------------------------------------------|P  | 10  |              Reserved             |  Output port 1 channel selection  |P  |-----+-----------------------------------------------------------------------|P  | 11  |                           Output port 1 volume                        |P  |-----+-----------------------------------------------------------------------|P  | 12  |              Reserved             |  Output port 2 channel selection  |P  |-----+-----------------------------------------------------------------------|P  | 13  |                           Output port 2 volume                        |P  |-----+-----------------------------------------------------------------------|P  | 14  |              Reserved             |  Output port 3 channel selection  |P  |-----+-----------------------------------------------------------------------|P  | 15  |                           Output port 3 volume                        |P  +=============================================================================+  =  =A  The parameters savable (PS) bit is only used with the MODE SENSEuG  command.  This bit is reserved with the MODE SELECT command.  A PS bitCD  of one indicates that the target is capable of saving the page in a'  non-volatile vendor-specific location.    E  An immediate (Immed) bit of zero indicates the target shall not send=D  completion status until the audio playback operation is terminated.   F  An Immed bit of one indicates the target shall send completion status4  as soon as the playback operation has been started.   I     NOTE 188 It is recommended that a Logical Unit type RESERVE be issued1K     prior to starting audio play operations with an Immed bit of one in any3#     multiple initiator environment.r  eG  A stop on track crossing (SOTC) bit of zero indicates the target shalleC  terminate the audio playback operation when the transfer length is F  satisfied.  Multiple tracks shall be played as necessary.  Periods ofG  time encoded as audio pause/silence at the beginning of tracks, (index   0) shall also be played.   dF  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. e   G  The audio playback rate valid (APRVal) bit value of one indicates thatiE  the format of logical blocks per second field and the logical blocks=.  per second of audio playback field are valid.  =B  The format of logical blocks addresses per second field gives theB  multiplier to be used with the logical blocks per second of audio)  playback.  This is defined in table 269.l  n7                         Table 269 - Multiplier for LBAsrE  +==============================-===================================+hE  |  Format of LBAs / Sec value  |  Multiplier for LBAs / Sec field  |yE  |------------------------------+-----------------------------------|6E  |                0h            |                1                  |=E  |              1h - 7h         |                Reserved           | E  |                8h            |                1/256              | E  |              9h - Fh         |                Reserved           | E  +==================================================================+A  d  oN     NOTE 189 This field is provided as a means to return fractional (i.e. non-G     integral) values in the logical block addresses per second of audio J     playback.  This shall occur when logical block sizes that are not even?     multiples or divisions of the physical block size are used.t  n@  The logical blocks per second of audio playback field gives theE  relationship between time and the duration of play per logical block E  address. The value in this field is to be multiplied by the value in "  format of LBAs per second field.    J     NOTE 190 The logical blocks per second of audio playback field and itsJ     companion format of LBAs per second field may not be supported by mostA     current CD-ROM devices as a modifiable mode select parameter.=  =H  The output port channel selection specifies the audio channels from theE  disc to which this output port should be connected (see table 270).  F  More than one output port may be connected to an audio channel.  More<  than one audio channel may be connected to an output port.   R<                    Table 270 - Output port channel selection=  +==========-===============================================+d=  |   Code   |  Description                                  | =  |==========+===============================================|m=  |   0000b  |  output port muted                            | =  |   0001b  |  connect audio channel 0 to this output port  | =  |   0010b  |  connect audio channel 1 to this output port  |d=  |   0100b  |  connect audio channel 2 to this output port  |6=  |   1000b  |  connect audio channel 3 to this output port  |o=  +==========================================================+=  =  =I  The channel volume control indicates the relative volume level for this  H  audio output port. A value of zero indicates the output is muted, and a-  value of FFh indicates maximum volume level.=  |I     NOTE 191 If volume controls are implemented, the default volume level|I     should be no more than 25 % of the maximum level as a personal safety      consideration.   #  14.3.3.2 CD-ROM device parameters     E  The CD-ROM parameters page (see table 271) specifies parameters that   affect all CD-ROM data types.   9                        Table 271 - CD-ROM parameters pagebP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+========+========+=====================================================|P  | 0   |   PS   |Reserved|         Page code (0Dh)                             |P  |-----+-----------------------------------------------------------------------|P  | 1   |                           Parameter length (06h)                      |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |             Reserved              |     Inactivity timer multiplier   |P  |-----+-----------------------------------------------------------------------|P  | 4   |                                                                       |P  |-----| - - -         Number of MSF - S units per MSF - M unit          - - - |P  | 5   |                                                                       |P  |-----+-----------------------------------------------------------------------|P  | 6   |                                                                       |P  |-----| - - -         Number of MSF - F units per MSF - S unit          - - - |P  | 7   |                                                                       |P  +=============================================================================+  a   A  The parameters savable (PS) bit is only used with the MODE SENSE G  command.  This bit is reserved with the MODE SELECT command.  A PS biteD  of one indicates that the target is capable of saving the page in a'  non-volatile vendor-specific location.    F  The inactivity timer multiplier specifies the length of time that theF  drive shall remain in the hold track state after completion of a seek#  or read operation (see table 272).    N     NOTE 192 Higher values in this parameter may have an adverse effect on the(     drive MTBF, in some implementations.   ?                  Table 272 - Inactivity timer multiplier valuesaO  +==================-==================-===================-==================+=O  | Inactivity timer | Minimum time in  | Inactivity timer  | Minimum time in  |MO  |    multiplier    | hold track state |    multiplier     | hold track state |bO  |------------------+------------------+-------------------+------------------|oO  |       0h         | Vendor-specific  |       8h          |      16s         |6O  |       1h         | 125 ms           |       9h          |      32s         |=O  |       2h         | 250 ms           |       Ah          |      1 min       | O  |       3h         | 500 ms           |       Bh          |      2 min       | O  |       4h         |   1 s            |       Ch          |      4 min       |=O  |       5h         |   2 s            |       Dh          |      8 min       |aO  |       6h         |   4 s            |       Eh          |     16 min       |-O  |       7h         |   8 s            |       Fh          |     32 min       |mO  +=====================================-======================================+-  -  -D  The number of S units per M unit field gives the ratio of these MSFG  address values. For media conforming to the CD-ROM and CD-DA standard,-  this value is 60. -  -D  The number of F units per S unit field gives the ratio of these MSFG  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     F  The read error recovery parameters page (see table 273) specifies theG  error recovery parameters the target shall use during any command that B  performs a data read operation to the media (e.g. READ, READ TOC,  etc.).   -?                 Table 273 - Read error recovery parameters page-P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+========+========+=====================================================|P  | 0   |   PS   |Reserved|                 Page code (01h)                     |P  |-----+-----------------------------------------------------------------------|P  | 1   |                       Parameter length (06h)                          |P  |-----+-----------------------------------------------------------------------|P  | 2   |                       Error recovery parameter                        |P  |-----+-----------------------------------------------------------------------|P  | 3   |                        Read retry count                               |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   |                           Reserved                                    |P  +=============================================================================+  =  +A  The parameters savable (PS) bit is only used with the MODE SENSEDG  command.  This bit is reserved with the MODE SELECT command.  A PS bitAD  of one indicates that the target is capable of saving the page in a'  non-volatile vendor-specific location.o  i;  The error recovery parameter bits are defined in 9.3.3.6. g  sG     NOTE 193 The implementation of error recovery procedures for CD-ROMtJ     devices is markedly different from those used for magnetic medium diskN     drives.  At least one level of error correction (i.e. CIRC) is required toJ     transfer the data stream.  Therefore, the performance of the drive mayN     differ substantially from what would be expected by sending the same error4     recovery parameters to a magnetic medium device.  SE  The correlation of the error recovery parameter and the bit settingsbF  defined for CD-ROM devices is given in table 274.  The interpretationG  of these bit settings for CD-ROM devices is given in table 275. If thesF  error recovery parameter is set to any other value, the command shallG  be terminated with CHECK CONDITION status.  The sense key shall be setlF  to ILLEGAL REQUEST and the additional sense code set to INVALID FIELD  IN PARAMETER LIST.n  e;                     Table 274 - Error recovery bit settingsf   +===========-=================+   | Error     |   Bit settings  |   | recovery  |-----------------|   | parameter | 7 6 5 4 3 2 1 0 |   |===========+=================|   |    00h    | R R 0 0 R 0 0 0 |   |    01h    | R R 0 0 R 0 0 1 |   |    04h    | R R 0 0 R 1 0 0 |   |    05h    | R R 0 0 R 1 0 1 |   |    06h    | R R 0 0 R 1 1 0 |   |    07h    | R R 0 0 R 1 1 1 |   |    10h    | R R 0 1 R 0 0 0 |   |    11h    | R R 0 1 R 0 0 1 |   |    14h    | R R 0 1 R 1 0 0 |   |    15h    | R R 0 1 R 1 0 1 |   |    20h    | R R 1 0 R 0 0 0 |   |    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 |   |    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.       |   +=============================+     l?                  Table 275 - CD-ROM error recovery descriptionseP  +=============================================================================+P  |Error recovery description                                                   |P  |-----------------------------------------------------------------------------|P  | 00h The maximum error recovery procedures available are used.  If an error  |P  |     occurs which is uncorrectable with the error correction codes (ECC) on  |P  |     the media, data transfer is terminated with CHECK CONDITION status. The |P  |     block with the error is not transferred. The sense key is set to MEDIUM |P  |     ERROR. The information bytes give the address of the block where the    |P  |     unrecovered error was detected. Recovered errors are not reported.      |P  |                                                                             |P  | 01h Only retries of the read operation and CIRC are used (layered error     |P  |     correction is not used). Only CIRC unrecovered data errors are reported.|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 bytes|P  |     give the address of the block where the unrecovered error was detected. |P  |     Recovered errors are not reported.                                      |P  |                                                                             |P  | 04h The maximum error recovery procedures available are used. Recovered data|P  |     errors are reported.  If a recovered data error occurs, 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 RECOVERED ERROR. |P  |     The information bytes give the address of the last block where a        |P  |     recovered data error was detected.                                      |P  |                                                                             |P  |     If a data error occurs that is uncorrectable with the ECC information   |P  |     available on the media, data transfer is terminated and CHECK CONDITION |P  |     status is reported. The block with the error is not transferred. The    |P  |     sense key is set to MEDIUM ERROR. The information bytes give the address|P  |     of the block where the uncorrectable error was detected.                |P  |                                                                             |P  | 05h 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 a 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 not     |P  |     transferred. The sense key is set to MEDIUM ERROR. The information bytes|P  |     give the address of the block where the unrecovered error was detected. |P  |                                                                             |P  | 06h 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 not 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 medium, data transfer is terminated with CHECK CONDITION status. |P  |     The block with the error is not transferred.  The sense key is set to   |P  |     MEDIUM ERROR. The information bytes give the address of the block where |P  |     the uncorrectable error was detected.                                   |P  +=============================================================================+  d  a  Table 275  (continued) Q  +==============================================================================+-Q  |Error recovery description                                                    ||Q  |------------------------------------------------------------------------------| Q  | 07h Only retries of the read operation are used (layer error correction is   | Q  |     not used).  CIRC recovered data errors are reported.  If a CIRC          | Q  |     recovered data error occurs, data transfer is terminated with CHECK      | Q  |     CONDITION status.  The block with the recovered error is not             |iQ  |     transferred.  The sense key is set to RECOVERED ERROR. The information   | Q  |     bytes give the address of the block where the recovered data error was   | Q  |     detected.                                                                |=Q  |                                                                              | Q  |     If an CIRC unrecovered data error occurs, data transfer is terminated    |uQ  |     with CHECK CONDITION status.  The block with the error is not            |FQ  |     transferred.  The sense key is set to MEDIUM ERROR. The information      |aQ  |     bytes give the address of the block where the unrecovered error was      |oQ  |     detected.                                                                |tQ  |                                                                              |dQ  | 10h If data transfer can be maintained, the maximum error recovery           |vQ  |     procedures available are used. (RC = 1.) If an error occurs which is     |-Q  |     uncorrectable with the error correction codes (ECC) on the media, or is  | Q  |     uncorrectable in time to maintain data transfer, the data transfer is    | Q  |     not terminated.  However, when the data transfer has completed, CHECK    |=Q  |     CONDITION status is reported.  The sense key is set to MEDIUM ERROR.     | Q  |     The information bytes give the address of the block where the first      |-Q  |     unrecovered error was detected. Recovered errors are not reported.       | Q  |                                                                              |-Q  | 11h If data transfer can be maintained, retries of the read operation and    | Q  |     CIRC are used (layered error correction is not used). (RC = 1.)  Only    ||Q  |     CIRC unrecovered data errors are reported. If a CIRC unrecovered data    | Q  |     error occurs, data transfer is not terminated. However, when the data    ||Q  |     transfer has completed, CHECK CONDITION status is reported.  The sense   |-Q  |     key is set to MEDIUM ERROR. The information bytes give the address of    | Q  |     the block where the first unrecovered error was detected.  Recovered     |+Q  |     errors are not reported.                                                 | Q  |                                                                              |-Q  | 14h If data transfer can be maintained, the maximum error recovery           | Q  |     procedures available are used. (RC = 1.)  Recovered data errors are      |=Q  |     reported.  If a recovered data error occurs, data transfer is not        |mQ  |     terminated.   However, when the data transfer has completed, CHECK       |sQ  |     CONDITION status is reported.  The sense key is set to RECOVERED ERROR.  |sQ  |     The information bytes give the address of the block where a recovered    |eQ  |     data error was detected.                                                 |eQ  |                                                                              |nQ  |     If an data error occurs that is uncorrectable with the ECC information   |rQ  |     available on the media, or is uncorrectable in time to maintain data     |hQ  |     transfer, the data transfer is not terminated.  However, when the data   |dQ  |     transfer has completed CHECK CONDITION, status is reported. The sense key|SQ  |     is set to MEDIUM ERROR. The information bytes give the address of the    |fQ  |     block where the first uncorrectable error was detected.  Reporting       |sQ  |     unrecovered errors takes precedence over reporting recovered errors.     |tQ  +==============================================================================+   e  n  k  Table 275  (continued)EP  +=============================================================================+P  |Error recovery description                                                   |P  |-----------------------------------------------------------------------------|P  | 15h If data transfer can be maintained, retries of the read operation and   |P  |     CIRC are used (layered error correction is not used). (RC = 1.)         |P  |     Recovered data errors are reported.  If a recovered data error occurs,  |P  |     data transfer is not terminated.  However, when the data transfer has   |P  |     completed CHECK CONDITION status is reported.  The sense key is set to  |P  |     RECOVERED ERROR. The information bytes give the address of the block    |P  |     where a CIRC recovered data error was detected.                         |P  |                                                                             |P  |     If an unrecovered data error occurs, data transfer is not terminated.   |P  |     However, when the data transfer has completed CHECK CONDITION status is |P  |     reported.  The sense key is set to MEDIUM ERROR. The information bytes  |P  |     give the address of the block where the first unrecovered error was     |P  |     detected.  Reporting unrecovered errors takes precedence over reporting |P  |     recovered errors.                                                       |P  |                                                                             |P  | 20h The maximum error recovery procedures available are used.  If an error  |P  |     occurs which is uncorrectable with the error correction codes (ECC) on  |P  |     the media, data transfer is terminated with CHECK CONDITION status. The |P  |     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  |     unrecovered error was detected. Recovered errors are not reported.      |P  |                                                                             |P  | 21h Only retries of the read operation and CIRC are used (layered error     |P  |     correction is not used). Only CIRC unrecovered data errors are reported.|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  |     Recovered errors are not reported.                                      |P  |                                                                             |P  | 24h The maximum error recovery procedures available are used. Recovered data|P  |     errors are reported.  If a recovered data error occurs 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 RECOVERED ERROR. |P  |     The information bytes give the address of the last block where a        |P  |     recovered data error was detected.                                      |P  |                                                                             |P  |     If a data error occurs that is uncorrectable with the ECC information   |P  |     available on the media data transfer is terminated and CHECK CONDITION  |P  |     status is reported. The block with the error is transferred. The sense  |P  |     key is set to MEDIUM ERROR. The information bytes give the address of   |P  |     the block where the uncorrectable error was detected.                   |P  +=============================================================================+  f  e  a  Table 275  (concluded)uQ  +==============================================================================+eQ  |Error recovery description                                                    |rQ  |------------------------------------------------------------------------------|tQ  | 25h Only retries of the read operation and CIRC are used (layered error      | Q  |     correction is not used).  Recovered data errors are reported.  If a      |rQ  |     recovered data error occurs, data transfer is not terminated.  However,  | Q  |     when the data transfer has completed, CHECK CONDITION status is reported.| Q  |     The sense key is set to RECOVERED ERROR. The information bytes give the  | Q  |     address of the last block where an CIRC recovered data error was         |tQ  |     detected.                                                                |yQ  |                                                                              |.Q  |     If an unrecovered data error occurs, data transfer is terminated and     ||Q  |     CHECK CONDITION status is reported. The block with the error is          | Q  |     transferred.  The sense key is set to MEDIUM ERROR.  The information     ||Q  |     bytes give the address of the block where the unrecovered error was      | Q  |     detected.                                                                | Q  |                                                                              |rQ  | 26h The maximum error recovery procedures are used.  Recovered data errors   | Q  |     are reported.  If a recovered data error occurs, data transfer is        | Q  |     terminated and CHECK CONDITION status is reported.  The block with the   | Q  |     recovered error is transferred.  The sense key is set to RECOVERED       |kQ  |     ERROR.  The information bytes give the address of the block where the    |OQ  |     recovered data error was detected.                                       |tQ  |                                                                              |=Q  |     If a data error occurs that is uncorrectable with the ECC information    |nQ  |     on the media, data transfer is terminated with CHECK CONDITION status.   |=Q  |     The block with the error is transferred. The sense key is set to MEDIUM  | Q  |     ERROR. The information bytes give the address of the block where the     |-Q  |     uncorrectable error was detected.                                        |nQ  |                                                                              | Q  | 27h Only retries of the read operation are used (layer error correction is   |KQ  |     not used).  CIRC recovered data errors are reported.  If a CIRC          | Q  |     recovered data error occurs, data transfer is terminated with CHECK      |tQ  |     CONDITION status.  The block with the recovered error is transferred.    | Q  |     The sense key is set to RECOVERED ERROR. The information bytes give the  | Q  |     address of the block where the recovered data error was detected.        | Q  |                                                                              |tQ  |     If a CIRC unrecovered data error occurs, data transfer is terminated     | Q  |     with CHECK CONDITION status. The block with the error is transferred.    |nQ  |     The sense key is set to MEDIUM ERROR. The information bytes give the     |sQ  |     address of the block where the unrecovered error was detected.           | Q  |                                                                              | Q  | 30h  Same as code 10H.                                                       | Q  |                                                                              |iQ  | 31h  Same as code 11H.                                                       |oQ  |                                                                              | Q  | 34h  Same as code 14H.                                                       |EQ  |                                                                              |RQ  | 35h  Same as code 15H.                                                       |tQ  +==============================================================================+       B  The read retry count field specifies the number of times that the8  controller shall attempt its read recovery algorithm.    rE  A CIRC recovered data error is defined as a block for which the CIRCrF  based error correction algorithm was unsuccessful for a read attempt,H  but on a subsequent read operation no error was reported. The number ofG  subsequent read operations is limited to the read retry count. Layered   error correction was not used.E        IG  A CIRC unrecovered data error is defined as a block for which the CIRC.G  based error correction algorithm was unsuccessful on all read attemptstD  up to the read retry count. Layered error correction was not used.    F  An L-EC recovered data error is defined as a block for which the CIRCC  based error correction algorithm was unsuccessful, but the layered E  error correction was able to correct the block within the read retryr  count.    G  An L-EC uncorrectable data error is defined as a block which could not F  be corrected by layered error correction within the read retry count.  a*  14.3.3.4 Verify error recovery parameters   H  The verify error recovery parameters page (see table 276) specifies theH  error recovery parameter the target shall use during verify operations.     T@                Table 276 - Verify error recovery parameters pageP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+========+========+=====================================================|P  | 0   |   PS   |Reserved|                  Page code (07h)                    |P  |-----+-----------------------------------------------------------------------|P  | 1   |                      Parameter length (06h)                           |P  |-----+-----------------------------------------------------------------------|P  | 2   |                    Error recovery parameter                           |P  |-----+-----------------------------------------------------------------------|P  | 3   |                       Verify retry count                              |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   |                           Reserved                                    |P  +=============================================================================+  R  eA  The parameters savable (PS) bit is only used with the MODE SENSE G  command.  This bit is reserved with the MODE SELECT command.  A PS bit D  of one indicates that the target is capable of saving the page in a'  non-volatile vendor-specific location.   nF  The error recovery parameters for verify operations are as defined by3  the read error recovery parameters (see 14.3.3.3).       ,  14.4 Definitions specific to CD-ROM devices  uF  14.4.1 absolute F field:  The sub-division of the S Field part of the@  absolute physical address from the beginning of the media.  OneB  physical sector.  Written on CD-ROM media in binary coded decimalI  notation.  The value is from 00bcd to 74bcd. (See 14.4.12 and 14.4.18.) T  m  mD  14.4.2 absolute M field:  The most significant part of the absoluteD  physical address from the beginning of the media. Written on CD-ROMD  media in binary coded decimal notation.  The value is from 00bcd to  74bcd.  (See 14.4.18.)   oC  14.4.3 absolute S field:  The intermediate significant part of the|G  absolute physical address from the beginning of the media.  Written on H  CD-ROM media in binary coded decimal notation.  The value is from 00bcd  to 59bcd.  (See 14.4.18.)   A  14.4.4 bcd; binary coded decimal:  The number system used on the F  physical CD-ROM and CD-DA media.  Numbers that use this notation haveH  the 'bcd' suffix attached. A byte has two four-bit values each of whichI  can have a value from 0 to 9.  The maximum value is 99bcd (99 decimal). f-  Hence the maximum number of tracks is 99bcd.T   E         Example: 00 01 02 03 ... 08 09 10 11 ... 19 20 21 ... 98 99. k  iH  14.4.5 block:  The term block refers to the data in one logical block -D  the number of bytes defined by the logical block length in the mode  block descriptor.  rG  14.4.6 blocks per sector:  The number of logical blocks read from each F  CD-ROM physical sector. The value depends on the logical block LengthC  as defined in the mode block descriptor.  The value for blocks pert  sector is:r?                        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, andB                        8 if the logical block length is 256 bytes.H         (Assuming a density code of 1 - 2 048 bytes of data per sector.)  rH  14.4.7 CD-DA; compact disc - digital audio:  The standardized media forC  recording digital audio information.  The 'Red Book' defines CD-DA   media.a  eG  14.4.8 CD-ROM; compact disc - read only memory:  A standardized mediumaD  for recording digitized audio and digital data.   CD-ROM is used toE  describe media with digital data rather than discs that encode audioh8  only.  The ISO/IEC 10149 standard defines CD-ROM media.  nD  14.4.9 CD-ROM control field:  A four bit field in the Q sub-channelG  data indicating the type of information encoded on the current track. =F  Indicates audio versus data and the type of audio encoding, etc.  The>  control field is also found in the table of contents entries.  =I  14.4.10 CD-ROM data mode:  A byte in the header of CD-ROM data sectors.  B  This indicates if data is present and if layered error correction  information is present.  -H  14.4.11 CIRC; cross interleaved reed-solomon code:  The error detectionE  and correction technique used within small frames of audio or data. R@  The CIRC bytes are present in all CD-ROM data modes.  The errorE  correction procedure which uses the CIRC bytes is referred to as the ?  CIRC based algorithm.  In most CD-ROM drives, this function iss  implemented in hardware.  e  yE  14.4.12 frame:  A physical sector on CD-ROM media.  Also the F fieldaF  unit of a MSF CD-ROM address.  The term frame is also used in the CD-:  ROM model to describe the amount of data received betweenG  synchronization patterns. 98 of these frames make a sector.  This sort C  of frame is referred to as 'small frames' where the meaning is notr  clear from context.   F  14.4.13 hold track state:  When a CD-ROM device enters the hold trackE  state the optical pick-up is maintained at an approximately constantyE  position on the media.  This allows a paused operation to be resumed E  without latency due to seeking.  Rotational latency may be incurred,t	  however.    F  14.4.14 index:  An index is a subdivision of a CD-ROM track.  A trackG  can have from 1 to 99 index numbers.  Index numbers within a track are2  sequential starting with 1. r  dF  14.4.15 lead-in area:  The area on a CD-ROM disc prior to track one. A  The main channel in the lead-in area contains audio or data nulliF  information.  This area is coded as track zero but is not addressableH  via the SCSI command set.  The Q sub-channel in this area is coded with#  the table of contents information.i  bB  14.4.16 lead-out area:  The area on a CD-ROM disc beyond the lastC  information track.  The main channel in the lead-out area contains|G  audio or data null information.  This area is coded as track AAbcd but G  is not addressable via the SCSI command set.  The READ CD-ROM CAPACITYi@  data is the first logical block address of this area minus one.  tH  14.4.17 L-EC; layered error correction:  The error correction techniqueG  used with CD-ROM data mode one sectors.  In such sectors, 276 bytes ofyF  the auxiliary data field contain L-EC bytes.  The algorithm that usesD  these bytes to perform error correction is often implemented in the  drive firmware.     E  14.4.18 MSF address:  The physical address written on CD-ROM discs. eD  Expressed as a sector count relative to either the beginning of theG  medium (absolute) or to the beginning of the current track (relative). G  As defined by the CD-DA and CD-ROM standards, each F field unit is onehE  physical sector; each S field unit is 75 F field units; each M fieldeH  unit is 60 S field units.  Valid contents of F fields are binary valuesH  from 0 through 74.  Valid contents of S fields are binary values from 0A  through 59.  Valid contents of M fields are binary values from 0 
  through 74.     D  14.4.19 output port:  A means for connecting the audio signal being/  played to equipment outside the CD-ROM device.    E  14.4.20 pause area:  A transition area at the beginning or end of annA  audio track encoded with audio silence.  This transition area isfB  required where the audio track immediately precedes a data track.  nE  14.4.21 post-gap area:  A transition area at the end of a data track G  encoded with null information.  This transition area is required whereo4  the data track immediately precedes an audio track.   D  14.4.22 pre-gap area:  A transition area at the beginning of a dataG  track encoded with null information.  This transition area is required 9  where the data track immediately follows an audio track.    G  14.4.23 relative F field:  The sub-division of the S field part of the1H  relative physical address from the beginning of the current track.  OneC  physical sector.  Written on CD-ROM medium in binary coded decimalR?  notation.  The value is from 00bcd to 74bcd.  (See 14.4.12 and   14.4.18.)    tE  14.4.24 relative M field:  The most significant part of the relative=F  physical address from the beginning of the current track.  Written onH  CD-ROM media in binary coded decimal notation.  The value is from 00bcd  to 74bcd.  (See 14.4.18.)  rD  14.4.25 relative S field:  The intermediate significant part of theD  relative physical address from the beginning of the current track. F  Written on CD-ROM medium in binary coded decimal notation.  The value(  is from 00bcd to 59bcd.  (See 14.4.18.)  aF  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 aE  second).  In the CD-ROM standard document the term block is used foreB  this unit.  There may be more than one logical block per sector. ?  Similarly, a single logical block may map to multiple sectors.C  bG  14.4.27 sub-channel:  CD-ROM and CD-DA media have a main channel and arF  sub-channel.  The sub-channel area has eight parts called P, Q, R, S,F  T, U, V, and W.  The Q-sub-channel contains information useful to theH  controller and drive, such as the control field and MSF addresses.  TheE  data rate of each sub-channel (P, Q, etc.) is 1/192nd of that of the   main channel.  mH  14.4.28 TOC:  The table of contents has information on the type of discH  and the starting address of the tracks.  This information is encoded in  the Q sub-channel.  y  rH  14.4.29 track:  A sub-division of the CD-ROM media. A disc has from oneF  to ninety-nine tracks.  The data within a track is always of the sameF  type.  A track can be either CD-ROM or CD-Audio.  A disc can start at  any track number.   F  14.4.30 track relative logical address:  An offset from the beginningA  of the recorded information on a track expressed in units of the C  logical block length.  The value is used to address logical blocks-D  relative to the beginning of a track using the relative MSF address%  encoded in the CD-ROM Q sub-channel.    D  14.4.31 transition area:  Sectors at the beginning or end of tracksE  coded with null information.  Where required by the media standards,oE  these areas have minimum lengths of 1 s or 2 s.  The maximum lengths-E  are not specified.  Transition areas at the beginning of a track are G  encoded with index zero.  Addresses within transition areas may not be-  read.  15 Scanner devices-  -  -  15.1 Model for scanner devices   4D  Scanner devices generate a digital representation of two- or three-F  dimensional objects (e.g. a page of text, a photograph, or a piece ofD  art). This is accomplished by sensing the amount of light reflectedG  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.   H  There are two types of scanners in use; in one type, the operations andF  functions of the scanner are fixed; in the other type, the operationsD  and functions are programmable and need to be set up prior to being  used for scanning objects.=  =E  The scanner device generates the data and transfers it in accordancebD  with the commands received from the initiator.  The contents of theG  data is vendor-specific; therefore, the initiator and the scanner muste*  know how to use the contents of the data.  tD  Scanners generate a digital image of an object in a two dimensionalG  plane.  The x-axis dimension is along the cross-scan direction that is C  perpendicular to the direction in which a scan occurs.  The y-axissH  dimension is along the scan direction, and is parallel to the directionE  in which a scan occurs.  The coordinates are measured from the upperpG  left hand corner of the two dimensional plane.  The x-axis measurementoH  increases in a positive manner going from left to right.  The left sideF  of the two dimensional plane (i.e. where x equals zero) is called theC  base element line.  The y-axis measurement increases in a positive F  manner going from top to bottom.  The top side of the two dimensionalH  plane (i.e. where y equals zero) is called the base line.  The scanningF  range encompasses the area in which the scanner can operate, from the@  scan line and base line to the maximum x and y position.  TheseF  conventions are adopted to aid in understanding the fields within theG  command descriptor blocks and parameters used for scanner devices.  AsDC  such this is a conceptual model and may not accurately reflect the'  physical device.   eE  The displacements used for positioning windows is independent of the ?  resolution with which a window is scanned.  The measurement ofmE  displacements is controlled by the scan measurement mode parameters.   .E  In the event of a scanner automatic creation of sub-windows within atE  defined window (i.e. the auto bit in the DEFINE WINDOW parameters isi5  one), one of the following responses is appropriate:1K     a)     the initiator may issue a GET WINDOW PARAMETERS command prior toO            any READ commands;pF     b)     if the initiator issues a READ command before issuing a GETC            WINDOW PARAMETERS command, the target shall return CHECK1L            CONDITION status.  The ILI and valid bits in the sense data shallG            be set to one.  The initiator should then issue a GET WINDOW K            PARAMETERS command.  This feature is useful when the scanner has5H            the ability to distinguish between image and text data and to&            define windows accordingly.   G  It may occur that a scanner device temporarily does not have resourcesrH  available to manage a data transfer from the initiator or does not haveC  data available to transfer to the initiator.  One of the followingd*  responses is appropriate in such a case: K     a)     A CHECK CONDITION status is returned and the sense key is set toiF            NOT READY with the appropriate additional sense code.  This?            response is applicable to a TEST UNIT READY command.dK     b)     The target disconnects until the resource or data are available,c7            and then reconnects to resume the operation.c%     c)     A BUSY status is returned.    F  If the scanner device determines that an error or exception conditionD  has occurred while executing the SCSI command from the initiator, aF  CHECK CONDITION status is returned.  A REQUEST SENSE command can thenC  be used to determine additional information regarding the error ord  exception condition.s  w  i"  15.2 Commands for scanner devices  eA  The commands for scanner devices shall be as shown in table 277.e  o<                     Table 277 - Commands for scanner devicesI  +=====================================-============-======-============+tI  |  Command name                       | Operation  | Type |  Subclause | I  |                                     |   code     |      |            |uI  |-------------------------------------+------------+------+------------| I  | CHANGE DEFINITION                   |    40h     |   O  |   8.2.1    |oI  | COMPARE                             |    39h     |   O  |   8.2.2    |fI  | COPY                                |    18h     |   O  |   8.2.3    |hI  | COPY AND VERIFY                     |    3Ah     |   O  |   8.2.4    |cI  | GET DATA BUFFER STATUS              |    34h     |   O  |  15.2.1    |uI  | GET WINDOW                          |    25h     |   O  |  15.2.2    |tI  | INQUIRY                             |    12h     |   M  |   8.2.5    |aI  | LOG SELECT                          |    4Ch     |   O  |   8.2.6    | I  | LOG SENSE                           |    4Dh     |   O  |   8.2.7    | I  | MODE SELECT(6)                      |    15h     |   O  |   8.2.8    |nI  | MODE SELECT(10)                     |    55h     |   O  |   8.2.9    |aI  | MODE SENSE(6)                       |    1Ah     |   O  |   8.2.10   |eI  | MODE SENSE(10)                      |    5Ah     |   O  |   8.2.11   |.I  | OBJECT POSITION                     |    31h     |   O  |  15.2.3    |nI  | READ                                |    28h     |   M  |  15.2.4    |lI  | READ BUFFER                         |    3Ch     |   O  |   8.2.12   | I  | RECEIVE DIAGNOSTIC RESULTS          |    1Ch     |   O  |   8.2.13   |gI  | RELEASE UNIT                        |    17h     |   M  |  10.2.9    |rI  | REQUEST SENSE                       |    03h     |   M  |   8.2.14   |nI  | RESERVE UNIT                        |    16h     |   M  |  10.2.10   |iI  | SCAN                                |    1Bh     |   O  |  15.2.5    |cI  | SET WINDOW                          |    24h     |   M  |  15.2.7    |eI  | SEND                                |    2Ah     |   O  |  15.2.6    |rI  | SEND DIAGNOSTIC                     |    1Dh     |   M  |   8.2.15   |eI  | TEST UNIT READY                     |    00h     |   M  |   8.2.16   |CI  | WRITE BUFFER                        |    3Bh     |   O  |   8.2.17   |uI  |----------------------------------------------------------------------|oI  |Key:  M = command implementation is mandatory.                        |fI  |      O = command implementation is optional.                         |sI  +======================================================================+a  f  cG  All other operation codes for scanner devices are  reserved for future   standardization..  p  e&  15.2.1 GET DATA BUFFER STATUS command  oH  The GET DATA BUFFER STATUS command (see table 278) provides a means forH  the initiator to get information about the data buffer.  Information isG  returned only for window identifiers for which a SCAN command has beenc  received (see 15.2.5).f  a=                    Table 278 - GET DATA BUFFER STATUS command P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (34h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |            Reserved               |  Wait  |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   | (MSB)                                                                 |P  |-----+---                        Allocation length                        ---|P  | 8   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+  .  9I  A wait bit of zero indicates that the target shall respond immediately. yF  A wait bit of one indicates that the target shall wait for image data5  to be available before returning scan status data.  r  t<  The data buffer status data format is defined in table 279.  ::                      Table 279 - Data buffer status formatP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 1   |                           Data buffer status length                   |P  |-----+---                                                                 ---|P  | 2   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                           |  Block |P  |=====+=======================================================================|P  |     |                           Data buffer status descriptor(s)            |P  |=====+=======================================================================|P  | 0   |                           Window identifier                           |P  |-----+-----------------------------------------------------------------------|P  | 1   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                           Available data buffer                       |P  |-----+---                                                                 ---|P  | 4   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 5   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 6   |                           Filled data buffer                          |P  |-----+---                                                                 ---|P  | 7   |                                                                 (LSB) |P  +=============================================================================+  i   E  The data buffer status length indicates the length, in bytes, of thehF  following scan status data that is available to be transferred duringB  the DATA IN phase. The data buffer status length does not includeB  itself.  The data buffer status data transferred to the initiatorG  includes zero or more data buffer status descriptors.  Each descriptorsG  returns information for the window specified by the window identifier.m  uF  The block bit specifies the buffering capabilities of the scanner.  AF  block bit of one indicates that the data buffer is full and all imageD  data must be transferred to the initiator before the scan operationD  resumes.  A block bit of zero indicates that the data buffer is notE  full and scan operations can continue with the available data bufferh  space.o  sC  The available data buffer field indicates, in bytes, the amount ofSH  buffer available for transfers from the initiator.  This field is validG  only in scanners with the ability to accept data from an initiator forT  processing.     C  The filled data buffer field indicates the amount of image data ine/  bytes available for transfer to the initiator.a  i  15.2.2 GET WINDOW command   @  The GET WINDOW command (see table 280) provides a means for the?  initiator to get information about previously defined windows.o  e7                          Table 280 - GET WINDOW commandoP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (25h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |              Reserved             | Single |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Window identifier                           |P  |-----+-----------------------------------------------------------------------|P  | 6   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 7   |                           Transfer length                             |P  |-----+---                                                                 ---|P  | 8   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+  |   G  A single bit of one specifies that a single window descriptor shall be D  returned for the specified window identifier.  A single bit of zero=  specifies that window descriptors be returned for all window A  identifiers that were defined by a SET WINDOWS command or by the0.  target, if the automatic bit was set to one.   1G  The GET WINDOW data shall consist of a header (see table 281) followed2E  by one or more window descriptors.  Each window descriptor specifies ;  the location, size, and scanning method used for a window.    9                        Table 281 - Get window data header P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   | (MSB)                                                                 |P  |-----+---                        Window data length                       ---|P  | 1   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 6   | (MSB)                                                                 |P  |-----+---                        Window descriptor length                 ---|P  | 7   |                                                                 (LSB) |P  +=============================================================================+      F  The window data length specifies the length in bytes of the followingG  data that is available to be transferred.  The window data length does=C  not include itself.  If the allocation length is not sufficient toeD  return all the get window data, the window data length shall not be*  adjusted to reflect the truncation data.   -G  The window descriptor length specifies the length in bytes of a single C  window descriptor.  Each descriptor shall be of equal length.  The-G  first forty-eight bytes are defined in this International Standard and <  the remaining bytes in each descriptor are vendor-specific.  -1  The window descriptors are defined in table 282.   39                       Table 282 - Window descriptor bytes P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Window identifier                           |P  |-----+-----------------------------------------------------------------------|P  | 1   |                           Reserved                           |  Auto  |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                        X-Axis resolution                        ---|P  | 3   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 4   | (MSB)                                                                 |P  |-----+---                        Y-Axis resolution                        ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   | (MSB)                                                                 |P  |- - -+- - -                      X-Axis upper left                      - - -|P  | 9   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 10  | (MSB)                                                                 |P  |- - -+- - -                      Y-Axis upper left                      - - -|P  | 13  |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 14  | (MSB)                                                                 |P  |- - -+- - -                      Window width                           - - -|P  | 17  |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 18  | (MSB)                                                                 |P  |- - -+- - -                      Window length                          - - -|P  | 21  |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 22  |                           Brightness                                  |P  |-----+-----------------------------------------------------------------------|P  | 23  |                           Threshold                                   |P  |-----+-----------------------------------------------------------------------|P  | 24  |                           Contrast                                    |P  |-----+-----------------------------------------------------------------------|P  | 25  |                           Image composition                           |P  |-----+-----------------------------------------------------------------------|P  | 26  |                           Bits per pixel                              |P  |-----+-----------------------------------------------------------------------|P  | 27  | (MSB)                                                                 |P  |-----+---                        Halftone pattern                         ---|P  | 28  |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 29  |  RIF   |                  Reserved         |      Padding type        |P  |-----+-----------------------------------------------------------------------|P  | 30  | (MSB)                                                                 |P  |-----+---                        Bit ordering                             ---|P  | 31  |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 32  |                           Compression type                            |P  |-----+-----------------------------------------------------------------------|P  | 33  |                           Compression argument                        |P  |-----+-----------------------------------------------------------------------|P  | 34  |                                                                       |P  |- - -+---                        Reserved                                 ---|P  | 39  |                                                                       |P  |-----+-----------------------------------------------------------------------|P  | 40  |                                                                       |P  |- - -+---                        Vendor-specific parameter byte(s)        ---|P  | n   |                                                                       |P  +=============================================================================+  T  eA  The window identifier specifies the window defined by the window=H  descriptor. A window is referenced by the window identifier during data!  transfers and parameter updates.    F  When used with the SET WINDOW command, an automatic (auto) bit of oneF  indicates that the target is allowed to create sub-windows within theH  window specified.  An auto bit of zero indicates that the target is not  allowed to create sub-windows.    E  When used with the GET WINDOW command, an auto bit of zero indicates-C  that the window was defined directly by the SET WINDOW command.  A H  value of one indicates that the window was defined by the target.  ThisA  is a sub-window within a window defined by a SET WINDOW command.s  eH  The window identifiers assigned by the target shall be unique and shallD  not be currently in use.  The parameters for the sub-windows may be(  retrieved using the GET WINDOW command.   F  The x-axis resolution field specifies the resolution in the scan lineH  direction.  The unit of measure is picture elements (pixels) per inch. 4  A value of zero specifies the default resolution.    -F  The y-axis resolution field specifies the resolution in the base lineD  direction.  The unit of measure is scan lines per inch.  A value of)  zero specifies the default resolution.  -  -C  The x-axis upper left field specifies the x-axis coordinate of the G  upper left corner of the window.  This coordinate is measured from the C  scan line using the target's current measurement unit divisor (see   15.3.3.1).   aC  The y-axis upper left field specifies the y-axis coordinate of the G  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).-  -F  The window width field specifies the width of window in the scan lineD  direction.  The window width is measured using the target's current)  measurement unit divisor (see 15.3.3.1).=  =G  The window length field specifies the length of the window in the basesB  line direction.  The window length is measured using the target's1  current measurement unit divisor (see 15.3.3.1).i  sH  The brightness field specifies the level of brightness used to scan theG  object.  A value of zero specifies the default brightness or automatic E  brightness control, if it is supported.  Any other value indicates arE  relative brightness setting, with 255 being the highest setting, onei=  being the lowest setting, and 128 being the nominal setting.e  dB  The threshold field specifies the threshold at which scan data isA  converted to binary data.  A value of zero specifies the default=H  threshold or automatic threshold control if it is supported.  Any otherG  value indicates relative threshold setting, with 255 being the highest A  setting, one being the lowest setting, and 128 being the nominal=	  setting.=  =D  The contrast field specifies the level of contrast used to scan theE  object.  A value of zero specifies the default contrast or automatic C  contrast control, if it is supported.  Any other value indicates a|C  relative contrast setting, with 255 being the highest setting, one =  being the lowest setting, and 128 being the nominal setting.-  -E  The halftone field specifies the level of halftone at which the scan H  data is converted to binary data.  The values in this field are vendor-D  specific.  The halftone field is used in conjunction with the image  composition field.    A  The image composition field specifies the type of scan operation-D  requested.  The image composition is defined as shown in table 283.   9                       Table 283 - Image composition codes-;  +=============-==========================================+-;  |    Code     |  Description                             | ;  |-------------+------------------------------------------|-;  |     00h     |  Bi-level black & white                  |S;  |     01h     |  Dithered/halftone black & white         | ;  |     02h     |  Multi-level black & white (gray scale)  |l;  |     03h     |  Bi-level RGB colour                     | ;  |     04h     |  Dithered/halftone RGB colour            |=;  |     05h     |  Multi-level RGB colour                  |=;  |  06h - FFh  |  Reserved                                | ;  +========================================================+r  .  hH  The bits per pixel field specifies the number of bits used to represent"  the intensity of a single colour.   E  A reverse image format (RIF) bit of zero indicates that white pixelseF  are indicated by zeros and black pixels are indicated by ones.  A RIFG  bit of one indicates that white pixels are to be indicated by ones andlF  black pixels are to be indicated by zeros.  The RIF bit is applicable4  only for images represented by one bit per pixel.    hD  The padding type field specifies how the target shall pad the imageE  data transmitted to the initiator if it is not an integral number ofp2  bytes.  The padding type is defined in table 284.  -4                            Table 284 - Padding types2  +=============-=================================+2  |    Code     |  Description                    |2  |-------------+---------------------------------|2  |     00h     |  No padding                     |2  |     01h     |  Pad with 0's to byte boundary  |2  |     02h     |  Pad with 1's to byte boundary  |2  |     03h     |  Truncate to byte boundary      |2  |  04h - FFh  |  Reserved                       |2  +===============================================+      H  The bit ordering field specifies the order in which data is transferredG  to the host from the window.  The bit ordering specifies the direction F  of pixels in a scan line, the direction of scan lines within a windowH  and the image data packing within a byte.  The values in this field are  vendor-specific.     (A  The compression type and compression argument fields specify the-G  compression technique to be applied to the image data (see table 285).    =                   Table 285 - Compression types and argumentsAP  +=============-===============================================-===============+P  | Compression |  Description                                  |  Compression  |P  |   code      |                                               |   argument    |P  |-------------+-----------------------------------------------+---------------|P  |     00h     |  No compression                               |   Reserved    |P  |     01h     |  CCITT group III, 1 dimensional               |   Reserved    |P  |     02h     |  CCITT group III, 2 dimensional               |   K factor    |P  |     03h     |  CCITT group IV, 2 dimensional                |   Reserved    |P  |  04h - 0Fh  |  Reserved                                     |   Reserved    |P  |     10h     |  Optical character recognition (OCR)          |Vendor-specific|P  |  11h - 7Fh  |  Reserved                                     |   Reserved    |P  |  80h - FFh  |  Vendor-specific                              |Vendor-specific|P  +=============================================================================+        15.2.3 OBJECT POSITION command|  |A  The OBJECT POSITION command (see table 286) provides positioning-F  functions.  Absolute as well as relative positioning is provided.   AD  target shall return CHECK CONDITION status and set the sense key toC  ILLEGAL REQUEST if a positioning function is requested that is not   supported.    9                       Table 286 - OBJECT POSITION command-P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (31h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |    Reserved     |      Position function   |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                           Count                                       |P  |-----+---                                                                 ---|P  | 4   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 8   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+  -  -H  The position function field specifies the requested function (see table  287).   6                          Table 287 - Position function)  +=============-========================+ )  |  Position   |  Description           | )  |  function   |                        | )  |-------------+------------------------|-)  |    000b     |  Unload object         |-)  |    001b     |  Load object           | )  |    010b     |  Absolute positioning  ||)  |    011b     |  Relative positioning  |-)  |    100b     |  Rotate object         |n)  |    101b     |  Reserved              | )  |    110b     |  Reserved              |=)  |    111b     |  Reserved              |=)  +======================================+n     nK     a)     Unload Object.  This position function specifies that the objectrL            shall be positioned for removal.  If upon receipt of this commandM            there is no object loaded, the target shall return a GOOD status. eF            This condition shall not be considered as an error.  If theL            target is unable to unload the object (i.e. paper jam or mis-feedI            condition), the target shall return CHECK CONDITION status and 3            set the sense key sense to MEDIUM ERROR.d  nL     b)     Load object.  This position function specifies that the object isL            to be loaded and positioned to the base line.  If upon receipt ofJ            this command there is a object already loaded, the target shallJ            returns GOOD status.  This condition shall not be considered asL            an error.  If an object is not loaded and the target is unable toI            load an object, the target shall return CHECK CONDITION statusnH            and set the EOM bit to one and the sense key to MEDIUM ERROR.  eK     c)     Absolute positioning.  This position function specifies that theiL            object is to be positioned at a y-axis displacement from the baseG            line.  The y-axis displacement is determined using the count G            field and the target's current measurement unit divisor (see H            15.3.3.1).  A count field of zero positions the object at the            base line.  e   D         Any other value in the count field shall cause the target toA         position the object that number of units in the scan linefK         direction.  If there is no object loaded or if the specified y-axisiC         displacement is not achieved, the target shall return CHECK H         CONDITION status and set the EOM bit to one and the sense key to         MEDIUM ERROR.i   K     d)     Relative positioning.  This position function specifies that the.J            object is to be positioned at a y-axis displacement relative toG            the current position.  The y-axis displacement is determinedsJ            using the count field and the target's current measurement unitJ            divisor (see 15.3.3.1).  A count field of zero causes no change'            in position of the object.     oE         A positive value in the count field shall cause the target toaA         position the object that number of units in the scan linetJ         direction.  If the scan range is exceeded, the target shall returnK         CHECK CONDITION status.  The EOM bit is set to one,  the ILI bit iseH         set to one, and the sense key is set to MEDIUM ERROR.  The validB         bit is set to one and the information bytes are set to theG         difference (residue) between the requested count and the actuali          number of units moved.     K         A negative value (e.g. twos complement notation) in the count fieldeJ         shall cause the target to position the object that number of unitsE         toward the base line.  If there is no object loaded or if the G         specified y-axis displacement is not achieved, the target shallhH         return CHECK CONDITION status and set the EOM bit to one and theH         sense key to MEDIUM ERROR.  If the base line is encountered, theJ         target shall position the object at the base line and return CHECKI         CONDITION status.  The ILI bit is set to one and the sense key isiA         set to MEDIUM ERROR.  The valid bit is set to one and theiI         information bytes are set to the difference (residue) between thee=         requested count and the actual number of units moved.   gK     e)     Rotate object.  This position function specifies that the object=A            is rotated in an anti-clockwise direction expressed in L            thousandths of a degree.  The count field specifies the number of0            units that the object is to be moved.  0I         The count field is used with the position function to specify thet#         displacement of the object.l  |  15.2.4 READ command  RH  The READ command (see table 288) requests that the target transfer data  to the initiator.  |4                             Table 288 - READ commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (28h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |             Reserved                       |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Data type code                              |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   | (MSB)                                                                 |P  |-----+---                        Data type qualifier                      ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 7   |                           Transfer length                             |P  |-----+---                                                                 ---|P  | 8   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+      D  The transfer data type distinguishes between the different types ofH  data that may be transferred between the initiator and the target.  The/  types of transfers are specified in table 289.-  -5                           Table 289 - Data type codes $  +=============-===================+$  |    Code     |  Description      |$  |-------------+-------------------|$  |     00h     |  Image            |$  |     01h     |  Vendor-specific  |$  |     02h     |  Halftone mask    |$  |     03h     |  Gamma function   |$  |  04h - 7Fh  |  Reserved         |$  |  80h - FFh  |  Vendor-specific  |$  +=================================+     iE  The data type qualifier field provides a means to differentiate dataFE  transfers of the same data type code.  The values used in this field|  are vendor-specific.   iD  The transfer length specifies the number of blocks the target shallG  transfer to the initiator during the DATA IN phase.  The block size is1D  the current block size in the mode parameters block descriptor (seeE  8.3.3).  A transfer length of zero is not considered an error and not  data shall be transferred.  A  tB  If the target transfers less than transfer length blocks, a CHECKE  CONDITION status shall be returned.   The ILI bit is set to one, thesB  valid bit is set to one, and the information bytes are set to theC  difference (residue) between the requested transfer length and the-&  actual number of blocks transferred.    G  This command shall be terminated with a status of RESERVATION CONFLICT E  if any reservation access conflict (see 10.2.10) exists, and no data=  shall be transferred.  =  15.2.5 SCAN command  =B  The SCAN command (see table 290) requests the target begin a scan  operation.    4                             Table 290 - SCAN commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (1Bh)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |                  Reserved                  |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Transfer length                             |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+  -  -@  The transfer length specifies the length in bytes of the windowA  identifier list that shall be sent during the DATA OUT phase.  A=F  transfer length of zero indicates that no data shall be transferred. 1  This condition shall not be considered an error.e  dH  The window identifier list consists of zero or more window identifiers,1  each of which specifies a window to be scanned. =  =     15.2.6 SEND command  tF  The SEND command (see table 291) transfers data from the initiator to  the target.  -4                             Table 291 - SEND commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (2Ah)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |             Reserved                       |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Data type code                              |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   | (MSB)                                                                 |P  |-----+---                        Data type qualifier                      ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 7   |                           Transfer length                             |P  |-----+---                                                                 ---|P  | 8   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+      C  The data type code and data type qualifier are defined in the READi  command (see 15.2.4). i  oD  The transfer length specifies the number of blocks the target shallG  transfer from the initiator during the DATA OUT phase.  The block size G  is the current block size in the mode parameters block descriptor (see E  8.3.3).  A transfer length of zero is not considered an error and nol  data shall be transferred.  t  sG  This command shall be terminated with a status of RESERVATION CONFLICTtE  if any reservation access conflict (see 10.2.10) exists, and no datae  shall be transferred.     15.2.7 SET WINDOW command   @  The SET WINDOW command (see table 292) provides a means for theF  initiator to specify one or more windows within the scanning range of  the device.  u7                          Table 292 - SET WINDOW commandaP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (24H)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |                  Reserved                  |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 6   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 7   |                           Transfer length                             |P  |-----+---                                                                 ---|P  | 8   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+      E  The transfer length specifies the length, in bytes, of the data that=D  shall be sent during the DATA OUT phase.  A transfer length of zeroE  indicates that no window parameters data shall be transferred.  This-,  condition shall not be considered an error.  -H  The window parameters data shall consist of a header followed by one or?  more window descriptors.  Each window descriptor specifies the-9  location, size, and scanning method used for a window.      4  The set window data header is defined in table 293.  -9                        Table 293 - Set window data header-P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 1   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 6   | (MSB)                                                                 |P  |-----+---                        Window descriptor length                 ---|P  | 7   |                                                                 (LSB) |P  +=============================================================================+  e  sB  The window descriptor length specifies the length, in bytes, of aF  single window descriptor.  Each descriptor shall be of equal length. F  The first 48 bytes are defined in this International Standard and the8  remaining bytes in each descriptor are vendor-specific.  c9  See table 282 for the definition of a window descriptor.   i$  15.3 Parameters for scanner devices  e  f  15.3.1 Diagnostic parameterss   @  This subclause defines the descriptors and pages for diagnostic'  parameters used with scanner devices. e  bH  The diagnostic page codes for scanner devices are defined in table 294.  n8                        Table 294 - Diagnostic page codesP  +=============-==================================================-============+P  |  Page code  |  Description                                     | Subclause  |P  |-------------+--------------------------------------------------+------------|P  |     00h     |  Supported diagnostic pages                      |  8.3.1.1   |P  |  01h - 7Fh  |  Reserved                                        |            |P  |  80h - FFh  |  Vendor-specific pages                           |            |P  +=============================================================================+     n  15.3.2 Log parameters   D  This subclause defines the descriptors and pages for log parameters  used with scanner devices.   =A  The log page codes for scanner devices are defined in table 295.|  35                            Table 295 - Log page codes P  +=============-==================================================-============+P  |  Page code  |  Description                                     | Subclause  |P  |-------------+--------------------------------------------------+------------|P  |     01h     |  Buffer over-run/under-run page                  |  8.3.2.1   |P  |     03h     |  Error counter page (read) page                  |  8.3.2.2   |P  |     07h     |  Last n error events page                        |  8.3.2.3   |P  |     06h     |  Non-medium error page                           |  8.3.2.4   |P  |     00h     |  Supported log pages                             |  8.3.2.5   |P  |  08h - 2Fh  |  Reserved                                        |            |P  |     3Fh     |  Reserved                                        |            |P  |  30h - 3Eh  |  Vendor-specific pages                           |            |P  +=============================================================================+        15.3.3 Mode parameters    E  This subclause defines the descriptors and pages for mode parameters=  used with scanner devices.   -F  The mode parameter list, including the mode parameter header and mode'  block descriptor, is defined in 8.3.3.g  eE  The medium-type code field is contained in the mode parameter headerh;  (see 8.3.3).  This field is reserved for scanners devices.   eG  The device specific parameter field is contained in the mode parameterdA  header (see 8.3.3).  This field is reserved for scanner devices.    @  The density code field is contained in the mode parameter blockB  descriptor (see table 8.3.3).  This field is reserved for scanner	  devices.a   B  The mode page codes for scanner devices are defined in table 296.  =5                           Table 296 - Mode page codes|P  +=============-==================================================-============+P  |  Page code  |  Description                                     | Subclause  |P  |-------------+--------------------------------------------------+------------|P  |     0Ah     |  Control mode page                               |  8.3.3.1   |P  |     02h     |  Disconnect-reconnect page                       |  8.3.3.2   |P  |     03h     |  Measurement units page                          | 15.3.3.1   |P  |     09h     |  Peripheral device page                          |  8.3.3.3   |P  |     01h     |  Reserved                                        |            |P  |  03h - 08h  |  Reserved                                        |            |P  |  0Bh - 1Fh  |  Reserved                                        |            |P  |     00h     |  Vendor-specific (does not require page format)  |            |P  |  20h - 3Eh  |  Vendor-specific (page format required)          |            |P  |     3Fh     |  Return all pages                                |            |P  |             |     (valid only for the MODE SENSE command)      |            |P  +=============================================================================+         15.3.3.1 Measurement units page   B  The measurement units page (see table 297) specifies the units ofD  measurement used for calculating the displacement of window and for  positioning an object.    E  The measurement units are independent of the horizontal and vertical   scan resolutions.     9                        Table 297 - Measurement units page P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+========+========+=====================================================|P  | 0   |   PS   |Reserved|         Page code (03h)                             |P  |-----+-----------------------------------------------------------------------|P  | 1   |                           Parameter length (06h)                      |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Basic measurement unit                      |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   | (MSB)                                                                 |P  |-----+---                        Measurement unit divisor                 ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   |                           Reserved                                    |P  +=============================================================================+      A  The parameters savable (PS) bit is only used with the MODE SENSE-F  command.  This bit is reserved for the MODE SELECT command.  A PS bitD  of one indicates that the target is capable of saving the page in a'  non-volatile vendor-specific location.-  -C  The basic measurement unit field is defined in table 298.  Targetse8  shall use inches as the default basic measurement unit.  -9                       Table 298 - Basic measurement units    +=============-===============+   |    Code     |  Description  |   |-------------+---------------|   |     00h     |  Inch         |   |     01h     |  Millimetre   |   |     02h     |  Point        |   |  03h - FFh  |  Reserved     |   +=============================+  -  -E  The measurement unit divisor specifies the number of units needed to B  equal one basic measurement unit.  Targets shall use 1 200 as theG  default measurement unit divisor.  If a value of zero is specified the|D  target shall return CHECK CONDITION status and set the sense key to  ILLEGAL REQUEST.-   H     NOTE 194 A target that does not implement this page or only supportsL     default values uses twelve hundredths (1/1200) of an inch as the unit of     measure.  --  15.4 Definitions specific to scanner devices-  -A  15.4.1 base element line:  An x-axis displacement equal to zero.    9  15.4.2 base line:  An y-axis displacement equal to zero.=  =H  15.4.3 beginning-of-medium:  A x-axis and y-axis of zero displacement. G  Alternatively this is being positioned at the intersection of the baseA  and scan lines.  eC  15.4.4 end-of-medium:  The maximum x-axis and y-axis displacement.t  s-  15.4.5 image:  The digital result of a scan.r  a4  15.4.6 object:  The original or item being scanned.  fE  15.4.7 pixel:  Picture-element, which is the smallest photo sight ins  the array.f   ?  15.4.8 platen:  The surface on which the target is positioned.    C  15.4.9 scan:  An operation that generates a digital image from the   reflected light of an object.  a>  15.4.10 scan line:  A y-axis displacement from the base line.  =G  15.4.11 scanning range:  The total area that a scanner can generate an3D  image from.  For two dimensional objects this may correspond to the$  largest object that can be scanned.   E  15.4.12 window:   All or part of the scanning range of a scanner.  A=/  window defines the part of the object scanned.R  r       Optical memory devices      |&  16.1 Model for optical memory devices  -D  An optical memory device is a device that can potentially support aD  variety of optical media, (e.g. read-only, write-once, erasable, orG  reversible).  In several respects, an optical memory device is similar F  to a direct-access device.  However, optical memory devices typicallyD  offer features that are not available with other devices, including&  very large capacity removable media.    H  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.  -B  This standard has specific device types for write-once and CD-ROMG  devices that also use optical media, but are not capable of supporting E  several types of optical media.  A device that uses write-once media-G  can be an optical memory device.  Devices that use read-only media can D  be optical memory devices; however, devices using CD-ROM media haveH  certain unique characteristics and should not be implemented as optical  memory devices.   F  A model of optical memory devices is complicated by the nature of oneA  of its potential advantages, that it can support media which hasnF  different characteristics.  There are three types of optical media inH  general use, read-only, write-once and reversible.  Read-only media areF  typically used for publishing applications requiring dissemination ofE  large amounts of data, since the data can be replicated on a disk atnE  low cost.  Write-once media are used in applications that have large.H  backup or archiving requirements.  It is also used in applications thatG  need large amounts of on-line reference information.  Reversible mediaeG  is typically used in applications that need large amounts of temporary A  storage (e.g. a graphics workstation), and can take advantage of=D  removable media.  In some applications, reversible media drives are(  used in place of direct-access devices.   F  Reversible media usually need to be reversed (erased, blanked) beforeG  new data can be written.  In such cases an erase operation is requiredeF  before data can be written.  Some optical memory devices perform thisB  erase operation implicit with each write operation that typicallyA  impacts the data throughput. Some devices can perform the erase  I  separately.  The ERASE command may be used to erase areas of the medium =E  with a corresponding increase in data throughput on subsequent writeeG  operations.  Products using optical media should not be implemented asvG  direct-access devices, due to the overhead penalty on performance from2G  the emulation and the lack of support in direct-access devices to take=F  advantage of the sophisticated features available with optical memory  devices.  d  |B  The type of medium supported by the device and the type of mediumF  currently loaded can be determined by examining the MODE SENSE data. F  One unique feature of optical memory devices is support of media withC  mixed types (e.g. media with read-only and write-once areas).  The D  INQUIRY command informs the initiator that the target is an opticalH  memory device; the initiator should then determine the medium type fromD  the MODE SENSE data.  The initiator needs to be cognizant of mediumF  type since the device's characteristics can change when the media are	  changed.e  dG  Write-once media can have valid data written to a logical block once.  G  This is an important feature where audit trails and permanent archives E  are needed.  Many optical memory devices supporting write-once media D  have the ability to update a logical block, preserving the previousF  generation of data.  These devices usually provide a means to recoverH  the previous data through use of commands that allow read access to theH  different generations of data that are stored at the same logical block	  address.o  dF  An important requirement in dealing with optical media is determiningH  which logical blocks contain written data and which are blank.  A blankG  logical block is one that is properly initialized so that data writtent@  to it can be recovered.  The logical blocks usually have a flagF  associated with each that indicates whether they have been written or  not.   eD  Many of the strategies used to manage write once and erasable mediaC  depend on being able to determine the boundary between written andcA  blank areas of the medium.  The MEDIUM SCAN command is useful in95  finding blank areas for subsequent write operations.=  =  16.1.1 Defect management=  =F  Defect management can be performed on logical blocks by updating in aG  manner similar to that used by direct-access devices with the REASSIGN-C  BLOCKS command.  The advantage of using the updating (which is not D  supported by direct-access devices) is access to the previous data.  cH  The update operation assigns an alternate physical block to the logicalH  block while simultaneously writing the data to the block.  commands areB  provided to allow the recovery of previous generations of updated  blocks.  |I  Defect management on optical-memory devices is usually vendor-specific.  H  However there are standards for some types of optical-memory media thatC  specify defect management techniques.  These standards, where they C  exist, may supersede the implementation requirements pertaining tor;  error and defect reporting in this International Standard.   m  16.1.2 Error reporting    C  If any of the following conditions occur during the execution of a =  command the target shall return CHECK CONDITION status.  TheDD  appropriate sense key and additional sense code should be set.  TheD  following list illustrates some error conditions and the applicableH  sense keys.  The list does not provide an exhaustive enumeration of all6  conditions that may cause the CHECK CONDITION status.  ic  Condition                                                                                Sense Key o  Invalid logical block address                                                                          ILLEGAL o                                                                                                         REQUEST5   k  Unsupported option requested                                                                       ILLEGAL|k                                                                                                     REQUEST|  P|  Target reset or medium change since last command from this initiator                                                            UNIT ATTENTION  |p  Self diagnostic failed                                                                                 HARDWAREm                                                                                                         ERROR    p  Unrecovered read error                                                                             MEDIUM ERRORa                                                                                    HARDWARE ERROR-  -p  Recovered read error                                                                            RECOVERED ERROR   {  Overrun or other error that might be resolved by repeating the command                                                       ABORTED command   r  Attempt to write on write protected medium                                                                   DATAu                                                                                                               PROTECT-  -u  Attempt to read a blank or previously unwritten block                                                               =  BLANK CHECK  =B  Attempt to write a previously written block and blank checking is  enabled          BLANK CHECKi  no  Attempt to write on read-only medium                                                                      DATAir                                                                                                            PROTECT  u  e@  In the case of an invalid logical block address, the sense dataC  information field shall be set to the logical block address of thea  first invalid address.n  nB  In the case of an attempt to read a blank or previously unwrittenD  block, the sense data information field shall be set to the logicalF  block address of the first blank block encountered.  The data read up$  to that block shall be transferred.  =C  In the case of an attempt to write a previously written block whenfG  blank checking is enabled, the sense information field shall be set toaD  the logical block address of the first non-blank block encountered.  l)  16.2 Commands for optical memory devices   uH  The commands for optical memory devices shall be as shown in table 299.   ?                 Table 299 - Commands for optical memory devicespI  +=====================================-============-======-============+uI  |  Command name                       | Operation  | Type |  Subclause |-I  |                                     |   code     |      |            |1I  |-------------------------------------+------------+------+------------|nI  | CHANGE DEFINITION                   |    40h     |   O  |   8.2.1    |tI  | COMPARE                             |    39h     |   O  |   8.2.2    | I  | COPY                                |    18h     |   O  |   8.2.3    |sI  | COPY AND VERIFY                     |    3Ah     |   O  |   8.2.4    |oI  | ERASE(10)                           |    2Ch     |   O  |  16.2.1    |iI  | ERASE(12)                           |    ACh     |   O  |  16.2.2    |aI  | FORMAT UNIT                         |    04h     |   O  |   9.2.1    |tI  | INQUIRY                             |    12h     |   M  |   8.2.5    |1I  | LOCK UNLOCK CACHE                   |    36h     |   O  |   9.2.2    |sI  | LOG SELECT                          |    4Ch     |   O  |   8.2.6    |.I  | LOG SENSE                           |    4Dh     |   O  |   8.2.7    |hI  | MEDIUM SCAN                         |    38h     |   O  |  16.2.3    |eI  | MODE SELECT(6)                      |    15h     |   O  |   8.2.8    | I  | MODE SELECT(10)                     |    55h     |   O  |   8.2.9    |sI  | MODE SENSE(6)                       |    1Ah     |   O  |   8.2.10   | I  | MODE SENSE(10)                      |    5Ah     |   O  |   8.2.11   |rI  | PRE-FETCH                           |    34h     |   O  |   9.2.3    |iI  | PREVENT ALLOW MEDIUM REMOVAL        |    1Eh     |   O  |   9.2.4    |uI  | READ(6)                             |    08h     |   O  |   9.2.5    |iI  | READ(10)                            |    28h     |   M  |   9.2.6    |rI  | READ(12)                            |    A8h     |   O  |  16.2.4    |rI  | READ BUFFER                         |    3Ch     |   O  |   8.2.12   |dI  | READ CAPACITY                       |    25h     |   M  |   9.2.7    |eI  | READ DEFECT DATA(10)                |    37h     |   O  |   9.2.8    | I  | READ DEFECT DATA(12)                |    B7h     |   O  |  16.2.5    |oI  | READ GENERATION                     |    29h     |   O  |  16.2.6    |eI  | READ LONG                           |    3Eh     |   O  |   9.2.9    |aI  | READ UPDATED BLOCK                  |    2Dh     |   O  |  16.2.7    |lI  | REASSIGN BLOCKS                     |    07h     |   O  |   9.2.10   |yI  | RECEIVE DIAGNOSTIC RESULTS          |    1Ch     |   O  |   8.2.13   | I  | RELEASE                             |    17h     |   M  |   9.2.11   |eI  | REQUEST SENSE                       |    03h     |   M  |   8.2.14   |aI  | RESERVE                             |    16h     |   M  |   9.2.12   |fI  | REZERO UNIT                         |    01h     |   O  |   9.2.13   |lI  | SEARCH DATA EQUAL(10)               |    31h     |   O  |   9.2.14.1 |uI  | SEARCH DATA EQUAL(12)               |    B1h     |   O  |  16.2.8    |aI  | SEARCH DATA HIGH(10)                |    30h     |   O  |   9.2.14.2 |aI  | SEARCH DATA HIGH(12)                |    B0h     |   O  |  16.2.8    |.I  | SEARCH DATA LOW(12)                 |    B2h     |   O  |  16.2.8    |II  | SEEK(6)                             |    0Bh     |   O  |   9.2.15   |aI  | SEEK(10)                            |    2Bh     |   O  |   9.2.15   |bI  | SEND DIAGNOSTIC                     |    1Dh     |   M  |   8.2.15   | I  | SET LIMITS(10)                      |    33h     |   O  |   9.2.16   |fI  | SET LIMITS(12)                      |    B3h     |   O  |  16.2.9    |yI  | START STOP UNIT                     |    1Bh     |   O  |   9.2.17   |rI  | SYNCHRONIZE CACHE                   |    35h     |   O  |   9.2.18   | I  | TEST UNIT READY                     |    00h     |   M  |   8.2.16   |nI  | UPDATE BLOCK                        |    3Dh     |   O  |  16.2.10   |eI  | VERIFY(10)                          |    2Fh     |   O  |  16.2.11   |nI  | VERIFY(12)                          |    AFh     |   O  |  16.2.12   |hI  | WRITE(6)                            |    0Ah     |   O  |   9.2.20   |TI  | WRITE(10)                           |    2Ah     |   M  |  16.2.13   |yI  | WRITE(12)                           |    AAh     |   O  |  16.2.14   |eI  | WRITE AND VERIFY(10)                |    2Eh     |   O  |  16.2.15   |.I  | WRITE AND VERIFY(12)                |    AEh     |   O  |  16.2.16   |sI  | WRITE BUFFER                        |    3Bh     |   O  |   8.2.17   | I  | WRITE LONG                          |    3Fh     |   O  |   9.2.23   |iI  |----------------------------------------------------------------------|iI  |Key:  M = command implementation is mandatory.                        |eI  |      O = command implementation is optional.                         |rI  +======================================================================+m     iE  The following codes are vendor-specific: 20h, 21h, 22h, 23h, and C0h A  through FFh.  All remaining codes for optical memory devices are %  reserved for future standardization.e  e  16.2.1 ERASE(10) commando  nE  The ERASE(10) command (see table 300) requests that the target eraserG  the specified number of blocks starting at the specified logical blockmE  address on the medium.  As used here, erased means either the medium B  shall be erased, or a pattern shall be written on the medium thatF  appears to the target as no data present.  The blocks erased shall beA  considered blank for purposes of blank checking (see 16.1).  ThehH  previous data recorded on the medium, if any, shall not be recoverable.  t6                          Table 300 - ERASE(10) commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (2Ch)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   |   Logical unit number    |     Reserved    |  ERA   |Reserved| RelAdr |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                                                                       |P  |-----+---                        Logical block address                    ---|P  | 4   |                                                                       |P  |-----+---                                                                 ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   | (MSB)                                                                 |P  |-----+---                        Transfer length                          ---|P  | 8   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+      G  The erase all (ERA) bit set to one indicates that all remaining blocks H  on the medium shall be erased.  If the ERA bit is set to one and if theG  number of blocks is not zero, the target shall return CHECK CONDITION, F  and the sense key shall be set to ILLEGAL REQUEST, with an additional$  sense code of INVALID FIELD IN CDB.   H  See 9.2.2 for a description of the RelAdr bit and logical block address  field.    F  The transfer length specifies the number of contiguous logical blocksG  that shall be erased when the ERA bit is zero.  If the ERA bit is zero E  a transfer length of zero indicates that no blocks shall be erased.  E  This condition shall not be considered an error and no data shall beRE  erased.  Any other value indicates the number of logical blocks that   shall be erased.    G  This command shall be terminated with a status of RESERVATION CONFLICT C  if any reservation access conflict (see 9.2.12) exists and no data   shall be erased.A  TI     NOTE 195 This command allows the user to separate the erase and write N     operations.  This may increase system performance in certain applications.     16.2.2 ERASE(12) command    E  The ERASE(12) command (see table 301) requests that the target erasetG  the specified number of blocks starting at the specified logical block   address on the medium.    6                          Table 301 - ERASE(12) commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (ACh)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   |   Logical unit number    |     Reserved    |  ERA   |Reserved| RelAdr |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                                                                       |P  |-----+---                        Logical block address                    ---|P  | 4   |                                                                       |P  |-----+---                                                                 ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 7   |                                                                       |P  |-----+---                        Transfer length                          ---|P  | 8   |                                                                       |P  |-----+---                                                                 ---|P  | 9   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 10  |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 11  |                           Control                                     |P  +=============================================================================+      F  See the ERASE(10) command (16.2.1) for a description of the fields in  this command.  |  16.2.3 MEDIUM SCAN command    D  The MEDIUM SCAN command (see table 302) requests that the target toA  scan the medium for a contiguous set of written or blank logical|
  blocks.     7                         Table 302 - MEDIUM SCAN command P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                            Operation code (38h)                       |P  |-----+-----------------------------------------------------------------------|P  | 1   |  Logical unit number     |   WBS  |   ASA  |   RSD  |   PRA  | RelAdr |P  |-----+-----------------------------------------------------------------------|P  | 2   |  (MSB)                                                                |P  |-----+----                                                                ---|P  | 3   |                                                                       |P  |-----+----                      Logical block address                     ---|P  | 4   |                                                                       |P  |-----+----                                                                ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   |                            Reserved                                   |P  |-----+-----------------------------------------------------------------------|P  | 7   |                            Reserved                                   |P  |-----+-----------------------------------------------------------------------|P  | 8   |                            Parameter list length                      |P  |-----+-----------------------------------------------------------------------|P  | 9   |                            Control                                    |P  +=============================================================================+      H  A written block search (WBS) bit of zero indicates that the scan is forG  blank blocks.  A WBS bit of one indicates that the scan is for written   blocks.  9E  An advanced scan algorithm (ASA) bit of zero indicates that the scan9F  area is scanned in sequential order (as selected by the RSD bit).  AnH  ASA bit of one indicates to the target that the written and blank areasF  within the scan area form contiguous extents (as opposed to scattered5  blocks).  This indication is advisory to the target.    I     NOTE 196 The purpose of this bit is to allow the target to use a more H     advanced algorithm (such as a binary search) to locate the requested     blocks.    D  A reverse scan direction (RSD) bit of zero indicates the scan shallF  begin with the first logical block of the scan area. A RSD bit of oneG  indicates the scan shall begin with the last logical block of the scan   area.   G  A partial results acceptable (PRA) bit of zero indicates that the scan F  shall not be considered satisfied until a contiguous set of blocks isH  found within the scan area that is at least equal in size to the numberC  of blocks requested, and meets the other criteria specified in the-H  command descriptor block.  A PRA bit of one indicates that the scan mayH  be satisfied by a contiguous set of blocks within the scan area that isG  less than the number of blocks requested, and meets the other criteria=+  specified in the command descriptor block.    H  See 9.2.2 for a description of the RelAdr bit and logical block address  field.h  A?  The parameter list length specifies the length in bytes of the G  parameter list that shall be transferred during the DATA OUT phase.  A1B  parameter list length of zero indicates that the number of blocksE  requested field has a value of one, and the number of blocks to scaneF  field has a value of zero.  This condition shall not be considered anG  error.  The contents of the parameter list are specified in table 303.    ;                      Table 303 - MEDIUM SCAN parameter listiP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 1   |                                                                       |P  |-----+---                        Number of blocks requested               ---|P  | 2   |                                                                       |P  |-----+---                                                                 ---|P  | 3   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 4   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 5   |                                                                       |P  |-----+---                        Number of blocks to scan                 ---|P  | 6   |                                                                       |P  |-----+---                                                                 ---|P  | 7   |                                                                 (LSB) |P  +=============================================================================+  -  -B  A link bit of zero indicates a non-linked command; if the scan isI  satisfied, the command shall be terminated with a CONDITION MET status. aE  A REQUEST SENSE command can then be issued to determine the starting G  logical block address of the area that meets the request.  If the scan-F  is not satisfied and no error occurs, the command shall be terminated  with GOOD status.   H  A link bit of one indicates that a command is linked to the MEDIUM SCANF  command; if the search is satisfied, CONDITION MET status is returnedA  and the next command is executed.  If the RelAdr bit in the nextoF  command is one, the logical block address of the next command is usedE  as a displacement from the logical block address at which the search D  was satisfied.    If a linked scan is not satisfied, the command isG  terminated with a CHECK CONDITION status.  A REQUEST SENSE command mayn  then be issued.  dB  A REQUEST SENSE command following a satisfied MEDIUM SCAN command  shall:eE     a)     return a sense key of EQUAL if the scan was satisfied by aiI            contiguous set of blocks equal in size to the number of blocks K            requested. If the PRA bis is one and the scan was satisfied by arB            contiguous set of blocks less than the number of blocksE            requested, then a sense key of NO SENSE shall be returned; +     b)     return the valid bit set to one;NI     c)     return the logical block address of the first logical block of K            the contiguous set of blocks that satisfied the scan criteria int!            the information bytes;oJ     d)     return the number of contiguous logical blocks meeting the scan>            criteria in the command specific information bytes.  rE  A REQUEST SENSE command following an unsatisfied MEDIUM SCAN commandg  shall:pJ     a)     return a sense key of NO SENSE if no errors occurred during the            command execution;d,     b)     return the valid bit set to zero.  =D  The number of blocks requested field specifies the number of blocksF  that meet the specified requirements.  The number of blocks requestedF  field, if set to zero, indicates that the scan shall not take place. 1  This shall not be considered an error condition.=  =E  The number of blocks to scan field specifies the length in blocks of D  the area to be scanned on the medium.  The number of blocks to scanF  field, if set to zero, indicates that the scan shall continue for allD  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) command   G  The READ(12) command (see table 304) requests that the target transfer A  data to the initiator from the medium.  See the READ(10) command B  (9.2.6) for a complete description of the fields in this command.   6                           Table 304 - READ(12) commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (A8h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   |   Logical unit number    |   DPO  |   FUA  |     Reserved    | RelAdr |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                                                                       |P  |-----+---                        Logical block address                    ---|P  | 4   |                                                                       |P  |-----+---                                                                 ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 7   |                                                                       |P  |-----+---                        Transfer length                          ---|P  | 8   |                                                                       |P  |-----+---                                                                 ---|P  | 9   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 10  |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 11  |                           Control                                     |P  +=============================================================================+  -  -$  16.2.5 READ DEFECT DATA(12) command  |C  The READ DEFECT DATA(12) command (see table 305) requests that the F  target transfer the medium defect data to the initiator. See the READH  DEFECT DATA(10) command (9.2.8) for a description of the fields in this	  command.    <                     Table 305 - READ DEFECT DATA(12) commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (B7h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   |   Logical unit number    | Plist  | GList  | Defect list format       |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 6   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 7   |                                                                       |P  |-----+---                        Allocation length                        ---|P  | 8   |                                                                       |P  |-----+---                                                                 ---|P  | 9   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 10  |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 11  |                           Control                                     |P  +=============================================================================+     iG  The READ DEFECT DATA(12) list header (see table 306) contains an eighth:  byte header, followed by zero or more defect descriptors.  =>                   Table 306 - READ DEFECT DATA(12) list headerP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 1   |          Reserved        | PList  | GList  | Defect list format       |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 5   |                                                                       |P  |-----+---                        Defect list length                          |P  | 6   |                                                                       |P  |-----+---                                                                 ---|P  | 7   |                                                                 (LSB) |P  |=============================================================================|P  |                              Defect descriptors                             |P  |=====-=======================================================================|P  | 0   |                                                                       |P  |-----+---                                                                 ---|P  | n   |                                                                       |P  +=============================================================================+  =  =F  See the description of the READ DEFECT DATA defect list (see 9.2.1.1)0  for a description of the fields in this header.  d  16.2.6 READ GENERATION command   mE  The READ GENERATION command (see table 307) requests that the targetEA  transfer to the initiator the maximum generation address for theo  logical block specified.   t9                       Table 307 - READ GENERATION commandrP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (29h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   |   Logical unit number    |             Reserved              | RelAdr |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                                                                       |P  |-----+---                        Logical block address                    ---|P  | 4   |                                                                       |P  |-----+---                                                                 ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 8   |                           Allocation length                           |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+  h  eH  See 9.2.2 for a description of the RelAdr bit and logical block address  field.   n2  The READ GENERATION data is defined in table 308.   <                    Table 308 - Maximum generation data blockP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   | (MSB)                                                                 |P  |-----+---                       Maximum generation address                ---|P  | 1   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 2   |                          Reserved                                     |P  |-----+-----------------------------------------------------------------------|P  | 3   |                          Reserved                                     |P  +=============================================================================+  -  -D  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   E  The READ UPDATED BLOCK(10) command (see table 309) requests that the H  target transfer data to the initiator from the specified generation and  logical block.s   =                    Table 309 - READ UPDATED BLOCK(10) command P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (2Dh)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   |   Logical unit number    |   DPO  |   FUA  |     Reserved    | RelAdr |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                                                                       |P  |-----+---                        Logical block address                    ---|P  | 4   |                                                                       |P  |-----+---                                                                 ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   | Latest | (MSB)                                                        |P  |-----+------------               Generation address                          |P  | 7   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 8   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+      F  See 9.2.6 for a description of the cache control bits (DPO and FUA). H  See 9.2.2 for a description of the RelAdr bit and logical block address  field.u  r;  One block of data is transferred during the DATA IN phase.-  -H  The latest bit determines the meaning of the generation address field. H  A latest bit of zero indicates that the generation address is specifiedG  relative to the first generation of the block; generation address zero-A  specifies the first generation.  Increasing generation addresses   specify later generations.-  -G  A latest bit of one indicates that the generation address is specified|H  relative to the latest generation of the block; generation address zeroG  specifies the most recent generation.  Increasing generation addresses-  specify earlier generations.    A  If the requested generation does not exist, the command shall be+G  terminated with CHECK CONDITION status.  The sense key shall be set to F  BLANK CHECK, and the additional sense code shall be set to GENERATION  DOES NOT EXIST.   G  This command shall be terminated with a status of RESERVATION CONFLICT7C  if any reservation access conflict (see 9.2.12) exists and no data   shall be transferred.      16.2.8 SEARCH DATA(12) commands   H  The SEARCH DATA(12) commands (see table 310) search one or more logicalE  blocks for equality or inequality to a data pattern.  See the SEARCH C  DATA(10) commands (9.2.14) for a description of the fields in this 	  command.    :                       Table 310 - SEARCH DATA(12) commandsP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (B0h, B1h, B2h)              |P  |-----+-----------------------------------------------------------------------|P  | 1   |   Logical unit number    | Invert |    Reserved     | SpnDat | RelAdr |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                                                                       |P  |-----+---                        Logical block address                    ---|P  | 4   |                                                                       |P  |-----+---                                                                 ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 7   |                                                                       |P  |-----+---                        Transfer length                          ---|P  | 8   |                                                                       |P  |-----+---                                                                 ---|P  | 9   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 10  |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 11  |                           Control                                     |P  +=============================================================================+        16.2.9 SET LIMITS(12) command  =D  The SET LIMITS(12) command (see table 311) defines the range withinF  which subsequent linked commands may operate.  See the SET LIMITS(10)B  command (9.2.16) for a description of the fields in this command.   9                        Table 311 - SET LIMITS(12) command P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (B3h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   |   Logical unit number    |         Reserved         | RdInh  | WrInh  |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                                                                       |P  |-----+---                        Logical block address                    ---|P  | 4   |                                                                       |P  |-----+---                                                                 ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 7   |                                                                       |P  |-----+---                        Number of blocks                         ---|P  | 8   |                                                                       |P  |-----+---                                                                 ---|P  | 9   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 10  |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 11  |                           Control                                     |P  +=============================================================================+       -  -  16.2.10 UPDATE BLOCK command    B  The UPDATE BLOCK command (see table 312) requests that the targetH  logically replace data on the medium with the data sent during the DATA  OUT phase.9  28                         Table 312 - UPDATE BLOCK commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (3Dh)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   |   Logical unit number    |            Reserved               | RelAdr |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                                                                       |P  |-----+---                        Logical block address                    ---|P  | 4   |                                                                       |P  |-----+---                                                                 ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 8   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+  -  -H  See 9.2.2 for a description of the RelAdr bit and logical block address  field.u  r=  One block of data is transferred during the DATA OUT phase. -  -N     NOTE 197 See the MODE Parameters (16.3) for a description of the behaviourM     of the UPDATE BLOCK command relative to the enable blank check (EBC) bit.    H  This standard does not define the result of a WRITE command issued to aH  block previously updated by an UPDATE BLOCK command when blank checking  is disabled.    F     NOTE 198 It is recommended that the target inhibit this behaviour.   A  A logical block may be updated until the alternate block area is E  exhausted.  The alternate blocks used for the update operation shall G  not be reported in the READ CAPACITY data. If the alternate block area G  is exhausted, the command shall be terminated with CHECK CONDITION and-F  the sense key shall be set to  MEDIUM ERROR, and the additional sense0  code set to NO DEFECT SPARE LOCATION AVAILABLE.  -@  If the report updated block read parameter specifies posting ofH  recovered errors for a read operation of a logical block that has had a@  successful update operation performed, occurs the command shallH  terminate with a CHECK CONDITION status.  The sense key shall be set toC  RECOVERED ERROR and the additional sense code set to UPDATED BLOCK-  READ.  -  16.2.11 VERIFY(10) command   9G  The VERIFY command (see table 313) requests that the target verify the   data on the medium.  =5                            Table 313 - VERIFY command=P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (2Fh)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   |   Logical unit number    |   DPO  |Reserved| BlkVfy | BytChk | RelAdr |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                                                                       |P  |-----+---                        Logical block address                    ---|P  | 4   |                                                                       |P  |-----+---                                                                 ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   | (MSB)                                                                 |P  |-----+---                        Verification length                         |P  | 8   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+  -  +@  If the MODE SELECT command is implemented, and the Verify ErrorH  Recovery Parameters page is also implemented, then the current settingsC  in that page define the verification criteria. If the Verify Error-C  Recovery Parameters page is not implemented, then the verification   criteria is vendor unique.    E  A byte check (BytChk) bit of zero causes a medium verification to be F  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 datacE  transferred from the initiator.  The data shall be transferred as it G  would be for a WRITE command.  If the compare is unsuccessful, for any E  reason, the target shall return CHECK CONDITION status and the sense    key shall be set to MISCOMPARE.   B  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 be H  considered an error. The target shall return CHECK CONDITION status andH  the sense key shall be set to ILLEGAL REQUEST, and the additional sense"  code set to INVALID FIELD IN CDB.   H  See 9.2.6 for a description of the cache control bits (DPO).  See 9.2.2E  for a description of the RelAdr bit and logical block address field.    C  The verification length specifies the number of contiguous logical H  blocks of data or blanks that shall be verified.  A verification lengthB  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-  -G  The VERIFY(12) command (see table 314) requests that the target verify D  the data on the medium.  See the VERIFY(10) command (16.2.11) for a+  description of the fields in this command.=  =7                          Table 314 - VERIFY(12) commandmP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (AFh)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   |   Logical unit number    |   DPO  |Reserved| BlkVfy | BytChk | RelAdr |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                                                                       |P  |-----+---                        Logical block address                    ---|P  | 4   |                                                                       |P  |-----+---                                                                 ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 7   |                                                                       |P  |-----+---                        Verification length                      ---|P  | 8   |                                                                       |P  |-----+---                                                                 ---|P  | 9   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 10  |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 11  |                           Control                                     |P  +=============================================================================+        16.2.13 WRITE(10) command  |E  The WRITE(10) command (see table 315) requests that the target write-7  the data transferred from the initiator to the medium.    6                          Table 315 - WRITE(10) commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (2Ah)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   |   Logical unit number    |   DPO  |   FUA  |   EBP  |Reserved| RelAdr |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                                                                       |P  |-----+---                        Logical block address                    ---|P  | 4   |                                                                       |P  |-----+---                                                                 ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   | (MSB)                                                                 |P  |-----+---                        Transfer length                             |P  | 8   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+      B  An erase by-pass (EBP) bit of zero indicates that the device willD  default to the normal write operation.  An EBP bit of one indicatesC  that the target is allowed to by-pass the erase operation prior to H  writing the data. When accessing write-once media, the EBP bit shall be  considered reserved.=  =F  See 9.2.6 for a description of the cache control bits (DPO and FUA). H  See 9.2.2 for a description of the RelAdr bit and logical block address  field.h  .F  The transfer length specifies the number of contiguous logical blocksH  of data that shall be transferred.  A transfer length of zero indicates@  that no data shall be transferred.  This condition shall not beC  considered an error and no data shall be written.  Any other valueAB  indicates the number of logical blocks that shall be transferred.  IG  This command shall be terminated with a status of RESERVATION CONFLICTbD  if any reservation access conflict (see 9.2.12) exists, and no data  shall be written.  d  16.2.14 WRITE(12) command   E  The WRITE(12) command (see table 316) requests that the target writee@  the data transferred from the initiator to the medium.  See theD  WRITE(10) command (16.2.13) for a description of the fields in this	  command.e  c6                          Table 316 - WRITE(12) commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (AAh)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   |   Logical unit number    |   DPO  |   FUA  |   EBP  |Reserved| RelAdr |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                                                                       |P  |-----+---                        Logical block address                    ---|P  | 4   |                                                                       |P  |-----+---                                                                 ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 7   |                                                                       |P  |-----+---                        Transfer length                          ---|P  | 8   |                                                                       |P  |-----+---                                                                 ---|P  | 9   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 10  |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 11  |                           Control                                     |P  +=============================================================================+  -  -%  16.2.15 WRITE AND VERIFY(10) command-  -C  The WRITE AND VERIFY(10) command (see table 317) requests that the G  target write the data transferred from the initiator to the medium and=0  then verify that the data is correctly written.  o<                     Table 317 - WRITE AND VERIFY(10) commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (2Eh)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   |   Logical unit number    |   DPO  |Reserved|   EBP  | BytChk | RelAdr |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                                                                       |P  |-----+---                        Logical block address                    ---|P  | 4   |                                                                       |P  |-----+---                                                                 ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   | (MSB)                                                                 |P  |-----+---                        Transfer length                             |P  | 8   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+  |  1@  If the MODE SELECT command is implemented, and the Verify ErrorH  Recovery Parameters page is also implemented, then the current settingsC  in that page define the verification criteria. If the Verify Error C  Recovery Parameters page is not implemented, then the verification-  criteria is vendor unique.-  -E  A byte check (BytChk) bit of zero causes a medium verification to be F  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 data E  transferred from the initiator.  The data shall be transferred as it-G  would be for a WRITE command.  If the compare is unsuccessful, for any|E  reason, the target shall return CHECK CONDITION status and the sense    key shall be set to MISCOMPARE.   B  An erase by-pass (EBP) bit of zero indicates that the device willD  default to the normal write operation.  An EBP bit of one indicatesC  that the target is allowed to by-pass the erase operation prior to F  writing the data.  When accessing write-once media, the EBP bit shall  be considered reserved.  +H  See 9.2.6 for a description of the cache control bits (DPO).  See 9.2.2E  for a description of the RelAdr bit and logical block address field.    F  The transfer length specifies the number of contiguous logical blocksH  of data that shall be transferred.  A transfer length of zero indicatesG  that no logical blocks shall be transferred.  This condition shall noteC  be considered as an error and no data shall be written.  Any other H  value indicates the number of logical blocks that shall be transferred.   %  16.2.16 WRITE AND VERIFY(12) command   -C  The WRITE AND VERIFY(12) command (see table 318) requests that the G  target write the data transferred from the initiator to the medium and-C  then verify that the data is correctly written.  See the WRITE AND C  VERIFY(10) command (16.2.15) for a description of the bits in this-	  command.-  -<                     Table 318 - WRITE AND VERIFY(12) commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (AEh)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   |   Logical unit number    |   DPO  |Reserved|   EBP  | BytChk | RelAdr |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                                                                       |P  |-----+---                        Logical block address                    ---|P  | 4   |                                                                       |P  |-----+---                                                                 ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 7   |                                                                       |P  |-----+---                        Transfer length                          ---|P  | 8   |                                                                       |P  |-----+---                                                                 ---|P  | 9   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 10  |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 11  |                           Control                                     |P  +=============================================================================+  =  =+  16.3 Parameters for optical memory devices   p     16.3.1 Diagnostic parameterst  e@  This subclause defines the descriptors and pages for diagnostic.  parameters used with optical memory devices.   -D  The diagnostic page codes for optical memory devices are defined in  table 319.d   8                        Table 319 - Diagnostic page codesP  +=============-==================================================-============+P  |  Page code  |  Description                                     | Subclause  |P  |-------------+--------------------------------------------------+------------|P  |     00h     |  List of supported parameters page               |  8.3.1.1   |P  |  01h - 3Fh  |  Reserved (for all device type pages)            |            |P  |     40h     |  Translate address page                          |  9.3.1     |P  |  41h - 7Fh  |  Reserved                                        |            |P  |  80h - FFh  |  Vendor-specific pages                           |            |P  +=============================================================================+  1  r  16.3.2 Log parameters  tD  This subclause defines the descriptors and pages for log parameters#  used with optical memory devices. s  pH  The log page codes for optical memory devices are defined in table 320.  65                            Table 320 - Log page codes=P  +=============-==================================================-============+P  |  Page code  |  Description                                     | Subclause  |P  |-------------+--------------------------------------------------+------------|P  |     01h     |  Buffer over-run/under-run page                  |  8.3.2.1   |P  |     03h     |  Error counter page (read) page                  |  8.3.2.2   |P  |     05h     |  Error counter page (verify) page                |  8.3.2.2   |P  |     02h     |  Error counter page (write) page                 |  8.3.2.2   |P  |     07h     |  Last n error events page                        |  8.3.2.3   |P  |     00h     |  List of supported parameters page               |  8.3.2.5   |P  |     06h     |  Non-media error page                            |  8.3.2.4   |P  |     04h     |  Reserved                                        |            |P  |  08h - 2Fh  |  Reserved                                        |            |P  |  30h - 3Eh  |  Vendor-specific                                 |            |P  |     3Fh     |  Reserved                                        |            |P  +=============================================================================+  -  -  16.3.3 Mode parameters-  -E  This subclause defines the descriptors and pages for mode parameters #  used with optical memory devices.     F  The mode parameter list, including the mode parameter header and mode(  block descriptor, are defined in 8.3.3.   E  The medium-type code field is contained in the mode parameter headergE  (see 8.3.3).  Table 321 defines the medium-type code values used for   optical memory devices.   >                   Table 321 - Optical memory medium-type codesP  +=============-===============================================================+P  |    Code     |  Description                                                  |P  |-------------+---------------------------------------------------------------|P  |     00h     |  Default (only one medium type supported)                     |P  |     01h     |  Optical read-only medium                                     |P  |     02h     |  Optical write-once medium                                    |P  |     03h     |  Optical reversible or erasable medium                        |P  |     04h     |  Combination of read-only and write-once medium               |P  |     05h     |  Combination of read-only and reversible or erasable medium   |P  |     06h     |  Combination of write-once and reversible or erasable medium  |P  |  07h - 7Fh  |  RESERVED                                                     |P  |  80h - FFh  |  Vendor-specific                                              |P  +=============================================================================+      G  The device specific parameter field is contained in the mode parameter=E  header (see 8.3.3).  Table 322 defines the device specific parameter (  values used for optical memory devices.  -B               Table 322 - Optical memory device specific parameterP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |=====+========+=================+========+==========================+========|P  |     |   WP   |    Reserved     | DPOFUA |           Reserved       |  EBC   |P  +=============================================================================+  -   B  When used with the MODE SELECT command the WP bit is not defined.  4E  When used with the MODE SENSE command, a write protected (WP) bit of B  zero indicates that the medium is write enabled.  A WP bit of oneG  indicates that the medium is write protected.  For read-only media the   WP bit is reserved.  |C  When used with the MODE SELECT command the DPOFUA bit is reserved.-  -E  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).-  -E  For the MODE SELECT command, an enable blank check (EBC) bit of zero B  advises the target to disable the blank checking operation of theF  medium during write operations or during an UPDATE BLOCK command.  AnF  EBC bit of one enables blank checking.  If a non-blank block is foundG  during a write operation, the command shall be terminated with a CHECK-F  CONDITION status and the sense key shall be set to BLANK CHECK.  If aG  blank block is found during an UPDATE BLOCK command, the command shall=H  be terminated with a CHECK CONDITION status, and the sense key shall beC  set to BLANK CHECK.  For read-only media, the EBC bit is reserved.,  eD  For the MODE SENSE command, an enable blank check (EBC) bit of zeroG  indicates that blank checking of the medium during write operations isnH  disabled.  An EBC bit of one indicates that blank checking during writeG  and update operations is enabled.  For read-only media, the EBC bit ist
  reserved.   @  The density code field is contained in the mode parameter blockH  descriptor (see 8.3.3).  Table 323 defines the density code values used  for optical memory devices.  w<                     Table 323 - Optical memory density codesR  +========-======================================================================+R  |Density |                      Optical media                                   |R  | code   |                                                                      |R  |--------+----------------------------------------------------------------------|R  |  00h   |Default density (currently mounted density)                           |R  |        |----------------------------------------------------------------------|R  |        | Diameter | Type|  Sector   | Tracks | Sides | Servo| Reference |Notes|R  |        | mm (in)  |     |   size    |        |       |      | standard  |     |R  |        |----------+-----+-----------+--------+-------+------+-----------+-----|R  |  01h   | 86 (3,5) | R/W | 512/1 024 | 12 500 |   1   |      |  660-D    | 1   |R  |  02h   | 89 (3,5) | R/W | 512/1 024 | 12 500 |   2   |      |  581-D    | 1   |R  |  03h   |130 (5,25)| R/W | 512/1 024 | 18 750 |   2   |  CS  |  607-I    | 1   |R  |  04h   |130 (5,25)| W-O | 512/1 024 | 30 000 |   2   |  SS  |  655-D    | 1,2 |R  |  05h   |130 (5,25)| W-O | 512/1 024 | 20 000 |   2   |  SS  |  659-D    | 1,3 |R  |  06h   |130 (5,25)| W-O | 512/1 024 | 18 750 |   2   |  CS  |  457-D    | 1   |R  |  07h   |200 (8,0) |     |           |        |       |      |  407-D    | 1,4 |R  |  08h   |300 (12,0)|     |   1 024   |        |   2   |      |  408-D    | 1,4 |R  |  09h   |356 (14,0)|     |   1 024   | 56 350 |   2   |      |  456-D    | 1   |R  |        |          |     |           |        |       |      |           |     |R  |-------------------------------------------------------------------------------|R  | Codes 80h - FFh are vendor-specific, all other codes are reserved             |R  |-------------------------------------------------------------------------------|R  |Key:    Type    Description                 Servo  Description                 |R  |        ----    -----------                 -----  ----------------            |R  |        R/W     Erasable                     CS    Continuous servo            |R  |        W-O     Write once                   SS    Sampled servo               |R  |        R/O     Read only                                                      |R  |-------------------------------------------------------------------------------|R  | NOTES                                                                         |R  |  1 The reference standard refers to an ANSI X3B11 project under               |R  | development.  The project may have several documents describing different     |R  | aspects of the media. Please contact the Secretariat for current information  |R  | on status and availability.                                                   |R  |  2 RZ modulation.                                                             |R  |  3 4/15 modulation.                                                           |R  |  4 This project is not presently active.                                      |R  +===============================================================================+      G  The mode page codes for optical memory devices are shown in table 324.    5                           Table 324 - Mode page codes-P  +=============-==================================================-============+P  |  Page code  |  Description                                     | Subclause  |P  |-------------+--------------------------------------------------+------------|P  |     08h     |  Caching page                                    |  9.3.3.1   |P  |     0Ah     |  Control mode page                               |  8.5.3.1   |P  |     02h     |  Disconnect-reconnect page                       |  8.3.3.2   |P  |     0Bh     |  Medium types supported page                     |  9.3.3.4   |P  |     06h     |  Optical memory page                             | 16.3.3.1   |P  |     09h     |  Peripheral device page                          |  8.3.3.3   |P  |     01h     |  Read-write error recovery page                  |  9.3.3.6   |P  |     07h     |  Verify error recovery page                      |  9.3.3.8   |P  |  03h - 05h  |  Reserved                                        |            |P  |  0Ch - 1Fh  |  Reserved                                        |            |P  |     00h     |  Vendor-specific (does not require page format)  |            |P  |  20h - 3Eh  |  Vendor-specific (page format required)          |            |P  |     3Fh     |  Return all pages                                |            |P  |             |     (valid only for the MODE SENSE command)      |            |P  +=============================================================================+  =  =  16.3.3.1 Optical memory page    G  The optical memory page (see table 325) defines parameters for control   of optical memory devices.l  m7                         Table 325 - Optical memory pageyP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+========+========+=====================================================|P  | 0   |   PS   |Reserved|         Page code (06h)                             |P  |-----+-----------------------------------------------------------------------|P  | 1   |                           Parameter length (02h)                      |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                           |  RUBR  |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  +=============================================================================+      A  The parameters savable (PS) bit is only used with the MODE SENSE G  command.  This bit is reserved with the MODE SELECT command.  A PS bit D  of one indicates that the target is capable of saving the page in a(  non-volatile, vendor-specific location.  =D  A report updated block read (RUBR) bit of zero indicates the targetG  shall not report an error when a command performs a successful read ofeG  a block that has been updated.  A RUBR bit of one indicates the targeteH  shall terminate a command that performs a read of a block that has beenD  updated with CHECK CONDITION status, the sense key set to RECOVEREDD  ERROR, the additional sense code set to UPDATED BLOCK READ, and theF  data shall be transferred to the initiator.  The default state of theE  RUBR bit for write-once devices (as reported in the INQUIRY command)e  shall be one.  =;  16.4 Definitions specific to write-once and optical memory=  devices   G  16.4.1 blank:  The logical block contains no information detectable by|G  the target, or is written with a pattern that appears to the target as-D  no data present.  The logical block is considered ready for a write  operation.    F  16.4.2 generation:   Indicates a relative revision level of a logicalE  block that has been updated via the UPDATE BLOCK command.  A logical E  block that has never been updated has only one generation associatede	  with it.    E  16.4.3 read-only medium:   This is medium that may not be written byoH  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 withoutH  destroying the previous data.  After a block has been updated, a normal>  read returns the most recent generation of the data.  Earlier2  generations are still available after the update.  =D  16.4.5 write-once medium:   This is medium that may be written onlyE  once by the initiator.  Logical blocks on write-once media that haveaE  not been written are considered blank.  Logical blocks on write-oncea7  media that have been written may not be written again.         17 Medium-changer devices  v   !  17.1 Medium-changer device model=  =C  Medium changer devices mechanize the movement of media to and from|B  primary devices (such as disk or tape drives) and other locationsG  within the range of the medium changer. The medium changer command set=4  is based on a physical model of this functionality.  |H  This command set supports varied physical implementations of the medium?  changer function. Most of these variations are hidden from thewH  initiator by the high level of function provided by the MOVE MEDIUM andF  EXCHANGE MEDIUM commands and by the generalized nature of the elementC  addressing scheme. However, initiators may need to be aware of the <  capabilities of the particular medium changer device. TheseD  characteristics and capabilities are conveyed via MODE SENSE pages.  b  17.1.1 Medium-changer elementsw   D  The medium-changer command set uses as its address space the set ofG  physical locations and mechanisms within the scope of a medium changercH  device. The term element is used throughout this clause to refer to oneG  member of the medium changer address space. Each element is a discretenG  physical entity that may hold zero or one physical unit of media - onehH  disk cartridge, one spool of tape, etc. Element addresses do not extendE  across multiple physical units of media. Likewise, element addresses H  are independent of any logical partitioning that the primary device may,  support within a physical unit of media.     nE  A medium changer is viewed as a set of addressable elements, each of G  which may contain a unit of media or be used to move a unit of media. eF  Each medium changer element has a unique 16 bit element address. EachA  element is an instance of one of four classes or element types. s  e$     a)     MEDIUM TRANSPORT ELEMENT      b)     STORAGE ELEMENT a!     c)     IMPORT EXPORT ELEMENT o!     d)     DATA TRANSFER ELEMENT    sF  Units of media (cartridges, cassettes, caddies, etc.) are referred toF  only indirectly by this device model.  Units of media can be moved toH  or from any of the elements of the medium changer device.  The presenceH  of media at the various elements in a medium changer can be sensed.  InG  order to ensure exclusive access to a unit of media, the element whereOF  the unit of media is located (the element address) must be reserved.    B  Elements of the medium transport, import export and (rarely) dataE  transport types may not provide independent storage for medium.  The|C  capabilities of a particular medium changer in this respect can be D  sensed via the device capabilities page of the mode sense data. TheE  following hypothetical medium changer implementation illustrates oneTB  case of an element not providing independent storage for medium. A  Consider a medium changer which has a carousel style storage for E  medium. The import export function could be provided by a port which|B  allows operator access to one of the storage elements.  In such aG  device, the MOVE ELEMENT command from storage element to import export A  element would rotate the carousel to align the addressed storage|F  element to the import export position. In this case the import exportF  element does not provide independent storage but rather access to one  of the storage elements.    #  17.1.1.1 Medium transport elements|  6F  Medium transport elements address the functions of the medium changerC  device that perform the movement of units of media. Where a medium|E  transport element can serve (even temporarily) as a storage location D  for medium, the location of each unit of media must have a separate  element address.    G  In larger medium changer devices, the medium movement functions may be E  performed by multiple independent robotics subsystems. Each of these-E  may have a number of medium transport element addresses. The elementoH  addresses within each subsystem shall be contiguous. Any of the elementG  addresses within a subsystem may be used interchangeably in the medium C  transport element address field of MOVE MEDIUM and EXCHANGE MEDIUM D  commands. An initiator may determine the capabilities of the mediumA  movement facilities of a medium changer device via the transportC(  geometry MODE SENSE page, see 17.3.3.3.   A  Element address zero is reserved for use in the medium transport E  element address field of MOVE MEDIUM and EXCHANGE MEDIUM commands to F  direct the medium changer to use a default or medium changer selected  medium transport element.  |H  In some implementations, medium transport elements may be source and/orD  destination addresses in MOVE MEDIUM and EXCHANGE MEDIUM commands. E  They may or may not provide independent storage of a unit of media. u9  See the device capabilities MODE SENSE page, see 17.3.3.P  s  17.1.1.2 Storage elements  uC  Storage elements are locations of units of media while not in some H  other element type.  Medium in storage elements is available for access  by medium transport elements.     D  Storage elements may be source and/or destination addresses in MOVE%  MEDIUM and EXCHANGE MEDIUM commands.t      17.1.1.3 Import export elements   G  Import export elements are locations of units of media which are being=F  inserted into or withdrawn from the medium changer device.  Medium inG  these elements is accessible by both medium transport elements, by the =  operator, or by another independent medium changer device.  =  =E  Import export elements may be source and/or destination addresses inoF  MOVE MEDIUM and EXCHANGE MEDIUM commands. They may or may not provideD  independent storage of a unit of media, see the device capabilities  MODE SENSE page, see 17.3.3.    B  Particular import export elements may be capable of either import?  actions, export actions, both or neither (if an element is not 
  present).  t   17.1.1.4 Data transfer element    F  Data transfer elements are locations of the primary devices which areE  capable of reading or writing the medium. Data transfer elements may E  also be viewed as medium changer element addresses of units of media F  loaded in or available for loading in or removal from primary devicesC  such as disk or tape drives. Note that the medium changer function F  specified in this clause does not control the primary device. That is"  the responsibility of the system.   E  Data transfer elements may be source and/or destination addresses in F  MOVE MEDIUM and EXCHANGE MEDIUM commands. They may or may not provideD  independent storage of a unit of media, see the device capabilities  MODE SENSE page, see 17.3.3.m  r1  17.1.2 SCSI addressing of medium changer devices   uD  Medium changer devices respond to a SCSI ID / LUN address differentC  from those used by the data transfer element devices.  If the data|H  transfer elements served by the medium changer device are SCSI devices,H  they may be addressed though the same SCSI ID as the changer device butE  with a different logical unit number or through a different SCSI ID.yB  There is no requirement that communication with the data transferH  elements be done with the same SCSI bus as the medium changer device or@  by an SCSI interface at all.  This command set does not supportD  addressing both the changer and the data transfer elements with theD  same SCSI ID / LUN because the device at a particular SCSI ID / LUN4  address must have a single peripheral device type.   0A  The READ ELEMENT STATUS response page for data transfer elements H  provides the SCSI ID / LUN address of the primary devices serviced by a>  medium changer device if known to the medium changer device.   t<  17.1.3 Data access operations using a medium changer device  -A  The medium changer device moves units of media among the several G  elements accessible to it.  It is able to report the full/empty status-@  of any of these elements.  Data transfer elements represent theD  interface between the medium changer device and some primary device=  such as a removable media optical disk drive or tape drive. =  =B  In order to access data on a unit of media currently located in aH  medium changer storage element, a system will have to issue commands toH  both the medium changer device and to the primary device.  The commandsF  to the medium changer may include MOVE MEDIUM or EXCHANGE MEDIUM plusF  READ ELEMENT STATUS commands.  The commands to the primary device mayF  include TEST UNIT READY, INQUIRY, START STOP and LOAD UNLOAD commands)  in addition to READ and WRITE commands. R   /  17.1.4 Element status maintenance requirementse  cC  If the medium changer device chooses to implement the READ ELEMENTHG  STATUS command, the medium changer device must be capable of reportingnF  the various data (i.e. full, error, etc.) required by each page type.A  The medium changer may maintain this information at all times ortB  regenerate it in response to the READ ELEMENT STATUS command. TheG  INITIALIZE ELEMENT STATUS command can be used to force regeneration ofc  this information. :  h  17.1.5 Volume tagsi  n@  The read element status descriptor format for all element typesG  includes two sets of fields that contain volume tag information. ThesekD  optional fields are used to report media identification informationC  that the medium changer has acquired either by reading an external G  label (e.g. bar code labels), by a SEND VOLUME TAG command or by othereH  means which may be vendor unique. The same volume tag information shallF  be available to all initiators whether assigned by that initiator, by5  some other initiator or by the media changer itself.r  tE  Volume tag information provides a means to confirm the identity of aiE  unit of media that resides in a medium changer element. This command E  set does not define any direct addressing of units of media based on E  these fields. However, commands are defined that provide translationrG  between volume tag information and the element address where that unit   of media currently resides.  t>  The medium changer command set definition does not impose theD  requirement that volume tag information be unique over the units of/  media within the scope of the changer device.     F  The following commands support the optional volume tag functionality:L     a)     SEND VOLUME TAG - either as a translation request or to associateG            a volume tag with the unit of media currently residing at an             element address.eF     b)     REQUEST VOLUME ELEMENT ADDRESS - return the element addressK            currently associated with the volume tag information transferredo1            with the last send volume tag command.vJ     c)     READ ELEMENT STATUS - optionally reports volume tag information!            for all element types.AH     d)     MOVE MEDIUM and EXCHANGE MEDIUM commands - if volume tags areJ            implemented, these commands must retain the association betweenK            volume tag information and units of media as they are moved fromt            element to element.  e  17.1.5.1 Volume tag format   eC  Volume tag information consists of a volume identifier field of 32 A  bytes plus a volume sequence number field of 2 bytes. The volumea?  identifier shall consist of a left justified sequence of ASCIIiH  characters. Unused positions shall be blank (20h) filled.  In order forG  the SEND VOLUME TAG translate with template to work the characters '*'iG  and'?' (2Ah and 3Fh) must not appear in volume identification data andtH  there must be no blanks (20h) within the significant part of the volumeB  identifier. If volume tag information for a particular element is8  undefined, the volume identifier field shall be zero.     D  The volume sequence number is a 2 byte integer field. If the volumeF  sequence number is not used this field shall be zero.  The volume tagB  contents are independent of the volume identification information  recorded on the media.   eK     NOTE 199 For compatibility with the volume identifier defined by volume N     and file structure standards, it is recommended that the characters in theN     significant non-blank portion of the volume identifier field be restrictedJ     to the set: '0'..'9', 'A'..'Z', and '_' (30h .. 39h, 41h .. 5Ah, 5Fh).M     Specific systems may have differing requirements that may take precedencee     over this recommendation.n   F  Table 326 defines the fields within the 36 byte primary and alternateG  volume tag information fields found in READ ELEMENT STATUS descriptorsO8  and in the data format for the SEND VOLUME TAG command.   <                    Table 326 - Volume tag information formatP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                                                                       |P  |- - -+---                   Volume identification field                   ---|P  | 31  |                                                                       |P  |-----+-----------------------------------------------------------------------|P  | 32  |                                                                       |P  |- - -+---                            Reserved                             ---|P  | 33  |                                                                       |P  |-----+-----------------------------------------------------------------------|P  | 34  | (MSB)                                                                 |P  |-----+---                     Volume sequence number                      ---|P  | 35  |                                                                 (LSB) |P  +=============================================================================+  m  b6  17.1.5.2 Primary and alternate volume tag information   B  Element status descriptors as reported by the READ ELEMENT STATUSA  command define a primary volume tag and an alternate volume tag.gF  Alternate volume tag information provides a means for a system to useD  different volume identification information for each side of doubleB  sided media. In such a system, the primary volume tag informationB  refers to the logical medium accessible via a MOVE MEDIUM commandH  without the invert bit set. The alternate volume tag information refersE  to the other side of the media, i.e. the side that would be accessede3  via a MOVE MEDIUM command with the invert bit set.U  o  n)  17.2 Commands for medium changer devices   aH  The commands for medium changer devices shall be as shown in table 327.  e?                 Table 327 - Commands for medium changer devicesiI  +=====================================-============-======-============+rI  |  Command name                       | Operation  | Type |  Subclause | I  |                                     |   code     |      |            | I  |-------------------------------------+------------+------+------------|oI  | CHANGE DEFINITION                   |    40h     |   O  |   8.2.1    | I  | EXCHANGE MEDIUM                     |    A6h     |   O  |  17.2.1    |sI  | INITIALIZE ELEMENT STATUS           |    07h     |   O  |  17.2.2    |.I  | INQUIRY                             |    12h     |   M  |   8.2.5    |uI  | LOG SELECT                          |    4Ch     |   O  |   8.2.6    | I  | LOG SENSE                           |    4Dh     |   O  |   8.2.7    |aI  | MODE SELECT(6)                      |    15h     |   O  |   8.2.8    |eI  | MODE SELECT(10)                     |    55h     |   O  |   8.2.9    |aI  | MODE SENSE(6)                       |    1Ah     |   O  |   8.2.10   |tI  | MODE SENSE(10)                      |    5Ah     |   O  |   8.2.11   |iI  | MOVE MEDIUM                         |    A5h     |   M  |  17.2.3    |mI  | POSITION TO ELEMENT                 |    2Bh     |   O  |  17.2.4    |iI  | PREVENT ALLOW MEDIUM REMOVAL        |    1Eh     |   O  |   9.2.4    | I  | READ BUFFER                         |    3Ch     |   O  |   8.2.12   |pI  | READ ELEMENT STATUS                 |    B8h     |   O  |  17.2.5    |eI  | RECEIVE DIAGNOSTIC RESULTS          |    1Ch     |   O  |   8.2.13   |oI  | RELEASE                             |    17h     |   O  |  17.2.6    |rI  | REQUEST VOLUME ELEMENT ADDRESS      |    B5h     |   O  |  17.2.7    |aI  | REQUEST SENSE                       |    03h     |   M  |   8.2.14   |eI  | RESERVE                             |    16h     |   O  |  17.2.8    |eI  | REZERO UNIT                         |    01h     |   O  |   9.2.13   |oI  | SEND DIAGNOSTIC                     |    1Dh     |   M  |   8.2.15   | I  | SEND VOLUME TAG                     |    B6h     |   O  |  17.2.9    |eI  | TEST UNIT READY                     |    00h     |   M  |   8.2.16   |dI  | WRITE BUFFER                        |    3Bh     |   O  |   8.2.17   |tI  |----------------------------------------------------------------------|,I  |Key:  M = command implementation is mandatory.                        | I  |      O = command implementation is optional.                         |eI  +======================================================================+e  n  iC  Operation codes 0Ch, and C0h through FFh are vendor-specific.  Alle$  other operation codes are reserved.  s  o  17.2.1 EXCHANGE MEDIUM commanda  t@  The EXCHANGE MEDIUM command (see table 328) provides a means toH  exchange the medium in the source element, with the medium located at a  destination element.   e9                       Table 328 - EXCHANGE MEDIUM commandtP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (A6h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |                  Reserved                  |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                        Transport element address                ---|P  | 3   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 4   | (MSB)                                                                 |P  |-----+---                        Source address                           ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   | (MSB)                                                                 |P  |-----+---                        First destination address                ---|P  | 7   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 8   | (MSB)                                                                 |P  |-----+---                        Second destination address               ---|P  | 9   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 10  |                           Reserved                  |  Inv2  |  Inv1  |P  |-----+-----------------------------------------------------------------------|P  | 11  |                           Control                                     |P  +=============================================================================+  d  cF     NOTE 200 Support of this command requires that the device have theI     capability of handling two units of media at the same time or that itn     emulate this capability. t  iC  The medium in the source element is moved to the first destination F  element and the medium that previously occupied the first destination?  element is moved to the second destination element. The secondgE  destination element may or may not be the same element as the sourceaG  element.  In the case of a simple exchange, the source element and theq*  second destination element are the same.   iC  If this command is received and the source element is empty or thedF  first destination element is empty, or the second destination element>  (if different from the source element) is full, or the secondF  destination element (if the same as the source element) is empty, theD  target shall return CHECK CONDITION status and set the sense key to  ILLEGAL REQUEST.   aE  The transport element address specifies the medium transport element D  that is to be used in executing this command. The default transportG  element address of zero may be used if this functionality is supportedf?  by the medium changer device. If the transport element addresseC  specified has not been assigned or has been assigned to an elementoE  other than a medium transport element, the target shall return CHECKr@  CONDITION status and the set the sense key to ILLEGAL REQUEST.   uB  The source address, the first destination address, and the secondF  destination address may represent a storage element, an import exportE  element, a data transfer element, or a medium transport element.  IfaE  the address specified has not been assigned to a specific element oftG  the medium changer, the target shall return CHECK CONDITION status anda'  set the sense key to ILLEGAL REQUEST. n   C  The device capabilities page (see 17.3.3.) provides a matrix whicheH  defines the supported source element type and first destination elementG  type combinations for EXCHANGE MEDIUM commands when the source element 5  type is the same as second destination element type.t  mH  An Inv1 bit of one specifies that the medium shall be inverted prior to;  depositing the medium into the first destination element. m  eH  An Inv2 bit of one specifies that the medium shall be inverted prior to<  depositing the medium into the second destination element.   .D  If the medium changer does not support medium rotation for handlingE  double sided media, the Inv1 and Inv2 bits should be set to zero. IfeC  either of these bits is non-zero, a target which is not capable ofpF  medium rotation shall return CHECK CONDITION status and set the sense  key to ILLEGAL REQUEST. d   )  17.2.2 INITIALIZE ELEMENT STATUS commandm  .E  The INITIALIZE ELEMENT STATUS command (see table 329) will cause the=E  medium changer to check all elements for medium and any other status=F  relevant to that element. The intent of this command is to enable theG  initiator to get a quick response from a following READ ELEMENT STATUS G  command. It may be useful to issue this command after a power failure,=H  or if medium has been changed by an operator, or if configurations have  been changed.   >                  Table 329 - INITIALIZE ELEMENT STATUS commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (07h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |                Reserved                    |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+  a  M  17.2.3 MOVE MEDIUM commandt  iH  The MOVE MEDIUM command (see table 330) requests that the target move a?  unit of media from a source element to a destination element. M   7                         Table 330 - MOVE MEDIUM commandoP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (A5h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |             Reserved                       |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                        Transport element address                ---|P  | 3   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 4   | (MSB)                                                                 |P  |-----+---                        Source address                           ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   | (MSB)                                                                 |P  |-----+---                        Destination address                      ---|P  | 7   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 8   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 10  |                           Reserved                           | Invert |P  |-----+-----------------------------------------------------------------------|P  | 11  |                           Control                                     |P  +=============================================================================+  8  1C  The source address specifies the location that the medium is taken B  from, and the destination address specifies the location that the  medium is moved to. |  :C  If this command is received and the source element is empty or the H  destination element (if different from the source element) is full, theD  target shall return CHECK CONDITION status and set the sense key to  ILLEGAL REQUEST.   iE  The transport element address specifies the medium transport elementeA  that is to be used in executing this command. The default mediumaG  transport element address of zero may be used if this functionality iseF  supported by the medium changer device.  If the address specified hasB  not been assigned or has been assigned to an element other than aB  medium transport element, the target shall return CHECK CONDITION6  status and the set the sense key to ILLEGAL REQUEST.   |G  The source address and the destination address may represent a storage H  element, an import export element, a data transfer element, or a mediumG  transport element. If the address specified has not been assigned to a|F  specific element of the medium changer, the target shall return CHECK<  CONDITION status and set the sense key to ILLEGAL REQUEST.   -C  The device capabilities MODE SENSE page provides a matrix with the E  supported source element or destination element combinations for the-!  MOVE MEDIUM command. See 17.3.3.-  -D  An invert bit of one specifies that the medium shall be inverted orH  rotated prior to depositing the medium into the destination element. IfH  the medium changer does not support medium rotation for handling doubleH  sided media, the invert bit should be set to zero.  If this bit is non-C  zero, a target that is not capable of medium rotation shall return B  CHECK CONDITION status and set the sense key to ILLEGAL REQUEST.    #  17.2.4 POSITION TO ELEMENT command    B  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 command P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (2Bh)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |                Reserved                    |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                        Transport element address                ---|P  | 3   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 4   | (MSB)                                                                 |P  |-----+---                        Destination element address              ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 8   |                           Reserved                           | Invert |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+  u  rJ     NOTE 201 In this context, in front of is defined to mean positioned soJ     that no further motion of the medium transport element is necessary toH     execute an appropriate MOVE MEDIUM command between the two elements.  sB  An invert bit value of one requests that the transport element beC  inverted or rotated before positioning in front of the destinationrD  element. A value of zero requests that the orientation be unchanged8  before positioning in front of the destination element.   #  17.2.5 READ ELEMENT STATUS commande  tB  The READ ELEMENT STATUS command (see table 332) requests that theD  target report the status of its internal elements to the initiator.  b;                     Table 332 - READ ELEMENT STATUS commandtP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (B8h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      | VolTag |        Element type code          |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                        Starting element address                 ---|P  | 3   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 4   | (MSB)                                                                 |P  |-----+---                        Number of elements                       ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 8   |                           Allocation length                           |P  |-----+---                                                                 ---|P  | 9   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  |10   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  |11   |                           Control                                     |P  +=============================================================================+  -  -H  A volume tag (VolTag) bit of one indicates that the target shall reportE  volume tag information if this feature is supported. A value of zero-D  indicates that volume tag information shall not be reported. If theC  volume tag feature is not supported this field shall be treated as 
  reserved.  |E  The element type code field specifies the particular element type(s)-H  selected for reporting by this command.  A value of zero specifies thatH  status for all element types shall be reported.  The element type codes  are defined in table 333.   6                          Table 333 - Element type codeI       +=============-===================================================+ I       |    Code     |  Description                                      |aI       |-------------+---------------------------------------------------|-I       |      0h     |  All element types reported, (valid in CDB only)  | I       |      1h     |  Medium transport element                         | I       |      2h     |  Storage element                                  |=I       |      3h     |  Import export element                            | I       |      4h     |  Data transfer element                            |-I       |   5h - Fh   |  Reserved                                         ||I       +=================================================================+|  -  -F  The starting element address specifies the minimum element address toA  report. Only elements with an element type code permitted by the H  element type code specification, and an element address greater than orA  equal to the starting element address shall be reported. Element E  descriptor blocks are not generated for undefined element addresses.-  -?  The number of elements specifies the maximum number of element D  descriptors to be created by the target for this command. The valueD  specified by this field is not the range of element addresses to beF  considered for reporting but rather the number of defined elements toG  report. If the allocation length is not sufficient to transfer all the-E  element descriptors, the target shall transfer all those descriptors G  that can be completely transferred and this shall not be considered ann  error.      17.2.5.1 Element status data    C  The data returned by the READ ELEMENT STATUS command is defined in|G  table 334 and 17.2.5.3 through 17.2.5.6.  Element status data consists-A  of an eight-byte header, (see table 334) followed by one or more   element status pages.  +7                         Table 334 - Element status data-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 available                 ---|P  | 3   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 4   |                              Reserved                                 |P  |-----+-----------------------------------------------------------------------|P  | 5   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 6   |                     Byte count of report available                    |P  |-----+---                        (all pages, n - 7 )                      ---|P  | 7   |                                                                 (LSB) |P  |=====+=======================================================================|P  | 8   |                                                                       |P  |- - -+---                     Element status page(s)                      ---|P  | n   |                                                                       |P  +=============================================================================+  f   G  The first element address reported field indicates the element addressdG  of the element with the smallest element address found to meet the CDBt	  request.a  nH  The number of elements available field indicates the number of elementsE  meeting the request in the command descriptor block.  The status fora?  these elements is returned if sufficient allocation length was   specified.Q  TG  The byte count of report available field indicates the number of bytesTC  of element status page data available for all elements meeting theiB  request in the command descriptor block.  This value shall not be4  adjusted to match the allocation length available.   =D     NOTE 202 - The READ ELEMENT STATUS command can be issued with anI     allocation length of eight bytes in order to determine the allocation L     length required to transfer all the element status data specified by the     command.  |>  Figure 28 provides an illustration of the element status data  structure.|  |                          e  i  c     h                       -  +  -  -  -  -  -  -  -  -  -D            Figure 28 - Illustration of element status data structure        17.2.5.2 Element status page    F  The element status page is defined in table 335.  Each element statusC  page includes an eight-byte header followed by one or more element C  descriptor blocks.  The header includes the element type code, theoC  length of each descriptor block and the number of bytes of element F  descriptor information that follow the header for this element type.   -8                         Table 335 - Element status page P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Element type code                           |P  |-----+-----------------------------------------------------------------------|P  | 1   | PVolTag| AVolTag|                      Reserved                       |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                    Element descriptor length                    ---|P  | 3   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 4   |                              Reserved                                 |P  |-----+-----------------------------------------------------------------------|P  | 5   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 6   |                Byte count of descriptor data available                |P  |-----+---                      (this page, n - 7)                         ---|P  | 7   |                                                                 (LSB) |P  |=====+=======================================================================|P  | 8   |                                                                       |P  |- - -+---                     Element descriptor(s)                       ---|P  | n   |                                                                       |P  +=============================================================================+      H  The element type code field indicates the element type reported by this  page.  =E  A primary volume tag (PVolTag) bit of one indicates that the primary A  volume tag information field is present in each of the following-F  element descriptor blocks. A value of zero indicates that these bytes6  are omitted from the element descriptors that follow.  -@  An alternate volume tag (AVolTag) bit of one indicates that theA  alternate volume tag information field is present in each of the D  following element descriptor blocks. A value of zero indicates thatB  these bytes are omitted from the element descriptors that follow.   E  The element descriptor length field indicates the number of bytes in-  each element descriptor.   -G  The byte count of descriptor data available field indicates the number C  of bytes of element descriptor data available for elements of this E  element type meeting the request in the CDB. This value shall not be 3  adjusted to match the allocation length available.-  -G  Each element descriptor includes the element address and status flags; H  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 descriptor Q  +======-========-========-========-========-========-========-========-========+ Q  |   Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | Q  |Byte  |        |        |        |        |        |        |        |        |-Q  |======+=======================================================================| Q  |  0   | (MSB)                                                                 |-Q  |------+---                      Element address                            ---| Q  |  1   |                                                                 (LSB) |=Q  |------+-----------------------------------------------------------------------|aQ  |  2   |            Reserved                        | Except |Reserved|  Full  |iQ  |------+-----------------------------------------------------------------------|aQ  |  3   |                            Reserved                                   |eQ  |------+-----------------------------------------------------------------------| Q  |  4   |                      Additional sense code                            |eQ  |------+-----------------------------------------------------------------------|aQ  |  5   |                  Additional sense code qualifier                      |eQ  |------+-----------------------------------------------------------------------| Q  |  6   |                                                                       |-Q  |- - --+---                         Reserved                                ---| Q  |  8   |                                                                       | Q  |------+-----------------------------------------------------------------------|tQ  |  9   | SValid | Invert |                      Reserved                       | Q  |------+-----------------------------------------------------------------------| Q  | 10   | (MSB)                                                                 | Q  |------+---                Source storage element address                   ---|=Q  | 11   |                                                                (LSB)  |oQ  |------+-----------------------------------------------------------------------| Q  | 12   |                                                                       |eQ  |- - --+---                Primary volume tag information                   ---|rQ  | 47   |                   (Field omitted if PVolTag = 0)                      |uQ  |------+-----------------------------------------------------------------------|lQ  | 48   |                                                                       |eQ  |- - --+---               Alternate volume tag information                  ---|aQ  | 83   |                   (Field omitted if AVolTag = 0)                      |tQ  |------+-----------------------------------------------------------------------|sQ  | 84   |                                                                       |eQ  |- - --+---                          Reserved                               ---|.Q  | 87   |    (Field moved up if volume tag information field(s) are omitted.)   |sQ  |------+-----------------------------------------------------------------------| Q  | 88   |                                                                       |=Q  |- - --+---                        Vendor-specific                          ---||Q  | z-1  |    (Field moved up if volume tag information field(s) are omitted.)   | Q  +==============================================================================+=  =  =B  The element address field gives the address of the medium changerC  element whose status is reported by this element descriptor block.F  t@  An exception (Except) bit of one indicates the element is in anH  abnormal state.  An exception bit of zero indicates the element is in aE  normal state.  If this bit is one, information on the abnormal state H  may be available in the additional sense code and additional sense code  qualifier bytes.    F  A full bit value of one indicates that the element contains a unit ofF  media.  A value of zero indicates that the element does not contain a  unit of media.-  -G  The additional sense code field may provide specific information on an E  abnormal element state.  The values in this field are as defined for D  the additional sense code of the REQUEST SENSE data (see 8.2.14.3).  -D  The additional sense code qualifier field may provide more detailedH  information on an abnormal element state.  The values in this field areH  as defined for the additional sense code qualifier of the REQUEST SENSE  data (see 8.2.14.4).    C  A source valid (SValid) bit value of one indicates that the source H  storage element address field and the invert bit information are valid.B  A value of zero indicates that the values in these fields are not  valid.   =H  An invert bit value of one indicates that the unit of media now in thisH  element was inverted by MOVE MEDIUM or EXCHANGE MEDIUM operations sinceF  it was last in the source storage element.  A value of zero indicates1  that no inversion occurred during the operation.|  +E  The source storage element address field provides the address of the=H  last storage element this unit of media was moved.  This field is valid  only if the SValid bit is one.i  tD  The primary and alternate volume tag information fields provide forF  identifying the unit of media residing in this element (see 17.1.5.).B  Either or both of these fields may be omitted for all the elementG  descriptor blocks that comprise an element status page as indicated bye@  the PVolTag and AVolTag bits in the element status page header.   $  17.2.5.4 Storage element descriptor   2  Table 337 defines the storage element descriptor.  i;                      Table 337 - Storage element descriptorjQ  +======-========-========-========-========-========-========-========-========+NQ  |   Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |eQ  | Byte |        |        |        |        |        |        |        |        |tQ  |======+=======================================================================|tQ  |  0   | (MSB)                                                                 |cQ  |------+---                      Element address                            ---| Q  |  1   |                                                                 (LSB) |.Q  |------+-----------------------------------------------------------------------| Q  |  2   |            Reserved               | Access | Except |Reserved|  Full  | Q  |------+-----------------------------------------------------------------------|eQ  |  3   |                            Reserved                                   |hQ  |------+-----------------------------------------------------------------------| Q  |  4   |                       Additional sense code                           |=Q  |------+-----------------------------------------------------------------------||Q  |  5   |                   Additional sense code qualifier                     | Q  |------+-----------------------------------------------------------------------|=Q  |  6   |                                                                       | Q  |- - --+---                         Reserved                                ---|-Q  |  8   |                                                                       | Q  |------+-----------------------------------------------------------------------|-Q  |  9   | SValid | Invert |                      Reserved                       | Q  |------+-----------------------------------------------------------------------|-Q  | 10   | (MSB)                                                                 ||Q  |------+---                    Source element address                       ---| Q  | 11   |                                                                (LSB)  ||Q  |------+-----------------------------------------------------------------------|5Q  | 12   |                                                                       |-Q  |- - --+---                 Primary volume tag information                  ---||Q  | 47   |                    (Field omitted if PVolTag = 0)                     |-Q  |------+-----------------------------------------------------------------------| Q  | 48   |                                                                       |=Q  |- - --+---                Alternate volume tag information                 ---| Q  | 83   |                    (Field omitted if PVolTag = 0)                     | Q  |------+-----------------------------------------------------------------------| Q  | 84   |                                                                       |=Q  |- - --+---                         Reserved                                ---|pQ  | 87   |    (Field moved up if volume tag information field(s) are omitted.)   |lQ  |------+-----------------------------------------------------------------------|iQ  | 88   |                                                                       |rQ  |- - --+---                      Vendor unique                              ---|.Q  | z-1  |    (Field moved up if volume tag information field(s) are omitted.)   |vQ  +==============================================================================+o  l  sE  An access bit value of one indicates that access to the element by amF  medium transport element is allowed.  An access bit of zero indicatesF  that access to the element by the medium transport element is denied.   E  The source storage element address field provides the address of theeE  last storage element this unit of media was moved from. This elementtH  address value may or may not be the same as this element. This field is%  valid only if the SValid bit is one.-  -8  For fields not defined in this subclause, see 17.2.5.3.  t*  17.2.5.5 Import export element descriptor  n8  Table 338 defines the import export element descriptor.  m>                   Table 338 - Import export element descriptorQ  +======-========-========-========-========-========-========-========-========+ Q  |   Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | Q  |Byte  |        |        |        |        |        |        |        |        | Q  |======+=======================================================================| Q  |  0   | (MSB)                                                                 | Q  |------+---                        Element address                          ---| Q  |  1   |                                                                 (LSB) | Q  |------+-----------------------------------------------------------------------| Q  |  2   |     Reserved    | InEnab | ExEnab | Access | Except | ImpExp |  Full  | Q  |------+-----------------------------------------------------------------------| Q  |  3   |                             Reserved                                  | Q  |------+-----------------------------------------------------------------------| Q  |  4   |                        Additional sense code                          | Q  |------+-----------------------------------------------------------------------| Q  |  5   |                    Additional sense code qualifier                    | Q  |------+-----------------------------------------------------------------------| Q  |  6   |                                                                       | Q  |------+---                          Reserved                               ---| Q  |  8   |                                                                       | Q  |------+-----------------------------------------------------------------------| Q  |  9   | SValid | Invert |                      Reserved                       | Q  |------+-----------------------------------------------------------------------| Q  | 10   | (MSB)                                                                 | Q  |------+---                  Source storage element address                 ---| Q  | 11   |                                                                (LSB)  | Q  |------+-----------------------------------------------------------------------| Q  | 12   |                                                                       | Q  |- - --+---                  Primary volume tag information                 ---| Q  | 47   |                     (Field omitted if PVolTag = 0)                    | Q  |------+-----------------------------------------------------------------------| Q  | 48   |                                                                       | Q  |- - --+---                 Alternate volume tag information                ---| Q  | 83   |                     (Field omitted if PVolTag = 0)                    | Q  |------+-----------------------------------------------------------------------| Q  | 84   |                                                                       | Q  |- - --+---                          Reserved                               ---| Q  | 87   |    (Field moved up if volume tag information field(s) are omitted.)   | Q  |------+-----------------------------------------------------------------------| Q  | 88   |                                                                       | Q  |- - --+---                         Vendor unique                           ---| Q  | z-1  |    (Field moved up if volume tag information field(s) are omitted.)   | Q  +==============================================================================+   z   F  An import enable (InEnab) bit of one indicates that the import exportH  element supports movement of media into the scope of the medium changerD  device.  An InEnab bit of zero indicates that this element does not  support import actions.  wF  An export enable (ExEnab) bit of one indicates that the import exportB  element supports movement of media out of the scope of the mediumG  changer device. An ExEnab bit of zero indicates that this element doest  not support export actions.  tH  An access bit of one indicates that access to the import export elementA  by a medium transport element is allowed.  An access bit of zerouB  indicates access to the import export element by medium transport  elements is denied. t   K     NOTE 203 An example of when access would be denied is when the operatoro6     has exclusive access to the import export element.   H  An import export (ImpExp) bit of one indicates the unit of media in theF  import export element was placed there by an operator.  An ImpExp bitE  of zero indicates the unit of media in the import export element wasn.  placed there by the medium transport element.  f5  For fields not defined in this clause, see 17.2.5.3.l  e*  17.2.5.6 Data transfer element descriptor   8  Table 339 defines the data transfer element descriptor.  t>                   Table 339 - Data transfer element descriptorQ  +======-========-========-========-========-========-========-========-========+eQ  |   Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |wQ  |Byte  |        |        |        |        |        |        |        |        | Q  |======+=======================================================================|vQ  |  0   | (MSB)                                                                 |lQ  |------+---                      Element address                            ---| Q  |  1   |                                                                 (LSB) |aQ  |------+-----------------------------------------------------------------------|nQ  |  2   |            Reserved               | Access | Except |Reserved|  Full  |rQ  |------+-----------------------------------------------------------------------|tQ  |  3   |                            Reserved                                   |.Q  |------+-----------------------------------------------------------------------|oQ  |  4   |                       Additional sense code                           |=Q  |------+-----------------------------------------------------------------------| Q  |  5   |                   Additional sense code qualifier                     | Q  |------+-----------------------------------------------------------------------|=Q  |  6   |Not bus|Reserved|ID valid|LU valid|Reserved|    Logical unit number    |BQ  |------+-----------------------------------------------------------------------| Q  |  7   |                         SCSI bus address                              | Q  |------+-----------------------------------------------------------------------|-Q  |  8   |                             Reserved                                  | Q  |------+-----------------------------------------------------------------------|-Q  |  9   | SValid | Invert |                      Reserved                       | Q  |------+-----------------------------------------------------------------------|-Q  | 10   | (MSB)                                                                 | Q  |------+---              Source storage element address                     ---|-Q  | 11   |                                                                (LSB)  | Q  |------+-----------------------------------------------------------------------|-Q  | 12   |                                                                       | Q  |- - --+---                 Primary volume tag information                  ---| Q  | 47   |                    (Field omitted if PVolTag = 0)                     | Q  |------+-----------------------------------------------------------------------|-Q  | 48   |                                                                       |lQ  |- - --+---                Alternate volume tag information                 ---|-Q  | 83   |                    (Field omitted if PVolTag = 0)                     |BQ  |------+-----------------------------------------------------------------------| Q  | 84   |                                                                       | Q  |- - --+---                         Reserved                                ---|-Q  | 87   |    (Field moved up if volume tag information field(s) are omitted.)   | Q  |------+-----------------------------------------------------------------------| Q  | 88   |                                                                       | Q  |- - --+---                        Vendor unique                            ---|-Q  | z-1  |    (Field moved up if volume tag information field(s) are omitted.)   | Q  +==============================================================================+       A  An access bit value of one indicates access to the data transfer E  element by the medium transport element is allowed.  A value of zero D  indicates access to the data transfer element by a medium transport  element is denied.|   M     NOTE 204 Access to the data transfer element by medium transport elements|K     might be denied if a data transfer operation was under way. Note that a-F     one value in this bit may not be sufficient to ensure a successfulN     operation. This bit can only reflect the best information available to theL     medium changer device, which may not accurately reflect the state of the#     primary (data transfer) device.-   F  A not this bus (not bus) bit value of one indicates that the SCSI busF  address and logical unit number values are not valid for the SCSI busF  used to select the medium changer device. A not bus bit value of zeroG  indicates that the SCSI address and logical unit values, if valid, arec.  on the same bus as the medium changer device.   G  An ID Valid bit value of one indicates that the SCSI bus address field H  contains valid information. An LU Valid bit value of one indicates that:  the logical unit number field contains valid information.  mH  The SCSI bus address field, if valid, provides the SCSI address (binaryF  representation) of the primary device served by the medium changer at  this element address.  FC  The logical unit number field, if valid, provides the logical unit F  number within the SCSI bus device of the primary device served by the(  medium changer at this element address.   5  For fields not defined in this clause, see 17.2.5.3.=  =.  17.2.6 REQUEST VOLUME ELEMENT ADDRESS command  =F  The REQUEST VOLUME ELEMENT ADDRESS command (see table 340) is used toE  transfer the results of a SEND VOLUME TAG command.  Multiple REQUEST H  VOLUME ELEMENT ADDRESS commands may be used to recover the results of a:  single SEND VOLUME TAG command with the translate option.  MA                Table 340 - REQUEST VOLUME ELEMENT ADDRESS command P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (B5h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      | VolTag |        Element type code          |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                        Element address                          ---|P  | 3   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 4   | (MSB)                                                                 |P  |-----+---                        Number of elements                       ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 8   |                           Allocation length                           |P  |-----+---                                                                 ---|P  | 9   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  |10   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  |11   |                           Control                                     |P  +=============================================================================+     FE  For each SEND VOLUME TAG command, the target shall be able to report-F  multiple elements that match a volume tag template in element addressH  order.  Once information for a given element address has been reported,E  only higher element addresses will be reported by subsequent REQUEST "  VOLUME ELEMENT ADDRESS commands.    J     NOTE 205 In order to ensure the successful completion of a SEND VOLUMEE     TAG, REQUEST VOLUME ELEMENT ADDRESS sequence in a multi-initiator M     environment, it may be necessary to reserve the medium changer device. To|N     do this, issue a unit RESERVE command prior to the SEND VOLUME TAG commandM     and delay issuing the RELEASE until after the last REQUEST VOLUME ELEMENT 
     ADDRESS. =  =H  A volume tag (VolTag) bit of one indicates that the target shall reportB  volume tag information. A value of zero indicates that volume tagF  information shall not be reported. This is provided for compatibility&  with the READ ELEMENT STATUS command.  nE  The element type code field specifies the particular element type(s)xH  selected for reporting by this command.  A value of zero specifies thatC  status for all element types shall be reported. The codes for thisdB  field are defined in 17.2.5.  This acts as a qualification of the?  element(s) determined by SEND VOLUME TAG to match the templatet  specified.   pG  The element address field gives a medium changer element address whose F  interpretation depends on the send action code received with the lastD  SEND VOLUME TAG command.  This code is echoed in the volume elementG  address return format transferred by this command.  When the last send A  action code was a translate, (code values 0h .. 7h), the elementnG  address field gives the minimum element address to be reported by thishC  command.  When the send action code is other than translate, (i.e.dC  assert, replace, and undefined, code values 8h .. Dh), the elementnH  address field gives the particular element whose volume tag information  was modified.  aD  The number of elements specifies the maximum number of elements andE  volume tags to be reported by the target for this command. The valuelD  specified by this field is not the range of element addresses to beH  considered for reporting but rather the number of elements to report ofE  those that match the last send volume tag translate template. If the @  allocation length is not sufficient to transfer all the elementF  descriptors, the target shall transfer all those descriptors that canE  be completely transferred and this shall not be considered an error.    E  The data returned by this command consists of a header as defined by D  table 341, plus one or more element type specific pages in the same6  format as defined by the READ ELEMENT STATUS command.  -@                 Table 341 - Volume element address header formatQ  +======-========-========-========-========-========-========-========-========+-Q  |   Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    | Q  |Byte  |        |        |        |        |        |        |        |        |-Q  |======+=======================================================================| Q  | 0    | (MSB)                                                                 |-Q  |------+---                  First element address reported                 ---| Q  | 1    |                                                                 (LSB) |-Q  |------+-----------------------------------------------------------------------| Q  | 2    | (MSB)                                                                 |-Q  |------+---                    Number of elements reported                  ---| Q  | 3    |                                                                 (LSB) |-Q  |------+-----------------------------------------------------------------------| Q  | 4    |          Reserved        |              Send action code              |-Q  |------+-----------------------------------------------------------------------| Q  | 5    | (MSB)                                                                 |-Q  |------+---                                                                 ---| Q  | 6    |                     Byte count of report available                    |-Q  |------+---                        (all pages, x - 7 )                      ---| Q  | 7    |                                                                 (LSB) |-Q  |======+=======================================================================| Q  |8 to  |                                                                       |-Q  |  - --+---                     Element status page(s)                      ---| Q  | x    |                                                                       |-Q  +==============================================================================+       D  The send action code field gives the function performed by the lastG  SEND VOLUME TAG command as defined in 17.2.9. This command reports the ,  results of this send action code operation.  e8  For fields not defined in this subclause, see 17.2.5.1.  -  17.2.7 RELEASE command-  -B  The RELEASE command (see table 342) is used to release previouslyB  reserved units, or, if the element release option is implemented,F  previously reserved elements within units.  It is not an error for anD  initiator to attempt to release a reservation that is not currentlyC  active.  In this case, the target shall return GOOD status without-   altering any other reservation.   5                           Table 342 - RELEASE command P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (17h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      | 3rdPty | Third party device ID    | Element|P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reservation identification                  |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+  a     17.2.7.1 Logical unit release  cC  If the element bit is zero, this command shall cause the target totE  terminate all non-third party unit and element reservations that areS9  active from the initiator to the specified logical unit.(  a$  17.2.7.2 Element release (optional)  e@  If the element bit is one and the element release option is not@  implemented, the RELEASE command shall be terminated with CHECKE  CONDITION status and the sense key shall be set to ILLEGAL REQUEST.  H  This option shall be implemented if the element reservation option (see  17.2.8.1) is implemented.   <  If the element bit is one and the element release option is?  implemented, this command shall cause any reservation from theaF  requesting initiator with a matching reservation identification to beD  terminated.  Other reservations from the requesting initiator shall  remain in effect.     17.2.7.3 Third party release    @  The third-party release option of the RELEASE command allows an@  initiator to release a unit or elements within a unit that wereC  previously reserved using third-party reservation (see 17.2.8.3). 3D  Third-party release shall be  implemented if third-party reserve is  implemented.    H  If the third-party (3rdPty) bit is zero, the third-party release optionF  is not requested.  If the 3rdPty bit is one and the target implementsG  the third-party release option, the target shall release the specified-H  unit or elements, but only if the reservation was made using the third-A  party reservation option by the initiator that is requesting the+H  release for the same SCSI device as specified in the third-party device
  ID field.   F  If the 3rdPty bit is one and the target does not implement the third-H  party release option, the target shall terminate the command with CHECKD  CONDITION status and the sense key shall be set to ILLEGAL REQUEST.     17.2.8 RESERVE command-  -H  The RESERVE command (see table 343) is used to reserve units or, if theE  element reservation option is implemented, elements within units for|G  the use of the initiator.  The third-party reservation allows units or H  elements to be reserved for another specified SCSI device.  The RESERVE@  and RELEASE commands provide the basic mechanism for contention*  resolution in multiple-initiator systems.   5                           Table 343 - RESERVE command P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (16h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      | 3rdPty | Third party device ID    | Element|P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reservation identification                  |P  |-----+-----------------------------------------------------------------------|P  | 3   | (MSB)                                                                 |P  |-----+---                        Element list length                      ---|P  | 4   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+     U"  17.2.8.1 Logical unit reservation  RG  If the element bit is zero, this command shall request that the entiretB  unit be reserved for the exclusive use of the initiator until theD  reservation is superseded by another valid RESERVE command from theC  initiator that made the reservation or until released by a RELEASEDD  command from the same initiator that made the reservation, by a BUSG  DEVICE RESET message from any initiator, by a hard RESET condition, or E  by a power off/on cycle.  A unit reservation shall not be granted ifmG  the unit or any element is reserved by another initiator.  It shall be A  permissible for an initiator to reserve a unit that is currently =  reserved by that initiator.  If the element bit is zero, thea@  reservation identification and the element list length shall be	  ignored.d  nE  If the unit, or any element within the unit, is reserved for anothernF  initiator, the target shall respond by returning RESERVATION CONFLICT  status.  fE  If, after honouring the reservation, any other initiator attempts toeH  perform any command on the reserved unit other than an INQUIRY, REQUESTH  SENSE, ALLOW MEDIUM REMOVAL, RESERVE, or a RELEASE command, the command5  shall be rejected with RESERVATION CONFLICT status.    e(  17.2.8.2 Element reservation (optional)   D  The reservation identification provides a means for an initiator toB  identify each element reservation.  This allows an initiator in a<  multiple-tasking environment, to have multiple reservationsD  outstanding.  The reservation identification is used in the RELEASED  command to specify which reservation is to be released.  It is alsoH  used in superseding RESERVE commands to specify which reservation is to  be superseded.o  hF  If the element reservation option is implemented, the element releaseG  option (see 17.2.7.2) shall also be implemented.  These options permiteG  multiple elements within the unit to be reserved, each with a separatee  reservation identification.  eA  If the element bit is one, and the element reservation option ishA  implemented, the target shall process the reservation request ase	  follows:rJ     a)     The element list shall be checked for valid element addresses. G            If any element address is invalid for this unit, the commandoL            shall be terminated with CHECK CONDITION status and the sense keyF            shall be set to ILLEGAL REQUEST.  The element list shall beB            checked for invalid element overlaps with other elementF            descriptors in the element list and if invalid overlaps areF            found, the command shall be terminated with CHECK CONDITIOND            status and the sense key shall be set to ILLEGAL REQUEST.L     b)     If the requested reservation does not conflict with any active orL            previously requested reservation, the elements specified shall beJ            reserved until superseded by another valid RESERVE command fromJ            the initiator that made the reservation, or until released by aI            RELEASE command from the same initiator, by a BUS DEVICE RESET-H            message from any initiator, or by a hard RESET condition.  IfI            either of the last two conditions occur, the next command fromoI            each initiator shall be terminated with CHECK CONDITION status <            and the sense key shall be set to UNIT ATTENTION.J     c)     If the reservation request conflicts with a reservation alreadyF            active the target shall return RESERVATION CONFLICT status.   E  If the element bit is one, and the element reservation option is not-@  implemented, the RESERVE command shall be terminated with CHECKB  CONDITION status.  The sense key shall be set to ILLEGAL REQUEST.   B  The size of the element list shall be defined by the element listB  length parameter.  The element list shall consist of zero or moreA  descriptors as shown in table 344.  Each element list descriptor H  defines a series of elements beginning at the specified element addressD  for the specified number of elements.  If the number of elements isH  zero, the element list shall begin at the specified element address and7  continue through the last element address on the unit.-   A               Table 344 - Data format of element list descriptors P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                                                                       |P  |- - -+---                         Reserved                                ---|P  | 1   |                                                                       |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                        Number of elements                       ---|P  | 3   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 4   | (MSB)                                                                 |P  |-----+---                        Element address                          ---|P  | 5   |                                                                 (LSB) |P  +=============================================================================+  |  -F  If an initiator issues a command to an element that has been reservedE  by a different initiator, the command shall not be performed and the F  command shall be terminated with a RESERVATION CONFLICT status.  If aD  reservation conflict precludes any part of the command, none of the  command shall be performed.     !  17.2.8.3 Third party reservation-  -D  The third-party reservation option of the RESERVE command allows anG  initiator to reserve a unit or elements within a unit for another SCSI-  device.  -E  If the third-party (3rdPty) bit is zero, the third-party reservation G  option is not requested.  If the 3rdPty bit is one and the third-party-E  reservation option is implemented, the RESERVE command shall reserve D  the specified unit or elements for the SCSI device specified in theH  third-party device ID field.  The target shall preserve the reservationA  until it is superseded by another valid RESERVE command from thelH  initiator that made the reservation or until it is released by the sameG  initiator, by a BUS DEVICE RESET message from any initiator, or a hardeE  RESET condition.  The target shall ignore any attempt to release thes)  reservation made by any other initiator.e  dG  If the 3rdPty bit is one and the third-party reservation option is notlD  implemented, the target shall reject the RESERVE command with CHECKE  CONDITION status and the sense key shall be set to ILLEGAL REQUEST. e  e"  17.2.8.4 Superseding reservations  i>  An initiator that holds a current reservation may modify thatH  reservation by issuing another RESERVE command to the same unit and, ifH  the element bit is one, using the same reservation identification.  TheF  superseding RESERVE command shall release the previous reservation in@  place when the new reservation request is granted.  The currentH  reservation shall not be modified if the new reservation request cannotF  be granted.  If the superseding reservation cannot be granted because@  of conflicts with a previous active reservation (other than theC  reservation being superseded), the target shall return RESERVATIONt  CONFLICT status.h  -K     NOTE 206 Superseding reservations are principally intended to allow the.G     SCSI device ID to be changed on a reservation using the third-partyl     reservation option.h     17.2.9 SEND VOLUME TAG commande  eC  The SEND VOLUME TAG command (see table 345) transfers a volume tagsE  template to be searched for or new volume tag information for one ortH  more media changer elements. The function of the command is conveyed byG  the send action code field. The REQUEST VOLUME ELEMENT ADDRESS command A  is used to transfer the results of a translate search operation.C  K9                       Table 345 - SEND VOLUME TAG commandAP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (B6h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |Reserved|        Element type code          |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                        Element address                          ---|P  | 3   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 4   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 5   |          Reserved        |              Send action code              |P  |-----+-----------------------------------------------------------------------|P  | 6   |                                                                       |P  |-----+---                        Reserved                                 ---|P  | 7   |                                                                       |P  |-----+-----------------------------------------------------------------------|P  | 8   | (MSB)                                                                 |P  |-----+---                     Parameter list length                       ---|P  | 9   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  |10   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  |11   |                           Control                                     |P  +=============================================================================+     oG  The element type code field specifies an element type specification as B  defined in 17.2.5.  If the send action code indicates a translateE  operation, this field indicates the element types to be searched. IfeA  this is a zero, all element types are candidates for a translatenG  operation. If the send action code does not indicate a translate, this $  field shall be treated as reserved.   F  The send action code field gives the function to be performed by this!  command as listed in table 346.     <                     Table 346 - Send volume tag action codesP  +=============-===============================================================+P  |    Code     |  Description                                                  |P  |-------------+---------------------------------------------------------------|P  |      0h     |  Translate - search all defined volume tags                   |P  |      1h     |  Translate - search only primary volume tags                  |P  |      2h     |  Translate - search only alternate volume tags                |P  |      3h     |  Reserved                                                     |P  |      4h     |  Translate - search all defined tags - ignore sequence numbers|P  |      5h     |  Translate - search primary tags - ignore sequence numbers    |P  |      6h     |  Translate - search alternate tags - ignore sequence numbers  |P  |      7h     |  Reserved                                                     |P  |      8h     |  Assert - as the primary volume tag - if tag now undefined    |P  |      9h     |  Assert - as the alternate volume tag - if tag now undefined  |P  |      Ah     |  Replace - the primary volume tag - current tag ignored       |P  |      Bh     |  Replace - the alternate volume tag - current tag ignored     |P  |      Ch     |  Undefined - the primary volume tag - current tag ignored     |P  |      Dh     |  Undefined - the alternate volume tag - current tag ignored   |P  |   Eh - 1Bh  |  Reserved                                                     |P  |  1Ch - 1Fh  |  Vendor-specific                                              |P  +=============================================================================+  s  eC  Translate operations request that the target search the volume tagvF  information available to it for elements whose volume tag informationD  matches the template given by the command parameters. The resultingH  information is reported via the REQUEST VOLUME ELEMENT ADDRESS command.  tH  Assert operations define volume tag information for a single element. AH  CHECK CONDITION with ILLEGAL REQUEST is reported if the subject elementG  already has defined volume tag information; in this case, the original 0  volume tag information shall remain unaltered.   oG  Replace operations define volume tag information for a single element.a>  Any previously defined volume tag information is overwritten.   E  Undefined operations cause previously defined volume tag informationaG  for the specified element to be cleared. It shall not be considered an.B  error to undefined volume tag information that was not previously	  defined.i  eC  A medium changer device that implements volume tag information mayNB  choose to not implement the facilities that modify the volume tagD  information.  With such an implementation a request for the assert,G  replace or undefined functions would cause the SEND VOLUME TAG commandaA  to be terminated with CHECK CONDITION and a sense key of ILLEGALr	  REQUEST.e   G  The element address field gives a medium changer element address whoseeB  interpretation depends on the send action code received with this@  command. When the send action code is a translate, (code valuesF  0h .. 7h), the element address field gives the starting element to beG  examined for satisfaction of the search criteria. When the send action=D  code is other than translate, (i.e. assert, replace, and undefined,F  code values 8h .. Dh), the element address field gives the particular8  element whose volume tag information is to be modified.   B  The volume tag information used for translate, assert and replaceD  functions is defined in table 347.  No parameters are necessary for  undefined operations.   >                  Table 347 - Send volume tag parameters formatP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                                                                       |P  |- - -+---               Volume identification template field              ---|P  | 31  |                                                                       |P  |-----+-----------------------------------------------------------------------|P  | 32  |                                                                       |P  |-----+---                            Reserved                             ---|P  | 33  |                                                                       |P  |-----+-----------------------------------------------------------------------|P  | 34  | (MSB)                                                                 |P  |- - -+---                  Minimum volume sequence number                 ---|P  | 35  |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 36  |                                                                       |P  |-----+---                            Reserved                             ---|P  | 37  |                                                                       |P  |-----+-----------------------------------------------------------------------|P  | 38  | (MSB)                                                                 |P  |- - -+---                  Maximum volume sequence number                 ---|P  | 39  |                                                                 (LSB) |P  +=============================================================================+  t  eE  The volume identification template field specifies a search templateh>  for translate functions and the exact value of the new volumeH  identification information for other SEND VOLUME TAG command functions.  VE  As a search template, this field may contain the wildcard characterstD  '*' and '?' (2Ah and 3Fh). '*' will match any string of characters,C  when it appears in a template the remainder of the template is noti,  used. '?' will match any single character.    H  For a function other than translate, this field may not contain the '*'  or '?' wildcard characters. R  cD  The minimum volume sequence number field specifies the new sequenceC  number for the assert and replace functions. For a translate, thisbD  specifies the least value that will meet the search specification.   pF  The maximum volume sequence number field specifies the greatest valueB  that will meet the search specification. This field is ignored on   functions other than translate.  T+  17.3 Parameters for medium changer devicesp  e  g  17.3.1 Diagnostic parametersn  d@  This subclause defines the descriptors and pages for diagnostic.  parameters used with medium changer devices.    D  The diagnostic page codes for medium changer devices are defined in  table 348.   t8                        Table 348 - Diagnostic page codesP  +=============-==================================================-============+P  |  Page code  |  Description                                     | Subclause  |P  |-------------+--------------------------------------------------+------------|P  |     00h     |  Supported diagnostic pages                      |  8.3.1.1   |P  |  01h - 3Fh  |  Reserved (for all device type pages)            |            |P  |  40h - 7Fh  |  Reserved                                        |            |P  |  80h - FFh  |  Vendor-specific pages                           |            |P  +=============================================================================+        17.3.2 Log parameters  cD  This subclause defines the descriptors and pages for log parameters#  used with medium changer devices. -  -H  The log page codes for medium changer devices are defined in table 349.   5                            Table 349 - Log page codes-P  +=============-==================================================-============+P  |  Page code  |  Description                                     | Subclause  |P  |-------------+--------------------------------------------------+------------|P  |     00h     |  Supported log pages                             |  8.3.2.5   |P  |     06h     |  Non-medium error page                           |  8.3.2.4   |P  |     07h     |  Last n error events page                        |  8.3.2.3   |P  |  01h - 05h  |  Reserved                                        |            |P  |  08h - 2Fh  |  Reserved                                        |            |P  |     3Fh     |  Reserved                                        |            |P  |  30h - 3Eh  |  Vendor-specific pages                           |            |P  +=============================================================================+        17.3.3 Mode parameters|  |E  This subclause defines the descriptors and pages for mode parameters-#  used with medium changer devices.     F  The mode parameter list, including the mode parameter header and mode(  block descriptor, are defined in 8.3.3.   E  The medium-type code field is contained in the mode parameter header A  (see 8.3.3).  This field is reserved for medium changer devices.-  -G  The device specific parameter field is contained in the mode parametereH  header (see 8.3.3).  This field is reserved for medium changer devices.  -@  The density code field is contained in the mode parameter blockC  descriptor (see 8.3.3).  This field is reserved for medium changer=	  devices.=  =G  The mode page codes for medium changer devices are shown in table 350.e  t5                           Table 350 - Mode page codesaP  +=============-==================================================-============+P  |  Page code  |  Description                                     | Subclause  |P  |-------------+--------------------------------------------------+------------|P  |     1Fh     |  Device capabilities                             | 17.3.3.1   |P  |     1Dh     |  Element address assignment                      | 17.3.3.2   |P  |     1Eh     |  Transport geometry parameters                   | 17.3.3.3   |P  |  01h - 1Ch  |  Reserved                                        |            |P  |     00h     |  Vendor-specific (does not require page format)  |            |P  |  20h - 3Eh  |  Vendor-specific (page format required)          |            |P  |     3Fh     |  Return all pages                                |            |P  |             |     (valid only for the MODE SENSE command)      |            |P  +=============================================================================+     |"  17.3.3.1 Device capabilities page   H  The device capabilities page (see table 351) defines characteristics of>  the element types on this medium changer implementation. ThisD  information may be employed by the initiator to determine functions;  permitted by the MOVE MEDIUM and EXCHANGE MEDIUM commands.s  e:                       Table 351 - Device capabilities pageP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+========+========+=====================================================|P  | 0   |   PS   |Reserved|         Page code (1Fh)                             |P  |-----+-----------------------------------------------------------------------|P  | 1   |                       Parameter length (12h)                          |P  |-----+-----------------------------------------------------------------------|P  | 2   |               Reserved            | StorDT | StorI/E| StorST | StorMT |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   |               Reserved            | MT->DT | MT->I/E| MT->ST | MT->MT |P  |-----+-----------------------------------+--------+--------+--------+--------|P  | 5   |               Reserved            | ST->DT | ST->I/E| ST->ST | ST->MT |P  |-----+-----------------------------------+--------+--------+--------+--------|P  | 6   |               Reserved            |I/E->DT |I/E->I/E|I/E->ST |I/E->MT |P  |-----+-----------------------------------+--------+--------+--------+--------|P  | 7   |               Reserved            | DT->DT | DT->I/E| DT->ST | DT->MT |P  |-----+-----------------------------------------------------------------------|P  | 8   |                                                                       |P  |- - -+---                        Reserved                                 ---|P  | 11  |                                                                       |P  |-----+-----------------------------------------------------------------------|P  | 12  |               Reserved            | MT<>DT | MT<>I/E| MT<>ST | MT<>MT |P  |-----+-----------------------------------+--------+--------+--------+--------|P  | 13  |               Reserved            | ST<>DT | ST<>I/E| ST<>ST | ST<>MT |P  |-----+-----------------------------------+--------+--------+--------+--------|P  | 14  |               Reserved            |I/E<>DT |I/E<>I/E|I/E<>ST |I/E<>MT |P  |-----+-----------------------------------+--------+--------+--------+--------|P  | 15  |               Reserved            | DT<>DT | DT<>I/E| DT<>ST | DT<>MT |P  +=============================================================================+     mA  The parameters savable (PS) bit is only used with the MODE SENSEtG  command.  This bit is reserved with the MODE SELECT command.  A PS bitsD  of one indicates that the target is capable of saving the page in a(  non-volatile, vendor-specific location.  =<  In the field names on this page, the following element type  abbreviations are used:)      MT       a medium transport element,        ST       a storage element,2      I/E             an import export element, and&      DT       a data transfer element.;  In the descriptions, XX and YY are any of the element type   abbreviations.    F  A StorXX bit value of one indicated that the defined elements of typeH  XX may provide independent storage for a unit of media. A value of zero>  indicates that elements of type XX provide virtual sources orG  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.-  -D  An XX->YY bit value of one indicates that the medium changer deviceG  supports all MOVE MEDIUM commands where the source is element type XX, C  the destination is element type YY and these element addresses are-G  otherwise valid. An XX->YY bit value of zero indicates that these MOVE D  MEDIUM commands may or may not be valid depending on the particularD  elements requested. Those which are not valid will be rejected with  ILLEGAL REQUEST.    D  An XX<>YY bit value of one indicates that the medium changer deviceG  supports all EXCHANGE MEDIUM commands where the source is element type H  XX, destination 1 is element type YY, destination 2 is the same type asB  the source element type and these element addresses are otherwiseH  valid. An XX<>YY bit value of zero indicates that these EXCHANGE MEDIUMF  commands may or may not be valid depending on the particular elementsC  requested. Those which are not valid will be rejected with ILLEGAL 	  REQUEST.    )  17.3.3.2 Element address assignment pagel   F  The element address assignment page (see table 352) is used to assignE  addresses to the elements of the medium changer (MODE SELECT) and to=B  report those assignments (MODE SENSE). This page also defines the(  number of each type of element present.  f=                   Table 352 - Element address assignment pagevP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+========+========+=====================================================|P  | 0   |   PS   |Reserved|         Page code (1Dh)                             |P  |-----+-----------------------------------------------------------------------|P  | 1   |                           Parameter length (12h)                      |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                        Medium transport element address         ---|P  | 3   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 4   | (MSB)                                                                 |P  |-----+---                        Number of medium transport elements      ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   | (MSB)                                                                 |P  |-----+---                        First storage element address            ---|P  | 7   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 8   | (MSB)                                                                 |P  |-----+---                        Number of storage elements               ---|P  | 9   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 10  | (MSB)                                                                 |P  |-----+---                        First import export element address      ---|P  | 11  |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 12  | (MSB)                                                                 |P  |-----+---                        Number of import export elements         ---|P  | 13  |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 14  | (MSB)                                                                 |P  |-----+---                        First data transfer element address      ---|P  | 15  |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 16  | (MSB)                                                                 |P  |-----+---                        Number of data transfer elements         ---|P  | 17  |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 18  |                                                                       |P  |-----+---                        Reserved                                 ---|P  | 19  |                                                                       |P  +=============================================================================+     iA  The parameters savable (PS) bit is only used with the MODE SENSErG  command.  This bit is reserved with the MODE SELECT command.  A PS biteD  of one indicates that the target is capable of saving the page in a'  non-volatile vendor-specific location.    F  The first medium transport element address field identifies the firstE  medium transport element contained in the medium changer (other thaniD  the default medium transport address of zero). The number of mediumF  transport elements field defines the total number of medium transportB  elements contained in the medium changer. If the number of mediumF  transport elements field in a MODE SELECT command is greater than theD  default value returned in the MODE SENSE parameter data, the targetE  shall return CHECK CONDITION status and set the sense key to ILLEGAL 	  REQUEST.    D  The first storage element address field identifies the first mediumH  storage element contained in the medium changer.  The number of storageC  elements field defines the total number of medium storage elementsuA  contained in the medium changer. If the number of medium storage D  elements field in a MODE SELECT command is greater than the defaultB  value returned in the MODE SENSE parameter data, the target shallH  return CHECK CONDITION status and set the sense key to ILLEGAL REQUEST.   C  The first import export element address field identifies the firsteF  medium portal that is accessible both by the medium transport devicesG  and also by an operator from outside the medium changer. The number ofOG  import export elements field defines the total number of import export F  elements contained in the medium changer and accessible to the mediumG  transport elements. If the number of import export elements field in a F  MODE SELECT command is greater than the default value returned in theC  MODE SENSE parameter data, the target shall return CHECK CONDITION=2  status and set the sense key to ILLEGAL REQUEST .  =>     NOTE 207 The number of import export elements may be zero.   H  The first data transfer element address field identifies the first dataE  transfer element contained in the medium changer.  The data transferrG  elements may be either read/write or read-only devices.  The number of-G  data transfer field defines the total number of data transfer elements A  contained within the medium changer and accessible to the medium-H  transport elements.  If the number of data transfer elements field in aF  MODE SELECT command is greater than the default value returned in theC  MODE SENSE parameter data, the target shall return CHECK CONDITION-2  status and set the sense key to ILLEGAL REQUEST .  eF  Each element in the medium changer must have a unique address. If theH  address ranges defined for any of the element types overlap, the targetE  shall return CHECK CONDITION status and set the sense key to ILLEGAL|
  REQUEST.   -,  17.3.3.3 Transport geometry parameters page  -G  The transport geometry parameters page (see table 353) defines whether/D  each medium transport element is a member of a set of elements thatH  share a common robotics subsystem and whether the element is capable ofF  media rotation.  One transport geometry descriptor is transferred for?  each medium transport element, beginning with the first medium H  transport element. (Other than the default transport element address of  zero.)    ?                  Table 353 - Transport geometry parameters page1P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+========+========+=====================================================|P  | 0   |   PS   |Reserved|         Page code (1Eh)                             |P  |-----+-----------------------------------------------------------------------|P  | 1   |                           Parameter length                            |P  |=====+=======================================================================|P  |     |                        Transport geometry descriptor(s)               |P  |=====+==============================================================-========|P  | 0   |                           Reserved                           | Rotate |P  |-----+-----------------------------------------------------------------------|P  | 1   |                Member number in transport element set                 |P  +=============================================================================+  i  oA  The parameters savable (PS) bit is only used with the MODE SENSE G  command.  This bit is reserved with the MODE SELECT command.  A PS bitdD  of one indicates that the target is capable of saving the page in a'  non-volatile vendor-specific location.i  o@  The parameter length specifies the number of bytes of transport?  geometry descriptors that follow.  The geometry of each medium F  transport element is defined using a two-byte field as defined below.   @  A rotate bit of one indicates that the medium transport elementG  supports media rotation for handling double-sided media.  A rotate bitnE  of zero indicates that the medium transport element does not supportl  media rotation.  hE  The member number in set indicates the position of this element in at>  set of medium transport elements that share a common roboticsC  subsystem. The first element in a set has a member number of zero.   uK     NOTE 208 This page reports information about the way transport elementsdH     are physically clustered in a system. The model for this is a mediumK     changer device with more than one independent robotics subsystem, where M     each of these supports multiple transport elements. The elements that aresI     supported by a particular robotics subsystem form a set. This sort ofdN     information is helpful for optimization and error recovery in such a largeJ     system.  (Recall that in the model for this device type, see 17.1, theL     individual transport element is addressed not the robotics subsystem. AnN     element is defined to be a place where a unit of media may be at any point
     in time.)    4  17.4 Definitions specific to medium changer devices  eG  17.4.1 data transfer element:  A component of a medium changer used totA  access the data stored on a unit of media. The address in medium ,  changer element space of a primary device.   fG  17.4.2 element:  An addressable physical component of a medium changer :  device that can serve as the location of a unit of media.  =B  17.4.3 import export element:  A location within a medium changerF  device that can be accessed by both the medium transport elements and  by the operator.    B  17.4.4 medium transport element:  A component of a medium changer.  device that is used to move units of media.    =E  17.4.5 media rotation:  The process of changing the orientation of a(H  unit of media. In particular this refers to inverting a two sided mediaH  cartridge so that a data transport element that can access only side at,  a time can access data on the other side.    |I  17.4.6 primary device:  A device for reading or writing data on medium. -F  These devices would typically implement the direct access, sequential=  access, optical memory device or CD-ROM command sets in thisnF  International Standard.  Examples are magnetic disk drives, cartridgeE  tape drives, optical disk drives and CD-ROM drives.  Use in a medium-H  changer environment implies that the device supports removable media.        E  17.4.7 storage element:  A component of a medium changer device used )  for inactive storage of a unit of media.r  l  n  18 Communications devices      !  18.1 Communications device model    @  A communications device provides a facility to send and receiveC  information over some medium (usually an electrical or fiber-optic B  cable) using a defined protocol to one or more other systems thatH  support the same protocol.  The media and protocols are often specifiedH  in national or international standards, although some are proprietary. C  Within this subclause, the protocol used on the external medium is-  called the external protocol.   A  The SCSI communications device model assumes that information to F  control the external protocol is embedded within the data transferredA  by the SEND and GET MESSAGE commands.  The structure of the data C  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.-   G  The SCSI communications device is a target with the characteristics of D  a network access device, typically attached to a local area networkE  (LAN), public telecommunications network, private telecommunications-I  network, or packet switching network, etc., with no theoretical limits.  B  Such a communications device is often called a network node.  The?  communications device transmits or receives packets of data as B  requested by the initiator.  The contents and meaning of the dataH  packets is not defined by this standard.  The bytes in the data packetsC  may or may not contain addressing, path selection, or path control G  information identifying separate data streams.  Additional informationsH  may be provided by the stream selection identifier found in the ten and3  twelve byte SEND MESSAGE and GET MESSAGE commands.-  -G  In the SCSI communications device, the target accepts and provides the G  data packets transferred in accordance with commands received from the >  initiator.  There is an assumption that the initiator and theG  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 theB  information.  These rules are not specified by this International
  Standard.   F  The initiator requests that the communications device accept a packetH  of data by transmitting a SEND MESSAGE command.  The initiator requestsG  that the communications device return a packet of data by transmittingt@  a GET MESSAGE command.  The communications device also supportsC  commands related to configuration of the network access device andnG  network management of the particular environment.  MODE SENSE and MODEt5  SELECT are examples of these configuration commands.r  pD  If a communications device temporarily has no resource available toB  handle a data packet from the initiator, or has no data packet toF  provide to the initiator, or has no resources assigned to perform theG  operation, the device may then choose one of the following responses: nL     a)     Terminate the command with CHECK CONDITION status.  The sense keyI            shall be set to NOT READY and the appropriate additional sense "            code for the condition.I     b)     Disconnect until the necessary resource or data packet becomesEH            available, and then reconnect to the initiator and resume the            operation.c2     c)     Terminate the command with BUSY status.   C  More than one logical unit  can be implemented by a communications H  device.   Logical units can serve as multiple paths to a single networkH  access device, and/or each logical unit can serve as a discrete path toG  different resources within the device.  A single logical unit may alsoOG  serve as a path to multiple resources if the communications device caniE  interpret information within the data packet and route the packet tol@  the appropriate resource.  If the logical unit addressed by theH  initiator does not have an available resource or data packet associatedH  with it, the communications device may choose to treat the logical unitF  as an invalid logical unit (see 7.5.3) or respond as described in the  previous paragraph.  rA  If the communications device determines that an error or unusualaF  condition has occurred while performing an operation specified by theG  contents of a data packet, the information describing the condition isoB  normally returned as a part of a data packet from another networkB  device.  If the communications device determines that an error orG  unusual condition has occurred while either executing the SCSI commandhG  from the initiator, or during a network medium access transaction, thel@  command is terminated with a CHECK CONDITION.  The failures are,  identified through a REQUEST SENSE command.  tG  The SCSI communications device is distinguished from an SCSI processor.D  device by the fact that the primary destination of the data packetsB  transferred to the communications device is not the target deviceG  itself, but another network node.  A SCSI communications device passes D  the data on to an ultimate destination outside the target through aG  network.  In contrast, the SCSI processor device is itself the primary B  destination of the data packets.  Devices requiring protocols andC  command sets that are totally incompatible with the communications.B  device protocols should be examined carefully to be sure that the:  incompatibilities are based on functional requirements.    a  18.1.1 Implementation examplese  fG  Several examples of communications device implementations are providedt5  to clarify the range of utility of this device type.y  s&  18.1.1.1 Host-to-host communications   aF  In this example of host to host communications, only the SEND MESSAGE  command is used.l  rG  A communications device (comm A) is attached to a network (net A), andaE  another communications device (comm B) is attached to a network (net=B  B).  Comm A takes the initiator role and selects a communicationsH  device (comm B), transmitting a packet to comm B using the SEND MESSAGEG  command.  After transmitting the packet on the attached network medium+A  (net B), the action required by the SEND MESSAGE command, comm B=B  assumes the initiator mode and selects comm A as a communicationsD  device, and uses a SEND MESSAGE command to transmit a packet on the&  network (net A) attached to comm A.     G     Note 209 The SEND MESSAGE command is sufficient to perform complete=K     transactions between communications devices if comm A and comm B act as N     initiators.  This provides the function of a network bridge or gateway forC     high bandwidth intercommunication among nearby host processors.=  =(  18.1.1.2 Host-to-device communications   RG  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),E  transmitting a packet on network net A to some other network node(s)tF  using the SEND MESSAGE command to comm A.  Host A then assumes that aE  result will be obtained by the other network node(s) consistent withaF  rules understood by all involved network devices.  Host A generates aD  GET MESSAGE command to obtain packets from other network nodes.  IfF  there are no packets that need handling pending at comm A, comm A mayA  disconnect until a packet arrives.  Comm A can then complete thefG  transaction,  reconnect to host A and the requested data packet can bemG  returned to host A.  Note that Host A need not support target mode anddC  Comm A need not support initiator mode to successfully complete aneC  exchange between the two devices.  The host system (host A) can be D  replaced by a communications device that is capable of acting as an  initiator.t  a'  18.1.1.3 Multiple role communications s  lF  In this example of multiple role communications, the SEND MESSAGE andE  GET MESSAGE commands are used.  The device acts as both a host and alG  communications device, depending on its needs and the requests made ini
  the network.a  nG  A communications device (comm A) is attached to a network (net A), andiF  another communications device (comm B)  is attached to a network (netB  B).  Comm A takes the initiator role and selects a communicationsH  device (comm B).  Comm A transmits a packet for network net B using theH  SEND MESSAGE command to comm B.  Comm A then requests data packets fromH  net B by issuing a GET MESSAGE command to the comm B device.  FollowingH  these actions, comm B assumes the initiator role and transmits a packetE  using the SEND MESSAGE command to comm A for transmission to networkcH  node(s) located on net A.  Comm B then requests data packets from net A,  by issuing a GET MESSAGE command to comm A.  a5  18.2 Command descriptions for communications devicesr  rH  The commands for communications devices shall be as shown in table 354.  u?                 Table 354 - Commands for communications deviceseI  +=====================================-============-======-============+rI  |  Command name                       | Operation  | Type |  Subclause |bI  |                                     |   code     |      |            |eI  |-------------------------------------+------------+------+------------|eI  | CHANGE DEFINITION                   |    40h     |   O  |   8.2.1    |aI  | GET MESSAGE(6)                      |    08h     |   O  |   8.2.17   |hI  | GET MESSAGE(10)                     |    28h     |   O  |  18.2.2    |sI  | GET MESSAGE(12)                     |    A8h     |   O  |  18.2.3    |nI  | INQUIRY                             |    12h     |   M  |   8.2.5    |eI  | LOG SELECT                          |    4Ch     |   O  |   8.2.6    |dI  | LOG SENSE                           |    4Dh     |   O  |   8.2.7    |,I  | MODE SELECT(6)                      |    15h     |   O  |   8.2.8    |mI  | MODE SELECT(10)                     |    55h     |   O  |   8.2.9    |iI  | MODE SENSE(6)                       |    1Ah     |   O  |   8.2.10   |iI  | MODE SENSE(10)                      |    5Ah     |   O  |   8.2.11   |tI  | READ BUFFER                         |    3Ch     |   O  |   8.2.12   |iI  | RECEIVE DIAGNOSTIC RESULTS          |    1Ch     |   O  |   8.2.13   |mI  | REQUEST SENSE                       |    03h     |   M  |   8.2.14   |cI  | SEND DIAGNOSTIC                     |    1Dh     |   M  |   8.2.15   |aI  | SEND MESSAGE(6)                     |    0Ah     |   M  |  18.2.4    |,I  | SEND MESSAGE(10)                    |    2Ah     |   O  |  18.2.5    | I  | SEND MESSAGE(12)                    |    AAh     |   O  |  18.2.6    |oI  | TEST UNIT READY                     |    00h     |   M  |   8.2.16   |aI  | WRITE BUFFER                        |    3Bh     |   O  |   8.2.17   |SI  |----------------------------------------------------------------------|iI  |Key:  M = command implementation is mandatory.                        |mI  |      O = command implementation is optional.                         | I  +======================================================================+   a  tF  All other operation codes for communications devices are reserved for  future standardization.  w  18.2.1 GET MESSAGE(6) command  nC  The GET MESSAGE(6) command (see table 355) transfers data from the.  target to the initiator.d  c9                        Table 355 - GET MESSAGE(6) commandiP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (08h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |                  Reserved                  |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                           Allocation length                           |P  |-----+---                                                                 ---|P  | 4   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+  n     18.2.2 GET MESSAGE(10) commandu   D  The GET MESSAGE(10) command (see table 356) transfers data from the  target to the initiator.I   9                       Table 356 - GET MESSAGE(10) command P  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (28h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |                  Reserved                  |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   | (MSB)                                                                 |P  |-----+---                        Stream selection                         ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   | (MSB)                                                                 |P  |-----+---                        Allocation length                        ---|P  | 8   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+     EG  The stream selection field specifies a further level of addressing fordH  the data, so that it can be accessed by the target from the appropriate
  data stream.c  s  18.2.3 GET MESSAGE(12) commando  dD  The GET MESSAGE(12) command (see table 357) transfers data from the  target to the initiator.p  e9                       Table 357 - GET MESSAGE(12) commandgP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (A8h)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |                  Reserved                  |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   | (MSB)                                                                 |P  |-----+---                        Stream selection                         ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 7   |                                                                       |P  |-----+---                        Allocation length                        ---|P  | 8   |                                                                       |P  |-----+---                                                                 ---|P  | 9   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 10  |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 11  |                           Control                                     |P  +=============================================================================+  m   G  The stream selection field specifies a further level of addressing forsH  the data, so that it can be accessed by the target from the appropriate
  data stream.   e  18.2.4 SEND MESSAGE(6) commandg  mD  The SEND MESSAGE(6) command (see table 358) transfers data from the  initiator to the target.    9                       Table 358 - SEND MESSAGE(6) commandyP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (0Ah)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |                  Reserved                  |P  |-----+-----------------------------------------------------------------------|P  | 2   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 3   |                           Transfer length                             |P  |-----+---                                                                 ---|P  | 4   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 5   |                           Control                                     |P  +=============================================================================+  =  =H  The transfer length specifies the length in bytes of data that shall beE  sent during the DATA OUT phase.  A transfer length of zero indicatescG  that no data shall be sent.  This condition shall not be considered an-  error.-  -   18.2.5 SEND MESSAGE(10) command  IE  The SEND MESSAGE(10) command (see table 359) transfers data from theE  initiator to the target.   8:                       Table 359 - SEND MESSAGE(10) commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (2Ah)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |                  Reserved                  |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   | (MSB)                                                                 |P  |-----+---                        Stream selection                         ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 7   | (MSB)                                                                 |P  |-----+---                        Transfer length                          ---|P  | 8   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 9   |                           Control                                     |P  +=============================================================================+  =  -G  The stream selection field specifies a further level of addressing for F  the data, so that it can be directed by the target to the appropriate
  data stream.    E  Please refer to the SEND MESSAGE(6) command for a description of the=  fields in this command.  =   18.2.6 SEND MESSAGE(12) command  0E  The SEND MESSAGE(12) command (see table 360) transfers data from the   initiator to the target.-  -:                       Table 360 - SEND MESSAGE(12) commandP  +=====-========-========-========-========-========-========-========-========+P  |  Bit|   7    |   6    |   5    |   4    |   3    |   2    |   1    |   0    |P  |Byte |        |        |        |        |        |        |        |        |P  |=====+=======================================================================|P  | 0   |                           Operation code (AAh)                        |P  |-----+-----------------------------------------------------------------------|P  | 1   | Logical unit number      |                  Reserved                  |P  |-----+-----------------------------------------------------------------------|P  | 2   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 3   |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 4   | (MSB)                                                                 |P  |-----+---                        Stream selection                         ---|P  | 5   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 6   | (MSB)                                                                 |P  |-----+---                                                                 ---|P  | 7   |                                                                       |P  |-----+---                        Transfer length                          ---|P  | 8   |                                                                       |P  |-----+---                                                                 ---|P  | 9   |                                                                 (LSB) |P  |-----+-----------------------------------------------------------------------|P  | 10  |                           Reserved                                    |P  |-----+-----------------------------------------------------------------------|P  | 11  |                           Control                                     |P  +=============================================================================+  -  -G  The stream selection field specifies a further level of addressing foreF  the data, so that it can be directed by the target to the appropriate
  data stream.-  -E  Please refer to the SEND MESSAGE(6) command for a description of the   fields in this command.   *  18.3 Parameters for communication devices  l  18.3.1 Diagnostic parameters    @  This subclause defines the descriptors and pages for diagnostic-  parameters used with communication devices. -  -C  The diagnostic page codes for communication devices are defined in   table 361.    8                        Table 361 - Diagnostic page codesP  +=============-==================================================-============+P  |  Page Code  |  Description                                     |  Subclause |P  |-------------+--------------------------------------------------+------------|P  |     00h     |  Supported log pages                             |   8.3.1.1  |P  |  01h - 3Fh  |  Reserved (for all device type pages)            |            |P  |  40h - 7Fh  |  Reserved                                        |            |P  |  80h - FFh  |  Vendor-specific pages                           |            |P  +=============================================================================+        18.3.2 Log parameters  |D  This subclause defines the descriptors and pages for log parameters"  used with communication devices.    G  The log page codes for communication devices are defined in table 362.-  -5                            Table 362 - Log page codes-P  +=============-==================================================-============+P  |  Page code  |  Description                                     |  Subclause |P  |-------------+--------------------------------------------------+------------|P  |     01h     |  Buffer over-run/under-run page                  |   8.3.2.1  |P  |     02h     |  Error counter page (write) page                 |   8.3.2.2  |P  |     03h     |  Error counter page (read) page                  |   8.3.2.2  |P  |     04h     |  Error counter page (read reverse) page          |   8.3.2.2  |P  |     05h     |  Error counter page (verify) page                |   8.3.2.2  |P  |     07h     |  Last n error events page                        |   8.3.2.3  |P  |     06h     |  Non-medium error page                           |   8.3.2.4  |P  |     00h     |  Supported log pages                             |   8.3.2.5  |P  |  08h - 2Fh  |  Reserved                                        |            |P  |  30h - 3Eh  |  Vendor-specific pages                           |            |P  |     3Fh     |  Reserved                                        |            |P  +=============================================================================+     -  18.3.3 Mode parameters    E  This subclause defines the descriptors and pages for mode parameters "  used with communication devices.    F  The mode parameter list, including the mode parameter header and mode(  block descriptor, are defined in 8.3.3.   E  The medium-type code field is contained in the mode parameter header+A  (see 8.3.3).  This field is reserved for communications devices.-  |G  The device specific parameter field is contained in the mode parameter H  header (see 8.3.3).  This field is reserved for communications devices.  =@  The density code field is contained in the mode parameter blockC  descriptor (see 8.3.3).  This field is reserved for communicationsy	  devices.   mG  The mode page codes for communications devices are shown in table 363.m  T5                           Table 363 - Mode page codestP  +=============-==================================================-============+P  |  Page code  |  Description                                     |  Subclause |P  |-------------+--------------------------------------------------+------------|P  |     0Ah     |  Control mode page                               |   8.3.3.1  |P  |     02h     |  Disconnect-reconnect page                       |   8.3.3.2  |P  |     09h     |  Peripheral device page                          |   8.3.3.3  |P  |     01h     |  Reserved                                        |            |P  |  03h - 08h  |  Reserved                                        |            |P  |  0Bh - 1Fh  |  Reserved                                        |            |P  |     00h     |  Vendor-specific (does not require page format)  |            |P  |  20h - 3Eh  |  Vendor-specific (page format required)          |            |P  |     3Fh     |  Return all pages                                |            |P  |             |     (valid only for the MODE SENSE command)      |            |P  +=============================================================================+      4  18.4 Definitions specific to communications devices  -H  18.4.1 communications device:   An SCSI device whose principal function?  is to communicate with one or more other systems, usually over=A  distances that exceed the maximum cable length defined for SCSI.=  TG  18.4.2 external medium:   The medium used by the communications devicesE  to send or receive information to or from one or more communicationstF  devices.  The other communications devices may or may not use an SCSI  interface.   .G  18.4.3 external protocol:   The protocol(s) used by the communicationseG  device to transfer information over the external medium.  The external <  protocol(s) are not defined by this International Standard.  =  =  =  =  Annex A  (informative)  =  SCSI signal sequence example|  7   F  This annex is included to provide an example of the signal sequencingH  of an I/O process that includes most of the SCSI bus phases (see figureH  29).  In this example, the target does not disconnect from the SCSI bus%  prior to completing the I/O process.    N     In a typical system, the computer's host adapter acts as the initiator andL     the peripheral device's controller acts as the target.  In general, thisM     International Standard does not attempt to distinguish between a computer-J     and its host adapter.  These functions may be separate or merged.  TheN     term initiator encompasses both.  The term target refers to the controllerC     portion of the peripheral device, which may be separate (bridge F     controller) from the peripheral device or merged with it (embeddedE     controller).  The term SCSI device refers to a device that may be-M     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. 9     2)     DB(7) is the highest priority arbitration bit.-J     3)     DB(P) is the data parity bit (odd).  Parity is not valid during!            the ARBITRATION phase.      BUS PHASE NOTESI     1)        BUS FREE phase.  BUS FREE phase begins when the SEL and BSY M               signals are both continuously false for a bus settle delay.  It|L               ends when the BSY signal becomes true.  (In the SCSI-1 single-J               initiator option, BUS FREE phase could also end when the SEL"               signal became true.)  -J     2)        ARBITRATION phase.  This phase is documented as mandatory in:               SCSI-2.  In SCSI-1, this phase was optional.  =L            At least one bus free delay after first detecting BUS FREE phase,L            but no more than a bus set delay after the bus was last free, theK            initiator asserts the BSY signal and its assigned SCSI device IDdJ            bit on the DATA BUS.  The initiator waits an arbitration delay,K            then examines the DATA BUS.  If a higher priority SCSI device ID K            bit is true, the initiator loses arbitration and may release theiI            BSY signal and its SCSI ID bit.  Otherwise, the initiator winsEI            arbitration and asserts the SEL signal.  All SCSI devices must-J            release the BSY signal and their SCSI ID bit within a bus clearI            delay after the SEL signal becomes true (even if they have not H            yet examined the DATA BUS).  The winning SCSI device waits atJ            least a bus clear delay plus a bus settle delay after assertingA            the SEL signal before changing any signals on the bus.-  -L     3)        SELECTION phase.  The I/O signal is false during this phase to8               distinguish it from the RESELECTION phase.  |J               NON-ARBITRATING SYSTEMS (only permitted in SCSI-1):  In suchK               systems, the initiator waits at least a bus clear delay after M               detecting BUS FREE phase, then it asserts the target's  SCSI ID-J               bit and, optionally, the initiator's SCSI ID bit on the DATAK               BUS.  After at least two deskew delays, the initiator asserts-               the SEL signal.S   M               ARBITRATING SYSTEMS:  In such systems, the SCSI device that won K               arbitration has both the BSY and SEL signals asserted.  After K               at least a bus clear delay plus a bus settle delay, it places-L               both the target's and the initiator's SCSI ID bits on the DATAI               BUS.  At least two deskew delays later, it releases the BSY                signal.    J               ALL SYSTEMS:  The target determines that it is selected whenM               the SEL signal and its SCSI ID bit are true and the BSY and I/O L               signals are false for at least a bus settle delay.  The targetM               then asserts the BSY signal within a selection abort time after-H               it last determined that it was still being selected.  (TheG               target is not required to respond to a selection within aSH               selection abort time;  but it must ensure that it will notJ               assert the BSY signal more than a selection abort time after8               the initiator aborts a selection attempt.)  -I            At least two deskew delays after the initiator detects the BSYC6            signal is true, it releases the SEL signal.  =J     4)        MESSAGE OUT phase.  During this phase the initiator sends anM               IDENTIFY message to the target.  The target asserts the C/D anddD               MSG signals and negates the I/O signal for the messageM               transfer.  After detecting the assertion of the REQ signal, theoG               initiator negates the ATN signal before asserting the ACKdH               signal.  (Refer to the handshake procedure for the command               phase.)    K     5)        COMMAND phase.  The target asserts the C/D signal and negatesiM               the I/O and MSG signals for all of the bytes transferred during M               this phase.  The direction of transfer is from the initiator to=               the target.=  =I            HANDSHAKE PROCEDURE:  The target asserts the REQ signal.  Upon J            detecting the REQ signal is true, the initiator drives the DATAK            BUS to the desired value, waits at least one deskew delay plus a K            cable skew delay and then asserts the ACK signal.  The initiatoriI            continues to drive the DATA BUS until the REQ signal is false.    J            When the ACK signal is true at the target, the target reads the4            DATA BUS and then negates the REQ signal.  =L            When the REQ signal becomes false at the initiator, the initiatorH            may change or release the DATA BUS and negate the ACK signal.  aL            The target may continue to request command bytes by asserting theJ            REQ signal again.  The number of command bytes is determined byL            the group code (most significant 3 bits) that is contained in the            first command byte.  =K     6)        DATA IN phase.  The target asserts the I/O signal and negates L               the C/D and MSG signal for all of the bytes transferred duringJ               this phase.  The direction of transfer is from the target to               the initiator.  0H            HANDSHAKE PROCEDURE:  The target first drives the DATA BUS toG            their desired values, waits at least one deskew delay plus a.I            cable skew delay, and then asserts the REQ signal.  The target H            continues to drive the DATA BUS until the ACK signal is true.   L            When the REQ signal is true at the initiator, the initiator reads8            the DATA BUS and then asserts the ACK signal.   K            When the ACK signal is true at the target, the target may changee=            or release the DATA BUS and negate the REQ signal.   eG            When the REQ signal is false at the initiator, the initiator F            negates the ACK signal.  After the ACK signal is false, theG            target may continue the transfer by driving the DATA BUS and 7            asserting the REQ signal as described above.=  =K     7)        DATA OUT phase (not shown in the figure).  The target negates L               the C/D, I/O, and MSG signals for all of the bytes transferredG               during this phase.  The direction of transfer is from thehM               initiator to the target.  (Refer to the handshake procedure forc!               the command phase.)p  mK     8)        STATUS phase.  The target asserts the C/D and I/O signals andsI               negates the MSG signal for the byte transferred during thiseI               phase.  The direction of transfer is from the target to theeK               initiator.  (Refer to the handshake procedure for the DATA INs               phase.)h  fI     9)        MESSAGE IN phase.  The target asserts the C/D, I/O, and MSGfE               signals during the byte transferred during this phase.  I               Typically, a command COMPLETE message would be sent at this=I               point.  The direction of transfer is from the target to the K               initiator.  (Refer to the handshake procedure for the DATA IN-               phase.)-  -F     10)       BUS FREE phase.  The target returns to BUS FREE phase byJ               releasing the BSY signal.  Both the target and the initiatorL               release all bus signals within a bus clear delay after the BSYB               signal is continuously false for a bus settle delay.  v                                         |  |  3           e  d                                                  F  |  e  v                  <                    Figure A.1 - SCSI signal sequence example  i  d     Annex B  (informative)     Fast SCSI skew time      D  This annex is included to explain the skew budget for the fast SCSI%  option which is defined in Clause 4.    F  Synchronous transfer rates using a transfer period between 100 ns andD  200 ns are known as the fast SCSI option.  Fast data transfer timesF  have been tested using the following skew budget (see table B.1) withF  the differential alternative using transceivers with 25 m of 0,080 42<  mm2 (28 AWG) twisted pair cable as specified in 5.2.3.  TheF  transceivers were subjected to a maximum temperature difference of 255  degrees C and a maximum of 200 mV of VCC difference.1  .9                       Table B.1 - Fast SCSI jitter budgetdP  +================-============================================-===============+P  |       Parameter|                                            | Jitter budget |P  |           label|           Description                      |    +/- ns     |P  |----------------+--------------------------------------------+---------------|P  |              a | clock offset                               |       5       |P  |              b | transmitting logic skew                    |       3       |P  |Transmitting  c | foil delay                                 |       1       |P  |  Device      d | transmitter propogation delay skew         |       6       |P  |              e | foil delay                                 |       1       |P  |              f | drop cable propogation delay               |       1       |P  |-- Connector  --|--------------------------------------------|---------------|P  |              g | external cable - skew between pairs        |       5       |P  |   Cable      h | distortion due to cable impedance          |       1       |P  |              i | distortion due to intersymbol interferance |       2       |P  |              j | bias distortion                            |       2       |P  |-- Connector  --|--------------------------------------------|---------------|P  |              k | drop cable propogation delay               |       1       |P  |Receiving     l | foil delay                                 |       1       |P  | Device       m | receiver propogation delay skew            |       9       |P  |              n | foil delay                                 |       1       |P  |              o | logic setup/hold                           |       5       |P  |----------------+--------------------------------------------+---------------|P  |                | total jitter budget                        |      44       |P  +=============================================================================+  tF  Mapping the above jitter or skew budget to the SCSI format in 5.7 and  5.8 is done in Table B.2.  L:                      Table B.2 - Mapping of jitter to SCSI8  +=======================-=============-===============+8  | SCSI timing parameter | Calculation | Value (ns)    |8  |-----------------------+-------------+---------------|8  | Fast cable skew delay |      g      |   5           |8  | Fast deskew delay     |  SUM(h..n)  |  20 (note 1)  |8  | Fast hold time        |      o      |  10 (note 1)  |8  | Fast assertion period |   (note 2)  |  30           |8  | Fast negation period  |   (note 2)  |  30           |8  |-----------------------------------------------------|8  | Notes                                               |8  |  1) Value is rounded up from the jitter budget.     |8  |  2) The fast assertion period and fast negation     |8  |     period are derived from isolated pulse          |8  |     mesurements and represent a minimum pulse width |8  |     with a satisfactory margin.                     |8  +=====================================================+      I  The maximum driver skew allowed was 6 ns (tPLH min. - tPHL max.) and the G  maximum receiver skew tested was 9 ns (tPLH min. - tPHL max.).  ValuesnF  greater than these could be used if other numbers could be reduced --  the sum is what is important.   E  Fast data transfer timing parameters were not tested for the single- D  ended transceiver option prior to publication of this International
  Standard.  ,  e  i  Annex C  (informative)  l&  Other SCSI standardization activities  U  R@  This annex provides information on other formal standardization  activities related to SCSI.  s  C.1 SCSI-3 standards projects   G  Accredited Standards Committee X3 has approved several SCSI-3 projects H  to enhance and restructure the SCSI-2 standard as shown in figure C.1. F  These projects (except fibre channel) are assigned to the X3T9.2 TaskA  Group which developed this International Standard and the SCSI-1b=  standard.  Please contact the Chairman of X3T9.2 for further '  information concerning these projects.C  I9  C.2 Digital data exchange for colour electronic prepress   systems   C  Accredited Standards Committee IT8 has developed several standardsYE  pertaining to the exchange of digital data between colour electronichA  prepress systems.  These devices are used for high quality color G  printing.  At least one of the IT8 projects involves transferring such C  data over SCSI.  Please contact the Secretariat of IT8 for furtherm'  information concerning their projects.d  a  C.3 Fibre channel  lF  Accredited Standards Committee X3 has approved a project to develop aB  fibre optic channel physical layer for the Intelligent PeripheralC  Interface (IPI), SCSI, and the High Performance Parallel Interface E  (HIPPI).  This project is assigned to the X3T9.3 Task Group.  PleaseiG  contact the Chairman of X3T9.3 for further information concerning thiso	  project.h  S           s  a  s  u  i  e  s  t  S  s  a                 E;                     Figure C.1 - SCSI-3 standards structure            N  Annex D  (informative)  T  Numeric order codes     dF  This annex contains SCSI-2 additional sense codes and operation codesB  in numeric order as a reference.  In the event of a conflict withC  between the codes in this annex and the body of this Internationale?  Standard, the codes in the body should be regarded as correct.o  uE  Table D.1 is a numerical order listing of the additional sense codesh*  and the additional sense code qualifiers.  a:                       Table D.1 - ASC and ASCQ assignmentsP  +=============================================================================+P  |           D - DIRECT ACCESS DEVICE                                          |P  |           .T - SEQUENTIAL ACCESS DEVICE                                     |P  |           . L - PRINTER DEVICE                                              |P  |           .  P - PROCESSOR DEVICE                                           |P  |           .  .W - WRITE ONCE READ MULTIPLE DEVICE                           |P  |           .  . R - READ ONLY (CD-ROM) DEVICE                                |P  |           .  .  S - SCANNER DEVICE                                          |P  |           .  .  .O - OPTICAL MEMORY DEVICE                                  |P  |           .  .  . M - MEDIA CHANGER DEVICE                                  |P  |           .  .  .  C - COMMUNICATION DEVICE                                 |P  |           .  .  .  .                                                        |P  | ASC ASCQ  DTLPWRSOMC  DESCRIPTION                                           |P  | --- ----              ----------------------------------------------------- |P  |  00  00   DTLPWRSOMC  NO ADDITIONAL SENSE INFORMATION                       |P  |  00  01    T          FILEMARK DETECTED                                     |P  |  00  02    T    S     END-OF-PARTITION/MEDIUM DETECTED                      |P  |  00  03    T          SETMARK DETECTED                                      |P  |  00  04    T    S     BEGINNING-OF-PARTITION/MEDIUM DETECTED                |P  |  00  05    T    S     END-OF-DATA DETECTED                                  |P  |  00  06   DTLPWRSOMC  I/O PROCESS TERMINATED                                |P  |  00  11   R           AUDIO PLAY OPERATION IN PROGRESS                      |P  |  00  12   R           AUDIO PLAY OPERATION PAUSED                           |P  |  00  13   R           AUDIO PLAY OPERATION SUCCESSFULLY COMPLETED           |P  |  00  14   R           AUDIO PLAY OPERATION STOPPED DUE TO ERROR             |P  |  00  15   R           NO CURRENT AUDIO STATUS TO RETURN                     |P  |  01  00   DW  O       NO INDEX/SECTOR SIGNAL                                |P  |  02  00   DWR OM      NO SEEK COMPLETE                                      |P  |  03  00   DTL W SO    PERIPHERAL DEVICE WRITE FAULT                         |P  |  03  01    T          NO WRITE CURRENT                                      |P  |  03  02    T          EXCESSIVE WRITE ERRORS                                |P  |  04  00   DTLPWRSOMC  LOGICAL UNIT NOT READY, CAUSE NOT REPORTABLE          |P  |  04  01   DTLPWRSOMC  LOGICAL UNIT IS IN PROCESS OF BECOMING READY          |P  |  04  02   DTLPWRSOMC  LOGICAL UNIT NOT READY, INITIALIZING command REQUIRED |P  |  04  03   DTLPWRSOMC  LOGICAL UNIT NOT READY, MANUAL INTERVENTION REQUIRED  |P  |  04  04   DTL    O    LOGICAL UNIT NOT READY, FORMAT IN PROGRESS            |P  |  05  00   DTL WRSOMC  LOGICAL UNIT DOES NOT RESPOND TO SELECTION            |P  |  06  00   DWR OM  NO  REFERENCE POSITION FOUND                              |P  |  07  00   DTL WRSOM   MULTIPLE PERIPHERAL DEVICES SELECTED                  |P  |  08  00   DTL WRSOMC  LOGICAL UNIT COMMUNICATION FAILURE                    |P  |  08  01   DTL WRSOMC  LOGICAL UNIT COMMUNICATION TIME-OUT                   |P  |  08  02   DTL WRSOMC  LOGICAL UNIT COMMUNICATION PARITY ERROR               |P  |  09  00   DT  WR O    TRACK FOLLOWING ERROR                                 |P  |  09  01       WR O    TRACKING SERVO FAILURE                                |P  |  09  02       WR O    FOCUS SERVO FAILURE                                   |P  |  09  03       WR O    SPINDLE SERVO FAILURE                                 |P  +=============================================================================+  e  i  Table D.1  (continued)oP  +=============================================================================+P  |           D - DIRECT ACCESS DEVICE                                          |P  |           .T - SEQUENTIAL ACCESS DEVICE                                     |P  |           . L - PRINTER DEVICE                                              |P  |           .  P - PROCESSOR DEVICE                                           |P  |           .  .W - WRITE ONCE READ MULTIPLE DEVICE                           |P  |           .  . R - READ ONLY (CD-ROM) DEVICE                                |P  |           .  .  S - SCANNER DEVICE                                          |P  |           .  .  .O - OPTICAL MEMORY DEVICE                                  |P  |           .  .  . M - MEDIA CHANGER DEVICE                                  |P  |           .  .  .  C - COMMUNICATION DEVICE                                 |P  |           .  .  .  .                                                        |P  | ASC ASCQ  DTLPWRSOMC  DESCRIPTION                                           |P  | --- ----              ----------------------------------------------------- |P  |  0A  00   DTLPWRSOMC  ERROR LOG OVERFLOW                                    |P  |  0B  00                                                                     |P  |  0C  00    T     S    WRITE ERROR                                           |P  |  0C  01   D   W  O    WRITE ERROR RECOVERED WITH AUTO REALLOCATION          |P  |  0C  02   D   W  O    WRITE ERROR - AUTO REALLOCATION FAILED                |P  |  0D  00                                                                     |P  |  0E  00                                                                     |P  |  0F  00                                                                     |P  |  10  00   D   W  O    ID CRC OR ECC ERROR                                   |P  |  11  00   DT  WRSO    UNRECOVERED READ ERROR                                |P  |  11  01   DT  W SO    READ RETRIES EXHAUSTED                                |P  |  11  02   DT  W SO    ERROR TOO LONG TO CORRECT                             |P  |  11  03   DT  W SO    MULTIPLE READ ERRORS                                  |P  |  11  04   D   W  O    UNRECOVERED READ ERROR - AUTO REALLOCATE FAILED       |P  |  11  05       WR O    L-EC UNCORRECTABLE ERROR                              |P  |  11  06       WR O    CIRC UNRECOVERED ERROR                                |P  |  11  07       W  O    DATA RESYNCHRONIZATION ERROR                          |P  |  11  08    T          INCOMPLETE BLOCK READ                                 |P  |  11  09    T          NO GAP FOUND                                          |P  |  11  0A   DT     O    MISCORRECTED ERROR                                    |P  |  11  0B   D   W  O    UNRECOVERED READ ERROR - RECOMMEND REASSIGNMENT       |P  |  11  0C   D   W  O    UNRECOVERED READ ERROR - RECOMMEND REWRITE THE DATA   |P  |  12  00   D   W  O    ADDRESS MARK NOT FOUND FOR ID FIELD                   |P  |  13  00   D   W  O    ADDRESS MARK NOT FOUND FOR DATA FIELD                 |P  |  14  00   DTL WRSO    RECORDED ENTITY NOT FOUND                             |P  |  14  01   DT  WR O    RECORD NOT FOUND                                      |P  |  14  02    T          FILEMARK OR SETMARK NOT FOUND                         |P  |  14  03    T          END-OF-DATA NOT FOUND                                 |P  |  14  04    T          BLOCK SEQUENCE ERROR                                  |P  |  15  00   DTL WRSOM   RANDOM POSITIONING ERROR                              |P  |  15  01   DTL WRSOM   MECHANICAL POSITIONING ERROR                          |P  |  15  02   DT  WR O    POSITIONING ERROR DETECTED BY READ OF MEDIUM          |P  |  16  00   DW     O    DATA SYNCHRONIZATION MARK ERROR                       |P  |  17  00   DT  WRSO    RECOVERED DATA WITH NO ERROR CORRECTION APPLIED       |P  |  17  01   DT  WRSO    RECOVERED DATA WITH RETRIES                           |P  |  17  02   DT  WR O    RECOVERED DATA WITH POSITIVE HEAD OFFSET              |P  |  17  03   DT  WR O    RECOVERED DATA WITH NEGATIVE HEAD OFFSET              |P  |  17  04       WR O    RECOVERED DATA WITH RETRIES AND/OR CIRC APPLIED       |P  |  17  05   D   WR O    RECOVERED DATA USING PREVIOUS SECTOR ID               |P  |  17  06   D   W  O    RECOVERED DATA WITHOUT ECC - DATA AUTO-REALLOCATED    |P  |  17  07   D   W  O    RECOVERED DATA WITHOUT ECC - RECOMMEND REASSIGNMENT   |P  |  17  08   D   W  O    RECOVERED DATA WITHOUT ECC - RECOMMEND REWRITE        |P  |  18  00   DT  WR O    RECOVERED DATA WITH ERROR CORRECTION APPLIED          |P  |  18  01   D   WR O    RECOVERED DATA WITH ERROR CORRECTION & RETRIES APPLIED|P  |  18  02   D   WR O    RECOVERED DATA - DATA AUTO-REALLOCATED                |P  |  18  03        R      RECOVERED DATA WITH CIRC                              |P  |  18  04        R      RECOVERED DATA WITH LEC                               |P  |  18  05   D   WR O    RECOVERED DATA - RECOMMEND REASSIGNMENT               |P  |  18  06   D   WR O    RECOVERED DATA - RECOMMEND REWRITE                    |P  +=============================================================================+  e  n  Table D.1  (continued)CP  +=============================================================================+P  |           D - DIRECT ACCESS DEVICE                                          |P  |           .T - SEQUENTIAL ACCESS DEVICE                                     |P  |           . L - PRINTER DEVICE                                              |P  |           .  P - PROCESSOR DEVICE                                           |P  |           .  .W - WRITE ONCE READ MULTIPLE DEVICE                           |P  |           .  . R - READ ONLY (CD-ROM) DEVICE                                |P  |           .  .  S - SCANNER DEVICE                                          |P  |           .  .  .O - OPTICAL MEMORY DEVICE                                  |P  |           .  .  . M - MEDIA CHANGER DEVICE                                  |P  |           .  .  .  C - COMMUNICATION DEVICE                                 |P  |           .  .  .  .                                                        |P  | ASC ASCQ  DTLPWRSOMC  DESCRIPTION                                           |P  | --- ----              ----------------------------------------------------- |P  |  19  00   D      O    DEFECT LIST ERROR                                     |P  |  19  01   D      O    DEFECT LIST NOT AVAILABLE                             |P  |  19  02   D      O    DEFECT LIST ERROR IN PRIMARY LIST                     |P  |  19  03   D      O    DEFECT LIST ERROR IN GROWN LIST                       |P  |  1A  00   DTLPWRSOMC  PARAMETER LIST LENGTH ERROR                           |P  |  1B  00   DTLPWRSOMC  SYNCHRONOUS DATA TRANSFER ERROR                       |P  |  1C  00   D      O    DEFECT LIST NOT FOUND                                 |P  |  1C  01   D      O    PRIMARY DEFECT LIST NOT FOUND                         |P  |  1C  02   D      O    GROWN DEFECT LIST NOT FOUND                           |P  |  1D  00   D   W  O    MISCOMPARE DURING VERIFY OPERATION                    |P  |  1E  00   D   W  O    RECOVERED ID WITH ECC                                 |P  |  1F  00                                                                     |P  |  20  00   DTLPWRSOMC  INVALID command OPERATION CODE                        |P  |  21  00   DT  WR OM   LOGICAL BLOCK ADDRESS OUT OF RANGE                    |P  |  21  01           M   INVALID ELEMENT ADDRESS                               |P  |  22  00   D           ILLEGAL FUNCTION (SHOULD USE 20 00, 24 00, OR 26 00)  |P  |  23  00                                                                     |P  |  24  00   DTLPWRSOMC  INVALID FIELD IN CDB                                  |P  |  25  00   DTLPWRSOMC  LOGICAL UNIT NOT SUPPORTED                            |P  |  26  00   DTLPWRSOMC  INVALID FIELD IN PARAMETER LIST                       |P  |  26  01   DTLPWRSOMC  PARAMETER NOT SUPPORTED                               |P  |  26  02   DTLPWRSOMC  PARAMETER VALUE INVALID                               |P  |  26  03   DTLPWRSOMC  THRESHOLD PARAMETERS NOT SUPPORTED                    |P  |  27  00   DT  W  O    WRITE PROTECTED                                       |P  |  28  00   DTLPWRSOMC  NOT READY TO READY TRANSITION(MEDIUM MAY HAVE CHANGED)|P  |  28  01           M   IMPORT OR EXPORT ELEMENT ACCESSED                     |P  |  29  00   DTLPWRSOMC  POWER ON, RESET, OR BUS DEVICE RESET OCCURRED         |P  |  2A  00   DTL WRSOMC  PARAMETERS CHANGED                                    |P  |  2A  01   DTL WRSOMC  MODE PARAMETERS CHANGED                               |P  |  2A  02   DTL WRSOMC  LOG PARAMETERS CHANGED                                |P  |  2B  00   DTLPWRSO C  COPY CANNOT EXECUTE SINCE HOST CANNOT DISCONNECT      |P  |  2C  00   DTLPWRSOMC  command SEQUENCE ERROR                                |P  |  2C  01         S     TOO MANY WINDOWS SPECIFIED                            |P  |  2C  02         S     INVALID COMBINATION OF WINDOWS SPECIFIED              |P  |  2D  00    T          OVERWRITE ERROR ON UPDATE IN PLACE                    |P  |  2E  00                                                                     |P  |  2F  00   DTLPWRSOMC  commandS CLEARED BY ANOTHER INITIATOR                 |P  |  30  00   DT  WR OM   INCOMPATIBLE MEDIUM INSTALLED                         |P  |  30  01   DT  WR O    CANNOT READ MEDIUM - UNKNOWN FORMAT                   |P  |  30  02   DT  WR O    CANNOT READ MEDIUM - INCOMPATIBLE FORMAT              |P  |  30  03   DT          CLEANING CARTRIDGE INSTALLED                          |P  |  31  00   DT  W  O    MEDIUM FORMAT CORRUPTED                               |P  |  31  01   D L    O    FORMAT command FAILED                                 |P  |  32  00   D   W  O    NO DEFECT SPARE LOCATION AVAILABLE                    |P  |  32  01   D   W  O    DEFECT LIST UPDATE FAILURE                            |P  |  33  00    T          TAPE LENGTH ERROR                                     |P  |  34  00                                                                     |P  |  35  00                                                                     |P  |  36  00     L         RIBBON, INK, OR TONER FAILURE                         |P  +=============================================================================+        Table D.1  (continued) P  +=============================================================================+P  |           D - DIRECT ACCESS DEVICE                                          |P  |           .T - SEQUENTIAL ACCESS DEVICE                                     |P  |           . L - PRINTER DEVICE                                              |P  |           .  P - PROCESSOR DEVICE                                           |P  |           .  .W - WRITE ONCE READ MULTIPLE DEVICE                           |P  |           .  . R - READ ONLY (CD-ROM) DEVICE                                |P  |           .  .  S - SCANNER DEVICE                                          |P  |           .  .  .O - OPTICAL MEMORY DEVICE                                  |P  |           .  .  . M - MEDIA CHANGER DEVICE                                  |P  |           .  .  .  C - COMMUNICATION DEVICE                                 |P  |           .  .  .  .                                                        |P  | ASC ASCQ  DTLPWRSOMC  DESCRIPTION                                           |P  | --- ----              ----------------------------------------------------- |P  |  37  00   DTL WRSOMC  ROUNDED PARAMETER                                     |P  |  38  00                                                                     |P  |  39  00   DTL WRSOMC  SAVING PARAMETERS NOT SUPPORTED                       |P  |  3A  00   DTL WRSOM   MEDIUM NOT PRESENT                                    |P  |  3B  00    TL         SEQUENTIAL POSITIONING ERROR                          |P  |  3B  01    T          TAPE POSITION ERROR AT BEGINNING-OF-MEDIUM            |P  |  3B  02    T          TAPE POSITION ERROR AT END-OF-MEDIUM                  |P  |  3B  03     L         TAPE OR ELECTRONIC VERTICAL FORMS UNIT NOT READY      |P  |  3B  04     L         SLEW FAILURE                                          |P  |  3B  05     L         PAPER JAM                                             |P  |  3B  06     L         FAILED TO SENSE TOP-OF-FORM                           |P  |  3B  07     L         FAILED TO SENSE BOTTOM-OF-FORM                        |P  |  3B  08    T          REPOSITION ERROR                                      |P  |  3B  09         S     READ PAST END OF MEDIUM                               |P  |  3B  0A         S     READ PAST BEGINNING OF MEDIUM                         |P  |  3B  0B         S     POSITION PAST END OF MEDIUM                           |P  |  3B  0C         S     POSITION PAST BEGINNING OF MEDIUM                     |P  |  3B  0D           M   MEDIUM DESTINATION ELEMENT FULL                       |P  |  3B  0E           M   MEDIUM SOURCE ELEMENT EMPTY                           |P  |  3C  00                                                                     |P  |  3D  00   DTLPWRSOMC  INVALID BITS IN IDENTIFY MESSAGE                      |P  |  3E  00   DTLPWRSOMC  LOGICAL UNIT HAS NOT SELF-CONFIGURED YET              |P  |  3F  00   DTLPWRSOMC  TARGET OPERATING CONDITIONS HAVE CHANGED              |P  |  3F  01   DTLPWRSOMC  MICROCODE HAS BEEN CHANGED                            |P  |  3F  02   DTLPWRSOMC  CHANGED OPERATING DEFINITION                          |P  |  3F  03   DTLPWRSOMC  INQUIRY DATA HAS CHANGED                              |P  |  40  00   D           RAM FAILURE (SHOULD USE 40 NN)                        |P  |  40  NN   DTLPWRSOMC  DIAGNOSTIC FAILURE ON COMPONENT NN (80H-FFH)          |P  |  41  00   D           DATA PATH FAILURE (SHOULD USE 40 NN)                  |P  |  42  00   D           POWER-ON OR SELF-TEST FAILURE (SHOULD USE 40 NN)      |P  |  43  00   DTLPWRSOMC  MESSAGE ERROR                                         |P  |  44  00   DTLPWRSOMC  INTERNAL TARGET FAILURE                               |P  |  45  00   DTLPWRSOMC  SELECT OR RESELECT FAILURE                            |P  |  46  00   DTLPWRSOMC  UNSUCCESSFUL SOFT RESET                               |P  |  47  00   DTLPWRSOMC  SCSI PARITY ERROR                                     |P  |  48  00   DTLPWRSOMC  INITIATOR DETECTED ERROR MESSAGE RECEIVED             |P  |  49  00   DTLPWRSOMC  INVALID MESSAGE ERROR                                 |P  |  4A  00   DTLPWRSOMC  command PHASE ERROR                                   |P  |  4B  00   DTLPWRSOMC  DATA PHASE ERROR                                      |P  |  4C  00   DTLPWRSOMC  LOGICAL UNIT FAILED SELF-CONFIGURATION                |P  |  4D  00                                                                     |P  |  4E  00   DTLPWRSOMC  OVERLAPPED COMMANDS ATTEMPTED                         |P  |  4F  00                                                                     |P  |  50  00    T          WRITE APPEND ERROR                                    |P  |  50  01    T          WRITE APPEND POSITION ERROR                           |P  |  50  02    T          POSITION ERROR RELATED TO TIMING                      |P  |  51  00    T     O    ERASE FAILURE                                         |P  |  52  00    T          CARTRIDGE FAULT                                       |P  +=============================================================================+        Table D.1  (continued) P  +=============================================================================+P  |           D - DIRECT ACCESS DEVICE                                          |P  |           .T - SEQUENTIAL ACCESS DEVICE                                     |P  |           . L - PRINTER DEVICE                                              |P  |           .  P - PROCESSOR DEVICE                                           |P  |           .  .W - WRITE ONCE READ MULTIPLE DEVICE                           |P  |           .  . R - READ ONLY (CD-ROM) DEVICE                                |P  |           .  .  S - SCANNER DEVICE                                          |P  |           .  .  .O - OPTICAL MEMORY DEVICE                                  |P  |           .  .  . M - MEDIA CHANGER DEVICE                                  |P  |           .  .  .  C - COMMUNICATION DEVICE                                 |P  |           .  .  .  .                                                        |P  | ASC ASCQ  DTLPWRSOMC  DESCRIPTION                                           |P  | --- ----              ----------------------------------------------------- |P  |  53  00   DTL WRSOM   MEDIA LOAD OR EJECT FAILED                            |P  |  53  01    T          UNLOAD TAPE FAILURE                                   |P  |  53  02   DT  WR OM   MEDIUM REMOVAL PREVENTED                              |P  |  54  00      P        SCSI TO HOST SYSTEM INTERFACE FAILURE                 |P  |  55  00      P        SYSTEM RESOURCE FAILURE                               |P  |  56  00                                                                     |P  |  57  00        R      UNABLE TO RECOVER TABLE-OF-CONTENTS                   |P  |  58  00     O         GENERATION DOES NOT EXIST                             |P  |  59  00     O         UPDATED BLOCK READ                                    |P  |  5A  00   DTLPWRSOM   OPERATOR REQUEST OR STATE CHANGE INPUT (UNSPECIFIED)  |P  |  5A  01   DT  WR OM   OPERATOR MEDIUM REMOVAL REQUEST                       |P  |  5A  02   DT  W  O    OPERATOR SELECTED WRITE PROTECT                       |P  |  5A  03   DT  W  O    OPERATOR SELECTED WRITE PERMIT                        |P  |  5B  00   DTLPWRSOM   LOG EXCEPTION                                         |P  |  5B  01   DTLPWRSOM   THRESHOLD CONDITION MET                               |P  |  5B  02   DTLPWRSOM   LOG COUNTER AT MAXIMUM                                |P  |  5B  03   DTLPWRSOM   LOG LIST CODES EXHAUSTED                              |P  |  5C  00   D   O       RPL STATUS CHANGE                                     |P  |  5C  01   D   O       SPINDLES SYNCHRONIZED                                 |P  |  5C  02   D   O       SPINDLES NOT SYNCHRONIZED                             |P  |  5D  00                                                                     |P  |  5E  00                                                                     |P  |  5F  00                                                                     |P  |  60  00         S     LAMP FAILURE                                          |P  |  61  00         S     VIDEO ACQUISITION ERROR                               |P  |  61  01         S     UNABLE TO ACQUIRE VIDEO                               |P  |  61  02         S     OUT OF FOCUS                                          |P  |  62  00         S     SCAN HEAD POSITIONING ERROR                           |P  |  63  00        R      END OF USER AREA ENCOUNTERED ON THIS TRACK            |P  |  64  00        R      ILLEGAL MODE FOR THIS TRACK                           |P  |  65  00                                                                     |P  |  66  00                                                                     |P  |  67  00                                                                     |P  |  68  00                                                                     |P  |  69  00                                                                     |P  |  6A  00                                                                     |P  |  6B  00                                                                     |P  |  6C  00                                                                     |P  |  6D  00                                                                     |P  |  6E  00                                                                     |P  |  6F  00                                                                     |P  +=============================================================================+  |  |  Table D.1  (concluded)PP  +=============================================================================+P  |           D - DIRECT ACCESS DEVICE                                          |P  |           .T - SEQUENTIAL ACCESS DEVICE                                     |P  |           . L - PRINTER DEVICE                                              |P  |           .  P - PROCESSOR DEVICE                                           |P  |           .  .W - WRITE ONCE READ MULTIPLE DEVICE                           |P  |           .  . R - READ ONLY (CD-ROM) DEVICE                                |P  |           .  .  S - SCANNER DEVICE                                          |P  |           .  .  .O - OPTICAL MEMORY DEVICE                                  |P  |           .  .  . M - MEDIA CHANGER DEVICE                                  |P  |           .  .  .  C - COMMUNICATION DEVICE                                 |P  |           .  .  .  .                                                        |P  | ASC ASCQ  DTLPWRSOMC  DESCRIPTION                                           |P  | --- ----              ----------------------------------------------------- |P  |  70  00                                                                     |P  |  71  00                                                                     |P  |  72  00                                                                     |P  |  73  00                                                                     |P  |  74  00                                                                     |P  |  75  00                                                                     |P  |  76  00                                                                     |P  |  77  00                                                                     |P  |  78  00                                                                     |P  |  79  00                                                                     |P  |  7A  00                                                                     |P  |  7B  00                                                                     |P  |  7C  00                                                                     |P  |  7D  00                                                                     |P  |  7E  00                                                                     |P  |  7F  00                                                                     |P  |                                                                             |P  |  80  xxh \                                                                  |P  |   THROUGH >  Vendor-specific.                                               |P  |  FF  xxh /                                                                  |P  |                                                                             |P  |  xxh 80 \                                                                   |P  |  THROUGH >  Vendor-specific QUALIFICATION OF STANDARD ASC.                  |P  |  xxh FF /                                                                   |P  |               ALL CODES NOT SHOWN OR BLANK ARE RESERVED.                    |P  +=============================================================================+  |  |  EG  Table D.2 is a numerical order listing of the command operation codes.|  |9                        Table D.2 - SCSI-2 Operation CodesNP  +=============================================================================+P  |           D - DIRECT ACCESS DEVICE                       Device column key  |P  |           .T - SEQUENTIAL ACCESS DEVICE                  M = Mandatory      |P  |           . L - PRINTER DEVICE                           O = Optional       |P  |           .  P - PROCESSOR DEVICE                        V = Vendor-specific|P  |           .  .W - WRITE ONCE READ MULTIPLE DEVICE        R = Reserved       |P  |           .  . R - READ ONLY (CD-ROM) DEVICE                                |P  |           .  .  S - SCANNER DEVICE                                          |P  |           .  .  .O - OPTICAL MEMORY DEVICE                                  |P  |           .  .  . M - MEDIA CHANGER DEVICE                                  |P  |           .  .  .  C - COMMUNICATION DEVICE                                 |P  |           .  .  .  .                                                        |P  |        OP DTLPWRSOMC Description                                            |P  |----------+----------+-------------------------------------------------------|P  |        00 MMMMMMMMMM TEST UNIT READY                                        |P  |        01  M         REWIND                                                 |P  |        01 O V OO OO  REZERO UNIT                                            |P  |        02 VVVVVV  V                                                         |P  |        03 MMMMMMMMMM REQUEST SENSE                                          |P  |        04   O        FORMAT                                                 |P  |        04 M      O   FORMAT UNIT                                            |P  |        05 VMVVVV  V  READ BLOCK LIMITS                                      |P  |        06 VVVVVV  V                                                         |P  |        07         O  INITIALIZE ELEMENT STATUS                              |P  |        07 OVV O  OV  REASSIGN BLOCKS                                        |P  |        08          M GET MESSAGE(06)                                        |P  |        08 OMV OO OV  READ(06)                                               |P  |        08    O       RECEIVE                                                |P  |        09 VVVVVV  V                                                         |P  |        0A   M        PRINT                                                  |P  |        0A          M SEND MESSAGE(06)                                       |P  |        0A    M       SEND(06)                                               |P  |        0A OM  O  OV  WRITE(06)                                              |P  |        0B O   OO OV  SEEK(06)                                               |P  |        0B   O        SLEW AND PRINT                                         |P  |        0C VVVVVV  V                                                         |P  |        0D VVVVVV  V                                                         |P  |        0E VVVVVV  V                                                         |P  |        0F VOVVVV  V  READ REVERSE                                           |P  |        10   O O      SYNCHRONIZE BUFFER                                     |P  |        10 VM VVV     WRITE FILEMARKS                                        |P  |        11 VMVVVV     SPACE                                                  |P  |        12 MMMMMMMMMM INQUIRY                                                |P  |        13 VOVVVV     VERIFY(06)                                             |P  |        14 VOOVVV     RECOVER BUFFERED DATA                                  |P  |        15 OMO OOOOOO MODE SELECT(06)                                        |P  |        16 M   MM MO  RESERVE                                                |P  |        16  MM   M    RESERVE UNIT                                           |P  |        17 M   MM MO  RELEASE                                                |P  |        17  MM   M    RELEASE UNIT                                           |P  |        18 OOOOOOOO   COPY                                                   |P  |        19 VMVVVV     ERASE                                                  |P  |        1A OMO OOOOOO MODE SENSE(06)                                         |P  |        1B  O         LOAD UNLOAD                                            |P  |        1B       O    SCAN                                                   |P  |        1B   O        STOP PRINT                                             |P  |        1B O   OO O   STOP START UNIT                                        |P  +=============================================================================+  A     Table D.2 (continued)P  +=============================================================================+P  |           D - DIRECT ACCESS DEVICE                       Device column key  |P  |           .T - SEQUENTIAL ACCESS DEVICE                  M = Mandatory      |P  |           . L - PRINTER DEVICE                           O = Optional       |P  |           .  P - PROCESSOR DEVICE                        V = Vendor-specific|P  |           .  .W - WRITE ONCE READ MULTIPLE DEVICE        R = Reserved       |P  |           .  . R - READ ONLY (CD-ROM) DEVICE                                |P  |           .  .  S - SCANNER DEVICE                                          |P  |           .  .  .O - OPTICAL MEMORY DEVICE                                  |P  |           .  .  . M - MEDIA CHANGER DEVICE                                  |P  |           .  .  .  C - COMMUNICATION DEVICE                                 |P  |           .  .  .  .                                                        |P  |        OP DTLPWRSOMC Description                                            |P  |----------+----------+-------------------------------------------------------|P  |        1C OOOOOOOOOO RECEIVE DIAGNOSTIC RESULTS                             |P  |        1D MMMMMMMMMM SEND DIAGNOSTIC                                        |P  |        1E OO  OO OO  PREVENT ALLOW MEDIUM REMOVAL                           |P  |        1F                                                                   |P  |        20 V   VV V                                                          |P  |        21 V   VV V                                                          |P  |        22 V   VV V                                                          |P  |        23 V   VV V                                                          |P  |        24 V   VVM    SET WINDOW                                             |P  |        25       O    GET WINDOW                                             |P  |        25 M   M  M   READ CAPACITY                                          |P  |        25      M     READ CD-ROM CAPACITY                                   |P  |        26 V   VV                                                            |P  |        27 V   VV                                                            |P  |        28          O GET MESSAGE(10)                                        |P  |        28 M   MMMM   READ(10)                                               |P  |        29 V   VV O   READ GENERATION                                        |P  |        2A          O SEND MESSAGE(10)                                       |P  |        2A       O    SEND(10)                                               |P  |        2A O   M  M   WRITE(10)                                              |P  |        2B  O         LOCATE                                                 |P  |        2B         O  POSITION TO ELEMENT                                    |P  |        2B O   OO O   SEEK(10)                                               |P  |        2C V      O   ERASE(10)                                              |P  |        2D V   O  O   READ UPDATED BLOCK                                     |P  |        2E O   O  O   WRITE AND VERIFY(10)                                   |P  |        2F O   OO O   VERIFY(10)                                             |P  |        30 O   OO O   SEARCH DATA HIGH(10)                                   |P  |        31       O    OBJECT POSITION                                        |P  |        31 O   OO O   SEARCH DATA EQUAL(10)                                  |P  |        32 O   OO O   SEARCH DATA LOW(10)                                    |P  |        33 O   OO O   SET LIMITS(10)                                         |P  |        34       O    GET DATA BUFFER STATUS                                 |P  |        34 O   OO O   PRE-FETCH                                              |P  |        34  O         READ POSITION                                          |P  |        35 O   OO O   SYNCHRONIZE CACHE                                      |P  |        36 O   OO O   LOCK UNLOCK CACHE                                      |P  |        37 O      O   READ DEFECT DATA(10)                                   |P  |        38     O  O   MEDIUM SCAN                                            |P  |        39 OOOOOOOO   COMPARE                                                |P  |        3A OOOOOOOO   COPY AND VERIFY                                        |P  |        3B OOOOOOOOOO WRITE BUFFER                                           |P  |        3C OOOOOOOOOO READ BUFFER                                            |P  |        3D     O  O   UPDATE BLOCK                                           |P  |        3E O   OO O   READ LONG                                              |P  |        3F O   O  O   WRITE LONG                                             |P  +=============================================================================+  c  A  Table D.2 (continued)P  +=============================================================================+P  |           D - DIRECT ACCESS DEVICE                       Device column key  |P  |           .T - SEQUENTIAL ACCESS DEVICE                  M = Mandatory      |P  |           . L - PRINTER DEVICE                           O = Optional       |P  |           .  P - PROCESSOR DEVICE                        V = Vendor-specific|P  |           .  .W - WRITE ONCE READ MULTIPLE DEVICE        R = Reserved       |P  |           .  . R - READ ONLY (CD-ROM) DEVICE                                |P  |           .  .  S - SCANNER DEVICE                                          |P  |           .  .  .O - OPTICAL MEMORY DEVICE                                  |P  |           .  .  . M - MEDIA CHANGER DEVICE                                  |P  |           .  .  .  C - COMMUNICATION DEVICE                                 |P  |           .  .  .  .                                                        |P  |        OP DTLPWRSOMC Description                                            |P  |----------+----------+-------------------------------------------------------|P  |        40 OOOOOOOOOO CHANGE DEFINITION                                      |P  |        41 O          WRITE SAME                                             |P  |        42      O     READ SUB-CHANNEL                                       |P  |        43      O     READ TOC                                               |P  |        44      O     READ HEADER                                            |P  |        45      O     PLAY AUDIO(10)                                         |P  |        46                                                                   |P  |        47      O     PLAY AUDIO MSF                                         |P  |        48      O     PLAY AUDIO TRACK INDEX                                 |P  |        49      O     PLAY TRACK RELATIVE(10)                                |P  |        4A                                                                   |P  |        4B      O     PAUSE RESUME                                           |P  |        4C OOOOOOOOOO LOG SELECT                                             |P  |        4D OOOOOOOOOO LOG SENSE                                              |P  |        4E                                                                   |P  |        4F                                                                   |P  |        50                                                                   |P  |        51                                                                   |P  |        52                                                                   |P  |        53                                                                   |P  |        54                                                                   |P  |        55 OOO OOOOOO MODE SELECT(10)                                        |P  |        56                                                                   |P  |        57                                                                   |P  |        58                                                                   |P  |        59                                                                   |P  |        5A OOO OOOOOO MODE SENSE(10)                                         |P  |        5B                                                                   |P  |        5C                                                                   |P  |        5D                                                                   |P  |        5E                                                                   |P  |        5F                                                                   |P  +=============================================================================+     |  Table D.2 (concluded)P  +=============================================================================+P  |           D - DIRECT ACCESS DEVICE                       Device column key  |P  |           .T - SEQUENTIAL ACCESS DEVICE                  M = Mandatory      |P  |           . L - PRINTER DEVICE                           O = Optional       |P  |           .  P - PROCESSOR DEVICE                        V = Vendor-specific|P  |           .  .W - WRITE ONCE READ MULTIPLE DEVICE        R = Reserved       |P  |           .  . R - READ ONLY (CD-ROM) DEVICE                                |P  |           .  .  S - SCANNER DEVICE                                          |P  |           .  .  .O - OPTICAL MEMORY DEVICE                                  |P  |           .  .  . M - MEDIA CHANGER DEVICE                                  |P  |           .  .  .  C - COMMUNICATION DEVICE                                 |P  |           .  .  .  .                                                        |P  |        OP DTLPWRSOMC Description                                            |P  |----------+----------+-------------------------------------------------------|P  |        A0                                                                   |P  |        A1                                                                   |P  |        A2                                                                   |P  |        A3                                                                   |P  |        A4                                                                   |P  |        A5         M  MOVE MEDIUM                                            |P  |        A5      O     PLAY AUDIO(12)                                         |P  |        A6         O  EXCHANGE MEDIUM                                        |P  |        A7                                                                   |P  |        A8          O GET MESSAGE(12)                                        |P  |        A8     OO O   READ(12)                                               |P  |        A9      O     PLAY TRACK RELATIVE(12)                                |P  |        AA          O SEND MESSAGE(12)                                       |P  |        AA     O  O   WRITE(12)                                              |P  |        AB                                                                   |P  |        AC        O   ERASE(12)                                              |P  |        AD                                                                   |P  |        AE     O  O   WRITE AND VERIFY(12)                                   |P  |        AF     OO O   VERIFY(12)                                             |P  |        B0     OO O   SEARCH DATA HIGH(12)                                   |P  |        B1     OO O   SEARCH DATA EQUAL(12)                                  |P  |        B2     OO O   SEARCH DATA LOW(12)                                    |P  |        B3     OO O   SET LIMITS(12)                                         |P  |        B4                                                                   |P  |        B5                                                                   |P  |        B5         O  REQUEST VOLUME ELEMENT ADDRESS                         |P  |        B6                                                                   |P  |        B6         O  SEND VOLUME TAG                                        |P  |        B7        O   READ DEFECT DATA(12)                                   |P  |        B8                                                                   |P  |        B8         O  READ ELEMENT STATUS                                    |P  |        B9                                                                   |P  |        BA                                                                   |P  |        BB                                                                   |P  |        BC                                                                   |P  |        BD                                                                   |P  |        BE                                                                   |P  |        BF                                                                   |P  +=============================================================================+     |I                                                                                                               U  Annex E  (informative)     Vendor identification      C  This annex contains the list of SCSI-2 vendor identifications (see|F  table E.1) as of the date of this document.  The purpose of this listH  is to help avoid redundant usage of vendor identifications.  Task GroupG  X3T9.2 of Accredited Standards Committee X3 maintains an informal list @  of vendor identifications currently in use.  Please contact theG  chairman of X3T9.2 prior to using a new vendor identification to avoidH  conflicts.    ;                      Table E.1 - Vendor identification list S  +==========-=====================================================================+AS  |     ID   |                          Organization                               | S  |----------+---------------------------------------------------------------------| S  | 3M       |  3M Company                                                         | S  | ACL      |  Automated Cartridge Librarys, Inc.                                 | S  | ADAPTEC  |  Adaptec                                                            | S  | ADSI     |  Adaptive Data Systems, Inc. (a Western Digital subsidiary)         | S  | AMCODYNE |  Amcodyne                                                           | S  | ANAMATIC |  Anamartic Limited (England)                                        | S  | ANCOT    |  ANCOT Corp.                                                        | S  | ANRITSU  |  Anritsu Corporation                                                | S  | APPLE    |  Apple Computer, Inc.                                               | S  | ARCHIVE  |  Archive                                                            ||S  | ASACA    |  ASACA Corporation                                                  |+S  | ASPEN    |  Aspen Peripherals                                                  |AS  | AST      |  AST Research                                                       |=S  | ASTK     |  Alcatel STK A/S                                                    |iS  | AT&T     |  AT&T                                                               |dS  | ATARI    |  Atari Corporation                                                  |lS  | ATTO     |  ATTO Technology Inc.                                               |iS  | ATX      |  Alphatronix                                                        ||S  | AVR      |  Advanced Vision Research                                           ||S  | BALLARD  |  Ballard Synergy Corp.                                              | S  | BERGSWD  |  Berg Software Design                                               | S  | BEZIER   |  Bezier Systems, Inc.                                               |.S  | BULL     |  Bull Peripherals Corp.                                             | S  | CalComp  |  CalComp, A Lockheed Company                                        |MS  | CALIPER  |  Caliper (California Peripheral Corp.)                              |-S  | CAST     |  Advanced Storage Tech                                              |ES  | CDC      |  Control Data or MPI                                                |ES  | CDP      |  Columbia Data Products                                             |NS  | CHEROKEE |  Cherokee Data Systems                                              | S  | CHINON   |  Chinon                                                             | S  | CIE&YED  |  YE Data, C.Itoh Electric Corp.                                     | S  | CIPHER   |  Cipher Data Products                                               | S  +================================================================================+         Table E.1 - (continued)S  +==========-=====================================================================+ S  |   ID     |                          Organization                               | S  |----------+---------------------------------------------------------------------| S  | Ciprico  |  Ciprico, Inc.                                                      |OS  | CMD      |  CMD Technology                                                     |ES  | CNGR SFW |  Congruent Software, Inc.                                           | S  | COGITO   |  Cogito                                                             | S  | COMPORT  |  Comport Corp.                                                      | S  | COMPSIG  |  Computer Signal Corporation                                        | S  | CONNER   |  Conner Peripherals                                                 | S  | CPU TECH |  CPU Technology, Inc                                                | S  | CREO     |  CREO Products Inc.                                                 | S  | CROSFLD  |  Crosfield Electronics                                              | S  | CSM, INC |  Computer SM, Inc.                                                  | S  | CYGNET   |  Cygnet Systems, Inc.                                               | S  | DATABOOK |  Databook, Inc.                                                     | S  | DATACOPY |  Datacopy Corp.                                                     | S  | DATAPT   |  Datapoint Corp.                                                    | S  | DEC      |  Digital Equipment                                                  | S  | DELPHI   |  Delphi Data Div. of Sparks Industries, Inc.                        | S  | DENON    |  Denon/Nippon Columbia                                              |ES  | DEST     |  DEST Corp.                                                         | S  | DGC      |  Data General Corp.                                                 |=S  | DIGIDATA |  Digi-Data Corporation                                              |cS  | DILOG    |  Distributed Logic Corp.                                            |=S  | DISC     |  Document Imaging Systems Corp.                                     | S  | DPT      |  Distributed Processing Technology                                  | S  | DSM      |  Deterner Steuerungs- und Maschinenbau GmbH & Co.                   | S  | DTC QUME |  Data Technology Qume                                               | S  | DXIMAGIN |  DX Imaging                                                         | S  | EMULEX   |  Emulex                                                             |SS  | EPSON    |  Epson                                                              | S  | EXABYTE  |  Exabyte Corp.                                                      |DS  | FILENET  |  FileNet Corp.                                                      |NS  | FUJI     |  Fuji Electric Co., Ltd. (Japan)                                    | S  | FUJITSU  |  Fujitsu                                                            | S  | FUTURED  |  Future Domain Corp.                                                |-S  | Gen_Dyn  |  General Dynamics                                                   | S  | GIGATAPE |  GIGATAPE GmbH                                                      | S  | GIGATRND |  GigaTrend Incorporated                                             | S  | Goidelic |  Goidelic Precision, Inc.                                           | S  | GOULD    |  Gould                                                              | S  | HITACHI  |  Hitachi America Ltd or Nissei Sangyo America Ltd                   | S  | HONEYWEL |  Honeywell Inc.                                                     | S  | HP       |  Hewlett Packard                                                    | S  | IBM      |  International Business Machines                                    ||S  | ICL      |  ICL                                                                ||S  | IDE      |  International Data Engineering, Inc.                               | S  | IGR      |  Intergraph Corp.                                                   | S  | IMPLTD   |  Integrated Micro Products Ltd.                                     | S  | IMPRIMIS |  Imprimis Technology Inc.                                           | S  | INSITE   |  Insite Peripherals                                                 | S  | IOC      |  I/O Concepts, Inc.                                                 | S  | IOMEGA   |  Iomega                                                             | S  +================================================================================+)           Table E.1 - (continued)S  +==========-=====================================================================+ S  |   ID     |                          Organization                               ||S  |----------+---------------------------------------------------------------------||S  | ISi      |  Information Storage inc.                                           | S  | ITC      |  International Tapetronics Corporation                              | S  | JVC      |  JVC Information Products Co.                                       | S  | KENNEDY  |  Kennedy Company                                                    | S  | KODAK    |  Eastman Kodak                                                      |OS  | KONAN    |  Konan                                                              |ES  | KONICA   |  Konica Japan                                                       | S  | LAPINE   |  Lapine Technology                                                  |ES  | LASERDRV |  LaserDrive Limited                                                 | S  | LASERGR  |  Lasergraphics, Inc.                                                | S  | LMS      |  Laser Magnetic Storage International Company                       | S  | MATSHITA |  Matsushita                                                         | S  | MAXTOR   |  Maxtor Corp.                                                       | S  | MaxOptix |  Maxoptix Corp.                                                     | S  | MDI      |  Micro Design International, Inc.                                   | S  | MELA     |  Mitsubishi Electronics America                                     |=S  | MELCO    |  Mitsubishi Electric (Japan)                                        | S  | MEMREL   |  Memrel Corporation                                                 |nS  | MEMTECH  |  MemTech Technology                                                 |tS  | MICROBTX |  Microbotics Inc.                                                   |iS  | MICROP   |  Micropolis                                                         |cS  | MICROTEK |  Microtek Storage Corp                                              |sS  | MINSCRIB |  Miniscribe                                                         |oS  | MITSUMI  |  MITSUMI Electric Co., Ltd.                                         | S  | MOTOROLA |  Motorola                                                           |=S  | MST      |  Morning Star Technologies, Inc.                                    | S  | NAI      |  North Atlantic Industries                                          |-S  | NatInst  |  National Instruments                                               | S  | NatSemi  |  National Semiconductor Corp.                                       | S  | NCL      |  NCL America                                                        | S  | NCR      |  NCR Corporation                                                    |uS  | NEC      |  NEC                                                                | S  | NISCA    |  NISCA Inc.                                                         | S  | NKK      |  NKK Corp.                                                          | S  | NT       |  Northern Telecom                                                   | S  | OCE      |  Oce Graphics                                                       | S  | OMI      |  Optical Media International                                        | S  | OMNIS    |  OMNIS Company (FRANCE)                                             | S  | OPTIMEM  |  Cipher/Optimem                                                     | S  | OPTOTECH |  Optotech                                                           | S  | ORCA     |  Orca Technology                                                    | S  | OSI      |  Optical Storage International                                      | S  | OTL      |  OTL Engineering                                                    | S  | PASCOsci |  Pasco Scientific                                                   | S  | PERTEC   |  Pertec Peripherals Corporation                                     | S  | PFTI     |  Performance Technology Inc.                                        | S  | PIONEER  |  Pioneer Electronic Corp.                                           | S  | PRAIRIE  |  PrairieTek                                                         | S  | PRESOFT  |  PreSoft Architects                                                 | S  | PRESTON  |  Preston Scientific                                                 | S  | PRIAM    |  Priam                                                              | S  | PRIMAGFX |  Primagraphics Ltd                                                  | S  +================================================================================+         Table E.1 - (concluded)S  +==========-=====================================================================+ S  |   ID     |                          Organization                               | S  |----------+---------------------------------------------------------------------| S  | PTI      |  Peripheral Technology Inc.                                         | S  | QUALSTAR |  Qualstar                                                           | S  | QUANTEL  |  Quantel Ltd.                                                       |=S  | QUANTUM  |  Quantum Corp.                                                      |bS  | R-BYTE   |  R-Byte Inc.                                                        |=S  | RACALREC |  Racal Recorders                                                    | S  | RADSTONE |  Radstone Technology                                                |-S  | RGI      |  Raster Graphics, Inc.                                              | S  | RICOH    |  Ricoh                                                              | S  | RODIME   |  Rodime                                                             | S  | RTI      |  Reference Technology                                               | S  | SANKYO   |  Sankyo Seiki                                                       | S  | SANYO    |  SANYO Electric Co., Ltd.                                           | S  | SCREEN   |  Dainippon Screen Mfg. Co., Ltd.                                    | S  | SEAGATE  |  Seagate                                                            | S  | SEQUOIA  |  Sequoia Advanced Technologies, Inc.                                | S  | Shinko   |  Shinko Electric Co., Ltd.                                          | S  | SIEMENS  |  Siemens                                                            | S  | SII      |  Seiko Instruments Inc.                                             | S  | SMS      |  Scientific Micro Systems/OMTI                                      | S  | SNYSIDE  |  Sunnyside Computing Inc.                                           | S  | SONIC    |  Sonic Solutions                                                    | S  | SONY     |  Sony Corporation Japan                                             | S  | SPECTRA  |  Spectra Logic, a Division of Western Automation Labs, Inc.         | S  | SPERRY   |  Sperry (now Unisys Corp.)                                          | S  | STK      |  Storage Technology Corporation                                     | S  | SUMITOMO |  Sumitomo Electric Industries, Ltd.                                 | S  | SUN      |  Sun Microsystems, Inc.                                             | S  | SyQuest  |  SyQuest Technology, Inc.                                           | S  | SYSGEN   |  Sysgen                                                             | S  | T-MITTON |  Transmitton England                                                | S  | TALARIS  |  Talaris Systems, Inc.                                              | S  | TALLGRAS |  Tallgrass Technologies                                             | S  | TANDBERG |  Tandberg Data A/S                                                  | S  | TANDON   |  Tandon                                                             | S  | TEAC     |  TEAC Japan                                                         | S  | TECOLOTE |  Techolote Designs                                                  | S  | TEGRA    |  Tegra Varityper                                                    | S  | Tek      |  Tektronix                                                          | S  | TI-DSG   |  Texas Instruments                                                  | S  | TOSHIBA  |  Toshiba Japan                                                      | S  | ULTRA    |  UltraStor Corporation                                              | S  | UNISYS   |  Unisys                                                             | S  | USDC     |  US Design Corp.                                                    | S  | VERBATIM |  Verbatim Corporation                                               | S  | VRC      |  Vermont Research Corp.                                             | S  | WangDAT  |  WangDAT                                                            | S  | WANGTEK  |  Wangtek                                                            | S  | WDIGTL   |  Western Digital                                                    | S  | WEARNES  |  Wearnes Technology Corporation                                     | S  | XEBEC    |  Xebec Corporation                                                  | S  +================================================================================+                  Index   P  3rdPty bit. . . . . . . . . . . . . . . . . . . . . 188, 191, 253, 254, 398-401P  ABORT . . . . 3, 36, 38, 41, 43, 44, 49, 52, 55-59, 64, 76, 79, 80, 82, 85, 422P  ABORT TAG . . . . . . . . . . . . . . . . 3, 41, 52, 55, 56, 58, 64, 76, 79, 85P  absolute CD-ROM address field . . . . . . . . . . . . . . . . . . . . .319, 324P  access bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394-396P  active format field . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267P  active I/O process. . . . . . . . . . . . . . . . . . . . . . . . . . 3, 51, 54P  active notch field. . . . . . . . . . . . . . . . . . . . . . . . 210, 218, 221P  active partition field. . . . . . . . . . . . . . . . . . . . . . . . .266, 267P  actual retry count field. . . . . . . . . . . . . . . . . . . . . . . . . . 126P  additional length field . . . . . . . . . . . . . . . . . . . . . . . . . . 107P  additional partitions defined field . . . . . . . . . . . . . . . . . . . . 269P  additional sense code field . . . . . . . . . . . . . . . . . . . 123, 124, 392P  additional sense code qualifier . . . . . . . . . . . . .123, 124, 302, 392-395P  ADDRESS MARK NOT FOUND FOR DATA FIELD . . . . . . . . . . . . . . . . .130, 430P  ADDRESS MARK NOT FOUND FOR ID FIELD . . . . . . . . . . . . . . . . . .130, 430P  address to translate field. . . . . . . . . . . . . . . . . . . . . . . 206-208P  ADR field . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302, 318, 324P  advanced scan algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . 362P  AEN . . . . . . . . . . . . . . .xxv, 5, 81-83, 89, 95, 126, 127, 150, 151, 290P  AENC bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82, 107P  AFC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .282, 283Q  Allocation Length . . 67, 72, 73, 75, 95, 104, 107, 111, 112, 115, 117-119, 121, R                        122, 124, 155-159, 183, 185, 289, 314, 316, 323, 341, 343, B                        364, 366, 388, 389, 391, 396, 397, 414, 415P  allocation length field . . . . . . . . . . . . . . . . . . . . . . . . 75, 111P  alternate sector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207P  alternate sectors per zone field. . . . . . . . . . . . . . . . . . . . . . 218P  alternate track . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208P  alternate tracks per logical unit field . . . . . . . . . . . . . . . . . . 218P  alternate tracks per zone . . . . . . . . . . . . . . . . . . . . . . . 216-218P  alternate volume tag. . . . . . . . . . . . . . . . . . . . . 382, 391-395, 402P  alternate volume tag information field. . . . . . . . . . . . . . . . . . . 391P  ALTSEC bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207P  ALTTRK bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208P  ANSI-approved version field . . . . . . . . . . . . . . . . . . . . . . . . 106P  APRVal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .327, 328P  Arbitration Delay . . . . . . . . . . . . . . . . . . . . .3, xxxi, 36, 42, 421P  ARBITRATION Phase . . . . . . . . . . . . . .33, 34, 36, 37, 41-43, 59, 86, 421P  ARRE bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223P  ASA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362P  ASC . . . . . . . . . . . . . . 1, xxii, xxvii, 106, 124, 130-133, 135, 429-434P  ASCII forms control . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283P  ASCII Implemented Operating Definition Page . . . . . . . . . . . . . . . . 155P  ASCII information field . . . . . . . . . . . . . . . . . . . . . . . . . . 156P  ASCII operating definition description data field . . . . . . . . . . . . . 155P  ASCQ. . . . . . . . . . . . . . . . . . xxii, xxvii, 124, 130-133, 135, 429-434P  Assertion Period. . . . . . . . . . . . . . . . . . . . . . 36, 38, 45, 46, 425P  asynchronous event notification . . xxxi, 5, 27, 56, 61, 81-83, 107, 126, 145, <                                      149, 151, 238, 241, 290P  attention condition . . . . . . . . 33, 48-51, 56, 59, 63, 79, 81, 82, 85, 88, O                                      89, 94, 95, 104, 110, 112, 128, 138, 142,  F                                      148, 150, 151, 188, 230, 253, 264P  AUDIO PLAY OPERATION IN PROGRESS. . . . . . . . . . . . . . . . . 130, 318, 429P  AUDIO PLAY OPERATION PAUSED . . . . . . . . . . . . . . . . . . . 130, 318, 429P  AUDIO PLAY OPERATION STOPPED DUE TO ERROR . . . . . . . . . . . . 130, 318, 429P  AUDIO PLAY OPERATION SUCCESSFULLY COMPLETED . . . . . . . . . . . 130, 318, 429P  audio playback rate valid . . . . . . . . . . . . . . . . . . . . . . . . . 328P  audio status field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317P  auto bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .339, 345P  autofd. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280, 282P  automatic line feed . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282P  automatic read reallocation . . . . . . . . . . . . . . . . . . . . . . . . 223P  automatic velocity control. . . . . . . . . . . . . . . . . . . . . . . . . 267P  automatic write reallocation. . . . . . . . . . . . . . . . . . . . . . . . 222P  available data buffer field . . . . . . . . . . . . . . . . . . . . . . . . 342P  AVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .266, 267P  AVolTag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391-393P  AWG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5, 9, 425P  AWRE bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203, 223, 231P  basic measurement unit field. . . . . . . . . . . . . . . . . . . . . . . . 354P  baud rate field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286P  beginning of partition. . . . . . . . . . . . . . . . . . . . . . . . . . . 250P  BEGINNING-OF-PARTITION/MEDIUM DETECTED. . . . . . . . . . . . . . . . .130, 429P  BIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . .249, 266, 267, 363P  bit ordering field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346P  bit pointer field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125P  bit pointer valid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125P  bits per character field. . . . . . . . . . . . . . . . . . . . . . . . . . 286P  bits per pixel field. . . . . . . . . . . . . . . . . . . . . . . . . . . . 346P  BLANK CHECK . . . . .102, 129, 247, 257, 294, 304, 307, 326, 358, 367, 370, 376P  blank verify. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .299, 370P  BlkVfy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299, 370, 371P  block address type. . . . . . . . . . . . . . . . . . . . . . . . . . .245, 249M  block descriptor. .  xxii, 113, 115, 116, 124, 146-148, 161, 208, 209, 246,  M                       259, 263, 264, 279, 280, 298, 325, 326, 337, 349, 351,  -                       353, 375, 376, 404, 418nP  block descriptor length . . . . . . . . . . . . . . . . . . . . . . . . . . 147P  block device logical block address field. . . . . . . . . . . . . . . . . . .99P  block device number of blocks field . . . . . . . . . . . . . . . . . . . . .99P  block identifiers supported . . . . . . . . . . . . . . . . . . . . . . . . 267P  block length field. . . . . . . . . . . . . . . . . . . . . .101, 124, 148, 246P  block length in bytes . . . . . . . . . . . . . . . . . . . .182, 183, 246, 259P  block position unknown. . . . . . . . . . . . . . . . . . . . . . . . . . . 250P  BLOCK SEQUENCE ERROR. . . . . . . . . . . . . . . . . . . . . . . . . .130, 430P  BOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236-240, 249, 250P  BPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .249, 250P  BPV bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125P  brightness field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345P  BT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245, 249P  buffer capacity field . . . . . . . . . . . . . . . . . . . . . . 119, 120, 137P  buffer empty ratio field. . . . . . . . . . . . . . . . . . . . . . . . . . 152P  buffer full ratio field . . . . . . . . . . . . . . . . . . . . . . . . . . 152P  buffer ID field . . . . . . . . . . . . . . . . . . . . . . . . . . . .119, 137P  buffer offset field . . . . . . . . . . . . . . . . . . . . . . . . . .119, 120P  Buffer Over-Run/Under-Run Page. . . 143, 208, 262, 279, 291, 325, 352, 375, 418P  buffered mode field . . . . . . . . . . . . . . . . . . . . . . . 259, 263, 280P  Bus Clear Delay . . . . . . . . . . . . . . . . . . . . 36, 41-43, 51, 421, 423O  BUS DEVICE RESET. . . . . . .3, 41, 49, 50, 55, 57-59, 65, 67-69, 76, 79, 82, DL                               83, 85, 88, 112, 116, 132, 179, 189-191, 254, *                               399-401, 431P  Bus Free Delay. . . . . . . . . . . . . . . . . . . . . . . . . 36, 37, 42, 421N  BUS FREE Phase. . 3, 4, 36, 37, 41-44, 49-52, 57-60, 64, 66, 68, 69, 77, 84,                     86, 421, 423 P  Bus Set Delay . . . . . . . . . . . . . . . . . . . . . . . . . 36, 37, 42, 421P  Bus Settle Delay. . . . . . . . . . . . . . . . . . .36, 37, 41-44, 49, 421-423P  BUSY status . . . . . . . . . . . . . . . . . . . . . 82-85, 127, 287, 339, 411P  BytChk bit. . . . . . . . . . . . . . . . . . . . . . . 103, 200, 203, 370, 374P  byte check. . . . . . . . . . . . . . . . . . . . . . . 103, 200, 203, 370, 374P  byte count of descriptor data available field . . . . . . . . . . . . . . . 391P  byte count of report available field. . . . . . . . . . . . . . . . . . . . 389P  byte transfer length field. . . . . . . . . . . . . . . . . . . . . . .185, 204P  C/D bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125P  Cable Skew Delay. . . . . . . . . . . . . . . . . . . . 36-38, 45, 46, 422, 425P  Caching Page  . . . . . . . . . . . . . . . . . . . . . . . . . . 210, 327, 377P  CAF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .266, 267P  CANNOT READ MEDIUM - INCOMPATIBLE FORMAT. . . . . . . . . . . . . . . .130, 431P  CANNOT READ MEDIUM - UNKNOWN FORMAT . . . . . . . . . . . . . . . . . .130, 431P  CAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266P  CARTRIDGE FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . .130, 432P  cat bit . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxi, 96, 99, 102P  catenate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99P  cause field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii, 144P  CD-ROM Audio Control Page . . . . . . . . . . . . . . . . . . . . . . . . . 327P  CD-ROM devices. xxx, 124, 297, 299, 304, 305, 313, 325, 326, 328, 330, 336, 357P  CD-ROM Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327P  change active format. . . . . . . . . . . . . . . . . . . . . . . . . . . . 267P  change active partition . . . . . . . . . . . . . . . . . . . . . . . . . . 266P  CHANGE DEFINITION command . . . . . . . . . . . . xxi, 79, 93-95, 104, 156, 164P  change partition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245P  CHANGED OPERATING DEFINITION. . . . . . . . . . . . . . . . . . . .79, 130, 432P  channel bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .277, 283P  channel volume control. . . . . . . . . . . . . . . . . . . . . . . . . . . 329N  CHECK CONDITION status. . . . . 3, 47, 49, 52, 60, 71, 75, 80-82, 88, 92, 95,O                                  98, 99, 101, 102, 104, 108-113, 115-117, 119,  M                                  122, 125-127, 134, 135, 137, 139, 140, 142, 2I                                  143, 145, 149, 153, 162, 166, 169, 170, 5L                                  172-174, 176, 182-185, 187, 188, 190, 191, P                                  193, 194, 197, 199, 200, 203-206, 218, 223-226,P                                  228, 230, 233, 240, 243-247, 251-253, 255-262, Q                                  267, 271, 276-278, 287, 293, 302-304, 306, 307, 3Q                                  309, 310, 312, 323, 331-335, 339, 347-349, 354, aN                                  358, 363, 367, 370, 371, 374, 376, 378, 384, A                                  385, 386, 398-401, 407, 408, 411.P  CIRC UNRECOVERED ERROR. . . . . . . . . . . . . . . . . . . . . . . . .130, 430P  CLEANING CARTRIDGE INSTALLED. . . . . . . . . . . . . . . . . . . . . .130, 431P  CLEAR QUEUE . . . . . . . . . . . . . . . . . 3, 41, 55, 56, 58, 59, 76, 79, 85P  clear to send . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286P  CmpLst bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . 170, 171, 173P  code field. . . xxii, xxiv, 73, 97, 104, 112, 116, 121, 123-125, 139-141, 143, M                  144, 148, 149, 156, 158, 208, 209, 256, 263, 264, 279, 280, .M                  298, 325, 326, 353, 375, 376, 388, 391, 392, 397, 398, 401, .                  402, 404, 418P  command code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73, 74P  COMMAND COMPLETE. . . . . . .3, 41, 52, 55, 59, 62, 75, 77, 78, 83, 86, 94, 423P  command data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125, 317O  command descriptor block. . . xxi, 3, 50, 54, 67, 72-77, 80, 86, 99-102, 107, .P                                118, 122, 124, 125, 128, 137, 140, 141, 146-148, P                                156-158, 173, 178, 182, 188, 195, 198, 199, 219, I                                243-245, 255, 258, 261, 272, 313, 362, 389fP  COMMAND Phase . . . . . . . 41, 48, 50, 61, 75, 77, 83, 127, 130, 422, 423, 432P  COMMAND PHASE ERROR . . . . . . . . . . . . . . . . . . . . . . . . . .130, 432P  command queue . . . . . . . . . . . . . . . . . . . . . 3, 4, 64, 67, 77, 83-86P  COMMAND SEQUENCE ERROR. . . . . . . . . . . . . . . . . . . . . . . . .130, 431P  COMMAND TERMINATED status . . . . . . . . . . 61, 67, 76, 82, 83, 122, 126, 128P  command-specific information field. . . . . . . . . . . . . . 98, 124, 187, 194P  COMMANDS CLEARED BY ANOTHER INITIATOR . . . . . . . . . . 59, 85, 130, 150, 431P  communications devices. . . . . . .2, xxvii, xxix, xxx, xxxi, 411-413, 418, 419P  COMPARE command . . . . . . . . . . . . . . . . . . . . . . . . . . xxi, 95, 97P  complete list . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171, 184P  CONDITION MET status. . . . . . . . . . . . . . . . . . . 75, 77, 178, 193, 363P  connect time limit field. . . . . . . . . . . . . . . . . . . . . . . . .3, 153P  connection. . . . . 3, 4, 6, 9, 27, 36, 41, 57-60, 63, 64, 79, 80, 85, 153, 297N  contingent allegiance . .xxxi, 3, 58, 59, 61, 62, 64, 67, 76, 77, 79-85, 88, 3                           92, 95, 122, 149-151, 238pP  contrast field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345O  control . . . . . .xxi, xxii, xxiv, xxv, xxxii, 3, 6, 33, 37, 42, 44, 45, 67, iN                     72, 73, 75, 77, 81, 84-86, 93, 95, 96, 103, 104, 109-112, M                     114, 115, 117, 118, 121, 122, 134-136, 138, 141-143, 145,tM                     149, 153, 162-164, 169, 170, 173, 177-183, 185-187, 189, aN                     192, 193, 196-205, 210, 213, 223, 230, 243-246, 248, 249, N                     251-256, 258, 259, 261, 265, 267, 273, 275-278, 280, 281, Q                     282, 283, 287-290, 292, 293, 300-302, 306-314, 316-318, 320,  K                     321, 323, 324, 327, 329, 337, 338, 341, 343, 345, 347, 3L                     349-351, 353, 360-362, 364-374, 377, 378, 380, 384-388, >                     396, 398, 399, 401, 411, 414-417, 419, 439P  Control Field . . . . . . . . . . . . xxi, 75, 109-111, 115, 302, 324, 337, 338M  Control Mode Page . . . xxii, 67, 81, 84, 85, 142, 143, 145, 149, 210, 265, .0                          280, 327, 353, 377, 419P  COPY ABORTED. . . . . . . . . . . . . . . . . . . . . . . . . .98, 99, 101, 129P  COPY AND VERIFY command . . . . . . . . . . . . . . . . xxi, 103, 123, 124, 231P  COPY CANNOT EXECUTE SINCE HOST CANNOT DISCONNECT. . . . . . . . . . . .130, 431P  COPY command. . . . . . . xxi, xxxii, 5, 27, 95-99, 102-104, 188, 191, 254, 287P  COPY function code field. . . . . . . . . . . . . . . . . . . . . . . . . . .97P  CORRCT bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185P  correct . . . . . . . 4, 43, 78, 83, 86, 125, 128, 130, 167, 244, 335, 429, 430P  count basis field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144P  count field . . . . . . . . . . . . . 102, 126, 224-228, 231, 256-258, 335, 348P  CP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245P  CTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .285, 286P  current I/O process . . . . . . . . . . . . . . . 3, 41, 58, 59, 65, 67, 77, 84P  current operating definition field. . . . . . . . . . . . . . . . . . . . . 157P  cylinder skew factor field. . . . . . . . . . . . . . . . . . . . . . . . . 218P  data buffer recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . 267P  data buffer status descriptor . . . . . . . . . . . . . . . . . . . . . . . 341P  data bytes per physical sector field. . . . . . . . . . . . . . . . . . . . 218P  data bytes per sector field . . . . . . . . . . . . . . . . . . . . . . . . 214P  data defect list. . . . . . . . . . . . . . . . . . . . . .xxiii, 170, 184, 365Q  DATA IN Phase . . .48, 61, 75, 77, 118, 119, 182, 277, 292, 313, 324, 342, 349, .!                     367, 422, 423iJ  DATA OUT Phase. . .48, 72, 74, 81, 96, 109, 110, 113, 125, 137, 170-172, C                     275-277, 290, 292, 350, 351, 362, 369, 416, 4239P  DATA PATH FAILURE (SHOULD USE 40 NN). . . . . . . . . . . . . . . . . .130, 432P  DATA PHASE ERROR. . . . . . . . . . . . . . . . . . . . . . . . . . . .130, 432P  DATA PROTECT. . . . . . . . . . . . . . . . . 128, 166, 191, 197, 240, 294, 358P  Data Release Delay. . . . . . . . . . . . . . . . . . . . . . . . . .36, 37, 49P  DATA SYNCHRONIZATION MARK ERROR . . . . . . . . . . . . . . . . . . . .130, 430P  data transfer disconnect control. . . . . . . . . . . . . . . . . . . xxii, 153P  data transfer element . . . xxvii, 379-381, 384, 386, 388, 395, 396, 405, 406, %                              408, 410.P  data type qualifier field . . . . . . . . . . . . . . . . . . . . . . . . . 349P  DBD bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115P  DBR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .266, 267P  DC bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100, 101P  DCR bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224, 271P  DCRT bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173P  default operating definition field. . . . . . . . . . . . . . . . . . . . . 157P  defect descriptor . . . . . . . . . . . . . . . . xxii, xxiii, 170-175, 184-187P  DEFECT LIST ERROR . . . . . . . . . . . . . . . . . . . . . . . . 130, 173, 431P  DEFECT LIST ERROR IN GROWN LIST . . . . . . . . . . . . . . . . . . . .130, 431P  DEFECT LIST ERROR IN PRIMARY LIST . . . . . . . . . . . . . . . . . . .130, 431P  defect list format field. . . . . . . . . . . . . . . . . . . . . . . .172, 184P  defect list length field. . . . . . . . . . . . . . . . . . . . . 173, 184, 187P  DEFECT LIST NOT AVAILABLE . . . . . . . . . . . . . . . . . . . . . . .130, 431P  DEFECT LIST NOT FOUND . . . . . . . . . . . . . . . 130-132, 173, 183, 184, 431P  DEFECT LIST UPDATE FAILURE. . . . . . . . . . . . . . . . . . . . . . .130, 431P  defect logical block address. . . . . . . . . . . . . . . . . . . . . .186, 187P  definition parameter field. . . . . . . . . . . . . . . . . . . . . xxi, 93, 94P  demand read retention priority field. . . . . . . . . . . . . . . . . . . . 211P  Deskew Delay. . . . . . . . . . . . . . . . . .36, 37, 39, 45, 46, 49, 422, 425P  destination count . . . . . . . . . . . . . . . . . . . . . . . . . . .100, 101P  destination logical block address field . . . . . . . . . . . . . . . . . . 100P  device off-line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134P  device-specific parameter . . . . . . . xxiv, xxv, 146, 147, 263, 272, 279, 326P  DevOfl bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135P  DIAGNOSTIC FAILURE ON COMPONENT NN (80H-FFH). . . . . . . . . . . . . .130, 432M  Diagnostic Parameters . 7, 74, 134, 138, 139, 206, 262, 279, 291, 325, 352, .&                          375, 404, 418N  direct-access devices . xxii, xxx, xxxi, 6, 97, 124, 144, 148, 161-163, 165, M                          168, 206, 208-210, 220, 229, 232, 233, 297, 357, 358 P  disable block descriptors . . . . . . . . . . . . . . . . . . . . . . . . . 115P  disable certification . . . . . . . . . . . . . . . . . . . . . . . . . . . 173P  disable correction. . . . . . . . . . . . . . . . . . . . . . . . . . .224, 271P  disable page out. . . . . . . . . . . . . . . . . . . . . . . . . . . .163, 181P  disable pre-fetch transfer length field . . . . . . . . . . . . . . . . . . 212P  disable primary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173P  disable queuing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150P  disable save. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141P  disable saving parameters . . . . . . . . . . . . . . . . . . . . . . . . . 173P  disable transfer on error . . . . . . . . . . . . . . . . . . . . . . .223, 271P  disable update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141M  DISCONNECT. . . . . .3, xxii, 3, 5, 37, 41, 47, 49, 50, 52, 55, 57, 59, 60, 9L                       62, 76-79, 84, 86, 122, 126, 130, 149, 152, 153, 210, P                       265, 280, 287, 288, 327, 353, 377, 411, 412, 419, 421, 431P  disconnect time limit field . . . . . . . . . . . . . . . . . . . . . . .3, 153N  Disconnect-Reconnect Page . .3, xxii, 60, 149, 152, 210, 265, 280, 327, 353, &                               377, 419P  Disconnection Delay . . . . . . . . . . . . . . . . . . . . . . . . .36, 37, 59P  displacement field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195P  download microcode. . . . . . . . . . . . . . . . . . . . . . . . . . .137, 138P  DPO bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163, 181P  DPOFUA bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . 209, 326, 376P  DPRY bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173P  DQue bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85, 150P  drive step pulse width field. . . . . . . . . . . . . . . . . . . . . . . . 214P  drive step rate field . . . . . . . . . . . . . . . . . . . . . . . 3, 214, 230P  DS bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109, 111, 141P  DSP bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173P  dt. . . . . . . . . . . . . . . . . . . . . . . . . .130-133, 405, 429-431, 433P  DTE bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224, 271P  DU bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141, 142P  EAENP bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151P  EBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326, 370, 376P  EBP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372-374P  EECA bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151P  EEG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .266, 268P  EER bit . . . . . . . . . . . . . . . . . . . . . . . . . . .223, 224, 232, 271P  electronic vertical forms unit. . . . . . . . . . . . . . . .133, 282, 283, 432P  Element Address Assignment Page . . . . . . . . . . . . . . . . . . .xxvii, 406P  element address field . . . . . . . . . . . . .380, 392-394, 397, 402, 407, 408P  element bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398-401P  element descriptor length field . . . . . . . . . . . . . . . . . . . . . . 391P  element descriptors . . . . . . . . . . . . . . . . . . 388, 389, 391, 397, 400P  element status. . . . . .xxvi, xxvii, 381-383, 385, 388-391, 393, 397, 435, 438P  element type code field . . . . . . . . . . . . . . . . . . .388, 391, 397, 401P  enable blank check. . . . . . . . . . . . . . . . . . . . . . . . 326, 370, 376P  enable early recovery . . . . . . . . . . . . . . . . . . . . . . . . .223, 271P  enable EOD generation . . . . . . . . . . . . . . . . . . . . . . . . . . . 268P  enable extended contingent allegiance . . . . . . . . . . . . . . . . . . . 151P  enable threshold comparison . . . . . . . . . . . . . . . . . . . . . . . . 141P  enable vital product data . . . . . . . . . . . . . . . . . . . . . . . . . 104P  end of partition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250P  END OF USER AREA ENCOUNTERED ON THIS TRACK. . . . . . . . . .130, 304, 307, 433P  END-OF-DATA DETECTED. . . . . . . . . . . . . . . . . . . . . . . . . .130, 429P  END-OF-DATA NOT FOUND . . . . . . . . . . . . . . . . . . . . . . . . .130, 430P  end-of-medium . . . . . . 123, 133, 233, 234, 236, 239, 244, 272, 278, 355, 432P  END-OF-PARTITION/MEDIUM DETECTED. . . . . . . . . . . . . . . . . . . .130, 429P  end-of-tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244P  ending boundary field . . . . . . . . . . . . . . . . . . . . . . . . . . . 222P  ending F field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309P  ending index field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310P  ending M field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309P  ending S field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309P  ending track field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310P  EOD defined field . . . . . . . . . . . . . . . . . . . . . . . . . . .268, 272P  EOM bit . . . . . . . . . . . . . . . . . . . 123, 247, 257, 258, 267, 347, 348P  EOP . . . . . . . . . . . . . . . . . . . . . . . .236, 237, 239, 240, 249, 250P  EOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .244, 272N  EQUAL . . 38, 45, 47, 57, 66, 68, 78, 113, 129, 142, 147, 168, 174, 175, 182,L            184, 187, 193, 195, 212, 214, 221, 228, 230, 248, 250, 295, 301, K            304, 305, 307, 309-311, 313, 344, 352, 354, 355, 359, 362, 363, .            388, 436, 438P  ERA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .360, 361P  erase all . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360P  erase by-pass . . . . . . . . . . . . . . . . . . . . . . . . . . . . .372, 374P  ERASE command . . . . . . . . . . . . . . . . . . . . . . . xxiv, 238, 243, 357P  ERASE FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130, 432P  ERASE(10) command . . . . . . . . . . . . . . . . . . . . . . . .xxvi, 360, 361P  ERASE(12) command . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi, 361P  error AEN permission. . . . . . . . . . . . . . . . . . . . . . . . . . . . 151P  Error Counter Pages . . . . . . . . . . . . . . . . . . . . . . . . . xxii, 144P  ERROR LOG OVERFLOW. . . . . . . . . . . . . . . . . . . . . . . . . . .130, 430P  ERROR TOO LONG TO CORRECT . . . . . . . . . . . . . . . . . . . . . . .130, 430P  ETC bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141, 142P  EVFU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .282, 283P  EVFU format start character field . . . . . . . . . . . . . . . . . . . . . 283P  EVFU format stop character field. . . . . . . . . . . . . . . . . . . . . . 283P  EVPD bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104, 108M  except. . . . . . . . . 28, 36, 41, 48, 50, 51, 59, 64, 76, 78, 80, 84, 95,  O                          103, 110, 112, 116, 122, 124, 134, 138, 141, 142, 150,.K                          154, 169, 170, 171, 251, 252, 300, 302, 303, 324, .%                          392-395, 427 P  EXCESSIVE WRITE ERRORS. . . . . . . . . . . . . . . . . . . . . . . . .130, 429P  EXCHANGE MEDIUM command . . . . . . . . . . . . . . . . . . . . . . . xxvi, 384P  exclusive access. . . . . . . . . . . . . . . . . . . . . . .190, 191, 379, 395P  ExEnab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394P  export enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394P  extended contingent allegiance. . .xxxi, 3, 58, 59, 61, 62, 64, 79, 81, 83-85, 4                                     95, 149-151, 238P  extent. . . . . . . . . . . . . . . . . .xxiii, 77, 162, 164, 165, 169, 187-192P  extent bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188-190P  extent list length field. . . . . . . . . . . . . . . . . . . . . . . . . . 190P  FAILED TO SENSE BOTTOM-OF-FORM. . . . . . . . . . . . . . . . . . . . .130, 432P  FAILED TO SENSE TOP-OF-FORM . . . . . . . . . . . . . . . . . . . . . .130, 432P  Fast Assertion Period . . . . . . . . . . . . . . . . . . . . . . . 36, 38, 425P  Fast Cable Skew Delay . . . . . . . . . . . . . . . . . . . . . . . 36, 38, 425P  Fast Deskew Delay . . . . . . . . . . . . . . . . . . . . . . . . . 36, 39, 425P  Fast Hold Time. . . . . . . . . . . . . . . . . . . . . . . . . . . 36, 39, 425P  Fast Negation Period. . . . . . . . . . . . . . . . . . . . . . . . 36, 39, 425P  Fast Synchronous Transfer Option. . . . . . . . . . . . . . . . . . . . . . .38P  FDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269P  field pointer field . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125P  filemark. . . . .123, 128, 130, 237, 240, 247, 251, 252, 256-258, 272, 429, 430P  filemark bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123, 257P  FILEMARK DETECTED . . . . . . . . . . . . . . . . . . . . . . . . . . .130, 429P  FILEMARK OR SETMARK NOT FOUND . . . . . . . . . . . . . . . . . . . . .130, 430P  filled data buffer field. . . . . . . . . . . . . . . . . . . . . . . . . . 342P  first block location field. . . . . . . . . . . . . . . . . . . . . . . . . 250P  first data transfer element address field . . . . . . . . . . . . . . . . . 408P  first element address reported field. . . . . . . . . . . . . . . . . . . . 389P  first import export element address field . . . . . . . . . . . . . . . . . 408P  first record offset field . . . . . . . . . . . . . . . . . . . . . . . . . 194P  first storage element address field . . . . . . . . . . . . . . . . . . . . 407P  fixed bit . . . . . . . . . . . . . . .124, 240, 241, 246-248, 251-253, 258-260P  fixed data partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . 269P  flag bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62, 75, 301P  Flexible Disk Page. . . . . . . . . . . . . . . . . . . . . .3, xxiii, 210, 213P  FmtData bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171-173P  FOCUS SERVO FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . .130, 429P  font identification field . . . . . . . . . . . . . . . . . . . . . . . . . 282P  forced unit access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163P  form slew options field . . . . . . . . . . . . . . . . . . . . . . . . . . 284P  FORMAT command. . . . . . . . . . . . . . . . . . . . .xxiv, 130, 275, 283, 431P  FORMAT COMMAND FAILED . . . . . . . . . . . . . . . . . . . . . . . . .130, 431P  format data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169, 170P  Format Device Page. . . . . . . . . . . . . . . . . . . . .xxiii, 165, 210, 216P  format of logical blocks addresses per second field . . . . . . . . . . . . 328P  format options valid. . . . . . . . . . . . . . . . . . . . . . . . . . . . 172P  format type field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275Q  FORMAT UNIT command . . .xxii, 116, 126, 162, 165, 169-173, 183, 184, 186, 191,  +                           206, 217-219, 2938P  FOV bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172P  FUA bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181P  full bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392P  gap size field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243P  generation address field. . . . . . . . . . . . . . . . . . . . . . . .366, 367P  GENERATION DOES NOT EXIST . . . . . . . . . . . . . . . . . . . . 130, 367, 433P  GET DATA BUFFER STATUS command. . . . . . . . . . . . . . . . . . . . xxvi, 341P  GET MESSAGE(10) command . . . . . . . . . . . . . . . . . . . . . . .xxvii, 414P  GET MESSAGE(12) command . . . . . . . . . . . . . . . . . . . . . . .xxvii, 415P  GET WINDOW command. . . . . . . . . . . . . . . . . . . . . . . .xxvi, 343, 345P  Glist bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183, 184M  GOOD status . . 77, 82, 86, 89, 92, 116, 122, 126, 127, 134, 135, 165, 178, ,P                  181, 187, 193, 211, 238, 253, 259, 263, 278, 280, 347, 363, 398P  group code. . . . . . . . . . . . . . . . . . . . . . . . . . .73, 74, 265, 422P  grown defect list . . . . . . . . . . . . . . 131, 170, 173, 183, 184, 186, 431P  GROWN DEFECT LIST NOT FOUND . . . . . . . . . . . . . . . . . . . . . .131, 431P  hard sector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .218, 219P  HARDWARE ERROR. . . . . . . . .125, 128, 134, 166, 187, 230, 240, 294, 304, 358P  head load delay field . . . . . . . . . . . . . . . . . . . . . . . . . . . 215P  HEAD OF QUEUE TAG . . . . . . . . . . . . . . . . . xxi, 55, 63, 64, 77, 85, 87P  head settle delay field . . . . . . . . . . . . . . . . . . . . . . . . . . 214P  head unload delay . . . . . . . . . . . . . . . . . . . . . . . . . . .213, 215P  Hold Time . . . . . . . . . . . . . . . . . . . . . . . . . .36-39, 46, 51, 425P  host adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3, 5, 421P  HSEC bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218P  i/e . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405K  I/O process . . . .3-5, 41, 42, 47, 51, 52, 54, 55, 58-61, 63-65, 67, 75, .O                     77-82, 84-87, 107, 122, 126, 127, 131, 150, 151, 230, 421, .                     429pP  I/O PROCESS TERMINATED. . . . . . . . . . . . . . . . . . . . . . .67, 131, 429P  I_T . . . . 4, 57, 58, 60, 61, 63, 64, 74, 77-79, 81-84, 86, 112, 122, 150, 253P  I_T_L . . . . . . . . 4, 57, 58, 60, 61, 63, 64, 74, 77-79, 81-84, 86, 112, 253P  I_T_L_Q . . . . . . . . . . . . . . . . . . . . . 4, 58, 61, 63, 64, 79, 84, 86P  I_T_R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4, 57, 60P  I_T_x . . . . . . . . . . . . . . . . . . . . . . . .4, 58, 64, 82-84, 122, 150P  I_T_x_y . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4P  ID CRC OR ECC ERROR . . . . . . . . . . . . . . . . . . . . . . . . . .131, 430P  ID Valid bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396O  IDENTIFY. . . 2, xxi, 4, 6, 50, 51, 55-58, 60, 61, 64, 74, 77-79, 83, 84, 86, EN                91, 95, 103, 105, 127, 128, 131, 161, 167, 173, 189, 270, 399,                 422, 432.P  IDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269P  IGNORE WIDE RESIDUE . . . . . . . . . . . . . . . . . . . . . . . . xxi, 55, 61P  ILI bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .348, 349P  ILLEGAL FUNCTION (SHOULD USE 20 00, 24 00, OR 26 00). . . . . . . . . .131, 431P  ILLEGAL MODE FOR THIS TRACK . . . . . . . . . . . . . . . . .131, 304, 307, 433Q  ILLEGAL REQUEST . . .60, 71, 75, 80, 99, 101, 102, 104, 108-113, 115, 116, 119, .M                       125, 128, 135, 137, 139, 140, 142, 143, 149, 153, 166, .G                       170, 172, 176, 182, 185, 188, 190, 191, 194, 199,.L                       204-206, 227, 228, 240, 244, 246, 256, 258, 277, 283, L                       284, 294, 303, 304, 307, 309-311, 323, 331, 347, 354, >                       358, 360, 371, 384-386, 398-402, 406-408P  image composition field . . . . . . . . . . . . . . . . . . . . . . . . . . 345P  Immed bit . . . . . . 126, 173, 178, 198, 199, 243-245, 255, 258, 259, 261, 328O  immediate . . . . . 81, 126, 173, 178, 198, 199, 238, 243-245, 255, 258, 261, ."                      302, 306, 328P  ImpExp. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .394, 395P  Implemented Operating Definition Page . . . . . . . . . . . .xxii, 94, 155, 156P  import enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394P  import export . . .xxvii, 379, 380, 384, 386, 388, 394, 395, 405, 406, 408, 410P  import export element . xxvii, 379, 384, 386, 388, 394, 395, 405, 406, 408, 410P  IMPORT OR EXPORT ELEMENT ACCESSED . . . . . . . . . . . . . . . . . . .131, 431P  inactivity timer multiplier . . . . . . . . . . . . . . . . . . . . . .xxv, 329P  INCOMPATIBLE MEDIUM INSTALLED . . . . . . . . . . . . . . . . . . . . .131, 431P  INCOMPLETE BLOCK READ . . . . . . . . . . . . . . . . . . . . . . . . .131, 430P  incorrect length indicator. . . . . . . . . . . . . . . . . . . . . . .123, 246P  InEnab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394L  information field . . 67, 98, 102, 123, 124, 128, 156, 166, 185, 187, 194, P                       204, 225-228, 241, 243, 246, 247, 251-253, 256, 257, 259, @                       260, 261, 262, 294, 304, 358, 359, 391-395P  Information Page. . . . . . . . . . . . . . . . . . . . . . xxii, 125, 155, 156P  initial connection. . . . . . . . . . . . . . . . . . . . .3, 4, 60, 63, 79, 85P  initialization pattern. . . . . . . . . . . . . . . . xxiii, 170, 173, 175, 176P  initialization pattern descriptor . . . . . . . . . . . . .xxiii, 170, 173, 175P  initialization pattern length field . . . . . . . . . . . . . . . . . . . . 176P  INITIALIZE ELEMENT STATUS command . . . . . . . . . . . . . . . .xxvi, 381, 385P  INITIATE RECOVERY . . . . . . . . . . . . . . . . 3, 55, 56, 61, 62, 64, 83, 95P  INITIATOR DETECTED ERROR. . . . . . . . . . . . . . . . . .47, 55, 62, 131, 432P  INITIATOR DETECTED ERROR MESSAGE RECEIVED . . . . . . . . . . . . . . .131, 432P  initiator-defined partitions. . . . . . . . . . . . . . . . . . . . . . . . 269P  INQUIRY command . . . .xxi, 65, 79-82, 88, 91, 92, 94, 95, 104, 108, 154, 156, /                         158, 169, 219, 357, 378.P  INQUIRY DATA HAS CHANGED. . . . . . . . . . . . . . . . . . . . . . . .131, 432P  interleave field. . . . . . . . . . . . . . . . . . . . . . . . . . . .172, 218P  INTERMEDIATE status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178P  INTERMEDIATE-CONDITION MET status . . . . . . . . . . . . . . .75, 77, 178, 193P  INTERNAL TARGET FAILURE . . . . . . . . . . . . . . . . . . . . . . . .131, 432P  Inv1 bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385P  Inv2 bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385P  INVALID BITS IN IDENTIFY MESSAGE. . . . . . . . . . . . . . . . . .60, 131, 432P  INVALID COMBINATION OF WINDOWS SPECIFIED. . . . . . . . . . . . . . . .131, 431P  INVALID COMMAND OPERATION CODE. . . . . . . . . . . . . . . . . . . . .131, 431P  INVALID ELEMENT ADDRESS . . . . . . . . . . . . . . . . . . . . . . . .131, 431M  INVALID FIELD IN CDB. . . .104, 108-113, 115, 116, 131, 135, 137, 185, 199, .8                             204, 246, 323, 360, 371, 431M  INVALID FIELD IN PARAMETER LIST . . .99, 101, 110, 111, 113, 131, 139, 140, .N                                       142, 143, 149, 170, 172, 176, 206, 227, .                                       331, 431P  INVALID MESSAGE ERROR . . . . . . . . . . . . . . . . . . . . . . . . .131, 432P  invert. . . . . . . . . . . . . . . . . . 193, 195, 368, 382, 386, 387, 392-395P  Invert bit. . . . . . . . . . . . . . . . . . . . .193, 195, 382, 386, 387, 393P  IP bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173P  IP modifier field . . . . . . . . . . . . . . . . . . . . . . . . . . .175, 176P  L-EC UNCORRECTABLE ERROR. . . . . . . . . . . . . . . . . . . . . . . .131, 430P  LAMP FAILURE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131, 433P  landing zone cylinder field . . . . . . . . . . . . . . . . . . . . . . . . 230P  last block location field . . . . . . . . . . . . . . . . . . . . . . . . . 250P  Last n Error Events Page. 143, 145, 208, 262, 279, 291, 325, 353, 375, 404, 418P  latest bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367P  line slew options field . . . . . . . . . . . . . . . . . . . . . . . . . . 283P  link bit. . . . . . . . . . . . . . . . . . . . . . . . .75, 178, 193, 203, 363P  LINKED COMMAND COMPLETE . . . . . . . . . . . . . . . . . . . . .55, 62, 75, 78P  LINKED COMMAND COMPLETE (WITH FLAG) . . . . . . . . . . . . . . .55, 62, 75, 78P  list parameter. . . . . . . . . . . . . . . . . . . . . . . . . . . . .142, 145P  load bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4, 244P  load eject. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198P  LOAD UNLOAD command . . . . . . . . . . . . . . . . . . . . . . .xxiv, 244, 272P  LOCATE command. . . . . . . . . . . . . . . . . . . . . . . xxiv, 239, 245, 250P  lock. . . . . . . . . . . . .xxiii, 163, 164, 168, 177, 294, 300, 305, 359, 436P  lock bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177P  LOCK UNLOCK CACHE command . . . . . . . . . . . . . . . . . . . . . .xxiii, 177P  LoEj bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198P  LOG COUNTER AT MAXIMUM. . . . . . . . . . . . . . . . . . . . . . 131, 142, 433P  LOG EXCEPTION . . . . . . . . . . . . . . . . . . . . . . . . . . 131, 150, 433P  LOG LIST CODES EXHAUSTED. . . . . . . . . . . . . . . . . . .131, 142, 145, 433N  Log Parameters. . . .7, 74, 109-112, 131, 135, 140, 141, 144, 208, 262, 279, 7                       291, 325, 352, 375, 404, 418, 431.P  LOG PARAMETERS CHANGED. . . . . . . . . . . . . . . . . . . . . . 110, 131, 431P  LOG SELECT command. . . . . . . . . . . . . . .xxi, 109-111, 140, 141, 143, 146P  LOG SENSE command . . . . . . . . . . . . . . . . . xxi, 109, 111, 140-142, 145I  logical block . . 4, 7, 50, 72-74, 78, 86, 99, 100, 123, 124, 131, 148, .P                    161-163, 165-167, 169, 174, 176-178, 180-187, 190, 191, 193, M                    194, 196, 197, 199-208, 212, 218, 221, 222, 225-228, 231, .N                    237-240, 245, 247, 249, 250, 252, 293, 294, 297, 299, 300, N                    303, 304, 307, 308, 311-315, 319, 324, 326, 328, 337, 338, -                    357-364, 366-374, 378, 431nI  Logical Block Address . . . 7, 72-74, 99, 100, 124, 131, 161, 162, 166, dM                              176-178, 180-187, 190, 191, 193, 194, 196, 197, aN                              199-207, 221, 222, 225, 226, 227, 240, 245, 249, M                              293, 294, 299, 300, 303, 304, 307, 308, 311-315,.P                              319, 324, 328, 337, 357-364, 366, 367, 368-374, 431P  LOGICAL BLOCK ADDRESS OUT OF RANGE. . . . . . . . . . . . . . . . . . .131, 431P  logical block data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205P  logical blocks per second of audio playback field . . . . . . . . . . . . . 328P  logical or physical notch . . . . . . . . . . . . . . . . . . . . . . . . . 221P  logical record length field . . . . . . . . . . . . . . . . . . . . . . . . 194N  logical unit. . .xxxi, 4-6, 51, 57-60, 64, 72-74, 77, 79, 80, 82-84, 86, 88, P                   89, 91-96, 98-101, 103-107, 109-112, 114, 115, 117, 118, 121, M                   122, 127, 128, 131, 134-136, 143, 146, 148, 154, 155, 158, TO                   159, 164, 169, 177-183, 185-193, 196-205, 210, 216, 217-222, lN                   230, 243-256, 258-262, 267-270, 273, 275-278, 287, 289, 290,P                   306-314, 316, 323, 328, 341, 343, 347, 349-351, 360-362, 364, P                   366-374, 381, 384-388, 395, 396, 398, 399, 401, 411, 414-417,                    429, 431, 432.P  LOGICAL UNIT COMMUNICATION FAILURE. . . . . . . . . . . . . . . . . . .131, 429P  LOGICAL UNIT COMMUNICATION PARITY ERROR . . . . . . . . . . . . . . . .131, 429P  LOGICAL UNIT COMMUNICATION TIME-OUT . . . . . . . . . . . . . . . . . .131, 429P  LOGICAL UNIT DOES NOT RESPOND TO SELECTION. . . . . . . . . . . . . . .131, 429P  LOGICAL UNIT FAILED SELF-CONFIGURATION. . . . . . . . . . . . . . . . .131, 432P  LOGICAL UNIT HAS NOT SELF-CONFIGURED YET. . . . . . . . . . . . . . . .131, 432P  LOGICAL UNIT IS IN PROCESS OF BECOMING READY. . . . . . . . . . . . . .131, 429P  LOGICAL UNIT NOT READY, CAUSE NOT REPORTABLE. . . . . . . . . . . . . .131, 429P  LOGICAL UNIT NOT READY, FORMAT IN PROGRESS. . . . . . . . . . . . . . .131, 429P  LOGICAL UNIT NOT READY, INITIALIZING COMMAND REQUIRED . . . . . . . . .131, 429P  LOGICAL UNIT NOT READY, MANUAL INTERVENTION REQUIRED. . . . . . . . . .131, 429P  LOGICAL UNIT NOT SUPPORTED. . . . . . . . . . . . . . . . . . 80, 131, 135, 431M  Logical Unit Number . . 4, 5, 57, 60, 72-74, 91, 93, 95, 96, 103, 104, 109, .O                          111, 112, 114, 115, 117, 118, 121, 122, 134-136, 169, 4P                          177-183, 185-187, 189, 192, 193, 196-205, 243-246, 248,N                          249, 251-256, 258, 259, 261, 273, 275-278, 289, 290, I                          306, 307-314, 316, 323, 341, 343, 347, 349-351, .M                          360-362, 364, 366-374, 381, 384-388, 395, 396, 398, i/                          399, 401, 414, 415-417.P  long bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243P  LP bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141, 142P  LPN bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .221, 222P  LU Valid bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396M  mandatory . . . . . . . .xxxi, 4, 6, 56, 57, 63, 71, 74, 92, 123, 124, 134, 1Q                           168, 169, 172, 188, 189, 191, 192, 237, 242, 256, 274, 4I                           289, 295, 305, 340, 359, 383, 413, 421, 435-438,P  maximum additional partitions field . . . . . . . . . . . . . . . . . . . . 269P  maximum burst size field. . . . . . . . . . . . . . . . . . . . . . . . . . 153P  maximum generation address field. . . . . . . . . . . . . . . . . . . . . . 366P  maximum line length field . . . . . . . . . . . . . . . . . . . . . . . . . 283P  maximum number of notches field . . . . . . . . . . . . . . . . . . . . . . 221P  maximum pre-fetch ceiling field . . . . . . . . . . . . . . . . . . . . . . 212P  maximum pre-fetch field . . . . . . . . . . . . . . . . . . . . . . . . . . 212P  maximum volume sequence number. . . . . . . . . . . . . . . . . . . . . . . 403P  MCVal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317, 319, 321P  Measurement Units Page. . . . . . . . . . . . . . . . . . . . . . . . xxvi, 353P  MECHANICAL POSITIONING ERROR. . . . . . . . . . . . . . . . . . . . . .131, 430P  MEDIA LOAD OR EJECT FAILED. . . . . . . . . . . . . . . . . . . . . . .131, 433P  MEDIUM DESTINATION ELEMENT FULL . . . . . . . . . . . . . . . . . . . .131, 432N  MEDIUM ERROR. . . . .xxii, 125, 128, 143, 145, 166, 173, 183, 187, 208, 238, Q                       240, 247, 257, 258, 260, 279, 291, 294, 304, 325, 331-335, .7                       347, 348, 353, 358, 370, 404, 418aP  MEDIUM FORMAT CORRUPTED . . . . . . . . . . . . . . . . . . . . . . . .131, 431P  medium format recognition field . . . . . . . . . . . . . . . . . . . . . . 270P  MEDIUM NOT PRESENT. . . . . . . . . . . . . . . . . . . . . . . . 131, 135, 432P  Medium Partition Page . . . . . . . . . . . . . . . . . . . xxiv, 266, 269, 270P  MEDIUM REMOVAL PREVENTED. . . . . . . . . . . . . . . . . . . . . 131, 179, 433P  medium rotation rate field. . . . . . . . . . . . . . . . . . . . . . . . . 216P  MEDIUM SCAN command . . . . . . . . . . . . . . . . . .xxvi, 293, 358, 362, 363P  MEDIUM SOURCE ELEMENT EMPTY . . . . . . . . . . . . . . . . . . . . . .131, 432I  medium transport element. .xxvii, 379, 380, 384, 386-388, 392, 394-396, .-                             405-407, 409, 410 P  medium transport element address field. . . . . . . . . . . . . . . . .380, 407P  medium type . . . . . . . . . .xxv, 146, 147, 167, 209, 219, 220, 325, 357, 375P  medium types supported. . . . . . . . . . . . . . . . xxiii, 210, 219, 327, 377P  Medium Types Supported Page . . . . . . . . . . . . . xxiii, 210, 219, 327, 377P  medium-changer devices. . . . . . . . . . . . . . . . . . . . . . . . . . . 379P  MESSAGE ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . .49, 131, 432P  MESSAGE IN Phase. . . . . . . . . . .48, 50, 52, 59-62, 64, 66, 69, 77, 78, 423P  MESSAGE OUT Phase 43, 44, 48-50, 52, 55, 60, 62-64, 66, 68, 69, 77, 79, 86, 422P  MESSAGE PARITY ERROR. . . . . . . . . . . . . . . . . . . . .50, 55, 62, 66, 68P  MESSAGE REJECT. . . . . . . . . . . . . . . .55, 59, 60, 62, 63, 65-69, 85, 151P  MF bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211, 212P  MICROCODE HAS BEEN CHANGED. . . . . . . . . . . . . . . . . . 88, 131, 138, 432P  minimum pre-fetch field . . . . . . . . . . . . . . . . . . . . . . . . . . 212P  minimum volume sequence number. . . . . . . . . . . . . . . . . . . . . . . 403P  MISCOMPARE. . . . . . . . . . . 95, 104, 129, 131, 200, 203, 259, 370, 374, 431P  MISCOMPARE DURING VERIFY OPERATION. . . . . . . . . . . . . . . . . . .131, 431P  MISCORRECTED ERROR. . . . . . . . . . . . . . . . . . . . . . . . . . .131, 430P  MO bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215P  mode field. . . . . . . . . . xxi, xxii, 118, 137, 259, 263, 280, 283, 301, 315Q  mode parameter header . . . . xxii, 113, 115, 116, 146, 147, 208, 209, 259-261, VO                                263, 272, 279, 325, 326, 353, 375, 376, 404, 418vQ  Mode Parameters . . . . . . . .7, 74, 88, 112, 113, 115-117, 127, 131, 146-149, rQ                                 162, 188, 191, 208, 210, 231, 246, 253-255, 263, .Q                                 279, 303, 307, 308, 309-312, 325, 339, 349, 351, i<                                 353, 370, 375, 404, 418, 431P  MODE PARAMETERS CHANGED . . . . . . . . . . . . . . . . . . . . . 112, 131, 431P  MODE SELECT(10) command . . . . . . . . . . . . . . . . . . . . . xxi, 114, 117P  MODE SENSE(10) command. . . . . . . . . . . . . . . . . . . .xxi, 114, 115, 117P  MODIFY DATA POINTER . . . . . . . . . . . . . . . . . . . . . . xxi, 55, 57, 63P  motor off delay field . . . . . . . . . . . . . . . . . . . . . . . . . . . 214P  motor on. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213-215P  motor on delay field. . . . . . . . . . . . . . . . . . . . . . . . . . . . 214P  MOVE MEDIUM command . . . . . . . . . . . . . . . . . . . . xxvi, 382, 386, 387Q  MSF . . . . . . . . . xxv, 297-300, 302, 303, 305, 307, 309, 311, 313-316, 319,  8                        323, 324, 329, 330, 337, 338, 437P  mt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405P  MULTIPLE PERIPHERAL DEVICES SELECTED. . . . . . . . . . . . . . . . . .131, 429P  MULTIPLE READ ERRORS. . . . . . . . . . . . . . . . . . . . . . . . . .131, 430P  multiplication factor . . . . . . . . . . . . . . . . . . . . . . . . . . . 211P  ND bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .218, 221P  Negation Period . . . . . . . . . . . . . . . . . . . . 36, 37, 39, 45, 46, 425P  nexus . . . . .3, 4, 41, 50, 57, 58, 60, 61, 63-65, 74, 77-79, 81-84, 86, 112,                  122, 151, 253 P  NO ADDITIONAL SENSE INFORMATION . . . . . . . . . . . . 122, 124, 131, 135, 429P  NO CURRENT AUDIO STATUS TO RETURN . . . . . . . . . . . . . . . . 131, 318, 429P  NO DEFECT SPARE LOCATION AVAILABLE. . . . . . . . . . . . . .131, 187, 370, 431P  NO GAP FOUND. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131, 430P  NO INDEX/SECTOR SIGNAL. . . . . . . . . . . . . . . . . . . . . . . . .131, 429P  NO OPERATION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55, 63P  NO SEEK COMPLETE. . . . . . . . . . . . . . . . . . . . . . . . . . . .132, 429O  NO SENSE. . . . 67, 80, 122, 128, 135, 183, 193, 194, 247, 251-253, 256, 257, .(                  259, 261, 276, 302, 363P  NO WRITE CURRENT. . . . . . . . . . . . . . . . . . . . . . . . . . . .132, 429P  Non-Medium Error Page . . . . . . . 143, 145, 208, 279, 291, 325, 353, 404, 418P  Not Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .395, 396M  NOT READY . . . . 80, 116, 117, 126, 128, 131-133, 135, 136, 162, 169, 233,  O                    244, 264, 287, 302, 307, 309, 310, 312, 339, 411, 429, 431, 3                    432P  NOT READY TO READY TRANSITION(MEDIUM MAY HAVE CHANGED). . . . . . . . . . . 431P  not this bus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396P  Notch and Partition Page. . . . . . . . . . . . . . . . . . . . . . . .210, 220P  notched drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221P  number of blocks field. . . . . . . . . . . . . 98-101, 148, 177, 197, 199, 205P  number of blocks in buffer field. . . . . . . . . . . . . . . . . . . . . . 251P  number of blocks requested field. . . . . . . . . . . . . . . . . . . .362, 363P  number of blocks to scan field. . . . . . . . . . . . . . . . . . . . .362, 363P  number of bytes in buffer field . . . . . . . . . . . . . . . . . . . . . . 251P  number of cylinders field . . . . . . . . . . . . . . . . . . . . 214, 229, 230P  number of data transfer elements field. . . . . . . . . . . . . . . . . . . 408P  number of elements available field. . . . . . . . . . . . . . . . . . . . . 389P  number of F units per S unit field. . . . . . . . . . . . . . . . . . . . . 330P  number of heads field . . . . . . . . . . . . . . . . . . . . . . . . .214, 229P  number of import export elements field. . . . . . . . . . . . . . . . . . . 408P  number of medium transport elements field . . . . . . . . . . . . . . . . . 407P  number of records field . . . . . . . . . . . . . . . . . . . . . . . . . . 194P  number of S units per M unit field. . . . . . . . . . . . . . . . . . . . . 330P  number of storage elements field. . . . . . . . . . . . . . . . . . . . . . 407P  OBJECT POSITION command . . . . . . . . . . . . . . . . . . . . . . . xxvi, 347P  offset boundary field . . . . . . . . . . . . . . . . . . . . . . . . . . . 120N  Operation Code. . . . .xxi, 71-74, 93, 95, 96, 103, 104, 109, 111, 112, 114, M                         115, 117, 118, 121, 122, 131, 134-136, 169, 177-183, RM                         185, 186, 187, 189, 192, 193, 195-205, 243-246, 248, IH                         249, 251-255, 258, 259, 261, 275-278, 289, 290, L                         306-314, 316, 323, 341, 343, 347, 349-351, 360-362, L                         364, 366-374, 384-388, 396, 398, 399, 401, 414-417,                          431.P  OPERATOR MEDIUM REMOVAL REQUEST . . . . . . . . . . . . . . . . . . . .132, 433P  OPERATOR REQUEST OR STATE CHANGE INPUT (UNSPECIFIED). . . . . . . . . .132, 433P  OPERATOR SELECTED WRITE PERMIT. . . . . . . . . . . . . . . . . . . . .132, 433P  OPERATOR SELECTED WRITE PROTECT . . . . . . . . . . . . . . . . . . . .132, 433P  optical memory devices. . . . .xxvi, xxx, 124, 293, 296, 357, 359, 360, 375-378P  Optical Memory Page . . . . . . . . . . . . . . . . . . . . . . .xxvi, 377, 378P  ORDERED QUEUE TAG . . . . . . . . . . . . . . . . . . . .55, 63, 64, 77, 84, 85P  OUT OF FOCUS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132, 433P  output port channel selection . . . . . . . . . . . . . . . . . . . . .xxv, 328P  OVERLAPPED COMMANDS ATTEMPTED . . . . . . . . . . . . . . . . . . .80, 132, 432P  OVERWRITE ERROR ON UPDATE IN PLACE. . . . . . . . . . . . . . . . . . .132, 431P  pacing protocol field . . . . . . . . . . . . . . . . . . . . . . . . . . . 286P  pad bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96, 99, 102P  padding type field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346P  page code field . . . . . . . . . . . . .112, 116, 121, 139, 140, 149, 156, 158P  page control. . . . . . . . . . . . . . . . . . . . . . . . . xxi, 109-111, 115Q  page format . .xxii, 112, 115, 121, 134, 138-140, 144, 148, 149, 210, 266, 280, o'                 327, 353, 377, 405, 419.P  page length field . . . . . . . . . . . . . . .139, 140, 146, 149, 155-159, 207P  pages notched field . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222P  paper instruction parity check. . . . . . . . . . . . . . . . . . . . . . . 281P  PAPER JAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132, 347, 432P  Parallel Printer Interface Page . . . . . . . . . . . . . . . . . . . . . . 280P  parameter code field. . . . . . . . . . . . . . . . . . . . xxii, 141, 143, 144P  parameter code reset. . . . . . . . . . . . . . . . . . . . . . . . . . . . 109P  parameter data length field . . . . . . . . . . . . . . . . . . . . . . . . .94P  Parameter List Length . . . 67, 72-74, 95, 96, 99-101, 103, 109, 110, 112-114, 8                              132, 134-138, 362, 401, 431P  PARAMETER LIST LENGTH ERROR . . . . . . . . . . . . . . . . . . . 113, 132, 431P  parameter list length field . . . . . . . . . . . . . . .96, 110, 113, 135, 137P  PARAMETER NOT SUPPORTED . . . . . . . . . . . . . . . . . . . . . . . .132, 431P  parameter pointer control . . . . . . . . . . . . . . . . . . . . . . . . . 111P  parameter rounding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80P  parameter value field . . . . . . . . . . . . . . . . . . . . . . . . . . . 145P  PARAMETER VALUE INVALID . . . . . . . . . . . . . . . . . . . . . . . .132, 431P  PARAMETERS CHANGED. . . . . . . . . . . . . . . . . . . 110, 112, 131, 132, 431O  parameters savable. . . 149, 210, 214, 217, 220-222, 229, 231, 281, 282, 285, .>                          328-330, 336, 354, 378, 405, 407, 409P  parity select field . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281P  parity selection field. . . . . . . . . . . . . . . . . . . . . . . . . . . 286P  partial medium indicator. . . . . . . . . . . . . . . . . . . . . . . .182, 313P  partial results acceptable. . . . . . . . . . . . . . . . . . . . . . . . . 362P  partition field . . . . . . . . . . . . . . . . . . . . . . . . . 245, 266, 267P  partition size descriptor . . . . . . . . . . . . . . . . . . . . . . .269, 270P  partition size field. . . . . . . . . . . . . . . . . . . . . . . . . . . . 270P  partition size unit of measure. . . . . . . . . . . . . . . . . . . . . . . 269P  pattern field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195P  pattern length field. . . . . . . . . . . . . . . . . . . . . . . . . .176, 195P  pattern type field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176P  PAUSE RESUME command. . . . . . . . . . . . . . . . . . . . . . . . . .xxv, 306P  PCR bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109P  PER bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223, 271P  Peripheral Device Page. . . . xxii, 149, 154, 210, 266, 280, 327, 353, 377, 419P  peripheral device type field. . . . . . . . . . . . . . . . . . . . . . 155-159P  PERIPHERAL DEVICE WRITE FAULT . . . . . . . . . . . . . . . . . . . . .132, 429P  peripheral qualifier field. . . . . . . . . . . . . . . . . . . . . . . 155-159P  PF bit. . . . . . . . . . . . . . . . . . . . . . . . . . . .112, 134, 135, 138P  physical block data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205P  pin 1 field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216P  pin 34 field. . . . . . . . . . . . . . . . . . . . . . . . . . xxiii, 215, 216P  pin 4 field . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxiii, 215P  PIPC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280, 281P  PLAY AUDIO MSF command. . . . . . . . . . . . . . . . . . . . . . . . .xxv, 309P  PLAY AUDIO TRACK INDEX command. . . . . . . . . . . . . . . . . . . . .xxv, 310P  PLAY AUDIO(10) command. . . . . . . . . . . . . . . . . . . . . . xxv, 307, 308P  PLAY AUDIO(12) command. . . . . . . . . . . . . . . . . . . . . . . . .xxv, 308P  Plist bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183, 184P  PMI bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162, 182, 313P  POSITION ERROR RELATED TO TIMING. . . . . . . . . . . . . . . . . . . .132, 432P  position function field . . . . . . . . . . . . . . . . . . . . . . . . . . 347P  POSITION PAST BEGINNING OF MEDIUM . . . . . . . . . . . . . . . . . . .132, 432P  POSITION PAST END OF MEDIUM . . . . . . . . . . . . . . . . . . . . . .132, 432P  POSITION TO ELEMENT command . . . . . . . . . . . . . . . . . . . . .xxvii, 387P  POSITIONING ERROR DETECTED BY READ OF MEDIUM. . . . . . . . . . . . . .132, 430P  post error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223, 271P  POWER ON, RESET, OR BUS DEVICE RESET OCCURRED . . . . . . . . . . . . .132, 431P  POWER-ON OR SELF-TEST FAILURE (SHOULD USE 40 NN). . . . . . . . . . . .132, 432P  Power-On to Selection Time. . . . . . . . . . . . . . . . . . . . . .36, 37, 50P  PPC bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111P  PRA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .362, 363P  PRE-FETCH command . . . . . . . . . . . . . . . . . . . . . . . . . .xxiii, 178P  prevent . . . . xxiii, 27, 51, 65, 108, 161, 163-165, 168, 179, 189, 241, 254, -                  268, 295, 305, 359, 383, 4361P  PREVENT ALLOW MEDIUM REMOVAL command. . . . . . . . . . . . . . xxiii, 161, 179P  prevent bit . . . . . . . . . . . . . . . . . . . . . . . . .164, 179, 189, 254P  primary defect list . . . . . . . . . . . . . . . .132, 169, 173, 183, 184, 431P  PRIMARY DEFECT LIST NOT FOUND . . . . . . . . . . . . . . . . . . . . .132, 431P  primary volume tag. . . . . . . . . . . . . . . . . . . . . . 382, 391-395, 402P  primary volume tag information field. . . . . . . . . . . . . . . . . . . . 391P  PRINT command . . . . . . . . . . . . . . . . . . . . . xxiv, 276-278, 283, 284P  printer devices . . . . . . . xxiv, xxx, 123, 124, 273, 274, 277, 279, 280, 285P  Printer Options Page. . . . . . . . . . . . . . . . . . . . .277, 278, 280, 282P  priority field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97, 211P  product identification field. . . . . . . . . . . . . . . . . . . . . . . . 108P  product serial number field . . . . . . . . . . . . . . . . . . . . . . . . 159P  progress indication field . . . . . . . . . . . . . . . . . . . . . . . . . 126Q  PS bit. . . . . 113, 115, 149, 173, 210, 214, 217, 220-222, 229, 231, 281, 282, A;                  285, 328-330, 336, 354, 378, 405, 407, 4099P  PSUM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .269, 270P  PVolTag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391-395P  QErr bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150P  queue algorithm modifier field. . . . . . . . . . . . . . . . . . . . . . . 150P  queue error management. . . . . . . . . . . . . . . . . . . . . . . . . 85, 150P  QUEUE FULL status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83-85P  queue tag . . . . . . . xxi, 4, 51, 55, 57, 60, 61, 63, 64, 77, 83-87, 150, 151P  queued I/O process. . . . . . . . . . . . . . . . . . . . . . . . 4, 58, 85, 86P  RAENP bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151P  RAM FAILURE (SHOULD USE 40 NN). . . . . . . . . . . . . . . . . . . . .132, 432P  RANDOM POSITIONING ERROR. . . . . . . . . . . . . . . . . . . . . . . .132, 430P  RAREA bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207P  RBO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252, 266, 267P  RC bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223P  RCD bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211P  READ BLOCK LIMITS command . . . . . . . . . . . . . . . . . xxiv, 246, 248, 259P  READ BUFFER command . . . . . . . . . . . . . . . . . . xxi, 118, 119, 136, 137P  read cache disable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211P  READ CAPACITY command . . . . . . . . . . . . . . . . xxiii, 161, 182, 184, 313P  READ CD-ROM CAPACITY command. . . . . . . . . . . . . . . . .xxv, 299, 300, 313P  read continuous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223P  READ DEFECT DATA(10) command. . . . . . . . . . . . . . . . . . . . . . . . 364P  READ DEFECT DATA(12) command. . . . . . . . . . . . . . . . . . . . . xxvi, 364P  READ ELEMENT STATUS command . . . . . . . . xxvii, 381, 382, 385, 388, 389, 397P  read exclusive. . . . . . . . . . . . . . . . . . . . . . . . . . . . .190, 191P  READ GENERATION command . . . . . . . . . . . . . . . . . . . . . . . xxvi, 366P  READ HEADER command . . . . . . . . . . . . . . . . . . . . . . . . . .xxv, 314P  read inhibit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197P  READ LONG command . . . . . . . . . . . . . . . . . . . . . . . xxiii, 185, 204P  READ PAST BEGINNING OF MEDIUM . . . . . . . . . . . . . . . . . . . . .132, 432P  READ PAST END OF MEDIUM . . . . . . . . . . . . . . . . . . . . . . . .132, 432P  READ POSITION command . . . . . . . . . . . . . . . . . . . . . .xxiv, 239, 249P  READ RETRIES EXHAUSTED. . . . . . . . . . . . . . . . . . . . . . . . .132, 430P  READ REVERSE command. . . . . . . . . . . . . . . . . . . . . . . . . xxiv, 251P  read shared . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .190, 191P  READ SUB-CHANNEL command. . . . . . . . . . . . . . . . . . . . . xxv, 300, 316P  READ TOC command. . . . . . . . . . . . . . . . . . . . . . . . . xxv, 298, 323P  READ(10) command. . . . . . . . . . . . . . . . . . . xxiii, 180, 181, 202, 364P  READ(12) command. . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi, 364P  Read-Write Error Recovery Page. . . xxiii, xxiv, 203, 210, 222, 231, 240, 266, -                                      270, 377bP  ready AEN permission. . . . . . . . . . . . . . . . . . . . . . . . . . . . 151P  REASSIGN BLOCKS command . . . . . . . .xxiii, 162, 165, 170, 186, 187, 223, 358P  RECEIVE command . . . . . . . . . . . . . . . . . . . . . . . xxv, 287-289, 292P  RECEIVE DIAGNOSTIC RESULTS command. xxii, 92, 121, 134, 135, 138, 139, 206, 207N  reconnect . . . . 3, xxii, 4, 43, 59-62, 64, 79, 82, 84, 144, 149, 152, 210, >                    265, 280, 287, 327, 353, 377, 411, 412, 419P  RECORD NOT FOUND. . . . . . . . . . . . . . . . . . . . . . . . . . . .132, 430P  RECORDED ENTITY NOT FOUND . . . . . . . . . . . . . . . . . . . . . . .132, 430P  recover buffer order. . . . . . . . . . . . . . . . . . . . . . . . . . . . 267P  RECOVER BUFFERED DATA command . . . . . . . . . . xxiv, 240, 252, 267, 276, 278P  RECOVERED DATA - DATA AUTO-REALLOCATED. . . . . . . . . . . . . . . . .132, 430P  RECOVERED DATA - RECOMMEND REASSIGNMENT . . . . . . . . . . . . . . . .132, 430P  RECOVERED DATA - RECOMMEND REWRITE. . . . . . . . . . . . . . . . . . .132, 430P  RECOVERED DATA USING PREVIOUS SECTOR ID . . . . . . . . . . . . . . . .132, 430P  RECOVERED DATA WITH CIRC. . . . . . . . . . . . . . . . . . . . . . . .132, 430P  RECOVERED DATA WITH ERROR CORRECTION & RETRIES APPLIED. . . . . . . . .132, 430P  RECOVERED DATA WITH ERROR CORRECTION APPLIED. . . . . . . . . . . . . .132, 430P  RECOVERED DATA WITH L-EC. . . . . . . . . . . . . . . . . . . . . . . . . . 132P  RECOVERED DATA WITH NEGATIVE HEAD OFFSET. . . . . . . . . . . . . . . .132, 430P  RECOVERED DATA WITH NO ERROR CORRECTION APPLIED . . . . . . . . . . . .132, 430P  RECOVERED DATA WITH POSITIVE HEAD OFFSET. . . . . . . . . . . . . . . .132, 430P  RECOVERED DATA WITH RETRIES . . . . . . . . . . . . . . . . . . . . . .132, 430P  RECOVERED DATA WITH RETRIES AND/OR CIRC APPLIED . . . . . . . . . . . .132, 430P  RECOVERED DATA WITHOUT ECC - DATA AUTO-REALLOCATED. . . . . . . . . . .132, 430P  RECOVERED DATA WITHOUT ECC - RECOMMEND REASSIGNMENT . . . . . . . . . .132, 430P  RECOVERED DATA WITHOUT ECC - RECOMMEND REWRITE. . . . . . . . . . . . .132, 430P  RECOVERED ERROR . . . . . 80, 122, 125, 128, 142, 145, 166, 173, 184, 224-227, L                            230, 240, 247, 251, 259, 261, 294, 304, 331-335, (                            358, 370, 378P  RECOVERED ID WITH ECC . . . . . . . . . . . . . . . . . . . . . . . . .132, 431P  REFERENCE POSITION FOUND. . . . . . . . . . . . . . . . . . . . . . . .131, 429Q  RelAdr bit. . . . . . . . 107, 177, 178, 181, 182, 185, 193, 199, 200, 202-205, .F                            360, 362, 363, 366, 367, 369, 371, 372, 374P  RELEASE command . . . . . . . . . . . . . . . . .xxiii, xxvii, 187-190, 398-400P  RELEASE RECOVERY. . . . . . . . . . . . . . . . . . . . . . . 3, 41, 55, 64, 83P  RELEASE UNIT command. . . . . . . . . . . . . . . . . . . . . . .xxiv, 253, 254P  removable . . . . . . . 81, 88, 92, 106, 128, 161, 162, 167, 219, 357, 381, 410P  report early-warning. . . . . . . . . . . . . . . . . . . . . . . . . . . . 267P  report log exception condition. . . . . . . . . . . . . . . . . . . . . . . 150P  report setmarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267P  report updated block read . . . . . . . . . . . . . . . . . . . . . . .370, 378P  REPOSITION ERROR. . . . . . . . . . . . . . . . . . . . . . . . . . . .132, 432P  REQUEST SENSE command . .xxii, 41, 67, 80, 82, 88, 92, 95, 122, 123, 127, 156, @                           169, 193, 194, 287, 302, 339, 363, 412P  request to send . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286P  REQUEST VOLUME ELEMENT ADDRESS command. . . . . . . . . . .xxvii, 396, 401, 402P  RESELECTION Phase . . . . . . . . . . . . 4, 34, 38, 41-44, 50, 57, 61, 86, 421P  RESERVATION CONFLICT status . . . . . . . .164, 169, 189-192, 254, 255, 399-401P  reservation identification field. . . . . . . . . . . . . . . . . . . . . . 189P  reservation type field. . . . . . . . . . . . . . . . . . . . . . . . . . . 190P  RESERVE command . . . . xxiii, xxvii, 112, 165, 188-192, 254, 255, 397, 399-401P  RESERVE UNIT command. . . . . . . . . . . . . . . . . . . . . . . xxiv, 253-255P  reserved area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207Q  reset condition . . . .3, 33, 38, 41, 47, 49-52, 59, 65, 67-69, 76, 79, 80, 82,  P                         83, 88, 95, 108, 112, 116, 117, 179, 189-191, 254, 264, %                         399, 400, 401.P  Reset Hold Time . . . . . . . . . . . . . . . . . . . . . . . . . . .36, 38, 51P  Reset to Selection Time . . . . . . . . . . . . . . . . . . . . . . .36, 38, 51P  RESTORE POINTERS. . . . . . . . . . . . . . . . . . .54, 55, 57, 60, 62, 65, 78P  resume bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306P  retain bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278P  reverse scan direction. . . . . . . . . . . . . . . . . . . . . . . . . . . 362P  REW . . . . . . . . . . . . . . . . . . . . . . 247, 257-259, 261, 266-268, 272P  REWIND command. . . . . . . . . . . . . . . . . . . . . . . .xxiv, 81, 236, 255P  REZERO UNIT command . . . . . . . . . . . . . . . . . . . . . . xxiii, 165, 192P  RIBBON, INK, OR TONER FAILURE . . . . . . . . . . . . . . . . . . . . .132, 431P  RIF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .344, 346P  Rigid Disk Drive Geometry Page. . . . . . . . . . . . . . . . . . . . xxiv, 229P  RLEC bit. . . . . . . . . . . . . . . . . . . . . . . . . . .142, 143, 145, 150P  RMB bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106P  rotate bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409P  ROUNDED PARAMETER . . . . . . . . . . . . . . . . . . . . . . . . .81, 132, 432P  RPL . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132, 229, 230, 433P  RPL STATUS CHANGE . . . . . . . . . . . . . . . . . . . . . . . . 132, 230, 433P  RSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362P  RSmk. . . . . . . . . . . . . . . . . . . 102, 123, 247, 252, 256-258, 266, 267P  RTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .285, 286P  RUBR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378P  save bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93P  SAVE DATA POINTER . . . . . . . . . . . . . . . . . . . .52, 54, 55, 59, 65, 78P  save implemented. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157P  save parameters . . . . . . . . . . . . . . . . . . . . . . . . . 109, 111, 219P  SavImp bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157P  SAVING PARAMETERS NOT SUPPORTED . . . . . . . . . . . . . . . . . 116, 132, 432P  SCAN command. . . . . . . . . . . . . . . . .xxvi, 293, 341, 350, 358, 362, 363P  SCAN HEAD POSITIONING ERROR . . . . . . . . . . . . . . . . . . . . . .132, 433P  scanner devices . . . . . . . . . . . . . . .xxvi, xxx, 339, 340, 352, 353, 355P  SCSI ID . . . . . . . . . . . . . . . .5, 31, 34, 37, 42, 43, 82, 381, 421, 422P  SCSI PARITY ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . .132, 432P  SCSI Pointers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54P  SCSI TO HOST SYSTEM INTERFACE FAILURE . . . . . . . . . . . . . . . . .132, 433P  SCSI-2. . . . 2, xxvii, xxx, xxxi, 1, 5, 6, 9, 33, 43, 74, 79, 84, 91, 94, 95, 5                149, 187, 189, 421, 427, 429, 435, 4398P  SCTE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .282, 283P  SDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269P  search argument descriptor. . . . . . . . . . . . . . . . . . . . . . .194, 195P  search argument length field. . . . . . . . . . . . . . . . . . . . . . . . 194P  sectors per track field . . . . . . . . . . . . . . . . . . . . . . . .214, 218P  SEEK(10) command. . . . . . . . . . . . . . . . . . . . . . . . . . .xxiii, 196P  segment descriptor. . . . . . . . . . . . . . . . . . . . xxi, 96-102, 123, 124P  segment number field. . . . . . . . . . . . . . . . . . . . . . . . . . . . 123P  select data compression algorithm field . . . . . . . . . . . . . . . . . . 268P  select data partitions. . . . . . . . . . . . . . . . . . . . . . . . . . . 269P  SELECT OR RESELECT FAILURE. . . . . . . . . . . . . . . . . . . . . . .132, 432P  Selection Abort Time. . . . . . . . . . . . . . . . . . . . 36, 38, 43, 44, 422P  SELECTION Phase . . . . . . . . . . . . . 3, 34, 41-43, 50, 57, 60, 77, 86, 421P  Selection Time-out Delay. . . . . . . . . . . . . . . . . . . . .36, 38, 43, 44P  self test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92, 128P  send action code field. . . . . . . . . . . . . . . . . . . . . . 398, 401, 402P  SEND DIAGNOSTIC command . . . . . . . . . xxii, 92, 121, 134, 138, 139, 206-208P  SEND MESSAGE(10) command. . . . . . . . . . . . . . . . . . . . . . .xxvii, 416P  SEND MESSAGE(12) command. . . . . . . . . . . . . . . . . . . . . . .xxvii, 417P  SEND VOLUME TAG command . . . . . . . . . . . xxvii, 381, 382, 396-398, 401-403P  sense key field . . . . . . . . . . . . . . . . . . . . . . . . . . . .124, 125P  sense-key specific field. . . . . . . . . . . . . . . . . . . . . . . .125, 126P  sense-key specific valid. . . . . . . . . . . . . . . . . . . . . . . . . . 125P  SEQUENTIAL POSITIONING ERROR. . . . . . . . . . . . . . . . . . . . . .133, 432Q  sequential-access devices . . .xxiv, xxx, 80, 97, 101, 102, 123, 124, 148, 233, x<                                 239, 241, 242, 262, 263, 265P  Serial Printer Interface Page . . . . . . . . . . . . . . . . . . . . .280, 285P  SET LIMITS(10) command. . . . . . . . . . . . . . . . . . . . . . . . . . . 368P  SET LIMITS(12) command. . . . . . . . . . . . . . . . . . . . . . . . xxvi, 368P  SET WINDOW command. . . . . . . . . . . . . . . . . . . . . . . .xxvi, 345, 351P  SETMARK DETECTED. . . . . . . . . . . . . . . . . .133, 247, 252, 256, 257, 429P  SEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259, 261, 266-268P  SftRe bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51, 108P  SILI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246, 251, 252P  SIMPLE QUEUE TAG. . . . . . . . . . . . . . . . .55, 61, 63, 64, 77, 84-86, 150P  single bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42, 343P  SKSV bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125, 126P  SLEW AND PRINT command. . . . . . . . . . . . . . . . . xxiv, 276-278, 283, 284P  SLEW FAILURE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133, 432P  slew mode field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283P  slew value field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277P  SOCF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266-268P  soft sector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .218, 219P  SOTC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307-312, 327, 328P  source block length field . . . . . . . . . . . . . . . . . . . . . . . . . 101P  source logical block address field. . . . . . . . . . . . . . . . . . . . . 100P  source storage element address field. . . . . . . . . . . . . . . . . .393, 394P  source valid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393P  SP bit. . . . . . . . . . . . . . . . . . . . . . . . . 109, 111, 113, 116, 141P  SPACE command . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv, 256P  spanned data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193P  speed field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv, 263P  SPINDLE SERVO FAILURE . . . . . . . . . . . . . . . . . . . . . . . . .133, 429P  SPINDLES NOT SYNCHRONIZED . . . . . . . . . . . . . . . . . . . . . . .133, 433P  SPINDLES SYNCHRONIZED . . . . . . . . . . . . . . . . . . . . . . . . .133, 433P  SpnDat bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193P  SSEC bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218P  SSN bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215P  st. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405P  start . . . . . xxiii, 3, 54, 81, 108, 135, 161, 162, 164, 167, 168, 193, 195, P                  198, 214, 215, 282, 283, 295, 305-307, 310, 311, 324, 338, 359,                  381, 4352P  start bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198P  start sector number . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215P  starting boundary field . . . . . . . . . . . . . . . . . . . . . . . . . . 221P  starting F field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309P  starting index field. . . . . . . . . . . . . . . . . . . . . . . . . . . . 310P  starting M field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309P  starting S field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309P  starting track field. . . . . . . . . . . . . . . . . . . . . . . 310, 311, 323O  status. . . . . .3, xxi, xxv, xxvi, xxvii, xxx, 3, 5, 31, 33, 34, 37, 38, 41, nN                   44, 45, 47-52, 54, 58-62, 65, 67, 71, 75-77, 80-89, 92, 95, M                   98, 99, 101, 102, 104, 108-113, 115-117, 119, 122, 125-128,rN                   131, 132, 134, 135, 137, 139, 140, 142, 143, 145, 149, 153, O                   162, 164-166, 169, 170, 172-174, 176, 178, 181-185, 187-194,  P                   197-200, 203-206, 209, 211, 214, 218, 219, 223-228, 230, 233, O                   238, 240, 243-247, 251-263, 267, 271, 276-278, 280, 283, 284, M                   287, 292, 293, 302-304, 306, 307, 309, 310, 312, 317, 318, .P                   320, 321, 323, 328, 331-335, 339-342, 347-349, 351, 354, 358, J                   360, 363, 367, 370-372, 374, 376-378, 381-386, 388-393, F                   397-401, 407, 408, 411, 423, 429, 433, 435, 436, 438P  STATUS Phase. . . . . . . . . . . . . . . . . . . . . . 41, 48, 50, 76, 77, 423P  step count truncate enable. . . . . . . . . . . . . . . . . . . . . . . . . 283P  step pulse per cylinder . . . . . . . . . . . . . . . . . . . . . . . . . . 215P  stop bit length field . . . . . . . . . . . . . . . . . . . . . . . . . . . 286P  stop format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173P  stop on consecutive filemarks . . . . . . . . . . . . . . . . . . . . . . . 267P  stop on track crossing. . . . . . . . . . . . . . . . . . . . . . 310, 311, 328P  STOP PRINT command. . . . . . . . . . . . . . . . . . . . . . . . . . xxiv, 278P  storage element . . . . . xxvii, 379, 381, 384, 386, 388, 392-395, 405-407, 410P  STPF bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173P  stream selection field. . . . . . . . . . . . . . . . . . . . . . . . . 414-417P  sub Q bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .316, 317P  sub-channel data format field . . . . . . . . . . . . . . . .316, 317, 321, 322P  sub-channel data header . . . . . . . . . . . . . . . . . . . . . 317, 320, 321P  sub-channel data length field . . . . . . . . . . . . . . . . . . . . . . . 317P  SubQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316P  supplied format field . . . . . . . . . . . . . . . . . . . . . . . . .206, 207P  Supported Diagnostic Pages. . . . . . . xxii, 139, 206, 262, 279, 325, 352, 404P  Supported Log Pages . . .xxii, 143, 145, 146, 208, 262, 279, 325, 353, 404, 418P  supported page list field . . . . . . . . . . . . . . . . . . . . 140, 146, 158P  Supported Vital Product Data Pages. . . . . . . . . . . . . . . .xxii, 155, 158P  suppress incorrect length indicator . . . . . . . . . . . . . . . . . . . . 246P  SURF bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219P  surface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219, 355P  SValid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392-395P  SYNCHRONIZE BUFFER command. . . . . . . . . . . . . . . . . . . .xxiv, 278, 284P  SYNCHRONIZE CACHE command . . . . . . . . . . . . . . . . .xxiii, 165, 198, 199P  SYNCHRONOUS DATA TRANSFER ERROR . . . . . . . . . . . . . . . . . . . .133, 431P  SYNCHRONOUS DATA TRANSFER REQUEST . . . . . . . . . . . . . xxi, 55, 57, 65, 82P  SYSTEM RESOURCE FAILURE . . . . . . . . . . . . . . . . . . . . . . . .133, 433P  TAPE LENGTH ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . .133, 431P  TAPE OR ELECTRONIC VERTICAL FORMS UNIT NOT READY. . . . . . . . . . . .133, 432P  TAPE POSITION ERROR AT BEGINNING-OF-MEDIUM. . . . . . . . . . . . . . .133, 432P  TAPE POSITION ERROR AT END-OF-MEDIUM. . . . . . . . . . . . . . . . . .133, 432P  target certification list . . . . . . . . . . . . . . . . . . . . . . . . . 170P  TARGET OPERATING CONDITIONS HAVE CHANGED. . . . . . . . . . . . . . . .133, 432P  target routine. . . . . . . . . . . . . . .4, 5, 57-60, 63, 80, 82, 84, 91, 290P  target save disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141P  TB bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223, 271P  TCVal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317, 319, 322P  TERMINATE I/O PROCESS . . . . . . . . . . . . . . . . . . . 55, 67, 77, 79, 107P  TEST UNIT READY command . . . . . . . . . . . .xxii, 82, 92, 135, 161, 287, 339P  third party . . . . . . . . . . . . . .96, 112, 187, 189, 191, 253-255, 398-400P  third party reservation . . . . . . . . . . . . . . . . . . .112, 191, 254, 400P  THRESHOLD CONDITION MET . . . . . . . . . . . . . . . . . . . . . 133, 142, 433P  threshold field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345P  threshold met criteria. . . . . . . . . . . . . . . . . . . . . . . . xxii, 142P  THRESHOLD PARAMETERS NOT SUPPORTED. . . . . . . . . . . . . . . . . . .133, 431P  TOO MANY WINDOWS SPECIFIED. . . . . . . . . . . . . . . . . . . . . . .133, 431P  track code valid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319P  TRACK FOLLOWING ERROR . . . . . . . . . . . . . . . . . . . . . . . . .133, 429P  track number field. . . . . . . . . . . . . . . . . . . . . . . . . . .317, 324P  track relative CD-ROM address field . . . . . . . . . . . . . . . . . . . . 319P  track skew factor field . . . . . . . . . . . . . . . . . . . . . . . . . . 218P  TRACKING SERVO FAILURE. . . . . . . . . . . . . . . . . . . . . . . . .133, 429P  tracks per zone field . . . . . . . . . . . . . . . . . . . . . . . . .217, 218P  transfer block. . . . . . . . . . . . . . . . . . . . . . . . . . .223-227, 271O  Transfer Length . . 54, 67, 72-74, 137, 148, 178, 180-182, 185, 200-204, 210, ,N                      212, 241, 246, 247, 251-253, 259-262, 272, 275-277, 283, P                      290, 303, 307, 308, 311, 312, 328, 343, 349-351, 360, 361, 0                      364, 368, 372-374, 416, 417P  Transfer Period . . . . . . . . . . . . . . . . . . .36, 38, 45-47, 65, 66, 425P  Translate Address Page - RECEIVE DIAGNOSTIC . . . . . . . . . . xxiii, 206, 207P  Translate Address Page - SEND DIAGNOSTIC. . . . . . . . . . . . . . .xxiii, 206P  translate format field. . . . . . . . . . . . . . . . . . . . . . . . .206, 208P  translated address field. . . . . . . . . . . . . . . . . . . . . . . . . . 208P  transport element address field . . . . . . . . . . . . . . . . . . . .380, 407P  transport geometry descriptor . . . . . . . . . . . . . . . . . . . . . . . 409P  true ready. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214, 215P  TSD bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109, 141P  UAAENP bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151P  UNABLE TO ACQUIRE VIDEO . . . . . . . . . . . . . . . . . . . . . . . .133, 433P  UNABLE TO RECOVER TABLE-OF-CONTENTS . . . . . . . . . . . . . . . . . .133, 433P  unexpected disconnect . . . . . . . . . .3, 5, 47, 49, 50, 57, 60, 76, 122, 126P  unexpected reselection. . . . . . . . . . . . . . . . . . . . . . . . . . . .82M  UNIT ATTENTION. . . . . . 51, 59, 79, 81, 82, 85, 88, 89, 94, 95, 104, 110, 2M                            112, 128, 138, 142, 148, 150, 151, 166, 188, 190, .A                            230, 240, 253, 264, 294, 304, 358, 400.P  unit attention AEN permission . . . . . . . . . . . . . . . . . . . . . . . 151P  unit off-line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134P  Unit Serial Number Page . . . . . . . . . . . . . . . . . . . . .xxii, 155, 159P  UnitOfl bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134P  UNLOAD TAPE FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . .133, 433P  UNRECOVERED READ ERROR. . . . . . . . . . 133, 166, 239-241, 294, 304, 358, 430P  UNRECOVERED READ ERROR - AUTO REALLOCATE FAILED . . . . . . . . . . . .133, 430P  UNRECOVERED READ ERROR - RECOMMEND REASSIGNMENT . . . . . . . . . . . .133, 430P  UNRECOVERED READ ERROR - RECOMMEND REWRITE THE DATA . . . . . . . . . .133, 430P  UNSUCCESSFUL SOFT RESET . . . . . . . . . . . . . . . . . . . . . . . .133, 432P  UPDATE BLOCK command. . . . . . . . . . . . . . . . . .xxvi, 369, 370, 376, 378P  UPDATED BLOCK READ. . . . . . . . . . . . . . . . . . . . . .133, 370, 378, 433P  VCBP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280, 281P  VCBS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280, 281P  vendor identification field . . . . . . . . . . . . . . . . . . . . . . . . 108P  verification length field . . . . . . . . . . . . . . . . . . . . . . . . . 200P  verify correction span field. . . . . . . . . . . . . . . . . . . . . . . . 231P  Verify Error Recovery Page. . . . . . . . . . . . xxiv, 203, 210, 231, 327, 377P  verify recovery time limit field. . . . . . . . . . . . . . . . . . . . . . 231P  verify retry count field. . . . . . . . . . . . . . . . . . . . . .224-226, 231P  VERIFY(10) command. . . . . . . . . . . . . . . . . . .xxvi, 370, 371, 373, 374P  VERIFY(12) command. . . . . . . . . . . . . . . . . . . . . . . .xxvi, 371, 374P  vertical forms unit . . . . . . . . . . . . . . . . . . . . . 133, 281-283, 432P  VES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280, 281P  VFU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv, 281P  VFU control bit polarity. . . . . . . . . . . . . . . . . . . . . . . . . . 281P  VFU control bit select. . . . . . . . . . . . . . . . . . . . . . . . . . . 281P  VFU extended skip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281P  VIDEO ACQUISITION ERROR . . . . . . . . . . . . . . . . . . . . . . . .133, 433P  Vital Product Data Parameters . . . . . . . . . . . . . . . . . . . . . .7, 154P  VolTag. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388, 396, 397P  volume identification field . . . . . . . . . . . . . . . . . . . . . . . . 382P  volume identification template field. . . . . . . . . . . . . . . . . . . . 403P  VOLUME OVERFLOW . . . . . . . . . . . . . . . . . . . . .129, 240, 259-262, 267P  volume sequence number field. . . . . . . . . . . . . . . . . . . . . .382, 403P  volume tag. . . . . . . . . . .xxvi, xxvii, 381-383, 388, 391-398, 401-403, 438P  wait bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341P  WBS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362P  WCE bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211P  WIDE DATA TRANSFER REQUEST. . . . . . . . . . . . . . . . . .46, 55, 57, 67, 68P  window length field . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345P  window width field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345P  WP bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209, 263, 376P  WRITE AND VERIFY(10) command. . . . . . . . . . . . . . . . . . .xxvi, 373, 374P  WRITE AND VERIFY(12) command. . . . . . . . . . . . . . . . . . . . . xxvi, 374P  WRITE APPEND ERROR. . . . . . . . . . . . . . . . . . . . . . . . . . .133, 432P  WRITE APPEND POSITION ERROR . . . . . . . . . . . . . . . . . . . . . .133, 432P  WRITE BUFFER command. . . . . . . . . . . . . . . . . .xxii, 118, 119, 136, 138P  write cache enable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211P  WRITE ERROR . . xxiii, xxiv, 124, 133, 203, 210, 222, 231, 238, 240, 241, 266, #                  270, 271, 377, 430.P  WRITE ERROR - AUTO REALLOCATION FAILED. . . . . . . . . . . . . . . . .133, 430P  WRITE ERROR RECOVERED WITH AUTO REALLOCATION. . . . . . . . . . . . . .133, 430P  write exclusive . . . . . . . . . . . . . . . . . . . . . . . . . . . .190, 191P  WRITE FILEMARKS command . . . . . . . . xxiv, 238, 244, 255, 259, 261, 262, 268P  write inhibit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197P  WRITE LONG command. . . . . . . . . . . . . . . . . . . . . . . . . .xxiii, 204P  write precompensation field . . . . . . . . . . . . . . . . . . . 214, 215, 230P  write protect . . . . . . . . . . . . . . . . . . . . . .81, 132, 209, 263, 433P  WRITE PROTECTED . . . . . . . .133, 166, 209, 233, 240, 263, 294, 358, 376, 431P  write retention priority field. . . . . . . . . . . . . . . . . . . . . . . 211P  WRITE SAME command. . . . . . . . . . . . . . . . . . . . . . . . . .xxiii, 205P  write setmark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261P  WRITE(10) command . . . . . . . . . . . . . . . .xxiii, xxvi, 201-203, 372, 373P  WRITE(12) command . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi, 373P  written block search. . . . . . . . . . . . . . . . . . . . . . . . . . . . 362P  WSmk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261P  X-axis resolution field . . . . . . . . . . . . . . . . . . . . . . . . . . 345P  X-axis upper left field . . . . . . . . . . . . . . . . . . . . . . . . . . 345P  Y-axis resolution field . . . . . . . . . . . . . . . . . . . . . . . . . . 345P  Y-axis upper left field . . . . . . . . . . . . . . . . . . . . . . . . . . 345  9  s