ANSI AIIM MS66-1999 Metadata for Interchange of Files on Sequential Storage Media Between File Storage Management Systems (FSMSs)《文件储存管理系统(FSMS)间系列存储介质文件互换用元数据》.pdf

上传人:brainfellow396 文档编号:430695 上传时间:2018-11-11 格式:PDF 页数:47 大小:1.87MB
下载 相关 举报
ANSI AIIM MS66-1999 Metadata for Interchange of Files on Sequential Storage Media Between File Storage Management Systems (FSMSs)《文件储存管理系统(FSMS)间系列存储介质文件互换用元数据》.pdf_第1页
第1页 / 共47页
ANSI AIIM MS66-1999 Metadata for Interchange of Files on Sequential Storage Media Between File Storage Management Systems (FSMSs)《文件储存管理系统(FSMS)间系列存储介质文件互换用元数据》.pdf_第2页
第2页 / 共47页
ANSI AIIM MS66-1999 Metadata for Interchange of Files on Sequential Storage Media Between File Storage Management Systems (FSMSs)《文件储存管理系统(FSMS)间系列存储介质文件互换用元数据》.pdf_第3页
第3页 / 共47页
ANSI AIIM MS66-1999 Metadata for Interchange of Files on Sequential Storage Media Between File Storage Management Systems (FSMSs)《文件储存管理系统(FSMS)间系列存储介质文件互换用元数据》.pdf_第4页
第4页 / 共47页
ANSI AIIM MS66-1999 Metadata for Interchange of Files on Sequential Storage Media Between File Storage Management Systems (FSMSs)《文件储存管理系统(FSMS)间系列存储介质文件互换用元数据》.pdf_第5页
第5页 / 共47页
点击查看更多>>
资源描述

1、STD-AIIM MSbb-ENGL 1997 11111 1012348 O501802 978 1111 ANSIIAIIM MS66-1999 American National Standard for Information and Image Management - Metadata for Interchange of Files on Sequential Storage Media Between File Storage Management Systems (FSMSs) An American National Standard prepared by the Ass

2、ociation for Information and Image Management International Approved as an American National Standard April 6, 1999 Abstract: This document describes a standard for specifying metadata that describes how a File Storage Management System (FSMS) has stored files on sequential media. This metadata desc

3、ription is independent of any particular proprietary metadata format, but it may be used to describe the proprietary format that an FSMS uses to write files to sequential media. COPYRIGHT Association for Information an identifier that is unique among all objects in the universe of discourse. In this

4、 con- text, a UID is unique among all of the objects in the metadata export. It need not be reproducible, since one acceptable method of generating such an ID involves using a time stamp. 4.34 user with respect to the metadata export, the person who causes the metadata export to be written and in so

5、 doing makes the choices of record types. More generally, a person or program that commands an appli- cation. 5 Abbreviations and acronyms 5.1 DCE Distributed Computing Environment. 8 ASSOCIATION FOR INFORMATION AND IMAGE MANAGEMENT INTERNATIONAL COPYRIGHT Association for Information however, in the

6、 representations of clauses 7 through IO, they are all upper case. This standard does not impose a limit to the length of a record or to the length of any of the information fields. The only length restrictions are imposed by the operating system that writes the metadata. Simi- larly, the size of th

7、e numbers that are likely to be encountered in the metadata is not limited by the stan- ASSOCIATION FOR INFORMATION AND IMAGE MANAGEMENT INTERNATIONAL 9 COPYRIGHT Association for Information 2. metadata describing the removable media being exchanged; 3. metadata describing the file segments on the r

8、emovable media being exchanged; 4. metadata describing the directory and file structure being exchanged. The metadata export shall consist of four sections, one corresponding to each of the four types. If the metadata export is presented as one file, then the first section shall contain all of the m

9、etadata of the first type, and each of the other sections shall contain all of the metadata of one of the other types and may occur in any order. For metadata export, it is also acceptable that each of these sections be in a separate file if the files are appropriately identified. 6.5 Order If the o

10、rder of a particular record is not specified, it may appear in any order, if that does not conflict with records whose order is specified. Similarly, if the order of fields is not specified, then they may be in any order. For example, in the second section of the metadata, all records following a Ca

