ANSI INCITS 380-2003 For Information Technology - SCSI Stream Commands -2 (SSC-2).pdf

《ANSI INCITS 380-2003 For Information Technology - SCSI Stream Commands -2 (SSC-2).pdf》由会员分享，可在线阅读，更多相关《ANSI INCITS 380-2003 For Information Technology - SCSI Stream Commands -2 (SSC-2).pdf（137页珍藏版）》请在麦多课文档分享上搜索。

1、American National StandardDeveloped byfor Information technology -SCSI Stream Commands - 2 (SSC-2)ANSI INCITS 380-2003ANSIINCITS380-2003ANSIINCITS 380-2003American National Standardfor Information Technology SCSI Stream Commands - 2 (SSC-2)SecretariatInformation Technology Industry CouncilApproved O

2、ctober 30, 2003 American National Standards Institute, Inc.AbstractThis standard specifies the device model and functional requirements for the SCSI sequential-accessstream device type. This standards permits the SCSI sequential-access stream device type to attach tocomputers and provides the defini

3、tions for their use.This standard does not contain material related to any service delivery subsystem which is used to trans-port the commands, command parameter data, command response data, and status specified in this stan-dard.Approval of an American National Standard requires review by ANSI that

4、 therequirements for due process, consensus, and other criteria for approval havebeen met by the standards developer.Consensus is established when, in the judgement of the ANSI Board ofStandards Review, substantial agreement has been reached by directly andmaterially affected interests. Substantial

5、agreement means much more thana simple majority, but not necessarily unanimity. Consensus requires that allviews and objections be considered, and that a concerted effort be madetowards their resolution.The use of American National Standards is completely voluntary; theirexistence does not in any re

6、spect preclude anyone, whether he has approvedthe standards or not, from manufacturing, marketing, purchasing, or usingproducts, processes, or procedures not conforming to the standards.The American National Standards Institute does not develop standards andwill in no circumstances give an interpret

7、ation of any American NationalStandard. Moreover, no person shall have the right or authority to issue aninterpretation of an American National Standard in the name of the AmericanNational Standards Institute. Requests for interpretations should beaddressed to the secretariat or sponsor whose name a

8、ppears on the titlepage of this standard.CAUTION NOTICE: This American National Standard may be revised orwithdrawn at any time. The procedures of the American National StandardsInstitute require that action be taken periodically to reaffirm, revise, orwithdraw this standard. Purchasers of American

9、National Standards mayreceive current information on all standards by calling or writing the AmericanNational Standards Institute.American National StandardPublished byAmerican National Standards Institute, Inc.25 West 43rd Street, New York, NY 10036Copyright 2003 by Information Technology Industry

10、Council (ITI)All rights reserved.No part of this publication may be reproduced in anyform, in an electronic retrieval system or otherwise,without prior written permission of ITI, 1250 Eye Street NW, Washington, DC 20005. Printed in the United States of AmericaCAUTION: The developers of this standard

11、 have requested that holders of patents that may berequired for the implementation of the standard disclose such patents to the publisher. However,neither the developers nor the publisher have undertaken a patent search in order to identifywhich, if any, patents may apply to this standard. As of the

12、 date of publication of this standardand following calls for the identification of patents that may be required for the implementation ofthe standard, no such claims have been made. No further patent search is conducted by the de-veloper or publisher in respect to any standard it processes. No repre

13、sentation is made or impliedthat licenses are not required to avoid infringement in the use of this standard.iContentsPageForeword viIntroduction .ix1 Scope . 12 Normative references 32.1 Normative references 32.2 Approved references. 42.3 References under development 43 Definitions, acronyms, keywo

14、rds, and conventions 53.1 Definitions . 53.2 Acronyms 93.3 Keywords 93.4 Editorial Conventions 103.5 Notation Conventions 113.5.1 Notation for state diagrams 114 General Concepts . 134.1 Overview . 134.2 Sequential-access device model. 134.2.1 Sequential-access device model overview 134.2.2 Physical

15、 elements 134.2.3 Early-warning . 164.2.4 Partitions within a volume 174.2.5 Logical objects . 194.2.5.1 Logical objects within a partition . 194.2.5.2 Logical object identifier 204.2.6 Logical files 204.2.6.1 Logical files within a partition 204.2.6.2 Logical file identifier. 204.2.7 Logical sets 2

16、04.2.7.1 Logical sets within a partition 204.2.7.2 Logical set identifier 204.2.8 Object buffering 204.2.9 Synchronize operation behavior. 214.2.10 Direction and position definitions . 214.2.11 Error reporting 224.2.12 Write protection 234.2.12.1 Write protection introduction . 234.2.12.2 Write prot

17、ection additional sense code use 244.2.12.3 Software write protection for the device server . 244.2.12.4 Associated write protection . 254.2.12.5 Persistent write protection. 254.2.12.6 Permanent write protection . 254.2.13 Progress indication. 254.2.14 Tagged command queuing 264.2.14.1 Tagged comma

