ANSI INCITS441-2008 Information technology - Automation Drive Interface - Commands - 2 (ADC-2)《信息技术.自动控制接口 驱动接口.命令.2(ADC-2)》.pdf

《ANSI INCITS441-2008 Information technology - Automation Drive Interface - Commands - 2 (ADC-2)《信息技术.自动控制接口 驱动接口.命令.2(ADC-2)》.pdf》由会员分享，可在线阅读，更多相关《ANSI INCITS441-2008 Information technology - Automation Drive Interface - Commands - 2 (ADC-2)《信息技术.自动控制接口 驱动接口.命令.2(ADC-2)》.pdf（83页珍藏版）》请在麦多课文档分享上搜索。

1、American National StandardDeveloped byfor Information Technology Automation/DriveInterface Commands - 2(ADC-2)ANSI INCITS 441-2008ANSIINCITS441-2008Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without li

2、cense from IHS-,-,-Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-ANSIINCITS 441-2008American National Standardfor Information Technology Automation/Drive Interface Commands -

3、2(ADC-2)SecretariatInformation Technology Industry CouncilApproved May 12, 2008American National Standards Institute, Inc.AbstractThis standard specifies the device model and functional requirements for the SCSI automation/driveinterface device type. This standard permits the SCSI automation/drive i

4、nterface device type tocommunicate with application clients and defines the commands and data exchanged in suchcommunications.This standard does not contain material related to the service delivery subsystem that is used to transportthe commands, command parameter data, command response data, and st

5、atus specified in this standard.Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-Approval of an American National Standard requires review by ANSI that therequirements for due pr

6、ocess, 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 agreement means much more t

7、hana 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 respect preclude anyone, whet

8、her 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 interpretation of any American Natio

9、nalStandard. 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 appears on the titlepage of

10、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 National Standards mayrecei

11、ve 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 2008 by Information Technology Industry Council (ITI)All rights res

12、erved.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 have requested that holder

13、s of patents that may be re-quired for the implementation of the standard disclose such patents to the publisher. However, nei-ther the developers nor the publisher have undertaken a patent search in order to identify which, ifany, patents may apply to this standard. As of the date of publication of

14、 this standard, followingcalls for the identification of patents that may be required for the implementation of the standard,notice of one or more such claims has been received. By publication of this standard, no positionis taken with respect to the validity of this claim or of any rights in connec

15、tion therewith. The knownpatent holder(s) has (have), however, filed a statement of willingness to grant a license underthese rights on reasonable and nondiscriminatory terms and conditions to applicants desiring to ob-tain such a license. Details may be obtained from the publisher. No further paten

16、t search is con-ducted by the developer or publisher in respect to any standard it processes. No representation ismade or implied that this is the only license that may be required to avoid infringement in the use ofthis standard.Copyright American National Standards Institute Provided by IHS under

17、license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-iContentsPageForeword vIntroduction x1 Scope. 12 Normative references. 32.1 Normative references overview .32.2 Approved references 32.3 References under development. 43 Definitions, symbols, abbrevi

18、ations, and conventions . 53.1 Definitions 53.2 Symbols and abbreviations 73.3 Keywords . 83.4 Conventions. 94 General 114.1 Automation/drive interface model overview . 114.2 Device server interaction . 124.3 ADI bridging . 144.3.1 ADI bridging introduction 144.3.2 Local SMC device server operation.

19、 144.3.3 Remote SMC device server operation. 154.3.4 Bridging manager operation. 154.3.5 Caching SMC data and status . 164.4 Load and unload states 174.4.1 Load states 174.4.2 Unload states. 194.5 Sense data masking 204.6 TapeAlert application client interface. 204.7 Medium Auxiliary Memory attribut

20、es 234.8 DT device primary ports. 234.8.1 DT device primary port index. 234.8.2 Enabling and disabling DT device primary ports 234.9 Sequential mode operation 235 Commands for automation/drive interface devices 255.1 Summary of commands for automation/drive interface devices 255.2 NOTIFY DATA TRANSF