11、rtridge Identifier record refer to the cartridge identified in it, until another Cartridge Identifier record is encountered. The records between the Cartridge Identifier records may be in any order. 6.6 Counting and counts All counting in the metadata shall be zero-based. That is, the first element

12、shall be element O; the second element shall be element 1, etc. For example, a stripe set consisting of five cartridges shall have the 10 ASSOCIATION FOR INFORMATION AND IMAGE MANAGEMENT INTERNATIONAL COPYRIGHT Association for Information NO if not. Record category: Required. Example: CART-DRlVE-TYP

13、E0MFR0ABC0MODEL0XYZ40000 TY PE0MNZ0DRIVE-COMPRESSlON0YES0 Rationale: This record, with the record described in 8.2, is designed to remove any ambiguity in speci- fying a drive for reading or writing the cartridge. 8.4 Cartridge layout Record name: CART-LAYOUT Description: This record describes the h

14、igh level layout of the data on the cartridge. For the purposes of this standard, all cartridges are assumed to be partitioned into at least one partition, even if partitioning is not supported by that cartridge technology. Named fields: NO-PARTITIONS: The number of partitions on the cartridge. This

15、 number shall always be at least 1. NO-SIDES: The number of sides on the cartridge. This number shall always be at least I. SIDE-NO, PARTITION-NO, PARTITION -NAME, LABEL-TYPE, INTERNAL-LABEL, SIZE-MB, FREE-SPACE-MB: These fields shall appear with the SIDE-NO and PARTITION-NO fields first in that ord

16、er. The remaining fields (LABEL-TYPE, INTERNAL-LABEL, SIZE-MB, FREE-SPACE-MB) may appear in any order, and all refer to the partition on the side specified by the two previous fields. This entire group of fields shall be repeated for as many partitions as there are on the cartridge. SIDE-NO: The sid

17、e number. PARTITION-NO: The number of one of the partitions on the tape. Partitions are to be numbered con- secutively, in physical order, O, 1, 2, 3, . n-I, where there are n partitions on a side of the cartridge. PARTITION-NAME: The name, if any, of the partition. If the partition is not named, th

18、en this field may be omitted. SIZE-MB: The estimated capacity of the partition, in MB, represented as an integer, rounded to the nearest MB (1 024 x 1024). FREE-SPACE-MB: The estimated free space of the partition, in MB, represented as an integer, rounded to the nearest MB (1 024 x 1024). LABEL-TYPE

19、: The name of the label format, assuming that there is an internal label on the cartridge or partition. If this label conforms to a standard, this is the name and number of the standard. Otherwise the label format shall be named and described in a separate document, and the name specified in that do

20、cument shall be used for this field. INTERNAL-LABEL: The contents of the internal label, sufficient to do label checking. ASSOCIATION FOR INFORMATION AND IMAGE MANAGEMENT INTERNATIONAL 15 COPYRIGHT Association for Information & Imaging ManagementLicensed by Information Handling ServicesANSIIAIIM MS6

21、6-1999 - METADATA FOR INTERCHANGE OF FILES ON SEQUENTIALSTORAGE MEDIA BETWEEN FILE STORAGE MANAGEMENTSYSTEMS (FSMSs) Record category: Required. Example: CART-LAY OUT0N O-PARTI TI O NS03 0NO-SI DES 0 1 OSI D E-N O 00 0 PARTITION-NO000LABEL-FORMAT0XYZ1.201NTERNAL-LABEL0 My-First-Partition0SIZE-MB0 1 5

22、060000000FREESPACEMB04940000000 SI DE-NO000PARTI TI ON-NO0 1 0LABEL-TY P E0XYZ2.101 NTERN AL-LABEL0 MySecondPartition0SIZEMB012060000000FREESPACEMB07940000000 SIDE-NO000PARTITION-NO020LABEL-FORMAT0XYZ2.10 INTERNAL-LABEL0My-Third-Partition0SIZE-MB01 O01 0000000 FREE-SPACE-MB0239805 Rationale: This re