18、nd queuing overview 264.2.14.2 Explicit address mode tagged write sequences 264.2.15 Block address mode. 27iiPage4.2.15.1 Block address mode overview 274.2.15.2 Block address mode selection 274.2.15.3 Block address mode state diagrams. 284.2.16 TapeAlert application client interface . 374.2.16.1 Int

19、roduction to TapeAlert application client interface 374.2.16.2 TapeAlert log sense format. 374.2.16.3 Tape drive/autoloader flag types and definitions. 384.2.17 READ ATTRIBUTE and WRITE ATTRIBUTE command support 394.2.18 Device reservations and command behavior. 405 Explicit address command descript

20、ions for sequential-access devices. 435.1 Summary of commands for explicit address mode . 435.2 ERASE(16) command. 455.3 READ(16) command. 475.4 READ REVERSE(16) command. 505.5 VERIFY(16) command 515.6 WRITE(16) command . 535.7 WRITE FILEMARKS(16) command 556 Implicit address command descriptions fo

21、r sequential-access devices 576.1 Summary of commands for implicit address mode . 576.2 ERASE(6) command. 606.3 LOCATE(10) command. 606.4 READ(6) command. 626.5 READ REVERSE(6) command. 646.6 SPACE(6) command. 646.7 VERIFY(6) command 676.8 WRITE(6) command . 696.9 WRITE FILEMARKS(6) command 707 Comm

22、on command descriptions for sequential-access devices 727.1 FORMAT MEDIUM command. 727.2 LOAD UNLOAD command 737.3 LOCATE(16) command. 757.4 READ BLOCK LIMITS command 777.5 READ POSITION command . 787.6 RECOVER BUFFERED DATA command. 857.7 REPORT DENSITY SUPPORT command . 867.8 REWIND command. 907.9

23、 SET CAPACITY command . 917.10 SPACE(16) command. 928 Parameters for sequential-access devices 978.1 Diagnostic parameters 978.2 Log parameters. 978.2.1 Log parameters overview. 978.2.2 Sequential-Access Device log page. 988.2.3 TapeAlert log page. 998.3 Mode parameters 998.3.1 Mode parameters overv

24、iew 998.3.2 Data Compression mode page 1038.3.3 Device Configuration mode page. 107iiiPage8.3.4 Medium Partition mode page . 1118.3.5 Read-Write Error Recovery mode page . 1158.3.6 Informational Exceptions Control mode page 116Tables1 Error conditions and sense keys 222 Write protect additional sens

25、e code combinations . 243 Commands providing progress indication without changing ready state 254 Commands changing ready state and providing progress indication265 TapeAlert flag types . 386 TapeAlert flags minimum subset 387 TapeAlert flag definition grouping. 398 Device common attributes 399 Medi

26、um common attributes 4010 SSC-2 commands that are allowed in the presence of various reservations 4111 Explicit address command set for sequential-access devices 4312 ERASE(16) command 4613 READ(16) command 4714 READ REVERSE(16) command 5015 VERIFY(16) command . 5116 WRITE(16) command. 5317 WRITE FI

27、LEMARKS(16) command . 5518 Implicit address command set for sequential-access devices 5719 ERASE(6) command 6020 LOCATE(10) command 6121 READ(6) command 6222 READ REVERSE(6) command 6423 SPACE(6) command 6524 Code definition . 6525 VERIFY(6) command . 6726 WRITE(6) command. 6927 WRITE FILEMARKS(6) c

28、ommand . 7028 FORMAT MEDIUM command 7229 Format field definition . 7330 LOAD UNLOAD command. 7431 LOCATE(16) command 75ivPage32 dest_type field definitions. 7633 READ BLOCK LIMITS command. 7734 READ BLOCK LIMITS data . 7735 READ POSITION command 7836 READ POSITION service action codes . 7837 READ PO

29、SITION data format, short form 8038 READ POSITION data format, long form. 8239 READ POSITION data format, extended form. 8440 RECOVER BUFFERED DATA command 8541 REPORT DENSITY SUPPORT command 8642 Density support header 8743 Density support data block descriptor 8844 REWIND command 9145 SET CAPACITY

30、 command 9146 SPACE(16) command 9347 Space positioning information 9448 Diagnostic page codes. 9749 Log page codes 9750 Parameter codes for Sequential-Access Device log page. 9851 TapeAlert log page. 9952 Device-specific parameter. 10053 Buffered modes. 10054 speed field definition 10055 Sequential-

31、access density codes 10156 Mode page codes 10157 Data Compression mode page 10358 Possible boundaries and resulting sense keys due to data compression . 10459 Compression algorithm identifiers. 10660 Device Configuration mode page. 10761 eod defined values. 10962 rewind on reset field definition 110

32、63 Medium Partition mode page . 11164 PSUM values . 11265 Medium format recognition values . 114vPage66 Read-Write Error Recovery mode page . 11567 Informational Exceptions Control mode page 11668 TapeAlert test descriptions 117Figures 1 SCSI document relationships 12 Example state diagram. 113 Typi

33、cal volume layout 144 Typical medium track layout 155 Serpentine recording example 156 Parallel recording example 167 Helical scan recording example 168 Early-warning example 179 Partitioning example - one partition per track group 1710 Partitioning example - one partition per two track groups . 181