21、ER DEVICE command 285.3 SET MEDIUM ATTRIBUTE command. 305.3.1 SET MEDIUM ATTRIBUTE command introduction. 305.3.2 SET MEDIUM ATTRIBUTE parameter list format . 315.3.3 SET MEDIUM ATTRIBUTE attribute format 32Copyright American National Standards Institute Provided by IHS under license with ANSI Not fo

22、r ResaleNo reproduction or networking permitted without license from IHS-,-,-iiPage6 Parameters for automation/drive interface devices . 336.1 Log parameters 336.1.1 Log parameters overview 336.1.2 DT Device Status log page 346.1.2.1 DT Device Status log page overview. 346.1.2.2 Very high frequency

23、data log parameter 346.1.2.3 Very high frequency polling delay log parameter. 386.1.2.4 DT device primary port status log parameter(s) 396.1.3 TapeAlert Response log page . 426.1.4 Requested Recovery log page 436.1.4.1 Requested Recovery log page overview . 436.1.4.2 Recovery procedures log paramete

24、r . 446.1.5 Service Buffers Information log page. 466.2 Mode parameters. 496.2.1 Mode parameters overview . 496.2.2 ADC Device Server Configuration mode page 516.2.2.1 Target Device subpage 516.2.2.2 DT Device Primary Port subpage 536.2.2.3 Logical Unit subpage . 596.2.2.4 Target Device Serial Numbe

25、r subpage 666.3 Vital product data parameters 676.3.1 Vital product data parameters overview and page codes 676.3.2 Device Identification VPD page . 686.3.3 Manufacturer-assigned Serial Number VPD page. 68Tables1 ISO and American numbering conventions examples. 92 Load states 173 Load states example

26、 184 Unload states. 195 Additional conditions that cause TapeAlert state flags to be set to zero . 216 Command set for automation/drive interface. 257 NOTIFY DATA TRANSFER DEVICE command . 288 SET MEDIUM ATTRIBUTE command 309 SET MEDIUM ATTRIBUTE parameter list format . 3110 SET MEDIUM ATTRIBUTE att

27、ribute format 3211 ATTRIBUTE IDENTIFIER field 3212 FORMAT field . 3213 Log page codes . 3314 DT Device Status log page 3415 DT Device Status log page parameter codes 3416 Very high frequency data log parameter format 35Copyright American National Standards Institute Provided by IHS under license wit

28、h ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-iiiPage17 VHF data descriptor . 3518 DT DEVICE ACTIVITY field 3719 Very high frequency polling delay log parameter format 3820 DT device primary port status log parameter(s) format 3921 Port status data format

29、by protocol identifier 3922 Fibre Channel port status data format 4023 SCSI parallel interface port status data format 4124 Serial Attached SCSI port status data format 4125 TapeAlert Response log page 4226 Requested Recovery log page. 4327 Requested Recovery log page parameter codes. 4328 Requested

30、 recovery log parameter format. 4429 Recovery procedures . 4530 Service Buffers Information log page . 4631 Service buffer information log parameter format 4732 Service buffer information parameter codes 4733 Mode page codes. 5034 Target Device subpage 5135 MTDN field . 5236 DT Device Primary Port s

31、ubpage. 5337 DT device primary port descriptor format. 5338 Primary port descriptor by protocol identifier value 5439 Fibre Channel descriptor parameter format . 5440 TOPLOCK bit, P2P bit, and TOPORD bit interaction 5541 Effect of LIV and RHA bits 5542 MPN field . 5643 SPEED field 5744 Parallel SCSI

32、 descriptor parameter format 5745 BMQ field . 5746 Serial Attached SCSI descriptor parameter format 5847 MPI field 5848 Logical Unit subpage 5949 RMC logical unit descriptor format. 6050 MLUD field . 6151 AUTOLOAD MODE field 62Copyright American National Standards Institute Provided by IHS under lic

33、ense with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-ivPage52 SMC logical unit descriptor format. 6353 ADC logical unit descriptor format . 6554 Target Device Serial Number subpage 6655 MPSN field. 6756 ADC device VPD page codes 6757 Manufacturer-assigned

34、 Serial Number VPD page. 68Figures1 General Document Structure of SCSI 12 Example of an automation device and DT device relationship 123 Device server model 13Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted

35、 without license from IHS-,-,-vForeword (This foreword is not part of American National Standard ANSI INCITS 441-2008.)This standard specifies the external behavior of a device server that defines itself asan automation/drive interface device in the DEVICE TYPE field of the standardINQUIRY data. Thi

36、s device type is known as an automation/drive interface device.Requests for interpretation, suggestions for improvement and addenda, or defectreports are welcome. They should be sent to the INCITS Secretariat, InterNationalCommittee for Information Technology Standards, Information Technology Instit

37、ute,1250 Eye Street, NW, Suite 200, Washington, DC 20005-3922. This standard was processed and approved for submittal to ANSI by the InterNa-tional Committee for Information Technology Standards (INCITS). Committeeapproval of the standard does not necessarily imply that all committee membersvoted fo

38、r approval. At the time it approved this standard, INCITS had the followingmembers:Karen Higginbottom, ChairJennifer Garner, SecretaryOrganization Represented Name of RepresentativeAdobe Systems, Inc Steve ZillesScott Foshee (Alt.)AIM Global Dan MullenCharles Biss (Alt.)Apple Computer, Inc. David Mi

39、chaelDistributed Managment Task Force . Tony DiCenzoElectronic Industries Alliance Edward Mikoski, Jr.EMC Corporation Gary RobinsonFarance, Inc Frank FaranceTimothy Schoechle (Alt.)Google Zaheda BhoratGS1 US Ray DelnickiFrank Sharkey (Alt.)James Chronowski (Alt.)Mary Wilson (Alt.)Hewlett-Packard Com

40、pany. Karen HigginbottomSteve Mills (Alt.)Scott Jameson (Alt.)IBM Corporation . Ronald F. SillettiRobert Weir (Alt.)Sandy Block (Alt.)Richard Schwerdtfeger (Alt.)IEEE . Judith GormanTerry DeCourcelle (Alt.)Bill Ash (Alt.)Jodi Haasz (Alt.)Bob Labelle (Alt.)Susan Tatiner (Alt.)Intel. Philip WennblomDa

41、ve Thewlis (Alt.)Grace Wei (Alt.)Lexmark International . Don WrightDwight Lewis (Alt.)Paul Menard (Alt.)Microsoft Corporation . Jim HughesDave Welsh (Alt.)Isabelle Valet-Harper (Alt.)Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction

42、 or networking permitted without license from IHS-,-,-viOrganization Represented Name of RepresentativeNational Institute of Standards b) define commands unique to the automation/drive interface device type; andc) define commands and parameters to manage the operation of the automation/drive interfa

43、ce device typeand the operation of logical units of other specific device types that are present in the same device as theautomation/drive interface logical unit.The following commands, parameter data, and features defined in previous versions of this standard are madeobsolete by this standard: Link

44、ed commands.Figure 1 shows the relationship of this standard to the other standards and related projects in the SCSI family ofstandards as of the publication of this standard.Figure 1 General Document Structure of SCSIAmerican National Standard ANSI INCITS 441-2008SCSIArchitectural Model (e.g.,SAM-3

45、)Device-type specific command sets (e.g., SSC-2, this standard)Primary command set(e.g., SPC-3)SCSI transport protocols (e.g., SCSI encapsulation in ADT-2)Interconnects (e.g., ADT-2)Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction

46、or networking permitted without license from IHS-,-,-ANSI INCITS 441-20082Figure 1 is intended to show the general relationship of the documents to one another. Figure 1 is not intended toimply a relationship such as a hierarchy, protocol stack, or system architecture. It indicates the applicability

47、 of astandard to the implementation of a given transport.Commands in this standard do not require the use of a specific SCSI transport protocol.Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without licens

48、e from IHS-,-,-ANSI INCITS 441-200832 Normative references2.1 Normative references overviewThe following standards contain provisions that, by reference in the text, constitute provisions of this standard. Atthe time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agree-ments based on this standard are encouraged to investigate the possibility of applying the most recent editions ofthe standards listed below.Copies of the following documents may be obtained from ANSI: approved ANSI standards, approved and draft