23、cord specifies the top level structure of the cartridge so that the cartridge can be prop- erly identified and positioned at the proper partition. 8.5 Cartridge number of blocks between tape marks Record name: CART-NO-BLOCKS-BETWEEN-TM Description: This record specifies the number of blocks between

24、tape marks, if constant throughout the cartridge (except possibly for the last collection of blocks). Named fields: None. Record category: Required Example: For a cartridge where the number of blocks between tape marks is constant, CART-NO-BLOCKS-BETWEEN-TM0480$ Rationale: At least one FSMS implemen

25、tation sets a maximum for the number of fixed length data blocks that may appear contiguously on a tape without being interrupted by a tape mark. This is a char- acteristic of the cartridge, imposed by the FSMS, and the presence of a tape mark does not necessarily indicate the end of a file or file

26、segment. 8.6 Cartridge number of bytes after tape marks Record name: CART-NO-BYTES-AFTER-TM Description: This record specifies the number of bytes after a tape mark that are not part of the original file but instead consist of control information written by the FSMS. Named fields: 16 ASSOCIATION FOR

27、 INFORMATION AND IMAGE MANAGEMENT INTERNATIONAL COPYRIGHT Association for Information & Imaging ManagementLicensed by Information Handling ServicesSTD-AIIM MShh-ENGL 1999 111 1012348 050182b 301 ANSIIAIIM MS66-1999 - METADATA FOR INTERCHANGE OF FILES ON SEQUENTIAL STORAGE MEDIA BETWEEN FILE STORAGE

28、MANAGEMENTSYSTEMS (FSMSs) NO-BLOCKS: The number of blocks containing the specified number of bytes. NO-BYTES: The total number of bytes in the blocks. Record category: Required. Example: For a cartridge where a 64 byte block after the tape mark is used for control information, CART-NO-BYTES-AFTER-TM

29、0NO-BLOCKS010NO-BYTES0640 For a cartridge where 64 bytes of control information is after the tape mark but in two blocks (not neces- sarily of equal length), CART-NO-BYTESAFTER-TM0NO-BLOCKS020NO-BYTES0640 Rationale: At least one FSMS implementation follows each tape mark with a fixed amount of contr

30、ol information that is not part of a file segment. 8.7 Cartridge block size Record name: CART-BLOCK-SIZE Description: This record specifies the block structure on the cartridge as it is seen and written by the FSMS, giving the block size in bytes if it is fixed (constant) throughout the cartridge. N

31、amed fields: MODE: Either FIXED or VARIABLE, depending on whether the block size is fixed or variable. SIZE: The size in bytes of the blocks, if MODE is FIXED. Otherwise this field shall be omitted. Record category: Required Example: CARTBLOCKSIZE0MODE0FIXED0SlZE010240 Rationale: MODE refers to the

32、data blocks on a cartridge, not to any control information that may be written in a different block size. If the data blocks are all of the same size, then MODE should be FIXED and SIZE should be provided, otherwise mode should be VARIABLE. 8.8 Cartridge family Record name: CART-FAMILY Description:

33、If families are supported, this record names the family to which this cartridge belongs. If multiple families are supported for a single cartridge, then this should list the families for this cartridge in any order. Named fields: None. Record category: Selectable ASSOCIATION FOR INFORMATION AND IMAG

34、E MANAGEMENT INTERNATIONAL 17 COPYRIGHT Association for Information & Imaging ManagementLicensed by Information Handling ServicesSTD=AIIM MSbb-ENGL 1999 W 1012348 0501827 248 B ANSI/AIIM MS66-1999 - METADATA FOR INTERCHANGE OF FILES ON SEQUENTIALSTORAGE MEDIA BETWEEN FILE STORAGE MANAGEMENTSYSTEMS (

35、FSMSs) Example: For the case where there is only one family, CART-FAMI LY0DAAC-TRMM0S For the case where there are two families, CART-FAM I LY0Accou ntin g0Ch emisty09 Rationale: At least one FSMS implementation allows the arbitrary grouping of cartridges into sets which are called families. No addi