34、1 Partitioning example - two partitions per track group 1812 Block address mode state diagram, overview . 2913 Block address mode state diagram, Idle state 3014 Block address mode state diagram, Explicit Address Mode - Neutral . 3215 Block address mode state diagram, Explicit Address Mode - Write Ca

35、pable 3416 Block address mode state diagram, Implicit Address Mode 36AnnexA TapeAlert log page parameter codes (flags). 119viForeword (This foreword is not part of American National Standard ANSI INCITS 380-2003.)This standard specifies the external behavior of a device server that defines itself as

36、a sequential-access device in the device type field of the INQUIRY command re-sponse data. This device type is known as a stream device. This standard conformsto the SCSI Architecture Model - 2 (T10/1157-D) standard.With any technical document there may arise questions of interpretation as newproduc

37、ts are implemented. INCITS has established procedures to issue technicalopinions concerning the standards developed by INCITS. These procedures may re-sult in SCSI Technical Information Bulletins being published by INCITS.These Bulletins, while reflecting the opinion of the Technical Committee that

38、devel-oped the standard, are intended solely as supplementary information to other usersof the standard. This standard, ANSI INCITS 380-2003, as approved through thepublication and voting procedures of the American National Standards Institute, isnot altered by these bulletins. Any subsequent revisi

39、on to this standard may or maynot reflect the contents of these Technical Information Bulletins.Current INCITS practice is to make Technical Information Bulletins available through:INCITS Online Store http:/ by Techstreet Telephone: 1-734-302-7801 or1327 Jones Drive 1-800-699-9277Ann Arbor, MI 48105

40、 Facsimile: 1-734-302-7811orGlobal Engineering http:/15 Inverness Way East Telephone: 303-792-2181 orEnglewood, CO 80112-5704 800-854-7179Facsimile: 303-792-2192Requests for interpretation, suggestions for improvement and addenda, or defect re-ports are welcome. They should be sent to the INCITS Sec

41、retariat, InterNationalCommittee for Information Technology Standards, Information Technology Institute,1250 Eye Street, NW, Suite 200, Washington, DC 20005-3922. This standard was processed and approved for submittal to ANSI by the InterNation-al Committee for Information Technology Standards (INCI

42、TS). Committee approvalof the standard does not necessarily imply that all committee members voted for ap-proval. At the time of it approved this standard, INCITS had the following members:Karen Higginbottom, ChairJennifer Garner, SecretaryOrganization Represented Name of RepresentativeApple Compute

43、r, Inc. David MichaelWanda Cox (Alt.)Farance, Inc Frank FaranceHewlett-Packard Company. Karen HigginbottomScott Jameson (Alt.)Steve Mills (Alt.)EIA Edward Mikoski, Jr.Suan Hoyler (Alt.)viiOrganization Represented Name of RepresentativeIBM Corporation Ronald F. SillettiInstitute for Certification of

44、Computer Professionals .Kenneth M. ZemrowskiThomas Kurihara (Alt.)IEEE Judith Gorman Richard Holleman (Alt.)Robert Pritchard (Alt.)Intel CorporationGregory KisorDave Thewlis (Alt.)Microsoft CorporationMike KsarFrank Camara (Alt.)National Institute of Standards b) define commands unique to the sequen

45、tial-access device type; andc) define commands to manage the operation of the sequential-access device type.Figure 1 shows the relationship of this standard to the other standards and related projects in the SCSI familystandards as of the publication of this standard.Figure 1 SCSI document relations

46、hipsThe roadmap in figure 1 is intended to show the general applicability of the documents to one another. The figure isnot intended to imply a relationship such as a hierarchy, protocol stack, or system architecture. It specifies theapplicability of a standard to the implementation of a given SCSI

47、protocol.Device-Type Specific Command SetsShared Command Set (for all device types)SCSI ProtocolsInterconnectsArchitecure ModelAMERICAN NATIONAL STANDARD BSR INCITS 380ANSI INCITS 380-2003ANSI INCITS 380-20032At the time this standard was generated, examples of the SCSI general structure included:In

48、terconnects:Automation/Drive Interface - Physical Layer ADP T10/1556-DFibre Channel Arbitrated Loop - 2 FC-AL-2 ISO/IEC 14165-122ANSI INCITS 332-1999Fibre Channel Physical Interfaces FC-PI ANSI INCITS 352-2002Fibre Channel Physical Interfaces - 2 FC-PI-2 T11/1506-DFibre Channel Framing and Signaling

49、 Interface FC-FS ANSI INCITS 373-2003High Performance Serial Bus ANSI IEEE 1394-1995High Performance Serial Bus ANSI IEEE 1394a-2000(supplement to ANSI/IEEE 1394-1995)SCSI Parallel Interface - 2 SPI-2 ISO/IEC 14776-112ANSI INCITS 302-1999SCSI Parallel Interface - 3 SPI-3 ISO/IEC 14776-113ANSI INCITS 336-2000SCSI Parallel Interface - 4 SPI-4