36、tional information is implied in this grouping. 8.9 Cartridge billing ID Record Name: CART-BI LLI NG-I D Description: If a billing ID is associated with this cartridge, this field specifies the billing ID. Named fields: None. Record cat ego ry: Sel e cta bl e. Example: CART-BI LLING-I D0JSC587209 Ra

37、tionale: Some implementations allow for billing on the cartridge level. 8.10 Cartridge volume group Record name: C ART-VOL-G ROUP Description: If volume groups are supported, this record specifies the volume group to which this car- tridge belongs. Named fields: NAME: This specifies the name of the

38、volume group. BLOCKSIZE: This specifies the block size in uncompressed bytes for all of the cartridges in this volume group. COMPRESSIONALLOWED: This specifies whether compression is allowed or not. The value of this field is to be either YES or NO. Record category: Selectable. Example: CARTVOLGROUP

39、0NAME0Accounting0BLOCKSIZE040960 COMPRESSION_ALLOWED0NO0 18 ASSOCIATION FOR INFORMATION AND IMAGE MANAGEMENT INTERNATIONAL COPYRIGHT Association for Information & Imaging ManagementLicensed by Information Handling ServicesSTD*AIIM MSbb-ENGL 1999 W 3032348 0503828 384 BB ANSI/AIIM MS66-1999 - METADAT

40、A FOR INTERCHANGE OF FILES ON SEQUENTIALSTORAGE MEDIA BETWEEN FILE STORAGE MANAGEMENTSYSTEMS (FSMSs) Rationale: At least one implementation allows the association of specific cartridges with a directory structure and its contents. This allows the user to specify that the contents of a directory stru

41、cture is al- ways placed in a defined set of cartridges. In addition, the user can specify the block size and whether compression is allowed for these cartridges or not. In most cases, users want the data compressed by the drive when it is written onto the cartridges. However in some cases, the user

42、s forbid any compression because they fear loss of data or they have already compressed their data and do not want the drive to compress it again. Examples are medical data and video data. 8.11 Cartridge location Record name: CART-LOC Description: This record specifies the current location of the ca

43、rtridge. Named fields: CART-LIB: The name of the Library or Physical Volume Repository in which the cartridge resides. There is no universal naming scheme for libraries. The name could be a string, a SCSI-ID, or an IP address. There will be cases where a library will hold thousands of cartridges. Du

44、ring an FSMS migration, it may be unreasonable to assume that each cartridge will be ejected and then reloaded into the same library under the new FSMS. This allows for the translation of the name of the library from the exporting FSMS to the importing FSMS. The meaning of the library name shall be

45、documented by the exporting FSMS. CART-PLACE: A string describing the current location of the cartridge within the Library or Physical Vol- ume Repository. There is no universal location naming scheme within libraries. There will be cases where a library will hold thousands of cartridges. During an

46、FSMS migration, it may be unreasonable to assume that each cartridge will be ejected and then reloaded into the same library under the new FSMS. This field allows for the translation of the location from the exporting FSMS to the importing FSMS. The meaning of the location string shall be documented

47、 by the exporting FSMS. Record category: Selectable. Example: CART-LOC0CART-LIB0Vaultl0 CART_PLACE0RackG,Shelf30$ Rationale: This record is intended to aid in the situation where one FSMS is being replaced by another in the same facility. 8.12 Cartridge lot Record name: CART-LOT Description: The lot

48、 number or lot identifier of the cartridge. This may include a cartridge vendor name. Named fields: None. Record category: Selectable. Example : CART-LOT01 7649030s Rationale: This information is useful for management purposes, since cartridge quality may vary by lot. ASSOCIATION FOR INFORMATION AND

49、 IMAGE MANAGEMENT INTERNATIONAL 19 COPYRIGHT Association for Information & Imaging ManagementLicensed by Information Handling ServicesSTD=AIIM MSbb-ENGL 1999 1012348 0501829 O10 E ANSVAIIM MS66-1999 - METADATA FOR INTERCHANGE OF FILES ON SEQUENTIALSTORAGE MEDIA BETWEEN FILE STORAGE MANAGEMENTSYSTEMS (FSMSs) 8.13 Cartridge statistics Record name: CART-STATS Description: Statistics on the use of the cartridge. Named fields: NO-MOUNTS: The number of times the cartridge has been mounted. CREATION: The time the cartridge was created, in the form yyyy/mm/dd/hh:mm:ss. The time zone s

展开阅读全文
相关资源
  • ANSI Z97 1-2009 American National Standard for Safety Glazing Materials used in Buildings - Safety Performance Specifications and Methods of Test《建筑物中窗用玻璃材料安全性用.pdfANSI Z97 1-2009 American National Standard for Safety Glazing Materials used in Buildings - Safety Performance Specifications and Methods of Test《建筑物中窗用玻璃材料安全性用.pdf
  • ANSI Z97 1 ERTA-2010 Re ANSI Z97 1 - 2009 Errata《修订版 美国国家标准学会Z97 1-2009标准的勘误表》.pdfANSI Z97 1 ERTA-2010 Re ANSI Z97 1 - 2009 Errata《修订版 美国国家标准学会Z97 1-2009标准的勘误表》.pdf
  • ANSI Z21 40 2a-1997 Gas-Fired Work Activated Air-Conditioning and Heat Pump Appliances (Same as CGA 2 92a)《燃气、工作激活空气调节和热泵器具(同 CGA 2 92a)》.pdfANSI Z21 40 2a-1997 Gas-Fired Work Activated Air-Conditioning and Heat Pump Appliances (Same as CGA 2 92a)《燃气、工作激活空气调节和热泵器具(同 CGA 2 92a)》.pdf
  • ANSI Z124 9-2004 American National Standard for Plastic Urinal Fixtures《塑料小便器用美国国家标准》.pdfANSI Z124 9-2004 American National Standard for Plastic Urinal Fixtures《塑料小便器用美国国家标准》.pdf
  • ANSI Z124 4-2006 American National Standard for Plastic Water Closet Bowls and Tanks《塑料抽水马桶和水箱用美国国家标准》.pdfANSI Z124 4-2006 American National Standard for Plastic Water Closet Bowls and Tanks《塑料抽水马桶和水箱用美国国家标准》.pdf
  • ANSI Z124 3-2005 American National Standard for Plastic Lavatories《塑料洗脸盆用美国国家标准》.pdfANSI Z124 3-2005 American National Standard for Plastic Lavatories《塑料洗脸盆用美国国家标准》.pdf
  • ANSI T1 659-1996 Telecommunications - Mobility Management Application Protocol (MMAP) RCF-RACF Operations《电信 可移动管理应用协议(MMAP) RCF-RACF操作》.pdfANSI T1 659-1996 Telecommunications - Mobility Management Application Protocol (MMAP) RCF-RACF Operations《电信 可移动管理应用协议(MMAP) RCF-RACF操作》.pdf
  • ANSI T1 651-1996 Telecommunications – Mobility Management Application Protocol (MMAP)《电信 可移动性管理应用协议》.pdfANSI T1 651-1996 Telecommunications – Mobility Management Application Protocol (MMAP)《电信 可移动性管理应用协议》.pdf
  • ANSI T1 609-1999 Interworking between the ISDN User-Network Interface Protocol and the Signalling System Number 7 ISDN User Part《电信 ISDN用户间网络接口协议和7号信令系统ISDN用户部分.pdfANSI T1 609-1999 Interworking between the ISDN User-Network Interface Protocol and the Signalling System Number 7 ISDN User Part《电信 ISDN用户间网络接口协议和7号信令系统ISDN用户部分.pdf
  • ANSI T1 605-1991 Integrated Services Digital Network (ISDN) - Basic Access Interface for S and T Reference Points (Layer 1 Specification)《综合服务数字网络(ISDN) S和T基准点的.pdfANSI T1 605-1991 Integrated Services Digital Network (ISDN) - Basic Access Interface for S and T Reference Points (Layer 1 Specification)《综合服务数字网络(ISDN) S和T基准点的.pdf
  • 猜你喜欢
    相关搜索

    当前位置:首页 > 标准规范 > 国际标准 > ANSI

    copyright@ 2008-2019 麦多课文库(www.mydoc123.com)网站版权所有
    备案/许可证编号:苏ICP备17064731号-1